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 support improvement of job efficiency of a third person differing from a user by enabling video data of a monitor camera to be shared temporarily with the third person.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 at least monitor camera information showing information on at least one selected monitor camera selected by a user terminal based on external user information on an external user of a plurality of monitor cameras and authorized user information on an authorized user having an access right to video data of the selected monitor camera. On the basis of sharing processing on the access permission data to the user terminal based on the external user information, the server adds external user information including an access valid period to the access permission data to the access permission data and updates the access permission data.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 video distribution system including a distribution system that distributes video via the Internet, a viewing terminal that views the video, and a relay system that receives video calls from the viewing terminal, performs videophone communication with the viewing terminal, and relays and transmits the video received from the distribution system via the Internet to the viewing terminal using the videophone communication. A validity period is set for access information generated by the distribution system and used by the relay system to access the distribution system. [Prior art documents] [Patent documents]

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

[0004] In the configuration of Patent Document 1, video distribution via videophone communication between the distribution system and the viewing terminal via a relay system is possible only for users who own the distribution system and viewing terminal that constitute the video distribution system during the validity period of the access information. However, Patent Document 1 does not anticipate a third party who does not own the distribution system (e.g., a police officer remotely viewing and playing video data from a surveillance camera installed in a store) accessing video data captured by the distribution system for a limited period of time for work (e.g., an investigation conducted in the course of performing their duties). In other words, there is room for improvement in terms of making it easier for a third party, a person other than the user or an external organization, to access video data captured by a distribution system related to the user for a specified period of time (in other words, temporarily).

[0005] The present disclosure has been devised in consideration of the above-mentioned conventional circumstances, and aims to provide a surveillance camera video sharing system and a surveillance camera video sharing method that enable temporary sharing of surveillance camera video data with third parties other than the user, thereby helping to improve the business efficiency of the third parties. [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, and to a system for accessing external user information of external users who are registered to be able to temporarily use the surveillance cameras. Link the user terminal By the user terminal linked to the authorized user information of the authorized user, The system has surveillance camera information indicating information about at least one selected surveillance camera and has access rights to video data of the selected surveillance camera. The aforementioned Regular user's The aforementioned and a server that stores access permission data including at least authorized user information, The external user's The external user information Link Sharing the access permission data to the user terminal operationand updating the access permission data by adding the external user information including the access validity period to the access permission data based on the access permission data, and adding the video data of the selected surveillance camera specified by the surveillance camera information linked to the access permission data to the external user information only during the access validity period. Link Set the user terminal to be accessible Performing a sharing process We provide a surveillance camera video sharing system.

[0007] The present disclosure also provides: A surveillance camera video sharing method executed by a surveillance camera video sharing system, comprising: Among the multiple surveillance cameras installed in the target facility, the external user information of external users who are registered to be temporarily available Link User terminal User terminals linked to the authorized user information of authorized users so that they can access and monitoring camera information indicating information of at least one selected monitoring camera selected by the The aforementioned Regular user's The aforementioned Authorized user information and access permission data including at least Protect Exist, The server: The external user information Link Sharing the access permission data to the user terminal operation and updating the access permission data by adding the external user information including the access validity period to the access permission data based on the access permission data, and adding the video data of the selected surveillance camera specified by the surveillance camera information linked to the access permission data to the external user information only during the access validity period. Link Set the user terminal to be accessible Performing a sharing process A method for sharing surveillance camera footage is provided.

[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, video data from a surveillance camera can be temporarily shared with a third party other than the user, thereby helping to improve the work efficiency of the third party.

[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] A diagram showing the outline of the favorite data sharing process [Figure 4] FIG. 10 shows an example of screen transitions displayed on the mobile terminal of police officer U2 in the first operation example. [Figure 5] A sequence diagram showing the operation procedure of the setting process for granting access authority according to the first operation example in chronological order. [Figure 6] FIG. 10 shows an example of screen transitions displayed on the mobile terminal of police officer U2 in the second operation example. [Figure 7] A sequence diagram showing the operation procedure of the setting process for granting access authority according to the second operation example in chronological order. [Figure 8] A sequence diagram showing the chronological order of the process for deleting favorite data when the access validity period expires. 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) In the following first embodiment, an example of a use case will be described in which video data from a surveillance camera installed in a target facility such as a store, which is required for the performance of duties such as an investigation, is temporarily made accessible to a terminal used by a police officer U2 who is an external user and not an authorized user of the surveillance camera system 100. Note that the use case according to the first embodiment is not limited to the above example.

[0014] 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.

[0015] 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.

[0016] 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.

[0017] 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.

[0018] 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; the same applies below) 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., public facilities such as shopping malls, office buildings, city halls, or libraries), or multiple stores, may also be considered as a single facility.

