JP4110133B2 - Image supply apparatus and control method thereof - Google Patents

Description

  The present invention relates to an image supply apparatus and a control method thereof.

  Recent printers have sufficient print quality. For example, even when a natural image is printed, the quality is comparable to that of a photograph.

  On the other hand, it is natural that digital still cameras (hereinafter referred to as DSC) have millions of imaging pixels, and the quality of captured images is comparable to silver halide cameras.

  From such a background, it is desired to print an image photographed with a digital camera with a printer without using a personal computer (hereinafter referred to as a PC), and several products have appeared.

  One of them is that DCS uses removable storage media (generally, there are various types of memory cards using flash memory), and the storage media is taken out from the DSC and placed in the slot of the printer. By setting the storage medium, image data is read out and printed.

  If all the images stored in the storage medium are printed one by one, the images stored in the storage medium can be read out unconditionally sequentially and printed, so no special technical problem occurs.

  However, in reality, there is a demand for selecting an image to be printed and an image not to be printed, and / or designating the number of prints for each image.

  One solution for this is a technology called DPOF (Digital Print Order Format). Briefly described is as follows.

  In general, a DSC is provided with a liquid crystal display for confirming a photographed image and for displaying various menus, and various keys (buttons) are also prepared. Using this, the image to be printed is selected and the number of copies to be printed is designated. This designated content is stored as a file in the storage medium storing the image. When this storage medium is set in the printer, an image print process is performed in accordance with the file in which the above instruction content is described.

  The above is the outline of DPOF. If both the DSC and the printer support DPOF, the above functions can be realized.

  As described above, the print request content generated on the DSC side is a DPOF format text file. Naturally, DSC is expected to become more multifunctional and to describe information other than the image to be simply printed and the number of copies to be printed. For example, more detailed designations such as designation of the size of the image to be printed, designation of the size of the recording paper to be printed, and designation of a desired layout of a plurality of images on one recording paper can be considered.

  However, the problem here is that even if such a setting can be made using the DSC, it is performed at a place unrelated to the printer. For example, even in a DPOF compatible printer, there are various sizes of recording paper set, so that it may naturally be different from that set in the DSC.

  As described above, the above-described problem is caused by the fact that the setting for printing with DSC is performed at a place unrelated to the printer.

  Therefore, further measures are desired. One of the solutions is to enable direct communication between the DSC and the printer by using a USB (Universal Serial Bus) which is a PC connection interface normally provided in the DSC.

If such an environment can be constructed, the DSC side can know the capabilities of the printer, and the conditions for printing can be set after reflecting the capabilities (or functions and states). Such a problem is solved at a stretch. However, in this case, it is necessary to solve the following problems.
1. Since the printer connected to the DSC is not unique, it is difficult to construct the DSC user interface in a state that reflects the capabilities of the printer. This is because items in the capabilities of the printer (for example, usable recording medium size, type, print quality, layout, etc.) are not independent, and linked items differ for each printer.
2. Usually, the DPOF file is stored in a removable medium such as a CF card. Many cameras support a subset of the DPOF specification, and whether or not a DPOF file stored in a removable medium can be analyzed by another camera depends on the subset of the DPOF specification supported by the camera.

  For the above two reasons, it is possible to analyze the DPOF file by the printer by constructing the “DPOF Print” button etc. in the DSC and sending the DPOF file to the printer, but specifying the file to be used on the interface The method and the file designation method in the DPOF file are not necessarily the same. Although both are print instructions, if the print designation methods are different, the user is confused.

  In addition, even if the DSC is physically connected directly to the printer using the interface provided by the DSC, how to specify individual images on the DSC side by the protocol used on the interface becomes a problem.

  As described above, in DPOF, the description of the print instruction content is in a text format. Therefore, the description for designating an image directly uses the name of the directory in which the image file is stored and the file name.

  On the other hand, when the DSC and the printer are connected, PTP (Picture Transfer Protocol) is followed. The problem here is that even if the DSC transfers the file describing the DPOF format print instruction content to the printer, the printer requests the DSC for the file described by the path name as described above. It is a point that cannot be done. This is because PTP does not provide a command for designating a file with a path name.

  Although DPOF has been described so far, the same can be said for a description language in which a screen is configured by linking image files with path names, such as markup languages such as HTML and XML.

  The present invention has been made in view of such a problem, and even when the image supply apparatus has a print request list described by the file name of the image, image transfer is performed with the image supply apparatus using a handler. It is intended to provide technology that makes it possible to perform

In order to solve this problem, for example, an image supply apparatus of the present invention has the following configuration. That is,
Directly communicates with the image processing apparatus, receives a transmission request from the image processing apparatus using a numbered handle for specifying image data to be processed, and processes the image specified by the handle with the image processing An image supply device for supplying to the device,
Before connecting to the image processing apparatus, a designation means for designating an image to be processed in advance;
Storage control means for storing in a storage medium image designation information different from the predetermined handle as information for designating the processing target image designated by the designation means;
Determining means for determining whether or not the image designation information exists in the storage medium when communication with the image processing apparatus is enabled;
Display means for displaying that there is no image designation information when the judgment means determines that the image designation information does not exist in the storage medium;
A conversion unit that converts the image designation information into the predetermined handle when the determination unit determines that the image designation information exists in the storage medium ;
An image supply apparatus comprising: output means for outputting information converted by the conversion means to the image processing apparatus.

  According to the present invention, even when there is a print request list described with information different from a predetermined handler such as an image file name, the system that transfers image data with a predetermined handle is intended. It is possible to transfer and print street images.

  Embodiments according to the present invention will be described below with reference to the accompanying drawings.

<Description of basic configuration>
First, the basic part in the present embodiment will be described. Hereinafter, a method for printing video stored in a storage medium in the DSC in an environment where the printer can directly communicate with a digital still camera (DSC) will be referred to as a photo direct printing method.

  FIG. 1 is an external view of an apparatus of a photo direct printer (referred to as a PD printer) in the embodiment, and FIG. 2 illustrates a direct connection of a DSC to a printer.

  In FIG. 1, this PD printing apparatus 1000 directly reads image data stored in a storage medium such as a memory card and a function as a normal PC printer that receives data from a host computer (PC) and prints it. A function for printing (DPOF function) and a function for receiving and printing image data from the DSC by directly communicating with a digital camera described below are provided.

  The main body that forms the outer shell of the PD printing apparatus 1000 includes exterior members such as a case M1001, an upper case 1002, an access cover 1003, and a discharge tray 1004. The lower case 1001 forms a substantially lower half of the PD printing apparatus 1000, and the upper case 1002 forms a substantially upper half of the main body. A combination of both cases accommodates the mechanisms described below. A hollow body structure having a space is formed, and openings are formed in the upper surface portion and the front surface portion, respectively. Further, one end of the discharge tray 1004 is rotatably held by the lower case 1001, and an opening formed on the front surface of the lower case 1001 can be opened and closed by the rotation. For this reason, when executing the recording operation, the discharge tray 1004 is rotated to the front side to open the opening, so that the recording sheets can be discharged from here and the discharged recording sheets are sequentially stacked. It has come to be able to do. In addition, the discharge tray 1004 stores two auxiliary trays 1004a and 1004b. By pulling out each tray as needed, the sheet support area can be expanded or reduced in three stages. It has become.

  One end of the access cover 1003 is rotatably held by the upper case 1002 so that an opening formed on the upper surface can be opened and closed. By opening the access cover 1003, the access cover 1003 is accommodated inside the main body. It is possible to replace the recording head cartridge (not shown) or the ink tank (not shown). Although not particularly shown here, when the access cover 1003 is opened and closed, the protrusion formed on the back surface rotates the cover opening and closing lever, and the rotation position of the lever is detected by a micro switch or the like. Thus, the open / closed state of the access cover can be detected.

  A power key 1005 is provided on the upper surface of the upper case 1002 so that it can be pressed. The upper case 1002 is provided with an operation panel 1010 having various key switches and the like. An automatic feeding unit 1007 automatically feeds the recording sheet into the apparatus main body. Reference numeral 1008 denotes a paper interval selection lever, which is a lever for adjusting the interval between the print head and the recording sheet. Reference numeral 1009 denotes a card slot into which an adapter capable of mounting a memory card is inserted. As this memory card, for example, there are a Compact Flash (registered trademark) memory (R), a smart media (R), a memory stick (R), and the like. By using the memory card from the DSC and setting it, This is used as a printing function by the conventional DPOF.

  Reference numeral 1012 denotes a terminal for connecting a digital camera to be described later. Usually, a digital camera often uses a USB (Universal Serial Bus) as a means for connecting to a personal computer (PC). Therefore, in this embodiment, the terminal 1012 adopts a USB interface. Communication means may be used. In addition, the connection with the digital camera can be performed from the front as shown in the drawing in order to simplify the connection work.

  On the other hand, the PD printing apparatus 1000 includes an interface for realizing printing from a personal computer (PC). Normally, once connected to the PC, the connection state is maintained unless there are special circumstances, so the interface terminal is provided on the back side. The connection interface between the PCs may be a Centronics specification parallel interface, USB interface, or the like, but at least supports a bidirectional communication function.

  FIG. 2 shows a state in which the PD printing apparatus 1000 according to this embodiment and the digital camera 3012 are connected.

  In the figure, a cable 5000 (USB cable) includes a connector 5001 for connecting to the connector 1012 of the PD printing apparatus 1000 and a connector 5002 for connecting to the connection connector 5003 of the digital camera 3012. Note that when the digital camera 3012 is connected to a PC, the captured image can be transferred to the PC by connecting the connector 5001 to a USB connector included in the PC.

  The digital camera 3012 is configured to be able to output image data stored in an internal memory via a connection connector 5003. Note that as the configuration of the digital camera 3012, various configurations such as a configuration having a memory as a storage unit inside and a configuration having a slot for mounting a removable memory can be employed. As described above, by connecting the PD printing apparatus 1000 and the digital camera 3012 via the cable 5000 shown in FIG. 2, the image data from the digital camera 3012 can be directly printed by the PD printing apparatus 1000.

  FIG. 3 is a block diagram of a control system of the PD printer 1000 according to the embodiment.

  In the figure, 1 is a CPU that controls the entire apparatus, 2 is a ROM that stores an operation processing procedure (program) of the CPU 1 and fonts, and 3 is a RAM that is used as a work area of the CPU 1. Reference numeral 4 denotes an operation panel (corresponding to 1010 in FIG. 1). Reference numeral 5 denotes an interface for connecting to a PC, and reference numeral 7 denotes an interface (USB host side) for connecting to a digital still camera. Reference numeral 9 denotes a card interface to which an adapter (PCMCIA) 10 equipped with a memory card can be connected. The PD printer 1000 reads a description file relating to a print instruction in a memory card that is photographed and stored by DPOF, that is, a digital camera. For printing accordingly. A printer engine unit 6 is a print engine that discharges ink liquid using thermal energy in the embodiment, but the recording method is not limited to this. Reference numeral 11 denotes an interface for connecting an expansion device. As will be described in detail later, a display device or the like for displaying an image prepared as an option can be connected.

  FIG. 4 is a block diagram of a DSC (digital still camera) 3012. In the figure, 31 is a CPU that controls the entire DSC, and 32 is a ROM that stores the processing procedure (program) of the CPU 31. Reference numeral 33 denotes a RAM used as a work area for the CPU 33, and reference numeral 34 denotes a switch group for performing various operations. A liquid crystal display 35 is used for confirming a captured image and displaying a menu for performing various settings. An optical unit 36 is mainly composed of a lens and its driving system. 37 is a CCD element, and 38 is a driver for controlling the optical unit 36 under the control of the CPU 31. Reference numeral 39 denotes a connector for connecting a storage medium 40 (compact flash (registered trademark) memory card, smart media, etc.), and 41 is a USB interface (USB slave side) for connecting to a PC or the PD printer 1000 in the embodiment. ).

  The above is the description of the configuration of the PD printer and DSC in the embodiment. It should be noted that the memory card is extracted from the DSC 3012, set in the slot 1009 of the PD printer 1000, and printed according to the print instruction file stored in the memory card. The description will be omitted, and the description thereof will be omitted. In the present embodiment, a case will be described in which the DSC 3012 and the PD printer 1000 are connected by a cable 5000 and can communicate directly.

  FIG. 5 shows a connection layer when this direct connection is established. In the drawing, the upper side shows a DSC (digital camera) side layer, and the lower side shows a PD printer side layer.

  In the case shown in the figure, SCSI and wireless TCP / IP are also shown as communication means, but here, connection with a USB interface will be described.

  In the illustrated layer structure, in the case of USB communication, a well-known PTP (Picture Transfer Protocol) is used. In the embodiment, since the DSC 3012 uses a USB interface prepared for connecting to a PC and connects it to a PD printer, the DSC 3012 functions as a USB slave and the PD printer 1000 functions as a USB host. become. That is, it should be noted that when in the connected state, the control as the system is on the PD printer 1000 side.

  FIG. 6 shows a general communication procedure using PTP. In order to facilitate understanding, in the case of the embodiment, the USB host is a PD printer, and the DSC 3012 is a USB slave.

  First, in step 1400, the PTP command GetDeviceInfo is transmitted from the PD printer 1000 to the DSC 3012. At this stage, it is easy to understand that the PD printer inquires about the connected device because the connected device is unknown. In response to this, the DSC 3012 transmits (notifies) information related to the DSC 3012 to the PD printer 1000 using DeviceInfo Dataset.

  Next, in step 1402, the DSC 3012 is allocated as a resource by the PTP command OpenSession, and a procedure for assigning a handle to a data object or performing special initialization as required is started.

  In step 1403, a handle is requested from the DSC 3012. This is because the PD printer 1000 requests a number uniquely assigned to an object owned by the DSC 3012 in order to identify an unknown object (such as a photographed image or script) that the DSC 3012 has. In response to this request, the handle list held in the DSC 3012 is returned in step 1404 (equivalent to notifying how many objects are present).

  As a result, the PD printer 1000 can determine how many objects the DSC holds (printing instruction file (hereinafter referred to as DPOF file) by DPOF, captured image file).

  Thereafter, when the PD printer inquires what the i-th object is, the attribute information about the i-th object (whether the object is an image or text such as a script) is obtained by GetObjectinfo (i ) And the result is received as Objectinfo i Dataset (step 1405).

  By repeating this procedure, the PD printer 1000 can know the attributes of all objects owned by the DSC 3012.

  If the attribute is image data, the PD printer issues a GetObject using the handle indicating the image data, and as a result, the image data can be obtained by receiving it as SendObjectInfo (step 1406). .

  Information can be exchanged with each other in the above-described procedure, but the problem here is that in PTP, the PD printer 1000 uses the memory card of the DSC 3012 to store the image file to be printed. It is a point that cannot be directly requested using a path name.

  It is as follows to explain more clearly.

  It is assumed that the designation of an image to be printed and the setting of the number of copies have already been performed using the UI of the DSC 3012. That is, this is the case where the corresponding DPOF file has already been stored in the memory card of the DSC 3012 (however, the setting for printing will be described later after connection with the PD printer). Since the process itself for creating the DPOF file is known, the details are omitted here.

  In such a situation, the PD printer 1000 can know which object is the handle of the DPOF file (which has already been described in the text format) with GetObjectInfo. Therefore, it is possible to get the contents of the file with GetObject using the handle. However, even if the PD printer 1000 receives this file, the description for specifying the image described in the file is the directory name + directory name + ... + file name traced from the root of the memory card 40. There is no way in PTP to request this file directly. That is, since there is nothing other than acquisition using the handle, printing using the DPOF file cannot be performed.

  Therefore, this embodiment solves this problem. An example for solving the problem will be described below.

<First example>
FIG. 7 shows an example of the contents of a DPOF file created by the DSC 3012.

In the case of illustration, each image to be printed is
../DCIM/105GANON/IMG_0572.JPG
../DCIM/105GANON/IMG_0573.JPG
It is two lines indicated by.

  This means that there is a directory called “DCIM”, in which there is a further directory called “105GANON”, and the file name “IMG_0572.JPG” or “IMG_0573.JPG” is designated as the print target. Is shown.

Even if the PD printer receives a file with such a description from the DSC 3012, it cannot request the file for the reason described above.
Therefore, when the DSC 3012 in the embodiment is in a state where direct communication with the PD printer 1000 can be performed, and the DPOF file exists in the internal memory card 40, the file name with a path described therein is used. Then, a new file (hereinafter referred to as a print instruction document or a print instruction file) converted into information indicating an internal handle is created.

For example,
../DCIM/105GANON/IMG_0572.JPG handle "00000001"
../DCIM/105GANON/IMG_0573.JPG handle "00000002"
In this case, the file (text) shown in FIG. 8 is created as a print instruction by performing the conversion process. In the figure, <image (00000001)> and <image (00000002)> indicate a part converted into a handler for specifying a file.

  There is no difference that the converted print instruction file is also an object, and a handler is also assigned to that object, so the timing of this conversion is the initial stage when the DSC 3012 is connected to the PD printer 1000. To do. For example, as shown in FIG. 6, when GetDeviceInfo or OpenSession is received from the PD printer, the conversion process is started. In the embodiment, the CPU 31 in the DSC 3012 performs the conversion process of the DPOF file using the reception of OpenSession as a trigger.

  From the perspective of the PD printer 1000, it appears that there are at least two files having the text attribute in the DSC 3012 (DPOF file and print instruction file after conversion), and the contents of each are received by the GetObject command. Then, printing is performed using a character string indicating a specific command (for example, <command (DPS_Job)> in FIG. 8).

  That is, by receiving the data in the format shown in FIG. 8, the image data requested for printing by the user can be received by the GetObject command using the handles “00000001” and “00000002”, that is, the intended image is printed. Will be possible, and the problems described above will be solved at once.

  In order to realize the above processing, the DSC 3012 may perform the processing shown in FIG. This figure is a process called when an OpenSession command is received, and it is assumed that handles for other objects have been established before this.

  First, in step S1, it is determined whether or not there is an instruction file related to printing by DPOF created according to the contents set in the previous print setting process in the memory card 40. If it does not exist, it is treated as an error. For example, processing such as displaying a message indicating that there is no print instruction content on the display panel 4 or no setting for printing may be performed.

  On the other hand, if it is determined that DPOF exists, a new file (print instruction) is created by replacing the file name with a path name described therein with a handle (step S2). In step S3, a new handle is assigned to the created file, and this process ends.

  On the other hand, the PD printer 1000 may perform the processing shown in FIG. It is assumed that the initial communication establishment process when the DSC is connected has already been completed.

  First, in step S11, a DPOF file converted file (print instruction) is acquired from the connected DSC 3012. As described above, this is performed by receiving an object having a text attribute and acquiring a file in which a character string serving as a specific key exists.

  In step S12, the file acquired in step S11 is analyzed, and the handle of the image to be printed is acquired. In step S13, data (image data) indicated by the handle is requested (which can be realized by the GetObject command). As a result, the received image data is received (step S14), and printing processing is performed (step S15).

  Then, the processes in and after step S12 are repeated until it is determined that the above process has been performed for all requests.

  As a result, even in a situation where the digital camera and the printer communicate directly, it is possible to print only the image as intended by the user.

<Second example>
The first example is based on the assumption that before connecting the DSC 3012 to the PD printer 1000, an image to be printed is selected using the UI of the DSC 3012 and the result is stored as a DPOF file. .

  In the second example, after the DSC 3012 is connected to the PD printer 1000, the DSC 3012 acquires the function of the PD printer being connected, and sets the conditions for printing according to the function of the printer. Will be described.

  There are two points to note. One is that it is necessary to notify the DSC 3012 of the functions of the PD printer 1000 (such as the printable paper size). In the second example, the DPOF file is created using the DSC 3012 UI after the connection with the PD printer. At the time of connection, the memory card of the DSC 3012 is created. Reference numeral 40 denotes that the DPOF file and the print instruction file after the conversion process do not exist (that is, there is no handle indicating them).

  First, as for the first point, in the case of PTP, a command SendObjectInfo for inquiring whether information can be transmitted from the host side (PD printer) to the slave side (DSC 3012) is prepared. Is used (see FIG. 11). In other words, the PD printer 1000 prepares a text file describing items indicating its own function in advance (for example, stores it in the ROM 2), and issues a request SendObjectInfo to the DSC 3012 so that the DSC 3012 makes the request. It is judged whether or not to accept (OK is returned when accepted). When this OK is returned, the PD printer notifies the DSC 3012 of a file describing its function information (SendObject, ObjectData).

  Regarding the second problem, a handle is reserved in advance for the DPOF file and the print instruction file that is the conversion result of the DPOF file. For example, a handle “00000001” is reserved in advance for the DPOF file and a handle “00000002” is reserved in advance in the print instruction file, and when assigning a handle to another object, the other is assigned.

  Therefore, the processing will be as follows.

  First, when the PD printer and the DSC 3012 are connected, the PD printer 1000 (the CPU 1 thereof) transmits information indicating its function to the DSC 3012. In response to this, the DSC 3012 uses its own UI to make various settings within the range allowed by the function of the connected PD printer 1000 as well as the selection and number of images to be printed.

  For example, when the PD printer is for A4 paper, it is possible to print up to 2 × 2 images on a single recording paper, and processing such as narrowing down usable layout candidates can be realized.

  Note that the UI at this time may be the same as the UI when printing is set using DPOF when a printer is not connected. As a result, the user can designate printing by the same operation without being conscious of the connection between the printer and the DSC, which is easy to use.

  In this way, when the setting relating to printing is completed, a DPOF file is created, and when the creation is completed as a trigger, a new file in which at least the path name of the DPOF file created on the memory card 40 is replaced with a handle name is created. A conversion process for creating a (print instruction) is executed. In order to transfer the created print instruction file to the PD printer, for example, the procedure shown in FIG. 12 is performed.

  First, in order to notify that there is information (print instruction) to be transmitted to the PD printer 1000, the DSC 3012 notifies the PD printer using a command RequestObjectTransfer (at this time, a handle that reserves the handle of the object in advance is specified). To do. If the PD printer 1000 is a printer like this embodiment, the command GetObjectInfo command is issued to the printer, so that the contents of the file converted and created so as to respond to it are sent to the PD printer as an ObjectInfo Dataset. Would be good.

  When there is a file transmitted as an ObjectInfo Dataset from the DSC 3012, the PD printer may execute print processing according to the contents according to FIG.

  As a result, according to the second example, after the DSC 3012 is directly connected to the PD printer, the printing conditions can be set according to the function of the connected PD printer. Can match.

  Note that the second example may be combined with the first example. That is, when the DSC 3012 is initially connected to the PD printer, if the DPOF file already exists, the operation is performed as in the first example, and if it does not exist, the error is not generated and the operation is performed as in the second example. is there.

<Modification of the second example>
In the above example, an example is described in which handlers are reserved for DPOF and print instruction file. However, in PTP, when a USB slave (DSC3012) generates a new object, an event that uses a command AddObject is prepared. ing. By using this, it is possible to notify the PD printer 1000 of the creation of a new object, so there is no need to reserve a handle as described above.

<Third example>
In the above first and second examples, the DSC 3012 side converts the DPOF file and outputs the result (print instruction file) to the PD printer 1000. In the third example, the DPOF file is An example will be described in which an image file transferred to a PD printer is matched with a handler on the PD printer side expressed by a path name.

  First, a DPOF file is obtained from the DSC 3012 on the PD printer 1000 side, as described in the first example, to narrow down to a file having an attribute as text, and then to supply the contents of the object to the DSC 3012. Issue the command GetObject and request transmission. Whether or not the content of the file is DPOF can be easily understood by examining the description content.

  The PD printer 1000 analyzes the DPOF file transferred as described above, and extracts all path names + file names described therein. Then, a text file composed of the extracted path name + file name is created on the RAM 3, and a command or script for requesting a handler for each file is described at the top of the text file.

  When the creation of the text file for the handler request is completed in this way, the PD printer issues a command SendObject to the DSC 3012 according to the same procedure as in FIG. 11 to notify the object transmission. When an OK response is received from the DSC 3012, the created handler request file (object) is output to the DSC 3012.

  Upon receipt of this object, the DSC 3012 interprets the contents of the object, and adds a character string indicating a handler determined at the time of connection with the PD printer 1000 to each path name + file name described therein (handler). Create a correspondence list). When this creation process is completed, the handler corresponding list file is output to the PD printer 1000 according to the procedure shown in FIG. That is, the command RequestObjectTransfer is issued so that the PD printer receives the object. As a result, the PD printer issues a command GetObjectInfo requesting the object, and accordingly, a handler correspondence list (object) is notified to the PD printer.

  As a result, the PD printer has the DPOF file received first and the handler correspondence list file in which the handler of each print target image file described therein is described. With respect to the described file name + path name, the corresponding handler is used by using the handler correspondence list, the DSC 3012 is requested for the image (command GetObject), the image data is received, and the printing process is performed.

  In this case, the PD printer process may replace step S11 in FIG. 10 with a process for acquiring the DPOF file and the handler correspondence list, and analyze both in step S12.

  As described above, according to the third example, the DPOF printing process using the PTP protocol is successful. Note that the PD printer 1000 in the third example receives the DPOF file in accordance with a request from the DSC 3012 side. Therefore, even when the printing conditions are input on the DSC 3012 side after the PD printer 1000 and the DSC 3012 are connected, of course. Applicability will be readily apparent to those skilled in the art.

  As described above, according to the first to third examples, when a digital camera and a printer are directly connected with a USB interface, the user can use the DPOF method while utilizing the existing PTP protocol. The printing process can be performed as intended. In particular, in the conventional DPOF, setting of printing conditions is performed in a place where the function of the printer is completely ignored, but according to the second example, printing is performed based on the ability of the printer to actually print. Since the conditions can be set using the UI, the set content and the print result do not differ, and the intended print result can be obtained.

  In the embodiment, the digital camera and the printer are directly connected via the USB interface and communication using the PTP protocol is described as an example. However, the present invention is not limited to this. In short, it can be applied when a file stored in one storage device cannot be directly accessed by a path name due to interface and / or protocol restrictions.

  Therefore, in the embodiment, DPOF has been described as an example. However, the present invention is not limited to DPOF, but may be a file described in a markup language such as HTML, or may be in other formats. Like.

  That is, the present invention can be applied to a description language such as HTML, in which a link destination specified by a file name or the like is converted to a handle and specified for printing.

  Many digital cameras have a USB interface, and considering that the hardware resources can be utilized as they are, USB connection is desirable and the burden on the digital camera manufacturer can be reduced.

  When the above embodiment is realized, particularly when the digital camera manufacturer implements the processing or function of the DSC 3012 described in the above embodiment, it can be realized by updating the firmware (program). There is also an advantage that the cost is small.

  As described above, according to the present embodiment, when there is a print request list described with an image file name, even if the system transfers image data with a handle, image transfer and printing as intended. Can be performed.

