GSM

PRESENTATION
by

Brendan Mannion


GSM Introduction and Structure Overview

Transcoder Introduction

Introduction and Diagram of the Blocks Involed

Explaination and Functions of the Blocks
The CME 20( Ericssons Product) product was developed to
comply with GSM (Global System for Mobile Communication).

The CME 20 Product was devloped for use in European
and Asian Markets.

GSM Network is divided into two systems:

Switching System:
Contains :
Mobile Services Switching Centre, Visitor Location Registor,
Home Loation Registor, Authentication Centre,
Equipment Identity Registor.

Base Station System:
Contains:
Base Station Controller, Base Tranceiver Station.

AuC

HLR
EIR

MSC OMC
BTS
BSC
VLR
GSM Network Structure
SS
BSS

MS(Handset)
The elements of the Network perform the following functions:

BSC handles the connection towards the mobile station and the
administration of cell data. Also handles the operation and maintenance
of the base stations and controls functions such as handover, location
of subscribers and call set up within the PLMN,

BTS contains the radio equipment needed for communicating to
the MS over the air interface.

MSC controls the switching functions for the mobile Network to
PSTN, ISDN etc

HLR main function is as a network database to store information such as
Subscriber Identity, Subscriber Location, Subscriber Authentication
Information etc...


VLR is another database that contains information about all MSs
currently located in an MSC service area. The VLR temporarily
stores subscription information so that the MSC can service all
Subscribers currently visiting that MSC service area.

AuC is needed to authenticate the subscribers attempting to use
the network.

EIR is a database containing Mobile Equipment Identity information
which helps to block calls from stolen, unauthorised or defective MSs.

OMC is the Operation and Maintenance Centre and monitors the Network
on both the radio and network side.

MS is the Mobile station or handset and is used to make and receive calls.


GENERAL INFORMATION

















The Radio and Transport Subsystem forms part of the Base Station
Controller/Transcoder Controller (BSC/TRC) node in the mobile
telephony system CME20.

RTS handles three main functions:

Setup and Maintenance of connection services to BTS equipment

Setup and Maintenance of Transcoder and Rate Adaptor Equipment

Operation and Maintenance of SNTs and transmission devices


RTS
STRUCTURE
RTS has the following Structure:

Abis Communication (BG-ABIS)

Coordination (BG-COORD)

Transmission Equipment Handling (BG-TRANSM)

Transceiver Handling (BG-TRH)

Transcoder and Rate Adopter Handling (BG-TRA)

Gb Interface and Packet Control Unit (BG-GbPCU)
BLOCK GROUP TRANSCODER (BG-TRA)

BG-TRA is part of the TRC Node.

Main Functions Include
Administration of Transcoder and Rate Adapter
Maintenance of Transcoder and Rate Adaptor
Start and Restart of Transcoder and Rate Adaptor
Configuration of Transcoder and Rate Adaptor
Interface to Fixed Transcoder and Rate Adaptor Devices
Interface to Pooled Transcoder and Rate Adaptor Devices
Supervision of Transcoder and Rate Adaptor Pools
Maintenance of Transcoder and Rate Adaptor Pools
Administration of Transcoder and Rate Adaptor Pools

Function of a Transcoder
The function of a Transcoder is to perform encoding/decoding of speech
signals and rate adaption of data information.

The function of converting the PCM coder information to the GSM
speech coder information is called transcoding. This fuction is both
present in the MS and BSS.

Rate Adaption involves the conversion of information arriving from the
MSC/VLR at a rate of 64Kbits/sec to a rate of 16Kbit/sec for transmission
to a BSC for a full rate call. 13Kbits/s represent speech and 3Kbits/s
represent inband signalling information.

The TRC contains units which perform transcoding and rate adaption,
These hardware units are called Transcoder and Rate Adaption Units
or TRAUs.


The transcoder functions that are controlled by the BTS include


Shift between data and speech


Control of rate adaption functions at data transfer


Downlink frame timing for speech frames


DTX control information
MULTIPLEXING and DEMULTIPLEXING OF CHANNELS.

The transcoder multiplexes a number of compressed traffic channels
into one 64 Kbit/s transmission channel. The number of channels
multiplexed and carried on one multiplexed device depends on
the channel rate of the speech codec for eexample

4 traffic channels for FR and EFR

8 traffic channels for HR.

Demultiplexing of one 64Kbit/s transmission channel yields a number
of decoded (not compressed) traffic channels carried on demultiplexed
devices depending on the channel rate of the speech codec for example

4 Traffic channels for FR and EFR
8 Traffic Channels for HR
Options for implementing the TRC

BSC/TRC :A combined BSC and TRC

Standalone BSC and Standalone TRC
- Optimised for low and medium Capacity
Applications. Can support 16 remote BSCs.

Diagram on the next page shows an example of
this type of implementation.



Location of transcoder in GSM
Digital
cellular
subscriber A
PSTN
subscriber
Base
Station
BTS
Transcoder
Node
TRA
TRC
PLMN
subscriber B
BTS
TRC/BSC
GMSC
16 kbit Full Rate Channel
8 kbit Half Rate Channel
PCM 64kbps
Base
Station
Controller
BSC
MSC
TRA
Ater
Abis A
Abis
BSS
Semi-permanent connection
" A semi-permanent connection is if all transcoders are continuously
connected to the same base station.
" Disadvantage:
If a transcoder board gets faulty the BTS cant be used
For every possible connection there has to be a transcoder
BSC/TRC
TRA 1
TRA 2
TRA n
BTS 1
BTS 2
BTS n
PSTN
1
n
Transcoder in pool
" In a transcoder pool the group switch connects the transcoders only
during the calls
" Advantage:
Less transcoder HW is needed
Redundancy
BSC/TRC
BTS 1
BTS 2
BTS n
TRA n
TRA 1 TRA 2
Transcoder pool
Group Switch PSTN
CONCEPTS
TRANSCODER (TRA)

SPEECH CODEC

MULTIPLEXED DEVCE (MUX)

DEMULTIPLEXED DEVICE (DEMUX)

SWITCHING NETWORK TERMINAL
(SNT)

SEMI-PERMANENT CONNECTION

TRANSCODER POOL

EM


Explaination of Terms

