ATIS 0200005-2012 Cloud Framework for Telepresence Service.pdf

《ATIS 0200005-2012 Cloud Framework for Telepresence Service.pdf》由会员分享，可在线阅读，更多相关《ATIS 0200005-2012 Cloud Framework for Telepresence Service.pdf（28页珍藏版）》请在麦多课文档分享上搜索。

1、 TECHNICAL REPORT ATIS-0200005 CLOUD FRAMEWORK FOR TELEPRESENCE SERVICE ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and communications industry. More than 200 co

2、mpanies actively formulate standards in ATIS Committees, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Architectural Platforms and Emerging Networks. In addition, numero

3、us Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Connected Vehicle, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American Organizational Partner for the 3rd Generation Partnership Pro

4、ject (3GPP), a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the American National Standards Institute (ANSI). For more informat

5、ion, please visit . Notice of Disclaimer there is intent to delve into a number of topics in future specifications to achieve an implementable solution. These topics include, but are not limited to: Scheduling Directory Addressing Redundancy Topology QoS/QoE Service and user management Mobile endpoi

6、nt and infrastructure (3G/4G/WiFi) Over the top endpoint ATIS-0200005 3 The goal of the work described in this specification is to: Develop a Global Marketplace for telepresence services as a component of a broader set of unified communications services with support for (but not limited to) current

7、fully immersive telepresence service endpoints, mobile endpoints, and software clients. Develop a commercial model to support the Global Marketplace and the interfaces and infrastructure required to make it real in today and tomorrows economy. Develop a technical and architectural plan to deploy and

8、 augment the Global Marketplace dimensioning the relationship between the network providing the service, the components of the telepresence service itself, and the service management components. Leverage a platform (focusing on interoperability and interconnectivity) as the foundation for the constr

9、uction of the Global Marketplace for telepresence services. The platform will develop models and standards for interoperability across vendors and the business and technical elements required to build, deploy, and scale the Global Marketplace for telepresence services when deployed point to point (s

10、ervice provider to service provider) and multi-point (more than 2 service providers involved). 2 Informative References The following standards contain provisions which, through reference in this text, constitute provisions of this ATIS Standard. At the time of publication, the editions indicated we

11、re valid. All standards are subject to revision, and parties to agreements based on this ATIS Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. 1 ATIS-0100035 High Level OSS/BSS Telepresence Quality of Experience and Quality

12、 of Service (pending publication).12 ITU-T, Y.1540, Internet Protocol Data Communication Service - IP Packet Transfer and Availability Performance Parameters, 2011.23 Definitions For a list of common communications terms and definitions, please visit the ATIS Telecom Glossary, which is located at .

13、3.1 Exchange: The facilities that allow for cloud services interconnection, system interfaces, and service delivery elements. Exchange does not include service specific components, but primarily contains mediation and common component functions. 3.2 Interoperability: The common set of features, capa

14、bilities, and services enabled and available to customers across a variety of compatible (albeit vendor agnostic) endpoints. 3.3 Interconnectivity: The set of concerns that are addressed when telepresence is deployed between two or more service providers. 3.4 Telepresence: A virtual meeting solution

15、 that is designed to enable users to dictate the “experience” theyd desire with commercial and user preferences driving eventual standards. 3.5 Telepresence service: The telepresence service is a managed, hosted, or premises-based delivery of video services. A telepresence service is a component of

16、the broader set of services enabling unified communications for an enterprise or consumer. Unified communications refers to services such as presence, instant messaging, document and personal video sharing, telephony, unified inbox services such as voice mail, blogging, web conferencing, and other e

17、lements of what it takes to provide a portfolio of collaborative services for an enterprise or consumer. The telepresence service may consist of the following elements: 1This document is available from the Alliance for Telecommunications Industry Solutions, 1200 G Street N.W., Suite 500, Washington,

18、 DC 20005. 2This document is available from the International Telecommunications Union. ATIS-0200005 4 1. Fully managed service bundle that includes installation, full monitoring and management of endpoints, network and inter-company scheduling. 2. Secure, reliable, and highly scalable “in person” m

