WO2006092645A1 - Ip multiservice network and method for making resource reservations for priority traffic - Google Patents
Ip multiservice network and method for making resource reservations for priority traffic Download PDFInfo
- Publication number
- WO2006092645A1 WO2006092645A1 PCT/IB2005/000547 IB2005000547W WO2006092645A1 WO 2006092645 A1 WO2006092645 A1 WO 2006092645A1 IB 2005000547 W IB2005000547 W IB 2005000547W WO 2006092645 A1 WO2006092645 A1 WO 2006092645A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- traffic flow
- qos
- resources
- priority traffic
- low priority
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2416—Real-time traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/15—Flow control; Congestion control in relation to multipoint traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/245—Traffic characterised by specific attributes, e.g. priority or QoS using preemption
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
- H04L47/724—Admission control; Resource allocation using reservation actions during connection setup at intermediate nodes, e.g. resource reservation protocol [RSVP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/74—Admission control; Resource allocation measures in reaction to resource unavailability
- H04L47/745—Reaction in network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
- H04L47/765—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the end-points
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/80—Actions related to the user profile or the type of traffic
- H04L47/801—Real time traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/82—Miscellaneous aspects
- H04L47/821—Prioritising resource allocation or reservation requests
Definitions
- the present invention relates in general to a multiservice Internet Protocol (IP) network and a method that supports an enhanced QoS message that contains two levels of reservations which makes it possible for IP router(s) to reserve resources for a high priority traffic flow and admit the high priority traffic flow without needing to terminate an existing low priority traffic flow.
- IP Internet Protocol
- RSVP Resource Reservation Protocol
- the QoS has to be ensured for the real-time traffic flows.
- the RSVP signaling protocol requires that RSVP signaling messages be used to reserve resources in each IP router along a data path that is going to be used to deliver the real-time traffic flow. These resources are identified by a flow ID. If the reservation is successful, then the data flow can be entered into the multiservice IP network.
- the RSVP signaling protocol also requires that the per flow reservation states be stored in each IP router along the data path. The reservation states are soft states which means that they need to be refreshed by sending periodic refresh messages.
- a reserved state is not refreshed, then the state and the corresponding resources are removed after a time-out period. Reservations can also be removed by an explicit tear down message.
- the storing and maintaining of per flow reservation states in each IP router can be a problem in large networks, where the number of flows and therefore the number of reservation states is high. The IP routers may not have enough capacity to store and maintain all of these reservation states.
- the IETF specified the RSVP aggregation method which allows IP routers to make reservations for aggregated flows.
- the aggregated reservations are identified by a DiffServ code point (DSCP) and require the storing of one aggregated reservation state which is used for multiple flows in the IP routers.
- the aggregated reservation state does not need to be created, modified or refreshed for each flow request.
- DSCP DiffServ code point
- NSIS Next Steps In Signaling
- WG Next Steps In Signaling
- the NSIS QoS application signaling protocol which is currently under specification, is fundamentally similar to the RSVP signaling protocol.
- the proposed NSIS QoS application signaling protocol supports most of the extensions that have been made for the RSVP signaling protocol including the RSVP aggregation method.
- the multiservice IP network also needs to provide emergency priority services not only for traditional telephony calls but also for other real-time applications like video streams and audio-video conference calls. Even though emergency traffic is high priority traffic, it also needs to have resource reservations made within the IP routers that are on the data path to protect it from background traffic. If there are not enough resources to make the reservation for the high priority traffic, then one or more lower priority reservations have to be pre-empted so that the higher priority reservation can be accepted. This pre-emption policy is described in detail within the following document:
- the adaptive resource broker requires information about the whole network, like network topology, traffic matrix etc., which in turn requires additional signaling, or configuration. And, all of this required information is less likely to be available in a multi-domain network.
- the adaptive resource broker may require that an additional node or intelligence be added to the network.
- the adaptive resource broker is a centralized solution because decisions are made based on more than local information. As a result, the security requirements are demanding and the redundancy of the node has to be solved. In another attempt, a method has been used to reserve in advance the resources needed for priority traffic.
- the present invention includes a multiservice IP network and a method that support an enhanced QOS message which makes it possible for an IP router to reserve resources for and admit a high priority traffic flow without needing to terminate an existing low priority traffic flow.
- the IP router reduces the reservation of one or more low priority traffic flows to a reduced level.
- the IP router also sends a notification message to the sender indicating that the reservations have been reduced. Thereafter, the high priority traffic flow can be admitted.
- the low priority calls need not be terminated instead only the resources are reduced to a lower but still acceptable QoS level. And, when traffic conditions improve then the reduced reservations can be increased back to the original level.
- FIGURE 1 is a flowchart that illustrates the steps of a preferred method for using an enhanced QoS message which makes it possible for a multiservice IP network and in particular IP router(s) to reserve resources for an emergency traffic flow and then admit the emergency traffic flow without needing to terminate an existing low priority traffic flow in accordance with the present invention
- FIGURE 2 is a block diagram that illustrates an exemplary multiservice IP network and a signal flow chart which are used to help describe the steps of the preferred method shown in FIGURE 1;
- FIGURE 3 is a signal flow diagram that illustrates one scenario as to how the exemplary multiservice IP network shown in FIGURE 2 can use the enhanced QoS message to admit an emergency traffic flow without needing to terminate an existing low priority traffic flow using NSIS in accordance with one embodiment of the present invention
- FIGURE 4 is a signal flow diagram that illustrates one scenario as to how the exemplary multiservice IP network shown in FIGURE 2 can use the enhanced QoS message to admit an emergency traffic flow without needing to terminate an existing low priority traffic flow using RSVP in accordance with a second embodiment of the present invention.
- FIGURE 5 is a diagram that illustrates the parameters of a minimum QoS object which is part of the enhanced QoS message.
- FIGURE 1 there is a flowchart that illustrates the basic steps of a preferred method 100 which uses an enhanced QoS message that contains two levels of resource reservations which makes it possible for a multiservice IP network and in particular IP router(s) to reserve resources for and then admit an emergency traffic flow without needing to terminate an existing low priority traffic flow.
- an exemplary multiservice IP network 200 is used which is shown in FIGURE 2.
- the exemplary multiservice IP network 200 includes a sender 202, two IP routers 204 and 204' (only two shown) and a receiver 206. It should be understood that certain details associated with the multiservice IP network 200 and its' components are well known in the industry. Therefore, for clarity, the description provided below omits those well known details about the multiservice IP network 200 and its' components that are not necessary to understand the present invention.
- the IP routers 204 and 204' receive a reservation request 208 for a low priority traffic flow 210.
- the receiver 206 also receives the reservation request 208.
- the sender 202 sends the reservation request 208 which contains an enhanced QoS message 212 (QoS Description 212) that includes the following objects:
- a QoS desired object 214a which contains parameters that indicate the desired resources (e.g., bandwidth) which are needed to have a desired QoS for the real-time low priority traffic flow 210; • A minimum QoS object 214d which contains parameters that indicate the reduced resources (e.g., bandwidth) which are needed to have a minimum acceptable QoS for the real-time low priority traffic flow 210 (see FIGURE 5).
- a QoS available object 214b which contains parameters describing the available resources along a reservation path.
- a QoS reserved object 214c which contains parameters describing the reserved resources and related QoS parameters (e.g. Slack Term).
- the IP routers 204 and 204' Upon receiving the reservation request 208, the IP routers 204 and 204' store within their memories 205 and 205 1 the information associated with resources needed for both the desired QoS and the minimum acceptable QoS.
- the IP routers 204 and 204' and in particular their processors 207 and 207' reserve the desired resources for the low priority traffic flow 210.
- the desired resources are identified in the QoS desired object 214a.
- the receiver 206 reserves the desired resources for the low priority traffic flow 210.
- the IP routers 204 and 204' admit the low priority traffic flow 210 using the desired resources that are associated with the QoS desired object 214a.
- the receiver 206 admits the low priority traffic flow 210 using the desired resources.
- the IP routers 204 and 204' receive an emergency reservation request 216 for an emergency traffic flow 218.
- the sender 202 sends the emergency reservation request 216 that contains a QoS message 220 (QoS Description 220).
- the QoS message 220 does not need to have the same objects that are in the enhanced QoS message 212. For instance, the QoS message 220 may not have a minimum QoS object 214d.
- the IP routers 204 and 204' and in particular their processors 207 and 207' make a determination as to whether or not they have enough resources to support the emergency traffic flow 218. If the IP routers 204 and 204' have enough resources, then at step 112 they reserve the desired resources and admit the emergency traffic flow 218. At the same time, the IP routers 204 and 204' still use the desired resources to support the low priority traffic flow 210. Steps 110 and 112 are not shown in FIGURE 2.
- Step 114 determines if it can accept the emergency traffic flow 218 if it reduced the resources for the low priority traffic flow 210 from the desired resources to the reduced resources. Step 114 is not shown in FIGURE 2.
- Step 116 is not shown in FIGURE 2.
- An exemplary policy on exactly which low priority traffic flow(s) 210 (only one described above) is/are terminated is described below with respect to FIGURES 3 and 4. If the IP router 204' can support the emergency traffic flow 218 by reducing the resources of the low priority traffic flow 210, then the IP router 204' at step 118 reduces the resources of the low priority traffic flow 210 from the desired QoS to the minimum acceptable QoS. Step 118 is not shown in FIGURE 2.
- the IP router 204' sends a notification message 222 to the receiver 202 which indicates that the resources for the low priority traffic flow 210 have been reduced to the minimum acceptable QoS. It should be noted that this process does not require any prior negotiation between the sender 202 and IP router 204'. In other words, the IP router 204' determines by itself to reduce the resources for the low priority traffic flow 210.
- the IP routers 204 and 204' admit the low priority traffic flow 210 using the reduce resources associated with the minimum QoS object 214d.
- the receiver 206 also admits the low priority traffic flow 210 using the reduced resources.
- the IP routers 204 and 204' admit the emergency traffic flow 218 using the desired resources identified in the QoS message 220.
- the receiver 206 also uses the desired resources to admit the emergency traffic flow 218.
- the IP router 204' can increase the resources back to the desired QoS for the affected low priority traffic flow 210 if there is an improvement in traffic conditions. How this can be done with refresh messages is described in greater , detail below with respect to FIGURES 3 and 4. As can be seen, step 126 is not shown in FIGURE 2.
- An important aspect of method 100 is that there is a possibility that the low priority traffic flow 210 need not be terminated because of the addition of an emergency call 218 (see steps 110, 114, 118, 120 and 122).
- TWs is all possible because many real-time traffic types transported in IP networks 200 are adaptive to the bandwidth rate.
- AMR adaptive multi rate
- the advantage of this adaptive behavior is twofold: (1) if the transmission conditions are favorable a reduced codec rate is enough to provide an acceptable QoS; and (2) the transmission rate can be decreased from the ideal rate usually without degrading the QoS significantly.
- FIGURE 3 there is a signal flow diagram that illustrates one scenario as to how the exemplary multiservice IP network 200 can use the enhanced QoS message 212 in conjunction with the NSIS QoS application protocol to admit an emergency traffic flow 218 without needing to terminate an existing low priority traffic flow 210.
- the sender 202 initiates the reservation message 208 for a low priority traffic flow 210.
- the reservation message 208 contains QoS descriptors 214a and 214d for both the reserved resources (desired resources) and the reduced resources (minimum acceptable QoS). Reservation is made based on the desired resources in each IP router 204 and 204' along the data path.
- the low priority traffic 210 is admitted using the standard desired traffic rate.
- a high priority reservation request 216 arrives, the high priority reservation is made in each IP router 204 and 204'.
- This IP router 204 makes the reservation for the high priority traffic flow 218 and reduces the reservation of the low priority traffic flow 210 (only one shown) to the acceptable level.
- the IP router 204 then sends the sender 202 a notification message 222 that indicating that the reserved resources are reduced and the transmission should be reduced to the acceptable rate for the affected low priority traffic flow 210.
- the low priority traffic flow 210 is then sent at the reduced rate. After this the high priority traffic 218 can be admitted. It should be noted that there can be more than one affected low priority flow 210 and that number depends on the amount of resources that are needed for the high priority traffic flow 218. A discussion is provided below about the rest of the signals that are shown in FIGURE 3.
- FIGURE 4 there is a signal flow diagram that illustrates one scenario as to how the exemplary multiservice IP network 200 can use the enhanced QoS message 212 in conjunction with the RSVP protocol to admit an emergency traffic flow 218 without needing to terminate an existing low priority traffic flow 210.
- the sender 202 sends a path message 208a which advertises the low priority traffic stream 210.
- the path message 208a may contain a sender traffic specification object (TSpec 214a) describing the reserved resources and may also contain an acceptable sender traffic specification object (TSpec 214d) describing the traffic specification of the acceptable rate. Priority may be indicated as well.
- the receiver 206 sends a resv message 208b containing a flow specification object (FSpec) for the desired rate and an acceptable flow specification object (acceptable FSpec) for the reduced rate.
- FSpec flow specification object
- Acceptable FSpec acceptable flow specification object
- the priority can be indicated as well.
- the low priority traffic flow 210 can be sent at the desired rate from sender 202 to receiver 206.
- the high priority reservation is made in each IP router 204 and 204'. In this scenario, assume that one of the IP routers 204 (for example) does not have enough resources to accommodate both the low priority traffic flow 210 and the high priority traffic flow 218.
- This IP router 204 makes the reservation for the high priority traffic flow 218 and reduces the reservation of the low priority traffic flow 210 (only one shown) to the acceptable level.
- the IP router 204 then sends the sender 202 a resv message 222 (notification message 222) that indicates the resources should be reduced to the reduced rate for the affected low priority traffic flow 210.
- the low priority traffic flow 210 is then sent at the reduced rate. After this the high priority traffic 218 can be admitted. It should be noted that there can be more than one affected low priority flow 210 and that number depends on the amount of resources that are needed for the high priority traffic flow 218.
- the sender 202 may send a refresh message 224a with a desired rate for the low priority traffic flow 210 to try to restore the low priority traffic flow 210 to the reserved traffic rate.
- the reservations for the low priority traffic 210 may be increased in each IP router 204 and 204' after a certain time period if the traffic conditions improve (see step 126 in FIGURE 1). If the reservation with the desired QoS is not possible in an IP router 204 and 204', then this IP router sends back an error message to the sender 202 indicating that increasing the traffic rate for the low priority flow is not possible. In this case, the sender 202 should immediately initiate a refresh with the reduced rate.
- the sender 202 can send a first refresh message 224a with an acceptable rate for the low priority traffic flow 210 so that it remains at a reduced acceptable rate for at least a certain period of time.
- the sender 202 sends a first refresh message 224a which contains the QoS specification for the desired rate to IP router 204 (for example).
- the IP router 204 still cannot reserve resources at the desired rate for the low priority traffic flow 200.
- the IP router 204 sends the sender 202 a response message 226a which indicates that the first refresh message 224a was not successful.
- the sender 202 immediately sends a new refresh message 224b which contains the QoS specification for the reduced rate to IP routers 204 and 204' and receiver 206.
- the receiver 206 then sends a response message 226b which indicates that the second refresh message 226a was successful.
- the sender 202 sends another refresh message 224c which contains the QoS specification for the desired rate to IP router 204.
- the IP router 204 can reserve resources at the desired rate for the low priority traffic flow 200. Therefore, the refresh message 224c is forwarded further to the receiver 206.
- the receiver 206 then sends a response message 226c back to the sender 202.
- This response message 226c indicates that it is ok to upgrade the resources for the low priority traffic flow 210.
- the sender 202 uses the desired rate to send the low priority traffic flow 210 to the receiver 206 via IP routers 204 and 204'.
- a similar mechanism can be applied as well for the scenario shown in
- FIGURE 4 The difference in this scenario is that here the receiver 206 receives the refresh/path message 224a which contains the TSpec and acceptable TSpec and the receiver 206 decides if the refresh should be tried at the reserved rate or the acceptable rate. In this example, the reservation is attempted with the desired rate so the receiver 206 sends a desired FSpec object in resv message 226a to the sender 202. In this example, this reservation is successful for the first attempt. The sender 202 then increases the traffic rate of the low priority traffic flow 210.
- the refresh message 224a besides the desired QoS object 214a and the minimum QoS object 214d also includes a reserved QoS object 214c.
- This refresh is tried for the desired QoS in IP routers 204 and 204', if it is not successful then the refresh is done for minimum QoS.
- the reserved QoS object 214c carries information about the reserved resources in the previously passed IP router(s). This object is updated in each IP router only if the reserved resources in the given IP router are lower than the reserved resources in previous IP routers.
- the reserved QoS object 214c is going to contain the minimum of the reserved resources in the date path. It can also contain values for the desired QoS, the minimum QoS or values between them. This reserved QoS is signaled back to the sender 202 in a response message. It should be noted that, any case, when even the minimum QoS cannot be refreshed, this is an erroneous situation and the standard error handling procedure implemented in a given method is used.
- one or more low priority traffic flows 210 should be terminated (see step 116 in FIGURE 1).
- a local policy can be used to determine the order in which low priority traffic flows 210 are terminated. For instance, pre-emption of the low priority traffic flows 210 can be done in priority order, starting with the lowest priority reservations. And, among the reservations with the same priority, the reservations of low priority traffic flows 210 for which reduced resources are not indicated may be pre-empted first. In this way, the users may have more of an interest to fill in the reduced resource field 214d in the QoS specification object 212. However, it should be noted that indicating reduced resources in the QoS specification object 212 is not mandatory.
- FIGURE 5 there is a diagram that illustrates the parameters of an exemplary minimum QoS object 214d which can be part of the enhanced QoS message 212.
- the exemplary minimum QoS object 214d shown is related to the QoS desired object 214a which has a traffic specification form based on an Integrated Services (IntServ) token bucket and a simple reserved rate.
- the QoS desired object's token bucket model has 5 parameters: token bucket rate (r), token bucket size (b), peak data rate (p), minimum policed unit (m), maximum packet size (M).
- the reserved rate (R) is also signaled, or only R is signaled.
- Each parameter is encoded in 32 bits. The exact definition of these parameters can be found in the aforementioned RFC 2210.
- the traffic specification form for the minimum QoS object 214d can have a similar token bucket descriptor as shown in FIGURE 5.
- the new token bucket descriptor has 5 parameters: acceptable token bucket rate (ar), acceptable token bucket size (ab), acceptable peak data rate (ap), acceptable minimum policed unit (am), acceptable maximum packet size (aM).
- acceptable reserved rate (aR) can also be signaled, or only aR is signaled.
- Each parameter is encoded in 32 bits.
- the relationship between the parameters of the minimum QoS object 214d and the Qos desired object 214a are as follows: ar ⁇ r, ab ⁇ b, p ⁇ ap, aM ⁇ M; aR ⁇ R.
- the descriptors for the acceptable QoS can be the same parameter set as the QoS descriptors, it may be enough to store the regular QoS descriptors and a factor that describes the relative values of the acceptable parameters comparing to the regular ones.
- the reservation and reduced reservation parameters of the enhanced QoS message 212 refer to a whole aggregated flow.
- the present invention is especially useful in this application because emergency reservation can be supported without terminating the whole aggregate of low priority traffic flows 210.
- the number of reservation states in the case of aggregated reservation is low because per micro-flow states are not stored. Therefore, storing the reduced reservation states in addition to the reservation states is not an issue.
- multiservice IP network can be any type of telecommunication network which uses IP as a transport technology.
- the QoS manager is implemented in a telecom control node e.g., SGSN.
- the present invention is related to the resource reservation in the IP transport layer, i.e., in the IP routers. And, the present invention is based on standard resource reservation protocols that can be implemented in commodity routers.
- the traditional QoS manager is able to control only the traffic for which control plane it belongs to, i.e., UMTS. As such, it cannot be used for preempting resources in a multiservice IP network.
- the present invention has a resource management function that is implemented in a standard resource reservation protocol in the transport layer, in a lower layer, which is common for all applications. Therefore, pre-emption of resources for a high priority traffic can be performed in the multiservice IP network.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/IB2005/000547 WO2006092645A1 (en) | 2005-03-03 | 2005-03-03 | Ip multiservice network and method for making resource reservations for priority traffic |
US11/817,737 US7760644B2 (en) | 2005-03-03 | 2005-03-03 | IP multiservice network and method for making resource reservations for priority traffic |
GB0716119A GB2437232B (en) | 2005-03-03 | 2005-03-03 | IP multiservice network and method for making resource reservations for priority traffic |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/IB2005/000547 WO2006092645A1 (en) | 2005-03-03 | 2005-03-03 | Ip multiservice network and method for making resource reservations for priority traffic |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006092645A1 true WO2006092645A1 (en) | 2006-09-08 |
Family
ID=34960932
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/IB2005/000547 WO2006092645A1 (en) | 2005-03-03 | 2005-03-03 | Ip multiservice network and method for making resource reservations for priority traffic |
Country Status (3)
Country | Link |
---|---|
US (1) | US7760644B2 (en) |
GB (1) | GB2437232B (en) |
WO (1) | WO2006092645A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2086173A1 (en) * | 2007-07-16 | 2009-08-05 | Huawei Technologies Co., Ltd. | A method, system and network device for resource management |
FR2928231A1 (en) * | 2008-03-03 | 2009-09-04 | Nexter Systems Sa | METHOD FOR MANAGING DATA FLOW ON A COMMUNICATIONS NETWORK AND DEVICE IMPLEMENTING SUCH A METHOD |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8031603B1 (en) | 2005-06-30 | 2011-10-04 | Cisco Technology, Inc. | Technique for reducing resources allocated to an existing reservation in a data network |
US7558271B2 (en) * | 2005-10-21 | 2009-07-07 | International Business Machines Corporation | Method and apparatus for adaptive bandwidth control with defined priorities for different networks |
US8849297B2 (en) * | 2006-07-14 | 2014-09-30 | Qualcomm Incorporated | Call establishment and maintenance in a wireless network |
EP2090021B1 (en) * | 2006-10-26 | 2012-12-05 | France Télécom | Method for monitoring a plurality of equipments in a communication network |
US7764694B2 (en) * | 2008-03-07 | 2010-07-27 | Embarq Holdings Company, LLP | System, method, and apparatus for prioritizing network traffic using deep packet inspection (DPI) |
US20090238071A1 (en) * | 2008-03-20 | 2009-09-24 | Embarq Holdings Company, Llc | System, method and apparatus for prioritizing network traffic using deep packet inspection (DPI) and centralized network controller |
US8305896B2 (en) * | 2007-10-31 | 2012-11-06 | Cisco Technology, Inc. | Selective performance enhancement of traffic flows |
US8504091B2 (en) | 2008-02-01 | 2013-08-06 | Qualcomm Incorporated | Interference mitigation for control channels in a wireless communication network |
US8599705B2 (en) * | 2008-02-01 | 2013-12-03 | Qualcomm Incorporated | Interference management based on enhanced pilot measurement reports |
US8289852B2 (en) * | 2009-02-18 | 2012-10-16 | Clearwire Ip Holdings Llc | Setting token bucket parameters for scheduling of air-interface resources |
US8190744B2 (en) | 2009-05-28 | 2012-05-29 | Palo Alto Research Center Incorporated | Data center batch job quality of service control |
US8379517B2 (en) * | 2010-06-14 | 2013-02-19 | Alcatel Lucent | Call admission and preemption for multiple bit-rate applications |
US8811281B2 (en) * | 2011-04-01 | 2014-08-19 | Cisco Technology, Inc. | Soft retention for call admission control in communication networks |
US20120320751A1 (en) * | 2011-06-17 | 2012-12-20 | Jing Zhu | Method and system for communicating data packets |
US9094345B2 (en) * | 2012-01-31 | 2015-07-28 | International Business Machines Corporation | Reservation system for an ethernet network |
US9455927B1 (en) * | 2012-10-25 | 2016-09-27 | Sonus Networks, Inc. | Methods and apparatus for bandwidth management in a telecommunications system |
WO2017001634A1 (en) * | 2015-06-30 | 2017-01-05 | British Telecommunications Public Limited Company | Negotiating quality of service for data flows |
US20230171203A1 (en) * | 2021-11-29 | 2023-06-01 | Dish Network Technologies India Private Limited | Internet bandwidth/data management by gateway device |
US11966784B2 (en) * | 2021-12-27 | 2024-04-23 | Rakuten Mobile, Inc. | Cloud-native application reservation management method and apparatus |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010025310A1 (en) * | 2000-02-04 | 2001-09-27 | Srikanth Krishnamurthy | System for pricing-based quality of service (PQoS) control in networks |
EP1193920A2 (en) * | 2000-09-29 | 2002-04-03 | Microsoft Corporation | Improved media streaming methods and arrangements |
EP1211851A1 (en) * | 2000-11-30 | 2002-06-05 | TELEFONAKTIEBOLAGET L M ERICSSON (publ) | Method and system for resource reservation in a multicasting network |
US20030074443A1 (en) * | 2001-10-15 | 2003-04-17 | Makonnen Melaku | Last mile quality of service broker (LMQB) for multiple access networks |
US20030152029A1 (en) * | 2002-02-14 | 2003-08-14 | Alcatel | Control for admission to a data network for providing service quality |
WO2003075523A1 (en) * | 2002-03-05 | 2003-09-12 | Pa Consulting Group | Quality of service management in packet data networks |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0851706A1 (en) * | 1996-12-24 | 1998-07-01 | International Business Machines Corporation | Flow control for very bursty connections in high speed cell switching networks |
US6859438B2 (en) * | 1998-02-03 | 2005-02-22 | Extreme Networks, Inc. | Policy based quality of service |
US6201971B1 (en) * | 1998-03-26 | 2001-03-13 | Nokia Mobile Phones Ltd. | Apparatus, and associated method for controlling service degradation performance of communications in a radio communication system |
GB9822550D0 (en) * | 1998-10-15 | 1998-12-09 | British Telecomm | Computer communications |
US6934258B1 (en) * | 1999-05-26 | 2005-08-23 | Nortel Networks Limited | Quality of service based transitioning between alternate transport paths |
US6574195B2 (en) * | 2000-04-19 | 2003-06-03 | Caspian Networks, Inc. | Micro-flow management |
US20020059432A1 (en) * | 2000-10-26 | 2002-05-16 | Shigeto Masuda | Integrated service network system |
US7035279B2 (en) * | 2001-01-09 | 2006-04-25 | Corrigent Systems Ltd. | Flow allocation in a ring topology |
US7180855B1 (en) * | 2001-04-19 | 2007-02-20 | At&T Corp. | Service interface for QoS-driven HPNA networks |
KR100426357B1 (en) * | 2001-08-08 | 2004-04-06 | 엘지전자 주식회사 | Scheduling Method for QoS and Resource Management in Mobile Communication System |
US20030093526A1 (en) * | 2001-11-13 | 2003-05-15 | Koninklijke Philips Electronics N. V. | Apparatus and method for providing quality of service signaling for wireless mac layer |
US7457287B1 (en) * | 2001-12-31 | 2008-11-25 | Cisco Technology, Inc. | System and method for assigning call priority |
US7477657B1 (en) * | 2002-05-08 | 2009-01-13 | Juniper Networks, Inc. | Aggregating end-to-end QoS signaled packet flows through label switched paths |
US7023843B2 (en) * | 2002-06-26 | 2006-04-04 | Nokia Corporation | Programmable scheduling for IP routers |
US7191231B2 (en) * | 2003-02-12 | 2007-03-13 | Cisco Technology, Inc. | System and method for consistent forwarding of packets across wireless and wireline networks |
US7573819B2 (en) * | 2004-04-01 | 2009-08-11 | Verizon Services Corp. | Methods and apparatus for controlling bandwidth and service in a communications system |
KR101059876B1 (en) * | 2004-06-16 | 2011-08-29 | 엘지전자 주식회사 | Data Transmission Volume Selection Method for Guaranteeing Service Quality of Mobile Communication System |
US7826424B2 (en) * | 2005-10-11 | 2010-11-02 | Toshiba America Research, Inc. | Packet loss prevention during handoff through managed buffer nodes architecture |
US7668081B2 (en) * | 2006-11-10 | 2010-02-23 | Alcatel-Lucent Usa Inc. | Preemptive transmission protection scheme for data services with high resilience demand |
-
2005
- 2005-03-03 WO PCT/IB2005/000547 patent/WO2006092645A1/en not_active Application Discontinuation
- 2005-03-03 US US11/817,737 patent/US7760644B2/en active Active
- 2005-03-03 GB GB0716119A patent/GB2437232B/en not_active Expired - Fee Related
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010025310A1 (en) * | 2000-02-04 | 2001-09-27 | Srikanth Krishnamurthy | System for pricing-based quality of service (PQoS) control in networks |
EP1193920A2 (en) * | 2000-09-29 | 2002-04-03 | Microsoft Corporation | Improved media streaming methods and arrangements |
EP1211851A1 (en) * | 2000-11-30 | 2002-06-05 | TELEFONAKTIEBOLAGET L M ERICSSON (publ) | Method and system for resource reservation in a multicasting network |
US20030074443A1 (en) * | 2001-10-15 | 2003-04-17 | Makonnen Melaku | Last mile quality of service broker (LMQB) for multiple access networks |
US20030152029A1 (en) * | 2002-02-14 | 2003-08-14 | Alcatel | Control for admission to a data network for providing service quality |
WO2003075523A1 (en) * | 2002-03-05 | 2003-09-12 | Pa Consulting Group | Quality of service management in packet data networks |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2086173A1 (en) * | 2007-07-16 | 2009-08-05 | Huawei Technologies Co., Ltd. | A method, system and network device for resource management |
EP2086173A4 (en) * | 2007-07-16 | 2009-11-25 | Huawei Tech Co Ltd | A method, system and network device for resource management |
FR2928231A1 (en) * | 2008-03-03 | 2009-09-04 | Nexter Systems Sa | METHOD FOR MANAGING DATA FLOW ON A COMMUNICATIONS NETWORK AND DEVICE IMPLEMENTING SUCH A METHOD |
WO2009112720A1 (en) * | 2008-03-03 | 2009-09-17 | Nexter Systems | Method of managing data streams on a communications network and device implementing such a method |
Also Published As
Publication number | Publication date |
---|---|
GB2437232A (en) | 2007-10-17 |
US20080192632A1 (en) | 2008-08-14 |
GB2437232B (en) | 2008-08-20 |
GB0716119D0 (en) | 2007-09-26 |
US7760644B2 (en) | 2010-07-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7760644B2 (en) | IP multiservice network and method for making resource reservations for priority traffic | |
EP1312226B1 (en) | DYNAMIC QoS MANAGEMENT IN DIFFERENTIATED SERVICES USING BANDWIDTH BROKERS, RSVP AGGREGATION AND LOAD CONTROL PROTOCOLS | |
US6931448B2 (en) | Method, server and arrangement in a communication network | |
KR100547139B1 (en) | METHOD AND APPARATUS FOR DELIVERING MPEG MEDIA DATA USING IETF QoS PROTOCOLS | |
US20060218302A1 (en) | Communication system and communication method | |
AU2007353984B2 (en) | Priority flow handling in stateless domains | |
CN101330445B (en) | Method for implementing load-bearing path as well as apparatus and system thereof | |
US8031603B1 (en) | Technique for reducing resources allocated to an existing reservation in a data network | |
US7428216B2 (en) | Method and apparatus for policy and admission control in packet-based communication systems | |
EP2433443B1 (en) | Methods and apparatuses for a dynamic resource reservation | |
US8908684B2 (en) | Method and communication system for selecting a transmission mode for transmitting payload data | |
US20060274650A1 (en) | Avoiding unnecessary RSVP-based preemptions | |
US6920499B2 (en) | Resource reservation in third generation telecommunication network by comparing RSVP messages | |
JP2009105949A (en) | TERMINAL CAPABLE OF EXECUTING QoS CONTROL | |
Cisco | Quality of Service for Voice over IP | |
KR100384934B1 (en) | Method of controlling a resource reservation using two-pass rsvp over sbm network | |
Olaussen et al. | A policy-based priority and precedence framework for military IP networks | |
KR100766033B1 (en) | Method of Guarantee for End-To-End Quality of Service using SIP and RSVP-TE | |
Dhesikan | H. 323/RSVP Synchronization for Video over IP | |
WO2003075521A1 (en) | Packet data communications networks | |
BANDBREITEN-MAKLERN et al. | RSVP AGGREGATION AND LOAD CONTROL PROTOCOLS | |
Rodríguez et al. | Quality of Service Mechanisms | |
Salehin et al. | MPLS Core Network for an Interworked NGN Providing QoS |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
ENP | Entry into the national phase |
Ref document number: 0716119 Country of ref document: GB Kind code of ref document: A Free format text: PCT FILING DATE = 20050303 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 0716119.3 Country of ref document: GB |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11817737 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: RU |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 05708657 Country of ref document: EP Kind code of ref document: A1 |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 5708657 Country of ref document: EP |