APG43_InternalWorkshop_CSI .ppt

wafawafa52 28 views 39 slides Jun 24, 2024
Slide 1
Slide 1 of 39
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26
Slide 27
27
Slide 28
28
Slide 29
29
Slide 30
30
Slide 31
31
Slide 32
32
Slide 33
33
Slide 34
34
Slide 35
35
Slide 36
36
Slide 37
37
Slide 38
38
Slide 39
39

About This Presentation

APG43_InternalWorkshop_CSI


Slide Content

Copyright © 2006 AT&T. All rights Reserved.
Ericsson 3G SGSN Architecture
Functional Unit Descriptions
MKIV Hardware
MKVI Hardware
Cabling Description
Physical Interface Design
AT&T Configuration of 3G SGSN
Iu/IP Architecture
SGSN Pool Architecture
SGSN Numbers Network Wide

SGSN Functional Description
The Serving GPRS Support Node (SGSN) handles data
subscriber mobility management and transfers user data
packets between the User Equipment (UE) and GPRS or
UMTS packet core network. In addition, it authenticates
the subscriber and the mobile terminal. The SGSN also
generates charging data and transfers it to the Charging
Gateway (CG) for billing purposes.
The SGSN supports primary interfaces for the following
equipment in the AT&T network: BSC (Gb) or RNC (Iu -
PS), HLR (Gr), GGSN & DNS (Gn), CGF (Ga), OSS (OAM)
and LiG (Li).
Copyright © 2006 AT&T. All rights Reserved.Page 2

SGSN Centric Topology Diagram
Copyright © 2006 AT&T. All rights Reserved.Page 3

Functional Board Descriptions
Copyright © 2006 AT&T. All rights Reserved.Page 4
Board Type Purpose
IP Router PIUSupport only IP-based Interfaces (Gn/Gb, Iu-U,Gb over IP, SS7 over IP)
FR PIU Support only Frame Relay-based Interfaces (Gb over Frame Relay)
SS7 FE NB PIUSupport only narrowband SS7-based interfaces
SS7 FE BB PIUSupport only broadband SS7-based interfaces
GPB
The General Processing Board (GPB) acts as an AP or an NCB, and is applicable to the MKIV
hardware platform only.
IBxx
The Interface Board version 3 (IBxxv3) PIUs can act as DPs handling payload processing, or
handle IP routing or SS7 signaling. The IBxxv4 PIUs can, apart from the IBxxv3 roles, also act
as APs.
-IBAS Interface Board for ATM Single-mode fiber
-IBTE Interface Board for E1/T1
-IBS7 Interface Board for SS7
-IBEN Interface Board for Ethernet
FSB
The File Server Board (FSB) acts as a File and Boot Server. In the SGSN, one FSB serves as the
master FSB. A second FSB serves as a standby FSB mirroring all stored data. If the master FSB
fails or needs replacement, the spare FSB takes over operation.
PEB
The PEB supplies the magazine with power, which is distributed from power connectors on
the PEB front panel, through the backplane, to all slots. The PEB supplies the backplane
communication with a dual star Ethernet network. The front panel has three ports that are
used for magazine interconnection.

Ericsson Rack Specifics
Copyright © 2006 AT&T. All rights Reserved.Page 5Ericsson SGSN MKIV or MKVI
Hardware components
1 - Magazines
a Magazine 1
b Magazine 2
c Magazine 3 (optional)
2 – Plug In Units (PIUs)
3 - Backplane

Ericsson SGSN MKIV WCDMA Hardware
Copyright © 2006 AT&T. All rights Reserved.Page 6
MKIV WCDMA
SS7 (Narrowband/Broadband SIGTRAN)
NB -x2 or
BB –x2
Iu-PS (Iu-U & Iu-C)
ATM –x2 User Plane/ x2 Control Plane or
IP –x2 User Plane/ x2 Control Plane
Gn GigE x2
OAM/Gom x2
Console x2
GSS x1
SGSN (W) MkIV 1000

