CN107181687A - Service switching method and operation exchange cloud - Google Patents

Abstract

Service switching method and operation exchange cloud, the present invention disclose a kind of target NextAddr and determine method, and the operation exchange cloud based on this method, for the interacting message between LSvr.Method is determined according to target NextAddr, by setting route data, or, by the operation exchange cloud, the service message interaction between LSvr can be easily and flexibly realized, LSvr connection management is greatly simplified.The present invention also provides a kind of message addressing method, in the method, can be addressed according to the SClass of message, so that the business of the purpose HSvr sides of message or the network planning are unaffected.

Description

Service switching method and operation exchange cloud

Technical field

The present invention relates to internet communication, more particularly in internet, the method for carrying out interacting message exchanges cloud.

Background technology

In internet communication, it is related to global Unified Identity (GUID, Global Unified Identity), the GUID includes two parts：Belong to code (HCode, Home Code) and user code (UCode, User Code).Wherein, HCode indicates which attribution server (HSvr the GUID, namely the corresponding Internet users of the GUID (IUsr, Internet User) belong to, Home Server), UCode is used to indicate GUID different under a HCode.By setting up HCode and HSvr corresponding relation, a pointed HSvr can be obtained according to a HCode.One HSvr one service-domain of correspondence.

The GUID can be an email address or principal and subordinate's code or a shadow code.On the more descriptions of GUID and HSvr, referring to Application No. 201310037232.X's《Communication means and system》Patent of invention, and Application No. 201310049772.X《Shadow code addressing method》Patent of invention.

Each account has an account address (AccoAddr, Account Address), is addressed for account.

The AccoAddr of one GUID source account is the GUID.

The AccoAddr of one GUID migration account is the corresponding cross-domain address code (CDAddr, Cross-domain Address) of the migration account.The GUID is this base GUID (BaseGUID of the CDAddr, The Base GUID), a HCode across last HSvr information (CeSvrDesc, Cross-end HSvr Description) HSvr where the migration account of the CDAddr.On CDAddr more descriptions, referring to Application No. 201310079118.3《Support the network and related news processing method of GUID migrations》Patent of invention.

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 the AccoAddr is the UCode of the GUID, and the AddrHome of the AccoAddr is the HCode of the GUID；When an AccoAddr is a CDAddr, the AddrBase of the AccoAddr is the BaseGUID of the CDAddr, and the AddrHome of the AccoAddr is the CeSvrDesc of the CDAddr.For example for AccoAddr value caocao@yixin.im, corresponding AddrBase is caocao, and corresponding AddrHome is yixin.im.

The HSvr of one AccoAddr ownership is the HSvr pointed by the AddrHome of the AccoAddr.

The AddrHome of one account, is the AccoAddr of account AddrHome；The AddrBase of one account, is the AccoAddr of account AddrBase.

In Application No. 201410098231.0《Message method based on semi-permanent address》The message method based on semi-permanent address is proposed in patent of invention.This method first obtains the guard station code (RCode, Residence Code) corresponding to the guard station server (RSvr, Residence Server) in purpose HSvr where purpose account.When sending message to the purpose account, according to the semi-permanent address (SPAddr corresponding to the AccoAddr and the RCode of the purpose account, Semi-permanent Address) or semipermanent email addresses (SPEmailAddr, Semi-permanent email Address), the message is transmitted directly to the RSvr where the purpose account, so as to improve messaging efficiency.

The two parts such as the RCode that the AccoAddr and RSvr where the account that the SPAddr of one account includes the account are assigned.One SPAddr can be write as (AccoAddr, RCode) form.

More descriptions, referring to described《Message method based on semi-permanent address》Patent of invention.

It is above-mentioned when sending message according to SPAddr or SPEmailAddr, due to needing to parse the domain name corresponding to corresponding SPAddr or SPEmailAddr, to obtain the IP address of the purpose RSvr, therefore, in order to improve domain name resolution efficiency, usually, can be in local cache domain name mapping result, so that next time uses.But, due in a HSvr, it is understood that there may be many RSvr, therefore, corresponding to message sending side, it is necessary to which the domain name mapping result of caching will be multiplied, so as to have influence on recall precision.In addition, by way of carrying out interacting message, also resulting in the connection that RSvr safeguards enormous amount directly setting up connection between RSvr.

In this regard, in Application No. 201610086133.4《Exchange method and exchange cloud》A kind of exchange method and a kind of exchange cloud (XCld, eXchange Cloud) based on this method are proposed in patent of invention.The XCld at least includes two swap servers (XS, eXchange Server)；In XS, route data (RData, Routing Data) is set；Include purpose SPAddr message to be sent for one, the XS, according to the RData of setting, determines next station address (NextAddr, Next Address) of the message according to the purpose SPAddr of the message, that is, determine target NextAddr；According to identified target NextAddr, the message is sent.Pass through XCld, it is possible to achieve each RSvr is directly interconnected in HSvr, the RSvr interconnections between each HSvr can also be realized.So, a RSvr only needs to be linked into the XCld in this HSvr, so that it may carry out interacting message with the RSvr in any HSvr, this just enormously simplify RSvr connection management.

Internet service is colourful.For example, except interacting message between basic user, such as various texts, image, audio, video etc. chat messages；Also customer location is registered and query messages, such as neighbouring people's business；Also payment message, for example, payment message (market payment) between individual human world payment message (such as giving bonus), personal and common account；Also RCode query messages, number dictionary query messages；File transmission, etc..Different Internet services, its frequency of use has difference, its business complexity, resource occupation is there is also difference, therefore, in a HSvr, for different business, the deployment of corresponding Service Process Server (Processing Server) can also have difference.Such as, RSvr higher, the higher chat messages of requirement of real-time that are relatively adapted to processing frequency of use, it is usually, proper in more urban deployment one RSvr of each user.And for individual human world payment transaction; because occurrence frequency is relatively low; therefore; one or several payment transaction processing centers are disposed in the whole nation; for example, East China disposes one in Shanghai or Nanjing, the north disposes one in Beijing or Hebei; south disposes one in Guangzhou, and western part disposes one in Chengdu.For RCode inquiry businesses, equally, frequency of use is relatively low (just being needed when only user migrates), therefore, also need to only dispose several business processing centers.In this case, XS can not just determine target NextAddr when carrying out message exchange according only to the purpose SPAddr of message.

The content of the invention

In view of this, method, and the operation exchange cloud based on this method are determined the invention discloses a kind of target NextAddr, for solving at least one of above-mentioned various problems problem.Method is determined according to the target NextAddr, by correspondingly setting RData, or, by the operation exchange cloud, the service message interaction between each LSvr can be easily and flexibly realized, and enormously simplify LSvr connection management.

A kind of target NextAddr determines method, the target NextAddr for determining message, and the message includes SClass；SelfRData is set；This method comprises the following steps：

A, the SClass according to message, determine the SinkRCode of message；

B, the SinkRCode determined by, according to the SelfRData of setting, determine target NextAddr.

Alternatively, SClass and SinkRCodeDNism corresponding relation are set up；Step a is further：According to the SClass of message, SinkRCodeDNism is selected, according to selected SinkRCodeDNism, to determine the SinkRCode of message.

Alternatively, the corresponding relation for setting up SClass and SinkRCodeDNism is further by setting SCPrefix tables to set up；Step a is further：According to the SClass of the message, according to the SCPrefix tables, best match record is obtained；Judge whether corresponding SinkRCode values effective, if it is, using the SinkRCode as message SinkRCode；Otherwise, using the SinkRCode as SinkRCodeDNism_ID, according to corresponding SinkRCodeDNism, to determine the SinkRCode of message.

Alternatively, the corresponding relation for setting up SClass and SinkRCodeDNism is further by setting SCPrefix tables to set up；Step a is further, according to the SClass of message, searches SCPrefix tables, judges whether SinkRCode is effective in the record of best match, if it is, SinkRCodes of the SinkRCode as message；Otherwise, illustrate the message include purpose RCode, then, using purpose RCode values as message SinkRCode.

Alternatively, default setting is carried out；Before step b, determine whether whether the operation for determining the SinkRCode of message succeeds, if it fails, then directly determining target NextAddr according to default setting.

Alternatively, the message further comprises SinkItem；

Correspondingly, before step a, further comprise：Judge whether the SinkItem of message is effective, if it is, performing step a, otherwise, directly perform step b；Correspondingly, after step a, further comprise, the SinkItem of message is set to identified SinkRCode.

Alternatively, step b is further：According to the SClass of the message and identified SinkRCode, according to the SelfRData of setting, to determine target NextAddr.

Alternatively, step b is further：According to the SClass of the message and identified SinkRCode, RCodeSClass is produced, according to the RCodeSClass of generation, according to the SelfRData of setting, to determine target NextAddr.

One kind exchanges cloud (XCld), for interacting message；The XCld at least includes two XS；

In XS, SelfRData is set；Include SClass message to be sent for one, the XS determines the SinkRCode of message according to the SClass of message；According to identified SinkRCode, according to the SelfRData of setting, target NextAddr is determined；According to identified target NextAddr, the message is sent.

A kind of message addressing method, the message includes SClass and purpose HCode；This method comprises the following steps：

The message for carrying SClass and purpose HCode is sent to this HSvr XCld by a, Source；

B, described HSvr XCld send the message to purpose HSvr XCld according to purpose HCode；

C, the XCld of the purpose HSvr determine the SinkRCode of message according to the SClass；According to identified SinkRCode, according to the SelfRData pre-set, target NextAddr is determined；According to identified target NextAddr, Sink is sent the message to.

In the technical scheme that above-described embodiment is provided, except LSvr can be simplified towards other HSvr communication interface, and therefore simplify outside LSvr processing and the management of interacting message between difference HSvr, corresponding relation also by setting up SClass and SinkRCodeDNism, the planning change that business scale changes possible caused correlation LSvr is encapsulated within HSvr, this just fundamentally solves future, Internet service, internet of things service, in convergence era, because the enormous impact problem that business transition may be brought to interaction between HSvr.

Brief description of the drawings

It is HSvr networkings exemplary plot of the present invention shown in Fig. 1.

It is that target NextAddr of the present invention determines method general embodiment flow chart shown in Fig. 2.

It is that the SinkRCode of message of the present invention standardizes the flow chart of embodiment one of determination method shown in Fig. 3.

It is that the SinkRCode of message of the present invention standardizes the flow chart of embodiment two of determination method shown in Fig. 4.

It is that target NextAddr of the present invention determines that method extends the flow chart of embodiment one shown in Fig. 5.

It is that target NextAddr of the present invention determines that method extends the flow chart of embodiment two shown in Fig. 6.

Embodiment

For the object of the invention, technical scheme and advantage is more clearly understood, with reference to embodiment, it is described in detail from many aspects.