Transcoder:
Handles encoding/decoding of speech, and rate adaptation of data information
between the format used on the A-interface and the format used on the Abis
interface.

Speech CoDec:
Combination of a channel rate and a speech version. FR is the speech CoDec
type utilizing speech version algorithm 1. EFR is the full rate speech CoDec
type utilizing the speech version algorithm 2 for GSM and PCS 1900. HR is
the speech CoDec type utilizing speech version algorithm 1. AMR FR is
speech CoDec type utilizing speech version algorithm 3 for FR.
AMR HR is speech CoDec type utilizing speech version algorithm 3 for HR.



Multiplexed Device (MUX):
A 64Kbit/s device carrying 4 FR, EFR or AMR FR TCHs,
each being a 16Kbit/s subchannel on the device.
HR or AMR HR carries 8 TCHs, each being an 8Kbit/s
subchannel carried on the MUX device.
The device is connected to the BTS via a transmission device.
One MUX caters for the communication on 4 or 8 DEMUXs.

Demultiplexed Device (DEMUX):
A 64Kbit/s device, carrying one traffic channel. It is used to connect
traffic channels to the MSC via an A-interface line terminal (RALT).

Switching Network Terminal (SNT)
Unit that, via a digital link consisting of 32 x 64Kbit/s channels, is
connected to the Group Switch. For TRA-R6, the digital link consists of 256
x 64Kbit/s channels.


Semipermanent Connection
Interconnection of devices through the Group Switch. The interconnection
setup and release of a TRA device is not performed on a per call basis.
Transmission is supervised in the same way as ordinary connections
are supervised.



Transcoder and Rate Adaptor Pool
Resource pool containing a number of TRA resources supporting a specific
channel service. TRA resources are seized on a per call basis from a TRA pool.


Extension Modules (EM) group together TRA devices.
An EM for TRA-R6 can handle 192 traffic channels. For other TRA HW types
an EM handles 24 traffic channels. A traffic channel is the logical channel
that carries the speech or data information.
HIERARCHY
RP


EM


SNT


DEVICE

Understanding the Hierarchy


RP = Working(WO)
EM = Working(WO)
SNT = Working(WO)
DEV = Idle

ACTION: Block the RP.
BLRPI:RP = XXX;


RP = BLOC MBL
EM = BLOC CBL
SNT = BLOC CBL
DEV = BLOC CBL



Understanding the Hierarchy


RP = Working(WO)
EM = Working(WO)
SNT = Working(WO)
DEV = Idle

ACTION: Block the EM.
BLEMI:RP = XXX,RPT=XXX,EM=XXX;


RP = Working(WO)
EM = BLOC MBL
SNT = BLOC CBL
DEV = BLOC CBL



Understanding the Hierarchy


RP = Working(WO)
EM = Working(WO)
SNT = Working(WO)
DEV = Idle

ACTION: Block the SNT.
NTBLI:SNT=XXX.


RP = Working(WO)
EM = Working (WO)
SNT = BLOC MBL
DEV = BLOC ABL



Understanding the Hierarchy


RP = Working(WO)
EM = Working(WO)
SNT = Working(WO)
DEV = Idle

ACTION: Block the SNT.
NTBLI:SNT=XXX.


RP = Working(WO)
EM = Working (WO)
SNT = BLOC MBL
DEV = BLOC ABL



Understanding the Hierarchy


RP = Working(WO)
EM = Working(WO)
SNT = Working(WO)
DEV = Idle

ACTION: Block the EM,SNT,DEVICES.

1 BLEMI:RP=XXX,RPT=XXX,EM=XXX.
2 NTBLI:SNT=XXX.
3 BLODI:DEV=XXX

DEV = BLOC CBL DEV=BLOC CBL DEV=BLOC CBL
ABL ABL
MBL
TRA R2
1 SNT per EM -> 32 mups


6 TRABs per EM


6 Mux & 24 Demux per EM


1 Mux, 4 Demux per TRAB


Full Rate codec supported only


TRA R3

1 SNT per EM -> 32 mups


1 TRAB per EM


6 Mux & 24 Demux per EM



Full Rate codec supported only
TRA R4
1 SNT per EM -> 32 mups

2 TRABs per EM

FR, EFR and HR codecs supported

FR 1 TRA/EM 6 Mux & 24 Demux
EFR 2 TRA/EM 6 Mux & 24 Demux
HR 2 TRA/EM 3 Mux & 24 Demux


TRA R5
1 SNT per EM -> 32 mups

FR and EFR codecs supported

FR/EFR 1 TRA/EM 6 Mux & 24 Demux

FR capability of 12 Mux & 48 Demux per TRAB

RP-EM bus interface as TRA R4

Remotely loadable

TRA R6
1 SNT per EM -> 256 mups


Multiple codecs supported


1 TRA/EM Up to 48 Mux & 192 Demux


New CP-RPI interface


TRA R7(NOW NOT TAKING PLACE)
1 SNT per EM -> 512 mups


Multiple codecs supported


1 TRA/EM Up to 96 Mux & 384 Demux


Same CP-RPI interface as TRA R6


TRA R5 Subrack (front view)
T
R
A
B
-
0

T
R
A
B
-
1
5

D
L
H
B
-
B

D
L
H
B
-
A

R
P
4
-
0

R
P
4
-
1

GS
TSM

Plane A
B
Generic Ericsson Magazine,
GEM
T
R
A

T
R
A

T
R
A

T
R
A

E
T
1
5
5

E
T
1
5
5

E
c
h
o

E
c
h
o

E
c
h
o

E
c
h
o

E
c
h
o

S
y
n
c

S
y
n
c

C
l
o
c
k

C
l
o
c
k

D
L
E
B

D
L
E
B

S
w
i
t
c
h

S
C
B
-
R
P

E
T
1
5
5

E
T
1
5
5

T
R
A

T
R
A

S
C
B
-
R
P

S
w
i
t
c
h

Some Points on Hardware

Each CM controls 1 EM.

There is 1 EM per SNT.

Building Practise BYB202 is used for TRAs prior to TRA R5A/R5B.

Building Practise BYB501 is used for TRA R5A/R5B and R6.

Each TRA R5A/R5B subrack is connected to the GS via a DL3. Each DL3
is demultiplexed into DL2s in the backplane.

Each TRA R6 is connected to the GS via a DL34.

For HW versions up to TRA-R6, the EM also contains the EMC6, which is
the general interface between an EM and the controlling software, and the
TPLU, which is the general interface towards the GS. One RP pair controls
up to 16 TRA-EMs through the duplicated EMB.






Data Links

DL2: 2Mb/s Data Link corresponding to 32 MUP in the GS.

DL3: A data link which is made up of 16 DL2s which corresponds to
512 Multiple Positions in the Group Switch.

DL34: A Digitial link adaptablefrom version 3 to version 4.
Also a Serial Interface capable of carrying 2048 x 64Kbit/s
channels. When configured to communicate with a TRA-R6
SNT, up to 256 TRA devices may be connected to each SNT over a
DL34 link. One device per connection point in the APT 1.5 GS.
Physical Connections in BSC
CP-B
CP-A
RP RP RP RP
EM
0
EM
1
EM
2
EM
3
EM
15
TSM-a-b
TSM-x-y
DL2
DL2
DL2
DL2
EM Bus A
EM Bus B
RP Bus
RPM6A RPM6A
GS
DL2
Extension Modules (EM) group together TRA devices.
An EM for TRA-R6 can handle 192 traffic channels. For other TRA HW types
an EM handles 24 traffic channels. A traffic channel is the logical channel
that carries the speech or data information.


RPs control the boards that are grouped together and located in magazines
in the exchange.
Regional Processors are used for all communication with hardware in the AXE.
A maximum of 16 boards per RP pair are possible.

NEXT SLIDE



DIAGRAM OF TRA HANDLING FUNCTIONS.
RTTPRINT
RTTPR
ROEPC
RTTCGC
DEVICE RTTRC
TRA-HW
RTTRL
ROEXDA

ROEXDAP
SNT
RTTPH
APZ
ALARM
HANDLING
SNTDA

SNTMC
RTDPLC
RTTPSC
RP
RTSDI
RTPDI RTTPC
APZ
ALARM
HANDLING

ROSEMI
DEVICE OWNERS.


A device owner handles the administration and maintenace
of TRA devices. This includes:

Connection and disconnection of devices to and from an SNT

Blocking and Deblocking of devices

Distribution of device fault information

Testing of devices when a loop test is ordered

Testing of devices when performing an SNT test

LIST OF DEVICES.

Mother Block: RTTRD (no clones)

Mother Block: RTTF1D
Clone Blocks: RTTF1D1, RTTF1D2, RTTF2D, RTTAF1D

Mother Block: RTTH2D
Clone Blocks: RTTH1D, RTTAH1D

Mother Block: RTTGD (no clones)


SNT OWNERS

SNT PERFORM THE FOLLOWING FUNCTIONS

Administration of the devices for Transcoding and Rate Adaptor
function within the SNT.

Maintenance of the devices for Transcoding and Rate Adaptor
function within the SNT.

Handles all SNT and EM/CM functionality and coordinates
device alarms with SNT alarms.

Signalling to and from the TRA hardware is directed through the
SNT owning block to the device owning block.



LIST OF SNT OWNERS in CP.

Mother Block: RTTRS (no clones)

Mother Block: RTTF1S
Clone Blocks: RTTF1S1, RTTF1S2, RTTF2S, RTTAF1S

Mother Block: RTTH2S
Clone Blocks: RTTH1S, RTTAH1S

Mother Block: RTTGS (no clones)


LIST OF SNT OWNERS in RP.

Mother Block: RTTRSR (no clones)

Mother Block: RTTF1SR
Clone Blocks: RTTF1S1R, RTTF1S2R, RTTF2SR, RTTAF1SR

Mother Block: RTTH2SR
Clone Blocks: RTTH1SR, RTTAH1SR

Mother Block: RTTGSR (no clones)


The following blocks belong to BG-TRA:
Device Owners: CNT 242 1140
RTTRD/RTTAF1D/RTTAHID/
RTTF1D/RTTF2D/RTTF1D1/
RTTF1D2/RTTH2D/RTTH1D
RTTGD CNT 242 1149

SNT Owners: CNT 242 1141
CP RP
RTTRS RTTRSR
RTTAF1S RTTAF1SR
RTTAH1S RTTAH1SR
RTTF1S RTTF1SR
RTTF2S RTTF2SR
RTTH2S RTTH2SR
RTTF1S1 RTTF1S1R
RTTF1S2 RTTF1S2R
RTTH1S RTTH1SR
RTTGS RTTGSR CNT 242 1150

Other Blocks:
RTTPH CNT 242 1142
RTPDI CNT 242 1143
RTSDI CNT 242 1144
RTTPC CNT 242 1147
RTTPSC CNT 242 1148
RTTRC CNT 242 1145
RTTRL CNT 242 1146
RTTCGC CNT 242 1151
RTDPLC CNT 242 1160
TABLE OF MAIN BLOCKS
BELONGING TO BG-TRA.
The SNT owners, RTTRS, RTTAF1S, RTTAH1S, RTTF1S, RTTF2S,
RTTF1S1, RTTF1S2, RTTH2S, and RTTH1S handle 32 devices.
RTTRS/ RTTAF1S/RTTF1S/ RTTF1S1/ RTTF1S2 use 30 devices in 6 groups
of 1 MUX device and 4 associated DEMUX devices.

RTTF2S uses 24 devices in 5 groups of: 1 MUX device and 4 associated
DEMUX devices when MCC is activated. When MCC is not activated, RTTF2S
uses 30 devices in 6 groups of: 1 MUX device and 4 associated DEMUX devices.

RTTAH1S/RTTH2S/ RTTH1S use 27 devices in 3 groups of: 1 MUX device
and 8 associated DEMUX devices.


The SNT owner RTTGS (TRA R6) can handle 256 devices.
RTTGS uses 8 groups of 32 devices. Within each device group, the
MUX to DEMUX relationship is dependent on the CoDec to be applied by that
device group.

With the FR/EFR or AMR FR speech configuration, a device group
is comprised of: 6 MUX devices and 24 DEMUX devices,
with two unused devices in each group.

Each of the 6 MUX devices have 4 associated DEMUX devices.
For HR/AMR HR, a device group is comprised of:
3 MUX devices and 24 associatedDEMUX devices.

