JP6355055B2 - Imaging system and application control method - Google Patents

Description

  The present invention relates to an imaging system and an application control method.

  Conventionally, when an application is installed in a device (execution device) that executes the application, the server (storage server) manages application programs and application packages (hereinafter also simply referred to as applications), and the storage server applies the application to the execution device May supply. The execution device installs and executes the supplied application.

  As a conventional system for handling applications, in a multifunction device with an embedded license file, when a license file is passed to the server and specified in response to a user operation, the server uses the specified license file to the multifunction device. It is known to install an application (see, for example, Patent Document 1).

  Also, the external terminal, the internal terminal, and the application server are registered in the management server, and the encrypted communication path is established between the application server and the internal terminal using the encrypted communication keys received from the management server. It is known (see, for example, Patent Document 2).

  In addition, there is a system in which captured images captured by an imaging apparatus are accumulated in an image recording apparatus and distributed to an image distribution apparatus as necessary. In such a system, the key management device distributes the shared key to the image distribution device and the image reproduction device, and the image recording device receives the image distribution from the plurality of image distribution devices and distributes the image to the image reproduction device. It is known (see, for example, Patent Document 3).

JP 2009-205262 A JP 2006-352834 A JP 2006-166279 A

  Assume that the execution device is applied to an imaging device that captures an image, and the application is applied to an application (camera application) used by the imaging device. In this case, with the techniques described in Patent Documents 1 to 3, the safety and operability of application control for the imaging device by the application server are insufficient.

  The present invention has been made in view of the above circumstances, and provides an imaging system and an application control method that can improve the safety and operability of application control for an imaging apparatus by a control apparatus that issues a control request to an application.

An imaging system of the present invention is an imaging system connected to an imaging apparatus, a management apparatus that manages control for the application for the imaging apparatus, and a network, and the management apparatus is an application for the imaging apparatus. And an imaging device identification information for identifying the imaging device related to the contract is generated based on a contract relating to the imaging device, and the imaging device identification information for identifying the imaging device related to the contract is generated. The control request from the control device and the imaging device identification information are acquired and acquired from the control device and the imaging device identification information transmitted to the control device. It is determined whether the control device has the control authority according to whether the imaging device identification information matches, If determined that the control device has the controlling authority, the control request acquired from the control unit, and sends to the identified are the imaging device by the imaging device identification information, the image pickup apparatus via the management device the The control request from the control device is received, and the application for the imaging device is controlled according to the control request.

An application control method of the present invention is an application control method in an imaging apparatus connected to an imaging apparatus, a management apparatus that manages control for the application for the imaging apparatus, and a network, and the management apparatus Generating a control authority for controlling the application for the imaging device based on the contract for the imaging device application and the imaging device, and identifying the imaging device according to the contract by the management device Is transmitted to the control device that issues a control request for the application for the imaging device, the control device acquires the control request and the imaging device identification information from the control device , and the control device The imaging device identification information transmitted to and the imaging device acquired from the control device If a separate information depending on whether or not match, the controller determines whether they have the controlling authority, by the management device, the control device is determined to have the controlling authority, the control request To the imaging device identified by the imaging device identification information, the imaging device receives the control request from the control device via the management device, and the imaging device responds to the control request. In response, the application for the imaging device is controlled.

  ADVANTAGE OF THE INVENTION According to this invention, the safety | security and operativity of application control with respect to an imaging device by the control apparatus which performs a control request | requirement to an application can be improved. For example, a mechanism in which the control device controls the imaging device using an application can be realized safely and easily for the user.

FIG. 2 is a schematic diagram illustrating a configuration example of a camera system according to the first embodiment. The schematic diagram which shows the structural example of each apparatus arrange | positioned in the shop in 1st Embodiment. The schematic diagram which shows the structural example of each apparatus arrange | positioned in the provider base in 1st Embodiment. 1 is a block diagram illustrating a configuration example of a camera according to a first embodiment. The block diagram which shows the structural example of the management server in 1st Embodiment. The block diagram which shows the structural example of the App server in 1st Embodiment. The schematic diagram which shows an example of the registration content of the table in which the user information which the management server in 1st Embodiment manages was registered The schematic diagram which shows an example of the registration content of the table in which the camera information which the management server in 1st Embodiment manages was registered. The schematic diagram which shows an example of the registration content of the table in which the App provider information which the management server in 1st Embodiment manages is registered. The schematic diagram which shows an example of the registration content of the table in which App information which the management server in 1st Embodiment manages is registered. The schematic diagram which shows an example of the registration content of the table in which the contract information which the management server in 1st Embodiment manages was registered The schematic diagram which shows an example of the registration content of the table in which the information of the CamApp control key which the management server in 1st Embodiment manages was registered. Sequence diagram showing an example of user registration and camera registration procedure by the camera system in the first embodiment Sequence diagram showing an example of App provider registration and App registration procedure by the camera system in the first embodiment The sequence diagram which shows an example of the App contract procedure by the camera system in 1st Embodiment Schematic diagram showing an example of a GUI screen in the first embodiment The sequence diagram which shows an example of the App utilization start procedure by the camera system in 1st Embodiment The schematic diagram which shows an example of the setting GUI displayed on the display of PC in 1st Embodiment Sequence diagram showing an example of the App use procedure by the camera system in the first embodiment The sequence diagram which shows an example of the App contract cancellation procedure by the camera system in 1st Embodiment FIG. 6 is a block diagram illustrating a configuration example of a camera according to a second embodiment. The block diagram which shows the structural example of the management server in 3rd Embodiment. The block diagram which shows the structural example of the App server in 4th Embodiment. The schematic diagram which shows an example of the registration content of the table in which CamApp information which the management server in 2nd Embodiment manages is registered. The schematic diagram which shows an example of the registration content of the table in which the installed CamApp information which the management server in 2nd Embodiment manages was registered. The schematic diagram which shows an example of the registration content of the table in which the contract information which the management server in 2nd Embodiment manages was registered The schematic diagram which shows an example of the registration content of the table in which the information which concerns on the CamApp control authority which the management server in 2nd Embodiment manages was registered. The sequence diagram which shows an example of the App registration procedure by the camera system in 2nd Embodiment The sequence diagram which shows an example of the App contract procedure by the camera system in 2nd Embodiment The sequence diagram which shows an example of the App utilization start procedure by the camera system in 2nd Embodiment The sequence diagram which shows an example of the App contract cancellation procedure by the camera system in 2nd Embodiment

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

(Background to obtaining one embodiment of the present invention)
As a surveillance camera system, a system in which a plurality of cameras (imaging devices) are controlled by an application server (hereinafter also referred to as an App server) via a network is assumed. In this surveillance camera system, for example, the App server causes each camera to install a camera application (hereinafter referred to as CamApp).

  In this surveillance camera system, for example, it is assumed that a master key of a camera is registered in an application server, and access is performed while ensuring security between the camera and the APP server using this master key.

  However, such a surveillance camera system has insufficient safety and operability. For example, since the App server retains the master key of the camera even after the CamApp contract ends, the camera can be controlled using CamApp even if the techniques of Patent Documents 1 and 2 are used. On the other hand, it is difficult for the camera owner to delete or change the master key once registered in the camera.

  If the master key is leaked, camera control using CamApp may be possible from another App server. Therefore, it is desired that camera control using CamApp becomes impossible after the contract of an application including CamApp is terminated.

  In addition, it is difficult to control the access authority to the camera by the App server. For example, it is difficult to specify to the App server which CamApp control authority is given to which camera.

  Hereinafter, an imaging system and an imaging apparatus control method that can improve the safety and operability of application control for an imaging apparatus by a control apparatus that issues a control request to an application will be described.

  An imaging system according to the following embodiment is applied to, for example, a monitoring camera system that monitors a person entering and exiting a store.

