CN106161420A

CN106161420A - GUID migrates method to set up

Info

Publication number: CN106161420A
Application number: CN201610011770.5A
Authority: CN
Inventors: 王正伟
Original assignee: Individual
Current assignee: Individual
Priority date: 2015-05-13
Filing date: 2016-01-09
Publication date: 2016-11-23

Abstract

The open a kind of GUID of the present invention migrates method to set up, in the method, described migration arranges operation flow and is initiated by corresponding MDSvr side, completes MDSvr side and the migration data configuration of corresponding MSSvr side simultaneously, simplify user's migration and operation is set, facilitate migration and handling of business is set.Invention additionally discloses a kind of GUID and migrate method to set up, in the method, described migration arranges operation flow and is initiated by corresponding MSSvr side, completes MSSvr side and the migration data configuration of corresponding MDSvr side simultaneously, simplify user's migration and operation is set, facilitate migration and handling of business is set.

Description

GUID migrates method to set up

Technical field

The present invention relates to internet communication, migrate the method arranged more particularly to GUID in the Internet.

Background technology

In internet communication, relate to whole world Unified Identity (GUID, Global Unified Identity), described GUID Including two parts: ownership code (HCode, Home Code) and user code (UCode, User Code).Wherein, HCode refers to Show a GUID, namely the Internet user (IUsr, Internet User) that this GUID is corresponding belongs to instant messaging network Which instantaneous communication system (IMS, Instant Messenger in (IMN, Instant Messenger Network) Namely belong to which attribution server (HSvr, Home Server) System),；UCode is for one HCode of instruction Lower different GUID or IUsr.

Shadow code is as a kind of special GUID, and the HCode of its correspondence is an ownership two tuples (H2T, Home Two-Tuple). Described H2T includes two parts: national code (CC, Country Code) and state's inside trade code (NBC, National Business Code), I.e. (CC, NBC) or CC*NBC.The representation of shadow code is generally: CC*NBC*UCode, and * is shadow code designator or divides here Every symbol.

More information, sees " communication means and system " patent of invention of Application No. 201310037232.X, and application number " shadow code addressing method " patent of invention for 201310049772.X.

By setting up the corresponding relation of HCode and HSvr, pointed HSvr can be obtained according to a HCode.Equally, According to the HCode of an IUsr, may determine that, according to the corresponding relation of described HCode and HSvr, the HSvr that this IUsr belongs to. Here, the HCode of an IUsr refers to the HCode of GUID of this IUsr.The corresponding relation of described HCode and HSvr can To be saved in HSvr, it is also possible to be stored in the equipment that HSvr can access.

In order to ensure that an IUsr can find the migration account of this GUID by a GUID, in Application No. In " supporting network and the related news processing method of GUID migration " patent of invention of 201310079118.3, disclose one Supporting the network that GUID migrates, in the network, at least HSvr is as the move target HSvr of GUID to be migrated (MDSvr, Migration Destination HSvr), migrates account for creating according to described GUID；For destination address In containing the message of described GUID, described MDSvr determines target account according to this GUID.Described network also includes described wanting Migrate the migration source HSvr (MSSvr, Migration Source HSvr) of GUID；Described GUID is registered in this MSSvr Across end HSvr information (CeSvrDesc, Cross-end HSvr Description), in order to indicate correspondence MDSvr；Right In the message that destination address is described GUID, described MSSvr, according to the source address of this message, replys the CeSvrDesc of this GUID； Or, for the message that destination address is described GUID, described MSSvr transmits the message to the CeSvrDesc of this GUID Indicated MDSvr.So, when a GUID is moved in another one HSvr, still this GUID can be moved Shifting account is addressed.

From the foregoing, it will be observed that the effective mobility of a GUID, in addition to creating the migration account of this GUID in corresponding MDSvr, relatively Goodly, in the MSSvr of this GUID, also mark the CeSvrDesc of this GUID.

In the middle of actual, if allow a user complete above-mentioned GUID in two service-domains respectively by hand migrate arranged simultaneously Action, it will have influence on the impression of user, more especially to internet, applications not very familiar user, operate, There may be obstacle.So, just influence whether that the actual of migration business is carried out.

It addition, illegal person utilizes other people GUID to create migration account in some HSvr, and utilize this migration account outside Send message, then there will be the phenomenon mixed the spurious with the genuine, thus encroach on the legitimate rights and interests of the real user of this GUID.

Summary of the invention

In view of this, the invention discloses GUID and migrate method to set up, be used at least one problem in above-mentioned various problems that solves.

A kind of GUID migrates method to set up, and in the method, described migration setting procedure is initiated by corresponding MDSvr side, the completeest Become MDSvr side and the migration data configuration of corresponding MSSvr side, simplify user's migration and operation is set, facilitate migration and industry is set Handling of business.Said method comprising the steps of:

A, MDSvr obtain GUID to be migrated, and create according to described GUID and migrate account；

B, described MDSvr send to the MSSvr of described GUID and migrate registration request, indicate this GUID in the request；

C, described MSSvr, after receiving described migration registration request, obtain the CeSvrDesc value of described GUID；Registration is described The CeSvrDesc of GUID.

Alternatively, in step a, the migration account created is holding account；Step a also includes: produce one and move State password, and described dynamic password is saved in described holding account；Construct one and activate link, logical in this activation links Cross parameter and carry described dynamic password, by this activation link MSSvr by described GUID, be sent to described GUID corresponding Client；Subsequently into activating responding process.

Alternatively, in step a, the migration account created is holding account；In step c, want performing described registration Before the operation of the CeSvrDesc of the GUID migrated, first sending according to this GUID and migrate license request, reception migrates license and rings Should, and after receiving described migration permission response, just perform the operation of the CeSvrDesc of described registration GUID to be migrated；

After step c, farther include step d: described MSSvr sends to described MDSvr and migrates register response；Described After MDSvr receives described migration register response, the holding account of described GUID is activated.

Alternatively, in step a, the migration account created is holding account；In step c, want performing described registration Before the operation of the CeSvrDesc of the GUID migrated, obtain a communicating number, produce a dynamic password, according to described logical Signal code sends produced dynamic password, waits the reply from MDSvr；Described method farther includes, described MDSvr Receive described dynamic password, the dynamic password of reception is sent to described MSSvr；Described MSSvr is receiving described dynamic password After, it may be judged whether consistent with the dynamic password previously produced, if unanimously, just perform described registration GUID's to be migrated The operation of CeSvrDesc, and send migration register response to described MDSvr；Described MDSvr receives described migration register response After, the holding account of described GUID is activated.

Alternatively, described MDSvr obtains corresponding communicating number, according to described communicating number and an one's own HCode Produce a superposition shadow code GUID together, the migration account created is set up bundle with described account corresponding for superposition shadow code GUID Tie up or incidence relation.

Alternatively, described communicating number is that described MDSvr obtains when obtaining GUID to be migrated.

Alternatively, described communicating number is to be obtained by described MSSvr, and carries described in acquisition in described migration register response Communicating number；Described MDSvr obtains described communicating number from described migration register response.

Another kind of GUID migrates method to set up, and in the method, described migration setting procedure is initiated by corresponding MSSvr side, simultaneously Complete MSSvr side and the migration data configuration of corresponding MDSvr side, simplify user's migration and operation is set, facilitate migration and arrange Handling of business, said method comprising the steps of:

A, MSSvr obtain GUID to be migrated and corresponding CeSvrDesc value, register phase in the account that described GUID is corresponding The CeSvrDesc value answered；

B, described MSSvr determine corresponding MDSvr according to described CeSvrDesc value, send migration request to this MDSvr, Request indicates described GUID；

After c, described MDSvr receive described migration request, create according to described GUID and migrate account.

Alternatively, described migration request carries respective communication number further；

In step c, described MDSvr, when creating migration account, also produces a password, is migrated account as creating Initial password preserves, and sends described password according to described communicating number.

Alternatively, described migration request carries respective communication number further；In step c, according to described communicating number with An one's own HCode produces a superposition shadow code GUID together, and with described, the migration account created is superposed shadow code Account corresponding for GUID sets up binding or incidence relation.

The GUID provided by the present invention migrates method to set up, facilitates user and carries out migration and arrange business operation, moreover it is possible to helps to solve Certainly identity personation phenomenon.

Accompanying drawing explanation

Shown in Fig. 1, a kind of GUID initiated by MDSvr side for the present invention migrates method to set up embodiment flow chart.

Shown in Fig. 2, a kind of GUID initiated by MSSvr side for the present invention migrates method to set up embodiment flow chart.

Shown in Fig. 3, for IMN networking illustration.

Detailed description of the invention

About IMN networking diagram, shown in Figure 3.In the figure, there is multiple service provider (SP, Service Provider) IMS, wherein, the HSvr of A service provider (SP-A) is HSvr-A, wherein, registers with user A (UsrA) and user X (UsrX)；The HSvr of B service provider (SP-B) is HSvr-B, wherein, registers with user B (UsrB) and user Y (UsrY)； The HSvr of C service provider (SP-C) is HSvr-C, wherein, registers with user C (UsrC) and user Z (UsrZ).

After the present invention with { as domain name, GUID is email address to the HCode of GUID } as a example by, but be not used in restriction.

For ease of understanding, in present invention narration below, it is that rice is chatted, SP-B is credulity, SP-C is footpath between fields, footpath between fields, HCode with SP-A Value immomo.com belongs to HSvr-C, HCode value yixin.im and belongs to HSvr-B, HCode value miliao.com ownership In HSvr-A etc., as a example by.

The present invention: belong to GUID in the territory that the GUID of this HSvr is called this HSvr；Do not belong to the GUID of a HSvr Overseas GUID for this HSvr.Such as, in guanyc@immomo.com and liubei@immomo.com is the territory of HSvr-C GUID, is the overseas GUID of HSvr-B and HSvr-A.

The most also introduce a kind of cross-domain address code (CDAddr, Cross-domain Address): described CDAddr be one across Domain addresses two tuple, including CeSvrDesc and Ben Ji GUID (BaseGUID, The Base GUID) two parts.Described CeSvrDesc For indicate this CDAddr corresponding across end HSvr, can be host IP address or the host domain name of this HSvr, usually, It is any one HCode of being had of this HSvr." the auxiliary addressing method " that see Application No. 201310073334.7 is sent out Bright patent.

Usually, a CDAddr can write (CeSvrDesc, BaseGUID) form, or writing The form of BaseGUID $ CeSvrDesc, wherein, " $ " is separator.

Below as a example by a CeSvrDesc is the HCode that corresponding HSvr is had, but it is not used in the restriction present invention.

For the ease of describing, the account that the present invention registers according to this GUID in the HSvr that a GUID belongs to is called this GUID Source account, the account registered according to this GUID in other HSvr is as the migration account of this GUID.Such as, according to GUID Value liubei@immomo.com, the account registered in HSvr-C is as the source account of liubei@immomo.com；According to GUID Value liubei@immomo.com, all the moving as liubei@immomo.com of the account registered in HSvr-A and HSvr-B Move account.

In order to solve an IUsr when changing SP, it has to the problem changing GUID, " support that GUID migrates described Network and related news processing method " in patent of invention, it is provided that support the network that GUID migrates.This network include some mutually The HSvr of connection, at least one of which HSvr, as the MDSvr of GUID to be migrated, migrates account for creating according to described GUID Family.For containing the message of described GUID to be migrated in destination address, described MDSvr determines target account according to this GUID.

So, for moving to the GUID in a MDSvr, when carrying out message addressing, after being addressed to this MDSvr, just The migration account of correspondence can be determined according to this GUID by this MDSvr.

Described MDSvr is after determining target account, it is also possible to further described message is ended in this target account.About such as More descriptions of what one message of termination, refering to described " network supporting GUID to migrate and related news processing method " invention Patent.Here repeat no more.

The network migrated based on described support GUID, a GUID to move in a HSvr, it is only necessary in this HSvr Create the migration account of this GUID.This HSvr is the MDSvr of this GUID.

The network migrated based on described support GUID, when sending message to the GUID migrated, can be with a CDAddr conduct The destination address of message, the CeSvrDesc of this CDAddr points to the BaseGUID of the MDSvr of this GUID, this CDAddr and is This GUID；Correspondingly, described MDSvr determines target account according to the BaseGUID of described CDAddr.

One GUID, after migration, can register the CeSvrDesc of this GUID in the MSSvr of this GUID, to indicate correspondence MDSvr.So, when other people send message according to this GUID, the MSSvr of this GUID can be by this GUID's of registration CeSvrDesc replies to the sender of message, and so, the sender of message just can be according to the CeSvrDesc replied and this GUID The CDAddr of composition to send message to the migration account of this GUID.So, a GUID after migration, corresponding IUsr It is no longer needed for informing especially the good friend of oneself.

Handling migration business for the ease of user, the present invention proposes GUID and migrates method to set up, handles migration industry simplifying user The operation of business.Described migration is arranged can be initiated by MDSvr side, it is also possible to initiated by MSSvr side.

As it is shown in figure 1, a kind of GUID initiated by MDSvr side for the present invention migrates method to set up embodiment flow chart.At this In embodiment, comprise the steps:

Step 11, MDSvr obtain GUID to be migrated, and create according to described GUID and migrate account.

In the middle of actual, the Information Retrieval Strategy that the mode of MDSvr establishment migration account uses to it is relevant.It is exemplified below several side Formula is for reference.

Mode one, when creating migration account in the MDSvr of this GUID according to a GUID, this MDSvr can direct basis This GUID preserves this migration account.

Such as: described MDSvr, can be by Account History corresponding for GUID in territory and overseas GUID pair when preserving accounts information The Account History answered is saved in a table, user account information table as shown in table 4:

Table 4

GUID	Password	Remark
			sunquan@miliao.com	********	The Account History of sunquan@miliao.com
zhouyu@miliao.com	********	The Account History of zhouyu@miliao.com
			liubei@immomo.com	********	The Account History of liubei@immomo.com

In table 4, sunquan@miliao.com and zhouyu@miliao.com be HSvr-A territory in GUID, Liubei@immomo.com is the overseas GUID of HSvr-A.

According to user account information table as shown in table 4, the accounts information of correspondence can be retrieved directly according to a GUID.

In the middle of actual, in order to improve recall precision, user account information table as shown in table 4 can be divided into two by described MDSvr Individual: user account information table corresponding for GUID in territory, the user account information table corresponding with overseas GUID.

Mode two, when creating migration account in the MDSvr of this GUID according to a GUID, MDSvr is corresponding according to this GUID Territory in GUID preserve this migration account.

Such as: first will migrate GUID and be converted to the user name of an email address, by a domain name kind of described MDSvr HCode is as the domain name of this email address, thus obtains an email address, preserves establishment according to this email address Migrate account.In described below many most by this way as a example by, but be not used in restriction.

During the present invention is described below, can relate to cover the application of mutually conversion between email address, territory and GUID, such as, how One email address is converted to a user name, or how the email address, territory of covering of a user name form is converted to The GUID of one email address format.About more descriptions of the method for mutually conversing between covering email address, territory and GUID, See " E-mail address coding method " patent of invention of Application No. 201310435356.3.Here and the most not Select again.

So that { the default indicated value of TLD im is i, is that c} is with the default indicated value of TLD com after the present invention Example is illustrated, but is not used in the restriction present invention.

Such as, when creating migration account in HSvr-A according to GUID value machao@yixin.im, can be by @in machao@yixin.im replace to double underline _ _, and TLD im is replaced to after i adds subdomain yixin to, Thus it is converted into machao__yixini.By machao__yixini Yu HSvr-A HCode value miliao.com mono- Rise and obtain a new email address machao__yixini@miliao.com.Correspondingly, described MDSvr is according to one When overseas GUID determines target account, first this overseas GUID can be converted to GUID in a territory, then according to GUID in this territory Determine target account.

User account information table as shown in table 4-A:

Table 4-A

GUID	Password	Remark
			sunquan@miliao.com	********	The Account History of sunquan@miliao.com
zhouyu@miliao.com	********	The Account History of zhouyu@miliao.com
			Liubei__immomoc@miliao.com	********	The Account History of liubei@immomo.com

In table 4-A, sunquan@miliao.com and zhouyu@miliao.com be HSvr-A territory in GUID, Liubei@immomo.com is the overseas GUID of HSvr-A, and Liubei__immomoc@miliao.com is the territory of HSvr-A Interior GUID.

According to the user account information table as shown in table 4-A, MDSvr is for GUID in a territory, directly according to a GUID, Retrieve the accounts information of correspondence；MDSvr is for an overseas GUID, according to by the territory obtained coded by this overseas GUID GUID, obtains the accounts information of correspondence.Such as, for overseas GUID value liubei@immomo.com, it is through compiling After Ma, corresponding to GUID value Liubei__immomoc@miliao.com in a territory of described MDSvr, this MDSvr is permissible The accounts information of correspondence is retrieved according to Liubei__immomoc@miliao.com.

Step 12, described MDSvr send to the MSSvr of described GUID and migrate registration request, indicate this GUID in the request.

Step 13, described MSSvr, after receiving described migration registration request, obtain the CeSvrDesc value of described GUID；Step on Remember the CeSvrDesc of described GUID.

In step 12, described this GUID of instruction in the request, can be directly to carry this GUID value in this request.

Certainly, in step 12, if described MSSvr only has a HCode value, permissible in the most described migration registration request It it is the UCode part carrying described GUID.Such as, described step 12 is further: described MDSvr is to described GUID's MSSvr sends and migrates registration request, carries the UCode part of this GUID in request.In this case, in step 13, Described MSSvr i.e. can determine that the GUID of correspondence according to the UCode part received.

So that { in step 12, described this GUID of instruction in the request is: carry this GUID} in this request after the present invention As a example by illustrate, but be not used in the restriction present invention.

