Beruflich Dokumente
Kultur Dokumente
COPYRIGHT INFORMATION
© Copyright Hughes Software Systems, 2004
All information included in this document is under a licence agreement. This publication and its contents
are proprietary to Hughes Software Systems. No part of this publication may be reproduced in any form or
by any means without the written permission of
TRADEMARKS
All the brand names and other products or services mentioned in this document are identified by the
trademarks or service marks of their respective owners.
DISCLAIMER
The information in this document is subject to change without notice and should not be construed as
commitment by Hughes Software Systems. Hughes Software Systems assumes no responsibility or
makes no warranties for any errors that may appear in this document and disclaims any implied warranty
of merchantability or fitness for a particular purpose.
2
Contents
1. 3 G Wireless Networks 5
1.1. Management Modules 6
1.2. Challenges 7
1.3. 3G-SGSN Managers 8
1.4. Future Roadmap 8
1.5. Conclusion 9
1.6. References 9
3
3G SGSN Element Management
Figures
4
The 3G-SGSN is the network entity in a 3G GPRS
1. 3 G Wireless Networks network primarily responsible for managing the
mobility of a served GPRS capable UE in the 3G
Serving GPRS Support Node (3G-SGSN) is
mobile network. It also performs session management
an integrated system consisting of several
procedures for packet routing and transfer functions
modules. 3G SGSN provides a framework for
and is responsible for the delivery of data packets
complete element management intended for a
from and to the mobile stations within its geographical
field-deployable system. The 3G-SGSN Element
service area.
Management involves management of the
system as well as its constituent modules. The The figure below gives an architectural overview
paper summarizes element management of a 3G network, illustrating the important
framework of 3G-SGSN. It also highlights the components of the network and the logical interfaces
challenges involved in development of the between these components
element management framework and solutions
to various challenges faced
Other PLMN
Gp BG GSN
Billing
Other Center
SGSN
GERAN
BT Charging
Ga Ga PDN
Um S Border Gn Gateway
Gateway
BS
BT C
S Gb SGSN Gn GGSN Gi
Gc
Abis Gd
BT A Gr
S Gf
S
EI M-
R SMS SM
Gs HLR/AUC C S
Gateway E
C
F
UTRAN D E
IuPS
N
Uu B R D
N IuCS MSC E GMSC
C
N
B Iur
E/G
R PSTN
N N Other
Iub MSC
B C
5
3G SGSN Element Management
¡ Read status values and tables of the 3G-SGSN. 1.1.3. Fault Manager (FM)
¡ Retrieve (and possibly atomically reset) statistics
Any fault in the system is reported to the FM. The
data collected at the 3G-SGSN. FM takes necessary actions depending on the severity
¡ Report alarm conditions asynchronously. of the fault. The different levels of severity identified
¡ Detect faults and take necessary corrective for the faults reported are Critical, Major, Minor and
actions. Informational. The Critical faults trigger a restart of
the system. All the faults that occur in the system are
¡ Accept and perform imperative commands.
further reported to the Event Manager.
The basic principle here is that the public element
1.1.4. Event Manager (EM)
management interface will be accessible from the
system controller through a proprietary suite of APIs The EM receives information for various events
based on OIDs generated from SMIv2C MIBs. and alarms that have occurred in the system from the
Internally, each management function is available at respective modules or the FM. All the events and
the system level as well as on individual slots. alarms are reported to the configured external
element manager.
6
1.2. Challenges 3G-SGSN management API is defined for a basic
set of following 5 commands
3G-SGSN consists of several modules, which have
¡ Set Request – This API corresponds to any
been developed independently. All these modules
individually export different APIs towards the request received to set a particular management
management interface. The biggest challenge attribute to a particular value.
involved in managing the 3G-SGSN and its modules, ¡ Set Response – This API contains the response to
was to address these several disjoint management the corresponding Set Request received indicating
APIs through a common management point.
a success or failure. In case of success the value
To address this mammoth management task a configured is also present in the API.
uniform interface has been used to manage all the
¡ Get Request– This API corresponds to any
modules irrespective of the APIs exported by them.
request received to receive the value
The API interface for 3G-SGSN management has also
been adaptable enough to suite a standard corresponding to a particular management
The MIBs defined for 3G-SGSN and its constituent ¡ Trap – This API is used to asynchronously report
modules provided unique OIDs for each management occurrence of any event or alarm in the 3G-SGSN.
attribute. Internally 3G-SGSN addresses these OIDs
All the management attributes are identified by
from the level of 3G-SGSN OID. Hence it is possible to
their OIDs in the above APIs. Hence the management
modify the MIBs to generate OIDs for any network in
interface is independent of the API expected by the
which the OIDs for any management attribute below
corresponding modules. Each module has a small
the level of 3G-SGSN OID did not change.
encapsulation layer which translates these generic
Example: APIs (based on OIDs) to the module specific APIs and
vice-versa. This ensures that any changes in the
The PLMN Id attribute of GMM module MIB in the
module specific management APIs require minimal
3G-SGSN has the OID 1.3.6.1.4.1.303.1.1.1.1.1.7
change in the 3G-SGSN management modules.
defined for a 3G-SGSN with its MIBs defined for HSS
(OID 1.3.6.1.4.1.303). Internally 3G-SGSN processes The Iu interface is split into 2 parts: circuit
the OID after the prefix OID for HSS switched and packet-switched. The Iu interface is
(1.3.6.1.4.1.303). If this MIB is later defined for any based on ATM with voice traffic embedded on virtual
other network the prefix (1.3.6.1.4.1.303) can change circuits using AAL2 technology and IP-over-ATM for
but the suffix (1.1.1.1.1.7) will remain unchanged. data traffic using AAL5 technology. These traffic types
Hence there is no change required in the are switched independently to either 3G SGSN for
management functionality of 3G-SGSN when placed in data or 3G MSC for voice.
a different network.
7
3G SGSN Element Management
Generic API
8
for the system. A proxy MIB will be defined for 3G-
SGSN, which shall require a single configuration for
such attributes and internally 3G-SGSN management
modules can configure appropriate modules based on
the module specific MIBs.
1.5. Conclusion
Element management system of HSS 3G SGSN
provides a uniform management interface of all the
integrated stack components. Being MIB based NM
interface, this can be adapted to interface with a
standard NM framework
1.6. References
¡ HSS Internal Approach Papers for 3G-SGSN
Feature Development
¡ IETF RFC 1157 Simple Network Management
Protocol (SNMP). J.D. Case, M. Fedor, M.L.
Schoffstall, J. Davin. May-01-1990.
¡ 3GPP TS 32.106, 3G Configuration Management:
Concepts and Requirements
¡ 3GPP TS 32.111-1, 3G Fault Management
Architecture
¡ ITU-T Recommendation X.733, Alarm Reporting
Function
9
Hughes Software Systems is a key
supplier of communication
technologies for Voice over Packet,
Intelligent Networks and High-speed
Mobile Networks, and is fully focussed
on the needs of its customers to build
Next Generation Networks.
The comprehensive set of software building blocks from Hughes
Software Systems consists of both frameworks and protocol stacks for
the Voice over Packet domain.
Frameworks Stacks
Softswitch Framework MEGACO stack
Media Gateway Framework MGCP stack
Gatekeeper Framework SIP stack
SIP Server Framework H.323 stack
Mini Gateway Framework SIGTRAN stack