Information management system, management server, information management method, and program

Abstract

This prevents the loss of user information and the resulting deterioration of the user experience when devices are replaced. [Solution] The system provides an information management system including a first device, a second device, and a user terminal, all of which are accessible via a network to a management server. The management server includes a storage unit that stores user accounts, a first unique identifier of the first device, and user information in association with each other; a reception unit that receives transfer requests from the user terminal; and a processing unit that stores user information in association with the second unique identifier of the second device in response to the transfer request. This allows the new device to utilize the user information from the old device even after a device replacement.

Description

Technical Field

[0001] The present disclosure relates to an information management system, a management server, an information management method, and a program.

Background Art

[0002] In recent years, a so-called monitoring service has become widely popular, in which a mobile terminal equipped with a GPS (Global Positioning System) function and a communication function is carried by a person to be monitored such as a child or an elderly person, and a user such as a guardian can check the current position and movement history of the person to be monitored on his / her own smartphone or the like (see Patent Document 1).

[0003] In such a monitoring service, various settings and action histories accumulated by the user are not mere data, but have value as an invaluable collection of memories recording the daily interactions between the user, especially the guardian on the monitoring side, and the child or parent who is the person to be monitored. In addition, the setting of the "monitoring range" is an important function for ensuring safety, and it is not uncommon for the setting itself to be the result of trial and error.

[0004] By the way, due to reasons on the operator side, for example, when reviewing the service fee plan system and providing a more high-functional plan, when a user continues to use the service, a situation may occur where the user is forced to physically exchange the device (old terminal) that has been used so far for a new device (new terminal). For example, when changing from a plan that provides only a basic GPS function to a high-functional plan that enables sending and receiving of voice messages, this case corresponds to a case where dedicated hardware is required for each.

[0005] In the past, when such a device replacement occurred, the new device could not access user information on the server linked to the old device, resulting in users losing all the data they had accumulated. Specifically, when users started using the new device, they not only lost access to their past activity history, but also had to reconfigure their carefully set "monitoring range" and various notification settings from scratch. [Prior art documents] [Patent Documents]

[0006] [Patent Document 1] Patent No. 6936539 [Overview of the project] [Problems that the invention aims to solve]

[0007] This disclosure is made in view of the above circumstances and aims to provide an information management system, management server, information management method, and program that can appropriately transfer user information accumulated through the use of an old device to a new device, even when a user needs to replace their device. [Means for solving the problem]

[0008] To solve the above problems, an information management system according to one aspect of this disclosure includes a first device and a second device that can access a management server via a network, and a user terminal. The management server includes a storage unit that stores user accounts and a first unique identifier of the first device in association with each other, and stores user information in association with the first unique identifier; a receiving unit that receives a transfer request from the user terminal to transfer user information from the first device to the second device; and a processing unit that, in response to the transfer request received by the receiving unit, causes the user information to be stored in the storage unit in association with a second unique identifier of the second device. The system is characterized in that, after the storage by the processing unit is performed, the second device uses the user information stored in the storage unit in connection with the use of the first device. [Effects of the Invention]

[0009] According to this disclosure, even if a user needs to replace their device, user information accumulated through the use of the old device can be appropriately transferred to the new device. [Brief explanation of the drawing]

[0010] [Figure 1] This is a schematic diagram showing the overall configuration of an information management system according to one embodiment of the present disclosure. [Figure 2] This is a block diagram showing the functional configuration of the management server according to this embodiment. [Figure 3] This block diagram shows the functional configuration of the user terminal according to this embodiment. [Figure 4] This is a block diagram showing the functional configuration of the device (first device or second device) according to this embodiment. [Figure 5] This figure shows an example of the data structure of the information stored in the storage unit of the management server according to this embodiment. [Figure 6] This is a sequence diagram showing the flow of the user information transfer process executed by the information management system according to this embodiment. [Figure 7] This flowchart shows the flow of the information transfer process executed by the management server according to this embodiment. [Figure 8] This flowchart shows the flow of the information transfer process performed by the user terminal according to this embodiment. [Figure 9] This figure shows an example of the device selection screen from which the data was transferred, which is displayed on the display unit of the user terminal according to this embodiment. [Figure 10] This figure shows an example of a screen displayed on the user terminal's display unit according to this embodiment, which specifies the device from which the data was transferred using the name of the person being monitored. [Figure 11] This figure shows an example of a screen displayed on the user terminal's display unit according to this embodiment, which confirms the transfer after the new registration of the second device. [Figure 12] This diagram illustrates the process of generating a handover request using a code image in this embodiment. [Figure 13] This diagram illustrates the process of generating a handover request using short-range wireless communication in this embodiment. [Figure 14] This flowchart shows the flow of the startup operation mode setting process performed by the device according to this embodiment. [Figure 15] This is a sequence diagram showing the process flow for analyzing user information and proposing settings, according to Modification 1 of this embodiment. [Figure 16] This figure shows an example of a new setting suggestion screen displayed on the display unit of a user terminal according to Modification 1 of this embodiment. [Figure 17] This block diagram shows an example of the hardware configuration of the management server according to this embodiment. [Figure 18] A block diagram showing an example of the hardware configuration of a user terminal according to this embodiment. [Figure 19] This is a block diagram showing an example of the hardware configuration of the device according to this embodiment. [Figure 20] This figure shows an example of the screen display on the user terminal after the user information has been transferred in this embodiment.

Mode for Carrying Out the Invention

[0011] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In all the following drawings, the same elements are denoted by the same reference numerals, and redundant descriptions will be omitted as appropriate. The configurations described in this embodiment are examples, and the present disclosure can be implemented with various modifications to these configurations and processes without departing from the gist thereof.

[0012] (Overall Configuration of Information Management System) FIG. 1 is a schematic diagram showing the overall configuration of an information management system 100 according to an embodiment of the present disclosure. As shown in FIG. 1, the information management system 100 mainly includes a management server 1, a user terminal 2, a first device 3A, and a second device 3B. These are communicably connected to each other via a network 4.

