TIA-1188-2012 Femtocell Configuration Parameter《Femtocell配置参数》.pdf

《TIA-1188-2012 Femtocell Configuration Parameter《Femtocell配置参数》.pdf》由会员分享，可在线阅读，更多相关《TIA-1188-2012 Femtocell Configuration Parameter《Femtocell配置参数》.pdf（110页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA-1188 February 2012Femtocell Configuration Parameter NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting

2、the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards and Pub

3、lications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent policy. By such

4、action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the respon

5、sibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Project No. 3-0394-A, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Document will

6、 be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual property rights (“IP

7、R”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof is requested, al

8、l in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead left to the parties in

9、volved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. If the Documen

10、t contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory,

11、alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of vol

12、untary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s

13、) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS

14、OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLA

15、IMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRO

16、DUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES

17、 FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF

18、THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. 3GPP2 X.S0063-0 v1.0 Revision History Revision Description Date X.S0063 v1.0 Initial Publication December 2011 3GPP2 X.S0063-0 v1.0 i Table of Contents 1 Foreword iii 2 1 Introduction . 1-1 3 1

19、.1 Overview . 1-1 4 1.1.1 Purpose 1-1 5 1.1.2 Scope . 1-1 6 1.1.3 Document Convention 1-1 7 1.2 References . 1-1 8 1.2.1 Normative References . 1-1 9 1.2.2 Informative References . 1-3 10 1.3 Terminology 1-3 11 1.3.1 Acronyms 1-3 12 1.4 Architecture 1-3 13 2 Configuration Parameter Tables . 2-1 14 1

20、5 16 3GPP2 X.S0063-0 v1.0 ii Table of Tables 1 2 Table 2-1 TR-157 Device: Data Model 2-1 3 Table 2-2 TR-262 InternetGatewayDevice: Data Model 2-17 4 Table 2-3 TR-196 FAPService: Data Model 2-31 5 6 7 8 3GPP2 X.S0063-0 v1.0 iii Foreword 1 The foreword is not part of this standard. 2 This document was

21、 prepared by the Third Generation Partnership Project 2 (3GPP2). 3 4 5 6 3GPP2 X.S0063-0 v1.0 iv 1 (This page intentionally left blank) 2 3 4 3GPP2 X.S0063-0 v1.0 1-1 1 Introduction 1 2 1.1 Overview 3 This document defines configuration parameters for the femtocell network. It specifies the air, Rad

22、io 4 Access Network (RAN) and network related configuration parameters that are exchanged between the 5 Femtocell Access Point (FAP) and the Femtocell Management System (FMS) during auto-configuration 6 of the FAP. This document contains parameters that are also defined in 36, 37 and 38. If there is

23、 a 7 conflict between the parameter definition in 36, 37 and 38 and this document, then 36, 37 and 8 38 shall take precedence. 9 1.1.1 Purpose 10 The purpose of this document is to provide a listing of configuration parameters for the femtocell network. 11 1.1.2 Scope 12 This document provides a lis

24、ting of femtocell network configuration parameters. This document contains 13 parameters, definitions, types, values and ranges necessary for auto-configuration interoperability. 14 1.1.3 Document Convention 15 “Shall” and “shall not” identify requirements to be followed strictly to conform to the s

25、tandard and from 16 which no deviation is permitted. “Should” and “should not” indicate that one of several possibilities is 17 recommended as particularly suitable, without mentioning or excluding others; that a certain course of 18 action is preferred but not necessarily required; or (in the negat

26、ive form) that a certain possibility or 19 course of action is discouraged but not prohibited. “May” and “need not” indicate a course of action 20 permissible within the limits of the document. “Can” and “cannot” are used for statements of possibility 21 and capability, whether material, physical, o

27、r causal. 22 1.2 References 23 References are either normative or informative. A normative reference is used to include another doc-24 ument as a mandatory part of a 3GPP2 specification. Documents that provide additional non-essential in-25 formation are included in the informative references sectio

28、n. 26 1.2.1 Normative References 27 The following standards contain provisions which, through reference in this text, constitute provisions of 28 this standard. At the time of publication, the editions indicated were valid. All standards are subject to 29 revision, and parties to agreements based up

29、on this document are encouraged to investigate the possibility 30 of applying the most recent editions published by them. 31 1 3GPP: TS-23.107, Quality of Service (QoS) concept and architecture. 32 2 3GPP: TS 32.300, Telecommunication management; Configuration Management (CM); Name 33 convention for

30、 Managed Objects. 34 3 3GPP: TS 32.582, Telecommunications management; Home Node B (HNB) Operations, Admin-35 istration, Maintenance and Provisioning (OAM Information model for Type 1 interface HNB 36 to HNB Management System (HMS). 37 3GPP2 X.S0063-0 v1.0 1-2 4 3GPP: TS 32.584, Telecommunications m

31、anagement; Home Node B (HNB) Operations, Admin-1 istration, Maintenance and Provisioning (OAM XML definitions for Type 1 interface HNB to 2 HNB Management Systems (HMS). 3 5 3GPP: TS 32.592, Telecommunications management; Home enhanced Node B (HeNB) Operations, 4 Administration, Maintenance and Prov

32、isioning (OAM Information model for Type 1 interface 5 HeNB to HeNB Management System (HeMS). 6 6 3GPP2: A.S0008-C v4.0, Interoperability Specification (IOS) for High Rate Packet Data (HRPD) 7 Radio Access Network Interfaces with Session Control in the Access Network, April 2011. 8 7 3GPP2: A.S0009-

33、C v4.0, Interoperability Specification (IOS) for High Rate Packet Data (HRPD) 9 Radio Access Network Interfaces with Session Control in the Packet Control Function, April 2011. 10 8 3GPP2: A.S0013-D v3.0, Interoperability Specification (IOS) for cdma2000 Access Network 11 Interfaces Part 3 Features,

34、 May 2011. 12 9 3GPP2: A.S0014-D v3.0, Interoperability Specification (IOS) for cdma2000 Access Network 13 Interfaces Part 4 (A1, A1p, A2, and A5 Interfaces), May 2011. 14 10 3GPP2: A.S0024-A v1.0, Interoperability Specification (IOS) for Femtocell Access Points, April 15 2011 16 11 3GPP2: C.S0005-0

35、 v3.0, Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread 17 Spectrum Systems - Release 0, July 2001. 18 12 3GPP2: C.S0005-A v6.0, Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread 19 Spectrum Systems - Release A, Addendum 2, February 2002. 20 13 3GPP2: C.S0005-E v3.0, Upper Lay

36、er (Layer 3) Signaling Standard for cdma2000 Spread 21 Spectrum Systems, June 2011. 22 14 3GPP2: C.S0024-B v3.0, cdma2000 High Rate Packet Data Air Interface Specification, September 23 2009. 24 15 3GPP2: C.S0057-D v1.0, Band Class Specification for cdma2000 Spread Spectrum Systems, 25 September 200

37、9. 26 16 3GPP2: N.S0010-0 v1.0, Advanced Features in Wideband Spread Spectrum Systems, January 1998. 27 17 3GPP2: S.S0132-0 v1.0, Femtocell Security Framework, January 2010. 28 18 3GPP2: X.S0011-005-C v3.0, cdma2000 Wireless IP Network Standard: Accounting Services and 29 3GPP2 RADIUS VSAs, October

38、2006. 30 19 3GPP2: X.S0059-000-0 v1.0, Femtocell Network: Overview, January 2010. 31 20 IETF: RFC 3261, SIP: Session Initiation Protocol, June 2002. 32 21 IETF: RFC 3455, Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) 33 for the 3rd-Generation Partnership Project (3GPP

39、), January 2003. 34 22 IETF: RFC 3550, RTP: A Transport Protocol for Real-Time Applications, July 2003. 35 23 IETF: RFC 3873, Stream Control Transmission Protocol (SCTP) Management Information Base 36 (MIB), September 2004. 37 24 IETF: RFC 3986, Uniform Resource Identifier (URI): Generic Syntax, Jan

40、uary 2005. 38 25 IETF: RFC 4028, Session Timers in the Session Initiation Protocol (SIP), April 2005. 39 26 IETF: RFC 4301, Security Architecture for the Internet Protocol, December 2005. 40 27 IETF: RFC 4307, Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 41 (IKEv2), Decemb

41、er 2005. 42 3GPP2 X.S0063-0 v1.0 1-3 28 IETF: RFC 4960, Stream Control Transmission Protocol, September 2007. 1 29 IETF: RFC 5139, Revised Civic Location Format For Presence Information Data Format Location 2 Object (PIDF-LO), February 2008. 3 30 IETF: RFC 5280, Internet X.509 Public Key Infrastruct

42、ure Certificate and Certificate Revocation 4 List (CRL) Profile, May 2008. 5 31 IETF: RFC 5491, GEOPRIV Presence Information Data Format Location Object (PIDF-LO) 6 Usage Clarification, Considerations, and Recommendations, March 2009. 7 32 ITU-T: Recommendation X.509, Information technology Open Sys

43、tems Interconnection The 8 Directory: Public-key and attribute certificate frameworks, August 2005. 9 33 ITU-T: Recommendation X.731, Information Technology - Open Systems Interconnection - 10 Systems Management: State Management Function, International Telecommunication Union, 11 January 1992. 12 3

44、4 ITU-T: Recommendation X.733, Information technology - Open Systems Interconnection - Systems 13 Management: Alarm reporting function February 1992. 14 35 TR-069, CPE WAN Management Protocol, Broadband Forum 2008. 15 36 TR-157, Component Objects for CWMP, Broadband Forum 2011. 16 37 TR-196, Femto A

45、ccess Point Service Data Model, Broadband Forum 2011. 17 38 TR-262, Femto Component Objects, Broadband Forum 2011. 18 19 1.2.2 Informative References 20 I-1 3GPP2: C.R1001-G v1.0, Administration of Parameter Value Assignments for cdma2000 Spread 21 Spectrum Standards - Release G, June 2009. 22 23 1.

46、3 Terminology 24 25 1.3.1 Acronyms 26 3GPP2 3rd Generation Partnership Project 2 FAP Femtocell Access Point FMS Femtocell Management System RAN Radio Access Network 27 1.4 Architecture 28 Refer to 10 and 19. 29 30 31 32 3GPP2 X.S0063-0 v1.0 1-4 1 (This page intentionally left blank) 2 3 4 3GPP2 X.S0

47、063-0 v1.0 2-1 2 Configuration Parameter Tables 1 This section provides tables for 3GPP2 cdma20001 configuration parameters. These parameters are also 2 defined in 36 (Table 2-1), 38 (Table 2-2) and 37 (Table 2-3). 3 Table 2-1 includes general parameters also defined in 36. 4 Table 2-1 TR-157 Device

48、: Data Model Name Type Write Description PeriodicStatistics. object - PeriodicStatistics.SampleSet.i. object W At most one entry in this table can exist with a given value for Alias. On creation of a new table entry, the CPE MUST choose an initial value for Alias such that the new entry does not con

49、flict with any existing entries. Alias string(64) W A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference. If the CPE supports the Alias-based Addressing feature as defined in Section 3.6.1/TR-069a4 and described in Appendix II/TR-069a4, the following mandatory constraints MUST be enforced: Its value MUST NOT be empty. Its value MUST start with a letter. If its instance object is created