Cisco Cisco Packet Data Gateway (PDG) Manuale Di Manutenzione
New Feature Summary
Generally Available 06-30-2010
1-48
SGSN Features in Release 8.0
This section provides information for new features (listed alphabetically) in Release 8.0 for
the Serving GPRS Support Node (SGSN). Additional information on these features can be
found in the SGSN Overview section of the Product Overview, in the SGSN Administration
Guide, and in the CLI Reference Guide.
the Serving GPRS Support Node (SGSN). Additional information on these features can be
found in the SGSN Overview section of the Product Overview, in the SGSN Administration
Guide, and in the CLI Reference Guide.
Limits / Engineering Rules
The following limits for releases 8.0, 8.1, and 9.0 have been modified in the Engineer Rules
appendix of the SGSN Administration Guide.
appendix of the SGSN Administration Guide.
●
2G Gb over FR Intf: Max NSEs controlling the same RA increased from 16 to 64
●
2G Gb over IP Intf: Max NSEs controlling the same RA increased from 16 to 64
●
Connection Rules:
●
Max # of logically connected GGSNs per Gn/Gp intf increased from 20,000 to “no
limit”
limit”
●
Max # of packets buffered -- rules have been clarified:
- Minimum of 2KB/subscriber.
- Maximum of 10KB/subscriber -- if buffers are available in the shared pool*.
(*SGSN provides a buffer pool of 10M per session manager - buffer to be shared by
all subscribers “belonging” to that session manager.)
- Minimum of 2KB/subscriber.
- Maximum of 10KB/subscriber -- if buffers are available in the shared pool*.
(*SGSN provides a buffer pool of 10M per session manager - buffer to be shared by
all subscribers “belonging” to that session manager.)
●
SIGTRAN: Max number of peer servers per SS7RD increased from 144 to 256.
Correction:
●
Max# of RNCs per 3G intf: corrected from 1024 to 256.
1-in-N IMEI Checks for Subscriber Events
The IMEI check procedure is performed to avoid fraudulent usage of mobile equipment. At
attach, when a subscriber registers with an SGSN, the SGSN retrieves the MS equipment
identity and then sends a “Check_IMEI” request to the EIR.
attach, when a subscriber registers with an SGSN, the SGSN retrieves the MS equipment
identity and then sends a “Check_IMEI” request to the EIR.
The EIR maintains a database of all equipment. The database is organized in three lists –
white, gray, and black lists. The EIR checks the three lists to determine on which list the
MS’ equipment identity belongs. Then the EIR returns the status request back to the SGSN
with the list information.
white, gray, and black lists. The EIR checks the three lists to determine on which list the
MS’ equipment identity belongs. Then the EIR returns the status request back to the SGSN
with the list information.
●
If the equipment status is black-listed, the SGSN does not allow the mobile to register
with the SGSN.
with the SGSN.
●
If the equipment status is white-listed, the SGSN proceeds with the registration.
●
If the equipment status is gray-listed, the default handling is to allow the registration,
which can be overridden via the SGSN CLI.
which can be overridden via the SGSN CLI.
The number of IMEI checks is configured with the
check-imei-every-n-events
keyword
of the
equipment-identity-register
command in the MAP Service configuration mode.
The feature is enabled with the
verify-equipment-identity
keyword of the
gmm
retrieve-equipment-identity imei
command in the SGSN Operator Policy