[0013] The network 4 is a communication infrastructure that functionally connects each component of the present system. For example, it can be used alone or in combination with communication networks of any standard or form such as the Internet, a mobile communication network (e.g., 3G, 4G / LTE, 5G), a Wi-Fi (registered trademark) network, a LAN (Local Area Network), a WAN (Wide Area Network), etc. In the present disclosure, the specific type and topology of the network 4 are not limited.

[0014] The first device 3A and the second device 3B (hereinafter simply referred to as "device 3" unless otherwise specified) are both GPS trackers used for the purpose of monitoring people. Here, "GPS tracker" refers to a portable electronic device that has at least the function of receiving radio waves from GPS satellites to determine its own location and the communication function of transmitting the determined location information to the management server 1 via the network 4. In this embodiment, it is carried by the person being monitored, for example, a child, an elderly person, or any other person who needs monitoring. Device 3 is used by being attached to a school bag or purse, or stored in a clothing pocket. An important premise in this embodiment is that the first device 3A and the second device 3B are exchanged by the same user for the purpose of continuing to use the service. For example, this includes cases where the user exchanges for a new model device with a longer battery life, or exchanges for a device with different functions (for example, the presence or absence of a voice messaging function) due to a change in the service provider's plan.

[0015] User terminal 2 is an information processing device operated by the service user, i.e., a guardian or other person who monitors the person being monitored. User terminal 2 may be, for example, a smartphone, tablet, personal computer, or other smart device. User terminal 2 usually functions as the user interface in this system by installing and running a dedicated application program (hereinafter referred to as "app"). Through this app, the user can view and confirm the current location and past activity history transmitted from device 3 on a map, and make various settings. As one of the core functions of this disclosure, the user operates user terminal 2 to issue a transfer request to management server 1 to transfer user information from first device 3A to second device 3B. Specifically, for example, a guardian who manages the GPS tracker issues a transfer request by entering the ID of the replacement terminal (second device) through the app on user terminal 2. This operation links the old and new terminals on the management server 1 side.

[0016] Management Server 1 is a server device consisting of one or more computers that oversees the entire information management system 100. Management Server 1 may be a single physical server, or it may be implemented in a so-called cloud computing environment where functions are distributed across multiple servers. Management Server 1 forms the core of the system and centrally manages user accounts, unique identifiers for physically identifying each device, and various user information set by users or accumulated as a result of device use. As a core function of this disclosure, in response to a handover request transmitted from the user terminal 2, it performs a series of information processing to make the user information associated with the first device 3A seamlessly available on the second device 3B. Through this processing, users can continue using the service with their past data carried over without being aware of the device change.

[0017] (Management server functional configuration) Figure 2 is a block diagram showing the functional configuration of the management server 1 according to this embodiment. The management server 1 comprises a communication unit 11, a control unit 12, and a storage unit 13 as functional components. These functional units are realized through the cooperation of hardware (Figure 17) which will be described later.

[0018] The communication unit 11 is an interface for communicating with other devices via the network 4, and is composed of, for example, a NIC (Network Interface Card) or a communication module. The communication unit 11 receives handover requests and various data requests from the user terminal 2, and also receives information including location information and unique identifiers from the device 3. Furthermore, it transmits the results processed by the control unit 12 (for example, a handover completion notification or requested user information) to the user terminal 2.

[0019] The memory unit 13 is a storage device for permanently storing the vast amount of information necessary for the operation of this system, and is composed of, for example, an HDD, an SSD, or an array thereof. As detailed in Figure 5, it is preferable that the memory unit 13 manages user information and account information in the form of a structured database. The memory unit 13 stores, at a minimum, user accounts that manage service users, unique identifiers that physically or logically uniquely identify each device 3, and user information such as behavioral history and monitoring range, all in a consistent and related manner. This memory unit 13 is the source of the information assets to be inherited and plays the role of maintaining the "state" of this system (corresponding to the "memory unit" in Appendix 1).

[0020] The control unit 12 is the brain that controls the operation of the entire management server 1, and is realized by a CPU, memory, and the like. The control unit 12 reads and executes a predetermined program stored in the memory unit 13, thereby realizing the core processing unit functions of this disclosure as described below. In particular, the control unit 12 includes the functions of both the receiving unit 121 and the processing unit 122. The reception unit 121 is a dedicated interface module for receiving handover requests from the user terminal 2 via the communication unit 11. The reception unit 121 verifies the format of the received request and confirms that all necessary parameters (e.g., user account, unique identifiers for the handover source and destination) are present. If it determines that the request is legitimate, it passes the request to the processing unit 122. As the entry point to the system, it plays an important role in eliminating fraudulent requests and ensuring the security of subsequent processing (corresponding to the "reception unit" in Appendix 1). The processing unit 122 is the functional unit that performs the most central information processing of this disclosure. Based on a legitimate handover request received from the receiving unit 121, the processing unit 122 manipulates the information stored in the storage unit 13. Specifically, it updates or creates new records in the database within the storage unit 13 to newly associate the user information associated with the first unique identifier of the first device 3A specified in the handover request with the second unique identifier of the second device 3B. This "association" process is the core operation that substantially realizes the handover of information. Through this process, the second device 3B can access and use past data as if it had been storing that user information from the beginning.

[0021] (Functional configuration of user terminals) Figure 3 is a block diagram showing the functional configuration of the user terminal 2 according to this embodiment. The user terminal 2 includes a communication unit 21, a control unit 22, a storage unit 23, a display unit 24, an operation unit 25, and other functional components. These functional units are realized through the cooperation of hardware such as a smartphone (Figure 18), which will be described later.

[0022] The communication unit 21 is an interface for communicating with the management server 1 via the network 4. The memory unit 23 temporarily or permanently stores dedicated application programs necessary for using this system, as well as user information obtained from the management server 1. The display unit 24 is an LCD display or an OLED display, and displays the user interface (UI) of the application. The control unit 25 is an interface for receiving user input, such as a touch panel or physical buttons.

[0023] The control unit 22 is a processor that oversees the operation of the entire user terminal 2, and implements the core user-side functions in this disclosure by reading and executing a dedicated application program stored in the memory unit 23. This program causes the computer to function as one of the following "means".

