Beruflich Dokumente
Kultur Dokumente
2PGPDSK
TCAP/MAP
15
TCAP/MAP
GIPS
LAN
7
I/O
LP
4POC3
15
SIC
ATM I/F
ATM MPE
Gr
Gr
Ga
UDP/IP
Figure 22 Network view Mobile Attach
In order to access the PS services, an MS first makes its presence known to the network
by performing a GPRS Attach. This makes the MS available for SMS over PS, paging via
the SGSN, notification of incoming PS data, and PDP context activation.
In order for Mobile Attaches to succeed, the following interfaces must be operational: Gb
(2.2), Gr (2.6) and Gs (2.7) interface for combined attaches. Refer to the corresponding
sections in this document for information on how to monitor the health of these
interfaces.
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 74 October 2003
In order for Mobile Attaches to succeed the following network elements are required:
MS, SGSN Passport, SIG, and HLR. Therefore each of these elements must be
operational. Refer to section on SIG (3.11) for monitoring this element. HLR Monitoring
is outside the scope of this document.
In order for Mobile Attaches to succeed, the following functional components are
required: GTL (3.4), GSD LLC (3.3), GSC Gmm (3.2), GSC HlrC, GSC Mc, Tcap/Map
(3.10). Refer to the corresponding sections in this document for information on how to
monitor the health of these functional components.
The guidelines in the following sub-sections can be used to monitor GPRS Attach
operations.
Additional information on troubleshooting Attach/Detach can be found in UMTS/GPRS
Troubleshooting Guide NTP 411-5221-501.
4.1.1 Monitoring Attach Activity
The operator can determine how many mobiles are currently attached by displaying the
value of Gsc/ Gmm currentlyAttached counter. The GSC has a provisioned maximum
number of attaches that can be supported simultaneously via the Gsc/
maxAttachedSubscribers provisioning attribute. When this maximum is reached a Major
Set alarm (7068 1006) is raised against the GSC component. No new subscribers can
attach to the GSC until the number of currently attached subscribers falls below the
provisioned limit. This alarm is updated with a different severity depending upon what
percentage of maximum is reached: Minor denotes 90%, Major denotes 95% and Critical
severity denotes 100% of maximum. When the maximum is reached no new subscribers
are able to attach. The severity of this alarm is reduced to Major and Minor when the
number of currently attached subscribes falls below 98% and 93% respectively.
Provisioning a new GSC card into the shelf or increasing the provisioned value for Gsc/
maxAttachedSubscribers attribute could prevent this fault from occurring in the future.
The Gsc/ currentlyAttached attribute can be compared to the provisioned Gsc/
maxAttachedSubscribers attribute to get an indication of this alarm before the resources
are exhausted.
The GSC monitors the success rate of mobile attaches. Every 15 minutes, the GSC
calculates the percentage of attach rejections vs. total attach requests. If the attach success
rate for the 15 minute interval is below 90% then a Major Set alarm (Attach Requests
Rejected or not Received Alarm: 7068 1531) is raised against the Gsc/ Gmm component.
If the attach success rate is between 90% and 95% this alarm is raised with Minor
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 75 October 2003
severity. The alarm is cleared when the attach success rate is above 95%. This alarm also
gets raised with Critical severity if zero attach requests were received by the GSC within
the 15 minute window. This occurrence of the alarm is cleared when at least one attach
request is received within a 15 minute window. If this alarm is raised, the operator should
verify the GTL and MAP components are operating properly.
4.1.2 Identifying Reason for Attach Failure
If attach operations are failing, the following counters can be displayed to identify the
reason for the failures. All of these counters are on the Gsc/ Gmm component.
attachRejPacketNetworkFailure Major contributing factors to this counter is
MAP system failure and Gb Xid negotiation timeouts. MAP is receiving system
failure or SCCP SAI/UGL UDTS from the interface.
attachRejSgsnCongestion - cause could be:
o Maximum number of subscribers limit for GSC card is reached.
o GSD Max LLC active subscribers reached.
o TLLI collision.
o MAP or Gr congestion.
The above counters are also tracked on a per-cell basis. The attribute names are
attachRejPacketNetworkFailurePerCell and attachRejSgsnCongestionPerCellis and
they reside on the Gsc/ Mcc/ Mnc/ Lac/ Rac/ Cid/ component.
In addition to the above mentioned attach reject counters, there are attach reject counters
for tracking other attach reject reasons. The full set of counters can be viewed by
displaying the Gsc/ Gmm gmmAttRejStats group. Per cell versions of these counters
can be viewed by displaying the Gsc/ Mcc/ Mnc/ Lac/ Rac/ Cid/ gmmCellOper group.
If the Attach Reject count is greater than 0 for a DCS collection cycle, a warning message
alarm (Attach Reject Cause Code Reporting Alarm: 7068 1028) raised against the Gsc/
Gmm component itemizes the specific reasons for the attach rejects. The counts included
for network failures are resource exhaustion for primary contexts (noPrimCtxt), resource
exhaustion for procedural contexts (canNotAllocateTempCtxt), LLC general failure
(genFailureFromLlc), resource exhaustion for HLRc context (canNotAllocateHlrcCtxt),
TLLI assignment failures (assignReqFailure), MS reset procedure failure
(msResetProcFailure), LLC Deactivation Failures (deactReqFailure), security failures
(iovReqFailure), and map client failures (mapClientFailure). The counts included for
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 76 October 2003
congestion failures are maximum provisioned attaches reached (maxSubsReached),
resource error on the MAP (mapResourceError), TLLI Collisions (tlliCollision), and
failures in the attach confirm message (actConfirmFailure). The warning message is
informational in nature and can help to identify the specific part of the network
contributing to the attach failure.
4.1.3 CPU Utilization
Refer to the Logical Processor Monitoring section (3.8).
4.1.4 Max Subscribers Reached
The GSD also has maximum subscribers limit that is accompanied by a Major Message
alarm (Maximum Active Subscribers Reached Alarm: 7068 1009) when reached. If the
maximum subscribers limit has been reached, no new subscribers will be able to attach
until the number of active subscribers falls below the provisioned limit set by Gsd/
maxLlcActiveSubscribers provisioning attribute on the GSD.
The GSC may also disallow attaches if congested. The Major Message alarm (GSC
Memory Exhausted Alarm: 7068 1005) indicates resources exhausted on the GSC and
no further attaches will be allowed.
4.1.5 Other Things to Monitor
M-CDRs and M-CDRs are indirect indicators of shelf wide stability. See section (4.2)
for billing details.
4.1.6 Overload Conditions
See the Overload Control Monitoring section (3.2.6) for information on discarded
attaches during overload conditions.
4.2 Billing
Billing is recorded by events that occur on both the SGSN and the GGSN. The SGSN
creates Mobile Call Detail Record (MCDR) and Serving GPRS Support Node Call Detail
Records (SCDR). Each attach mobile generates a time based MCDR for the time that the
mobile is attached and a time based SCDR for each session created. For monitoring
information, reference the SAS Monitoring Section (3.9).
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 77 October 2003
4.3 RAU/ IRAU
Figure 23 Network view IRAU
Three types of RAU procedures can be performed on the SGSN: Periodic RAU, Intra-
RAU, and Inter SGSN RAU. The periodic RAU is a procedure between the SGSN and
the MS to maintain the position of the MS. The IntraSGSN-RAU is a procedure in which
the MS moves from one Routing Area (RA) to another RA where both are serviced by
the same SGSN. Inter SGSN RAU is a procedure in which the MS moves from one RA
to another RA where the new RA is served by a different SGSN.
MS
7K
Frame Relay
E1/T1
GTL
WPDS
GSD
7K
GSD
(LLC)
OC3
7K
SIC
ATM I/F
ATM MPE
4POC3
15K
SIC
ATM I/F
ATM MPE
2PGPDSK
GSC/DNS
CGF
SGSN
Global
TCP/IP
secure
network
2PGPDSK
SAS
15K
SAS
MCDR &
SCDR
TCAP/MAP
GIPS
2PGPDSK
TCAP/MAP
15K
SIG
HP
TCP/IP
SIPR
SS7
Network
Gb
15K
LAN
7K To
GGSN or
Old
SGSN
I/O
LP
Gn
Ga
Gr
G
HLR
UDP/IP
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 78 October 2003
4.3.1 Interfaces to Monitor
As the RAU procedure uses more nodes, more interfaces are involved in the procedure:
for periodic RAU, only the Gb (2.2) interface is used for a single RA, for Intra-RAU the
Gb (2.2) interface is used between two RAs, and for Inter SGSN RAU the Gb (2.2), Gn
(2.5), Gs (2.7), and Gr (2.6) interfaces are used.
4.3.1.1 Interfaces to Monitor for Periodic RAU
The periodic Rau involves a procedure where the mobile messages with the SGSN to
indicate that it is still present in the same RA. The number of periodic RAUs received at a
GSC is presented in the Gsc/ Gmm periodicIntraSgsnRaUpdate counter. The periodic
RAU timer runs on the mobile and triggers the MS to send the periodic RAU Request
message to the SGSN, which resets the msReachable timer. When the msReachable timer
times out, the MS is implicitly detached. Failures on periodic RAU procedures could be
attributed mostly to the Gb interface. The msReachable timer is a provisionable attribute
on Sgsn Gsc component.
4.3.1.2 Interfaces to Monitor for Intra RAU
The Intra-Rau update involves a procedure where the mobile messages with the SGSN to
indicate the new RA that the mobile has moved to. The number of Intra-RAUs received
at a GSC is presented in the Gsc/ Gmm normalIntraSgsnRaUpdate counter. The MS
location is updated in the GSC and a BVC relating to the new cell is assigned on the
GSD. Failures on Intra-RAU procedures could be mostly attributed to Gb interface, GSD,
or GTL problems.
4.3.1.3 Interfaces to Monitor for Inter SGSN RAU
The Inter SGSN RAU involves a procedure where the context related to the mobiles
attachment and the contexts related to all of the mobiles sessions are transferred over
from the old SGSN to the new SGSN. This includes a short period of time where
downlink data is transferred from the old SGSN to the new SGSN while the Gn interface
is being moved.
The Gb interface on the new SGSN receives the RAU request message indicating that the
mobile is requesting a move. A successful move of a mobile to a new SGSN will
increment the Gsc/ Gmm interSgsnRaUpdateAccepts counter the old SGSN will
decrement the Gsc/ Gmm currentlyAttached counter and the new SGSN will increase
that attribute.
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 79 October 2003
Mobile contexts are transferred between SGSN with the use of the Gn interface using the
GTP protocol. Inter SGSN RAU specific counters are presented in the Gsc/ GtpM
component of the SGSN. The new SGSN uses the DNS to find the IP address of the old
SGSN to communicate the Gn signaling with. See the DNS section (3.5) of this document
for possible problems with the DNS query. The new SGSN will increment the Gsc/ GtpM
sgsnContextReqAttempts and Gsc/ GtpM sgsnContextAcks counters during this
communication. A problem with the Gn interface on the new SGSN can be seen by a
rapid increase in the Gsc/ GtpM sgsnContextReqExhaust counter. This counter is
pegged when the old SGSN does not respond to the SGSN context request message sent
across the Gn interface. Failed Gn messaging will cause the old SGSN to continue to hold
the context for the mobile while the new SGSN will release any resources allocated for
the Inter SGSN RAU procedure.
The old SGSN also increments counters for its use of the Gn interface for Inter SGSN
RAU procedures. For each SGSN Context Request message received, the old SGSN
responds with an SGSN Context Response message, increments the Gsc/ GtpM
sgsnContextRespAttempts counter, and waits for an SGSN Context Acknowledge
message from the new SGSN. If the SGSN Context Acknowledge message is not
received before the GtpM T3 timer and N3 retries is exhausted, the Gsc/ GtpM
sgsnContextRespExhaust counter is incremented. A failed response for this message
may mean a failed connection, insufficient resources on the new SGSN, or the new
SGSN may have failed before sending the acknowledgement back to the old SGSN.
To successfully move a mobile from an old SGSN to a new SGSN, the Gr interface is
required. The new SGSN will send an Update GPRS Location request to the HLR and
receives an ISD from the HLR while the old SGSN will receive a Cancel Location from
the HLR. See the Gr interface section of this document for specific monitoring of the Gr
interface.
A mobile performing an Inter SGSN RAU procedure may contain active sessions that are
also transferred with the mobile. When sessions are transferred, extra messaging occurs
between the two SGSNs and the new SGSN and the GGSN where the sessions were
established. The SGSN Context Acknowledge message informs the old SGSN that the
new SGSN is ready to accept data packets. Data packets flowing from the GGSN are
tunneled to the old SGSN across the Gn interface, which forwards them to the new SGSN
across another Gn interface. The new SGSN delivers the packets to the MS. This happens
until the new SGSN receives an Update PDP Ctxt Response message from the GGSN.
When this happens, the GGSN starts tunneling packets to the new SGSN directly across a
Gn interface. Uplink packets are discarded until the MS sends a RAU Complete message
to the new SGSN. Refer to the Gn Interface section (2.5) for information on counters to
monitor.
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 80 October 2003
The new SGSN must transfer the Gn interface established between the old SGSN and the
GGSN to the new SGSN before completing the Inter SGSN RAU procedure. The update
PDP context request and update PDP context response message pair is used to transfer
the tunnel from the old SGSN to the new SGSN. Failures on this messaging could
indicate a connection or congestion problem on the Gn or GGSN respectively. See the Gn
interface section (2.5) for details.
Camel sessions transferred to a new SGSN can be deactivated if the Ge interface has a
problem. If the subscription for the session being transferred indicates that camel must be
active for that tunnel, the new SGSN will deactivate the session once it is received. Refer
to section (2.4) on the Ge Interface on how to monitor the health of that interface.
4.3.1.4 GMM T3 Tunnel Timeout on the New SGSN for Inter SGSN RAU
Procedures
GMM starts a T3 Tunnel timer on the old SGSN when the SGSN Context Request
message is received from the new SGSN. If a cancel location is not received on the old
SGSN before this timer expires, the old SGSN stops forwarding data to the new SGSN
and continues to service the mobile as before the Inter SGSN RAU procedure started.
The number of T3 timeouts is presented in the Gsc/ Gmm t3Timeouts counter. When
this counter is determined to be increasing rapidly or have a percentage higher than at
normal traffic times, the Gr interface and Gn interfaces should be examined.
4.3.1.5 Insufficient Resources on the New SGSN for Inter SGSN RAU
Procedures
The new SGSN must allocate resources for the new mobile and the new sessions
transferred over as part of an Inter SGSN RAU procedure. Resources are allocated on the
GSD and GSC for each mobile transferred. If resources are exhausted on either the GSD
or GSC, one of the following alarms is likely to be seen
(GSD Maximum Active Subscribers Reached Alarm: 7068 1009) Major
Message alarm,
(GSC Memory Exhausted Alarm: 7068 1005) Message alarm will be indicated
and the procedure will fail,
(GSC Maximum Attached Subscribers Reached Alarm: 7068 1006) Set
alarm.
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 81 October 2003
4.3.1.6 Excessive IRAU or RAU Failure Indications
Excessive IRAU and RAU failures are indicated by a minor set alarm (I/RAU Requests
Rejected Alarm: 7068 1027) raised against the Gsc/ Gmm component. When the failure
rate of the RAU procedure or the IRAU procedure is greater than 5% for the measured
DCS interval, this alarm is set. When the failure rate falls below the 5% limit during a
DCS interval, the alarm is cleared. This alarm could be the result of a network problem
on the Gr interface or an incompatibility issue between the Nortel SGSN and another
manufacturers SGSN. The total number of IRAU failures is recorded on the Gsc/ Gmm
totalIrauRejects operational and collected attributes and the total number of RAU
failures is recorded on the Gsc/ Gmm totalRauRejects operational and collected
attributes.
4.4 Activation and Deactivation
Activations are the establishment of data tunnels between the mobile and the network
requested. Multiple sessions can be activated simultaneously on a mobile. Each session
on a mobile is treated equally in all session related counters, provisioning and alarms.
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 82 October 2003
Figure 24 Network view Activation and Deactivation
4.4.1 Interfaces to Monitor
For activation and deactivation of sessions, the SGSN uses the Gb (2.2) and Gn (2.5)
interfaces. Refer to sections on monitoring these interfaces for any of the following
problems:
Excessive activation rejects
Excessive SGSN initiated deactivations (Gsc/ Sm sgsnInitDeacts)
GGSN initiated deactivations (Gsc/ Sm ggsnInitDeacts)
If the Gsc/ Sm mobileInitDeacts counter is not increasing while known MS initiated
deactivations are initiated, the Gb connection should be checked.
Deactivations initiated by the HLR, GGSN or the SGSN will succeed even without the
use of the Gb interface; however, the SGSN may try to page the mobile before skipping
the messaging to the mobile and completing the procedure. Not all network initiated
deactivations use the Gb interface. Examples of network initiated deactivations without
the use of the Gb interface include deactivation for duplicate activation request and
deactivations due to power off detach or detach.
MS
7
Frame
Relay
E1/T1
WPDS
GSD
7
GSD (LLC)
GSD (LLC)
GSD
OC3
7
SIC
ATM I/F
4POC
15
SIC
ATM I/F
2PGPDSK
SAS
15
SAS
2PGPDSK
GSC/DNS
Agent 15
GSC
CGF
SGSN
Global
TCP/IP
secure
network
Partial SCDR
LA
7
SIC
ATM I/F
Gn over
100Base
Bearer
Data
Ga
To
GGS
Gn
To DNS
DNS
Gb
UDP/IP
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 83 October 2003
The GSC monitors the success rate of PDP Context activations. Every 15 minutes, the
GSC calculates the percentage of activation rejections vs. total activation requests. If the
success rate for the 15 minute interval is below 90% then a Major Set alarm (PDP
Activations Requests Rejected or not Received Alarm: 7068 1532) is raised against the
Gsc/ Sm component. If the activation success rate is between 90% and 95% this alarm is
raised with Minor severity. The alarm is cleared when the activation success rate is above
95%. This alarm also gets raised with Critical severity if zero activation requests were
received by the GSC within the 15 minute window. This occurrence of the alarm is
cleared when at least one activation request is received within a 15 minute window. If
this alarm gets raised the operator should verify the GTL (3.4)and MAP (3.10)
components are operating properly.
4.4.2 GSD Failure on Sessions
All SGSN initiated deactivations, resulting from a failed GSD card, will not happen at the
time of the card reset. Instead, the deactivation is initiated when the next mobile message
originated message is received at the SGSN. A periodic RAU or an activate PDP Context
Request message for an additional session as well as others, would trigger an SGSN
initiated deactivate PDP Context Request message with the cause value of reactivation
requested for the sessions on a specific mobile. The Gsc/ Sm sgsnInitDeacts counter
and the Gsc/ Sm reactivationsRequested counters used together can indicate a possible
GSD failure.
An activation reject can be the result of a GSD failure. Although unlikely, there is a small
window where the GSD card could fail activation. The GSD card failure alarm will be
seen in this situation.
4.4.3 DNS Failure on PDP Context Activation
Activation rejects caused by failed DNS queries can be discovered through examining the
DnsAg/ serverQueryTimeouts or the DnsAg/ serverQueryFailures counter under the
DNS Agent component. The DnsAg/ serverQueryTimeouts counter indicates how
many times an external DNS had not responded to a request. The DnsAg/
serverQueryFailures counter is an indication of a failed DNS or a failed link to the
DNS. These failures may not be critical since the GSC allows up to four external DNSs
to be connected to a single GSC card.
4.4.4 Gn Connection Failures
The Gn interface carries the create PDP context message to the GGSN from the SGSN as
well as delete PDP context request and response and update PDP context request and
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 84 October 2003
response. Under high traffic conditions, the SGSN will generate the Major Message
alarm (GSC Memory Exhausted Alarm: 7068 1005). Two operational parameters in the
Gsc/ GtpM gprsGtpMgmtOp group indicate the use of the Gn transactions: the Gsc/
GtpM peakTransactions indicates the high water mark of the resource usage and the
Gsc/ GtpM currentTransactions attribute indicates how much GTP resources are
currently in use. If this alarm is seen often because of Gn failures, the Gsc/ GtpM
maxTransactions provisionable variable can be increased to allow for more transactions
to the GGSN.
4.4.5 GSD Resource Constraint on Activation
A GSD does not allow sessions to be established on it if the allocated resource for
sessions has been exhausted. A Major Message alarm (GSD Maximum Allocated LLEs
Reached Alarm: 7068 1012), should be seen simultaneously to the failed activations on
the GSC card.
4.4.6 GSC Resource Constraint on Activation
When the result of an activation reject is because of Gn or GSC reaching the provisioned
limit of resources, the Major Message Alarm (GSC Memory Exhausted Alarm: 7068
1005) is triggered indicating the exhaustion of all available resources. This alarm is an
indication of either poor engineering provisioning or high traffic through the GSC card.
By checking the CPU usage on the GSC card, the cause of the instability can be better
understood. If the CPU is not running at full capacity, the engineered value of the gsc/
maxAttachedSubscribers or the gsc/ avgActivePdpCPerActiveSub attributes may be
too low; these attributes are found in the gprsGscProv group. (Note: gsc/
maxAttachedSubscribers and gsc/ avgActivePdpCPerActiveSub attributes should not
be set higher than the maximum supported values as specified by Nortel Networks). The
Gsc/ maxAttachedSubscribers attribute defines how many mobiles can attach
simultaneously to one GSC. The Gsc/ avgActivePdpCPerActiveSub attribute defines
the average number of sessions activated per mobile.
The GSC monitors the rate of PDP Context activations.
4.4.7 Activation Reject Due to Timeout
Activation rejects could occur because of system instability. To activate a PDP context
the DNS, the Gb interface, the Gn interface and a GSD are used. The key indication of
system instability during activation is timeouts occurring during and activation
procedure. When activating, the SGSN has 30 seconds to activate the context before the
MS will retry the request. If within that 30 seconds the SGSN does not accomplish the
activation, an activate reject shall be sent to the mobile. A delay in activation could be the
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 85 October 2003
result of a failed Gn interface that causes the SGSN to try a new IP addressed obtained
from the DNS, no more resources available on the Gn interface to send the create PDP
context request to the GGSN, no more resources available on the GSC card to create the
local PDP context on the card, or the failure of the GSD card before the activation has
completed. Timeouts may also occur due to the fallback procedure implemented on the
Gn interface. The SGSN defaults to version 1 of the GTP specifications whenever a path
is used for the first time. After exhausting the retry mechanism, the fallback to version 0
of the GTP protocol may use all of the time allocated for activation. To decrease the time
needed to send the create PDP Context Request message to the GGSN, the Sgsn Gsc
n3CreateRequest retry attribute and the Sgsn Gsc t3CreateResponse timer attribute can
be adjusted downward.
4.4.8 SGSN Initiated Deactivations
The SGSN can initiate deactivations for stability issues. The stability issue may be
internal or external to the SGSN. Internal events requiring an SGSN initiated deactivation
include sessions on a GSD that failed or a session where traffic volume query counts
cant be retrieved from the GSD where it was activated. External events requiring an
SGSN initiated deactivation include an activation request from the mobile for resources
already used by that mobile for a present session, a cancel location received from the
HLR against a mobile that has an active session, or a disconnect mode received during an
XID negotiation where the QoS reliability class is either class 1 or class 2 or a failed XID
negotiation. These deactivations are recorded on the SGSN and sent in a message alarm
(Sgsn-Initiated Session Deactivations Cause Code Reporting: 7068 1029) raised against
the Gsc/ Sm component on a 15 minute interval.
4.4.9 Overload Conditions
See the Overload Control Monitoring section (3.2.6) for information on discarded PDP
Context Activate Requests during overload conditions.
4.5 CAMEL Activations
A Camel activation is a specialization to a regular activation that adds prepaid billing
functionality. Only Ge interface problems discussed in section (2.4) can be attributed to
Camel failures.
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 86 October 2003
MS
7
Frame Relay
E1/T1
GTL
WPDS
GSD
7
GSD (LLC)
GSD (LLC)
GSD
(SNDCP)
OC3
7K
SIC
ATM I/F
ATM MPE
4POC3
15
SIC
ATM I/F
ATM MPE
2PGPDSK
GSC/DNS
Agent
15
CG
SGSN
Global
TCP/IP
secure
network
2PGPDSK
SAS
15
SAS
GSC
SCDR
LA
7
Gn over
100Base
Bearer
Data
To
GGS
SIG
HP
TCP/IP
SS7
Netwo
rk
TCAP/MAP
GIPS
2PGPDSK
TCAP/MA
15
SC
I/O
LP
Gb
Gn
Ga
UDP/IP
Ge
Figure 25 Network view for CAMEL
4.6 SGSN and MS-Initiated PDP Context Modification
This SGSN and MS-Initiated PDP context modification procedures update specific
parameters of an already active PDP context. The SGSN-Initiated PDP context
modification is triggered by a change to the Qos in the HLR profile. The MS-Initiated
PDP context modification supports the modification of negotiated QoS. The QoS can be
upgraded or a downgraded.
4.6.1 Interfaces to Monitor
The interfaces used for PDP Context modification are the same as for activation except
for the Gr interface is used for the Insert Subscriber Data (ISD) message involved in a
HLR initiated PDP context modification; the main interfaces are Gb (2.2) and Gn (2.5).
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 87 October 2003
Monitoring the health of each interface is presented in both SGSN-initiated modifications
and MS-initiated modification counters.
The attempted SGSN- initiated context modifications are counted on Gsc/ Sm
sgsnInitModifyAttempts counter. Failures to modifications on the Gn interface or on the
GGSN itself are counted by the Gsc/ Sm sgsnInitFailAtGgsn counter.
The attempted MS-initiated context modifications are counted on the Gsc/ Sm
msInitModifyAttempts counter. Failures to modifications on the Gn interface or by the
GGSN itself are counted by the Gsc/ Sm msInitFailAtGgsn counter, while failures on
the Gb interface or on the mobile are counted by the Gsc/ Sm msInitFailAtMs counter.
4.6.2 Congestion During PDP Context Modification
Congestion on the SGSN could cause modification failures on the SGSN. The number of
failures caused by the SGSN is counted by the Gsc/ Sm msInitFailAtSgsn counter and
on the Gsc/ Sm sgsnInitFailAtSgsn counter.
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 88 October 2003
4.7 Short Message Service (SMS)
CGF
MS
7
Frame
Relay
WPDS
GSD
7
GSD (LLC)
OC3
7
SIC
ATM I/F
4POC3
15
SIC
ATM I/F
ATM MPE
2PGPDS
K
GSC
SI
H
SGSN
Global
TCP/IP
secure
network
TCP/IP
SIPR
SS7
Network
SMS
Initiated
2PGPDS
K
15
SAS
2PGPDSK
TCAP/MA
15
TCAP/MAP
GIPS
SMT-CDR
7
Gb
15
LAN
7
I/O
LP
Gr
Gr
Ga
UDP/IP
Figure 26 Network view for SMS
The Short Message Service (SMS) provides a means of sending messages of limited size
to and from GSM mobiles. Short messages, which are destined for or originated from a
fixed network node or another mobile, are transported through a Service Center that acts
as a store and forward center. A GSM PLMN needs to support the transfer of short
messages between Service Centers and mobiles.
Overload can occur for Mobile Originated Short Messaging when the rate of request from
the mobile exceeds the provisioned rate or the map client transactions are exhausted. In
either of those cases, a major message alarm (Mobile-Originated SMS Overload Alarm:
7068 1030) is raised against the Gsc/ Sms component to indicate overload on the Gs
interface. The alarm is only set if messages are dropped during a DCS cycle because of
an overload event.
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 89 October 2003
Overload can occur for Mobile Terminated Short Messaging when the rate of request
from the network exceeds the provisioned rate or the map client transactions are
exhausted. In either of those cases, a major message alarm (Mobile-Terminated SMS
Overload Alarm: 7068 1031) is raised against the Gsc/ Sms component to indicate
overload on the Gs interface. The alarm is only set if messages are dropped during a DCS
cycle because of an overload event.
SMS uses the following network elements: MS, BSS, SGSN, SIG, SMS-GMSC.
SMS can be monitored through the following application components within the SGSN:
GSC Map Client (3.2.5), Tcap/Map Stack (3.10).
SMS utilizes the Gd (2.3), Gr (2.6), and Gb (2.2) interfaces.
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 90 October 2003
4.8 Prepaid Short Message Service (PSMS)
MS
7
Frame
Relay
WPDS
GSD
7
GSD
(LLC)
OC3
7
SIC
ATM I/F
ATM MPE
4POC3
15
SIC
ATM I/F
ATM MPE
2PGPDSK
GSC
15
2PGPDSK
TCAP/MAP
15
CGF
SGSN
Global
TCP/IP
secure
network
SIG
HP
TCP/IP
SS7
Network
2PGPDSK
SAS
15
SAS
TCAP/MAP
GIPS
SMO-CDR
SC
Gb
Ge
LA
7
I/O
LP
Ga
Ge
UDP/IP
Figure 27 Network view PSMS
The Prepaid Short Message Service extends SMS feature by utilizing an external Service
Control Point (SCP) to manage and authorize prepaid SMS subscriber messaging. The
SCP supports requests by the Sgsn to increment, and decrement the subscriber account
balance when the mobile attempts to utilize the messaging service.
The PSMS uses the SMS Service (4.7); therefore the monitoring guidelines for SMS are
also relevant for monitoring the availability of PSMS.
PSMS uses the following network elements: Service Center, SMS-GMSC/SMS-IWMSC,
SIG, SGSN, BSS, MS, HLR, and SCP. Therefore each of these components and
interfaces to them must be functional in order to provide PSMS service to the mobile.
The following SGSN application components are relevant for monitoring the health of
PSMS: GSC SMS (4.7), GSC MAP Client (3.2.5), TCAP/MAP Stack (3.10).
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 91 October 2003
The following subsections provide information on monitoring the connection between
GSC PSMS and the SCP.
4.8.1 Monitoring Connectivity to SCP
A connection to the SCP must be in service for PSMS to function. The health of the
connection(s) between SGSN and SCP can be monitored by displaying the nccpState
attribute of the Gsc/ Psms Scp/ component(s). There must be at least one SCP
component in the dataExchange state for the service to be functional. If the nccpState is
null, connecting, idle, or releasing then PSMS is not in service.
If the nccpState is not equal to dataExchange the operator should display the
nccploginFailures attribute and the nccpLoginResponseTimeout attribute. If these
counters are actively pegging this means the PSMS is trying to log into the SCP and it is
not getting an Acknowledge message back from the SCP. The operator can display the IP
Server (GIPS) to determine if there is any packet activity on the protocol port (Gips/ Ip/
Tcp ) used by PSMS. The operator should also ping the router that is the next hop from
the SGSN to determine if it is responding. The ping should be done from the SGSN Ip
Server protocol port that is used by PSMS. If the ping is successful, the operator should
then ping the IP address of the SCP. If this ping is successful, it indicates the router
knows how to route the packet to the SCP and that the Login Request messages being
sent by PSMS on the SGSN are in fact reaching the SCP.
Assuming the packets are reaching the SCP, the operator should next check that the
clusterIds are provisioned correctly on the SGSN. These are provisioned on the Gsc/
Psms Scp/ component. The operator needs to verify that the clusterId is a unique number
across all the GSC instances that talk to a given SCP. In addition, the operator should
verify that the cluster ids provisioned on the SCP side are also unique for each GSC that
talks to that SCP. This will rule out the possibility of a problem that may have been
introduced during a provisioning change on the SCP or SGSN.
4.8.2 Monitoring Activity between the SGSN and SCP
The success rate of transactions between the SGSN and SCP can be obtained by
displaying the value of totalTransactionSuccesses vs. totalTransactionFailures on the
Gsc/ Psms component. If the failures are pegging more than the successes then further
steps should be taken to determine what is wrong. The failure counter is incremented
each time the response timer on the GSC expires before receiving a response message
from the SCP. This could be due to network congestion or messages are not reaching the
SCP.
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 92 October 2003
4.8.3 Monitoring For Congestion on Link to SCP
Congestion can be monitored from the PSMS by displaying the Gsc/ Psms
peakConcurrentTransactions attribute. This attribute shows the maximum number of
concurrent transactions the PSMS has realized during its operation. A transaction
represents a message that has been sent to the SCP and the SGSN is waiting on a
response. If this counter is going up it indicates congestion is happening at the CTP
protocol layer. The congestion problem is most likely at the SCP and should be
investigated.
4.9 Packet Flow Management (PFM)
The BSS Packet Flow Context (PFC) Feature offers the Aggregate BSS QoS Profile
(ABQP) functionality that can be shared by all the activated PDP contexts of the same
MS with similar QoS profiles.
PFM uses the Gb interface for (2.2) Qos negotiations.
4.9.1 Monitoring for Connectivity to the BSS for PFM
The Gb interface is used for the QoS negotiations between the PFM component on the
SGSN and the BSS. Beyond monitoring the Gb interface section for connectivity (2.2),
the PFM component provides some relative counters. The Gsc/ Pfm component provides
a t7RetryExpires operational counter that counts the number of failed messaging to the
BSS; an unusually high increase in this counter could indicate a loss of connection.
4.9.2 Monitoring for Activity to the BSS for PFM
The number of transactions between the SGSN and the BSS can be obtained by
displaying the value of downloadBssPfcRx, createBss,PfcsTx, createBssPfcAcksRx,
CreateBssPfmNacksRx, ModifyBssPfcsRx, ModifyBssPfcAcksTx, and
DeleteBssPfcsTx operational counters on the Gsc/ Pfm component. When those counters
increase, activity is occurring.
4.9.3 Monitoring for Congestion to the BSS for PFM
Congestion can be from either a congested link or from a congested BSS. Congestion on
the link or on the BSS could result in an increase in the Gsc/ Pfm t7RetryExpires
operational attribute due to messages being dropped on the link or on the BSS. A
congested BSS could also respond to a create PFC request with a not acknowledged
message that is counted on the Gsc/ Pfm CreateBssPfmNacksRx operational attribute.
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 93 October 2003
5 Summary of OAM Indicators
Area Alarms Counters
External Interfaces
Ga Interface
Connectivity
Activity
Congestion
Set 7068 1003
None
None
Sas/ cdrsXferCgf1, cdrsXferCgf2,
gtpMsgXferCgf1, gtpMsgXferCgf2
Sas/ openScdrs < 900,000
Sas/ openMcdrs < 300,000
Sas/ cdrXferCgf1Fail, cdrXferCgf2Fai,
gtpMsgXferCgf1fail, gtpMsgXferCgf2fail
Gb Interface
Connectivity
Activity
Congestion
Set 7068 1023
Set 7007 0000
Set 7007 1000
7007 2000
7007 2020
Set 7011 2000
Set 7011 5000
Set 7011 5002
Set 7011 5004
Set 7011 5010
MSG 7068 1020
None
Sggtl/ Nse/ Nsvc/ blocksFromPcu
Gsc/ Sms cpResponseExhaust,
rpResponseTimeouts
Sggtl/ Nse/Nsvc/ alivesFromPcu, alivesToPcu ,
aliveAcksFromPcu, alivesAcksToPcu
Sggtl/ Nse/ Ptpbvc/ blocksFromPcu
Sggtl/ Nse/ Ptpbvc/ resetsFromPcu, pdusToPcu,
pduFromPcu, flowCntrlPdusDiscarded
Gd Interface
Connectivity
Activity
None
None
Gsc/ Sms iwmscResponseTimouts
Tcap/ Map moFsmTimeouts , mtFsmTimeouts
Gsc/ Sms rpResponseTimeouts
Gsc/ Sms moAttempts, moFailNetworkFailures,
moFailUnidentifiedSubscriber,
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 94 October 2003
Congestion
None
None
moFailFacilityNotSupp, moFailCongestion,
moFailUnknownServiceCenter,
moFailInvalidSmeAddress,
moFailMissingSmsSubscription,
moFailOdbSubscriber, moFailOthers
Gsc/ Mc ofSmMsgs
Gsc/ Sms mtAttempts,
mtFailUnidentifiedSubscriber,
mtFailSubscriberAbsent,
mtFailSubscriberBusy,
mtFailSubscriberNotSmEquipped,
mtFailNetworkFailures,
mtFailMemCapExceeded, mtFailOthers
Gsc/ Mc tfsmMsgs
Gsc/ Sms moFailCongestion
Ge Interface
Connectivity
Activity
Congestion
Set 7068 1532
None
Set 7068 1519
Gsc/ Ssf totalTssfTimeouts
Gsc/ Ssf attemptedCamelDialogues,
unsuccessfulCamelDialogues
Gsc/ Ssf pdpContextsRedirected
Gsc/ Ssf currentCamelDialogues
Gn Interface
Connectivity
Activity
Set 0000 1000
Set - 7068 1540
None
Gsc/ Sm sgsnInitDeacts
Gsc/ Sm networkFailures
Gsc/ GtpM pathFailures
Gsc/ GtpM updatePdpReqAttempts,
updatePdpReqExhausted
Gsc/ GtpM peakGgsnPaths ,
currentTransactions
Gsd/ Gtp pdusToNetwork, pdusToNetwork
Gsc/ Sm sgsnInitDeacts
Gsc/ Sm networkFailures
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 95 October 2003
Congestion
None
Gsc/ GtpM currentTransactions,
maxTransactions
Gsd/ Gtp discPdusFromNetwork
Gsd/ Gtp pdusFromNetwork
Gsc/ Gtp incomingRequestsRejected,
maxIncomingRequests
Gr Interface
Connectivity
Congestion
MSG - 7068 1535
MSG - 7068 1032
None
Gsc/ Mc sccpServiceRequestTimeouts
Gsc/ Mc saiMsgs, uglMsgs , isdMsgs
Gsc/ Mc transLimitDiscards, rstMsgs
Gsc/ Hlrc recordsdToBeReset,
recordsWaitingForHlrConf
Tcap/ Map rfSmTimeouts
Gs Interface
Connectivity
Activity
Congestion
Set 7068 1523
None
None
Gsc/ Bssap sigRegisterFailures, vlrFailures
Gsc/ Bssap gsAssociatedCurrent,
gprsDetachMaxAttempts ,
explicitImsiDetachMaxAttempts,
implicitImsiDetachMaxAttempts ,
sgsnResetMaxAttempts
Gsc/ Bssap t8Timeouts, t9Timeouts,
t10Timeouts, t12Timeouts.
LICP Interface
Connectivity
Activity
Congestion
Set 7068 1525
Set 7068 1528
None
None
Liaf/ bufferOverFlows
Functional Components
GIPS
Connectivity
None
Vr/1 Ip/ tcp attemptFails, inErrs
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 96 October 2003
Activity
Congestion
None
None
Gips/ Ip/ inDelivers, outRequests
GSC
Instance
Connectivity
Congestion
Resources
Map Client
Overload Control
Set 7068 1025
Set 7068 1024
None
MSG 7068 1005
Set - 7068 1996
Set - 7068 1521
MSG 7068 1520
MSG 7068 1529
Set 7068 1511
MSG 7068 1496
Gsc/ Mc sccpServiceRequestTimeouts,
systemFailureRespRecv, uAbortMsgRecv,
uglMsgs, uglResponseMsgs, uAbortMsgSent
Tcap/ noticeRecieved
Gsc/ Mc currentTransactions
Gsc/Mc ofSmMsgs, ofSmResMsgs, rsmMsgs,
rsmResMsgs
Gsc/ cpuOvldAttachesDiscarded,
cpuOvldActivationsDiscarded,
subCountOvldAttachesDiscarded
GSD
Instance
Connectivity
Congestion
MSG 7068 1009
MSG 7068 1012
Set 7068 1025
Set 7068 1024
MSG 7068 1022
MSG 7068 1009
MSG-- 7068 1021
Gsd/ DBuff totalDiscardsDueToMaxBytes ,
totalDiscardsDueToMaxPackets,
totalDiscardsDueToBucketFull,
totalDiscardsDueToBvcBlocked
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 97 October 2003
Gsd/ Sndcp discardedNpdusFromMS
GTL
Instance
Set 7068 1025
DNS Agent
Connectivity
Activity
Congestion
Set 7068 1522
Set 7068 1530
None
None
DnsAg/ serverQueryTimeouts,
serverQueryFailures
DnsAg/ clientQueries, cacheHits , serverQueries
DnsAg/ serverPendingQueries
Inter-shelf
Connectivity
Activity
Congestion
Set 7039 1000
Set 7039 2000
Set 7041 0150
MSG 7041 0251
MSG 7039 4000
Set 7039 4001
MSG 70392001
Set 7039 5000
Atmif/ Vcc/ rxCell, txCell
Atmif/ Vcc/ txCellDiscard, txCellDiscardClp,
txFrameDiscard, txFrameDiscardC,
rxCellDiscard, rxCellDiscardClp,
rxFrameDiscard, & rxFrameDiscardClp
LAIF
Instance
Connectivity
Activity
Congestion
Set 7086 1026
None
None
Set 7068 1525
Logical Processor
Activity
Congestion
None
Set 7013 0022
Lp/ cpuUtil cpuUtilAvg, memoryUsage
normalRam
SAS
Instance
Set 7068 1026
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 98 October 2003
Hard Disk
Activity
Set 7068 1001
Set 7068 1002
Sas/ openScdrs , openMcdrs, closedScdrs,
smoCdrs, smtCdrs
Sgsn Acct cdrCapture
Gsc/ Gmm detachesSuccessful
Gsc/ Sm mobileInitDeacts, ggsnInitDeacts
TCAP and Map Stack
Instance
Connectivity
Activity
Congestion
Set 7068 1025
Set 7068 1523
Set 0000 1000
Set -- 7068 1515
Set -- 7068 1516
Set -- 7068 1517
None
MSG 7068 1495
MSG 7068 1533
MSG 7068 1534
MSG -- 7068 1536
Set 7068 1505
Set 7068 1506
Set 7068 1509
Set 7068 1510
Set -- 7068 1513
Set -- 7068 1514
Tcap/ invokeSent , invokeReceived
Tcap/ currentTransaction,
maxTransactionsPerSubsystem,
concurrentInvokesLowBySs,
concurrentInvokesAvgBySs,
concurrentInvokesHighBySs
Services
Mobile Attach
Activity
Attach Failure
Set 7068 1006
Set 7068 1531
None
Gsc/ Gmm currentlyAttached
Gsc/ Gmm attachRejPacketNetworkFailure,
attachRejSgsnCongestion, gmmAttRejStats
Gsc/ Mcc/ Mnc/ Lac/ Rac/ Cid/
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 99 October 2003
CPU Utilization
Max Subs reached
None
MSG 7068 1009
MSG 7068 1005
attachRejPacketNetworkFailurePerCell,
attachRejSgsnCongestionPerCellis,
gmmCellOper
Billing None
RAU/IRAU
Periodic RAU I/F
Intra RAU I/F
Inter SGSN RAU I/F
GMM T3 Tnl Timeout
Insufficient Resources
Excessive IRAU or RAU
Failure Indications
None
None
None
None
MSG 7068 1009
Set - 7068 1006
MSG 7068 1005
None
Gsc/ Gmm periodicIntraSgsnRaUpdate
Gsc/ Gmm normalIntraSgsnRaUpdate
Gsc/ Gmm interSgsnRaUpdateAccepts,
currentlyAttached
Gsc/ GtpM sgsnContextReqAttempts,
sgsnContextAcks, sgsnContextReqExhaust
Gsc/ Gmm t3Timeouts
None
Gsc/ Gmm totalIrauRejects, totalRauRejects
Activation and Deactivation
Interfaces
GSD Session Failure
DNS Failure
Set 7068 1532
None
None
Gsc/ Sm sgsnInitDeacts, ggsnInitDeacts,
mobileInitDeacts
Gsc/ Sm sgsnInitDeacts
Gsc/ Sm reactivationsRequested
DnsAg/ serverQueryTimeouts,
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 100 October 2003
Gn Connection Failure
GSD Resource Failure
GSC Resource Failure
Activiation Reject
SGSN Initiated
Deactivations
Overload
MSG 7068 1005
MSG 7068 1012
MSG 7068 1005
None
MSG -- 7068 1029
None
serverQueryFailures, serverQueryFailures
Gsc/ GtpM gprsGtpMgmtOp,
peakTransactions, currentTransactions
CAMEL Activations None
SGSN/MS PDP Context Mod
Interfaces
Congestion
None
None
Gsc/ Sm sgsnInitModifyAttempts
sgsnInitFailAtGgsn, msInitFailAtGgsn,
msInitFailAtMs
Gsc/ Sm msInitFailAtSgsn, sgsnInitFailAtSgsn
Short Message Service MSG -- 7068 1030
MSG -- 7068 1031
Prepaid Short message Service
Connectivity
Activity
Congestion
None
None
None
Gsc/ Psms Scp nccploginFailures,
nccpLoginResponseTimeout
Gsc/ Psms Scp totalTransactionSuccesses vs.
totalTransactionFailures
Gsc/ Psms peakConcurrentTransactions
Packet Flow Management
Connectivity
Activity
None
None
Gsc/ Pfm t7RetryExpires
Gsc/ Pfm downloadBssPfcRx, createBss,PfcsTx,
createBssPfcAcksRx, CreateBssPfmNacksRx,
ModifyBssPfcsRx, ModifyBssPfcAcksTx, and
DeleteBssPfcsTx
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 101 October 2003
Congestion None
Gsc/ Pfm t7RetryExpires,
CreateBssPfmNacksRx
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 102 October 2003
6 Glossary
ATM Asynchronous Transfer Mode
BSS Base Station System
BSSGP Base Station System GPRS Protocol
BVC BSSGP Virtual Circuit
BVCI BSSGP Virtual Circuit Identifier
CAMEL Customized Applications for Mobile Network Enhanced
Logic
CDR Call Detail Record
CGF Charging Gateway Function
CoS Class of Service
CP Control Processor
CPU Central Processing Unit
DNS Domain Name Server
DLCI Data Link Connection Identifier
FP Functional Processor
GGSN Gateway GSN
GIPS GPRS IP Server
GPRS General Packet Radio System
GSM Global System for Mobile communications
GSN GPRS Support Node
GTP' GPRS Tunneling Protocol Prime
GTP GPRS Tunneling Protocol
GTL GPRS Transport Layer
HLR Home Location Register
HP Hewlett Packard
IETF Internet Engineering Task Force
IP Internet Protocol
IRAU Inter-SGSN Routing Area Update
ITU International Telecommunication Union
LIAF Lawful Intercept Access Function
LICP Lawful Intercept Common Protocol
LIG Lawful Intercept Gateway
LLC Logic Link Controller
LP Logical Processor
SGSN Monitoring Guide Nortel Networks Confidential GPRS5.0
411-5221-050 Standard 02.01 103 October 2003
M-CDR Mobility Call Detail Record
MDM Meridian Data Manager
MG Media Gateway
MM Mobility Management
MS Mobile Station
MSA Mobile Serving Area
MSC Mobile Switching Center
NSAP Network Service Access Point
NSE Network Service Entity
NS-VCs Network Service Virtual Circuit
OAM Operations, Administration, and Maintenance
OS Operating System
PCU Packet Control Unit
PDP Packet Data Path
PDU Packet Data Unit
PNNI Private-Network-to-Network-Interface
PS Packet Switch
PtpBvc Point-to-point BVC
QoS Quality of Service
SAS SGSN Accounting System
SCCP Signaling Connection Control Part
S-CDR SGSN Call Detail Record
SCP Service Control Point
SGSN Serving GPRS Support Node
SIG SS7/IP Gateway
SigBVC Signaling BSSGP Virtual Channel
SM Session Management
SMS Short Message Service
SS7 Signaling System #7
SVC Switched Virtual Circuit
TCAP Transaction Capabilities Application Part
TCP Transmission Control Protocol
UDP User Datagram Protocol
UMTS Universal Mobile Telecommunications System
VLR Visitor Location Register
test
Family Product Manual Contacts Copyright Confidentiality Legal
GPRS
SGSN Monitoring Guide
To order documentation from Nortel Networks Global Wireless Knowledge Services, call
(1) (877) 662-5669
To report a problem in this document, call
(1) (877) 662-5669
or send e-mail from the Nortel Networks Customer Training & Documentation World Wide Web site at
http://www.nortelnetworks.com/td
Copyright ! 2003 Nortel Networks, All Rights Reserved
NORTEL NETWORKS CONFIDENTIAL
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its
employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the
same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly
authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as
progress in engineering and manufacturing may warrant.
* Nortel Networks, the Nortel Networks logo, the Globemark, Unified Networks, Passport, and DMS-HLR are trademarks of Nortel
Networks. GSM is a trademark of GSM MOU Association.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
Document number: 411-5221-050
Product release: GPRS5.0
Document version: Standard 02.01
Date: October 2003
Originated in the United States of America