The GSM Mobile Number feature implements mobile number portability for GSM networks and
supports the SRF-based MNP solution as defined in ETSI standards. G-Port allows the subscriber to
retain the MSISDN number when changing subscription networks. The user's IMSI is not portable.
For call-related messages, G-Port acts as a “NP HLR”, in the case where the number has been exported,
by responding to the switch with a MAP SRI ack message. For calls to imported numbers and non-call
related messages, G-Port performs message relay.
The INP (INAP-based Number Portability) feature implements IN-based number portability (using
INAP protocol). It is also used by wireline network operators in accordance with ITU Number
Portability supplements, or by wireless network operators in accordance with ETS I NP standards.
INP provides both query/response and message relay functionality.
The EIR (Equipment Identity Register) feature implements handset security within the GSM network.
It does this by allowing carriers to provision IMEIs (International Mobile Equipment Identity) in the
database and assigning them a list type. List types are Black, Gray, and White. When an IMEI is placed
on the Black list, the carrier is able to prevent the handset from accessing their network. A White listed
IMEI is allowed access to the network, while a Gray may require additional screening but is typically
allowed access to the network.
The Prepaid Short Message Service Intercept (PPSMS) feature uses the G-Port DN portability type
(PT) field to identify prepaid subscribers. These subscribers can be categorized as subscribers that are
ported and subscribers that are not ported. The originated short messages (as part of SMS) of these
subscribers need to be intercepted and forwarded to a corresponding intelligent network platform for
verification. However, the new PT values of the subscribers that are ported in or not ported do not
logically overlap with the existing values. Therefore, the PT values for these subscribers cannot be set
when the DN associated with an SP is removed. In order to minimize changes to the interface, the PT
field is not added to the commands where an IMSI is provided as input. PPSMS is a part of G-Port
that is activated separately.
The V-Flex feature is used to route calls to a specific VMS based on subscription (voice, multimedia)
data provisioned via the EAGLE 5 ISS MMI port and EPAP PDBI . The V-Flex feature utilizes VMS
and GRN Network Entity types. In addition, the Multiple Network Entities per Subscriber feature
introduces the ability to associate DN Blocks and individual DNs with up to 2 NEs. SP and RN remain
mutually exclusive, however any combination of 2 NEs per DN is allowed so long as there is only 1
of each Network Entity type.
The ASD (Additional Subscriber Data) feature enables generic data to be associated with DN and DN
Block subscriber records.
The EPAP Provisioning Blacklist feature helps prevent provisioning of protected E.164 address strings
in the EPAP G-Flex database. Provisioning a protected E.164 address string as a DN, DN Block, or
IMSI may result in unintended and incorrect routing of messages by the EAGLE 5 ISS Service Module
card. The EPAP Provisioning Blacklist feature allows the user to define a list of address strings that
cannot be provisioned as DN, DN Block or IMSI address strings. The E.164 addresses of all HLRs must
be provisioned in the provisioning blacklist.
The TIF Number Substitution feature is used to provision a new DN association for DNs and DN
Blocks. All DN and DN Block records have a subscriber type to identify them as either public or private.
Public DN and DN Block records may substitute to private DN. Likewise, private DN and DN Blocks
may substitute to a public DN. Records are public by default; this default applies to pre-existing records
and new records for which subscriber type is not explicitly defined.
The IDP A-Party Blacklist feature provides subscriber blacklisting capability on the Calling Party
(A-Party or CgPN) number in the IDP CAMEL message. The blacklisting function is achieved using
either a query-based mode, or a relay-based mode in conjunction with IDP Relay feature processing.
19
910-6022-001 Revision A, March 2011
Functional DescriptionProvisioning Database Interface Manual
To Next Page
Loading...