19、eeting capabilities including document sharing, integrated web conferencing, recording, multi-screen services, and integration with enterprise telephony systems. 3. A network capable of Quality of Service delivery an optimal quality of experience. Today, this is delivered over an MPLS network. 4. We

20、b-based scheduling, directory assistance, reporting, and billing/settlement services. 5. “Meet-Me” scheduling with any subscribed locations (intra and inter company). 6. Delivery of telepresence over QoS challenged devices and access network. 7. Service provisioning including MPLS VPN transport serv

21、ices (although, in the future, perhaps MPLS VPN will not be required). 8. Remote help desk service and on-site equipment maintenance and repair. 4 Acronyms some of these areas appear below: 1. No common implementation between providers. 2. Very limited business to business end customer visibility. 3

22、. Desire for common and easily identified routing mechanism between disjoint users. 4. Integration of the OTT to the “network” via standards and application programing interfaces (APIs). 5. Doesnt address the explosion of personal end points (both fixed and mobile). 6. Explore the role of a (or a ne

23、twork of) neutral third party exchange (s) as a facilitator for inter-provider unified architecture and business delivery. A different way to ask the same question is: “What elements of the telepresence service, once services are to a size and scale of three or more providers, will scale better (ope

24、rate more efficiently) if offered by one of the providers involved in the service delivery?” There are currently two options to achieve federation in telepresence, they are described below. 1. Current Path: Negotiated bi-lateral or multi-lateral agreement. Safe approach, controlled business model. S

25、LA “certainty” and manageability. Competitive sales differentiation (“you can call anyone in the XYZ SP community for free”). Enterprise customers of the Service Providers are frustrated because of the lack of endpoint visibility. 2. Proposed Path: Standards-based approach leveraging existing SIP vo

26、ice methods. Reachability to millions versus thousands of end points. Leverage existing SIP voice capabilities: hierarchical (leveraging current network layers in place for SIP-based voice services), OSS/BSS, settlements. There are parts of the topology and compilation of application and service com

27、ponents that will perhaps scale better and more efficiently using a hierarchical model. There are other components, however, that will be more operationally efficient in a “flatter” or non-hierarchical deployment. These are described in this specification, and also is a topic for further research in

28、 future specifications driven by commercial and market evolution. Approach OTT ubiquity with a collective wireline/wireless service provider approach. Create a tipping point for pervasive business and business to consumer video services. One of the key architectural and business considerations shoul

29、d address the natural IP peering point between two service providers that offer telepresence services: Existing SP telepresence exchanges are not the natural IP peering point between providers (line side services only). An “interworking” of application level peering for telepresence is required to i

30、nsure the network “behaves”: These elements include QoS treatment and the way that the network interacts with the application to deliver optimal QoE. In order to deliver the optimal QoE, a separation of what is done at the network peering level and what is done at a neutral third party, more specifi

31、cally at the application level, is one of the key elements to consider for delivery of telepresence services at cloud size and scale. A neutral third party exchange provides services based on the SIP voice model such as billing/settlement, directory integration, scheduling, and endpoint, plus other

32、visibility services. These services, delivered by a neutral third party (or network of them), empower the delivery of telepresence services across providers at the size and scale required as video services become a pervasive part of how we communicate. ATIS-0200005 14 Redundancy and resiliency at al

33、l levels of the service deployment is imperative. Examples of redundancy and resiliency include multi-path, failover, determination of routing, and selection of path, and many other network, application, and service management layer considerations. Service assurance is described later in this specif

34、ication in the context of security services required to insure all elements of the services operate as they should, and provide the required visibility and control elements required for proper network operation. There are other elements that will continue to operate in a bi-lateral, manner adopting

35、and utilizing current methods and practices. Further exploration of service separation and location for telepresence services is a key item for further consideration as telepresence standards work is progressed. The model for SP-to-SP telepresence peering is described in Figure 8 below. The evolutio

36、n of the telepresence exchange and the role of the neutral third party is a topic that will be addressed in a future specification. The architecture and business models for the neutral third party and the services that it will provide establish the foundation for delivery of telepresence services as

