Method and system for managing monitoring service

Abstract

To appropriately operate a service that provides infrastructure camera images, including images of a monitoring subject, to a communication terminal of a user, while preventing spoofing by a third party.SOLUTION: When receiving an application for use of a monitoring service from a communication terminal of a user of the monitoring service, a management server transmits a request for identity verification to a communication terminal of a monitoring subject. When receiving information that meets the request for identity verification from the communication terminal of the monitoring subject, transmission of infrastructure camera images, including the monitoring subject, to the communication terminal of the user is permitted. The request for identity verification includes taking an image including a face portion of the monitoring subject using the communication terminal of the monitoring subject, and transmitting the captured image of the face portion from the communication terminal of the monitoring subject to the management server.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present disclosure relates to a method and system for managing a service that provides images from infrastructure cameras, including images of a monitored subject, to a user's communication terminal. [Background technology]

[0002] Japanese Patent Application Laid-Open Publication No. 2002-197565 discloses a server that provides images of an infant placed in a facility to the guardian of the infant in a remote location. When this conventional server receives a request for information about the infant from the guardian's terminal, it authenticates whether the request is legitimate. In this authentication, a number preregistered in the server is compared with the number of the guardian's terminal. If the comparison shows that the request is legitimate, the server identifies images from a camera installed in the facility that contain an image of the infant in question and transmits the identified images to the guardian's terminal.

[0003] In addition to JP-A-2002-197565, examples of documents showing the state of the art in the technical field related to the present disclosure include JP-A-2007-060528, JP-A-2004-356816, and JP-A-2006-107187. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2002-197565 A [Patent Document 2] JP 2007-060528 A [Patent Document 3] JP 2004-356816 A [Patent Document 4] JP 2006-107187 A Summary of the Invention [Problem to be solved by the invention]

[0005] Consider a "monitoring service" that uses multiple infrastructure cameras installed indoors and outdoors to provide infrastructure camera images that include images of the person being monitored to a user's communication terminal. In a confined space such as a childcare facility, the people that can be included in the camera images are limited, but this limitation does not exist indoors or outdoors. Therefore, key information is considered to be necessary to identify the camera images that include the image of the person being monitored from the camera images acquired by multiple infrastructure cameras.

[0006] For example, an image containing the characteristics of the person being watched (e.g., a facial photograph) is registered in the server, and when a request to use the service is received from a user's terminal, a search for the person being watched is performed using this registered image as key information. This makes it possible to identify camera images captured by multiple infrastructure cameras that contain the person being watched, and provide these to the user's communication terminal.

[0007] In addition, in the "monitoring service," consent to the monitoring can be obtained from the person being monitored. This is because the person being monitored in the "monitoring service" is assumed to be a person who acts of his or her own volition both indoors and outdoors. The method of obtaining consent to the monitoring can be an approval by the person being monitored using a communication terminal carried by the person being monitored.

[0008] According to the conventional server described above, by authenticating the request, it is possible to prevent an image of the requested child from being provided to a third party who is masquerading as the guardian. It is desirable to prevent this masquerading by a third party in the "monitoring service" as well. However, under the above-mentioned premise of the "monitoring service," if the registered image, which is key information, is illegally obtained by a third party, there is a possibility that an image including the monitored subject will be provided to the third party who is masquerading as the user. Therefore, there is a demand for technological development to prevent such masquerading and to operate the "monitoring service" appropriately.

[0009] One objective of the present disclosure is to provide technology that enables proper operation of a service that provides images from infrastructure cameras, including images of a monitored subject, to a user's communication terminal while preventing impersonation by a third party. [Means for solving the problem]

[0010] A first aspect of the present disclosure is a management method for a monitoring service using an infrastructure camera, and has the following characteristics. The method comprises: When the application for using the monitoring service is received from the communication terminal of the user, the management server transmits a request for identity verification to the communication terminal to be monitored; The method includes a step in which, when information satisfying the request for identity verification is received from the communication terminal of the monitored target, the management server allows the transmission of images from the infrastructure camera including the monitored target to the user's communication terminal. The request for identity verification includes photographing the facial portion of the person being monitored using the communication terminal of the person being monitored, and transmitting a photographed image of the facial portion from the communication terminal of the person being monitored to the management server.

