JP6534585B2 - Loss prevention system - Google Patents

Description

  The present invention relates to a loss prevention system for preventing loss of an article.

  As a mechanism to prevent the article from being lost, a wireless tag is attached to the article and the portable terminal and the wireless tag are coupled, and it is detected that the distance between the two has become equal to or longer than a predetermined distance. Some mobile devices send alerts. The following patent documents 1-2 disclose an example of such a loss prevention system.

  The following Non-Patent Documents 1 and 2 describe the loss prevention tag. In addition to sending an alert when the connection between the mobile device and the tag is broken, the tag can also display the time and place of the break on the mobile device.

JP, 2009-213036, A JP, 2008-077477, A

"Bluetooth 4.0 + LE compatible loss prevention tag REX-SEEK 2", URL: http://www.ratocsystems.com/products/subpage/seek2.html (October 13, 2015 acquisition) "I tried using the Bluetooth loss prevention tag ♪", URL: http://k-tai.impress.co.jp/docs/column/stapa/20150601_704510.html (October 13, 2015 acquisition)

  The techniques described in Patent Documents 1 and 2 and Non-Patent Documents 1 and 2 are considered to be useful when an individual prevents loss of an article. On the other hand, with regard to articles owned by a company and loaned to employees, it may be required that the company immediately grasps and copes with it when it is lost. For example, consider the case where a laptop is lent to an employee. If data that should not be leaked is stored in the notebook PC, it is necessary to immediately take measures as the loss of this data may develop into the trust problem of the company.

  Since the techniques described in Patent Documents 1 and 2 and Non-Patent Documents 1 and 2 send an alert from a tag or a portable terminal when the distance between the article and the tag is large, the holder of the article immediately It is expected to notice that. However, when the item is lent by the company, it is difficult for the company to immediately grasp that the item has been lost (or lost). Therefore, it may be delayed for the company to take appropriate measures.

  Further, since the techniques described in Patent Documents 1 and 2 and Non-patent Documents 1 and 2 rely on an alert transmitted by a tag or a portable terminal, for example, when any of these power supplies is interrupted, the alert functions It disappears. With regard to articles owned by a company, it is considered desirable that the company can issue an alert when the article is lost.

  The present invention has been made in view of the above problems, and an object of the present invention is to provide a loss prevention system suitable for preventing the loss of articles owned by a company.

  The loss prevention system according to the present invention stores a loss report to the effect that an article has been lost in a server received from a wireless terminal, and sends an alert from the server to the wireless terminal if there is no discovery report from the wireless terminal Do.

  According to the loss prevention system of the present invention, it is possible to immediately grasp that the article has been lost on the server side. As a result, a person other than the holder of the article (for example, an article manager in a company) can easily grasp the loss of the article.

FIG. 1 is a block diagram of a loss prevention system 1000 according to a first embodiment. It is a figure which shows the structure and data example of registration data 310. FIG. It is a figure which shows the structure and data example of tag management data 410. FIG. It is a figure which shows the structure and data example of the loss management data 420. FIG. It is a figure which shows the structure of goods data 430, and an example of data. It is a figure showing composition of employee data 440, and an example of data. It is a figure which shows the structure and data example of the notification management data 450. FIG. FIG. 6 is an operation flow diagram for explaining the operation of the loss prevention system 1000; FIG. 7 is a configuration diagram of a loss prevention system 1000 according to a second embodiment. FIG. 14 is an operation flow diagram for explaining the operation of the loss prevention system 1000 in the second embodiment. FIG. 7 is a configuration diagram of a loss prevention system 1000 according to a third embodiment. FIG. 18 is an operation flowchart illustrating the operation of the loss prevention system 1000 in the third embodiment. FIG. 14 is a configuration diagram of a loss prevention system 1000 according to a fourth embodiment. FIG. 18 is an operation flowchart illustrating the operation of the loss prevention system 1000 in the fourth embodiment.

