SGSN Changes in Release 14.0

This chapter identifies features and functionality added to, modified for, or deprecated from 14.0 SGSN software releases.

Topics covered in this chapter are:

IMPORTANT:

Enhancements to Diameter, GTPP, and RADIUS in release 14.0 are located in the Accounting Management Changes chapter.

Enhancements to SNMP MIB in release 14.0 are located in the SNMP MIB Changes chapter.

Enhancements to Web Element Manager (WEM) in release 14.0 are located in the Web Element Manager Changes chapter.

Omissions and Corrections

The following list links to (1) content that was omitted from previous versions of this document or to (2) content that was in error in previous versions of this document.

Omissions from and Corrections to November 7, 2012 Content
Omissions from and Corrections to June 29, 2012 Content

SGSN Feature Changes as of May 31, 2013

This section provides information on SGSN feature changes in release 14.0.

IMPORTANT:

For more information regarding features in this section, refer to the SGSN Administration Guide for this release.

New SGSN Features

This section identifies new SGSN features available in release 14.0.

Downlink Data Lockout Timer

Currently, if paging fails after maximum number of retries, the page proceed flag (PPF) is cleared and further downlink data is dropped. The PPF is set to ‘true’ if there is any uplink activity from the UE.

The Downlink Data Lockout Timer is a new, configurable timer added for both GPRS and SGSN services to reduce the frequency of mobile-initiated keep alive messages. If enabled, this timer starts whenever the paging procedure fails after the maximum number of retransmissions and the Page Proceed Flag (PPF) is cleared. If there is any downlink activity when the lockout timer is running, the packets are dropped and the drop cause is set as Page Failed. When the lockout timer expires, the PPF is set to true and further downlink packets are queued and paging is re-initiated. In order to avoid endless paging activity when there is no page response or uplink activity from the UE, an optional configurable repeat count value is used. If the repeat value is configured as 'y' then the lockout timer is started 'y' number of times after page failure. The implementation of the lockout timer is different for 2G/3G subscribers, but the behavior is the same.

E-UTRAN Service Handover Support

The SGSN supports configuration-based enabling of the E-UTRAN Service Handover Information Element, which is optional in the following RANAP messages used during SRNS relocation:

  • RAB Assignment Request
  • Relocation Request

This feature is useful in the following scenarios:

  1. A UE is E-UTRAN capable, the PLMN is E-UTRAN capable, but the UE has not subscribed to EPS services (no 4G subscription available).
  2. The VPLMN is E-UTRAN-capable, and the UE of an inbound roamer is E-UTRAN capable, but the UE has only a UTRAN/GERAN roaming agreement in place.

The feature ensures that an SRNS relocation handover to E-UTRAN is not allowed for E-UTRAN capable UEs that have only a UTRAN/GERAN roaming agreement. This results in an elimination of potential service denial or disruption issues, and unnecessary signaling.

To implement this feature, new CLI commands have been implemented so that the SGSN can be configured to:

  • Override the "eutran-not-allowed" flag received from the HLR/HSS in the ISD/ULA request for the Access Restriction Data (ARD) parameter (for scenario #2 above).
  • Enable the inclusion of the E-UTRAN Service Handover IE in RAB Assignment Request and Relocation Request RANAP messages (for scenarios #1 and #2 above).

IMPORTANT:

SRNS relocation must be configured via the srns-inter and/or srns-intra commands in Call Control Profile Configuration Mode before configuring E-UTRAN Service Handover Support.

Gb Manager

A new SGSN proclet has been developed. Now, all the link level procedures related to Gb -

  • protocol (GPRS-NS and BSSGP) hosting, handling, administration, message distribution,
  • keeping the other managers informed about the link/remote-node status,
  • handling functionality of the Gb interface (all 2G signaling)
are removed from the Link Manager and moved to the SGSN's new Gb Manager proclet.

The new Gb Manager provides increased flexibility in handling link level procedures for each access type independently and ensures scalability. The consequence of relieving the Link Manager, of a large amount of message handling, is to decrease delays in sending sscop STAT messages resulting in the detection of link failure at the remote end. Use of this separate new proclet to handle 2G signaling messages means there will not be any MTP link fluctuation towards the RNS, which is seen during the BSC restart or extension activity in the network. As well, this improves the fluctuation towards the 3G connectivity.

Modified SGSN Features

This section identifies SGSN features modified in release 14.0.

Check For UEs From MME

Previous Behavior: For UEs coming from MME (MSB of LAC is 1), the SGSN fails to send a RAU reject and update the Session Disconnect Reasons, Statistics respectively.

New Behavior: The SGSN behavior has now been modified to send a RAU reject and update the Session Disconnect Reasons , Statistics respectively. If egtpc is associated in gprs-service, the following checks for S4-SGSN have been added:

  • In pure S4 conditions, the MSB set in the LAC bit specifies if the UE is coming from MME.
  • In S4/Gn mixed conditions, the guti db configuration is used to determine if the UE is coming from MME as Gn SGSNs can have MSB set in LAC.

Clear Port Output Updated

Previous Behavior: Executing the command clear port datalink counter all does not clear the DLCI level statistics, only port level statistics are cleared.

New Behavior: Executing the command clear port datalink counter all now clears both DLCI level statistics and port level statistics.

Custom10, Custom11 Dictionaries Value Of Fields Changed

Previous Behavior: In custom10 and custom11 dictionaries, if the value of the fields rNCUnsentDownlinkVolume/dataVolumeGPRSUplink/dataVolumeGPRSDownlink is greater than 0x7fffffff, then an additional byte (00)is added to make it five bytes.

New Behavior: In custom10 and custom11 dictionaries, if the value of the fields rNCUnsentDownlinkVolume/dataVolumeGPRSUplink/dataVolumeGPRSDownlink is greater than 0x7fffffff, an additional byte (00) is not encoded at the beginning of the byte. This implies that the values of the three fields will not go beyond four bytes.

Default Value Of “sctp-max-out-strms”

Previous Behavior: If the value of "sctp-max-out-strms" is configured to less than "2", the configured value is set to "sctp-max-out-strms" and a crash occurs.

New Behavior: The default value of "sctp-max-out-strms" is set to "2". If the user tries to configure the value of "sctp-max-out-strms" less than "2", a message is displayed and the default value of "2" is set for "sctp-max-out-strms".

Extra Signalling To GGSN And MS

Previous Behavior: During a RNC initiated modification procedure if the GGSN downgrades QoS and while updating the RNC with RAB modify request if a RAB modify failure is received the GGSN and MS are not updated with the old QoS information (QoS before the GGSN downgraded the QoS).

New Behavior: During a RNC initiated modification procedure if the GGSN downgrades QoS and while updating the RNC with RAB modify request if a RAB modify failure is received the GGSN and MS are now updated with the old QoS information (QoS before the GGSN downgraded the QoS).

Impact

Two extra messages will be seen in this scenario one on Gn interface (Update PDP) and one on the Iu interface (modify PDP).

GGSN-initiated UPCQ

Previous Behavior: The SGSN receives an UPCQ from GGSN when activation is in progress and always sends an update PDP context response "no resources available" cause code.

New Behavior: In case of non-direct tunnel subscribers where the RNC does not downgrade the QoS during activation, the GGSN initiated UPCQ is processed by SGSN.

Gmm Reject Causes “11 - 15” Re-direct Indication

Previous Behavior: For network-sharing cases of reject due to HLR, the SGSN sends re-direct complete even if gmm reject causes are between 11-15.

New Behavior: When gmm reject causes are between 11-15, the re-direct indication is sent.

IMEI Time Out Cause Feild Changed

Previous Behavior: The cause field in RAU reject for IMEI time out is "Network Failure".

New Behavior: The cause field in RAU reject for IMEI time out is now changed to "Implicit Detach".

InTracer Invoke In 2G Is Disabled

Previous Behavior: InTracer is invoked for both 2G and 3G calls.

New Behavior: InTracer support is invoked only for 3G calls. InTracer support is not invoked for 2G calls and unknown subscribers (for example, unrecognized Transaction ID in case of TCAP continue message).

Impact

Customers network is not flooded with the 2G call events to InTracer (IPMS).

License Control for Prefer Subscription-Interface

Previous Behavior: Previously, the prefer command, in the Call Control Profile configuration mode, was controlled by the basic SGSN license.

New Behavior: Use of the prefer command is now controlled by the feature-specific S6d license. Without the S6d license, the command appears but is non-functional. The current subscription-interface keyword only appears if the operator has an S6d license.

LinkMgr Uses Dedicated DMA with NPU

Previous Behavior: The LinkMgr communicated over default direct memory access (DMA) channel to the NPU.

New Behavior: The internal interface between the LinkMgr and the NPU has changed. The LinkMgr now communicates over a dedicated DMA channel with the NPU.

Customer Impact: Marginally improves session setup time for higher attach and detach rates.

MME-FQDN For Peer MME

Previous Behavior: In DNS, RAI-FQDN is performed if the peer is MME.

New Behavior: In DNS, MME-FQDN will be performed if the peer is MME.

MO SMS CDR Generation

Previous Behavior: CDRs are generated when MO SMSes are dropped due to routing failure.

New Behavior: CDRs are not generated when MO SMSes are dropped due to routing failure.

PGW PLMN-Id in EPS Subscription Information

Previous Behavior: PGW PLMN-Id field is not displayed in EPS subscription information when the command show subscribers gprs-only full all is executed.

New Behavior: PGW PLMN-Id is now included in eps subscription information display.

S4-SGSN DP Structure Memory Usage Statistics

Previous Behavior: No statistics are available to track S4-SGSN data path related data structure memory usage.

New Behavior: New statistics are added to the show CLI command show sgsn sessmgr instance < > memory statistics to display S4-SGSN data path structure memory usage statistics.

S4-SGSN Support For SRNS

Previous Behavior: The S4-SGSN supports peer SGSN/MME configuration only for RAUs.

New Behavior: The S4-SGSN now supports peer SGSN/MME configuration for RAUs and SRNS.

Severity Level For “starSGSNRMMemWarn”

Previous Behavior: The old "starent.my" file incorrectly displays the SEVERITY level as "INFORMATIONAL" for "starSGSNRMMemWarn" (trap code 1217).

New Behavior: The new "starent.my" file now correctly displays the SEVERITY level as "WARNING" for "starSGSNRMMemWarn" (trap code 1217).

Impact: The correct SEVERITY level for "starSGSNRMMemWarn" trap is now displayed.

SGSN Context Transfer From MME

Previous Behavior: In certain scenarios, post LTE to 2G RAU, several RAUs from UE do not receive response from SGSN. The SGSN does not perform a context transfer from MME.

New Behavior: The SGSN now performs a context transfer from MME.

SGTP-Service Cannot Be Shared Between MME and SGSN

Previous Behavior: There was no note in the documentation to indicate an association limit for the SGTP service in regard to co-located services.

New Behavior: The following is the note that has been added to the documentation for SGSN and GPRS service configuration to limit association of SGTP services: “When using the associate command in GPRS Service configuration mode or SGSN Service configuration mode, only one SGTP service can be associated with a single service definition. If co-located, the GPRS and SGSN services can share the same SGTP service association or they can have different SGTP services associated. When an SGSN and an MME are co-located, the GPRS or SGSN service cannot be associated with the same SGTP service that is used by the MME.

Show Output Updated To Include “SGSN change” Attribute

Previous Behavior: The SGSN-Change present attribute was included in S-CDRs for Custom33 Dictionary. This attribute is not displayed on execution of the command show gtpp group name default .

New Behavior: The missing attribute SGSN-Change present is now included in the show output show gtpp group name default .

Show Output “show port npu counter” Updated

Previous Behavior: The show output show port npu counter < > displays the individual VPI/VCI instead of summing up all VPI/VCI.

New Behavior: The show output show port npu counter < > now displays the summed entities of all VPI/VCI present on the port. The show output show port npu counter < > vpi < > vci < > now displays the statistics of that particular VPI/VCI.

State And Severity Fields On SDH Traps

Previous Behavior: Incorrect STATE and SEVERITY fields for some SDH traps in "starent.my" file present in the system.

New Behavior: The incorrect STATE and SEVERITY fields of SDH traps in "starent.my" file have been corrected.

Impact: The correct STATE and SEVERITY fields for SDH traps in "starent.my" file can be viewed on the system.

Support For APN-OI-REPLACEMENT At GPRS UE Level And GPRS PDP Level

Previous Behavior: Support for APN-OI-REPLACEMENT is not present at GPRS UE level and GPRS PDP level.

New Behavior: Support for APN-OI-REPLACEMENT is added at GPRS UE level and GPRS PDP level.

Impact: APN-OI-REPLACEMENT at GPRS UE and PDP level is available for use.

System_Type Attribute For Custom42 Dictionary

Previous Behavior: The values of the attribute “System_Type” in custom42 dictionary are as follows:

  • 01 = S-CDRs
  • 02 = SGW-CDRs

New Behavior: The values of the attribute “System_Type” for custom42 dictionary are modified as follows:

  • System_Type= 1 for 2G S-CDRs
  • System_Type= 2 for 3G S-CDRs
  • System_Type= 2 for 4G SGW- CDRs

Impact

Custom42 S-CDR has new values for the attribute System_Type.

SGSN Command Changes as of May 31, 2013

This section provides information on SGSN command changes in release 14.0.

IMPORTANT:

For more information regarding commands in this section, refer to the Command Line Interface Reference for this release.

New SGSN Commands

This section identifies new SGSN commands available in release 14.0.

None for this release.

Modified SGSN Commands

This section identifies SGSN commands modified in release 14.0.

access-restriction-data

The eutran-not-allowed keyword has been added to the access-restriction-data command in Call Control Profile Configuration Mode. Enabling this parameter allows the SGSN to override the eutran-not-allowed flag received in ISD/ULA messages from the HLR/HSS. Configuration of the eutran-not-allowed parameter is valid only if SRNS relocation first has been configured in Call Control Profile Configuration Mode via the srns-inter and/or srns-intra commands.

config
   call-control-profile cc_profile_name
      access-restriction-data
eutran-not-allowed
      remove
access-restriction-data eutran-not-allowed 
      end
  • eutran-not-allowed overrides the eutran-not-allowed flag received in ISD/ULA messages from the HLR/HSS received during the Attach process. The overridden value will be sent to the RNC during PDP context activation (in the RAB Assignment Request message) so that the RNC subsequently avoids handing over to E-UTRAN.
  • Once created, the call-control-profile must then be associated with an operator policy in Operator Policy Configuration Mode using the associate command.
  • Once the operator policy is associated with the call-control-profile, inclusion of the E-UTRAN Service Handover Information Element in RAB Assignment Request and Relocation Request RANAP messages must be enabled. This is done by executing the ranap eutran-service-handover-ie command in RNC Configuration Mode.

aggregate-ipc-msg

Flushing limits the number of messenger calls between managers to transfer the received packets. The new gbmgr keyword, representing the Gb Manager, enables the operator to configure the threshold limit for flushing IPC messages, to the Session Manager, that have been aggregated at the Gb Manager. The flushing limit will be based on either desired flush-frequency or maximum number of messages to be aggregated. Repeat the command to engage both limits.

config
   sgsn-global
      aggregate-ipc-msg { gbmgr } { flush-frequency time | numb-msgs
 number_msgs
      default
aggregate-ipc-msg { gbmgr} 
      end

Where:

  • gbmgr identifies the Gb Manager as the for which flushing limitations are configured.
  • flush-frequency sets the frequency of message flushes in units of 100 msecs, with a valid range of 1 to 3; default is 1.
  • num-msgs sets the maximum number of IPC messages to be aggregated before flushing, with a valid range of 1 to 164; default is 10.
  • default resets both frequency and aggregation limits to default values.

IMPORTANT:

Setting num-msgs to a value of 1 will disable message packet aggregation.

gmm paging-failure-action

A new gmm command enables and configures the downlink data lockout timer (for both GPRS and SGSN services) to reduce the frequency of mobile-initiated keep alive messages. The following enables the timer for 3G subscribers:

config
   context <context_name>
      sgsn-service  <sgsn_service_name>
         gmm
paging-failure-action downlink-data-lockout-timer seconds [ repeat number_repeats ]
         default
gmm paging-failure-action downlink-data-lockout-timer 
         [ default | no ] gmm
paging-failure-action  
         end
Where:
  • Replacing sgsn-service sgsn_service_name with gprs-service gprs_service_name enables the timer for 2G subscribers.
  • seconds sets timer expiry for 0 to 10000 seconds; default is 1000.
  • number_repeats sets the number of times (1 to 10) that the timer restarts after page failure.
  • default resets the timer default value.
  • [ default | no ] gmm paging-failure-action disables the downlink data lockout timer.

IMPORTANT:

If repeat is not configured, then paging proceeds endlessly until the maximum repeat (MR) timer expires.

peer-mme

The tac keyword has been added to the peer-mme command to allow for local configuration of the Tracking Area Code (TAC) of the target eNodeB that maps to the peer MME address. The TAC is used by the S4-SGSN for UTRAN to E-UTRAN (SGSN to MME) SRNS relocation across the S3 interface. Configuration of the tac is optional, and valid only if SRNS relocation first has been configured in Call Control Profile Configuration Mode via the srns-inter and/or srns-intra commands. The tac can be configured as part of the local peer MME address used to bypass DNS resolution during SRNS relocation, or as part of a fallback peer-mme address that the system will use if DNS fails.

config
   call-control-profile name
      peer-mme
tac tac prefer local address
ipv4 ipv4-address interface s3
      peer-mme
tac tac prefer fallback-for-dns
address ipv4-address interface s3
      remove
peer-mme tac tac address ipv4-address interface s3
      end

Where:

  • tac is the Tracking Area Code of the target eNodeB that maps to the address of the peer MME being configured. Valid entries are 1 to 65535.

ranap eutran-service-handover-ie

The eutran-service-handover-ie keyword has been added to the ranap command in RNC Configuration Mode. Enabling this parameter results in the inclusion of the E-UTRAN Service Handover Information Element in RAB Assignment Request messages (during the PDP activation phase) and Relocation Request RANAP messages (during the SRNS relocation phase). The IE in the RAB Assignment Request during the PDP activation phase informs the RNC not to handover the subscriber to E-UTRAN. The IE in the Relocation Request message is sent when there is an intra-or inter-SGSN SRNS relocation within the UTRAN itself so that the target RNC knows that it shall not handover the subscriber to E-UTRAN. Configuration of the eutran-not-allowed parameter is valid only if SRNS relocation first has been configured in Call Control Profile Configuration Mode via the srns-inter and/or srns-intra commands.

config
   context context_name
      iups-service iups-service_name
         rnc
id rnc_id
            ranap
eutran-service-handover-ie            no
ranap eutran-service-handover-ie

Where:

  • eutran-service-handover-ie enables the inclusion of the E-UTRAN Service Handover IE in the RAB Assignment Request and Relocation Request RANAP messages.
  • no ranap eutran-service-handover-ie specifies that the SGSN will never include the E-UTRAN Service Handover IE in RAB Assignment Request and Relocation Request RANAP messages.

sgsn-address

The rnc_id keyword has been added to the sgsn-address command to allow for the local configuration of the target RNC ID that maps to the address of the peer SGSN via the S16 interface. The RNC ID is used by the S4-SGSN for inter-SGSN SRNS relocation. Configuration of the rnc_id is optional, and valid only if SRNS relocation first has been configured in Call Control Profile Configuration Mode using the srns-inter and/or srns-intra commands. The rnc_id can configured to as part of the local peer SGSN address used to bypass DNS resolution during SRNS relocation, or as part of a fallback peer SGSN address that the system will use if DNS fails.

config
   call-control-profile cc_profile_name
      sgsn-address
rnc_id rnc_id prefer local address
ipv4 ip-address interface s16
      sgsn-address
rnc_id rnc_id prefer fallback-for-dns
ipv4 ipv4-address interface s16
      no
sgsn-address ipv4 ip-address rnc_id rnc_id interface s16

Where:

  • rnc_id is the target RNC ID that maps to the address of the peer SGSN being configured. Valid entries are 0 to 65535.

snmp mib

The system-level Global Configuration mode snmp command has been modified to include a new keyword - mib. The mib keyword allows an operator to selectively enable other industry standard and Cisco Management Information Bases (MIBs) supported by the system. By default, only the STARENT-MIB is enabled. You can display a list of available MIBs by running the show snmp server command.

config
   [ no ] snmp
mib mib_name
   end

IMPORTANT:

This command is not yet qualified.

Deprecated SGSN Configuration Commands

This section identifies deprecated SGSN commands that are no longer supported in release 14.0.

None for this release.

SGSN Performance Indicator Changes as of May 31, 2013

This section provides information on SGSN performance indicator changes in release 14.0.

IMPORTANT:

For more information regarding bulk statistics and output fields and counters in this section, refer to the Statistics and Counters Reference for this release.

New SGSN Bulk Statistics

This section identifies new SGSN bulk statistics available in release 14.0.

The following bulk statistics are new in this release:

System Schema

  • disc-reason-535 (sgsn-dsd-allepswithdrawn) - This disconnect reasons is for future use.

Modified SGSN Bulk Statistics

This section identifies SGSN bulk statistics modified in release 14.0.

None for this release.

Deprecated SGSN Bulk Statistics

This section identifies deprecated SGSN bulk statistics that are no longer supported in release 14.0.

None for this release.

New SGSN Output Fields and Counters

This section identifies new SGSN show command output fields and counters available in release 14.0.

show call-control-profile full

A new field has been added to the command output to indicate if the system is configured to override the eutran-not-allowed flag received in ISD/ULA messages received from the HLR/HSS.

In the ARD output section, when eutran-not-allowed is enabled:

  • Access Restriction Data            : EUTRAN Not Allowed

In the ARD output section, when eutran-not-allowed is disabled:

  • Access Restriction Data            :EUTRAN Allowed

show call-control-profile full

Two fields have been added to the output of this command to display the configured TAC (for the peer sgsn-address) and/or RNC ID for the peer sgsn-address), if configured.

In the SGSN Address output section:

  • RNCid rnc_id

In the PEER MME output section:

  • tac tac

show egtpc statistics verbose

Retransmission statistics have been added for Suspend Notification and Resume Notification in the CS Fallback Messages section of the command output.

One counter has been added to track the total number of CSFB (Circuit Switched Fallback) - initially transmitted suspend notification messages that had to be retransmitted by the system, the specified service, or the specified interface:

  • Retrans TX

One counter has been added to track the total number of CSFB - initially transmitted resume notification messages that had to be retransmitted by the system, the specified service, or the specified interface:

  • Retrans TX

show gmm-sm statistics verbose

New counters have been added to to validate the number of times the lockout timer starts/stops/expires for both 2G and 3G subscribers. All new counters are organized under the Timers heading.

  • Total-Lockout-timer-Start:
  • 3G-Lockout-timer-Start:
  • 2G-Lockout-timer-Start:
  • Total-Lockout-timer-Stop:
  • 3G-Lockout-timer-Stop
  • 2G-Lockout-timer-Stop:
  • Total-Lockout-timer-Expiry:
  • 3G-Lockout-timer-Expiry:
  • 2G-Lockout-timer-Expiry:

show gprsns statistics msg-stats nse nsei

The format of the output related to the BSC Lock statistics is modified under the “Number of pdu dropped due to locked nse” heading to separately display the number of packets dropped in both uplink and downlink directions. The modified subheading and field titles are listed below:

  • dropped in uplink direction
    • ns-pdu dropped
  • dropped in downlink direction
    • ns-unitdata pdu dropped

show gtpp group name default

The attribute SGSN-Change present included in the show output.

  • SGSN- Change present

show iups-service all

The output of this command has been enhanced to indicate if the system is configured to include the E-UTRAN Service Handover IE in RAB Assignment Request and Relocation Request RANAP messages.

When the system is configured to include the E-UTRAN Service Handover IE:

  • EUTRAN Service Handover            : IE included in message

When the system is not configured to include the E-UTRAN Service Handover IE:

  • EUTRAN Service Handover            : IE Not included in message

show session disconnect-reason verbose

The following disconnect reason is for future use even though it is visible:

  • sgsn-dsd-allepswithdrawn(535)

show session subsystem facility aaamgr instance <number>

New field added to display number of GPRS UE level records.

  • Total GPRS records

show subscribers gprs-only full all

PGW PLMN-Id is included as a part of EPS subscription information.

  • PGW PLMN-Id

New field added to the CLI display of show subscribers gprs-only full all to display GPRS UE and PDP level APN-OI-REPLACEMENT.

  • APN OI Replacement

show subscribers sgsn-only full all

New field added to the CLI display of show subscribers sgsn-only full all to display GPRS UE and PDP level APN-OI-REPLACEMENT.

  • APN OI Replacement

show sgsn sessmgr instance instance_no memory statistics

Three statistics have been added to provide S4-SGSN data path structure memory usage statistics. The new statistics appear in the SGSN-specific Memory Statistics section of the command output:

  • S4 DP | S4 DP Sess
  • S4 DP | S4-Gn Data Fwd
  • S4 DP | S4 IDFT Sess

show subscribers sgsn-only full

A new field has been added to the output of this command to indicate if the system is configured to override the eutran-not-allowed flag received in ISD/ULA messages from the HLR/HSS.

When the systen is configured to override the eutran-not-allowed flag:

  • Eutran-not-allowed       :True

When the systen is not configured to override the eutran-not-allowed flag:

  • Eutran-not-allowed       : False

Modified SGSN Output Fields and Counters

This section identifies modified SGSN show command output fields and counters available in release 14.0.

show session subsystem facility aaamgr instance <number>

The field “Total PDP records” is modified as “Total GPRS PDP records”

  • Total GPRS PDP records

Deprecated SGSN Output Fields and Counters

This section identifies deprecated SGSN output fields and counters that are no longer supported in release 14.0.

None for this release.

SGSN Feature Changes as of January 31, 2013

This section provides information on SGSN feature changes in release 14.0.

IMPORTANT:

For more information regarding features in this section, refer to the ASR 5000 Serving GPRS Support Node Administration Guide for this release.

New SGSN Features

This section identifies SGSN features new in release 14.0.

Custom S-CDR Dictionary

The SGSN supports a new custom42 S-CDR dictionary. For detailed information, refer to the Cisco ASR 5x00 GTPP Interface Administration and Reference.

Dual PDP Parameter Support for Custom SGSN S-CDR Dictionaries

All custom S-CDR dictionaries support the CDR Field "Served PDP/ PDN Address extension". This field holds the IPv4 address of the subscriber (if available) when the PDP type is IPv4v6. The inclusion of this field in the S-CDR dictionary is enabled on execution of the command gtpp attribute served-pdp-pdn-address-extension in the GTPP Server Group Configuration Mode. This field is disabled by default and is not supported by the following dictionaries:

  • custom17
  • custom18
  • custom23
  • custom42
  • custom41

IMPORTANT:

This field was supported previously only on custom24 dictionary.

Gn Handoff from S4-SGSN to 2G/3G Gn SGSN

Support is now available for handoffs from the S4-SGSN to a 2G/3G peer SGSN as follows:

  1. An EPC capable UE is attached to an S4-SGSN and has PDP contexts towards the EPC core using the S4 interface.
  2. When the UE hands off to a Gn/Gp SGSN, the S4-SGSN transfers the PDP contexts to the peer SGSN using the GTPv1 protocol.

Handling SMC’s GE Switch with Bad MMU

When the software detects a catastrophic error with an internal control plane switch located on the SMC card, the system will put the failed SMC in offline state. The card with a control plane switch failure should be replaced.

The following is the log message indicating a control plane failure:

“The System Management Card with serial number <serial_number> in slot <slot_number> has failed and will be reset and kept down. (Device=SMC_GE_BCM5695, Reason=CONTROL_PLANE_MMU_FAILURE, Status=[CPU0 MB: LINUX_RC: Done HB: xx] [CPU1 HB: xx] [CPU2] [CPU3])"

Preventing QoS Re-Negotiation Failures

When there is a change in QoS due to Inter-RAT handover from 2G to 3G OR Inter-SGSN handover with no RAB establishment, the SGSN first informs the MS of new QoS through “Modify PDP context request” and then sets up a RAB. With new CLI control provided at the SGSN Service Configuration Mode, the SGSN can first set up a RAB and then proceed with a UPCQ towards GGSN / Modify towards UE based on whether or not RNC downgrades the QoS.

TheA new command implements this feature is documented in the New SGSN Configuration Commands section.

Modified SGSN Features

This section identifies SGSN features modified in release 14.0.

Authentication When Hostname Used

Previous Behavior: Hostname in authorized-key configuration was not checked in previous Release 12.0 code when using key-based authentication. Later, the procedure was changed to check the hostname against the client IPv4 address.

New Behavior: Hostname in the authorized-key configuration will be checked against the client IPv4 address when it is configured as the IPv4 address in the key-based authentication. Currently, the hostname associated with a non-IPv4 address in the authorized-key configuration will not be checked and will be treated in the previous manner and passed.

Bulk Stats for 3G Activation Failure/Reject with Cause Codes

Previous Behavior: The existing SGSN counters do not support segregation of internal and external triggers that lead to 3G Activation Failure/Reject with following cause codes:

  • 3G-actv-rej-network-failure
  • 3G-actv-rej-svc-opt-tmp-out-of-order
  • 3G-actv-rej-unspecified-error
  • 3G-sec-actv-rej-unspecified-error
  • 3G-actv-rej-insufficient-resources
  • 3G-sec-actv-rej-insufficient-resources

New Behavior: New counters are added to indicate internal and external triggers that lead to 3G Activation Failure/Reject with cause codes. With the new counters, the operator has the flexibility to choose either internal or external triggers to compute KPIs.

The new counters are listed in the New SGSN Bulk Statistics section.

Bulk Stats for Iu Release before 3G Attach

Previous Behavior: Several reasons (triggers) can be attributed in the SGSN for an Iu being released before a 3G Attach. Previously, there was no break up in the SGSN code to separately indicate internal and external triggers that lead to Iu being released before Attach in 3G.

New Behavior: New bulk statistics have been added to the SGSN schema to support the segregation of internal and external triggers for Iu being released when it occurs prior to a 3G Attach. With the new counters, the operator has the flexibility to choose either internal or external triggers to compute KPIs.

The new counters are listed in the New SGSN Bulk Statistics section.

IMPORTANT:

Currently, there are no internal failure triggers for the Iu release before Attach, "3G-attach-fail-iu_release-internal" and "3G-attach-fail-iu_release-comb-internal" are place holders for future enhancements in the bulk statistics.

Bulk Stats Track 2G or 3G Attach Rej with Network Failure Cause Codes

Previous Behavior: Prior to this release, the SGSN counters did not support segregation of internal and external triggers that lead to 2G/3G Attach Reject with a “Network Failure” cause code.

New Behavior: With this release, new bulk statistics are added to the SGSN schema to indicate both internal and external triggers that lead to 2G/3GAttach Reject with a “Network Failure” cause code. With the new counters, the operator has the flexibility to choose either internal or external triggers to compute KPIs.

IMPORTANT:

Currently, the internal failure triggers for 2G Attach Reject with “Network Failure” cause code are not available.

The new counters are listed in the New SGSN Bulk Statistics section.

Bulk Stats for 2G Simple and Combined Attach Failures

Previous Behavior: The SGSN code does not provide counters or bulk statistics that support segregation of internal and external triggers for 2G Attach Failures. In the CLI output the following counters account only for internal triggers (Internal Errors) for 2G Attach Failures:

  • 2G-Attach-Failure
  • Gprs-Attach-Failure
  • Comb-Attach-Failure

The following bulk statistics account only for internal triggers (Internal Errors) in 2G Attach Failures:

  • 2G-total-attach-fail
  • 2G-total-attach-fail-comb
  • 2G-total-attach-fail-all

New Behavior: The SGSN's behavior regarding the above counters has been changed. The SGSN code now supports segregation of internal and external triggers (errors) for 2G Attach Failures. As well, new bulk statistics have been added to the SGSN schema. The new counters are listed in the New SGSN Bulk Statistics section.

Impact on Customer: The values of the above mentioned counters increase due to the change in behavior. A drop in the counter “2G-attach success rate” is observed if the same counters are used for calculating KPIs.

Cause Value Corrected

Previous Behavior: When the SGSN receives a BSSGP UL data packet with signaling BVCI (bvci = 0) it sends a status message with cause value "process overload".

New Behavior: When the SGSN receives a BSSGP UL data packet with signaling BVCI (bvci = 0) it sends a status message with correct cause value "protocol error, unspecified", per 3GPP TS 40.018 (section 5.4.1).

Change in Text Displayed While Configuring Point Code

Previous Behavior: On configuring a value higher than one in the valid range for self point code, the following text was displayed:

[local]bngnc3(config-ss7-rd-3-ps-id-1)# self-point-code 16384
itu point-code out
of range, valid range is 0 to 16383

New Behavior: The text displayed, when entering a value higher than valid range for self point code, has been modified for several variants to read:

Failure: ITU point-code
out of range, valid range is 0 to 16383
Failure: ANSI/CHINA
point-code out of range, valid range is 0 to 16777215
Failure: ITU point-code
out of range, valid range is 0.0.0 to 7.255.7
Failure: point-code
value out of range

Changes to IPv4v6 PDP-Type Fallback Statistics

Previous Behavior: The requested PDN-Type of IPv4v6 is NOT overridden in Create-Session-Request with the subscribed PDN-Type of IPv4 or IPv6 for the following scenario where:

  • the PDN-Type received in an Activate-PDP-Ctx-Req is IPv4v6 and
  • the APN is not sent by the MS and
  • the PDN-Type in the Subscription is IPv4 or IPv6.

As there was no fallback of IPv4v6 PDN-type done in this scenario, the corresponding counters under GMM-SM stats were not incremented.

New Behavior: Behavior is changed to override the requested IPv4v6 PDN-Type in Create-Session-Request with the subscribed type (IPv4 or IPv6) and the corresponding counters under GMM-SM stats are incremented for this scenario also.

The following show gmm-sm statistics counters are now incremented for the above mentioned scenario.

  • 2G IPv4v6 PDP Type Fallback Statistics
  • IPv4 due to subscription:
  • IPv6 due to subscription:
  • 3G IPv4v6 PDP Type Fallback Statistics
  • IPv4 due to subscription:
  • IPv6 due to subscription:

Ext-PDP-Address and Type Displayed upon Validation of Ext-PDP-Type

Previous Behavior: The Ext-PDP-Address and Ext-PDP-Address type were displayed without checking for Ext-PDP-Type.

New Behavior: The software has been modified so that the Ext-PDP-Address and Ext-PDP-Address type are displayed only if Ext-PDP-Type is “ipv4v6”.

Handling EGTP Context Response for 2G Old-ISRAU

Previous Behavior:

If :

  • the subscriber wasUMTS_Enabled,
  • the ME was UMTS_AKA enabled,
  • the subscriber was attached to a 2G (old_NW),

And if

  • the Old_SGSN received EGTP_Req (Identification / Context),

then the SGSN should have sent "UMTS Key, Used Cipher and Quintuplets" type MM_CTXT to the Peer (per 29.274, 8.38).

And if

  • the subscriber was UMTS and
  • the ME was NO_UMTS_AKA enabled,

then the SGSN should have sent the peer "GSM Key, Used Cipher and Quintuplets" type MM_CTXT as the EGTP response.

However,

  • instead of sending "GSM Key, Used Cipher and Quintuplets (2)", the SGSN was sending "UMTS Key and Quintuplets (3)" type MM_CTXT, and
  • in place of sending "UMTS Key and Quintuplets (3)”, the SGSN was sending "UMTS Key, Used Cipher and Quintuplets(1)".

And if the subscriber was UMTS, the ME was UMTS_AKA, then the SGSN was responding to EGTP Req with MM_CTXT type as UMTS Key and Quintuplets (1)

New Behavior:

  • If the subscriber is UMTS and the ME is UMTS_AKA, then the SGSN will respond to EGTP Req with MM_CTXT type as UMTS Key, Used Cipher and Quintuplets (1)
  • If the subscriber is UMTS and the ME is NO_UMTS_AKA, then the SGSN will send GSM Key, Used Cipher and Quintuplets (2).

Handling of Delete Bearer Request during Inter-SGSN Handoff / new-SGSN

Previous Behavior: Delete Bearer Request during Inter-SGSN hand-off, Cisco SGSN was the new-SGSN, was being queued and was processed once hand-off procedure was completed.

New Behavior: Delete Bearer Request during Inter-SGSN hand-off, Cisco SGSN is the new-SGSN, will be rejected with cause 110 (Temporarily rejected due to handover procedure in progress).

Impact on Customer: Increase in Delete Bearer Response with cause 110.

Handling of Re-transmitted Secondary PDP Context Request Messages

Previous Behavior: In 2G scenarios, the SGSN clears the original call to receive re-transmitted Activate PDP context request message. The SGSN incorrectly treats the re-transmitted request as a new activate request with some parameters same as the original activation request.

New Behavior: If the new activate PDP request is same as the on-going activation request it indicates that the new request is a re-transmitted request, the SGSN drops such re-transmitted activation requests and continues with the on-going activation request.

Identification Request Not Initiated by SGSN

Previous Behavior: The SGSN initiates an Identification / CTXT request to a Peer MME even if the MS has not provided the PTMSI_SIG in Attach request / RAU PDU. The MME is unable to create a GUTTI without the PTMSI_SIG. The request is rejected and GMM Id request or RAU Reject is sent to the MS.

New Behavior: As per 3GPP TS 29.274 v9, now the SGSN will not initiate an Identification / CTXT request but, it directly initiates a GMM Id request or RAU Reject if the subscriber is previously attached to a MME and the MS has not provided a PTMSI_SIG in Attach request / RAU PDU.

Identifying EPC-Capable 3G Subscribers Activated via GN Interface

Previous Behavior: : When 3G EPC-capable subscribers were attached to the S4-SGSN and activated via the Gn interface, the show subscriber summary command incorrectly listed the 3G subscribers as activated via the S4 interface.

New Behavior: The software has been modified to correct how the system identifies 3G subscribers activated via the Gn and S4 interfaces. The show subscriber summary command now correctly identifies the interface over which a 3G subscriber has been activated.

Managing TLLI from Unknown Subscriber

Previous Behavior: Immediately after receiving an uplink packet from an unknown subscriber the SGSN sent Detach.

New Behavior: When receiving an uplink packet from an unknown subscriber with local or foreign TLLI, the SGSN will queue the TLLI for that subscriber until a configured number of packets are received and then the SGSN sends Detach. A new "queue-unknown-tlli" command has been added to the SGSN Global configuration mode to support the change in functionality.

Impact on Customer: Stats per Routing Area are not pegged for the packets from an unknown subscriber except for those packets for which the SGSN sends Detach.

PDP Activation Support for EPS Subscribers using Non-EPC Devices

Previous Behavior: If a subscriber had only an EPS subscription but was using a non-EPC device, PDP activation on the S4-SGSN was always attempted via the Gn interface. Since the system always looks for a GPRS subscription for activation via the Gn interface, activation would fail.

New Behavior: If a subscriber has only an EPS subscription at the HLR / HSS, and attempts PDP activation from a non-EPC device, the S4-SGSN will attempt to activate the PDP context over the S4 interface. The S4-SGSN will perform APN selection using the EPS subscription and, if that succeeds, PDP activation will proceed using the S4 interface. However, if the DNS server returns a GGSN address instead of PGW-S5 interface address for the APN FQDN, the S4-SGSN will reject the PDP activation because a GPRS subscription is required for activation via the Gn interface.

This implementation of this new behavior is based on the following:

  • If an APN is in the user's EPS subscription it means it is an LTE APN. As a result, operators should ensure that the PGW S5-GTP address is available for those APNs.
  • For PDP activation over the Gn interface, the S4-SGSN looks for a GPRS subscription because activation of an EPS subscription on the Gn interface is not yet supported.

Note that an EPS subscriber with a non-EPC capable UE could attempt PDP activation in the following scenarios:

  • The UE is EPC (4G) capable, but the user has temporarily switched to 3G only mode. The user then attempts the first PDP activation after switching from 4G to 3G.
  • An EPS subscriber inserted a 4G SIM card in a 3G phone.

Processing of Activate Requests Modified

Previous Behavior: The Activate Requests are processed during on-going Attach procedure for a subscriber who is already Attached.

New Behavior: The Activate Requests are dropped during on-going Attach procedure for a subscriber who is already Attached.

Impact on Customer: An increase in Activation re-transmission requests will be observed in the network when Activate Requests are dropped during ongoing Attach procedure for a subscriber who is already Attached.

Sending ULI and UE Timezone IE in GTPv2 CSRs

Previous Behavior: : The S4-SGSN was not including User Location Information (ULI) or the UE Time Zone IE in GTPv2 Create Session Request (CSR) messages as required by standard TS 29.274 section 7.2.1.

New Behavior: The software has been modified to correct this issue. To comply with the standard, the S4-SGSN now provides the following:

  • The ULI and UE Time Zone IE in GTPv2 Create Session Request messages sent by the S4-SGSN during PDP activation procedures.
  • The UE Time Zone value in GTPv2 Create Session Request messages sent by the S4-SGSN during SGW relocation procedures.

No CLI changes were required to implement this functionality.

IMPORTANT:

The PGW Requested Location Information Change Reporting function is not yet supported on the S4-SGSN. As a result, if that functionality is requested, the SGSN will not include ULI in the GTPv2 Create Session Request messages sent during SGW relocations.

SGSN Configuration Management Changes as of January 31, 2013

This section provides information on SGSN configuration command changes in release 14.0.

IMPORTANT:

For more information regarding features in this section, refer to the Command Line Interface Reference for this release.

New SGSN Configuration Commands

This section identifies SGSN commands new in release 14.0.

queue-unknown-tlli

New command enables, disables, and configures parameters that manage TLLI and packets received from unknown subscribers. Enabling the command causes the SGSN to store the TLLI of an unknown subscriber in a hash list.

SGSN Global Configuration Mode

queue-unknown-tlli [ expiry-time time | max-pkts
 number ]
[ default | no ] queue-unknown-tlli

Where:

  • expiry-time - Defines the number of minutes before the SGSN checks the hash list for expired TLLI entries and removes them..
  • max-pkts - Defines the maximum number of packets with TLLI of an unknown subscriber that can be queued before Detach is sent.
  • default - Disables the queue configuration.
  • no - Disables the queue configuration and clears the has list.

qos-modification inform-rnc-before-ue

New CLI control, introduced in the SGSN Service configuration mode, helps the operators to prevent QoS re-negotiation failures by providing the flexibility to enable/ disable RAB set up followed by UPCQ towards GGSN / Modify towards UE based on whether or not RNC downgrades the QoS. By default, the SGSN informs UE before RNC.

SGSN Service Configuration Mode
qos-modification inform-rnc-before-ue
no qos-modification 

Where:

  • Execution of the command qos-modification overrides SGSN Behavior during PDP modification procedure.
  • On execution of the keyword inform-rnc-before-ue, the SGSN informs RNC of new QoS before informing UE.

Modified SGSN Configuration Commands

This section identifies SGSN commands modified in release 14.0.

gtp send

In the Call Control Profile Configuration Mode, the keywords rai and uli for the command gtp send have been enhanced to include new keyword options to select the PLMN.

Call Control Profile Configuration Mode
gtp send { rai | uli } [ use-local-plmn [ network-sharing { use-selected-plmn | use-ue-plmn | use-common-plmn } ] 

Where:

use-local-plmn: This keyword includes the local PLMN when network is not shared.
  • network-sharing: This keyword configures network sharing.
  • use-selected-plmn: This keyword includes the Selected PLMN when network sharing is enabled.
  • use-ue-plmn : This keyword includes the Selected PLMN for supporting UE and Common PLMN for non-supporting UE when network sharing is enabled.
  • use-common-plmn: This keyword includes the Common PLMN when network sharing is enabled.

iu-hold-connection

The range of the parameter iu-hold-connection is modified, the minimum permissible limit is changed from “10” seconds to “1” second.

IMPORTANT:

It is recommended to use a minimum value of “10” seconds. If a value less than “10” seconds is used, more collisions may be observed. If the minimum value of “1” is set, after a re-load INTRA-RAU (with unknown ptmsi, old-rai known) will be released in “1” second if the Identity Rsp does not come within “1” second.

IuPS Service Configuration Mode

iu-hold-connection [ always | requested-by-ms ] [ hold-time seconds ] 

Deprecated SGSN Configuration Commands

This section identifies SGSN commands deprecated in release 14.0.

local-directory

Backup of statistics into the local directory is no longer a needed function so the local-directory command (in italics below) has been removed from the Bulkstatistics configuration mode.

[local]asr5000(config-bulkstats)# ?
...
local-directory      -
Configure the local directory for storing collection files 
remotefile           -
Configure the naming convention(s) used when storing the collection
files to the receiver
...

SGSN Performance Management Changes as of January 31, 2013

New SGSN Bulk Statistics

This section identifies new SGSN bulk statistics available in release 14.0.

New in the SGSN Schema

New bulk stats track 2G Attach Rej with network failure cause codes:

  • 2G-attach-rej-network-failure-ext
  • 2G-attach-rej-network-failure-int
  • 2G-comb-attach-rej-network-failure-ext
  • 2G-comb-attach-rej-network-failure-int

New bulk stats track 3G Attach Rej with network failure cause codes:

  • 3G-attach-rej-network-failure-ext
  • 3G-attach-rej-network-failure-int
  • 3G-comb-attach-rej-network-failure-ext
  • 3G-comb-attach-rej-network-failure-int

New bulk stats for Iu Release before 3G Attach:

  • 3G-attach-fail-iu_release-external
  • 3G-attach-fail-iu_release-internal
  • 3G-attach-fail-iu_release-comb-external
  • 3G-attach-fail-iu_release-comb-internal

New stats track 3G Activation Failure/Reject with cause codes:

  • 3G-actv-rej-network-failure-ext
  • 3G-actv-rej-network-failure-int
  • 3G-actv-rej-svc-opt-tmp-out-of-order-ext
  • 3G-actv-rej-svc-opt-tmp-out-of-order-int
  • 3G-actv-rej-unspecified-error-ext
  • 3G-actv-rej-unspecified-error-int
  • 3G-sec-actv-rej-unspecified-error-ext
  • 3G-sec-actv-rej-unspecified-error-int
  • 3G-actv-rej-insufficient-resources-ext
  • 3G-actv-rej-insufficient-resources-int
  • 3G-sec-actv-rej-insufficient-resources-ext
  • 3G-sec-actv-rej-insufficient-resources-int
  • 3G-total-actv-reject-internal
  • 3G-total-actv-reject-external

Statistics for 2G simple and combined Attach failures:

  • 2G-attach-fail-suspend-received
  • 2G-attach-fail-bvc-rst-received
  • 2G-attach-fail-sai-failure
  • 2G-attach-fail-auth-tmr-expiry
  • 2G-attach-fail-sgsn-init-detach
  • 2G-attach-fail-plmn-check-failed
  • 2G-attach-fail-identity-failure
  • 2G-attach-fail-radio-status-cell-resel
  • 2G-attach-fail-check-imei-failure
  • 2G-attach-fail-rej-due-to-congestion
  • 2G-attach-fail-camel-failure
  • 2G-attach-fail-radio-status-bad
  • 2G-attach-fail-t3350-expiry
  • 2G-attach-fail-auth-failure
  • 2G-attach-fail-glu-failure
  • 2G-attach-fail-ms-init-detach
  • 2G-attach-fail-opr-policy-failure
  • 2G-attach-fail-cl-init-detach
  • 2G-attach-fail-abort-on-attach
  • 2G-attach-fail-attach-on-attach
  • 2G-attach-fail-ready-tmr
  • 2G-attach-fail-camel-srv-not-assoc
  • 2G-attach-fail-p-tmsi-sign-mismatch
  • 2G-attach-fail-xid-resp-failure
  • 2G-attach-fail-internal-failure
  • 2G-attach-fail-comb-suspend-received
  • 2G-attach-fail-comb-bvc-rst-received
  • 2G-attach-fail-comb-sai-failure
  • 2G-attach-fail-comb-auth-tmr-expiry
  • 2G-attach-fail-comb-sgsn-init-detach
  • 2G-attach-fail-comb-plmn-check-failed
  • 2G-attach-fail-comb-identity-failure
  • 2G-attach-fail-comb-radio-status-cell-resel
  • 2G-attach-fail-comb-check-imei-failure
  • 2G-attach-fail-comb-rej-due-to-congestion
  • 2G-attach-fail-comb-camel-failure
  • 2G-attach-fail-comb-radio-status-bad
  • 2G-attach-fail-comb-t3350-expiry
  • 2G-attach-fail-comb-auth-failure
  • 2G-attach-fail-comb-glu-failure
  • 2G-attach-fail-comb-ms-init-detach
  • 2G-attach-fail-comb-ms-init-detach
  • 2G-attach-fail-comb-opr-policy-failure
  • 2G-attach-fail-comb-cl-init-detach
  • 2G-attach-fail-comb-abort-on-attach
  • 2G-attach-fail-comb-attach-on-attach
  • 2G-attach-fail-comb-ready-tmr
  • 2G-attach-fail-comb-camel-srv-not-assoc
  • 2G-attach-fail-comb-p-tmsi-sign-mismatch
  • 2G-attach-fail-comb-xid-resp-failure
  • 2G-attach-fail-comb-internal-failure

New in the System Schema

The following new bulk statistics are also new disconnect reason visible in the output of the show session disconnect-reason verbose command.

  • sgsn-cancel-loc-inital-attach(513)
  • sgsn-nrspca-actv-rej-by-sgsn(515)
  • sgsn-nrspca-actv-rej-by-ms(516)
  • sgsn-no-ptmsi-signature(518)

Modified SGSN Bulk Statistics

This section identifies modified SGSN bulk statistics available in release 14.0.

None in this release.

Deprecated SGSN Bulk Statistics

This section identifies SGSN bulk statistics deprecated in release 14.0.

Deprecated in the SGSN Schema

  • 2G-attach-fail-plmn-check-failed
  • 2G-attach-fail-comb-plmn-check-failed

New SGSN Performance Commands

This section identifies new SGSN performance commands available in release 14.0.

None for this release.

Modified SGSN Performance Commands

This section identifies modified SGSN performance commands available in release 14.0.

clear ss7-routing-domain

The command clear ss7-routing-domain asp all sctp statistics end-point is issued to clear statistics of ASP instances, the error message displayed on for non-existing ASP instances is modified to indicate the instance does not exist.

Exec Mode

clear ss7-routing-domain
asp all sctp statistics end-point

show bulkstatistics

The output for the show bulkstats command has been modified and the following counter has been removed:

  • Local File Storage

show gmm-sm statistics verbose

New counters peg TLLI from unknown subscribers. These new counters appear in both the GPRS GMM Stack Internal Statistics section of the command output:

  • rem-utlli-ptmsi-alloc:
  • rem-utlli-attach-rx:
  • rem-utlli-rau-rx:
  • rem-utlli-max-pkts:
  • rem-utlli-queue-full:
  • rem-utlli-timer-expiry:
  • detach-sent-utlli:
  • utlli-entries-added:

New statistics have been added to indicate transmission or receipt of a Modification PDP Context Reject with a cause code of Request Rejected, Bearer Control Mode (BCM) Violation on the S4-SGSN.

These new counters appear in both the Modify PDP Context Denied Tx and Modify PDP Context Denied Rx sections of the command output:

  • 3G-Req Rej BCM Violation
  • 2G-Req Rej BCM Violation
  • 3G-Iu Release Before Attach Segregation:
    • GPRS-Attach
      • External Triggers
      • Internal Triggers
    • Comb-Attach:
      • External Triggers
      • Internal Triggers
The following new counters track 3G activation failure/reject with cause codes:
  • Activate Context Reject Segregation:
  • Total-3G-Actv-Reject:
  • External Triggered
  • Internal Triggered
  • 3G-Primary-Actv-Reject
  • External Triggered
  • Internal Triggered
  • 3G-Secondary-Actv-Reject
  • External Triggered
  • Internal Triggered
  • Activate Primary PDP Context Insufficient Resource Cause Segregation
  • Total 3G-Insuff res triggers
  • Total 3G-Insuff res external triggs
  • 3G-Qos Negotiation Fail
  • 3G-Operator Policy Fail
  • 3G-GGSN Has No Resources
  • 3G-GGSN Changed PDP Type
  • 3G-GGSN PDP Addr Alloc Fail
  • 3G-RNC GTPU Path Failure
  • 3G-RNC RAB Establishment Fail
  • Total 3G-Insuff res internal triggs
  • 3G-SGSN Has No Memory
  • Activate Secondary PDP Context Insufficient Resource Cause Segregation
  • Total 3G-Insuff res triggers
  • Total 3G-Insuff res external triggs
  • 3G-Qos Negotiation Fail
  • 3G-Operator Policy Fail
  • 3G-Primary is GTPV0
  • 3G-GGSN Has No Resource
  • 3G-PDP Addr Type Mismatch
  • 3G-RNC GTPU Path Failure
  • 3G-RNC RAB Establishment Fail
  • 3G-Ongoing Bundle Deactivation
  • Total 3G-Insuff res internal triggs
  • 3G-SGSN Has No Memory

show gmm-sm statistics gmm-only verbose

New counter added:

  • No suitable cell in Location Area

show linkmgr instance <#> parser statistics all

Link Manager parser statistics are updated to include the count of TC-Continue messages forwarded and received at respective Link Managers. Also a field has been added to indicate the number of free transactions available per Link Manager instance since the max is 2048. Listed below are the new counters added:

  • FWD Cont
  • RCD Cont
  • FWD Cont Error
  • Free Dlg Count:

show location-service statistics

The following changes were made to the output:

  • Changed the names of the message statistics.
  • Added a counter for PSL request dropped.
  • Removed Retry and Timeout counter.
  • Removed LR Request counters.
  • Changed the names of Message Error statistics.

The new display appears as:

[local]SGSN3# show
location-service statistics all
Location Service  Statistics
for all services
Message Statistics:
  PSL
Request            0      PSL Answer            0
  PSL
Request Dropped    0      PSL
Answer Dropped    0
Message Error Statistics:
  User
Unknown            0     Unauthorized
Requesting Network  0
  Unreachable
User        0     Suspended User           0
  Detached
User            0    Positioning Denied      0
  Positioning
Failed       0    Unreachable
LCS Client   0
  Other Errors             0

show s4-sgsn statistics all

New statistics have been added to provide more detailed information on the reasons for Idle Mode Signaling Reduction (ISR) deactivations on the S4-SGSN. These new counters appear in the ISR Deactivations section of the command output:

  • 3G NW Initiated Detach
  • 3G MR IDT Expiry
  • 3G MS Initiated Detach
  • 3G Cancel Location from HSS/HLR
  • 3G SRNS Abort
  • 3G Local Admin Detach
  • 3G SGW Change During SRNS

As a result of these counter additions, the 3G Implicit Detach counter has been deprecated.

show session setuptime

A check is added prior to the retrieval of the counter values from the Session Manager to verify if the given service is configured and running. If an SGSN service is not configured and the command show session setuptime sgsn-only is executed, an error message is displayed indicating the service is not configured/ started. If an SGSN service is configured counter values are retrieved.

Exec Mode

show session setuptime
sgsn-only

show session subsystem facility

The show CLI output for show session subsystem facility aaamgr all (or) instance <num> has been modified. No functional change has occurred. The word ‘Primary’ has been removed from 3 fields in the show command output:

Old display:

  • 8010 Total APN Primary database records
  • 0 Total PDN GW Primary database records
  • 8 Total Duplicate Entries in Primary database records

New display:

  • 8010 Total APN database records
  • 0 Total PDN GW database records
  • 8 Total Duplicate Entries in database records

show sgsn-fast-path statistics all/smgr-instance

The CLI output is enhanced to include a new counter to indicate the number of un-attempted fast path activations due to non-availability of NPU flow. Listed below is the new counter:

  • FP Max flow Limit Reached

show sgsn-service name

New counter introduced to display if the new funtionality enabled/disabled to inform RNC before UE during QoS modification.

  • Inform RNC before UE during QOS Modification : Enabled

show sgsn sessmgr instance memory statistics

The output has been enhanced to include HSS Session and Request statistics for:

  • entities
  • block user
  • block size
  • number of allocations
  • number of free items

show sgtpc statistics verbose

New counter pegs dropped GTPv0 messages:

  • GTPV0 msgs drpd due to no support in the usr app:

show subscribers { gprs-only | sgsn-only } full

In the EPS Subscription section of the command output, the PDN Allocation Type field has been renamed PGW Allocation Type. This name change was made to avoid confusing PDN Allocation Type with PDP Address Allocation Type.

The output is enhanced to include the “LCS Subscription Information” fields listed below:

  • LCS Subscription
    • GMLC List
    • GMLC Address
  • LCS Privacy Exception List
  • LCS Privacy Class
    • SS Code
    • SS Status
    • Notification to MS User
    • External Client List
      • External Client Id
      • GMLC Restriction
      • Notification to MS User
  • PLMN Client List
    • PLMN
  • Ext-External Client List
    • External Client Id
    • GMLC Restriction
    • Notification to MS User
  • Service List
    • Service Type Id
    • GMLC Restriction
    • Notification to MS User
  • MOLR List
    • MOLR Class
      • SS Code
      • SS Status
  • Add LCS Privacy Exception List
    • LCS Privacy Class
      • SS Code
      • SS Status
      • Notification to MS User
      • External Client List
      • PLMN Client List
      • Ext-External Client List
      • Service List

show subscribers { gprs-only | sgsn-only } full all

The following new fields have been added to the output for this command:

  • Ext PDP Type
  • Ext PDP Address Type
  • Ext PDP address

IMPORTANT:

Ext-PDP-Address and Ext-PDP-Address-Type fields only appear if the value for Ext-PDP-Type is ‘IPV4-V6’.

show support details Includes HSS-Peer Service Info

HSS Peer Service information displayed by theshow hss-peer-service service all command is now included in the show support details command.

Deprecated SGSN Performance Commands

This section identifies SGSN performance commands deprecated in release 14.0.

None in this release.

SGSN Security Management Changes as of January 31, 2013

This section provides information on SGSN security management changes in release 14.0.

None for this release.

SGSN Feature Changes as of December 21, 2012

This section provides information on SGSN feature changes in release 14.0.

IMPORTANT:

For more information regarding features in this section, refer to the ASR 5000 Serving GPRS Support Node Administration Guide for this release.

New SGSN Features

This section identifies SGSN features new in release 14.0.

None for this release.

Modified SGSN Features

This section identifies SGSN features modified in release 14.0.

Support for Non-Shared Area Access

Previous Behavior: The SGSN does not support non-shared area access when network-sharing is enabled. The SGSN sends the common-plmn value if the selected-plmn IE is not present for the non-shared area.

New Behavior: A new CLI command is provided to support non-shared area access when network-sharing is enabled. A new network-sharing command option non-shared is provided in the IuPS Service Configuration Mode to enable non-shared area access. Refer to the section New SGSN Configuration Commands for syntax details.

Impact: Non-shared area access is supported when network-sharing is enabled

SGSN Configuration Management Changes as of December 21, 2012

This section provides information on SGSN configuration command changes in release 14.0.

IMPORTANT:

For more information regarding features in this section, refer to the Command Line Interface Reference for this release.

New SGSN Configuration Commands

This section identifies SGSN commands new in release 14.0.

network-sharing non-shared

New command allows non-shared area access when network-sharing is enabled. By default non-shared access is disabled. The no form of the command is used to disable non-shared area access.

IuPS Service Configuration Mode

network-sharing non-shared
no network-sharing non-shared 
default network-sharing
non-shared 

Modified SGSN Configuration Commands

This section identifies SGSN commands modified in release 14.0.

None for this release.

Deprecated SGSN Configuration Commands

This section identifies SGSN commands deprecated in release 14.0.

gmm-sm-statistics attach-rejects

This command is deprecated and removed from the code.

SGSN-Global Configuration mode

gmm-sm-statistics attach-rejects
cause network-failure only-internal  
no gmm-sm-statistics
attach-rejects 

SGSN Performance Management Changes as of December 21, 2012

This section provides information on SGSN performance management changes in release 14.0.

None for this release.

SGSN Security Management Changes as of December 21, 2012

This section provides information on SGSN security management changes in release 14.0.

None for this release.

SGSN Feature Changes as of November 30, 2012

This section provides information on SGSN feature changes in release 14.0.

IMPORTANT:

For more information regarding features in this section, refer to the ASR 5000 Serving GPRS Support Node Administration Guide for this release.

New SGSN Features

This section identifies SGSN features new in release 14.0.

Release 8 Specific IEs Supported for MAP

The following Release 8 IEs, for MAP, 3GPP specificationTS 29.002, are supported.

  • Update GPRS Location - Req:
    • Supported RAT Types Indicator
    • EPS Info
    • Serving Node Type Indicator
    • Supported Features
    • Used RAT Type
    Update GPRS Location - Resp:
    • SGSN-MME Separation Support Indicator
    Insert Subscriber Data - Req:
    • EPS Subscription Data
    • Roaming Restricted In SGSN/MME Due To Unsupported Feature
    Delete Subscription Data - Req:
    • EPS Subscription Data Withdraw
    Send Authentication Info - Req:
    • Requesting Node Type (New enums to be added)
    • Number of additional requested vectors
    • Additional requested Vectors are for EPC
    READY FOR SM - Req:
    • Additional Alert Reason Indicator

Support for Modified S-CDR Field “System Type”

The SGSN supports a new custom dictionary “Custom38”, In this dictionary, the “System Type” field is not included in the S-CDR for GERAN and the value for UTRAN is “1”.

Modified SGSN Features

This section identifies SGSN features modified in release 14.0.

Defaults Included for RANAP ARP IE

Previous Behavior: If ARP mapping was not configured in the APN profile with the ranap allocation-retention-priority-ie, then the SGSN was not sending the ARP IE in the RANAP message even if ranap arp-ie was configured for the RNC under the IuPS service configuration.

New Behavior: Default function has changed so that even if ARP mapping has not been configured in the APN profile, the SGSN will send out default values in the RANAP message when ranap arp-ie is configured for the RNC under the IuPS service configuration.

SGSN Configuration Management Changes as of November 30, 2012

This section provides information on SGSN configuration command changes in release 14.0.

None in this release.

SGSN Performance Management Changes as of November 30, 2012

New SGSN Bulk Statistics

This section identifies new SGSN bulk statistics available in release 14.0.

None in this release.

Modified SGSN Bulk Statistics

This section identifies modified SGSN bulk statistics available in release 14.0.

None in this release.

Deprecated SGSN Bulk Statistics

This section identifies SGSN bulk statistics deprecated in release 14.0.

None in this release.

New SGSN Performance Commands

This section identifies new SGSN performance commands available in release 14.0.

None in this release.

Modified SGSN Performance Commands

This section identifies modified SGSN performance commands available in release 14.0.

show aaa group name aaa-grp

New prefix dynamic-load is added to the dictionary name to indicate if it is a dynamic dictionary.The updated output contains the following new field:

  • dynamic-load

show gmm-sm statistics

The show ouput is updated with new counters to display the number of re-transmitted Activate PDP context request messages from MS for both 2G and 3G and counters to display each of the primary Activate PDP context request re-transmissions and secondary activate PDP context request re-transmissions. Listed below are the new counters:

  • Activate Context Request Retransmitted
    • 3G-Primary-Actv-drop
    • 2G-Primary-Actv-Drop
    • 3G-Secondary-Actv-Drop
    • 2G-Secondary-Actv-Drop

show sgtpc statistics verbose

The output of this command has been updated to include the following new counter to display GTPv0 messages dropped:

  • GTPV0 msgs drpd due to no support in the usr app

Deprecated SGSN Performance Commands

This section identifies SGSN performance commands deprecated in release 14.0.

None in this release.

SGSN Security Management Changes as of November 30, 2012

This section provides information on SGSN security management changes in release 14.0.

None for this release.

SGSN Feature Changes as of November 7, 2012

This section provides information on SGSN feature changes in release 14.0.

IMPORTANT:

For more information regarding features in this section, refer to the ASR 5000 Serving GPRS Support Node Administration Guide for this release.

New SGSN Features

This section identifies SGSN features new in release 14.0.

Release 8 Specific IEs Supported for MAP

The following Release 8 IEs, for MAP, 3GPP specificationTS 29.002, are supported.

  • Update GPRS Location - Req:
    • Supported RAT Types Indicator
    • EPS Info
    • Serving Node Type Indicator
    • Supported Features
    • Used RAT Type
    Update GPRS Location - Resp:
    • SGSN-MME Separation Support Indicator
    Insert Subscriber Data - Req:
    • EPS Subscription Data
    • Roaming Restricted In SGSN/MME Due To Unsupported Feature
    Delete Subscription Data - Req:
    • EPS Subscription Data Withdraw
    Send Authentication Info - Req:
    • Requesting Node Type (New enums to be added)
    • Number of additional requested vectors
    • Additional requested Vectors are for EPC
    READY FOR SM - Req:
    • Additional Alert Reason Indicator

Modified SGSN Features

This section identifies SGSN features modified in release 14.0.

Defaults Included for RANAP ARP IE

Previous Behavior: If ARP mapping was not configured in the APN profile with the ranap allocation-retention-priority-ie, then the SGSN was not sending the ARP IE in the RANAP message even if ranap arp-ie was configured for the RNC under the IuPS service configuration.

New Behavior: Default function has changed so that even if ARP mapping has not been configured in the APN profile, the SGSN will send out default values in the RANAP message when ranap arp-ie is configured for the RNC under the IuPS service configuration.

SGSN Configuration Management Changes as of November 7, 2012

This section provides information on SGSN configuration command changes in release 14.0.

IMPORTANT:

For more information regarding commands in this section, refer to the GPRS/UMTS Command Line Interface Reference for this release.

New SGSN Configuration Commands

This section identifies new SGSN commands available in release 14.0.

peer-nri-length

New command enables the SGSN to use NRI-FQDN based DNS resolution for non-local RAIs when selection of the call-control profile is based on the old-RAI and the PLMN Id of the RNC.

Call Control Profile Configuration Mode

peer-nri-length <length>
remove peer-nri-length 

Modified SGSN Configuration Commands

This section identifies SGSN commands modified in release 14.0.

None for this release.

SGSN Performance Management Changes as of November 7, 2012

New SGSN Bulk Statistics

This section identifies new SGSN bulk statistics available in release 14.0.

None in this release.

Modified SGSN Bulk Statistics

This section identifies modified SGSN bulk statistics available in release 14.0.

None in this release.

Deprecated SGSN Bulk Statistics

This section identifies SGSN bulk statistics deprecated in release 14.0.

None in this release.

New SGSN Performance Commands

This section identifies new SGSN performance commands available in release 14.0.

None in this release.

Modified SGSN Performance Commands

This section identifies modified SGSN performance commands available in release 14.0.

show port

New keyword verbose displays port utilization data with kilobyte accuracy using decimal points.

Exec Mode

show port utilization
table verbose

There are no new fields added to the display.

Deprecated SGSN Performance Commands

This section identifies SGSN performance commands deprecated in release 14.0.

None in this release.

SGSN Security Management Changes as of November 7, 2012

This section provides information on SGSN security management changes in release 14.0.

None for this release.

SGSN Feature Changes as of September 28, 2012

This section provides information on SGSN feature changes in release 14.0.

IMPORTANT:

For more information regarding features in this section, refer to the ASR 5000 Serving GPRS Support Node Administration Guide for this release.

New SGSN Features

This section identifies SGSN features new in release 14.0.

AAA Changes To Support Location Services (LCS) Feature

The Location Services (LCS) feature in SGSN provides the mechanism to support mobile location services for operators, subscribers and third party service providers. AAA changes have been made to support the LCS feature. A new CDR type Mobile Terminated Location Request CDRs (LCS-MT-CDR) is introduced. LCS-MT-CDRs support the standard dictionaries.

For detailed information on LCS-MT-CDRs, refer to the Cisco ASR 5x00 GTPP Interface Administration and Reference manual.

The accounting command in GPRS Service Configuration Mode and SGSN Service Configuration Mode has been modified to include a new keyword lcs mt-cdr, to enable/disable the generation of LCS-MT-CDRs. New counters and statistics have been introduced to support LCS-MT-CDRs.

APN Redirection per APN with Lowest Context-ID

The APN Redirection per APN with Lowest Context-ID feature adds the flexibility to select the subscription APN with the least context ID when the APN is not found in the subscription. SGSN already provides sophisticated APN replacement with support for first-in-subscription, default APN, blank APN, and wildcard APN. This latest feature works along similar lines providing further flexibility to the operator in allowing activations when the MS requested APN is incorrect, misspelled, or not present in the subscription.The SGSN's APN selection procedure is based on 3GPP 23.060 Annex A, which this feature extends based on CLI controls under the APN Remap Table configuration mode.The APN Redirection per APN with Lowest Context-ID feature is selected within the CLI using a new keyword in the APN Remap Table configuration mode.

Commandguard

Operators can accidentally enter configuration mode via CLI or file replay. To protect against this, SGSN supports a new commandguard CLI command, commandguard, which is disabled by default, can only be enabled or disabled from the Global Configuration mode. When commandguard is enabled it affects the configure and autoconfirm CLI commands by causing them to prompt (Y/N) for confirmation. When autoconfirm is enabled commandguard has no affect. The commandguard state is preserved in the SCT and, when enabled, is output by the various variants of the show config CLI command.

Disassociated DSR Support on the S4-SGSN

The S4-SGSN now supports the disassociation of the SGSN and EGTP applications for a Delete Session Request in a certain scenario. In this scenario, the SGSN application instructs the EGTP facility to send the Delete Session Request to the SGW and not respond back to the SGSN application to confirm the action. Since the SGSN application is no longer waiting for a response from the EGTP facility, there will be reduced internal communication between the SGSN and EGTP. The EGTP facility will handle retransmissions of the DSR request, thereby eliminating the possibility of hanging sessions at the SGSN.

GMM-Cause for MAP-Cause for ‘roaming-not-allowed’

It is now possible for the operator to configure the desired reject cause code for map-cause ‘roaming-not-allowed’ when sending GMM-Reject to the UE. Cause options include:

  • gprs-serv-and-non-gprs-serv-not-allowed
  • gprs-serv-not-allowed
  • gprs-serv-not-in-this-plmn
  • location-area-not-allowed
  • network-failure
  • no-suitable-cell-in-this-la
  • plmn-not-allowed
  • roaming-not-allowed-in-this-la

GTP Echo-Specific Retransmissions Timer

Previously, the retransmission-timeout parameter for the SGSN's Gn interface was common for GTP-C echo and non-echo messages. A single "fixed-retransmission" timer (explicitly configured via CLI) made it difficult for operators to fine tune this timer to ensure fast failover to an alternative gateway, yet not have all existing tunnels to a GGSN disconnected due to one or two local GTP echo messages. Now, the SGSN supports different retransmission-timeout values for GTP-C echo and non-echo messages. The idea is to prevent early detection of path failure in cases of delayed echo responses due to congestion in the network.

Now, the SGSN supports two echo-retransmission mechanisms for both GTP-C and GTP-U based on how retransmission-timeout is calculated, whether statically or dynamically. One mechanism is the echo-retransmission default, the fixed-retransmission timer, which is configured with a fixed value. The second mechanism is the exponential-backoff timer for which retransmission-timeout is not explicitly configured but calculated dynamically based on RTT values of previous echo transmissions.

gtpv2 Protocol Support for SRNS Relocation on the S4-SGSN

As part of the S4-SGSN Support for Intra- and Inter-SGSN SRNS feature, the software has been enhanced to support the use of the gtpv2 (egtp) protocol to support:

  • Inter-SGSN SRNS relocation over the S16 interface
  • MME - SGSN SRNS relocation over the S3 interface

Ignore Context-ID During 4G/3G Handovers

HSS and HLR, when operating as separate network nodes, are required to use the same context-ID for a given APN-configuration of a subscriber. During inter-RAT cell re-selections and handovers between 2G/3G and 4G, if the SGSN does not find a matching APN-configuration for the given context-ID learnt from the peer node, then the PDP does not get established. This could result in SRNS relocation failures when none of the PDP's learnt from the SGSN has a matching context-ID in the HLR.

New commands have been added to enable the operator to configure the SGSN to ignore the context-ID provided by the peer and to use the PDP- type and address information to search through HLR subscription and to update the context-ID information within the PDP. For details, refer to the description for the rau-inter command under the Call-Control Profile Configuration Mode Commands section of the Cisco ASR 5x00 GPRS / UMTS Command Line Interface Reference.

Location Services

LoCation Services (LCS) on the SGSN is a 3GPP standards-compliant feature that enables the SGSN to collect and use or share location (geographical position) information for connected UEs in support of a variety of location services, such as location-based charging and positioning services. The SGSN uses the Lg interface to the gateway mobile location center (GMLC), which provides the mechanisms to support specialized mobile location services for operators, subscribers, and third party service providers. Use of this feature and the Lg interface is license controlled.

A variety of new commands are used to configure this feature and they are identified in the New SGSN Configuration Commands section of this document. For details about this feature and its configuration, refer to the Location Services section of the SGSN Administration Guide.

Lock/Shutdown the BSC from the SGSN

When the SGSN returns to Active state, after scenarios such as rebooting or reloading, all the BSCs that had been connected to the SGSN would attempt to re-establish connections. This could result in two serious problems for operators:

  1. high CPU usage in the SGSN where too many BSC/RNCs were connected.
  2. network overload when other network nodes cannot match the SGSN's capacity.

The SGSN now supports a Lock/Shutdown feature that provides a two prong solution. CPU Usage Solution: Staggering the BSC auto-learning procedures when the SGSN re-loads will help to reduce the high CPU usage. This can be achieved by the operator locking the NSE/BSCs from the SGSN before reboot/reload and then unlocking them one-by-one to avoid high CPU usage.

Network Overload Solution: A new timer, SNS-GUARD, has been added to clean-up resources if the SNS procedure does not complete properly, whether or not the BSC is administratively locked. Now the SGSN starts this timer after sending SNS-SIZE-ACK and the BSC information will be removed, if the auto-learning clean-up procedure does not complete before the timer expires.

A series of new commands and keywords has been added to enable the operator to configure this new administrative Lock/Shutdown the BSC functionality as part of 'interface management' configuration. For details, refer to the SGSN Global Interface Management section of the Cisco ASR 5x00 GPRS / UMTS Command Line Interface Reference.

MS, PGW and HSS Initiated PDP Context Modification Procedure Support

The S4-SGSN now supports the following MS and network initiated PDP modification procedures on the S4-SGSN:

  • 3G MS initiated PDP modification procedure
  • 2G MS initiated modification procedure
  • 3G PGW Initiated PDP modification procedure
  • 2G PGW initiated bearer modification procedure
  • 3G HSS initiated PDP modification procedure
  • 2G HSS initiated bearer modification procedure

S4-SGSN Support for Intra- and Inter-SGSN SRNS Relocation

SRNS relocation is the method defined in 3GPP TS 23.401 for connected mode inter-RAT handovers from E-UTRAN to UTRAN or UTRAN to E-UTRAN networks. The SGSN already supports SRNS relocation across the Gn interface. The S4-SGSN now also supports SRNS relocation for the following cases across the S3 (S4-SGSN to MME) and S16 (S4-SGSN to S4-SGSN) interfaces:

  • Intra-SGSN SRNS relocation
  • Inter-SGSN SRNS relocation over the S16 interface
  • UTRAN-to-E-UTRAN connected mode Inter-RAT handover over the S3 interface
  • UTRAN-to-E-UTRAN connected mode Inter-RAT handover over the S3 interface

S4-SGSN Support for ISD / DSD Message Handling and HSS Initiated Bearer Modification

ISD / DSD Message Handling

Insert Subscriber Data (ISD) and Delete Subscriber Data (DSD) messages are generated by the HSS/HLR. These messages are used to communicate the subscribers current subscription data to the S4-SGSN. The subscription data for a subscriber can include GPRS subscription data or EPS subscription data or both.

The PDP is either modified or deleted based on the subscription data received by the S4-SGSN. The S4-SGSN deletes the PDP context if any form of barring is detected or if the APN-name or PDP-type of the PDP address is changed. The S4-SGSN modifies the PDP if QoS is changed or APN-AMBR is changed (in case of EPS subscription).

If a PDP modification is required based on the subscription data received but the associated UE is disconnected or in an inactive state, such PDP contexts are deleted by the S4-SGSN.If the UE is connected or in a ready state, the S4-SGSN sends an updated bearer command (with subscribed QoS) to the S-SGW or P-GW and the P-GW initiates a PDP modify procedure.

The Modify bearer command is a notification sent to the S-GW/P-GW which notifies a change in the subscribed QoS. The message is sent to S-GW/P-GW if the UE is in ready or connected state. Modify Bearer command is not sent when the PDP is in preserved state and when ISR is active, in such cases the S4-SGSN initiated modify request using Modify Bearer Request updates the QoS to the S-GW/P-GW after the PDP is active or UE activity is detected on S4-SGSN respectively.

Support for PDN Type IPv4_OR_IPv6 (3) on the S4-SGSN

To comply with 3GPP TS 29.272, the S4-SGSN now supports a PDP type value of IPv4_OR_IPv6 (3) sent from the Home Subscriber Server (HSS).

This value is used to indicate that the PDN can be accessed either in IPv4 mode, or in IPv6 mode, but not from UEs supporting dualstack IPv4v6. This value is only used as part of the APN subscription context, as an authorization mechanism between the HSS and MME.

IMPORTANT:

The PDP type value of IPv4_OR_IPv6 will never be used as a requested PDN Type from the UE, since UEs use only one of their supported PDN Types, i.e., IPv4 only, IPv6 only or IPv4v6 (dualstack).

Modified SGSN Features

This section identifies SGSN features modified in release 14.0.

Change to GTP_SGSN_CONTEXT_ACK_MSG 'cause' IE

Previous Behavior: Earlier when SGSN ctxt ack is sent in the scenarios noted below, then the message contains the "gtp authentication failure" in the IE "cause". Scenario:

  • ISRAU in 3G
  • SGSN ctxt response with No IMEISV
  • Identity request to MS
  • Identity response with No identity
  • SGSN ctxt ack

New Behavior: The value in "cause" IE in GTP_SGSN_CONTEXT_ACK_MSG is changed for a specific scenario during ISRAU in 3G. Now the cause code is "GTP_REQUEST_ACCEPTED" in IE "cause".

Change in LORC Status in DPCR for Specified Scenario

Previous Behavior: In the scenario noted below, the LORC status was not updated when PDP contexts deactivated and, while sending DPCR, the correct LORC status was not being included even if the LORC status was "UE is back in Radio".

  • Precondition:
    • Enable LORC Feature in the apn-profile for sending LORC to GGSN.
    • Enable IU release cause in iups-service.
  • Scenario:
    • Attach & activate in 3G.
    • Send IU Release Request
    • SGSN sends IU Rel Cmd, UPCQ with LORC "LORC detected for UE".
    • UPCR, Iu Release Complete.
    • Send DPCQ from the GGSN.
    • Paging.
    • Service Request for Paging, common ID, Sec mode command, complete.
    • After Iu is established, Deactivate Request, Accept.
    • DPCR is sent by SGSN with LORC status.

New Behavior: Now the LORC status is updated when PDP contexts are deactivated and the LORC status "UE is back in Radio" is included in DPCR.

Change in Cancel-Location Behavior

Previous Behavior: During a 2G call, when Cancel Location was received after Attach Accept is sent, the SGSN was not sending Detach Request.

New Behavior: Now during a 2G call, if Cancel Location is received after Attach Accept is sent, then Page Req will be sent and page response Detach Request will be sent to the MS. If Attach Accept has not been sent, the Attach Reject will be sent.

Changes in Traps for SS7 Congestion

Previous Behavior: When the SGSN receives a congestion indication (SCON) for a remote code (PC) from a signaling gateway (SG), this results in an SS7PCCongested trap. So if the SGSN receives an indication that the remote has become unavailable (DUNA) after receiving a congestion indication and without receiving a congestion cleared indication, then the SGSN generates:

  • SS7PCCongestionCleared
  • SS7PCUnavailable

New Behavior: When the SGSN receives a congestion indication (SCON) from a signaling gateway (GS), which is followed by an indication that the remote has become unavailable (DUNA) without receiving a congestion cleared indication, then the traps generated are:

  • SS7PCCongested
  • SS7PCUnavailable

Extensions Added to Initial UE Message Extensions

Previous Behavior: Previously, the Initial UE Message Extension did not contain any of the following IE Extensions: CSG ID, Cell Access Mode, and L-GW Transport Layer Address and the extensions were not supported by the SGSN in Mon-Pro.

New Behavior: Per 3GPP TS 25.413, CSG ID, Cell Access Mode, and L-GW Transport Layer Address extensions have been added to the Initial UE MEssage Extensions and they display in Mon-Pro in RANAP if they are provided by the MS.

Flush-LL Message Sent to BSC When Intra-RAU Occurs in SGSN from a Different Cell

Previous Behavior: In a certain scenario, a Flush-LL message was not sent to the BSC.

  • Scenario:
    • Attach a subscriber in 3G.
    • Inter-RAT RAU to 2G occurs in foreign TLLI.
    • During RAU accept retries, suspend and suspend ack occurs with the new local TLLI.
    • Intra RAU again occurs with the local TLLI derived from the PTMSI of the previous RAU Accept Message (from a different cell).
    • The Flush LL message is not sent to the old BSC.

New Behavior: In this scenario, the Flush-LL message now will be sent to the BSC.

Impact: The number of Flush-LL messages increases if this scenario occurs in the network.

In/Outbound Stream Control Enhanced

Previous Behavior: The maximum configurable CLI limit for sctp-max-out-strms was set to 65535 even though internally the number was capped at 16 as the maximum number of streams supported.

New Behavior: The maximum configurable CLI limit for sctp-max-out-strms is now 16, the default limit. To expand the operators control of streaming, a configurable parameter to control inbound streaming - sctp-max-in-strms - has been made accessible in the CLI.

Impact: For outbound streaming with sctp-max-out-strms, backward compatibility is maintained. For inbound streaming, the customer can configure the maximum number of streams, up to 16, to accommodate reception needs from the peer - hence stream negotiation is improved and complete.

Note:

To ensure backward compatibility, the CLI range from “17” to “65535” has been deprecated. If the user provides a value in the deprecated range, a warning message will be displayed.

ISR Deactivation Cause Value and Node Value Sent in Delete Session Request

Previous Behavior: When the Idle Mode Signaling Reduction feature was enabled on the S4-SGSN, and a UE initiated a GPRS Detach, the S4-SGSN was sending the Indication Flag IE to the SGW in the Delete Session Request.

New Behavior: In this scenario, the Indication Flag is no longer sent, Instead, the S4-SGSN sends the cause value (ISR Deactivation) and Node Type to the SGW in the Delete Session Request message.

License Control for Access-Type

Previous Behavior: Access-type keyword options "gprs" and "umts" for commands in the Call-Control Profile configuration mode were generally available.

New Behavior: The access-type options "gprs" and "umts" for commands in the Call-Control Profile configuration mode will only be accessible if the SGSN service license is installed.

License Control for Location Reporting

Previous Behavior: Some configuration commands related to Location Reporting functionality were available and configurable even if the appropriate license was not enabled.

New Behavior: The location-reporting command in the Call Control Profile configuration mode is now available and configurable only if the specified license is enabled.

License Control for S4-SGSN Configuration Commands

Previous Behavior: Some configuration commands related to S4-SGSN functionality were available and configurable even if the appropriate licenses were not enabled.

New Behavior: The following S4-SGSN configuration commands now are available and configurable only if the specified license is enabled:
Table 1. License Controlled Commands on the S4-SGSN
Command CLI Mode Required License

associate tai-mgmt-db

SGSN Service Configuration

SGSN S4 License

associate tai-mgmt-db

GPRS Service Configuration

SGSN S4 License

associate network-global-mme-id-mgmt-db

SGSN Service Configuration

SGSN S4 License

associate network-global-mme-id-mgmt-db

GPRS Service Configuration

SGSN S4 License

gmm t3323-timeout

SGSN Service Configuration

Idle Mode Signaling Reduction

idle-mode-signaling-reduction

Call Control Profile Configuration

Idle Mode Signaling Reduction

sgsn-core-nw-interface

Call Control Profile Configuration

SGSN S4 License



LORC Private Extension Included in DPCQ during Specific Scenarios

Previous Behavior: In scenarios similar to the one described below, where the SGSN locally deactivated a PDP context without informing the MS, then the SGSN (with LORC feature enabled) sent DPCQ to the GGSN without including the LORC private extension.

  • Precondition:
    • loss-of-radio-coverage ranap-cause 46 (in iups-service)
    • gtp private-extension loss-of-radio-coverage send-to-ggsn send-to-peer-sgsn (in apn-profile)
  • Scenario:
    • Attach in 3G.
    • Activate with background class.
    • Iu Release Request, Cmd.
    • UPCQ, DL data, UPCR.
    • Iu Release Complete, UPCR.
    • PTMSI attach in 3G.
    • Common Id, Security mode cmd, complete.
    • After Accept.
    • DPCQ, DPCR.

New Behavior: In scenarios similar to the one described above, where the SGSN locally deactivates a PDP context without informing the MS, then the SGSN (with LORC feature enabled) sends DPCQ, including the LORC private extension, to the GGSN

LORC IE Included in DPCQ Triggered by Inter-RAT RAU Rejects

Previous Behavior: In a scenario where the SGSN locally deactivates a PDP context without informing the MS, and when the LORC feature is enabled, the DPCQ sent to GGSN did not include the LORC private extension.

  • Precondition:
    • loss-of-radio-coverage ranap-cause 46 (in iups-service)
    • gtp private-extension loss-of-radio-coverage send-to-ggsn send-to-peer-sgsn (in apn-profile)
  • Scenario:
    • Attach in 3G (with access restriction for 3G)
    • Activate in 3G (with background class)
    • Iu Release Request, Cmd
    • UPCQ, DL data, UPCR
    • Iu Release Complete, DL Data
    • IRAT RAU in 2G
    • RAU Reject with cause 13
    • DPCQ

New Behavior: In this scenario the DPCQ sent to the GGSN now includes the LORC private extension.

Impact: The data count while the MS is in the LORC state is more accurate.

New S-CDR Field Support for custom33 Dictionary

Previous Behavior: The S-CDR field “SGSN Change” is not present in custom33 dictionary.

New Behavior: The S-CDR field “SGSN Change” has been included in custom33 dictionary. This field is the first record after an inter-SGSN routing area update. The field “SGSN Change” is populated in the custom33 dictionary by default. CLI support has been provided to disable this field. A new keyword sgsn-change is included in the command gtpp attribute to optionally disable the S-CDR field “SGSN Change” for custom33 dictionary. The keyword is license restricted.

Note:

For custom33 users, upgrading from pre-R14.0 release to R14.0 and higher releases it is recommended that this field is disabled before an upgrade to avoid billing issues.

For detailed information, refer to the Cisco ASR 5x00 GTPP Interface Administration and Reference manual.

NF capability decoding

Previous Behavior: The length of Spare bits in MS Network Capability is 2 bits and Decoding of NF Capability bit is absent. If the MS Network Capability bit is provided by the MS, NF Capability is not decoded in MS Network Capability in mon-pro as a part of GMM Message and Spare bits are Decoded as 2 bits. 2 bit Spare Bits are decoded instead of 1 bit NF Capability Bit Field and 1 bit Spare Bit Field.

New Behavior: Code changes are added to decode the NF Capability Bit under MS Network Capability octets. The Length of Spare bits in MS Network Capability is reduced to 1 bit from 2 bits, and decoding of 1 bit length value 'NF capability’ is added. NF Capability now is decoded in MS Network Capability.

PS Paging Change for Clear Subscribers All Command

Previous Behavior: In a certain scenario, subscribers were not cleared when the MS responded to a Paging Request from the SGSN. To authenticate the subscriber, the SGSN performed an SAI. If the SAI failed with type Network Failure, the SGSN re-initiated the Paging Request and did not clear the subscribers.

  • Precondition: A call-control-profile is created and configured with the authenticate service-request parameter.
  • Scenario:
    • Attach in 3G
    • IU Released
    • PMM-IDLE state
    • Execute the clear subscribers all command in Exec Mode
    • The SGSN pages the MS
    • The MS sends the Service Request with a type Paging Response
    • SAI response returned as SYSTEM FAILURE
    • The SGSN sends a service reject with a cause of Network Failure

New Behavior: The SGSN will not re-initiate the Paging Request if the SAI fails due to a Network Failure. The SGSN clears the subscribers with an Implicit Detach.

RAU Reject Cause Corrected when AIA and UGL with 5003

Previous Behavior: Authentication information is sent from the SGSN to the Diameter (HSS) and the Diameter returns an error code 5003 (DIAMETER_AUTHORIZATION_REJECTED). The SGSN rejects the call with an incorrect GMM cause code value "Network Failure".

New Behavior: As per 3GPP TS 29272 v9.7, the correct cause code to be sent in this scenario is "15 - No Suitable Cells In Tracking Area". The mapping has been corrected and the GMM cause now displays "No Suitable Cells In Tracking Area" when Diameter Returns reject cause as 5003 in both the cases AIA and UGL.

Support for IE "SubscriberProfileIDforRFP" in added Direct Tx Message

Previous Behavior: IE "SubscriberProfileIDforRFP" Cause Code:202, is not present in the Direct Tx Message, if MS provides a "SubscriberProfileIDforRFP", a Decode Error is displayed in Mon_Pro.

New Behavior: IE "SubscriberProfileIDforRFP" added in Direct Tx Message, if MS provides a "SubscriberProfileIDforRFP" it will be decoded in the Direct Tx message.

SGSN Configuration Management Changes as of September 28, 2012

This section provides information on SGSN configuration command changes in release 14.0.

IMPORTANT:

For more information regarding commands in this section, refer to the GPRS/UMTS Command Line Interface Reference for this release.

New SGSN Configuration Commands

This section identifies new SGSN commands available in release 14.0.

associate

New command associates the MAP service configured for the LCS with the Location Service configuration:

Location-Service Configuration Mode

[ no ] associate
map-service <map_serv_name> 

commandguard

New command prevents operators from accidentally entering configuration modes, via CLI or file replay, by enabling prompting for autoconfirm and configuration commands:

Global Configuration Mode

commandguard 
[ default | no ] commandguard

enb-direct-data-forward

A new command has been implemented to enable and disable the setup of indirect data forwarding tunnels (IDFT) between the eNodeB and the RNC via the SGW during connected mode handovers.

RNC Configuration Mode

enb-direct-data-forward 
no enb-direct-data-forward

gmlc

A new command identifies the gateway mobile location center (GMLC) for the SGSN when using Location Services.

MAP Service Configuration Mode

gmlc { isdn <E.164#> | point-code <point_code> } [ gsn-address <ipv4_address> ] [ source-ssn <ssn> ]
no gmlc { isdn <E.164#> | point-code <point_code>

interface-management

A new command enters the SGSN global interface management configuration mode:

SGSN-Global Configuration Mode

interface-management 

interface-management

A new command maps the interface management configuration to the NSE-ID or to an NSE-name to identify the peer NSE/BSC:

Interface Management Configuration Mode

[ no ] interface
gb peer-nsei id nsei_id name nsei_name

interface-management

A new command locks or shuts down the interface towards the NSE based on either the NSE-ID or the NSE-name. The “no” form of the command unlocks the interface towards the NSE/BSC.

Interface Management Configuration Mode

[ no ] lock-interface
gb peer-nsei { name nsei_name | id nsei_id } 

lcs-mo, lcs-mt, lcs-ni

3 new commands restrict or allow location requests (mobile-terminating, mobile-originating, or network-induced) by access-type and associate the LCS with operator policies for granular control

Call-Control Profile Configuration Mode

lcs-mo { allow | restrict } access-type { gprs | umts }
lcs-mt { allow | restrict } access-type { gprs | umts }
lcs-ni { allow | restrict } access-type { gprs | umts } 

location-services

A new command is used to create an instance of the location service configuration and to access the Location Service configuration mode.

Context Configuration Mode

location-services <loc_serv_name>
no location-services 

location-services

A new command is used to enable or ‘start’ the new Location Services (LCS) functionality on the SGSN. The negative form of the command can be used to disable or ‘stop’ LCS.

SGSN-Global Configuration Mode

location-services 
no location-services 

release-compliance

The release-compliance command is implemented to enable or disable the sending of EPS information in the Update GPRS Location (UGL) Request message to the HLR.

HLR Configuration Mode

release-compliance release-8
no release-compliance

sctp-max-in-strms

Enables the operator to determine the maximum number of inbound streams to receive from the peer.

PSP Configuration Mode

sctp-max-in-strms < max_in_strms
> 
default sctp-max-in-strms

timeout

New command configures the LCSN timer for the Location Service configuration:

Location-Service Configuration Mode

timeout lcsn <10-20> 

Modified SGSN Configuration Commands

This section identifies SGSN commands modified in release 14.0.

accounting

A new keyword lcs mt-cdr is included in the command accounting, this keyword is used to enable/disable the generation of LCS-MT-CDRs.

GPRS Service Configuration Mode

accounting { cdr-types { mcdr | scdr | sms { mo-cdr | mt-cdr } } | lcs { mt-cdr } | smbmscdr } + | context cntx_name }

SGSN Service Configuration Mode

accounting ( cdr-types { mcdr | scdr | sms { mo-cdr | mt-cdr } } | lcs { mt-cdr }  | smbmscdr } + | context  cntx_name  }

apn-selection-default

A new keyword lowest-context-id enables the operator to configure selection of the subscription APN with the least context-ID when the APN is not found in the subscription.

APN Remap Table Configuration Mode

[ no ] apn-selection-default { first-in-subscription | lowest-context-id | network-identifier <apn_net_id> } 

aps

The default keyword has been added to the aps command in this release.

Card Configuration Mode

default aps 

IMPORTANT:

default aps is the equivalent of entering aps 1+1 uni-directional non-revertive.

gtpc

A new keyword echo-retransmission and accompanying filters (exponential-backoff, min-timeout, smooth-factor, timeout) enable the operator to configure retransmission parameters for GTPC echo messages or to use system defaults by using the default keyword.

SGTP-Service Configuration Mode

gtpc echo-retransmission { exponential-backoff [ min-timeout <1-20> | smooth-factor <1-5> ] | timeout <1-20> } 
default gtpc echo-retransmission

gtpp attribute

A new keyword sgsn-change is included in the command gtpp attribute, this keyword is used to optionally disable the inclusion of the S-CDR field “SGSN Change” in custom33 dictionary. The keyword is license restricted, specific to SGSN and is enabled by default.

GTPP Server Group Configuration Mode

gtpp attribute { camel-info | cell-plmn-id | diagnostics | duration-ms | imei | local-record-sequence-number | msisdn | node-id-suffix STRING | plmn-id | rat | record-extensions rat | served-pdp-pdn-address-extension | sgsn-change |sms { destination-number | recording-entity | service-centre }  } +
default gtpp attribute { cell-plmn-id | diagnostics | duration-ms | imei | local-record-sequence-number | msisdn | plmn-id | rat | record-extensions rat | served-pdp-pdn-address-extension | sgsn-change |sms { destination-number | recording-entity | service-centre } }
no gtpp attribute { cell-plmn-id | diagnostics | duration-ms | imei | local-record-sequence-number | msisdn | node-id-suffix | plmn-id | rat | record-extensions rat | served-pdp-pdn-address-extension | sgsn-change |sms { destination-number | recording-entity | service-centre } }

Note:

For SGSN specific custom33 dictionary, it is recommended to disable this keyword before an upgrade to prevent billing issues.

gtpu

A new keyword echo-retransmission and accompanying filters (exponential-backoff, min-timeout, smooth-factor, timeout) enable the operator to configure retransmission parameters for GTP-U echo messages or to use system defaults by using the default keyword.

SGTP-Service Configuration Mode

gtpu echo-retransmission { exponential-backoff [ min-timeout <1-20> | smooth-factor <1-5> ] | timeout <1-20> } 
default gtpc echo-retransmission

local-cause-code-mapping

A new keyword, map-cause-code, configures the GMM reject cause code to send to a UE for map cause 'roaming not allowed'

Call-Control Profile Configuration Mode

local-cause-code-mapping
map-cause-code roaming-not-allowed gmm-cause-code gmm-cause
remove local-cause-code-mapping
map-cause-code roaming-not-allowed 

ns-timer

A new keyword, sns-guard, sets the wait time for the auto-learn procedure to complete proper clean-up of learnt BSC/NSE information.

Network Service Entity IP-Local Configuration Mode

 ns-timer sns-guard seconds
 default ns-timer sns-guard 

peer-mme

The fallback-for-dns keyword is now supported in the peer-mme command. Enabling this keyword enables the S4-SGSN to support fallback to the locally configured peer-mme address in the event a DNS query times out or fails.

Call Control Profile Configuration Mode

peer-mme mme-groupid <lac val> mme-code <rac value> prefer { fallback-for-dns | local } address { <ipv4_address> | <ipv6_address> } interface { gn [ s3 ] | s3 [ gn ] }

peer-mme

The CLI online help for this command has been modified. A warning has been added that informs the user that changing the currently configured prefer option for the same RAC and LAC via the peer-mme command overwrites the previously configured prefer setting for all interfaces.

ranap

A new keyword arp-ie is added to enable or disable the inclusion of ARP-IE in RAB assignment / Relocation request RANAP messages per RNC.

RNC Configuration Mode

[ default | no ] ranap
arp-ie 

rau-inter

New keyword makes it possible to configure the SGSN to ignore the peer’s context-ID and replace with PDP context-ID information based on the HLR subscription.

Call-Control Profile Configuration Mode

[ default | no ] rau-inter
ignore-peer-context-id

sgsn imsimgr

Session Manager instance ranges have been modified from a maximum of 4095 to a maximum of 384:

Exec Mode

sgsn imsimgr audit-with
sessmgr instance <1 - 384>

sgsn imsimgr

Session Manager instance ranges have been modified from a maximum of 4095 to a maximum of 384:

Exec Mode

sgsn imsimgr add-record <integer> sessmgr instance <1 - 384>

sctp-max-out-strms

The system has always capped the maximum number of outbound SCTP streams at 16 and now the configurable range (1 - 16) has been modified to accommodate the cap.

PSP Configuration Mode

sctp-max-out-strms < max_in_strms
> 
default sctp-max-out-strms

Note:

To ensure backward compatibility, the CLI range from “17” to “65535” has been deprecated. If the user provides a value in the deprecated range, a warning message will be displayed.

sgsn-address

The fallback-for-dns keyword is now supported. Enabling this keyword enables the S4-SGSN to support fallback to the locally configured peer-sgsn address in the event a DNS query times out or fails.

Call Control Profile Configuration Mode

sgsn-address rac <rac-id> lac <lac_id> [  nri <nri> ]  prefer { fallback-for-dns | local } address { ipv4 <ip_address> | ipv6 <ip_address> } interface { gn | s16 }

sgsn-address

The CLI online help for this command has been modified. A warning has been added that informs the user that changing the currently configured prefer option for the same RAC and LAC via the sgsn-address command overwrites the previously configured prefer setting for all interfaces.

Deprecated SGSN Configuration Commands

This section identifies SGSN commands deprecated in release 14.0.

aps

The no keyword for the aps command has been deprecated in this release.

Card Configuration Mode

no aps 

IMPORTANT:

To disable APS, use the redundancy port-mode command in the Card Configuration Mode.

authenticate detach

The CLI syntax for the command authenticate detach in the call-control-profile configuration mode is modified to configure the authentication procedure during detach only for UMTS access type. The “gprs” option is deprecated and no longer valid.

Call Control Profile Configuration Mode

[ no | remove] authenticate
detach [ access-type { umts | gprs } ]

SGSN Performance Management Changes as of September 28, 2012

New SGSN Bulk Statistics

This section identifies new SGSN bulk statistics available in release 14.0.

None in this release.

Modified SGSN Bulk Statistics

This section identifies modified SGSN bulk statistics available in release 14.0.

None in this release.

Deprecated SGSN Bulk Statistics

This section identifies SGSN bulk statistics deprecated in release 14.0.

None in this release.

New SGSN Performance Commands

This section identifies new SGSN performance commands available in release 14.0.

show location-service

A new show command displays configuration for the Location Service parameters.

Exec Mode

show location-service
service { all | name <loc_serv_name> } 

Modified SGSN Performance Commands

This section identifies modified SGSN performance commands available in release 14.0.

show call-control-profile full all

The show call-control-profile full all command output has been modified to provide the configured DNS context associations for the PGW and SGW for the S4-SGSN.

Exec Mode

show call-control-profile
full all

show cdr statistics

The output of this Exec mode command has been modified to include two new statistics:

  • Number of files pending transfer: This statistic represents number of files that are present in the directory "/records/***" waiting to be transferred to the remote server.
  • Number of files queued transfer: This statistic represents the number of files that are currently queued to transfer to the remote server.

Exec Mode

show cdr statistics

Note:

The Context Configuration Mode edr-module active-charging-service has to be configured before executing the show cdr statistics command.

show configuration

The show configuration command with keywords verbose and context name has been enhanced to include LCS-MT-CDR information. LCS-MT-CDR is a new accounting CDR type introduced to support the LCS feature.

The parameter ranap arp-ie is displayed in the show configuration output, if inclusion of ARP-IE in RAB assignment / Relocation request RANAP messages per RNC is enabled.

The parameter no ranap arp-ie is displayed in the show configuration output, if inclusion of ARP-IE in RAB assignment / Relocation request RANAP messages per RNC is disabled.

Exec Mode

show configuration verboseshow configuration context nameshow configuration context name verbose

show gmm-sm statistics

SGW Change Statistics were placed in the output of the show show gmm-sm statistics command. These statistics have been removed. The equivalent SGW relocation change statistics were already available, and remain, in the output of the show s4-sgsn statistics command.

Exec Mode

show gmm-sm statistics

The SGW Change Statistics that were removed from the show gmm-sm statistics output are:

  • SGW Change Statistics
  • Total S-GW Changes
  • 3G SGW Changes
  • Intra RAU (3G)
  • Inter SGSN RAU over S16 (3G)
  • MME-SGSN RAU over S3 (3G)
  • 2G SGW Changes
  • Intra Rau (2G)
  • Inter SGSN RAU over S16 (2G)
  • MME-SGSN RAU over S3 (2G)

As noted above, The equivalent SGW relocation change statistics are still available in the output of the show s4-sgsn statistics command.

Exec Mode

show s4-sgsn statistics
...  ...  ...
S4 SGSN Statistics Summary:
   SGW Relocations :
      3G Intra SGSN RAU        :
0    2G Intra SGSN RAU       :
0
      3G
Inter SGSN RAU (S16)  : 0    2G
Inter SGSN RAU (S16) : 0
      3G
MME-SGSN RAU (S3)     :
0    2G MME-SGSN RAU (S3)    :
0
      Intra SGSN 2G to 3G
RAU  : 0    Intra
SGSN 3G to 2G RAU : 0
...  ...  ...

show gmm-sm statistics

New counters have been added to the output of this command to track attempted and successful SRNS relocations between SGSNs and MMEs.

Exec Mode

show gmm-sm statistics

show gmm-sm statistics verbose

New inter-GPRS Service and inter-RAT / RAU / FSM counters expand RAU failure and internal failure statistics. Some counters were removed to avoid confusion regarding internal failures.

The following is a list of new counters:

  • Inter GPRS Srv Rau Requests:
  • Inter GPRS Srv Rau Accepts:
  • Inter GPRS Srv Rau Failures:
  • Inter GPRS Srv Rau Success:
  • No Matching Sgtp Service:
  • No Matching Map Service:
  • Inter RAT Requests
  • Inter RAT Accepts:
  • Inter RAT Failures
  • Inter RAT Success

The following is a list of removed counters:

  • Alloc SMID Failed:
  • Insert SMID Failed:
  • No Sgtp inst:
  • No Map inst:
  • Inter RAT Requests:

show gmm-sm statistics verbose

The command show gmm-sm statistics verbose displayed incorrect counters when a 3G to 2G IRAT is performed. The counter names have been changed.

"Radio-status-bad before a" changed to "Radio-status-bad before auth"

"Radio-status-bad after au" changed to "Radio-status-bad after auth”

Exec Mode

show gmm-sm statistics verbose

show gprsns statistics

New stats peg the number of NS-UNITDATA packets received over an inactive NSVC link and handled by the SGSN. Stats are pegged for facility sessmgr and linkmgr.

New counter “Number of udata handled in inactive state” displays when the command includes the msg-stats nse <nse> keywords and either the facility linkmgr all or the facility sessmgr all keywords.

Exec Mode

show gprsns statistics
msg-stats nse <nse> facility linkmgr allshow gprsns statistics
msg-stats nse <nse> facility sessmgr allshow gprsns statistics
msg-stats consolidated nse <nse>

show gprs-service all

The show gprs-service all command has been enhanced to include LCS-MT-CDR information. LCS-MT-CDR is a new accounting CDR type introduced to support the LCS feature.

Exec Mode

show gprs-service all

show gtpp counters

The output of this command is enhanced to include new counters related to LCS-MT-CDRs. The updated output is obtained when the command is used with the keywords all, group name group_name and cgf_address cgf_address.

Exec Mode

show gtpp counters allshow gtpp counters group
name group_nameshow gtpp counters cgf-address cgf_address

show gtpp statistics

The output of this command is enhanced to include new counters related to LCS-MT-CDRs. The updated output is obtained when the command is used with the keywords group name group_name, cgf_address cgf_address, debug-info and verbose debug-info.

Exec Mode

show gtpp statisticsshow gtpp statistics
group name group_nameshow gtpp statistics
cgf-address cgf_addressshow gtpp statistics
debug-infoshow gtpp statistics
verbose debug-info

show gtpp storage-server

The output of this command is enhanced to include new counters related to LCS-MT-CDRs. The updated output is obtained when the command is used with the keywords group name group_name and verbose.

Exec Mode

show gtpp storage-server statisticsshow gtpp storage-server
statistics verboseshow gtpp storage-server
group name group_name

show iups-service name

A new field, E-NodeB Direct Data Forwarding, has been added to the output of the show iups-service name command to indicate whether eNodeB direct data forwarding is enabled or disabled. If the field reads Disabled, the S4-SGSN uses indirect data forwarding tunnels (IDFT).

Exec Mode

show iups-service name <service_name>

show llc status

Session Manager instance ranges have been modified from a maximum of 4294967295 to a maximum of 384:

Exec Mode

show llc status gprs-service
<variable> sessmgr instance <1 - 384>

show map-service all

The field 3GPP Release Compliance has been added to the show map-service all command output to indicate the configured 3GPP release compliance setting. The 3GPP release compliance setting is configured with the release-compliance command in HLR Configuration Mode.

Exec Mode

show map-service all

show s4-sgsn statistics all

More granularity has been provided in the command output so that ISRAUs across both the S16 and S3 interfaces are tracked individually for SGW relocations. Formerly, only one counter tracked both interfaces.

Exec Mode

show s4-sgsn statistics all

show s4-sgsn statistics all

The command output has been modified to show packet and byte queued and dropped statistics for the S4-SGSN. These statistics are provided in the GTPU Statistics section of the output.

Exec Mode

show s4-sgsn statistics all

show s4-sgsn statistics all

A new section, IDFT Statistics, has been added to the command output to provide counters that track the number of indirect data forwarding tunnel (IDFT) packets and bytes sent to and from the SGW.

Exec Mode

show s4-sgsn statistics all

show s4-sgsn statistics all

The output of this command has been enhanced to provide statistics related to the Inter- and Intra SGSN SRNS feature, including:

  • Intra- and Inter-SGSN SRNS relocation counters added to the SGW Relocation Statistics output section.
  • SRNS procedure abort counters in the new Procedure Abort Statistics output section.

show session subsystem

The show session subsystem command with the keyword facility has been enhanced to include LCS-MT-CDR information. LCS-MT-CDR is a new accounting CDR type introduced to support the LCS feature. New LCS-MT-CDR related counters are provided.

Exec Mode

show session subsystem [ full | facility facility [ all | instance id ] ] [ verbose ] [ | { grep grep_options | more }]

show sgsn-fast-path statistics

Session Manager instance ranges have been modified from a maximum of 65535 to a maximum of 384:

Exec Mode

show sgsn-fast-path
statistics smgr-instance  <1 - 384>

show sgsn sessmgr memory statistics

The output of this command has been enhanced to provide memory allocation information for the PDN bundle level bearer information required during 3G PGW Initiated PDP Bearer Modification.

Exec Mode
show sgsn sessmgr instance <instance number> memory statistics
...  ...  ...
|------------------------------------------------------------------|
        SGSN-specific
Memory Statistics
|------------------------------------------------------------------|
| Entity     |   Blk User          | blkSize | numAlloc | numFree
 |
|------------------------------------------------------------------|
...  ...  ...
| SM
App    |   S4 PDN TransCb     | 20      |   0      | 409      |
...  ...  ...

show sgsn-service all

Exec Mode

The show sgsn-service all command has been modified to correctly output the configured GMM T3323-timeout setting in minutes. Previously, the output identified the setting in units of seconds.

The show sgsn-service all command has been enhanced to include LCS-MT-CDR information. LCS-MT-CDR is a new accounting CDR type introduced to support the LCS feature.

Exec Mode

show sgsn-service all

show subscribers gprs-only full all

In the PDN Gateway section of the show subscribers gprs-only full all command, the Name field has been changed to FQDN and the FQDN field now shows both the configured destination-host and destination-realm for the subscribed FQDN. The FQDN is a concatenation of these two items. The FQDN is a concatenation of both the destination-host and destination-realm.

Exec Mode

show subscribers gprs-only
full all all

show subscribers sgsn-only full all

In the PDN Gateway section of the show subscribers sgsn-only full all command, the Name field has been changed to FQDN and the FQDN field now shows both the destination host and destination realm for the subscribed FQDN.

Exec Mode

show subscribers sgsn-only
full all all

Deprecated SGSN Performance Commands

This section identifies SGSN performance commands deprecated in release 14.0.

SGSN Security Management Changes as of September 28, 2012

This section provides information on SGSN security management changes in release 14.0.

SGSN Feature Changes as of July 31, 2012

This section provides information on SGSN feature changes in release 14.0.

IMPORTANT:

For more information regarding features in this section, refer to the ASR 5000 Serving GPRS Support Node Administration Guide for this release.

New SGSN Features

This section identifies SGSN features new in release 14.0.

None for this release.

Modified SGSN Features

This section identifies SGSN features modified in release 14.0.

Holding Iu Established via Service Request

Previous Behavior: For an Iu established as the result of a Service Request (signaling), the SGSN would not wait for the iu-hold-timer to expire (unless “iu-hold-connection always” is configured). The SGSN would immediately release the Iu after any SM/SMS activity completes. If the Iu were established by an RAU/Attach, the SGSN would consult the “follow-on-req” bit in the RAU-Request/Attach-Request message. As this bit is not part of the Service Request message, the SGSN assumed that the MS just has a single activity to complete, and hence, the SGSN would release the Iu after any activity (SM/SMS) completed.

New Behavior: The SGSN now waits until the iu-hold-timer expires before releasing the Iu. In addition, this behavior is controllable via a new CLI command, refer to section New SGSN Configuration Commands for syntax details.

SGSN Configuration Management Changes as of July 31, 2012

This section provides information on SGSN configuration command changes in release 14.0.

IMPORTANT:

For more information regarding commands in this section, refer to the GPRS/UMTS Command Line Interface Reference for this release.

New SGSN Configuration Commands

This section identifies new SGSN commands available in release 14.0.

service-request-follow-on

New command instructs the SGSN (by default) not to release an Iu immediately but to wait for the Iu-Hold-Timer expiry. A negative command would disable this function.

IuPS Service Configuration Mode

service-request-follow-on[ default | no ] service-request-follow-on

Modified SGSN Configuration Commands

This section identifies SGSN commands modified in release 14.0.

random-value-in-iov-ui

New keyword in the llc command enables the SGSN to send random IOV-UI values, with zeros sent as the IOV-UI value in the XID messages by default.

GPRS Service Configuration Mode

llc random-value-in-iov-ui 
[ default | no ] llc
random-value-in-iov-ui

Deprecated SGSN Configuration Commands

This section identifies SGSN commands deprecated in release 14.0.

None in this release.

SGSN Performance Management Changes as of July 31, 2012

This section provides information on SGSN performance management changes in release 14.0.

IMPORTANT:

For more information regarding bulk statistics in this section, refer to the Statistics and Counters Reference for this release.

For more information regarding commands in this section, refer to the UMTS Command Line Interface Reference for this release.

New SGSN Bulk Statistics

This section identifies new SGSN bulk statistics available in release 14.0.

None in this release.

Modified SGSN Bulk Statistics

This section identifies modified SGSN bulk statistics available in release 14.0.

None in this release.

Deprecated SGSN Bulk Statistics

This section identifies SGSN bulk statistics deprecated in release 14.0.

None in this release.

New SGSN Performance Commands

This section identifies new SGSN performance commands available in release 14.0.

None in this release.

Modified SGSN Performance Commands

This section identifies modified SGSN performance commands available in release 14.0.

show gmm-sm statistics

The output of this Exec mode command has been modified to display appropriate reasons for PDP overrides with the following new fields/counters:

  • 2G Call Control Profile IPv4v6 PDP Type Override Statistics
  • Successful override to IPv4:
  • IPv4 activation success after Override:
  • Pv4 activation failure after Override:
  • Successful override to IPv6:
  • IPv6 activation success after Override:
  • IPv6 activation failure after Override:
  • IPv6 activation failure after Override:
  • Successful override to IPv4:
  • IPv4 activation success after Override:
  • IPv4 activation failure after Override:
  • Successful override to IPv6:
  • IPv6 activation success after Override:
  • IPv6 activation failure after Override:

show gmm-sm statistics gprs-service <gprs-name> nsei <nsei-id>

The output of this Exec mode command has been modified to provide enhanced details for attach failures per NSEI with new fields/counters:
  • Inter RAT PS Only Routing Area Update Failure Causes
    • 2G-Failure due to Other Ongoing Procedure
  • Inter RAT Comb. Routing Area Update Failure Causes:
    • 2G-Failure due to Other Ongoing Procedure:
  • Intra Ra-Upd Routing Area Update Failure Causes:
    • 2G-Failure due to Other Ongoing Procedure:
  • Intra Combo. Routing Area Update Failure Causes:
    • 2G-Failure due to Other Ongoing Procedure:
  • Intra Periodic Routing Area Update Failure Causes:
    • 2G-Failure due to Other Ongoing Procedure:
  • Inter SGSN PS Only Routing Area Update Failure Causes:
    • 2G-Failure due to Other Ongoing Procedure:
  • Inter SGSN Comb. Routing Area Update Failure Causes:
    • 2G-Failure due to Other Ongoing Procedure:
  • Inter-System Attach Statistics
    • 2G-Attach
    • 2G-Comb-Attach:
    • 2G-Attach-Rej:
    • 2G-Comb-Attach-Rej
    • 2G-Attach-Acc
    • 2G-Comb-Attach-Acc
  • Gprs-Attach Failure Causes:
    • 2G-Failure Due to Other Ongoing Procedure:
  • Comb-Attach Failure Causes:
    • 2G-Failure Due to Other Ongoing Procedure:
  • GPRS FSM Attach Statistics:
    • Attach Failures:
  • Inter Service PS Only Routing Area Update Failure Causes:
    • 2G-Failure due to Other Ongoing Procedure:
  • Inter Service Comb. Routing Area Update Failure Causes:
    • 2G-Failure due to Other Ongoing Procedure:
  • GPRS FSM Total RAU Statistics:
    • RAU Failures:
  • Authentication And Ciphering Response With SRES Mismatch:
    • Total-Auth-Cipher-Resp with Sres Mismatch:
    • 2G-Auth-Cipher-Resp with Sres Mismatch:
  • Authentication And Ciphering Reject:
    • Total-Auth-Cipher-Rej
    • 2G-Auth-Cipher-Rej
  • Authentication and Ciphering Reject Reasons:
    • 2G-XRes Mismatch
    • 2G-Too many SYNC Failures:
    • 2G-Too many MAC Failures:
    • 2G-Gsm Auth Unacc:

show gprs-service all

The output of this Exec mode command has been modified to track configuration for sending random IOV-UI values in XID messages with the following new fields/counters:

  • GMM accept procedure : old tlli
  • LLC IOVUI in xid-reset : send
  • LLC IOVUI val in xid-reset: Random value
  • LLC Reset VUR during intra RAU : Disabled
  • LLC detect overflow : Disabled

Deprecated SGSN Performance Commands

This section identifies SGSN performance commands deprecated in release 14.0.

None in this release.

SGSN Security Management Changes as of July 31, 2012

This section provides information on SGSN security management changes in release 14.0.

None for this release.

SGSN Feature Changes as of June 29, 2012

This section provides information on SGSN feature changes in release 14.0.

IMPORTANT:

For more information regarding features in this section, refer to the ASR 5000 Serving GPRS Support Node Administration Guide for this release.

New SGSN Features

This section identifies new SGSN features available in release 14.0.

2G and 3G Inter -PLMN Intra-RAU Support on the S4-SGSN

The S4-SGSN supports 2G and 3G inter- and intra-PLMN intra RAU procedures. However, if the new PLMN’s operator policy is configured to use the Gn interface, the PDP contexts are not transferred from the S4 interface to the Gn interface. In addition, the S4-SGSN currently does not support the association of a different EGTP service for each PLMN.

2G and 3G Routing Area Update Support on the S4-SGSN

The S4-SGSN supports outbound Routing Area Update (RAU) procedures for a subscriber already attached on that SGSN (that have PDP contexts anchored through S4 interface) and inbound RAU procedures for an EPC capable UE.

The following RAU procedures are supported for both 2G and 3G services:

  • 2G and 3G Intra-SGSN RAU with and without S-GW relocation
  • 2G and 3G Inter-SGSN/SGSN-MME RAU with and without S-GW relocation across S16 and S3 interfaces
  • Intra-SGSN Inter-RAT RAU with and without S-GW relocation

Accounting Path Framework, New

The SGSN uses a new accounting path framework to support PSC3 numbers of 8 million attached subs and 16 million PDP contexts. In the old accounting path framework, there was one AAA session per sub-session in the Session manager and one archive session per sub-session in AAA manager. As part of the new accounting path framework there is only one AAA session per call in the Session manager and one archive session per call in the AAA manager. Also, there is an additional accounting session in the Session manager and the AAA manager per sub-session. The new accounting path framework improves memory and CPU utilization and prevents tariff or time limit delay. There are no changes in the CLI syntax to support the new accounting path and the existing accounting behavior of SGSN is not modified.

ASCII S-CDR Format Support

The SGSN supports a new custom dictionary (custom41) that is based on custom6. The new custom41 generates the S-CDR in ASCII format for post-processing by the external mediation server. For detailed information, refer to the Cisco ASR 5x00 GTPP Interface Administration and Reference.

CLI Control of Gr or S6d Interface Selection on the S4-SGSN

The S4-SGSN supports control over the selection of the S6d (Diameter) or legacy Gr interface for PDP context operations. This allows flexible operator control over interface selection for operational or administrative reasons. This feature overrides any other criteria for the selection of the P-GW or GGSN for PDP contexts. This feature is applicable only for EPC-capable UEs.

New CLI commands have been introduced to support this feature.

Custom GUTI Mapping Support on the S4-SGSN

The S4-SGSN supports the configuration of a custom list of MME group IDs for operators with networks that have been configured with LACs in the 32768-65535 range for UMTS and GPRS coverage.

Once valid MME group codes are configured, the S4-SGSN uses them to identify whether the received LAC is a native LAC or a LAC mapped from a globally unique temporary UI identifier (GUTI); i.e., an MME group code that is part of a GUTI.

A new CLI command has been introduced to support this feature.

Deactivation Procedure Support on the S4-SGSN

The S4-SGSN supports the following deactivation procedures:

  • 3G / 2G MS initiated bundle deactivation
  • 3G / 2G MS initiated dedicated bearer deactivation
  • 3G / 2G P-GW initiated dedicated bearer deactivation
  • 3G / 2G P-GW initiated PDN deactivation

DNS Support on the S4-SGSN

By default, the S4-SGSN supports the initiation of a DNS query after APN selection using a S-NAPTR query. The S4-SGSN resolves a P-GW by sending an APN-FQDN query to the DNS client. Similarly, the S4-SGSN resolves the S-GW by sending a RAI-FQDN query to the DNS client. The DNS Client then sends a query to the DNS server to retrieve NAPTR/SRV/A records and return the S-GW or P-GW IP address to the SGSN.

To perform a DNS SNAPTR query, the SGSN requires an additional, optional, configuration that identifies the context where DNS lookup for EPC-capable UEs must occur. This is accomplished by creating a call-control-profile that specifies the context from which the DNS client should be used for resolving a co-located P-GW/GGSN address on a Gn SGSN as well

New CLI commands have been introduced to support this feature.

DSCP Marking of Control Packets for Gb and Iu Interfaces

The SGSN now supports a mechanism for differentiated services code point (DSCP) marking of control packets and signaling messages at the SGSN’s M3UA level on Iu interfaces and LLC messages for the Gb interface.

This DSCP marking feature enables the SGSN to perform classifying and managing of network traffic and to determine quality of service (QoS) for the interfaces to an IP network. Implementation of this feature requires the use of several existing, modified and new CLIs.

  1. Use the dscp-template command in the SGSN Global configuration mode to create a new template or to access an existing DSCP template.
  2. Use the commands in the DSCP Template configuration mode to define DSCP marking for data packets and control packets.
  3. Use modified and new commands to associate the DSCP template at the
    • GPRS service level
    • Peer-NSE level
    • IuPS service level
    • PSP instance level

Forcing UE to a Particular SGSN in Iu/Gb Flex Pool

3GPP TS 23.236 defines pooling of SGSNs and the ability to offload subscribers from one SGSN to another within the pool. This proprietary enhancements allows an SGSN to offload on a per-subscriber basis (IMSI) and can force the selected IMSI to offload to a specific SGSN (Target NRI). The maximum number of IMSI that can be off-loaded at one time is 256.

Idle Mode Signaling Reduction Support on the S4-SGSN

The S4-SGSN supports the license-enabled idle mode signaling reduction (ISR) feature. The ISR feature enables a UE to be registered in both UTRAN and GERAN networks at the same time it is registered in the E-UTRAN network. To activate the ISR feature, for a UE, ISR functionality must be supported in both the UE and the SGSN, MME, S-GW and HSS.

New CLI commands are introduced to enable and configure this feature.

Ignoring/Rejecting Secondary PDP Request from UE

It is now possible for the SGSN administrator to configure the operator policy’s IMEI profile to either ignore or reject Secondary PDP Requests from UEs based on an IMEI range.

Local Configuration of P-GW Address on the S4-SGSN

The S4-SGSN provides support for the local configuration of a P-GW to obtain its address for operators wishing to bypass DNS resolution of APN FQDN for obtaining a P-GW address.

A new CLI command has been introduced to support this feature.

Local Configuration of an S-GW Address per RAI on the S4-SGSN

The S4-SGSN supports the option to configure a local S-GW address for a RAI (LAC, RAC, MCC and MNC). The S4-SGSN will select this address based on the configured local policy. The local policy can also be configured to allow the selection of the locally configured S-GW address when the DNS lookup fails. Local selection of the S-GW address applies in the following scenarios:

  • First PDP context activation for a subscriber
  • Intra SGSN routing area update
  • New SGSN routing area update
  • Intr inter RAT handover
    New CLI commands have been introduced to support this feature.

Location Change Reporting

3G/2G Location Change Reporting on the SGSN facilitates location-based charging on the GGSN by providing the UE’s location information when the UE is in connected mode. The SGSN notifies the GGSN whenever one of the following changes:

  • the serving cell global identity (CGI), or
  • the service area identity (SAI), or
  • the routing area identity (RAI).

Mobility Management Procedure Support on the S4-SGSN

The S4-SGSN supports the following mobility management procedures over the S6d (Diameter) and Gr interfaces:

  • Attach
  • Service request
  • Detach
  • Iu-Release procedures
  • Operator policy override for the Gn/S4 interface for EPC subscribers
  • Zone code
  • ARD
  • ADD
  • Operator policy-based Mobility Management context handling

MS Initiated Primary Secondary Activation Procedure Support on the S4-SGSN

The S4-SGSN supports default and dedicated bearer activation for:

  • Default and dedicated activation secondary PDP procedure trigger from MS).
  • Lawful Intercept activation rejects and failures
  • Dual stack PDP handling
  • APN-selection as per annex A.2/Spec 23.060 rel-9

Multi-Services Support on CLC2

With Release 14.0, the CLC2 is now able to support simultaneously multiple services through the same optical port - such as Frame Relay and MTP2. The service configuration is done at the path level and each path will correspond to one of the possible services.

P-GW Initiated Bearer Deactivation on the S4-SGSN

The S4-SGSN supports the P-GW initiated PDP deactivation procedure in addition to the legacy MS initiated deactivation procedure.

PSC3 Support

As Part of PSC3 support, in Release 14.0 the SGSN now supports 8M attached subscribers and 16M PDP contexts. This enhanced support applies only to PSC3 with 14.0. For PSC2 with 14.0, the previous support numbers of 4M attached subscribers and 8M PDP contexts still applies.

P-TMSI Scaling Support for PSC3 Cards

Previous Behavior: All P-TMSIs were allocated from a single pool.

New Behavior: Each P-TMSI will be allocated from a specific NRI pool. To facilitate this new default behavior, the no nri command has been deprecated from both the GPRS Service and SGSN Service configuration modes (refer to the sections for Deprecated SGSN Configuration Commands for details.

In support of the new default behavior for P-TMSI scaling for PSC3 cards, the nri command structure in the GPRS Service and the SGSN Service configuration modes has been modified, refer to the section for Modified SGSN Configuration Commands for details.

New statistics have been added to aid in monitoring NRI requirements, refer to the show sgsn sessmgr command in the section on Modified SGSN Performance Commands for details.

IMPORTANT:

To ensure backward compatibility of the configuration file, pre-14.0 configuration files will have the no nri configuration treated as if NRI length 6 with NRI value of 0 was configured.

QoS Mapping Support on the S4-SGSN

The S4-SGSN supports the configuration of quality of service (QoS) parameters as call-control-profiles that will ensure proper QoS mapping between the S4-SGSN and the EPC UEs.

The configured call-control-profiles will be used if the S4 interface is chosen for PDP activation, but the subscription does not have an EPS subscription. Therefore, GPRS subscription data (which uses QoS in pre-release 8 format), will be mapped to EPS QoS behavior. The Allocation and Retention policy will be mapped to EPS ARP using the configured call-control-profiles.

New CLI commands have been introduced to support this feature.

Restricting Activation Based on PDP-Type

Administrative controls for the SGSN have been enhanced so that PDP context activation can be restricted based on the type of PDP requested. For an operator policy’s call control profile, restrictions can be specified for a single PDP-type or for multiple PDP-types and the restriction can be further fine-tuned by network access type.

S13’ Interface Support on the S4-SGSN

In addition to the MAP-based Gf interface, the S4-SGSN supports the DIAMETER based S13’ (S13 prime) interface towards the Equipment Identify Registry. The S13’ interface enables the S4-SGSN to perform the ME Identity Check procedure to validate the IMEI with the EIR.

S13’ interface support is a license-enabled feature.

New CLI commands have been introduced to support this feature.

S3 Interface Support on the S4-SGSN

A signaling interface from the S4-SGSN to the MME in the EPC network is now supported over the S3 interface. This interface provides a GTV2 signaling path connection between the S4-SGSN and the MME for S4-SGSN-to-MME RAU / TAU context handovers.

S4-SGSN Support

Support for S4-SGSN functionality has been added to the SGSN to enable connectivity of subscribers to the EPC core network when accessing through UMTS/GPRS. The S4-SGSN is a license- enabled feature, and the license also provides support for the S3 signaling interface to the MME.

The S4-SGSN supports control and bearer separation, and off loads the backward compatibility requirement from the MME and S-GW elements to the UMTS core.

Comprehensive S4-SGSN support also includes support for these additional interfaces to the following network elements and gateways:

  • S-GW via the S4 interface (base feature of the S4 license)
  • Equipment Identity Registry (EIR) via the S13’ interface (additional feature license required)
  • Home Subscriber Server (HSS) via the S6d interface (additional feature license required)
  • MME via the S3 interface (base feature of the S4 license)
  • Peer S4-SGSN via the S16 interface (base feature of the S4 license)

S6d Interface Support for the S4-SGSN

The S4-SGSN supports the DIAMETER-based S6d interface to the HSS, in addition to the legacy Gr interface to the HLR (for the Gn/Gp SGSN). This license-enabled feature enables operators to consolidate the HLR/HSS functions into a single node. The SGSN selects the Gr interface / S6d interface based on the MAP or HSS service associated with the configured SGSN and/or GPRS services.

In addition, the S4-SGSN sets the following initiate UGL messages on a change of HSS service:

  • Initial attach indicator bit in Update GPRS Location message, ISR information IE, if the UGL is sent for an initial attach or for a inbound routing area update without ISR activation and the selected interface is Gr.
  • Initial attach indicator bit in Update Location Request message, ULR flags, if the ULR is sent for an initial attach or for a inbound routing area update without ISR activation and the selected interface is S6d.
    New CLI commands have been introduced to support this feature.

S-GW and P-GW Tunnel and Subscription Recovery on the S4-SGSN

The S4-SGSN supports session recovery procedures and recovers the S4 tunnel created for each subscriber assigned PDP contexts through S4 interface.

This functionality is part of session recovery procedures and allows sessions to be reconstructed when the system recovers from a card-level software fault.

Statistics Support for the S4-SGSN

Bulk statistics support has been implemented for the S4-SGSN. System and SGSN schemas have been enhanced, and EGTPC schema bulk statistics support has been introduced to provide information and statistics related to S4-SGSN functionality.

UE Requested Service Request Procedure Support on the S4-SGSN

The S4-SGSN supports the UE requested Service Request procedure as defined in section 6.12.1A of TS 23.060 v8.10.0.

UMTS/GSM AKA Support for the S4-SGSN

The S4-SGSN provides support for the following UMTS/GSM Authentication and Key Agreement (AKA) procedures:

  • SRNS
  • Attach
  • PTMSI attach (foreign/local)
  • Service Request
  • Inter SGSN RAU
  • Timers Handling
  • Re-use of Vectors
  • Using Peer SGSN/MME vectors (ISRAU/PTMSI attach) in the same or different PLMN

Modified SGSN Features

This section identifies SGSN features modified in release 14.0.

Backwards Compatibility

IMPORTANT:

Configuration files created with Release 14.0 will not be downgradable.

With release of 14.0, several commands have been deprecated and replaced by similar commands. These changes were made to ensure the configurations would be compatible with potential product combinations such as the SGSN/MME.

If your system is running pre-14.0 software, we recommend that prior to upgrading to 14.0 you copy the configuration file and store the copy off the chassis for possible use if a downgrade is required.

Configuration files created with releases prior to 14.0, that use the deprecated commands, will automatically be converted using the new form of the commands required for release 14.0.

The table below provides a mapping between the deprecated (pre-14.0) commands, used for associating various services with GPRS and SGSN services, and their release 14.0 equivalents.
Table 2. 14.0 Deprecated/Replacement Commands
Deprecated Command New Equivalent in Release 14.0

SGSN Service Configuration Mode

SGSN Service Configuration Mode

associate-service egtp <service_name> context <context_name>

associate egtp-service <service_name> context <context_name>

associate-service hss-peer-service <service_name> context <context_name>

associate hss-peer-service <service_name> context <context_name>

camel-service <service_name> context <context_name>

associate camel-service <service_name> context <context_name>

gs-service <service_name> context <context_name>

associate gs-service <service_name> context <context_name>

mobile-application-part service <service_name> context <context_name>

associate map-service <service_name> context <context_name>

sgtp-service <service_name> context <context_name>

associate sgtp-service <service_name> context <context_name>

.

GPRS Service Configuration Mode

GPRS Service Configuration Mode

associate-dscp-template downlink <template_name>

associate dscp-template downlink <template_name>

associate-service camel <service_name> context <context_name>

associate camel-service <service_name> context <context_name>

associate-service egtp <service_name> context <context_name>

associate egtp-service <service_name> context <context_name>

associate-service gs <service_name> context <context_name>

associate gs-service <service_name> context <context_name>

associate-service hss-peer-service <service_name> context <context_name>

associate hss-peer-service <service_name> context <context_name>

associate-service map <service_name> context <context_name>

associate map-service <service_name> context <context_name>

associate-service sgtp <service_name> context <context_name>

associate sgtp-service <service_name> context <context_name>



Configurable Support for Extended RNC ID

Corrected Content: This section includes corrections to previously published content. The previous content stated that the “Extended RNC ID expands the ID range from 1 - 4096 to 1 - 65535” which is incorrect.

In accordance with 3GPP TS 29.060, v9.2.0, if the Target Identification IE preamble byte is included as part of the gtpc send configuration of the SGTP Service, then multiple optional parameters, such as Extended RNC ID, are encoded. Extended RNC ID expands the ID range from 0 - 4095 to 0 - 65535.

This is an expansion of the supported functionality and no changes were made to the syntax. If the gtpc send configuration does not include the IE (the default), then the SGSN accords with 3GPP TS 29.060, v9.7.0 which discourages inclusion of the preamble as this version of 29.060 specifies some of the optional parameters (such as Extended RNC IDs) have become mandatory and some operational parameters are removed.

Previous Behavior: The SGSN did not support Extended RNC ID IE in RANAP messages. GTP messages like Forward Relocation Requests and GTP Relay Information Message did not support Extended RNC ID. Forward Relocation Request was using the encoding and decoding scheme mention in 3GPP 29.060 (Release 9.1.0 or earlier).

New Behavior: The SGSN now supports Extended RNC ID IE in RANAP messages. GTP messages like Forward Relocation Requests and GTP Relay Information Message will support Extended RNC ID. Forward Relocation Request uses the encoding and decoding scheme mentioned in 3GPP 29.060 (Release 9.7.0 or after).

Default APN Enhancement to Support Multiple Trigger APNs

It is now possible to configure up to four (4) default APNs with the apn-selection-default command in the APN Remap Table configuration mode. The default APN selection procedure will proceed to check each configuration sequentially (in the order of configuration) for all conditions and options unti l one is a match.

This enhancement is intended to reduce the number of activation rejections because of incorrectly configured APNs and enable better operational efficiency. An example, would be the ability for an operator to define separate default APNs for prepaid and post-paid subscribers. Any one of the default APN configurations can be deleted but they must be deleted one-at-a time.

No changes were made to the syntax to support this functionality.

Previous Behavior: Previously, it was only possible to configure one default APN for an operator policy.

New Behavior: Now it is possible to use the same command syntax, apn-selection-default in the Call Control Profile configuration mode, to configure up to four instances of a default APN configuration per APN remap table and operator policy.

GTP-C Echo Sent Immediately

Previous Behavior: The SGSN sent GTP-C Echo Request 60 seconds after RAU Accept was received in the following scenario:
  • Precondition:
    • iups1-sgtp-service1/map-service1/sgsnno1/plmn1
    • iups2-sgtp-service2/map-service2/sgsnno2/plmn2
    • gprs1-sgtp-service2/map-service2/sgsnno2/plmn1
    • gprs2-sgtp-service1/map-service1/sgsnno1/plmn3
  • Scenario:
    • Attach in gprs1
    • Activate
    • GTPC/GTPU echo retries
    • Intra RAU in gprs2
    • Path failure
    • Complete RAU

New Behavior: When a new GTPC session is added to the SGTPCmgr and the SGTPCmgr does not have any information on that GGSN node, then the SGTPCmgr will send an Echo Request immediately without waiting for 60 seconds (even if SGTP service remote restart counter verification is disabled). So in the above scenario, the modifications mean that the SGSN sends Echo Request immediately after RAU Accept.

IMEI-SV Sending Behavior

Corrected Content: This section includes corrections to previously published content. The previous content stated that the “New Behavior: If CLI gtp send imeisv is not enabled and the SGSN receives IMEI-SV from the MS during authentication, then the SGSN IMEI-SV in the Create PDP Context Request to the GGSN. So now by default, the SGSN sends IMEI-SV if it is received even if gtp send imeiv is not enabled.”-- This information was in error and has been corrected below.

Previous Behavior: If CLI gtp send imeisv was not enabled and the SGSN received IMEI-SV from the MS during authentication, then the SGSN sent the IMEI-SV, in the Create PDP Context Request, to the GGSN. So by default, IMEI-SV was sent if received, even if gtp send imeiv was not enabled.

New Behavior: If CLI gtp send imeisv is not enabled and the SGSN receives IMEI-SV from the MS during authentication, then the SGSN does not send IMEI-SV in the Create PDP Context Request to the GGSN. So now by default, the SGSN sends IMEI-SV if it is received only if gtp send imeiv is enabled.

In/Outbound Stream Control Enhanced

Previous Behavior: The maximum configurable CLI limit for sctp-max-out-strms was set to 65535 even though internally the number was capped at 16 as the maximum number of streams supported.

New Behavior: The maximum configurable CLI limit for sctp-max-out-strms is now 16, the default limit. To expand the operators control of streaming, a configurable parameter to control inbound streaming - sctp-max-in-strms - has been made accessible in the CLI.

Impact: For outbound streaming with sctp-max-out-strms, backward compatibility is maintained because even if the customer configured a maximum greater than 16 in the CLI, the functional maximum was capped. For inbound streaming, the customer can configure the maximum number of streams, up to 16, to accommodate reception needs from the peer - hence stream negotiation is improved and complete.

NRIs per SGSN

Beginning with Release 14.0, the number of subscribers per sessmgr has increased. For this reason, it is strongly recommended that at least 3 local NRIs be configured per SGSN to ensure smooth operation.

P-TMSI Allocation Strategy Change

Previous Behavior: The SGSN re-issued the same P-TMSI rather than relinquish a previously allocated P-TMSI even if the MS had not started to use it.

New Behavior: The SGSN relinquishes a P-TMSI if the MS is not using it and re-generates another P-TMSI on the next Attach/RAU.

Impact: The SGSN has a free run to generate any P-TMSI, so there should not be any impact due to this change.

Session Manager Guard-Timer

Previous Behavior: The internal SM guard-timer was hard-coded to 80s for 2G subscribers and 35 seconds for 3G subscribers.

New Behavior: The internal SM guard-timer is now configurable and the default for both 3G and 2G timers is 80 seconds.

SGSN Configuration Management Changes as of June 29, 2012

This section provides information on SGSN configuration command changes in release 14.0.

IMPORTANT:

For more information regarding commands in this section, refer to the GPRS/UMTS Command Line Interface Reference for this release.

New SGSN Configuration Commands

This section identifies new SGSN commands available in release 14.0.

associate

Beginning with release 14.0, the associate CLI command will be used to associate all services associated with GPRS and SGSN services. The only exception is the IuPS service. This is to provide a common framework for associating services across the SGSN.

GPRS Service Configuration Mode

associate { { camel-service < camel_svc_name
> | dscp-template
downlink <
dscp_template_name > | egtp-service < egtp_svc_name
> | gs-service< gs_svc_name
> | hss-peer-service < hss_svc_name
> | map-service < map_svc_name
> | network-global-mme-id-mgmt-db | sgtp-service < sgtp_svc_name
> } [ context < ctx_name
> ] | tai-mgmt-db < database_name
> } 
no associate { camel-service | dscp-template downlink | egtp-service
 | gs-service | hss-peer-service | map-service | network-global-mme-id-mgmt-db | sgtp-service | tai-mgmt-db < database_name
> }

SGSN Service Configuration Mode

associate { { camel-service < camel_svc_name
> | egtp-service< egtp_svc_name
> | gs-service< gs_svc_name
> | hss-peer-service< hss_svc_name
> | map-service< map_svc_name
> | network-global-mme-id-mgmt-db | sgtp-service < sgtp_svc_name > } [ context < ctx_name
>  ] | tai-mgmt-db < database_name > }
no associate { camel-service
 | egtp-service  | gs-service  | hss-peer-service
 | map-service  | network-global-mme-id-mgmt-db | sgtp-service | tai-mgmt-db < database_name
>  }

associate

New associate command with a new keyword dscp-template downlink in the IuPS service configuration mode associates the DSCP template with the IuPS service and the Iu interface to apply the configured DSCP values for all downlink subscriber-specific control packets sent out from the SGSN.

IuPS Service Configuration Mode

associate dscp-template
downlink <template_name>
no associate dscp-template downlink

associate

New associate command with a new keyword dscp-template downlink in the GPRS service configuration associates the DSCP template with the GPRS service and the Gb interface to apply the configured DSCP values for all downlink subscriber-specific control packets sent out from the SGSN.

GPRS Service Configuration Mode

associate dscp-template
downlink <template_name>
no associate dscp-template downlink

dns-pgw

Specifies the name of the context where the S4-SGSN should perform a DNS lookup for the P-GW.

Call Control Profile Configuration Mode

dns-pgw context < context_name
>
remove dns-pgw

dns-sgw

Specifies the name of the context where the S4-SGSN should perform a DNS lookup for the S-GW.

Call Control Profile Configuration Mode

dns-sgw context <context_name
>
remove dns-sgw

egtp-service

Creates a new, or enter an existing, EGTP service on the S4-SGSN.

Context Configuration Mode

egtp-service <service_name>
no egtp-service <service_name>

gmm T3323-timeout

Configures the Idle Mode Signaling Reduction deactivation timer value sent to the UE by the S4-GSSN during Attach Accept and RAU messages.

SGSN Service Configuration Mode

gmm T3323-timeout <dur_mins>
default T3323-timeout

gtpc

Configures an EGTP service on the S4-SGSN

EGTP Service Configuration Mode

gtpc { bind { ipv4-address <ipv4_address> [ ipv6-address <ipv6_address> ] | ipv6-address <ipv6_address> [ ipv4-address <ipv4_address> ] } | echo-interval <seconds> { dynamic | smooth factor <multiplier> ] } | echo-retransmission-timeout <secs> | max-retransmissions <num> | path-failure detection | retransmission-timeout <seconds> }
no gtpc { bind { ipv4-address <ipv4_address> [ ipv6-address <ipv6_address> ] | ipv6- address <ipv6_address> [ ipv4-address <ipv4_address> ] } | echo-interval | path-failure
detection }
default gtpc { echo-interval | max-retransmissions | path-failure
detection | retransmission-timeout }

idle-mode-signaling-reduction

Configures the Idle Mode Signaling Reduction (ISR) feature on the S4-SGSN. Only umts is currently supported as an access-type.

Call Control Profile Configuration Mode

idle-mode-signaling-reduction
access-type { umts | gprs }
remove idle-mode-signaling-reduction
access-type { gprs | umts }

interface-type

Specifies the interface type for a pre-configured EGTP service.

EGTP Service Configuration Mode

interface-type { interface-mme | interface-pgw-ingress | interface-sgsn | interface-sgw-egress
 | interface-sgw-ingress }

location-reporting

Enables the SGSN to perform location change reporting to the GGSN.

Call Control Profile Configuration Mode

location-reporting access-type { gprs | umts }
remove location-reporting
access-type { gprs | umts }

pdn-type-override

Enables the SGSN to override the IPv4v6 PDP/PDN type based on the access-type.

Call Control Profile Configuration

pdn-type-override ipv4v6
( ipv4 | ipv6 ) [ access-type { eps | gprs | umts } ]
remove pdn-type-override
access-type { eps | gprs | umts }

pdp-activate

Enables the operator to configure the SGSN to reject secondary PDP requests from the UE based on the configured IMEI range.

IMEI Profile Configuration Mode

pdp-activate { drop | restrict } secondary-activation
access-type { gprs | umts }
remove pdp-activate { drop | restrict } secondary-activation
access-type { gprs | umts }

peer-mme

Configures a peer MME address for a given MME group ID (LAC) and MME code (RAC) on the S4-SGSN.

Call Control Profile Configuration Mode

peer-mme mme-groupid  <lac_id> mme-code <rac_id>  prefer { fallback-for-dns | local } address  { <ipv4_address> |  <ipv6_address> } interface { gn { s3 } | s3 { gn } }
remove peer-mme mme-groupid
 <lac_id> mme-code  <rac_id> prefer { fallback-for-dns | local } address {  <ipv4_address>| <ipv6_address>} interface { gn { s3 } | s3 { gn } }

pgw-address

Configures a local P-GW address on the S4-SGSN.

APN Profile Configuration Mode

pgw-address <ip4_address> weight <value> [ -noconfirm ]


plmn

Creates a custom list of MME group IDs on the S4-SGSN if networks have been configured with LACs in the 32768-65535 range for UMTS and GPRS coverage.

LTE Network Global MME ID Management Database Mode

plmn mcc <mcc_value> mnc <mnc_value>mme-group-id-range first <low_num>last <high_num>
no plmn mcc <mcc_value> mnc <mnc_value> mme-group-id-range
first <low_num> last <high_num>

prefer subscription-interface

Selects the specified subscription interface (Gr or S6d) if both interfaces are associated with call control profile.

Call Control Profile Configuration Mode

prefer subscription-interface { hlr | hss } 
remove prefer subscription-interface { hlr | hss }

qos

Enables the operator to define QoS mapping parameters between the S4-SGSN and the S-GW.

Call Control Profile Configuration Mode

qos gn-gp { arp
high-priority  <
priority > medium-priority < priority > | pre-emption { capability { may-trigger-pre-emption | shall-not-trigger-pre-emption } | vulnerability { not-pre-emptable | pre-emptable } }
remove qos gn-gp arp
remove qos gn-gp pre-emption { capability | vulnerability } 

rai

Configures local a Routing Area Instance that will serve the S-GW addresses for an S4-SGSN.

LTE TAI Management Object Configuration Mode

rai mcc  <mcc_value> mnc  <mnc_value> lac  <lac_value> rac  <rac_value>
no rai mcc  <mcc_value> mnc  <mnc_value> lac  <lac_value> rac  <rac_value>

sctp-max-data-chunks

Enables the operator to define a maximum limit for the number of Data chunks that can be bundled into an SCTP message.

Peer Server Process Configuration Mode

sctp-max-data-chunks ( limit <1..65535> | mtu-limit )
default sctp-max-data-chunks

sctp-max-in-strms

Enables the operator to determine the maximum number of inbound streams to receive from the peer.

PSP Configuration Mode

sctp-max-in-strms < max_in_strms
> 
default sctp-max-in-strms

sctp-parameters

Enables the operator to suppress repeat sending of the source IPv4 address as part of the Optional Address Parameter IE i the INIT/INIT-Ack chunk when the endpoint is uni-homed.

Peer Server Process Configuration Mode

sctp-parameter ipv4-address
suppress single-ended 
[ default | no
sctp-parameter ipv4-address suppress single-ended

service-type

A new service-type command enables the operator to configure multi-service support for a single port on a channelized line card (CLC2).

Card Configuration Mode

service-type multi-service  
default service-type

sgsn-core-nw-interface

On the S4-SGSN, enables operators to forcefully select the Gn interface for EPC-capable UEs.

sgsn-core-nw-interface { gn | s4 }

sgw-address

Configure a local S-GW address serving the configured RAIs in the TAI object on an S4-SGSN.

LTE TAI Object Configuration Mode

sgw-address <ipv4_addr> | <ipv6_addr> s5-s8-protocol { both | gtp | pmip } weight <number>
no sgw-address <ipv4_addr> | <ipv6_addr> s5-s8-protocol { both | gtp | pmip }

tai-mgmt-db

Creates a TAI Management Database for the S-GW for RAI configuration on the S4-SGSN. Once created, the user enters TAI Management Database Configuration Mode.

LTE Policy Configuration Mode

tai-mgmt-db <tai_mgmt_db_name> [ -noconfirm ]
no tai-mgmt-db <tai_mgmt_db_name> [ -noconfirm ]

tai-mgmt-obj

Creates a TAI management object and enters TAI Management Object Configuration Mode for configuring S-GW addresses per RAI on the S4-SGSN.

LTE Management Database Configuration Mode

tai-mgmt-ojb <obj_name> [ -noconfirm ]
no tai-mgmt-obj <obj_name>

validation-mode

Specifies the validation method to be performed on messages received by the configured EGTP service on the S4-SGSN.

EGTP Service Configuration Mode

validation-mode { custom1 | standard }
default validation-mode

vplmn-address

Overrides the ‘vplmn-address-allowed’ flag behavior during GGSN selection.

Call Control Profile Configuration Mode

vplmn-address { allowed | not-allowed }
remove vplmn-address

Modified SGSN Configuration Commands

This section identifies SGSN commands modified in release 14.0.

associate

A new keyword dscp-template downlink associates the DSCP template with a specific peer server process (PSP) instance to allow the SGSN to apply the configured DSCP values for all downlink control messages sent out of the SGSN over the SCTP association.

PSP Configuration Mode

associate dscp-template downlink < template_name
>
no associate dscp-template downlink

ciphering-algorithm-gprs

The maximum number of ciphering algorithm priorities that can be configured has been reduced from 8 to 4.

Call Control Profile Configuration Mode

ciphering-algorithm-gprs
priority <
priority > < algorithm_type > 
remove ciphering-algorithm-gprs
priority <
priority >

failure-handling

The functionality of the continue option for IMEI procedures can be configured in case of timeout and error responses requests from HSS so that the requests will be re-tried on a second peer (if configured) and the call is continued. Previously, for IMEI procedures the continue option had the same funtionality as the retry-and-terminate option.

HSS Peer Service Configuration Mode

failure-handling { authentication-information-request | check-identity-request| notify-request | purge-ue-request | update-location-request } { diameter-result-code start_error_code [ to end_error_code ] | request-timeout } action {  continue | retry-and-terminate | terminate }

nri

Modified to support configuration of P-TMSI scaling for PSC3s. For the nri length command, keywords are now optional rather than mandatory. The default nri command is added to set the NRI length to 6 and the value to 0.

GPRS Service Configuration Mode

nri length < length > [ nri-value < nri_value > | null-nri-value < null_nri > non-broadcast-lac < lac > rac <rac>  nri-value  < nri_value
> ] 
default nri

path

The new service-type keyword enables the operator to configure multiple service types (e.g., Frame Relay and MTP2) for the same port on a Channelized line card (CLC2).

Channelized Port Configuration Mode

path path_id { ds1 connects | e1 connects } service-type service-type frame-mapping multiplexing
index# index# framing mode mapping-mode { bit-sync | byte-sync } [ timeslots slot# [ slot# ] | framerelay [ intf-type intf_type [ lmi_type lmi_type ] ] ]
no path path_id   { ds1 | e1 } connects service-type service_type 

pdp-activate restrict

New pdp-type keyword enables the SGSN to restrict PDP activation on the basis of the requested PDP-type and network access type.

Call Control Profile Configuration Mode

pdp-activate restrict
pdp-type { all | dual-ipv4v6 | ipv4 | ipv6 | ppp } access-type { gprs | umts } [ all | location-areas-list
instance <
instance >  } 
remove pdp-activate restrict
pdp-type { all | dual-ipv4v6 | ipv4 | ipv6 | ppp } access-type { gprs | umts } [ all | location-areas-list
instance <
instance >  }

peer-nsei

In the peer-nsei command, a new set of keywords enables the operator to associate a DSCP marking template at the peer-NSE level to allow the SGSN to apply the configured DSCP values for all downlink packets sent out from the SGSN over the Gb interface.

GPRS Service Configuration Mode

peer-nsei <nse_id> associate dscp-template downlink < template_name
>
no peer-nsei <nse_id> associate dscp-template downlink 

peer-nsei

For the peer-nsei command, the name keyword is added to enable the operator to assign a name to the BSC in the configuration.

GPRS Service Configuration Mode

peer-nsei <nse_id> [ name < peer_nsei_name
> ]
no peer-nsei < nsei_id > [ name ]  

sctp-max-out-strms

The system has always capped the maximum number of outbound SCTP streams at 16 and now the configurable range (1 - 16) has been modified to accommodate the cap.

PSP Configuration Mode

sctp-max-out-strms < max_in_strms
> 
default sctp-max-out-strms

sgsn-address

New keyword interface has been added to enable operators to specify the interface type (s16 or gn) used for communication between the SGSN and the peer SGSN.

Call Control Profile Configuration Mode

sgsn-address rac <rac value> lac <lac value> [ nri <val> ] prefer { local | fallback-for-dns} address
ipv4 <ipv4 addr> interface { gn | s16 }

sgsn offload

Keyword combinations for imsi and target-nri have been added to enable the operator to select a particular subscriber for offloading and/or to select a particular SGSN as the target for offloading.

Exec Mode

sgsn offload { gprs-service < service_name
> | sgsn-service < service_name
> }  { activating [ imsi < imsi > | nri-value < nri_value > | stop [ imsi < imsi > | nri-value < nri_value
> ] ] | connecting [ nri-value < nri_value
>  | stop [ imsi < imsi > | nri-value < nri_value > | target-nri < target_nri > ] | t3312-timeout < seconds > [ nri-value < nri_value > | target-nri < target_nri > ] | target-nri < target_nri > [ imsi < imsi > | target-count < num_to_offload > ] ] }

sm

The new guard-timer keyword enables the operator to set the expiry timer for the internal timer that controls when the session manager resources are cleared for both 3G and 2G SGSNs:

GPRS Service Configuration Mode and SGSN Service Configuration Mode

sm guard-timer< guard_seconds> 
default sm guard-timer

Deprecated SGSN Configuration Commands

This section identifies SGSN commands that are no longer supported in release 14.0.

associate-service

The associate-service command has been deprecated and the function has been added to the associate command.

SGSN Service Configuration Mode

associate-service { egtp <service_name> | hss-peer-service <service_name> context <context_name> }

associate-service

The associate-service command has been deprecated and the function has been added to the associate command.

GPRS Service Configuration Mode

associate-service { egtp <service_name> | camel-service <service_name> | gs-service <service_name> | hss-peer-service <service_name> | map-service <service_name> | sgtp-service <service_name> context <context_name> }

camel-service

The camel-service command has been deprecated and the function has been added to the associate command.

SGSN Service Configuration Mode

camel-service <service_name> context <context_name> 

gs-service

The gs-service command has been deprecated and the function has been added to the associate command.

SGSN Service Configuration Mode

gs-service <service_name> context <context_name> 

mobile-application-part service

The mobile-application-part-service command has been deprecated and the function has been added to the associate command.

SGSN Service Configuration Mode

mobile-application-part service<service_name> context <context_name> 

no nri

The no nri option has been deprecated from the nri command.

GPRS Service Configuration Mode

no nri

sgtp-service

The sgtp-service command has been deprecated and the function has been added to the associate command.

SGSN Service Configuration Mode

sgtp-service<service_name> context <context_name> 

SGSN Performance Management Changes as of June 29, 2012

This section provides information on SGSN performance management changes in release 14.0.

IMPORTANT:

For more information regarding bulk statistics in this section, refer to the Statistics and Counters Reference for this release.

For more information regarding commands in this section, refer to the Command Line Interface Reference for this release.

New SGSN Bulk Statistics

This section identifies new SGSN bulk statistics available in release 14.0.

The following bulk statistics are new in this release:

EGTPC (The SGSN supports only the following variables in the schema):

  • vpnname
  • vpnid
  • servname
  • servid
  • tun-sent-cresess
  • tun-sent-retranscresess
  • tun-recv-cresessresp
  • tun-recv-cresessrespaccept
  • tun-recv-cresesssrespdenied
  • tun-recv-crebear
  • tun-recv-retranscrebear
  • tun-sent-crebearresp
  • tun-sent-crebearrespaccept
  • tun-sent-crebearrespdenied
  • tun-sent-retranscrebearresp
  • tun-sent-bearrescmd
  • tun-sent-retransbearrescmd
  • tun-recv-bearrescmd-fail
  • tun-recv-retransbearrescmd-fail
  • tun-sent-modbearreq
  • tun-sent-retransmodbearreq
  • tun-recv-modbearresp
  • tun-recv-modbearrespaccept
  • tun-recv-modbearrespdenied
  • tun-sent-delsessreq
  • tun-sent-retransdelsessreq
  • tun-recv-delsessresp
  • tun-recv-delsessrespaccept
  • tun-recv-delsessrespdenied
  • tun-recv-delbearreq
  • tun-recv-retransdelbearreq
  • tun-sent-delbearresp
  • tun-sent-delbearrespaccept
  • tun-sent-delbearrespdenied
  • tun-recv-dlinknotif
  • tun-recv-retransdlinknotif
  • tun-sent-dlinknotifack
  • tun-sent-dlinkdatafail
  • tun-sent-relaccbearreq
  • tun-sent-retransrelaccbearreq
  • tun-recv-relaccbearresp
  • tun-recv-relaccbearrespaccept
  • tun-recv-relaccbearrespdenied
  • tun-sent-delbearcmd
  • tun-sent-retransdelbearcmd
  • tun-recv-delbearfail
  • tun-recv-retransdelbearfail
  • tun-recv-deactbear
  • tun-sent-deactbearfail
  • OutSigPktS4SGSN
  • IncSigPktS4SGSN
  • OutSigOctS4SGSN
  • IncSigOctS4SGSN
  • path-sent-echoreq
  • path-sent-retransechoreq
  • path-recv-echoreq
  • path-sent-echoresp
  • path-recv-echoresp
  • path-sent-versnotsupp
  • path-recv-versnotsupp
  • mobility-sent-ctxreq
  • mobility-sent-retransctxreq
  • mobility-recv-ctxreq
  • mobility-recv-retransctxreq
  • mobility-sent-ctxrsp
  • mobility-sent-retransctxrsp
  • mobility-recv-ctxrsp
  • mobility-recv-retransctxrsp
  • mobility-sent-ctxrspaccept
  • mobility-sent-ctxrspdenied
  • mobility-recv-ctxrspaccept
  • mobility-recv-ctxrspdenied
  • mobility-sent-ctxack
  • mobility-sent-retransctxack
  • mobility-recv-ctxack
  • mobility-recv-retransctxack
  • mobility-sent-ctxackaccept
  • mobility-sent-ctxackdenied
  • mobility-recv-ctxackaccept
  • mobility-recv-ctxackdenied
  • mobility-sent-idtreq
  • mobility-sent-retransidtreq
  • mobility-recv-idtreq
  • mobility-recv-retransidtreq
  • mobility-sent-idtrsp
  • mobility-recv-idtrsp
  • mobility-recv-retransidtrsp
  • mobility-recv-retransidtrsp
  • mobility-sent-idtrspaccept
  • mobility-sent-idtrspdenied

SGSN Schema

  • 2G-total-num-actv-pdp-on-s4
  • 3G-total-num-actv-pdp-on-s4
  • 2G-num-subs-with-isr
  • 3G-num-subs-with-isr
  • 2G-num-sgw-reloc-due-to-intra-rau
  • 3G-num-sgw-reloc-due-to-intra-rau
  • 2G-num-sgw-reloc-due-to-s16-rau
  • 3G-num-sgw-reloc-due-to-s16-rau
  • 2G-num-sgw-reloc-due-to-s3-rau - visible but not yet supported
  • 3G-num-sgw-reloc-due-to-s3-rau - visible but not yet supported

SS7 Schema

  • ss7-dpc-route-set-test-prohibited-tx
  • ss7-dpc-route-set-test-restricted-tx
  • ss7-dpc-route-set-test-prohibited-rx
  • ss7-dpc-route-set-test-restricted-rx

System Schema

  • disc-reason-438 (sgsn-egtpc-connection-failed)
  • disc-reason-439 (sgsn-egtpc-create-sessionfailed)
  • disc-reason-440 (sgsn-hss-detacc)
  • disc-reason-441 (sgsn-hss-connection-failure)
  • disc-reason-442 (sgsn-pgw-detach)
  • disc-reason-443 (sgsn-s5-s8-no-support-for-apn)
  • disc-reason-444 (sgsn-no-rab-for-gbr-bearer) – not yet supported
  • disc-reason-445 (sgsn-sgw-selection-failure)
  • disc-reason-446 (sgsn-pgw-selection-failure)
  • disc-reason-488 (sgsn-detach-notify)
  • disc-reason-493 (sgsn-pgw-init-deact)
  • disc-reason-494 (s6b-ip-validation-failed)
  • disc-reason-495 (sgsn-failure-rsp-from-sgw)
  • disc-reason-499 (ptmsi-signature-mismatch)
  • disc-reason-500 (camel-invalid-configuration)
  • disc-reason-503 (sgsn-isr-addl-ptmsi-rai)
  • disc-reason-504 (sgsn-sgw-dbr-cause-isr-deact)
  • disc-reason-505 (sgsn-isr-mme-init-detach)
  • disc-reason-507 (sgsn-ptmsi-crunch)

Modified SGSN Bulk Statistics

This section identifies SGSN bulk statistics modified in release 14.0.

None for this release.

Deprecated SGSN Bulk Statistics

This section identifies deprecated SGSN bulk statistics that are no longer supported in release 14.0.

None for this release.

New SGSN Performance Commands

This section identifies new SGSN performance commands available in release 14.0.

show s4-sgsn statistics

Provides statistics related to the S4-SGSN, including S-GW Relocations, ISR Deactivations, and S3 Interface Selection Statistics.

Exec Mode

show s4-sgsn statistics [ all | smgr-instance <instance_number> ]
clear s4-sgsn statistics [ all | smgr-instance <instance_number> ] 

Modified SGSN Performance Commands

This section identifies SGSN performance commands modified in release 14.0.

clear subscribers

Use of the new imei keyword enables the operator to disconnect one subscriber or a range of subscribers based on the international mobile equipment identity (IMEI or IMEI-SV) of the subscriber’s mobile equipment.

Exec Mode

clear subscribers imei <imei> 
clear subscribers sgsn-service <service_name> imei <imei>
clear subscribers gprs-service <service_name> imei <imei>

clear subscribers

Use of the new pooled-only keyword ensures offloading only the subscribers from pooled RNCs/NSEIs.

Exec Mode

clear subscribers { gprs-service < service_name
> | sgsn-service < service_name
> } nri { any | <nri_value> } pooled-only 

show bssgp statistics

The output of this command has been modified so that RIM messages dropped due to an invalid LAC value in the destination address display only for the invalid destination address.

Exec Mode

show bssgp statistics

show bssgp statistics verbose

The output of this command, using the verbose keyword, has been enhanced due to the moving of detailed BSSGP statistics for downlink packets dropped due to different causes to verbose mode.

Exec Mode

show bssgp statistics verbose

show bulkstat variables

The output of this command has been enhanced to include the two bulkstat variables related to message errors for permanent and transient failures on the SGSN.

Exec Mode

show bulkstat variables

show call-control-profile

The output of this command, using the full and all keywords, has been enhanced to provide information related to the preferred subscription interface configured on the SGSN.

Exec Mode

show call-control-profile
full all

show call-control-profile

The output of this command, using the full and name keywords, has been modified to show the name of the TAI management database associated with the specified call-control-profile on the S4-SGSN.

Exec Mode

show call-control-profile
full name <name>

show call-control-profile

The output of this command, using the full and name keywords, has been modified to show the GPRS, UMTS, and/or EPS PDN Type Override configuration information. EPS information is applicable to the S4-SGSN only.

Exec Mode

show call-control-profile
full name <name>

show configuration

The output of this command has been modified to indicate if a DSCP template has been associated with the ss7-routing-domain.

Exec Mode

show configuration

show configuration

This command output, using the verbose keyword, has been modified to show the interface type configured for the peer SGSN.

Exec Mode

show configuration verbose

show egtp statistics

The output of this command is enhanced to show message statistics for the Idle Mode Signaling Reduction (ISR) feature on the S4-SGSN. The verbose option provides additional ISR-related message information.

Exec Mode

show egtpc statistics [ verbose ]

show gmm-sm statistics

The output of this command has been enhanced to provide counters related to the override of the VPLMN Address-Allowed Flag on a per service basis.

Exec Mode

show gmm-sm statistics { gprs-service | sgsn-service }<service-name>

show gmm-sm statistics

The output of this command, with the sm-only keyword, has been enhanced to provide statistics related to the Override PDP Type for Inbound Roamers.

Exec Mode

show gmm-sm statistics
sm-only

show gmm-sm statistics

The output of this command, with the verbose keyword, has been enhanced to provide information related to idle-mode-signaling reduction activity and operator policy-based reject counters related to EGTPC.

Exec Mode

show gmm-sm statistics verbose

show gmm-sm statistics

The output of this command, with the sm-only and verbose keywords, has been enhanced to provide information on how many secondary PDP requests from a UEs have been restricted (ignored) or rejected.

Exec Mode

show gmm-sm statistics
sm-only verbose

show gmm-sm statistics

The output of this command, with the verbose keyword, has been enhanced to provide a new counter that increments by one only when all instances of an APN Selection failed.

Exec Mode

show gmm-sm statistics verbose

show gmm-sm statistics

The output of this command, with the verbose keyword, has been modified to rename the Cancel Location Attempts Indicator to cancel-loc-att-indicator. This counter also has been re-aligned to appear inline with the counter that precedes it.

Exec Mode

show gmm-sm statistics verbose

show gprsns statistics

The output of this command, with the sns-msg-stats and verbose keywords, has been enhanced to provide three new counters that provide information on the type of cause for the transmission of the SNS status message.

Exec Mode

show gprsns statistics
sns-msg-stats verbose

show gprs-service

The output of this command, with the name keyword, has been modified to indicate whether a DSCP template has been associated with the peer NSEI.

Exec Mode

show gprs-service name <service_name>

show gprs-service

The output of this command, with name keyword, has been modified to indicate if a Network Global MME ID Management Database and TAI Management Database are associated with the specified GPRS service on the S4-SGSN.

Exec Mode

show gprs-service name <service_name>

show gprs-service name

The output of this command, with the name keyword, has been enhanced to provide the BSC name associated with the configuration.

Exec Mode

show gprs-service name <service_name>

show gprs-service

The output of this command, with the all and nsei all keywords, has been enhanced to show the NSEI information (MCC, MNC, LAC, RAC, NSE status) in tabular form.

Exec Mode

show gprs-service all
nsei all

show gprs-service

The output of this command, with the all and nsei id keywords, has been enhanced to show the NSE information in tabular form.

Exec Mode

show gprs-service all
nsei id <nse-id>

show gprs-service

The output of this command, with the name and nsei all keywords, has been enhanced to show the NSE information in tabular form.

Exec Mode

show gprs-service name <service_name> nsei all

show gprs-service

The output of this command, with the name and nsei id keywords, has been enhanced to show the NSE information in tabular form.

Exec Mode

show gprs-service name <service_name> nsei id <nse-id>

show hss-peer-service

The output of this command, with the all keyword, has been modified so that the Request timeout field always reads n/a (not applicable), as the Request timeout is not currently used.

Exec Mode

show hss-peer-service all

show imsa - Changes to the Output

Corrected Content: Information related to changes to the output of show imsa was added to the SGSN section in error and it has been removed.

show iups service name

The output of this command, with the name keyword, has been enhanced to indicate if a DSCP template has been defined for the specified iups-service.

Exec Mode

show iups-service name <service-name>

show llc statistics verbose

The output of this command, with the verbose keyword, been enhanced so that in the tlli unassigned state, the SGSN will not process an XID with a SAP value not equal to 1.

Exec Mode

show llc statistics verbose

show lte-policy

Including the tai-mgmt-db name keyword with the command generates an output enhanced to provide the parameters for the configured TAI management database on the S4-SGSN.

Exec Mode

show lte-policy tai-mgmt-db name<db_name>

show sgsn

Including the sessmgr keyword with the command generates a display that has been enhanced to provide output related to P-TMSI scaling for PS3 cards.

Exec Mode

show sgsn sessmgr ptmsi
statistics { nri <nri_value> }

show sgsn-pool statistics

The output of this command, with the sgsn-service, imsi-offloaded-to-peer and verbose keywords, has been enhanced to show the current off-loading configuration, and to show the off-load status for subscribers based on the IMSI.

Exec Mode

show sgsn-pool statistics
sgsn-service <service_name> imsi-offloaded-to-peer
verbose

show sgsn-service

The output of this command, with all keyword, has been enhanced to provide the configured GMM-T3323 Timeout value for the Idle Mode Signaling Reduction feature on the S4-SGSN.

Exec Mode

show sgsn-service all

show sgsn sessmgr

New keywords ptmsi statistics and nri <nri_value> have been added to provide information for how many P-TMSIs are presently allocated and how many are still free to be freshly allocated.

Exec Mode

show sgsn sessmgr { all | instance <instance> } ptmsi statistics { nri <nri_value> }

show sgtpc statistics

The output of this command, with the all keyword, has been enhanced to display GTP MS Info Change Notification Request and MS Info Change Notification Response message statistics.

Exec Mode

show  sgtpc statistics all

show ss7-routing-domain

The output of this command has been enhanced to provide counter information related to RST and RSR messages when the keywords, illustrated below, are included with the command.

Exec Mode

show ss7-routing-domain
all mtp3 statistics destination-point-code all

show ss7-routing-domain

The output of this command has been modified to indicate whether or not a DSCP template has been associated with the specified ss7-routing domain.

Exec Mode

show ss7-routing-domain <domain_num>

show subscribers

Use of the new pooled-only keyword in combination with the nri keyword instructs the SGSN to only display subscribers with a specific NRI in pooled RNCs/NSEIs.

Exec Mode

show subscribers { gprs-service < service_name
> | sgsn-service < service_name
> } nri { any | <nri_value> } pooled-only 

show subscribers

The output of this command has been enhanced to provide information pertaining to subscriber usage of S4-SGSN related interfaces when keywords, illustrated below, are included with the command.

Exec Mode

show subscribers [ grps-only | sgsn-only ] summary

show subscribers

The output of the this command, with the gprs-only and full keywords, has been modified to change the status indication for QoS-related parameters on the S4-SGSN from “TRUE” to “ENABLED” and from “FALSE” to “DISABLED.”

Exec Mode

show subscribers gprs-only full

show subscribers

The output of this command, with the gprs-only and full keywords, has been modified to output the current PTMSI, PTMSI Ack flag, and any previously allocated PTMSI (when the current PTMSI is not acknowledged).

Exec Mode

show subscribers gprs-only full

show subscribers

The output of the this command, with the sgsn-only and full keywords, has been modified to change the status indication for QoS-related parameters on the S4-SGSN from “TRUE” to “ENABLED” and from “FALSE” to “DISABLED.”

Exec Mode

show subscribers sgsn-only full

show subscribers

The output of this command, with the sgsn-only and full keywords, has been modified to output the current PTMSI, PTMSI Ack flag, and any previously allocated PTMSI (when the current PTMSI is not acknowledged).

Exec Mode

show subscribers sgsn-only full

show subscribers

The output of this command, when including the sgsn-only, full, and all keywords, has been enhanced to provide information related to S4-SGSN functionality.

Exec Mode
show subscribers sgsn-only
full all

show subscribers

The output of this command, when including the summary keyword, has been enhanced to provide information relating to subscribers’ use of interfaces.

Exec Mode

show subscribers summary

Deprecated SGSN Performance Commands

This section identifies deprecated SGSN performance commands that are no longer supported in release 14.0.

None for this release.

SGSN Security Management Changes as of June 29, 2012

This section provides information on SGSN security management changes in release 14.0.

None for this release.