RET Naming Standard 101918

LTE RET Naming Implementation – Job
Aid
ATT-JA-WIRELESS-000-102-194 Issue 9.0 10/19/2018
Overview
This document provides instructions, implementation and examples for the LTE RET standard
naming convention.
AT&T CONFIDENTIAL & PROPRIETARY Page 1 of 62

Use pursuant to Company instructions © 2014 AT&T
RET Implementation – Job Aid
Table of Contents
1. About This Document ............................................................................................................................ 7
1.1 General Objective ....................................................................................................................... 7
1.2 Audience ..................................................................................................................................... 7
1.3 Related Documentation............................................................................................................... 7
1.4 Acronyms and Terms .................................................................................................................. 7
1.5 Trademarks ................................................................................................................................. 8
1.6 Contacts ...................................................................................................................................... 8
2. Tower crew RET/TMA Installation Check list ........................................................................................ 9
3. LTE RET .............................................................................................................................................. 10
4. ATT Naming Convention for “RET NAME” in OSS (ENM/NetAct) ...................................................... 11
4.1 Convention: USID ..................................................................................................................... 12
4.2 Convention: CellId1/CellId2/CellId3 .......................................................................................... 13
4.3 Convention: AntPos .................................................................................................................. 14
4.4 Convention: FreqBand .............................................................................................................. 15
4.5 Convention: Tech ...................................................................................................................... 16
4.6 Convention: Delimiter/Delimiter................................................................................................. 17
4.7 Convention: CELLNAME........................................................................................................... 18
4.8 ATT Naming Convention for “RET NAME” in RET Actuator: BaseStationID or SectorID ....... 19
5. Write “RET NAME” in the following locations: ..................................................................................... 20
5.1 Powerwave MCU Screenshot ................................................................................................... 21
5.2 Andrew Teletilt Controller Screenshot ...................................................................................... 22
5.3 Kathrein Screenshot .................................................................................................................. 23
6. RET Naming Convention with CELLNAME ......................................................................................... 24
7. AISG Fields ......................................................................................................................................... 26
8. Configuration Examples ...................................................................................................................... 27
8.1 Common Daisy-Chaining Configurations for using RET Name .................................................. 28
8.2 LTE Plumbing ............................................................................................................................ 29
8.3 Scenarios .................................................................................................................................. 30
8.4 Example A ................................................................................................................................. 31
8.5 Example B ................................................................................................................................. 32
8.6 Example C ................................................................................................................................. 33
8.7 Typical Configurations: Multi-Band / BiSector Antenna ............................................................ 34
8.8 RET Connections via LTE-RRU (per Sector)............................................................................ 35

9. NOKIA NETACT - Checking and Modify RETSubUnit properties via NetAct/CM Editor .................... 36
9.1 Step 1 ........................................................................................................................................ 37
9.2 Step 2 ........................................................................................................................................ 38
9.3 Step 2 (continue) ....................................................................................................................... 39
10. ERICSSON – Checking and Modify RETSubUnit MO via ENM Application Launcher/Network
Explorer ............................................................................................................................................... 40
10.1 Step 1 ........................................................................................................................................ 41
10.2 Step 2 ........................................................................................................................................ 42
10.3 Step 3 ........................................................................................................................................ 43
10.4 Step 4 ........................................................................................................................................ 44
Repeat Steps for remaining RETs .................................................................................................... 44
11. RET Name Deployment in Nokia NetAct ............................................................................................ 45
11.1 Step 1 ........................................................................................................................................ 46
11.2 Step 2 ........................................................................................................................................ 47
11.3 Step 3 ........................................................................................................................................ 48
11.4 Step 4 ........................................................................................................................................ 49
11.5 Step 5 ........................................................................................................................................ 50
11.6 Step 6 ........................................................................................................................................ 51
11.7 Step 7 ........................................................................................................................................ 52
11.8 Step 8 ........................................................................................................................................ 53
11.9 Step 9 ........................................................................................................................................ 54
12. RET Name Deployment in Ericsson OSS ........................................................................................... 55
12.1 CLI Commands to change or get RET Naming in ENM ........................................................... 56
12.2 CLI Commands to change or get the RET label from ‘userLabel’ in ENM ............................... 57
12.3 CLI Commands to change or get the RET label from ‘userLabel’ in ENM (continue) .............. 58
12.7 Another way to execute changes in bulk .................................................................................. 62
Document Revision History

This table identifies content revisions made to this document.
Date Rev Revision Description Writer Sponsor
06/03/2014 1.0 Initial Document Release Anthony DiRaimo TBD

10/29/2014 2.0 Added the OSS Naming Appendix Anthony DiRaimo TBD

03/10/2015 3.0 Frequency Band Update Pg. 8 & 12 Anthony DiRaimo TBD
1/20/2016 4.0 RACI changed Cecilia Nguyen TBD
Contacts changed
Added Section 3 – LTE RETs
Section 4 – AntPos - added:
• “-“ unknown antenna position
Section 4 – FreqBand – modified:
• 700 MHz
• 700 MHz & 850 MHz combined
• 2300 MHz (WCS)
Section 4 – Tech - added:
• F – License Protection/FCC
Compliance
Added Section 6 - Future RET Naming
Convention
Added Section 8.2 - Common Daisy-
Chaining Configurations for using Future
RET Naming Convention
Removed Section 7 - Differences
between Job Aid and ATT-002-125 v9
documentation
1/16/2017 5.0 • Updated FirstNet (Band 14) Cecilia Nguyen TDB
naming
• Updated FWLL note
1/23/2018 6.0 Update Antenna Positions – Section 4 Cecilia Nguyen TDB
Modify/Update RET Naming Convention
• Nokia/NetAct
• Ericsson ENM
• Impact:
o Sections 4 – 6
o Sections 8.1 – 8.2
o Sections 9.7
o Sections 14.1 – 16.8
3/28/2018 7.0 • Update Section 2. Tower crew Cecilia Nguyen TDB
RET/TMA Installation Check
List
• Update Section 4 – 4.7 ATT
Naming Convention for “RET
NAME” in OSS (ENM/NetAct)
and ‘Tech’ table
• Add 4.8 ATT Naming
Convention for “RET NAME” in
RET Actuator: BaseStationID
or SectorID
• Impact:
o Sections 5 – 5.3
• Add note to Section 6

• Add note to Section 8.1

• Update RET NAME screenshot
on Section 8.3
• Update Sector 8.4
• Update page 53
8/15/2018 8.0 Add new FreqBand for RET Naming Cecilia Nguyen TBD
Convention
• 700 MHZ B/C, Band 14, and
850 MHz combination
• Impact
Section 4 - 6
Update RACI
Remove ALCATEL- LUCENT - Checking
RETSubUnit properties via 5620 GUI
Remove RET Name Deployment in
Alcatel-Lucent OSS
Remove Retrieve Workorder from WPS
to 5620 SAM Client
10/19/2018 9.0 Add new FreqBand for RET Naming Cecilia Nguyen TBD
Convention
• 2100 MHz - Band 66 (AWS3)
only
• 2100 MHz (AWS1) & Band 66
(AWS3) combined
• 1900 MHz & Band 66 (AWS3)
combined
• 2300 MHz & Band 66 (AWS3)
combined
• 1900 MHz &2100 MHz (AWS1)
& Band 66 (AWS3) combined
• 1900 MHz & 2100 MHz (AWS1)
& Band 66 (AWS3) & 2300
MHz combined
• Impact
Section 4, 4.4, 4.8
RACI
This table identifies RACI team members.
Accountable Responsible Consulted Informed
Scott Whitney Cecilia Nguyen Ming Ho TBD

Tanvi Alam David Giesfeldt
Effendi Jubilee

Copyright © 2014 AT&T Intellectual Property.
All rights reserved. No part of the contents of this document may be reproduced or transmitted in any
form without the written permission of the publisher.

1. About This Document
1.1 General Objective

This document provides instructions, implementation and examples for the LTE RET standard
naming convention.
1.2 Audience
This document is intended for AT&T Mobility RF engineering, implementation and construction
engineering and operation engineering personnel and authorized personnel by AT&T Mobility
including civil vendor and contractors.
1.3 Related Documentation

[1] ATT-002-290-125 RET Guidelines
[2] ATT-002-290-581 Antenna Implementation
1.4 Acronyms and Terms

The following acronyms and terms are used in this document:
RET Remote Electrical Tilt

CCU Central Control Unit
MCU Master Control Unit
RRH Remote Radio Head
RRU Remote Radio Unit

1.5 Trademarks
The trademarks used in this document are the property of their respective owners.
1.6 Contacts
For questions or comments about this document's technical content or to request changes to
the document, contact:
Cecilia Nguyen
972-215-8806
cn2861@att.com
David Giesfeldt
414-339-0309
dg1571@att.com
Tanvi Alam
404-499-6857
ia766a@att.com
Scott Whitney
404-375-0126
sw1707@att.com

2. Tower crew RET/TMA Installation Check list
High Level Task (Not meant to be a complete list of instructions please refer to applicable MOPs/Handbooks)
Antenna installation:
 RF cabling (PIM Test / Sweep tests)
 AISG cabling
 Take pictures that clearly show labeling of devices. Save these in the site close out material.
Provision Antenna Line Devices (RET and/or TMA)
 Confirm all connected devices are AISG 2.0
 Calibrate RET actuators
 Confirm no alarms
 Set Tilts on Actuator per RF design
 Set special formatting “RET NAME” in BASESTATION ID or SECTOR ID fields for each detected
RET. See page 19 for details.
 Confirm no alarms
 Confirm TMA is set to Normal mode (not Bypass mode)
 Export RET/TMA configuration from CCU and/or capture screen shots to store in Site Close
out material.

3. LTE RET
Note: LTE RETs must be connected to the LTE RRH and controlled from LTE OSS. A 3rd-party RET
controller will not be needed for LTE RET. See section 7.1 from ATT-002-290-125 for more details on
RET connectivity via LTE RRH.

ATT-002-290-125
4. ATT Naming Convention for “RET NAME” in OSS (ENM/NetAct) Antenna Remote Electrical
Tilt (RET) Guidelines
Usage: [USID][CellId1][CellId2][CellId3][AntPos][FrequencyBand][Tech][Delimiter][Delimiter][CELLNAME]

4.1 Convention: USID
Definition:
• The Universal Site ID (USID) is intended to describe the location where all the various equipment resides.
• Notice there are typically several names associated to equipment in a given site.
• It is not tied to a particular technology.
Rules:
• USID must be 6 characters long.
• If the USID is not 6 characters long, then 0’s must be added at the beginning.
• Example:
USID=77412 this is only 5 chars. Need to pad with one 0 at the front so that it becomes “077412”
USID=823 this is only 3 chars. Need to pad with three 0’s at the front so that it becomes “000823”
USID=109845 this is exactly 6 chars. DO NOT add any 0’s at the front. Its should remain “109845”
See additional examples below
EXAMPLE Input: EXAMPLE OUTPUT:

4.2 Convention: CellId1/CellId2/CellId3
BiSector
Typical. ALPHA
ALPHA Typically found on bi-sector
Notice no other transmitter
DELTA sites where 1 antenna panel
ANT sector is connected to this ANT radiates 2 sectors. This
Antenna Segment. CellId2
example identifies Alpha and
and CellId3 have “-” to
Delta transmitting out this
indicate only 1 transmitting
sector.
Diplexer antenna segment.
ALPHA ALPHA DELTA

RRH RRH RRH
4.3 Convention: AntPos
Definition:
• AntPos is the Relative Antenna Position
• From inside the triangle looking out, the relative position counts from the left.
• Relative position values range from 1 to 9.
ALPHA
1 2 3 4 5

4.4 Convention: FreqBand
Usage: [USID][CellId1][CellId2][CellId3][AntPos][FreqBand][Tech][Delimiter][Delimiter][CELLNAME]
Definition:
• Frequency Band represents the RF frequency of the transmitter connected to this antenna segment.
• When multiple frequencies are combined (example UMTS 850 and LTE 700) to an antenna segment, use
the frequency of the newest technology (example LTE 700 was installed after the UMTS 850).

Convention: Tech
Definition:
• Tech field describes the technology of the transmitting
equipment connected to the antenna segment.
• It is necessary for RF teams to know which Technology
(technologies) is connected to this antenna segment to
ensure the correct tilt is modified.
Commonly used values:

U for UMTS RETs
L for LTE RETs

4.5 Convention: Delimiter/Delimiter
Definition:
• Delimiters is used to separate the RET Name with the CellName
• SON will parse and sync with the RET from the first 12 digits of RET Naming Convention
The Cell Naming Convention can be up to 17

characters or more. Refer to RFDS or HQ RAN
LTE Standard Naming Convention Guideline.

4.6 Convention: CELLNAME
Definition:
Example 1: Single RET; Single Cell
• CellName is to be used for market’s reference as physical links from the RET to the Cell ID
077412A—57L__NWL03818_7A_1
• CellName will be used to pull Electrical Tilt values into Atoll Database for Design
Example 2: Single RET; Multiple Cells
077412A—5KL__NWL03818_7A_1;NWL03818_8A_1
*use semicolon “;” to separate between CellNames when multiple cells are
sharing one RET

4.8ATT Naming Convention for “RET NAME” in RET Actuator: BaseStationID

or SectorID ATT-002-290-125
Antenna Remote Electrical Tilt (RET) Guidelines
Usage: [USID][CellId1][CellId2][CellId3][AntPos][FrequencyBand][Tech]

5. Write “RET NAME” in the following locations:
Kathrein CCU:
• Use the Sector ID for both singleActuator and multiActuator RETs
Powerwave MCU:
• Use the Sector field for both singleActuator and multiActuator RETs
Andrew TeleTilt
• Use the Base Station ID field for both singleActuator and MultiActuator RETs

5.1 Powerwave MCU Screenshot
1. Go to the ALD Installation page

2. Enter “RET NAME” in the Sector field.

5.2 Andrew Teletilt Controller Screenshot

5.3 Kathrein Screenshot

6. RET Naming Convention with CELLNAME
The Cell Naming Convention can be up to 17

characters or more. Refer to RFDS or HQ RAN
LTE Standard Naming Convention Guideline.
Enter “-“ if
antenna position
is unknown
❖ 025647A---7L__AKL02048_7A_1

It is recommended for markets (Ericsson and Nokia) to use the NEW RET Naming Convention. Currently, ALU markets do not
have the same capability due to the limitation of only 20 characters in the “AntennaBandClass” field under the RETSubUnit MO.
Nokia/NetAct’s ‘userNote1’ is a parameter replacement for ‘antennaBandClass’ and ‘userNote2’ for ‘remoteCellID’. The
‘userNote1’ can support the NEW RET Naming Convention.
With the NEW RET Naming Convention, markets’ engineers can use the CELLNAME appended with standard 12 characters RET
Naming Convention to:
• Pull the electrical antenna tilt value automatically into Atoll.
• Quickly sort by CELLNAME
• Easy to identify the RET connections to the CELLNAME

• Easy for audit
• Easy for scripting
• Easy parsing for self-automated validation checking

• Human friendly for customizing and sanitizing checking (less transposing)
• Increased accuracy and efficiency when making manual tilts.

7. AISG Fields
• Each RET Actuator and TMA subunit contain user definable attributes that are stored on the actuator
itself.
Sector ID
Base Station ID
Installers ID
Installation Date

8. Configuration Examples
AT&T’s “RET NAME” Convention

8.1 Common Daisy-Chaining Configurations for using RET Name

ALPHA BETA GAMMA
LO HI LO HI LO HI
AISG AISG AISG
700 1900 700 1900 700 1900

RRH RRH RRH RRH RRH RRH
Typical RET Configuration
Each Sectors RFM controls its own antenna. LO band is daisy-chained to HI band
LTE 1 LTE 2
LTE LTE UMTS ALPHA BETA GAMMA
L H L H L H L H L H L H L H L H
700
“Cell Name” 700 RRH 700
700 RRH RRH
RRH
(gray) is used
for translation Multiple Sector Daisy-Chained
Multiple Technologies Daisy-Chained Single LTE RFM controls all the different Same Technology Daisy-Chained
in ENM/NetAct
LTE RFM controls all the different technology Sectors LTE RETs Single LTE RFM controls its own sectors RETs
RETs for this one sector
SectorID: 001234A--17L__xxL01234_7A_1 SectorID: 001234A--17L__xxL01234_7A_1
SectorID: 001234A--19L__xxL01234_9A_1
SectorID: 001234A--17L__xxL01234_7A_1 SectorID: 001234A--19L__xxL01234_9A_1
SectorID: 001234B--17L__xxL01234_7B_1
SectorID: 001234A--17L__xxL01234_7A_1
SectorID: 001234A--19L__xxL01234_9A_1 SectorID: 001234B--19L__xxL01234_9B_1 SectorID: 001234A--28L__xxL01234_8A_1
SectorID: 001234A--19L__xxL01234_9A_1 SectorID: 001234A--28U SectorID: 001234C--17L__xxL01234_7C_1 SectorID: 001234A--22L__xxL01234_2A_1
SectorID: 001234A--29U SectorID: 001234C--19L__xxL01234_9C_1
8.2 LTE Plumbing

8.3 Scenarios

8.4 Example A

8.5 Example B

8.6 Example C

8.7 Typical Configurations: Multi-Band / BiSector Antenna

8.8 RET Connections via LTE-RRU (per Sector)

9. NOKIA NETACT - Checking and Modify RETSubUnit properties via

NetAct/CM Editor
NOKIA/NETACT

9.1 Step 1
Left click “ ” sign beside ‘Actual Configuration’ and repeat the same steps to get to the ‘RETU’ to see child objects.

9.2 Step 2
Left click “ ” sign beside ‘MRBTS’ and repeat the same steps to get to the ‘RETU’ to see child objects.

9.3 Step 2 (continue)

Left click “ ” sign beside ‘Actual Configuration’ and repeat the same steps to get to the ‘RETU’ to see child objects. Check
mark the ‘Modify actual value(s) to modify the RET Name in ‘UserNote1’ parameter.
Single change

10. ERICSSON – Checking and Modify RETSubUnit MO via ENM Application

Launcher/Network Explorer
ERICSSON

10.1 Step 1
Launch ‘Network Explorer’ to launch Network Elements

10.2 Step 2
Search for Network Element and launch Element Manager

10.3 Step 3
Left click on “ ” sign beside ‘Equipment’, ‘Antenna System Equipment’, ‘AntennaNearunit’, and ‘RetSubUnit’ to see child
objects and if in need to modify a single change for ‘userLabel’ – RET Name.

10.4 Step 4
For Ericsson OSS:

Verify correct 12 character RET name has been assigned to the actuator.
Note: The resulting window will include the “iuantBaseStationId:” and “iuantSectorId:” attributes that are display on the previous
screenshot. If it is a Kathrein RET, a 12 character RET name entered into the actuator during field commissioning should be displayed in the
box to the right of the “iuantSectorId:” attribute, as per below. If it is an Andrews RET, a 12 character RET name entered into the actuator
during field commissioning should be displayed in the box to the right of the “iuantBaseStationId:” attribute.
Repeat Steps for remaining RETs

1. On the left panel, click on “AntennaUnitGroup=2”, “AntennaNearUnit=x”, and “RetSubUnit=x” for Beta 700 MHz RRU and
1900 RRU
2. Repeat the same steps for Gamma 700 MHz RRU and 1900 MHz RRU
Note: The resulting of BASESTATION ID and SECTOR ID from RET motor will automatically feed the “iuantBaseStationId:” and
“iuantSectorId:”. The “userLabel” attributes to be populated by integration vendor (Ericsson, QuadgenWireless, or AT&T in-house ‘MPC’).
For NetAct:
Verify correct 12 character RET name has been assigned to the actuator.
Note: If it is a Kathrein RET, a 12 character RET name entered into the actuator during field commissioning should be displayed in the box to
the right of the “Sector ID” attribute. If it is an Andrews RET, a 12 character RET name entered into the actuator during field commissioning
should be displayed in the box to the right of the “Base station ID” attribute.
• The integration team is responsible to populate the “userLabel” or “userNote1 and userNote2” fields under
the RetSubUnit MO/Object

11. RET Name Deployment in Nokia NetAct
RET Name Deployment in Nokia NetAct

(Bulk Upload)
NOTE: At the present time SON CICO-L recognizes LTE Tech value of ‘L’ ONLY in the RET Name’s 12th character.
(Please use Tech value ‘L’ for all LTE combination options listed in the Description box for V, Y, P, Q & T)

11.1 Step 1
NetAct Home Page, open ‘Configuration’ folder and then open up the ‘CM Editor’

11.2 Step 2
In ‘CM Editor’, select all Manage Object DNs to be changed and export for modification.

11.3 Step 3
Once MO DNs selected, click on ‘Actual’ to ‘Export’ and provide a path to local drive to save the CM Manage Object DNs
from ‘Actual Configuration’

11.4 Step 4
Select all ‘Options’ to export

11.5 Step 5
Once the RET Name and CellName have been implemented in ‘userNote1’ and ‘userNote2’ parameters. Select ‘Plan’ and
‘Import’ to upload the file to ‘Opened Plans’

11.6 Step 6
The ‘Full Log’ for Managed Objects, ‘Errors’, ‘Warnings’, and ‘Audit findings’ report will be generated.
Examples:

11.7 Step 7
In ‘CM Editor’, click on “ “ next to ‘Opened Plans’ and select the work order plan for the MRBTS/RETU to see ‘Planned
value’ versus ‘Actual value’

11.8 Step 8
In CM Operations Manager, select ‘Upload’ and then ‘New Upload…’. Filter your job name and select ‘Provision…’ to activate
your plan.

11.9 Step 9
Results for Provision/Activation

12. RET Name Deployment in Ericsson OSS
RET Name Deployment in Ericsson OSS

(Bulk Upload)
NOTE: At the present time SON CICO-L will recognize LTE Tech value of ‘L’ ONLY in the RET Name’s 12th character.
(Please use Tech value ‘L’ for all LTE combination options listed in the Description box for V, Y, P, Q & T)

12.1 CLI Commands to change or get RET Naming in ENM

12.2 CLI Commands to change or get the RET label from ‘userLabel’ in ENM

12.3 CLI Commands to change or get the RET label from ‘userLabel’ in ENM (continue)




12.7 Another way to execute changes in bulk


RET Naming Standard 101918

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RET Naming Standard 101918

Uploaded by

Copyright:

Available Formats

LTE RET Naming Implementation – Job

AT&T CONFIDENTIAL & PROPRIETARY Page 1 of 62

AT&T CONFIDENTIAL & PROPRIETARY Page 2 of 62

Document Revision History

Date Rev Revision Description Writer Sponsor

06/03/2014 1.0 Initial Document Release Anthony DiRaimo TBD

AT&T CONFIDENTIAL & PROPRIETARY Page 3 of 62

AT&T CONFIDENTIAL & PROPRIETARY Page 4 of 62

• Add note to Section 8.1

Accountable Responsible Consulted Informed

Scott Whitney Cecilia Nguyen Ming Ho TBD

AT&T CONFIDENTIAL & PROPRIETARY Page 5 of 62

Copyright © 2014 AT&T Intellectual Property.

AT&T CONFIDENTIAL & PROPRIETARY Page 6 of 62

1. About This Document

1.1 General Objective

1.3 Related Documentation

1.4 Acronyms and Terms

RET Remote Electrical Tilt

AT&T CONFIDENTIAL & PROPRIETARY Page 7 of 62

AT&T CONFIDENTIAL & PROPRIETARY Page 8 of 62

2. Tower crew RET/TMA Installation Check list

AT&T CONFIDENTIAL & PROPRIETARY Page 9 of 62

AT&T CONFIDENTIAL & PROPRIETARY Page 10 of 62

AT&T CONFIDENTIAL & PROPRIETARY Page 11 of 62

4.1 Convention: USID

EXAMPLE Input: EXAMPLE OUTPUT:

AT&T CONFIDENTIAL & PROPRIETARY Page 12 of 62

4.2 Convention: CellId1/CellId2/CellId3

ALPHA ALPHA DELTA

4.3 Convention: AntPos

AT&T CONFIDENTIAL & PROPRIETARY Page 14 of 62

4.4 Convention: FreqBand

AT&T CONFIDENTIAL & PROPRIETARY Page 15 of 62

Commonly used values:

AT&T CONFIDENTIAL & PROPRIETARY Page 16 of 62

4.5 Convention: Delimiter/Delimiter

The Cell Naming Convention can be up to 17

AT&T CONFIDENTIAL & PROPRIETARY Page 17 of 62

4.6 Convention: CELLNAME

Example 2: Single RET; Multiple Cells

AT&T CONFIDENTIAL & PROPRIETARY Page 18 of 62

4.8ATT Naming Convention for “RET NAME” in RET Actuator: BaseStationID

AT&T CONFIDENTIAL & PROPRIETARY Page 19 of 62

5. Write “RET NAME” in the following locations:

AT&T CONFIDENTIAL & PROPRIETARY Page 20 of 62

5.1 Powerwave MCU Screenshot

1. Go to the ALD Installation page

AT&T CONFIDENTIAL & PROPRIETARY Page 21 of 62

5.2 Andrew Teletilt Controller Screenshot

AT&T CONFIDENTIAL & PROPRIETARY Page 22 of 62

5.3 Kathrein Screenshot

AT&T CONFIDENTIAL & PROPRIETARY Page 23 of 62

6. RET Naming Convention with CELLNAME

The Cell Naming Convention can be up to 17

AT&T CONFIDENTIAL & PROPRIETARY Page 24 of 62

• Easy to identify the RET connections to the CELLNAME

• Easy parsing for self-automated validation checking

AT&T CONFIDENTIAL & PROPRIETARY Page 25 of 62

AT&T CONFIDENTIAL & PROPRIETARY Page 26 of 62

AT&T’s “RET NAME” Convention

AT&T CONFIDENTIAL & PROPRIETARY Page 27 of 62

8.1 Common Daisy-Chaining Configurations for using RET Name