JP2012104150A - Customizing space in network environment - Google Patents

Abstract

PROBLEM TO BE SOLVED: To allow each of different users, in the case where a PC is shared by the users, to store fundamental personal settings in a user account of the PC.SOLUTION: A model client platform produces a file image including an increment file stored in a first model block of a model storage device, produces a file description image including a file description stored in a second model block of the model storage device, and uploads the file image and the file description image to a server connected with the model client platform. The file description includes a position of the first model block in the model storage device. A normal client platform produces a normal block bitmap indicating the situation of using each of normal blocks in a normal storage device of the normal client platform, and receives a file description image from a server connected with the normal client platform.

Description

  The ability to customize a computer is an important feature of the platform. In general, customization includes changing computer settings to suit a particular user. For example, a personal computer (PC) can be customized by changing the background image, choosing a text font, or operating system color scheme. If the PC is shared by different users, the individual users can store their basic personal settings in the PC's user account. You can then access those settings by logging in.

  The invention described herein is illustrated in the accompanying drawings, but is not intended to be limiting. For simplicity and clarity of illustration, components shown in the drawings are not necessarily drawn to scale. For example, the dimensions of some components may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals are repeated throughout the drawings to indicate corresponding or analogous elements.

1 illustrates one embodiment of a network environment having a server platform and a plurality of client platforms connected to the server platform.

An example of the structure of the normal client platform in a network environment, a model client platform, and a server platform is shown.

1 illustrates one embodiment of a storage device that is divided into a plurality of blocks.

Fig. 4 illustrates an embodiment of an incremental file image and an incremental file description image.

Fig. 4 illustrates one embodiment of a model block bitmap generated by a model client platform.

FIG. 4 illustrates one embodiment of a regular block bitmap generated by a regular client platform.

Fig. 4 illustrates one embodiment of a method for installing a model client platform.

Fig. 4 illustrates an embodiment for initializing a normal client platform.

Fig. 4 illustrates an embodiment for processing an I / O request in a normal client platform.

FIG. 6 illustrates one embodiment of saving storage space for a client of a client platform in a network environment. FIG.

1 illustrates one embodiment of a general platform.

  A technique for customizing a space in a network environment is described below. In the following description, a logical implementation, pseudocode, means for identifying operands, resource partitioning / sharing / duplication implementation, system component types and interrelationships, and logical partitioning to further enhance a full understanding of the present invention A number of specific details are described, such as the choice of integration. However, the present invention may be practiced without such specific details. In other instances, control structures, gate level circuits, and complete software instruction sequences have not been shown in detail in order to avoid obscuring the present invention. Those skilled in the art who have read the description will be able to implement appropriate functions without having to repeat experiments.

  As used herein, "one embodiment", "one embodiment", "one example", etc., although the described embodiment may include a particular feature, structure, or characteristic, is not necessarily that particular feature , Structure or property may not be included. Moreover, such phrases are not necessarily referring to the same embodiment. In addition, if a particular feature, structure, or characteristic is described in connection with one embodiment, is it also explicitly stated in such feature, structure, or characteristic in relation to the other embodiment It will be apparent to those skilled in the art whether it is effective or not.

  Embodiments of the invention may be implemented in hardware, firmware, software, or any combination thereof. Embodiments of the invention may also be implemented as instructions stored on a machine-readable medium, which may be read and executed by one or more processors. A machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (such as a computer). For example, a machine readable medium may be a ROM (Read Only Memory), a RAM (Random Access Memory), a magnetic storage device storage medium, an optical storage medium, a flash memory device, an electrical, optical, acoustic, or other form of propagated signal Others (eg, carrier wave, infrared signal, digital signal, etc.) may be included.

An embodiment of a network environment 10 is shown in FIG. The network environment 10 includes a server platform 12 and a plurality of client platforms 11 _{1 to} 11 _N connected to the server platform 12 via a network 13 such as Ethernet (registered trademark), Fiber Channel, or other communication link. You can do it. In this embodiment, the network environment 10 may have any number of client platforms and server platforms.

The network environment 10 may provide different content to different groups of clients to meet their customized requirements. For example, young students may need educational content and adults may prefer entertainment content. To meet these needs, the client platform 11 ₁ -11 _N are operating systems, and, or, the base software image including based software application that runs on an operating system, and / or, perhaps even other software image installation Can be done.

One client platform (such as client platform 11 _1), the base file may be selected as a model client platform that good incremental software image I different is installed. For example, the incremental file may include a program (such as educational content) that may provide customized services to a particular group of clients (such as young students). In other examples, the incremental file may be an updated version of the base file. The model client platform can then generate an incremental package that includes the incremental software images and their descriptive information uploaded to the server. The incremental package may further include a block description that describes the block that stores the incremental software image. In one embodiment, the block description may include the location of the block in the model platform storage.

  The model client platform may further generate information indicating whether incremental software images stored in the storage device block are available from the server and upload the information to the server 12. In one embodiment, the information may be a model block bitmap that indicates the usage of each block of the model client platform storage.

The above configuration can realize a normal client platform (client platform 11 ₂ ) in the network environment 10. The client platform does not have the incremental software image installed in advance, and provides customized content to the group of clients by downloading the incremental software image from the server in response to a request from the client.

One embodiment of the structure of a model client platform (eg, client platform 11 ₁ ), normal client platform (eg, client platform 11 ₂ ), and server platform 12 in network environment 10 is shown in FIG.

As shown, the model client platform (e.g., client platform 11 ₁ ) includes a hardware machine 20, a firmware 21 that runs on the hardware machine 20, an operating system 22, and an application 23. Software images that operate.

  The hardware machine 20 may further include one or more processors 201, a memory 202, a storage device 203, a network interface 204, and the like. The storage device 203 can include an internal storage device (such as a hard disk) within the client platform and an external storage device (floppy (registered trademark) disk, optical disk, etc.) external to the client platform. In the present embodiment, the storage device 203 may be divided into a plurality of blocks for data storage.

  The firmware 21 stores a BIOS (bios) routine 210 executed by the platform during system startup, and an EFI (extended firmware interface) routine 211 serving as an interface between the firmware 21 and the operating system 22. A standard environment for booting can be provided. The operating system 22 can control tasks performed by the client platform, manage system resources, and optimize performance. The operating system 22 may perform basic tasks such as keeping file and dictionary tracks in the storage device 203.

  In this embodiment, there can be two types of files: a base file and an incremental file. The base file may include programs for the operating system 22 and / or programs for basic applications such as database programs, word processors, spreadsheets, and the like. The incremental file may be different from the base file. For example, the incremental file may include a program designed for a group of clients, such as an educational program for young students or a game for adults. The operating system 22 receives a call from the application 23, reads / writes a file to / from the storage device 203, a file system 221 that organizes a track of the file and holds the file in the storage device 203, and A driver 222 for inputting / outputting a file from / to the storage device 203 may be included. The driver 222 may further include a storage device protection (SUP) driver 2220 to prevent the storage device base file from being destroyed.

  The application 23 may include a software program that runs within a software platform provided by the operating system 22 and provides a user interface 230 for user interaction.

A typical client platform (e.g., client platform 11 ₂ ) is a hardware machine 24, firmware 25 that runs on the hardware machine 24, and a software image that runs on the firmware 25, including an operating system 26 and applications 27. Can be included.

  The configuration of a normal client platform is a model except that the normal client platform operating system 26 further includes a supply on demand (POD) driver 2621 for reading files from the storage device 243 or the server 12 in response to a client request. The configuration is the same as that of the client platform.

  The server 12 can include a hardware machine 120, an account server 121, a package server 122, and an image server 123. The hardware machine 120 may include one or more processors 1201, a memory 1202, a storage device 1203, a network interface 1204, and the like. The account server 121 can confirm the account information received from the client platform. The package server 122 can send and receive incremental packages to and from the client platform based on the confirmation result from the account server 121.

  In order to provide a customized service to a group of clients, a base file containing an operating system and / or basic application may be pre-installed on the storage device of each client platform during a pre-install period. However, the base file may be installed in other ways. For example, the base file may be preinstalled in the storage device 203 of the model client platform. Thereafter, the EFI 221 of the model client platform generates a base package including a base file and a base file description (file name, file size, file structure, etc.), and uploads the base package to the image server 123 of the server 12. You can do it.

  The base package may further include a block description that describes the block that stores the base file, such as the location of the block in the storage device 203 of the model client platform. Then, the image server 123 downloads the base package to each of the other client platforms during the preinstall period, so that each of the other client platforms can preinstall the base file at the same block position as the model client platform.

  Incremental files designed for a group of clients, such as educational material or games, may be installed in the model client platform storage 203. During installation, the SUP driver 2220 directs the incremental file to a block of the storage device 203 that the base file does not use so that the base file is not destroyed. The SUP driver 2220 further determines whether the incremental file is an updated version of the base file, and if the incremental file is an updated base file, maps the block storing the incremental file to the block storing the base file. Mapping information indicating this may be recorded.

  The EFI 211 may then generate an incremental package based on the incremental file and the available mapping information. Incremental packages may be uploaded to the server. The package may include an incremental file image having the contents of the incremental file and an incremental file description image having a file description of the incremental file. Examples of file descriptions may include file name, file size, and file structure (such as a file system tree structure). In this embodiment, the file description may further include information about blocks of the storage device 203 that can store incremental files, such as block locations within the storage device 203. The EFI 211 may further generate a model block bitmap indicating the usage status of each block in the storage device 203 and upload the model block bitmap to the server 12.

  FIG. 3A shows, for example, blocks 1. 1 illustrates one embodiment of a storage device 203 that is divided into a plurality of blocks, such as block n.

  FIG. 3B illustrates one embodiment of an incremental package 300 having an incremental file image 301 and an incremental file description image 302. The incremental file image 301 may have a plurality of entries, and each of the plurality of entries corresponds to one block of the storage device 203. Each entry of the incremental file image 301 may include two parts, one is the contents of the incremental file stored in the block, and the other is descriptive information associated with the block.

  For example, entry 1 of incremental file image 301 may include the contents of incremental file 1 stored in block 1 of storage device 203 and descriptive information about block 1 (eg, block location in storage device 203). For incremental files that may require multiple blocks for storage, the corresponding incremental file image may include multiple entries.

  Similarly, the incremental file description image 302 may have a plurality of entries, and each of the plurality of entries corresponds to one block of the storage device 203. Each entry of the incremental file description image 302 may have two parts, one is file description information stored in the block and the other is description information related to the block.

  For example, the entry 1 ′ of the incremental file description image 302 may include file description information stored in the block 20 of the storage device 203 and block description information regarding the block 20 (for example, a block position in the storage device 203). As described above, the file description information includes the file name, file size, file structure, and increment such as the block of the storage device 203 that stores the incremental file (eg, blocks 4, 5, and 10 that store the incremental files 1 and 2). Descriptive information about the files (eg, incremental files 1 and 2) may be included.

  FIG. 3C illustrates one embodiment of a model block bitmap, where each bit of the bitmap corresponds to each block of storage device 203, and bit '1' or bit '0' is the corresponding block used. It may represent that it is present and not used. However, it should be understood that other techniques may be applied to the model block bitmap. For example, the model block bitmap may indicate whether the content stored in each block of the storage device 203 has been uploaded to the server. In that case, bit '1' or bit '0' may indicate that the content of the corresponding block has been uploaded and has not been uploaded.

  Referring back to FIG. 2, when one client (eg, a young student) in the group logs on to a regular client platform that has pre-installed base files, the EFI 251 may receive an account entered by the client via the user interface 270. Information can be received. The account information may then be sent to the account server 121 for verification prior to booting the operating system 26 during platform initialization.

  After the confirmation, the account server 121 may activate the package server 122 and send a model block bitmap that matches the account information to the EFI 251. The model block bitmap can be provided by the EFI 211 of the model client platform indicating the usage status of each block of the storage device 203 of the model client platform. The EFI 251 may further generate a normal block bitmap indicating the usage status of each block of the storage device 243 of the normal client platform.

  FIG. 3D illustrates one embodiment of a regular block bitmap 304. As shown, blocks 1 through 3 of storage device 243 may be used to store base files during normal client platform pre-installation.

  After the operating system 26 is booted up and the driver 262 including the SUP driver 2620 and the POD driver 2621 is set up in a normal client platform, the package server 121 transmits an incremental file description image designed for the client to the POD driver. 2621 may be transmitted. The POD driver 2621 may extract file description information and block description information from the incremental file description image. The POD driver 2621 may store file description information about the block position described in the block description information, and update a normal block bitmap extracted from the EFI 251. The normal block bitmap may be updated by indicating that a block of storage 243 that stores incremental file description information is used.

  By using the incremental file description information read from the server 12 and other information (for example, base file description information), the operating system 26 can construct a file system 261 representing the file structure. In this embodiment, the file system 261 may further represent information regarding files, particularly blocks corresponding to incremental files. The file system 261 may help the operating system 26 present the incremental file and / or base file icons on the screen of the user interface 270 even if the contents of the incremental file are not installed in the normal platform storage 243. . For example, the user interface 270 may present an e-class icon for young students or a game icon for adults.

  When a client opens a file by clicking a file icon on the user interface 270, the I / O handler 260 receives an I / O call from the user interface 270, and the file system 261 determines which block of the storage device 243 It may be analyzed whether it can correspond to the selected file. The POD driver 2621 may determine whether the selected file is stored in the storage device 243 by referring to a normal block bitmap. When the normal block bitmap indicates that the corresponding block is used, the POD driver 2621 may read the file from the block of the storage device 243 and output the file to the user interface 270. However, if the normal block bitmap indicates that the corresponding block is not being used, the POD driver 2621 refers to the model block bitmap to determine whether the selected file is available from the server 12. Can be determined. For example, indicating that the corresponding block is used in the model block bitmap may indicate that the selected file is available from the server.

  In response to determining that the selected file is available from the server 12, the POD driver 2621 sends a request to download the selected file to the server 12. The package server 122 reads the incremental file image entry storing the selected file and downloads the incremental file image entry to the POD driver 2621 so that the POD driver 2621 is retrieved from the incremental file image entry. The normal block bitmap may be updated by storing the file in a corresponding block of the storage device 243 and indicating that the corresponding block is being used. Finally, the POD driver 2621 may output the selected file to the user interface 270.

  If the client chooses to download a new file to the storage device 243, the SUP driver 2620 may store the new file in a block of the storage device 243 that is not used by the base file to protect the base file. The SUP driver 2620 may further determine whether the new file is an updated version of the base file. If the new file is an updated base file, the SUP driver 2620 may record mapping information for mapping the block storing the new file to the block storing the base file.

  If the client decides to save the current storage configuration before logging off, the normal client platform will reboot and the EFI 251 will store the incremental file and / or mapping stored in the normal client platform storage 243. Based on the information, an incremental package may be generated and the incremental package uploaded to the server 12. The normal block bitmap downloaded from the server 12 to create the same storage environment when the client logs on to another normal client platform by the EFI 251 further uploading the normal block bitmap to the server And incremental packages may be used.

  Other embodiments may implement other techniques for the structure as shown in FIG. For example, the model platform may be further used to install incremental files designed for other groups of clients. In that case, the EFI 211 may generate an incremental package and a block bitmap, respectively, for each group of clients. In another example, the EFI 211 may not upload the incremental file description image to the server 12 if the corresponding file description is not pre-installed on the regular client platform. In yet another example, the model block bitmap may be omitted and the information about the block storing the incremental file is an increment such as an indicator that indicates whether the incremental file stored in the corresponding block is available from the server 12. May be integrated with the file description image.

FIG. 4 illustrates one embodiment of a method for installing a model client platform. As shown, in block 401, IT administrator or appropriate device may be installed based files to one or more client platforms ₁₁ 1 -11 _N. The base file may include an operating system and / or any basic application file.

  At block 402, the IT administrator or appropriate device may determine whether an incremental file designed for a new group of clients has been installed on the model client platform. If it is determined that it has been installed, the IT administrator or appropriate device selects one client platform as the model client platform from the network environment 10 at block 403 and matches the group of clients at block 404. The designed incremental file may be determined, and at block 405, the incremental file may be installed on the storage device of the selected model client platform.

  While installing the incremental file, at block 406, the model client platform SUP driver 2220 may determine whether the incremental file is an updated version of the base file installed in the model client platform storage. In response to determining that the incremental file is an updated base file, at block 407, the SUP driver stores the incremental file in a block that is not used by the base file, and replaces the block storing the incremental file with the base file. You may map to the block to store. Thereafter, at block 408, the EFI 211 may generate an incremental package that includes the incremental file image and the incremental file description image, and a model block bitmap that indicates the usage of the blocks of the model client platform storage 203. Finally, at block 409, the model client platform's EFI 211, or other suitable device, may upload the incremental package and model block bitmap to the server 12.

  FIG. 5 illustrates one embodiment for initializing a normal client platform. In block 501, the firmware routine may execute the BIOS program before the normal client platform starts and boots the operating system. At block 502, the EFI 251 may prompt the client to enter account information via the user interface 270. Thereafter, in block 503, the account server 121 may confirm the account information by the EFI 251 sending the account information to the server 12. At block 504, in response to confirmation, the package server 122 may send a model block bitmap that matches the account information to the EFI 251. The model block bitmap may be generated by a model client platform with an incremental file designed for the client installed.

  At block 505, the EFI 251 may generate a normal block bitmap that indicates the block usage of the normal client platform storage 243. Thereafter, at block 506, operating system 26 is booted and drivers including SUP driver 2620 and POD driver 2621 are set up. In block 507, the package server 122 may send the incremental file description image uploaded by the model client platform to the POD driver 2621. The incremental file description image may include descriptive information regarding the incremental file and a block description regarding the block storing the incremental file in the model platform.

  Thereafter, in block 508, the normal client platform operating system 26 sets up the file system by utilizing the incremental file description image, even if the incremental file is not actually loaded on the normal client platform. A file icon may be displayed on the user interface 270.

  FIG. 6 illustrates one embodiment of processing an I / O request by a normal client platform. In block 601, the normal client platform I / O handler 260 may receive an I / O request and read / write a file to / from the storage device 243. At block 602, the I / O handler 260 may determine whether the request is a read request or a write request. In the case of a read request, the I / O handler 260 transfers the request to the POD driver 2621. Thereafter, at block 603, the POD driver 2621 may find file related information, such as information about the block storing the file, by using the file system 261 to check the requested file.

  At block 604, the POD driver 2621 may determine whether the requested file has already been loaded into the block of the storage device 243 by referring to the normal block bitmap read from the EFI 251. If the file is loaded into a block of the storage device 243, the POD driver 2621 may read the file from the storage device 243 and output it to the user interface 270 to end the I / O request. If the file is not loaded into a block of storage device 243, POD driver 2621 may determine whether the requested file is available from server 12 by referring to the model block bitmap.

  In response to determining that the requested file is available from server 12, POD driver 2621 may send a file image download request to server 12, and package server 122 may increment the file with the requested file. The image entry may be found and the incremental file image entry sent to the POD driver 2621. The POD driver 2621 may then read the file from the incremental file image entry at block 606 and load the file into the corresponding block of the storage device 243 at block 607. At block 608, the POD driver 2621 may update the normal block bitmap by indicating that the block storing the requested file is being used. In block 609, the POD driver 2621 may output the file to the user interface 270 and terminate the I / O request.

  In block 602, in response to determining that the I / O request is a request to write a new file to the storage device 243, the I / O handler 260 may forward the request to the SUP driver 2620. In block 610, the SUP driver 2620 may store the new file in a block of the storage device 243 that is not used by the base file. In block 611, the SUP driver 2620 may update the normal block bitmap by indicating that the block storing the new file is being used. At block 612, the SUP driver 2620 may further determine whether the new file is an updated version of the base file stored in the storage device 243. If it is a new version, at block 613, the SUP driver 2620 may record mapping information that maps the block storing the new file to the block storing the base file.

  FIG. 7 illustrates one embodiment of saving storage space for a client of a client platform in a network environment. In block 701, the client may be given the option to log out of the client platform and save the current storage device environment. To save the storage environment, the client platform may reboot the platform at 703, and EFI 251 or other suitable device on the client platform may generate incremental packages and block bitmaps. The incremental package may include an incremental file image corresponding to the incremental file stored on the storage device and an incremental file description image describing information about the incremental file. The block bitmap may indicate the usage status of the block of the storage device. As mentioned above, the block bitmap may be omitted and such information related to the block may be integrated into the incremental file description image.

  Thereafter, at block 705, the EFI 251 may upload the incremental package and block bitmap to the server 12. At block 706, the EFI 251 may erase the incremental file from the client platform storage and log out.

  Other embodiments may implement other techniques for the method shown in FIG. For example, before providing a storage environment save / restore service, the client platform may determine whether the client is a VIP client if only the VIP client is eligible for such service.

  FIG. 8 illustrates one embodiment of a general platform that can function as a client platform or server in the network environment 10 of FIG. The platform may include one or more processors 850, memory 851, chipset 852, I / O device 853, firmware 854, and storage device 855. The processor 850 is communicatively coupled to other components via one or more buses, such as a processor bus. The processor 850 is, for example, Intel® Xeon®, Intel® Pentium®, Intel® Itanium®, available from Intel Corporation of Santa Clara, California. It can be implemented as an integrated circuit (IC) having one or more processing cores that can execute code under a suitable architecture, such as an architecture.

  In one embodiment, the memory 851 may store code that can be executed by the processor 850. Some examples of memory 851 include, but are not all, SDRAM (synchronous ad-hoc write / read memory) devices, RAMBUS RDRAM (dynamic random access memory) devices, double data rate (DDR) memory devices, SRAM (static RAM) and one or a combination of semiconductor devices such as flash memory devices.

  In one embodiment, chipset 852 provides one or more communication paths between processor 850, memory 851, and other components such as, for example, I / O device 853, firmware 854, and storage device 855. sell. Examples of the I / O device 853 may include a keyboard, a mouse, a network interface, a storage device, a camera, Bluetooth, and an antenna.

  Firmware 854 interfaces with the BIOS routines executed by the platform during system setup and / or firmware 1054 and the platform operating system to initialize processor 850, chipset 852, and other components of the platform. EFI routines that provide a standard environment for booting the operating system may be stored.

  The storage device 855 can include an internal storage device (such as a hard disk) that is within the platform and / or an external storage device (eg, floppy disk, optical disk, etc.) that is outside the client platform. If a client platform such as that shown in FIG. 8 can be implemented as a client platform, the storage device 855 may also store base files, incremental files, file descriptions, or possibly other data. If the platform as shown in FIG. 8 is server 12, storage device 855 may also store incremental file images, incremental file description images, block bitmaps, or possibly other data.

  While certain features of the invention have been described with reference to illustrative embodiments, this description is not meant to be construed in a limiting sense. It will be apparent to those skilled in the art that various modifications of these exemplary embodiments and other embodiments of the invention are within the spirit and scope of the invention.

While certain features of the invention have been described above with reference to illustrative embodiments, the description is not intended to be construed in a limiting sense. It will be apparent to those skilled in the art that various modifications of these illustrative items, and other items of the invention, are within the spirit and scope of the invention. Examples of the present invention are shown as the following items.
[Item 1]
Model client platform method,
Generating a file image including an incremental file stored in a first model block of a model storage device of a model client platform;
Generating a file description image including a file description stored in a second model block of the model storage device;
Uploading a file image and a file description image to the server;
With
The file description includes the position of the first model block in the model storage device,
Method.
[Item 2]
The method of item 1, further comprising generating a model block bitmap indicating whether data stored in each model block of the model storage device is available from a server.
[Item 3]
The method of item 1, further comprising the step of generating a model block bitmap that indicates the usage status of each model block in the model storage device.
[Item 4]
The method of claim 1, wherein the file image further includes a position of the first model block in the model storage device.
[Item 5]
The method of item 1, wherein the file description image further comprises a position of a second model block in the model storage device.
[Item 6]
Generating a base file stored in a third model block of the model storage device and another file image including a position of the third model block in the model storage device;
Uploading other file images to the server,
The method according to item 1, further comprising:
[Item 7]
Determining that the incremental file is an updated version of the base file stored in the third model block of the model store;
Recording mapping information that maps a first model block storing an incremental file to a third model block storing a base file;
Uploading the mapping information to the server;
The method according to item 1, further comprising:
[Item 8]
A normal client platform approach,
Generating a normal block bitmap indicating the usage of each normal block on a normal storage device on a normal client platform;
Downloading a file description image including a file description from a server;
With
The file description includes the location of the first model block in the model store of the model client platform;
The first model block stores an incremental file;
Method.
[Item 9]
Further comprising downloading a model block bitmap from the server;
Item 9. The method according to Item 8, wherein the model block bitmap indicates a usage status of each model block of the model storage device.
[Item 10]
Determining whether an incremental file is available from the server based on the normal block bitmap and the model block bitmap;
Downloading incremental files from the server;
Storing the incremental file in the first normal block of the normal storage device corresponding to the position of the first model block in the model storage device;
Updating the normal block bitmap to indicate that the first normal block is being used;
The method according to item 9, further comprising:
[Item 11]
Reading the incremental file from the file image stored on the server based on the location of the first model block;
The method of item 10, wherein the file image links the incremental file to the location of the first model block.
[Item 12]
10. The method of item 9, wherein the file description image further includes a location of a second model block in the model storage device, wherein the second model block stores the file description.
[Item 13]
Storing the file description in a second normal block of a normal storage device corresponding to the location of the second model block;
Updating the normal block bitmap to indicate that the second normal block is being used;
The method of item 12, further comprising:
[Item 14]
Downloading a base file and a base file image including a location of a third model block storing the base file in the model storage device from the server;
Storing the base file in a third normal block of a normal storage device corresponding to the position of the third model block;
The method according to item 9, further comprising:
[Item 15]
Storing the new file in a fourth normal block of a normal storage device;
If the new file is an updated version of the base file, recording mapping information that maps the fourth regular block to the third regular block;
15. The method of item 14, further comprising:
[Item 16]
A machine-readable medium comprising a plurality of instructions that when executed on a client platform,
Storing the incremental file in the first block of the client platform storage;
Rebooting the client platform;
Generating a file image including an incremental file and a file description image including a file description of the incremental file;
And execute
A machine-readable medium, wherein the file description includes a location of the first block in the storage device.
[Item 17]
Multiple instructions
Uploading a file image and a file description image to the server;
Deleting incremental files from the storage device; and
Logging out of the client platform;
The machine-readable medium according to item 16, further comprising:
[Item 18]
Multiple instructions
Generating a block bitmap indicating usage of each block of the storage device;
Uploading the block bitmap to the server;
The machine-readable medium according to item 16, further comprising:
[Item 19]
A model storage device having a first model block storing an incremental file and a second model block storing a file description of the incremental file;
A model firmware component that generates a file image including an incremental file and a file description image including a file description; and
With
The model client platform, wherein the file description includes the location of the first model block in the model store.
[Item 20]
Item 20. The model client platform of item 19, further comprising a model network interface for uploading a file image and a file description image to a server.
[Item 21]
The model firmware component further generates a model block bitmap indicating the usage status of each model block in the model storage device,
The model client platform of item 20, wherein the model network interface further uploads the model block bitmap to the server.
[Item 22]
20. The model client platform of item 19, wherein the model storage device further comprises a third model block that stores a base file.
[Item 23]
The model firmware further generates a base file and other file images including the location of the third model block in the model store,
The model client platform of item 20, wherein the model network interface further uploads other file images to the server.
[Item 24]
Item 23, further comprising a driver that records mapping information that maps a first model block storing the incremental file to a third model block storing the base file if the incremental file is an updated version of the base file. The model client platform described.
[Item 25]
A normal storage device having a plurality of normal blocks;
A normal network interface for downloading a file description image including a file description from the server;
A normal firmware component that generates a normal block bitmap indicating normal block usage, and
With
The file description includes the location of the first model block in the model store of the model client platform;
The first model block stores an incremental file;
Normal client platform.
[Item 26]
26. The normal client platform of item 25, wherein the normal network interface further downloads a model block bitmap from the server, the model block bitmap indicating usage of each model block in the model storage device.
[Item 27]
A first driver, the first driver comprising:
Based on the normal block bitmap and model block bitmap, determine whether an incremental file is available from the server,
Download incremental files from the server,
Storing the incremental file in a first regular block of the plurality of regular blocks corresponding to the location of the first model block;
26. The regular client platform of item 25, wherein the regular block bitmap is updated to indicate that the first regular block is being used.
[Item 28]
The file description image further includes a position of the second model block in the model storage device, the second model block storing the file description,
26. The normal client platform of item 25, wherein the normal storage device further stores a file description in a second normal block of the plurality of normal blocks corresponding to the location of the second model block.
[Item 29]
A second driver, the second driver comprising:
Receiving from the server a base file image including a base file and a location of a third model block storing the base file in the model storage device;
26. The ordinary client platform according to item 25, wherein the base file is stored in a third ordinary block of the plurality of ordinary blocks corresponding to the position of the third model block.
[Item 30]
A second driver, the second driver comprising:
Store the new file in the fourth regular block of the multiple regular blocks,
30. A regular client platform according to item 29, wherein if the new file is an updated version of the base file, the mapping information mapping the fourth regular block to the third regular block is recorded.

