1 / 51

Designing Triple-Play Apps Using DSP Resource Boards

Learn about the latest trends in voice and video markets, the needs of operators, and optimal hardware and software architectures for designing triple play applications using DSP resource boards.

barid
Download Presentation

Designing Triple-Play Apps Using DSP Resource Boards

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. Designing Triple-Play Apps Using DSP Resource Boards Amir Zmora VP Marketing & Product Management Surf Communication Solutions

  2. Agenda • Voice and Video Market Trends • Operators Needs • Triple-Play in Action • Optimal Hardware System Architecture • Optimal Software System Architecture • Summary

  3. Voice and Video Market Trends

  4. Triple-Play Overview • Currently different systems are used for each media type • Telephone for voice (VoIP or PSTN) • Video system for video calls • Data collaboration applications for data sharing • In Triple-Play all 3 media types are combined • Right-click on an e-mail to open a session (voice/video) with sender • Seamlessly switch between voice-only and voice + video • Share desktop and applications in same session • TVoIP/TVoDSL, VoD, PVR, DVR  a single CPE box that will handle all communication applications

  5. The Drivers of Video Deployment • Technology improvements • Better video codecs – H.263, MPEG4, H.264 • Cheaper components – LCD screens, memory • Processors are cheaper, better and require less power • Longer battery life for handheld devices • Different networks that can now be converged • Cellular – 3G (3G-324M) • Wireless – WiFi & WiMAX (SIP) • Wireline IP (SIP & H.323) • Wireline PSTN (H.324)

  6. Cellular – 3G Services • 3G is now in mass deployment • 156 commercial 3G operators in 70 countries • 187M subscribers (CDMA & WCDMA) • Source www.3gtoday.com July 2005 • Video streaming • V-Live of NTT DoCoMo – Real-Time TV • Video on demand • Home/Business/Homeland security – Video surveillance • Messaging & Presence • IM, MMS, Video mail, PoC • Presence – Online/offline plus available for service X with person Y

  7. Cellular – 3G Services • Conversational Multimedia • Video Telephony • PoC – Half-duplex communication (Push-to-Talk, Show, View) • Online multi-participant games • Combine with Video to other parties • Combine with PoC

  8. Wireless IP - WiFi & WiMAX • WiFi (and WiMAX, in the future) will be integrated into mobile devices • A mobile device will roam seamlessly between networks • In the office – Use WiFi as a terminal in office PBX • In the city – Use WiMAX if available for higher bandwidth at lower price • On the go – Use 3G cellular network • Hence all services in cellular network will need to be available also in Wireless

  9. Wireline IP • Video is mainly used today in room systems with H.323 or ISDN BUT… • Video is getting into the home and on the desktop • MSN Messenger • Many SIP Video clients • STB (Set-top Boxes) with Video clients • Both Siemens and Samsung showed this direction at Supercomm 2004 • D-Link i2eye has this product for more than a year - http://www.dlink.com/products/?pid=293 • Leadtek has IP, ISDN & PSTN Video phones http://www.leadtek.com/videophone.html

  10. Wireline PSTN • PSTN Video phones using H.324 have existed for years • They had low Video quality • They were expensive • With the technology improvements these 2 issues have been solved • Amstrad announced in September availability of its PSTN E3 Video Phone • Service experiencing rapid deployment in Italy (HiTel and other phones)

  11. Voice and Video Market Trends • Current deployment of Video is mainly in the Enterprise & 3G Mobile segments • Deployment of Video over broadband and PSTN is ramping up • Deployment facts • NTT DoCoMo: Over 12.8M subscribers (May 2005) • Hutchison 3G: Over 8M subscribers (March 2005) • Skype to add Video (announced Oct 2004) • Vonage to add Video (announced Dec 2004) • 8x8 already provides Video (since June 2004) • VoicePulse to add Video (planned for H2/2005) • Video over PSTN in Italy, UK and other countries

  12. Operators Needs

  13. Operators Needs • Connectivity between the different networks • Cross-networks services • Voice/Video mail • Video portal • Multimedia server • Recording • All applications must support packet-to-packet, TDM-to-packet, TDM-to-TDM

  14. Operators Needs cont’d • Since Video deployment demands are still relatively small compared to Voice deployment, flexible channel type assignment is required • Price, Price, Price! • Smooth and flexible migration from Voice systems to Voice and Video systems • Simple, synchronized, and balanced systems

  15. Megs of traffic 10s of Megs in back plane Gigs of traffic 10 Gig per AMC in back plane Not ready for new powerful DSPs Ready for new powerful DSPs DSP Farms:Moving from PTMC to AMC

  16. Applications Host PRI/ BRI CAS 3G-324M H.323 SIP Signaling TDM H.223/ H.221 IP/ UDP Transport DSPC64x Video Processing:Resolution Frame RateBit Rate ECAN Tones Detection/ Generation Video Encode/ Decode Voice Encode/ Decode Media Processing Fax RTP/RTCP Jitter -T.32/ T.38 -V.17/ V.34HD Modem -V.92/ V.34 Voice & Video Gateway

  17. Applications Host With Partners PRI/ BRI CAS 3G-324M H.323 SIP Signaling TDM H.223/ H.221 IP/ UDP Transport DSPC64x Video Processing:Resolution Frame RateBit Rate ECAN Tones Detection/ Generation Video Encode/ Decode Voice Encode/ Decode Media Processing Fax RTP/RTCP Jitter -T.32/ T.38 -V.17/ V.34HD Modem -V.92/ V.34 Voice & Video Gateway

  18. Triple-Play in Action

  19. H.324 Video Phone 3G-324M Video Phone Mobile PSTN IP SIP Video Phone Voice & Video Gateway Voice & Video GW Media processing board H.264 30 FPS 4CIF SIP Video Phone 1. Call starts from the SIP Video Phone

  20. H.324 Video Phone 3G-324M Video Phone Mobile PSTN IP SIP Video Phone Voice & Video Gateway Control Voice & Video GW Media processing board H.264 30 FPS 4CIF SIP Video Phone 2. GW application configures Media Gateway according to destination and codec properties

  21. H.324 Video Phone 3G-324M Video Phone Mobile PSTN IP SIP Video Phone Voice & Video Gateway Control MPEG4 10 FPS QCIF H.263 10 FPS CIF Voice & Video GW Media processing board H.264 30 FPS 4CIF SIP Video Phone 3. Media goes directly to Media Gateway avoiding Host-DSP bottleneck

  22. Voice/Video Gateway Application Requirements • Interfaces • Simultaneous interfaces required: IP-IP, TDM-IP, TDM-TDM • C64x has native interfaces to IP, TDM • Each DSP has an Ethernet I/F requiring aggregation to one IP address • High Density • Powerful DSP • Separate control and media path • Network aggregation is done using an IP switch • H.223 runs on DSP • Media Processing • H.263, H.264, MPEG4 • G.729, G.723, AMR… • All voice/video/fax/data media processing and stack performed on the DSP

  23. H.324 Video Phone 3G-324M Video Phone Mobile PSTN IP SIP Video Phone Voice & Video Mail – Record/Play H.263 10 FPS CIF Voice & Video GW Media processing board SIP Video Phone 1. SIP phone initiates a call to PSTN Video Phone. Call is routed to Voice/Video Mail.

  24. H.324 Video Phone 3G-324M Video Phone Mobile PSTN IP SIP Video Phone Voice & Video Mail – Record/Play Control H.263 10 FPS CIF Voice & Video GW Media processing board H.264 30 FPS 4CIF SIP Video Phone 2. Media is buffered in DSP external memory to avoid host interrupts in 10/20 ms interval, then stored on host.

  25. H.324 Video Phone 3G-324M Video Phone Mobile PSTN IP SIP Video Phone Voice & Video Mail – Record/Play Control MPEG4 10 FPS QCIF H.263 10 FPS CIF Voice & Video GW Media processing board H.264 30 FPS 4CIF SIP Video Phone 3. Voice/Video mail retrieved from mobile. Media is processed in DSP.

  26. Messaging Application Requirements • Interfaces • Disk Host DSP Network (Simultaneous IP/PSTN) • C64x has native interfaces to IP, TDM • Each DSP has an Ethernet I/F requiring aggregation to one IP address • Temporary Storage • Allows keeping commonly-used messages in memory (IVR) • Allows buffering to avoid host interrupts in 10/20ms intervals (voice block size) • High Density • Powerful DSP • Separate control and media path • Network aggregation is done using an IP switch • H.223 runs on DSP

  27. Messaging Application Requirements • Media Processing • H.263, H.264, MPEG4 • G.729, G.723, AMR… • All voice/video/fax/data media processing and stack performed on the DSP • Transport • Reliable Host-DSP over UDP (“TCP light”)

  28. H.324 Video Phone 3G-324M Video Phone Mobile PSTN IP SIP Video Phone Voice & Video Conferencing MPEG4 10 FPS QCIF H.263 10 FPS CIF Voice & Video GW Media processing board H.264 30 FPS 4CIF SIP Video Phone 1. Each party in the conference calls in. Different protocols and media properties are supported.

  29. H.324 Video Phone 3G-324M Video Phone Mobile PSTN IP SIP Video Phone Voice & Video Conferencing Control MPEG4 10 FPS QCIF H.263 10 FPS CIF Voice & Video GW Media processing board H.264 30 FPS 4CIF SIP Video Phone 2. DSP is configured to create a channel for each voice/video party.

  30. H.324 Video Phone 3G-324M Video Phone Mobile PSTN IP SIP Video Phone Voice & Video Conferencing Control MPEG4 10 FPS QCIF H.263 10 FPS CIF Voice & Video GW Media processing board H.264 30 FPS 4CIF SIP Video Phone 3. An output channel is created for each party that requires voice/video/H.223/RTP processing.

  31. Voice/Video Conferencing Application Requirements • Interfaces • Simultaneous interfaces required: IP-IP, TDM-IP, TDM-TDM • C64x has native interfaces to IP, TDM • Each DSP has an Ethernet I/F requiring aggregation to one IP address • High Density • Powerful DSP • Separate control and media path • Network aggregation is done using an IP switch • H.223 runs on DSP

  32. Voice/Video Conferencing Application Requirements • Media Processing • H.263, H.264, MPEG4 • G.729, G.723, AMR… • All voice/video/fax/data media processing and stack performed on the DSP • Voice/Video should be transmitted to each party according to its: • Voice codec properties • Video codec properties • Transport & interface – IP/TDM (H.223)

  33. Optimal Hardware System Architecture

  34. Definition of Terms • Hardware Framework • DSP • Routing device • Aggregation device • System controller • Software Framework • DSP algorithms • DSP framework • Diagnostics system • Expert analysis system

  35. DSP Requirements Prerequisites: • External SD-RAM • Packet interface • High enough performance to enable video processing • Wide range of reliable software vendors C6412, New C64xx

  36. Interface between DSP and Network Aggregation Unit • With a Host Port Interface (HPI, PCI…), all the DSPs are connected to the same bus. A slow retrieval from one DSP can cause delay in other DSPs (the butterfly effect). • Using an Ethernet interface, the DSPs have independent communication routes.

  37. Aggregator Interface between DSP and Network Aggregation Unit DSP1 DSP1 DSP2 DSP2 Aggregator DSP3 DSP3

  38. Interface between Host and DSP • A DSP with small memory needs to send/receive small chunks of data to/from the Host at a high rate. This inflicts severe stress on the Host and is particularly important for messaging solutions. • Use DSPs with large external memory. The external memory can be used as temporary storage, enabling the Host to send/receive larger chunks of data less frequently.

  39. Aggregation Unit Bottleneck: Payload and Control Handling • Network aggregation and control application compete for the same resources. • Separate control and media paths. For example: Use IP interconnections between DSPs, Host and Network.

  40. Optimal Software System Architecture

  41. Optimizing the Software Framework • Interoperability/Testing • Open Framework • Flexible APIs • Remote diagnostics

  42. Interoperability and Testing • Solution components must be field-hardened & interoperable (signaling interop is not enough) • Voice Codecs • Video Codecs • H.223/H.221 • T.38 • Echo Canceller • Modem • Critical components need constant support • Echo Canceller • Modem • Tools needed for diagnostics extraction from deployed systems

  43. What is an Open Framework? • A solution that enables manufacturers to add media processing algorithms to their platforms simply and quickly • A few basic APIs to “hook” the third party algorithm • Algorithm can be • Proprietary Voice/Video codecs • New transport protocols • Density, performance and cost should not be compromised in order to provide an open solution.

  44. Why Move to an Open Framework on Your DSP? • Be ready for the “killer application” • Support for new features • Allow multiple vendors to interface with your product technology • Differentiate your product • Reduce DSP maintenance and support fees from your software vendor

  45. Flexible APIs • Full control over ALL media type parameters • Pre-set defaults • Video example • User defined screen layout • Logo insertion • Background/Foreground manipulation • Multiple layer picture • Any resolution support • Cropping & resizing • Same stream can be encoded in different formats/bit rates/resolutions simultaneously

  46. Remote Diagnostics • 75% of cost of solving issues in the field is related to the extraction of diagnostics • Need to be able to extract all the necessary diagnostics • Diagnostics should be part of the release version • Diagnostics should be enabled/disabled on a per-service/per-DSP/per-port basis • Minimize load on network interface by sending large packets • Predictable impact, of enabling diagnostics, on system performance

  47. Summary

  48. Technical Requirements • One media processing system for all media types • Same HW (board & DSP) must run all media types • Easier synchronization between Voice and Video • More balanced system • Less load on system bus • Must include a robust Voice solution • Powerful DSP that can handle Voice + Video. And: • External SD-RAM • Packet interface

  49. Technical Requirements cont’d • Separate media and control path • Requires TDM and IP DSP interfaces • Eliminates Host-DSP bottleneck • Reduces load on host processor • Open Framework • Allows legacy/proprietary algorithms to be “plugged-in” to DSP • High capacity DSP farm • Support latest form factors • PTMC (cPCI)  AMC (ATCA/MicroTCA)

More Related