3GPP2 TSG-S WG5 femto Management Notes

3GPP2 TSG-S WG5 femto Management Notes Randall J. Scheerrjscheer@alcatel-lucent.com

3GPP2 TSG-S WG5Specifications • 3GPP2 TSG-S WG5 works on management specifications for CDMA / cdma2000 interfaces between Element Management Systems (EMS) and Network Management Systems (NMS) • Provides standard interfaces for: • Alarms / security alarms / state changes / notifications • Performance measurements • Provisioning data [when modeled] • Etc. • Provides Network Resource management models for CDMA / cdma2000 networks • Reuses 3GPP SA5 management specifications whenever appropriate • Management interfaces below the EMS are considered proprietary and are not standardized • In 3GPP2, management billing interfaces are covered under TSG-X

Two Levels of FemtoManagement • NMS view of Femto (WG5 scope): • Alarms • Security alarms • State (based on ITU-T state model) • Read-only parameters • Read-write parameters • Performance measurements • Operator / customer view of Femto (outside WG5 scope): • Diagnostics • Customer provisioning • Firmware downloads • Software updates • Alarms / Security alarms / State information / Performance measurements • Not clear which organization owns the specification of the second management area

Femto Management

Femto Network GatewayManagement Responsibilities to EMS • Femto (and Femto Network Gateway) alarm, security alarm, state collection, storing and forwarding to EMS • Femto (and Femto Network Gateway) performance measurement collection, storing and forwarding to EMS • Collection, storage and transmission of Femto provisioning parameters to and from the NMS (when modeled) • Read/write attributes changed by the NMS will be transferred to the EMS, then to the Femto Network Gateway and onto the Femto • Read only and read/write attributes transferred from Femto / Femto Network Gateway to the EMS and onto the NMS

Femto Management ModelObjects • Femto • Femto Network Gateway (FngFunction) • Call Manager (CmFunction) • Reference Point F1 (Link_Femto_Fng) • Reference Point F2 (actually M1 reference point) • Reference Point F3 (Link_Aaa_Fng) • Reference Point F4 (Link_Cm_Fng) • Reference Point A (Link_Cm_Msc) • Reference Point Aquater (Link_Cm_Pdsn) • Reference Point F5 (control? bearer?) • Reference Point F6 (control? bearer?)

Femto Management Model

Questions • Need to understand whether a Femto can be fed from more than one Femto Network Gateway: • As an example, for geographical redundancy / higher availability solutions • Is there information sharing between Femto Network Gateways? Is a new reference point needed? • Need to understand how IPSec is initiated the first time between the Femto and Femto Network Gateway • Need to understand the IPSec parameters and support (IPSec provisioning): • IKE? • transport or tunnel mode? • key revocation? • Need to understand the Femto Network Gateway Denial of Service (DoS) protections from malfunctioning Femto • Need to understand which Femto provisioning parameters need to be made visible / modifiable through NMS interface: • Typically, expect company contributions to identify any NMS visible parameters • Need to understand how the control for a particular Femto is transferred from one Femto Network Gateway to another: • Transfer could occur based on capacity issues or customer changing operator • Who makes this decision? • Will there be information transfer between the Femto Network Gateways? • Need to understand how a Femto needs to act if more than one Femto Network Gateway (with valid security parameters) try to communicate with the Femto • Need to understand whether we will allow the NMS to take a Femto out of service? • Need to understand whether separate control and management channels are required between Femto and Femto Network Gateway • As a DoS protection

Comments on February 20083GPP2 S.R0tbd-0 version 0.0 • When you review the S.R0037-B v1.0 specification, the bearer and control reference points are separated into separate reference points (as an example, see reference points 41 and 43/Mb). This makes sense, because, in general, different network elements handle the signaling and bearer channel traffic. Unless it is a requirement that bearer and control traffic be intermixed on the same channel, this specification needs to separate control / signaling and bearer traffic into different reference points. In particular, look at F1, F2, F4, F5 and F6. • It appears the F2 is a duplicate reference point to the already defined reference point M1. I would expect that the Call Manager also has a M1 reference point. • Under Reference Point F2, there is no such thing as OAM&P signaling and bearer traffic. All OAM&P traffic, such as alarms, are transmitted over management channels, not control or bearer channels. • Need specific network elements specified for Reference Point F6 communication. The F6 reference point needs to explicitly interface with a specific network element in the IMS core network.. I believe that there must be two separate reference points, one for control and one for bearer, and that they would go to different network elements. We need to explicitly list all of the IMS components that can be connected to the control and bearer, it may be more than two. Management models have to be explicit for what interfaces are supported between network entities. • Need specific network elements specified for Reference Point F5 communication. Need to specify different reference points for control and bearer. • The Aquarter Reference Point should be between the Call Manager and a PDSN in pictures (as in 3GPP2 S.R0005-B v.2.0) • Does all management communication, including management communication, between the Femto and Femto Network Gateway get transmitted over signaling / control Reference Point F1? If not, there needs to be a separate management reference point. • In section 3.1, it states that Reference Point F5 communicates with the MSC. Is the bearer traffic sent to a MGW? Similar question to Call Manager in section 3.2 and Reference Point A.

Other Notes • Femto Network Gateway communication to Femto on provisioning and radio parameters are typically considered control / signaling communication and not management communication • Consider specifying Femto / Femto Network Gateway performance measurements when designing call flows / management flows / accounting flows

3GPP2 TSG-S WG5 Background

3GPP2 Structure 3GPP2 Steering Committee TSG-X (TSG-N / TSG-P) TSG-A TSG-C ANSI-41 / WIN Wireless Packet Data Interworking A-Interface System cdma2000 Air Interface Technical Specification Groups (TSG’s) TSG-S Service and System Aspects WG1 – Features & Services Requirements WG2 – Architecture WG3 – Program Management WG4 – Security WG5 – OAM&P

3GPP2 Organization Information • Upcoming 3GPP2 TSG-S meetings: • Meeting calendar: http://www.3gpp2.org/Public_html/Cal/index.cfm • 3GPP2 Info: • 3GPP2: http://www.3gpp2.org • 3GPP2 Organizational Partners: • ARIB, CCSA, TIA, TTA, TTC • Current member companies: http://www.3gpp2.org/Public_html/Misc/MembersHome.cfm • 3GPP2 Specifications: http://www.3gpp2.org/Public_html/specs/index.cfm • 3GPP2 TSG-S Contributions: ftp://ftp.3gpp2.org/TSGS/Working/

3GPP2 OAM&P Specifications • Delta Specifications: • S.S0028-0 “OAM&P for cdma2000 (3GPP R99 Delta Specification)” • S.S0028-A “OAM&P for cdma2000 (3GPP R4 Delta Specification)” • S.S0028-xxx-B: • S.S0028-000-B: " OAM&P for cdma2000 (Overview)"; • S.S0028-001-B: " OAM&P for cdma2000 (3GPP R5 Delta Specification)"; • S.S0028-002-B: " OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; • S.S0028-003-B: " OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; • S.S0028-004-B: " OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; • S.S0028-xxx-C (v2.0): • S.S0028-000-C: " OAM&P for cdma2000 (Overview)"; • S.S0028-001-C: " OAM&P for cdma2000 (3GPP R6 Delta Specification)"; • S.S0028-002-C: " OAM&P for cdma2000 (3GPP2 Generic NRM IRP)"; • S.S0028-003-C: " OAM&P for cdma2000 (3GPP2 Core NRM IRP)"; • S.S0028-004-C: " OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)"; • S.S0028-D (draft): • S.S0028-D: " OAM&P for cdma2000 (Overview, 3GPP R7 Delta Specification, 3GPP2 Network Resource Model IRP)"; • S.R0017-0: • “3G Wireless Network Management System High Level Requirements” • S.P0093-0: • “CDMA2000 Network Performance Measurement Types”

3GPP2/3GPP “Delta” Relationship Alignment ! TSG-SA5 TSG-S WG5 • 3GPP SA5 defines standard northbound interfaces based on Integration Reference Point (IRP) methodology • 3GPP2 re-uses 3GPP’s Interface IRP’s as well as the Generic portion of the NRM IRP’s – and is adding CDMA/CDMA2000 NRM IRP’s • One set of northbound interface standards for all 2G, 3G, 4G and future wireless technologies!