Ericsson SGSN MKIV GSM Hardware
Copyright © 2006 AT&T. All rights Reserved.Page 7
MKIV GSM
SS7 (Narrowband/Broadband SIGTRAN)
NB -x2 or
BB –x2
Gb (Frame Relay / IP)
FR –x2 per BSC or
IP –x2 User Plane/ x2 Control Plane
Gn GigE x2
OAM/Gom x2
Console x2
GSS x1
SGSN (G) MkIV 1000

Ericsson SGSN MKVI DA Hardware
Copyright © 2006 AT&T. All rights Reserved.Page 8
MKIV DA / WCDMA Connectivity
SS7 (Narrowband/Broadband SIGTRAN)
NB -x2 or
BB –x2
Iu-PS (Iu-U & Iu-C)
ATM –x2 User Plane/ x2 Control Plane or
IP –x2 User Plane/ x2 Control Plane
Gn GigE x2
OAM/Gom x2
Console x4
GSS x2
SGSN (WG) MkVI 1500/4

Cabling Description
Copyright © 2006 AT&T. All rights Reserved.Page 9

Physical Interface Design
Copyright © 2006 AT&T. All rights Reserved.Page 10OSPF Area
Global Control
Application
Iu-U
Router1
Iu-U
Router2
Iu-U Internal
connection
SS7 Broadband
front-end interface
SS7 Back-End
Application
SCTP Front End
Point
Iu-C
Networks
Gom
Router 2
Gom
Router 1
Back Plane
Connection
Gr/Gd/Ge
Networks
Gn Router1
(GigE)
Gn Router2
(GigE)
ATM
PVC
SS7 Hardware
Magazine 1
( Slots 2 - 5 )
ATM PVC
IBENv4
Magazine 1
( Slots 19 - 20)
IBTEv4
Magazine 2
IBASv4
Magazine 2
( Slots 11 - 12 )
IBASv4
Mag 1 slot 6, 7
Magazine 2
Magazine 1
ATM
PVC
Gom Internal
Connection
Primary
Secondary
Primary
Node B Node BNode B
. . . . .
Node B
IBASv4
Magazine 2
( Slots 14 - 15 )
Primary
Secondary
Yao Kuang Lai
by Yao Kuang Lai
Control
Application Control
Application
Yao Kuang Lai
By Yao Kuang Lai
User
Application
GSS
FSBv4
Magazine 1
( Slots 17 – 18 )
A B C D E F G H
SELECTED
ON-LINE
BackPlane Ethernet 1
Node B
RNCs
. . . .
Terminal Server
LI/GTP Prime Source
Address in Gom Networks
Cingular Gn
Routers
AT&T Gom
Routers
Port 19
Port 20
Name
WTC1ERCUS08
UMTS SGSN
SGSN Logical Network
SIZE Date : DWG NO rev
May 20, 2008 Logical Diagram PA2
1 OF 1
SS7
Router 2
SS7
Router 1
10.250.255.37 /29 10.251.255.37 /29
SIGNET
Routers
Magazine 3
IBENv4
Magazine 3
IBTEv4
Magazine 3
AT&T Redmond Lab
WCDMA SGSN
WTC1ERCUS08
R8 MKVI
STP1
SPC: 229-210-0
10.224.241.18
STP2
SPC: 229-211-0
10.225.240.130
Alias
SPC: 229-203-0
GigE switch
IBASv4
Mag 1 slot 6 - 7
IBENv4
Magazine 2
IBENv4
Magazine 1
IBASv4
Magazine 3
( Slots 11 - 12 )
FSBv4
Magazine 1
( Slots 17 - 18)
ANCBPNCB
Port 19
Port 20
4.38.11.254
O&M
155.165.207.1 /32
Gom Network
155.165.206.0 /27
Gom OSPF
Area 0.0.2.154.231.230
Gom Service IP
155.165.207.1 /32
Reserved Gn VIP
155.165.17.1 /32
Gn GTP-U
155.165.17.1 /32
Gn OSPF
Area 0.0.0.254.10 .11
Gn Networks
(172.24.4.0/27)
10.251.255.33
10.250.255.33
10.250.255.34 /29
10.251.255.34/29
Back Plane Network
(169.254.0.0/17)
Sigtran
Secondary
PEBv3
Magazine 2
( Slots 1 )
PEBv3
Magazine 1
( Slots 1 )
BackPlane Ethernet 1
BackPlane Ethernet 1
PEBv3
Magazine 3
( Slots 1 )
BackPlane Ethernet 1
PEBv3
Magazine 1
( Slots 21)
PEBv3
Magazine 2
( Slots 21)
BackPlane Ethernet 2
BackPlane Ethernet 2
BackPlane Ethernet 2
PEBv3
Magazine 3
( Slots 21)
Gn Internal
ConnectionSGSN SS7
SPC 229-98-184
Iu Service IP
172.26.240.1 /32
155.165.195.237 /24
1
st
FSB2
nd
FSB

