CN108377563B - Method for managing wearable equipment, server and client - Google Patents
Method for managing wearable equipment, server and client Download PDFInfo
- Publication number
- CN108377563B CN108377563B CN201610981988.3A CN201610981988A CN108377563B CN 108377563 B CN108377563 B CN 108377563B CN 201610981988 A CN201610981988 A CN 201610981988A CN 108377563 B CN108377563 B CN 108377563B
- Authority
- CN
- China
- Prior art keywords
- server
- wearable device
- user name
- module
- client
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B1/00—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
- H04B1/38—Transceivers, i.e. devices in which transmitter and receiver form a structural unit and in which at least one part is used for functions of transmitting and receiving
- H04B1/3827—Portable transceivers
- H04B1/385—Transceivers carried on the body, e.g. in helmets
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a method for managing wearable equipment, a server and a client. The method for managing the wearable equipment comprises the following steps: the method comprises the steps that a client logged in by a current user name obtains a mark code of wearable equipment, obtains a feature code of a current mobile terminal connected with the wearable equipment at present, and then sends the mark code and the feature code to a server; the server side inquires a local pre-stored binding relation record table according to the mark code to obtain a user name bound with the mark code and a bound feature code, wherein the binding relation record table is used for recording the binding relation among the mark code of the wearable device, the user name and the feature code of the mobile terminal; and the server judges whether the feature code of the current mobile terminal is the same as the bound feature code, and if not, the server sends an abnormal reminding notice to the client logged in by the bound user name.
Description
Technical Field
The invention relates to the technical field of computers and software thereof, in particular to a method for managing wearable equipment, a server and a client.
Background
Wearable devices refer to portable devices that are worn directly on the body or integrated into the clothing or accessories of the user. Wearable equipment is not only a hardware, but also hardware software integrated equipment which realizes powerful functions through software support, data interaction and cloud interaction. Wearable devices will bring great changes to our lives and perceptions.
The existing anti-theft measures of the wearable device generally act on the instant that the device is stolen, for example, the wearable device gives an alarm when being disconnected with a mobile phone Bluetooth, and prompts a user to timely recover the stolen device. However, in a place with dense people flow, such as a subway or a station, the user may ignore the alarm signal. And after the user responds that the wearable equipment is stolen, the wearable equipment can be retrieved basically without any technical means.
Disclosure of Invention
In view of this, the present invention provides a method, a server and a client for managing a wearable device with good usability.
To achieve the above object, according to one aspect of the present invention, there is provided a method of managing a wearable device.
The method for managing the wearable device comprises the following steps: the method comprises the steps that a client logged in by a current user name obtains a mark code of wearable equipment, obtains a feature code of a current mobile terminal connected with the wearable equipment at present, and then sends the mark code and the feature code to a server; the server side inquires a locally pre-stored binding relationship record table according to the mark code to obtain a user name bound with the mark code and a bound feature code, wherein the binding relationship record table is used for recording the binding relationship among the mark code of the wearable device, the user name and the feature code of the mobile terminal; and the server judges whether the feature code of the current mobile terminal is the same as the bound feature code, and if not, the server sends an abnormal reminding notice to the client logged in by the bound user name.
Optionally, before the step of sending the flag code and the feature code to the server, the method further includes: the client acquires the current user name and/or the current position data of the wearable device; before the step of the server querying a locally pre-stored binding relationship record table according to the flag code, the method further includes: the server receives the current user name and/or the current position data of the wearable device sent by the client; after the step of sending an abnormal reminding notification to the client logged in by the bound user name by the server, the method further comprises the following steps: after receiving a stolen recovery instruction sent by a user, the client logged in by the bound user name sends an information acquisition request to the server; and after receiving the information acquisition request, the server sends the current user name and/or the current position data of the wearable device to the client logged in by the bound user name.
Optionally, after the step of sending an abnormal alert notification to the client logged in with the bound username, the method further includes: after receiving a rebinding instruction sent by a user, the client logged in by the bound user name sends a rebinding request to the server; and after receiving the re-binding request, the server modifies the feature code of the bound mobile terminal corresponding to the equipment mark code in the binding relation record table into the feature code of the current mobile terminal.
To achieve the above object, according to still another aspect of the present invention, there is provided a server for managing a wearable device.
The server for managing the wearable equipment comprises a receiving module, an inquiring module, a judging module and a sending module, wherein: the receiving module is used for receiving the mark code of the wearable equipment and the feature code of the current mobile terminal sent by the client logged in by the current user name, and the current mobile terminal is connected with the wearable equipment; the inquiry module is used for inquiring a local pre-stored binding relationship record table according to the mark code so as to obtain a user name bound with the mark code and a bound feature code, wherein the binding relationship record table is used for recording the binding relationship among the mark code of the wearable device, the user name and the feature code of the mobile terminal; the judging module is used for judging whether the feature code of the current mobile terminal is the same as the bound feature code; and the sending module is used for sending an abnormal reminding notice to the client logged in by the bound user name under the condition that the judgment result of the judging module is negative.
Optionally, the receiving module is further configured to receive the current user name and/or the current location data of the wearable device sent by the client; receiving an information acquisition request sent by a client; the sending module is further configured to send the current user name and/or the current location data of the wearable device to the client logged in with the bound user name according to the information acquisition request.
Optionally, the system further comprises a re-binding module, and the receiving module is further configured to receive a re-binding request sent by the client; and the rebinding module is used for modifying the feature code of the binding mobile terminal corresponding to the equipment mark code in the binding relation record table into the feature code of the current mobile terminal according to the rebinding request.
To achieve the above object, according to still another aspect of the present invention, there is provided a client managing a wearable device.
The client for managing the wearable equipment comprises a first acquisition module, a first sending module and a first receiving module, wherein: the first acquisition module is used for acquiring a mark code of the wearable device and acquiring a feature code of a current mobile terminal currently connected with the wearable device; the first sending module is used for sending the mark code and the feature code to a server; the first receiving module is used for receiving an abnormal reminding notification sent by the server.
Optionally, the system further includes a first user interaction module, a second obtaining module, a second sending module, and a second receiving module, where: the first user interaction module is used for receiving a stolen recovery instruction sent by a user; the second acquisition module is used for acquiring the current user name and/or the current position data of the wearable device; the second sending module is used for sending the current user name and/or the current position data of the wearable device to a server and sending an information acquisition request to the server according to the stolen retrieval instruction; the second receiving module is used for receiving the current user name and/or the current position data of the wearable device sent by the server.
Optionally, the system further comprises a second user interaction module and a third sending module, wherein: the second user interaction module is used for receiving a rebinding instruction sent by a user; and the third sending module is used for sending a rebinding request to the server according to the rebinding instruction.
To achieve the above object, according to still another aspect of embodiments of the present invention, there is provided an electronic apparatus.
An electronic device of an embodiment of the present invention includes: one or more processors; a storage device for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement a method of managing a wearable device of an embodiment of the invention.
To achieve the above object, according to still another aspect of embodiments of the present invention, there is provided a computer-readable medium.
A computer-readable medium of an embodiment of the invention has stored thereon a computer program that, when executed by a processor, implements a method of managing a wearable device of an embodiment of the invention.
According to the technical scheme of the invention, whether the wearable device is abnormal in use is judged by detecting whether the current mobile terminal connected with the wearable device is the same as the history binding mobile terminal. Such warning logic as long as wearable equipment is launched by thief or other illegal identity person and just can judge, need not to require wearable equipment's owner to make a response in stolen instant to user experience has been promoted, has advantages such as good reliability, degree of safety height, intellectuality.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
fig. 1 is a schematic diagram of the main steps of a method of managing a wearable device according to an embodiment of the invention;
fig. 2 is a schematic diagram of the main modules of a server managing a wearable device according to an embodiment of the invention;
fig. 3 is a schematic diagram of the main modules of a client managing a wearable device according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of the main steps of a method according to an embodiment of the invention. As shown in fig. 1, the method of the embodiment of the present invention may mainly include steps a to C as follows.
Step A: the client logged in with the current user name acquires the mark code of the wearable device, acquires the feature code of the current mobile terminal connected with the wearable device, and then sends the mark code and the feature code to the server.
The user name is an identity mark code of a user login server, and the user name usually adopts a mobile phone number of the user in real life. The identification code of the wearable device refers to a unique identity code which each piece of wearable device has. The feature code of the Mobile terminal may be the international Mobile Equipment identity imei (international Mobile Equipment identity). The IMEI is composed of 15 digits or English letters and has uniqueness.
And B: the server side inquires a local pre-stored binding relation record table according to the mark code so as to obtain the user name bound with the mark code and the bound feature code, wherein the binding relation record table is used for recording the binding relation among the mark code of the wearable device, the user name and the feature code of the mobile terminal.
And C: and the server judges whether the feature code of the current mobile terminal is the same as the bound feature code, and if not, the server sends an abnormal reminding notice to the client logged in by the bound user name.
According to the method for managing the wearable device, whether the wearable device is abnormally used or not is judged by detecting whether the current mobile terminal connected with the wearable device is the same as the history binding mobile terminal or not. Such warning logic as long as wearable equipment is launched by thief or other illegal identity person and just can judge, need not to require wearable equipment's owner to make a response in stolen instant to user experience has been promoted, has advantages such as good reliability, degree of safety height, intellectuality.
According to the method for managing the wearable device of the embodiment of the invention, before the step of sending the identifier code and the feature code to the server, the method may further include: the client acquires the current user name and/or the current position data of the wearable device (for example, the client logged in by the current user name acquires the identifier of the wearable device, the feature code of the current mobile terminal, and the current user name and/or the current position data of the wearable device at the same time). Before the step of the server querying the locally pre-stored binding relationship record table according to the flag code, the method may further include: the server receives the current user name and/or the current position data of the wearable device sent by the client (for example, the client logged in by the current user name sends the identifier of the wearable device, the feature code of the current mobile terminal, and the current user name and/or the current position data of the wearable device to the server at the same time). After the step of sending an abnormal reminding notification to the client logged in by the bound user name by the server, the method may further include: after receiving a stolen recovery instruction sent by a user, a client logged in by using a bound user name sends an information acquisition request to a server; and after receiving the information acquisition request, the server sends the current user name and/or the current position data of the wearable device to the client logged in by the bound user name. The method for managing the wearable device of the embodiment can recover the stolen wearable device by using the current user name and/or the current position data of the wearable device after the wearable device is stolen.
According to the method for managing the wearable device in the embodiment of the present invention, after the step of sending the abnormal reminding notification to the client logged in with the bound user name by the server, the method may further include: after receiving a rebinding instruction sent by a user, a client logged in with a bound user name sends a rebinding request to a server; and after receiving the re-binding request, the server modifies the feature code of the bound mobile terminal corresponding to the equipment mark code in the binding relation record table into the feature code of the current mobile terminal. The method for managing the wearable device of the embodiment can realize the function of binding the wearable device with the new mobile terminal.
In order that those skilled in the art will better understand the disclosure of the present invention, the following detailed description is given with reference to specific embodiments.
One of the specific application scenarios is: the wearable device attempts to recover after being stolen.
Assuming that the user name of the owner is the mobile phone number 13900000000 of the owner, the identification code of the wearable device owned by the owner is X, and the feature code of the mobile terminal used by the owner is IMEI1, the mobile terminal is loaded with the client a. Assuming that the user name of the thief is 13111111111 of the mobile phone number of the thief, and the feature code of the mobile terminal used by the thief is IMEI2, the mobile terminal is provided with client B (client a and client B are essentially the same, but are provided on different mobile terminals).
First, the owner logs in the client a by using "13900000000", and the client a acquires the identifier X of the wearable device and the feature code IMEI1 of the mobile terminal used by the owner. The client a then sends the signpost code X, the username 13900000000 and the feature code IMEI1 together to the server. The server side saves the binding record of X-13900000000-IMEI1 in the binding relation record table data.
Subsequently, the thief steals the owner's wearable device. The thief then connects the wearable device to the thief's mobile terminal and then logs in to client B with the username "13111111111". At this time, the client B sends the acquired identifier code X, the current login user name 13111111111, and the feature code IMEI2 to the server.
Then, the server side queries the binding relation record table data according to the identifier X, and obtains that the feature code of the bound mobile terminal should be IMEI 1. Since the server determines that the feature code IMEI1 of the bound mobile terminal is inconsistent with the feature code IMEI2 of the currently connected mobile terminal, the server sends an exception alert notification to the client a logged in with the bound username 13900000000.
Then, after receiving the abnormal reminding notification, the client A provides two options of 'stolen recovery' and 'rebinding' for the owner. In this application scenario, the user issues a stolen recovery instruction to the client a. And the client A sends an information acquisition request to the server according to the stolen recovery instruction.
Finally, the server sends 13111111111 the current user name to the client a according to the request for obtaining information. Therefore, the owner can know the mobile phone number of the thief and can further take measures to actively retrieve the wearable device.
It should be noted that, in a preferred embodiment, the current login client (i.e., client B corresponding to the thief) may also collect current location data of the wearable device and upload the current location data to the server. And after the server receives the information acquisition request, the server also sends the current position data of the wearable device to the client corresponding to the bound user name (namely, the client A corresponding to the owner). This allows the owner to better orient the recovery of stolen equipment.
The second specific application scenario is: the wearable device is re-bound with the new mobile terminal.
Suppose the owner's user name is the owner's cell phone number 13900000000 and the owner's wearable device has an identification code of X. The owner uses the old mobile terminal with the IMEI1 as the feature code, and the mobile terminal has the client a loaded thereon. The feature code of the new mobile terminal used by the owner is IMEI3, and the mobile terminal has client C installed thereon (client C and client a are essentially the same, but installed on different mobile terminals).
First, the owner logs in the client a by using "13900000000", and the client a acquires the identifier X of the wearable device and the feature code IMEI1 of the old mobile terminal used by the owner. The client a then sends the signpost code X, the username 13900000000 and the feature code IMEI1 together to the server. The server side saves the binding record of X-13900000000-IMEI1 in the binding relation record table data.
The owner then changes the new mobile terminal. The owner connects the wearable device to the new mobile terminal and then still logs in to client C with the user name "13900000000". At this time, the client C sends the obtained identifier code X, the user name 13900000000, and the feature code IMEI3 to the server.
Then, the server side queries the binding relation record table data according to the identifier X, and obtains that the feature code of the bound mobile terminal should be IMEI 1. Since the server determines that the IMEI1 of the bound old mobile terminal is inconsistent with the IMEI3 of the currently connected new mobile terminal, the server sends an exception notification to the client C logged in with the username 13900000000.
Then, after receiving the abnormal reminding notification, the client C provides two options of "stolen recovery" and "rebinding" to the owner. In this application scenario, the owner issues a rebinding instruction to the client C. And the client C sends a rebinding request to the server according to the rebinding instruction.
Finally, the server modifies the IMEI1 in the X-13900000000-IMEI1 in the binding relation record table data into the IMEI3 according to the rebinding request. At this point, a new binding relationship record is established.
According to the two specific application scenarios, after the method for managing the wearable device is adopted, whether the relevant mobile phone terminal information bound by the wearable device is changed or not can be automatically judged. Under the condition of change, the system automatically notifies the original user of the related latest information, so that the user can easily retrieve the lost device or change the binding information.
Fig. 2 is a schematic diagram of the main modules of a server managing a wearable device according to an embodiment of the present invention. As shown in fig. 2, the server 20 for managing a wearable device according to an embodiment of the present invention includes: a receiving module 21, an inquiring module 22, a judging module 23 and a sending module 24.
The receiving module 21 is configured to receive an identifier of the wearable device and a feature code of a current mobile terminal from a client logged in with a current user name, where the current mobile terminal is connected to the wearable device.
The query module 22 is configured to query the locally pre-stored binding relationship record table according to the identifier to obtain the user name bound to the identifier and the bound feature code. The binding relationship recording table is used for recording the binding relationship among the mark code of the wearable device, the user name and the feature code of the mobile terminal.
The judging module 23 is configured to judge whether the feature code of the current mobile terminal is the same as the bound feature code.
The sending module 24 is configured to send an exception prompting notification to the client logged in with the bound user name if the determination result of the determining module is negative.
According to the server for managing the wearable device, the receiving module can be further used for receiving the current user name and/or the current position data of the wearable device sent by the client; and receiving an information acquisition request sent by a client. And the sending module may be further configured to send the current user name and/or the current location data of the wearable device to the client logged in with the bound user name according to the information acquisition request.
The server for managing the wearable device according to the embodiment of the invention can further comprise a rebinding module. The receiving module in the server is further configured to receive a rebinding request sent by the client. And the rebinding module is used for modifying the feature code of the bound mobile terminal corresponding to the equipment mark code in the binding relation record table into the feature code of the current mobile terminal according to the rebinding request.
Fig. 3 is a schematic diagram of the main modules of a client managing a wearable device according to an embodiment of the present invention. As shown in fig. 2, the client 30 for managing a wearable device according to an embodiment of the present invention includes: a first acquisition module 31, a first sending module 32 and a first receiving module 33.
The first obtaining module 31 is configured to obtain an identifier of the wearable device, and obtain a feature code of a current mobile terminal currently connected to the wearable device.
The first sending module 32 is configured to send the identifier code and the feature code to the server.
The first receiving module 33 is configured to receive an exception notification sent by the server.
The client for managing the wearable device according to the embodiment of the present invention may further include a first user interaction module, a second obtaining module, a second sending module, and a second receiving module (not shown in fig. 3). Wherein: the first user interaction module is used for receiving a stolen recovery instruction sent by a user. The second obtaining module is used for obtaining the current user name and/or the current position data of the wearable device. The second sending module is used for sending the current user name and/or the current position data of the wearable device to the server and sending an information obtaining request to the server according to the stolen retrieving instruction. The second receiving module is used for receiving the current user name and/or the current position data of the wearable device sent by the server.
The client for managing the wearable device according to the embodiment of the present invention may further include a second user interaction module and a third transmission module (not shown in fig. 3). Wherein: the second user interaction module is used for receiving a rebinding instruction sent by a user. And the third sending module is used for sending a rebinding request to the server according to the rebinding instruction.
According to the server and the client for managing the wearable device, whether the wearable device is abnormal in use is judged by detecting whether the current mobile terminal connected with the wearable device is the same as the historical binding mobile terminal. Such warning logic as long as wearable equipment is launched by thief or other illegal identity person and just can judge, need not to require wearable equipment's owner to make a response in stolen instant to user experience has been promoted, has advantages such as good reliability, degree of safety height, intellectuality.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (6)
1. A method of managing a wearable device, comprising:
the method comprises the steps that a client logged in by a current user name obtains a mark code of wearable equipment, obtains a feature code of a current mobile terminal connected with the wearable equipment at present, and then sends the mark code and the feature code to a server;
the server side inquires a locally pre-stored binding relationship record table according to the mark code to obtain a user name bound with the mark code and a bound feature code, wherein the binding relationship record table is used for recording the binding relationship among the mark code of the wearable device, the user name and the feature code of the mobile terminal, and the user name is an identity mark code of a user login server side;
when the wearable device is started, the server side judges whether the feature code of the current mobile terminal is the same as the bound feature code, if not, the wearable device is abnormal in use, and the server side sends an abnormal reminding notice to a client side logged in by the bound user name;
before the step of sending the flag code and the feature code to the server, the method further includes: the client acquires the current user name and/or the current position data of the wearable device;
before the step of the server querying a locally pre-stored binding relationship record table according to the flag code, the method further includes: the server receives the current user name and/or the current position data of the wearable device sent by the client;
after the step of sending an abnormal reminding notification to the client logged in by the bound user name by the server, the method further comprises the following steps: after receiving a stolen recovery instruction sent by a user, the client logged in by the bound user name sends an information acquisition request to the server; and after receiving the information acquisition request, the server sends the current user name and/or the current position data of the wearable device to the client logged in by the bound user name.
2. The method for managing a wearable device according to claim 1, wherein after the step of the server issuing an abnormal alert notification to the client logged in with the bound username, the method further comprises:
after receiving a rebinding instruction sent by a user, the client logged in by the bound user name sends a rebinding request to the server;
and after receiving the re-binding request, the server modifies the feature code of the bound mobile terminal corresponding to the equipment mark code in the binding relation record table into the feature code of the current mobile terminal.
3. The utility model provides a server side of management wearable equipment, its characterized in that includes receiving module, inquiry module, judgement module and sending module, wherein:
the receiving module is used for receiving the mark code of the wearable equipment and the feature code of the current mobile terminal sent by the client logged in by the current user name, and the current mobile terminal is connected with the wearable equipment;
the inquiry module is used for inquiring a local pre-stored binding relationship record table according to the mark code so as to obtain a user name bound with the mark code and a bound feature code, wherein the binding relationship record table is used for recording the binding relationship among the mark code of the wearable device, the user name and the feature code of the mobile terminal, and the user name is an identity mark code of a user login server;
the judging module is used for judging whether the feature code of the current mobile terminal is the same as the bound feature code or not when the wearable device is started;
the sending module is used for sending an abnormal reminding notice to a client logged in by a bound user name when the wearable device is abnormal in use under the condition that the judgment result of the judging module is negative;
the receiving module is further configured to receive the current user name and/or the current location data of the wearable device sent by the client; receiving an information acquisition request sent by a client;
the sending module is further configured to send the current user name and/or the current location data of the wearable device to the client logged in with the bound user name according to the information acquisition request.
4. The server for managing a wearable device according to claim 3, further comprising a re-binding module,
the receiving module is also used for receiving a rebinding request sent by the client;
and the rebinding module is used for modifying the feature code of the binding mobile terminal corresponding to the equipment mark code in the binding relation record table into the feature code of the current mobile terminal according to the rebinding request.
5. The client for managing the wearable equipment is characterized by comprising a first acquisition module, a first sending module and a first receiving module, wherein:
the first acquisition module is used for acquiring a mark code of the wearable device and acquiring a feature code of a current mobile terminal currently connected with the wearable device;
the first sending module is used for sending the mark code and the feature code to a server;
the first receiving module is used for receiving an abnormal reminding notification sent by the server;
the client for managing the wearable device further comprises a first user interaction module, a second acquisition module, a second sending module and a second receiving module, wherein:
the first user interaction module is used for receiving a stolen recovery instruction sent by a user;
the second acquisition module is used for acquiring the current user name and/or the current position data of the wearable device;
the second sending module is used for sending the current user name and/or the current position data of the wearable device to a server and sending an information acquisition request to the server according to the stolen retrieval instruction;
the second receiving module is used for receiving the current user name and/or the current position data of the wearable device sent by the server.
6. The client managing a wearable device according to claim 5, further comprising a second user interaction module and a third sending module, wherein:
the second user interaction module is used for receiving a rebinding instruction sent by a user;
and the third sending module is used for sending a rebinding request to the server according to the rebinding instruction.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610981988.3A CN108377563B (en) | 2016-11-08 | 2016-11-08 | Method for managing wearable equipment, server and client |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610981988.3A CN108377563B (en) | 2016-11-08 | 2016-11-08 | Method for managing wearable equipment, server and client |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108377563A CN108377563A (en) | 2018-08-07 |
| CN108377563B true CN108377563B (en) | 2021-08-20 |
Family
ID=63015148
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610981988.3A Active CN108377563B (en) | 2016-11-08 | 2016-11-08 | Method for managing wearable equipment, server and client |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108377563B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111083635A (en) * | 2019-12-25 | 2020-04-28 | 联想(北京)有限公司 | Reminding method, terminal and reminding system |
| CN112672278A (en) * | 2020-12-17 | 2021-04-16 | 南昌逸勤科技有限公司 | Positioning method and device of wearable equipment |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103248489A (en) * | 2013-05-17 | 2013-08-14 | 刘琦 | Method for realizing client login through intelligent terminal, server and intelligent terminal |
| CN103901769A (en) * | 2013-04-01 | 2014-07-02 | 杭州惠道科技有限公司 | Intelligent watch |
| CN104065712A (en) * | 2014-06-17 | 2014-09-24 | 成都雅鲁科技有限公司 | System applied to intelligent bracelet capable of preventing children from being lost |
| CN104468581A (en) * | 2014-12-10 | 2015-03-25 | 小米科技有限责任公司 | Method and device for logging into application program |
| CN104601327A (en) * | 2013-12-30 | 2015-05-06 | 腾讯科技（深圳）有限公司 | Safe verification method, relative apparatus and system |
| CN104753679A (en) * | 2015-03-05 | 2015-07-01 | 北京畅游天下网络技术有限公司 | User authentication method and system as well as intelligent wearing equipment |
| CN105278686A (en) * | 2015-09-30 | 2016-01-27 | 宇龙计算机通信科技(深圳)有限公司 | Safety prompt method and device for smart wearable device |
| CN105491524A (en) * | 2015-12-11 | 2016-04-13 | 小米科技有限责任公司 | Method and apparatus for determining position of object portable device |
-
2016
- 2016-11-08 CN CN201610981988.3A patent/CN108377563B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103901769A (en) * | 2013-04-01 | 2014-07-02 | 杭州惠道科技有限公司 | Intelligent watch |
| CN103248489A (en) * | 2013-05-17 | 2013-08-14 | 刘琦 | Method for realizing client login through intelligent terminal, server and intelligent terminal |
| CN104601327A (en) * | 2013-12-30 | 2015-05-06 | 腾讯科技（深圳）有限公司 | Safe verification method, relative apparatus and system |
| CN104065712A (en) * | 2014-06-17 | 2014-09-24 | 成都雅鲁科技有限公司 | System applied to intelligent bracelet capable of preventing children from being lost |
| CN104468581A (en) * | 2014-12-10 | 2015-03-25 | 小米科技有限责任公司 | Method and device for logging into application program |
| CN104753679A (en) * | 2015-03-05 | 2015-07-01 | 北京畅游天下网络技术有限公司 | User authentication method and system as well as intelligent wearing equipment |
| CN105278686A (en) * | 2015-09-30 | 2016-01-27 | 宇龙计算机通信科技(深圳)有限公司 | Safety prompt method and device for smart wearable device |
| CN105491524A (en) * | 2015-12-11 | 2016-04-13 | 小米科技有限责任公司 | Method and apparatus for determining position of object portable device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108377563A (en) | 2018-08-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2017177830A1 (en) | Two-dimensional code-based method and system for seeking ward | |
| US20150207917A1 (en) | Mobile terminal intelligent anti-theft method and mobile terminal | |
| EP4156724A1 (en) | Monitoring objects capable of wireless communications | |
| CN104066050A (en) | Method for preventing communication terminal from getting lost, communication terminal and server | |
| JP2015511735A (en) | Software installation method, device and system | |
| CN102497635A (en) | Server, terminal and account password acquisition method | |
| CN103150776B (en) | A kind of attendance checking system based on navigator fix and living things feature recognition and method | |
| WO2013166886A1 (en) | Anti-theft method, device and system for portable computer equipment | |
| US10638270B2 (en) | Location-based wireless tracking | |
| CN103607697A (en) | Terminal anti-theft method and system based on SIM card | |
| CN104202172A (en) | Pairing Bluetooth anti-lost and warning system based on BLE technology and web database | |
| CN104427468A (en) | Automatic alarming method and device of mobile terminal | |
| WO2015077947A1 (en) | System for recovering lost device | |
| CN105744071A (en) | One-key emergency help system and method based on fingerprint identification | |
| CN102843405A (en) | Mobile terminal, network server and method for anti-theft service of mobile terminal | |
| WO2015117315A1 (en) | Tracking method, tracking server and tracking system | |
| CN108377563B (en) | Method for managing wearable equipment, server and client | |
| CN105376711A (en) | Position prompting method and apparatus of wearable device, and wearable device | |
| KR20190009375A (en) | Method and apparatus for notifying terminal loss | |
| CN104994224A (en) | Antitheft method and device for mobile terminal | |
| TW201525951A (en) | Roadblock device, road condition management device, road condition management system and method | |
| CN105007571A (en) | Information processing method and service equipment | |
| CN107580132B (en) | Information sending method, information sending device, storage medium and electronic equipment | |
| CN104244410A (en) | Positioning method and system | |
| WO2017177789A1 (en) | Anti-theft method and device for mobile terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |