CN104144112A - Message compatibility processing method - Google Patents
Message compatibility processing method Download PDFInfo
- Publication number
- CN104144112A CN104144112A CN201410155559.1A CN201410155559A CN104144112A CN 104144112 A CN104144112 A CN 104144112A CN 201410155559 A CN201410155559 A CN 201410155559A CN 104144112 A CN104144112 A CN 104144112A
- Authority
- CN
- China
- Prior art keywords
- account
- message
- com
- hsvr
- forwarding
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a message compatibility processing method. A forwarding objective account and a forwarding source account are set, so that after receiving a message, an HSvr can determine whether forwarding operation is executed or not according to a source address of the message, the message is prevented from being cyclically forwarded, the purpose that an existing communication protocol is compatible is achieved, and therefore smooth evolution of a communication network is facilitated.
Description
Technical field
The present invention relates to internet communication, relate to or rather the compatible processing method of message.
Background technology
In internet communication, relate to global Unified Identity (GUID, Global Unified Identity), described GUID comprises two parts: ownership code (HCode, Home Code) and user code (UCode, User Code).Wherein, HCode indicates this GUID, also Internet user (the IUsr that this GUID is corresponding, Internet User) belong to instant messaging network (IMN, Instant Messenger Network) which instantaneous communication system (IMS in, Instant Messenger System), and the attribution server (HSvr that belongs to which IMS, Home Server), and belong to which (SP of service provider, Service Provider), UCode is used to indicate different IUsr under a HCode.By setting up the corresponding relation of HCode and HSvr, according to a HCode, can determine HSvr pointed.The < < communication means that more descriptions are 201310037232.X referring to application number and system > > patent of invention.
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), the some HCode for this migration account place HSvr across last HSvr information (CeSvrDesc, Cross-end HSvr Description) of this CDAddr.About more descriptions of CDAddr, the < < that is 201310079118.3 referring to application number supports network and the related news processing method > > patent of invention of GUID migration.
Each AccoAddr consists of an address base (AddrBase, Address Base) and an address ownership (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.
The AddrHome HSvr pointed that the HSvr of an AccoAddr ownership is this AccoAddr.
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.
In the < < multiple terminals reminding method > > patent of invention of submitting to, mention, Liu is for having five accounts: the account of the account of the account of Tencent QQ, Netease 163, the account of the Outlook of Microsoft and Fetion 139, corresponding AccoAddr is respectively 123789@qq.com, liubei@163.com, 13923856563@163.com and liubei@Outlook.com, 13923856563@139.com.For example, but Liu is standby can't login a plurality of accounts of oneself conventionally: when Liu's spare moving terminal is surfed the Net, can login account corresponding to 13923856563@163.com simultaneously; Standby when home PC is surfed the Net as Liu, can login the account that 123789 qq.com are corresponding; Liu is standby to be on duty while surfing the Net with PC, can login account corresponding to 13923856563@139.com; Standby the going on business of Liu can be logined account corresponding to liubei@Outlook.com while surfing the Net with PC.The standby colleague of Liu knows the standby AccoAddr value of Liu 13923856563@139.com, the standby client of Liu knows the AccoAddr value liubei@Outlook.com that Liu is standby, the standby friend of Liu knows the standby AccoAddr value of Liu 123789@qq.com, and the standby household of Liu knows the standby AccoAddr value of Liu 13923856563@163.com.Liu is standby to wish can receive the calling of household to oneself when oneself logins arbitrary account, and especially, Liu is standby also to wish, when oneself logins certain several account simultaneously, can select arbitrary account of logining to receive the calling of household to oneself.This invention by arranging corresponding synchronous account associated description information (SyncAccoDesc in account corresponding to the standby AccoAddr value 13923856563@163.com of Liu, Synchronous Account Descriptin), in the account, receive after a message, according to the destination address of message, determine target account; According to the SyncAccoDesc of target account, to the client of the synchronous account of correspondence, send this message, like this, corresponding client (being called party client end) is received after described message, carries out call reminding operation.For example, in account SyncAccoDesc corresponding to 13923856563@163.com, can comprise AccoAddr value 123789@qq.com, like this, in account corresponding to 13923856563@163.com, receive after message, this message will be forwarded to account corresponding to 123789@qq.com.
But, if in account SyncAccoDesc corresponding to 123789@qq.com, also comprise AccoAddr value 13923856563@163.com, like this, in account corresponding to 123789@qq.com, receive after message, this message will be forwarded to account corresponding to 13923856563@163.com.Like this, just there will be the circulation of message to send.
Certainly, can adopt many modes to eliminate above-mentioned message circulation and send the endless loop possibility causing, for example, when forwarding messages, in message, carrying one forces recipient that terminated flag (or forwarding sign) informs message after receiving this message, no longer carry out corresponding forwarding and operate, but this message that directly terminates.But, can require so corresponding HSvr synchronously to upgrade, this is obviously unfavorable for the smooth evolution of network system.
Summary of the invention
In view of this, the present invention discloses a kind of information compatibility processing method, the method is by arranging or set forwarding object account and the source of forwarding account, make HSvr after receiving a message, can determine whether to carry out to forward according to the source address of this message and operate, to avoid the circulation of message to forward, and then reach the object of compatible existing communication agreement, thereby contribute to the smooth evolution of communication network.
An information compatibility processing method, the method, for an account, arranges and forwards object account and the source of forwarding account; Said method comprising the steps of:
A, HSvr receipt message, determine target account according to the destination address of message;
B, described HSvr judge that this message, whether from the forwarding source account of described target account, if so, performs step c; Otherwise, execution step d;
C: described HSvr ends in described target account by this message;
D, described HSvr send to this message the forwarding object account of described target account.
Step a is further: for an account, ToAccoDesc is set, in order to describe, forwards object account; FromAccoDesc is set, in order to describe forwarding source account.
Step a is further: for an account, SyncAccoDesc attribute is set, in order to describe, forwards object account and the source of forwarding account.
Step a is further: for an account, ToAccoDesc is set, in order to describe, forwards object account; Step b is further: described HSvr judges that whether described message is with base, if so, performs step c; Otherwise, execution step d.
In step a, FromAccoDesc is further set, in order to describe forwarding source account; Step c is further: described HSvr judges the AddrHome that whether is provided with the source address of described message in the FromAccoDesc attribute of described target account, if so, this message is ended in to described target account; Otherwise, directly finish.
Step a is further: for an account, SyncAccoDesc attribute is set, in order to describe, forwards object account and the source of forwarding account; Step c is further: described HSvr judges the AddrHome that whether is provided with the source address of described message in the SyncAccoDesc attribute of described target account, if so, this message is ended in to described target account; Otherwise, directly finish.
In steps d, described HSvr also ends in described target account by described message.
By information compatibility processing method provided by the invention, when avoiding message circulation, do not need all synchronously upgradings of existing HSvr, thereby can reach the object of network smooth evolution.
Accompanying drawing explanation
Shown in Fig. 1, be IMN network example figure.
Shown in Fig. 2, it is execution mode one flow chart of information compatibility processing method of the present invention.
Shown in Fig. 3, be execution mode two flow charts of information compatibility processing method of the present invention.
Shown in Fig. 4, be execution mode three flow charts of information compatibility processing method of the present invention.
Embodiment
For making the object of the invention, technical scheme and advantage clearer, below in conjunction with embodiment, be elaborated in all its bearings.
For ease of explanation, the IMN network that the present invention be take is as shown in Figure 1 example, in the figure:
The HSvr of A service provider (SP-A) is HSvr-A, and wherein, registration has user A(UsrA) and user X(UsrX);
The HSvr of B service provider (SP-B) is HSvr-B, and wherein, registration has user B(UsrB) and user Y(UsrY);
The HSvr of C service provider (SP-C) is HSvr-C, and wherein, registration has user C(UsrC) and user Z(UsrZ);
The HSvr of D service provider (SP-D) is HSvr-D, and wherein, registration has user D(UsrD) and user O(UsrO).
Wherein, SP-A is that Tengxun, SP-B are that Netease, SP-C are that Microsoft, SP-D are Fetions.HCode value qq.com belongs to HSvr-A, and HCode value 163.com belongs to HSvr-B, and HCode value Outlook.com belongs to HSvr-C, and HCode value 139.com belongs to HSvr-D etc.
Usually, in an accounts information, can comprise AddrBase, Password, ClientIP and the ClientPort of these attributes: AccoAddr or AccoAddr, etc.Wherein, the password that Password is proper account, the online information that ClientIP and ClientPort are proper account.When an account is when logining state, IP address and the port numbers of the client of corresponding ClientIP and ClientPort corresponding account; When the account is when publishing state, usually, corresponding ClientIP and/or ClientPort are null value null or 0.
Described HSvr can obtain IP address and the port numbers of corresponding client when the login of account, and in ClientIP and ClientPort attribute that the IP address obtaining and port numbers are kept to the account.
About more descriptions of accounts information referring to described < < communication means and system > > patent of invention.
Described HSvr can preserve by accounts information table as shown in table 1 the accounts information of proper account.
Table 1
| AccoAddr | Password | ClientIP | ClientPort |
| caocao@163.com | ******** | Corresponding IP address | Respective end slogan |
| liubei@163.com | ******** | Corresponding IP address | Respective end slogan |
| zhangliao@163.com | ******** | Corresponding IP address | Respective end slogan |
| 13923856563@163.com | ******** | Corresponding IP address | Respective end slogan |
Certainly, if the port numbers of unified agreement client,, in table 1, ClientPort attribute can save.
According to table 1, corresponding HSvr can determine corresponding account according to an AccoAddr.
As shown in Figure 2, be execution mode one flow chart of information compatibility processing method of the present invention, in the figure,
First in step 11, for an account: arrange and forward object account and the source of forwarding account.
Step 12, HSvr receipt message, determine target account according to the destination address of message.
Step 13, described HSvr judge that this message, whether from the forwarding source account of described target account, if so, performs step 14; Otherwise, execution step 15.
Step 14, described HSvr end in described target account by this message.
Step 15, described HSvr send to described message the forwarding object account of described target account.
In step 14, described this message is ended in to described target account can be: described HSvr sends to this message the client of this target account.For example, this message is for sending a short message.
In step 15, can further include: described HSvr ends in described target account by described message.
In the middle of reality, the set-up mode that forwards object account and the source of forwarding account has varied.Below according to being illustrated forwarding object account and the setting of the source of forwarding account and the difference of limiting mode.
For convenience of explanation and understand, the present invention uses a kind of message format, and this message format comprises address list (MsgAddrList, Messasge Address List) and message body (MsgBody, Messasge Body), use branch between the two "; " cut apart.Like this, a message can be write as { MsgAddrList; MsgBody } form.
In MsgAddrList, at least comprise an address.First address (being called MsgAddr1) of MsgAddrList is the destination address of message.
If the address in MsgAddrList is more than one: second address (being called MsgAddr2) of MsgAddrList is the source address of message, and the original sender that last address of MsgAddrList is message is also initial sender's address.
While there is a plurality of address in MsgAddrList, between each address, use comma, " cut apart, like this, message general type is { MsgAddr1, MsgAddr2; MsgBody }, or be { MsgAddr1, MsgAddr2, MsgAddr3; MsgBody }, etc.
If the destination address of a message and source address with base, claim that this message is with base message, otherwise, claim that this message is different base message.
Step 11 is further: for an account: the associated description information (ToAccoDesc, To Account Descriptin) of corresponding forwarding object account is set, in order to describe, forwards object account; The associated description information (FromAccoDesc, From Account Descriptin) of corresponding forwarding source account is set, in order to describe forwarding source account.
With in corresponding accounts information, increase ToAccoDesc attribute and FromAccoDesc attribute, be respectively used to indicate the account corresponding forwarding object account and the source of forwarding account be example.
When the ToAccoDesc of account attribute is null value null, represent that the account does not have corresponding forwarding object account; When the FromAccoDesc of account attribute is null value null, represent that the account does not have corresponding forwarding source account.
With { the corresponding AccoAddr that forwards object account of the account is directly set in the ToAccoDesc of account attribute, the AccoAddr of corresponding forwarding of account source account is directly set in the FromAccoDesc of account attribute, }, it is example.
Can preserve ToAccoDesc attribute and the FromAccoDesc attribute of proper account by forwarding account description list is set.Referring to forwarding account description list as shown in table 2:
Table 2
Known according to table 2, in account corresponding to AccoAddr value 13923856563@163.com, in ToAccoDesc attribute, be provided with four AccoAddr:13923856563@139.com, liubei@Outlook.com, 123789@qq.com and liubei@163.com that forward object account; In FromAccoDesc attribute, be provided with four AccoAddr:13923856563@139.com, liubei@Outlook.com, 123789@qq.com and liubei@163.com that forward source account.
The AccoAddr that AddrBase is identical is same base address, and the account that AddrBase is identical is called same base account.
In table 2, if described forwarding object account or forwarding source account and current account, with base, can only arrange the AddrHome of corresponding forwarding object account or the source of forwarding account.For example, 13923856563@139.com and 13923856563@163.com are with base, therefore, can be by the ToAccoDesc attribute of 13923856563@163.com corresponding accounts, or in FromAccoDesc attribute, AccoAddr value 13923856563@139.com replace to corresponding AddrHome value 139.com.
In step 13, described judge that whether this message from the forwarding source account of described target account can be: the source address that is provided with described message in the FromAccoDesc attribute judging whether in described target account, if so, illustrate that this message comes from the forwarding source account of described target account; Otherwise, be not.
If what preserve in the FromAccoDesc attribute of an account is the AddrHome value of the same base account of the account, in step 13, described judge that whether this message from the forwarding source account of described target account can be: judge whether to meet that { this message is with base, and in the FromAccoDesc of this target account attribute, be provided with the AddrHome value of the source address of this message } condition, if so, illustrate that this message comes from the forwarding source account of described target account; Otherwise, be not.For example, in the FromAccoDesc attribute of 13923856563@163.com corresponding accounts, be provided with AddrHome value 139.com, being used to indicate the account that 13923856563@139.com are corresponding is corresponding forwarding source account.Like this, receiving that destination address is 13923856563@163.com, source address is the message of 13923856563@139.com, and determined after target account according to the destination address of this message, just can judge whether to meet that { the source address 13923856563@139.com of this message and the destination address 13923856563@163.com of this message are with base, and in the FromAccoDesc of this target account attribute, be provided with the AddrHome value 139.com of 13923856563@139.com } this condition, because this message is with base, and in the FromAccoDesc of this target account attribute, be provided with AddrHome value 139.com, therefore, illustrate that this message comes from the forwarding source account of described target account.
In step 15, described HSvr determines corresponding forwarding object account according to the ToAccoDesc property value of described target account, sends to these to forward object account described message.
Above be provided with ToAccoDesc attribute and the FromAccoDesc attribute of 13923856563@163.com corresponding account in HSvr-B in the forwarding account description list shown in table 2.
Equally, HSvr-A arranges ToAccoDesc attribute and the FromAccoDesc attribute of 123789@qq.com corresponding accounts by forwarding account description list as shown in table 2.Referring to showing 2-A:
Table 2-A
Equally, HSvr-C arranges ToAccoDesc attribute and the FromAccoDesc attribute of liubei@Outlook.com corresponding account by forwarding account description list as shown in table 2.Referring to showing 2-C:
Table 2-C
Equally, HSvr-D arranges ToAccoDesc attribute and the FromAccoDesc attribute of 13923856563@139.com corresponding accounts by forwarding account description list as shown in table 2.Referring to showing 2-D:
Table 2-D
The AccoAddr of example 1: Guan Yunchang is guanyunchang Outlook.com, Guan Yunchang has logined account corresponding to guanyunchang Outlook.com, Guan Yunchang according to standby AccoAddr value 13923856563 163.com of Liu to Liu standby send short message " eldest brother is fine recently! ", process is as follows:
The client structure message of step 101, Guan Yunchang: { 13923856563 163.com, guanyunchang Outlook.com; Message body }, this message is sent to HSvr-C.Here, the destination address of this message is 13923856563@163.com, and source address is guanyunchang@Outlook.com, and message body has comprised short message content, and " eldest brother is fine recently! ".
Step 102, HSvr-C receive after described message, judge that the destination address of message belongs to HSvr-B, so, this message is sent to HSvr-B.
Step 103, HSvr-B receive after described message, according to the destination address of message, determine target account, this message are sent to the client of this target account.
Step 104, HSvr-B judge that described message is whether from the forwarding source account of described target account, because the FromAccoDesc attribute of this target account does not arrange AccoAddr value guanyunchang@Outlook.com, therefore, HSvr-B confirms that this message is not the forwarding source account that comes from this target account, so HSvr-B carries out message and forwards operation: according to four that arrange in the ToAccoDesc attribute of this target account AccoAddr values that forward object accounts: 13923856563@139.com; Liubei@Outlook.com; 123789@qq.com; Liubei@163.com, carries out respectively the operation that the client that forwards object account to each sends this message:
Judgement liubei@163.com belongs to oneself, so the destination address using liubei@163.com as this message obtains message: { liubei@163.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is processed as the new message receiving: determine liubei@163.com corresponding account, the FromAccoDesc of judgement liubei@163.com corresponding account has comprised the source address 13923856563@163.com of described message, therefore, directly this message is sent to the client of liubei@163.com corresponding account.
Judge that 13923856563@139.com belong to HSvr-D, so, destination address using 13923856563@139.com as this message obtains message: { 13923856563@139.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-D.
Judgement liubei@Outlook.com belongs to HSvr-C, so, destination address using liubei@Outlook.com as this message obtains message: { liubei@Outlook.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-C.
Judge that 123789@qq.com belong to HSvr-A, so the destination address using 123789@qq.com as this message obtains message: { 123789@qq.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-A.
Step 105, comprise following 3 operations:
A, HSvr-D receive after described message, according to the destination address 13923856563@139.com of message, determine target account, because the source address 13923856563@163.com of this message have setting in the FromAccoDesc of this target account attribute, so, judge the forwarding source address that this message comes from target account, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account;
B, HSvr-C receive after described message, according to the destination address liubei@Outlook.com of message, determine target account, because the source address 13923856563@163.com of this message have setting in the FromAccoDesc of this target account attribute, so, judge the forwarding source address that this message comes from target account, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account;
C, HSvr-A receive after described message, according to the destination address 123789@qq.com of message, determine target account, because the source address 13923856563@163.com of this message have setting in the FromAccoDesc of this target account attribute, so, judge the forwarding source address that this message comes from target account, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account.
In step 103, HSvr-B is according to AccoAddr value 13923856563@163.com, from accounts information table as shown in table 1, corresponding target account can be determined, from the forwarding account description list shown in table 2, corresponding ToAccoDesc attribute and FromAccoDesc attribute can be determined.
It should be noted that, in step 101, in the MsgAddrList of described message, also can not comprise source address, or the source address comprising is a null value null.Like this, in step 102, HSvr-C receives after described message, obtains corresponding source address, and the second address of the MsgAddrList using the source address of obtaining as this message is filled up in described message.
For example, described step 101 is directly the client structure message of step 101B: Guan Yunchang: { 13923856563 163.com; Message body }, this message is sent to HSvr-C.Here, the destination address of this message is 13923856563@163.com, default source address.Correspondingly, described step 102 is further that step 102B:HSvr-C receives after described message, obtain corresponding source address, the second address using the source address guanyunchang@Outlook.com obtaining as the MsgAddrList of this message is filled up in this message, the message obtaining is: { 13923856563@163.com, guanyunchang@Outlook.com; Message body }; The destination address of judgement message belongs to HSvr-B, so, the message obtaining is sent to HSvr-B.
In step 102B, HSvr-C is when receiving the message that calling terminal sends, can obtain IP address and the port numbers of calling terminal, according to IP address and the port numbers of calling terminal, from accounts information table as described in Table 1, determine corresponding Account History, the source address using the AccoAddr value of determined record as described message.
One, the restricted usage of the first of the present invention
In this restricted usage, require the ToAccoDesc property value of an account and the FromAccoDesc property value of the account consistent.
In this restriction usage, with a synchronous account associated description information (SyncAccoDesc, Synchronous AccountDescriptin) attribute, represent corresponding ToAccoDesc and two attributes of FromAccoDesc simultaneously.
For example, can substitute with synchronous account description list as shown in table 3 forwarding account description list as shown in table 2.
Table 3
In table 3, when SyncAccoDesc value is null, illustrate that corresponding account does not have synchronous account,, both do not forwarded object account yet, do not forward source account yet.
In table 3, in the SyncAccoDesc attribute of AccoAddr value 13923856563@163.com corresponding accounts, be provided with AccoAddr:13923856563@139.com, liubei@Outlook.com, 123789@qq.com and the liubei@163.com of four synchronous accounts, four that have described the account forward object account and four forwarding source accounts.
Step 11 is further: for an account: SyncAccoDesc attribute is set, in order to describe, forwards object account and the source of forwarding account.
In the middle of reality, those skilled in the art are by above-mentioned execution mode one or embodiment 1, forwarding account description list as shown in table 2 is replaced into synchronous account description list as shown in table 3, and by corresponding ToAccoDesc and FromAccoDesc all simple substitute be SyncAccoDesc, can obtain the described restricted usage of the first.
In forwarding account description list for example,, shown in table 3, be provided with the SyncAccoDesc attribute of 13923856563@163.com corresponding account in HSvr-B.
Equally, HSvr-A arranges the SyncAccoDesc attribute of 123789@qq.com corresponding accounts by forwarding account description list as shown in table 3.Referring to showing 3-A:
Table 3-A
Equally, HSvr-C arranges the SyncAccoDesc attribute of liubei@Outlook.com corresponding account by forwarding account description list as shown in table 3.Referring to showing 3-C:
Table 3-C
Equally, HSvr-D arranges the SyncAccoDesc attribute of 13923856563@139.com corresponding accounts by forwarding account description list as shown in table 3.Referring to showing 3-D:
Table 3-D
For example: step 104 further: HSvr-B judges that described message is whether from the forwarding source account of described target account, because the SyncAccoDesc attribute of this target account does not arrange AccoAddr value guanyunchang@Outlook.com, therefore, HSvr-B confirms that this message is not the forwarding source account that comes from this target account, so HSvr-B carries out message and forwards operation: according to four that arrange in the SyncAccoDesc attribute of this target account AccoAddr values that forward object accounts: 13923856563@139.com; Liubei@Outlook.com; 123789@qq.com; Liubei@163.com, carries out respectively the operation that the client that forwards object account to each sends this message:
Judgement liubei@163.com belongs to oneself, so the destination address using liubei@163.com as this message obtains message: { liubei@163.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is processed as the new message receiving: determine liubei@163.com corresponding account, the SyncAccoDesc of judgement liubei@163.com corresponding account has comprised the source address 13923856563@163.com of described message, therefore, directly this message is sent to the client of liubei@163.com corresponding account.
Judge that 13923856563@139.com belong to HSvr-D, so, destination address using 13923856563@139.com as this message obtains message: { 13923856563@139.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-D.
Judgement liubei@Outlook.com belongs to HSvr-C, so, destination address using liubei@Outlook.com as this message obtains message: { liubei@Outlook.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-C.
Judge that 123789@qq.com belong to HSvr-A, so the destination address using 123789@qq.com as this message obtains message: { 123789@qq.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-A.
Also for example, step 105 is further:
A, HSvr-D receive after described message, according to the destination address 13923856563@139.com of message, determine target account, because the source address 13923856563@163.com of this message have setting in the SyncAccoDesc of this target account attribute, so, judge the forwarding source address that this message comes from target account, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account;
B, HSvr-C receive after described message, according to the destination address liubei@Outlook.com of message, determine target account, because the source address 13923856563@163.com of this message have setting in the SyncAccoDesc of this target account attribute, so, judge the forwarding source address that this message comes from target account, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account;
C, HSvr-A receive after described message, according to the destination address 123789@qq.com of message, determine target account, because the source address 13923856563@163.com of this message have setting in the SyncAccoDesc of this target account attribute, so, judge the forwarding source address that this message comes from target account, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account.
Two, the restricted usage of the second of the present invention
In this restricted usage, require an account and its forwarding source account with base.Take { the forwarding source account that all same base account of described account is all the account } be example, after the judgement source address of a message and destination address are with base, just no longer carry out the corresponding operation that forwards, like this, in an accounts information, FromAccoDesc attribute can be do not comprised, thereby better technique effect can be reached.
Step 11 is further: for an account, ToAccoDesc attribute is set, in order to describe, forwards object account.
Step 13 is further: described HSvr judges that whether described message is with base, if so, performs step 14; Otherwise, execution step 15.
As shown in Figure 3, be execution mode two flow charts of information compatibility processing method of the present invention, in the figure,
First in step 21, for an account, ToAccoDesc attribute is set, in order to describe to forward object account.Here, take { the same base account that the forwarding object account of described account is the account } be example, but be not used in restriction.
When the ToAccoDesc of account attribute is null value null, represent that the account does not have corresponding forwarding object account.
Take { the corresponding AddrHome that forwards object account of the account is directly set in the ToAccoDesc of account attribute } be example, but be not used in restriction the present invention.
Can preserve the ToAccoDesc attribute of proper account by forwarding account description list is set.Referring to as the forwarding account description list of table as shown in 2B:
Table 2B
In table 2B, in the ToAccoDesc attribute of AccoAddr value 13923856563@163.com corresponding accounts, be provided with three AddrHome:139.com, Outlook.com and qq.com that forward object account such as 13923856563@139.com, 13923856563@Outlook.com and 13923856563@qq.com.
Step 22, HSvr receipt message, determine target account according to the destination address of message.
Step 23, described HSvr judge that whether described message is with base, if so, perform step 24; Otherwise, execution step 25.
Step 24, described HSvr end in described target account by this message.
Step 25, described HSvr send to this message the forwarding object account of described target account.
In step 24, described this message is ended in to described target account can be: described HSvr sends to this message the client of this target account.For example, this message is for sending a short message.
In step 25, described HSvr determines corresponding forwarding object account according to the ToAccoDesc property value of described target account, sends to these to forward object account described message.For example, the AccoAddr of described target account is 13923856563@163.com, described HSvr is HSvr-B, HSvr-B is according to the ToAccoDesc property value of described target account: 139.com, Outlook.com and qq.com, AddrBase value 13923856563 with this target account, obtain respectively forwarding the AccoAddr value of object account: 13923856563@139.com, 13923856563@Outlook.com and 13923856563@qq.com, the AccoAddr value that forwards object account according to these, sends described message.
In step 25, can further include: described HSvr ends in described target account by described message.
Show to be provided with in the forwarding account description list shown in 2B the ToAccoDesc attribute of 13923856563@163.com corresponding account in HSvr-B above.
Equally, HSvr-A arranges the ToAccoDesc attribute of 13923856563@qq.com corresponding accounts by the forwarding account description list as shown in table 2B.Referring to showing 2B-A:
Table 2B-A
Equally, HSvr-C arranges the ToAccoDesc attribute of 13923856563@Outlook.com corresponding accounts by the forwarding account description list as shown in table 2B.Referring to showing 2B-C:
Table 2B-C
Equally, HSvr-D arranges the ToAccoDesc attribute of 13923856563@139.com corresponding accounts by the forwarding account description list as shown in table 2B.Referring to showing 2B-D:
Table 2B-D
The AccoAddr of example 2: Guan Yunchang is guanyunchang Outlook.com, Guan Yunchang has logined account corresponding to guanyunchang Outlook.com, Guan Yunchang according to standby AccoAddr value 13923856563 163.com of Liu to Liu standby send short message " eldest brother is fine recently! ", process is as follows:
The client structure message of step 201, Guan Yunchang: { 13923856563 163.com, guanyunchang Outlook.com; Message body }, this message is sent to HSvr-C.Here, the destination address of this message is 13923856563@163.com, and source address is guanyunchang@Outlook.com, and message body has comprised short message content, and " eldest brother is fine recently! ".
Step 202, HSvr-C receive after described message, judge that the destination address of message belongs to HSvr-B, so, this message is sent to HSvr-B.
Step 203, HSvr-B receive after described message, according to the destination address of message, determine target account, this message are sent to the client of this target account.
Step 204, HSvr-B judges that whether described message is with base, because the source address guanyunchang@Outlook.com of this message and destination address 13923856563@163.com are not with base, therefore, HSvr-B confirms that this message is not the forwarding source account that comes from this target account, so, HSvr-B carries out message and forwards operation: according to three that arrange in the ToAccoDesc attribute of this target account AddrHome:139.com that forward object account, Outlook.com and qq.com, AddrBase value 13923856563 with this target account, obtain respectively forwarding the AccoAddr value of object account: 13923856563@139.com, 13923856563@Outlook.com and 13923856563@qq.com, carry out respectively the operation that the client that forwards object account to each sends this message:
Judge that 13923856563@139.com belong to HSvr-D, so, destination address using 13923856563@139.com as this message obtains message: { 13923856563@139.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-D.
Judge that 13923856563@Outlook.com belong to HSvr-C, so, destination address using 13923856563@Outlook.com as this message obtains message: { 13923856563@Outlook.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-C.
Judge that 13923856563@qq.com belong to HSvr-A, so, destination address using 13923856563@qq.com as this message obtains message: { 13923856563@qq.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-A.
Step 205, comprise following 3 operations:
A, HSvr-D receive after described message, according to the destination address 13923856563@139.com of message, determine target account, because the source address 13923856563@163.com of this message and destination address 13923856563@139.com are with base, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account;
B, HSvr-C receive after described message, according to the destination address 13923856563@Outlook.com of message, determine target account, because the source address 13923856563@163.com of this message and destination address 13923856563@Outlook.com are with base, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account;
C, HSvr-A receive after described message, according to the destination address 13923856563@qq.com of message, determine target account, because the source address 13923856563@163.com of this message and destination address 13923856563@qq.com are with base, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account.
It should be noted that, in step 201, in the MsgAddrList of described message, also can not comprise source address, or the source address comprising is a null value null.Like this, in step 202, HSvr-C receives after described message, obtains corresponding source address, and the second address of the MsgAddrList using the source address of obtaining as this message is filled up in described message.
For example, described step 201 is directly the client structure message of step 201B: Guan Yunchang: { 13923856563 163.com; Message body }, this message is sent to HSvr-C.Here, the destination address of this message is 13923856563@163.com, default source address.Correspondingly, described step 202 is further that step 202B:HSvr-C receives after described message, obtain corresponding source address, the second address using the source address guanyunchang@Outlook.com obtaining as the MsgAddrList of this message is filled up in this message, the message obtaining is: { 13923856563@163.com, guanyunchang@Outlook.com; Message body }; The destination address of judgement message belongs to HSvr-B, so, the message obtaining is sent to HSvr-B.
In step 202B, HSvr-C is when receiving the message that calling terminal sends, can obtain IP address and the port numbers of calling terminal, according to IP address and the port numbers of calling terminal, from accounts information table as described in Table 1, determine corresponding Account History, the source address using the AccoAddr value of determined record as described message.
In order to strengthen the fail safe that between same base account, message forwards, preferably, in an accounts information, FromAccoDesc attribute is also set, in order to describe forwarding source account.
About same base account synchronization mechanism with the associated description of base account interoperability, participate in described < < with informing mechanism implementation method > > patent of invention between base account.
Three, the third restricted usage of the present invention
In this restricted usage, based on the restricted usage of the second, further to forwarding source account, limit.
Step 11 is still: for an account: ToAccoDesc attribute is set, in order to describe, forwards object account; FromAccoDesc attribute is set, in order to describe forwarding source account.
Step 13 is further: described HSvr judges that whether described message is with base, if so, performs step 14, otherwise, perform step 15.
Step 14 is further: described HSvr judges the AddrHome that whether is provided with the source address of described message in the FromAccoDesc attribute of described target account, if so, this message is ended in to described target account; Otherwise, directly finish.
As shown in Figure 4, be execution mode three flow charts of information compatibility processing method of the present invention, in the figure,
First in step 31, for an account: ToAccoDesc attribute is set, in order to describe, forwards object account; FromAccoDesc attribute is set, in order to describe forwarding source account.Here, take { the same base account that the forwarding object account of described account is the account } be example, but be not used in restriction.
When the ToAccoDesc of account attribute is null value null, represent that the account does not have corresponding forwarding object account; When the FromAccoDesc of account attribute is null value null, represent that the account does not have corresponding forwarding source account.
With { the corresponding AddrHome that forwards object account of the account is directly set in the ToAccoDesc of account attribute, the AddrHome of corresponding forwarding of account source account is directly set in the FromAccoDesc of account attribute }, it is example.
Can preserve ToAccoDesc attribute and the FromAccoDesc attribute of proper account by forwarding account description list is set.Referring to as the forwarding account description list of table as shown in 2C:
Table 2C
In table 2C, when ToAccoDesc value is null, illustrate that corresponding account does not forward object account; When FromAccoDesc value is null, illustrate that corresponding account does not forward source account.
According to table, 2C is known, in account corresponding to AccoAddr value 13923856563@163.com, in ToAccoDesc attribute and FromAccoDesc attribute, be all provided with three AddrHome value: 139.com, Outlook.com and qq.com that AccoAddr value 13923856563@139.com, 13923856563@Outlook.com and 13923856563@qq.com etc. are corresponding; .
Step 32, HSvr receipt message, determine target account according to the destination address of message.
Step 33, described HSvr judge that whether described message is with base, if so, perform step 34, otherwise, perform step 35.
Step 34, described HSvr judge the AddrHome that whether is provided with the source address of described message in the FromAccoDesc attribute of described target account, if so, this message are ended in to described target account; Otherwise, directly finish.
Step 35, described HSvr send to this message the forwarding object account of described target account.
In step 34, described this message is ended in to described target account can be: described HSvr sends to this message the client of this target account.For example, this message is for sending a short message.
In step 35, described HSvr determines corresponding forwarding object account according to the ToAccoDesc property value of described target account, sends to these to forward object account described message.For example, the AccoAddr of described target account is 13923856563@163.com, described HSvr is HSvr-B, HSvr-B is according to the ToAccoDesc property value of described target account: 139.com, Outlook.com and qq.com, AddrBase value 13923856563 with this target account, obtain respectively forwarding the AccoAddr value of object account: 13923856563@139.com, 13923856563@Outlook.com and 13923856563@qq.com, the AccoAddr value that forwards object account according to these, sends described message.
In step 35, can further include: described HSvr ends in described target account by described message.
Show to be provided with in the forwarding account description list shown in 2C ToAccoDesc attribute and the FromAccoDesc attribute of 13923856563@163.com corresponding account in HSvr-B above.
Equally, HSvr-A arranges ToAccoDesc attribute and the FromAccoDesc attribute of 13923856563@qq.com corresponding accounts by the forwarding account description list as shown in table 2C.Referring to showing 2C-A:
Table 2C-A
Equally, HSvr-C arranges ToAccoDesc attribute and the FromAccoDesc attribute of 13923856563@Outlook.com corresponding accounts by the forwarding account description list as shown in table 2C.Referring to showing 2C-C:
Table 2C-C
Equally, HSvr-D arranges ToAccoDesc attribute and the FromAccoDesc attribute of 13923856563@139.com corresponding accounts by the forwarding account description list as shown in table 2C.Referring to showing 2C-D:
Table 2C-D
The AccoAddr of example 3: Guan Yunchang is guanyunchang Outlook.com, Guan Yunchang has logined account corresponding to guanyunchang Outlook.com, Guan Yunchang according to standby AccoAddr value 13923856563 163.com of Liu to Liu standby send short message " eldest brother is fine recently! ", process is as follows:
The client structure message of step 301, Guan Yunchang: { 13923856563 163.com, guanyunchang Outlook.com; Message body }, this message is sent to HSvr-C.Here, the destination address of this message is 13923856563@163.com, and source address is guanyunchang@Outlook.com, and message body has comprised short message content, and " eldest brother is fine recently! ".
Step 302, HSvr-C receive after described message, judge that the destination address of message belongs to HSvr-B, so, this message is sent to HSvr-B.
Step 303, HSvr-B receive after described message, according to the destination address of message, determine target account, this message are sent to the client of this target account.
Step 304, HSvr-B judges that whether described message is with base, because the source address guanyunchang@Outlook.com of this message and destination address 13923856563@163.com are not with base, so, HSvr-B carries out message and forwards operation: according to three that arrange in the ToAccoDesc attribute of this target account AddrHome:139.com that forward object account, Outlook.com and qq.com, AddrBase value 13923856563 with this target account, obtain respectively forwarding the AccoAddr value of object account: 13923856563@139.com, 13923856563@Outlook.com and 13923856563@qq.com, carry out respectively the operation that the client that forwards object account to each sends this message:
Judge that 13923856563@139.com belong to HSvr-D, so, destination address using 13923856563@139.com as this message obtains message: { 13923856563@139.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-D.
Judge that 13923856563@Outlook.com belong to HSvr-C, so, destination address using 13923856563@Outlook.com as this message obtains message: { 13923856563@Outlook.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-C.
Judge that 13923856563@qq.com belong to HSvr-A, so, destination address using 13923856563@qq.com as this message obtains message: { 13923856563@qq.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-A.
Step 305, comprise following 3 operations:
A, HSvr-D receive after described message, according to the destination address 13923856563@139.com of message, determine target account, because the source address 13923856563@163.com of this message and destination address 13923856563@139.com are with base, and the AddrHome of 13923856563@163.com has setting in the FromAccoDesc of this target account attribute, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account;
B, HSvr-C receive after described message, according to the destination address 13923856563@Outlook.com of message, determine target account, because the source address 13923856563@163.com of this message and destination address 13923856563@Outlook.com are with base, and the AddrHome of 13923856563@163.com has setting in the FromAccoDesc of this target account attribute, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account;
C, HSvr-A receive after described message, according to the destination address 13923856563@qq.com of message, determine target account, because the source address 13923856563@163.com of this message and destination address 13923856563@qq.com are with base, and the AddrHome of 13923856563@163.com has setting in the FromAccoDesc of this target account attribute, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account.
It should be noted that, in step 301, in the MsgAddrList of described message, also can not comprise source address, or the source address comprising is a null value null.Like this, in step 302, HSvr-C receives after described message, obtains corresponding source address, and the second address of the MsgAddrList using the source address of obtaining as this message is filled up in described message.
For example, described step 301 is directly the client structure message of step 301B: Guan Yunchang: { 13923856563 163.com; Message body }, this message is sent to HSvr-C.Here, the destination address of this message is 13923856563@163.com, default source address.Correspondingly, described step 302 is further that step 302B:HSvr-C receives after described message, obtain corresponding source address, the second address using the source address guanyunchang@Outlook.com obtaining as the MsgAddrList of this message is filled up in this message, the message obtaining is: { 13923856563@163.com, guanyunchang@Outlook.com; Message body }; The destination address of judgement message belongs to HSvr-B, so, the message obtaining is sent to HSvr-B.
In step 302B, HSvr-C is when receiving the message that calling terminal sends, can obtain IP address and the port numbers of calling terminal, according to IP address and the port numbers of calling terminal, from accounts information table as described in Table 1, determine corresponding Account History, the source address using the AccoAddr value of determined record as described message.
Four, the 4th kind of restricted usage of the present invention
In this restricted usage, based on above-mentioned the third restricted usage, further require the ToAccoDesc property value of an account and the FromAccoDesc property value of the account consistent.Also be the forwarding object account of described account and to forward source account be all the same base account of the account, and the ToAccoDesc property value of the account and the FromAccoDesc property value of the account consistent.
In this restriction usage, with a SyncAccoDesc attribute, represent corresponding ToAccoDesc and two attributes of FromAccoDesc simultaneously.
For example, can substitute with the synchronous account description list as shown in table 3B the forwarding account description list as shown in table 2C.
Table 3B
In table 3B, when SyncAccoDesc value is null, illustrate that corresponding account does not have synchronous account,, do not forward object account yet, do not forward source account yet.
In table 3, in the SyncAccoDesc attribute of AccoAddr value 13923856563@163.com corresponding accounts, be provided with 13923856563@qq.com; 13923856563@Outlook.com; Three AddrHome:qq.com with base account such as 13923856563@139.com; Outlook.com; 139.com, for indication three forwarding object accounts and three the forwarding source accounts of the account.
Step 11 is further: for an account: SyncAccoDesc attribute is set, in order to describe, forwards object account and the source of forwarding account.
Step 13 is further: described HSvr judges that whether described message is with base, if so, performs step 14, otherwise, perform step 15.
Step 14 is further: described HSvr judges the AddrHome that whether is provided with the source address of described message in the SyncAccoDesc attribute of described target account, if so, this message is ended in to described target account; Otherwise, directly finish.
In the middle of reality, those skilled in the art are by above-mentioned execution mode three or embodiment 3, as show the forwarding account description list as shown in 2C and be replaced into as the synchronous account description list of table as shown in 3B, and by corresponding ToAccoDesc and FromAccoDesc all simple substitute be SyncAccoDesc, can obtain the 4th kind of described restricted usage.
For example, step 31 further: for an account: SyncAccoDesc attribute is set, in order to describe, forwards object account and the source of forwarding account.
Also for example, step 34 further: described HSvr judges the AddrHome that whether is provided with the source address of described message in the SyncAccoDesc attribute of described target account, if so, this message is ended in to described target account; Otherwise, directly finish.
For example, show to be provided with in the forwarding account description list shown in 3B the SyncAccoDesc attribute of 13923856563@163.com corresponding account in HSvr-B above.
Equally, HSvr-A arranges the SyncAccoDesc attribute of 13923856563@qq.com corresponding accounts by the forwarding account description list as shown in table 3B.Referring to showing 3B-A:
Table 3B-A
Equally, HSvr-C arranges the SyncAccoDesc attribute of 13923856563@Outlook.com corresponding accounts by the forwarding account description list as shown in table 3B.Referring to showing 3B-C:
Table 3B-C
Equally, HSvr-D arranges the SyncAccoDesc attribute of 13923856563@139.com corresponding accounts by the forwarding account description list as shown in table 3B.Referring to showing 3B-D:
Table 3B-D
For example, step 304 is further: HSvr-B judges that whether described message is with base, because the source address guanyunchang@Outlook.com of this message and destination address 13923856563@163.com are not with base, so, HSvr-B carries out message and forwards operation: according to three that arrange in the SyncAccoDesc attribute of this target account AddrHome:139.com that forward object account, Outlook.com and qq.com, AddrBase value 13923856563 with this target account, obtain respectively forwarding the AccoAddr value of object account: 13923856563@139.com, 13923856563@Outlook.com and 13923856563@qq.com, carry out respectively the operation that the client that forwards object account to each sends this message:
Judge that 13923856563@139.com belong to HSvr-D, so, destination address using 13923856563@139.com as this message obtains message: { 13923856563@139.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-D.
Judge that 13923856563@Outlook.com belong to HSvr-C, so, destination address using 13923856563@Outlook.com as this message obtains message: { 13923856563@Outlook.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-C.
Judge that 13923856563@qq.com belong to HSvr-A, so, destination address using 13923856563@qq.com as this message obtains message: { 13923856563@qq.com, 13923856563@163.com, guanyunchang@Outlook.com; Message body }, this message is sent to HSvr-A.
Also for example, step 305 is further:
A, HSvr-D receive after described message, according to the destination address 13923856563@139.com of message, determine target account, because the source address 13923856563@163.com of this message and destination address 13923856563@139.com are with base, and the AddrHome of 13923856563@163.com has setting in the SyncAccoDesc of this target account attribute, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account;
B, HSvr-C receive after described message, according to the destination address 13923856563@Outlook.com of message, determine target account, because the source address 13923856563@163.com of this message and destination address 13923856563@Outlook.com are with base, and the AddrHome of 13923856563@163.com has setting in the SyncAccoDesc of this target account attribute, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account;
C, HSvr-A receive after described message, according to the destination address 13923856563@qq.com of message, determine target account, because the source address 13923856563@163.com of this message and destination address 13923856563@qq.com are with base, and the AddrHome of 13923856563@163.com has setting in the SyncAccoDesc of this target account attribute, so, directly this message is ended in to this target account, also, this message is sent to the client of this target account.
The restricted usage of the second of the present invention is more succinct than the flow process of the 4th kind of restricted usage, but the fail safe of the 4th kind of restricted usage is better.For example, consider with the synchronization mechanism between base account, or with better fail safes such as the interoperability between base account, preferably, adopt the 4th kind of restricted usage.Technical staff, in the middle of reality, can select according to service needed.
These are only better embodiment of the present invention or embodiment, 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 modification of doing, improve, be equal within replacement etc. all should be included in protection scope of the present invention.
Claims (7)
1. an information compatibility processing method, is characterized in that, for an account, arranges and forwards object account and the source of forwarding account; Said method comprising the steps of:
A, HSvr receipt message, determine target account according to the destination address of message;
B, described HSvr judge that this message, whether from the forwarding source account of described target account, if so, performs step c; Otherwise, execution step d;
C: described HSvr ends in described target account by this message;
D, described HSvr send to this message the forwarding object account of described target account.
2. method according to claim 1, is characterized in that, step a further: for an account, ToAccoDesc is set, in order to describe to forward object account; FromAccoDesc is set, in order to describe forwarding source account.
3. method according to claim 1, is characterized in that, step a further: for an account, SyncAccoDesc attribute is set, in order to describe to forward object account and the source of forwarding account.
4. method according to claim 1, is characterized in that, step a further: for an account, ToAccoDesc is set, in order to describe to forward object account; Step b is further: described HSvr judges that whether described message is with base, if so, performs step c; Otherwise, execution step d.
5. method according to claim 4, is characterized in that, in step a, FromAccoDesc is further set, in order to describe forwarding source account; Step c is further: described HSvr judges the AddrHome that whether is provided with the source address of described message in the FromAccoDesc attribute of described target account, if so, this message is ended in to described target account; Otherwise, directly finish.
6. method according to claim 5, is characterized in that, step a further: for an account, SyncAccoDesc attribute is set, in order to describe to forward object account and the source of forwarding account; Step c is further: described HSvr judges the AddrHome that whether is provided with the source address of described message in the SyncAccoDesc attribute of described target account, if so, this message is ended in to described target account; Otherwise, directly finish.
7. according to the either method described in claim 1 to 6, it is characterized in that, in steps d, described HSvr also ends in described target account by described message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410155559.1A CN104144112A (en) | 2013-05-11 | 2014-04-18 | Message compatibility processing method |
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310173402.7 | 2013-05-11 | ||
| CN201310173402 | 2013-05-11 | ||
| CN201410155559.1A CN104144112A (en) | 2013-05-11 | 2014-04-18 | Message compatibility processing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104144112A true CN104144112A (en) | 2014-11-12 |
Family
ID=51853181
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410155559.1A Pending CN104144112A (en) | 2013-05-11 | 2014-04-18 | Message compatibility processing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104144112A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020112187A1 (en) * | 2000-09-11 | 2002-08-15 | Transnexus, Inc. | Clearinghouse server for internet telephony and multimedia communications |
| CN1859323A (en) * | 2005-12-22 | 2006-11-08 | 华为技术有限公司 | Method and device for realizing pocket transmission news service |
| CN101902699A (en) * | 2009-05-31 | 2010-12-01 | 中兴通讯股份有限公司 | Message number-based message processing method and device |
| CN102595348A (en) * | 2012-02-20 | 2012-07-18 | 华为技术有限公司 | Method for acquiring forwarding report of massages, device of sender and massage handling system |
-
2014
- 2014-04-18 CN CN201410155559.1A patent/CN104144112A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020112187A1 (en) * | 2000-09-11 | 2002-08-15 | Transnexus, Inc. | Clearinghouse server for internet telephony and multimedia communications |
| CN1859323A (en) * | 2005-12-22 | 2006-11-08 | 华为技术有限公司 | Method and device for realizing pocket transmission news service |
| CN101902699A (en) * | 2009-05-31 | 2010-12-01 | 中兴通讯股份有限公司 | Message number-based message processing method and device |
| CN102595348A (en) * | 2012-02-20 | 2012-07-18 | 华为技术有限公司 | Method for acquiring forwarding report of massages, device of sender and massage handling system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11012527B2 (en) | Managing multiple profiles for a single account in an asynchronous messaging system | |
| US7016307B2 (en) | Method and system for finding related nodes in a social network | |
| CN101317474B (en) | Message conversion equipment, system and conversion method | |
| US9247401B2 (en) | Signature control for SMS | |
| CN103457828B (en) | The instant communication method and system of a kind of inter-network | |
| CN102223293B (en) | The method for routing of message request and treatment system | |
| US10075408B2 (en) | Managing messaging sessions among multiple participants | |
| CN101400023A (en) | Method and device for realizing multimedia message service | |
| CN102130845A (en) | Method for transmitting return receipt report and processing system | |
| CN103095549B (en) | The method and system of message transmission between a kind of JICQ | |
| CN102255897A (en) | IM (Instant Message) system and instant communication method based on WAP (Wireless Application Protocol) technology | |
| CN105847131B (en) | E-mail sending method and system, outgoing mail server, mail reception server | |
| CN106921555B (en) | User account defining method for cross-network instant messaging | |
| CN104144112A (en) | Message compatibility processing method | |
| US7894835B2 (en) | Method, system and devices for processing messages in multimedia messaging service | |
| CN104184647A (en) | Social e-mail communication system and method | |
| CN109218162B (en) | Mail delivery method and device | |
| CN103391333A (en) | Network supporting GUID (Global Unified Identity) migration and relevant message process methods | |
| CN1322725C (en) | Method for receiving and transmitting e-mail using digital number and its mail system | |
| CN1984083A (en) | Method and system for notifying instant-message in electronic bulletin edition system | |
| CN107317741A (en) | It is a kind of to support while connecting the instant communication client of multiserver | |
| CN102638415A (en) | Butt joint method of instant communication and electronic mail | |
| US10798039B2 (en) | Intelligent real-time SMTP routing | |
| CN109218163B (en) | Mail delivery method and server | |
| CN101237428A (en) | Method, system and server for establishing multi-party session based on instant messaging group |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C53 | Correction of patent of invention or patent application | ||
| CB02 | Change of applicant information |
Address after: Wuhou District Shaoling road Chengdu city Sichuan province 610000 No. 29 2-2-3 Li Huaijiang Applicant after: Wang Zhengwei Address before: 610000 Sichuan city in Chengdu province Wuhou Temple Street No. 87 (empty Jiashuyuan) 1 Building 1 unit 3 Applicant before: Wang Zhengwei |
|
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20141112 |