37、 the industry matures. Figure 8 - SP to SP Telepresence Peering When examined through the lens of the Service Provider-to-Service Provider telepresence peering model, there are similarities to federated SIP-based voice services in the market today. These include: 1. Telepresence deployment and opera

38、tion has many similarities to Voice over IP but with an extra media stream (or two). 2. Telepresence should use the same VoIP routing (plus URI). ATIS-0200005 15 3. Telepresence is similar to Voice over IP Quality of Service Marking and Billing. 4. For telepresence, instead of 64kbps, it is 1.5Mbps

39、to 15Mbps per session. There are a number of critical considerations for the third party peering model described above: Common exchange of telepresence traffic: o Billing and settlements. o QoS/QoE traffic exchange. o Directory integration. o Endpoint visibility. o Routing plan: a desire for common

40、and easily identified routing mechanism between disjointed users. o Media streams: a number of video, audio, and presentation streams. Security model: o Coping with DDoS attacks. o Rate limiting. o Topology hiding. Regulatory issues: Lawful Intercept. How to integrate OTT traffic (need to integrate

41、into value add network services). This specification endeavors to contribute to a catalog of non-service specific service enablers. Examining three services produces the catalog or Cloud Service data model: 1. CDN-I 2. Telepresence 3. Virtual desktop services The “macro” areas of the telepresence se

42、rvice that contribute to the Cloud Service data model are: 1. SMI (Service Management Infrastructure layer): a. Billing and settlement. b. Operations. c. Fulfillment. d. Service assurance (performance, SLA ,and fault management). e. Visibility and control. f. Portal and presentation services. g. Sub

43、scriber management services. 2. RTNI (Real Time Network Infrastructure layer): a. UNI. b. NNI. 3. Telepresence infrastructure layer: a. Signaling interface. b. Policy interface. c. Identity interface. d. Endpoint/client interface. 8 Quality of Experience Measurements these differences are highlighte

44、d below. The following table represents spatial resolution and motion handling aspects, with associated bandwidth, of different telepresence quality levels. The targets specified in the table below are illustrative. Recommendations for formal standardization of these measurements will be further def

45、ined in upcoming ATIS specifications. ATIS-0200005 17 Table 1 - Telepresence Traffic Characteristics - Max Bandwidth Consumption Per Second Maximum Bandwidth Consumption Kilobits Per Second (kbps) Resolution 1080p 1080p 1080p 720p 720p 720p 720p Motion Handling Best Better Good Best Better Good Lite

46、 Video per Screen (kbps) 4000 3500 3000 2250 1500 100 936 Audio per Microphone (kbps) 64 64 64 64 64 64 64 Auto Collaboration Video Channel 500 500 500 500 500 500 100 Auto Collaborate Audio Channel (kbps) 64 64 64 64 64 64 64 Single Screen Systems 4628 4128 3628 2878 2128 1628 1164 Total Audio and

47、Video (kbps) 4756 4256 3756 3006 2256 1756 1292 Triple Screen Systems 12756 11256 9756 7606 6256 3766 Total Audio and Video (kbps) + 20% for Layer 2-4overhead Single Screen Systems max bandwidth (kbps) Tx 5554 4954 4358 3454 2554 1954 1397 Includes layer 2-4 overheard Rx 5707 6107 4607 3607 2707 210

48、7 1550 Triple screen systems max bandwidth (kbps) 15307 13507 11707 9007 6307 4507 Includes layer 2-4 overheard Optional Ad-on Features (kbps) *Not applicable to 720p Lite 30fps Auto Collaborate 4000 +20% for Layer 2-4 overhead 4800 CTRS Recording in CIF 704 +20% for Layer 2-4 overhead 845 SD Intero

49、perability Audio 704 +20% for Layer 2-4 overhead 922 Video 64 WebEx On Touch Audio 304 +20% for Layer 2-4 overhead 442 Video 64 The table above details resolutions with a minimum of 720p lite. A future specification will detail the architecture and interworking required to provide a quality experience over bandwidth constrained access methods and devices. The graphics and text below detail the measurement and impact of latency, network jitter, video jitter, and loss targets as they relate to the telepresence servi