Claims (30)

Model client platform method,
Generating a file image including an incremental file stored in a first model block of a model storage device of the model client platform;
Generating a file description image including a file description stored in a second model block of the model storage device;
Uploading the file image and the file description image to a server;
With
The file description includes a position of the first model block in the model storage device;
Method.   The method of claim 1, further comprising generating a model block bitmap indicating whether data stored in each model block of the model storage device is available from the server.   The method of claim 1, further comprising generating a model block bitmap indicating usage of each model block in the model storage device.   The method of claim 1, wherein the file image further includes the location of the first model block in the model storage device.   The method of claim 1, wherein the file description image further includes a position of the second model block in the model storage device. Generating a base file stored in a third model block of the model storage device and another file image including a position of the third model block in the model storage device;
Uploading the other file image to the server;
The method of claim 1, further comprising: Determining that the incremental file is an updated version of a base file stored in a third model block of the model store;
Recording mapping information for mapping the first model block storing the incremental file to the third model block storing the base file;
Uploading the mapping information to the server;
The method of claim 1, further comprising: A normal client platform approach,
Generating a normal block bitmap indicating usage of each normal block in the normal storage of the normal client platform;
Downloading a file description image including a file description from a server;
With
The file description includes a location of a first model block in a model storage device of a model client platform;
The first model block stores an incremental file;
Method. Downloading a model block bitmap from the server;
The method of claim 8, wherein the model block bitmap indicates a usage status of each model block in the model storage device. Determining whether the incremental file is available from the server based on the normal block bitmap and the model block bitmap;
Downloading the incremental file from the server;
Storing the incremental file in a first normal block of the normal storage device corresponding to the location of the first model block in the model storage device;
Updating the normal block bitmap to indicate that the first normal block is being used;
The method of claim 9, further comprising: Reading the incremental file from a file image stored on the server based on the location of the first model block;
The method of claim 10, wherein the file image links the incremental file to the location of the first model block.   The method of claim 9, wherein the file description image further includes a location of a second model block in the model storage device, wherein the second model block stores the file description. Storing the file description in a second normal block of the normal storage device corresponding to the location of the second model block;
Updating the normal block bitmap to indicate that the second normal block is being used;
The method of claim 12, further comprising: Downloading a base file and a base file image including a position of a third model block storing the base file in the model storage device from the server;
Storing the base file in a third normal block of the normal storage device corresponding to the location of the third model block;
The method of claim 9, further comprising: Storing a new file in a fourth normal block of the normal storage device;
If the new file is an updated version of the base file, recording mapping information that maps the fourth regular block to the third regular block;
15. The method of claim 14, further comprising: A machine-readable medium comprising a plurality of instructions that when executed on a client platform,
Storing an incremental file in a first block of the storage device of the client platform;
Rebooting the client platform;
Generating a file image including the incremental file and a file description image including a file description of the incremental file;
And execute
The machine-readable medium, wherein the file description includes a location of the first block in the storage device. The plurality of instructions are:
Uploading the file image and the file description image to a server;
Deleting the incremental file from the storage device;
Logging out of the client platform;
The machine-readable medium of claim 16, further executing: The plurality of instructions are:
Generating a block bitmap indicating the usage status of each block of the storage device;
Uploading the block bitmap to a server;
The machine-readable medium of claim 16, further executing: A model storage device having a first model block for storing an incremental file and a second model block for storing a file description of the incremental file;
A model firmware component for generating a file image including the incremental file and a file description image including the file description;
With
The model client platform, wherein the file description includes a location of the first model block in the model storage device.   20. The model client platform of claim 19, further comprising a model network interface that uploads the file image and file description image to a server. The model firmware component further generates a model block bitmap indicating the usage status of each model block of the model storage device;
21. The model client platform of claim 20, wherein the model network interface further uploads the model block bitmap to the server.   The model client platform of claim 19, wherein the model storage device further comprises a third model block for storing a base file. The model firmware further generates a base file and another file image including a position of a third model block in the model storage device;
21. The model client platform of claim 20, wherein the model network interface further uploads the other file image to the server.   A driver that records mapping information that maps the first model block storing the incremental file to the third model block storing the base file if the incremental file is an updated version of the base file; The model client platform of claim 23, further comprising: A normal storage device having a plurality of normal blocks;
A normal network interface for downloading a file description image including a file description from the server;
A normal firmware component that generates a normal block bitmap indicating usage of the normal block;
With
The file description includes a location of a first model block in a model storage device of a model client platform;
The first model block stores an incremental file;
Normal client platform.   26. The normal client platform of claim 25, wherein the normal network interface further downloads a model block bitmap from the server, the model block bitmap indicating usage of each model block in the model storage device. . A first driver, the first driver comprising:
Determining whether the incremental file is available from the server based on the normal block bitmap and the model block bitmap;
Download the incremental file from the server;
Storing the incremental file in a first regular block of the plurality of regular blocks corresponding to the location of the first model block;
26. The regular client platform of claim 25, wherein the regular block bitmap is updated to indicate that the first regular block is being used. The file description image further includes a position of a second model block in the model storage device, and the second model block stores the file description;
26. The normal storage device of claim 25, wherein the normal storage device further stores the file description in a second normal block of the plurality of normal blocks corresponding to the location of the second model block. Client platform. A second driver, the second driver comprising:
Receiving from the server a base file image including a base file and a location of a third model block storing the base file in the model storage device;
26. The normal client platform of claim 25, wherein the base file is stored in a third normal block of the plurality of normal blocks corresponding to the location of the third model block. A second driver, the second driver comprising:
Storing a new file in a fourth regular block of the plurality of regular blocks;
30. The normal client platform of claim 29, wherein if the new file is an updated version of the base file, mapping information is recorded that maps the fourth normal block to the third normal block.

Images