CN100370770C - Method for implementing long connection changeover of network - Google Patents
Method for implementing long connection changeover of network Download PDFInfo
- Publication number
- CN100370770C CN100370770C CNB2004100083227A CN200410008322A CN100370770C CN 100370770 C CN100370770 C CN 100370770C CN B2004100083227 A CNB2004100083227 A CN B2004100083227A CN 200410008322 A CN200410008322 A CN 200410008322A CN 100370770 C CN100370770 C CN 100370770C
- Authority
- CN
- China
- Prior art keywords
- server
- client
- real server
- address
- real
- 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.)
- Expired - Fee Related
Links
Images
Abstract
The present invention discloses a method for realizing a long connection changeover of a network. The method comprises: establishing at least virtual service, and corresponding to a server group which is composed of at least one real server and has the same service function; setting an identifier word for the virtual service so as to identity the variation of the real server in the server group; judging whether the state of the real server has the variation according to the identifier word; establishing the connection of a client and the real server when the state of the real server is normal; realizing the long connection changeover according to the identifier word when the state of the real server is changed. By using the present invention, whole flow rate can be still averagely allocated to different servers when the states of the servers are changed, and moreover, the long connection changeover realized by network load equalizing equipment is ensured after the servers return to normal.
Description
Technical field
The present invention relates to network interconnection technique field, be specifically related to a kind of Chief Web Officer of realizing and connect the method for switching.
Background technology
Along with development of internet technology, networking and application are advanced by leaps and bounds, the network user constantly increases, network load balancing device also is applied in the network of all trades and professions more and more, present load-balancing device has all been realized the load sharing for network traffics, promptly utilize multiple algorithm with total flowing of access mean allocation to different servers.And also has corresponding health testing mechanism, if certain real server is unavailable, the flow that then is connected on this equipment will be by on the server of sharing other, load-balancing device can be re-assigned to network traffics on this server after this station server can normally move again, but these flows are not to be the unavailable flow that is connected before on this server of server.In some special dimension (such as bank, security etc.), client can be sent length and be connected to server: set up TCP (transmission control protocol) and connect not chain rupture afterwards, remain connection status.These long connection requests are assigned on the different servers, if a station server is unavailable then client software can initiate to connect again, load-balancing device can be assigned to this connection on the new server, after original disabled server recovers normally, requirement will originally be connected on this server, be assigned to the connection chain rupture on the new server at present, reconnect to then on this server.
Present load-balancing device has all just been realized the load sharing for flow, when server available-＞unavailable-＞after changing between available these two states, a part of flow can be reconnected to the server that recovers normal condition, guarantee the load balancing of each server, but but can't accomplish original flow is reconnected on the server that recovers normal condition, like this, after one playscript with stage directions has the server of load to lose efficacy, load is all transferred on other servers, after the server that lost efficacy is reworked, owing to there be not new long the connection to produce (because all being long the connection), so this server will be in the state that does not have load, as illusory always.Just can't use in some application like this.
Summary of the invention
The objective of the invention is to overcome the above-mentioned shortcoming of prior art, provide a kind of Chief Web Officer of realizing to connect the method switch so that when status change appears in server whole flow still can mean allocation to different effective servers.
A kind of Chief Web Officer of realizing connects the method for switching, and described method comprises step:
A, set up at least one empty service, corresponding server group of forming by at least one real server with same services function;
B, be identifier word of described empty service initialization, with the variation of real server in the sign corresponding server group;
C, judge according to described identifier word whether described real server state changes;
D, when described real server state does not change, set up being connected of client and described real server by network load balancing device;
E, when described real server state changes, realize long switching of connecting according to the allocation result of pre-defined algorithm distribution server.
Described step D comprises:
The information of D1, the described empty service of configuration on described network load balancing device and the information of described real server, and set up corresponding relation between them;
D2, set up being connected of client and described real server according to the empty information on services and the corresponding relation of real server information of described foundation.
Described step D1 comprises:
The information that disposes described empty service comprises: IP address, port numbers and the protocol number of empty service;
The information that disposes described real server comprises: IP address, port numbers and the protocol number of real server.
Described step D2 comprises:
D21, described client initiate access request to described empty service;
D22, described network load balancing device find the corresponding server group according to described access request, and are that described client requests is distributed a real server by pre-defined algorithm;
D23, set up being connected of real server of described client and described distribution.
Described pre-defined algorithm comprises: source IP address hash algorithm, purpose IP address hash algorithm, source IP address and purpose IP address hash algorithm.
Described step D23 comprises:
D231, the corresponding relation tabulation of setting up client and server according to the information of the real server of first packet message information and described distribution in the described access request for this connection;
D232, be connected the real server of described client and described distribution with the corresponding relation tabulation of server according to the client of described foundation.
Described step D231 comprises: when the corresponding relation tabulation of setting up described client and server, write down current described identifier word.
The tabulation of the corresponding relation of described client and server comprises: the source of client access/purpose IP address, source/destination slogan and client agreement number, and the address of the real server of described distribution and port numbers; Source/purpose IP the address of the real server back message using that distributes, source/destination slogan and service device protocol number, and described back message using need be replaced behind the described network load balancing device of process source IP address and source port number.
Described step e comprises:
E1, when there being real server to become available or when newly adding real server, change described identifier word in the described empty service by unavailable;
After E2, described network load balancing device are received the subsequent packet of the empty service of client access, if the identifier word of record is different in the tabulation of the corresponding relation of current identifier word and described client and server, then utilize described pre-defined algorithm to redistribute a real server.
Described step e 2 comprises:
If the information of record is identical in the tabulation of the corresponding relation of E21 allocation result and described client and server, then directly transmit described subsequent packet to described real server;
If the information of record is different in the tabulation of the corresponding relation of E22 allocation result and described client and server, the client who then deletes described foundation tabulates with the corresponding relation of server;
E23, receive client's subsequent packet once more when described network load balancing device after, can not find out the corresponding relation tabulation of corresponding client and server, respond the message that resets then for described client, notify the user to rebulid connection.
Provide a kind of Chief Web Officer of realizing to connect the method switch so that when status change appears in server whole flow still can mean allocation to different effective servers.
Utilize the present invention, not only guaranteed server when state variation occurring whole flow still can mean allocation to different effective servers, and after server recovers normally, if there is not new server to add this network, then will originally switch back on this server corresponding to long connection of this server by network load balancing device, if when having new server to add this network, that then realizes long connection redistributes the equilibrium of proof load; Simultaneously, the present invention also makes network load balancing device support length connect switch function, has reliably realized the backup between the server, has fully guaranteed the safety of long connection data.
Description of drawings
Fig. 1 is the schematic diagram that following three client computer of normal condition are connected with two servers respectively;
Fig. 2 be among Fig. 1 a station server unavailable after All Clients all be connected to situation schematic diagram on another station server;
Fig. 3 is the situation schematic diagram that original connection is reconnected to this server after disabled server among Fig. 2 recovers normally;
Fig. 4 is a flow chart of being set up client and server step of connecting in the inventive method by network load balancing device;
Fig. 5 is a schematic flow sheet of setting up signal in the real server connection procedure of client and distribution in the flow process shown in Figure 4;
Fig. 6 realizes the long flow chart that connects the step of switching by network load balancing device in the inventive method.
Embodiment
In order to make those skilled in the art person understand the present invention better, the present invention is described in further detail below in conjunction with drawings and embodiments.
With reference to Fig. 1, Fig. 2 and Fig. 3, the realization thinking of the inventive method is: under normal circumstances, use pre-defined algorithm to select real server, client computer Client1 is connected to server S erver2, client computer Client2 and Client3 are connected to server S erver1, as shown in Figure 1; After server S erver2 is unavailable for a certain reason, client computer Client1 will disconnect with being connected of server S erver2, client computer Client1 initiates to connect again then, so because the unavailable server S erver1 that is connected to of server S erver2, as shown in Figure 2; Network load balancing device can be initiatively be connected disconnections of client computer Client1 with server S erver1 after server S erver2 recovers operate as normal, then by client computer Client1 initiate again connection also finally and server S erver2 connect.
The present invention utilizes network load balancing device to realize switching of Chief Web Officer connection, when having server to break down, to be switched on other effective server corresponding to long connection of this server, after this server recovers normally, will originally switch back on this server again corresponding to long connection of this server.When having new server to add described network, also to redistribute the long corresponding server that connects.In all changes process of above-mentioned server, remain the equilibrium of offered load.
The present invention program comprises with the lower part:
(1) sets up at least one empty service, corresponding server group of forming by at least one real server with same services function.That is to say,, one or more real server with same services function are formed one group, the corresponding empty service of each server group with the real server in the format management network of group.
(2) be identifier word of empty service initialization, with the variation of real server in the identification server group.
(3) judge according to described identifier word whether described real server state changes.
(4) when true server state just often, set up being connected of client and real server by network load balancing device.
(5) when true server state changes, realize long switching of connecting according to described identifier word.
Introduce respectively under the real server state normal condition below in conjunction with accompanying drawing and to set up the process that is connected of client and real server and the real server state back that changes by network load balancing device and realize the long process of switching that connects by this equipment.
With reference to Fig. 4, Fig. 4 has described the flow chart of being set up client and server step of connecting by network load balancing device.
Step 401: on network load balancing device, dispose the information of empty service and the information of real server, and set up the corresponding relation between them.Wherein, the information of empty service comprises: IP address, port numbers and the protocol number of empty service; The information of real server comprises: IP address, port numbers and the protocol number of real server.
Step 402: the client initiates access request to described empty service.
Step 403: network load balancing device finds the corresponding server group according to access request, and is that client requests is distributed a real server by pre-defined algorithm.Be after network load balancing device is received the first packet of the empty service of client access, judge whether purpose IP address, destination slogan and protocol number mate empty relevant configuration of serving in the message, if coupling is then distributed a real server according to predetermined algorithm for this is connected in this void service corresponding server group.Such as, can be according to the source IP address hash algorithm, purpose IP address hash algorithm, source IP address and purpose IP address hash algorithm distribute a real server for this is connected in this void service corresponding server group.
Step 404: tabulate according to the corresponding relation that the information of the real server of first packet message information and distribution in the access request is set up client and server for this connection, and in this table, write down current identifier word.This table comprises following information: the source of client access/purpose IP address, source/destination slogan and client agreement number, and the address of the real server of described distribution and port numbers; Source/purpose IP the address of the real server back message using that distributes, source/destination slogan and service device protocol number, and described back message using need be replaced behind the described network load balancing device of process source IP address and source port number.
Step 405: the real server that is connected client and distribution according to the client who sets up with the corresponding relation tabulation of server.That is: after the subsequent packet of client's side arrived network load balancing device, network load balancing device obtained the address and the port numbers of corresponding real server according to the corresponding relation tabulation of information matches client in the subsequent packet and server; Then the purpose IP address in the subsequent packet and destination slogan are replaced with the address and the port numbers of corresponding real server, and the message after will replacing is transmitted to the real server of correspondence.Equally, after real server sends to network load balancing device with result, network load balancing device is according to the corresponding relation tabulation of information matches client in the back message using and server, obtain source IP address and source port number that corresponding back message using need be replaced, and the source IP address in the back message using and source port number replaced with the IP address of corresponding void service and the port numbers of empty service, and the message after will replacing is transmitted to described client.Like this, the client just can't know the true address of server, has guaranteed the safety of server.
In above-mentioned steps 404, also can set up the corresponding relation of client and server in accordance with the following methods, such as, set up a pair of Cache (high-speed cache): client Cache and server end Cache according to the information of the real server of first packet message information and distribution in the access request for this connection.Wherein, client Cache content comprises: the source of client access/purpose IP address, source/destination slogan and protocol number, and the address and the port numbers of the real server that distributes; Server end Cache content comprises: the source of the real server back message using of distribution/purpose IP address, source/destination slogan and protocol number, and back message using need be replaced behind the process network load balancing device source IP address and source port number.
Then, Cache is connected the real server of client and distribution according to this that set up.That is: after the subsequent packet of client's side arrived network load balancing device, network load balancing device obtained the address and the port numbers of corresponding real server according to the information matches client Cache in the subsequent packet; Then the purpose IP address in the subsequent packet and destination slogan are replaced with the address and the port numbers of real server corresponding among the client Cache, and the message after will replacing is transmitted to the real server of correspondence.Equally, after real server sends to network load balancing device with result, network load balancing device is according to the information matches server end Cache in the back message using, obtain source IP address and source port number that corresponding back message using need be replaced, and the source IP address in the back message using and source port number replaced with the IP address of void service corresponding among the server end Cache and the port numbers of empty service, and the message after will replacing is transmitted to described client.
Signal flow as shown in Figure 5 in the above-mentioned connection procedure.
Refer again to Fig. 5, Fig. 5 has described the flow process of signal in the real server connection procedure of setting up client and distribution among Fig. 4:
1. the client sends request message to network load balancing device;
2. network load balancing device is replaced empty service IP address and empty service port number with real server IP address and port numbers, and client requests is mail to real server;
3. real server sends result and responds the client;
4. network load balancing device is replaced real server IP address and port numbers with empty service IP address and port numbers, will visit the result and mail to access customer.
Describe under the real server state normal condition process that is connected of setting up client and real server by network load balancing device above in detail.
If for a certain reason, make certain real server unavailable, then be connected to originally this server on the client will disconnect, again initiate connection request then, network load balancing device can be that new connection is set up in new request by pre-defined algorithm according to present effectively server, guarantee whole flow still can mean allocation to different server.Detailed process is: load equalizer can be with all deletions of corresponding relation tabulation of client relevant with this server and server after detecting server failure.Receive the corresponding relation tabulation that can't match corresponding client and server behind client's the subsequent packet, load equalizer sends RST (resetting) message and gives the client, after the client receives the RST message, can initiate connection request at once again.And the server response RST message that needn't break down by the time, perhaps the client retransmits message according to Transmission Control Protocol, connects up to overtime the reconstruction again.Improved and switched efficient.Load-balancing device is redistributed effective real server for this request, sets up new connection according to flow process shown in Figure 4.If there are a plurality of servers to break down in the network simultaneously, it also is the same handling, as long as there is effective server, load balancing will be assigned on all effective servers.
After unavailable server recovers normally again, can realize switching long the connection by network load balancing device.Specifically comprise: if there is not new server to add this network, then can be with originally long connection the corresponding to this server switched back on this server the equilibrium of proof load; If there is new server to add this network,, redistribute the long corresponding server that connects for the equilibrium of proof load.
Introduction by the front is learnt, network load balancing device is to carry out with the form of group for the management of real server, that is to say, all real server during a void is served are counted as one group, and be that each such server is set up upright global variable, just above-mentioned identifier word, at every turn in this group certain real server by unavailable become available or have new server to add just this value is added 1.At first in this tabulation, write down this value receiving when client's first packet is set up the corresponding relation tabulation of client and server, will check all at every turn when receiving subsequent packet then whether this value of this value in this tabulation and current system is identical.If identical, illustrate that then real server does not have status change, do not handle, direct this message of transmitting got final product after only need be replaced empty service IP address and empty service port number with real server IP address and port numbers; If inequality, illustrate that then the real server state in the server group changes, two kinds of situations are arranged: or have new server to add this group, or have the server that breaks down to recover normal again in this group.At this moment need to utilize pre-defined algorithm to redistribute a real server.If the result of record is the same in current result calculated and this tabulation, illustrate that then allocation result is identical, do not need to handle, this message of forwarding gets final product only to need to replace after empty service IP address and the empty service port number directly with real server IP address and port numbers; If the result of record is different in current result calculated and this tabulation, then two conditions that change corresponding to identifier word show equally two kinds of situations: if there is new server to add this server group, in order to make load balancing, need redistribute current load; If there is the server that breaks down to recover again normally in this group, then need and will switch back on this server long connection the corresponding to this server originally, the equilibrium of proof load simultaneously distributes.At this moment to initiatively delete the corresponding relation tabulation of the client that set up and server.When receiving client's subsequent packet once more,, rebulid connection so can respond a RST (resetting) message notifying client to the client owing to corresponding relation tabulation that can not find out corresponding client and server is not again a first packet simultaneously.After the client receives the RST message, can initiate again to connect, current connection will be selected previously used server or initiate server.Like this, both realize switching of long connection, guaranteed the equilibrium of flow again.Its detailed process is referring to Fig. 6.
Fig. 6 describes in detail in the inventive method and realizes the long flow process that connects the step of switching by network load balancing device:
Step 601: network load balancing device receives client's subsequent packet;
Step 602: judge whether the corresponding relation tabulation of existing corresponding client and server;
If no, then enter step 604: respond the RST message to the client, notify the client to rebulid connection;
If have, then enter step 603: judge whether identifier word changes, whether the identifier word of record was identical with the server group id word of present system during just relatively the corresponding relation of client and server was tabulated;
If identical, then enter step 607: directly transmit subsequent packet after replacing empty service IP address and empty service port number with real server IP address and port numbers;
If inequality, then enter step 605: redistribute a real server by pre-defined algorithm;
Then, enter step 606: whether the record in judging allocation result and the corresponding relation of client and server being tabulated is identical;
If identical, then enter step 607: directly transmit subsequent packet after replacing empty service IP address and empty service port number with real server IP address and port numbers;
If inequality, then enter step 608: client that deletion has been set up and the tabulation of the corresponding relation of server.
When receiving client's subsequent packet once more owing to can not find out the corresponding relation of corresponding client and server and tabulate, not again first packet simultaneously, then respond a RST message to the client, the client can initiate to connect after receiving the RST message again, and load-balancing device guarantees to distribute previously used server or initiate server for current the connection according to pre-defined algorithm.
Once repeatedly mentioned in the foregoing description when connecting, need distribute a real server according to predetermined algorithm by network load balancing device for client and real server.In the present invention, also utilize this pre-defined algorithm to guarantee that same client recovers to distribute under the normal situation same server at server.Illustrate the realization of this algorithm below.With IP address hash algorithm is example:
Suppose to have three real server A, B, C, set two threshold value a1, a2 so, when receiving client's message, client's IP address (can be source IP address, purpose IP address, source IP address and purpose IP address) extracted and carry out the Hash computing and obtain a value, algorithm guarantees that the value that same address computation obtains is unique, compare with two threshold value a1, a2 setting with this value then, just select A less than a1, just select B less than a2, just select C greater than a2 greater than a1.If server B is unavailable with regard to only remaining A and C, the also only surplus next a1 of corresponding threshold value, after server B is recovered normally, still B is put in the middle of A and the C, recover a1 simultaneously, two threshold values of a2 so just can guarantee that the client who connected it after server recovers normal condition last time can also choose this server.
Though described the present invention by embodiment, those of ordinary skills know, the present invention has many distortion and variation and do not break away from spirit of the present invention, wish that appended claim comprises these distortion and variation and do not break away from spirit of the present invention.
Claims (10)
1. realize that Chief Web Officer connects the method for switching, and is characterized in that described method comprises step for one kind:
A, set up at least one empty service, corresponding server group of forming by at least one real server with same services function;
B, be identifier word of described empty service initialization, with the variation of real server in the sign corresponding server group;
C, judge according to described identifier word whether described real server state changes;
D, when described real server state does not change, set up being connected of client and described real server by network load balancing device;
E, when described real server state changes, realize long switching of connecting according to the allocation result of pre-defined algorithm distribution server.
2. realization Chief Web Officer as claimed in claim 1 connects the method for switching, and it is characterized in that described step D comprises:
The information of D1, the described empty service of configuration on described network load balancing device and the information of described real server, and set up corresponding relation between them;
D2, set up being connected of client and described real server according to the empty information on services and the corresponding relation of real server information of described foundation.
3. realization Chief Web Officer as claimed in claim 2 connects the method for switching, and it is characterized in that described step D1 comprises:
The information that disposes described empty service comprises: IP address, port numbers and the protocol number of empty service;
The information that disposes described real server comprises: IP address, port numbers and the protocol number of real server.
4. connect the method for switching as claim 2 or 3 described realization Chief Web Officers, it is characterized in that described step D2 comprises:
D21, described client initiate access request to described empty service;
D22, described network load balancing device find the corresponding server group according to described access request, and are that described client requests is distributed a real server by pre-defined algorithm;
D23, set up being connected of real server of described client and described distribution.
5. realization Chief Web Officer as claimed in claim 4 connects the method for switching, and it is characterized in that described pre-defined algorithm comprises: source IP address hash algorithm, purpose IP address hash algorithm, source IP address and purpose IP address hash algorithm.
6. realization Chief Web Officer as claimed in claim 4 connects the method for switching, and it is characterized in that described step D23 comprises:
D231, the corresponding relation tabulation of setting up client and server according to the information of the real server of first packet message information and described distribution in the described access request for this connection;
D232, be connected the real server of described client and described distribution with the corresponding relation tabulation of server according to the client of described foundation.
7. realization Chief Web Officer as claimed in claim 6 connects the method for switching, and it is characterized in that described step D231 comprises: when the corresponding relation tabulation of setting up described client and server, write down current described identifier word.
8. realization Chief Web Officer as claimed in claim 6 connects the method for switching, it is characterized in that, the tabulation of the corresponding relation of described client and server comprises: the source of client access/purpose IP address, source/destination slogan and client agreement number, and the address of the real server of described distribution and port numbers; Source/purpose IP the address of the real server back message using that distributes, source/destination slogan and service device protocol number, and described back message using need be replaced behind the described network load balancing device of process source IP address and source port number.
9. realization Chief Web Officer as claimed in claim 8 connects the method for switching, and it is characterized in that described step e comprises:
E1, when there being real server to become available or when newly adding real server, change described identifier word in the described empty service by unavailable;
After E2, described network load balancing device are received the subsequent packet of the empty service of client access, if the identifier word of record is different in the tabulation of the corresponding relation of current identifier word and described client and server, then utilize described pre-defined algorithm to redistribute a real server.
10. realization Chief Web Officer as claimed in claim 9 connects the method for switching, and it is characterized in that described step e 2 comprises:
If the information of record is identical in the tabulation of the corresponding relation of E21 allocation result and described client and server, then directly transmit described subsequent packet to described real server;
If the information of record is different in the tabulation of the corresponding relation of E22 allocation result and described client and server, the client who then deletes described foundation tabulates with the corresponding relation of server;
E23, receive client's subsequent packet once more when described network load balancing device after, can not find out the corresponding relation tabulation of corresponding client and server, respond the message that resets then for described client, notify the user to rebulid connection.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100083227A CN100370770C (en) | 2004-03-03 | 2004-03-03 | Method for implementing long connection changeover of network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100083227A CN100370770C (en) | 2004-03-03 | 2004-03-03 | Method for implementing long connection changeover of network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1665206A CN1665206A (en) | 2005-09-07 |
| CN100370770C true CN100370770C (en) | 2008-02-20 |
Family
ID=35036105
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100083227A Expired - Fee Related CN100370770C (en) | 2004-03-03 | 2004-03-03 | Method for implementing long connection changeover of network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100370770C (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103368841B (en) * | 2012-03-29 | 2016-08-17 | 深圳市腾讯计算机系统有限公司 | Message forwarding method and device |
| CN104092650B (en) * | 2013-12-04 | 2018-04-03 | 腾讯数码（天津）有限公司 | A kind of method and apparatus for distributing service request |
| CN103795642B (en) * | 2014-01-24 | 2017-04-19 | 北京京东尚科信息技术有限公司 | Load balancing method and device |
| EP3404896B1 (en) * | 2016-01-12 | 2022-03-09 | Fujitsu Limited | Wireless communication device, wireless communication system, and wireless communication method |
| CN107317830B (en) * | 2016-04-26 | 2021-05-18 | 中兴通讯股份有限公司 | Service discovery processing method and device |
| CN107438012B (en) * | 2016-05-27 | 2020-07-28 | 北京金山云网络技术有限公司 | Load balancing service forwarding method, system, balancing device and host machine |
| CN107026907B (en) * | 2017-03-30 | 2020-08-14 | 广东红餐科技有限公司 | Load balancing method, load balancer and load balancing system |
| CN108200218B (en) * | 2018-03-09 | 2021-11-26 | 北京奇艺世纪科技有限公司 | Method and device for realizing load balance and electronic equipment |
| CN109936635B (en) * | 2019-03-12 | 2021-09-28 | 北京百度网讯科技有限公司 | Load balancing method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1202772A (en) * | 1997-05-30 | 1998-12-23 | 国际商业机器公司 | Dynamic routing in internet |
| US5938732A (en) * | 1996-12-09 | 1999-08-17 | Sun Microsystems, Inc. | Load balancing and failover of network services |
| CN1322315A (en) * | 1998-10-09 | 2001-11-14 | 国际商业机器公司 | Load balancing cooperatig cache servers |
| CN1372405A (en) * | 2001-02-26 | 2002-10-02 | 阿瓦雅通信以色列有限公司 | Go-on sustained connection |
-
2004
- 2004-03-03 CN CNB2004100083227A patent/CN100370770C/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5938732A (en) * | 1996-12-09 | 1999-08-17 | Sun Microsystems, Inc. | Load balancing and failover of network services |
| CN1202772A (en) * | 1997-05-30 | 1998-12-23 | 国际商业机器公司 | Dynamic routing in internet |
| CN1322315A (en) * | 1998-10-09 | 2001-11-14 | 国际商业机器公司 | Load balancing cooperatig cache servers |
| CN1372405A (en) * | 2001-02-26 | 2002-10-02 | 阿瓦雅通信以色列有限公司 | Go-on sustained connection |
Non-Patent Citations (1)
| Title |
|---|
| 使用NAT实现Linux虚拟服务器. 吴进，刘雁飞.西安邮电学院学报，第8卷第3期. 2003 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1665206A (en) | 2005-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10868840B1 (en) | Multiple-master DNS system | |
| US11184299B2 (en) | Hierarchical publish and subscribe system | |
| JP6883427B2 (en) | Diameter load and overload information and methods for virtualization, system and computer readable media | |
| US20170070457A1 (en) | Multiplexed demand signaled distributed messaging | |
| EP2066101B1 (en) | System and method for an improved high availability component implementation | |
| US9235829B2 (en) | Hierarchical publish/subscribe system | |
| US9269080B2 (en) | Hierarchical publish/subscribe system | |
| CN106453136B (en) | The method and apparatus for establishing message queue | |
| CN106030542A (en) | Proxy server failover and load clustering | |
| US9762405B2 (en) | Hierarchical publish/subscribe system | |
| CN101364889B (en) | Method for multicast user quick access | |
| US9569753B2 (en) | Hierarchical publish/subscribe system performed by multiple central relays | |
| KR20120088744A (en) | Method and system for application level load balancing in a publish/subscribe message architecture | |
| CN112671928B (en) | Equipment centralized management architecture, load balancing method, electronic equipment and storage medium | |
| CN100370770C (en) | Method for implementing long connection changeover of network | |
| CN106453669A (en) | Load balancing method and server | |
| CN107682442A (en) | A kind of Web connection methods and device | |
| CN114157605B (en) | Communication method, system, electronic equipment and computer readable storage medium | |
| CN105376252A (en) | Distributed architecture data communication device, distributed architecture data communication device authentication method and service board | |
| US8370897B1 (en) | Configurable redundant security device failover | |
| CN106878117B (en) | Data processing method and device | |
| CN116743836A (en) | Long connection communication link establishment method and device, electronic equipment and storage medium | |
| US20090182881A1 (en) | Network communication device and internet protocol session distributing method | |
| EP2680539B1 (en) | Hierarchical publish/subscribe system | |
| CN108363551A (en) | A kind of storage system copy link flow control realizing method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20080220 Termination date: 20190303 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |