(Continuation of Question 17/13 studied during 1997-2000)

Background and justification

Call processing performance parameters, objectives, and allocation methods are needed to support efficient design of digital networks and to provide guidance to developers of related systems and applications. Implementation of B-ISDN and related IP applications will require performance specifications for advanced call processing features.

Items for study

IP-based networks

1. What performance parameters should be used to characterize the performance of call processing of IP telephony in Recommendation I.38IPCP, including advanced features such as the establishment of multipoint connections and multiconnection calls, the adding and dropping of parties, and the negotiation of call attributes in established calls?

2. Are call processing parameters of IP telephony required to characterize network performance in support of IP and multimedia applications?

3. How should the definitions for call processing parameters of IP telephony be related to protocol-defined UNI timers?

4. What values should be recommended for call processing parameters of IP telephony?

5. What traffic conditions and hypothetical reference connections should be used in specifying such values?

6. How do those values change based on the type, amount, and quality of network resources being requested?

7. How should the call processing work take into account consideration of ‘emergency services’?

B-ISDN

8. What performance parameters should be used to characterize the performance of B-ISDN call processing in Recommendation I.358, including advanced features such as the establishment of multipoint connections and multiconnection calls, the adding and dropping of parties, and the negotiation of call attributes in established calls?

9. Are special B-ISDN call processing parameters required to characterize network performance in support of IP and multimedia applications?

10. How should the definitions for B-ISDN call processing parameters be related to protocol-defined UNI timers?

11. What values should be recommended for B-ISDN call processing parameters?

12. What traffic conditions and hypothetical reference connections should be used in specifying such values?

13. How do those values change based on the type, amount, and quality of network resources being requested?

14. How should the defined B-ISDN call processing parameters be measured?

15. What are the connection control performance parameters/requirements in Bearer Independent Connection Control architectures (e.g., MPLS, ATM or IP used as a bearer)?

16. What is the dependency between call and connection control performance?

N-ISDN

17. Should the connection processing delay objectives specified in Recommendation I.352 and I.354 be modified on the basis of operational experience and emerging requirements?

18. What connection processing accuracy and dependability parameters and objectives should be specified in Recommendation I.359?

Specific tasks with deadlines

• New Recommendations I.38ipcp by 2001
• Revised Recommendations I.358 by 2002
• Revised Recommendations I.359 by 2002
• Revised Recommendations I.352 by 2003
• Revised Recommendations I.354 by 2003

Relationships

• ITU-T Study Groups on services and network operations
• ITU-T Study Groups on public data networks
• ITU-T Study Groups on switching and signalling
• ITU-T Study Groups on multimedia services