1. 2.

UMTS to GSM iRAT capability3G-2G .pptx

Introduction

This document specifies the requirements and details from an enhancements for APO and ANR INTRA regarding the ability to define andconfigure 2G neighbors.

This feature needs to be implemented in SON-5 release 6.

General description

Most of 3G operators also have 2G networks.The GSM networks are widely deployed and their coverage, in many cases, is superior to UMTS coverage. Many operators see their GSMnetwork as a “safety net” for calls, mainly voice, in places where 3G coverage is not full and deep or where the economic viability for 3G servicesis low.In such areas and borders smooth handover from 3G network to 2G network is important to keep service retainability and customers’satisfaction is voice services quality. HO from 3G to 2G can happen for 2 reasons:

when UMTS network is loaded.UMTS network coverage is too low.

Planning relations between UMTS and GSM cells can be done through offline planning but in such cases will not take into account changes in RFconditions, new added cells, outages and other phenomena affecting networks behavior. To overcome networks changes dynamic SON solutionis required to maintain the most optimized UMTS to GSM relations list for each UMTS cell in the network.

High Level Solution Description

The solution is based on an algorithm which access information only in the UMTS OSS and cells.

The solution requires that the SON database will be populated with geo-location in formation of all GSM cells in the network in addition to theUMTS cells information.

The solution is divided between first time GSM neighbors list population as part of APO-U product and ongoing optimization of the list as part ofthe Periodic Mode.

Main Algorithm and requirements

conditions prerequisites and clarifications :

Asymmetric Relations will defined ( add /delete ) only 1 way ( from 3G to 2G only) as SON is not connected to any GSM OSS. There is no connection from Cisco SON and 2G OSS - agreed with product. ( SON actions are based on "offline data" that came fromoperator ).Operator needs to supply to SON-DB from time to time CSV file with all required and necessary data for 3G 2G definition. ( for moreinformation please see in next chapter ).GSM relation weight calculation based on IRAT HO attempts - not part of release 6.Removing weak GSM neighbors and adding new ones instead ( based on counters ) - not part of release 6.

Required data from operator :

Operator needs to supply from time to time CSV file with following information about GSM layer ( depend on GSM changes )

Operator needs to upload and save the CSV file into accepted folder.

In the file header will be written "date and time creation file" ( Year/ Month / Day 00:00:00 ).

at least 3 latest files need to be saved for use as needed.

Needed information in CSV file :

CellName

Cell ID BSC ID LAC NCC BCC BCCH MNC MCC AntennaAzimuth

AntennaBeamwidth

Longitude

Latitude

1. 2. 3. 4.

1.

HERZEL35

17572X 188 25 5 4 680 03 262 120 65 -84.300 33.803

*** GSM cell without full information will not be candidate for addition as neighbor to UMTS cell.

Types of work

there are 4 types of work:

Dry run mode.APO mode Periodic modeManual mode.

for additional information please find n next chapter.

Settings for IRAT :

It is mandatory to fill the settings parameters before the application is starting to run.all

extension parameter in AOP-U: Application setting

Parameter Name Range Default Comments

Create GSM Relations Yes /No Yes This parameter is part of APO-UApplication Settings

2. New screen for IRAT application: Application settings

Parameter Name Range Default Comments

Enabled App On/ Off off

Live Run On/ Off off

Application Priority 0-100 0 App settings- Market level

Periodic mode Each 15 min /1 Hr/ Once a day Once a day App settings - Market level

Run one iteration in dry run Yes/ No No App setting , When application indry run mode, will run only oneiteration

Enable Manual IRATapplication

Yes/ No No App settings, Manualintervention

3. need to define the following hidden parameter:

Parameter Name Range Default Comments

Max distance for GSM cell 3- 30 10 Hidden parameter, configurablethrough CLI commands by AS/TS.

4. extension parameters in screen: ANR-INTER/ LMS Policies

Parameter Name Range Default Comments

GSM Relation Type E///: 0-HO_AND_CELL_RESEL, 1- RESELECTION

NSN:

For CELL DCH meas only ==> 0For SIB and CELL DCH meas==> 1For SIBbis and CELL DCH meas==> 2For SIB only ==> 3For SIBbis only ==> 4

DCH only Part of policy rule ( LMS ) - LMSper vendor

Max Number of GSM Relationper UNTS carrier

0- 32 15 Part of policy rule ( LMS ),comment : ( total gsm relationsfrom umts carriers must be lessor equal to "Max Number of

parameter ).GSM Relations"

Relation Profile Pointer to relation profileparameters

Default per vendor Part of policy rule ( LMS )

Destination ( BCCH Channels ) 0-124, 128-251, 955-1023 ,512-810 ( need ability to use ORfor bcch channels, more than 1range ).

Part of policy rule ( LMS )

Primary Yes/ No Yes In case the operator hasconnection between 1UMTSlayer to at least 2GSM layers

exp:

Source Freq Destination GSM Relation Type Max Number ofGsm Relation

Relation Profile Primary

F1 1087 512-568, 580-588 0-HO_AND_CELL_RESEL

10 Default *

F1 1087 1-124 1- RESELECTION 10 Default

5. parameters for "IRAT relation profile".

a. The IRAT relation profile is per vendor. for the next release we support only for E/// and NSN.

b. Need the ability to edit / delete and create new profiles.

c. No rules enforced related to these parameters ( exp: difference between GSM1800/ GSM900 or difference between U2100 and U900 ).

Table A: "IRAT relation profile" for UMTS E///

Parameter name Range Step Units Default Value Comment MO

qOffset1sn { -50..50 } 1 dB 7 UtranCell/GsmRelation

selectionPriority

0-32 1 0 1- highest priority

0- no priority

comment: It isnot configurable,see in sectionxxxx

UtranCell/GsmRelation

bandIndicator 0-DCS1800

1-pcs1900

2-notapplicable/other_band

0-DCS1800 RncFunction /ExternalGsmNetwork /ExternalGsmCell

individualOffset

{ -50..50 } 1 dB 0 RncFunction /ExternalGsmNetwork /ExternalGsmCell

maxTxPowerUl { -50..33, 100 } 1 dBm 100 When set to 100,no value isincluded in SIB11for this neighbor.The UE shoulduse the valuefrom the serving UTRAN cellinstead.

RncFunction /ExternalGsmNetwork /ExternalGsmCell

qRxLevMin { -115..-25, 100 } 2 dBm 100 When set to 100,no value isincluded in SIB11for this neighbor.The UE shoulduse the valuefrom the serving UTRAN cellinstead.

RncFunction /ExternalGsmNetwork /ExternalGsmCell

Table B: "IRAT relation profile" for UMTS NSN

ParameterName

Range Step Unit Default Value Gui Value/Internal value

Comments MO

AdjgBandIndicator

No (0), GSM1900 (1)

None None 0 gui ==>internalNo ==> 0GSM 1900==> 1

ADJG

AdjgTxPwrMaxRACH

0... 33 1 dBm None internal_value= gui_value

ADJG

AdjgTxPwrMaxTCH

0... 43 1 dBm None internal_value= gui_value

ADJG

NrtHopgIdentifier

1... 100 1 None None Default valueis not possible

ADJG

RtHopgIdentifier

1... 100 1 None None Default valueis not possible.

ADJG

AdjgHCSpriority

0... 7 1 None 0 internal_value= gui_value

HOPG

AdjgHCSthreshold

-110... -37 1 dBm -110 internal_value= (gui_value +110)

HOPG

AdjgMinRxLevNCHO

-110... -47 1 dBm -95 internal_value= gui_value

HOPG

AdjgPenaltyTime

0... 60 1 Sec 0 internal_value= gui_value /10

HOPG

AdjgPenaltyTimeNCHO

0... 60 1 Sec 10 internal_value= gui_value

HOPG

AdjgPriorityCoverage

0... 7 1 None 0 internal_value= gui_value

HOPG

AdjgPrioritySLHO

0... 7 1 None 0 internal_value= gui_value

HOPG

AdjgQoffset1 -50... 50 1 dB 0 internal_value= gui_value

HOPG

AdjgQrxlevMin

-115... -25 1 dBm -101 internal_value= (gui_value -1) / 2

HOPG

AdjgRxLevMinHO

-110... -47 1 dBm -95 internal_value= (gui_value +110)

HOPG

AdjgTempOffset1

