Shared Services Canada Converged Communications Session III Architecture Framework Advisory Committee

Transcription

1 Shared Canada Converged Communications Session III Architecture Framework Advisory Committee Transformation, Service Strategy and Design June 3, 2013

2 Agenda TIME TOPICS PRESENTERS 09:30 09:45 Opening remarks and objectives for meeting 09:45 09:55 Review of feedback/discussion from previous meetings on converged communications 09:55 11:00 Converged communications - Issues/questions for discussion - Bring your own device (BYOD) B. Long, Chair, W. Daley, Vice-Chair Michel Fortin, DG Telecommunications Transformation Michel Fortin, DG Telecommunications Transformation 11:00 11:15 Health Break 11:15 12:00 Converged communications (continued) Review/discussion of recommendations 12:00 12:15 Upcoming topics core/foundational services All Chair 12:15 12:30 Next steps closing remarks Chair 2

3 Recap From Previous Meetings 3

4 Landscape of Converged Communication Directory Identity Mgmt Authentication Public Certificates ICAM Element Wikis Blogs RSS Conferencing Drop-boxes Collaboration Account Provisioning Address Books Distribution Lists Routing Aliasing Notification Calendaring Public Folders Messaging Converged Communications Chat Mobile Support Converged Voice/Data/Video IP Telephony Instant Messaging Conferencing(Web/ Audio/Video) Presence FAX Archiving Message Search Public Folders Attachments Classification Content Archiving Records Mgmt Enterprise Library Enterprise Search Data De-Duplication Tiered Storage Enterprise Content Management and Storage 4

5 Key Messages From Previous Meetings Separate/decouple Transport/Network from Transport/Network can be provided by multiple carriers (but is more complex to manage) Utilizing the same service/product for a specific service (eg. IP Telephony) across the GC would be preferable to avoid interoperability challenges some services could be bundled Three tier architectural framework is preferable to handle multi-vendor mix but no agreement that IP Multimedia Subsystem (IMS) is the architectural framework for delivering IP multimedia services. 5

6 Three-Tier Architecture (Converged Communications) IP Telephony Service Videoconferencing Service /Applications IM/Presence Service Webconferencing Service Directory DNS Core Standard Protocols (SIP,H.264,G.711,SRTP,etc) Session Management Standard Protocols (SIP,H.264,G.711,SRTP,etc) Access/Connectivity/User Devices Networks 6

7 Potential Deployment Models (Presented at AFAC) Option 1 Network One winner takes all Network and (Not recommended) Option 2 Network #2 Network single provider multi-provider Option 3 Regional Network + Regional Network + Regional Network + Regional Network + Regional integration of Network and (Not recommended) Option 4 Network Network Network Network #3 Network multi-provider multi-provider Most complex to manage 7

8 Potential Deployment Models (Presented at AFAC) Option 5 Network Network Network Network Option 6 Service A Service B Service C Service D Service E Network Network Network Network National Integrated Converged Communications Solution #1 Network multi-provider (potentially single provider) single provider for each service type (eg. voice) (Recommended option) IP Telephony Videoconferencing Bridging Web-conferencing Audio-conferencing Contact Centre Toll Free Network multi-provider single provider for integrated national converged communications service (voice, video and contact center) 8

9 Converged Communications Service Architecture IP Tel Web Conf. Video Conf. IaaS Cloud LAN IaaS Net ISP1 Contact Ctr. Presence IaaS I-Net Gate SaaS MyKey PaaS SEC1 Firewall SaaS IPTel IaaS National Backbone Transport IaaS Regional WAN Transport IaaS Regional WAN Transport PaaS Audio Conf. IaaS DC LAN IaaS LAN IaaS WiFI Broker / Orchest. PaaS Desktop PaaS Directory User Converged Communications Scope Future Not in Scope In Scope Transport Identity & Access Mgmt. SaaS IaaS x86 SaaS Instant Msg. SaaS Fax SaaS Contact Ctr. SaaS Web Conf. SaaS Video Conf. *GSM - Generic Service Model, A generic framework for describing a Service in terms of its systematic hierarchy of related service objects. 9

10 Questions/Issues For Discussion

11 Questions For Discussion Architecture/protocol standards: Voice standards: Preference: G.711 or G729 or other? (i.e. compress?) Call control and signalling: H.323 or SIP (Session Initiation Protocol)? (Call signalling and control, bandwidth control and multimedia transport and control) H:323: H.245 (Control channel protocol); H (Call signaling and RAS signalling) SIP: Real-time Transport Protocol (RTP); Session Description Protocol (SDP); Secure Real-time Protocol (SRTP) Videoconferencing: H.264/MPEG-4 codec standard, others? XMPP (Extensible Messaging and Presence Protocol) for instant messaging and presence Webcast standards? 11

12 Questions For Discussion Security: Separate virtual local area networks (VLANs) for voice/data? SIP trunk security - network security measures Transport Layer Security (TLS) TLS or Internet Protocol (IP) Security? Voice over IPv6 required to implement to meet Government of Canada direction? Security risks? Gateway support? Quality of Service (QoS)/network: Is QoS always required/used for voice over internet protocol (VoIP)? Most cost-effective way to provide QoS? Software-Defined Networking (overlays) Benefits? Readiness? Way ahead? Impact on QoS? MPLS-TP(transport profile) implemented in carrier networks? Interoperability: Unified Communications Interoperability Forum Are the standards (related to voice/video) supported? 12

13 Bring Your Own Device: Discussion Is there a common definition for BYOD? What are the main benefits of implementing BYOD? Is BYOD implementation cost-neutral? Can cost savings be achieved? What is the business case for BYOD that is being made successfully across enterprises? What architectures have become a reference to support BYOD? What are the primary risks (e.g. security, standardization) or challenges (e.g. interoperability) in implementing BYOD? Are you using BYOD in your or a client s organization? How has BYOD supported your organisation s objectives? Have written BYOD policies been developed? Subsidies? What approaches would you recommend to implement/transition to BYOD? What are the challenges in providing communications services to organisations that have BYOD? 13

14 Recommendations Consensus Overall architectural approach is sound Three tier architectural framework is accepted Network should be decoupled from converged communications services from architectural and procurement perspective QoS on network will be important to deliver voice and videoconferencing services Additional Engagement Required Procurement approach for network and converged communications services? Framework used for three-tier model needs further input? Network services deployment model (e.g. national or regional)? Bundling model for converged communications services? Best way to deliver QoS over multivendor networks? BYOD approaches? 14

15 Possible Upcoming Topics (Core/Foundational ) Core/foundational services Enterprise identity credential access management (ICAM) Directory services Internet Protocol addressing (IPv4, IPv6) DNS/DHCP Network operations centre/security operations centre Distributed and workplace computing environments (including devices) Service management Service catalogue 15

16 Next Steps GCNet (wide area network) Industry consultation (date to be confirmed) Converged communications/ip telephony industry engagement - in Fall 2013 (date to be confirmed) Next AFAC meetings focused on core services (e.g. ICAM) (next meeting planned for early July 2013) 16