JP6835799B2 - File management systems and methods with mobile computing devices - Google Patents

Description

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

Mobile computing devices may have multiple input / output (I / O) interfaces and / or peripheral devices such as still image cameras, video cameras, and / or microphones. Files acquired 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-A-2002-209131 JP-A-2007-323378 Japanese Unexamined Patent Publication No. 2003-8508 Japanese Unexamined Patent Publication No. 2011-257990 Japanese Unexamined Patent Publication No. 2006-60630

The present disclosure is illustrated by example rather than by limitation and may be better understood by reference to the detailed description below when considered in connection with the drawings.

FIG. 5 is a network level diagram illustrating one exemplary embodiment of a mobile computing device that performs file management, according to one or more aspects of the disclosure. FIG. 5 schematically illustrates a data structure that tracks access to a file stored on a mobile computing device, according to one or more aspects of the disclosure. It is a figure which shows typically the example of the file management method by one or more aspects of this disclosure. It is a diagram schematically showing a plurality of data structures supported by a computer system running a calendar application according to one or more aspects of the present disclosure. FIG. 5 schematically illustrates an example of a calendar view rendered by a computer system running a calendar application, according to one or more aspects of the present disclosure. FIG. 5 schematically illustrates an example of a calendar view rendered by a computer system running a calendar application, according to one or more aspects of the present disclosure. It is a diagram schematically showing an example of a notebook view rendered by a computer system running a calendar application according to one or more aspects of the present disclosure. It is a diagram schematically showing an example of a notebook view rendered by a computer system running a calendar application according to one or more aspects of the present disclosure. It is a flow chart which shows the file management method by one or more aspects of this disclosure. It is a block diagram which shows the exemplary computer system which operates according to the example of this disclosure.

Described herein are file management methods and systems by mobile computing devices. "Mobile computing device" as used herein refers 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 desktop computers.
Mobile computing devices can enter information through a variety of interfaces, including, for example, keyboards, touch screens, network interfaces, microphones, camcorders, still image cameras, and / or microphones. Such mobile computing devices may be capable of inputting still image files, video stream files, audio stream files, and / or document files (eg, text files).

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

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

The mobile computing device can also attempt a memory write operation (eg, storage of newly acquired image files in the local file system). If the space available within the mobile computing device's local file system is insufficient to allow the attempted memory write operation to complete, the mobile computing device is removed from the local file system. And therefore, one or more previously acquired files can be selected to free up space needed to store the newly acquired files. In one exemplary example, a mobile computing device can remove the least accessed file by the number of file access operations. In another example, a mobile computing device can remove the least recently accessed files. In a further example, the mobile computing device can remove the most recently acquired files.

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

Therefore, the mobile computing device can store at least some preview files of the files acquired by the mobile computing device, and can further accommodate the full size file within the file system of the mobile computing device. To the extent, you can store the full size version of a file for a subset of the acquired files. Full-size files may be removed from the file system to accommodate newly acquired files, and preview files may be presented to the user in response to user interface commands. The full size file can be retrieved from the file server in response to receiving a user interface command that explicitly targets the full size file.

In some embodiments, the file management methods described above may be implemented to facilitate the processing of file attachments by the calendar application performed by the mobile computing device. "Calendar application" as used herein refers 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 mentioned above are described in detail below herein by way of example, not by limitation.

FIG. 1 shows a network-level diagram of one exemplary embodiment of computer system 1000, according to one or more aspects of the present disclosure. The computer system 1000 can include one or more servers 110 running the server-side portion 120 of a file management application (eg, a calendar application). One or more client computers 130 running the client-side portion 125 of the file management application can be connected to the server computer 110 through multiple interconnected networks 115.

"Computer" as used herein refers to a device that includes a processor, memory, and at least one I / O interface. A computer can be represented by, for example, a server, a virtual machine running on a host computer system, a portable personal computer (PC) or a desktop personal computer (PC), a tablet computer, or a smartphone. In addition, the term "computer" is the entire set of computers that execute a set of instructions (or a set) individually or jointly 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 a plurality of computers. The network can be represented by, for example, a local area network (LAN), a wide area network (WAN), or a virtual private network (VPN). In some embodiments, the plurality of interconnected networks 115 can include the Internet.

The functions of the computer system 1000 can be delivered to the end user via one or more client devices 130, such as a portable personal computer (PC) or desktop personal computer (PC), tablet computer, or smartphone. In one example, one or more client devices 130 provide user interface functionality and communicate with one or more servers 110, which server 110 handles client requests, load balancing, client authentication, authorization, and files. Can perform memory and search, billing, and other functions. The above and other functions can be distributed among one or more servers 110 existing in one or more physical facilities.

In another example, at least some of the server-side features listed above can be performed by one or more client devices 130. In some embodiments, the client device 130 can perform at least a subset of its functionality while not connected to the server 110. This processing mode is also called an offline client operation mode.

Some of the features listed above, such as client request processing, load balancing, client authentication, authorization, file storage and retrieval, and / or billing, may be said to be related to server-side functionality. Other features, such as accepting user input, retrieving files through one or more communication interfaces, and / or rendering information on the display, may be said to be related to client-side functionality. However, in some embodiments, the computer system 1000 performs at least some of the server-side functionality associated with server-side functionality and at least some of the functionality associated with client-side functionality. May include a computer. Therefore, the specification of client-side functionality and server-side functionality that may be mentioned herein is for illustration purposes and has nothing to do with the operation of the components of computer system 1000. Intended.

In some embodiments, the computer system 1000 can be configured to acquire different types of files via one or more communication interfaces of the mobile computing device 130. In one exemplary example, the mobile computing device 130 can include a still image camera that can be used to acquire still image files. In another example, the mobile computing device 130 can include a video camera that can be used to capture a video stream. In a further example, the mobile computing device 130 can include a microphone that can be used to capture an audio stream. In a further example, the mobile computing device 130 can include a keyboard or touch screen that can be used to acquire text files.

In response to the acquisition of the file, the mobile computing device 130 can store the file in the local memory of the mobile computing device. In one exemplary example, the mobile computing device 130 can store files in a local file system that resides in local non-volatile memory. In another example, the mobile computing device 130 can store files in a database that resides in local non-volatile memory.

In response to further file acquisition, the mobile computing device 130 may send a copy of the file to one or more servers 110 running 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 the appropriate architecture.

In response to further 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 the size of the base file. The preview file is intended to act on behalf of the base file for rendering the base file on the screen of the mobile computing device, unless the user specifically requires that the base file be displayed instead of the preview file. The computing device may display one or more preview files corresponding to the file requested by the user in response to receiving a user interface command to display one or more files.

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

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

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

The mobile computing device 130 is in local memory (for example, in one or more local file systems) to store files acquired by the mobile computing device via one or more I / O interfaces. ) Quotas can be allocated. The mobile computing device 130 is insufficient for the available local memory of the mobile computing device to handle attempted memory write operations (eg, storage of newly acquired files in the local file system). There is a possibility that it will be finally determined to be. To complete the attempted memory write operation, the mobile computing device 130 is required to remove from the file system and therefore store the newly acquired file based on predefined selection criteria. You can choose one of the previously acquired files to free up memory.

In one exemplary example, the mobile computing device is in the local memory of the mobile computing device to select a file with the minimum number of file access actions associated with it, based on a total of 216 file access actions. An array of data structures 200 can be analyzed for multiple files stored in. In another example, the mobile computing device has data about multiple files stored in the mobile computing device's local memory in order to select the least 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 has a data structure for multiple files stored in the mobile computing device's local memory in order to select the most previously acquired file based on the file creation timestamp 212. 200 sequences can be analyzed. In a further example, the mobile computing device is in the local memory of the mobile computing device to select files that meet multiple criteria, for example, the least accessed file created by a given date. An array of data structures 200 can be analyzed for multiple stored files.

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

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

Mobile computing devices may eventually receive user interface commands that require them to perform actions on files that were previously removed from local memory. The mobile computing device then presents the corresponding preview file and / or receives the base file from the server where the file was previously stored in response to receiving a user interface command that explicitly targets the base file. Can be taken out. If the local file system does not have enough available space to accommodate the full-size files retrieved from the server, the mobile computing device will be described in more detail above herein. You can select one or more of the least accessed files or the least accessed files and remove those files from your local file system.

Therefore, as outlined by FIG. 3, the mobile computing device 130 is in local memory (eg, local file system 310) at least some of the files 314 acquired by the mobile computing device. The preview file 312 can be stored. The mobile computing device can also store at least some full size versions of file 314, as long as the full size file can be accommodated in the mobile computing device's local memory. In one exemplary example, a mobile computing device can store multiple preview files 312 corresponding to base file 314 within a predefined quota 316 within the local file system 310. The mobile computing device also does not allow the base file corresponding to the preview file 312-2 to fit in the predefined quota 316 in the local file system 310 within the predefined quota 316 in the local file system 310. It is possible to store multiple preview files 312-2 that do not have a base file to do.

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

In some embodiments, the computer system 1000 can run a calendar application that facilitates scheduling and tracking of events for individual users and / or groups of users. Users can access the calendar application through a variety of client devices, including the mobile computing device 130.

In one example, the computer system 1000 can support a data model that includes calendar items and notes, as outlined by FIG. The calendar item can be represented by a data structure 410 containing an identifier 412 and a time 414. In some embodiments, the identifier 412 can be provided by a human-readable sequence of alphanumeric characters that includes the title and / or description of the calendar item. In the alternative, the calendar item identifier can be provided by an alphanumeric or non-alphanumeric identifier that is not intended to be human readable.

In some embodiments, time 414 can be represented by the start time of the event identified by the calendar item and the duration of the event. In the alternative, time 414 can be represented by the start and end times of the event. The start and / or end times of an event can be represented by dates (including, for example, days, months, and years) and times (including, for example, hours, minutes, and seconds). Time 414 may further include a time zone identifier.

Data structure 410 includes calendar item title 416, description 418, location 420, event originator identifier 422 identified by the calendar item, event participant list 424, recurrence schedule 426, and / or other fields. Further can be included. In some embodiments, the data structure 410 can include a calendar item type identifier 411. Examples of calendar items represented by data structure 410 can include visit appointments, meeting requests, reminders, and so on. In some embodiments, the data structure 410 may include one or more pointers 428 to a dataset, sometimes referred to as an attachment. In one example, the attachment can be provided by any type of file, such as text, audio stream, video stream, still image, and so on.

A memo can be represented by a data structure 440 containing memo text 448. In some embodiments, the data structure 440 may further include a type identifier 441, a memo identifier 442, a memo creation and / or modification time 444, and / or a memo title 446. Time 444 can be represented by a date (including, for example, days, months, and years) and a time (including, for example, hours, minutes, and seconds). Time 444 may further include a time zone identifier.

In some embodiments, the data structure 440 can include one or more pointers 450 to a dataset, sometimes referred to as an attachment. In one example, the attachment can be provided by any type of file, such as text, audio stream, video stream, still image, and so on.

In some embodiments, computer system 1000 is mentioned above within a relational database that resides on one or more computers, including one or more servers 110 and / or one or more client devices 130. Can store files and / or data structures. In some embodiments, the computer system 1000 uses other methods of storing files and / or data structures that implement the data model described above, such as hierarchical databases, or one or more flat files. can do.

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

Upon receiving a user interface command, the computer system 1000 can render one or more calendar items and / or notes on the client device through various views, including, for example, calendar and notebook views.

The calendar view can contain one or more calendar items that are 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 shown by FIG. 5a. Week view 510 can include up to seven visually separate screen areas (day view 512) corresponding to the day of the week. Each day view can be visually divided into multiple screen areas 514 corresponding to the time. You can place one or more time values in one day view. One or more calendar items 516 can be shown in day view 512. In another example, the calendar view 500 can include one or more month views 520, as outlined by FIG. 5b. The month view 520 can include a plurality of week views 510. Week view 510 can include up to seven visually separate screen areas (day view 512) corresponding to the day of the week. Each day view can be visually divided into multiple screen areas 514 corresponding to the time. You can place one or more time values in one day view. One or more calendar items 516 can be shown in day view 512. In a further example, the calendar view can include a quarter view, a year view, and / or other views.

The notebook view can contain one or more notes rendered on the screen. In one example, one or more notes 610 rendered within Notebook View 600 can be sorted alphabetically by title / subject, as outlined by FIG. 6a. In another example, one or more notes rendered within Notebook View 600 can be sorted chronologically by date at the time the note was created or modified, as outlined in Figure 6b. ..

In some embodiments, the computer system 1000 selects and / or sorts calendar events and notes by, for example, title, keyword, author, and / or date and time of creation or modification of the calendar event or memo. , One or more calendar events and one or more notes can be rendered in a mixed view.

In some embodiments, the computer system 1000 can accept user input to edit existing calendar items or existing notes. In one example, in response to accepting user input to edit a memo, the computer system 1000 can determine that the newly added text contains a time reference. After such a determination, as described in more detail above herein, the computer system 1000 converts the memo into a calendar item and into the calendar item data structure, along with zero or more optional fields. The time identified by the time reference can be stored.

FIG. 7 shows a flow chart of an embodiment of the file management method 700 by the mobile computing device. Method 700 includes hardware (eg, network, dedicated logic, and / or programmable logic), software (eg, instructions that can be executed on a computer system to perform hardware simulation), or a combination thereof. It can be run by a computer system that can. Method 700 and / or its individual functions, routines, subroutines, or actions can be performed by one or more physical processors in a computer system that performs this method. Multiple functions, routines, subroutines, or actions of Method 700 can be executed in parallel or in an order that may differ from the order described above.

Processing may be initiated at block 710 by the mobile computing device receiving a file through one or more I / O interfaces of the mobile computing device. In some embodiments, the mobile computing device may be configured to acquire different types of files, and in one exemplary example, the mobile computing device is used to acquire a still image file. Can be equipped with a still image camera, in another example, a mobile computing device can be equipped with a video camera that can be used to capture a video stream, and in a further example, a mobile computing device. It can be equipped with a microphone that can be used to capture the audio stream, and in a further example, the mobile computing device can be equipped with a keyboard or touch screen that can be used to capture the text file.

Block 715 allows the mobile computing device to store files in the mobile computing device's local memory. In one exemplary example, the mobile computing device 130 can store files in a local file system that resides in local non-volatile memory. In another example, a mobile computing device can store files in a database that resides in local non-volatile memory.

Block 720 allows mobile computing devices to send a copy of a file to one or more external computers (eg, a file server that runs the server-side portion of a file management application).

Block 725 allows the mobile computing device to 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 can be smaller than the size of the first file. For image files, a preview file can be provided, for example, as a thumbnail image or other reduced size image or reduced resolution image. For video files, preview files can be provided, for example, by a "trailer" that contains a subset of the frames of the base video file. For audio files, a preview file can be provided, for example, by one or more parts of the base audio file. For text files, a preview file can be provided by summary, abstract, or other description of the base text file. In some embodiments, the mobile computing device can create a preview file locally. In the alternative, the mobile computing device can send the acquired file to an external server for processing and then receive a preview file from that external server.

In response to the determination at block 730 that local memory is insufficient to perform the attempted memory write operation, processing can continue at block 735, otherwise this method Can be terminated. In some embodiments, the mobile computing device is in local memory (eg, one or more) to store the files acquired by the mobile computing device via one or more input / output interfaces. Quotas can be allocated (within the local file system of). For mobile computing devices, the available local memory of the mobile computing device is insufficient to handle attempted memory write operations (eg, storage of newly acquired files within the local file system). There is a possibility that it will be finally determined to be present.

In block 735, the mobile computing device has a third file so that the third file has a fourth file associated with it and the fourth file is derived from the third file. You can select the file. To complete the attempted memory write operation, the mobile computing device removes it from the file system and thus frees the memory needed to store the newly acquired file, a predefined choice. Based on the criteria, you can select one of the previously acquired files. In one exemplary example, a mobile computing device can select a file that has the minimum number of file access actions associated with it. In another example, the mobile computing device can select the file that has not been accessed for the longest time. In a further example, the mobile computing device can select the earliest acquired file. In a further example, the mobile computing device can select files that satisfy multiple criteria, for example, the least accessed files created by a given date. In some embodiments, the mobile computing device can select the file to be removed among the files of the same type as the newly acquired file. In the alternative, the mobile computing device can select the file to be removed among the files that are larger than the size of the newly acquired file. In some embodiments, 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 the newly acquired files.

Block 740 allows mobile computing devices to remove selected files from local memory.

At block 745, the mobile computing device is able to complete the attempted memory write operation.

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

Block 755 allows the mobile computing device to 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 files retrieved from the server, the mobile computing device will be described in more detail above herein. You can select one or more of the least accessed files or the least accessed files and remove those files from your local file system. This method can be terminated in response to the completion of the operation referenced by block 755.

FIG. 8 shows an example computer system 100 capable of executing an instruction that causes a computer to execute one or more of the methods described herein. In some embodiments, the computer system 100 can accommodate one or more servers 110 and / or client devices in FIG.