AT&T Configuration of 3G SGSN
Copyright © 2006 AT&T. All rights Reserved.Page 11
The AT&T configuration of the Ericsson 3G SGSN is governed
by two sets of complimentary standards.
•Gold Standards
•Covers configuration that is Global in nature
•Overseen by the Gold Standards Governance Board
•Standards available in the Gold Standards Library:
https://operations.web.att.com/sites/GoldStandard/Data%20Sha
ring/GS_Library.aspx?PageView=Shared
•Site Specific CIQs
•Covers configuration that is local in nature
•Maintained and published by the local Engineering groups

Iu/IP Architecture
Copyright © 2006 AT&T. All rights Reserved.Page 12

Logical Diagram IuPS/IP
Copyright © 2006 AT&T. All rights Reserved.Page 13

Iu/IP and Pooling
Copyright © 2006 AT&T. All rights Reserved.Page 14

Logical Diagram Gb/IP
Copyright © 2006 AT&T. All rights Reserved.Page 15REMOTE BSC LOCATION
SGSN / COLO BSC LOCATION
Gb
Gb
BSC
BSC
BSC
BSC
BSC
BSC
BSC
SGSN SGSN
IP/MPLS NetworkSiSi SiSi SiSi SiSi
802.1Q
Trunk
PE
Routers’s
Remote BSC 6500/7600
both a layer2 switch and
L3 router. WAN links
will terminate on closest
PE routers within GB
VPN. OSPF is used to
exchange routing
information between
remote BSC and PE
locations.
Each pair of BSC Extreme switches will reside in its own subnet/VLAN. The
Extreme switches will provide a layer3 interface creating a L2 demarc. The
Extreme switches will run HSRP requiring L2 connectivity from the Cingular
provided switches. The Extreme VLAN’s are trunked back to the Juniper routers
which provide a highly available L3 gateway using VRRP. Static routes are used
on the Extreme switches and within the GB routing-instance for routing
information. Static routes are redistributed into GB OSPF process.
GB and GN routing-instances
will be created on the PE
routers to separate GB and
GN. OSPF adjacencies will
be established between
SGSN’s and PE routers.
Aggregate routes are used to
control route export of OSPF
learned routes.
Black lines represent GN routing-
instance/VLAN/Subnets. This by
definition is a separate OSPF
routing process. Green lines
represent GB routing-instance/
VLAN/subnets.
GN
GB

Copyright © 2006 AT&T. All rights Reserved.Page 16
Gb/IP Lab Diagram
Copyright © 2006 AT&T. All rights Reserved.Page 16

Ericsson SGSN Counts
Copyright © 2006 AT&T. All rights Reserved.Page 17YE2008 CentralNE SE West
Ericsson 2G 37 0 10 21
Total 2G YE 2008 37 0 10 21Company Total 68
YE2009 CentralNE SE West
Ericsson 2G 34 0 11 23
Total 2G YE 2009 34 0 11 23Company Total 68
YE2010 CentralNE SE West
Ericsson 2G 34 4 11 23
Total 2G YE 2010 34 4 11 23Company Total 72
YE2008 CentralNE SE West
Ericsson 3G MkIV 5 3 7 8
Ericsson 3G MkVI 3 0 0 0
Total 3G YE 2008 8 3 7 8Company Total 26
YE2009 CentralNE SE West
Ericsson 3G MkIV 5 3 9 11
Ericsson 3G MkVI 15 1 6 7
Total 3G YE 2009 20 4 15 18Company Total 57
YE2010 CentralNE SE West
Ericsson 3G MkIV 0 0 2 7
Ericsson 3G MkVI 30 9 21 19
Total 3G YE 2010 30 9 23 26Company Total 88
Total 2G & 3G SGSNs YE 2008 45 3 17 29Company Total 94
Total 2G & 3G SGSNs YE 2009 54 4 26 41Company Total 125
Total 2G & 3G SGSNs YE 2010 64 13 34 49Company Total 160
YE2010 Ericsson 3G SGSN
w/Ericsson RAN 21 9 23 24
Total
Ericsson/Ericsson77
YE2010 Ericsson 3G SGSN
w/ALU RAN 9 0 0 2
Total
Ericsson/ALU 11
2G SGSN Counts
3G SGSN Counts
Grand Totals

Copyright © 2006 AT&T. All rights Reserved.
Ericsson SGSN Performance and
Capacity
SGSN Capacity
Capacity Measurements & Counters
Performance of Ericsson 3G SGSN

SGSN Capacity
Copyright © 2006 AT&T. All rights Reserved.Page 19
Product Package SGSN MKIV (G)
Gb Transport Type Throughput @ 300 bytes/packet
Throughput @ 1450 bytes/packet SAU PDP Contexts
MkIV 650/xx (2 Magazine) Gb over Frame Relay 42 kpps (100 Mbps)
11 kpps (130 Mbps) 650,000 780,000
Gb over IP 54 kpps (130 Mbps)
19 kpps (220 Mbps) 650,000 780,000
MkIV 1000/xx (3 Magazine) Gb over Frame Relay 83 kpps (200 Mbps)
30 kpps (350 Mbps) 1,000,000 1,200,000
Gb over IP 117 kpps (280 Mbps)
43 kpps (500 Mbps) 1,000,000 1,200,000
Product Package SGSN MKIV (W) Iu/Gn Transport Type Throughput @ 300 bytes/packet
Throughput @ 1450 bytes/packet SAU PDP Contexts
MkIV 650/xx (2 Magazine) Iu and Gn over ATM or Ethernet200 kpps (500 Mbps)
86 kpps (1024 Mbps) 650,000 780,000
MkIV 1000/xx (3 magazine) Iu and Gn over ATM 310 kpps (750 Mbps)
(1)
84 kpps (1024 Mbps) 1,000,000 1,200,000
Iu and Gn over Ethernet 625 kpps (1536 Mbps)
345 kpps (4096 Mbps) 1,000,000 1,200,000
Iu over ATM and Gn over Ethernet420 kpps (1024 Mbps)
(2)
200 kpps (2457.6 Mbps) 1,000,000 1,200,000
(1) The throughput figure for WCDMA payload applies for SGSNs using IBASv3b PIUs. When using IBASv3 the throughput figure is 200kpps (480 Mbps).
(2) The throughput figure for WCDMA payload applies for SGSNs using IBASv3b PIUs and having Gn and Iu collocated on all routers except Gom routers.
Product Package SGSN MKVI (W) Iu/Gn Transport Type Throughput @ 300 bytes/packet
Throughput @ 1450 bytes/packet SAU PDP Contexts
MkVI 1500/xx Iu over ATM 417 kpps (1.0 Gbps)
86 kpps (1.0 Gbps) 1,500,000 2,250,000 (W)
Iu over Ethernet 1050 kpps (2.5 Gbps)
530 kpps (6.0 Gbps) 1,500,000 2,250,000 (W)
MkVI 2000/xx Iu over Ethernet 625 kpps (1.5 Gbps)
345 kpps (4.0 Gbps) 2,000,000 3,000,000 (W)

