阅读说明：本技术 通信系统、通信设备及其控制方法和程序 (communication system, communication device, control method therefor, and program ) 是由 小山润 于 2018-03-02 设计创作，主要内容包括：根据本发明,为了使得服务器侧能够在拉式传输型通信协议中、在用户期望的定时中断信息的传送,客户端具有用于向服务器发送内容请求的第一请求单元,并且服务器具有用于向客户端发送第一请求单元所请求的内容的第一响应单元。此外,客户端具有用于请求服务器在达到规定状态的情况下作出响应的第二请求单元,并且服务器具有用于在接收到来自第二请求单元的请求时、在未达到规定状态的情况下暂停响应的提供并在达到规定状态的情况下向客户端发送响应。(According to the present invention, in order to enable the server side to interrupt the transfer of information at a timing desired by the user in the pull transmission type communication protocol, the client has a first request unit for transmitting a content request to the server, and the server has a first response unit for transmitting the content requested by the first request unit to the client. Furthermore, the client has a second request unit for requesting the server to respond if the prescribed state is reached, and the server has a function for suspending the provision of a response if the prescribed state is not reached and transmitting a response to the client if the prescribed state is reached, upon receiving a request from the second request unit.)

1. A communication system comprising a client and a server for sending information in response to a request from the client, characterized in that,

The client comprises:

First requesting means for sending a content request to the server, the server comprising:

A first response component for transmitting the content requested from the first request component to the client, the client further comprising:

Second requesting means for requesting the server to respond in the case where a predetermined state has occurred, and

The server further comprises:

Second response means for delaying a response if the predetermined state has not occurred and transmitting the response to the client if the predetermined state has occurred, in a case where the request by the second request means is received.

2. The communication system of claim 1,

The client comprises:

First acquisition means for transmitting a request for an information list of an object to be forwarded as the first request means and acquiring the information list,

Second acquisition means for requesting the server for each information indicated in the information list acquired by the first acquisition means and acquiring each information, an

And an ending section configured to end processing related to information reception when a response to the second requesting section is received.

3. The communication system of claim 2,

the server includes:

first display means for list-displaying the object to be forwarded so that the user can select the object to be forwarded, in the case where a request for the information list is received, and

A generation section for generating a list describing information for specifying information selected by a user from the information displayed in the list, an

The first responding section responds with the list generated by the generating section as the information list.

4. The communication system according to any of claims 1 to 3,

The server is an image pickup apparatus including image pickup means and storage means for storing an image obtained by image pickup by the image pickup means,

the client is a portable terminal for receiving the image from the server, an

The server and the client each communicate via a wireless communication component.

5. the communication system according to any of claims 1 to 4,

The second response section includes a second display section for displaying a UI for interrupting information forwarding in a case where a request from the second request section is received, and makes a response indicating that the predetermined state has occurred in a case where the UI is operated.

6. The communication system of claim 2,

The second response component includes:

A second display section for displaying a UI for interrupting information forwarding in a case where a request from the second request section is received, and

A monitoring section for monitoring whether a preset state change has occurred, and the second responding section, in a case where the UI is operated, transmits a response indicating that the operation has been performed, and in a case where the state change has occurred, transmits a response indicating that the state change has occurred to the client, and

The ending section ends processing related to information reception in a case where a response indicating an operation on the UI is received, and causes the second requesting section to make a request again in a case where a response indicating a state change other than the operation on the UI is received.

7. a communication device, comprising:

First receiving means for receiving a content request from a client;

First transmitting means for transmitting, to the client, content corresponding to the content request in response to the first receiving means receiving the content request;

second receiving means for receiving a predetermined request from the client;

Display means for displaying a UI for interrupting the content transmission processing by the first transmission means, in a case where the second reception means receives the predetermined request; and

second transmission means for transmitting a predetermined response to the predetermined request to the client in a case where the UI displayed by the display means is operated,

Wherein the content transmission processing by the first transmission means is interrupted by the second transmission means transmitting a response.

8. A method for controlling a communication device, comprising:

A first receiving step of receiving a content request from a client;

A first transmission step of transmitting content corresponding to the content request to the client in response to receiving the content request in the first reception step;

A second receiving step of receiving a predetermined request from the client;

A display step of displaying a UI for interrupting the content transmission processing performed by the first transmission step, in a case where the predetermined request is received in the second reception step; and

A second transmission step of transmitting a predetermined response to the predetermined request to the client in a case where the UI displayed in the display step is operated,

Wherein the content transmission processing performed by the first transmission step is interrupted by transmission of a response in the second transmission step.

9. A program for reading and executing by a processor of a communication device to cause the processor to perform the steps of the method of claim 8.

10. A server device in communication with a client device, comprising:

First receiving means for receiving a first request for executing a predetermined process from the client apparatus;

First processing means for starting the predetermined processing in response to the first receiving means receiving the first request;

Second receiving means for receiving, from the client device, a second request for interrupting the predetermined processing performed by the first processing means; and

Control means for controlling transmission of a response to the first request and the second request,

Wherein the control means delays a response to the second request during the predetermined processing by the first processing means in response to the first request, and transmits the delayed response to the second request if the predetermined processing is interrupted by the first processing means.

11. the server apparatus according to claim 10, comprising:

Display means for performing, in response to the second receiving means receiving the second request, display for accepting an instruction to interrupt the predetermined processing performed by the first processing means.

12. The server device according to claim 11,

The first processing section interrupts the predetermined processing in response to the display section accepting an instruction to interrupt the predetermined processing.

13. The server device according to any one of claims 10 to 12,

The predetermined processing is processing for transmitting content included in the server device to the client device in response to the first request.

14. The server device according to any one of claims 10 to 13,

the second receiving means receives the second request before the first receiving means receives the first request.

Technical Field

The present invention relates to a communication system, a communication apparatus, a control method thereof, and a program.

Background

The development of communication functions of image processing apparatuses (or image pickup apparatuses) such as digital cameras has enabled digital cameras, PCs, and mobile phones, for example, to communicate with each other and exchange content. Currently, cameras can also be used as servers to enable remote shooting by using server/client systems such as HTTP. In systems such as server/client systems, there are often certain limitations to providing some kind of notification from a server to a client autonomously.

In this regard, it is contemplated that the server autonomously notifies the client at the necessary timing by first sending a request by the client and the server maintaining a delayed state of its response. As such a method, there is a method of transmitting a status notification request in advance and returning a response at a timing at which the server status has changed (patent document 1).

reference list

Patent document

Patent document 1: japanese patent laid-open publication No. 2013-21526

disclosure of Invention

Problems to be solved by the invention

However, the method according to patent document 1 assumes only the state notification of the server. Depending on the application scope of the server/client system, there may be situations where notifications other than status notifications are desired.

Means for solving the problems

To solve this problem, a communication system according to the present invention includes, for example, the following structures: a communication system comprising a client and a server for transmitting information in response to a request from the client, characterized in that the client comprises: first requesting means for sending a content request to the server, the server comprising: a first response component for transmitting the content requested from the first request component to the client, the client further comprising: second requesting means for requesting the server to respond in the case where a predetermined state has occurred, and the server further includes: second response means for delaying a response if the predetermined state has not occurred and transmitting the response to the client if the predetermined state has occurred, in a case where the request by the second request means is received.

ADVANTAGEOUS EFFECTS OF INVENTION

according to the present invention, the forwarding of information can be interrupted at a timing desired by the user on the server side.

Other features and advantages of the present invention will become apparent from the following description taken in conjunction with the accompanying drawings. Note that throughout the drawings, the same reference numerals designate the same or similar components.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.

Fig. 1A is a block diagram showing the structure of a digital camera according to the embodiment.

Fig. 1B is a front view of a digital camera according to an embodiment.

Fig. 1C is a back view of a digital camera according to an embodiment.

Fig. 2 is a block diagram showing the structure of a smart device according to the embodiment.

Fig. 3A is a diagram showing a list of APIs provided by the digital camera according to the embodiment.

Fig. 3B is a diagram showing a list of APIs provided by the digital camera according to the embodiment.

Fig. 4 is a diagram showing an example of a communication sequence between the digital camera and the smart device according to the first embodiment.

Fig. 5A is a diagram showing a user interface screen of a digital camera according to the embodiment.

Fig. 5B is a diagram showing a user interface screen of the digital camera according to the embodiment.

Fig. 5C is a diagram showing a user interface screen of the digital camera according to the embodiment.

Fig. 6A is a flowchart showing a processing procedure of the digital camera according to the first embodiment.

Fig. 6B is a flowchart showing a processing procedure of the digital camera according to the first embodiment.

Fig. 7 is a flowchart showing a processing procedure of the smart device according to the first embodiment.

Fig. 8A is a diagram showing an example of a communication sequence between the digital camera and the smart device according to the second embodiment.

Fig. 8B is a diagram showing an example of a communication sequence between the digital camera and the smart device according to the second embodiment.

Fig. 9A is a flowchart showing a processing procedure of the digital camera according to the second embodiment.

Fig. 9B is a flowchart showing a processing procedure of the digital camera according to the second embodiment.

fig. 10A is a flowchart showing a processing procedure of the smart device according to the second embodiment.

Fig. 10B is a flowchart showing a processing procedure of the smart device according to the second embodiment.

fig. 11A is a diagram showing an example of a communication sequence between the digital camera and the smart device according to the third embodiment.

Fig. 11B is a diagram showing an example of a communication sequence between the digital camera and the smart device according to the third embodiment.

Fig. 12A is a flowchart showing a processing procedure of the digital camera according to the third embodiment.

Fig. 12B is a flowchart showing a processing procedure of the digital camera according to the third embodiment.

fig. 13A is a flowchart showing a processing procedure of the smart device according to the third embodiment.

Fig. 13B is a flowchart showing a processing procedure of the smart device according to the third embodiment.

Detailed Description

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments described later are merely typical means for implementing the present invention, and may be modified or changed as appropriate depending on the structure of an apparatus to which the present invention is applied and various conditions. The embodiments may also be combined as appropriate.

[ first embodiment ]

< construction of digital Camera 100 >

Fig. 1A is a block diagram showing a typical structure of a digital camera 100 serving as a member of a communication system to which the present embodiment is applied. Note that although a digital camera that can record image data in a recording medium will be described here as an example of a communication apparatus, the communication apparatus is not limited thereto. For example, the communication apparatus may be a portable media player, a so-called tablet device, a personal computer, or an information processing apparatus connected to or incorporated in various facilities. In addition, the data to be processed is not limited to image data, and may be audio data or document data or the like.

the control unit 101 controls various units of the digital camera 100 according to an input signal and a program described later. Note that, instead of the control unit 101 controlling the entire apparatus, the entire apparatus may be controlled by a plurality of hardware sharing the processing among them.

The image pickup unit 102 is configured of, for example, an optical lens unit, an optical system for controlling an aperture, zooming, focusing, and the like, an image pickup element for converting light (video image) introduced through the optical lens unit into an electric image signal, and the like. Generally, CMOS (complementary metal oxide semiconductor), CCD (charge coupled device), or the like is used as an image pickup element. By the control of the control unit 101, the image pickup unit 102 converts object light imaged by a lens included in the image pickup unit 102 into an electric signal using an image pickup element, performs noise reduction processing or the like, and outputs digital data as image data. The control unit 101 of the digital camera 100 according to the present embodiment encodes captured image data and records the encoded data as a file in the recording medium 110 according to DCF (design rule for camera file system).

The nonvolatile memory 103 is an electrically erasable/recordable nonvolatile memory, and stores, for example, a program described later executed by the control unit 101 and various types of data related to settings. The work memory 104 functions as a buffer memory for temporarily holding image data captured by the image capturing unit 102, an image display memory of the display unit 106, a work area of the control unit 101, or the like.

The operation unit 105 is used to accept an instruction given from the user to the digital camera 100. The operation unit 105 includes, for example, a power button for enabling a user to make an instruction to turn on/off the power of the digital camera 100, a release switch for instructing image capturing, and a reproduction button for instructing reproduction of image data. The operation unit 105 also includes an operation member such as a dedicated connection button for starting communication with an external device via a communication unit 111 described later. The operation unit 105 includes a touch panel formed on a display unit 106 described later. Note that the release switch includes a first switch and a second switch for detecting a pressed state in two stages. When the release switch enters a so-called half-pressed state, the first switch is turned on. Therefore, an instruction to perform image capturing preparation such as AF (auto focus) processing, AE (auto exposure) processing, AWB (auto white balance) processing, and EF (electronic flash pre-emission) processing is accepted. When the release switch enters a so-called fully-depressed state, the second switch is turned on. Therefore, an instruction to perform imaging is received.

The display unit 106 displays a viewfinder image during image capturing, captured image data, and various menus and characters for interactive operations, and the like. Note that the display unit 106 does not have to be built into the digital camera 100. It is sufficient that the digital camera 100 can be connected to an internal or external display unit 106 and include at least a display control function for controlling display of the display unit 106. Note that the operation unit 105 and the display unit 106 constitute a user interface of the digital camera.

The recording medium 110 can record a file of image data output from the image capturing unit 102. The recording medium 110 may be configured to be removable from the digital camera 100, or may be built into the digital camera 100. That is, it is sufficient that the digital camera 100 includes at least a means for accessing the recording medium 110.

The communication unit 111 is an interface for connecting to an external device. The digital camera 100 according to the present embodiment can exchange data with an external device via the communication unit 111. For example, the image data generated by the image capturing unit 102 may be transmitted to an external apparatus via the communication unit 111. Note that, in the present embodiment, the communication unit 111 includes an interface for communicating with an external device using a so-called wireless LAN compliant with the IEEE802.11 standard. The control unit 101 realizes wireless communication with an external device by controlling the communication unit 111. Note that the communication method is not limited to the wireless LAN, and may include, for example, a wireless communication method such as an infrared communication method, a Bluetooth (registered trademark) communication method, and a wireless USB. Further, wired connections such as USB cable, HDMI, IEEE 1394, and ethernet may be employed. The communication unit 111 is an example of a first wireless communication section.

The short-range communication unit 112 is constituted by, for example, an antenna for wireless communication, and a modulation/demodulation circuit and a communication controller for processing wireless signals. The short-range communication unit 112 realizes short-range communication compliant with the ISO/IEC18092 standard (so-called NFC: near field communication) by outputting a modulated wireless signal from an antenna and demodulating a wireless signal received by the antenna. In addition, the short-range wireless communication is realized in accordance with a wireless communication method such as an infrared communication method, a bluetooth (registered trademark) communication method, and a wireless USB. The short-range communication unit 112 according to the present embodiment is an example of a second wireless communication section provided at the side of the digital camera 100.