[0019] Furthermore, when a client terminal PC1 used by user U1, who is registered as an authorized user of the surveillance camera system 100, performs an operation to share favorite data (an example of access permission data) of a surveillance camera with another user's terminal (for example, a mobile terminal TB1 used by police officer U2, who is an external user and not an authorized user of the surveillance camera system 100), the surveillance camera system 100 executes a sharing process that, based on the sharing operation, enables the mobile terminal TB1 to access the video data of the surveillance camera specified in the sharing operation. Details of this sharing process will be described later with reference to the accompanying drawings from FIG. 3 onwards.

[0020] 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.

[0021] 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.

[0022] 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.

[0023] The client terminal PC1 is, for example, a personal computer, and is used by user U1, who is registered as an authorized user of the surveillance camera system 100. An authorized user of the surveillance camera system 100 is, for example, a user who has been granted access rights to all contracted video data from the surveillance cameras of the surveillance camera system 100, and this access right is registered (saved) as user U1's setting information data in database DB1 (see FIG. 2) of DB server S1. The client terminal PC1 communicates data with each of the DB server S1, device management server S2, user management server S3, and distribution control server S4 via network NW2. In the following description, user U1 is a person who performs a sharing operation on favorite surveillance camera data at the request of police officer U2 or of his or her own volition. The client terminal PC1 sends a request for sharing favorite surveillance camera data to the user management server S3 in response to an operation by user U1.

[0024] The mobile terminal TB1 is, for example, a mobile phone, smartphone, or tablet terminal, and is used by a police officer U2. After being registered as a temporary user in the surveillance camera system 100, 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 police officer U2 is a person with whom the favorite data of the surveillance camera is shared in the course of performing duties such as investigations. 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.

[0025] The DB server S1 is configured, for example, by a server computer, and includes a database DB1 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 (specifically, authorized user, temporary user) who is registered to be able to use the surveillance camera system 100 (see FIG. 2). The DB server S1 references the database DB1, retrieves data from the database DB1 in response to a request from the device management server S2 or the user management server S3, and responds. 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 validity period), but is not limited to these. The various setting information for each user includes, but is not limited to, the user's name, user type (e.g., regular user, temporary user), 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 validity period of the login ID and password, user authority (e.g., store manager authority with authority equivalent to that of a supervisor, store clerk authority with authority equivalent to that of a general user, access authority to surveillance camera video data provided for each surveillance camera), and the validity period of access set only for temporary users. A detailed example of the hardware configuration of DB server S1 will be described later with reference to FIG. 2.

[0026] The device management server S2 is configured, for example, by 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 a request for device setting information data, including information on a facility (e.g., a store) that is the target of favorite data, from the client terminal PC1, the device management server S2 transfers the request for the device information data to the DB server S1. Based on the transferred request, the DB server S1 acquires the corresponding device information data from the database DB1 and returns it to the device management server S2. The device management server S2 responds to the client terminal PC1 with the device information data returned from the DB server S1. A detailed example of the hardware configuration of the device management server S2 will be described later with reference to FIG. 2.

[0027] The user management server S3 is, for example, 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 to create setting information data for a temporary user (e.g., police officer U2), the user management server S3 instructs the DB server S1 to add setting information data for the temporary user, including information on the access validity period, which is set to a predetermined period (e.g., one hour), based on the request. Based on this instruction, the DB server S1 creates and registers (stores) the setting information data for the corresponding temporary user (hereinafter referred to as "user data"). Furthermore, when the user management server S3 receives from the client terminal PC1 a request to add access authority to video data of a surveillance camera for the temporary user (e.g., police officer U2), the user management server S3 instructs the DB server S1 to add data (hereinafter referred to as "camera access user data") containing the setting information data for the surveillance camera and the setting information data for the temporary user who will be able to access the video data of the surveillance camera based on the request. Based on this instruction, the DB server S1 adds the corresponding camera access user data. Furthermore, the user management server S3 instructs the DB server S1 to add access authority to the favorite data of the target facility (e.g., store A) that is the target of the temporary user (e.g., police officer U2). Based on this instruction, the DB server S1 adds access authority to the favorite data that is relevant to the temporary user (e.g., police officer U2). A detailed example of the hardware configuration of the user management server S3 will be described later with reference to FIG. 2.

[0028] 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 validity period has not yet expired), it determines to permit the client terminal PC1 or the mobile terminal TB1 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., both the license validity period and the recording grace period have expired) and the license has not been updated, it determines to prohibit the client terminal PC1 or the mobile terminal TB1 from viewing the video data captured by the surveillance camera Ca1.

