JP4389180B2 - Media connection device, media connection system, and operation method of media connection system - Google Patents

Description

The present invention is a media connecting unit, a media connection system consisting of its media connection device and the host device, and to a method of operation thereof.

JP 2003-177987 A

  A mechanism for transferring a file by FTP (File Transfer Protocol) is conventionally known (see, for example, Patent Document 1).

  In recent years, a so-called memory card (an example of a storage medium) in which a non-volatile memory such as a flash memory is packaged in a card type is widely known. This memory card is rapidly spreading as a data storage medium used in digital devices such as digital cameras and portable music players. The specifications of the memory card are not unified. For example, compact flash (registered trademark, hereinafter abbreviated as “CF”), smart media (registered trademark, hereinafter abbreviated as “SM”), memory stick (registered trademark, hereinafter “ Various products such as “MS” and SD memory card (registered trademark, hereinafter abbreviated as “SD”) are on the market.

  A PC or the like communicates with a memory card reader / writer (hereinafter abbreviated as “reader / writer”) that also reads and writes a memory card, thereby enabling access to the memory card connected to the reader / writer. In recent years, printing apparatuses equipped with such a reader / writer have also become widespread. For example, by connecting a memory card in which an image data file saved in JPEG format or the like is connected to a reader / writer, an image can be transmitted without going through a PC. Can be printed directly.

  If an FTP client program is installed on a PC, etc., and an FTP server program is installed on the card reader side, the memory card used as the storage location for the captured image data file of a digital camera or camera-equipped mobile phone is read / written. By connecting to, the data file stored in the memory card can be transferred to the PC by FTP. That is, the reader / writer can be used as an external FTP storage device of a PC.

Incidentally, as its name suggests, FTP is a protocol designed for file transfer, and no protocol design has been made on the assumption that storage media (removable media, hereinafter simply referred to as media) will be handled.
Therefore, when an FTP server is installed in the FTP storage device as described above (or a peripheral device such as a printer in which the FTP storage device is installed), a client that only conforms to the FTP protocol itself can receive data from a memory card reader on the network. It is impossible to display information, and it is impossible to perform operations such as formatting a memory card from a client.
As a technique for solving the above-described problems, first, it is conceivable that the FTP protocol itself is extended and modified so that the media itself and operations in units of media can be directly performed from a client compliant with the FTP protocol. However, when an extended change is made, existing FTP client users cannot benefit from the benefits. In addition, protocol changes need to be approved through international organizations and are not practical.

  SUMMARY OF THE INVENTION An object of the present invention is to make it possible to directly perform operations on a medium itself or a medium on an FTP server from a client conforming to the FTP protocol without performing an extension change of the protocol.

Means for Solving the Problems and Effects of the Invention

In order to solve the above-mentioned problem, a media connection device according to claim 1 provides a media connection unit for connecting a storage medium, and commands indicating a directory name specification, a file name specification, and a file unit operation from the host device to the server. a server unit that conforms to the procedure of transmitting to the apparatus defined protocol, a media connection apparatus wherein the server means stores the storage media, the media and the corresponding directory name, in association with each other, When a file operation command indicating a media-compatible directory name specification, one file name specification, and a file operation request for each file is received from a host device connected via a network by the procedure defined in the protocol, The one file stored in a storage medium corresponding to the directory name corresponding to the medium The file unit is operated on a file having a file name, and the server means further stores a hypertext file name, and includes at least one of the format of the storage medium and the opening of the storage medium An operation-corresponding file name storage unit that associates and stores media operations in units of media and operation-corresponding file names, and designates a virtual directory name that is different from the media-corresponding directory name in the procedure defined by the protocol; Generating a hypertext file including an operation-corresponding link for causing the host device to execute a process of transmitting a file operation command indicating the operation-corresponding file name and a file operation request in file units to the media connection device; Connect via a network When a file operation command indicating a virtual directory name specification different from the media-compatible directory name, a hypertext file name specification, and a data operation request in units of files is received from the target device according to the procedure defined by the protocol The hypertext file is returned to the host device, and the virtual directory name is specified and stored in the operation-corresponding file name storage means from the host device that has received the hypertext file according to the procedure defined by the protocol. When the file operation command indicating the designation of the file name corresponding to one operation and the data operation request for each file is received, the media operation corresponding to the file name corresponding to the one operation is executed on the storage medium. to, characterized in that.

The media connection device according to claim 2, wherein the protocol includes a procedure for transmitting a command indicating a directory unit operation request from the host device to the server device, and the server means is a host connected via a network. A file stored in a storage medium corresponding to the media-corresponding directory name when receiving a list request command indicating the media-corresponding directory name specification and a file name list request from the apparatus according to the procedure defined by the protocol and Shin returns the list of names to the host device, prior Symbol server means further from the host device connected via a network, a list request specifying the file name of the virtual directory name by the procedure defined in the protocol When a list request command indicating It returns a name to the host device, and wherein the.

The media connection device according to claim 3 is characterized in that the server means returns the hypertext file name in such a manner that the host device can display the click operation of the user so as to be accepted .

The media connection device according to claim 4, wherein the server means is connected to the media connection unit, whether a storage medium is connected to the media connection unit, whether the storage medium connected to the media connection unit is formatted, or connected to the media connection unit. A state indicating that the detected storage medium is accessible, detecting at least one of the capacity of the storage medium connected to the media connection unit and the free capacity of the storage medium connected to the media connection unit, and indicating the detected state The hypertext file is generated so as to include information .

6. The media connection device according to claim 5, wherein the server means generates progress data that is data indicating the progress of the operation by the execution of the operation, and transmits the progress data to the host device. To do.

The media connection device according to claim 6, wherein the server means transmits data including a link to the progress data to the host device .

The media connection device according to claim 7, wherein the server means transmits data including a link to the progress data and a command for deleting cache data relating to a link destination to the host device .

The media connection device according to claim 8, wherein the server means transmits a link to the progress data and redirect instruction data instructing redirection to the link to the host device .

The media connection device according to claim 9, wherein the server means is different from the link together with the progress data, and is a link to the next progress data, which is data indicating the progress of the operation of the next stage, and to the link. Redirection instruction data for instructing redirection is transmitted to the host device .

The media connection device according to claim 10, wherein the media connection device is provided with a plurality of media connection units, and the operation-corresponding link corresponds to an operation on a storage medium connected to any one of the media connection units. Features.

The media connection device according to an eleventh aspect is characterized in that storage media of different types can be connected to the media connection unit, and the operation corresponding link corresponds to an operation on any type of storage media .

The media connection device according to claim 12, wherein the operation-compatible link corresponds to an operation of transmitting a file name or a directory name in a storage medium connected to the media connection unit to the host device .

According to a thirteenth aspect of the present invention, there is provided a media connection device incorporated in a network printer capable of executing printing based on print data transmitted via the network .

The media connection device according to claim 14 is characterized in that the protocol is an FTP protocol .

In the media connection system according to claim 15, a procedure for transmitting a command indicating a media connection unit for connecting a storage medium, a directory name designation, a file name designation, and a file unit operation from the host device to the server device is defined. A media connection system comprising: a server device that complies with a designated protocol; and a host device that is connected to the media connection device via a network. A media and a directory name corresponding to the media are stored in association with each other, and from the host device connected via the network, the directory name corresponding to the media, the designation of one file name, and the file unit according to the procedure defined by the protocol. If a file operation command indicating that a file operation request is received, the previous A storage medium corresponding to the directory name corresponding to the medium stores the file unit for the file having the one file name, and the server means further stores a hypertext file name, An operation-corresponding file name storage unit that associates and stores a media operation in units of the storage medium including at least one of the format of the storage medium and the opening of the storage medium, and an operation-corresponding file name. A process of transmitting a file operation command indicating a virtual directory name different from the media-corresponding directory name, a specification of the operation-corresponding file name, and a file operation request for each file to the media connection device in a predetermined procedure; Operations to be executed by the host device A hypertext file including a response link is generated, and a virtual directory name that is different from the media-compatible directory name and a hypertext file name are specified from a host device connected via a network according to the procedure defined by the protocol. And a procedure specified by the protocol from the host device that has returned the hypertext file to the host device and received the hypertext file when a file operation command indicating a file-unit data operation request is received. When the file operation command indicating the designation of the virtual directory name, the designation of one operation-corresponding file name stored in the manipulation-corresponding file name storage means and the data manipulation request in units of files is received, the one manipulation correspondence The media corresponding to the file name The operation is performed on the storage medium .

The media connection system according to claim 16 is characterized in that the host device stores a shortcut file to the file having the predetermined file name .

The operation method of the media connection system according to claim 17 transmits a command indicating a media connection unit for connecting a storage medium, a directory name specification, a file name specification, and a file unit operation from the host device to the server device. A server that conforms to a protocol for which a procedure is defined, and the server means stores the storage medium and a media-corresponding directory name in association with each other, and connects them via a network. When a file operation command is received from the host device indicating a media-compatible directory name specification, a single file name specification, and a file-unit-specific file operation request according to the procedure defined in the protocol, the media-compatible directory name is set. The file with the one file name is stored in the corresponding storage medium. The file is operated for each file, and the server means further stores a hypertext file name and includes at least one of the format of the storage medium and the opening of the storage medium. Operation-corresponding file name storage means for storing the media operation and the operation-corresponding file name in association with each other, and specifying the virtual directory name different from the media-corresponding directory name and the operation according to the procedure defined by the protocol A hypertext file including an operation corresponding link for causing the host device to execute a process of transmitting a file operation command indicating designation of a corresponding file name and a file operation request for each file to the media connection device is generated, and a network is created. From a host device connected via When a file operation command indicating a virtual directory name designation different from the media-corresponding directory name, a hypertext file name designation, and a file-unit data manipulation request is received in the procedure defined by the protocol, One operation stored in the operation-corresponding file name storage means and the designation of the virtual directory name from the host device that has returned the text file to the host device and received the hypertext file in accordance with the procedure defined by the protocol. When the file operation command indicating the designation of the corresponding file name and the data operation request for each file is received, the media operation corresponding to the one operation corresponding file name is executed on the storage medium. It is characterized by operation .

  The FTP system according to claim 18 is characterized in that the FTP processing apparatus according to claim 3 includes the host device storing a shortcut file to the file having the predetermined file name.

  The FTP system operation method according to claim 19, further comprising a media connection unit, and in accordance with a command from the host device via FTP communication via a network, at least a file unit of data for the storage medium connected to the media connection unit In an FTP type processing apparatus having an FTP server means for reading and writing data, data including an operation correspondence link associated with an operation in units of the storage medium is transmitted to the host device, and the operation correspondence link An operation corresponding to the operation-corresponding link is executed on the condition that an access request to is received.

  According to the FTP processing device of claim 1, the FTP system of claim 17, and the FTP system operation method of claim 19, the FTP processing device is provided with an FTP server corresponding to the FTP protocol, and the host device Is provided with an FTP client corresponding to the FTP protocol. The FTP server transmits data including an operation corresponding link associated with an operation in units of storage media to the FTP client in accordance with a command from the FTP client through FTP communication via the network. The FTP client can confirm the state of the media by opening the data transmitted from the FTP server with a browser. Further, by performing an operation-related link operation included in the file, it is possible to directly perform the operation of the medium itself or the medium.

  That is, it is possible to directly perform operations on the media itself on the FTP server and the media as a unit from a client compliant with the FTP protocol without changing the extension of the FTP protocol.

  According to the FTP processing apparatus of the second aspect, the user can directly perform the operation on the FTP server itself or the unit of the medium from the client conforming to the FTP protocol. In addition, by using hypertext data, it is possible to convey media information and operation means in a form that is easier for the user to understand (such as using colors).

  According to the FTP processing apparatus of the third aspect, the user can know an operation that can be performed when the FTP processing apparatus receives an access request. Therefore, there is no problem caused by the user specifying an operation that cannot be performed.

  According to the FTP type processing apparatus of the fourth aspect, the user can know the operation execution status of the FTP type processing apparatus because the user can obtain an entity file describing the operating status.

  According to the FTP processing apparatus of the fifth aspect, since the user can know the link for obtaining the entity file describing the operation status, the user can know the operation execution status of the FTP processing apparatus. .

  According to the FTP type processing apparatus of the sixth aspect, in order to transmit data including a command for deleting cache data, when the user accesses the FTP type processing apparatus using a browser of a type holding the cache You can also update the file and open the latest file.

  According to the FTP server means in the FTP processing apparatus of claim 7, since the host side automatically redirects to the next entity data reflecting the operation execution status of the next stage, the user himself / herself gives an instruction to access the link. It is possible to know the operation execution status without the trouble of performing.

  According to the FTP type processing apparatus of the eighth aspect, even if the host has a cache function, it always redirects and acquires new entity data, so the user always knows the next operation execution status. be able to.

  According to the FTP processing apparatus of the ninth aspect, the user can easily operate the storage medium connected to the intended connection unit.

  According to the FTP processing apparatus of the tenth aspect, the user can easily operate the intended type of storage medium.

  According to the FTP type storage device of the eleventh aspect, the user can easily grasp / acquire the directory and file structure of the storage medium connected to the FTP type processing device by the operation-corresponding link.

  According to the FTP type processing apparatus of the twelfth aspect, the user can obtain the actual data in the storage medium by the operation corresponding link.

  According to the FTP processing apparatus of the thirteenth aspect, the user can perform a formatting operation on the storage medium connected to the FTP processing apparatus.

  According to the FTP processing apparatus of the fourteenth aspect, the user can perform a file erasing operation on the storage medium connected to the FTP processing apparatus.

  According to the FTP type processing apparatus of the fifteenth aspect, the user can perform a file copy operation between the storage media on the storage medium connected to the FTP type processing apparatus.

  According to the sixteenth aspect, a network printer can be included as the FTP processing apparatus.

  According to the FTP system of the eighteenth aspect, since it is not necessary to input an address to the browser, the user can easily check the status and operate the storage medium connected to the FTP type processing apparatus from the host side.

  Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Note that the configuration of the FTP system described below is merely an example for embodying the present invention, and it is natural that the configuration can be appropriately changed without departing from the gist of the present invention. FIG. 1 is a block diagram showing a schematic configuration of the FTP system 1. In the FTP system 1, a printer 80 and a host device (personal computer: hereinafter also referred to as “PC”) 3 that uses the printer 80 as a network printer can communicate with each other via a network 410.

  The network 410 may be a wired network as illustrated or a wireless network.

  FIG. 2 shows an external configuration of the printer 80. The printer 80 is a so-called multi-function device (MFP), and is configured as a printer multi-function machine in which the multi-reader / writer 2 constituting the FTP processing device is incorporated in the printer. Specifically, a multi-reader / writer 2 disposed so as to expose media connection slots (hereinafter also simply referred to as “slots”) 16 to 19 on the front surface of the apparatus is integrally provided with a printer function, It has a scanner function, a copy function, and a facsimile function.

  Note that, instead of or in addition to the media connection slot, a USB connection unit may be provided and a USB memory as a storage medium may be connected, or a wireless connection unit may be provided and a wireless function as a storage medium may be provided. A configuration in which a memory card can be connected may be used.

  The printer 80 is connected to the PC 3 via a network and functions as a reader / writer device that performs data communication between the PC 3 and a memory card inserted into the multi-reader / writer 2. Also, based on the print data transmitted from the PC 3 (FIG. 1), an image or document is printed on a predetermined sheet. Further, based on the print data read from the memory card (storage medium) by the multi-reader / writer 2, an image or document is printed on a predetermined sheet (direct printing). It is also possible to transmit image data read by the scanner unit to the PC 3 and to copy an image read by the scanner unit using the printing unit.

  As shown in FIG. 2, the multi-reader / writer 2 of the printer 80 inserts the first slot 16 for inserting the first memory card 11 and the second memory card 12 as the media connection slots 16 to 19. The second slot 17, the third slot 18 for inserting the third memory card 13, and the fourth slot 19 for inserting the fourth memory card 14. Further, it may be configured to have a slot of another memory card (such as an xD picture card (registered trademark, hereinafter abbreviated as “XD”)).

  FIG. 3 is a block diagram showing an electrical configuration of the printer 80. The printer 80 includes therein a CPU 34 that controls each component, a ROM 35 that stores a control program, various data, and the like (in the present embodiment, a nonvolatile memory such as a flash memory), A RAM 37 serving as a work area for operations performed by the CPU 34 is connected to the RAM 34 so that data can be transferred between them. The slots 33 to 19 are connected to the bus 33 via flash memory control LSIs. Each of the first to fourth memory cards 11 to 14 detachably connected to the slots 16 to 19 is, for example, a CF, SM, MS, SD, or the like that can write, rewrite, erase, and read data. This is a card-type storage medium equipped with a memory. The slots 16 to 19 can alternatively be connected to any type of memory card.

  An operation / display unit 91 including a printing unit 82, a scanner unit 132, a telephone line I / F 133, an LCD, a keyboard, a cursor movement key, and the like is connected to the bus 33. Further, a LAN I / F 24 is connected to the bus 33. The LAN I / F 24 is connected to the PC 3 that is a host device via the first network. A plurality of PCs 3 and printers 80 are interconnected by a TCP / IP network 410 (see FIG. 1).

  The ROM 35 stores an operation control program for the multi-reader / writer 2 and control programs for controlling printing control, scan control, FAX communication control, and the like. The CPU 34 executes these programs using the RAM 37 as an execution area. Performs overall operation control as a printer multifunction peripheral.

  The ROM 35 further stores an FTP server program. The ROM 35 also stores an IP address and subnet mask for specifying the printer 80 on the TCP / IP network 410. Further, a status data transmission program for transmitting the status of the storage medium, and an operation compatible data transmission program for transmitting data including an operation compatible link associated with an operation in units of the storage medium to the host device. Stored in the ROM 35.

  Memory cards (storage media) 11 to 14 are connected to the media connection slots 16 to 19. The PC 3 includes a local disk 3L formed of a hard disk or the like and a monitor 3M formed of a liquid crystal display or the like, and a browser incorporating an FTP client program is installed in the local disk 3L.

  On the printer 80 side, the control program, the status reflection file name determination program, and the FTP server program described above are executed by the CPU 34, so that the FTP server means, the operation corresponding file name determination means, and the operation execution means are provided. Realized on the system.

  Hereinafter, the data sequence in the communication system 1 will be described with reference to the sequence diagram of FIG. This sequence diagram starts when the user starts up a browser on which the FTP client function is incorporated on the PC 3 side, inputs the node name “ftp: // brn_600789” of the printer 80, and starts access. Alternatively, a shortcut to the node name “ftp: // brn_600789” may be prepared on the PC 3 side, and the shortcut may be operated to access the printer 80 as it is after the browser is activated. The node name “ftp: // brn_600789” of the printer 80 may be changed as appropriate.

  First, in order to access the printer 80 (FTP server), the PC 3 (FTP client) connects with the 21st port assigned to FTP (J1). The printer 80 transmits a user name request response to the PC 3 (J2). In response to this, the PC 3 transmits a user name for logging in to the FTP server to the printer 80 (J3).

  Next, a password request response is transmitted from the printer 80 to the PC 3 (J4). Then, the PC 3 that has received the password request response transmits the password input in the previous host device to the printer 80 (J5). The printer 80 authenticates the login user based on the received password and user name, and returns a response permitting login to the FTP server (printer 80) of the login user to the PC 3 in the case of authentication acceptance (J6). .

Subsequently, the PC 3 permitted to log in to the FTP server issues a command “cd / (change directory root)” requesting access to the root directory (J7).
Upon receiving this command, the printer 80 accesses the root directory (attempts to change the current directory to the root directory), and returns a code indicating success to the PC 3 (J8).

  If access to the root directory fails, a response code “550” or the like is returned as described above. In this embodiment, even if the storage medium is not connected, a code indicating that the access to the root directory is successful is returned to the PC 3.

  The PC 3 receiving the code indicating that the access to the root directory is successful issues a list command for this root directory (J9). The printer 80 that has received the list command indicates that the directory including the file having the operation-corresponding file name determined by the state of the media connection unit and the operation-corresponding file name determining program exists in the root directory. Information is transmitted (J10).

  Hereinafter, the processing of the present invention will be described with reference to flowcharts and the like.

  FIG. 23 is a flowchart showing creation of a shortcut by the installer. The installer corresponding to the printer 80 creates a shortcut to Index.htm on the FTP server simultaneously with installation of software such as a printer driver (S1800). By creating a shortcut, the user can eliminate the trouble of inputting an IP address, a password, and the like necessary for connecting to the FTP server each time the connection is made.

  FIG. 24 is a flowchart showing the processing of the PC 3 when the shortcut is activated. A URL such as Index.htm on the FTP server is written in the shortcut, and the browser is started by giving the URL written in the shortcut as an argument to connect to the FTP server installed in the printer 80.

  FIG. 5 is an operational flow of FTP server processing executed by the CPU 34 in the printer 80 in accordance with the FTP server program. The FTP server process starts when the printer 80 is activated.

  In the FTP server process shown in FIG. 5, first, a virtual directory tree initialization process is executed, and a directory tree managed by the CPU in the FTP server process is formed on a memory such as a RAM (S100). Subsequently, preparation for connecting to a network device as an FTP server is performed, such as opening an FTP port (S110). Subsequently, steady operation processing such as reception of a file access request and response to the request is executed as an FTP server (S120). Thereafter, the printer 80 continues to operate normally until the printer 80 is turned off or reset.

  FIG. 6 is a flowchart showing in detail the initialization process of the virtual directory tree in S110. First, the CPU 34 secures a memory necessary for managing the configuration of the virtual directory tree and a memory necessary for managing the FTP server system in the RAM (S200).

  Subsequently, a management area for the root directory of the FTP server is secured in the virtual directory tree on the secured memory (S210). Subsequently, the management area for the secured root directory is initialized. Here, there is no directory name, the directory entity exists in the system area described above, the file name of the file stored in the directory does not exist (that is, there is no file in the directory), sub An attribute that there is no directory is set in the management area (S220).

  Subsequently, the root directory described above is recognized as the current directory (S230), and the initialization process of the virtual directory tree is terminated. By recognizing in this way, even when an FTP client (hereinafter also referred to as a client) accessing the FTP server transmits a list command without performing “cd /”, the printer 80 is in the current directory. File names and subdirectory names of files existing in the root directory are returned.

  FIG. 15A is a conceptual diagram showing a virtual directory tree formed by the initialization process of the virtual directory tree.

  FIG. 7 is a flowchart showing in detail the steady operation process in (S120) of FIG. First, when the initialization as the FTP server is completed, the CPU 34 enters a login wait state waiting for login from the client (see FIG. 4: J1) (S300).

  If there is no login request from the client (S310: NO), the login wait state is entered again. If there is a login request from the client (S310: YES), the login sequence is executed (S320) (see FIG. 4: J2 to J5). If the login sequence fails (S330: NO), the login wait state is entered again. .

  If the login sequence is successful (S330: YES), a code indicating successful login is transmitted to the client (see FIG. 4: J6), and an FTP command from the client is awaited (S340).

  If there is a “cd” command from the client (S350: YES), cd processing corresponding to the command is executed (S360).

  If there is a “list” command from the client (S370: YES), list processing corresponding to the command is executed (S380).

  If there is a “get” command from the client (S390: YES), a get process corresponding to the command is executed (S400).

  If there is a “put” command from the client (S410: YES), put processing corresponding to the command is executed (S420).

  If there is another command from the client, processing corresponding to the other command is executed (S430).

  If each process is executed or there is no command from the client, it is determined whether there is an instruction to end the program, such as in the shutdown process of the printer 80 (S440). If there is no instruction to end the program (S440: NO), the command wait state is entered again, and if there is an instruction to end the program (S440: YES), a shutdown process for ending the function as the FTP server is executed (S450). ) And end the steady operation.

  FIG. 8 is a flowchart showing in detail the cd process in S360 of FIG. In the cd processing, the directory specified by the cd command is recognized as the current directory, in other words, the current directory is switched.

  First, the CPU 34 creates virtual file information based on the current device state (S500). Subsequently, if the command specifies the target directory (S510: YES), the directory specified by the command from the client exists in the virtual directory tree or exists in the actual directory. Is determined (S520). If the specified directory exists in the virtual directory tree or exists in the actual directory (S520: YES), the specified directory is recognized as the current directory (S530), and the command is successful. An OK code indicating this has been transmitted to the client (S540), and the cd processing is terminated.

  In the FTP server process, unless the current directory is recognized again, the directory specified by the cd command is continuously recognized as the current directory.

  If the specified directory does not exist in the virtual directory tree and does not exist in the actual directory (S520: NO), the specified directory is not recognized as the current directory and the command has failed. Is transmitted to the client (S550), and the cd processing is terminated.

  On the other hand, if the command does not specify the target directory in S510 (S510: NO), it is recognized that the command specifies the current directory (S560), and the processing after S530 is executed. .

  FIG. 11 is a flowchart showing in detail the list process in S380 of FIG. In list processing, the file name of the file and directory directory name that exist in the directory specified by the list command are returned to the client. In other words, the client recognizes the list of files and directories in the directory specified by the client. To perform the process.

  First, the CPU 34 creates virtual file information based on the current device state (S600). Subsequently, if the command specifies the target directory (S610: YES), the directory specified by the command from the client exists in the virtual directory tree or exists in the actual directory. Is determined (S620).

  Subsequently, when the designated directory exists in the virtual directory tree or in the actual directory (S620: YES), the CPU 34 further identifies the designated directory in the system area. It is determined whether or not (S630). If the specified directory is within the system area (S630: YES), the file name and subdirectory name stored in the management area for the specified directory are transmitted to the client (S640), and the list process is terminated. .

  If the entity of the designated directory is not in the system area, in other words, in the storage device such as a storage medium (S630: NO), the file name and subdirectory name stored in the designated directory are given to the client. Transmit (S650), and the list process ends. That is, the file name and directory name of the file and directory actually stored in the storage medium or the like are transmitted.

  If the specified directory does not exist in the virtual directory tree and does not exist in the actual directory (S620: NO), an NG code indicating that the command has failed is transmitted to the client (S660), End the list process.

  On the other hand, if the command does not specify the target directory in S610 (S610: NO), it is recognized that the command specifies the current directory (S670), and the processes after S630 are executed. .

  FIG. 10 is a flowchart showing in detail the get process in S400 of FIG. In the get process, the entity data of the file specified by the get command is returned to the client, in other words, the client acquires the entity data of the file specified by the client. First, the CPU 34 creates virtual file information based on the current device state (S700).

  Subsequently, it is determined whether or not the command specifies a target file (S710). If the target file is specified, it is determined whether or not the command specifies the directory in which the file is targeted (where the target directory is) (S720).

  If the target directory is specified by the command (S720: YES), it is determined whether the directory specified by the command from the client exists in the virtual directory tree or the actual directory. (S730).

  If the specified directory exists in the virtual directory tree or exists in the entity directory (S730: YES), it is further determined whether or not the entity of the specified directory is in the system area. Judgment is made (S740). If the designated directory is within the system area (S740: YES), the memory card is operated based on the information stored in the designated directory management area (S750). If the file entity data can be acquired (S760: YES), the entity data is transmitted to the client (S770), and the get process ends.

  If the file entity data cannot be acquired (S760: NO), an NG code indicating that the command has failed is transmitted to the client (S780), and the get process ends.

  If the specified directory is not in the system area, in other words, in the storage device such as a storage medium (S740: NO), the actual data of the file stored in the specified directory is acquired (S790). ), The process after S760 is executed. That is, the actual data of the file actually stored in the storage medium or the like is transmitted.

  If the specified directory does not exist in the virtual directory tree and does not exist in the actual directory (S730: NO), an NG code indicating that the command has failed is transmitted to the client (S780), The get process ends.

  On the other hand, if the command does not specify the target directory in S720 (S720: NO), the command is recognized as specifying the file in the current directory (S800), and after S740. Execute the process. If the command does not specify the target file (S710: NO), an NG code indicating that the command has failed is transmitted to the client (S780), and the get process ends.

  FIG. 11 is a flowchart showing in detail the put process in S420 of FIG. In the put process, the entity data of the file transmitted from the client by the put command is stored in the storage device in the FTP server. In other words, the process of causing the FTP server to write the entity data of the file designated by the client is performed.

  First, the CPU 34 creates virtual file information based on the current device state (S900). Subsequently, it is determined whether or not the command specifies a directory for storing the file (target directory) (S910). If the target directory is specified by the command (S910: YES), it is determined whether the directory specified by the command from the client exists in the virtual directory tree or the actual directory. (S920). If the specified directory exists in the virtual directory tree or exists in the entity directory (S920: YES), it is further determined whether or not the entity of the specified directory is in the system area. Judgment is made (S930). If the entity of the designated directory is in the system area (S930: YES), an NG code indicating that the command has failed is transmitted to the client (S960), and the put process is terminated. That is, the content of the information that informs the FTP client of the state on the FTP server side, the operation that the FTP client can perform on the connected storage medium, and the file name of html data for operating the storage medium To prevent access to a virtual special directory provided for sending to the client. As a result, it is possible to prevent a situation in which the directory is not written because the user of the PC 3 thinks that the file entity data has been written, but the directory is virtual.

  If the specified directory is not in the system area, in other words, in the storage device such as a storage medium (S930: NO), the actual data is stored in the specified directory (S940), and the command succeeds. An OK code indicating this has been transmitted to the client (S950), and the put process is terminated. That is, the actual data is actually stored in a storage medium or the like. On the other hand, if the specified directory does not exist in the virtual directory tree and does not exist in the actual directory (S920: NO), an NG code indicating that the command has failed is transmitted to the client (S960). ), And put processing ends.

  On the other hand, if the command does not specify the target directory (S910: NO), it is recognized that the command specifies the file in the current directory (S970), and the processing after S930 is performed. Execute.

  12A and 12B are flowcharts showing in detail the virtual file information creation processing in FIGS. 8, 9, 10 and 11. FIG.

  In the virtual file information creation process, the creation of Index.htm to be browsed by the FTP client and the content of Main.htm are determined. In other words, the content is connected to the content of information that informs the FTP client of the state on the FTP server side. Processing for determining operations that can be performed by the FTP client on the storage medium is performed.

  Here, since the status of the printer 80 and the status of the storage medium connected to the media connection unit are confirmed, even if another storage medium is reconnected to the media connection unit, a new storage media Since the state can be reflected, the operation-corresponding file name corresponds to the connected memory card, so that it is less likely to select an incorrect operation.

  Here, it returns to description of a process.

  The CPU 34 first creates Index.htm and Main.htm.

  Index.htm describes a transfer command (redirect) to ftp: //brn_600789/Main.htm. This makes it possible to move to Main.htm by accessing Index.htm.

  Index.htm also describes a cache deletion command of ftp: //brn_600789/Main.htm. Some browsers keep the html file once accessed as a cache. When using such a browser, the previously accessed html file remains in the cache, so the updated html file may not be displayed. Since it is necessary to delete the cache deletion in order to display the updated html file, the cache deletion command is used. A display example of the generated Index.htm file is shown in FIG.

  At the stage of generation, the contents of Main.htm are empty, and the FTP server dynamically describes the contents according to the subsequent processing.

  Subsequently, the CPU 34 checks the status of the printer 80 (S1020). Information regarding the number of media connection units provided in the printer 80 and the types of storage media that can be connected to the media connection units is also acquired at this time.

  Subsequently, the CPU 34 substitutes 0 for the variable N (S1030). This N is a variable used in the program in order to confirm information about all media connections.

  Subsequently, the CPU 34 compares N with the number of media connection units (S1040). If N is less than the number of media connection units (S1040: NO), the CPU 34 checks whether a storage medium is connected to the Nth media connection unit (hereinafter also referred to as the Nth slot) (S1110).

  If a storage medium is connected to the Nth slot (S1110: YES), it is subsequently confirmed whether or not the storage medium has been formatted (S1120).

  If the storage medium in the Nth slot has been formatted (S1120: YES), then the CPU 34 confirms whether the storage medium connected to the Nth slot is open (S1130).

  If the storage medium connected to the Nth slot is in an open state (S1130 :), then the CPU 34 confirms the total storage capacity and the remaining storage capacity of the storage medium connected to the Nth slot (S1200). .

  Subsequently, the CPU 34 determines the state of the slot to be written to Main.htm (S1150). The state of writing is a corresponding card name, total storage capacity, remaining storage capacity, a link for starting formatting, and a link for opening a card.

  Subsequently, the process returns to S1040 again, and the series of processes in S1040 to S1150 is repeated until the confirmation of all the media connection portions of the printer 80 is completed (S1040: YES).

  If the confirmation has been completed for all the media connection portions of the printer 80 (S1040: YES), since the state relating to all the media connection portions has been confirmed, the process is repeated.

  After exiting from the repetition, the CPU 34 first confirms the number of slots (S1205). If there is only one recognized slot (S1205: YES), it is confirmed whether there is a link for opening the card in the slot state (S1210).

  If there is a link for opening the card in the slot state (S1210: YES), the CPU 34 writes a transfer command to Main.htm using the link for opening the card (S1215). FIGS. 14A (a-1) and 14A (a-2) show examples of screen displays when there is a link for opening a card in the slot state. FIG. 14A (a-1) is an example of Main.htm, and FIG. 14A (a-2) shows a situation where the browser opens the card according to the transfer command written in Main.htm.

  Subsequently, the CPU 34 writes a cache deletion command of the transfer destination indicated by the transfer command in Main.htm (S1220).

  Subsequently, the CPU 34 updates the management area information for the root directory (S1270). Specifically, the generated Index.htm and Main.htm are added to the root directory.

  After updating the management area information, the CPU 34 ends the virtual file information creation process.

  If there is no link for opening the card in the slot state (S1210: NO), the CPU 34 writes the slot state in Main.htm (S1265), and then updates the management area information for the root directory. In step S1270, the virtual file information creation process is terminated. As a case where there is no link for opening the card in the slot state, the memory card may be unformatted or not connected. Screen display examples are shown in FIGS. 14B (b-1) and 14B (b-2).

  On the other hand, when there are a plurality of recognized slots (S1205: NO), the CPU 34 substitutes 0 for the prepared variable X (S1225).

  Subsequently, the CPU 34 compares X and N. When X is smaller than N (S1230: NO), it is confirmed whether or not there is a link for opening the card in the slot state (S1235).

  If there is a link for opening the card in the slot state (S1235: YES), the CPU 34 uses the link for opening the card to send a transfer command to CardOpenX.htm (where X is the value of the variable X). Writing is performed (S1215).

  Subsequently, the CPU 34 writes a transfer destination cache deletion command indicated by the transfer command to CardOpenX.htm (S1245).