In a MSSvr register GUID to be migrated CeSvrDesc, have various ways, be set forth below several for reference.

Mode one, migration information table is set registers the CeSvrDesc of this GUID according to a GUID.As shown in table 1 moves Move information table, for the migration information table of HSvr-C, this table have recorded the CeSvrDesc of corresponding GUID.

Table 1

GUID	CeSvrDesc	Remark
			guanyc@immomo.com	yixin.im	Guanyc@immomo.com moves to HSvr-B
liubei@immomo.com	miliao.com	Liubei@immomo.com moves to HSvr-A

Such as: the standby migration account registering liubei@immomo.com in HSvr-A of Liu, correspondingly, exist The HSvr-C of liubei@immomo.com ownership is had according to GUID value liubei@immomo.com registration HSvr-A One HCode value miliao.com, as the CeSvrDesc of liubei@immomo.com.

Migration information table as shown in table 1 is actually a kind of special direction information table, and the purpose that turns to of the most corresponding GUID is By the CDAddr corresponding to this GUID and corresponding CeSvrDesc.About more descriptions of direction information table, see application number It it is " diversion treatments method " patent of invention of 201310070280.9.

Mode two, preserve one and move outside GUID's by increasing CeSvrDesc field in accounts information table as shown in table 4 CeSvrDesc value, the accounts information table as shown in table 4-B.

Table 4-B

GUID	Password	CeSvrDesc	Remark
				guanyc@immomo.com	********	yixin.im	Guanyc@immomo.com moves to HSvr-B
zhugl@immomo.com	********	null	Zhuge Liang does not migrate
				liubei@immomo.com	********	miliao.com	Liubei@immomo.com moves to HSvr-A

In table 4-B, when the CeSvrDesc of certain Account History is null value null, then illustrate that this GUID does not move outside.

In described below, as a example by mode two, but it is not used in restriction.

In a step 11, MDSvr is when obtaining GUID to be migrated, it is also possible to be obtain this GUID corresponding cover territory email Address.Such as, for GUID value liubei@immomo.com, after it is encoded, corresponding covers email address, territory For Liubei__immomoc."@" symbolic code " _ _ " in Liubei__immomoc is replaced back "@", and by end The default indicated value " c " of position reverts to " com ", i.e. can get GUID value liubei immomo.com.

In the case of a HSvr only has a HCode, if two HSvr, such as HSvr1 and HSvr2, between build Stood SS connection, and the corresponding SS of HCode labelling that HSvr1 HSvr2 has connects, then, HSvr1 is according to reception SS connection corresponding to message may determine that opposite end HSvr, the HCode being had.The more descriptions connected about SS, See described " communication means and system " patent of invention.

Such as, it is connected if establishing SS between described MSSvr with described MDSvr, and the HCode labelling phase having with opposite end The SS answered connects, then, in step 13, described MSSvr is according to the SS received corresponding to described migration register request message even Connecing and may determine that opposite end HSvr, i.e. MDSvr, the HCode being had, using this HCode as described GUID to be migrated CeSvrDesc value.

It is preferred that in a step 11, described migration registration request also carries the CeSvrDesc of described GUID to be migrated Value, so, in step 13, described MSSvr is after receiving described migration registration request, directly from this migration registration request The CeSvrDesc value of the GUID that acquisition is to be migrated.Below as example, but it is not used in restriction.

Example 1.1: filing a request to HSvr-A and move in HSvr-A by liubei@immomo.com, respective process is as follows:

Step 1101, to this HSvr-A send registration request, request carries GUID value liubei@immomo.com.

Such as, HSvr-A provides registration web page, and liubei downloads this registration web page from HSvr-A, inputs on this webpage GUID to be migrated is liubei@immomo.com, then clicks on registration button, and this webpage is as client, to HSvr-A Send described registration request, request carries GUID value liubei@immomo.com.

After step 1102, described HSvr-A receive described registration request, create according to GUID value liubei@immomo.com and move Move account.

According to GUID value liubei@immomo.com, step 1103, HSvr-A determine that the MSSvr of correspondence is HSvr-C, then, Send to HSvr-C and migrate registration request, request is carried described GUID value liubei@immomo.com, and oneself has HCode value miliao.com using the CeSvrDesc as this GUID.

Step 1104, HSvr-C, after receiving described migration registration request, obtain described GUID value liubei@immomo.com With corresponding CeSvrDesc value miliao.com, determine the account of correspondence according to described GUID value liubei@immomo.com, In account determined by, the CeSvrDesc of registration liubei@immomo.com is miliao.com.

In step 1102, described HSvr-A creates according to GUID value liubei@immomo.com to be migrated and migrates account Can carry out according to the following two kinds mode.

Mode one, direct establishment according to GUID value liubei@immomo.com migrate account

Such as, user account information table as shown in table 4 increases a record, in this record, according to GUID value Liubei@immomo.com preserves corresponding accounts information.

Mode two, be converted to create after GUID value in territory migrate account

That is, the GUID value liubei immomo.com that will migrate is encoded to cover email address, territory by HSvr-A liubei__immomoc；Email address, territory liubei__immomoc login account is covered, that is, this is covered territory according to described Email address liubei__immomoc, as the UCode part of GUID in a territory, creates migration account.

Being created GUID in migrating the territory that account is corresponding is: by liubei__immomoc Yu CeSvrDesc value miliao.com GUID value liubei__immomoc@miliao.com in the territory formed together.

Such as, the user account information table as shown in table 4-A increases a record, in this record, according to GUID value Liubei__immomoc@miliao.com preserves corresponding accounts information.

In described below, as a example by { when corresponding MDSvr creates migration account according to a GUID, use mode two }, but not For limiting the present invention.

In a step 11: when described MDSvr obtains GUID to be migrated, it is also possible to obtain corresponding account password further, Correspondingly, when creating migration account, the account password of acquisition is preserved as creating the password migrating account.

Certainly, MDSvr is when creating migration account, it is also possible to one password of stochastic generation, as being created at the beginning of migration account Beginning password.The initial password of generation can also be sent to relative users by MDSvr further.Such as, when registration, it is desirable to use Family input receive initial password address, this address can be an email address, so can by send email by The initial password produced is sent to user；This address can also be a phone number, as such, it is possible to will be produced by note Initial password be sent to user.

Especially, in a step 11: when described MDSvr obtains GUID to be migrated, also obtain corresponding communicating number, will This communicating number, as the UCode part of a superposition shadow code GUID, produces one together with an one's own HCode and folds Add shadow code GUID；Correspondingly, after creating migration account, also by the account and described account corresponding for superposition shadow code GUID Set up binding or incidence relation.

About more descriptions of superposition shadow code GUID, see described " network supporting GUID to migrate and related news process side Method " patent of invention, the most no longer selects.

Set up multiple accounts of bundle relation, form an account bundle.Such as, account A and account B establish bundle relation, In account A, preserve the GUID value of account B, in account B, preserve the GUID value of account A.Step on when A account enters When entering state, B account is placed in and same logins state；Otherwise, when B account enters and logins state, A account is placed in Same logins state.So, after user logins any account of account bundle, multiple in can the account being restrainted simultaneously Account operates.So, user just it is very easy to.Account bundle solution will be in future communications, surmount and for Substitute the most effective practical means of unified communications solutions in existing telecommunications network.

Described step 11 is further: MDSvr obtains GUID to be migrated and corresponding communicating number, according to GUID to be migrated Create and migrate account；Produce one together with an one's own HCode according to described communicating number and superpose shadow code GUID, will The account sets up binding or incidence relation with described account corresponding for superposition shadow code GUID.

Such as, described step 1101 is further: sends registration request to this HSvr-A, carries GUID value in request Liubei@immomo.com and communicating number 8613923568901.Correspondingly, described step 1102 is step 1102B further: After HSvr-A receives described registration request, create according to GUID value liubei@immomo.com and migrate account；According to described logical Signal code 8613923568901 produces one together with one's own HCode value miliao.com and superposes shadow code GUID It is worth 8613923568901@miliao.com, is migrated account and described account foundation bundle corresponding for superposition shadow code GUID by creating Tie up or incidence relation.

In this case, it is preferred that using the password of described account corresponding for superposition shadow code GUID as according to GUID value The password of the migration account that liubei@immomo.com creates.

In step 1102B, if there is no 8613923568901 accounts corresponding for@miliao.com, then can return to user Return abnormal, tell that user does not exist the account of 8613923568901 correspondences.

In step 1102B, if there is no 8613923568901 accounts corresponding for@miliao.com, it is also possible to create further Build 8613923568901 accounts corresponding for@miliao.com, perform described foundation the most again and bundle or the operation of incidence relation.

One skilled in the art will appreciate that when the account that establishment 8613923568901 is corresponding for@miliao.com, in order to ensure safety Property, send an active coding produced can to communicating number 8613923568901, after user terminal receives described active coding, It is submitted to HSvr-A, HSvr-A after receiving described active coding, compares the most consistent with produced active coding, if one Cause, just activate described account.

