Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
CH1. Introduction
CS TRANSPORT NETWORK
call routing and switching charging (CDR) interface to external networks INCOMING CALLS
Abis BSC
RBS AXE RPP
VLR
PCU
Packet Control Unit
MSC
AXE
AXE
GMSC
Intermediate exchanges
AXE
Intelligent Network
AUC
EIR
SCP
AXE/TSP
UNIX
Gb Gd Gr
Service Control Point Optional (specified). In practice not implemented no mobile terminated data services
Internet
Gf
Ge
Iub RNC
CPP
Iu SGSN
WPP
Corporate Intranet
B-Node
CPP
packet routing and switching charging (CDR) database (subs. profiles) WPP: Wireless Packe Platform, AXE cabinet security mobility management compliant J20: platform invented by JUNIPER (now ///) session management CIPHERING CPP: Connectivity Packet Platform compression (IP, payload) - /// features TSP: Telephony Server Platform (in future replacement of AXE) RPP: Regional Processor with PCI bus
Gateway GPRS Support Node packet routing and switching charging (CDR) session management interface to external networks OUTGOING PACKET TRANSFERS
Streaming Services
Telemetry
[OH] Fig.1-3. Page 13: Structure of BSS and interfaces Impact on RBS and A-bis OLD RBS 2000 cTRU
CS-1&2 new software CS-3&4 new hardware s cTRU classical (old) CS 1&2 sTRU single CS 1 - 4 + EDGE
NO Local Bus
cTRU cTRU
dTRU
dTRU
Um
A-bis
BSC/ TRC
5 6 7 0 1 2 3 4 30 31
CS 1-4 EDGE
SARA Service Oriented Allocation of Resources On A-bis Interface Problem with speech transmitted over TSs 4-7 wastage of resources on A-bis
[OH] Fig.2-3. Page 20: PCU using frame relay with more than One RPP (CS-1 and CS-2)
Group Switch
Regrional Processor with PCI Bus A Power PC processor running at 333 MHz. 64 MB of SDRAM More than four times the CPU/memory capacity of the RPG Dual 10/100 Base TX Ethernet Two DL2 Group Switch interfaces Communicates via other RPPs via ethernet (duplicated) May work towards Gb and Abis RPP#1 or towards Abis only RPP#2 Cell may be controlled by one RPP only
Ethernet
GS
Gb
RPP#1
Abis
SGSN
RPP#2
1 RPP ~ 4 RPG
SRS RPG
Subrate Switch (used for CS1 & CS2)
D E R L P RPP RPP P #1 H S #2 4 B B
E P S B
D R L P H 4 B
Slot
0 1 2 3 4 5 6 7 8
15
[OH] Fig.2-6. Page 24: GDM magazines equipped with RPPs (BYB501 hardware)
Function of DLHB DL 2 2Mb/s 0 1 2 3 4 5
GS
D L H B
16 logical connections
PCU Limitations Maximum number of RPP: 64 book, now 128. Maximum number of Cells: 512. Maximum number of PDCHs: 4096. RPP Limitations Maximum number of PDCHs: 150 software limitation (6 DSP*25 PDCHs) Maximum number of PDCHs: 64 hardware limitation for CS3&4, EDGE (64 Devices) Can work only towards Gb
0 1 2
RTGPHDV-0&&-31
29 30 31
DSP #1
DSP #2
DSP #3
DSP #4
32 33 34
RTGPHDV-32&&-63
GS
61 62 63
DSP #5
DSP #6
DSP #7
LPDCH~PDCH
RADIO
2 Different RPP configurations RP working towards Gb and Abis Max 150 PDCHs for CS 1&2 Max 45 PDCHs for CS 3&4 and EDGE
0 1 2
DSP #1
DSP #2
DSP #3
DSP #4
32 33 34
SGSN
GSL Devices
61 62 63
DSP #5
DSP #6
DSP #7
DSP #8
RP working towards Gb and Abis Max 150 PDCHs for CS 1&2 Max 64 PDCHs for CS 3&4 and EDGE Not used
0 1 2
GS GSL Devices
29 30 31
DSP #1
DSP #2
DSP #3
DSP #4
32 33 34
SGSN
GSL Devices
61 62 63
DSP #5
DSP #6
DSP #7
DSP #8
TRH
Compression S
S LLC frame
MSC
SGSN TRAU
Segmentation
RPP#1
S
RPP#1
RPP#2
RPP#2
SRS
COMMAND DESCRIPTION C change, I initiate, E end, B block. Activation of GPRS Support in BSC SYPAC: ACCESS=ENABLED, PSW=XXXXXX; DBTRI; DBTSC: Command changes access for updating the values of AXE parameters Access is enabled Access password must be given Initiates database transaction Changes data fields for an existing row in a table TAB=AXEPARS, Specifies table SETNAME=CME20BSCF, Specifies parameter set NAME=GPRS, VALUE=1; Specifies parameter, and value (1=active) NAME=GBCAPACITY, VALUE=2; Specifies Gb capacity (0-1023 in 64kb/s steps) Commits database transaction Database is updated automatically
Access is disabled
Definition of RP Intercommunication Group (RPIG) DBTRI; DBTSI: TAB=RPSRPIGROUPS, GROUP=CHARLIE, GROUPNO=1; DBTRE: COM; Inserts a row in a table Specifies table Specifies name of intercommunication group Specifies number of intercommunication group
Enabling Ethernet in the PCU - concluded Connection of RP to Ethernet Group DBTRI; DBTSI: TAB=RPSRPIRPS, RPADDR=98, GROUP=CHARLIE; COM;
DBTRE:
Deblocking of RP NET A and NET B in RPIG BLRCE: GROUP=CHARLIE, NET=A; Checking Ethernet status (working/not) DBTSP: TAB=RPSRPISUPERVS, GROUP=CHARLIE, Address for RP which is supervising the communication RPADDR1=98, RPADDR2=99, Address for the other RP in the supervision NET=A; Intercommunication network Deblocking of RP communication net Net identifier (A or B)
Checking which RPs have state UP DBTSP: TAB=RPSRPISUPERVS, GROUP=CHARLIE, STATE=UP; Desired RP state (UP or DOWN)
Checking PCU configuration RRPCP: RPINFO; Prints PCU Configuration Data Specific info about RPP state is included
GS
SNT SNTP
EM 0 EM 1 EM 2
2. Software loading EXRUI: RP=99, SUID ="CXC 146 1002 R2A04"; Software Unit ID 3. Allocation of Extension Module EXEMI: SUID="CXC1461002R2A04", RP=99, EQM=RTGPHDV-0&&-63, EM=2; 4. Connection of Switching Network Terminal NTCOI: SNT=RTGPHDV-0, SNTV=1, SNTP=TSM-29-1; 5. Connection of Devices DEV=RTGPHDV-0&&-31; EXDUI: 6. Deblocking of EMs BLEME: RP=99, EM=0; 7. Deblocking of RP BLRPE: RP=99; 8. Deblocking of SNT SNT=RTGPHDV-0; NTBLE: 9. Taking devices into service EXDAI: DEV=RTGPHDV-0&&-31; 10. Deblocking of devices BLODE: DEV=RTGPHDV-0&&-31; 3
RPP
software 2
RP bus
CP-A CP-B
SNT name and number SNT version Switching Network Terminal Point
Gb Interface CH.4
Gb BSC Base Transceiver Station Packet Control Unit PCU Base Station Controller SGSN
Abis
Protocol Description user plane SNDCP Subnetwork Dependent Convergence Protocol multiplexing of PDP Contexts (different IP/QoS) IP packet segmentation (segment length is dynamically controlled by the network; good radio longer segment) IP header compression option, not implemented in all networks IP payload compression
QoS #1
QoS#2
NSAPI 2
IP#1
NSAPI 1
IP#2 (max 5)
NSAPI 2
APN #1 NSAPI 1
APN #2 NSAPI 2
SNDCP
SNDCP
SNDCP
SNDCP
MS
GGSN
MS
GGSN
Protocol Description user plane continued LLC Logical Link Control sequence control (even if the cell has been changed) error detection error correction by retransmission (acknowledgements between MS & SGSN) ciphering A5/3 GEA option, not implemented in all networks MS identity TLLI (Temporary Logical Link Identifier) in 99,99% contains P-TMSI RLC Radio Link Control positive/negative acknowledgement for the received data (acknowledgements between MS & BSC) retransmissions measurement reporting quality of the connection dynamic power regulation and Coding Scheme selection MAC Medium Access Control controls access to common resources (1 PDCH many users) TFI, USF allocation BSSGP (BSS GPRS Protocol) transfer of LLC frames passed between an SGSN and an MS with radio related information negotiation of QoS profile (SGSN BSS) cell information for SGSN (BVCI) node management (flush) mobility management (paging) NS (Network Service) provides communication paths between remote NS user entities load sharing between links (frame relay PVCs) link establishment detection if other links is down
Gb interface definition [OH] Fig. 4-4. Page 50: Frame Relay connection between the SGSN and PCUv
1. Network Service Entity Identifier NSEI Uniquely identifies each BSC/PCU (as a collection of NSVCs) to the SGSN (and vice versa). PCU may be connected to one SGSN only. PCU can be connected to a SGSN via an intermediate transmission network (Frame Relay) or via point-to-point connection. PCU can use one or more physical links to connect to a SGSN. NSEI definition RRNEI: NSEI=1;
2. Data Link Connection Identifier DLCI Identifies local connection in Frame Relay network. Defined between two FR nodes. 3. Network Service Virtual Connection Identifier NSVCI Identifies virtual connection between SGSN and BSC/PCU. DLCI and NSVCI definition RRNSI: NSVCI=1, DLCI=100, DEV=RTGLT-2, NUMDEV=5; RRVBE: NSVCI=1; Definition of NSVCI and DLCI NSVCI # unique in BSC/PCU DLCI # unique in BSC/PCU First RTGLT device Total # of consecutive RTGLT devices. After the definition, the NSVCI must be deblocked GS DEV=RTGPHDV-0&&-31
012 4
DEV=RTGLT-0&&-31 SNT=ETRTG-0
012 67
31
ETC
31
RPP
allocated automatically by the system
NUMDEV=5 DEV=RTGLT-2
4. BSSGP Virtual Connection Identifier BVCI Identifies a virtual connection between the SGSN and a cell in BSS. Allocated immediately after activation of GPRS in the cell. RLGSI: CELL=C1AG11; GPRS functionality activation Cell specification
3 NSVCI=1 2 DLCI=106
1 CELL 1 4 BVCI=1
NSEI=2
3 NSVCI=2 FR switch DLCI=101
CELL 2
4 BVCI=2
BSC
PCU
2 DLCI=100
SGSN
CELL 3
4 BVCI=3 1
3 NSVCI=3 2 DLCI=103
3 NSVCI=4
Ethernet working
Ethernet
GS
BVCI
SGSN
BVCI
GS
SGSN
RPP#1
RPP#1
BVCI
RPP#2
RPP#2
BVCI
RPP#3
Marked as blocked
RPP#3
Marked as deblocked
RP deblocking GS
BVCI
RP blocking/restart SGSN
BVCI
GS
SGSN
RPP#1
RPP#1
BVCI
RPP#2
BVCI
RPP#2
RPP#3
BVCI After deblocking of RPP3 Calculated Number of BVCs per RP = 2
BVCI
RPP#3
RPP#1
NEW BVCI
RPP#1
BVCI
RPP#2
BVCI
RPP#2
RPP#3
BVCI To which RPP allocate this cell?
RPP#3
BVCI Move the cell to RP with sufficient GSL resources
BSC
BSC
BSC
BSC
BSC
MSC
BSC
SGSN
SGSN BSC
SGSN
BSC
BSC
BSC
BSC
LA UPDATE
- 19 -
BSC
BSC
BSC
BSC
BSC
BSC
BSC
BSC
No LA UPDATE
No RA UPDATE
- 20 -
GEOGRAPHICAL STRUCTURE
NO POOL Network utilization is geographically dependent. Problem with dimensioning. POOL Easy dimensioning. Average traffic distribution over the Whole geographical area.
BSC
BSC
BSC
BSC
LONDON BUSINESS
BSC SGSN SGSN
LONDON SOHO
SGSN BSC SGSN BSC SGSN SGSN SGSN BSC MSC BSC BSC BSC
BSC
BSC
Addition of MSC requires redesigning of radio network. MSC failure/upgrage causes loss of service area.
To add MSC, data transcript from existing one may be used. MSC failure/upgrage only causes problem with capacity.
- 21 -
MSC/ 25%~CAP SGSN NRI Network Resource Identifier MSC/ 25%~CAP SGSN NRI
2
BSC
CAP =10
IMSI 2
MSC/ SGSN
RA/LA UPDATE 1 TMSI/P-TMSI RA/LA UPDATE NRI UPON OLD NRI
50%~CAP NRI
BSC
BSC
Additional resources must be added to provide the same GoS No such problem with SGSN because SGSN in POOL requires Gb over IP Solution A over IP
- 22 -
0 B,C
1 D D
If no GSM traffic more PDCHs are allocated higher GPRS throughput. It is possible to specify priorities, e.g. GSM can preempt all GPRS channels on congestion or take only Idle ones. If On Demand PDCH becomes idle it is returned to CS domain after PILTIMER ( Packet Idle List Timer) expiry.
TBF (Temporary Block Flow) transmission of data (radio blocks) over GPRS air interface signaling and traffic TBF TBF (new) released if idle (classic approach) TBF 5s release after 5 s (in practice) transmission over one or more TSs
TBF is unidirectional (independent control of UL and DL radio resources) 1MS 1 UL ( ) TBF 1MS 1 DL ( ) TBF 1MS 1 UL ( ) TBF + 1 DL ( ) TBF
DL
0 1 2 3 4 5 6 7
UL
0 1 2 3 4 5 6 7
DL Transfer TFI (Temporary Flow Identity) TBF ID (VALUES 0-31) MSs listen to all PDCHs allocated to them. Moreover they read all radio blocks. However, only radio blocks allocated to them (proper TFI) are processed. Without QoS resources are divided evenly among all MSs. (MSs
TFI=1
DL
0 1 2 3 4 5 6 7
and
TFI=3 TS=3&4
TFI=1 TS=4&5
TFI=7 TS=6&7
UL Transfer USF (Uplink State/Status Flag) (VALUES 0-7) transmitted downlink designates the MS that is allowed to transmit in UL direction on the particular TS
DL
0 1 2 3
USF=1 4
USF=1 5
USF=4 6
USF=5 7
UL
0 1 2 3 2 4 5 6 7
[Hint] Parameter TBF Granularity enables transmission of more UL Radio Blocks upon reception of proper TFI (TBF Granularity =4 4 Radio Blocks may be transmitted)
Logical Channels GSM FCCH SCH BCCH CCCH: PCH RACH AGCH DCH: SDCCH FACCH SACCH PACCH PTCCH TCH PDTCH Option which requires Master PDCH. (GPRSNWMODE parameter) MPDCH - first of dedicated PDCH, carry DATA + SIGNALING (80-90%) (10-20%) GPRS
0 B,C
1 D D
5 M
PBCCH
[OH] Fig. 5-2. Page 76: Logical channels in GSM [OH] Fig. 5-3. Page 76: Logical channels in GPRS
[OH] ------. ------: Cell without MPDCH [OH] ------. ------: Cell with MPDCH
Presence of MPDCH depends on Network Operation Mode
PCH
CS PAGING PS PAGING
PPCH MS LISTENS TO PCH AND PPCH -NO PAGING COORDINATION WITH DATA TRANSFER
GSM and GPRS channel allocation must be coordinated. (GPRS channel administration is responsible for this).
BSC
NO Gs
MS must support DTM. However, paging coordination works for all MSs (session must be suspended)
SGSN
MSC
RA UPDATE TUNNELED
BSC
SGSN
Allocation of FPDCH RLGSC: CELL=KISTA, FPDCH/SPDCH=3, MPDCH=YES/NO; RLCLC: Changing of GPRS cell parameters Cell name Number of Fixed/Semi-dedicated PDCHs (max 16) Allocation of MPDCH in the cell No selection preference. No selection preference for CS and select TCHs first for PS. No selection preference for CS and select TCHs last for PS.
Setting the Network Operation Mode RAEPC: Changing exchange properties (many different properties are changed with this command) PROP=GPRSNWMODE1; Choosing appropriate NOM
Selection of dedicated coding scheme for the particular cell RLGSC: CELL=KISTA, NA CS1 CS2, CS3 CS4 Cell name
CHCSDL=
CS downlink for the particular cell. If NA is selected, the exchange property CHCODING is used
LA = ON/OFF;
Activation of Link Adaptation feature. CS specified by CHCSDL will be taken as initial value.
Definition of required number of PDCH RLBDC: CELL=KISTA, CHGR=0-15, NUMREQBPC=8-128, NUMREQCS3CS4BPC=0-128 NUMREQEGPRSBPC=0-128, TN7BCCH=GPRS/EGPRS; Changing configuration of BPDCH Cell name Channel Group number Number of required BPCs, if not given all TSs are GPRS capable Number of required GPRS CS-3 or CS-4 BPCs Number of required EGPRS BPCs This parameter indicates if Timeslot Number (TN) 7 on the BCCH frequency can be configured with Traffic Channels (TCHs) supporting EGPRS or GPRS only.
Activation of Dual Transfer Mode in the cell RLDUI: CELL=KISTA, Changing configuration of BPDCH Cell name
Throughput
CS4 CS3
BSC
CS2 CS1
C/I
GSM
50%/50% 50%/50% CS4 20K
GPRS
CS3 14.4K CS2 12K CS1 8K
RBS
C/I
distance
distance
RAEPC: PROP=TBFDLLIMIT2; PROP=TBFULLIMIT2; PROP=PILTIMER20; Desired max # of DL TBFs sharing one PDCH. Value range is 1 8 Desired max # of UL TBFs sharing one PDCH. Value range is 1 6 PILTIMER value. Protection of PDCHs from returning to CS domain
Specification which on-demand PDCHs that are possible to pre-empt to be used for circuit switched calls. RLGSC: CELL=KISTA, 0 All on-demand PDCHs are possible to preempt 1 On-demand PDCHs not used for Dual Transfer Mode (DTM) are possible to preempt 2 On-demand PDCHs not used for Streaming are possible to preempt 3 On-demand PDCHs not used for DTM nor for Streaming are possible 4 ; On-demand PDCHs that are not essential are possible to preempt 5 On-demand PDCHs that are not essential nor DTM PDCHs are 6 On-demand PDCHs that are not essential nor Streaming PDCHs 7 On-demand PDCHs that are not essential nor DTM nor Streaming 8 Idle on-demand PDCHs are possible to preempt
PDCHPREEMPT=
[OH] Fig. 5-17. Page 90: Location Area (LA) and Routing Area (RA)
LA#2 RA#4
Location update
LA#3
RA#3 RA#5
LA Location Area
RA Routing Area
GMSK
Gaussian Minimum Shift Keyiing
8-PSK
8 - Phase Shift Keyiing
0/Different bit
1,1,0
SS
SS
[Q] Why transmission power in EDGE is lower, comparing with GMSK ? PPEAK GMSK PAV GMSK = > ~3dB PPEAK EDGE PAV EDGE MS measures average power.
GPRS GMSK
Solution no 8PSK on BCCH carrier or no 8PSK on TS 0 & 7 of BCCH carrier GMSK vs 8PSK
TX interference interference RX TX RX
large distance
small distance
Lower bitrate. High resistance to interferences thanks to large distances between symbols.
High bitrate. Lower resistance to interferences (symbols are close). Solution good radio, dynamic adaptation of coding and modulation (back to GMSK)
[OH] Fig. 6-5. Page 105: Coding Schemes for GPRS and EDGE (standard improvement) [Q] What is coverage area for GPRS ?
Coverage Area for GPRS bitrate achieved from 1 TS is at least 8 kb/s
GPRS
8PSK
GMSK
[Q] Why coverage for EGPRS with GMSK is greater than GPRS with GMSK ?
~3dB Processing Gain. Result of better coding schemes and more efficient protocols.
Improvements in EDGE [OH] Fig. 6-6. Page 106: Retransmission in EGDE in comparison to GPRS
In GPRS retransmission is allowed only with the same coding scheme. coding user data #1 NOT ACK #2 #3
#1 ACK, #3 ACK, #2 NOT ACK
#1 sequential number CS 4
#2
MCS 9
#1 MCS 6 #2 NOT ACK NOT ACK #1.1 #1.2 #2.1 GPRS protocols do not allow splitting one block into smaller parts due to problems with numbering. No space In protocol header for 2.1 & 2.2. Transmission window 64 frames (stall if exceeded) #2.2 MCS3 (GMSK)
INCREMENTAL REDUNDANCY enables utilization of less robust codec (MCS 9) in radio conditions suitable for more robust codec (MCS 5)
[OH] HANDOUT: Incremental Redundancy [OH] HANDOUT: MCS-9 and MCS-5 - comparison [Q] Why to introduce Incremental Redundancy ?
C/I
1 transmission 2 transmissions
3 transmissions
Radio conditions are changing constantly. In some cases only one or two transmissions are sufficient for proper decoding of the transmitted signal with incremental redundancy. Throughput is increased. Incremental redundancy requires MS buffer for soft combining. If buffer is exceeded link adaptation is utilized.
[Hint] In GPRS 10% of the whole transmitted data are retransmissions (for good network) In EDGE 40% of the whole transmitted data are retransmissions (for good network)
Selection of Default Modulation and Coding Scheme (MCS) DL/UL RAEPC: PROP=LQCDEFAULTMCSDL5; Changing exchange properties Default MCS downlink. Values 1-9 ~ MCS1MCS9 (valid if LQCACT1 or 3, no EGPRS Link Quality Control DL) Default MCS upnlink. Values 1-9 ~ MCS1- MCS9 (valid if LQCACT2 or 3, no EGPRS Link Quality Control UL)
PROP=LQCDEFAULTMCSUL5;
Activation/Deactivation of EGPRS Link Quality Control (ELQC) RAEPC: PROP=LQCACT 0 1; 2 3 ELQC deactivated ELQC activated for DL TBFs only ELQC activated for UL TBFs only ELQC activated for DL and UL TBFs
Limiting the highest MCS than can be selected by the system in LQC procedures (UL/DL) RAEPC: PROP=LQCHIGHMCS9; Values 1-9 ~ MCS1- MCS9
Link Adaptation and Incremental Redundancy (LA/IR/BLER) activation RAEPC: PROP=LQCMODEDL/UL 0 1; 2 LA mode LA/IR mode LA/IR BLER mode