CA3166102C - Smart device monitoring method and apparatus - Google Patents
Smart device monitoring method and apparatus Download PDFInfo
- Publication number
- CA3166102C CA3166102C CA3166102A CA3166102A CA3166102C CA 3166102 C CA3166102 C CA 3166102C CA 3166102 A CA3166102 A CA 3166102A CA 3166102 A CA3166102 A CA 3166102A CA 3166102 C CA3166102 C CA 3166102C
- Authority
- CA
- Canada
- Prior art keywords
- heartbeat
- software development
- development kit
- smart device
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- 238000012544 monitoring process Methods 0.000 title claims abstract description 52
- 230000004044 response Effects 0.000 claims abstract description 85
- 230000036541 health Effects 0.000 claims abstract description 63
- 238000007689 inspection Methods 0.000 claims description 27
- 230000000977 initiatory effect Effects 0.000 claims description 11
- 238000004891 communication Methods 0.000 claims description 6
- 230000015556 catabolic process Effects 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 5
- 230000007246 mechanism Effects 0.000 claims description 5
- 238000003032 molecular docking Methods 0.000 claims description 5
- 230000000737 periodic effect Effects 0.000 claims description 5
- 230000011664 signaling Effects 0.000 claims description 5
- 230000003993 interaction Effects 0.000 description 6
- 230000009286 beneficial effect Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 3
- 238000003780 insertion Methods 0.000 description 2
- 230000037431 insertion Effects 0.000 description 2
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- Environmental & Geological Engineering (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- Cardiology (AREA)
- Health & Medical Sciences (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- General Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Debugging And Monitoring (AREA)
- Telephonic Communication Services (AREA)
- Selective Calling Equipment (AREA)
- Alarm Systems (AREA)
Abstract
Description
BACKGROUND OF THE INVENTION
Technical Field [0001] The present invention relates to management of terminal devices, and more particularly to a method and an apparatus for monitoring a smart device.
Description of Related Art
SUMMARY OF THE INVENTION
to DM to request for registration; and
Date Regue/Date Received 2022-06-27
to SDK; and
BRIEF DESCRIPTION OF THE DRAWINGS
and
DETAILED DESCRIPTION OF THE INVENTION
Date Regue/Date Received 2022-06-27
Based on the embodiments of the present invention, all the other embodiments can be conceived without creative labor by people of ordinary skill in the art, and all these and other embodiments shall be encompassed in the scope of the present invention.
initializing SDK using Client, and sending a login message from SDK to DM to request for registration; and from DM, returning a response message to SDK based on the login message, and at SDK, analyzing the response message to extract a heartbeat parameter TTL, so that the heartbeat relationship is established between SDK and DM. The response message carries latest configuration data in addition to TTL, and the latest configuration data are used to refresh a local configuration at SDK.
,,,,f Arly_wipmchifm,,,,mkiiiiiiiiimmollopp.onniminemmaiiilunkNammou iiim ifitilfillfi 11111111rAW Ilnillff 11V Ziwoia 10(Ill I 1 Lid I icld 1)c,c1 iption Rciii,111, , Type The description of the business name of the Mandatory device, e.g., CCT, Android POS, robot arm, etc.
Vendor The information about the supplier provided by Mandatory the device Date Regue/Date Received 2022-06-27 Model The model information of the device, having to Mandatory be unique Version No. The version number of the system Optional Model Description The description about the role, the features, or Mandatory other information of the device
ICIll 11)11011 RCincii Device Name The device name from the Model Table Mandatory Serial Number The serial number of the device Mandatory Store ID No. The unique Identification of the store Mandatory Report Time/Date The time and the date on which a heartbeat is Mandatory reported Use Frequency The number of times of use in the current Optional heartbeat cycle Current State of The state of charge in the current heartbeat cycle Optional Charge Staff ID The staff ID of the staff member who is Optional conducting current operation
DC',C111)t 1011 RCI11,111\
Store ID No. The unique Identification of the store Mandatory State The state information Mandatory Region The region information Mandatory Province The province information Mandatory Branch The branch information Mandatory serial number The serial number of the device Mandatory Type The type from the Model Table Mandatory Vendor The vendor from the Model Table Mandatory Model The model from the Model Table Mandatory Model Description The model description from the Model Table Mandatory Device Name The device name from the Model Table Mandatory Version No. The version no. of the software Mandatory Device Status The current status of the device Mandatory Last Heartbeat Time The time of the last successful heartbeat Mandatory Continuous Online The duration from the previous login to the Optional Duration previous successful heartbeat Use Frequency The use frequency in the cycle for which the Optional query is made to, specifically the number of times of transaction
If yes, it refreshes the local configuration of the software development kit SDK
accordingly; otherwise, the existing local configuration of SDK remains. Then the heartbeat parameter TTL is used as a general heartbeat parameter, and a notification of establishment of heartbeat connection is sent back to the client Client. In general, the heartbeat packet issued for the first heartbeat only contains device information, such as Store ID No., the serial number of the device, and Device Name. The device information is sent in by Client through initialization interface of the software development kit SDK.
automatically sends a heartbeat packet to the device manager DM based on the heartbeat parameter TTL on a periodic basis. This process can be done without calling any SDK interface by Client. The device information in the heartbeat packet includes the serial number of the device and the heartbeat parameter TTL. The service information includes the number of times of transaction in the heartbeat cycle and the currently remaining charge in the smart device. The health information includes error codes and corresponding error descriptions. The serial number of the device is sent in Date Regue/Date Received 2022-06-27 by the client through the initialization interface of the software development kit SDK.
The heartbeat parameter TTL is acquired from the response sent from the login interface or the heartbeat interface of the device manager DM to the software development kit SDK. In addition to the heartbeat parameter TTL, the latest configuration data are also sent back with the response from the login interface or the heartbeat interface of the device manager DM, so that the software development kit SDK after receiving the response message, can analyze and cache the latest configuration data, and store the heartbeat parameter TTL as the general heartbeat parameter for sending a response to the client Client. In the event of a failed heartbeat, the software development kit SDK
pushes a heartbeat failure notification to the client Client, so s to warn the user timely.
has built-in capability for error inspection, if the smart device has an error during heartbeats, when initiating a heartbeat, the software development kit SDK
first calls the inspection interface at the driving level to acquire an error code and its corresponding error description. Then they are carried by the heartbeat packet sent to the device manager DM. It is to be noted that the inspection interface driven by the device adopts a private protocol and supports docking through the following ways: 1. The information is acquired by accessing the local port at the smart device through a socket;
2. The information is transmitted in by calling a relevant interface at the software development kit SDK after inspection performed by the client Client; and 3. The information is transmitted in from the error interface of the software development kit SDK, including an Error Code parameter and an Error Info parameter.
Date Regue/Date Received 2022-06-27
Therein, the non-reentrant function may be transmitted through the client Client. The software development kit SDK makes the heartbeat packet carry the count of transaction accumulated in the present heartbeat cycle so that the count is reported to the heartbeat interface of the device manager DM. The device manager DM analyzes and sinks the reported data before sending a heartbeat response and notifying the monitoring platform.
The software development kit SDK after receiving the response message, empties the count of transactions accumulated in the previous TTL cycle, and analyzes the latest configuration data in the returned heartbeat. Afterward, and the newly acquired TTL is stored as a general heartbeat parameter and a notification about this is sent to the client Client.
After the present heartbeat fails, the interval between heartbeat requests is redefined.
Generally, the interval is such set that it is slightly shorter than a normal heartbeat cycle, such as 5000ms. The attempts are made until the device manager DM sends back a heartbeat response that indicates successful restoration of heartbeats. Now the normal heartbeat connection relationship is reestablished.
Similarly, the health information generated by the smart device in the time period can be called for analysis that measure the health of the device, so that an operation management scheme specific to the device can be made according to the usage and health of the device.
The storage medium may be a ROM/RAM, a hard drive, an optical disk, a memory card or the like.
Date Regue/Date Received 2022-06-27
Claims (116)
a receiving unit, configured to provide a heartbeat connection between a server and a smart device, for the server to receive from the smart device a heartbeat packet containing device information, service information and/or health information, wherein the server receives the heartbeat packet from a software development kit (SDK) in the smart device;
a data sinking unit, at the server, configured to data sink the service information and/or the health information based on the device information, and synchronize reported data of the smart device;
a returning unit, at the server, configured to return a heartbeat response to the smart device, to maintain the heartbeat connection therebetween, wherein the SDK
analyzes a response message to extract a heartbeat parameter (TTL); and a monitoring unit, configured to monitor the smart device and/or managing operation based on the heartbeat connection, the service information, and/or the health information.
providing the smart device with a client and the software development kit (SDK);
providing the server with a device manager (DM);
initializing the software development kit using the client;
sending a login message from the software development kit to the device manager to request for registration;
from the device manager, returning the response message to the software development kit based on the login message; and Date Recue/Date Received 2023-12-07 at the software development kit, analyzing the response message to extract the heartbeat parameter, wherein heartbeat relationship is established between the software development kit and the device manager.
at the software development kit, automatically initiating a heartbeat request as a heartbeat packet to the device manager based on the heartbeat parameter, wherein the device information includes a device serial number, wherein the service information includes a count of transactions in a heartbeat cycle, and wherein the health information includes an error code and a corresponding error description; and wherein the software development kit fails to establish the heartbeat relationship between the software development kit and the device manager, at the software development kit, actively sending a failure notification to the client.
every time the client of the smart device generates a transaction order, recording the transaction order by calling an event tracking interface of the software development kit through the client; and at the software development kit, summing up the transaction orders recorded in one heartbeat cycle to obtain the count of transactions in current heartbeat cycle.
Date Recue/Date Received 2023-12-07 providing a united subscription service interface at the device manager, allowing a monitoring platform to acquire the service information and/or the health information from the device manager and information about the failure notification from the software development kit related to the heartbeat connection through the united subscription service interface.
after the smart device successfully data sinks reported data in the heartbeat packet, at the device manager, actively notifying a monitoring platform;
at the device manager, returning the response message carrying the latest configuration data and the heartbeat parameter to the software development kit; and according to the heartbeat parameter, sending heartbeat packets regularly from the smart device to the device manager, to maintain the heartbeat connection.
Date Recue/Date Received 2023-12-07
Date Recue/Date Received 2023-12-07
the information is acquired by accessing a local port at the smart device through a socket;
the information is transmitted in by calling a relevant interface at the software development kit after inspection performed by the client; and the information is transmitted in from an error interface of the software development kit, including an Error Code parameter and an Error Info parameter.
Date Recue/Date Received 2023-12-07
providing a heartbeat connection between a server and a smart device, for the server to receive from the smart device a heartbeat packet containing device information, service information and/or health information, wherein the server receives the heartbeat packet from a software development kit in the smart device;
at the server, data sinking the service information and/or the health information based on the device information, and synchronizing reported data of the smart device;
sending a heartbeat response from the server to the smart device, to maintain the heartbeat connection therebetween, wherein the SDK analyzes a response message to extract a heartbeat parameter (T1t); and monitoring the smart device and/or managing operation thereof based on the heartbeat connection, the service information, and/or the health information.
providing the smart device with a client and the software development kit (SDK);
providing the server with a device manager (DM);
initializing the software development kit using the client;
sending a login message from the software development kit to the device manager to request for registration;
from the device manager, returning the response message to the software development kit based on the login message; and Date Recue/Date Received 2023-12-07 at the software development kit, analyzing the response message to extract the heartbeat parameter, wherein heartbeat relationship is established between the software development kit and the device manager.
at the software development kit, automatically initiating a heartbeat request as a heartbeat packet to the device manager based on the heartbeat parameter, wherein the device information includes a device serial number, wherein the service information includes a count of transactions in a heartbeat cycle, and wherein the health information includes an error code and a corresponding error description; and wherein the software development kit fails to establish the heartbeat relationship between the software development kit and the device manager, at the software development kit, actively sending a failure notification to the client.
every time the client of the smart device generates a transaction order, recording the transaction order by calling an event tracking interface of the software development kit through the client; and at the software development kit, summing up the transaction orders recorded in one heartbeat cycle to obtain the count of transactions in current heartbeat cycle.
Date Recue/Date Received 2023-12-07 providing a united subscription service interface at the device manager, allowing a monitoring platform to acquire the service information and/or the health information from the device manager and information about the failure notification from the software development kit related to the heartbeat connection through the united subscription service interface.
after the smart device successfully data sinks reported data in the heartbeat packet, at the device manager, actively notifying a monitoring platform;
at the device manager, returning the response message carrying the latest configuration data and the heartbeat parameter to the software development kit; and according to the heartbeat parameter, sending heartbeat packets regularly from the smart device to the device manager, to maintain the heartbeat connection.
Date Recue/Date Received 2023-12-07
Date Recue/Date Received 2023-12-07
the information is acquired by accessing a local port at the smart device through a socket;
the information is transmitted in by calling a relevant interface at the software development kit after inspection performed by the client; and the information is transmitted in from an error interface of the software development kit, including an Error Code parameter and an Error Info parameter.
Date Recue/Date Received 2023-12-07
providing a heartbeat connection between a server and a smart device, for the server to receive from the smart device a heartbeat packet containing device information, service information and/or health information, wherein the server receives the heartbeat packet from a software development kit in the smart device;
at the server, data sinking the service information and/or the health information based on the device information, and synchronizing reported data of the smart device;
sending a heartbeat response from the server to the smart device, to maintain the heartbeat connection therebetween, wherein the SDK analyzes a response message to extract a heartbeat parameter (TIL); and monitoring the smart device and/or managing operation thereof based on the heartbeat connection, the service information, and/or the health information.
providing the smart device with a client and the software development kit (SDK);
providing the server with a device manager (DM);
initializing the software development kit using the client;
sending a login message from the software development kit to the device manager to request for registration;
from the device manager, returning the response message to the software development kit based on the login message; and Date Recue/Date Received 2023-12-07 at the software development kit, analyzing the response message to extract the heartbeat parameter, wherein heartbeat relationship is established between the software development kit and the device manager.
at the software development kit, automatically initiating a heartbeat request as a heartbeat packet to the device manager based on the heartbeat parameter, wherein the device information includes a device serial number, wherein the service information includes a count of transactions in a heartbeat cycle, and wherein the health information includes an error code and a corresponding error description; and wherein the software development kit fails to establish the heartbeat relationship between the software development kit and the device manager, at the software development kit, actively sending a failure notification to the client.
every time the client of the smart device generates a transaction order, recording the transaction order by calling an event tracking interface of the software development kit through the client; and at the software development kit, summing up the transaction orders recorded in one heartbeat cycle to obtain the count of transactions in current heartbeat cycle.
Date Recue/Date Received 2023-12-07 providing a united subscription service interface at the device manager, allowing a monitoring platform to acquire the service information and/or the health information from the device manager and information about the failure notification from the software development kit related to the heartbeat connection through the united subscription service interface.
after the smart device successfully data sinks reported data in the heartbeat packet, at the device manager, actively notifying a monitoring platform;
at the device manager, returning the response message carrying the latest configuration data and the heartbeat parameter to the software development kit; and according to the heartbeat parameter, sending heartbeat packets regularly from the smart device to the device manager, to maintain the heartbeat connection.
Date Recue/Date Received 2023-12-07
Date Recue/Date Received 2023-12-07
the information is acquired by accessing a local port at the smart device through a socket;
the information is transmitted in by calling a relevant interface at the software development kit after inspection performed by the client; and the information is transmitted in from an error interface of the software development kit, including an Error Code parameter and an Error Info parameter.
Date Recue/Date Received 2023-12-07
provide a heartbeat connection between a server and a smart device, for the server to receive from the smart device a heartbeat packet containing device information, service information and/or health information, wherein the server receives the heartbeat packet from a software development kit in the smart device;
at the server, data sink the service information and/or the health information based on the device information, and synchronize reported data of the smart device;
send a heartbeat response from the server to the smart device, to maintain the heartbeat connection therebetween, wherein the SDK analyzes a response message to extract a heartbeat parameter (TTL); and monitor the smart device and/or manage operation thereof based on the heartbeat connection, the service information, and/or the health information.
providing the smart device with a client and the software development kit (SDK);
providing the server with a device manager (DM);
initializing the software development kit using the client;
sending a login message from the software development kit to the device manager to request for registration;
from the device manager, returning the response message to the software development kit based on the login message; and Date Recue/Date Received 2023-12-07 at the software development kit, analyzing the response message to extract the heartbeat parameter, wherein heartbeat relationship is established between the software development kit and the device manager.
at the software development kit, automatically initiating a heartbeat request as a heartbeat packet to the device manager based on the heartbeat parameter, wherein the device information includes a device serial number, wherein the service information includes a count of transactions in a heartbeat cycle, and wherein the health information includes an error code and a corresponding error description; and wherein the software development kit fails to establish the heartbeat relationship between the software development kit and the device manager, at the software development kit, actively sending a failure notification to the client.
every time the client of the smart device generates a transaction order, recording the transaction order by calling an event tracking interface of the software development kit through the client; and at the software development kit, summing up the transaction orders recorded in one heartbeat cycle to obtain the count of transactions in current heartbeat cycle.
Date Recue/Date Received 2023-12-07 providing a united subscription service interface at the device manager, allowing a monitoring platform to acquire the service information and/or the health information from the device manager and information about the failure notification from the software development kit related to the heartbeat connection through the united subscription service interface.
after the smart device successfully data sinks reported data in the heartbeat packet, at the device manager, actively notifying a monitoring platform;
at the device manager, returning the response message carrying the latest configuration data and the heartbeat parameter to the software development kit; and according to the heartbeat parameter, sending heartbeat packets regularly from the smart device to the device manager, to maintain the heartbeat connection.
Date Recue/Date Received 2023-12-07
Date Recue/Date Received 2023-12-07
the information is acquired by accessing a local port at the smart device through a socket;
the information is transmitted in by calling a relevant interface at the software development kit after inspection performed by the client; and the information is transmitted in from an error interface of the software development kit, including an Error Code parameter and an Error Info parameter.
Date Recue/Date Received 2023-12-07
Date Recue/Date Received 2023-12-07
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA3177668A CA3177668C (en) | 2019-12-25 | 2020-08-28 | Smart device monitoring method and apparatus |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201911358092.XA CN111200538B (en) | 2019-12-25 | 2019-12-25 | Monitoring method and device for intelligent equipment |
CN201911358092.X | 2019-12-25 | ||
PCT/CN2020/111944 WO2021128915A1 (en) | 2019-12-25 | 2020-08-28 | Smart device monitoring method and apparatus |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA3177668A Division CA3177668C (en) | 2019-12-25 | 2020-08-28 | Smart device monitoring method and apparatus |
Publications (2)
Publication Number | Publication Date |
---|---|
CA3166102A1 CA3166102A1 (en) | 2021-07-01 |
CA3166102C true CA3166102C (en) | 2024-03-19 |
Family
ID=70747070
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA3166102A Active CA3166102C (en) | 2019-12-25 | 2020-08-28 | Smart device monitoring method and apparatus |
CA3177668A Active CA3177668C (en) | 2019-12-25 | 2020-08-28 | Smart device monitoring method and apparatus |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA3177668A Active CA3177668C (en) | 2019-12-25 | 2020-08-28 | Smart device monitoring method and apparatus |
Country Status (3)
Country | Link |
---|---|
CN (1) | CN111200538B (en) |
CA (2) | CA3166102C (en) |
WO (1) | WO2021128915A1 (en) |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111200538B (en) * | 2019-12-25 | 2022-03-11 | 苏宁云计算有限公司 | Monitoring method and device for intelligent equipment |
CN112351094B (en) * | 2020-11-02 | 2023-10-03 | 深圳市安软科技股份有限公司 | Webpage pushing method and device, electronic equipment and storage medium |
CN113193987B (en) * | 2021-04-08 | 2023-03-24 | 杭州迪普科技股份有限公司 | Equipment control method and device |
CN113672588A (en) * | 2021-07-16 | 2021-11-19 | 浙江大华技术股份有限公司 | Data storage method, data storage device, storage node and management node |
CN113641392B (en) * | 2021-07-16 | 2023-08-15 | 多点生活(成都)科技有限公司 | Off-line general implementation method for store terminal |
CN113746934B (en) * | 2021-09-14 | 2023-11-14 | 圆周率科技(常州)有限公司 | Service connection method and electronic equipment |
CN114237196B (en) * | 2021-11-15 | 2024-08-13 | 北京云迹科技股份有限公司 | Split robot fault processing method and device, terminal equipment and medium |
CN114221823B (en) * | 2022-02-18 | 2022-04-26 | 中航信移动科技有限公司 | Information processing method and device, electronic equipment and storage medium |
CN114640705B (en) * | 2022-04-22 | 2022-08-09 | 山东恒远智能科技有限公司 | Large-scale Internet of things terminal heartbeat monitoring method |
CN115102885B (en) * | 2022-06-17 | 2024-05-14 | 中建八局第二建设有限公司 | Variable-speed heartbeat method for low-power-consumption Internet of things equipment |
CN115794802A (en) * | 2023-01-29 | 2023-03-14 | 国网瑞嘉(天津)智能机器人有限公司 | Data real-time processing method and device, computer equipment and storage medium |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6834302B1 (en) * | 1998-12-31 | 2004-12-21 | Nortel Networks Limited | Dynamic topology notification extensions for the domain name system |
US7024473B2 (en) * | 2001-01-05 | 2006-04-04 | Matsushita Electric Works, Ltd. | Web server for communicating with one or more electronic devices through a gateway computer |
CN101854367A (en) * | 2010-06-13 | 2010-10-06 | 用友软件股份有限公司 | Method and system for server side to monitor client |
CN102257848B (en) * | 2011-05-31 | 2014-12-10 | 华为技术有限公司 | Main and secondary apparatuses conversion method betwenn communication equipment, communication equipment and system, and request equipment of system and service |
WO2013154905A1 (en) * | 2012-04-09 | 2013-10-17 | Seven Networks, Inc. | A method and system for management of a virtual network connection without heartbeat messages |
CN103841587B (en) * | 2012-11-20 | 2017-06-23 | 中国移动通信集团江苏有限公司 | A kind of implementation method, the apparatus and system of Internet of Things Convergence gateway |
WO2015042859A1 (en) * | 2013-09-27 | 2015-04-02 | 华为技术有限公司 | Method and device for asynchronous communication |
CN104754679B (en) * | 2013-12-30 | 2019-07-30 | 北京大唐高鸿数据网络技术有限公司 | Improved ZRP method for routing in vehicle-mounted short haul connection net |
CN104796445B (en) * | 2014-01-21 | 2018-06-05 | 航天信息股份有限公司 | Server node carries out the method, apparatus of source synchronous |
CN105528728A (en) * | 2015-12-09 | 2016-04-27 | 江苏易销电子商务有限公司 | Mall e-commerce service platform based on cloud computing and method thereof |
CN107124324B (en) * | 2016-02-25 | 2020-09-01 | 阿里巴巴集团控股有限公司 | Heartbeat protocol method and equipment based on lease |
WO2018125785A1 (en) * | 2016-12-31 | 2018-07-05 | General Electric Company | Real time location platform beacon protocol systems and methods |
CN108040048A (en) * | 2017-12-11 | 2018-05-15 | 福建福诺移动通信技术有限公司 | A kind of mobile client end subscriber dynamic secret key encryption communication method based on http protocol |
CN109360351A (en) * | 2018-10-25 | 2019-02-19 | 深圳怡化电脑股份有限公司 | A kind of finance self-help terminal monitory system and method |
CN109714202B (en) * | 2018-12-21 | 2021-10-08 | 郑州云海信息技术有限公司 | Client off-line reason distinguishing method and cluster type safety management system |
CN109887125B (en) * | 2019-02-02 | 2021-12-14 | 北京主线科技有限公司 | Fault detection method and device |
CN111200538B (en) * | 2019-12-25 | 2022-03-11 | 苏宁云计算有限公司 | Monitoring method and device for intelligent equipment |
-
2019
- 2019-12-25 CN CN201911358092.XA patent/CN111200538B/en active Active
-
2020
- 2020-08-28 CA CA3166102A patent/CA3166102C/en active Active
- 2020-08-28 CA CA3177668A patent/CA3177668C/en active Active
- 2020-08-28 WO PCT/CN2020/111944 patent/WO2021128915A1/en active Application Filing
Also Published As
Publication number | Publication date |
---|---|
CN111200538B (en) | 2022-03-11 |
CA3166102A1 (en) | 2021-07-01 |
WO2021128915A1 (en) | 2021-07-01 |
CA3177668A1 (en) | 2021-07-01 |
CA3177668C (en) | 2023-08-29 |
CN111200538A (en) | 2020-05-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA3166102C (en) | Smart device monitoring method and apparatus | |
US8055735B2 (en) | Method and system for forming a cluster of networked nodes | |
US7076691B1 (en) | Robust indication processing failure mode handling | |
JP4433967B2 (en) | Heartbeat device via remote duplex link on multisite and method of using the same | |
US9130967B2 (en) | Method and system for network element service recovery | |
US7886295B2 (en) | Connection manager, method, system and program product for centrally managing computer applications | |
US7937716B2 (en) | Managing collections of appliances | |
US20050210081A1 (en) | Data synchronization method | |
US20090063650A1 (en) | Managing Collections of Appliances | |
US20030196148A1 (en) | System and method for peer-to-peer monitoring within a network | |
CN106993043B (en) | Data communication system and method based on agency | |
RU2013143788A (en) | SUPPORT OF WITNESS SERVICE | |
TW200405696A (en) | Client assisted autonomic computing | |
CN106330475A (en) | Method and device for managing main and standby nodes in communication system and high availability cluster | |
US20090177743A1 (en) | Device, Method and Computer Program Product for Cluster Based Conferencing | |
CN108322358B (en) | Method and device for sending, processing and consuming multi-live distributed messages in different places | |
KR100423192B1 (en) | A method for availability monitoring via a shared database | |
CN110109772A (en) | A kind of method for restarting of CPU, communication equipment and readable storage medium storing program for executing | |
JP2003233512A (en) | Client monitoring system with maintenance function, monitoring server, program, and client monitoring/ maintaining method | |
CN110534136B (en) | Recording method and device | |
CN109474694A (en) | A kind of management-control method and device of the NAS cluster based on SAN storage array | |
CN100359865C (en) | Detecting method | |
CN107465727B (en) | Time monitoring system and method | |
US7127637B2 (en) | Method and apparatus for high availability distributed processing across independent networked computer fault groups | |
KR100970211B1 (en) | Method and Apparatus for Monitoring Service Status Via Special Message Watcher in Authentication Service System |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |
|
EEER | Examination request |
Effective date: 20220627 |