ETSI TS 137 466 V15.5.0 (2020-01)

Universal Mobile Telecommunications System (UMTS); LTE; 5G; Iuant interface: Application part (3GPP TS 37.466 version 15.5.0 Release 15)

RTS/TSGR-0337466vf50

General Information

• Status: Published
• Publication Date: 16-Jan-2020
• Technical Committee: 3GPP RAN 3 - lub specification, lur specification, lu specification and UTRAN & O&M
• Current Stage: 12 - Completion
• Completion Date: 17-Jan-2020

Standards Content (Sample)

TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
5G;
Iuant interface: Application part
(3GPP TS 37.466 version 15.5.0 Release 15)

3GPP TS 37.466 version 15.5.0 Release 15 1 ETSI TS 137 466 V15.5.0 (2020-01)

Reference
RTS/TSGR-0337466vf50
Keywords
5G,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture 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 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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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, 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 authorized 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 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 37.466 version 15.5.0 Release 15 2 ETSI TS 137 466 V15.5.0 (2020-01)
Intellectual 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 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 the 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 be, 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 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.
Legal Notice
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. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 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 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
3GPP TS 37.466 version 15.5.0 Release 15 3 ETSI TS 137 466 V15.5.0 (2020-01)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 8
4 General . 8
4.1 Procedure specification principles . 8
4.2 Forwards and backwards compatibility . 8
4.3 Multi-antenna units. 8
4.4 Integer representation . 9
4.5 TMA Subunits . 9
5 Services expected from signalling transport . 9
5.1 Elementary procedure format . 9
5.1.1 Initiating message . 9
5.1.2 Response message . 9
6 Control elementary procedures . 10
6.1 State model . 10
6.2 General procedure handling . 11
6.2.1 Alarms . 11
6.2.2 Procedure message interpretation . 11
6.2.3 Parallel procedure handling . 11
6.3 Overview of elementary procedures . 12
6.4 Description of elementary procedures . 14
6.5 Common elementary procedures . 15
6.5.1 Reset Software . 15
6.5.2 Get Alarm Status . 16
6.5.3 Get Information . 16
6.5.4 Clear Active Alarms . 17
6.5.5 Alarm Subscribe . 18
6.5.6 Self Test . 18
6.5.7 Void . 19
6.5.8 Void . 19
6.5.9 Read User Data . 19
6.5.10 Write User Data . 20
6.5.11 Download Start . 21
6.5.12 Download Application . 21
6.5.13 Download End . 22
6.5.14 Vendor specific procedure . 23
6.6 Single-antenna elementary procedures . 23
6.6.1 Calibrate . 23
6.6.2 Send Configuration Data . 24
6.6.3 Set Tilt . 25
6.6.4 Get Tilt . 26
6.6.5 Alarm Indication . 26
6.6.6 Set Device Data . 27
6.6.7 Get Device Data . 27
6.7 Multi-antenna elementary procedures . 28
6.7.1 Antenna Calibrate . 28
ETSI
3GPP TS 37.466 version 15.5.0 Release 15 4 ETSI TS 137 466 V15.5.0 (2020-01)
6.7.2 Antenna Set Tilt . 29
6.7.3 Antenna Get Tilt . 30
6.7.4 Antenna Set Device Data . 30
6.7.5 Antenna Get Device Data . 31
6.7.6 Antenna Alarm Indication . 32
6.7.7 Antenna Clear Active Alarms . 32
6.7.8 Antenna Get Alarm Status . 33
6.7.9 Antenna Get Number Of Antennas . 34
6.7.10 Antenna Send Configuration Data . 34
6.8 TMAAP Elementary procedures for TMA . 35
6.8.1 TMA Set Mode . 35
6.8.2 TMA Get Mode . 36
6.8.3 TMA Get Supported Functions . 36
6.8.4 TMA Set Gain . 37
6.8.5 TMA Get Gain . 38
6.8.6 TMA Set Device Da ta . 39
6.8.7 TMA Get Device Data . 40
6.8.8 TMA Alarm Indication . 40
6.8.8.1 Further requirements . 41
6.8.9 TMA Clear Active Alarms . 41
6.8.10 TMA Get Alarm Status . 42
6.8.11 TMA Get Number of Subunits . 42
6.8.12 3GPP Clear Active Alarms and Get Alarm Status . 43
6.8.13 TMA Get Supported Non-Linear Gain Values . 43
7 Unknown elementary procedures . 44
Annex A (normative): Return codes for secondary devices . 45
Annex B (normative): Assigned fields for additional data . 46
Annex C (normative): Procedure sequence for download of software to a secondary device. 49
Annex D (informative): Overview of elementary procedures. 50
Annex E (informative): I-frame and INFO-field format . 51
Annex F (Informative): Assigned fields for additional data coding for operating bands . 52
Annex G (informative): Change History . 55
History . 56