Especially, when user performs registration operation by client end AP P downloading HSvr-A, this client can directly be read The active coding got, and this active coding is submitted to automatically HSvr-A, thus facilitate user.

In the middle of actual, it is also possible to be, when user logins in HSvr-A first according to 8613923568901@miliao.com, Prompting user inputs active coding, after judging that user inputs correct active coding, just activates the account.

If it is considered that HSvr has the situation of two HCode simultaneously, when described MDSvr obtains GUID to be migrated, also The CeSvrDesc value of correspondence can be obtained further.Correspondingly, when creating migration account, further according to acquired CeSvrDesc value is carried out, that is, using acquired CeSvrDesc value as the CeSvrDesc value of described GUID.Correspondingly, In the migration registration request that the MSSvr of described GUID sends, also carry the CeSvrDesc value of this GUID.

The GUID that illegal person utilizes Liu standby creates migrated users in some HSvr, and utilizes this migration account to be sent out disappearing Breath, can reach the purpose mixed the spurious with the genuine, thus infringement is to the legitimate interests of liubei.

Consider for communication security, HSvr-A registers the GUID account as liubei immomo.com, should obtain The GUID registered in HSvr-C is as the license of the account of liubei@immomo.com, namely obtains the license of liubei.

Legal in order to ensure the migration account created, described GUID can be verified by MDSvr further.

In a step 11, the migration account created is holding account.In described step 11, farther include to produce one and move State password, and described dynamic password is saved in described holding account；Construct one and activate link, logical in this activation links Cross parameter and carry described dynamic password, by this activation link MSSvr by described GUID to be migrated, be sent to described GUID Corresponding client；Subsequently into activating responding process.

Such as, the described a certain address of service that address is HSvr-A activating link correspondence, usually one network address, wherein carry Parameter include described dynamic password.

In described client corresponding for GUID to be migrated, user connects execution activation manipulation, to described by clicking on described activation MDSvr sends activation instruction, and instruction includes the described parameter including described dynamic password activating and carrying in link.Described After MDSvr receives described dynamic password, compare with the dynamic password preserved in described holding account, it is judged that the two is the most consistent, If consistent, then will activate the account, be i.e. changed into formal account, and terminate to activate responding process.If it is determined that received Dynamic password is inconsistent with the dynamic password of preservation in described holding account, then continue described activation responding process, or terminate whole Individual migration setting procedure.

Here, formal account and holding account can be distinguished by a Status Flag, such as, by preserve in holding account Dynamic password is set to null value null to represent that the account is activated as formal account.In the middle of actual, for holding account, i.e. do not have The account being activated, HSvr typically can limit certain operations, such as, for holding account, forbid that user passes through it to other account Send message.

Example 1.2: filing a request to HSvr-A and move in HSvr-A by liubei@immomo.com, respective process is as follows:

Step 1201, to this HSvr-A send registration request, request carries GUID value liubei@immomo.com.

Such as, SP-A provides relative client APP, and liubei downloads this client end AP P, and is held by this client end AP P Row registers operation: inputs GUID to be migrated as liubei@immomo.com, then clicks on registration button, this client end AP P, Send described registration request to HSvr-A, request carries GUID value liubei@immomo.com.

After step 1202, described HSvr-A receive described registration request, produce a dynamic password, according to GUID value Liubei@immomo.com creates holding account, preserves described dynamic password in this holding account；Construct one and activate link, In this activation links, carry described dynamic password by parameter, this activation is connected through the MSSvr of this GUID, is sent to this The client that GUID is corresponding；Wait client end response.Such as, the described a certain clothes that address is HSvr-A activating link correspondence Business address, usually one network address, the parameter wherein carried includes described dynamic password.

Here, according to GUID value liubei@immomo.com, HSvr-A determines that the MSSvr of correspondence is HSvr-C, then, and will Described activation link is sent to HSvr-C, and the destination address of message is GUID value liubei@immomo.com.HSvr-C is receiving After described message, determine corresponding client according to the destination address liubei@immomo.com of message, send out to this client Described activation is sent to link.

Here, in HSvr-C, can set up online user's information table as shown in table 3, HSvr-C exists After liubei@immomo.com logins, save the online record of liubei@immomo.com in the table.

Table 3

GUID	IP address	Port	Remark
				zhugl@immomo.com	The IP address of relative client	Respective end slogan
liubei@immomo.com	The IP address of relative client	Respective end slogan

In table 3, the IP address of IP address field client corresponding for corresponding GUID with Port field record and port numbers. Certainly, if the port numbers of unified subscribed client, then, in table 3, Port field can be saved.

The IP address and/or the port numbers that obtain login client when logging in are mature technologies, see " communication means and system " Patent of invention.Here repeat no more.

When client set up with HSvr TCP be connected time, it is also possible to corresponding connection identifier, such as corresponding socket descriptor (SktD, Socket Descriptor) identifies the client of correspondence.

After the present invention as a example by identifying client by client ip address and port numbers, but it is not used in the restriction present invention.

User, when client opens described activation link, can send an instruction accessing HSvr-A, carry in this instruction Described dynamic password, so, HSvr-A can receive described dynamic password.

It is the mature technology being widely used owing to activation is linked at during login account activates, repeats no more the most here.

Step 1203, HSvr-A receive the described dynamic password that described client sends, it is judged that this dynamic password and described interim account The dynamic password preserved in family is the most consistent, if unanimously, then described holding account is converted to formal account, i.e. activates this account Family, and send registration request to HSvr-C, request is carried described GUID value liubei@immomo.com to be migrated, with And one's own HCode value miliao.com is using the CeSvrDesc value as this GUID.

Step 1204, HSvr-C are after receiving described registration request, and the CeSvrDesc of registration liubei@immomo.com is miliao.com。

In step 1202, described may furthermore is that according to GUID value liubei@immomo.com establishment holding account: GUID value liubei@immomo.com is converted to cover territory emai address value liubei__immomoc by HSvr-A, will Liubei__immomoc, as the UCode part of GUID in territory, creates described holding account.Created holding account is corresponding Territory in GUID be: by the GUID value formed together with liubei__immomoc with CeSvrDesc value miliao.com liubei__immomoc@miliao.com。

Activate in the parameter that link is carried it should be noted that described, it is also possible to farther include the relevant information of described GUID, The most described relevant information is directly this GUID, or this GUID carries out one that digest calculations obtains according to certain algorithm and plucks Want information.So, when user performs activation manipulation, described MDSvr can obtain the relevant information of described GUID further, And the holding account of this GUID is determined according to the relevant information of described GUID.So, described MDSvr is accepting multiple migration Shen Please time, asynchronous message process can be carried out, thus improve treatment effeciency.

Such as, described step 1202 further: after described HSvr-A receives this registration request, produce a dynamic password, Create holding account according to GUID value liubei@immomo.com, this holding account preserves described dynamic password；Structure one Individual activation links, and carries described dynamic password and GUID value liubei@immomo.com by parameter in this activation links, will This activation connects through the MSSvr of this GUID, is sent to client corresponding to this GUID；Wait client end response.Correspondingly, Described step 1203 is further: HSvr-A receives described dynamic password and the GUID value that described client sends, according to described GUID value liubei@immomo.com determines corresponding holding account；Judge this dynamic password with determined by holding account is protected The dynamic password deposited is the most consistent, if unanimously, then described holding account is converted to formal account, i.e. activates the account, and Send registration request to HSvr-C, request is carried described GUID value liubei@immomo.com to be migrated, and oneself HCode value miliao.com having is using the CeSvrDesc value as this GUID.

This use-case is generally used for described MSSvr and described MDSvr has carried out the situation of safety verification.Such as, described MSSvr Establish secure connection with described MDSvr in advance, and when setting up secure connection, both sides are to being recognized the other side's identity respectively Card, thus avoid malice and connect.

Its MSSvr is belonged to, it is preferred that described GUID is verified by MSSvr in view of described GUID.

In a step 11, the account created is holding account.Correspondingly, in step 13, to move performing described registration Before the operation of the CeSvrDesc of the GUID moved, first send according to this GUID and migrate license request, receive and migrate permission response, And after receiving described migration permission response, just perform the operation of the CeSvrDesc of described registration GUID to be migrated.

Correspondingly, after step 13, farther include step 14: described MSSvr sends to described MDSvr and migrates registration Response；After described MDSvr receives described migration register response, the holding account of described GUID is activated.Such as, described migration Register response is carried described GUID, described MDSvr and determines the holding account of correspondence according to described GUID, by this holding account Activate.

The GUID that described basis is to be migrated sends and migrates license request it may be that sent out as the destination address of message by this GUID Send described migration license request.Such as, directly described migration license request is sent to the client of this GUID.

Example 1.3: filing a request to HSvr-A and move in HSvr-A by liubei@immomo.com, respective process is as follows:

Step 1301, to this HSvr-A send registration request, request carries GUID value liubei@immomo.com.