Embodiment 1
FIG. 1 is a block diagram of the loss prevention system 1000 according to the first embodiment of the present invention. The loss prevention system 1000 is a system that prevents the article 100 from being lost. The loss prevention system 1000 includes a loss prevention tag 200, a smartphone 300, and a server 400. The smartphone 300 and the server 400 can communicate via an appropriate network (eg, the Internet).

  The loss prevention tag 200 is a wireless tag that prevents the article 100 from being lost by being attached to the article 100. The loss prevention tag 200 stores a tag ID 210 for identifying itself.

  The smartphone 300 is a portable terminal carried by the holder of the article 100. The owner pairs the smartphone 300 and the loss prevention tag 200 (for example, the tag ID 210 of the loss prevention tag 200 is stored in the smartphone 300). Thereby, for example, an alarm sound can be transmitted from at least one of the smartphone 300 and the loss prevention tag 200 when the distance between the two is greater than the set value, and the loss of the article 100 can be prevented.

  The cooperation between the loss prevention tag 200 and the smartphone 300 can suppress the loss of the article 100 to some extent. Further, in the present invention, assuming a case in which an organization (for example, a company) lends an article 100, a mechanism has been devised in which the lender can immediately grasp the loss of the article 100. Therefore, the smart phone 300 registers predetermined registration data 310 in the server 400 so that the server 400 can immediately grasp the loss of the article 100. The details of the registration data 310 will be described later.

  The server 400 is, for example, a server computer managed by a company that lends the article 100. The server 400 is a server that manages the article 100 and the loss prevention tag 200 attached thereto. The server 400 includes a storage device for storing tag management data 410, loss management data 420, article data 430, employee data 440, and notification management data 450. The server 400 further includes a registration unit 460, an alert unit 471, and a notification unit 472. Details of these data and function units will be described later.

  FIG. 2 is a diagram showing the configuration of the registration data 310 and an example of the data. The registration data 310 is data that the holder of the smartphone 300 inputs, for example, on the smartphone 300 in order to register information on the article 100 and the loss prevention tag 200 in the server 400. The application for inputting the registration data 310 and transmitting it to the server 400 may be configured as part of an application for pairing the loss prevention tag 200 and the smartphone 300, for example, but is not limited thereto.

  The registration data 310 includes a tag ID 311, an article ID 312, a terminal ID 313, and an employee ID 314. The tag ID 311 is obtained by acquiring the tag ID 210 from the loss prevention tag 200, and can be acquired, for example, at the time of pairing. The item ID 312 is an ID for identifying the item 100. The item ID 312 can be notified from the company to the holder, for example, when the item 100 is lent. The terminal ID 313 is an ID for identifying the smartphone 300, and can be notified from a company as in the case of the item ID 312, or can be stored in advance in an appropriate storage device in the smartphone 300. The employee ID 314 is the ID of the owner of the company, and can use, for example, a login ID when the owner logs in to the in-house information system.

  After the owner of the smartphone 300 pairs the loss prevention tag 200 with the smartphone 300, each field of the registration data 310 is input and transmitted to the server 400. When a plurality of articles 100 exist, registration data 310 is created according to the number and transmitted to server 400.

  FIG. 3 is a view showing the configuration of the tag management data 410 and an example of the data. The registration unit 460 receives the registration data 310 from the smartphone 300 and stores it as tag management data 410. The configuration of the tag management data 410 is the same as the registration data 310. When the registration data 310 is created for each of the plurality of articles 100, a plurality of (or a plurality of records) tag management data 410 is also stored correspondingly.

  FIG. 4 is a diagram showing the configuration of the loss management data 420 and an example of the data. The loss management data 420 is data for managing a record in which the article 100 is lost. When the distance between the loss prevention tag 200 and the smartphone 300 is greater than the set value, the smartphone 300 transmits a loss report to that effect to the server 400. The server 400 writes the content of the lost report as a record of lost management data 420.

  The loss management data 420 includes a lost ID 421, a tag ID 422, a lost date 423, a lost location 424, a found date 425, and a found location 426. The lost ID 421 is an ID for identifying each record. The tag ID 422 is a tag ID 210 of the loss prevention tag 200 attached to the lost item 100. The lost date and time 423 and the lost place 424 respectively record the date and time and place where the article 100 was lost. The date of discovery 425 and the location of discovery 426 record the date and time of discovery of the lost item 100 and the location, respectively.

  When the smartphone 300 transmits a loss report indicating that the article 100 is lost to the server 400, the smartphone 300 acquires the position of the smartphone 300 using, for example, a GPS (Global Positioning System) function. The smartphone 300 transmits the tag ID 311 input in the registration data 310 in association with the article 100 having a distance greater than the set value, the position (for example, latitude and longitude) acquired from the GPS, and the transmission date as content of the loss report. . The server 400 stores the information described in the loss report in the loss ID 421 to the loss location 424.

  The holder of the smartphone 300 notices that the article 100 is lost due to an alert sound transmitted from either the loss prevention tag 200 or the smartphone 300, and searches for the article 100 with a search function provided by the loss prevention tag 200, for example. When the article 100 is found, the holder reports the fact to the server 400 via the smartphone 300. At this time, the smartphone 300 acquires the position by GPS or the like, and transmits the position to the server 400 together with the report date and time. The server 400 stores the information described in the report transmitted by the smartphone 300 in the discovery date 425 and the discovery location 426.

  FIG. 5 is a view showing the configuration of the item data 430 and an example of the data. The item data 430 is data for managing the item 100, and includes an item ID 431 and an item type 432. The item ID 431 holds a value corresponding to the item ID 312. The item type 432 holds the type of the item 100.

  FIG. 6 is a diagram showing the configuration of the employee data 440 and an example of the data. The employee data 440 is data for managing employee information in a company or the like to which the possessor of the article 100 belongs, and has an employee ID 441 and a notification destination 442. The employee ID 441 is an ID of a possessor in the company or the like, and corresponds to the employee ID 314. The notification destination 442 holds a destination that should be notified when there is no report that the item 100 has been found. This notification will be described later.

  FIG. 7 is a view showing a configuration of notification management data 450 and an example of the data. The notification management data 450 is data for managing a history of alerts transmitted from the server 400 to the smartphone 300 or a notification destination described later. Each alert will be described later.

  The notification management data 450 includes a lost ID 451, an alert count 452, an alert date 453, and a notification date 454. The lost ID 451 corresponds to the lost ID 421. The number of times of alert 452 is the number of times the alert unit 471 has sent an alert to the smartphone 300. The alert date 453 is the date when the alert unit 471 last transmitted an alert to the smartphone 300. The notification date 454 is the date when the notification unit 472 transmits an alert to a notification destination described later.

  FIG. 8 is an operation flow diagram for explaining the operation of the loss prevention system 1000. For convenience of description, some components are omitted from the drawings. Each step of FIG. 8 will be described below.

(Figure 8: Step (1): leave)
For example, when the holder of the article 100 misplaces the article 100, the distance between the loss prevention tag 200 attached to the article 100 and the smartphone 300 carried by the holder is increased.

(Figure 8: Step (2): Lost Report)
When the distance between the loss prevention tag 200 and the smartphone 300 becomes equal to or greater than a preset value, one or both of the loss prevention tag 200 and the smartphone 300 alert the holder by emitting an alert sound or the like. Do. Furthermore, the smartphone 300 transmits, to the server 400, a loss report indicating that the article 100 is lost. The server 400 receives the loss report and writes a record describing the content of the loss report in each field to the loss management data 420.

(Figure 8: Step (2): Loss Report: Supplement)
This step is significant in that the server 400 can recognize that the article 100 has been lost. Only by pairing of the loss prevention tag 200 and the smartphone 300, the holder of the article 100 only receives a warning by alert sound or the like, and it is delayed that the company lent the article 100 recognizes the loss. Therefore, in this step, it is decided to report a loss to the server 400. As a result, since the loss management data 420 is recorded on the server 400, an administrator or the like can immediately grasp the loss.

(Figure 8: Step (3): Alert)
When the owner of the article 100 finds the article 100, the owner of the article 100 transmits a discovery report to that effect to the server 400 via the smartphone 300. When the server 400 does not receive the discovery report from the smartphone 300 after the server 400 receives the loss report in step (2) and until a preset period (for example, 30 minutes) elapses, the alert unit 471 detects the discovery report. Send an alert to 300. As the destination of the alert, for example, an e-mail address of the smartphone 300 may be recorded on the server 400 in advance by using the terminal ID 313 or the employee ID 314 as a key. The alert unit 471 further records a record regarding the alert in the notification management data 450.

(Figure 8: Step (3): Alert: Supplement)
In addition to the alerting by the pairing of the loss prevention tag 200 and the smart phone 300, this step has the meaning of alerting newly from the server 400 side which grasped loss. For example, when the owner does not notice the alert sound emitted from the loss prevention tag 200, this step is effective.

(Figure 8: Step (4): Notification)
The notification unit 472 notifies the notification destination 442 that the alert has been transmitted to the smartphone 300. After performing step (3) a predetermined number of times, notification may be made, or when step (3) is initially performed, notification may be made in parallel with this. May be

(Figure 8: Step (4): Notification: Supplement)
This step is significant in notifying a person other than the holder of the lost item 100 of the loss. That is, since it is possible that the owner himself is not aware of the loss when reaching this step, the detection is promoted by alerting another person.

Second Embodiment
FIG. 9 is a block diagram of the loss prevention system 1000 according to the second embodiment of the present invention. In the second embodiment, the article 100 is a security card used to pass through the entrance gate of the building. The security card stores, for example, an ID unique to the card, and the entry gate authenticates the ID so that the holder can pass through the entry gate and enter the building. There is.

  When a company lends an article 100 (security card), the company stores the ID stored in the article 100 as an article ID 431 in advance. The holder of the article 100 may input the article ID 312 when transmitting the registration data 310 or, for example, by registering the correspondence between the article ID 431 and the employee ID 414 on the server 400 in advance. You may omit. Furthermore, the smartphone 300 may read the ID in the security card and use it as the item ID 312.

  The loss prevention system 1000 is connected to an entrance management system 510 for controlling an entrance gate for entrance using the article 100. The entrance management system 510 can be configured as part of the loss prevention system 1000 or can be configured as a system different from the loss prevention system 1000.

  The loss prevention system 1000 further includes a card control unit 481. The card control unit 481 prohibits the user from using the article 100 by invalidating the article 100 when the article 100 is lost. The card control unit 481 can be disposed on the server 400 or can be disposed on the entrance management system 510. In FIG. 9, the card control unit 481 is disposed on the entrance management system 510, and the card control unit 481 and the server 400 communicate with each other to perform cooperative operation.

  The configuration other than the above is the same as that of the first embodiment. In the following, differences in the second embodiment will be mainly described.

  FIG. 10 is an operation flow diagram for explaining the operation of the loss prevention system 1000 according to the second embodiment. For convenience of description, some components are omitted from the drawings. Steps (1) to (4) are the same as in FIG. Each step added in FIG. 10 will be described below.

(Figure 10: Step (5): Acquisition)
The card control unit 481 periodically (eg, every 10 minutes) refers to the notification management data 450. The card control unit 481 acquires the record of the corresponding loss management data 420 by using the loss ID 451 as a key when the alert count 452 has reached a predetermined count (for example, the number of times the notification unit 472 sends a notification), and further tags The employee ID 414 and the corresponding item ID 431 are acquired using the ID 422 as a key.

(Figure 10: Step (5): Acquisition: Supplement)
In FIG. 10, in view of the fact that the card control unit 481 is disposed on the entrance management system 510, the card control unit 481 inquires the notification management data 450. However, for example, the alert unit 471 and the notification unit 472 May be notified to the card control unit 481. The same applies to each control unit in the following embodiments.

(Figure 10: Step (6): Invalidation)
The card control unit 481 prohibits the holder of the article 100 from passing through the entrance gate by invalidating the security card corresponding to the article ID 431 acquired in step (5). Specifically, for example, when a request is received from the entrance gate so as to authenticate the item ID 431, an answer indicating that the authentication is rejected may be answered, and the entrance gate may reject the entrance according to the answer. By this step, it is possible to prevent a person who illegally acquires the security card as the article 100 is lost from passing through the entrance gate illegally.

Embodiment 3
FIG. 11 is a block diagram of the loss prevention system 1000 according to the third embodiment of the present invention. In the third embodiment, the holder of the article 100 inputs a login ID used to log in to the information system of the company as a part of the registration data 310. For example, the employee ID 314 may be replaced by this, or a separate login ID may be input. The same applies to the tag management data 410.

  In the third embodiment, the loss prevention system 1000 is connected to the user authentication system 520. The user authentication system 520 is a system for authenticating the login ID when the owner of the article 100 logs in to the information system of the company. The user authentication system 520 can be configured as part of the loss prevention system 1000 or can be configured as a separate system from the loss prevention system 1000.

  The loss prevention system 1000 further includes a login control unit 482. The login control unit 482 prohibits login to the information system by invalidating the login ID of the holder when the article 100 is lost. The login control unit 482 can be disposed on the server 400 or can be disposed on the user authentication system 520. In FIG. 11, it arrange | positions on the user authentication system 520 similarly to FIG.

  The configuration other than the above is the same as that of the first embodiment. The differences in the third embodiment will be mainly described below.

  FIG. 12 is an operation flowchart illustrating the operation of the loss prevention system 1000 according to the third embodiment. For convenience of description, some components are omitted from the drawings. Steps (1) to (4) are the same as in FIG. Each step added in FIG. 12 will be described below.

