1、 ETSI TS 1Universal Mobile TelAutomatic Neighb(3GPP TS 25.4TECHNICAL SPECIFICATION125 484 V13.0.0 (2016elecommunications System (hbour Relation (ANR) for UTRStage 2 .484 version 13.0.0 Release 1316-01) (UMTS); TRAN; 13) ETSI ETSI TS 125 484 V13.0.0 (2016-01)13GPP TS 25.484 version 13.0.0 Release 13R
2、eference RTS/TSGR-0325484vd00 Keywords 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 la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The
3、 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 shall not be modified without the prior written authorization o
4、f 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 ETSI Secretariat. Users of the present document should be aware t
5、hat 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, please send your comment to one of the following services: https:
6、/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 permission of ETSI. The content of the PDF version shall not be m
7、odified 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 the ETSI logo are Trade Marks of ETSI registered for the benef
8、it 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 125 484 V13.0.0 (2016-01)23GPP TS 25.484 version 13.0.0 Release
9、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-members, and can be found in ETSI SR 000 314: “Intellectual Proper
10、ty 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 to the ETSI IPR Policy, no investigation, including IPR searc
11、hes, 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 document. Foreword This Technical Specification (TS) has been produce
12、d 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 the corresponding ETSI deliverables. The cross reference betwe
13、en 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“ and “cannot“ are to be interpreted as described in clause 3.2
14、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 125 484 V13.0.0 (2016-01)33GPP TS 25.484 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword
15、 . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 5g33.1 Definitions 5g33.2 Symbols 6g33.3 Abbreviations . 7g34 Automatic Neighbour Relation Function, Main Concepts . 7g34.1 General . 7g34.2 ANR Handling in the UTRAN Infrastructure -
16、 Overall Description 8g34.2.1 Iur Connectivity exists between the involved RNCs 8g34.2.1.1 ANR Report over Uu for UTRAN cells 8g34.2.1.2 ANR Report over Iur for UTRAN cells 9g34.2.1.3 ANR Report over Iur for IRAT cells. 11g34.2.2 Iur Connectivity does not exist between some RNCs involved in ANR . 12
17、g34.2.2.1 ANR report over Uu for UTRAN cells . 12g34.2.3 ANR Report over Uu for IRAT cells - with and without Iur 13g35 Functions and Procedures . 14g35.1 ANR Management 15g35.1.1 ANR Report Forwarding 15g35.1.2 ANR Report Distribution Controlling. 15g35.2 Neighbour Cell Configuration 16g35.2.1 Neig
18、hbour Cell Configuration for Intra-RNS cells . 16g35.2.2 Neighbour Cell Configuration for Inter-RNS cells (with Iur) . 16g35.2.3 Neighbour Cell Configuration (without Iur) . 16g35.3 ANR Logging configuration. 16g35.3.1 Configuration parameters . 17g35.3.2 Configuration validity . 17g35.4 Measurement
19、 Collection . 18g35.5 Measurement Reporting . 18g35.6 UE Capabilities 19g3Annex A (informative): Change history . 20g3History 21g3ETSI ETSI TS 125 484 V13.0.0 (2016-01)43GPP TS 25.484 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Pr
20、oject (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 contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in v
21、ersion 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 approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corre
22、ctions, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 125 484 V13.0.0 (2016-01)53GPP TS 25.484 version 13.0.0 Release 131 Scope The present document is a technical specification of the overall support of Automatic Neig
23、hbour Relation (ANR) Function in UTRA. 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 publication, edition number, version number, etc.) or non-speci
24、fic. - 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 to the latest version of that document in the same Rele
25、ase as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 3 Definitions, symbols and abbreviations 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
26、 precedence over the definition of the same term, if any, in TR 21.905 1. Base UTRAN Cell: A cell in UTRAN for which a missing neighbour cell is detected. Neighbour Cell: A cell in UTRAN, LTE or GSM/GERAN that is a neighbour cell to a Base UTRAN Cell. Neighbour Cell Identifier (NCI): The identifier
27、of a Neighbour Cell Neighbour cell Relation (NR): Information that a Neighbour Cell, identified with NCI, is a neighbour to a Base UTRAN Cell. NR is stored in the RNC controlling the Base UTRAN Cell. Conceptual Neighbour Relation Functions: The ANR is described using a number of conceptual entities
28、and functions in the RNC: Neighbour Relation Table, Neighbour Relation Table Management Function, Neighbour Removal Function and Neighbour Detection Function. These entities and functions are used for descriptive purpose only and shall not be regarded as requirements on the implementation in RNC. Re
29、ceiving RNC: the RNC receiving the ANR report over Uu Base RNC: the CRNC of the Base UTRAN Cell Neighbour RNC: the CRNC of the Neighbour Cell in UTRAN ANR-PLMN List: A list of PLMNs that is the RPLMN and the list of equivalent PLMNs for the UE at the point of receiving ANR logging configuration. ANR
30、 measurement: Physical measurements and reading of System Information towards detected cells outside NCL. ANR logging: Storing of essential information of detected cell into UE internal ANR log, when one or more detected cell satisfies ANR logging criteria. ETSI ETSI TS 125 484 V13.0.0 (2016-01)63GP
31、P TS 25.484 version 13.0.0 Release 133.2 Symbols Void ETSI ETSI TS 125 484 V13.0.0 (2016-01)73GPP TS 25.484 version 13.0.0 Release 133.3 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 apply. 4 Automatic Neighbour Relation Function, Main Concepts 4.1 Ge
32、neral Neighbour Detection FunctionInternal IinformationRRCCell InformationAdd/UpdateNeighborRelationsNRreportNRTManagemnt FunctionNeighbourRemovalFunctionNeighbor Relation Table12NCI3No RemoveNCI#1NCI#1No HONRNCl#1Neighbour Cell IinformationFigure 4.1-1: Interaction between RNC and O&M due to ANR Th
33、e ANR function resides in the RNC and is composed of the Neighbour Relation Table (NRT) Management Function, Neighbour Detection Function and Neighbour Removal Function. The Neighbour Detection Function detects new neighbours and adds them to the NRT. The Neighbour Removal Function removes outdated
34、NRs. ETSI ETSI TS 125 484 V13.0.0 (2016-01)83GPP TS 25.484 version 13.0.0 Release 13A Neighbour cell Relation (NR) between a Base UTRAN Cell and a Neighbour Cell exists if the RNC controlling the Base UTRAN Cell: a) Knows the following Neighbour Cell information: - Neighbour cell is in UTRAN: PLMN-I
35、d, Cell Identifier(C-ID), RNC-ID/Extended RNC-ID, - Neighbour cell is in LTE: ECGI (PLMN Id + Cell Identity) - Neighbour cell is in GSM/GERAN: PLMN Id, LAC, CI, BSIC b) Has an entry in the Neighbour Relation Table for the Base UTRAN Cell identifying the neighbour cell. c) Has all required attributes
36、 defined in the Neighbour Relation Table entry or set to default values. Among these attributes are the frequency information (UARFCN, BCCH ARFCN, EARFCN) and handover routing parameters not already considered in (a): - Neighbour cell is in UTRAN: LAC and RAC - Neighbour cell is in LTE: TAI For each
37、 NR, the NRT contains the Neighbour Cell Identifier (NCI), which identifies the neighbour cells. A neighbour cell may be a UTRAN, LTE or GSM cell. Furthermore, each NR has two attributes, the No Remove and the No HO attributes. These attributes have the following definitions: - No Remove: If checked
38、, the RNC shall not remove the Neighbour cell Relation from the NRT. - No HO: If checked, the Neighbour cell Relation shall not be used as a neighbour cell by Intra RNS, Inter RNS or Inter RAT mobility functions in UTRAN. The ANR function also allows O&M to manage the NRT. O&M can add and delete NRs
39、. It can also change the attributes of the NR. The O&M system is informed about changes in the NRT. 4.2 ANR Handling in the UTRAN Infrastructure - Overall Description If UTRAN ANR functionality is supported in UTRAN, RNC shall be able to configure the UE to perform the ANR measurement. ANR capable U
40、E performs the ANR measurement and records in its logbook newly detected cells which meet the criteria given in the configuration. The Receiving RNC uses RRC signalling to retrieve the ANR report over the Uu interface after the UE has indicated that it has a logged ANR report. The Receiving RNC hand
41、les the ANR report and may forward the ANR report to different RNCs. This chapter illustrates the handling and message sequences to be used to configure a new neighbour relation for a UTRAN cell. 4.2.1 Iur Connectivity exists between the involved RNCs The ANR function supports forwarding of ANR repo
42、rts from the Receiving RNC to RNCs indicated as Base RNCs in the ANR report. Furthermore the ANR function supports suspension (and resuming) ANR logs reporting over Iur from other RNCs as described in 5.1.2. This chapter describes the handling in the Receiving, Base and Neighbour RNCs when Iur conne
43、ctivity exists between the involved RNCs. 4.2.1.1 ANR Report over Uu for UTRAN cells When receiving an ANR report over Uu, the Receiving RNC uses the globally unique cell identities in the report to determine the network addresses of the RNCs that are controlling the Base UTRAN cells. The network ad
44、dress of this Base RNC is retrieved using configuration in the Receiving RNC and/or O&M. The Receiving RNC decides the necessity to forward the ANR report. If the Base UTRAN Cell is under control of the Receiving RNC, the Receiving RNC terminates the relevant ANR report entry, and may update the Nei
45、ghbouring Relation accordingly. Otherwise, the ANR report is forwarded to the Base RNCs over Iur with the RNSAP Direct Information Transfer procedure. ETSI ETSI TS 125 484 V13.0.0 (2016-01)93GPP TS 25.484 version 13.0.0 Release 13If newly detected neighbour cells are controlled by another RNC the RN
46、SAP Information Exchange Initiation procedure is used to request cell information from the neighbour RNC. In addition the Base RNC may interact with O&M before a neighbour relation is stored in the NRT. Figure 4.2.1.1-1 ANR Report over Uu for UTRAN cells 4.2.1.2 ANR Report over Iur for UTRAN cells O
47、n reception of an ANR report from another RNC using the RNSAP Direct Information Transfer procedure, the Base RNC uses the globally unique cell identities and L1 information in the ANR report, and optionally also configuration in the RNC/O&M, to determine if the ANR report contains any potential nei
48、ghbour cells. If any of these potential neighbour cells is controlled by another RNC the RNSAP Information Exchange Initiation procedure may be used to request cell information from the neighbour RNC. In addition the Base RNC may interact with O&M before a neighbour relation is be stored in the NRT
49、as shown in the figure below: ETSI ETSI TS 125 484 V13.0.0 (2016-01)103GPP TS 25.484 version 13.0.0 Release 13RNC2(Role:- Base RNC)RNC3(Role:- Neighbour RNC)IurRNC1(Role:- Receiving RNC)IurIntra UMTS, Inter RNS, ANR report over IurRNSAP: DIRECT INFORMATION TRANSFER, ANR report transparent:(list NR:- Cell-ID a - Cell-ID b, - Cell-ID c-Cell-ID d,- Cell-ID e-Cell-ID f,.)RNSAP: INFORMATION EXCHANGE INITIATION REQUEST(List: C-ID n, type=on demand)RNSAP: INFORMATION EXCHANGE INITIATION RESPONSE(List: cell attributes)Store UTRAN neighbour cells (C-ID n) in NRT after interac