In some embodiments, the computer system 100 can be connected to another computer system (eg, via a network such as a local area network (LAN), an intranet, an extranet, or the Internet). Computer system 100 can operate as a server or client computer in a client-server environment, or as a peer computer in a peer-to-peer or distributed network environment. Computer system 100 should be performed by personal computers (PCs), tablet PCs, set-top boxes (STBs), personal digital assistants (PDAs), cellular phones, web devices, servers, network routers, switches or bridges, or their devices. It can be provided by any device (sequentially or otherwise) capable of executing a set of instructions that specify the action.

In a further aspect, the computer system 100 can communicate with each other 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) can be included. Processor 1002 implements general purpose processors (eg, compound instruction set computing (CISC) microprocessors, reduced instruction set computing (RISC) microprocessors, ultralong instruction word (VLIW) microprocessors, and other types of instruction sets. Microprocessors, or microprocessors that perform a combination of instruction set types) or specialized processors (eg, application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), Or it can be provided by one or more processors such as network processors).

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

The secondary memory 1016 may include a non-temporary computer-readable storage medium 1024 on which the instructions of the file management applications 120, 125 can be stored. Instructions for file management applications 120, 125 can also be present entirely or partially within main memory 1004 and / or processor 1002 during its execution by computer system 1000, and thus also main memory 1004 and processor 1002. , A machine-readable storage medium can be constructed. Although the 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 it must contain multiple media (eg, centralized or distributed databases, and / or associated caches and servers). The term "computer-readable storage medium" is used to store or encode a set of instructions for computer execution that causes a computer to perform any one or more of the methods described herein. It must also include all possible non-temporary media. The term "computer-readable storage medium" must include, but is not limited to, solid state memory, optical media, and magnetic media.

The methods, components, and features described herein can be implemented by discrete hardware components or integrated with the functionality of other hardware components such as ASICs, FPGAs, DSPs, or similar devices. Can be transformed into. In addition, methods, components, and features can be implemented by firmware modules or functional networks within hardware devices. In addition, methods, components, and features can be implemented in any combination of hardware devices and software components, or in software alone.

Otherwise, unless otherwise stated, terms such as "update," "identify," "judgment," "send," "allocation," or analog are the physical (electronic) quantities in computer system registers and memory. A computer that manipulates the data represented as and converts it into the memory or registers of a computer system or other data that is also represented as a physical quantity in a computer system's memory or register or other such information storage device, information transmission device, or information display device. Refers to actions and processes performed or performed by the system.

The embodiments described herein also relate to devices that perform the methods described herein. The device may be specifically configured for the required purpose, or may include a general purpose computer system selectively programmed by a computer program stored within the computer system. Such computer programs can be stored in computer-readable non-temporary storage media.

The methods and exemplary examples described herein are not unique to any particular computer or other device. A variety of general purpose systems can be used according to the teachings described herein, or configure more specialized equipment to perform functions, routines, subroutines, or operations in the required manner. It may be more convenient to do. The required structure of the various these systems looks like those shown in the discussion above.

The above description is intended to be exemplary rather than restrictive. Although the present disclosure has been described with reference to specific exemplary examples and embodiments, it is acknowledged that the present disclosure is not limited to the described embodiments. The scope of the present disclosure shall be determined by reference to the following claims, along with the full scope of the equivalents for which the claims are eligible.

100 computer system
110 server
115 Multiple interconnected networks
120 Server-side part
125 Client side part
130 Client computers, client devices, mobile computing devices
200 data structure
210 File identifier
212 File creation time stamp
214 File access timestamp
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 quota
318 Newly acquired files
410 data structure
411 Type identifier
412 Identifier
414 time
416 Calendar item title
418 Description
420 position
422 Event Founder Identifier
424 List of participants in the event
426 Schedule for recurrence
428 pointer
440 data structure
441 Type identifier
442 Memo identifier
444 Time to create and / or modify notes
446 Memo title
448 Memo text
450 pointer
500 calendar view
510 week view
512 day view
514 screen area
516 Calendar items
5 May view
600 notebook view
610 memo
700 methods
1000 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-temporary computer-readable storage medium

Claims (17)

