Tracking device locating system, tracking device locating server, tracking device locating method, and tracking device locating program

Abstract

This system effectively detects stalking incidents and implements effective sanctions against perpetrators while protecting the privacy of tracking device owners. [Solution] The tracking device search system comprises a user terminal and a server that manages location information for multiple tracking devices. In response to a search request from the user terminal, the server transmits information to the user terminal based on the number of tracking devices present in its vicinity. The information based on the number only indicates the number of tracking devices and does not include detailed location information for the tracking devices. The server analyzes the results of multiple searches to detect patterns in which the same tracking device is continuously detected at different locations or at different times, and restricts the acquisition of location information for the reported tracking device's owner account.

Description

Technical Field

[0006] , , ,

[0005] , ,

[0001] The present disclosure relates to a tracking terminal search system, a tracking terminal search server, a tracking terminal search method, and a tracking terminal search program.

Background Art

[0002] In recent years, small tracking devices such as GPS tracking terminals and short-range wireless communication beacons have become widely popular, and their use for legitimate purposes such as watching over children and preventing theft of valuables has been expanding. On the other hand, stalking behavior using these tracking terminals has become a social problem. It is a crime in which a tracking terminal is attached to a victim's belongings or vehicle without permission and the location information is continuously obtained illegally.

[0003] To address this problem, some provide a function to issue a warning when an unknown tracking terminal is moving with oneself (see, for example, Patent Document 1). In the prior art, there was a concern about the privacy of legitimate tracking terminal owners because the detailed location information of the detected tracking terminal was displayed.

Prior Art Documents

Patent Documents

[0007] According to the present invention, it is possible to effectively detect the possibility of stalking while protecting the privacy of the tracking device owner. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 shows the overall configuration of the tracking terminal search system according to the embodiment. [Figure 2] Figure 2 is a block diagram showing the hardware configuration of a server according to an embodiment. [Figure 3] Figure 3 is a block diagram showing the hardware configuration of a user terminal according to an embodiment. [Figure 4] Figure 4 is a functional block diagram of the server according to the embodiment. [Figure 5] Figure 5 shows the database table configuration according to the present invention. [Figure 6] Figure 6 is a sequence diagram of the search process according to the embodiment. [Figure 7] Figure 7 is a flowchart of the search process according to the embodiment. [Figure 8] Figure 8 is a flowchart of the fraudulent pattern detection process according to the embodiment. [Figure 9] Figure 9 is a flowchart of the notification and sanctions process according to this embodiment. [Figure 10] Figure 10 shows an example of the search results screen of a user terminal according to this embodiment. [Figure 11] Figure 11 shows an example of a notification confirmation screen on a user terminal according to this embodiment. [Figure 12]Figure 12 is a functional block diagram of a user terminal according to an embodiment. [Figure 13] Figure 13 is a block diagram showing the configuration of a tracking terminal according to an embodiment. [Figure 14] Figure 14 shows a diagram illustrating the concept of the search range according to this embodiment. [Figure 15] Figure 15 shows the operational concept of the sanctions measure according to this embodiment. [Modes for carrying out the invention]

[0009] 1. System Overview 1.1 Basic Concept The tracking device search system according to this embodiment is a system that allows users to actively search for tracking devices (GPS trackers, short-range wireless communication beacons, etc.) in their vicinity and obtain information on the number of such devices. The core feature of this system is that it notifies information based on the "number" of tracking devices, rather than the "detailed location information" of the tracking devices. This allows the system to warn users of the presence of suspicious tracking devices while protecting the privacy of legitimate tracking device owners (for example, parents using GPS devices to monitor their children).

[0010] In this specification, "numerical information" means information indicating the number of tracking terminals 30 (e.g., numerical information such as "3 units" or "5 units"), and may not include information for identifying or specifying individual tracking terminals 30 (such as tracking terminal ID, serial number, or owner information) or information indicating the location of individual tracking terminals 30 (such as latitude, longitude, address, or location on a map). However, it is possible to add location information of the user terminal 20 itself (information about the location where the search was performed) to the "numerical information".

[0011] Since the "number-based information" does not include the detailed location information of the tracking terminal 30, the following two important effects can be obtained. First, the privacy of the legitimate owner of the tracking terminal 30 (e.g., a guardian who uses a GPS terminal to monitor a child) is protected. If the detailed location is displayed as in the prior art, there is a risk that the behavior pattern and living area of the legitimate owner may be known to a third party, but this risk can be avoided with only a notification of the number of units. Second, the effectiveness of the tracking terminal 30 for anti-theft purposes is maintained. If a thief or the like can know the detailed location, it becomes easy to find and invalidate the tracking terminal 30. However, with only the number of units, even if it is known that "there is something around", it is impossible to specify exactly where it is hidden in one's own vehicle. The coexistence of these two effects is made possible by the technical approach of "number-based information".

[0012] The specific presentation form of the "number-based information" can have various variations. The most basic form is to display the counted number of the detected tracking terminals 30 as a numerical value directly (e.g., "3 units", "5 units"), but it is not limited to this. For example, a form that classifies the number of units step by step and presents it is also included in the "number-based information". Specifically, it can be a form that classifies the detected number of units into categories such as "few (0 - 1 unit)", "normal (2 - 3 units)", "many (4 units or more)" and displays them, or a form that converts them into risk indicators such as "risk level: low", "risk level: medium", "risk level: high" and displays them. All of these are information generated based on the server 10 counting the tracking terminals 30 existing in the vicinity and based on the number information thereof, and thus are included in the category of "number-based information".

[0013] In addition, it is also possible to graphically represent the quantity information. For example, indicators colored according to the detected quantity (green: 0 - 1 unit, yellow: 2 - 3 units, red: 4 units or more), number of stars (★: 1 unit, ★★: 2 - 3 units, ★★★: 4 units or more), length of the progress bar, size of the warning icon, etc. can visually present the quantity information. Furthermore, forms of expressing the detected quantity by acoustic effects (the frequency of the beep sound increases as the quantity increases) or tactile feedback (the vibration becomes stronger as the quantity increases) are also conceivable. All of these forms of expression have the process of "counting the quantity" at their core and are generated based on the quantity information, thus corresponding to "information based on numbers".

[0014] What is important is not the form of information expression, but the fact that the information is "generated based on the result of counting the number of tracking terminals 30". Whether the quantity is directly indicated by a numerical value, indicated by a hierarchical classification, indicated by a risk level, or indicated graphically is just a design choice in the user interface, and the essence of "information based on numbers" does not change regardless of the form.

[0015] Furthermore, this system has a function to detect and suppress unauthorized use on the part of the pursuer. Specifically, it includes reinstallation resistance by terminal unique identification, suppression of excessive pursuit by controlling the number of searches, detection of continuous unauthorized patterns, etc. Also, upon receiving a report from the victim, it executes a sanction measure to restrict the acquisition of the position information of the tracking terminal by the perpetrator's account.

[0016] The usage scenarios assumed by this system include (1) surrounding monitoring when stalking damage is suspected, (2) regular checks to see if a suspicious tracking terminal has been installed on one's own vehicle or belongings, (3) reporting and sanctioning the perpetrator when an illegal tracking act is detected, etc. Through these uses, it is the purpose of this system to deter the abuse of the tracking terminal and protect the safety and privacy of users.

[0017] In this embodiment, a centralized architecture is described in which server 10 is responsible for centralized management of location information and search processing. However, the present invention is not limited to this architecture. For example, a distributed architecture is also possible in which location information management and search processing functions are distributed among multiple servers. In this case, the group of servers responsible for location information management and the group of servers responsible for search processing operate in cooperation.

[0018] Furthermore, a configuration in which some or all of the functions of the server 10 are distributed among the user terminals 20 is also conceivable. For example, a so-called peer-to-peer (P2P) architecture in which each user terminal 20 directly detects surrounding tracking terminals 30 and shares that information with other user terminals 20. In this case, even without a specific central server, the user terminals 20 cooperate with each other to realize the function of "managing location information for multiple tracking terminals" as a whole. In such a P2P system, the user terminal 20 that provides information can be interpreted as playing the role of a "server" for the user terminals 20 that request information.

[0019] Furthermore, based on the concept of edge computing, it is also possible to distribute the functions of server 10 across multiple edge nodes (base stations, routers, IoT gateways, etc.). In this case, the edge node geographically closest to the user terminal 20 functions as the "server," enabling low-latency discovery processing.

[0020] In this specification, "server" is not limited to a single, fixed physical server, but broadly includes virtual servers, server clusters, distributed server groups, cloud servers, edge servers, or other user terminals—in short, any "information processing device that manages location information for multiple tracking terminals and provides information in response to search requests." What is important is not the physical form of the device, but its functional role of "managing location information" and "responding to search requests."

[0021] 1.2 Technical Effects This system's approach offers the following three technical benefits: (Effect 1: Privacy protection) Because the detailed location of the tracking device is not displayed, the location information and privacy of the legitimate tracking device owner (e.g., a parent using a GPS device to monitor their child) are protected. In conventional technology, the location of all detected tracking devices is displayed on the map, which means that tracking devices of unrelated people who happened to be nearby are also displayed, and there is a risk that their behavioral patterns may be inferred. This system fundamentally solves this problem. (Effect 2: Maintaining the anti-theft function) Even if a thief or other malicious person uses this system to locate a tracking device attached to a stolen vehicle, the detailed location of the tracking device will not be displayed, making it difficult to locate and disable the device. This maintains the tracking device's original anti-theft function. (Effect 3: Stalking detection) Because users can see the number of tracking devices in their vicinity, they can detect the presence of suspicious tracking devices (e.g., a tracking device that keeps moving with them). By analyzing patterns in which the same tracking device is continuously detected through multiple searches, stalking can be detected early.

[0022] 2. System Configuration 2.1 Overall Structure Figure 1 shows the overall configuration of the tracking terminal search system 1 according to this embodiment. The tracking terminal search system 1 consists of a server 10, a user terminal 20, a tracking terminal 30, and a network 40.

[0023] Server 10 is the core device of this system, collecting and managing location information of tracking terminals 30, and providing information on the number of surrounding tracking terminals in response to search requests from user terminals 20. Server 10 can be implemented as a virtual server built in a cloud environment, a physical server installed on-premises, or a combination of these.

[0024] The user terminal 20 is a terminal device operated by a user of this system, and includes smartphones, tablet devices, wearable devices, etc. A client application dedicated to this system is installed on the user terminal 20, and the user sends a search request and checks the results through this application.

[0025] The tracking terminal 30 is a small device capable of acquiring and transmitting location information, such as a GPS tracking terminal, short-range wireless communication beacon, or UWB (Ultra Wide Band) tag. The tracking terminal 30 periodically transmits its own location information to the server 10.

[0026] Network 40 is a communication network that interconnects Server 10, User Terminal 20, and Tracking Terminal 30, and is composed of communication technologies such as the Internet, mobile communication networks (4G / 5G), Wi-Fi, and short-range wireless communication.

[0027] 2.2 Role of Each Device The main roles of server 10 are five: (1) to collect and manage location information from tracking terminals 30, (2) to receive search requests from user terminals 20 and calculate the number of surrounding tracking terminals, (3) to manage the number of searches and limit excessive searches, (4) to analyze the search history and detect fraudulent patterns, and (5) to receive reports and take sanctions against perpetrator accounts.

[0028] The main roles of the user terminal 20 are five: (1) receiving search requests from the user, (2) acquiring current location information and sending it to the server 10, (3) displaying the number of devices received from the server 10 on the screen, (4) displaying a warning to the user if a fraudulent pattern is detected, and (5) receiving reporting operations from the user and sending them to the server 10.

[0029] The tracking terminal 30 has three main roles: (1) to acquire its own location information using GPS, etc., (2) to periodically transmit location information to the server 10, and (3) to perform functions such as making a sound in response to a request from the owner.

[0030] 2.3 System Configuration Flexibility The configuration of this system is not limited to the basic form described above, and various variations are possible. For example, possible configurations include distributing the functions of server 10 across multiple servers, having user terminals 20 share information with each other via peer-to-peer communication, and performing search processing at edge nodes based on the concept of edge computing. These variations will be described in detail in the following chapter, "8. Variations and Others."

[0031] 2.4 Configuration of the tracking terminal Figure 13 is a block diagram showing the configuration of the tracking terminal 30. The tracking terminal 30 consists of a processor 31, memory 32, storage 33, location information acquisition module 34, communication module 35, battery 36, and a bus 37 connecting these components.

[0032] The processor 31 is a processing unit that performs control processing for the tracking terminal 30. It performs processes such as acquiring location information, transmitting it to the server 10, and power saving control.

[0033] The location information acquisition module 34 is a module that acquires the current location of the tracking terminal 30 using technologies such as GPS, Wi-Fi positioning, and short-range wireless communication positioning. The acquired location information is periodically transmitted to the server 10.

[0034] The communication module 35 is a communication interface that transmits location information to the server 10. It connects to the network 40 using communication technologies such as mobile communication networks (4G / 5G), Wi-Fi, and short-range wireless communication, and communicates with the server 10.

[0035] 3. Server detailed configuration 3.1 Hardware Configuration Figure 2 is a block diagram showing the hardware configuration of server 10. Server 10 includes a processor 11, memory 12, storage 13, and a network interface 14.

[0036] The processor 11 is a processing unit such as a CPU or GPU, and it realizes various functions of the server 10 by executing programs stored in the memory 12. Ideally, the processor 11 should have a high processing power configuration, such as a multi-core CPU or a CPU+GPU combination.

[0037] Memory 12 is a volatile memory device such as RAM, which temporarily stores programs and data executed by the processor 11. By installing a large-capacity memory, multiple processes can be executed in parallel.

[0038] Storage 13 is a non-volatile storage device such as an SSD or HDD, which permanently stores the OS, application programs, databases, etc. By installing a large-capacity storage device, a large amount of location information and search history can be stored for a long period of time.

[0039] The network interface 14 is a communication interface such as Ethernet or Wi-Fi, and connects the server 10 to the network 40. By using a high-speed communication line, simultaneous communication with a large number of user terminals 20 and tracking terminals 30 becomes possible.

[0040] 3.2 Functional Block Diagram Figure 4 is a functional block diagram of server 10. Server 10 consists of a communication unit 101, a terminal identification unit 102, a location information management unit 103, a surrounding terminal detection unit 104, a search count management unit 105, a fraudulent pattern detection unit 106, a notification processing unit 107, a sanctions execution unit 108, and a database 110. These functional units are realized by the processor 11 executing programs.

[0041] The communication unit 101 is a functional unit that communicates with the user terminal 20 and the tracking terminal 30 via the network interface 14. The communication unit 101 receives a search request from the user terminal 20 and transmits the search result. It also receives location information from the tracking terminal 30.

[0042] The terminal identification unit 102 is a functional unit that verifies terminal-specific identification information received from the user terminal 20 and uniquely identifies the user terminal 20. The terminal-specific identification information can include OS-provided device IDs, hardware-specific information, software-generated UUIDs, device fingerprints, etc. Because the terminal identification unit 102 can identify the same user terminal 20 even after the user reinstalls the application, it can prevent circumvention of the search limit.

[0043] The location information management unit 103 is a functional unit that stores and manages location information periodically transmitted from the tracking terminals 30 in the database 110. The location information management unit 103 manages the latest location, past location history, and movement trajectory of each tracking terminal 30. It also manages the expiration date of location information and automatically deletes old information.

[0044] The surrounding terminal detection unit 104 is a functional unit that detects tracking terminals 30 present around the user terminal 20 based on a search request received from the user terminal 20 and calculates the number of such terminals. The surrounding terminal detection unit 104 compares the current location information of the user terminal 20 with the location information of the tracking terminals 30 stored in the database 110 and extracts the tracking terminals 30 present within a specified search range (e.g., a radius of 100m).

[0045] The search count management unit 105 is a functional unit that counts the number of searches for each user terminal 20 and rejects search requests if the number of searches within a predetermined period exceeds the upper limit. The search count management unit 105 suppresses excessive searches by malicious users (which could itself constitute stalking).

[0046] The fraudulent pattern detection unit 106 is a functional unit that analyzes the search history of each user terminal 20 and detects abnormal patterns that suggest stalking behavior. For example, the fraudulent pattern detection unit 106 detects patterns such as "repeatedly detecting the same tracking terminal at different times and locations" or "abnormally high search frequency" and sends a warning to the user terminal 20.

[0047] The notification processing unit 107 is a functional unit that receives notifications from user terminals 20 and records them in the database 110. The notification information includes the user ID of the person making the notification, the ID of the tracking terminal being reported, the reason for the notification, comments, detection history, etc. The notification processing unit 107 aggregates and analyzes multiple notifications to identify the owner of a tracking terminal that is highly malicious.

