1、 ETSI TS 128 669 V15.0.0 (2018-07) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Radio Planning Tool Access (RPTA) Integration Reference Point (IRP); Solution Set (SS) definitions (3GPP TS 28.669 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS
2、128 669 V15.0.0 (2018-07)13GPP TS 28.669 version 15.0.0 Release 15Reference RTS/TSGS-0528669vf00 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 enr
3、egistre la 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 d
4、ocument shall 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 w
5、ithin ETSI 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the pr
6、esent document, please 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 author
7、ized by written permission 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 tradem
8、arks of ETSI registered 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 GS
9、M Association. ETSI ETSI TS 128 669 V15.0.0 (2018-07)23GPP TS 28.669 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, i
10、s publicly available 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 th
11、e ETSI Web server (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 b
12、e, or may become, 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
13、 to use or reproduce 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 Genera
14、tion 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 between GSM, UMTS, 3GPP a
15、nd 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 of the ETSI Drafting
16、 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 128 669 V15.0.0 (2018-07)33GPP TS 28.669 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs te
17、rminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Solution Set Definitions . 7g3Annex A (normative): CORBA Solution Set . 8g3A.0 Introduction 8g3Annex B (normative): XML definitions . 9g3B.0 Introduc
18、tion 9g3B.1 Architectural features . 9g3B.1.1 General . 9g3B.1.2 Description of the XML definitions . 9g3B.2 Mapping . 9g3B.3 Solution Set definitions 9g3B.3.1 XML Schema “rptaIrpIOCs.xsd“ . 9g3B.3.2 XML Schema “rptaIRPOpR.xsd“ . 11g3Annex C (normative): HTTP Solution Set . 13g3C.0 Introduction 13g3
19、C.1 Architectural features . 13g3C.1.1 General . 13g3C.1.2 Supported Specifications 13g3C.1.3 Introduction to HTTP-GET 13g3C.1.4 Usage of HTTP-GET 14g3C.1.5 Request-URI . 14g3C.1.6 Headers . 14g3C.2 Mapping . 15g3C.2.0 Introduction 15g3C.2.1 Operation and Notification mapping 15g3C.2.2 Operation par
20、ameter mapping 16g3C.3 Solution Set definitions 17g3C.3.1 XML Schema “rptaIRPHTTP.xsd“ 17g3C.3.2 JSON definition structure . 17g3Annex D (normative): SOAP Solution Set . 19g3D.0 Introduction 19g3D.1 Architectural features . 19g3D.1.1 General . 19g3D.1.2 Supported W3C specifications . 19g3ETSI ETSI T
21、S 128 669 V15.0.0 (2018-07)43GPP TS 28.669 version 15.0.0 Release 15D.1.3 Filter language 19g3D.2 Mapping . 20g3D.2.1 Operation and Notification mapping 20g3D.2.2 Operation parameter mapping 21g3D.2.2.1 Operation getPlannedData 21g3D.2.2.1.1 Input parameters 21g3D.2.2.1.2 Output parameters . 21g3D.2
22、.2.1.3 Fault definition 21g3D.3 Solution Set definitions 21g3D.3.1 WSDL definition structure . 21g3D.3.2 Graphical Representation . 22g3D.3.3 WSDL specification “RPTAIRPSystem.wsdl“ 23g3Annex E (informative): Change history . 25g3History 26g3ETSI ETSI TS 128 669 V15.0.0 (2018-07)53GPP TS 28.669 vers
23、ion 15.0.0 Release 15Foreword 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 contents of the pre
24、sent 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 approved document under ch
25、ange 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 TS-family covering
26、 the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 28.667: Radio Planning Tool Access (RPTA) Integration Reference Point (IRP); Requirements. 28.668: Radio Planning Tool Access (RPTA) Integration Refer
27、ence Point (IRP): Information Service (IS). 28.669: Radio Planning Tool Access (RPTA) Integration Reference Point (IRP); Solution Set (SS). definitions ETSI ETSI TS 128 669 V15.0.0 (2018-07)63GPP TS 28.669 version 15.0.0 Release 151 Scope The present document specifies the Solution Set definitions (
28、SS) of the Radio Planning Tool Access (RPTA) Integration Reference Point (IRP). This IRP allows the NM to read planned site and antenna data from the RPT. This Solution Set specification is related to 3GPP TS 28.668 V14.0.X 4. 2 References The following documents contain provisions which, through re
29、ference 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 a non-specific reference, the latest v
30、ersion 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 Specifications“. 2 3GPP TS 32.101: “Telecomm
31、unication management; Principles and high level requirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 3GPP TS 28.668: “Telecommunication management; Radio Planning Tool Access (RPTA) Integration Reference Point (IRP); Information Service (IS)“. 5 IETF RFC 2616: “Hypertext
32、Transfer Protocol - HTTP/1.1“ (https:/www.ietf.org/rfc/rfc2616.txt) 6 IETF RFC 7159: “The JavaScript Object Notation (JSON) Data Interchange Format“ (https:/www.ietf.org/rfc/rfc7159.txt) 7 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 8 W3C WSDL 1.1 specification (http:/w
33、ww.w3.org/TR/2001/NOTE-wsdl-20010315) 9 W3C XPath 1.0 specification (http:/www.w3.org/TR/1999/REC-xpath-19991116) 10 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/) 11 IETF RFC 7230: “HTTP/1.1: Message Syntax and Routing“ (https:/www.ietf.org/rfc/rfc7230.txt) 12 IETF RFC 7231: “HTTP/1
34、.1: Semantics and Content“ (https:/www.ietf.org/rfc/rfc7231.txt) 13 IETF RFC 7232: “HTTP/1.1: Conditional Requests“ (https:/www.ietf.org/rfc/rfc7232.txt) 14 IETF RFC 7233: “HTTP/1.1: Range Requests“ (https:/www.ietf.org/rfc/rfc7233.txt) 15 IETF RFC 7234: “HTTP/1.1: Caching“ (https:/www.ietf.org/rfc/
35、rfc7234.txt) 16 IETF RFC 7235: “HTTP/1.1: Authentication“ (https:/www.ietf.org/rfc/rfc7235.txt 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1, 3GPP TS 32.101 2, 3GPP TS 32.102 3, 3GPP TS 28.668 4 and the follow
36、ing apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. ETSI ETSI TS 128 669 V15.0.0 (2018-07)73GPP TS 28.669 version 15.0.0 Release 153.2 Abbreviations For the purposes of the present document, the following abbreviations appl
37、y: IS Information Service SS Solution SetWSDL Web Service Description Language 4 Solution Set Definitions The present document defines the following RPTA IRP Solution Set Definitions: Annex A provides the CORBA Solution Set. Annex B provides the XML Definitions. Annex C provides the HTTP Solution Se
38、t. Annex D provides the SOAP Solution Set. ETSI ETSI TS 128 669 V15.0.0 (2018-07)83GPP TS 28.669 version 15.0.0 Release 15Annex A (normative): CORBA Solution Set A.0 Introduction This annex specifies the CORBA Solution Set for the IRP whose semantics are specified in 3GPP TS 28.668 4. This annex is
39、not provided in the current version of the present document. ETSI ETSI TS 128 669 V15.0.0 (2018-07)93GPP TS 28.669 version 15.0.0 Release 15Annex B (normative): XML definitions B.0 Introduction This annex specifies the XML definitions for the IRP whose semantics are specified in 3GPP TS 28.668 4. B.
40、1 Architectural features B.1.1 General The overall architectural feature of RPTA IRP is specified in 3GPP TS 28.668 3. This clause specifies features that are specific to the XML definitions. B.1.2 Description of the XML definitions This annex specifies the XML definitions for the Support IOCs of th
41、e RPTA IRP in rptaIrpIOCs.xsd. It provides also the XML type definitions used for constructing the getPlannedData() response in rptaIRPOpR.xsd. B.2 Mapping The mapping is not present in this version of the present document. B.3 Solution Set definitions B.3.1 XML Schema “rptaIrpIOCs.xsd“ targetNamesp
42、ace=“http:/www.3gpp.org/ftp/specs/archive/28_series/28.669#rptaIrpIOCs“ xmlns=“http:/www.w3.org/2001/XMLSchema“ xmlns:xrpi=“http:/www.3gpp.org/ftp/specs/archive/28_series/28.669#rptaIrpIOCs“ elementFormDefault=“qualified“ ETSI ETSI TS 128 669 V15.0.0 (2018-07)103GPP TS 28.669 version 15.0.0 Release
43、15ETSI ETSI TS 128 669 V15.0.0 (2018-07)113GPP TS 28.669 version 15.0.0 Release 15B.3.2 XML Schema “rptaIRPOpR.xsd“ targetNamespace=“http:/www.3gpp.org/ftp/specs/archive/28_series/28.669#rptaIRPOpR“ elementFormDefault=“qualified“ xmlns=“http:/www.w3.org/2001/XMLSchema“ xmlns:xrpi=“http:/www.3gpp.org
44、/ftp/specs/archive/28_series/28.669#rptaIRPIOCs“ xmlns:xrpo=“http:/www.3gpp.org/ftp/specs/archive/28_series/28.669#rptaIRPOpR“ ETSI ETSI TS 128 669 V15.0.0 (2018-07)123GPP TS 28.669 version 15.0.0 Release 15ETSI ETSI TS 128 669 V15.0.0 (2018-07)133GPP TS 28.669 version 15.0.0 Release 15Annex C (norm
45、ative): HTTP Solution Set C.0 Introduction This annex specifies the HTTP Solution Set for the IRP whose semantics are specified in 3GPP TS 28.668 4. The HTTP Solution Set is specific for this IRP, and not applicable to any other IRP. C.1 Architectural features C.1.1 General The overall architectural
46、 feature of RPTA IRP is specified in 3GPP TS 28.668 4. This clause specifies features that are specific to the HTTP SS. C.1.2 Supported Specifications HTTP 1.1 5 is supported. JSON 6 is supported. NOTE: IETF RFC 2616 5 is superseded by RFC 7230 11 RFC 7231 12, RFC 7232 13, RFC 7233 14, RFC 7234 15,
47、and RFC 7235 16. These specifications are function wise identical to RFC 2616. C.1.3 Introduction to HTTP-GET IETF RFC 2616 5 specifies the Hypertext Transfer Protocol (HTTP) Version 1.1 (HTTP/1.1). Chapter 1.4 of this document describes the overall operation: “The HTTP protocol is a request/respons
48、e protocol. A client sends a request to the server in the form of a request method, URI, and protocol version, followed by a MIME-like message containing request modifiers, client information, and possible body content over a connection with a server. The server responds with a status line, includin
49、g the messages protocol version and a success or error code, followed by a MIME-like message containing server information, entity metainformation, and possible entity-body content.” Chapter 5 of 5 specifies the HTTP request message and chapter 6 the HTTP response message. The definitions are repeated below for convenience: Request = Request-Line ; *( general-header ; | request-header ; | entity-header ) CRLF) ; CRLF message-body ; Request-Line = Method SP Req
