1、 ETSI TS 1Universal Mobile TelTelecommAutomatic NeighboConcep(3GPP TS 32.5TECHNICAL SPECIFICATION132 511 V13.0.0 (2016elecommunications System (LTE; munication management; bour Relation (ANR) managemcepts and requirements .511 version 13.0.0 Release 1316-02) (UMTS); ement; 13) ETSI ETSI TS 132 511 V
2、13.0.0 (2016-02)13GPP TS 32.511 version 13.0.0 Release 13Reference RTS/TSGS-0532511vd00 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre l
3、a Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document s
4、hall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETS
5、I Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, ple
6、ase send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written per
7、mission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand
8、the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 13
9、2 511 V13.0.0 (2016-02)23GPP TS 32.511 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-memb
10、ers, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant
11、 to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present documen
12、t. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to
13、the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“
14、and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 511 V13.0.0 (2016-02)33GPP TS 32.511 version 13.0
15、.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Concepts and background 6g35 Requirements 6g35.1 Business level req
16、uirements . 6g35.1.1 Void 7g35.1.1.1 Void. 7g35.1.1.2 Void. 7g35.1.1.3 Void. 7g35.2 Specification level requirements 7g35.2.1 Void 7g35.2.2 Void 7g35.2.3 Void 7g35.2.4 Use cases . 7g35.2.4.1 Management of fully automatic ANR function . 7g35.2.4.2 Manual start of the ANR function by operator 8g35.2.4
17、.3 Handling of noX2 attribute . 8g35.2.4.4 Manual stop of the ANR function by operator 9g35.2.5 Requirements 10g35.2.5.1 ANR function management in E-UTRAN 10g35.2.5.2 ANR function management in UTRAN 11g3Annex A (informative): Change history . 13g3History 14g3ETSI ETSI TS 132 511 V13.0.0 (2016-02)4
18、3GPP TS 32.511 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the
19、contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approve
20、d document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part of a
21、 TS-family covering the 3rdGeneration Partnership Project Technical Specification Group Services and System Aspects, Telecommunication management; as identified below: 32.511: “Automatic Neighbour Relation (ANR) management; Concepts and requirements“. ETSI ETSI TS 132 511 V13.0.0 (2016-02)53GPP TS 3
22、2.511 version 13.0.0 Release 131 Scope The present document describes the concepts and requirements for the management of Automatic Neighbour Relation (ANR) in UTRAN and E-UTRAN across the Itf-N. The ANR management is a key feature of Self Organizing Networks (SON) 4. The NR concept and background i
23、nformation are described in clause 4. The requirements for management of NR are defined in clause 5. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of pub
24、lication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers
25、 to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 3GP
26、P TR 32.816: “Telecommunication management; Study on Management of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Evolved Packet Core (EPC)“. 5 3GPP TS 32.501 “Telecommunication management; Self-Configuration of Network Elements; Concepts and requirements“. 6 3GPP TS 36.300 “Evolve
27、d Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2“. 7 3GPP TS 32.301 “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Requirements“. 8 3GPP TS 25.48
28、4 “Automatic Neighbour Relation (ANR) for UTRAN; Stage 2“. 3 Definitions and abbreviations For the purposes of the present document, the terms and definitions given in TS 32.101 2, TS 32.102 3 and TS 21.905 1 and the following apply. A term defined in the present document takes precedence over the d
29、efinition of the same term, if any, in TS 32.101 2, TS 32.102 3 and TS 21.905 1, in that order. 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definitio
30、n of the same term, if any, in TR 21.905 1. ANR function: The ANR function in E-UTRAN is described in TS 36.300 6, section 22.3.2a. The ANR function in UTRAN is described in TS 25.484 8. Neighbour cell Relation: The Neighbour cell Relation (NR) in E-UTRAN is defined in TS 36.300 6 section 22.3.2a. T
31、he Neighbour cell Relation in UTRAN is defined in TS 25.484 8. ETSI ETSI TS 132 511 V13.0.0 (2016-02)63GPP TS 32.511 version 13.0.0 Release 13Searchlist: List of frequencies and supporting information to be used for neighbour cell measurements. The Searchlist contains entries for E-UTRAN and support
32、ed IRATs. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. ANR Automatic Neighbour Relatio
33、n eNB eNodeB or evolved NodeB NR Neighbour cell Relation NRT Neighbour cell Relation Table UC Use Case 4 Concepts and background For E-UTRAN, the ANR function in the eNB relates to the Use Cases Establishment of new eNB in network and Optimisation of the neighbourhood list in 4. For Establishment of
34、 new eNB in network. If the operator so chooses, the OAM system adds and configures NRs before the eNB goes into operation. For Optimisation of the neighbourhood list, the ANR function deals with automatic NR additions and removals. It minimizes the need for planning and configuring NRs. If the oper
35、ator so chooses, the OAM system adds and configures NRs or removes NRs after the eNB goes into operation. For UTRAN, the ANR function concept and overall description is documented in TS 25.484 8. The ANR function in RNC allows OAM system to manage the NRT. OAM system can add and delete NRs and also
36、change the attributes of the NRs. The OAM system is informed about changes in the NRT made by ANR function. 5 Requirements 5.1 Business level requirements REQ-ANR-CON-001 NRs shall be set up and optimized with no or minimal human intervention. REQ-ANR-CON-002 For E-UTRAN, initial status of the newly
37、 created NR by ANR function shall be such that HO is allowed, X2 connection setup is allowed, and the NR is allowed to be removed by ANR function in eNB. REQ-ANR-CON-003 E-UTRAN ANR supports management of NRs from E-UTRAN to E-UTRAN, from E-UTRAN to UTRAN, from E-UTRAN to CDMA2000 and from E-UTRAN t
38、o GERAN. REQ-ANR-CON-004 For UTRAN, initial status of the newly created NR by ANR function shall be such that HO is allowed and the NR is allowed to be removed by ANR function in RNC. REQ-ANR-CON-005 UTRAN ANR supports management of NRs from UTRAN to UTRAN, from UTRAN to E-UTRAN and from UTRAN to GE
39、RAN. ETSI ETSI TS 132 511 V13.0.0 (2016-02)73GPP TS 32.511 version 13.0.0 Release 135.1.1 Void 5.1.1.1 Void 5.1.1.2 Void 5.1.1.3 Void 5.2 Specification level requirements 5.2.1 Void 5.2.2 Void 5.2.3 Void 5.2.4 Use cases 5.2.4.1 Management of fully automatic ANR function Use Case Stage Evolution / Sp
40、ecification Related use Goal (*) The goal is that the IRPManager may add and remove NRs and that it may change attributes of the NRs Actors and Roles (*) IRPManager as user Telecom resources ANR function eNB or RNC Assumptions Pre conditions The ANR function in eNB or RNC is active; The cell may or
41、may not have Neighbour Relations configured by O For E-UTRAN, the eNB has finished Use Case Self-configuration of a new eNodeB 5; For UTRAN, the RNC is properly installed and running. Begins when This Use Case begins when all pre conditions have been met. Step 1 (*) (M) If the IRPManager finds out t
42、hat an unsuitable Neighbour Relation has been added by ANR, the IRPManager may Blacklist that particular Neighbour Relation. If the IRPManager finds out that a desired Neighbour Relation has not been added by ANR, the IRPManager may Whitelist that particular Neighbour Relation. The IRPManager may un
43、check the noRemove attribute from any present Neighbour Relation. Ends when (*) This Use Case ends when the eNB or RNC is taken out of service or when the ANR function is stopped. Exceptions One of the steps identified above fails and retry is unsuccessful. Post Conditions Traceability (*) REQ-ANR-C
44、ON-001 ETSI ETSI TS 132 511 V13.0.0 (2016-02)83GPP TS 32.511 version 13.0.0 Release 135.2.4.2 Manual start of the ANR function by operator Use Case Stage Evolution / Specification Related use Goal (*) The ANR function in eNB or RNC can be enabled by IRPManager. Actors and Roles (*) IRPManager as use
45、r Telecom resources ANR function eNB or RNC Assumptions Pre conditions The ANR function is not active; The eNB or RNC may have Neighbour Relations. The NRs may be configured by O&M or be may have been added by ANR function if ANR function has been active previously. Begins when The Use Case begins w
46、hen the IRP Manager starts the ANR function. Step 1 (*) (M) The IRPManager enables the ANR function in eNB or RNC. Ends when (*) Ends when all steps identified above are completed or when an exception occurs Exceptions One of the steps identified above fails and retry is unsuccessful. Post Condition
47、s The ANR function in eNB or RNC is enabled by IRPManager successfully or unsuccessfully. Traceability (*) REQ-ANR-FUN-10, REQ-ANR-FUN-26 5.2.4.3 Handling of noX2 attribute Use Case 1 IRPManager needs to be able to forbid and allow the establishment of X2 interfaces from the source macro eNBs to a t
48、arget eNB. IRPManager is aware that the target eNB cannot support X2 connections. This UC on how noX2 is used relates to node level rather than cell level. Use Case 2 IRPManager needs to be able to allow and forbid the establishment of X2 interfaces from the source HeNBs to a target macro eNB. This
49、UC supports the case when a potentially large number of HeNBs in the vicinity of a macro eNB, X2 establishment requests from HeNB might saturate the physical ports of the macro eNB (not in terms of bandwidth saturation but rather the saturation in terms of the number of simultaneous establishment requests supported). This UC on how noX2 is used relates to node level rather than Cell level. Use Case 3 IRPManager needs to be able to forbid the establishment of the X2 interface f
