1) Importance of Telecom OSS and BSS

A. BSS/OSS Technical Overview

OSS/BSS infrastructure to manage customers in mobile and fixed domain, evolution from vertical to well
defined modular, component-based architecture.

B. BSS/OSS Architecture
 Operator systems architecture consists of three layers:
 Business Support System (BSS) layer
 Operations Support System (OSS) layer
 Networks layer
Above diagram displayed High Level Architecture, which includes.

 BSS (Business Support Systems) – Fulfillment Systems.

 Business Support System (BSS) is a combination of Business components that
Service providers use to run Business.
 BSS are a separate set of applications supporting commercial, revenue and
customer-relationship activities.
 It helps service providers support and extend operations to enhance Business
services.
 BSS is basically used in mobile, fixed and cable networks.

BSS includes launching and analyzing new marketing campaigns, creating invoices, payment collection,
and revenue sharing with partners and billing.

Some of the most important real-time network facing components of a BSS system is:
 Charging
 Rating
 Mediation
 Billing
 Reconciliation

 OSS (Operations Support Systems) – Fulfillment Systems.

 OSS is an aggregation of functions that enable the CSP (Communications Service
Provider) to provision and manage their inventory, customers, services and
network elements.
 Resource may be a customer, a value added service, inventory such as
Telephone device or even a network element such as a switches.
 OSS helps CSP to monitor, control, analyze and manage a Telephone or
Computer network.
In traditional Telephone Systems (PSTN), OSS converges.
a) Packet-Oriented Internet traffic (VoIP)
b) Broadband Applications such as Teleconferencing and DSL
c) Network Components (IP addresses)
d) Usage and Traffic patterns, Billing and Reporting.

 Network Layer –
 Networks layer contains network operator’s network infrastructure.
Multiple networks can be managed simultaneously by one system.

C. OSS and BSS Components

 Following are OSS and BSS components
 OSS:
 Inventory
 Provisioning and Activation
 Fault and Performance Management
 Planning
 BSS:
 Order Management
 Customer Care/ Self Service
 Billing/ Invoice
 Service Assurance

2) Telecom Mediation Architecture & Work flows

A. Telecom Mediation Architecture
B. Mediation Stages
 Collection – Mediation System can access to remote Switch Servers and copy binary
(encrypted) files (ASN.1 format etc.) on production server for mediation modules.
 Validation – Checking like bad time format, time in future and etc.
 Transformation – Conversions (decryption) from binary to decade.
 Distribution – Sending (FTP) this data to other modules. For example billing systems.

C. Rating and Billing

 After Provisioning has been done, Customer start using real time services like
Phone, Video, Internet in and service consumption starts.
 On the basis of consumption records are generated by Network Elements (Network
Switches) these records are called CDR / UDR.
 In other term these are offline charged records (OFCS).
 These records (OFCS) are passes through various Network elements to the Billing
System;
 Whole Telecom process is called Telecommunications Mediation.
 Mediation process converts raw CDR/ UDR to pre-defined layouts that can be
imported by a specific Billing System (here whole rating and charging process
converts records to Invoices etc).

D. Network Elements
 A customer starts generating usage at Network as soon as he/she starts using the
products and services sold by the operator. A network element is a combination of
software plus hardware and responsible for overall service control and metering
events for any type of service.
 E. GSM telephony
 GSM (Global System for Mobile communications) is a standard developed by the
European Telecommunications Standards Institute (ETSI) to describe the protocols
for second-generation digital cellular networks used by mobile devices such
as tablets, first deployed in Finland in December 1991. As of 2014, it has become the
global standard for mobile communications – with over 90% market share,
operating in over 193 countries and territories. GSM Architecture is shown below.

 What is a CDR?
 An event along with all its attributes is called Call Detail Record (CDR). A
data collector in the network switch captures the usage in the form of Call Detail Record
(CDR)/Usage Detail Record (UDR). These raw CDRs/UDRs are in turn converted by the mediation
system into a format understandable by the Billing System.
 There could be different network elements controlling the services and
producing different
 Types of CDRs; for example, for GSM telephony −
 Voice calls are captured by the MSC (Mobile Switching Centre).
 SMS traffic is captured by the SMSC.
 Data traffic is captured by the GGSN.
 MMS traffic is captured by the MMSC.
 Roaming CDRs are captured by roaming partner's switching element.
F. Voice calls – MSC
 A mobile switching center (MSC) is the centerpiece of a network
switching subsystem (NSS). The MSC is mostly associated with
communications switching functions, such as call set-up, release,
and routing. However, it also performs a host of other duties,
including routing SMS messages, conference calls, fax, and service
billing as well as interfacing with other networks, such as the public
switched telephone network (PSTN).

The MSC is structured so that base stations connect to it, while it

connects to the PSTN. Because cellphones connect to these base
stations, all forms of communication, whether between two cell
phones or between a cell phone and a landline telephone, travel
through the MSC

G. SMS traffic – SMSC

 The Short Message Service Centre (SMSC) is an element in
a GSM network responsible for the delivery of short messages
(SMS). All messages are sent to the SMSC. The SMSC stores the
messages, extracts the destination from it and tries to deliver the
message. If the message cannot be delivered, the SMSC will try
again to deliver the message in a so-called retry-schedule. If the
mobile phone is turned on or comes within reach of the network,
the SMSC will also retry to deliver the message. If a mobile
telephone received a message, it will send an acknowledgement
back. Usually the message will be discarded after two days if the
destination cannot be reached.
 The number of the SMSC has to be programmed in the mobile
phone.

H. Data traffic – GGSN

 The Gateway GPRS Support Node (GGSN) is a main component of the GPRS
network. The GGSN is responsible for the interworking between the GPRS network and
external packet switched networks, like the Internet and X.25networks. From the
external networks’ point of view, the GGSN is a router to a sub-network, because the
GGSN ‘hides’ the GPRS infrastructure from the external network. When the GGSN
receives data addressed to a specific user, it checks if the user is active. If it is, the GGSN
forwards the data to the SGSN serving the mobile user, but if the mobile user is inactive,
the data are discarded. On the other hand, mobile-originated packets are routed to the
right network by the GGSN.
To do all this, the GGSN keeps a record of active mobile users and the SGSN the mobile
users are attached to. It allocates IP addresses to mobile users and last but not least, the
GGSN is responsible for the billing.
I. MMS traffic – MMSC
 The Multimedia Messaging Centre (MMC) is an element in a GSM network
responsible for the delivery of multimedia messages (MMS). All messages from
subscribers are send to the MMC. The MMC stores the messages, extracts the
destination from it and tries to deliver the message. If the message cannot be delivered,
the MMC will try again to deliver the message in a so-called retry-schedule. If the mobile
phone is turned on or comes within reach of the network, the MMC will also retry to
deliver the message. If a mobile telephone received a message, it will send an
acknowledgement back. Usually the message will be discarded after two days if the
destination cannot be reached. The number of the MMC has to be programmed in the
mobile phone.

J. Roaming CDRs from business partners

 Mobile subscriber travels to another country and creates usage on the foreign
network. In order to bill the subscriber, this information has to be passed back to the
subscriber's home network. The foreign network will collect information on the usage
from it's switches, etc., and then creates TAP files containing the information set out in
the standard.
 The files are then EXPORTED (on a regular basis, generally at least one file per day)
to the home operator, who will IMPORT them and then use the information to invoice
the subscriber. The foreign operator will rate the calls and then charge the subscribers
home network for all the calls within a file. The home operator can mark up or re-rate
the calls in order to make revenue.

K. Interconnect CDRs from partners

 Interconnect is the process of handling calls for other service providers. This allows
the customers of one service provider to communicate with the customers of another
service provider. If two operators A and B are not interconnect partners, then it would
not be possible for a customer of Operator A to communicate with a customer of
operator B.
3) Introduction to DP,CABS, UBP, Wifi and Cloud
A. DP (Digital Phone) – After Provisioning of the Mediation and Rating of Digital
Phone Call Detail records (CDRs) of customers.
CDR information after Mediation and Rating is used to generate final charge amount.
Below are the list of Switches on which DP mediation activities can be performed

 HiQ (Nokia Siemens)

 BTS (Cisco)
 IMS (Nokia Siemens)
 ALU (Alcatel Lucent CTS)
B. CABS (Carrier Access Billing system) – Carrier Access Billing System process
long duration calls specific to below Telecom switches to perform Mediation and Rating
activities.

 BTS Tandem (Cisco)

 SONUS SBC
 SONUS GSX
