Transcript 21-06-0489-01-0000-MIH_Neighbor_Information

21-06-0489-01-0000-MIH_Neighbor_Information
IEEE 802.21 MEDIA INDEPENDENT HANDOVER
DCN:21-06-0489-01-0000-MIH_Neighbor_Information
Title: Neighbor Information Considerations in Heterogeneous
Handovers
Date Submitted: January 2006
Presented at IEEE 802.21 session #12 at Hawaii
Authors or Source(s):
Xiaoyu Liu, Samsung AIT
Abstract: This is a presentation on how to deal with Neighbor
Information issues in Handovers across Heterogeneous
Networks
21-06-0489-01-0000-MIH_Neighbor_Information
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-0489-01-0000-MIH_Neighbor_Information
Neighbor Information
Considerations in MIH
Presenter
Slide 3
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
Agenda
•
•
•
•
•
Introduction
Basic Issues of Neighbor Information
Key Components in Std.
A Case Study of MIH Neighbor Issues
Conclusion
Slide 4
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
References
• 802.21 MIH
– Draft P802-21-D00-04
– 21-05-0401-03-0000-IE_TLV_Representation.doc
• Media Specific Neighbors
– 802.11k Neighbor Reports
– 802.16e
– Cellular Networks
Slide 5
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
Basic Issues for MIH Neighbor
Information
• [1-1] From the perspective of a terminal, how to get
the heterogeneous neighbor information?
– A mechanism for POS to provide the neighbor information
– Assume that neighbor information is already available in the
network
– The ‘Pull’ Model for MIIS
• [1-2] From the perspective of a network, how to get
the heterogeneous neighbor information?
– A mechanism for POS to collect or update the neighbor
information
– To meet the assumption of [1-1]
– The ‘Push’ Model for MIIS
Slide 6
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
Key Components in Std. regarding MIH
Neighbor Information
• [2-1] Neighbor Report
– Information Element contained in the Neighbor Report
• [2-2] Primitives of the related SAPs
• [2-3] MIH Protocol
– Messages and related formats exchanged between
terminal and the network
Slide 7
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
MIIS and Neighbor Information
• Relationship between MIIS and Neighbor Information
– Neighbor information could be obtained from MIIS services.
– MIH Neighbor Report may consist of the IEs defined in MIIS.
• Similar to MIIS IEs, the MIH Neighbor Information may be
classified into:
– Neighbor Information regarding General Network Information
– Neighbor Information regarding Access Network Specific Information
– Neighbor information regarding POA Specific Information
• Note:
– Section 6.3.1 (D00-04 ) mentioned ‘neighbor reports’, ‘neighbor maps’,
‘neighboring …’, ‘neighbor information’, etc., but does not have a
‘explicit’ concept for MIH neighbor information/reports.
– A particular bullets to introduce a concept about the MIH Neighbor
Information (or MIH Neighbor Graph) might be helpful.
Slide 8
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
A Case Study of Issue [1-1]
• Assumptions
– A client in WLAN access network is interested in getting neighbor
information of heterogeneous networks, WMAN and UMTS in this
example.
– POS in the WLAN access network maintains the neighbor information
and may derive the neighbor understands that which BS in WMAN and
UMTSA are the neighbors of the WLAN AP to which the client
currently connected.
– The following steps are based on the D00-04 and contribution (21-050401-03-0000).
• Step [1-1-a]
– L3MP in a terminal issues a request to MIH in the terminal for the MIH
Neighbor Information
– Solution: A primitive in MIH_SAP setting appropriate QueryFilter and
QueryParameters; MIH Get Information.request may do this work.
– Note: No definition for the primitive MIH_Get_Information in Table 8
(entry 23) in D00-04
Slide 9
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
A Case Study of Issue [1-1]
• Step [1-1-b]
– MIH in a terminal issues a request to MAC or IP in a terminal for MIH
Neighbor Information
– Solution: MIH_Information.request setting appropriate QueryFilter and
QueryParameters
– Note:
• 7.4.15.1MIH_Information.request is not consistent with the flow chart in 6.3.5.
• The description in 7.4.15.1.3 ‘this primitive is generated by a "NETWORK"
L3MP…’ is not correct.
• If the primitive is sent to MAC, it may not be appropriate to classify it to ‘MIH_SAP’
which is between MIH and L3MP.
• Step [1-1-c]
– MAC or IP generates Information Request Frame and transport from the
terminal to network
– Solution: Information Request in 4.1/4.2/4.3 (21-05-0401-03) may do this work.
– Note:
• Information Request should be part of 8.4.5 MIH Message Data. The related part in
the MIH protocol should also be specified.
Slide 10
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
A Case Study of Issue [1-1]
• Step [1-1-d]
– Peer MIH in the network receive ‘indication’ from MAC or IP for MIH Neighbor
Information request
– Note:
• MIH_Information.indication is not shown in D00-04
• Step [1-1-e]
– Peer MIH in the network issues a response to MAC or IP in the network to respond to the
request for MIH Neighbor Information
– Solution: MIH_Information.response with MIH_REPORT which may contain the
Neighbor Information
– Note:
• MIH_REPORT is not specified in D00-04.
• Step [1-1-f]
– MAC or IP in the network generates Information Response Frame and transport from the
network back to the terminal
– Solution: Information Response in 4.1/4.2/4.3 (21-05-0401-03) may do this work.
– Note:
• The Information Response should be part of 8.4.5 MIH Message Data. The related part in the MIH
protocol should also be specified.
• Should make MIH_REPORT and Information Response consistent.
Slide 11
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
A Case Study of Issue [1-1]
• Step [1-1-g]
– MIH in the terminal receive ‘confirmation’ from MAC or IP for MIH Neighbor
Information
– Note: MIH_Information.confirmation is not shown in D00-04
• Step [1-1-h]
– MIH in the terminal issues a response to L3MP in the terminal to for the retrieved MIH
Neighbor Information
– Solution: MIH Get Information.response may do this work.
– Note:
• No definition for the primitive MIH_Get_Information in Table 8 (entry 23) in D00-04
• Summary of the Proposals for Issue [1-1]
– Primitives
• MIH-SAP: MIH Get Information.request/response
• MIH-SAP: MIH_Information.request/response/indication/confirmation
– MIH Protocol
• Information Request/Response Frames
– Neighbor Report
– MIH_REPORT
– IEs: MIIS IEs
Slide 12
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
Neighbor Information Issue [1-2]
• The ‘PUSH’ Model
– Discussed in the early stage of this WG, but concluded to be
‘out-of-scope’, but the motivation is still…
• You may manually configure the MIIS Server and MIH
Neighbor Information, but
– Heavy administrative load for a big heterogeneous network
and …
– It is really difficult for 802.21 MIH to support a highly
dynamic topology, for example Multi-Hop Relay or Client
Mesh networks (although at current stage 802.21 MIH
assumes the infra-structured networks).
– Above is the motivation for a mechanism for POS to collect
or update the MIIS as well as the Neighbor Information, i.e.,
– Reconsider the PUSH Model.
Slide 13
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
Neighbor Information Issue [1-2]
• Possible Approaches
– Exchange MIIS/Neighborhood renew information within network
(Reference Point R5/R4) whenever the topology changes, and/or
– Exchange MIIS/Neighborhood renew information between terminal and
network (Reference Point R1/R2/R3).
• Out of Scope – How to ‘collect’ neighbor information
– The procedures and the implementation related things
• In Scope – What to be collected
– Primitives
• MIH_SAP: Primitives
– MIH Protocol
• Frames for POS to get information
Slide 14
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
Other Considerations
• Static vs. Dynamic Neighbor information
– Since the IEs defined in MIIS are static, i.e., if MIH
Neighbor Report consists only the MIIS IEs, it would
be static.
– Media Specific neighbor information may include some
dynamic info.
• Primitives
– MIH Neighbor Information use the same set of
primitives as MIIS or a different set of primitives?
– For example: MIH_Neighbor_Report.request
Slide 15
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
Conclusion
•
Neighbor information report is an important use case of MIIS during handover.
– By combination of QueryFilter and QueryParameters, Neighbor Information may be
derived from the current mechanisms for MIIS, but mainly for static information
– Dedicated set of primitives for Neighbor Information is preferred – providing
extensibility for dynamic neighbor information.
•
There are still some inconsistencies and missing things in the current draft.
•
Suggest Work Items for Issue [1-1]
– Add a sub-section in MIIS to clarify the relationship between Neighbor and related IEs
– Clean the inconsistencies and add missing parts presented.
– Provide an example in the Annex B for the use cases of different neighbor report
•
Request the group to reconsider the Issue [1-2]
– Dynamic update for MIIS server and Neighbor Information
Slide 16
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
Feedback?
Slide 17
Xiaoyu Liu
January 2006
21-06-0489-01-0000-MIH_Neighbor_Information
Backup Slide: Neighbor Report in 802.11k
• Information Element
– Neighbor Report Element
• Element ID
• Length
• Neighbor List
– {BSSID, BSSID Information, Channel Number, Regulatory Class, PHY Options, TSF
Offset}
• Action Frames
– Neighbor Report Request frame
– Neighbor Report Response frame
• Primitives
–
–
–
–
MLME-NEIGHBORREP.request
MLME-NEIGHBORREP.confirm
MLME-NEIGHBORREP.indication
MLME-NEIGHBORREP.response
• Usage of Neighbor Report
– An overview of the basic mechanisms
Slide 18
Xiaoyu Liu