A.2.1 Scenario 1

23.2073GPPEnd-to-end Quality of Service (QoS) concept and architectureRelease 17TS

The UE does not provide an IP BS Manager. The end-to-end IP QoS bearer service towards the remote terminal is controlled from the GGSN.

The scenario assumes that the GGSN supports DiffServ edge functions, and the backbone IP network is DiffServ enabled.

NOTE: The UE may always include an authorisation token in establishment of the PDP context. Inclusion of the authorisation token in scenario 1 changes the QoS mechanisms to be the same as those described in scenario 5. Therefore, please refer to scenario 5 if the authorisation token is included.

The application layer (e.g. SIP/SDP) between the end hosts identifies the QoS requirements. The QoS requirements determined from the application layer (e.g. TS 23.228 [4] describes interworking from SIP/SDP to QoS requirements) are mapped down to PDP context parameters in the UE.

In this scenario, the control of the QoS over the UMTS access network (from the UE to the GGSN) may be performed either from the terminal using the PDP context signalling, or from the SGSN by subscription data.

The IP QoS for the downlink direction is controlled by the remote terminal up to the GGSN. The GGSN will apply receiver control DiffServ edge functions and can reclassify the data (remarking the DiffServ Code Point (DSCP)). This may affect the QoS applied to the data over the UMTS access (the TFT may use the DSCP to identify the data to be allocated to the PDP context).

The end-to-end QoS is provided by a local mechanism in the UE, the PDP context over the UMTS access network, DiffServ through the backbone IP network, and DiffServ in the remote access network in the scenario shown in the figure below. The GGSN provides the interworking between the PDP context and the DiffServ function. However, the interworking may use information about the PDP context which is established, or be controlled from static profiles, or dynamically through other means such as proprietary HTTP based mechanisms. The UE is expected to be responsible for the control of the PDP context, but this may instead be controlled from the SGSN by subscription.

Figure A.2: Local UE does not provide IP BS Manager

Notes:

– The solid horizontal lines indicate the mechanism that is providing QoS for the flow of data in the direction indicated.

– The dashed horizontal lines indicate where QoS control information is passed that is not directly controlling the QoS in that link/domain.

– The arrows on the horizontal lines indicate nodes that receive information about QoS from that mechanism, even if that mechanism is not used to control the QoS over that link/domain.

– The solid vertical lines indicate interworking between the different mechanisms.

– In the figure, the term RAP refers to the Remote Access Point, and RUE is the Remote UE.

No solid vertical line is shown from DiffServ to PDP flow on the downlink at the GGSN. The TFT determines the QoS applicable over the UMTS access. However, the configuration of the TFT may use the DiffServ to select the PDP context to be applied, so there may be interworking between DiffServ and the PDP Flow via the TFT filters.