the digital camera 100 according to the present embodiment is connected to the smart device 200 by starting communication with the smart device 200, which will be described later, using the communication unit. The communication unit 111 of the digital camera 100 according to the present embodiment has an AP mode in which the communication unit 111 functions as an access point in the infrastructure mode, and a CL mode in which the communication unit 111 functions as a client in the infrastructure mode. Then, by causing the communication unit 111 to operate in the CL mode, the digital camera 100 according to the present embodiment can operate as a CL device in the infrastructure mode. In the case where the digital camera 100 operates as a CL device, the digital camera 100 can join the network formed by the AP devices by connecting to the peripheral AP devices. By causing the communication unit 111 to operate in the AP mode, the digital camera 100 according to the present embodiment can operate as a simplified AP (hereinafter referred to as "simple AP") which is a kind of AP but has more limited functions. In the case where the digital camera 100 operates as a simple AP, the digital camera 100 itself forms a network. The peripheral devices of the digital camera 100 recognize the digital camera 100 as an AP device and can join the network formed by the digital camera 100. A program for causing the digital camera 100 to operate in the above-described manner is held in the nonvolatile memory 103, and the user selects between the AP mode and the CL mode by operating the operation unit 105.

Note that the digital camera 100 according to the present embodiment is a kind of AP, but is a simple AP that does not have a gateway function for forwarding data received from a CL device to an internet service provider or the like. Therefore, even in the case where the digital camera 100 receives data from other devices that have joined the network formed by the digital camera 100, the digital camera 100 cannot forward the data to a network such as the internet.

< appearance of digital Camera 100 >

Next, the appearance of the digital camera 100 will be explained. Fig. 1B and 1C are front and back views, respectively, of an appearance example of the digital camera 100. The release switch 105a, the reproduction button 105b, the direction key 105c, and the touch panel 105d are operation members included in the operation unit 105 described above. An image obtained as a result of imaging performed by the imaging unit 102 is displayed on the display unit 106. The structure of the digital camera 100 according to the present embodiment is explained above.

< internal Structure of Smart device 200 >

Fig. 2 is a block diagram showing a typical structure of a smart device 200, wherein the smart device 200 is an example of an information processing apparatus (terminal apparatus) for communicating with the digital camera 100 according to the present embodiment. Note that the smart device means a portable terminal such as a smart phone and a tablet device. Although a smart device will be described here as an example of the information processing apparatus, the information processing apparatus is not limited thereto. For example, the information processing apparatus may be a digital camera, a printer, a television, or a personal computer having a wireless function.

The control unit 201 controls various units of the smart device 200 according to the input signal and a program described later. Note that, instead of the control unit 201 controlling the entire apparatus, a plurality of pieces of hardware may share processing among them to control the entire apparatus.

The image pickup unit 202 converts subject light imaged by a lens included in the image pickup unit 202 into an electric signal, performs noise reduction processing or the like, and outputs digital data as image data. The captured image data is accumulated in a buffer memory, and then subjected to predetermined arithmetic operation or encoding processing by the control unit 201, and recorded as a file in the recording medium 210.

The nonvolatile memory 203 is an electrically erasable/recordable nonvolatile memory. In the nonvolatile memory 203, an OS (operating system) serving as basic software executed by the control unit 201, and an application for realizing an application function in cooperation with the OS are recorded. In the present embodiment, the nonvolatile memory 203 stores an application (hereinafter referred to as "app") for communicating with the digital camera 100.

The work memory 204 is used as an image display memory of the display unit 206, a work area of the control unit 201, and the like. The operation unit 205 is used to accept an instruction from the user to the smart device 200. The operation unit 205 includes, for example, a power button for causing a user to instruct to turn on/off the power of the smart device 200, and an operation member such as a touch panel or the like formed on the display unit 206. The display unit 206 displays image data, characters for interactive operation, and the like. Note that the display unit 206 need not be included in the smart device 200. It is sufficient that the smart device 200 is capable of being connected to the display unit 206 and includes at least a display control function for controlling the display of the display unit 206. Note that the operation unit 205 and the display unit 206 constitute a user interface of the smart device 200.

The recording medium 210 can record image data output from the image capturing unit 202. The recording medium 210 may be configured to be removable from the smart device 200, or may be built into the smart device 200. That is, it is sufficient that the smart device 200 includes at least a means for accessing the recording medium 210.

The communication unit 211 is an interface for connecting to an external device. The communication unit 211 in the present embodiment includes an interface for performing communication using a so-called wireless LAN compliant with the IEEE802.11 standard. The smart device 200 according to the present embodiment can exchange data with the digital camera 100 via the communication unit 211. In the present embodiment, the communication unit 211 is an antenna, and the control unit 101 can be connected to the digital camera 100 via the antenna. Note that the connection with the digital camera 100 may be established directly or may be established via an access point. Examples of protocols for communicating data include HTTP (hypertext transfer protocol). In addition, PTP/IP (picture transfer protocol via internet protocol) by wireless LAN can also be used. Note that communication with the digital camera 100 is not limited to this. For example, the communication unit 211 may include a wireless communication module such as an infrared communication module, a bluetooth (registered trademark) communication module, or a wireless USB. Further, a wired connection such as a USB cable, HDMI, IEEE 1394, or ethernet may also be used.

the short-range wireless communication unit 212 is a communication unit for realizing noncontact short-range communication with other devices. The short-range wireless communication unit 212 is constituted by an antenna for wireless communication, and a modulation and demodulation circuit and a communication controller for processing wireless signals. The short-range wireless communication unit 212 realizes noncontact short-range communication by outputting a modulated wireless signal from an antenna and demodulating a wireless signal received via the antenna. Here, contactless communication compliant with the ISO/IEC18092 standard (so-called NFC) is realized. Upon receiving a data read request from another device, the short-range wireless communication unit 212 outputs response data based on the data stored in the nonvolatile memory 203.

The public network communication unit 213 is an interface for public wireless communication. The smart device 200 can talk with other devices via the public network communication unit 213. At this time, the control unit 201 realizes a call by inputting/outputting an audio signal via the microphone 214 and the speaker 215. In the present embodiment, the public network communication unit 213 is an antenna, and the control unit 101 may be connected to the public network via the antenna. Note that one antenna may be used for both the communication unit 211 and the public network communication unit 213. The smart device 200 according to the present embodiment is explained above.

< Structure of API for controlling digital Camera from external device >

Fig. 3A and 3B are diagrams showing an API (application programming interface) for controlling the digital camera 100 (server) from an external device. In the case where the digital camera 100 according to the present embodiment functions in the above-described AP mode, an API is used.

The digital camera 100 presents an API that can be controlled from an external device such as the smart device 200. Through these APIs, the digital camera 100 of the present embodiment provides the device information recorded in the nonvolatile memory 103 of the digital camera 100 and the content file stored in the recording medium 110 of the digital camera 100 to the external device. The content file is a file generated by the digital camera 100 and then stored in the recording medium 110 or the nonvolatile memory 103, and refers to a still image file or a moving image file of an image that has been photographed in the present embodiment.

the API is stored in advance in the nonvolatile memory 103. When establishing communication with an external device (the smart device 200 in the present embodiment) via the communication unit 111, the control unit 101 loads a program for executing the API to the work memory 104 and waits for a request for the API from an external apparatus. In the case where the control unit 101 detects that the API has been requested from the external apparatus, the digital camera 100 performs processing according to the type of the API, and returns the processing result to the external apparatus as a response. Note that the API is executed according to a communication protocol specified by the digital camera 100, and the external device communicates with the digital camera 100 using the specified communication protocol to request the API. In the description of the present embodiment, it is assumed that the API is executed according to HTTP (hypertext transfer protocol). That is, the digital camera 101 functions as an HTTP server, and the smart device 200 functions as an HTTP client. Note that the communication protocol is not limited to HTTP, and may be other protocols. The protocol itself, which is the HTTP protocol, is widely used, and therefore, the description thereof is omitted here. The method for executing the API according to HTTP is implemented as follows: the external device describes the API name and required arguments in the HTTP request body in text, and transmits the HTTP request body to the digital camera 100 using a GET method or a POST method. Then, the digital camera 100 adds the execution result of the API to the HTTP response body, and returns the HTTP response body to the external apparatus.

