MAP - Mobile Application Part
Mobility Management in GSM GSM services Short Message Service CAMEL = IN+GSM integration
Raimo Kantola/ k2002 Telecommunications Switching Technology 17 - 1
Course scope - lecture scope
H.323 or SIP IP CAS, R2 PABX ISDN CCS7 AN V5 Control Part Switching Fabric IP MAP SIP or ISUP HLR
Voice path
ISUP
INAP SCP
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 2
GSM system consists of 4 sub-systems
Radio or Air i/f
A-interface
MS = ME+SIM
Base Station Sub-system (BSS)
Network Sub-System (NSS)
O&M
Network Management Sub-system
MS - Mobile Station ME - Mobile Equipment SIM - Subscriber Identity Module BSS - Base Station Subsystem NSS - Network Sub-System
Raimo Kantola/ k2002
Main differences cmp to wire-line networks - air interface for the subscribers - mobility and roaming of users NB: the whole system is digital incl the ME.
17 - 3
Telecommunications Switching Technology
NSS interfaces are
VLR G VLR (B) MSC E MSC D C F EIR HLR std
A Base Station sub-system
MSC - Mobile Switching Center HLR - Home Location Register VLR - Visitor Location Register EIR - Equipment Identity Register NB: MSC+VLR always in the same node +H-interface: MSC - SMS Gateway interface +I - interface: MS - HLR (MS-MSC/VLR-HLR)
All NSS interfaces: B-H conform to the MAP protocol
Raimo Kantola/ k2002 Telecommunications Switching Technology 17 - 4
Milestones in MAP development
MAP1
phase 1
MAP2
phase 2
Phase 2+
Release96 Release97
...
In phase 2+ versioning is per operation package. This supports the idea of deploying small sets of features at a time in the network. If the remote systems does not understand the newest tricks, fall-back negotiation restores operation on the level of the previous version.
Raimo Kantola/ k2002 Telecommunications Switching Technology 17 - 5
MAP -operations can be mapped to interfaces
I/f
Elements
Mobility management 12 9 5 1 1
O&M
Call handling 4 1 1
B C D E F G
MSC- VLR GMSC- HLR VLR- HLR MSC- MSC MSC- EIR VLR- VLR HLR- SMSGW MSC- SMSGW
1 3
Supplementary services 1 10
Short messages 2 1
Sum
Sum
28
11
1 3 1 8
20 1 24 5 1 2 3 1 57
The table corresponds to MAPv2 This lecture does not discuss MSC-VLR interface operations nor O&M -operations.
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 6
Addressing MAP messages
MSC VLR HLR EIR
GT=358601332, PC=7895
AuC
(Authentication centre)
GT=358601212, PC=7896
MAP TCAP
SSN=8
MAP TCAP
SSN=7
MAP TCAP
SSN=6
MAP TCAP
SSN=9
MAP TCAP
SSN=6
SCCP MTP GT formats: IMSI MSISDN Hybrid MCC CC CC + + + MNC NDC NDC + + + MSIN SN MSIN
SCCP MTP
GT - Global Title PC - Point Code MCC - Mobile Country Code CC - Country Code MNC - Mobile Network Code NDC - National Destination Code MSIN - Mobile Subscriber Identity Number SN - Subscriber Number
17 - 7
Raimo Kantola/ k2002
Telecommunications Switching Technology
MAP uses the structured dialogue provided by TCAP
TC TC-INVOKE-req TC-INVOKE-req TC- BEGIN-req TR-BEGIN-req TC- CONTINUE-req TR-CONTINUE-req TC-CONTINUE-ind TC-END-ind BEGIN CONTINUE TR-CONTINUE-ind CONTINUE TR-END-ind END TR
MAP
Begin causes a transaction identifier to be reserved. The remote system can either continue the transaction or close it. Continue - messages are exchanged in a full-duplex mode. Closing options: based on pre-arrangement independently normally by the End-message or abnormally by an Abort message
Raimo Kantola/ k2002 Telecommunications Switching Technology 17 - 8
Mobility management is the most important feature in MAP
Location management Handover MSC-MSC during a call
handover is supported on many levels - also BSSAP (A- i/f protocol) is needed, but we do not cover that here
Authentication and security IMEI - mobile equipment id queries Subscriber management Fault recovery
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 9
Home Location Register - HLR - contains subscriber and service information
IMSI MSISDN
Subscriber information (location, etc) Service info (voice, fax, blocking modes, etc)
In a mobile terminated call, the right HLR can be found based on a prefix in MSISDN or if free numbering within the operator network is supported, a Global Title (MSISDN is embedded in the GT in SCCP) translation needs to be done first e.g. in a specific network element.
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 10
Location management maintains the location of the MSs in the HLR
(MSC) VLR SendIdentification UpdateLocation CancelLocation PurgeMS (MSC) VLR MAP/D HLR
SendIdentification requests MS info (IMSI, authentication) from the previous VLR. UpdateLocation updates the new location with the accuracy of a VLR area With PurgeMS VLR tells to HLR that MS is unreachable.
Telecommunications Switching Technology 17 - 11
Raimo Kantola/ k2002
With HLR query the MS is found in a Mobile terminated call
PSTN GMSC MAP/C HLR
ProvideRoamingNumber ProvideRoamingNumberACK ISUP - IAM
MAP/D VLR
MSC
ISUP - IAM
SendRoutingInformation SendRoutingInformationACK
MSRN - Mobile Subscriber Roaming Number - conforms to E.164 format (any exchange can pass along the number) - each MSC has a limited range of MSRNs - MSRN has a validity timeout - MSRN may be allocated on a call be call basis or for the duration of the visit
Raimo Kantola/ k2002 Telecommunications Switching Technology 17 - 12
Handover from MSC to MSC
MSC-A MAP/E
PrepareHandover Call ProcessAccessSignalling control mirrors A-interface to MSC-A responsibility SendEndSignal remains in (MSC-B and MS have radio channel) MSC-A ForwardAccessSignalling PrepareSubsequentHandover PrepareHandover Transports messages to be sent to the A-interface
MSC-B
MAP/E
MSC-B
SendEndSignal
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 13
Security operations ensure that only authorized subscribers can use the service
MSC MAP/D VLR
SendAuthenticationInfo
HLR EIR
CheckIMEI
Black list of suspect stolen phones ensures that stolen equipment can not be used for long
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 14
Subscriber management takes care of the subscriber data
MAP/D VLR
InsertSubscriberData
HLR
When the operator or the subscriber have changed any of subscriber data. When location has been updated. When a basic or a supplementary service is cancelled.
DeleteSubscriberData
With these operations all information residing in the VLR, can be manipulated, when the HLR has the master copy of the information. (HLR does not have some detailed location info)
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 15
Supplementary service operations are passed from MS via MSC/VLR to HLR
MS --> MSC/VLR --> HLR
RegisterSS EraseSS ActivateSS DeactivateSS InterrogateSS RegisterPassword GetPassword USSD operations Activation of call forwarding Switching off supplementary services Activation of call blocking Deactivation of supplementary services Interrogation of supplementary service settings Password setting for SS Password query to MS Unstructured SS data transport
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 16
USSD - Unstructured Supplementary Service Data transports SS data between MS and the network Network destinations can be e.g.
MSC, VLR, HLR HLR-> SCP, WWW-server
Data is in ascii(cmp DTMF) E.g. WAP - Wireless Application Protocol can in principle use the USSD service a latecomer among features
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 17
USSD uses the structured dialogue of TCAP
Dialogue is connection oriented A Dialogue has an identity Are independent of calls Message length is 80 octets, having max 91 Ascii characters a 7-bits
80 octets
1 octet
DCS DCS - Data Coding Scheme
USSD-string
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 18
USSD dialogue can be initiated by MS (pull) or by a server (push)
MAP MAP MSC/ HLR VLR ProcessUnstructuredSSRequest ProcessUnstructuredSSRequest Server
UnstructuredSSRequest UnstructuredSSRequest ACK UnstructuredSSRequest UnstructuredSSRequest ACK
UnstructuredSSRequest UnstructuredSSRequest ACK UnstructuredSSRequest UnstructuredSSRequest ACK An arbitrary nrof of requests Release
Release
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 19
Short Message Service
SMS-IWMSC SMSC store SMS-GMSC
MO-SMS
MT-SMS
SMSC - Short Message Service Center (or SC - Service Center) SMS-GMSC - Short message Gateway MSC, issuer of routing information query to HLR in MT-SMS SMS-IWMSC - Short message Inter-working MSC, routing MSC in MO-SMS service SMS-GW = SMS-IWMSC + SMS-GMSC MO - Mobile Originated MT - Mobile Terminated
SMSC - HLR operations: - MS short message buffer full - MS reachability - successful delivery of message
Telecommunications Switching Technology 17 - 20
Raimo Kantola/ k2002
Short message transport protocol stack
SME SMSC SMS-GMSC/ SMS-IWMSC MSC MS/SCP SM-AP SM-RP SM-LP SM-RP SM-LP SM-TP SM-RP SM-LP MAP User Info MAP TCAP SCCP MTP Non standard SME - Short Message Entity SM-LP - Short Message Link Protocol SM-RP - Short Message Relay Protocol SM-TP - Short Message Transfer Protocol SM-AP - Short Message Application Protocol
Raimo Kantola/ k2002 Telecommunications Switching Technology 17 - 21
SM-AP SM-TP SM-RP SM-LP
ForwardShortMessage
Messages in MO-SMS service
DTAP
MSC
MAP/E
SMSIWMSC
Vendor specific
SMSC
ForwardSM ForwardSM ACK
SubmitSM SubmitSM ACK
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 22
Messages in MT-SMS service
Vendor specific
SMSC
DeliverSM
SMSGMSC
MAP
MAP HLR MSC
SendRoutingInfoForSM SRIForSMResult ForwardSM
DeliverSM ACK
ForwardSM ACK
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 23
Status information is kept in HLR
MSC VLR
ReadyForSM MS has again a non-full buffer or it has become reachable InformServiceCenter
SMSIWMSC SMSGMSC
HLR
ReportSMDeliveryStatus Messages waiting/ successful delivery
AlertServiceCenter
SM destination subscriber can tell the network, that its SM buffer is full or that the subscriber has become unreachable. HLR stores the status. When Status is good for receiving, VLR gets the info and sends it to HLR. HLR informs those SMSCs that have reported themselves onto the waiting list.
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 24
Addressing of Short messages
MO-SMS Submit service MAP MSC MT-SMS Deliver service MAP MSC SMSC+ SMS-IWMSC SMS-GMSC
SCCP-DA: MAP-DA: MAP-OA: SM-TP-DA:
SMSC(GT) SMSC(GT) A-MSISDN B-MSISDN
SCCP-DA: MAP-DA: MAP-OA: SM-TP-OA:
MSC(GT) IMSI(GT) SMSC(GT) A-MSISDN
SMSC gets the IMSI of the B subscriber and the address of the VMSC by SRIForSM operation from the HLR. NB: Addresses are on three protocol layers!
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 25
CAMEL adapts the IN technology to GSM
CAMEL - Customized Application for Mobile network Enhanced Logic The goal is the capability of providing the home network services to visiting subscribers CAP - CAMEL Application Part is a subset of ETSI CoreINAP
phases (Capability Sets) 1 and 2 are ready
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 26
IN is a way of implementing services in nodes separate from exchanges
SCE
INAP
SMP SCF INAP
INAP
SRF
SDF
Network of STP nodes
SSF CCF exchange
Raimo Kantola/ k2002
SSF CCF exchange
INAP = IN Application Part = main protocol SSF - Service Switching Function maintains call state with CCF SCF - Service Control Function implements service logic SRF - Special Resource Function processes in-band signals SDF - Service Data Function is a database SCE - Service Creation Environment for creating new service logic SMP - Service Management Point implements mgt functions
17 - 27
Telecommunications Switching Technology
Features of the IN architecture ...
BCSM - Basic Call State Model is a standardized state machine in SSP - couples/ de-couples IN service logic from connection resources BCSM states (detection points) can be programmed to trigger on conditions queries to an SCF concerning a certain call BCSM architectural issue is that a call is also a service and therefore the architecture is service dependent INAP messages are independent of voice channel connections
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 28
Phase 1 CAMEL architecture
Home network HLR MAP gsmSCF
Requesting network
MAP
CAP
MAP VLR
CAP
Visited network
gsmSSF
Incoming call
gsmSSF MSC
GMSC
rerouteing
roaming leg
MO outgoing call or rerouteing
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 29
MS originated CAMEL call
MSC/VLR + gsmSSF gsmSCF CAP-InitialDP CAP-Connect PSTN
A C
ISUP-IAM
A - MSC gets the CAMEL service info from the VLR concerning the A subscriber, sees an active CAMEL service and hands the call to gsmSSF. gsmSSF queries gsmSCF:lle (service key, A-nr, B-nr, IMSI, location... B - gsmSCF can for example do a number translation C - MSC sets up a call using the received info
Raimo Kantola/ k2002
Telecommunications Switching Technology
17 - 30
Mobile terminated CAMEL call
PSTN ISUP-IAM GMSC + gsmSSF
HLR
gsmSCF
A B
ISUP-IAM
MAP-SendRoutingInfo MAP-SRInfoResult CAP-InitialDP CAP-Connect
C A - GMSC queries HLR of the location of the MS. HLR sends the terminating CAMEL service data of the subscriber. B - GMSC hands the call to gsmSSF, which queries gsmSCF gsmSCF returns C-number that is used for routeing the call C - GMSC sets up the call to C-number. If needed, GMSC can first do a new HLR query.
Raimo Kantola/ k2002 Telecommunications Switching Technology 17 - 31
IN+GSM integration based on CAMEL is a step towards 3G
CAPv1 supports only 7 operations CAPv1 call model has only a few triggering points (TDP - trigger detection point) CAPv2 has 22 operations Still no triggering for Short Messages CAMEL compatible equipment is in use in many networks
Raimo Kantola/ k2002 Telecommunications Switching Technology 17 - 32
