Surveillance camera video sharing system and surveillance camera video sharing method

Abstract

To provide a monitor camera video sharing system and a monitor camera video sharing method that make it efficient to share data on video of at least one monitor camera.SOLUTION: A monitor camera video sharing system comprises: one or more user terminals for browsing video data of a plurality of monitor cameras disposed at an object facility; and a server for preserving access permission data including first user information having an access right to the video data of the monitor cameras and monitor camera information showing information on at least one selected monitor camera selected by user terminal operation based on the first user information. On the basis of sharing processing on the access permission data to second user information by user terminal operation based on the first user information, the server adds an access right to video data of the selected monitor camera to the second user information and updates the access permission data to be accessible by a user terminal based on the second user information.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to a surveillance camera video sharing system and a surveillance camera video sharing method. [Background technology]

[0002] Patent Document 1 discloses a system including a surveillance camera that communicates with an external terminal and an image management server that communicates with the external terminal and the surveillance camera. When the external terminal requests image data from a surveillance camera that belongs to a group to which the surveillance camera belongs, the image management server transmits to the external terminal an electronic file that includes connection information for acquiring image data from the surveillance camera that belongs to the group. This connection information is, for example, link information such as a uniform resource locator (URL) of the image data. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-116125 Summary of the Invention [Problem to be solved by the invention]

[0004] In the configuration of Patent Document 1, an external terminal cannot acquire image data from a series of surveillance cameras belonging to a certain group unless it requests image data from the surveillance cameras belonging to that group and obtains connection information (in other words, information on the authority to acquire image data from other surveillance cameras belonging to that group) in response to the request. Therefore, in an environment where multiple surveillance cameras are installed, not only is corresponding connection information required to acquire image data from each surveillance camera, but administrators also face the problem of making incorrect settings when setting authority for each surveillance camera one by one. Therefore, it is difficult to efficiently share image data from surveillance cameras belonging to a certain group with external terminals, and there is room for improvement.

[0005] The present disclosure has been devised in view of the above-described conventional circumstances, and aims to provide a surveillance camera video sharing system and a surveillance camera video sharing method that improve the efficiency of data sharing of video from at least one surveillance camera. [Means for solving the problem]

[0006] The present disclosure relates to one or more user terminals for viewing video data from a plurality of surveillance cameras installed in a target facility, first user information having access rights to the video data from the surveillance cameras, and a system for accessing the first user information. Link and a server that stores access permission data including at least the first user information and the second user information. Link Sharing the access permission data to second user information by operating the user terminal operation Based on the second user information, an access right to the access permission data; Access authority to the video data of the selected surveillance camera and and updating the access permission data by adding the video data of the selected surveillance camera specified by the surveillance camera information linked to the access permission data. the user terminal associated with the first user information; The second user information LinkA surveillance camera video sharing system is provided that is set to be accessible by the user terminal.

[0007] The present disclosure also provides a method for obtaining a first user who has access rights to video data from a plurality of surveillance cameras installed in a target facility, and a method for obtaining a first user who has access rights to video data from a plurality of surveillance cameras installed in a target facility. Link and monitoring camera information indicating information of at least one selected monitoring camera selected by operation of the user terminal. Link Sharing the access permission data to second user information by operating the user terminal operation Based on the second user information, an access right to the access permission data; adding an access right to the video data of the selected surveillance camera to update the access permission data, and accessing the video data of the selected surveillance camera specified by the surveillance camera information linked to the access permission data; the user terminal associated with the first user information; The second user information Link A surveillance camera video sharing method is provided, in which the video is set to be accessible by the user terminal.

[0008] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium. [Effects of the Invention]

[0009] According to the present disclosure, it is possible to improve the efficiency of data sharing of video from at least one surveillance camera.

[0010] Further advantages and benefits of certain aspects of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some of the embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features. [Brief explanation of the drawings]

[0011] [Figure 1] A diagram showing an example of the system configuration of a surveillance camera system. [Figure 2] Block diagram showing an example of hardware configuration for the device management server, database server, and user management server [Figure 3] FIG. 10 is a diagram showing an outline of an operation according to a first operation example. [Figure 4] FIG. 10 shows an example of screen transitions displayed on the terminals of users U1 and U2 according to the first operation example. [Figure 5] A sequence diagram showing the operation procedure of the favorite data creation process according to the first operation example in chronological order. [Figure 6] FIG. 10 is a sequence diagram showing the operation procedure of the favorite data sharing process according to the first operation example in chronological order. [Figure 7] FIG. 10 is a diagram showing an outline of an operation according to a second operation example. [Figure 8] FIG. 10 shows an example of screen transitions displayed on the terminals of users U1 and U2 according to a second operation example. [Figure 9] A sequence diagram showing the operation procedure of the favorite data creation process according to the second operation example in chronological order. [Figure 10] A sequence diagram showing the operation procedure of the favorite data sharing process according to the second operation example in chronological order. [Figure 11] FIG. 10 is a diagram showing an outline of an operation according to a third operation example. [Figure 12] FIG. 10 shows an example of screen transitions displayed on the terminals of users U1 and U2 according to the third operation example. [Figure 13] A sequence diagram showing the operation procedure of the favorite data sharing process according to the third operation example in chronological order. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, with reference to the drawings as appropriate, a detailed description of an embodiment specifically disclosing a surveillance camera video sharing system and a surveillance camera video sharing method according to the present disclosure will be described in detail. However, more detailed description than necessary may be omitted. For example, detailed description of well-known matters or redundant description of substantially identical configurations may be omitted. This is to avoid unnecessary redundancy in the following description and to facilitate understanding by those skilled in the art. Note that the accompanying drawings and the following description are provided to enable those skilled in the art to fully understand the present disclosure and are not intended to limit the subject matter recited in the claims.

[0013] (System configuration example) Fig. 1 is a diagram showing an example of the system configuration of a surveillance camera system 100. As shown in Fig. 1, surveillance camera system 100 (an example of a surveillance camera video sharing system) includes at least a client terminal PC1 (an example of a first user terminal), a DB server S1 (an example of a server), a device management server S2 (an example of a server), and a user management server S3 (an example of a server). Note that DB server S1, device management server S2, and user management server S3 are not necessarily required individually, and one or more servers having the functions of each server may be configured.

[0014] The surveillance camera system 100 may further include a mobile terminal TB1 (an example of a second user terminal) and a distribution control server S4. The client terminal PC1 and the mobile terminal TB1 are each connected to the DB server S1, the device management server S2, the user management server S3, and the distribution control server S4 via the network NW2 so as to be able to communicate data with each other.

[0015] Furthermore, the surveillance camera system 100 may further include surveillance cameras Ca1, Ca2, ... and a recorder RD that are installed in a target facility (for example, store A), and surveillance cameras Cb1, Cb2, ... that are installed in a target facility (for example, store B). The surveillance cameras Ca1, Ca2, ... and the recorder RD as well as the surveillance cameras Cb1, Cb2 are connected to the distribution control server S4 via the network NW1 so as to be able to communicate data with each other.

[0016] The networks NW1 and NW2 are, for example, wireless networks conforming to a wireless LAN (Local Area Network) such as Wi-Fi (registered trademark), a cellular mobile communication system such as 4G or 5G, Bluetooth (registered trademark), or WiGig (Wireless Gigabit), but are not limited to these. The networks NW1 and NW2 may also be wired networks such as a USB (Universal Serial Bus) cable or a wired LAN. In the following description, the video data captured by the surveillance cameras Ca1, Ca2, Cb1, Cb2, ... includes not only the video data but also identification information of the surveillance cameras that captured the video data and information on the date and time of capture.

[0017] The surveillance camera system 100 allows remote viewing (e.g., viewing or playback; the same applies below) of video data captured by surveillance cameras Ca1 and Ca2 installed in a target facility (e.g., store A) from at least one of client terminal PC1 and mobile terminal TB1 for monitoring purposes. Similarly, the surveillance camera system 100 allows remote viewing (e.g., viewing or playback) of video data captured by surveillance cameras Cb1 and Cb2 installed in a target facility (e.g., store B) from at least one of client terminal PC1 and mobile terminal TB1 for monitoring purposes. Note that while a store is given as an example of a target facility, facilities other than stores (e.g., shopping malls, office buildings), or multiple stores may also be considered as a single facility.

