7.1 capc product description wmx 1

Motorola Confidential Proprietary Preliminary CAP-C Product Description

Document is subject to change

MOTOWi4 Motorola CAP-C

Preliminary Product Description

Information contained within this preliminary product description is subject to change

Initial Draft Version: 0.1 Working Draft Date: 2007-03-13 Pilot Released Revision to Released



Revision History

Doc Revision Date Changed Name Modifications Made 0.1 03/13/2007 Jason Tian Initial draft



Table of Contents 1 Introduction................................................................................................................. 5

1.1 Broadband Wireless Access................................................................................ 5 1.2 MotoWi4 based on 802.16e ................................................................................ 5 1.3 Wimax Forum Defined Architecture .................................................................. 6 1.4 Mapping of Motorola Architecture to the Wimax Reference Architecture........ 7

2 CAP-C Details ............................................................................................................ 9 2.1 CAP-C platform.................................................................................................. 9

2.1.1 CAP-C Chassis.......................................................................................... 10 2.1.2 CAP-C System Controller......................................................................... 10 2.1.3 CAP-C Payload Blade............................................................................... 11 2.1.4 Power Entry Module (PEM) ..................................................................... 11 2.1.5 Shelf Management Controller................................................................... 11 2.1.6 Fan Tray Modules (FTM) ......................................................................... 11 2.1.7 Rear Transition Moduel (RTM)................................................................ 12 2.1.8 CAP-C Platform Transport ....................................................................... 12

2.2 CAP-C Redundancy.......................................................................................... 12 2.3 CAP-C Capacity................................................................................................ 12 2.4 CAP-C Interfaces .............................................................................................. 13

2.4.1 CAP-C Physical Interface ......................................................................... 13 2.4.2 CAP-C Logical Interface Types................................................................ 13

2.5 CAP-C IP addressing ........................................................................................ 14 2.5.1 IP Addressing for System Controller........................................................ 14 2.5.2 IP Addressing for pCAPC blade ............................................................... 14

2.6 Regulatory......................................................................................................... 15



Table of Figures

Figure 1: Wimax Forum Defined Network Reference Architecture .................................. 7 Figure 2: ASN Decomposition............................................................................................ 7 Figure 3: Motorola ASN Gateway...................................................................................... 8 Figure 4: Motorola ASN-GW Minimum Configuration..................................................... 8 Figure 5: CAP-C Platform .................................................................................................. 9 Figure 6 CAP-C Chassis Slot Mapping ............................................................................ 10

CAP-C Product Description v1.01 5



1 Introduction

1.1 Broadband Wireless Access Networks including wireless and wireline are converging towards mobile broadband allowing for greater mobility providing user experience similar to what a user would have in an office LAN environment. The technology that offers both mobility and broadband wireless access is the 802.16e based Wimax technology offering significant benefits over other technologies. Wimax networks are geared to support deployments that range from fixed to nomadic to fully mobile solutions. Motorola provides an end to end solution combining it’s Wimax products with commercial off the shelf equipment for either a fixed or mobile solution.

1.2 MotoWi4 based on 802.16e

Motorola is already a leader in Broadband Wireless Access through the Canopy™ product line, a low cost solution primarily used for unlicensed fixed applications. Governments (municipalities) and enterprises use Canopy for voice, video and data backhaul, while many carriers use Canopy for Wireless Internet service, primarily in rural and developing areas. Canopy's excellent RF interference rejection characteristics make it an ideal solution for unlicensed bands at 900MHz, 2.4GHz, and 5.2 to 5.7GHz. Motorola’s first Wimax product Ultra Light Access Point leverages heavily on the success of the canopy product line and offers a Wimax 802.16e based solution for early fixed deployments.

Motorola decided to adopt the 802.16e specification after carefully weighing the benefits of 802.16e over 802.16d. There are significant benefits in using 802.16e over 802.16d even for fixed deployments. These benefits are listed below.

• Scalable OFDMA support o Subchannelization suited for combating varying channel conditions

• Mobility Support • Power savings with the introduction of sleep mode and idle mode • Advanced antenna techniques • Multicast Broadcast Service (MBS) support • Additional service class for realtime applications such as VoIP

The “MotoWi4” is an umbrella marketing term encompassing Motorola Wimax products addressing the broadband wireless access including both fixed and mobile segments. The following segments are the target markets for MotoWi4 solutions.

• Last mile access to residences for voice & data • T1/E1 alternative service for small businesses and enterprises • Personal Broadband service with mobility • Portable VPN service for Mobile Workers




