JP5430410B2 - COMMUNICATION DEVICE AND ITS CONTROL METHOD - Google Patents

Description

  The present invention relates to a service negotiation control technique in a communication system.

  In Non-Patent Document 1, in a file transfer service executed between devices via a communication path, when the service for the same file is executed by both devices using the setting of the communication path as a trigger, the order of service activation Describes that the service is executed from the start side. Patent Document 1 also transfers device identification information of a transfer source device in order to prevent overwriting when a file with the same file name exists on the transferee side when a file is transferred in response to setting of a communication path. A method of adding and storing the target file name is described.

  When devices requesting different services execute the respective services, useless communication may be performed. For example, consider a case where a device A that desires a synchronization service that synchronizes stored files between devices and a device B that desires a push service for transferring a specified file to the other party are connected. In this case, if the synchronization service is executed first, the device A acquires a file not stored in the device A from the device B and synchronizes the file. Thereafter, device B transfers the designated file to device A. Here, the file transferred from the device B to the device A is already acquired by the device A by the synchronization service, and the device A stores a plurality of the same files.

JP 2007-128139 A

Bluetooth Basic Imaging Pro file 1.0 Interoperability Specification (2003)

  As described above, when the device that performs the push service and the device that performs the synchronization service are connected, the same file is transferred repeatedly, and wasteful communication occurs. Further, even when the file for which the device A requests the push service and the file for which the device B requests the pull service are the same, the same file is transferred repeatedly, resulting in useless communication. As described above, depending on the service executed by the devices, useless communication occurs when the devices are connected to each other and execute the service.

  An object of the present invention is to provide a technique capable of avoiding duplicate transfer of the same file even when a peer-to-peer communication path is set between devices in which the push transfer service and the sink transfer service are activated.

To solve the above problem,
A communication device that performs sync transfer according to the connection with an external communication device
A communication means for communicating with an external communication device;
Determining means for determining a communication service requested by the external communication device when connected to the external communication device by the communication means;
When the determination unit determines that the external communication device requests a file push transfer service, the external communication device performs sync transfer with the external communication device after the push transfer service, and the determination unit performs the external communication device. And executing means for executing the sink transfer before executing the requested communication service when it is determined that the communication service is different from the push transfer service. And

  Even if a peer-to-peer communication path is set between devices for which the push transfer service and the sink transfer service are activated, it is possible to avoid duplicate transfer of the same file.

The figure which shows a system structure. The functional block diagram in a component apparatus. FIG. 6 is a diagram illustrating an example of a control sequence when a push transfer service and a sync pull transfer service for the same file are activated simultaneously in the first embodiment. 5 is an operation flowchart of each device in the first embodiment. The figure which shows the example of the control sequence at the time of simultaneous activation of the push transfer service and the sink pull transfer service with respect to the same file in Embodiment 2. The figure which shows the example of the control sequence at the time of simultaneous activation of the push transfer service with respect to the same file, and a sync pull transfer service in Embodiment 3. 10 is an operation flowchart when priority is given to a push transfer service according to the fourth embodiment. The figure which shows the sequence at the time of the push transfer service priority in Embodiment 4.

<Embodiment 1>
FIG. 1 is a configuration diagram relating to a communication system connectable by a peer-to-peer communication path according to the present embodiment. This system includes an imaging apparatus 1 and a PC 2, and the imaging apparatus 1 and the PC 2 are connected by a close proximity wireless communication path 4 that is a peer-to-peer communication path. The proximity wireless communication path 4 is a communication path using an induction electric field such as non-contact IC card wireless communication using electromagnetic induction or NFC (Near Field Communication).

  In addition, the imaging device 1 requests a transfer service of the latest image file that has been captured to the PC 2, and the PC 2 requests a sink transfer service of the file in the captured image file storage folder.

  FIG. 2 is a functional block diagram of the imaging apparatus 1 and the PC 2 in the present embodiment. The imaging apparatus 1 includes a proximity wireless communication unit 301 that controls a medium of the proximity wireless communication path 300, a communication control unit 302 that controls the proximity wireless communication unit, and a communication middleware 303 that performs communication protocol control. It is implemented as a part.

  Furthermore, an in-device application 305 that performs a transfer service of the latest image file that has been taken to the PC 2 is installed. As the in-device application 305, a file push mode control point 304 of a file push service for performing a user operation regarding the push transfer service, and a file transmission / reception application 306 are implemented.

  Further, the PC 2 includes a proximity wireless communication unit 307 that controls the medium of the proximity wireless communication path 300, a communication control unit 308 that controls the proximity wireless communication unit, and a communication middleware 309 that performs communication protocol control. As implemented.

  Furthermore, an in-device application 311 that manages a file sync (synchronous) transfer service in the captured image storage folder is installed. As the in-device application 311, a control point 310 of a file sync (Sync) service for performing a user operation regarding the sync transfer service and a file transmission / reception application 312 are implemented.

  FIG. 3 is a diagram illustrating an example of a control sequence chart at the time of simultaneous activation of the push transfer service and the sink transfer service for the same file in the first embodiment. FIG. 4 is a diagram illustrating an example of an operation flowchart in each device according to the embodiment of the present invention. Hereinafter, the processing procedure of the first embodiment will be described with reference to the sequence chart of FIG. 3 and the flowchart of FIG. 4.

  A file sync transfer service (transfer service in the first transfer mode) of the captured image storage folder in the PC 2 (communication device) is requested from the PC 2 by a user operation or other external input, and the PC 2 accepts this request. As a result, the file transmission / reception application 312 for the file sync service in the PC 2 transmits a service sync start request to the communication middleware 309 (S401). Here, in the file sync transfer, the file in the sync folder at the other party of communication and the file in its own sync folder are the same (so as to synchronize), from the other party of communication, Get (pull) the latest file.

  On the other hand, a file push service (transfer service in the second transfer mode) is also requested for the imaging apparatus 1 (external communication apparatus) by a user operation or other external input, and the imaging apparatus 1 accepts this request. Here, push transfer means that only the selected file is transmitted to the other party of communication. Further, it is assumed that a file push service for transferring an image file selected from the captured image storage folder to the captured image storage folder of the PC 2 is requested by a user operation or other external input.

  The file transmission / reception application 306 for the file push transfer service in the imaging device 1 makes a service push start request to the communication middleware 303 (S402). As an interface for close proximity wireless communication, there are an initiator mode for connecting to a communication partner and leading communication operation, and a response mode for responding to communication in the initiator mode.

  In each embodiment of the present invention, it is assumed that the PC 2 is activated first and always performs sync transfer. That is, since the PC 2 is activated before the imaging device 1, the PC 2 always operates in the initiator mode and transmits a connection request to the imaging device 1. Further, it is assumed that the imaging apparatus 1 that receives the communication connection always starts after the PC 2 and therefore operates as a response mode and performs push transfer.

  Accordingly, when the PC 2 is activated, it receives a sync service start request (Sync Start) from the user or an external device in order to perform sync transfer (S401). Since the PC 2 operates in the initiator mode, a connection request message is transmitted in order to connect to the imaging device 1 (S403, S404). Along with this, the PC 2 side activation request service information (file sync service) is notified by an information parameter.

  Further, it is assumed that the imaging apparatus 1 has already received a push start request (Push Start) of the file push transfer service from the user. Since the imaging apparatus 1 operates in the response mode, the imaging apparatus 1 waits for reception of a connection display (Connec. Ind) via the close proximity wireless communication medium (S405). In step S405, the communication middleware 303 of the imaging device 1 recognizes the information (transfer parameter) of the activation request service at the communication partner.

  The imaging device 1 makes a file push transfer request by notifying the file push transfer service information, which is its activation request service information, together with the transmission of the connection acceptance message (S406, S407) by an information parameter.

  Conventionally, sync transfer is received with priority given to sync transfer from the PC 2 in the initiator mode. However, in this embodiment, the file push transfer request has priority over the sync transfer. Therefore, the communication middleware 303 of the imaging apparatus 1 in FIG. 2 is characterized in that it sends StartAck to the in-device application 305 in order to prioritize its own transfer (to permit execution of the file push transfer service) (S409). is there.

  In FIG. 4, the operation of the imaging apparatus 1 will be described from the beginning. In S501, since the imaging image apparatus 1 side operates in the response mode, “No” is selected, and connection display (Connection Ind.) Is received from the PC 2 in S502. In step S <b> 506, the imaging apparatus 1 determines whether there is a service for requesting activation of the PC 2 that is a communication partner. If no service is requested, the process proceeds to S510. If there is a service request, it is determined in step S507 whether the service is a file push service. If it is not a file push service, the process proceeds to S510.

  If the request for this service is a file push service, the imaging apparatus 1 gives priority to the service of the PC 2. In this example, the request for the service of the PC 2 is a sink service. Accordingly, the process proceeds to S511 to notify the execution permission of the file push transfer service which is the activation request service of the imaging apparatus 1 itself. This operation is performed when the communication middleware 303 of the imaging apparatus 1 notifies the in-device application 305 (S409).

  In FIG. 4, the operation of the PC 2 will be described from the beginning. In S501, the PC 2 operates as an initiator. Accordingly, a connection request is transmitted to the imaging apparatus 1 in S502. In S504, the PC 2 (the message receiving means) receives the connection entrustment message from the imaging device 1 (S408). Conventionally, when the PC 2 receives the connection entrustment message, the PC 2 returns an ACK to the imaging apparatus 1 and grants its own sync transfer permission to start sync transfer. However, in the present embodiment, as described below, the PC 2 does not immediately perform sync transfer but operates to give priority to push transfer.

  That is, first, in S505, it is determined whether or not the imaging apparatus 1 recognizes its own requested service. This determination is made when the imaging apparatus 1 confirms the request for the file sink service included in the connection entrustment message and returns the connection entrustment message to the PC 2, and the PC 2 includes the push service request in the connection entrustment message. It is done by confirming that. In step S506, the PC 2 confirms that there is a request for activation of the file push transfer service from the imaging device 1 (opposite device).

  In step S <b> 507, the PC 2 determines whether the service request for the imaging apparatus 1 is a file push service. In this example, the imaging device 1 makes a request for starting a file push service. Therefore, the activation request (file push activation request), which is one of the information parameters of the connection entrustment message, is confirmed. Then, the PC 2 proceeds to S508, and notifies the activation delay of the file sink service, which is its own activation request service, according to the content of the activation request information (S410). This operation is performed when the communication middleware 309 notifies the in-device application. In S510, the PC 2 measures the time during which the data payload from the imaging device 1 is idle with respect to the specified period.

  Thereafter, in S509, the file push transfer service (S411 to S415) for starting the imaging apparatus 1 is executed. That is, discovery of the file push transfer service is performed (S411). Then, the imaging apparatus 1 executes a transfer destination folder existence confirmation process of the PC 2 (S412). Thereafter, the imaging apparatus selects a transfer destination folder of the PC 2 (S413, S414), and push-transfers the target file (S415).

  The PC 2 (the transfer receiving means) receives the transfer of the transfer target file by the imaging apparatus 1 and after all the data is transferred, there is no communication of the data payload accompanying the file push service, and an idle state is entered. In step S509, the PC 2 measures that the idle time of the data payload from the imaging device 1 has continued for a specified period. In S510, the PC 2 notifies activation of the file sink service whose execution has been postponed (S417). This operation is performed when the communication middleware 309 in the PC 2 notifies the in-device application 311.

  Thereafter, in S512, a file sync transfer service (S418 to S422) started by PC2 is executed. Therefore, after the discovery of the file sync transfer service (S418), the sync target folder existence confirmation process (S419) on the imaging device 1 side is executed. That is, the PC 2 confirms all file names and file update dates in the sync target folder of the image capturing apparatus 1 (S419), and names of all files including files received by push transfer in its sync folder. And the file modification date. (In this embodiment, it is assumed that when a file having the same file name transmitted from the imaging apparatus 1 is stored in the sync folder of the PC 2, the old file is rewritten with the new file on the update date. Then, a file in the sync target folder of the image pickup apparatus 1 that does not exist on the PC 2 or is not the latest file is selected as a transfer target file (S421), and the selected file is pulled-transferred from the photographing apparatus to the PC 2 (S422).

  As described above, when the transfer is performed between the imaging device 1 that desires the push transfer service to the PC 2 and the PC 2 that desires the sync transfer service, the push transfer service is given priority over the order of the linked services to be activated, Thereafter, control is performed to execute the sync transfer service. In the first embodiment, since the image file can be prevented from being duplicated by operating in this way, it is possible to avoid waste of communication resources and information storage resources due to image file transfer as in the past.

<Embodiment 2>
In the first embodiment, an example in which the service negotiation function is implemented in both the imaging device 1 and the PC 2 has been described. However, this embodiment will be described in the second embodiment because the same effect can be obtained if the service negotiation function is mounted at least on the device side that desires the file sink transfer service. That is, in the second embodiment, an example is shown in which the service negotiation function is implemented in the PC 2 that is a device that requests a file sync transfer service, but not in the imaging apparatus 1. Hereinafter, a device that does not have a service negotiation function is referred to as a legacy type device. The PC 2 side is activated in the initiator mode and the imaging device 1 is activated in the response mode, as in the first embodiment.

  FIG. 5 shows an example of a control sequence chart at the time of simultaneous activation of the push transfer service and the sync pull transfer service for the same file according to the second embodiment. The operation flow of the second embodiment will be described below using the sequence chart of FIG. 5 and the flowchart of FIG.

  As a result of the user operation, a sync transfer service for a file in the captured image storage folder in the PC 2 is requested to the PC 2, and the PC 2 accepts this request. As a result, the file transmission / reception application 312 for the file sync service in the PC 2 makes a service sync start request to the communication middleware 309 (S601).

  The image pickup apparatus 1 is also requested by a user operation for a file push service for transferring the selected image file into the taken image storage folder of the PC 2, and the image pickup apparatus 1 accepts this request. The file transmission / reception application 306 for the file push transfer service in the imaging device 1 makes a service push start request to the communication middleware 303 (S602).

  In step S501 of FIG. 4, the PC 2 that has received the file service sync start request 601 operates in the initiator mode. In step S <b> 502, the PC 2 issues a connection request to the imaging apparatus 1 for the sink transfer service via the communication middleware 309. In step S502, along with the transmission of the connection request message (S603, S604), the activation request service information including the file sync transfer service on the PC 2 side is notified by the information parameter.

  Next, the operation of the imaging apparatus side 1 will be described with reference to FIG. It is assumed that the imaging apparatus 1 receives a push start request 602 of the file push transfer service. Accordingly, in S501, the imaging apparatus 1 receives a connection request from the PC 2 and operates in the response mode. In step 503, reception of a connection display via the proximity wireless communication medium is awaited (S605). In the second embodiment, since the imaging device 1 is a legacy device, the information on the activation request service sent from the communication partner, in this case, the PC 2 cannot be recognized. Therefore, the imaging apparatus 1 transmits a legacy type (existing) connection acceptance message not including the transfer request parameter to the PC 2 (S606, S607). The legacy-type imaging apparatus 1 transmits a connection acceptance message that does not add file push transfer service information, which is its activation request service information, and file sync service recognition information.

  The imaging apparatus 1 cannot recognize the presence of the activation request service in the PC 2 that is the other party of communication, but when the setting of the close proximity wireless communication path 300 is completed, execution permission of the file push transfer service that is its activation request service is permitted. Is notified (S609). This operation is performed when the communication middleware 303 of the imaging apparatus 1 notifies the in-device application 305 of execution permission.

  Next, the operation of the PC 2 in FIG. 4 will be described. In S504, the PC 2 receives a connection acceptance display from the imaging device 1 (S608). Since this message is legacy, the PC 2 recognizes that the image capturing apparatus 1 that is the other party of communication does not recognize its own file sync service activation request, and that the image capturing apparatus 1 is operating in the legacy mode. Recognize that.

  In step S505, the PC 2 determines that the imaging apparatus 1 that is the opposite device does not recognize the request service of the own device, and in step S508, notifies the startup delay of the file sink service that is its startup request service (S610). ). This operation is performed when the communication middleware 309 of the PC 2 notifies the in-device application 311 of the postponement of activation.

  In S509, the PC 2 starts to measure the idle time of the data payload with respect to the specified period. In parallel with this, a file push transfer service (S611 to S615) to the PC 2 by the startup of the imaging apparatus 1 is executed in S509. That is, when the discovery of the file push transfer service (S611) is completed, the imaging apparatus 1 executes a transfer destination folder existence confirmation process on the PC 2 side (S612). Thereafter, the transfer destination folder is determined (S613), and the folder is selected (S614). Then, the imaging device 1 push-transfers the target file to the PC 2 (S615).

  When all the transfer of the transfer target file by the imaging device 1 is completed, communication of the data payload accompanying the file push service is lost and the idle state is set. Further, when the image pickup apparatus 1 does not execute the file push service, the data payload from the image pickup apparatus 1 is not communicated, and the idle state is set.

  In S510, the PC 2 measures that the idle time of the data payload from the imaging device 1 has continued for a specified period. In S511, the PC 2 notifies the activation of the file sink service whose execution has been postponed (S617). This operation is performed when the communication middleware 309 in the PC 2 notifies the in-device application 311.

  Thereafter, in S512, a file sync transfer service (S618 to S622) by the start of the PC 2 is executed. That is, after the discovery of the file sync transfer service (S618), the PC 2 executes a sync target folder existence confirmation process (S619) on the imaging device 1 side.

  That is, the PC 2 confirms all file names and file update dates in the sync target folder of the image capturing apparatus 1 (S619), and all files and files including files received by push transfer in its sync folder. Compare with renewal date. (In this embodiment, it is assumed that when a file having the same file name transmitted from the imaging apparatus 1 is stored in the sync folder of the PC 2, the old file is rewritten with the new file on the update date. Then, among the files in the sync target folder of the imaging device 1, a file that does not exist on the PC 2 and a file that is not the latest are selected as transfer target files (S621), and the selected file is pulled and transferred from the photographing device to the PC 2 (S622). )

  As described above, when the transfer is performed between the imaging device 1 that desires the push transfer service and the PC 2 that desires the sync transfer service, priority is given to the push transfer service of the legacy device in the order of the linked services to be activated, Thereafter, the sink transfer service on the PC 2 side is executed.

  In the second embodiment, by operating in this manner, a device that requests a file sync transfer service is provided with a service negotiation function, thereby preventing redundant image file transfer. By adopting this configuration, it is possible to avoid wasting communication resources and information storage resources due to redundant transfer of redundant image files as before.

<Embodiment 3>
In the third embodiment, an example is shown in which the service negotiation function is implemented only in the PC 2 that is a device that requests the file sync transfer service, and only the file sync transfer service on the PC 2 side is required.

  FIG. 6 shows an example of a control sequence when only the sync file transfer service of the third embodiment is activated. The operation of this embodiment will be described with reference to FIGS.

  As a result of the user operation, a sync transfer service for a file in the captured image storage folder in the PC 2 is requested to the PC 2, and the PC 2 accepts this request. As a result, the file transmission / reception application 312 for the file sync service in the PC 2 makes a service sync start request to the communication middleware 309 (S701).

  In this embodiment, the start request for the device connection service is not made to the imaging device 1 by the user's operation. The operation of the PC 2 will be described with reference to FIG. In step S501, the PC 2 receiving the sync start request 701 of the file sync service performs an initiator mode operation (S501). In step S502, together with the transmission of the connection request message to the image pickup apparatus 1 (S703, S704), the activation request service information (file sync service) related to the file sync service on the PC side is sent to the image pickup apparatus 1 as an information parameter. Notice.

  Next, the operation of the imaging apparatus 1 will be described with reference to FIG. In S501, the imaging apparatus 1 operates in the response mode. In step S503, reception of a connection display via a close proximity wireless communication medium (S705) is awaited. In this embodiment, since the imaging apparatus 1 is assumed to be a legacy device, information on the activation request service from the other party of communication. I cannot recognize the information even if I send it. Therefore, the imaging apparatus 1 transmits an existing connection acceptance message (not adding file transfer service recognition information) (S706, S707).

  On the other hand, the PC 2 receives a connection acceptance display from the imaging device 1 in step S504 (S708). Then, the PC 2 recognizes that the imaging device 1 has not recognized the activation request of the file sync service of the PC 2 and is in the legacy mode operation state by receiving the legacy connection commission display.

  In step S505, the PC 2 determines that the imaging device 1 that is the opposite device does not recognize the requested service of the own device, and notifies the activation delay of the file sink service that is its own activation request service in S508 ( S710). This operation is performed when the communication middleware 309 in the PC 2 notifies the in-device application 311. Thereafter, in step S509, the data payload idle time is measured. The imaging device 1 side does not activate any communication service. Accordingly, there is no data payload communication by the imaging device 1 from the beginning.

  In step S509, the PC 2 confirms that the idle duration of the data payload of the imaging device 1 exceeds the specified time (S716), and then in step S510, notifies the activation of the file sink service whose execution has been postponed (S717).

  Thereafter, a file sync transfer service started by the PC 2 is executed (S718 to S722). That is, after discovery of the file sync transfer service (S718), the PC 2 executes a sync target folder existence confirmation process on the imaging device 1 side (S719). Then, among the files in the sync target folder of the imaging device 1, a file that does not exist on the PC 2 and a file that is not the latest are selected as transfer target files (S721), and the selected file is pulled and transferred from the photographing device to the PC 2 (S722). Is done.

  As described above, in the third embodiment, the imaging apparatus 1 stores the latest captured image, but the case where the file transfer service is not requested has been described. That is, only the PC 2 side desires a sync transfer service for files in the captured image file storage folder. By adopting a configuration having a negotiation function under such conditions, even if the imaging device 1 is a legacy device, the PC 2 can start the desired sink transfer service to the imaging device 1 without any problem. Can produce the effect.

<Embodiment 4>
In the first to third embodiments, an example has been shown in which duplication of transfer files is prevented by selectively starting sequentially the services requested by both devices. In addition to such a mode, when there is a request for a transfer service from both sides, a method for exclusively starting one transfer service, prohibiting the other transfer service from starting, and canceling the other transfer is described in Embodiment 4. Will be described.

  As a condition for exclusive activation processing, an embodiment for determining the priority of the sink transfer service to be lower than that of push transfer and avoiding duplicate file transfer is shown in the flowchart of FIG. 7 and the sequence diagram of FIG.

  First, a user operation requests the PC 2 for a sync transfer service of a file in the captured image storage folder in the PC 2, and the PC 2 accepts this request. As a result, the file transmission / reception application 312 for the file sync service in the PC 2 makes a service sync start request to the communication middleware 309 (S901).

  The image pickup apparatus 1 is also requested by a user operation for a file push service for transferring the selected image file into the taken image storage folder of the PC 2, and the image pickup apparatus 1 accepts this request. The file transmission / reception application 306 for the file push transfer service in the imaging device 1 makes a service push start request to the communication middleware 303 (S902).

  In FIG. 7, the PC 2 that received the file service sync start request operates in the initiator mode in S801. In step S802, the PC 2 sends a connection request message to the image capturing apparatus 1 for the sync transfer service via the communication middleware 309 (S903, S904), and the PC 2 side file sync service activation request service. Information is notified by an information parameter.

  In FIG. 7, in step 801, the imaging apparatus 1 operates in a response mode after receiving a push start request for a file push transfer service from a user. In step S803, reception of a connection display (Connec. Ind) via the close proximity wireless communication medium is awaited (S905). In step S806, the information (transfer parameter) of the activation request service in the PC 2 of the communication partner sent along with the connection display is confirmed, and it is determined whether there is an activation service request in the opposite device. In this embodiment, since the PC 2 requests the file sync transfer service, in S807, the PC 2 recognizes that the service of the opposite device is the file sync transfer. The imaging apparatus 1 recognizes that the activation request of the PC 2 is the file sync transfer service, and the push transfer that is the activation request of the PC 2 should be given priority, and the image push device of the file push transfer service that is the activation request service of itself. The execution permission is notified (S909). This operation is performed when the communication middleware 303 in the imaging apparatus 1 notifies the in-device application 305.

  In addition, the image pickup apparatus 1 notifies the PC 2 of an information parameter indicating a request for its own file push transfer, together with transmission of a connection acceptance request (Accept Request), file push transfer service information that is its own activation request service information. (S906, S907).

  In S804, the PC 2 receives a connection acceptance display (Accept Ind.) (S908). In step S805, the PC 2 confirms whether the request for its own sink transfer service is recognized on the imaging apparatus 1 side. In this case, since the connection acceptance display message is returned together with the parameter indicating the request for transfer, it is determined that it is recognized. In step S806, the PC 2 recognizes that there is a request that the imaging apparatus 1 that is the other party of communication has a file push transfer service for itself. In S807, the PC 2 recognizes from the information parameter of the connection acceptance display message that the service is a file push service and should be prioritized (S908).

  In step S809, the PC 2 prioritizes the file push transfer service, which is the activation request service of the imaging device 1 that is the counterpart, and cancels its own activation request service (S908). The imaging apparatus 1 executes a file push transfer service (S911 to S915) started by itself. That is, when the discovery of the file push transfer service (S911) is completed, the imaging apparatus 1 executes a transfer destination folder existence confirmation process on the PC 2 side (S912). Thereafter, a transfer destination folder is determined (S913), and the folder is selected (S914). Then, the imaging apparatus 1 push-transfers the target file to the PC 2 (S915).

  By such a control method, the requested file transfer service, that is, the file sync transfer, has not been executed on the start side device that performs the file transfer service that has not been started, that is, the PC 2 after one file transfer service is completed. A message is displayed.

  By the above processing, redundant image file transfer can be prevented in advance, and waste of communication resources and information storage resources that are wasted for image file transfer can be eliminated.

Claims (6)

A communication device that performs sync transfer according to connection with an external communication device,
Communication means for communicating with the external communication device,
When connected to the external communication apparatus by said communication means, determining means for communication services external communication device requests,
When the determination unit determines that the external communication device requests a file push transfer service, the external communication device performs sync transfer with the external communication device after the push transfer service, and the determination unit performs the external communication device. Execution means for executing the sink transfer with the external device before the execution of the requested communication service when it is determined that the communication service is different from the push transfer service ,
A communication apparatus comprising: The execution means includes the file stored in the external communication device and the push transfer when a period in which data from the external communication device is not sent continues for a specified period after the push transfer service is started. A file stored in the communication device including a file received by a service is compared, and a file that exists in the external communication device and does not exist in the communication device is connected to the external communication device via the communication unit. The communication apparatus according to claim 1, wherein the sink transfer is performed to the communication apparatus. 2. The communication according to claim 1, wherein the execution unit compares a file name and update date and time stored in the external communication device with a file name and update date and time stored in the communication device. apparatus. The determination means according to claim 1, characterized in that to determine on the basis of the information contained in the response to the external communication apparatus has transmitted the connection request, the previous Kigaibu communication device requesting a push transfer files The communication apparatus as described in. The determination means further determines whether or not the external communication device is a device having a service negotiation function,
The communication device according to claim 1, wherein when the determination unit determines that the external communication device is not a device having a service negotiation function, the execution unit postpones the execution of the sync transfer. A method of controlling a communication device that performs sync transfer according to connection with an external communication device,
A communication step in which the communication means communicates with the external communication device;
A determination step of determining a communication service requested by the external communication device when the determination unit is connected to the external communication device by the communication unit;
When the execution unit determines that the external communication device is requesting a file push transfer service by the determination unit, the execution unit executes sync transfer with the external communication device after the push transfer service. An execution step of executing the sink transfer with the external device before execution of the requested communication service when it is determined that the external communication device is requesting a communication service different from the push transfer service;
Method characterized by having a.

Images