WO2009024020A1

WO2009024020A1 - A server implementing network short message service and the communication method between the server and the clients

Info

Publication number: WO2009024020A1
Application number: PCT/CN2008/001447
Authority: WO
Inventors: Hanmin Yang
Original assignee: Hanmin Yang
Priority date: 2007-08-15
Filing date: 2008-08-11
Publication date: 2009-02-26
Also published as: CN101207579B; CN101207579A

Abstract

The invention discloses a method which realizes the communication between a server and a client in the network short message(NSM) service. A NSM server receives the login of the client, which declares the own user name and the acceptable information title when logging in. Other application programs can send out information to the NSM server, and the information indicts the receiver and the title. The NSM server can instantly transmit the information to the proper client. When the NSM server transmits the information, the network protocol packet source address of the information, which is obtained from the network transmission protocol, is attached. Different titles represent different applications, and the NSM server can serve for the different applications at the same time. Adopting the NSM server of the invention can realize the direct communication (P2P) among the clients. The both parties of the communication do not need other facilities and processes which are specially used to build the P2P, and the both parties of the communication also do not need to care the network addresses thereof, thereby dispensing with the course to inquire a third party the network address of the own party or the opposite party. The communication process is simple and effective.

Description

Server for realizing network short message service and communication method between clients thereof

The present invention relates to a server for implementing NSM Network Short Message service, and more particularly to a server capable of forwarding a network short message in real time. The present invention also relates to a method for communicating between clients based on a network short message server, which can implement direct client communication through a network short message server, also called Peer-to-Peer (P2P) communication. Background technique

The NSM service is a universal real-time forwarding service for network information, which enables instant messaging (IM) and Internet telephony (V0IP). In many cases, direct communication between NSM clients is also possible, also known as Peer-to-Peer (P2P) communication.

The existing Internet instant messaging service is a common service, but these services are usually only one application service. There are many ways to make the forwarding server serve multiple applications at the same time. The most common method is to offload on the client side. This method requires a communication manager on the client side to provide a communication offload interface. However, this method requires all applications of the same username to be in the same computing device, and this approach is also inconvenient for embedded applications.

In addition, the existing methods for establishing Ρ2Ρ communication mainly have the following three treatment methods:

1. US Patent 6108704 Point-to-Point Internet Protocol discloses an implementation of an address server, which is implemented by the client logging in to the address server, and the address server stores the client's IP address and online status. information. When it is necessary to send information to a client, the address server is first queried for the target client state, the address server feeds back the IP address of the target client and the online state information, and then initiates P2P to the target client. This patent mainly includes two technical points: one is to set up an address server, and the other is to feed back the target client address information to the querier through the address server, so that the querier can initiate P2P to the target client address. The address server is only responsible for the address information service of the client, and has no function of forwarding information. When the target client is in the private network, it is difficult to establish P2P communication. 2008/001447

2. Another way of implementing P2P communication is disclosed in US Patent No. 7,227,864 Methods and systems for establishing communications through firewalls and network address translators. The client first logs in to the central server, then forwards the P2P communication request through the central server, and initiates P2P by the client receiving the request. When P2P cannot be successfully established, the other party's address information is obtained by other means, and then P2P is initiated. The patent's central server is only used to assist in establishing P2P, such as forwarding P2P communication requests without forwarding other data. If P2P is not established, inter-client communication requires an additional forwarding server. The patent does not disclose how the client receiving the request obtains the sender's network address in order to initiate P2P. It is also known from the process described in the patent that the originator needs to query the address of the other party from a third party (for example, a central server) to directly initiate P2P.

3. Chinese patent application CN 1881916A - A method and device for realizing communication between communication devices also discloses a method for realizing P2P communication, and the implementation manner thereof is: the connection client first determines the address of the P2P communication (public network address) Or the private network address), and send the address together with the P2P connection request to the central server, the central server forwards the above information to the connected client, and the P2P is initiated by the connected client. It is known from the patent description that the connection party in the private network must query its public network address from a third party (for example, a central server) before the P2P connection request is sent, if the request carries its own public address.