[0048] The sanctions enforcement unit 108 is a functional unit that restricts the acquisition of location information of a reported tracking device by the owner account of that device. The sanctions enforcement unit 108 is the most important function of this system and implements effective sanctions against the perpetrator. Possible forms of sanctions include complete prohibition, provision of only rough location information, acquisition with a warning display, and restriction for a certain period of time.

[0049] Database 110 consists of a user table 111, a tracking device table 112, a location information table 113, a search history table 114, a reporting table 115, and a sanctions table 116. The structure of these tables will be described in detail in the next section.

[0050] 3.2 Database Table Configuration Figure 5 shows the table structure of database 110. Database 110 consists of six main tables (user table 111, tracking device table 112, location information table 113, search history table 114, reporting table 115, and sanctions table 116).

[0051] User Table 111 is a table that stores information about users registered in this system. Key items include User ID, email address, password (hashed), registration date and time, last login date and time, account status (active / inactive / deleted), and paid plan subscription status.

[0052] The tracking terminal table 112 is a table that stores information about tracking terminals registered in this system. Its main items include tracking terminal ID, owner user ID, terminal type, registration date and time, last communication date and time, and nickname (set by the owner).

[0053] Location information table 113 is a table that stores location information of the tracking device. Its main items include location information ID, tracking device ID, latitude, longitude, positioning accuracy, positioning date and time, and server reception date and time. Because this table accumulates a large number of records as time-series data, appropriate index design and partitioning strategies are crucial.

[0054] The search history table 114 is a table that records search requests from user terminals and their results. Its main items include search ID, user ID, user terminal unique identification information, search execution date and time, search location (latitude and longitude), search range (radius), number of detected devices, list of detected tracking terminal IDs, and fraud pattern detection flag.

[0055] Reporting table 115 is a table that stores user-submitted report information. Key items include report ID, reporter user ID, tracked device ID, report date and time, reason for report (suspicion of stalking / invasion of privacy, etc.), comments, detection history (list of tracking IDs), report status (receiving / under investigation / completed / rejected), response date and time, and response details.

[0056] The sanctions table 116 is a table that stores information on sanctions implemented based on reports. Key items include sanctions ID, report ID, sanctioned user ID, sanctioned tracking terminal ID, sanctions type (complete ban / rough location only / warning display / period restriction), sanctions start date and time, sanctions end date and time (in the case of time-limited sanctions), sanctions reason, sanctions status (active / removed / expired), etc. For example, in the case of a "complete ban," specifically, in the case of a "complete ban," the sanctions execution unit 108, upon receiving a location information acquisition request (API request) from the sanctioned user, refers to the sanctions table 116 to check whether the combination of user ID and tracking terminal ID is registered as a target for sanctions. If it is a target for sanctions, the sanctions execution unit 108 does not query the location information management unit 103 and sends an error response (e.g., "Location information for this terminal cannot be obtained") to the sanctioned user's client application. As a result, the sanctioned user is unable to obtain any location information from the sanctioned tracking terminal 30. In the case of "providing only coarse location information," the sanctions execution unit 108 converts the detailed location information (latitude and longitude to 6 decimal places) obtained from the location information management unit 103 into coarse location information (for example, at the city / ward level, or to about 2 decimal places of latitude and longitude) before returning it to the sanctioned user. This allows the sanctioned user to understand the approximate location of the tracking terminal 30, but detailed tracking becomes difficult. In the case of "restriction for a certain period," the sanctions execution unit 108 applies the above restriction only during the period based on the start and end dates and times recorded in the sanctions table 116. After the period ends, location information can be obtained as usual. In the case of "acquisition with warning display," the sanctions execution unit 108 provides location information but displays a warning message on the client application such as "This terminal has been reported. There is suspicion of unauthorized use." This has a psychological deterrent effect on the sanctioned user.

[0057] "Restricting location information acquisition" does not mean completely prohibiting the acquisition of location information, but rather broadly means "restricting location information acquisition functions more than usual." Specific forms of restriction include the following: (Restriction type 1) Complete prohibition of acquisition: Sanctioned users cannot acquire any location information from the sanctioned tracking device 30. (Restriction type 2) Restriction on acquisition frequency: Sanctioned users can acquire location information, but the frequency of acquisition is restricted (e.g., normally it can be updated every 5 minutes, but it may be restricted to every hour or once a day). (Restriction type 3) Restriction of acquisition accuracy: Sanctioned users can acquire location information, but the accuracy of the location information provided will be reduced (e.g., normally 10m accuracy, but limited to 100m accuracy, 1km accuracy, or only coarse information at the city / town level). (Restriction type 4) Addition of acquisition delay: A deliberate delay is added between the time the sanctioned user requests location information and the time the information is actually provided (e.g., information that would normally be provided immediately is delayed by 30 minutes or 1 hour). (Restriction type 5) Limitation on the number of acquisitions: An upper limit is set on the number of times an acquisition can be made within a certain period (e.g., up to 10 times per day, up to 50 times per week).

[0058] These restriction forms can be applied individually or in combination. Furthermore, it is possible to gradually transition to stricter restriction forms as the number of reports increases (corresponding to the phased sanctions in claim 12). For example, a phased approach could be taken where only restriction form 5 (limit on the number of acquisitions) is applied for the first report, restriction form 3 (limit on acquisition accuracy) is added for the second report, and then restriction form 1 (complete prohibition) is applied for the third report and beyond.

[0059] The key point is that the sanctions are applied to the act of "acquiring location information of the tracking device 30." By restricting only the acquisition of location information for a specific tracking device 30, rather than suspending the entire account of the sanctioned user, appropriate sanctions that respect the principle of proportionality can be achieved. This allows the sanctioned user to continue using the system for other legitimate purposes (e.g., monitoring children with another tracking device), thus avoiding excessive restriction of rights.

[0060] 4. Detailed configuration of the user's terminal 4.1 Hardware Configuration Figure 3 is a block diagram showing the hardware configuration of the user terminal 20. The user terminal 20 includes a processor 21, memory 22, storage 23, display 24, touch panel 25, GPS receiver 26, and network interface 27.

[0061] The processor 21 is a processing unit such as a System on Chip (SoC) for smartphones, and executes the OS and application programs stored in the memory 22.

[0062] Memory 22 is a volatile memory device such as RAM, which temporarily stores programs and data that are currently running.

[0063] Storage 23 is a non-volatile storage device such as flash memory, which permanently stores the OS, applications, user data, etc.

[0064] The display 24 is a display device such as an LCD display or an OLED display, and it displays the application screen.

[0065] The touch panel 25 is an input device placed on top of the display 24 and detects user touch operations.

[0066] The GPS receiver 26 is a positioning device that receives signals from GPS satellites and obtains the current location (latitude and longitude) of the user terminal 20.

[0067] The network interface 27 is a communication interface such as a mobile communication network or Wi-Fi, and connects the user terminal 20 to the network 40.

[0068] 4.2 Functional Configuration of User Terminals Figure 12 is a functional block diagram of the user terminal 20. The client application of the user terminal 20 consists of the following functional blocks.

[0069] The display control unit 201 is a functional unit that controls the display on the display 24. It controls the display of various screens such as the search results screen, notification confirmation screen, settings screen, and history screen.

[0070] The input reception unit 202 is a functional unit that receives user input from the touch panel 25. It detects taps of the search button, taps of the report button, setting change operations, etc., and notifies the corresponding processing unit.

[0071] The location information acquisition unit 203 is a functional unit that acquires current location information from the GPS receiver 26. When a search request is sent, it acquires the current location (latitude and longitude) of the user terminal 20 and provides it to the search request generation unit 205.

[0072] The communication control unit 204 is a functional unit that controls communication with the server 10. It manages all communication with the server 10, including sending search requests, receiving search results, sending notification information, and receiving various notifications. Secure communication is achieved through encrypted HTTPS communication.

[0073] The search request generation unit 205 is a functional unit that generates a search request in response to a search operation by the user. It generates search request data that includes the user terminal's terminal-specific identification information, location information obtained from the location information acquisition unit 203, and the user ID, and transmits it to the server 10 via the communication control unit 204.

