3GPP2 TSG-S WG2 Plans for Femto Management

1. 3GPP2 TSG-S WG2Plans for Femto Management Randall J. Scheer (Co-chair) rjscheer@alcatel-lucent.com

2. 3GPP2 TSG-S WG2Specifications • 3GPP2 TSG-S WG2 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 • Provides standard performance measurement definitions • Reuses 3GPP SA5 management specifications whenever appropriate • Management interfaces below the EMS are considered proprietary and are not standardized (though the data required to be sent to and from the EMS may be standardized) • In 3GPP2, management billing interfaces are covered under TSG-X

3. Two Levels of FemtoManagement • NMS view of Femto (WG2 scope): • Alarms • Security alarms • State (based on ITU-T state model) • Read-only parameters • Read-write parameters (very few, if any) • Performance measurements • Operator / customer view of Femto (outside WG2 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

4. Femto Management

5. 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 • The Femto Network Gateway has the responsibility to protect the OAM&P network from data flooding initiated from Femtos (i.e., OAM&P DoS protection)

6. The NMS wants to be able to… • Receive Femto network alarms, security alarms and performance measurements meeting 3GPP / 3GPP2 guidelines and formats • Determine if a Femto is in service or out of service • Determine the network resources being used by a particular Femto • Take a particular Femto out of service / into service • Understand which Femto Network Gateway(s) are responsible for which Femtos • Distinguish each Femto network entity from all others • Limit privacy concerns from Femto network data • As an example, Femto latitude and longitude data could be considered private or a security risk • Automatically discover additions and deletions of Femtos • Allow Femto support to be transferred between Femto Network Gateways without loosing Femto information

7. The NMS does not want to … • Control the low level of details of the potentially large volume of Femtos • Understand all of the Femto attributes • Allocate Femtos to particular Femto Network Gateway(s) • Provision Femtos • Initiate software updates / firmware downloads / diagnostics or receive results of them • Have the Femto network OAM&P data overwhelm the NMS

8. 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?)

9. Early Femto Management Model