[0029] (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.

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

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

[0036] The favorite data is provided and created for each target facility (e.g., Store A, Store B) and is data configured using at least one of user data, favorite-linked camera data, favorite-access user data, and camera-access user data. More specifically, the favorite data is data for each target facility (e.g., Store A, Store B) that a user of the surveillance camera system 100 (e.g., an authorized user or a temporary user such as police officer U2) has selected as a target for remote monitoring, including setting information for the target facility (e.g., a store), setting information for the equipment (e.g., surveillance cameras) installed in the target facility (see above), and setting information for users who can access the facility (see above). Note that the setting information for the target facility (e.g., a store) may be omitted. Note that the favorite data does not have to be created for each store, and may be created to cover, for example, the surveillance cameras installed in front of the registers of all stores.

[0037] User data is data constituting favorite data and is data of setting information of a user who can access favorite data. The user data includes, for example, setting information of user U1 (e.g., name, user type, and access validity period). The user type indicates whether the user is a regular user or a temporary user. The access validity period indicates a predetermined period (e.g., one hour) during which the favorite data corresponding to the user data can be accessed. Note that the predetermined period is not limited to one hour and may be set automatically or specified by the user's operation. A regular user can access the surveillance camera system 100 at any time as long as they are permitted to log in, unless their registration as a regular user is deleted. On the other hand, a temporary user can access the surveillance camera system 100 only during the access validity period specified by the user data, once the access validity period expires, as the temporary user's user data (in other words, account) is also deleted and the temporary user is no longer able to access the system.

[0038] The favorite-linked camera data is data that constitutes the favorite data, and is data of the setting information (see above) of the surveillance cameras that are the subject of viewing for monitoring purposes 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 includes data of the setting information of the target facility (e.g., store A) and data of setting information (e.g., names) of surveillance cameras Ca1 and Ca2.

[0039] The favorite access user data is data constituting the favorite data, and is data of setting information (see above) of users who can access the favorite data. For example, if 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 data of setting information of the target facility (e.g., store A) and setting information (e.g., name) of user U1. Also, if user U1 performs a sharing operation on the favorite data so that police officer U2 can also access it (see FIG. 7), the favorite access user data constituting the favorite data will have data of setting information of the target facility (e.g., store A) and data of setting information (e.g., name) of user U1 and police officer U2.

[0040] The camera access user data is data constituting the favorite data, and includes setting information (see above) data of users who can access the video data of a device (e.g., a surveillance camera) specified by the favorite-linked camera data, and setting information data of that device (e.g., a surveillance camera). For example, when user U1 performs an operation to newly enable police officer U2 to access the video data of the surveillance camera specified by the favorite-linked camera data (see FIG. 7), DB server S1 creates camera access data consisting of setting information data of that surveillance camera and setting information data of the new police officer U2.

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

[0042] 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.

[0043] 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.

[0044] 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.

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

[0046] 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.

[0047] 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.

[0048] 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.

[0049] Next, an outline of the operation 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 the outline of the operation of the favorite data sharing process. Favorite data Dt1 is created by user U1, who is an authorized user of the surveillance camera system 100.

[0050] As shown in Figure 3, an example is described in which user U1 is pre-registered as a legitimate user of the surveillance camera system 100, and police officer U2, who has been newly registered as a temporary user of the surveillance camera system 100, is set to be able to access surveillance cameras Ca1 and Ca2 in store A, which are linked to favorite data Dt1 created by user U1.

[0051] (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 or a login ID and password pair) 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 authorized 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 the setting information data for the surveillance cameras Ca1 and Ca2 in store A. This favorite data Dt1 is data that serves as the authority to access the video data from the surveillance cameras Ca1 and Ca2 in store A selected by user U1. While the creation of favorite data Dt1 has been described above, user U1 can also edit or delete the favorite data Dt1 through the operation of the client terminal PC1.

[0052] (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 police officer U2 (in other words, to make it accessible from mobile terminal TB1 used by police officer U2). Note that mobile terminal TB1 used by police officer U2 is an example of a user terminal that allows police officer U2 as a temporary user to log in to surveillance camera system 100 based on police officer U2's setting information (e.g., login ID and password), and the same applies below. As a result, mobile terminal TB1 used by police officer U2 can obtain favorite data that is substantially similar to favorite data Dt1.

[0053] (St3) As a result, the mobile terminal TB1 used by police officer U2 is able to temporarily access the video data from surveillance cameras Ca1 and Ca2 in store A identified by favorite data Dt1, enabling remote viewing. The length of time for which access is available is determined by the valid access period included in the user data (see FIG. 5 or FIG. 7) that constitutes favorite data Dt1. In addition to remote viewing, when temporary access is available, it is also possible to download the video data from the necessary surveillance cameras.

[0054] (First operation example) 4 is a diagram showing an example of screen transitions displayed on the mobile terminal TB1 of the police officer U2 according to the first operation example. In FIG. 4, the surveillance camera is simply abbreviated as camera.

[0055] In the initial state Cn11 of the client terminal PC1, which corresponds to step St1 in Figure 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 the video data of surveillance cameras Ca1, Ca2, Ca3, and Ca4 located in store A can be remotely viewed.

[0056] Here, it is assumed that user U1 has operated the client terminal PC1 to create user data for a police officer U2 who will be a temporary user of the surveillance camera system 100 (St11).

[0057] Next, suppose that user U1 performs an operation using client terminal PC1 to share surveillance camera Ca1 with police officer U2 (St12), corresponding to step St2 in Fig. 3. In the example of Fig. 4, the sharing target is not the favorite data Dt1 shown in Fig. 3, but a specific device (e.g., surveillance camera Ca1) designated by user U1 from among the target facilities of surveillance camera system 100 in response to a request for investigation by police officer U2, etc.

[0058] In the initial state Cn21 of the mobile terminal TB1, the mobile terminal TB1 can access only the video data of the surveillance camera Ca1 through the sharing process (see FIG. 7) based on the sharing operation of the surveillance camera Ca1 in step St12. Therefore, the mobile terminal TB1 used by the police officer U2 (i.e., the mobile terminal TB1 that is permitted to log in as the police officer U2 based on the setting information of the police officer U2) displays a thumbnail Thm1 on the camera list screen WD3, indicating that the video data of the surveillance camera Ca1 can be remotely viewed.

[0059] 5 is a sequence diagram showing, in time sequence, the operation procedure of the setting process for granting access authority according to the first operation example. In the explanation of FIG. 5, the process performed by each server is mainly executed by a processor that the server has.

[0060] 5, police officer U2 requests user U1 for access rights to a surveillance camera (e.g., surveillance camera Ca1) that needs to be viewed for an investigation. The access rights request may be made by filling out an online request form, by email or telephone, or verbally during a visit to inspect the scene.

[0061] Upon receiving this request, user U1 performs an operation on client terminal PC1 to create a temporary user for the surveillance camera system 100. This operation specifies the setting information data for surveillance camera Ca1, for which police officer U2 is requesting access privileges. In response to the operation by user U1, client terminal PC1 creates a temporary user creation request to make police officer U2 a temporary user, and sends the request to user management server S3 (St21), so that police officer U2 can access the video data from surveillance camera Ca1 that is the target of the request from police officer U2. In accordance with the creation request in step St21, user management server S3 instructs DB server S1 to add user data Dt11 that makes police officer U2 a temporary user (St22). In accordance with this instruction, DB server S1 adds user data Dt11 for police officer U2 to database DB1. The user data Dt11 indicates, for example, that police officer U2 is permitted access until 9:00 PM on September 10, 2021. In other words, the valid access period is set from the time the user data Dt11 is created (20:00 on September 10, 2021) until 21:00 on September 10, 2021, a predetermined time later (for example, one hour). An ACK indicating that the addition of the user data Dt11 of police officer U2 to database DB1 has been completed is returned to the user management server S3 and the client terminal PC1.

[0062] Upon receiving the Ack from the DB server S1, the client terminal PC1 sends a setting request for the surveillance camera (e.g., surveillance camera Ca1) linked to the police officer U2 to the user management server S3 (St23). In response to the setting request in step St23, the user management server S3 instructs the DB server S1 to add data for linking the police officer U2 with the surveillance camera Ca1 (St24). In accordance with this instruction, the DB server S1 creates camera access user data Dt12 containing setting information data for the police officer U2 and setting information data for the surveillance camera Ca1 and adds it to the database DB1 so that the police officer U2 can temporarily access the video data of the surveillance camera Ca1. An Ack indicating that the camera access user data Dt12 has been added to the database DB1 is returned to the user management server S3 and the client terminal PC1. After confirming receipt of the Ack from the client terminal PC1, the user U1 knows that the temporary user creation has been completed and that the police officer U2 has been able to set the access rights to the video data from the specific surveillance camera Ca1, and notifies the police officer U2 that his own account has been created. As a method of notifying the police officer that the account has been created, for example, the user management server S3 may automatically send an email containing the account and initial password to the mobile terminal TB1 used by the police officer.

[0063] As a result, the mobile terminal TB1 used by police officer U2 (i.e., authorized to log in as police officer U2 based on the setting information of police officer U2) can temporarily access the video data of a specific surveillance camera Ca1 selected (designated) by user U1 at the request of police officer U2 through a shared operation of the client terminal PC1 used by user U1. This allows police officer U2 to remotely view the video data of surveillance camera Ca1 during an investigation, etc., thereby improving work efficiency. Furthermore, because police officer U2 can view the video data remotely himself, there is no need for user U1 to operate it on behalf of police officer U2 in the presence of police officer U2.

[0064] (Second operation example) Fig. 6 is a diagram showing an example of screen transitions displayed on the mobile terminal TB1 of police officer U2 in the second operation example. In Fig. 6, as in Fig. 4, the surveillance camera is simply abbreviated as camera. In the explanation of Fig. 6, the same elements as those in Fig. 4 are given the same reference numerals, and explanations thereof are simplified or omitted, and only differences will be explained.

[0065] 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).

[0066] Now, suppose that user U1 has created user data (see FIG. 5) for police officer U2, who will be a temporary user of the surveillance camera system 100, through an operation using client terminal PC1 (St11). Then, in the initial state Cn21 of mobile terminal TB1, which corresponds to step St1 in FIG. 3, the mobile terminal TB1 used by police officer U2 displays a camera list screen WD3 and a favorites screen WD4, which do not display thumbnails of surveillance cameras, because the sharing process for favorite data Dt1 has not yet been executed and no surveillance cameras that mobile terminal TB1 can access have been set.

[0067] Next, suppose that user U1 performs an operation using client terminal PC1 to share favorite data Dt1 with police officer U2 (St12), corresponding to step St2 in Fig. 3. In the example of Fig. 6, unlike the example of Fig. 4, the favorite data Dt1 shown in Fig. 3 (i.e., access rights to video data from surveillance cameras Ca1 and Ca2 installed in store A) is the object of sharing.

[0068] In state Cn22 of mobile terminal TB1, the mobile terminal TB1 used by police officer U2 (i.e., permitted to log in as police officer U2 based on the setting information of police officer U2) can access the favorite data Dt1 through the sharing process (see FIG. 7) based on the sharing operation of the favorite data Dt1 in step St12, and can access the video data of surveillance cameras Ca1 and Ca2 installed in store A. 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 installed in store A can be remotely viewed. In addition, the mobile terminal TB1 updates the display of thumbnails Thm1f and Thm2f on the favorite screen WD4a, indicating the contents of the favorite data Dt1 (e.g., that the video data of surveillance cameras Ca1 and Ca2 installed in store A can be remotely viewed).

[0069] Fig. 7 is a sequence diagram showing the operation procedure of the setting process for granting access authority according to the second operation example in chronological order. In the explanation of Fig. 7, the processing performed by each server is mainly executed by the processor of that server. Note that the explanation of Fig. 7 is premised on the assumption that favorite data Dt1 for store A has already been created, and that setting information data for store A and setting information data for surveillance cameras Ca1 and Ca2 located in store A have been registered as favorite-linked camera data constituting the favorite data Dt1 for store A.

[0070] In FIG. 7, user U1 uses client terminal PC1 to perform an operation to create a temporary user for the surveillance camera system 100. This operation specifies the setting information data for surveillance cameras Ca1 and Ca2 located in store A, for which police officer U2 is requesting access privileges. In response to the operation by user U1, client terminal PC1 creates a temporary user creation request for making police officer U2 a temporary user, enabling police officer U2 to access the video data from surveillance cameras Ca1 and Ca2 that are the subject of the request from police officer U2, and sends the request to user management server S3 (St31). In response to the creation request in step St31, user management server S3 instructs DB server S1 to add user data Dt11 that makes police officer U2 a temporary user (St32). In response to this instruction, DB server S1 adds user data Dt11a for police officer U2 to database DB1. For example, user data Dt11a indicates that police officer U2 is permitted access until 9:00 PM on September 10, 2021. In other words, the valid access period is set from the time the user data Dt11a was created (20:00 on September 10, 2021) to 21:00 on September 10, 2021, a predetermined time later (for example, one hour). An ACK indicating that the addition of the user data Dt11a of police officer U2 to database DB1 has been completed is returned to the user management server S3 and client terminal PC1.

[0071] Based on the receipt of Ack from the DB server S1, the client terminal PC1 creates a request to acquire device data (e.g., data on setting information for surveillance cameras Ca1 and Ca2) for constituting the favorites-linked camera data that constitutes the favorites data of store A, and sends the request to the device management server S2 (St33). In response to the request in step St33, the device management server S2 instructs the DB server S1 to acquire setting information data for surveillance cameras Ca1 and Ca2 to add to the favorites-linked camera data that constitutes the favorites data of store A (St34). In response to this instruction, the DB server S1 acquires setting information data for accessible devices (e.g., surveillance cameras Ca1 and Ca2) from the favorites-linked camera data that constitutes the favorites data Dt1 of store A, and responds to the device management server S2 (St35). The device management server S2 transfers the setting information data for surveillance cameras Ca1 and Ca2 received in response from the DB server S1 in step St35 to the client terminal PC1.

[0072] When the client terminal PC1 receives the setting information data for the surveillance cameras Ca1 and Ca2 from the device management server S2, it requests the user management server S3 to add access authority for the temporary user (i.e., police officer U2) to the video data of those surveillance cameras Ca1 and Ca2 (St36). In response to the request in step St36, the user management server S3 instructs the DB server S1 to create camera access user data Dt12a containing setting information data for police officer U2 and setting information data for surveillance cameras Ca1 and Ca2 in order to add access authority to the video data of the surveillance cameras Ca1 and Ca2 that have been added to the favorites data Dt1 of store A (St37). In accordance with this instruction, the DB server S1 adds (registers) the setting information data for police officer U2 and the setting information data for surveillance cameras Ca1 and Ca2 to the camera access user data Dt12a that constitutes the favorites data Dt1 of store A. An Ack is returned to the user management server S3 to indicate that the addition (registration) of the camera access user data Dt12a to the database DB1 has been completed.

[0073] Based on the Ack received from the DB server S1, the user management server S3 instructs the DB server S1 to create favorite access user data Dt13, which includes the setting information data for police officer U2 and the setting information data for store A, in order to add access authority for police officer U2 to the favorite data Dt1 for store A (St38). In accordance with this instruction, the DB server S1 adds (registers) the setting information data for police officer U2 and the setting information data for surveillance cameras Ca1 and Ca2 to the favorite camera access user data Dt12a constituting the favorite data Dt1 for store A. An Ack is returned to the user management server S3 and the client terminal PC1 to indicate that the addition (registration) of the camera access user data Dt12a to the database DB1 has been completed. After confirming the receipt of the Ack from the client terminal PC1, user U1 understands that the temporary user creation has been completed and that police officer U2 has been granted access authority to the video data of the surveillance cameras Ca1 and Ca2 located in store A by having received the favorite data Dt1 shared with him, and notifies police officer U2 that his own account has been created.

[0074] As a result, the mobile terminal TB1 used by police officer U2 (i.e., permitted to log in as police officer U2 based on the setting information of police officer U2) can temporarily access the video data from the surveillance cameras Ca1 and Ca2 located in store A selected (designated) by user U1 at the request of police officer U2 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). Therefore, police officer U2 can remotely view the video data from the surveillance cameras Ca1 and Ca2 during investigations, etc., thereby improving work efficiency.

[0075] Figure 8 is a sequence diagram showing the operation procedure of the deletion process of favorite data due to the expiration of the access validity period in chronological order. In the explanation of Figure 8, the processing performed by each server is mainly executed by the processor possessed by that server. Note that the explanation of Figure 8 is premised on the fact that the user management server S3 constantly or periodically obtains data on the access validity period included in the user data of a temporary user (for example, police officer U2) from the DB server S1.

[0076] 8, the user management server S3 monitors whether the access valid period included in the user data of a temporary user (e.g., police officer U2) has expired (St41). When the user management server S3 determines that it has extracted user data (e.g., user data of police officer U2) whose access valid period has expired, it instructs the DB server S1 to delete favorite-access user data Dt13 that indicates access authority to favorite data of store A and that is linked to the temporary user (e.g., police officer U2) whose access valid period has expired (St42). The DB server S1 deletes the corresponding favorite-access user data Dt13 in accordance with the instruction in step St42, and responds with an Ack to that effect to the user management server S3.

[0077] Based on the Ack received from the DB server S1, the user management server S3 instructs the DB server S1 to delete the camera access user data indicating the access authority to the surveillance camera video data associated with the temporary user (e.g., police officer U2) whose access validity period has expired (St43). In accordance with the instruction in step St43, the DB server S1 deletes the corresponding camera access user data Dt12a and returns an Ack to that effect to the user management server S3.

[0078] Based on the Ack received from the DB server S1, the user management server S3 instructs the DB server S1 to delete the user data of the temporary user (e.g., police officer U2) whose access validity period has expired (St44). In accordance with the instruction in step St44, the DB server S1 deletes the user data Dt11a of the police officer U2 and sends an Ack to that effect to the user management server S3.

[0079] After step St44, the valid access period for the temporary user of the surveillance camera system 100 has elapsed. After this valid access period has elapsed, the mobile terminal TB1 is operated by the police officer U2 to request login to the user management server S3 in order to access the surveillance camera system 100 (St45). In response to the request in step St45, the user management server S3 instructs the DB server S1 to request the user data of the police officer U2 (St46). However, because the user data of the police officer U2 was deleted by the DB server S1 in the processing of step St42, the DB server S1 returns a result to the user management server S3 indicating that the user data of the police officer U2 does not exist (St47). The user management server S3 returns a notification to the mobile terminal TB1 indicating that the login in step St45 failed (St48). In other words, the police officer U2 cannot log in to the surveillance camera system 100 (in other words, access is denied). As a result, when the access validity period included in the user data of police officer U2 as a temporary user expires, police officer U2 loses his authority as a temporary user. Therefore, the surveillance camera system 100 can appropriately deny access to the surveillance camera system 100 to police officer U2 who has lost this authority, which contributes to improving security.

