JP6552578B2 - COMMUNICATION DEVICE, ITS CONTROL METHOD, PROGRAM - Google Patents

Description

  The present invention relates to technology for controlling an external device using communication.

  A system for connecting a communication device such as a digital camera to a PC and controlling the digital camera from the PC to acquire an image and control the camera has been proposed. In recent years, with the spread of mobile terminals such as smartphones, there has been an increasing demand for controlling digital cameras from various devices.

JP 2005-136833 A

  As devices and applications that can communicate with digital cameras spread, it is necessary to realize control that matches the characteristics of each application.

A communication device according to the present invention communicates with an external device using a communication application that includes a first program that receives a user operation for communication with the communication device, and a second program for performing communication with the communication device. Communication means for notifying the external device of available operations of the external device among operations for controlling the communication device in communication between the communication device and the external device, and the external device Determining means for determining whether the second program used by the communication apparatus is provided by the vendor of the communication apparatus, and the notification means includes a program provided by the vendor of the communication apparatus for the second program. Depending on whether or not the operation to be notified is different.

  According to the present invention, it is possible to use an optimal operation according to the characteristics of an application.

It is a conceptual diagram which shows a system configuration. It is a block diagram which shows the hardware constitutions of a digital camera. It is a block diagram which shows the hardware constitutions of PC and a portable terminal. It is a figure explaining the connection of the application structure and digital camera which are started with an external device. It is a figure which shows the table which a digital camera has. It is a sequence which shows communication with PC and a digital camera. It is a sequence which shows communication with a portable terminal and a digital camera. It is an example of a screen of PC application and a portable terminal application. It is a figure which shows the table which a digital camera has. It is a sequence which shows communication with PC and a digital camera. It is a sequence which shows communication with PC and a digital camera. It is a figure which shows the table which a digital camera has.

