A.2 Example figures
23.1073GPPQuality of Service (QoS) concept and architectureRelease 17TS
The following values are indicative of the QoS attributes required by audio and video media streams, including bit error rates (BER) and frame erasure rates (FER).
For the purposes of example, figures are provided for the AMR speech codec and the MPEG-4 video codec.
AMR speech codec payload
Bit rate: 4,75 – 12,2 kbit/s
Delay: end-to-end delay not to exceed 100ms (codec frame length is 20ms)
BER: 10-4 for Class 1 bits
10-3 for Class 2 bits
for some applications, a higher BER class (~10-2) might be feasible.
FER < 0,5% (with graceful degradation for higher erasure rates)
MPEG-4 video payload:
Bit rate: variable, average rate scalable from 24 to 128 kbit/s and higher
Delay: end-to-end delay between 150 and 400ms
video codec delay is typically less than 200 ms
BER: 10-6 – no visible degradation
10-5 – little visible degradation
10-4 – some visible artefacts
> 10-3 – limited practical application
Packet loss rate FFS
Data and control:
Data (data refers to other types than audio and video e.g. file transfers, shared whiteboard) and control information shall be transmitted reliably (i.e. residual bit errors should result in a lost packet).
Annex B (normative):
Reference Algorithm for Conformance Definition of Bitrate
The annex shows a reference algorithm for the conformance definition of bitrate. This may be used for traffic contract between UMTS bearers and external network/user equipment. It should be noted that the reference algorithm will never imply a particular implementation for the traffic conditioner.
The algorithm is well known as "Token Bucket Algorithm" which has been described in IETF. Here, "tokens" represents the allowed data volume, for example in byte. "Tokens" are given at a constant "token rate" by a traffic contract, are stored temporarily in a "token bucket", and are consumed by accepting the packet. This algorithm uses the following two parameters (r and b) for the traffic contract and one variable (TBC) for the internal usage.
– r: token rate, (corresponds to the monitored Maximum bitrate/Guaranteed bitrate).
– b: bucket size, (the upper bound of TBC, corresponds to bounded burst size).
– TBC(Token bucket counter): the number of given/remained tokens at any time.
In words, conformance according to a token bucket can be defined as: "Data is conformant if the amount of data submitted during any arbitrarily chosen time period T does not exceed (b+rT)".
The algorithm is described in the following.
Token bucket counter (TBC) is usually increased by "r" in each small time unit. However, TBC has upper bound "b" and the value of TBC shall never exceed "b".
When a packet #i with length Li arrives, the receiver checks the current TBC. If the TBC value is equal to or larger than Li, the packet arrival is judged compliant, i.e., the traffic is conformant. At this moment tokens corresponding to the packet length is consumed, and TBC value decreases by Li.
When a packet #j with length Lj arrives, if TBC is less than Lj, the packet arrival is non-compliant, i.e., the traffic is not conformant. In this case, the value of TBC is not updated.
Figure B.1: Operation example of the reference conformance algorithm
Annex C (normative):
Determine which QoS profile is of highest QoS
In handovers from Release 1999 to GPRS Release 97/98 networks, it will be necessary to determine which PDP context of a set of PDP contexts provides the highest QoS, since, of a set of PDP contexts with the same APN and PDP address, all PDP contexts except the one with the highest QoS profile will be deactivated.
To determine which PDP context that has the highest QoS table C.1 is used. Only the PDP context(s) with the highest QoS ranking will be maintained and the rest will be deactivated. In a second step, if more than one PDP context remain, the PDP context with the highest value for the maximum bitrate attributes for downlink or uplink is selected. All PDP contexts except the PDP context(s) with the highest Maximum bitrate selected will be deactivated.
If more than one PDP context remain after the second step, all PDP contexts except that with the lowest NSAPI are deactivated.
Table C.1
|
QoS ranking |
Traffic class |
Traffic handling priority |
|
1 |
Interactive |
1 |
|
2 |
conversational |
Not applicable |
|
3 |
streaming |
Not applicable |
|
4 |
Interactive |
2 |
|
5 |
Interactive |
3 |
|
6 |
Background |
Not applicable |
Annex D (normative):
Determine Traffic Class weights in HLR QoS profile
The QoS profile in the subscription record represents the maximum QoS per PDP context to the associated APN. Subsequently, it shall be possible to negotiate all QoS parameters, including an appropriate Traffic Class for each QoS flow. This is valid for the first PDP context that is established as well as subsequent PDP contexts, i.e. this includes primary and secondary PDP contexts activations. The traffic classes have increasing weight according to the order background, interactive, streaming and conversational.
Annex E (informative):
Change History
|
Change history |
||||||||
|---|---|---|---|---|---|---|---|---|
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Cat |
Subject/Comment |
Old |
New |
|
12/2003 |
SP-22 |
SP-030654 |
0145 |
– |
F |
Radio Access Bearer Service Attributes for GERAN |
5.10.0 |
6.0.0 |
|
03/2004 |
SP-23 |
SP-040033 |
0149 |
2 |
A |
Correction to the use of delivery order set to yes |
6.0.0 |
6.1.0 |
|
03/2004 |
SP-23 |
SP-040033 |
0150 |
2 |
F |
ARP Clarification |
6.0.0 |
6.1.0 |
|
03/2004 |
SP-23 |
SP-040033 |
0151 |
1 |
F |
Removal of reliability class 1 |
6.0.0 |
6.1.0 |
|
12/2004 |
SP-26 |
SP-040912 |
0153 |
3 |
A |
Clarification on delivery order set to no |
6.1.0 |
6.2.0 |
|
06/2005 |
SP-28 |
SP-050334 |
0154 |
2 |
F |
RAB Allocation/Retention Priority |
6.2.0 |
6.3.0 |
|
06/2005 |
SP-28 |
SP-050334 |
0156 |
1 |
F |
Addition of GERAN to the scope clause |
6.2.0 |
6.3.0 |
|
03/2006 |
SP-31 |
SP-060138 |
0159 |
– |
F |
Peak throughput class reference |
6.3.0 |
6.4.0 |
|
06/2007 |
SP-36 |
– |
– |
– |
– |
Update to Rel-7 version (MCC) |
6.4.0 |
7.0.0 |
|
09/2007 |
SP-37 |
SP-070539 |
0164 |
1 |
F |
Support of higher maximum bitrate and guaranteed bit rate |
7.0.0 |
7.1.0 |
|
12/2008 |
SP-42 |
– |
– |
– |
– |
Update to Rel-8 version (MCC) |
7.1.0 |
8.0.0 |
|
12/2009 |
SP-46 |
– |
– |
– |
– |
Update to Rel-9 version (MCC) |
8.0.0 |
9.0.0 |
|
06/2010 |
SP-48 |
SP-100327 |
0165 |
3 |
F |
Addition of new QoS parameters evolved ARP and APN-AMBR |
9.0.0 |
9.1.0 |
|
2011-03 |
SP-51 |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
9.1.0 |
10.0.0 |
|
2011-06 |
SP-52 |
SP-110322 |
0168 |
1 |
A |
Clarification of SRVCC usage of QoS |
10.0.0 |
10.1.0 |
|
2011-12 |
SP-54 |
SP-110729 |
0171 |
1 |
A |
QoS mapping |
10.1.0 |
10.2.0 |
|
2012-06 |
SP-56 |
SP-120250 |
0172 |
2 |
F |
MBR and GBR values to support 8C-HSDPA |
10.2.0 |
11.0.0 |
|
2014-09 |
SP-65 |
– |
– |
– |
– |
Update to Rel-12 version (MCC) |
11.0.0 |
12.0.0 |
|
2015-12 |
– |
– |
– |
– |
– |
Update to Rel-13 version (MCC) |
12.0.0 |
13.0.0 |
|
2017-03 |
– |
– |
– |
– |
– |
Update to Rel-14 version (MCC) |
13.0.0 |
14.0.0 |
|
2018-06 |
SP-80 |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
14.0.0 |
15.0.0 |
|
2020-07 |
SP-88E |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
15.0.0 |
16.0.0 |
|
2022-03 |
SP-95E |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
16.0.0 |
17.0.0 |