Capacity Measurements & Counters
Copyright © 2006 AT&T. All rights Reserved.Page 20CPU
TechnologyAvailableUsed% UtilizedAvailableUsed% UtilizedAvailableUsed% Utilized% UtilizedLink Type# of LinksAverage % Utilized
3G (MkVI) 950000 303815 32% 1200000 160978 13% 1000 403.73 40% 37% IP 1 11%
3G (MkVI) 950000 236910 25% 1200000 125727 10% 1000 291.01 29% 28% IP 1 6%
3G (MkVI) 950000 254909 27% 1200000 151279 13% 1000 323.18 32% 41% LSL 16 29%
3G (MkVI) 950000 426017 45% 1200000 199309 17% 1000 584.12 58% 50% IP 1 14%
3G (MkIV) 700000 260269 37% 1200000 121875 10% 1500 307.51 21% 65% IP 1 5%
3G (MkIV) 700000 257741 37% 1200000 120146 10% 1500 303.33 20% 62% IP 1 5%
3G (MkIV) 700000 259645 37% 1200000 121548 10% 1500 311.59 21% 62% IP 1 5%
3G (MkIV) 700000 257686 37% 1200000 120689 10% 1500 304.05 20% 63% IP 1 5%
3G (MkIV) 700000 258294 37% 1200000 121158 10% 1500 305.42 20% 65% IP 1 5%
3G (MkVI) 950000 387390 41% 1200000 181038 15% 1500 466.76 31% 40% IP 1 8%
3G (MkVI) 950000 388600 41% 1200000 181759 15% 1500 464.88 31% 40% IP 1 8%
2G 650000 225511 35% 780000 75976 10% 200 31.89 16% 51% LSL 16 13%
2G 650000 118278 18% 780000 29376 4% 200 11.38 6% 29% LSL 16 11%
2G 650000 175826 27% 780000 40161 5% 200 18.46 9% 40% LSL 16 15%
2G 650000 141525 22% 780000 42245 5% 200 21.84 11% 38% LSL 16 10%
Attachment PDP Throughput (Mbps) SS7

Sample Performance Data for an Ericsson 3G SGSN
Copyright © 2006 AT&T. All rights Reserved.Page 21
0
50000
100000
150000
200000
250000
4/12/2010 3:00 4/12/2010 4:00 4/12/2010 5:00 4/12/2010 6:00 4/12/2010 7:00 4/12/2010 8:00 4/12/2010 9:00
4/12/2010 10:00 4/12/2010 11:00 4/12/2010 12:00 4/12/2010 13:00 4/12/2010 14:00 4/12/2010 15:00 4/12/2010 16:00 4/12/2010 17:00 4/12/2010 18:00 4/12/2010 19:00 4/12/2010 20:00 4/12/2010 21:00 4/12/2010 22:00 4/12/2010 23:00
4/13/2010 0:00 4/13/2010 1:00 4/13/2010 2:00 4/13/2010 3:00 4/13/2010 4:00 4/13/2010 5:00 4/13/2010 6:00 4/13/2010 7:00 4/13/2010 8:00 4/13/2010 9:00
4/13/2010 10:00 4/13/2010 11:00 4/13/2010 12:00 4/13/2010 13:00 4/13/2010 14:00 4/13/2010 15:00 4/13/2010 16:00 4/13/2010 17:00 4/13/2010 18:00 4/13/2010 19:00 4/13/2010 20:00 4/13/2010 21:00 4/13/2010 22:00 4/13/2010 23:00
4/14/2010 0:00 4/14/2010 1:00
SAU W
68000
70000
72000
74000
76000
78000
80000
82000
84000
86000
88000
90000
4/12/2010 3:00 4/12/2010 4:00 4/12/2010 5:00 4/12/2010 6:00 4/12/2010 7:00 4/12/2010 8:00 4/12/2010 9:00
4/12/2010 10:00 4/12/2010 11:00 4/12/2010 12:00 4/12/2010 13:00 4/12/2010 14:00 4/12/2010 15:00 4/12/2010 16:00 4/12/2010 17:00 4/12/2010 18:00 4/12/2010 19:00 4/12/2010 20:00 4/12/2010 21:00 4/12/2010 22:00 4/12/2010 23:00
4/13/2010 0:00 4/13/2010 1:00 4/13/2010 2:00 4/13/2010 3:00 4/13/2010 4:00 4/13/2010 5:00 4/13/2010 6:00 4/13/2010 7:00 4/13/2010 8:00 4/13/2010 9:00
4/13/2010 10:00 4/13/2010 11:00 4/13/2010 12:00 4/13/2010 13:00 4/13/2010 14:00 4/13/2010 15:00 4/13/2010 16:00 4/13/2010 17:00 4/13/2010 18:00 4/13/2010 19:00 4/13/2010 20:00 4/13/2010 21:00 4/13/2010 22:00 4/13/2010 23:00
4/14/2010 0:00 4/14/2010 1:00
NbrActivePdpPerSgsn W
0.00
5.00
10.00
15.00
20.00
25.00
30.00
35.00
40.00
45.00
Busy Hour CPU Load(Average)
CPU Load
Attached Subscribers
Active PDP Sessions

