ly inter- active real-time transaction service, such as user-to-user signaling and highly interactive transaction service, will require less than 50 ms of end-to-end delay. Highly interactive real-time constant bit rate (CBR) conversation service, such as VoIP, will require end-to-end delay of 100 ms and jitter of 50 ms [18], and can be supported by expedited forwarding (EF) class-type in DiffServ standard. Highly interactive real-time variable bit rate (VBR) conversation service, such as multimedia phone, will require the same QoS parameters, but may be pro- vided by assured forwarding (AF) a class-type that efficiently handles the VBR characteristics. Multimedia conference will require extended end-to-end delay of 400 ms, and jitter of 50 ms [18]. Interactive transaction data, such as a telnet session, will require end-to-end delay of 400 ms without jitter constraints, while Web C 2009 by Taylor & Francis Group, LLC Q-SIP/SDP for Converged Heterogeneous Wired and Wireless Networks 367 search or bulk data transfer will require much looser time constraints, such as more than one sec of end-to-end delay. Finally, the best effort service is a class type for legacy Internet service that does not guarantee time constraints or traffic parameters. As explained above, each class-type requires different QoS requirements; some service classes requires tight end-to-end delay of 100 or 400 ms and lim- ited jitter, while the other non-real-time service classes do not require tight end-to-end delay. The different service class-types will require different fault restoration capabilities; highly interactive real-time transaction or conversa- tional services will require fast restoration with 1+1, 1:1 or M:N backup path, while non-real-time services will require less strict fault restoration with 1:N or sometimes may allow no restoration. In order to simplify the required functions of connection establishment for QoS-guaranteed DiffServ provisioning, traffic grooming in the transit networks should be supported. Configuration of 