The remaining 5 devices (MUX & DEMUX) are unused.

SNT owners include two software units, a CP software unit
and an RP software unit.
The RP software unit controls the TRA HW.
One RP can handle up to 16 EMs.




Blocks RTTRD, RTTAF1D, RTTAH1D, RTTF1D, RTTF2D,
RTTF1D1, RTTF1D2, RTTH2D,RTTH1D, RTTGD
Radio Transmission, Transcoder and Rate Adaptor, Device Owning Block
Device Administration
The objective of device administration is to prepare a path
between theAbis interface line terminal and the TRA equipment.
This path differs depending on the node type.
Device administration handles the pre-seizure of MUX devices,
the seizure of MUX and DEMUX devices,
and the release of pre-seized or seized devices
for semipermanent connections.
Pre-seizing of a MUX device.

This sub-function handles the pre-seizingof idle TRA MUX devices
before a seizure request from RTSDI (via ROSEMI) or RTPDI.
An idle and fully connected MUX device with the greatest number of
associated, idle, DEMUX devices is pre-seized.
Seizure of a MUX device for semipermanent configuration.

This sub-function handles the seizure of pre-seized
TRA MUX devices for a semipermanent connection.
As a result of a request from RTSDI for a TRA MUX device/subdevice,
ROSEMI seizes a pre-seized MUX device/subdevice.
When seizing a complete MUX device,
a 64Kbit/s semipermanent connection through the GS is established.
When seizing a MUX subdevice, a 16Kbit/s semipermanent connection through
the GS is established. For successful seizure,
the device/subdevice must be pre-seized and in state idle.
If these conditions apply the device state is
changed to semipermanent busy and the GS rate is set to FR,
and (in the case of 16Kbit/s seizure) the MUX subdevice state is changed
to seized, and the GS rate is set to SR.

Release of MUX device from semipermanent configuratio

The release of a fixed TRA MUX device is ordered by ROSEMI.
RTSDI can order the release of a complete MUX device
or a MUX subdevice.
At a 64Kbit/s release of a TRA MUX device that is fully deblocked,
the device state is set to idle, otherwise the state is set to blocked.
At a 16Kbit/s release of a fixed TRA MUX subdevice,
the MUX subdevice state is changed to idle.
If all subdevices associated with the MUX are now idle
and if the device is fully deblocked, the MUX device
state is set to idle.
If it is not fully deblocked the state is set to blocked.
If all the remaining subdevices are not idle,
the MUX device does not change.
Seizure of a MUX device for TRA pool

This sub-function handles the seizure of pre-seized
TRA MUX devices for a TRA pool.
RTPDI seizes the pre-seized MUX subdevice.
For successful seizure, the subdevice must be pre-seized
and idle. If so, the MUX device state is changed to busy,
the MUX subdevice state is changed to seized,
and the GS rate is set to SR. The selected subdevice
is connected to a transmission device through the GS
on a per call basis.
Seizure of pooled TRAs is always on a 16Kbit/s basis
for FR/EFR/AMR FR and on a 8Kbit/s basis for HR/AMR HR.
Release of a MUX device from a TRA pool

TRA MUX subdevice is ordered directly by RTPDI.
At a release of a MUX subdevice,
the MUX subdevice state is changed to idle.
If all subdevices associated with
the MUX are now idle, and if the device is fully deblocked,
the MUX device state is set to idle.
If it is not fully deblocked, the state is set to blocked.
If all the remaining subdevices are not idle the MUX device
state does not change.
Seizure of DEMUX device

The DEMUX device is seized by RTSDI or RTPDI with reference
to the associated TRA MUX device/subdevice and the offset
required for the TRA DEMUX device.
If the associated TRA MUX device/subdevice has been successfully seized,
the idle DEMUX device is marked selected and busy.

Release of DEMUX device

RTSDI or RTPDI orders the release of
a TRA DEMUX device. If the device was busy,
the state is set to idle.
If the device was not busy, the state is set to blocked.
RTSDI or RTPDI always releases all DEMUX devices
associated with a MUX device/subdevice before the actual
release of the MUX device/subdevice.
RTTRL, Radio Transmission Transcoding and Rate Adaptor, Alarm Handling

RTTRL handles the alarm for strictly device-related
faults in the TRA equipment.
RTTRL performs the following functions:

Alarm Initiation.
An SNT owner orders RTTRL to initiate device
alarms when device faults are reported from the HW
and coordinated by theSNT owner.
The device alarm for failure of routine tests which has the lowest
priority and is not a fault defined by the HW itself.

Alarm Ceasing.
Alarm ceasing is handled in a similar way to alarm initiation.
Alarm Printout.
RTTRL prints out the slogan and column headings
for the device alarms.
RTTRC, Radio Transmission, Transcoding and Rate Adaptor,
Command Handling


RTTRC is the command handling block within the
Transcoding and Rate Adaptor function.
RTTRC commands perform the following tasks:

Change and print uplink and downlink line speech level adjustments.

Manually block and deblock MUX devices and print the results.

Attach and detach a DEMUX TRA device to a mobile traffic recording
reference. Print the mobile traffic recording references and the DEMUX TRA
device attached to the reference. Print the status of those DEMUX devices
attached to mobile traffic recording references.
RTTCGC, Radio Transmission, Transcoding Configuration Command Handling

RTTCGC is the configuration command handling block within the Transcoder
and Rate Adaptation Function. RTTCGC commands provide an operator with the
ability to configure SNTs of type R6 by using the manual configuration command.
This command allows the operator to change the CoDec, or combination of
CoDecs loaded on the board by specifying a combination
of channel rate and speech version.

Each device group in a TRA R6 board may be independently configured with
any of the CoDecs supported by the SNT owner. The CoDec type can be changed
by command once the SNT is manually deblocked and the associated devices are
not pool or semipermanently connected. The associated devices may be manually
deblocked. Speech CoDecs for FR, EFR, HR, AMR FR and AMR HR
are supported.
RTSDI, Radio Transmission, Interface to Fixed Transcoder Devices


RTSDI acts as an interface between the users in RTS and TRA handling for
semipermanent connections.

RTSDI coordinates the setup of semipermanent connections
of transmission devices to MUX devices at either
16K bits/s or 64K bits/s nand then the seizure of DEMUX devices.
Semipermanent connections are only valid for the FR speech CoDec type.

At start/restart RTSDI requests the HW priority from the FR device blocks.
RTTPC, Radio Transmission, Transcoder Pool Change


Block RTTPC handles administration of TRA pools.
RTTPC receives commands to:

Define a TRA pool which supports a specified channel rate and speech
version.

Delete a TRA pool.

Change the number of TRA resources in a pool.

Print statistical data for one,several, or all defined pools and data for
each subpool within the pool. The TRA devices belonging to the subpools
can also be printed.
RTPDI, Radio Transmission, Pool Device Interface

RTPDI contains the interface functionality between the TRA pool handler
(RTTPH) and the TRA device owning blocks. RTPDI holds the interface data
for all device resources which are selected for a TRA pool.

At start/restart RTPDI interrogates each of the device blocks on their
TRA capabilities and the HW priority.

RTPDI informs RTTPC if there are TRA resources available of a certain type
when requested at definition of a TRA pool.

RTTPH requests RTPDI to seize a DEMUX device from the device owning
blocks when the number of required pooled TRA resources is increased.
If the TRA capabilities match the required TRA resources the
HW priority is checked.

RTPDI then pre-seizes and seizes a MUX device and its associated DEMUX
devices from the appropriate device block.
RTTPSC, Radio Transmission, Transcoder Pool Supervision Change


RTTPSC performs the administration and execution of mean hold time and
idle level supervision of TRA pools. RTTPSC contains commands to
Connect a TRA pool to idle level supervision.
Disconnect TRA pool idle level supervision for the specified pool(s).

Print TRA pool idle level supervision information.
Connect a TRA pool to mean hold time supervision.
Disconnect TRA pool mean hold time supervision for the specified pool(s).
Print TRA pool mean hold time supervision information.
Print the TRA resources which is in an mean hold time alarm state.

For idle level supervision RTTPSC checks every 30 seconds with RTTPH
to see if there are any alarms to be issued, ceased, or changed for any pool.
For mean hold time supervision, RTTPSC checks with RTTPH every 5 minutes.
RTDPLC, Radio Transmission, Device Processor Loading Administration

RTDPLC allows an operator to load a device software unit from the CP program
store onto a TRA board. This applies to all TRA boards apart from R2 and R6
boards. R2 boards are not loadable and the R6 boards are loaded with RSUs
using existing APZ commands. The commands in RTDPLC allow an operator to

Load up to 32 SNTs with a tied device software unit from the central
processor program store into TRA-EMs.

Abort loading of an SNT.

Print the identity of the device software programs currently loaded
on the TRABs in the TRA-EMs.

In order for loading to occur all devices on the affected boards must be
manually blocked and the SNT must be manually blocked. The device software
identity or block name must be tied by command to the equipment to be loaded
or to the SNT block name.
Presentation

on

Radio Transmission, Transcoder Pool Handler

or

RTTPH
RTTPRINT
RTTPR
ROEPC
RTTCGC
DEVICE RTTRC
TRA-HW
RTTRL
ROEXDA

ROEXDAP
SNT
RTTPH
APZ
ALARM
HANDLING
SNTDA

SNTMC
RTDPLC
RTTPSC
RP
RTSDI
RTPDI RTTPC
APZ
ALARM
HANDLING

ROSEMI
RTTPH

Part of the Radio Transmission and Transport Subsystem (RTS)

Defines Transcoder Pools

Deletes Transcoder Pools

Changes Transcoder Pools

Supplies block RTTPSC with supervision data

Seize Transcoder Resources

Release Transcoder Resources

Handles Fault situations and statistics of Transcoder Pools
TRANSCODER POOL PRINTOUT EXAMPLE:

COMMAND:rrtpp:trapool=fr1p,printdev;

RADIO TRANSMISSION TRANSCODER POOL DETAILS
TRAPOOL CHRATE SPV RNOTRA POOLACT POOLIDLE POOLTRAF
FR1P FR 1 6 6 6 0

SUBPOOL SUBACT SUBIDLE SUBTRAF
0 3 3 0
2 3 3 0

DEV SUBPOOL
RTTRD-9 0
RTTRD-10
RTTRD-11
RTTF1D-3 2
RTTF1D-4
RTTF1D-5
END

Maintaining TRA Resources

RTTPH maintains the TRA resources stored in the TRA pools.

RTTPH maintains the number of TRA resources in a pool by replacing
faulty TRA resources in a pool.

Information for each pool is stored in the TRA Pool file and information
on each MUX in pool is stored in the TRA Individual file.

Information on each TRA resource is stored in the TRA Resource file.

The MUX devices are grouped into sub-pools using linked lists.

All TRA devices in a sub-pool provide the same channel services
and have the same features.

Changing the Size of a Pool

When a request to change the size of a pool is received, the number of
available TRA resources in a pool is checked against the requested number.
If the requested number is greater than the number of available resources,
TRA resources are seized from RTPDI. If the requested number of resources
is less than the number of available resources, the TRA resources are
removed from the pool when they become idle.

The command used to increase or decrease the pool size is called RRTPC:

Radio Transmission Transcoder Pool Change (RRTPC).

When this command is used in conjunction with the FORCE parameter,
it permits unconditional removal of transcoders from the Transcoder Pool.



Seizing a TRA Resource

A request to seize a TRA resource for traffic is received from the block
RTTPR, which sends a list of preferred channel services.

A TRA resource is seized from a pool according to the channel service first
in the list.
If no TRA resource of the type is available, the next channel service from
the list is used.

The process is repeated until the TRA resource is found, or
there are no more channel services in the list.

SPEECH AND DATA CALLS

Speech and data calls are treated differently.

For a data call the TRA with the lowest capability that provides the required
data rate is used for the call. For a speech call the highest capable
TRA available that provides the required speech CoDec is used for the call.
This ensures that a speech call gets the TRA which provides
the best speech quality available. A low capable TRA is has few TRA features.
A high capable TRA has several features.

For Example if a pool is created with Channel Rate = FR and SPV=1
and populated with RTTRD, RTTF1D, RTTF1D1, RTTGD devices
and then a data call is made, RTTRD will be seized for this data call as it is the
TRA with the lowest capability and provides the required data rate.