[0018] Furthermore, when a client terminal PC1 used by user U1 performs an operation to share favorite data (an example of access permission data) of a surveillance camera with another user (e.g., user U2), the surveillance camera system 100 executes a sharing process based on the sharing operation to enable the mobile terminal TB1 specified in the sharing operation to access the video data of the surveillance camera identified by the favorite data. Details of this sharing process will be described later with reference to the accompanying drawings from FIG. 3 onwards.

[0019] Each of the surveillance cameras Ca1, Ca2, ... is positioned so as to be able to capture the area to be monitored within store A, and captures video data showing a subject (for example, a person present in store A, or an area of ​​store A that should be noted). This captured video data is recorded in a memory (not shown) within each of the surveillance cameras Ca1, Ca2, ..., and may be sent to and stored in a recorder RD, or may be sent directly to the distribution control server S4 via the network NW1. Note that the subject may be an element other than the person or area described above, and the same applies below.

[0020] The recorder RD has a storage (not shown) and receives video data of subjects captured by each of the surveillance cameras Ca1, Ca2, ... located within store A from each of the surveillance cameras Ca1, Ca2, ..., and stores it in the storage (see above), and may also transmit it intermittently or periodically to the distribution control server S4.

[0021] Each of the surveillance cameras Cb1, Cb2, ... is positioned so as to be able to capture an area to be monitored within store B, and captures video data showing a subject (for example, a person present in store B, or an area of ​​store B that should be noted). This captured video data may be recorded in a memory (not shown) within each of the surveillance cameras Ca1, Ca2, ..., and may also be sent directly to the distribution control server S4 via the network NW1. Note that, to simplify the illustration in FIG. 1, store B is shown as not including a recorder RD, but store B may also be provided with a recorder RD.

[0022] The client terminal PC1 is, for example, a personal computer used by a user U1. The client terminal PC1 communicates data with the DB server S1, the device management server S2, the user management server S3, and the distribution control server S4 via the network NW2. In the following description, the user U1 is the person who performs the sharing operation of the favorite data of the surveillance camera and has the authority to access the video data of the surveillance camera identified by that favorite data. The client terminal PC1, operated by the user U1, sends a request for the sharing process of the favorite data of the surveillance camera to the device management server S2 or the user management server S3.

[0023] The mobile terminal TB1 is, for example, a mobile phone, smartphone, or tablet terminal, and is used by a user U2. The mobile terminal TB1 communicates data with the DB server S1, the device management server S2, the user management server S3, and the distribution control server S4 via the network NW2. In the following description, the user U2 is the person with whom the favorite data of the surveillance camera is shared, and is the person who only gains access rights to the video data of the surveillance camera identified by the favorite data of the user U1 through the sharing operation of the user U1. The mobile terminal TB1 becomes able to access the video data of the surveillance camera identified by the favorite data of the surveillance camera through a sharing process (see below) based on the operation of the user U1.

[0024] The DB server S1 is configured, for example, by a server computer, and has a database DB that stores various setting information data for each device (e.g., surveillance camera, recorder) to be monitored by the surveillance camera system 100, and various setting information data for each user who is registered as being able to use the surveillance camera system 100 (see FIG. 2). The DB server S1 references the database DB and responds with data in response to a request from the device management server S2 or the user management server S3. The various setting information for each device includes, for example, the name of the device, its identification number, the date and time when placement (in other words, installation) in the target facility was completed, the name of the target facility where the device is placed (e.g., Store A), and license information indicating usage rights such as remote viewing (e.g., license expiration date), but is not limited to these. The various setting information for each user includes, for example, the user's name, the login ID (IDentification) and password that the user is required to enter when using (in other words, logging in to) the surveillance camera system 100, the expiration date of the login ID and password, and the user's authority (for example, store manager authority with the same authority as a supervisor, store clerk authority with the same authority as a general user, and access authority to video data from the surveillance camera provided for each surveillance camera), but is not limited to these. A detailed example of the hardware configuration of DB server S1 will be described later with reference to FIG. 2.

[0025] The device management server S2 is, for example, configured as a server computer, and executes processing for handling various setting information or favorite data for each device monitored by the surveillance camera system 100 through data communication with the DB server S1. For example, when the device management server S2 receives favorite data (see below) from the client terminal PC1 or the mobile terminal TB1, it adds the favorite data to the DB server S1 or instructs the DB server S1 to change (e.g., add, change, or delete) the setting information data of the surveillance camera (hereinafter referred to as "favorite-linked camera data") linked to (or corresponding to) the favorite data. Based on this instruction, the DB server S1 changes the corresponding favorite-linked camera data. Furthermore, the device management server S2 requests the DB server S1 to update the favorite-data-linked camera data based on the operation of the client terminal PC1 or the mobile terminal TB1. Furthermore, the device management server S2 requests and acquires camera data identified by the camera data linked to the favorite data (i.e., data on the setting information of the surveillance camera linked to the favorite data) from the DB server S1 based on the operation of the client terminal PC1 or the mobile terminal TB1. A detailed example of the hardware configuration of the device management server S2 will be described later with reference to FIG.

[0026] The user management server S3 is, for example, configured by a server computer, and executes processing for handling various setting information or favorite data for each user registered as being able to use the surveillance camera system 100 through data communication with the DB server S1. For example, when the user management server S3 receives a request from the client terminal PC1 or the mobile terminal TB1 to change (e.g., add, change, or delete) the setting information data (hereinafter referred to as "favorite access user data") of a user who can access favorite data (see below), the user management server S3 instructs the DB server S1 to change the favorite access user data based on the request. The DB server S1 changes the corresponding favorite access user data based on this instruction. Furthermore, when the user management server S3 receives a request to change (e.g., add, change, or delete) the setting information data (hereinafter referred to as "camera access user data") of a user who can access a surveillance camera linked to the favorite data, the user management server S3 instructs the DB server S1 to change the camera access user data based on the request. The DB server S1 changes the corresponding camera access user data based on this instruction. Similarly to the device management server S2, when the user management server S3 receives favorite data (see below) from the client terminal PC1 or the mobile terminal TB1, the user management server S3 may add the favorite data to the DB server S1. A detailed example of the hardware configuration of the user management server S3 will be described later with reference to FIG.

[0027] The distribution control server S4 is configured, for example, by a server computer, and acquires and references license information for each device (e.g., surveillance camera, recorder) monitored by the surveillance camera system 100 from the DB server S1, and determines whether the client terminal PC1 or the mobile terminal TB1 is permitted to view the video data. If the distribution control server S4 determines that the license for the device being determined (e.g., surveillance camera Ca1) is valid (i.e., the license expiration date has not yet passed), it determines that the client terminal PC1 or the mobile terminal TB1 is permitted to view the video data captured by the surveillance camera Ca1. On the other hand, if the distribution control server S4 determines that the license for the device being determined (e.g., surveillance camera Ca1) is invalid (i.e., the license expiration date has passed) and the license has not been updated, it determines that the client terminal PC1 or the mobile terminal TB1 is prohibited from viewing the video data captured by the surveillance camera Ca1.

[0028] (Example of hardware configuration) 2 is a block diagram showing an example of the hardware configuration of the device management server S2, DB server S1, and user management server S3. Except for the fact that DB server S1 has a database DB1, the device management server S2, DB server S1, and user management server S3 have similar hardware configurations. It is also possible to eliminate the DB server S1 and have other servers (i.e., the device management server S2 and the user management server S3) each hold the database DB1 and have the functions and data to manage the held database DB1. The device management server S2, DB server S1, and user management server S3 are connected to each other so that they can communicate data using a wired network such as a wired LAN.

[0029] The DB server S1 includes a communication device 21, a processor 22, a memory 23, and a database DB1. Note that in the accompanying drawings, the interface is abbreviated as "IF" for convenience.

[0030] The communication device 21 performs data communication (i.e., data transmission and reception) with the device management server S2 or the user management server S3 connected via the above-mentioned wired network (e.g., wired LAN). When the communication device 21 receives a request from the device management server S2 or the user management server S3, the communication device 21 returns an acknowledgement (hereinafter abbreviated as "Ack") to the device management server S2 or the user management server S3 indicating that the processor 22 has executed the request. Note that the communication device 21 may also execute data saving or reading processes directly with the memory 23 without going through the processor 22.

