[go: up one dir, main page]

CN101383879B - Method for allocating connection attempt to server - Google Patents

Method for allocating connection attempt to server Download PDF

Info

Publication number
CN101383879B
CN101383879B CN200710145330XA CN200710145330A CN101383879B CN 101383879 B CN101383879 B CN 101383879B CN 200710145330X A CN200710145330X A CN 200710145330XA CN 200710145330 A CN200710145330 A CN 200710145330A CN 101383879 B CN101383879 B CN 101383879B
Authority
CN
China
Prior art keywords
phone
central server
devices
connection
attempting
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
Application number
CN200710145330XA
Other languages
Chinese (zh)
Other versions
CN101383879A (en
Inventor
克里斯托弗·詹姆斯·纳森
罗伯特·斯达尔
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mitel Networks Corp
Original Assignee
Mitel Networks Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mitel Networks Corp filed Critical Mitel Networks Corp
Priority to CN200710145330XA priority Critical patent/CN101383879B/en
Publication of CN101383879A publication Critical patent/CN101383879A/en
Application granted granted Critical
Publication of CN101383879B publication Critical patent/CN101383879B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention discloses a method for allocating attempts to connect a server. A client/server network comprises a plurality of IP devices communicating with a center server and also communicating with each other. Each of the IP devices maintains a count value of the number of the IP devices simultaneously attempting to connect to the center server so as to monitor a load on a center server, wherein each of the IP devices verifies that the count value does not exceed a maximum value before attempting to connect to the center server.

Description

The method that is used for the connection trial of branch pairing server
Technical field
The present invention relates to be used for the method that the connection of branch pairing server is attempted, described connection to server is attempted particularly promptly excitation (stimulus) IP phone the connection of PBX is attempted.
Background technology
In typical client/server voice communication network, a plurality of IP phone are utilized transmission control protocol (TCP) to connect and are communicated by letter with PBX.IP phone utilizes 3 grades of processes to be connected to PBX.This process generally comprises the TCP link (usually needing three-way handshake) that gets access to PBX, the control link (i.e. registration) that carries out safe connection and establishment and PBX.Depend on general needs of IP phone that stimulus messages is transmitted to the lasting TCP control link of their PBX.
For example, during some incident (for example from power failure, recovering), when a large amount of IP phone attempt connecting simultaneously, the PBX excess load that may become.A large amount of SYN groupings in the formation will be waited for for a long time before connecting with PBX with the IP phone that other message cause asking.
Because increase the security protocol such as Secure Sockets Layer(SSL), the PBX connection delay of all IP phone is increased the weight of.Because needed a large amount of calculating when establishment has the key of the desired the highest level of security of IP phone, it is very time-consuming to make that treatment S SL connects.Like this, the general restriction of PBX can be attempted the IP phone number that SSL connects simultaneously, and just refuses further SSL trial in case reach the limit of PBX.Under such situation, IP phone is denied access to usually, is forced to disconnect their TCP connection and attempt three-way handshake on unsafe plaintext port of PBX.
In case IP phone is connected to safe or dangerous port, it just provides its capacity of equipment to the PBX registration and in the registration request.If IP phone is but announced it and supported SSL on unsafe port, then PBX can refuse its registration request and force IP phone to disconnect to connect to connect with retry SSL.If PBX accepts registration, then it will send a large amount of activation commands to IP phone, make it can send and accept call with the configuration of IP phone.The remarkable deterioration that streams may cause the PBX performance is transmitted in a large amount of inside stories that are associated with configuration at a large amount of burst IP phone.
Allowing a large amount of IP phone to be connected to PBX with random fashion is inefficient and tediously long process.A solution is a number of optimizing the TCP SYN grouping that each phone sent.The time quantum that IP phone is attempted being connected to PBX is restricted to and for example made that the SYN transmission packets concentrates on than in short time interval in 10 seconds.If allow phone to attempt connecting with the longer period, then since the delay that random back-off (backoff) scheme that TCP adopted will make the SYN grouping be grown separate very much.
The trend of telecommunication industry provides the client/server network that each PBX can support increasing phone.Like this, connect and constantly increase needed total time of all IP phone.Thereby wish to minimize connect needed time quantum and minimizing total connect hours of each IP phone and PBX.
Summary of the invention
In one aspect of the invention, provide a kind of a plurality of IP devices that are used for communicating by letter to be connected to the method for central server with central server.This method comprises: when the number of the IP device of attempting being connected to central server during less than maximum number, an IP device in a plurality of IP devices attempts being connected to central server, the connection that a described IP device in wherein a plurality of IP devices is Once you begin attempted central server is other device broadcasts first message in a plurality of IP devices just, and when finishing the connection of attempting central server to described other device broadcasts second message.In a single day each IP device in the IP device receives the number that first message just increases progressively IP device, and in case receives just the successively decrease number of IP device of second message.
Description of drawings
With reference to accompanying drawing, will be better understood the present invention, wherein similar label is represented similar parts and wherein:
Fig. 1 is the schematic diagram of prior art IP phone subnet;
Fig. 2 illustrates the schematic diagram that IP phone well known in the prior art gets access to the TCP link of PBX;
Fig. 3 illustrates IP phone well known in the prior art to carry out the schematic diagram that is connected of safety with PBX;
Fig. 4 is the schematic diagram that the control link of IP phone establishment well known in the prior art and PBX is shown;
Fig. 5 is the state diagram that illustrates according to the operation of the IP phone of the embodiment of the invention; And
Fig. 6 illustrates the sequential chart of example that a plurality of IP phone according to the present invention are attempted the connection of PBX.
Embodiment
In an embodiment of the present invention, the subnet 5 of excitation IP phone 1 is communicated by letter so that the client/server network to be provided, as shown in Figure 1 with central server or PBX 3.IP phone also communicates with one another and is connected to the number of the IP phone 1 of PBX 3 with control trial simultaneously.Four IP phone 1 shown in Fig. 1, still, subnet 5 can comprise the IP phone 1 of any number.
IP phone-PBX registration comprises three phases: (i) get access to the TCP link of PBX 3, and generally shown in Figure 2, (ii) carry out safe connection, generally shown in Figure 3, and (iii) create the control link or register to PBX 3, generally shown in Figure 4.Each stage all relates to IP phone and attempts dissimilar being connected with PBX.Carry out the described stage in order, and proceeding to realize successful connection in each stage before the next stage.The IP phone of attempting connecting in each stage of three phases is considered in one of following three groups: the 1st group: TCP connects; The 2nd group: Secure Sockets Layer(SSL) connects; And the 3rd group: the registration request, these three groups provide in Fig. 2, Fig. 3 and Fig. 4 respectively.
After powering up, IP phone 1 receives their configuration information from DHCP (DHCP) manual configuration or from configuration file.According to the present invention, configuration information comprises the maximum phone counting of each group in above-mentioned three groups.More specifically, configuration information comprises the maximum number of the IP phone 1 of attempting being connected to PBX 3, the maximum number of attempting carrying out the phone that SSL connects and the attempts registration maximum number to the phone of PBX.
Configuration parameter also comprise three respectively with the 1st group, the 2nd group and the 3rd group of unique multicast address that is associated.Each IP phone 1 is safeguarded three Counter Values that all IP phone 1 are shared, the number of the IP phone that its trial of following the tracks of each group in three groups connects.For each group, IP phone 1 is responsible for the number of the IP phone 1 of attempting connecting is counted separately, and when IP phone 1 does not reattempt connection, by the suitable countdown value of multicast message.
When IP phone 1 attempted connecting, the multicast address that the IP phone utilization is associated with the group that IP phone is attempting being connected to sent declaration on subnet 5.Other IP phone receive this declaration and correspondingly increase progressively their counters that is associated with this group separately.When IP phone 1 was finished the trial connection, no matter IP phone 1 success or not, IP phone 1 all used identical multicast address to send declaration to represent that connecting trial finishes on subnet 5.Other IP phone 1 their counter that after receiving this declaration, successively decreases then.
Three unique message types are defined as follows.The 1st group of TCP connection message comprises type of message (STARTING or FINISHED), PBX IP address, phone IP address and phone MAC Address.The STARTING type of message will be sent out when IP phone 1 will attempt being connected with the TCP of PBX 3.The FINISHED type of message is sent out when the connection trial and success of the socket processor of IP phone or failure.The 2nd group of SSL connection message comprises type of message (STARTING or FINISHED), PBX IP address, phone IP address and phone MAC Address.The STARTING type of message will be sent out when IP phone 1 will attempt being connected with the SSL of PBX 3.The FINISHED type of message is sent out when the connection trial and success of the SSL of IP phone processor or failure.The 3rd group of registration message comprises type of message (STARTING or FINISHED), PBX IP address, phone IP address and phone MAC Address.The STARTING type of message will be sent out when IP phone 1 will be attempted registration request with PBX 3.The FINISHED type of message is sent out when PBX3 receives the confirmation the final configuration messages of registration of IP phone 1 in IP phone 1.
IP phone 1 utilizes the cipher key shared in advance in the flash memory that is stored in each IP phone 1 that multicast message is decrypted, and upgrades their inside counting in response.If any message parameter mistake, then this message is left in the basket.During fabrication or during disposing, cipher key shared in advance is located in the flash memory of each IP phone, still, those skilled in the art will know that and can use any known method that fail safe is provided as multicast message.
With reference to Fig. 5, all IP phone 1 all start from the 1st group and be random back-off between 1 to 2 second of 10ms with the execution interval.When in random back-off state 12, IP phone 1 is answered the counter that is used for the 1st group, the 2nd group and the 3rd group from all declarations of other IP phone 1 and maintenance.The IP phone 1 of coming out from random back-off state 12 enters the state 14 of the count value of checking current group and checks desirable group counter.If count value equals maximum number (definition during disposing), then IP phone 1 is returned random back-off state 12, to be spaced apart another random back-off of 1 to 2 second of 10ms.But, if count value less than maximum number, then IP phone 1 will be utilized with desirable group of multicast address that is associated and send STARTING declaration on subnet 5.
In case the STARTING declaration is sent out, IP phone 1 just enters the state 16 of waiting for successfully or failing.If to the successful connection of the 1st group or the 2nd group, then IP phone 1 sends the FINISHED declaration and enters random back-off state 12 once more.If to the 3rd group successful connection, then IP phone sends the FINISHED declaration and enters and finishes the state 18 that stimulus messages is downloaded, and in this state, IP phone 1 is exercisable and for example can sends and receipt of call.If to the connection failure of any group in three groups, then IP phone 1 sends the FINISHED declaration and enters random back-off state 12 once more.
Come out from the 1st group in case should be appreciated that IP phone 1, it just no longer answers the 1st group multicast, but continues to answer the multicast message from the 2nd group and the 3rd group.Similarly, in case IP phone 1 is come out from the 2nd group, it just no longer answers the 2nd group multicast, but continues to answer the 3rd group multicast message.
In some cases, the safety connection is not supported by PBX and is unwanted.In these cases, the keeper can set SSL restriction and equals 0.IP phone 1 is restricted to 0 with SSL and is interpreted as representing not have the SSL stage.
If the current count value that detects grouping owing to any reason IP phone in predetermined periods (for example, 40 seconds) all do not have to change, then IP phone 1 sends and makes that all IP phone 1 are removed (flush) their internal counter and the hypothesis count value is zero multicast message.IP phone 1 will be before the state 14 that enters the count value of checking current group once more then, and backoff interval is another random time section (for example, between 1 to 2 second) of 10ms.The IP phone 1 of attempting the TCP connection is preferably overtime after 40 seconds under the unsuccessful situation, and transmission FINISHED declares and enter once more random back-off state 12.The timeout period of why selecting 40 seconds is because SSL stage and registration phase generally just received success or failure reporting less than 40 seconds, still, those skilled in the art will know that and can select another suitable timeout period.
With reference to Fig. 6, will describe now and attempt carrying out the operation that TCP connects, SSL connects or register the IP phone " A " to " I " of request.Fig. 6 is general figure, and therefore is applied to the connection trial of each group in the 1st group, the 2nd group or the 3rd group.In this example, the maximum number of the IP phone 1 of each group is set to 5 during disposing.
As shown in the figure, phone A is first phone that comes out from random back-off state 12.When phone A entered the state 14 of the count value of checking current group, it was found that count value equals zero (this is less than maximum count 5) and therefore sends the STARTING declaration to other phones.The count value of being safeguarded by phone is from zero increase to 1 then.During phone A attempt to connect, phone B, D, C and F determined that also count value is lower than maximum number, sends the STARTING declaration and attempt being connected.
When phone E when random back-off state 12 comes out and enter the state 14 of the count value of checking current group, its find count value equal 5 and therefore phone E must enter random back-off state 12 once more, as shown in the figure.In a single day phone A has finished being connected of they with B, just sends the FINISHED declaration.
Phone H comes out and enter the state 14 of the count value of current group of inspection receives the FINISHED declaration from phone A and B after from random back-off state 12.The count value of being announced equals 3, and this is less than maximum number 5, so phone H sends the STARTING declaration and attempts connection.Therefore as shown in the figure, count value equals 4 now, and when the FINISHED that sends them subsequently as phone D and C declared, count value was reduced to 3 from 4 step by step and is reduced to 2 again.Thereby phone E can send the STARTING declaration now and attempt connecting.
In a single day phone F finishes its connection and attempts just sending the FINISHED declaration, and count value is decremented to 2.Phone G and I come out, send the STARTING declaration and attempt being connected from random back-off state 12 then.Attempt finishing in case connect, phone E, F, G and I just send FINISHED declaration and count value vanishing.
The single random back-off period of phone J is shown as one or two random back-off period greater than other phones.When phone J last for the first time when random back-off state 12 comes out, count value equal zero and therefore phone J can send the STARTING declaration and attempt connecting.Connect trial in case phone J finishes it, count value just is decremented to zero once more.
As shown in Figure 6, phone does not enter random back-off state 12 once more after connecting trial.Like this, in this example that can represent any group in the 1st group, the 2nd group or the 3rd group, it all is successful that all between IP phone and the PBX connect trial.
In another embodiment, IP phone notifies its equity side to carry out specific action.For example, IP phone can make its message transmission be enhanced to comprise that the TCP that attempts particular port connects the specific instruction of how many times, and perhaps IP phone can notify its equity side to attempt being connected to the tcp port of particular range.In addition, if IP phone can not be connected to a PBX in the special time amount, then they can be notified each other to be connected to different PBX.
Those skilled in the art will know that the present invention is not limited to IP phone.Any IP device that is connected to central server be can use, computer or other network equipments for example comprised.
Shown here and described specific embodiments of the invention.But those skilled in the art can make amendment and be out of shape.Think that modification that all are such and distortion are all in the field of the invention and scope.

Claims (12)

1. a plurality of IP devices that are used for communicating by letter with central server are connected to the method for described central server, and described method comprises:
When the number of the described IP device of attempting being connected to described central server during less than maximum number, an IP device in described a plurality of IP devices attempts being connected to described central server;
First message is broadcasted in the connection that a described IP device in described a plurality of IP device is Once you begin attempted described central server just other IP devices in described a plurality of IP devices;
Described IP device other IP devices in described a plurality of IP devices when finishing the connection of attempting described central server in described a plurality of IP device are broadcasted second message;
Wherein, in a single day each IP device in the described IP device receives the number that described first message just increases progressively the IP device that described trial connects, and in case receives just the successively decrease number of the IP device that described trial connects of described second message.
2. the method for claim 1, wherein described a plurality of IP devices are connected to described central server by using three stage enrollment process.
3. method as claimed in claim 2, wherein, each IP device in the described IP device is safeguarded the number that is connected to the described IP device of described central server at the trial in each stage in the three phases of described three stage enrollment process simultaneously.
4. method as claimed in claim 3, wherein, described maximum number is identical for each stage in the described three phases.
5. the method for claim 1, wherein described IP device is an IP phone.
6. method as claimed in claim 4, wherein, described three phases be (i) to the TCP of described central server connect, (ii) to the safety connection of described central server with (iii) register to described central server.
7. the method for claim 1, wherein before attempting being connected to described central server, the described IP device in described a plurality of IP devices is in compensating coefficient.
8. the connection that the described IP device in the method for claim 1, wherein described a plurality of IP devices is Once you begin attempted described central server just enters the state of waiting for successfully or failing.
9. client/server network comprises:
A plurality of IP devices of communicating by letter and communicating with one another with central server, first message is broadcasted in the connection that each IP device in described a plurality of IP device is Once you begin attempted described central server just other IP devices in described a plurality of IP devices, in case when finishing the connection of attempting described central server just described other IP devices in described a plurality of IP devices broadcast second message, and safeguard the count value of the number of the described IP device of attempting being connected to described central server simultaneously;
Wherein, each IP device in described a plurality of IP device verified that before the connection of attempting described central server described count value does not surpass maximum count value.
10. client/server network as claimed in claim 9, wherein, described IP device is an IP phone.
11. client/server network as claimed in claim 9, wherein, each IP device in described a plurality of IP devices all was in compensating coefficient before the connection of attempting described central server.
12. client/server network as claimed in claim 9, wherein, when attempting the connection of described central server, each IP device in described a plurality of IP devices all is in the state of waiting for successfully or failing.
CN200710145330XA 2007-09-07 2007-09-07 Method for allocating connection attempt to server Expired - Fee Related CN101383879B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN200710145330XA CN101383879B (en) 2007-09-07 2007-09-07 Method for allocating connection attempt to server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN200710145330XA CN101383879B (en) 2007-09-07 2007-09-07 Method for allocating connection attempt to server

Publications (2)

Publication Number Publication Date
CN101383879A CN101383879A (en) 2009-03-11
CN101383879B true CN101383879B (en) 2011-05-18

Family

ID=40463492

Family Applications (1)

Application Number Title Priority Date Filing Date
CN200710145330XA Expired - Fee Related CN101383879B (en) 2007-09-07 2007-09-07 Method for allocating connection attempt to server

Country Status (1)

Country Link
CN (1) CN101383879B (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1408089A (en) * 1999-09-24 2003-04-02 阿坎巴公司 System and method for managing connections between client and server

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1408089A (en) * 1999-09-24 2003-04-02 阿坎巴公司 System and method for managing connections between client and server

Also Published As

Publication number Publication date
CN101383879A (en) 2009-03-11

Similar Documents

Publication Publication Date Title
CN106332224A (en) Equipment networking method, equipment networking device and equipment networking system
US8982736B2 (en) Method for implementing radiophone based conference call and dynamic grouping
CN102025616B (en) Method, device and switch for realizing BFD (Bidirectional Forwarding Detection)
US12021950B2 (en) Multi-link communications
EP1921817A1 (en) Methods and a device for associating a first device with a second device
CN101605235A (en) A kind of method and apparatus of video communication
CN101383879B (en) Method for allocating connection attempt to server
CN106060784B (en) Voice calling method, system and device of cluster communication system and gateway equipment
US9906426B2 (en) Method of accelerating control link loss detection
CN106254040A (en) The response process method of order and device
CN101383878B (en) Queuing method for coordinating connection attempt to server
WO1999012314A2 (en) Arrangement for controlling network elements
CA2582003C (en) Queueing method to coordinate connection attempts to a server
US8446898B2 (en) Method for distributing connection attempts to a server
EP1878200B1 (en) Method and apparatus for introducing devices with simple user interfaces into a secure network community
JP2010287960A (en) IP telephone and IP communication command system for receiving simultaneous command broadcast
CN101616012A (en) Fork service processing method and core network element
CN116488961B (en) Public unit gateway, communication method and communication system
WO2018001127A1 (en) Transmission method, device and system, and computer readable storage medium
CN100369431C (en) Networkable appliance
JP3642987B2 (en) Service providing system and service stop control device used in the system
CN119865467A (en) Message correction method and system for preventing session from being blocked by operation and maintenance audit system
CN101369964A (en) Method for accelerating control link loss detection
CN101370057A (en) Method for sharing network resource
JPH104440A (en) Dynamic revision system for communication control procedure and its 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: 20110518

Termination date: 20170907

CF01 Termination of patent right due to non-payment of annual fee