01 2513e7a01 MSC Database

MSC Database Administration
Siemens
(**++**Register-Z hlung**++**)1
Objectives
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
MN2513E7A01
Siemens
Contents
1 1.1 1.2 2 2.1 2.2 3 3.1 3.2 4 4.1 4.2 5 5.1 5.2 5.3 6 6.1 6.2 6.3 7 8 Cells and Location Areas Definition of Cells and Location Areas Using Cells and Location Areas Regional Roaming Subscription Functionality MML Commands Cell-Oriented Routing Functionality MML Commands Subscriber-Related Routing Functionality Administration Monitoring of Forwarded and Transferred Calls Function Administration Example Mobile Station Routing Numbers Inter-MSC Handover Mobile Terminating Call Administration of Mobile Station Routing Numbers Exercises Solutions 3 4 6 25 26 28 31 32 34 39 40 42 45 46 48 50 53 54 56 58 61 69
MN2513E7A01
Siemens
Cells and Location Areas
MN2513E7A01
Siemens
1.1
Definition 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 base station. 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 the signaling point code (CCS7 address) of the BSC. The location cell of a subscriber is not used for call setup in the MSC, but it is known in the MSC and is used for traffic measurement. A cell is internationally unambiguously addressed via the cell global identity. This consists of the components MCC/MNC/LACOD/CI. Location area As described already, the location of the subscriber in the MSC/VLR is not carried out 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 can contain several cells. One or several location areas are allocated unambiguously to an MSC. The address logic of the location area and thus of all the cells from the MSC contained within ensues via the signaling point code of the BSC. A location area is internationally unambiguously identifiable via the location area identity. This consists of the following components: MCC/MNC/LACOD.
MN2513E7A01
Siemens
SIEMENS
SIEMENS
MSC/VLR
Subscriber Data LAI
BSS
addressed by Signaling Point Code
BSS
addressed by Signaling Point Code
Cell Cell Cell Cell Location Area Cell Cell Cell Cell Cell
Cell Cell Cell Location Area
Cell: CGI = MCC/MNC/LACOD/CI Location Area: LAI = MCC/MNC/LACOD

Fig. 1 Cells and location areas
Location Area
MN2513E7A01
Siemens
1.2
1.2.1
1.2.1.1
Using Cells and Location Areas

Internal Cells and Location Areas
Function
The location of a mobile subscriber is defined in the MSC specific only to the location area. In other words, regardless of the cell in a location area in which the subscriber is 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 system via 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 location update that is stored on the SIM card. If the two LAIs do not match, the mobile station has changed location and is now positioned in a different location area of the same or another MSC. The mobile station sends the old LAI and the received LAI to the MSC. The MSC then analyzes the old LAI. If the location has changed within the MSC area, the MSC can detect the change by means of the database because the old LAI can be found as an internal cell/location area in the MSC in this case. The new LAI is then entered in the subscriber data of the VLR in order to make the mobile subscriber accessible for mobile terminating calls, for example.
MN2513E7A01
Siemens
SIEMENS
SIEMENS
VLR/MSC Cell/Lacode Cell/Lacode Data Data VLR MSUB VLR MSUB Data Data new LAI new LAI old LAI? old LAI?
old LAI new LAI
new LAI
SIM Card
SIM Card
old LAI
Fig. 2 Internal cell data for location update
old LAI
new LAI = old LAI?
MN2513E7A01
Siemens
Mobile terminating calls After a location update, the location area identity (LAI) is stored in the subscribers VLR data. If a provide roaming number is then received from the HLR during a mobile terminating call, a mobile station roaming number is output, linked with the VLR subscriber data and returned to the HLR. Next, a circuit connection (e.g. ISUP) is set up to the visited MSC/VLR of the called party by the visited MSC/VLR of the calling party. The subscriber can be easily identified since the called party number received (mobile station roaming number) is linked with the VLR subscriber data. The LAI and TMSI are stored in the VLR subscriber data. The CCS7 signaling address or addresses of the assigned base station systems are assigned to the location areas in the semipermanent location area / cell data. A paging signal is sent with the TMSI in the broadcast channel to all assigned base station systems. If the mobile station is in the corresponding BSC area, this information is returned as a paging response. A traffic channel is then switched to the appropriate base station system in reply. The LAI is therefore used for detecting the location area of the called subscriber and thus for detecting the corresponding base station system(s).
MN2513E7A01
Siemens
SIEMENS
SIEMENS
Cell/Lacod Cell/Lacod Data Data LAI LAI BSC SPC BSC SPC Netind Netind
ISUP: MSRN
VLR MSUB VLR MSUB Data Data LAI LAI TMSI TMSI Paging Response Paging (TMSI)
Broadcast TMSI
Broadcast TMSI
SIM Card
Broadcast TMSI = stored TMSI?
Fig. 3 Application of cells/location areas for mobile terminating calls
MN2513E7A01
Siemens
Internal MSC handover In the course of a handover, the base station system suggests possible cells to the MSC for the handover. The MSC can use the cells assigned to it to check whether they are internal cells with which it can perform an internal MSC handover.
10
MN2513E7A01
Siemens
SIEMENS
SIEMENS
Cell/Lacode Cell/Lacode data data Intra-MSC Handover suggested cell? suggested cell?
Handover required (List of possible cells)
Handover
SIM Card SIM Card
Fig. 4 Intra-MSC handover dependent on internal cell
MN2513E7A01
11
Siemens
1.2.1.2
MML Command
Cells assigned to an MSC are created with CR INTCELL. This MML command assigns a cell ID to an LACOD each time. The command can be entered multiply with the same LACOD but with different cell IDs. Another important assignment is the combination of the cell ID base station and SPC/NETIND (CCS7 signaling point code). The parameter location mark number must also be entered. This parameter is treated separately at a later stage. The parameter LOCNO (0...999999999999999) enables all cells in a network to be uniquely numbered and identified. The parameter can be used in the mobile call record, for example, in order to clearly identify the origin, or can be transferred to the IN (service control point) in order to perform origin-dependent routing, for example. The parameter ORIG2 allows distance-related charging because, on the one hand, it can be included in the mobile call records and, on the other hand, evaluated in the zoning converter. DISP INTCELL BSCSPC NETIND LACOD X <lacod> CI Result LACODs only CI BSCSPC NETIND LMN <bscspc> <netind> LACOD CI LMN <lacod> <ci> BSCSPC NETIND LMN Cell-dependent routing data
12
MN2513E7A01
Siemens
Creation and Display of Location Areas, Cells and Location Mark Numbers
CR 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>],.....; LACOD= <location area code>[,CI= <cell identification] or BSCSPC= <BSC signalling point code>, NETIND= <net indicator>,....; LMN= <location mark number>;
DISP INTCELL:
DISP LMN:
BSCSPC
NETIND
LACOD X <lacod>
CI
Result just LACODs CI BSCSPC NETIND LMN LACOD CI LMN
<bscspc>
<netind>
<lacod>
<ci>
BSCSPC NETIND LMN cell depend. Routing data
Fig. 5 Cell, location area and location mark number administration
MN2513E7A01
13
Siemens
1.2.1.3
Location Mark Numbers
A location mark number can be allocated to a cell. A location mark number is a celldependent full directory number which is applied cell-dependently as dialing information for a GSM emergency call.
14
MN2513E7A01
Siemens
SIEM ENS
SIEM ENS
MSC/VLR
PSTN BSS
PSTN
Emergency Center 1
Emergency Center 2 Emergency Button LMN= e.g.E8902CC110C9172
Emergency Button LMN= e.g.E8901CC110C9172
Fig. 6 Location mark number
MN2513E7A01
15
Siemens
1.2.2
1.2.2.1
External Location Areas

Function
Location change from a known VLR/MSC If an MSUB changes the location from an VLR/MSC that is known in the new VLR/MSC, the IMSI can be requested from the old VLR. This dispenses with the need to transmit the IMSI via the air interface this is undesirable because it would be transferred without encryption. In addition to the LACODs of neighboring MSCs, the LACODs of MSCs considered to 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 the LACODs of all national MSCs/VLRs in all national MSCs/VLRs.
16
MN2513E7A01
Siemens
SIEMENS
SIEMENS
SIEMENS
External Lacode External Lacode Data Data

SIEMENS
Old VLR/MSC
old LAI? old LAI? => VLRISD => VLRISD IMSI New VLR/MSC
VLR MSUB VLR MSUB Data Data IMSI IMSI
old LAI new LAI
IMSI
new LAI
SIM Card
SIM Card
old LAI
Fig. 7 Location area data for location update
old LAI
new LAI = old LAI?
MN2513E7A01
17
Siemens
Inter-MSC handover A minimum of all location areas of neighboring MSCs must be created as external location 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 first compares the first cell in the list with the internal cell database so as to initiate an internal MSC handover if necessary. If the cell is not found there, a search for the cell is made in the external location area database. The external database contains the external LACODs and the associated MSCID. If the cell is found there, the MSCID is converted to a CCS7 signaling address and the inter-MSC handover is initiated.
18
MN2513E7A01
Siemens
SIEMENS
SIEMENS
SIEMENS
Inter-MSC handover
SIEMENS
External Lacode External Lacode data data suggested cell? suggested cell? =>MSCID =>MSCID
Cell/Lacode Cell/Lacode data data suggested cell? suggested cell?
Handover request (List of possible cells)
Handover
SIM Card SIM Card
Fig. 8 Location area data for inter-MSC handover
MN2513E7A01
19
Siemens
1.2.2.2
MML Commands
The command CR EXTLAC reports external LACODs in an MSC/VLR. A LACOD is linked with an MSCID for each command call. The MSCID is used for finding the foreign MSC for handover later. A VLRISDN may also be assigned as an optional parameter. The VLRISDN is used, for example, for addressing the VLR for location updates. If no VLRISDN is entered, the MSCID is used instead. The commands CAN EXTLAC and DISP EXTLAC are used to respectively cancel and display external LACODs. MOD EXTLAC can modify either a LACOD, MSCID or VLRISDN.
20
MN2513E7A01
Siemens
External LACOD Administration CR EXTLAC: CAN EXTLAC: DISP EXTLAC: MOD EXTLAC: MOD EXTLAC: LACOD= LACOD= ; MSCID= ; LACOD= ,NLACOD= ; LACOD= <,NMSCID= ,NVLRISD= >; ,MSCID= [,VLRISD= ];
Fig. 9 External LAC administration
MN2513E7A01
21
Siemens
1.2.2.3
Structured LACODs
A great deal of administration is required to create the LACODs of all MSCs/VLRs belonging to a PLMN in all MSCs/VLRs of this PLMN. Structured LACODs provide a solution to this problem. In accordance with GSM, a LACOD has 16 bits. If a structured LACOD is used, the 16 bits are distributed project-specifically to bits per MSC (DISP MPRDDAT MSCLACOD) and bits per LACOD belonging to the corresponding MSC. If the LACODs of a different MSC/VLR are then announced in an MSC/VLR using CR EXTLAC, only the MSC-specific part of the 16 bits has to be defined. The remaining bits can assume any value at all. Example: The number of bits for the LACOD must be set to 8 in the mobile project data i.e., in this case, 8 bits are assigned to the MSC-specific part and the supplement to make up the 16 bits represents the LACOD for the corresponding MSC. If the MSC-specific part has the binary value 1, the following LACOD range is obtained for the MSC: MSC-specific part Specific part Decimal of the LACODs LACOD value of the MSC 256 257 511
00000001 00000000 00000001 00000001 0 0 0 0 0 0 0 1 ................ 00000001 11111111
Since the decimal value range (e.g., 256..511) is permanently assigned to the corresponding 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, the following 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,..).
22
MN2513E7A01
Siemens
Example structured LACOD:

Mobile Project Data:
LENGTH OF MSC EXTERNAL LACOD (MSCLACOD): 8
8 bits MSC-specific (MSCLACOD): 8
8 bits for the LACOD of the MSC

LACOD range decimal
MSC-specific
LACOD-specific
CR EXTLAC:LACOD=
00000000 00000000 00000000 ..... 00000000 00000001 00000001 00000001 ....... 00000001 ................
Fig. 10 Structured LACOD
00000000 00000001 00000010 ....... 11111111 00000000 00000001 00000010 .......... 11111111 ................
0 1 2 ....... 255 256 257 258 ........ 511 ...............
256
.....................
MN2513E7A01
23
Siemens
24
MN2513E7A01
Siemens
Regional Roaming Subscription
MN2513E7A01
25
Siemens
2.1
Functionality
Regional zones can be assigned to a mobile subscriber for each PLMN whose services he is entitled to use (e.g. wireless loop subscriber). The zones limit the possibility to certain location areas or cells. The subscriber is assigned zone codes used for identifying these permitted roaming zones. The zones themselves are defined in the VLR. During a location update the zone codes of zones permitted for the 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 of the PLMN in his present location area by comparing the mobile subscriber zone codes 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 of these zones is assigned in the HLR to a subscriber, he/she is only permitted to use the service (location update) in those LACODs. Regional roaming administration based on cells, roaming restriction based on LACODs: In this case the cell IDs constituting a roaming zone are specified in the VLR. If one of these zones is assigned in the HLR to a subscriber, he/she is only permitted to use the service (location update) in the location area to which the corresponding cell or cells are assigned. Regional roaming administration based on cells, roaming restriction based on cells: In this case the cell IDs constituting a roaming zone are specified in the VLR. If one of these zones is assigned in the HLR to a subscriber, he/she is only permitted to use location updates in the location area to which the corresponding cell or cells are assigned. A check is performed during call setup (MOC/MTC, mobile terminating SMS, mobile origin SMS, etc.) to determine whether the subscriber is located in any of the permitted cells.
26
MN2513E7A01
Siemens
SIEMENS
SIEMENS
HLR
Roaming Zone
SIEMENS SIEMENS
Regional Regional Roaming Roaming Data Data Local Area Local Area or Cell ids or Cell ids
HLR MSUB HLR MSUB Data Data Roaming Zone Roaming Zone
VLR/MSC
Roaming Roaming allowed allowed call not call not allowed allowed Roaming Roaming allowed allowed call call allowed allowed
Roaming Zone Administration based on Cell. Cell checked during Call setup
Roaming Zone Administration based on Cell. Subscription in the whole location area
allowed allowed allowed allowed

Roaming Zone Administration based on Location Area. Subscription in the whole location area
allowed too allowed too allowed allowed
Fig. 11 Roaming zones
MN2513E7A01
27
Siemens
2.2
MML 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 and RSCELLID. FEAT=REGRO basic feature: The regional subscription is administered on the basis of the location area. FEAT=REGRO&RSCELLBA supplementary feature: The regional subscription is administered using the cell ID but is effective for location areas. FEAT=REGRO&RSCELLID supplementary feature: Administered like RSCELLBA but 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 zone number (roaming zone) in the MSC/VLR. The MML command ENTR RSSERV assigns the zones defined in the MSC/VLR to a mobile subscriber as permitted roaming areas. Rule: If the zone 0 is assigned to the subscriber in addition to other zones for RSCELLBA, the subscriber is allowed to use the service in the corresponding VLRs in the known zones (LACODs) and in all other VLRs.
28
MN2513E7A01
Siemens
Regional Subscription Administration Feature in the DISP MSERVOPT REGRO REGRO& RSCELLBA REGRO& RSCELLID In the VLR CR RSZONE: In the HLR ENTR RSSERV: MSIN= , PLMN= <CC>-[<NDC>], ZCODE=<roaming zone number>, ZCODE=<roaming zone number>, RSAREA= <cell id or lacode> ; GSM Basic Feature: Administration and check based on LACOD Supplementary Feature: Administration based on CELL, check based on LACOD Supplementary Feature: Administration based on CELL, call setup check based on Cell
Fig. 12 Administration of regional subscription
MN2513E7A01
29
Siemens
30
MN2513E7A01
Siemens
Cell-Oriented Routing
MN2513E7A01
31
Siemens
3.1
Functionality
Alongside the cell-dependent management of real emergency calls, there is the possibility to cell-dependently convert certain service abbreviated numbers into full directory numbers. This could, for instance, be applied when the operator-specific service numbers, breakdown service, etc. are to be accessed cell-dependently. This means, for example, that depending on the location on the freeway that a car breaks down the call is connected to different breakdown service points although the same abbreviated number is used. This takes place through the evaluation of the cell in which the subscriber is currently located and the conversion of the dialed abbreviated numbers into various full directory numbers.
32
MN2513E7A01
Siemens
SI EM ENS
SIEMEN S
MSC/VLR
PSTN
PSTN
BSS
Service Center 1 Short Service Number Long Number = e.g. 08917389 Short Service Number
Service Center 2
Long Number = e.g. 082217389
Fig. 13 Cell-dependent routing
MN2513E7A01
33
Siemens
3.2
MML Commands
The setup of the database for cell-dependent routing consists of several steps: a) The service provider name must be announced with the command CR PROVNAM (create provider name). In addition, whether the call to this provider should be handled as an emergency call can be specified in this command. b) The full directory numbers per origin cell are specified with the command CR PROVNO (create provider number) for the provider setup. c) The general code via which the provider should be able to be reached is set up and linked with the provider name with the command CR CPT (create code point). The following display commands are reachable for the display: DISP PROVNAM, DISP PROVNO, DISP CPT.
34
MN2513E7A01
Siemens
Creation and Display of Cell dependent Routing

CR PROVNAM: PROVNAM=<provider name>, TYPE={ORD|EM},.....; PROVNAM=<provider name>, PROVNO=<digit combination cell dependent>, CI=<cell id>, LACOD=<location area code>; CODE=<cell independent short code>, TRATYP=MOBPROV, PROVNAM=<provider name>,....; PROVNAM=<provider name>; PROVNO=<digit combination cell dependent>; CODE=<cell independent short code>, {TRATYP=MOBPROV | PROVNAM=<provider name>};
CR PROVNO:
CR CPT:
DISP PROVNAM: DISP PROVNO: DISP CPT:
Fig. 14 Cell-dependent routing administration
MN2513E7A01
35
Siemens
3.2.1
Example
In the next example, the provider number for a second emergency number is displayed in addition to the official GSM number. The subscriber dials 110. The incoming normal call is analyzed in the digit translator and routed to the provider EMCAL110. Cell-dependent full emergency numbers are created for this provider. They begin with E and are followed by the PSTN local area code. The remaining digits are determined by national legal requirements. With the long directory number, the call is again routed to the digit translator and a destination in the PSTN is addressed from there.
36
MN2513E7A01
Siemens
LAC=05051
LAC=05021
LAC=05721
PSTN
SIEMENS
SIEMENS
CI=10191 CI=10191 E05021 E05021
CI=10192 CI=10192 E05021 E05021
CI=3590 CI=3590 E05051 E05051
CI=10200 CI=10200 E05021 E05021
CI=2381 CI=2381 E05721 E05721
<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! .....
Cell Id 110
Fig. 15 Example: provider number used for emergency calls
MN2513E7A01
37
Siemens
38
MN2513E7A01
Siemens
Subscriber-Related Routing
MN2513E7A01
39
Siemens
4.1
Functionality
The subscriber-related routing feature enables mobile originating calls (MOC) to be routed to specific destination numbers defined in the mobile subscriber's HLR. To request a connection of this kind, the mobile subscriber generally dials an abbreviated directory number. The MSC detects from the associated code point that the requested connection belongs to a service provider and to a specific service. It therefore 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 not specified exactly in the MSC, but identified by a service code Y (Y=0,1,2,...,9). If the mobile subscriber is set up with multinumbering i.e., the subscriber has more than one SN, the MSC uses the SN of the base MSISDN. The service number is used to carry out global title translation and then an interrogation of the HLR of the calling subscriber. In each case, the full service directory number is sent to the HLR. The HLR determines the service address created for this service and, in some cases, for this mobile subscriber, and this address is then sent to the MSC in response to the interrogation (see OMN: SSSSU). The service address is defined in the HLR using one of the following methods: a fixed entered directory number, which usually corresponds to the ISDN numbering 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 least xxx, although parts of the SN may also be necessary for routing a mobile station roaming number which is requested by the HLR of the service center; in this case, the connection is similar to a pseudo MTC to a service center. The service address received as interrogation response in the HLR is used to execute routing to the service center in the MSC.
40
MN2513E7A01
Siemens
Service SIEMENS short MSC/VLR number
SIEMENS
Provider data: Provider data: Service specific Service specific indication Y indication Y
PBX
Service Center
b) MSRN
Interrogation Send Routing Info: <CC><NDC>1<Y><SN>
a) CC/NDC/<service Center> b) MSRN from service Center c) CC/NDC/<service Center>/<SN> b) MSRN Request
SIEMENS
SIEMENS
HLR
Subscriber related Service data Subscriber related Service data for Service Indication Y: for Service Indication Y: a) Fixed address: a) Fixed address: Service Center Number Service Center Number as Interrogation Response as Interrogation Response b) Service Center Address: b) Service Center Address: global title to request an MSRN global title to request an MSRN from aaService Center from Service Center c) Subscriber dependent c) Subscriber dependent Address: Address: Service Center Directory Number Service Center Directory Number inclusive SN as Interrogation Result inclusive SN as Interrogation Result
Fig. 16 Subscriber-related routing
MN2513E7A01
41
Siemens
4.2
Administration
In the MSC/VLR, the abbreviated directory number must be created using a code point and must also refer to a provider (PROVNAM). The provider is assigned a SERVICE INDICATOR (SERVIND) in the CR PROVNO command. This index has one character and corresponds to the service indicator Y described earlier. The service indicator is inserted in the MAP message to the HLR with a leading 1 between the NDC and the SN of the calling party. If the HLR does not find the calling party number in the HLR subscriber data, it branches to the subscriber-related service data that were specified with CR SUBRSERV and assigned to a subscriber with ENTR OPRSERV.
42
MN2513E7A01
Siemens
Service short code:233
SIEMENS
SIEMENS
CR CPT: CODE=233, TRATYP=MOBPROV, PROVNAM=SERV233; CR PROVNAM: PROVNAM=SERV233, SERVIND=3; CR CPT:CODE=0049 178 13 89, TRATYP=MOBINTER,...;
Interrogation Send Routing Info for: 0049178138942361
FIXED 0049 178 99 233 SCADR MSRN from service Center SUBDEP 0049 178 99 233 89 42361
SIEMENS
SIEMENS
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;
Fig. 17 Example: administration
Subscriber Related Routing Administration In the VLR/MSC CR PROVNAM: In the HLR CR SUBRSERV: OPRSERV= ,SERV= ,IND= ,ADDRTYPE= ,ADDR= ; PROVNAM= ,SERVIND= ;
ENTR OPRSERV: MSIN= ,OPRSERV= ,SERV=
Fig. 18 Subscriber-related routing: MML commands
MN2513E7A01
43
Siemens
44
MN2513E7A01
Siemens
Monitoring of Forwarded and Transferred Calls
MN2513E7A01
45
Siemens
5.1
Function
The so-called fraud protection package has been introduced for CF and CT in order to prevent mobile subscribers from committing fraud by switching calls with call forwarding 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 call forwarding or call transfer calls per party, or issues a warning when a specified number of calls has been exceeded. Manual monitoring: CF and CT calls can be indicated according to a specified call duration or number of simultaneous calls. Forced release: CT and CF calls that were conspicuous during manual monitoring can be manually released.
46
MN2513E7A01
Siemens
Japan
SIEMENS SIEMENS
1 2
SIEMENS SIEMENS
SIEMENS SIEMENS
USA
MSC
SIEMENS
SIEMENS
MSUB with CT or CF
n Russia
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
MN2513E7A01
47
Siemens
5.2
Administration
Threshold values for the maximum number of simultaneously existing CF or CT calls are entered with the MML command ACT SMSUBDET (suspect MSUB detection). Moreover, thresholds for the maximum number of calls can also be administered. A warning is output each time this number is exceeded. Note that CT calls always have an incoming and an outgoing side and must therefore be considered as two calls in each 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. The command is often used if the threshold value for a display for an MSUB has been exceeded. DISP SMCALL displays MSUBs that have exceeded either a specified number of CT or 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.
48
MN2513E7A01
Siemens
Fraud Protection Administration DISP MSERVOPT: ACT SMSUBDET : DACT SMSUBDET ; DISP SMSUBDET ; DISP SMSUB : DISP SMCALL : REL SMCALL : <IMSI= ,CALL= ,CDUR=> ; IMSI= ; IMSI= ,CALLIND= ; FEAT=FRAUDPR; [INFOTHR=] [,RELTHR=] ;
Fig. 21 Fraud protection for CF/CT
MN2513E7A01
49
Siemens
5.3
Example
50
MN2513E7A01
Siemens
Display to check if feature is generally activ DISP MSERVOPT:FEAT=FRAUDPR; DISPMSERVOPT:FEAT=FRAUDPR; EXEC'D
SERVICE/ CONNECTION RADIO CHANNEL ALTERNATIVE FEATURE 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; SUSPECT MOBILE SUBSCRIBER DETECTION STATUS: ACTIVE END JOB 9589 3 CF or 2 CT calls for MSUB 262085300000000 have happened INFORMATION THRESHOLD: 2 RELEASE THRESHOLD: 4 EXEC'D
D900#/MSC00000/SR6012345678-NNN/410 9628 2996/08702 SUSPECT MOBILE SUBSCRIBER DETECTION REASON: MAXIMUM NUMBER OF CALLS EXCEEDED
96-11-12
12:34:07
IMSI : 262085300000000 Display MSUB 262085300000000 DISP SMCALL:IMSI=262085300000000; DISPSMCALL:IMSI=262085300000000; SUSPECT MOBILE CALLS IMSI = 262085300000000 CALL-DURATION CALLIND FTN/CDPA TYPE HOUR MINUTE MSISDN --------+---------------+-----+------+-------+--------------1 0893304 CT 0 3 491785110000 2 0893303 CT 0 3 491785110000 3 0893302 CT 0 0 491785110000 4 0893301 CT 0 0 491785110000 END JOB 9629 EXEC'D
Realease of the first Call Transfer-connection (Callind=1 or 2): REL SMCALL:IMSI=262085300000000,CALLIND=2 DANGEROUS COMMAND RELSMCALL READY TO EXECUTE < ; RELSMCALL:IMSI=262085300000000,CALLIND=2; EXEC'D
Fig. 22 Example: fraud protection
MN2513E7A01
51
Siemens
52
MN2513E7A01
Siemens
Mobile Station Routing Numbers
MN2513E7A01
53
Siemens
6.1
Inter-MSC Handover
1. The mobile station and BTS (base transceiver station) measure, for example, the transmission quality and reception level. The mobile station also measures the reception of neighboring cells and transfers the values to the BSS. 2. If required, the BSC generates a list of suggested cells from the measurement results with up to 16 cells, and sends the list with a handover required to the corresponding MSC. 3. The MSC checks the first cell in the list to determine whether it belongs to the MSCs own area (CR INTCELL:CI=, LACOD=...;). If not, it checks if the cell belongs to an announced MSC (CR EXTLAC:LACOD=..., MSCID=...;). 4. The MSCID found in CR EXTLAC is then translated to a signaling address and a handover 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 reference number. The MSC seizes a trunk to the BSC. 7. The new MSC provides temporary routing information for the old MSC (handover number). 8. The old MSC switches a conference (in the group switch) on receiving the handover 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 old BSC/mobile station. 12. The mobile station carries out a handover to the new cell. This is done using the handover 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 release the old connection.
54
MN2513E7A01
Siemens
3 2
SIEMENS SIEMENS
1 11
Trunk LTG
15
8 9 14
SCCP
14
12 10
SIEMENS SIEMENS
Handover Handover Numbers Numbers
SCCP
1788980 000 1788980 000 .. .. .. 1788980 999 1788980 999

Fig. 23 Inter-MSC handover
5 6 13
MN2513E7A01
55
Siemens
6.2
Mobile Terminating Call
1. 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 routing information is sent to the HLR of the called party. 3. The HLR searches in the HLR subscriber data for the VLR/MSC of the called party on the basis of the IMSI. The VLRISD stored there is converted to the signaling address of the VLR/MSC. A provide roaming number message is sent to the VLR/MSC of the called party. 4. The VLR/MSC of the called party takes a temporary directory number from the pool of mobile station roaming numbers (MSRN) and in standard cases (specified in 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 means of the MSRN output there. 7. The TMSI and LACOD stored in the VLR subscriber data are used to send a paging 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 with a paging response.
56
MN2513E7A01
Siemens
SIEMENS
SIEMENS
VLR/MSC
5
SCCP
SIEMENS
SIEMENS
HLR
SCCP
SIEMENS
SIEMENS
Mobile Station Mobile Station Roaming Numbers Roaming Numbers
SCCP
1788980 000 1788980 000 .. .. .. 1788980 999 1788980 999

Fig. 24 Mobile terminating call
VLR/MSC
MN2513E7A01
57
Siemens
6.3
Administration of Mobile Station Routing Numbers
The handover numbers and mobile station roaming numbers discussed earlier can be combined to form so-called mobile station routing numbers. In other words, each MSC has a pool of mobile station routing numbers that can, however, be distributed between mobile station roaming numbers and handover depending on the project. The mobile station routing numbers are administered in the national format but are sent 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 for handover or roaming or for both. If the LACOD parameter is specified, the routing numbers are output in accordance with the location (LACOD). This can be used for mobile terminating calls in the intelligent network, for example.
58
MN2513E7A01
Siemens
Mobile Station Routing Number Administration CR MSRNB : CAN MSRNB : DISP MSRNB ; MOD MSRNB : MOD MSRNB : MOD MSRNB : MSRNP= ,LACOD= ,NLACOD= [,NMSRNR=] [,NMSRNK=] ; MSRNP= [,LACOD=] <,NMSRNR= ,NMSRNK=> ; MSRNP= ,NMSRNP= [,LACOD=] [,NMSRNR=] [,NMSRNK=] ; MSRNP = ,MSRNR= [,LACOD=] [,MSRNK=]; MSRNP= [,LACOD=] ;
MSRNK={BOTH|HON|MSRN} MSRNP Mobile Station Routing Number Prefix MSRNR Mobile Station Routing Number Range
Fig. 25 Mobile station routing number administration
MN2513E7A01
59
Siemens
60
MN2513E7A01
Siemens
Exercises
MN2513E7A01
61
Siemens
62
MN2513E7A01
Siemens
Exercise 1
Title: Objective: Prerequisite: Task
An internal mobile call from the MSUB _________________________________ to the MSUB ______________________________________ was unsuccessful. Check the MSC database using what you have learned, and attempt to find the error. Do not correct the error. MSC data The Participant can detect errors in the MSC database
Query
What suggestions would you make to clear the error?
MN2513E7A01
63
Siemens
64
MN2513E7A01
Siemens
Exercise 2
Title: Objective: Prerequisite:
Mobile Station Routing Numbers The participant can create mobile station routing numbers Groups are used. Group 1 uses the existing HLRID+1, group 2 the HLRID+2, group 3 the HLRID+3, etc. For example, HLRID=70, group 1:71, group 2:72, group 3:73, etc.
Task
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
Query
What MML commands did you use?
MN2513E7A01
65
Siemens
66
MN2513E7A01
Siemens
Exercise 3
Create the connection to a mobile provider as follows: Short number: ____________________ <team> Provider name: ADAC<team> Provider number/cell id: ______________ <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: Provider data The participant can create mobile provider numbers Groups are used. The individual groups use different input values. They are distinguished by the number <team>.
Query
MN2513E7A01
67
Siemens
68
MN2513E7A01
Siemens
Solutions
MN2513E7A01
69
Siemens
70
MN2513E7A01
Siemens
Solution 1
An internal mobile call from the MSUB _________________________________ to the MSUB ______________________________________ was unsuccessful. Check the MSC database using what you have learned, and attempt to find the error. Do not correct the error. MSC data The participant can detect errors in the MSC database
Query
What suggestions would you make to clear the error?
MN2513E7A01
71
Siemens
72
MN2513E7A01
Siemens
Solution 2
Title: Objective: Prerequisite:
Mobile Station Routing Numbers The participant can create mobile station routing numbers Groups are used. Group 1 uses the existing HLRID+1, group 2 the HLRID+2, group 3 the HLRID+3, etc. For example, HLRID=70, group 1:71, group 2:72, group 3:73, etc.
Task
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
Query
MSC6/SR70/D2MMPK1V1702-F05/103 0907 CA SIEMENS0 99-05-25 2878/00007 EXEC'D 09:02:15
CRMSRNB:MSRNP=1725480,MSRNR=3,MSRNK=MSRN; END JOB 0907 MSC6/SR70/D2MMPK1V1702-F05/103 0908 CA SIEMENS0 99-05-25 2878/00007
09:02:19 EXEC'D
CRMSRNB:MSRNP=1725481,MSRNR=2,MSRNK=HON; END JOB 0908 MSC6/SR70/D2MMPK1V1702-F05/103 0911 CA SIEMENS0 99-05-25 2878/00007
09:02:23
MN2513E7A01
73
Siemens
EXEC'D
09:02:27 EXEC'D
09:02:32 EXEC'D
CRMSRNB:MSRNP=1725484,MSRNR=2,MSRNK=HON; END JOB 0920
74
MN2513E7A01
Siemens
Solution 3
Create the connection to a mobile provider as follows: Short number: ____________________ <team> Provider name: ADAC<team> Provider number/cell id: ______________ <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: Provider data The participant can create mobile provider numbers Groups are used. The individual groups use different input values. They are distinguished by the number <team>.
Query
MSC6/SR70/D2MMPK1V1702-F05/103 1134 CFE NELSON22 CRPROVNAM:PROVNAM=ADAC1;
99-05-25 2999/00007
09:10:47
EXEC'D
END JOB 1134
MSC6/SR70/D2MMPK1V1702-F05/103 1190 CFE NELSON22
99-05-25 2999/00007
09:14:34
CRPROVNO:PROVNAM=ADAC1,LACOD=1,CI=2,PROVNO=01726000001;
EXEC'D
END JOB 1190
MN2513E7A01
75
Siemens
99-05-25 2999/00007
09:14:38
CRPROVNO:PROVNAM=ADAC1,LACOD=1,CI=1,PROVNO=01726000002;
EXEC'D
END JOB 1194
99-05-25 2878/00007
13:02:17
CRCPT:CODE=110,ORIG1=20,TRATYP=MOBPROV,PROVNAM=ADAC1;
EXEC'D
END JOB 5341
76
MN2513E7A01

01 2513e7a01 MSC Database

Uploaded by

Document Information

Original Description:

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

01 2513e7a01 MSC Database

Uploaded by

Copyright:

Available Formats

MSC Database Administration

MSC Database Administration

MSC Database Administration

MSC Database Administration

Cells and Location Areas

MSC Database Administration

Definition of Cells and Location Areas

MSC Database Administration

Cell Cell Cell Location Area

Cell: CGI = MCC/MNC/LACOD/CI Location Area: LAI = MCC/MNC/LACOD

MSC Database Administration

Using Cells and Location Areas

MSC Database Administration

old LAI new LAI

new LAI = old LAI?

MSC Database Administration

MSC Database Administration

Broadcast TMSI = stored TMSI?

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

MSC Database Administration

MSC Database Administration

Handover required (List of possible cells)

Fig. 4 Intra-MSC handover dependent on internal cell

MSC Database Administration

MSC Database Administration

Result just LACODs CI BSCSPC NETIND LMN LACOD CI LMN

BSCSPC NETIND LMN cell depend. Routing data

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

MSC Database Administration

Location Mark Numbers

MSC Database Administration

Emergency Center 2 Emergency Button LMN= e.g.E8902CC110C9172

Emergency Button LMN= e.g.E8901CC110C9172

Fig. 6 Location mark number

MSC Database Administration

External Location Areas

MSC Database Administration

External Lacode External Lacode Data Data

VLR MSUB VLR MSUB Data Data IMSI IMSI

old LAI new LAI

new LAI = old LAI?

MSC Database Administration

MSC Database Administration

Cell/Lacode Cell/Lacode data data suggested cell? suggested cell?

Handover request (List of possible cells)

Fig. 8 Location area data for inter-MSC handover

MSC Database Administration

MSC Database Administration

Fig. 9 External LAC administration

MSC Database Administration

00000001 00000000 00000001 00000001 0 0 0 0 0 0 0 1 ................ 00000001 11111111

MSC Database Administration

Example structured LACOD:

8 bits MSC-specific (MSCLACOD): 8

8 bits for the LACOD of the MSC

0 1 2 ....... 255 256 257 258 ........ 511 ...............

MSC Database Administration

MSC Database Administration

Regional Roaming Subscription

MSC Database Administration

MSC Database Administration

allowed allowed allowed allowed