(Figure 12: Step (5): Acquisition)
Similar to the card control unit 481 in FIG. 10, the login control unit 482 inquires the record of the loss management data 420 and the employee ID 414 (here, also assumed to be the login ID).

(Figure 12: Step (6): Invalidation)
The login control unit 482 prohibits the holder of the article 100 from logging in to the information system by invalidating the employee ID 414 (login ID) acquired in step (5). Since the process of invalidating the login ID is a general process in the authentication system, the description will be omitted. This step can prohibit a person who has lost the article 100 from logging in to the in-house information system.

Fourth Preferred Embodiment
FIG. 13 is a block diagram of the loss prevention system 1000 according to the fourth embodiment of the present invention. In the fourth embodiment, the loss prevention system 1000 is connected to the domain management system 530. The domain management system 530 is a system that manages a corporate network domain of a company that lends the article 100. The domain management system 530 can be configured as part of the loss prevention system 1000 or can be configured as a separate system from the loss prevention system 1000.

  The domain management system 530 holds address data 531. The address data 531 is between a login ID used when an employee in the company logs in to the network domain and a network address of a work terminal permitted to log in to the network domain using the login ID. It is data that describes the correspondence. The login ID can be shared with the employee ID 314 (and the employee ID 414). The network address is, for example, a MAC (Media Access Control) address assigned to a desktop computer or the like used by the employee. These correspondence relationships can be set in advance, for example, by a domain administrator of the network domain.

  The loss prevention system 1000 further includes a terminal control unit 483. The terminal control unit 483 prohibits the owner's work terminal from logging in to the in-house network domain when the article 100 is lost. The terminal control unit 483 can be disposed on the server 400 or can be disposed on the domain management system 530. In FIG. 13, it arrange | positions on the domain management system 530 similarly to FIG.

  FIG. 14 is an operation flowchart illustrating the operation of the loss prevention system 1000 according to the fourth embodiment. For convenience of description, some components are omitted from the drawings. Steps (1) to (4) are the same as in FIG. Each step added in FIG. 14 will be described below.

(Figure 14: Step (5): Acquisition)
The terminal control unit 483 inquires the record of the loss management data 420 and the employee ID 414 in the same manner as the card control unit 481 in FIG.

(Figure 14: Step (6): Invalidation)
The terminal control unit 483 acquires the network address corresponding to the employee ID 414 (login ID) acquired in step (5) from the address data 531 and prohibits the work terminal having the network address from logging in to the network domain. Do. The process for prohibiting login to the network address is a general process in the domain management system, and thus the description thereof is omitted. This step can prohibit a person who lost the article 100 from logging in to the in-house network domain.

  In the fourth embodiment, the same function can be exhibited even when the item 100 is a mobile terminal such as a notebook PC, for example, and the mobile terminal can be used to log in to the network domain. Specifically, the correspondence between the network address of the mobile terminal and the login ID may be described in the address data 531. Alternatively, the network address of the mobile terminal can be input as the item ID 312, and the terminal control unit 483 can acquire the network address from the item ID 412. Furthermore, the network address of a work terminal (for example, a desktop computer) other than the item 100 can be similarly input as the item ID 312.