[0011] A second aspect of the present disclosure is a management system for a monitoring service, which has the following characteristics. The management system includes a communication terminal of a user of the monitoring service, a communication terminal of the monitored target, and a management server that communicates with the communication terminals of the user and the monitored target. The management server includes: When the application for using the monitoring service is received from the communication terminal of the user, a request for identity verification is transmitted to the communication terminal of the monitoring target; When information satisfying the request for identity verification is received from the communication terminal of the monitoring target, transmission of an image of the infrastructure camera including the monitoring target to the communication terminal of the user is permitted. It is structured as follows. The request for identity verification includes photographing the facial portion of the person being monitored using the communication terminal of the person being monitored, and transmitting a photographed image of the facial portion from the communication terminal of the person being monitored to the management server. Effect of the Invention

[0012] According to the present disclosure, it is possible to prevent an image captured by an infrastructure camera including an image of a monitored target from being provided to a third party who is posing as at least one of a user of a monitoring service and a monitored target, thereby enabling the monitoring service to be operated appropriately. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram for explaining an overview of a monitoring service. [Diagram 2] FIG. 1 is a diagram illustrating a problem with a monitoring service. [Diagram 3] FIG. 3 is a diagram for explaining an example of a measure to address the problem described in FIG. 2. [Figure 4] FIG. 11 is a diagram illustrating another problem with the monitoring service. [Diagram 5] FIG. 1 is a diagram illustrating a spoofing countermeasure technique according to an embodiment. [Figure 6] 11 is a flowchart showing an example of processing by a management server that is particularly related to the embodiment. [Figure 7] 11 is a flowchart showing an example of processing by a management server that is particularly related to the embodiment. [Figure 8] 11 is a flowchart showing a first processing example related to registration of a new terminal by a management server. [Figure 9] 13 is a flowchart showing a second processing example related to the registration of a new terminal by the management server 10. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In each drawing, the same or corresponding parts are denoted by the same reference numerals, and the description thereof will be simplified or omitted.

[0015] 1. Monitoring service FIG. 1 is a diagram for explaining an overview of the monitoring service. The monitoring service is a service that identifies a camera image IM_CA including an image IMG_TG of a monitoring target TG from among camera images IM_CA acquired by a plurality of infrastructure cameras constituting an infrastructure camera group 20 (a whole-body image IMG_TGB in the example shown in FIG. 1), and provides the identified camera image IM_CA to a communication terminal (hereinafter also referred to as a "user terminal") 30 of a user US. Here, the user US is a person who uses the monitoring service. The monitoring target TG is a person whom the user US wishes to watch over (for example, a family member of the user US, a friend of the user US, or a person cared for by the user US).

[0016] Fig. 1 is also a diagram showing an example of the overall configuration of a management system for a monitoring service according to an embodiment. In the example shown in Fig. 1, the management system includes a management server 10, an infrastructure camera group 20, a user terminal 30, and a communication terminal of a TG to be monitored (hereinafter also referred to as a "target terminal") 40. The infrastructure camera group 20, the user terminal 30, and the target terminal 40 communicate with the management server 10 via a communication line network (not shown). The communication line network is not particularly limited, and wired and wireless networks may be used.

[0017] The management server 10 includes a data processing device 11 and a database 12. The data processing device 11 includes at least one processor and at least one memory. The processor includes a CPU (Central Processing Unit). The memory is a volatile memory such as a DDR memory, and expands various programs used in various processes performed by the processor and temporarily stores various data. The various data used by the processor includes data stored in the database 12.

[0018] The database 12 is formed in a predetermined storage device (e.g., a hard disk, a flash memory). The database 12 stores user data USR and camera data CAM. The user data USR is transmitted from the user terminal 30 to the management server 10. The user data USR includes identification information of the user US and identification information of the monitoring target TG. The camera data CAM includes identification information of each of the multiple infrastructure cameras constituting the infrastructure camera group 20, position information of these infrastructure cameras, camera images IM_CA acquired by each of these infrastructure cameras, and the like.

[0019] The infrastructure camera group 20 includes a plurality of infrastructure cameras. These infrastructure cameras include not only infrastructure cameras installed outdoors but also infrastructure cameras installed indoors. The shooting ranges of two or more infrastructure cameras may overlap partially or entirely. Each infrastructure camera acquires a camera image IM_CA. The camera image IM_CA is typically a video, but may also be a still image. Each infrastructure camera also transmits the acquired camera image IM_CA to the management server 10 together with its own identification information.

[0020] The user terminal 30 is a terminal with communication capabilities, such as a smartphone, tablet, or notebook computer carried by the user US. The user terminal 30 is used when the user US uses the monitoring service for the first time. At the first use, an application AFU (Application For Use) for using the monitoring service is sent from the user terminal 30 to the management server 10. The application AFU includes user data USR including identification information of the user US and identification information of the TG to be monitored. When the user data USR is registered in the database 12, the monitoring service can be used.

[0021] Examples of the identification information of the user US include attribute information of the user US (e.g., name, sex, age) and identification information of the user terminal 30. Examples of the identification information of the monitored TG include a facial image IMG_TGF of the monitored TG. This facial image IMG_TGF is information particularly necessary for monitoring the monitored TG. Therefore, when an application AFU is received in which the facial image IMG_TGF is missing, the management server 10 may request the user terminal 30 to transmit a captured image of the facial portion of the monitored TG before registering the user data USR included in this application AFU in the database 12. The identification information of the monitored TG may include identification information of the target terminal 40 and relationship information between the user US and the monitored TG (e.g., family, friends, people cared for by the user US).

[0022] The user terminal 30 is also used when the user US uses the monitoring service for the second or subsequent times. When using the service for the second or subsequent times, a request for provision (RFP) for information on the TG to be monitored is sent from the user terminal 30 to the management server 10. The request RFP includes, for example, login information for the user US to access the database 12. The request RFP may also include information for updating some or all of the data of the user data USR registered in the database 12. When such update information is included in the request RFP, the user data USR registered in the database 12 is updated.

[0023] The target terminal 40 is, for example, a terminal having a communication function, such as a smartphone or a wearable device carried by the TG to be monitored. The target terminal 40 also has a camera function. By having the communication function and the camera function, the target terminal 40 transmits camera images taken by the target terminal 40 to an external device (for example, the management server 10, the user terminal 30). The target terminal 40 may have a GPS (Global Positioning System) function. By having the GPS function, the target terminal 40 transmits location information of the target terminal 40 to an external device.

[0024] 2. Features of the embodiment 2-1. Issues with monitoring services FIG. 2 is a diagram for explaining the problems of the monitoring service. In the monitoring service described in FIG. 1, the face image IMG_TGF of the monitoring target TG is included in the requested AFU. Therefore, it is considered possible to exclude the requested AFU by a third party TP that has no relationship with the monitoring target TG. However, it is possible for the third party TP to obtain the face image IMG_TGF by some method. If the third party TP that has obtained the face image IMG_TGF masquerades as the user US and maliciously submits the requested AFU and the requested RFP, it becomes possible to view the camera image IM_CA that includes the image IMG_TG.

[0025] FIG. 3 is a diagram for explaining a countermeasure example for the problem described in FIG. 2. In the countermeasure example shown in FIG. 3, when the management server 10 accepts a request RFP, a request RFR (Request For Reply) as a reply to the request RFP is transmitted from the management server 10 to the target terminal 40. Then, when a reply AR (Approve Reply) approving the provision of information is received from the target terminal 40, the camera image IM_CA including the image IMG_TG is provided to the user US who sent the request RFP. On the other hand, when a reply DR (Disapprove Reply) disapproving the provision of information is received from the target terminal 40, the camera image IM_CA is not provided. The camera image IM_CA is not provided when there is no reply to the request RFR either.

[0026] 2-2. Other issues with monitoring services 3, the TG to be watched over can transmit a reply RTR by operating the target terminal 40. Therefore, for example, when the TG to be watched over determines that there has been a request RFP from a malicious third party TP based on the state of the TG to be watched over when the target terminal 40 receives the request RFR, it is possible to avoid providing the camera image IM_CA to the third party TP by not replying to the request RFR or by transmitting a reply DR.

[0027] However, there may be a case where the third party TP masquerades as the user US and the monitoring target TG. Fig. 4 is a diagram for explaining another problem with the monitoring service. In the example shown in Fig. 4, the third party TP transmits an application AFU and a request RFP. In addition, the third party TP transmits a response AR in response to a request RFR transmitted by the management server 10 that has accepted the request RFP. When such masquerading occurs, the camera image IM_CA including the image IMG_TG is provided to the third party TP.

[0028] 2-3. Request for identity verification In view of these problems, in an embodiment, when the management server 10 accepts an application AFU, a request for identity verification RFKYC (Request For Know Your Customer) is transmitted from the management server 10 to the target terminal 40. FIG. 5 is a diagram illustrating an anti-spoofing method according to an embodiment. In the example shown in FIG. 5, the management server 10 that accepts the application AFU transmits a request RFKYC to the target terminal 40. In this example, the request RFKYC, which includes acquisition of a photographed image IMG_F of the face of the person using the built-in camera of the target terminal 40 and transmission of the photographed image IMG_F using the target terminal 40, is transmitted to the target terminal 40.

[0029] When the target terminal 40 receives the RFKYC request, the TG to be watched over takes an image of its own face in accordance with the RFKYC request and transmits the captured image IMG_F. This enables the management server 10 to determine that a series of actions performed in accordance with the RFKYC request were performed by the TG to be watched over.

[0030] The mechanism of online identity verification (electric Know Your Customer) itself is publicly known. However, according to the method shown in FIG. 5, a request RFKYC is sent to the target terminal 40 in response to an application AFU from the user terminal 30, and identity verification is performed using the captured image IMG_F from the target terminal 40. If information satisfying the request RFKYC (i.e., the captured image IMG_F) is obtained, and the camera image IM_CA is permitted to be sent to the user terminal 30, it is possible to prevent the camera image IM_CA including the image IMG_TG from being provided to a third party TP impersonating the user US and the monitoring target TG.

[0031] In the method shown in FIG. 5, a request RFKYC including taking a photographed image IMG_F of the face of the person and transmitting this photographed image IMG_F was transmitted to the target terminal 40. The photographed image IMG_F of the face may be a photograph of a desired movement (nodding movement) such as moving the face a random number of times in random directions (for example, right, left, left three times). In this case, the photographed image IMG_F obtained by photographing the desired movement is obtained as information that satisfies the request RFKYC. This makes it possible to improve the accuracy of identity verification.

[0032] 2-4. Request for Association In an embodiment, when the management server 10 accepts the application AFU, a request for association RFA (Request For Association) may be transmitted from the management server 10 to the user terminal 30. The request RFA is a request for associating a new communication terminal (hereinafter also referred to as a "new terminal") with the user terminal 30. Then, when information satisfying the request RFA is obtained, the new communication terminal may be registered as a target terminal 40 based on this information.

[0033] As described above, the application AFU may include identification information of the target terminal 40 as identification information of the monitoring target TG. By acquiring the identification information of the target terminal 40 in response to the request RFA, the effort required of the user US to register the target terminal 40 can be reduced. In addition, if the target terminal 40 is registered based on the request RFA, it is expected that the effect of avoiding the provision of the camera image IM_CA to the third party TP will be enhanced by combining it with the method using the request RFKYC described above.

