Content for  TS 23.207  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   5…   6…   A…   A.2…   A.2.3   A.2.4…   C   D…   D.2…


A  QoS Conceptual Modelsp. 19

A.1  Introductionp. 19

There are many different end-to-end scenarios that may occur from a UE connected to a UTMS network. The following examples depict how end-to-end QoS will be delivered for a number of scenarios that are considered to be significant.
In all the scenarios presented below, the network architecture is as shown in Figure A.1 below.
Copy of original 3GPP image for 3GPP TS 23.207, Fig. A.1: Network Architecture for QoS Conceptual Models
  • Although the backbone IP network is shown as a single domain, it may consist of a number of separate domains.
  • The structure of the Local UE is not specified. It includes cases from a simple host, to a gateway to a network such as a LAN. If the UE is acting as a gateway, it is responsible for providing the IP BS Management towards the extended network.
  • The remote side is shown as a simple host. Other more complex cases on the remote side such as a private LAN with over-provisioning, or possibly LAN priority marking, and DiffServ and/or RSVP capable routing elements is not depicted. It is envisaged however that interworking between the QoS mechanisms in a more complex remote user side could also be performed with some similarities to the mechanisms shown at the local side.
The reference point shown at the UE is at the interface to the UE. Within the UE, the QoS control could be derived from any of the mechanisms that occur across that reference point, or it could use a different mechanism internally.
Although the scenarios currently identified are mainly using DiffServ in the backbone IP network (RSVP is indicated as an alternative in scenario 4), it is not mandated that DiffServ must be used in the backbone IP network. Other mechanisms, for example, over-provisioning and aggregated RSVP may be used.

Up   Top   ToC