Mobile Application Part Contents Facilities provided Published specification Implementation MAP signaling References Navigation menu3GPP TS 09.023GPP TS 29.0023GPP2 X.S0004YateITU-T Recommendation Q.2220

Signaling System 7Application layer protocols


SS7protocolmobile core networksGPRS core networksShort message service centerServing GPRS Support NodeETSI3GPPCDMA2000AMPSIS-136cdmaOneIS-413GPP23GPP2 X.S0004Transaction Capabilities Application PartSS7 protocolsIPSIGTRANYateGSMUMTSCircuit SwitchedPacket SwitchedMobile Switching CenterServing GPRS Support Node




The Mobile Application Part (MAP) is an SS7 protocol that provides an application layer for the various nodes in GSM and UMTS mobile core networks and GPRS core networks to communicate with each other in order to provide services to users. The Mobile Application Part is the application-layer protocol used to access the Home Location Register, Visitor Location Register, Mobile Switching Center, Equipment Identity Register, Authentication Centre, Short message service center and Serving GPRS Support Node (SGSN).




Contents





  • 1 Facilities provided


  • 2 Published specification


  • 3 Implementation


  • 4 MAP signaling


  • 5 References




Facilities provided


The primary facilities provided by MAP are:



  • Mobility Services: location management (to support roaming), authentication, managing service subscription information, fault recovery,

  • Operation and Maintenance: subscriber tracing, retrieving a subscriber's IMSI


  • Call Handling: routing, managing calls whilst roaming, checking that a subscriber is available to receive calls

  • Supplementary Services

  • Short Message Service


  • Packet Data Protocol (PDP) services for GPRS: providing routing information for GPRS connections

  • Location Service Management Services: obtaining the location of subscriber


Published specification


The Mobile Application Part specifications were originally defined by the GSM Association, but are now controlled by ETSI/3GPP. MAP is defined by two different standards, depending upon the mobile network type:


  • MAP for GSM (prior to Release 4) is specified by 3GPP TS 09.02 (MAP v1, MAP v2)

  • MAP for UMTS ("3G") and GSM (Release 99 and later) is specified by 3GPP TS 29.002 (MAP v3)

In cellular networks based on ANSI standards (currently CDMA2000, in the past AMPS, IS-136 and cdmaOne) plays the role of the MAP a similar protocol usually called IS-41 or ANSI-41 (ANSI MAP). Since 2000 it is maintained by 3GPP2 as N.S0005 and since 2004 it is named 3GPP2 X.S0004.



Implementation


MAP is a Transaction Capabilities Application Part (TCAP) user, and as such can be transported using 'traditional' SS7 protocols or over IP using Transport Independent Signalling Connection Control Part (TI-SCCP);[1] or using SIGTRAN.


Yate is a partial open source implementation of MAP.



MAP signaling


In mobile cellular telephony networks like GSM and UMTS the SS7 application MAP is used. Voice connections are Circuit Switched (CS) and data connections are Packet Switched (PS) applications.


Some of the GSM/UMTS Circuit Switched interfaces in the Mobile Switching Center (MSC) transported over SS7 include the following:



  • B -> VLR (uses MAP/B). Most MSCs are associated with a Visitor Location Register (VLR), making the B interface "internal".


  • C -> HLR (uses MAP/C) Messages between MSC to HLR handled by C Interface


  • D -> HLR (uses MAP/D) for attaching to the CS network and location update


  • E -> MSC (uses MAP/E) for inter-MSC handover


  • F -> EIR (uses MAP/F) for equipment identity check


  • H -> SMS-G (uses MAP/H) for Short Message Service (SMS) over CS


  • I -> ME (uses MAP/I) Messages between MSC to ME handled by I Interface


  • J -> SCF (uses MAP/J) Messages between HLR to gsmSCF handled by J Interface



There are also several GSM/UMTS PS interfaces in the Serving GPRS Support Node (SGSN) transported over SS7:



  • Gr -> HLR for attaching to the PS network and location update


  • Gd -> SMS-C for SMS over PS


  • Gs -> MSC for combined CS+PS signaling over PS


  • Ge -> Charging for Customised Applications for Mobile networks Enhanced Logic (CAMEL) prepaid charging


  • Gf -> EIR for equipment identity check


References




  1. ^ ITU-T Recommendation Q.2220, Transport Independent Signalling Connection Control Part (TI-SCCP).








Application layer protocols, Signaling System 7Uncategorized

Popular posts from this blog

Frič See also Navigation menuinternal link

Identify plant with long narrow paired leaves and reddish stems Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is this plant with long sharp leaves? Is it a weed?What is this 3ft high, stalky plant, with mid sized narrow leaves?What is this young shrub with opposite ovate, crenate leaves and reddish stems?What is this plant with large broad serrated leaves?Identify this upright branching weed with long leaves and reddish stemsPlease help me identify this bulbous plant with long, broad leaves and white flowersWhat is this small annual with narrow gray/green leaves and rust colored daisy-type flowers?What is this chilli plant?Does anyone know what type of chilli plant this is?Help identify this plant

fontconfig warning: “/etc/fonts/fonts.conf”, line 100: unknown “element blank” The 2019 Stack Overflow Developer Survey Results Are In“tar: unrecognized option --warning” during 'apt-get install'How to fix Fontconfig errorHow do I figure out which font file is chosen for a system generic font alias?Why are some apt-get-installed fonts being ignored by fc-list, xfontsel, etc?Reload settings in /etc/fonts/conf.dTaking 30 seconds longer to boot after upgrade from jessie to stretchHow to match multiple font names with a single <match> element?Adding a custom font to fontconfigRemoving fonts from fontconfig <match> resultsBroken fonts after upgrading Firefox ESR to latest Firefox