ERICSSON

Core Network Overview

Introduction
GSM Network Architecture
SIM = Subscriber Identity Mobile
 International Mobile Station Equipment Identity
IMEI
serial number allocated by the manufacturer and registered by the network operator.

uniquely identifies mobile stations internationally.

stored in the Equipment Identity Register (EIR).

IMEI = TAC+FAC+SNR+SP

TAC - type approval code ( first 2 digits identify the country in wich type approval
code was granted ).

FAC - final assembly code (identifies the faciliy where the phone was assembled ex.
Ericsson,Nokia,Motorola).

SNR - serial number (unique number for the mobile phone).

Spare - spare digit,usually 0.

 International Mobile Subscriber Identity
IMSI

when registering for a service with a mobile network operator,each subscriber

receives a unique identifier stored in the SIM.

a mobile station can be used if a SIM with a valid IMSI is inserted in a equipment with
a valid IMEI.

IMSI = MCC + MNC +MSIN.

MCC - mobile country code.

MNC - mobile network code,unique identification of mobile networks within a country.

MSIN identification nr of the subscriber in the mobile network.

 Mobile Subscriber ISDN Number
MSISDN

real phone number assigned to a subscriber(SIM).

each MSISDN of a subscriber is reserved for specific service:voice,data,fax.

MSISDN = CC+NDC+SN.

CC Country Code,internationally standardized.

NDC National Destination Code (assigend by the mobile operator).

SN Subscriber Number (assigend by the mobile operator).

For the MSRN (mobile station roaming number) the CC and NDC are assigned
depending on the location (visited network)
Authentication procedures
 when a subscriber is added to a network for the first time,a Ki subscriber
authentication key is assigned in addition to the IMSI.
at the network side,Ki is stored in the AUC and at the subcriber side is stored on the
SIM.
this process of authentication is based on A3 algorithm,performed at network side
and subscriber side.
calculates independently on both sides the SRES (Signature Response) and a
RAND(Random Number) offered by the network.
the MS transmits its SRES value to the network wich compares it with its calculated
value.(values agree <> authentication successful ).
Home Location Register (HLR)
database for management of mobile subscribers, stores the international mobile subscriber
identity (IMSI), mobile station ISDN number (MSISDN) and current visitor location register
(VLR) address
keeps track of the services associated with each MS
an HLR may be used by multiple MSCs
Visitor Location Register (VLR)
caches some information from the HLR as necessary for call control and service provisioning for
each mobile currently located in the geographical area controlled by this VLR
connected to one MSC and is often integrated into the MSC
Authentication Center (AuC)
a protected database which has a copy of the secret key stored in each subscribers SIM card
this secret is used for authentication and encryption over the radio channel
normally located close to HLR
Equipment Identity Register (EIR)
contains a list of all valid mobile station equipment within the network, where each mobile station
is identified by its international mobile equipment identity (IMEI) - split into 3 databases:
White list: all known, good IMEIs
Black list: bad or stolen handsets
Grey list: handsets/IMEIs that are uncertain

Optional in a GSM network.

.
Sometimes the AuC and EIR are combined.
 Mobile Switching Center(MSC)
The MSC performs switching for mobile and data calls, as well as :

Signalling

Paging

Collecting charging information

And many other functions.

MSC also acts as an interface between the PSTN and the Radio Access Network
(RAN)
Classic GSM 2G
GPRS 2.5G
 General Packet Radio Service:
a way to extend packet transfer up to the mobile station
UMTS 3G
 Interfaces
Gb Interface between the base station subsystem and the SGSN the transmission
protocol could be Frame Relay or IP.

Gn IP Based interface between SGSN and other SGSNs and (internal) GGSNs.
DNS also shares this interface. Uses the GTP Protocol.

Gp IP based interface between internal SGSN and external GGSNs. Between the
SGSN and the external GGSN, there is the border gateway (which is essentially a
firewall). Also uses the GTP Protocol.

Ga The interface servers the CDRs (accounting records) which are written in the
GSN and sent to the charging gateway (CG). This interface uses a GTP-based
protocol, with modifications that supports CDRs (Called GTP' or GTP prime).

Gr Interface between the SGSN and the HLR. Messages going through this interface

uses the MAP3 protocol.

 Interfaces
Gd Interface between the SGSN and the SMS Gateway. Can use MAP1, MAP2 or MAP3.

Gs Interface between the SGSN and the MSC (VLR). Uses the BSSAP+ protocol. This interface allows
paging and station availability when it performs data transfer. When the station is attached to the GPRS
network, the SGSN keeps track of which routing area (RA) the station is attached to. An RA is a part of a
larger location area (LA). When a station is paged this information is used to conserve network
resources. When the station performs a PDP context, the SGSN has the exact BTS the station is using.

Gi IP based interface between the GGSN and a public data network (PDN) either directly to the Internet
or through a WAP gateway.

Ge The interface between the SGSN and the service control point (SCP); uses the CAP protocol.

Gx The on-line policy interface between the GGSN and the charging rules function (CRF). It is used for

provisioning service data flow based charging rules. Uses the diameter protocol.
 Interfaces

Gy The on-line charging interface between the GGSN and the online charging
system (OCS). Uses the diameter protocol (DCCA application).

Gz The off-line (CDR-based) charging interface between the GSN and the CG. Uses
GTP.

Gmb The interface between the GGSN and the broadcast-multicast service center
(BM-SC), used for controlling MBMS bearers
Protocols and Call flows
Protocols

The most important protocols to be presented (at this stage) are:

MAP
ISUP
INAP
 MAP
Mobile Application Part
 MAP Mobile Application Part

MAP is a protocol located at application level (the equivalent of OSI

layer 7) and its used between MSCs and telecom databases (HLRs,
VLRs, EIRs)

A typical example for MAP used with DB interaction is when a

subscriber switch on the phone and try to find network (the correct
term is location update).
Location Update Flow
Location Update is the process where a subscriber get registered in a MSC/VLR. It can occur a Location
Update, for example, when a customer change Location Area (change MSC responsibility) see the flow
below

1. Subscriber requests a Location Update in

the New MSC/VLR.
HLR
2. MSC/VLR check if the IMSI corresponds to
any known entry in the registry. If so, simply
update info and register the subscriber. If
OLD MSC/VLR not, MSC requests to the HLR to update
2. 5. the DB with the information from the
subscriber and to send the data related to
NEW MSC/VLR 3. 6. the subscriber. MAP message sent from
BSC is LocationUpdate Request)
4. 3. HLR check the record for the subscriber
and send to the new MSC/VLR all the
7. subscriber profile. (Insert Subscriber
Data).

1. 4. New MSC ACK the previous message.

5. HLR sends then a Cancel LocationUpdate
to the old MSC to delete the register
referred to the subscriber.
6. Old MSC replies with an ACK to the old
Subscriber message.
7. HLR informs new MSC and updates it own
database. Subscriber information is totally
updated. (LocationUpdate Result).
SMS - Short Message Service Flow
SMS is a service non-connection oriented (it means that the information changed can be accessed any
time. The opposite of non-connection oriented is connection oriented USSD. Example in the next slide.)

1. MS send SMS to MSC/VLR.

HLR 2. MSC forward the request to SMSC
(ForwardShortMessage-MO)
3. SMS-C requests HLR the location of
the recipient of the message (Send
Routing Info SM).
3. 4. 4. HLR replies to SMS-C with the address
provided (MSC address)
SendRoutingInfo ACK
MSC/VLR - A MSC/VLR - B
5. SMS-C sends the Short Message to
2. 5.
the MSC of the messages recipient
(Forward Short Message Mobile
8. 7. Terminating).
SMSC
6. 6. Short Message is delivered to the MSC
1. that forwards to the recipients mobile
8. 7. station.
7. A delivery report is sent to SMS-C
(from MSC). Forward Message
Subscriber A Subscriber B ACK
8. When configured on the terminal, a
report message is sent to the
Subscriber A.
 USSD Unstructured Supplementary Service Data Flow
USSD is a connection-oriented service which means that it is valid while the connection is established.
Basically, the requests are strings of characters and the responses as well and, because its unstructured

1. MS sends the request string to the

HLR MSC.
2. MSC processes the request and route
it to HLR (Unstructured_SS_REQ).
3. HLR will relay the USSD string to the
3.
correct service (in fact, USSD
2. gateway).

5. 4. USSD Application Server will get the

MSC/VLR 6. USSD - AS
string, process the request and reply
4.
back to the USSD Gateway with the
response string.
USSD - AS
5. USSD Gateway will simply forward the
reply to the HLR with the message
1. Unstructured_SS_RSP
USSD - AS
USSD - Gateway 6. HLR will forward the string to the
7.
originating MSC.
7. MSC forward the response string to the
mobile.
Subscriber
 ISUP
ISDN User Part
 ISUP ISDN User Part

ISUP defines the protocol and procedures used to setup, manage and release trunk circuits that carry
voice and data calls over the PSTN (Public Switched Telephone Network)

HLR

STP A STP B

2. 4.

7.
MSC/VLR - A 9. MSC/VLR - B
6.
9.
8.
5.

10.

1.

A-number B-number
ISUP ISDN User Part

1. A-number dials B-number.

2. MSC analyze the digits (B-number) and send a Send Routing Info (MAP) to the
HLR.
3. HLR checks on the subscriber profile and requests Roaming Number (Provide
Roaming Number MAP) to to MSC-B
4. MSC replies with Roaming Number to HLR and this its forwarded to MSC-A.
5. With this information, MSC determines the routing to MSC-B and generates a
Initial Address Message (ISUP).
6. Message sent to STP-A
7. STP forward the message to MSC-B
8. MSC-B analyzes the IAM and identify the subscriber.
9. MSC-B sends ACM (Address Complete Message ISUP). A ring tone is
generated on the B-number and a ring tone is generated to the caller party.
10. MSC receives the ACM and performs connection between the voice trunk and the
connection with the subscriber (A-number).
11. Subscriber B answers the call and an ANM (Answer Message ISUP) is sent. At
this point MSRN is released (after being sure that A# is connected to the outgoing
trunk).
12. When one of the parties release the call, a REL (Release ISUP) message is
generated and the reply is a RLC (Release Complete - ISUP)
 INAP
Intelligent Network Application
Part
INAP Intelligent Network Application Part

INAP is the protocol used by the CORE to interact with IN (Intelligent Network).
IN is basically, a set of resources that facilitates the speedy introduction of customized and value added
services. Some examples of IN services are:
Geographical services (emergency 112, hotline service for technical assistance), prepaid service,
Number translation (short codes, taxi service, etc).

Requests,
Queries and
Credit
SCP reservations
SCP SDP

HLR
2. 3. 6. 9. 10.
8.

5.
1. 4. 11. 4.
5. 7. 5. 7.
A-number B-number
MSC/VLR - A MSC/VLR - B
INAP Intelligent Network Application Part

A-number calls B-number

1. A-number dials B-number telephone number. Number is received from MSC.

2. VLR has the prepaid subscriber profile downloaded (when LU was completed). When the attempt to call B-number takes place, an event is triggered and a
request is sent to SCP (IDP). Basically, MSC requests SCP, the rules to handle the call.

3. SCP receives the IDP and before something else, check with Billing Engine/SDP, if the subscriber has balance enough to proceed with the call. If so, reply to
MSC informing about how to charge the client, which events it should be informed (through events report sent by MSC) and a Connect/Continue message, as an
instruction to MSC to proceed with the call.

4. MSC proceed with the call routing to the destination.

5. B-number answers the call

6. Triggered an event and a report is sent to SCP.

7. B-number release the call.

8. MSC/VLR A inform SCP about the call state (event triggered).

9. SCP order a Release call to MSC.

10. MSC disconnects the call and send an Apply Charging Report.

11. A RLC (Release Complete) message is exchanged between MSCs.

 ATM

Asynchronous Transfer Mode

 Introduction
ATM-Asynchronous Transfer Mode is a connection-oriented multiplexing and
switching method. It is asynchronous in the sense that cells carrying user data need
not to be periodic.

ATM has a fixed transmission unit, called the Cell''. Each Cell is 53 octets , of which
5 octets are used for the ATM header and the remaining 48 octets

The ATM header contains information about destination, type and priority of the cell.
Interfaces
 ATM Connections
An ATM connection is identified by the combined virtual path identifier (VPI) and
virtual channel identifier (VCI).

Types:

PVC-established manually by a network administrator using network management

procedure; it remains in place for a long time

SVC -established in real-time by the network using signaling procedures; it remains

up for an arbitrary amount of time.

S-PVC-is set up using both network management procedures and signaling

procedures.

For UNI there can be a maximum of 256 virtual paths

For NNI there can be a maximum of 4096 virtual paths.

In each interface, there can be a maximum of 65,536 VCIs.

 ATM Virtual Connections

VC Virtual Channel VP Virtual Path

 ATM Switching Operations

The basic operation of an ATM switch is straightforward.

The cell is received across a link on a known VCI or VPI value.

The switch looks up the connection value in a local translation table to

determine the outgoing port (or ports) of the connection and the new
VPI/VCI value of the connection on that link.

The switch then retransmits the cell on that outgoing link with the
appropriate connection identifiers.

Because all VCIs and VPIs have only local significance across a particular
link, these values are remapped, as necessary, at each switch
 ATM Reference Model

Control---This plane is responsible for generating and managing signaling

requests.

User--- This plane is responsible for managing the transfer of data.

Management--- This plane contains two components

Layer management -- manages layer-specific functions, such as the

detection of failures and protocol problems.

Plane management -- manages and coordinates functions related to the

complete system.
OSI ATM Reference
 Main services carried over ATM are:

Residential, BP, Corporate Data Traffic (DSLAMs )

Residential, BP, Corporate Voice Traffic (DSLAMs)

Voice Traffic (Radio sites)

Data Traffic (Radio sites)

 Login to Applications

Show every single day work flow and alarm

supervision
 Front Office Core Team Structure

Most experienced is Lead Engineer (LE).

Engineers dedicated for IP side.

Engineers dedicated for CORE side.

 Activities
Customer Problem Management

1st level end-user fault restoration

1st level end-user fault trending

Track & Manage end-user Problem

End-user Outage Notification

Problem Escalation

Multi-user problem escalation

 Activities
1st Level Operations

Service Alarm Handling

Service Problem Handling

1st Level Service Restoration

Track & Manage Service problem

Service Performance Monitoring

Resource Alarm Handling

1st level Resource Fault Restoration

Track & Manage Resource Problem

Resource Performance Monitoring

Request Field Services

Control & Support Reactive or Planned activities

Management Notification & Escalation

Real-time Change permission & surveillance

1st Level Routine Maintenance