The Fifth Preferred Embodiment
In recent years, the smartphone 300 is generally equipped with a GPS system. The fifth embodiment of the present invention describes an example in which the function of the loss prevention system 1000 is expanded using this. The other configuration is the same as that of the first to fourth embodiments.

  The server 400 can acquire the current position of the smartphone 300 via the GPS system included in the smartphone 300. Even if the loss prevention tag 200 and the smart phone 300 leave | separate using this, when the smart phone 300 exists in an office at that time, for example, the alert of step (3) can be prevented from transmitting. This is because it is assumed that if the item 100 is lost in the company, it will be discovered immediately, so there is little need to send an alert again. Similarly, the smartphone 300 itself may not transmit an alert or a lost report of step (2).

  The geographical range in which the server 400 or the smartphone 300 does not transmit an alert or the like can be set in advance by storing data in which the coordinate value range is acquired in the server 400 in advance. However, if the holder moves after the loss prevention tag 200 and the smartphone 300 move away from each other, for example, and enters the coordinate value range, an alert or the like should be transmitted as described in the first to fourth embodiments.

  After the article 100 is lost, the server 400 repeatedly estimates the current position of the smartphone 300 at appropriate time intervals (for example, every few minutes) to estimate which one of the article 100 and the smartphone 300 is lost. it can. If the item 100 is lost, the item 100 will stay in that place, and the smartphone 300 will move as the owner moves, so the current position of the smartphone 300 continues to change. On the other hand, if the smartphone 300 is lost, the smartphone 300 is considered to stay in place, so the current position of the smartphone 300 does not change or stays within a narrow range. Using this, the server 400 can send a message indicating the result of estimating which one of the article 100 and the smartphone 300 has been lost to an appropriate destination.

<About the modification of the present invention>
The present invention is not limited to the embodiments described above, but includes various modifications. For example, the embodiments described above are described in detail in order to explain the present invention in an easy-to-understand manner, and are not necessarily limited to those having all the configurations described. In addition, part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. In addition, another configuration can be added to, deleted from, or replaced with a part of the configuration of each embodiment.

  In the above embodiment, it has been described that the holder of the article 100 inputs the article ID 312 in the registration data 310. However, considering that the article 100 is lent from a company, the article ID 312 and the employee ID 314 The correspondence between the two may be managed only on the server 400 side. In this case, it is not necessary to input the item ID 312 as the registration data 310. Instead, for example, the item data 430 may be associated with the item ID 431 to store the employee ID of the person lent the item.

  In the above embodiment, the notification unit 472 has been described to notify the e-mail address designated by the notification destination 442, but the notification destination may be other than the e-mail. Since the notification by the notification unit 472 has a meaning of alerting a person other than the holder of the article 100, other notification means may be used as long as the same effect can be exhibited. For example, (a) automatic voice call notification, (b) in-house broadcast, (c) lighting of an alarm lamp, and the like can be considered.

  In the above embodiment, the alert unit 471 or the notification unit 472 transmits an alert or notification, and the same content (for example, the fact that the distance between the article 100 and the loss prevention tag 200 has reached the set value or more) It may be transmitted so that a third party can view the described message. For example, the same content can be posted as a message on a social networking service (SNS) site that can be browsed by persons other than the owner of the article 100. This will facilitate the discovery of the item 100 as more people will see the message. For example, if it is not desirable for someone outside the company to view the message, post a message with appropriate viewing restrictions, or build an in-house SNS in advance (eg, host a SNS service on the server 400) Can be posted as a message on the in-house SNS. Furthermore, the same message may be posted when the smartphone 300 also receives an alert from the alert unit 471 or when the distance between the smartphone 300 and the loss prevention tag 200 is equal to or larger than a set value.

  In the above-described second to fourth embodiments, the control unit is provided for each target to be invalidated, but a combination of these may be considered. In such a case, for example, processing to be performed together with the operation of the alert unit 471 or the notification unit 472 can be defined in advance for each item ID 431, each employee ID 441, or for each of these types. For example, when the type of the item 100 is a security card, the operation can be predefined as calling the card control unit 481 or the like. However, when these control units operate independently from the server 400 as described in FIG. 10 and the like, the predefinition is not necessarily required.

  In the above embodiments, it has been described that each control unit acquires each data held by the server and carries out predetermined invalidation processing and the like, but each data held by the server is If the management terminal of the external system requires it, the data may be provided from the server 400 to the terminal via an appropriate application programming interface (API) or authentication process. The same API or authentication process may be used when each control unit acquires each data.

  In the above embodiment, the notification destination 442 is held by the server 400. However, for example, the notification destination 442 can also be specified on the registration data 310 from the smartphone 300. Furthermore, it is also possible to specify on the registration data 310 whether to post the SNS message.

  Each function part with which server 400 in each above-mentioned embodiment or each subsystem is provided can also be constituted using hardware modules, such as a circuit device, or CPU (Central Processing Unit) is a program module which mounted the same function. Etc. can also be configured to execute.

  100: goods, 200: loss prevention tag, 300: smart phone, 400: server, 410: tag management data, 420: loss management data, 430: goods data, 440: employee data, 450: notification management data, 460: registration unit , 471: alert unit, 472: notification unit, 481: card control unit, 482: login control unit, 483: terminal control unit, 1000: loss prevention system.