3GPP2 S.S0028-xxx-C/D: What … • What it is: • A Delta specification: • Incorporation 3GPP SA5 Specifications by reference • Defining exceptions and additions (“delta’s”) as applicable to cdma2000 • Providing cdma2000 specific specifications (e.g. 3GPP2 NRM IRP’s) • What is included: • 3GPP SA5 R6 / R7 Specifications: • Requirements & Architecture (32.101, 32.102, 32.15x) • CM Requirements (32.600) and Naming Conventions (32.300) • Interface IRP’s: See later viewgraphs • NRM IRP’s: See later viewgraphs • PM Concept and Requirements (32.40x): • not including 3GPP-specific performance measurements • 3GPP2 NRM IRP’s: • 3GPP2 Inventory NRM IRP (CORBA only) • 3GPP2 Generic NRM IRP • 3GPP2 Core Network NRM IRP • 3GPP2 Radio Access Network (RAN) NRM IRP

IRP Concept – Build to last … and to cope with change Relative stable over long period of time Requirements / Use Cases IS Definition (UML) • Data Def IRP’s • State Management IRP • Interface IRP’s • Notification IRP • Alarm IRP • BulkCM IRP • KernelCM IRP • BasicCM IRP • PM IRP • … Changes only with respect to addition and extensions • NRM IRP’s • Generic NRM • CoreNW NRM • UMTS NRM’s • CDMA NRM’s Changes with new/better Technologies Solution Set Definitions (CORBA) Solution Set Definitions (CMIP/XML/RMI/SOAP/other)

IRP Development Principles • Interface IRP & NRM IRP Independence • Interface IRP’s: Defining HOW Information is shared (Operations & Notifications) • NRM IRP’s: Defining WHAT can be managed (Object Models) • Enabling: Independent development as well as reusable across the industry • NRM IRP Extendibility • vsDataContainer • Rule-based NRM Extensions • Enabling: Technology & vendor specific NRM extensions (3GPP2 NRM’s are technology-specific NRM extensions !!) • Interface IRP Flexibility • Flexible use of qualifiers “mandatory”, “optional”, “visibility” for operation, notifications and/or parameters • NRM/Technology-neutrality & avoiding competing procedures • Enabling: wide applicability, phased introduction capabilities & broad industry adoption (not just for wireless !!)

3GPP SA5 Interface IRP’s • Fault Management: • Alarm IRP (32.111-x) • Test Management IRP (32.32x) • Trace Management IRP (32.44x) [R7] • Configuration Management: • Basic CM IRP (32.60x) • Bulk CM IRP (32.61x) • Kernel CM IRP (32.66x) • Security Management: • Security Management (32.37x) • Performance Management: • Performance Management IRP (32.41x) • Common: • Notification IRP (32.30x) • Generic IRP Management (32.31x) • Notification Log IRP (32.33x) • File Transfer IRP (32.34x) • Communications Surveillance IRP (32.35x) • Entry Point IRP (32.36x) • Partial Suspension of Itf-N IRP (32.38x) [new in R7] • Delta Synchronization IRP (32.39x) [R7] [not supported in 3GPP2 in red]

3GPP SA5 and 3GPP2 NRM IRP’s • 3GPP Common: • Generic NRM IRP (32.62x) • Inventory Management IRP (32.69x) • Signaling Transport Network Interface NRM IRP (32.74x) • State Management IRP (32.67x) • IMS NRM IRP (32.73x) [new in R7] • 3GPP2 Specific: • 3GPP2 Inventory NRM IRP (CORBA only) • 3GPP2 Generic NRM IRP • 3GPP2 Core Network NRM IRP • 3GPP2 Radio Access Network NRM IRP • 3GPP Specific: • 3GPP Core NRM IRP (32.63x) • 3GPP UTRAN NRM IRP (32.64x) • 3GPP GERAN NRM IRP (32.65x) • 3GPP Subscription Management NRM IRP (32.14x, 32.17x) • 3GPP Subscriber and Equipment Trace (32.42x) • Transport Network Interface NRM IRP (32.71x) • Repeater NRM IRP (32.72x) [R7] [not supported in 3GPP2 in red]

3GPP2 TSG-S WG5 femto Management Notes