Download 21-06-0472-00-0000-Handover_Use_Case_More_IEs

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

IEEE 1355 wikipedia , lookup

Wireless security wikipedia , lookup

Net bias wikipedia , lookup

WiMAX wikipedia , lookup

Distributed firewall wikipedia , lookup

Piggybacking (Internet access) wikipedia , lookup

Computer network wikipedia , lookup

IEEE 802.11 wikipedia , lookup

Zero-configuration networking wikipedia , lookup

Network tap wikipedia , lookup

Cracking of wireless networks wikipedia , lookup

Airborne Networking wikipedia , lookup

Transcript
21-06-0472-00-0000-Handover_Use_Case_More_IEs
IEEE 802.21 MEDIA INDEPENDENT HANDOVER
DCN:21-06-0472-00-0000-Handover_Use_Cases_More_IEs
Title: Handover Use Cases and Additional IEs
Date Submitted: January 2006
Presented at IEEE 802.21 session #12 at Hawaii
Authors or Source(s):
Dave Wisely, Steve Buttery : British Telecommunications
Vivek Gupta: Intel Corporation
Abstract: This is an operator’s view point on some use cases for
Handovers and need for additional IEs
21-06-0472-00-0000-Handover_Use_Case_More_IEs
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>
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Handover Use Cases and Additional IEs
(Operator’s View Point)
Dave Wisely, Steve Buttery
British Telecommunications
Vivek Gupta
Intel Corporation
Slide 3
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Agenda
• Handover: Use Cases
• Dynamic Information Elements
• Additional Information Elements
Slide 4
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Use case 1 – Cyclist through hot spot
•
Description
– Cyclist on a WiMAX network cycles through a WLAN hotspot
•
Network Handovers
– WiMAX to WLAN to WiMAX (if this can be achieved quickly enough to be of use – eg
may be streaming video from bike cam)
•
Key Information service parameters
–
–
–
–
•
Emergency call support (requires to have this at all times)
WLAN power consumption (whether has power saving features enabled)
WLAN hand-in and hand-out times
Pre-authentication possible at WLAN
Value chain relationship
– Cyclist is subscriber to Service Provider (SP) A that is also a Network Operator (NO) and
has extensive roaming agreements
•
Handover decision point
– SP makes handover decisions and terminal must send parameters about available network
– User is unaware of network change and not able to influence handover in any way
Slide 5
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Use case 2 – Business Group on train
•
Description
– A group of businessmen are traveling on a train – they are sharing a single external
connection via a PAN (Personal Area Network)
•
Network Handovers
– Currently one is on 3G (data, voice and video) and needs to decide if a handover to the
onboard WLAN is sensible (this is hard without knowledge of the train backhaul network
characteristics)
•
Key Information service parameters
–
–
–
–
•
Support for Gold users (eg priority)
Broadcast/multicast support (to enable colleagues in other locations to join session)
Encryption strength (do we need VPN?)
QoS (Max/min/typical bandwidth, latency, jitter)
Value chain relationship
– Terminals supplied by company – can only connect to approved networks
•
Handover decision point
– All decisions are made by remote corporate server (3G is default)
– User agent send info on available networks to corporate server for decision
Slide 6
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Use case 3 – Users on a Bus
•
Description
– A coach is taking holiday makers to the seaside – the coach offers an on-board WLAN but
connects to a variety of back haul networks as it finds them
•
Network Handovers
– The Bus is doing the handover and “sees” a variety of WLAN and WiMAX networks as
well as universal GPRS – it needs to decide which one(s) to connect to
•
Key Information service parameters
–
–
–
–
–
•
Globally routable IP@
Handover in and out times
Coverage extent (no point joining to leave soon after)
Maximum speed of mobility support (fast bus!)
QoS (Max/min/typical bandwidth, latency, jitter)
Value chain relationship
– Bus offers internet connectivity free as part of services and connects to cheapest network
•
Handover decision point
– All decisions are made by bus router
– See enclosed work on ASCOT project fro more details
Slide 7
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Use case 4 – Orienteering Gamer
•
Description
– A team is playing a game that requires precise location control and very low latency
between participants. An external server is controlling the game
•
Network Handovers
– From 3G to WiMAX to WLAN and back to 3G (if WLAN and WiMAX networks can
support the game)
•
Key Information service parameters
–
–
–
–
–
–
•
Globally routable IP@ (required by game)
Firewall and NAT restrictions (game requires open ports)
Handover in and out times
Latency
Packet error rates
Location accuracy
Value chain relationship
– Content provider is being paid by games users – they also need to pay the SP fro network
services
•
Handover decision point
– Game installation has installed small control add-on that recovers network info service
parameters and decides if networks are suitable for the game
Slide 8
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Use case 5 – Indigent student
•
Description
– Student needs very cheap calls and always lowest price
•
Network Handovers
– WiMAX to WLAN (frequently)
•
Key Information service parameters
–
–
–
–
•
Cost
Current congestion
Hand-in and hand-out times
Seamlessness of handovers
Value chain relationship
– Student uses external service (semi-legal) that supplies log-on information about WLAN
APs and buys pre-pay WLAN and WiMAX one-time passwords in bulk and re-sells them
•
Handover decision point
– By installed app on terminal that is in constant contact with external server
Slide 9
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Extensions to 802.21 Info services (Dynamic info)
Info Service
(Static)
Future
Locations
Location
Available
Networks
Possible
Networks
Possible
Networks
Congestion
information
Future
Locations
Basic
Info Service
(Static) Client
Info Service
(Dynamic)
Congestion
Report
Advanced
Service
Client
Slide 10
Third party
Server (SP or 3P service)
Handover Plan
Authentication keys
One time vouchers
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Info Service Elements (1)
Name of Info Element
Description
Comments
Network Capability list
List of common capabilities
(presence
Mobility etc)
21C is based on CCs – so 21C
service will need a sub set to
be supported
Network Service list
Eg could use OMA services
that are being specified fro
inter -operability
Can the service (eg weather)
be supported on the local
network?
Cost of basic services
Voice ppm, video, price per
MByte data
Needs careful definition of
basic services
Pre-authentication and CAC?
Does network offer a pre
handover authentication (via
SP or NO?) and a session
admission
Would greatly speed
handovers
Emergency service support
Does the network offer
112/911 support
Might be a requirement to
always have 1 network with
this
Slide 11
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Info Service Elements (2)
Name of Info Element
Description
Comments
Proxy terminal network
support
Allows access to information
services – terminal can
request info about FUTURE
locations
Can be used for smart network
selection (see slide on
dynamic services)
Static/dynamic network
parameter support
Eg is information about
congestion available?
Need up to date congestion
information to make sensible
hand-over decisions
Class of user supported
Eg Gold. Silver, Bronze
Gold users might want to only
use networks that support min
(Gold) service award
characteristics
Latency
Typical, Max,Min
Current (Dynamic)
Needed for real-time apps
Jitter
Typical, Max,Min
Current (Dynamic)
Needed for real-time apps
Slide 12
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Info Service Elements (3)
Name of Info Element
Description
Comments
Location information
Format
Resolution
Some Services need very
precise location info
IP Address
V4/v6
Globally routable?
Certain apps will require a
globally routable address
Firewall Restrictions
Blocked services
Blocked ports
No point handing over to a
network that blocks your
service (eg Voda and VoIP)
NAT
Does the network use NAT?
Certain apps (eg Skype) don’t
work properly with NAT
Encryption support
AES.TKIP etc
Key length
Tells user if VPN is required
on top of encryption
Slide 13
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Info Service Elements (4)
Name of Info Element
Description
Comments
Bandwidth
Max, Min, Typical (up)
Max, Min, Typical (down)
Current (dynamic)
Need to know what sort of
bandwidth a network will
offer (preferably in real-time)
Power consumption
Typical consumption figure
for network (say 1 to 10)
Some networks of the same
type may implement different
power saving features
Coverage
100%? 90%
No point using a network with
patchy coverage if continuous
connections are required
Cell size
Typical, Max, Min
Handovers can fail and need
power/signalling
Mobility speed supported
Max handover speed
Bicycle, fast car …
Slide 14
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Info Service Elements (5)
Name of Info Element
Description
Comments
ARQ speed on link layer
Eg 2ms
Much better on 802.20 –
might be needed by some apps
Breakout options
Eg PSTN or Circuit mobile
Terminal might want to break
out of IP to PSTN close to
destination
Multicast support
Supported?
Needed for group-based
services
Broadcast support
Supported?
Eg Tsunami warnings
Hand-over times
Hand-in and hand-out times
(Max,min and typical)
Could be too slow to be useful
Slide 15
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Info Service Elements (6)
Name of Info Element
Description
Comments
Seamless handovers
Supported?
Horizontal (eg WLAN to
WLAN) and vertical (eg
WLAN to WiMAX)
Lossless and “speedy”
Lossless handovers
Supported?
Horizontal (eg WLAN to
WLAN) and vertical (eg
WLAN to WiMAX)
No packets lost
Priority support
Force handover possible
Eg in Fusion need to go to
Bluetooth as soon as detected
– absolute priority.
Slide 16
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Conclusion
• Handover decision making requires additional IEs
beyond just static Neighbor Graphs
– Specially for less managed networks like 802.11
• In some cases this may be Dynamic information
– Can be provided separately as a value add feature
– Values can be provided as (Typical, Min, Max) to take
into account regular/dynamic updates
• Most of these IEs need to be computed and are not
directly provided even by different access networks
– 802.21 can provide additional services above and beyond
those provided directly by different access networks
Slide 17
January 2006
21-06-0472-00-0000-Handover_Use_Case_More_IEs
Feedback?
Slide 18