ETSI
3GPP TS 37.466 version 15.5.0 Release 15 5 ETSI TS 137 466 V15.5.0 (2020-01)
Foreword
rd
This Technical Specification has been produced by the 3 Generation 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 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 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 digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 37.466 version 15.5.0 Release 15 6 ETSI TS 137 466 V15.5.0 (2020-01)
1 Scope
The present document is an introduction to the 3GPP TS 37.46x series of Technical Specifications that define the Iuant
Interface. The Iuant interface is applicable for UTRAN, E-UTRAN and NG-RAN. In this specification UTRAN, E-
UTRAN and NG-RAN are denoted as "RAN", whereas the corresponding network entities Node B, eNB, en-gNB and
NG-RAN node are denoted as "RAN Node". The logical Iuant interface is an interface internal to the RAN Node and
defined to reside between the implementation specific O&M function and the RET antennas together with the TMAs
control unit function of the RAN Node.
The present document is applicable for UTRAN, E-UTRAN and NG-RAN and specifies the Remote Electrical Tilting
Application Part (RETAP) and the Tower Mounted Amplifier Application Part (TMAAP). In this specification UTRAN,
E-UTRAN and NG-RAN are denoted as "RAN", whereas the corresponding network entities Node B, eNB, en-gNB
and NG-RAN node are denoted as "RAN Node". RETAP supports the functions of the Iuant interface between the
implementation specific O&M transport function and the RET Antenna Control unit function, TMAAP supports the
functions of the Iuant interface between the implementation specific O&M transport function and the TMA control
function.
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-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 to the latest version of that document in the same
Release as the present document.
[1] Void
[2] Void
[3] 3GPP TS 37.462: "Iuant Interface: Signalling Transport".
[4] 3GPP TS 37.461: "Iuant Interface: Layer 1".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply.
Active alarm: An alarm which has an alarm state that has been raised, but not cleared
Alarm: Persistent indication of a fault
Alarm code: A code that identifies a specific alarm. The alarm code set is a subset of the return code set. The alarm
codes are listed in annex A of this TS
Alarm state: A condition or state in the existence of an alarm. Alarm states are raised and cleared
ASCII character: A character forming part of the International Reference Version of the 7-bit character set defined in
ISO/IEC 646:1991
Calibrate: Exercise the antenna drive unit over its entire range of travel to ensure fault-free operation and synchronise
the measured and actual beam tilt of the antenna
ETSI
3GPP TS 37.466 version 15.5.0 Release 15 7 ETSI TS 137 466 V15.5.0 (2020-01)
Configuration data: A stored table or function defining the relationship between the physical position of the drive and
electrical beam tilt
Data type: A definition determining the value range and interpretation of a series of octets. The following specified
data types are used in this TS:
Name: Definition:
AlarmCode 1 octet unsigned enumerated code
All AlarmCode values are listed in annex A of this TS
FieldNumber 1 octet unsigned enumerated code
All field number values are listed in annex B of this TS
ProcedureCode 1 octet unsigned enumerated code
ReturnCode 1 octet unsigned enumerated code
All ReturnCode values are listed in annex A of this TS
TextString Octets with integer values in the range of 32 to 126 to be interpreted as ASCII characters