[0080] 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 surveillance camera information indicating information about at least one selected surveillance camera selected from the multiple surveillance cameras based on a request from an external user registered to be temporarily available, and authorized user information about an authorized user who has access authority to the video data from the selected surveillance camera. The authorized user is, for example, user U1. The authorized user information is, for example, setting information (e.g., login ID and password) of the authorized user 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, data about setting information for surveillance cameras Ca1 and Ca2. The external user is, for example, police officer U2. The external user information is, for example, data about setting information (e.g., login ID and password) for police officer U2. 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. Based on the process of sharing access permission data with a user terminal (e.g., mobile terminal TB1) based on the external user information of the external user, the server updates the access permission data by adding external user information including the access validity period to the access permission data, 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 to the user terminal based on the external user information only during the access validity period.

[0081] As a result, surveillance camera system 100 can temporarily share surveillance camera video data with a third party (e.g., police officer U2) other than an authorized user (e.g., user U1) by sharing favorite data of at least one surveillance camera selected based on a request from an external user registered as temporarily available. Therefore, surveillance camera system 100 can set mobile terminal TB1 used by a third party who is not an authorized user to be temporarily able to access surveillance camera video data, thereby helping to improve the work efficiency of the third party.

[0082] After the server has completed the sharing process of the access permission data, it causes the second user terminal to display a display screen having thumbnails of the selected surveillance cameras identified by the surveillance camera information linked to the access permission data. This allows the surveillance camera system 100 to access only the video data from the specific surveillance cameras that are necessary for the police officer U2's investigation, etc., and prevents access to video data that is not necessary for the police officer U2's investigation, thereby preventing the leakage of unnecessary video data.

[0083] The access permission data further includes facility information indicating information about the facility where the selected surveillance camera is located. As a result, the favorite data includes setting information data for the store A selected by the first user terminal (for example, the client terminal PC1), making it easy for not only the user U1 but also the police officer U2 to confirm which surveillance camera the video data is from.

[0084] After the access permission data is shared, the server displays the video data of the selected surveillance camera identified by the surveillance camera information linked to the access permission data and the information of the target facility on the first user terminal and the second user terminal in the same screen layout. This allows the police officer U2 who receives the favorite data to view the video data of the selected surveillance camera in the same screen layout, reflecting the preferences of the user U1 who created the favorite data.

[0085] The access permission data includes first access permission data that can be created, edited, or accessed only by a first user terminal (e.g., client terminal PC1) based on the authorized user information, and second access permission data that can be accessed only by a second user terminal (e.g., mobile terminal TB1) based on the external user information. After sharing the first access permission data, the server causes the first user terminal (e.g., client terminal PC1) based on the first user information to display a first display screen that includes video data from a 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 second user terminal (e.g., mobile terminal TB1) based on the second user information to display a second display screen that includes video data from a 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. This allows creation, editing, and access of favorite data to be set individually for authorized users and external users, enabling highly flexible operation of favorite data in a way that reflects each user's preferences. Also, while favorite data is stored in database DB1 so that it differs for each user, the display screen layout preferences of the user who created the favorite data are reflected, and other users who receive the favorite data can view the video data of the selected surveillance camera in a screen format with the same display screen layout.

