A method and system for managing the call state of a locator device

Abstract

The application discloses a kind of management method and system of positioner equipment conversation state, system includes: message communication module, for providing the subscription / release function of different subject message, while carrying out the control of authority;Rule configuration module, for providing the label of all labels under label library is presented by visual interface, and the pass state rule of single or multiple label configuration is arranged in interface for a session;Message processing module is responsible for the call state scheduling and call record in session;Call record analysis module is used for user to query according to not limited to session id, voice call state, device id, device type, call time, call time condition according to own demand, understand the use condition of system and optimize business process.The application realizes the independent control of whole process to call state, while in this process, it is integrated into the communication failure scene processing, group call and other guarantee means for improving call connection rate, to help user reduce risk and improve product reliability.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method and system for managing the call status of a locator device. Background Art

[0002] With my country's aging population facing a severe challenge, using technology to effectively ensure the safety of elderly users while facilitating their integration into smart living has become a pressing issue. When elderly individuals encounter emergencies and require assistance, quickly, promptly, and accurately communicating the need for help to their children becomes a top priority. Given this, most terminal trackers on the market feature SOS communication capabilities.

[0003] Existing tracker SOS communication functions often pre-configure all call states during the development process, implementing corresponding logic for different call states. While this model can meet temporary needs, due to the high degree of system coupling, subsequent feature iterations and personalized scenario settings will continuously increase maintenance costs and development difficulties. Furthermore, many trackers simply default to call failure when SOS communication fails without any special handling, which poses a significant risk to users in such an emergency. Most existing SOS communication systems can only handle calls from a single user, with a single purpose, and the connection rate cannot be guaranteed in emergency situations. Summary of the Invention

[0004] The embodiments of the present application provide a method and system for managing the call status of a locator device. Based on four modules: a message communication module, a rule configuration module, a message processing module, and a call record analysis module, the system achieves independent control of the entire call status process. At the same time, this process incorporates communication failure scenario processing, group calling, and other measures to improve the call connection rate and enhance the reliability of the locator's SOS communication.

[0005] In a first aspect, the present application provides a method for managing the call status of a locator device. The method is based on four modules: a message communication module, a rule configuration module, a message processing module, and a call record analysis module. The method implements independent control of the call status throughout the entire process. Specifically,

[0006] Using the username and password rules, a corresponding username and password are generated to connect to the message communication module. If authentication fails, the device is non-compliant and cannot be used. After authentication, the device establishes a persistent connection with the message communication module and subscribes to the corresponding topic. This generally refers to devices involved in communication, such as trackers and customized apps that can communicate with trackers.

[0007] The rule configuration module provides a visual interface that displays all tags in the tag library. This interface allows you to configure the pass status rules for a single or multiple tags. It also configures offline message processing rules. After rule configuration is complete, when the device reports a heartbeat, the rule configuration module detects that the device's corresponding tag has been configured with a customized rule. It then uses the rule hot update topic to send the latest customized rule to the device and save it locally. This rule will be used in subsequent calls.

[0008] The message processing module subscribes to messages generated by all devices under the call status topic. After receiving the message, it first obtains the offline message processing rules under the corresponding tag of the device from the tag library. After obtaining the offline processing rules, it obtains the online status of the app from the device status topic based on the binding relationship between the locator and the app:

[0009] If online, the call status message will be sent;

[0010] If the user is offline, measures including app message push, SMS push, and group call will be taken according to the configuration in the rule. The call status message will be saved in the message processing module and will not be sent out for the time being.

[0011] If the rule is configured with App message push or SMS push, a push or SMS message will be sent to the target user. The content of the message will directly open the App's answering page. Once the user opens the App, the message will be delivered.

[0012] If a group call is configured in the rule, the system first obtains the group call target list set by the device user. Then, through the subscription / publish function provided by the message communication module, it publishes call messages to the call status topics subscribed by the group call targets and conducts subsequent communication operations with the first person who answers the call.

[0013] The call record analysis module provides a call record query interface. Users can query based on conditions including but not limited to session ID, voice call status, device ID, device type, call time, and call duration according to their needs, to understand the system usage status and optimize business processes.

[0014] Furthermore, the device establishes a long connection with the message communication module and subscribes to corresponding topics, including: heartbeat, rule hot update, call status, and device status. The heartbeat topic is used to communicate device heartbeat data; the rule hot update topic is used to communicate rule data of call status; the call status topic is used to communicate communication status data in each session; the device status topic is maintained by the PING mechanism of the MQTT client itself, and is used to query the current online status of the device.

[0015] Furthermore, the heartbeat data also includes the local method name and its interpretation used by the device to process SOS communication.