If a speech call was being made, RTTGD will be seized.

To maximise the use of the SRS, if there is an idle DEMUX of the required
channel service and sub-pool on an already seized MUX connection to the
SRS,that TRA is used for the call. Otherwise a new MUX connection to the
SRS is seized.

Supplying block RTTPSC with Supervision Data.
On request from the block RTTPSC the number of idle TRA resources and the
number of required TRA resources are sent. Also on request from RTTPSC, the
alarm counter for the pool is sent. The alarm counter counts TRA resources
that have mean hold time below the alarm level for the pool. Hold time is
calculated during the traffic process. Each TRA resource individual stores
the time (in seconds) when it was seized. When it is released the 'release
time minus the storage time' is the new hold time. For the first 64 times
a resource is allocated the hold times are added together. This is the mean
hold time for the TRA. The new mean hold time for the next and subsequent
allocations is calculated from the formula below.
New MHT = Old MHT - Old MHT/64 + New HOLD TIME

The overall mean hold time for all the resources in the pool is calculated
every 5 minutes. This is multiplied by a an alarm percent specified by the
operator when connecting the function for a pool. This leads to a weighted
mean hold time for the whole TRA pool. Each individual TRA resource mean hold
time is compared to this weighted mean and if lower, the resource is marked
as alarmed. RTTPSC is informed at every 5 minutes to issue an alarm on such
DEMUX devices.



LOOP TEST

On request from RTTPR, RTTPH seizes a pooled TRA resource for loop test.
Loop test can only be performed on FR and EFR devices.

A device with a different channel service and a different priority is tested each
time if possible. Once a device has been seized a link is established between the
TRA device and the A-is transmission device to the BTS.

RTTPR orders a loop test to be carried out on the TRA device in the device
block. The device owning block returns the result of the loop test to RTTPR.
RTTPR orders RTTPH to release the TRA device which was seized for loop test.

Mobile Test Call

When a TRA DEMUX device which is in pool is attached to a mobile traffic
recording reference, RTTRC informs the device owner.

It in turn informs RTPDI which informs RTTPH that the pooled resource
is reserved for mobile traffic recording.

At call setup if a valid mobile traffic recording reference is
received in the call setup request, the TRA with that recording reference
is used for the call - if it is idle and can provide one of the requested
channel services. Otherwise the call is dropped.
Mobile Test Call Contd

There are commands provided to:

Attach a TRA to a mobile traffic Recording Reference.
The recording Reference is a number with a possible value 0-65535.


Detach a TRA from a mobile traffic recording reference


Print a table of mobile traffic recording references and the DEMUX
device the reference is attached to. The status of the DEMUX devices
is also given in this table.

Fault Handling

RTPDI informs RTTPH of faulty TRA resources.

If the TRA resource is used for traffic the TRA is marked faulty
and RTTPR is informed.

The TRA resource is removed from the pool
(RTTPH releases the TRA resource to RTPDI) when RTTPR
has released the TRA resource.

If the TRA resource is not seized for traffic, it is removed from the pool.
Presentation

on

Codecs

and

Channel Service Overview.
Terminology.
Channel Rate

Speech Version

Speech CoDec

Uplink Line Speech Level

C/I

Codec Rate

Codec Mode

Codec Set





Channel Rate
The available transmission bandwidth on a TCH for speech or data. Channel
rate can be Full Rate/Enhanced Full Rate (FR/EFR), Half Rate (HR), Adaptive
Multi Rate FR (AMR FR) or Adaptive Multi Rate HR (AMR HR).

Speech Version
The variant of speech encoding algorithm within the same channel rate.
There are three speech versions (speech version 1, 2, 3).

Speech CoDec
Combination of a channel rate and a speech version. FR is the speech CoDec
type utilizing speech version algorithm 1. EFR is the full rate speech CoDec
type utilizing the speech version algorithm 2 for GSM and PCS 1900. HR is
the speech CoDec type utilizing speech version algorithm 1. AMR FR is speech
CoDec type utilizing speech version algorithm 3 for FR. AMR HR is speech
CoDec type utilizing speech version algorithm 3 for HR.

Uplink Line Speech Level
Reference level of a speech signal from the BTS to the TRC.




















C/I
The ratio between the signal strength and the interference signal strength


Codec Rate
The bit rate of the coded speech after the speech coding
example: 12.2Kpps and 6.7Kbps


Codec Mode
A codec rate used within a codec set is called a codec mode


Codec Set
A set of up to 4 different codec modes (using the same channel rate)
example: 12.2, 7.95, 5.15 Kbps for a full rate channel


Speech codec
" The algorithm which is used to compress and decompress speech data
in a mobile system is called a speech codec.
" Speech codecs are optimized for speech data and the loss of speech
data on the air interface.
" A speech codec is always a compromise between speech quality and
bit rate.
Speech Codec
Uncompressed
Speech Data
Compressed
Speech Data
LIST OF CODECS


FR = Full Rate


HR = Half Rate


EFR = Enhanced Full Rate


AMR = Adaptive Multi Rate



Transcoder
" The basic functionality of a transcoder is to convert data from one
coded format into another, i.e. a transcoder includes 2 speech codecs.
" Example:
PCM coding to Full Rate coding and vice versa.
104 kBit/s
PCM coded
Speech Data
(64 kBit/s)
FR coded
Speech Data
(16 kBit/s)
Transcoder
Speech codec examples for GSM
systems
" Full Rate codec (FR)
Was the first codec introduced in the GSM system.
It reduces the incoming data from 64 to 16 kBit/s, incl. signalling.
" Enhanced Full Rate codec (EFR)
It reduces the incoming data from 64 to 16 kBit/s, incl. signalling.
The speech quality is better compared to the Full Rate Codec but the
algorithm demands more processor capacity
" Half Rate codec (HR)
It reduces the incoming data from 64 to 8 kBit/s, incl. signalling.
Under good transmission condition it is better than the FR codec, but
under normal (worse) circumstances the speech quality is below the FR
codec.
The algorithm demands more processor capacity than EFR
HR increases the capacity by 100 %.
Speech codec examples for GSM
systems
" Full Rate codec (AMR FR)
New codec type introduced in the GSM system.
Offers good speech Qualiy at low C/I