[0024] The display unit 24 functions as a display mechanism, displaying a series of user interfaces optimized for smooth transfer of user information. This includes a screen for selecting the device to be transferred, as described later in Figures 9 and 10. This display mechanism not only displays information but also guides the user so that they can intuitively understand the next action they should take.

[0025] The function of the request transmission means is to send a handover request to the management server 1 based on user instructions received via the operation unit 25. At this time, the request transmission means generates a message in a format that can be interpreted by the reception unit 121 of the management server 1, which includes the first unique identifier of the selected first device, the second unique identifier of the second device to be used, and a token for user authentication, and sends it via the communication unit 21.

[0026] The function of acquiring information involves requesting and acquiring user information associated with the second device 3B (e.g., activity history and monitoring range) from the management server 1 after the handover process is completed or during normal use of the application.

[0027] The function of the display control means is to appropriately format and display user information acquired by the information acquisition means on the display unit 24. For example, it maps the acquired GPS coordinate data of the activity history onto a map and draws it as a trajectory, or overlays the monitoring area as a polygon. In particular, ensuring that past information inherited from the first device 3A is correctly displayed when the user checks the information on the second device 3B after the handover process is completed is extremely important in giving the user a sense of security and visually conveying the success of the handover.

[0028] (Device Functional Configuration) Figure 4 is a block diagram showing the functional configuration of device 3 (first device 3A or second device 3B) according to this embodiment. Device 3, as a portable multi-function terminal, includes a communication unit 31, a control unit 32, a non-volatile memory 33, a GPS receiver 34, a speaker 35, a microphone 36, a display 37, an acceleration sensor 38, operation buttons 39, and the like. The device configuration in Figure 4 is illustrative and is not limited to this configuration.

[0029] The communication unit 31 is a communication module for communicating with the management server 1 via the network 4. The GPS receiver 34 receives signals from GPS satellites and calculates its own latitude and longitude. Speaker 35 is a device for outputting sound, and is used, for example, to play voice messages from the management server or to output various notification sounds. Microphone 36 is a device designed to capture the voice of the person being monitored and ambient sounds, and is used for recording voice messages and monitoring environmental sounds. The display 37 is a screen for visually displaying information, and is used, for example, to display the time, battery level, or a simple message. The display 37 may be a touch panel display, and may also accept user input via the display 37. The accelerometer 38 is a sensor used to detect changes in the movement and posture of a device, and is used, for example, to detect the activity level of a person being monitored, falls, and abnormal movements. The operation button 39 is a physical input device used to receive instructions from the user, such as turning the power on / off, making a call, or sending an emergency notification.

[0030] The non-volatile memory 33 is a memory whose contents are not erased even when the power is turned off, and is composed of, for example, flash memory. In addition to the basic firmware that defines the operation of device 3, this non-volatile memory 33 stores its own operating mode information, which is an important feature of this disclosure. This operating mode information is, for example, a flag that defines whether the device should operate in "GPS plan" mode or "talk plan" mode. This information is usually written at the time of factory shipment or set when the device has previously communicated with the management server 1, and is permanently stored.

[0031] The control unit 32 is a microcontroller (MCU) that manages the operation of the entire device 3. A key feature of this disclosure is that when the device 3 starts up, the control unit 32 first reads the operating mode information from the non-volatile memory 33 without first querying the management server 1. Based on the read operating mode, it autonomously determines its own operation and configures each functional unit. For example, if the operating mode is "GPS plan," the control unit 32 performs a series of initialization processes, such as hardware-based power cutoff to the power supply to the power-hungry codec and amplifier for voice calls, setting the positioning interval of the GPS receiver 34 to 5 minutes, and setting the format of the data packets that the communication unit 31 sends to the server to a lightweight one specifically for location information. Furthermore, the control unit 32 processes the audio data input from the microphone 36 and transmits it to the management server 1 via the communication unit 31, or outputs the audio data received from the management server 1 through the speaker 35. It also displays information on the display 37 and accepts input from the operation buttons 39. In addition, it monitors the condition of the person being monitored based on information from the acceleration sensor 38, and if an abnormality is detected, it sends a notification to the management server 1 via the communication unit 31, similar to an emergency call from the operation buttons 39. This autonomous operation decision mechanism ensures that even if the service provider changes the server-side specifications and stops sending plan information from the server to each device, each device maintains its correct operating mode, allowing the entire service to continue operating without inconsistencies. This is an extremely important feature that allows for flexible adaptation to server-side changes even after a large number of devices have been deployed in the market.

[0032] (Data structure and processing flow) Next, the data structure stored in the memory unit 13 and the overall system processing flow related to information transfer in the information management system 100 of this embodiment will be described in detail with reference to Figures 5 and 6.

[0033] (Data structure) Figure 5 shows an example of the data structure of the information stored in the storage unit 13 of the management server 1 according to this embodiment. In this embodiment, a relational database model is used for explanation, but this disclosure is not limited thereto, and any other database model or data structure, such as a KVS (Key-Value Store) or document-oriented database, may be adopted. The storage unit 13 manages complex user information in a consistent manner by, for example, organically linking the user account table 131, the device management table 132, and the user information table 133.

[0034] The user account table 131 is a table for uniquely managing each user of the service. This table stores at least a system-wide unique "user ID" as its primary key. In addition, it may store information directly associated with the user, such as the user's name, contact information, login information (e.g., a hashed password), and registration date and time.

[0035] The device management table 132 is a core table for managing the relationships between which users are using which devices. Each record in this table contains a "User ID," which is linked to a user in the user account table 131. It also stores a "Device ID" as the primary key or unique key to uniquely identify each device 3. This "Device ID" is a concrete example of the "unique identifier" mentioned in the appendix. Furthermore, it is highly preferable to have a "Device Name" column (e.g., "Taro's GPS") so that users can easily identify devices within the application. This enables a highly convenient user interface, as shown in Figures 9 and 10.

[0036] The user information table 133 is a table that stores the main body of the information assets to be transferred. Each record in this table is associated with a device in the device management table 132 by including a "device ID". This table can have, for example, an "information type" column that identifies the type of information and a "data" column that stores the specific content of that information. The "information type" column stores strings such as "activity history", "communication history", and "monitoring range" (the range of the person being monitored). Depending on the information type, the "data" column stores time-series data of GPS coordinates (e.g., in JSON format), message logs, or polygon vertex coordinate data that defines the "monitoring range". In this disclosure, "user information" is not limited to these histories and scope settings, but may include any information stored or set in connection with the device, such as "attribute information of the person being monitored" (name, nickname, photo, etc.), "attribute information of the guardian" (name, contact information, notification settings, etc.), or "settings information related to the device's location information measurement" (positioning interval, power saving mode settings, positioning accuracy settings, etc.) (Appendix 7). The user information to be transferred here may include, in addition to this history information (location history, sensor information, notification history, etc.), profile information such as the name and photo of the person being monitored, the monitoring range set by the user, a list of people being monitored (approved third parties other than the administrator), and various setting information related to GPS positioning (positioning interval, power saving settings, etc.), as well as any setting information and stored information linked to the device. This structure allows for flexible handling of future additions of new types of user information without changing the table structure.

[0037] In the information transfer process, which is the core of this disclosure, the processing unit 122 of the management server 1 operates across these tables. Specifically, using the user ID and first unique identifier included in the transfer request as clues, it identifies all relevant records from the user information table 133, and either updates the "device ID" of those records with the second unique identifier, or duplicates and saves them as new records with the second unique identifier. This database operation is the technical entity that realizes the functional effect of transferring user information.

[0038] (System-wide integration process) Figure 6 is a sequence diagram showing the overall flow of the user information transfer process executed by the information management system 100 according to this embodiment. The process begins when the user operates user terminal 2. When the user specifies the first device 3A, which will be the source of the transfer, and the second device 3B, which will be the destination, on the application and instructs the transfer to be executed, the request transmission means on user terminal 2 sends a transfer request to management server 1 (step S601). This transfer request is usually sent using an encrypted protocol such as HTTPS to ensure secure communication. The request payload includes a session token or API key for user authentication, as well as unique identifiers for the source and destination devices.

[0039] When the reception unit 121 of the management server 1 receives this handover request, the control unit 12 first authenticates the sender to confirm that the request is from a legitimate user, and then executes the handover process (step S602). The details of this internal process will be described later in Figure 7, but in short, it performs the database operation described in Figure 5 and associates the user information with the second device 3B. Since this process may take time depending on the amount of data, the management server 1 may execute this process as an asynchronous background job.

[0040] Once the handover process is successfully completed in the database, the management server 1 sends a handover completion notification to the user terminal 2 indicating the success of the process (step S603). This notification may be returned, for example, as an HTTP response to the original handover request, or it may be sent using an asynchronous communication method such as a push notification.

[0041] Upon receiving the handover completion notification, the control unit 22 of the user terminal 2 displays a screen to inform the user that the handover is complete (step S604). This allows the user to recognize that the series of operations have been successfully completed.

[0042] As a result of this series of processes, the second device 3B effectively inherits the "state" of the first device 3A. Therefore, if a user later operates the user terminal 2 and requests user information associated with the second device 3B (e.g., activity history) (step S605), the management server 1 correctly references the newly associated user information table 133 record and responds with the requested information (step S606). This response naturally includes the past history accumulated when the first device 3A was used.

[0043] Then, based on the received information, the user terminal 2 displays the activity history, including past history, on its screen (step S607). At this time, the app on the user terminal 2 may display the history of the first device 3A and the history of the second device 3B seamlessly as a single continuous location history of one monitored person, without making the user aware of the device exchange. By seeing this display (see Figure 20), the user can finally be convinced that the information transfer was successful.

[0044] (Details of processing on the server and user terminals) Next, regarding the user information transfer process, which is the core of this embodiment, the flow of processing executed internally by the management server 1 and the user terminal 2, which play the main roles in this process, will be explained in more detail using flowcharts and examples of screen transitions.

[0045] (Management server processing flow) Figure 7 is a flowchart showing the central logic of the information transfer process executed by the management server 1 according to this embodiment. This processing routine is activated by the control unit 12 when the communication unit 11 receives a valid transfer request from the user terminal 2.

[0046] First, the reception unit 121 receives a handover request from the user terminal 2 (step S701). This step not only receives the request but also includes a security check to verify the authentication token included in the HTTP header and confirm that the request is from a user with legitimate authority.

[0047] Next, the control unit 12 analyzes the received handover request payload and retrieves and expands various parameters necessary for subsequent processing, namely, information identifying the user account (user ID), the first unique identifier of the first device 3A, and the second unique identifier of the second device 3B, into memory (step S702).

[0048] Next, the processing unit 122 queries the database in the storage unit 13 using the acquired user ID and first unique identifier as search keys (step S703). Specifically, it first searches the device management table 132 (Figure 5) to confirm whether the specified user and device combination exists correctly. If it does, it identifies and retrieves all user information (behavior history, monitoring range, etc.) associated with that record from the user information table 133 (Figure 5). This step is an important process for accurately identifying the information assets to be handed over.

[0049] Then, the processing unit 122 executes the database update process, which is the core of this process. That is, all user information identified in step S703 is newly associated with the second unique identifier of the second device 3B and stored in the storage unit 13 (step S704). There are several ways to implement this "association," and this disclosure encompasses all of them. For example, one method is to simply UPDATE the value of the "device ID" column of the relevant record in the user information table 133 from the first unique identifier to the second unique identifier. Alternatively, considering data security, it is also preferable to retain the original record with a logical deletion flag set, while INSERTing the information as a new record with the second unique identifier. In either case, the result is that past user information can be referenced using the second unique identifier, and this falls within the technical scope of this disclosure.

[0050] Once all database operations are successfully completed and the transaction is committed, the control unit 12 generates a handover completion notification indicating that the process has been completed successfully and sends it to the user terminal 2 via the communication unit 11 (step S705). This completes the series of handover processes on the management server 1, and control returns to the user terminal 2, which is waiting for a response.

[0051] (Processing flow and user interface of the user terminal) Figure 8 is a flowchart showing the process flow for initiating the information transfer process, which is performed by the user terminal 2 according to this embodiment. This process is initiated when the user selects a specific menu item within the application (e.g., "Change device / transfer").

[0052] When a user selects the handover function, the control unit 22 first displays a dedicated user interface (UI) for handover settings on the display unit 24 (step S801). This UI consists of a series of screen transitions and is designed to allow the user to complete the handover process without confusion or errors.

[0053] Figure 9 shows an example of the device selection screen 90, which is displayed as part of this UI. This screen is particularly important when a user manages multiple devices with a single account. Screen 90 displays a list 91 of devices currently associated with the user's account. What is important here is that the list 91 is not just a list of identifiers (device IDs), but is displayed with "device names" (e.g., "Taro's GPS") that the user can intuitively understand. This allows the user to clearly distinguish which device belongs to whom and reduces the risk of making a serious mistake such as transferring information from the wrong device.

[0054] On this screen 90 and the following screen (not shown), the user clearly specifies the first device 3A to be the source of the transfer and the second device 3B to be the destination of the transfer, and then presses the final execute button (step S802).

[0055] Upon receiving this final execution instruction, the request transmission means of the control unit 22 generates a handover request that summarizes the information selected and specified up to that point (user ID, first unique identifier, second unique identifier, etc.) and transmits it to the management server 1 via the communication unit 21 (step S803).

[0056] After sending the request, the user terminal 2 enters a waiting state to wait for processing to complete. The control unit 22 monitors whether or not it has received a handover completion notification from the management server 1 (step S804). Preferably, this monitoring is performed with a set timeout period. If the handover completion notification is successfully received (step S804: Yes), the control unit 22 displays a screen indicating that the handover is complete (for example, a message such as "Information handover is complete") on the display unit 24 (step S805), and the series of processes is successfully completed. On the other hand, if no notification is received within the timeout period, or if an error notification is received from the management server 1 (step S804: No), an error message (for example, "Communication failed. Please try again later") is displayed (step S806), prompting the user to try again.

[0057] (Variations of the handover process) The above embodiment describes the basic flow in which a user proactively initiates a transfer operation from the app's menu, but this disclosure is not limited thereto. To further reduce the user's effort and accommodate a wider range of situations, various modifications, as described below, can be adopted as "triggers" for generating a transfer request. Each of these modifications is protected as a dependent note and reinforces the technical scope of this disclosure in multiple layers.

[0058] (Variation 1: Improved user interface details and usability) Figure 10 shows an example of a screen 100 displayed on the display unit 24 of the user terminal 2 according to this embodiment, which specifies the device from which the transfer was made using the name of the person being monitored. This is a more specific implementation example of the list 91 shown in Figure 9. As this modified example demonstrates, it is highly preferable that the list be displayed along with the name of the person being monitored associated with each device (e.g., "Taro," "Hanako," "Grandma") and an icon to indicate it. Many users are unaware of the physical model name or identifier of the device, and manage it based on "who is using this device." Therefore, providing such a user interface allows users to intuitively and reliably select the device to be handed over without making a mistake. This is a crucial feature that dramatically improves usability, especially for users monitoring multiple children or family members.

[0059] (Variation 2: Handover initiated by a proactive proposal from the system) It is conceivable that users may be unaware of the handover function or may forget how to perform the operation. This modified version addresses such situations by providing a more intelligent workflow in which the system proactively suggests the handover to the user. Figure 11 shows an example of the transfer confirmation screen 110 displayed on the display unit 24 of the user terminal 2 after the new registration of the second device 3B. In this modified version, the control unit 12 of the management server 1 is equipped with a trigger function that detects specific events. Specifically, it detects the fact that a new registration request for a new second device 3B is received from a user account while a first device 3A is already registered and in use by that user account. This is a situation in which there is a very high probability that a device "exchange" is about to take place. Upon detecting this situation, the control unit 12 sees this as an opportunity and sends a control signal to the user terminal 2 to display a screen prompting confirmation of the handover. When the user terminal 2 receives this control signal, it brings a confirmation screen 110 in the foreground, either as a modal window or a pop-up, as shown in Figure 11. The confirmation screen 110 displays a specific and easy-to-understand message, such as "A new device has been registered. Do you want to transfer information from the existing device 'Taro's GPS'?", along with options such as "Yes" and "No". If the user selects "Yes", the handover process will start automatically, or the user will be redirected to the selection screen shown in Figures 9 and 10. This proactive (push) approach allows users to retrieve information at the most appropriate time and with minimal effort, without having to navigate complex menu hierarchies, dramatically improving the user experience.

[0060] (Variation 3: Handover using physical interaction - Code image) With the widespread use of smartphones, interacting with the physical world using camera functions has become an extremely common operation for users. This modification applies this paradigm to the handover process. Figure 12 is a diagram illustrating the process of generating a handover request using a code image. In this variation, a code image 121 is printed or affixed to the product packaging, accompanying card, or the device itself of the new second device 3B, with embedded information that uniquely identifies the device (e.g., the second unique identifier itself, or a URL to obtain it). Here, “code image” refers to any optically readable two-dimensional symbol, including various forms such as QR codes®, data matrices, or one-dimensional barcodes. When transferring data, the user activates the camera function within the dedicated app on user terminal 2 and reads the code image 121. The app decodes the identification information from the code image and, based on that, automatically generates a transfer request designating this device as the transfer destination and sends it to management server 1. This method completely eliminates the need for the user to select a device from a list or manually enter an ID, providing a simple, fast, and reliable transfer method.

[0061] (Variation 4: Handover using physical interaction - Short-range wireless communication) Near-field communication technologies such as Bluetooth® and NFC are widely used as a means of secure communication between devices. This modified version applies this technology to achieve a more intuitive and physical handover process. Figure 13 is a diagram illustrating the process of generating a handover request using short-range wireless communication. In this modified version, the user terminal 2, the first device 3A, and the second device 3B are each equipped with short-range wireless communication functions such as an NFC tag / reader and a Bluetooth® module. After the user initiates the transfer mode in the app, these three devices are brought physically close to each other (for example, within a few centimeters or by lightly tapping each other). A handshake and authentication then take place between the devices via near-field communication, and their respective roles (user terminal, transfer source, transfer destination) and unique identifiers are exchanged. Upon successful completion of this secure information exchange, user terminal 2 automatically generates a transfer request and sends it to management server 1. This method minimizes even screen operations, offering advanced and superior usability by linking intuitive actions in the physical world ("gathering the things you want to transfer in one place") with processing in the digital world.