A step of storing multiple base files in the local memory of the computer system by the computer system,
A step to make the remote server store copies of the multiple base files,
Each of the plurality of base files is a step of storing a plurality of preview files derived from the corresponding base files in the local memory, and the size of each preview file is the size of the corresponding base file. Smaller, each preview file is one of a subset of the frames of the base file for a video file, one or more parts of the base file for an audio file, and a summary or summary for a text file. The steps to remember and provided by
In response to the determination that the predefined memory quotas in the local memory have been exceeded by the plurality of base files and the plurality of preview files.
A step of selecting the first base file among the plurality of base files whose copy is stored by the remote server, and
The step of removing the first base file from the local memory and
The steps to perform the memory write operation and
A step of presenting a preview file corresponding to the first base file in response to receiving a first user interface command requesting the first base file.
Sufficient use of the local memory to accommodate the full-size file in response to receiving a second user interface command that explicitly requests the full-size file corresponding to the first base file. If you do not have a possible space
A step of selecting a second base file from the plurality of base files, and
The step of removing the second base file from the local memory and
A method comprising retrieving a copy of the first base file from the remote server. The method of claim 1, wherein each base file is provided by one of a still image file, a video file, an audio file, or a document file. The step of selecting the first base file is one of the steps of selecting the earliest acquired file, the least accessed file, or the longest inaccessible file. The method of claim 1, comprising one. The method of claim 1, wherein the step of selecting the first base file comprises selecting a file having a size equal to or greater than the size of the memory required to perform the memory write operation. The method according to claim 1, wherein the step of selecting the first base file includes a step of selecting a plurality of files. The method of claim 1, further comprising the step of receiving the plurality of base files via one of a still image camera, a video camera, a microphone, or a network interface. The method according to claim 1, wherein the memory write operation is required by a user interface command. The method of claim 1, wherein the memory write operation is represented by storing a newly acquired base file received by the computer system in the local memory. The method of claim 8, wherein the newly acquired base 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 the step of storing each preview file comprises receiving the preview file via a communication interface in response to sending the corresponding base file to an external computer. The method of claim 8, further comprising receiving the newly acquired base file via an input / output interface. 8. The method of claim 8, further comprising sending the newly acquired base file to an external computer. With memory
A processor coupled to the memory
A plurality of base files are stored in the memory,
Make the remote server remember multiple copies of the base file
In the memory, a plurality of preview files, each derived from the corresponding base file of the plurality of base files, are stored, and the size of each preview file is smaller than the size of the corresponding base file, and each preview The file is provided by one of a subset of the frames of the base file for a video file, one or more parts of the base file for an audio file, and a summary or abstract for a text file.
In response to the determination that the predefined memory quota in memory has been exceeded by the plurality of base files and the plurality of preview files.
Select the first base file of the plurality of base files whose copy is stored by the remote server.
Remove the first base file from the memory and
Execute memory write operation,
In response to receiving a first user interface command requesting the first base file, a preview file corresponding to the first base file is presented.
The memory is sufficiently available to accommodate the full size file in response to receiving a second user interface command that explicitly requests the full size file corresponding to the first base file. If you do not have space
Select the second base file from the plurality of base files and select
Remove the second base file from local memory and
A system that includes a processor that is configured to retrieve a copy of the first base file from the remote server. 13. The system of claim 13, wherein the processor is further configured to receive a base file of the plurality of base files via an input / output interface. 13. The system of claim 13, wherein the processor is further configured to transmit a base file of the plurality of base files to an external computer. When executed by a computer system, the computer system,
Store multiple base files in memory,
Have the remote server remember multiple copies of the base file
A plurality of preview files, each derived from a corresponding base file among the plurality of base files, are stored in the memory, and the size of each preview file is smaller than the size of the corresponding base file, and each preview The file is provided by one of a subset of the frames of the base file for a video file, one or more parts of the base file for an audio file, and a summary or abstract for a text file.
In response to the determination that the predefined memory quota in memory has been exceeded by the plurality of base files and the plurality of preview files.
The first base file among the plurality of base files whose copy is stored by the remote server is selected.
The first base file is removed from the memory and
Execute memory write operation,
In response to receiving the first user interface command requesting the first base file, the preview file corresponding to the first base file is presented.
The memory is sufficiently available to accommodate the full size file in response to receiving a second user interface command that explicitly requests the full size file corresponding to the first base file. If you do not have space
Select the second base file from the plurality of base files,
Remove the second base file from local memory
A computer-readable non-temporary storage medium containing an executable instruction that causes a copy of the first base file to be retrieved from the remote server. The executable instruction that causes the computer system to store each preview file is an executable instruction that causes the computer system to receive the preview file via a communication interface in response to transmitting the corresponding base file to an external computer. The computer-readable non-temporary storage medium of claim 16, further comprising.