QoS issues in the converged 3G wireless and wired networks

End-to-End QoS Issues of MPEG4-FGS Video Streaming Traffic Delivery in an IP/UMTS Network

“…The appropriate mapping of UMTS traffic classes to the aforementioned DiffServ service classes could offer a vehicle for the end-to-end QoS provision over a heterogeneous DiffServ/UMTS network. In our work, we employ and evaluate the three different mapping approaches presented in [7]- [9] respectively.…”

Efficient Resource Allocation for Policy-Based Wireless/Wireline Interworking

“…The differentiated services (DiffServ) scheme [5] has been extensively accepted for both wireless and wireline domains as the network-layer QoS mechanism due to its scalability and convenience for SLA-based network management [11,24,26], we therefore discuss resource allocation in the DiffServ context.…”

“…Therefore, a proper service class mapping between neighboring domains is very important for maintaining a consistent level of end-to-end QoS. For example, the Universal Mobile Telecommunications System (UMTS) based on WCDMA technology defines four QoS classes, i.e., conversational, streaming, interactive, and background, for 3G wireless communications [24]. Conversational and streaming classes are intended for realtime multimedia traffic, and the other two classes for delay tolerant data traffic.…”

“…To extend IP services to the wireless domain, the UMTS QoS classes must be mapped into DiffServ classes. Normally, the conversational class can be mapped to the EF PHB for a very low delay and low loss service, the streaming and interactive traffic to the AF PHB, and the background traffic to the best-effort service [24]. The transit domain in the interworking architecture has a path-oriented environment, where per-class peringress/egress pair TRSLAs are negotiated at network boundaries [9].…”

“…The nominal capacity of SLA ðs; 'Þ is denoted as C s;' , and the bandwidth allocated to traffic trunk ðs; rÞ (determined by the network dimensioning) is denoted as C s;r , with C s;' ¼ P r2Rðs;'Þ C s;r . In the DiffServ context, the logical central entity responsible for the network resource management is termed as a bandwidth broker [24,28,31,32]. In practice, the bandwidth broker also adopts the policybased management framework, where the PEPs/PDPs are not separate components but are collocated with the resource management function blocks, e.g., SLA subscription, network dimensioning, and dynamic resource management, which composes the bandwidth broker [32].…”