Subsequently, the CPU 34 writes the slot state in Main.htm (S1265), updates the information in the management area for the root directory (S1270), and ends the virtual file information creation process.
Display examples in the case where there are a plurality of recognized slots are shown in FIGS. 14C (c-1) to 14C (c-3). When “Open Memory Card” in FIG. 14C (c-1) is clicked on the browser, a page on which a transfer command for accessing the card is written is displayed for a while, and then the contents of the card are displayed on the browser. (See FIGS. 14C (c-2) and 14C (c-3)).

  FIG. 15B is a conceptual diagram showing a virtual directory tree after execution of the virtual file information creation process. The root directory includes Index.htm and Main.htm as files, and it can be seen that each media connection is handled as a directory.

  FIG. 16A is a conceptual diagram showing the system area after execution of the virtual file information creation process. It can be seen that Index.htm, Main.htm, and CardOpen1.htm are included as files in the system area.

  FIG. 17 is a flowchart showing the memory card operation process in S750 of FIG. In the memory card operation process, the memory card is operated (formatting, deleting a file in the memory card, etc.) according to the specified file.

  If the designated file is Index.htm (S1300: YES), the CPU 34 acquires Index.htm (S1300), and ends the memory card operation process. Not only the Index.htm acquisition process but also the file entity acquired by the memory card operation process is transmitted to the client in S770.

  If the specified file is Format000.htm (S1320: YES), the CPU 34 executes the processing of the FTP server when Format000.htm is requested (S1330), acquires Format000.htm (S1340), End the memory card operation process. A display example of Format000.htm is shown in FIG.

  If the specified file is FormatN.htm (N is the value of variable N. Variable N used here is a variable different from variable N used in creating virtual file information) ( (S1350: YES), the CPU 34 executes processing of the FTP server when FormatN.htm is requested (S1360), acquires FormatN.htm (S1370), and ends the memory card operation processing.

  When the designated file is Main.htm (S1380: YES), the CPU 34 acquires Main.htm (S1390), and ends the memory card operation process.

  When the designated file does not correspond to any of Index.htm, FormatN.htm, and Main.htm (S1380: NO), the CPU 34 determines the file entity based on the information stored in the management area for the designated directory. Is acquired (S1400), and the memory card operation process is terminated.

  FIG. 18 is a flowchart showing in detail the processing of the FTP server when Format000.htm is requested in S1330 of FIG. First, the CPU 34 starts formatting the memory card (S1500).

  Subsequently, the CPU 34 determines the contents of Format000.htm (S1510). The contents of Format000.htm are determined by a message indicating the format progress (0%), a transfer command for displaying FormatN.htm, and a cache deletion command for updating FormatN.htm. .

  Subsequently, the CPU 34 creates Format000.htm (S1520), sets a variable N indicating the progress of formatting to 1 (S1530), and then terminates the processing of the FTP server when Format000.htm is requested. .

  FIG. 19 is a flowchart showing in detail the processing of the FTP server when FormatN.htm is requested in S1360 of FIG. N is a variable set in S1530, and changes as the format progresses. First, the CPU 34 starts formatting the memory card (S1500).

  Subsequently, when the confirmed memory card has been formatted or the formatting has been completed (S1610: YES), the CPU 34 determines the contents of FormatN.htm (S1620). What is determined as the contents of FormatN.htm is a message indicating the progress of formatting (100%). Subsequently, the CPU 34 creates FormatN.htm (S1630), and ends the processing of the FTP server when FormatN.htm is requested.

  On the other hand, if the formatting is not completed (S1610: NO), the CPU 34 creates FormatN.htm (S1630), sets a variable N indicating the progress of formatting to 1, and then returns to the processing of S1610 to format the format. Repeat until is finished. Display examples of FormatN.htm are shown in FIGS. It can be seen that the degree of progress increases as the variable N increases. The timing for transferring FormatN.htm may be determined as appropriate.

  FIG. 16B is a conceptual diagram showing a system area after execution of processing of the FTP server when Format000.htm to FormatN.htm are requested. It can be seen that Format000.htm, FormatN.htm, etc. are included as files in the system area. Although not shown in the figure, Format000.htm, Format001.htm, Format002.htm, Format003.htm, ... are sequentially generated in the system area.

  FIG. 22 is a flowchart showing the monitoring process of the memory card connection unit (slot). Although the slot monitoring is a process independent of the FTP server, the slot state is always transmitted to the FTP server.

  First, the CPU 34 confirms slot increase / decrease or card connection / detachment (S1700). When the increase / decrease of the slot or the connection / detachment of the card is confirmed (S1700: YES), the CPU 34 confirms whether or not the actual directory of the current directory exists (S1710). If the card connection / disconnection is not confirmed (S1700: NO), the CPU 34 waits until the slot increase / decrease or the card connection / detachment is confirmed.

  When the actual directory of the current directory exists (S1710: YES), the CPU 34 returns to the process of S1700.

  On the other hand, if the actual directory of the current directory does not exist (S1710: NO), the CPU 34 recognizes that the root directory is the current directory, and returns to the processing of S1700.

  FIG. 25 is a flowchart showing processing of a steady operation of the browser in the PC 3. First, the PC 3 performs browser activation processing (S2000).

  Subsequently, the browser checks whether a link to the file has been clicked (S2010). If it is confirmed that the link has been clicked, the browser executes browser processing when the link to the file is clicked (S2070), and checks whether there is a browser termination instruction (S2050).

  When there is a browser termination instruction (S2050: YES), browser termination processing (S2060) is executed, and the browser's steady operation is terminated.

  On the other hand, when the link to the file is not clicked (S2010: NO), the browser checks whether the link to the directory is clicked (S2020). If it is confirmed that the link is clicked (S2020: YES), the browser executes the browser process when the link to the directory is clicked, and proceeds to the process of S2050.

  On the other hand, when the link to the directory is not clicked (S2020: NO), the browser checks whether or not the transfer command is written in the displayed html file (S2030). If it is confirmed that the transfer command is written (S2030: YES), the browser executes the transfer process (S2090), and proceeds to the process of S2050.

  FIG. 26 is a flowchart showing browser activation processing in S2000 of FIG. First, the browser determines whether a file is designated as an argument (S2100). When a file is specified as an argument (S2100: YES), the browser executes the browser process when the link to the file is clicked, and ends the activation process.

  If no file is specified as an argument (S2100: NO), the browser determines whether a directory is specified as an argument (S2110). When a directory is specified as an argument (S2110: YES), the browser executes browser processing when a link to the directory is clicked, and ends the startup processing.

  If a directory is not specified as an argument (S2110: NO), the browser requests the html file set on the browser home page from the server (S2120).

  Subsequently, the browser determines whether or not the html file set on the browser home page has been acquired (S2130). If the html file has been acquired (S2130: YES), the browser displays the acquired html file (S2140) and ends the activation process.

  When the html file set on the browser home page cannot be acquired (S2130: NO), the browser waits until the html file can be acquired.

  FIG. 27 is a flowchart showing the browser processing when the link to the file in S2150 of FIG. 26 is clicked. First, the browser requests the FTP server for the file written in the link (S2200). Subsequently, the browser checks whether the file has been acquired (S2210).

  If the file can be acquired (S2210: YES), the browser displays the acquired file and ends the browser processing when the link to the file is clicked.

  When the file cannot be acquired (S2210: NO), the browser waits until the file can be acquired.

  FIG. 28 is a flowchart showing browser processing when a link to a directory is clicked in S2160 of FIG. First, the browser requests the FTP server for a file list of the directory written in the link (S2300).

  If the file list can be acquired (S2310: YES), the browser displays the acquired file list and ends the browser processing when the link to the directory is clicked.

  When the file list cannot be acquired (S2310: NO), the browser waits until the file list can be acquired.

  FIG. 29 is a flowchart showing the transfer process in S2090 of FIG. First, the browser checks whether a cache deletion command is described in the displayed html file (S2400).

  If the cache deletion command is described in the html file (S2400: YES), the browser deletes the transfer destination cache (S2410). If the cache deletion command is not described in the html file (S2400: NO), the browser confirms the transfer destination (S2420).

  Subsequently, the browser confirms the transfer destination (S2420). If the transfer destination is a directory (S2420: YES), the browser requests a file list of the transfer destination directory from the server (list command) according to the transfer command written in the html file (S2430).

  Subsequently, the browser confirms whether the file list has been acquired (S2440). If the file list can be acquired (S2440: YES), the browser displays the acquired file list (S2450) and ends the transfer process. When the file list cannot be acquired (S2440: NO), the browser waits until the file list can be acquired.

  On the other hand, if the transfer destination is not a directory (S2420: NO), the browser requests the server for the transfer destination file (get command) according to the transfer command written in the html file (S2460).

  Subsequently, the browser confirms whether the file has been acquired (S2470). If the file can be acquired (S2470: YES), the browser displays the acquired file (S2480) and ends the transfer process. When the file cannot be acquired (S2470: NO), the browser waits until the file can be acquired.

  The printer 80 is shown as an example of the FTP processing apparatus. However, the scanner apparatus, the display apparatus, the audio apparatus, the karaoke apparatus, the digital camera apparatus, the projector apparatus, the disk drive apparatus, the sewing machine, the telephone, the mobile apparatus, and the machine apparatus. It is obvious that the present invention may be applied to any apparatus that has an FTP server function and can have a media connection unit, such as a robot.

The block diagram which shows the outline of the whole structure of the FTP system of this invention. FIG. 2 is a perspective view illustrating an example of a printer applied to the FTP system of the present invention. FIG. 3 is a block diagram illustrating an example of an electrical configuration of a printer (card reader). The sequence diagram which shows an example of operation | movement of the FTP system of this invention. 7 is a flowchart showing FTP server processing in the printer 80. 7 is a flowchart showing virtual directory tree initialization processing in the printer 80. 7 is a flowchart showing steady operation processing in the printer 80. 7 is a flowchart showing cd processing in the printer 80. 7 is a flowchart showing list processing in the printer 80. 7 is a flowchart showing get processing in the printer. 7 is a flowchart showing put processing in the printer 80. 7 is a flowchart showing in detail a pre-process for creating virtual file information in the printer 80. 6 is a flowchart showing in detail a subsequent process of creating virtual file information in the printer. Display example of the generated Index.htm file. Screen display example of Main.htm file when there is a link to open the card in the slot state. Screen display example of Main.htm file when there is no link to open the card in the slot state. Screen display example of Main.htm file when multiple slots are recognized. The conceptual diagram which shows a virtual directory tree. The conceptual diagram which shows a system area | region. 7 is a flowchart showing memory card operation processing in the printer 80. 7 is a flowchart showing processing of the FTP server when Format000.htm is requested in the printer 80. 7 is a flowchart showing in detail the processing of the FTP server when FormatN.htm is requested in the printer 80. A display example of Format000.htm on the printer 80. A display example of FormatN.htm on the printer 80. 7 is a flowchart showing monitoring processing of a memory card connection unit in the printer 80. 7 is a flowchart showing creation of a shortcut by an installer in the printer 80. 7 is a flowchart showing processing of the PC 3 when a shortcut is activated in the printer 80. The flowchart which showed the process of the steady operation | movement of the browser in PC3. The flowchart which showed the starting process of the browser in PC3. The flowchart which showed the process of the browser when the link to a file was clicked in PC3. The flowchart which showed the process of the browser when the link to the directory was clicked in PC3. The flowchart which showed the process of the browser at the time of the transfer process in PC3.

Explanation of symbols

1 FTP system 2 Multi-reader / writer 3 Personal computer 3L Local disk 3M Monitor 11 First memory card (CF)
12 Second memory card (SM)
13 Third memory card (MS)
14 4th memory card (SD)
16 Media connection slot (first slot)
17 Media connection slot (second slot)
18 Media connection slot (3rd slot)
19 Media connection slot (4th slot)
24 LAN I / F
33 bus 34 CPU
35 ROM
37 RAM
80 Printer 82 Printing Unit 91 Operation / Display Unit 152 File Icon 153 with Operation Corresponding File Name Operation Corresponding File Name 410 Network

Claims (17)

A media connection for connecting storage media ;
Server means conforming to a protocol in which a procedure for transmitting a command indicating a directory name specification, a file name specification, and a file unit operation from the host device to the server device is defined ;
A media connection device comprising :
The server means includes
Storing the storage medium and a media-compatible directory name in association with each other;
When a file operation command indicating a media-compatible directory name specification, one file name specification, and a file operation request for each file is received from a host device connected via a network by the procedure defined in the protocol, A storage medium corresponding to the media-corresponding directory name is stored, and the file operation is performed in units of files for a file having the one file name ,
The server means further includes:
Remember the hypertext file name,
An operation-corresponding file name storage means for storing a media operation in units of the storage medium including at least one of the format of the storage medium and the opening of the storage medium, and an operation-corresponding file name in association with each other;
A file operation command indicating the designation of a virtual directory name different from the media-corresponding directory name, the designation of the operation-corresponding file name, and a file operation request in units of files is transmitted to the media connection device according to the procedure determined by the protocol. Generating a hypertext file including an operation corresponding link for causing the host device to execute processing;
A file indicating a virtual directory name designation different from the media-corresponding directory name, a hypertext file name designation, and a data operation request in units of files from a host device connected via a network according to a procedure defined by the protocol When an operation command is received, the hypertext file is returned to the host device,
From the host device that has received the hypertext file, designation of the virtual directory name, designation of one operation-corresponding file name stored in the manipulation-corresponding file name storage means, and data operation in units of files in accordance with the procedure determined by the protocol When a file operation command indicating a request is received, the media operation corresponding to the one operation-compatible file name is executed on the storage medium;
A media connection device characterized by that. The protocol defines a procedure for transmitting a command indicating an operation request in units of directories from the host device to the server device,
The server means includes
Corresponding to the media-compatible directory name when a list request command indicating the media-compatible directory name designation and file name list request is received from the host device connected via the network according to the procedure defined by the protocol. Returns a list of file names stored in the storage medium to the host device,
The server means further includes:
When receiving a list request command indicating a designation of the virtual directory name and a file name list request by a procedure defined by the protocol from a host device connected via a network, the hypertext file name is set to the host Reply to the device,
The media connection device according to claim 1. The server means includes
In a mode that the host device can display so that a user's click operation can be accepted, the hypertext file name is returned.
The media connection device according to claim 2, wherein: The server means includes
A storage medium is connected to the media connection unit, a storage medium connected to the media connection unit is formatted, a storage medium connected to the media connection unit is accessible, or connected to the media connection unit Detecting at least one of the capacity of the stored storage medium and the free capacity of the storage medium connected to the media connection unit;
Generating the hypertext file to include state information indicating the detected state;
The media connection device according to any one of claims 1 to 3, wherein 5. The server unit according to claim 1, wherein the server means generates progress data that is data indicating the progress of the operation by executing the operation, and transmits the progress data to the host device . The media connection device according to item 1 . 6. The media connection device according to claim 5 , wherein the server means transmits data including a link to the progress data to the host device. The media connection device according to claim 6 , wherein the server means transmits data including a command for deleting cache data relating to a link destination to the host device together with a link to the progress data . 8. The server according to claim 5 , wherein the server unit transmits a link to the progress data and redirect instruction data for instructing redirection to the link to the host device . 9. Media connection device. The server means, along with the progress data, provides a link to the next progress data, which is data indicating the progress of the next stage operation, and redirect instruction data for instructing redirection to the link. 9. The media connection device according to claim 5 , wherein the media connection device transmits the data to a host device . The media connection device is provided with a plurality of media connection units,
The media connection device according to claim 1 , wherein the operation corresponding link corresponds to an operation on a storage medium connected to any one of the media connection units. Different types of storage media can be connected to the media connection,
The media connection device according to any one of claims 1 to 10, wherein the operation-corresponding link corresponds to an operation on any type of storage medium . 12. The operation corresponding link corresponds to an operation of transmitting a file name or a directory name in a storage medium connected to the media connection unit to the host device. The media connection device described. 13. The media connection device according to claim 1, wherein the media connection device is incorporated in a network printer capable of executing printing based on print data transmitted via the network . The media connection device according to claim 1 , wherein the protocol is an FTP protocol . A media connection for connecting storage media;
Server means conforming to a protocol in which a procedure for transmitting a command indicating a directory name specification, a file name specification, and a file unit operation from the host device to the server device is defined;
A media connection device comprising:
A host device connected to the media connection device via a network;
A media connection system comprising:
The server means includes
Storing the storage medium and a media-compatible directory name in association with each other;
When a file operation command indicating a media-compatible directory name specification, one file name specification, and a file operation request for each file is received from a host device connected via a network by the procedure defined in the protocol, A storage medium corresponding to the media-corresponding directory name is stored, and the file operation is performed in units of files for a file having the one file name ,
The server means further includes:
Remember the hypertext file name,
An operation-corresponding file name storage means for storing a media operation in units of the storage medium including at least one of the format of the storage medium and the opening of the storage medium, and an operation-corresponding file name in association with each other;
A file operation command indicating the designation of a virtual directory name different from the media-corresponding directory name, the designation of the operation-corresponding file name, and a file operation request in units of files is transmitted to the media connection device according to the procedure determined by the protocol. Generating a hypertext file including an operation corresponding link for causing the host device to execute processing;
A file indicating a virtual directory name designation different from the media-corresponding directory name, a hypertext file name designation, and a data operation request in units of files from a host device connected via a network according to a procedure defined by the protocol When an operation command is received, the hypertext file is returned to the host device,
From the host device that has received the hypertext file, designation of the virtual directory name, designation of one operation-corresponding file name stored in the manipulation-corresponding file name storage means, and data operation in units of files in accordance with the procedure determined by the protocol When a file operation command indicating a request is received, the media operation corresponding to the one operation-compatible file name is executed on the storage medium;
A media connection system characterized by that. The media connection system according to claim 15 , wherein the host device stores a shortcut file to the file having the predetermined file name . A media connection for connecting storage media;
Server means conforming to a protocol in which a procedure for transmitting a command indicating a directory name specification, a file name specification, and a file unit operation from the host device to the server device is defined;
A media connection device equipped with
The server means includes
Storing the storage medium and a media-compatible directory name in association with each other;
When a file operation command indicating a media-compatible directory name specification, one file name specification, and a file operation request for each file is received from a host device connected via a network by the procedure defined in the protocol, A storage medium corresponding to the media-corresponding directory name is stored, and the file operation is performed in units of files for a file having the one file name,
The server means further includes:
Remember the hypertext file name,
An operation-corresponding file name storage means for storing a media operation in units of the storage medium including at least one of the format of the storage medium and the opening of the storage medium, and an operation-corresponding file name in association with each other;
A file operation command indicating designation of a virtual directory name different from the media-corresponding directory name, designation of the operation-corresponding file name, and file operation request in units of files is transmitted to the media connection device in accordance with a procedure determined by the protocol. Generating a hypertext file including an operation corresponding link for causing the host device to execute processing;
A file indicating a virtual directory name designation different from the media-corresponding directory name, a hypertext file name designation, and a data operation request in units of files from a host device connected via a network according to a procedure defined by the protocol When an operation command is received, the hypertext file is returned to the host device,
From the host device that has received the hypertext file, designation of the virtual directory name, designation of one operation-corresponding file name stored in the manipulation-corresponding file name storage means, and data operation in units of files in accordance with the procedure determined by the protocol When a file operation command indicating a request is received, the media operation corresponding to the one operation-compatible file name is executed on the storage medium;
A method of operating a media connection system, characterized by:

Images