ETSI TS 125 463-2007 Universal Mobile Telecommunications System (UMTS) UTRAN Iuant interface Remote Electrical Tilting (RET) antennas Application Part (RETAP) signalling《全球移动通信系统(U.pdf

1、 ETSI TS 125 463 V7.5.0 (2007-03)Technical Specification Universal Mobile Telecommunications System (UMTS);UTRAN Iuant interface: Remote Electrical Tilting (RET)antennas Application Part (RETAP) signalling (3GPP TS 25.463 version 7.5.0 Release 7)ETSI ETSI TS 125 463 V7.5.0 (2007-03) 1 3GPP TS 25.463

2、 version 7.5.0 Release 7 Reference RTS/TSGR-0325463v750 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 78

3、03/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference ver

4、sion is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of st

5、atus. 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: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notific

6、ation No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered fo

7、r the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 125 463 V7.5.0 (2007-03) 2 3GPP

8、TS 25.463 version 7.5.0 Release 7 Intellectual 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

9、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 (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR

10、 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. Foreword This

11、 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, UMTS identities or GSM identities. These should be interpreted as being references to the correspondin

12、g ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 125 463 V7.5.0 (2007-03) 3 3GPP TS 25.463 version 7.5.0 Release 7 Contents Intellectual Property Rights2 Foreword.2 Foreword.5 1 Scope 6 2 Ref

13、erences 6 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .8 4 General .8 4.1 Procedure specification principles8 4.2 Forwards and backwards compatibility8 4.3 Multi-antenna units.8 4.4 Integer representation.8 5 Services expected from signalling transport.9 5.1 Elementary proce

14、dure 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 .10 6.2.1 Alarms 10 6.2.2 Procedure message interpretation .11 6.2.3 Parallel procedure handling 11 6.3 Overview of elementary procedures.12 6.4 De

15、scription of elementary procedures14 6.5 Common elementary procedures15 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 Test18 6.5.7 Void 19 6.5.8 Void 19 6.5.9 Read User Data .19 6.5.10 Write User Data 20

16、6.5.11 Download Start .21 6.5.12 Download Application21 6.5.13 Download End 22 6.5.14 Vendor specific procedure 23 6.6 Single-antenna elementary procedures.23 6.6.1 Calibrate23 6.6.2 Send Configuration Data 24 6.6.3 Set Tilt 25 6.6.4 Get Tilt25 6.6.5 Alarm Indication.26 6.6.6 Set Device Data 27 6.6.

17、7 Get Device Data27 6.7 Multi-antenna elementary procedures 28 6.7.1 Antenna Calibrate .28 6.7.2 Antenna Set Tilt29 6.7.3 Antenna Get Tilt .30 ETSI ETSI TS 125 463 V7.5.0 (2007-03) 4 3GPP TS 25.463 version 7.5.0 Release 7 6.7.4 Antenna Set Device Data30 6.7.5 Antenna Get Device Data .31 6.7.6 Antenn

18、a 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 7 Unknown elementary procedures.35 Annex A (normative): Return codes for secondary devices .36 Annex B (normative): Assigned

19、fields for additional data .37 Annex C (normative): Procedure sequence for download of software to a secondary device.38 Annex D (informative): Overview of elementary procedures.39 Annex E (informative): Change history .40 History 41 ETSI ETSI TS 125 463 V7.5.0 (2007-03) 5 3GPP TS 25.463 version 7.5

20、.0 Release 7 Foreword 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 present doc

21、ument, 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 con

22、trol. 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 ETSI TS 125 463 V7.5.0 (2007-03) 6 3GPP TS 25.463 version 7.5.0 Rele

23、ase 7 1 Scope The present document specifies the Remote Electrical Tilting Application Part (RETAP) between the implementation specific 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 ca

24、use 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

25、 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 describ

26、ed 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 i

27、t 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 respon

28、se 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 sh

29、all 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 ETSI TS 125 463 V7.5.0 (2007-03) 123GPP TS 25.463 version 7.5.0 Release 7 Table 6.2.3.1: Definition of TCPs and the execution of procedures in parall

30、el to a TCP Elementary Procedure TCP Execution in parallel to a TCP Common Procedure Set (Reserved) Reset Software no mandatory 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 option

31、al 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 D

32、ata 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

33、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 pr

34、ocedure 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 “disall

35、owed” 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 f

36、ailure. 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 tha

37、n 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. 6.3 Overview of elementary procedures The s

38、et of elementary procedures for RET antenna 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 elementary procedures specific for single-antenna devi

39、ce types described in subclause 6.6. Table 6.3.3 lists ETSI ETSI TS 125 463 V7.5.0 (2007-03) 133GPP TS 25.463 version 7.5.0 Release 7 all elementary procedures specific for multi-antenna device types described in subclause 6.7. subclause 6.4 describes how to interpret the elementary procedure defini

40、tions in subclauses 6.5 to 6.7. 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

41、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 m

42、andatory 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: Elementary procedure set for single-antenna device type Elementary procedure Requirement Comment Cali

43、brate 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: Elementary procedure set for multi-antenna device type Elementary procedure Requirement Comment Antenna Calibrate mandat

44、ory 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 An

45、tennas mandatory ETSI ETSI TS 125 463 V7.5.0 (2007-03) 143GPP TS 25.463 version 7.5.0 Release 7 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: The code is defined here. All other code reference

46、s are informative Issued by: Primary device or secondary device Procedure class: Class 1 or Class 2 DownloadMode state: Defines whether the procedure shall be supported in the DownloadMode state. Power mode: Defines the secondary device power consumption as described in 4 during the execution of the

47、 elementary procedure. Table 6.4.2: Initiating and response message parameters and format Number Length Type Description The enumerated order in which the parameter occurs in the data field of the message. The first number is 1. The length of the parameter, in number of octets, if defined. The data

48、type used in the parameter. Description of the parameter. 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

49、 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 Table 6.4.5: Response message parameters and format for multi-antenna class 1 elementary procedures upon error Number Length Type Description 1 1 octet Unsigned integer Antenna number 2 1 octet ReturnCode Return code FAIL 3 1 octet ReturnCode Reason for failure NOTE: The response message in the elementary procedure AntennaGetAntennaNumber, has the format given in table 6.4.4, although i