[0074] The results processing unit 206 is a functional unit that processes the search results received from the server 10. It analyzes the received "number-based information" and formats it into a format suitable for display. For example, it performs color coding according to the number of units (green, yellow, red), determines the risk level, and generates warning messages.

[0075] The notification control unit 207 is a functional unit that processes user-initiated reporting operations. After receiving a notification of fraud detection, if the user taps the report button, it generates report information (reporter ID, target tracking terminal ID, reason for reporting, comments, etc.) and sends it to the server 10 via the communication control unit 204.

[0076] The settings management unit 208 is a functional unit that manages various settings for the application. A particularly important function is the registration and management of user-owned tracking devices. By registering user-owned tracking devices (such as GPS devices for monitoring children), these devices can be excluded from search results, preventing false positives.

[0077] The history management unit 209 is a functional unit that locally saves and manages past search history. It stores information such as the search date and time, search location, and number of detected devices in the storage unit 210, allowing users to check the history later.

[0078] The memory unit 210 stores application data, configuration information, search history, etc. A portion of the storage area 23 is used to permanently save the data.

[0079] 5. Processing Sequence 5.1 Search Process Sequence Figure 6 shows the overall sequence of the search process. Each step is explained below.

[0080] (S601) When the user taps the search button, the user terminal 20 obtains the current location information from the GPS receiver 26 and sends a search request to the server 10. The search request includes the user ID, user terminal unique identification information, current location information (latitude and longitude), search range (radius), etc.

[0081] (S602) The terminal identification unit 102 of the server 10 verifies the user terminal-specific identification information.

[0082] (S603) The search count management unit 105 of server 10 checks whether the user's search count is within the upper limit.

[0083] (S604) The server 10 sends a location information acquisition request to the tracking terminal 30 as needed. The tracking terminal 30 replies with the latest location information. Through this communication, the server 10 can determine the latest location of the tracking terminal 30.

[0084] (S605) The surrounding terminal detection unit 104 of the server 10 detects the tracking terminals 30 present around the user terminal 20 and calculates the number of terminals. In the detection process, a high-speed search using a spatial index is performed on the location information table 113 to extract the tracking terminals 30 around the user terminal 20 (within a specified range).

[0085] (S606) The surrounding terminal detection unit 104 refers to the user table 111 and the tracking terminal table 112 and excludes the user's own tracking terminals associated with that user from the detection results. This prevents false detection of legitimate tracking terminals (e.g., GPS for monitoring children).

[0086] (S607) Server 10 generates "number-based information" including the number of devices after exclusion processing and sends it to user terminal 20 as a search result response.

[0087] (S608) Server 10 saves the search record for this search to the search history table 114 of database 110. The search record includes the user ID, the date and time of the search, the location of the user terminal 20, the list of detected tracking terminal IDs, the number of detected terminals, etc.

[0088] (S609) The user terminal 20 displays the search results on the screen (see Figure 10).

[0089] (S610) The malicious pattern detection unit 106 of the server 10 analyzes the search history in the background and detects malicious patterns. If a malicious pattern is detected, the server 10 sends a malicious detection notification to the user terminal 20, and the user terminal 20 displays a warning screen to the user (see Figure 11).

[0090] 5.2 Malicious Pattern Detection Process Figure 8 is a flowchart of the fraudulent pattern detection process. Each step is described in detail below.

[0091] (S801) The fraudulent pattern detection unit 106 obtains the search history records of the user's past N searches (e.g., N=10) from the search history table 114 of the database 110.

[0092] (S802) The fraudulent pattern detection unit 106 extracts a list of detected tracking terminal IDs from each acquired search record and identifies the tracking terminal 30 that was commonly detected in multiple searches. Specifically, it counts the number of times each tracking terminal ID appears and extracts tracking terminals 30 that have appeared M times or more (e.g., M=3) as candidates.

[0093] (S803) The fraud pattern detection unit 106 analyzes the changes in the detection location of the extracted candidate tracking terminals 30. If the same tracking terminal 30 is detected even though the detection location (location of the user terminal 20) is in a different location (e.g., a location more than 1 km away), it is determined that there is a high suspicion of fraud.

[0094] (S804) The fraudulent pattern detection unit 106 checks whether the candidate tracking terminal 30 is included in the self-terminal exclusion list (a list of self-owned tracking terminals registered in advance by the user). If it is included in the self-terminal exclusion list, it is determined that it is not fraudulent and the process is terminated.

[0095] (S805) The fraud pattern detection unit 106 generates fraud detection notification information for the tracking terminal 30 that it has determined to be suspicious of fraud, and transmits it to the user terminal 20 via the communication unit 101.

[0096] (S806) The user terminal 20 displays the received fraud detection notification on its screen (see Figure 11). The warning screen includes information on the detected tracking terminals (number of terminals, detection date and time, etc.), a report button, a detailed information display button, etc.

[0097] 5.3 Reporting and Sanctions Figure 9 is a flowchart of the reporting and sanctions process. Each step is described in detail below.

[0098] (S901) The user of user terminal 20 taps the report button on the warning screen.

[0099] (S902) The user terminal 20 displays a screen for selecting the reason for reporting. The user selects the reason for reporting (e.g., "suspicion of stalking," "suspicious tracking") and enters comments as needed.

[0100] (S903) The user terminal 20 sends notification information, including the reason for reporting and comments selected by the user, to the server 10. The notification processing unit 107 of the server 10 stores the received notification information in the notification table 115 of the database 110. The notification information includes the reporting user ID, the tracking terminal ID of the reported device, the reason for reporting, comments, the date and time of reporting, etc.

[0101] (S904) The notification processing unit 107 queries the tracking terminal table 112 in the database 110 based on the tracking terminal ID of the target tracking terminal and identifies the owner user ID of the tracking terminal 30.

[0102] (S905) The sanctions enforcement unit 108 retrieves past reporting history from the reporting table 115 of the database 110 based on the identified owner user ID and tracking terminal ID. It counts the number of reports made to the same tracking terminal 30.

[0103] (S906) The sanctions enforcement unit 108 determines the sanction level according to the number of reports. For example, the sanctions are strengthened in stages, such as "warning display" for the first report, "provision of rough location information only" for the second report, and "complete prohibition of location information acquisition" for the third report and beyond (corresponding to claim 12).

[0104] (S907) The sanctions enforcement unit 108 adds the sanctions record to the sanctions table 116 in the database 110 based on the determined sanctions level.

[0105] (S908) The sanctions enforcement unit 108 sends a sanctions notification to the sanctioned user (owner terminal 20B). The notification includes the details of the sanctions, the reasons for the sanctions, and how to file an objection.

[0106] (S909) Server 10 sends a notification to the user terminal 20A, the person who made the report, confirming receipt of the report. The notification includes the report ID, the date and time of receipt, the processing status, etc.

[0107] (S910) If a sanctioned user attempts to obtain location information of the sanctioned tracking terminal 30, the sanctions execution unit 108 refers to the sanctions table 116 and automatically applies restriction processing according to the sanctions level (see Figure 15).

[0108] The above outlines the basic flow of the search process, fraudulent pattern detection process, and reporting / sanctions process. These processes enable effective detection of stalking incidents and effective sanctions against perpetrators, while protecting the privacy of tracking device owners.

[0109] 6. Detailed Processing Flow 6.1 Details of the search process Figure 7 is a detailed flowchart of the search process. Each step is described in detail below.

[0110] (S701) The communication unit 101 of the server 10 receives a search request from the user terminal 20. The search request is encrypted and sent via HTTPS communication, and the communication unit 101 receives it and parses it in JSON format.

[0111] (S702) The terminal identification unit 102 extracts terminal-specific identification information (IMEI, device ID, etc.) included in the search request.

[0112] (S703) The terminal identification unit 102 queries the user table 111 in the database 110 and determines whether the terminal-specific identification information matches that of an existing user.

[0113] (S704) If the terminal identification information matches that of an existing user, the terminal identification unit 102 obtains the user ID of that user.

[0114] (S705) If the terminal identification information does not match an existing user, the terminal identification unit 102 registers the new user in the user table 111 and issues a new user ID.

[0115] (S706) The search count management unit 105 queries the search history table 114 in the database 110 based on the acquired user ID and counts the number of searches for today (or the last 24 hours).

[0116] (S707) The search count management unit 105 determines whether the number of searches exceeds a predetermined threshold (e.g., 10 times / day).

[0117] (S708) If the number of searches exceeds the limit, the search count management unit 105 generates an error message (e.g., "You have reached the search limit for today. Please try again tomorrow.") and sends it back to the user terminal 20 via the communication unit 101 to terminate the process. Furthermore, if the violation is repeated, the search count management unit 105 may take measures to restrict the search function of the user terminal 20 for a certain period of time.

[0118] (Implementation of search function limitations) If the number of searches exceeds a threshold, the search count management unit 105 can not only reject the search request but also restrict the search function itself for the user terminal 20 for a certain period of time. Specifically, it records a "function restriction flag" and a "restriction release date and time" in the user table 111 and automatically rejects all search requests during the restriction period. The restriction period is set in stages according to the severity and number of violations (e.g., 24 hours for the first violation, 1 week for the second, and permanent suspension from the third violation onward). This staged restriction allows for distinguishing between temporary exceedances due to user error and malicious, organized excessive searches.

[0119] (S709) If the number of searches is within the upper limit, the surrounding terminal detection unit 104 starts processing. The surrounding terminal detection unit 104 issues a query to the location information table 113 using the location information of the user terminal 20 and the search range (e.g., radius of 100m) included in the search request.

[0120] (S710) The surrounding terminal detection unit 104 excludes its own tracking terminals from the detected tracking terminal list by referring to the user table 111 and the tracking terminal table 112. Through this exclusion process, tracking terminals included in the user's pre-registered list of personal terminals (such as GPS for monitoring children) are removed from the detection results (corresponding to claim 7).

[0121] (S711) The surrounding terminal detection unit 104 calculates the number of tracking terminals after exclusion processing and generates "number-based information". The "number-based information" includes the number of detected terminals, location information of the search point (corresponding to claim 6), search date and time, etc.

[0122] (S712) The communication unit 101 of the server 10 generates a search result response that includes "information based on numbers" and sends it to the user terminal 20.

[0123] (S713) Server 10 adds the current search record to the search history table 114 of database 110. The search record includes the user ID, search date and time, location of user terminal 20, list of detected tracking terminal IDs, number of detected terminals, etc.

[0124] (S714) The malicious pattern detection unit 106 of server 10 performs malicious pattern detection processing in the background (see Figure 8). This processing is performed asynchronously and does not affect the response to the search.

[0125] 6.2 Implementation Example of Surrounding Device Detection Process The surrounding device detection process is a core function of this system. To achieve high-speed and accurate detection, the following implementation techniques are used.

[0126] (Technology 1: Spatial Indexing) Spatial indexes such as R-tree, Geohash, and PostgreSQL's PostGIS extension are created for the location information table 113. This allows for the rapid extraction of tracking devices within a specific rectangular area.

[0127] (Technology 2: Optimization of distance calculation) For tracking terminals extracted within a rectangular region, the exact distance from the user terminal 20 is calculated. Spherical geometry formulas such as Haversine's formula and Vincenty's formula are used for distance calculation. To reduce the computational load, a two-stage approach is adopted: first, filtering is performed using a simplified rectangular distance, and then the exact spherical distance is calculated.

[0128] (Technology 3: Parallel Processing) When there are a large number of tracking devices, distance calculations are accelerated through parallel processing. The multi-core CPU and GPU of processor 11 are utilized to simultaneously perform distance calculations for multiple tracking devices.

[0129] (Technology 4: Cash Advance) For frequently searched areas, detection results are temporarily stored in a cache (such as Redis), and database access is omitted when searching the same area again. The cache expiration time is dynamically adjusted according to the tracking device's movement speed (e.g., 1 minute for pedestrians, 10 seconds for vehicles).

[0130] These implementation techniques enable server 10 to handle search requests from tens of thousands of users simultaneously, keeping response times below 100ms.

[0131] 6.3 Fraudulent Pattern Detection Algorithm The fraudulent pattern detection unit 106 detects abnormal patterns that suggest stalking behavior using the following algorithm.

[0132] (Algorithm 1: Continuous detection of the same tracking device) The system determines whether the same tracking device ID has been detected multiple times (e.g., 3 or more times) in the past N search history (e.g., N=10). If the number of detections exceeds the threshold, it is determined that there is a high probability that the tracking device is "attached" to user device 20.

[0133] (Algorithm 2: Patterns of change in time and location) For multiple searches in which the same tracking device was detected, the search time and location will be analyzed. If the device is continuously detected at different times (e.g., a time difference of more than one hour) and in different locations (e.g., a distance difference of more than 1 km), it will be considered highly likely to be stalking behavior.

[0134] (Algorithm 3: Anomaly in search frequency) If the number of searches per unit of time is abnormally high (e.g., more than 10 searches per hour), it suggests that the search activity itself may be for stalking purposes. This excessive searching is detected and a warning is issued.

[0135] (Algorithm 4: Correlation of movement patterns) The movement trajectory of the user terminal 20 is compared with the movement trajectory of the detected tracking terminal, and a correlation coefficient is calculated. If the correlation coefficient is high (e.g., 0.8 or higher), it indicates that the tracking terminal is moving along the same route as the user terminal 20, and it is determined that there is a high possibility of stalking.

[0136] (Algorithm 5: Machine Learning Model) In addition to the rule-based algorithms described above, anomaly detection using machine learning models (e.g., random forests, neural networks) is also possible. Past report data is used as training data to automatically identify stalking patterns.

[0137] By combining these algorithms, highly accurate fraudulent pattern detection can be achieved. To improve detection accuracy, threshold parameters (number of detections, time difference, distance difference, correlation coefficient, etc.) are continuously tuned based on operational results.

[0138] 7. User Interface 7.1 Search results screen Figure 10 shows an example of a search results screen 500 displayed on the user terminal 20. The search results screen 500 consists of a title section 501, a number of units display section 502, a detailed information section 503, and an action button section 504.

[0139] The title section 501 displays a title such as "Nearby Tracking Devices".

[0140] The device count display unit 502 prominently displays the number of detected tracking terminals. For example, it displays a number such as "3 devices". By color-coding the number of devices (e.g., 0-1 devices are green, 2-3 devices are yellow, 4 or more devices are red), the level of risk can be visually represented.

[0141] The detailed information section 503 displays supplementary information such as the location information (address) of the search point, the date and time of the search, and the search area.

[0142] The action button section 504 contains buttons such as "Rescan," "View History," and "Settings." If a malicious pattern is detected, a "Report" button will also be displayed.

[0143] 7.2 Report Confirmation Screen Figure 11 shows an example of the notification confirmation screen 510 that is displayed when an inappropriate pattern is detected. The notification confirmation screen 510 consists of a warning message section 511, a detection history display section 512, and a notification button section 513.

[0144] The warning message section 511 displays warning messages such as, "A suspicious tracking device has been detected. You may be a victim of stalking."

[0145] The detection history display unit 512 displays a list of search histories in which malicious patterns were detected. Each history entry includes the search date and time, search location, number of detected devices, etc.

[0146] The reporting button section 513 includes a "Report" button and a "Cancel" button. When a user taps the "Report" button, the reporting information is sent to the server 10.

[0147] 7.3 Other screens In addition to the above, this system provides the following screens.

[0148] (Screen 1: Main screen) This is the screen displayed when the app is launched. It contains buttons such as the Explore button, History button, Settings button, and Help button.

[0149] (Screen 2: Settings screen) This screen allows you to set the search range, register and delete your own tracking devices, configure notification settings, and edit account information.

[0150] (Screen 3: History screen) This screen displays a list of past exploration history. Tapping on each history entry allows you to view detailed information. You can visually check your movement trajectory by plotting exploration locations on the map.

[0151] (Screen 4: Report history screen) This screen displays a list of reports previously submitted by the user. For each report, you can check the date and time of the report, the report status (received / under investigation / completed), and the result of the response.

[0152] (Screen 5: Help screen) This screen displays information on how to use the system, frequently asked questions, and contact information.

[0153] 8. Variations and Others 8.1 Implementation Variations Each process described in this embodiment can be implemented using software, hardware, or a combination thereof. In software implementation, the process is realized by a processing unit such as a CPU, GPU, or FPGA executing a program. In hardware implementation, the process is realized by an ASIC, dedicated circuit, or the like.

[0154] Each process in this system can be executed on a single device or distributed across multiple devices. Distributed processing offers higher availability and performance in terms of load balancing, redundancy, and continued processing during failures. Furthermore, technologies such as microservice architecture and container orchestration can be utilized.

[0155] Each functional block and component described in this embodiment can be integrated or decomposed according to the requirements of implementation. Simplifying implementation can be achieved by integrating multiple functions into a single module, while conversely, improving maintainability and extensibility can be achieved by decomposing a single function into multiple modules.

[0156] Elements of each embodiment may be combined as appropriate. For example, a modified server architecture can be combined with a modified notification method, or a modified search trigger can be combined with an example of AI / machine learning utilization.

[0157] Furthermore, the accuracy of fraud pattern detection can be improved by utilizing AI and machine learning technologies. For example, this could involve time-series pattern recognition using deep learning models (LSTM, Transformer, etc.) and analysis of search patterns using anomaly detection models (Isolation Forest, Autoencoder, etc.). These models can be continuously improved by using past reporting data and search history as training data.

[0158] 8.2 Variations of Server Architecture In this embodiment, an example in which server 10 is implemented as a single physical server or a cloud server has been described, but the following modifications are also possible.

[0159] (Example 1: Distributed Server Architecture) The functions of server 10 are distributed across multiple physical servers. For example, separate server groups are built for location information management, search processing, and malicious pattern detection, each performing specialized processing. This allows for distribution of processing load, limiting the scope of impact in the event of a failure, and enabling independent scaling for each function.

[0160] (Modification 2: Edge Computing Architecture) Some of the functions of server 10 (particularly the surrounding terminal detection process) are executed on edge nodes (base stations, routers, IoT gateways, etc.) located near the user terminal 20. This minimizes communication latency and improves real-time performance. It also leads to savings in network bandwidth.

[0161] (Modification 3: Peer-to-peer (P2P) architecture) A peer-to-peer (P2P) network is constructed where each user terminal 20 communicates directly with each other, without a central server. Each user terminal 20 shares information about the tracking terminals 30 it has detected with other user terminals 20 using technologies such as blockchain and distributed hash tables (DHT). A user terminal 20 performing a search collects information from the P2P network and calculates the number of tracking terminals 30 present in its vicinity. This configuration eliminates single points of failure (SPOF) and achieves high availability.

[0162] (Modification 4: Hybrid Architecture) Hybrid configurations combining a central server with edge nodes or a P2P network are also possible. For example, routine reconnaissance can be performed on edge nodes or via P2P, while malicious pattern detection, reporting, and sanctions are handled by the central server. This division of roles allows for leveraging the advantages of each architecture.

[0163] 8.3 Variations in setting the search range In this embodiment, the search range was described as a fixed value (e.g., radius of 100m), but the following modifications are also possible.

[0164] (Example 1: Search range based on user settings) The settings screen will allow users to freely set the search range. For example, they could select preset values ​​such as "short range (50m radius)," "medium range (100m radius)," and "long range (500m radius)," or they could set any value (e.g., 10m to 1000m) using a slider.

[0165] (Variation 2: Situation-Adaptive Search Range) The search range is automatically adjusted according to the status of the user terminal 20. For example, (a) adjustment according to movement speed: radius of 50m when walking (e.g., 5km / h or less), radius of 100m when cycling (e.g., 10-20km / h), radius of 500m when moving in a vehicle (e.g., 30km / h or more), (b) adjustment according to location: radius of 50m in urban areas, radius of 200m in suburban areas, (c) adjustment according to time of day: radius reduced to 30m during late-night hours (times with a high risk of stalking), radius of 100m during the day.

[0166] (Modification 3: Hierarchical search range) Multiple search ranges can be set simultaneously, and the number of detected devices in each range is displayed hierarchically. For example, displaying it as "Short range (50m radius): 3 devices, Medium range (100m radius): 7 devices, Long range (500m radius): 15 devices" allows for a more detailed understanding of the distribution of tracking devices.

[0167] (Modification 4: Illustration of the search area) As shown in Figure 14, the search area is displayed as a circle on the map for easier visual understanding. Users can adjust the search area by dragging the circle on the map.

[0168] 8.4 Variations of notification methods In this embodiment, a method of displaying the search results on the screen of the user terminal 20 has been described, but the following notification methods are also possible.

[0169] (Variation 1: Push notification) The search results are sent via push notifications. In particular, sending push notifications when a fraudulent pattern is detected or when the number of detected devices exceeds a threshold can alert users.

[0170] (Variation 2: Voice notification) If a large number of devices are detected, an audio warning will be issued. For example, an audio message such as, "Four tracking devices have been detected in your vicinity. Please be careful," will be played.

[0171] (Modification 3: Notification to a wearable device) The search results are notified to wearable devices such as smartwatches. Vibration, LED flashing, and a simplified screen display allow users to understand the situation without having to take out their smartphone.

[0172] (Modification 4: Email notification) The search results are sent to the user's email address. In particular, if a significant fraudulent pattern is detected, a detailed report can be sent via email, which can be used as evidence later.

[0173] 8.5 Variations of the Search Trigger In this embodiment, we have described a so-called "on-demand search" in which a search request is sent when the user of the user terminal 20 taps the search button, but the search trigger can take other forms.

[0174] (Variation 1: Regular automatic search) The application on the user terminal 20 automatically sends search requests to the server 10 periodically (e.g., every 5 minutes, 10 minutes, or every hour) without explicit user intervention. The server 10 processes these automatically sent search requests in the same way as normal search requests and returns the results to the user terminal 20. The user terminal 20 either displays the received results on its screen or sends a push notification to the user only if the number of devices exceeds a threshold. This configuration reduces the burden on the user to constantly be aware of and perform searches, and enables continuous monitoring.

[0175] (Modification 2: Conditional trigger type search) The user terminal 20 automatically sends a search request when certain conditions are met. Examples of conditions include: "when the user terminal 20's location changes significantly (e.g., moves more than 1 km)", "when a specific time arrives (e.g., 8 AM every morning, 10 PM every evening)", "when arriving at a specific location (e.g., geofenced locations such as home, work, or school)", and "when another application (map application, camera application, etc.) is launched". These conditions can be selected and customized by the user in the application's settings screen.

[0176] (Variation 3: Server-driven push notifications) Server 10 periodically acquires the location information of each user terminal 20 (not the location information of the tracking terminal 30, but the location information of the user terminal 20 itself obtained by functions such as Find My Device), and actively searches for tracking terminals 30 around each user terminal 20. If the search detects an anomaly, such as a large number of tracking terminals in the vicinity, Server 10 sends a push notification to the user terminal 20. In this configuration, there is no explicit "search request" sent from the user terminal 20, but it can be interpreted that "Server 10 is performing the search on behalf of the user terminal 20." Alternatively, the periodic acquisition of location information by Server 10 can be considered equivalent to an "implicit search request."

[0177] In any of the above configurations, the essential function of the present invention, which is to "detect the number of tracking terminals 30 present around the user terminal 20 and provide that information to the user terminal 20," remains unchanged. Whether the trigger for the search is an explicit operation by the user, an automated process by the application, or active monitoring by the server is merely a difference in user experience and operational policy, and all are within the technical scope of the present invention. In this specification, "search request" is not limited to explicit communication such as an HTTP request from the user terminal 20 to the server 10, but broadly means "the trigger for initiating processing to detect tracking terminals 30 around the user terminal 20."

[0178] 8.6 Conceptual Diagram of Search Range Figure 14 illustrates the concept of the search range. In Figure 14, the user terminal 20 is placed in the center, and a circle representing the search range R is drawn around it. The radius of this circle is, for example, 100m.

[0179] Within the circle, there are three tracking terminals, 30A, 30B, and 30C, which are subject to detection. On the other hand, tracking terminal 30D, which is located outside the circle, is outside the search range and therefore is not subject to detection.

[0180] The user terminal 20's screen displays "3 devices" as the detection result. This display does not show the detailed locations of tracking devices 30A, 30B, and 30C, but simply provides the number of devices, indicating that "3 tracking devices are present in the vicinity." This protects the privacy of the tracking device owners.

[0181] 8.7 Conceptual Diagram of Sanctions Operations Figure 15 is a diagram illustrating the operational concept of sanctions. Figure 15 is divided into two areas: the upper half and the lower half.

[0182] The upper half shows the flow from reporting to sanctions. The victim, user terminal 20A, detects stalking and reports it to server 10. Server 10's reporting processing unit 107 receives the reporting information, compiles the number of reports, and determines the sanction level. The sanctions execution unit 108 executes sanctions based on the determined sanction level and sends a sanctions notification to the perpetrator, owner terminal 20B.

[0183] The lower half shows the actions after the sanctions are imposed. When the perpetrator attempts to obtain the location information of the tracking terminal 30, a location information acquisition request is sent from the owner terminal 20B to the server 10. The sanctions execution unit 108 of the server 10 refers to the sanctions table 116 and applies the restriction process.

[0184] The sanctions patterns branch into three categories. Pattern A is a "complete ban," and an error response is returned. Pattern B is "rough location only," and location information at the city / town level is returned. Pattern C is "with warning," and a warning message is displayed along with the location information.

[0185] In this way, sanctions are applied in stages, with the level of sanctions escalating depending on the number of reports and the severity of the offense. This allows for a balance between consideration for false reports and a strict response to malicious stalking.

[0186] [summary] The following is a summary of this disclosure. One of the purposes of this disclosure is to prevent misuse by devices capable of tracking location information. One of the purposes of this disclosure is to effectively detect stalking while protecting the privacy of tracking device owners.

[0187] Issues related to [Appendix 1] One of the purposes of this disclosure is to provide a tracking device search system that balances privacy protection with stalking detection. [Note 1] The invention described in Appendix 1 is a tracking terminal search system comprising a user terminal and a server that manages location information relating to a plurality of tracking terminals, wherein the server transmits to the user terminal, in response to a search request from the user terminal, information based on the number of tracking terminals present around the user terminal. [Effects of Appendix 1] This "number-based information" allows for both privacy protection and stalking detection. Users can only see the number of tracking devices in their vicinity, and their privacy is protected because they cannot learn the identity or detailed location of legitimate tracking device owners. On the other hand, the detection of suspicious device counts and continuous detection allows for the early detection of potential stalking.

[0188] Issues related to [Appendix 2] One of the purposes of this disclosure is to prevent the circumvention of anti-fraud measures by reinstalling the application. [Note 2] The invention described in Appendix 2 is the tracking terminal search system described in Appendix 1, wherein the server uniquely identifies the user terminal. [Effects of Appendix 2] This identification process enables management of the number of searches per user device, detection of fraudulent patterns, and recording of reported information. Particularly important is the ability to prevent circumvention through application reinstallation. By using device-specific identification information, even if the app is deleted and reinstalled, it will be recognized as the same device, and anti-fraud measures such as search limiting will continue to be applied.

[0189] Issues related to [Appendix 3] One of the purposes of this disclosure is to deter excessive exploration by malicious users. [Note 3] The invention described in Appendix 3 is a tracking terminal search system as described in Appendix 1, wherein the server counts the number of search requests from the user terminal and rejects the search request if the number of search requests within a predetermined period exceeds a predetermined threshold. [Effects of Appendix 3] This feature helps deter excessive searching by malicious users. Since excessive searching itself can constitute stalking, this usage limit feature provides two-way protection. The upper limit and duration of the usage limit can be dynamically set according to system operation policies, user attributes, past usage patterns, etc., allowing for flexible operation.

[0190] Issues related to [Appendix 4] One of the purposes of this disclosure is to detect stalking behavior at an early stage. [Note 4] The invention described in Appendix 4 is a tracking terminal search system as described in Appendix 1, wherein the server analyzes the results of multiple searches and detects a pattern in which the same tracking terminal is continuously detected at different locations or at different times. [Effects of Appendix 4] This detection process allows for the early detection of stalking behavior. The detection algorithm can be implemented using rule-based, machine learning-based, or a combination of these. To improve detection accuracy, multiple parameters such as the number of detections, detection period, location changes, and time patterns are comprehensively evaluated to minimize false positives while enabling effective detection.

[0191] Issues related to [Appendix 5] One of the purposes of this disclosure is to maximize the effectiveness of privacy protection. [Note 5] The invention described in Appendix 5 is a tracking terminal search system as described in Appendix 1, wherein the information based on the number indicates the number of tracking terminals and does not include location information of the tracking terminals. [Effects of Appendix 5] This specification maximizes privacy protection. Users can only know "how many tracking devices are around them," and cannot infer the identity or actions of legitimate tracking device owners. This protects the privacy of users of tracking devices for legitimate purposes, such as GPS monitoring.

[0192] Issues related to [Appendix 6] One of the purposes of this disclosure is to enable the analysis of the search history at a later date. [Note 6] The invention described in Appendix 6 is the tracking terminal search system described in Appendix 1, wherein the information based on the number is information to which the location information of the user terminal has been added. [Effects of Appendix 6] This additional information allows users to review their search history later and analyze suspicious patterns. For example, a history like "3 devices at home, 3 at work, 4 at the train station" can reveal that a particular tracking device is "sticking to" them. The important point here is that the added location information is the "location of the user's device," not the "location of the tracking device." This protects the privacy of the tracking device owner while allowing for analysis of the user's own behavioral patterns.

[0193] Issues related to [Appendix 7] One of the purposes of this disclosure is to prevent false detection of legitimate tracking devices. [Note 7] The invention described in Appendix 7 is the tracking terminal search system described in Appendix 1, wherein the server excludes tracking terminals associated with a user account from the search results. [Effects of Appendix 7] This exclusion process prevents false positives of legitimate tracking devices. For example, if a GPS device purchased by the user for monitoring their child, or an anti-loss tag attached to their bag, is included in the search results, tracking devices will always be detected, making it impossible to determine the presence of truly suspicious tracking devices. The exclusion process is implemented by the user registering their own tracking devices in advance using a dedicated app, and the exclusion list is managed on the server side.

[0194] Issues related to [Appendix 8] One of the purposes of this disclosure is to clearly explain the reasons for refusal to users and encourage them to take appropriate action. [Note 8] The invention described in Appendix 8 is a tracking terminal search system as described in Appendix 3, wherein the server sends an error message indicating the reason for rejection to the user terminal if it rejects the search request. [Effects of Appendix 8] This error message clearly indicates the reason for the rejection to the user and prompts them to take appropriate action. The error message can include information such as, "You have reached your search limit for today. Please try again tomorrow," or "You can increase your search limit by upgrading to a paid plan," which prevents user confusion and clearly shows them what to do next.

[0195] Issues related to [Appendix 9] One of the purposes of this disclosure is to provide more effective sanctions to users who exceed the search limit. [Note 9] The invention described in Appendix 9 is a tracking terminal search system as described in Appendix 3, wherein the server restricts the search function from the user terminal if the number of search requests from the user terminal within a predetermined period exceeds a predetermined threshold. [Effects of Appendix 9] This functional restriction directly and continuously prevents excessive reconnaissance by malicious users. While "denial of reconnaissance requests" in Appendix 3 is a temporary denial response to individual reconnaissance requests, the "restriction of reconnaissance functions" in this invention is a functional-level restriction on user accounts or devices, and therefore has a stronger deterrent effect.

[0196] Issues related to [Appendix 10] One of the purposes of this disclosure is to provide a reporting channel from victims to businesses, enabling a coordinated response. [Note 10] The invention described in Appendix 10 is a tracking terminal search system as described in Appendix 4, wherein the user terminal accepts a notification operation when it receives a notification indicating the detection of the pattern, and the server receives notification information corresponding to the notification operation. [Effects of Appendix 10] This reporting function provides a reporting channel from victims to businesses, enabling organized responses. Report information includes the ID of the tracking device being reported, the reason for the report, comments, detection history, etc., and is recorded and analyzed on the server side. This makes it possible for businesses to intervene and respond to organized stalking, which would be difficult for individual victims to deal with on their own.

