US20140379966A1 - Distributed Storage Service Systems and Architecture - Google Patents
Distributed Storage Service Systems and Architecture Download PDFInfo
- Publication number
- US20140379966A1 US20140379966A1 US14/317,950 US201414317950A US2014379966A1 US 20140379966 A1 US20140379966 A1 US 20140379966A1 US 201414317950 A US201414317950 A US 201414317950A US 2014379966 A1 US2014379966 A1 US 2014379966A1
- Authority
- US
- United States
- Prior art keywords
- storage module
- application
- host device
- lsd
- external
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000004891 communication Methods 0.000 claims abstract description 88
- 238000000034 method Methods 0.000 claims abstract description 78
- 230000004044 response Effects 0.000 claims description 11
- 230000008878 coupling Effects 0.000 claims 3
- 238000010168 coupling process Methods 0.000 claims 3
- 238000005859 coupling reaction Methods 0.000 claims 3
- 238000013500 data storage Methods 0.000 abstract description 12
- 230000000977 initiatory effect Effects 0.000 abstract 1
- 230000008569 process Effects 0.000 description 60
- 239000003795 chemical substances by application Substances 0.000 description 28
- 238000012546 transfer Methods 0.000 description 13
- 238000001514 detection method Methods 0.000 description 12
- 238000007726 management method Methods 0.000 description 11
- 230000008901 benefit Effects 0.000 description 9
- 230000008859 change Effects 0.000 description 7
- 230000003993 interaction Effects 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 238000013459 approach Methods 0.000 description 4
- 238000004590 computer program Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 238000013475 authorization Methods 0.000 description 3
- 229920001690 polydopamine Polymers 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000001404 mediated effect Effects 0.000 description 1
- 230000007935 neutral effect Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 239000000344 soap Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000002195 synergetic effect Effects 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
- G06F3/0679—Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0238—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
- G06F12/0246—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
- G06F3/0607—Improving or facilitating administration, e.g. storage management by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0662—Virtualisation aspects
- G06F3/0664—Virtualisation aspects at device level, e.g. emulation of a storage device or system
Definitions
- the present invention relates generally to digital devices. More particularly, the present invention relates to providing cross platform mass storage services for digital devices.
- Mass storage devices such as FLASH memory that includes SD and MMC type mass storage devices
- FLASH memory that includes SD and MMC type mass storage devices
- This increase in available storage capacity has had a synergistic effect on the general availability of devices whose capabilities can depend greatly on available memory.
- Such devices include portable digital devices such as portable media players, interactive personal communication devices (cell phones, PDAs, etc.) and the like. In this way, a digital consumer's exposure to digital products that rely upon the storage capability of mass storage devices such as FLASH memory has greatly increased. Exposure that typically spans across multiple devices—connected or unconnected—or access modes—wired vs. wireless, fixed vs. mobile etc.—each having specific storage requirements.
- a digital consumer's storage management can be fragmented with personal content spread across various locations, various devices, and managed in a ‘silo mode’ resulting in content not synchronized, backed-up etc.
- a consumer can possess a cell phone, a PDA, a multimedia player, a tablet PC, each of which can have different manufacturers, used different operating systems, different storage protocols, etc.
- legacy digital devices are based upon a master/slave paradigm in that a host device (as master) is coupled by way of a legacy interface to a legacy slave device that typically takes the form of a logical block addressing (LBA) mass storage device.
- LBA logical block addressing
- the master/slave paradigm dictates that the legacy mass storage device and its contents be fully managed by the host device (including a host device file system).
- the host device and legacy storage device are locked into a master/slave relationship imposed by the physical link connecting them in that it is the host device (and in some cases, but not all, the host file system) that initiates all transactions between the host device and the legacy mass storage device. Therefore, the master/slave paradigm between host device and legacy mass storage device whereby the host device manages the legacy mass storage device using various LBA commands, poses further constraints on any possible solution.
- a proposed solution includes integrating a client agent on the host device.
- the client agent is application specific.
- the client agent can enable back up of the portable memory device, or the client agent can enable “content push” from a server computer to the portable memory device.
- the client agent can also provide a translation layer into LBA commands as well as provide a platform for processing by the host computer (thereby off-loading the most processor intensive operations from the portable memory device to the host computer).
- using a client agent on the host computer presents its own set of problems. One such problem is related to the heterogeneity of host operating systems, particularly in mobile platforms.
- One embodiment describes a computing system that includes at least a host device (HD), a local storage device (LSD) managed by the HD.
- the LSD does not utilize any interface to a device external to the HD other than that interface provided by the HD.
- the LSD prompts the HD to execute a requested process with a LSD logical request.
- the LSD logical request is not created to serve a HD initiated process.
- the computing system also includes a HD/LSD interface providing a communication path between the HD and the LSD.
- a computing system in another embodiment, includes at least a host device having at least a host device file system, and a local storage device (LSD) coupled to the host device by way of a HD/LSD interface.
- the LSD does not utilize any interface to a device external to the HD other than that interface provided by the HD.
- the LSD has at least one storage area managed by the HD.
- the HD manages the at least one storage area by sending a block command to the at least one storage area by way of the HD/LSD interface.
- the LSD prompts the HD to execute a requested process with a LSD logical request.
- the LSD logical request is not created to serve a HD initiated process.
- the LSD generates the LSD logical request, associates the LSD logical request with a LSD interrupt, and raises the LSD interrupt to the attention of the host device thereby prompting the host device to execute the requested process.
- a computing system in yet another embodiment, includes a host device having at least a host device file system (HDFS), and a local storage device (LSD) coupled to the host device by way of a HD/LSD interface.
- the LSD does not utilize any interface to a device external to the HD other than that interface provided by the HD.
- the LSD has at least one storage area managed at least by the HD and the HD manages the at least one storage area by sending a block command to the at least one storage area by way of the HD/LSD interface.
- the LSD responds to a polling of the LSD by the host device with a LSD logical request.
- the LSD logical request is not created to serve a HD initiated process.
- the LSD prompts the HD to execute a requested process with the LSD logical request.
- the polling by the host device is independent of any HDFS initiated process.
- a method performed by a computing system includes a local storage device (LSD) having at least one storage area, where the LSD is managed by a host device (HD) by passing at least a block command to the LSD by way of a HD/LSD interface.
- the LSD does not utilize any interface to a device external to the HD other than that interface provided by the HD.
- the method can be carried out by performing at least the following operation: prompting the HD by the LSD to execute a requested process with a LSD logical request.
- the LSD logical request is not created to serve a HD initiated process.
- a computing system in another embodiment, includes at least a host device (HD) having at least a host device file system and a LSD driver, and a local storage device (LSD) having at least one storage area managed by the host device file system.
- the HDFS manages the at least one storage area by generating a block command and passing the block command to the at least one storage area by way of the HD/LSD interface.
- the system also includes an application in communication with the host device. The application does not utilize any communication paths between the application and either the host device file system or the LSD driver. The application compels the LSD to perform at least one storage operation on the at least one storage area without intervention by the host device file system.
- the computing system includes at least a host device (HD) having at least a host device file system and a LSD driver, a local storage device (LSD) having at least one storage area managed at least by the host device file system, and an application in communication with the host device wherein the application does not utilize any communication paths between the application and either the LSD driver or the host device file system.
- the method includes at least the following operation: compelling the LSD to perform at least one storage operation on the at least one storage area by the application without intervention by the host device file system.
- Computer program product executed by a processor included in a computing system having a local storage device (LSD) managed by a host device (HD) wherein the HD manages the LSD by passing at least a block command to the LSD by way of a HD/LSD interface, wherein the LSD does not utilize any interface to a device external to the HD other than that interface provided by the HD is disclosed.
- the computer program product includes computer code for prompting the HD by the LSD to execute a requested process with a LSD logical request wherein the LSD logical request is not created to serve a HD initiated process and computer readable medium for storing the computer code.
- Computer program product executed by a processor in a computing system having at least a host device (HD) having at least a host device file system and a LSD driver, a local storage device (LSD) having at least one storage area managed by the host device file system, and an application in communication with the host device wherein the application does not utilize any communication paths between the application and either the LSD driver and the host device file system is disclosed.
- the computer program product includes computer code for compelling the LSD to perform at least one storage operation on the at least one storage area by the application without intervention by the host device file system and computer readable medium for storing the computer code.
- FIG. 1 shows a symbolic representation of a system in accordance with an embodiment of the invention.
- FIG. 2 illustrates a host device/local storage device system in accordance with an embodiment of the invention.
- FIGS. 3A and 3B shows a computing system in accordance with an embodiment of the invention.
- FIG. 4 shows a computing system in accordance with an embodiment of the invention.
- FIGS. 5A-5B show a more detailed view of network shown in FIG. 3 .
- FIG. 6 shows a flowchart detailing a process in accordance with an embodiment of the invention.
- FIG. 7 shows a flowchart detailing a process in accordance with an embodiment of the invention.
- FIG. 8 shows a representative media network in accordance with an embodiment of the invention.
- FIG. 9 shows a representative system illustrating additional components typically found in host device.
- Such user oriented storage services can be used for improving a user's digital content consumption experience that typically spans across multiple devices—connected or unconnected—or access modes—wired vs. wireless, fixed vs. mobile etc.—each having specific storage requirements.
- the invention goes beyond the strict limitations of the host managed, LBA-based mass storage paradigm and provides a storage services paradigm that while fully backward compatible with legacy mass storage devices enhances mass storage with other kinds of interactions.
- Other kinds of interactions that, for example, allow for storage resources and service building blocks to be potentially distributed across various physical locations (i.e., a data storage device, in a host computer, or across a network).
- the storage services paradigm provides that a local data storage device is now capable of 1) interactions with other data storage devices present in the same host computer, or with applications running on a remote server computer, and 2) the interactions can be initiated by the data storage device itself, by a host application or by a remote server.
- the invention can further pertain to an electronic system that includes a memory device discussed above.
- Memory devices i.e., memory cards
- the memory device is often removable from the electronic system so the stored digital data is portable.
- the memory devices according to the invention can have a relatively small form factor and be used to store digital data for electronics products that acquire data, such as cameras, hand-held or notebook computers, network cards, network appliances, set-top boxes, hand-held or other small media (e.g., audio) players/recorders (e.g., MP3 devices), and medical monitors.
- Embodiments of the invention are discussed below with reference to FIGS. 1-9 . However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the invention extends beyond these limited embodiments. It should be noted that it is contemplated that the invention can be used for any type of local data storage devices that can include non-volatile memory such as Multi Media Card (MMC) and Secure Digital Card (SD).
- MMC Multi Media Card
- SD Secure Digital Card
- FIG. 1 shows a symbolic representation of master device/slave system 100 in accordance with an embodiment of the invention.
- master/slave is a model for a communication protocol where one device or process has unidirectional control over one or more other devices. Once a master/slave relationship between devices or processes is established, the direction of control is always from the master to the slaves. In some systems a master is elected from a group of eligible devices with the other devices acting in the role of slaves. Accordingly, master/slave system 100 (hereinafter referred to simply as system 100 ) includes master device 102 and slave device 104 that relate to each other, in part, by way of conventional master/slave paradigm 106 . It should also be noted that slave device 104 has no interface to any device external to master device 102 other than that provided by master device 102 .
- Master device 102 can operate a number of master device processes 108 .
- master device process it is meant a process executed solely for the benefit of the master device.
- Such master device processes can include any number and type of processes such as, for example, a fetch instruction command useful in providing master device 102 with an executable instruction.
- Master device processes 108 can include master device processes 110 , 112 , and 114 each of which can be executed by processing unit 116 . Any of the processes 110 , 112 or 114 can request service from slave device services 118 .
- Process 110 for example, can request service from slave device service 118 by generating master device request 120 .
- Slave device service 118 can respond to master device request 120 with slave service response 122 .
- master device request 120 can take the form of a READ command and requested slave service response 122 can take the form of DATA.
- slave device 104 can not prompt nor in any manner cause master device 102 to execute any process outside of master device processes 108 .
- master device 102 can only execute at least one of the master device processes 108 .
- slave device 104 can include slave device agent 126 that can associate slave device process 128 with slave device logical request 130 .
- Master device 102 can include master device agent 132 in communication with processor 116 and slave device 104 by way of slave device logical request 130 .
- master device agent 132 can use slave device logical request 130 to prompt processor 116 to execute requested slave device process 124 .
- a logical request generated by a slave device can be converted into a master device provided physical response unrelated to and independent of any master device initiated process.
- FIG. 2 shows a computing system 200 in accordance with an embodiment of the invention.
- System 200 can include slave device 104 that can take the form of local storage device (LSD) 204 .
- LSD 204 can take the form of removable memory devices such as a memory card having a relatively small form factor and can be used to store digital data for electronics products such as cameras, hand-held or notebook computers, network cards, network appliances, set-top boxes, hand-held or other small audio players/recorders (e.g., MP3 devices), and medical monitors.
- LSD local storage device
- Examples of a memory card include PC Card (formerly PCMCIA device), Flash card (e.g., Compact Flash Type I and II), Secure Digital (SD) card, Multimedia card (MMC), ATA card (e.g., Compact Flash card), memory stick, SmartMedia card.
- LSD 204 can take the form of non-removable memory devices such as SD compatible iNANDTM embedded Flash drive manufactured by SanDisk Corporation of Milpitas Calif.
- LSD 204 can communicate with master device 102 in the form of host device (HD) 202 by way of HD/LSD interface 206 .
- HD/LSD 206 can be configured as a mechanical entity (such as a socket or interconnecting bus) into which HD 202 and LSD 204 can mechanically connect.
- HD/LSD 206 can take the form of a wireless interface. Since HD 202 is a master device, HD 202 includes a processor. However, for the sake of clarity, the processor included in HD 202 is neither shown nor mentioned further in this discussion but is, nonetheless, presumed to be present.
- LSD 204 can be physically connected exclusively to HD 202 and therefore cannot access or otherwise communicate with circuits and/or applications external to computing system 200 without intervention by HD 202 . Typically, LSD 204 does not utilize any interface to a device external to HD 202 other than that interface provided by the HD 202 .
- HD 202 includes host device file system (HDFS) 208 in communication with LSD driver 210 .
- HDFS 208 can issue LSD management command 212 to LSD driver 210 .
- LSD driver 210 can, in turn, pass LSD management command 212 (appropriately formatted) to LSD 204 by way of HD/LSD interface 206 .
- LSD management command 212 can take the form of a block command in those cases where LSD 204 is configured to include a data storage array having logical block address (LBA) architecture.
- HD 202 can also include (internal) software application 214 . By internal application it is meant that software application 214 can utilize HDFS 208 and LSD driver 210 to communicate with LSD 204 .
- Such software applications can include host device operating system (HDOS) 216 and application 218 each of which typically resides in host device main memory (that can take the form of a hard disk drive, or HDD, as well as non-volatile memory such as FLASH memory).
- HDOS host
- software application 214 can utilize HDFS 208 and LSD driver 210 to communicate with LSD 204 and is therefore “visible” to HDFS 208 .
- external application 220 (referred to hereinafter as target application) does not utilize any communication path between target application 220 and either HDFS 208 and LSD driver 210 to communicate with LSD 204 and is therefore not “visible” to HDFS 208 .
- target application 220 can reside in any number of locations and devices, either locally or remotely.
- Such locations and devices can include, for example, HD 202 (having local application 220 - 1 ), or any device external to HD 202 and LSD 204 but still within system 200 such as external device 222 (having local application 220 - 2 ).
- external device 222 can take the form of a second LSD 222 coupled by way of interface 223 to HD 202 .
- such locations and devices can also include device 224 (having remote application 220 - 3 ) that is external to system 200 included in network 226 in communication with HD 202 by way network link 228 at network interface 230 . In this way, a communication channel using network link 228 can be established between external device 224 and HD 202 through which information 232 can pass.
- HD 202 can communicate with network 226 by way of network interface 230 .
- network interface 230 facilitates communication between HD 202 and network 226 by way of network link 228 .
- network link 228 For example if network 226 is an IP protocol type network, then network interface 230 can establish an IP protocol based network link 228 (such as a URL) between, for example, application 218 and any network device (ND) 224 included in network 226 .
- network interface 230 can be physically located anywhere deemed appropriate.
- network interface 230 can be incorporated into HD 202 .
- network interface 230 can also be located in any physical location not included in HD 202 (or system 200 ) but still be utilized by HD 202 to establish the appropriate network link 228 with network 226 .
- Network interface 230 is therefore not limited to being physically incorporated within or in close proximity to HD 202 .
- Master device agent 132 can take the form of host device agent 234 that provides in addition to the functions described above with regards to master device agent 124 , at least a bridging functionality between storage services provided by LSD 204 and any available external resources.
- host device agent 234 can be used to identify a LSD logical request by any means appropriate (such as polling or interrupts described below in more detail).
- host device agent 234 can be configured to route and/or maintain a communication path to/from a target application once established by same.
- host device agent 234 can be application neutral so as to serve any type of target application.
- LSD 204 can include controller 236 and mass storage array 238 having first storage array 240 and second storage array 242 .
- storage array 238 can be formed of an array of memory cells (such as FLASH).
- controller 236 includes file manager 243 that can manage first storage array 240 within host/LSD paradigm 106 (i.e., acting at the behest of HDFS 208 ).
- first storage area 240 can be a LBA based mass storage array.
- first storage array 240 is compatible with legacy installed base. Accordingly, the location of blocks of data stored in first storage area 240 can be specified using logical block addressing (LBA) where each block can be, for example, on the order of 512 or 1024 bytes each. In this way, first storage area 240 can be fully backward compatible with any contemplated legacy mass storage architectures (i.e. able to work in conjunction with legacy hosts) and more specifically LBA type systems.
- LSD 204 in particular, first storage area 240
- Controller 236 can also include LSD agent 244 that can act as a bridge (described below) between first storage area 240 and second storage area 242 using interface 246 .
- LSD agent 244 can also manage a network stack/interface 248 that provides a mechanism for internal LSD applications 250 to communicate with external devices and/or target applications using standard protocols (such as Internet Protocol, or IP) and any available network resources by way of LSD interface 252 .
- LSD 204 can translate any network communication (such as LSD logical request 130 ) into a standard format (such as physical bus-based format) so as to enable host device agent 234 to execute instructions (such as a message fetch) in a manner appropriate to an LBA based implementation of HD/LSD interface 206 .
- any fetched message for example, can be successfully conveyed over network link 228 created between host device agent 234 and remote application 220 - 3 (or a local communication path between local applications 220 - 1 or 220 - 2 and LSD 204 ).
- network stack/interface 248 can be considered to be part of LSD agent 244 .
- LSD agent 244 also can provide authentication and security services to LSD application 250 as well as manage any incoming service requests.
- Either the first storage area 240 or second storage area 242 can be partitioned into separate internal regions. These partitioned regions can each be acted upon so that they can interact with each other and/or circuits and/or software applications external to LSD 204 in any appropriate manner.
- Such external circuitry can include for example, HD 202 (that includes all components therein, such as host file system 208 ), LSD 222 , or any of a number of external devices included in network 226 such as ND 224 .
- Second storage area 242 can be partitioned to include region 254 .
- region 254 can be configured to be “invisible” to HDFS 208 and as such can be designated as covert storage area (CSA) 254 .
- CSA covert storage area
- any data content or changes to data content of CSA 254 cannot be detected by HDFS 208 (unless notified of such).
- HDFS 208 can be notified of any such data content or data content changes.
- any circuit or software application not in communication with HDFS 208 can prompt HD 202 to establish communication path 256 between itself and CSA 254 without being visible by HDFS 208 .
- LSD 204 can prompt HD 202 to establish communication path 256 between LSD 204 and any designated application 220 .
- information can be passed without further intervention by HD 202 (except for any intervention related to the passing of data, such as data packet routing) and also being invisible to HDFS 208 .
- CSA 254 can provide notification to HDFS 208 of any such changes.
- First storage area 240 can be partitioned to include region 260 .
- region 260 can be fully accessible to HDFS 208 or any other appropriate external circuit so long as the communication is mediated by HDFS 208 (using, for example, LBA based commands as described in some detail above in some embodiments). Therefore, region 260 can be designated as host storage area (HSA) 260 in keeping with the fact that host device file system 208 manages HSA 260 .
- HSA host storage area
- CSA 254 and HSA 260 can communicate with each other by way of interface 246 that is independent of HDFS 208 .
- interface 246 can bridge first storage area 240 and second storage area 242 .
- LSD agent 244 can include an internal file management system (e.g. LSD FS) that can read, for example, a file allocation table (FAT) managed by HDFS 208 .
- LSD agent 244 can also write to/from CSA 254 to HAS 260 using, for example, a placeholder file having dummy content.
- CSA 254 and HSA 260 can communicate with each other over communication path 262 unseen by HDFS 208 .
- all (or only portions) of CSA 254 and/or HSA 260 can be designated as protected portions 264 and 266 , respectively. By protected it is meant that HDFS 208 can not gain access to these protected regions unless authorized.
- Such authorization can be provided by a device external to computing system 200 such as, for example, an authorization server.
- LSD 204 can prompt HD 202 to execute requested process 124 for the benefit of LSD 204 . It should be noted that even in those cases where a host command (e.g. read/write) triggers the generation of LSD logical request 130 , LSD logical request 130 does not serve the host command.
- a host command e.g. read/write
- LSD 204 can prompt HD 202 to, for example, establish network link 228 and/or establish communication path 256 to either local applications 220 - 1 and/or 220 - 2 all without being visible to HDFS 208 .
- requested process 124 has been executed (i.e., the appropriate communication path established, for example) any further intervention by HD 202 is unnecessary (except for any routing or other housekeeping functions).
- HD 202 can be prompted by LSD 204 to execute LSD logical request 130 in a number of ways.
- FIG. 3A illustrates a polling scheme 300 in accordance with an embodiment of the invention.
- HD 202 can poll LSD 204 by sending polling signal (PS) 302 to LSD 204 that is intercepted by LSD agent 244 .
- PS polling signal
- LSD agent 244 can include logical request generator 304 that responds to PS 302 by generating LSD logical request 130 .
- Logical request generator 304 subsequently forwards LSD logical request back to host device agent 234 .
- the described polling process is not conditional upon the need or expectation of HD 202 for a specific response from LSD 204 .
- LSD 204 can at any time prompt HD 204 to execute requested process 124 by simply responding to polling signal 302 with LSD logical request 130 .
- LSD logical request 130 includes command information that can prompt HD 202 execute LSD requested process 124 .
- command information can include data such as a command code indicative of a particular operation to be completed by HD 202 (such as setting up communication channel 256 ).
- the command information can also include device information such as target device identification (ID), target device location (IP address, for example), etc.
- ID target device identification
- IP address IP address
- LSD 204 can provide command information indicating a particular operation but lacks a particular target device ID or target device location.
- a discovery server computer can be queried by LSD 204 by way of network link 238 , for example, in order to obtain the missing yet necessary information.
- LSD 204 can initiate a storage operation on a target storage device simply by responding to PS 302 at any time with LSD logical request 130 .
- LSD logical request 130 can include a command with instructions for HD 202 to establish a communication channel between LSD 204 and the target storage device. It should be noted that the target storage device can be in any location so long as HD 202 can establish an appropriate communication channel. For example, if the target storage device is ND 224 in network 226 , then HD 202 can respond to LSD logical request 130 by establishing network link 228 between network interface 230 and the ND 224 .
- LSD 204 can prompt HD 202 to execute requested process 124 by using LSD interrupt associator 402 to associate LSD logical request 130 received from LSD logical request generator 304 with LSD generated interrupt 404 .
- LSD interrupt associator 402 to associate LSD logical request 130 received from LSD logical request generator 304 with LSD generated interrupt 404 .
- LSD 204 raises interrupt 404 to the attention of HD 202 .
- HD 202 responds to logical request 130 associated with LSD interrupt 404 by executing requested process 124 .
- LSD 204 can also direct HD 202 to establish communication with other local storage device(s) such as second LSD 222 .
- computing system 200 can be a portable media player (in which case LSD 204 stores various digital media files such as audio files in the form of MP3) that can be coupled to a personal computer in order to, for example, synchronize media files between second LSD 222 and LSD 204 .
- LSD 204 can initiate an appropriate synchronization operation whereby data content between both LSD 222 and LSD 204 are compared and updated invisible to HDFS 208 .
- LSD 204 can perform any number of operations, generate a result and based upon that result, generate an associated logical request. The logical request can then be used by LSD 204 to prompt HD 204 to execute an appropriate LSD process. For example, LSD 204 can perform a detection of a set of LSD parameters operation.
- the set of LSD parameters detected can include parameter such as a data content back-up parameter, a data content parameter (such as a file size, a file type, a file name, and a file keyword), a logical storage parameter (such as a remaining capacity, and a LSD IP address, if appropriate), a physical storage parameter (such as a wear level, a number of bad blocks, a number of bit flips), a violation of rules parameter, and a host device IP address.
- a detection operation result is generated. It should be noted that in some cases, the result generated is a NULL result in that the detected parameters fall within a set of rules governing the operation of the LSD.
- the result generated can be associated with LSD logical request 130 as detection logical request 130 that can prompt HD 202 to establish a communication path to a target application.
- target applications can include local applications 220 - 1 , 220 - 2 or remote application 220 - 3 .
- the communication path is referred to as a local communication path.
- LSD 204 and target application 220 can logically interact in order to perform a requested detection process. It should be noted that once the communication path has been established, no further intervention by HD 202 is required except for maintaining the communication path and any other housekeeping duties.
- the requested detection process can include a content backup process, a content sharing process, an event notification process, a request for a remote instruction process, a request for usage/access right process, a registration to a remote server process.
- LSD 204 associates the detection logical request with the polling by the host device. In other embodiments, however, LSD 204 associates the detection logical request with a LSD interrupt and raises the LSD interrupt to the attention of HD 202 . In either case, HD 202 can be prompted to execute the appropriate requested detection process.
- the invention is essentially symmetric in that any circuit or software application external to LSD 204 and/or system 200 can target LSD 204 using HD 204 as a mechanism to establish a communication path between the requesting device and target device, LSD 204 .
- LSD 204 can respond to requests (such as provide current status information, current capacity, etc.) that originate from external circuits or external software applications.
- FIG. 4 illustrates a situation whereby remote application 220 - 3 compels first storage area 240 to perform any of a number of storage operations independent of HDFS 208 .
- external application 220 - 3 can write data to storage area 240 by writing data to a pre-established proxy file 450 (also referred to as a placeholder file) that is visible and therefore manageable by host device file system (HDFS) 208 .
- proxy file 450 also referred to as a placeholder file
- HDFS host device file system
- any data content included in placeholder file 450 can be considered “dummy” data in that placeholder file 450 is merely a part of the mechanism whereby remote application 220 - 3 can access/change data within proxy file without being “seen” by HDFS 208 (unless notified).
- external application 220 - 3 can write data 454 to placeholder file 450 without intervention of HDFS 208 by forwarding data 454 to be written to placeholder file 450 .
- data 454 can be sent directly to placeholder file 450 or use CSA 254 as a cache to buffer selected portions of data 454 .
- CSA 254 is used to cache data 454
- data 454 is passed to placeholder file 450 by way of communication path 256 without intervention by HD 202 (except for the establishing communication path 256 ).
- remote application 220 - 3 (or any external application 220 for that matter) can write data to placeholder file 450 or can stream data 454 from placeholder file 450 without intervention by HDFS 208 .
- LSD 204 can perform a detection operation that determines that the available storage capacity of first storage array 240 is less than a predetermined amount. Based upon that result, LSD logical request generator 340 can generate a LSD detection logical request 130 that prompts HD 202 to establish communication path 228 between LSD 204 and remote application 220 - 3 . Once communication path 228 has been established, HD 202 can have no intervention since HD 202 is now assuming a role commensurate to a modem, router, or other such device used to route data packets, for example. Once remote application 220 - 3 and LSD 204 are linked by way of communication path 228 , LSD 204 and remote application 220 - 3 can logically interact over communication path 228 .
- LSD 204 can forward results of the detection operation to remote application 220 - 3 .
- Remote application 220 - 3 can respond by pushing (writing) data 454 (in the form of a user notification, advertisement, etc.) to placeholder file 452 .
- data 454 is now visible to HDFS 208 and can be processed by HD 202 in any number of ways.
- data 454 can be used by HD 204 to display a notification that additional storage capacity is required and even suggest a product to purchase and where it can be purchased and for what price.
- FIG. 5A shows a more detailed view of network 500 in accordance with an embodiment of the invention.
- network 500 is one embodiment of network 226 shown in FIG. 3 .
- network 500 is shown to include server computer 502 coupled to computing system 200 by way of distributed communication channels.
- distributed communication channels can include wireless communications (WiFi, Bluetooth, etc.) as well as wired communications, etc.
- server computer 502 includes server component 504 that provides, in part, some clear and well defined interfaces, using, for example, standard Web technology e.g. HTTP/SOAP-based Web Services to developers and other users.
- server component 504 that can provide at least authorization and authentication services whenever a secure channel between a remote application and LSD 204 , for example, is required.
- Device registration module 506 and discovery services module 508 provide, respectively, a registration service and discovery service.
- registration service it is meant that any device included in, added to, or removed from network 226 that is registered to device registration module 506 has associated registration data updated consistent with a current status of the corresponding device.
- registration data can include device type, device location (IP address if the network is an IP protocol based network), etc.
- registration data associated with a device can be updated by registration module 506 in a number of different ways.
- One approach relies upon the registration module 506 being notified that a device status has changed (i.e., the device has been added, removed, or has moved location within network 226 , etc.).
- a device status has changed (i.e., the device has been added, removed, or has moved location within network 226 , etc.).
- registration module 506 can be notified of the status change by registration module 506 continually pinging all devices included in network 226 and requesting each device return current status information. Any status information that has changed with regards to a previous device status and that has been determined to represent a notifiable status change will invoke a notice event at device registration module 506 .
- registration module 506 can request that the device having the changed status forward current device status information to registration module 506 .
- the status information associated with the device can be updated at registration module 506 and forwarded to discovery server 508 .
- Another approach can have device registration module 506 taking on a more passive approach in that each device can forward its particular current status to device registration module 506 whenever a change in status has occurred. Again, in order to preserve computing resources and network bandwidth some aspects of the invention only provide for reporting only certain status changes and not all status changes.
- registration module 506 can forward the current status information to discovery services module 508 where it can be stored to provide subsequent discovery services to requesting devices and or software application.
- information can include any information related to any device included in network 324 in order to facilitate, for example, establishing a communication channel between the requesting device (including software applications, if any) and target device or target applications.
- LSD 222 can, in one aspect of the invention, notify device registration service 506 that it has joined network 226 .
- device registration service 506 can actively determine that LSD 222 has entered network 226 by, for example, pinging computing system 200 and determining that a notifiable change has occurred.
- LSD 222 can request HD 202 to establish a communication channel between LSD 222 and device registration service 506 that includes network link 228 from HD 202 to network 226 and communication channel 510 from network 226 to registration service 506 , using at least one of the mechanisms described above. It should be noted that if LSD 204 does not know the location of device registration service 506 , then either HD 202 will provide the location as a default location or network services will automatically direct status changes to a predefined location.
- registration information can include any relevant information related to the device.
- relevant information in the case of a data storage device
- Such information can also include more transitory information such as currently available data storage capacity, quality of stored data, location of device, etc. as well as data content parameters that can include a file size, a file type, a file name, and a file keyword.
- discovery service 508 can provide requested discovery information to any requesting device (or software application) about any target device (or target software application) having data stored therein.
- remote computing device 510 having remote host device 512 coupled with remote storage device 514 , can remotely invoke a storage operation on a target device such as LSD 204 using discovery service 508 by first establishing a communication channel between remote computing device 510 and LSD 204 .
- the communication channel can be established by remote computing device 510 sending a discovery request 516 to discovery service 508 requesting discovery information for target device LSD 204 .
- discovery information can include target device location information, target device current operating status information, target device current parametric information, etc.
- discovery service 508 can forward a discovery server response 518 that includes the appropriate target device discovery information back to the requesting device (i.e., remote computing device 510 ).
- remote computing device 510 can establish a communication channel between target device LSD 204 (using HD 104 as a conduit) that includes at least network link 228 . Once the communication channel has been established between target device LSD 204 and remote computing device 510 , then remote computing device 510 can remotely invoke any number and types of storage operations on target device LSD 204 . Such operations can include, for example, reading, writing, and/or erasing data.
- FIG. 6 shows a flowchart detailing a process 600 in accordance with an embodiment of the invention.
- Process 600 begins at 602 by determining if a host device is in communication with a local storage device.
- communication it is meant that the host device and local storage device have a capable communication channel established between them.
- capable communication it is meant that there is a physical connection established, a wireless connection established, or a logical connection established between the host device and the local storage device over which information can be passed.
- a determination is made if the local storage device has a pending LSD initiated event.
- LSD initiated event it is meant an event unrelated to and independent of any host device or host device file system process.
- the process 600 ends, otherwise a 606 a determination is made whether or not the host device in continuously polling the local storage device. If the host device is not polling the local storage device, then the local storage device generates a LSD logical request at 608 that includes information related to the pending LSD initiated event and at 610 the local storage device throws up an interrupt flag associated with the LSD logical request. At 612 , the host device responds to the interrupt flag.
- the local storage device responds to the host device polling with an LSD polling response that includes information related to the pending LSD initiated event.
- the host device responds to the LSD polling response.
- FIG. 7 illustrates a process 700 in accordance with an embodiment of the invention.
- Process 700 begins at 702 by determining if a remote device wants to invoke an operation on a local target device. If affirmative, then at 704 a determination is made if the remote device sends a query to the discovery server in order to obtain target device information. If the remote device has determined that it does not need to query the discovery server, than at 706 the remote device contacts the local device. On the other hand, if the remote device has determined that discovery information for the target device is needed, than at 708 a determination is made whether or not the discovery server has the target device discovery information.
- the remote device sends a discovery information request to the discovery server and at 716 the discovery server provides the requested target device discovery information. At 706 , the remote device contacts the target device and at in any case, at 718 the target device responds to the remote device.
- FIG. 8 provides a context of the invention where a media network 800 as a specific configuration of network 226 includes a number of media devices such as media players.
- computing system 200 can be a media player 100 arranged to store a number of digital media items (such as video, audio possibly as MP3 files, etc.).
- Network 800 can include distributed communications 802 configured as either or both a wired network 804 and a wireless network 806 .
- wired data network 802 pertains to some portion of the World Wide Web.
- Personal computer 806 can couple to wired network 802 (which in this case is connected to computing system 100 by way of a USB cable at second interface).
- Wireless data network 804 can also couple to wired data network 802 .
- Wireless data network 804 can include one or more wireless data networks, such as cellular networks, WiFi networks, WiMAX networks, etc.
- Media network 800 includes central media server 808 that stores or has access to numerous media items.
- network 800 supports one or more additional computing systems 810 configured as network devices that can take the form of portable media devices such as portable media player 200 , 810 , 812 and 814 some of which can be configured as having only legacy mass storage while others can be configured as computing system 200 shown in FIG. 2 .
- Any of the portable media devices 200 , 810 , 812 and 814 can communicate with personal computer 806 over wired link 816 or wireless link 818 .
- wired link 816 can correspond to a cable (e.g., USB cable) that, if available, can interconnect portable media device 810 to personal computer 806 .
- Wireless link 818 can be provided by a wireless capability, such as Bluetooth, infrared, etc.
- the portable media device 810 would be capable of communicating with personal computer 806 using either wired link 816 , wireless link 816 , or both.
- Portable media device 814 can couple to the wireless data network 804 over a wireless link 820 .
- portable media device 812 can couple to wireless data network 804 over a wireless link 822 .
- portable media devices 814 and 812 can access central media server 808 via wireless data network 804 .
- portable media devices 810 , 812 and 814 can wirelessly access each other, thereby exchange media item data between portable media devices.
- Computing system 200 can take the form of a media device that can pertain to portable media players such as MP3 players as well as wireless device such as mobile phones that can include LSD 204 and HD 202 .
- These mobile devices can include a media management application on the host computer that operates on the mobile device.
- mobile devices Given the portability of mobile devices, mobile devices are smaller and have less resources (e.g., storage capacity). Consequently, a media management application designed for use on a mobile device can offer less features and capabilities than would a counterpart media management application operating on a larger, more powerful computing device, e.g., a personal computer.
- the mobile devices Given that the mobile devices have wireless access to central media server 808 , the mobile devices can interact with media server 808 to request and/or receive media item data (or other data).
- a media management application operating on the mobile devices can communicate with the media server 808 to perform various tasks, including: navigating available media content at the server (such as navigation of a media store), receiving a periodic delivery of media content to media devices (such as a daily pushing of media item data from a server to a media device), etc.
- FIG. 9 shows a representative system 900 illustrating additional components typically found in host device 204 .
- System 900 includes central processing unit (CPU) 910 , random access memory (RAM) 920 , read only memory (ROM) 930 , and primary storage devices 940 and 950 .
- CPU central processing unit
- RAM random access memory
- ROM read only memory
- primary storage devices 940 and 950 are also coupled to one or more input/output devices 960 familiar to those of skill in the computer hardware and software arts.
- mobile devices e.g., portable media devices
- peer-to-peer interaction can be referred to as peer-to-peer interaction.
- one mobile device can communicate (e.g., unicast) directly with another mobile device.
- one mobile device can communicate (e.g., broadcast, any cast or multicast) to a plurality of other mobile devices.
- one mobile device can communicate with one or more other electronic devices (whether mobile or stationary) in the immediate vicinity. Data sharing can be performed when such communication is available.
- Data transfer could be between a mobile device and a computing device, such as a home computer or another mobile device.
- the mobile device and the computing device would be associated with a particular user.
- data transfer can be performed between the mobile device and the home computer.
- Data transfer could also be between two or more mobile devices, or between two or more non-mobile devices.
- the data transfer can be automatic without any user action or can alternatively require manual approval by a user.
- the network devices can be associated with one another via an identification number or other suitable mechanism.
- a mobile device or non-mobile device capable of receiving, transmitting and/or storing data may be referred to as a “data device.”
- the manner by which the data arrives at the data device can depend upon implementation.
- the data can be directly transferred to the data device, or the data can be indirectly transferred to the data device.
- the data transfer can be between one data device to another data device.
- one data device can cause another data device to transfer desired data to a recipient data device.
- the shared data can be transferred to a recipient device by file transfer or streaming.
- the data transferred can be received by one or more data devices.
- data devices include a media player, PDA, a speaker unit, a wireless transmitter/receiver unit, etc.
- Users of data devices can also create and distribute content through data sharing.
- the streaming can be limited so as to restrict the number of data devices simultaneously receiving the data.
- the users of the data devices are subscribers to the streaming content (i.e., have a subscription)
- the streaming can be unlimited as to subscribers.
- Storing some portion of the media item content associated with the media item metadata may also be done to facilitate the streaming of media item content. For example, a user could begin playing such a previously stored portion of the media item content before streaming of the remaining content even begins.
- Data can be shared after being purchased.
- a recipient could purchase data from a remote server.
- the remote server would then cause the purchased data to be delivered to the recipient's data device.
- the purchase can be performed in real-time or can be deferred until a later point in time. Thereafter, the purchased data can be shared from the recipient's data device to another data device.
- the user's mobile device can transfer data to the user's work computer or to a network server for the office.
- the data transfer can be automatic without any user action or can alternatively require manual approval by a user.
- the user of the mobile device can also communicate with mobile devices of coworkers or other users of the network to exchange data.
- the data transfer can be wireless.
- the wireless data transfer can be facilitated by a wireless network.
- One mobile device could wirelessly transmit data in a unicast fashion from one mobile device to another mobile device or stationary computing device.
- one mobile device could wirelessly transmit data in a multicast or broadcast fashion to a plurality of other mobile devices.
- any home-server computer can reside on any of a number of other data storage devices in a network to which computing device 200 belongs.
- One advantage of the invention is legacy devices can be added or removed without consideration of modifying system hardware.
- Another advantage of the invention is that it can be used with any host computer without modification therefore reducing the cost and increasing the applicability of the invention.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Storage Device Security (AREA)
Abstract
Various methods, devices and systems are described for providing distributed storage services. A data storage device is capable of initiating a communication session with an external entity such as a local host computer (and vice versa) coupled directly to the data storage device, a remote server computer, or directly with remote data storage devices with or without intervention by a local host computer.
Description
- The present application is a continuation of U.S. patent application Ser. No. 13/355,146, (still pending) filed Jan. 20, 2012, which is divisional application of U.S. patent application Ser. No. 12/019,573 (now U.S. Pat. No. 8,452,927), which claims priority under 35 U.S.C. 119(e) to (i) U.S. Provisional Patent Application No. 61/018,644 filed on Jan. 2, 2008 (Attorney Docket No. SDK1P048P) entitled “DISTRIBUTED STORAGE SERVICE SYSTEMS AND ARCHITECTURE” by Nochimowski et al., and (ii) U.S. Provisional Patent Application No. 61/018,979 filed on Jan. 4, 2008 (Attorney Docket No. SDK1P048P2) entitled “DISTRIBUTED STORAGE SERVICE SYSTEMS AND ARCHITECTURE” by Nochimowski et al., the entirety of each of which are incorporated by reference.
- This application is also related to co-pending U.S. patent application Ser. No. 11/967,938 entitled LOCAL PROXY SYSTEM AND METHOD by Mosek et al., filed Dec. 31, 2007, which is incorporated by reference for all purposes.
- The present invention relates generally to digital devices. More particularly, the present invention relates to providing cross platform mass storage services for digital devices.
- Mass storage devices (such as FLASH memory that includes SD and MMC type mass storage devices) have increased greatly in both storage capacity and in the capabilities (i.e., processing resources) of associated mass storage device controllers. This increase in available storage capacity has had a synergistic effect on the general availability of devices whose capabilities can depend greatly on available memory. Such devices include portable digital devices such as portable media players, interactive personal communication devices (cell phones, PDAs, etc.) and the like. In this way, a digital consumer's exposure to digital products that rely upon the storage capability of mass storage devices such as FLASH memory has greatly increased. Exposure that typically spans across multiple devices—connected or unconnected—or access modes—wired vs. wireless, fixed vs. mobile etc.—each having specific storage requirements. Unfortunately, however, as a result of this vast increase in available devices, a digital consumer's storage management can be fragmented with personal content spread across various locations, various devices, and managed in a ‘silo mode’ resulting in content not synchronized, backed-up etc. For example, a consumer can possess a cell phone, a PDA, a multimedia player, a tablet PC, each of which can have different manufacturers, used different operating systems, different storage protocols, etc.
- A number of attempts at solving the problem of fragmented management of the digital consumer's digital data have been proposed. It should be noted, however, that a large proportion of legacy digital devices (particularly those that include FLASH type mass storage) are based upon a master/slave paradigm in that a host device (as master) is coupled by way of a legacy interface to a legacy slave device that typically takes the form of a logical block addressing (LBA) mass storage device. In particular, the master/slave paradigm dictates that the legacy mass storage device and its contents be fully managed by the host device (including a host device file system). In this way, the host device and legacy storage device are locked into a master/slave relationship imposed by the physical link connecting them in that it is the host device (and in some cases, but not all, the host file system) that initiates all transactions between the host device and the legacy mass storage device. Therefore, the master/slave paradigm between host device and legacy mass storage device whereby the host device manages the legacy mass storage device using various LBA commands, poses further constraints on any possible solution.
- A proposed solution includes integrating a client agent on the host device. Typically, the client agent is application specific. For example, the client agent can enable back up of the portable memory device, or the client agent can enable “content push” from a server computer to the portable memory device. The client agent can also provide a translation layer into LBA commands as well as provide a platform for processing by the host computer (thereby off-loading the most processor intensive operations from the portable memory device to the host computer). However, using a client agent on the host computer presents its own set of problems. One such problem is related to the heterogeneity of host operating systems, particularly in mobile platforms. This heterogeneity is made even worse in the case of a “closed” operating systems (such as Nucleus) as opposed to that of “open” operating systems such as Windows, Symbian, and the like. Furthermore, only those portable devices compatible with the agent integrated on the host computer can be used, again, limiting the potential market for these portable devices.
- Therefore, a method, system, and apparatus that overcomes the structural limitations of legacy mass storage devices while still offering backward compatibility thereby providing richer cross platform storage services is desirable.
- According to different embodiments of the present invention, various methods, devices and systems are described for providing distributed storage services. One embodiment describes a computing system that includes at least a host device (HD), a local storage device (LSD) managed by the HD. The LSD does not utilize any interface to a device external to the HD other than that interface provided by the HD. The LSD prompts the HD to execute a requested process with a LSD logical request. The LSD logical request is not created to serve a HD initiated process. The computing system also includes a HD/LSD interface providing a communication path between the HD and the LSD.
- In another embodiment, a computing system is described. The computing system includes at least a host device having at least a host device file system, and a local storage device (LSD) coupled to the host device by way of a HD/LSD interface. The LSD does not utilize any interface to a device external to the HD other than that interface provided by the HD. The LSD has at least one storage area managed by the HD. The HD manages the at least one storage area by sending a block command to the at least one storage area by way of the HD/LSD interface. The LSD prompts the HD to execute a requested process with a LSD logical request. The LSD logical request is not created to serve a HD initiated process. The LSD generates the LSD logical request, associates the LSD logical request with a LSD interrupt, and raises the LSD interrupt to the attention of the host device thereby prompting the host device to execute the requested process.
- In yet another embodiment, a computing system is disclosed that includes a host device having at least a host device file system (HDFS), and a local storage device (LSD) coupled to the host device by way of a HD/LSD interface. The LSD does not utilize any interface to a device external to the HD other than that interface provided by the HD. The LSD has at least one storage area managed at least by the HD and the HD manages the at least one storage area by sending a block command to the at least one storage area by way of the HD/LSD interface. The LSD responds to a polling of the LSD by the host device with a LSD logical request. The LSD logical request is not created to serve a HD initiated process. The LSD prompts the HD to execute a requested process with the LSD logical request. The polling by the host device is independent of any HDFS initiated process.
- In still another embodiment, a method performed by a computing system is described. The computing system includes a local storage device (LSD) having at least one storage area, where the LSD is managed by a host device (HD) by passing at least a block command to the LSD by way of a HD/LSD interface. The LSD does not utilize any interface to a device external to the HD other than that interface provided by the HD. The method can be carried out by performing at least the following operation: prompting the HD by the LSD to execute a requested process with a LSD logical request. The LSD logical request is not created to serve a HD initiated process.
- In another embodiment, a computing system is described that includes at least a host device (HD) having at least a host device file system and a LSD driver, and a local storage device (LSD) having at least one storage area managed by the host device file system. The HDFS manages the at least one storage area by generating a block command and passing the block command to the at least one storage area by way of the HD/LSD interface. The system also includes an application in communication with the host device. The application does not utilize any communication paths between the application and either the host device file system or the LSD driver. The application compels the LSD to perform at least one storage operation on the at least one storage area without intervention by the host device file system.
- A method performed by a computing system is described. The computing system includes at least a host device (HD) having at least a host device file system and a LSD driver, a local storage device (LSD) having at least one storage area managed at least by the host device file system, and an application in communication with the host device wherein the application does not utilize any communication paths between the application and either the LSD driver or the host device file system. The method includes at least the following operation: compelling the LSD to perform at least one storage operation on the at least one storage area by the application without intervention by the host device file system.
- Computer program product executed by a processor included in a computing system having a local storage device (LSD) managed by a host device (HD) wherein the HD manages the LSD by passing at least a block command to the LSD by way of a HD/LSD interface, wherein the LSD does not utilize any interface to a device external to the HD other than that interface provided by the HD is disclosed. The computer program product includes computer code for prompting the HD by the LSD to execute a requested process with a LSD logical request wherein the LSD logical request is not created to serve a HD initiated process and computer readable medium for storing the computer code.
- Computer program product executed by a processor in a computing system having at least a host device (HD) having at least a host device file system and a LSD driver, a local storage device (LSD) having at least one storage area managed by the host device file system, and an application in communication with the host device wherein the application does not utilize any communication paths between the application and either the LSD driver and the host device file system is disclosed. The computer program product includes computer code for compelling the LSD to perform at least one storage operation on the at least one storage area by the application without intervention by the host device file system and computer readable medium for storing the computer code.
-
FIG. 1 shows a symbolic representation of a system in accordance with an embodiment of the invention. -
FIG. 2 illustrates a host device/local storage device system in accordance with an embodiment of the invention. -
FIGS. 3A and 3B shows a computing system in accordance with an embodiment of the invention. -
FIG. 4 shows a computing system in accordance with an embodiment of the invention. -
FIGS. 5A-5B show a more detailed view of network shown inFIG. 3 . -
FIG. 6 shows a flowchart detailing a process in accordance with an embodiment of the invention. -
FIG. 7 shows a flowchart detailing a process in accordance with an embodiment of the invention. -
FIG. 8 shows a representative media network in accordance with an embodiment of the invention. -
FIG. 9 shows a representative system illustrating additional components typically found in host device. - Reference will now be made in detail to a particular embodiment of the invention an example of which is illustrated in the accompanying drawings. While the invention will be described in conjunction with the particular embodiment, it will be understood that it is not intended to limit the invention to the described embodiment. To the contrary, it is intended to cover alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims.
- With the increase of the capabilities of storage device controllers, the execution of software applications from within the storage device using processing resources made available by the storage device controllers becomes possible. This enhanced operability of the storage device controllers leads to a paradigm of new (and heretofore impractical) interaction modes such as user-oriented storage services. Such user oriented storage services can be used for improving a user's digital content consumption experience that typically spans across multiple devices—connected or unconnected—or access modes—wired vs. wireless, fixed vs. mobile etc.—each having specific storage requirements.
- In order to provide support “user-centric” (as opposed to traditional “device-centric”) storage management approach, the invention goes beyond the strict limitations of the host managed, LBA-based mass storage paradigm and provides a storage services paradigm that while fully backward compatible with legacy mass storage devices enhances mass storage with other kinds of interactions. Other kinds of interactions that, for example, allow for storage resources and service building blocks to be potentially distributed across various physical locations (i.e., a data storage device, in a host computer, or across a network).
- With this in mind, the storage services paradigm provides that a local data storage device is now capable of 1) interactions with other data storage devices present in the same host computer, or with applications running on a remote server computer, and 2) the interactions can be initiated by the data storage device itself, by a host application or by a remote server.
- The invention can further pertain to an electronic system that includes a memory device discussed above. Memory devices (i.e., memory cards) are commonly used to store digital data for use with various electronics products. The memory device is often removable from the electronic system so the stored digital data is portable. The memory devices according to the invention can have a relatively small form factor and be used to store digital data for electronics products that acquire data, such as cameras, hand-held or notebook computers, network cards, network appliances, set-top boxes, hand-held or other small media (e.g., audio) players/recorders (e.g., MP3 devices), and medical monitors.
- Embodiments of the invention are discussed below with reference to
FIGS. 1-9 . However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the invention extends beyond these limited embodiments. It should be noted that it is contemplated that the invention can be used for any type of local data storage devices that can include non-volatile memory such as Multi Media Card (MMC) and Secure Digital Card (SD). -
FIG. 1 shows a symbolic representation of master device/slave system 100 in accordance with an embodiment of the invention. It should be noted that master/slave is a model for a communication protocol where one device or process has unidirectional control over one or more other devices. Once a master/slave relationship between devices or processes is established, the direction of control is always from the master to the slaves. In some systems a master is elected from a group of eligible devices with the other devices acting in the role of slaves. Accordingly, master/slave system 100 (hereinafter referred to simply as system 100) includesmaster device 102 andslave device 104 that relate to each other, in part, by way of conventional master/slave paradigm 106. It should also be noted thatslave device 104 has no interface to any device external tomaster device 102 other than that provided bymaster device 102. -
Master device 102 can operate a number of master device processes 108. By master device process it is meant a process executed solely for the benefit of the master device. Such master device processes can include any number and type of processes such as, for example, a fetch instruction command useful in providingmaster device 102 with an executable instruction. Master device processes 108 can include master device processes 110, 112, and 114 each of which can be executed by processingunit 116. Any of theprocesses Process 110, for example, can request service fromslave device service 118 by generatingmaster device request 120.Slave device service 118 can respond tomaster device request 120 with slave service response 122. For example,master device request 120 can take the form of a READ command and requested slave service response 122 can take the form of DATA. However, within the confines of master/slave paradigm 106,slave device 104 can not prompt nor in any mannercause master device 102 to execute any process outside of master device processes 108. In other words, within the context of conventional master/slave paradigm 106,master device 102 can only execute at least one of the master device processes 108. - However, the invention circumvents conventional master/
slave paradigm 106 by allowingslave device 104 to promptprocessor 116 to execute requestedprocess 124 for the benefit ofslave device 102. In this way, requestedprocess 124 can be executed byprocessor 116 and yet can be totally independent of and unrelated to any of the master device processes 108.Slave device 104 can includeslave device agent 126 that can associateslave device process 128 with slave devicelogical request 130.Master device 102 can includemaster device agent 132 in communication withprocessor 116 andslave device 104 by way of slave devicelogical request 130. In this way,master device agent 132 can use slave devicelogical request 130 to promptprocessor 116 to execute requestedslave device process 124. In this way, a logical request generated by a slave device can be converted into a master device provided physical response unrelated to and independent of any master device initiated process. - The invention will now be described in terms of more specific embodiments all of which are in keeping with the spirit and scope of the invention. It should be noted that any functional blocks or functional arrangements described herein can be implemented as either a physical entity or as a logical entity, or as a combination of both.
-
FIG. 2 shows acomputing system 200 in accordance with an embodiment of the invention.System 200 can includeslave device 104 that can take the form of local storage device (LSD) 204.LSD 204 can take the form of removable memory devices such as a memory card having a relatively small form factor and can be used to store digital data for electronics products such as cameras, hand-held or notebook computers, network cards, network appliances, set-top boxes, hand-held or other small audio players/recorders (e.g., MP3 devices), and medical monitors. Examples of a memory card include PC Card (formerly PCMCIA device), Flash card (e.g., Compact Flash Type I and II), Secure Digital (SD) card, Multimedia card (MMC), ATA card (e.g., Compact Flash card), memory stick, SmartMedia card. In addition,LSD 204 can take the form of non-removable memory devices such as SD compatible iNAND™ embedded Flash drive manufactured by SanDisk Corporation of Milpitas Calif. -
LSD 204 can communicate withmaster device 102 in the form of host device (HD) 202 by way of HD/LSD interface 206. It should be noted that HD/LSD 206 can be configured as a mechanical entity (such as a socket or interconnecting bus) into whichHD 202 andLSD 204 can mechanically connect. In some embodiments, HD/LSD 206 can take the form of a wireless interface. SinceHD 202 is a master device,HD 202 includes a processor. However, for the sake of clarity, the processor included inHD 202 is neither shown nor mentioned further in this discussion but is, nonetheless, presumed to be present.LSD 204 can be physically connected exclusively toHD 202 and therefore cannot access or otherwise communicate with circuits and/or applications external tocomputing system 200 without intervention byHD 202. Typically,LSD 204 does not utilize any interface to a device external toHD 202 other than that interface provided by theHD 202. -
HD 202 includes host device file system (HDFS) 208 in communication withLSD driver 210. In the described embodiment,HDFS 208 can issueLSD management command 212 toLSD driver 210.LSD driver 210 can, in turn, pass LSD management command 212 (appropriately formatted) toLSD 204 by way of HD/LSD interface 206. For example,LSD management command 212 can take the form of a block command in those cases whereLSD 204 is configured to include a data storage array having logical block address (LBA) architecture.HD 202 can also include (internal)software application 214. By internal application it is meant thatsoftware application 214 can utilizeHDFS 208 andLSD driver 210 to communicate withLSD 204. Such software applications can include host device operating system (HDOS) 216 andapplication 218 each of which typically resides in host device main memory (that can take the form of a hard disk drive, or HDD, as well as non-volatile memory such as FLASH memory). - In the described embodiment,
software application 214 can utilizeHDFS 208 andLSD driver 210 to communicate withLSD 204 and is therefore “visible” toHDFS 208. In contrast toapplication 214, however, external application 220 (referred to hereinafter as target application) does not utilize any communication path between target application 220 and eitherHDFS 208 andLSD driver 210 to communicate withLSD 204 and is therefore not “visible” toHDFS 208. In the described embodiment, target application 220 can reside in any number of locations and devices, either locally or remotely. Such locations and devices can include, for example, HD 202 (having local application 220-1), or any device external toHD 202 andLSD 204 but still withinsystem 200 such as external device 222 (having local application 220-2). In the described embodiment,external device 222 can take the form of asecond LSD 222 coupled by way ofinterface 223 toHD 202. Moreover, such locations and devices can also include device 224 (having remote application 220-3) that is external tosystem 200 included innetwork 226 in communication withHD 202 by way network link 228 atnetwork interface 230. In this way, a communication channel usingnetwork link 228 can be established betweenexternal device 224 andHD 202 through whichinformation 232 can pass. -
HD 202 can communicate withnetwork 226 by way ofnetwork interface 230. In the describedembodiment network interface 230 facilitates communication betweenHD 202 andnetwork 226 by way ofnetwork link 228. For example ifnetwork 226 is an IP protocol type network, thennetwork interface 230 can establish an IP protocol based network link 228 (such as a URL) between, for example,application 218 and any network device (ND) 224 included innetwork 226. It should be noted thatnetwork interface 230 can be physically located anywhere deemed appropriate. For example,network interface 230 can be incorporated intoHD 202. However,network interface 230 can also be located in any physical location not included in HD 202 (or system 200) but still be utilized byHD 202 to establish theappropriate network link 228 withnetwork 226.Network interface 230 is therefore not limited to being physically incorporated within or in close proximity toHD 202. -
Master device agent 132 can take the form ofhost device agent 234 that provides in addition to the functions described above with regards tomaster device agent 124, at least a bridging functionality between storage services provided byLSD 204 and any available external resources. In the described implementation,host device agent 234 can be used to identify a LSD logical request by any means appropriate (such as polling or interrupts described below in more detail). Moreover,host device agent 234 can be configured to route and/or maintain a communication path to/from a target application once established by same. Furthermore,host device agent 234 can be application neutral so as to serve any type of target application. -
LSD 204 can includecontroller 236 andmass storage array 238 havingfirst storage array 240 andsecond storage array 242. It should be noted thatstorage array 238 can be formed of an array of memory cells (such as FLASH). In this particular case, even thoughmass storage array 238 can be presumed to be an array of FLASH memory cells, the invention is not limited to only FLASH type memory cells since it is contemplated that the invention can be used with any appropriate type of memory cell.Controller 236 includesfile manager 243 that can managefirst storage array 240 within host/LSD paradigm 106 (i.e., acting at the behest of HDFS 208). In a particularly useful arrangement,first storage area 240 can be a LBA based mass storage array. In this way,first storage array 240 is compatible with legacy installed base. Accordingly, the location of blocks of data stored infirst storage area 240 can be specified using logical block addressing (LBA) where each block can be, for example, on the order of 512 or 1024 bytes each. In this way,first storage area 240 can be fully backward compatible with any contemplated legacy mass storage architectures (i.e. able to work in conjunction with legacy hosts) and more specifically LBA type systems. In particular, LSD 204 (in particular, first storage area 240) can operate under standard LBA architecture using legacy interfaces, busses, and all associated protocols providing for full compatibility with installed base of legacy products. -
Controller 236 can also includeLSD agent 244 that can act as a bridge (described below) betweenfirst storage area 240 andsecond storage area 242 usinginterface 246.LSD agent 244 can also manage a network stack/interface 248 that provides a mechanism forinternal LSD applications 250 to communicate with external devices and/or target applications using standard protocols (such as Internet Protocol, or IP) and any available network resources by way ofLSD interface 252. In particular,LSD 204 can translate any network communication (such as LSD logical request 130) into a standard format (such as physical bus-based format) so as to enablehost device agent 234 to execute instructions (such as a message fetch) in a manner appropriate to an LBA based implementation of HD/LSD interface 206. In this way, any fetched message, for example, can be successfully conveyed overnetwork link 228 created betweenhost device agent 234 and remote application 220-3 (or a local communication path between local applications 220-1 or 220-2 and LSD 204). In this regard, network stack/interface 248 can be considered to be part ofLSD agent 244.LSD agent 244 also can provide authentication and security services toLSD application 250 as well as manage any incoming service requests. - Either the
first storage area 240 or second storage area 242 (or both) can be partitioned into separate internal regions. These partitioned regions can each be acted upon so that they can interact with each other and/or circuits and/or software applications external toLSD 204 in any appropriate manner. Such external circuitry can include for example, HD 202 (that includes all components therein, such as host file system 208),LSD 222, or any of a number of external devices included innetwork 226 such asND 224. -
Second storage area 242 can be partitioned to includeregion 254. In the described embodiment,region 254 can be configured to be “invisible” toHDFS 208 and as such can be designated as covert storage area (CSA) 254. In this way, any data content or changes to data content ofCSA 254 cannot be detected by HDFS 208 (unless notified of such). However,HDFS 208 can be notified of any such data content or data content changes. For example, as described in more detail below, any circuit or software application not in communication with HDFS 208 (such as remote application 220-3 residing inND 224, local application 220-1 inHD 202, and local application 220-2 in LSD 222), can promptHD 202 to establishcommunication path 256 between itself andCSA 254 without being visible byHDFS 208. Conversely,LSD 204 can promptHD 202 to establishcommunication path 256 betweenLSD 204 and any designated application 220. Once established, however, information (such asinformation 232,information 258, and information 260) can be passed without further intervention by HD 202 (except for any intervention related to the passing of data, such as data packet routing) and also being invisible toHDFS 208. In some cases, however,CSA 254 can provide notification toHDFS 208 of any such changes. -
First storage area 240 can be partitioned to includeregion 260. In the described embodiment,region 260 can be fully accessible toHDFS 208 or any other appropriate external circuit so long as the communication is mediated by HDFS 208 (using, for example, LBA based commands as described in some detail above in some embodiments). Therefore,region 260 can be designated as host storage area (HSA) 260 in keeping with the fact that hostdevice file system 208 managesHSA 260. In one aspect of the invention,CSA 254 andHSA 260 can communicate with each other by way ofinterface 246 that is independent ofHDFS 208. In the described embodiment, as part ofLSD agent 244,interface 246 can bridgefirst storage area 240 andsecond storage area 242.LSD agent 244 can include an internal file management system (e.g. LSD FS) that can read, for example, a file allocation table (FAT) managed byHDFS 208.LSD agent 244 can also write to/fromCSA 254 to HAS 260 using, for example, a placeholder file having dummy content. In this way,CSA 254 andHSA 260 can communicate with each other overcommunication path 262 unseen byHDFS 208. In some cases, all (or only portions) ofCSA 254 and/orHSA 260 can be designated as protectedportions HDFS 208 can not gain access to these protected regions unless authorized. Such authorization can be provided by a device external tocomputing system 200 such as, for example, an authorization server. As described above,LSD 204 can promptHD 202 to execute requestedprocess 124 for the benefit ofLSD 204. It should be noted that even in those cases where a host command (e.g. read/write) triggers the generation of LSDlogical request 130, LSDlogical request 130 does not serve the host command. - In this way, requested
process 124 can be totally independent of and unrelated to any of the host device processes 108. In particular,LSD 204 can promptHD 202 to, for example, establishnetwork link 228 and/or establishcommunication path 256 to either local applications 220-1 and/or 220-2 all without being visible toHDFS 208. However, once requestedprocess 124 has been executed (i.e., the appropriate communication path established, for example) any further intervention byHD 202 is unnecessary (except for any routing or other housekeeping functions).HD 202 can be prompted byLSD 204 to execute LSDlogical request 130 in a number of ways. For example,FIG. 3A illustrates a polling scheme 300 in accordance with an embodiment of the invention.HD 202 can pollLSD 204 by sending polling signal (PS) 302 toLSD 204 that is intercepted byLSD agent 244. - In the described embodiment,
LSD agent 244 can includelogical request generator 304 that responds toPS 302 by generating LSDlogical request 130.Logical request generator 304 subsequently forwards LSD logical request back tohost device agent 234. It should be noted that the described polling process is not conditional upon the need or expectation ofHD 202 for a specific response fromLSD 204. In this way,LSD 204 can at any timeprompt HD 204 to execute requestedprocess 124 by simply responding to polling signal 302 with LSDlogical request 130. In the described embodiment, LSDlogical request 130 includes command information that can promptHD 202 execute LSD requestedprocess 124. It should be noted that command information can include data such as a command code indicative of a particular operation to be completed by HD 202 (such as setting up communication channel 256). - The command information can also include device information such as target device identification (ID), target device location (IP address, for example), etc. In some cases, however, neither
LSD 204 norHD 202 has sufficient information at hand to complete a required task. For example,LSD 204 can provide command information indicating a particular operation but lacks a particular target device ID or target device location. In these situations, it may be possible to utilize a discovery server computer that can be queried byLSD 204 by way ofnetwork link 238, for example, in order to obtain the missing yet necessary information. For example,LSD 204 can initiate a storage operation on a target storage device simply by responding toPS 302 at any time with LSDlogical request 130. LSDlogical request 130 can include a command with instructions forHD 202 to establish a communication channel betweenLSD 204 and the target storage device. It should be noted that the target storage device can be in any location so long asHD 202 can establish an appropriate communication channel. For example, if the target storage device isND 224 innetwork 226, thenHD 202 can respond to LSDlogical request 130 by establishingnetwork link 228 betweennetwork interface 230 and theND 224. - Another mechanism by which
LSD 204 can promptHD 202 to execute requestedprocess 124 is described in terms of a LSD generated interrupt illustrated inFIG. 3B .LSD 204 can promptHD 202 to execute requestedprocess 124 by using LSD interruptassociator 402 to associate LSDlogical request 130 received from LSDlogical request generator 304 with LSD generated interrupt 404. Once LSDlogical request 130 has been associated with LSD interrupt 404,LSD 204 raises interrupt 404 to the attention ofHD 202.HD 202 responds tological request 130 associated with LSD interrupt 404 by executing requestedprocess 124. -
LSD 204 can also directHD 202 to establish communication with other local storage device(s) such assecond LSD 222. For example,computing system 200 can be a portable media player (in which case LSD 204 stores various digital media files such as audio files in the form of MP3) that can be coupled to a personal computer in order to, for example, synchronize media files betweensecond LSD 222 andLSD 204. In this example,LSD 204 can initiate an appropriate synchronization operation whereby data content between bothLSD 222 andLSD 204 are compared and updated invisible toHDFS 208. - In another example,
LSD 204 can perform any number of operations, generate a result and based upon that result, generate an associated logical request. The logical request can then be used byLSD 204 to promptHD 204 to execute an appropriate LSD process. For example,LSD 204 can perform a detection of a set of LSD parameters operation. In the described embodiment, the set of LSD parameters detected can include parameter such as a data content back-up parameter, a data content parameter (such as a file size, a file type, a file name, and a file keyword), a logical storage parameter (such as a remaining capacity, and a LSD IP address, if appropriate), a physical storage parameter (such as a wear level, a number of bad blocks, a number of bit flips), a violation of rules parameter, and a host device IP address. OnceLSD 204 has completed the detection operation, a detection operation result is generated. It should be noted that in some cases, the result generated is a NULL result in that the detected parameters fall within a set of rules governing the operation of the LSD. However, in other cases, the result generated can be associated with LSDlogical request 130 as detectionlogical request 130 that can promptHD 202 to establish a communication path to a target application. Such target applications can include local applications 220-1, 220-2 or remote application 220-3. It should be noted that in the case of local applications 220-1 and 220-2, the communication path is referred to as a local communication path. Once such a communication path has been established,LSD 204 and target application 220 can logically interact in order to perform a requested detection process. It should be noted that once the communication path has been established, no further intervention byHD 202 is required except for maintaining the communication path and any other housekeeping duties. The requested detection process can include a content backup process, a content sharing process, an event notification process, a request for a remote instruction process, a request for usage/access right process, a registration to a remote server process. - In one embodiment,
LSD 204 associates the detection logical request with the polling by the host device. In other embodiments, however,LSD 204 associates the detection logical request with a LSD interrupt and raises the LSD interrupt to the attention ofHD 202. In either case,HD 202 can be prompted to execute the appropriate requested detection process. - It should be noted that the invention is essentially symmetric in that any circuit or software application external to
LSD 204 and/orsystem 200 can targetLSD 204 usingHD 204 as a mechanism to establish a communication path between the requesting device and target device,LSD 204. In this way,LSD 204 can respond to requests (such as provide current status information, current capacity, etc.) that originate from external circuits or external software applications. For example,FIG. 4 illustrates a situation whereby remote application 220-3 compelsfirst storage area 240 to perform any of a number of storage operations independent ofHDFS 208. For example, external application 220-3 can write data tostorage area 240 by writing data to a pre-established proxy file 450 (also referred to as a placeholder file) that is visible and therefore manageable by host device file system (HDFS) 208. However, any data content included in placeholder file 450 can be considered “dummy” data in thatplaceholder file 450 is merely a part of the mechanism whereby remote application 220-3 can access/change data within proxy file without being “seen” by HDFS 208 (unless notified). - For example, external application 220-3 can write
data 454 to placeholder file 450 without intervention ofHDFS 208 by forwardingdata 454 to be written to placeholder file 450. In one implementation,data 454 can be sent directly to placeholder file 450 or useCSA 254 as a cache to buffer selected portions ofdata 454. WhenCSA 254 is used tocache data 454,data 454 is passed to placeholder file 450 by way ofcommunication path 256 without intervention by HD 202 (except for the establishing communication path 256). In this way, remote application 220-3 (or any external application 220 for that matter) can write data to placeholder file 450 or can streamdata 454 fromplaceholder file 450 without intervention byHDFS 208. - For example,
LSD 204 can perform a detection operation that determines that the available storage capacity offirst storage array 240 is less than a predetermined amount. Based upon that result, LSD logical request generator 340 can generate a LSD detectionlogical request 130 that promptsHD 202 to establishcommunication path 228 betweenLSD 204 and remote application 220-3. Oncecommunication path 228 has been established,HD 202 can have no intervention sinceHD 202 is now assuming a role commensurate to a modem, router, or other such device used to route data packets, for example. Once remote application 220-3 andLSD 204 are linked by way ofcommunication path 228,LSD 204 and remote application 220-3 can logically interact overcommunication path 228. For example,LSD 204 can forward results of the detection operation to remote application 220-3. Remote application 220-3 can respond by pushing (writing) data 454 (in the form of a user notification, advertisement, etc.) to placeholder file 452. Oncedata 454 is stored in placeholder file 452,data 454 is now visible toHDFS 208 and can be processed byHD 202 in any number of ways. For example,data 454 can be used byHD 204 to display a notification that additional storage capacity is required and even suggest a product to purchase and where it can be purchased and for what price. -
FIG. 5A shows a more detailed view ofnetwork 500 in accordance with an embodiment of the invention. In particular,network 500 is one embodiment ofnetwork 226 shown inFIG. 3 . In particular,network 500 is shown to includeserver computer 502 coupled tocomputing system 200 by way of distributed communication channels. Such distributed communication channels can include wireless communications (WiFi, Bluetooth, etc.) as well as wired communications, etc. In the described embodiment,server computer 502 includesserver component 504 that provides, in part, some clear and well defined interfaces, using, for example, standard Web technology e.g. HTTP/SOAP-based Web Services to developers and other users. In the described embodiment,server component 504 that can provide at least authorization and authentication services whenever a secure channel between a remote application andLSD 204, for example, is required. In this way, an efficient guard against possible network-originated attacks, spywares, malwares etc. can be provided. Furthermore, privacy protection, in order to ensure the end user content usage cannot be tracked by unauthorized third party, optimized communication protocol with the storage device possibly using some compression techniques and the server computer can also include broadcast and/or multicast capabilities.Device registration module 506 and/ordiscovery services module 508 can be included in or coupled toserver computer 502. -
Device registration module 506 anddiscovery services module 508 provide, respectively, a registration service and discovery service. By registration service it is meant that any device included in, added to, or removed fromnetwork 226 that is registered todevice registration module 506 has associated registration data updated consistent with a current status of the corresponding device. Such registration data can include device type, device location (IP address if the network is an IP protocol based network), etc. - In one embodiment, registration data associated with a device (or software application) can be updated by
registration module 506 in a number of different ways. One approach relies upon theregistration module 506 being notified that a device status has changed (i.e., the device has been added, removed, or has moved location withinnetwork 226, etc.). In some aspects of the invention, in order to preserve processing resources as well as network bandwidth, not all changes are considered of sufficient interest to notifyregistration module 506. However, in those situations when a device status change has occurred and notice is warranted,registration module 506 can be notified of the status change byregistration module 506 continually pinging all devices included innetwork 226 and requesting each device return current status information. Any status information that has changed with regards to a previous device status and that has been determined to represent a notifiable status change will invoke a notice event atdevice registration module 506. - In response to the notice event,
registration module 506 can request that the device having the changed status forward current device status information toregistration module 506. Once received byregistration module 506, the status information associated with the device can be updated atregistration module 506 and forwarded todiscovery server 508. Another approach can havedevice registration module 506 taking on a more passive approach in that each device can forward its particular current status todevice registration module 506 whenever a change in status has occurred. Again, in order to preserve computing resources and network bandwidth some aspects of the invention only provide for reporting only certain status changes and not all status changes. - In any case, once current status information has been received and appropriately processed,
registration module 506 can forward the current status information todiscovery services module 508 where it can be stored to provide subsequent discovery services to requesting devices and or software application. Such information can include any information related to any device included in network 324 in order to facilitate, for example, establishing a communication channel between the requesting device (including software applications, if any) and target device or target applications. - Still referring to FIG. 5A., if
LSD 222 has not been previously coupled withHD 204 but at somepoint LSD 222 is coupled toHD 204 by insertingLSD 204 into interface 223 (for example, inserting a Secure Digital (SD) card into a portable computer, digital camera in communication with a network, etc.) then LSD 222 can, in one aspect of the invention, notifydevice registration service 506 that it has joinednetwork 226. In yet another aspect of the invention, however,device registration service 506 can actively determine thatLSD 222 has enterednetwork 226 by, for example, pingingcomputing system 200 and determining that a notifiable change has occurred. - In the case where
LSD 222 actively notifiesdevice registration service 506 of a change in status (which in this case is thatLSD 222 has been added to network 226),LSD 222 can requestHD 202 to establish a communication channel betweenLSD 222 anddevice registration service 506 that includes network link 228 fromHD 202 tonetwork 226 andcommunication channel 510 fromnetwork 226 toregistration service 506, using at least one of the mechanisms described above. It should be noted that ifLSD 204 does not know the location ofdevice registration service 506, then eitherHD 202 will provide the location as a default location or network services will automatically direct status changes to a predefined location. - Once communication between
LSD 204 and registration service has been established, thendevice registration service 506 can update (either passively or actively) the current status of LSD 222 (where the current status ofLSD 222 is either pushed byLSD 222 or pulled by registration server 506). Once updated,device registration service 506 can then forward the current status ofLSD 222 todiscovery services module 508 where it is stored for subsequent retrieval whenever a remote device targetsLSD 222. It should be noted that registration information can include any relevant information related to the device. Such relevant information (in the case of a data storage device) can include logical storage device parameters (remaining available storage capacity, device IP address, available storage applications on the device, firmware version and characteristics, etc.) that are more of a fixed characteristic of the device. Such information can also include more transitory information such as currently available data storage capacity, quality of stored data, location of device, etc. as well as data content parameters that can include a file size, a file type, a file name, and a file keyword. - Once
discovery service 508 has been updated,discovery service 508 can provide requested discovery information to any requesting device (or software application) about any target device (or target software application) having data stored therein. For example,remote computing device 510 havingremote host device 512 coupled withremote storage device 514, can remotely invoke a storage operation on a target device such asLSD 204 usingdiscovery service 508 by first establishing a communication channel betweenremote computing device 510 andLSD 204. The communication channel can be established byremote computing device 510 sending a discovery request 516 todiscovery service 508 requesting discovery information fortarget device LSD 204. Such discovery information can include target device location information, target device current operating status information, target device current parametric information, etc. In response to the discovery request,discovery service 508 can forward a discovery server response 518 that includes the appropriate target device discovery information back to the requesting device (i.e., remote computing device 510). - Once
remote computing device 510 has received the appropriate target discovery information regardingtarget device LSD 204, then as shown inFIG. 5B ,remote computing device 510 can establish a communication channel between target device LSD 204 (usingHD 104 as a conduit) that includes atleast network link 228. Once the communication channel has been established betweentarget device LSD 204 andremote computing device 510, thenremote computing device 510 can remotely invoke any number and types of storage operations ontarget device LSD 204. Such operations can include, for example, reading, writing, and/or erasing data. -
FIG. 6 shows a flowchart detailing aprocess 600 in accordance with an embodiment of the invention.Process 600 begins at 602 by determining if a host device is in communication with a local storage device. By communication it is meant that the host device and local storage device have a capable communication channel established between them. By capable communication, it is meant that there is a physical connection established, a wireless connection established, or a logical connection established between the host device and the local storage device over which information can be passed. Once it has been determined that a capable communication path exists between the host device and the local storage device, then at 604 a determination is made if the local storage device has a pending LSD initiated event. By LSD initiated event it is meant an event unrelated to and independent of any host device or host device file system process. If at 604, it is determined that there is no pending LSD initiated event, then theprocess 600 ends, otherwise a 606 a determination is made whether or not the host device in continuously polling the local storage device. If the host device is not polling the local storage device, then the local storage device generates a LSD logical request at 608 that includes information related to the pending LSD initiated event and at 610 the local storage device throws up an interrupt flag associated with the LSD logical request. At 612, the host device responds to the interrupt flag. - Returning to 606, if the host device is continuously polling the local storage device, then at 614, the local storage device responds to the host device polling with an LSD polling response that includes information related to the pending LSD initiated event. At 616, the host device responds to the LSD polling response.
-
FIG. 7 illustrates aprocess 700 in accordance with an embodiment of the invention.Process 700 begins at 702 by determining if a remote device wants to invoke an operation on a local target device. If affirmative, then at 704 a determination is made if the remote device sends a query to the discovery server in order to obtain target device information. If the remote device has determined that it does not need to query the discovery server, than at 706 the remote device contacts the local device. On the other hand, if the remote device has determined that discovery information for the target device is needed, than at 708 a determination is made whether or not the discovery server has the target device discovery information. If it is determined that the discovery server does not have the requested target device discovery information, then at 710 a determination is made whether or not a registration server has the requested target device information. If it is determined that the registration server does not have the requested target device information, then process 700 ends. Otherwise, the registration server forwards the requested target device discovery information to the discovery server at 712. Returning back to 708, if the discovery server has determined that it has the requested target device discovery information, then at 714, the remote device sends a discovery information request to the discovery server and at 716 the discovery server provides the requested target device discovery information. At 706, the remote device contacts the target device and at in any case, at 718 the target device responds to the remote device. -
FIG. 8 provides a context of the invention where amedia network 800 as a specific configuration ofnetwork 226 includes a number of media devices such as media players. In this example,computing system 200 can be amedia player 100 arranged to store a number of digital media items (such as video, audio possibly as MP3 files, etc.).Network 800 can include distributedcommunications 802 configured as either or both awired network 804 and a wireless network 806. In the described embodiment,wired data network 802 pertains to some portion of the World Wide Web. Personal computer 806 can couple to wired network 802 (which in this case is connected tocomputing system 100 by way of a USB cable at second interface).Wireless data network 804 can also couple towired data network 802.Wireless data network 804 can include one or more wireless data networks, such as cellular networks, WiFi networks, WiMAX networks, etc. -
Media network 800 includescentral media server 808 that stores or has access to numerous media items. In addition,network 800 supports one or more additional computing systems 810 configured as network devices that can take the form of portable media devices such asportable media player computing system 200 shown inFIG. 2 . Any of theportable media devices wired link 816 orwireless link 818. As an example,wired link 816 can correspond to a cable (e.g., USB cable) that, if available, can interconnect portable media device 810 to personal computer 806.Wireless link 818 can be provided by a wireless capability, such as Bluetooth, infrared, etc. Typically, the portable media device 810 would be capable of communicating with personal computer 806 using eitherwired link 816,wireless link 816, or both. - Portable media device 814 can couple to the
wireless data network 804 over awireless link 820. Similarly,portable media device 812 can couple towireless data network 804 over awireless link 822. In this regard,portable media devices 814 and 812 can accesscentral media server 808 viawireless data network 804. In addition,portable media devices 810, 812 and 814 can wirelessly access each other, thereby exchange media item data between portable media devices. -
Computing system 200 can take the form of a media device that can pertain to portable media players such as MP3 players as well as wireless device such as mobile phones that can includeLSD 204 andHD 202. These mobile devices can include a media management application on the host computer that operates on the mobile device. Given the portability of mobile devices, mobile devices are smaller and have less resources (e.g., storage capacity). Consequently, a media management application designed for use on a mobile device can offer less features and capabilities than would a counterpart media management application operating on a larger, more powerful computing device, e.g., a personal computer. Given that the mobile devices have wireless access tocentral media server 808, the mobile devices can interact withmedia server 808 to request and/or receive media item data (or other data). In this regard, a media management application operating on the mobile devices can communicate with themedia server 808 to perform various tasks, including: navigating available media content at the server (such as navigation of a media store), receiving a periodic delivery of media content to media devices (such as a daily pushing of media item data from a server to a media device), etc. -
FIG. 9 shows arepresentative system 900 illustrating additional components typically found inhost device 204.System 900 includes central processing unit (CPU) 910, random access memory (RAM) 920, read only memory (ROM) 930, andprimary storage devices ROM 930 acts to transfer data and instructions uni-directionally to theCPU 910, whileRAM 920 is used typically to transfer data and instructions in a bi-directional manner.CPU 910 may generally include any number of processors. Bothprimary storage devices CPUs 910 are also coupled to one or more input/output devices 960 familiar to those of skill in the computer hardware and software arts. - In the described embodiment, mobile devices (e.g., portable media devices) can communicate with one another. This type of communication can be referred to as peer-to-peer interaction. In this regard, one mobile device can communicate (e.g., unicast) directly with another mobile device. In another example, one mobile device can communicate (e.g., broadcast, any cast or multicast) to a plurality of other mobile devices. In the peer-to-peer environment, one mobile device can communicate with one or more other electronic devices (whether mobile or stationary) in the immediate vicinity. Data sharing can be performed when such communication is available.
- Data transfer could be between a mobile device and a computing device, such as a home computer or another mobile device. Typically, the mobile device and the computing device would be associated with a particular user. For example, when the mobile device is within range of a home computer (or a home network), data transfer can be performed between the mobile device and the home computer. Data transfer could also be between two or more mobile devices, or between two or more non-mobile devices. The data transfer can be automatic without any user action or can alternatively require manual approval by a user. The network devices can be associated with one another via an identification number or other suitable mechanism.
- A mobile device or non-mobile device capable of receiving, transmitting and/or storing data may be referred to as a “data device.” The manner by which the data arrives at the data device can depend upon implementation. For example, the data can be directly transferred to the data device, or the data can be indirectly transferred to the data device. For example, the data transfer can be between one data device to another data device. Alternatively, one data device can cause another data device to transfer desired data to a recipient data device.
- The shared data can be transferred to a recipient device by file transfer or streaming. The data transferred can be received by one or more data devices. Examples of data devices include a media player, PDA, a speaker unit, a wireless transmitter/receiver unit, etc. Users of data devices can also create and distribute content through data sharing. The streaming can be limited so as to restrict the number of data devices simultaneously receiving the data. On the other hand, if the users of the data devices are subscribers to the streaming content (i.e., have a subscription), then the streaming can be unlimited as to subscribers. Storing some portion of the media item content associated with the media item metadata may also be done to facilitate the streaming of media item content. For example, a user could begin playing such a previously stored portion of the media item content before streaming of the remaining content even begins.
- Data can be shared after being purchased. For example, a recipient could purchase data from a remote server. The remote server would then cause the purchased data to be delivered to the recipient's data device. The purchase can be performed in real-time or can be deferred until a later point in time. Thereafter, the purchased data can be shared from the recipient's data device to another data device.
- For example, in the work environment or other network environment, as a user comes into an employer's office to work, the user's mobile device can transfer data to the user's work computer or to a network server for the office. The data transfer can be automatic without any user action or can alternatively require manual approval by a user. The user of the mobile device can also communicate with mobile devices of coworkers or other users of the network to exchange data.
- Regardless of the particular environment, the data transfer can be wireless. The wireless data transfer can be facilitated by a wireless network. One mobile device could wirelessly transmit data in a unicast fashion from one mobile device to another mobile device or stationary computing device. Still further, one mobile device could wirelessly transmit data in a multicast or broadcast fashion to a plurality of other mobile devices. It should be noted that any home-server computer can reside on any of a number of other data storage devices in a network to which
computing device 200 belongs. - The advantages of the invention are numerous. Different embodiments or implementations may yield one or more of the following advantages. One advantage of the invention is legacy devices can be added or removed without consideration of modifying system hardware. Another advantage of the invention is that it can be used with any host computer without modification therefore reducing the cost and increasing the applicability of the invention.
- The many features and advantages of the invention are apparent from the written description and, thus, it is intended by the appended claims to cover all such features and advantages of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the invention to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention.
Claims (20)
1. A storage module comprising:
an interface providing a communication path between the storage module and a host device coupled with the storage module;
a local storage device agent configured to prompt a host device agent of the host device via the interface to establish a communication path with an application on an external device that is external to both the host device and the storage module, where the communication path is configured to allow the storage module to communicate with the application on the external device via the interface coupling the host device and the storage module; and
a non-volatile memory configured to store information received from the application on the external device over the communication path without intervention by the host device.
2. The storage module of claim 1 , wherein the external device is in communication with the host device over a network.
3. The storage module of claim 1 , wherein the local storage device agent is further configured to:
receive an indication that the host device has established the communication path with the application on the external device;
communicate information to the application on the external device over the communication path without intervention by the host device, wherein the information that the local storage device agent sends to the application on the external device is invisible to the host device file system; and
receive information from the application on the external device over the communication path without intervention by the host device.
4. The storage module of claim 3 , wherein the external device is an external storage module; and
wherein to communicate information to the application on the external device, the local storage device is configured to communicate a command to the application on the external storage module instructing the application on the external storage module to store the information at the external storage module.
5. The storage module of claim 4 , wherein the information that the controller sends to the application on the external device without intervention by the host device comprises at least one of a read command, a write command, and an erase command.
6. The storage module of claim 4 , wherein the information received from the application on the external device without intervention by the host device comprises at least one of a read command, a write command, and an erase command.
7. The storage module of claim 1 , wherein the controller is configured to prompt the host device to establish the communication path with the application on the external device in response to the external device registering on a network on which the host device is also registered.
8. The storage module of claim 1 , wherein the storage module is embedded in the host device.
9. The storage module of claim 1 , wherein the storage module is a removable memory card.
10. A method comprising:
in a storage module comprising an interface and a controller in communication with the interface, the interface configured to provide a communication path between the storage module and a host device coupled with the storage module:
prompting over the interface the host device to establish a communication path with an application on an external device that is external to both the host device and the storage module, where the communication path is configured to allow the storage module to communicate with the application on the external device via the interface coupling the host device and the storage module;
receiving an indication that the host device has established the communication path with the application on the external device;
communicating information to the application on the external device over the communication path without intervention by the host device, wherein the information that the controller sends to the application on the external device is invisible to the host device file system; and
receiving information from the application on the external device over the communication path without intervention by the host device.
11. The method of claim 10 , wherein the external device is in communication with the host device over a network.
12. The method of claim 10 , wherein the external device is an external storage module; and
wherein communicating information to the application on the external device comprises communicating a command to the application on the external storage module instructing the application on the external storage module to store the information at the external storage module.
13. The method of claim 10 , wherein the information that the controller sends to the application on the external device without intervention by the host device comprises at least one of a read command, a write command, and an erase command.
14. The method of claim 10 , wherein the information received from the application on the external device without intervention by the host device comprises at least one of a read command, a write command, and an erase command.
15. The method of claim 10 , wherein the information received from the application on the external device compels the controller to perform a storage operation on the non-volatile memory independent of a host device file system.
16. The method of claim 10 , wherein the controller prompts the host device to establish the communication path with the application on the external device in response to the external device registering on a network on which the host device is also registered.
17. The method of claim 10 , wherein the storage module is embedded in the host device.
18. The method of claim 10 , wherein the storage module is a memory card.
19. A storage module comprising:
means for providing a communication path between the storage module and a host device coupled with the storage module;
means for prompting a host device agent of the host device via the interface to establish a communication path with an application on an external device that is external to both the host device and the storage module, where the communication path is configured to allow the storage module to communicate with the application on the external device via the interface coupling the host device and the storage module; and
a non-volatile memory configured to store information received from the application on the external device over the communication path without intervention by the host device.
20. The storage module of claim 19 , further comprising:
means for communicating information to the application on the external device over the communication path without intervention by the host device, wherein the information that local storage device agent sends to the application on the external device is invisible to the host device file system.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/317,950 US20140379966A1 (en) | 2008-01-02 | 2014-06-27 | Distributed Storage Service Systems and Architecture |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US1864408P | 2008-01-02 | 2008-01-02 | |
US1897908P | 2008-01-04 | 2008-01-04 | |
US12/019,573 US8452927B2 (en) | 2008-01-02 | 2008-01-24 | Distributed storage service systems and architecture |
US13/355,146 US20120185641A1 (en) | 2008-01-02 | 2012-01-20 | Distributed Storage Service Systems and Architecture |
US14/317,950 US20140379966A1 (en) | 2008-01-02 | 2014-06-27 | Distributed Storage Service Systems and Architecture |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/355,146 Continuation US20120185641A1 (en) | 2008-01-02 | 2012-01-20 | Distributed Storage Service Systems and Architecture |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140379966A1 true US20140379966A1 (en) | 2014-12-25 |
Family
ID=40799965
Family Applications (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/019,573 Active 2030-10-09 US8452927B2 (en) | 2008-01-02 | 2008-01-24 | Distributed storage service systems and architecture |
US12/036,440 Expired - Fee Related US8370850B2 (en) | 2008-01-02 | 2008-02-25 | Cache management |
US12/045,472 Expired - Fee Related US8359654B2 (en) | 2008-01-02 | 2008-03-10 | Digital content distribution and consumption |
US12/059,107 Active 2037-03-17 US10289349B2 (en) | 2008-01-02 | 2008-03-31 | Data usage profiling by local storage device |
US12/101,065 Active 2029-06-26 US8959285B2 (en) | 2008-01-02 | 2008-04-10 | Storage system with local and remote storage devices which are managed by the local storage device |
US13/355,146 Abandoned US20120185641A1 (en) | 2008-01-02 | 2012-01-20 | Distributed Storage Service Systems and Architecture |
US14/317,950 Abandoned US20140379966A1 (en) | 2008-01-02 | 2014-06-27 | Distributed Storage Service Systems and Architecture |
Family Applications Before (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/019,573 Active 2030-10-09 US8452927B2 (en) | 2008-01-02 | 2008-01-24 | Distributed storage service systems and architecture |
US12/036,440 Expired - Fee Related US8370850B2 (en) | 2008-01-02 | 2008-02-25 | Cache management |
US12/045,472 Expired - Fee Related US8359654B2 (en) | 2008-01-02 | 2008-03-10 | Digital content distribution and consumption |
US12/059,107 Active 2037-03-17 US10289349B2 (en) | 2008-01-02 | 2008-03-31 | Data usage profiling by local storage device |
US12/101,065 Active 2029-06-26 US8959285B2 (en) | 2008-01-02 | 2008-04-10 | Storage system with local and remote storage devices which are managed by the local storage device |
US13/355,146 Abandoned US20120185641A1 (en) | 2008-01-02 | 2012-01-20 | Distributed Storage Service Systems and Architecture |
Country Status (1)
Country | Link |
---|---|
US (7) | US8452927B2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9158460B2 (en) | 2011-04-25 | 2015-10-13 | Kt Corporation | Selecting data nodes using multiple storage policies in cloud storage system |
US9888062B2 (en) | 2010-12-24 | 2018-02-06 | Kt Corporation | Distributed storage system including a plurality of proxy servers and method for managing objects |
US10810016B2 (en) | 2015-08-11 | 2020-10-20 | Samsung Electronics Co., Ltd. | Operating methods of computing devices comprising storage devices including nonvolatile memory devices, buffer memories and controllers |
Families Citing this family (65)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9052826B2 (en) * | 2006-07-28 | 2015-06-09 | Condusiv Technologies Corporation | Selecting storage locations for storing data based on storage location attributes and data usage statistics |
KR101473344B1 (en) * | 2007-08-24 | 2014-12-17 | 삼성전자 주식회사 | Devices that use flash memory as storage and how they work |
US8583878B2 (en) * | 2008-01-02 | 2013-11-12 | Sandisk Il Ltd. | Storage device having direct user access |
US8370402B2 (en) | 2008-01-02 | 2013-02-05 | Sandisk Il Ltd | Dual representation of stored digital content |
US9098506B2 (en) * | 2008-01-02 | 2015-08-04 | Sandisk Il, Ltd. | Data indexing by local storage device |
US8452927B2 (en) * | 2008-01-02 | 2013-05-28 | Sandisk Technologies Inc. | Distributed storage service systems and architecture |
US8271751B2 (en) | 2008-04-24 | 2012-09-18 | Echostar Technologies L.L.C. | Systems and methods for reliably managing files in a computer system |
US7877522B2 (en) | 2008-05-27 | 2011-01-25 | Sandisk Il Ltd. | Method of monitoring host activity |
US20090310760A1 (en) * | 2008-06-17 | 2009-12-17 | Judith Neely Coltman | Audio Message Recorder with Flexible Control |
CN101640589B (en) * | 2008-07-29 | 2012-11-07 | 华为技术有限公司 | Method and device for sharing license between safe and removable media |
JP5135147B2 (en) * | 2008-09-29 | 2013-01-30 | 富士フイルム株式会社 | Video file transmission server and operation control method thereof |
US9092387B2 (en) * | 2008-12-10 | 2015-07-28 | Micron Technology, Inc. | Non-volatile memory device capable of initiating transactions |
US8738621B2 (en) | 2009-01-27 | 2014-05-27 | EchoStar Technologies, L.L.C. | Systems and methods for managing files on a storage device |
FI129360B (en) | 2009-04-15 | 2021-12-31 | Andritz Oy | Method of reducing flue gas emissions and boiler |
CN102687157B (en) | 2009-08-17 | 2015-09-16 | 克拉姆全球有限责任公司 | Digital content management and sending |
US8788615B1 (en) * | 2009-10-02 | 2014-07-22 | Adobe Systems Incorporated | Systems and methods for creating and using electronic content that requires a shared library |
US10496608B2 (en) * | 2009-10-28 | 2019-12-03 | Sandisk Il Ltd. | Synchronizing changes in a file system which are initiated by a storage device and a host device |
US8886597B2 (en) * | 2009-10-28 | 2014-11-11 | Sandisk Il Ltd. | Synchronizing changes in a file system which are initiated by a storage device and a host device |
US20110122142A1 (en) * | 2009-11-24 | 2011-05-26 | Nvidia Corporation | Content presentation protection systems and methods |
TWI439859B (en) * | 2009-11-30 | 2014-06-01 | Silicon Motion Inc | Data storage system and data management method thereof |
US9514089B1 (en) | 2010-03-31 | 2016-12-06 | EMC IP Holding Company LLC | Mobile device network data synchronization |
US8694744B1 (en) | 2010-03-31 | 2014-04-08 | Emc Corporation | Mobile device snapshot backup |
US8655966B1 (en) | 2010-03-31 | 2014-02-18 | Emc Corporation | Mobile device data protection |
US8683005B1 (en) * | 2010-03-31 | 2014-03-25 | Emc Corporation | Cache-based mobile device network resource optimization |
US9152650B1 (en) | 2010-03-31 | 2015-10-06 | Emc Corporation | Mobile device data recovery |
US8694597B1 (en) | 2010-03-31 | 2014-04-08 | Emc Corporation | Mobile device group-based data sharing |
US8700841B2 (en) | 2010-04-19 | 2014-04-15 | International Business Machines Corporation | Sub-LUN input/output profiling for SSD devices |
WO2013015835A1 (en) | 2011-07-22 | 2013-01-31 | Seven Networks, Inc. | Mobile application traffic optimization |
WO2012051590A1 (en) * | 2010-10-15 | 2012-04-19 | Magtek, Inc. | Systems and methods for authenticating aspects of an oline transaction using a secure peripheral device having a message display and/or user input |
US8898310B2 (en) | 2010-12-15 | 2014-11-25 | Microsoft Corporation | Enhanced content consumption |
US9633391B2 (en) | 2011-03-30 | 2017-04-25 | Cram Worldwide, Llc | Secure pre-loaded drive management at kiosk |
US20120297158A1 (en) * | 2011-05-19 | 2012-11-22 | Chih-Yao Hua | Mass storage device capable of accessing a network storage |
US9449113B2 (en) | 2011-06-28 | 2016-09-20 | Microsoft Technology Licensing, Llc | Browser storage management |
DK2555488T3 (en) * | 2011-08-02 | 2016-06-13 | Telia Co Ab | A method for transmitting data to a functional application and a user terminal therefor |
EP2600257A1 (en) * | 2011-11-30 | 2013-06-05 | Thomson Licensing | Method and apparatus for processing digital content |
CN102521361A (en) * | 2011-12-15 | 2012-06-27 | 北京世纪高通科技有限公司 | Distributed type storage method based on massive Sequence File data |
US9900231B2 (en) | 2012-01-27 | 2018-02-20 | Microsoft Technology Licensing, Llc | Managing data transfers over network connections based on priority and a data usage plan |
US9740435B2 (en) * | 2012-02-27 | 2017-08-22 | Fujifilm North America Corporation | Methods for managing content stored in cloud-based storages |
US9210217B2 (en) | 2012-03-10 | 2015-12-08 | Headwater Partners Ii Llc | Content broker that offers preloading opportunities |
US9503510B2 (en) | 2012-03-10 | 2016-11-22 | Headwater Partners Ii Llc | Content distribution based on a value metric |
US9338233B2 (en) | 2012-03-10 | 2016-05-10 | Headwater Partners Ii Llc | Distributing content by generating and preloading queues of content |
US8868639B2 (en) | 2012-03-10 | 2014-10-21 | Headwater Partners Ii Llc | Content broker assisting distribution of content |
US20130305388A1 (en) * | 2012-05-10 | 2013-11-14 | Qualcomm Incorporated | Link status based content protection buffers |
US9003381B2 (en) * | 2012-08-14 | 2015-04-07 | Derek J. Conrod | Context-specific optimized code |
US10348778B2 (en) * | 2013-02-08 | 2019-07-09 | Avaya Inc. | Dynamic device pairing with media server audio substitution |
CN103269371B (en) * | 2013-05-23 | 2016-06-01 | 中国科学院计算机网络信息中心 | A kind of thing based on Anycast networking DS querying method and system |
KR20150065435A (en) * | 2013-12-05 | 2015-06-15 | 삼성전자주식회사 | Storage device and computing system |
CN103645992B (en) * | 2013-12-19 | 2016-09-28 | 深圳市捷顺科技实业股份有限公司 | A partition formatting method and device for iNAND |
US9880971B2 (en) * | 2013-12-20 | 2018-01-30 | Rambus Inc. | Memory appliance for accessing memory |
US9933980B2 (en) * | 2014-02-24 | 2018-04-03 | Toshiba Memory Corporation | NAND raid controller for connection between an SSD controller and multiple non-volatile storage units |
CN103870570B (en) * | 2014-03-14 | 2018-04-27 | 上海艾讯云计算有限公司 | HBase data availability and persistence method based on remote log backup |
US10133488B2 (en) * | 2014-03-17 | 2018-11-20 | Primaryio, Inc. | Apparatus and method for cache provisioning, configuration for optimal application performance |
US10146437B2 (en) | 2014-03-17 | 2018-12-04 | Primaryio, Inc. | Tier aware caching solution to increase application performance |
US9003109B1 (en) | 2014-05-29 | 2015-04-07 | SanDisk Technologies, Inc. | System and method for distributed computing in non-volatile memory |
US9842115B2 (en) | 2014-05-30 | 2017-12-12 | Apple Inc. | Media asset proxies |
KR102275706B1 (en) * | 2014-06-30 | 2021-07-09 | 삼성전자주식회사 | Method of operating data storage device and method of operating data processing system having same |
US9967358B2 (en) * | 2015-03-26 | 2018-05-08 | International Business Machines Corporation | Collaborative based caching |
CN105187783A (en) * | 2015-08-30 | 2015-12-23 | 周良勇 | Monitoring video file processing method |
US10261902B2 (en) * | 2016-01-04 | 2019-04-16 | Toshiba Memory Corporation | Parallel processing of a series of data units for writing |
CN106020960B (en) * | 2016-05-30 | 2020-02-18 | 北京奇艺世纪科技有限公司 | Calling method and device |
CN107122227A (en) * | 2017-04-12 | 2017-09-01 | 福建星海通信科技有限公司 | A kind of picture method for down loading based on JavaScript front ends script |
US10656869B1 (en) * | 2018-06-28 | 2020-05-19 | Amazon Technologies, Inc. | Performance-based volume replica migration |
DE112019007666T5 (en) * | 2019-08-27 | 2022-06-15 | Micron Technology, Inc. | Write buffer control in a managed storage system |
TWI820883B (en) * | 2022-08-30 | 2023-11-01 | 新唐科技股份有限公司 | Integrated circuit and method for cleaning valid bits in cache memory thereof |
US20240192871A1 (en) * | 2022-12-13 | 2024-06-13 | International Business Machines Corporation | Speeding cache scans with a bytemap of active tracks with encoded bits |
Family Cites Families (64)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2591008B1 (en) | 1985-11-30 | 1991-05-17 | Toshiba Kk | PORTABLE ELECTRONIC DEVICE |
US5000185A (en) * | 1986-02-28 | 1991-03-19 | Cardiovascular Imaging Systems, Inc. | Method for intravascular two-dimensional ultrasonography and recanalization |
US5509134A (en) | 1993-06-30 | 1996-04-16 | Intel Corporation | Method and apparatus for execution of operations in a flash memory array |
JPH11296418A (en) | 1998-04-09 | 1999-10-29 | Nec Corp | File system |
US7685311B2 (en) | 1999-05-03 | 2010-03-23 | Digital Envoy, Inc. | Geo-intelligent traffic reporter |
US7318117B2 (en) | 2004-02-26 | 2008-01-08 | Super Talent Electronics, Inc. | Managing flash memory including recycling obsolete sectors |
US6901385B2 (en) | 2000-02-17 | 2005-05-31 | Matsushita Electric Industrial Co., Ltd. | Semiconductor memory card that records contents for trial and purchase, recording apparatus, reproducing apparatus, and sales method |
EP1410276A1 (en) | 2000-05-19 | 2004-04-21 | Gemplus | Portable electronic device, method and system for analysing and/or predicting behaviour using same |
GB2400707B (en) | 2000-05-25 | 2004-12-29 | Sealedmedia Ltd | Search engine and digital rights management |
US6986030B2 (en) | 2000-10-27 | 2006-01-10 | M-Systems Flash Disk Pioneers Ltd. | Portable memory device includes software program for interacting with host computing device to provide a customized configuration for the program |
JP4524480B2 (en) | 2000-11-24 | 2010-08-18 | 三洋電機株式会社 | Data terminal equipment |
US20020174295A1 (en) | 2001-01-29 | 2002-11-21 | Ulrich Thomas R. | Enhanced file system failure tolerance |
US6748467B2 (en) | 2001-01-30 | 2004-06-08 | Hitachi, Ltd. | High speed data transfer between mainframe storage systems |
JP2003058487A (en) | 2001-08-13 | 2003-02-28 | Hitachi Ltd | Data access control method |
US7209633B1 (en) | 2002-01-23 | 2007-04-24 | Melodeo, Inc. | System and methods for logical memory devices in a digital media player |
US6732222B1 (en) | 2002-02-01 | 2004-05-04 | Silicon Motion, Inc. | Method for performing flash memory file management |
US6922757B2 (en) * | 2002-02-15 | 2005-07-26 | Exanet Inc. | Flexible and adaptive read and write storage system architecture |
US7085879B2 (en) * | 2002-02-27 | 2006-08-01 | Microsoft Corporation | Dynamic data structures for tracking data stored in a flash memory device |
US7143420B2 (en) | 2002-08-29 | 2006-11-28 | Sun Microsystems, Inc. | Strategic technology architecture roadmap |
US7945669B2 (en) | 2002-10-30 | 2011-05-17 | Emc Corporation | Method and apparatus for provisioning storage resources |
US20040117785A1 (en) | 2002-12-13 | 2004-06-17 | Samsung Electronics Co., Ltd. | Component download manager for a wireless mobile station and method of operation |
US20060107330A1 (en) | 2003-01-02 | 2006-05-18 | Yaacov Ben-Yaacov | Method and system for tracking and managing rights for digital music |
ATE350875T1 (en) * | 2003-02-13 | 2007-01-15 | Research In Motion Ltd | MANUAL NETWORK SELECTION FOR MOBILE STATIONS |
US6842794B2 (en) | 2003-05-27 | 2005-01-11 | Inventec Corporation | Method for starting a data processing system via a flash memory device |
JP2005056077A (en) | 2003-08-01 | 2005-03-03 | Hitachi Ltd | Database control method |
US20080147964A1 (en) | 2004-02-26 | 2008-06-19 | Chow David Q | Using various flash memory cells to build usb data flash cards with multiple partitions and autorun function |
US20050203872A1 (en) | 2004-03-05 | 2005-09-15 | Kwong Kwan John M. | Method and apparatus making, operating and using media parsers to mark, read, and unmark instances of media formats supporting one, two and multi-dimensional instances and data streams |
US7363510B2 (en) | 2004-05-26 | 2008-04-22 | Mount Sinai School Of Medicine Of New York University | System and method for presenting copy protected content to a user |
WO2005125072A2 (en) | 2004-06-22 | 2005-12-29 | Nds Limited | Digital rights management system |
US8181255B2 (en) | 2004-06-22 | 2012-05-15 | Nds Limited | Digital rights management system |
US7427027B2 (en) | 2004-07-28 | 2008-09-23 | Sandisk Corporation | Optimized non-volatile storage systems |
CN101027929B (en) | 2004-09-23 | 2012-04-25 | 金雅拓股份有限公司 | System and method for communication with universal integrated circuit cards in mobile devices using internet protocols |
US9384619B2 (en) | 2006-07-31 | 2016-07-05 | Ricoh Co., Ltd. | Searching media content for objects specified using identifiers |
US7395395B2 (en) | 2004-11-09 | 2008-07-01 | At&T Delaware Intellectual Property, Inc. | Methods, systems, and storage mediums for monitoring consumption of storage space and relocating content contained in the storage when a predetermined condition is met |
WO2006053958A1 (en) | 2004-11-17 | 2006-05-26 | David Fauthoux | Portable personal mass storage medium and computer system with secure access to a user space via a network |
US7406489B2 (en) | 2005-01-28 | 2008-07-29 | Solid Information Technology Oy | Apparatus, system and method for persistently storing data in a data synchronization process |
US20060288166A1 (en) | 2005-06-17 | 2006-12-21 | Wanderback Llc | System, method, and computer program product for nonvolatile memory devices |
US7457910B2 (en) | 2005-06-29 | 2008-11-25 | Sandisk Corproation | Method and system for managing partitions in a storage device |
CA2513014A1 (en) | 2005-07-22 | 2007-01-22 | Research In Motion Limited | A method of controlling delivery of multi-part content from an origin server to a mobile device browser via a proxy server |
CA2513022A1 (en) | 2005-07-22 | 2007-01-22 | Research In Motion Limited | System and method for communicating state management between a browser user-agent and a mobile data server |
CA2513019A1 (en) | 2005-07-22 | 2007-01-22 | Research In Motion Limited | A method for communicating state information between a server and a mobile device browser with version handling |
CA2513018A1 (en) | 2005-07-22 | 2007-01-22 | Research In Motion Limited | Method for training a proxy server for content delivery based on communication of state information from a mobile device browser |
US20070038749A1 (en) * | 2005-07-29 | 2007-02-15 | Broadcom Corporation | Combined local and network storage interface |
US7627733B2 (en) | 2005-08-03 | 2009-12-01 | Sandisk Corporation | Method and system for dual mode access for storage devices |
JP5068754B2 (en) | 2005-08-03 | 2012-11-07 | サンディスク テクノロジィース インコーポレイテッド | Improved host interface |
US7925973B2 (en) | 2005-08-12 | 2011-04-12 | Brightcove, Inc. | Distribution of content |
JP5155861B2 (en) | 2005-08-25 | 2013-03-06 | シリコン イメージ,インコーポレイテッド | Smart scalable memory switch architecture |
US20070056042A1 (en) | 2005-09-08 | 2007-03-08 | Bahman Qawami | Mobile memory system for secure storage and delivery of media content |
WO2007044947A2 (en) | 2005-10-12 | 2007-04-19 | Clevx, Llc | Software-firmware transfer system |
CA2540058A1 (en) | 2005-12-06 | 2007-06-08 | Emeka Akaezuwa | Portable search engine |
US20070156998A1 (en) | 2005-12-21 | 2007-07-05 | Gorobets Sergey A | Methods for memory allocation in non-volatile memories with a directly mapped file storage system |
US7747837B2 (en) | 2005-12-21 | 2010-06-29 | Sandisk Corporation | Method and system for accessing non-volatile storage devices |
US8327192B2 (en) | 2006-02-06 | 2012-12-04 | Intel Corporation | Method for memory integrity |
US8787973B2 (en) | 2006-03-20 | 2014-07-22 | Sandisk Il Ltd. | Device and method for controlling usage of a memory card |
US8706799B2 (en) | 2006-05-29 | 2014-04-22 | Sandisk Il Ltd. | Method and apparatus to exchange information with a local storage device |
KR100833188B1 (en) | 2006-11-03 | 2008-05-28 | 삼성전자주식회사 | Nonvolatile memory system that stores data in single-level cells or multi-level cells, depending on the nature of the data |
US8549236B2 (en) | 2006-12-15 | 2013-10-01 | Siliconsystems, Inc. | Storage subsystem with multiple non-volatile memory arrays to protect against data losses |
US9201603B2 (en) | 2007-06-01 | 2015-12-01 | Oracle America, Inc. | Dynamic logical mapping |
US20090094160A1 (en) | 2007-10-09 | 2009-04-09 | Webster Kurt F | Portable digital content device and methods for use therewith |
US9098506B2 (en) | 2008-01-02 | 2015-08-04 | Sandisk Il, Ltd. | Data indexing by local storage device |
US8370402B2 (en) | 2008-01-02 | 2013-02-05 | Sandisk Il Ltd | Dual representation of stored digital content |
US8583878B2 (en) | 2008-01-02 | 2013-11-12 | Sandisk Il Ltd. | Storage device having direct user access |
US20090171911A1 (en) | 2008-01-02 | 2009-07-02 | Sandisk Il, Ltd. | Data indexing by local storage device |
US8452927B2 (en) * | 2008-01-02 | 2013-05-28 | Sandisk Technologies Inc. | Distributed storage service systems and architecture |
-
2008
- 2008-01-24 US US12/019,573 patent/US8452927B2/en active Active
- 2008-02-25 US US12/036,440 patent/US8370850B2/en not_active Expired - Fee Related
- 2008-03-10 US US12/045,472 patent/US8359654B2/en not_active Expired - Fee Related
- 2008-03-31 US US12/059,107 patent/US10289349B2/en active Active
- 2008-04-10 US US12/101,065 patent/US8959285B2/en active Active
-
2012
- 2012-01-20 US US13/355,146 patent/US20120185641A1/en not_active Abandoned
-
2014
- 2014-06-27 US US14/317,950 patent/US20140379966A1/en not_active Abandoned
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9888062B2 (en) | 2010-12-24 | 2018-02-06 | Kt Corporation | Distributed storage system including a plurality of proxy servers and method for managing objects |
US9158460B2 (en) | 2011-04-25 | 2015-10-13 | Kt Corporation | Selecting data nodes using multiple storage policies in cloud storage system |
US10810016B2 (en) | 2015-08-11 | 2020-10-20 | Samsung Electronics Co., Ltd. | Operating methods of computing devices comprising storage devices including nonvolatile memory devices, buffer memories and controllers |
Also Published As
Publication number | Publication date |
---|---|
US8452927B2 (en) | 2013-05-28 |
US10289349B2 (en) | 2019-05-14 |
US20090172694A1 (en) | 2009-07-02 |
US8370850B2 (en) | 2013-02-05 |
US20120185641A1 (en) | 2012-07-19 |
US8359654B2 (en) | 2013-01-22 |
US20090172400A1 (en) | 2009-07-02 |
US20090172275A1 (en) | 2009-07-02 |
US20090172217A1 (en) | 2009-07-02 |
US20090172276A1 (en) | 2009-07-02 |
US8959285B2 (en) | 2015-02-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8452927B2 (en) | Distributed storage service systems and architecture | |
US8583878B2 (en) | Storage device having direct user access | |
US10649801B2 (en) | Virtual machine based content processing | |
EP2249254A2 (en) | Storage device having direct user access | |
CN101930449B (en) | Client, brokerage server and method for providing cloud storage | |
RU2631137C2 (en) | Connection of devices | |
US9119052B2 (en) | Content sharing for mobile devices | |
CN107168905A (en) | A kind of document display method, device, storage medium and mobile terminal | |
US20090210923A1 (en) | Personal license server and methods for use thereof | |
US7953822B2 (en) | Method of and apparatus for downloading data | |
CN106101206A (en) | The method and system of content is provided | |
US20140115091A1 (en) | Machine-implemented file sharing method for network storage system | |
US20080313287A1 (en) | E-mail publishing of photos to photo albums | |
TW201448580A (en) | Directing a playback device to play a media item selected by a controller from a media server | |
CN102185881A (en) | Household digital equipment wireless multi-protocol space sharing storage manager and method | |
TWI599892B (en) | Home network system file management and sharing methods | |
CN108563752B (en) | Data interaction method, device, terminal device and storage medium | |
JP6578701B2 (en) | Information processing system, information processing device, terminal device, and program | |
CN108769389A (en) | Picture acquisition method and device, terminal equipment and storage medium | |
CN103795760A (en) | Method and system for processing document through network and system for processing data through network | |
KR101710488B1 (en) | File sharing apparatus and method | |
TWI436221B (en) | Method for providing remote access and communication device thereof | |
US20110270928A1 (en) | Data sharing operation between storage device and host group | |
CN119884255A (en) | A database access method and device | |
CN114915914A (en) | Terminal switching method and device and electronic equipment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |