1、 ETSI TS 128 667 V15.0.0 (2018-07) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Radio Planning Tool Access (RPTA) Integration Reference Point (IRP); Requirements (3GPP TS 28.667 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 128 667 V15.0.0 (
2、2018-07)13GPP TS 28.667 version 15.0.0 Release 15Reference RTS/TSGS-0528667vf00 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 la Sous-P
3、rfecture 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 shall not
4、 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 ETSI Secret
5、ariat. 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, p
6、lease 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 p
7、ermission 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. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI regi
8、stered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ET
9、SI ETSI TS 128 667 V15.0.0 (2018-07)23GPP TS 28.667 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly availa
10、ble for ETSI members and non-members, 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
11、 (https:/ipr.etsi.org/). Pursuant 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,
12、 essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reprod
13、uce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership
14、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 between GSM, UMTS, 3GPP and ETSI identitie
15、s 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 of the ETSI Drafting Rules (Verbal fo
16、rms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 128 667 V15.0.0 (2018-07)33GPP TS 28.667 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Fore
17、word . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 Concepts and background 5g34.1 General . 5g34.2 Architecture 6g34.3 Functionality . 6g35 Business level requirements . 6g35.1 Requirements 6g35.2 Actor roles 6g35.3 T
18、elecommunications resources 6g35.4 High-level use cases . 7g35.4.1 Use Case: Read planned data from the RPT . 7g36 Specification level requirements 7g36.1 Requirements 7g36.2 Actor roles 7g36.3 Telecommunications resources 7g36.4 Use cases 7g36.4.1 Use Case 1: Read planned site data 7g36.4.2 Use Cas
19、e 2: Read planned antenna data 8g36.4.3 Use Case 3: Find out the planned antennas supporting a planned cell 8g36.4.4 Use Case 4: Find out the planned cells supported by a planned antenna 8g36.4.5 Use Case 5: Find out the RAT of a planned cell . 8g3Annex A (informative): Relation of RPT Planned Data,
20、 ARCF data and configuration data 9g3Annex B (informative): Change history . 10g3History 11g3ETSI ETSI TS 128 667 V15.0.0 (2018-07)43GPP TS 28.667 version 15.0.0 Release 15Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the pre
21、sent 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 version number as follows: Version x.y
22、.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, corrections, updates, etc. z the third dig
23、it is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
24、 28.667 Radio Planning Tool Access (RPTA) Integration Reference Point (IRP); Requirements 28.668 Radio Planning Tool Access (RPTA) Integration Reference Point (IRP); Information Service (IS) 28.669 Radio Planning Tool Access (RPTA) Integration Reference Point (IRP); Solution Set (SS) definitions ETS
25、I ETSI TS 128 667 V15.0.0 (2018-07)53GPP TS 28.667 version 15.0.0 Release 151 Scope The present document specifies the requirements of the Radio Planning Tool Access (RPTA) Integration Reference Point (IRP). This IRP allows to read site and antenna data from RPTs. 2 References The following document
26、s 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-specific. - For a specific reference, subsequent revisions do not apply. - For
27、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 Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specif
28、ications“. 2 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 3 3GPP TS 32.501: “Telecommunication management; Self-configuration of network elements; Concepts and requirements“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present do
29、cument, 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 definition of the same term, if any, in TR 21.905 1. Radio Planning Tool: The tool which is used for radio network planning, where the planning process typ
30、ically includes radio frequencies assigning, sites and site locations determination, traffic planning, interference analysis, and configuration parameters planning to provide sufficient coverage and capacity for a radio network. Planned Data: It is the data exposed by the RPT for read access by the
31、NM. 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. NMLS Network Management Layer Service
32、 RPT Radio Planning Tool RPTA Radio Planning Tool Access (RPTA) SC Service Consumer SP Service Provider 4 Concepts and background 4.1 General The initial planning of radio parameters is typically done with specialized tools called Radio Planning Tools (RPTs). RPTs generate throughput and capacity es
33、timations as well as predictions for coverage and interference maps. RPTs utilize site and antenna (equipment) information, as well as geographic data (e.g. terrain data, type of land usage, building data and road data). This data has to be entered into the tools. ETSI ETSI TS 128 667 V15.0.0 (2018-
34、07)63GPP TS 28.667 version 15.0.0 Release 15In order to improve the initial network planning, planned site and antenna data are adjusted until the estimated system performance meets the requirements within the given deployment constraints. Information about the sites and antennas is needed also by o
35、ther applications, like SON applications or CM applications on NM level. For this reason it is beneficial if this data can be read via standardized interfaces. In contrast to configuration information it is normally not possible to read this data from the network elements. The only place where this
36、data is available in many deployment scenarios is in the RPT. Though this data represents initial planning, site data and antenna data are not likely to be changed very often, so that there is a fair chance that the data stored by the RPT represents also the actual situation in the network. For this
37、 reason it is beneficial to have a read access to site and antenna data stored by the RPT. It is to be noted that this TS series is only about the read access to site and antenna data. It is not concerned with any other functionality the RPT might have, nor with how the read data is used, nor if the
38、 read data represents the actual information about the network or if the data is outdated. Reading of site and antenna data stored by the RPT is hence the only use case in scope. 4.2 Architecture The RPT is a kind of NMLS (see TS 32.101 2). 4.3 Functionality The RPT offers a capability allowing read
39、 access to site and antenna data. The RPT is a Service Provider (SP) and the NM a Service Consumer (SC). The RPTA IRP specifies the information model exposed by the RPT, and the operations to access it. 5 Business level requirements 5.1 Requirements REQ-RPT_NRM-CON-001: The RPT shall support a capab
40、ility allowing the NM to retrieve planned data from the RPT. 5.2 Actor roles The function at the NM requesting to read planned data from the RPT. 5.3 Telecommunications resources RPT: The Radio Planning Tool storing the planned data and exposing it by its Service Provider (SP) function. NM: The Netw
41、ork Manager requesting the planned data by its Service Consumer (SC) function. SP in the RPT: The Service Provider (SP) in the RPT offering read access to planned data in the RPT. SC in the NM: The Service Consumer (SC) in the NM using services offered by the RPT. ETSI ETSI TS 128 667 V15.0.0 (2018-
42、07)73GPP TS 28.667 version 15.0.0 Release 155.4 High-level use cases 5.4.1 Use Case: Read planned data from the RPT Use case stage Evolution/Specification Related use Goal The NM reads planned data from the RPT. Actors and Roles The function in the NM requesting to read planned data from the RPT. Te
43、lecom resources RPT, NM, SP in the RPT, SC in the NM. Assumptions Connectivity exists between RPT SP and the NM SC, so that SP and SC can communicate. Pre-conditions The network is planned and the planned data is stored and available in the RPT. Begins when The NM SC requests the RPT SP to provide c
44、ertain planned data stored in the RPT by sending an appropriate request message to the RPT SP. Step 1 (M) The RPT SP receives the request message. Step 2 (M) The RPT processes the request message, identifies the requested planned data and retrieves the requested planned data. Step 3 (M) The RPT SP s
45、ends back to the NM SC the requested planned data in a response message. Ends when The NM SC has received the requested planned data. Exceptions The NM SC does not receive the requested planned data. Numerous failure reasons may be indicated. Post-conditions The requested planned data has been retur
46、ned. The planned data stored in RPT before and after the exchange of the request/response messages are identical. Traceability Requirement REQ-RPT_NRM-CON-001 in clause 5.1. 6 Specification level requirements 6.1 Requirements REQ-RPT_NRM-FUN-001: The RPT shall support a capability allowing the NM to
47、 retrieve planned site data (e.g. site latitude, site longitude) from the RPT. REQ-RPT_NRM-FUN-002: The RPT shall support a capability allowing the NM to retrieve planned antenna data (e.g. antenna latitude, antenna longitude, antenna type, pattern label, antenna tilt) from the RPT. REQ-RPT_NRM-FUN-
48、003: The RPT shall support a capability allowing the NM to find out the planned antennas supporting a planned cell. REQ-RPT_NRM-FUN-004: The RPT shall support a capability allowing the NM to find out the planned cells supported by a planned antenna. REQ-RPT_NRM-FUN-005: The RPT shall support a capab
49、ility allowing the NM to find out the RAT of a planned cell. 6.2 Actor roles See clause 5.2. 6.3 Telecommunications resources See clause 5.3. 6.4 Use cases 6.4.1 Use Case 1: Read planned site data The use case in clause 5.4.1 describes in generic fashion the use case on reading planned data from the RPT. In the use case “Read planned site data“ this information is planned site data. ETSI ETSI TS 128 667 V15.0.0 (2018-07)83GPP TS 28.667 version 15.0.0 Release 156.4.2 Use Case 2: Read planned antenna data The use case in clause 5.4.1 describes in generic fashion