[0034] In the first example, the request RFA includes acquiring the terminal information TID of the new terminal by short-distance communication between the user terminal 30 and the new terminal, and transmitting the terminal information TID from the user terminal 30 to the management server 10. In this first example, it is assumed that the user terminal 30 and the new terminal are in the same space when transmitting the application AFU. Therefore, according to the first example, it is possible to exclude the application AFU by a third party TP that attempts to acquire a camera image IM_CA including an image IMG_TG using a single communication terminal.

[0035] In the second example, the request RFA includes reading by the new terminal of the connection information CNC output from the user terminal 30, and connecting by the new terminal to the management server 10 based on the connection information CNC. The connection information CNC is information on the connection destination of the management server 10 (i.e., the management server 10). The connection information CNC is output from the user terminal 30 by, for example, displaying a QR code (registered trademark) representing the connection information CNC on the display of the user terminal 30. In this second example, it is also assumed that the user terminal 30 and the new terminal are in the same space when the application AFU is transmitted. Therefore, according to the second example, the same effect as the first example is expected.

[0036] 3. Example of processing by the management server 6 and 7 are flowcharts showing an example of processing particularly related to the embodiment by the management server 10 (the processor of the data processing device 11). The routines shown in Figs. 6 and 7 are executed repeatedly at predetermined intervals, for example.

[0037] 6, first, it is determined whether or not an application AFU has been received (step S11). If the determination result of step S11 is positive, processing of step S12 is performed. In the processing of step S12, user data USR (such as face image IMG_TGF) included in the application AFU acquired in the processing of step S11 is registered in the database 12.

[0038] Following the process of step S12, the process of step S13 is performed. In the process of step S13, a request RFKYC is transmitted to the target terminal 40. As described above, the request RFKYC includes obtaining a captured image IMG_F of the face portion of the person and transmitting this captured image IMG_F.

[0039] In the example shown in FIG. 6, in the process of step S13, the identification information UID is transmitted together with the request RFKYC. The identification information UID is information specific to the user terminal 30 and is arbitrarily added to the request RFKYC. An example of the identification information UID is a password set between the user US and the monitoring target TG. The identification information UID is added, for example, when the request RFP is transmitted. Such identification information UID can provide the monitoring target TG with information to determine that the request RFKYC transmitted to the target terminal 40 was not transmitted in response to the request RFP by the third party TP. In addition, when there are multiple users US who wish to monitor the monitoring target TG, the monitoring target TG can guess who the user US who transmitted the request RFP is by changing the identification information UID for each user US.

[0040] Following the process of step S13, the process of step S14 is performed. In the process of step S14, the captured image IMG_F received from the corresponding terminal 40 in response to the process of step S13 is compared with the facial image IMG_TGF included in the user data USR received in the process of step S11. If the captured image IMG_F and the facial image IMG_TGF match, the determination result of step S14 is positive. If the determination result of step S14 is positive, the process of step S15 is performed. In the process of step S15, the transmission of the camera image IM_CA to the user terminal 30 is permitted.

[0041] If the determination result in step S14 is negative, the process of step S16 is performed. In the process of step S16, the transmission of the camera image IM_CA to the user terminal 30 is not permitted. In addition, the reason for not permitting the transmission is transmitted to the terminal from which the application AFU was transmitted (e.g., the user terminal 30, the communication terminal of the third party TP). An example of this reason is that the captured image IMG_F and the face image IMG_TGF do not match.

[0042] 7, first, it is determined whether or not a request RFP has been received (step S21). As described above, the request RFP includes login information of the user US for accessing the database 12. If the determination result of step S21 is positive, the process of step S22 is performed.

