21-06-0659-00-0000

IEEE 802.21 MEDIA INDEPENDENT HANDOVER

DCN: 21-06-0659-00-0000

Title: Initial feedback by FMCA on IEEE 802.21 questions

Date Submitted: May, 12th, 2006

Presented at IEEE 802.21 session #14 in Jacksonville, USA

Authors or Source(s):

 Rob Glassford (BT), Rodrigo Donazzolo (FMCA)

Abstract: Initial feedback from FMCA on IEEE 802.21 questions and a liaison update.

21-06-0659-00-0000

Discussion Items

• FMCA – IEEE 802.21 Engagement

• Initial Feedback on IEEE 802.21 questions for FMCA

• Initial Feedback on IEEE 802.21 comments on PRD Matrix

• Converged Applications & Device Management Requirements

21-06-0659-00-0000

Engagement History to date

• March IEEE 802.21 Meeting: • FMCA shared a Wi-Fi SIP PRD Release 1.0 Matrix showing

key product requirements that the FMCA would welcome IEEE 802.21 feedback on.

• End April: • IEEE 802.21 provided feedback on FMCA PRD Matrix• IEEE 802.21 provided a list of MIH questions for the FMCA• IEEE 802.21 indicated their interest in future FMCA PRDs

referencing appropriate IEEE 802.21 capabilities.

21-06-0659-00-0000

Proposed Future Engagement

• FMCA to provide feedback to IEEE 802.21 questions in time for IEEE 802.21 September Meeting.

• FMCA to review IEEE 802.21 PRD comments as part of FMCA PRD Release 3.0 development discussions.

• FMCA to invite IEEE 802.21 to present at FMCA Technical Review Session – 19th – 23rd June, Hong Kong.

21-06-0659-00-0000

Proposed Time Line

March 06FMCA highlightsWi-Fi SIP PRD R1.0Handover Requirementsto IEEE 802.21 for comment

End of AprilIEEE 802.21 providePRD R1.0 feedback and a list of handover questions requiring FMCA comment.

15th – 19th MayFMCA Initial Feedback at IEEE 802.21 Plenary

19th – 23rd JuneIEEE 802.21 Presentation atFMCA TechnicalReview Session

15th – 22nd JulyIEEE 802.21 Plenary

SeptemberFMCA Feedback at IEEE 802.21 Plenary

FMCA Members review and respondto IEEE 802.21 Feedback & Questions

21-06-0659-00-0000

Feedback on IEEE 802.21 questions

• FMCA have noted the IEEE 802.21 questions and review requests, relating to the following capabilities:

• Event Service• Information Elements• Definition of Voice Quality Parameters• UE Display of Available Wireless Networks• Roaming• Interference & Co-existence• Link Layer Triggers

• FMCA will provide feedback on these at the September IEEE 802.21 meeting.

• However we have some initial comments and points for clarification

21-06-0659-00-0000

Initial commentsInformation Elements (1)

• IEEE 802.21 question: • Are there any other Information Elements the FMCA would like to see in

the standard?

• FMCA initial comment:• FMCA will provide feedback on this in time for IEEE 802.21 September

meeting. However in the interim, we support in principle the additional IEs mentioned in the joint BT/Intel Handover Use Cases and Additional IEs (http://www.ieee802.org/21/doctree/2006-01_meeting_docs/21-06-0472-00-0000-Handover_Use_Cases_More_IEs.ppt) presentation made in January• E.g. Cost of basic services, Pre-Authentication & CAC, Emergency Service Support, Class

of User Supported, Latency, Jitter, Encryption Support, Power consumption, Coverage, Mobility speed supported, Hand-over times, etc

• What parameters will exist for cost IE? • Do different cost parameters need to be considered, e.g. messaging, data, voice, etc and not

just minute based parameters?

21-06-0659-00-0000

Initial commentsInformation Elements (2)

• IEEE 802.21 question:• Are the Information Elements in the right format?

• FMCA initial comment:• What naming convention will be used to ensure consistency?

• IEEE 802.21 question:• In the view of FMCA operators, how and where in the network

should the 802.21 Information Server be deployed in the following scenarios?

– a) Multiple Networks managed by single operator– b) Multiple Networks co-managed by multiple operators,

etc.

• FMCA initial comment:• Multiple Networks managed by single operator and multiple

networks co-managed by multiple operators should be treated the same, through the use of standard interfaces.

21-06-0659-00-0000

Initial comments Information Elements (3)

• FMCA Follow-up Question:• How does IEEE 802.21 envisage Information Elements fitting

into a 3GPP IMS compliant network architecture?• What is the current status of the 3GPP liaison?• Has IEEE 802.21 considered discussions with ETSI TISPAN

regarding the use of Information Elements and Network Intelligence for Handover decisions?

• How does IEEE 802.21 envisage operators building and maintaining databases of “neighbouring networks” ?

• There seems to be a requirement for the geographical location of each AP to be known. Will MIH be able to function without this information being available?

21-06-0659-00-0000

UE display of available wireless networks

• IEEE 802.21 question:• IEEE 802.21 would like FMCA feedback on what are the key

parameters which a UE should display when showing the list of available networks?

• In addition what are the key parameters the UE should display to help the end-user make optimum network selection decisions?

• FMCA initial comments:• The FMCA will provide feedback on this subject at the

September IEEE 802.21 meetings.• Perhaps this question needs to be expanded to consider how

different applications could also use these key parameters?

21-06-0659-00-0000

Roaming

• IEEE 802.21 questions:• How are the roaming agreements specified between different

operators?• Do the roaming agreements specified as part of IS in section

8.3 of current IEEE 802.21 draft capture this appropriately?• Information Elements (as specified in Section 6.3) can provide

details on Roaming Agreements, how does this align with FMCA Roaming requirements?

• FMCA initial comment:• FMCA is intending to cover roaming and inter-operability

aspects in subsequent PRDs and white papers. IEEE 802.21 will have the opportunity to review these requirements.

21-06-0659-00-0000

Interference & Co-existence

• IEEE 802.21 questions:• When connecting to multiple networks concurrently the UE may

have to deal with interference and co-existence type issues across different wireless networks.

• Since during handovers across heterogeneous technologies, multiple links have to be in operation anyway, should IEEE 802.21 try to define a preferred sequence of steps to conduct handover and thereby mitigate interference and co-existence type issues to a certain extent?

• FMCA initial comment:• What is meant by concurrent connections, e.g. how long before and

after a handover would concurrent connections exist for?• Have IEEE 802.21 considered security (multiple network

authentications, denial of service attacks) and battery life/power saving aspects?

21-06-0659-00-0000

Initial Feedback on IEEE 802.21 comments on PRD Matrix

• FMCA will review IEEE 802.21 comments on the PRD Matrix as part of PRD Release 3.0 development discussions.

• FMCA will look to reference IEEE 802.21 capabilities, where appropriate, in PRD Release 3.0.

• See embedded spreadsheet for initial FMCA feedback on IEEE 802.21

• IEEE 802.21 are encouraged to review FMCA Wi-Fi SIP and Wi-Fi GAN PRD Release 2.0 documents, which are now available off the FMCA website – www.thefmca.com

Microsoft Excel Worksheet

21-06-0659-00-0000

Converged Application Requirementsfor IEEE 802.21

• In a heterogenous network environment applications will need to know about the availability and characteristics of network connections• Certain application functions only make sense either from a

cost or usability perspective if they use an appropriate network . i.e. match application bandwidth/latency/cost requirements against those provided by current networks.

• Applications will want to dynamically alter their behaviour and UI based on what the current network can support e.g. a comms client may alter presence info to indicate video messaging is available when in Wi-Fi.

• Applications may only be launched or become active when certain network conditions are available.

21-06-0659-00-0000

Scenario 1: Network Aware OTA Device Management

Scenario: Device Management client performs various functions including low bandwidth aspects like settings updates through to large application downloads and even OTA firmware upgrades. Device Management needs to know about imminent loss of network or change in QoS in order to perform a graceful stop or warn the user. Certain DM functions may take a significant period of time and hence networks may disappear during function. DM client may want to postpone completion of DM functions until appropriate network reappears.

Moves into home network, application downloads restart. Connection likely to be available for a prolonged period, offers OTA firmware upgrade to user. User warned if network performance drops so they can take action.

User moves into Wi-Fi public hotspot, DM system realises good opportunity to initiate application downloads and starts download. Handover or Wi-Fi network is lost mid download, DM suspends app provisioning

User has Cellular coverage only, basic settings are managed, e.g. APN updates

CellularPublicWi-Fi

HomeWi-Fi

21-06-0659-00-0000

Scenario 2: Network Aware Data Synchronisation Client

Scenario: – Data sync client manages exchange of local device data with a network store. Device data includes essential data such as calendar, contacts that need regular synchronisation and less important data that relies on more intermittent connections e.g. picture gallery, email attachments. Client adapts its behaviour according to the available networks to deliver the best cost/performance balance. Default client behaviour may be modified or overridden according to user preferences, e.g. urgent data may be sync’d even if connection is expensive and slow.

Moves into home network, no backhaul congestion. Starts full synchronisation including bandwidth hungry picture and multimedia gallery, email attachments etc.

User moves into Wi-Fi public hotspot, up-link congested. Client initiates email attachment download but maintains suspension of outbox and picture gallery upload.

User has cellular coverage only, only important, time critical data sync’d e.g. Calendar, contact, inbox. Email attachments, outbox and picture gallery suspended

CellularPublicWi-Fi

HomeWi-Fi

21-06-0659-00-0000

Handover Implications for Device Management

• FMCA would welcome IEEE 802.21 feedback on the handover implications for automatically initiated device management and over the air updates.

• Implications associated with running simultaneous background applications and foreground applications as the UE handsover between different access networks.