3 dB (0), 6 dB(1), 9 dB (2),12 dB (3), 15dB (4), 18dB (5), 21 dB(6), 100 dB.Infinity (7)

internal: 0....7

None dB 3 dB (0) gui ==>internal3 dB ==> 06 dB ==> 19 dB ==> 212 dB ==> 315 dB ==> 418 dB ==> 521 dB ==> 6100 dB. Infinity==> 7

HOPG

comment: NrtHopgIdentifier / RtHopgIdentifier should be same mechanism as for INTRA/ INTER.

UMTS -APO mode

1. 2. 3.

4. 5.

6. 7. 8.

9.

10.

11.

12. 13. 14.

1.

2.

New UMTS cell is identified in OSS by AppManager. APO UMTS operates on new cells only, Rehomed cells are skipped.The application shall be triggered within ~20 minutes from the time the new cell was introduced to the network.At the beginning, APO-U will try to add new INTRA relations, than INTER relations and final GSM relations in case "Create GSM

paraemeter is enabled. Relations"The application use the latest GSM- CSV file for GSM candidate relations. In case that there is no CSV file or there is any problem with this file - Alert is needed:" No GSM relations were added due to missing csvfile/ file problems".Application uses the same algorithm for GSM as it uses for APO_U INTRA relations.Cells without all mandatory data can't be candidate. Create list of GSM cells candidate by following tests: a. Search for all GSM cells in radius according to "Max Distance For Relations From Outdoor/indoor Cells (km)" parameter ( part ofAPO-U application settings ) related to new umts cell.b. Search for relevant BCCH frequencies according to LMS profile. c. It doesn't matter if the neighbor cell is on or off air since we are not connecting to GSM OSS. Comment1: Can be more than 1 GSM band for UMTS carrier. Comment2: In case that there are no candidate at all - Alert is needed:" GSM candidate not found". App uses the Geo location, Azimuth and beamwidth for source umts cell and for all GSM candidtaes in order to find overlapping betweensource and candidate triangulations.Since SON is not familiar with Propagation Delay ( time advanced ) of GSM cells, App uses: "Max distance for GSM cell" hiddenparameter in order to Determining the diameter and for UMTS cell uses "Max Distance For Relations From Outdoor/indoor Cells(km)".App will create the co-located cells and then closest intersecting cells up to "Max Number of GSM Relation per UNTS carrier" parameter or up to SIB11 limitation. In case there are 2 GSM bands, App will create GSM relation once at the time for each GSM band.App will send to Infra list of parameters per relation according to UMTS cell vendor and "IRAT Relation Profile".In case of E///, is needed to define parameter for each relation. ( 1- highest priority.... ). " selectionPriority"

Periodic Mode

SON needs to update UMTS to GSM relations from time to time according to GSM network changes like: new GSM cells, GSM rehomed cells,BCCH/ BSIC changes ect...by following method:

according to "Periodic mode" parameter, Application is looking for new CSV file in acceptable folder relative to last time that theapplication run in periodic mode. 1a. There is no new CSV file >>>> "No action is needed for IRAT"1b. There is new CSV file - goes to step 2. For each UMTS cell, application build new candidate GSM cells based on new CSV file according following steps: : Cells without all mandatory data can't be candidate.Commenta. Search for all GSM cells in radius according to "Max Distance For Relations From Outdoor/indoor Cells (km)" parameter ( part ofAPO-U application settings ) related to new umts cell.b. Search for relevant BCCH frequencies according to LMS profile.c. It doesn't matter if the neighbor cell is on or off air since we are not connecting to GSM OSS.

Comment1: Can be more than 1 GSM band for UMTS carrier. Comment2: In case that there are no candidate at all - Alert is needed:" GSM candidate not found". 3. App uses the Geo location, Azimuth and beamwidth for source umts cell and for all GSM candidtaes inorder to find overlapping between source and candidate triangulations. 4. Since SON is not familiar with Propagation Delay ( time advanced ) of GSM cells, App uses: "Max distancefor GSM cell" hidden parameter in order to Determining the diameter (The value can configure through CLI command by AS/TS.) and for UMTS cell uses: "Max Distance For Relations From Outdoor/indoor Cells (km)". 5. App creates new list based on co-located cells and then closest intersecting cells up to "Max Number of GSM Relation per UNTS carrier" parameter or up to SIB11 limitation. 6. App creates comparison between the old list and new list and has to update the GSM relations according to following main outcomes.Comments: Relation marked as "Never Remove" has the highest priority and can't be removed at all.

case A:

lists are the equal ( need to check all columns )

Example:

Oldlist:

CellName

CellID

BSCID

LAC

NCC

BCC

BCCH

MNC

MCC

AntennaAzimuth

AntennaBeamwidth

Longitude

Latitude

Newlist:

CellName

CellID

BSCID

LAC

NCC

BCC

BCCH

MNC

MCC

AntennaAzimuth

AntennaBeamwidth

Longitude

Latitude

HERZEL35

17572X

188

25

5 4 680

3 262

120

65

-84.3

33.803

HERZEL35

17572X

188

25

5 4 680

3 262

120

65

-84.3

33.803

HERZEL36

17572Y

188

25

5 5 682

3 262

240

65

-84.3

33.803

HERZEL36

17572Y

188

25

5 5 682

3 262

240

65

-84.3

33.803

Action:

"No Action is needed"

case B:

"Old list" contains the "new list" and it under the "Max Number of GSM Relation per UNTS carrier" parameter or up to SIB11 limitation.

Example:

Oldlist:

CellName

CellID

BSCID

LAC

NCC

BCC

BCCH

MNC

MCC

AntennaAzimuth

AntennaBeamwidth

Longitude

Latitude

Newlist:

CellName

CellID

BSCID

LAC

NCC

BCC

BCCH

MNC

MCC

AntennaAzimuth

AntennaBeamwidth

Longitude

Latitude

HERZEL35

17572X

188

25

5 4 680

3 262

120

65

-84.3

33.803

HERZEL35

17572X

188

25

5 4 680

3 262

120

65

-84.3

33.803

HERZEL36

17572Y

188

25

5 5 682

3 262

240

65

-84.3

33.803

HERZEL36

17572Y

188

25

5 5 682

3 262

240

65

-84.3

33.803

HERZEL37

17572Z

188

25

5 6 684

3 262

0 65

-84.3

33.803

Action:

"No Action is needed"

case C:

New relations found in "new list" and it under the " Max Number of GSM Relation per UNTS carrier" parameter or up to SIB11 limitation.

Example:

Oldlist:

CellName

CellID

BSCID

LAC

NCC

BCC

BCCH

MNC

MCC

AntennaAzimuth

AntennaBeamwidth

Longitude

Latitude

Newlist:

CellName

CellID

BSCID

LAC

NCC

BCC

BCCH

MNC

MCC

AntennaAzimuth

AntennaBeamwidth

Longitude

Latitude

HERZEL35

17572X

188

25

5 4 680

3 262

120

65

-84.3

33.803

HERZEL35

17572X

188

25

5 4 680

3 262

120

65

-84.3

33.803

HERZEL36

17572Y

188

25

5 5 682

3 262

240

65

-84.3

33.803

HERZEL36

17572Y

188

25

5 5 682

3 262

240

65

-84.3

33.803

HERZEL37

17572Z

188

25

5 6 684

3 262

0 65

-84.3

33.803

1. 2.

Create new relations from UMTS cell to GSM cell: HERZEL37Action:

case D: New relations found in "new list" and it under the " Max Number of GSM Relation per UNTS carrier" parameter or up to SIB11 limitationand one or more parameters had changed in exist cell.

Example:

Oldlist:

CellName

CellID

BSCID

LAC

NCC

BCC

BCCH

MNC

MCC

AntennaAzimuth

AntennaBeamwidth

Longitude

Latitude

Newlist:

CellName

CellID

BSCID

LAC

NCC

BCC

BCCH

MNC

MCC

AntennaAzimuth

AntennaBeamwidth

Longitude

Latitude

HERZEL35

17572X

188

25

5 4 680

3 262

120

65

-84.3

33.803

HERZEL35

17572X

188

25

3 3 680

3 262

120

65

-84.3

33.803

HERZEL36

17572Y

188

25

5 5 682

3 262

240

65

-84.3

33.803

HERZEL36

17572Y

188

25

5 5 682

3 262

240

65

-84.3

33.803

HERZEL37

17572Z

188

25

5 6 684

3 262

0 65

-84.3

33.803

Actions:

Del cell HERZEL35 and create it again with new parameters.Create new relations from UMTS cell to GSM cell: HERZEL37.

The exist list is too long and more than case E: "Max Number of GSM Relation per UNTS carrier" parameter or up to SIB11 limitation.

Save the "Never Remove" relations and then delete the GSM relations according the farthest relation from UMTS cell. Action:

7. Application will not add New GSM relations in case they marked as " Never Add".

8.. In case that there is OSS problem related to 1 relation or more then application needs to take the next candidate from the list.

9. In case there are 2 GSM bands, App will create GSM relation once at the time for each GSM band.

10. App will send to Infra list of parameters per relation according to UMTS cell vendor and "IRAT RelationProfile".

11. In case of E///, is needed to define " selectionPriority" parameter for each relation. ( 1- highest priority.... ).

Dry Run Mode:

1. Operator needs to supply and save the GSM CSV file in acceptable folder.

2. AS/TS team need to fill all required parameters and setting, including policy settings and relation profile parameters ( " Enabled App" = On," and Live Run"= off )

3. For each UMTS cell, the application needs to make comparison between "existing GSM relations list" and "new GSM relations list" accordingto main algorithm that mentioned in last chapter.

4. The outcome for dry mode mode will be only report with all recommended changes.

5. OSS commands will not be send.

Manual Mode:

1. Operator needs to supply and save the GSM CSV file in acceptable folder the moment he attend to operate the application.

2. AS/TS team need to fill all required parameters and setting, including policy settings and relation profile parameters ( " Enabled App" = On," and Live Run"= On )

3. For each UMTS cell, the application needs to make comparison between "existing GSM relations list" and "new GSM relations list" accordingto main algorithm that mentioned in last chapter.

5. OSS commands will be send according to the outcomes that mentioned in last chapter.

Comments: Relation marked as "Never Remove" has the highest priority and can't be removed at all.

Requirements from GUI:

Map Layer for GSM cells with the following information:a. Cell_ID / Cell_NAME b. azimuthc. antenna beam spand. BSIC (ncc/bcc )e. Longitude / Latitude f. BSC_ID.Ability to create and present GSM cells on map based on one or more parameters mentioned.

For each UMTS cell, is needed to add information about IRAT-neighbors in 2 forms: 1. Display Cell Neighbors on Map ( mark those cells with different color ).

In case there are more than 1 band, Is needed to distinguish between them on map.

2. Display Cell Neighbors Report with the following information:a. Count of IRAT neighbors.b. GSM Cell id.c. Distance from UMTS source cell.d. BSIC (NCC/BCC ).e. GSM Relation type ( SIB11 / DCH only ect.. ).e. Ability to represent the GSM cell on map through information table.

Ability to Search and represent GSM cell on map through "Network Element" window.Distances from the UMTS cell to its GSM NBRs shall be marked as unidirectional only.Ability to make action through the GUI ( "Never add" /"Never delete" relations from UMTS cell to GSM cell ).All GSM relations creations shall be presented in the APO SON Action report with indication of the relation being an iRAT one.All Relations shall be downloadable to external CSV report. Information in this report shall follow the SON Action GUI report.

Log:

All iRAT actions and decision shall be indicated in a log file.New file not found - no action is needed. candidate GSM cells.

Events/ Reports:

list of cells with necessary missing data (example: missing lat/ long missing data).list of cells with less "Max Of GSM Relations" due to distance threshold ( "Max Distance Relation" ).List of new GSM relation that created by the application.The number of iRAT relations added during a selected duration shall be presented as a graph.The graph information shall be available for export using CSV file.Dry Run report - list of relations that application recommended.

Policy

GSM networks operate in a number of different carrier frequency ranges:

GSM 900 / GSM 1800 MHz are used in most parts of the world: Europe, Asia, Australia, Middle East, Africa. are used in the United States, Canada, Mexico and most countries of S. America.GSM 850 / GSM 1900 MHz

Operator can work with more than 1GSM band, also can work from different UMTS carriers to different GSM bands.

example:

UMTS Band GSM band Method

F1- 1087 GSM 1800 MHz Only for IDLE

F1-1087 GSM 900 MHz DCH only

F2- 1062 GSM 900 MHz DCH and IDLE

