Transcript 21-04-0164-04-0000-Freescale_March2005

• IEEE 802.21 MEDIA INDEPENDENT HANDOVER
• DCN: IEEE802.21-05-0164-04-0000
• Title: Optimal Beacon & Architecture for MIH
• Date Submitted: March 4, 2005
• Presented at IEEE 802.21 in Monterey, CA
• Authors or Source(s): Michael Hoghooghi, Karl Heubaum, Jeff
Keating, Dan Orozco, Michael Lee
•
Freescale Semiconductor, Inc.
• Abstract: This contribution aims to facilitate MIH services for mobile
nodes & networks able to support multiple protocols while adhering to
the requirements of the IEEE802.21 WG.
21-05-0164-04-0000
Slide 1
Freescale Semiconductor, Inc.
Hoghooghi, et al
•
•
•
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>
21-05-0164-04-0000
Slide 2
Freescale Semiconductor, Inc.
Hoghooghi, et al
IEEE802.21 – Media Independent Handover
Optimal Beacon & Architecture for MIH
Freescale Semiconductor, Inc.
DCN: IEEE802.21-05-0164-03-0021
Michael Hoghooghi
Karl Heubaum
Jeff Keating
Michael Lee
Daniel Orozco
21-05-0164-04-0000
Slide 3
Freescale Semiconductor, Inc.
Hoghooghi, et al
Overview
• Considerations for mobility and HO
• Network MIH Beacon
• Focus on events and triggers
• Focus on intra-layer communication to facilitate
handover process
• Focus on MIH call flows between protocol
technologies
• Scope matrix & MIH call flow
• Summary
21-05-0164-04-0000
Slide 4
Freescale Semiconductor, Inc.
Hoghooghi, et al
Connection Analysis
Cellular BTS
BSC-1
BSC-2
....
BSC-n
STA-1
AN
HTTP Server
BSC
STA-2
Internet
AP-1
STA-n
FTP Server
STA-1
....
PDSN
AP-2
STA-2
Ethernet
STA-n
Video Server
AP-n
21-05-0164-04-0000
Slide 5
Freescale Semiconductor, Inc.
Hoghooghi, et al
Transport Protocol & MIH Function
(Based on v.12, 21-04-0087-12-0000)
• No restrictions on use of any transport protocol to exchange MIH function
events between STA Fn-Entity & Net Fn-Entity
Mgmt
L3
App
Mgmt
MIHSignaling
MIHFunction
L3
App
MIHFunction
MAC
LLC
Function
PHY
MACFunctions(802.xx)
802.yy
PHYFunction(802.xx)
PHY
802.yy
MACFunction(802.xx)
LLCFunction
PHYFunctions(802.xx)
Station Functional Entity
21-05-0164-04-0000
MAC
Data
Network Functional Entity
Slide 6
Freescale Semiconductor, Inc.
Hoghooghi, et al
MIH Recommendations for Mobility & HO
Important mobility enablers

Network capability ID – modified Beacon (MIH-Beacon)
 Fits into existing protocols and may vary one to another protocol, in
placement
 Minimal protocol impact with optimized channel utilization and
spectral efficiency.
 Broadcast existence of network

Triggers





Seamless handover and service continuity
Events occur and fire triggers
Beacon is also a trigger
Mobile node <---> Network actions
Layer communications



MIH layer down the stack
QoS issues
Handover selection decisions
21-05-0164-04-0000
Slide 7
Freescale Semiconductor, Inc.
Hoghooghi, et al
Logical HO Views
• Interoperability to facilitate smooth network handover
• All traffic types & payload converge on the Ethernet level – follow MoIPv6
(preferred) rules

Home-Adr, c/o-Adr, subnet fields, etc.
• Service engine plays a big role on Fast-HO


Enables native & non-native traffic flows
Net-controller can harmonize, when needed
>>
802.11
802.16
. ... .
MoIP addressing over Ethernet
Cellular
MAC-xx
MAC-xx
MAC-yy
MAC-zz
PHY-xx
PHY-xx
PHY-yy
PHY-zz
21-05-0164-04-0000
Slide 8
Freescale Semiconductor, Inc.
Hoghooghi, et al
MIH-Beacon Direction
1.
Network to broadcast MIH beacon



2.
Mobile Node to scan for MIH-Beacon in background



3.
Periodic broadcast
Beacon contains MIH capabilities of network
Beacon can indicate MIH capability and details stored
MN decide when want to roam onto a new network
Exchange basic capabilities with network during registration
Capabilities exchanged during registration process
Modifications needed to protocol


New management message (or other appropriate frame) to indicate MIH
beacon – communicate MIH capabilities
New data type to define capabilities, per recommendations
21-05-0164-04-0000
Slide 9
Freescale Semiconductor, Inc.
Hoghooghi, et al
MIH Network Selection
Power-Up Example Scenario
1.
Upon power-up, MN scans for MIH beacon


Scan MN native mode first then proceed to other modes, if needed
Immediately register in native mode, if available
2.
If receive beacon from multiple networks, determine and track network
types – could use influence from service engine, etc.
3.
MN needs to determine primary function


4.
Adherence to service engine rules to determine network selection
Link metrics will influence decision to associate, or not
Register with that network
21-05-0164-04-0000
Slide 10
Freescale Semiconductor, Inc.
Hoghooghi, et al
Content of MIH Beacon Message
MAC
Header
•
QOS
Level
APPL
CLASS
(4 Bits)
(4 Bits)
NET-TYPE
Carrier ID
(4 Bits)
(32 bits)
TRUST
CAPACITY
EXTENDED
LEVEL
(4 Bits)
SERVICES
(4 Bits)
CRC
(4 Bits)
Optimization methods



MIH-Capability (MIHC) flag  TRUE or FALSE (1 bit)
Most spectrally efficient option (also provides rapid cognition)
If MIHC is true, several options may be implemented


MN could query the network for additional details or share its capability info
Service engine may perform the lookup to get MIH details, i.e. each field maps
to a lookup table for decode

New fields to consider: MoIP-ver (2 bits), location (relative or absolute),
device/user preferences, etc.

If MIHC flag is not set, there may be other options for the MN



It could still register with the network
Send its visiting net info to its native net along with routing
Service engine could determine association or other options
21-05-0164-04-0000
Slide 11
Freescale Semiconductor, Inc.
Hoghooghi, et al
Capability Advertising
Who advertises this information and how frequently is it done?
• MIH-Beacon information may be exchanged by the network controller only
during association with the MN
 Or, it may be exchanged more frequently – in this case MN may choose
to look for this only when required, or it may choose to battery-save
otherwise
• Neighboring networks advertised


Network controller (assuming it is MIH capable) will share this information
MIH capable MN may periodically scan for supported protocols and report results
to network controller or the service set



