CN108377563A - Manage method, server-side and the client of wearable device - Google Patents
Manage method, server-side and the client of wearable device Download PDFInfo
- Publication number
- CN108377563A CN108377563A CN201610981988.3A CN201610981988A CN108377563A CN 108377563 A CN108377563 A CN 108377563A CN 201610981988 A CN201610981988 A CN 201610981988A CN 108377563 A CN108377563 A CN 108377563A
- Authority
- CN
- China
- Prior art keywords
- wearable device
- server
- binding
- user name
- 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.)
- Granted
Links
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 present invention provides method, server-side and the clients of management wearable device.Wherein, the method for management wearable device of the invention includes：The identity code of wearable device is obtained with the client that current user name logs in, and obtains the condition code for the current mobile terminal currently being connect with wearable device, and identity code and condition code are then sent to server-side；Server-side inquires the binding relationship record sheet locally to prestore according to identity code, to obtain the condition code of the user name bound with identity code and binding, wherein binding relationship record sheet is used to record the binding relationship between the condition code three of the identity code of wearable device, user name and mobile terminal；Server-side judge current mobile terminal condition code and binding condition code it is whether identical, if differing, server-side sends out abnormity prompt notice to the client logged in the user name of binding.
Description
Technical field
The present invention relates to computer and its software technology field, particularly a kind of method of management wearable device,
Server-side and client.
Background technology
Wearable device refers to the portable device for directly wearing or being integrated into the clothes or accessory of user.It can
Wearable device is not only a kind of hardware, is even more interacted by software support and data interaction, high in the clouds to realize powerful work(
The hardware-software package of energy.Wearable device will bring prodigious transformation to our life, perception.
The moment that existing wearable device anti-theft measure general action is stolen in equipment works, such as wearable device
It alarms when being disconnected with Bluetooth of mobile phone, user is prompted to recover stolen equipment in time.But crowded place for example
The places such as subway or station, user are possible to that alarm signal can have been neglected.Equal users react wearable device quilt afterwards
It steals, can but be recovered without any technological means substantially.
Invention content
In view of this, the present invention provides method, server-side and the client of a kind of good management wearable device of availability
End.
To achieve the above object, according to an aspect of the invention, there is provided a kind of method of management wearable device.
The method of the management wearable device of the present invention, including：It is obtained with the client that current user name logs in wearable
The identity code of equipment, and the condition code for the current mobile terminal currently being connect with wearable device is obtained, then by the mark
Will code and described document information are sent to server-side；The server-side is remembered according to the binding relationship that identity code inquiry locally prestores
Table is recorded, to obtain the condition code of the user name and binding bound with the identity code, wherein the binding relationship record sheet is used for
Record the binding relationship between the condition code three of the identity code of wearable device, user name and mobile terminal；The service
End judges whether the condition code of the current mobile terminal is identical as the condition code of the binding, if differing, the server-side
Abnormity prompt notice is sent out to the client logged in the user name of binding.
Optionally, before the described the step of identity code and described document information are sent to server-side, further include：It is described
Client obtains the current user name and/or the wearable device current location data；The server-side is according to the mark
Will code was inquired before the step of binding relationship record sheet locally to prestore, further included：The server-side receives the client hair
The current user name and/or the wearable device current location data sent；The server-side is to the user name of binding
After the client of login sends out the step of abnormity prompt notice, further include：The client that the user name with binding logs in
Receive that user sends out it is stolen recover instruction after, send out acquisition information request to the server-side；The server-side receives
After the acquisition information request, the client logged in the user name with binding sends the current user name and/or institute
State wearable device current location data.
Optionally, the server-side to the client logged in the user name of binding send out the step of abnormity prompt notifies it
Afterwards, further include：After the client that the user name with binding logs in receives the instruction of binding again that user sends out, to the clothes
Business end sends out bind request again；After the server-side receives the bind request again, by the binding relationship record sheet
Described in the condition code of the corresponding binding mobile terminal of device flag code be revised as the condition code of current mobile terminal.
To achieve the above object, according to a further aspect of the invention, a kind of service of management wearable device is provided
End.
The server-side of the management wearable device of the present invention, including receiving module, enquiry module, judgment module and transmission mould
Block, wherein：The receiving module is used to receive the identity code for the wearable device that the client logged in current user name is sent
With the condition code of current mobile terminal, which connect with the wearable device；The enquiry module is used for root
The binding relationship record sheet locally to prestore is inquired according to the identity code, to obtain the user name bound with the identity code and binding
Condition code, wherein the binding relationship record sheet is used to record identity code, user name and the mobile terminal of wearable device
Condition code three between binding relationship；The judgment module be used to judge the condition code of the current mobile terminal with it is described
Whether the condition code of binding is identical；The sending module is used in the case where the judging result of the judgment module is no, to
The client logged in the user name of binding sends out abnormity prompt notice.
Optionally, the receiving module is additionally operable to receive the current user name that the client is sent and/or described
Wearable device current location data；Receive the acquisition information request that client is sent；The sending module is additionally operable to according to institute
It states and obtains the client that information request is logged in the user name with binding and send the current user name and/or described wear
Wear equipment current location data.
Optionally, further include again binding module, the receiving module is additionally operable to receive the binding again that client is sent
Request；Again the binding module is used for according to again bind request by equipment mark described in the binding relationship record sheet
The condition code of the corresponding binding mobile terminal of will code is revised as the condition code of current mobile terminal.
To achieve the above object, according to a further aspect of the invention, a kind of client of management wearable device is provided
End.
The client of the management wearable device of the present invention, including the first acquisition module, the first sending module and first connect
Module is received, wherein：First acquisition module is used to obtain the identity code of wearable device, and obtains and currently set with wearable
The condition code of the current mobile terminal of standby connection；First sending module is used to send the identity code and described document information
To server-side；First receiving module is used to receive the abnormity prompt notice that the server-side is sent.
Optionally, further include the first user interactive module, the second acquisition module, the second sending module and the second reception mould
Block, wherein：First user interactive module is used to receive that user to send out stolen recovers instruction；Second acquisition module is for obtaining institute
State current user name and/or the wearable device current location data；Second sending module is used for described in server-side transmission
Current user name and/or the wearable device current location data, and instructed to the service according to stolen recover
End sends out acquisition information request；Second receiving module is used to receive the current user name that the server-side is sent and/or wearable
Equipment current location data.
Optionally, further include second user interactive module and third sending module, wherein：Second user interactive module is used for
Receive the instruction of binding again that user sends out；Third sending module is used to bind instruction again according to and be sent out to the server-side
Go out bind request again.
According to the technique and scheme of the present invention, it is bound with history by detecting the current mobile terminal being connect with wearable device
Whether whether mobile terminal is identical, to judge wearable device using abnormal.As long as such prompting logic wearable device quilt
Thief or other illegal identity persons enable and can be carried out judging, without requiring the owner of wearable device instantaneously to be done stolen
Go out reaction, to which the user experience is improved, has many advantages, such as that good reliability, safe coefficient are high, intelligent.
Description of the drawings
Attached drawing does not constitute inappropriate limitation of the present invention for more fully understanding the present invention.Wherein：
Fig. 1 is the schematic diagram according to the key step of the method for the management wearable device of embodiment of the present invention；
Fig. 2 is the schematic diagram according to the main modular of the server-side of the management wearable device of embodiment of the present invention；
Fig. 3 is the schematic diagram according to the main modular of the client of the management wearable device of embodiment of the present invention.
Specific implementation mode
It explains to the exemplary embodiment of the present invention below in conjunction with attached drawing, including embodiment of the present invention
Various details should think them only exemplary to help understanding.Therefore, those of ordinary skill in the art should recognize
Know, various changes and modifications can be made to embodiment described herein, without departing from scope and spirit of the present invention.
Equally, for clarity and conciseness, the description to known function and structure is omitted in following description.
Fig. 1 is the schematic diagram according to the key step of the method for embodiment of the present invention.As shown in Figure 1, the present invention is implemented
The method of mode can include mainly following step A to step C.
Step A：With current user name log in client obtain wearable device identity code, and obtain currently with can
The condition code of the current mobile terminal of wearable device connection, is then sent to server-side by identity code and condition code.
User name is the identity tag code of user login services device, the hand of user name generally use user in actual life
Machine number.The identity code of wearable device refers to the identity code for the uniqueness that every wearable device has.The spy of mobile terminal
It can be International Mobile Station Equipment Identification IMEI (International Mobile Equipment Identity) to levy code.IMEI
It is made of 15 bit digitals or English alphabet, there is uniqueness.
Step B：Server-side inquires the binding relationship record sheet locally to prestore according to identity code, to obtain binding with identity code
User name and binding condition code, wherein binding relationship record sheet for record identity code, the user name of wearable device with
And the binding relationship between the condition code three of mobile terminal.
Step C：Server-side judge current mobile terminal condition code and binding condition code it is whether identical, if differing,
Server-side sends out abnormity prompt notice to the client logged in the user name of binding.
According to the method for the management wearable device of embodiment of the present invention, worked as by what detection was connect with wearable device
Whether whether preceding mobile terminal and history binding mobile terminal are identical, to judge wearable device using abnormal.Such prompting
As long as logic wearable device is enabled by thief or other illegal identity persons and can be carried out judging, without requiring wearable set
Standby owner instantaneously makes a response stolen, to which the user experience is improved, has good reliability, safe coefficient high, intelligent
The advantages that.
According to the method for the management wearable device of embodiment of the present invention, identity code and condition code are being sent to service
Before the step of end, can also include：Client obtain current user name and/or wearable device current location data (such as：
The client that current user name logs in obtains the identity code of wearable device, the condition code of current mobile terminal, current use simultaneously
Name in an account book and/or wearable device current location data).It is recorded according to the binding relationship that identity code inquiry locally prestores in server-side
Before the step of table, can also include：Server-side receives the current user name and/or wearable device present bit that client is sent
Set data (such as：The client that current user name logs in sends the identity code of wearable device, current movement to server-side simultaneously
The condition code of terminal sends current user name and/or wearable device current location data).Server-side is to the user of binding
After the client that name logs in sends out the step of abnormity prompt notice, can also include：The client logged in the user name of binding
Termination receive that user sends out it is stolen recover instruction after, send out acquisition information request to server-side；Server-side receives acquisition letter
After breath request, current user name and/or wearable device current location number are sent to the client logged in the user name of binding
According to.The method of the management wearable device of the embodiment can after wearable device is stolen, using current user name and/or
Wearable device current location data recovers stolen wearable device.
According to the method for the management wearable device of embodiment of the present invention, server-side with the user name of binding to being logged in
After client sends out the step of abnormity prompt notice, can also include：It is received and is used with the client that the user name of binding logs in
After the instruction of binding again that family is sent out, bind request again is sent out to server-side；It, will after server-side receives bind request again
The condition code of the corresponding binding mobile terminal of device flag code is revised as the feature of current mobile terminal in binding relationship record sheet
Code.The method of the management wearable device of the embodiment may be implemented to bind wearable device and new mobile terminal
Function.
To make those skilled in the art more fully understand present disclosure, retouched in detail with reference to specific embodiment work
It states.
One of concrete application scene：It attempts to recover after wearable device is stolen.
Assuming that the phone number 13900000000 of the entitled owner of the user of owner, the mark for the wearable device that owner possesses
Will code is X, and the condition code for the mobile terminal that owner uses is IMEI1, and customer end A is mounted with above the mobile terminal.Assuming that small
The condition code of the phone number 13111111111 of the entitled thief of user steathily, the mobile terminal that thief uses is IMEI2, the shifting
Dynamic terminal is equipped with customer end B (customer end A is identical with customer end B essence, is simply installed on different mobile terminal).
First, owner utilizes " 13900000000 " to log in customer end A, and customer end A gets the identity code of wearable device
X, the condition code IMEI1 for the mobile terminal that owner uses.Then customer end A is by identity code X, user name 13900000000 and spy
Sign code IMEI1 sends jointly to server-side.By " X-13900000000-IMEI1 ", this binding record is stored in binding to server-side
In relation record table data.
Then, thief steals the wearable device of owner.Then mobile terminal of the thief wearable device and thief
It is connected, customer end B is then logged in user name " 13111111111 ".At this moment, customer end B is by the identity code X got, current
Login username 13111111111 and condition code IMEI2 send jointly to server-side.
Then, server-side inquires binding relationship record sheet data according to identity code X, obtains the condition code of binding mobile terminal
Should be IMEI1.Since server-side judges the spy of the condition code IMEI1 and the mobile terminal currently connecting of the mobile terminal of binding
Sign code IMEI2 is inconsistent, and then server-side sends out abnormity prompt to the customer end A logged in user bound name 13900000000
Notice.
Then, after customer end A receives abnormity prompt notice, " stolen recover " and " binding again " two is provided to owner
Option.In this application scene, user, which sends out to be stolen to customer end A, recovers instruction.Customer end A is stolen according to this and recovers instruction,
Acquisition information request is sent out to server-side.
Finally, server-side sends current user name 13111111111 according to information request is obtained to customer end A.In this way,
Owner can learn the phone number of thief, can further take steps to actively recover the wearable device of oneself.
It should be noted that in a preferred embodiment, currently logging in client (i.e. the corresponding customer end B of thief) can be with
Acquisition wearable device current location data uploads to server-side.And in server-side after receiving acquisition information request, also
Wearable device current location data is sent to the corresponding client of user bound name (i.e. the corresponding customer end A of owner).This
Sample can allow owner to be more favorably oriented and recover stolen equipment.
The two of concrete application scene：Wearable device is bound again with new mobile terminal.
Assuming that the phone number 13900000000 of the entitled owner of the user of owner, the mark for the wearable device that owner possesses
Will code is X.The condition code for the old mobile terminal that owner uses is IMEI1, and customer end A is mounted with above the mobile terminal.Owner
The condition code of the new mobile terminal used is IMEI3, and the mobile terminal is installed above client C (client C and customer end A
Essence is identical, is simply installed on different mobile terminal).
First, owner utilizes " 13900000000 " to log in customer end A, and customer end A gets the identity code of wearable device
X, the condition code IMEI1 for the old mobile terminal that owner uses.Then customer end A is by identity code X, 13900000000 and of user name
Condition code IMEI1 sends jointly to server-side." X-13900000000-IMEI1 " this binding record is stored in and ties up by server-side
Determine in relation record table data.
Then, owner has changed new mobile terminal.Owner is connected wearable device with new mobile terminal, then still with user
Name " 13900000000 " logs in client C.At this moment, client C is by the identity code X got, 13900000000 and of user name
Condition code IMEI3 sends jointly to server-side.
Then, server-side inquires binding relationship record sheet data according to identity code X, obtains the condition code of binding mobile terminal
Should be IMEI1.Since server-side judges the condition code IMEI1 of the old mobile terminal of binding and the new mobile terminal currently connecting
Condition code IMEI3 it is inconsistent, then server-side sends out abnormity prompt to the client C logged in user name 13900000000
Notice.
Then, after client C receives abnormity prompt notice, " stolen recover " and " binding again " two is provided to owner
Option.In this application scene, owner sends out binding instruction again to client C.Client C binds instruction according to this again,
Bind request again is sent out to server-side.
Finally, server-side is according to bind request again, by " X-13900000000- in binding relationship record sheet data
" IMEI1 " in IMEI1 " is revised as " IMEI3 ".So far, new binding relationship record is established.
Using the method for the management wearable device of present embodiment it can be seen from above-mentioned two concrete application scene
Afterwards, whether associated change can have occurred with the related information of mobile phone terminal that automatic decision wearable device is bound.It is changing
In the case of, system automatic will notify the relevant up-to-date information of original subscriber, the equipment for making user relatively easily give loss for change, or
Binding information is changed.
Fig. 2 is the schematic diagram according to the main modular of the server-side of the management wearable device of embodiment of the present invention.Such as
Shown in Fig. 2, the server-side 20 of the management wearable device of embodiment of the present invention includes：Receiving module 21, is sentenced enquiry module 22
Disconnected module 23 and sending module 24.
Receiving module 21 be used to receive the identity code of the wearable device that the client logged in current user name is sent with
The condition code of current mobile terminal, the current mobile terminal are connect with wearable device.
Enquiry module 22 is used to inquire the binding relationship record sheet locally to prestore according to identity code, to obtain tying up with identity code
The condition code of fixed user name and binding.Wherein binding relationship record sheet is used to record identity code, the user name of wearable device
And the binding relationship between the condition code three of mobile terminal.
Whether the condition code of condition code and binding of the judgment module 23 for judging current mobile terminal is identical.
Sending module 24 is used in the case where the judging result of judgment module is no, to what is logged in the user name of binding
Client sends out abnormity prompt notice.
According to the server-side of the management wearable device of embodiment of the present invention, receiving module can be also used for receiving client
Hold the current user name sent and/or wearable device current location data；Receive the acquisition information request that client is sent.And
And sending module can be additionally operable to send active user to the client logged in the user name of binding according to acquisition information request
Name and/or wearable device current location data.
Can also include again binding module according to the server-side of the management wearable device of embodiment of the present invention.It should
Receiving module in server-side is additionally operable to receive the bind request again that client is sent.Again binding module is used for according to again
The condition code of the corresponding binding mobile terminal of device flag code in binding relationship record sheet is revised as current movement by bind request
The condition code of terminal.
Fig. 3 is the schematic diagram according to the main modular of the client of the management wearable device of embodiment of the present invention.Such as
Shown in Fig. 2, the client 30 of the management wearable device of embodiment of the present invention includes：First acquisition module 31, first is sent
Module 32 and the first receiving module 33.
First acquisition module 31 is used to obtain the identity code of wearable device, and obtains and currently connect with wearable device
Current mobile terminal condition code.
First sending module 32 is used to identity code and condition code being sent to server-side.
First receiving module 33 is used to receive the abnormity prompt notice of server-side transmission.
Can also include that the first user interacts mould according to the client of the management wearable device of embodiment of the present invention
Block, the second acquisition module, the second sending module and the second receiving module (being not shown in Fig. 3).Wherein：First user interactive module
Stolen instruction is recovered for receive that user sends out.Second acquisition module is for obtaining current user name and/or wearable device
Current location data.Second sending module is used to send current user name and/or wearable device current location number to server-side
According to, and according to stolen recover instruction and send out acquisition information request to server-side.Second receiving module is for receiving server-side hair
The current user name and/or wearable device current location data sent.
Can also include second user interactive module according to the client of the management wearable device of embodiment of the present invention
It (is not shown in Fig. 3) with third sending module.Wherein：Second user interactive module refers to for receiving the binding again that user sends out
It enables.Third sending module, for sending out bind request again to server-side according to binding instruction again.
According to the server-side and client of the management wearable device of embodiment of the present invention, set with wearable by detecting
Whether whether the current mobile terminal of standby connection and history binding mobile terminal are identical, to judge wearable device using abnormal.
As long as such prompting logic wearable device is enabled by thief or other illegal identity persons and can be carried out judging, woth no need to
It asks the owner of wearable device instantaneously to make a response stolen, to which the user experience is improved, there is good reliability, safe coefficient
The advantages that high, intelligent.
Above-mentioned specific implementation mode, does not constitute limiting the scope of the invention.Those skilled in the art should be bright
It is white, design requirement and other factors are depended on, various modifications, combination, sub-portfolio and replacement can occur.It is any
Modifications, equivalent substitutions and improvements made by within the spirit and principles in the present invention etc., should be included in the scope of the present invention
Within.
Claims (9)
1. a kind of method of management wearable device, which is characterized in that including：
The identity code of wearable device is obtained with the client that current user name logs in, and is obtained and currently connected with wearable device
Then the identity code and described document information are sent to server-side by the condition code of the current mobile terminal connect；
The server-side inquires the binding relationship record sheet locally to prestore according to the identity code, to obtain tying up with the identity code
The condition code of fixed user name and binding, wherein the binding relationship record sheet is used to record the identity code of wearable device, uses
Binding relationship between name in an account book and the condition code three of mobile terminal；
The server-side judges whether the condition code of the current mobile terminal is identical as the condition code of the binding, if not phase
Together, the server-side sends out abnormity prompt notice to the client logged in the user name of binding.
2. the method for management wearable device according to claim 1, which is characterized in that
Before the described the step of identity code and described document information are sent to server-side, further include：The client obtains
The current user name and/or the wearable device current location data；
Before the step of server-side inquires the binding relationship record sheet locally to prestore according to the identity code, further include：Institute
It states server-side and receives the current user name and/or the wearable device current location data that the client is sent；
After the server-side sends out the step of abnormity prompt notifies to the client logged in the user name of binding, further include：
The client that the user name with binding logs in receive that user sends out it is stolen recover instruction after, sent out to the server-side
Obtain information request；After the server-side receives the acquisition information request, to the visitor of the user name login with binding
Family end sends the current user name and/or the wearable device current location data.
3. the method for management wearable device according to claim 1, which is characterized in that the server-side is to binding
After the client that user name logs in sends out the step of abnormity prompt notice, further include：
After the client that the user name with binding logs in receives the instruction of binding again that user sends out, sent out to the server-side
Go out bind request again；
It is after the server-side receives the bind request again, device flag code described in the binding relationship record sheet is right
The condition code for the binding mobile terminal answered is revised as the condition code of current mobile terminal.
4. it is a kind of management wearable device server-side, which is characterized in that including receiving module, enquiry module, judgment module and
Sending module, wherein：
The receiving module is used to receive the identity code for the wearable device that the client logged in current user name is sent and works as
The condition code of preceding mobile terminal, the current mobile terminal are connect with the wearable device；
The enquiry module is used to inquire the binding relationship record sheet locally to prestore according to the identity code, to obtain and the mark
The condition code of the user name and binding of the binding of will code, wherein the binding relationship record sheet is used to record the mark of wearable device
Binding relationship between the condition code three of code, user name and mobile terminal；
The judgment module is for judging whether the condition code of the current mobile terminal is identical as the condition code of the binding；
The sending module is used in the case where the judging result of the judgment module is no, to the user name login with binding
Client send out abnormity prompt notice.
5. the server-side of management wearable device according to claim 4, which is characterized in that
The receiving module is additionally operable to receive the current user name of the client transmission and/or the wearable device is worked as
Front position data；Receive the acquisition information request that client is sent；
The sending module is additionally operable to be sent out according to the client that the acquisition information request is logged in the user name with binding
Send the current user name and/or the wearable device current location data.
6. the server-side of management wearable device according to claim 5, which is characterized in that further include binding mould again
Block,
The receiving module is additionally operable to receive the bind request again that client is sent；
Again the binding module is used for according to again bind request by equipment mark described in the binding relationship record sheet
The condition code of the corresponding binding mobile terminal of will code is revised as the condition code of current mobile terminal.
7. a kind of client of management wearable device, which is characterized in that including the first acquisition module, the first sending module and the
One receiving module, wherein：
First acquisition module is used to obtain the identity code of wearable device, and obtains and currently connect with wearable device
The condition code of current mobile terminal；
First sending module is used to the identity code and described document information being sent to server-side；
First receiving module is used to receive the abnormity prompt notice that the server-side is sent.
8. the client of management wearable device according to claim 7, which is characterized in that further include the first user interaction
Module, the second acquisition module, the second sending module and the second receiving module, wherein：
First user interactive module is used to receive that user to send out stolen recovers instruction；
Second acquisition module is for obtaining the current user name and/or the wearable device current location data；
Second sending module is used to send the current user name and/or wearable device current location number to server-side
According to, and according to described stolen recover instruction and send out acquisition information request to the server-side；
Second receiving module is used to receive the current user name and/or wearable device current location number that the server-side is sent
According to.
9. the client of management wearable device according to claim 8, which is characterized in that further include second user interaction
Module and third sending module, wherein：
Second user interactive module is used to receive the instruction of binding again that user sends out；
Third sending module is used to bind instruction again according to sends out bind request again to the server-side.
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 true CN108377563A (en) | 2018-08-07 |
| CN108377563B 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) |
Cited By (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 |
Cited By (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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108377563B (en) | 2021-08-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101242404B (en) | A validation method and system based on heterogeneous network | |
| CN101582927B (en) | Server, movable terminal and method used for information backup and restoration | |
| CN104618622A (en) | Method and system for binding user account and image forming device by mobile terminal | |
| CN105025490A (en) | Method and device for identifying pseudo base station | |
| CN107113613B (en) | Server, mobile terminal, network real-name authentication system and method | |
| CN102970360B (en) | Browser client is logged in the system being controlled | |
| CN101155212A (en) | Method for limiting use of mobile terminal | |
| CN102724322A (en) | Remote control method and device | |
| CN103209247A (en) | Information display method and system, terminal and server | |
| CN102780989A (en) | Method and system for preventing loss of mobile terminal | |
| CN101155229A (en) | Distributed method and system for anti-fake and tracing product information | |
| CN102801781B (en) | Terminal, location-server and localization method | |
| CN108377563A (en) | Manage method, server-side and the client of wearable device | |
| US20170265233A1 (en) | Apparatus and method of connecting a mobile device to a field device | |
| CN104811927A (en) | Information processing method, terminal and server and communication method and system | |
| JP5380786B2 (en) | Network system | |
| CN104053137A (en) | Data recovery method and device | |
| WO2021099431A1 (en) | Method for authenticating a user on a network slice | |
| CN106211203A (en) | Lock network data updating method and device | |
| JP5465600B2 (en) | Support systems and methods | |
| US20100093331A1 (en) | System and method for configuring a communication device | |
| CN106412240A (en) | Incoming call bullet screen system and method of centralized management of enterprise communication | |
| CN103108316A (en) | Authentication method, device and system for aerial card writing | |
| CN108737112A (en) | A kind of system for the shield that Activates Phone | |
| CN101568090A (en) | Method, system and apparatus for accessing communication features |
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 |