4749 116 introducing optimal routing 11-2010

3BL78508EAAARJZZA Ed. 01 RELEASED 12/16/2010

Introducing optimal routing Introducing optimal routing Introducing optimal routing Introducing optimal routing In HLRIn HLRIn HLRIn HLR

OPERATION METHODS AND PROCEDURES

Status RELEASED 2010/12/16

3BL78508EAAARJZZA Ed. 01 RELEASED 2

SOMMAIRE 1.1. REFERENCED DOCUMENTS ............................................. 3 1.2. Applicability .................................................... 3

2. Function description................................................. 3 2.1. Purpose .......................................................... 3 2.2. Manufacturer data ................................................ 4 2.2.1. Functional options ............................................ 4 2.2.2. Equipment Capbilities ......................................... 5 2.2.3. AC phases associated .......................................... 6 2.2.4. Translator ata ................................................ 6

3. Procedure preparation................................................ 6 3.1. Network prerequirement ........................................... 6 3.2. Site requirement ................................................. 6 3.3. Services to be performed by the customer ......................... 7 3.3.1. Back up ....................................................... 7 3.3.2. Function management ........................................... 7

3.4. Services to be performed by the manufacturer ..................... 7 4. Procedure : Set optimal routing...................................... 7 4.1. Procedure duration ............................................... 7 4.2. Preliminary checks ............................................... 7 4.3. Caution .......................................................... 8 4.4. Data initialisation .............................................. 8 4.4.1. AC initialisation. ............................................ 8 4.4.2. Contract data initialisation .................................. 8 4.4.3. Translation management ........................................ 9

4.5. Back-up .......................................................... 9 4.6. New Conformity ................................................... 9 4.7. Registering the changes .......................................... 9 4.8. Testing the functionality ........................................ 9

5. Procedure : Set optimal routing customization....................... 10 5.1. Procedure duration .............................................. 10 5.2. Preliminary checks .............................................. 10 5.3. Caution ......................................................... 10 5.4. Data initialisation ............................................. 10 5.4.1. AC initialisation. ........................................... 10 5.4.2. Contract data initialisation ................................. 10 5.4.3. NE Capability management ..................................... 12

5.5. Back-up ......................................................... 14 5.6. New Conformity .................................................. 14 5.7. Registering the changes ......................................... 14 5.8. Testing the functionality ....................................... 14

Appendix A Bulk file .................................................... 15


PREFACE

The purpose of the MPI is to describe the operations to enable optimal routing in the NgHLR. The function can be set by the manufacturer or one of his representatives.

HISTORY Edition Date (yy-mm-dd) Author Comments

Ed. 01 11/23/2010 Li Mimi Add optimal routing customization per feature 67409

1.1. REFERENCED DOCUMENTS

MASS MANAGEMENT :NHLRMASOPG : 3BL65040AAAAPCZZA

PLMN MANAGEMENT NHLRPLMOPG 3BL76879AAAAPCZZA

CAMEL SUBCRIPTION MANAGEMENT NHLRCAMOPG 3BL76640AAAAPCZZA

TRANSLATOR MANAGEMENT : NHLRTROPG 3BL76661AAAAPCZZA

SUBSCRIPTION MANAGEMENT :NHLRSUBOPG 3BL65041PCZZA

MPI : SETTING UP USSD IN NGHLR : 3BL78499AAAARJZZA

MPI : AC VERSION MANAGEMENT IN HLR : 3BL78440AAAARJZZA

1.2. Applicability

8650 SDM R3.1

2. Function description

2.1. Purpose

The optimal routing is used to optimise the routing between two MSs by no longer using the called partys HPLMN in the following cases : The called party is located in the same country as the calling party The called party is located in the same country as his HPLMN In the event of call forwarding, calls can be routed directly to forwarded to number without passing through the called partyVPLMN in the following cases : The forwarded to number is located in the same country as the calling party The forwarded to number is located in the same country as the called partys HPLMN.


Optimal routing function is activated once VLR address is translated. Optimal route barring (ORB) ensures that all internationally roamed calls are routed via the HPLMN GMSC and can be charged for. The HLR controls how the call is routed by the Roaming Number that is returned in response to a SendRoutingInformation request message. Roaming Optimal Routing is similar with optimal routing. The difference is the Roaming Optimal Routing is used for the subscriber who registered out of HPLMN. If GMSC/SCP is set to ORB or ORBROAM, MSISDN will be returned instead of real roaming number in SRI response. testCallCase for divert call scenario is used for IN network entity to test if the forwarded to number can be terminated. The normal FTN and SE FTN may be requested in the scenario. The FTN authorization and ODB/SS barring will be checked for the forwarded to number. If no error returned, the HLR will return OICK information in response.

2.2. Manufacturer data

2.2.1. Functional options

fSOR001 M (boolean) F-SOR-001 allows the implementation of the first optimised routing function

phase in the HLR to be checked.

The optimised routing allows call routing between two subscribers from two different PLMNs