[0016] Furthermore, the rule configuration module provides a visual interface to display all tags under the tag library, where the tags are derived from various attributes in the heartbeat data of the device, including but not limited to general, firmware version, location, and channel.

[0017] Furthermore, a timeout period is set in the offline message processing rule configuration. If no App user answers or rejects the call within the specified time, the offline message will be cleared. All operations in the message processing module will be synchronized to the call record analysis module to form a call record.

[0018] Furthermore, the call record analysis module also generates statistical reports to help users conduct more in-depth data mining and analysis.

[0019] In a second aspect, the present application provides a management system for the call status of a locator device, comprising:

[0020] The message communication module is used to provide subscription / publishing functions for messages on different topics, and to control the permissions of devices that subscribe to / publish messages;

[0021] The rule configuration module provides a visual interface for displaying all tags in the tag library. This interface allows you to configure the pass status rules for a session for a single or multiple tags. It also configures offline message processing rules. Once the rule configuration is complete, when the device reports a heartbeat, the rule configuration module detects that the device's corresponding tag has been configured with a customized rule. It then uses the rule hot update topic to send the latest customized rule to the device, where it is stored locally and used in subsequent calls.

[0022] The message processing module is responsible for call status scheduling and call record recording in the session. The message processing module subscribes to the messages generated by all devices under the call status topic. After obtaining the message, it first obtains the offline message processing rules under the corresponding tag of the device from the tag library. After obtaining the offline processing rules, it obtains the online status of the App from the device status topic based on the binding relationship between the locator and the App. Among them, the App refers to the customized App participating in the locator communication.

[0023] If online, the call status message will be sent;

[0024] If the user is offline, measures including app message push, SMS push, and group call will be taken according to the configuration in the rule. The call status message will be saved in the message processing module and will not be sent out for the time being.

[0025] If the rule is configured with App message push or SMS push, a push or SMS message will be sent to the target user. The content of the message will directly open the App's answering page. Once the user opens the App, the message will be delivered.

[0026] If a group call is configured in the rule, the system first obtains the group call target list set by the device user. Then, through the subscription / publish function provided by the message communication module, it publishes call messages to the call status topics subscribed by the group call targets and conducts subsequent communication operations with the first person who answers the call.

[0027] The call record analysis module is used to provide a user query interface. Users can query according to their needs based on conditions including but not limited to session ID, voice call status, device ID, device type, call time, and call duration to understand the system usage status and optimize business processes.

[0028] Furthermore, the message communication module uses the username and password rules to generate a corresponding username and password to connect to the message communication module. If the authentication fails, it means that the device is non-compliant and cannot be used; after the authentication passes, the device establishes a long connection with the message communication module and subscribes to the corresponding topic; among them, the device generally refers to the device participating in the communication, such as the locator and the customized APP that can communicate with the locator.

[0029] Furthermore, the rule configuration module is used to provide a visual interface to display all tags under the tag library, where the tags are derived from various attributes in the heartbeat data of the device, including but not limited to general, firmware version, location, and channel tags.

[0030] Furthermore, a timeout period is set in the offline message processing rule configuration. If no App user answers or rejects the call within the specified time, the offline message will be cleared. All operations in the message processing module will be synchronized to the call record analysis module to form a call record.

[0031] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0032] The present invention provides a method for managing the call status of a locator device. There is no need to pre-set the call status. By managing the call status of different tags in the tag library, customized configuration of the call status of the locator device under different tags can be achieved. In extreme cases, one device and one process can be achieved. In the event of communication failure, the call connection rate is improved through emergency group calls, App message push, SMS push, etc. The full process of call status is independently controlled. At the same time, the process incorporates communication failure scenario processing, group calls, and other safeguards to improve the call connection rate, helping users reduce risks and improve product reliability. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0034] Figure 1 This is a principle block diagram of a management system for the call status of a locator device in this application. DETAILED DESCRIPTION

[0035] To make the purpose, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with the specific embodiments of this application and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0036] The following describes in detail the technical solutions provided by various embodiments of the present application in conjunction with the accompanying drawings.

[0037] The present invention provides a call status rule configuration method for tags. Based on four modules, namely, a message communication module, a rule configuration module, a message processing module, and a call record analysis module, the method realizes independent control of the entire call status process. At the same time, the method incorporates communication failure scenario processing, group calling, and other guarantee measures to improve the call connection rate, thereby enhancing the reliability of the locator's SOS communication.

[0038] The SOS communication connection process under the general rules of this system is:

[0039] 1. Device authentication;

[0040] 2. The locator initiates a call;

[0041] 3. The message module receives the call message;

[0042] 4. Send online / offline messages based on App status;

[0043] 5. The app answers the call, activates local instant messaging, generates a unique meeting number, and returns an answer message;

[0044] 6. The message module receives the answer message;

[0045] 7. The message module sends the receiving message to the locator;

[0046] 8. The locator uses the conference number returned in the answering message to activate the local instant messaging function and enter the designated conference room for the call.

[0047] The present invention proposes four modules, namely, message communication, rule configuration, message processing, and call record analysis, to implement the above basic process and further add the configuration of personalized process on this basis.

[0048] (1) Message communication module

[0049] The message communication module of the present invention is implemented with the MQTT protocol, which is mainly responsible for providing subscription / publishing functions for messages on different topics, and at the same time controlling permissions for devices that subscribe to / publish messages. The device first needs to use the username and password rules issued by the enterprise to generate the corresponding username and password to connect to the message communication module. If the authentication fails, it means that the device is non-compliant and cannot be used. After the authentication is passed, the device will establish a long connection with the message communication module and subscribe to the corresponding topic. The message communication module maintains four topics: heartbeat, rule hot update, call status, and device status. The heartbeat topic is used for communication device heartbeat data, the rule hot update topic is used for communication call status rule data, the call status topic is used for communication status data in each communication session, and the device status topic is maintained through the PING mechanism of the MQTT client itself, which is used to query the current online status of the device.

[0050] (2) Rule configuration module

[0051] The rule configuration module introduces the concept of a tag library. Tags are derived from various attributes in the device's heartbeat data. This invention proposes various tags, including, but not limited to, general, firmware version, location (through IP analysis), and channel. This module provides a visual interface displaying all tags within the tag library. Operators can use this interface to configure session pass-through status rules for individual or multiple tags. Heartbeat data also includes the device's local method names and their interpretations for handling SOS communications. This interface also associates different call states with local method names. This mapping of local methods to call states decouples call states. In addition to configuring call state rules under tags, rules for handling offline messages can also be configured. After rule configuration is complete, when a device reports a heartbeat, the rule configuration module detects that the corresponding tag has been configured with customized rules. It then distributes the latest customized rules to the device through a hot rule update topic, saving them locally and applying them to subsequent calls.

[0052] (3) Message processing module

[0053] The message processing module is responsible for dispatching call status and recording call records within a session. The message processing module subscribes to messages generated by all devices under the call status topic. Upon receiving a message, it first retrieves the offline message processing rules for the corresponding device tag from the tag library. After obtaining the offline processing rules, it retrieves the app's online status from the device status topic based on the locator's binding relationship with the app. If the app is online, the call status message is delivered. If the app is offline, the module uses methods configured in the rule, including but not limited to app message push, SMS push, and group call. The call status message is then stored in the message processing module and not delivered. If the rule configures app message push or SMS push, a push or SMS message is sent to the target user, which can directly open the app's answering page. Once the user opens the app, the message is delivered. If the rule configures group calling, it first retrieves the group call target list configured by the device user. Then, using the subscription / publishing functionality provided by the message communication module, it publishes call messages to the call status topic to which the group call targets are subscribed, and then communicates with the first person who answered the call. The offline message rule configuration also includes a timeout period. If no app user answers or rejects the call within the specified time, the offline message will be cleared. All operations in the message processing module are synchronized to the call record analysis module to generate a call record.

[0054] (4) Call record analysis module

[0055] The call record analysis module provides a real-time, easy-to-use call record query interface. Users can query records based on session ID, voice call status, device ID, device type, call time, and call duration, enabling them to better understand system usage and optimize business processes. This module also generates detailed statistical reports, enabling users to conduct deeper data mining and analysis.

[0056] The present invention provides a method for managing the call status of a locator device. There is no need to pre-set the call status. By managing the call status of different tags in the tag library, customized configuration of the call status of the locator device under different tags can be achieved. In extreme cases, one device and one process can be achieved. In the event of communication failure, the call connection rate is improved through emergency group calls, App message push, SMS push, etc. The full process of call status is independently controlled. At the same time, the process incorporates communication failure scenario processing, group calls, and other safeguards to improve the call connection rate, helping users reduce risks and improve product reliability.

[0057] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims

1. A method for managing the call status of a locator device, characterized in that: Based on the four modules of message communication module, rule configuration module, message processing module and call record analysis module, the full process of call status is independently controlled. Specifically: After the device is authenticated, the message communication module establishes a persistent connection with it, provides subscription or publishing functions for messages on different topics, and controls the permissions of devices that subscribe to or publish messages. The rule configuration module provides a visual interface to display all tags in the tag library. Through the interface, you can configure the passing status rules of a session for single or multiple tags. It also configures the processing rules of offline messages. The message processing module subscribes to all messages generated by devices under the call status topic. After receiving the message, it first obtains the offline message processing rules under the corresponding tag of the device from the tag library. Then, based on the binding relationship between the locator and the app, it obtains the online status of the app from the device status topic, where: If online, the call status message will be sent; If the user is offline, App message push, SMS push, or group call actions are performed according to the configuration in the rule. The call status message is saved in the message processing module and is not sent out for the time being. If the rule is configured with App message push or SMS push, a push or SMS message will be sent to the target user. The content of the message will directly open the App's answering page. Once the user opens the App, the message will be delivered. If a group call is configured in the rule, the system first obtains the group call target list set by the device user, and then uses the subscription or publishing function provided by the message communication module to publish call messages to the call status topics subscribed by the group call targets, and conducts subsequent communication operations with the first person who answered the call; The call record analysis module provides a call record query interface, where users can perform conditional queries based on their needs. The conditions include session ID, voice call status, device ID, device type, call time, and call duration.

2. A method for managing the call status of a locator device according to claim 1, characterized in that: The device establishes a persistent connection with the message communication module and subscribes to corresponding topics, which include: Heartbeat topic, rule hot update topic, call status topic or device status topic. Among them, the heartbeat topic is used to communicate device heartbeat data; the rule hot update topic is used to communicate call status rule data; the call status topic is used to communicate communication status data in each session; the device status topic is maintained through the MQTT client's own PING mechanism and is used to query the current online status of the device.

3. A method for managing the call status of a locator device according to claim 2, characterized in that: The heartbeat data also includes the local method name and its interpretation used by the device to process SOS communication.

4. The method for managing the call status of a locator device according to claim 1, characterized in that: The rule configuration module provides a visual interface to display all tags under the tag library, where the tags are derived from various attributes in the heartbeat data of the device, including general, firmware version, location and channel.

5. The method for managing the call status of a locator device according to claim 1, characterized in that: The offline message processing rule configuration also sets a timeout period. If no App user answers or rejects the call within the specified time, the offline message will be cleared. All operations in the message processing module will be synchronized to the call record analysis module to form a call record.

6. A method for managing the call status of a locator device according to claim 1, characterized in that: The call log analysis module also generates statistical reports to help users conduct more in-depth data mining and analysis.

7. A management system for the call status of a locator device, characterized in that: include: The message communication module is used to establish a persistent connection with the device after it passes authentication, provide subscription or publishing functions for messages on different topics, and control the permissions of devices that subscribe to or publish messages; The rule configuration module is used to provide a visual interface to display all tags in the tag library. Through the interface, you can configure the passing status rules of a session for single or multiple tags. It also configures the processing rules of offline messages. The message processing module is responsible for call status scheduling and call record recording in the session. It subscribes to messages generated by all devices under the call status topic. After obtaining the message, it first obtains the offline message processing rules under the corresponding tag of the device from the tag library. After obtaining the offline processing rules, it obtains the online status of the app from the device status topic based on the binding relationship between the locator and the app: If online, the call status message will be sent; If the user is offline, App message push, SMS push, or group call actions are performed according to the configuration in the rule. The call status message is saved in the message processing module and is not sent out for the time being. If the rule is configured with App message push or SMS push, a push or SMS message will be sent to the target user. The content of the message will directly open the App's answering page. Once the user opens the App, the message will be delivered. If a group call is configured in the rule, the system first obtains the group call target list set by the device user, and then uses the subscription or publishing function provided by the message communication module to publish call messages to the call status topics subscribed by the group call targets, and conducts subsequent communication operations with the first person who answered the call; The call record analysis module is used to provide a user query interface, where users can perform conditional queries based on their needs. The conditions include session ID, voice call status, device ID, device type, call time, and call duration.

8. A management system for locator device call status according to claim 7, characterized in that: The message communication module uses the username and password rules to generate a corresponding username and password to connect to the message communication module. If the authentication fails, it means that the device is non-compliant and cannot be used; After authentication is passed, the device establishes a persistent connection with the message communication module and subscribes to the corresponding topic.

9. A management system for locator device call status according to claim 7, characterized in that: The rule configuration module is used to provide a visual interface to display all tags under the tag library, where the tags are derived from various attributes in the heartbeat data of the device, including general, firmware version, location or channel tags.

10. A management system for locator device call status according to claim 7, characterized in that: The offline message processing rule configuration also sets a timeout period. If no App user answers or rejects the call within the specified time, the offline message will be cleared. All operations in the message processing module will be synchronized to the call record analysis module to form a call record.

Images