Priority Access for IEEE 802.16m
IEEE 802.16 Presentation Submission Template (Rev. 9)
Document Number: IEEE C802.16m-07/253
Date Submitted: 2007-11-07
Source
An Nguyen
Arnaud Tonnerre
An.P.Nguyen@dhs.gov
arnaud.tonnerre@fr.thalesgroup.com
DHS/NCS
THALES COMMUNICATIONS
USA
Colombes, France
Djamal-Eddine Meddour
djamal.meddour@orange-ft.com
FRANCE TELECOM
Lannion, France
Sheng Sun
shengs@nortel.com
Nortel
Ottwa, Ontario, Canada
Richard Li
richard929@itri.org.tw
ITRI
Hsinchu, Taiwan
Carlos de Segovia
carlos.desegovia@orange-ftgroup.com
FRANCE TELECOM
Cesson Sévigné – France
Bong Ho Kim
bhkim@posdata-usa.com
Posdata
San Jose, CA, USA
Venue: IEEE 802.16 Session #52 Atlanta, United States
Base Contribution: None
Purpose: Response to SDD Call for Proposal of IEEE 802.16m
Notice:
This document does not represent the agreed views of the IEEE 802.16 Working Group or any of its subgroups. It represents only the views of the participants listed in
the “Source(s)” field above. It is offered as a basis for discussion. It is not binding on the contributor(s), who reserve(s) the right to add, amend or withdraw material
contained herein.
Release:
The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an
IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s
sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this
contribution may be made public by IEEE 802.16.
Patent Policy:
The contributor is familiar with the IEEE-SA Patent Policy and Procedures:
<http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and <http://standards.ieee.org/guides/opman/sect6.html#6.3>.
Further information is located at <http://standards.ieee.org/board/pat/pat-material.html> and <http://standards.ieee.org/board/pat >.
Priority Access for IEEE 802.16m
An Nguyen, DHS/NCS
Arnaud Tonnerre, THALES COMMUNICATIONS
Djamal-Eddine Meddour, FRANCE TELECOM
Sheng Sun, Nortel
Carlos de Segovia, FRANCE TELECOM
Richard Li, ITRI
Bong Ho Kim, Posdata
Outline
• Objective
• Priority access requirements
• 802.16m system architecture to support
priority access
Objective
Objective
• Priority access is one of the important requirements for Emergency
Telecommunications Service (ETS)*
• IEEE 802.16m has requirements on priority for the government and public
safety
– Section 5.8 of IEEE 802.16m-07/002r4
• “IEEE 802.16m shall be able to support public safety first responders, military and
emergency services such as call-prioritization, preemption, push-to-talk”
• “Priority access” is a SPWG requirement in Mobile WiMAX
– In Release 1.5**, “R-[193] The WIMAX network SHALL provide high priority
for special circumstances such as emergency services and deadlock situations.
Such high priority SHALL be protected with appropriate additional levels of
authentication.”
• Priority access is required for National Security and Emergency Preparedness (NS/EP)
users.
• This contribution presents 1) more detailed ETS requirements, specially in the
area of priority access and 2) system architecture to support priority access to
be considered by 802.16m
*“Overview of Standards in Support of Emergency Telecommunication Service (ETS),” ATIS-pp-0100009, November 2006.
**”Recommendations and Requirements for Networks based on WiMAX Forum Certified Products,” Release 1.5, Jan. 2007
Priority Access Requirements
Background on DHS Priority Access*
• Priority access service is intended to facilitate emergency
response and recovery operations in response to natural and
man-made disasters and events, such as floods, earthquakes,
hurricanes, and terrorist attacks. Priority access service is also
intended to support both national and international emergency
communications. Priority access service is based upon, and
complies with, the FCC Second Report and Order (R&O) 00242 (Wireless Telecommunications (WT) Docket No. 96-86).
Priority access service is intended to allow qualified and
authorized National Security and Emergency Preparedness
(NS/EP) users to obtain priority access to radio traffic channels
and core network resources during situations when
Commercial Mobile Radio Service (CMRS) provider network
congestion is blocking call attempts
*Wireless Priority Service (WPS) Industry Requirements For UMTS – Phase 1 – Redirection to GSM,” DHS/NCS IR
Document, Version 0.3, April 2005
Background on Emergency Telecommunications
Service (ETS)
• “Emergency Telecommunications Service: A telecommunications service
offering available on public communications networks that facilitates the
work of authorized emergency personnel in times of disaster, national
emergency, or for executive/governmental communications relating to
National Security / Emergency Preparedness (NS/EP).”*
**“Overview of Standards in Support of Emergency Telecommunication Service (ETS),” ATIS-pp-0100009, November 2006
ETS Standardization Activities Around the Globe
•
•
•
•
•
•
•
ITU (International Telecommunication Union)
IETF (Internet Engineering Task Force)
ETSI (European Telecommunications Standards Institute)
ATIS (Alliance for Telecommunications Industry Solution)
TIA (Telecommunications Industry Association)
3GPP (3rd Generation Partnership Project)
3GPP2 (3rd Generation Partnership Project 2)
WiMAX from a DHS NS/EP Perspective
NS/EP Use Cases
Other Core
Network
Elements
(e.g., IMS NGN)
Backhaul
Backhaul
Switch
High Priority data sent using
highest QoS
VLAN switch
or router
Edge equipment
WiMAX
Base Station
&
P2P
Core
Network
BS
WiMAX
Base Station
& P2P
Streaming Video and
Video Conferencing
to and from the
Disaster site and the
Disaster
Management
Other Associated Requirements
• Ubiquitous Services:
– Able to make a call/session in times of disaster, national emergency, or for
executive/governmental communications relating to National Security /
Emergency Preparedness (NS/EP).
– It applies to voice, video, and data services
• Availability:
– It is available to NS/EP users at all times.
• QoS
– End-to-end QoS should be provided based on 802.16e QoS classes and
parameters
• Security
– “Networks must have protection against corruption and intrusion such as
unauthorized access, control and traffic”*
• Priority treatment
– “ETS communications should be provided preferential end-to-end treatment so
that higher communication session completion rates, as compared with public
communication session completion rates, would be successfully achieved”*
*“Overview of Standards in Support of Emergency Telecommunication Service (ETS),” ATIS-pp-0100009, November 2006.
Service Scenarios
• Scenario 1: Mobile originating call
– Authorized user initiates a voice, data or video call
to any party using 802.16m technology
• Scenario 2: Mobile terminating call
– Authorized user calls another authorized user
reachable using 802.16m technology
Scenarios are presented to develop the requirements and technical solutions for priority access.
802.16m System Architecture to Support
Priority Access
Mobile WiMAX Network Architecture
Network Access Provider
Regular
Mobile
Network Service Provider
BS
Access Services
Network (ASN)
Gateway
Authorized
Mobile
BS
FA
ASN is defined as a complete set of network
functions needed to provide radio access to a
WiMAX subscriber.
HA: Home Agent
FA: Foreign Agent
AAA: Authentication, Authorization and Accounting
Connectivity
Services
Network (CSN)
HA
AAA
CSN is defined as a set of network
functions that provide IP connectivity
services to the WiMAX subscriber.
Congestion Points
• Over the air
– Contention-based*
• Bandwidth request and initial ranging
– Allocation-based
• OFDMA capacity
Focus of this presentation
• Core network
– ASN gateway
– CSN
Instead of using contention-based technique, allocation-based technique may be required for priority users.
Admission Control and Priority Treatment
•
The priority access requirement manifests itself in two functionalities: 1)
admission control and 2) priority treatment of the request once admitted
Admission control is implementation specific, and should not be discussed
in standards
•
–
However, how to identify the authorized user and the user’s requested services
(i.e., convey the priority access indicator to 802.16m networks) should be
standardized
1.
2.
SIM-based (802.16 needs to support this type of application) [x]
Subscriber MAC address based* combined with User ID and/or Device ID []
•
3.
This is to identify authorized user
Feature based (prefix dialing-digits for voice calls and SIP-based for data calls) []
•
4.
This is to indicate priority access service
Priority information encoded in IP or Ethernet headers* [] (but priority is either
mapped to layer 2 SFID or new traffic type field in the MAC header)
•
This is to indicate priority access service
•
5.
–
•
For example: IP Type of Services (TOS) field based
The Access Control List (ACL) should be either statically or dynamically provisioned
on the edge devices (BS or ANS-GW) []
Capacity reservation scheme for authorized users should be explored
Priority treatment is done first by mapping the priority access indicator to
the pre-provisioned Service Flow ID (SFID).
*Authorized user identify needs to be authenticated. Security protection of transfer of MAC address and IP header becomes important.
Network Entry – An Example of Using MAC
Address as Priority Indicator
• The following are the steps in
network entry (802.16e)
– Scanning
– Obtaining parameters
– Initial ranging
• The first time (unprotected) Subscriber MAC address
is conveyed to the 802.16m BS
–
–
–
–
–
Exchanging capabilities • The MAC address (with user ID/device ID )are
passed to the 802.16m network during authentication.
Authentication
The authorized user is authenticated in the 802.16m
network during the authentication step.
Registration
IP connectivity
• The priority access indicator is
Creating transport connection
passed to the network at the adding
(Adding service)
service step. Their QoS is mapped
to the corresponding SFID.
Security – Authentication
• Authentication
– Standard shall support Mutual Authentication for the
assurance of mutual trusts between subscriber devices and
the authenticator
– Authentication method could vary from RSA X.509, EAP,
SIM based or the combinations
– ‘Rapid’ Authentication/Re-authentication that reduces the
performance implication for mobile applications, such as
Handoff
– For priority access, edge devices (BS or ASN-GW) should
have the capability to run the subset of AAA function
which can validate the subscriber/devices at local premise
Security – Confidentiality and Integrity
Protection of Prioritized Traffic
• Confidentiality and Integrity Protection
– All traffic (Management and Subscriber Data)
Shall be protected either by encryption (by session
keys) or MAC (Message Authentication Code)
– For prioritized traffic, MAC is mandated,
encryption is optional
– Sensitive prioritized traffic has to be encrypted
with strong session keys
Authentication Step
• The Subscriber MAC address (combined with
user ID/device ID) for authorized priority users
can be pre-provisioned, and stored in the
Home Agent database.
Adding Service Step
• For scenario 1, the feature-based indicator
allows the BS to allocate pre-provisioned
service for authorized users, and map the
service to the corresponding SFID
• For scenario 2, the Ethernet or IP TOS
achieves the same effect.
Priority Treatment
• Out of the five 802.16e QoS classes, the following four are considered
appropriate for priority access services (UGS, rtps, Ertps, and nrtps).
Within each QoS class, authorized user can get non-preempted
preferential treatment for their traffic in the network
– One example is to perform priority treatment via queuing and scheduling;
authorized user has their request in the front of the queue.
• Within the authorized users, there are multiple sub-priority levels. The subpriority level and the request arrival time determine the queue position
• The queuing and scheduling would be implementation specific, but their
behavior should be measurable. Also, it is envisioned that a priority
resource allocation technique will be “recommended” for each of the
QoS classes
– The “recommended” priority resource allocation technique will be presented
in future sessions.
Flow Chart
Registration
Authorize user identity
Adding service
Pass priority access indicator to the network
Capacity scheduling
(MAC)
Provide preferential treatment to authorized user
Capacity allocation
(MAC and PHY)
Deployment Timing
• DHS/NCS would like to have the priority
access service available for NS/EP community
whenever and wherever Mobile WiMAX
service is available
Conclusion
• We have presented requirements on priority access
from ETS view point
• We have provided a system architecture that supports
these services and requirements
• We would like this concept to be considered by
802.16m
• We are looking for others to collaborate on this
concept with. If you are interested, please contact us.
References
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
“Overview of Standards in Support of Emergency Telecommunication Service (ETS),” ATISpp-0100009, November 2006.
Quality of Service Attributes for Diameter,” draft-ietf-dime-qos-attributes-02.txt
“Quality of Service Parameters for Usage with the AAA Framework,” draft-ietf-dime-qosparameters-01.txt
“RSVP Extensions for Emergency Services,” draft-ietf-tsvwg-emergency-rsvp-03.txt
“QoS NSLP QSPEC Template,” draft-ietf-nsis-qspec-18.txt
Report ITU-R.[PPDR]: “Radiocommunication objectives and requirements for public
protection and disaster relief (PPDR)”
Recommendation H.460.4 – Call priority designation for H.323 calls
Draft recommendation H.SETS – security for ETS (H.235)
E.106 – Description of an international emergency preference scheme (IEPS)
Draft Recommendation U.roec – network requirements and capabilities to support ETS
RFC3523: “Internet Emergency Preparedness (IEPREP) Telephony Topology Terminology”
TETRA: “Mobile narrowband and wideband communications for public safety applications”
TR41.4 TSB146: “Telecommunications – IP Telephony Infrastructure – IP Telephony Support
for Emergency Calling Service)
3GPP TS 22.153, “Technical Specification Group Services and System Aspects; Multimedia
priority service”, Release 8.
3GPP S.R0017-0, “Multimedia Priority Service (MMPS) for MMD-based Networks – Stage 1
Requirements”