CN101360111A - Customer managing method, apparatus and system - Google Patents
Customer managing method, apparatus and system Download PDFInfo
- Publication number
- CN101360111A CN101360111A CNA2008101986652A CN200810198665A CN101360111A CN 101360111 A CN101360111 A CN 101360111A CN A2008101986652 A CNA2008101986652 A CN A2008101986652A CN 200810198665 A CN200810198665 A CN 200810198665A CN 101360111 A CN101360111 A CN 101360111A
- Authority
- CN
- China
- Prior art keywords
- account
- information
- node
- user name
- client node
- 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.)
- Pending
Links
Images
Abstract
The invention discloses a user management system, comprising a customer node, a center node and a backup node; correspondingly, the invention also discloses a user account registration method, a user account information modifying method and a user management device. The embodiments of the invention can be implemented to improve the stability of the user management system and reduce high dependence on a dedicated server.
Description
Technical field
The present invention relates to the communications field, relate in particular to user management method, equipment and system.
Background technology
Existing Subscriber Management System is usually based on the model of client/service end; the user is by client login service end registering account and revise account's relevant information; service end need use the server of a special use to finish the work such as adding, delete, change, look into of user management usually; account information is also left concentratedly on this private server, and there is following defective in it:
1. need special-purpose server to finish establishment, modification, inquiry and the deletion action of user account, consume the resource of operator;
2. account information need leave on the special-purpose server, also needs to take a large amount of specific resources;
3. existing this Subscriber Management System is to private server dependence height, when this private server breaks down or during job insecurity, can greatly have influence on the performance or the stability of whole Subscriber Management System.
Summary of the invention
The problem to be solved in the present invention is to provide a kind of user management method, equipment and system, improves the stability of Subscriber Management System, and the height that reduces private server relies on.
For addressing the above problem, the invention provides a kind of user account register method, comprising:
Client node generates the registration information that comprises the designated user name;
Described client node is selected service node and is submitted to described registration information to register the account of described user name to it according to the cryptographic Hash of described user name.
The present invention also provides a kind of user account information amending method, comprising:
Client node generates the landing request information that comprises the registering account user name;
Described client node is selected service node and is submitted to described landing request information to revise the information of described account to login described service node to it according to the cryptographic Hash of described user name.
Accordingly, the present invention also provides a kind of client node equipment, comprising:
The registration generation module is used to generate the registration information that comprises the designated user name;
The login generation module is used to generate the landing request information that comprises the registering account user name;
The services selection module is used for extracting user name and selecting to provide the service node of service according to the cryptographic Hash of described user name from described registration information or landing request information.
Corresponding the present invention also provides a kind of central node equipment, comprising:
User registration module is used to receive the registration information that comprises the designated user name from client node equipment;
Authentication module is used for verifying the account who whether has had described user name according to described registration information;
Respond module is used for returning the already present information of user name to described client node equipment when described authentication module verifies that the account of described user name has existed;
Creation module is used for when described authentication module verifies that the account of described user name does not exist the account who creates described user name;
The account information synchronization module, account's the information synchronization that is used for described user name that described creation module is created is to backup node equipment.
The present invention also provides a kind of backup node equipment, comprising:
The account information synchronization module is used for receiving accounts information from central node equipment;
User log-in block is used to receive from the landing request information that comprises the registering account user name of client node equipment and confirms the login of client node equipment;
Sending module is used for after described user log-in block is confirmed the login of client node equipment the information of described registering account is sent to described client node equipment;
Receiver module, be used to receive the information of the registering account after the described client node apparatus modifications, and information that will this amended login account passes to described accounts information synchronization module, by the account information synchronization module with the information synchronization of described amended login account to central node equipment.
In addition, the present invention also provides a kind of Subscriber Management System, comprises client node, Centroid and backup node, wherein:
Described client node is used to generate the registration information that comprises the designated user name and comprises the landing request information of specifying the registering account user name, selects suitable service node to provide user account registration and account information to revise service according to the cryptographic Hash of described user name;
Described Centroid is used for when online as provide user account registration and account information to revise the service node of service for described client node;
The accounts information that described backup node is used for the described client node registration of back-up storage or revises, and when described Centroid is not online, revise service for described client node provides user account information temporarily.
Implement the embodiment of the invention and have following beneficial effect:
Client node can select different service nodes to provide subscriber management service for the user by the cryptographic Hash of user name, has improved the stability of Subscriber Management System, and the height that has reduced private server relies on.
Description of drawings
The structural representation of a kind of Subscriber Management System that Fig. 1 provides for the embodiment of the invention;
The structural representation of a kind of client node equipment that Fig. 2 provides for the embodiment of the invention;
The structural representation of a kind of central node equipment that Fig. 3 provides for the embodiment of the invention;
The structural representation of a kind of backup node equipment that Fig. 4 provides for the embodiment of the invention;
The schematic flow sheet of a kind of user registering method that Fig. 5 provides for the embodiment of the invention;
Fig. 6 is the schematic flow sheet of the embodiment of step S51 among Fig. 5;
The schematic flow sheet of a kind of user's modification method that Fig. 7 provides for the embodiment of the invention;
Fig. 8 is the schematic flow sheet of the embodiment of step S71 among Fig. 7;
Fig. 9 is the schematic flow sheet of another embodiment of step S71 among Fig. 7.
Embodiment
Below in conjunction with accompanying drawing the embodiment of the invention is introduced in further detail.
Subscriber Management System in the embodiment of the invention is based on the peer-to-peer network structure, peer-to-peer network uses the DHT algorithm organization, each node has a unique ID, and the Centroid that the embodiment of the invention relates to, backup node and client node all are the nodes in the peer-to-peer network.
The structural representation of a kind of Subscriber Management System that Fig. 1 provides for the embodiment of the invention, this Subscriber Management System comprises client node 10, the Centroid 11 that links to each other with this client node 10, and at least one backup node ( backup node 12,13,14 here for convenience of description only draws).
Described client node 10 is used to generate the registration information that comprises the designated user name and comprises the landing request information of specifying the registering account user name, selects suitable service node to provide user account registration service and user account information to revise service according to the cryptographic Hash of described user name.
Described Centroid 11 is used for as provide user account registration service and user account information to revise the service node of service for client node 10 when online.Detailed process can be: described Centroid 11 receives the registration information of client node 10, whether the account who verifies described user name according to described registration information exists, the account who when described user's account does not exist, creates described user name, with described account's information synchronization to all backup nodes.In addition, the login that described Centroid 11 also is used to receive the landing request information of client node 10 and confirms client node, with the information synchronization of described registering account to client node, receive the information of the amended described registering account of client node, and the information synchronization of the described registering account after will upgrading is to backup node 12,13,14.
Described backup node 12,13,14 accounts informations that are used for the described client node registration of back-up storage or revise, and when the center node is not online, for providing user account information, described client node revises service temporarily, client node 10 has selected backup node 12 to provide user account information to revise service when supposing here that Centroid 11 is not online, backup node 12 receives the described landing request information of client node 10 and confirms the login of client node, with the information synchronization of described registering account to client node 10, receive the information of client node 10 amended described registering accounts, and the information synchronization of the described registering account after will upgrading to Centroid 11 by its with the information synchronization of amended described registering account to backup node 13,14.
The Subscriber Management System that the embodiment of the invention provides, client node selects Centroid to provide registration service for oneself by the cryptographic Hash of the account user name that will register, Centroid is when making that with account information stores synchronized to a plurality of backup nodes client node is revised account information, both can login Centroid revises, also can login backup node revises, make stability, the availability of system improve, reduced that simultaneously the height to private server in the existing Subscriber Management System is relied on.
As shown in Figure 2, the structural representation of a kind of client node equipment that provides for the embodiment of the invention, described client node equipment comprise registration generation module 101, login generation module 102, services selection module 103, receiver module 104, modified module 105 and sending module 106.
Modified module 105 is used to revise the information of the described registering account that described accounts information receiver module receives and preserves;
As shown in Figure 3, the structural representation of a kind of central node equipment that provides for the embodiment of the invention, Centroid 11 complete for the user provides the user to register and revises service, when the center node provides the user registration service for the user, described central node equipment comprises:
Respond module 113 is used for returning the already present information of user name to described client node equipment when the account of the described user name of authentication module 112 checkings has existed;
Account information synchronization module 115, the information synchronization that is used for described account that creation module 114 is created is to backup node equipment ( backup node 12,13,14).
When the center node provides the user's modification service for the user, it also comprises:
User log-in block 116 is used for receiving from the landing request information that comprises the registering account user name of client node equipment (client node 10) and confirms the login of client node equipment;
Sending module 117 is used for after user log-in block 116 is confirmed the login of client node equipment the information of described registering account is sent to described client node equipment;
This moment, account information synchronization module 115 also was used for amended described account's that receiver module 118 is received information synchronization to backup node equipment ( backup node 12,13,14).
As shown in Figure 4, the structural representation of a kind of backup node equipment that provides for the embodiment of the invention, described backup node equipment comprises account information synchronization module 121, is used for receiving accounts information and storage from central node equipment, to realize the function of backup node back-up storage; User log-in block 122 is used for receiving from the landing request information that comprises the registering account user name of client node equipment (client node 10) and confirms the login of client node equipment; Sending module 123 is used for after user log-in block 122 is confirmed the login of client node equipment the information of described registering account is sent to described client node equipment; Receiver module 124 is used to receive the information of the described registering account after the described client node apparatus modifications.Described account information synchronization module 121 also is used for amended described account's that described receiver module is received information synchronization to central node equipment (Centroid 11).
Be illustrated in figure 5 as the schematic flow sheet of a kind of user account register method that the embodiment of the invention provides, it may further comprise the steps:
S50: client node generates the registration information comprise the designated user name, and the client node request registration has the account of certain user name in registration information, such as the following account of client node request registration:
User name: Lion password: leo628
Certainly it is as follows such as some private data to fill in some other user profile registering account the time:
Sex: male star's seat: Aquarius mailbox: leo_003@163.com
It is to be noted that user profile is not limited to the above example of enumerating, other possible user profile repeat no more herein.
S51: client node is sought service node and is submitted to registration information to register the account of described user name to it according to the cryptographic Hash of described user name, and as shown in Figure 6, step S51 comprises:
S510: it is that the Centroid of user name cryptographic Hash is as service node that client node is selected the ID value, as the example among the step S50, client node is selected service node according to the cryptographic Hash of user name Lion, here, preferably, service node is the Centroid of ID=Hash (Lion);
S511: Centroid receives registration information;
S512: Centroid is verified the account who whether has had described user name according to described registration information, and whether the service node inspection has existed the account of user Lion by name;
S513: the result is for being then to return the already present information of user name in checking;
S514: the checking result is for denying, then create the account of described user name and with described account's information synchronization to backup node, backup node is several neighbor nodes of Centroid, there is not the account of user Lion by name in Centroid, then create the account and with accounts information synchronously to backup node;
Can be found by above-mentioned steps, be Centroid for the user provides the actual of service in user registration course.
In this user registering method embodiment, the cryptographic Hash of the user name of client node by wanting registering account selects Centroid that the user is provided registration service, Centroid again with account's the information synchronization of registration to backup node, so in follow-up user management, client node both can have been logined Centroid and obtain and revised the user profile of oneself, also can login backup node when Centroid is not online and obtain and revise the user profile of oneself.
As shown in Figure 7, the schematic flow sheet of a kind of user account information amending method that provides for the embodiment of the invention may further comprise the steps:
S70: client node generates the landing request information that comprises the registering account user name, connects the example among the above-mentioned embodiment, and client node has been registered the account of user Lion by name, and this step generates the landing request information that comprises user name Lion;
S71: client node is selected service node and is submitted to landing request information to revise the information of described login account to login described service node to it according to the cryptographic Hash of described user name, preferentially select Centroid as service node if Centroid is online, do not select one of them backup node as service node if Centroid is online, if select Centroid as service node, wherein Centroid is the node that ID equals described user name cryptographic Hash, backup node is several neighbor nodes of Centroid, as shown in Figure 8, step S71 comprises:
S710: the Centroid that client node selection ID value equals the user name cryptographic Hash is as service node, and client node is selected service node according to the cryptographic Hash of Lion, and the Centroid of selecting ID=Hash (Lion) is as service node;
S711: Centroid receives the login that described landing request information is confirmed described client node, and Centroid receives and confirms that client node is called account's login of Lion by the user;
S712: Centroid with the information synchronization of described registering account to client node this locality, Centroid with account's relevant information of user Lion by name synchronously to client node this locality;
S713: client node revises the information of described registering account and synchronously to Centroid, if client node has been revised password and mailbox, amended user profile is as follows:
User name: Lion password: Leo725 (modification)
Sex: male star's seat: Aquarius mailbox: leo_623@gmail.com (modification) client node then sends to Centroid with amended user profile, and Centroid upgrades password in the original stored user information and mailbox;
S714: Centroid with the information synchronization of amended described registering account to backup node, backup node is several neighbor nodes of Centroid, the relevant information after Centroid upgrades the account of user Lion by name synchronously to backup node to guarantee the uniqueness of accounts information.
If service node is a backup node, as shown in Figure 9, step S71 comprises:
S7100: client node selects the backup node of Centroid as service node, and client node is selected a suitable backup node as service node from several backup nodes of Centroid;
S7101: backup node receives the login that described landing request information is confirmed described client node, and backup node receives and confirms that client node is called account's login of Lion by the user;
S7102: backup node with the information synchronization of described registering account to client node this locality, backup node with account's relevant information of user Lion by name synchronously to client node this locality;
S7103: client node revises the information of described registering account and synchronously to backup node, if client node has been revised password and mailbox, amended user profile is as follows:
User name: Lion password: Leo725 (modification)
Sex: male star's seat: Aquarius mailbox: leo_623@gmail.com (modification)
Client node sends to backup node with amended user profile then, and backup node upgrades password in the original stored user information and mailbox;
S7104: backup node with the information synchronization of amended described registering account to Centroid by its with the information synchronization of amended described registering account to other backup nodes, relevant information after backup node upgrades the account of user Lion by name is synchronously to Centroid, Centroid again with above-mentioned information synchronization to other backup nodes to guarantee the consistency of accounts information.
As seen from the above step S711-S713 and step S7101-S7103 comparing class seemingly, difference obviously is that the service node difference of client node login causes.
In the embodiment of user's modification method of the present invention, client node both can have been logined Centroid and revise user profile, also can when Centroid is not online, login backup node and revise user profile, improved the stability of user management, can not occur in legacy user's management system the height of certain private server is relied on.
It is to be noted that at last the foregoing description is the preferred embodiment of the present invention only, does equal conversion according to claim of the present invention, still belongs to protection range of the present invention.
Claims (12)
1, a kind of user account register method is characterized in that, comprising:
Client node generates the registration information that comprises the designated user name;
Described client node is selected service node and is submitted to described registration information to register the account of described user name to it according to the cryptographic Hash of described user name.
2, user account register method as claimed in claim 1 is characterized in that, described client node is selected service node and submitted to described registration information to comprise with the account's that registers described user name step to it according to the cryptographic Hash of described user name:
Described client node selects the ID value to equal the Centroid of described user name cryptographic Hash as service node;
Described Centroid receives described registration information;
Whether described Centroid has existed the account of described user name according to described registration information checking;
If the result is for being then to return the already present information of user name in checking;
If the checking result, then creates the account of described user name for not and with described account's information synchronization to backup node, described backup node is the neighbor node of described Centroid.
3, user account register method as claimed in claim 2 is characterized in that, described client node, service node and backup node are the node in the peer-to-peer network, and described account's information comprises user name, password and user profile.
4, a kind of user account information amending method is characterized in that, comprising:
Client node generates the landing request information that comprises the registering account user name;
Described client node is selected service node and is submitted to described landing request information to revise the information of described account to login described service node to it according to the cryptographic Hash of described user name.
5, user account information amending method as claimed in claim 4, it is characterized in that described client node is selected service node and submitted to described landing request information to revise the information of described account and comprise to login described service node to it according to the cryptographic Hash of described user name:
Described client node selects the ID value to equal the Centroid of described user name cryptographic Hash as service node;
Described service node receives the login that described landing request information is confirmed described client node;
Described service node with the information synchronization of described registering account to described client node this locality;
Described client node is revised the information and the synchronous extremely described service node of described registering account;
To backup node, described backup node is the neighbor node of described service node to described service node with the information synchronization of amended registering account.
6, user account information amending method as claimed in claim 4, it is characterized in that described client node is selected service node and submitted to described landing request information to revise the step of the information of described account and comprise to login described service node to it according to the cryptographic Hash of described user name:
Described client node selects the backup node of Centroid as service node, and described Centroid is the node that the ID value equals the cryptographic Hash of described user name, and described backup node is the neighbor node of the described account information of described Centroid back-up storage;
Described service node receives the login that described landing request information is confirmed described client node;
Described service node with the information synchronization of described registering account to described client node this locality;
Described client node is revised the information and the synchronous extremely described service node of described registering account;
Described service node with the information synchronization of amended registering account to described Centroid, by its with the information synchronization of amended registering account to other backup nodes.
7, a kind of client node equipment is characterized in that, comprising:
The registration generation module is used to generate the registration information that comprises the designated user name;
The login generation module is used to generate the landing request information that comprises the registering account user name;
The services selection module is used for extracting user name and selecting to provide the service node of service according to the cryptographic Hash of described user name from described registration information or landing request information.
8, client node equipment as claimed in claim 7 is characterized in that, also comprises:
Receiver module is used to receive the information of the described registering account that described service node sends;
Modified module is used to revise the information of the described registering account that described receiver module receives and preserves;
Sending module is used for the information of the amended registering account of described modified module is sent to described service node.
9, a kind of central node equipment is characterized in that, comprising:
User registration module is used to receive the registration information that comprises the designated user name from client node equipment;
Authentication module is used for verifying the account who whether has had described user name according to described registration information;
Respond module is used for returning the already present information of user name to described client node equipment when described authentication module verifies that the account of described user name has existed;
Creation module is used for when described authentication module verifies that the account of described user name does not exist the account who creates described user name;
The account information synchronization module, account's the information synchronization that is used for described user name that described creation module is created is to backup node equipment.
10, central node equipment as claimed in claim 9 is characterized in that, also comprises:
User log-in block is used to receive the landing request information that comprises the registering account user name from client node equipment, and confirms the login of client node equipment;
Sending module is used for after described user log-in block is confirmed the login of client node equipment, and the information of described registering account is sent to described client node equipment;
Receiver module, be used to receive the information of the registering account after the described client node apparatus modifications, and information that will this amended login account passes to described accounts information synchronization module, by the account information synchronization module with the information synchronization of described amended login account to backup node equipment.
11, a kind of backup node equipment is characterized in that, comprising:
The account information synchronization module is used for receiving accounts information from central node equipment;
User log-in block is used to receive from the landing request information that comprises the registering account user name of client node equipment and confirms the login of client node equipment;
Sending module is used for after described user log-in block is confirmed the login of client node equipment, and the information of described registering account is sent to described client node equipment;
Receiver module, be used to receive the information of the registering account after the described client node apparatus modifications, and information that will this amended login account passes to described accounts information synchronization module, by the account information synchronization module with the information synchronization of described amended login account to central node equipment.
12, a kind of Subscriber Management System is characterized in that, comprising: client node, Centroid and backup node, wherein:
Described client node is used to generate the registration information that comprises the designated user name and comprises the landing request information of specifying the registering account user name, selects suitable service node to provide user account registration service and account information to revise service according to the cryptographic Hash of described user name;
Described Centroid is used for when online as provide user account registration service and account information to revise the service node of service for described client node;
The accounts information that described backup node is used for the described client node registration of back-up storage or revises, and when described Centroid is not online, revise service for described client node provides user account information temporarily.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008101986652A CN101360111A (en) | 2008-09-22 | 2008-09-22 | Customer managing method, apparatus and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008101986652A CN101360111A (en) | 2008-09-22 | 2008-09-22 | Customer managing method, apparatus and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101360111A true CN101360111A (en) | 2009-02-04 |
Family
ID=40332448
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2008101986652A Pending CN101360111A (en) | 2008-09-22 | 2008-09-22 | Customer managing method, apparatus and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101360111A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011135169A1 (en) | 2010-04-29 | 2011-11-03 | Nokia Corporation | Method and apparatus for coordinating service information across multiple server nodes |
| CN102932185A (en) * | 2012-11-07 | 2013-02-13 | 曙光信息产业股份有限公司 | Server user management system |
| WO2014063551A1 (en) * | 2012-10-22 | 2014-05-01 | 腾讯科技（深圳）有限公司 | Account number generation method, device and system |
| CN104080175A (en) * | 2013-03-25 | 2014-10-01 | 腾讯科技（深圳）有限公司 | Number resource allocation method, terminal, server and system |
| CN107566412A (en) * | 2017-10-23 | 2018-01-09 | 朱子腾 | Account shared system based on dynamic password and network node memory technology |
| CN107908949A (en) * | 2017-10-20 | 2018-04-13 | 广东欧珀移动通信有限公司 | Information updating method, device and server |
| CN109376527A (en) * | 2018-09-29 | 2019-02-22 | 广州江南科友科技股份有限公司 | A kind of management method and system based on receipts and trustship in account |
-
2008
- 2008-09-22 CN CNA2008101986652A patent/CN101360111A/en active Pending
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011135169A1 (en) | 2010-04-29 | 2011-11-03 | Nokia Corporation | Method and apparatus for coordinating service information across multiple server nodes |
| CN102859532A (en) * | 2010-04-29 | 2013-01-02 | 诺基亚公司 | Method and apparatus for coordinating service information across multiple server nodes |
| US9628583B2 (en) | 2010-04-29 | 2017-04-18 | Nokia Technologies Oy | Method and apparatus for coordinating service information across multiple server nodes |
| WO2014063551A1 (en) * | 2012-10-22 | 2014-05-01 | 腾讯科技（深圳）有限公司 | Account number generation method, device and system |
| CN103780578A (en) * | 2012-10-22 | 2014-05-07 | 腾讯科技（深圳）有限公司 | Account generating method, system and apparatus |
| CN102932185A (en) * | 2012-11-07 | 2013-02-13 | 曙光信息产业股份有限公司 | Server user management system |
| CN104080175A (en) * | 2013-03-25 | 2014-10-01 | 腾讯科技（深圳）有限公司 | Number resource allocation method, terminal, server and system |
| CN107908949A (en) * | 2017-10-20 | 2018-04-13 | 广东欧珀移动通信有限公司 | Information updating method, device and server |
| CN107908949B (en) * | 2017-10-20 | 2020-04-21 | Oppo广东移动通信有限公司 | Information updating method and device and server |
| CN107566412A (en) * | 2017-10-23 | 2018-01-09 | 朱子腾 | Account shared system based on dynamic password and network node memory technology |
| CN109376527A (en) * | 2018-09-29 | 2019-02-22 | 广州江南科友科技股份有限公司 | A kind of management method and system based on receipts and trustship in account |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108881232B (en) | Sign-on access method, apparatus, storage medium and the processor of operation system | |
| CN101360111A (en) | Customer managing method, apparatus and system | |
| CN108470298B (en) | Method, device and system for transferring resource numerical value | |
| CN104008028B (en) | Intelligent mobile terminal data backup memory method and system based on many cloud storages | |
| CN106470184B (en) | Security authentication method, device and system | |
| WO2017016252A1 (en) | Token generation and authentication method, and authentication server | |
| CN103873505B (en) | Method, system and the device uploaded offline to cloud storage service device | |
| CN105812488A (en) | Cloud computing distributed service cluster system and method of using the system | |
| CN104052746B (en) | Heterogeneous applications single-node login system and its single-point logging method | |
| CN101877637A (en) | Single sign-on method and single sign-on system | |
| CN107705088B (en) | Service processing method, open platform and computer readable storage medium | |
| WO2020253634A1 (en) | Data processing method, system and device | |
| CN104754009A (en) | Service acquisition and invocation method, device, client-side and server | |
| CA2988434C (en) | Automatic recharging system, method and server | |
| CN104168304A (en) | System and method for single-sign-on in virtual desktop infrastructure environment | |
| CN106254377A (en) | Support soft load-balancing method and the system of the connection of magnanimity length | |
| CN109493051B (en) | Main chain and parallel multi-subchain system architecture capable of dynamically allocating and migrating accounts | |
| CN112101942A (en) | Transaction request processing method, system, device and equipment based on block chain | |
| CN105376347A (en) | IP address allocation method and system | |
| CN103414732A (en) | Application integration device and application integration processing method | |
| CN105208042A (en) | Resource safety access method and system | |
| CN102891863A (en) | Data reading and writing method | |
| CN111614726B (en) | Data forwarding method, cluster system and storage medium | |
| CN104184836A (en) | Multi-service single sign on system and method based on remote service business | |
| CN106375334A (en) | Authentication method for distributed system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20090204 |