(First embodiment)
FIG. 1 is a schematic diagram illustrating a configuration example of a camera system 5 according to the first embodiment. FIG. 2 is a schematic diagram illustrating a configuration example of each device arranged in the store 3. FIG. 3 is a schematic diagram illustrating a configuration example of each device arranged in the provider base 90.

  The camera system 5 includes a management server 30, devices arranged in the store 3, and devices arranged in the provider base 90. In the store 3, for example, a PC 10, an input device 14, a display 15, and one or more cameras 20a, 20b, and 20c are arranged. In the provider base 90, for example, a PC 10A, an input device 14A, a display 15A, and one or more application (App) servers 40 are arranged. The number of cameras and App servers 40 is not limited to the examples shown in FIGS.

  In the camera system 5, for example, a plurality of types of cameras 20a, 20b, 20c installed in the store 3 and the PC 10 are connected to a network 8 such as the Internet. When it is not necessary to distinguish the individual cameras 20a, 20b, and 20c, they are collectively referred to as cameras 20. The camera 20 may be installed in a place other than a store (for example, an outdoor event hall or a toll road). PC10 is used for the user 7 of the shop 3, for example.

  In the camera system 5, the management server 30 and the App server 40 are connected to the network 8. Each device included in the camera system 5 can communicate data with each other via the network 8. The communication path using the network 8 may be a communication path encrypted with, for example, SSL (Secure Sockets Layer). In this case, the safety of data to be communicated is improved.

  In the camera system 5, the PC 10 </ b> A is connected to the network 8. The PC 10A is used for the App provider 9, for example.

  The PCs 10 and 10A have, for example, a CPU (Central Processing Unit) or a DSP (Digital Signal Processor), a ROM (Read Only Memory), or a RAM (Random Access Memory). The CPU or DSP executes various programs (for example, OS (Operating System), middleware program, application program) held in the ROM or RAM, and realizes various functions of the PCs 10 and 10A. For example, the PCs 10 and 10A download, install, and execute various applications.

  The PCs 10 and 10A include, for example, a communication interface for communicating with other communication devices, an input / output interface for inputting / outputting data, and a user interface.

  The PC 10 includes a web browser function unit 12 and includes an input device 14 and a display 15. The PC 10A includes a web browser function unit 12A, and includes an input device 14A and a display 15A. The Web browser function units 12 and 12A have a Web browser function, and for example, download an application (for example, HTML (HyperText Markup Language), Javascript (registered trademark)) from a Web server and execute it.

  For example, the user 7 is a user who receives and provides an application for the camera 20 (camera application: CamApp). The App provider 9 is a provider that generates and provides CamApp, for example.

  For example, the Web browser function unit 12 of the PC 10 accesses the App server 40 from a Web browser and executes a Web application (for example, HTML or Javascript (registered trademark) provided by the Web server). By the Web application, the PC 10 receives a service (for example, display of a captured image, display of statistical information based on metadata derived from the captured image) by a function provided by CamApp or a function provided by App corresponding to CamApp. it can. For example, the user 7 (for example, the owner of the store 3) uses the PC 10 to purchase a desired App from the management server 30 that operates the App store, so that the Camera App corresponding to App can be captured by the operation of the camera system 5. 20 can be installed and used. The management server 30 has an App store function, and the App server 40 is a server that is developed and managed by the App provider 9 in order to realize each App.

  The application is used, for example, for presenting user information to a Web server and transmitting input information from the user to the Web server. Note that the PCs 10 and 10A do not necessarily have the function of a Web browser, and other applications that operate on the PCs 10 and 10A (for example, native applications (Windows (registered trademark) application, Java (registered trademark) application, ios ( (Registered trademark) application, MacOS (registered trademark) application, etc.).

  The PC 10, 10A downloads, installs, and executes an application. Further, as the information processing apparatus, a smartphone or a tablet terminal may be used instead of the PCs 10 and 10A.

  The PC 10 and the camera 20 may be provided at different positions (for example, different stores 3). Further, the App server 40 may be arranged at a position other than the provider base 90. When there are a plurality of App servers 40, they may be distinguished by hardware, software, or hardware and software. When there are a plurality of App servers 40 that are distinguished by hardware, the App servers 40 may be installed separately (for example, at different locations).

  FIG. 4 is a block diagram illustrating a configuration example of the camera 20.

  The camera 20 has, for example, a CPU or DSP, ROM, or RAM. The CPU or DSP executes various programs (for example, OS, middleware program, application program) held in the ROM or RAM, and realizes various functions of the camera 20. For example, the camera 20 downloads, installs, and executes various applications.

  The camera 20 includes a communication interface for communicating with other communication devices, an input / output interface for inputting / outputting data, and a user interface, for example.

  The camera 20 includes a CamApp management unit 21, a control authority management unit 22, a control request reception determination unit 23, a management server authentication unit 24, a communication unit 25, a camera image distribution unit 26, an imaging unit 27, and an application execution unit 28. The camera 20 is installed in the store 3 or outside the store 3, for example. The application execution unit 28 is provided in the camera 20 by installing CamApp.

  The imaging unit 27 captures an image. The application execution unit 28 generates metadata from an image captured by the imaging unit 27 (captured image) based on, for example, a known method. The metadata includes, for example, information on facial features, age, sex, dressing, time (for example, imaging time and metadata generation time), and dressing.

  The CamApp management unit 21 controls and manages installation, uninstallation, activation, and termination of CamApp. The CamApp management unit 21 manages CamApp in response to a CamApp control request, for example. This control request includes, for example, CamApp installation, uninstallation, activation, termination, and update requests.

  The control authority management unit 22 receives a CamApp control authority change request from the management server 30, and manages the CamApp control authority for each CamApp in accordance with the change request. This change request includes, for example, a CamApp control authority setting request and a discard request. Here, the CamApp control authority is a CamApp control key generated by the management server 30. The CamApp control authority may be managed for each contract or for each contract and each camera 20.

  The control request acceptance determination unit 23 receives the CamApp control request from the App server 40 and determines whether the CamApp control request is a request from the App server 40 having a legitimate authority. In the case of a CamApp control request from a legitimate App server 40, the CamApp management unit 21 executes processing according to the CamApp control request. For example, if the CamApp control key held by the control authority management unit 22 matches the CamApp control key from the App server 40, it is determined that the request is a valid CamApp control request.

  The management server authentication unit 24 authenticates the management server 30 and ensures that requests and instructions from the management server 30 are valid. For example, the management server 30 can be authenticated by embedding an authentication key (for example, CamApp control authority control key (master key)) of the management server 30 when the camera 20 is manufactured.

  The communication unit 25 communicates various information and data. For example, the communication unit 25 receives a CamApp control request from the management server 30 or the App server 40.

  For example, in response to a request from each CamApp, the camera image distribution unit 26 acquires a camera image (captured image) captured by the imaging unit 27 and sends the camera image to CamApp. Note that the application execution unit 28 executes CamApp and generates metadata based on the camera image.

  FIG. 5 is a block diagram illustrating a configuration example of the management server 30.

  The management server 30 includes, for example, a plurality of users 7, a plurality of App providers 9, a plurality of cameras 20 for each user 7, a plurality of Apps for each App provider 9, a single App server 40 and a plurality of CamApps for each App. to manage.

  The management server 30 includes, for example, a CPU or DSP, ROM, or RAM. The CPU or DSP executes various programs (for example, OS, middleware program, application program) held in the ROM or RAM, and realizes various functions of the management server 30.

  In addition, the management server 30 includes, for example, a communication interface for communicating with other communication devices, an input / output interface for inputting / outputting data, and a user interface.

  The management server 30 manages various types of information, for example, controls for CamApp. The management server 30 includes a user management unit 31, a camera management unit 32, an App provider management unit 33, an App management unit 34, an App server authentication unit 35, a contract management unit 36, a control authority management unit 37, and a communication unit 38.

  The user management unit 31 manages user information (for example, information related to a user who uses CamApp). For example, when accessed from the PC 10 via a Web browser, the user management unit 31 performs authentication (user authentication) using a password managed by the user management unit 31. The user information is accumulated in a table 51 described later, for example.

  The camera management unit 32 manages information on the camera 20 (for example, information on the camera 20 on which CamApp is installed). The information on the camera 20 includes, for example, owner information on the camera 20. The information of the camera 20 is accumulated in, for example, a table 52 described later.

  The App provider management unit 33 manages the information of the App provider 9 (for example, information on the App provider that provides CamApp). The information of the App provider 9 is accumulated in, for example, a table 53 described later.

  The App management unit 34 manages App information including CamApp information. The App information includes, for example, information on the provider of the provider. App information is accumulated in, for example, a table 54 described later.

  The App includes, for example, a CamApp that is an application for the camera 20 and a server application that is an application for the App server 40 (also referred to as ServerApp). The function of App is realized by the combination of the execution of CamApp and ServerApp.

  The App server authentication unit 35 authenticates the App server 40 used to execute App. Thereby, the delivery of CamApp control authority (CamApp control key) can be performed correctly. The authentication technology of the App server 40 includes, for example, a message authentication code and a digital signature. In the message authentication code, when using MAC (Message Authentication Code), for example, the key used is a common key. This common key is, for example, a random number having a sufficient length generated by a random number generator. In the digital signature, different keys are used on the transmission side (for example, the management server 30) and the reception side (for example, the App server 40). This key is generated by, for example, a key generation algorithm of a public key cryptosystem.

  The contract management unit 36 manages contract information regarding an App (CamApp) contract. For example, the contract management unit 36 manages which user uses which App. The contract information is accumulated in, for example, a table 55 described later.

  The control authority management unit 37 manages which CamApp the App server 40 has to control which CamApp, that is, the CamApp control authority. Specifically, the control authority management unit 37 generates and manages a CamApp control key for managing the CamApp control authority. The CamApp control key is sent to the camera 20 in which CamApp is installed, and is sent to the App server 40 that provides CamApp. The CamApp control key is used when controlling CamApp. The CamApp control key is, for example, a random number generated by a random number generator (not shown) and corresponds to a sub key.

  When the CamApp control request is transmitted from the App server 40 to the camera 20, the CamApp control key is transmitted together, so that the camera 20 is the App server 40 with the request source having the correct CamApp control authority. I can confirm that.

  In addition, the control authority management unit 37 manages information related to a CamApp control key described later. Information relating to the CamApp control key is accumulated in, for example, tables 55 and 56 described later.

  The communication unit 38 communicates various information and data. For example, when the communication unit 38 is accessed via the Web browser function unit 12 of the PC 10 according to an instruction from the user 7 or the App provider 9, the communication unit 38 transmits HTML or Javascript (registered trademark) data for the user 7 or the App provider 9 to the Web. Return to the browser function unit 12.

  FIG. 6 is a block diagram illustrating a configuration example of the App server 40.

  The App server 40 includes, for example, a CPU or DSP, ROM, or RAM. The CPU or DSP executes various programs (for example, OS, middleware program, application program) held in the ROM or RAM, and realizes various functions of the App server 40.

  The App server 40 includes, for example, a communication interface for communicating with other communication devices, an input / output interface for inputting / outputting data, and a user interface.

  The App server 40 controls, for example, the CamApp of one or more cameras 20, collects various data (eg, metadata) from the one or more cameras 20, executes ServerApp, etc., and derives various statistical information To do. That is, the App server 40 uses the metadata collected from each camera 20 to generate data with high user value and provides it to the user's PC 10 or the like via the network 8.

  The App server 40 includes, for example, an App server for customer analysis App, an App server for store clerk analysis App, and an App server for customer notification App.

  The App server 40 includes a CamApp management unit 41, a control unit 42, a communication unit 45, and a statistical information management unit 46. The App server 40 stores CamApp and ServerApp.

  The statistical information management unit 46 collects various data (for example, metadata) from the camera 20 and derives various statistical information. The statistical information management unit 46 may derive the statistical information according to the processing result of the ServerApp held by the App server 40 together with the collected metadata. The result of the statistical information is sent to the PC 10 via the network 8, for example, and displayed on the display 15 of the PC 10. The statistical information is used for monitoring and marketing of the store 3, for example.

  The CamApp management unit 41 accumulates and manages CamApp information and CamAppPackage (camera application package) installed in the camera 20. The CamApp information includes, for example, CamApp identification information. The CamAppPackage includes, for example, a CamApp application main body and setting information for installing and executing CamApp.

  The communication unit 45 communicates various information and data. For example, the communication unit 45 requests the management server 30 to acquire a CamApp control key necessary when transmitting a CamApp control request to the camera 20. The communication unit 45 transmits, for example, a CamApp control request (for example, a request for starting, ending, installing, uninstalling, or updating a CamApp) or a CamAppPackage to the camera 20.

  For example, the communication unit 45 communicates information about GUI (for example, see FIG. 18) for initial setting of App or information display when using App to the user 7. For example, in the case of an application that sends an email to the user 7 when an event occurs, the GUI may be unnecessary. This event includes, for example, detection of a person registered in a memory or the like in advance, that the number of people in the store has reached a predetermined number or more, and that the number of customers at a predetermined time has reached a predetermined number or more.

  Next, specific examples of App, CamApp, and SeverApp will be described.

  Specific examples of App include customer analysis App, store clerk analysis App, shoplifter and customer notification App. Customer analysis App is an application for providing, as statistical information, the lead wire and staying time in the store 3 for each customer age and sex. The clerk analysis App is an application for providing the clerk's business attitude as statistical information. The shoplifter or customer notification App is an application for notifying by e-mail or the like when a specific person enters the store 3, for example. As information on a specific person (for example, facial feature information), information registered by the user is registered in advance in the memory of the App server 40.

  Specific examples of CamApp include, for example, face identification App, age sex estimation App, posture detection App, and face identification matching App. The face identification App is an application for obtaining face identification information (face recognition information), for example, by performing a known face identification process (face recognition process) on a captured image. Age sex estimation App is an application for obtaining age sex information by performing a known age sex estimation process on a captured image, for example. Age sex includes at least one of age and sex. The posture detection App is an application for obtaining posture information of a clerk or the like by performing a known posture detection process on the captured image, for example. The posture information includes, for example, information on a standing posture, a sitting posture, and a bowing posture. The face identification matching App is an application for, for example, comparing face information registered in advance with face information detected by face identification (face identification matching) and obtaining a determination result as to whether or not they are the same person. .

  The above-mentioned CamApp is used, for example, as a CamApp for the entrance of the store 3, a CamApp for the inside of the store 3 (for example, for a cashier), and a CamApp for the exit of the store 3, for example.

  Specific examples of ServerApp include customer tracking App, statistical information calculation App, and email notification App. The customer tracking App is an application for tracking customer trends in the store 3 according to the results of face identification processing, age and gender estimation processing, and posture detection processing, for example. The statistical information calculation App is an application for calculating various statistical information based on various information obtained by CamApp. This statistical information can be derived in consideration of various aspects such as each App, each CamApp, each camera 20, and each App contract. The e-mail notification App is an application for e-mail notification when a specific person is detected by face identification matching, for example.

  For example, when calculating customer tracking and statistical information as customer analysis, the App server 40 collects face identification information and age / gender estimation information as metadata related to CamApp. The App server 40 can derive, for example, the customer's age, the customer's conductor in the store 3, and the customer's stay time as statistical information based on the collected metadata. Then, the App server 40 can provide the derived statistical information to the owner of the store 3 or the like.

  For example, when calculating salesclerk tracking and statistical information as salesclerk analysis, the App server 40 collects face identification information, posture detection information, and the like as metadata related to CamApp. Based on the collected metadata, the App server 40 can derive, for example, the lead of the clerk in the store 3 and the business attitude of the clerk as statistical information. The business attitude includes, for example, an attitude of standing, sitting, or bowing.

  For example, the App server 40 collects matching information with face identification information, a pre-registered face image, or the like as metadata related to CamApp, for example, when performing shoplifter notification or customer notification using email. To do. Thereby, the App server 40 can notify the user 7 (for example, the owner of the store 3) by e-mail when it is detected that a specific person has entered the store 3.

  The parameters included in each CamApp include, for example, the resolution of the image used for calculating the facial feature amount and the matching threshold used for the face search process.

  FIG. 7 is a schematic diagram illustrating an example of registered contents of the table 51 in which user information managed by the management server 30 is registered.

  The table 51 is managed by the user management unit 31 in the management server 30. In the table 51, for example, user ID, e-mail address, and password information are registered for each user 7 as user information.

  The user ID is an example of CamApp user identification information. The e-mail address is an e-mail address used by the user 7. The password is a password used by the user 7. For example, a user ID: “1001”, a mail address: “xxx@xxx.com”, and a password: “xxx” are registered.

  FIG. 8 is a schematic diagram illustrating an example of registered contents of the table 52 in which camera information managed by the management server 30 is registered.

  The table 52 is managed by the camera management unit 32 in the management server 30. In the table 52, for example, for each camera 20, a camera ID, a URL (Uniform Resource Locator), a user ID, and a camera name are registered as camera information.

  The camera ID is an example of identification information of the camera 20 in which CamApp is installed. The URL is the URL of the camera 20 in which CamApp is installed. The camera name is the name of the camera 20 in which CamApp is installed. The camera name can be arbitrarily set by the user 7 via the input device 14 of the PC 10, for example.

  For example, camera ID: “1101”, URL: “http: //xxx.xxx.xxx.001/camera.cgi”, user ID: “1001”, camera name: “entrance camera” are registered.

  FIG. 9 is a schematic diagram illustrating an example of registered contents of the table 53 in which App provider information managed by the management server 30 is registered.

  The table 53 is managed by the App provider management unit 33 in the management server 30. In the table 53, for example, an App provider ID, a mail address, and a password are registered for each App provider 9 as App provider information.

  The App provider ID is an example of identification information of the App provider 9 that provides CamApp. The e-mail address is an e-mail address used by the App provider 9 that provides CamApp. The password is a password used by the App provider 9 that provides CamApp.

  For example, App provider ID: “2001”, mail address: “xxxx@pppp.com”, and password: “xxxxxxxx” are registered.

  FIG. 10 is a schematic diagram illustrating an example of registered contents of the table 54 in which App information managed by the management server 30 is registered.

  The table 54 is managed by the App management unit 34 in the management server 30. In the table 54, for example, AppID, App name, App description, App provider ID, and App server authentication key are registered as App information.

  AppID is an example of App identification information corresponding to CamApp. The App name is the name of App corresponding to CamApp. The App description is information for explaining the contents of App corresponding to CamApp. The App provider ID is an example of identification information of the App provider 9 that provides App corresponding to CamApp. The App server authentication key is a key for authenticating the App server 40 that provides App corresponding to CamApp.

  For example, AppID: “2101”, App name: “People Count”, App description: “Statistical information such as counting people, every time zone, every day of the week, every month, etc.”, App provider ID: “2002” "App server authentication key:" qazwsxedcrfvtgb "is registered.

  FIG. 11 is a schematic diagram illustrating an example of registered contents of the table 55 in which contract information managed by the management server 30 is registered.

  The table 55 is managed by the contract management unit 36 in the management server 30. In the table 55, for example, a contract ID, a user ID, an AppID, a contract authentication key, and a CamApp control key are registered as contract information. The contract ID is an example of identification information for identifying a contract that receives the provision of App. The user ID is an example of identification information of a user as a contractor. AppID is an example of identification information of a contracted App. The contract authentication key is a key for referring to contract contents and usage information (for example, usage history information) of the contracted App. The CamApp control key is a control key for controlling the CamApp corresponding to the contracted App.

  For example, contract ID: “3001”, user ID: “1001”, AppID: “2101”, contract authentication key: “asdfghjklsdfghjklassdfghjkl” are registered.

  When the table 55 is used, for example, one CamApp control key is issued for each contract. In this case, the CamApp control key is transmitted to and used by each camera 20 owned by the user 7 who has signed the App contract.

  When the table 55 is used, a CamApp control key may be issued for each contract and each camera. In this case, an individual CamApp control key is transmitted and used for each camera for one contract (one App). In this case, the management server 30 also uses a table 56 shown in FIG. Further, in this case, the information of “CamApp control key” in the table 55 becomes unnecessary.

  FIG. 12 is a schematic diagram illustrating an example of registered contents of the table 56 in which information about the CamApp control key managed by the management server 30 is registered. The table 56 is referred to together with the table 55.

  The table 56 is managed by the control authority management unit 37 in the management server 30. In the table 56, for example, a CamApp control key ID, a contract ID, a camera ID, and a CamApp control key are registered as information about the CamApp control key. The CamApp control key ID is an example of identification information of a CamApp control key.

  By using the table 55 and the table 56, one CamApp control key and CamApp control authority are determined for each contract and each camera.

  The user 7 may specify the camera 20 used for each App via the input device 14 or the like. Thereby, the user 7 can permit access to a specific camera 20 among the cameras 20 owned by the user 7.

  In the example of the table 56, the App (App server) associated with the contract ID: 3001 is permitted to control CamApp to the three cameras 20 identified by the camera IDs: 1101, 1102, and 1103. An App (App server) related to the contract ID: 3002 is permitted to control CamApp to a total of one camera 20 identified by the camera ID: 1101.

  By using the table 56, security can be further improved.

  Next, an operation example of the camera system 5 will be described.

  FIG. 13 is a sequence diagram illustrating an example of user registration and camera registration procedures by the camera system 5.

  In the PC 10, when the user 7 requests user registration through the input device 14, the Web browser function unit 12 makes a user registration request to the management server 30 (T1). In this user registration request, the e-mail address and password information of the user 7 held by the PC 10 or input via the input device 14 is transmitted from the PC 10 to the management server 30.

  In the management server 30, when the communication unit 38 receives a user registration request from the PC 10, the user management unit 31 performs user registration, and the communication unit 38 returns a user registration completion to the PC 10 (T2). In the user registration, the user management unit 31 attaches a user ID for identifying the user 7 based on the user registration request, and causes the table 51 to store the user ID, the email address from the PC 10 and the password.

  In the PC 10, when the user 7 inputs a mail address and password via the input device 14 and requests login, the Web browser function unit 12 transmits a mail address and password to the management server 30 to request login. (T3).

  In the management server 30, when the communication unit 38 receives a login request and a mail address and password from the PC 10, the user management unit 31 refers to the table 51 and collates the mail address and password. If the verification is successful, that is, if there is a matching mail address and password, the communication unit 38 issues a session ID and notifies login completion (T4). This session ID is managed in association with the user ID.

  In the PC 10, when the user 7 requests camera registration via the input device 14 or the like, the Web browser function unit 12 makes a camera registration request to the management server 30 using the session ID (T5). In this camera registration request, the camera name and the camera URL are transmitted from the PC 10 to the management server 30.

  In the management server 30, when the communication unit 38 receives a camera registration request from the PC 10, the camera management unit 32 performs camera registration. In this camera registration, the camera management unit 32 identifies the camera 20 based on the camera registration request, the URL for accessing the camera 20 via the network (camera URL), and the owner of the camera 20 Information on the user ID and the name of the camera 20 (camera name) is stored in the table 52 as information. A value associated with the session ID is used as the user ID.

  The communication unit 38 sends a connection confirmation to the camera URL designated by the camera registration request (T6). When the camera 20 is normally connected, the communication unit 38 receives a camera connection response from the camera 20 (T7). Then, the communication unit 38 returns camera registration completion to the PC 10 (T8).

  According to the user registration and camera registration procedure shown in FIG. 13, the camera system 5 can easily set the information of the user 7 and the information of the camera 20 in the management server 30.

  In T5, it is exemplified that the PC 10 makes a camera registration request to the management server 30 without going through the camera 20, but the PC 10 makes a camera registration request to the management server 30 through the camera 20 based on the input of the user 7. Also good. In this case, when a camera registration request is made, user ID, password, and camera name information is sent. Even in this case, the management server 30 can access the camera 20.

  FIG. 14 is a sequence diagram showing an example of App provider registration and App registration procedures by the camera system 5.

  In the PC 10A, when the App provider 9 requests App provider registration via the input device 14A or the like, the Web browser function unit 12 makes an App provider registration request to the management server 30 (T11). In this App provider registration request, the email address and password information of the App provider 9 that is held by the PC 10A or input via the input device 14A or the like is transmitted from the PC 10A to the management server 30.

  In the management server 30, when the communication unit 38 receives an App provider registration request from the PC 10A, the App provider management unit 33 performs App provider registration, and the communication unit 38 returns App provider registration completion to the PC 10A (T12).

  In this App provider registration, the App provider management unit 33 attaches an App provider ID for identifying the App provider 9 based on the App provider registration request, and the App provider ID, the email address and password of the App provider 9 are stored in the table 53. Hold. When the App provider registration is completed, the App provider ID is returned to the PC 10A.

  In the PC 10A, when the App provider 9 inputs a mail address and password via the input device 14A and requests login, the Web browser function unit 12A transmits a mail address and password to the management server 30 to request login. (T3A).

  In the management server 30, when the communication unit 38 receives the login request and the mail address and password from the PC 10A, the user management unit 31 refers to the table 53 and collates the mail address and password. If the collation is successful, that is, if there is a matching mail address and password, the communication unit 38 issues a session ID and notifies login completion (T4A). This session ID is managed in association with the App provider ID.

  In the PC 10A, when the App provider 9 requests the App registration via the input device 14A or the like, the Web browser function unit 12 makes an App registration request to the management server 30 using the session ID (T13). In this App registration request, the App name and the App description are transmitted from the PC 10A to the management server 30. The App name is input by, for example, the input device 14A of the PC 10A.

  In the management server 30, when the communication unit 38 receives an App registration request from the PC 10A, the App management unit 34 performs App registration, and the communication unit 38 returns App registration completion to the PC 10A (T14). In the App registration, the App management unit 34 attaches an AppID based on the App registration request, generates an App server authentication key, identifies the AppID, the App name from the PC 10A, the App description related to the App identified by the AppID, and the AppID. The table 54 stores an App provider ID for identifying the App provider 9 that provides the App to be executed and an App server authentication key. Upon completion of App registration, AppID and App server authentication key are returned to PC 10A.

  In the App server 40, when the App provider 9 receives various types of information via the input device 14B of the App server 40, the control unit 42 sets various types of information (T15). This setting indicates that various types of information are held in the memory of the App server 40, for example. The various information includes, for example, information on AppID and App server authentication key.

  The communication unit 45 can access the management server 30 using the set AppID and App server authentication key (T16).

  According to the App provider registration and App registration procedure shown in FIG. 14, the camera system 5 can easily set the information of the App provider 9 and the information of the App. Further, by using the App server authentication key, the security of communication between the App server 40 that can be used by the App provider 9 and the management server 30 can be secured.

  FIG. 15 is a sequence diagram illustrating an example of an App contract procedure by the camera system 5.

  First, the PC 10 performs the process of T3 shown in FIG. The management server 30 performs the process T4 shown in FIG.

  In the PC 10, when the user 7 requests acquisition of the App list via the input device 14 or the like, the Web browser function unit 12 requests the management server 30 to acquire the App list using the session ID (T21). .

  In the management server 30, when the communication unit 38 receives a request for acquiring the App list, the App management unit 34 extracts the App information as an App list from the table 54, and the communication unit 38 transmits the extracted information to the PC 10 ( T22). In this case, the App management unit 34 extracts all or part of each App information as an App list.

  In the PC 10, when the Web browser function unit 12 acquires the App list and the user 7 selects a desired App from the App list via the input device 14 or the like, the Web browser function unit 12 uses the session ID to manage the management server. An App contract request is made to T30 (T23). In the App contract request, AppID for identifying the selected App is sent from the PC 10 to the management server 30.

  In the management server 30, when receiving the request for the App contract, the communication unit 38 transmits information on the GUI screen 59 (see FIG. 16) to the PC 10 (T24). The GUI screen 59 is a setting screen for setting a camera used in the contracted App.

  In the PC 10, the Web browser function unit 12 acquires the GUI screen 59, and the user 7 selects a camera to be used in the contracted App through the input device 14 or the like (T25). Then, the Web browser function unit 12 includes the selection information of the camera in the setting information and transmits it to the management server 30 (T26).

  In the management server 30, when the communication unit 38 receives the setting information from the PC 10, the control authority management unit 37 generates a CamApp control authority by generating a CamApp control key (T27). Then, the communication unit 38 notifies the camera 20 of a CamApp control key registration request including information on the CamApp control key (T28). The registration request for the CamApp control key is notified to the camera 20 selected in T25, for example.

  In the camera 20, the communication unit 25 receives the CamApp control key registration request, and the control authority management unit 22 registers the CamApp control key, thereby setting the CamApp control authority. The CamApp control key is held in the control authority management unit 22, for example. In addition, the communication unit 25 returns registration completion of the CamApp control key to the management server 30 (T29).

  When the CamApp control key is registered in the camera 20, the management server authentication unit 24 uses the camera control authority control key (master key) written at the time of manufacturing the camera 20 to determine whether the CamApp control key can be registered, that is, CamApp. It may be determined whether control authority can be set.

  In the management server 30, when the communication unit 38 receives a notification of CamApp control authority registration completion from the camera 20, the contract management unit 36 registers the contract. In the contract registration, the contract management unit 36 assigns a contract ID based on the App contract request, generates a contract authentication key, controls the contract ID, the user ID related to the contract, the App ID related to the contract, the contract authentication key, and the CamApp control. The key is held in the table 55. The contract registration may be performed before the management server 30 receives a registration completion notification from the camera 20.

  When one CamApp control key is issued for each contract, information registration in the table 55 is sufficient, but when a CamApp control key is issued for each contract and one camera, information registration in the table 56 is performed. Is also done. Specifically, in contract registration, the control authority management unit 37 issues a CamApp control key ID based on the App contract request and the setting information in T26, and the contract ID, camera ID, and CamApp control key are displayed in the table 56. To hold.

  The communication unit 25 transmits the contract ID and contract authentication key information held in the table 55 to the PC 10 and notifies the completion of the App contract (T30).

  According to the App contract procedure shown in FIG. 15, the camera 20 can register a CamApp control key for each contracted App, that is, can set CamApp control authority. Thereby, the control with respect to CamApp installed in the camera 20 can be restrict | limited to a specific apparatus, and the unauthorized change and use of CamApp can be suppressed.

  Note that the processing from T24 to T26 may be omitted. In this case, for the App selected in T23, the CamApp control key is set for all the cameras 20 owned by the user 7. Therefore, the App server 40 can control CamApp for all the cameras 20 owned by the user 7.

  FIG. 16 is an example of the GUI screen 59. The GUI screen 59 is provided to the PC 10 by the management server 30 when, for example, the user 7 newly makes an App contract or when the user 7 changes the settings of the already-applied App. The GUI screen 59 designates which camera 20 is allowed to install CamApp corresponding to App.

  FIG. 16 illustrates that App is a customer analysis App, and an entrance camera, an exit camera, and a drink corner camera are selected as the cameras 20 that allow installation of CamApp. In this case, for example, a camera ID for identifying the selected camera 20 is sent from the PC 10 to the management server 30.

  Note that the camera name displayed on the GUI screen 59 may be arbitrarily selected by the user 7 via the input device 14 or the like. For example, when information about the camera 20 is registered in the management server 30, a camera name is designated.

  In the case of FIG. 16, the CamApp control key is registered for the entrance camera, the exit camera, and the drink corner camera selected on the GUI screen 59, and the access authority (CamApp control authority) from the App server 40 is given.

  FIG. 17 is a sequence diagram illustrating an example of an App usage start procedure by the camera system 5.

  In the PC 10, when the user 7 inputs a contract ID and a contract authentication key via the input device 14 and requests login, the Web browser function unit 12 transmits the contract ID and the contract authentication key to the App server 40. To log in (T31).

  In the App server 40, when logged in, the communication unit 45 transmits the contract ID and contract authentication key information acquired from the PC 10 to the management server 30, and requests the contract information (T32). In addition, for the authentication of the App server 40, the communication unit 45 may transmit an AppID and an App server authentication key to the management server 30.

  In the management server 30, when the communication unit 38 receives a request for contract information, the contract management unit 36 extracts part or all of the contract information held in the table 55 related to the acquired contract ID, and the communication unit 38 transmits the extracted contract information to the App server 40 (T33). The contract information includes a CamApp control key. In the App server 40, the control unit 42 holds a CamApp control key. In the App server 40, the CamApp control key is managed in association with each contract ID or for each contract ID and camera ID.

  When one CamApp control key is issued for each contract, the contract management unit 36 has only to extract the contract information from the table 55. On the other hand, when a CamApp control key is issued for each contract and each camera, the control authority management unit 37 further extracts a part or all of the information of the CamApp control key from the table 56. Then, the communication unit 38 transmits the extracted CamApp control key information to the App server 40. In the App server 40, the control unit 42 holds a CamApp control key.

  In the App server 40, the communication unit 45 transmits a contract ID and a contract authentication key to the management server 30, and requests camera information (T34).

  In the management server 30, when the communication unit 38 receives a request for camera information, the camera management unit 32 extracts part or all of the camera information held in the table 52 relating to the acquired contract ID, and the communication unit 38 transmits the extracted camera information to the App server 40 (T35).

  In the App server 40, when the communication unit 38 receives the camera information from the management server 30, it issues a session ID to the PC 10 and transmits information on a setting GUI 60 (see, for example, FIG. 18) that is an initial setting screen ( T36). This session ID is associated with the contract ID.

  In the PC 10, for example, when the user 7 inputs setting information via the input device 14 using the setting GUI 60, the Web browser function unit 12 transmits this setting information to the App server 40 using the session ID (T37). ). This setting information includes, for example, CamAppID for identifying CamApp and information for selecting the installation location of the camera 20 by the PC 10.

  In the App server 40, when receiving the setting information, the communication unit 45 transmits the CamAppPackage and the CamApp control key related to the selected CamAppID and the installation location of the camera 20 to the camera 20 to request installation of CamApp. (T38). This installation request is made to the installation target camera 20, that is, all the cameras 20 related to the contract or the specific camera 20. In addition, as the CamApp control key to be transmitted, the contract ID or the CamApp control key associated with the contract ID and the camera ID is selected.

  In the camera 20 to be installed, when the communication unit 25 receives a CamApp installation request, the control request acceptance determination unit 23 determines whether or not the installation request from the App server 40 is permitted using the CamApp control key. For example, the control request acceptance determination unit 23 grants an installation request when the CamApp control key transmitted at T38 matches the CamApp control key registered at T28 from the management server 30; Do not grant the request.

  When it is determined that the installation request is permitted, the CamApp management unit 21 installs CamApp using the CamAppPackage. When the installation of CamApp is completed, the communication unit 25 transmits the installation completion to the App server 40 (T39). Note that the installed CamApp including the installation ID in the installation completion notification is controlled using the installation ID.

  In the App server 40, the communication unit 45 transmits the selected CamAppID and the CamApp control key and the installation ID related to the installation location of the camera 20 to the camera 20 to request activation of CamApp (T40). This activation request is made to the activation target camera 20, that is, all the cameras 20 related to the contract or the specific camera 20.

  In the camera 20 to be activated, when the communication unit 25 receives a CamApp activation request, the control request acceptance determination unit 23 determines whether the activation request from the App server 40 is permitted using the CamApp control key. The method for determining whether or not the activation request is permitted is the same as the method for determining whether or not the installation request is permitted.

  When it is determined that the activation request is permitted, the CamApp management unit 21 activates CamApp related to the installation ID. When the activation of CamApp is completed, the communication unit 25 transmits the activation completion to the App server 40 (T41).

  In the App server 40, when the communication unit 25 receives the completion of activation from the camera 20, it transmits a dashboard page to the PC 10 (T42).

  According to the App usage start procedure shown in FIG. 17, it is possible to specify which CamApp should be installed in which camera by the PC 10. For example, the user 7 is the owner of the store 3 (for example, a store or a restaurant), and sufficiently understands which camera image he / she wants to use for what purpose. When the user 7 uses the PC 10 to specify the camera 20 and CamApp to be installed, the user 7 can reflect the intention of the user 7 and can be installed in CamApp.

  Further, the App server 40 can safely acquire contract information and camera information from the management server 30 by using the contract authentication key. Further, the camera 20 can securely control the CamApp by authenticating the App server 40 using the CamApp control key related to the contract, and can suppress, for example, unauthorized use or CamApp modification.

  FIG. 18 is a schematic diagram illustrating an example of the setting GUI 60 displayed on the display 15 of the PC 10.

  For example, the setting GUI 60 is displayed on the screen of the display 15 of the PC 10 and is operated by the user via the input device 14 of the PC 10 or the like. For example, the input device 14 receives an input operation for selecting a specific camera 20 from a plurality of cameras 20 installed in the store 3. For example, it is possible to set which CamApp is installed for the cameras 20 installed in various places of the store 3.

  The CamApp is, for example, a CamApp for the camera 20 installed at the entrance of the store 3 (described simply as “entrance” in FIG. 18), or a CamApp for the camera 20 installed at the exit of the store 3 (in FIG. 18). And “CamApp” for the camera 20 installed in the rest of the store 3 (indicated simply as “others” in FIG. 18).

  In FIG. 18, camera names: “entrance camera”, “exit camera”, “bento corner camera”, and “drink corner camera” are displayed as the plurality of cameras 20 installed in the store 3. This camera name corresponds to the installation location of the camera 20.

  The CamApp installed in each of the “entrance camera”, “exit camera”, “lunch corner camera”, and “drink corner camera” is selected by the input device 14 using the pull-down menu 61, for example. The selected information (for example, CamAppID for identifying the selected CamApp) is transmitted to the App server 40 as setting information, for example.

  Further, the input device 14 of the PC 10 uses the setting GUI 60 to select the start time and end time of the time zone for which the statistics by the App server 40 are desired using the pull-down menu 64. The selected information is transmitted to, for example, the App server 40 and used for statistical information derivation processing by the App server 40.

  By using the setting GUI 60, the user 7 can easily input which CamApp should be installed in which camera 20 using the input device 14. Further, the user 7 can easily input the time zone for which statistics are desired and other information related to the statistics.

  In this example, the user 7 selects the CamApp to be installed via the input device 14 or the like. However, even if the User 7 installs the CamApp in the installation destination camera 20 without selecting the CamApp. Good. Thereby, App 7 can be easily used without being conscious of each CamApp.

  Two other examples of the method of specifying the CamApp to be installed are shown below. In another example, it is assumed that a combination of an installation location of the camera 20 and a CamApp installed in the camera 20 is determined in advance, and information on the combination is stored in the CamApp management unit 41 of the App server 40 in advance. . The combination of the installation location of the camera 20 and the CamApp to be installed may be different for each App.

  For example, in the camera 20, the communication unit 25 may transmit an image captured by the imaging unit 27 to the App server 40. In the App server 40, the CamApp management unit 41 may determine the installation position of the camera 20 (for example, the entrance of the store 3 or the exit of the store 3) by performing predetermined image processing. The CamApp management unit 41 may designate CamApp corresponding to the determined installation position as the CamApp to be installed.

  For example, at the time of an App contract (for example, when the camera 20 is initially set), an operator (not shown) located remotely visually recognizes the image of each camera 20 to determine the installation position, and uses an App server via an input device or the like. Information on the installation position of each camera 20 as a determination result may be set in 40. In the App server 40, the CamApp management unit 41 may designate the CamApp corresponding to the determined installation position as the CamApp to be installed.

  When the user 7 installs CamApp without selecting the CamApp to be installed, the user of App installs the CamApp for entrance or the CamApp for exit at the camera 20 installed at the entrance or exit of the store 3. You do not have to recognize that. In addition, the App user does not need to recognize what processing is performed by the entrance CamApp and the exit CamApp.

  FIG. 19 is a sequence diagram illustrating an example of an App use procedure by the camera system 5.

  In the camera 20, the imaging unit 27 captures an image, the application execution unit 28 generates metadata from the captured image, and the communication unit 25 transmits the metadata to the App server 40 (T51). The metadata may be sequentially transmitted from each camera 20.

  For example, the camera 20 calculates the feature value (an example of metadata) of the customer's face by executing the CamApp for the entrance of the store 3, and uses the feature amount for the CamApp for the interior of the store 3 and for the exit It transmits to the App server 40 corresponding to CamApp. Note that there is one App server 40 for each App. When the feature amount matching is performed in CamApp, the feature amount calculated by the entrance CamApp is sent to the internal CamApp and the exit CamApp. When the feature amount matching is performed by the App server 40, the feature amount calculated by the entrance CamApp is transmitted to the App server 40.

  For example, the camera 20 searches for a face that matches the feature amount (an example of metadata) calculated by the CamApp for the entrance of the store 3 by executing the CamApp for the inside of the store 3. When a matching face is found, the camera 20 transmits information (an example of metadata) including that a matching face exists to the App server 40 corresponding to the CamApp for the inside of the store 3. The calculated feature amount may be transmitted as metadata to the App server 40, and the App server 40 may perform face matching processing.

  For example, the camera 20 searches for a face that matches the feature amount calculated by the CamApp for the entrance of the store 3 by executing the CamApp for the exit of the store 3. When a matching face is found, the camera 20 transmits information including that a matching face exists to the App server 40. The calculated feature amount may be transmitted as metadata to the App server 40, and the App server 40 may perform face matching processing.

  In the App server 40, the communication unit 45 receives the metadata, and the application execution unit 28 determines which contract or metadata is based on the camera 20 that is the transmission source of the acquired captured image. Statistical information for each is calculated.

  In the PC 10, the user 7 inputs a contract ID and a contract authentication key via the input device 14 and requests login, and the Web browser function unit 12 transmits the contract ID and the contract authentication key to the App server 40. To log in (T52).

  In the App server 40, when the communication unit 45 receives a login request, the CamApp management unit 41 issues a session ID in response to the login, and the communication unit 45 transmits information on the dashboard page to the PC 10 (T53).

  In the PC 10, when the web browser function unit 12 receives the information on the dashboard page, the dashboard page including the received information is displayed on the display 15.

  In the PC 10, when the user 7 selects one of the buttons on the dashboard page using the session ID via the input device 14 or the like, the Web browser function unit 12 instructs the App server 40 to execute the selected execution button. Necessary information related to is requested (T54).

  In the App server 40, when the communication unit 45 receives a request for necessary information related to the selected button, the statistical information management unit 46 derives various statistical information based on the acquired information. The communication unit 45 transmits display information to be displayed on the dashboard page to the PC 10 (T55). The App server 40 manages the session ID and the contract ID in association with each other, and determines the contract ID based on which contract ID the access source is based on the session ID.

  In the PC 10, the Web browser function unit 12 receives display information from the App server 40, and the display 15 displays a dashboard page according to the display information.

  Thereby, for example, when a predetermined button is selected, a result relating to the selected statistical process is displayed on the display 15.

  According to the App usage procedure shown in FIG. 19, the user 7 can confirm the image captured by the desired camera 20 and the statistical information related to the desired App using the PC 10, and can improve convenience. Further, the user 7 can easily input using the dashboard page when confirming the image captured by the desired camera 20 or the statistical information related to the desired App.

  FIG. 20 is a sequence diagram illustrating an example of an App contract cancellation procedure by the camera system 5.

  First, the PC 10 performs the process of T3 shown in FIG. The management server 30 performs the process T4 shown in FIG.

  In the PC 10, when the user 7 requests acquisition of the App contract list via the input device 14 or the like, the Web browser function unit 12 requests the management server 30 to acquire the App contract list using the session ID ( T61).

  In the management server 30, when the communication unit 38 receives a request for acquiring the App contract list, the contract management unit 36 extracts contract information from the table 55 as an App contract list, and the communication unit 38 extracts the extracted information. It transmits to PC10 (T62). In this case, the contract management unit 36 extracts all or a part of each piece of contract information as an App contract list.

  In the PC 10, the Web browser function unit 12 acquires the App contract list, the user 7 refers to the App contract list displayed on the display 15, and instructs the discard of a specific App contract by the input device 14 or the like. Then, the Web browser function unit 12 transmits the contract ID of the contract instructed to cancel the contract to the management server 30 using the session ID, and requests the App contract to be canceled (T63).

  In the management server 30, when the communication unit 38 receives a request for discarding the App contract from the PC 10, the control authority management unit 37 requests the camera 20 to discard the CamApp control key related to the acquired contract ID (T64).

  In the camera 20, when the communication unit 25 receives a CamApp control key discard request, the control authority management unit 22 discards the held CamApp control key. The control authority management unit 22 may discard the CamApp control key, and the CamApp management unit 21 may search for a CamApp related to the CamApp control key and uninstall this CamApp.

  In the camera 20, when the CamApp control key is discarded, the communication unit 25 notifies the management server 30 and the PC 10 of the completion of the CamApp control key destruction (T65, T66).

  According to the App contract discard procedure shown in FIG. 20, the camera 20 can easily discard the App contract and can discard the CamApp control key related to the discarded App contract. Therefore, even when the camera 20 acquires the CamApp control key from the App server 40, the camera 20 can not permit control of CamApp. Therefore, it is possible to suppress the camera 20 from being controlled using CamApp after the App contract ends.

  According to the camera system 5 of the present embodiment, the management server 30 can control the access authority (control authority) to the camera 20 with respect to the App server 40. In other words, the management server 30 can easily provide the CamApp control authority for the specific camera 20 to the specific App server 40 using the CamApp control key. Therefore, the camera system 5 can safely and easily realize a mechanism in which the App server 40 controls the camera 20 using CamApp.

  Therefore, for example, even when CamApp is newly installed remotely according to the request of the user 7 after installation of the camera 20, the camera system 5 can improve the safety related to the installation and can realize the function addition by CamApp.

  In addition, even when the App provider 9 as a third party different from the monitoring agent by the user 7 or the camera 20 newly develops CamApp and provides the CamApp using the App server 40, the camera system 5 is connected to the CamApp. Can be limited to a specific App server 40. Therefore, even when the degree of freedom in using the App server 40 is increased, it is possible to ensure security when accessing the CamApp and the camera 20 from the App server 40.

  Further, the camera 20 can extract metadata such as age and sex from the captured image using CamApp, and the App server 40 can obtain various statistical information using the metadata. The user 7 can utilize the obtained information for monitoring and marketing. The App server 40 can also derive, for example, the correlation between the customer residence time in the store 3 and the sales as statistical information, and can estimate the customer psychology and use it for store management.

  In addition, by installing an appropriate CamApp for each camera 20, the App server 40 can collect and analyze various attributes (for example, facial features, age, gender, dress, time). The analysis results can be utilized.

  In addition, by using the CamApp control key generated by the management server 30, the camera 20 can confirm that it is an installation request and activation request from the legitimate App server 40, and safety when installing and starting CamApp. Can be improved.

  Further, the camera 20 can ensure that the request or instruction from the management server 30 is valid by authenticating the management server 30 by the management server authentication unit 24.

  Further, when the App contract is terminated, the CamApp control authority is deleted from the camera 20 so that the App server 40 cannot access the camera 20 via the CamApp. Therefore, the App server 40 after the contract ends can access the camera 20. It can prevent fraud.

  Further, by using the CamApp control authority, it is not necessary to change the master key of the camera 20 every time the contract is terminated, and the complexity in key management can be reduced. Moreover, since the App server 40 acquires the CamApp control key without acquiring the master key, it is possible to reduce the leakage of the master key of the camera 20.

  Further, by using the setting GUI 60, the user 7 can easily perform an operation of selecting the installation location of the camera 20, and the operability can be improved.

(Second Embodiment)
In the first embodiment, the App server 40 (CamApp management unit 41 of the App server 40) stores the CamAppPackage including the CamApp. In the second embodiment, it is exemplified that the management server 30A stores the CamAppPackage including the CamApp.

  In the camera system 5A of the second embodiment, the same components as those of the camera system 5 of the first embodiment are denoted by the same reference numerals, and description thereof is omitted or simplified. The configuration of each device of the present embodiment is the same as that of the first embodiment.

  FIG. 21 is a block diagram illustrating a configuration example of the camera 20A.

  The camera 20A includes, for example, a CPU or DSP, ROM, or RAM. The CPU or DSP executes various programs (for example, OS, middleware program, application program) held in the ROM or RAM, and realizes various functions of the camera 20A. For example, the camera 20A downloads, installs, and executes various applications.

  The camera 20A includes, for example, a communication interface for communicating with other communication devices, an input / output interface for inputting / outputting data, and a user interface.

  The camera 20 </ b> A includes a CamApp management unit 21, a control authority management unit 22, a control request reception determination unit 23, a management server authentication unit 24, a communication unit 25, a camera image distribution unit 26, an imaging unit 27, and an application execution unit 28. Therefore, the camera 20 </ b> A does not include the control authority management unit 22 and the control request acceptance determination unit 23. That is, the camera 20A does not determine whether or not the camera 20A can be controlled.

  FIG. 22 is a block diagram illustrating a configuration example of the management server 30A. The management server 30A accumulates CamApp.

  The management server 30A includes, for example, a CPU or DSP, ROM, or RAM. The CPU or DSP executes various programs (for example, OS, middleware program, application program) held in the ROM or RAM, and realizes various functions of the management server 30A.

  In addition, the management server 30A includes, for example, a communication interface for communicating with other communication apparatuses, an input / output interface for inputting / outputting data, and a user interface.

  The management server 30A includes a user management unit 31, a camera management unit 32, an App provider management unit 33, an App management unit 34, an App server authentication unit 35, a contract management unit 36, a control authority management unit 37A, a communication unit 38A, and a CamApp management unit. 39A, a control request acceptance determination unit 39B, and an installed CamApp management unit 39C.

  The control authority management unit 37A manages which CamApp has authority to control which camera 20A the App server 40A has, that is, CamApp control authority. In the first embodiment, the CamApp control authority is determined using the control key. In the second embodiment, the CamApp control authority is determined using the contract information of App corresponding to CamApp. The contract information of App is information related to the contract registered in the table 55A, and includes at least the contract ID.

  The CamApp management unit 39A accumulates and manages CamApp information and CamAppPackage (camera application package) installed in the camera 20A. The CamApp management unit 39A accumulates, for example, CamApp information described later in the table 62.

  The CamApp information and CamAppPackage are registered by the App provider 9 via the input device 14A and the like. The GUI for the registration is transmitted to the PC 10A operated by the App provider 9 by a Web server, for example.

  The control request acceptance determination unit 39B receives the CamApp control request from the App server 40A, refers to the CamApp control authority, and determines whether the CamApp control request is a request from the App server 40A having a legitimate authority. That is, it is determined whether or not the CamApp control request to the camera 20A is within the range of the CamApp control authority permitted to the App server 40A. In the case of the CamApp control request from the legitimate App server 40A, the CamApp management unit 39A instructs the camera 20A to perform processing according to the CamApp control request.

  The control request acceptance determination unit 39B determines, for example, whether or not the App server 40A that has issued the CamApp control request has control authority for the CamApp of the specific camera 20A based on contract information (for example, contract ID) regarding the contract. To do. For example, the control request acceptance determination unit 39B refers to the table 55A in which the contract information is registered. If the contract ID related to the control request is registered in the table 55A, the control request reception determination unit 39B determines that the user has control authority and controls the CamApp. To give permission. On the other hand, for example, the control request acceptance determination unit 39B refers to the table 55A in which the contract information is registered, and determines that there is no control authority when the contract ID related to the control request is not registered in the table 55A. Prohibit control.

  The communication unit 38A communicates various information and data. The communication unit 38A transmits, for example, a CamAppPackage or a CamApp control request (for example, a request for starting, terminating, installing, uninstalling, or updating a CamApp) to the camera 20A.

  FIG. 23 is a block diagram illustrating a configuration example of the App server 40A. The App server 40A accumulates ServerApp.

  The App server 40A includes, for example, a CPU or DSP, ROM, or RAM. The CPU or DSP executes various programs (for example, OS, middleware program, application program) held in the ROM or RAM, and realizes various functions of the App server 40A.

  The App server 40A includes, for example, a communication interface for communicating with other communication devices, an input / output interface for inputting / outputting data, and a user interface.

  The App server 40A includes a control unit 42, a communication unit 45, and a statistical information management unit 46. The communication unit 45 communicates various information and data. For example, the communication unit 45 transmits a CamApp control request (for example, a request for starting, ending, installing, uninstalling, or updating a CamApp) to the management server 30A.

  FIG. 24 is a schematic diagram illustrating an example of registration contents of the table 62 in which the CamApp information managed by the management server 30A according to the second embodiment is registered.

  The table 62 is managed by the CamApp management unit 39A in the management server 30A. In the table 62, for example, CamAppID, CamApp name, AppID, and package file path (PackageFilepath) are registered as CamApp information.

  CamAppID is an example of CamApp identification information. CamApp name is the name of CamApp. AppID is an example of App identification information corresponding to CamApp. The package file path is a path for accessing the storage location of the CamAppPackage file.

  For example, CamAppID: “2201”, CamApp name: “PearleCountCamApp”, AppID: “2101”, and package file path: “/ packageFile / 2201” are registered.

  FIG. 25 is a schematic diagram illustrating an example of registered contents of the table 63 in which installed CamApp information managed by the management server 30A is registered.

  The table 63 is managed by the installed CamApp management unit 39C in the management server 30A. In the table 63, for example, InstalledCamAppID, contract ID, CamAppID, camera ID, and installation ID are registered as installation information.

  InstalledCamAppID is an example of management information for managing CamApp installed in the camera 20A. The contract ID is an example of contract identification information related to CamApp installation. CamAppID is an example of identification information of CamApp installed in the camera 20A. The camera ID is an example of identification information of the camera 20A in which CamApp is installed. The installation ID is an example of identification information for identifying the installation of CamApp, and is acquired from the camera 20A.

  For example, InstalledCamAppID: “3201”, contract ID: “3001”, CamAppID: “2201”, camera ID: “1101”, and installation ID: “0001” are registered.

  FIG. 26 is a schematic diagram illustrating an example of registered contents of the table 55A in which contract information managed by the management server 30A is registered.

  Comparing the table 55A with the table 55 of the first embodiment, the table 55A does not hold the CamApp control key information. The table other than the CamApp control key is the same as the table 55.

  When the table 55A is used, for example, one CamApp control authority exists for each contract. In the present embodiment, the CamApp control authority is generated by registering the contract information in the table 55A. Therefore, it can be said that the control request acceptance determination unit 39B determines the presence or absence of the CamApp control authority based on whether or not the user 7 of the camera 20A has an App contract.

  Further, when the table 55A is used, CamApp control authority may be generated for each contract and each camera. In this case, the control authority management unit 37A generates a CamApp control authority for each contract ID and camera ID held by the camera 20A and the App server 40A. In this case, information related to the CamApp control authority is held in a table 56A shown in FIG. 27 described later.

  FIG. 27 is a schematic diagram illustrating an example of registered contents of the table 56A in which information related to the CamApp control authority managed by the management server 30A is registered. The table 56A is held in the control authority management unit 37A, for example.

  Comparing the table 56A with the table 56 of the first embodiment, the table 56A retains the CamApp control authority ID information instead of the CamApp control key ID, and does not retain the CamApp control key information. The table other than the CamApp control authority ID (CamApp control key ID) and the CamApp control key is the same as the table 56.

  By using the table 55A and the table 56A, one CamApp control authority managed by the control authority management unit 37A is determined for each contract and each camera.

  Further, the user 7 may designate the camera 20A used for each App via the input device 14 or the like. Thereby, the user 7 can permit access to a specific camera 20 </ b> A among the cameras 20 </ b> A owned by the user 7.

  In the example of the table 56A, the App (App server 40A) associated with the contract ID: 3001 is permitted to control CamApp to a total of three cameras 20A identified by the camera IDs: 1101, 1102, and 1103. The App (App server 40A) relating to the contract ID: 3002 is permitted to control CamApp to a total of one camera 20A identified by the camera ID: 1101.

  Security can be further improved by using the table 56A.

  As in the first embodiment, the management server 30A has a table 51 in which user information is registered, a table 52 in which camera information is registered, a table 53 in which App provider information is registered, and a table in which App information is registered. 54 is managed.

  Next, an operation example of the camera system 5A will be described.

  FIG. 28 is a sequence diagram showing an example of App provider registration and App registration procedures by the camera system 5A.

  First, the camera system 5A executes the processes of T11, T12, T3A, T4A, T13, and T14 in FIG.

  After the process of T14, in the PC 10A, when the App provider 9 requests CamApp registration via the input device 14A or the like, the Web browser function unit 12A requests CamApp registration to the management server 30A using the session ID ( T71).

  In this CamApp registration request, the CamApp name, the CamAppPackage, and the AppID held by the App provider PC 10A or input via the input device 14A are transmitted from the PC 10A to the management server 30A.

  In the management server 30A, when the communication unit 38A receives the CamApp registration request, the CamApp management unit 39A performs CamApp registration, and the communication unit 38A transmits CamApp registration completion to the PC 10A (T72). In the CamApp registration, the CamApp management unit 39A attaches a CamAppID based on the CamApp registration request, and stores the CamAppID, the CamApp name from the PC 10A, the AppID corresponding to the CamApp, and the CamAppPackage or its file path in the table 62. When the CamApp registration is completed, CamAppID is returned to the PC 10A.

  Subsequently, when the PC 10A receives various information via the input device 14A or the like, the CamApp management unit 41 sets the various information (T73). This setting information includes, for example, information on AppID, App server authentication key, and CamAppID. For example, various information may be set via a Web browser. Various information may be set by directly logging into a computer on which the App server 40A operates and editing a file.

  When the setting information is set, the App server 40A can access the management server 30A using the AppID and the App server authentication key (T74). The CamApp registered in the management server 30A is controlled by a control request from the App server 40A to the management server 30A using the issued CamAppID. Note that when the App server 40A makes a CamApp control request, the management server 30A is also accessed using the CamAppID.

  According to the App registration procedure shown in FIG. 28, CamApp generated by the App provider 9 can be easily registered in the management server 30A. Further, the management server 30A accumulates and manages CamApp, so that the safety at the time of storage of CamApp can be improved.

  FIG. 29 is a sequence diagram showing an example of an App contract procedure by the camera system 5A.

  First, the camera system 5A performs processes T3, T4, T21 to T26.

  After the process of T26, in the management server 30A, when the communication unit 38A receives the setting information from the PC 10, the control authority management unit 37A generates a CamApp control authority (T27A). The CamApp control authority is generated based on the contract registration by the contract management unit 36 and is managed by the control authority management unit 37A. When the contract management unit 36 registers a contract, the contract information of App is registered in the table 55A (see FIG. 26). This contract information includes a contract ID, a user ID, an AppID, and a contract authentication key. When the contract management unit 36 registers a contract in the table 55A, the control authority management unit 37A generates a CamApp control authority.

  When one CamApp control authority is generated for each contract, information registration in the table 55A is sufficient. However, when a CamApp control authority is generated for each contract and one camera, information registration in the table 56A is performed. Is also done. Specifically, in contract registration, the control authority management unit 37 issues a CamApp control authority ID based on the App contract request and setting information, and stores the contract ID and camera ID in the table 56A.

  After the process of T27A, the management server 30A performs the process of T30.

  Thus, in this embodiment, the CamApp control key is not generated, and the management server 30A manages the CamApp control authority based on the contract information (for example, contract ID).

  FIG. 30 is a sequence diagram illustrating an example of an App usage start procedure by the camera system 5A.

  First, the camera system 5A executes processes T31 and T32.

  After the process of T32, in the management server 30A, when the communication unit 38A receives the request for the contract information, the contract management unit 36 acquires a part or all of the contract information held in the table 55A related to the acquired contract ID. Then, the communication unit 38A transmits the extracted contract information to the App server 40A (T91).

  Subsequently, the camera system 5A executes processes T34 to T37.

  The communication unit 45 transmits the CamAppID and the camera ID specified by the setting information of T37 to the management server 30A, and requests installation of CamApp (T92). This installation request is made to the installation target camera 20A, that is, all the cameras 20A related to the contract or the specific camera 20A. Accordingly, the transmitted camera ID is the camera ID of the installation target camera 20A.

  In the management server 30A, when the communication unit 38A receives a CamApp installation request from the App server 40A, the control request acceptance determination unit 39B determines whether the App server 40A has CamApp control authority. Although details will be described later, the control request acceptance determination unit 39B determines whether or not the contract ID associated with AppID is stored in the table 55A. If there is a contract ID corresponding to the table 55A, it is determined that the user has CamApp control authority, and if there is no contract ID corresponding to the table 55A, it is determined that the user does not have CamApp control authority.

  When one CamApp control authority is generated for each contract, the control request acceptance determination unit 39B only needs to determine whether or not the contract ID acquired from the App server 40A is held in the table 55A. On the other hand, when the CamApp control authority is generated for each contract and each camera, the control request reception determination unit 39B further determines that the contract ID and the camera ID acquired from the App server 40A are one CamApp control authority ID. It is determined whether or not they are stored in the table 56A. In this case, if there is a corresponding CamApp control authority ID, it is determined that it has CamApp control authority, and if there is no corresponding CamApp control authority ID, it is determined that it does not have CamApp control authority.

  The AppID and App server authentication key are added to the request from the App server 40 to the management server 30. The App server 40 exists for each App. The AppID is used by the management server 30 to identify which AppID is an access from the App server 40 associated with the AppID. The App server authentication key is used by the management server 30 to authenticate the App server 40. The same applies to the first embodiment.

  When it is determined that the user has the CamApp control authority, the communication unit 38A transmits the CamAppPackage identified by the CamAppID to the camera 20A identified by the acquired camera ID, and requests the installation of CamApp (T93). . When the management server 30A receives the installation request, the App server authentication unit 35 may authenticate the App server 40A. The management server 30A may determine the presence or absence of the CamApp control authority when it is determined that the App Server 40A is a valid App server as a result of the authentication.

  In the camera 20A to be installed, when the communication unit 25 receives a CamApp installation request, the CamApp management unit 21 issues an installation ID for identifying the CamApp installation, and installs the CamApp using the CamAppPackage. The CamApp management unit 21 stores the installation ID and CamApp in association with each other. When receiving the CamApp installation request, the management server authentication unit 24 may determine whether or not the installation can be set using, for example, a camera control authority control key written when the camera 20A is manufactured. When the installation of CamApp is completed, the communication unit 25 transmits the installation completion to the App server 40A via the management server 30A (T94). The installation completion information includes an installation ID.

  In the management server 30A, when the communication unit 38A receives installation completion information from the camera 20A, the CamApp management unit 39A issues an InstalledCamAppID and registers the installation information in the table 63. The installation information includes InstalledCamAppID, contract ID, CamAppID, camera ID, and installation ID. This installation ID is included in the information of installation completion from the camera 20A.

  When the installation information is registered, the communication unit 38A transmits installation completion information to the App server 40A (T95). This installation completion information includes InstalledCamAppID.

  In the App server 40A, when the communication unit 45 receives the installation completion information from the management server 30A, the communication unit 45 holds the InstalledCamAppID included in the installation completion information in the control unit 42.

  In the App server 40A, the communication unit 45 transmits the stored InstalledCamAppID to the management server 30A to request activation of CamApp (T96).

  In the management server 30A, when the communication unit 38A receives a CamApp activation request from the App server 40A, the control request acceptance determination unit 39B determines whether or not the App server 40A has CamApp control authority. Specifically, the control request acceptance determination unit 39B refers to the table 63 and acquires the contract ID, camera ID, and installation ID associated with the InstalledCamAppID from the App server 40A. The control request acceptance determination unit 39B determines the presence or absence of CamApp control authority depending on whether or not the acquired contract ID is held in the table 55A. If there is a contract ID corresponding to the table 55A, it is determined that the user has CamApp control authority, and if there is no contract ID corresponding to the table 55A, it is determined that the user does not have CamApp control authority. The CamApp control authority is generated and held by the control authority management unit 37A.

  When one CamApp control authority is generated for each contract, the control request acceptance determination unit 39B may determine whether the contract ID is held in the table 55A. On the other hand, when the CamApp control authority is generated for each contract and each camera, the control request reception determination unit 39B holds the contract ID and the camera ID in the table 56A in association with the one CamApp control authority ID. It is determined whether or not. In this case, if there is a corresponding CamApp control authority ID, it is determined that it has CamApp control authority, and if there is no corresponding CamApp control authority ID, it is determined that it does not have CamApp control authority.

  If it is determined that the user has the CamApp control authority, the CamApp management unit 39A transmits the acquired installation ID to the camera 20A identified by the acquired camera ID, and requests the startup of CamApp (T97). ). When the management server 30A receives the activation request, the App server authentication unit 35 may authenticate the App server 40A. The management server 30A may determine the presence or absence of the CamApp control authority when it is determined that the App Server 40A is a valid App server as a result of the authentication.

  In the activation target camera 20A, when the communication unit 25 receives a CamApp activation request from the management server 30A, the application execution unit 28 activates CamApp corresponding to the installation ID. When receiving the activation request for CamApp, the management server authentication unit 24 may determine whether the activation is permitted using, for example, a camera control authority control key written when the camera 20A is manufactured. When the activation is completed, the communication unit 25 transmits the activation completion to the App server 40A via the management server 30A (T98, T99).

  After the completion of the activation of CamApp, the App server 40A executes the process of T45.

  According to the App usage start procedure shown in FIG. 30, which CamApp should be installed in which camera can be designated by the PC 10. For example, the user 7 is the owner of the store 3 (for example, a store or a restaurant), and sufficiently understands which camera image he / she wants to use for what purpose. When the user 7 specifies the installation target camera 20 </ b> A and CamApp using the PC 10, the user 7 can be installed in CamApp reflecting the intention of the user 7.

  Further, the management server 30A can control the App server 40A to safely access via the management server 30A without directly accessing the camera 20A by determining the presence or absence of the CamApp control authority. Thereby, the unauthorized use of CamApp of camera 20A and the modification of CamApp can be suppressed, for example.

  FIG. 31 is a sequence diagram illustrating an example of an App contract cancellation procedure by the camera system 5A.

  First, the camera system 5A executes processes T3, T4, T61 to T63.

  After the process of T63, in the management server 30A, the control authority management unit 37A discards the CamApp control authority corresponding to the acquired contract ID that is held internally. In this case, the contract management unit 36 deletes the contract information corresponding to the acquired contract ID from the table 55A. Further, when the CamApp control authority is generated for each contract and camera, the control authority management unit 37A deletes the information related to the CamApp control authority corresponding to the acquired contract ID from the table 56A.

  In this embodiment, since the camera 20A does not hold the CamApp control key, it is not necessary to request the camera 20A to discard the CamApp control key. Note that the communication unit 25 may request the camera 20A to uninstall the CamApp corresponding to the contract ID to be discarded from the camera 20A.

  Subsequently, the camera system 5A executes the process of T66.

  According to the App contract cancellation procedure shown in FIG. 31, the management server 30A can cancel the CamApp control authority related to the CamApp whose contract has been canceled as the App contract by the camera 20A ends. Therefore, even when the management server 30A acquires a CamApp control request from the App server 40A, the management server 30A can not permit control of CamApp. Therefore, it is possible to suppress the camera 20 </ b> A from being controlled using CamApp after the App contract ends.

  The user registration, camera registration procedure, and App use procedure by the camera system 5A in this embodiment are the same as those in the first embodiment.

  As described above, in the camera system 5A, the management server 30A generates the CamApp control authority and is managed by the management server 30A itself. Therefore, it is not necessary to pass the CamApp control key to both the camera 20A and the App server 40A. Can be prevented from leaking outside. Therefore, the management server 30A can manage the control for CamApp more safely.

  Further, the management server 30A accesses the camera 20A, and the App server 40A does not directly access the camera 20A. Therefore, an event that can occur when the camera 20A is directly connected can be reduced. For example, it is possible to suppress that the camera 20A can be freely controlled. Further, the management server 30 only needs to take measures against communication connection via NAT (Network Address Translation), and the App server 40 does not need to be aware of NAT.

  According to the camera system 5A of the present embodiment as described above, the mechanism in which the App server 40A controls the camera 20A using CamApp can be realized safely and easily for the user.

  In addition, the determination of the presence or absence of the CamApp control authority in the second embodiment may be performed as follows.

(1) At the time of communication from the App server 40A to the management server 30A, the AppID and the App server authentication key are sent.
(2) Subsequently, the management server 30A refers to the table 54 related to App and determines whether or not there is an entry (record) having the sent AppID and App server authentication key at the same time.
(3) The management server 30A refers to the contract-related table 55A, extracts an entry having “Sent AppID”, and creates a list of contract IDs possessed by each entry. If the entry is 0, it is determined that there is no CamApp authority. When one App is contracted by a plurality of users, there are a plurality of contract IDs associated with AppID.

After the process (3), the following (4A), (5A) or (4B), (5B) is performed.

[In the case of CamApp installation instruction (arguments: CamAppID, camera ID)]
(4A) The management server 30A refers to the table 62 related to CamApp and determines whether or not there is an entry having both “CamAppID specified by the argument” and “AppID sent” simultaneously. This process is performed both when setting the control authority for each contract and when setting the control authority for each contract and for each camera.
(5A) When setting the control authority for each contract and for each camera, the management server 30A refers to the table 56A related to the CamApp control authority, and contract IDs and arguments included in the contract ID list created in (3) It is determined whether or not there is an entry having the camera ID specified in (1). When the entry exists, the management server 30A determines that the App server 40A has the CamApp control authority.

[In the case of installed CamApp control instruction (argument: InstalledCamAppID)]
(4B) The management server 30A refers to the table 63 related to the installed CamApp, and there is an entry having both the InstalledCamAppID specified by the argument and the contract ID included in the contract ID list created in (3). It is determined whether or not to do. When the entry exists, the management server 30A acquires the contract ID, CamAppID, and camera ID related to the entry.
(5B) The management server 30A refers to the table 56A related to the CamApp control authority, and whether there is an entry having the contract ID acquired in (4B) and the camera ID acquired in (4B) at the same time. Determine whether or not. When the entry exists, the management server 30A determines that the App server 40A has the CamApp control authority.

  The above (1), (2), and (3) are also divided into a CanApp installation instruction and an installed CamApp control instruction. In the case of a CamApp installation instruction, the arguments are an AppID, an App server authentication key, a MapID, and a camera ID. In the case of an installed CamApp control instruction, the arguments are AppID, App server authentication key, and InstalledCamAppID.

  The management server 30A can determine whether or not there is a CamApp control authority by confirming that there is definitely an App related to the contract by determining whether or not the CamApp control authority exists.

  While various embodiments have been described above with reference to the drawings, it goes without saying that the present invention is not limited to such examples. It will be apparent to those skilled in the art that various changes and modifications can be made within the scope of the claims, and these are naturally within the technical scope of the present invention. Understood.

  In the above-described embodiment, the camera information is acquired from the management server 30 using the contract ID or the like obtained from the user 7 by the App server 40A in FIG. 30, but the present invention is not limited to this. For example, the App server 40A makes a separate contract between the App server 40A and the management server 30A without using the contract ID obtained from the user 7, and manages the camera information based on the separate contract. You may make it acquire from 30A.

  At this time, if the management server 30A manages the contract with the user 7 and the contract with the App server 40A in association with each other, based on the camera information (for example, the camera previously transmitted to the App server 40A) It is also possible to determine whether the App server 40A has the CamApp control authority (depending on whether the information matches the camera information received when the control request is received from the App server 40A).

  For example, the App provider 9 collects metadata from a large number of cameras 20A installed on the sidewalk, collects information for each hour, sex, and age and sells the data to a third party (service) Provided). The App provider 9 can acquire camera information from the management server 30A based on a separate contract concluded between the App server 40A and the management server 30A. Therefore, the App provider 9 can provide the service using the camera 20A without knowing anything about the contract between the user 7 who is the owner of each camera and the management server 30A.

  On the other hand, for the user 7, the CamApp control authority is generated on the management server 30A side based on the contract between the user 7 and the management server 30A, and application control for the camera 20A of the user 7 is managed based on the CamApp control authority. ing. Therefore, safety when the camera 20A is used can be secured.

  As described above, in the imaging system according to the above-described embodiment, the imaging apparatus and the management apparatus that manages control for the application for the imaging apparatus are connected via the network. The management device generates control authority for controlling the application for the imaging device based on the contract for the application for the imaging device and the imaging device, and imaging device identification information for identifying the imaging device for the contract Is transmitted to the control device that makes a control request to the application for the imaging device. The management device acquires a control request and imaging device identification information from the control device, and determines whether the control device has control authority based on the imaging device identification information. When having the control authority, the management device transmits a control request to the imaging device identified by the imaging device identification information. The imaging apparatus receives a control request from the management apparatus, and controls an application for the imaging apparatus according to the control request.

  The imaging system is, for example, a camera system 5A. The imaging device is a camera 20A, for example. The management device is, for example, the management server 30A. The control device is, for example, the App server 40A. The imaging device identification information is, for example, a camera ID. The control authority is, for example, CamApp control authority.

  In this way, by providing a management device that manages control of the application for the imaging device separately from the control device that makes a control request to the application for the imaging device, the control authority is managed without using the control key, Whether or not the control request is acceptable can be performed with high accuracy. For example, it is possible to easily set which control device is to be given control authority for which imaging device application to which imaging device. As described above, a mechanism in which the control device controls the imaging device using the application for the imaging device can be realized safely and easily for the user. In addition, since the control authority is not transferred to other devices, it is possible to suppress leakage of control authority information and improve security.

  In addition, the management device may hold an application for the imaging device. The management device may receive imaging device identification information, a control request, and first identification information for identifying an application for the imaging device from the control device. When the control device has control authority, the management device may transmit the control request and the application for the imaging device identified by the first identification information to the imaging device identified by the imaging device identification information Good. The imaging device identified by the imaging device identification information receives the control request from the management device and the application for the imaging device, and controls the application for the imaging device identified by the first identification information according to the control request. May be. Note that the first identification information is, for example, CamAppID.

  As a result, for example, only a part of the imaging devices owned by the user can be permitted to request a control request to an application for a specific imaging device, and the permission of the control request can be divided for each imaging device.

  Further, the management device generates and holds the control authority for each contract of the application for the imaging device, and whether or not the held imaging device identification information matches the imaging device identification information from the control device, It may be determined whether the control device has control authority.

  Thereby, the control authority according to the contract can be generated, and the application can be controlled in common for each contract.

  In addition, the management device holds the imaging device identification information, generates and holds a control authority for each contract of the imaging device application and each imaging device, and acquires a control request and the imaging device identification information from the control device May be. The management device may determine whether or not the control device has the control authority based on whether or not the held imaging device identification information matches the imaging device identification information from the control device.

  Thereby, the control authority can be generated according to the contract and the imaging device, and application control can be permitted in various variations in consideration of the imaging device.

  The management device may authenticate the control device, and may determine whether the control device has control authority when the authentication is successful.

  Thereby, it can be ensured that the request or instruction from the control device is valid by the management device authenticating the control device.

  Further, the imaging system may include an information processing device that transmits a discard request for discarding the contract to the management device. The discard request may include second identification information for identifying the contract to be discarded. The management device may receive the discard request and discard the control authority in response to the discard request. The second identification information is, for example, a contract ID.

  Accordingly, it is possible to disable the control for the application for the imaging apparatus installed in the imaging apparatus from the control apparatus by a simple process of discarding the control authority held by the management apparatus. Therefore, the management apparatus can suppress controlling the application for the imaging apparatus from the control apparatus after the contract ends.

  The control request may include an application installation request or an activation request for the imaging apparatus.

  As a result, when an application for an imaging device is installed in the imaging device, when an application for the imaging device held by the imaging device is activated, a control request can be rejected if the request is from an inappropriate control device. .

  Further, the imaging device may capture an image, extract a predetermined feature from the captured image, and transmit information about the extracted feature of the captured image to the control device.

  Thereby, the control device can collect the characteristics of each imaging device and analyze statistical information (for example, presence / absence of a specific person, tracking information of a specific person, presence / absence of a specific operation) according to the collected characteristics. .

  In addition, the application control method in the above embodiment is a method in an imaging system in which an imaging device and a management device that manages control for an application for the imaging device are connected via a network. In this method, the management device generates a control authority for controlling the application for the imaging device based on the contract for the application for the imaging device and the imaging device, and the imaging device for the contract is generated by the management device. Imaging device identification information for identification is transmitted to a control device that makes a control request to an application for the imaging device, and the management device acquires a control request and imaging device identification information from the control device. Based on the imaging device identification information, it is determined whether or not the control device has the control authority. When the management device has the control authority, the control request is transmitted to the imaging device identified by the imaging device identification information. Then, the imaging device receives a control request from the management device, and the imaging device controls an application for the imaging device according to the control request.

  In this way, by providing a management device that manages control of the application for the imaging device separately from the control device that makes a control request to the application for the imaging device, the control authority is managed without using the control key, Whether or not the control request is acceptable can be performed with high accuracy. For example, it is possible to easily set which control device is to be given control authority for which imaging device application to which imaging device. As described above, a mechanism in which the control device controls the imaging device using the application for the imaging device can be realized safely and easily for the user. In addition, since the control authority is not transferred to other devices, it is possible to suppress leakage of control authority information and improve security.

  INDUSTRIAL APPLICABILITY The present invention is useful for an imaging system, an application control method, and the like that can improve the safety and operability of application control for an imaging apparatus by a control apparatus that makes a control request to an application.

3 stores 5, 5A camera system 7 users 8 network 9 App provider 10, 10A PC
12, 12A Web browser function unit 14, 14A, 14B Input device 15, 15A Display 20, 20a, 20b, 20c, 20A Camera 21 CamApp management unit 22 Control authority management unit 23 Control request acceptance determination unit 24 Management server authentication unit 25 Communication Unit 26 Camera image distribution unit 27 Imaging unit 28 Application execution unit 30, 30A Management server 31 User management unit 32 Camera management unit 33 App provider management unit 34 App management unit 35 App server authentication unit 36 Contract management unit 37, 37A Control authority management Unit 38, 38A Communication unit 39A CamApp management unit 39B Control request acceptance determination unit 39C Installed CamApp management unit 40, 40A App server 41 CamApp management unit 42 Control unit 45 Communication unit 46 Statistical information management unit 51, 5 2, 53, 54, 55, 62, 63 Table 60 Setting GUI
61, 64 pull-down menu

Claims (9)

An imaging device, and a management device that manages control of the application for the imaging device;
Is an imaging system connected via a network,
The management device
Based on a contract relating to the application for the imaging device and the imaging device, generate a control authority to control the application for the imaging device,
Sending imaging device identification information for identifying the imaging device related to the contract to a control device that makes a control request for an application for the imaging device,
Obtaining the control request and the imaging device identification information from the control device;
It is determined whether or not the control device has the control authority according to whether or not the imaging device identification information transmitted to the control device matches the imaging device identification information acquired from the control device,
If judged that the control device has the controlling authority, the control request acquired from the control device, and transmitted to the imaging apparatus identified by the imaging device identification information,
The imaging device
Receiving the control request from the control device via the management device;
An imaging system that controls an application for the imaging apparatus in response to the control request. The imaging system according to claim 1,
The management device
Holding an application for the imaging device;
Receiving the imaging device identification information, the control request, and first identification information for identifying an application for the imaging device from the control device;
When the control device has the control authority, the control request and the application for the imaging device identified by the first identification information are transmitted to the imaging device identified by the imaging device identification information.
The imaging device identified by the imaging device identification information is
Receiving the control request and the application for the imaging device from the management device;
An imaging system for controlling an application for the imaging apparatus identified by the first identification information in response to the control request. The imaging system according to claim 1,
The management device
Generating the control authority for each contract of the application for the imaging device ;
Imaging system. The imaging system according to claim 2,
The management device
Holding the imaging device identification information;
Generate the control authority for each contract of the application for the imaging device and for each imaging device,
Obtaining the control request and the imaging device identification information from the control device;
An imaging system that determines whether or not the control device has the control authority based on whether or not the held imaging device identification information matches the imaging device identification information from the control device. The imaging system according to any one of claims 1 to 4,
The management apparatus authenticates the control device, and determines whether the control device has the control authority when the authentication is successful. The imaging system according to any one of claims 1 to 5, further comprising:
An information processing device that transmits a discard request for discarding the contract to the management device;
The discard request includes second identification information for identifying a contract to be discarded,
The management device
Receiving the discard request;
An imaging system that discards the control authority in response to the discard request. The imaging system according to any one of claims 1 to 6,
The imaging device
Receiving an application for the imaging device from the control device;
The imaging system, wherein the control request includes an installation request or activation request for an application for the imaging device. The imaging system according to any one of claims 1 to 7,
The imaging device
Take an image,
Extract the specified features from the captured image,
An imaging system that transmits information about the characteristics of the extracted captured image to the control device. An imaging device, and a management device that manages control of the application for the imaging device;
Is an application control method in an imaging system connected via a network,
Based on a contract related to the imaging device application and the imaging device, the management device generates a control authority to control the imaging device application,
The management device transmits imaging device identification information for identifying the imaging device related to the contract to a control device that makes a control request for the application for the imaging device,
The management device acquires the control request and the imaging device identification information from the control device,
It is determined whether or not the control device has the control authority according to whether or not the imaging device identification information transmitted to the control device matches the imaging device identification information acquired from the control device,
Wherein the management device, when the control device is determined to have the controlling authority, the control request, and sends to the image sensing apparatus identified by the imaging device identification information,
The imaging device receives the control request from the control device via the management device,
An application control method in which an application for the imaging apparatus is controlled by the imaging apparatus in response to the control request.

Images