C. UBP (Usage Base Pricing – High Speed Data) – Usage Base Pricing is used to
process High Speed Data switches and perform Mediation and Rating activities.
D. Wifi (Wifi Zone) – Perform Mediation and Rating activities for operators Wifi
Hotspot zone.
E. Cloud (Mailbox) – Perform Mediation and Rating activities for Cloud mailboxes like
applications.
4) DP Collection Process in detail, DP Mediation and Enrichment Process in
detail
  Usage Collection is the act of initially loading CDRs from an outside CDR source.
 Usage Correlation is the act of correlating multiple CDRs together to formulate one
(or more) complete call record(s). BTS, HiQ and ALU require this action.
 Usage Mediation is the act of taking information off a source specific CDR and
putting it in a common form.
 Usage Enrichment is the act of taking information from the source CDR and using it
to determine and add additional information to the common CDR.
 Filtering is the act of removing records from further processing but still have them
available for distribution to downstream systems.
Enrichment troubleshooting scenarios –
Let’s have one CDR file from any telecom switch must contain raw records, below are the file standard
structure.
Below are the mediation stages and each stage having multiple troubleshooting scenarios.
 Collection
 During CDR collection process if file masking (name or extension) are
incorrect processed file must reached to Collection Error stage.
 Let’s have unique CDR file and it should process in 6 Hrs. If same duplicate
file process with in 6 Hrs., file must be rejected system must generate
warning and file must reached to Collection Error stage.

 Parsing
 CDR file contain Header, Record and Trailer all fields are mandatory
 If Header is missing and CDR is process file must be rejected system
must generate warning and file must reached to Parse Error stage.
 If any Records are missing and CDR is process file must be rejected system
must generate warning and file must reached to Parse Error stage.
 If Trailer is missing and CDR is process file must be rejected system must
generate warning and file must reached to Parse Error stage.
 Usage Correlation
 For log duration call let say one calling CDR record comes under more than
one CDR and records are augmented with a “Correlation Id” field and it
enable identification of a group of records that comprise a single call event.
The “Correlation Id” will be formed from the concatenation for the “Switch
Id” and the HEX component of the “Record Id” separated by a colon ‘:’
character.
Switch Id = xxx01xxxxx2
Record Id = 2018-20-06T16:56:20.3-
0500:FF000200000000004FE200B40022B24C
Correlation Id = xxx01xxxxx2:FF000200000000004FE200B40022B24C
 Usage mediation
 When a field in a record fails validation the record should be recorded in an
invalid record table and the count of invalid records should be increased.
The following information should be place in the invalid record table:
 When record validation pass records should mediated successfully and
processed record reached to RAW table.
  Filtering – Filtering in Mediation process are Pre filtering after mediation and Post
filtering after Enrichment process records are move to Filter table.
 Pre Filtering – Below are can be example of pre filtering scenario.
 All CDR records are fine except Call Connect time is 0
 All CDR records are fine except Call Disconnect time is 0
 Any field which affects CDR Enrichment processes like Off Hook
indication any other environment variable.
 Post Filtering – Below are can be example of post filtering scenario.
 During CDR enrichment process for outbound call Calling party NPA-
NXX are not available in Ref Schema.
 During CDR enrichment process for inbound call Called party NPA-
NXX are not available in Ref Schema.
 Enrichment – CDR raw Data processing valid data enriched successfully and
processed should reached to enriched table on which rating should be applied
Below are other validation stages.
 Zero record files, verify no record successfully enriched.
 Discarded Records, verify records moves to discard table.

5) Digital Phone Rating and Billing Process, Details about Telecom Switches
The rating process will examine the usage record to be rated and ask a few simple questions about the
record in order to determine how to rate this record. The questions to be asked are:
 What are the rate sheets that are applicable to the service; determined using the
relationship between billing service code, package and rating plan? Are there
multiple packages associated with the service?
 For toll free calls, what are the rate sheets that are applicable to the terminating
service; determined using the relationship between terminating billing service code,
package and rating plan?
 Does this call apply to one of the rates in the rate sheets?

6) Unix Commands & Call Records and Vendor Records CDR files
7) Introduction to HIQ,BTS, ALU and IMS for Call Records CDR file Processing
A. HIQ – HiQ CDR Files are formatted ASCII text files. The files contain header and trailer
information in addition to CDRs.

The following file tags and format must exist inside the header section. All tags are followed by “<NL>”
new line character.

TAG Description

FILENAME: The FILENAME tag is used to identify the name of the file when it was created.

DEVICE: The DEVICE tag identifies the device that created the file.

The HOSTNAME tag identifies the configured IP Hostname of the device that created
HOSTNAME:
the file.

FILETYPE: The FILETYPE tag identifies the type of file.

The VERSION tag specifies the version of the file format. The version is formatted as
VERSION:
<major>.<minor>.<patch>

<NL> Blank line.

 The CREATE tag is used to indicate the start of the call record information and
CREATE:
additionally specifies the date / time stamp when the file was initially created.

<NL> Blank line

Individual CDR(s), numbered sequentially and separated by <NL>, are located between the header and
trailer sections. Each CDR is composed of number of fields in an ASCII comma delimited format.

The following file tags and format must exist inside the trailer section. All tags are followed by “<NL>”
new line character.

TAG Description

<NL> Blank line

The CLOSE tag is used to indicate the end of the call record information and
CLOSE:
additionally specifies the date / time stamp when the file was closed.

B. BTS
 BTS File Layout
o BTS CDR Files are formatted ASCII text files. The file contains header and trailer
information as well as call detail records.

The first record in the file contains the header information and the last record in the file contains the
trailer information. Each field within a record is separated by a semi-colon ‘;’ character. Records are
separated by a pipe ‘|’ character.

The following fields and must exist inside the header record:

Field Description

Header/Trailer
Specifies the version of the header/trailer format.
Version Number

Specifies the version of the CDR format. The version number will be formatted as
CDR Version
<major>.<minor>.<patch>

Starting Time Specifies the date / time stamp when the file was initially created.

Call Agent Id A value that uniquely identifies the switch

A blank record will immediately follow the header record.

 Individual CDR(s), follow the blank record. Each CDR is composed of number of fields which
varies depending on the CDR version.
 Following the last CDR record and preceding the trailer record is a blank record.
  The following fields and must exist inside the trailer record:

Field Description

CDR Count Specifies the total number of CDR(s) in the file.

Finish Time Specifies the date / time stamp when the file was closed.

 TWC supports two versions of the BTS switch – Release 04.5 and release 06.0. The BTS CDR
usage file layout is defined in detail in the Cisco BTS10200 Softswitch Billing Interface Guide.
Both the Release 4.5 and the Release 6.0 versions of the guide are attached below.

C. IMS
 File Layout

The ALU CDR Usage files will be in XML format. An Apollo CDR file will contain data from only one
switch. Each CDR has a parent element, a header section, and a body section. The overall structure of
an ALU CDR file is as follows:

 Parent element <cdr_file>

o Everything is a child of this element. To detect if a file is complete, simply ensure that
there is an open and close tag for this element.
 Header element <header>
o The header section defines parameters that apply to the entire file. The following three
items are identified in the header – CDRMS version number, CDRMS collector name, and
record count. The header is always the first child element in the file.
 Body element <body>
o The body section contains all of the individual records produced by the switch. The
body directly precedes the header.

The body element <body> contains individual call record elements <cdr>, one per call record.

Basic ALU CDR formatting is described in the ATG East – Operational Support Services Functional
Specification – Apollo Call Data Records.

8) Introduction to Sprint ,VERIZON, SONUS for Vendor Records CDR file

Processing
A. Sprint Vendor records CDR file for Toll Free Numbers
Sprint Vendor records CDR files mainly used for Toll free Numbers processing. Have same processing
stage like other non-vendor CDRs like BTS, HIQ.

Below are some functional validation stages.

 Sprint CDR Initial Enrichment

 Sprint Filename Format
 Sprint File Duplicate Check
 Sprint File Layout
 Sprint Call File Parsing
 Zero Padding
 Duplicate Record Check
  Zero record files
 Discarded Records

B. VERIZON Vendor records CDR file for Toll Free Numbers

VERIZON Vendor records CDR files mainly used for Toll free Numbers processing. Have same processing
stage like other non-vendor CDRs like BTS, HIQ.

Below are some functional validation stages.

 VERIZON CDR Initial Enrichment

 VERIZON Filename Format
 VERIZON File Duplicate Check
 VERIZON File Layout
 VERIZON Call File Parsing
 Zero Padding
 Duplicate Record Check
 Zero record files
 Discarded Records

9) Prepaid work flow Voice, SMS, Data

A. Voice
i. Normal Prepaid (IN) Call Flow

Above architecture describe basic direct dial call scenario with normal call termination:
  Mobile A starts a new call by Dials Mobile B Called Number.
 MSC sends an IDP (Initial Detection Point) event, which notifies IN-SCP for new call.
 IDP Message Contains: - A-Party Number, B-Party Number, Service key, A
Party Location, Time stamp.
 The IN SCP processes the request (Initial Quota request) and after authorizing the
user, the IN SCP sends 3 IN messages to the MSC -
 AC (Apply Charging) :- Check the A-Party Balance / tariff plan and provides
maximum granted time for a call.
 CIQ (Call Information Query) :- IN SCP request MSC for Call information
 CAET - Call Attempt Elapsed Time (time between call ringing & user
picks the call)
 CCET - Call Connect Elapsed Time (Duration of a call)
 CST - Call Stop Time (exact time when call disconnect)
 RC - Release Cause (Exact release cause due to which call got
disconnected).
 RRBCSM (Request Report Basic Call State Module) :- IN again request from
MSC for detailed Release Cause.
 Connect :- When each request from IN SCP have been done then IN sends a Connect
message to MSC for further call processing & connect the call.
 Activity Test :- After IN provides "connect" message to MSC, perform Activity Test
using unidirectional ping message, to know the progress of a call.
 Once connection is established, event report (only answer event) is sent to SDP via
IN-SCP, for analyze revenue loss during call setup.
 After call completion and call gets Disconnected, a new event report is sent to SDP
via IN-SCP, which instructs to release the call.
 After call released, Apply Charging Report (ACR) is sent to IN-SCP, which contains
full time usage details of a call. Sent to SDP for accurate & final call charging.
 CIR (Call Information Report) :- Using CIQ message details, MSC makes a report i.e.
CIR (which contains CAET, CCET, CST, RC) & sends to SDP via IN-SCP.
 ERB (Evert Report BCSM) :- Another report send by MSC to IN, which contains
actual release cause in details, like B-Party Busy, B-Party no answer, B-Party not
reachable, route selection failure, disconnect.
ii. GSM Mobile Terminated Call

Case Study – A Land Line Subscriber calling a Mobile Subscriber.

 PSTN subscriber dials the Mobile MSISDN; it is analyzed in the PSTN and identifies
this is a call for mobile network subscriber.
 Connection is established to the MS’s home GMSC and PSTN sends an Initial
Address message (IAM) to the GMSC.
 GMSC analyzes the MSISDN to find out which HLR MS is registered.
 GMSC queries to HLR for route information of the call to the serving
MSC/VLR.
 HLR looks up MSISDN and determines the IMSI and the SS7 address for the
MSC/VLR that is servicing the MS.
 HLR checks any call forwarding if the service to C-number is activated, then
call is rerouted by the GMSC to that number.
 HLR then contacts the servicing MSC/VLR and asks it to assign a MSRN to the call.
 MSC/VLR returns an MSRN via HLR to the GMSC.
 GMSC sends an Initial Addressing message (IAM) to the servicing MSC/VLR and uses
the MSRN to route the call to the MSC/VLR.
 Once servicing MSC/VLR receives the call, the MSRN can be released and
may be made available for reassignment.
 MSC/VLR routes call to all BSCs and BTSs to page the MS. To know serving BSC and
BTS, pages will be sent out across the entire Location Area(LA).
 When the MS detects the paging message to the BTS’s in the desired LA.
 BTS’s transmit the message over the air interface using PCH.
 Page the MS network using IMSI or TMSI and valid only in serving MSC/VLR
area only.
 When the MS detects the paging message, it sends a request on RACH for a SDCCH.
 The BSC provides a SDCCH, using AGCH.
  SDCCH is used for call set-up procedures. Over SDCCH all signaling call takes place.
Includes
 Verify MS as “active” in the VLR.
 Authentication procedure (Start ciphering, Equipment identification).
 The MSC/VLR instructs the BSC/TRC to allocate an idle TCH. The BTS and MS are told
to tune to the TCH. The mobile phone rings. If the subscriber answers, the connection is
established.
iii. GSM Originating Call Flow

Case Study – A Mobile User calling a Land Line Subscriber.

 MS after dialing a land line number and pressing SEND key, sends Channel Request
message on RACH to ask for a signaling channel.
 Then BSC allocates a Traffic Channel (TCH) using AGCH. TCH assigns a specific
Frequency & a Timeslot on that frequency.
 The MS sends a call setup request through SDCCH, to the MSC/VLR. Over SDCCH, all
