The GSM / 3GPP compliant MAP Stack from
Aricent
, enables signaling between different network
entities such as HLR, MSC/VLR, SGSN and GGSN. This stack
is built on top of the Transaction Capabilities Application
Part (TCAP) layer, which is the top most layer of the
Signaling System Number 7 (SS7) stack.
MAP
interfaces
MAP
stack design
Aricent’ MAP
Stack: Capabilities
Aricent MAP stack, compliant to latest 3GPP
specifications, has been successfully used by our customers
in their live networks and has successfully inter-operated
against other implementations.
The Aricent MAP Stack provides extensive layer
management features via APIs which:
Initialize stack entity
Provision/unprovision data
Collect/initialize statistics and enable/disable
statistics collection
Log trace messages, enable or disable
tracing, and configure different trace levels
Support error and alarm reporting
The diagram below depicts the MAP interfaces
in a GSM network:
Aricent’ MAP Stack provides individual
packages for specific MAP users, which include:
HLR
SGSN
GGSN
MSC/VLR
GSM SCF
EIR
SWIFS
Combined SGSN, GGSN and MSC
All Packages
Customized packages can also be provided,
if required
Aricent’ MAP stack has a multi-threaded
architecture to take advantage of a multi-processor
environment. This ensures that independent tasks are
performed in different threads. Aricent MAP stack can also
support single-threaded execution, if required. The
stack has wrapper functions for encoding or decoding
which eliminates dependency on an ASN compiler.
Conformance to
Standards
1. 3GPP TS 29.002 version 4.8.0 Release
4., Mobile Application Part (MAP) specification.