Elementary procedure: The RETAP and TMAAP protocol consists of elementary procedures (EPs). An elementary
procedure is a unit of interaction between the primary device (RAN Node) and the secondary devices (RET or TMAs
devices)
An EP consists of an initiating message and possibly a response message.
Two kinds of EPs are used:
- Class 1: Elementary procedures with response (success or failure).
- Class 2: Elementary procedures without response.
For Class 1 EPs, the types of responses can be as follows:
Successful
- A signalling message explicitly indicates that the elementary procedure has been successfully
completed with the receipt of the response.
Unsuccessful
- A signalling message explicitly indicates that the EP failed.
Class 2 EPs are considered always successful.
Error: Deviation of a system from normal operation
Fault: Lasting error condition
Little endian: The order of transmission in which the least-significant octets of a multi-octet representation of a number
are transmitted first. Little endian only applies to binary integer representations
MaxDataReceiveLength: SecondaryPayloadReceiveLength minus 3 octets (see subclause 4.8.1 in TS 37.462 [3])
MaxDataTransmitLength: SecondaryPayloadTransmitLength minus 3 octets (see subclause 4.8.1 in TS 37.462 [3])
Procedure code: A code identifying an elementary procedure
Reset: A process by which the device is put in the state it reaches after a completed power-up
Return code: A code which defines information about the outcome of an elementary procedure execution
Tilt (also downtilt, tilt angle, beamtilt): The elevation angle between the direction orthogonal to the antenna element
axis and the maximum of its main beam in the elevation plane. A positive electrical tilt angle means that the antenna
beam is directed below the direction orthogonal to the antenna axis. An antenna has separate values for electrical and
mechanical tilt. The mechanical tilt is fixed by the geometry of the installation. In this TS the tilt referred to is always
the electrical tilt unless otherwise stated
Tilt value: A signed integer used in elementary procedures to define the electrical tilt setting of the antenna. The tilt
value is 10 times the antenna electrical tilt angle in degrees.
ETSI
3GPP TS 37.466 version 15.5.0 Release 15 8 ETSI TS 137 466 V15.5.0 (2020-01)
TMA: A TMA comprises a low noise amplifier together with its control and monitoring electronics and optional
antenna modem.
TMA subunit: A TMA may comprise more than one TMA subunit. All TMA subunits within one TMA have the same
HDLC address and are addressable by an index via the application layer procedures.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
EP Elementary Procedure
HDLC High-Level Data Link Control
RET Remote Electrical Tilting
TMA Tower Mounted Amplifier
RETAP Remote Electrical Tilting Application Part
TMAAP Tower Mounted Amplifier Application Part
TCP Time-Consuming Procedure
4 General
4.1 Procedure specification principles
The principle for specifying the procedure logic is to specify the functional behaviour of the RET antenna control unit
and TMA Subunits exactly and completely. The RAN Node functional behaviour is left unspecified.
The following specification principles have been applied for the procedure text in clause 6:
- The procedure text discriminates between:
1) Functionality which "shall" be executed
The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain
condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the
REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report
unsuccessful outcome for this procedure, containing an appropriate cause value.
2) Functionality which "shall, if supported" be executed
The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under
a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the
receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the
not supported functionality.
4.2 Forwards and backwards compatibility
The forwards and backwards compatibility of all versions of the protocol shall be assured by a mechanism in which all
current and further messages will not be changed in the future. These parts can always be decoded regardless of the
standard version.
New functionalities are added into the specification by introducing new procedures and thus the existing messages are
not changed in the future.
4.3 Multi-antenna units
The RETAP elementary procedures are split into a single-antenna oriented part, a multi-antenna oriented part and a
common part for both device types in order to support RET units controlling single- or multi-antenna devices. The RET
unit responds, upon request, the number of antennas it controls. All multi-antenna oriented elementary procedures
include a parameter stating which antenna the elementary procedure addresses. Antennas are numbered 1 and upwards.
ETSI
3GPP TS 37.466 version 15.5.0 Release 15 9 ETSI TS 137 466 V15.5.0 (2020-01)
4.4 Integer representation
Multi-octet integer values are transmitted in little endian order. Signed integers are represented as 2-complement values.
4.5 TMA Subunits
TMA subunits shall be numbered starting with 1 and proceeding upwards. The error message format for TMA
procedures follows that of multiple RET devices.
5 Services expected from signalling transport
RETAP and TMAAP requires an assured in-sequence delivery service from the signalling transport and notification if
the assured in-sequence delivery service is no longer available.
5.1 Elementary procedure format
Layer 2 provides a full-duplex link for the transmission of RETAP and TMAAP messages.
There are two types of RETAP and TMAAP elementary procedures:
Class 1: Initiating messages are sent either from the primary to a secondary device, or from a secondary to the primary
device, in order to initiate some action within the receiving device. The other device sends a response message
completing the procedure.
Class 2: Initiating messages are sent either from the primary to a secondary device, or from a secondary to the primary
device. No response message is expected.
All RETAP and TMAAP messages use the same basic format:
Table 5.1.1: Basic format for all RETAP and TMAAP messages
Elementary procedure Number of data octets Data
1 octet 2 octets MaxDataReceiveLength or
MaxDataTransmitLength.
NOTE: Response messages have the same basic format as initiating messages. The elementary procedure code
shall be the same in the response message as in the associated initiating message.
5.1.1 Initiating message
The data part of an initiating message may contain parameters as specified in clause 6 of this TS.
5.1.2 Response message
Elementary procedures shall, unless otherwise specified, provide a response message within 1 second. The response
time is measured from the time the message frame was received by the transport layer to the time the response message
is ready for transfer by the transport layer.
If the class1 elementary procedure requested by the initiating message was successfully executed, the response message
data part from a single-antenna device shall contain return code . Additional information may follow in the data
part. The response message data part from a multi-antenna device starts with the antenna number followed by return
code and optional additional information.
If the elementary procedure requested by the initiating message was not successfully executed, the response message
data part from a single-antenna device shall contain return code .
ETSI
3GPP TS 37.466 version 15.5.0 Release 15 10 ETSI TS 137 466 V15.5.0 (2020-01)
The following octet shall contain a second return code which describes why the execution of the requested procedure
failed. The response message data part from a multi-antenna device starts with the antenna number followed by return
code and a second return code which describes why the execution of the requested procedure failed.
In some situations an initiating message can cause a change of operating conditions, for instance a SetTilt procedure
might cause a RET device to discover that an adjuster is jammed or that a previously jammed adjuster works normally
again. In these cases an alarm procedure reporting the change of operating conditions shall be used in addition to the
regular or return codes in response message.
A complete annotated table of all return codes with their corresponding hexadecimal numbers is provided in annex A of
this TS.
Return codes marked with an X in the Alarm column of annex A in this TS are used to report operating conditions in
alarm procedures (see subclauses 6.6.5 and 6.7.6 for details).
6 Control elementary procedures
6.1 State model
The state model describing the secondary device is shown in figure 6.1 with procedures written in italic.
The relation to the connection state model for layer 2 can be found in TS 37.462 [3].

