9700 WiMAX W4 End-To-End Architecture

Do not delete this graphic elements in here:
9700 WiMAX W4 End-to-End

Architecture
TMO18005ed1
All Rights Reserved Alcatel-Lucent @@YEAR

TMO18005
9700 W4 End-to-End Architecture Page 1
Blank Page
9700 WiMAX E2E Architecture 2
This page is left blank intentionally
Document History
Edition
Date
Author
Remarks
01
2009-02-16
Ikram ANDONIAN
First edition

TMO18005
Module Objectives
Upon completion of this module, you should be able to:
Describe the E2E architecture of any WiMAX Network and its different
components
List the different interfaces and distinguish between the legacy and
compliant one and the difference between them
Explain the E2E scenarios for all the services provided by the WiMAX network
Identify the QOS mechanisms used in the air interface and the Ip transport
network
Identify the Security algorithms used in the whole network.

TMO18005
Module Objectives [cont.]
This page is left blank intentionally

TMO18005
Table of Contents
Switch to notes view!
1 IEEE802.16e Vs The WiMAX FORUM
1.1 IEEE802.16 Standards
1.2 WiMAX Forum Specifications
2 Network Reference Model
2.1 WiMAX Forums Network Reference Model
2.2 ASN (Access Service Network)
2.3 CSN & ASP
2.5 Alcatel-Lucent Reference Model
2.5.1 Alcatel-Lucents Template Exemple
3 E2E Services Over WiMAX Access
3.1 Reference Model for E2E Services Over Wimax Access
3.1.1 Direct IP Access
3.1.2 E2E Voice Over IP services
3.1.3 E2E Video Over IP services (MiTv)
3.1.4 E2E Corporate VPN Services
3.1.5 RAN Sharing
3.1.5.1 Service Level Agreement
3.2 Direct Internet Access, VoIP, Live TV and VLAN services
4 Alcatel-Lucent Solution Network Elements
4.1 Alcatel-Lucent NAS Network Elements
4.1.1 WiMAX Base Station (WBS)
4.1.2 WiMAX Access Controller (WAC)
4.1.3 9753 OMC-WR
4.1.4 9759 NPO
4.1.5 9755 RNP
4.1.6 5580 HNM
4.1.7 Backhauling Solution
4.1.7.1 Wireless Solutions
4.1.7.2 Wired Solution
4.1.7.3 Example (DSL Backhauling)
4.1.8 Aggregation Solutions
4.2 Alcatel-Lucent Core Network Elements
5 QoS Management in WiMAX RAN
5.1 QoS in Alcatel-Lucent WiMAX E2E solution
5.1.1 QoS in The Air Interface
5.1.1.1 Service Flows
5.1.1.1 Classifiers
5.1.1.2 ARQ/ H-ARQ Mechanisms
5.1.2 QoS In the IP Transport Interface
5.1.2.1 DCSP Values
5.2 User Profile
5.2.1 Packet-Flow-Descriptor Attribute
5.2.1.1 Packet Data Flow ID
5.2.2 QoS-Descriptor Attribute
5.2.5 QoS Authorization Reference Model
5.2.3 Authorization & Preprovisioned SF
5.2.4 Provisioned SF Creation
5.3 Lease Line
5.3.1 Lease Line Principles
5.3.1.1 Leased Line Profile Example
5.4 Support of VLAN (Tagged Frames)
6 Protocoles & Interfaces in WiMAX Alcatel-Lucent Network
6.1 Network Elements Interconnection
6.2 Air Interface (R1)
6.2.1 PHY Layer

TMO18005
Page
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
24
25
26
27
28
29
31
33
34
35
36
37
38
39
40
41
42
43
44
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
Table of Contents [cont.]

6.2.2 MAC Layer
6.3 Interface R6 (BS-WAC)
6.3.1 BS-WAC IP Addressing
6.3.2 User Plane (BS-WAC)
6.3.3 Control Plane (BS-WAC)
6.3.4 BS-WAC Load balancing
6.3.5 Control Plane (BS-WAC Load balancing )
6.4 Interface R3 (WAC-Core Network)
6.4.1 External HA: Enhanced Legacy vs R3 Compliance
6.4.1 R3 With AAA (RADIUS)
6.4.1.1 Authentication, Authorization & Accounting
6.4.1.2 Radius Paket Format
6.4.2 R3 With External Home Agent (Mobile IP)
6.4.2.1 MiP Principle
6.4.2.2 MiP Registration & Deregistration
6.4.3 R3 with DHCP
6.4.4 DHCP Packet Format
6.4.3.1 DHCP Relay & DHCP Proxy
6.4.4 R3 With SBC (Gq Interface)
6.4.4.1 Diameter Protocol: QoS Management
6.5 Interface R4 (WAC-WAC interface)
7 Initial Network Entry and IP Service Establishment.
7.1 Initial Network Entry (Mobile User)
7.1.1 ASN Connection Setup
7.1.2 Access Authentication and Authorization
7.1.3 IP @ Assignment & Initial Service Establishment
7.1.3.1 DHCP (Relay Case)
7.1.3.2 DHCP (Proxy Case)
7.1.5 Accounting
8 End to End Scenarios
8.1 Network Entry & Initialization
8.2 Discover: Sip Registration
8.3 Discover: VoIP call
8.4 Discover: VoIP Call Release & QoS
8.5 Video Streaming Session Setup (Service Discovery)
8.5 Video Streaming Session Setup: First Part
8.5 Video Streaming Session Setup: QoS and Second Part
9 Mobility
9.1 A Multi-layer IP Mobility Solution
9.1.1 The Proxy Mobile IP Approach
9.2 Intra WAC Hand Over
9.3 MiP Operation
9.3.1 Inter WAC Hand Over with External HA
9.4 Idle Mode & Paging
9.4.2 Idle Mode Principle In BS Load Balancing
10 End To End Security Architecture
10.1 WiMAX Security Methods
10.2 WiMAX Security Protocol Stack
10.3 WiMAX Standard Security Sublayers
10.4 EAP-TTLS & X.509 Certificate
10.5 Security Mechanisms & Protocols : CHAP

TMO18005
Page
67
68
69
70
71
72
73
74
76
77
78
79
81
82
84
86
87
88
89
90
92
93
94
95
96
97
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
117
119
120
121
122
123
124
125
Table of Contents [cont.]

10.6 Two Phases Of EAP-TTLS Protocol
10.6.1 Identity Exchange Phase
10.6.2 Hello Exchange Phase
10.6.3 Finished Exchange Phase
10.6.4 Chap Authentication Phase
10.7 Authentication Successful
10.8 EAP SIM/AKA Methods
10.9 Key Materials
10.10 Key Materials Distribution
10.10 OMC and NE Access Security
11 Accounting And Charging Scenarios
11.1 Accounting & Charging Scenarios
11.2 Online Subscription & PrePaid Architectural Model
11.2.1 Web-Portal/Provisioning Server
11.2.2 Pre-paid Architectural Model
11.2.3 ALU Pre-paid Architecture
11.2.4 Hotlining Architectural Model
11.2.5 Online Subscription Architectural Model
11.2.6 Pre-Provisioning Phase
11.2.7 Subscription Phase
11.3 Post-paid Architectural Model
11.3.1 Post-Paid Messages
11.3.2 Off Line Accounting Procedure_HSI

TMO18005
Page
126
127
128
129
130
131
132
133
134
136
137
138
139
140
141
142
143
144
145
146
150
151
152
1 IEEE802.16e Vs The WiMAX FORUM

TMO18005
1 WMAN Brief Backgrounder
1.1 IEEE802.16 Standards

IEEE Standardisation: IEEE 802 : the LAN/MAN Standards Committee 6 Working Groups:
IEEE 802.11: WLAN Local
IEEE 802.15: WPAN Personal
IEEE 802.16: WMAN Metropolitan
IPIP
transport
transport
MAC
Service
ServiceSpecific
SpecificConvergence
Convergence
Sublayer
Sublayer(CS)
(CS)
MAC
MACCommon
CommonPart
PartSublayer
Sublayer
(MAC
CPS)
(MAC CPS)
Privacy
Privacysublayer
sublayer
Physical
PhysicalLayer
Layer(PHY)
(PHY)
IEEE 802.16 protocol layering
802.16e-2005: IEEE Standard for Local and Metropolitan Area Networks - Part 16: Air Interface for Fixed and
MobileBroadband Wireless Access Systems - Physical and Medium Access Control Layers for Combined Fixed
and Mobile Operation in Licensed Bands-IEEE Computer Society Document
This Amendment updates and expands IEEE Standard 802.16 to allow mobility for mobile subscriber
stations.

TMO18005
1 WMAN Brief Backgrounder
1.2 WiMAX Forum Specifications

WiMAX Forum Develops a certification program for multi-vendor interoperability
Definition of system profiles (lists of features and characteristics)
Elaboration of certification tests
Definition of the certification process
Scheduling of vendors certification
Selection and approval of certification labs
Delivery of certificate
WiMAX Forum defines an end-to-end architecture
Fill the gap with 802.16e
Definition of end-to-end IP network architecture supporting fixed, portable and mobile users
Definition of test procedures to ensure end to end multi-vendor interoperability
Content /
Ecosystem
WiMAX
Forum
(28%)
Component
Suppliers
(17%)
434 Members
Representation in 57
Countries
28 WiMAX Forum
Certified Products
Service Providers
System
Vendors
(32%)
(23%)
There are several standards belonging to the WiMAX family. Some of these standards relating to End-toEnd architecture are outlined below:
1- Recommendations and Requirements for Networks based on WiMAX Forum CertifiedTM Products
Release 1.2.2 --- Stage 1
2- WiMAX End-to-End Network Systems Architecture - (Stage 2: Architecture Tenets, Reference Model and
Reference Points)
3- WiMAX End-to-End Network Systems Architecture (Stage 3: Detailed Protocols and Procedures)

TMO18005

TMO18005
2.1 WiMAX Forums Network Reference Model

The network Reference Model identifies functional entities and reference
points over Which interoperability may be achieved.
It should be noted that in the current Alcatel-lucent Release:

Interface R8 is not supported
Interface R3 is now compliant with the WiMAX Forum recommendations. This release supports
two R3 modes: R3 legacy mode and R3 compliant mode.
Interface R4 is now compliant with the WiMAX Forum recommendations.
Interface R6 remains not compliant with WiMAX Forum recommendations.

TMO18005
2.2 ASN (Access Service Network)

ASN is defined as a complete set of network functions to provide radio access to a
WiMAX subscriber it is called RAN (Radio Access Network) in Alcatel-Lucent Solution :
Layer 3 connectivity with MSS

Transfer of AAA control messages.

Network discovery and selection
of an appropriate NSP

Relay functionality for IP
address allocation)

Radio Resource Management

ASN-CSN tunneling
In addition to the above mandatory features, an ASN may support:

Intra-ASN mobility & Paging and Location Management
ASN comprises network elements such as Base Station, ASN-GW

TMO18005
2.3 CSN & ASP

CSN (Connectivity Service Network) is defined as a set of network functions
that provide IP connectivity services to the WiMAX subscriber, it provides:
MSS IP address allocation for a user session
Internet access
AAA Proxy or Server
Policy and Admission Control based on user subscription profiles
ASN-CSN tunneling support
Subscriber billing and Inter-operator settlement
Inter-ASN mobility
WiMAX services (Multimedia, Broadcast/Multicast, Services, IMS Services, Law
Enforcement Services, etc)

ASP (Application Service Provider) is a 3rd-party business entity that provides
applications or services via Visited-NSP or Home-NSP.
CSN comprises networks elements such as routers, AAA proxy/server, user databases, Interworking GW
devices.
ASP is a 3rd-party business entity that provides applications or services via Visited-NSP or Home-NSP.

TMO18005
2.5 Alcatel-Lucent Reference Model

Alcatel-Lucent reference model as illustrated in the Figure below is in line with the
WiMAX Forum reference.
/ RAN
/ RAN
MSS: Mobile Subscriber Station

ASN: Access Services Network Equivalent to WiMAX ASN
NAP: Network Access Provider (ASN Operator)
CSN: Connectivity Services Network
NSP: Network Service Provided (CSN Operator)
ASP: Application Service Provider

TMO18005
2.5 Alcatel-Lucent reference model
2.5.1 Alcatel-Lucents Template Exemple
WiMAX RAN
WiMAX CN
H4
HA
WAC1
TELECOM
MSS
CN Telecom
BS1
WAC2
BS2
SBC
WAC3
AAA
NGN - IMS
OMC-R Server
DHCP MSS
OMC-R
Client

TMO18005

TMO18005

This section gives an Overview of the E2E architecture. It applies for several types
of E2E network depending of the involved players. It focuses on the E2E
architecture in compliance with the following requirements:

Direct access to the IP network (Direct IP Access)

E2E Voice Over IP services based on IMS/NGN network
Access to Live TV and VoD based on IMS/NGN network
End-to-End VLAN services
NAP sharing.

TMO18005
3.1.1 Direct IP Access
9753
OMC-R
AAA
DNS/DHCP
Linux/Dell 1950
M
Wi
Internet
AX
Ethernet
9740 WAC
Home Agent
Cisco
Firewall
Data Plane
Control Plane

TMO18005
3.1.2 E2E Voice Over IP services

PLMN &
PSTN
Data Plane
Control Plane
MG
MGC
Billing
RTP/IP
SIP
WiMAX RAN &CORE
LSM
AAA/HSS
DHCP
RADIUS
DIAMETER
SIP
SBC
Gq/DIAMETER
DHCP
RTP/IP
BS
WAC
Home Agent
IP
Internet/ISP
The following NEs are part of the IMS solution:

A SBC (Session Border Controller): please refer to previous section
A S-CSCF (Serving - Call Session Control Function)
A HSS (Home Subscriber Server)
A MRF (Media Resource Function) to send tones and announcements
A MGCF (Media Gateway Control Function)
A MGW (Media GateWay)
Nodes for ensuring IMS charging (Prepaid and Postpaid)
O&M nodes
A node in charge of the Legal Interceptions.

TMO18005
3.1.3 E2E Video Over IP services (MiTv)
WiMAX RAN & CORE
Mobile Interactive TV
DHCP
Mob. TV streaming
server
AAA
SBC
Gq/DIAMETER
RTP/IP
RADIUS
Mob. TV
Studio 5942
DHCP
RTP/IP
BS
Home Agent
WAC
HTTP
IP
Internet /ISP
The Alcatel-Lucent complete solution includes the following logical components:

MiTV application server
Encoder
Streaming Server
Content Management System
Video mixer (used with RichMedia client
WAP interface
Service Node
MiTV Client
For more details please refer to Annex number

TMO18005
Mob. TV engine
8670
Data Plane
Control Plane
3.1.4 E2E Corporate VPN Services

Transparent connection of customer site to service provider network at layer 2 via WiMAX RAN
Ethernet frames transparently transported through WiMAX RAN
QoS on air interface & WiMAX RAN (per VLAN QoS)

TMO18005
3.1.4 E2E Corporate VPN Services [cont.]

The architecture can allow WiMAX customers to access the IP/MPLS service providers leveraging
different VPN services and other IP-based services empowered by the 7x50 PE.

TMO18005
3.1.5 RAN Sharing

The following figure presents the end-to-end architecture for the NAP sharing:
DHCP
DNS
AAA
SBC/
FW/
NAT
NSP 1
NSP 1
NSP 2
NSP 2
ER
DHCP
DNS
AAA
SBC/
FW/
NAT
NSP n
NSP n
DHCP
DNS
AAA
SBC/
FW/
NAT
ER
ER
ER
ER
ER
802.1q
802.1qtransport
transportnetwork
networktransport
transport
GRE tunnel
(one per SF)
WAC cluster 1
WAC cluster p
transport network
transport network
BS
BS
BS
BS
BS
BS
NAP WiMAX
network
MSs
MSs
MSs
MSs
W3 situation:
Only fixed NSPs. No mobility for RAN sharing, only in HA less configuration.
MS IP@ overlap between NSPs not supported
Blind network entry
No roaming
W4 Improvement:
MS IP@ overlap between NSPs supported
Network Discovery and Selection (defined by NWG and 802.16g) supported
Roaming supported (W4.2)

TMO18005
MSs
MSs
3.1.5 RAN Sharing
3.1.5.1 Service Level Agreement

SLA
Subscriber
NAP
NSP
CSN 1
CPE I SP 1
ASN
CSN x
CPE I SP x
SLA
Service Level Agreement between the User and its NSP

Service Level Agreement Between the NSP and the NAP

TMO18005
3.2 Direct Internet Access, VoIP, Live TV and VLAN services

Access
Backhaul
Broadband
WiMAX Access Broadband Services
Aggregation & Mobility Control
Routing
Gig-E Ring
Eth.
PTP Microwave
Eth.
Service
Routing
7450
ESS
Copper
Eth.
Fiber
Content
7450
ESS
WAC
or
Optical
Multi-Service
Node
7750
SR
HA
IMS/ NGN Networks
PSTN
OMSN
WAC
Eth.
OMSN
Leased lines
Video Head-End
VoD
Encoders
Ethernet
Eth.
Services
Network
The WAC through the feature HA is connected to:

A SBC for real time traffic as VoIP and Live TV
A Firewall for Direct IP services
A BSR (Broadband Service Router) for End-to-end Ethernet services.

TMO18005
7750
SR
Internet
4 Alcatel-Lucent Solution Network

Elements

TMO18005
4.1 Alcatel-Lucent NAS Network Elements

The WiMAX Alcatel-Lucent WiMAX ASN Network consists of an integrated network
providing standardized interfaces towards IP Packet Data Networks an comprises:
BS (Base Station): A WiMAX Base Station provides wireless Internet access to Subscriber
Stations (MSS), which are compliant with (WiMAX) standard IEEE 802.16e.
WAC (WiMAX Access Controller): The WAC provides the connectivity for the MSS with
the rest of the network (Internet, Core Network, Corporate Network, etc..).
OMC-R: it performs network surveillance, configuration and management.
RNP: it performs Radio Network Planning/optimization.
NPO: it performs network quality of service monitoring and radio Network optimization
for the WiMAX Access Network.
HMN (Home Network Manager): it performs device management
Backhauling solutions: wireless or wired solutions.

TMO18005
4.1 Alcatel-Lucent NAS network Elements
4.1.1 WiMAX Base Station (WBS)

C-WBS, L-WBS and L2- WBS
C-WBS
Compact
Base Station for WiMAX
L-WBS
Lightweight
All-in-one
High Capacity
Single Carrier with 4TX/RX
All-in-one
Small form factor
Single Carrier with 2TX/RX
Urban Roof Top

Remote radio system
4 x 35 dBm output power
AC and DC Power Supply
35 l
Hot Zones - Tower Mounted

Remote radio system
2 x 35 dBm output power
DC Power Supply
24 l
L2-WBS
Lightweight-2
All-in-one
Reduced weight versus L-WBS
Multi-Carrier with 2TX/RX
Hot Zones - Tower Mounted

High power (2 x 38 dBm)
4TX/4RX with two L2-WBS
DC Power Supply
12.5 l
The Alcatel-Lucent solutions are the following:

COMPACT WIMAX BASE STATION (C-WBS)
This Base Station includes integrated 4 TX/RX chains for maximizing radio performances through Beam Forming
(BF) radio algorithms.
The C-WBS with BF provides significant coverage and capacity gains, strongly reduces interference and
optimizes the spectrum usage.
LIGHT WIMAX BASE STATION (L-WBS)
This Base Station is equipped with 2 TX/RX chains. The L-WBS, due to its small size and weight, can be installed
with fewest site constraints on walls, poles and towers. It is optimized for MIMO algorithms, providing
additional increase in capacity and/or coverage versus a single antenna system.
LIGHTWEIGHT 2 WiMAX BASE STATION (L2-WBS)
L2-WBS evolves the Lightweight WiMAX Base Station product range: Reduced weight, Multi-carrier
capabilities, Higher output power: 38 dBm (6W), 20 MHz bandwidth support, Support AAS feature with two
L2-WBS units, 2 radio chains per L2-WBS unit, Single sector, 20 MHz support, Multi-carrier capable, MiMo &
BF support.

TMO18005
4.1 Alcatel-Lucent NAS network Elements
4.1.1 WiMAX Base Station (WBS) [cont.]

Distributed WiMAX BS
D-WBS
Distributed
BS Solutions for WiMAX
D-WBS for central site functions
L- and C-WBS for remote unit
Central Cabinet Option

DC and Ethernet/Fiber supply
C-WBS and L-WBS Connections
Transmission & BBU Options
Central O&M Site Access
DISTRIBUTED WIMAX BASE STATION (D-WBS)

The D-WBS consists of an outdoor site support cabinet, hosting power supply, battery backup, optional backhaul
transmission equipment and WBS O&M access functions, in a multi-sector configuration, backup batteries for
backup times up to 8 hours.
The L-WBS or C-WBS can be remotely installed from the D-WBS Central cabinet with either Electrical Ethernet
(integrated in Power Supply) or Optical Ethernet connections.

TMO18005
4.1 IOT with Alcatel-Lucent NAS network Elements
4.1.2 WiMAX Access Controller (WAC)

The WAC cluster is composed of a switch stack and a set of WAC units in a rack. (The
number of switches and WAC units -Dell1950 servers- depends on the Configuration).
SWITCH 1
SWITCH 2
SWITCH 3
WAC Unit 1
Depending on the configuration:
WAC Unit 2
The switch stack is composed of one, two or three switches.

The WAC unit stack is composed of one up to 10 active WAC
units + two spare WAC units.
WAC Unit 3
WAC Unit N+P
WAC (WiMAX Access Controller):

The WAC as central equipment in the ASN provides or participates to the realization of the
following features:
Subscriber Station authentication and authorization at initial network entry.
MSS IP connectivity establishment by implementing of a DHCP Relay function and a DHCP Proxy function.
MSS context release procedures
MIP Foreign Agent and PMIP client or Embedded Home Agent
Intra-WAC handover & Inter-WAC handover:
MSS idle context management & Paging controller

TMO18005
4.1.2 WiMAX Access Controller (WAC) [cont.]

Configuration 2
Configuration 1
Configuration 4
Configuration 6
WAC Server 4
Configuration 10
WAC Server 4
WAC Server 4
WAC Server 12
WAC Server 3
WAC Server 3
WAC Server 3
WAC Server 2
WAC Server 2
WAC Server 2
WAC Server 3
WAC Server 2
WAC Server 11
WAC Server 1
WAC Server 1
OK PRI PWR BPS
OmniSwitc h 6850- 24 X
10
11 12
13 1 4 1 5 16
17
18 19
2 0 21
22
O K PRI PWR BPS
23 24
O mni Swit ch 685 0- 24X
10
11
12
13
14
WAC Server 1
15 16
17
18 19
2 0 2 1 22
OK PRI PWR BPS
23 24
OmniSwi tch 6 850- 24X
10
11 12
13
USB
WAC Server 1
WAC Server 1
14
15
16 17
18 19
20
21 22
23 2 4
OK PRI PWR BPS
OmniSwitc h 6850- 24 X
USB
10
11 12
1 3 1 4 1 5 16 1 7 1 8 19
20
21 22
23
O K PR I PWR BPS
24
OmniSwitc h 6 850- 24X
X1
21
X1
X2
22
23
24
X2
CL AS S 1 LA SE R P RO D UC T
CLA S S 1 LA SE R P RO D UC T
C O NS O LE
10
11 12
13 1 4 1 5 16
17
18 19
20
21
22
23 24
USB
X1
21
X1
X2
22
23
24
X2
CLA S S 1 LA SE R P RO D UC T
C LA SS 1LA S ER PR O DU C T
C O NS O LE
21
X1
X2
22
23
24
X1
C LAS S 1 LA SE R P R OD U CT
X2
CLA S S 1 LAS E R P RO D UC T
CO N SO LE
WAC Switch 1
USB
USB
X1
X2
C O NS O LE
WAC Switch 1
WAC Switch 1
X1
21
X1
X2
22
23
24
C O NS O LE
WAC Switch 1
WAC Switch 3
WAC Switch 2
WAC Switch 2
X2
C LA SS 1LA S ER PR O DU C T
CL AS S 1 LA SE R P RO D UC T
WAC Switch 2
21
X1
X2
22
23
24
WAC Switch 1
WAC Switch 3
WAC Switch 2
WAC Server 10
WAC Server 9
WAC Server 7
WAC Server 7
WAC Server 8
Power Distribution
Power Distribution
WAC Server 6
WAC Server 6
WAC Server 5
WAC Server 5
WAC Server 5
Power Distribution
Power Distribution
Power Distribution
High Availability Configurations

TMO18005
4.1.3 9753 OMC-WR

The OMC-R provides, using the Element Manager (NEM) and Network Management
functional blocks (integrated in a single GUI), operations and maintenance
services with full WiMAX RAN scope :
Physical and logical resource supervision
Software management application
Hardware and software inventory
OMC-R
WiMAX
Radio Network configuration

Performance Monitoring and
QoS analysis
SNMP
Interface
LMT
BS
BS NEM
OMC-R: it performs network surveillance, quality of service monitoring and radio network
planning/optimization for the WiMAX Access Network. It provides a complete set of advanced
management features:
Easy interface with Radio Network Planning (RNP) application for trouble-free
implementation of the network during deployment and densification.
Network plug and play functions
Provisioning and template-based radio configuration
Highly intuitive man-machine interface
Full set of QoS indicators and predefined or customized QoS reports give full network
performance visibility,
RNO (Radio Network Optimizer)
Scalable capacity, up to 2000 cells,
It hosts a NTP server, a DNS server and a DHCP server

TMO18005
LMT
WAC
WAC NEM
4.1.4 9759 NPO

Measurements are permanently collected on nodes, covering:
Call Control Management
Northbound
Registration procedures
SS attachements
Sessions setup
Handover procedures and execution times
Authentication events
IP packet statistics
User plane statistics
QoS measurements
Radio measurements
Traffic load
Radio traces

NPO
PM
Consolidation, QoS
Analysis and long
term storage
PM
Temporary storage
and QoS alerter
processing
OMC
Reporting period can be configured to

60, 30 or 15
WAC
BS
Network Elements

TMO18005
4.1.5 9755 RNP

A9155 is Open to Seamlessly Integrate in Customers Environment:
Easy Data Model Adaptation
Adding New Parameters to any Data Table
Full Availability of Customized Parameters
for Filter, Display, Export/Import,
Prediction Module and AFP Module API
Access to all Input Parameters (Compatibility
Information, Network Data, Path Loss Matrices,
Control Parameters, )
Seamless Integration of Model Parameters
General API
Access to All Data Tables
All Major Functionality Accessible Inside Macros
Support of Automation of Repeating Tasks

TMO18005
4.1.6 5580 HNM

The HNM 5580 is an Alcatel-Lucent ACS (Auto Configuration Server) for
performing the management activities for DSL (Digital Subscribe Line) CPE
management which supports TR-069 Standard.
The WiMAX CPE obeys IEEE 802.16 and WiMAX forum standards. It shall support TR-069
standard for remote CPE management to interwork with HNM 5580.
The WiMAX CPE follows the procedures of IEEE 802.16 (Channel Synchronization, Initial Ranging, Basic
Capabilities Negotiation, AAA Procedures, PKM Key Exchange and Registration Procedure) for entering into
the network. After BS registration (Reg-req, Reg-rsp) the CPE performs DHCP (Dynamic Host Control
Protocol) procedures [Ref. 2.4]. During the DHCP procedure the CPE obtains the URL of HNM 5580 in the
DHCP offer message included in DHCP option 43 and the CPE uses DNS (Domain Name Server) to
resolve the IP address of the HNM 5580 server.

TMO18005

Wimax system solutions includes radio sites backhauling options for different kind of
physical support: wireless, copper or optical solutions.
Star Topology
Chain Topology
WiMAX
Microwave
backhauling
Microwave
backhauling
WiMAX-WAC
WiMAX-WAC
Microwave
Metro
Microwave
Metro
The backhauling on the RAN is full IP>> It can be on a level 2 network.


TMO18005
4.1.7.1 Wireless Solutions

In the Alcatel portfolio two products can be used for microwave backhauling:
A9400 AWY and A9600 USY.
9400 AWY
10/100
BaseT
7 GHz up to 38 GHz
9600 USY
6 GHz up to 38 GHz
10/100 BaseT
A9400 AWY (7 to 38 GHz):

On the air bitrate:
>> Up to 64Mbps
Available interfaces:
>> 2 x 10/100 BaseT Ethernet interfaces.
>> From 2xE1 up to 16xE1 interfaces
>> Any mix of traffic is possible.
A9600 USY (6 to 38 GHz)
>> 1 x 1 Gb/s Ethernet
>> Up to 3 x 100Base-T Ethernet on VC3

TMO18005
STM1
WAC
4.1.7.2 Wired Solution

The Wired Backhaul solution can be on Twisted Copper Line or Optical Fibre Line.
Copper solution: The Copper line has smaller capacity and allows a limited distance.
Aggregation
Network
WiMAX Site
Up to 8 twisted pairs
BS
10/100 Base
1521 CL IP
1521 CL IP
Ethernet switch,
Optical solution: There are two optical solutions: one SDH solution based on Alcatel SDH
family products and a stand-alone solution based on the Alcatel 1521FL IP.
Ethernet, switch,
Router, ADM
BS
1521 CL IP
Optical fibre
BS
1521 Subrack
1521 FL IP
The Alcatel 1521CL IP extends the reach of native Ethernet services to sites by using twisted copper pairs
thanks to standards-based 2BASE-TL and SHDSL and G-SHDSL technology. Ethernet frames are fragmented
across multiple copper pairs.
Alcatel 1615BCE is a solution for Ethernet extension of SDH network on copper line up to 4 pairs. It is managed by
the Alcatel 1353SH also used for all the OMSN Alcatel family. It can be an integrated solution when the SDH
network is an Alcatel one. If the SDH network is not from Alcatel the stand-alone solution is well adapted.

TMO18005
4.1.7.3 Example (DSL Backhauling)

WIMAX
WIMAX RAN
RAN
PEF
PEF
Indoor CPE
OMC-R
BS
AAA
server
PDF
Can be
common
WAC
IP
IP
CORE
CORE
Session
Resource
Broker
S-CSCF
Outdoor CPE
HA
ISAM
ADSL modem
Ethernet
switch
ADSL
ADSL
AWS AN
AN
Router with
HA function
Voice
Gateway
BRAS
SBC
INTERNET
This architecture provides Portability/Mobility WiMAX services in the ADSL Network

Basics of the solution:
Base Station connected to ISAM via electrical or optical Ethernet
Base Station is connected on the existing Ethernet switch embedded in the ISAM
VLAN tagging is done by per port by the ISAM Ethernet switch
ISAM used as an Ethernet switch for BS to WAC link
Level 2 ADSL aggregation network is used
IP Convergence Sub-layer and DHCP model used
Solution is valid for Fixed Wireless Access and also for Nomadicity/Mobility services
AWS and OMC-R integration

Unique subscriber management provided by AWS using OMC-R northbound interface
AWS is the central point of supervision (alarms, logs,)

TMO18005
PSTN
PSTN
4.1.8 Aggregation Solutions

The most commonly used products for aggregation are :
7710 / 7750 SR - Service router, used for Multi-Service Edge/Core
7450 ESS - Ethernet service switch, used for Metro Service Edge Aggregation
Wireless
backhauling
MPLS
network
WTD
product
9500
MXC
IPD
products
An IPD product is used as aggregation switch for two wireless backhauling networks,
the RAN corresponds to one VPLS.
As this IPD product uses unqualified mode, any frames received on its 2 ports are
part of the same VPLS, whatever the tag.
A broadcast sent by a booting WBS in the first group of WBS is forwarded to the
second group of WBS.
In the WiMAx solution, IPD routers are used :

As aggregation device on RAN (7750 SHT - Packet One)
As interconnection device on CSN (7450 SHT - Packet One), to connect AAA, DHCP, HA.
As Edge Router (SFR Wholesale solution) to route traffic to NSP networks.
On backhauling networks, using MPLS technology.
Sites and WAC clusters can be interconnected using :

Layer 2 VPN

With VLL, a point to point layer 2 Ethernet connection is defined between two endpoints
With VPLS, multipoint to multipoint Ethernet connections are available (MPLS network is then seen as a
Big switch )
Layer3-VPN (MPLS networks, rfc 2547)

TMO18005
4.2 Alcatel-Lucent Core Network Elements

Home Agent (Cisco 3845):
Higher capacity may be envisaged if required
IPD 77X0 support of HA function under assessment
AAA server:
HSS 1430 / SDM (Carrier/Applications/Subscriber Data Management)
Vital AAA (Services/Professional Services/OSS-BSS Software Integration)
DHCP Server
Vital QIP (Enterprise/Enterprise Solution Group)
E2E Voice service:
WiMAX RAN ACME
Pre-Paid server and On-line Subscription server
8610 ICC (Carrier/Applications/Payment)

TMO18005
5 QoS Management in WiMAX RAN

TMO18005
5 QoS Management & Admission Control in WIMAX RAN

Overview of the NE of the WiMAX RAN involved in QoS in the Alcatel-Lucent
WiMAX E2E solution.
The RAN supports two types of traffic:

With guaranteed resources.
Without guaranteed resources.
In this release multiple NSPs may supply their service through the same NAP. In this case mobility (full
mobility) is not supported (handover is not supported).
When the NAP and NSP domains are separated domains, an Edge Router (ER) shall be present at the
interface between the NAP and each NSP to control the traffic according to the SLA each NSP has with the
NAP. This ER may also have firewall functions.
When the NAP and NSP domains are in the same administrative domain, there is no need to have an ER at
the interface between the NAP and each NSP. In this case the ER shall be at the interface between the
NSPs and external content providers (ASP).

TMO18005
5.1 QoS in Alcatel-Lucent WiMAX E2E solution [cont.]

Service-aware Architecture
QoS initiated by the network for VoIP, VoD, sessions (through SBC)
QoS treatment shared over SBC, WAC and BS
QoS treatment results in a classification and prioritization of traffics at both:
Air Interface : based on Classifiers and selection of the appropriate Service Flow
IP Transport interface : based on DSCP tagging at layer 3 IP
IP Networks
IP
IP
MSS
applications)
BS
IEEE QoS Classes

Service Flows
(QoS sensitive
WAC
IP QoS Classes (DiffServ)

TMO18005
SBC

Classification
Process by which a packet is mapped on to a particular connection (CID) for transmission between
MSS and BS
SF associated to a CID.
Classification mechanism = procedure used to select most appropriate SF
For a Service Flow, a classifier consists on:
Browser
SIP user
agent
IP packet classifiers
Reference to a CID ( Connection Id )
Mapping of a packets to a classifier priority

TMO18005
Convergence
HTTP ports,
sub-layer
IP @
nrtPS
Classifiers parameters
TOS/DSCP range
Protocol
Source port and source IP address
Destination port and destination IP address
RTP ports, IP @
BE
IP stack
UGS
Classifiers operates at Convergence sub-layer (IP-CS):

configured with classifiers which act as filters for classifying
packets
5.1.1.1 Service Flows

Data delivery Services
(Service flow types)
QoS parameters
Examples of application
UGS (Unsolicited Grant Service)
Traffic rate, Tolerate jitter, Max

latency,
Unsolicited grant interval
VoIP without silence suppression,

circuit emulation, leased line
ERT-VR (Extended Real Time

Variable Rate)
Min reserved traffic rate, Max

sustained traffic rate, Max jitter,
Max latency,
Unsolicited grant interval,
priority
VoIP with silence suppression,

gamming, leased line

sustained traffic rate, Max jitter,
Max latency,
Unsolicited polling interval,
priority
Video streaming, leased line

sustained traffic rate, Traffic
priority
Internet access with guaranteed

BW (i.e. 512kbps Internet
access), delay tolerant data
streams
Max sustained traffic rate, Traffic

priority
Background communication (Mail,

FTP etc)
RT-VR (Real Time Variable Rate)
NRT-VR (Non-Real Time Variable

Rate)
BE (Best Effort)

TMO18005
5.1.1.1 Classifiers
A classifier for IP CS may include the following criteria:
IP Type of Service/DSCP (one range of ToS/DSCP values may be included),IP masked
source address, IP destination address, Protocol source port range, Protocol

destination port range
IP CS classifiers criteria for DL packets
IP CS classifiers criteria for UL packets


TMO18005
5.1.1.2 ARQ/ H-ARQ Mechanisms

ARQ is one of the mechanisms that are used on the radio interface to satisfy the QoS requirements
of a service flow received in the user QoS profile.
Defined in IEEE802.16e ARQ is a MAC layer mechanism between a MS and a BS that uses the
retransmission of parts of MAC SDUs (ARQ blocks) being received erroneously to reduce the number
of errored SDUs or even to deliver error free SDUs.
The H-ARQ mechanism is a combination between ARQ and FEC technique.
ARQ STOP & WAIT
H- ARQ

TMO18005

DiffServ approach based on the following principles :
Classify : packets are analysed
Aggregate : Packets are put in the same queue when they should receive the same treatment A set
of packet forwarding treatments (PHB) is created.

(Different PHB: Default, Best Effort, AF (Assured Forwarding) : divided in 4 classes AF1 to AF4 & EF
(Expedited Forwarding)
Each packet is marked by writing its PHB in the DSCP field. Core routers rely only on DSCP to
provide the different types of service.

Classification, marking, policing/shaping, in edge routers.
Queuing & scheduling per DSCP class in core/edge routers

TMO18005
5.1.2.1 DCSP Values

DS Field uses the same byte as TOS in the IPv4 header, but that byte is redefined to solve the
limitations of TOS Definition.
6
7
ECN : Explicit Congestion
DCSP: Differentiated Service Code Point
Notification
Exemple:
Service type = Media flow type
DSCP
DSCP
ARQ
Decimal
Schedule
Type
Value
VoIP
Streaming live TV, Streaming VoD
Robust Browser
EF (101110)
46
UGS or ERT- VR
AF41 (100010)
34
RT- VR or ERT VR
BE
BE (000000)
Leased line - conversational
EF (101110)
46
Leased line - streaming
AF41 (100010)
34
RT - VR
Leased line - non - real time
AF31 (011010)
26
NRT - VR

TMO18005
UGS or ERT - VR
5.2 User Profile

The AAA server is able to provide users QoS profiles under the VSAs format as below:
User profile in W4 (new VSA in Radius message)
Packet Flow Descriptor
>> In Access Accept message

>> Corresponds to the initial downlink and
uplink service flows that are activated on
the air interface at MS network entry time.
TLV
ID
1
2
4
5
6
7
8
9
10
TLV N ame
PacketDataFlowID
ServiceDataFlowID
Direction
ActivationTrigger
TransportType
UplinkQosID
DownlinkQoSID
UplinkClassifier
DownlinkClassifier
Length
Octets
2+ 2
2+ 2
2+ 1
2+ 1
2+ 1
2+ 1
2+ 1
2+ Length
2+ Length
QoS Descriptor
This attribute describes QoS parameters

that are associated to a packet data flow
>> One QoS descriptor per service flow
TLV ID
TLV N a me
1
4
5
6
7
9
10
12
13
14
15
Q oS ID
Schedule Type
Traffic Priority
Maximum Sustained Traffic Rate
Minimum Reserved Traffic Rate
Tolerated Jitter
Maximum Latency
Media Flow Type
Unsolicited Grant Interval
SDU Size
Unsolicited Polling Interval

TMO18005
Length
O ctets
3
3
3
6
6
6
6
3
4
3
4
5.2 User Profile

This attribute describes a packet service flow that may be unidirectional or bi-directional. The
following parameters (TLV) may be included in this attribute:
PacketDataFlow-ID: This parameter identifies a packet data flow instance.
ServiceDataFlow-ID: This parameter is used to group one or more packet data flows belonging to
the same service instance (VoIP call, VoD call, ).
Direction: The direction of the Packet Data Flow (uplink, downlink, or bi-directional).
Activation Trigger: This parameter specifies the trigger to be used for the activation of the
service flow. This attribute allows to distinguish pre-provisioned SFs from dynamic SFs.
UplinkQoSID: The identifier of the QoS-Descriptor for the uplink direction or for bi-direction if the
flow is bi-directional with symmetrical QoS.
DownlinkQoSID: The identifier of the QoS-Descriptor for the downlink direction.
Uplink/ DownlinkClassifier: The classifier to match for traffic flowing in the uplink/ downlink
direction.
At least a one Packet-Flow-Descriptor VSA describing a bi-directional packet data

flow shall be included in the Access-Accept message: this packet data flow
corresponds to the initial DL & UL service flows that are activated on the air
interface at MS network entry time.

TMO18005
5.2.1.1 Packet Data Flow ID

Three kinds of Service Flows are handled by the ALUs ASN, distinguished by means of the Packet-DataFlow-ID (PDF-ID) retrieved from AAA server:
Initial Service Flow (ISF): PDF-ID value is between 1 and 20.
During Initial Network Entry this Service Flow is established just after the authentication without waiting
for the MS IP allocation procedure.
Pre-Provisioned Service Flow: PDF-ID value is greater than 20 with the Activation Trigger identifying
a pre-provisioned SF.
These Service Flows are established after the MS IP allocation procedure during the Initial Network Entry.
Dynamic Service Flow: PDF-ID value is greater than 20 with the Activation Trigger identifying a
Dynamic SF.
Dynamic SFs retrieved from the AAA server are used for Authorization when a call setup or VoD request is
received from the user through the SBC. Dynamic SFs are only established during call setup and are
activated via Gq.

TMO18005
5.2 User Profile
5.2.2 QoS-Descriptor Attribute

This attribute describes over the air QoS parameters that are associated with a flow:
QoSID: A unique ID for this QoS specification.
Schedule Type: The parameter specifies the Uplink Granted Scheduling Type.
Traffic Priority: The value of this parameter specifies the priority assigned to a service flow.
Maximum Sustained Traffic Rate: This parameter defines the peak information rate of the service.
Minimum Reserved Traffic Rate: Represents the minimum reserved traffic rate.
Maximum Traffic Burst: Represents the maximum traffic burst.
Tolerated Jitter
Maximum Latency
Media Flow Type: This parameter defines the service type.
Unsolicited Grant Interval: The value of this parameter specifies the nominal interval between
successive data grant opportunities for this service flow.
Unsolicited Polling Interval: The value of this parameter specifies the maximal nominal
interval between successive polling grants opportunities for this Service Flow.

TMO18005
5.2 User Profile
5.2.5 QoS Authorization Reference Model

SBC
MSS
SIP / RTSP ( SDP : Media information )
RTSP Client
P-CSCF
SIP Client
BS
Diameter
Relay
WAC
Diameter
PDF
RELAY
AAR/AAA
(SF/QoS
Parameters)
PEF
AC
Gq Diameter
PEF
AC
Service Information
AC
(SF/QoS
Parameters)
IP transport
MAC
scheduler
IP transport
R1
MAC
scheduler
IP transport
IP transport
R6
R4
AC - Admission Control: the set of actions taken by a network during the call
set-up phase or during
handover in order to determine if the call should be accepted or rejected.
PDF - Policy Decision Function: is a logical policy decision element that uses
standard IP mechanisms to
implement policy in the IP media layer. The PDF makes decisions in regard to
network based IP policy
Using policy rules, and communicates these decisions to the PEF.
PEF - Policy Enforcement Function: a logical entity that enforces policy
decisions made by the PDF.

TMO18005
5.2 User Profile
5.2.3 Authorization & Preprovisioned SF

The QoS user profile is downloaded in the Packet-Flow-Descriptor and
QoSDescriptor VSAs of the RADIUS Access Accept message by the WAC from AAA
just after the successful authentication.
The Pre-provisioned Service Flows are immediately created.
Example:
User
Serving BS
User authentication
WAC
Radius client
AAA
User profile
Example:
128 kbit/s minimum UL & DL
512 kbits/s maximum UL & DL
Radius Accept (, User Profile,)
Creation of pre-provisionned service at network entry

Based on User Profile
Creation of 2 NRT-VR connections [128 kbits/s
min. UL & DL and 512 kbits/s max. UL & DL]

TMO18005
5.2 User Profile
5.2.4 Provisioned SF Creation

The Provisioned Service Flows are dynamically created on demand basis:
Example:
RAN
SBC
WAC Serving
Gq
Diameter
User Profile
Check
SIP: INVITE (SDP Offer)
Service Flow Setup
SF Creation
Request
SF Creation
Response
Diameter: AAR
(service information)
Diameter: AAA
(success)
SIP: TRYING/RINGING/2000K/ACK

TMO18005
5.3 Lease Line

A Leased Line is defined by a set of entities:
GRE tunnel-end-point and DSCP code point
Service Flow on Radio End-Point carrying the GRE tunnel Service Flow leased Line

or Service flow
Classifiers defining which user flows will be encapsulated in the GRE tunnel.
A Service Flow leased line corresponds to a pre-provisioned service flow
Scheduling types For LL, may be set to UGS or RT-Vr or ERT-Vr or NRT-Vr
Service Flow Leased lines may be established using the following service types:
LEASED LINECONVERSATIONAL
LEASED LINE STREAMING
LEASED LINE-NON-REAL TIME

TMO18005
5.3 Leased Line

A leased line is established after the MS authentication procedure during network
entry.
A leased line corresponds to a pre-provisioned service flow created from profiles in
the AAA server through RADIUS Access Accept message and corresponding to a given
user QoS profile.
Classifiers
BE
WAC parameters
LLC
BS
CPE
BE
BS
LLC
WAC
Robust Bowser
DSCP = 0
Lease Line
Conversationnal
DSCP = 46
Service Flows

TMO18005
AAA
Profiles
HA
5.3.1.1 Leased Line Profile Example

Guaranteed DL & UL throughput on air interface
Leased line QoS characteristics defined in User Profile
E.g. 512 kbits/s DL and 512 kbits/s UL
Connection created at Network entry
1) Network entry
AAA server
WAC
PC
Example:
Lease line (UGS connection)
512 kbits/s guaranteed UL
512 kbits/s guaranteed DL
PC
CPE
2) User profile download

3) Connection creation
request
4) Connection creation
(512 kbits/ s UL, DL)

TMO18005
5.4 Support of VLAN (Tagged Frames)

A VLAN-tagged frame is a tagged frame whose tag header carries both VLAN identification and priority
Information:

VLAN-tagging on the CN side (HA less configuration): to isolate the traffic of the different NSPs.
VLAN-tagging on the ASN side (HA and HA less configurations): priority bits in the Ethernet frames.
VLAN-tagging on the CN and ASN side (HA less configuration): priority bits in the Ethernet frames.

TMO18005
6 Protocoles & Interfaces in WiMAX

Alcatel-Lucent Network

TMO18005
6.1 Network Elements Interconnection

SBC
OMC
R3
SNMPv3
DIAMETER/TCP/IP
SNMPv3
DHCP
XML/HTTPS
R1
MSS
DHCP/UDP/IP
R6
BS
802.16e
MAC
R3
WAC
R3
CCC/TCP/IP
MIP/UDP/IP
R3
R4
HA
RADIUS/UDP/IP
DIAMETER/TCP/IP
WAC
AAA

TMO18005
Server

The WiMAX protocol stack as defined by the IEEE802.16e:
CS SAP
Convergence
Convergence Sub-layer
Sub-layer (CS)
(CS)
CS
MAC
MAC SAP
MAC CPS
MAC
MAC Common
Common Part
Part Sub-layer
Sub-layer
Security Sub-layer
Security
Security Sub-layer
Sub-layer
PHY
PHY SAP
Physical
Physical Layer
Layer
PHY

TMO18005
6.2.1 PHY Layer

The resources are available in the time domains by means of symbols and in frequency domain by
means of sub-carrier for allocation to individual users.
Frame Control Header

Time Symbol
Sub-channel
DL& UL maps
Preamble DL
FCH
DL-MAP
FCH
UL-MAP
DL-MAP
FCH
UL-MAP
Sucarriers
Preamble DL
DL Preamble
DL
UL
OFDMA Frame
WiMAX as defined in the IEEE 820.16e supports both TDD and FDD. The Commercial Alcatel-Lucent solution is
limited to the TDD (Time Duplex Mode). Burst downlinks allow the use of more advanced robustness and
capacity enhancement techniques, such as subscriber-level adaptive burst profiling and advanced antenna
systems.

TMO18005
6.2.2 MAC Layer

MAC layer is connection-oriented. All data communications are in the context of a
connection
BS
SS
Network
Network Access
Access
Connection
Connection Establishment/Release
Establishment/Release
Connection
Connection Maintenance
Maintenance
Service
Service Flow
Flow Establishment
Establishment

TMO18005

The network interface of the BS is based on the Fast Ethernet technology.
This Ethernet link connects the BS to the access controller (WAC) via a Transport
Network.
The transport network may be a Layer 3 (IP) network or a Layer 2 network (layer2),
that means, it includes routers and/or L2 switches
BS
Control Plane
User plane
The transport network

TMO18005
WAC
6.3.1 BS-WAC IP Addressing

IP addresses used in the Control Plane are distinct from those used in the User
Plane.
1
1
1
1
RAN CN
OAM IP@
CP IP@ WAC-BS & IWAC
UP IP@ WAC-BS (GRE/NSP)
UP IP@ IWAC (GRE/NSP)
Management plane
1 CP IP@ VLAN/NSP)
Control plane
NSP1
NSP2
WAC
BS
NSPn
GRE/NSP (User plane)
VLAN /NSP
1 unique CP @/Bs
1 unique UP IP @

TMO18005
6.3.2 User Plane (BS-WAC)

All user plane IP packets whether originated from or sent to MS are tunneled over the
BS-WAC interface in a GRE/IP tunnel.

All the MS traffic is mapped onto a Service Flow on the air interface and encapsulated
by GRE tunnels between BS and WAC
One-To-One mapping for each unidirectional service flow, GRE key and CID.
While GRE key is added in the GRE extension field, BS-WAC tunnel is per NSP and per
SF based.
Data Plane
BS
WAC
GRE Tunnel
Outer IP
Header
GRE
Header
Inner IP
Header
Inner IP
Payload
GRE
Key
DSCP
GRE
Packet
DSCP
There is one separate tunnel endpoint IP address per NSP on WAC side, but one common
tunnel endpoint IP address for all NSPs on BS side.

TMO18005
6.3.3 Control Plane (BS-WAC)

Common Control Channel is the Signaling plane protocol between BS and WAC specific to
Alcatel-Lucent Solution, it is performed using TCP control links that are set up by the
BS with its Serving Wac .
Control
Interface
Base Station
TCP
Control
Interface
Control
Interface
Control
Interface
WAC
WAC
Serving
WAC
Cluster

TMO18005
6.3.4 BS-WAC Load balancing

Each WACU in a Cluster can serve MS managed by any BS in the cluster.

Each BS maintains R6 Control and Data path with each WACU in the cluster.
For each served MS BS maintains a notion of Serving WAC as part of MS context
BS forwarding MS request to a WAC:
If no MS context, the BS chooses a "Load Balancer" (Prefered) WACU in the WAC
cluster to forward initial MS request.

TMO18005
6.3.5 Control Plane (BS-WAC Load balancing )

Common Control Channel in the Load Balancing configuration is is performed using
TCP control links that are set up by the BS towards all the WACs of the cluster.

TMO18005

W4 release supports two R3 modes:
- R3 compliant mode and a R3 non compliant Mode.
The interfaces denoted as R3 are:
Home NSP
NAP
The interface with the AAA Server for users
authentication and accounting.
The interface with the HA for Mobile IP
procedure.
R3
ASN
CSN
The interface with the DHCP Server for users IP
connectivity management.
For managed services, an additional R3 interface
between the WAC Diameter Relay and the SBC is

to be supported for QoS handling (Gq interface).
Depending upon the Operator preferences, HA in this release can be

configured as Embedded in WAC or External (in CSN).

TMO18005
6.4 Interface R3 (WAC-Core Network) [cont.]

R3
DHCP/ DNS
AAA
RAN
WAC Serving
Embedded HA
External HA
SBC

TMO18005
6.4.1 External HA: Enhanced Legacy vs R3 Compliance
R3 compliant
- DHCP proxy or DHCP
relay
External HA
- HA IP@ from AAA
Enhanced Legacy
- DHCP relay
- DHCP server IP from OMC
- HA IP@ from DHCP server
- DHCP Relay or DHCP

Proxy
- HA IP@ assigned in
initial Serving WAC
- DHCP Relay
- HA IP@ assigned in initial
Serving WAC
Embedded
HA

TMO18005
6.4.1 R3 With AAA (RADIUS)

The AAA Framework provides the following services to WIMAX:
Authentication & Accounting services.
MS revocation list Support
On-Line Subscription & Hot Lining
MS IP address assigment (optionnaly)
DHCP security
Radius

TMO18005
6.4.1 R3 With AAA
6.4.1.1 Authentication, Authorization & Accounting

The AAA protocol is:
Client/Server Model in which WAC acts as RADIUS Client and AAA server acts as RADIUS Server
Radius protocol is transported over UDP/IP
The Alcatel-Lucent WiMAX solution uses AAA RADIUS server for :
The Authentication: Server Authentication (AAA server), Device Authentication, Subscriber
Authentication)
Download users QoS profiles into the WAC = Authorization
Tracking users activity and manage users sessions = Accounting
CPE
WAC

TMO18005
AAA Server
6.4.1 R3 With AAA
6.4.1.2 Radius Paket Format

A RADIUS packet is encapsulated in the UDP Data field, where the UDP Destination Port field indicates
1812 (decimal).
RADIUS Codes (decimal) are assigned according to the message type as follows:
1
2
3
4
5
11
12
13
255
Access-Request
Access-Accept
Access-Reject
Accounting-Request
Accounting-Response
Access-Challenge
Status-Server (experimental)
Status-Client (experimental)
Reserved

TMO18005
6.4.1 R3 With AAA
6.4.1.2 Radius Packet Format [cont.]

Radius Packet Exemple: Access Request
WAC
Access-Request
AAA
Dst Port
Code (1)= Access Request

Authenticator
Length
Attributes
EAP-Attribute

TMO18005

MIP Protocol is supported only when the Home Agent is a part of CSN (External HA).
MIP Protocol is not supported for Embedded Home Agent.
MIP Protocol is intended to enable mobile nodes to move from one location to another without
changing their IP addresses.
Alcatel-Lucent WiMAX solution supports only Proxy-MiP approach
MiP Tunnel 1
E
Ho xte
me rna
Ag l
en
t
CSN
CoA1
RAN
Foreign Agent
MiP Tunnel 2
CoA2
Foreign Agent
R3 MiP is not valid with Embedded HA
Home Agent (HA)

A router on a mobile node's home network which tunnels datagrams for delivery to the mobile node and maintains
current location information for the mobile node.
Foreign Agent (FA)

A router on a mobile node's visited network which provides routing services to the mobile node while registered.
The foreign agent de-tunnels and delivers datagrams to the mobile node that were tunneled by the mobile node's home
agent.
Home address
IP address received by the MSS from the DHCP (Local IP Address Allocation)
Care-of Address (CoA)

The termination point of a tunnel toward a mobile node, for datagrams forwarded to the mobile node while it is away
from home. It is the address of the serving WAC.

TMO18005
6.4.2.1 MiP Principle

The Home Agents scope
Intercepts packets from the corresponding node
Tunnels them toward the Foreign Agent
New IP header
Original IP Packet
@IP Source HA
@IP Care of address
@IP Corresponding Node
@IP Corresponding Node
Home @IP Mobile Node
Home @IP Mobile Node

CN
Payload
MN
RAN
HA
Tunnel
FA CoA

TMO18005
Payload
6.4.2.1 MiP Principle [cont.]

The update of the Binding Table is the scope of the FA
Binding table
Foreign
Agent (WAC)
10.31.3.1
1.1.1.7
Foreign
Agent (WAC)
New tunnel
Mobile
Node
CoA
1.1.1.7
1.1.1.7
1.1.1.8
1.1.1.5
10.31.1.1
10.31.2.1
10.31.2.1
10.31.3.1
10.31.2.1
Foreign
Agent (WAC)
1.1.1.7
Old tunnel
Home Agent
10.31.1.1

TMO18005
Corresponding Node
6.4.2.2 MiP Registration & Deregistration

Only 2 MIP messages used today :
MIP Registration request (Lifetime = 0 for de-registration)
MIP Registration Reply
MSS
BS
WAC/FA
DHCP Server
HA
MIP registration request

MIP registration reply
Ww
MSS
BS
WAC/FA
DHCP Server
HA
MIP registration request (lifetime = 0)

MIP registration reply (lifetime = 0)
Ww

TMO18005
6.4.2.2 MiP Registration & Deregistration [cont.]

MiP Packet Format:
Type=Registration Request
Registration Life Time =1h
Home Adress (MN IP@)
Home Agent IP@
CoA IP@

TMO18005
6.4.3 R3 with DHCP

RFC 2131/Runs over UDP ( ports 67/68)
Main DHCP messages:
dhcpdiscover, dhcpoffer , dhcprequest ,dhcpack.
IP Address Allocation Mechanisms
Static IP Addressing
Dynamic IP Addressing

TMO18005
6.4.4 DHCP Packet Format
HoA IP@
MS IP@
IP@ Offer
DHCP Server
IP@
DHCP Relay
IP@
CPE/MS MaC @
Option List

TMO18005
6.4.3 R3 with DHCP
6.4.3.1 DHCP Relay & DHCP Proxy

MS performs DHCP procedure to get a local IP address. The local IP address can be obtained with
DHCP relay or DHCP proxy in the WAC.
1- DHCP Relay Mode: DHCP relay may add information before relaying DHCP messages that are taken
into account by DHCP server when returning MS IP@ and DHCP options:
Options value 68 in option 55 : In case of External HA.
Option 82/1 : In case of Embedded HA, WAC inserts the DHCP Relay Agent option set to a value that
identifies the WAC .

Option 82/1 : Also used in case of external HA and IP @ of HA allocated by the AAA.
2- DHCP Proxy Mode:

WAC terminates the DHCP protocol , so behaves as DHCP server towards MS and MS IP@ assigned by AAA
or by HA

TMO18005
6.4.4 R3 With SBC (Gq Interface)

In Alcatel-Lucent WiMAX network, Diameter protocol is used for QoS management.

It is involved in all VoIP, VoD, Live TV channel, and all applications with QoS.
Diameter is implemented between The WAC and the SBC (P-CSCF).
For HSI service, Diameter is not involved.
SIP_INVITE(SDP)
Call Set Up Request

RAN
R6
WAC
Serving
WAC
DR
User Profiles
R1
User Profiles

TMO18005
R3
Gq
Diameter
SBC
6.4.4 R3 With SBC (QoS Management)
6.4.4.1 Diameter Protocol: QoS Management

SBC translates and maps the SDP parameters into service information
SBC sends the service information to the WAC for authorization in the appropriate AAR
command
<AAR> = < Diameter Header: 265, REQ, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
[ Media-Component-Description ]
CPE1
CPE2
WAC
SBC
INVITE (Session1)
AAR (Session 1)
AAA (Session 1)
<AAA> = < Diameter Header: 265, PXY >

< Session-Id >
{ Auth-Application-Id }
{ Origin-Host }
{ Origin-Realm }
[ Result Code ]
[ Experimental Result ]
INVITE (Session2)
AAR (Session 2)
AAA (Session 2)
Bye (Session1)
STR (Session 1)
STA (Session 1)

TMO18005
6.4.4 R3 With SBC (QoS Management)
6.4.4.2 Diameter Protocol: QoS Management [cont.]

Diameter Messages exchanged over Gq Interface:
Command
Description
Code
CER
Capabilities Exchange Request
257
CEA
Capabilities Exchange Answer
257
AAR
AA Request
265
AAA
AA Answer
265
ASR
Abort Session Request
274
ASA
Abort Session Answer
274
DWR
Device Watchdog Request
280
DWA
Device Watchdog Answer
280
STR
Session Termination Request
275
STA
Session Termination Answer
275
DPR
Disconnect Peer Request
282
DPA
Disconnect Peer Answer
282
Details
Activation of Diameter connection between SBC and WAC
QoS resource authorization request/answer for the session
Termination of the session after the SIP BYE, resources

previously allocated are released
Messages used over the diameter connection to detect
transport failures
Termination of the session (e.g after SIP BYE), resources
previously allocated are released
Deactivation of the Diameter connection triggered by the
WAC in case of reconfiguration of the SBC

TMO18005
6.5 Interface R4 (WAC-WAC interface)

Two kinds of interfaces R4 exist:
1- The interface between two adjacent WACs called inter-WAC interface
2- The interface between WAC units within the same WAC cluster.
The interfaces denoted as R4 are:
For mobility: interface between Serving WAC unit and Target WAC unit
For idle mode: interface between WAC supporting Paging Controller and Target WAC
For managed services (VoIP, VoD, etc): interface between WAC Diameter Relay and
Serving WAC.
For intra-cluster interface (Load Balancing of BS into WAC cluster): interface between
Load Balancer WAC and Serving WAC unit

TMO18005
7 Initial Network Entry and IP Service

Establishment.

TMO18005
7 Initial Network Entry and IP Service Establishment.

Ww
CPE
BS
WAC
AAA
DHCP
Ext
HA
DR
ND& S + ASN Connection Set Up *

Access Authentication and Authorization
IP Service Establishment & First MiP Registration
Diameter Relay Registration
Accounting
Second MiP Registration
HSI Service Establishement

TMO18005
ASP
7.1.1 ASN Connection Setup

MS performs cell selection, NSP discovery and network attachment.
CPE
BS
Ww
R6
WAC
Scanning and synchronisation

WAC units runs the load sharing algorithm
and selects the Serving WAC unit in the
cluster to handle the MS.
DL-MAP, DCD, UCD, UL-MAP
Network Discovery
and Selection
ND&S
RNG REQ_ MS MAC@

RNG RES_Basic & primary management CIDs
SBC REQ (Basics Capabilities)
SBC RES
BS Selects
prefered WAC
SS Associated-Ind (MS-MAC@)
Ranging cause=NW_ENTRY
SS Associated-res (MS-MAC@ UP-T W-Adress-list)
Upon installation, an MSS begins scanning its frequency list to find an operating channel. The MSS tries to
synchronize to the downlink transmission by detecting the periodic frame preambles. Once the physical
layer is synchronized, the MSS will look for the periodically broadcast Downlink Coding Descriptor (DCD) and
Uplink Coding Descriptor (UCD) messages.
Upon learning what parameters to use for its initial ranging transmissions, the MSS will look for initial
ranging opportunities by scanning the Uplink-MAP messages present in every frame. The MSS chooses an
initial ranging slot to send a ranging request message.
The response also provides the MSS with the basic and primary management CIDs.
To avoid wasting capacity, the MSS next reports its PHY capabilities, including the modulation and coding
schemes it supports. The BS, in its response, can deny or accept the use of any capability reported by the
MSS.

TMO18005
7.1.2 Access Authentication and Authorization

After successful completion of access authentication:
WAC Anchor-Authentication retrieves the keying material contained in the RADIUS message, and
then send them to BS.
The NSP ID is provided to the BS.
Upon receiving message MSS-Set_AK-Req, the BS starts the keying materials exchange procedure
with the MSS
BS indicate to WAC the Key exchange result (message MSS_Set_AK-Cnf)

MS sends REG-REQ message to register with the BS
CPE
Ww
BS
R6
WAC
Authentication & authorisation
R3
AAA
Radius Access Accept
SS_Set_AK-Req(MS MAC@, AK context, NSP ID)

PKM : Key exchange
SS_Set_AK-Cnf
REG-Req
REG-Res
Each MSS contains both a manufacturer-issued factory-installed X.509 digital certificate and the
certificate of the manufacturer. The network is able to verify the identity of the MSS by checking
the certificates and can subsequently check the level of authorization of the MSS. If the MSS is authorized
to join the network, the BS will respond to its request with an Authorization Reply containing an
Authorization Key (AK). Upon successful authorization, the MSS will register with the network.

TMO18005
7.1.3 IP @ Assignment & Initial Service Establishment

Initial Service flow creation:
After a successful registration, the BS creates and activates the initial Service flows which purpose is to
allow the MSS to exchange DHCP signaling
WAC Anchor-Authenticator for it establishes the Initial

Service Flow using the VSAs retrieved from the AAA server
CPE
BS
Ww
R6
WAC
SS_SF_Request (Type=Addition, SFID, QoS

parameters UL& DL)
DSA, QoS Parameters, CiD, Classifiers
SS_SF_Cnf (SFID
After registration, the MSS attains an IP address via DHCP and establishes the time of day via the Internet
Time Protocol (NTP server).

TMO18005
7.1.3 IP @ Assignment & Initial Service Establishment [cont.]

DHCP Relay:
MS IP@ Offer
DHCP Server
MS IP@ ??
Legacy
AAA
WAC (DHCP-RELAY)
HA
DHCP Proxy:
No DHCP Server
MS IP@ ??
MS IP@ Radius VSA

Compliant
AAA
WAC (DHCP-Proxy)
HA
MS IP@ MiP Registration


TMO18005
7.1.3 IP Service Establishement
7.1.3.1 DHCP (Relay Case)

The WAC acts as the DHCP relay:
CPE
Ww
BS
R6
WAC
(DHCP Relay)
DHCP
Server
R3
External HA
PCS_PDU(DHCP DISCOVER)
Initial SF
DHCP Server IP@ is

known by the WAC:
GRE (DHCP DISCOVER)
IP Destination@ set to
255.255.255.255
(DHCP DISCOVER)
-OMC configuration
-AAA VSA
(DHCP OFFER)+ HAIP@

GRE (DHCP OFFER)
PCS_PDU(DHCP OFFER)
- Change IP@ Dst from

Broadcast to unicast
- + GIADDR
PCS_PDU(DHCP REQUEST)
GRE (DHCP REQUEST)
1st MiP Registration

(DHCP REQUEST)
(DHCP ACK)
GRE (DHCP ACK)
PCS_PDU (DHCP ACK)

TMO18005
7.1.3 IP Service Establishement
7.1.3.2 DHCP (Proxy Case)

At this point, based upon the absence of DHCP server IP address, WAC decides to use DHCP Proxy Mode.
CPE
Ww
BS
R6
WAC
DHCP Proxy
AAA
External HA
Radius Acces Accept
Initial SF
PCS_PDU(DHCP DISCOVER)
R3
HA IP@, MIP security keys and attributes,

Optionnaly: DNS IP@&SBC IP@(P-cscf)
GRE (DHCP DISCOVER)
MS IP@ (HoA)
IP Destination@ set to
255.255.255.255
PCS_PDU(DHCP OFFER)
1st MiP Registration

GRE (DHCP OFFER)
MS IP@ as obtained by HA
DHCP Offer=DHCP request ??
PCS_PDU(DHCP REQUEST)
GRE (DHCP REQUEST)
GRE (DHCP ACK)
No DHCP Server
PCS_PDU (DHCP ACK)

TMO18005
7.1.5 Accounting
WAC starts to record the duration of the session (HSI), input and output octets, or input and output
packets of the user.
CPE
Ww
BS
R6
WAC
(ASN Anchor)
R3
AAA
AccountingStart (beginning of the session=True,

Acct-Session-Id, NAS-IP-Address, NAS-Port, Acct-Status)
User session begins
Accounting Response
2nd MiP Registration
WAC performs the second MIP registration shortly

after the first successful registration.
HSI Service Establishement

TMO18005
HA
8 End to End Scenarios

TMO18005
8. End to End Scenario
8.1 Network Entry & Initialization

MS
BS
WAC
AAA
DHCP
Radio entry
Scan, DL/UL
Parameters
Mutual Authentication via EAP
Registration
Local IP address allocation
Service Flow
Creation
MIP registration
Accounting start
SIP Registration
VoIP Call Setup

TMO18005
HA
HSI
8.2 Discover: Sip Registration

When the CPE is connected, the SIP agent performs the SIP registration to indicates
its presence on the network to the IMS.
MS
BS
WAC
AAA
DHCP
HA
SBC
IMS
SIP Request: Register

SIP Request: Register
SIP OK
SIP OK

TMO18005
8.3 Discover: VoIP call

Try to complete the call flow for E2E WiMAXs user SIP call:
MS-1
MS-2
BS
WAC
DHCP
HA

TMO18005
SBC
Softswitch
8.4 Discover: VoIP Call Release & QoS

Based on the previous call flow, try to complete the following one for VoIP call release:
MS-1
MS-2
BS
WAC
DHCP
HA

TMO18005
SBC
Softswitch
8.5 Video Streaming Session Setup (Service Discovery)
MSS
BS
WAC
Diameter
Relay WAC
SBC
Video Streaming
server
1
HTTP Get (HTTP_url, HTTP_headers)
HTTP Get (HTTP_url, HTTP_headers)

2
User Authentication
HTTP 200 OK (rtsp_url,CONF_ID, UID)
HTTP 200 OK (rtsp url,CONF ID, UID)

TMO18005
8.5 Video Streaming Session Setup: First Part

MSS
BS
Diameter
Relay WAC
WAC
SBC
Video Streaming Server
1
RTSP DESCRIBE (rtsp url,Accept:Application/sdp)
RTSP 200 OK (SDP information

RTSP 200 OK ( RtspSessionID,SDP information)
SBC store SDP information
RTSP SETUP(rtsp url, RtspSessionID,stream_ID, parameter list)

SBC store client seting
for parameters
RTSP SETUP(rtsp url, RtspSessionID,
stream_ID, parameter list)
RTSP 200 OK ( RtspSessionID)
RTSP SETUP(rtsp url, RtspSessionID,stream_ID, parameter list)
SBC store client Seting for
parameters
RTSP SETUP(rtsp url,RtspSessionID,
stream_ID, parameter list)
RTSP Play (rtsp url, RtspSessionID,Range)

TMO18005
8.5 Video Streaming Session Setup: QoS and Second Part

MSS
BS
WAC
Diameter
Relay WAC
SBC
Video Streaming Server
DIAMETER:AAR(Service
Information for Audio and Video)
DIAMETER:AAR(Service
Information for Audio and Video)
SS-SF-Req(MS MAC,SF-ReqType=ADDITION, SFlist)
Service flow creation for
Audio and Video
SS-SF-Cnf(MS MAC@,
Service Flow Results
DIAMETER:AAA(success)
DIAMETER:AAA(success)
RTSP PLAY(rtsp url, RtspSessionID,Range)
RTSP 200 OK ( RtspSessionID,Range,RTP-Info)
RTSP 200 OK ( RtspSessionID,Range, RTP-Info)

TMO18005
9 Mobility

TMO18005
9 Mobility

Intra WAC handover
Handover between base stations keeping the same WAC as anchor point
No change of Mobile IP Foreign Agent (FA)
Inter WAC handover
Handover between base stations leading to a change of WAC

Requires a binding update with the Home Agent (HA)
BS
WAC
(proxy M IP/ FA)
BS
IMS
HA
802.1 6e
Corporate
Internet
BS
WAC
(proxy M IP/ FA)
Seamless handover
intra WAC
inter WAC

TMO18005
HA: Home Agent

FA: Foreign Agent
9.1.1 The Proxy Mobile IP Approach

WiMAX mobility solution based on Proxy Mobile IP:
The Mobile IP client is located in the WAC
Compliant to WiMAX Forum which defines both Proxy Mobile IP and Client Mobile IP
Mobile IP Approach defines 3 functional elements:
The Home Agent which manages the WiMAX terminal IP@.
The node communicating with the WiMAX terminal only knows the WiMAX terminal
IP@ managed by the HA. All traffic to/from the WiMAX terminal converge to the HA.
The Foreign Agent located in the WiMAX RAN (i.e. in the WAC). All traffic to/from
the WiMAX terminal is tunneled between the HA and FA.

The Mobile IP client in charge of updating the HA <-> FA tunnel when the WiMAX
terminal moves from one FA to another (i.e. from one WAC to another).

TMO18005
9 Mobility
9.2 Intra WAC Hand Over

Intra WAC handover is based on 4 functional
steps:
WAC
Cell reselection (scanning)

Scanning neighbors
Handover initiation & preparation
Mob-msho-req (BSs list)
Handover execution
ho req (BSs list)
MSS disconnected from the network
ho req
Network re-entry
After this step MSS can send/receive
ho rsp
packets to/from network

Mob-bsho-rsp (BS)
ho rsp (BS)
Mob-ho-ind (BS)
Network re-entry
Handover is MS initiated network controlled
Cell reselection

TMO18005
HO initiation
& preparation
9 Mobility
9.3 MiP Operation

Handover between base stations leading to a change of WAC
As the WAC (FA) changes, a binding update with the Home Agent (HA) is required to
update L3 routing
WAC-1
(proxy M IP)
802.1 6e
HA
WiMAX RAN
Macro mobility
WAC-2
(proxy M IP)

TMO18005
9.3 MiP Operation
9.3.1 Inter WAC Hand Over with External HA

At Initial Network Entry
WAC gets required information allowing to perform Mobile IP registration (e.g. Home
Agent IP @)
WAC performs the Mobile IP registration on behalf of the MS. This is transparent to the
MS.
binding : CoA (IP@ of the FA in the WAC) and MS IP@ done in HA
1) IP@ acquisition
2) IP@ acquisition
3) MIP RRQ / RSP
4) ACK
DHCP
server
WAC-1
(PMIP)
802.1 6e
HA
WiMAX RAN
Macro mobility
WAC-2
(PMIP)

TMO18005
Core Network
9.3 MiP Operation
9.3.1 Inter WAC Hand Over with External HA [cont.]

During inter WAC handover:
MIP related information (e.g. HA IP@) are provided by serving WAC to target WAC.
Target WAC has all information to perform MIP registration

Inter-WAC tunnel created to continue to send/receive traffic to/from MS
HA
WAC-1
HA
HA
WAC-2
WAC-1
WAC-2
WAC-1

TMO18005
WAC-2
9 Mobility

Mechanism & Principles of Idle Mode feature:

After a period (configurable) of inactivity the MS enters in Idle Mode

Idle mode is a state allowing a MS, which is inactive, to conserve power and operational resources
by restricting MS activity to scanning at discrete intervals.
The MS has no more bindings with the BS (Service Flows, CIDs), therefore, the resources
can be re-used by other MSs The MS is still reachable for the outside IP world. Its context is still
alive in the WAC & HA, therefore IP traffic can be sent to the MS.
When DL traffic has to be delivered to the MS, the BS pages the MS. MS will go through a Network
Entry procedure and re-attach to the BS.
If the MS needs to send data in UL, it will go through a Network Entry procedure and re-attach to
the BS MS in idle mode is managed by a Paging Controller located in the WAC.

TMO18005
9 Mobility
9.4 Idle Mode & Paging [cont.]

Role of the MS when in idle mode:
Periodically listen to paging messages broadcast by the Paging Controller to know if
there are pending data for this MS in the network (If any, the MS re-enters the
network)
Periodically refresh MS context lifetime stored in the Paging Controller
Periodically listen to paging information broadcast by the network in order to know if
the MS has moved to another Paging Group
Role of the Paging Controller:
Keeps track of MS location while in idle mode to know in which paging group the MS is
Stores MS context for MS in idle mode
Notifies MS in idle mode of incoming IP packets
Paging:
When PC receives a downlink packet towards an IDLE MS, it first checks the current PG
of the MS. PC can initiate Paging procedure to all the BSs of the Cluster which belong
to the PG via R6 interface.
Location Update:
LU MAY be either Secure or Unsecure

TMO18005
9.4.2 Idle Mode Principle In BS Load Balancing

Each WAC unit can manage all the BSs belonging to the Cluster.
Each WAC Unit can manage all the PGs of the BSs in the Cluster.
The BSs controlled by the WAC units from the same cluster can be divided into different
PGs.
BS association with a particular PG within a cluster is done via OMC-R.

TMO18005

TMO18005
10.1 WiMAX Security Methods

The possible combination for the authentication in W4 are:
User and server authentication via EAP-AKA or EAP-SIM.

This is already supported in W3 and the mutual authentication occurs by the very
nature of the shared secrets used for these authentication schemes.
User and server authentication via EAP-TTLS with CHAP or MS-CHAPv2.

Server authentication is already supported in W3 as part of the EAP-TTLS protocol.
User, server and device authentication via EAP-TTLS with CHAP or MS-CHAPv2.
Device authentication as part of the EAP-TTLS exchange is new in W4.
Server and device authentication via EAP-TLS
Support for plain EAP-TLS is new to W4. This combination performs both server and
device authentication using X.509 certificates

TMO18005
10.2 WiMAX Security Protocol Stack

CHAP
User authentication
CHAP
TTLS AAA server & Device authentication with X.509 certificate

TLS
TLS
Mutual Authentication through EAP-TTLS

EAPTTLS
EAPTTLS
EAP
EAP
PKM
PKM
16e MAC
16e MAC
16e PHY
MSS
EAP
RADIUS
EAP
RADIUS
RADIUS
or
DIAMETER
RADIUS
or
DIAMETER
BS/WAC
control
BS/WAC
control
TCP
TCP
UDP
UDP
UDP
UDP
IP
IP
IP
IP
IP
IP
L2/L1
L2/L1
L2/L1
L2/L1
L2/L1
L2/L1
16e PHY
BS
WAC

TMO18005
TTLS AAA Server
HomeAAA
Server
10.3 WiMAX Standard Security Sublayers

A dedicated security layer is defined in WiMAX standard, to provide privacy to subscribers
and strong protection to operators.

TMO18005
10.4 EAP-TTLS & X.509 Certificate

X.509 Certificates:
Asymmetric keys principleA public
identity card, containing the information of the owner and its public key.
The certificate is signed by the private key of a Certification Authority (CA), a
trustworthy third partyIdentity of peer is verified if the certificate decrypted with
CA public key gives readable informations.
EAP-TTLS:
Peer and AAA server negotiate an authentication method in EAP messages : EAP-TTLS,
EAP-SIM, EAP-AKA, there are several uses of EAP-TTLS :
EAP-TTLS as an native authentication protocol, using digital certificates to
authenticate the server on peer side.
EAP-TTLS as an encrypted tunnel to secure other protocol exchanges to
authenticate user and/or device
EAP-TTLS as protocol to exchange key materials
EAP-TTLS as a way to negotiate encryption method
The TTLS AAA server holds a X.509 certificate and presents it to the peer for
authentication.

TMO18005
10.5 Security Mechanisms & Protocols : CHAP

CHAP stands for Challenge Handshake Authentication Protocol.
CHAP uses a three way handshake mechanism :
The AAA server sends to the client a counter and a 16 octets challenge.
The client hashes the number, the counter and the shared secret and sends back
the result to the AAA server

The AAA server compares its local result and the result of the client and, if similar,
grants the access.

The verification is based on a shared secret : the user's password.
In this release CHAP is this only inner authentication method used over EAP-TTLS.
The real username of the user is used in CHAP, and the association username/password is stored in AAA server.

TMO18005
MSS
WAC
TTLS Server
AAA Server
TLS Handshake Phase

Identity Exchange phase
Hello Exchange phase
Finished Exchange phase
TLS Tunnel Phase

CHAP authentication phase
EAP messages are exchanged between MSS and TTLS AAA server in each direction. They are transparently
relayed by BS and WAC.
The WAC initiates the EAP authentication exchanges by sending an EAP Request / Identity to the MSS via the
Base Station. Subsequent EAP messages are relayed by the WAC.
The TLS layer authenticates the homeTTLS/AAA server to the MSS and builds a secure MSS-AAA Server tunnel for
subsequent MSS authentication using CHAP.

TMO18005
10.6.1 Identity Exchange Phase
MSS
WAC
AAA Server
EAP-Request / Indentity
EAP-Response / Indentity
The identity contains the realm
Check Realm
EAP-Request / TTLS Start

TMO18005
10.6.2 Hello Exchange Phase

MSS
AAA Server
EAP-Response / Client Hello

client version, random number, session
ID, ciphersuite, compression methods
EAP-Request / Server Hello
Verify the server

Certificate
server version, random number, session ID, ciphersuite,

compression alg, Certificate of server [TLS Certificate
Request], Server Hello Done, ServerKeyExchange,
ServerHelloDone
Trigger: Radius Access Request/EAP-Response/Identity

Normal case: TTLS server sends an EAP-Request/TTLS-Start message.

TMO18005
10.6.3 Finished Exchange Phase
MSS
AAA Server
Compute
pre master secret
EAP-Response / ClientKeyExChange
pre master encrypted, Rsp([Certificate],
ClientKeyExchange TLS record, ChangeCipherSpec,

TMO18005
Compute
pre master secret
10.6.4 Chap Authentication Phase
MSS
AAA Server
EAP-Request
EAP-Response / TTLS / CHAP message

Username, user password

TMO18005
10.7 Authentication Successful

MSS
WAC
AAA Server
EAP-sucess
The MS directly sends the CHAP challenge response to the AAA server, as the challenge used is
calculated with the master key.
At the end of CHAP authentication, the TTLS AAA server sends an EAP-success message to the MS.
This message is encapsulated in an EAP-Access-Accept message, sent to the WAC and relayed to
the MS.
This message also contains key materials : Master Secret Key (MSK), derived from master secret,
is sent encrypted in RADIUS attributes.

TMO18005
10.8 EAP SIM/AKA Methods

EAP-SIM
This authentication mechanism has been originally defined for the GSM
mobile system. It uses a SIM card (Subscriber Identity Module). Client and
Server share a predefined secret key.
EAP-AKA
This authentication mechanism has been originally defined for the UMTS
mobile system. It uses a SIM card (Subscriber Identity Module). Client and
Server share a predefined secret key.
Allows 2G/3G operators to deploy WIMAX while keeping their existing

authentication infrastructure (SIM cards, HLR)

TMO18005
10.9 Key Materials

Security on air interface
On control plane
Integrity of messages and Identity of peer are verified through authentication
method based on CMAC algorithm and key derived from EAP authentication phase
On user plane
Encryption and integrity of MAC messages are assumed by the use of an encryption
method and key named TEK
The transfer of TEK on the control plane from BS to MS is realized thanks to encryption
with the KEK key.
Key derivation from previous MSK ( elaborated during users authentication phase)
and distribution of key materials in order to secure the exchange of data on the air
interface.

TMO18005
10.10 Key Materials Distribution

Key derivation from MSK
BS
MS
MSK
512 bits
WAC
MSK
512 bits
EAP authentication
MSK
512 bits
AK
160 bits
AK
160 bits
KEK
KEK
TEK
TEK
KEK : Key Encryption Key

Used to secure the exchange of TEK over the control
plane.
TEK : Traffic Encryption Key
Used to authenticate and encrypt users data traffic
TEK is sent from BS to MSS encrypted by means of KEK.
TEK are randomly generated by the BS.

TMO18005
AAA
server
AK
160 bits
RADIUS
10.10 Key materials distribution [cont.]

MSK (512)
Trunked
PMK (160)
Dot16KDF (PMK, SSID, BSID , #)
AK (160)
Dot16KDF (AK, SSID, BSID, #)
CMAC-Key-UL
(128)
CMAC-Key-DL
(128)
MSK: Master Session Key
PMK: Pair wise Master Key
AK: Authentication Key
SSID: SS Identity (MAC@)
BSID: BS Identity
MAC: Message Authentication Code
CMAC: Cipher-based MAC
UL/DL: Uplink /Downlink
KEK: Key Encryption Key
TEK: Traffic Encryption Key
#: Dot16KDF operation identifier
KEK (128)
TEK (128)
{KEK, TEK}
protected by KEK

TMO18005
10.10 OMC and NE Access Security

Use of secured protocol SNMPv3, all transactions between OMC-R , WAC and BS are encrypted and
authenticated:
Parameters setting
counters polling
Alarms management
Use of SSL between WAC and OMC (authentication and encrypted tunnel to transfer data for an HTTP
session):
o
o
WAC OMC authenticate each other through X.509v3 certificate

LMT, NEMW are authenticated by user/password on WAC, by certificate on user side
Use of SSH2 to connect on NE (BS and WAC) (ensure authentication and encryption):
WAC
o SSH
o SSH
BS
o SSH
o SSH
client always uses username/password

server authenticates through X.509v3 certificate
client always uses username/password
server authenticates through raw public key (initiated by the OMC)
Use of SFTP for code transfer (ensure authentication and encryption)

TMO18005

TMO18005
11.1 Accounting & Charging Scenarios

In WiMAX Alcatel-Lucent Solution, the ASN supports Off Line Accounting, On line
Accounting (Post-Paid and Pre-Paid) and hotlining for Direct IP access (Internet Access)
only,
The ASP supports accounting for VoIP, VoD, and other services if any.
OFF Line:
ON Line:
A charging process where charging

information does not affect, in
real-time, the service rendered.
A charging process where charging

information can affect, in real-time, the
service rendered and therefore directly
interacts with the session/service
control.
Online subscription feature : also called Over the Air (OTA) provisioning
It permits a future WiMAX user to register on the WiMAX RAN
Same approach as self registration on WiFI hotspots
Pre-Payment feature ( On line accounting)

Pre-paid : capability to handle sessions based on the consumption of a pre-existing credit managed by a PrePaid Server (PPS)
Account Refilling feature

Redirection rules for in order to connect users to a Web portal
Hot lining for on line subscription when AAA detects an unknown user
Hot lining for on line replenishment (or account refilling) : triggered by AAA when PPS detects that credit
limit is reached.
Refill capability both at network entry or during session ( expiration of credit)
Note: Pre-paid option can be used on a WiMAX RAN without Online subscription. But Online Subscription usage implies also Pre-paid option for
the self registered users

TMO18005

The WiMAX RAN provides access to the High Speed Internet Service (HSI).
The PPC function for HSI is located in the WAC.

The interface between PPS and AAA interface is used to provide online accounting for High Speed
Internet (HSI) service.
PPC for HSI

Service
PPC for Other

Services
Transport
Network
Instant Convergent Charging (ICC)

Diameter
PPS
Vital AAA
ICC DB
Diameter
WAC
DB
Web Portal
SOAP/ HTTP
Voucher DB
The other PPC for VoIP and VoD services are located in the CSN. DCC interface is also used
between PPS and PCC at CSN.
Online Subscription is also called Over The Air (OTA) provisioning. Online Subscription feature permits a
future WiMAX user to register himself/herself on the WiMAX RAN. This is the same approach in WiMAX
than for WiFi users self registration on WiFi Hotspots.Feature goal:
To allow a user, which purchases a WiMAX capable device, to subscribe to WiMAX services directly from its device to any
provider.
The WiMAX service provider, chosen by the customer, shall offer solution to provision a new user account and to provision and
configure the user device
Additional online procedures: account modification by the user, account deletion (operator,automatic)
W4 assumptions
- Online subscription only for prepaid user
- Only concerns High Speed Internet service
- W4.1: payment using voucher (scratch card)
- future: payment using CB
W4 restrictions
- In W4, the terminal configuration is done by user: no bootstrapping and provisioning over the air
- In W4, no online subscription modification
- In W4, online subscription deletion done manually by the operator on each server (PPS, AAA)

TMO18005
11.2.1 Web-Portal/Provisioning Server

Web-Portal/Provisioning server is the main functional block within ICC (Instant
Convergent Charging)
Web-Portal/Provisioning server has three external interfaces:
Web-browser based GUI interface.

SOAP/HTTP interface between Web-Portal and AAA server.

Payment checking interface between
Instant Convergent Charging (ICC)
Web-Portal and Voucher database.
Vital AAA
PPS
ICC DB
Diameter
DB
SOAP/ HTTP
Web Portal
HTTPS
Voucher DB

TMO18005
11.2.2 Pre-paid Architectural Model

For Online Subscription OTA service, Pre-paid accounting is most of the time used.
Prepaid mode is the capability to handle user sessions based on the consumption of a pre-
existing credit defined in a Prepaid Server.

The Prepaid mode uses the Hotlining feature to enable users to refill their account when it is
depleted.
ASN-GW
Prepaid attributes
User Device
Prepaid Client
RADIUS
Client
RADIUS
Prepaid Server
RADIUS
Server
Diameter
User Plane
FA
HA
IPIPservices
services
When the credit expires, the session is ended. When the session ends before credit expires,
the unused credit is given back to the Prepaid Server
On-line accounting mainly involves two entities: the Prepaid Client (PPC), and the Prepaid Server (PPS)
The PPC
dialogs with AAA and PPS for the prepaid accounting authorization
Monitors the provision of the per-paid according to quota allocated by PPS
The PPS
Manages the accounts of the pre-paid users
Allocated the quota per service

TMO18005
11.2.3 ALU Pre-paid Architecture

The ALU architecture distributes the Prepaid Client over the ASN and the CSN depending on the
different services.
The WiMAX RAN provides one unique service: High Speed Internet access service.
The other services like VoIP or Video are provided by the CSN / Core networks.
Home-CSN
PPC
for VoIP
Dia
me
ter
MS
PPC for
Internet Access
Service
Radius
Home-AAA Transl.
Server
Agent
Diameter
ter
me
a
i
D
PPC
for VoD, ...
ASN

TMO18005
Pre-Paid
Server
Online
Charging
Server
HLA
11.2.4 Hotlining Architectural Model

The Prepaid mode uses the Hotlining feature to enable user to refill their account when it is
depleted.
The refill capability is available both at Network Entry and during a session.
During Hotlining, the user can only access to the User account refill web page presented by the
the NSP Web Portal.

ASN
Radius
MS
HLD
H- AAA
HTTP/ HTTPs traffic
Diameter
PPS
(OCS)
HLA
The Prepaid mode uses the Hotlining feature to enable user to refill their account when it is depleted. This refill
capability is available both at Network Entry (no initial) and during a session (credit has exhausted). During
hotlining, the user can only access to the User account refill web page presented by the the NSP Web Portal.
HLA
The Hot-Line Application is a functional entity that performs the following roles:
Initiates notification of the Hot-Line status to the MS. This is done via a delivery of an
HTML page to the subscribers browser.
Provides a mechanism for the user to rectify the issue that triggered Hot-Lining (Web Page).
Terminates the user's packet data session upon unsuccessful resolution of the problem.
HLD
A Hot-Lining Device (HLD) implements the Hot-Lining rules requested by the Home AAA server for a
user. All User Plane packets of a hot-lined user are checked against the Hot-Lining rules and when a
match is found the corresponding action (permit, deny, or redirect) is performed by the HLD.
PPS/OCS
Communicates with the AAA (Diameter Credit Control)
Maintains the user account balance.
Serves requests issued by the PPC for allocation of user quota.
Associates every allocated quota with a Validity-Time (VT). The CSN operator configures VT
on a per service basis. Should the PPC loose the prepaid context of a user (PPC reset) the
allocated quota is moved back to the user account on VT expiry.

TMO18005
11.2.5 Online Subscription Architectural Model

The different NEs involved in an online subscription procedure are:
The MS
The BS and the ASN-GW(WAC) in the ASN
The AAA, Authentication Authorization ans Accounting server
The Subscription Web Portal/Provisioning server: (Web-Portal/Provisioning server is the main
functional block)

An unknown Wimax user connects to the Wimax network

As it is undeclared in the AAA server, the user is redirected to the IP address of a Web Portal offering Online
subscription facility
During the Online subscription, the user performs:
-
QoS/service profile selection
A NAI and pasword is provided to the user
Credit filling with a scratch card (Voucher)
At the end of the Online subscription:

-
Subscriber/Account creation
The user is declared in the AAA server
The user is informed that it has to reconnect to Wimax in order to access the service (normal entry phase)

TMO18005
11.2.6 Pre-Provisioning Phase

CPE
Ww
BS
WAC/HLD
NSPAAA/
HLA
DHCPServer
Network Discovery & Selection

Access Request (NAI, EAP idenity, Wimax
Capabilities)
Mutual Authentication & Authorization
Access Accept (AAA sessionID, EAP Success,
HOTLining Attributes, SF data, session time,
termination action)
PKM Exchange
MS IP @ Allocation
Filtering and Redirection
initiation
IP redirection rule: It is a set of IP

filter rules Giving the Action to
perform.
SF creation
Accounting Start (NAI, SessionID,
MS mac@, Class, HOTLINE
indication)
Pre-provisioning phase
1- ASN access: scanning,
radio synchronisation,
NSP discovery and selection
2- Authentication
3- Pre-provisioned subscription service flow creation.
Hot-lined session: user flow re-directed to the Subscription Web Portal => only a limited access is authorized

TMO18005
11.2.7 Subscription Phase

CPE
Ww
BS
NSPAAA/
HLA
WAC
HTTP get request (from User Home Page)

HTTP redirection
HTTP 404 (Page not found, please access the following URL
to subscribe to the service provider network)
HTTP get request (Open Welcome Page to Subscription Web Portal )
HTTP get answer (Open Welcome Page to Subscription Web Portal )
HTTPS post: ordering subscription and accounting selection)
User subscription information acquisition
Subscription phase
4a- User confidential data requested to create an account through a secured connection
4b- User subscription creation authorized: voucher validity checked
4c- User account creation on AAA and PPS

TMO18005
NSP Web
Portal/ PS
11.2.7 Subscription Phase [cont.]

CPE
Ww
BS
NSPAAA/
WAC
Welcome to on-line subscription page of XXX

HLA Operator
To get a Wimax account, you must have bought a
"XXXPage)
Wimax voucher" in our distribution network
HTTP get request (from User Home
Please enter the required infomation to allow us to create your
new account:
NSP Web
Portal/ PS
HTTP redirection
oYour first name:
oYour Last name:
HTTP 404 (Page not found,

please
access number:
the following URL
oYour
voucher
oYour MAC address:

HTTP get request (Open Welcome Page to Subscription Web Portal )
oPassword
oConfirm
HTTPpassword
get request (Open Welcome Page to Subscription
A description of each
possible subscription is
provided,
inlcuding
Web
Portal
) :
cost, bandwith, et .. la
duration in min
Service selection
256
768
1500

OK
Cancel
- Behavior on request of an unknown page (user traffic IP re-direction consequence)

-
In a return NOK(404): The associated message recommend to access the proposed URL (several could be
proposed for several device format) in order to be authorized to access the service.
- Interfaces with the user through an HTTPS interface with HTML format
-
To get user information needed to create the account through a secured connection
To provide the account creation result to the user:

-
data are provided to the user to allow him to perform a subsequent initial network entry (NAI, url/pwd)
The user is also informed that, in order to achieve his subscription he has:
- To disconnect from the WiMAX network
- To follow the instructions (get when he buys the voucher or that he will receive) to configure his device
- To re-enters the WiMAX network to access the subscribed HSI service
- Authorizes or not the user account creation: check voucher validity

- Interfaces with other servers (AAA,PPS) that need a to create the user account in their own database.

TMO18005

CPE
Ww
BS
NSPAAA/
WAC
Welcome to on-line subscription page of XXX

HLA Operator
To get a Please
Wimax validate
account,your
you subscription
must have bought a
Please print
this
page
"XXX Page)
Wimax voucher"
in our
distribution
network
HTTP get request (from User Home
Please enter the required infomation to allow us to create your
new account:
oYour first name:
xxxxxxxxx
oYour first name:
HTTP redirection
xxxxxxxxx
oYour Last name:
oYour Last name:
oYour voucher number:
xxxxxxxxx
HTTP 404 (Page not found,

please
access number:
the following URL
oYour
voucher
to subscribe to theoYour
serviceMAC
provider
network)
address:
xxxxxxxxx
oYour MAC address:
oPassword
xxxxxxxxx
HTTP get request (Open
Welcome Page to Subscription Web Portal )
oPassword
A description of each
possible subscription is
:
cost, bandwith, et .. la
duration in min
oConfirmpassword xxxxxxxxx
HTTPpassword
get request (Open Welcome Page to Subscription Web
provided,
Portal
inlcuding
)
oConfirm
Service selected : xxxxxxxxx
Service
selection
NAI: xxxxxxxxx
256
768
1500
Validate
OK
Cancel

TMO18005
NSP Web
Portal/ PS

CPE
Ww
BS
WAC
NSPAAA/
HLA
NSP Web
Portal/ PS
User subscription information

exploitation
Account creation
Trigger AAA Povisionning
HTTPS: Account Creation Result
Welcome to on-line subscription page of XXX Operator

Thank you!
Your new Wimax account was created successfully.
Now you should disconnect and reconnect,
to use your new account.
Information will be provided soon to help you to configure your
device with the provided NAI & password

TMO18005

Post-paid accounting is also performed for verification and tracking purposes for all Pre-paid
users.
Accounting messages that convey Usage Data Records (UDRs) are sent by the NAS to a AAA
server.
The AAA server creates text files for UDR that are processed by a charging server.
In any case charging files always include the actual identity of the user.
Charging server
User Device
ASN-GW
RADIUS
Client
RADIUS ACCOUNTING
(UDRs)
RADIUS
Server
User Plane
FA
HA

TMO18005
IPIPservices
services
11.3.1 Post-Paid Messages

Accounting Start:
This message to the AAA server after the user has been authenticated and the
Internet, Access Service Flow has been created. It marks the start of the users
WiMAX network access.
Accounting Stop:
The WAC sends the Accounting Stop message when the users WiMAX network access
is closed.
Accounting Interim Update:
The WAC generates periodic Accounting Interim Update messages. The AAA sets the
corresponding Time period using the Acct-Interim-Update Radius attribute.

TMO18005
11.3.2 Off Line Accounting Procedure_HSI

CPE
Ww
BS
DHCP
WAC
AAA
CG
NAP Discovery and NSP Selection
IPIP
services
services
Mutual Authentication (server & Device)/ PKM Exchange/ IP@ Allocation

SF creation
AccountingRequest (Acct-Status Type=START)

AccountingResponse (OK)
Subscriber accesses to the internet service
AccountingRequest (Acct-Status-Type=INTERIM)
InterimCDR
AccountingRequest (Acct-Status-type=STOP)
CDR
Off line accounting is completely transparent for the WAC for VoIP and Video services, the accounting in this case
is managed by the NGN, IMS or MiTV part.

TMO18005
Self-assessment on the Objectives

Please be reminded to fill in the form

Self-Assessment on the Objectives
for this module
The form can be found in the first part
of this course documentation

TMO18005
Exercises

TMO18005
Answer the Questions

Please answer the following questions:

What
What
What
What
What
is the scope of: IEEE802.16e ?

is the scope of the WiMAX Forum ?
are the Layers specified by the WiMAX Standard ?
is the role of each layer as defined by the Standard ?
are the different services provided by the WiMAX network?

TMO18005
Exercise
Some equipments and components are missing in the following WiMAX Network,
please try to add the missed equipment in order to allow User1 to enter the
network and call User2 and User3
User 1
OMC-R
WiMAX
RAN
WAC
WiMAX
CN
User 2
BS
IMS/NGN
User 3
PSTN/2G/3G
10 mn

TMO18005
Soft
Switch
Exercise
Using the given information try to match the equipments description with the
corresponding equipment:

Mandatory for mobility

Can be embedded or external
Doesnt exist for fixed usage
Manages RAN equipments

Runs DHCP/DNS and NTP optionally
Allows RAN network elements
supervision and configuration

Aggregates WAC server traffic

Links the WAC to the other NE
In case of higher than 2
configuration, works as one with
others

10 mn
The Home Agent
Manages Radio Ressources

Supports 2 TX/RX
35dbm/Tx
DC compliant
The WAC Server

The DHCP
The AAA
The Session Border
Controller
The WiMAX L2 base
station
The WiMAX Compact
Base Station
Alcatel Omniswith
6850
The WiMAX Light Base
Station

TMO18005
OMC
Exercise
Below is a part of the WiMAX network with the different interfaces
mentioned as described by the WiMAX forum, please give the protocol
used for each interface for all types of traffic:
R1:
R3:
R4:
R6:
10 mn

TMO18005
Discover (Mobility With Distributed HA Configuration)

Using the acquired knowledge of the previous chapters,
try to describe the following different scenarios:
Corresponding Node
How the IP Packet will be delivered by the AR to the MS1

when it is connected to BS1.
Sr IP@ Ms(1)
CN
Ip@
PAYLOAD
How the IP Packet will be delivered by the AR to the MS1 AR

when it is connected to BS3 after HO
Describe the scenario with two options, if the
RAN and CSN are interconnected through
a- Layer3
b- Layer2
HA
HA
HA
WAC 1
WAC2
WAC3
BS1
1h
BS2
Cluster (1)
BS3
MS1
MS1

TMO18005
Discover (Mobility With Distributed HA Configuration)

Using the principles explained and described during Previous discover with what you did acquire
during the session, try to describe how the IP Packet will be delivered by the AR:
Corresponding Node
a- To the MS1 when it is connected to BS1

b- To the MS1 when it is connected to BS 4 after HO
Sr IP@ Ms(1)
CN
Ip@
PAYLOAD
AR
What you can conclude from all these scenarios.
Cluster (2)
Cluster (1)
HA
HA
HA
HA
WAC 1
WAC2
WAC3
WAC 1
BS1
BS2
30 mn
MS1
BS3
MS1

TMO18005
BS4
BS5
Exercise
Assume that we have one NSP connected to the WiMAX RAN, please put
on the picture all the IP@ in CN and RAN side for the WAC server, and do
the same for the BS.
Mention for each IP@, how it is assigned, and when?
RAN
CN
WAC
WAC
10 mn

TMO18005
Exercise
Please check the right answer (True/False):
The Home Agent is mandatory in the WiMAX Network
No services with QoS are provided by Internet
The WAC manages the mobile access and radio resources
The SBC is optional for Real time services
The WAC is always DHCP relay
Control plane is encapsulated between the BS and the WAC
DHCP messages are encapsulated in the RAN
In the RAN sharing, each NSP implements its own HA
PPC for all the services is embedded in the WAC
The WAC manages only HSI accounting session
15 mn

TMO18005
Exercise
From the following user profile taken from the AAA, try to list the QoS parameters
of this user:
INSERT INTO users ( user_name, user_realm, password, auth_type, reply_group )
VALUES ( 'w261-user8', 'lannion.fr', 'wimax', 'eap-ttls', 'BE1-LLCUGS' );
INSERT INTO group_avps values ( 'BE1-LLCUGS', '3gpp2-Service-OptionProfile="Maximum-Instances=1,Service-Option=\"Option-Number=176,MaximumInstances=1\""WiMAX-Packet-Flow-Descriptor="Packet-Data-Flow-ID=01,Service-DataFlow-ID=1,Direction=Bi-Directional,Transport-Type=IPv4-CS,ActivationTrigger=\"Active=true\",Uplink-QoS-ID=1,Downlink-QoS-ID=2WiMAX-QoSDescriptor="QoS-ID=1,Media-Flow-Type=Robust-Browser,Schedule-Type=BESTEFFORT,Traffic-Priority=0,Maximum-Sustained-Traffic-Rate=128000"WiMAX-QoSDescriptor="QoS-ID=2,Media-Flow-Type=Robust-Browser,Schedule-Type=BESTEFFORT,Traffic-Priority=0,Maximum-Sustained-Traffic-Rate=1024000"
WiMAX-Packet-Flow-Descriptor="Packet-Data-Flow-ID=3,Service-Data-FlowID=3,Direction=Bi-Directional,Activation-Trigger=\"Active=true\",Transport-Type=IPv4CS,Uplink-QoS-ID=3"WiMAX-QoS-Descriptor="QoS-ID=3,Schedule-Type=UGS,MinimumReserved-Traffic-Rate=120000,Tolerated-Jitter=150,Maximum-Latency=150,MediaFlow-Type=Leased-Line-Conversational,Unsolicited-Grant-Interval=20"ServiceType=Framed-User Framed-IP-Address=255.255.255.255 Termination-Action=RadiusRequest', 1 );
15mn

TMO18005
Exercise
Using the Trace (1) given by the trainer:
A- Please, try to find:

The Realm
The User Identity
The method used for user authentication.
The Ciphering method used by the two peers (User & AAA)
B- List the different steps of the authentication as you can observe on the
trace.
C- what can you conclude??
30mn

TMO18005
Exercise
Using the Trace given by the trainer, try to find:
The IP@ of each element in the following diagram.
The NSP ID or the Realm.
WiMAX RAN
H4
WiMAX CN
HA
WAC1
TELECOM
MSS
CN Telecom
BS1
BS2
WAC2
SBC
WAC3
AAA
NGN - IMS
OMC-R Server
20 h
DHCP MSS
OMC-R
Client

TMO18005
Exercise
Using the Trace(2) and the previous exercise results, fill the main
different steps that follow the Radio Network Entry on the following chart
flow:
MS
BS
WAC
AAA
DHCP
45mn

TMO18005
HA
Annexes

TMO18005
Annexes
Content
The Content of the annexes is:
1.
NGN Network
2.
IMS Network
3.
VLAN

TMO18005
Annexes NGN

TMO18005
Annexes
NGN
The 2 basic principles of an NGN:
NGN
Convergence of voice and data
(same technology for voice and data => a

single network to manage)
Effective separation of layers
Voice
("Control" and "Media" functions no longer

performed by the same physical
equipment)
Voice/data
convergence
Data
Multi
media
The need today is to route and manage increasing volumes of data traffic including voice and video.
Next Generation Networking (NGN) is a broad term to describe some key architectural evolutions in
telecommunication core and access networks that will be deployed over the next 5-10 years. The general idea
behind NGN is that one network transports all information and services (voice, data, and all sorts of media such
as video) by encapsulating these into packets, like it is on the Internet. NGNs are commonly built around the
Internet Protocol, and therefore the term "all-IP" is also sometimes used to describe the transformation towards
NGN.

TMO18005
Annexes
NGN
NGN Class 4
MGC
LEX
AN
Circuit Networks
TGW
TGW
LEX
AN
TGW
Packet
Backbone
BRAS
DSLAM
LPF
Internet

TMO18005
Annexes
NGN
NGN Class 5
MGC
AN
Circuit Networks
AGW
TGW
RGW
AN
AGW
STP
Packet
Backbone
BRAS
DSLAM
LPF
Internet

TMO18005
Annexes
NGN
The Signaling is SS7. The MGW is a signalling GW to map it on SIGTRAN on
the NGN side.
The User plane is carried over IP
Call Server Call Server
Home
(CPE)
Access
node
AN
Local
switch
LEX
Transit
National
TEX
MGW
IP
MGW
IP
MGW
TDM
User plane
Control plane
A Media Gateway, abbreviated MGW acts as a translation unit between disparate telecommunications networks
such as PSTN; Next Generation Networks; 2G, 2.5G and 3G radio access networks or PBX. Media Gateways
enable multimedia communications across Next Generation Networks over multiple transport protocols such as
ATM and IP.

TMO18005
Annexes
NGN
Thank to the SBC the WiMAX network is integrated with the NGN network
Call Server Call Server
Home
(CPE)
Access
node
AN
Local
switch
LEX
Transit
National
TEX
MGW
IP
MGW
SBC
TDM
WAC
IP
HA
A Media Gateway, abbreviated MGW acts as a translation unit between disparate telecommunications networks
such as PSTN; Next Generation Networks; 2G, 2.5G and 3G radio access networks or PBX. Media Gateways
enable multimedia communications across Next Generation Networks over multiple transport protocols such as
ATM and IP.

TMO18005
Annexes
NGN
s
today
f
o
e
s
On
itche
w
s
M
TD
NGN
Call Server
Services and
connection control
Access
Gateways
Switching
matrix
Subscriber
interfaces
Trunking
Gateways
IP
Circuit
interfaces
H323/SIP "soft" & "hard" phones

TMO18005
Annexes IMS

TMO18005
Annexes
IMS
Open, standardised, operator friendly, NGN multimedia architecture for
mobile and fixed services
Based on SIP, DIAMETER controls
Supports legal interception, localisation, PSTN interworking, etc.
Developed in 3GPP but now adopted by ETSI
Access Independent
Applications
Applications
3G
3Gmobile
mobile
WiMAX
WiMAX
Internet
IMS
IMSPlatform
Platform
DSL
DSL
Fibre
Fibre
Ethernet
Ethernet
PSTN
IP
IPtransport
transport
MGW
MGW
3GPP has decided to use a layered approach to architectural design. This means that transport and bearer are
separated from the IMS signalling network and the session management service.
Application layer:
Service Capabilities
Standardized access to telecom service capabilities for 3rd party developers: open Interfaces.
IMS User Profile stored in a central database.
Control layer:
Manages multimedia sessions using only one multimedia protocol (SIP) for session and service control.
Assumes the authentication of an IMS subscriber.
Is responsible for Home Service Control.
Transport layer:
Assumes the independence (as long as it is IP) with the access: fixed, mobile, wireless.
Quality of Service enabled (policed by control plane).
Combination with charging package for data and IMS services is possible.
Inter-working with circuit switched (fixed/mobile) is supported thanks to gateway.
Access layer:
Represents all the possible broadband access technologies: UTRAN, CDMA2000, xDSL, WLAN, cable networks.

TMO18005
Annexes
IMS
DHCP
AAA
WAC
Circuit
networks
WiMAX
GGSN
SGSN
HLR
AuC
GPRS
backbone
Node-B
RNC
IMS
Packet Switching (PS)

TMO18005
GGSN
Packet
networks
Annexes
IMS
Application
Layer
Control
Layer
AS
AS
HSS/ SLF
AS
S-CSCF
I-CSCF
IBCF
P-CSCF
Transport
Layer
IP network
AS
Application Server
CSCF
Call Session Control Function
HSS
Home Subscriber Server
IBCF
Interconnect Border Control Function
I-BGF
Interconnect Border Gateway Function
I-CSCF
Interrogating-CSCF
P-CSCF
Proxy-CSCF
S-CSCF
Serving-CSCF
SLF
Subscription Locator Function

TMO18005
I-BGF
Others IMS
Networks
Annexes
IMS
WiMAX Access
IMS Core
Control Layer
P-CSCF
Transport Layer
PDF
Access Transport
PEF
Network
BS
WAC

TMO18005
Annexes
IMS: P-CSCF
Entry point of
the IMS
IMS
network for UE
P-CSCF
Access Network
Internet
The P-CSCF function is done by the SBC
Alcatel-Lucent LAN
http
proxy

TMO18005
Annexes
IMS: S-CSCF
HSS
I-CSCF
S-CSCF
Other IMS
Server that downloads the subscriber profile in a

local database, and controls the subscriber
Network
Similar to the VMSC/VLR function
P-CSCF
VMSC/VLR
Access Network
HLR
AuC
GMSC
Circuit
networks
BTS
BSC

TMO18005
Annexes
IMS: HSS
HSS
I-CSCF
S-CSCF
Other IMS
Database which contains the multimedia

subscription.
Network
Similar to the HLR function
P-CSCF
AuC
Access Network
HLR
VMSC/VLR
Circuit
networks
BTS
BSC
GMSC

TMO18005
Annexes
IMS: SIP
User Agent Client:
Entity that creates and process new request,
User Agent Server:

Entity that generates a response to a SIP request,
User Agent
(ex: Endpoints)
Registrar:
Stores endpointss adresses ("location service"),
Redirect server:
Forward to the caller a set of callees addresses (contacts) thanks to the
location service

TMO18005
Annexes
IMS: SIP
REGISTER : used by the UA to send its location (IP address or hostname) to

a REGISTRAR server in order to be reachable
INVITE : used to setup a session between 2 UAs,
ACK : acknowledgment of final response to INVITE,
CANCEL : used to cancel pending session, initiate by the INVITE,
BYE : used to terminate a session initiated by the INVITE,
OPTIONS : used to query UA options and capabilities (ie : supported languages,

supported extensions),

TMO18005
Annexes
IMS: SIP
sip:erwan@orange.fr is reachable at
192.0.2.101
Location DB
Location DB
Registrar
REGISTER
sip:erwan@orange.com
192.0.2.101
Registrar
Proxy
Proxy
UE
UE
INVITE sip:christophe@sfr.fr
Im calling Christophe
sfr.fr
orange.fr

TMO18005
Annexes VLAN

TMO18005
Annexes
VLAN: Physical LAN
Sell
s
R&
D Fi
nan
ces
R&
D
Hub1
R&
D
Hub2
LAN1
Sell
st
r
po
Im C
R&
D
sells
Hub4
Hub3
B
A
t
art
p
de
rt
o
p B
Ex
R&
D
Hub5
LAN3
X
Fina
nces
Fina
nces
Hub6
W
LAN2
R&
D
Router
To inter connect IP devices one solution consist of using Hubs

TMO18005
Annexes
VLAN: Concept
VLAN2
VLAN1
Switch
1
VLAN-Aware Switches
Switch
2
Y
C
W
VLAN3
A VLAN comprises a set of stations ( defined by the VLAN association rules in effect) together with the links and
switches needed to interconnect them.
Virtual LAN (VLAN) technology allows us to separate the logical connectivity from the physical connectivity. Users
are still connected via physical cables to physical wiring devices, but the connectivity view from the station or
application perspective is no longer restricted to the bounds of this physical topology. That is, the set of
stations or applications that can directly communicate as if on a common LAN can be controlled through
software configuration of the switches and/or the end stations in the LAN. The LAN is virtual in that a set of
stations and applications can behave as if they are connected to a single physical LAN when in fact they are
not.
A VLAN is a flexible group of devices that can be located anywhere in a network, but they communicate as if they
are on the same physical segment. With VLANs, you can segment your network without being restricted by
physical connections a drawback of traditional network design. As an example, with VLANs you can segment
your network according to:
Departmental groups For example, you can have one VLAN for the Marketing department, another for the
Finance department, and another for the Development department.
Hierarchical groups For example, you can have one VLAN for directors, another for managers, and another
for general staff.
Usage groups For example, you can have one VLAN for users of e-mail, and another for users of
multimedia.
To achieve this flexibility, we must use switches rather than shared bandwidth (repeater) hubs for our device
interconnections. Furthermore, the switches need to be VLAN ; they must include a set of features and
capabilities beyond those of the VLAN switches considered up to now. It is these additional capabilities that
allow us to configure the logical connectivity as appropriate for the user's application environment.
TMO18005
Annexes
VLAN: Security
VLAN2
VLAN1
Switch
1
Switch
2
Y
C
W
VLAN3
When using a shared-bandwidth (non-switched) LAN, there is no inherent protection provided against unwanted
eavesdropping. Indeed, this is often used as a generic complaint against shared LANs; any user can, using
software on a conventional personal computer, capture and inspect every frame on the LAN, regardless of the
intended destination.
A malicious user on a shared LAN can also induce problems by sending lots of traffic to specific targeted users
(i.e., overloading their network interfaces and LAN software with huge amounts of spurious traffic, resulting in
performance degradation, undesired behavior, or system crashes) or the network as a whole (using spurious
broadcasts). The only cure is to physically isolate the offending user
By creating logical partitions with VLAN technology, we further enhance the protections against both unwanted
eavesdropping and spurious transmissions. A properly implemented port-based VLAN allows free communication
among the members of a given VLAN, but does not forward traffic among switch ports associated with members
of different VLANs. This isolation accrues both to unicast and multicast traffic.
The VLAN configuration is providing traffic isolation, even among ports on the same switch. This is true for
multicast and unknown unicast traffic as well. While a conventional switch forwards all multicast and unknown
unicast traffic to all ports except that on which the traffic arrived, a properly-configured VLAN-aware switch
will forward such traffic only to those ports ( except for the arrival port, of course) that contain members of
the VLAN associated with that traffic.
Users can eavesdrop only on the multicast and unknown unicast traffic within their own VLAN ; presumably the
configured VLAN comprises a set of logically related users (e.g., a company department). It is no longer possible
to eavesdrop on traffic from other departments. Similarly, while it is still possible to inject malicious traffic,
such traffic should only propagate among switch ports within a single VLAN, and thus any network disruption is
localized. Of course, this improvement in security is achieved through a reduction in connectivity; it is no
longer possible to communicate directly (Le., at the Data Link layer) between stations in disjoint VLANs, even
though they are connected to a common switched LAN. (Communication can still be achieved at Network layer
through a router.)

TMO18005
Annexes
VLAN
A
Sell
s
R&
D F
inan
ces
R&
D
R&
D
1 2 3 4 5 6
SwitchSwitch-A 0
Port
1
2
3
4
5
6
0
0
0
rtm
pa
e
d
ort B
p
Ex
vlan
1
3
2
2
2
2
1
2
3
Sell
ts
r
po
m
C
I
R&
D
sells
Port
1
2
3
4
5
6
0
0
0
vlan
1
2
1
2
3
3
1
2
3
R&
D
R&
D
0 1 2 3 4 5
SwitchSwitch-B 6
9 8 7
X
Fina
nces
Y
Fina
nces
Port-Based VLAN Mapping

The simplest implicit mapping rule is known as port-based VLAN mapping. A frame is assigned to a VLAN based
solely on the switch port on which the frame arrives.
Stations within a given VLAN can freely communicate among themselves using either unicast or multicast
addressing. No communication is possible at the Data Link layer between stations connected to ports that are
members of different VLANs. Communication among devices in separate VLANs can be accomplished at higher
layers of the architecture, for example, by using a Network layer router with connections to two or more
VLANs.
Multicast traffic, or traffic destined for an unknown unicast address arriving on any port, will be flooded only to
those ports that are part of the same VLAN.
This provides the desired traffic isolation and bandwidth preservation. The use of port-based VLANs effectively
partitions a single switch into multiple sub-switches, one for each VLAN.
Port-based VLANs were the first type available in commercial products, primarily because they are the easiest to
implement. It is not necessary to parse and inspect frames in real-time to determine their VLAN mapping;
regardless of their contents, all frames received on a given port will be assigned to the same VLAN. Port-based
VLANs are appropriate for software patch-panel, switch segmentation ( using a high port-density switch as if it
were a number of smaller switches ), and bandwidth preservation applications.

TMO18005
Annexes
VLAN
Destination Address
Source Address
Ethertype
= 0x8100
MAC Length/Type
This frame carries the tag

IEEE 802.1Q/802.1p.
802.1q
User PriorityCFI
(Vlan ID) 12 bits
Tag Control Information
Data
MAC Length/Type
PAD
Data
FCS
PAD
FCS
VID
802.1p
User priority Acronym
1
BK
2
0 (Default)
BE
3
EE
4
CL
5
VI
6
VO
7
NC
CFI : Canonical Format Identifier (1 Bit)
Tra ffic type

Background
Spare
Best Effort
Excellent Effort
Controlled Load
Video
Voice
Network Control
The tagging scheme proposed by the 802.3ac standard suggests the addition of the four octets after the source
MAC address. Their presence is indicated by a particular value of the EtherType field (called TPID), which has
been fixed to be equal to 0x8100.
When a frame has the EtherType equal to 0x8100, this frame carries the tag IEEE 802.1Q/802.1p.
The tag is stored in the following two octets and it contains :
CFI : Canonical Format Identifier (1 bit ), Canonical format refers to the bit ordering (Little or Big Endian) of
the bytes within a frame. The CFI is used for compatibility reasons between Ethernet-type networks and
Token Ring-type networks. Data within Ethernet frames is normally sent using canonical (Little Endian) bit
order (CFI=0). Token Ring frames normally send data using non-canonical (Big Endian) bit order (CFI=1).
VLAN ID (12 bits ). The VID is the identification of the VLAN, which is basically used by the 802.1Q standard;
being on 12 bits, it allows the identification of 4096 VLANs.
User Priority (3 bits) is used by the 802.1p standard. The priority field is actually unrelated to the use of tags
for VLAN identification; it is not there for VLAN purposes at all. (see note 1)
After the two octets of TPID and the two octets of the Tag Control Information field there are two octets that
originally would have been located after the Source Address field where there is the TPID. They contain either
the MAC length in the case of IEEE 802.3 or the EtherType in the case of Ethernet version 2.
Note 1 : Priority - Some LAN technologies have the native ability to carry user priority information (e.g., IEEE
802.4 Token Bus); others (such as Ethernet) don' have this capability. Therefore, it made sense to provide the
means to add explicit priority information to frames for use in those technologies with. out native priority
support. However, it seemed unreasonable to provide two types of tags, one for priority information and
another for VLAN identification; the two functions were therefore combined into a single tag. Thus, the
802.1Q VLAN tag carries priority information, which is actually there for the benefit of IEEE 802.1p (priorityaware) switches. A side benefit of this approach was that the tag format could be specified in just one place
(802.1Q), rather than having its semantic definitions spread out over multiple standards.
Note 2 : Adding a tag in a frames implies that the FCS field has to be recomputed

TMO18005
Annexes
VLAN
Physical connection
Switch 1
Switch 2
vlan1
vlan3
vlan3
W
vlan2
vlan2
Virtual
connections
Physical
connection
4
vlan1
There are two methods for identifying the VLAN membership of a given frame:
Parse the frame and apply the membership rules. This is sometimes referred to as implicit tagging. A frame's VLAN
association can always be inferred by inspecting the frame contents and applying the complete set of VLAN association
rules for the LAN. Typically, this form of VLAN determination is made by an edge switch the forwarding behavior of the
switch is, in part, determined by the resulting VLAN association of the frame.
Provide an explicit VLAN identifier within the frame itself This is known as explicit tagging (or sometimes just tagging). A
VLAN-aware end station or switch can declare the VLAN association through the use of a predefined tag field carried
within the frame.
implicit Tags
The name notwithstanding, there are no tags involved with implicit tagging An implicitly tagged frame is a normal, unmodified
frame as emitted by any conventional end station or switch. The VLAN association is implied by the frame contents and is a
function of the VLAN rules particular to the application environment. The VLAN association may be a function of:
- Data Link Source Address
- Protocol type
- Higher-layer network identifiers (e.g., IP subnet) - Application-specific fields, and so on

In a VLAN environment, all frames sent by VLAN end stations are considered implicitly tagged. Being VLAN, the end stations
don't know about VLAN associations; such associations are implied by the contents of the frames they send. Any such VLAN
switch operating on an implicitly tagged frame must first make the proper VLAN association from the frame contents. Once
done that switch may forward the frame with an explicit VLAN tag (if the frame being forwarded into a VLAN tag domain) or
without an explicit tag (i.e., the same way the frame arrived).
Implicit tagging requires that the VLAN association be determined by applying the set of VLAN rules every time the frame is
processed by a VLAN switch. If there are no explicit tags provided, each VLAN-aware switch in the path between the source
and destination(s) must independently determine VLAN association from an application of the rules. Besides requiring
repetitive superfluous, redundant processing, the implication is that every switch must know the complete set of VLAN
association rules in force in the entire LAN. Depending on the application environment, this could be hundreds or even
thousands of rules, applied to various fields in the frame (including higher-layer application-specific fields). This is a heavy
burden to place on every switch; this workload can be significantly reduced by making the VLAN association just once, then
explicitly tagging the frame with the resulting value.

TMO18005
Annexes
VLAN
A
Sell
s
R&
DF
inan
ces
R&
D
Port
1
2
3
4
5
6
0
0
0
vlan
1
3
2
2
2
2
1
2
3
R&
D
1 2 3 4 5 6
SwitchSwitch-A 7
rtm
pa
e
d
ort B
p
Ex
Sell
s
R&
ort
D
p
Im C
R&
D
ells
Port
1
2
3
4
5
6
0
0
0
vlan
1
2
1
2
3
3
1
2
3
R&
D
1 2 3 4 5
Switch-B 6
0 Switch9 8 7
X
Fina
nces
Y
Fina
nces
A routing function has to be used to communicate between Vlans.

By definition, any inter-subnet communication must occur at the Network layer through a router. in a traditional
(non-VLAN) case, this would mean connecting a router between the separate switches using a port on each
switch.
If the switch and/or the router does not managed tags, one port per Vlan must be connected to the router.

TMO18005
Self-assessment on the Objectives

Please be reminded to fill in the form

Self-Assessment on the Objectives
for this module
The form can be found in the first part
of this course documentation

TMO18005
Abbreviations and Acronyms

#
#1
#2
Full Writing of Term #1

Full Writing of Term #2
O
O1
O2
Full Writing of Term O1

Full Writing of Term O2
A
A1
A2
Full Writing of Term A1

Full Writing of Term A2
P
P1
P2
Full Writing of Term P1

Full Writing of Term P2
B
B1
B2
Full Writing of Term B1

Full Writing of Term B2
Q
Q1
Q2
Full Writing of Term Q1

Full Writing of Term Q2
C
C1
C2
Full Writing of Term C1

Full Writing of Term C2
R
R1
R2
Full Writing of Term R1

Full Writing of Term R2
D
D1
D2
Full Writing of Term D1

Full Writing of Term D2
S
S1
S2
Full Writing of Term S1

Full Writing of Term S2
E
E1
E2
Full Writing of Term E1

Full Writing of Term E2
T
T1
T2
Full Writing of Term T1

Full Writing of Term T2
F
F1
F2
9700 WiMAX
E2E Architecture
196 F1
Full
Writing
of Term
Full Writing of Term F2
U
U1
U2
Full Writing of Term U1

Full Writing of Term U2
G
G1
G2
Full Writing of Term G1

Full Writing of Term G2
V
V1
V2
Full Writing of Term V1

Full Writing of Term V2
H
H1
H2
Full Writing of Term H1

Full Writing of Term H2
W
W1
W2
Full Writing of Term W1

Full Writing of Term W2
I
I1
I2
Full Writing of Term I1

Full Writing of Term I2
X
X1
X2
Full Writing of Term X1

Full Writing of Term X2
J
J1
J2
Full Writing of Term J1

Full Writing of Term J2
Y
Y1
Y2
Full Writing of Term Y1

Full Writing of Term Y2
K
K1
K2
Full Writing of Term K1

Full Writing of Term K2
Z
Z1
Z2
Full Writing of Term Z1

Full Writing of Term Z2
L
L1
L2
Full Writing of Term L1

Full Writing of Term L2
M
M1
M2
Full Writing of Term M1

Full Writing of Term M2
N
N1
N2
Full Writing of Term N1

Full Writing of Term N2

TMO18005
Abbreviations and Acronyms [cont.]


TMO18005
Glossary
#
#1
#2
Explanation of Term #1
Explanation of Term #2
A
A1
A2
Explanation of Term A1
Explanation of Term A2
B
B1
B2
Explanation of Term B1
Explanation of Term B2
C
C1
C2
Explanation of Term C1
Explanation of Term C2
D
D1
D2
Explanation of Term D1
Explanation of Term D2
E
E1
E2
Explanation of Term E1
Explanation of Term E2
F
F1
F2
Explanation of Term F1
Explanation of Term F2
G
G1
G2
Explanation of Term G1
Explanation of Term G2
H
H1
H2
Explanation of Term H1
Explanation of Term H2
I
I1
I2
Explanation of Term I1
Explanation of Term I2
J
J1
J2
Explanation of Term J1
Explanation of Term J2
K
K1
K2
Explanation of Term K1
Explanation of Term K2
L
L1
L2
Explanation of Term L1
Explanation of Term L2
M
M1
M2
Explanation of Term M1
Explanation of Term M2

TMO18005
Glossary [cont.]
N
N1
N2
Explanation of Term N1
Explanation of Term N2
O
O1
O2
Explanation of Term O1
Explanation of Term O2
P
P1
P2
Explanation of Term P1
Explanation of Term P2
Q
Q1
Q2
Explanation of Term Q1
Explanation of Term Q2
R
R1
R2
Explanation of Term R1
Explanation of Term R2
S
S1
S2
Explanation of Term S1
Explanation of Term S2
T
T1
T2
Explanation of Term T1
Explanation of Term T2
U
U1
U2
Explanation of Term U1
Explanation of Term U2
V
V1
V2
Explanation of Term V1
Explanation of Term V2
W
W1
W2
Explanation of Term W1
Explanation of Term W2
X
X1
X2
Explanation of Term X1
Explanation of Term X2
Y
Y1
Y2
Explanation of Term Y1
Explanation of Term Y2
Z
Z1
Z2
Explanation of Term Z1
Explanation of Term Z2

TMO18005
End of Module

TMO18005

9700 WiMAX W4 End-To-End Architecture

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

9700 WiMAX W4 End-To-End Architecture

Загружено:

Авторское право:

Доступные форматы

Do not delete this graphic elements in here:

9700 WiMAX W4 End-to-End

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

9700 WiMAX E2E Architecture 2

All Rights Reserved Alcatel-Lucent @@YEAR

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent @@YEAR

9700 WiMAX E2E Architecture 3

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

Module Objectives [cont.]

9700 WiMAX E2E Architecture 4

All Rights Reserved Alcatel-Lucent @@YEAR

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

Table of Contents [cont.]

All Rights Reserved Alcatel-Lucent @@YEAR

Table of Contents [cont.]

All Rights Reserved Alcatel-Lucent @@YEAR

1 IEEE802.16e Vs The WiMAX FORUM

9700 WiMAX E2E Architecture 8

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

1 WMAN Brief Backgrounder

1.1 IEEE802.16 Standards

IEEE 802.16: WMAN Metropolitan

IEEE 802.16 protocol layering

9700 WiMAX E2E Architecture 9

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

1 WMAN Brief Backgrounder

1.2 WiMAX Forum Specifications

9700 WiMAX E2E Architecture 10

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

2 Network Reference Model

9700 WiMAX E2E Architecture 11

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

2 Network Reference Model

2.1 WiMAX Forums Network Reference Model

9700 WiMAX E2E Architecture 12

All Rights Reserved Alcatel-Lucent @@YEAR

It should be noted that in the current Alcatel-lucent Release:

All Rights Reserved Alcatel-Lucent @@YEAR

2 Network Reference Model

2.2 ASN (Access Service Network)

In addition to the above mandatory features, an ASN may support:

Intra-ASN mobility & Paging and Location Management

9700 WiMAX E2E Architecture 13

All Rights Reserved Alcatel-Lucent @@YEAR

ASN comprises network elements such as Base Station, ASN-GW

All Rights Reserved Alcatel-Lucent @@YEAR

2 Network Reference Model

2.3 CSN & ASP

Enforcement Services, etc)

9700 WiMAX E2E Architecture 14

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

2 Network Reference Model

2.5 Alcatel-Lucent Reference Model

9700 WiMAX E2E Architecture 15