WO2003075523A1 - Gestion de qualite de service dans des reseaux de paquets de donnees - Google Patents

Gestion de qualite de service dans des reseaux de paquets de donnees Download PDF

Info

Publication number
WO2003075523A1
WO2003075523A1 PCT/GB2003/000970 GB0300970W WO03075523A1 WO 2003075523 A1 WO2003075523 A1 WO 2003075523A1 GB 0300970 W GB0300970 W GB 0300970W WO 03075523 A1 WO03075523 A1 WO 03075523A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
transmission
packet data
resources
data stream
Prior art date
Application number
PCT/GB2003/000970
Other languages
English (en)
Inventor
Simon Charles Durrant
John David Ainsworth
Original Assignee
Pa Consulting Group
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Pa Consulting Group filed Critical Pa Consulting Group
Priority to AU2003209476A priority Critical patent/AU2003209476A1/en
Publication of WO2003075523A1 publication Critical patent/WO2003075523A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • 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/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/762—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 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/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/80—Actions related to the user profile or the type of traffic
    • H04L47/803—Application aware
    • 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/805—QOS or priority aware
    • 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/808—User-type aware
    • 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/824—Applicable to portable or mobile terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • the present invention relates to packet data communications networks, and more particularly, to optimising the allocation of transmission resources between applications executing on a packet data communications device.
  • the invention has been developed primarily for mobile wireless communications networks such as GPRS and UMTS. However, it will be appreciated by those skilled in the art that the invention is not limited to use with those particular technologies.
  • an application can specify the quality of service it requires for each of the data streams that it uses to send and/or receive packetised data to/from other applications.
  • Each data stream is sent over a packet switch connection.
  • the connection is defined by a Packet Data Protocol (PDP) context and is known as a UMTS bearer.
  • PDP Packet Data Protocol
  • the PDP context is used to specify the attributes of the connection and hence the qualify of service provided by that connection.
  • PDP context Packet Data Protocol
  • RAB Radio Access Bearer
  • the attributes that can be set for each PDP context are as follows:
  • a subset of the other attributes is defined as being applicable to that class. For example in both the conversational and streaming classes, all attributes are applicable with the exception of traffic handling priority.
  • An application executing on a mobile device will request a connection to be set-up for each one of the data streams it will use.
  • the application's view of the connection is termed a socket.
  • the application requests a socket to be set-up it will specify the quality of service attributes it requires for the connection such that it is appropriate for the type of data to be transmitted. It is obvious that these could be specified in terms of the PDP context attributes or other suitable set of parameters which can be mapped to PDP context attributes.
  • the entity that deals with the application's connection requests is termed a QoS Manager. It will determine if an existing PDP context could be used for the connection or whether a new UMTS bearer should be set up.
  • the QoS manager will associate the application's socket with that bearer. In this way packets sent on a particular socket are delivered to a particular bearer with the correct QoS attributes.
  • the network may change the attributes of a UMTS bearer at any time, typically in response to changes in traffic loading.
  • the network notifies the QoS manager when a modification to a PDP context is required, and it will then in turn notify the applications that have sockets that are bound to the changed PDP context.
  • the application can then adjust its data transfer accordingly, or may even decide to terminate if the required qualify of service is no longer available.
  • An application may also request a modification to the QoS attributes of any of its connections, which may result in the mobile device initiating a PDP modification to the network. The above works well if each application has a unique PDP context and hence bearer for each data stream, as the application can respond directly to changes.
  • the QoS manager when two or more sockets are bound to a single PDP context and the bit rate of the bearer changes, the QoS manager must determine the impact to each of the affected data streams. The fairest way is to simply adjust the bit rate allocated to each socket by the same fraction, and in the absence of any further information this is all that can be achieved. Some applications will be able to reduce their output accordingly, whilst some applications will terminate their execution, as the quality of service required no longer exists. A more intelligent QoS manager with more information at its disposal could make better decisions about how a change in a PDP context should affect the individual data streams of each application. In the above example, if the QoS manager knew how each application would be affected by a change in the bit rate, then it could adjust the bit rate for each socket such that at least the minimum required quality of service was maintained for both applications.
  • the present invention provides a method of optimising the allocation of shared transmission resources between two or more packet data streams of applications executing in a device in a packet data communications network, in which said device includes a transmission resource manager function, the method characterised in that each application specifies a range of acceptable values for one or more of the parameters that determine the transmission quality of its data stream; and the transmission resource manager function allocates the available transmission resources to all the data streams in dependence on the range of acceptable values supplied by each application.
  • the invention provides a device comprising the means for optimising the allocation of shared transmission resources between two or more packet data streams of applications executing on said device in a packet data communications network, said device including a transmission resource manager function, and means for the application to specify a range of acceptable values for one or more of the parameters that determine the transmission quality of its data stream; the transmission resource manager function being adapted to allocate the available transmission resources to all the data streams in dependence on the range of acceptable values supplied by each application.
  • the application supplies for each parameter a range in the form of a target value, which is the preferred value for the application, and a limit value, which is the minimum acceptable value for the application.
  • one of the parameters specifies the guaranteed bit rate for a packet data stream.
  • one of the parameters specifies the maximum bit rate for a packet data stream.
  • one of the parameters specifies the bit error rate for a packet data stream.
  • one of the parameters specifies the transfer delay for a packet data stream.
  • An application can request a new packet data stream from the transmission resource manager function of the device, and the transmission resource manager function preferably attempts to acquire the transmission resources required to provide the target value of each of the transmission parameters specified by the application from the network and when the required resources are not available from the network, reallocates the resources already amongst the data streams of the applications such that the number of data streams utilising the available transmission resources is maximised and each data stream is allocated at least the limit value for each transmission parameter specified; each application being informed by the transmission resource manager function of the new allocation.
  • the network can change the resources allocated to the transmission resource manager function of a device at any time, in which case the transmission resource manager function preferably reallocates the available resources amongst the data streams of the applications such that the number of data streams utilising the available transmission resources is maximised; and each data stream is allocated at least the limit value for each transmission parameter specified; and each application is informed by the transmission resource manager of the new allocation.
  • An application can change the ranges requested for any transmission parameter of any packet data stream at any time, and the transmission resource manager function then preferably attempts to acquire the transmission resources required to provide the target value of each of the transmission parameters specified by the application from the network; and when the required resources are not available from the network, reallocates the resources already acquired amongst the data streams of the applications such that the number of data streams utilising the available transmission resources is maximised, and each data stream is allocated at least the limit value for each transmission parameter specified; each application being informed by the transmission resource manager of the new allocation.
  • the transmission resource manager function determines the actual value of the parameters of the transmission resources to request from the network for a packet data stream ensure that the value to be requested for a parameter is within the range specified by the application for said packet data stream; and the transmission resource manager function uses tariff information for determining the cost per unit time of the transmission resources at the current time of day, and ensures that the cost per unit time of the transmission resources to be requested from the network for all the packet data streams of an application or all the packet data streams active on the device are within a user specified range.
  • the device is a mobile terminal attached to a GPRS packet data network.
  • Figure 1 is a simplified schematic diagram of a packet data communication system showing terminals, an access network, a core network, and other packet data networks;
  • FIG. 2 is a simplified schematic diagram of a UMTS communication system showing two mobile terminals, a radio access network, a UMTS backbone and a gateway to other IP networks;
  • Figure 3 is a simplified schematic of the architecture of the protocol stack of a wireless packet data communications device that supports QoS;
  • Figure 4 shows the different types of PDP QoS attributes for a RAB
  • Figure 5 is an entity relationship diagram in UML notation showing the relationships and cardinalities of the relationships between objects involved in quality of service enabled packet data communications;
  • Figure 6 is a message sequence chart showing the sequence of events and actions when an application running on a UMTS mobile terminal opens a QoS enabled socket;
  • Figure 7 is a message sequence chart showing the sequence of events and actions when a UMTS network initiates a change in the quality of service attributes of a UMTS bearer in use by a UMTS mobile terminal;
  • Figure 8 is a message sequence chart showing the sequence of events and actions when a UMTS network reduces the bandwidth of a RAB over which an application is transmitting on the uplink;
  • Figure 9 is a message sequence chart showing the sequence of events and actions when a UMTS network reduces the bandwidth of a RAB over which an application is receiving on the downlink;
  • Figure 10 is a diagram illustrating how the bandwidth or a wireless bearer is shared between a first and a second application, when the first application has a flexible QoS policy profile;
  • Figure 11 is a diagram illustrating how the bandwidth or a wireless bearer is not shared between a first and a second application, when the first application has a inflexible quality of service policy profile, resulting in the establishment of a second bearer for the second application;
  • Figure 12 is a diagram illustrating how a network initiated change in the bit error rate of one wireless bearer can result in a reconfiguration of the mapping of applications to wireless bearers and a corresponding change in the bandwidth allocated to the applications, in order to accommodate all applications within the quality of service attribute ranges specified in their quality of service policy profiles.
  • the preferred embodiment of the present invention is applied to packet data communication terminals that are able to provide guarantees of quality of service (QoS) of packet data communications to applications executing on the terminal and the associated networks that support guaranteed QoS packet data communication.
  • QoS quality of service
  • a packet data communications network 100 The network is composed of different network elements, which cooperate to provide the end-to-end connectivity.
  • the packet data terminal 101 is the endpoint of communication on the network. It provides the initial point of access to the network for user applications.
  • Each packet data terminal has at least one network address that uniquely identifies it to the network and hence allows packetised data to be sent to a specific terminal based upon this address.
  • the packet data terminal is physically connected to the access network 105 of the packet data communications network by the access link 103.
  • the access network 105 and the access links 103 may be either wireline or wireless.
  • the access network 105 manages terminal connectivity with its access control function 106. This function determines whether terminals are authorised to connect, the resources they are allowed for connection based upon policy, and provides accounting of the usage of terminal or access resources. It is also responsible for the resource management of the access network and providing guarantees on QoS of access links used by terminals.
  • the access network 105 is connected by a high bit rate connection 107 to the core packet data network.
  • one aspect of the access network is to convert between the link layer technologies of the access link to the link layer technology of the core packet data network.
  • the core packet data network provides connectivity to a plurality of access networks and hence packet data terminals.
  • the core packet data network also provides connectivity 109 to other packet data networks 110, and hence to packet data terminals in other networks.
  • the core packet data network may be QoS enabled in that it provides guarantees on, for example, the bandwidth available or the delay for a packet data stream, between two packet data terminals. It will be appreciated that a single core packet data network may have a plurality of access networks that in turn provide access to a plurality of packet data terminals.
  • the core packet data network may also provide connectivity to a plurality of other packet data networks.
  • IPv4 Internet Protocol version 4
  • IPv6 Internet Protocol version 6
  • Figure 1 is a schematic view of a packet data communications network, and that many different installations are possible, utilising a wide range of technologies and protocols.
  • Figure 2 is a Universal Mobile Telecommunications System (UMTS) packet data network.
  • UMTS Universal Mobile Telecommunications System
  • the UMTS packet data network will be used throughout but the invention is not restricted to a UMTS packet data network.
  • the mobile terminals (MT) 121 are the endpoints of communication on the network. They are connected to the Radio Access Network (RAN) 127 via the Uu interface, which uses Wideband Code Division Multiple Access (WCDMA) technology.
  • the RAN is composed of the so-called Node-B base stations, and the Radio Network Controller (RNC) 129 which manages the resources of the radio network.
  • the core packet data network is effectively composed of the Serving GPRS Support Node (SGSN) 131, which provides connectivity to access networks, the UMTS backbone 133, and the Gateway GPRS Support Node (GGSN) 135, which provides interconnectivity to other IP networks 137.
  • the UMTS backbone provides connectivity between SGSN and GGSN.
  • the connection between MT and SGSN is known as the Radio Access Bearer (RAB) Service.
  • RAB Radio Access Bearer
  • the QoS of each Radio Bearer that is set up is managed by the RNC. It also performs dynamic allocation of the finite radio resources available for data transmission across the RABs from the terminals.
  • QoS for packet data communication means guaranteeing that the characteristics of an end-to-end application data connection will be maintained for said application data connection. These characteristics include, but are not limited to, bit rate, delay, and error rates. In order to achieve these guarantees, the network must ensure that:
  • data packets carry an indication of how they should be treated by the network; and resources are reserved across the network so that phenomena such as congestion are avoided; and - the links of the network path that a packet is sent on have the desired characteristics such as bit error rate.
  • a packet data communications terminal 300 Some operational units and protocol layers of the terminal are shown where required for the description of the invention. All possible operational units and protocol layers are not shown. It will also be appreciated that there could be many specific instances of protocol layers and operational units used in the terminal, where in Figure 3, a schematic of the protocol layer or operational unit is used.
  • the terminal provides an execution environment for applications 311. Examples of applications which require packet data communications with other terminals or servers include, but are not limited to, email (using SMTP), web browsers (using HTTP), packetised voice (using SIP and RTP/RTCP) and streaming video (using RTSP and RTP/RTCP).
  • Socket API socket application programming interface
  • This interface provides programmatic routines that allow an application to open a data stream for reading and/or writing between itself and another application resident on another terminal or server in the network.
  • a second API 309 is provided to the application by the terminal's operating system through which the application can request that particular QoS attributes are guaranteed for a data stream. This is termed the quality of service application programming interface (QoS API).
  • QoS API quality of service application programming interface
  • the packet data protocol layer 308 is an implementation of packet data communications protocol on the terminal and is accessed by the application through the Socket API. There are many different packet data protocols such as Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6) and X.25. This protocol layer takes in data from the application via a socket and processes and formats it in accordance with the protocol. The protocol layer can provide various different types of packet data communication to the application.
  • IPv4 Internet Protocol version 4
  • IPv6 Internet Protocol version 6
  • X.25 X.25
  • IPv4 and IPv6 provide an unreliable datagram service using UDP and a reliable streaming service using TCP.
  • the packet data protocol layer may also provide mechanisms for guaranteeing end-to-end quality of service.
  • IPv4 RSVP can be used to reserve resources across a network.
  • the line 301 divides the packet data protocol layer 308 and the link layer protocols.
  • the link layer protocol (303 and 304) is responsible for establishing channels in the underlying physical transmission medium and for formatting and processing the packets received from the packet data protocol layer for transmission.
  • the link layer protocol is separated into two parts, a control function 303 and a data function 304.
  • the control function 303 is used for establishing and managing channels, setting up QoS characteristics for the channel and responding to network initiated changes in the QoS.
  • the data function 304 performs the task of processing the packets received from the packet data protocol layer and transmitting them on to the actual physical network interface, and processing packets received from the physical network interface and transmitting them to the packet data protocol layer.
  • QoSM quality of service manager
  • the QoSM 305 provides the implementation behind the QoS API. In the prior art it is known to provide the following functions: - determine whether a data transmission channel needs to be established or whether an existing data transmission channel is to be reused in response to an application request for a specific QoS for a data stream;
  • the QoS API provides a way for the application to request that a particular data stream has certain attributes, which are collectively termed the QoS Profile.
  • each bearer has values for each of these attributes:
  • the specific set of values of the QoS attributes associated with a bearer is contained within the PDP Context.
  • the actual values of the QoS attributes of each PDP context are controlled by the network and may be modified by the network at any time.
  • the network manages the available resources such that each user is allocated a fair share in accordance with the network operator's policy.
  • the application may also request at any time a modification to the QoS Profile associated with a particular data stream.
  • the QoS attributes of the PDP context can be categorised as either:
  • Asymmetric attributes have independent values in the send and receive directions respectively, and they may be the same or they may be different. Symmetric attributes must take on the same value in both the send and receive directions.
  • Non-cumulative attributes have the property that every data stream that is using the PDP context takes on the same value for that attribute. For example, the residual bit error ratio is non-cumulative as it is the same for all data streams on the same bearer. Cumulative attributes are those attributes that can be must be sub-divided between the data streams using the bearer. For example, if three data streams are sharing a single PDP context, then the guaranteed uplink bit rate of the PDP context must be shared between the data streams. The value of cumulative PDP context attributes can be changed, but this does not necessarily result in a change of said attribute for all application data streams using that PDP context.
  • Figure 4 shows the breakdown of the PDP QoS attributes.
  • FIG. 5 there is shown a relationship diagram in the Unified Modelling Language (UML) notation, which illustrates the relationship between the key entities in a packet data terminal involved in IP packet data communication with QoS.
  • An application 208 executing on a packet data terminal opens sockets to write 202 and sockets to read 322 for its transmit data streams 201 and receive data streams 321.
  • An application can open one or more read or transmit data streams and hence read or write sockets, but only one application can use any specific socket.
  • the operating system of the packet data terminal associates each write socket with a physical bearer downlink 203 which will be used for the transmission of packet data, and each read socket with a physical bearer uplink 323 which will be used for the reception of packet data.
  • a single physical bearer 207 may be used to transmit or receive the data packets of one or more sockets.
  • IP address identifies an endpoint of communication to the network.
  • Each data packet contains a recipient address, which is composed of an IP address and a port number so that any packet can be first delivered to the correct terminal and secondly delivered to the correct socket and hence application on said te ⁇ ninal.
  • the combination of IP address and port number is known as the transport address.
  • Associated with each write socket 202 are a destination IP address of a remote host 205 and a port number on that remote host.
  • Associated with each read socket 322 are an IP address on the local host 325 and a port number on the local host.
  • Each physical bearer 207 has a set of bearer QoS attributes 206 which defines the QoS that packets transported on said bearer will receive on the uplink and downlink. For UMTS packet data this is known as the PDP context.
  • the application opens a socket for reading or writing it will specify the QoS it requires for that socket.
  • the QoS manager in the packet data terminal must associate with that socket a physical bearer with the same QoS attributes specified by the application for the socket. Once the resources have been allocated to the socket, the QoS manager informs the application of the values of the QoS attributes allocated to the socket.
  • FIG. 6 there is shown a message sequence chart of the prior art for an application 210 executing on a UMTS mobile terminal 219 opening a QoS enabled IP data stream for communication with a server 215 in the packet network.
  • the application 210 requests the QoS Manager 211 to create a connection with the required QoS attributes in the UMTS network 221.
  • the UMTS protocol stack creates an Activate PDP Context Request 223 and sends it to the UMTS network 214.
  • the UMTS network responds with a positive acknowledgement 224 and the PDP context is established in the network.
  • This acknowledgement is received by the UMTS stack, which forwards it 225 to the QoS manager.
  • the QoS manager With the PDP context now set up and hence also the UMTS bearer, the QoS manager can now open the end to end IP connection with the server tlirough the IP stack 226. The details of the TCP/IP protocol exchange 227 are not shown.
  • the IP stack acknowledges positively to the QoS manager 228, which then provides the application with a reference to the socket 229. End-to-end QoS can be established by the QoS manager once the PDP context and associated RAB has been established, but before returning the socket reference to the application. Further detailed information is available in the Third Generation Partnership Project (3 GPP) technical specifications TS23.107 and TS23.207.
  • the SGSN 121 detects a need to modify the QoS attributes of a PDP context 231, possibly due to cell loading for example. It instructs 232 the Radio Access Network 127 to modify the Radio Access Bearer in accordance with the new QoS attributes supplied 233.
  • the SGSN requests the GGSN that the PDP context of the UMTS bearer is updated 235.
  • the GGSN updates its internal memory 236, and then signals the change 237, 238 to the Mobile Terminal 219 via the SGSN.
  • the QoS Manager 211 in the MT handles the PDP context modification message and updates its internal memory of the PDP context for that bearer to reflect the change in QoS 239. It acknowledges the PDP context modification back to the network 241.
  • the QoS manager determines which applications have data streams that are affected by the PDP context change and informs them of the new settings in turn 242, 243, 244. Finally, if any application's data streams were assigned to a new PDP context, then the Traffic Flow Template in the GGSN must be updated 245.
  • the prior art applications can specify the attributes that they require of the data transmission path to achieve a certain QoS, and the QoSM will allocate the resources if available or request more resources from the network.
  • an existing PDP context has matching QoS attributes and is reused.
  • the extra bandwidth required to accommodate the new data stream on said PDP context is requested from the network;
  • the request for resources from the network may fail, and the application must be informed that its QoS requirements cannot be met. It is then up to the application to determine what it should do next. It may choose to terminate or request a lower QoS for its data stream.
  • An application can request at any time that its QoS for a data stream should be changed.
  • the application using an uplink makes a request of the QoSM for more bandwidth.
  • the QoSM can request that the network allocated more bandwidth to the PDP context. This may be successful, but it may also fail. If it fails, then the QoSM may have the option of reallocating bandwidth that other applications are using on the same PDP context. However, the QoSM does not know how a reallocation of bandwidth on the uplink will affect the transmit data streams of other applications.
  • the application using an uplink may request a reduction in the bandwidth it requires for a transmit data stream.
  • the QoSM can simply return the resources to the network, or alternatively reallocate it to the data streams of other applications using the uplink that are active.
  • the QoSM cannot make an intelligent decision about how to allocate the excess bandwidth to applications using the uplink.
  • the network can change the PDP context at any time in accordance with its resource control algorithms, which affects the QoS granted to the data streams whose sockets are using the uplink or downlink of the corresponding physical bearer.
  • the RNC reduces the uplink bandwidth of a PDP context.
  • the QoSM must decide how each transmit data stream using the uplink is affected by this change, and inform the affected applications. In the case where there is only a single transmit data stream on the PDP context, this is straightforward.
  • the QoSM must pass the entire reduction on to the single transmit data stream and it's associated application.
  • the QoSM when there are two or more transmit data streams the QoSM must distribute the reduction on to each data stream and associated application in equal measures, because it does not know how each transmit data stream and associated application will be affected. This is not necessarily the optimal action, as one application may be more tolerant to a reduction in bit rate than the other, but the QoSM does not have this information. Alternatively, one application may accept the same bit rate on a data stream but at a higher bit error rate, which may be available.
  • the radio network controller increases the bandwidth of a PDP context.
  • the QoSM lacks the information to make an intelligent decision about how this new bandwidth should be optimally distributed between the data streams and their respective applications sharing this PDP context.
  • the application makes available to the QoSM additional information about the QoS it requires for each of its data streams, such that the QoSM is able to manage the resources made available by the network between multiple applications more effectively than in the prior art.
  • the application provides to the QoSM what is termed a QoS policy profile (QPP) for each socket that it opens.
  • QPP QoS policy profile
  • the value that the application requires for ideal operation This is termed the target value.
  • QoS attributes In a preferred embodiment the following QoS attributes would be specified in terms of target, and limit values:
  • target and limit values can be applied to any QoS attribute that can take on a range of values and it is not limited to those specified above.
  • the user can change the QPP for an applications packet data streams through an application configuration tool.
  • applications will have these values permanently fixed by the application developer.
  • the QoSM utilises the QPP supplied by the application for the data streams to perform intelligent management of the transmission resources allocated to it by the network such that:
  • Each application can be allocated a fair share of the resources available. The maximum possible number of simultaneous streams is maintained. It is an object of the present invention that the QoSM will always attempt to obtain from the network the target value of a QoS attribute for a data stream, specified by the application in the QPP. If the target values for QoS cannot be obtained, for example, because the network is heavily loaded, then the QoSM will reallocate some of the available resources such that each data stream of each application has at least the limit values specified in its QPP for its allocated QoS.
  • the QoSM will use an algorithm to determine which QPPs will be satisfied with their limit resources and which will not be satisfied.
  • This algorithm can be, though is not limited to, one of the following:
  • the QoSM will allocate them according to an algorithm such as, though not limited to:
  • the QoSM will use the QPP as described above whenever a change in resource allocation is required, specifically:
  • the QoSM will use tariff information available to it, for example, in a terminal's memory, which provides information about the costs of different QoS at different times of the day, along with a specified user preference for how much a packet data communication session for the specific application should cost, to determine whether
  • the QPP enables the QoSM to vary the QoS provided to an application in order to maintain a user specified cost for the service.
  • the invention is equally applicable whether an application is transmitting data, receiving data or both over the UMTS network. Transmit data streams will be transmitted over a RAB uplink, and receive data streams will be received over a RAB downlink. For each type of data stream, a QPP will be specified by the application to the QoSM. In the case of transmit data streams, the application will set the target and limit of QoS parameters based on its requirements. In the case of receive data streams, it will set the target and limit of QoS parameters based on the requirements of the entity transmitting. These requirements will have been communicated to the application from the entity transmitting.
  • the QoSM takes action using the QPPs and notifies the application.
  • the application will use the modified QoS parameters received from the QoSM to modify its output as in Figure 8.
  • An application 500 is transmitting data 510 to a receiver 502 over a RAB.
  • a network generated reduction in the bandwidth of this bearer occurs 511.
  • the application is notified of this reduction and reduces it's output bitrate 512.
  • the application will pass on notice of these changes in the Qo parameters to the transmitting entity as in Figure 9.
  • An application 500 is receiving data 520 from a transmitter 503. At some time later, a network generated reduction in the bandwidth of this bearer occurs 511. Through a dialogue with the QoSM the application is notified of this reduction and notifies the transmitter 522. Transmitter 503 then reduces it's output bitrate 523. Also as a result of the reduction of bandwidth 511, it may be necessary to reallocate the receive data streams onto different RABs. This would involve updating the Traffic Flow Templates (TFT) of the existing DPP contexts.
  • TFT Traffic Flow Templates
  • an application 401 has one transmit data stream using a DPP context 403.
  • Its target bit rate, BR(A)TARGET is equal to the unlink guaranteed bit rate of 403, BR PD po.
  • Its limit bit rate, BR(A) L IM ⁇ T is half of its target bit rate, BR(A) TA G ET-
  • Another application 402 is launched which can use the same DPP context (because Qom attributes such as error rate or delay are suitable for the second application) 404 (may even be the only one available as with GPIs) for its transmit data stream. No more resources are available from the network.
  • the QoSM can then determine that both applications can share the 404 if the sum of their limit bit rates, BR(A) ⁇ M ⁇ T + BR(B)LIMIT, is less than the PDP bit rate, BRPDPO.
  • the application must either request the minimum values acceptable, e.g. BR LM T, or request its ideal value, e.g. BRTARGET.
  • the application will always deliver to the user a sub-optimal experience, but will not monopolise the available resources.
  • it can deliver to the user high quality but will monopolise the resources and starve other applications to the extent that it can prevent them from executing.
  • an application 411 has one transmit data stream using a PDP context 413.
  • Its target bit rate, BR(A) TARGET is equal to the uplink guaranteed bit rate of the 413, BR PD po- Its limit bit rate BR(A) I T is, for example, 80% of its target bit rate, BR(A) TA RGET.
  • the sum of the two limit bit rates, BR(A) LMT + BR(B) LMT is greater than the total available bandwidth on the uplink of the bearer BR PDPO .
  • the cost of network resources varies over time. Peak time usage is more expensive than off-peak.
  • the QoSM can use this tariff information combined with the QPP to trade off cost and quality in accordance with the users configuration.
  • QPP The usage of a QPP is independent of where it is stored during application execution. In the preferred embodiment, it is passed to the QoSM, which can then autonomously make decisions about how to manage the QoS. In another embodiment, it is retained in the application, and the QoSM will offer new QoS attributes for a data stream to the application, which the application can then either accept or reject based upon its QPP. This embodiment is less efficient because of this negotiation procedure between the applications and the QoSM. It is also only possible for QoS " aware applications.
  • the characteristic feature of this invention is that specifying a limit value and a desired value for each QoS attribute enables the QoSM to perform intelligent management of the tramission resources.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne l'optimisation de l'attribution de ressources partagées entre deux ou plusieurs flux de données par paquets d'applications s'exécutant dans un dispositif de réseau de communications de données par paquets. Le dispositif comprend une fonction de gestion de ressource d'émission. Chaque application spécifie un domaine de valeurs acceptables concernant un ou plusieurs paramètres déterminant la qualité d'émission de son flux de données, et la fonction de gestion de ressource d'émission attribue les ressources disponibles d'émission à tous les flux de données en fonction du domaine des valeurs acceptables fourni par chaque application. Pour chaque paramètre, l'application fournit, de préférence, un domaine sous la forme d'une valeur cible, représentant la valeur préférée pour l'application, et une valeur limite représentant la valeur minimum acceptable concernant l'application.
PCT/GB2003/000970 2002-03-05 2003-03-05 Gestion de qualite de service dans des reseaux de paquets de donnees WO2003075523A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2003209476A AU2003209476A1 (en) 2002-03-05 2003-03-05 Quality of service management in packet data networks

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB0205105.0 2002-03-05
GB0205105A GB2386282A (en) 2002-03-05 2002-03-05 Allocating shared resources in a packet data communications network

Publications (1)

Publication Number Publication Date
WO2003075523A1 true WO2003075523A1 (fr) 2003-09-12

Family

ID=9932286

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB2003/000970 WO2003075523A1 (fr) 2002-03-05 2003-03-05 Gestion de qualite de service dans des reseaux de paquets de donnees

Country Status (3)

Country Link
AU (1) AU2003209476A1 (fr)
GB (1) GB2386282A (fr)
WO (1) WO2003075523A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005032066A1 (fr) * 2003-09-30 2005-04-07 Nokia Corporation Procede d'ordonnancement de paquets de donnees provenant de differents trains transmis par un terminal sans fil
FR2860679A1 (fr) * 2003-10-03 2005-04-08 Nec Technologies Uk Ltd Procede de selection d'un service support dans un reseau de telecommunication cellulaire
WO2006092645A1 (fr) * 2005-03-03 2006-09-08 Telefonaktiebolaget Lm Ericsson (Publ) Reseau multiservice a protocole internet (ip) et procede d'etablissement de reservations de ressources pour trafic prioritaire
US8279887B2 (en) 2005-11-09 2012-10-02 Telefonaktiebolaget Lm Ericsson (Publ) Selection of radio resources in a radio communications network
CN102934403A (zh) * 2010-06-18 2013-02-13 斯凯普公司 控制网络上的数据传输
CN103404096A (zh) * 2011-01-27 2013-11-20 高通股份有限公司 用户设备发起的和网络发起的服务质量流的共存
CN104618968A (zh) * 2004-04-08 2015-05-13 核心无线许可有限公司 在具有双重传送模式的移动无线系统中控制传输资源

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005099294A1 (fr) * 2004-04-08 2005-10-20 Nokia Corporation Regulation de ressources de transmission dans des systemes de radiocommunication mobiles dotes d'un mode de transfert mixte
CN100514961C (zh) 2004-08-02 2009-07-15 华为技术有限公司 一种网际协议服务质量的信令交互方法
EP1961251B1 (fr) * 2005-12-12 2012-02-29 Telefonaktiebolaget LM Ericsson (publ) Procede et structure pour etablir une session de communication multimedia
US8849297B2 (en) 2006-07-14 2014-09-30 Qualcomm Incorporated Call establishment and maintenance in a wireless network
FR2934745B1 (fr) * 2008-07-30 2014-06-06 Radiotelephone Sfr Terminal multimode a connexions optimisees
US8599720B2 (en) * 2009-06-26 2013-12-03 Qualcomm Incorporated Optimized resource usage with network initiated QoS
CN102396259A (zh) * 2009-10-31 2012-03-28 华为技术有限公司 无线通信系统中确定服务质量达标的方法
US9179381B2 (en) 2011-09-29 2015-11-03 Qualcomm Incorporated Reducing network-initiated QoS interruption time when radio and core networks are out of synchronization due to different underlying technologies
CN112020873B (zh) * 2018-05-03 2022-04-22 华为技术有限公司 用于发送和接收数据包流的方法和相关设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998053576A2 (fr) * 1997-05-20 1998-11-26 Telefonaktiebolaget Lm Ericsson Procede relatif au systeme gprs (service de radiocommunication generale par paquets) fournissant des connexions a commutation par paquets
WO1999005828A1 (fr) * 1997-07-25 1999-02-04 Telefonaktiebolaget Lm Ericsson (Publ) Qualite dynamique de reservation de service dans un reseau de communications mobile
WO1999048310A1 (fr) * 1998-03-19 1999-09-23 Nokia Networks Oy Procede de controle de la qualite de service dans un systeme de communications mobile
WO2000013436A2 (fr) * 1998-08-28 2000-03-09 Nokia Oy Procede et systeme pour prendre en charge la qualite du service dans des reseaux sans fil
EP1154664A1 (fr) * 2000-05-09 2001-11-14 Lucent Technologies Inc. Réservation de ressources dans un réseau de télécommunication de troisième ou future generation

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5675573A (en) * 1995-03-22 1997-10-07 Lucent Technologies Inc. Delay-minimizing system with guaranteed bandwidth delivery for real-time traffic
US5892754A (en) * 1996-06-07 1999-04-06 International Business Machines Corporation User controlled adaptive flow control for packet networks
US6714515B1 (en) * 2000-05-16 2004-03-30 Telefonaktiebolaget Lm Ericsson (Publ) Policy server and architecture providing radio network resource allocation rules

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998053576A2 (fr) * 1997-05-20 1998-11-26 Telefonaktiebolaget Lm Ericsson Procede relatif au systeme gprs (service de radiocommunication generale par paquets) fournissant des connexions a commutation par paquets
WO1999005828A1 (fr) * 1997-07-25 1999-02-04 Telefonaktiebolaget Lm Ericsson (Publ) Qualite dynamique de reservation de service dans un reseau de communications mobile
WO1999048310A1 (fr) * 1998-03-19 1999-09-23 Nokia Networks Oy Procede de controle de la qualite de service dans un systeme de communications mobile
WO2000013436A2 (fr) * 1998-08-28 2000-03-09 Nokia Oy Procede et systeme pour prendre en charge la qualite du service dans des reseaux sans fil
EP1154664A1 (fr) * 2000-05-09 2001-11-14 Lucent Technologies Inc. Réservation de ressources dans un réseau de télécommunication de troisième ou future generation

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005032066A1 (fr) * 2003-09-30 2005-04-07 Nokia Corporation Procede d'ordonnancement de paquets de donnees provenant de differents trains transmis par un terminal sans fil
FR2860679A1 (fr) * 2003-10-03 2005-04-08 Nec Technologies Uk Ltd Procede de selection d'un service support dans un reseau de telecommunication cellulaire
CN104618968A (zh) * 2004-04-08 2015-05-13 核心无线许可有限公司 在具有双重传送模式的移动无线系统中控制传输资源
WO2006092645A1 (fr) * 2005-03-03 2006-09-08 Telefonaktiebolaget Lm Ericsson (Publ) Reseau multiservice a protocole internet (ip) et procede d'etablissement de reservations de ressources pour trafic prioritaire
GB2437232A (en) * 2005-03-03 2007-10-17 Ericsson Telefon Ab L M IP multiservice network and method for making resource reservations for priority traffic
GB2437232B (en) * 2005-03-03 2008-08-20 Ericsson Telefon Ab L M IP multiservice network and method for making resource reservations for priority traffic
US8279887B2 (en) 2005-11-09 2012-10-02 Telefonaktiebolaget Lm Ericsson (Publ) Selection of radio resources in a radio communications network
CN102934403A (zh) * 2010-06-18 2013-02-13 斯凯普公司 控制网络上的数据传输
US9264377B2 (en) 2010-06-18 2016-02-16 Skype Controlling data transmission over a network
CN103404096A (zh) * 2011-01-27 2013-11-20 高通股份有限公司 用户设备发起的和网络发起的服务质量流的共存

Also Published As

Publication number Publication date
GB2386282A (en) 2003-09-10
AU2003209476A1 (en) 2003-09-16
GB0205105D0 (en) 2002-04-17

Similar Documents

Publication Publication Date Title
US10785784B2 (en) Method and devices for specifying the quality of service in a transmission of data packets
EP1250787B1 (fr) Traitement de rsvp dans les reseaux 3g
EP2109266B1 (fr) Méthode et dispositifs pour installer des filtres de paquets dans une transmission de données
EP1120939B1 (fr) Méthode, serveur et arrangement dans un réseau de transmission
JP5258989B2 (ja) モバイルｉｐ通信システムにおける異なる技術のアクセスネットワーク間でのモバイルノードのハンドオーバ
US20080273520A1 (en) NETWORK ARCHITECTURE FOR DYNAMICALLY SETTING END-TO-END QUALITY OF SERVICE (QoS) IN A BROADBAND WIRELESS COMMUNICATION SYSTEM
WO2003075523A1 (fr) Gestion de qualite de service dans des reseaux de paquets de donnees
JP2004532545A (ja) データネットワークにおけるルータ間のクラス毎の資源のポリシに基づく同期。
JP2004530340A (ja) データネットワークにおけるエッジに基づくフローごとのＱｏＳ許可制御
CN100546277C (zh) 在无线网络中通过信令通知以优化速率控制方案的方法和通信系统
US20060165126A1 (en) Bit rate controlling means in a telecommunication system
US7944833B2 (en) End-to-end QoS interoperation apparatus and method in heterogeneous network environment
WO2003075522A1 (fr) Gestion de flux d'ecoulement regroupes entre un gestionnaire de qualite de service et une application
WO2003075521A1 (fr) Reseau de communication de paquets de donnees
KR20050063416A (ko) 이동 단말기로의 다중 세션 지원 방법
Montes et al. Multimedia Streaming Service Framework for Q0S Management in 3G Networks.
WO2006123897A1 (fr) Appareil et procede d'interfonctionnement de qos de bout en bout dans un environnement de reseau heterogene

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP