CN105635142A - Account association relation establishment method and server - Google Patents
Account association relation establishment method and server Download PDFInfo
- Publication number
- CN105635142A CN105635142A CN201511018004.3A CN201511018004A CN105635142A CN 105635142 A CN105635142 A CN 105635142A CN 201511018004 A CN201511018004 A CN 201511018004A CN 105635142 A CN105635142 A CN 105635142A
- Authority
- CN
- China
- Prior art keywords
- account
- server
- relation
- request
- association relation
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 17
- 238000012795 verification Methods 0.000 claims abstract description 9
- 238000010586 diagram Methods 0.000 description 4
- 239000003814 drug Substances 0.000 description 4
- 230000036772 blood pressure Effects 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 238000005538 encapsulation Methods 0.000 description 2
- 238000000605 extraction Methods 0.000 description 2
- 239000011521 glass Substances 0.000 description 2
- 239000003550 marker Substances 0.000 description 2
- 238000004321 preservation Methods 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
Landscapes
- Engineering & Computer Science (AREA)
- Power Engineering (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The invention discloses an account association relation establishment method and server. The method comprises the steps that the server receives a request for establishment of an association relation of a first account and a second account; the request at least includes the unique account identifier of the second account; verification is performed according to the unique account identifier in the request and a preset unique account identifier of the second account; and the association relation of the first account and the second account is established after passing of verification. According to the account association relation establishment method and server, the association relation between the accounts can be established through verification of the unique account identifier performed by the server so that establishment of the account association relation is facilitated, and the verification step and network resources can also be saved.
Description
Technical field
The present invention relates to the technical field of network account association, particularly relate to method and server that a kind of account association relation is set up.
Background technology
The foundation of common account association relation, need the request first sending " set up account with another account and associate relation " in an account to server, then server sends a checking code to the other side's account (another account aforementioned) of request association, after waiting that the other side's account confirms, again this confirmation is returned server, device to be serviced can be associated after receiving relation, do not obtain the other side confirm or server do not receive this confirmation before association relation cannot set up.
Summary of the invention
The main purpose of the present invention, for providing a kind of account method that association relation is set up, verifies, by server, the relation that can be associated, convenient and swift.
The present invention proposes the method that a kind of account association relation is set up, and comprises step:
Server receives the first account and is associated with the 2nd account the request of relation; The account at least comprising described 2nd account in described request uniquely identifies;
Uniquely identify the account with the 2nd default account according to the account in request uniquely to identify and verify;
After being verified, that sets up the first account and the 2nd account associates relation.
Preferably, also comprise after the described step setting up the first account and the relation that associates of the 2nd account:
Relevant data in first account and the 2nd account are shared each other, and/or changes setting each other.
Preferably, described relevant data at least comprise health data and/or positional information.
Preferably, described server receive the first account be associated with the 2nd account relation request step before also comprise:
Server receives the hardware identifier code of the Wearable that the 2nd account is bound, and the account being set to the 2nd account uniquely identifies.
The present invention also proposes the server that a kind of account association relation is set up, and comprising:
Request reception unit, is associated with the 2nd account the request of relation for receiving the first account; The account at least comprising described 2nd account in described request uniquely identifies;
Requests verification unit, uniquely identifies verify for uniquely identifying the account with the 2nd default account according to the account in request;
Unit is set up in association, and for after being verified, that sets up the first account and the 2nd account associates relation.
Preferably, described server also comprises:
Data sharing unit, for the relevant data in the first account and the 2nd account being shared each other, and/or changes setting each other.
Preferably, described relevant data at least comprise health data and/or positional information.
Preferably, described server also comprises:
Mark setting unit, for receiving the hardware identifier code of the Wearable that the 2nd account is bound, the account being set to the 2nd account uniquely identifies.
The method that the account association relation of the present invention is set up and server, checking account uniquely identified by server, the association relation between account can be set up, associate the offering convenience property of foundation of relation to account, also save step and the network resource of checking.
Accompanying drawing explanation
Fig. 1 is the steps flow chart schematic diagram of the method that account association relation is set up in one embodiment of the invention;
Fig. 2 is the steps flow chart schematic diagram of the method that account association relation is set up in another embodiment of the present invention;
Fig. 3 is the high-level schematic functional block diagram of the server that account association relation is set up in one embodiment of the invention;
Fig. 4 is the high-level schematic functional block diagram of the server that account association relation is set up in another embodiment of the present invention.
The realization of the object of the invention, functional characteristics and advantage will in conjunction with the embodiments, are described further with reference to accompanying drawing.
Embodiment
It is to be understood that specific embodiment described herein is only in order to explain the present invention, it is not intended to limit the present invention.
With reference to Fig. 1, proposing the method that a kind of account association relation is set up in one embodiment of the invention, it can comprise:
Step S11, server receive the first account and are associated with the 2nd account the request of relation; The account at least comprising described 2nd account in described request uniquely identifies;
Step S12, uniquely identify the account with the 2nd default account according to the account in request and uniquely identify and verify;
Step S13, after being verified, that sets up the first account and the 2nd account associates relation.
In the present embodiment, need to pre-set in the server with account one to one account uniquely identify, form the synopsis that account and account uniquely identify and be stored in server. When the first account needs to be associated relation with the 2nd account, the account that first this first account needs to obtain the 2nd account uniquely identifies. After the account getting the 2nd account uniquely identifies, this first account can send the request of the relation of being associated to server, and the account at least comprising described 2nd account in this request uniquely identifies.
Above-mentioned server is after the request receiving above-mentioned first account, first by unique for the account in above-mentioned request marker extraction out, and account corresponding to the 2nd account that need to extract preservation from synopsis uniquely identifies, then both are compared, judge whether both are consistent, if the request that unanimously can be verified this first account, the first account is associated relation with the 2nd account; If both are inconsistent can refuse the request by this first account, both are associated relation unsuccessfully.
With reference to Fig. 2, in an alternative embodiment of the invention, also can comprise before above-mentioned steps S11:
Step S10, server receive the hardware identifier code of the Wearable that the 2nd account is bound, and the account being set to the 2nd account uniquely identifies.
In the present embodiment, above-mentioned first account and the 2nd account can be the Wearable of a respectively corresponding intelligence, and it can be the hardware identifier code of this Wearable that the account of the 2nd account uniquely identifies. After human consumer buys this Wearable, first register to server; This server gets the hardware identifier code of this Wearable, and sets up account for this Wearable and uniquely identified as the account of the account by this hardware identifier code and be stored in synopsis. This Wearable can comprise intelligent watch, Intelligent bracelet and/or intelligent glasses etc. In practical application, this hardware identifier code can also be unique designated code of Wearable factory settings.
With reference to Fig. 2, in an alternative embodiment of the invention, also can comprise after above-mentioned steps S13:
Step S14, the relevant data in the first account and the 2nd account are shared each other, and/or change setting each other; These relevant data at least comprise health data and/or positional information etc. This arranges and can comprise prompting and arrange, and such as arranges integral point and reminds, takes medicine prompting and/or prompting etc. of seeking help.
In the present embodiment, after above-mentioned first account sets up, with the 2nd account, the relation of association, some data in account each other can be shared to the other side by above-mentioned server, can check the relevant data that the other side's account is shared in interlock account at any time. Wherein, these relevant data can be the health data and/or positional information etc. that the other side's account monitors.
Such as, in the present embodiment, corresponding with above-mentioned first account and the 2nd account hardware device is the first intelligent watch and the 2nd intelligent watch respectively; The user of the first intelligent watch is the relatives of the 2nd intelligent watch user, and the user of the 2nd intelligent watch is old man.
, it is necessary to above-mentioned first intelligent watch and the 2nd intelligent watch are registered on the server respectively, first the first account and the 2nd account is obtained respectively. If this first account needs to understand the dynamically current of the 2nd account, such as certain physiological parameter (blood pressure, heartbeat etc., i.e. health data) or current location information etc., its relation that must be associated with the 2nd account. It uniquely identifies (i.e. the hardware identifier of the 2nd intelligent watch) by obtaining the account of the 2nd account, and the account uniquely identifies encapsulation and is sent to server in the request, is associated with the 2nd account relation to server request. After server receives this request, the account that can extract the 2nd account from request uniquely identifies, and uniquely identifies with the account of the 2nd account in synopsis and compare; When two accounts uniquely identify consistent, two accounts are associated relation; Otherwise association relation is set up unsuccessfully. So, the participation of the 2nd account in association relation is set up can be reduced, to user (old man) the offering convenience property of the 2nd account.
After the first account is set up with the relation that associates of the 2nd account, the current health data of user (old man) and the positional information that can be monitored due to the 2nd intelligent watch are stored in the 2nd account, and the user (relatives) of the first account (i.e. the first intelligent watch) also can view above-mentioned health data and positional information at any time in the first account; And according to specific needs, these relatives are also that old man changes setting in the 2nd account in the first account, such as add integral point and remind, take medicine and remind and prompting etc. of seeking help; So strengthen relatives to the treatment of old man and protection.
With reference to Fig. 3, one embodiment of the invention proposes the server that a kind of account association relation is set up. It can comprise: unit 23 is set up in request reception unit 21, requests verification unit 22 and association; This request reception unit 21, is associated with the 2nd account the request of relation for receiving the first account; The account at least comprising described 2nd account in described request uniquely identifies; This requests verification unit 22, uniquely identifies verify for uniquely identifying the account with the 2nd default account according to the account in request; Unit 23 is set up in this association, and for after being verified, that sets up the first account and the 2nd account associates relation.
In the present embodiment, need to pre-set in the server with account one to one account uniquely identify, form the synopsis that account and account uniquely identify and be stored in server. When the first account needs to be associated relation with the 2nd account, the account that first this first account needs to obtain the 2nd account uniquely identifies. After the account getting the 2nd account uniquely identifies, this first account can send the request of the relation of being associated to server, and the account at least comprising described 2nd account in this request uniquely identifies.
Above-mentioned server is after the request being received above-mentioned first account by request reception unit 21, first utilize requests verification unit 22 by unique for the account in above-mentioned request marker extraction out, and account corresponding to the 2nd account that need to extract preservation from synopsis uniquely identifies, then both are compared, judge whether both are consistent, if the request that unanimously can be verified this first account, utilize association to set up unit 23 and first account is associated with the 2nd account relation; If both are inconsistent can refuse the request by this first account, both are associated relation unsuccessfully.
With reference to Fig. 4, in an alternative embodiment of the invention, above-mentioned server also comprises: mark setting unit 20, for receiving the hardware identifier code of the Wearable that the 2nd account is bound, the account being set to the 2nd account uniquely identifies.
In the present embodiment, above-mentioned first account and the 2nd account can be the Wearable of a respectively corresponding intelligence, and it can be the hardware identifier code of this Wearable that the account of the 2nd account uniquely identifies. After human consumer buys this Wearable, first register to server; This server gets the hardware identifier code of this Wearable by mark setting unit 20, and sets up account for this Wearable and uniquely identified as the account of the account by this hardware identifier code and be stored in synopsis. This Wearable can comprise intelligent watch, Intelligent bracelet and/or intelligent glasses etc. In practical application, this hardware identifier code can also be unique designated code of Wearable factory settings.
With reference to Fig. 4, in an alternative embodiment of the invention, above-mentioned server also comprises: data sharing unit 24, for the relevant data in the first account and the 2nd account being shared each other. These relevant data at least can comprise health data and/or positional information etc. This arranges and can comprise prompting and arrange, and such as arranges integral point and reminds, takes medicine prompting and/or prompting etc. of seeking help.
In the present embodiment, after above-mentioned first account sets up, with the 2nd account, the relation of association, some data in account each other can be shared to the other side by the data sharing unit 24 in above-mentioned server, can check the relevant data that the other side's account is shared in interlock account at any time. Wherein, these relevant data can be the health data and/or positional information etc. that the other side's account monitors.
Such as, in the present embodiment, corresponding with above-mentioned first account and the 2nd account hardware device is the first intelligent watch and the 2nd intelligent watch respectively; The user of the first intelligent watch is the relatives of the 2nd intelligent watch user, and the user of the 2nd intelligent watch is old man.
, it is necessary to above-mentioned first intelligent watch and the 2nd intelligent watch are registered on the server respectively, first the first account and the 2nd account is obtained respectively. If this first account needs to understand the dynamically current of the 2nd account, such as certain physiological parameter (blood pressure, heartbeat etc., i.e. health data) or current location information etc., its relation that must be associated with the 2nd account. It uniquely identifies (i.e. the hardware identifier of the 2nd intelligent watch) by obtaining the account of the 2nd account, and the account uniquely identifies encapsulation and is sent to server in the request, is associated with the 2nd account relation to server request. After server receives this request, the account that can extract the 2nd account from request uniquely identifies, and uniquely identifies with the account of the 2nd account in synopsis and compare; When two accounts uniquely identify consistent, two accounts are associated relation; Otherwise association relation is set up unsuccessfully. So, the participation of the 2nd account in association relation is set up can be reduced, to user (old man) the offering convenience property of the 2nd account.
After the first account is set up with the relation that associates of the 2nd account, the current health data of user (old man) and the positional information that can be monitored due to the 2nd intelligent watch are stored in the 2nd account, and the user (relatives) of the first account (i.e. the first intelligent watch) also can view above-mentioned health data and positional information at any time in the first account; And according to specific needs, these relatives are also that old man changes setting in the 2nd account in the first account, such as add integral point and remind, take medicine and remind and prompting etc. of seeking help; So strengthen relatives to the treatment of old man and protection.
The foregoing is only the preferred embodiments of the present invention; not thereby the patent scope of the present invention is limited; every utilize specification sheets of the present invention and accompanying drawing content to do equivalent structure or equivalence flow process conversion; or directly or indirectly it is used in other relevant technical fields, all it is included in the scope of patent protection of the present invention with reason.
Claims (8)
1. the method that an account association relation is set up, it is characterised in that, comprise step:
Server receives the first account and is associated with the 2nd account the request of relation; The account at least comprising described 2nd account in described request uniquely identifies;
Uniquely identify the account with the 2nd default account according to the account in request uniquely to identify and verify;
After being verified, that sets up the first account and the 2nd account associates relation.
2. the method that account according to claim 1 association relation is set up, it is characterised in that, also comprise after the described step setting up the first account and the relation that associates of the 2nd account:
Relevant data in first account and the 2nd account are shared each other, and/or changes setting each other.
3. the method that account according to claim 2 association relation is set up, it is characterised in that, described relevant data at least comprise health data and/or positional information.
4. account according to any one of claim 1 to 3 association relation set up method, it is characterised in that, described server receive the first account be associated with the 2nd account relation request step before also comprise:
Server receives the hardware identifier code of the Wearable that the 2nd account is bound, and the account being set to the 2nd account uniquely identifies.
5. the server that an account association relation is set up, it is characterised in that, comprising:
Request reception unit, is associated with the 2nd account the request of relation for receiving the first account; The account at least comprising described 2nd account in described request uniquely identifies;
Requests verification unit, uniquely identifies verify for uniquely identifying the account with the 2nd default account according to the account in request;
Unit is set up in association, and for after being verified, that sets up the first account and the 2nd account associates relation.
6. the server that account according to claim 5 association relation is set up, it is characterised in that, described server also comprises:
Data sharing unit, for the relevant data in the first account and the 2nd account being shared each other, and/or changes setting each other.
7. the server that account according to claim 6 association relation is set up, it is characterised in that, described relevant data at least comprise health data and/or positional information.
8. according to any one of claim 5 to 7 account association relation set up server, it is characterised in that, described server also comprises:
Mark setting unit, for receiving the hardware identifier code of the Wearable that the 2nd account is bound, the account being set to the 2nd account uniquely identifies.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511018004.3A CN105635142A (en) | 2015-12-29 | 2015-12-29 | Account association relation establishment method and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511018004.3A CN105635142A (en) | 2015-12-29 | 2015-12-29 | Account association relation establishment method and server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105635142A true CN105635142A (en) | 2016-06-01 |
Family
ID=56049632
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201511018004.3A Withdrawn CN105635142A (en) | 2015-12-29 | 2015-12-29 | Account association relation establishment method and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105635142A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106973443A (en) * | 2017-03-31 | 2017-07-21 | 北京小米移动软件有限公司 | Equipment correlating method, equipment associated apparatus and electronic equipment |
| CN108022629A (en) * | 2017-12-01 | 2018-05-11 | 湖南暄程科技有限公司 | A kind of health account correlating method and system |
| CN110555687A (en) * | 2019-07-26 | 2019-12-10 | 上海泛标商务咨询有限公司 | method, server and user side for associating transaction account |
| CN112087409A (en) * | 2019-06-12 | 2020-12-15 | 腾讯科技（深圳）有限公司 | Account correlation method, terminal and server |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102868696A (en) * | 2012-09-18 | 2013-01-09 | 广州市动景计算机科技有限公司 | Method and system for communication and information synchronization among equipments |
| CN103281192A (en) * | 2013-05-31 | 2013-09-04 | 腾讯科技（深圳）有限公司 | Method, device and system for retrieving data |
| CN103347306A (en) * | 2013-06-24 | 2013-10-09 | 腾讯科技（深圳）有限公司 | Method, system and device for establishing correlation among multiple terminals |
| CN103616860A (en) * | 2013-11-08 | 2014-03-05 | 海信集团有限公司 | Method and device for remote control of household appliances |
| CN104796385A (en) * | 2014-01-20 | 2015-07-22 | 腾讯科技（深圳）有限公司 | Terminal binding method, device and system |
-
2015
- 2015-12-29 CN CN201511018004.3A patent/CN105635142A/en not_active Withdrawn
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102868696A (en) * | 2012-09-18 | 2013-01-09 | 广州市动景计算机科技有限公司 | Method and system for communication and information synchronization among equipments |
| CN103281192A (en) * | 2013-05-31 | 2013-09-04 | 腾讯科技（深圳）有限公司 | Method, device and system for retrieving data |
| CN103347306A (en) * | 2013-06-24 | 2013-10-09 | 腾讯科技（深圳）有限公司 | Method, system and device for establishing correlation among multiple terminals |
| CN103616860A (en) * | 2013-11-08 | 2014-03-05 | 海信集团有限公司 | Method and device for remote control of household appliances |
| CN104796385A (en) * | 2014-01-20 | 2015-07-22 | 腾讯科技（深圳）有限公司 | Terminal binding method, device and system |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106973443A (en) * | 2017-03-31 | 2017-07-21 | 北京小米移动软件有限公司 | Equipment correlating method, equipment associated apparatus and electronic equipment |
| CN108022629A (en) * | 2017-12-01 | 2018-05-11 | 湖南暄程科技有限公司 | A kind of health account correlating method and system |
| CN112087409A (en) * | 2019-06-12 | 2020-12-15 | 腾讯科技（深圳）有限公司 | Account correlation method, terminal and server |
| CN112087409B (en) * | 2019-06-12 | 2021-12-14 | 腾讯科技（深圳）有限公司 | Account correlation method, terminal and server |
| CN110555687A (en) * | 2019-07-26 | 2019-12-10 | 上海泛标商务咨询有限公司 | method, server and user side for associating transaction account |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107087033B (en) | Message pushing method and device, storage medium and computer equipment | |
| US9338628B2 (en) | Emergency notification system | |
| CN101926675B (en) | Method, device and system for remotely acquiring physical detection data of user | |
| CN105635142A (en) | Account association relation establishment method and server | |
| CN110913000A (en) | Method, system and computer readable storage medium for processing service information | |
| EP4376495A3 (en) | Method and apparatus for session management function selection | |
| CN104966346A (en) | User terminal, visit prompting method on basis thereof and network hospital platform | |
| CN104965977A (en) | Treatment prompting method based on network treatment platform and network hospital platform | |
| US20200388390A1 (en) | Digital health proxy system and device | |
| CN103886529A (en) | Health archive information management service system and method | |
| TWI507890B (en) | Pushlet instant messaging method and platform | |
| RU2015129549A (en) | COMBINING DEFIBRILLATOR DATA WITH PATIENT MONITOR | |
| RU2012132396A (en) | METHOD AND DEVICE FOR DETERMINING A COMMUNICATION PURPOSE AND ASSISTING COMMUNICATIONS BASED ON THE OBJECT DESCRIPTOR | |
| CN107211259A (en) | Apparatus and method for improving personal information Information Security | |
| CN103870704A (en) | Health service system and physiological parameter detecting device based on multi-user identity recognition | |
| CN105096226A (en) | Method for realizing multi-party consultation, hospital server, user terminal and system | |
| CN104580380B (en) | The synchronous method and system of logging state | |
| CN103488779A (en) | Doctor-patient prime index system and doctor-patient prime index platform | |
| CN104899428A (en) | Online hospital platform, expert platform and expert consultation request method | |
| KR102005338B1 (en) | Location based social networking system and method | |
| CN103473722B (en) | A kind of doctor-patient dispute early warning system | |
| CN110691350B (en) | Transmission device and non-transitory computer-readable storage medium for transmitting emergency resource scheduling related information | |
| CN117527338A (en) | Bidirectional identity enhanced identification method and system in Internet of things application | |
| CN105099738B (en) | Data capture method, apparatus and system | |
| KR20130108874A (en) | Method and apparatus for providing improved notification services for smart terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20190114 Address after: 518000 Building 405A, 01B, Zone E, Zhiheng Industrial Park, Nantou Street, Nanshan District, Shenzhen City, Guangdong Province Applicant after: SHENZHEN ZHIYING TECHNOLOGY Co.,Ltd. Address before: 518000 Meilong Road and Minwang Road, Minzhi Street, Longhua New District, Shenzhen City, Guangdong Province Applicant before: SHENZHEN RUIMING UNLIMITED TECHNOLOGY Co.,Ltd. |
|
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20160601 |