For each operator is needed to define the policy according to operator's inputs and LMS.

For more information and relevant parameters please find in next chapter. exp for E///:

<gn:ExternalGsmCell id="80YIL1">< >gn:attributes< >1</ >gn:mnc gn:mnc< >286</ >gn:mcc gn:mcc< >33950</ >gn:lac gn:lac< >5</ >gn:bcchFrequency gn:bcchFrequency< >0</ >gn:ncc gn:ncc< >7</ >gn:bcc gn:bcc< >80YIL1</ >gn:userLabel gn:userLabel< >25977</ >gn:cellIdentity gn:cellIdentity</ >gn:attributes<xn:VsDataContainer id="80YIL1">< >xn:attributes< >vsDataExternalGsmCell</ >xn:vsDataType xn:vsDataType< >EricssonSpecificAttributes.11.26</ >xn:vsDataFormatVersion xn:vsDataFormatVersion< >es:vsDataExternalGsmCell< >33</ >es:maxTxPowerUl es:maxTxPowerUl< >100</ >es:qRxLevMin es:qRxLevMin< >0</ >es:individualOffset es:individualOffset< >2</ >es:bandIndicator es:bandIndicator< >SubNetwork=ONRM_ROOT_MO_R,vsDataExternalGsmPlmn=286_1_2</ >es:parentSystem es:parentSystem< >2</ >es:mncLength es:mncLength</ >es:vsDataExternalGsmCell</ >xn:attributes</xn:VsDataContainer></gn:ExternalGsmCell>

<gn:GsmRelation id="80YIL1">< >gn:attributes< >SubNetwork=ONRM_ROOT_MO_R,ExternalGsmCell=80YIL1</ >gn:adjacentCell gn:adjacentCell</ >gn:attributes<xn:VsDataContainer id="80YIL1">< >xn:attributes< >vsDataGsmRelation</ >xn:vsDataType xn:vsDataType

< >EricssonSpecificAttributes.11.26</ >xn:vsDataFormatVersion xn:vsDataFormatVersion< >es:vsDataGsmRelation< >7</ >es:qOffset1sn es:qOffset1sn< >0</ >es:mobilityRelationType es:mobilityRelationType< >1</ >es:selectionPriority es:selectionPriority</ >es:vsDataGsmRelation</ >xn:attributes</xn:VsDataContainer></gn:GsmRelation>

Exp 1 NSN: Importing adjacencies with foregin cells - FBTS

These parameters presented in the examples are mandatory for external cell creation.

<managedObject class="ADCE"distName="PLMN-PLMN/BSC-33225/BCF-1/BTS-2/ADCE-399 5077"operation="create"><p name="adjacentCellIdCI">5077</p><p name="adjacentCellIdLac">399</p><p name="adjacentCellIdMCC">263</p><p name="adjacentCellIdMNC">03</p><p name="adjCellBsicBcc">1</p><p name="adjCellBsicNcc">1</p><p name="bcchFrequency">1</p></managedObject>

<managedObject class="ADJG"distName="PLMN-PLMN/RNC-190/WBTS-1/WCEL-0/ADJG-2"operation="create"><p name="AdjgCI">330</p><p name="AdjgLAC">25</p><p name="AdjgMCC">262</p><p name="AdjgMNC">03</p><p name="AdjgBCC">1</p><p name="AdjgNCC">1</p><p name="AdjgBCCH">38</p><p name="AdjgBandIndicator">0</p></managedObject>

Exp 2 NSN :

<managedObject class="ADJG"distName="PLMN-PLMN/RNC-190/WBTS-1/WCEL-0/ADJG-2"operation="create"><p name="AdjgCI">330</p><p name="AdjgLAC">25</p><p name="AdjgMCC">262</p><p name="AdjgMNC">03</p><p name="AdjgBCC">1</p><p name="AdjgNCC">1</p><p name="AdjgBCCH">38</p><p name="AdjgBandIndicator">0</p>

<p name="NrtHopgIdentifier">2</p>

<p name="RtHopgIdentifier">0</p>

\</managedObject>

Licensing Requirements:

need to complete.

1. 2.

comment after sitting with Adi:

test in LAB commands for 3G-2Gmention that there is no tests about incomplete CSV file.