Introduction 3G
Introduction 3G
Lesson Objectives
Upon completion of this lesson the student will be able to:
WCDMA was developed in order to create a global standard for real time multimedia
services that ensured international roaming. With the support of ITU (International
Telecommunication Union) a specific spectrum was allocated – 2GHz for 3G telecom
systems. The work was later taken over by the 3GPP (3rd Generation Partnership
Project), which is now the WCDMA specification body with delegates from all over the
world. Ericsson has for a long time played a very active role in both ITU and 3GPP and
is a major contributor to WCDMA and the fulfillment of the vision of a global mobile
telecommunication system.
These efforts will result in a GERAN system architecture that employs a common core
network for WCDMA RAN and GERAN.
The GSM network shown in the figure below consists of the Core network and the Radio
Access Network. The end users are offered voice and low data transmission services.
The network provides the Control logic to setup, maintain and release connections and
the Connectivity capabilities that is the establishment of through connections between
the end user and the requested service. The nodes are interconnected using mainly
TDM techniques.
The traditional GSM network has been monolithic. The Monolithic Network Architecture
provides Network Control and Connectivity in a monolithic implementation, that is,
without any layering. This implies that Network Control and Connectivity are tightly
coupled and located in one physical node.
WCDMA Evolution Path
The WCDMA consists of the Core Network, the Radio Access Network and the Service
Network. The backbone is ATM based but IP is also possible.
Furthermore, both GSM BSS and WCDMA RAN systems are based on the principles of
a cellular radio system. The GSM Base Station Controller (BSC) corresponds to the
WCDMA Radio Network Controller (RNC). The GSM Radio Base Station (RBS)
corresponds to the WCDMA RBS, and the A-interface of GSM was the basis of the
development of the Iu-interface of WCDMA, which mainly differs in the inclusion of the
new services offered by WCDMA.
The significant differences, apart from the lack of interface between the GSM BSCs and
an insufficiently specified GSM Abis-interface to provide multi-vendor operability, are
more of a systemic matter. The GSM system uses TDMA (Time Division Multiple Access)
technology with a lot of radio functionality based on managing the timeslots. The
WCDMA system on the other hand uses CDMA (Code Division Multiple Access) which
means that both the hardware and the control functions are different. Examples of
WCDMA-specific functions are fast power control and soft handover.
WCDMA is a step further in the CDMA technology. It uses a 5 MHz wide radio signal
and a chip rate of 3.84 Mcps, which is about three times higher than the chip rate of
CDMA2000 (1.22 Mcps).
Examples are the re-use and evolution of the Core Network, the focus on co-siting and
the support of GSM handover. In order to use GSM handover the subscribers need dual
mode handsets.
For application developers and service providers the Service Network offers open APIs,
which allows developers to make and test applications and get them out into the market
quickly. The Service Network gives service providers an environment where they can
easily market their services to subscribers.
The Radio Base Station handles the radio transmission and reception
to/from the UE over the radio interface (Uu). It is controlled from the Radio
Network Controller via the Iub interface. One Radio Base Station can handle
one or more cells.
The Radio Network Controller is the node that controls all WCDMA Radio
Access Network functions. It connects the WCDMA Radio Access Network
to the Core Network via the Iu interface.
The RAB carries the subscriber data between the UE and the Core Network. It is
composed of one or more Radio Access Bearers between the UE and the Serving RNC,
and one Iu bearer between the Serving RNC and the Core Network.
The Interactive and Background RABs are so called ‘best effort’, i.e. no resources are
reserved and the throughput depends on the load in the cell. The only difference is that
the Interactive RAB provides a priority mechanism.
The RAB is characterized by certain Quality of Service (QoS) parameters, such as bit
rate and delay. The Core Network will select a RAB with appropriate QoS based on the
service request from the subscriber, and ask the RNC to provide such a RAB.
WCDMA Basic Architecture Concepts
Transport in WCDMA Radio Access Network
The WCDMA Radio Access Network nodes communicate with each other over a
transport network. The 3GPP specification provides a very clear split between radio
related (WCDMA) functionality and the transport technology, meaning that there is no
particular bias to any technology. The transport network is initially based on ATM, but IP
will soon be included as an option.
The platform used in all WCDMA RAN nodes is the Connectivity Packet Platform, CPP,
that is a flexible solution able to provide ATM and IP interfaces.
The transmission functions of the physical layer include channel coding and interleaving,
multiplexing of transport channels, mapping to physical channels, spreading, modulation
and power amplification, with corresponding functions for reception.
WCDMA RAN nodes control and utilize the air interface by using the standardized
spectrum bands for full duplex connections. The spectrum available for WCDMA/UMTS
is not the same in all regions, as shown here.
The European Radio communications Committee (ERC) Decided 30 June 1997, among
others, to designate the frequency bands 1900 - 1980 MHz, 2010 - 2025 MHz and 2110
- 2170 MHz to terrestrial UMTS applications. Japan and Asia Pasific. The spectrum
allocation in the Asian Pacific states will be similar to those in Europe. Therefore, similar
operator scenarios will appear, as in Europe.
USA and North America. The situation is different in North America. The introduction of
PCS services and the auctioning led to a split into licenses of 2 x 15 MHz and 2 x 5 MHz
up to 1990 MHz.
The specifications related to the spectrum and duplex techniques include two modes:
the FDD mode (Frequency Division Duplex) and the TDD mode (Time Division Duplex).
The FDD mode is the mainstream mode that operators are now deploying in WCDMA.
The TDD mode may eventually be deployed as well, as a complement to the FDD mode.
The Medium Access Control (MAC) protocol (Layer 2) offers logical channels to the
layers above. The logical channels are distinguished by the different type of information
they carry, and thus include the Dedicated Control Channel (DCCH), Common Control
Channel (CCCH), Dedicated Traffic Channel (DTCH), Common Traffic Channel (CTCH),
Broadcast Control Channel (BCCH) and the Paging Control Channel (PCCH). The MAC
layer performs scheduling and mapping of logical channel data onto the transport
channels provided by the physical layer. Also, for common transport channels, the MAC
layer adds addressing information to distinguish data flows intended for different
handsets. One major difference to GSM is the possibility to dynamically switch one
logical channel (data flow) onto different transport channel types, e.g. based on the
activity of the subscriber. This is called channel type switching.
The Radio Link Control (RLC) protocol (Layer 2) operates in one of three modes:
transparent, unacknowledged or acknowledged mode. It performs segmentation/re-
assembly functions and, in acknowledged mode, provides an assured mode delivery
service by use of retransmission. RLC provides a service both for the RRC signaling (the
Signaling Radio Bearer) and for the user data transfer (the Radio Access Bearer)
Radio Interface Overview
L3
The Radio Resource Control (RRC) protocol (Layer 3) provides control of the UE from
the RNC. It includes functions to control radio bearers, physical channels, mapping of
the different channel types, handover, measurement and other mobility procedures.
Because of the flexibility of the WCDMA radio interface, this is a fairly complex protocol.
Radio Interface Overview
Radio Network Functionality
For optimal operation of a complete wireless system i.e. from UE to Radio Access
Network (RAN) several functions are needed to control the radio network and the many
handsets using it. All functions described in this section, except for Handover to GSM,
are essential and therefore necessary for a WCDMA system.
Power control
The power control regulates the transmit power of the terminal and base station, which
results in less interference and allows more users on the same carrier. Transmit power
regulation thus provides more capacity in the network.
With a frequency re-use of 1, it is very important to have efficient power control in order
to keep the interference at a minimum. For each subscriber service the aim is that the
base station shall receive the same power level from all handsets in the cell regardless
of distance from the base station. If the power level from one UE is higher than needed,
the quality will be excessive, taking a disproportionate share of the resources and
generating unnecessary interference with the other subscribers in the network. On the
other hand, if power levels are too low this will result in poor quality.
In order to keep the received power at a suitable level, WCDMA has a fast power control
that updates power levels 1500 times every second. By doing that the rapid change in
the radio channel is handled. To ensure good performance, power control is
implemented in both the up-link and the down-link, which means that both the output
powers of the UE and the base station are frequently updated.
To achieve good system performance with a frequency re-use of 1 and power control,
soft and softer handover is required. Soft and softer handover enables the UE to
maintain the continuity and quality of the connection while moving from one cell to
another. During soft or softer handover, the UE will momentarily adjust its power to the
base station that requires the smallest amount of transmit power and the preferred cell
may change very rapidly.
The difference between soft and softer handover is that during soft handover, the UE is
connected to multiple cells at different base stations, while during softer handover, the
UE is connected to multiple cells at the same base station. A drawback with soft
handover is that it requires additional hardware resources on the network side, as the
UE has multiple connections. In a well-designed radio network, 30–40 % of the users will
be in soft or softer handover.
Introduction
Radio Interface Overview
WCDMA to GSM Handover (inter-system handover)
When WCDMA was standardized a key aspect was to ensure that existing investments
could be re-used as much as possible. One example is handover between the new
(WCDMA) network and the existing (GSM) network, which can be triggered by coverage,
capacity or service requirements.
Handover from WCDMA to GSM, for coverage reasons, is initially expected to be very
important since operators are expected to deploy WCDMA gradually within their existing
GSM network. When a subscriber moves out of the WCDMA coverage area, a handover
to GSM has to be conducted in order to keep the connection. Handover between GSM
and WCDMA can also have a positive effect on capacity through the possibility of load
sharing. If for example the numbers of subscribers in the GSM network is close to the
capacity limit in one area, handover of some subscribers to the WCDMA network can be
performed.
Inter-frequency handover (intra-system handover)
The need for inter-frequency handover occurs in high capacity areas where multiple 5
MHz WCDMA carriers are deployed. Inter-frequency handover, which is handover
between WCDMA carriers on different frequencies, has many similarities with GSM
handover.
The dedicated channel is used when there is much information to transmit, such as a
voice conversation or downloading a web page. It utilizes the radio resources efficiently
as it supports both power control and soft handover.
The common channel, on the other hand, is less spectrum efficient. One benefit is that
the common channel reduces delays as many subscribers can share the same resource.
Hence it is the preferred channel for the transfer of very limited information.
Admission control
As there is a very clear trade-off between coverage and capacity in WCDMA systems,
the admission control functionality is used to avoid system overload and to provide the
planned coverage. When a new subscriber seeks access to the network, admission
control estimates the network load and based on the new expected load, the subscriber
is either admitted or blocked out. By this the operator can maximize the network usage
within a set of network quality levels, i.e. levels depending on what kind of
service/information the subscriber wants to use.
Congestion control
Even though an efficient admission control is used, overload may still occur, which is
mainly caused by subscribers moving from one area to another area. If overload occurs,
four different actions can be taken. First, congestion control is activated and reduces the
bit rate of non real-time applications, to resolve the overload. Second, if the reduced bit
rate activity is not sufficient, the congestion control triggers the inter- or intra-frequency
handover, which moves some sub-white paper scribers to less loaded frequencies. Third,
handover of some subscribers to GSM and forth action is to discontinue connections,
and thus protect the quality of the remaining connections.
Introduction
Lesson Objectives
Upon completion of this lesson the student will be able to:
The MGW handles payload processing, traffic and signaling interworking between
networks.
The user traffic function generates a trough connection path by bridging the termination
points of the interconnected nodes.
The WCDMA adapted User Equipment (UE) are using AMR coding in speech
connections.
setting up
routing
controlling
terminating
It also manages the collection of information for charging and accounting and handles
the requests for Supplementary Services.
The MSC (Server or combined) contains the logic to perform inter and intra-MSC
handovers.
MSC is available in various configurations adapted to the operators needs.
The MSC/VLR is a configuration of MSC that handles call control and user plane for
circuit-based services. It includes the following logical nodes:
OSS-RC
OSS-RC is Ericsson’s sub-network manager, supporting centralized operation and
maintenance of the radio access as well as the core networks of both GSM and WCDMA
systems. OSS-RC is a solid step toward a completely integrated OSS-RC solution to
support the Core Network and Radio Access Network for both the GSM & WCDMA
Standards.
CS Domain Architecture
Core Network Circuit Switched domain, CNCS, as a part of WCDMA/GSM system, is
schematically shown in the following figure:
The Monolithic Network Architecture provides Network Control and Connectivity in a
monolithic implementation, that is, without any layering. This implies that Network
Control and Connectivity are tightly coupled and located in one physical node. Both
WCDMA access, based on ATM transmission technology, as well as traditional GSM
access, based on TDM transmission, are implemented. The figure above shows logical
relations between nodes within CNCS and towards other part of the CN.
The split CNCS domain architecture follows the concept of layered network architecture,
according to 3GPP standards, where the core network is divided into the two following
different network layers:
The Serving GPRS Support Node (SGSN) and the Gateway GPRS Support Node
(GGSN) are the main network elements in the GPRS part of the core network. Operation
and maintenance of a node is typically performed from a management client with the
node as a server, for example, from the node management terminal.
SGSN
The SGSN is a primary control node in the WCDMA Core Network providing mobility
and session control for the UE. The mobility function makes it possible for the UE to
move in the GPRS serving area by activating routing area updates and handovers
whenever required. The SGSN establishes a logical link towards the UE and a session
towards the Internet. It also enables the UEs to access all network services.
The SGSN contains the control logic to establish links and forward incoming and
outgoing IP packets addressed to/from an UE that is attached within the SGSN service
area. The WCDMA traffic is routed to SGSN and UE via RNC.
The SGSN serves all WCDMA subscribers that are physically located within the
geographical area, SGSN service area. An SGSN performs functions in packet calls,
similar to those an MSC performs for speech.
GGSN
The Gateway GPRS Support Node (GGSN) is the gateway between mobile radio core
network and other packet data networks, such as the Internet, corporate intranets, and
private data networks.
In this role, the GGSN is responsible for session management within the mobile network,
as well as for encapsulation and de-encapsulation of bearer traffic sent to and from
Serving GPRS Support Nodes (SGSNs).
From the external IP network’s point of view, the GGSN acts as a router for the IP
addresses of all subscribers served by the GSM/WCDMA network. Routing to the
correct SGSN and protocol conversion is also provided by the GGSN.
The GGSN in the current release of the GSM/WCDMA networks are using on J20
platform. This is a new one that has redundant routing engines, redundant switch system
boards, redundant power supplies, and redundant cooling fans, which significantly offer
increased reliability. Moreover, the J20 GGSN offers complete fault tolerance and as
well, an exceptional software stability ensured by separated routing engine and
forwarding engines.
The Mobile Number Portability function enables a mobile subscriber to retain their
subscriber directory number (MSISDN) when changing network operators. The
subscriber shown in the here changed the subscription from Operator A to B keeping the
same MSISDN.
With the RBS 3000 family, Ericsson provides products for single sector and multiple
sector configurations. The architecture of the RBS 3000 supports a number of
configurations and establishes a basis for future development of RBSs supporting macro,
micro and Pico cell structures.
The RBS 3000 models facilitates a cost efficient solution for different network
configurations based on different capacity, coverage, power supply source, space and
environmental requirements.
RXI 820/810
Ericsson’s RXI 820/810 Real-time Router has been developed in response to specific
requirements associated with a new generation of IP and ATM-based wireless networks.
The real-time IP routing and ATM aggregation features of the RXI 820/810 makes it ideal
for deployment in wireless access networks, allowing for a smooth migration from ATM
to IP. The RXI 820/810 can be used as:
The O&M Intranet enables the RNCs and RBSs to be controlled remotely using RANOS
and the RNC and RBS Element Managers. This means that all O&M activities, such as
Element Management of one or all the nodes in the WCDMA RAN, can be performed
anywhere on the O&M Intranet.
Lawful interception is the activity that allows law enforcement agencies to access end-
users in a packet switched service environment. This feature enables the operator to
fulfill national or state security organization requirements to monitor packet switched
traffic for specific end-users and/or terminals.
For lawful intercept the WCDMA System supports all relevant 3GPP and ETSI
specifications.
LI-IMS Architecture
The Operator’s network is used for connecting each Network Element (NE) to the
common LI-IMS. In the standard two new functions are introduced:
Mobile-PBN provides a comprehensive feature set for GSM and WCDMA networks,
including its key role in facilitating the transition towards a completely packet-based IP
transport for mobile networks.
Mobile-PBN interconnects all the Core Network nodes (such as MSCs, GSNs, HLRs,
and so on) and provides connections to the required external networks and elements
(including RNCs, O&M networks, GSM/GPRS networks, ISPs, GRXs, PSTNs, ISDNs,
Service Networks, and Corporate Access Networks).
The modular Mobile-PBN is both flexible and scalable. It consists of different module
types combined to provide various additional network functions and services. This highly
flexible design is standards-based, with all modules being pre-validated to function
independently.
Mobile-PBN is a scalable solution and caters for mobile operator networks of all sizes,
from small networks comprising only one site to very large networks containing hundreds
of sites.
While transport is one important solution element, Mobile-PBN comprises modular
solution components and provides additional functionality of great importance to a
mobile Core Network. The following functions are included in the Mobile-PBN solution:
A backbone solution for GSM and WCDMA networks (both for user and
control traffic), based on IP and (optionally) ATM
Secure Corporate Access
Secure Roaming Gateway services
Connectivity solutions for ISP and GRX networks
A security solution for the whole mobile Core Network protecting user data,
billing information, and network elements
Additional server nodes needed in the network, such as DNS and RADIUS
for address look-up and AAA
An O&M transport solution (including FM, PM, CM, charging, and LI traffic)
O&M applications for Mobile-PBN products (Mobile-PBN Management Suite
The Mobile-PBN solution segments the WCDMA mobile Core Network requirement by
site type and function, and comprises modules that can be combined to fulfill the specific
operator's service requirements.
Secondary Sites serve as distribution sites and are dual-homed to Primary Sites
providing connectivity to other PLMNs, the Internet, and corporate customers.
Secondary Sites aggregate traffic from Concentrator Sites to the Primary Sites.
Concentrator Sites aggregate and transport GSM and WCDMA subscriber traffic to
Primary and Secondary Sites.
The Mobile-PBN IP transport design is built using high-performance core IP routers and
Ethernet switches. ATM traffic is transported over the backbone using layer 2 transport
technologies, which allow ATM or Frame Relay connectivity over MPLS backbones. This
functionality is provided by Ericsson's AXI 520 IP Router family.
A pair of AXI 520 routers is located at each site, creating the core functionality of the
packet backbone network. These site routers are redundantly inter-connected via
Gigabit Ethernet links within the sites and via Packet-over-SONET or Synchronous
Digital Hierarchy (SDH) between the sites. All user traffic inside the core is directly SDH-
encapsulated MPLS traffic.
The edge functionality is provided by the same site routers, which are configured as
combined MPLS label edge routers (LER) and label switch routers (LSR). MPLS is used
to provide BGP-based VPNs. MPLS is also used in conjunction with standards-based
layer 2 VPN technologies to provide ATM and Frame Relay transport across the
backbone network. The AXI 520 routers support MPLS, either as LERs or LSRs, and
provide Class-of-Service-based packet forwarding.
The Mobile-PBN IP/ATM transport design uses the proven "IP/ATM Overlay" model. In
contrast to the "MPLS-integrated" approach, the overlay model uses a layered
architecture where the AXI 520-based IP/MPLS connectivity is transported on top of
ATM PVCs.
TNINF
TNINF enables communication between the different NEs in the WCDMA RAN and
between the WCDMA RAN and the CN. The Transport Network can be built either with
external ATM and Plesiochronous Digital Hierarchy (PDH) and Synchronous Digital
Hierarchy (SDH) equipment, or with direct connections, such as fiber lines, copper lines,
or microwave systems. All connections between NEs use ATM-based transport
protocols. The NEs can, therefore, be interconnected either through direct physical layer
transmission services, such as those provided by a PDH or SDH network, or through an
intermediate ATM network.
WCDMA NETWORK MANAGEMENT ASPECTS
Network management is the fundamental underlying layer of telecom management. It is
the set of functions required from a sub-network interface by telecom management to
enable controlling, planning, allocating, deploying, coordinating, and monitoring the
resources of the sub-network.
The functional areas of Ericsson's WCDMA network management include the following:
Fault Management
Fault management is the detection and correction of abnormal network operation. It
provides the means to collect and correlate alarms from the network elements and to
present this information to the network operator, in a clear and meaningful way. This
information is presented so that the appropriate corrective action can be taken as quickly
as possible. The operator's revenue is thereby preserved by minimizing the time that a
particular service cannot be provided due to a fault situation. Consequently, the end-
users QoS perception is enhanced.
Configuration Management
Configuration Management encompasses activities, such as providing and updating the
network elements with the data, parameter settings, and connectivity information
necessary for them to provide the services and functions within the network for which
they were intended. This also includes software update and maintenance.
Node deployment
These are the installation / routine configuration tasks normally carried out on a
managed element.
Connection management
This involves the deployment of associations across the network between managed
elements to carry traffic or signalling.
Inventory Management
Inventory management provides information on all equipment in the network. It presents
a view of hardware assets, software versions, and configurations. An example of
configuration information is a view of logical entities available to the network, such as
network connection terminations defined that are available for use.
Topology Management
This is a layered information tool that provides a view of all connections from physical to
logical that can be discovered from the network.
Software Management
Software management is the controlled handling (from a central point, that is, the
network management system) of upgrades and changes to the software versions
running on network equipment.
Performance Management
Performance Management provides functions to report upon and evaluate the behavior
and the effectiveness of the network or network element. Its role is to gather and analyze
statistical data for the purposes of monitoring and correcting the behavior and
effectiveness of the overall network, as well as that of the individual network elements. In
addition, Performance Management plays an important role in facilitating network
planning, dimensioning, provisioning, maintenance, and measurement of quality. In
particular, it can be used to assist in verifying customer SLAs.
Security Management
Security management is the control and monitoring of access to a network, its elements,
and the services it provides.
Element management provides the management interface from either a centralized point,
that is, the network management system, to many managed elements or directly to each
managed element.
Network Management Solutions
The WCDMA System consists of several sub-networks and a network management
solution is provided for each sub network. The integration of the specified functions for
each sub-network towards an operator's existing or new Telecom Management
infrastructure is performed at NMS (multi-vendor Network Management System). NMS
can be considered an integrator to the Customer and Service management or can
actually be used to perform these functions.
It is the NMS at the integration layer and the OSS suites of functions that Ericsson
provides, which are focused upon here.
OSS-RC
Ericsson Mobile Network OSS (OSS-RC) is the Network Management solution for GSM
and WCDMA Mobile Networks. Each product supports or implements one or more
Network Management functions).
OSS-RC provides a framework and all specified network management functions for the
GSM and WCDMA network management in the following ways:
The supported node list includes CPP nodes: RBS and RNC.
SNOS
SNOS provides network management for Service networks and many IP-based services
where a generic service configuration interface is required towards the service providing
managed elements. SNOS also supports the other specified network management
functions. SNOS is an enabler in the Service Network Framework (SNF). As such,
SNOS can manage any system that is SNF-compliant.
OSS-PB
OSS-PB provides network management for IP backbone networks. It supports all the
specified network management functions for such a network.
OSS-AT
OSS-AT provides network management for access transmission networks (SDH,
minilink..). Fault and performance data from OSS-AT can be escalated to OSS-RC for
the purposes of engineering towards faults or traffic from the telecom network
perspective down to the transmission layer. OSS-AT supports all the specified network
management functions for such a network.
Introduction
Lesson Objectives
Upon completion of this lesson the student will be able to:
First, there is a need for open environments that do not restrict operators in what they
can use or offer. There is also a need for a high degree of flexibility in managing services,
the third-party partners, and the charging arrangements between them. By implementing
open Application Programming Interfaces (APIs) the service network takes advantage of
the WCDMA Core and Access subnetworks functions and establishes sessions between
the end users and the requested service.
Secondly, to allow for future growth, the service network must be flexible and scalable.
The operators must enable rapid development and a subsequent launch of services.
However, the implementation requires in-depth technical knowledge, skill and business
expertise plus the ability to manage numerous interrelationships between third parties,
such as:
service providers
content providers
application developers
equipment suppliers and software vendors
These parties are the driving forces forming the sharing, content, and the provisioning of
services and applications.
The use of standards-oriented and product-neutral reference architecture is instrumental
in delivering well-designed service networks which possess the set of technical qualities
that is required to efficiently, flexibly and reliably deliver functionality in the service layer.
The architectural framework of the SNF is expressed using a set of architectural views.
Each view provides insight into a particular architectural aspect as:
domain
structure
system type
deployment
tier
data model
applied
Each view works in concert with the other views to capture the architectural statements
provided by the framework and, over time, to enable the addition of further statements.
In addition, the architectural rules and best practices, which are presented along
functional and qualitative lines, add support in helping to apply the architecture and
provide guidelines. These are held in the SNF rule and SNF guideline catalogs
respectively.
Domain view
The domain view describes an ideal boundary for the service network and defines how
the service network interconnects and collaborates with other systems present in its
environment.
The domain view captures and reflects the SNF view of the service network environment
and identifies the domains with which service networks generally collaborate, making
explicit the demarcation and interfaces between it and other domains.
Structural view
The structural view provides a set of abstractions that architects can use for uniformly
analyzing, modeling and expressing SNF architectures. Uniform expression is a
necessity for creating solutions from a portfolio of reusable systems.
The highest level in the view is a compound system, which consists of one or more
systems. Much of the architectural guidance in the SNF comes from what it terms the
system level, which defines a system as a logical and modular building block that
provides certain services over established interfaces. A set of systems works as such a
building block to deliver the services that are available in a service network.
A service is an object that represents a collection of functionality accessed via protocols.
The service is the SNF mechanism for indicating interfaces. One or more services may
be provided from a compound system, a system or a component.
Finally, within this view, the service contract is the description that specifies how a
service can be accessed. It is a combination of the functionality in the service and the
protocol transfer mechanisms. The service contract is independent of, and is not
connected to, a specific compound system, system or component. Normally the Service
Contract is open in form of an API. The figure here shows the structural view for an IP
Multimedia service provided by an operator.
System type view
The system type view introduces and specifies a recurring set of SNF systems, which
are a set of logical building blocks for creating service networks. Each system type plays
a special role in a service network and is specified in terms of responsibility and service
(interface).
Solution architects may thus refer to system types as specifications for logical building
blocks within the service network.
Deployment view
Much of the SNF architecture rests on the assumption that Internet protocol (IP)
connectivity is present in the complete solution. Core network (CN).
The IP network is a key aspect of the deployment environment for every system in the
service network. The SNF deployment view provides guidance for ensuring that the IP
network possesses a set of common services and qualities on which every deployed
system can rely. Examples of common services include naming, addressing, routing,
load-balancing, firewall and security gateway services. Likewise, common qualities
include performance, scalability, flexibility, security, and high availability.
Figure here presents a conceptual depiction of how systems are deployed to, and make
use of, an IP network with various common services and qualities.
In this example, the application servers have been deployed on VLAN 1, whereas the
gateways have been deployed on VLAN n.
Tier view
The use of N-tier architectures is an accepted and proven approach toward partitioning
or organizing distributed computing architectures that require high levels of scalability
and availability. The SNF recommends that N-tier architecture should be employed for
organizing systems into scalable and available solutions in a distributed computing
environment.
The various tiers include client, presentation, business, integration, resource, and data.
The client tier is concerned with every device that accesses systems or applications.
Data model view
Data modeling is an important part of all architectural efforts. The SNF data model view
specifies a uniform data model for user and service-related data and associated
provisioning within the service network. The SNF data model has been designed:
the central provisioning entity (CPE), CDS, and system component registry
(SCR) - to achieve common provisioning of SNF systems that require
provisioning
the central management entity (CME) collaborating with all other SNF
systems - to achieve common management
the common charging entity (CCE) collaborating with all other SNF systems
- to achieve common charging
the border gateway (BGW), central authentication entity (CAE), and central
session entity (CSE) - to achieve single sign-on for HTTP
Introduction
Lesson Objectives
Upon completion of this lesson the student will be able to:
In WCDMA Systems, mobility management depends on the state of the UE. Basically,
when the UE is attached, it can be either Idle or Connected.
When the UE is Idle, the mobility management is mainly controlled by the UE itself. The
UE will read system information and use it to determine when to perform the UE internal
cell-reselection procedure and when to report location changes to the network. The
network will respond to such information from the UE by updating stored location
information, which is used to reach the UE from the network side, that is, in case of a
mobile terminated session set-up request.
The idle mode mobility management, which includes Roaming and Cell-Reselection,
largely involves the UE and the WCDMA Core Network, that is, the WCDMA Radio
Access Network is not involved except for transporting the signaling messages between
the UE and the Core Network, and broadcasting of cell-information which guides the UE
in the cell-reselection procedure. The WCDMA Network provides functionality to support
Inter- and Intra-PLMN Roaming and Cell-Reselection within the WCDMA Radio Access
Network. Inter- and Intra-PLMN Roaming and Reselection are also supported to and
from GSM.
In connected mode, however, the Core Network relies on the Radio Access Network to
track the UE and will, except for special cases, forward and receive user data to/from a
fixed anchor point (an RNC) in the Radio Access Network. The WCDMA RAN is in
charge of assigning resources for the connection. The RAN can assign either common
channel resources or dedicated channel resources.
Mobility Support
Mobility management is guided by a state machine, which is present in the CS core
network domain and in the PS core network domain. These two state machines are
independent, which means that no relation between the states in each domain exists,
except if it is forced by the UE or application implementation to act as such.
The state in each state machine (domain) is stored in both respective network domains
and in the UE. The network domain state and the UE state is synchronized, except for
the signaling delay between the UE and the core network domain. The basic principles
and the implied symmetry between the two domains are outlined in the figure below
Mobility is managed by separate states in the PS domain and the CS domain of the core
network. The state value is maintained in the core network serving nodes (MSC and
SGSN) and in the UE.
Each state machine has three different states: detached mode, idle mode, and
connected mode. For the two state machines, these states are referred to as CS MM
(Circuit-Switched Mobility Management) state and PMM (Packet Mobility Management)
state. For example, a UE can be in CS MM connected mode and PMM idle mode at a
certain time, meaning that the CS state machine is in connected mode and that the PS
state machine is in idle mode.
Detached mode means that the UE does not communicate with the respective domain in
any direction. If the UE is switched off it will be detached in both domains. Depending on
the UE implementation, attachments can be made to either domain or both.
Attaching to a domain implies that the UE registers with the respective domain via a
radio control channel. This registration cannot be initiated from the network, due to the
fact that in detached mode the UE is not reachable by the network.
Mobile network user making a call to a user belonging to the same network
Mobile network user making a call to a user belonging to another network
(can be both another mobile network or a fixed network)
User belonging to another network making a call to a mobile network user
Mobile network user making an emergency call
Dual Tone Multi Frequency (DTMF) tone generation during an ongoing call
The Traffic Control in the MSC gives an almost unlimited number of routes, alternative
routes, and elements per route. Certain calls (for example, emergency calls, calls to a
certain B-number) can be provided with a higher priority than others when allocating
resources such as processor capacity or outgoing trunks.
Calls to a mobile user are always routed to a Gateway MSC (GMSC). The GMSC
analyzes the received MSISDN number and interrogates HLR for routing information.
MSC/VLR receives a request for roaming number provision from HLR. The MSC/VLR
identifies the mobile user by means of the IMSI, allocates a roaming number, and sends
it back to HLR. The roaming number is only used during the routing and is released
immediately upon reception of an incoming call in the MSC/VLR. When the routing
information is received in GMSC the call re-routing is started and the call is set up
through the network to the MSC in which the mobile user is located.
The emergency call can be routed to the closest emergency centre by defining an
emergency area category per cell, which then can be used for call routing in the MSC.
DTMF tone generation makes it possible for a mobile user to send digits from the User
Euipment (UE) to a remote end. In this context, "digits" refers to the digits 0 to;9, as well
as the characters A, B, C, D, * and #. Each digit is represented by a specific tone
(frequency). The DTMF tones are not generated by the UE, but by hardware in either the
MSC or the MGW. This is done to avoid the speech coder distorting the tones. When the
mobile user enters a digit on the UE, a signalling message is sent from the UE to the
MSC, which initiates tone sending.
From an IP point-of-view, the WCDMA PS network can be divided into the following
parts:
Supplementary Services
The Supplementary Services supported in WCDMA system are the following:
A multimedia messages consists of one or more media elements (text, picture, photo,
video, animation, speech, audio, and so on). A multimedia messages can, for example,
be a photo or picture post card annotated with text and/or an audio clip.
MMS represents the total solution, which consists of the MMS-enabled handsets, the
Multimedia Messaging Center (MMC), plus possibly additional MMS applications,
Multimedia Library (MML), Multimedia Processor (MMP) and Multimedia Client Proxy
(MMCP).
MMC
The MMC implements the network side of MMS, as well as making it possible for an
operator to offer MMS to its mobile subscribers.
The MMC can be deployed in any mobile network that supports WAP. The following
figure shows an example of the MMC and its basic components, as connected within a
mobile network for message traffic.
The different components of the MMC are described below.
MML
The MML provides a long-term repository, where multimedia messages and content may
be stored for future use. The Multimedia Message Composer feature facilitates
composing and submitting multimedia messages by WAP and web users without the
need for a MMS-capable phone.
The long-term MML repository can be used by MMS users to store not only their
multimedia messages, but also their pictures and images, audio, text, and video content.
Multimedia messages can be forwarded to a user's personal storage area, the MMBox.
Alternatively, content may be uploaded from a PC to the MML using the web interface.
Content may be organized in different albums and can be used to create new multimedia
messages. Subscribers can have both private and shared albums. A user can invite
guests to visit shared albums. Private albums can only be accessed by the album owner.
Operators and content providers can store multimedia content within the MML for use by
(sold to) subscribers. The operator may have selected content providers automatically to
download multimedia content into the MML using a specific VASP interface. The user
then accesses the MML through the web or WAP interfaces to browse for media content.
MMP
The MMP enables applications to send multimedia messages to any device, regardless
of media format, screen colors, or size. It provides media processing and transcoding for
purposes of media enhancement, as well as non-MMS-capable legacy terminal
compatibility. Due to the fact that naive transcoding may result in unreadable content on
the small screen of a mobile terminal, MMP enhances the image to correct such faults
when the content type is identified.
MMCP
The MMCP provides the intelligence to determine whether a multimedia message is
being sent to a non-MMS-capable mobile terminal. Furthermore, it will notify the recipient
of a location from where the message can be retrieved. It provides the non-MMS-
capable mobile terminal user with the ability to read multimedia messages via an
Internet browser and/or WAP micro-browser.
Streamed Services
The Streaming Services is a function designed for the delivery of Digital Media Content
using streaming, progressive download, and download. Streaming occurs when the
content is consumed during the transport with a minimum of delay. The progressive
download mechanism uses repetitive client HTTP GET request on parts of the target file.
This enables consumption to start prior to the complete file being transferred.
Consequently, progressive download offers a similar experience for the user as
streaming, with the difference being a larger start-up delay. Download happens when the
consumption of the content takes place after the complete file is downloaded.
Digital Media, such as news, music, sport, and movies, encoded in 3GPP, MPEG-4, and
Real Media formats are supported and can be transferred to mobile clients over service
and core networks, as well as UMTS radio networks.
The Quality of Service (QoS) network bearer service and the streaming class is
supported. This allows the operator to assign a fixed radio resource usage to each user
and each session. In addition control mechanisms are present in the service and core
network that secure the transport of the streamed content and keep interruptions to a
minimum under unreliable conditions.
In addition access to streaming service is also supported through a circuit-switched
bearer from 3G.324M mobile terminals through an interworking unit connecting to the
streaming service.
The user scenario starts with the retrieval of a link to media content. This can be
achieved using WAP/WEB, SMS/MMS, or other delivery methods. The next step is to
attach to the content server with an HTTP request in order to retrieve the SDPnfile,
which holds the information about the media file or stream. The information tells the
streaming client in the UE how to retrieve the media. The client then initiates the QoS
set-up in the radio and core network. When QoS is established, the client retrieves the
media content from the content server.
User' subscribed Quality of Service is checked via reading in the subscriber database.
Maximum subscribed bandwidth is checked.
Streaming Server
Streamed Services function streaming server is part of the ECDS function. It stores and
delivers media content. The delivery can be performed from the streaming server itself
or through a proxy function allowing content to be retrieved from the outside of the
operator domain. The streaming server supports the 3GPP standards, as well as media
content of Real format. An operator may choose to provide 3GPP content, Real content,
or both. Therefore, it supports both protocols and content formats of the 3GPP standards,
as well as RealAudio® and RealVideo® content over the RealNetworks® Data Transport
(RDT) protocol.
Charging Management
The charging management function for Streamed Services is controlled by the ECDS. It
supports a standardized and configurable file-based charging in the form of periodically
generated Charging Data Records (CDRs). It also supports postpaid charging, Hot
Billing, and Real-Time charging over DIAMETER and PARLAY. Various events, such as
abrupt termination, trigger the generation of charging data. Consequently, the charging
module ensures that a user does not get charged for services that are not received.
The GGSN initially generates a Charging Identifier at set-up of the PDP context. If this is
unavailable, the ECDS can generate a Charging ID. Also, the ECDS generates
identifying tags to the sub sessions within the PDP context. This information allows
partial records to be incorporated in CDR files, thus supporting a flexible payment model
towards end-users and content providers. This feature can also be used to make sure a
user is not charged for data volume or airtime when premium services are accessed.
In case of a failure in CDR generation, the ECDS can be configured to either continue
without charging or to refuse all new connections until the error condition is cleared.
Loss of connection to the billing system can be notified by a log file entry in the O&M
system.
Streaming Client
Streamed Services is designed for terminals supporting transparent end-to-end Packet-
Switched Service (PSS), 3GPP 26.233, 26.234. Streamed Services does not include
terminals.
Videotelephony
The 3G videotelephony function enables end-to-end multimedia communication over the
circuit-switched domain in the WCDMA network.
The standard for videotelephony over 3G networks has been set by 3GPP in release 99
and is called 3G.324M. This standard is based on the ITU-T H.324 standard and
describes how 3G.324M multimedia services can be implemented in the WCDMA circuit-
switched domain with interworking with the IP domain through H.323/SIP. The figure
below outlines the reference architecture for 3G videotelephony.
Call Set-Up
When setting up a 3G videotelephony call a transparent 64K kbps circuit-switched
bearer has to be first set up on the air interface and through the core network and then
on the B-terminals air interface, in the case of the mobile-to-mobile call. In the case of
interworking with another network, typically Internet, the 64 kbps circuit-switched bearer
is set up to the video gateway system ViG. The setup of the video communication is
subsequently done end-to-end using in-band signaling between the two terminals or
between a terminal and the ViG using the H.245 protocol according to the 3G.324M
standard.
During call setup the terminal will send information in the setup message in DTAP
indicating that a 64kbps circuit-switched bearer for unrestricted digital information (UDI)
is to be established. It will also be indicated that it is a video telephony call, which will
use H.245/H.223 signalling. As a result, the core network is able to charge the call
accordingly, and in case of interworking with other networks, also can connect the ViG. It
should be noted that this low layer information in the setup message from the terminal
will be transparently sent through the core network towards the B-terminal, in order for
both sides to understand that this will be a video call. Further information and call setup
will be achieved through in-band signalling.
The 3G.324M mobile terminal accesses the ViG network through a 64kbps Circuit-
Switched Data connection in the 3G mobile network, indicating that a multimedia service
is requested. After call setup the media streams will be sent directly between the clients
and the MGW.
Subscribers to the ViG system are associated in the network with two unique identifiers
that can be used for user identification and call routing. They are, as follows:
A ViG user name (H.323 ID), with the format of an e-mail address
(mandatory)
A personal E.164 telephone number (optional)
The routing of calls between 3G.324M mobile terminals and H.323/SIP terminals will be
carried out in the core network. Roaming call cases can, therefore, be supported by
configuring routing data in the core network, provided that the ViG is accessed using a
public number (E.164).
Service Network
The HLR provides the administrative means to provide mobile subscribers with the
appropriate basic service (Synchronous General Bearer Service - BS30) to handle
multimedia calls.
Charging
In the 3G Video Telephony function both pre-paid and post-paid charging is supported.
The MSC and the ViG will generated the necessary charging information for a
multimedia call.
The Charging Data Record (CDR) will contain an indication of whether it is a multimedia
call or not. Based on this information, it is possible to apply different tariffs for 3G
videotelephony.
Browsing
Browsing enables a user to access applications and services on the Internet, Mobile
Internet, and corporate intranet using standard browsers, which support a variety of
mark-up languages.
The browsing system function is based on the Mobile Internet Enabling Proxy (MIEP).
As well as incorporating the functionality of a WAP gateway, MIEP serves as the bridge
between the mobile network and the applications and services. MIEP can be seamlessly
integrated with the core network.
In addition to MPS, LBS includes content and application middleware, as well as a range
of professional services to ensure that location-based services can be quickly and
smoothly integrated into the operator's mobile network. MPS supports WCDMA (MPS-U).
MPS-U consists of the Gateway Mobile Positioning Center (GMPC) and network
features in the form of software extensions for the MSC/VLR, HLR, and RNC. The
GMPC is the Ericsson implementation of the standardized node Gateway Mobile
Location Centre (GMLC). MPS-U delivers the position of the subscriber to the
applications, referred to as LoCation Service Clients (LCS Clients). The position co-
ordinates are then used by LCS clients, which are provided either by the operator or by
service providers on the Internet.
The LCS client is not a part of the MPS, but rather a part of the LBS solution. The LCS
Client contains applications that make use of the positioning information. It
communicates with the GMPC through a standardized Application Programming
Interface (API), that is, the Mobile Location Protocol (MLP) protocol according to Open
Mobile Alliance (OMA). The standardized API makes it easy for third party application
developers to build new services. MLP positioning requests from the LCS client to the
GMPC and positioning answers from the GMPC to the LCS client are exchanged. The
GMPC can handle connections from multiple LCS clients simultaneously.
IN Services
The Intelligent Network (IN) is a key element in the Service Network Architecture. It
provides the means to introduce innovative and competitive telecom services in a cost-
effective way with a short lead-time. The following are examples of available services for
WCDMA:
The Virtual Private Network (VPN) service provides the corporate customer
with a private numbering plan for fixed and mobile end-users within the
public telephone network.
The Information & Business (I&B) service can operate as one or more of
three services: Free phone, Premium Rate and Universal Access Number.
The Intelligent Router & Data Server (IR&DS) is a framework containing
several IN regulatory services including, for example, Route selector,
Access screening, and Number Portability.
Number portability means that the end user can keep the same telephone number when
changing from one Service Provider to another.
The Intelligent Network is an architecture where call control logic is separated from the
switches into a centralized node (the Service Control Point [SCP]) that communicates
with the switching platform (the Service Switching Point [SSP]) using a service-
independent protocol (for instance, CS1, CS1+, CAMEL). Service data is contained on
the Service Data Point (SDP) and management of the IN services is done through the
Service Management System (SMAS). The Intelligent Peripherals (IP) or IVRs are the
nodes or devices that perform the Specialized Resource Function (SRF) within the IN
architecture.
The signaling towards the SCP from the other IN nodes can either run over a classical
SS7 network or using SIGTRAN.
SCP
The Service Control Point (SCP), which holds the SCP function (SCF), is the heart of the
Intelligent Network where every IN call asks the SCP for instructions on how to execute
the IN service. In WCDMA two different implementations of the SCP are supported, AXE
based (SCP) and TSP based (INS).
The AXE SCP supports co-location with Ericsson's AUC, FNR, HLR, and MSC products.
Special consideration is needed if gsmSSF and gsmSCF are to be located in one
physical node when using CAMEL.
The TSP-based INS middleware offers an open Customer Administration Interface (CAI)
towards the customer administration system. The INS also supports generation of Call
Data Records (CDR) directly from the SCP. It also supports an interface to allow
services to retrieve and update call rating data (prepaid account data) stored in the
Rating Engine (RE).
SSP
The Service Switching Point (SSP) executes tasks for the SCP. Its main functions are to
switch IN calls through the network, play recorded announcements, trigger and invoke IN
calls, generate charging details and very important control of network congestion. The
SSP function (SSF) is part of the MSC/VLR (gsmSSF) and the SGSN (gprsSSF). The
MSC/VLR also supports the Specialized Resource Function (gsmSRF), which is used to
order the announcement machine to play announcements.
SDP
The most important task for the Service Data Point (SDP) is to provide the Intelligent
Network with high capacity data storage with full data integrity, and is accessible via a
well-defined interface. It interfaces the SCP over SS7 and the SMAS system via a Binary
interface (BIF) over TCP/IP.
SMAS
The Service Management System (SMAS) is Ericsson's product for installing,
provisioning, and managing IN services towards the AXE-based SCP. SMA Base is a
set of tools and applications that give service providers a common platform for service
provisioning and end user control of IN services.
SDE
The Service Development Environment (SDE) is an application for developing IN
services for the AXE SCP.
SDK
The Service Development Kit (SDK) allows operators to develop their own services with
the IN capabilities offered by the INS and TSP platform.
Principles for service development for the Ericsson Intelligent Network Server (INS) are
based on Openness, Industry Standards, and Reuse of software components.
Openness means that operators can easily develop their own service logic to execute on
the INS. Industry standards such as the Rational Unified Process (RUP) for software
engineering process support, the Unified Modeling Language (UML) for Visual Modeling,
and the Java programming language for implementation are used for service
development.
Service development is performed outside the actual INS node, on standard computer
hardware and software platforms. After the service logic has been developed, it can be
deployed onto the INS target node.
Single Sign On (SSO)
Single Sign On (SSO) allows users to access content from various sources and content
providers without making a manual authentication and authorization each time. If the
user, for example, wants to retrieve a multi-media message or watch a football clip, the
network will take care of authentication and authorization.
The SSO solution depends on the business model of the operator. Several business
models are developed the most important are the Walled Garden SSO and the HE-
VASP SSO (Home Environment Value Added Service Provider ).
On the Internet, a Walled Garden refers to a browsing environment that controls the
information and Web sites the user is able to access. This is a popular method used by
ISPs in order to keep the user navigating only specific areas of the Web, whether for the
purpose of shielding users from information -- such as restricting children's access to
pornography -- or directing users to paid content that the ISP supports.
In the Walled Garden SSO business model, the operator provides all services. An end-
user can then use SSO for the services within the walled garden for which the user has
a subscription and for which the operator has activated the service.
The SSO Infrastructure consists of the nodes AAA, HTTP Proxy, and MIEP, and also an
SSO SDK.
WCDMA Main Interfaces and Signaling
Protocols
Uu interface
Iu interface
Mub interface
Mur interface
Circuit-Switched Interfaces:
Iu CS interface
C interface
D interface
F interface
CAMEL interface
Mp interface
Packet-Switched Interfaces:
Iu PS interface
Ge interface
Gi interface
Gr interface
Gp interface
Gom interface
Lg interface
Lh interface
Circuit-Switched Interfaces
Iu CS interface
The WCDMA RAN - Circuit-Switched interface is used to carry the user plane (user data
as speech and CS data) and control plane (signalling as information concerning
WCDMA RAN management, call handling, and mobility management).
In a layered architecture, the Media Gateway manipulates and transports the user plane
part of the Iu interface. The control plane part of Iu is relayed to the appropriate MSC
(which acts as the Media Gateway Controller).
C interface
In the Circuit-Switched (GMSC) - Authentication, User Databases, and Provisioning
(HLR) interface, the MAP protocol is used to perform the interrogation needed to set up
calls to a mobile subscriber. To forward a short message to a mobile, the Circuit
Services interrogates the User Databases to obtain routing information.
Signaling on this interface uses the Mobile Application Part (MAP), which, in turn, uses
the services of Transaction Capabilities. See TS 29.002.
D interface
On the Circuit-Switched (VLR) - Authentication, User Databases and Provisioning (HLR)
interface, the MAP protocol is used to exchange data related to the location of the
mobile station and to the service management of the subscriber.
Signalling on this interface uses the Mobile Application Part (MAP), which, in turn, uses
the services of Transaction Capabilities. See TS 29.002.
F interface
On the Circuit-Switched (MSC) - Authentication, User Databases and Provisioning (EIR)
interface, the MAP protocol is used to exchange data, in order that to verify the status of
the IMEI retrieved from the Mobile Station.
Signaling on this interfaces uses the Mobile Application Part (MAP), which in turn uses
the services of Transaction Capabilities. See TS 29.002.
CAMEL interface
CAMEL (Customised Applications for Mobile network Enhanced Logic) provides the
mechanisms to support operator-specific services that are not covered by the
standardised GSM services and also when roaming outside the HPLMN by using
Intelligent Network (IN) principles.
Mp interface
Inter-working with the PSTN network is achieved by TTC ISUP, standard ETSI TUP+
and market variants such as SSUTR2 and CAS R1 signalling. ISDN inter-working is
supported via ETSI PRA and BRA.
Packet-Switched Interfaces
Iu PS interface
The WCDMA RAN - Packet-Switched interface is used to carry the user plane (user data)
and control plane (signalling as information concerning mobility management, session
management, and packet data transmission).
Ge interface
The Ge Interface is the logical interface between the SGSN in Packet-Switched and the
SCP in Application Enablers for real-time support of a users activity in the network. In
other words, it allows the SCP to control how and if the Mobile Station may connect to
the network, as well as its network resource usage. One example of SCP control is the
prepaid functionality.
Signalling on this interface uses the Mobile Application Part (MAP), which, in turn, uses
the services of Transaction Capabilities (TCAP). See TS 29.002.
Gi interface
This interface connects the PLMN to external public or private packet data networks.
The Gi interface is used for GGSN control signalling towards ISP servers located in IP
networks, such as the ISP network. The Gi interface is also used for transportation of all
end user IP data between the mobile network and external IP networks.
Gr interface
The Gr interface is the Packet-Switched (SGSN) interface towards the Authentication,
User Databases, and Provisioning (HLR). The interface is used for storage/retrieval of
subscriber data. It is also used to update the HLR of the location information of the MS.
Signaling on this interface uses MAP, which, in turn, uses the services of Transaction
Capabilities (TCAP). See TS 29.002.
Gp interface
The Gp interface is used between Packet Services located in different mobile networks,
allowing visiting subscribers to be routed through their home network. Signaling on this
interface uses the User Datagram Protocol (UDP/IP). The Gp interface is defined in TS
29.060.
Gom interface
The Gom interface connects O&M equipment to the Packet-Switched network, making it
possible for an operator to communicate with the Packet-Switched.
The Gom interface is Ericsson-specific, and it is not part of the GPRS standard.
Lh interface
Interface between the Location Services, within Application Enablers, and the HLR
within Authentication, User Databases, and Provisioning. This interface is used by the
Location Services to retrieve the address of the visited MSC or SGSN for a particular
target UE/MS, whose location has been requested.
A
AA Authorization Authority
AH Authentication Header
AN Access Network
B
BA List BCCH Allocation List
BAR BA-List Recording
BG Border Gateway
BS Base Station
C
CA Capacity Allocation
CC Call Control
CK Ciphering Key
CM Configuration Management
Circuit Mode
Connection Management
CN Core Network
CP Central Processor
CS Circuit Switched
D
D-AMPS Digital Advanced Mobile Phone System
DF Delivery Function
DT Data Transcript
E
EAH External Alarm Handler
ET Exchange Terminal
F
FACCH Fast Associated Control CHannel
FE Fast Ethernet
FER File Input Output Link, (An old DOS version) Terminal application for remote
control of switches
FR Full Rate
G
GARP Generic Application Regional Processor
GE Gigabit Ethernet
GP Guard Period
GPB General Processor Board
GS Group Switch
GSM OSS Global System for Mobile Telecommunications Operations Support System
GSM RAN Global System for Mobile Telecommunications Radio Access Network
H
HCS Hierarchical Cell Structure
HO HandOver
HW Hardware
I
IAM Initial Address Message
ID Identity
IF Infrastructure
IH Internet Host
Integration Hub
IK Integrity Key
IM Interactive Messaging
IMEI International Mobile Equipment Identity
IN Intelligent Network
IP Internet Protocol
IPMM IP Multimedia
IPSec IP Security
IT Information Technology
J
J2AS Java 2 Application Server
K
KRD Key-set Receiver Device
L
L1 Layer 1 (physical layer)
LA Location Area
Link Adaptation
LE Local Exchange
M
MA Multiple Access
MC Message Center
ME Mobile Equipment
MM Mobility Management
MO Mobile Originated
MS Mobile Station
MT Mobile Terminated
Mobile Terminal
N
NAS Non Access Stratum
NAD/ESC config GUI
NE Network Element
Nt Notification (SAP)
O
ODCH ODMA Dedicated Transport Channel
OL Overlay
OSS-RC Operations Support System for the Ericsson Radio and Core Network
P
PAP Password Authentication Protocol
PC Power Control
PI Paging Indication
PM Packet Mode
Performance Management
PN Pseudo Noise
PS Packet Switched
PXM The local Network Element manager for SGSN is the PXM
Q
QoS Quality of Service
R
RA Registration Authority
RA Routing Area
RB Radio Bearer
RES response
RF Radio Frequency
RP Regional Processor
RT Real Time
RU Replacable Unit
RU Resource Unit
RX Receiver
S
SA Security Association
SC Switch Core
SF Spreading Factor
SG Security Gateway
SGSN Serving GPRS Support Node
SP Service provider
SP Switching Point
SS Supplementary Services
SS Switching System
ST Signalling Terminal
SW Software
T
TA Timing Advance
TA Terminal Agent
TB Tail Bit
TBF Temporary Block Flow
TE Terminal Equipment
TRA Transcoder
TRX Tranceiver
TS Time Slot
U
UDP User Datagram Protocol
UE user equipment
UI user interface
Um Air Interface
V
VAS Value Added Service
W
WAP Wireless Application Protocol
WCDMA RAN Wide-band Code Division Multiple Access Radio Access Network
X
XML eXtensible Markup Language