" Half Rate codec (AMR HR)
New codec type introduced into the GSM system.
Offers good speech Qualiy at low C/I
Substanially better then the HR SPV1 HR codec
BACKGROUND INTO AMR

AMR is a codec type that makes it possible to offer good speech at a low
C/I.

During an AMR call the codec rate changes depending on the quality of
the radio channel.

Selection of Codec is based on measurements of the uplink and downlink
radio channel.

Codec rate used on the uplink can be different than the codec rate used
on the downlink channel.

Eight different Codec Rates available in the AMR transcoder. All eight are
available for FR channels and the five lowest can be used for HR channels.
( as seen later)
Speech Coding
" speech encoding and decoding
Full Rate Channel with 16 kbit/s Abis/Ater Interface
" EFR with net bit rate of 12.2 kbit/s (most important at the
moment)
" FR with net bit rate of 13 kbit/s
" AMR/FR with net bit rates between 4.75 and 12.2
kbit/s(=EFR)
Half Rate Channel with 8 kbit/s Abis/Ater Interface
" HR with net bit rate of 5.6 kbit/s
" AMR/HR with net bit rate between 4.75 and 7.4 kbit/s
(7.95 kbit/s is not supported, because of too few control
bits)
POOLS INFORMATION.

Speech Codec Subpool Pool Capabilities Boards
FR 0 FR Speech, FR Data R2/R3
1 FR Speech, FR Data,14.4, MCC R4
2 FR Speech, FR Data,14.4,MCC R5a,R5b,R6

EFR 0 EFR Speech, FR Data,14.4,MCC R4
1 EFR Speech, FR Data,14.4, MCC R5a,R5b,R6

HR 0 HR Speech R4
1 HR Speech,MCC R5a,R5b,R6

AMR FR 0 AMR FR Speech R6
FR Data,14.4,MCC

AMR HR 0 AMR HR Speech R6
HR Data,MCC


TRA R6 Hardware (RTTGD)

An operator will have the ability to configure Transcoder and Rate Adaptor
Boards of type R6 by the use of two commands.
One command to configure the board and the other to printout the current
transcoder device configuration on the board.

This means RTTGD can support FR, EFR, HR, AMR.
Depending on how the device has been configured it will support one of the
above codecs.

Command to Configure:
RRTCC = Radio Transmission Transcoder Configuration, Change

Command to Print:
RRTCP = Radio Transmission Transcoder Configuration, Print





Table of:

Channel Mode, Channel codec Mode, Speech codec Rate, Sub Channel Rate

TCH/AFS(22.8) TCH/AFS12.2 12.2 16
TCH/AFS10.2 10.2 16
TCH/AFS7.95 7.95 16
TCH/AFS7.40 7.40 16
TCH/AFS6.70 6.70 16
TCH/AFS5.90 5.90 16
TCH/AFS5.15 5.15 16
TCH/AFS4.75 4.75 16
TCH/AHS(11.4) TCH/AHS7.4 7.40 8
TCH/AHS6.7 6.70 8
TCH/AHS5.9 5.90 8
TCH/AHS5.15 5 .15 8
TCH/AHS4.75 4.75 8







Speech Version and Channel Rate Combinations


Speech Version Channel Rate Codec

1 FR FR

2 FR EFR

3 FR AMR FR

1 HR HR

3 HR AMR HR
AMR WORKING


At call setup an active codec set (ACS) and a channel rate are selected. The
ACS is a subset of the 8 codecs mentioned above containing up to 4 codec
modes. During the call the BTS shall constantly measure the C/I and change
between the codec modes accordingly. For example if the C/I is good, 12.2
kbps speech codec can be selected which gives the best quality in good
radio conditions. But if the C/I drops it is better to use a lower and more
robust codec with better channel coding to maintain the best possible speech
quality.

Note : According to the standard 12.2 kbps and 10.2 kbps can only be used
for FR channels and the other 6 can be used in both HR and FR channels.
Due to problems of using 7.95 on 8 kbps ABIS it has also been decided that
7.95 kbps shall only be used with FR channels in the Ericsson
implementation.







EXCHANGE PROPERTIES FOR SUPPORTING AMR.

AMRSUPPORT DEFAULT SET
0 AMR OFF
1 FR 1, HR1
2 FR 2, HR1
3 FR 1, HR 2
4 FR 2, HR 2


This shall be removed in the Enhanced AMR Project underway at the
moment. See following Slides
The following table is now used to determine which FR set is used as default.


AMRFRSUPPORT SETTING
0 AMRFRSUPPORT OFF
1 FR 1
2 FR 2
3 FR 3
4 FR 4
The following table is now used to determine which HR set is used as default.


AMRFRSUPPORT SETTING
0 AMRHRSUPPORT OFF
1 HR 1
2 HR 2
3 HR 3
4 HR 4
Benefits of AMR

Improves speech quality in both FR and HR channel rates


Improves Robustness to channel errors


Better speech quality for HR will make it more attractive for operators
to use HR, which in turn means higher capacity


A future enhancement is to combine power control with AMR to lower
the interference in the network and thereby increase the capacity.

Command Handling in GSM



Commands Commonly used in GSM Testing


Commands used in writing Approved Correction





Print state of the devices (e.g. TRA)

stdep:dev=rttrd-0&&-11;

Print state of EM
exemp:em=all,rp=all;

Print state of RP
exrpp:rp=166

Print sate of SNT
ntstp:snt=rttrs-0;



RRTBI A command for Manual BlockingTranscoder Devices.


RRTBE A command for deblocking Transcoder Devices.



RRLLC A command to change uplink and downlink line speech level
in dB within a BSC/TRC.
RRLLP A command to print the current uplink and downlink line
speech level in dB within a BSC/TRC.


RRTRI A command to attach a transcoder device to are cording
reference using for mobile traffic recording.


RRTRE A command to detach a transcoder device to a recording
reference using for mobile traffic recording.


RRTRP A command to initiate the printout of mobile traffic recording
references, the transcoder devices attached to them and the status of the
corresponding transcoder resources.
RRLLP A command to print the current uplink and downlink line
speech level in dB within a BSC/TRC.