[0197] Issues related to [Appendix 11] One of the purposes of this disclosure is to prevent stalking itself at a systemic level. [Note 11] The invention described in Appendix 11 is a tracking device search system as described in Appendix 10, wherein the server restricts the owner account of the reported tracking device from obtaining location information of the tracking device. [Effects of Appendix 11] This restriction allows for the prevention of stalking behavior at a system level. This is a groundbreaking feature not found in conventional technologies. In the prior art (for example, U.S. Patent Application Publication No. 2018 / 0343561), the victim was only given a warning, and the perpetrator could ignore the warning and continue stalking. However, the present invention directly deprives the perpetrator of their "tracking ability" itself. This difference is achieved through the following three technical features. Conventional technologies only provide detection and warnings on the victim's device, resulting in one-way protection. This invention achieves more effective protection by adopting a two-way approach of detection on the victim's side (Appendix 4) and sanctions against the perpetrator (Appendix 11). This two-way functionality is only possible when the server centrally manages information from both parties (victim and perpetrator). Conventional reporting systems typically resulted in the suspension of the entire account. However, this is an excessive measure that also disables legitimate uses (e.g., another tracking device for monitoring children). This invention achieves granular sanctions that respect the principle of proportionality by limiting sanctions to "location information acquisition for specific tracking devices only." This implementation is made possible by designing the sanctions table to use a combination of "user ID" and "tracking device ID" as keys. The sanctions of this invention escalate in stages depending on the number of reports (Appendix 12). A staged approach—a "warning display" for the first report, "only rough location information" for the second, and a "complete ban" from the third report onward—minimizes infringement of legitimate users' rights due to false reports while applying strict measures to malicious perpetrators. This automated staged sanctions provide the speed and consistency that was difficult to achieve with conventional manual review. The combination of the three technical features described above is non-trivial for the following reasons: (a) The tracking device detection technology (prior art A) and the notification system (prior art B) are in different technological fields, and the motivation for integrating them is unclear. (b) Sanctions at the tracking terminal level require ingenuity in database design (matrix management of user ID × tracking terminal ID) and are not simply a combination of known technologies. (c) The automation of phased sanctions is innovative in that it resolves two seemingly trade-off requirements—the need to prevent false reports and ensure effective protection—through system design. The restrictions can be set in stages, ranging from complete prohibition to providing only rough location information, to acquisition with warning displays, allowing for a balance between consideration for false reports and strict measures against malicious misuse.

[0198] Issues related to [Appendix 12] One of the purposes of this disclosure is to balance measures against false reporting with a strict response to malicious stalking. [Note 12] The invention described in Appendix 12 is a tracking terminal search system as described in Appendix 11, wherein the server changes the level of the restriction in stages according to the number or frequency of notifications. [Effects of Appendix 12] This phased approach balances measures to prevent false reports with a strict response to malicious stalking. For example, the sanctions are gradually strengthened: only a warning is displayed for the first report, rough location information is provided for the second report, and a complete ban is imposed for the third report and beyond. This phased approach minimizes the risk of legitimate users being wrongly penalized while applying strict measures to malicious stalkers. Furthermore, the phased nature of the sanctions provides perpetrators with opportunities to improve their behavior, and if no improvement is seen, the sanctions are gradually strengthened, thus achieving an effective deterrent effect.

[0199] Issues related to [Appendix 13] One of the purposes of this disclosure is to secure a broad scope of rights that is independent of the system's implementation. [Note 13] The invention described in Appendix 13 is a tracking terminal locating method, comprising the steps of: a server receiving a locating request from a user terminal; the server generating information based on the number of tracking terminals present around the user terminal; and the server transmitting the information based on the number to the user terminal. [Effects of Appendix 13] This method enables the realization of all the effects described in Appendices 1 through 12. By protecting it as a method claim, a broad scope of rights can be secured that is independent of the system implementation. In particular, it becomes possible to enforce rights against various server implementations, such as cloud servers, on-premise servers, and distributed servers.

[0200] Issues related to [Appendix 14] One of the purposes of this disclosure is to enable a tracking device search function on the user's terminal. [Note 14] The invention described in Appendix 14 is a tracking terminal search program that causes a user terminal computer to function as a search request transmission means for transmitting a search request to a server, an information receiving means for receiving information from the server based on the number of tracking terminals present around the user terminal, and a display means for displaying the information based on the number. [Effects of Appendix 14] This program runs on user devices such as smartphones and tablets and provides users with a device tracking function. The program is compatible with various operating systems and can be implemented as a native app, hybrid app, or PWA. By protecting it as a program claim, it becomes possible to enforce rights against the distribution and sale of the application.

[0201] Issues related to [Appendix 15] One of the purposes of this disclosure is to protect the physical configuration of the tracking device search server. [Note 15] The invention described in Appendix 15 is a tracking terminal search server comprising: a storage unit for storing location information relating to a plurality of tracking terminals; a receiving unit for receiving search requests from a user terminal; an information generation unit for generating information based on the number of tracking terminals present around the user terminal; and a transmission unit for transmitting the information based on the number to the user terminal. [Effects of Appendix 15] This device enables all the functions described in Appendices 1 to 12. By protecting it as a device claim, the scope of rights based on the physical configuration of the server can be secured. The server can be implemented in various forms, such as a cloud server, on-premise server, distributed server, edge server, etc., and all implementation forms are included within the technical scope of the present invention. [Explanation of symbols]

[0202] 1...Tracking terminal search system, 10...Server, 11...Processor, 12...Memory, 13...Storage, 14...Network interface, 20...User terminal, 20A...User terminal (victim), 20B...Owner terminal (perpetrator), 21...Processor, 22...Memory, 23...Storage, 24...Display, 25...Touch panel, 26...GPS receiver, 27...Network interface, 30...Tracking terminal, 30A-30D...Tracking terminal, 31...Processor, 32...Memory, 33...Storage, 34...Location information acquisition module, 35...Communication module, 36...Battery, 37...Bus, 40...Network, 101...Communication unit, 102...Terminal identification unit, 103...Location information management unit, 104...Nearby terminal detection unit, 105...Search count management unit, 106 ...Fraudulent pattern detection unit, 107...Notification processing unit, 108...Sanctions execution unit, 110...Database, 111...User table, 112...Tracking terminal table, 113...Location information table, 114...Search history table, 115...Notification table, 116...Sanctions table, 201...Display control unit, 202...Input reception unit, 203...Location information acquisition unit, 204...Communication control unit, 205...Search request generation unit, 206...Result processing unit, 207...Notification control unit, 208...Setting management unit, 209...History management unit, 210...Storage unit, 500...Search result screen, 501...Title unit, 502...Number of units display unit, 503...Detailed information unit, 504...Action button unit, 510...Notification confirmation screen, 511...Warning message unit, 512...Detection history display unit, 513...Notification button unit, R...Search range

Claims

1. A tracking terminal search system, User terminal and It includes a server that manages location information for multiple tracking devices, The server, in response to a search request from the user terminal, transmits to the user terminal information based on the number of tracking terminals present in the vicinity of the user terminal. Tracking device search system.

2. The server uniquely identifies the user terminal, The tracking terminal search system according to claim 1.

3. The server counts the number of search requests from the user terminal, and if the number of search requests within a predetermined period exceeds a predetermined threshold, it rejects the search requests. The tracking terminal search system according to claim 1.

4. The server analyzes the results of multiple searches and detects a pattern in which the same tracking device is continuously detected at different locations or at different times. The tracking terminal search system according to claim 1.

5. The information based on the aforementioned number indicates the number of tracking terminals and does not include the location information of the tracking terminals. The tracking terminal search system according to claim 1.

6. The information based on the aforementioned number is information with the location information of the user terminal added. The tracking terminal search system according to claim 1.

7. The aforementioned server excludes tracking devices associated with user accounts from the search results. The tracking terminal search system according to claim 1.

8. If the server rejects the search request, it sends an error message indicating the reason for the rejection to the user terminal. The tracking terminal search system according to claim 3.

9. The server restricts the search function from the user terminal if the number of search requests from the user terminal within a predetermined period exceeds a predetermined threshold. The tracking terminal search system according to claim 3.

10. When the user terminal receives a notification indicating the detection of the pattern, it accepts the reporting operation. The server receives notification information corresponding to the notification operation. The tracking terminal search system according to claim 4.

11. The server restricts the owner account of the reported tracking device from obtaining the location information of the tracking device. The tracking terminal search system according to claim 10.

12. The server changes the level of the restriction in stages depending on the number or frequency of reports. The tracking terminal search system according to claim 11.

13. A method for locating a tracking device, The server receives a search request from the user terminal, The server generates information based on the number of tracking terminals present around the user terminal, The server includes the step of transmitting information based on the number to the user terminal, Method for locating tracking devices.

14. The user's computer terminal Search request transmission means for sending a search request to a server, Information receiving means that receives information from the server based on the number of tracking terminals present around the user terminal. Display means for displaying information based on the aforementioned number, A tracking device search program designed to function as such.

15. A tracking device search server, A storage unit that stores location information for multiple tracking devices, A receiving unit that receives a search request from the user terminal, An information generation unit that generates information based on the number of tracking terminals present around the user terminal, The system includes a transmitting unit that transmits information based on the aforementioned number to the user terminal. Tracking terminal search server.

Images