Copyright © 2006 AT&T. All rights Reserved.Page 22
0
100000
200000
300000
400000
500000
600000
succGprsAttachUmts
0
500000
1000000
1500000
2000000
2500000
3000000
3500000
succInterSgsnRaUpdateUmts
Inter RAU Success Rate
0
1000000
2000000
3000000
4000000
5000000
6000000
succIntraSgsnRaUpdateUmts
0
500000
1000000
1500000
2000000
2500000
SM.SuccActPdpContext.U
Sample Performance Data for an Ericsson 3G SGSN -
Continued
Intra RAU Success Rate Attach Success Rate
PDP Activation Success Rate

Copyright © 2006 AT&T. All rights Reserved.
Ericsson SGSN Lab Testing
SGSN/MME Development Process
Lab Certification
FFA Process
Fault Management Process
Lab Lineups
Load/Stress Testing

SGSN/MME Development Process
Copyright © 2006 AT&T. All rights Reserved.Page 24SGSN/MME Development
FNP LABsCP, Market, Ops...
Feature,
enhancement,
Solution...
Review
request
AcceptedRejected
EDR
Review EDR
Rejected
Accepted
Send Back
Inform of Decision
Analyze
Time and budget
assessment
Review
And set
Priorities
Agree
TNRP
Budget,
Communicate
Reject
LAB
FFA
GA
POR
Development
Features, Fixes
Enhancement
Product evolution...

Software Certification Process
Copyright © 2006 AT&T. All rights Reserved.Page 25Test documentation including the Test Object
List (TOL), Test Instructions (TI) and Test
Results (TR) received from SGSN vendor.
TOL, TI and TR review conducted by A&P and
the SGSN vendor.
Discrepancies
identified in test
Requirements?
Review and address discrepancies/
gaps in the TOL, TI or TR
Lab Entry – A&P performs lab validation of
the release using test documentation
provided in previous steps.
Faults Found?
Lab Exit – A&P and the vendor mutually agree
that the release is stable and all known faults
and issues are properly addressed. Lab Exit
Report Approved.
Are faults considered
lab exit gating?
Fix faults, determine level of
regression testing required to fully
validate the fix and subsequent
software build.
Perform Regression Testing
FFA Entry
Addition of A&P approved regression test
suite and finalize test plan for the SGSN
release.
Update
Documentation
escalate comprehensive and fully
documented issue including severity
(high, medium and low)
Update LAB
Issue List
Update LAB
Issue List
LAB Requirements Completed
LAB Requirements:
· Software Requirement
· Hardware Requirement
· Testing Requirement
· Timeframe
· Network Configuration
· Resources Requirement
· Activity Freezes
· Test Call Plan
· Soak Period
· Alternates
NO
YES
YES
YES
NO
NO

