TECHNICAL REPORT TR-196 Femto Access Point Service Data Model Issue: 2 Issue Date: November 2011 © The Broadband Forum. All rights reserved. Femto Access Point Service Data Model TR-196 Issue 2 Notice The Broadband Forum is a non-profit corporation organized to create guidelines for broadband network system development and deployment. This Broadband Forum Technical Report has been approved by members of the Forum. This Broadband Forum Technical Report is not binding on the Broadband Forum, any of its members, or any developer or service provider. This Broadband Forum Technical Report is subject to change, but only with approval of members of the Forum. This Technical Report is copyrighted by the Broadband Forum, and all rights are reserved. Portions of this Technical Report may be copyrighted by Broadband Forum members. This Broadband Forum Technical Report is provided AS IS, WITH ALL FAULTS. ANY PERSON HOLDING A COPYRIGHT IN THIS BROADBAND FORUM TECHNICAL REPORT, OR ANY PORTION THEREOF, DISCLAIMS TO THE FULLEST EXTENT PERMITTED BY LAW ANY REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY: (A) OF ACCURACY, COMPLETENESS, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE; (B) THAT THE CONTENTS OF THIS BROADBAND FORUM TECHNICAL REPORT ARE SUITABLE FOR ANY PURPOSE, EVEN IF THAT PURPOSE IS KNOWN TO THE COPYRIGHT HOLDER; (C) THAT THE IMPLEMENTATION OF THE CONTENTS OF THE TECHNICAL REPORT WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. By using this Broadband Forum Technical Report, users acknowledge that implementation may require licenses to patents. The Broadband Forum encourages but does not require its members to identify such patents. For a list of declarations made by Broadband Forum member companies, please see http://www.broadband-forum.org. No assurance is given that licenses to patents necessary to implement this Technical Report will be available for license at all or on reasonable and non-discriminatory terms. ANY PERSON HOLDING A COPYRIGHT IN THIS BROADBAND FORUM TECHNICAL REPORT, OR ANY PORTION THEREOF, DISCLAIMS TO THE FULLEST EXTENT PERMITTED BY LAW (A) ANY LIABILITY (INCLUDING DIRECT, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES UNDER ANY LEGAL THEORY) ARISING FROM OR RELATED TO THE USE OF OR RELIANCE UPON THIS TECHNICAL REPORT; AND (B) ANY OBLIGATION TO UPDATE OR CORRECT THIS TECHNICAL REPORT. Broadband Forum Technical Reports may be copied, downloaded, stored on a server or otherwise re-distributed in their entirety only, and may not be modified without the advance written permission of the Broadband Forum. The text of this notice must be included in all copies of this Broadband Forum Technical Report. November 2011 © The Broadband Forum. All rights reserved 2 of 46 Femto Access Point Service Data Model TR-196 Issue 2 Issue History Issue Number Issue Date Issue Editor Changes 1 April 2009 Taka Yoshizawa, Technicolor Original John Blackford, 2Wire Heather Kirksey, Alcatel-Lucent 1 Amendment 1 May 2011 Klaus Wich, Defines Nokia Siemens Networks FAPService:1.1 with updates to Service Model for 3GPP release 9 and 10. New Theory of operations included. 2 November 2011 Klaus Wich, New Femto Access Nokia Siemens Networks Point Service Data Model (FAPService:2) defining UMTS, LTE and CDMA2000 FAP radio models. Comments or questions about this Broadband Forum Technical Report should be directed to [email protected]. Editor Klaus Wich Nokia Siemens Networks BroadbandHome™ WG Greg Bathrick PMC-Sierra Chairs Jason Walls UNH Chief Editor Michael Hanrahan Huawei Technologies November 2011 © The Broadband Forum. All rights reserved 3 of 46 Femto Access Point Service Data Model TR-196 Issue 2 TABLE OF CONTENTS EXECUTIVE SUMMARY .......................................................................................................... 7 1 PURPOSE AND SCOPE ...................................................................................................... 8 1.1 PURPOSE .......................................................................................................................... 8 1.2 SCOPE .............................................................................................................................. 8 2 REFERENCES AND TERMINOLOGY ............................................................................ 9 2.1 CONVENTIONS ................................................................................................................. 9 2.2 REFERENCES .................................................................................................................. 10 2.3 DEFINITIONS .................................................................................................................. 11 2.4 ABBREVIATIONS ............................................................................................................ 11 3 TECHNICAL REPORT IMPACT ................................................................................... 13 3.1 ENERGY EFFICIENCY ...................................................................................................... 13 3.2 IPV6 ............................................................................................................................... 13 3.3 SECURITY ....................................................................................................................... 13 4 DATA MODEL DEFINITION .......................................................................................... 14 5 FAPSERVICE:2 PARAMETER DEFINITIONS ........................................................... 16 ANNEX A: REQUIRED CPE METHOD IN OPTIONAL RPC MESSAGES ................. 17 ANNEX B: VENDOR SPECIFIC TYPE DEFINITIONS .................................................. 18 B.1 VENDOR SPECIFIC FILE TYPE ......................................................................................... 18 B.2 VENDOR SPECIFIC EVENT TYPES ................................................................................... 18 ANNEX C: URN DEFINITIONS FOR APP AND FLOW TABLES ................................ 20 C.1 PROTOCOL IDENTIFIER ................................................................................................... 20 C.2 FLOW TYPE .................................................................................................................... 20 APPENDIX I. STRUCTURE OF FEMTO DATA MODEL ............................................... 21 I.1 STRUCTURE .................................................................................................................... 21 I.2 EXAMPLES ..................................................................................................................... 22 I.2.1 Single radio UMTS FAP device based on TR-098.................................................... 22 I.2.2 Single radio LTE FAP device based on TR-181i2 .................................................... 23 I.2.3 Multiple radio UMTS/CDMA200 multiple service FAP device based on TR-098 ... 24 I.2.4 Multiple radio UMTS/CDMA2000 single service FAP device based on TR-181i2.. 25 APPENDIX II. THEORY OF OPERATION FOR UMTS FEMTO ACCESS POINTS .... 26 II.1 MANAGEMENT CONNECTION ESTABLISHMENT ........................................ 27 II.2 SECGW, FAPGW DISCOVERY AND CONNECTION ESTABLISHMENT .... 29 II.3 LOCATION VERIFICATION .................................................................................. 31 November 2011 © The Broadband Forum. All rights reserved 4 of 46 Femto Access Point Service Data Model TR-196 Issue 2 II.4 SELF-CONFIGURATION ........................................................................................ 32 II.1.1 General Description.............................................................................................. 32 II.1.2 General Approach to Self-Configuration.............................................................. 32 II.1.3 General Process Flow........................................................................................... 33 II.1.4 Use of “Active Notification” ................................................................................. 33 II.1.5 Default Values ....................................................................................................... 34 II.1.6 Discovery of Device Capabilities and Activation of Self-Configuration .............. 34 II.1.7 Deactivation of Self-Configuration ....................................................................... 35 II.1.8 Self-Configuration Operation ............................................................................... 36 II.5 RADIO ENVIRONMENT MEASUREMENT (REM) PROCESS ........................ 37 II.5.1 Execution of REM ................................................................................................. 37 II.1.9 Configuration of Periodic Measurement .............................................................. 38 II.1.10 Configuration of Selective Measurement .............................................................. 38 II.1.11 Storage and Retrieval the Measurement Result .................................................... 39 II.6 NEIGHBOR LIST CONFIGURATION................................................................... 40 II.1.12 Fixed-configuration .............................................................................................. 40 II.1.13 Self-configuration ................................................................................................. 42 II.7 STATE MANAGEMENT