Claims (11)

A loss prevention system for preventing loss of articles, comprising:
A wireless terminal for wireless communication with a loss prevention tag attached to the article;
A server for communicating with the wireless terminal,
Have
When the wireless terminal detects that the distance between the loss prevention tag and the wireless terminal is equal to or greater than a set value, the wireless terminal transmits a loss report describing that to the server.
The server, upon receiving the loss report from the wireless terminal, stores data describing the loss report in a storage device.
The server transmits an alert to the wireless terminal if the server does not receive from the wireless terminal a detection report indicating that the item has been found within a set period.
When the server does not receive the discovery report from the wireless terminal after transmitting the alert to the wireless terminal and before the setting period has elapsed, the alert to the wireless terminal Resubmit ,
The article is a security card that opens the entry gate by presenting it to the entry gate of the building when entering the building,
The security card stores a card ID for identifying the security card,
The wireless terminal transmits a personal ID identifying a holder of the article to the server,
The loss prevention system further includes a security card control module that controls availability of the security card.
The security card control module acquires the correspondence between the card ID stored in the security card and the personal ID from data on the server in which the correspondence is described in advance or from the wireless terminal. ,
The security card control module, when the server transmits the alert to the wireless terminal a predetermined number of times or more but does not receive the discovery report from the wireless terminal, the security card corresponding to the card ID A loss prevention system characterized by prohibiting a holder of the security card corresponding to the card ID from entering the building by invalidating the . A loss prevention system for preventing loss of articles, comprising:
A wireless terminal for wireless communication with a loss prevention tag attached to the article;
A server for communicating with the wireless terminal,
Have
When the wireless terminal detects that the distance between the loss prevention tag and the wireless terminal is equal to or greater than a set value, the wireless terminal transmits a loss report describing that to the server.
The server, upon receiving the loss report from the wireless terminal, stores data describing the loss report in a storage device.
The server transmits an alert to the wireless terminal if the server does not receive from the wireless terminal a detection report indicating that the item has been found within a set period.
When the server does not receive the discovery report from the wireless terminal after transmitting the alert to the wireless terminal and before the setting period has elapsed, the alert to the wireless terminal Resubmit ,
The wireless terminal transmits, to the server, a login ID used when the holder of the article logs in to the information system.
The loss prevention system further includes a login ID control module that controls availability of the login ID,
The login ID control module transmits the alert to the wireless terminal a predetermined number of times or more even if the server does not receive the discovery report from the wireless terminal, the login ID received from the wireless terminal A loss prevention system characterized by prohibiting the holder corresponding to the login ID from logging in to the information system by invalidating . A loss prevention system for preventing loss of articles, comprising:
A wireless terminal for wireless communication with a loss prevention tag attached to the article;
A server for communicating with the wireless terminal,
Have
When the wireless terminal detects that the distance between the loss prevention tag and the wireless terminal is equal to or greater than a set value, the wireless terminal transmits a loss report describing that to the server.
The server, upon receiving the loss report from the wireless terminal, stores data describing the loss report in a storage device.
The server transmits an alert to the wireless terminal if the server does not receive from the wireless terminal a detection report indicating that the item has been found within a set period.
When the server does not receive the discovery report from the wireless terminal after transmitting the alert to the wireless terminal and before the setting period has elapsed, the alert to the wireless terminal Resubmit ,
The wireless terminal transmits, to the server, a login ID used when a holder of the article logs in to a network domain.
The loss prevention system further includes a terminal control module that controls availability of a work terminal used when a person having the login ID logs in to the network domain,
The terminal control module acquires the correspondence between the login ID and the network address of the work terminal from address data in which the correspondence is described in advance or from the wireless terminal.
The terminal control module has a network address corresponding to the login ID when the server transmits the alert to the wireless terminal a predetermined number of times or more but does not receive the discovery report from the wireless terminal. A loss prevention system characterized by prohibiting a work terminal from logging in to the network domain . A loss prevention system for preventing loss of articles, comprising:
A wireless terminal for wireless communication with a loss prevention tag attached to the article;
A server for communicating with the wireless terminal,
Have
When the wireless terminal detects that the distance between the loss prevention tag and the wireless terminal is equal to or greater than a set value, the wireless terminal transmits a loss report describing that to the server.
The server, upon receiving the loss report from the wireless terminal, stores data describing the loss report in a storage device.
The server transmits an alert to the wireless terminal if the server does not receive from the wireless terminal a detection report indicating that the item has been found within a set period.
When the server does not receive the discovery report from the wireless terminal after transmitting the alert to the wireless terminal and before the setting period has elapsed, the alert to the wireless terminal Resubmit ,
The wireless terminal is equipped with a GPS system,
The wireless terminal and the server obtain the position of the wireless terminal via the GPS system,
The server acquires the position of the wireless terminal multiple times via the GPS system after receiving the loss report.
When the position of the wireless terminal acquired a plurality of times falls within a predetermined range, the server outputs a message to warn that the wireless terminal has been lost,
The loss prevention system , wherein the server outputs a message that warns that the article has been lost, when the position of the wireless terminal acquired a plurality of times does not fall within the predetermined range . A loss prevention system for preventing loss of articles, comprising:
A wireless terminal for wireless communication with a loss prevention tag attached to the article;
A server for communicating with the wireless terminal,
Have
When the wireless terminal detects that the distance between the loss prevention tag and the wireless terminal is equal to or greater than a set value, the wireless terminal transmits a loss report describing that to the server.
The server, upon receiving the loss report from the wireless terminal, stores data describing the loss report in a storage device.
The server transmits an alert to the wireless terminal if the server does not receive from the wireless terminal a detection report indicating that the item has been found within a set period.
When the server does not receive the discovery report from the wireless terminal after transmitting the alert to the wireless terminal and before the setting period has elapsed, the alert to the wireless terminal Resubmit ,
The wireless terminal is equipped with a GPS system,
The wireless terminal and the server obtain the position of the wireless terminal via the GPS system,
The loss prevention system according to claim 1, wherein the wireless terminal does not transmit the loss report when the position of the wireless terminal acquired via the GPS system is within a predetermined alert unnecessary range . A loss prevention system for preventing loss of articles, comprising:
A wireless terminal for wireless communication with a loss prevention tag attached to the article;
A server for communicating with the wireless terminal,
Have
When the wireless terminal detects that the distance between the loss prevention tag and the wireless terminal is equal to or greater than a set value, the wireless terminal transmits a loss report describing that to the server.
The server, upon receiving the loss report from the wireless terminal, stores data describing the loss report in a storage device.
The server transmits an alert to the wireless terminal if the server does not receive from the wireless terminal a detection report indicating that the item has been found within a set period.
When the server does not receive the discovery report from the wireless terminal after transmitting the alert to the wireless terminal and before the setting period has elapsed, the alert to the wireless terminal Resubmit ,
The wireless terminal is equipped with a GPS system,
The wireless terminal and the server obtain the position of the wireless terminal via the GPS system,
The loss prevention system according to claim 1, wherein the server does not transmit the alert when the position of the wireless terminal acquired via the GPS system is within a predetermined alert unnecessary range . The server transmits the alert to the wireless terminal, or after performing the retransmission a predetermined number of times, notifies the management terminal set in advance that the alert has been transmitted. The loss prevention system according to any one of claims 1 to 6 . When the wireless terminal detects that the distance between the loss prevention tag and the wireless terminal is equal to or greater than a set value, or when the alert is received, a person other than the owner of the wireless terminal browses it on the message site where it is, the loss prevention tag and said any one of claims distance from claim 1, characterized in that to record the message indicating that at least a set value 6 between the wireless terminal Loss prevention system. The message site is configured as an SNS service hosted by the server,
The loss prevention system according to claim 8 , wherein the wireless terminal posts a new message on the SNS service as the message. The loss prevention system according to any one of claims 1 to 6, wherein the server transmits data describing the loss report to the external terminal in response to a request from the external terminal. The article is the work terminal used by an owner of the article when logging in to the network domain,
The loss prevention system according to claim 3 , wherein the terminal control module acquires a correspondence between the login ID and a network address of the article from the address data or from the wireless terminal.

Images