FFA Process
Copyright © 2006 AT&T. All rights Reserved.Page 26Lab testing completed including: full
regression and functional tests and
production of a Lab Exit Report
Request FFA through TNRP FFA Process
Is FFA Accepted
YES
NO
Review and address any FFA technical
or budgetary requirements
YES
FFA Exit – General Availability (GA)
Declaration
All Initial Tests Passed
YES
Perform Initial Regression Testing
NO
Provide FFA site requirements and
recommendations through the TNRP process
Update FFA
Request
FFA Entry – A&P ensures that any applicable
test cases not able to be tested in the lab due
to limited HW or resources, etc. are verified.
Request FFA site selection through TNRP FFA
Site Selection Process
Is FFA Site Identified
NO
Escalate FFAA site selection through
the TNRP escalation process
Implement network changes including any
hardware, software and external interface
changes
Address faults / issues, determine
level of regression testing required to
fully validate the fix and subsequent
software build if applicable.
Do Critical network
impacting faults remain?
Perform Regression and Functional Testing
All Tests Passed
YES
NO
Address faults / issues, determine
level of regression testing required to
fully validate the fix and subsequent
software build if applicable.
NO
YES
YES
Revert FFA node to pre FFA Hardware
and software configuration
YES
Revert FFA node to pre FFA Hardware
and software configuration
NO
YES
FFA Requirements:
· Software Requirement
· Hardware Requirement
· Testing Requirement
· Timeframe
· Network Configuration
· Resources Requirement
· Activity Freezes
· Test Call Plan
· Soak Period
· Alternates
Do FFA exit gating
faults remain?
Do Critical network
impacting faults remain?
NO
Address faults / issues, determine
level of regression testing required to
fully validate the fix and subsequent
software build if applicable.

Fault Management Process
Copyright © 2006 AT&T. All rights Reserved.Page 27NO
Take SW Release/Correction
Package through AT&T A&P Lab
Certification Process (Ref. SGSN
Software Release Certification
Process Flow v6.vsd)
Document fault details – scope,
impact, subscriber and device info,
test environment, etc. Update
Issues tracker and test report
Further testing and analysis to
determine scope and impact
Collection of detailed SGSN logs
and traces
Assign fault severity. Open case
with SGSN vendor for further
analysis and resolution
Track case/ticket progress with
SGSN vendor
Obtain Fix/Fault Correction as part
of a new correction package
Review Fault Correction
description, Vendor test report,
Impact details, etc.
Vendor Fault and Correction Delivery Process
(Ref. Vendor Fault Correction Process Flow)
Update Issues
Tracker
SW Fault Discovery
during test case
execution in Redmond
lab
YES
Lab Exit – A&P and the vendor
mutually agree that the release is
stable and all known faults/issues are
addressed.
Take SW Release/Correction
Package through AT&T FFA Process
(Ref. SGSN FFA Process Flow v1.2)
SW Fault Discovery
during test case
execution in FFA
FFA Exit – A&P and the vendor
mutually agree that the release is
stable and all known faults/issues are
addressed.
YES
NO

Ericsson 3G SGSN Lab Buildout
Copyright © 2006 AT&T. All rights Reserved.Page 28

Ericsson 2G SGSN Lab Buildout
Copyright © 2006 AT&T. All rights Reserved.Page 292G
Integration
WTC3ERCGS03
E/// BSC 4
SIE BSC 1
SIE BSC 2
SIE BSC 4
2G
Development
WTC3ERCGS04
E/// BSC 7
SIE BSC 3
2G
Pool
Development
WTC3ERCGS05
E/// BSC 3
E/// BSC 6
WTC3ERCGS06
SGSN 4 will be converted
from a MKIV 2G node to a
MKVI 3G node to support
the Iu-PS/IP for ALU RAN
project.
2009A/CP03
Development Work
MKVI 3G Conversion
ALU Iu-ps & 3G Pooling
Pooled Environment Support