• A complement to 2G, 2.5G and 3G by lowering the cost of data service • Low cost backhaul service for broadband cellular and WiFi Access Points

The product line includes the Ultra Light Access Point (ULAP), Diversity Access Point (DAP), a range of Subscriber Devices – portable and mobile handset solutions, and multi-mode terminals to support other 2G/3G cellular technologies simultaneously, and other supporting network elements such as the CAP-C. This document focuses on the DAP in light of “Mobile” broadband wireless access.

1.3 Wimax Forum Defined Architecture The Wimax forum (http://www.wimaxforum.org) defines the reference architecture for WiMAX based solutions providing an operator the capability to provide fixed or mobile networks. The reference architecture also defines the interfaces between the different logical entities. Error! Reference source not found. below breaks down the reference network into subscriber, network access (NAP) and network service (NSP) domains and defines the interfaces across these domains. As can be seen the NAP is a combination of ASNs with each ASN comprising of network elements to provide network access to end devices. These network elements are shown in Figure 2: ASN DecompositionFigure 2 which breaks the ASN further into the relevant entities.

NAP

R1 R3 R5SS/

MSS

R2

ASN CSN CSN

ASP Network OR Internet

ASP Network OR Internet

R4,

Another ASN

R2Visited NSP

Home NSP




Figure 1: Wimax Forum Defined Network Reference Architecture

ASN

BS

BS

BS

ASN-GWDP & EP

R6

R6

R6

R8

R1

R3/R4

R1

Figure 2: ASN Decomposition

The WiMAX forum also defines three profiles for the ASNs. Profile A and C are similar with an open interface called R6 between the BS and the ASN-GW and an open interface called R8 between the BSs. Profile B considers the R6 and R8 interfaces as unexposed and the ASN interworking is done over the R3/R4 interfaces. Please note that the ASN-GW has two logical parts – one is the Detection Point or DP and the other is the Enforcement Point or EP.

1.4 Mapping of Motorola Architecture to the Wimax Reference Architecture

Motorola’s solution for the ASN is compliant to Profile B with the defined reference points of R3 and R4 available for interworking with other network components such as other ASNs and system elements within the core services network (CSN). The figure below is a high level representation of the Motorola implementation of the ASN-GW. This implementation covers both the ASN-GW DP and ASN-GW EP. Motorola’s core strength is embodied in the CAP-C part of the ASN-GW where some of the control functionality including authentication and mobility related functions resides. Motorola’s relies on its partners core strengths in IP routing and L2 switching to provide




a complete ASN-GW solution. Figure 3 shows the complete Motorola ASN-GW solution. The minimum configuration will have an CAP-C chassis, one Ethernet Switch (Foundry XMR8000) and a Redback SmartEdge 800 chassis. Details are provided in the capacity section.

Ethernet SwitchTo Radio Sites

Router/FAIP Core

MotorolaCAP

Controller

Figure 3: Motorola ASN Gateway

Figure 4: Motorola ASN-GW Minimum Configuration




2 CAP-C Details The ASN as shown in Figure 2 contains ASN Gateways and BSs. An ASN GW is further divided into two parts called the ASN-Detection Point (ASN-DP) and ASN-Enforcement Point (ASN-EP). The CAP-C roughly is equivalent to the ASN-DP function with majority of the functionality of the CAP-C related to the mobility aspects of the Wimax system. The following is a list of features for the CAP-C.

• Authentication liaison between the user/device and the AAA server • Security functions such as Local Key Distribution Function (LKDF) for

delivering Authentication Keys • Paging Controller (PC) • QoS Policy Decision Point • Flow admission control related to handovers • Access Control • Handover Decision Point • Proxy Mobile IP Client Validation

2.1 CAP-C platform The CAP-Controller is designed to support a large number of users (up to 1 million) on a single chassis based on the ATCA platform architecture with scalability in mind. The platform is the Motorola Embedded Communications Computing Avantellis 3406 server running standard MontaVista CGL (Carrier Grade Linux) OS. The Avantellis product line encompasses the hardware platform, hardware control software, middleware, and operating system environment.

Figure 5: CAP-C Platform




2.1.1 CAP-C Chassis The CAP-C chassis, which is Motorola Avantellis 3406 server, utilizes the 1406 ATCA-based chassis.. The chassis provides 14-slots, two of which are utilized by the system controller and two of which are reserved for future use. There are 10 slots available for pCAPC blades. As shown in the Figure 6 , there are 14 logical slots that are mapped to the physical slots. Each logical slot will have one specific blade / card associated with. The CAP-C chassis provides 14-slots, two of which are utilized by the system controller and two of which are reserved for future use leaving 10 slots being available for CAP-C function blades.

Figure 6 CAP-C Chassis Slot Mapping

CAP-C features the following:

• Two DC hot-swappable. N+1 redundant Power Entry Modules (PEM) • Two Shelf Managers (SAM) • Upper Fan Tray Modules (FTM) • 1 Lower Fan Tray Module (FTM) • Front access service and installation of blades • Rear access service and installation of transition modules

2.1.2 CAP-C System Controller The CAP-C System Controller is the Motorola ECC provided ATCA-F101 System Controller and Switching Blade. The System Controller provides both redundant layer-2 switching and system management. The major features of this blade are as follows:




• MPC7447 microprocessor @ 1.0 GHz • PMC-based 40GB hard disk drive • Marvell Discovery II System Controller • 512 MB ECC protected RAM • PICMG 3.0 base interface and PICMG 3.1 data interface switching (up to 1.0

Gbs)

2.1.3 CAP-C Payload Blade The CAP-C payload blade is the Motorola ECC provided ATCA-7221 processing blade. This processing blade will contain dual single core Intel® Xeon LV 2.8 GHz processors running in two-way symmetric multi-processing mode. In addition, each CAP-C blade will be equipped with 8 GB ECC-enabled DDR2 RAM and can be extended up to 16 GBs. Each CAP-C will also be equipped with a rear transition module that comes equipped with dual GbE ports and a Fujitsu 37GB Serial Attached SCSI hard drive used for storing local software and logging information.

2.1.4 Power Entry Module (PEM) The CAP-C chassis has PICMG 3.0 compliant, dual PEMs and is rated for -40VDC to -72VDC. The PEMs plug directly into the mid-plane and deliver power to the backplane. Each input is rated for 100 Amps which is then segmented down to four individual 25 Amp circuit breakers, or four internal feeds with voltage and circuit breaker monitoring per PEM. These four feeds each power four ATCA blade or hub slots. Each PEM can supply 200 watts of power to each blade slot. The PEMs are hot-swappable and when using 200W per slot PEMs, two are required to support N+1 redundancy. If the system is configured for redundant operation using two power supplies, they operate in load sharing where the total load is equal to or less than what one power supply can provide. The CAP-C can operate at 200W per slot capacity with one PEM installed however this would not be a redundant configuration.

2.1.5 Shelf Management Controller The CAP-C contains 2 shelf management controllers referred to as SAMs, each of which consists of the shelf manager carrier and the shelf management mezzanine module that is installed on the carrier blade. Both controllers are installed in slot 0 located at the left side of the front of the CAP-C chassis. The Shelf Management Controllers operate in an active/ standby mode of operation.

2.1.6 Fan Tray Modules (FTM) The CAP-C chassis supports three upper and one lower FTM. Each upper FTM houses 4 separate fans and are arranged for maximum volume air flow, even distribution, and fault tolerance. The lower FTM is a single module which is responsible for cooling all rear transition modules in the chassis. The CAP-C is required to be equipped with 3 upper FTMs and 1 lower FTM.




2.1.7 Rear Transition Moduel (RTM) The CAP-C System Controller will come equipped with a RTM that will provide connectivity to external devices. 4 GbE ports will be allocated for extending the data interface fabric to provide connectivity to an external IP network. 8 GbE ports will be reserved for future multi-chassis CAP-C support.

2.1.8 CAP-C Platform Transport The CAP-C transport is in charge of providing connectivity between the internal and external components. Internal components include pCAPC tasks and other pCAPCs on the same node; external components include Router/FA, AAA, DHCP, EMS, DNS, AP, CAP-C nodes, and pCAPCs on a different node.The following CAP-C components are needed to support the transport functionality:

• Base and Fabric Interface switching fabrics • ATCA-F101 Switch Board • ATCA-F101 Rear Transition Module • ATCA-7221 pCAPC Board • ATCA-7221 Rear Transition Module

The CAP-C transport is designed to meet the availability of 99.9995%. Therefore all of the internal/ external interfaces will be deployed on a redundant configuration.

2.2 CAP-C Redundancy CAP-C, as part of the Wi4 system, is designed to achieve 5-NINES high availability. Based on the industry-standard ATCA platform, CAP-C inherits the high-availability design of the PICMG 3.0 specifications. The backplane, power supply and distribution, fan module, alarm boards, switching fabrics, and shelf controller boards are all redundant. The host processing boards and processor PMC cards are in active-standby redundancy. In addition, the hard-disk for persistent data storage is redundant as well.

2.3 CAP-C Capacity • AP Capacity:

The CAP-C is required to support a maximum of 1000 APs. The CAP-C will have a total of 5 active pCAPCs in a fully configured system. Therefore, each pCAPC and the components executing as part of that pCAPC must support a maximum of 200 APs.

• Subscriber Capacity: The subscriber capacity within the CAP-C is determined by the type of traffic, the mobility of that traffic, and the overall throughput that the traffic is introducing within the CAP-C. In WMX 1.0, total 1,000,000 subscribers can be supported by a CAP-C node and each pCAPC can support upto 200,000 subscribers.




2.4 CAP-C Interfaces

2.4.1 CAP-C Physical Interface CAP-C is physically connected to the IP network via the Ethernet interface. Typically, there will be routers in between the CAP-C and other WiMAX network entities, such as AP, AAA and EMS. Each active blade (System Controller or pCAPC) of CAP-C will have a unique IP address for communication within the IP network.

2.4.2 CAP-C Logical Interface Types There are three types of logical interfaces implemented in the CAP-C node for the system communication and operation management. The logical interfaces are defined as follows:

• External Communication Interface • Internal Communication Interface • Operational Interface

2.4.2.1 External Communication Interface The external communication interface enables the CAP-C to communicate with other NEs in the WiMAX system. This interface includes the following logical connections.

• CAP-C – AP • CAP-C – CAP-C • CAP-C – AAA • CAP-C - EMS • CAP-C – Router

The connections for CAP-C – AP, CAP-C – CAP-C and CAP-C - Router are controlled by CAP-C Link Management function. The communication between the CAP-C and AAA is being managed by the CAP-C AAA proxy server, which is the Authenticator component. For communication to the EMS, the CNEOMI-Lite Agent is implemented in the CAP-C product and acts as the interface between the CAP-C and EMS.

2.4.2.2 Internal Communication Interface The internal communication interface is implemented for message processing between components. This interface will not have exposure to the network entities outside CAP-C node.

2.4.2.3 Operational Interface The CAP-C Operational Interface consists of the following:

• Local Maintenance Terminal (LMT) • CAP-C Shell Access

LMT is a web-based interface,which is used for day-to-day operations including account management, debugging CAP-C, alarm and statistics management, etc. CAP-C Shell Access is utilized to commission the CAP-C for the first time. This interface will not be used for normal operations.




2.5 CAP-C IP addressing

2.5.1 IP Addressing for System Controller The Active System Controller residing in the ATCA-F101 board needs to be reachable by the different network elements residing on the other side of the Router/FA. In order to accomplish this, the Active System Controller Ethernet Interfaces will need to be configured with a routable IP address. This address can be obtained via a customer provided DHCP or via static configuration from the LMT. The IP address is assigned to the pair of System Controllers and is used by the active controller. The Standby System Controller will not perform a DHCP request. It will take over the IP address assigned to the pair of System Controllers during the failover. The EMS will decide the way to obtain the IP address by selecting DHCP or Static IP address. By default, the DHCP should be enabled. If DHCP is disabled, all the network related information will need to be configured via the LMT.

2.5.2 IP Addressing for pCAPC blade The ATCA-7221 pCAPC cards need to be reachable by the different Network Elements located on the other side of the Router/FA. In order to accomplish this, the pCAPC Ethernet Interfaces will need to be configured with a routable address provided by the EMS. The EMS may provide a FQDN (Fully Qualified Domain Name) or an IP Address. If a FQDN is provided, the address will be retrieved via a DNS query. The CAP-C LMT also allows configuring the ATCA-7221 with static IP address




2.6 Regulatory




Appendix A – Abbreviations AP Access Point ASN Access Service Network ASN-GW ASN-Gateway BCU Base Control Unit BTS Base Transceiver Station CAP-C Carrier Access Point Controller CPE Customer Premise Equipment CPRI Common Public Radio Interface CSN Core Service Network DAP Diversity Access Point EAP Extensible Authentication Protocol EMS Element Management System FRU Field Replaceable Unit GHz Gigahertz GPS Global Positioning System I/O Input/Output IMS Internet Multimedia System IP Internet Protocol IPSec IP Security IPv6 IP version 6 LAN Local Area Network MAC Media Access Control MHz Megahertz MSS Mobile Subscriber Station OFDMA Orthogonal Frequency Division Multiple Access QoS Quality of Service QPSK Quadrature Phase Shift Keying RF Radio Frequency RoHC Robust Header Compression SNMP Simple Network Management Protocol TDD Time Division Duplex WIMAX Worldwide Interoperability for Microwave Access

7.1 capc product description wmx 1

Documents