[0086] The access permission data includes first access permission data that is provided to allow at least one of creation, editing, and access by only a first user terminal (e.g., client terminal PC1) based on authorized user information, and second access permission data that is provided to allow access by only a second user terminal (e.g., mobile terminal TB1) based on external user information. After sharing the first access permission data, the server displays a first display screen on the first user terminal (e.g., client terminal PC1) that includes video data from a 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 the second user terminal (e.g., mobile terminal TB1) that includes video data from a selected surveillance camera identified by the surveillance camera information linked to the second access permission data. This allows creation, editing, and access of favorite data to be set individually for authorized users and external users, enabling highly flexible management of favorite data that reflects each user's preferences. Furthermore, the surveillance camera system 100 allows the police officer U2 to remotely view video data from the surveillance camera that is the monitoring target in the favorite data of the authorized user U1 for monitoring purposes, without having to create his own favorite data.

[0087] Furthermore, when the server detects that the valid access period has expired, it deletes the access permission data corresponding to that valid access period. This allows the surveillance camera system 100 to avoid unnecessary storage of user data for users whose valid access period has expired and who should not be allowed access, thereby effectively securing the capacity of the database DB1.

[0088] After deleting the access permission data, the server also executes a process to deny access from the second user terminal. This allows the surveillance camera system 100 to deny logins by users whose access validity period has expired and who should not be allowed access, thereby preventing unauthorized access to the surveillance camera video data.

[0089] Furthermore, the external user is police officer U2. The video data from the selected surveillance camera is data that police officer U2 is permitted to temporarily access in the course of his duties. This allows surveillance camera system 100 to temporarily permit police officer U2 to view the video data from the surveillance camera that is necessary for the performance of his duties in investigating a crime, etc., thereby contributing to improved investigation efficiency.

[0090] 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]

[0091] The present disclosure is useful for a surveillance camera video sharing system and a surveillance camera video sharing method that enable temporary sharing of surveillance camera video data with a third party different from the user, thereby supporting the third party's business efficiency. [Explanation of symbols]

[0092] 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 surveillance camera information indicating information on at least one selected surveillance camera selected by a user terminal linked to authorized user information of an authorized user so that the selected surveillance camera can be accessed by the user terminal linked to external user information of an external user registered to be allowed temporary use from among the plurality of surveillance cameras, and authorized user information of the authorized user who has access authority to video data of the selected surveillance camera; the server, based on an operation of the external user to share the access permission data with the user terminal linked to the external user information, adds the external user information including an access validity period to the access permission data to the access permission data to update the access permission data, and executes a sharing process to set the video data of the selected surveillance camera identified by the surveillance camera information linked to the access permission data to be accessible to the user terminal linked to the external user information only during the access validity period. Surveillance camera video sharing system.

2. After the access permission data sharing process, the server causes the user terminal associated with the external user information to display a display screen having a thumbnail showing the selected surveillance camera identified by the surveillance camera information associated with the access permission data. The surveillance camera video sharing system according to claim 1 .

3. 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 .

4. After the access permission data sharing process, the server causes a display screen having the 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 to be displayed in the same screen layout on each of the first user terminal linked to the authorized user information and the second user terminal linked to the external user information. The surveillance camera video sharing system according to claim 3 .

5. the access permission data includes first access permission data that is provided to allow at least one of creation, editing, and access only by a user terminal linked to the authorized user information, and second access permission data that is provided to allow access only by a user terminal linked to the external user information, After the sharing process of the first access permission data, the server causes a user terminal associated with the authorized 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 on the target facility, and causes a user terminal associated with the external 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 on 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 3 .

6. the access permission data includes first access permission data that is provided to allow at least one of creation, editing, and access by only a first user terminal associated with the authorized user information, and second access permission data that is provided to allow access by only a second user terminal associated with the external user information, 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 3 .

7. When the server detects that the access validity period has elapsed, it deletes the access permission data corresponding to the access validity period. The surveillance camera video sharing system according to claim 1 .

8. the server, after deleting the access permission data, executes a process of denying access from a user terminal associated with the external user information. The surveillance camera video sharing system according to claim 7.

9. A surveillance camera video sharing method executed by a surveillance camera video sharing system, comprising: a server included in the surveillance camera video sharing system stores access permission data including at least surveillance camera information indicating information on at least one selected surveillance camera selected by a user terminal linked to the authorized user information of an authorized user, among the multiple surveillance cameras installed in the target facility, so that the selected surveillance camera can be accessed by a user terminal linked to the external user information of an external user registered to be allowed temporary use, and the authorized user information of the authorized user who has access authority to the video data of the selected surveillance camera; The server updates the access permission data by adding the external user information including an access validity period to the access permission data based on a sharing operation of the access permission data to the user terminal linked to the external user information, and executes a sharing process that sets the video data of the selected surveillance camera identified by the surveillance camera information linked to the access permission data to be accessible to the user terminal linked to the external user information only during the access validity period. How to share surveillance camera footage.

Images