the API list 300 shown in fig. 3A and 3B is obtained by tabulating the API set provided by the digital camera 100 of the present embodiment operating in the above-described setting. Each API will be explained below.

The API 301 is an API for acquiring product information of the digital camera 100. If a request for the API name "RequestProductInfo" is received without any argument, the digital camera 100 composes a response from the product name, manufacturer name, firmware version, and serial number of the digital camera 100 stored in the nonvolatile memory 103. Then, the digital camera 100 transmits the composed information to the request originator external apparatus. Note that the product name is a product name of the digital camera 100. The manufacturer name is the manufacturer name of the digital camera 100. The firmware version is a version number of a program stored in the nonvolatile memory 103 for controlling the digital camera 100. The serial number is a unique number that can be used to individually identify the digital camera 100.

The API 302 is an API for acquiring information about a storage area of the digital camera 100. If a request for the API name "RequestMemoryInfo" is received without any argument, the digital camera 100 composes a response from the storage area ID, the available storage capacity, the free space, and the number of storage content files of the digital camera 100. Then, the digital camera 100 transmits the composed response to the request originator external device. Note that the storage area ID is an ID (identification) assigned to each area where a content file generated by the digital camera 100 can be stored. For example, a storage area ID is assigned to the recording medium 110 of the digital camera 100. The available storage capacity is an upper limit size of a storage area in which the content file can be stored. The free space is the size of a space in the storage area where no content file is stored. The stored content number is the total number of content files stored in the storage area.

the API 303 is an API for acquiring a content ID stored in a storage area of the digital camera 100 and basic information related to a content file. If the storage area ID, the type of content format, and the number of acquisition requests acquired by the API 302 are received as arguments together with a request for the API name "RequestContentInfo", the digital camera 100 acquires the content ID, the file name, the file size, the file generation date and time of the content file stored in the storage area of the digital camera 100, and transmits the acquired information to the request initiator external device. Note that the content ID is an ID assigned to individually identify content files. With the API in the present embodiment, an upper limit is set for information on a content file that can be acquired at one time, according to the size of the work memory 104. Therefore, in the case where the number of content files stored in the recording medium 110 or the like exceeds the upper limit of the API for the present embodiment, it is necessary to repeatedly request the API.

The API 304 is an API for acquiring a content file stored in a storage area of the digital camera 100. If the content ID and the content size are received as arguments together with a request for the API name "requestcontent", the digital camera 100 transmits a corresponding content file to the request originator external device. Note that, as for the content size, it is possible to select whether the content file is acquired in the original size or in the reduced size. The digital camera 100 generates a content file according to the designated size and transmits the content file to the external device as a response. In the present embodiment, for example, it can be specified whether the still image file is acquired in the original size or in the thumbnail size. Therefore, instead of numerical values, a character string for identifying the original size or the thumbnail size may also be used as the size.

The API305 is an API for acquiring change information on the state of the digital camera 100. If a request for the API name "requestcamera event" is received without any argument, the digital camera 100 acquires some or all of the information that the API 801 can acquire. Note that the digital camera 100 does not immediately return a response to the request for the API 305. The digital camera 100 waits until the state of the digital camera 100 partially changes, and upon detecting the change, the digital camera 100 returns only change information as a response. For example, in the present embodiment, the API305 is an API for acquiring battery information.

The API 306 is an API for acquiring an ID of a content file transmitted by the digital camera 100 to a request initiator external device. If a request for the API name "RequestContentList" is received without any argument, the digital camera 100 transmits a list of corresponding content files to the request originator external device. Note that the digital camera 100 does not immediately return a response to the request for the API 306. The digital camera 100 returns a response when the user selects an image to be transmitted to the request originator external device from among the content files stored in the storage area of the digital camera 100.

The API 307 is an API for causing the digital camera 100 to interrupt transmission of a content file to a request initiator external device. If a request for the API name "cancelerequestcontent" is received without any argument, the digital camera 100 interrupts transmission of a content file being transmitted from the digital camera 100 to the request originator external apparatus according to the API 304 "requestcontent". Note that the digital camera 100 interrupts not only the transmission of a content file currently being forwarded, but also the transmission of any content file that is subsequently scheduled to be transmitted to the request originator external apparatus. Note that the digital camera 100 does not display a UI for instructing cancellation of content file forwarding on the display unit 106 until the API 307 has been received. In addition, the digital camera 100 does not immediately return a response to the request for the API 307. The digital camera 100 returns a response to the external apparatus when the digital camera 100 detects that the user has performed the cancel instruction operation.

The API 308 is an API for causing the digital camera 100 to interrupt transmission of a content file to a request originator external device or to acquire change information. If a request for the API name "canceeventndcancel" is received without any argument, the digital camera 100 performs the processing of the API305 or the API 307 described above. This API is a common API for API305 and API 307 and may be used for both applications.

The API in the present embodiment is described above. The above API is an example of a main API, and various APIs for a control method of the digital camera 100 other than the above API may also be provided. Further, it is assumed that, when transmitting a response to each API request described above, the digital camera 100 specifies the requested request and transmits a return value (if any) for the request to the request originator. The response format is defined as "response (API request name, return value)". For example, in a case where the digital camera 100 receives a RequestProductInfo request from an external apparatus and responds to the request, the response to the request originator will be "response (RequestProductInfo, return value)". Note that it may be sufficient to notify the request originator as to which API the response corresponds, and the present invention is not limited by the above-described examples.

In all the embodiments described later, the smart device 200 and the digital camera 100 constitute an image processing system via a network (wireless LAN in the embodiment). Note that it is assumed that the control unit 101 of the digital camera 100 has transitioned to the simple AP mode (the file server mode using the HTTP protocol in the initial state) using the operation unit 105. The content file in all embodiments will be described by taking an image file as an example. For example, in the description of the embodiment, "the smart device 200 transmits the API 301" RequestProductInfo "to the digital camera 100" and "the smart device 200 requests the RequestProductInfo 301 from the digital camera" will be denoted for the sake of simplicity.

< sequence of interrupting image transfer from digital camera to Intelligent device >

A procedure for interrupting image forwarding of a content file from the digital camera 100 to the smart device 200 in the above-described image processing system at any timing set by the digital camera 100 will be described below with reference to fig. 4 to 7.

Fig. 4 shows an example of a communication sequence between the smart device 200 and the digital camera 100. In particular, the sequence is a process up to and including the following operations: the smart device 200 acquires a list of content files to be received from the digital camera 100, then requests transmission of an image from the smart device 200 to the digital camera 100 based on the list of content files, and the digital camera 100 transmits the content files to the smart device 200. Fig. 5A to 5C are diagrams showing a User Interface (UI) displayed on the display unit 106 by a program running on the digital camera 100.

In step S401, the digital camera 100 and the smart device 200 establish a wireless Local Area Network (LAN) connection. Here, a process performed in a case where the digital camera 100 starts a simple AP and establishes a connection in response to a user operation will be described.

After generating an SSID (service set identifier) and an encryption key required to establish a wireless LAN connection, the control unit 101 of the digital camera 100 starts a simple AP using the SSID and the encryption key and generates a wireless LAN network. At this time, the digital camera 100 displays information such as an SSID and an encryption key for connecting to a simple AP provided by the digital camera 100 on the display unit 106. Note that the SSID is an identifier of an access point in an IEEE802.11 series wireless LAN, and is a name provided to prevent interference. The encryption key is a key for encrypting the wireless LAN to prevent unauthorized access to the SSID. Note that the user can appropriately edit the SSID and encryption key and the like displayed here, and display the information in the case where the previously used information has not been changed or edited. Next, the control unit 101 starts a DHCP (dynamic host configuration protocol) server and prepares so that an IP address can be assigned to a device that has joined the network generated by the simple AP.

on the other hand, when the process for connecting to the wireless LAN network is started according to the user operation, the control unit 201 of the smart device 200 performs a process for searching for a peripheral AP, as a result of which the obtained list of SSIDs is displayed on the display unit 206. The user operates the operation unit 205 to select an SSID that matches the SSID of the simple AP displayed on the display unit 106 of the digital camera 100 from the SSID list displayed on the display unit 206. Then, the user inputs the same key (character string) as the encryption key displayed on the display unit 106 of the digital camera 100 using the operation unit 205. As a result, the control unit 201 of the smart device 200 starts joining the simple AP network generated by the digital camera 100. Note that the smart device 200 may store the SSID to which it was previously connected and the corresponding encryption key, and if the SSID selected by the user is included in the stored SSIDs, the smart device 200 may display the encryption key stored in association with the SSID as a default value in the encryption key input field so that the user only has to press (or touch) the OK button. As a result of the above, an IP address is assigned from the digital camera 100 to the smart device 200, and the connection to the wireless LAN is completed. Although an example in which the digital camera 100 also functions as a DHCP server is explained here, it is conceivable to adopt a structure as follows: the digital camera 100 and the smart device 200 are each connected to a local area network constructed by a router.

In step S402, the smart device 200 performs discovery processing. Then, the digital camera 100 and the smart device 200 recognize the presence of each other and the provided service. In addition, the smart device 200 makes preparations to communicate using the API provided by the digital camera 100 via the wireless LAN. Note that examples of protocols for discovery include SSDP (single service discovery protocol) and multicast DNS. SSDP and multicast DNS are known protocols, and therefore, description thereof is omitted.

An example of the discovery process will be explained. The control unit 101 of the digital camera 100 transmits an advertisement notification to the network generated by the digital camera 100 itself and notifies the smart device 200 of its presence. Upon receiving the advertisement notification from the digital camera 100, the control unit 201 of the smart device 200 acquires the discovery description describing the device information of the digital camera 100 from the digital camera 100 and determines whether the digital camera 100 provides the API service. If it is determined that the digital camera 100 provides the API service, the control unit 201 loads a program for acquiring an image file from the digital camera 100 by using the API from the nonvolatile memory 203 to the work memory 204, and executes the program.

In step S403, the control unit 201 requests the RequestProductInfo 301 from the digital camera 100 via the communication unit 211. In step S404, upon detecting that the request has been received via the communication unit 111, the control unit 101 acquires the product name, the manufacturer name, the firmware version, and the serial number from the nonvolatile memory 103, and forms a response data set according to the acquired information. Then, the control unit 101 transmits the formed data set to the smart device 200 via the communication unit 111.

In step S405, the control unit 201 requests the RequestMemoryInfo 302 from the digital camera 100 via the communication unit 211. In step S406, upon detecting that the request has been received via the communication unit 111, the control unit 101 acquires the storage area ID, the available storage capacity, the free space, and the number of stored contents from the work memory 104 or the recording medium 110, and forms a response data set according to the acquired information. Then, the control unit 101 transmits the formed data set to the smart device 200 via the communication unit 111.

In step S407, the control unit 201 requests the RequestContentList 306 from the digital camera 100 via the communication unit 211. Upon detecting that the request has been received via the communication unit 111, the control unit 101 of the digital camera 100 optionally displays a thumbnail list of images recorded in the recording medium 110 as shown in fig. 5A on the display unit 106 of the digital camera 100 in step S408. Then, the control unit 100 prompts the user for a selection to determine an image to be forwarded to the smart device 200.

In step S409, when the user selects an image to be forwarded on the display unit 106 of the digital camera 100 using the selection button 502 and touches the OK button 503, the control unit 101 displays the forward forwarding image on the display unit 106 as shown in fig. 5B. At this time, the control unit 101 stores the ID list of the selected image in the work memory 104. Thereafter, in step S410, the control unit 101 acquires the ID list of the transmission images selected by the user from the work memory 104, and forms a response data set from the list. Then, the control unit 101 transmits the formed data set to the smart device 200 via the communication unit 111.

As a result, the control unit 201 of the smart device 200 can acquire information for specifying the image selected by the user.

In step S411, the control unit 201 requests the cancel requestcontent 307 from the digital camera 100 via the communication unit 211. This is done in order to enable a transmission interruption operation from the digital camera side. Upon detecting that the request has been received via the communication unit 111, the control unit 101 of the digital camera 100 additionally displays a cancel button 504 on the display unit 106 of the digital camera 100, as shown in fig. 5C. The control unit 201 does not immediately return a response to the request and places the response in a delayed state. By intentionally placing the request in the delay state, the digital camera 100 can transmit data to the smart device 200 at any timing. In the present embodiment, the digital camera 100 returns a response at the timing when the cancel button 504 is pressed in accordance with the user operation. Sending data from the server side to the client at any timing in this manner is referred to as "server push", and a technique for implementing server push by creating an intentional response delay state is referred to as "long polling".

in step S412, the control unit 201 requests the Request Content 304 from the digital camera 100 via the communication unit 211. In step S413, upon detecting that the request has been received via the communication unit 111, the control unit 101 acquires a content file (image file selected by the user) corresponding to the specified content ID from the work memory 104 or the recording medium 110, and forms a response data set from the content file. Then, the control unit 101 transmits the formed data set to the smart device 200 via the communication unit 111.

Thereafter, from steps S414 and S415, the same processing as that in steps S412 and S413 is repeated. That is, in general, the process is repeated until the forwarding of all images selected by the user from the digital camera 100 to the smart device is completed. A case will be described in which the user cancels forwarding for some reason during this time.

Now, assume that in step S416 in which an image is being forwarded, the user has pressed the cancel button 504 shown in fig. 5C by operating the operation unit 105. In this case, in step S417, the control unit 101 transmits the response data for step S411 to the smart device 200 via the communication unit 111.

In step S418, upon detecting an instruction to end the program according to the user instruction, the control unit 201 ends communication with the digital camera 100 in step S419. That is, if the end instruction is detected, the control unit 201 ends the communication regardless of whether the reception of all the images initially selected by the user is completed.

In step S420, the process for disconnecting the communication between the digital camera 100 and the smart device 200 is completed.

the above is an example of a method for interrupting acquisition of a content file from the digital camera 100 when the smart device 200 is connected to the digital camera 100 and acquires the content file.

< details of processing performed in the digital camera 100 >

The flow of processing performed in the digital camera 100 will be described. Fig. 6A and 6B show a flowchart of the processing flow of the API service performed in the digital camera 100.

In step S601, the control unit 101 establishes a wireless Local Area Network (LAN) connection between the digital camera 100 and the smart device 200. This processing is the same as the processing performed in the digital camera 100 described in relation to step S401, and therefore, the description thereof is omitted.

in step S602, the control unit 101 discovers that the digital camera 100 and the smart device 200 recognize each other' S presence and a provided service, and the control unit 101 prepares to communicate using an API provided by the digital camera 100 via the wireless LAN. This processing is the same as the processing performed in the digital camera 100 described in relation to step S402, and therefore the description thereof is omitted.

In step S603, the control unit 101 detects whether an API RequestContentList request has been received via the communication unit 111. If the request is detected, the process advances to step S604. Otherwise, the process is repeated.

In step S604, the control unit 101 displays a UI representing the image information list illustrated in fig. 5A, and accepts an image selection operation by the user. Then, if the selection ends (the OK button in fig. 5A has been pressed), the control unit 101 generates an information list (or an image list) including an ID for specifying the selected image via the communication unit 111, and transmits the information list as a response to the API RequestContentList.

In step S605, the control unit 101 displays a UI representing the progress status of forwarding shown in fig. 5B on the display unit 106.

In step S606, the control unit 101 initializes a FLAG (indicating an unreceived value) for determining whether or not a cancel request has been received. Note that the flag is ensured at a predetermined address of the working memory 104.

In step S607, the control unit 101 detects whether an API RequestContent request has been received via the communication unit 111. If the request has been received, the control unit 101 proceeds to step S608. Otherwise, the control unit 101 advances the process to step S609.

In step S608, the control unit 101 transmits a response to the API Request Content via the communication unit 111. The response is transmission of image data indicated by the ID described in the RequestContent request. When the response processing ends, the control unit 101 returns the processing to step S607.

On the other hand, if the process advances to step S609, the control unit 101 determines whether an API cancel request content request has been received via the communication unit 111. If the request has been received, the control unit 101 advances the process to step S610. Otherwise, the control unit 101 advances the process to step S612.

In step S610, since the API cancel request content request has been received, the control unit 101 sets the FLAG to "1". Then, in step S611, the control unit 101 displays the cancel button 504 illustrated in fig. 5C on the display unit 106. After that, the control unit 101 returns the process to step S607.

In step S612, the control unit 101 determines whether the FLAG is "1". In other words, it can also be said that the control unit 101 determines whether or not a cancel request has been received or whether or not the cancel button 504 has been displayed in the UI. If the FLAG is "1", the control unit 101 advances the process to step S613. If the FLAG is "0", the control unit 101 returns the process to step S607.

In step S613, the control unit 101 determines whether the user presses the cancel button 504 by operating the operation unit 105. If the cancel button 504 has been pressed, the control unit 101 advances the process to step S614, and if the cancel button 504 has not been pressed, the control unit 101 returns the process to step S607.

In step S614, the control unit 101 transmits a response to the API CancelRequestContent via the communication unit 111. That is, the control unit 101 notifies the smart device 200 that the user has performed an operation to cancel image forwarding. Thereafter, the control unit 101 receives an instruction to end the connection from the smart device 200, and ends the processing.

< details of processing performed in the smart device 200 >

Next, a flow of processing performed in the smart device 200 when acquiring status information on the digital camera 100 in a case where a content list display or a content file obtained by remote shooting is acquired will be described.

Fig. 7 is a flowchart showing a processing flow of the application executed in the smart device 200.

in step S701, the control unit 201 establishes a wireless Local Area Network (LAN) connection between the digital camera 100 and the smart device 200. This process is the same as the process performed in the smart device 200 described in connection with step S401, and therefore, the description thereof is omitted.

in step S702, the control unit 201 discovers that the digital camera 100 and the smart device 200 recognize each other' S presence and a provided service, and the control unit 201 prepares to communicate using an API provided by the digital camera 100 via the wireless LAN. This process is the same as the process performed in the smart device 200 described in connection with step S402, and therefore, the description thereof is omitted.

in step S703, the control unit 201 transmits RequestProductInfo to the digital camera 100. This processing is the same as the processing described with respect to step S403, and therefore, the description thereof is omitted.

In step S704, the control unit 201 transmits RequestMemoryInfo to the digital camera 100. This processing is the same as the processing described in relation to step S405, and therefore the description thereof is omitted.

In step S705, the control unit 201 transmits the RequestContentList to the digital camera 100. This processing is the same as the processing described in relation to step S407, and therefore the description thereof is omitted.

In step S706, the control unit 201 determines whether a response to the RequestContentList (information list describing the ID of the image to be forwarded) has been received via the communication unit 211. The control unit 201 advances the process to step S707 if the response has been received, otherwise the control unit 201 waits until the response is received.

In step S707, the control unit 201 transmits the CancelRequestContent to the digital camera 100 via the communication unit 211. This processing is the same as that described with respect to step S411, and therefore, description thereof is omitted.

In step S708, the control unit 201 transmits RequestContent to the digital camera 100. That is, the control unit 201 requests the digital camera 100 for a transmission request for one of the images selected by the user. This processing is the processing described in relation to step S412.

In step S709, the control unit 201 determines whether a response to the API CancelRequestContent has been received via the communication unit 211. The control unit 201 interrupts the image reception process if a response to the CancelRequestContent has been received, and ends the process by sending an instruction to end the connection to the digital camera 100. If it is determined that the cancel requestcontent response has not been received, the control unit 201 advances the process to S710.

in step S710, the control unit 201 determines whether an API RequestContent response (image data) has been received via the communication unit 211. If the Request Content response has been received, the control unit 201 determines in step S711 whether the reception of all images has ended. If not, the control unit 201 returns the process to step S708 to receive the next image from the digital camera 100 in order to acquire the next image. On the other hand, if the reception of the attention image data is not completed, the control unit 201 returns the process to step S709 to determine whether the user has performed the cancel process.

As explained above, according to the present embodiment, in the case where the user forwards the captured image stored and held in the digital camera to the smart device, the forwarding can be interrupted via the operation unit on the digital camera side.

In the above first embodiment, an example in which forwarding of an image is canceled by operating the digital camera 100 during image forwarding is explained. The API cancelled requestcontent for canceling image forwarding can also be used for status notification of the digital camera 100 in the same manner.

Therefore, in the second embodiment, an example will be explained in which image forwarding is canceled using a dedicated API CancelRequestContent, and a status notification relating to a digital camera is made using another API RequestCameraEvent.

In the third embodiment, the following example will be explained: the API requesteventndcancel common to cancellation of image forwarding and status notification of the digital camera is used.

[ second embodiment ]

< sequence of cases where image forwarding API and camera status notification API are used separately >

Fig. 8A and 8B show an example of a communication sequence including a case where cancellation of image forwarding between the smart device 200 and the digital camera 100 is not performed according to the second embodiment. Specifically, this is an example of canceling image forwarding using the dedicated API 307, and making a status notification relating to the digital camera 100 using another API 305.

The processing in steps S801 and S802 is the same as the processing in steps S401 and S402 shown in fig. 4 described in the first embodiment, and therefore the description thereof is omitted.

In step S803, the control unit 201 requests the RequestCameraEvent 305 from the digital camera 100 via the communication unit 211. Even if the request has been received via the communication unit 111, the control unit 101 of the digital camera 100 does not immediately return a response. If the request has been received, the control unit 101 starts monitoring for a change in the state of the camera 100 (state change), and returns a response to the requestcamera event 305 only after there is a change in the state. In the second embodiment, an example when notification relating to the battery state is performed is explained. Of course, any other parameter may be used besides the battery state as long as the parameter indicates the internal state of the camera.

The processing of steps S804 to S818 is the same as the processing of steps S414 and S415 shown in fig. 4 described in the first embodiment, and therefore, the description thereof is omitted.

In step S819, the battery state has changed. In step S820, upon detecting that the battery state of the digital camera 100 has changed, the control unit 101 forms a response data set from the battery information with respect to the requestcamera event 305 requested in step S803, and transmits the response data set to the smart device 200 via the communication unit 111.

In step S821, the control unit 201 requests the RequestCameraEvent 305 from the digital camera 100 via the communication unit 211. Performing step S821 enables the state notification of the digital camera 100 to be provided to the smart device 200 again.

In step S822, the control unit 101 transmits a response to the CancelRequestContent 307 to the digital camera 100 via the communication unit 111. The reason for this is as follows: the image transfer started in step S813 is not canceled, and therefore, in the case where the image transfer processing is normally completed, a response is always returned to the CancelRequestContent 307, thereby preventing resource consumption.

The processing in steps S823 to S837 is the same as the processing in steps S401 to S420 shown in fig. 4 described in the first embodiment, and therefore, the description thereof is omitted.

< details of processing performed in the digital camera 100 >

The flow of processing performed in the digital camera 100 will be described. Fig. 9A and 9B are flowcharts showing the flow of processing of the API service performed in the digital camera 100. The following description will be made with reference to fig. 9A and 9B.

The processing in steps S901 and S902 is the same as the processing in steps S601 and S602 shown in fig. 6A described in the first embodiment, and therefore, the description thereof is omitted.

In step S903, the control unit 101 clears FLAGs FLAG _ E and FLAG _ C that have been secured in advance in the work memory 104. FLAG _ E is a FLAG for determining whether a RequestCameraEvent request has been received, and FLAG _ C is a FLAG for determining whether a cancel requestcontent request has been received. The processing in step S903 is performed to mark these two requests as not yet received.

In step S904, the control unit 101 determines whether any request has been received from the smart device 200 via the communication unit 111. If a request has been received, the control unit determines the type of the received request and performs processing corresponding to each type in subsequent steps S905 to S908. On the other hand, if it is determined that the request has not been received, the control unit 101 advances the process to step S921.

If the received request is a RequestContentList request, the control unit 101 advances the process from step S905 to S909. Then, in step S909, the control unit 101 transmits a response to the RequestContentList. The transmission is the same as step S604 in the first embodiment. Then, in step S910, the control unit 101 starts displaying an image transfer screen. In addition, the process is the same as step S605 in the first embodiment. After that, the control unit 101 returns the process to step S904.

If the received request is a RequestCameraEvent request, the control unit 101 advances the process from step S906 to step S911. In step S911, control unit 101 sets FLAG _ E to "1" in order to indicate that a RequestCameraEvent request has been received. Then, the control unit 101 returns the process to step S904.

If the received request is a CancelRequestContent request, the control unit 101 advances the process from step S907 to step S912. In step S912, the control unit 101 sets a FLAG _ C to "1" in order to indicate that a cancel requestcontent request has been received. Then, in step S913, the control unit 101 displays the cancel button 504 on the display screen. After that, the control unit 101 returns the process to step S904.

In the present embodiment, it is assumed that the forwarding screen has been displayed before the cancel requestcontent request is received; however, if a RequestContentList request is received after the cancel requestcontent request is received, the control unit 101 displays a forwarding screen including the cancel button 504 in step S910.

If the received request is a RequestContent request, the control unit 101 advances the process from step S908 to step S914. In step S914, the control unit 101 transmits a response to the RequestContent request. The transmission processing is the same as step S608 in the first embodiment. After that, the control unit 101 returns the process to step S904.

If the received request is a request other than the above, the control unit 101 advances the process from step S908 to step S915, and performs a process corresponding to the received request. Then, the control unit 101 returns the process to step S904.

in step S904, if it is determined that the request has not been received, the control unit 101 advances the process to step S921. In step S921, the control unit 101 determines whether the FLAG _ E is "1", or in other words, whether a RequestCameraEvent request has been received. If FLAG is 0 (not received), the control unit 101 skips the processing in steps S922 and S923, and advances the processing to step S924. If the FLAG _ E is "1" (received), the control unit 101 determines in step S922 whether there is a change in the battery state or the like of the digital camera 100. If there is no change, the control unit 101 advances the process to step S924. If there is a change, the control unit 101 creates a response message describing the details of the change and transmits the response message as a response to the requestcamera event request in step S923. Then, the control unit 101 advances the process to step S924.

In step S924, the control unit 101 determines whether the FLAG _ C is "1", or in other words, whether a cancel request content request has been received. If FLAG _ C is 0 (not received), control unit 101 returns the process to step S904. If FLAG _ C is 1 (received), control unit 101 advances the process to step S925. In step S925, the control unit 101 determines whether the cancel button 504 has been pressed. If the cancel button 504 has not been pressed, the control unit 101 returns the process to step S904. If it is determined that the cancel button 504 has been pressed, the control unit 101 advances the process to step S926. In step S926, the control unit 101 generates a response message to the CancelRequestContent request, and transmits the response message. The processing in step S926 is the same as step S614 in the first embodiment.

< details of processing performed in the smart device 200 >

Next, the flow of processing performed in the smart device 200 will be described with reference to the flowcharts shown in fig. 10A and 10B.

the processing in steps S1001 to S1004 is the same as the processing in steps S701 to S704 shown in fig. 7 described in the first embodiment, and therefore, the description thereof is omitted.

In step S1005, the control unit 201 transmits a request for the RequestCameraEvent 305 to the digital camera 100. The processing steps S1006 to S1010 are the same as those in steps S701 to S709 shown in fig. 7 described in the first embodiment, and therefore, the description thereof is omitted.

In step S1011, the control unit 201 determines whether a response to the API RequestCameraEvent has been received via the communication unit 211. If a response has been received, the control unit 201 interrupts the image reception processing, and ends the processing by sending an instruction to end the connection to the digital camera 100. If it is determined that a response to the cancel requestcontent has not been received, the control unit 201 advances the process to step S1011.

In step S1011, the control unit 201 determines whether a response to the RequestCameraEvent 305 is received. If a response to the RequestCameraEvent 305 has not been received, the control unit 201 advances the process to step S1013. If a response to the RequestCameraEvent 305 has been received, in step S1012, the control unit 201 performs processing corresponding to the state of the digital camera, and transmits a request for the RequestCameraEvent 305 to the digital camera 100 again to receive a notification in the event that there is a change in state later.

Step S1013 is the same as the processing in step S710 shown in fig. 7 described in the first embodiment, and thus the description thereof is omitted.

In step S1014, the control unit 201 determines whether all the images in the RequestContentList received in step S1007 have been received. If all the images have not been received, the control unit 201 returns the process to step S1009 to receive the next image. On the other hand, if the reception of all the images is completed, the control unit 201 ends the communication to end the processing.

[ third embodiment ]

< sequence of cases where image forwarding API and camera status notification API are used separately >

Fig. 11A and 11B show an example of a communication sequence including a case where cancellation of image forwarding between the smart device 200 and the digital camera 100 is not performed according to the third embodiment. Specifically, this is an example as follows: the API requesteventndcancel 308 common to cancellation of image forwarding and status notification of the digital camera 100 is used.

The processing in steps S1101 and S1102 is the same as the processing in steps S401 and S402 shown in fig. 4 described in the first embodiment, and therefore the description thereof is omitted.

In step S1103, the control unit 201 requests the requestcamera eventadcencel 308 from the digital camera 100 via the communication unit 211. Even if it is determined that the request has been received via the communication unit 111, the control unit 101 of the digital camera 100 does not immediately return a response. The control unit 101 returns a response in image transfer cancellation processing performed subsequently or when the state of the camera changes.

