01 2513e7a01 Msc Database

MSC Database Administration Siemens

MN2513E7A011

ObjectivesObjectivesObjectivesObjectives

The participant is able to� administer Cells and Location Areas� administer MSC specific features� explain the Inter MSC Handover� explain the Mobile Terminating Call� administer Mobile Station Routing Numbers

(**++**Register-Zählung**++**)1

MSC Database AdministrationMSC Database AdministrationMSC Database AdministrationMSC Database Administration

Siemens MSC Database Administration

MN2513E7A012

ContentsContentsContentsContents

1 Cells and Location Areas 31.1 Definition of Cells and Location Areas 41.2 Using Cells and Location Areas 62 Regional Roaming Subscription 252.1 Functionality 262.2 MML Commands 283 Cell-Oriented Routing 313.1 Functionality 323.2 MML Commands 344 Subscriber-Related Routing 394.1 Functionality 404.2 Administration 425 Monitoring of Forwarded and Transferred Calls 455.1 Function 465.2 Administration 485.3 Example 506 Mobile Station Routing Numbers 536.1 Inter-MSC Handover 546.2 Mobile Terminating Call 566.3 Administration of Mobile Station Routing Numbers 587 Exercises 618 Solutions 69


MN2513E7A013

1111 Cells and Location AreasCells and Location AreasCells and Location AreasCells and Location Areas


MN2513E7A014

1.11.11.11.1 Definition of Cells and Location AreasDefinition of Cells and Location AreasDefinition of Cells and Location AreasDefinition of Cells and Location Areas� Cell

A cell is the smallest addressable radio range from the perspective of the MSC.A cell describes the geographical area covered by the radio resources of a basestation. A cell is identified from the MSC with the help of the location area code(LACOD) and the cell identification (CI). A cell is addressed from the MSC via thesignaling point code (CCS7 address) of the BSC. The location cell of a subscriber isnot used for call setup in the MSC, but it is known in the MSC and is used fortraffic measurement. A cell is internationally unambiguously addressed via the cellglobal identity. This consists of the components MCC/MNC/LACOD/CI.

� Location areaAs described already, the location of the subscriber in the MSC/VLR is not carriedout on a call basis. Only the location area of the subscriber is stored in the VLR –i.e., the subscriber is reachable owing to the location area. A location area cancontain several cells. One or several location areas are allocated unambiguously toan MSC. The address logic of the location area and thus of all the cells from theMSC contained within ensues via the signaling point code of the BSC.A location area is internationally unambiguously identifiable via the location areaidentity. This consists of the following components:MCC/MNC/LACOD.


MN2513E7A015

SIEMENS SIEMENS

MSC/VLR

BSS BSS

addressed by Signaling Point Code

Location Area

Location AreaCell:CGI = MCC/MNC/LACOD/CILocation Area:LAI = MCC/MNC/LACOD

Subscriber DataLAI

addressed by Signaling Point Code

Cell

Cell

CellCell

CellCell

Cell

Cell

Cell

CellCell Cell

Location Area

Fig. 1 Cells and location areas


MN2513E7A016

1.21.21.21.2 Using Cells and Location AreasUsing Cells and Location AreasUsing Cells and Location AreasUsing Cells and Location Areas

1.2.11.2.11.2.11.2.1 Internal Cells and Location AreasInternal Cells and Location AreasInternal Cells and Location AreasInternal Cells and Location Areas

1.2.1.11.2.1.11.2.1.11.2.1.1 FunctionFunctionFunctionFunction

The location of a mobile subscriber is defined in the MSC specific only to the locationarea. In other words, regardless of the cell in a location area in which the subscriberis currently to be found, only the location area of the subscriber is stored in the VLR.For this reason, the cells that constitute a location area and the base station systemvia which the subscriber can be reached must be reported to the system.

Location update:

When a subscriber changes location, the mobile station compares the new LAI(location area identity) transmitted by the BSS with the LAI of the previous locationupdate that is stored on the SIM card. If the two LAIs do not match, the mobilestation has changed location and is now positioned in a different location area of thesame or another MSC. The mobile station sends the old LAI and the received LAI tothe MSC. The MSC then analyzes the old LAI. If the location has changed within theMSC area, the MSC can detect the change by means of the database because theold LAI can be found as an internal cell/location area in the MSC in this case. Thenew LAI is then entered in the subscriber data of the VLR in order to make themobile subscriber accessible for mobile terminating calls, for example.


MN2513E7A017

SIEMENS SIEMENS

SIM CardSIM Card

old LAIold LAI

newLAI

old LAInew LAI

new LAI =old LAI?

Cell/Lacode Data

old LAI?

Cell/Lacode Data

old LAI?VLR MSUB

Data

new LAI

VLR MSUB Data

new LAI

VLR/MSC

Fig. 2 Internal cell data for location update


MN2513E7A018

Mobile terminating calls

After a location update, the location area identity (LAI) is stored in the subscriber’sVLR data. If a ‘provide roaming number’ is then received from the HLR during amobile terminating call, a mobile station roaming number is output, linked with theVLR subscriber data and returned to the HLR.

Next, a circuit connection (e.g. ISUP) is set up to the visited MSC/VLR of the calledparty by the visited MSC/VLR of the calling party. The subscriber can be easilyidentified since the called party number received (mobile station roaming number) islinked with the VLR subscriber data. The LAI and TMSI are stored in the VLRsubscriber data.

The CCS7 signaling address or addresses of the assigned base station systems areassigned to the location areas in the semipermanent location area / cell data. Apaging signal is sent with the TMSI in the broadcast channel to all assigned basestation systems. If the mobile station is in the corresponding BSC area, thisinformation is returned as a paging response. A traffic channel is then switched tothe appropriate base station system in reply.

The LAI is therefore used for detecting the location area of the called subscriber andthus for detecting the corresponding base station system(s).


MN2513E7A019

SIEMENS SIEMENS

SIM Card

Broadcast TMSI

Cell/LacodData

LAIBSC SPCNetind

Cell/LacodData

LAIBSC SPCNetind

VLR MSUB Data

LAITMSI

VLR MSUB Data

LAITMSI

ISUP:MSRN

Paging (TMSI)

Paging Response

Broadcast TMSI

Broadcast TMSI =stored TMSI?

Fig. 3 Application of cells/location areas for mobile terminating calls


MN2513E7A0110

Internal MSC handover

In the course of a handover, the base station system suggests possible cells to theMSC for the handover. The MSC can use the cells assigned to it to check whetherthey are internal cells with which it can perform an internal MSC handover.


MN2513E7A0111

SIEMENS SIEMENS

SIM CardSIM Card

Handover required(List of possible cells)

Cell/Lacode data

suggested cell?

Cell/Lacode data

suggested cell?

Handover

Intra-MSCHandover

Fig. 4 Intra-MSC handover dependent on internal cell


MN2513E7A0112

1.2.1.21.2.1.21.2.1.21.2.1.2 MML CommandMML CommandMML CommandMML Command

Cells assigned to an MSC are created with CR INTCELL. This MML commandassigns a cell ID to an LACOD each time. The command can be entered multiplywith the same LACOD but with different cell IDs.

Another important assignment is the combination of the cell ID base station andSPC/NETIND (CCS7 signaling point code).

The parameter ‘location mark number’ must also be entered. This parameter istreated separately at a later stage.

The parameter LOCNO (0...999999999999999) enables all cells in a network to beuniquely numbered and identified. The parameter can be used in the mobile callrecord, for example, in order to clearly identify the origin, or can be transferred to theIN (service control point) in order to perform origin-dependent routing, for example.

The parameter ORIG2 allows distance-related charging because, on the one hand, itcan be included in the mobile call records and, on the other hand, evaluated in thezoning converter.

DISP INTCELL

BSCSPC NETIND LACOD CI Result

X LACODs only

<lacod> CI

BSCSPC

NETIND

LMN

<bscspc> <netind> LACOD

CI

LMN

<lacod> <ci> BSCSPC

NETIND

LMN

Cell-dependent routing data


MN2513E7A0113

Creation and Display of Location Areas, Cells andLocation Mark NumbersCR INTCELL: LACOD= <location area code>,

CI= <cell identification,BSCSPC= <BSC signalling point code>,NETIND= <net indicator>,LMN= <location mark number>[,LOCNO=<location number>][,ORIG2=<originating mark for zoning>],.....;

DISP INTCELL: LACOD= <location area code>[,CI= <cell identification]orBSCSPC= <BSC signalling point code>,NETIND= <net indicator>,....;

DISP LMN: LMN= <location mark number>;

BSCSPC NETIND LACOD CI Result

X just LACODs

<lacod> CIBSCSPCNETIND

LMN

<bscspc> <netind> LACODCI

LMN

<lacod> <ci> BSCSPCNETIND

LMNcell depend.Routing data

Fig. 5 Cell, location area and location mark number administration


MN2513E7A0114

1.2.1.31.2.1.31.2.1.31.2.1.3 Location Mark NumbersLocation Mark NumbersLocation Mark NumbersLocation Mark Numbers

A location mark number can be allocated to a cell. A location mark number is a cell-dependent full directory number which is applied cell-dependently as dialinginformation for a GSM emergency call.


MN2513E7A0115

SIEMENS SIEMENS

MSC/VLR

BSS

LMN= e.g.E8901CC110C9172LMN= e.g.E8902CC110C9172

PSTN PSTN

Emergency Button

Emergency Button

Emergency Center 1

Emergency Center 2

Fig. 6 Location mark number


MN2513E7A0116

1.2.21.2.21.2.21.2.2 External Location AreasExternal Location AreasExternal Location AreasExternal Location Areas

1.2.2.11.2.2.11.2.2.11.2.2.1 FunctionFunctionFunctionFunction

Location change from a known VLR/MSC

If an MSUB changes the location from an VLR/MSC that is known in the newVLR/MSC, the IMSI can be requested from the old VLR. This dispenses with theneed to transmit the IMSI via the air interface – this is undesirable because it wouldbe transferred without encryption.

In addition to the LACODs of neighboring MSCs, the LACODs of MSCs consideredto be the most important national traffic nodes (airports, major train stations, etc.)should be known in all national MSCs/VLRs. Even better would be to report theLACODs of all national MSCs/VLRs in all national MSCs/VLRs.


MN2513E7A0117

SIEMENS SIEMENS

SIM CardSIM Card

old LAIold LAI

newLAI

old LAInew LAI

new LAI =old LAI?

External Lacode Data

old LAI?=> VLRISD

External Lacode Data

old LAI?=> VLRISD

SIEMENS SIEMENS

VLR MSUB Data

IMSI

VLR MSUB Data

IMSI

Old VLR/MSC

New VLR/MSCIMSI

IMSI

Fig. 7 Location area data for location update


MN2513E7A0118

Inter-MSC handover

A minimum of all location areas of neighboring MSCs must be created as externallocation areas for handovers to the areas to be completed successfully.

The BSS sends the MSC a list of suggested cells for a handover. The MSC firstcompares the first cell in the list with the internal cell database so as to initiate aninternal MSC handover if necessary. If the cell is not found there, a search for thecell is made in the external location area database. The external database containsthe external LACODs and the associated MSCID. If the cell is found there, theMSCID is converted to a CCS7 signaling address and the inter-MSC handover isinitiated.


MN2513E7A0119

SIEMENS SIEMENS

SIM CardSIM Card

Handover request(List of possible cells)

Cell/Lacode data

suggested cell?

Cell/Lacode data

suggested cell?

Handover

SIEMENS SIEMENS

External Lacode data

suggested cell?

=>MSCID

External Lacode data

suggested cell?

=>MSCID

Inter-MSChandover

Fig. 8 Location area data for inter-MSC handover


MN2513E7A0120

1.2.2.21.2.2.21.2.2.21.2.2.2 MML CommandsMML CommandsMML CommandsMML Commands

The command CR EXTLAC reports external LACODs in an MSC/VLR. A LACOD islinked with an MSCID for each command call. The MSCID is used for finding theforeign MSC for handover later. A VLRISDN may also be assigned as an optionalparameter. The VLRISDN is used, for example, for addressing the VLR for locationupdates. If no VLRISDN is entered, the MSCID is used instead.

The commands CAN EXTLAC and DISP EXTLAC are used to respectively cancel anddisplay external LACODs.

MOD EXTLAC can modify either a LACOD, MSCID or VLRISDN.


MN2513E7A0121

External LACOD Administration

CR EXTLAC: LACOD= ,MSCID= [,VLRISD= ];

CAN EXTLAC: LACOD= ;

DISP EXTLAC: MSCID= ;

MOD EXTLAC: LACOD= ,NLACOD= ;

MOD EXTLAC: LACOD= <,NMSCID= ,NVLRISD= > ;

Fig. 9 External LAC administration


MN2513E7A0122

1.2.2.31.2.2.31.2.2.31.2.2.3 Structured LACODsStructured LACODsStructured LACODsStructured LACODs

A great deal of administration is required to create the LACODs of all MSCs/VLRsbelonging to a PLMN in all MSCs/VLRs of this PLMN. Structured LACODs provide asolution to this problem.

In accordance with GSM, a LACOD has 16 bits. If a structured LACOD is used, the16 bits are distributed project-specifically to bits per MSC (DISP MPRDDATMSCLACOD) and bits per LACOD belonging to the corresponding MSC. If theLACODs of a different MSC/VLR are then announced in an MSC/VLR usingCR EXTLAC, only the MSC-specific part of the 16 bits has to be defined. Theremaining bits can assume any value at all.

Example: The number of bits for the LACOD must be set to 8 in the mobile projectdata – i.e., in this case, 8 bits are assigned to the MSC-specific part and thesupplement to make up the 16 bits represents the LACOD for the correspondingMSC.

If the MSC-specific part has the binary value 1, the following LACOD range isobtained for the MSC:

MSC-specificpart

Specific partof the LACODsof the MSC

DecimalLACOD value

0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 256

0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 257

0 0 0 0 0 0 0 1 ................

0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 511

Since the decimal value range (e.g., 256..511) is permanently assigned to thecorresponding MSC, the MML command ‘CR EXTLAC’ need only create the LACOD‘256’ (i.e., only the start of the range) and assign it to an MSC. In other words, thefollowing LACODs would be assigned to the different MSCs.

For example:

MSC1: 0...255 (CR EXTLAC:LACOD=0,..),

MSC2: 256...511 (CR EXTLAC:LACOD=256,..),

MSC3:512...767 (CR EXTLAC:LACOD=511,..),

MSCn: 65280...65535 (CREXTLAC:LACOD=65280,..).


MN2513E7A0123

Mobile Project Data:LENGTH OF MSC EXTERNAL LACOD (MSCLACOD): 8

8 bits MSC-specific(MSCLACOD): 8

8 bits for the LACOD

of the MSC

Example structured LACOD:

MSC-specific

000000000000000000000000.....00000000000000010000000100000001.......00000001................

LACOD-specific

000000000000000100000010.......11111111000000000000000100000010..........11111111................

LACOD range decimal012.......255256257258........511...............

CR EXTLAC:LACOD=

0

256

.....................

Fig. 10 Structured LACOD


MN2513E7A0124


MN2513E7A0125

2222 Regional Roaming SubscriptionRegional Roaming SubscriptionRegional Roaming SubscriptionRegional Roaming Subscription


MN2513E7A0126

2.12.12.12.1 FunctionalityFunctionalityFunctionalityFunctionalityRegional zones can be assigned to a mobile subscriber for each PLMN whoseservices he is entitled to use (e.g. wireless loop subscriber). The zones limit thepossibility to certain location areas or cells. The subscriber is assigned zone codesused for identifying these permitted roaming zones. The zones themselves aredefined in the VLR. During a location update the zone codes of zones permitted forthe location PLMN are stored in the VLR together with other mobile subscriber data.It can be decided in the VLR whether the mobile subscriber may use the services ofthe PLMN in his present location area by comparing the mobile subscriber zonecodes with the identifiers of the cells or location areas.

� Regional roaming administration based on LACODs:

Here the LACODs that make up a roaming zone are specified in the VLR. If one ofthese zones is assigned in the HLR to a subscriber, he/she is only permitted touse the service (location update) in those LACODs.

� Regional roaming administration based on cells, roaming restriction based onLACODs:

In this case the cell IDs constituting a roaming zone are specified in the VLR. Ifone of these zones is assigned in the HLR to a subscriber, he/she is onlypermitted to use the service (location update) in the location area to which thecorresponding cell or cells are assigned.

� Regional roaming administration based on cells, roaming restriction based oncells:

In this case the cell IDs constituting a roaming zone are specified in the VLR. Ifone of these zones is assigned in the HLR to a subscriber, he/she is onlypermitted to use location updates in the location area to which the correspondingcell or cells are assigned. A check is performed during call setup (MOC/MTC,mobile terminating SMS, mobile origin SMS, etc.) to determine whether thesubscriber is located in any of the permitted cells.


MN2513E7A0127

allowedallowed

SIEMENS SIEMENS

Regional Roaming

Data

Local Areaor Cell ids

Regional Roaming

Data

Local Areaor Cell ids

SIEMENS SIEMENS

HLR MSUB Data

Roaming Zone

HLR MSUB Data

Roaming Zone

HLR

VLR/MSC

allowedallowed

allowed tooallowed too

allowedallowedRoaming Zone Administration based on Location Area. Subscription in the whole location area

Roaming Zone Administrationbased on Cell. Subscription in the whole location area

Roaming allowedcall not allowed

Roaming allowedcall not allowed

Roaming allowed

callallowed

Roaming allowed

callallowed

Roaming Zone Administration based on Cell. Cell checked during Call setup

Roaming Zone

Fig. 11 Roaming zones


MN2513E7A0128

2.22.22.22.2 MML CommandsMML CommandsMML CommandsMML Commands� For a feature to function correctly it must be released (sales feature) and activated

with MODMSERVOPT.

A distinction must be made between the features REGRO, RSCELLBA andRSCELLID.

FEAT=REGRO basic feature: The regional subscription is administered on thebasis of the location area.

FEAT=REGRO&RSCELLBA supplementary feature: The regional subscription isadministered using the cell ID but is effective for location areas.

FEAT=REGRO&RSCELLID supplementary feature: Administered like RSCELLBAbut checks during call setup if the subscriber is in the appropriate cell.

� The command CR RSZONE uniquely assigns one or more location areas (REGRO)or one or more cell IDs (REGRO&RSCELLBA or REGRO&RSCELLID) to a zonenumber (roaming zone) in the MSC/VLR.

� The MML command ‘ENTR RSSERV’ assigns the zones defined in the MSC/VLRto a mobile subscriber as permitted roaming areas.Rule: If the zone 0 is assigned to the subscriber in addition to other zones forRSCELLBA, the subscriber is allowed to use the service in the correspondingVLRs in the known zones (LACODs) and in all other VLRs.


MN2513E7A0129

Regional Subscription Administration

Feature in the DISP MSERVOPT

REGRO GSM Basic Feature: Administration and check basedon LACOD

REGRO&RSCELLBA

Supplementary Feature: Administration based onCELL, check based on LACOD

REGRO&RSCELLID

Supplementary Feature: Administration based onCELL, call setup check based on Cell

In the VLR

CR RSZONE: ZCODE=<roaming zone number>, RSAREA= <cell idor lacode> ;

In the HLR

ENTR RSSERV: MSIN= ,PLMN= <CC>-[<NDC>],ZCODE=<roaming zone number>,

Fig. 12 Administration of regional subscription


MN2513E7A0130


MN2513E7A0131

3333 Cell-Oriented RoutingCell-Oriented RoutingCell-Oriented RoutingCell-Oriented Routing


MN2513E7A0132

3.13.13.13.1 FunctionalityFunctionalityFunctionalityFunctionalityAlongside the cell-dependent management of real emergency calls, there is thepossibility to cell-dependently convert certain service abbreviated numbers into fulldirectory numbers. This could, for instance, be applied when the operator-specificservice numbers, breakdown service, etc. are to be accessed cell-dependently. Thismeans, for example, that – depending on the location on the freeway that a carbreaks down– the call is connected to different breakdown service points althoughthe same abbreviated number is used. This takes place through the evaluation of thecell in which the subscriber is currently located and the conversion of the dialedabbreviated numbers into various full directory numbers.


MN2513E7A0133

SIEMENS SIEMENS

MSC/VLR

BSS

Long Number = e.g. 08917389Long Number = e.g. 082217389

PSTN PSTN

ServiceCenter 1

Service Center 2

Short Service Number

Short Service Number

Fig. 13 Cell-dependent routing


MN2513E7A0134

3.23.23.23.2 MML CommandsMML CommandsMML CommandsMML Commands� The setup of the database for cell-dependent routing consists of several steps:

a) The service provider name must be announced with the commandCR PROVNAM (create provider name). In addition, whether the call to thisprovider should be handled as an emergency call can be specified in thiscommand.

b) The full directory numbers per origin cell are specified with the command CRPROVNO (create provider number) for the provider setup.

c) The general code via which the provider should be able to be reached is setup and linked with the provider name with the command CR CPT (createcode point).

� The following display commands are reachable for the display: DISP PROVNAM,DISP PROVNO, DISP CPT.


MN2513E7A0135

Creation and Display of Cell dependent Routing

CR PROVNAM: PROVNAM=<provider name>,TYPE={ORD|EM},.....;

CR PROVNO: PROVNAM=<provider name>,PROVNO=<digit combination cell dependent>,CI=<cell id>,LACOD=<location area code>;

CR CPT: CODE=<cell independent short code>,TRATYP=MOBPROV,PROVNAM=<provider name>,....;

DISP PROVNAM: PROVNAM=<provider name>;

DISP PROVNO: PROVNO=<digit combination cell dependent>;

DISP CPT: CODE=<cell independent short code>,{TRATYP=MOBPROV | PROVNAM=<provider name>};

Fig. 14 Cell-dependent routing administration


MN2513E7A0136

3.2.13.2.13.2.13.2.1 ExampleExampleExampleExample

In the next example, the provider number for a second emergency number isdisplayed in addition to the official GSM number.

The subscriber dials 110. The incoming normal call is analyzed in the digit translatorand routed to the provider EMCAL110. Cell-dependent full emergency numbers arecreated for this provider. They begin with E and are followed by the PSTN local areacode. The remaining digits are determined by national legal requirements. With thelong directory number, the call is again routed to the digit translator and a destinationin the PSTN is addressed from there.


MN2513E7A0137

<CRPROVNAM:PROVNAM=EMCAL110,TYPE=EM;

<CRPROVNO:PROVNAM=EMCAL110,LACOD=511,CI=10192,PROVNO=E05021CC110C9172!:PROVNAM=EMCAL110,LACOD=511,CI=10191,PROVNO=E05021CC110C9172!:PROVNAM=EMCAL110,LACOD=511,CI=3590,PROVNO=E05051CC110C9172!:PROVNAM=EMCAL110,LACOD=511,CI=10200,PROVNO=E05021CC110C9172!:PROVNAM=EMCAL110,LACOD=511,CI=2381,PROVNO=E05721CC110C9172!.....<CRDEST:DEST=HNVR541VE1E ;<CRCPT:CODE=110,ORIG1=20-1,TRATYP=MOBPROV, PROVNAM=EMCAL110!.....<CRCPT:CODE=E,DEST=HNVR541VE1E ,ORIG1=20-1!.....

110

Cell Id

CI=10192E05021

CI=10192E05021

CI=3590E05051

CI=3590E05051

CI=10200E05021

CI=10200E05021

CI=2381E05721

CI=2381E05721

LAC=05021

LAC=05051

LAC=05721

SIEMENS SIEMENS

PSTN

CI=10191E05021

CI=10191E05021

Fig. 15 Example: provider number used for emergency calls


MN2513E7A0138


MN2513E7A0139

4444 Subscriber-Related RoutingSubscriber-Related RoutingSubscriber-Related RoutingSubscriber-Related Routing


MN2513E7A0140

4.14.14.14.1 FunctionalityFunctionalityFunctionalityFunctionalityThe ”subscriber-related routing” feature enables mobile originating calls (MOC) to berouted to specific destination numbers defined in the mobile subscriber's HLR. Torequest a connection of this kind, the mobile subscriber generally dials anabbreviated directory number. The MSC detects from the associated code point thatthe requested connection belongs to a service provider and to a specific service. Ittherefore builds a ”service number” with the format <CC> <NDC> 1 <Y> <SN>from the MSISDN (contained in the VLR database) of the mobile subscriber. CC,NDC and SN form the MSISDN of the calling subscriber. The service itself is notspecified exactly in the MSC, but identified by a service code Y (Y=0,1,2,...,9). If themobile subscriber is set up with multinumbering – i.e., the subscriber has more thanone SN, the MSC uses the SN of the base MSISDN.

The service number is used to carry out global title translation and then aninterrogation of the HLR of the calling subscriber. In each case, the full servicedirectory number is sent to the HLR. The HLR determines the service addresscreated for this service and, in some cases, for this mobile subscriber, and thisaddress is then sent to the MSC in response to the interrogation (see OMN: SSS-SU). The service address is defined in the HLR using one of the following methods:

� a fixed entered directory number, which usually corresponds to the ISDNnumbering plan (E.164)

� a directory number which consists of a digit sequence xxx (usually three digits)and the MSISDN of the calling mobile subscriber, and has the following structure:<CC><NDC> <xxx> <SN>; in this case, the service center is identified by at leastxxx, although parts of the SN may also be necessary for routing

� a mobile station roaming number which is requested by the HLR of the servicecenter; in this case, the connection is similar to a ”pseudo MTC” to a servicecenter.

The service address received as interrogation response in the HLR is used toexecute routing to the service center in the MSC.


MN2513E7A0141

SIEMENS SIEMENSServiceshort number

Provider data:Service specific indication „Y“

Provider data:Service specific indication „Y“

MSC/VLR

SIEMENS SIEMENS

HLR

Interrogation Send Routing Info:<CC><NDC>1<Y><SN>

Subscriber related Service data for Service Indication „Y“:• a) Fixed address: Service Center Number as Interrogation Response• b) Service Center Address: global title to request an MSRN from a Service Center• c) Subscriber dependent Address: Service Center Directory Number inclusive SN as Interrogation Result

Subscriber related Service data for Service Indication „Y“:• a) Fixed address: Service Center Number as Interrogation Response• b) Service Center Address: global title to request an MSRN from a Service Center• c) Subscriber dependent Address: Service Center Directory Number inclusive SN as Interrogation Result

PBX

Service Center

b) MSRN Request

b) MSRN

a) CC/NDC/<service Center>b) MSRN from service Centerc) CC/NDC/<service Center>/<SN>

Fig. 16 Subscriber-related routing


MN2513E7A0142

4.24.24.24.2 AdministrationAdministrationAdministrationAdministrationIn the MSC/VLR, the abbreviated directory number must be created using a codepoint and must also refer to a provider (PROVNAM). The provider is assigned aSERVICE INDICATOR (SERVIND) in the CR PROVNO command. This index has onecharacter and corresponds to the service indicator “Y” described earlier.

The service indicator is inserted in the MAP message to the HLR with a leading 1between the NDC and the SN of the calling party.

If the HLR does not find the calling party number in the HLR subscriber data, itbranches to the subscriber-related service data that were specified with CRSUBRSERV and assigned to a subscriber with ENTR OPRSERV.


MN2513E7A0143

SIEMENS SIEMENS

SIEMENS SIEMENS

Serviceshortcode:233

CR CPT: CODE=233, TRATYP=MOBPROV, PROVNAM=SERV233;CR PROVNAM: PROVNAM=SERV233, SERVIND=3;CR CPT:CODE=0049 178 13 89, TRATYP=MOBINTER,...;

CR SUBRSERV: OPRSERV=SUBRELRO, SERVICE=233, IND=3, ADDRTYPE= FIXED , SCADR SUBDEP ADDR= 49178 99 233;ENTR OPRSERV: OPRSERV=SUBRELRO, MSIN= 89 2134321, SERV=233;

InterrogationSend Routing Info for:0049178138942361 FIXED 0049 178 99 233

SCADR MSRN from service Center

SUBDEP 0049 178 99 233 89 42361

Fig. 17 Example: administration

Subscriber Related Routing Administration

In the VLR/MSCCR PROVNAM: PROVNAM= ,SERVIND= ;In the HLR

CR SUBRSERV: OPRSERV= ,SERV= ,IND= ,ADDRTYPE= ,ADDR= ;

ENTR OPRSERV: MSIN= ,OPRSERV= ,SERV=

Fig. 18 Subscriber-related routing: MML commands


MN2513E7A0144


MN2513E7A0145

5555 Monitoring of Forwarded andMonitoring of Forwarded andMonitoring of Forwarded andMonitoring of Forwarded andTransferred CallsTransferred CallsTransferred CallsTransferred Calls


MN2513E7A0146

5.15.15.15.1 FunctionFunctionFunctionFunctionThe so-called fraud protection package has been introduced for CF and CT in order toprevent mobile subscribers from committing fraud by switching calls with callforwarding or call transfer and then failing to pay the ensuing charges.

� Automatic monitoring function:

This function uses thresholds to limit the maximum number of simultaneous callforwarding or call transfer calls per party, or issues a warning when a specifiednumber of calls has been exceeded.

� Manual monitoring:

CF and CT calls can be indicated according to a specified call duration or numberof simultaneous calls.

� Forced release:

CT and CF calls that were conspicuous during manual monitoring can be manuallyreleased.


MN2513E7A0147

SIEMENS SIEMENS

SIEMENS SIEMENS

SIEMENS SIEMENS

SIEMENS SIEMENS

MSUB withCT or CF

Japan

USA

Russia

1

n

2MSC

Fig. 19 Reason for fraud protection

Fraud package

• Threshholds for CT and CF call limitation• Threshholds for CT and CF call displays• Manual monitoring of suspect calls by input of call duration or number of calls• Release of suspect calls

Fig. 20 Fraud package


MN2513E7A0148

5.25.25.25.2 AdministrationAdministrationAdministrationAdministrationThreshold values for the maximum number of simultaneously existing CF or CT callsare entered with the MML command ‘ACT SMSUBDET’ (suspect MSUB detection).Moreover, thresholds for the maximum number of calls can also be administered. Awarning is output each time this number is exceeded. Note that CT calls always havean incoming and an outgoing side and must therefore be considered as two calls ineach case.

The same MML command is also used to reactivate the feature after deactivation.

The command DISP SMSUB displays all current CT or CF calls for the MSUB. Thecommand is often used if the threshold value for a display for an MSUB has beenexceeded.

DISP SMCALL displays MSUBs that have exceeded either a specified number of CTor CF calls, or a duration specified for individual CT or CF calls.

Calls that appear suspicious to a carrier can be released with REL SMCALL.


MN2513E7A0149

Fraud Protection Administration

DISP MSERVOPT: FEAT=FRAUDPR;

ACT SMSUBDET : [INFOTHR=] [,RELTHR=] ;

DACT SMSUBDET ;

DISP SMSUBDET ;

DISP SMSUB : <IMSI= ,CALL= ,CDUR=> ;

DISP SMCALL : IMSI= ;

REL SMCALL : IMSI= ,CALLIND= ;

Fig. 21 Fraud protection for CF/CT


MN2513E7A0150

5.35.35.35.3 ExampleExampleExampleExample


MN2513E7A0151

Display to check if feature is generally activ

DISP MSERVOPT:FEAT=FRAUDPR;

DISPMSERVOPT:FEAT=FRAUDPR; EXEC'D

SERVICE/ CONNECTION RADIO CHANNEL ALTERNATIVEFEATURE STATUS ELEMENT REQUIREMENT SCI OCI SERVICE----------+--------+------------+--------------+-----+-----+-----------FRAUDPR ACT

END JOB 8948

Activate Suspect MSUB detection

ACT SMSUBDET:INFOTHR=2,RELTHR=4;

ACTSMSUBDET:INFOTHR=2,RELTHR=4; EXEC'D

SUSPECT MOBILE SUBSCRIBER DETECTION

STATUS: ACTIVE INFORMATION THRESHOLD: 2 RELEASE THRESHOLD: 4

END JOB 9589

3 CF or 2 CT calls for MSUB 262085300000000 have happened

D900#/MSC00000/SR6012345678-NNN/410 96-11-12 12:34:079628 2996/08702

SUSPECT MOBILE SUBSCRIBER DETECTION

REASON: MAXIMUM NUMBER OF CALLS EXCEEDED

IMSI : 262085300000000

Display MSUB 262085300000000

DISP SMCALL:IMSI=262085300000000;

DISPSMCALL:IMSI=262085300000000; EXEC'D

SUSPECT MOBILE CALLS

IMSI = 262085300000000

CALL-DURATION

CALLIND FTN/CDPA TYPE HOUR MINUTE MSISDN--------+---------------+-----+------+-------+---------------

1 0893304 CT 0 3 4917851100002 0893303 CT 0 3 4917851100003 0893302 CT 0 0 4917851100004 0893301 CT 0 0 491785110000

END JOB 9629

Realease of the first „Call Transfer“-connection (Callind=1 or 2):

REL SMCALL:IMSI=262085300000000,CALLIND=2DANGEROUS COMMAND RELSMCALL READY TO EXECUTE <;

