Transcript 21-04-0167-02-0000-FranceTelecom

•
•
•
•
•
IEEE 802.21 MEDIA INDEPENDENT HANDOVER
DCN:
Title: Proposal for the 802.21 solution
Date Submitted: November, 8th, 2004
Presented at IEEE 802.21 session #NN in San Antonio,
TX, US
• Authors or Source(s):
• Eric Njedjou, France Telecom
• Abstract: This is the abstract text. Replace this text with a
short statement of the contents and purpose of the
presentation. Communicate well, you only have a few
lines or so to convey the essence of the slides.
•
•
•
IEEE 802.21 presentation release statements
This document has been prepared to assist the IEEE 802.21 Working
Group. It is offered as a basis for discussion and is not binding on the
contributing individual(s) or organization(s). The material in this
document is subject to change in form and content after further study.
The contributor(s) reserve(s) the right to add, amend or withdraw
material contained herein.
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.21.
The contributor is familiar with IEEE patent policy, as outlined in
Section 6.3 of the IEEE-SA Standards Board Operations Manual
<http://standards.ieee.org/guides/opman/sect6.html#6.3>
and
in
Understanding Patent Issues During IEEE Standards Development
http://standards.ieee.org/board/pat/guide.html>
Proposal for the IEEE 802.21
solution
[email protected]
Outline
• Needed modifications to the Requirements
Document
• Components of the Solution
• MIH Architecture
• Event Indication
• Information Service
• Conclusion
Needed Modifications to the
Requirements Document
• Section 2: Definitions
– Network Selection:
• Current: the process by which a mobile terminal
collects appropriate information and select an L2
link for higher layer communication is called
Network Selection
• Required for the sake of being policy agnostic: the
process by which a mobile terminal or an entity
within the network collects appropriate information
and selects an L2 link for higher layer
communication is called Network selection
Required Modifications to the
Requirements Document
• Section 4: Architecture
– Section 4.1: Intended handover function
should be everything but Media Independant!
Reason:the handover decision making
process should take into account the diversity
of attributes between links to perform the best
selection
Suggestion: Change from Media Independent
(MIH) to Heterogeneous Media Handover
(HMH)
Required Modifications to the
Requirements Document
• Section 4: Architecture
– MIH function is intended to provide services to Internet mobility
and applications layers.
– MIH function is also intended to request services from various
link layers
– This defines a layer
– Actually what has to be standardized within 802.21 is;
• An Heterogeneous/Inter Media Convergence (HMC/IMC) Layer
– Requires time and hard work!
– The Heterogeneous Media Handover function specification
should be let at the discretion of Equipment vendors and
Operators
• Standardized parameters to achieve that function should be
available though (scope of 802.21)
Components of the solution
• Architecture
– MIH function (HMC layer actually)
– Event indication to/HMC
– Information service
• Handover scenarios addressed
– A single 802.11 interface going across ESS (in Phase 1
proposal)
– Handover between GPRS/UMTS and 802.11 interfaces
• Technologies affected by the proposal
– Couple of GPRS/UMTS Specifications in Release 6
– IEEE Std 802.11-1999, IEEE Std 802.11i-2004, IEEE Draft
802.11e-2003
HMC layer
Multi Access Mobile Station
HMC layer functions
• Reception of events reports from various entities of link
types
• Mapping of these events reports into (as much as
possible) generic triggers reports
• Sending of the generic triggers to the Heterogeneous
Media Handover service (or to Higher layer Mobility
Protocols)
• Carrying of Heterogeneous Media Handover Instructions
and Completion messages from Station to Network
– Messages to be defined as part of 802.21 scope
– For the case where Handover Control is handled in the Access
Network
HMC layer at UMTS side
• Architecture placement in protocol stack
– To be eventually figured out by 3GPP!
– Requests from IEEE 802.21 would have to be
adressed to 3GPP describing;
• The intended functions of the HMC layer
• The information reporting types requested by HMC
(periodic, event-triggered, on demand)
• HMC messages transport requirements
– In order for 3GPP to define/select the transport
mechanim (between RRC, RLC, MAC…)
HMC layer at UMTS side
• Architecture placement in protocol stack on
station/network
– UMTS Layers that are provide services to the HMC layer;
• GMM/SM, that performs
– Attachment to the UMTS network
– Mobility Management states handling
– Procedures to activate, deactivate and
Modify a PDP context
• RRC, that performs
–
–
–
–
Station measurements reporting
Requested Data QoS control
Paging control
Initial cell selection/re-selection in idle mode
• RNSAP, that performs
– Cell load measurements reporting
HMC
GMM/SM
RRC
RLC
MAC
LI
UMTS Control plane
protocol stack at MS
HMC layer at UMTS side
HMC
HMC
GMM/SM
GMM/SM
RANAP
RANAP
SCCP
SCCP
Signalling
Bearer
Signalling
Bearer
L2
L2
LI
LI
SGSN
RRC
RNSAP/RRC
RNC
RLC
RLC
MAC
MAC
LI
LI
RNC
Station
UTRAN
Fig.1 UMTS Non-Access and Radio Control Plane
Which link between Joint RRM and HMC/HMH?
Impact of the WLAN/Cellular Integration
Architecture on HMC/HMH operation
• Depending on the coupling model and/or
roaming status
– the importance of the HMC functions between
terminal and network side will vary
– The HMC entity at terminal side will be able or
not to connect to its network peer
– Handover performances will be significantly
different
HMC layer at 802.11 side
• Architecture placement in protocol stack
– To be figured out by IEEE 802.11 Project Task
Groups!
– Requests from IEEE 802.21 would have to be
adressed to IEEE 802.11 describing;
• The intended functions of the HMC layer
• The information reporting types requested by HMC
(periodic, event-triggered, on demand)
• HMC messages transport requirements
– In order for 802.11 to define/select the transport
mechanim (between LLC,MAC…)
HMC layer at 802.11 side
• Architecture placement in protocol stack on
station
– 802.11 layers that are to provide services to the HMC
layer
• From 802.11 MAC, that performs
–
–
–
–
Association/Re-association functions
QoS provisionning (defined by 11e)
Security functions as part of 11i exchange
Radio Resources Management (11k, WNM…)
• From 802.11 PHY, that provides
– Station Measurements of Received Signal
Strength and Quality
HMC
LLC
MAC
PHY
802.11 STA
HMC Messages
• Functions
– Establishment/Release of the Heterogeneous Media Convergence
session between HMC peers (station and network sides)
• The ability for the station to establish such a session would signify that the
Handover service can be delivered by the network
– Request for handover to a particular link (for instance coming from
applications)
• Such a request would be either locally adressed (within the HMH function in
the terminal) or remotely (HMH function in the Network)
– Handover Instruction (typically arrived from the Network)
– Acknowledgement of the Handover Completion (directed to HMC peer
in the network)
• The Heterogeneous Handover Function would then update the information
service with the newly confirmed station location (out of scope though)
• Semantics
– To be determined during protocol design phase
HMC interaction with upper layers
• Important 802.21 requirement
– Higher layer mobility protocols shall be supported
• Interface between an L3MP/HMH and the HMC layer:
– HMC reported events can be directly used for example by the
Mobile IP layer for care-of address re-selection
• Effort for IETF recommendations document will have to be initiated
for consideration in the 802.21 solution design
– HMC reported events can also be sent to an Heterogeneous
Media Handover function
• Interface with Applications
– Applications should be able to generate handover requests to
the HMC function: these requests would be either processed
locally or relayed to the network
• Implementation specific
Architecture at station side
Applications
Mobile IPv4/v6
Host Identity Protocol
FMIPv4/v6
Other L3MPs
Heterogeneous Media
Handover Function
802.21
HMC layer
GMM/SM
RRC
RLC
LLC
MAC
MAC
PHY
LI
Transport for HMC messages
• 3GPP
– UMTS
• RRC?? Needed extensions to be defined
– GPRS
• LLC/RLC?? Needed extensions to be defined
• IEEE 802.11
– MAC??
• Complete the Definition of an Heterogeneous Media
Information subtype of the Management frame
– LLC??
HMC SAPs and Service Primitives
• Not Part of this Proposal !
Event Indication to HMC
• UMTS events station/network side
– From GMM/SSM layer
– UMTS station has attached to the network
• Station_attached (Station/SGSN to HMC layer, PLMN ID,
Cell and/or Routeing Area Identity, Authentication and
ciphering algorithm used, key length…)
• Effect on receipt: out of scope
• Recipient: local
– UMTS station has detached from the network
• Station_detached (Station/SGSN to HMC layer, reason)
• Effect on receipt: out of scope
• Recipient: local
Event Indication to HMC
• UMTS event at station/network side
– From GMM/SM layer
– Change in the Mobility Management state
• Mobility_Management_State_Changed (Station/SGSN to HMC
layer, precedent MM state, new MM state)
• Effect on receipt:
• Recipient: local
– PDP context has been activated
• PDPcontext_is_activated (Station/SGSN to HMC layer, PDP type,
PDP state, QoS profile requested, QoS profile negotiated, APN
requested)
• Effect on receipt:
• Recipient: local
Event Indication to HMC
• UMTS event at station/network side
– From GMM/SM layer
– PDP context has been modified
• PDPcontext_is_modified (Station/SGSN to HMC layer, PDP type,
PDP state, QoS profile requested, new QoS profile negotiated,
APN)
• Effect on receipt:
• Rcipient: local
– PDP context has been deactivated
• PDPcontext_is_deactivated (Station/SGSN to HMC layer, PDP type,
PDP state, QoS profile requested, new QoS profile negotiated,
APN)
• Effect on receipt:
• Recipient: local
Event Indication to HMC
• UMTS event at station/network side
– Physical Layer Measurement Report available (RRC
layer)
• Measurement_report_available (Station/RNC to HMC layer,
report)
• Effect on receipt:
• Recipient: local
– Cell Load reaches High thresold (RNSAP layer)
• Cell_load_reaches_high_thresold (Station to HMC layer in
Station/Network)
• Effect on receipt:
• Recipient local/remote
Event Indication to HMC
• IEEE 802.11 event at station/network side (optionally
11e/11i compliant)
– STA has associated to an Access Point
• Station_associated (Station/AP to HMC layer, BSSID of AP, SSID,
RSN Elements)
• Effect on receipt:
• Recipient: local
– STA has deassociated
• Station_deassociated (Station/AP to HMC layer, reason)
• Effect on receipt:
• Recipient: local
– STA has changed Operational Mode
• Station_mode_changed (Station/AP to HMC layer,previous mode,
new mode)
• Effect on receipt:
• Recipient: local
Event Indication to HMC
• IEEE 802.11 event at station/network side
– EAP Authentication has succeeded
• EAP_auth_successful (Station/AP to HMC layer in station/network)
• Effect on receipt:
• Recipient local/remote
– Received Signal Strentgh Indicator value reaches low threshold (PHY
layer)
• RSSI_reaches_low_thresold(Station to HMC layer in station/network)
• Effect on receipt:
• Recipient local/remote
– Received Signal Quality Indicator value reaches low threshold (PHY
layer)
• RSQI_reaches_low_thresold(Station to HMC layer in network)
• Effect on receipt:
• Recipient:remote
Event Indication to HMC
• EEE 802.11 event at station/network side (MAC layer)
– STA data QoS attributes have changed
• Data_QoS_attributes_changed (Station/AP to HMC layer, requested
QoS profile, new QoS profile)
• Effect on receipt:
• Recipient: local
– QoS BSS maximum admission capacity reached
• QoS_BSS_max_admission_capacity_reached (AP to HMC layer,
BSSID of AP)
• Effect on receipt:
• Recipient: local
• The HMC layer may want event indications also from 11k,
11u, 11v when those become available!
Mapping between link specific and
Generic events
From UMTS
From IEEE 802.11 (e,i)
Generic
Station_attached
Station_associated
Link_up
Station_detached
Station_deassociated
Link_down
Mobility_management_state_changed
Station_mode_changed
data_traffic_state_changed
PDP_context_is_activated
EAP_auth_successful (802.11i with
EAP) )
IP_configuration_valid
PDP context_is_modified
Data_QoS_attributes_changed
Data_QoS_attributes_changed
PDP_context_is_deactivated
IP_configuration_not_valid
Ciphering_conditions_modified
(event sent to HMC uppon reception of
station_attached)(
(tbi)
Link_security_attributes_change
d
Measurements_report_available
Measurements_report_available
Measurements_report available
(tbe)
RSQI_reaches_low_thresold
Link_signal_quality_degraded
(tbe)
RSSI_reaches_low_thresold
Link_signal_level_down
Cell_load_reaches_high_thresold
QoS_BSS_max_admission_capacity
_reached
RAP_load_critic
Event Indication to an HMH
function (when used)
• The HMC layer registers and receives event indications
from specific link layers technologies
• It transcodes them as much as possible into generic
events
• The HMC layer relays the newly formatted event
indications to the HMH function that uses them in the
handover decision making process
• Higher Layer Mobility Protocols will be consumers of the
HMH function provided information
– HMH function messages to Higher Layer Mobility Protocols have
to be implemention specific
– They can carry Handover instructions to be enforced by Higher
Layer Mobility protocols as Mobile IP
Event Indication to HMH/Higher
Layers
• Wireless link is established
• Link_up (From Station/RAP, Link Type, Radio Access Point
ID, Link Provider ID, Security Context Data)
• Effect on receipt:
• Recipient:local
• Wireless link is teared down
• Link_down (From Station/RAP, Link Type)
• Effect on receipt:
• Recipient: local
• Status of data traffic on link changed
• Data_traffic_status_changed (From Station/RAP, Link Type,
precedent state, new state)
• Effect on receipt:
• Recipient: local/remote
Event Indication to HMH/Higher
Layers
• Station ready to send/receive data traffic
• IP_configuration_valid (Link Type, Negotiated Security and QoS
Context, External Data Network Requested)
• Effect on receipt:
• Recipient:local
• Data QoS attributes have been modified
• Data_QoS_attributes_changed (Link Type, Requested QoS profile,
Re-negotiated QoS profile)
• Effect on receipt:
• Recipient: local
• Link Security attributes have been modified
• Link_Security_attributes_modified (Link Type, Re-negotiated
Security Context)
• Effect on receipt:
• Recipient: local
Event Indication to HMH/Higher
Layers
• Measurement report is available
• Measurement_report_available (Link Type, Report)
• Effect on receipt: Read values
• Recipient:local
• Radio link level has reached low thresold
• Link_signal_level_down (Link Type)
• Effect on receipt:
• Recipient: local/remote
• Radio link quality has reached low thresold
• Link_signal_quality_degraded (Link Type)
• Effect on receipt:
• Recipient: local/remote
Event Indication to HMH/Higher
layers
• Radio Access Point load is critic
• RAP_load_critic (Link Type)
• Effect on receipt:
• Recipient: local
• Station can no more send/receive data traffic
• IP_configuration_deleted (Link Type)
• Effect on receipt:
• Recipient:local
• HMC entity at station has registered to peer in
the network
• HMC_entity_registered (Link Type)
• Effect on receipt:
• Recipient: remote
Overall Architecture Framework
Integrated
Access
Network
Information
service
Multi-Access
Station
Information
service
Heterogeneous Media
Handover Function
Heterogeneous Media
Handover Function
802.21
HMC layer
HMC layer
802.21
GMM/SM
RANAP
HMC layer
RNSAP
GMM/SM
SCCP
RRC
Signalling
Bearer
L2
RRC
LLC
RLC
LLC
RLC
MAC
MAC
LI
LI
UTRAN
PHY
WLAN
Radio
Controller
WLAN RAN
MAC
LI
MAC
PHY
Information Service
• Station:
– Preferred access links/networks for the station (link type with
provider IDs -PLMN/SSIDs list)
– Barred access networks (associated provider IDs -PLMN/SSIDs
list)
– Level of QoS required by different applications
– Subscription type (roaming profile, billing profile…)
– Specific link type static attributes
• Network:
– Characteristics of the radio access network at particular
locations (Cell size and capacity, Access Point capabilities…)
– preferred and/or forbidden SSID/PLMN list
Conclusion
• Requirement Document should be reviewed
• A lot of work still ahead
– Design of the HMC Layer/function for Heterogeneous Media
Handover
• 802.21 can not handle the work alone
• Need to synchronize with other SDOs efforts on Inter-Media
Handover (eg: Joint Radio Resource Management work item of
3GPP)
• Can we complete the design of that HMC layer within the time frame
announced for a solution? (considering the above points)
– Generic link layer triggers
• Can we complete the work of mapping specific events and
parameters from various technologies to their generic peers within
the time frame announced for a solution?