Professional Documents
Culture Documents
Brkagg 2002
Brkagg 2002
Brkagg 2002
BRKAGG-2002
Presentation_ID
Cisco Public
Agenda
Introduction to Femtocell Market Drivers Femtocell Architecture Key Femto Features Femto Call Flows Standards Update Cisco Solution Components Femto Integration Summary S
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
Introduction to Femtocell
BRKAGG-2002_c1
Cisco Public
What Is a Femtocell?
In-Home
What Is a Femtocell?
Contrast With Macro
Tiny 3G Home Access Point
Gives 3G signal inside the home
Licensed Spectrum
Node-B
Very low RF power. Standalone or integrated into home gateway. Works with all standard handsets.
Licensed Spectrum
Security Gateway
Internet
Market Drivers
BRKAGG-2002_c1
Cisco Public
New generation will influence new purchases and drive network traffic
BRKAGG-2002_c1
Cisco Public
BRKAGG-2002_c1
Cisco Public
Early Adopters
2008
Cross Chasm
Mass Market
2012
10
Femtocell Architecture
BRKAGG-2002_c1
Cisco Public
11
Fg/ tbd
Femto GW
Radio/ Uu
Mobile device
Fa/ Iuh
FL
Home GW
Fb-ps/ Iu-ps
PS core
SeGW
Fb-ims/ tbd
IMS core
HPLMN RAN
BRKAGG-2002_c1
Cisco Public
12
9 Low (5mW) output power (NWL) ) for auto 9 Network Listen ( configuration, interference management and location verification 9 Four simultaneous users 9 Up to 3.6Mbps HSDPA 9 Emergency call support
Fm
Fm
9 Provides secure DMZ for access controllers and management system 9 Provides single point of termination for signaling/ management security
9 Fully y redundant ATCA-based architecture (IP.Access) 9 Closed access control (initial rel) 9 Hand-in/Hand-out support g 20k HNB p per HNB 9 Scaling: Gw (initial rel)
Iuh Uu
BRKAGG-2002_c1
Cisco Public
13
Bearer Plane De- AAL2 Encap Jitter GTP Encap p Iu-cs Iu-ps
PDCP RRC R RANAP RLC MAC PHY Paging Control Access Control SRNC relocation to CN
Uu UE
BRKAGG-2002_c1
Cisco Public
MSC
3G AC
3G AP
UE
Functionality moved from RNC to Home Node-B Regular RANAP stack towards MSC persistent URSL connection AP and AC have a p URSL is an enhanced RANAP including HNB management procedures
*Pre-version of Iuh Protocol stack
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
15
Keepalives IPSEC
Keepalives IPSEC
Regular g Iu-CS stack towards MSC Keepalives layer is similar to session layer ensuring the IPSEC remains up all the time
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
16
Keepalives
Keepalives
IPSEC
IPSEC
Regular Iu-PS stack towards SGSN Standards seem to incline towards GTP-U encapsulation to start at AP
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
17
BRKAGG-2002_c1
Cisco Public
18
Consumer Services
Most macro services are offered through Femto
Voice Services D t Services Data S i Emergency Calls Messaging SMS,MMS SMS MMS Multi-RAB
BRKAGG-2002_c1
Cisco Public
19
Zero-touch Provisioning
Safely installing an operator owned Node B in the user environment
20
21
Network Listen
Network listen is a scan of radio environment by HNB which detects neighbor cells cells, their frequencies and transmit power levels levels. Network listen procedure allows the HNB to monitor surrounding 2G and 3G macrocell and femtocell layer. Results esu ts a are e used to se select ect a and d adjust t the e access related e ated pa parameters a ete s (frequency, power, scrambling code, neighbour list).
Invoke Frequency (re-)synchronization Measure noise power DL and UL Measure code powers Decode neighbor cell info
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
S l Select DL scrambling bli code d Update/ report hand-out neighbor g list; ; Select LAC & RAC Report nearby MCCs
22
Network Listen
Network Listen feature on the Home Node-B uses both 3G and 2G downlink receivers and signal processing chains for:
Fast synchronize the internal Home Node-B clock with any nearby macro cell frequency. Validate the Mobile Country Code (MCC) used by nearby cells to help in verification of the territory of operation. Check Interference levels on uplink & downlink for each operational permitted frequency. Decode the System y Information of nearby y Home Node-Bs as the basis for selecting LAC. Detect the scrambling codes used by nearby Home Node-Bs to help choose an optimal scrambling code for the location. Decode the System Information of nearby macro cells as the b i f basis for constructing t ti neighbor i hb li lists t i in th the H Home N Node-B. d B Estimate the noise power in the band, to set the Home Node-B transmit power.
Network Listen feature is a mode of the device i.e. when in NWL mode, Home Node-B is not providing service. Intelligent scheduling algorithms used to minimize service interruption.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
23
GPS
GPS chipset within HNB is authority for l location ti verification. ifi ti Since the GPS test can potentially take minutes to complete, NWL is preferred first. GPS results are passed back from HNB to Provisioning Pro isioning S System stem for comparison against Expected Lat/Long based on a tolerance value set. Restrictions: direct line of sight requirements to the sky.
BRKAGG-2002_c1
Cisco Public
24
Location Verification
HNB must pass Location Verification before it can be activated activated. Location Verification is the process of confirming the HNB (and radio) location is within a specified tolerance of its expected location. There are 2 primary steps in Location Verification:
Network Listen GPS
Location Verification is performed on boot/provisioning and also periodically (once per day) policies. E E.g. g Operators may define to set policies
Location Verification must pass before the HNB can be activated by the Provisioning system.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
25
Frequency Synchronization
Frequency synchronization of Home Node-B is required forsuccessful for successful handover processing and minimizing dropped sessions during handover, minimizing spectrum channel overlap to reduce channel co-interference, improve frame synchronization optimizing handover g delay y and user signal g j jitter. times, user signal 3GPP has relaxed the frequency accuracy for Femto to 250ppb. This would reduce synchronization related traffic. Cisco Home Node-B uses the following order to meet the pre-relaxed tolerance limit of 100ppb:
Network Listen for fast-lock frequency synchronization to macro network GPS lock and frequency synchronization (in the future releases) NTP for slow maintenance of frequency synchronization 24-hour holdover period of internal on-board oscillator for the stability.
In some cases depending on operators requirements, one of the above can be missed. missed Many operators may choose to not implement GPS lock feature which could be difficult inside a closed building.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
26
Info: UE States
When a UE is switched on, a PLMN is selected and the UE searches for a suitable cell of this PLMN, chooses that cell to provide available services, and tunes to its control channel. This choosing is known as camping on the cell. The Th UE will ill th then register i t it its presence b by means of Location Registration Update procedure. The UE then repeatedly searches for a better cell in terms of path loss to a cell site. If the UE is roaming away from its home network, the UE shall search for higher priority PLMNs at regular time intervals. If the UE finds a more suitable cell, it reselects onto that cell and camps on it. The UE in idle mode will perform camping, cell selection and reselection and Location Registration procedures. When the UE requires req ires to access ser services ices of the UMTS network, it establishes a RRC connection with the serving RNC and is in connected mode.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
27
If not accepted by the Femto, a UE may still camp on the cell (in the absence of surrounding macro coverage) and then be able to establish emergency calls. LU Reject is used in such scenario.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
28
Interference Management
Minimize Interference: Femto-to-Macro (non-femto user femto user, user, user reselect) reselect), Femto-to-Femto Femto to Femto, UE performance Factors affecting interference:
Open or Closed Access Unauthorized femto user should be able bl to access M Macro i in close l f femto vicinity i i i Dedicated channel or Co-channel same or distinct carriers Power control (adaptive or fixed)
For an effective femtocell deployment, deployment interference management shall be done automatically. Factors for Home Node-B transmit power:
Power is too high: g there is effectively y a macro dead zone around the Home Node-B. Power is too low: femto coverage will be poor and femto UEs may not reselect the femtocell itself.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
29
Interference Management
Both 3GPP RAN WG4 and Femto Forum, recognizing questions which needs to be that one of the serious q answered is the RF interference of Femto with the Macro, have embarked on studies for RF Interference. Summary from these studies is that femto and macro p with the networks can co-exist and cooperate incorporation of proper power management techniques that are already becoming available in the industry. Following is a quick list of those features:
Adaptive Attenuation or Automatic Gain Control (dynamic receiver gain management in the femto) ensures that femtocell can offer good service to both near and far UEs without unnecessarily increasing the UE transmit power, therefore keeping the noise rise contribution to a minimum. Power capping of the UE when operating in the femto environment ensures that even in difficult radio conditions, the UE hands-off to the macro network before its transmit power increases to the point where macro noise rise is a problem. Downlink Power Management femtocell to dynamically adjust its transmit power by measuring its environment or for required cell coverage area. I Increased dR Receiver i D Dynamic i R Range to accommodate d f femto operation reliably even in the presence of nearby non-allowed high power UE. This has already been incorporated into the latest 3GPP Release-8 25.104 specification.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
30
Info: Measurements
UTRAN may control a measurement in the UE either by broadcast of SYSTEM INFORMATION and/or by transmitting a MEASUREMENT CONTROL message. Common Pilot Channel (CPICH) is used to enable channel estimation. CPICH uses a pre defined bit sequence at a fixed rate and allows the UE to estimate power measurements. The different types of measurements are:
Intra-frequency measurements - measurements on downlink physical channels at the same frequency f as the th active ti set t Inter-frequency measurements - measurements on downlink physical channels at frequencies that differ from the frequency of the active set and on downlink physical channels in the active set Inter-RAT measurements - measurements on downlink physical channels belonging to another radio access technology than UTRAN, e.g. GSM T ffi volume Traffic l measurements t - measurements t on uplink li k t traffic ffi volume l Quality measurements - measurements of downlink quality parameters, e.g. downlink transport block error rate UE-internal measurements - measurements of UE transmission power and UE received signal level UE positioning measurements - measurements of UE position.
Since the WCDMA system requires continuous transmission and reception, the UE measurements on different frequencies or different systems, e.g., GSM, requires UTRAN to command that the UE enters in compressed mode. When the UE is in compressed p mode, , the transmission and reception p are stopped pp for a short duration to take the measurements. To ensure the data is not lost, the data is compressed in the frame making an empty space where measurements are performed.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
31
Info: Handover
The simplest definition of handover is the transfer of a ( users connection from one radio channel to another (can be same or different cell). It is important to note that the handover procedure comes into effect when the RRC connection is established i.e. a call is in progress. Following is a list of different scenarios for handoff that are manifested: if t d
Intra Node-B intra-cell (softer), inter-cell (soft) Inter Node-B intra-RNS, inter-RNS with Iur interface (soft or hard handover), inter-RNS (hard handover) Inter Core Network when the two radio are part of two different core net ork network Inter-URAN (handover from UMTS to GSM BSS, GERAN or other RAN network) intra core network or inter core network During a soft (or softer) handover, the UE is connected to at least one radio cell at every instance. This requires an optimal combining of physical p y layer y data collected from UE through g two ( (or one) ) node-Bs, , and the transmission of the same physical layer data through two (or one) node-Bs to the UE. In case of soft handover, if the two node-Bs are in different RNC, such recombining requires a real-time interface (Iur) between the serving and target RNCs. Hard handover occurs when there is no common radio link between the source and target networks or where the architecture does not support soft handover, e.g., GSM, HSDPA or WCDMA in the cell-FACH state. In hard handover the radio connection gets broken between the UE and source network before a new radio connection is established with the target network.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
32
For Hand-out, neighbor macro cells list (2G or 3G) is created after Network Listen (NWL). Same list used for cell ll reselect. l t For Hand-in, a dummy Femto id which is common for all Femto under the same HNB Gw and LAC/RAC is g in the macro network configured
Hand-in request are directed to the HNB Gw which performs access control and IMSI-based filtering to find the targeted Femto in the LAC Note that a high number of Femtos will likely be associated to a single LAC and that a user may be associated to multiple Femtos. Femto gateway requests all matching candidate APs to send out a beacon signal on the downlink sync channel to which the UE responds with an uplink sync on the correct hand-in candidate AP.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
33
Since the hard handover is supported, the handover between Femto and 3G macro or 2G macro will ill b be similar i il except t th the RAN network t k will ill be either UTRAN for 3G or BSS or GERAN for 2G.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
34
QoS requirements:
Delay: RTT < 300 ms to preserve voice quality. Max 100ms one-way recommended. Jitter: 30ms rolling average for CS; buffering capable of holding 100msec of data at the RAB rate for PS PS. Packet Loss: Connection can operate reliably at up to 1% packet loss. For CS (i.e. AMR), speech quality can be preserved with up to 3% packet loss
IP addressing dd i requirement i t
Public/Private IP address support at the HNB. NAT traversal required.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
35
36
ISP
SSL
Cisco HNB
Home Gateway Cisco 7609 with SSL termination (ACE) and Firewall (FWSM) IPSec termination (SAMI) Cisco BAC (DPE) Statistics Server (OAM)
Home Premises
SP Regional/Central PoP
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
37
Plug-n-Play installation
Automatic discovery of the provisioning system Activation procedure requiring strong integration work prior to deployment No macro network reconfiguration at new HNB activation
38
BRKAGG-2002_c1
Cisco Public
39
Emergency Call
Location of the UE making an emergency call ll can b be id identified tifi d using i th the SAI of f th the cell where the call was made. The coverage of the femtocell is within ~150ft. Access Control is not applied for emergency calls, following could be the two cases:
An emergency call for a UE that has camped on to the Home Node-B for emergency calls only in the absence of macro coverage of the APs Home PLMN. (Such a UE will have been LUrejected by Access Control when it attempted to register.) An emergency call A ll f for a SIM SIM-less l UE UE. (N (Note t th that t such a UE will not have attempted to register previously but may have silently camped on.)
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
40
Split tunneling of local-identified traffic is required at the AP thus creating potential security breach in the architecture Overall local breakout requires further study and will not be part of first 3GPP standardised H(e)NB architecture
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
41
BRKAGG-2002_c1
Cisco Public
42
HNB Register/Activate
HNB
IPSEC
IPSEC
IPSEC
Connection Request
Note: within the above flow, if the location verification process failed to match within a specified tolerance, a ToleranceFailure message would be sent. At that point, the provisioning process would require intervention from Ops to determine whether to Activate the HNB.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
43
BRKAGG-2002_c1
Cisco Public
44
BRKAGG-2002_c1
Cisco Public
45
RRC_Downlink_Direct_TRansfer( CN_Domain, MM-Identity Request (IMSI) RRC_Uplink_Direct_Transfer CN Domain MM-Identity CN_Domain, MM Identity Response)
Access Control
URSL_ Initial_Direct_Transfer (Loc Upd Req) SCCP_Connection_Request(RANAP_ Initial_UE_Message(LUREQ)) SCCP_Connection_Confirm() URSL_ UplinkDirect_Transfer (MM_null) RANAP_Direct_Transfer (MM-Null)
RANAP_Downlink_Direct_Transfer (LUACC)
BRKAGG-2002_c1
Cisco Public
46
RRC_ Initial_Dire ct_Transfer(CM Service Re quest) RRC_Downlin k_Dire ct_Transfer( CN_ Domai n MM_Identity_Req uest (IMSI))
RRC_Upli nkl _Di rect_Transfer(CN_Do main MM-Identity main, MM Identity_Respon Respon se)
URSL_Home_ LAC(IMS I, LA C)
RRC_Upli nkl _Di rect_Transfer(CN_Do main, User_A uth _Reject(S ync Failure))
Loop x3
BRKAGG-2002_c1
Cisco Public
47
URSL_Home_LA C_ Re q ( IMSI)
BRKAGG-2002_c1
Cisco Public
48
BRKAGG-2002_c1
Cisco Public
49
BRKAGG-2002_c1
Cisco Public
50
BRKAGG-2002_c1
Cisco Public
51
Provisioning
Forced
BRKAGG-2002_c1
Cisco Public
52
Standards Update
BRKAGG-2002_c1
Cisco Public
53
Organised in working groups covering service requirements (wg1), radio and interference management (wg2), network architecture (wg3) and legal issues (wg4)
Mobile Service Providers organisation defining deployment guidelines and interoperability procedures
www.gsmworld.com
Defining standards for 3G W-CDMA and SAE/LTE Femtocell services and architecture
Objective is to reuse TR-069 framework for zero-touch provisioning of Femtocell Access Point
54
Femtoforum Activities
Defined Femtocell requirements (including end user, OAM, Security, integration, etc.) Focus on enabling femto industry:
Interference management (covering multiple scenarios) Business Requirements Homezone services, services taking advantage of presence presence capabilities of Femto Enterprise Femto
Feature focus:
Local breakout support Architecture evolution (IMS integration) Legal and regulatory requirements
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
55
3G HNB GW
3G HNB
Full standardization will likely span p two 3GPP releases: R8 and R9 3GPP R8 adopts RAN-based architecture Home Node B Technical Report on RAN aspects completed (3G TR 25.820)
Focus on Radio related aspects (interference, power control, etc.)
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
3G HNB
3G HNB GW
3G HNB
I h Interface Iuh I t f
Iu Interface
56
Handover scenarios
Macro to/from Femto, Femto to Femto
Security impacts Addresses attack scenarios for H(e)NB (brute , eavesdropping, pp g, sw manipulation, p , etc.) ) force attack,
ftp://ftp.3gpp.org/tsg_sa/WG3_Security/TSGS3_52_Sophia/Docs/S3-080608.zip
57
BRKAGG-2002_c1
Cisco Public
58
UMA/Dual Mode
Yes No Yes
Femtocell
Phone needs to be within femtocell range, and *might* be locked to a residence or location Yes Yes Yes Yes/Eventually Better Voice and Data
Licensed Radio Enables Quad Play New Family/Zone plans Integration into SIP/IMS Core Battery Life Bearer
No Yes Yes UMA Generally No Dual-Mode - Yes Not as good Primarily Voice
59
BRKAGG-2002_c1
Cisco Public
60
Public Internet
BRKAGG-2002_c1
Cisco Public
61
Call Signaling g g
2G/3G MSC
2G Pico
SMB LAN Internet
A/ Iu-cs
Enterprise User
3G Pico
EFR/AMR Voice GW
Media
Femto/Residential
Connected Home premise based integration
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
Super p Femto/Enterprise p
Managed Service/Unified Communications premise based integration
62
Cisco HNB
Standalone Femto HNB
I t Integrated t d with ith DSL gateway t or STB planned l di in f future t release l
3G R6 Radio compliant
UMTS Band I, II and V support Single carrier with up to 5mW (7dBm) output power CS and PS support ; up to 3.6Mbps HSDPA (7.2Mbps and 1.4Mbps HSUPA in next release)
Service mix
Four simultaneous user service limit: Multi-RAB CS/PS combinations per user Emergency call support (RANAP SAI handling)
Backhaul capability
Secure transport (IPSec tunnel), NAT traversal, bandwidth management)
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
63
Engines
Route Switch Processor 720
S Chassis SeGW
Scalable IPsec Termination 7609-S, 7606-S, 7603-S, 7604
Services Modules
Firewall, IDS, SSL termination, termination Load Balancing
Traditional Chassis
7606, 7609, 7613
BRKAGG-2002_c1
Cisco Public
64
HNB Gateway
Femtocell Access Control
Cl Closed dA Access C Control t lb based d on a li list t of f authorized th i d IMSI Open Access Control planned in subsequent release (assessing impact on performance)
Handover capabilities
Si l Simultaneous h hard dh handover d and d SRNS relocation l i Outgoing to Macro (2G, 3G)Based on identified neighbour cell list Incoming from Macro Femto-femto handover not supported initially (targeted for Picocell deployment)
Performance Figures
20k Femtos per HNB Gw (to be enhanced in future) 5200 voice/video call Erlangs (90s hold time, 60 cps, 60 LUs/s) 1Gbit/sec PS traffic
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
65
66
67
Unmanaged NATs, NAT s, limited uplink, unsecure IP links, and problematic and Untrusted home IP networks do not impact system performance ISP Network and Home IP Network Automated (Zero Touch) CPE Many Each endpoint gets registered, located for E911 and macro cell handoff, provisioned, and managed automatically (with exceptions flagged as alarms) Low price, with custom per carrier modifications, and rapid innovation of CPE products Integration with Video STB, PVR, Satellite, Second Line Voice, WiFi, and Home Media Gateway over time
Provisioning
BRKAGG-2002_c1
Cisco Public
68
Femto Integration
BRKAGG-2002_c1
Cisco Public
69
Iuh Integration
Routing & Switching Internet Routing (BGP) with Internet Provider Aggregation Router for the site VRF-Lite for Internet Routing and OAM Q S / CoS QoS C S Management M t Security IPSEC Stateful firewall Intrusion Prevention (optional) Tunnel termination CA Server, Certificates, Certificate Verification, CRL DSCP Marking of tunnel traffic Load Balancing Management Security Load-balancing of servers, SeGW farm SSL Offload for server traffic Control Plane Policing
BRKAGG-2002_c1
Cisco Public
70
SS7
RAN
Iu-PS: ATM
SS7 RAN
RANAP / ALCAP / Bearer VCs Class of Service and Parameters RANAP / ALCAP Point Codes for SGSN Point Code for Femto Gateway MCC, MNC RAC, LAC
IP Addressing
BRKAGG-2002_c1
71
OSS Integration
Hexagonal maps of county/market LAC, RAC for Femto LAC, RAC for Macro New AP addition, deletion User MSISDN, MSID changes Friends list
E911
Location Identification
BRKAGG-2002_c1
Cisco Public
72
Summary
BRKAGG-2002_c1
Cisco Public
73
Summary
Operators looking to offload/complement their Macro with ith Femto F t to t provide id Mobile M bil I Internet t t to t indoor i d users Standard bodies bodies, 3GPP and Femto For Forum, m ha have e churned major interest. RAN-Gateway approach by 3GPP makes it easier to integrate with Macro. Femto Success = Seamless Integration with Macro + Auto Provisioning / Self Optimizing Auto-Provisioning Femto trend continues with LTE Femto and Super Femto interests.
BRKAGG-2002_c1 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
74
References
3GPP Standards http://www.3gpp.org 3GPP Standards http://www.3gpp.org/femto TR-069 with CPE WAN Management g Protocol proposed as a framework http://www.broadbandforum.org/technical/download/TR-069Amendment2.pdf
BRKAGG-2002_c1
Cisco Public
75
Dont forget f to activate your Cisco Live Virtual account for access to all session material, communities, and on-demand and live activities throughout the h year. A Activate i your account at the h Cisco booth in the World of Solutions or visit www.ciscolive.com.
76
BRKAGG-2002_c1
Cisco Public
BRKAGG-2002_c1
Cisco Public
77