First Embodiment
Hereinafter, embodiments according to the present invention will be described in detail with reference to the accompanying drawings.

  FIG. 1 is a diagram illustrating a configuration example of a system capable of executing image transfer processing according to the present embodiment.

  The camera control process shown in FIG. 1 includes a digital single-lens reflex camera (hereinafter, digital camera) 201, a PC 202 connected to the digital camera 201 as an external device for control, or a portable terminal 203 such as a smartphone or a tablet. The

  The digital camera 201 and the PC 202 can be connected by a wired cable 204 and can transmit and receive content data including image data and various signals. The wired cable 204 may be a USB cable or a wired LAN cable.

  In addition, the digital camera 201 and the PC 202 in this embodiment can be connected wirelessly via the access point 205. It is assumed that the digital camera 201 and the portable terminal 203 in the present embodiment are connected by a wireless LAN.

  Communication between the digital camera 201 and the portable terminal 203 may be direct connection using an ad hoc network or the like, or may be infrastructure connection via the access point 205 or the like. Further, the camera may be a simple access point, and direct communication may be established with the mobile terminal 103 through infrastructure connection.

  FIG. 2 is a block diagram showing a configuration of a single-lens reflex digital camera 201 according to an embodiment of the present invention.

  In FIG. 2, reference numeral 101 denotes a photographing lens. Reference numeral 102 denotes an AF (auto focus) driving unit. The AF drive unit 102 is configured by, for example, a DC motor or a stepping motor, and focuses by changing the focus lens position of the photographing lens 101 under the control of the microcomputer 123.

  Reference numeral 103 denotes a zoom drive unit. The zoom driving unit 103 is constituted by, for example, a DC motor or a stepping motor, and changes the focal length of the photographing lens 101 by changing the position of the variable magnification lens of the photographing lens 101 under the control of the microcomputer 123.

  Reference numeral 104 denotes an aperture.

  Reference numeral 105 denotes an aperture drive unit. The diaphragm drive unit 105 drives the diaphragm 104. The amount to be driven is calculated by the microcomputer 123, and the optical aperture value is changed.

  Reference numeral 106 denotes a main mirror for switching the light beam incident from the photographing lens 101 between the viewfinder side and the image sensor side. The main mirror 106 is always arranged to reflect light so as to guide the light flux to the finder unit, but when shooting is performed, the main mirror 106 bounces upward so as to guide the light flux to the imaging device 112 and retreats from the light flux. . The main mirror 106 is a half mirror so that a central portion thereof can transmit a part of the light, and transmits a part of the light beam so as to enter a sensor for performing focus detection.

  Reference numeral 107 denotes a sub mirror for reflecting the light flux transmitted from the main mirror 106 and guiding it to a sensor (disposed in the focus detection circuit 109) for focus detection.

  Reference numeral 108 denotes a pentaprism that constitutes a finder. In addition, the viewfinder is composed of a focus plate, an eyepiece lens (not shown), and the like.

  Reference numeral 109 denotes a focus detection circuit. The light beam transmitted through the center of the mirror 106 and reflected by the sub-mirror 107 reaches a sensor for performing photoelectric conversion disposed inside the focus detection circuit 109. The defocus amount used for the focus calculation is obtained by calculating the output of the sensor. The microcomputer 123 evaluates the calculation result and instructs the AF driving unit 102 to drive the focus lens.

  Reference numeral 110 denotes a focal plane shutter. Reference numeral 111 denotes a shutter drive circuit that drives the focal plane shutter 110. The opening time of the shutter is controlled by the microcomputer 123.

  Reference numeral 112 denotes an image sensor. A CCD, CMOS sensor, or the like is used as the image sensor 112, and the subject image formed by the photographing lens 101 is converted into an electrical signal.

  Reference numeral 113 denotes a clamp circuit. Reference numeral 114 denotes an AGC circuit. The clamp circuit 113 and the AGC circuit 114 perform basic analog signal processing before A / D conversion, and the microcomputer 123 changes the clamp level and the AGC reference level. Reference numeral 115 is an A / D converter. The A / D converter 115 converts the analog output signal of the image sensor 112 into a digital signal. Reference numeral 116 denotes a video / audio signal processing circuit, which is realized by a logic device such as a gate array.

  Reference numeral 117 denotes an EVF drive circuit. Reference numeral 118 denotes an EVF (Electronic Viewfinder) monitor.

  Reference numeral 119 denotes a memory controller. Reference numeral 120 denotes a memory. Reference numeral 121 denotes an external interface that can be connected to a computer or the like. Reference numeral 122 denotes a buffer memory.

  The video / audio signal processing circuit 116 subjects the digitized image data to filter processing, color conversion processing, gamma processing, compression processing such as JPEG, and the like, and outputs the resultant to the memory controller 119.

  The video / audio signal processing circuit 116 compresses the audio signal from the microphone 132 or the audio line input 133 and outputs the compressed signal to the memory controller 119. The video / audio signal processing circuit 116 can also output the video signal from the image sensor 112 and the image data input in reverse from the memory controller 119 to the EVF (electronic viewfinder) monitor 118 through the EVF drive circuit 117. It is. Switching between these functions is performed according to instructions from the microcomputer 123. The video / audio signal processing circuit 116 can output information such as exposure information and white balance of the signal from the image sensor 112 to the microcomputer 123 as necessary. Based on the information, the microcomputer 123 instructs white balance and gain adjustment. In the case of the continuous shooting operation, the shooting data is temporarily stored in the buffer memory 122 as an unprocessed image, the unprocessed image data is read through the memory controller 119, and image processing and compression are performed by the video / audio signal processing circuit 116. Process and perform continuous shooting. The number of continuous shots depends on the size of the buffer memory.

  The video / audio signal processing circuit 116 can output the audio data from the microphone 132 or the audio line input 133 to the speaker 136 through the DA conversion 135.

  The memory controller 119 stores the unprocessed digital video / audio data input from the video / audio signal processing circuit 116 in the buffer memory, and stores the processed digital video / audio data in the memory 120. Conversely, the video / audio data is output from the buffer memory 122 or the memory 120 to the video / audio signal processing circuit unit 116. The memory 120 may be removable. The memory controller 119 can output images and sounds stored in the memory 120 via an external interface 121 that can be connected to a PC or the like.

  Reference numeral 123 denotes a microcomputer. Reference numeral 124 denotes an operation member. The operation member 124 transmits the state to the microcomputer 123, and the microcomputer 123 controls each part according to the change of the operation member.

  125 is a switch 1 (hereinafter referred to as SW1). Reference numeral 126 is a switch 2 (hereinafter referred to as SW2). The switches SW1 and SW2 are switches that are turned on and off by operating the release button, and are each one of the input switches of the operation member 124. When only the switch SW1 is on, the release button is half-pressed. In this state, the auto focus operation or the photometric operation is performed. When the switches SW1 and SW2 are both on, the release button is fully pressed, and the release button for recording an image is on. Shooting is performed in this state. Further, a continuous shooting operation is performed while the switches SW1 and SW2 are kept on. In addition, switches such as an ISO setting button, an image size setting button, an image quality setting button, and an information display button are connected to the operation member 124, and the state of the switch is detected.

  127 is a liquid crystal drive circuit. 128 is an external liquid crystal display member. Reference numeral 129 denotes an in-finder liquid crystal display member. The liquid crystal drive circuit 127 drives the external liquid crystal display member 128 and the in-finder liquid crystal display member 129 in accordance with the display content command of the microcomputer 123. The in-viewfinder liquid crystal display member 129 is provided with a backlight such as an LED (not shown), and the LED is also driven by the liquid crystal drive circuit 127. The microcomputer 123 checks the memory capacity through the memory controller 119 based on the predicted value data of the image size according to the ISO sensitivity, image size, and image quality set before photographing, and then the remaining number of images that can be photographed Can be calculated. If necessary, it can also be displayed on the external liquid crystal display member 128 and the liquid crystal display member 129 in the viewfinder.

  Reference numeral 130 denotes a nonvolatile memory (EEPROM) that can store data even when the camera is not turned on.

  Reference numeral 131 denotes a power supply unit. The power supply unit 131 supplies power necessary for each IC and drive system.

  Reference numeral 132 denotes a microphone.

  Reference numeral 133 denotes an audio line input.

  134 is an A / D converter. The A / D converter 133 converts the analog output signal of the microphone 132 or the audio line input 133 into a digital signal.

  135 is a D / A converter. The D / A converter converts the digital signal to an analog output signal.

  136 speakers.

  Reference numeral 137 denotes an external device represented by a personal computer, a cellular phone, and a portable information terminal. Through the above-described interface 121, it becomes a partner for transmitting and receiving various information and image data of the camera. Similarly, a camera provided with a communication circuit can also be used as an external device. In this case, various information and image data can be transmitted and received between the cameras.

  FIG. 3a is a block diagram showing a hardware configuration of the PC 202 according to an embodiment of the present invention.

  Reference numeral 301 denotes a CPU, 302 denotes an internal memory, and 303 denotes a display unit including a graphic controller, which may be connected to an external monitor device or may have a built-in monitor. Reference numeral 304 is a keyboard, 305 is a mouse, and 306 is a communication port, which enables communication with the camera. Reference numeral 307 denotes a disk memory such as an HD. 307 is not necessarily a disk-shaped medium, but may be a storage device that can be handled like a disk, such as a flash memory. Reference numeral 308 denotes a power supply in the PC.

  The display 303 displays various screens including a shooting parameter operation screen and a live view image display screen. An application program for such a remote shooting (remote shooting) system is stored in the HD 307 and is activated by a trigger such as a user operation or camera device detection and executed by the CPU 301.

  FIG. 3b is a block diagram illustrating a hardware configuration of the mobile terminal 203 according to an embodiment of the present invention. Examples of mobile terminals include mobile phones such as so-called smart phones, tablet devices, PDAs (Personal Digital Assistants), portable AV players, electronic books, electronic dictionaries and the like.

  The portable terminal 203 includes a CPU 400, a flash memory 401, a RAM 402, a built-in camera 403, a microphone 404, a speaker 405, an earphone 406, a touch panel 410, a liquid crystal display unit 411, a switch 412, a communication unit 413, and an external I / F 414. Furthermore, the mobile terminal 203 includes a GPS (Global Positioning System) sensor 407, an electronic compass 408, and the like. In addition to these, the portable terminal 203 may include a call antenna, a call communication module, and the like.

  The CPU 400 controls the processes executed by the mobile terminal 203 in an integrated manner.

  The RAM 402 is used as a work area of the CPU 400, and temporarily stores various data such as contents processed by the CPU 400 and various application programs.

  The flash memory 401 stores various contents such as digital photograph images and moving images taken by the built-in camera 403, various control programs executed by the CPU 400, and various application programs.

  The liquid crystal display unit 411 is an LCD such as a TFT (Thin Film Transistor) or an OELD (Organic Electro-Luminescence Display), for example, and displays a so-called GUI. Further, the liquid crystal display unit 411 is provided integrally with the touch panel 410. The touch panel 410 detects a user's touch operation in a state where a photograph or GUI is displayed by executing an application, and notifies the CPU 400 of the touch operation. As an operation method of the touch panel 410, for example, a resistance film method or a capacitance method is used, but other methods may be used. The touch panel 410 enables, for example, the user to select a photo for full screen display while the photo display application is being executed, and to zoom in / out an image by pinch-in or pinch-out.

  The switch 412 receives a user operation that cannot be input on the touch panel 415, such as a power switch and a start button, and transmits an input signal to the CPU 400.

  The earphone 406 and the speaker 405 output an audio signal stored in the flash memory 401 or the like or input from the communication unit 413, the external I / F 414 or the like.

  The communication unit 413 performs communication processing with other devices via a network such as the Internet or a LAN (Local Area Network). The communication unit 413 may include a wireless LAN (Local Area Network) module or a WWAN (Wireless Wide Area Network) module.

  The external I / F (interface) 414 exchanges data in accordance with various standards such as USB (Universal Serial Bus) and HDMI (registered trademark) (High-Definition Multimedia Interface).

  A power source 415 is a power source for the portable terminal 203. Generally, a rechargeable power source such as a lithium ion battery is used.