to be simplified when the called party is roaming out of his PLMN preventing useless inter-

PLMN connections to be created.

The first phase applies in the following cases:

- Inter-PLMN mobile/mobile call:

- the calling subscriber is located in the same country as the called subscriber,

- the called subscriber is located in the country of his HPLMN.

- Call with inter-PLMN forward to a subscriber located in:

- the same country as the calling subscriber,

- the country of the called party HPLMN,

- the same country as the called subscriber.

TRUE:

- The first phase of the optimised routing function is offered by the HLR.

FALSE:

- The first phase of the optimised routing function is not offered by the HLR.

fSOR005 M (boolean) F-SOR-005 allows limitation of optimised routing depending on the called

subscriber location.

When the HLR receives an optimised routing request, i.e. when the 'Or Interrogation'

parameter is filled in in the MAP_SEND_ROUTING_INFORMATION_inv message, if F-SOR-

005 is set to TRUE, it compares the address of the VLR where the called subscriber is located

with a list of prefixes contained in the HY_VLR_I table. If the two values are the same, the

request is rejected.

TRUE:

- The optimised routing function depending on the called subscriber location is offered by

the HLR.

FALSE:


- The optimised routing function depending on the called subscriber location is not offered

by the HLR.

fTC105 M (boolean)

fTC105 is to indicate whether the customized optimal routing service for Vf-UK

can be enabled or not.

If fTC105 is enabled, HLR will check whether the GMSC/SCP support Optimal Routing or

not. If GMSC/SCP does not support Optimal Routing, in other words, is provisioned as

Optimal Routing Barring (ORB)(Refer to 2.2.2), the HLR shall return subscribers MSISDN as

the roaming number in the sendRoutingInfo response message to the GMSC/SCP. The IMSI

and Basic Service Code shall also be returned in SRI response. If fTC107 is active and no

suppress-T-CSI parameter in camelInfo parameter is present, the HLR shall return GSM

Bear Capability parameter got from database in SRI response.

TRUE: Enable

FALSE: Disable

fTC106 M (boolean)

This contract data is to indicate whether the customized Roaming Optimal

Routing service for Vf-UK can be enabled or not.

If fTC106 is enabled, when HLR receives sendRoutingInfo request message from GMSC/SCP,

if the subscriber is roamed out of the HPLMN and if the GMSC/SCP is not provisioned as

Optimal Routing Barred (ORB)(Refer to 2.2.2), the HLR shall check whether the GMSC

support Roaming Optimal Routing or not.

If the GMSC/SCP is provisioned as Roaming Optimal Routing Barred (ORBROAM)(Refer to

2.2.2), the HLR shall not send provideRoamingNumber request message to the VLR and

return subscribers MSISDN as the roaming number in the sendRoutingInfo response

message to the GMSC/SCP. The IMSI, Basic Service Code and GSM Bear Capability

parameter shall also be returned. If fTC107 is active and no suppress-T-CSI parameter in

camelInfo parameter is present, the HLR shall return GSM Bear Capability parameter got

from database in SRI response.

TRUE: Enable

FALSE: Disable

fTCC101 M (boolean)

This contract data is to indicate whether the testCallCase divert call can be

enabled or not. NULL equals to false.

2.2.2. Equipment Capbilities

mscSupportedServices O (bitfield(32))

This attributes defines supported services for a gateway MSC network entity.

Enum description:

ORB: Optimal Routing Barred

ORBROAM: Optimal Routing Barred in Roaming

scpSupportedServices O (bitfield(32))

This attributes defines the supported services on SCP.

Enum description:

ORB: Optimal Routing Barred

ORBROAM: Optimal Routing Barred while Roaming


2.2.3. AC phases associated

Incoming AC : RNBENQ and SINENQ (MAP V3 minimum)

Outgoing AC : (MAP V3 minimum)

2.2.4. Translator ata

ccOptimalRouteing M (bcd (3)) Country code for Optimal Routeing : from 1 to 3 digits

ccOptimalRouteing

OAM-Interface

hyr_trr

translatorTriggerId=1,triggerServiceId=1,managedElementId=HSS1

HYR_TRR.HY_RESTR.HY_CC.HY__VCC for digits +HY_LCC for

Length

ndcOptimalRouteing M (bcd (4))

National Destination Code for optimal routeing : from1 to 4 digits

ndcOptimalRouteing

OAM-Interface

hyr_trr

translatorTriggerId=1,triggerServiceId=1,managedElementId=HSS1

HYR_TRR.HY_RESTR.HY_NDCOR.HY__VNDC for digits +HY_LNDC for

Length

3. Procedure preparation

3.1. Network prerequirement

the function must be operational in all entities of the network.

3.2. Site requirement

The HLR must be in perfect working order.


3.3. Services to be performed by the customer

3.3.1. Back up

The customer: - Takes a platform application backup before the operation. - Takes a platform application backup after the operation

3.3.2. Function management

The customer supplies and executes a test plan after the operation.

3.4. Services to be performed by the manufacturer

The manufacturer: - Applies the procedure described in the following sections. - Checks that the service to perform by the customer are complete. - In addition:

. Before modification : - Checks the conformity reference.

. After modification : - On the first site (trial site), establishes a new conformity reference and sends

it to the Alcatel customer interface. - On the other sites, checks data conformity using the first site as a reference.

4. Procedure : Set optimal routing

4.1. Procedure duration

Procedure takes some minutes to update data. Not included acceptance test and backup.

4.2. Preliminary checks

Check backup is done.

- In addition: . Before modification :

- Checks the conformity reference. . After modification :

- On the first site (trial site), establishes a new conformity reference and sends it to the Alcatel customer interface.

- On the other sites, checks data conformity using the first site as a reference.


4.3. Caution

In case of problem on contract data initialisation contract data must be checked. Eventually a database restoration must be done.

4.4. Data initialisation

Only data initialisation using IHM is described. However initialisation can be done applying bulk files. Format of these files is given in Annexe.

4.4.1. AC initialisation.

Check and initialise LOCRET, RNBENQ, SINENQ Refer to MPI : AC version Management in HLR : 3BL78440AAAARJZZA

4.4.2. Contract data initialisation

Set fSOR001 and fSOR005 (if requested)


4.4.3. Translation management

A PLMN (or a set of VLR) can be authorized for OR, implicitly by omitting the NDC as result of the entity translation or explicitly by giving the NDC (or a part of NDC) equal to the HLR NDC as result of the entity translation. A PLMN (or a set of VLR) can be excluded of OR by giving the VLR NDC (or another value different of HLR NDC value) as result of the entity translation. For each concerned VLR , eventually set ccOptimalrouteing and if requested ndcOptimalRouting.

4.5. Back-up

Back up the application.

4.6. New Conformity

Establish a new conformity reference.

4.7. Registering the changes

Immediate.

4.8. Testing the functionality

The customer executes his test plan, only when the station has been modified.


5. Procedure : Set optimal routing customization

5.1. Procedure duration

Procedure takes some minutes to update data. Not included acceptance test and backup.

5.2. Preliminary checks

Check backup is done.

- In addition: . Before modification :

- Checks the conformity reference. . After modification :

- On the first site (trial site), establishes a new conformity reference and sends it to the Alcatel customer interface.

- On the other sites, checks data conformity using the first site as a reference.

5.3. Caution

In case of problem on contract data initialisation contract data must be checked. Eventually a database restoration must be done.

5.4. Data initialisation

Only data initialisation using IHM is described. However initialisation can be done applying bulk files. Format of these files is given in Annexe.

5.4.1. AC initialisation.

Check and initialise LOCRET, RNBENQ, SINENQ Refer to MPI : AC version Management in HLR : 3BL78440AAAARJZZA

5.4.2. Contract data initialisation

Set fTC105 , fTC106 and fTCC101(if requested)


5.4.3. NE Capability management

Set ORB for GMSC:

Set ORBROAM for GMSC:


Set ORB for SCP:

Set ORBROAM for SCP:


5.5. Back-up

Back up the application.

5.6. New Conformity

Establish a new conformity reference.

5.7. Registering the changes

Immediate.

5.8. Testing the functionality

The customer executes his test plan, only when the station has been modified.


APPENDIX A BULK FILE

The xml files have to be updated with customer contract data.

a) Initialise contract data for optimal routing

1

0

b) Declare AC phases (see corresponding MPI)

c) Initialise contract data for optimal routing customization

0

0


0

TITLE PAGESOMMAIREPREFACEHISTORY1.1. REFERENCED DOCUMENTS1.2. Applicability2. Function description2.1. Purpose2.2. Manufacturer data2.2.1. Functional options2.2.2. Equipment Capbilities2.2.3. AC phases associated2.2.4. Translator ata

3. Procedure preparation3.1. Network prerequirement3.2. Site requirement3.3. Services to be performed by the customer3.3.1. Back up3.3.2. Function management

3.4. Services to be performed by the manufacturer

4. Procedure : Set optimal routing4.1. Procedure duration4.2. Preliminary checks4.3. Caution4.4. Data initialisation4.4.1. AC initialisation.4.4.2. Contract data initialisation4.4.3. Translation management

4.5. Back-up4.6. New Conformity4.7. Registering the changes4.8. Testing the functionality

5. Procedure : Set optimal routing customization5.1. Procedure duration5.2. Preliminary checks5.3. Caution5.4. Data initialisation5.4.1. AC initialisation.5.4.2. Contract data initialisation5.4.3. NE Capability management

5.5. Back-up5.6. New Conformity5.7. Registering the changes5.8. Testing the functionality

APPENDIX A BULK FILE

4749 116 introducing optimal routing 11-2010

Documents

optimal routing customization

ac initialisation

contract data initialisation

procedure duration

manufacturer data

procedure preparation

function management

translation management