This ability distributes the detection burden (power & time)
Extends beyond network boundaries (if left only to network controller)
Does not affect non-MIH MN
21-05-0164-04-0000
Slide 12
Freescale Semiconductor, Inc.
Hoghooghi, et al
MIH Logical Stack Interfaces
Application
Network
Convergence
Mobility Mgmt
LLC
- User Preferences
- Net. operation preference
- Applications
MM-SAP
MIH Mobility
Management
Convergence
MIH-MM-SAP
MAC-SAP
MAC 802.X/3GPP
MIH Handover
Control
MIH-PHY-SAP
PHY-SAP
PHY 802.X/3GPP
21-05-0164-04-0000
Slide 13
MIH Physical
Convergence
Freescale Semiconductor, Inc.
Hoghooghi, et al
MIH Block Within the Stack
Application
Network
Convergence
Mobility Mgmt
LLC
- User Preferences
- Net. operation preference
- Applications
MIH Mobility Management
Convergence
MIH Handover Control
Mobility Events
MIH
MIH Physical Convergence
MAC Events
MAC 802.X/3GPP
PHY Events
PHY 802.X/3GPP
21-05-0164-04-0000
Slide 14
Freescale Semiconductor, Inc.
Hoghooghi, et al
MIH Layer Descriptions
MIH Mobility Management Convergence
• Processes user/network requests based on defined preferences and network configurations and
submits actions to the MIH Handover Control sub-layer
MIH Handover Control
• Processes MAC layer events and QoS-related network events
• In response to submitted actions, executes handover function and performs handover sequence
between all MIH layers
MIH Physical Convergence
• Processes RF-related indicators and submits actions to the MIH Handover Control sub-layer
21-05-0164-04-0000
Slide 15
Freescale Semiconductor, Inc.
Hoghooghi, et al
MIH Layer Interface Descriptions
MM-SAP
• Carries messages of user preferences, network operation preferences, and applications between
the MIH and MM
MAC-SAP
• Carries network triggers and QoS parameters required by the handover control sublayer.
PHY–SAP
• Carries RSSI, BER, CINR and RF-related parameters required by the handover control sublayer.
MIH-MM-SAP
• Carries requests, commands, and services required by the handover control sublayer.
MIH-PHY-SAP
• Carries link quality and RF-related parameters required by the handover control sublayer.
21-05-0164-04-0000
Slide 16
Freescale Semiconductor, Inc.
Hoghooghi, et al
MIH Triggers
Trigger Designation
Event Reported
Source
Propose nomenclature for
this trigger. E.g.,
MIH_HO_PREPARE,
MIH_Event_Indication
It refers to the nature of
the event that is being
reported. E.g., Link on
connected interface is
unavailable
It describes the
entity that
originated the
trigger. E.g.,
802.11 MAC
layer
MIH.MAC.QoS
Lack of bandwidth
and/or other QoS
parameter definitions.
MAC
Sender
When generated
It describes the
entity
responsible for
sending the
trigger from the
source. E.g.,
MIH_SAP
It describes the series
of events, conditions
and/or behavior that
prompted the Source
of this trigger to fire it.
E.g., QoS thresholds
being crossed
MAC-SAP
Use existing transports
below L3.
QoS thresholds
QoS element values
QoS thresholds
Use existing transports
above L3.
Cost thresholds.
Cost value.
Cost thresholds.
Use existing transports
above L3.
Priority preference
table.
Priority level.
Priority preference
table.
MM-SAP
User commands.
MIH Mobility
Management
Convergence
MIH Mobility
Management
Convergence
Submit user
initiated action to
MIH HO Control local trigger
Use existing transports
above L3.
User preferences. User input.
User preferences.
Network supported
applications.
MIH Mobility
Management
Convergence
MIH Mobility
Management
Convergence
Submit
application
initiated action to
MIH HO Control local trigger
Use existing transports
above L3.
Application
parameters.
Application
parameters.
Preferred network.
21-05-0164-04-0000
Receipt of a beacon
and associated
parameters.
MM-SAP
MIH.MOB.ROAM_PRIO
MM
QoS level, Appl class,
Net-type, Carrier ID,
Trust level, Capacity,
Extended Services
Submit costinitiated action to
MIH HO Control local trigger
Submit network
priority action to
MIH HO Control local trigger
MM-SAP
User applications.
QoS level, Appl
class, Net-type,
Carrier ID, Trust
level, Capacity,
Extended Services
MIH Mobility
Management
Convergence
MIH Mobility
Management
Convergence
MIH.MOB.COST
MIH.MOB.APPL
Based on QoS parameter
definition for bandwidth, Based on QoS
i.e. min/max bitrate
parameter definition
MIH Mobility
Management
Cost or Free.
Convergence
MIH Mobility
Primary/home network Management
detected.
Convergence
Network service fee only
in terms of "tariff or free" MM
MM
Based on QoS
parameter
definition
Use existing transports
below L3.
PHY-SAP
MM-SAP
MIH Handover Control
Slide 17
Initiates
handover
sequence.
Configuration
Option
QoS parameters as MIH Physical
reported through PHY. Convergence
MIH.PHY.RRM
User preferences.
Mobility Mgmt
appl is executed
via the Mob
Mgmt conv layer
QoS processing
and as a result,
function within MIH passed back to
HO Control layer
MIH HO Control local trigger
Proposed Transport
Options (s)
Beacon detected.
RSSI, BER/PER,
latency, jitter, and other
PHY QoS elements
PHY
MIH.MOB.USER
QoS thresholds being
crossed.
MIH Handover Control
Effect of receipt Trigger Scope
MAC-SAP
MIH.MAC.NETWORK
MM
Destination
Beacon processing
within MIH
Handover Control
PHY QoS
processing function
within MIH PHY
Conv Layer (CL).
Beacon message
received.
MAC
Configuration
Parameter and
Trigger Description
Information Elements
It describes the entity
It describes the
It describes the It describes
It describe the transport
It specifies what It specifies all parameters It summarizes the
responsible for receiving entity that processes behavior at
whether a
mechanisms that are
parameters are provided by the trigger, characteristics of a
the trigger at the
the trigger. E.g., MIP destination upon trigger has
required. E.g., Whether L2 configurable and both configurable and
triggers in terms of the
destination. E.g., MM
stack
receipt of the
local or remote or L3 transport is used,
what is the entity dynamically set
conditions that cause
entity
trigger. E.g., L3 scope. If a
Whether existing protocols that handles their parameters. E.g., Inter- the triggers to be fired
handover is
trigger has
or new protocols are used. configuration. E.g., technology Capabilities, and the expected
triggered.
remote scope What are the precise end
Throughput
Measured throughput.
behavior at the
then the
points, What is the structure thresholds set at
receiving side.
transport
of the frame, What are the the MIH layer
option must be required parameters
specified.
parameters and options
Receiver
Use existing transports
remote trigger below L3.
Submit PHY-QoS
actions to MIH
HO Control
local trigger
Freescale Semiconductor, Inc.
Application.
Hoghooghi, et al
Event & Link Triggers
• Authorized MIH Capable
• PHY RRM







Force to leave network roamed
to, if needed
 Pay for feature access
Signal strength (RSSI)
BER
CINR/SNR
Loss of link
Better link available
Link error occurred
• User-selected preferences
• Applications
• Network billing cost
• MAC QoS





Bit rate
Voice quality
Jitter
Bandwidth availability
Traffic congestion
• MIH Preferences

Roam priority

i.e. Home, .11, .16, etc.
21-05-0164-04-0000
Slide 18
Freescale Semiconductor, Inc.
Hoghooghi, et al
Event & Link Triggers
Trigger Name
Source
Destination
MIH.MOB.COST
MIH.MOB.ROAM_PRIO
MIH.MOB.USER
MIH.MOB.APPL
MIH.MAC.NETWORK
MIH.MAC.QoS
MOB
MOB
MOB
MOB
MAC
MAC
MIH Mobility Mgmt Conv
MIH Mobility Mgmt Conv
MIH Mobility Mgmt Conv
MIH Mobility Mgmt Conv
MIH Handover Control
MIH Handover Control
PHY
MIH Phys Conv





Bit rate
Voice quality
Jitter
Bandwidth availability
Traffic congestion
MIH.PHY.RRM






BER
Signal strength (RSSI)
CINR/SNR
Loss of link
Better link available
Link error occurred
21-05-0164-04-0000
Slide 19
Freescale Semiconductor, Inc.
Hoghooghi, et al
MIH Call Flow
Multimode STA
HL
MIH
Function
MIH Mobility Conv
Old Point of Attachment
LL
LL
MIH
Function
New Point of Attachment
HL
LL
MIH
Function
Local
Trigger
HO Rqst
MIH HO Control
MIH PHY Conv
Beacon Message
Handover association request and SS basic parameters
Query current network
Obtain subscriber details
Handover grant
Activate on new network
21-05-0164-04-0000
Slide 20
Freescale Semiconductor, Inc.
Hoghooghi, et al
HL
Cellular Handover Example
Mobile Downward – “to” Cellular handover
•
•
•
•
•
•
•
•
•
•
Weak signal detected from current network
Access the cellular channel
Receive agent advertisement from cellular network
Handoff ready request from MN to cellular network
Data packets begin buffering in cellular network
Routing update completed
Assignment of cellular traffic channel
MN registers on the cellular network
Buffered packets are forwarded to MN
Disassociation with previous network
Mobile Upward – “from” Cellular handover
•
•
•
•
•
•
•
MN receives strong beacon from new network
Receive agent advertisement from cellular network
Handoff ready request from MN to cellular network
Traffic channel release request from MN
Reassociation request to new network
Data packets forwarded to new network
Release completed
21-05-0164-04-0000
Slide 21
Freescale Semiconductor, Inc.
Hoghooghi, et al
Media Independent Handover Proposal
Scope Matrix for Discussion Part-I
Core Elements
Event Service Information
Service
MIHO
Support
MIH
Reference
Model
802.3
to/from
802.X
802.3
to/from
3GPP
802.3
to/from
3GPP2
802.X
to/from
802.Y
802.X
to/from
3GPP
802.X
to/from
3GPP2
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
21-05-0164-04-0000
- Addressed
Network
Discovery
Other Elements
Transport Special HL Security
Support
Schema
QoS
Schema
Other
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
- Addressed
Slide 22
Freescale Semiconductor, Inc.
Hoghooghi, et al
Media Independent Handover Proposal
Scope Matrix for Discussion Part-II
MIHO
Support
802.3
to/from
802.X
802.3
to/from
3GPP
802.3
to/from
3GPP2
802.X
to/from
802.Y
802.X
to/from
3GPP
802.X
to/from
3GPP2
21-05-0164-04-0000
Station Initiated –
Station Controlled
Architectural Precepts of the Proposal
Station Initiated –
Network Initiated –
Network Controlled Station Controlled
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
- Supported
Slide 23
Network Initiated Network Controlled
Freescale Semiconductor, Inc.
Hoghooghi, et al
Summary
• Key points:



Beacon message to indicate network presence and MIH capability
MN capable of querying network for capabilities
MN can associate with newly detected network
• Updated information on triggers to initiate handover
• SAPs defined to carry information between MIH and other
layers
• Processing of triggers done at specific blocks within MIH
layer
• Call flow example to show how handover would be done
using beacon as trigger
21-05-0164-04-0000
Slide 24
Freescale Semiconductor, Inc.
Hoghooghi, et al