[0031] The processor 22 is configured using, for example, a CPU (Central Processing Unit), a DSP (Digital Signal Processor), a GPU (Graphical Processing Unit), or an FPGA (Field Programmable Gate Array). The processor 22 functions as a controller that manages the overall operation of the DB server S1, and performs control processing for managing the operations of each part of the DB server S1, data input / output processing between each part of the DB server S1, data arithmetic processing, and data storage processing. The processor 22 operates in accordance with programs and data stored in the memory 23. The processor 22 uses the memory 23 during operation, and temporarily stores data or information (including Ack) created or acquired by the processor 22 in the memory 23 or sends it to the communication device 21. Specific examples of processing performed by the processor 22 will be described with reference to the accompanying drawings from FIG. 3 onwards.

[0032] The memory 23 is configured using, for example, RAM (Random Access Memory) and ROM (Read Only Memory), and temporarily stores programs required to execute the operations of the DB server S1, as well as data or information created during operation. The RAM is a work memory used when the DB server S1 is operating. The ROM pre-stores and saves programs and data for controlling the DB server S1.

[0033] Database DB1 is configured using a storage medium (for example, a flash memory, a hard disk drive (HDD), or a solid state drive (SSD)). Database DB1 stores various setting information (see above) data for each device (for example, a surveillance camera, a recorder) that is the target of monitoring by surveillance camera system 100, various setting information (see above) data for each user who is registered as being able to use surveillance camera system 100, and various data related to favorite data.

[0034] The various data related to favorite data include, for example, favorite data, camera data linked to favorites, favorite access user data, and camera access user data.

[0035] The favorite data is data configured using at least one of favorite-linked camera data, favorite-access user data, and camera-access user data. More specifically, the favorite data is data including setting information of a target facility (e.g., a store) selected as a target for remote monitoring by a user of the surveillance camera system 100 (in other words, a user who can access the favorite data), setting information (see above) of the equipment (e.g., surveillance cameras) installed in the target facility, and setting information (see above) of users who can access the favorite data.

[0036] The favorite-linked camera data is data that constitutes the favorite data, and is the setting information (see above) of the surveillance cameras that are the subject of monitoring viewing by accessing the favorite data. For example, if user U1 creates favorite data to include the setting information of surveillance cameras Ca1 and Ca2 in store A (see FIG. 3), the favorite-linked camera data that constitutes the favorite data will be the setting information (e.g., names) of surveillance cameras Ca1 and Ca2.

[0037] The favorite access user data is data constituting the favorite data, and is data of the setting information (see above) of users who can access the favorite data. For example, if the favorite data is created so that user U1 can access it (see step St1 in FIG. 3), the favorite access user data constituting the favorite data will be the setting information (e.g., name) of user U1. Also, if user U1 performs a sharing operation on the favorite data so that user U2 can also access it (see step St2 in FIG. 3), the favorite access user data constituting the favorite data will be the setting information (e.g., name) of each of users U1 and U2.

[0038] The camera access user data is data constituting the favorite data, and is the setting information (see above) data of the user who can access the video data of the surveillance camera specified by the favorite-linked camera data. For example, when the user U1 performs an operation so that the user U2 can newly access the video data of the surveillance camera specified by the favorite-linked camera data (see step St2 in FIG. 3), the DB server S1 creates camera access data consisting of the setting information of the surveillance camera and the setting information of the new user U2.

[0039] The device management server S2 includes a communication device 31, a processor 32, and a memory 33.

[0040] The communication device 31 performs data communication (i.e., sending and receiving data) with the DB server S1 connected via the above-mentioned wired network (for example, a wired LAN). The communication device 31 performs data communication with the client terminal PC1 or the mobile terminal TB2 connected via the network NW2. When the communication device 31 receives a request from the client terminal PC1 or the mobile terminal TB1, the communication device 31 returns a response (Ack) to the client terminal PC1 or the mobile terminal TB1 indicating that the processor 32 has executed the operation with the DB server S1 based on the request. Note that the communication device 31 may also execute the process of saving or reading data directly with the memory 33 without going through the processor 32.

[0041] The processor 32 is configured using, for example, a CPU, DSP, GPU, or FPGA. The processor 32 functions as a controller that manages the overall operation of the device management server S2, and performs control processing for managing the operations of each unit of the device management server S2, data input / output processing between each unit of the device management server S2, data arithmetic processing, and data storage processing. The processor 32 operates according to programs and data stored in the memory 33. The processor 32 uses the memory 33 during operation, and temporarily stores data or information (including ACKs) created or acquired by the processor 32 in the memory 33 or sends them to the communication device 31. Specific examples of the processing performed by the processor 32 will be described with reference to the accompanying drawings from FIG. 3 onwards.

[0042] The memory 33 is configured using, for example, RAM and ROM, and temporarily stores programs necessary for executing the operation of the device management server S2, as well as data or information created during operation. The RAM is a work memory used when the device management server S2 is operating. The ROM pre-stores and saves programs and data for controlling the device management server S2.

[0043] The user management server S3 includes a communication device 41, a processor 42, and a memory 43.

[0044] The communication device 41 performs data communication (i.e., sending and receiving data) with the DB server S1 connected via the above-mentioned wired network (for example, a wired LAN). The communication device 41 performs data communication with the client terminal PC1 or the mobile terminal TB2 connected via the network NW2. When the communication device 41 receives a request from the client terminal PC1 or the mobile terminal TB1, the communication device 41 returns a response (Ack) to the client terminal PC1 or the mobile terminal TB1 indicating that the processor 42 has executed the operation with the DB server S1 based on the request. Note that the communication device 41 may also execute the process of saving or reading data directly with the memory 43 without going through the processor 42.

[0045] The processor 42 is configured using, for example, a CPU, DSP, GPU, or FPGA. The processor 42 functions as a controller that manages the overall operation of the user management server S3, and performs control processing to integrate the operation of each part of the user management server S3, data input / output processing between each part of the user management server S3, data arithmetic processing, and data storage processing. The processor 42 operates in accordance with programs and data stored in the memory 43. The processor 42 uses the memory 43 during operation, and temporarily stores data or information (including Ack) created or acquired by the processor 42 in the memory 43 or sends it to the communication device 41. Specific examples of the processing performed by the processor 42 will be described with reference to the accompanying drawings from FIG. 3 onwards.

[0046] The memory 43 is configured using, for example, RAM and ROM, and temporarily stores programs necessary for executing the operations of the user management server S3, as well as data or information created during operation. The RAM is a work memory used when the user management server S3 is operating. The ROM pre-stores and saves programs and data for controlling the user management server S3.

[0047] (First operation example) Next, an outline of a first operation example of the favorite data sharing process of the surveillance camera system 100 according to the first embodiment will be described with reference to Fig. 3. Fig. 3 is a diagram showing an outline of the operation according to the first operation example. In the first operation example, the favorite data Dt1 is data common to users U1 and U2 of the surveillance camera system 100, and is not provided for each user.

[0048] As shown in Figure 3, for example, a user U1 is pre-registered as a user of the surveillance camera system 100, and a newly registered user U2 is set to be able to access the surveillance cameras Ca1 and Ca2 of store A, which are linked to the favorite data Dt1 created by user U1.

[0049] (St1) User U1 is set up to be able to remotely view video data from surveillance cameras (e.g., four surveillance cameras Ca1, Ca2, Ca3, and Ca4) installed in store A. That is, user U1's setting information (e.g., authority) grants him / her the authority to access the video data from each of the surveillance cameras Ca1, Ca2, Ca3, and Ca4 installed in store A. The client terminal PC1 used by user U1 is an example of a user terminal that is permitted to log in to the surveillance camera system 100 as user U1 based on user U1's setting information (e.g., login ID and password), and so on. This client terminal PC1, through user U1's operation, creates favorite data Dt1, which includes data on the setting information for the surveillance cameras Ca1 and Ca2 in store A. This favorite data Dt1 is data that serves as authority to access video data from the surveillance cameras Ca1 and Ca2 (examples of selected surveillance cameras) in store A selected by user U1. While the creation of favorite data Dt1 has been described above, the client terminal PC1 can also edit or delete favorite data Dt1 through user U1's operation.

[0050] (St2) In response to the sharing operation of user U1, client terminal PC1 executes a sharing process to share the favorite data Dt1 created in step St1 with user U2. Note that the mobile terminal TB1 used by user U2 is an example in which user U2 is permitted to log in to the surveillance camera system 100 as user U2 based on the user U2's setting information (e.g., login ID and password), and similarly applies below. As a result, the mobile terminal TB1 used by user U2 can acquire the favorite data Dt1, and can access the video data of surveillance cameras Ca1 and Ca2 in store A identified by this favorite data Dt1, enabling remote viewing.

[0051] (St3) By sharing the favorite data Dt1, user U2 is now set up to be able to remotely view the video data from the surveillance cameras Ca1 and Ca2 located in store A. The mobile terminal TB1 used by user U2 (i.e., permitted to log in as user U2 based on the setting information of user U2) can edit or delete the favorite data Dt1 through operations by user U2.

[0052] 4 is a diagram showing an example of screen transitions displayed on the terminals of users U1 and U2 according to the first operation example. In FIG. 4, the surveillance camera is simply abbreviated as camera.

[0053] 3, the client terminal PC1 used by user U1 (i.e., permitted to log in as user U1 based on the setting information of user U1) displays thumbnails Thm1, Thm2, Thm3, and Thm4 on the camera list screen WD1, indicating that video data from surveillance cameras Ca1, Ca2, Ca3, and Ca4 located in store A can be remotely viewed. In addition, in response to the creation of favorite data Dt1, the client terminal PC1 displays thumbnails Thm1f and Thm2f on the favorite screen WD2, indicating the contents of favorite data Dt1 (e.g., that video data from surveillance cameras Ca1 and Ca2 located in store A can be remotely viewed).

[0054] On the other hand, in the initial state Cn21 of the mobile terminal TB1, which corresponds to step St1 in Figure 3, the mobile terminal TB1 used by user U2 (i.e., allowed to log in as user U2 based on the setting information of user U2) displays a camera list screen WD3 and a favorite screen WD4 that do not display thumbnails of surveillance cameras, because the sharing process of the favorite data Dt1 has not yet been executed and no surveillance cameras that the mobile terminal TB1 can access have been set.

[0055] For example, it is assumed that the user U1 performs an operation to share the favorite data Dt1 with the user U2, corresponding to step St2 in FIG. 3 (St11).

[0056] In state Cn22 of the mobile terminal TB1, the mobile terminal TB1 is able to access the favorite data Dt1 (in other words, access the video data of the surveillance cameras Ca1 and Ca2 installed in store A) through the sharing process (see FIG. 6) based on the sharing operation of the favorite data Dt1 in step St11. Therefore, the mobile terminal TB1 updates the display of thumbnails Thm1 and Thm2, which indicate that the video data of the surveillance cameras Ca1 and Ca2 installed in store A can be remotely viewed, on the camera list screen WD3. In addition, the mobile terminal TB1 updates the display of thumbnails Thm1f and Thm2f, which indicate the contents of the favorite data Dt1 (for example, that the video data of the surveillance cameras Ca1 and Ca2 installed in store A can be remotely viewed), on the favorite screen WD4.

[0057] For example, suppose that user U2 performs an editing operation on favorite data Dt1 (e.g., an operation to delete surveillance camera Ca2) (St12) corresponding to step St3 in Fig. 3. Note that this deletion of surveillance camera Ca2 corresponds to, for example, deleting the setting information data of surveillance camera Ca2 in the favorite-linked camera data constituting favorite data Dt1.

[0058] In state Cn23 of the mobile terminal TB1, the mobile terminal TB1 updates the display of the favorites screen WD4 by deleting the thumbnail Thm2f from the favorites screen WD4 through the editing operation of the favorites data Dt1 in step St12. As a result of this display update, only the thumbnail Thm1f of the surveillance camera Ca1 is displayed on the favorites screen WD4. Furthermore, the mobile terminal TB1 sends a notification (deletion notification) to the device management server S2 that the surveillance camera Ca2 has been deleted from the favorites data Dt1 in step St12 (St13). Upon receiving this deletion notification, the device management server S2 forwards the deletion notification to the client terminal PC1 and also sends an instruction to the DB server S1 to delete the setting information data of the surveillance camera Ca2 from the favorites-linked camera data constituting the favorites data Dt1. Based on the instruction from the device management server S2, the DB server S1 deletes the setting information data of the surveillance camera Ca2 from the favorites-linked camera data constituting the favorites data Dt1.

[0059] In the state Cn12 of the client terminal PC1, when the client terminal PC1 receives a deletion notification from the device management server S2, the client terminal PC1 deletes the thumbnail Thm2f of the favorites screen WD2 in the initial state Cn11, thereby updating the display of the favorites screen WD2.

[0060] Fig. 5 is a sequence diagram showing the operation procedure of the favorite data creation process according to the first operation example in chronological order. Fig. 6 is a sequence diagram showing the operation procedure of the favorite data sharing process according to the first operation example in chronological order. In the explanations of Fig. 5 and Fig. 6, the processing performed by each server is mainly executed by the processor possessed by that server. In the explanation of Fig. 6, the same step numbers are assigned to processes that overlap with the explanation of Fig. 5, and explanations are simplified or omitted, and different contents are explained.

[0061] 5, in response to an operation by user U1, client terminal PC1 displays a favorites screen (St21), selects surveillance cameras Ca1 and Ca2 located in store A, and creates favorites data with a role of authority that enables access to the video data of each of the selected surveillance cameras Ca1 and Ca2 (St22). The client terminal PC1 requests the device management server S2 to add the favorites data of store A created in step St22 (St23). In response to the request in step St23, the device management server S2 instructs the DB server S1 to add the favorites data of store A created in step St22 (St24). In response to this instruction, the DB server S1 adds the favorites data of store A to database DB1. An Ack is returned to the device management server S2 to indicate that the favorites data of store A has been added to database DB1.

[0062] Based on the Ack received from the DB server S1, the device management server S2 instructs the DB server S1 to add the setting information data for the surveillance cameras Ca1 and Ca2 to the favorites-linked camera data that constitutes the favorites data for store A (St25). In accordance with this instruction, the DB server S1 adds the favorites-linked camera data Dt2 to which the setting information data for the surveillance cameras Ca1 and Ca2 has been added to the database DB1 in order to configure (create) the favorites data for store A. An Ack indicating that the favorites-linked camera data Dt2 has been added to the database DB1 is returned to the device management server S2 and the client terminal PC1.

[0063] Based on the Ack received from the DB server S1, the client terminal PC1 requests the user management server S3 to add the setting information data of user U1 to the favorite access user data constituting the favorite data of store A (St26). In response to the request in step St26, the user management server S3 instructs the DB server S1 to add the setting information data of user U1 to the favorite access user data constituting the favorite data of store A (St27). In accordance with this instruction, the DB server S1 adds the favorite access user data Dt3 to which the setting information data of user U1 has been added to the database DB1 to constitute the favorite data of store A. An Ack indicating that the favorite access user data Dt3 has been added to the database DB1 is returned to the user management server S3 and the client terminal PC1. As a result, the client terminal PC1 has completed registering the favorite data having the role of authority to access the video data of the surveillance cameras Ca1 and Ca2 installed in store A in the database DB1.

[0064] 6, in response to an operation by user U1, client terminal PC1 executes a sharing operation on the favorites screen (see FIG. 5) displayed in step St21 to share with user U2 favorite data having the authority to access video data from surveillance cameras Ca1 and Ca2 installed in store A (St31). The client terminal PC1 requests device management server S2 to acquire device data (i.e., device setting information data) associated with the favorite data that is the target of the sharing operation executed in step St31 (St32). In response to the request in step St32, device management server S2 instructs DB server S1 to request camera data associated with favorites that constitutes the favorite data that is the target of the sharing operation (St33). In response to this instruction, DB server S1 returns the camera data associated with favorites that constitutes the favorite data of store A (i.e., setting information data for surveillance cameras Ca1 and Ca2) to device management server S2 (St34). An Ack is returned to the client terminal PC1 to indicate that the return of the favorite-linked camera data (that is, the setting information data of the surveillance cameras Ca1 and Ca2) that constitutes the favorite data of the store A has been completed.

[0065] Based on the Ack received from the device management server S2, the client terminal PC1 requests the user management server S3 to add access authority for the user (specifically, user U2) to the favorites data for store A (St35). In response to the request in step St35, the user management server S3 instructs the DB server S1 to add the setting information data for user U2 to the camera access user data indicating that user U2 has access authority to the video data of all surveillance cameras Ca1 and Ca2 registered in the favorites data for store A (St36). In accordance with this instruction, the DB server S1 adds the camera access user data Dt4 to which the setting information data for user U2 has been added to the database DB1 in order to configure the favorites data for store A. An Ack is returned to the user management server S3 to notify that the addition of the camera access user data Dt4, indicating that user U2 has authority to access the video data of surveillance cameras Ca1 and Ca2, to the database DB1 has been completed. Furthermore, in response to receiving the Ack from the DB server S1, the user management server S3 instructs the DB server S1 to add the data of user U2's setting information to the favorite access user data constituting the favorite data of store A (St37). In response to this instruction, the DB server S1 adds favorite access user data Dt5 to which the data of user U2's setting information has been added to the database DB1 to constitute the favorite data of store A. An Ack indicating that the favorite access user data Dt5 has been added to the database DB1 is returned to the user management server S3 and the client terminal PC1. As a result, the mobile terminal TB1 used by user U2 (i.e., permitted to log in as user U2 based on the setting information of user U2) is set to be able to access the video data from the surveillance cameras Ca1 and Ca2 located in store A through a shared operation of the client terminal PC1 used by user U1 (i.e., permitted to log in as user U1 based on the setting information of user U1), and thus the video data can be viewed remotely.

[0066] (Second operation example) Next, an outline of a second operation example of the favorite data sharing process of the surveillance camera system 100 according to the first embodiment will be described with reference to Fig. 7. Fig. 7 is a diagram showing an outline of the operation according to the second operation example. In the second operation example, favorite data Dt1a and Dt1a(1) are data created individually for users U1 and U2 of the surveillance camera system 100, respectively.

[0067] As shown in Figure 7, for example, a user U1 is pre-registered as a user of the surveillance camera system 100, and a newly registered user U2 is set to be able to access the surveillance cameras Ca1 and Ca2 of store A, which are linked to the favorite data Dt1a created by user U1.

[0068] (St1a) User U1 is set up to be able to remotely view video data from surveillance cameras (e.g., four surveillance cameras Ca1, Ca2, Ca3, and Ca4) located in store A. The client terminal PC1 used by user U1 (i.e., permitted to log in as user U1 based on user U1's setting information) creates favorites data Dt1a, which includes setting information data for surveillance cameras Ca1 and Ca2 in store A, through operation by user U1. This favorites data Dt1a is data that serves as authority to enable access to video data from surveillance cameras Ca1 and Ca2 (examples of selected surveillance cameras) in store A selected by user U1. Note that while the creation of favorites data Dt1a has been described here, the client terminal PC1 can also edit or delete favorites data Dt1a through operation by user U1.

[0069] (St2a) In response to the sharing operation of user U1, client terminal PC1 executes a sharing process to share the favorite data Dt1a created in step St1a with user U2. As a result, the mobile terminal TB1 used by user U2 (i.e., permitted to log in as user U2 based on the setting information of user U2) can obtain favorite data Dt1a(1), which is substantially the same data as the favorite data Dt1a, and can access the video data of surveillance cameras Ca1 and Ca2 in store A identified by this favorite data Dt1a(1), thereby enabling remote viewing.

[0070] (St3a) By acquiring the favorite data Dt1a(1), user U2 is now set up to be able to remotely view the video data from the surveillance cameras Ca1 and Ca2 located in store A. The mobile terminal TB1 used by user U2 (i.e., permitted to log in as user U2 based on the setting information of user U2) can edit or delete the favorite data Dt1a(1) independently of user U1's favorite data Dt1a, by operation of user U2.

[0071] Fig. 8 is a diagram showing an example of screen transitions displayed on the terminals of users U1 and U2 according to the second operation example. In Fig. 8, the surveillance camera is simply abbreviated as camera. In the explanation of Fig. 8, the same elements as those in Fig. 4 are designated by the same reference numerals, and explanations thereof are simplified or omitted, and only differences will be explained.

[0072] 7, the client terminal PC1, which is used by user U1 (i.e., permitted to log in as user U1 based on the setting information of user U1), displays thumbnails Thm1, Thm2, Thm3, and Thm4 on the camera list screen WD1, indicating that video data from surveillance cameras Ca1, Ca2, Ca3, and Ca4 located in store A can be remotely viewed. In addition, in response to the creation of favorite data Dt1a, the client terminal PC1 displays thumbnails Thm1f and Thm2f on the favorite screen WD2, indicating the contents of favorite data Dt1a (e.g., that video data from surveillance cameras Ca1 and Ca2 located in store A can be remotely viewed).

[0073] On the other hand, in the initial state Cn21 of the mobile terminal TB1, which corresponds to step St1a in Figure 3, the mobile terminal TB1 used by user U2 (i.e., allowed to log in as user U2 based on the setting information of user U2) displays a camera list screen WD3 and a favorite screen WD4 that do not display thumbnails of surveillance cameras, because the sharing process of the favorite data Dt1a has not yet been executed and no surveillance cameras that the mobile terminal TB1 can access have been set.

[0074] For example, it is assumed that the user U1 performs an operation to share the favorite data Dt1a with the user U2 in response to step St2a in FIG. 7 (St11).

[0075] In state Cn22 of the mobile terminal TB1, the mobile terminal TB1 acquires favorite data Dt1a(1), which is substantially the same data as favorite data Dt1a, through the sharing process (see FIG. 10) based on the sharing operation of favorite data Dt1a in step St11, and becomes able to access this favorite data Dt1a(1) (in other words, access to the video data of surveillance cameras Ca1 and Ca2 installed in store A). Therefore, the mobile terminal TB1 updates the display of thumbnails Thm1 and Thm2 on the camera list screen WD3a, indicating that the video data of surveillance cameras Ca1 and Ca2 installed in store A can be remotely viewed. In addition, the mobile terminal TB1 updates the display of thumbnails Thm1f and Thm2f on the favorites screen WD4a, indicating the contents of the favorite data Dt1a(1) (for example, that the video data of surveillance cameras Ca1 and Ca2 installed in store A can be remotely viewed).

[0076] For example, suppose that user U2 performs an editing operation on favorite data Dt1a(1) (e.g., an operation to delete surveillance camera Ca2) (St12) in response to step St3a in Fig. 3. Note that this deletion of surveillance camera Ca2 corresponds to, for example, deleting the setting information data of surveillance camera Ca2 in the favorite-linked camera data constituting favorite data Dt1a(1).

[0077] In state Cn23 of the mobile terminal TB1, the mobile terminal TB1 updates the display of the favorites screen WD4a by deleting the thumbnail Thm2fa from the favorites screen WD4a through the editing operation of the favorites data Dt1a(1) in step St12. As a result of this display update, only the thumbnail Thm1fa of the surveillance camera Ca1 is displayed on the favorites screen WD4a. Furthermore, the mobile terminal TB1 sends a notification (deletion notification) to the device management server S2 that the surveillance camera Ca2 has been deleted from the favorites data Dt1a(1) in step St12 (St13). Upon receiving this deletion notification, the device management server S2 forwards the deletion notification to the client terminal PC1 and also sends an instruction to the DB server S1 to delete the setting information data of the surveillance camera Ca2 from the favorites-linked camera data constituting the favorites data Dt1a(1). Based on the instruction from the device management server S2, the DB server S1 deletes the setting information data of the surveillance camera Ca2 from the favorites-linked camera data constituting the favorites data Dt1a(1).

[0078] In the state Cn12 of the client terminal PC1, even if the client terminal PC1 receives a deletion notification from the device management server S2, the client terminal PC1 does not update the display from the favorites screen WD2 in the initial state Cn11 and continues to display the same favorites screen WD2 as the favorites screen WD2 in the initial state Cn11. This is because, as described above, in the second operation example, the favorite data Dt1a of the user U1 and the favorite data Dt1a(1) of the user U2 are created separately, and editing one of the favorite data does not affect the contents of the other favorite data.

[0079] Fig. 9 is a sequence diagram showing the operation procedure of the favorite data creation process according to the second operation example in chronological order. Fig. 10 is a sequence diagram showing the operation procedure of the favorite data sharing process according to the second operation example in chronological order. In the explanation of Fig. 9 and Fig. 10, the processing performed by each server is mainly executed by the processor possessed by that server. In the explanation of Fig. 9 and Fig. 10, the same step numbers are assigned to processes that overlap with the explanation of Fig. 5, and explanations are simplified or omitted, and different contents are explained.

[0080] 9, the client terminal PC1 requests the user management server S3 to add the favorite data of store A created by user U1 in step St22 (St41). In accordance with the request in step St41, the user management server S3 instructs the DB server S1 to add the favorite data of store A created by user U1 in step St22 (St42). In accordance with this instruction, the DB server S1 adds the favorite data Dt1a of store A by user U1 to the database DB1. An Ack indicating that the favorite data of store A by user U1 has been added to the database DB1 is returned to the user management server S3 and the client terminal PC1.

[0081] Based on the Ack received from the DB server S1, the client terminal PC1 requests the device management server S2 to add the favorite-linked camera data constituting the favorites data for store A created by user U1 (St43). This request includes the setting information data for each of the surveillance cameras Ca1 and Ca2 identified by the favorites data Dt1a for store A. In accordance with the request of step St43, the device management server S2 instructs the DB server S1 to add the setting information data for the surveillance cameras Ca1 and Ca2 to the favorite-linked camera data constituting the favorites data for store A created by user U1 (St25). In accordance with this instruction, the DB server S1 adds the favorite-linked camera data Dt2a to the database DB1, to which the setting information data for the surveillance cameras Ca1 and Ca2 included in the request of step St43 has been added, in order to configure (create) the favorites data for store A. An Ack indicating that the favorite-linked camera data Dt2a has been added to the database DB1 is returned to the device management server S2 and the client terminal PC1. As a result, the client terminal PC1 has completed the registration of the favorite data of the user U1, who has the role of being authorized to access the video data of the surveillance cameras Ca1 and Ca2 installed in the store A, in the database DB1.

[0082] 10, the client terminal PC1 requests the device management server S2 to add favorite data that is substantially the same as the favorite data by the user U1 who is the target of the sharing operation executed in step St31 (St51). This request includes various setting information data that constitute the favorite data Dt1a of store A. In response to the request in step St51, the device management server S2 instructs the DB server S1 to request favorite-linked camera data that constitutes the favorite data by the user U1 who is the sharing source (St52). In response to this instruction, the DB server S1 returns the favorite-linked camera data that constitutes the favorite data by the user U1 (i.e., data on setting information for the surveillance cameras Ca1 and Ca2) to the device management server S2 (St53). An Ack is returned to the client terminal PC1 to indicate that the return of the favorite-linked camera data that constitutes the favorite data by the user U1 (i.e., data on setting information for the surveillance cameras Ca1 and Ca2) has been completed.

[0083] Based on the Ack received from the device management server S2, the client terminal PC1 requests the user management server S3 to add favorite data of store A by user U2, which is substantially the same data as the favorite data by user U1, who is the source of sharing, and to grant access rights to all video data of surveillance cameras Ca1 and Ca2 registered in the favorite data by user U1, who is the source of sharing (St54). In response to the request in step St54, the user management server S3 instructs the DB server S1 to add the favorite data of store A by user U2 (St55). In response to this instruction, the DB server S1 adds the favorite data Dt1a(1) of store A by user U2 to the database DB1. An Ack is returned from the DB server S1 to the user management server S3, notifying that the favorite data Dt1a(1) of store A by user U2 has been added to the database DB1.

[0084] Based on the Ack received from the DB server S1, the user management server S3 instructs the DB server S1 to add the setting information data of user U2 to the camera access user data indicating that user U2 has been granted permission to access the video data of surveillance cameras Ca1 and Ca2, in order to configure favorite data Dt1a(1) of store A by user U2 (St56). In accordance with this instruction, the DB server S1 adds the camera access user data Dt4a to which the setting information data of user U2 has been added to the database DB1, in order to configure favorite data Dt1a(1) of store A by user U2. An Ack is returned to the user management server S3 and the client terminal PC1 to notify that the camera access user data Dt4a, indicating that user U2 has permission to access the video data of surveillance cameras Ca1 and Ca2, has been added to the database DB1.

[0085] Furthermore, based on receiving an Ack from the user management server S3, the client terminal PC1 requests the device management server S2 to update the favorites-linked camera data that constitutes the favorites data Dt1a(1) of store A by user U2 (St57). In response to the request in step St57, the device management server S2 instructs the DB server S1 to add the setting information data of the surveillance cameras Ca1 and Ca2 to the favorites-linked camera data that constitutes the favorites data Dt1a(1) of store A by user U2 (St58). In accordance with this instruction, the DB server S1 adds the favorites-linked camera data Dt2a to the database DB1, to which the setting information data of the surveillance cameras Ca1 and Ca2 has been added, in order to constitute the favorites data Dt1a(1) of store A by user U2. An Ack indicating that the favorites-linked camera data Dt2a has been added to the database DB1 is returned to the device management server S2 and the client terminal PC1. As a result, the mobile terminal TB1 used by user U2 (i.e., permitted to log in as user U2 based on the setting information of user U2) can create favorite data Dt1a(1) for user U2 that is separate from the favorite data Dt1a for user U1 through a shared operation of the client terminal PC1 used by user U1 (i.e., permitted to log in as user U1 based on the setting information of user U1), and this favorite data Dt1a(1) is set to be accessible to the video data from the surveillance cameras Ca1 and Ca2 installed in store A, so that this video data can be viewed remotely.

[0086] (Third operation example) Next, an outline of a third operation example of the favorite data sharing process of the surveillance camera system 100 according to the first embodiment will be described with reference to Fig. 11. Fig. 11 is a diagram showing an outline of the operation according to the third operation example. In the third operation example, similar to the second operation example, the favorite data Dt1a is data created individually for the user U1 of the surveillance camera system 100.

[0087] 11, for example, a user U1 is pre-registered as a user of the surveillance camera system 100, and a user U2, who is newly registered as a user of the surveillance camera system 100, is set to be able to access the surveillance cameras Ca1 and Ca2 linked to the favorite data Dt1a created by the user U1. That is, in the third operation example, the favorite data Dt is not created by the user U2, and the setting information data of the surveillance cameras linked to the favorite data Dt1a created by the user U1 and the setting information data of the user U2 who is able to access the video data of those surveillance cameras are registered in the database DB1.

[0088] (St1) User U1 is set up to be able to remotely view video data from surveillance cameras (e.g., four surveillance cameras Ca1, Ca2, Ca3, and Ca4) located in store A. The client terminal PC1 used by user U1 (i.e., permitted to log in as user U1 based on user U1's setting information) creates favorites data Dt1a, which includes setting information data for surveillance cameras Ca1 and Ca2 in store A, through operation by user U1. This favorites data Dt1a is data that has the role of granting access to the video data of surveillance cameras Ca1 and Ca2 in store A selected by user U1. Note that while the creation of favorites data Dt1a has been described here, the client terminal PC1 can also edit or delete favorites data Dt1a through operation by user U1.

[0089] (St2) In response to the sharing operation of user U1, client terminal PC1 executes a sharing process to share the favorite data Dt1a created in step St1a with user U2. As a result, the mobile terminal TB1 used by user U2 (i.e., permitted to log in as user U2 based on the setting information of user U2) can access the video data of surveillance cameras Ca1 and Ca2 linked to the favorite data Dt1a by user U1, and can perform remote viewing.

[0090] (St3) Through the sharing operation in step St2, user U2 is now set to be able to remotely view the video data from surveillance cameras Ca1 and Ca2. The mobile terminal TB1 used by user U2 (i.e., permitted to log in as user U2 based on user U2's setting information) can remotely view the video data from surveillance cameras Ca1 and Ca2 through the operation of user U2. However, in the third operation example, as described above, the setting information data for store A is not added to the favorite data by user U2, so mobile terminal TB1 can only remotely view the video data from surveillance cameras Ca1 and Ca2.

[0091] Fig. 12 is a diagram showing an example of screen transitions displayed on the terminals of users U1 and U2 according to the third operation example. In Fig. 12, the surveillance camera is simply referred to as camera. In the explanation of Fig. 12, the same elements as those in Fig. 4 are designated by the same reference numerals, and explanations thereof are simplified or omitted, and only differences will be explained.

[0092] 11, the client terminal PC1 used by user U1 (i.e., permitted to log in as user U1 based on the setting information of user U1) displays thumbnails Thm1, Thm2, Thm3, and Thm4 on the camera list screen WD1, indicating that video data from surveillance cameras Ca1, Ca2, Ca3, and Ca4 located in store A can be remotely viewed. In addition, in response to the creation of favorite data Dt1a, the client terminal PC1 displays thumbnails Thm1f and Thm2f on the favorite screen WD2, indicating the contents of favorite data Dt1a (e.g., that video data from surveillance cameras Ca1 and Ca2 located in store A can be remotely viewed).

[0093] On the other hand, in the initial state Cn21 of the mobile terminal TB1, which corresponds to step St1 in Figure 11, the mobile terminal TB1 used by user U2 (i.e., allowed to log in as user U2 based on the setting information of user U2) displays a camera list screen WD3 and a favorite screen WD4 that do not display thumbnails of surveillance cameras, because the sharing process of the favorite data Dt1a has not yet been executed and no surveillance cameras that the mobile terminal TB1 can access have been set.

[0094] For example, it is assumed that the user U1 performs an operation to share the favorite data Dt1a with the user U2, corresponding to step St2 in FIG. 11 (St11).

[0095] By operating step St11, the setting information data for the surveillance camera linked to the favorite data Dt1a by user U1 and the setting information data for user U2 who can access the video data of that surveillance camera are registered in database DB1. Therefore, in state Cn22 of mobile terminal TB1, the mobile terminal TB1 cannot acquire favorite data such as the favorite data Dt1a of store A by user U1, and can only access the video data of surveillance cameras Ca1 and Ca2. Therefore, the mobile terminal TB1 updates the display of thumbnails Thm1a and Thm2a on the camera list screen WD3a, indicating that the video data of surveillance cameras Ca1 and Ca2 can be remotely viewed, but does not update the display of the favorite screen WD4.

[0096] For example, assume that user U2 has created favorite data by operating the user U2, which allows the user U2 to access video data captured by a surveillance camera Cc1 installed in a store C (St14).

[0097] In the state Cn23 of the mobile terminal TB1, the mobile terminal TB1 updates the display of the thumbnail Thm3 on the favorites screen WD4a, indicating the content of the favorites data (for example, that video data from the surveillance camera Cc1 installed in store C can be remotely viewed) through the favorites data creation operation in step St14. The mobile terminal TB1 also sends a notification (store C creation notification) that the favorites data has been created in step St14 to the user management server S3 (St14, see FIG. 9). The user management server S3 performs a process similar to that shown in FIG. 9 and instructs the DB server S1 to add the favorites data created in step St14. Based on the instruction from the user management server S3, the DB server S1 adds the setting information data for the surveillance camera Cc1 to the favorite-linked camera data that constitutes the favorites data. An ACK is returned to the mobile terminal TB1 indicating that the favorites data by the user U2 has been added to the DB server S1. This ACK may also be forwarded to another client terminal PC1.

[0098] In the state Cn12 of the client terminal PC1, even if the client terminal PC1 receives an Ack notifying that the favorite data by the user U2 has been added to the DB server S1, the client terminal PC1 does not update the display from the favorite screen WD2 in the initial state Cn11 and continues to display the same favorite screen WD2 as the favorite screen WD2 in the initial state Cn11. This is because, as in the second operation example, in the third operation example, the favorite data Dt1a of the user U1 and the favorite data of the user U2 are created separately, and editing one of the favorite data does not affect the contents of the other favorite data.

[0099] Fig. 13 is a sequence diagram showing the operation procedure of the favorite data sharing process according to the third operation example in chronological order. In the explanation of Fig. 13, the process performed by each server is mainly executed by the processor of that server. In the explanation of Fig. 13, the same step numbers are assigned to the processes that overlap with the explanation of Fig. 5, and the explanation is simplified or omitted, and only the different contents are explained.

[0100] 13, upon receiving an Ack from the device management server S2, the client terminal PC1 requests the user management server S3 to grant access rights to the video data of all surveillance cameras Ca1 and Ca2 registered in the favorite data by user U1 (St54b). In response to the request in step St54b, the user management server S3 instructs the DB server S1 to add the setting information data of user U2 to the camera access user data Dt4b that will enable access to the video data of surveillance cameras Ca1 and Ca2 (St56b). In response to this instruction, the DB server S1 adds the setting information data of user U2 to the camera access user data Dt4b to the database DB1. An Ack is returned from the DB server S1 to the user management server S3 and the client terminal PC1, indicating that the setting information data of user U2 has been added to the camera access user data Dt4b in the database DB1. As a result, the mobile terminal TB1 used by user U2 (i.e., permitted to log in as user U2 based on the setting information of user U2) is not able to create favorite data for user U2 that is separate from the favorite data Dt1a by user U1 through the shared operation of the client terminal PC1 used by user U1 (i.e., permitted to log in as user U1 based on the setting information of user U1), but is set up to be able to access the video data of surveillance cameras Ca1 and Ca2 registered in that favorite data Dt1a, and therefore can view this video data remotely.

[0101] As described above, the surveillance camera system 100 according to the first embodiment includes one or more user terminals for viewing video data from multiple surveillance cameras installed in a target facility, and a server for storing access permission data including at least first user information about a user with access authority to the video data from the surveillance cameras and surveillance camera information indicating information about at least one selected surveillance camera selected by operating the user terminal based on the first user information. The first user information is, for example, setting information (e.g., user authority) for permitting user U1 to log in as a user of the surveillance camera system 100. The user terminal based on the first user information is, for example, client terminal PC1 used by user U1 (i.e., permitted to log in as user U1 based on the setting information of user U1). The target facility is, for example, a store. The selected surveillance cameras are, for example, surveillance cameras Ca1 and Ca2. The surveillance camera information is, for example, setting information data for surveillance cameras Ca1 and Ca2. The access permission data is, for example, favorite data. The servers are, for example, DB server S1, device management server S2, and user management server S3. The server updates the access permission data by adding access authority to the video data of the selected surveillance camera to the second user information based on the sharing process of the access permission data for the second user information by operating the user terminal based on the first user information, and sets the video data of the selected surveillance camera identified by the surveillance camera information linked to the access permission data to be accessible by the user terminal based on the second user information. The second user information is, for example, setting information (e.g., user authority) that allows user U2 to log in as a user of the surveillance camera system 100. The user terminal linked to the second user information is, for example, the mobile terminal TB1 used by user U2 (i.e., permitted to log in as user U2 based on the setting information of user U2).

[0102] As a result, the surveillance camera system 100 can easily share video data from at least one surveillance camera identified by the favorite data with a user terminal based on second user information by performing a sharing operation on the favorite data of at least one surveillance camera selected by a user terminal based on first user information, thereby improving the efficiency of data sharing.

[0103] The access permission data also includes facility information (e.g., information about store A) indicating information about the facility where the selected surveillance camera is located. This allows the favorite data to include setting information data for store A selected by a user terminal (e.g., client terminal PC1) based on the first user information, making it easy to confirm which surveillance camera the video data is from.

[0104] The access permission data is a single piece of data that can be shared by both the user terminal based on the first user information and the user terminal based on the second user information, so that editing, adding, or deleting the contents of the favorite data on one user terminal affects the use of the other user terminal, improving convenience.

[0105] Furthermore, after the access permission data sharing process, the server displays a display screen having the video data of the selected surveillance camera specified by the surveillance camera information linked to the access permission data and information about the target facility in the same screen layout on each of the user terminal based on the first user information and the user terminal based on the second user information. This allows the other user who has shared the favorite data to view the video data of the selected surveillance camera in a screen format with the same layout, in a form that reflects the preferences of the one user who created the favorite data.

[0106] Furthermore, the server, based on a deletion process by a user terminal based on the second user information for some of the selected surveillance cameras identified by the surveillance camera information linked to the access permission data, sets only the video data of the selected surveillance cameras after the deletion process to be accessible to both the user terminal based on the first user information and the user terminal based on the second user information. This allows, for example, the setting information data of a selected surveillance camera that no longer requires remote monitoring for both users to be easily deleted from favorite data by a deletion process by the user terminal based on the first user information or the user terminal based on the second user information, which is expected to facilitate maintenance of favorite data.

[0107] The access permission data includes first access permission data that is set to allow at least one of creation, editing, and access only by the user terminal based on the first user information, and second access permission data that is set to allow at least one of creation, editing, and access only by the user terminal based on the second user information. The first access permission data is favorite data created by user U1. Similarly, the second access permission data is favorite data created by user U2. This allows the creation, editing, and access of favorite data to be set individually for each user, enabling the management of favorite data with a high degree of freedom in a manner that reflects each user's preferences.

[0108] After the first access permission data is shared, the server creates and stores second access permission data, which is a copy of the first access permission data. This allows user U1 to easily share favorite data with user U2 that has the same content as the favorite data of user U1.

[0109] Furthermore, after the first access permission data sharing process, the server displays a first display screen on a user terminal based on the first user information, the first display screen including video data from the selected surveillance camera identified by the surveillance camera information linked to the first access permission data and information about the target facility, and also displays a second display screen on a user terminal based on the second user information, the second display screen including video data from the selected surveillance camera identified by the surveillance camera information linked to the second access permission data and information about the target facility. The first display screen and the second display screen each have the same layout. The first display screen is, for example, a favorites screen WD2a on the client terminal PC1. The second display screen is, for example, a favorites screen WD4a on the mobile terminal TB1. As a result, while the favorite data is stored in the database DB1 so that it is different for each user, the display screen layout preferences of the user who created the favorite data are reflected, and the other user who receives the favorite data can view the video data from the selected surveillance camera in a screen format with the same display screen layout.

[0110] Furthermore, based on a deletion process performed by a user terminal based on the second user information for some of the surveillance cameras identified by the surveillance camera information linked to the second access permission data, the server sets the video data of the surveillance cameras after the deletion process to be accessible only to the user terminal based on the second user information, and sets the video data of the surveillance cameras identified by the first access permission data that are not subject to the deletion process to be accessible to the user terminal based on the first user information. As a result, even if user U2 uses mobile terminal TB1 to remove a surveillance camera that is no longer required for monitoring from among the surveillance cameras identified by his / her own favorite data, the configuration of the favorite data of other users (e.g., user U1) is not affected, and user U1 can view the video data of the surveillance camera for monitoring based on the favorite data linked to him / her.

[0111] Furthermore, after sharing the first access permission data, the server causes the user terminal based on the first user information to display a first display screen having video data from the selected surveillance camera identified by the surveillance camera information linked to the first access permission data and information about the target facility, and also causes the user terminal based on the second user information to display a second display screen having video data from the selected surveillance camera identified by the surveillance camera information linked to the second access permission data. This allows surveillance camera system 100 to remotely view for monitoring the video data of the surveillance camera that is the monitoring target in user U1's favorite data, without user U2 having to create his or her own favorite data.

[0112] Although various embodiments have been described above with reference to the drawings, it goes without saying that the present disclosure is not limited to such examples. It is clear that a person skilled in the art can conceive of various modifications, alterations, substitutions, additions, deletions, and equivalents within the scope of the claims, and it is understood that these also naturally fall within the technical scope of the present disclosure. Furthermore, the components of the various embodiments described above may be combined in any manner without departing from the spirit of the invention. [Industrial Applicability]

[0113] The present disclosure is useful for a surveillance camera video sharing system and a surveillance camera video sharing method that improve the efficiency of data sharing of video from at least one surveillance camera. [Explanation of symbols]

[0114] 21, 31, 41 Communication devices 22, 32, 42 processors 23, 33, 43 memory 100 Surveillance Camera System Ca1, Ca2, Cb1, Cb2 surveillance cameras DB1 database TB1 Mobile Terminal NW1 and NW2 networks PC1 client terminal RD Recorder S1 DB server S2 Device Management Server S3 User Management Server S4 distribution control server

Claims

1. one or more user terminals for viewing video data from multiple surveillance cameras installed in the target facility; a server that stores access permission data including at least first user information having access authority to the video data of the surveillance camera and surveillance camera information indicating information of at least one selected surveillance camera selected by operation of the user terminal linked to the first user information; the server updates the access permission data by adding, to the second user information, access authority to the access permission data and access authority to the video data of the selected surveillance camera based on an operation of sharing the access permission data with second user information performed by an operation of the user terminal linked to the first user information, and sets the video data of the selected surveillance camera identified by the surveillance camera information linked to the access permission data to be accessible by the user terminal linked to the first user information and the user terminal linked to the second user information. Surveillance camera video sharing system.

2. the access permission data further includes facility information indicating information about the target facility in which the selected surveillance camera is installed, The surveillance camera video sharing system according to claim 1 .

3. the access permission data is a single piece of data that can be shared by each of the first user information and the second user information; The surveillance camera video sharing system according to claim 1 .

4. After the access permission data sharing process, the server causes a first user terminal based on the first user information and a second user terminal based on the second user information to display a display screen having video data of the selected surveillance camera identified by the surveillance camera information linked to the access permission data and information about the target facility in the same screen layout. The surveillance camera video sharing system according to claim 2 .

5. the server, based on a deletion process by the second user terminal of some of the selected surveillance cameras identified by the surveillance camera information linked to the access permission data, sets only the video data of the selected surveillance cameras after the deletion process to be accessible to each of the first user terminal and the second user terminal; The surveillance camera video sharing system according to claim 4.

6. the access permission data includes first access permission data that is provided so that at least one of creation, editing, and access can be performed only by a first user terminal based on the first user information, and second access permission data that is provided so that at least one of creation, editing, and access can be performed only by a second user terminal based on the second user information; The surveillance camera video sharing system according to claim 1 .

7. after the sharing process of the first access permission data, the server creates and stores the second access permission data, which is a copy of the first access permission data; The surveillance camera video sharing system according to claim 6.

8. After the sharing process of the first access permission data, the server causes a first user terminal based on the first user information to display a first display screen having video data of the selected surveillance camera specified by the surveillance camera information linked to the first access permission data and information about the target facility, and causes a second user terminal based on the second user information to display a second display screen having video data of the selected surveillance camera specified by the surveillance camera information linked to the second access permission data and information about the target facility, the first display screen and the second display screen are configured with the same layout; The surveillance camera video sharing system according to claim 6.

9. the server, based on a deletion process by the second user terminal of some of the surveillance cameras identified by the surveillance camera information linked to the second access permission data, sets the video data of the surveillance cameras after the deletion process to be accessible only to the second user terminal, and sets the video data of the surveillance cameras identified by the first access permission data that are not subject to the deletion process to be accessible to the first user terminal; The surveillance camera video sharing system according to claim 6.

10. After the sharing process of the first access permission data, the server causes the first user terminal to display a first display screen having video data of the selected surveillance camera specified by the surveillance camera information linked to the first access permission data and information about the target facility, and causes the second user terminal to display a second display screen having video data of the selected surveillance camera specified by the surveillance camera information linked to the second access permission data. The surveillance camera video sharing system according to claim 6.

11. storing in a server access permission data including at least first user information having access authority to video data from a plurality of surveillance cameras installed in the target facility and surveillance camera information indicating information on at least one selected surveillance camera selected by operation of a user terminal linked to the first user information; updating the access permission data by adding, to the second user information, an access right to the access permission data and an access right to the video data of the selected monitoring camera, based on an operation of sharing the access permission data with second user information by an operation of the user terminal linked to the first user information; setting the video data of the selected surveillance camera identified by the surveillance camera information linked to the access permission data to be accessible by the user terminal linked to the first user information and the user terminal linked to the second user information; How to share surveillance camera footage.

Images