CN101360093A - Load control method and system thereof - Google Patents
Load control method and system thereof Download PDFInfo
- Publication number
- CN101360093A CN101360093A CNA2007101415577A CN200710141557A CN101360093A CN 101360093 A CN101360093 A CN 101360093A CN A2007101415577 A CNA2007101415577 A CN A2007101415577A CN 200710141557 A CN200710141557 A CN 200710141557A CN 101360093 A CN101360093 A CN 101360093A
- Authority
- CN
- China
- Prior art keywords
- load
- service
- server
- type
- downstream server
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 65
- 238000011144 upstream manufacturing Methods 0.000 claims abstract description 75
- 238000012545 processing Methods 0.000 claims abstract description 10
- 238000012544 monitoring process Methods 0.000 claims description 32
- 238000011217 control strategy Methods 0.000 claims description 27
- 230000004044 response Effects 0.000 description 12
- 238000004891 communication Methods 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 2
- 239000000654 additive Substances 0.000 description 1
- 230000000996 additive effect Effects 0.000 description 1
- 238000000205 computational method Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 238000004321 preservation Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Landscapes
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention provides a load control method and a system. The load control method comprises: generating load information corresponding to service types according to the current load condition of a downstream server; feeding back the load information corresponding to the service types to an upstream server; and implementing the load control to the downstream server by the upstream server according to the load information. The embodiments of the invention provide the technical proposal to realize the load control based on service types and ensure the priority processing of key services when resources are limited.
Description
Technical field
The present invention relates to communication technical field, particularly a kind of load control method and system thereof.
Background technology
In communication system, for any network element, when session initiation protocol (SIP, Session InitiationProtocol) server received that the quantity of message surpasses the message number that it can handle, sip server just may transship.
The method of a kind of load control that prior art provides, receiving entity passes through monitoring module, monitor the current resource situation of receiving entity in real time, when monitoring receiving entity generation overload, current resource situation to sending entity feedback receiving entity is overload, by the resource situation of sending entity, the service request amount that is forwarded to receiving entity is adjusted according to receiving entity.
For example, a SIP request is handled by a plurality of sip servers usually, between on the SIP request path each is to adjacent sip server, when the monitoring module of downstream server monitors downstream server generation overload, provide load information to upstream server, described then upstream server is forwarded to the size of message of described downstream server according to the load information adjustment that receives.
Therefore, in carrying out the invention process, the inventor finds that there are the following problems at least in the prior art: in the load control method that prior art provides, in the described load information that feeds back to upstream server, destination address, the term of validity, load and threshold information have only been comprised, these information have only reflected the disposal ability of downstream server to service request generally, and upstream server can not be carried out corresponding load according to the difference of type of service and be handled.For example: can not be by type of service distribution server resource, certain service request emerge in multitude appears and when having taken server resource, other service request will can not get handling, and might cause the service request that some should priority treatment to be dropped like this.
Summary of the invention
In view of this, the embodiment of the invention provides a kind of load control method and system thereof, can carry out load control based on the difference of type of service.
The embodiment of the invention provides a kind of load control method, comprising:
According to present load situation in the downstream server, generate the load information corresponding with type of service;
Feed back described load information and give upstream server;
Described upstream server is carried out load control according to described load information to described downstream server.
The embodiment of the invention also provides a kind of load control system, comprises upstream server and downstream server, and described downstream server comprises:
The load monitoring unit is used for monitoring the situation of all types of business at the downstream server resource occupation, reports the load information generation unit;
The load information generation unit is used for all types of service request that report according to the described load monitoring unit situation at the downstream server resource occupation, generates the load information corresponding with type of service, reports transmitting element;
Transmitting element is used for the described load information that described load information generation unit generates is fed back to upstream server;
Described upstream server comprises:
Receiving element is used to receive described corresponding with the type of service load information and the service request to downstream server to be sent of described downstream server feedback, and sends to load control unit;
Load control unit is used for the load information according to described receiving element reception, at the service request to downstream server to be sent described downstream server is carried out load control.
The embodiment of the invention also provides a kind of upstream server, comprising:
Receiving element is used to receive the load information corresponding with type of service and the service request to downstream server to be sent of downstream server feedback, and sends to load control unit;
Load control unit is used for the load information according to described receiving element reception, at the service request to downstream server to be sent described downstream server is carried out load control.
The embodiment of the invention also provides a kind of downstream server, comprising:
The load monitoring unit is used for monitoring the situation of all types of business at the downstream server resource occupation, reports the load information generation unit;
The load information generation unit is used for all types of business that report according to the described load monitoring unit monitors situation at the downstream server resource occupation, generates the load information corresponding with type of service, reports transmitting element;
Transmitting element is used for the described load information that described load information generation unit generates is fed back to upstream server.
The load control method and the system thereof that provide by the invention described above embodiment, upstream server can be according to the situation of service request resource occupation in downstream server of current each type of service, generate the load information corresponding with type of service, and according to the load information corresponding with type of service, treat the request that is sent to downstream server, carry out load control by type of service, therefore can realize load control based on type of service.
Description of drawings
Fig. 1 is the process chart of load control method first embodiment in the embodiment of the invention;
Fig. 2 is the process chart of load control method second embodiment in the embodiment of the invention;
Fig. 3 is the structural representation of load control system in the embodiment of the invention.
Embodiment
For making technical scheme of the present invention clearer, below with reference to accompanying drawing and enumerate embodiment, the present invention is described in more detail.
Please refer to Fig. 1, be the process chart of first embodiment of load control method in the embodiment of the invention.
Described load control method specifically comprises:
Step 101:, generate the load information corresponding with type of service according to present load situation in the downstream server;
Step 102: feed back described load information and give upstream server;
Step 103: described upstream server is carried out load control according to described load information to described downstream server.
Please refer to Fig. 2, be the process chart of second embodiment of load control method in the embodiment of the invention.In the present embodiment, upstream server is carried out load control to downstream server, and described load control method specifically comprises:
Step 201: downstream server receives service request;
The service request that downstream server received can be the request message that the response message that sends over from other servers or upstream server send over;
In the present embodiment, the described service request that receives is response message 200OK, and concrete form is as follows:
SIP/2.0?200?OK
Via:SIP/2.0/UDP?a.network.com；branch＝z9hG4bK4b43c2ff8.1
Via:SIP/2.0/UDP?b.network.com；branch＝z9hG4bK77ef4c2312983.1
Via:SIP/2.0/UDP?c.network.com；branch＝z9hG4bKnashds8
Via:SIP/2.0/UDP?d.network.com；branch＝z9hG4bK4e3c2fd8
To:Bob<sip:[email protected]>；tag＝a6c85cf
From:Alice<sip:[email protected]>；tag＝1928301774
Call-ID:a84b4c76e66710
CSeq:314159?INVITE
Contact:<sip:[email protected]>
Content-Length:0
Wherein, the content of Via indicates the address that receives described response message and send the host-host protocol of described response message to next jump set, and the branch parameter that is wherein comprised is used for these affairs of only sign; The destination address of the described response message of content representation of To; The source address of the described response message of content representation of From; The source address of the described response message of content representation of Contact, the recipient can directly send message to transmit leg with this address.
Step 202:, generate the load information corresponding with type of service according to present load situation in the downstream server;
The described load information corresponding with type of service comprises traffic type information, the corresponding corresponding load-threshold value of current load value, type of service of type of service.The load-threshold value of described type of service correspondence is used to represent that described downstream server can handle the ability of load.For example, when the load-threshold value of certain type service is 30, represent that the type business to described downstream server to be sent has 30% will be rejected and be forwarded to downstream server.
The detailed process of the load information that described generation is corresponding with type of service comprises:
According to each professional type of service parameter in the downstream server, generate traffic type information;
According to the situation of all types of business resource occupation in downstream server, generate the current load value corresponding with type of service;
In described downstream server, be provided with the load control strategy, described load control strategy comprises the ratio that take resource corresponding with type of service, according to current load value corresponding and the described ratio that take resource corresponding, generate the load-threshold value corresponding with type of service with type of service with type of service.
Generate with the corresponding concrete mode of threshold value of type of service and be according to the ratio that allows to take resource that is provided with in current load value corresponding and the downstream server:, generate the load-threshold value corresponding with type of service according to taking the ratio of resource with all types of business of the corresponding current load value of type of service and permission with in the corresponding load control strategy of type of service with type of service.
For example, when certain type service current load value is 20, the ratio that allows to take resource is 60, the load value that shows the type business that described downstream server can also receive so is 40, therefore the load-threshold value of the type business is 100-40=60, and the business of the type to described downstream server promptly to be sent has 60% will be rejected and issue.
Described type of service can using method, message header and parameter value come together to represent type of service, enumerates the expression mode that the XML form describes type of service below:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<load-settings?xmlns＝″urn:ietf:params:xml:ns:load-settings″>
<servicetype?id＝″g.oma.poc″>
<Method>INVITE</Method>
<SIPHeader>
<Header>Contact</Header>
<Content>+g.poc.talkburst</Content>
</SIPHeader>
<threshold>50％</threshold>
<upperthreshold>60％</upperthreshold>
<lowerthreshold>20％</lowerthreshold>
</servicetype>
<servicetype?id＝″g.oma.sip-im″>
<Method>SUBSCRIBE</Method>
<SIPHeader>
<Header>Event</Header>
<Content>conference</Content>
</SIPHeader>
<threshold>20％</threshold>
<upperthreshold>30％</upperthreshold>
<lowerthreshold>10％</lowerthreshold>
</servicetype>
<servicetype?id＝″other?service″>
<threshold>10％</threshold>
<upperthreshold>10％</upperthreshold>
<lowerthreshold>5％</lowerthreshold>
</servicetype>
</load-settings>
Using method＜method in the above-mentioned example 〉, message header＜header and parameter value＜content three types of coming together to describe the g.oma.poc business.
Described type of service except can by in the message＜method,＜header and＜content represent, can also represent by additive method.For example for subscribing to class message, traffic type information can obtain from the Event head of subscribe message, and the form of subscribe message is as follows:
SUBSCRIBE?sips:[email protected]?SIP/2.0
Via:SIP/2.0/TLS?client.atlanta.example.com:5061；branch＝z9hG4bK74b8G
Max-Forwards:70
From:Alice<sips:[email protected]>；tag＝837348234
To:Bob<sips:[email protected]>
Call-ID:[email protected]
CSeq:1?SUBSCRIBE
Contact:[email protected]
Event:presence
Accept:application/pidf+xml
Content-Length:0
Is this type of service expressed as SUBSCRIBE? Event%3Dpresence, here＜method 〉,＜header〉and＜content〉be respectively SUBSCRIBE method, Event head and presence incident.
Described type of service can also be by expanding the SIP head in the sip message head, the content behind the use SIP head is represented type of service.For example expand the Service-ID head and represent different types of service, and represent type of service with professional and parameter information:
Service-ID:+g.poc.talkburst；session＝adhoc
Adhoc type of service in the PoC service is represented in above-mentioned expansion, and described type of service is exactly directly to use the content of Service-ID back to represent.
Described load control strategy further comprises the ratio that take resource corresponding with the type of service scope that fluctuates.When the ratio that takies resource when the business of certain type meets or exceeds described load-threshold value, judge whether the downstream server resource has the free time, if have, then adjust the ratio that described type service takies server resource with reference to the described scope of fluctuating that takies the ratio of resource.For example, describe in the expression mode of type of service at aforementioned list XML form,＜threshold〉expression allows this type of service to take the ratio of resource,＜upperthreshold〉and＜lowerthreshold〉be illustrated respectively in higher limit and lower limit unsteady under the resource permission situation.When certain type service current load value reaches the ratio＜threshold that allows this type of service to take resource〉time, if the current load value of other types business does not reach when allowing to occupy the ratio of resource, then the explanation resource of distributing to the other types business also has idlely, and then the resource that takies of the type business just can dynamic change between higher limit and lower limit.
The described load information corresponding with type of service can further include the term of validity of load information, the time that receives load information and destination address etc.
Step 203: described downstream server feeds back described load information and gives described upstream server;
The described load information corresponding with type of service further comprises the total load value in the downstream server, and the aggregate resource that is used to explain described downstream server takies situation, and described load control strategy can also comprise that load information reports threshold value.
Feeding back described load information may further include for described upstream server before:
Judge whether total load value in the described downstream server meets or exceeds load information and report threshold value, if then feed back described load information and give described upstream server; If not, then do not feed back described load information and give upstream server.
Feeding back described load information is for the concrete mode of upstream server: will the described load information corresponding be inserted in the message between downstream server and the upstream server with type of service, by described information reporting to upstream server.The message of carrying described load information can be any response message between downstream server and the upstream server.
For example, load information is added in the 200OK response message that downstream server returns to upstream server, by the 200OK response message load information is reported upstream server, its message format is as follows:
SIP/2.0?200?OK
Via:SIP/2.0/UDP?b.network.com；branch＝z9hG4bK77ef4c2312983.1
Via:SIP/2.0/UDP?c.network.com；branch＝z9hG4bKnashds8
Via:SIP/2.0/UDP?d.network.com；branch＝z9hG4bK4e3c2fd8
To:Bob<sip:[email protected]>；tag＝a6c85cf
From:Alice<sip:[email protected]>；tag＝1928301774
Call-ID:a84b4c76e66710
CSeq:314159?INVITE
LoadInfo:80；throttle＝60；validity＝500；target＝b.network.com；servicetype＝INVITE？Contact％3D+g.poc.talkburst
LoadInfo:80；throttle＝20；validity＝500；target＝b.network.com；servicetype＝INVITE？Contact％3D+g.oma.sip-im
Contact:<sip:[email protected]>
Content-Length:0
Wherein, the LoadInfo head is expressed as load information; First parametric representation load value; Throttle parametric representation threshold value; The term of validity of validity parametric representation load information; The target content of parameter represents to handle the downstream server address of this load information; Servicetype represents load information corresponding service type, comprises method, information header and content information.Information described in the above-mentioned message is: load value was 80 (through normalized); Threshold value is 60; The term of validity is 500ms, and the downstream server address of handling this load information is b.network.com; Is type of service INVITE? Contact%3D+g.oma.sip-im.
The described load information corresponding with type of service also comprises the quantity with the request of request source corresponding service, described load control strategy further comprises the threshold value corresponding with request source, when all types of service request quantity from same request source surpasses the threshold value corresponding with request source, feed back described load information and carry out load control for the described upstream server corresponding with the request source address.
When certain type the service request number that derives from same address surpasses threshold value corresponding with request source in the described load control strategy, destination address in the load information directly is designated the address (a nethermost address in the message header Via head) in described request source, and then described load information directly feeds back to the upstream server of described request source address correspondence.
Suppose from the Service type information of d.network.com address the threshold value corresponding in the described load control strategy that surpassed with request source for the message request of+g.oma.sip-im, then Service type information will directly feed back to the d.network.com address for the load information of+g.oma.sip-im, and the message XML form that feeds back to the d.network.com address is as follows:
SIP/2.0?200?OK
Via:SIP/2.0/UDP?b.network.com；branch＝z9hG4bK77ef4c2312983.1
Via:SIP/2.0/UDP?c.network.com；branch＝z9hG4bKnashds8
Via:SIP/2.0/UDP?d.network.com；branch＝z9hG4bK4e3c2fd8
To:Bob<sip:[email protected]>；tag＝a6c85cf
From:Alice<sip:[email protected]>；tag＝1928301774
Call-ID:a84b4c76e66710
CSeq:314159?INVITE
LoadInfo:80；throttle＝60；validity＝500；target＝b.network.com；servicetype＝INVITE？Contact％3D+g.poc.talkburst
LoadInfo:80；throttle＝20；validity＝500；target＝b.network.com；servicetype＝INVITE？Contact％3D+g.oma.sip-im
LoadInfo:30；throttle＝60；validity＝500；target＝d.network.com；servicetype＝INVITE？Contact％3D+g.oma.sip-im；source＝a.network.com
Contact:<sip:[email protected]>
Content-Length:0
The content of LoadInfo also can be used for representing cancelling the load control by type of service, represents to cancel to the load control of type of service for+g.oma.sip-im business as available validity=0, and form is as follows:
LoadInfo:0；throttle＝0；validity＝0；target＝b.network.com；servicetype＝INVITE？Contact％3D+g.oma.sip-im
Step 204: after described upstream server is received the message that carries the load information corresponding with type of service, described message is resolved, obtain the described load information corresponding with type of service;
Step 205: upstream server judges whether the destination address in the described load information corresponding with type of service is the address of upstream server, if, then carry out step 207, if not, then carry out step 206;
Step 206: transmit all message that carry the load information corresponding and give another server with type of service;
Step 207: upstream server is stored corresponding load information and the service request to downstream server to be sent of described and type of service that described downstream server reports, and can store described load information with the form of load control table;
If do not preserve the load information of the type service that described downstream server reports in the described upstream server, then storage if preservation is arranged, is then upgraded the load information of preserving.
According to the described load information corresponding with type of service, storage or the concrete mode of upgrading in the upstream server of load control table are:
For already present continuous item in the load control table, then the load information according to described feedback directly upgrades corresponding item; For original non-existent item in the load control table, then in the load control table, insert the load information of this correspondence.
If it is invalid that load information is represented the load control of type of service, then no longer downstream server is carried out load control at the type business, upstream server is deleted the corresponding record of downstream server according to type of server in the load information of described feedback and server address from the load control table.
For example, the address of upstream server is b.network.com, the downstream server address that produces load information is a.network.com, originally not having two servicetype load informations shown in the table 1 in the load control table is example, in the load control table, increased this two information newly, as shown in table 1:
Table 1 load control table
| ServiceType (type of service) | ServerAddress (server address) | Load (load) | Throttle (threshold value) | Validity (term of validity) | ReceiveTime (time of reception) |
| INVITE？Contact％ 3D+g.poc.talkburst | a.network.com | 80 | 60 | 500 | 789985256 |
| ?INVITE？Contact％ ?3D+g.oma.sip-im | a.network.com | 80 | 20 | 500 | 789985256 |
| ?… | … | … | … | … | … |
Every value of described load control table and load information are corresponding one by one, ServiceType is a load information corresponding service type, ServerAddress is the address of the downstream server of generation load information, these can obtain from the parameter of load information, Load is the downstream server current load value, Throttle is the load-threshold value of downstream server, and Validity is the term of validity of load information, and ReceiveTime is the time that receives load information.
After the load control table was upgraded and finished, upstream server was with the load information deletion of carrying in the described message, and for example, message after treatment is as follows:
SIP/2.0?200?OK
Via:SIP/2.0/UDP?c.network.com；branch＝z9hG4bKnashds8
Via:SIP/2.0/UDP?d.network.com；branch＝z9hG4bK4e3c2fd8
To:Bob<sip:[email protected]>；tag＝a6c85cf
From:Alice<sip:[email protected]>；tag＝1928301774
Call-ID:a84b4c76e66710
CSeq:314159?INVITE
Contact:<sip:[email protected]>
Content-Length:0
Step 208: upstream server receives the service request to downstream server to be sent, judges whether described service request is urgency traffic, if, then carry out step 209, if not, then carry out step 212;
Can judge whether to be urgency traffic according to whether comprising urn:service.sos information in the To head in the service request,, represent that then described business to downstream server to be sent is a urgency traffic if comprise; Not comprising urn:service.sos information for To head in service request, then is described professional non-emergent business to downstream server to be sent.
Step 209: judge whether downstream server transships, if then execution in step 210, if not, then execution in step 211;
Step 210: if there is not other server can handle described service request, then return errored response,, then handle with going to other servers before the described service request if also have other server can handle described business.
For example, the errored response form is as follows:
SIP/2.0?503?Service?Unavailable
Via:SIP/2.0/UDP?a.network.com；branch＝z9hG4bKnashds8
To:urn:service.sos；tag＝465568
From:Alice<sip:[email protected]>；tag＝1928301774
Call-ID:a84b4c76e66710
CSeq:314159?INVITE
Contact:<sip:[email protected]>
Max-Forwards:70
Content-Type:application/lost+xml
Content-Length:..
Step 211: transmit the server of described emergent operation request to other.
Step 212: the load information that obtains described downstream server feedback from the load control table;
Determine the type of described business to downstream server to be sent according to the traffic type information in the described load information,, in the load control table, obtain the load information corresponding with type of service according to the address of traffic type information and downstream server;
For example, the record that inquires from the load control table is as shown in table 2, please refer to table 2:
The relevant information records table of table 2 inquiry
| ServiceType | ServerAddress | Load | Throttle | Validity | ReceiveTime |
| INVITE？Contact％3D+g. oma.sip-im | c.network.com | 40 | 30 | 500 | 789985256 |
When the continuous item in above-mentioned load control table 1, searched less than ServiceType and ServerAddress correspondence, then represent not overload of the indicated downstream server of the professional corresponding ServerAddress of the type.
Step 213: according to described load-threshold value, the business to downstream server to be sent of transmitting or refuse to send out described;
Described load control strategy comprises further and type of service corresponding strategy value that the size of described strategy value generates at random according to the ratio that takies resource corresponding with type of service.
According to described load-threshold value, professional concrete mode to downstream server to be sent is to transmit or refuse to send out described:
Described strategy value is carried out normalized, judge whether described strategy value through normalized is less than or equal to load-threshold value, if, the business to downstream server to be sent of then refusing to send out described; If not, then transmit described business to downstream server to be sent.
For example, upstream server is according to certain professional type, obtaining the ratio that takies resource corresponding with type of service in the load control strategy is 50, in 0 to 50 scope, generate the size 40 of described strategy value at random, through normalized, this strategy value is 40 * 100/50=80, is 30 and inquire this type of service according to table 2 to deserved load-threshold value, strategy value 80 load-threshold value 30 corresponding with this type of service after normalization compared, because 80 greater than 30, therefore transmit this business to downstream server.
In addition, can also determine whether to transmit service request by the integrality of considering session, for there being session (session) message, this class message can preferentially be forwarded processing; For the message of first request, to compare with the message that has session, the priority of processing is lower, and the possibility that promptly is dropped is bigger.In the acting server of preserving session state, can determine by whether tag sign is arranged in the To head, for the request that comprises the tag sign in the To head, represent that this request set up a request of session, will obtain priority treatment.
Except the method for the integrality of above-mentioned consideration session, also can reduce the priority of the subscription class message of in the business request information body, carrying a large amount of contents and handle, this class is increased by the possibility that the sip message body carries the request refusal of mass data, as message such as SUBSCRIBE, PUBLISH.
The load information that upstream server is also corresponding with type of service according to acquisition judges whether this load information is invalid.It is multiple to judge that method that load information lost efficacy has, and the simplest method can judge according to the size that the current time deducts the time of reception and the term of validity, i.e. (current time-time of reception)-term of validity＞=0 o'clock, and the expression load information lost efficacy; (current time-time of reception)-term of validity＜0 o'clock, the expression load information is effective.
Enumerate below and a kind ofly conclude whether effectively determination methods of load information in conjunction with Load value and throttle value, its basic thought is, suppose that Load value and throttle value are respectively 100 situation, in N the term of validity, could eliminate loading condition fully, be each cycle to reduce 100/N, computational methods are as follows:
result＝value-[(cur_t-rec_t)DIV?validity]×(100/N)
Wherein, value represents actual parameter value, can be Load value in the load control table or Throttle value; Cur_t represents the current time of server; Rec_t represents to receive the time of load information, the ReceiveTime item in the corresponding load control table; Validity represents the term of validity, the Validity item in the corresponding load control table; DIV represents to divide exactly algorithm; N represents that number effective period that experiences, 100/N represent the amount that reduces in each cycle.
Judge that the load information detailed process that whether lost efficacy is: Load value and Throttle value respectively among the substitution following formula value, when two end values all satisfied result＜=0, load information lost efficacy, and upstream server is deleted this load information from the load control table; Otherwise load information is effective.Wherein, the threshold value that downstream server reports also can be the value of a dynamic change, and the cycle times along with process gradually reduces in threshold value.The data instance of above table 2 supposes that server recovers disposal ability in 10 effective periods, then passes through after first cycle, and the threshold value that reports just is 30-30 * 1/10=27.
One of ordinary skill in the art will appreciate that all or part of step that realizes the described method of the foregoing description is to instruct relevant hardware to finish by program, described program can be stored in the computer read/write memory medium, this program is when carrying out, can comprise the steps: situation, generate the load information corresponding with type of service according to all types of business resource occupation in downstream server; Feed back the described load information corresponding and give upstream server with type of service; Upstream server is carried out load control according to the described load information corresponding with type of service to described downstream server.Storage medium described here, as: ROM/RAM, magnetic disc, CD etc.
The processing procedure that above-mentioned steps 201 generates load information and reports for downstream server to step 203, the load information that step 204 reports according to downstream server for upstream server to step 213, the processing procedure of downstream server being carried out load control.This two parts processing procedure also can be carried out simultaneously.
Upstream server in the present embodiment and downstream server can be session initiation protocol acting server (SIP Proxy), also can be other network elements in the communication network.
Fig. 3 is for realizing the load control system structural representation of the inventive method embodiment.Please refer to Fig. 3, described load control system comprises downstream server 30 and upstream server 40.
Described downstream server 30 comprises load monitoring unit 31, load information generation unit 32 and transmitting element 33.
Described load monitoring unit 31 is used for monitoring the situation of all types of business at the downstream server resource occupation, reports load information generation unit 32.
Described load monitoring unit 31 comprise total load monitoring unit, the present load monitoring unit corresponding with type of service, with request source corresponding service monitoring unit.Described total load monitoring unit is used for monitoring the total load of downstream server; The described present load monitoring unit corresponding with type of service is used for monitoring the present load of all types of business of downstream server; Described and request source corresponding service monitoring unit are used for monitoring the quantity of downstream server and the request of request source corresponding service.
Described load information generation unit 32 is used for generating the load information corresponding with type of service according to all types of business of the described load monitoring unit monitors situation at the downstream server resource occupation, reports transmitting element 33.
Described load information comprises traffic type information, the current load value corresponding with type of service, with the corresponding load-threshold value of type of service, total load value, with the quantity of request source corresponding service request etc.
Described transmitting element 33 is used for the load information that load information generation unit 32 generates is fed back to described upstream server, can carry the corresponding load information of described and type of service by downstream server 30 and the message between the upstream server 40 and send to upstream server.
Described downstream server 30 may further include load control strategy memory cell 34, is used for the memory load control strategy, and offers load information generation unit 32.The generative process of described load information is: described load information generation unit 32 is according to the situation of all types of service request resource occupation in described downstream server 30 of described load monitoring unit 31 monitoring, and in conjunction with the load control strategy of storing in the load control strategy memory cell 34, generate the load information corresponding, send to described upstream server 40 by transmitting element 33 with type of service.
Described load control strategy comprise the ratio that take resource, the load information corresponding with type of service report threshold value, with corresponding threshold value of request source etc.
Described upstream server 40 comprises receiving element 41 and load control unit 43.
Described receiving element 41 is used to receive described corresponding with the type of service load information of described downstream server 30 feedbacks and the service request of handling for described downstream server 30 to be sent that other servers send over, and sends to load control unit 43.
Described load control unit 43 receives load information corresponding with type of service and the service request of handling to described downstream server 30 to be sent that transmitting element 41 sends, according to load information, described downstream server 30 is carried out load control at the service request to described downstream server to be sent.
Described upstream server 40 may further include Service Processing Unit 44, described Service Processing Unit 44 is used to judge whether the service request to described downstream server to be sent that described receiving element receives is emergent operation request, if, then transmit described emergent operation request and give described downstream server 30, if not, then transmit described emergent operation request and give described load control unit 43, carry out load control by 43 pairs of described downstream servers of described load control unit.
Described load control unit 43 may further include load information acquiring unit 431 and load drive unit 432.
Described load information acquiring unit 431, be used for service request and described load information to downstream server to be sent according to described receiving element reception, obtain the load information corresponding, and load information and described service request to described downstream server 30 to be sent are sent to load drive unit 432 with type of service.Described load drive unit 432, according to the load-threshold value in load information acquiring unit 431 load information corresponding that send over type of service, the service request to described downstream server 30 to be sent of transmitting or refuse to send out described.
Described load control strategy comprises further and type of service corresponding strategy value that the size of described strategy value generates at random according to the ratio that takies resource corresponding with type of service.
According to the load-threshold value in load information acquiring unit 431 load information corresponding with type of service that send over, service request to downstream server to be sent is specially to transmit or refuse to send out described:
Described strategy value is carried out normalized, judge whether described strategy value through normalized is less than or equal to load-threshold value, if, the service request to downstream server to be sent of then refusing to send out described; If not, then transmit described service request to downstream server to be sent.
Described upstream server 40 may further include memory cell 42, be used to store the load information corresponding of described receiving element 41 receptions and the service request of handling to described downstream server 30 to be sent that other servers send over, and report load information acquiring unit 431 with type of service.Described memory cell 42 memory load information and the described extremely form of the service request of described downstream server 30 to be sent, described load information can take the form of load control table to store.
The load control method and the system thereof that provide by the invention described above embodiment, described downstream server can take the situation of resource according to current each type of service in downstream server, generate the load information corresponding with type of service, report upstream server, described upstream server is according to the described load information corresponding with type of service, treat the service request that is sent to described downstream server, carry out load control, therefore can realize load control based on type of service by type of service; Further, when the service request to downstream server to be sent is emergent operation request, can directly be transmitted to described downstream server and carries out priority treatment, therefore can ensure that when resource-constrained important service obtains priority treatment.
More than a kind of load control method provided by the present invention and system thereof are described in detail, used specific case herein principle of the present invention and execution mode are set forth, the explanation of above embodiment just is used to help to understand disclosed technical scheme; Simultaneously, for one of ordinary skill in the art, according to thought of the present invention, the part that all can change in specific embodiments and applications, in sum, this description should not be construed as limitation of the present invention.
Claims (21)
1. a load control method is characterized in that, described method comprises:
According to present load situation in the downstream server, generate the load information corresponding with type of service;
Feed back described load information and give upstream server;
Described upstream server is carried out load control according to described load information to described downstream server.
2. load control method according to claim 1 is characterized in that, described load information comprises traffic type information, the current load value corresponding with type of service.
3. load control method according to claim 2 is characterized in that, the detailed process that generates the load information corresponding with type of service comprises:
According to each professional type of service parameter in the downstream server, generate traffic type information;
According to all types of service request occupation condition in downstream server, generate the current load value corresponding with type of service.
4. load control method according to claim 2 is characterized in that described load information further comprises the load-threshold value corresponding with type of service.
5. load control method according to claim 4 is characterized in that, at described downstream server the load control strategy is set, and described load control strategy comprises the ratio that take resource corresponding with type of service;
The described generation load-threshold value corresponding with type of service is: generate described load-threshold value according to corresponding current load value of described and type of service and the corresponding ratio that takies resource of described and type of service.
6. load control method according to claim 5 is characterized in that, described load control strategy further comprises the ratio that take resource corresponding with the type of service scope that fluctuates;
When the ratio that takies resource when the service request of certain type meets or exceeds described load-threshold value, judge whether described downstream server resource has the free time, if have, then adjust the ratio that described type service request takies server resource with reference to the described ratio scope of fluctuating that takies resource.
7. load control method according to claim 5 is characterized in that, the described load information corresponding with type of service further comprises the total load value of described downstream server, and described load control strategy comprises that further load information reports threshold value;
Feeding back described load information further comprises for upstream server before:
Whether the total load value of judging downstream server meets or exceeds described load information reports threshold value, if then feed back described load information and give described upstream server.
8. load control method according to claim 2 is characterized in that, the described load information corresponding with type of service further comprises the quantity with the request of request source corresponding service;
Described load control strategy further comprises the threshold value corresponding with request source;
Feeding back described load information further comprises for upstream server before:
When judgement surpasses the described threshold value corresponding with request source from the service request quantity of all types of business of same request source, feed back described load information and carry out load for the described upstream server corresponding to control with the request source address.
9. load control method according to claim 1 is characterized in that,
Described upstream server carries out comprising before the load control to described downstream server: store corresponding load information and the service request to downstream server to be sent of described and type of service that described downstream server reports.
10. load control method according to claim 9 is characterized in that, described upstream server is carried out load control to described downstream server and specifically comprised according to the described load information corresponding with type of service:
Determine the type of the service request to downstream server to be sent;
Load information according to described downstream server feedback obtains the load-threshold value corresponding with type of service;
According to described load-threshold value, the service request to downstream server to be sent of transmitting or refuse to send out described.
11. load control method according to claim 10 is characterized in that, described load control strategy comprises further and type of service corresponding strategy value that the size of described strategy value generates at random according to the ratio that takies resource corresponding with type of service;
According to described load-threshold value, the concrete mode of service request to downstream server to be sent is to transmit or refuse to send out described:
Described strategy value is carried out normalized, judge whether described strategy value through normalized is less than or equal to load-threshold value, if, the service request to downstream server to be sent of then refusing to send out described; If not, then transmit described service request to downstream server to be sent.
12. load control method according to claim 1 is characterized in that, described upstream server carries out comprising before the load control to described downstream server according to the described load information corresponding with type of service:
Judge whether the service request to downstream server to be sent is emergent operation request, if then transmit described emergent operation request and give described downstream server.
13. a load control system of implementing the described method of claim 1 comprises upstream server and downstream server, it is characterized in that,
Described downstream server comprises:
The load monitoring unit is used for monitoring the situation of all types of business at the downstream server resource occupation, reports the load information generation unit;
The load information generation unit is used for all types of service request that report according to the described load monitoring unit situation at the downstream server resource occupation, generates the load information corresponding with type of service, reports transmitting element;
Transmitting element is used for the described load information that described load information generation unit generates is fed back to upstream server;
Described upstream server comprises:
Receiving element is used to receive described corresponding with the type of service load information and the service request to downstream server to be sent of described downstream server feedback, and sends to load control unit;
Load control unit is used for the load information according to described receiving element reception, at the service request to downstream server to be sent described downstream server is carried out load control.
14. load control system according to claim 13, it is characterized in that, described downstream server further comprises load control strategy memory cell, be used for the memory load control strategy, described load information generation unit is according to the situation of all types of business resource occupation in described downstream server of described load monitoring unit monitors, and, generate the load information corresponding with type of service in conjunction with the load control strategy in the load control strategy memory cell.
15. load control system according to claim 13 is characterized in that, described upstream server further comprises:
Service Processing Unit, be used to judge whether the service request to described downstream server to be sent that described receiving element receives is emergent operation request, if, then transmit described emergent operation request and give described downstream server, if not, then transmit described emergent operation request and give described load control unit, described downstream server is carried out load control by described load control unit.
16. load control system according to claim 13 is characterized in that, described load control unit further comprises:
The load information acquiring unit receives business and described load information to downstream server to be sent that described receiving element receives, and sends to load drive unit;
Load drive unit, according to the load-threshold value in the corresponding load information of the described and type of service of obtaining, the service request to downstream server to be sent of transmitting or refuse to send out described.
17. load control system according to claim 13 is characterized in that, described load control strategy comprises further and type of service corresponding strategy value that the size of described strategy value generates at random according to the ratio that takies resource corresponding with type of service;
According to the load-threshold value in the load information corresponding with type of service that obtains, business to downstream server to be sent is specially to transmit or refuse to send out described:
Described strategy value is carried out normalized, judge whether described strategy value through normalized is less than or equal to load-threshold value, if, the service request to downstream server to be sent of then refusing to send out described; If not, then transmit described service request to downstream server to be sent.
18. a upstream server of implementing the described method of claim 1 is characterized in that, comprising:
Receiving element is used to receive the load information corresponding with type of service and the service request to downstream server to be sent of downstream server feedback, and sends to load control unit;
Load control unit is used for the load information according to described receiving element reception, at the service request to downstream server to be sent described downstream server is carried out load control.
19. upstream server according to claim 18 is characterized in that, described upstream server further comprises:
Service Processing Unit, be used to judge whether the service request to described downstream server to be sent that described receiving element receives is emergent operation request, if, then transmit described emergent operation request and give described downstream server, if not, then transmit described emergent operation request and give described load control unit, to described downstream server, carry out load control by described load control unit.
20. upstream server according to claim 18 is characterized in that, described load control unit comprises:
The load information acquiring unit receives service request and described load information to downstream server to be sent that described receiving element receives, and sends to load drive unit;
Load drive unit, according to the load-threshold value in the corresponding load information of the described and type of service of obtaining, the service request to downstream server to be sent of transmitting or refuse to send out described.
21. a downstream server of implementing the described method of claim 1 is characterized in that, comprising:
The load monitoring unit is used for monitoring the situation of all types of business at the downstream server resource occupation, reports the load information generation unit;
The load information generation unit is used for all types of business that report according to the described load monitoring unit monitors situation at the downstream server resource occupation, generates the load information corresponding with type of service, reports transmitting element;
Transmitting element is used for the described load information that described load information generation unit generates is fed back to upstream server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101415577A CN101360093B (en) | 2007-08-02 | 2007-08-02 | Load control method and system thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101415577A CN101360093B (en) | 2007-08-02 | 2007-08-02 | Load control method and system thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101360093A true CN101360093A (en) | 2009-02-04 |
| CN101360093B CN101360093B (en) | 2012-07-04 |
Family
ID=40332433
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101415577A Expired - Fee Related CN101360093B (en) | 2007-08-02 | 2007-08-02 | Load control method and system thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101360093B (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011054149A1 (en) * | 2009-11-06 | 2011-05-12 | 华为技术有限公司 | Method, device and communication system for load control |
| CN102137091A (en) * | 2010-11-15 | 2011-07-27 | 华为技术有限公司 | Overload control method, device and system as well as client-side |
| CN103139246A (en) * | 2011-11-25 | 2013-06-05 | 百度在线网络技术（北京）有限公司 | Load balancing device and load balancing and defending method |
| CN103765408A (en) * | 2011-08-25 | 2014-04-30 | 英派尔科技开发有限公司 | Quality of service aware captive aggregation with true datacenter testing |
| CN105516276A (en) * | 2015-11-30 | 2016-04-20 | 中电科华云信息技术有限公司 | Message processing method and system based on bionic hierarchical communication |
| CN107580033A (en) * | 2017-08-24 | 2018-01-12 | 阿里巴巴集团控股有限公司 | Load information treating method and apparatus, message treatment method and device, server |
| CN107832140A (en) * | 2017-10-10 | 2018-03-23 | 武汉斗鱼网络科技有限公司 | A kind of method, storage medium, electronic equipment and the system of RPC requests control |
| CN112306797A (en) * | 2020-10-22 | 2021-02-02 | 深圳市欢太科技有限公司 | Embedded point information reporting method and device, storage medium and electronic equipment |
| CN113055427A (en) * | 2019-12-28 | 2021-06-29 | 浙江宇视科技有限公司 | Service-based server cluster access method and device |
| WO2022042505A1 (en) * | 2020-08-31 | 2022-03-03 | 华为技术有限公司 | Methods and devices for forwarding messages and issuing forwarding instruction information and notification messages |
-
2007
- 2007-08-02 CN CN2007101415577A patent/CN101360093B/en not_active Expired - Fee Related
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011054149A1 (en) * | 2009-11-06 | 2011-05-12 | 华为技术有限公司 | Method, device and communication system for load control |
| CN102137091A (en) * | 2010-11-15 | 2011-07-27 | 华为技术有限公司 | Overload control method, device and system as well as client-side |
| CN102137091B (en) * | 2010-11-15 | 2013-11-06 | 华为技术有限公司 | Overload control method, device and system as well as client-side |
| CN103765408A (en) * | 2011-08-25 | 2014-04-30 | 英派尔科技开发有限公司 | Quality of service aware captive aggregation with true datacenter testing |
| CN103765408B (en) * | 2011-08-25 | 2016-05-25 | 英派尔科技开发有限公司 | Utilize the quality of service aware trap-type of True Data center test to assemble |
| CN103139246A (en) * | 2011-11-25 | 2013-06-05 | 百度在线网络技术（北京）有限公司 | Load balancing device and load balancing and defending method |
| CN103139246B (en) * | 2011-11-25 | 2016-06-15 | 百度在线网络技术（北京）有限公司 | Load balancing equipment and load balancing and defence method |
| CN105516276B (en) * | 2015-11-30 | 2020-04-17 | 中电科华云信息技术有限公司 | Message processing method and system based on bionic hierarchical communication |
| CN105516276A (en) * | 2015-11-30 | 2016-04-20 | 中电科华云信息技术有限公司 | Message processing method and system based on bionic hierarchical communication |
| CN107580033A (en) * | 2017-08-24 | 2018-01-12 | 阿里巴巴集团控股有限公司 | Load information treating method and apparatus, message treatment method and device, server |
| CN107580033B (en) * | 2017-08-24 | 2020-12-25 | 创新先进技术有限公司 | Load information processing method and device, message processing method and device, and server |
| CN107832140A (en) * | 2017-10-10 | 2018-03-23 | 武汉斗鱼网络科技有限公司 | A kind of method, storage medium, electronic equipment and the system of RPC requests control |
| CN107832140B (en) * | 2017-10-10 | 2021-01-01 | 武汉斗鱼网络科技有限公司 | RPC request control method, storage medium, electronic device and system |
| CN113055427A (en) * | 2019-12-28 | 2021-06-29 | 浙江宇视科技有限公司 | Service-based server cluster access method and device |
| CN113055427B (en) * | 2019-12-28 | 2022-12-23 | 浙江宇视科技有限公司 | Service-based server cluster access method and device |
| WO2022042505A1 (en) * | 2020-08-31 | 2022-03-03 | 华为技术有限公司 | Methods and devices for forwarding messages and issuing forwarding instruction information and notification messages |
| CN112306797A (en) * | 2020-10-22 | 2021-02-02 | 深圳市欢太科技有限公司 | Embedded point information reporting method and device, storage medium and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101360093B (en) | 2012-07-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101360093B (en) | Load control method and system thereof | |
| JP5536120B2 (en) | Optimize communication using scalable peer groups | |
| US8589547B2 (en) | Side channel for membership management within conference control | |
| US9740697B2 (en) | Subscriber driven media agnostic content delivery across networks | |
| CN101212719B (en) | Method and system for implementing converged message service in radio communication network | |
| US20110282957A1 (en) | Method for processing deferred message | |
| CN101273577B (en) | Method and equipment for group communication in communication system | |
| US20100153505A1 (en) | Method and apparatus for sending instant message disposition notification request and response in a converged-ip messaging service and system thereof | |
| CN101098267A (en) | Method and system for establishing cluster conversation | |
| US20110264777A1 (en) | Communications device and method | |
| CN101087446B (en) | A system and method for cluster session | |
| WO2009138553A1 (en) | Method, user equipment and software product for media stream transfer between devices | |
| KR101199401B1 (en) | METHOD FOR delivering and Storing Message based on CPS service and server thereof | |
| WO2007107064A1 (en) | A method and system for delivering dynamic content | |
| CN101771678B (en) | Method and device for managing or triggering view | |
| KR101504362B1 (en) | Mobile communication system and method for requesting disposition notification of im message for each of group members | |
| US8499035B2 (en) | Methods, systems and computer readable media for providing session initiation protocol (SIP) event watcher entity information in a communications network | |
| US9130873B2 (en) | Real time composition of services | |
| CN101287007A (en) | XML document managing method, system and XML document managing server | |
| WO2009008807A1 (en) | Real time composition of services | |
| CN1878171B (en) | Method for blocking information notice in chat room | |
| Singh et al. | Presence traffic optimization techniques | |
| CN101873542A (en) | Selecting method of URI (Uniform Resource Identifiers) based on conditions, server and communication system | |
| CN102546970A (en) | Method and device for issuing presence information | |
| Cartas et al. | An IMS Based Mobile Podcasting Architecture Supporting Multicast/Broadcast Delivery |
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: 20120704 |