Cisco TelePresence Network Systems 2.0 Design Guide - TelePresence Network Deployment Models [Design Zone for Medianet/Video]

Table Of Contents

TelePresence Network Deployment Models

Introduction

Intra-Campus Deployment Model

Intra-Enterprise Deployment Model

Cisco Powered Networks

Point-to-Point versus Multipoint

Inter-Enterprise/Business-to-Business Deployment Model

Hosting and Management Options

TelePresence Phases of Deployment

TelePresence Network Deployment Models

Introduction

TelePresence systems can be deployed over enterprise networks in one of four principle ways:

•Intra-Campus Deployment Model

•Intra-Enterprise Deployment Model

•MultiPoint Deployment Model (see Point-to-Point versus Multipoint)

•Inter-Enterprise/Business-to-Business Deployment Model

The following sections provide an overview of these TelePresence network deployment models, as well as logical phases of TelePresence deployments. In comparison, CUCM deployment models are discussed in detail in Chapter 9, "Call Processing Deployment Models."

Intra-Campus Deployment Model

The intra-campus network deployment model has TelePresence systems limited to a single enterprise campus or between sites interconnected via a high-speed (1 Gigabit or higher) Metropolitan Area Network (MAN). This deployment model is applicable for enterprises that have a large number of buildings within a given campus and employees who are often required to drive to several different buildings during the course of the day to attend meetings. Deploying multiple TelePresence systems intra-campus can reduce time lost by employees driving between buildings to attend meetings, without sacrificing meeting effectiveness, and thus improve overall productivity. The intra-campus deployment model is also commonly used in conjunction with the other two: where customers deploy multiple CTS rooms within their headquarters campus to meet demand for room availability as part of a global intra-enterprise or inter-enterprise deployment.

The network infrastructure of an intra-campus deployment model is predominantly Cisco Catalyst switches connecting via GigE or 10GigE links. The intra-campus TelePresence deployment model is illustrated in Figure 3-1.

Figure 3-1 TelePresence Intra-Campus Network Deployment Model

Intra-Enterprise Deployment Model

The intra-enterprise network deployment model for TelePresence systems connects not only buildings within a campus, but also geographically-separated campus sites and branch offices. The intra-enterprise model expands on the intra-campus model to include sites connected via a Wide Area Network (< 1 Gigabit).

The intra-enterprise deployment model is suitable for businesses that often require employees to travel extensively for internal meetings. Deploying TelePresence systems within the enterprise not only improves productivity—by saving travel time—but also reduces travel expenses. Furthermore, the overall quality of work/life is often improved when employees have to travel less.

The network infrastructure of an intra-enterprise deployment model is a combination of Cisco Catalyst switches within the campus and Cisco routers over the WAN, which may include private WANs, MPLS VPNs, or Metro Ethernet networks. WAN speeds may range from 34 Mbps E3 circuits to 1 Gbps OC-192 circuits. The intra-enterprise TelePresence deployment model is illustrated in Figure 3-2.

Figure 3-2 TelePresence Intra-Enterprise Network Deployment Model

Cisco Powered Networks

A valuable consideration when selecting WAN/VPN service providers is to identify those that have achieved Cisco Powered Network designation. These providers have earned the Cisco Powered designation by maintaining high levels of network quality and by basing their WAN/VPN services end-to-end on Cisco equipment.

In addition, an increasing number of Cisco Powered providers have earned the QoS Certification for WAN/VPN services. This means that they have been assessed by a third party for the ability of their SLAs to support real-time voice and video traffic, and for their use of Cisco best practices for QoS. For a list of recommended service providers, see the following URL: http://www.cisco.com/cpn.

The use of Cisco Powered networks is recommended—but not mandatory—for Cisco TelePresence intra-enterprise deployments. The key is meeting the service levels required by TelePresence, which are detailed in Chapter 4, "Quality of Service Design for TelePresence."

Point-to-Point versus Multipoint

In both the intra-campus and inter-enterprise deployment models, customers may also deploy multipoint TelePresence resources to facilitate multi-site meetings (meetings with three or more TelePresence rooms). These resources may be located at any one of the campus locations or may be located within the service provider cloud as either a co-located resource or a managed/hosted resource.

Multipoint platforms and network design recommendations, such as additional bandwidth and latency considerations, Cisco TelePresence Multipoint switch considerations, scaling considerations, etc., are discussed in further detail in Chapter 10, "Cisco TelePresence Multipoint Solution Essentials," Chapter 11, "Cisco Multipoint Technology and Design Details," and Chapter 12, "Cisco TelePresence Multipoint Solution Circuit and Platform Recommendations."

Inter-Enterprise/Business-to-Business Deployment Model

The inter-enterprise network deployment model connects not only TelePresence systems within an enterprise, but also allows for TelePresence systems within one enterprise to call systems within another enterprise. The inter-enterprise model expands on the intra-campus and intra-enterprise models to include connectivity between different enterprises. This is also referred to as the business-to-business (B2B) TelePresence deployment model.

The inter-enterprise model offers the most flexibility and is suitable for businesses that often require employees to travel extensively for both internal and external meetings. In addition to the business advantages of the intra-enterprise model, the B2B TelePresence deployment model lets employees maintain high-quality customer relations, without the associated costs of travel time and expense.

The network infrastructure of the inter-enterprise/B2B deployment model builds on the intra-enterprise model and requires the enterprises to share a common MPLS VPN service provider (SP). Additionally, the MPLS VPN SP must have a "shared services" Virtual Routing and Forwarding (VRF) instance provisioned with a Cisco IOS XR Session/Border Controller (SBC).

The Cisco SBC bridges a connection between two separate MPLS VPNs to perform secure inter-VPN communication between enterprises. Additionally, the SBC provides topology and address hiding services, NAT and firewall traversal, fraud and theft of service prevention, DDoS detection and prevention, call admission control policy enforcement and guaranteed QoS.

Note For more information about Cisco IOS XR SBC functionality and deployment models, refer to:
http://www.cisco.com/univercd/cc/td/doc/product/ioxsoft/iox34/cgcr34/sbc_c34/sbc34abt.htm

The inter-enterprise/B2B TelePresence deployment model is illustrated in Figure 3-3.

Figure 3-3 TelePresence Inter-Enterprise Network Deployment Model

The initial release of the B2B solution requires a single SP to provide the shared services to enterprise customers, which includes the secure bridging of customer MPLS VPNs. However, as this solution evolves, multiple providers will be able to peer and provide B2B services between them, which will no longer require that both enterprise customers share the same SP.

Hosting and Management Options

While the focus of this paper is TelePresence deployments within the enterprise, several of these options could be hosted or managed by SPs. For example, the Cisco Unified Communications Manager (CUCM) and Cisco TelePresence Manager (CTS-MAN) servers and multipoint resources may be located on-premise at one of the customer campus locations, co-located within the SP network (managed by the enterprise) or hosted within the SP network (managed by the SP). However, with the exception of inter-VPN elements required by providers offering B2B TelePresence services, the TelePresence solution components and network designs remain fundamentally the same whether the TelePresence systems are hosted/managed by the enterprise or the SP.

TelePresence Phases of Deployment

As TelePresence technologies evolve, so too will the complexity of deployment solutions. Therefore, enterprise customers will likely approach their TelePresence deployments in phases, with the main phases of deployment being:

•Phase 1. Intra-Campus/Intra-Enterprise Deployments—Most enterprise customers will likely begin their TelePresence rollouts by provisioning (Point-to-Point) Intra-Enterprise TelePresence deployments. This model could be viewed as the basic TelePresence building block, on which more complex models may be added.

•Phase 2. Intra-Enterprise MultiPoint Deployments—As collaboration requirements may not always be facilitated with Point-to-Point models, the next logical phase of TelePresence deployment would be to introduce multipoint resources to the Intra-Enterprise deployment model. Phases 1 and 2 may often be undertaken simultaneously.

•Phase 3. Business-to-Business Deployments—To expand the application and business benefits of TelePresence meetings to include external (customer- or partner-facing) meetings, a Business-to-Business deployment model can be subsequently overlaid on top of either a Point-to-Point or a MultiPoint Intra-Enterprise deployment.

•Phase 4. TelePresence to the Executive Home—Due to the high executive-perk appeal of TelePresence and the availability of high-speed residential bandwidth options (such as fiber to the home), some executives may benefit greatly from deploying TelePresence units to their residences. Technically, this is simply an extension of the Intra-Enterprise model, but for the purposes of this document it is viewed as a separate phase due to the unique provisioning and security requirements posed by such residential TelePresence deployments.

Figure 3-4 TelePresence to the Executive Home (an Extension of the Intra-Enterprise Deployment Model)

	Cisco TelePresence Network Systems 2.0 Design Guide
	TelePresence Network Deployment Models
Cisco TelePresence Network Systems 2.0 Design Guide Cisco TelePresence Solution Overview Connecting the Endpoints TelePresence Network Deployment Models Quality of Service Design for TelePresence Campus QoS Design for TelePresence Branch QoS Design for TelePresence Call Processing Overview Capacity Planning and Call Admission Control Call Processing Deployment Models Cisco TelePresence Multipoint Solution Essentials Cisco Multipoint Technology and Design Details Cisco TelePresence Multipoint Solution Circuit and Platform Recommendations Internal Firewall Deployments with Cisco TelePresence Cisco Services for Cisco TelePresence	Download this chapter TelePresence Network Deployment Models Download the complete book Cisco TelePresence Network Systems 2.0 DG PDF (PDF - 8 MB) Table Of Contents TelePresence Network Deployment Models Introduction Intra-Campus Deployment Model Intra-Enterprise Deployment Model Cisco Powered Networks Point-to-Point versus Multipoint Inter-Enterprise/Business-to-Business Deployment Model Hosting and Management Options TelePresence Phases of Deployment TelePresence Network Deployment Models Introduction TelePresence systems can be deployed over enterprise networks in one of four principle ways: •Intra-Campus Deployment Model •Intra-Enterprise Deployment Model •MultiPoint Deployment Model (see Point-to-Point versus Multipoint) •Inter-Enterprise/Business-to-Business Deployment Model The following sections provide an overview of these TelePresence network deployment models, as well as logical phases of TelePresence deployments. In comparison, CUCM deployment models are discussed in detail in Chapter 9, "Call Processing Deployment Models." Intra-Campus Deployment Model The intra-campus network deployment model has TelePresence systems limited to a single enterprise campus or between sites interconnected via a high-speed (1 Gigabit or higher) Metropolitan Area Network (MAN). This deployment model is applicable for enterprises that have a large number of buildings within a given campus and employees who are often required to drive to several different buildings during the course of the day to attend meetings. Deploying multiple TelePresence systems intra-campus can reduce time lost by employees driving between buildings to attend meetings, without sacrificing meeting effectiveness, and thus improve overall productivity. The intra-campus deployment model is also commonly used in conjunction with the other two: where customers deploy multiple CTS rooms within their headquarters campus to meet demand for room availability as part of a global intra-enterprise or inter-enterprise deployment. The network infrastructure of an intra-campus deployment model is predominantly Cisco Catalyst switches connecting via GigE or 10GigE links. The intra-campus TelePresence deployment model is illustrated in Figure 3-1. Figure 3-1 TelePresence Intra-Campus Network Deployment Model Intra-Enterprise Deployment Model The intra-enterprise network deployment model for TelePresence systems connects not only buildings within a campus, but also geographically-separated campus sites and branch offices. The intra-enterprise model expands on the intra-campus model to include sites connected via a Wide Area Network (< 1 Gigabit). The intra-enterprise deployment model is suitable for businesses that often require employees to travel extensively for internal meetings. Deploying TelePresence systems within the enterprise not only improves productivity—by saving travel time—but also reduces travel expenses. Furthermore, the overall quality of work/life is often improved when employees have to travel less. The network infrastructure of an intra-enterprise deployment model is a combination of Cisco Catalyst switches within the campus and Cisco routers over the WAN, which may include private WANs, MPLS VPNs, or Metro Ethernet networks. WAN speeds may range from 34 Mbps E3 circuits to 1 Gbps OC-192 circuits. The intra-enterprise TelePresence deployment model is illustrated in Figure 3-2. Figure 3-2 TelePresence Intra-Enterprise Network Deployment Model Cisco Powered Networks A valuable consideration when selecting WAN/VPN service providers is to identify those that have achieved Cisco Powered Network designation. These providers have earned the Cisco Powered designation by maintaining high levels of network quality and by basing their WAN/VPN services end-to-end on Cisco equipment. In addition, an increasing number of Cisco Powered providers have earned the QoS Certification for WAN/VPN services. This means that they have been assessed by a third party for the ability of their SLAs to support real-time voice and video traffic, and for their use of Cisco best practices for QoS. For a list of recommended service providers, see the following URL: http://www.cisco.com/cpn. The use of Cisco Powered networks is recommended—but not mandatory—for Cisco TelePresence intra-enterprise deployments. The key is meeting the service levels required by TelePresence, which are detailed in Chapter 4, "Quality of Service Design for TelePresence." Point-to-Point versus Multipoint In both the intra-campus and inter-enterprise deployment models, customers may also deploy multipoint TelePresence resources to facilitate multi-site meetings (meetings with three or more TelePresence rooms). These resources may be located at any one of the campus locations or may be located within the service provider cloud as either a co-located resource or a managed/hosted resource. Multipoint platforms and network design recommendations, such as additional bandwidth and latency considerations, Cisco TelePresence Multipoint switch considerations, scaling considerations, etc., are discussed in further detail in Chapter 10, "Cisco TelePresence Multipoint Solution Essentials," Chapter 11, "Cisco Multipoint Technology and Design Details," and Chapter 12, "Cisco TelePresence Multipoint Solution Circuit and Platform Recommendations." Inter-Enterprise/Business-to-Business Deployment Model The inter-enterprise network deployment model connects not only TelePresence systems within an enterprise, but also allows for TelePresence systems within one enterprise to call systems within another enterprise. The inter-enterprise model expands on the intra-campus and intra-enterprise models to include connectivity between different enterprises. This is also referred to as the business-to-business (B2B) TelePresence deployment model. The inter-enterprise model offers the most flexibility and is suitable for businesses that often require employees to travel extensively for both internal and external meetings. In addition to the business advantages of the intra-enterprise model, the B2B TelePresence deployment model lets employees maintain high-quality customer relations, without the associated costs of travel time and expense. The network infrastructure of the inter-enterprise/B2B deployment model builds on the intra-enterprise model and requires the enterprises to share a common MPLS VPN service provider (SP). Additionally, the MPLS VPN SP must have a "shared services" Virtual Routing and Forwarding (VRF) instance provisioned with a Cisco IOS XR Session/Border Controller (SBC). The Cisco SBC bridges a connection between two separate MPLS VPNs to perform secure inter-VPN communication between enterprises. Additionally, the SBC provides topology and address hiding services, NAT and firewall traversal, fraud and theft of service prevention, DDoS detection and prevention, call admission control policy enforcement and guaranteed QoS. Note For more information about Cisco IOS XR SBC functionality and deployment models, refer to: http://www.cisco.com/univercd/cc/td/doc/product/ioxsoft/iox34/cgcr34/sbc_c34/sbc34abt.htm The inter-enterprise/B2B TelePresence deployment model is illustrated in Figure 3-3. Figure 3-3 TelePresence Inter-Enterprise Network Deployment Model The initial release of the B2B solution requires a single SP to provide the shared services to enterprise customers, which includes the secure bridging of customer MPLS VPNs. However, as this solution evolves, multiple providers will be able to peer and provide B2B services between them, which will no longer require that both enterprise customers share the same SP. Hosting and Management Options While the focus of this paper is TelePresence deployments within the enterprise, several of these options could be hosted or managed by SPs. For example, the Cisco Unified Communications Manager (CUCM) and Cisco TelePresence Manager (CTS-MAN) servers and multipoint resources may be located on-premise at one of the customer campus locations, co-located within the SP network (managed by the enterprise) or hosted within the SP network (managed by the SP). However, with the exception of inter-VPN elements required by providers offering B2B TelePresence services, the TelePresence solution components and network designs remain fundamentally the same whether the TelePresence systems are hosted/managed by the enterprise or the SP. TelePresence Phases of Deployment As TelePresence technologies evolve, so too will the complexity of deployment solutions. Therefore, enterprise customers will likely approach their TelePresence deployments in phases, with the main phases of deployment being: •Phase 1. Intra-Campus/Intra-Enterprise Deployments—Most enterprise customers will likely begin their TelePresence rollouts by provisioning (Point-to-Point) Intra-Enterprise TelePresence deployments. This model could be viewed as the basic TelePresence building block, on which more complex models may be added. •Phase 2. Intra-Enterprise MultiPoint Deployments—As collaboration requirements may not always be facilitated with Point-to-Point models, the next logical phase of TelePresence deployment would be to introduce multipoint resources to the Intra-Enterprise deployment model. Phases 1 and 2 may often be undertaken simultaneously. •Phase 3. Business-to-Business Deployments—To expand the application and business benefits of TelePresence meetings to include external (customer- or partner-facing) meetings, a Business-to-Business deployment model can be subsequently overlaid on top of either a Point-to-Point or a MultiPoint Intra-Enterprise deployment. •Phase 4. TelePresence to the Executive Home—Due to the high executive-perk appeal of TelePresence and the availability of high-speed residential bandwidth options (such as fiber to the home), some executives may benefit greatly from deploying TelePresence units to their residences. Technically, this is simply an extension of the Intra-Enterprise model, but for the purposes of this document it is viewed as a separate phase due to the unique provisioning and security requirements posed by such residential TelePresence deployments. Figure 3-4 TelePresence to the Executive Home (an Extension of the Intra-Enterprise Deployment Model)
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks