JP2019083016A - System and method for file management by means of mobile computing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system and a method of file management by a mobile computing device. A system and method of file management by a mobile computing device. The example method performed by the computer system is to store the first file with the first size in memory by the computer system and the second file derived from the first file in memory. The step of storing a file, the second file having a second size, the second size being smaller than the first size, the step of storing and the memory performing a memory write operation. The step of determining that the fourth file is insufficient and the step of selecting the third file associated with the fourth file, the fourth file being derived from the third file, the step of selecting. And the step of removing the third file from memory. [Selection diagram] Fig. 1

Description

  The present disclosure relates generally to computer systems, and more particularly to systems and methods for file management by mobile computing devices.

  Mobile computing devices may have multiple input / output (I / O) interfaces and / or peripheral devices such as, for example, still image cameras, video cameras, and / or microphones. Files obtained by the mobile computing device via the above and other input / output interfaces may be stored in the mobile computing device's local memory.

JP, 2002-209131, A JP 2007-323378 A Unexamined-Japanese-Patent No. 2003-85008 JP 2011-257990 A JP, 2006-60630, A

  The present disclosure is illustrated by way of example, and not by way of limitation, and may be more fully understood by reference to the following detailed description when considered in connection with the drawings.

FIG. 1 is a network level diagram illustrating one exemplary embodiment of a mobile computing device that performs file management, in accordance with one or more aspects of the present disclosure. FIG. 10 schematically illustrates a data structure tracking access to files stored on a mobile computing device, in accordance with one or more aspects of the present disclosure. FIG. 10 schematically illustrates an example of a file management method, in accordance with one or more aspects of the present disclosure. FIG. 10 schematically illustrates a plurality of data structures supported by a computer system executing a calendar application, in accordance with one or more aspects of the present disclosure. FIG. 10 schematically illustrates an example of a calendar view rendered by a computer system executing a calendar application, in accordance with one or more aspects of the present disclosure. FIG. 10 schematically illustrates an example of a calendar view rendered by a computer system executing a calendar application, in accordance with one or more aspects of the present disclosure. FIG. 10 schematically illustrates an example of a notebook view rendered by a computer system executing a calendar application, in accordance with one or more aspects of the present disclosure. FIG. 10 schematically illustrates an example of a notebook view rendered by a computer system executing a calendar application, in accordance with one or more aspects of the present disclosure. 7 is a flow chart illustrating a file management method in accordance with one or more aspects of the present disclosure. FIG. 1 is a block diagram illustrating an exemplary computer system operating in accordance with an example of the present disclosure.