Load/Stress Testing
Copyright © 2006 AT&T. All rights Reserved.Page 30
•The Regional Packet Core team is in the process
of implementing Spirent Load Generation
equipment in the Lab. The LTE integration is the
priority and integration for 2G and 3G Ericsson
SGSN testing will follow.
•The current Spirent platform supports Iu/IP and
Iu/ATM support will be available beginning in
June 2010 with the exact Lab integration
schedule TBD.

Copyright © 2006 AT&T. All rights Reserved.
Ericsson SGSN Roadmap Overview
SGSN –MME Roadmap
Technical Roadmap
Release Plan

Copyright © 2006 AT&T. All rights Reserved.Page 32
Q1 Q2 Q3 Q4Q1 Q2 Q3 Q4
2009 2010 2011
SGSN-MME Roadmap O verview
Releases (GA dates)
CandidateReady for Contract IndicativeReleased
2011
SGSN-MME 2011A
Network requested 2ndary PDP HLR
QoS Override
M2M: Restoration procedures
Ue Trace Streaming
Selective Service Request Handling
Indirect LTE packet forwarding (S1)
HSS initiated modifications of MME
’VLR’
Rel 8 interfaces
S3, S4, S12, S6d, S16
Location Services: CellId over SLg
HSS/S6a on IPv6 transport
Idle-mode signaling reduction
2010A
2010
SGSN-MME 2010B
Increased throughput
Network requested 2ndary
PDP context activation
SGSN pool move with
session continuity
Enhanced ARP
SGSN-MME Interworking
IPv4-v6 over Gn
Mk VI+ hardware platform
IPv6 transport (MME)
SMS over SGs
CS Fallback
2011
SGSN-MME 2011B
Mk VIII Hardware platform
up to 10M SAU
20-30 Gbps (Iu/IP)
ETWS Support
MBMS for LTE
Ethernet Jumbo Frames
EUL up to 12 Mbps
2011A
Q1 Q2 Q3 Q4
2011B
2010B

Copyright © 2006 AT&T. All rights Reserved.Page 33
SGSN-MME 2011A
SGSN
›Network requested 2ndary PDP: HLR
QoS override
›M2M: Restoration Procedures
›Selective Service Request Handling
›Object Manager (OBM): adding Gb/FR
domain
Key Common SGSN -MME Functionality
›MkVIII HW Generation, in LTE/3G Dual Access
configuration supporting up to:
–10 MSAU
–20-30 Gbps (Iu/IP)
–Note: Release period not yet determined
›Automatic transfer of spooled CDR’s
›Improved location based services
›Optimization for M2M stationary devices
›EBM additional trigger events
›UE Trace streaming
Q1 Q2 Q3 Q4Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
2009 2010 2011
2010B2009B 2010A 2011A 2011B
GA date, Candidate release status
GA date, Indicative release status
GAdate

Copyright © 2006 AT&T. All rights Reserved.
Reference Materials

Reference Materials
The following SOLAR link has the reference material listed below:
http://solar.edc.cingular.net/livelink/livelink?func=ll&objid=15564987&objAction=brows
e&sort=name
2009A Architecture
2009A Characteristics
2009A Hardware
AT&T Q1 2010 SGSN -MME Roadmap
Ericsson SGSN 2-009A CP03 Lab Report
National SGSN Report
Network Overview
PDC Tool Report
SGSN Total Node Count
Copyright © 2006 AT&T. All rights Reserved.Page 35

Inter-SGSN
Call Flow
Copyright © 2006 AT&T. All rights Reserved.Page 36

PDP Activation
Call Flow
Copyright © 2006 AT&T. All rights Reserved.Page 37

Attach Call Flow
Copyright © 2006 AT&T. All rights Reserved.Page 38

Gi
GnIu
Two
Tunnels (Iu+Gn)
3G Direct Tunnel tunnel
GTP User plane
GTP signaling
Legend:
RANAP signaling
Iu-Cp
Iu-Up
SGSN
RNC
GGSN
3G Direct Tunnel –Concept
Direct connect between RNC and GGSN
Tags