The above three P2P implementations, the first method is simple to operate, but can only initiate P2P communication from one side. Due to the existence of private networks, there are not many opportunities for successful P2P establishment. The latter two patents attempt to improve this problem. From the bilateral launch of P2P communication, the chances of success increase a lot. But the process of obtaining and transmitting their own and the address of the other party is more complicated. In addition, it is more likely that the information should be sent directly to the address of the other party. The above patent methods do not give the best answer. Their success rate in establishing P2P is still not enough. Summary of the invention

One of the technical problems solved by the present invention is to propose a network short message server that can serve a variety of applications. The server for implementing a network short message service, wherein the network short message server is configured to receive a login request from a client, the login request at least: a user name, authentication information, one or more receivable information titles, and a login validity period ;

The network short message server is configured to obtain a network protocol packet source address of the login request from the network transmission protocol as the client network address;

The network short message server is configured to check a login request of the client, and if the verification is passed, the network short message server constructs the client record, and the record includes at least: a login request of the client and the client network address;

The network short message server is further configured to receive information from other applications, the information including at least: one or more recipient user names, one or more information titles, and information content;

The network short message server is configured to obtain a network protocol packet source address of the received information from the network transmission protocol, and use the sender address as the sender address of the information;

The network short message server is configured to combine the received original information and the sender address of the information to construct a new information, and forward the message to a client that meets the following conditions: the recipient user name of the original information includes the username of the client, And the client can receive any one of the information headers whose information header contains the original information;

When the network short message server forwards new information to the client that meets the above conditions, the client network address in the client record is used as the destination address for forwarding new information.

Preferably, the network short message server receives greeting information from the client and other applications, and replies to the server time thereto.

Preferably, the network short message service is further configured to store only a client record of the last one of the clients with the same user name and the same receivable information header client.

Preferably, the network short message server is configured to receive a client login request having only one receivable information header; the network short message server forwards only one recipient name and only one information header.

With the network short message server of the present invention, since the information is offloaded at the server, this is achieved by using the NSM information header. Different apps will use different titles. This is a very simple but effective way to handle it. In addition, the server of the present invention obtains the source address of the network protocol packet of the forwarding information through the underlying transmission protocol, and forwards the network address as the sender of the information to the receiver. After the recipient obtains this address, sending information directly to this address is most likely to be received by the other party. Take

Taking the TCP/IP protocol as an example, the present invention is only a mechanical (and thus a single) IP packet source address for extracting information from the TCP/IP protocol. Whether the sender is on the public network or on the private network. If the sender is on the private network, the source address retrieved is not the actual sender address. The true sender address is not good for establishing P2P unless the communicating parties are in the same network.

The second technical problem solved by the present invention is to propose an inter-client communication method based on a network short message server, which uses the sender address attached when the NSM server forwards information. Try P2P direct communication.

The method for communicating between clients based on the network short message server proposed by the invention includes the following processing:

a) The network short message server to which the communication belongs to each other is logged in, and the address of the network short message server to which the client belongs is known from the client network short message user name;

b) The communication parties forward the information through the network short message server to which the other party belongs, the information includes the other party's network short message user name, the same information title, their own network short message user name and information content;

c) When the client receives the other party's information forwarded by the network short message server to which it belongs, it obtains the network short message user name of the other party, and the sender address of the information attached when the network short message server forwards, and records the sender address of the information. For the direct address of the other party; when sending new information to the other party again, in addition to forwarding the new information through the network short message server to which the other party belongs, the same new information is also sent to the direct address of the other party;

d) In the process of sending information between the two parties, if a party receives the information directly sent by the other party, the P2P is established, and then the P2P communication is used, and the information is no longer forwarded through the network short message server of the other party; When P2P is established, the information is sent directly, and the information is forwarded only through the network short message server of the other party.

With the inter-client communication method of the present invention, the NSM server notifies the recipient of the TCP/IP transport protocol IP packet source address of the received forwarding information as the sender address. Imagine if the NSM server sends a message back to the sender at this address, the sender Can be received. Then, instead of returning the message to the sender by the recipient at this address, it is most likely to be received. And the advantage of using NSM to establish P2P is that the communication parties do not need other facilities (such as central servers) and processes that are specifically used to establish P2P. The two parties do not need to care about their network address. The process of not querying your own or the other party's network address. Both parties to the communication normally use the NSM service to forward information and attempt to establish P2P. If P2P is not established, it does not affect the normal indirect communication of forwarding information through the NSM service. DRAWINGS

1 is a schematic diagram of a login of a client of the present invention to a network short message server;

2 is a schematic diagram of forwarding information of a network short message server to a client according to the present invention; FIG. 3 is a schematic diagram of a method for communicating between clients based on a network short message server according to the present invention. detailed description

First of all, it should be noted that the short message service short message service used in the network short message and the mobile communication terminal of the present invention is not a concept. The network short message of the present invention can be regarded as a short information body and transmitted through the network. The network address mentioned in the present invention is specifically for the TCP/IP network: IP: PORT.

The network short message server of the present invention will be described in detail below through specific embodiments. For convenience of description, the following describes the implementation in TCP/IP UDP communication.

Assume that both the client and server are compute units in a TCP/IP network. Clients can hang directly on the public network, or they can hang on the private network and connect to the public network or the upper private network through a router. When a client in the private network sends information to the outside, the NAT of the router translates the IP packet source address of the information.

A reliable system can be served by the primary and secondary servers, and a simple system can also be a single server. The primary server and backup server function the same, except that their network address (IP:PORT) is different.

Each user has a user name. In this embodiment, the name is of the form: <user id>@<domain name or IP>, column ^ port: yanghm@12.34, 56.78 or 13902904910@headcall.com. Username is also known as NSM username and user NSM address. The server address can be identified by the NSM user name. For example, the server addresses of 13902290910@headcall.com are: nsm.headcall.com (primary server) and nsm2.headcall.com (backup server). A client is a computing unit. It uses an NSM username and an acceptable message header. The information title is shaped like abc or 123 or abc8.headcall.com. Different applications use different information headings so that the server can serve different applications at the same time. For example, iphone.headcall.com is the title used by headcall VoIP, and ichat.headcall.com is the title used by some instant message software.

The login process performed by the client to the server as shown in Figure 1. The login request sent by the client to the server includes: user name, authentication data, message title, login validity period (ie, lifetime). The client should send a new login request during this login lifetime to allow the server to keep the client online.

After receiving the login request, the server obtains the IP packet source address (IP:PORT) of the login request from the underlying network transport protocol as the client network address.

If the login request passes - verification, the server constructs a client record that records the client's login request, the client's network address.

When the client is in the private network, the recorded client network address is not the actual client network address, but the NAT-converted network address. However, the server only needs to record the converted network address and does not need a real client network address.

If the login request passes verification, the server returns a login confirmation to the client. Otherwise, the reason for the login failure is returned. For example: user error, authentication error, or the user has already

(temporary or permanent) transfer. With the temporary transfer feature, you can also construct a server cluster. The login authentication mode supports trivial authentication (that is, password encryption), and also supports SHA (password + challenge code) authentication, and other authentication methods. If the authentication fails, the return message tells the client the authentication method and the required challenge code in addition to the normal authentication. The challenge code is randomly generated and the NSM server will change the challenge code at any time. After receiving the message of the authentication error, the client recalculates the authentication information and issues the login request again. If the server is configured to restrict the use of certain headers, then the reason for the client login failure also includes a header error.

In addition, the request for login to the server through multiple clients has the same username and When the same user can receive the message title, the server only saves the client record of the last login request in those clients, and the previous client record will be discarded.

The client on the left in Figure 1 is the client 201 in the private network 101, and its login is not its native network address 601: 192168.0.12:1089, but the source network address 602 after NAT 102 conversion: 202.96.56.78: 65321. The login request 701 includes the information about the client: The name of the user yanghm@one.com, it can be seen that the address of the server 301 corresponding to the user is nsm.one.com (if there is a backup server, the backup server address is: nsm2 .one.com ). At login, client 201 logs in to the server with the address nsm.one.com (and to nsm2.one.com, if it exists). The information header supported by this client is: yanghm.xyz.com. The TCP/IP transmission protocol will encapsulate the login request 701 with the IP header information, the destination address (the address of the server 301), the source address 601, etc., and the result packet is 401, which is sent to the server 301. The packet 401 is routed to the private network exit and needs to pass through the NAT 102. The NAT has the IP address 203.34.56.78 of the public network 100. The converter NAT 102 converts the source address 601 in the translation packet to 602, and the packet 401 becomes 402, where the login request 701 is unchanged. The server 301 receives the 402 packet, takes out the login information 701 therefrom, and obtains the IP packet source address 602 from the TCP/IP transport protocol. If the login request 701 passes the check, the server 301 saves the login information 701, the same time storage source address 602, and the save record is 501.

The client 203 on the right side of FIG. 1 is a client hanged on the public network 100, and the network address 603 of the login is: 202.96.56.78.2078, and the client name displayed in the login request 703 is: john@one.com, supported. The message title is: headcall.one.com. The TCP/IP transport protocol will include the login request 703 packet, the IP header information, the destination address (the address of the server 301), the source address 603, etc., and the result packet is 403, which is sent to the server 301. The server 301 receives the 403 packet, takes out the login information 703 therefrom, and obtains the IP packet source address 603 from the TCP/IP transport protocol. If the login request 703 passes the check, the server 301 saves the login request 703, the same time storage source address 603, and the record is recorded as 503.

Referring now to Figure 2, it is illustrated how the NSM server forwards information. The other application 801 transmits the information 802 to the client 201 through the NSM server 301. Application The sequence 801 first creates an NSM format packet 805 containing a header 803 (recipient name, message header) and information 802. The TCP/IP transmission protocol encapsulates the 4 bar information 805 packet, adds the IP header information, contains the target address (the address of the server 301), the source address 804, etc., and the packet is 806, and is sent to the server 301 via the public network 100, that is, FIG. 2 The information transmission step in 807. The NSM server 301 receives the 806 packet, extracts the NSM format packet 805 therefrom, and finds the login information 501 of the corresponding client as indicated by the header 803. In addition, the NSM server 301 also obtains the IP packet source address 804 from the TCP/IP transport protocol. The NSM server 301 will add the source address 804 as the sender address 904 to the header 803 to form a new header 903 and a new packet 905. The NSM server 301 then sends this packet 905 to the TCP/IP transport protocol to the client address 908 of the 501 record. TCP/IP will add 905 packets, plus IP header information, including destination address 908, source address (address of server 301), etc., to 906. The IP packet 906 is sent to the NAT 102, i.e., the information transmission step of 907 in FIG. 2, which forwards the packet to the client 201 via the private network 101.

When receiving the information, the NSM server 301 does not care whether the sender is on the public network such as 801 or in the private network such as the client 809. The NSM server will mechanically obtain the IP packet source address of the received information from the TCP/IP transport protocol as its sender network address.

When the NSM server 301 forwards information, it does not care whether the recipient is on the public network such as the client 203 or in the private network such as the client 201. It is also not necessary to know the recipient's local address. It will only mechanically retrieve the forwarded destination address from the login information and forward the information.

If the NSM server fails to forward successfully if the client is offline or for other reasons, the NSM server replies to the sender's network address for the reason for the forwarding failure. This reply must have been received.

In addition, the NSM server also receives greeting messages from clients and other applications and replies to the server time.

The server 301 shown in Figure 1 is the primary server, and can also be replaced with a backup server (if present) to forward information. The process and effect are the same.

For a P2P application based on an NSM server, the NSM server receives only one client login request that can receive the information header; and only the information forwarded by the NSM server A recipient name and only one message title.

The following describes how the inter-client communication method proposed by the present invention is described in detail by how two NSM clients complete the communication process through the NSM server. Refer to Figure 3.

Client B of server NSM-B, which will initiate communication to client A of server NSM-A first. It should be noted that the NSM-A here may be the same server as NSM-B, or it may be a different server. Communication includes the following processes:

1) Clients A, B must first log in to their respective servers (NSM-A, NSM-B).

2) Client B sends the message 01 to the server NSM-A, which contains the user name, message title, own user name and information content of the recipient A.

3) When the server NSM-A forwards the message 01, it adds the IP packet source address of the information 01 obtained from the TCP/IP protocol, adds it as the sender address to the message 01, and the new information is sent to the client. Machine A.

4) After receiving the new information in step 3), client A obtains the NSM user name of client B and also obtains the sender address of the information. The information sender address is recorded as the direct address of client B.

5) When client A continues to send message 02 to client B, the message is forwarded by server NSM-B, and the same information 02P as that of message 02 is sent to the direct address of client B.

6) If client B receives message 02P, then client B knows that direct communication P2P has been established. When the content of the message 03 is resent, the P2P transmission, that is, the information 03P, can be used, and the information N03-A is not required to be forwarded through the server NSM-A. When client A receives the information 03P directly from client B, it knows that the direct communication P2P has been established, and then sends the information to P2P, which does not need to be forwarded by the NSM server.

7) If client B does not receive message 02P, but will definitely receive message 02, client B also obtains the sender address of the message. Record the sender's address as the direct address of A.

8) When client B continues to send message 03 to client A, it forwards the message 03 through the server NSM-A and simultaneously sends the same message 03Po to the direct address of client A. 9) If client A receives message 03P, client A knows that direct communication P2P has been established. When the information is sent again, it can be sent by P2P, and the information does not need to be forwarded through the NSM server. When Client B receives the information directly from Client A, it knows that the Direct Communication P2P has been established.

10) If client A does not receive the message 03P. But now both parties know the direct address of the other party. When sending the message, the information is forwarded through the NSM server of the other party, and the same information is sent to the direct address of the other party. Once P2P communication is established, the information is no longer forwarded through the other NSM server. If P2P cannot be established even if the information is sent to each other multiple times, the information is sent directly and the information is forwarded only through the NSM server of the other party. It is to be understood that the specific implementation of the invention is not limited to the description. It is to be understood by those skilled in the art that the present invention can be deduced or substituted without departing from the spirit and scope of the invention.

Claims

Rights request:

A server for implementing a network short message service, characterized in that

The network short message server is configured to receive a login request from a client, where the login request includes at least: a username, authentication information, one or more receivable information headers, and a login validity period;

The network short message server is configured to combine the received original information and the sender address of the information to construct new information, and forward the message to a client that meets the following conditions: the recipient user name of the original information includes the login request of the client. User name, and the receivable information header in the login request of the client contains any one of the information headers of the original information; when the network short message server forwards the new information to the client that meets the above conditions, the client records The client network address in the address is used as the destination address for forwarding new information.

2. The server for implementing a network short message service according to claim 1, wherein the network short message server receives greeting information from the client and other applications, and replies to the server time thereto.

The server for realizing a network short message service according to claim 1 or 2, wherein the network short message service is further used to save only a plurality of clients having the same user name and the same receivable information title. The last login request in the machine Machine record

The server for implementing a network short message service according to claim 1 or 2, wherein the network short message server is configured to receive a client login request having only one receivable information header; and the network short message server forwards There is only one recipient name and only one message title in the message.

The server for implementing a network short message service according to claim 3, wherein the network short message server is configured to receive a client login request having only one receivable information header; and the information forwarded by the network short message server There is only one recipient name and only one message title.

6. An inter-client communication method based on a network short message server, characterized in that the method comprises the following processing:

a) The network short message server to which the communication belongs to each other is logged in, and the address of the network short message server to which the client belongs is known from the username of the client;