[0043] In the process of step S22, the monitoring target TG is searched for from the camera image IM_CA stored in the database 12. In this search, the database 12 is searched using the login information received in the process of step S21 as a key, and the facial image IMG_TGF included in the user data USR corresponding to the login information is identified. Then, the database 12 is searched using this facial image IMG_TGF as a key, and a camera image IM_CA including an image of a person matching the person in the facial image IMG_TGF and the infrastructure camera that acquired this camera image IM_CA are identified. The identified camera image IM_CA is the camera image closest to the current time, that is, the most recent camera image.

[0044] It is assumed that the monitoring target TG will continue to move. Therefore, the process of step S22 is repeatedly executed. As a result, the infrastructure cameras that have acquired camera images IM_CA that include an image of a person matching the person in the facial image IMG_TGF are repeatedly identified. The total number of infrastructure cameras identified may be two or more. The reason for this is that when the shooting ranges of two or more infrastructure cameras overlap in part or in whole, there is a possibility that camera images IM_CA that include an image of a person matching the person in the facial image IMG_TGF will be acquired separately by these infrastructure cameras.

[0045] If the location information of the target terminal 40 is available, in the process of step S22, this location information may be used to narrow down the infrastructure cameras that search for the monitoring target TG. In this narrowing down, at least one infrastructure camera installed near the current location of the target terminal 40 is extracted. Then, from the camera images IM_CA of this at least one infrastructure camera, a camera image IM_CA that includes an image of a person that matches the person in the face image IMG_TGF is specified.

[0046] Following the process of step S22, the process of step S23 is performed. In the process of step S23, it is determined whether or not the TG to be monitored has been identified. If the determination result of step S23 is negative, the process of step S24 is performed. In the process of step S24, a reason for not transmitting the camera image IM_CA is transmitted to the terminal that sent the request RFP (i.e., the user terminal 30). An example of this reason is that the TG to be monitored could not be identified.

[0047] If the determination result in step S23 is positive, the process proceeds to step S25. In the process of step S25, the camera image IM_CA is transmitted to the terminal that transmitted the request RFP (that is, the user terminal 30).

[0048] 8 and 9 are flowcharts showing first and second processing examples related to the registration of a new terminal by the management server 10 (the processor of the data processing device 11). The routines shown in Figs. 8 and 9 are executed instead of the processing of steps S11 and 12 shown in Fig. 6, or are executed in parallel with the execution of the processing of steps S11 and 12. The routines shown in Figs. 8 and 9 are executed repeatedly at predetermined intervals, for example.

[0049] In the example shown in Fig. 8, first, it is determined whether or not an application AFU has been received (step S31). If the determination result of step S31 is positive, processing of step S32 is performed. In the processing of step S32, an association request RFA1 is transmitted. The request RFA1 includes obtaining terminal information TID and transmitting the terminal information TID from the user terminal 30 to the management server 10.

[0050] Following the processing of step S32, it is determined whether or not the terminal information TID has been received (step S33). The processing of step S33 is performed, for example, based on whether or not the management server 10 has received the terminal information TID within a predetermined time (for example, 1-2 minutes) from the time when the processing of step S22 was performed. If the determination result of step S33 is negative, the processing of step S34 is performed. In the processing of step S34, a reason for not allowing the registration of a new terminal is transmitted to the terminal that transmitted the application AFU (for example, the user terminal 30, the communication terminal of the third party TP). An example of this reason is that the terminal information TID was not transmitted.

[0051] If the determination result of step S33 is positive, the process of step S35 is performed. In the process of step S35, the terminal information TID acquired in the process of step S33 is registered in the database 12 together with the user data USR (such as the face image IMG_TGF) included in the application AFU acquired in the process of step S31.

[0052] In the example shown in Fig. 9, first, it is determined whether or not an application AFU has been received (step S41). If the determination result of step S41 is positive, processing of step S42 is performed. In the processing of step S42, an association request RFA2 is transmitted. The request RFA2 includes reading by the new terminal of the connection information CNC output from the user terminal 30, and connection by the new terminal to the management server 10 based on the connection information CNC.

[0053] Following the processing of step S42, the processing of step S43 is performed. In the processing of step S43, it is determined whether or not there has been a connection from a new terminal. The processing of step S43 is performed, for example, based on whether or not there has been a connection from the new terminal to the management server 10 within a predetermined time (e.g., 1-2 minutes) since the processing of step S42 was performed. If the determination result of step S43 is negative, the processing of step S44 is performed. In the processing of step S44, the reason for not allowing the registration of the new terminal is transmitted to the terminal that transmitted the application AFU (e.g., the user terminal 30, the communication terminal of the third party TP). An example of this reason is that there has been no connection from the new terminal.

[0054] If the determination result of step S43 is positive, the process of step S45 is performed. In the process of step S45, the terminal information (i.e., the terminal information TID) of the new terminal connected to the management server 10 in the process of step S43 is registered in the database 12 together with the user data USR (such as the face image IMG_TGF) included in the application AFU acquired in the process of step S41. [Explanation of symbols]

[0055] 10... Management server, 11... Data processing device, 12... Database, 20... Group of infrastructure cameras, 30... User terminal, 40... Target terminal, TG... Target to be monitored, TP... Third party, US... User of monitoring service, AFU... Application for use, CAM... Camera data, CNC... Connection information, TID... Terminal information of new terminal, UID... Identification information specific to user terminal 30, USR... User data, RFA, RFA1, RFA2... Association request, RFP... Request for information regarding TG to be monitored, RFR... Request for response to RFP request, RFKYC... Request for identity verification, IMG_F... Photographed image of face, IMG_TG... Image of TG to be monitored, IMG_TGB... Whole-body image of TG to be monitored, IMG_TGF... Facial image of TG to be monitored

Claims

1. A method for managing a monitoring service using an infrastructure camera, comprising: When the application for using the monitoring service is received from the communication terminal of the user, the management server transmits a request for identity verification to the communication terminal to be monitored; when information satisfying the request for identity verification is received from the communication terminal of the monitoring target, the management server permits transmission of an image of the infrastructure camera including the monitoring target to the communication terminal of the user; Including, The request for identity verification includes taking an image including a facial portion of the target being monitored using the communication terminal of the target being monitored, and transmitting a captured image of the facial portion from the communication terminal of the target being monitored to the management server. A monitoring service management method comprising:

2. The management method according to claim 1, The request for photographing the face part included in the request for identity verification includes photographing a desired movement of the face part. A monitoring service management method comprising:

3. The management method according to claim 1 or 2, When the application for using the monitoring service is received from the communication terminal of the user, the management server transmits an association request to the communication terminal of the user to register a new communication terminal to be associated with the communication terminal of the user; When information satisfying the association request is received from the user's communication terminal or the new communication terminal, the management server registers the new communication terminal as the communication terminal to be monitored based on the information satisfying the association request; Further includes A monitoring service management method comprising:

4. The management method according to claim 3, The request for association includes acquiring terminal information of the new communication terminal through short-range communication between the user's communication terminal and the new communication terminal, and transmitting the terminal information of the new communication terminal to the management server. A monitoring service management method comprising:

5. The management method according to claim 3, The request for association includes reading, by the new communication terminal, connection information output from the communication terminal of the user, and connecting, by the new communication terminal, to the management server based on the connection information. A monitoring service management method comprising:

6. A management system for a monitoring service using an infrastructure camera, A communication terminal of a user of the monitoring service; A communication terminal to be monitored; A management server that communicates with the user and the communication terminal to be monitored; Equipped with The management server includes: When the application for using the monitoring service is received from the communication terminal of the user, a request for identity verification is transmitted to the communication terminal of the monitoring target; When information satisfying the request for identity verification is received from the communication terminal of the monitoring target, transmission of an image of the infrastructure camera including the monitoring target to the communication terminal of the user is permitted. It is configured as follows: The request for identity verification includes taking an image including a facial portion of the target being monitored using the communication terminal of the target being monitored, and transmitting a captured image of the facial portion from the communication terminal of the target being monitored to the management server. A monitoring service management system comprising:

Images