After step 1302, described HSvr-A receive this registration request, create interim according to GUID value liubei@immomo.com Account；Determine that according to this GUID value liubei@immomo.com the MSSvr of correspondence is HSvr-C, then, send out to HSvr-C Send migration registration request, request is carried described GUID value liubei@immomo.com to be migrated, and one's own one Individual HCode value miliao.com is using the CeSvrDesc value as this GUID.

Step 1303, HSvr-C, after receiving described migration registration request, obtain described GUID value to be migrated Liubei@immomo.com and corresponding CeSvrDesc value miliao.com.

Step 1304, determine corresponding client according to liubei@immomo.com, send to this client and migrate license request, Request is carried the CeSvrDesc value of correspondence；Then the migration permission response from liubei@immomo.com client is waited.

After step 1305, the client of liubei@immomo.com receive described migration license request, receive user and select, and Respond.Such as, by the dialog box included validating that with cancel button ejected in client, show in dialog box Corresponding CeSvrDesc value, and wait that user confirms；After the message receiving user liubei selection ACK button, this client Hold to send to HSvr-C and migrate permission response.

Step 1306, HSvr-C, after receiving the migration permission response that described client sends, register liubei@immomo.com CeSvrDesc be miliao.com；The migration register response about liubei@immomo.com is sent to HSvr-A.Example As, described migration register response can be carried GUID value liubei@immomo.com to be migrated.

After step 1307, HSvr-A receive described migration register response, described holding account is activated and becomes formal account.

Such as, after HSvr-A receives described migration register response, therefrom obtain GUID value liubei@immomo.com to be migrated, Determine the holding account of correspondence according to this GUID, holding account determined by general activates as formal account.

In step 1302, described HSvr-A can also remind registration to migrate the user of account, enters into the client of corresponding GUID Hold to perform to migrate permit operation.

It should be noted that as a kind of mapping mode, in step 1302, described HSvr-A can also not create temporarily Account, but in step 1307, directly create described formal account.

In step 1306, HSvr-C can also obtain a communicating number further, such as 8613923568901, described in move Move in register response and also carry described communicating number.Correspondingly, in step 1307, HSvr-A is always according to described communicating number 8613923568901 produce one together with one's own HCode value miliao.com superposes shadow code GUID value 8613923568901@miliao.com, set up binding by the migration account created with described account corresponding for superposition shadow code GUID Or incidence relation.

Such as, in HSvr-C, described communicating number is pre-stored in the account that liubei@immomo.com is corresponding, or, Account corresponding for liubei@immomo.com is corresponding with a superposition shadow code GUID value 8613923568901@immomo.com Account establishes association or bundle relation, and described communicating number is the UCode part of this superposition shadow code GUID, i.e. 8613923568901。

By sending a communicating number to MDSvr so that user can previously be created by MDSvr for this communicating number Account and newly created migration account automatically set up bundle relation, thus reach to the business effect of a kind of beautiful experience of user.

If HSvr-A judges that described account corresponding for superposition shadow code GUID value 8613923568901@immomo.com does not exists, The most do not set up described binding or incidence relation.In this case, an initial password can be produced as the migration account created Password, and by this password by short message sending to user, the destination Mobile Station International ISDN Number of note is 8613923568901.

After setting up described association or bundle relation, HSvr-A can not be that newly created migration account produces initial password, but Using the password of described account corresponding for superposition shadow code GUID as the password of described newly created migration account.HSvr-A is all right The content that this bundle relation notifies in the way of note user, such as note is that " New Account is right with 8613923568901 Answering account to set up association or bundle relation, New Account password is consistent with interlock account password ".The destination Mobile Station International ISDN Number of note is described communication Number.

If HSvr-A judges to there are not 8613923568901 accounts corresponding for@miliao.com, it is also possible to create further 8613923568901 accounts corresponding for@miliao.com, perform to set up the operation of described binding or incidence relation the most again.This In the case of, it is also possible to automatically generate a password, as the initial password of newly created account, and by short message mode, this is close Code is sent to user, and the destination Mobile Station International ISDN Number of note is the UCode of described superposition shadow code GUID value 8613923568901@miliao.com Part, i.e. 8613923568901.

Especially, in order to reduce the disturbance for user of the MSSvr side, described MSSvr receive migrate permission response can be from Described MDSvr receives.So, user avoids the need for logining and gets final product smooth transacting business in MSSvr.

Such as, described migration license request farther includes a password, and described migration permission response includes this password, this Whether sample, be corresponding to migrate the password that license request includes and sentence by comparing password in the described migration permission response of reception This migration permission response disconnected is the most effective, if the two is inconsistent, then it is assumed that this migration permission response is invalid, can directly terminate This migrates setting procedure.

It is to be illustrated as a example by the dynamic password that randomly generates according to certain algorithm of MSSvr by described password below.

Example 1.4: filing a request to HSvr-A and move in HSvr-A by liubei@immomo.com, respective process is as follows:

Step 1401, to this HSvr-A send registration request, request carries GUID value liubei@immomo.com.

After step 1402, described HSvr-A receive described registration request, create according to GUID value liubei@immomo.com and face Time account；Determine that according to this GUID value liubei@immomo.com the MSSvr of correspondence is HSvr-C, then, to HSvr-C Send and migrate registration request, request is carried described GUID value liubei@immomo.com to be migrated, and one's own One HCode value miliao.com is using the CeSvrDesc value as this GUID.

After step 1403, HSvr-C receive described migration registration request, obtain described GUID value to be migrated Liubei@immomo.com and corresponding CeSvrDesc value miliao.com.

Step 1404, HSvr-C produce a dynamic password, determine the reception ground of dynamic password according to liubei@immomo.com Location, sends the migration license request carrying described dynamic password according to this address, waits from carrying of HSvr-A corresponding dynamic The migration permission response of password.Here, when sending described dynamic password, it is also possible to carry the CeSvrDesc of correspondence further Value, to help user to identify.

Here, described reception address pre-saves communicatedly in can being the account that GUID value liubei@immomo.com is corresponding Location, e.g. one email address.

Usually, described reception address is communicating number, such as a phone number.In this case, GUID value The account that liubei@immomo.com is corresponding can pre-save this communicating number.Especially, superpose with one when the account Shadow code GUID, such as 8613923568901@immomo.com, when corresponding account association or binding, this superposition shadow code GUID UCode part, i.e. 8613923568901, described communicating number can be considered.

When described reception address is a communicating number, can be by dynamic password described in short message sending.

Step 1405, HSvr-A receive described dynamic password, and after receiving described dynamic password, by migrating permission response Message, is sent to HSvr-C by this dynamic password.

Such as, dynamic password entrained in the note of reception, by described client end AP P, is sent to HSvr-A by user.

If using registration web page to register, then HSvr-A can receive described dynamic password by registration web page.Example As, the aft section of registration web page includes dynamic password entry item.Such as, after user receives note by telecommunications network terminal, The dynamic password that this note includes is input in described registration web page, and submits to HSvr-A by this registration web page.

Especially, when client end AP P performing registration is in telecommunications network terminal corresponding to described communicating number, this client end AP P Can directly read the short message received, parse corresponding dynamic password, dynamic password parsing obtained is sent to HSvr-A. In this case, just eliminate user and manually enter the trouble of dynamic password, thus facilitate user.

Step 1406, HSvr-C migrate after permission response receiving the described dynamic password that carries that HSvr-A sends, it is judged that connect The dynamic password received is the most consistent with the dynamic password previously produced, if unanimously, then registers l iubei@immomo.com's CeSvrDesc is miliao.com, and sends about the migration register response of liubei@immomo.com to HSvr-A, otherwise, Terminate flow process.

After step 1407, HSvr-A receive described migration register response, described holding account is activated as formal account.

Such as, after HSvr-A receives described migration register response, therefrom obtain GUID value liubei@immomo.com to be migrated, Determine the holding account of correspondence according to this GUID, holding account determined by general is changed into formal account.

In step 1404, if the reception address of dynamic password, then process ends cannot be determined.In this case, it is possible to To process by step 1304 in example 1.3 and flow process afterwards thereof further.In this case, HSvr-C can also be further Send reception address to HSvr-A and cannot determine notice, after HSvr-A receives this notice, by described client end AP P or user Enrollment page reminds user, " please login related account in HSvr-C, to receive described migration license request ".

Usually, described reception address is communicating number.As a example by described reception address is for communicating number 8613923568901:

In step 1406, described migration register response is also carried described communicating number 8613923568901.Correspondingly, exist In step 1407, HSvr-A is always according to described communicating number 8613923568901 and an one's own HCode value Miliao.com produces a superposition shadow code GUID value 8613923568901@miliao.com together, will be created migration account Binding or incidence relation is set up with described account corresponding for superposition shadow code GUID.

If HSvr-A judges that described account corresponding for superposition shadow code GUID value 8613923568901@immomo.com does not exists, The most do not set up described binding or incidence relation.In this case, a password can be produced as at the beginning of the migration account created Beginning password, and by this password by short message sending to user, the destination Mobile Station International ISDN Number of note is 8613923568901.

After setting up described association or bundle relation, HSvr-A can not be that newly created migration account produces initial password, but Using the password of described account corresponding for superposition shadow code GUID as the password of described newly created migration account.HSvr-A is all right The content that this bundle relation notifies in the way of note user, such as note is that " New Account is right with 8613923568901 The account answered sets up association or bundle relation, and New Account password is consistent with interlock account password ", the destination Mobile Station International ISDN Number of note is described logical Signal code.

As in figure 2 it is shown, a kind of GUID initiated by MSSvr side for the present invention migrates method to set up embodiment flow chart.At this In embodiment, comprise the steps:

Step 21, MSSvr obtain GUID to be migrated and corresponding CeSvrDesc value, in the account that described GUID is corresponding Register corresponding CeSvrDesc value.

Such as, GUID and corresponding CeSvrDesc value that client will migrate are sent to MSSvr, and this MSSvr receives and to move The GUID moved and corresponding CeSvrDesc value, at the accounts information the exterior and the interior as shown in table 4-B, in the account that this GUID is corresponding In record, register corresponding CeSvrDesc value.

Further for example, under client is in the state of logining, user selects shift function menu or button, perform migration operation, visitor Family end obtains the CeSvrDesc value of user's input, and this CeSvrDesc value is sent to server.Server is according to client ip Address, according to described online user's information table, it is possible to obtain the GUID value that this client is corresponding.

In view of the situation of the corresponding multiple accounts of a client, such as, multiple accounts bundle or are associated together.It is preferred that Client is when sending migration request, in addition to carrying described CeSvrDesc value, also indicates that the GUID to be migrated of correspondence.Example As, carrying this GUID the most in the request, or carry the instruction information of this GUID in the request, described MSSvr is according to institute State instruction information and determine GUID to be migrated.

Step 22, described MSSvr determine corresponding MDSvr according to described CeSvrDesc value, send to migrate to this MDSvr and ask Ask, indicate described GUID in the request.

After step 23, described MDSvr receive described migration request, create according to described GUID and migrate account.

As a kind of general knowledge, in step 23, if MDSvr judges to have existed the migration account of described GUID, the most directly End operation.The most no longer this is repeated.

In step 22, the described described GUID of instruction in the request, can be directly to carry this GUID value in this request.

If MSSvr only has a HCode, and, establish SS between described MDSvr with described MSSvr and be connected, and The corresponding SS of HCode labelling having with opposite end connects, then, in step 23, described MDSvr is according to receiving described migration Request SS connection corresponding to message may determine that opposite end HSvr, i.e. MSSvr, the HCode being had.In this case, In step 22, the described described GUID of instruction in the request, can be the UCode part carrying this GUID in this request.

So that { in step 22, the described described GUID of instruction in the request is: carry this GUID} in this request after the present invention As a example by illustrate, but be not used in the restriction present invention.

Example 2.1: Liu is standby logins HSvr-C, HSvr-C at liubei@immomo.com according to GUID value liubei@immomo.com After logining, online user's information table as shown in table 3 saves the online record of liubei@immomo.com.

Filing a request to HSvr-C moves in HSvr-A by liubei@immomo.com, and respective process is as follows:

Step 2101, the client of liubei@immomo.com send migration request to HSvr-C, carry correspondence in request CeSvrDesc value miliao.com, in order to indicate in HSvr-A to be moved to.

Step 2102, HSvr-C receive described migration request, at the accounts information the exterior and the interior as shown in table 4-B, by CeSvrDesc Value miliao.com is saved in the Account History that liubei@immomo.com is corresponding.

Such as, HSvr-C is when receiving described migration request, according to the IP address of client and the end that send described migration request Slogan, the GUID value obtaining correspondence from online user's information table as shown in table 3 is liubei@immomo.com.According to GUID Value liubei@immomo.com, determines the Account History of correspondence, by CeSvrDesc from the accounts information the exterior and the interior as shown in table 4-B Value miliao.com is saved in this record.

According to described CeSvrDesc value miliao.com, step 2103, HSvr-C determine that the MDSvr of correspondence is HSvr-A, in It is to send migration request to HSvr-A, request is carried GUID value liubei@immomo.com.

After step 2104, described HSvr-A receive described migration request, according to GUID value liubei@immomo.com to be migrated Create and migrate account.

In step 2104, described HSvr-A creates according to GUID value liubei@immomo.com to be migrated and migrates account Can carry out according to the following two kinds mode.

Mode two, be converted to create after GUID value in territory migrate account

That is, it is encoded to cover email address, territory liubei__immomoc by GUID value liubei@immomo.com；According to described Cover email address, territory liubei__immomoc login account, that is, this is covered email address, territory liubei__immomoc Migration account is created as a user name.

If it is considered that HSvr has the situation of two HCode values, the most in step 22, also may be used in described migration request To carry described CeSvrDesc value further.Correspondingly, in step 23, when creating described migration account, further root Carry out according to this CeSvrDesc value.

Have as a example by HCode value yixin.im and 163.com by HSvr-B below simultaneously and be illustrated.

Example 2.2: Liu is standby logins HSvr-C according to GUID value liubei@immomo.com, after logining, proposes to HSvr-C Liubei@immomo.com is moved in HSvr-B by request, and requires that corresponding CeSvrDesc value is yixin.im, phase Answer process as follows:

Step 2201, the client of liubei@immomo.com send migration request to HSvr-C, carry and migrate in request GUID value liubei@immomo.com, and CeSvrDesc value yixin.im of correspondence, in order to indicate HSvr-B to be moved to In.

Step 2202, HSvr-C receive described migration request, at the accounts information the exterior and the interior as shown in table 4-B, by CeSvrDesc Value yixin.im is saved in the Account History that liubei@immomo.com is corresponding.

Such as, after HSvr-C receives described migration request, according to GUID value liubei@immomo.com, from as shown in table 4-B Accounts information the exterior and the interior determine correspondence Account History, CeSvrDesc value yixin.im is saved in this record.

According to described CeSvrDesc value yixin.im, step 2203, HSvr-C determine that the MDSvr of correspondence is HSvr-B, then Send migration request to HSvr-B, request carries GUID value liubei@immomo.com and CeSvrDesc value yixin.im.

After step 2204, described HSvr-B receive described migration request, the GUID value liubei@immomo.com that will migrate It is encoded to liubei__immomoc, together with CeSvrDesc value yixin.im, obtains GUID value in territory liubei__immomoc@yixin.im；According to liubei__immomoc@yixin.im login account.

Such as, the user account information table as shown in table 4-A increases a record, in this record, according to GUID value Liubei__immomoc@yixin.im preserves corresponding accounts information.

In step 22, described request can not also be carried described GUID to be migrated, but carry described GUID to be migrated Cover email address, territory for corresponding one.Such as, described step 22 is further: described MSSvr is according to described CeSvrDesc Value determines corresponding MDSvr, described GUID is converted to one and covers email address, territory, sends migration request to described MDSvr, Request is carried this and covers email address, territory.Correspondingly, described step 23 is step 23B further: described MDSvr have received After described migration request, migrate account according to described territory email address creation of covering, this will cover email address, territory as one User name creates migration account.

Example 2.3: Liu is standby logins HSvr-C according to GUID value liubei@immomo.com, after logining, proposes to HSvr-C Liubei@immomo.com is moved in HSvr-A by request, and respective process is as follows:

Step 2301, the client of liubei@immomo.com send migration request to HSvr-C, carry and migrate in request GUID value liubei@immomo.com, and CeSvrDesc value miliao.com of correspondence, to move in order to indicate In HSvr-A.

Step 2302, HSvr-C receive described migration request, at the accounts information the exterior and the interior as shown in table 4-B, by CeSvrDesc Value miliao.com is saved in the Account History that liubei@immomo.com is corresponding.

Such as, after HSvr-C receives described migration request, according to GUID value liubei@immomo.com, from as shown in table 4-B Accounts information the exterior and the interior determine correspondence Account History, CeSvrDesc value miliao.com is saved in this record.

GUID value liubei@immomo.com is converted to one and covers email address, territory by step 2303, HSvr-C, obtains liubei__immomoc；According to described CeSvrDesc value miliao.com determine correspondence MDSvr be HSvr-A, then to HSvr-A sends migration request, carries and cover email address, territory liubei__immomoc in request.

After step 2304, described HSvr-A receive described migration request, cover email address, territory liubei__immomoc according to described Create and migrate account, that is, email address, territory liubei__immomoc will be covered as a user name to create migration account.

That is, described HSvr-A creates according to GUID value liubei__immomoc@miliao.com migrates account.

Certainly, step 23B can also be further: described MDSvr have received carry described in cover email address, territory migration please After asking, this is covered email address, territory and is converted to the GUID of correspondence, then create according to this GUID and migrate account.

Such as, described step 2304 is further: after described HSvr-A receives described migration request, will cover email address, territory "@" symbolic code in liubei__immomoc " _ _ " replace back "@", and " c " of position, end is replaced into " com ", Thus recover GUID value liubei@immomo.com, then directly create according to GUID value liubei@immomo.com and migrate Account.Such as, user account information table as shown in table 4 increases a record, in this record, according to GUID value Liubei@immomo.com preserves corresponding accounts information.

Client is when the CeSvrDesc value pointing out user to input correspondence, it is also possible to prompting user inputs corresponding migration further Account password.

Correspondingly, in step 21, MSSvr can also receive described migration account password further, and such as, client is also entered One step obtains the password migrating account, and the migration account password of acquisition is sent to corresponding MSSvr.

Correspondingly, in step 22, described migration request is carried described migration account password the most further.

Correspondingly, in step 23, described MDSvr also using the described migration account password that receives as the migration account created Password preserve.

In the middle of actual, it is also possible to be: in step 23, described MDSvr, when creating migration account, produces a password conduct Created the initial password migrating account, this password is saved in created migration Account History.Described MDSvr can lead to Cross and randomizer is set to produce password.

Correspondingly, after step 23, still further comprise step 24: the password of generation is sent to described by described MDSvr The user that GUID is corresponding.

The password of generation is sent to user corresponding for described GUID by described MDSvr can be to use the following two kinds mode:

The password of generation is sent to the MSSvr of described GUID by mode one, described MDSvr, and described password is sent by this MSSvr To the user that this GUID is corresponding, such as, it is sent to client corresponding to this GUID.

Mode two, described migration request are carried further user corresponding for described GUID further in connection with mode, described MDSvr By this contact method, produced password is sent to corresponding user.Such as, described contact method is a communicating number, Produced password is sent to corresponding user by short message mode by the most described MDSvr, and the most described MDSvr constructs note, will The destination address of this note is set to described communicating number, includes produced password at this short message content, by this short message sending Go out.When sending note, also filling in the calling address of correspondence, this calling address is generally short message service code.Owing to being public affairs Know technology, repeat no more here.Further for example, described contact method is an email address, the most described MDSvr is by sending Produced password is sent to the mailbox of relative users by email mode.

In step 22, described migration request is carried a communicating number the most further.Such as, described communicating number can be One phone number.

Such as, in step 21, described MSSvr, when obtaining GUID to be migrated and corresponding CeSvrDesc value, also may be used To obtain corresponding communicating number further.

In the middle of actual, in described MSSvr, corresponding communicating number can be preserved in described account corresponding for GUID to be migrated. In this case, in step 22, preserve during described MSSvr directly carries described GUID account in described migration request Communicating number.

Especially, in described MSSvr, described account corresponding for GUID to be migrated superposes shadow code GUID with one, such as 8613923568901@immomo.com, corresponding account establishes binding or incidence relation, then can be by this superposition shadow code GUID UCode part, i.e. 8613923568901, as a communicating number.In this case, in step 22, described MSSvr The UCode part of described superposition shadow code GUID is carried using as described communicating number in described migration request.

In step 23, described MDSvr, when creating migration account according to described GUID to be migrated, produces account further Initial password, is saved in this password in created account.In step 24, described MDSvr is according to the described communication obtained Number, sends produced password to user corresponding for described GUID.

The password of generation can also be sent to described MSSvr by described MDSvr, described MSSvr be sent to by this password described The user that GUID is corresponding.With reference to above-mentioned MDSvr way, no longer indiscriminately imitate.

Especially, described step 22 is step 22C further: described MSSvr determines according to described CeSvrDesc value accordingly MDSvr, sends migration request to this MDSvr, carries GUID to be migrated and a communicating number in request.

Correspondingly, described step 23 is step 23C further: after described MDSvr receives described migration request, wants according to described The GUID migrated creates and migrates account；Produce one according to described communicating number together with an one's own HCode and superpose shadow Code GUID, sets up binding or incidence relation by the migration account created with described account corresponding for superposition shadow code GUID.

In this case, can be using the password of described account corresponding for superposition shadow code GUID as being created the password migrating account.

Example 2.4: in HSvr-C, account that GUID value liubei@immomo.com is corresponding and superposition shadow code GUID value 8613923568901 accounts corresponding for@immomo.com establish bundle relation.Liu is standby according to GUID value Liubei@immomo.com or superposition shadow code GUID value 8613923568901@immomo.com logins HSvr-C, is logining After, to file a request to HSvr-C and liubei@immomo.com is moved in HSvr-A, respective process is as follows:

Step 2401, the client of liubei@immomo.com send migration request to HSvr-C, carry and migrate in request GUID value liubei@immomo.com, and CeSvrDesc value miliao.com of correspondence, to move in order to indicate In HSvr-A.

Step 2402, HSvr-C receive described migration request, at the accounts information the exterior and the interior as shown in table 4-B, by CeSvrDesc Value miliao.com is saved in the Account History that liubei@immomo.com is corresponding.

Such as, HSvr-C is when receiving described migration request, according to GUID value liubei@immomo.com, from such as table 4-B institute The accounts information the exterior and the interior shown determines the Account History of correspondence, CeSvrDesc value miliao.com is saved in this record.

According to described CeSvrDesc value miliao.com, step 2403, HSvr-C determine that the MDSvr of correspondence is HSvr-A, in It is to send migration request to HSvr-A, request carries fold corresponding with binding account of GUID value liubei@immomo.com Add the UCode part of shadow code GUID value 8613923568901@immomo.com, i.e. communicating number 8613923568901.

After step 2404, described HSvr-A receive described migration request, according to GUID value liubei@immomo.com to be migrated Create and migrate account；According to described communicating number 8613923568901 and one's own HCode value miliao.com mono- Rise and produce a superposition shadow code GUID value 8613923568901@miliao.com, superposed shadow by creating migration account with described Account corresponding for code GUID sets up binding or incidence relation.

In this case, it is preferred that HSvr-A using the password of described account corresponding for superposition shadow code GUID as according to GUID value The password of the migration account that liubei@immomo.com creates.

In step 2404, the GUID value liubei@immomo.com that described HSvr-A will migrate is encoded to cover territory email Address liubei__immomoc；Migration account is created according to described email address, the territory liubei__immomoc that covers, that is, This is covered email address, territory liubei__immomoc as a user name to create migration account.

In step 2404, if there is no 8613923568901 accounts corresponding for@miliao.com, then can return to user Return abnormal, tell that user does not exist the account of 8613923568901 correspondences.Such as, return abnormal information by short message mode, The destination Mobile Station International ISDN Number of note is 8613923568901.

In step 2404, if there is no 8613923568901 accounts corresponding for@miliao.com, it is also possible to create further Build 8613923568901 accounts corresponding for@miliao.com, perform the operation of described binding or incidence relation the most again.

When the account that establishment 8613923568901 is corresponding for@miliao.com, in order to ensure safety, may further produce one Active coding, and send this active coding to communicating number 8613923568901, after user receives active coding, it is submitted to HSvr-A, HSvr-A, after receiving described active coding, compares the most consistent with produced active coding, if unanimously, just activates described account. Usually, this operation can perform when user logins 8613923568901@miliao.com account first.

Such as, when user logins in HSvr-A first according to 8613923568901@miliao.com, prompting user inputs sharp Code alive, after judging that user inputs correct active coding, just activates the account.

Especially, it is also possible to described active coding is protected as the temporary password of account corresponding to 8613923568901@miliao.com It is stored in the account.

Such as, in step 2404, if there is no 8613923568901 accounts corresponding for@miliao.com, it is also possible to enter One step creates 8613923568901 accounts corresponding for@miliao.com, performs the operation of described binding or incidence relation the most again. In this case, it is also possible to automatically generate a password, as the initial password of described newly created account, and communicating number is given 8613923568901 send this password, such as, and by short message mode, this password are sent to user, the purpose number of note Code is the UCode part of described superposition shadow code GUID value 8613923568901@miliao.com, i.e. 8613923568901.

Superposition shadow code GUID and entitled Dou Bushi source, the email address GUID covering email address, territory of user.Such as, 8613923568901@miliao.com and liubei__immomoc@miliao.com are not the most source GUID, 8613923568901 shadow code 86*139*23568901 corresponding for@miliao.com, and l iubei__immomoc is corresponding Email address liubei@immomo.com then broadly falls into source GUID.

Shadow code GUID also referred to as numeral GUID.The source GUID of non-shadow code also referred to as letter source GUID.

In the UCode of letter source GUID, containing letter, it is of course also possible to allow containing numeral.

It should be noted that in step 2401, the client of liubei@immomo.com sends migration request to HSvr-C Time, request can not also be carried any GUID value liubei@immomo.com to be migrated, and only carry correspondence CeSvrDesc value miliao.com, in order to indicate move target to be HSvr-A.

Correspondingly, in step 2402, after HSvr-C receives described migration request, from current account, determine GUID to be migrated Value.Due to the corresponding accounts of two bindings of current account: account that GUID value liubei@immomo.com is corresponding and superposition shadow Code account corresponding to GUID value 8613923568901@immomo.com, and alphabetical source GUID value corresponding to the two account is only GUID value liubei@immomo.com, therefore, using liubei@immomo.com as GUID value to be migrated, then such as Accounts information the exterior and the interior shown in table 4-B, is saved in liubei@immomo.com corresponding by CeSvrDesc value miliao.com In Account History.Such as, HSvr-C is according to GUID value liubei@immomo.com, from the accounts information table as shown in table 4-B In determine correspondence Account History, CeSvrDesc value miliao.com is saved in this record.