<SDK>
FIG. 4 shows a software configuration example in the present embodiment. In order to control the digital camera 501 using the external device 502 in the present embodiment, it is necessary to install a communication application 503 for camera control. This application 503 is application software whose main purpose is to control the digital camera 501. The user can download the application 503 from a predetermined server on the Internet, for example, and install it on the external device 502. The application 503 includes, as a library, a camera connection SDK 504 (hereinafter referred to as an SDK) as a communication module with the digital camera 501. Direct communication with the digital camera 101 by the external apparatus 502 in which the application 503 is installed is performed via the SDK 504. That is, in the application 503, the SDK 504 is a software program mainly in communication with the digital camera 201. Other functions, such as accepting user operations, displaying a GUI, starting and ending the application 503, use software programs other than the SDK 504 in the application 503.

  In the present embodiment, an ordinary SDK for PC (hereinafter, SDK for PC) and an SDK for mobile terminal such as a mobile phone (hereinafter, SDK for mobile terminal) are prepared. Here, a normal PC here is assumed to be a desktop PC, a notebook PC or the like, whereas a mobile terminal is assumed to be a mobile phone or a tablet device represented by, for example, a so-called smart phone.

  It is assumed that any SDK is provided from the vendor of the digital camera 101 to the application developer. Therefore, the application developer determines which SDK is to be incorporated into the application 503 depending on whether the external device 502 on which the application is supposed to be installed is a PC or a portable terminal. Further, when it is desired to control the digital camera 101 with either a PC or a portable terminal, the vendor prepares two types, an application in which the SDK for PC is incorporated and an application in which the SDK for portable terminal is incorporated.

  Generally, mobile terminals such as mobile phones have different specifications in terms of processing capability and screen size compared to PCs. Therefore, in the present embodiment, processing that can be executed by an application for a PC is different from processing that can be executed by an application for a mobile terminal. In the present embodiment, control of executable processing according to the device is realized using the SDK.

  First, the configuration of the digital camera 201 will be described. The digital camera 201 has two controlled modes, a PC application mode and a mobile terminal application mode. The PC application mode is a mode controlled by a PC application in which a PC SDK is incorporated. The mobile terminal application mode is a mode controlled by an application of a mobile terminal in which the mobile terminal SDK is incorporated.

  Processing that can be executed from the external device in the two modes is managed by a table held in the nonvolatile memory 130 of the camera. An example of the management table in the present embodiment is shown in FIG. As shown in FIG. 5, the executable process is different between the PC application mode and the mobile terminal application mode.

<Digital camera / PC connection sequence>
FIG. 6 shows a processing sequence when the digital camera 201 and the PC 202 are connected in the present embodiment. The present sequence is started in response to establishment of a connection between the PC 202 on which the PC application is activated and the digital camera 201. Note that the processing of the digital camera 201 in this sequence is realized by a control unit such as the microcomputer 123 controlling each unit of the digital camera 201 according to an input signal or a program. Further, the processing of the PC 202 in this sequence is realized by the CPU 301 controlling each part of the PC 202 according to an input signal or a program.

  In the description of this sequence, a process for reading and executing a program (hereinafter referred to as a PC application) that does not depend on an SDK among PC applications and a process for reading and executing a PC SDK are described separately. Yes. Further, the description of this sequence includes a description as if these softwares are the main subject of processing in order to facilitate understanding. However, the actual operation subject is the CPU 301 that has read the PC application or the SDK for PC.

  First, the PC application makes a connection request to the PC SDK (S601).

  The SDK for PC that has received the connection request transmits a device information acquisition request to the digital camera 201 (S602).

  Upon receiving the acquisition request from the PC 202, the digital camera 201 transmits device information to the PC 202 (S651). This device information includes the operation corresponding to the digital camera 201, the valid event, and the current property.

  Here, the device information will be described in detail. The operation is a control command for the digital camera 201, and is mainly classified into an operation for transmitting an image of the digital camera 201 and an operation for controlling the photographing function of the digital camera 201. As an operation for transmitting an image of the digital camera 201, for example, there is “image acquisition” in which image data is transmitted from the digital camera 201 to an external device. A typical example of the operation for controlling the photographing function is “release” which causes the digital camera 201 to perform a still image photographing operation. In addition, there are “PC LiveView” for transmitting a so-called live view image from the digital camera 201 to an external device, “moving image recording start / end” for causing the digital camera 201 to perform a moving image shooting operation, and the like. Note that switching between the PC application mode and the mobile terminal application mode is also included in this operation. In S651, first, a switching operation between the PC application mode and the mobile terminal application mode is notified as an available operation.

  An event is information for notifying an external device of information generated by the digital camera 201. Examples of the event include an event when the setting value of the digital camera 201 is changed on the digital camera 201 side and an event when shooting is performed by an operation on the digital camera 201 side.

  The property is a parameter of the digital camera 201 and includes, for example, an aperture value, a shutter speed value, ISO sensitivity, and the like.

  It returns to the explanation of FIG. The PC SDK that has acquired the device information refers to the device information and determines whether the digital camera 201 supports the switching operation between the PC application mode and the mobile terminal application mode. If it is determined that the switching operation is supported, the digital camera 201 is requested to set the operation mode to the PC application mode (S603).

  Upon receiving the setting request, the digital camera 201 refers to the PC application mode controllable table 801 in FIG. Then, as the controllable functions, "image acquisition", "release", "camera parameter setting", "PC LiveView", and "moving image recording start / end" are added as usable operations (S652).

  Further, the digital camera 201 notifies the PC 202 to request reacquisition of device information in order to notify that a controllable function has been added (S653).

  Upon receiving the notification, the PC SDK transmits a device information reacquisition request to the digital camera 201 (S604).

  Upon receiving the device information reacquisition request, the digital camera 201 retransmits the current device information. Note that the device information transmitted here includes information related to the function added in S652. By receiving this device information in S654, the PC SDK can recognize the functions that can be used in the control of the digital camera 201.

  Next, a sequence for controlling the digital camera 201 from the PC application will be described.

  FIG. 8A shows a GUI screen displayed by the PC application when the PC application is activated. This screen may be displayed together with the activation of the PC application, or may be displayed after receiving notification that the processing from the PC SDK to S654 has been completed.

  The GUI screen shown in FIG. 8A includes an image acquisition button 801 and a camera control button 802. When the image acquisition button 801 is pressed by the user, processing for transmitting an image from the digital camera 201 to the PC 202 is started. The camera control button 802 is a button for shifting to a mode for remotely controlling the digital camera 201.

  When the camera control button 802 is pressed by the user, a camera control screen shown in FIG. 8B is displayed, and the digital camera 201 can be controlled from the PC 202. The functions of the digital camera 201 that can be controlled by the PC 202 include live view image display, still image shooting, moving image shooting, and exposure correction in the example of FIG. A live view button 814 is a button for setting whether to acquire and display a live view image from the digital camera 201. In the ON state, the PC 202 acquires a live view image from the digital camera 201 and displays it in the live view area 811. In the OFF state, the PC 202 does not acquire a live view image from the digital camera 201, and the live view area 811 is not displayed. The still image shooting button 812 is a button for instructing the digital camera 201 to take a still image. A movie shooting button 813 is a button for instructing the digital camera 201 to shoot a movie. If the moving image shooting button 813 is pressed during moving image shooting, the PC 202 instructs the digital camera to stop moving image shooting. The exposure correction button is a button for instructing the digital camera 201 to shoot a still image. When the exposure correction button is pressed by a user operation, correction value candidates (for example, −2 to +2) are displayed, and a desired correction value is set. Can do.

  Next, a case where the image acquisition button 801 on the GUI screen is pressed by a user operation will be described. The PC application requests the PC SDK to acquire image information in response to detecting the user operation (S605). The image information in the present embodiment is, for example, an ID for specifying an image such as a file name, a file size, and a file format. A thumbnail corresponding to an image may be transmitted as image information. The PC SDK transmits an image information acquisition request to the digital camera 201 (S606).

  In step S655, the PC SDK receives image information from the digital camera 201, and transfers the image information received in step S607 to the PC application. The PC application displays a list of file names and thumbnails based on the image information acquired in S607, and allows the user to select an image to be acquired. Then, the PC application requests the PC SDK to acquire an image (S608). This request includes the ID of the image selected as the acquisition target.

  When the PC SDK receives the image acquisition request, the PC SDK determines whether the image acquisition request from the PC application is valid based on whether the operation received in S654 is “image acquisition”. . When it is determined that the image acquisition request is valid, the PC SDK transmits the image acquisition request to the digital camera 201 together with the ID of the acquisition target image in S609.

  Upon receiving the image acquisition request in S609, the digital camera 201 reads an image having the acquisition target ID from the memory 120 and transmits the image to the PC SDK (S656).

  In step S610, the PC SDK passes the received image to the PC application. By this processing, the PC application can display the image received from the digital camera 201.

  Next, a case where the camera control button 703 on the UI screen 701 of the PC application is pressed by a user operation will be described. In this case, the PC application displays the camera control UI screen shown in FIG. 8B in S611 and makes a PC live view request to the PC SDK.

  When the PC SDK receives the PC live view request, the PC SDK determines whether the operation acquired in S654 includes PC LiveView. If it is included, in S612, the PC live view request is transmitted to the digital camera 201.

  Upon receiving the PC live view request, the digital camera creates a PC live view image, and transmits the PC live view image to the PC SDK in step S657.

  Then, in S613, the PC SDK passes the received PC live view image to the PC application. By this processing, the PC application can display the live view image received from the digital camera 201.

  Next, a case where the still image shooting button 812 of the PC application is pressed by the user operation will be described.

  When the still image shooting button 812 is pressed by a user operation, the PC application makes a release request to the PC SDK in S614.

  When the PC SDK receives a release request, it determines whether the operation acquired in S654 includes a release. If it is included, a release request is transmitted to the digital camera 201 in S615.

  Upon receiving the release request, the digital camera 201 performs a release operation in S658, so that a new shooting is performed and an image is acquired. After acquiring the image, the digital camera 201 transmits an image addition event to the SDK for PC in S659. The PC SDK transmits the image addition event received in S616 to the PC application. By this, the PC application can recognize that a new image has been obtained on the digital camera 201 side.

<Digital camera / mobile terminal connection sequence>
FIG. 7 shows a processing sequence when the digital camera 201 and the portable terminal 203 in this embodiment are connected. This sequence is started in response to establishment of a connection between the portable terminal 203 on which the portable terminal application is activated and the digital camera 201. Note that the processing of the digital camera 201 in this sequence is realized by a control unit such as the microcomputer 123 controlling each unit of the digital camera 201 according to an input signal or a program. Further, the processing of the mobile terminal 203 in this sequence is realized by the CPU 400 controlling each unit of the mobile terminal 203 according to an input signal or a program.

  In the description of this sequence, a process for reading and executing a program (hereinafter referred to as a mobile terminal application) that does not depend on the SDK among mobile terminal applications and a process for reading and executing the mobile terminal SDK are divided. It is described. Further, the description of this sequence includes a description as if these softwares are the main subject of processing in order to facilitate understanding. However, the actual action entity is the CPU 400 that has read the mobile terminal application or the mobile terminal SDK.

  Note that this sequence has many processes that are different from the sequence of FIG. 6 only in whether the PC 202 or the mobile phone 203 is different. Therefore, description of these processes will be omitted as appropriate.

  First, S701, S702, and S751 are the same processes as S601, S602, and S651 in FIG.

  The mobile terminal SDK that has acquired the device information in step S751 refers to the device information to determine whether the digital camera 201 supports the switching operation between the PC application mode and the mobile terminal application mode. If it is determined that the switching operation is supported, the digital camera 201 is requested to set the operation mode to the mobile terminal application mode (S703).

  Upon receiving the setting request, the digital camera 201 refers to the PC application mode controllable table 801 in FIG. 5 and adds “image acquisition” and “resize image acquisition” as controllable functions as usable operations. (S752). The operation added here is different from that in the PC application mode. That is, the digital camera 201 determines whether or not the partner apparatus is a portable terminal according to the information of the mode notified from the SDK, and restricts available functions when the other apparatus is a portable terminal.

  S753, S704, and S754 are the same processes as S653, S605, and S654 of FIG.

  FIG. 8C shows an example of the screen of the mobile terminal application. Unlike the PC application, the mobile terminal application in the present embodiment does not have a function of remotely controlling photographing with the digital camera 201 and has a function of acquiring an image of the digital camera. Therefore, on the screen 851, a button 852 for instructing image acquisition is displayed.

  Next, a case where the image acquisition button 852 is pressed by a user operation will be described. Since a general portable terminal has a lower data processing capacity than a PC, it may take time to receive or display a large size of data. Therefore, when an image of a large size is to be received, the mobile terminal application in the present embodiment requests the digital camera 201 to resize the image and transmit the image in a small size.

  Returning to the description of FIG. S705, S706, S755, and S707 when a user operation for pressing the image acquisition button 852 is detected are the same as S605, S606, S655, and S607 in FIG. Then, as in the case of the PC application, the mobile terminal application displays a list of file names and thumbnails based on the image information acquired in S707, and allows the user to select an image to be acquired.

  When the image to be acquired is selected, the portable terminal application determines whether the size of the selected image is equal to or more than a predetermined value based on the image information acquired in S707. As the predetermined value here, a specific number of bytes (for example, whether or not 5 MB or more) held in advance by the mobile terminal application can be used. For example, if the image size received in S755 includes information indicating a size such as S, M, or L, this size information may be used (for example, whether the size is M or larger). When it is determined that the selected image is not equal to or greater than the predetermined value, the mobile terminal application delivers an image acquisition request to the mobile terminal SDK, as with the PC application. If it is determined that the selected image is equal to or greater than the predetermined value, the portable terminal application passes a resized image acquisition request to the portable terminal SDK so as to request an image of a smaller size.

  First, the case where it is determined that the size of the selected image is not the predetermined value or more will be described. In this case, the mobile terminal application requests the mobile terminal SDK to obtain an image (S 708). This request includes the ID of the image to be acquired.

  When the mobile terminal SDK receives the image acquisition request, the mobile terminal SDK determines whether the image acquisition request from the mobile terminal application is valid based on whether or not the operation received in S754 includes “image acquisition”. Judging. If it is determined that the image acquisition request is valid, the mobile terminal SDK transmits the image acquisition request to the digital camera 201 together with the ID of the image to be acquired in S709.

  When the digital camera 201 receives the image acquisition request in S709, the digital camera 201 reads an image having an acquisition target ID from the memory 120, and transmits the image to the mobile terminal SDK (S756).

  In step S710, the PC SDK passes the received image to the PC application. By this processing, the PC application can display the image received from the digital camera 201.

  Next, the case where it is determined that the size of the selected image is equal to or larger than a predetermined value will be described. In this case, the mobile terminal application requests the SDK for mobile terminal to obtain a resized image (S711). This request includes the ID of the image to be acquired.

  When the mobile terminal SDK accepts the resize image acquisition request, the mobile terminal SDK receives a resize image acquisition request from the mobile terminal application based on whether or not “acquire resize image” is included in the operation received in S754. Determine whether it is valid. If it is determined that the resized image acquisition request is valid, the mobile terminal SDK transmits the resized image acquisition request to the digital camera 201 together with the ID of the image to be acquired in S 712.

  When the digital camera 201 receives a resized image acquisition request in step S712, the digital camera 201 reads an image having an ID to be acquired from the memory 120 and resizes it to a predetermined size. The size of the resized image may be stored in advance by the digital camera 201 or may be notified to the digital camera 201 by the mobile terminal SDK. After generating the resized image, the digital camera 201 transmits the image to the mobile terminal SDK (S757). Note that the resized image acquisition operation of the present embodiment is both a resize operation and an image acquisition operation. As another method, there is a method in which resizing operation is provided, and the mobile terminal SDK specifies the image ID to the digital camera 201 and instructs resizing. In this case, the digital camera 201 notifies the mobile terminal SDK when the resizing is completed, and the mobile terminal SDK acquires a resized image by an image acquisition operation.

  Then, in step S713, the mobile terminal SDK passes the received resized image to the mobile terminal application. By this processing, the PC application can display the image received from the digital camera 201.

  When a plurality of images are selected as acquisition targets, the mobile terminal application determines whether to perform an image acquisition request or a resized image acquisition request for each image, and performs a request according to the determination result.

  The mobile terminal application in the present embodiment does not have a GUI for performing live view or release. However, even if the mobile terminal SDK receives a PC live view request or release request from a mobile terminal application having a GUI for performing live view or release, the mobile terminal SDK returns an error (S714). ~ S717). By doing this, it is possible to perform appropriate error notification without requiring communication with the digital camera 201.

  When the application ends for both the PC application and the mobile terminal application, disconnection processing is performed on the digital camera 201 from each SDK, and the control function added in each mode is deleted.

  With the above configuration, even when the hardware specifications are different, such as a PC and a mobile terminal, it is possible to provide an optimal control function for a control terminal connected to the digital camera.

  The type of operation is not limited to that shown in the present embodiment, and the configuration of the table is not limited to that shown in FIG. For example, even in the case of a portable terminal, it may be considered that remote photographing is performed at the time of commemorative photographing of a sightseeing spot or the like. Therefore, the release and PC LiveView may be available operations even in the mobile terminal application mode. In this case, an operation for transmitting a live view image with a lower image quality or transfer rate than that of PC LiveView may be separately provided and used in the mobile terminal application mode. In addition, since it is considered that there are not many opportunities for detailed parameter setting in the mobile terminal, it is possible that the camera parameter setting is not made available even if the release is available. Further, the camera parameter setting may be divided into a plurality of operations according to the parameters so that only a part of the operations can be used in the mobile terminal.

Second Embodiment
In the first embodiment, an example in which available operations are different depending on whether the communication partner is a PC or a portable terminal has been described. On the other hand, in the present embodiment, the available operation is switched depending on whether it is an application made by a digital camera vendor or not. Opening the SDK for controlling the digital camera to a third party other than the vendor of the digital camera and creating an application is desirable in the sense of expanding the use of the camera system. However, on the other hand, if all operations are available, it is desirable to put certain restrictions on available operations, since unexpected control may be performed at the vendor side.

  Therefore, in the present embodiment, the available operations differ depending on whether the application is provided by a digital camera vendor.

  Hereinafter, this embodiment will be described in detail. Since this embodiment has many parts in common with the first embodiment, description of the common parts will be omitted, and description will be made centering on parts unique to the present embodiment.

  The digital camera 201 of the present embodiment has a mode (vendor application mode) for communicating with a PC application created by the vendor of the digital camera 201 (hereinafter referred to as vendor application), and a PC application created by a third party other than the vendor (hereinafter referred to as standard). Mode (standard application mode). The two modes have different usable operations, and a table indicating the relationship between the modes and the operations is held in the nonvolatile memory 130. FIG. 9 shows an example of the table. In the example of FIG. 9, in the vendor application mode, “image acquisition”, “release”, “camera parameter setting”, “PC Liveview”, and “moving image recording start / end” can be used. In the standard application mode, “image acquisition” can be used. The PC SDK similarly has a vendor application mode and a standard application mode, and operates in the standard application mode unless an instruction is issued from the PC application.

  The sequence which shows the process at the time of the company application mode in Example 2 of this invention is shown in FIG.

  The sequence which shows the process at the time of the other company application mode in Example 2 of this invention is shown in FIG.

  Hereinafter, referring to the table of FIG. 9 and the sequence of FIGS. 11 and 12, according to the connection mode from the SDK of the PC to the digital camera according to the first embodiment of the present invention, the functions provided by the digital camera The change will be described.

<Digital camera / vendor application connection sequence>
FIG. 6 shows a processing sequence when the digital camera 201 and the PC 202 are connected in the present embodiment. In addition, this flow demonstrates the case where a vendor application starts on PC202.

  First, at S1001, the vendor application requests the SDK for PC to set the connection mode to the vendor application mode.

  In step S1002, the PC SDK switches the PC SDK connection mode from the standard application mode to the vendor application mode.

  Subsequently, in S1003, the vendor application passes the connection request to the SDK for PC.

  S1004 and S1051 are the same processes as S602 and S651 of FIG.

  The PC SDK that has acquired the device information in S1051 refers to the device information and determines whether the digital camera 201 supports the switching operation between the vendor application mode and the standard application mode. If it is determined that the switching operation is supported, the digital camera 201 is requested to set the operation mode to the vendor application mode in accordance with its own mode (S1005).

  When the digital camera 201 receives the setting request, it refers to the table of the vendor application mode of FIG. Then, as a controllable function, "image acquisition", "release", "camera parameter setting", "PC LiveView", and "moving image recording start / end" are added as usable operations (S1052).

  The subsequent steps S1006 to S1018 and S1053 to S1059 are similar to the steps S604 to S616 and S653 to S659 of FIG.

<Digital camera / standard application connection sequence>
Next, FIG. 11 shows a processing sequence when the digital camera 201 and the PC 202 in the present embodiment are connected. In addition, this flow demonstrates the case where a standard application starts on PC202.

  When the standard application on the PC 202 starts up, the standard application passes the connection request to the SDK for PC. A major difference from the vendor application here is that the mode setting of the SDK for PC is not required as in S1001 of FIG. As mentioned above, the SDK for PC operates in the standard application mode unless requested by the PC application.

  S1102 and S1151 are the same processes as S602 and S651 of FIG.

  The PC SDK that has acquired the device information in S1151 refers to the device information and determines whether the digital camera 201 supports the switching operation between the vendor application mode and the standard application mode. If it is determined that the switching operation is supported, the digital camera 201 is requested to set the operation mode to the standard application mode in accordance with its own mode (S1103).

  Upon receiving the setting request, the digital camera 201 refers to the table in the vendor application mode of FIG. 9 and adds “image acquisition” as an available operation as a controllable function (S1152).

  The subsequent steps S1104 to S1110 and S1153 to S1156 are the same as the steps S604 to S610 and S653 to S656 in FIG.

  Next, the case where the SDK for PC receives a live view request for PC from a standard application will be described (S1111). In this case, the PC SDK determines whether the operation acquired in step S1154 includes PC LiveView. If the PC SDK is in the standard application mode, the PC LiveView operation cannot be acquired in S1154, and the PC SDK returns an error to the standard application (S1112). Similarly, when a release request is issued from the standard application to the PC SDK (S1113), the PC SDK returns an error (S1114).

  As described above, the SDK according to the present embodiment controls the mode of the digital camera according to whether it is incorporated in the standard application or the vendor application, and controls the available operations differently. did. By doing this, it is possible to appropriately limit the operations available to the app.

  Although the case where the vendor application and the standard application are prepared for the PC application has been described in this embodiment, the vendor application and the standard application may be prepared for the mobile terminal application, and different operations may be used.

