1 / 39

ITU-T Standards Update

ITU-T Standards Update. By Istvan Sebestyen, Siemens Istvan.Sebestyen@icn.siemens.de. Standards are important!. Whether it's “weissbier”, Munich "helles" or "pils", all Bavarian beers have one thing in common: the unsurpassed product quality.

sabin
Download Presentation

ITU-T Standards Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ITU-T Standards Update By Istvan Sebestyen, Siemens Istvan.Sebestyen@icn.siemens.de

  2. Standards are important! Whether it's “weissbier”, Munich "helles" or "pils", all Bavarian beers have one thing in common: the unsurpassed product quality. Our brewers guarantee that all Bavarian beers are brewed strictly in accordance with the Bavarian purity regulations of 1516. Only carefully selected quality malt, best aroma hops from the Hallertau and the finest yeast - our own cultures - are used. Our quite particular secret is the soft brewing water from our own 240 m (780 feet) deep well, which provides the purest glacier water, filtered 10,000 years ago in the strata of the earth and completely untouched by modern environmental influences. Its clear purity is particularly well suited for brewing our Munich beer specialities.

  3. Status on what areas? Not a comprehensive overview, only on selected topics and areas... • ITU-T SG16 WP 2 (Multimedia Systems - H.323) • ITU-T SG16 WP 3 (Multimedia Codec - Audio, Speech Codecs)

  4. Speech/Audio Codec - Status

  5. Status of relevant speech/audio coder standards • Wideband (7 kHz) “Clean Speech” Codec standardization (AMR-Wideband in GSM/EDGE/multislot/3G (UMTS) for mobile communication and ITU-T Q20/16 Wideband standardization) - scalable (typically:16 kbit/s) clean speech codec. AMR-WB is an extension to the AMR codec and is expected to provide several bit-rates in the range of around 12-32kb/s. Selection: 2000; Finalization: 2000-2001(?); Cooperation with ITU-T is planned. ITU-T “should” take over the results. • Wideband (7kHz) “Conferencing/Music” Codec activity (ITU-T Q20/16) : G.722.1 was approved in 9/99. Excellent low-complexity speech/music coder (24-32 kbit/s), especially for conferencing applications. Floating point of G.722.1 has been determined. New variant proposed: 16 kbit/s music only: Target: 2001-2002. G.722.1 is the successor of G.722.

  6. Status of relevant speech/audio codec standards • G.711 (PCM 3 kHz speech) is still alive!!!! (until 2010??) Mandatory in ISDN, H.323. Bandwidth is less and less an issue. Simple, no basic IPRs. Trend: to have a base variant for VoiP applications: DTX scheme is needed for using G.711 in VoIP which is an issue in ITU-T SG16 WP3, including comfort noise aspects, error concealment. • ITU-T 4kbit/s speech: It is still delayed. Importance? Currently three consortia are going into the selection phase (July 2000). Approval: 2001.

  7. ITU-T H.323 protocol suite update • H.323 V3 Approved („Decided“) • H.323 V4 prepared for Approval in Fall 2000 („Determined“) • H.323 V5 also in the „pipeline“

  8. ITU-T H.323 - General comments • H.323 is member of the ITU-T H.3xx (2nd generation MM Platform) – classical telecom approach • works on any transport network (unlike SIP), supports interoperability, migration concepts • Intelligent in endpoints (peer-to-peer) (like SIP, unlike MEGACO/H.248) • Backwards compatible (unlike SIP) • Multimedia, that supports also simple monomedia (Voip) profiles (unlike SIP) • First standard approved: 1996 • Since then continuous development, it will not end soon…., • No long term planning (no roadmaps), ad-hoc, very (too?)fast • Huge IP Telephony and IP MM Architecture and System • Not a single terminal standard, but full “packet based real-time communication” • Consequently: very powerful, and obviously complex

  9. Scope of H.323 H.323Terminal H.323MCU Packet Based Network (Note) H.323Gatekeeper H.323Gateway H.323Terminal H.323Terminal GuaranteedQOSLAN B-ISDN GSTN N-ISDN H.310 terminaloperating in H.321 mode V.70Terminal H.324Terminal SpeechTerminal H.322Terminal SpeechTerminal H.320Terminal H.321Terminal H.321Terminal Note: A gateway may support one or more of the GSTN,N-ISDN and/or B-ISDN connections. Source: H.323 Spec ITU-T H.323 Architecture

  10. Overview components of the H.323 standard suite • H.323 – „System“ • H.225.0 – Call signalling protocols and media stream packetization (functionality also in SIP) • H.245 – Control protocol for multimedia communication (functionality also in SIP) • H.246 – Interworking • H.248 – Megaco „Gateway Decomposition“, „Stimulus Terminals“ • H.450 – Supplementary Services • H.235 – Security • H.241 – Network Management (MIB) • G.7xx + H.26x + T.xx + „Non ITU“ = Media Codecs (Video, Audio, Speech, Still Picture, Facsimile, Conferencing, Text-Phone, File Transfer....)(IPR = Too many.....)

  11. Approved ITU-T H.323 Version 3 goes with: • H.225.0 v.3 • H.245 v.5

  12. Parts of H.323 (approved Version 3) • H.323 V.3 Main body • Annex A - H.245 messages used by H.323 endpoints • Annex B - Procedures for layered video codecs • Annex C - H.323 on ATM • Annex D - Real-time facsimile over H.323 systems • Annex E – Multiplexed Call Signaling Transport • Annex F - Audio Simple Endpoint Type (SET) • Annex G- Text SET • Appendix I - Sample MC to Terminal Communication Mode Command • Appendix II – Transport level resource reservation procedures • Appendix III – Gatekeeper based user location

  13. Parts of H.323 (Version 4) • H.323 V.4 Main body (Det. 02/00) • Draft Annex D (V.2) : Real-time facsimile • Draft Annex J - Security for Annex F (SETs) • Draft Annex K - HTTP Based Service Control Transport Channel • Draft Annex L - Stimulus Protocol • Draft Annex M.1 - Tunnelling of signalling protocols (QSIG) • Draft Annex M.2 - Tunneling of signalling protocols (ISUP)

  14. Parts of H.323 (Version 5) • H.323 V.5 Main body (Det. later) • Annex H - User, Terminal and Service Mobility • Annex I - Lower Layer End-to-End QoS (Mobile) • Annex N - End to End QoS Control and Signalling in H.323 systems

  15. Parts of ITU-T H.225.0 (Version 3) • Recommendation H.225.0 (02/98) - Call signaling protocols and media stream packetization for packet-based multimedia communication systems (Main body) • Annex A - RTP/RTCP • Annex B - RTP Profile (incl. Payload Types) • Annex C - RTP payload format for H.261 video streams • Annex D - RTP payload format for H.261A video streams • Annex E - Video packetization • Annex F - Audio packetization - G.723.1, G.729, G.728, ... • Annex G - Gatekeeper-to-gatekeeper communication • Annex H - H.225.0 Message Syntax (ASN.1) • Annex I: H.263+ video packetization

  16. Parts of ITU-T H.225.0 cont. • Recommendation H.225.0 (02/98) - Call signalling protocols and media stream packetization for packet-based multimedia communication systems cont. • Appendix I - RTP/RTCP algorithms • Appendix II - RTP profile • Appendix III - H.261 packetization • Appendix IV - H.225.0 operation on different packet-based network protocol stacks

  17. ITU-T H.246 • ITU-T H.246: Interworking of H-Series multimedia terminals with H-Series multimedia terminals and voice/voiceband terminals on GSTN and ISDN. • Annex A - H.323-H.320 interworking • Annex B - H.324-H.320 interworking (never finished) • Annex C - (02/00) ISDN User Part Function - H.225.0 Interworking • Draft Annex D - Gatekeeper to TCAP interworking (SG11) • Draft Annex E - Interworking Function (IWF) between H.323 Gatekeepers and PLMN networks (Det. 2/00)

  18. ITU-T H.235 (Version 1) • ITU-T H.235: Security and encryption for H-Series (H.323 and other H.245-based) multimedia terminals • Annex A - H.235 ASN.1 • Annex B - H.323 specific topics • Annex C - H.324 specific topics • Appendix I - H.323 implementation details • Appendix II - H.324 implementation details • Appendix III - Other H-series implementation details • Appendix IV - Bibliography • Draft ITU-T H.235 V.2 (Det. 02/00) • Annex D - "Signature Profile"

  19. ITU-T H.245 (Version 5 - Approved 02/2000) • ITU-T H.245: Control protocol for multimedia communication • Annex A - Messages: Syntax • Annex B - Messages: Semantic definitions • Annex C - Procedures • Annex D - Object identifier assignments • Appendix I - Overview of ASN.1 syntax • Appendix II - Examples of H.245 procedures • Appendix III - Summary of procedure timers and counters • Appendix IV - H.245 Extension Procedure • Appendix V - The replacementFor Procedure • Appendix VI - Examples of H.263 Capability Structure Settings

  20. ITU-T H.323 Annex GText (SET)

  21. 2000/02 Decision H.323 Annex G “Text Conversation and Text SET” • Based on ITU T.140 Recommendation • Based on ISO10646-1 character suitable to any language • H.245 OpenLogicalChannel is used to open data channel • Unreliable RTP channel should be used (RFC ##) • “Text SET” specifies a device for real time conversations in voice and text simultaneously

  22. ITU-T H.248 / MEGACO • Media Gateway Control Protocol • Initial triggering: MGCP of CISCO • Joint IETF/ITU development – to be finished in the ITU mid 2000. • Originally to allow „scalability“ in Media Gateways, i.e. to connect gateway components of different suppliers in a standardized way • and now trends for „IP backboning“ • Side-effect“: Likely also to go to terminals?An internet draft, and Draft H.248 Annex G exists: The approach to achieve this goal is to provide a very simple and direct master/slave control model in which very little feature intelligence is required in the end device. This design intent matches the Megaco/H.248 Protocol approach well.

  23. ITU-T H.248 / MEGACO Architecture Media Gateway Controller SCN signaling (ISUP) IP-based signaling (H.323, SIP) H.248 SCN IPnetwork Media Gateway Termination Termination SCN bearer channel RTP stream

  24. MEGACO - IP phone • draft-ietf-megaco-ipphone-02.txt • combines a terminal and a small MG in one appliance • enables “simple” terminals, requires powerful MGCs Media Gateway Controller IP-based signaling (H.323, SIP) Signaling (SS7, H.323, SIP, ...) Unnecessary !!! H.248 Media Gateway Terminal RTP stream Termination Termination RTP stream

  25. H.248 in gateways andterminals IP-based networks H.323 Non-StimulusTerminals ISDN SIP H.248 Circuit Switched Networks GSTN H.248 Gateway Stimulus Terminals

  26. Status of ITU-T H.248/ MEGACO • “Re-determination” of ITU-T H.248, Geneva, February 2000 • ITU-T “Decision” (approval) in June,15, 2000, • IETF publishes new standards track RFC by July 2000 • H.248 packages for „user interface elements and action packages“ have been defined (H.248 Annex G) for stimulus feature control for full stimulus H.248/megaco IP phones but also for H.323 endpoints using the add-on stimulus protocol (H.323 Annex L). • IPRs ? • H.248 products announced for end 2000

  27. ITU-T H.248 • ITU-T H.248 (Det. 02/00) Gateway Control Protocol • Annex A - The protocol syntax for the binary format of the protocol • Annex B - A complete ABNF of the text encoding of the protocol per RFC2234 • Annex C - specifies the encoding of the Local and Remote descriptors for use with the binary format • Annex D - Transport over IP • Annex E - Basic packages • Annex F - FAX/Textphone/Modem Tones Detection Package • Annex G - User Interface Elements and Action Packages • Annex H - Transport over SCTP • Annex I - Transport over ATM • Annex J - Dynamic Tone Definition Package • Annex K - Generic Announcement Package

  28. 2000/02 DeterminationH.323 Annex L “Stimulus signaling” • H.323 Annex L “Stimulus signaling” addresses the second approach among possible three listed below: • (1) A completely stateless H.248 single line gateway • (2) A call-stateful, feature-stateless H.323 Annex L device (uses H.323 encapsulated H.248 protocol elements) • (3) A call-stateful, feature-stateful H.323 + H.450 device

  29. Annex L in conjunction with GK routed signalling model

  30. 2000/02 DeterminationH.323 Annex K “HTTP based Service Control” • Another way to achieve “Stimulus signaling” • describes an optional way of controlling supplementary services in an H.323 environment • A separate HTTP connection for independent control protocol conveying a service independent control protocol. New services may be developed and deployed without updates to the H.323 endpoints. • Feasible for endpoint capable of running WEB browser • Call related and non-call related services are possible

  31. H.323 System overview for HTTP based service control Service Client Web-browser HTTP server HTTP Service H.323 H.323 endpoint H.323 entity Call

  32. 2000/02 DeterminationAnnex M • H.323 Annex M “General infrastructure for tunneling signaling protocols in H.323 will become an integral part of H.323/H.225v4 • H.323 Annex M.1 “QSIG Tunneling Procedures” • H.323 Annex M.2 “ISUP Tunneling Procedures” • Negotiation means for tunneled protocol are considered towards H.323/H.225.0v4

  33. H.323 Mobility Work Scope • Scope of H.246 Annex E • To connect H.323 Users with existing Mobile Networks • Scope of H.323 Annex H • Provide recommendations for User, Terminal and Service mobility in H.323 systems • To enable Inter-working with mobile and fixed networks • Scope of H.323 Annex I • H.323 Annex I: work so far has concentrated on issues with respect to QoS • H.323 Annex I does not specify any protocols, but concentrates on issues that may effect H.323 interactions with lower layers.

  34. H.323 Mobility Scope, cont..

  35. 2000/02 DeterminationH.323 Annex H “User and Service Mobility” • Also Terms of Reference have been prepared • TOR paper identifies • Home Location Function (HLF) • Visitor Location Function (VLF) • Authentication Functions (AuF) • Inter-working Function (IWF)

  36. Architecture for H.323 Mobility

  37. H.323 Mobility - Roadmap • H.246 Annex E • Basic Voice, Voice Mail and SMS services - Feb., 2000 determination • H.323 Annex H • User Mobility, Service Mobility Services - Feb., 2000 determination • Terminal Hand-over - For further Study • H.323 Annex I • Lower layer QoS - Nov., 2000 determination

  38. Thanks ..... Questions?

More Related