Such as, step 2401 is that the client of step 2401B:liubei@immomo.com is to HSvr-C transmission migration further Request, carries CeSvrDesc value miliao.com of correspondence, in order to indicate move target to be HSvr-A in request.Correspondingly, Step 2402 is that step 2402B:HSvr-C receives described migration request further, obtains in current binding account the most corresponding Letter source GUID value account number, obtains GUID value liubei@immomo.com；At the accounts information the exterior and the interior as shown in table 4-B, CeSvrDesc value miliao.com is saved in Account History corresponding to liubei@immomo.com.

In the middle of actual, the account setting up association or bundle relation can be with more than two.In this case, in step 2402B, The alphabetical source GUID value account number obtained may be more than one.In this case, in step 2403, in described migration request Multiple letter sources GUID value account number can be carried.Correspondingly, in 2404, can create multiple corresponding to letter source GUID value account Number migration account.And, it is also possible to by the multiple migration accounts corresponding to letter source GUID value account number created with created Described corresponding for superposition shadow code GUID account set up binding or incidence relation.

Especially, if set up in the account of association or bundle relation, it is also possible to there is the account moved into.

Such as, during Liu Bei Wei, have registered account with user name liuxuande in credulity, account number is liuxuande@yixin.im.Liu is standby set up Shu State after, for the ease of with the contact of acquaintance in Wei state, for Liuxuande@yixin.im creates migration account in footpath between fields, footpath between fields, and account address is Liuxuande__yixini@immomo.com, and the account account corresponding with GUID value liubei@immomo.com and Account corresponding for superposition shadow code GUID value 8613923568901@immomo.com establishes bundle relation.In this case, when Liu standby so that in three accounts of described binding, any one logins footpath between fields, footpath between fields after, if initiating the migration request chatted towards rice, then footpath between fields, footpath between fields Can also chat with rice and consult to realize further the migration for liuxuande@yixin.im.

Here, for GUID value liuxuande@yixin.im, after it is encoded, corresponding covers email address, territory For liuxuande__yixini."@" symbolic code " _ _ " in liuxuande__yixini is replaced back "@", and The default indicated value " i " of position, end is reverted to " im ", i.e. can get GUID value liuxuande yixin.im.

The mixing example application combined with aforementioned two kinds of embodiments below is illustrated.

Example 3.1: in HSvr-C, corresponding for GUID value liuxuande__yixini@immomo.com account, GUID value The account that account corresponding for liubei@immomo.com is corresponding with superposition shadow code GUID value 8613923568901@immomo.com Establish bundle relation.Liu is standby according to GUID value liuxuande__yixini@immomo.com or GUID value Liubei@immomo.com or superposition shadow code GUID value 8613923568901@immomo.com logins HSvr-C, is logining After, to file a request to HSvr-C and liubei@immomo.com is moved in HSvr-A, respective process is as follows:

Step 3101, the client of liubei@immomo.com send migration request to HSvr-C, carry correspondence in request CeSvrDesc value miliao.com, in order to indicate in HSvr-A to be moved to.

Step 3102, HSvr-C receive described migration request, obtain source account account number in current binding account, obtain letter source GUID value liubei@immomo.com；At the accounts information the exterior and the interior as shown in table 4-B, by CeSvrDesc value miliao.com It is saved in Account History corresponding to liubei@immomo.com；Obtain the account number of account of moving in current binding account, obtain GUID value liuxuande__yixini@immomo.com.

According to described CeSvrDesc value miliao.com, step 3103, HSvr-C determine that the MDSvr of correspondence is HSvr-A, in It is to send migration request to HSvr-A, request carries GUID value liuxuande__yixini@immomo.com and GUID The superposition shadow code GUID value 8613923568901@immomo.com's that value liubei@immomo.com is corresponding with binding account UCode part, i.e. communicating number 8613923568901.

After step 3104, described HSvr-A receive described migration request, according to GUID value liubei@immomo.com to be migrated Create and migrate account；One is produced together with covering email address, territory liuxuande__yixini and HCode value miliao.com Individual GUID value liuxuande__yixini@miliao.com, creates according to liuxuande__yixini@miliao.com and migrates Account, decodes according to liuxuande__yixini and obtains corresponding alphabetical source GUID value liuxuande@yixin.im, then, The HSvr-B pointed to HCode value yixin.im sends migration registration request, carries described GUID value in request Liuxuande@yixin.im, and one's own HCode value miliao.com is using the CeSvrDesc as this GUID； Obtain one according to described communicating number 8613923568901 together with one's own HCode value miliao.com to superpose Created two migration accounts are superposed shadow code GUID pair with described by shadow code GUID value 8613923568901@miliao.com The account answered sets up binding or incidence relation；

Step 3105, HSvr-B, after receiving described migration registration request, obtain described GUID value liuxuande@yixin.im With corresponding CeSvrDesc value miliao.com, determine the account of correspondence according to described GUID value liuxuande@yixin.im, In account determined by, the CeSvrDesc of registration liuxuande@yixin.im is miliao.com.

In step 3104, the GUID value liubei@immomo.com that described HSvr-A will migrate is encoded to cover territory email Address liubei__immomoc；Migration account is created according to described email address, the territory liubei__immomoc that covers, that is, This covering email address, territory liubei__immomoc as a user name to create migration account, this migration account is corresponding In territory, GUID is: by GUID value in the territory formed together with liubei__immomoc with CeSvrDesc value miliao.com liubei__immomoc@miliao.com。

In step 3104, if there is no 8613923568901 accounts corresponding for@miliao.com, it is also possible to create further Build 8613923568901 accounts corresponding for@miliao.com, perform the operation of described binding or incidence relation the most again.

In step 3104, if it is determined that there is migration corresponding to liuxuande__yixini@miliao.com in HSvr-A Account, the most no longer performs to create the operation of this migration account.

Configuring by implementing above-mentioned migration, user can seek the second communications service provider easily as backup services in the Internet Business, current service business's system malfunctions or collapse time, user can select in time second service business to provide communication service, Thus ensured the communication needs of user.

These are only better embodiment or the embodiment of the present invention, be not intended to limit protection scope of the present invention.All The spirit and principles in the present invention etc, any amendment made, improvement, equivalent etc. should be included in the protection model of the present invention Within enclosing.

Claims

1. a GUID migrates method to set up, it is characterised in that said method comprising the steps of:

Method the most according to claim 1, it is characterised in that in step a, the migration account created is interim account Family；Step a also includes: produce a dynamic password, and described dynamic password is saved in described holding account；Structure Make one and activate link, in this activation links, carry described dynamic password by parameter, this activation is linked by described GUID MSSvr, be sent to client corresponding to described GUID；Subsequently into activating responding process.

Method the most according to claim 1, it is characterised in that in step a, the migration account created is interim account Family；In step c, before performing the operation of CeSvrDesc of described registration GUID to be migrated, first according to this GUID Send and migrate license request, receive and migrate permission response, and after receiving described migration permission response, just perform described registration and want The operation of the CeSvrDesc of the GUID migrated；

Method the most according to claim 1, it is characterised in that in step a, the migration account created is interim account Family；In step c, before performing the operation of CeSvrDesc of described registration GUID to be migrated, obtain a messenger Code, produces a dynamic password, sends produced dynamic password according to described communicating number, waits the reply from MDSvr； Described method farther includes, and described MDSvr receives described dynamic password, and the dynamic password of reception is sent to described MSSvr； Described MSSvr is after receiving described dynamic password, it may be judged whether consistent with the dynamic password previously produced, if unanimously, just holds The operation of the CeSvrDesc of the GUID that the described registration of row is to be migrated, and send migration register response to described MDSvr；Described After MDSvr receives described migration register response, the holding account of described GUID is activated.

5. according to the method described in claim 1 or 2 or 3 or 4, it is characterised in that described MDSvr obtains corresponding communication Number, produces one according to described communicating number together with an one's own HCode and superposes shadow code GUID, by created Migrate account and set up binding or incidence relation with described account corresponding for superposition shadow code GUID.

Method the most according to claim 5, it is characterised in that described communicating number is that described MDSvr is obtaining and to migrate GUID time obtain.

Method the most according to claim 5, it is characterised in that described communicating number is to be obtained by described MSSvr, and Described migration register response is carried the described communicating number of acquisition；Described MDSvr obtains described from described migration register response Communicating number.

8. a GUID migrates method to set up, it is characterised in that said method comprising the steps of:

Method the most according to claim 8, it is characterised in that carry respective communication number in described migration request further；

Method the most according to claim 8, it is characterised in that carry respective communication number in described migration request further Code；In step c, produce one according to described communicating number together with an one's own HCode and superpose shadow code GUID, The migration account created is set up binding or incidence relation with described account corresponding for superposition shadow code GUID.