The processing in steps S1104 to S1117 is the same as the processing in steps S804 to S811 and steps S813 to S818 shown in fig. 8A and 8B described in the second embodiment, and therefore the description thereof is omitted.

It is assumed that the battery state is changed in step S1118. In this case, in step S1119, the control unit 101 detects that the battery state of the digital camera 100 has changed, then forms a response data set from the battery information for the requesteventndcancel 308 requested in step S1103, and transmits the response data to the smart device 200 via the communication unit 111.

In step S1120, in order to enable the response to be received again, the control unit 201 requests the requesteventndcancel 308 from the digital camera 100 via the communication unit 211. Performing step S1120 enables the state notification of the digital camera 100 to be provided to the smart device 200 again, and also enables the image forwarding to be cancelled.

The processing in steps S1121 to S1128 is the same as the processing in steps S823 to S826 and steps S828 to S831 shown in fig. 8A and 8B described in the second embodiment, and therefore the description thereof is omitted.

In step S1129, upon detecting that the battery state of the digital camera 100 has changed, the control unit 101 forms a response data set from the battery information for the requesteventndcancel 308 requested in step S1120, and transmits the response data set to the smart device 200 via the communication unit 111.

The processing in steps S1132 to S1135 is the same as the processing in steps S834 to S837 shown in fig. 8A and 8B described in the second embodiment, and therefore, the description thereof is omitted.

< details of processing performed in the digital camera 100 >

The flow of processing performed in the digital camera 100 will be described. Fig. 12A and 12B are flowcharts showing the flow of processing of the API service performed in the digital camera 100. The following description will be made with reference to fig. 12A and 12B.

The processing in steps S1201 and S1202 is the same as the processing in steps S601 and S602 shown in fig. 6A described in the first embodiment, and therefore, the description thereof is omitted.

In step S1203, the control unit 101 clears a FLAG that has been secured in advance in the work memory 104. FLAG is used to determine whether a requesteventndcancel request has been received. The processing in step S1203 is performed to mark the requesteventndcancel request as not yet received.

In step S1204, the control unit 101 determines whether any request has been received from the smart device 200 via the communication unit 111. If a request has been received, the control unit determines the type of the received request and performs processing corresponding to each type in subsequent steps S1205, S1206, and S1208. On the other hand, if it is determined that the request has not been received, the control unit 101 advances the process to step S1221.

If the received request is a RequestContentList request, the control unit 101 advances the process from step S1205 to S1209. Then, in step S1209, the control unit 101 transmits a response to the RequestContentList. The transmission is the same as the transmission in step S604 in the first embodiment. Then, in step S1210, the control unit 101 starts displaying an image transfer screen. In addition, the process is the same as step S605 in the first embodiment. After that, the control unit 101 returns the process to step S1204.

If the received request is a requesteventndcancel request, the control unit 101 advances the process from step S1206 to step S1211. In step S1211, to indicate that a requesteventndcancel request has been received, the control unit 101 sets a FLAG to "1". Then, in step S1212, the control unit 101 determines whether or not to display an image transfer screen. If the image transfer screen is not displayed, the control unit 101 returns the process to step S1204. If the image forwarding screen is displayed, the control unit 101 displays the cancel button 504 in step S1213. After that, the control unit 101 returns the process to step S1204.

Note that in the present embodiment, if a cancel requestcontent request has been received after a requesteventndcancel request is received, the flag is set to "1", and the control unit 101 displays a forwarding screen including the cancel button 504.

if the received request is a RequestContent request, the control unit 101 advances the process from step S1208 to step S1214. In step S1214, the control unit 101 transmits a response to the RequestContent request. The transmission processing is the same as step S608 in the first embodiment. After that, the control unit 101 returns the process to step S1204.

If the received request is a request other than the above, the control unit 101 proceeds from step S1208 to step S1215, and performs processing corresponding to the received request. Then, the control unit 101 returns the process to step S1204.

In step S1204, if it is determined that the request has not been received, the control unit 101 advances the process to step S1221. In step S1221, the control unit 101 determines whether the FLAG is "1", or in other words, whether a requesteventndcancel request has been received. If FLAG is 0 (not received), control unit 101 returns the process to step S1204.

If the FLAG is "1" (received), the control unit 101 determines in step S1222 whether there is a change in the battery state or the like of the digital camera 100. If there is no change, the control unit 101 advances the process to step S1224. If there is a change, the control unit 101 creates a response message describing the details of the change and transmits the response message as a response to the requesteventndcancel request in step S1223. Then, the control unit 101 returns the process to step S1204.

in step S1224, the control unit 101 determines whether the cancel button 504 has been pressed. If the cancel button 504 has not been pressed, the control unit 101 returns the process to step S1204. If it is determined that the cancel button 504 has been pressed, the control unit 101 advances the process to step S1225. In step S1225, the control unit 101 creates a message indicating that the cancel button 504 has been pressed, and transmits the message as a response to the cancel requestcontent request. Then, the control unit 101 returns the process to step S1204.

< details of processing performed in the smart device 200 >

Next, the flow of processing performed in the smart device 200 will be described with reference to the flowcharts shown in fig. 13A and 13B.

The processing in steps S1301 to S1304 is the same as the processing in steps S701 to S704 shown in fig. 7 described in the first embodiment, and therefore, the description thereof is omitted.

In step S1305, the control unit 201 transmits a request for the requesteventndcancel 308 to the digital camera 100. The processing in steps S1306 to S1308 is the same as the processing in steps S701 to S709 shown in fig. 7 described in the first embodiment, and therefore, the description thereof is omitted.

in step S1309, the control unit 201 determines whether a response to the API requesteventndcancel request has been received via the communication unit 211. The control unit 201 advances the process to step S1310 if a response to the requesteventndcancel request has been received, and otherwise, the control unit 201 advances the process to step S1313.

In step S1310, the control unit 201 analyzes the received response to the requesteventndcancel request, and determines whether the response is a response notifying a change in the state of the digital camera or a response indicating that cancellation of image forwarding has been instructed. Then, if the response indicates that cancellation of image forwarding has been instructed, the control unit 201 ends the communication process.

on the other hand, if the response indicates a change in state, in step S1311, the control unit 201 performs processing corresponding to the state of the digital camera 100, and again transmits a request for requesteventndcancel 308 to the digital camera 100 to receive a notification if there is a change in state later. Then, the control unit 201 advances the process to step S1313.

Step S1313 is the same as the processing in step S710 shown in fig. 7 described in the first embodiment, and therefore description thereof is omitted.

In step S1314, the control unit 201 determines whether all the images in the RequestContentList received in step S1307 have been received. If all the images have not been received, the control unit 201 returns the process to step S1308 to receive the next image. On the other hand, if the reception of all the images is completed, the control unit 201 ends the communication to end the processing.

OTHER EMBODIMENTS

aspects of the present invention can also be achieved by a process in which a program for realizing one or more functions in the above-described exemplary embodiments is supplied to a system or an apparatus via a network or a storage medium, and the program is read and executed by one or more processors included in the system or the apparatus. In addition, aspects of the invention may also be implemented by circuitry (e.g., an Application Specific Integrated Circuit (ASIC)) for performing one or more functions.

The present invention is not limited to the above embodiments, and various changes and modifications can be made within the spirit and scope of the present invention. Therefore, to apprise the public of the scope of the present invention, the following claims are appended.

The present application claims priority from japanese patent application 2017-091943 filed on 5/2 of 2017, which is incorporated herein by reference.