1 is an external view of a printing apparatus according to an embodiment. It is a figure in the case of connecting a digital camera and a printing apparatus in an embodiment. 1 is a block configuration diagram of a printer device according to an embodiment. It is a block block diagram of the digital camera in an embodiment. It is a figure which shows the layer structure regarding communication with the digital camera and printer in embodiment. It is a figure which shows the connection sequence by the general PTP protocol at the time of the connection of the digital camera and printer in embodiment. It is a figure which shows an example of the content of the DPOF file in embodiment. It is a figure which shows the file content after conversion of the DPOF file shown in FIG. It is a flowchart which shows a part of process of the digital camera in embodiment. 6 is a flowchart illustrating a part of processing of the printer in the embodiment. It is a figure which shows the sequence at the time of transmitting an object from a printer to a digital camera. It is a figure which shows the sequence at the time of transmitting an object from a digital camera to a printer.

Claims (8)

Directly communicates with the image processing apparatus, receives a transmission request from the image processing apparatus using a numbered handle for specifying image data to be processed, and processes the image specified by the handle with the image processing An image supply device for supplying to the device,
Before connecting to the image processing apparatus, a designation means for designating an image to be processed in advance;
Storage control means for storing in a storage medium image designation information different from the predetermined handle as information for designating the processing target image designated by the designation means;
Determining means for determining whether or not the image designation information exists in the storage medium when communication with the image processing apparatus is enabled;
Display means for displaying that there is no image designation information when the judgment means determines that the image designation information does not exist in the storage medium;
A conversion unit that converts the image designation information into the predetermined handle when the determination unit determines that the image designation information exists in the storage medium ;
An image supply apparatus comprising: output means for outputting information converted by the conversion means to the image processing apparatus.   2. The image supply apparatus according to claim 1, wherein the storage control unit stores information for specifying a plurality of images designated by the designation unit together as one file on the storage medium.   3. The image supply apparatus according to claim 2, wherein the conversion unit converts the information specifying the plurality of images stored in the file using the handle. Directly communicates with the image processing apparatus, receives a transmission request from the image processing apparatus using a numbered handle for specifying image data to be processed, and processes the image specified by the handle with the image processing A method for controlling an image supply apparatus to be supplied to an apparatus,
Before connecting to the image processing apparatus, a designation step for designating an image to be processed in advance;
A storage control step of storing in a storage medium with image designation information different from the predetermined handle as information for designating the processing target image designated in the designation step;
A determination step of determining whether or not the image designation information exists in the storage medium when communication with the image processing apparatus is enabled;
If it is determined in the determination step that the image designation information does not exist in the storage medium, a display step for displaying that there is no image designation information;
A conversion step of converting the image designation information into the predetermined handle when it is determined in the determination step that the image designation information exists in the storage medium ;
And an output step of outputting the information converted in the conversion step to the image processing device.   5. The method of controlling an image supply apparatus according to claim 4, wherein in the storage control step, information for specifying a plurality of images designated in the designation step is collectively stored in the storage medium as one file.   6. The method of controlling an image supply device according to claim 5, wherein in the conversion step, the information specifying the plurality of images stored in the file is converted using the predetermined handle. . By computer executes reading, when communicating directly with the image processing apparatus, from the image processing apparatus receives a transmission request using a handle numbered to identify the image data to be processed, the A computer program that functions as an image supply device that supplies an image specified by a handle to the image processing device,
Before connecting to the image processing apparatus, a designation means for designating an image to be processed in advance;
Storage control means for storing in a storage medium image designation information different from the predetermined handle as information for designating the processing target image designated by the designation means;
Determining means for determining whether or not the image designation information exists in the storage medium when communication with the image processing apparatus is enabled;
Display means for displaying that there is no image designation information when the judgment means determines that the image designation information does not exist in the storage medium;
A conversion unit that converts the image designation information into the predetermined handle when the determination unit determines that the image designation information exists in the storage medium ;
A computer program that functions as output means for outputting information converted by the conversion means to the image processing apparatus.   A computer-readable storage medium storing the computer program according to claim 7.

Images