i-hspa
TRANSCRIPT
I-HSPA
Richard Shephard
12th May 2009
Objectives and Introduction
Objectives
• To provide an introduction to I-HSPA• Provide an explanation as to connectivity and
architecture.• Explain how the nodes will be Operationally
supported• Provide explanation how calls are managed• Present the trial network• Generate questions to enhance the delivery to
Operations.
Introduction to I-HPSA
• I-HSPA is a 3GPP release 7 technology from NSN that allows faster access to the Internet by bridging less elements in the network.
• It is being deployed by Three ROI to meet the needs of the National Broadband Scheme.
• It is an evolution technology moving towards LTE.
• I-HSPA is a fully mobile solution. I-HSPA supports three kinds of mobility: – Intra-system Hand-over within the I-HSPA– Inter-system Hand-over between the I-HSPA and a
traditional 2G/3GPP (WCDMA/HSDPA)– Inter-system Hand-over from I-HSPA to WLAN or to any
IP based access• The intra-system hand-over (HO) between I-HSPA BTSs is
fast enough to support VoIP. The target for intra system HO is less than 100ms.
• The goal for Inter-system Handover between I-HSPA and traditional 3GPP is to be same as normal RNC relocation in 3GPP.
Introduction to I-HPSA
PS optimized HSPA – I-HSPA
SGSN
WCDMA BTS RNC
Content &Connectivit
y
Internet+Intranets
MSC-S+MGW+NVS
Nokia I-HSPA plug-in unit(“Adapter”)
HSPA device
IMS:IM, Presence, PoCVideo sharingVoIP, IP Centrex
GGSN
Inter-access mobility between 3G and I-HSPA carriers
Physical Hardware – Release 1
• The I-HSPA Node is a Flexi BTS with an adaptor fitted.
• The I-HSPA Adaptor cannot support voice services.
• To enable voice services it is co-located with another Flexi-BTS
Physical Hardware
The I-HSPA Adapter uses forced air cooling based on fresh air intake from back to front. This allows it be installed either horizontally or vertically. The contents of the I-HSPA Adapter delivery also include an air-blocking plate, to be used if the I-HSPA Adapter is with the Flexi BTS 2U module casing.The I-HSPA Adapter features a lightweight aluminum alloy casing with stainless steel alloy used for the fan carrier.
Physical Hardware - Connectivity
Front panel identifier Purpose Interface type Connector Type
EIF1 (SFP TRS)
External transportOptical for Ethernet (reserved for future use)
SFP, SFP cage
EIF2 (TRS/LMT)
External transport/Local Management Terminal
10/100/1000 Base-T Ethernet RJ45 shielded
EIF3 (TRS) External transport 10/100/1000 Base-T Ethernet RJ45 shielded
EIF4 BTS interface 10/100/1000 Base-T Ethernet RJ45 shielded
DC IN 48VDC Power Input Multi-Beam XL RA 2 pin
Architecture
High Level Architecture
• At each site a new node B will be deployed to support I-HSPA.
• The site will have 2 transmission requirements, existing transmission will remain but with reduced capacity
I-HSPA High Level Architecture
Core Switching Layer
Ingress Routing Layer
C-SGSN
GOMS
Flexi-ISN
Ingress Switching Layer
Nortel PP7K/PP20K
I-HSPA Node B
R99 Node B
I-HSPA Node B
R99 Node B
R99 Node B
I-HSPA Node B
MSS
High Level Architecture
High Level Architecture
Transmission - ATMPP20K (Nortel MSS)
I-HSPAFlexi-BTSOdd NumberedHostname
I-HSPA AdapterDSP
OMU
PS UP IP Address
Sigtran P2P IP Address for CS CP, PS CP, Iur CP and GOMS
Iur P2P IP Address
Vp=2Vc=34
Vp =2
Vc Vp config as per existing
design
R99Flexi-BTS
R99 base station with existing Iub configuration, and designed ATM configuration
Vp=1
Vc=50
Vp=1
Vc=51
Existing V
p
RNC
Vc=50
Vc=34
Vc=51
I-HSPAFlexi-BTSOdd NumberedHostname
I-HSPA AdapterDSP
OMU
PS UP IP Address
Sigtran P2P IP Address for CS CP, PS CP, Iur CP and GOMS
Iur P2P IP Address
R99Flexi-BTS
R99 base station with existing Iub configuration, and designed ATM configuration
Existing V
p
Existing V
p
Gn2
Spare
Gn2
Gn1
Spare
GE Ports
DT VR
HS VR
DT VR
I-HSPA – ATM Layer
Gn1
I-HSPA
I-HSPA
Ingress Switching and Routing Layer
Transmission - ATM
• Where ATM is used s the transmission medium each I-HSPA Node shall be connected via a 4 E1 IMA group
• The co-located r99 node B shall be connected via a reduced 2 E1 IMA group.
• 4 E1 IMA groups shall be terminated from BT as channelised STM-1s on the PP20K.
• VCs shall be terminated on the HS VR in the PP20K.• Onward connectivity to the ingress switching and routing
layer shall be provided via 2 GE point to point IP connections.
Transmission - Ethernet
• Where Ethernet is used 10Mbps Ethernet connection shall be made available to the Node.
• Ethernet transmission is supplied by BT Ireland and comes in 2 steps.
• Ethernet over Private Line (EPL) – A psuedo wire solution providing point to point Ethernet connectivty. Some sites will be deployed using EPL.
• Etherflow – BT’s 21CN Metro-Ethernet solution. Etherflow will be available from September.
Transmission - Ethernet
Firewall Service
ModuleSwitch
BT THS
DC I-HSPA 2
DC I-HSPA 4
I-HSPA adapters can be daisy chained using Ceragon microwave to provide
VLAN tag per adaptor
Ceragon switches through VLAN tagged traffic from 1st I-HSPA
adapter and adds VLAN Tag for 2nd I-
HSPA adapter
.1Q - 1
.1Q - 2
.1Q - 3
.1Q – 4
.1Q - 2001
.1Q - 2002
.1Q - 1
.1Q - 1
IP Subnet:1.1.1.1/28 Gateway 1.1.1.14
VLAN TAG 1
IP Subnet:1.1.1.16/28 Gateway
1.1.1.30VLAN TAG 2
DC I-HSPA 3
IP Subnet:1.1.1.32/28 Gateway –
1.1.1.46VLAN TAG 3
1.1.1.14
1.1.1.30
1.1.1.46
1.1.1.63
DC I-HSPA 1
IP Subnet:1.1.1.48/28
Gateway 1.1.1.63VLAN TAG 4
MSC
SGSN
GGSN
GOMS
DCN VLAN
GN VLAN
B/bard SIGTRAN VLAN
AlcatelSwitch
BT Transmission
Layer 2 Layer 3
DCN IP Addr
Sigtran IP Addr
Gn IP Addr
EPL will pass all traffic without adding any QoS or tagging
BT Eth
erne
t ove
r
Privat
e Lin
e
Iur IP Addr
Iur has an IP address provided but will route all traffic to other I-HSPA adaptors
for mobility purposes.
I-HSPA Connectivity
Transmission – Ethernet/Access
• To provide Ethernet to the I-HSPA Node a system of Ethernet radio is being deployed from Ceragon.
• The solution is a feature rich microwave system which includes Qos, Adaptive rate, VLAN tagging (802.1q). Only VLAN tagging shall be used initially.
• The microwave radio will be used from the THS to the I-HSPA Node.
• BTs Metro Ethernet shall be used between THS and City West Data centre.
IP Connectivity
• The I-HSPA node is an IP based platform which uses the IP layer to enable communication between the I-HSPA Node and the control and user plane functions in the core network.
GOMS
7600 OSR - Tnd76r01
MSS - TN02M
CC
SU
117
2.3
0.10
.141
172
.30.
10.2
05
GOMS Server??
DCN Router
Gateway??
Corporate Access
Node gateway IP addresses
172.30.9.238
172.30.9.18
PS CP IP Address172.30.9.161
PS CP IP Address172.30.9.177
CS CP IP Address172.30.10.189
CS CP IP Address172.30.10.253
PS UP IP Address172.30.9.145
PS UP IP Address172.30.193.121
DCN/GOMS IP Address192.168.250.169
I-HSPA Trail – Switching and Routing Layers
Combi-SGSN TN0SGN04
172
.30.
9.16
2P
AP
U 0
172
.30.
9.17
8
172
.30.
9.16
3P
AP
U 1
172
.30.
9.17
9
172.
30.9
.130
IOC
P-E
A 0
172.
30.9
.146
172.
30.9
.131
IOC
P-E
A 1
172.
30.9
.147
TNDOSR01 PS UP VLAN 282
TNDOSR02 PS UP VLAN 283
TNDOSR01 PS CP VLAN 280
TNDOSR02 PS CP VLAN 281
TNDOSR01VLAN 207
TNDOSR02 VLAN 208
PP20K Gen_2001
172.30.9.17
Gn1 IP Address217.171.143.147
Gn2 IP Address217.171.143.177
TNDOSR01 Gn1 VLAN 205
TNDOSR02 Gn2 VLAN 206
DCN Switch VLAN
I-HSPAHTN001
Cat 5E
Cat 5E
Test Node B 1
Cat 5E
Cat 5E
I-HSPA HTN002
Cat 5E
Cat 5E
Test Node B 2
Cat 5E
Cat 5E
I-HSPAHTN003
Test Node B 3
Point to point link CC
SU
217
2.3
0.10
.142
172
.30.
10.2
06
Service Flows
• I-HSPA Node can only support signalling, SMS, and PS data. Voice services cannot be supported.
• If MOC/MTC call is required UE will be SRNS relocated to the co-located R99 node B for connectivity to the RNC. After call completes UE will be SRNS relocated back.
• Go to Signalling document
Operational Support
• In release 1 GOMS is used to manage the I-HSPA nodes for alarm and performance data.
• When OSS 5.1 is delivered GOMS will be fully integrated into NetAct.
• GOMS is a Linux platform that gathers data from the I-HSPA nodes and downloads radio plans to the I-HSPA nodes.
• GOMS provides a facility for fault management, configuration management, performance management, software management etc.
GOMS Launcher
Accessed through NetAct
• The NEMS team are producing a wall board based on a set of KPIs.
• Alarm data is only available by accessing GOMS. The possibility of integrating into NetAct has been explored - faults would appear to be on NetAct as opposed to the I-HSPA node.
• This can be worked around with development. The amount of effort required would mean that OSS 5.1 would probably be available before the development was completed.
Operational Support
Trial Network
I-HSPA Trial Network
• The trial consisted of 10 filed sites in and around Wicklow.
• 2 sites in the City West DC.• All transmission is E1 IMA groups.• Ingress routing layer is provided by Nokia IP740
– operational support provided by NSN unless handover to operations is performed.
• Trial network is kept alive on best effort basis and to provide a FOA environment.
Nortel PP7K
BT
TS I-HSPA WK0019
TS I-HSPA WK0009
TS I-HSPA WK0011
TS I-HSPA WK0012
TS I-HSPA WK0022
TS I-HSPA WK0028
TS I-HSPA WK0015
TS I-HSPA WK0016
TS I-HSPA WK0017
TS I-HSPA WK0027
Nortel PP20K
NSN IP 740
DN1SGN01 NSN C-SGSN
Dn1dl301
DN1OSR01 (VLAN 207)
NSN MSS CCSU GOMS 192.168.210.82
GW 192.168.210.126
DC I-HSPA 1
Ca
t 5
E
DC I-HSPA 2
Ca
t 5
E
MM
F
SM
F
Ca
t 5
E
In p
lace
Ca
t 5
E
Nortel PP20KDB_2001 Slot 12 port 15 DB_2002 slot 12 port 10
Ca
t 5
E
Ca
t 5
E
DN1OSR02 (VLAN 208)
Ca
t 5
E
NSN MSS CCSUIn
pla
ce
DN2OSR01
Ca
t 5
E
DN2OSR02
Ca
t 5
E
Ca
t 5
ES
2-S
2/P
21
72.
30
.19
3.1
14
/29
17
2.3
0.1
93
.98
/29
S1
4-S
2/P
21
72
.30
.19
3.1
22
/29
17
2.3
0.1
93
.10
6/2
9C
at
5E
Ca
t 5
E
Ca
t 5
E
Ca
t 5
E
Net Act
Test Node B 1
Ca
t 5
E
Test Node B 2
Ca
t 5
E
Ca
t 5
E
Ca
t 5
E
20
/21
18
/19
22
/23
/24
/25
27
/28
/29
/30
ATM-S1/P1 ATM-S3/P1
ETH3172.29.244.33
ETH-S2/P3172.29.246.33
ETH4192.168.210.80/25
GW 192.168.210.126
ETH1172.30.193.97
ETH-S2/P2172.30.193.105
ETH-S2/P1172.30.193.113
ETH2172.30.193.121
Test Node B1 and 2 have 4 E1s each. 2 E1s from Node B1 on ports 22 & 23 will be connected to the first I-HSPA Node B and the E1s
connected to ports 24 & 25 will be used for the second I-HSPA Node B
IP 740 card uses MMF – unknown if PP20K supports
MMF
Interface card to be fitted – card will be taken from DN1SGN03 Tunnelling
Unit 4 when link deactivated
I-HSPA Trail – Physical Layer
G4/25
G4/26
G1/11 G1/11G4/5 G4/6 G4/15
G4/16 G4/16
G4/5
DN2OSR01 DN2OSR02
Cat 5E
Ca
t 5
E
Ca
t 5
E Cat 5E
G3/33 G3/33G3/30G3/30
IOC
P-E
A1
17
2.3
0.1
93
.11
5/2
9
IOC
P-E
A2
17
2.3
0.1
93
.12
3/2
9
PA
PU
11
72
.30
.19
3.9
9
PA
PU
21
72
.30
.19
3.1
07
Service Map
4
5
6
Each I-HSPA Node deployed will be co-located with a release 99 Node B. The I-HSPA Node is unable to process voice traffic therefore voice calls are processed by the co-located r99 node B. The I-HSPA node can only support 3GPP release 5 and later devices that support HSPA, Release 4 and previous devices shall use the Release 99 node B.
1. Subscriber powers up device and registers on the network, I-HSPA node sends traffic either over Ethernet transmission or ATM transmission dependant upon what the local transmission network is. If device is pre 3GPP Release 5 it will register on the R99 node and register.
2. If transmission is ATM connectivity is passed through the Nortel Passports, this could be to PP7K or PP20K. If transmission is Ethernet connectivity is direct from BT to a layer 3 switch.
3. The Flexi ISN or GGSN will try and match the destination IP adders against its flow configuration and zero rate else it will match the catch all flow (0.0.0.0).
4. CS Location Update and PS Attach are implemented using SIGTRAN between the I-HSPA node and the MSS and SGSN respectively.
5. The I-HSPA Node is managed from a Management station called GOMS, while standalone in Release 1 in Release 2 and with OSS 5.1 this management station is an integral part of NetAct. GOMS provides performance data. Alarm data is available on GOMS.
6. PS user plane traffic is carried over the same transmission medium, and can be carried through the SGSN 9 2 tunnel) or direct to the GGSN (direct tunnel).
7. If voice services are required the UE is forced on to the r99 node as the I-HSPA node dopes not support voice services. When the voice service has finished the subscriber will be handed back to the I-HSPA node.
8. If the UE is pre release 5 then the packet service shall be carried over the r99 node.
I-HSPA Service Map
Juniper OSR
1
2
IMSS
CSC Ops
MPC Ops
IP Ops
I-HSPA Node B
RAN Ops
Note: This is a service layer diagram – some devices within some operational areas have been omitted to aid clarity
2
1
Transmission Ops
Nortel PP7K Nortel PP20K
R99 Node B
RAN Ops
RNC
6500 OSRs
MGW
GOMS
SiSi
DCN Switch
Packet Data Networks (PDN eg Internet
BT Transmission
ROI Field Ops - BT
4
SGSN Flexi-ISN
6
6
6
7
7
Glossary
• I-HSPA – Internet- High Speed Packet Access• LTE – Long term Evolution• WCDMA – Wide band CDMA• C-SGSN – Combi- Serving GPRS Support Node• MSS – Mobile Switching Server• GOMS – G Operations and maintenance System• SRNS – Serving Radio Network Re-selection• CCSU – Call Control Signalling unit• PAPU – Packet Processing Unit• IOCP-EA• GGSN – Gateway GPRS Support Node• MGW – Media gateway• EPL – Ethernet over Private Line