Link Establishment from state
AddressAssigned, see ref. [3]
Application software is
Application software is
missing
available
DownloadStart
All other Elementary
OperatingMode
DownloadMode
Procedures except for
DownloadApplication
DownloadEnd or
and DownloadEnd
ResetSoftware
GetInformation,
DownloadStart or
to state NoAddress, see ref. [3]
DownloadApplication
Figure 6.1: State model for the Secondary device
If an application software is not missing the secondary device enters the state OperatingMode.
If an application software is missing, the secondary device enters the state DownloadMode. In this state only software
download functionality is supported in order to restore the application software.
The primary device will be notified that the secondary device has entered the state DownloadMode when a procedure
which only is supported in the state OperatingMode fails with the return code WorkingSoftwareMissing.
If no software download functionality is supported, then only the state OperatingMode for the secondary device is
supported.
ETSI
3GPP TS 37.466 version 15.5.0 Release 15 11 ETSI TS 137 466 V15.5.0 (2020-01)
6.2 General procedure handling
6.2.1 Alarms
When a fault is detected, the corresponding alarm state shall be changed to state raised by the secondary device. When
the fault no longer exists, the corresponding alarm state shall be changed to state cleared by the secondary device.
Alarm changes are reported through the AlarmIndication or AntennaAlarmIndication elementary procedures. Whenever
an AlarmIndication or AntennaAlarmIndication elementary procedure message is transmitted, it shall contain all the
alarm states changed that have not yet been reported as described in subclauses 6.6.5 and 6.7.6.
All alarm states shall be cleared by any type of reset.
6.2.2 Procedure message interpretation
The following message interpretation rules shall apply to a secondary device in the order mentioned:
- Any message shorter than 3 octets shall be disregarded. In case of Multi-Antenna-Procedures or TMA-
Procedures, which uses a subunit field, any messages shorter than 4 octets shall be disregarded;
- 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 device 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 message 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 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 inconsistent 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 state 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 in table 6.2.3.1:
ETSI
3GPP TS 37.466 version 15.5.0 Release 15 12 ETSI TS 137 466 V15.5.0 (2020-01)
Table 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
Get Alarm Status No mandatory
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 specific procedure vendor specific optional
Single-Antenna Procedure Set
Set Device Data No optional
Get Device Data No optional
Calibrate Yes disallowed
Send Configuration Data No disallowed
Set Tilt Yes disallowed
Get Tilt No optional
Alarm Indication No optional
Multi-Antenna Procedure Set
Antenna 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 Status 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
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 message 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
supported 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 Antenna 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 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 described in
subclause 6.6. Table 6.3.3 lists all RETAP elementary procedures specific for multi-antenna device types described in
ETSI
3GPP TS 37.466 version 15.5.0 Release 15 13 ETSI TS 137 466 V15.5.0 (2020-01)
subclause 6.7. Table 6.3.4 lists all TMAAP elementary procedures specific for TMA device types described 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 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 mandatory 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: RETAP Elementary procedure set for single-antenna device type
Elementary procedure Requirement Comment
Calibrate Mandatory
Send 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 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
3GPP TS 37.466 version 15.5.0 Release 15 14 ETSI TS 137 466 V15.5.0 (2020-01)
Table 6.3.4: TMAAP elementary procedure set for TMA devices
Elementary procedure Requirement Comment
TMASetMode Optional Shall only be supported if the TMA
subunit supports bypass mode
TMAGetMode Mandatory
TMAGetSupportedFunctions Mandatory
TMASetGain Optional Shall only be supported if the TMA
subunit supports variable gain
TMAGetGain Mandatory
TMASetDeviceData Mandatory
TMAGetDeviceData Mandatory
TMAAlarmIndication Mandatory
TMAClearActiveAlarms Mandatory
TMAGetAlarmStatus Mandatory
TMAGetNumberOfSubunits Mandatory
TMAGetSupportedNonLinearGainValues Optional Shall only be supported it the TMA
subunit supports variable gain with non-
linear steps
6.4 Description of elementary procedures
Table 6.4.1: Description of elementary procedures
Name:
The name used to refer to the elementary procedure
Code: Issued by: Procedure class: DownloadMode state: Power mode:
The code is defined Primary device or Class 1 or Class 2 Defines whether the Defines the
here. All other code secondary device procedure shall be secondary device
references are supported in the power consumption
informative DownloadMode state. as described in TS
37.461 [4] during the
execution of the
elementary
procedure.
Table 6.4.2: Initiating and response message parameters and format
Number Length Type Description
The enumerated order in The length of the The data type used in the Description of the
which the parameter parameter, in number of parameter. parameter.
occurs in the data field of octets, if defined.
the message. The first
number is 1.
Table 6.4.3: Response message parameters and format for common class 1
elementary procedures upon error
Number Length Type Description
1 1 octet ReturnCode Return code FAIL
2 1 octet ReturnCode Reason for failure

Table 6.4.4: Response message parameters and format for single-antenna class 1 elementary
procedures upon error
Number Length Type Description
1 1 octet ReturnCode Return code FAIL
2 1 octet ReturnCode Reason for failure

ETSI
3GPP TS 37.466 version 15.5.0 Release 15 15 ETSI TS 137 466 V15.5.0 (2020-01)
Table 6.4.5: Response message parameters and format for multi-antenna class 1 and TMA subunit
class 1 elementary procedures upon error
Number Length Type Description
1 1 octet Unsigned integer Antenna number or TMA
subunit number
2 1 octet ReturnCode Return code FAIL
3 1 octet ReturnCode Reason for failure

NOTE 1: The response message in the elementary procedure AntennaGetAntennaNumber, has the format given in
table 6.4.4, although it is defined as a multi-antenna class 1 elementary procedure.
NOTE 2: The response message in the elementary procedure TMAGetNumberOfSubunits has the
...