[0062] (Details regarding the device's autonomous operation) Figure 14 is a flowchart showing the flow of the startup operation mode setting process performed by device 3 according to this embodiment, and provides a detailed explanation of the device-specific invention. This process is an extremely important function for ensuring the operational stability of numerous devices distributed on the market and for flexibly responding to changes in server-side specifications. When device 3 is powered on or restarted by pressing the reset button, the control unit 32 starts this process. First, the control unit 32 accesses the non-volatile memory 33 mounted on its own circuit board (step S1401). Unlike volatile memory (RAM), which stores information that is frequently rewritten during device operation (for example, the latest GPS coordinates), this non-volatile memory 33 has the property of retaining its contents even when power is not supplied. Next, the control unit 32 reads its own operating mode information stored at a predetermined address in the non-volatile memory 33 (step S1402). As mentioned above, this operating mode information is a 1-bit or several-bit flag data that defines the service plan (e.g., "GPS plan" or "talk plan") that the device must comply with. This value allows each device to continue "remembering" its own state even after the server stops notifying each device of the plan information due to the operator's circumstances (e.g., a change in the plan specifications). Next, the control unit 32 autonomously configures its own functional units based on the read operating mode (step S1403). This is, so to speak, a self-initialization process for the device. For example, if the operating mode is "GPS plan," the control unit 32 performs a series of initialization processes, such as hardware-based power cutoff to the power supply to the power-hungry codec and amplifier for voice calls, setting the positioning interval of the GPS receiver 34 to 5 minutes, and setting the format of the data packets that the communication unit 31 sends to the server to a lightweight one specifically for location information. Once all settings are complete, device 3 transitions to its normal operating state in the defined mode without waiting for instructions from the server (step S1404). This autonomous operation determination mechanism ensures that the device always starts operating in the correct mode, even if communication with the server is temporarily interrupted during startup. This is a crucial foundational technology that supports the robustness and reliability of the service.

[0063] (Future advanced implementation: Value creation through AI collaboration) This disclosure not only solves the challenge of simply transferring user information, but can also function as a platform to actively utilize the transferred information assets and further enhance the value of the service. Figures 15 and 16 illustrate an example of this, illustrating a function that utilizes AI. Figure 15 is a sequence diagram showing the processing flow of the AI ​​integration function. The control unit 12 of the management server 1 may further include, as part of it, an analysis unit that executes machine learning models and the like, and a proposal unit that generates suggestions for users based on the analysis results. The analysis unit, for example, uses nighttime batch processing or specific events (e.g., completion of handover processing) as triggers to analyze user information of a specific user stored in the memory unit 13 (especially long-term behavioral history) using methods such as deep learning (step S1501). The analysis helps to estimate meaningful "places" such as home, school, cram school, and parks based on the user's behavior patterns, and extract patterns of movement routes and time spent between these places. This then helps to detect potentially useful insights for the user, such as "places that are frequently visited but not set as part of the 'monitoring area'" or "days when the user took a different route home than usual." When the analysis unit detects such insights, the proposal unit generates proposal information in a format that is easy for users to understand (step S1502). Then, the management server 1 sends this proposal information to the user terminal 2 (step S1503). Figure 16 shows an example of a settings suggestion screen 160 displayed by the user terminal 2 that receives this suggestion information. As shown in Figure 16, the app displays a specific message, such as "Your child seems to go to 'Central Park' often. Would you like to register this location as a new 'monitoring area'?", along with a suggested area 161 on the map. The user can set a meaningful "monitoring area" with just one tap by answering "yes," without having to perform any complicated map operations. By utilizing the inherited information for behavioral analysis and personalization, this system can deepen engagement with users and dramatically enhance the competitiveness of the service.

[0064] (Example hardware configuration) Next, we will supplement the explanation by referring to Figures 17 to 19 to show examples of physical hardware configurations for realizing each of the functional units described so far. Figure 17 is a block diagram showing an example of the hardware configuration of the management server 1. The management server 1 has a standard computer architecture, comprising a CPU 171, ROM 172, RAM 173, storage device 174 (HDD, SSD, etc.), communication interface 175 (NIC, etc.), etc., which are interconnected via a bus 176. The program of the present invention is stored in the storage device 174, and the CPU 171 loads it into the RAM 173 and executes it, thereby realizing each functional unit, such as the reception unit 121 and the processing unit 122, as software.

[0065] Figure 18 is a block diagram showing an example of the hardware configuration of user terminal 2. User terminal 2 is a typical smartphone or tablet device equipped with a processor 181, memory 182, communication module 183, display unit 184 (touch panel integrated display, etc.), operation unit 185, etc. The dedicated application of this disclosure is stored in memory 182 and executed by processor 181.

[0066] Figure 19 is a block diagram showing an example of the hardware configuration of device 3. Device 3 includes a microcontroller (MCU) 191, non-volatile memory 192 (such as flash memory), a communication module 193 (such as an LTE module), a GPS receiver 194, a battery, an antenna, etc. The functions of the control unit 32 are realized by the MCU 191 executing firmware stored in the non-volatile memory 192.

[0067] (Example of screen display after data transfer) Figure 20 is an example of a screen display on user terminal 2 that visually shows the final value provided to the user as a result of the series of processes in this embodiment. After the handover process is complete, when the user launches the app and checks the information of the new second device 3B, the screen 200 displays the past activity history 201 seamlessly on the map, and the previously set monitoring range 202 is also correctly displayed. This screen is proof of the "seamless user experience" provided by this disclosure, and users can enjoy the tremendous benefit of being able to continue using the service with peace of mind without being aware of the fact that the device has been physically replaced. In addition, while the user is not aware of the device replacement in this way, it is desirable that the storage unit 13 of the management server 1 separately maintains tracker replacement history, such as which user account replaced which device with which unique identifier, when, and the model information of each device. This allows the service provider to refer to accurate information when responding to user inquiries and troubleshooting.

[0068] Although embodiments of this disclosure have been described in detail above, this disclosure is not limited to the embodiments described above, and various modifications such as omission, substitution, and addition of components are possible without departing from the gist of the disclosure. Needless to say, the components described in each embodiment and modification can be freely combined to the extent that they do not contradict the technical standards.

[0069] [Note] [General tasks] One of the objectives of the present invention is to ensure the continuity of the user experience when a user's device is physically replaced, thereby maintaining and improving customer satisfaction and trust in the service.

[0070] [Issues corresponding to Appendix 1] One of the objectives of the present invention is to appropriately transfer user information accumulated during the use of the old device to the new device, even when a user needs to replace their device in order to continue using the service. [Note 1] The information management system according to this embodiment is an information management system including a first device and a second device that can access a management server via a network, and a user terminal, wherein the management server stores user accounts and a first unique identifier of the first device in association with each other, and also stores user information in association with the first unique identifier, a receiving unit that receives a transfer request from the user terminal to transfer information from the first device to the second device, and a processing unit that, in response to the transfer request received by the receiving unit, causes the user information to be stored in the storage unit in association with the second unique identifier of the second device, and after the storage by the processing unit is performed, the second device uses the user information stored in the storage unit in connection with the use of the first device. According to the information management system described above, even if a device needs to be replaced, users can continue using the service on the new device without losing user information such as past activity history and settings. This eliminates the need for users to reconfigure various settings and effectively prevents a decline in the user experience. As stated in Appendix 1, the following effects can be achieved.

[0071] Firstly, it contributes to improving customer satisfaction and service retention rates. When users face the barrier of continuing service use, such as device replacement, they can seamlessly continue using the service without losing their data assets. This increases their trust in the service provider and allows them to confidently switch to a new plan or upgrade to a new device. This directly leads to improved customer loyalty and has the effect of reducing the churn rate (cancellation rate).

[0072] Secondly, it contributes to reducing support costs. Because information is transferred automatically, the number of customer support inquiries from users due to reasons such as "I don't know how to set it up" or "My data has been lost" can be significantly reduced. This allows businesses to concentrate their resources on more creative tasks.

[0073] Thirdly, it leads to the creation of upsell and cross-sell opportunities. Providing an environment where users can easily migrate to more advanced devices or higher-priced plans without worrying about data loss presents a great opportunity for businesses to increase their average revenue per user (ARPU). This disclosure helps businesses maximize their revenue opportunities by streamlining that migration process.

[0074] Fourthly, it provides emotional value by preserving and utilizing family memories. The inherited history of past actions is not merely log data, but precious memories that families can look back on. This disclosure protects this intangible asset of "memories" and deepens users' attachment to the service. Furthermore, as shown in the modified examples described later, it becomes possible to use the protected data to enhance the added value of the service, such as by having AI analyze the inherited information and propose new "monitoring scopes."

[0075] [Issues corresponding to Appendix 2] One of the objectives of this invention is to improve the operability when users perform handover processing. [Note 2] The information management system described above, wherein the handover request is generated by an operation via the user interface displayed on the user terminal, as described in Appendix 1. This allows users to perform the handover process intuitively through a dedicated UI, improving usability.

[0076] [Issues corresponding to Appendix 3] One of the objectives of the present invention is to enable users to easily and reliably select the source device when managing multiple devices. [Note 3] The information management system described above, wherein the user interface displays a list of one or more first devices associated with the user account, and designates one of the first devices selected from the list as the transfer source, as described in Appendix 2. This allows users to intuitively select a device from a list of potential transfer targets without having to refer to irrelevant information, thus preventing accidental operation.

[0077] [Issues corresponding to Appendix 4] One of the objectives of this invention is to further reduce the effort required for device selection during handover operations and to completely eliminate input errors. [Note 4] In the above-described information management system, the handover request is generated when the user terminal reads the code image assigned to the second device, as described in Appendix 1. This significantly improves usability, as users can reliably initiate the handover process with just an intuitive and everyday operation: scanning a code image with their camera.

[0078] [Issues corresponding to Appendix 5] One of the objectives of this invention is to support users in transferring information at the most appropriate time without being aware of the existence of the transfer function. [Note 5] The information management system described above, wherein the management server, when it receives a request from the user terminal to register a second device while the first device is already associated with the user account, displays a screen on the user terminal prompting the user terminal to confirm whether or not to proceed to a transfer screen for transferring the user information, as described in Appendix 1. As a result, the system proactively proposes the handover, eliminating the need for users to navigate complex menus and allowing for a natural information transfer during device replacement.

[0079] [Issues corresponding to Appendix 6] One of the objectives of the present invention is to enable a more intuitive and secure handover process, even when the device is physically available, without requiring any screen operation. [Note 6] The information management system described above, wherein the handover request is generated by short-range wireless communication between a plurality of devices, including the user terminal, the first device, and the second device, as described in Appendix 1. This allows users to safely and reliably transfer data by simply bringing multiple devices physically close together, improving usability and enhancing security.

[0080] [Issues corresponding to Appendix 7] One of the objectives of this invention is to specifically protect the core content of user information that is to be transferred. [Note 7] The information management system described above, wherein the user information includes at least one selected from the group including the device's activity history, communication history, the range of the person being monitored, the attribute information of the person being monitored, the attribute information of the guardian, and setting information related to the positioning of the device's location information, as described in Appendix 1. This ensures that information assets that users consider particularly important when using the service (location logs, message exchanges, and safe zone settings) are reliably transferred.

[0081] [Issues corresponding to Appendix 8] One of the objectives of this invention is to clarify the technical scope of the invention by providing specific examples of what kind of information the concept of "unique identifier" can correspond to in implementation. [Note 8] The information management system described above, wherein the unique identifier is at least one selected from the group consisting of a communication identifier used for communication of the device, the serial number of the device, and a logical identifier managed by the management server, as described in Appendix 1. This comprehensively protects major forms of identifiers, both current and future, such as communication identifiers (IMEI, etc.), serial numbers, and logical identifiers, thereby increasing the stability of rights and preventing disputes caused by inconsistencies in interpretation.

[0082] [Issues corresponding to Appendix 9] One of the objectives of the present invention is to clarify the specific product fields in which the problems that the present invention primarily aims to solve exist. [Note 9] The information management system described above, wherein both the first device and the second device are GPS trackers used for the purpose of monitoring people, as described in Appendix 1. This clarifies the technical significance and purpose of the invention by specifying that the application of the invention is "a GPS tracker intended for monitoring people," making it easier to derive a favorable interpretation when claiming inventive step, etc.

[0083] [Issues corresponding to Appendix 10] One of the objectives of this invention is not simply to transfer information, but to actively utilize the transferred information assets to provide users with further added value. [Note 10] The information management system described above, wherein the management server further comprises an analysis unit for analyzing the user information and a proposal unit for proposing new settings to the user terminal based on the analysis results, as described in Appendix 1. This allows for the analysis of accumulated behavioral history and other data, enabling personalized suggestions to be made, thereby increasing service engagement and continuously improving value for users.

[0084] [Issues corresponding to Appendix 11] One of the objectives of the present invention is to provide information that users can intuitively understand, rather than impersonal identifiers, when displaying a device list, thereby essentially eliminating the risk of incorrect selection. [Note 11] The information management system described above, wherein the list includes the names of persons under observation associated with each of the first devices, as described in Appendix 3. This allows users to easily and reliably identify whose device it is at a glance by displaying the name of the person being monitored in the device list, dramatically improving usability and operational security. [Industrial applicability]

[0085] This disclosure is not limited to monitoring services, but has broad industrial applicability to any information management system or IoT platform where devices linked to an individual's account may be physically replaceable, including fitness bands, smartwatches, corporate asset management tags, and connected cars. [Explanation of symbols]

[0086] 1…Management Server 11… Communications Department 12…Control Unit 121... Reception Department 122... Processing Unit 13...Storage section 131...User Account Table 132... Device management table 133...User Information Table 2…User terminal 21... Communications Department 22... Control Unit 23…Storage section 24...Display section 25...Operation unit 3, 3A, 3B… Devices 31... Communications Department 32…Control Unit 33... Non-volatile memory 34…GPS receiver 4…Network 100... Information Management System 90, 100, 110, 160, 200... screen 91…list 121... Code image 161…Proposed scope 201... Activity History 202... Monitoring range

Claims

1. An information management system including a first device and a second device that can access a management server via a network, and a user terminal, The aforementioned management server A storage unit that stores a user account and a first unique identifier of the first device in association with each other, and stores user information in association with the first unique identifier, A receiving unit that receives a transfer request from the user terminal for transferring information from the first device to the second device, The system includes a processing unit that, in response to the handover request received by the reception unit, stores the user information in the storage unit in association with the second unique identifier of the second device, After the processing unit has performed the storage operation, the second device utilizes the user information stored in the storage unit in connection with the use of the first device. Information management system.

2. An information management method that utilizes a first device and a second device that can access a management server via a network, and a user terminal, The aforementioned management server A storage step includes storing a user account and a first unique identifier of the first device in association with each other, and storing user information in association with the first unique identifier, A reception step that receives a transfer request from the user terminal for transferring user information from the first device to the second device, The process includes, in response to the handover request received in the reception step, storing the user information in association with the second unique identifier of the second device, After the storage according to the processing step is performed, the second device utilizes the user information stored in the storage unit in connection with the use of the first device. Information management methods.

3. A computer serving as a user terminal is used to manage user information for a first device and a second device that can access the management server via a network. A display means for displaying a user interface for specifying the first device that will be the source of the transfer and the second device that will be the destination of the transfer, A request transmission means that transmits a transfer request to the management server for transferring user information from the first device to the second device based on the designation received via the user interface, Information acquisition means for acquiring the user information associated with the second device from the management server, A display control means that causes the user information acquired by the information acquisition means to be displayed on the display means, A feature that allows it to function as such program.

4. A device that can access the management server via a network, Non-volatile memory that stores its own operating mode, The system is characterized by comprising: a control unit that reads the operating mode from the non-volatile memory at startup and sets its own functions based on the read operating mode; device.

5. In the information management system described in claim 1, The aforementioned handover request is characterized by being generated through an operation via the user interface displayed on the user terminal. Information management system.

6. In the information management system described in claim 5, The user interface is characterized by displaying a list of one or more first devices associated with the user account, and designating one of the first devices selected from the list as the transfer source. Information management system.

7. In the information management system described in claim 1, The aforementioned handover request is characterized in that it is generated when the user terminal reads the code image assigned to the second device. Information management system.

8. In the information management system described in claim 1, The management server, when it receives a request from the user terminal to register a second device while the first device is already associated with the user account, is characterized in that it displays a screen on the user terminal prompting the user terminal to confirm whether or not to proceed to a transfer screen for transferring user information. Information management system.

9. In the information management system described in claim 1, The handover request is characterized by being generated by short-range wireless communication between a plurality of devices, including the user terminal, the first device, and the second device. Information management system.

10. In the information management system described in claim 1, The user information is characterized by including at least one selected from the group consisting of the device's activity history, communication history, the range of the person being monitored, the attribute information of the person being monitored, the attribute information of the guardian, and setting information related to the positioning of the device's location information. Information management system.

11. In the information management system described in claim 1, The unique identifier is characterized by being at least one selected from the group consisting of a communication identifier used for communication of the device, the serial number of the device, and a logical identifier managed by the management server. Information management system.

12. In the information management system described in claim 1, The first device and the second device are both characterized by being GPS trackers used for the purpose of monitoring people. Information management system.

13. In the information management system described in claim 1, The management server further comprises an analysis unit that analyzes the user information and a proposal unit that proposes new settings to the user terminal based on the analysis results. Information management system.

14. In the information management system described in claim 6, The list is characterized by including the names of the persons being monitored, each associated with the first device. Information management system.

Images