Third Embodiment
In the first embodiment, although the table configuration is provided with a large number of operations that can be used by the PC application because the PC has a higher specification than the portable terminal, the present invention is not necessarily limited to this configuration.

  For example, in the case of a portable terminal that is usually carried outside, it may be desirable to be able to perform remote photographing, such as taking a picture by operating the portable terminal in the case of a portable terminal carried around outside.

  Therefore, the table configuration shown in FIG. 12 may be used so that operations cannot be restricted or used from the PC, and the camera can be controlled only from the mobile terminal.

  By configuring as described above, it is possible to provide a camera control function that is suitable for usage modes such as a PC and a portable terminal.

Other Embodiments
As mentioned above, although preferable embodiment of this invention was described, this invention is not limited to these embodiment, A various deformation | transformation and change are possible within the range of the summary.

  The present invention can also be realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, or the like) of the system or apparatus reads the program. It is a process to be executed.

Claims (11)

A communication device,
A communication means for communicating with an external device using a communication application including a first program for accepting a user operation for communication with the communication device and a second program for communicating with the communication device;
Notification means for notifying the external device of operations available to the external device among operations for controlling the communication device in communication between the communication device and the external device;
And determining means for determining whether the second program used by the external device is a program provided by the vendor of the communication device , the notification means including the second program for the vendor of the communication device. A communication apparatus characterized in that an operation to be notified varies depending on whether or not the program is provided .   When the notification means determines that the second program is not a program provided by a vendor of the communication device, the notification means determines that the second program is a program provided by a vendor of the communication device The communication apparatus according to claim 1, wherein the operation of notifying is restricted in comparison with.   The communication device according to claim 2, further comprising a photographing unit configured to photograph a subject.   The communication apparatus according to claim 3, wherein the operation includes an operation of acquiring image data of the communication apparatus.   The communication apparatus according to claim 4, wherein the operation includes at least one operation related to remote imaging using the external apparatus.   The communication apparatus according to claim 5, wherein the operation related to remote shooting includes at least one of still image shooting, moving image shooting, live view image acquisition, and shooting parameter control. When it is determined by the determination unit that the second program is not the program provided by the vendor of the communication apparatus, the notification unit can use at least one of the operations related to remote imaging using the external device. The communication apparatus according to claim 5 or 6, wherein the external apparatus is not notified as an operation. When the determination unit determines that the second program is a program provided by a vendor of the communication apparatus, the notification unit notifies an operation for acquiring the image data as the available operation. The communication apparatus according to any one of claims 4 to 7. If it is determined by the determination unit that the second program is a program provided by the vendor of the communication device, it is determined that the second program is determined not to be a program provided by the vendor of the communication device. The communication device according to any one of claims 2 to 8, wherein the external device is notified of many operations. A control method of the communication device,
A communication step of communicating with an external device using a communication application including a first program for accepting a user operation for communication with the communication device and a second program for communicating with the communication device;
Among the operations for controlling the communication device in communication between the communication device and the external device, a notification step of notifying the external device of an operation that can be used by the external device;
Determining whether the second program used by the external device is a program provided by the vendor of the communication device, and in the notifying step, the vendor of the communication device is the second program. A control method of a communication apparatus, wherein an operation to be notified is made different depending on whether or not a program to be provided is provided .   A computer readable program which causes a computer of a communication device to function as each means of the communication device according to any one of claims 1 to 9.

Images