The HCode that one HSvr is possessed can be domain name, and an AccoAddr can be an email address.Exemplified by the present invention is with { HCode that a HSvr is possessed is a domain name, and an AccoAddr is an email address }, but it is not used in the restriction present invention.Below so that { HSvr-A HCode is miliao.com, and HSvr-B HCode is yixin.im, and HSvr-C HCode is immomo.com.Exemplified by illustrated.

Described《Exchange method and exchange cloud》Mentioned in patent of invention, XS, when carrying out message exchange, is carried out according to the RData of setting.

Usually, in an XS, for each HSvr, there is provided corresponding RData.In an XS, the corresponding RData of some HSvr are the HSvrRData of the HSvr.

Described《Exchange method and exchange cloud》Mentioned in patent of invention, when carrying out message exchange between each RSvr, for the stay of two nights (Sink), that is purpose RSvr, belong to this HSvr message, XS, when carrying out message exchange, is the target NextAddr that message is determined according to the HSvrRData corresponding to the purpose HSvr of message.

HSvr can determine whether the Sink of the message belongs to this HSvr according to the purpose HSvr information implicitly or explicitly carried in message.When purpose HSvr is this HSvr, then the Sink of the message belongs to this HSvr；Otherwise, the Sink of the message belongs to other HSvr.

For example, when purpose SPAddr is carried in message, the purpose HSvr information is indicated by the HCode of the SPAddr.Further for example, purpose HCode is directly carried in the message, for indicative purpose HSvr.Further for example, without any HCode information is carried in message, then the Sink that can give tacit consent to the message belongs to this HSvr.

In a HSvr, except XCld, and outside some RSvr, usually, in addition to some provide the server (OSvr, Other Server) of other professional abilities.For example, the OSvr is a dictionary agency (DicAgent, Dictionary Agent), for providing the service of number migration query；Further for example, the OSvr is a guard station identification server (RIDSvr, Residence Identification Server), for providing the inquiry service of account guard station；Further for example, the OSvr is a positional information server, for providing location register and position enquiring business (such as neighbouring people's business)；Further for example, the OSvr is a paying centre, for providing payment services, etc. between account.

On DicAgent and RIDSvr more descriptions, refering to Application No. 201610028014.3《Number dictionary》Patent of invention, and Application No. 201410098231.0《Message method based on semi-permanent address》Patent of invention.

In a HSvr, outside XCld, the server of the XCld is connected to, referred to as leaf server (LSvr, Leaf Server), for example, the RSvr or OSvr that are connected to XCld are LSvr.

In a HSvr, related XCld, XS, RSvr, OSvr etc. HCode, all HCode for the HSvr.

As shown in figure 1, being HSvr networkings exemplary plot of the present invention.In the figure, including three HSvr：HSvr-A、HSvr-B、HSvr-C.

In HSvr-A, there are three RSvr：Positioned at Pekinese RSvr-A10, the RSvr-A28 positioned at Chengdu and the RSvr-A29 positioned at Xi'an；There are two OSvr：OSvr-A1、OSvr-A2；Corresponding XCld is XCld-A, wherein there is two XS connected together：XS-A1 and XS-A2.

In HSvr-B, there are three RSvr：Positioned at Pekinese RSvr-B10, the RSvr-B20 positioned at Guangzhou and the RSvr-B21 positioned at Shanghai；There are three OSvr：OSvr-B1、OSvr-B2、OSvr-B3；Corresponding XCld is XCld-B, wherein there is three XS：XS-B1, XS-B2, XS-B3, and XS-B1 connects together with XS-B2, XS-B3 respectively.

In HSvr-C, there are two RSvr：RSvr-C20 positioned at the Guangzhou and RSvr-C21 positioned at Shanghai；There is an OSvr：OSvr-C1；Corresponding XCld is XCld-C, wherein there is two XS connected together：XS-C1 and XS-C2.

Between related XCld, XS-A1, XS-B1 and XS-C1 etc. connect together between any two, in addition, XS-A2 and XS-B2 connect together.

For two XCld：For XCld-1 and XCld-2, if the XS-2-b in XS-1-a and XCld-2 in XCld-1 is directly connected to, XS-1-a and XS-2-b is called critical point XS (GXS, GateWay XS).

For example, XS-A1, XS-B1, XS-C1, XS-A2, XS-B2 etc. are GXS.

If an XS and at least one LSvr is directly connected to, the XS is called cloud base XS (BXS, Cloud Bottom XS).

For example, XS-B1 is not directly connected to any LSvr, thus, it is not BXS；And others XS has been directly connected to corresponding LSvr, therefore, belong to BXS.

Usually, corresponding accounts information is preserved in the RSvr.

The RSvr that RSvr where the corresponding accounts of one AccoAddr is the AccoAddr.

Usually, these attributes can be included in the accounts information of an account：AccoAddr or AccoAddr AddrBase, Password, ClientIP and ClientPort, etc..Wherein, Password is the password of proper account, ClientIP and the online information that ClientPort is proper account.When an account, which is in, logins state, the IP address and port numbers of the client of the corresponding ClientIP account corresponding with ClientPort；When the account, which is in, publishes state, usually, corresponding ClientIP and/or ClientPort are null value null or 0, be can also appear as without corresponding online record.

The RSvr can obtain the IP address and port numbers for logging in client in an Account Logon, and the IP address and port numbers of acquisition are stored in ClientIP the and ClientPort attributes of the account.

More descriptions on accounts information are referring to described《Communication means and system》Patent of invention.

The RSvr can preserve the accounts information of proper account by accounts information table as shown in table 1.

Table 1

AccoAddr	Password	ClientIP	ClientPort
				caocao@yixin.im	********	Corresponding IP address	Respective end slogan
xushu@yixin.im	********	Corresponding IP address	Respective end slogan

If the port numbers of subscribed client, in table 1, it is convenient to omit ClientPort parts.

Each RSvr is assigned a RCode, for identifying a RSvr in corresponding HSvr.In fact, the RCode can be as the ID of trace route path in a HSvr, to identify the path that a RSvr is planned in HSvr.

The RCode can be a simple coding, for example：jing、guang、hu；Can also be the multiple subdomain strings connected by point, for example：Shen.guang, guang.shen, 10.86,86.10, etc.；Or the path connected by back slash, for example, guang shen, 86 10, etc..Certainly, the RCode can also be the landline telephone area code in correspondence RSvr locations.

The corresponding RSvr of one AccoAddr RCode, for the RCode of the AccoAddr.

One SPAddr AccoAddr AddrHome is the HCode or AddrHome of the SPAddr.

One SPAddr HCode points to a HSvr, namely belongs to the HSvr and possessed, then claims the SPAddr to belong to the HSvr.

For a RSvr, if a SPAddr belongs to this HSvr, and the RCode of the SPAddr points to this RSvr, then the SPAddr belongs to the RSvr.For example, so that RSvr-B10 RCode is 8610 as an example, then SPAddr is (caocao@yixin.im, 8610), and its HCode value yixin.im has pointed to HSvr-B, and therefore, the SPAddr belongs to HSvr-B；Again because its RCode value 8610 has pointed to the RSvr-B10 in HSvr-B, therefore, the SPAddr belongs to RSvr-B10.

It is illustrated below so that RCode is the binary number of one 32 as an example, but is not used in the restriction present invention.

For ease of writing and reading, the present invention presses byte, and with " dotted decimal notation " form, RCode is expressed as to the form of (a.b.c.d).Wherein, a, b, c, d are the decimal integers between 0~255.

For example：The actual corresponding RCode values of dotted decimal notation RCode values 123.1.254.16 are following 32 bit：

01111011 00000001 11111110 00010000

Described《Exchange method and exchange cloud》Mentioned in patent of invention, when carrying out interacting message between each RSvr, the RCode that can be assigned according to RSvr is addressed.For example, when being addressed to RSvr, this HSvr XS is according to the RCode of the RSvr, according to the corresponding relation for this HSvr RCode set and NextAddr, i.e. RCode-NextAddr corresponding relations, to determine target NextAddr.

In order to realize in the interacting message between RSvr and OSvr, or the interacting message between OSvr and OSvr, the present invention, in HSvr, corresponding RCode values are also assigned to each OSvr.So, in this HSvr, when being addressed to OSvr, the OSvr can be considered as a RSvr to carry out by this HSvr XS.That is, according to OSvr RCode, according to the RCode-NextAddr corresponding relations set for this HSvr, to determine target NextAddr.

In the present invention, the NextAddr can be XS address information (XSAddr, XS Address), can also be RSvr address information (RSvrAddr, RSvr Address), it can also be OSvr address information (OSvrAddr, OSvr Address).

For an XS, the XSAddr can be the XS towards other related XS communication link number or the XS towards other related XS TCP connections socket descriptor (SktD, Socket Descriptor).Below with { the unified port numbers of agreement, the XSAddr is other corresponding XS IP address } exemplified by, but be not used in restriction.

For an XS, the RSvrAddr can be the XS towards corresponding RSvr communication link number or the XS towards the SktD of corresponding RSvr TCP connections.Below with { the unified port numbers of agreement, the RSvrAddr is corresponding RSvr IP address } exemplified by, but be not used in restriction.

For an XS, the OSvrAddr can be the XS towards corresponding OSvr communication link number or the XS towards the SktD of corresponding OSvr TCP connections.Below with { the unified port numbers of agreement, the OSvrAddr is corresponding OSvr IP address } exemplified by, but be not used in restriction.

So, belong to this HSvr message for Sink, no matter the Sink is a RSvr,, can be according to the RCode (SinkRCode of the Sink or an OSvr, XS are in addressing, Sink RCode), according to the HSvrRData (SelfRData, Self HSvrRData) set for this HSvr, to determine target NextAddr.

For example, the SelfRData includes RCode-NextAddr corresponding relations, so, XS just can be according to the SinkRCode, according to the RCode-NextAddr corresponding relations of setting, to determine target NextAddr.

Usually, OSvr and RSvr difference is, directly RSvr can be addressed according to purpose SPAddr RCode, i.e., one SPAddr has pointed to a RSvr.

For example, when the Sink of message is a RSvr, usually, corresponding SinkRCode is explicitly carried in the message.For example, liubei sends message to sunquan, the Sink of this message is usually a RSvr, and message typically carries purpose SPAddr, and purpose SPAddr RCode is exactly corresponding SinkRCode.Refering to described《Exchange method and exchange cloud》Patent of invention, is no longer reported here.

But, when the Sink of message is an OSvr, in message, it just may not carry corresponding SinkRCode.Because sending a side of message, corresponding SinkRCode may not being known in advance.For example, the message is a guard station identification request message, for searching the corresponding RCode of an AccoAddr；Further for example, number dictionary inquiry business, there is also analogue；Further for example, for payment transaction, in a HSvr, one or several payment transaction processing centers may be set, to handle payment transaction, rather than for each RSvr one payment transaction processing server is set.In the case of these, how XS obtains the corresponding SinkRCode for addressing

Request message is recognized on guard station, refering to Application No. 201410098231.0《Message method based on semi-permanent address》Patent of invention, and Application No. 201410116253.5《Message addressing method based on semi-permanent address》Patent of invention, the present invention is no longer reported.On number dictionary inquiry business, refering to Application No. 201310700473.8《Telephone number mapping method》Patent of invention, and Application No. 201610028014.3《Number dictionary》Patent of invention, is no longer reported here.

During in order to solve Sink for OSvr, the problem of XS can not obtain corresponding SinkRCode, the present invention is proposed, in the message including a class of service (SClass, Service Class) information.XS determines the SinkRCode of message according to the SClass carried in message.Based on this, the present invention proposes target NextAddr and determines method, for XS when carrying out message exchange, assists in target NextAddr.In the method, SelfRData is set in XS, so that XS can be according to a RCode, according to the SelfRData of setting, to determine the target NextAddr of message.

As shown in Fig. 2 determining method general embodiment flow chart for target NextAddr of the present invention.According to the figure, belong to this HSvr for a Sink, include SClass message to be sent, perform following flow：

Step LT11, the SClass according to the message, determine the SinkRCode of message.

Step LT13, the SinkRCode determined by, according to the SelfRData of setting, determine target NextAddr.

So, the XS can just send the message according to identified target NextAddr.

For example, the SelfRData includes RCode-NextAddr corresponding relations, so, in step LT13, it is possible to according to identified SinkRCode, according to the RCode-NextAddr corresponding relations, to determine target NextAddr.

The message can be as transmitted by other HSvr, for example, being that some GXS is transmitted to this XS in other HSvr XCld.For example, from RSvr-A28 to RSvr-B20 send message when, for XS-B2, the message comes from XS-A2.

The message can also be as transmitted by corresponding LSvr in this HSvr.For example, from RSvr-B20 to OSvr-B3 send message when, for XS-B2, the message comes from RSvr-B20.

Certainly, the message can also be as transmitted by another XS in corresponding XCld in this HSvr.For example, from RSvr-C21 to RSvr-C20 send message when, for XS-C1, the message comes from XS-C2.

XS belongs to other HSvr message for Sink, can directly forward that message to the GXS in other HSvr.For example, from RSvr-A28 to RSvr-B20 send message when, XS-A2 directly forwards that message to XS-B2 when the purpose HCode for judging message has pointed to HSvr-B.

XS belongs to other HSvr message for Sink, can also forward that message to other XS in this HSvr, and the final a certain GXS in this HSvr forwards that message to the GXS in other HSvr.For example, from RSvr-C21 to RSvr-A29 send message when, XS-C2 judge message purpose HCode sensing other HSvr when, directly forward that message to XS-C1；XS-C1 is received after the message, when the purpose HCode for judging message has pointed to HSvr-A, directly forwards that message to XS-A1.

Described《Exchange method and exchange cloud》The message switching method being previously mentioned in patent of invention has elaborated how HSvr HCode is addressed according to where the Sink of message, and imitation narration is no longer carried out here.

Among actual, SClass and SinkRCode corresponding relation, namely SClass-SinkRCode corresponding relations can be set up.For example, preserving corresponding SinkRCode values according to SClass values by setting SClass-SinkRCode mapping tables.So, in step LT11, XS can determine corresponding SinkRCode according to the SClass carried in message according to the SClass-SinkRCode corresponding relations.

It is illustrated below so that SClass is the binary number of one 16 as an example, but is not used in the restriction present invention.

For ease of writing and reading, the present invention presses byte, and with " dotted decimal notation " form, SClass is expressed as into (e.f) form.Wherein, e, f are the decimal integers between 0~255.

For example：The actual corresponding SClass values of dotted decimal notation SClass values 5.65 are following 16 bit：

00000101 01000001

In order to simplify the configuration of RCode-NextAddr corresponding relations, preferably, the RCode-NextAddr corresponding relations are further the corresponding relation of RCode prefixes (RCodePrefix, RCode Prefix) and NextAddr, i.e. RCodePrefix-NextAddr corresponding relations.

For example, preserving the RCodePrefix-NextAddr corresponding relations by setting RCodePrefix tables.

Correspondingly, according to a RCode, corresponding NextAddr is determined according to the RCodePrefix tables of setting.For example, according to the RCode, the RCodePrefix of best match being found from the RCodePrefix tables, the NextAddr of corresponding record is regard as matching result.

Equally, in order to simplify the configuration of SClass-SinkRCode corresponding relations, preferably, the SClass-SinkRCode corresponding relations are further SClass prefixes (SCPrefix, SClass Prefix) with SinkRCode corresponding relation, i.e. SCPrefix-SinkRCode corresponding relations.

For example, preserving the SCPrefix-SinkRCode corresponding relations by setting SCPrefix tables.

Correspondingly, according to a SClass, corresponding SinkRCode is determined according to the SCPrefix tables of setting.For example, according to the SClass, the SCPrefix of best match being found from the SCPrefix tables, the SinkRCode of corresponding record is regard as matching result.

The present invention is so that best match is most long matching as an example.But it is not used in the restriction present invention.

According to RCode according to RCodePrefix tables, the mode of best match is determined, or, according to SClass according to SCPrefix tables, mode of best match, etc. is determined, there is varied., can be directly refering to ready-made, a large amount of disclosed IP route tables designs data related to realization when reality is implemented.

So that exemplified by, according to RCodePrefix tables, determining best match according to RCode, in addition to using this thick method of order traversal RCodePrefix tables, some conventional optimized algorithms can also be used.

, so, can be according to a RCode value, by searching the binary balance tree, to determine corresponding best match if for example, not including mutually between RCodePrefix, a binary balance tree can be set up directly according to the RCodePrefix tables.It is of course also possible to which with to a point query method, corresponding best match is determined by searching RCodePrefix tables.

If further for example, allowing mutually to include between RCodePrefix, binary balance tree can be set up by expanded prefix mode, then according to a RCode value, by searching the binary balance tree, to determine corresponding best match.Referring specifically to entitled《The design and realization and the improvement to router switching fabric of quick routing table》Beijing University of Post ＆ Telecommunication Master degree candidate's academic dissertation (author Wang Liyuan).

Due to searching an IP prefix table according to a purpose IP address, the mode for obtaining best match is ripe technology, therefore, and the present invention is no longer repeated with regard to this.

Among actual, the frequency that business occurs has very big difference.In this regard, the SCPrefix tables can be split and claim some sublists on earth by high according to traffic frequencies, in this manner it is possible to according to the SClass of message, first search the corresponding sublist of high frequency business, it is determined that after best match, end operation；In no determination best match, then search the corresponding sublist of rather low-frequency business.

Among actual, the SinkRCode of not all message can show in SCPrefix tables, that is, being not that effective SinkRCode can be correspondingly arranged in SCPrefix tables for all SCPrefix.For example, liubei sends message to sunquan, the Sink of this message is a RSvr, purpose SPAddr is carried in message, the RCode of the SPAddr is exactly corresponding SinkRCode, at this moment, corresponding SinkRCode cannot directly be determined from SCPrefix tables according to the SClass values carried in message.

In this case, there will be such case：{ in the SClass according to message, when searching SCPrefix tables, matching less than any record }.At this moment, it can arrange：Carry purpose RCode in default message, and using purpose RCode as message SinkRCode.

But so do, not best approach.It is often some high frequency business, such as chat messages because those directly carry purpose RCode business in the message.When there are chat messages to pass through every time, after XS is operated by { according to the SClass of message, search SCPrefix tables, judge whether best match } is such, the SinkRCode of message way is just can determine that, is poorly efficient.

Especially, for the class high frequency business for the SinkRCode for being directly used as message using the purpose RCode carried in message, unrelated SCPrefix (IndependentSCPrefix, Independent, SCPrefix) can be directly set.For example, can be by setting an IndependentSCPrefix table, for preserving corresponding IndependentSCPrefix values.

So, XS is when carrying out message exchange, just can be first according to the SClass carried in message, search IndependentSCPrefix tables, see whether can determine best match, if it is, illustrating that the message includes purpose RCode, then, the purpose RCode values of the message are regard as corresponding SinkRCode；Otherwise, according to the SClass values carried in message, SCPrefix tables are searched, to determine corresponding SinkRCode.In this case, if according to the SClass values carried in message, search SCPrefix tables, corresponding SinkRCode can not also be obtained, i.e. no proper fit, then can do Exception handling, or, the message can also be given tacit consent to including purpose RCode, and using purpose RCode as message SinkRCode.

Described Exception handling can be：By the part or all of of the message, and the write-in running log file such as description that makes an exception, or do other processing.Below as example, but it is not used in restriction.

The mode that one message includes purpose RCode has a variety of, for example, directly setting purpose RCode, the purpose RCode for bearer messages in the message.Generally, a message includes purpose SPAddr, at this moment, using purpose SPAddr RCode as message purpose RCode.No longer such situation is repeated below.

Among actual, for different SClass, the SinkRCode of message mode is determined, it is understood that there may be very big difference.

For example, liubei sends message to sunquan, the Sink of this message is a RSvr, purpose SPAddr is carried in message, the RCode of the SPAddr is exactly corresponding SinkRCode, at this moment, corresponding SinkRCode cannot directly be determined from SCPrefix tables according to the SClass values carried in message.

Further for example, liubei has in the people near inquiry, query messages, the current positional informations of liubei are carried, such as are a GeoHash values.And in HSvr-C, there is provided two positional information servers, XS-C1 wishes to be determined message being sent in which positional information server according to liubei current location.In this case, corresponding SinkRCode cannot directly simply be determined according to the SClass carried in message.

Because the rule for the SinkRCode for determining message has difference, therefore, the present invention is proposed, set up SClass and determine SinkRCode rule (SinkRCodeDNism, SinkRCode Determination Mechanism) corresponding relation, namely SClass-SinkRCodeDNism corresponding relations.So, XS is when carrying out message exchange, it is possible to according to the SClass carried in message, corresponding SinkRCodeDNism is selected according to the SClass-SinkRCodeDNism corresponding relations, then according to the SinkRCodeDNism of selection, to determine the SinkRCode of message.

The step LT11 is further step LT11B：According to the SClass of the message, according to the SClass-SinkRCodeDNism corresponding relations, corresponding SinkRCodeDNism is selected；According to the SinkRCodeDNism of selection, to determine the SinkRCode of message.

Among actual, developer can write different functions specifically to be handled for different SinkRCodeDNism, and the SinkRCode determined is returned to called side.Here it is possible to using the pointer of the message as call parameters, to call corresponding SinkRCodeDNism function.

Equally, in order to simplify the configuration of SClass-SinkRCodeDNism corresponding relations, it is preferred that the SClass-SinkRCodeDNism corresponding relations are further SCPrefix and SinkRCodeDNism corresponding relation, i.e. SCPrefix-SinkRCodeDNism corresponding relations.

Correspondingly, in step LT11B, described { according to the SClass of the message, according to the SClass-SinkRCodeDNism corresponding relations, selecting corresponding SinkRCodeDNism } is further：According to a SClass, according to the SCPrefix-SinkRCodeDNism corresponding relations of setting, to determine corresponding SinkRCodeDNism.For example, according to the SClass, the SCPrefix of best match being found from the SCPrefix-SinkRCodeDNism corresponding relations, corresponding SinkRCodeDNism is regard as matching result.

Among actual, in order to improve running efficiency of system, operated also for the configuration for simplifying network O＆M personnel, the present invention as follows, SCPrefix-SinkRCodeDNism corresponding relations is merged into described SCPrefix tables.

This method is：A part in RCode valued spaces is remained, for identifying corresponding SinkRCodeDNism.For example, it is expected that SinkRCodeDNism be no more than 256 kinds, then, by in RCode valued spaces, 0.0.0.0-0.0.0.255, namely 0-255 256 values are remained, and are used as SinkRCodeDNism ident values (SinkRCodeDNism_ID, SinkRCodeDNism Identity), the different SinkRCodeDNism for identifying.So, when a RCode value is more than 255, just effectively.

So, according to a SClass, when finding the SCPrefix of best match from the SCPrefix tables, if the SinkRCode values of corresponding record are more than 255, i.e., not in the range of 0.0.0.0-0.0.0.255, then it is effective to illustrate the SinkRCode.In this case, corresponding SinkRCodeDNism is：{ setting up SCPrefix and SinkRCode corresponding relation, the SCPrefix set up and SinkRCode corresponding relation are searched with the SClass in message, to obtain best match, so that it is determined that the SinkRCode of message }.Especially, in this case, it is not necessary to assign a SinkRCodeDNism_ID for the SinkRCodeDNism, but in order to describe below conveniently, the present invention is that the SinkRCodeDNism_ID of SinkRCodeDNism assignments is 255.

According to a SClass, when finding the SCPrefix of best match from the SCPrefix tables, if the SinkRCode of corresponding record is considered as SinkRCodeDNism_ID by the SinkRCode values of corresponding record in the range of 0.0.0.0-0.0.0.255.At this moment, XS further according to selection the SinkRCodeDNism, i.e., according to the SinkRCodeDNism indicated by the SinkRCodeDNism_ID recorded as best match, to determine the SinkRCode of message.

Certainly, in this case, the SCPrefix tables can also be split and claim some sublists on earth by high according to traffic frequencies, in this manner it is possible to according to the SClass of message, first search the corresponding sublist of high frequency business, it is determined that after best match, end operation；In no determination best match, then search the corresponding sublist of rather low-frequency business.

The step LT11 is further step LT11C：According to the SClass of the message, according to the SCPrefix tables, best match record is obtained；Judge whether the SinkRCode values of the record effective, for example whether more than 255, if it is, using the SinkRCode of the record as message SinkRCode；Otherwise, the SinkRCode of the record is considered as SinkRCodeDNism_ID, according to the SinkRCodeDNism corresponding to the SinkRCodeDNism_ID, to determine the SinkRCode of message.As shown in figure 3, standardizing the flow chart of embodiment one of determination method for the SinkRCode of message of the present invention.

For example：

SinkRCodeDNism_ID is 0：

Corresponding SinkRCodeDNism is：In the message carry purpose RCode, directly using the purpose RCode as message SinkRCode.

Correspondingly, in step LT11C, in the SClass according to the message, according to the SCPrefix tables, when obtaining best match record, if the SinkRCode of the record is 0, then give tacit consent to the message and carry purpose RCode, and using entrained purpose RCode as message SinkRCode.

SinkRCodeDNism_ID is 1：

Corresponding SinkRCodeDNism is：{ purpose RCode is carried in the message, the operation relation by purpose RCode to SinkRCode is set up, the SinkRCode is obtained by entrained purpose RCode computings }.

Correspondingly, in step LT11C, in the SClass according to the message, according to the SCPrefix tables, when obtaining best match record, if the SinkRCode of the record is 1, gives tacit consent to the message and carry purpose RCode, and calculated accordingly according to entrained purpose RCode, to obtain the SinkRCode of message.For example, the calculating can directly be that the purpose RCode is obtained into the SinkRCode of message plus an offset.Either two bytes of low level of the purpose RCode are all set to 0 to obtain the SinkRCode of message.

SinkRCodeDNism_ID is 2：

Corresponding SinkRCodeDNism is：{ purpose RCode is further carried in the message, for the corresponding SCPrefix or SinkRCodeDNism, purpose RCode and SinkRCode corresponding relations is set up；The corresponding relation is searched with the purpose RCode of message, to obtain best match, so that it is determined that the SinkRCode of message }.

Correspondingly, in step LT11C, in the SClass according to the message, according to the SCPrefix tables, when obtaining best match record, if the SinkRCode of the record is 2, gives tacit consent to the message and carry purpose RCode, and the corresponding relation for the SClass or SinkRCodeDNism purpose RCode and SinkRCode set up is searched with entrained purpose RCode, to obtain the SinkRCode of message.

SinkRCodeDNism_ID is 3：

Corresponding SinkRCodeDNism is：{ purpose AccoAddr is further carried in the message, for the corresponding SCPrefix or SinkRCodeDNism, purpose AccoAddr and SinkRCode corresponding relations is set up；The corresponding relation is searched with the purpose AccoAddr of message, to obtain best match, so that it is determined that the SinkRCode of message }.

Correspondingly, in step LT11C, in the SClass according to the message, according to the SCPrefix tables, when obtaining best match record, if the SinkRCode of the record is 3, gives tacit consent to the message and carry purpose AccoAddr, and the corresponding relation for the SClass or SinkRCodeDNism purpose AccoAddr and SinkRCode set up is searched with entrained purpose AccoAddr, to obtain the SinkRCode of message.

SinkRCodeDNism_ID is 4：

Corresponding SinkRCodeDNism is：HSvr and SinkRCode corresponding relation where setting up information source (Source), namely SourceHSvr tables are set up, the SourceHSvr tables set up are searched with the HCode of HSvr where Source, to determine the SinkRCode of message }.

Correspondingly, in step LT11C, in the SClass according to the message, according to the SCPrefix tables, when obtaining best match record, if the SinkRCode of the record is 4, SourceHSvr tables are searched with the HCode of HSvr where the Source of the message, to obtain the SinkRCode of message.For example, for paying class, because the payment transaction amount that some HSvr is interacted between this HSvr is especially big, and being separately provided a payment transaction class OSvr for being directed to corresponding HSvr.

Usually, HSvr HCode where Source is carried in the message.If do not carried, the Source that can give tacit consent to the message belongs to this HSvr.

SinkRCodeDNism_ID is 5：

Corresponding SinkRCodeDNism is：{ geography information (GI) of source user is further carried in the message；GI and SinkRCode corresponding relation, searches GI and SinkRCode corresponding relation with the GI of source user, best match is found, to determine the SinkRCode of message }.

Correspondingly, in step LT11C, in the SClass according to the message, according to the SCPrefix tables, when obtaining best match record, if the SinkRCode of the record is 5, then give tacit consent to the GI that the message carries source user, and GI and SinkRCode corresponding relation is searched with the GI of entrained source user, best match is found, to obtain the SinkRCode of message.

The GI can be longitude and latitude degrees of data, in this case, described { with the GI of the source user of the message, searching GI and SinkRCode corresponding relation, best match is found, to obtain the SinkRCode of message }, be further：According to the GI of the source user, determined and the closest record of the source user from GI and SinkRCode corresponding relation, to obtain the SinkRCode of message.

The GI can be GeoHash values, in this case, directly with the GI of the source user of the message, search GI and SinkRCode corresponding relation, best match is obtained, to obtain the SinkRCode of message.

The GI can be area information (AI), in this case, directly with the GI of the source user of the message, search GI and SinkRCode corresponding relation, best match is obtained, to obtain the SinkRCode of message.

{ longitude and latitude degrees of data is used for describing a geographic point, and GeoHash values are used for describing a geographic block } is different, and AI is divided according to the administrative right of attribution to tellurian region.On AI associated description, referring to Application No. 201410765289.6《Aid in analytic method》Patent of invention, is no longer reported here.

SinkRCodeDNism_ID is 6：

Corresponding SinkRCodeDNism is：{ purpose AccoAddr is further carried in the message, purpose AccoAddr and SinkRCode corresponding relations is set up；The corresponding relation is searched with the purpose AccoAddr of message, to obtain best match, so that it is determined that the SinkRCode of message }.

Correspondingly, in step LT11C, in the SClass according to the message, according to the SCPrefix tables, when obtaining best match record, if the SinkRCode of the record is 6, gives tacit consent to the message and carry purpose AccoAddr, and the purpose AccoAddr and SinkRCode that set up corresponding relation are searched with entrained purpose AccoAddr, to obtain the SinkRCode of message.XS can the AccoAddr and SinkRCode for locally preserving substantial amounts corresponding relation, so, XS can be directly from the corresponding RCode of one AccoAddr of local lookup.

The present invention can not all SinkRCodeDNism of limit.Among actual, technical staff can be as needed, according to inventive method, correspondingly to formulate a variety of SinkRCodeDNism.And embed it in the flow of the present invention.

In step LT11C, in the SClass according to the message, according to the SCPrefix tables, when obtaining best match record, if do not obtained, it can give tacit consent to and determine the SinkRCode of message according to SinkRCodeDNism_ID for 0 SinkRCodeDNism, for example, give tacit consent to the message and carry purpose RCode, and using entrained purpose RCode values as message SinkRCode.

So, it is the SClass corresponding to 0 SinkRCodeDNism for substantial amounts of SinkRCodeDNism_ID, avoids the need for carrying out corresponding data configuration in the SCPrefix tables, in this manner it is possible to greatly facilitate O＆M.

Certainly, set to simplify SCPrefix tables, acquiescence RCode (DefaultRCode, Default RCode) can also be set, correspondingly, in step LT11C, in the SClass according to the message, according to the SCPrefix tables, when obtaining best match record, if do not obtained, can using the DefaultRCode of setting as message SinkRCode.

It is whether effective as the DefaultRCode that before the SinkRCode of message, can also judge to set in the DefaultRCode using setting, for example, if more than 255, if it is, just using the DefaultRCode of setting as message SinkRCode；Otherwise, the SinkRCode of message is determined still according to SinkRCodeDNism_ID for 0 SinkRCodeDNism.

So, configuration provides greater flexibility just to the SCPrefix tables.

Especially, SClass and standby SinkRCodeDNism corresponding relation are further set up.In step LT11B, when the SinkRCode of message can not be determined, further according to the standby SinkRCodeDNism corresponding to the SClass of the message, to determine the SinkRCode of message.

It is preferred that in SCPrefix tables, further comprising standby SinkRCode fields.In step LT11C, when determining the SinkRCode of message according to the SinkRCodeDNism corresponding to the SinkRCodeDNism_ID, when the SinkRCode of message can not be determined, then determine whether whether the standby SinkRCode of record is effective, if it is, using the standby SinkRCode as message SinkRCode；Otherwise, the standby SinkRCode is considered as SinkRCodeDNism_ID, according to the SinkRCodeDNism corresponding to the SinkRCodeDNism_ID, to determine the SinkRCode of message.As shown in figure 4, standardizing the flow chart of embodiment two of determination method for the SinkRCode of message of the present invention.

By in SCPrefix tables, further comprising standby SinkRCode fields, to realize configuration of revealing all the details, so as to significantly enhance the flexibility of data configuration, O＆M is facilitated.For example, the configuration of revealing all the details can directly select the SinkRCodeDNism that SinkRCodeDNism_ID is 255.Effective SinkRCode is simply to set in standby SinkRCode to be by default worth.So, even if the SinkRCode of message can not be determined according to previous SinkRCodeDNism, by determining the SinkRCode of message according to standby SinkRCode fields so that the final SinkRCode for not interfering with message determination.

For example, in step LT11C, when the SinkRCode of message can not be determined for 4 SinkRCodeDNism according to SinkRCodeDNism_ID, the SinkRCode of message is determined for 255 SinkRCodeDNism further according to SinkRCodeDNism_ID.For example, in SourceHSvr tables in XS-B2, just for miliao.com there is provided corresponding SinkRCode, and the HCode of HSvr where the Source of message is immomo.com, in this case, according to according to SinkRCodeDNism_ID the SinkRCode of message can not be just determined for 4 SinkRCodeDNism, and now, the SinkRCode of message can be determined according to SinkRCodeDNism_ID is 255 SinkRCodeDNism, that is, using the standby SinkRCode field values of the record as message SinkRCode.Here, the configuration to the standby SinkRCode fields should ensure that the standby SinkRCode fields of the record are an effective SinkRCode values, otherwise, not be just the SinkRCodeDNism that SinkRCodeDNism_ID is 255.

Further for example, in step LT11C, when the SinkRCode of message can not be determined for 3 SinkRCodeDNism according to SinkRCodeDNism_ID, the SinkRCode of message is determined for 0 SinkRCodeDNism further according to SinkRCodeDNism_ID.

In order that, on the path from XS to Sink, XS below no longer needs to perform the operation for the SinkRCode for determining the message, SinkItem can be further comprised in the message, to record the SinkRCode values for the message having determined.Usually, the SinkItem initial values are RCode retention 0.XS just performs the operation for the SinkRCode for determining the message when judging the SinkItem of message for 0, and the SinkRCode values of determination are filled up in the SinkItem of the message.So, on the path from XS to Sink, follow-up XS just determines operating for the SinkRCode of corresponding message without performing again, so as to improve message exchange and overall transfer efficiency.

For example, sending message from RSvr-B20 to RSvr-B21 or OSvr-B2, XS-B2 is after message is received, whether the SinkItem for judging message is 0, if it is, it is determined that the SinkRCode of the message, and the SinkRCode values of determination are filled up in the SinkItem of message.So, from XS-B2 to RSvr-B21 or on OSvr-B2 path, the SinkRCode's that follow-up XS-B1 and XS-B3 determine the message without performing again operates.

Especially, in this case, for some business, work as message sender, such as RSvr or OSvr, when clearly knowing the SinkRCode of message, directly the SinkRCode values can be filled up in the SinkItem of message.In this case, for follow-up XS, the SinkItem of the message will directly be a virtual value.

For example, liubei sends message to sunquan, the Sink of this message is usually a RSvr, and the RCode that message typically carries purpose SPAddr, the SPAddr is generally exactly the SinkRCode of the message.This when, directly the RCode of the SPAddr can be preserved with the SinkItem of message, so, the message is when carrying the purpose SPAddr, the RCode values of the SPAddr are saved in the SinkItem of message, i.e. message includes the AccoAddr items of SinkItem and purpose SPAddr, and the purpose SPAddr of message is made up of the SinkItem and purpose SPAddr of message AccoAddr.

Among actual, there is such case, a message is that, for paying money to targeted customer, the RCode for the paying centre corresponding to the SClass of payment is only the SinkRCode of message, rather than in message the SPAddr of purpose account RCode.And paying centre is after payment is finished, if also to send a notification message to purpose account, at this moment, it is necessary to use the SPAddr of purpose account.In this case, the SPAddr of carrying target account is needed in message, but the RCode of the SPAddr can not be filled in the SinkItem of message.That is, the SinkRCode values of application message do not rewrite the RCode values of purpose SPAddr in message.

Certainly, if simply designing different message formats according to different SClass, so, for some SClass, foregoing liubei sends message to sunquan, in the case of carrying purpose SPAddr in the message, purpose SPAddr RCode is directly carried with the SinkItem of message, is also a kind of selection.But so it is unfavorable for flexibly being dispatched according to SClass in XCld aspects, so as to have influence on the network planning.

If it is considered that the scalability of business and facilitate O＆M, it is preferred that in the message simultaneously including SinkItem, purpose SPAddr AccoAddr items, and purpose SPAddr RCode items.So, the SClass by XS in message, selects corresponding SinkRCodeDNism, the SinkRCode of message is determined according to the SinkRCodeDNism, and the SinkRCode of determination is filled up in the SinkItem of message.So, in some OSvr, because business scale expands, and when being split, corresponding XS data configuration is directly updated in XCld sides, without being updated to the bigger RSvr sides of quantity or OSvr sides.

In order to reduce the disturbance to the network operation, in a HSvr, this thing of data configuration for updating corresponding XS on a large scale in XCld sides also should not frequently occur.

In a HSvr, when business, which is developed, causes corresponding RSvr or OSvr fractionation or merging, generally require and different RCode are distributed to new RSvr or OSvr, in this way it is possible to cause the change of corresponding SelfRData data in the multiple XS in XCld sides.In order to reduce RSvr and OSvr because business splits or merged the renewal of corresponding SelfRData data in the caused multiple XS in XCld sides, present invention further propose that, the shared RCode of multiple LSvr situation is allowed to exist, allow a RCode value being assigned to several LSvr, correspondingly, when according to SinkRCode to address LSvr, further carried out according to the SClass of message.

In this case, it is, according to RCode and SClass, to set corresponding NextAddr, that is, RCode-SClass-NextAddr corresponding relations to be set in the SelfRData.Correspondingly, the step LT13 is further step LT13B：According to the SClass of the message and identified SinkRCode, according to the SelfRData of setting, to determine target NextAddr.

For the ease of configuration, described { in the SelfRData, according to RCode and SClass, to set corresponding NextAddr, that is, setting RCode-SClass-NextAddr corresponding relations } is further：It is, according to RCodePrefix and SCPrefix, to set corresponding NextAddr, that is, RCodePrefix-SCPrefix-NextAddr corresponding relations to be set in the SelfRData.Correspondingly, the step LT13B is further：According to the SClass of the message and identified SinkRCode, according to the SelfRData of setting, best match is obtained, to determine target NextAddr.

In order to improve operational efficiency, preferably, it is used as a kind of restricted usage, a RCodeSClass value can be produced according to RCode and SClass, correspondingly, it is according to RCodeSClass in the SelfRData, to set corresponding NextAddr, that is, RCodeSClass-NextAddr corresponding relations are set.Correspondingly, the step LT13 is further step LT13C：According to the SClass of the message and identified SinkRCode, RCodeSClass is produced；According to the RCodeSClass of generation, according to the SelfRData of setting, to determine target NextAddr.

Have a variety of according to a RCode and SClass modes for producing a RCodeSClass value, name two examples.

Mode one, for RSvr or OSvr assignment RCode when, agreement RCode low byte is remained without as 00000000.So, can paste SClass upper byte in RCode low byte when producing a RCodeSClass value according to a RCode and SClass.For example, RCode values are 123.234.58.0, SClass values are 2.89, then the value 123.234.58.2 that the RCodeSClass values produced are made up of RCode a high position three bytes 123.234.58 and SClass upper byte 2.

Mode two, to produce a RCodeSClass value according to a RCode and SClass be directly that the SClass is spliced to behind the RCode values to obtain.For example, RCode values are 123.234.58.63, SClass values are 2.89, then after splicing, and the RCodeSClass values of generation are the 123.234.58.63.2.89 of 48.

For the ease of the configuration of RCodeSClass-NextAddr corresponding relations, preferably, the RCodeSClass-NextAddr corresponding relations are further RCodeSClass prefixes (RCodeSCPrefix, RCodeSClass Prefix) with NextAddr corresponding relation, i.e. RCodeSCPrefix-NextAddr corresponding relations.

For example, preserving the RCodeSCPrefix-NextAddr corresponding relations by RCodeSCPrefix tables.

Correspondingly, according to a RCodeSClass, corresponding NextAddr is determined according to the RCodeSCPrefix tables of setting.For example, according to the RCodeSClass, the RCodeSCPrefix of best match being found from the RCodeSCPrefix tables, the NextAddr of corresponding record is regard as matching result.

So, in a HSvr, when business, which is developed, causes corresponding RSvr or OSvr fractionation or merging, usually, corresponding RCode need not be assigned for new RSvr or OSvr, and only needed in the XS to the RSvr or OSvr connections, corresponding RCodeSCPrefix tables are updated, and the XCld sides of the HSvr, other XS are unaffected.

Configured for the ease of corresponding data in each XS in overall XCld, default setting can also be carried out in XS.Correspondingly, before step LT13, further step LT12：Judge whether the SinkRCode of determined message is effective, if it is, just performing step step LT13；Otherwise, according to default setting, target NextAddr is determined.

Referring to as shown in figure 5, determining that method extends the flow chart of embodiment one for target NextAddr of the present invention.

Especially, in step LT11C, in the SClass according to the message, according to the SCPrefix tables, when obtaining best match record, if do not obtained, then directly according to default setting, target NextAddr is determined, then terminates whole target NextAddr and determines flow.

Referring to as shown in fig. 6, determining that method extends the flow chart of embodiment two for target NextAddr of the present invention.

Among actual, according to XS in XCld position, different with the requirement to XS, the default setting also should be variant.

The default setting includes：Overall acquiescence NextAddr (GDNextAddr, General Default NextAddr) is set.Described determines that target NextAddr is further according to default setting：Directly it regard GDNextAddr as target NextAddr.

So, an XS avoids the need for setting those oneself unconcerned SCPrefix in SCPrefix tables.For example, XS-C2 does not connect any OSvr, and therefore, the message of the business for being related to OSvr, it is XS-C1 that can directly set GDNextAddr.So, XS-C2 data configuration is just simplified.

The present invention is by setting up SClass and SinkRCodeDNism corresponding relation in XCld sides so that XS can be according to the SClass of message, to select SinkRCodeDNism, and according to selected SinkRCodeDNism, to determine the SinkRCode of message.So, when carrying out interacting message between HSvr, Source can not needed to carry out decision message SinkRCode, this just provides great flexibility to the network planning of purpose HSvr sides, corresponding LSvr RCode need not about be fixed, but according to whether being easy to messaging, if it is easy to the configuration of RData in XS, flexibly to assign corresponding LSvr RCode.

From the embodiments above as can be seen that based on service message exchange method of the invention, and operation exchange cloud, it is possible to achieve flexibly interconnected between any LSvr, so that, it is internet communication, Internet of Things Network Communication, reliable technical support is provided in the fusion of service layer.

One skilled in the art that, in view of the flexibility of deployment, usually, in the respective end slogan of unified agreement corresponding server or module, XS, RSvr, OSvr etc. should be about set to different port numbers respectively, for example, RSvr port numbers are 5588, the port numbers that OSvr port numbers are 6688, XS are 7788.

It should be noted that if XS is a BXS, the BXS can be a distributed system.For example, for associative operation in step LT11, one part even can all be splitted out, zoom out, be placed into LSvr sides to implement, for example, in RSvr or OSvr sides, when sending message to the BXS of connection, the SinkRCode of message is directly determined, and the SinkRCode of determination is filled up in SinkItem.So, BXS whole work efficiency can be improved.Simply, this is not easy to data configuration and management, for example, when the corresponding SinkRCodeDNism of a certain SClass changes, or a certain SClass corresponding SinkRCode is when changing, in the distributed BXS, in the corresponding module for being placed into LSvr sides, it may be required for being updated about the data configuration of the SClass.

As it is known by the man skilled in the art that in the present invention, between the server or module that are in communication with each other, can be realized and interconnected by IP network.When the two is closer to the distance, it can also be communicated by using RS485 communication modes.Due to simple two communication between module or server, according to actual conditions, there can be various corresponding suitable mature technologies to realize, therefore, the present invention is no longer repeated with regard to this respect.

Presently preferred embodiments of the present invention is these are only, is not intended to limit the scope of the present invention.It is all and some key elements or flow to be deleted in the spirit and principles in the present invention etc, any modification made, improvement, equivalent substitution, wait and should be included in the scope of the protection.

Claims (10)

1. a kind of target NextAddr determines method, the target NextAddr for determining message, the message includes SClass； Characterized in that, setting SelfRData；This method comprises the following steps：

A, the SClass according to message, determine the SinkRCode of message；

B, the SinkRCode determined by, according to the SelfRData of setting, determine target NextAddr.

2. according to the method described in claim 1, it is characterised in that set up SClass passes corresponding with SinkRCodeDNism System；Step a is further：According to the SClass of message, SinkRCodeDNism is selected, according to selected SinkRCodeDNism, To determine the SinkRCode of message.

3. method according to claim 2, it is characterised in that pair for setting up SClass and SinkRCodeDNism It should be related to further by setting SCPrefix tables to set up；Step a is further：According to the SClass of the message, According to the SCPrefix tables, best match record is obtained；Judge whether corresponding SinkRCode values are effective, if it is, Using the SinkRCode as message SinkRCode；Otherwise, the SinkRCode is pressed as SinkRCodeDNism_ID According to corresponding SinkRCodeDNism, to determine the SinkRCode of message.

4. method according to claim 2, it is characterised in that pair for setting up SClass and SinkRCodeDNism It should be related to further by setting SCPrefix tables to set up；Step a is further, according to the SClass of message, to look into SCPrefix tables are looked for, judge whether SinkRCode is effective in the record of best match, if it is, the SinkRCode conducts The SinkRCode of message；Otherwise, illustrate that the message includes purpose RCode, then, regard purpose RCode values as message SinkRCode。

5. according to the method described in claim 1, it is characterised in that carry out default setting；Before step b, further sentence Whether the disconnected SinkRCode for determining message operation succeeds, if it fails, then directly determining target according to default setting NextAddr。

6. according to the method described in claim 1, it is characterised in that the message further comprises SinkItem；

Correspondingly, before step a, further comprise：Judge whether the SinkItem of message is effective, if it is, performing step Rapid a, otherwise, directly performs step b；Correspondingly, after step a, further comprise, the SinkItem of message is set For identified SinkRCode.

7. according to any described method in claim 1 to 6, it is characterised in that

Step b is further：According to the SClass of the message and identified SinkRCode, according to setting SelfRData, to determine target NextAddr.

8. method according to claim 7, it is characterised in that step b is further：According to the SClass of the message And identified SinkRCode, RCodeSClass is produced, according to the RCodeSClass of generation, according to setting SelfRData, to determine target NextAddr.

9. one kind exchanges cloud (XCld), for interacting message；The XCld at least includes two XS；It is characterized in that：

In XS, SelfRData is set；Include SClass message to be sent for one, the XS according to the SClass of message, Determine the SinkRCode of message；According to identified SinkRCode, according to the SelfRData of setting, target NextAddr is determined； According to identified target NextAddr, the message is sent.

10. a kind of message addressing method, the message includes SClass and purpose HCode；Characterized in that, this method includes Following steps：

The message for carrying SClass and purpose HCode is sent to this HSvr XCld by a, Source；

B, described HSvr XCld send the message to purpose HSvr XCld according to purpose HCode；

C, the XCld of the purpose HSvr determine the SinkRCode of message according to the SClass；According to identified SinkRCode, according to the SelfRData pre-set, determines target NextAddr；According to identified target NextAddr, Send the message to Sink.