RRTRI A command to attach a transcoder device to are cording
reference using for mobile traffic recording.


RRTRE A command to detach a transcoder device to a recording
reference using for mobile traffic recording.


RRTRP A command to initiate the printout of mobile traffic recording
references, the transcoder devices attached to them and the status of the
corresponding transcoder resources.
Printouts
Answer printout:

RADIO TRANSMISSION LINE SPEECH LEVEL DATA
A printout showing the uplink and downlink line speech level data.

RADIO TRANSMISSION TRANSCODER TEST CALL DETAILS
A printout indicating mobile traffic recording references, the transcoder
devices attached to them and the state of the corresponding transcoder resources.


RADIO TRANSMISSION TRANSCODER CONFIGURATION DATA
This printout shows ranges of devices and their associated codec. This
printout is the answer printout to command RRTCP.

RADIO TRANSMISSION DEVICE SOFTWARE UNIT INFORMATION
A printout gives information about the device software units associated
with an SNT(s).
Result Printouts:

RADIO TRANSMISSION MANUAL BLOCKING OF
TRANSCODER DEVICES RESULT

A printout indicating the blocking of transcoder devices request result.


RADIO TRANSMISSION MANUAL DEBLOCKING OF
TRANSCODER DEVICES RESULT

A printout indicating the deblocking of transcoder devices request result.


RADIO TRANSMISSION TRANSCODER CONFIGURATION RESULT
This printout indicates the result of configuration of a range of transcoder
devices. This printout is the result printout for command RRTCC.

RADIO TRANSMISSION DEVICE SOFTWARE UNIT LOAD RESULT
This printout indicates the result of loading a DSU into TRA-EMs.
Alarm Printout:

RADIO TRANSMISSION TRANSCODER AND RATE ADAPTOR FAULT
A printout indicating a fault found by the transcoder equipment or its
software.

RADIO TRANSMISSION TRANSCODER DEVICE RESERVED
FOR TEST CALL

A printout indicating that at least one transcoder devoce is reserved for
a test call.

BEFORE YOU START !!!
====================
saosp; ! Prints operating system info. !
lasip:block=mbtrac; ! Prints block revision. !
pcorp:block=mbtrac; ! Prints loaded corrcetions for block.!

pcore:block=mbtrac,ia=h'36AD; ! End correction - passivates.!
pcorr:block=mbtrac,ia=h36AD; ! Removes correction. !

pcorl:block=mbtrac,ia=h36AD,ci=m25ad8728; ! Load Correction. !
pcori:block=mbtrac,ia=h36AD; ! Initate correction. !
pcors:block=mbtrac,ia=h36AD; ! Confirms correction - and so !
! at restart is not passivated.!
pcodp:block=mbtrac,IS=H'11A0-H'11EA; ! Prints ASA in range. !

pcsdl:block=mbtrac,SIGNAL=READINFOREQ,IA=H'123;
! loads SDL into s/w unit.!
pcssl:block=mbtrac,SSP=36,SIGNAL=WRITEINFORPY;
! loads SST into s/w unit.!


syrip:survey; ! Prints software recovery information - e.g. !
! system restarts, software errors application !
! errors. !

syrae:event=56; ! Passivates error event 56.!
syrae:rectype=applerr; ! Passivates all appplerr. !
CHECK WHAT DUMP IS LOADED
=========================
ioexp;



LOAD A NEW DUMP
===============
(exslp:spg=0;) ! Shows state of link. (optional) !
fcsli:spg=0; ! Seperates link between CP and an SPG. !
! (support processor group). !
fcsei; ! Seperates and faultmarks SB side, !
! i.e. changing the state of the SB-side !
! from SB/WO to SB/SE-FM. !
sybfp:file; ! Prints System Backup Files. !
fccpl:file=relfsw1; ! Loads file into SB side. !


Examples of Commands and their Parameters

pcorp:block=rtth1d;
pcorp:block=rtth2d;
exdae:dev=rtth1d-2&&-31;
exdae:dev=rtth1d-8&&-31;
exdae:dev=rtth1d-18&&-31;
exdae:dev=rtth1d-28&&-31;
EXDUE:DEV=RTTH1D-2&&-31;
ntcop:snt=rtth1s-0;
ntbli:snt=rtth1s-0;
BLEMI:EM=15,RP=97,RPT=96;
EXEME:EM=15,RP=97,RPT=96;
NTCOE:SNT=RTTH1S-0;
exrup:rp=96;
laeip:block=rtth2s;
fcrws:rp=96,ws=sep;
BLRPI:RP=96;
BLRPI:RP=97;
EXRUI:RP=97,RPT=96,SUNAME=RTTH2S;
EXRUI:RP=97,RPT=96,SUNAME=RTTH2Sr;
EXEMI:RP=97,RPT=96,EQM=RTTH2S-0&&-31,EM=15;
NTCOI:SNT=RTTH2S-0,SNTP=MUX3-0-15,SNTV=1;
EXDUI:DEV=RTTH2D-0&&-31;
ntble:snt=rtth2s-0;
BLRPE:RP=96;
BLEME:RP=97,RPT=96,EM=15;
blemi:rp=97,rpt=96,em=15;
EXDAI:DEV=RTTH2D-2&&-31;
EXDAI:DEV=RTTH2D-8&&-31;
EXDAI:DEV=RTTH2D-18&&-31;
EXDAI:DEV=RTTH2D-28&&-31;
stdep:dev=rtth2d-2;
rrtbe:dev=rtth2d-2;
BLEME:RP=97,RPT=96,EM=15;
rrtbe:dev=rtth2d-2;
stdep:dev=rtth2d-2;
WEB Links




http://deltawww.ericsson.se/delta_bin/delta_access

What is?

http://www.whatis.com/

Ariadne

http://uabweb.uab.ericsson.se/inside/units/x/th/ariadne/

BSC R9

http://bss.ericsson.se/iiop/GenFrames?docno=web-00%3A9378

Lazy Moose

http://www.exu.ericsson.se/grc-external/Lazy/fm3g/index.htm

--

ALEXSERV LINK



http://alex-bscsuply.lmera.ericsson.se/cgi-bin/alex
END of PRESENTATI ON

Thank you for your Attendance