Patent US5898672A successfully refreshed from Google Patents.
US5898672A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Overload prevention in a telecommunication network node
Assignee: Nokia Technologies Oy
•
Filing: 1995-11-10
•
Granted: 1999-04-27
•
Expires: 2015-11-10
Abstract
Abstract A method and an arrangement for preventing an overload in a telecommunications network node where a service node transmits restriction requests to other nodes, so that the nodes will restrict the number of service requests towards the service node, including adding to a restriction request restriction parameters. The other nodes transmit the parameters they use, back to the service node, and the service node compares those parameters with the parameters it has transmitted to decide whether a restriction request is to be transmitted to the node which transmitted the parameters.
Inventors
- 👤 Philip Ginzboorg
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-01 18:27
CPC Classifications
H; H04; H04Q; H04Q3/00; H04Q3/64; H04Q3/66; H04Q3/0016; H04Q3/0062; H04Q3/0091; H04Q2213/00; H04Q2213/13521; H04Q2213/13561; H04Q2213/13563
Claims Analysis
Total Claims: 14
Claim 1
Independent Claim
227 words
A method of preventing an overload in a telecommunications network node of a network having a service node and at least one other node from which the service node receives service requests, comprising the steps of: said service node transmitting restriction requests to another said node connected thereto, so that said other node will restrict the number of service requests said other node transmits towards said service node, each said restriction request comprising a group of parameters indicating how said other node should perform a respective restriction, a said restriction request being transmitted by said service node to said other node at least whenever said group of parameters changes; said service node including in each said restriction request information identifying a respective said group of parameters; said other node in consequence of receiving each said restriction request copying the respective said information into a memory of said other node and transmitting data identifying the groups of parameters said other node uses, back to said service node; and said service node in regard to at least a proportion of said data as received thereby in consequence of receiving said data, comparing said data with the respective said information transmitted to said other node by said service node, and deciding on the basis of results of said comparing whether to transmit a next restriction request to said other node.
Claim 2
Independent Claim
227 words
A method of preventing an overload in a telecommunications network node of a network having a service node and at least one other node from which the service node receives service requests, comprising the steps of: said service node transmitting restriction requests to another said node connected thereto, so that said other node will restrict the number of service requests said other node transmits towards said service node, each said restriction request comprising a group of parameters indicating how said other node should perform a respective restriction, a said restriction request being transmitted by said service node to said other node at least whenever said group of parameters changes; said service node including in each said restriction request information identifying a respective said group of parameters; said other node in consequence of receiving each said restriction request copying the respective said information into a memory of said other node and transmitting data identifying the groups of parameters said other node uses, back to said service node; and said service node in regard to at least a proportion of said data as received thereby in consequence of receiving said data, comparing said data with the respective said information transmitted to said other node by said service node, and deciding on the basis of results of said comparing whether to transmit a next restriction request to said other node.
Claim 3
Dependent Claim
38 words
The method according to claim 1, wherein: said other node when transmitting said data identifying the groups of parameters said other node uses, back to said service node transmits said data together with a respective said service request.
Claim 4
Dependent Claim
24 words
The method according to claim 1, further comprising: said service node maintaining said data identifying group of parameters received thereby, by using a counter.
Claim 5
Dependent Claim
38 words
The method according to claim 3, further comprising: said as a consequence of receiving said data rolling over such that all data identifying the groups of parameters used in said other node are changed in said service node.
Claim 6
Dependent Claim
30 words
The method according to claim 2, wherein: said service node performs said comparing only to a predetermined proportion of a total number of service request received by said service node.
Claim 7
Dependent Claim
41 words
The method according to claim 1, further comprising: said other node restricting the number of said service requests transmitted towards said service node are restricted by restricting the number of said service requests transmitted by said other node per time unit.
Claim 8
Dependent Claim
51 words
The method according to claim 1, further comprising: said other node restricting the number of said service requests transmitted towards said service node by restricting the number of said service requests transmitted by said other node towards said service node to a certain percentage of a total number of service requests.
Claim 9
Dependent Claim
242 words
A network service node in a telecommunications network having at least one said service node and at least one other node from which the said service node, in use, receives service requests, said service node comprising: transmitting means arranged to transmit restriction requests to said other node, so that said other node will restrict the number of service requests said other node transmits towards said service node, each such restriction request including information identifying a respective group of parameters indicating how said other node should perform restriction, said service node being arranged to have said transmitting means transmit a respective restriction request at least whenever said group of parameters changes such that said other node, in consequence of receiving each said restriction request, copies said information into a memory of said other node, and transmits to said service node data identifying the groups of parameters said other node uses to perform restriction; comparing means for comparing data stored in said service node identifying a respective said group of parameters to corresponding data received from said other node for at least a proportion of said data as received by said service node, the comparing means being operationally connected to said transmitting means to control transmission by said transmitting means of restriction requests from said service node to said other node based on results of said comparing, such that deciding whether to send each next said restriction request is based on respective said results.
Claim 10
Dependent Claim
242 words
A network service node in a telecommunications network having at least one said service node and at least one other node from which the said service node, in use, receives service requests, said service node comprising: transmitting means arranged to transmit restriction requests to said other node, so that said other node will restrict the number of service requests said other node transmits towards said service node, each such restriction request including information identifying a respective group of parameters indicating how said other node should perform restriction, said service node being arranged to have said transmitting means transmit a respective restriction request at least whenever said group of parameters changes such that said other node, in consequence of receiving each said restriction request, copies said information into a memory of said other node, and transmits to said service node data identifying the groups of parameters said other node uses to perform restriction; comparing means for comparing data stored in said service node identifying a respective said group of parameters to corresponding data received from said other node for at least a proportion of said data as received by said service node, the comparing means being operationally connected to said transmitting means to control transmission by said transmitting means of restriction requests from said service node to said other node based on results of said comparing, such that deciding whether to send each next said restriction request is based on respective said results.
Claim 11
Dependent Claim
32 words
The method according to claim 1, wherein: each said group of parameters, and therefore each said restriction request is restriction-specific as to each of a plurality of subsystems of said service node.
Claim 12
Independent Claim
202 words
A method for preventing an overload in a service node which receives service requests from at least one other node and which includes a plurality of subsystems which are subject to being overloaded at least partially independently of one another, by restricting service requests from said other nodes to said service node on a subsystem-specific basis, said method comprising the steps of: said service node including in a restriction request which said service node transmits to said other node, information identifying a group of parameters indicating subsystem by subsystem for each of a plurality of subsystems how said other node should restrict service requests to be transmitted by said other node to said service node; said other node copying said information into a memory of said other node, and transmitting information back to said service node as to how said other node will restrict service requests to be transmitted by said other node to said service node; said service node comparing said information as transmitted to said other node, with said information as transmitted by said other node, and, upon finding a difference as a result of said comparing, said service node sending a new subsystem-specific restriction request to said other node.
Claim 13
Independent Claim
202 words
A method for preventing an overload in a service node which receives service requests from at least one other node and which includes a plurality of subsystems which are subject to being overloaded at least partially independently of one another, by restricting service requests from said other nodes to said service node on a subsystem-specific basis, said method comprising the steps of: said service node including in a restriction request which said service node transmits to said other node, information identifying a group of parameters indicating subsystem by subsystem for each of a plurality of subsystems how said other node should restrict service requests to be transmitted by said other node to said service node; said other node copying said information into a memory of said other node, and transmitting information back to said service node as to how said other node will restrict service requests to be transmitted by said other node to said service node; said service node comparing said information as transmitted to said other node, with said information as transmitted by said other node, and, upon finding a difference as a result of said comparing, said service node sending a new subsystem-specific restriction request to said other node.
Claim 14
Dependent Claim
35 words
The network service node of claim 8, wherein: said service node is arranged to provide each restriction request so as to be restriction-specific as to each of at plurality of subsystems of said service node.
References Cited (Backward Citations)
US5060258A
Cited
US5090011A
Cited
EP0425202A2
Cited
US5673252A
Cited
US5309431A
Cited
US5029164A
Cited
US5425086A
Cited
US5450483A
Cited
US5602841A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2002-04-26 | 2002-10-26 | 2003-04-27 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2006-04-26 | 2006-10-26 | 2007-04-27 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2010-04-26 | 2010-10-26 | 2011-04-27 | $7700.00 | Window Closed / Lapsed |