Described herein are methods and systems for file management by a mobile computing device. A "mobile computing device" refers herein to a portable device having at least one processor, memory, and at least one communication interface. However, it should be noted that the systems and methods described herein may be equally applicable to non-portable computer systems such as, for example, desktop computers.
Mobile computing devices can input information via various interfaces including, for example, keyboards, touch screens, network interfaces, microphones, video cameras, still image cameras, and / or microphones. Such mobile computing devices may be able to input still image files, video stream files, audio stream files, and / or document files (eg, text files).

  In some implementations, the mobile computing device can store the acquired file in its local memory in response to acquiring the file (e.g., a still image file). "Memory" as used herein refers to random access memory (RAM) and / or storage memory. The latter may be represented by one or more file systems residing in non-volatile memory such as EEPROM, flash memory, disk memory, etc.

  In response to obtaining the file, the mobile computing device may also send a copy of the obtained file to the file server, eg, via a wireless communication interface. The mobile computing device may further store the preview file derived from the captured image file in a local memory. The preview file may, for example, be in the form of a thumbnail image or other reduced size image or a reduced resolution image.

  The mobile computing device may further attempt a memory write operation (eg, storage of the newly acquired image file in a local file system). If the space available in the mobile computing device's local file system is insufficient to allow completion of the attempted memory write operation, the mobile computing device removes it from the local file system Thus, one or more previously acquired files can be selected to free up space needed to store the newly acquired files. In one illustrative example, the mobile computing device may remove the least recently accessed file by the number of file access operations. In another example, the mobile computing device can remove files that were least recently accessed. In a further example, the mobile computing device can remove files that were least recently acquired.

  In response to the removal of one or more selected files, the mobile computing device completes an attempted memory write operation (eg, storage of the newly acquired image file in the local file system) can do. Thereafter, in response to final receipt of a user interface command requesting a file previously removed from the local memory, the system can present a corresponding preview file. In response to receiving a user interface command that explicitly targets the full size file, the system can retrieve the full size file from the server where the file was originally stored.

  Thus, the mobile computing device can store a preview file of at least some of the files acquired by the mobile computing device, and can further accommodate full size files in the file system of the mobile computing device In scope, full-size versions of files can be stored for a subset of the files obtained. The full size file may be removed from the file system to accommodate the newly acquired file, and a preview file may be presented to the user in response to a user interface command. The full size file may be retrieved from the file server in response to receiving a user interface command that explicitly targets the full size file.

  In some implementations, the file management method described above may be implemented to facilitate processing of file attachments by a calendar application performed by a mobile computing device. "Calendar application" refers herein to an application that provides scheduling and tracking of events for individual users and / or groups of users.

  Various aspects of the systems and methods referred to above are described in detail herein below by way of example, and not by way of limitation.

  FIG. 1 illustrates a network level diagram of one exemplary embodiment of a computer system 1000 in accordance with one or more aspects of the present disclosure. Computer system 1000 may include one or more servers 110 executing server-side portions 120 of file management applications (e.g., calendar applications). One or more client computers 130 executing the client-side portion 125 of the file management application may be connected to the server computer 110 via a plurality of interconnected networks 115.

  A "computer", as used herein, refers to an apparatus that includes a processor, memory, and at least one I / O interface. The computer may be represented by, for example, a server, a virtual machine operating on a host computer system, a portable personal computer (PC) or a desktop personal computer (PC), a tablet computer, or a smartphone. Further, the term "computer" is a collection of all of the computers that individually or jointly execute a set (or sets) of instructions to perform any one or more of the methods described herein. Must be included.

  "Network", as used herein, refers to a distributed communication system that interconnects multiple computers. The network may be represented by, for example, a local area network (LAN), a wide area network (WAN), or a virtual private network (VPN). In some implementations, the plurality of interconnected networks 115 can include the Internet.

  The functions of computer system 1000 may be delivered to the end user via one or more client devices 130, such as, for example, a portable personal computer (PC) or desktop personal computer (PC), a tablet computer, or a smartphone. In one example, one or more client devices 130 provide user interface functionality and communicate to one or more servers 110, which process client request processing, load balancing, client authentication, authorization, files Storage and retrieval, billing, and other functions can be performed. These and other functions may be distributed among one or more servers 110 residing in one or more physical facilities.

  In another example, at least a portion of the server-side functions listed above may be performed by one or more client devices 130. In some implementations, the client device 130 can perform at least a subset of its functions while not connected to the server 110. This processing mode is also referred to as an off-line client operation mode.

  For example, some of the above-listed functions, such as client request processing, load balancing, client authentication, authorization, file storage and retrieval, and / or billing may be referred to as related to server side functionality. Other functions, such as, for example, accepting user input, acquiring files via one or more communication interfaces, and / or rendering information on a display, may be referred to as related to client-side functionality. However, in some embodiments, one or more of computer system 1000 performs at least a portion of server-side functionality related to server-side functionality and at least a portion of functions related to client-side functionality. May include a computer. Thus, the designation of client-side functionality and server-side functionality that may be referred to herein is for illustration purposes and has nothing to do with components of computer system 1000 in operation. Intended.

  In some implementations, computer system 1000 can be configured to obtain various types of files via one or more communication interfaces of mobile computing device 130. In one illustrative example, mobile computing device 130 may comprise a still image camera that may be used to acquire still image files. In another example, mobile computing device 130 may comprise a video camera that may be used to acquire a video stream. In a further example, mobile computing device 130 can comprise a microphone that can be used to acquire an audio stream. In a further example, mobile computing device 130 can comprise a keyboard or touch screen that can be used to obtain text files.

  In response to obtaining the file, the mobile computing device 130 can store the file in a local memory of the mobile computing device. In one illustrative example, the mobile computing device 130 can store files in a local file system residing in a local non-volatile memory. In another example, the mobile computing device 130 can store the file in a database residing in the local non-volatile memory.

  Further in response to obtaining the file, the mobile computing device 130 can send a copy of the file to one or more servers 110 executing the server-side portion 120 of the file management application. One or more servers 110 may store the received files in a file system, database, and / or any other repository of suitable architecture.

  Further in response to the file acquisition, the mobile computing device 130 can create a preview file derived from the acquired file. The preview file can have a size smaller than that of the base file. The preview file is intended to act as a proxy for the base file to render the base file on the screen of the mobile computing device, and unless the user is specifically requested to display the base file instead of the preview file, the mobile computing device The printing device may display one or more preview files corresponding to the file requested by the user in response to receiving a user interface command displaying the one or more files.

  For image files, a preview file can be provided, for example, by a thumbnail image or other reduced size image or a reduced resolution image. For video files, a preview file can be provided, for example, by a "trailer" that includes a subset of the frames of the base video file. For audio files, preview files may be provided, for example, by one or more portions of a base audio file. For text files, a preview file can be provided by a summary, synopsis, or other description of a base text file.

  In some implementations, the mobile computing device can create the preview file locally. Alternatively, the mobile computing device can send the obtained file to an external server for processing, and can then receive the preview file from that external server. In one illustrative example, server 110 processes the file to create a preview file in response to receiving the base file from mobile computing device 130 for storage in a server-based data repository The preview file can then be sent back to the mobile computing device 130.

  Mobile computing device 130 may track access to files stored on mobile computing device and / or server 110. In one illustrative example, the mobile computing device 130 may store in memory the data structure 200 schematically illustrated by FIG. 2 for each of a plurality of files acquired by the mobile computing device. it can. Data structure 200 may include file identifier 210, file creation timestamp 212, file access timestamp 214, and / or a total number 216 of file access operations. The information stored in this data structure may be used in identifying candidate files to be removed from the local memory of the mobile computing device 130, as described in more detail herein below.

  Mobile computing device 130 may be in local memory (eg, in one or more local file systems) to store files acquired by the mobile computing device via one or more input / output interfaces. ) Quotas can be allocated. Mobile computing device 130 has insufficient available local memory of the mobile computing device to handle attempted memory write operations (eg, storage of newly acquired files in a local file system) It may be finally determined that In order to complete the attempted memory write operation, the mobile computing device 130 removes from the file system based on predefined selection criteria and thus needs to store the newly acquired file You can select one of the previously acquired files to free up memory.

  In one illustrative example, the mobile computing device is configured to select a file having a minimum number of file access operations associated therewith based on the total number 216 of file access operations within the mobile computing device's local memory. The sequence of data structure 200 can be analyzed for multiple files stored in. In another example, the mobile computing device is data about a plurality of files stored in the mobile computing device's local memory to select the least recently accessed file based on the file access timestamp 214 The sequence of structure 200 can be analyzed. In a further example, the mobile computing device may data structure for a plurality of files stored in a local memory of the mobile computing device to select the most recently acquired file based on the file creation timestamp 212. 200 sequences can be analyzed. In a further example, the mobile computing device is located in the mobile computing device's local memory to select files that satisfy multiple conditions, such as the least recently accessed file created by a given date, for example. The sequence of data structure 200 can be analyzed for a plurality of stored files.

  In some implementations, the mobile computing device 130 can select a file to be removed among files of the same type as the newly acquired file. Alternatively, the mobile computing device 130 may select a file to be removed among files having a size greater than or equal to the size of the newly acquired file. In some implementations, the mobile computing device 130 can select multiple files to be removed that have a total size equal to or greater than the total size of newly acquired files.

  In response to the removal of one or more selected files, the mobile computing device completes an attempted memory write operation (e.g., storage of a newly acquired file in local memory) Can. The mobile computing device may further add an array of data structures 200 to include data structures that store creation and access timestamps of newly acquired files and / or access counters. The mobile computing device may further create a preview file corresponding to the newly acquired file and store it in the local memory, as described in more detail hereinabove.

  The mobile computing device may eventually receive a user interface command requesting to perform an operation on the file previously removed from the local memory. Thereafter, the mobile computing device presents the corresponding preview file and / or in response to receiving a user interface command that explicitly targets the base file, the file from the server where the file was previously stored. It can be taken out. If the local file system does not have enough available space to accommodate the full size file retrieved from the server, the mobile computing device is as described in more detail hereinabove. One or more least accessed files or files least recently accessed may be selected and those files may be removed from the local file system.

  Thus, as schematically illustrated by FIG. 3, the mobile computing device 130 may at least some of the files 314 acquired by the mobile computing device in the local memory (eg, the local file system 310). Preview files 312 can be stored. The mobile computing device may further store at least some full size versions of the file 314 to the extent that the full size file can be accommodated in the mobile computing device's local memory. In one illustrative example, the mobile computing device may store the plurality of preview files 312 corresponding to the base file 314 in a predefined quota 316 in the local file system 310. The mobile computing device is additionally capable of accommodating the base file corresponding to the preview file 312-2 in the predefined quota 316 in the local file system 310, as within the predefined quota 316 in the local file system 310. A plurality of preview files 312-2 having no base file can be stored.

  The base file 314-1 may be removed from the file system to accommodate the newly acquired file 318, and the corresponding preview file 312-1 may be presented to the user in response to user interface commands. it can. The full size file 314-1 may be retrieved from the file server in response to user interface commands that explicitly target the full size file 314-1.

  In some implementations, computer system 1000 can execute a calendar application that facilitates event scheduling and tracking for individual users and / or groups of users. Users can access the calendar application by various client devices, including mobile computing device 130.

  In one example, computer system 1000 can support a data model that includes calendar entries and notes, as schematically illustrated by FIG. Calendar items may be represented by a data structure 410 that includes an identifier 412 and a time 414. In some implementations, the identifier 412 can be provided by a human readable sequence of alphanumeric characters including the title and / or description of the calendar item. Alternatively, the calendar item identifier may be provided by an alphanumeric or non-alphanumeric identifier that is not intended to be human readable.

  In some implementations, time 414 may be represented by the start time of the event identified by the calendar entry and the duration of the event. Alternatively, the time 414 may be represented by the start and end times of the event. The start time and / or end time of an event may be represented by a date (eg, including day, month, and year) and a time (eg, including hour, minute, and second). Time 414 may further include a time zone identifier.

  Data structure 410 includes calendar item title 416, description 418, location 420, identifier 422 of the origin of the event identified by the calendar item, list of participants of the event 424, recurring schedule 426, and / or other fields. It can further include. In some implementations, the data structure 410 can include a calendar item type identifier 411. Examples of calendar items represented by data structure 410 may include meeting appointments, meeting requests, reminders, and the like. In some implementations, data structure 410 may include one or more pointers 428 to a data set, which may also be referred to as an attached file. In one example, the attached file can be provided by any type of file, such as text, audio stream, video stream, still image, etc.

  A note can be represented by a data structure 440 that includes note text 448. In some implementations, the data structure 440 can further include a type identifier 441, a note identifier 442, a note creation and / or modification time 444, and / or a note title 446. Time 444 may be represented by date (eg, including day, month, and year) and time (eg, including hour, minute, and second). Time 444 may further include a time zone identifier.

  In some implementations, data structure 440 may include one or more pointers 450 to a data set, which may also be referred to as an attached file. In one example, the attached file can be provided by any type of file, such as text, audio stream, video stream, still image, etc.

  In some embodiments, computer system 1000 may refer to the above in a relational database residing on one or more computers including one or more servers 110 and / or one or more client devices 130. Stored files and / or data structures. In some embodiments, computer system 1000 may use other methods of storing files and / or data structures that implement the data models described above, such as, for example, hierarchical databases or one or more flat files. can do.

  In some implementations, computer system 1000 can store a user directory associated with a calendar system in a directory server, such as a Lightweight Directory Access Protocol (LDAP) server. In some implementations, other methods of storing user directories, including, for example, native user directories provided by the operating system of server 110, can be used by computer system 1000.

  When receiving user interface commands, computer system 1000 may render one or more calendar items and / or notes on the client device via various views, including, for example, calendar views and notebook views.

  The calendar view can include one or more calendar items rendered on the screen with a visual reference to one or more time indicators. In one example, the calendar view 500 can include one or more weekly views 510, as schematically illustrated by FIG. 5a. The week view 510 may include up to seven visually distinct screen areas (day views 512) corresponding to the days of the week. Each day view may be visually divided into a plurality of screen areas 514 corresponding to the time of day. One or more time values can be placed in one day view. One or more calendar items 516 may be shown in day view 512. In another example, the calendar view 500 can include one or more monthly views 520, as schematically illustrated by FIG. 5b. The month view 520 can include multiple week views 510. The week view 510 may include up to seven visually distinct screen areas (day views 512) corresponding to the days of the week. Each day view may be visually divided into a plurality of screen areas 514 corresponding to the time of day. One or more time values can be placed in one day view. One or more calendar items 516 may be shown in day view 512. In further examples, the calendar view can include quarter views, year views, and / or other views.

  The notebook view can include one or more notes rendered on the screen. In one example, as schematically illustrated by FIG. 6a, one or more notes 610 rendered in the notebook view 600 can be sorted alphabetically by title / subject. In another example, one or more notes rendered in the notebook view 600 may be sorted chronologically by date of time of creation or modification of the notes, as schematically illustrated by FIG. 6b .

  In some implementations, computer system 1000 selects and / or sorts calendar events and notes by, for example, title, keywords, creator, and / or date of creation or modification of calendar events or notes. , One or more calendar events and one or more notes can be rendered in the mixed view.

  In some implementations, computer system 1000 can accept user input to edit existing calendar items or existing notes. In one example, in response to receiving a user input to edit a note, computer system 1000 can determine that the newly added text includes a time reference. After such a determination, computer system 1000 converts the note into a calendar entry, and together with zero or more optional fields, in the calendar entry data structure, as described in more detail hereinabove. The time identified by the time reference can be stored.

  FIG. 7 shows a flow diagram of an embodiment of a method 700 of file management by a mobile computing device. Method 700 includes hardware (eg, circuitry, dedicated logic, and / or programmable logic), software (eg, instructions executable on a computer system to perform hardware simulation), or a combination thereof. Can be implemented by a computer system. Method 700 and / or its respective functions, routines, subroutines, or operations may be performed by one or more physical processors of a computer system that performs the method. The multiple functions, routines, subroutines, or operations of method 700 may be performed in parallel or in an order that may be different than the order described above.

  Processing may begin at block 710 with the mobile computing device receiving a file via one or more input / output interfaces of the mobile computing device. In some implementations, the mobile computing device may be configured to acquire various types of files, and in one illustrative example, the mobile computing device is used to acquire still image files The mobile computing device may comprise a still image camera which may be used, and in another example the mobile computing device may comprise a video camera which may be used to acquire a video stream, and in a further example the mobile computing device It may comprise a microphone that may be used to acquire an audio stream, and in a further example, the mobile computing device may comprise a keyboard or touch screen that may be used to acquire a text file.

  At block 715, the mobile computing device can store the file in the mobile computing device's local memory. In one illustrative example, the mobile computing device 130 can store files in a local file system residing in a local non-volatile memory. In another example, the mobile computing device can store the file in a database residing in the local non-volatile memory.

  At block 720, the mobile computing device may send a copy of the file to one or more external computers (e.g., a file server executing a server-side portion of a file management application).

  At block 725, the mobile computing device may store a second file (also referred to as a "preview" file) derived from the first file in local memory. The size of the preview file may be smaller than the size of the first file. For image files, a preview file can be provided, for example, by a thumbnail image or other reduced size image or a reduced resolution image. For video files, a preview file can be provided, for example, by a "trailer" that includes a subset of the frames of the base video file. For audio files, preview files may be provided, for example, by one or more portions of a base audio file. For text files, a preview file can be provided by a summary, synopsis, or other description of a base text file. In some implementations, the mobile computing device can create the preview file locally. Alternatively, the mobile computing device can send the obtained file to an external server for processing, and can then receive the preview file from that external server.

  In response to determining at block 730 that the local memory is insufficient to perform the attempted memory write operation, processing may continue at block 735, otherwise the method. Can end. In some embodiments, the mobile computing device is in local memory (eg, one or more) to store files acquired by the mobile computing device via one or more input / output interfaces. Quotas can be allocated within the local file system of The mobile computing device is insufficient for the mobile computing device's available local memory to handle the attempted memory write operation (e.g. storage of newly acquired files in the local file system). There is a possibility to finally determine that there is.

  At block 735, the mobile computing device determines whether the third file has a fourth file associated therewith and the fourth file is derived from the third file. You can select a file. In order to complete the attempted memory write operation, the mobile computing device removes from the file system and thus a predefined selection to free the memory required to store the newly acquired file. Based on the criteria, one of the previously acquired files can be selected. In one illustrative example, the mobile computing device can select a file with a minimal number of file access operations associated with it. In another example, the mobile computing device can select the file that has not been accessed the longest. In a further example, the mobile computing device can select the file acquired most recently. In a further example, the mobile computing device can select a file that satisfies a plurality of conditions, such as, for example, the least recently accessed file created by a given date. In some implementations, the mobile computing device can select a file to be removed among files of the same type as the newly acquired file. Alternatively, the mobile computing device can select the file to be removed among the files having a size equal to or greater than the size of the newly acquired file. In some implementations, the mobile computing device can select multiple files to be removed that have a total size greater than or equal to the total size of newly acquired files.

  At block 740, the mobile computing device may remove the selected file from the local memory.

  At block 745, the mobile computing device can complete the attempted memory write operation.

  At block 750, the mobile computing device can receive a user interface command requesting to perform an operation on the third file.

  At block 755, the mobile computing device may retrieve a copy of the third file from the server where the file was previously stored. If the local file system does not have enough available space to accommodate the full size file retrieved from the server, the mobile computing device is as described in more detail hereinabove. One or more least accessed files or files least recently accessed may be selected and those files may be removed from the local file system. In response to the completion of the operation referenced by block 755, the method may end.

  FIG. 8 illustrates an example computer system 100 capable of executing instructions that cause a computer to perform one or more of the methods described herein. In some embodiments, computer system 100 may correspond to one or more servers 110 and / or client devices of FIG.

  In some embodiments, computer system 100 may be connected to other computer systems (eg, via a network such as a local area network (LAN), an intranet, an extranet, or the Internet). Computer system 100 may operate with the credentials of a server or client computer in a client-server environment, or as a peer computer in a peer-to-peer environment or a distributed network environment. The computer system 100 should be performed by a personal computer (PC), a tablet PC, a set top box (STB), a personal digital assistant (PDA), a cellular telephone, a web device, a server, a network router, a switch or bridge, or a device thereof. A set of instructions specifying an action may be provided (sequentially or otherwise) by any device.

  In further aspects, computer system 100 can communicate with one another via bus 1008, processor 1002, volatile memory 1004 (eg, random access memory (RAM)), non-volatile memory 1006 (eg, read only memory) (ROM) or electrically erasable programmable ROM (EEPROM), and secondary memory 1016 (eg, data storage device). Processor 1002 may implement a general purpose processor (eg, a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or any other type of instruction set Microprocessor, or a microprocessor that implements a combination of types of instruction sets, or a specialized processor (eg, application specific integrated circuit (ASIC), field programmable gate array (FPGA), digital signal processor (DSP), etc.) Or may be provided by one or more processors, such as a network processor or the like.

  Computer system 100 can further include a network interface device 1022. Computer system 100 may also include a video display unit 1010 (eg, LCD), an alphanumeric input device 1012 (eg, a keyboard), a pointing device 1014 (eg, a mouse), and an audio output device 1020 (eg, a speaker). it can.

  Secondary memory 1016 may include non-transitory computer readable storage medium 1024 on which the instructions of file management application 120, 125 may be stored. The instructions of file management application 120, 125 may also be completely or partially present in main memory 1004 and / or processor 1002 during their execution by computer system 1000, so that main memory 1004 and processor 1002 are also , Machine readable storage medium can be configured. Although computer readable storage medium 1024 is illustrated as a single medium in the illustrated embodiment, the term "computer readable storage medium" is a single medium that stores one or more sets of executable instructions. Or multiple media (eg, centralized or distributed databases, and / or associated caches and servers) must be included. The term "computer readable storage medium" refers to storing or encoding a set of instructions for computer execution causing the computer to perform any one or more of the methods described herein. It should also include all possible non-transitory media. The term "computer readable storage medium" should include, but is not limited to, solid state memory, optical media, and magnetic media.

  The methods, components, and features described herein may be implemented by discrete hardware components or be integral to the functionality of other hardware components such as ASICs, FPGAs, DSPs, or similar devices. Can be Further, the methods, components and features may be implemented by firmware modules or functional circuitry in a hardware device. Furthermore, the methods, components, and features may be implemented in any combination of hardware devices and software components, or in software only.

  Unless otherwise stated, terms such as "update", "identification", "determination", "delivery", "allocation", or the like are physical (electronic) quantities in the register and memory of the computer system. A computer that manipulates the data represented as and converts it into memory or registers of the computer system or other such information storage device, information transmission device, or other data similarly represented as physical quantities in the information display device Refers to the actions and processes performed or performed by the system.

  The embodiments described herein also relate to an apparatus for performing the method described herein. The apparatus may be specifically configured for the required purpose or may include a general purpose computer system selectively programmed by a computer program stored in the computer system. Such computer programs can be stored in computer readable non-transitory storage media.

  The methods and illustrative examples described herein are not inherently related to any particular computer or other apparatus. Various general purpose systems can be used in accordance with the teachings described herein, or more specialized devices configured to perform the functions, routines, subroutines, or operations of the required methods. It may be more convenient to do. The required structure of various of these systems looks like that given in the above description.

  The above description is intended to be illustrative rather than restrictive. Although the present disclosure has been described with reference to particular illustrative examples and embodiments, it is recognized that the present disclosure is not limited to the described embodiments. The scope of the present disclosure should be determined by reference to the following claims, along with the full scope of equivalents to which the claims are entitled.

100 computer systems
110 server
115 Multiple interconnected networks
120 server side part
125 Client side part
130 Client computer, client device, mobile computing device
200 data structure
210 File Identifier
212 File creation time stamp
214 File access time stamp
216 Total number of file access operations
310 Local File System
312 preview file
312-1 preview file
312-2 preview file
314 Base File
314-1 Base file
316 Predefined Quotas
318 newly acquired files
410 Data Structure
411 type identifier
412 identifier
414 time
416 Calendar Item Title
418 Description
420 positions
422 Event originator identifier
List of participants in 424 events
426 Recurring schedule
428 pointer
440 Data Structure
441 Type Identifier
442 memo identifier
444 Time of memo creation and / or modification
446 Note title
448 memo text
450 pointer
500 calendar views
510 weeks view
512 day view
514 screen area
516 Calendar items
520 Month View
600 notebook views
610 Notes
700 ways
1,000 computer system
1002 processor
1004 volatile memory
1006 Non-volatile memory
1008 bus
1010 video display unit
1012 Alphanumeric input device
1014 pointing device
1016 Secondary memory
1020 audio output device
1022 Network Interface Device
1024 non-transitory computer readable storage medium

Claims (20)

Storing the plurality of image files in a memory by the computer system;
Storing, in the memory, a plurality of preview files, each corresponding to an image file of the plurality of image files;
Determining that the memory is insufficient to perform a memory write operation;
Selecting an image file among the plurality of image files;
Removing a preview file associated with the selected image file from the memory.   The method of claim 1, further comprising performing the memory write operation.   The method of claim 1, wherein the first file is provided by one of a still image file, a video file, an audio file, or a document file.   The method of claim 1, wherein a second file is provided by one of a preview of a first file, at least a portion of the first file, or a description of the first file.   The step of selecting the third file may be one of the steps of selecting the most recently acquired file, selecting the least accessed file, or selecting the least recently accessed file. The method of claim 1, comprising:   The method of claim 1, wherein selecting a third file comprises selecting a file having a size greater than or equal to the size of memory required to perform the memory write operation.   The method of claim 1, wherein selecting the third file comprises selecting a plurality of files.   The method of claim 1, further comprising receiving the first file via one of a still image camera, a video camera, a microphone, or a network interface. Receiving a user interface command to perform a file operation on the third file;
The method of claim 1, further comprising: retrieving a copy of the third file via a communication interface.   9. The method of claim 8, wherein the file operation comprises one of displaying a third file or playing the third file.   The method of claim 1, wherein the memory write operation is requested by a user interface command.   The method of claim 1, wherein the memory write operation is represented by storing a fifth file received by the computer system in the memory.   The method according to claim 11, wherein the fifth file is provided by one of a still image file, a video file, an audio file, or a document file.   The method according to claim 11, wherein storing the second file comprises receiving the second file via a communication interface in response to transmitting the first file to an external computer.   The method of claim 11, further comprising receiving the first file via an input / output interface.   The method of claim 11, further comprising transmitting the first file to an external computer. With memory
A processor coupled to the memory;
Storing a first file having a first size in the memory;
A second file derived from the first file is stored in the memory, the second file having a second size, the second size being greater than the first size small,
Determining that the memory is insufficient to perform a memory write operation;
Selecting a third file associated with a fourth file, the fourth file being derived from the third file,
A processor configured to remove the third file from the memory.   The system of claim 16, wherein the processor is further configured to receive the first file via an input / output interface.   17. The system of claim 16, wherein the processor is further configured to send the first file to an external computer. Said computer system when executed by the computer system
Storing a first file having a first size in memory;
A second file derived from the first file is stored in the memory, the second file having a second size, the second size being greater than the first size. small,
Causing the memory to be determined to be insufficient to perform a memory write operation;
Selecting a third file associated with a fourth file, the fourth file being derived from the third file,
A computer readable non-transitory storage medium comprising executable instructions for causing the third file to be removed from the memory.