RELSMCALL:IMSI=262085300000000,CALLIND=2; EXEC'D

Fig. 22 Example: fraud protection


MN2513E7A0152


MN2513E7A0153

6666 Mobile Station Routing NumbersMobile Station Routing NumbersMobile Station Routing NumbersMobile Station Routing Numbers


MN2513E7A0154

6.16.16.16.1 Inter-MSC HandoverInter-MSC HandoverInter-MSC HandoverInter-MSC Handover1. The mobile station and BTS (base transceiver station) measure, for example, the

transmission quality and reception level. The mobile station also measures thereception of neighboring cells and transfers the values to the BSS.

2. If required, the BSC generates a list of suggested cells from the measurementresults with up to 16 cells, and sends the list with a ‘handover required’ to thecorresponding MSC.

3. The MSC checks the first cell in the list to determine whether it belongs to theMSC’s own area (CR INTCELL:CI=, LACOD=...;). If not, it checks if the cellbelongs to an announced MSC (CR EXTLAC:LACOD=..., MSCID=...;).

4. The MSCID found in CR EXTLAC is then translated to a signaling address and ahandover request is sent to the new MSC. The new cell is reported to the MSC.

5. The new MSC sends a handover request to the BSS associated with the cell(CR INTCELL).

6. The BSS seizes a traffic channel and provides a so-called handover referencenumber. The MSC seizes a trunk to the BSC.

7. The new MSC provides temporary routing information for the old MSC (handovernumber).

8. The old MSC switches a conference (in the group switch) on receiving thehandover number.

9. The trunk LTG reports ‘conference successful’.

10. A trunk call (e.g., ISUP) is set up to the new MSC.

11. A prepare handover is sent with the handover reference number to the oldBSC/mobile station.

12. The mobile station carries out a handover to the new cell. This is done using thehandover reference number transmitted by the new BSC.

13. The new BSC reports ‘handover performed’.

14. The message is transferred to the old MSC. It releases the conference.

15. The old MSC sends a traffic channel release message to the old BSS to releasethe old connection.


MN2513E7A0155

SIEMENS SIEMENS

SIEMENS SIEMENS

Trunk LTG

SCCP

SCCP

12

3

4

5

6

7

8

9

10

11

12

13

14

14

15

Handover Numbers

1788980 000...1788980 999

Handover Numbers

1788980 000...1788980 999

Fig. 23 Inter-MSC handover


MN2513E7A0156

6.26.26.26.2 Mobile Terminating CallMobile Terminating CallMobile Terminating CallMobile Terminating Call1. An own mobile subscriber number has been received. Interrogation is started in

the VLR/MSC of the calling party.

2. The dialed MSISDN is translated to a signaling address and a ‘send routinginformation’ is sent to the HLR of the called party.

3. The HLR searches in the HLR subscriber data for the VLR/MSC of the calledparty on the basis of the IMSI. The VLRISD stored there is converted to thesignaling address of the VLR/MSC. A ‘provide roaming number’ message is sentto the VLR/MSC of the called party.

4. The VLR/MSC of the called party takes a temporary directory number from thepool of mobile station roaming numbers (MSRN) and in standard cases (specifiedin the mobile project data) transfers it in international format to the HLR.

5. The HLR transfers the MSRN to the MSC of the calling party.

6. The MSC of the calling party analyzes the MSRN and sets up a trunk call (e.g.,ISUP) to the MSC/VLR of the called party. The subscriber is identified by meansof the MSRN output there.

7. The TMSI and LACOD stored in the VLR subscriber data are used to send apaging message to the appropriate BSC (CR INTCELL:LACOD= ...,BSCSPC=....,...;). The TMSI is transmitted in the broadcast channel.

8. If the subscriber is found in the area of the corresponding BSC, it responds witha paging response.


MN2513E7A0157

SIEMENS SIEMENS

SIEMENS SIEMENS

SCCP

1

SIEMENS SIEMENS

SCCP

VLR/MSC

2

5

3

4

SCCPMobile Station Roaming Numbers

1788980 000...1788980 999

Mobile Station Roaming Numbers

1788980 000...1788980 999

VLR/MSC

HLR

6

8

7

Fig. 24 Mobile terminating call


MN2513E7A0158

6.36.36.36.3 Administration of Mobile Station RoutingAdministration of Mobile Station RoutingAdministration of Mobile Station RoutingAdministration of Mobile Station RoutingNumbersNumbersNumbersNumbers

The handover numbers and mobile station roaming numbers discussed earlier can becombined to form so-called mobile station routing numbers. In other words, eachMSC has a pool of mobile station routing numbers that can, however, be distributedbetween mobile station roaming numbers and handover depending on the project.

The mobile station routing numbers are administered in the national format but aresent in the international format via MAP. This can be determined in the project data(with the DISP MPRDDAT parameters ‘MSRNFORM’ and ‘HONFORM’).

The mobile station routing numbers are entered with a directory number root – e.g.,1788980, and the range of directory numbers to be covered is specified (e.g.,1788980000...1788980999) with the following MML command:

CR MSRNB: MSRNP=1788980, MSRNR=3;

The parameter MSRNK indicates whether the directory numbers are to be used forhandover or roaming or for both.

If the LACOD parameter is specified, the routing numbers are output in accordancewith the location (LACOD). This can be used for mobile terminating calls in theintelligent network, for example.


MN2513E7A0159

Mobile Station Routing Number Administration

CR MSRNB : MSRNP = ,MSRNR= [,LACOD=] [,MSRNK=];

CAN MSRNB : MSRNP= [,LACOD=] ;

DISP MSRNB ;

MOD MSRNB : MSRNP= ,LACOD= ,NLACOD= [,NMSRNR=][,NMSRNK=] ;

MOD MSRNB : MSRNP= [,LACOD=] <,NMSRNR= ,NMSRNK=> ;

MOD MSRNB : MSRNP= ,NMSRNP= [,LACOD=] [,NMSRNR=][,NMSRNK=] ;

MSRNK={BOTH|HON|MSRN}MSRNP Mobile Station Routing Number PrefixMSRNR Mobile Station Routing Number Range

Fig. 25 Mobile station routing number administration


MN2513E7A0160


MN2513E7A0161

7777 ExercisesExercisesExercisesExercises


MN2513E7A0162


MN2513E7A0163

Exercise 1Exercise 1Exercise 1Exercise 1

Title:Title:Title:Title: MSC data

Objective:Objective:Objective:Objective: The Participant can detect errors in the MSC database

Prerequisite:Prerequisite:Prerequisite:Prerequisite:

TaskTaskTaskTask

An internal mobile call from the MSUB _________________________________

to the MSUB ______________________________________

was unsuccessful. Check the MSC database using what you have learned, andattempt to find the error.

Do not correct the error.

QueryQueryQueryQuery

What suggestions would you make to clear the error?


MN2513E7A0164


MN2513E7A0165


Title:Title:Title:Title: Mobile Station Routing Numbers

Objective:Objective:Objective:Objective: The participant can create mobile station routing numbers

Prerequisite:Prerequisite:Prerequisite:Prerequisite: Groups are used. Group 1 uses the existing HLRID+1, group 2the HLRID+2, group 3 the HLRID+3, etc.

For example, HLRID=70, group 1:71, group 2:72, group 3:73,etc.

TaskTaskTaskTask

� Display the mobile station routing numbers.

� Create the mobile station routing numbers as follows:

<NDC><HLRID>8.....

1000 mobile station roaming numbers should be available.

400 handover numbers should be available


What MML commands did you use?


MN2513E7A0166


MN2513E7A0167


Title:Title:Title:Title: Provider data

Objective:Objective:Objective:Objective: The participant can create mobile provider numbers

Prerequisite:Prerequisite:Prerequisite:Prerequisite: Groups are used. The individual groups use different inputvalues. They are distinguished by the number <team>.

TaskTaskTaskTask

� Create the connection to a mobile provider as follows:

Short number: ____________________ <team>

Provider name: ADAC<team>

Provider number/cell id: ______________ <team>/ ________________


BSC ORIG1:________________________

This number is not an emergency directory number.All directory numbers are routed to the destination ADAC:




MN2513E7A0168


MN2513E7A0169

8888 SolutionsSolutionsSolutionsSolutions


MN2513E7A0170


MN2513E7A0171

Solution 1Solution 1Solution 1Solution 1

Title:Title:Title:Title: MSC data

Objective:Objective:Objective:Objective: The participant can detect errors in the MSC database

Prerequisite:Prerequisite:Prerequisite:Prerequisite:

TaskTaskTaskTask

An internal mobile call from the MSUB _________________________________

to the MSUB ______________________________________

was unsuccessful. Check the MSC database using what you have learned, andattempt to find the error.

Do not correct the error.


What suggestions would you make to clear the error?


MN2513E7A0172


MN2513E7A0173


Title:Title:Title:Title: Mobile Station Routing Numbers

Objective:Objective:Objective:Objective: The participant can create mobile station routing numbers

Prerequisite:Prerequisite:Prerequisite:Prerequisite: Groups are used. Group 1 uses the existing HLRID+1, group 2the HLRID+2, group 3 the HLRID+3, etc.

For example, HLRID=70, group 1:71, group 2:72, group 3:73,etc.

TaskTaskTaskTask

� Display the mobile station routing numbers.

� Create the mobile station routing numbers as follows:

<NDC><HLRID>8.....

1000 mobile station roaming numbers should be available.

400 handover numbers should be available



MSC6/SR70/D2MMPK1V1702-F05/103 99-05-25 09:02:150907 CA SIEMENS0 2878/00007

CRMSRNB:MSRNP=1725480,MSRNR=3,MSRNK=MSRN; EXEC'D

END JOB 0907


CRMSRNB:MSRNP=1725481,MSRNR=2,MSRNK=HON; EXEC'D

END JOB 0908



MN2513E7A0174


END JOB 0911



END JOB 0915



END JOB 0920


MN2513E7A0175


Title:Title:Title:Title: Provider data

Objective:Objective:Objective:Objective: The participant can create mobile provider numbers

Prerequisite:Prerequisite:Prerequisite:Prerequisite: Groups are used. The individual groups use different inputvalues. They are distinguished by the number <team>.

TaskTaskTaskTask

� Create the connection to a mobile provider as follows:

Short number: ____________________ <team>

Provider name: ADAC<team>



BSC ORIG1: ________________________

This number is not an emergency directory number.All directory numbers are routed to the destination ADAC:



MSC6/SR70/D2MMPK1V1702-F05/103 99-05-25 09:10:471134 CFE NELSON22 2999/00007

CRPROVNAM:PROVNAM=ADAC1; EXEC'D

END JOB 1134


CRPROVNO:PROVNAM=ADAC1,LACOD=1,CI=2,PROVNO=01726000001; EXEC'D

END JOB 1190


MN2513E7A0176


CRPROVNO:PROVNAM=ADAC1,LACOD=1,CI=1,PROVNO=01726000002; EXEC'D

END JOB 1194


CRCPT:CODE=110,ORIG1=20,TRATYP=MOBPROV,PROVNAM=ADAC1; EXEC'D

END JOB 5341

01 2513e7a01 Msc Database

Documents

Transcript of 01 2513e7a01 Msc Database