Plans for Femto Management 3GPP2 TSG-S WG2 Plans for Femto Management Randall J. Scheer (Co-chair)

1 Plans for Femto Management – July 21, GPP2 TSG-S WG2 Specifications 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 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

2 Plans for Femto Management – July 21, 2008 Two Levels of Femto Management NMS view of Femto (WG2 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 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

3 Plans for Femto Management – July 21, 2008 Femto Management

4 Plans for Femto Management – July 21, 2008 Femto Network Gateway Management 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

5 Plans for Femto Management – July 21, 2008 Femto Management Model Objects 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?)

6 Plans for Femto Management – July 21, 2008 Femto Management Model

7 Plans for Femto Management – July 21, 2008 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

8 Plans for Femto Management – July 21, 2008 Comments on February GPP2 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.

9 Plans for Femto Management – July 21, 2008 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