RET Sector ID & MHA ID Naming Convention

2-July-2013 Version 7 OM37767 Author RAE National / updated by Kerry Owens

Introduction
In order to standardise the sector ID for both Kathrein and Andrew CCU across multi technologies nationally, the new sector ID naming convention is introduced By standardising all sector ID, the E-Tilt audit on each sector per technology will be more efficient Sector ID is a maximum 31-charater string which provide both concise operation and engineering information OJS06112_11-J_L18G18_AH01 In case of multi technologies or frequency bands running on same RET the string will have an extra 3 characters per additional technology/frequency band.

Current Sector ID on CCU

No existing naming convention Different installers with different formats, some information may not be captured Difficult for text post-processing as well as extracting the information

New Sector ID Naming Convention

OJS06112_11-J_L18G18_AH01

Lead Operator
O for Optus V for VHA N for no lead operator

eJV project may use Lead Operator approach on CCU configuration which means only the Lead Operator can modify the CCU/RET configuration. Nothing has been confirmed yet at this stage, Optus is used as default lead operator until further notice from eJV project

New Sector ID Naming Convention

OJS06112_11-J_L18G18_AH01
SSNNNNN indicator of site

Use JV number if it is available (for JV / eJV sites). Otherwise, use Optus number.
SS: 2 letters to indicate if using JV or Optus number for NNNNN
JA or AA for Adelaide JB or BB for Brisbane JC or SS for Canberra JD or DD for Darwin JH or HH for Hobart JM or MM for Melbourne JP or PP for Perth JS or SS for Sydney

NNNNN: Using 4 digits of JV site ID or 4 digits Optus site ID as per SS indicated with additional leading zero to accommodate future growth.

To accommodate the eJV project and JV sites the JV number format is used for the sector ID. This will enable the sector ID to be interpreted correctly by VHA. When an Optus site does NOT have a JV number, the city indicator of Optus site ID is required to be repeated (e.g. Optus site ID S0001 should be changed to SS00001, and include additional leading zero).

New Sector ID Naming Convention

OJS06112_11-J_L18G18_AH01

Sector Antenna Owner Number (SAO) S Sector Number (1 9) A Antenna Number in Sector (1; 2; 3; 4) O Antenna Owner (O Optus; V VHA; J Joint)

This is used for identify which operator will be affected if there is E-tilt change. Current U21 JV sites are with shared antenna system for both Optus and VHA. This may be changed in the eJV project which would introduce a multi-port (to separate 2 operators) antenna within one physical hardware. Need further confirmation from eJV project

New Sector ID Naming Convention

OJS06112_11-J_L18G18_AH01
TFF to indicate the technology and frequency associate with the sector and RET

If UMTS900 and GSM900 co-exist, use U09 If LTE1800 and GSM1800 co-exist, use L18
G for GSM U for UMTS L for LTE

T: Technology

FF: spectrum (must have leading 0)

07 (700MHz) 08 (800MHz) 09 (900MHz) 18 (1800MHz) 21 (2100MHz) 23 (2300MHz) 26 (2600MHz)

In case a RET has multi technologies and/or frequency band, additional 3-character string of TFF(s) may be appended in the naming convention one after the other

New Sector ID Naming Convention

Each pair of cross polar ports on each antenna forms a segment. The electrical downtilt mechanism controls the segment and therefore both ports simultaneously. So for a 12 port antenna we have 6 segments, 2 low band and 4 high band. A 10 port, five segments with 1 low band, 4 high band and so on.

New Sector ID Naming Convention

OJS06112_11-J_L18G18_AH01

D:Diversity
A - Diversity (2 way or SISO) B - MIMO C - MIMO (if 2nd RRU deployed)

For antenna with 2 TX/RX diversity use A When MIMO is deployed it takes precedence For MIMO 4X4 Use B on both segments If second RRU deployed for MIMO 4x4 use C on all 4 segments

New Sector ID Naming Convention

OJS06112_11-J_L18G18_AH01

Band and segment in use For 12 port show which antenna element.

12 Port ID L11 H12 H13 L21 H22 H23 Band/Segment Band/Segment 1 Antenna 1 Band/Segment 2 Antenna 1 Band/Segment 3 Antenna 1 Band/Segment 1 Antenna 2 Band/Segment 2 Antenna 2 Band/Segment 3 Antenna 2

10 Port ID L01 H02 H03 H04 H05 Band/Segment Band/Segment 1 Band/Segment 2 Band/Segment 3 Band/Segment 4 Band/Segment 5

6 Port ID L01 H02 H03 Band/Segment Band/Segment 1 Band/Segment 2 Band/Segment 3

4 Port ID L01 H02 Band/Segment Band/Segment 1 Band/Segment 2 OR H01 H02 Band/Segment 1 Band/Segment 2

2 Port ID L01 Band/Segment Band/Segment 1

OR H01 Band/Segment 1

MHA ID Naming Convention

Similar to the RET information the MHAs can be identified using a string with a consistent format to the sector ID. E.g. OJS06112_11-J_L18G18_1
Optus Lead Site ID JS6112 Sector 1, Antenna 1, shared MHA LTE1800, GSM1800 Port 1

Example
Information can be extracted from the sector ID E.g. OJS06112_11-J_L18_AH01
Optus Lead Site ID JS06112 Sector 1, Antenna 1, shared LTE1800 Diversity A High Band Segment 1

Example with multiple Technologies and/or

Frequency band
An naming convention example of multi technologies running on same RET may look like this E.g. OJS06112_12-V_L18G18_BH01
Optus Lead Site ID JS06112 Sector 1, Antenna 2, VHA LTE1800, GSM1800 Diversity B High band Segment 1

Where to Modify the Sector ID

For Kathrein CCU
Input the Sector ID under Sector ID

Where to Modify the MHA ID

For Kathrein CCU
Input the MHA ID under Sector ID

Where to Modify the Sector ID

For Andrew CCU
Input the Sector ID under Base Station ID

Where to Modify the MHA ID

For Andrew CCU
Input the MHA ID under Base Station ID