1、 ETSI TS 1Universal Mobile TelUTRAN Iuant(3GPP TS 25.4TECHNICAL SPECIFICATION125 466 V13.0.0 (2016elecommunications System (nt interface: Application part .466 version 13.0.0 Release 1316-01) (UMTS); rt 13) ETSI ETSI TS 125 466 V13.0.0 (2016-01)13GPP TS 25.466 version 13.0.0 Release 13Reference RTS/
2、TSGR-0325466vd00 Keywords LTE 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 present docum
3、ent 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 of ETSI. In cas
4、e 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 that the docume
5、nt 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:/portal.etsi.o
6、rg/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 modified withou
7、t 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 benefit of its Memb
8、ers. 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 466 V13.0.0 (2016-01)23GPP TS 25.466 version 13.0.0 Release 13Intellectual
9、 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 Property Rights (IPR
10、s); 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 searches, has been
11、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 produced by ETSI 3rd
12、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 between GSM, UMTS,
13、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 of the ETSI Dr
14、afting 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 466 V13.0.0 (2016-01)33GPP TS 25.466 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal ve
15、rbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 8g34 General . 8g34.1 Procedure specification principles 8g34.2 Forwards and backwards compatibility 8g34.3 Multi-antenna units. 8g34.4 Integer representation . 8g3
16、4.5 TMA Subunits 9g35 Services expected from signalling transport . 9g35.1 Elementary procedure format . 9g35.1.1 Initiating message . 9g35.1.2 Response message 9g36 Control elementary procedures 10g36.1 State model . 10g36.2 General procedure handling . 10g36.2.1 Alarms 10g36.2.2 Procedure message
17、interpretation . 11g36.2.3 Parallel procedure handling 11g36.3 Overview of elementary procedures . 12g36.4 Description of elementary procedures 14g36.5 Common elementary procedures 15g36.5.1 Reset Software 15g36.5.2 Get Alarm Status . 16g36.5.3 Get Information 16g36.5.4 Clear Active Alarms . 17g36.5
18、.5 Alarm Subscribe . 18g36.5.6 Self Test 18g36.5.7 Void 19g36.5.8 Void 19g36.5.9 Read User Data . 19g36.5.10 Write User Data 20g36.5.11 Download Start . 21g36.5.12 Download Application 21g36.5.13 Download End 22g36.5.14 Vendor specific procedure 23g36.6 Single-antenna elementary procedures . 23g36.6
19、.1 Calibrate 23g36.6.2 Send Configuration Data 24g36.6.3 Set Tilt 25g36.6.4 Get Tilt 26g36.6.5 Alarm Indication . 26g36.6.6 Set Device Data 27g36.6.7 Get Device Data 27g36.7 Multi-antenna elementary procedures 28g3ETSI ETSI TS 125 466 V13.0.0 (2016-01)43GPP TS 25.466 version 13.0.0 Release 136.7.1 A
20、ntenna Calibrate . 28g36.7.2 Antenna Set Tilt 29g36.7.3 Antenna Get Tilt . 30g36.7.4 Antenna Set Device Data 30g36.7.5 Antenna Get Device Data . 31g36.7.6 Antenna Alarm Indication 32g36.7.7 Antenna Clear Active Alarms . 32g36.7.8 Antenna Get Alarm Status 33g36.7.9 Antenna Get Number Of Antennas . 34
21、g36.7.10 Antenna Send Configuration Data 34g36.8 TMAAP Elementary procedures for TMA . 35g36.8.1 TMA Set Mode . 35g36.8.2 TMA Get Mode 36g36.8.3 TMA Get Supported Functions . 36g36.8.4 TMA Set Gain . 37g36.8.5 TMA Get Gain 38g36.8.6 TMA Set Device Data . 39g36.8.7 TMA Get Device Data 40g36.8.8 TMA A
22、larm Indication . 40g36.8.8.1 Further requirements . 41g36.8.9 TMA Clear Active Alarms . 41g36.8.10 TMA Get Alarm Status . 42g36.8.11 TMA Get Number of Subunits . 42g36.8.12 3GPP Clear Active Alarms and Get Alarm Status 43g36.8.13 TMA Get Supported Non-Linear Gain Values . 43g37 Unknown elementary p
23、rocedures . 44g3Annex A (normative): Return codes for secondary devices . 45g3Annex B (normative): Assigned fields for additional data . 46g3Annex C (normative): Procedure sequence for download of software to a secondary device. 50g3Annex D (informative): Overview of elementary procedures. 51g3Annex
24、 E (informative): I-frame and INFO-field format 52g3Annex F (informative): Change History 53g3History 54g3ETSI ETSI TS 125 466 V13.0.0 (2016-01)53GPP TS 25.466 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The conten
25、ts 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 version number as follows
26、: 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, corrections, updates, etc. z
27、the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 125 466 V13.0.0 (2016-01)63GPP TS 25.466 version 13.0.0 Release 131 Scope The present document specifies the Remote Electrical Tilting Application Part (RETAP) between the implementation s
28、pecific O - If a message has a length inconsistent with its “Number of data octets“ field value it shall be responded with a failure message stating “FormatError“ as the cause of failure. The response message shall be to the initiating message identified by the procedure code; - If a secondary devic
29、e in the OperatingMode state receives a procedure message which is undefined for this device type, it shall respond with “Unknown Procedure“; - If a secondary device in the OperatingMode state is receiving a procedure message of an optional procedure not supported, it shall respond with a failure me
30、ssage stating “UnsupportedProcedure“ as the cause of failure; - If a secondary device receives a procedure message, part of the software download procedure sequence described in Annex C, without having received the previous procedure messages in that sequence it shall respond with a failure message
31、stating “InvalidProcedureSequence“ as the cause of failure; - If a secondary device in the DownloadMode state is receiving a procedure message not supported in that state it shall respond with a failure message stating “WorkingSoftwareMissing“ as the cause of failure; - If a message has a length inc
32、onsistent with the defined message length in the procedure definition it shall be responded with a failure message stating “FormatError“ as the cause of failure. The response message shall be to the initiating message identified by the procedure code; - If a secondary device in the OperatingMode sta
33、te is receiving a procedure message which addressed device subunit does not exist “FormatError“ shall be returned. 6.2.3 Parallel procedure handling The secondary device shall support parallel execution of in maximum one additional EP only in parallel to one of the Time-Consuming Procedures defined
34、in table 6.2.3.1: ETSI ETSI TS 125 466 V13.0.0 (2016-01)123GPP TS 25.466 version 13.0.0 Release 13Table 6.2.3.1: Definition of TCPs and the execution of procedures in parallel to a TCP Elementary Procedure TCP Execution in parallel to a TCP Common Procedure Set (Reserved) Reset Software No mandatory
35、 Get Alarm Status Nomandatory Get Information No mandatory Clear Active Alarms No disallowed Read User Data No optional Write User Data No optional Alarm Subscribe No optional Self Test Yes disallowed Download Start No disallowed Download Application No disallowed Download End No disallowed Vendor s
36、pecific procedure vendor specific optional Single-Antenna Procedure Set Set Device Data No optional Get Device Data No optional Calibrate Yes disallowedSend Configuration Data No disallowed Set Tilt Yes disallowed Get Tilt No optional Alarm Indication No optional Multi-Antenna Procedure Set Antenna
37、Calibrate Yes optional Antenna Send Configuration Data No disallowed Antenna Set Tilt Yes optional Antenna Get Tilt No optional Antenna Set Device Data No optional Antenna Get Device Data No optional Antenna Alarm Indication No optional Antenna Clear Active Alarms No disallowed Antenna Get Alarm Sta
38、tus No mandatory Antenna Get Number of Antennas No mandatory “yes“ in the “TCP“ column indicates that the procedure is a TCP, “no“ in the “TCP“ column indicates that the procedure is not a TCP. “mandatory“ in the “Execution in parallel to a TCP“ column indicates that the procedure shall be executed
39、in parallel to an ongoing TCP. “optional“ in this column indicates, that the support of the execution of the procedure in parallel to an ongoing TCP is optional and “disallowed“ indicates that the procedure shall not be executed in parallel to a TCP. If a secondary device receives an initiating mess
40、age for an EP which cannot be executed due to the ongoing execution of other EPs, the secondary device shall respond with a failure message stating “Busy“ as the cause of failure. Parallel execution of one TCP marked “optional“ in the “Execution in parallel to a TCP“ column in table 6.2.3.1 may be s
41、upported for each antenna by the secondary device. The EPs AntennaSetTilt and AntennaCalibrate shall be executed in parallel only for different antenna numbers. If more than one TCP is executed, ResetSoftware shall be executed anyway and never be responded with “Busy“. If the EPs Get Tilt and Antenn
42、a GetTilt are executed in parallel with a TCP, their response message shall deliver a tilt value sampled during their execution. TMAAP doesn“t define any TCPs. Therefore parallel procedure handling is not supported by TMAAP. 6.3 Overview of elementary procedures The set of elementary procedures for
43、RET antennas and TMAs control provides procedure-oriented instructions. An overview of the procedures is given in annex D. Table 6.3.1 lists all common elementary procedures described in subclause 6.5. Table 6.3.2 lists all RETAP elementary procedures specific for single-antenna device types describ
44、ed in subclause 6.6. Table 6.3.3 lists all RETAP elementary procedures specific for multi-antenna device types described in ETSI ETSI TS 125 466 V13.0.0 (2016-01)133GPP TS 25.466 version 13.0.0 Release 13subclause 6.7. Table 6.3.4 lists all TMAAP elementary procedures specific for TMA device types d
45、escribed in subclause 6.8. Subclause 6.4 describes how to interpret the elementary procedure definitions in subclauses 6.5 to 6.8. Some elementary procedures shall be performed in sequence as described in Annex C for the software download. Table 6.3.1: Common elementary procedure set for all device
46、types Elementary procedure Requirement Comment Reset Software Mandatory Get Alarm Status Mandatory Get Information Mandatory Clear Active Alarms Mandatory Alarm Subscribe Mandatory Read User Data Mandatory Write User Data Mandatory Self Test Mandatory Download Start Optional This procedure is mandat
47、ory if the software download feature is supported Download Application Optional This procedure is mandatory if the software download feature is supported Download End Optional This procedure is mandatory if the software download feature is supported Vendor specific procedure Optional Table 6.3.2: RE
48、TAP Elementary procedure set for single-antenna device type Elementary procedure Requirement Comment Calibrate MandatorySend Configuration Data Mandatory Set Tilt Mandatory Get Tilt Mandatory Alarm Indication Mandatory Set Device Data Mandatory Get Device Data Mandatory Table 6.3.3: RETAP Elementary
49、 procedure set for multi-antenna device type Elementary procedure Requirement Comment Antenna Calibrate Mandatory Antenna Send Configuration Data Mandatory Antenna Set Tilt Mandatory Antenna Get Tilt Mandatory Antenna Set Device Data Mandatory Antenna Get Device Data Mandatory Antenna Alarm Indication Mandatory Antenna Clear Active Alarms Mandatory Antenna Get Alarm Status Mandatory Antenna Get Number Of Antennas Mandatory ETSI ETSI TS 125 466 V13.0.0 (2016-01)143GPP TS 25.466 version 13.0.0 Release 13Table 6.3.4: TMAAP elementary procedure set for TMA devices Elementary p