signaling takes place Includes marking the MS status as active in the VLR.
 Then comes Authentication Procedure which includes Ciphering (The channel is
ciphered so as to protect the call), Equipment Identification, etc.
 Then MSC/VLR instructs the BSC to allocate an Idle TCH (this message contains the
dialed digits and other information needed for call establishment). The BTS and MS are
told to tune to the TCH.
 The MSC allocates a voice circuit on one the digital trunks between the MSC and the
BSS.
 MSC informs the BSS about the allocated voice circuit. The call is also switched from
signaling to voice.
 The BSS notifies the Mobile about the changeover to voice mode.
 The MSC routes the call and sends the call towards the called subscriber.
 The PSTN indicates to the MSC that it has received all the digits and the called
subscriber is being rung.
 The MSC informs the mobile that the called subscriber is being alerted via a ring.
 The called subscriber answers the call.
iv. (GSM) Mobile to Mobile Call Flow, Within Same MSC/BSC
 1. CM Service Request – Message contains Global Cell Identity, Kind of Service
required by subscriber e.g Voice, SMS, Fax, USSD. Mobile Identity e.g TMSI/IMSI.
 2. CM Service Accept – Message is in reponse of CM Service Request.
 3. Set Up - Message contains dailed number from Mobile A (i.e Mob B number) and
speech Codec.
 4. Send Routing Info-Request (SRI) - After analysis of dialed numbers received from
A in set up message, MSC recognises its own MSISDN series and send SRI to HLR to get
the Mobile station roaming number(MSRN). This messge contains B MSISDN,
Interrogation type e.g Basic Call etc.
 5. Assignment Request - Message is to seize a channel for voice call for Mob A
between MSC and BSC. Message contains Circuit Identification Code(CIC).
 6. Assignment Complete - Acceptance from BSC end that same CIC has been seized.
 7. Provide Roaming Number Request - HLR checks in its database to which VLR,
Mob B is registered & ask for roaming number from that VLR. Message contains IMSI,
MSISDN, VLR ID of Mob B.
 8. Provide Roaming Number Response - Message is response of roaming no.
request and contains roaming number of Mob B. This message is for HLR. In this VLR
checks its database & allocate one free MSRN from its MSRN pool for B number.
 9. Send Routing Info-Response - In this HLR forward same roaming number which it
receives in above message to MSC.
 10. Paging Request - In this VLR checks the MSRN recieved from HLR & search which
MSISDN is against that MSRN, now MSC checks the VLR database of that MSISDN to get
the LAC & TMSI/IMSI of that MSISDN (Mob B) & initiates the paging request message to
that particular LAC on the basis of TMSI/IMSI in that BSC. BSC now page to that LAC on
the basis of IMSI/TMSI of Mob B. Message contains LAC, IMSI/TMSI, DPC of BSC.
 11. Paging Response - Mob B response to that paging with GCI (Global Cell Identity)
to BSC that inturn forwarded to MSC.
 12. Assignment Request - Message is to seize a channel for voice call for Mob B
between MSC and BSC. Message contains Circuit Identification Code(CIC).
 13. Assignment Complete - Acceptance from BSC end that same CIC has been
seized.
 14. Set Up - It is used to display Mob A number on Mob B handset.
 15 .Alert - This message indicates Mob A that Mob B is connected & its ringing. The
Ring Back Tone is send from MSC to Mob A.
 16. Connect - Mob B answers the call & connect message from Mob B is send to
MSC, inturn MSC sends connect message to Mob A indiacting that phone has been
answered & connects those 2 voice channels which were seized during the assignment
complete message.
 17. Connect Acknowledge - To acknowledge the connection.

B. SMS
i. Mobile Originated (MO) SMS Flow

 The mobile station transfers the short message to the MSC.

 The MSC queries the VLR to verify that the message transfer does not violate the
supplementary services invoked or the restrictions imposed on the subscriber.
 The MSC sends the short message to the SMS-IWMSC (Inter-Working MSC for SMS)
using the “forward Short Message” operation.
 The SMS-IWMSC delivers the short message to the SMSC (Short Message Service
Centre).
 The SMSC acknowledges the successful outcome of the “forward Short Message”
operation to the MSC.
 The MSC returns the outcome of the short message operation to the mobile station.

C. Data
i. GPRS Call Flow

 A subscriber accesses the Internet with GPRS mobile phone to set the APN (Access
Point Names) & gateway IP address defined on subscription. In fact, APN is a logical
name indicating the external data network in GGSN. A subscriber can select different
GGSNs via different APNs. Currently, however, only one APN can be activated at a time.
The purpose of selecting different APNs is to access the external network via different
GGSNs, because without GGSN, a subscriber cannot access the PDN (Public Data
Network). An APN consists of a fully qualified DNS (Domain Name Server) name e.g.
airtellive.com.cn., which should be parsed by DNS to get the real IP address of GGSN.
 The call reaches the SGSN of the GPRS network. The SGSN triggers the service in the
corresponding SCP (Service Control Point) according to subscriber's authentication
information on the HLR interconnected to the corresponding home SCP for processing.
 The DNS parses the APN and get the IP address of the GGSN.
 The call is routed to the GGSN according to the IP address.
 The GGSN assigns the IP address to the subscriber.
 After SCP verifies the subscriber, the subscriber begins to transmit data and log in to
the external web sites via the gateway whose IP address is set in the mobile phone.
 The subscriber may select the service from the portal web site to connect the SP/CP
web site that provides the service, or enter the IP address of the SP/CP in the mobile
phone to access the SP/CP web site.

D. IMS IPCDR
i. SIP (Session Initiation Protocol) Call Flow for Voice and SMS
1. Voice
Initial Call setup –

 System Acquisition: UE performs frequency synchronization and reads MIB/SIBs

from PBCH to acquire system information. Then locate the most suitable cell.
 RRC Connection Setup: The UE and eNodeB exchange signaling to set up an RRC
connection. The UE then sends RRC Connection Setup Complete message to the
eNodeB.
 Attach Request: The UE includes in the ATTACH REQUEST message a valid GUTI
together with the last visited registered TAI, if available. If there is no valid GUTI
available, the UE shall include the IMSI in the ATTACH REQUEST message. eNodeB
forwards the Attach Request message (including: Message Type, eNB UE ID, TAI, CGI
etc.) to the MME.
 Identity Procedure: MME sends an Identity Request to the UE. Identity procedure is
required only if attach request contains GUTI/last-TAI and the TAI is not local to MME
The UE responds with Identity Response including Mobile Identity that is set to IMSI.
  Authentication/Security: When there is no UE context on the network,
authentication is performed. The MME sends an Authentication Information Request to
the HSS and receives an Authentication Information Answer which is used to send
Authentication Request to the UE. Authentication procedure is optional. UE then sends
an Authentication Response to the MME
 Update Location Request: MME sends the Update Location Request including the
IMSI. The HSS replies with Update Location Answer.
 Create Session Request: MME sends a Create Session Request to SGW which is
followed by confirmation.
 Initial Context Setup Request/Attach Accept: Attach Accept is sent as NAS PDU in
the Initial Context Setup (Message Type, E-RAB ID, QoS parameters, Transport Layer
address, NAS-PDU, UE Security Capabilities, Security key) from MME to eNodeB.
 RRC Connection Re-configuration: The eNodeB sends the RRC Connection
Reconfiguration message including the EPS Radio Bearer Identity to the UE, and the
Attach Accept message to the UE.
 Initial Context Setup Response: The eNodeB sends Initial Context Setup Response
to the MME
 Uplink Information Transfer: The UE sends an Uplink Information Transfer message.
This message includes the Attach Complete message for MME Attach Complete: eNodeB
encapsulates the Attach Complete message and transfers it to MME.
 Modify Bearer Message: One receiving both Context Setup Response and Attach
Complete, the MME sends a Modify Bearer Request to SGW. SGW sends the response
and starts sending the DL packets.

SMS

 SC(service center) is responsible for relaying and forwarding of the SMS.

 SMS-IWMSC is interworking MSC for SMS system.
 HLR/HSS stands for home location register/home subscriber server.
  Let us understand LTE SMS MO Call procedure.
 After the EPS/IMSI attachment, LTE UE triggers service request in order to initiate
mobile originating SMS.
 SMS is encapsulated in NAS message and transmitted to MME entity.
 MME forwards this SMS to MSC/VLR.
 MSC/VLR acknowledges the receipt of SMS to LTE UE.
 SMS is forwarded to service center(SC) which returns delivery report back to UE as
shown in step-7 and step-8.
 UE acknowledges receipt of delivery report to MSC/VLR entity.
 MSC/VLR informs to MME that no more NAS messages are in the queue
 Release request is sent from MSC/VLR to MME.