CN104954500A - Message addressing method based on semi-permanent address - Google Patents

Message addressing method based on semi-permanent address Download PDF

Info

Publication number
CN104954500A
CN104954500A CN201410116253.5A CN201410116253A CN104954500A CN 104954500 A CN104954500 A CN 104954500A CN 201410116253 A CN201410116253 A CN 201410116253A CN 104954500 A CN104954500 A CN 104954500A
Authority
CN
China
Prior art keywords
rsvr
message
gsvr
address
spaddr
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201410116253.5A
Other languages
Chinese (zh)
Other versions
CN104954500B (en
Inventor
王正伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to CN201410116253.5A priority Critical patent/CN104954500B/en
Publication of CN104954500A publication Critical patent/CN104954500A/en
Application granted granted Critical
Publication of CN104954500B publication Critical patent/CN104954500B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Abstract

The invention discloses a message addressing method based on a semi-permanent address, which is used for message addressing over service domains. According to the message addressing method, because a source RSvr can transmit a message to a random account in a random RSvr in other HSvrs through one GSvr in other HSvrs, a communication interface between a source RSvr and other HSvrs is simplified. The invention further discloses a message processing method for processing the message which comprises a destination SPAddr. The invention further discloses a reply message processing method which is used for processing a replay message that comes from the RSvr of the HSvr and comprises the destination SPAddr by the GSvr. The invention further discloses a message processing method for processing the message which comes from a client and comprises the destination SPAddr. The invention further discloses a resident identification method over the service domain for obtaining the RCode of one AccoAddr. The invention further discloses an HSvr.

Description

Based on the address messages method of semi-permanent address
Technical field
The present invention relates to internet communication, relate in the Internet between two service-domains or rather, based on the address messages method of semi-permanent address, and distributed HSvr.
Background technology
In internet communication, Radix Angelicae Sinensis belongs to an attribution server (HSvr, Home Server) user (IUsr, Internet User) quantity abundant time (such as, the QQ number of users of Tengxun reaches 700,000,000), or these user distributions are when a very large territorial scope, in order to improve service quality, usually, multiple child servers can be set, come to provide service to corresponding user respectively.
Such as, described HSvr comprises some child servers.According to GUID(whole world Unified Identity, Global Unified Identity) UCode(user code, User Code), according to certain mapping relations, the accounts information of all IUsr belonging to this HSvr is stored in different child servers respectively, and carrys out these accounts of addressing according to these mapping relations.See " a kind of method passing through the storage of data message key and read data information " patent of invention that application number is 02146090.6.
Described GUID can be an email address, also can be principal and subordinate's code, also can be a shadow code.About the more descriptions of GUID and HSvr, be " communication means and system " patent of invention of 201310037232.X see application number, and application number is " shadow code addressing method " patent of invention of 201310049772.X.
Each account has an account address (AccoAddr, Account Address), for account addressing.
The AccoAddr of the source account of a GUID is this GUID.
The AccoAddr of the migration account of a GUID is cross-domain address code (CDAddr, Cross-domain Address) corresponding to this migration account.This GUID is this base GUID(BaseGUID of this CDAddr, The Base GUID), ownership code (HCode, Home Code) being this migration account place HSvr across last HSvr information (CeSvrDesc, Cross-end HSvr Description) of this CDAddr.About more descriptions of HCode, see described " communication means and system " patent of invention.About more descriptions of CDAddr, be " supporting network and the related news processing method of GUID migration " patent of invention of 201310079118.3 see application number.
Each AccoAddr is made up of an address base (AddrBase, Address Base) and an address attribution (AddrHome, Address Home).When an AccoAddr is a GUID, the AddrBase of this AccoAddr is the UCode of this GUID, and the AddrHome of this AccoAddr is the HCode of this GUID; When an AccoAddr is a CDAddr, the AddrBase of this AccoAddr is the BaseGUID of this CDAddr, and the AddrHome of this AccoAddr is the CeSvrDesc of this CDAddr.Such as AccoAddr value liubei@163.com, corresponding AddrBase is liubei, and corresponding AddrHome is 163.com.
The HSvr of HSvr pointed by the AddrHome of this AccoAddr of an AccoAddr ownership.
The AddrHome of an account is the AddrHome of the AccoAddr of the account; The AddrBase of an account is the AddrBase of the AccoAddr of the account.
For Netease 163 user: UsrA and UsrB, the mapping relations arranged according to Netease, UsrA is mapped in Netease's Pekinese's child servers, and UsrB is mapped in the child servers in Netease Guangzhou.UsrC is Tengxun qq user, and the mapping relations arranged according to Tengxun, UsrC is mapped in the child servers in Tengxun Shanghai.
When UsrC sends message to UsrB, message according to access way nearby, may be sent to the child servers in Netease Nanjing by the child servers in Tengxun Shanghai.After the child servers in Netease Nanjing receives this message, according to the mapping relations of Netease, determine that UsrB is in the child servers in Netease Guangzhou, sends to the child servers in Netease Guangzhou by this message, then by the child servers in Netease Guangzhou, this message is sent to UsrB again.
Because the mapped relationship map of UsrB is in the child servers in Netease Guangzhou, although the user that UsrB is corresponding hangs up one's hat Beijing, when UsrB logs in the account of oneself at every turn, can only the child servers in remote access Netease Guangzhou.For described remote access, the roaming child servers of UsrB can be registered in the child servers in Netease Guangzhou.Like this, UsrB, when Beijing, can register the child servers of UsrB current roaming, i.e. Netease's Pekinese's child servers, and is saved in Netease's Pekinese's child servers by the accounts information of UsrB in the child servers in Netease Guangzhou.Like this, UsrB logins the account of oneself during in Beijing, just directly can login Netease's Pekinese's child servers.
Under in support, UsrB roams into Pekinese's situation, when UsrC sends message to UsrB, message, according to access way nearby, is sent to the child servers in Netease Nanjing by the child servers in Tengxun Shanghai.After the child servers in Netease Nanjing receives this message, according to the mapping relations of Netease, this message is sent to the child servers in Netease Guangzhou, the child servers in Netease Guangzhou judges that UsrB roams into Beijing, so, again this message is forwarded to Netease's Pekinese's child servers, by Netease's Pekinese's child servers, this message is sent to UsrB.Like this, just create the roundabout of message, thus affect message transmission efficiency.
The child servers in Netease Nanjing, after receiving described message, according to the mapping relations of Netease, also can be the roaming information inquiring about UsrB from the child servers in Netease Guangzhou, then sends message according to this roaming information.Such as, if UsrB does not roam, then the direct child servers described message being sent to Netease Guangzhou, sends to UsrB by the child servers in Netease Guangzhou by this message; If roaming, such as roam into Netease's Pekinese's child servers, then according to the route related information of the Netease's Pekinese's child servers obtained, directly described message is sent to Netease's Pekinese's child servers, by Netease's Pekinese's child servers, this message is sent to UsrB.Like this, also can affect message transmission efficiency, and affect the treatment effeciency of correlator server.
Roundabout or the roaming queries of message in sending for the above-mentioned message across between service-domain, on the impact that message transmission efficiency produces, be the message method proposed in " message method based on semi-permanent address " patent of invention of 201410098231.0 based on semi-permanent address at application number.The method first obtains the guard station code (RCode, Residence Code) corresponding to guard station server (RSvr, Residence Server) at object account place in object HSvr.When sending message to described object account, according to the semi-permanent address (SPAddr corresponding to the AccoAddr of this object account and described RCode, Semi-permanent Address) or semipermanent email address (SPEmailAddr, Semi-permanent email Address), this message is directly sent to the RSvr at this object account place, thus improve message transmission efficiency.
The SPAddr of an account comprises the two parts such as the RCode that the AccoAddr of the account and account place RSvr is assigned.A SPAddr can be write as (AccoAddr, RCode) form.
The HCode that HSvr has can be domain name, and an AccoAddr can be an email address.
Such as, the HCode that the HSvr of Netease has is domain name 163.com, and this HSvr comprises a guard station identified server (RIDSvr, Residence Identification Server) and four RSvr.Wherein, being positioned at Pekinese RSvr is RSvr-10, and the RSvr being positioned at Guangzhou is RSvr-20, and the RSvr being positioned at Shanghai is RSvr-21, and the RSvr being positioned at Chengdu is RSvr-28, and the RCode be assigned is respectively 10,20,21,28.At domain name system (DNS, Domain Name System) in, four domain names such as 10.163.com, 20.163.com, 21.163.com, 28.163.com are pointed to respectively the host IP address of these four RSvr, domain name 163.com is pointed to the host IP address of described RIDSvr.
The AccoAddr value of the account of Liubei is email address liubei@163.com, and the account is in RSvr-28.So the SPAddr value of the account of Liubei is exactly (liubei@163.com, 28).
In described RIDSvr, be 28 according to the RCode value that AccoAddr value liubei@163.com registers.
Machao needs to communicate with liubei for a long time.
This side of machao RSvr first resolves the domain name of AccoAddr value liubei 163.com, obtain the host IP address of described RIDSvr, send guard station to this RIDSvr and identify request, AccoAddr value liubei@163.com is carried in request, after described RIDSvr receives this message, finding RCode corresponding to AccoAddr value liubei 163.com is 28, RCode value 28 is replied to this side of machao.
Like this, this side of machao, when sending message to liubei, just can send message by the SPAddr value (liubei 163.com, 28) corresponding to AccoAddr value liubei 163.com and RCode value 28.Such as, resolve the domain name 28.163.com corresponding to SPAddr value (liubei@163.com, 28), obtain the IP address of RSvr-28, corresponding message is directly sent to RSvr-28.
Relevant more descriptions, see described " message method based on semi-permanent address " patent of invention.
When sending message according to an a SPAddr or SPEmailAddr, owing to needing to resolve the domain name corresponding to corresponding SPAddr or SPEmailAddr, to obtain the IP address of described object RSvr, therefore, in order to improve domain name resolution efficiency, usually, in local cache domain name mapping result, can use so that next.But, due in a HSvr, numerous RSvr may be there is, therefore, corresponding to message transmitter side, need the domain name mapping result of buffer memory to be multiplied, thus have influence on recall precision.
In addition, when sending message to from a HSvr proper account in each RSvr another HSvr, owing to being directly this message is sent to corresponding RSvr, therefore, the communication connection of setting up between two service-domains, may be needed to be multiplied.Such as, three RSvr such as RSvr-A10, RSvr-A25 and RSvr-A29 are had in the HSvr of Tengxun's service-domain, four RSvr such as RSvr-B10, RSvr-B20, RSvr-B21 and RSvr-B28 are had in the HSvr of Netease's service-domain, as shown in Figure 1, be connect instance graph between two HSvr, so, the communication connection of setting up may be needed between two service-domains will to reach 12.These 12 communication connections may can not exist simultaneously as early as possible, but the two ends of each connection, that corresponding is all different RSvr.Like this, be just unfavorable for the management of two HSvr interfaces, such as, the following communication security considered possibly between service-domain, prevents fraudster from accessing.
Summary of the invention
In view of this, the present invention discloses a kind of address messages method based on semi-permanent address, for across the address messages between service-domain.According to the method, because source RSvr arbitrary account can send message by a GSvr in other HSvr in arbitrary RSvr in other HSvr described, therefore, simplify the communication interface of described source RSvr and other HSvr described.
Based on an address messages method for semi-permanent address, the destination address of described message is SPAddr; The method comprises the following steps:
A, source RSvr determine object GSvr according to the HCode of the object SPAddr of message, and described message is sent to described object GSvr;
After b, described object GSvr receive described message, the RCode according to described SPAddr determines object RSvr, and described message is sent to described object RSvr, and the destination address of message comprises the AccoAddr of described SPAddr;
After step c, described object RSvr receive described message, determine target account according to described object AccoAddr.
A kind of message treatment method, for GSvr process from the message comprising object SPAddr of other HSvr or for the message that comprises object SPAddr of RSvr process from client, the method comprises the following steps:
A, determine object RSvr according to the RCode of described SPAddr;
B, described message is sent to described object RSvr, the destination address of message comprises the AccoAddr of described SPAddr.
A kind of reply message treatment method, for the reply message that comprises object SPAddr of GSvr process from the RSvr of this HSvr, the method comprises the following steps:
A, determine object RSvr according to the RSvrCompDesc of described SPAddr;
B, described reply message is sent to determined RSvr.
A kind of message treatment method, for the treatment of the message comprising object SPAddr from client, the method comprises the following steps:
A, source RSvr judge whether the HCode having described SPAddr, if not, the HCode according to described SPAddr determines object GSvr, and described message is sent to described object GSvr.
The described HCode according to described SPAddr determines that object GSvr further: the domain name corresponding to HCode of resolving described SPAddr, obtains the IP address of corresponding ARSvr; According to described IP address, send auxiliary analysis request to corresponding ARSvr, in request, carry GI data; After described ARSvr receives described auxiliary analysis request, according to the GI data of wherein carrying, obtain the IP address of corresponding GSvr, this IP address is replied to described request side; Described request side joint receives the IP address of described GSvr; Describedly send to described object GSvr to refer to described message, according to the IP address of described GSvr, send described message.
Across a guard station recognition methods for service-domain, for obtaining the RCode of an AccoAddr; The method comprises the following steps:
Object GSvr, according to the AddrHome of described AccoAddr, is determined in a, request side, source, and send guard station to described object GSvr and identify request message, the identification target of carrying in this request message is described AccoAddr;
After b, described object GSvr receive this message, this request message is sent to the RIDSvr of this HSvr;
After c, described RIDSvr receive described request message, according to described AccoAddr, obtain corresponding RCode;
D, described RIDSvr reply the RCode obtained to request side, source.
A kind of HSvr, comprises GSvr and RSvr; Each RSvr is assigned a RCode;
Described RSvr is for preserving corresponding accounts information;
Described GSvr receive from other HSvr comprise the message of object SPAddr after, determine corresponding RSvr according to the RCode of described SPAddr, described message is sent to determined RSvr, the destination address of message comprises the AccoAddr of described SPAddr;
Described RSvr receive from this HSvr GSvr comprise the message of object AccoAddr after, according to described object AccoAddr, determine target account.
Described RSvr receive from client comprise the message of object SPAddr after, judge whether the HCode having described SPAddr, if not, then enter cross-domain Message Processing flow process; Otherwise, enter Message Processing flow process in territory.
Described HSvr can further include RIDSvr, identifies service for providing guard station; Receive one at described RIDSvr to comprise and identify that the guard station of target identifies after request message, determine the RCode that this identification target is corresponding; Reply determined RCode.
Described HSvr comprises ARSvr further, for providing auxiliary analysis service;
Be provided with goal description record in described ARSvr, describe record at an objective and comprise the GI that is resolved target and correspondence; Described ARSvr, when receiving one and carrying the auxiliary analysis request of GI data, according to described GI data, determines to resolve target accordingly from described goal description record, gives auxiliary analysis request person by determined parsing target retro.
In the technical scheme that above-described embodiment provides, due to the communication interface of RSvr towards other HSvr can be simplified, therefore, simplify the process of RSvr, and be conducive to the management to different HSvr information interaction.
Accompanying drawing explanation
Shown in Fig. 1, be connect instance graph between two HSvr.
Shown in Fig. 2, it is the instance graph of the distributed HSvr of the present invention.
Shown in Fig. 3, it is the process chart comprising the message of object SPAddr from client.
Shown in Fig. 4, it is the embodiment flow process of the cross-domain address messages method based on semi-permanent address.
Shown in Fig. 5, be the HSvr providing guard station to identify service.
Shown in Fig. 6, for GSvr superposes the HSvr of RIDSvr.
Shown in Fig. 7, be the HSvr that RIDSvr and GSvr merges.
Shown in Fig. 8, for GSvr superposes the HSvr of HashSvr.
Shown in Fig. 9, be the HSvr that HashSvr and GSvr merges.
Shown in Figure 10, for identifying the HSvr of request message via the outer guard station of GSvr acceptance domain.
Shown in Figure 11, be the HSvr comprising multiple GSvr.
Shown in Figure 12, for RSvr superposes the HSvr of GSvr.
Shown in Figure 13, be the HSvr comprising GRSvr.
Shown in Figure 14, be the HSvr comprising ARSvr.
Shown in Figure 15, it is the HSvr networking diagram of special recommendation of the present invention.
Embodiment
For making the object of the invention, technical scheme and advantage clearly understand, below in conjunction with embodiment, be described in detail from many aspects.
The present invention is example with { HCode that HSvr has is a domain name, and an AccoAddr is an email address }, but is not used in restriction the present invention.
The present invention claims the AddrHome of the AccoAddr of a SPAddr to be HCode or AddrHome of this SPAddr.
The present invention proposes a kind of HSvr, described HSvr comprises critical point server (GSvr, GateWay Server) and guard station server (RSvr, Residence Server).The HCode of described GSvr and described RSvr is the HCode of this HSvr.
As shown in Figure 2, be the instance graph of the distributed HSvr of the present invention.In the figure, two HSvr:HSvr-A and HSvr-B are comprised.Wherein, HSvr-A comprises a GSvr:GSvr-A, and three RSvr: be positioned at Pekinese RSvr-A10, be positioned at the RSvr-A25 in Nanjing and be positioned at the RSvr-A29 in Xi'an; HSvr-B comprises a GSvr:GSvr-B, and four RSvr: be positioned at Pekinese RSvr-B10, be positioned at the RSvr-B20 in Guangzhou, be positioned at the RSvr-B21 in Shanghai and be positioned at the RSvr-B28 in Chengdu.
Wherein, the HCode of HSvr-A is the HCode of qq.com, HSvr-B is 163.com.
Corresponding accounts information is preserved in described RSvr.
The RSvr at the account place that AccoAddr is corresponding is the RSvr of this AccoAddr.
Usually, in the accounts information of an account, these attributes can be comprised: the AddrBase of AccoAddr or AccoAddr, Password, ClientIP and ClientPort, etc.Wherein, Password is the password of proper account, ClientIP and ClientPort is the online information of proper account.When an account be in login state time, the IP address of the client of corresponding ClientIP and the ClientPort corresponding account and port numbers; When the account be in publish state time, usually, corresponding ClientIP and/or ClientPort is null value null or 0, also can show as and not have corresponding online record.
Described RSvr can obtain the IP address and port numbers that log in client when an Account Logon, and is kept in ClientIP and the ClientPort attribute of the account in the IP address of acquisition and port numbers.
About more descriptions of accounts information see described " communication means and system " patent of invention.
Described RSvr can preserve the accounts information of proper account by accounts information table as shown in table 4.
Table 4
AccoAddr Password ClientIP ClientPort
liubei@163.com ******** Corresponding IP address Respective end slogan
xushu@163.com ******** Corresponding IP address Respective end slogan
If the port numbers of subscribed client, then in table 4, ClientPort part can be omitted.
Each RSvr is assigned a guard station code RCode, identifies a RSvr in corresponding HSvr.In fact, described RCode can as the ID of trace route path in a HSvr, in order to identify a RSvr in HSvr by the path of planning.
Described RCode can be a simply coding, such as: jing, guang, hu; Also can be the multiple subdomain strings coupled together by point, such as: shen.guang, guang.shen, 10.86,86.10, etc.; Or the path to be coupled together by back slash, such as, guang shen, 86 10, etc.Certainly, described RCode also can be the on-site landline telephone area code of corresponding RSvr, after as example, but be not used in restriction.
Below with { RCode of the RCode of the RCode of RSvr-A10 to be the RCode of 10, RSvr-A25 be 25, RSvr-A29 to be the RCode of 29, RSvr-B10 be 10, RSvr-B20 is the RCode of 20, RSvr-B21 is that the RCode of 21, RSvr-B28 is for 28 } for example.
The RCode of the RSvr of an AccoAddr is the RCode of this AccoAddr.
Described GSvr receive from other HSvr comprise the message of object SPAddr after, perform following flow process:
Step G11, determine object RSvr according to the RCode of described SPAddr.
Step G12, described message is sent to described object RSvr, the destination address of message comprises the AccoAddr of described SPAddr.
Usually, in step G12, send to the destination address of the described message of described object RSvr can be directly described SPAddr.
RSvr routing table in territory is set in described GSvr, for the address information (RSvrAddr, RSvr Address) of RSvr corresponding in register HSvr.See RSvr routing table in territory as shown in table 7:
Table 7
RCode RSvrAddr Remark
10 The RSvrAddr of RSvr-B10 Corresponding RSvr-B10
20 The RSvrAddr of RSvr-B20 Corresponding RSvr-B20
21 The RSvrAddr of RSvr-B21 Corresponding RSvr-B21
28 The RSvrAddr of RSvr-B28 Corresponding RSvr-B28
In table 7, the RSvrAddr of this RSvr is registered according to the RCode of a RSvr.
Described step G11 is step G11A further: according to the RCode of described SPAddr, according to RSvr routing table in territory as shown in table 7, determines the RSvrAddr of object RSvr.Correspondingly, described step G12 is step G12A further: according to determined RSvrAddr, and described message is sent to described object RSvr, and the destination address of message comprises the AccoAddr of described SPAddr.
Here, described RSvrAddr can be the communication link number of described GSvr towards corresponding RSvr, the socket descriptor (SktD, Socket Descriptor) that also can be described GSvr connect towards the TCP of corresponding RSvr.
In the present invention's all descriptions below, be example with { described RSvrAddr is the IP address of corresponding RSvr, and arranges unified port numbers }, but be not used in restriction.
Described step G11 is step G11B further: according to the RCode of described SPAddr, according to RSvr routing table in territory as shown in table 7, determines the IP address of object RSvr.Correspondingly, described step G12 is step G12B further: according to the port numbers of determined IP address and agreement, described message is sent to described object RSvr, and the destination address of message comprises the AccoAddr of described SPAddr.
The present invention also describes (RSvrCompDesc, RSvr Complete Description) completely with a RSvr and comes to identify a RSvr in the Internet.Described RSvrCompDesc comprises HCode and RCode two parts information, can be write as (HCode, RCode) form.Wherein the HCode of this RSvrCompDesc is the HCode of corresponding RSvr, the RCode of this RSvrCompDesc is the RCode of corresponding RSvr.
Corresponding domain name can be produced according to a RSvrCompDesc.More descriptions, see described " message method based on semi-permanent address " patent of invention.The present invention is example using { mode producing domain name according to a RSvrCompDesc is: by the RCode of this RSvrCompDesc as a subdomain, produce the subdomain name of this HCode together with the HCode of this RSvrCompDesc }.For RSvrCompDesc value (163.com, 21), using 21 as a subdomain, before being inserted into domain name 163.com, obtain the subdomain name 21.163.com of domain name 163.com, the domain name that namely RSvrCompDesc value (163.com, 21) is corresponding.
HCode containing a RSvrCompDesc, this RSvrCompDesc in a SPAddr is the RCode of the HCode of this SPAddr, this RSvrCompDesc is the RCode of this SPAddr.Such as, a SPAddr is (liubei@163.com, 10), and the RSvrCompDesc of this SPAddr is (163.com, 10).
The present invention claims the domain name corresponding to RSvrCompDesc of a RSvr to be the domain name of this RSvr.
The described RCode according to a RSvr registers the RSvrAddr of this RSvr, can be the IP address of registering this RSvr according to the domain name of this RSvr further.See such as showing RSvr routing table in the territory shown in 7A:
Table 7A
Domain name IP address Remark
10.163.com The IP address of RSvr-B10 Corresponding RSvr-B10
20.163.com The IP address of RSvr-B20 Corresponding RSvr-B20
21.163.com The IP address of RSvr-B21 Corresponding RSvr-B21
28.163.com The IP address of RSvr-B28 Corresponding RSvr-B28
Described step G11B is step G11C further: according to the domain name corresponding to the RSvrCompDesc of described SPAddr, according to such as showing RSvr routing table in the territory shown in 7A, determines the IP address of object RSvr.
Especially, after a RSvr disposes, the domain name of this RSvr can be pointed to the IP address of this RSvr in corresponding DNS.Like this, in step G11C, when object IP address cannot be determined from described routing table, IP address corresponding to domain name can also be obtained by access far-end dns server, and by RSvr routing table in the territory that is cached to the analysis result of this domain name as shown in table 7A.In this case, in the territory as shown in table 7A, in fact RSvr routing table can be the cache table of a domain name mapping result in this locality.In this case, described step G11C is actually a domain name resolution process: the domain name corresponding to RSvrCompDesc of resolving described SPAddr, obtains the host IP address of RSvr pointed by this domain name.Correspondingly described step G12B is: according to the port numbers of resolving IP address and the agreement obtained, described message is sent to corresponding RSvr, and the destination address of message comprises the AccoAddr of described SPAddr.Because domain name mapping is ripe application technology, therefore, repeat no more here.
Such as, the object SPAddr that comprises that described GSvr receives from other HSvr is (liubei@163.com, 21) after message, according to the RSvrCompDesc value (163.com of this SPAddr, 21) the domain name 21.163.com corresponding to, according to such as showing RSvr routing table in the territory shown in 7A, determining the IP address of object RSvr, obtaining the IP address of RSvr-B21; Described GSvr is according to the port numbers of the IP address obtained and agreement, and send described message to RSvr-B21, the destination address of message comprises the AccoAddr value liubei 163.com of described SPAddr.
Described RSvr receive from GSvr in this HSvr comprise the message of object AccoAddr after, perform following flow process:
Step R01, according to described object AccoAddr, determine target account.
Like this, just step R09 can be performed: described message is ended in described target account.
Such as, described message is for sending a short message to target account, then described this target account that this message ended in can be the client this short message being sent to this target account.
In step R01, described RSvr, when determining target account, directly terminates.Before described end, can also reply to the source address side of message the reply message representing " target account does not exist " further.
The present invention proposes a kind of message treatment method, for the treatment of the message comprising object SPAddr from client.
As shown in Figure 3, be the process chart comprising the message of object SPAddr from client.
Described RSvr receive from client comprise the message of object SPAddr after, perform following flow process:
Step R21, described RSvr judge whether the HCode having described SPAddr, if not, then enter the cross-domain Message Processing flow process of step R22 to step R23; Otherwise, Message Processing flow process in the territory entering step R24 to step R27.
Usually, can preserve its HCode had in RSvr, like this, RSvr can judge whether a certain HCode is had by oneself.
Described step R22 is: the HCode according to described SPAddr determines object GSvr.
Described step R23 is: described message is sent to described object GSvr.Here, the destination address of message comprises described SPAddr.
Overseas GSvr routing table is set in described RSvr, for the address information (GSvrAddr, GSvr Address) of the overseas GSvr that register RSvr is correlated with.See overseas GSvr routing table as shown in table 8, wherein save the overseas GSvr routing table data in RSvr-B10.
Table 8
HCode GSvrAddr Remark
qq.com The GSvrAddr of GSvr-A Corresponding GSvr-A
gmail.com The GSvrAddr of GSvr-C Corresponding GSvr-C
In table 8, the GSvrAddr of this GSvr is registered according to the HCode of a GSvr.Wherein, GSvr-C is the GSvr in HSvr-C.Here, take HSvr-C as the instantaneous communication system of Google be example.
Described step R22 is step R22A further: according to the HCode of described SPAddr, according to overseas GSvr routing table as shown in table 8, determines the GSvrAddr of object GSvr.
Correspondingly, described step R23 is step R23A further: according to determined GSvrAddr, and described message is sent to described object GSvr.Here, the destination address of described message comprises described SPAddr.
Described GSvrAddr can be the communication link number of described RSvr towards corresponding GSvr, the SktD that also can be described RSvr connect towards the TCP of corresponding GSvr.
In the present invention's all descriptions below, be example with { described GSvrAddr is the IP address of corresponding GSvr, and arranges unified port numbers }, but be not used in restriction.
Described step R22 is step R22B further: according to the HCode of described SPAddr, according to RSvr routing table in territory as shown in table 8, determines the IP address of object GSvr.
Correspondingly, described step R23 is step R23B further: according to the port numbers of determined IP address and agreement, described message is sent to corresponding GSvr.Here, the destination address of described message comprises described SPAddr.
Especially, after a GSvr disposes, the domain name corresponding to the HCode of this GSvr can be pointed to the IP address of this GSvr in corresponding DNS.Like this, the cross-domain Message Processing flow process of described step R22 to step R23 is the cross-domain Message Processing flow process of following step R22-1 to step R23B further:
Step R22-1, HCode according to described SPAddr, according to overseas GSvr routing table as shown in table 8, determine the IP address of object GSvr, judge whether to determine, if so, then perform described step R23B; Otherwise, perform step R22-2: access far-end dns server obtains the IP address corresponding to the corresponding domain name of HCode of described SPAddr, and by being cached to the analysis result of this domain name in overseas GSvr routing table as shown in table 8, then perform described step R23B.
In this case, in fact overseas GSvr routing table as shown in table 8 can be the cache table of a domain name mapping result in this locality.In this case, described step R22-1 to step R22-2 is actually a domain name resolution process: the domain name corresponding to HCode of resolving described SPAddr, obtain the host IP address of the GSvr pointed by this domain name, this process also comprises this analysis result of buffer memory.Because domain name mapping is ripe application technology, therefore no longer report here.
Especially, when domain name corresponding for the HCode of a GSvr being pointed to the host IP address of this GSvr in corresponding DNS, Extensive domain name analysis configuration can also be carried out.Like this, just according to the domain name of arbitrary RSvr in HSvr belonging to this GSvr, object GSvr can be determined, thus the GSvr come to correspondence sends message.Like this, when described SPAddr is a SPEmailAddr, the host IP address of corresponding GSvr can be obtained by the domain name of directly resolving this SPEmailAddr, and do not need the domain name of the AccoAddr first obtaining this SPEmailAddr, then resolve this domain name again to obtain the host IP address of corresponding GSvr.
Described step R24 is: described RSvr judges whether the RCode of described SPAddr points to oneself, if so, then performs step R25; Otherwise, enter the flow process of step R26 to step 27.
Usually, can preserve its RCode be assigned in RSvr, like this, RSvr can judge whether a certain RCode points to oneself.
Described step R25 is: directly determine target account according to the AccoAddr of described SPAddr, then terminate.Like this, just this message can be ended in described target account.
Described step R26 is: the RCode according to described SPAddr determines object RSvr.
Described step R27 is: described message is sent to described object RSvr, and the destination address of message comprises the AccoAddr of described SPAddr.
RSvr routing table in territory is set in RSvr, for the RSvrAddr of other RSvr in register HSvr.See such as showing RSvr routing table in the territory shown in 7-1, RSvr routing table data in the territory wherein saving RSvr-B10.
Table 7-1
RCode RSvrAddr Remark
20 The IP address of RSvr-B20 Corresponding RSvr-B20
21 The IP address of RSvr-B21 Corresponding RSvr-B21
28 The IP address of RSvr-B28 Corresponding RSvr-B28
In the table, the IP address of this RSvr is registered according to the RCode of a RSvr.Here, the respective end slogan of unified agreement RSvr.
Described step R26 is step R26B further: according to the RCode of described SPAddr, according to such as showing RSvr routing table in the territory shown in 7-1, determines the IP address of corresponding RSvr.Correspondingly, described step R27 is step R27B further: according to the port numbers of determined IP address and agreement, described message is sent to corresponding RSvr, and the destination address of message comprises the AccoAddr of described SPAddr.
Such as, in step R26, described SPAddr value is (liubei@163.com, 21), described RSvr, according to the RCode value 21 of this SPAddr, from such as showing the IP address obtaining object RSvr in the territory shown in 7-1 RSvr routing table, obtains the IP address of RSvr-B21; In step R27, according to the port numbers of the IP address obtained and agreement, send described message to RSvr-B21, the destination address of message can be the AccoAddr value liubei 163.com of described SPAddr.
When registering the IP address of this RSvr according to the RCode of a RSvr, also can be the IP address of registering this RSvr according to the domain name of this RSvr further.See such as showing RSvr routing table in the territory shown in 7-1A:
Table 7-1A
Domain name IP address Remark
20.163.com The IP address of RSvr-B20 Corresponding RSvr-B20
21.163.com The IP address of RSvr-B21 Corresponding RSvr-B21
28.163.com The IP address of RSvr-B28 Corresponding RSvr-B28
Described step R26B is step R26C further: according to the domain name corresponding to the RSvrCompDesc of described SPAddr, according to such as showing RSvr routing table in the territory shown in 7-1A, determines the IP address of object RSvr.
Equally, after a RSvr disposes, the domain name of this RSvr can be pointed to the IP address of this RSvr in corresponding DNS.Like this, in step R26C, when the IP address of correspondence cannot be determined according to domain name from described routing table, IP address corresponding to domain name can also be obtained by access far-end dns server, and by RSvr routing table in the territory that is cached to the analysis result of this domain name as shown in table 7-1A.In this case, in the territory as shown in table 7-1A, in fact RSvr routing table can be the cache table of a domain name mapping result in this locality.
The present invention proposes a kind of address messages method based on semi-permanent address, and for the address messages across service-domain, the destination address of described message is SPAddr.
As shown in Figure 4, be the embodiment flow process of the address messages method based on semi-permanent address, in the figure:
First object GSvr is determined in step 101, source RSvr according to the HCode of the object SPAddr of message.See step R22, no longer repeat here.
Described message is sent to described object GSvr by step 102, described source RSvr.Here, the destination address of message comprises described SPAddr.See step R23, no longer repeat here.
After step 103, described object GSvr receive described message, the RCode according to described SPAddr determines object RSvr.See step G11, no longer repeat here.
Described message is sent to described object RSvr by step 104, described object GSvr, and the destination address of message comprises the AccoAddr of described SPAddr.See step G12, no longer repeat here.
After step 105, described object RSvr receive described message, determine target account according to described object AccoAddr.See step R01, no longer repeat here.
Like this, described message just can be ended in described target account by described object RSvr.See described step R09, no longer repeat here.
As from the foregoing, arbitrary RSvr in HSvr-A, such as RSvr-A29 arbitrary account will send message in HSvr-B, only needs the SPAddr comprising proper account at the destination address of this message, and this message is sent to GSvr-B.Like this, just greatly simplifie the interface of RSvr-A29 and HSvr-B, thus simplify the process of RSvr-A29.
Described RSvr receive from other RSvr in this HSvr comprise the message of object AccoAddr after, also can perform step R01, and further perform step R09.
Described HSvr can further include RIDSvr, identifies service for providing guard station.
In RIDSvr, the corresponding relation of AccoAddr and RCode can be set up, so that corresponding RCode can be obtained according to an AccoAddr.
About the corresponding relation how setting up AccoAddr and RCode, there is various ways, see described " message method based on semi-permanent address " patent of invention.Here wherein a kind of mode of only collecting supplies technical staff's reference: set up roaming table, in this roaming table, preserves the RCode of correspondence according to AccountAddr.
Receive one at described RIDSvr to comprise and identify that the guard station of target identifies after request message, according to described corresponding relation, determine the RCode that this identification target is corresponding; Reply determined RCode.Usually, described identification order table is an AccoAddr.
About more descriptions of RIDSvr, see described " message method based on semi-permanent address " patent of invention, no longer select here.As shown in Figure 5, the HSvr for providing guard station to identify service.This HSvr comprises a RIDSvr, a GSvr:GSvr-B, four RSvr:RSvr-B10, RSvr-B20, RSvr-B21, RSvr-B28.
Described RIDSvr and described GSvr can be deployed in same server, and in this case, described RIDSvr and described GSvr can arrange to use different port numbers.As shown in Figure 6, for GSvr superposes the HSvr of RIDSvr.This HSvr comprises a RIDSvr, a GSvr:GSvr-B, four RSvr:RSvr-B10, RSvr-B20, RSvr-B21, RSvr-B28.Wherein, RIDSvr and GSvr-B is deployed in same station server.
Described RIDSvr and described GSvr also can be merged into same server, i.e. critical point-guard station identified server (GRIDSvr, GateWay Residence Identification Server).As shown in Figure 7, be the HSvr of RIDSvr and GSvr merging.This HSvr comprises a GRIDSvr:GRIDSvr-B, four RSvr:RSvr-B10, RSvr-B20, RSvr-B21, RSvr-B28.Wherein, GRIDSvr realizes the function of RIDSvr and GSvr simultaneously.
Described RIDSvr can be a distributed RIDSvr, and such as, this RIDSvr comprises a hash server (HashSvr, Hash Server), three roaming queries servers (QSvr, Roam Query Server): QSvr1, QSvr2, QSvr3.
The HCode of described HashSvr and described QSvr is the HCode of this RIDSvr, is also the HCode of this HSvr.
Described HashSvr identifies request message for receiving guard station.That is, described RIDSvr receives guard station by described HashSvr and identifies request message.
Roaming sublist is set in corresponding QSvr, for preserving corresponding RCode according to corresponding AccoAddr.
Set up the mapping relations of AccoAddr and QSvr, so that according to an AccoAddr, according to set up mapping relations, corresponding QSvr can be determined.This QSvr is the QSvr that this AccoAddr maps, and is called for short the QSvr of this AccoAddr.
According to the mapping relations of AccoAddr and the QSvr set up, corresponding QSvr can be determined according to an AccoAddr.Like this, just in the roaming sublist of this QSvr, corresponding RCode can be preserved according to this AccoAddr.
Receive one at corresponding HashSvr to comprise and identify that the guard station of target identifies after request message, perform following flow process:
Step S31, described HashSvr, according to described identification target, according to the mapping relations of set up AccoAddr and QSvr, determine corresponding QSvr; The query messages comprising described identification target is sent to this QSvr.
After step S32, described QSvr receive described query messages, according to described identification target, from roaming sublist, search corresponding RCode; Judge whether to find, if found, then by response to query message, this RCode is sent to described HashSvr; Otherwise, by response to query message, RCode value 0 is sent to described HashSvr.
After step S33, described HashSvr receive described response to query message, reply the RCode received to described request side.
Here, RCode value 0 is considered as invalid RCode value.
Usually, described identification target is an AccoAddr.
About more descriptions of described distributed RIDSvr, described HashSvr and QSvr, see described " message method based on semi-permanent address " patent of invention, no longer select here.
Especially, for distributed RIDSvr, corresponding HashSvr and described GSvr can be deployed in same server, and in this case, described HashSvr and described GSvr can arrange to use different port numbers.As shown in Figure 8, for GSvr superposes the HSvr of HashSvr.This HSvr comprises a distributed RIDSvr, a GSvr:GSvr-B, four RSvr:RSvr-B10, RSvr-B20, RSvr-B21, RSvr-B28.Wherein, RIDSvr comprises a HashSvr, three QSvr:QSvr1, QSvr2, QSvr3; HashSvr and GSvr-B is deployed in same station server.
Equally, described HashSvr and described GSvr also can be merged into same server, i.e. critical point-Hash server (GHSvr, GateWay Hash Server).As shown in Figure 9, be the HSvr of HashSvr and GSvr merging.This HSvr comprises a GHSvr:GHSvr-B, four RSvr:RSvr-B10, RSvr-B20, RSvr-B21, RSvr-B28.Three QSvr:QSvr1, QSvr2, QSvr3; Wherein, GHSvr-B, except realizing GSvr function, also realizes the function of a distributed RIDSvr together with three QSvr.
Described RIDSvr can receive guard station via GSvr and identify request message.Correspondingly, for distributed RIDSvr, described HashSvr receives guard station via GSvr and identifies request message.
As shown in Figure 10, for identifying the HSvr of request message via the outer guard station of GSvr acceptance domain.This HSvr comprises a RIDSvr, a GSvr:GSvr-B, four RSvr:RSvr-B10, RSvr-B20, RSvr-B21, RSvr-B28.Wherein, the guard station from other HSvr identifies request message, all sends to RIDSvr via GSvr-B.
Described RSvr receive from client comprise the message of object AccoAddr after, obtain the RCode of described AccoAddr, the RCode of acquisition sent to described client.
When example one, RSvr needs the RCode of an acquisition AccoAddr, if judge that the AddrHome of this AccoAddr is not by oneself is had, then according to the AddrHome of this AccoAddr, determine object GSvr, send guard station to described object GSvr and identify request message, the identification target of carrying in this message is an AccoAddr; After described object GSvr receives this message, this message is sent to the RIDSvr of this HSvr to process.
In this case, described RIDSvr, according to described identification target, determines corresponding RCode, recognition result is directly replied to described RSvr, or via described object GSvr, recognition result is replied to described RSvr.
When example two, RSvr needs the RCode of an acquisition AccoAddr, if judge the AddrHome oneself having this AccoAddr, GSvr then directly to this HSvr sends guard station identification request message, after described GSvr receives this message, this message is sent to the RIDSvr of this HSvr to process.
In this case, recognition result can directly be sent to described RSvr by described RIDSvr, also by described GSvr, recognition result can be sent to described RSvr.
Usually, when a RSvr needs the RCode of an acquisition AccoAddr, if judge the AddrHome oneself having this AccoAddr, then direct this message is sent to the RIDSvr of this HSvr to process.
About the RCode how obtaining an AccoAddr, and about RIDSvr how to process guard station identify request message, etc. more descriptions, see associated description in described " message method based on semi-permanent address " patent of invention, no longer select here.
Can have multiple equivalent G Svr in a HSvr, to realize load sharing, thus the scale contributing to realizing HSvr is disposed.Such as, these equivalent G Svr, or backup each other, or mirror image each other, or select one of them to be GSvr main frame, remaining is GSvr mirror image, or except deployed environment difference, other identical GSvr.As shown in figure 11, be the HSvr comprising multiple GSvr.Three GSvr:GSvr-B1, GSvr-B2, GSvr-B3 are comprised at this HSvr, and four RSvr:RSvr-B10, RSvr-B20, RSvr-B21, RSvr-B28.
Certainly, also a GSvr and RSvr can be deployed in a server.As shown in figure 12, for RSvr superposes the HSvr of GSvr.Three GSvr, four RSvr are comprised at this HSvr.Wherein, GSvr-B1 and RSvr-B10 is deployed in same server, GSvr-B2 and RSvr-B20 is deployed in same server, GSvr-B3 and RSvr-B21 is deployed in same server.
When a GSvr and RSvr is deployed in same server, this GSvr receive from other HSvr comprise the message of object SPAddr after, before the flow process performing step G11 to step G12, first judge whether the RCode of this SPAddr points to local RSvr, if, then direct this message is sent to local RSvr, then terminate; Otherwise, just perform the flow process of step G11 to step G12.
Especially, a GSvr can be merged in a RSvr.The RSvr incorporating GSvr is called guard station, critical point server (GRSvr, GateWay-Residence Server) by the present invention.
As shown in figure 13, be the HSvr comprising GRSvr.In this HSvr, comprise three GRSvr:GRSvr-B10, GRSvr-B20 and GRSvr-B21, and a RSvr:RSvr-B28.
Described GRSvr receive from other HSvr comprise the message of object SPAddr after, before sending message according to described SPAddr, first judge whether the RCode of this SPAddr points to oneself, if, then the direct AccoAddr according to this SPAddr determines target account in this locality, then terminates; Otherwise, just perform the flow process of step G11 to step G12.Before described end, described message can be ended in local described target account.
Coming Anywhere in the Internet can dispose the GSvr of described multiple equivalence respectively, such as, described multiple equivalent G Svr can be disposed respectively in local and/or high in the clouds.Usually, each GSvr can be disposed according to region, such as, dispose GSvr-B1 in Beijing of North China, dispose GSvr-B2 in the Nanjing of East China, dispose GSvr-B3 in the Wuhan of Central China.
Correspondingly, in DNS system, carry out intelligently parsing configuration, make when the domain name corresponding to the HCode to this GSvr is resolved, can according to domain name mapping request from different geographical, be resolved to the host IP address of different GSvr respectively.Such as, the HCode of HSvr is 163.com, in corresponding DNS, 163.com is pointed to simultaneously the host IP address of multiple equivalent G Svr of this HSvr.After corresponding dns server receives the analysis request about domain name 163.com, with the IP address (IPrequester of domain name mapping requestor, Requester IP) mate multiple IP addresses corresponding to domain name 163.com, determine optimum Match person, the IP address of optimum Match is returned to domain name mapping requestor as analysis result.The described optimum Match person of determination is that the IP address that IPrequester described in chosen distance is nearest, determines the distance of two IP addresses here for the difference of two IP addresses from the multiple IP addresses corresponding to domain name 163.com.More descriptions, see domain name intelligently parsing method in described " message method based on semi-permanent address " patent of invention, no longer select here.
Like this, can to realize a domain name mapping according to the network segment at requestor place in configured different IP addresses.
Especially, described HSvr can further include auxiliary resolution server (ARSvr, Auxiliary Resolution Server), for providing auxiliary analysis service.The HCode of described ARSvr is the HCode of this HSvr.
As shown in figure 14, be the HSvr comprising ARSvr.An ARSvr:ARSvr-B is comprised, three GSvr:GSvr-B1, GSvr-B2, GSvr-B3 at this HSvr, and four RSvr:RSvr-B10, RSvr-B20, RSvr-B21, RSvr-B28.
Goal description record is provided with in described ARSvr.Describe record at an objective and comprise the geography information (GI, Geographic Information) that is resolved target and correspondence.
Described ARSvr, when receiving one and carrying the auxiliary analysis request of GI data, according to described GI data, determines to resolve target accordingly from described goal description record, gives auxiliary analysis request person by determined parsing target retro.
Described parsing target is an IP address, or another one domain name or another name, or other.Be an IP address for described parsing target below, but be not used in restriction the present invention.
Certain any longitude and latitude data instance with described GI.A goal description record comprises an IP address and corresponding longitude and latitude data.See such as showing the IP address descriptor table shown in 1-8:
Table 1-8
IP Longitude Latitude Remark
The IP address of GSvr-B1 Corresponding longitude data Corresponding latitude data
The IP address of GSvr-B1 Corresponding longitude data Corresponding latitude data
The IP address of GSvr-B1 Corresponding longitude data Corresponding latitude data
Describedly from described goal description record, determine that resolving target is accordingly according to corresponding longitude and latitude data further according to described GI data, from such as showing to determine preferably IP address the IP address descriptor table shown in 1-8.Describedly determine that preferably IP address can be determine nearest IP address, after as example.
After described ARSvr disposes, just in corresponding DNS, the domain name corresponding to the HCode of this ARSvr can be pointed to the IP address of this ARSvr.Here the port numbers of unified agreement ARSvr.
Described step R22-2 is further: access dns server obtains the IP address corresponding to the corresponding domain name of HCode of described SPAddr; According to the port numbers of this IP address and agreement, send auxiliary analysis request to corresponding ARSvr, carry corresponding longitude and latitude data in request, such as, carry the longitude and latitude data of the current present position of auxiliary analysis request person; After described ARSvr receives described auxiliary analysis request, the longitude and latitude data entrained by it, from such as showing to determine nearest IP address the IP address descriptor table shown in 1-8, reply to auxiliary analysis request side by described nearest IP address; Described auxiliary analysis request side is by described auxiliary analysis result, and namely domain name and described nearest IP address, be saved in overseas GSvr routing table as shown in table 8, then perform described step R23B.
Describedly determine that nearest IP address is: the IP address searching from the IP address descriptor table as shown in table 1-8: the longitude and latitude data of its correspondence and as described in the longitude and latitude data of carrying in auxiliary analysis request through calculating, the distance obtained is the shortest.
Described GI also can be area information (AI, Area Information), such as, divides zones of different according to country.Country code (the TCC of country can be used, Telecom Country Code) identify a country, such as, Chinese TCC is 86, the TCC of Japan is 81, the TCC of Korea S is 82, the TCC of Vietnam is 84, the TCC of Laos is 856, the TCC in Taiwan is 886.
In this case, described AI comprises corresponding TCC value.See such as showing the IP address descriptor table shown in 1-1:
Table 1-1
IP AI Remark
The IP address of China GSvr 86
The IP address of Japan GSvr 81
The IP address of Korea S GSvr 82
The IP address of Vietnam GSvr 84、856 TCC value 84 and 856 is all pointed to Vietnam Server
The IP address of Taiwan GSvr 886
In table 1-1, for the IP address of Vietnam GSvr, in corresponding A I, include TCC value 84 and 856, namely represent the region overlay Vietnam corresponding to IP address and Laos two countries of Vietnam GSvr.
Describedly from described goal description record, determine that resolving target is accordingly according to corresponding AI data further according to described GI data, from such as showing the IP address of searching coupling the IP address descriptor table shown in 1-1.
Described step R22-2 is further: access dns server obtains the IP address corresponding to the corresponding domain name of HCode of described SPAddr; According to the port numbers of this IP address and agreement, the ARSvr to correspondence sends auxiliary analysis request, carries corresponding TCC value in request, such as, carries the TCC value in the current residing national or region of auxiliary analysis request person; After described ARSvr receives described auxiliary analysis request, the TCC value entrained by it, from such as showing the IP address of searching coupling the IP address descriptor table shown in 1-1, replies to auxiliary analysis request side by the IP address of described coupling; Described auxiliary analysis request side is by described auxiliary analysis result, i.e. the IP address of domain name and described coupling, is saved in overseas GSvr routing table as shown in table 8, then performs described step R23B.
By described ARSvr, according to geographical distribution, access dispatching can be carried out to the RSvr be linked in other HSvr of each GSvr in this HSvr, can the load of each GSvr in this HSvr of Effective Regulation.
About ARSvr, goal description record, and more descriptions of corresponding auxiliary analytic method, be " auxiliary analytic method " patent of invention of 201410020948.3 see application number.Here repeat no more.
Purposes of the present invention and usage is shown below by an integrated embodiment.
As shown in figure 15, be the HSvr networking diagram of special recommendation of the present invention.An ARSvr:ARSvr-B is comprised, a distributed RIDSvr, three GSvr:GSvr-B1, GSvr-B2, GSvr-B3 at this HSvr, and four RSvr:RSvr-B10, RSvr-B20, RSvr-B21, RSvr-B28.Wherein, described RIDSvr comprises three HashSvr:HashSvr1, HashSvr2, HashSvr3, two QSvr:QSvr1, QSvr2; HashSvr1 and GSvr-B1 is deployed in same station server, and HashSvr2 and GSvr-B2 is deployed in same station server, and HashSvr3 and GSvr-B3 is deployed in same station server.The HCode that this HSvr has is 163.com.
GSvr-B1 is positioned at Beijing, and GSvr-B2 is positioned at Shanghai, and GSvr-B3 is positioned at Chongqing.
In corresponding DNS, domain name 163.com is pointed to the IP address of this ARSvr-B.
In ARSvr-B, the IP address descriptor table as shown in table 1-8 is set, registers the IP address of GSvr-B1, GSvr-B2, GSvr-B3 etc. in the table respectively, and the longitude and latitude data of correspondence.
In each GSvr, according to the RCode of RSvr-B10, RSvr-B20, RSvr-B21, RSvr-B28 etc., register corresponding IP address.See RSvr routing table in territory as shown in table 7.
The mapping relations setting up AccoAddr and QSvr are: the ASCII value of the lowercase that the initial of the AddrBase of an AccoAddr is corresponding is odd number, then this AccoAddr corresponds to QSvr1, otherwise this AccoAddr corresponds to QSvr2.Such as, Liubei has an AccoAddr value to be the account of liubei@163.com.Because the ASCII value of the initial l of liubei@163.com is 108, be even number, therefore, liubei@163.com corresponds to QSvr2.
Roaming sublist is set in QSvr1 and QSvr2, for registering the RCode corresponding to corresponding AccoAddr respectively.Such as, because liubei marries into and lives with the bride's family in Wu, its account data is migrated in RSvr-21.Like this, in QSvr2, register corresponding RCode value 21, in order to point to RSvr-B21 according to AccoAddr value liubei@163.com.
The machao always guarded the frontier will communicate with liubei often.The AccoAddr value of machao account is machao@qq.com, the account data be in RSvr-A29, corresponding SPAddr is (machao@qq.com, 29).
Show how machao communicates with liubei below in two steps.
The first step, obtains the RCode value that liubei@163.com is corresponding, see following flow process:
First in step 501, this side of machao RSvr, i.e. RSvr-A29, first resolve the domain name of AccoAddr value liubei 163.com, obtain the IP address of ARSvr-B; According to the port numbers of described IP address and agreement, send auxiliary analysis request to ARSvr-B, in request, carry the longitude and latitude data of this side of machao RSvr.
Such as, RSvr-A29 receive machao client send comprise identify target be AccoAddr value liubei@163.com guard station identification request message after, start to perform step 501, to start guard station identification process.
After step 502, ARSvr-B receive described auxiliary analysis request, according to the longitude and latitude data of wherein carrying, according to nearest principle, corresponding IP address is obtained from described IP address descriptor table, because distance Xi'an, Chongqing is nearest, like this, must to the IP address of GSvr-B3 being positioned at Chongqing, so, the IP address of GSvr-B3 is replied to RSvr-A29.
After step 503, RSvr-A29 receive the IP address of GSvr-B3, in overseas GSvr routing table as shown in table 8, preserve the IP address of domain name 163.com and GSvr-B3; According to the port numbers of this IP address and agreement, send guard station to GSvr-B3 and identify request message, the identification target that request comprises is AccoAddr value liubei 163.com.
Step 504, GSvr-B3 are transmitted to local HashSvr, i.e. HashSvr3 after receiving described guard station identification request message.
After step 505, HashSvr3 receive described guard station identification request message, according to the ASCII value 108 of the initial l of the AddrBase value of AccoAddr value liubei@163.com, judge that this AccoAddr corresponds to QSvr2, so, this message is sent to QSvr2.
After step 506, QSvr2 receive described guard station identification request message, according to AccoAddr value liubei@163.com, from the roaming sublist arranged, obtain corresponding RCode value 21, RCode value 21 is replied to HashSvr3.
RCode value 21 is replied to RSvr-A29 via the GSvr-B3 of this locality by step 507, HashSvr3.
Certainly, in step 507, HashSvr3 also can identify the source address of request message according to described guard station, RCode value 21 is replied to RSvr-A29, and such as this source address is SPAddr value (machao@qq.com, 29).HashSvr3 can send described reply message by the message mode of second step below to RSvr-A29.
After step 509, RSvr-A29 receive the RCode value 21 of replying, by the buddy list of machao, the RCode corresponding to liubei@163.com is set to 21.
In step 509, the RCode value 21 of liubei@163.com can also be sent to the client of machao by RSvr-A29.Like this, described when client sends message to liubei, just can the SPAddr value (liubei@163.com, 21) corresponding to AccoAddr value liubei@163.com and RCode value 21 carry out.
Second step, sends SMS message to liubei, see following flow process according to SPAddr value (liubei@163.com, 21):
First the client in step 601, this side of machao is to the RSvr of correspondence, i.e. RSvr-A29, sends SMS message, and the destination address of message is SPAddr value (liubei 163.com, 21), and source address is SPAddr value (machao qq.com, 29).
Step 602, RSvr-A29 judge that the HCode value 163.com of the object SPAddr of message does not belong to oneself, so, HCode value according to the object SPAddr of message determines object GSvr, such as, by searching overseas GSvr routing table as shown in table 8, obtain the IP address of GSvr-B3 corresponding to domain name 163.com.If there is no the IP address corresponding to domain name 163.com in overseas GSvr routing table as shown in table 8, then according to auxiliary analytic method, obtain the IP address of the corresponding GSvr corresponding to 163.com, here, see above-mentioned steps 501 to step 503, can repeat no more.
Step 603, the RSvr-A29 IP address according to GSvr-B3 and the port numbers of agreement, send to GSvr-B3 by described message.
After step 604, GSvr-B3 receive described message, according to the RCode value 21 of the object SPAddr of described message, in territory as shown in table 7, determine object RSvr RSvr routing table, obtain the IP address of RSvr-B21.
Step 605, the GSvr-B3 IP address according to RSvr-B21 and the port numbers of agreement, send to RSvr-B21 by described message, and the destination address of message comprises the AccoAddr value liubei 163.com of described object SPAddr.
After step 606, RSvr-B21 receive described message, determine target account according to AccoAddr value liubei@163.com.
After step 606, described message can be sent to the client of described target account by RSvr-B21.Like this, the client of this side of liubei just can receive the short message that machao sends.
We know, as long as liubei is unanimously in Wu, so, machao just can use SPAddr value (liubei@163.com, 21) to transmit to liubei always, and does not need all to perform step 501 to step 509 at every turn.
In GSvr, can preserve in other HSvr to the RSvrAddr of corresponding RSvr oneself carrying out information interaction.In the middle of reality, the RSvrAddr of this RSvr can be preserved according to the RSvrCompDesc of a RSvr, also the RSvrAddr of this RSvr can be preserved according to the domain name of a RSvr, the present invention is { to preserve the RSvrAddr of this RSvr according to the domain name of a RSvr, wherein said RSvrAddr is the IP address of corresponding RSvr, and arrange RSvr port numbers } be example, but be not used in restriction.Overseas RSvr routing table see as shown in table 9:
Table 9
Domain name IP address Remark
10.360.cn The IP address of RSvr-C10 Corresponding RSvr-C10
20.139.com The IP address of RSvr-D20 Corresponding RSvr-D20
29.qq.com The IP address of RSvr-A29 Corresponding RSvr-A29
In table 9, preserve the IP address of this RSvr according to the domain name of a RSvr.Wherein, 29.qq.com is the domain name of certain RSvr being positioned at Xi'an in the HSvr corresponding to qq.com, also be the domain name of RSvr-A29,10.360.cn be the domain name being positioned at Pekinese RSvr in the HSvr corresponding to 360.cn, 20.139.com is the domain name of certain RSvr being positioned at Guangzhou in the HSvr corresponding to 139.com.
Such as, in step 503, described guard station identifies that the source address of request message is SPAddr value (machao@qq.com, 29).In step 507, RCode value 21 is replied to GSvr-B3 by HashSvr3, and the destination address of replying message is SPAddr value (machao@qq.com, 29); After GSvr-B3 receives described reply message, according to the destination address of this reply message, corresponding RSvr is determined from overseas RSvr routing table as shown in table 9, such as, according to SPAddr value (machao@qq.com, 29) the domain name 29.qq.com corresponding to RSvrCompDesc, searches described overseas RSvr routing table, obtains the IP address of RSvr-A29; Described reply message, according to the port numbers of this IP address and agreement, is sent to RSvr-A29 by GSvr-B3.
Also such as, liubei finishes the route in Wu, and carry grandson madam and got back to Chengdu, its account data is moved back to in RSvr-28 again.Where machao knows that these change.Like this, this side of machao, when using SPAddr value (liubei 163.com, 21) to send SMS message to liubei, just there will be following situation:
In step 606, after RSvr-B21 receives described message, when determining target account according to AccoAddr value liubei@163.com, active account cannot be determined.In this case, RSvr-B21 can surpass the message of replying expression " account does not exist " or representing " account shifts out " in this side to horse.
Such as, in step 605, the source address of described message is SPAddr value (machao@qq.com, 29), in step 606, RSvr-B21, when determining target account according to AccoAddr value liubei@163.com, does not determine active account, like this, the recovery process of following steps 607 to step 608 is just directly entered:
Step 607, RSvr-B21 create the reply message of the expression " account does not exist " surpassing this side towards horse, and the destination address of this reply message is SPAddr value (machao qq.com, 29), and this reply message is sent to GSvr-B3.
After step 608, GSvr-B3 receive described reply message, from overseas RSvr routing table as shown in table 9, corresponding RSvr is determined according to the destination address of described reply message, such as, according to SPAddr value (machao@qq.com, 29) the domain name 29.qq.com corresponding to RSvrCompDesc, search described overseas RSvr routing table, obtain the IP address of RSvr-A29; GSvr-B3 is according to this IP address, and the port numbers of agreement, and described return information is sent to RSvr-A29.
Like this, machao must arrive this side the message of liubei " again adjourn ", and like this, this side of manchao, just obtains RCode value corresponding to liubei 163.com again.
Save the IP address of domain name 163.com and GSvr-B3 in overseas GSvr routing table as shown in table 8 for the RSvr-A29 of this side of machao, RSvr-A29 is according to the domain name of AccoAddr value liubei@163.com, search overseas GSvr routing table as shown in table 8, obtain the IP address of corresponding GSvr-B3.Then, RSvr-A29 is according to the port numbers of this IP address and agreement, and send guard station to GSvr-B3 and identify request message, the identification target that request comprises is AccoAddr value liubei 163.com.Afterwards, according to the flow process of the step of above-mentioned 504 to 509, namely RSvr-A29 can obtain the RCode value of liubei 163.com.Like this, the new RCode value 28 corresponding to liubei 163.com is just obtained.Like this, this side of machao just can transmit to liubei according to SPAddr value (liubei 163.com, 28).
It should be noted that, if only have a GSvr in a HSvr, so, RSvr in this HSvr only need configure the IP address of this GSvr, like this, in step 607, when RSvr-B21 sends described reply message to GSvr-B3, can directly carry out according to the port numbers of this IP address and agreement.
If be provided with multiple GSvr in a HSvr, then before step 606, RSvr-B21, when receiving the described message from described GSvr, also obtains the IP address of corresponding GSvr.Like this, in step 607, described RSvr, just can according to obtained IP address when sending described reply message to described GSvr, and the port numbers of agreement sends this reply message.
If be provided with multiple GSvr in a HSvr, this multiple GSvr numbering can also be given, to distinguish different GSvr.
In a RSvr, GSvr routing table in territory can be set, in the table, preserve the IP address of this GSvr according to the numbering of GSvr corresponding in this HSvr.Correspondingly, in step 605, described GSvr is when sending described message to described RSvr, the numbering of this GSvr can be carried in the message, like this, in step 607, described RSvr is when sending described reply message, can according to the GSvr numbering of carrying in corresponding message, obtain the IP address of corresponding GSvr, the port numbers according to this IP address and agreement sends described reply message.
Usually, service provider (SP, Service Provider) can in its corresponding RSvr GSvr routing table in territory described in manual configuration.
SP can according to the needs of service interaction, in corresponding GSvr, and the overseas RSvr routing table that manual configuration is as shown in table 9.
Preferably described GSvr safeguards automatically to overseas RSvr routing table as shown in table 9.
Such as, described step 503 is after step 503B:RSvr-A29 receives the IP address of GSvr-B3 further, in overseas GSvr routing table as shown in table 8, preserves the IP address of domain name 163.com and GSvr-B3; According to the port numbers of this IP address and agreement, send guard station to GSvr-B3 and identify request message, request comprises AccoAddr value liubei 163.com, and the source address of this request is SPAddr value (machao qq.com, 29).Correspondingly, described step 504, after step 504B:GSvr-B3 receives described guard station identification request message, is transmitted to local HashSvr, i.e. HashSvr3; Whether judge in overseas RSvr routing table as shown in table 9 according to source address (the machao@qq.com of described request message, 29) the domain name 29.qq.com corresponding to saves the IP address of RSvr-A29, if do not had, then in overseas RSvr routing table as shown in table 9, preserve the IP address of RSvr-A29 according to domain name 29.qq.com.Like this, the record that just can realize overseas RSvr routing table as shown in table 9 increases automatically.Here, GSvr-B3, when receiving described guard station and identifying request message, can obtain the source IP address of message, i.e. the IP address of RSvr-A29.
Also such as, described step 604 is after step 604B:GSvr-B3 receives described message further, and the RCode value 21 according to the object SPAddr of described message determines object RSvr, obtains the IP address of RSvr-B21; Whether judge in overseas RSvr routing table as shown in table 9 according to source address (the machao@qq.com of described message, 29) the domain name 29.qq.com corresponding to saves the IP address of RSvr-A29, if do not had, then in overseas RSvr routing table as shown in table 9, preserve the IP address of RSvr-A29 according to domain name 29.qq.com.
In order to control the expansion of overseas RSvr routing table as shown in table 9, a LastTime field can also be increased in the table, sending the time of message in order to record the RSvr received for the last time corresponding to corresponding domain name.See such as showing the overseas RSvr routing table shown in 9-1.
Table 9-1
Domain name IP address LastTime Remark
10.360.cn The IP address of RSvr-C10 The corresponding time Corresponding RSvr-C10
20.139.com The IP address of RSvr-D20 The corresponding time Corresponding RSvr-D20
29.qq.com The IP address of RSvr-A29 The corresponding time Corresponding RSvr-A29
Based on such as showing the overseas RSvr routing table shown in 9-1, in step 504B or step 604B, the LastTime of the record corresponding to domain name 29.qq.com is also set to current time by GSvr-B3.
GSvr can arrange a scan operation, the record regularly or randomly in traversal list 9-1, judges whether a LastTime value distance current time recorded exceedes default value, such as 7*24*3600 second, if so, then from table 9-1, deletes this record.Like this, just according to the change of traffic carrying capacity, the automatic growth and decline of table 9-1 can be kept, thus allow GSvr reach more good speed row mode.
How to transmit a reply message to described HashSvr about described QSvr, can with reference to described RSvr how to the processing mode that the GSvr of this HSvr transmits a reply message.
How message is sent to described HashSvr about described QSvr, how described HashSvr sends message to described GSvr, and how described RSvr sends message to the GSvr of this HSvr, owing to being encapsulated in a HSvr inside, access on other HSvr the impact do not produced on interface, therefore, different SP can according to the actual conditions of oneself, from the existing various ripe communication technology, select different implementer's formulas.The present invention repeats no longer at this point.
As can be seen from integrated embodiment above, the present invention is based on the address messages method of semi-permanent address, the same with the message method based on semi-permanent address mentioned in described " message method based on semi-permanent address " patent of invention, can once and for all solve the long-expected account number of people or number migration carry problem.The present invention makes every effort to reduce the interface between each service-domain, to simplify the process of RSvr; And last patent more focuses on the agility that message sends, network is flattening more.
Those skilled in the art know, consider the flexibility of deployment, usually, when the respective end slogan of corresponding server or module is arranged in unification, ARSvr, GSvr, RSvr etc. about should be decided to be different port numbers respectively, such as, the port numbers of ARSvr is 6688, the port numbers of GSvr is the port numbers of 7788, RSvr is 8888.
Those skilled in the art know, in order to improve recall precision, in described accounts information table, or in corresponding roaming sublist, the domain name part of corresponding AccoAddr can be saved, and only retain user name part.Correspondingly, when retrieving such table, only according to the user name part of an AccoAddr.
Those skilled in the art know, in the present invention, between the server intercomed mutually or module, can be realized interconnected by IP network.When the two close together, also can communicate by adopting RS485 communication modes.Due to the communication between simple two modules or server, according to actual conditions, can have corresponding mature technology to realize, therefore, the present invention no longer repeats with regard to this respect.
A SPAddr also can be write as an email address format, is also namely write as a SPEmailAddr, and therefore, SPAddr of the present invention is replaced to SPEmailAddr by those skilled in the art, can reach similar technology effect.About more descriptions of SPEmailAddr, see described " message method based on semi-permanent address " patent of invention, no longer carry out imitative stating with regard to the SPAddr of SPEmailAddr form here.
These are only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.All in the spirit and principles in the present invention and so on, any amendment done, improvement, equivalent replacement etc. all should be included within protection scope of the present invention.

Claims (10)

1., based on an address messages method for semi-permanent address, the destination address of described message is SPAddr; It is characterized in that, the method comprises the following steps:
A, source RSvr determine object GSvr according to the HCode of the object SPAddr of message, and described message is sent to described object GSvr;
After b, described object GSvr receive described message, the RCode according to described SPAddr determines object RSvr, and described message is sent to described object RSvr, and the destination address of message comprises the AccoAddr of described SPAddr;
After step c, described object RSvr receive described message, determine target account according to described object AccoAddr.
2. a message treatment method, for GSvr process from the message comprising object SPAddr of other HSvr or for the message that comprises object SPAddr of RSvr process from client; It is characterized in that, the method comprises the following steps:
A, determine object RSvr according to the RCode of described SPAddr;
B, described message is sent to described object RSvr, the destination address of message comprises the AccoAddr of described SPAddr.
3. reply a message treatment method, for the reply message that comprises object SPAddr of GSvr process from the RSvr of this HSvr; It is characterized in that, the method comprises the following steps:
A, determine object RSvr according to the RSvrCompDesc of described SPAddr;
B, described reply message is sent to determined RSvr.
4. a message treatment method, for the treatment of the message comprising object SPAddr from client; It is characterized in that, the method comprises the following steps:
A, source RSvr judge whether the HCode having described SPAddr, if not, the HCode according to described SPAddr determines object GSvr, and described message is sent to described object GSvr.
5. method according to claim 4, is characterized in that, the described HCode according to described SPAddr determines that object GSvr further: the domain name corresponding to HCode of resolving described SPAddr, obtains the IP address of corresponding ARSvr; According to described IP address, send auxiliary analysis request to corresponding ARSvr, in request, carry GI data; After described ARSvr receives described auxiliary analysis request, according to the GI data of wherein carrying, obtain the IP address of corresponding GSvr, this IP address is replied to request side; Described request side joint receives the IP address of described GSvr; Describedly send to described object GSvr to refer to described message, according to the IP address of described GSvr, send described message.
6. across a guard station recognition methods for service-domain, for obtaining the RCode of an AccoAddr; It is characterized in that, the method comprises the following steps:
Object GSvr, according to the AddrHome of described AccoAddr, is determined in a, request side, source, and send guard station to described object GSvr and identify request message, the identification target of carrying in this request message is described AccoAddr;
After b, described object GSvr receive this message, this request message is sent to the RIDSvr of this HSvr;
After c, described RIDSvr receive described request message, according to described AccoAddr, obtain corresponding RCode;
D, described RIDSvr reply the RCode obtained to request side, source.
7. a HSvr, is characterized in that, described HSvr comprises GSvr and RSvr; Each RSvr is assigned a RCode;
Described RSvr is for preserving corresponding accounts information;
Described GSvr receive from other HSvr comprise the message of object SPAddr after, determine corresponding RSvr according to the RCode of described SPAddr, described message is sent to determined RSvr, the destination address of message comprises the AccoAddr of described SPAddr;
Described RSvr receive from this HSvr GSvr comprise the message of object AccoAddr after, according to described object AccoAddr, determine target account.
8. HSvr according to claim 7, is characterized in that, described RSvr receive from client comprise the message of object SPAddr after, judge whether the HCode having described SPAddr, if not, then enter cross-domain Message Processing flow process; Otherwise, enter Message Processing flow process in territory.
9. HSvr according to claim 7, is characterized in that, described HSvr can further include RIDSvr, identifies service for providing guard station; Receive one at described RIDSvr to comprise and identify that the guard station of target identifies after request message, determine the RCode that this identification target is corresponding; Reply determined RCode.
10. HSvr according to claim 7, is characterized in that, described HSvr comprises ARSvr further, for providing auxiliary analysis service;
Be provided with goal description record in described ARSvr, describe record at an objective and comprise the GI that is resolved target and correspondence; Described ARSvr, when receiving one and carrying the auxiliary analysis request of GI data, according to described GI data, determines to resolve target accordingly from described goal description record, gives auxiliary analysis request person by determined parsing target retro.
CN201410116253.5A 2014-03-26 2014-03-26 Message addressing method based on semi-permanent address Active CN104954500B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201410116253.5A CN104954500B (en) 2014-03-26 2014-03-26 Message addressing method based on semi-permanent address

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201410116253.5A CN104954500B (en) 2014-03-26 2014-03-26 Message addressing method based on semi-permanent address

Publications (2)

Publication Number Publication Date
CN104954500A true CN104954500A (en) 2015-09-30
CN104954500B CN104954500B (en) 2019-10-22

Family

ID=54168841

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201410116253.5A Active CN104954500B (en) 2014-03-26 2014-03-26 Message addressing method based on semi-permanent address

Country Status (1)

Country Link
CN (1) CN104954500B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106657425A (en) * 2015-11-03 2017-05-10 王正伟 Automatic finding method of residence code

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1946104A (en) * 2006-03-01 2007-04-11 华为技术有限公司 Method for realizing one-card multiple-number service
US20110238767A1 (en) * 2008-09-24 2011-09-29 John Paul Murphy Message processing
CN102333105A (en) * 2010-07-14 2012-01-25 华为技术有限公司 Business communication method, system, push client terminal and user equipment

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1946104A (en) * 2006-03-01 2007-04-11 华为技术有限公司 Method for realizing one-card multiple-number service
US20110238767A1 (en) * 2008-09-24 2011-09-29 John Paul Murphy Message processing
CN102333105A (en) * 2010-07-14 2012-01-25 华为技术有限公司 Business communication method, system, push client terminal and user equipment

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106657425A (en) * 2015-11-03 2017-05-10 王正伟 Automatic finding method of residence code

Also Published As

Publication number Publication date
CN104954500B (en) 2019-10-22

Similar Documents

Publication Publication Date Title
US8756340B2 (en) DNS wildcard beaconing to determine client location and resolver load for global traffic load balancing
US7752210B2 (en) Method of determining geographical location from IP address information
CN103262503B (en) Node selecting method and equipment in packet core network
US8370457B2 (en) Network communication through a virtual domain
CN108574744A (en) A kind of domain name analytic method, device, electronic equipment and readable storage medium storing program for executing
EP2700208B1 (en) Global traffic management using modified hostname
CN107786678B (en) Domain name resolution method, device and system
EP2323350A1 (en) Method, computer program product and electronic device for hyper-local geo-targeting
EP2993853A1 (en) Route forwarding method, apparatus and system
CN104303489A (en) Method for performing dns resolution in a network, content distribution system and client terminal for deployment in a content distribution system
CN103167464B (en) Method, MS and the MN of triggering update mobile node map information
CN103546593B (en) Wireless sensor network node identifier resolution method based on IP Yu non-IP
CN109729183A (en) Request processing method, device, equipment and storage medium
CN105049550A (en) D1HT+Chord based name and address separation mapping system
CN107896257A (en) Method, apparatus, equipment and the medium of deploying client subsystem function
CN106357539A (en) Data acquisition method and equipment
US7406071B1 (en) Method and system for resolving between geographic information and network addresses in a wide area network, preferably in the internet
CN104125310B (en) Message method based on semi-permanent address
CN103347036A (en) ONS architecture with decentralized management-based EPC parsing method
CN104954500A (en) Message addressing method based on semi-permanent address
CN100566344C (en) A kind of online user search method and system
CN105025059B (en) Location information service system
CN214756421U (en) Domain name resolution system applied to terminal network access of Internet of things
CN105933470A (en) Hierarchical service resource analysis and mapping method and system
CN108055361B (en) Virtual machine positioning method using public service

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant