IEEE MEDIA INDEPENDENT HANDOVER

Slides:



Advertisements
Similar presentations
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Problem Scenario Date Submitted: September, 2007 Presented at.
Advertisements

IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: IEEE c TG November 2012 Report and Agenda Date Submitted: November.
IEEE MEDIA INDEPENDENT HANDOVER DCN: 100 Title: Cross Domain Trigger and Handover Talking Points Date Submitted: July 13, 2004.
IEEE DCN: SAUC Title: TG Closing Note Date Submitted: November 14, 2013 Presented at IEEE session #59 in Dallas, Texas,
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE DCN: Title: TG Opening Note Date Submitted: September 15, 2014
IEEE MEDIA INDEPENDENT HANDOVER DCN: MuGM
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: MuGM
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE DCN: Title: TG Opening Note Date Submitted: November 09, 2015
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx
REVP Session#60 Agenda IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP-Session#60-Agenda Title: m Session #60 Agenda.
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER SERVICES
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP Title: m Session #72 Closing Notes Date Submitted: January 21, 2016 IEEE session.
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE DCN: SAUC Title: TG Closing Note Date Submitted: Nov 06, 2014
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcst
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE DCN: Title: TG Closing Note Date Submitted: September 17, 2015
IEEE DCN: Title: TG Opening Note Date Submitted: Mar 09, 2015
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP Title: m Session #71 Closing Notes Date Submitted: November 12, 2015 IEEE session.
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcst
REVP Session#63 Opening Note
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT SERVICES DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER SERVICES
IEEE DCN: Title: TG Opening Note Date Submitted: July14, 2014
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP Title: m Session #70 Opening Notes Date Submitted: September 14, 2015 IEEE
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcst
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Your Title Here
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: Missing Gaps Related with MGW Date Submitted: June 13, 2012 Presented at IEEE c.
IEEE MEDIA INDEPENDENT HANDOVER DCN: mugm
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
Presentation transcript:

IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-10-0164-00-srho Title: Discussion about PoA parameter in TLV Query Date Submitted: July 22, 2010 Presented at IEEE 802.21c Teleconference Authors or Source(s):  Hongseok Jeon (ETRI) Abstract: Discussion about PoA parameter in TLV Query so that whereby IS retrieves information on the SFF specific to given query.

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 stated in Section 6 of the IEEE-SA Standards Board bylaws <http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/faq.pdf> 

Background New Information Elements for SFF addressing were presented in 21-10/131r2 (IEEE 802.21c Proposal). IE_SFF_IP_ADDR IE_SFF_FQDN Two issues were raised: Issue 1: IE_SFF_IP_ADDR and IE_SFF_FQDN provides same information. Which is more valuable? Issue 2: SFF has no physical location information. How can Information Server provide information about the SFF suitable for given query? Meeting Conclusion: IE_SFF_FQDN was adopted and IE_SFF_IP_ADDR was removed. The optional parameters in a TLV query can be useful for IS to respond with suitable SFF FQDN matching the preferred networks and the roaming partner of the current serving network (NET_TYPE_INC, NETWK_INC). 21-09-0164-00-

More Discussion on Issue 2 We need a more detailed information than NET_TYPE_INC and NETWK_INC. Given Network Type and Network ID can provide information on multiple SFFs than a specific SFF suitable to a querier. Specific PoA can be a meaningful parameter in the TLV query whereby IS retrieves information on the SFF specific to given query. POA_INC: Specific PoA the queirier wants to include in the query response. BASE_ID AP_ID (not existing) CELL_ID