IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-13-0119-00-MISU Title: Proposal on new MIH service for Proximity Service Communications Date Submitted:

Slides:



Advertisements
Similar presentations
IEEE MEDIA INDEPENDENT HANDOVER DCN: SAUC Title: MIH Service Use Cases for Dynamic Frequency Channel Allocation of IEEE WLANs.
Advertisements

IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: Discussion on “MGW vs. MIH-PoS” in IEEE c Date Submitted: Sept. 14 th, 2012.
21-06-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: The amendment for the MIH_Scan primitive Date Submitted: April,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposal of new SID in IEEE c Date Submitted: Presented at IEEE c TG Authors or Source(s):
xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Handover Procedure – Redraw of Annex Figure Date Submitted: January.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Utilizing terminal identifier to recognize the reserved resources.
IEEE MEDIA INDEPENDENT SERVICES DCN: SAUC Title: Needs of Link_Resource_Report and MIS_Resource_Report primitives/messages Date.
21-08-XXXX IEEE MEDIA INDEPENDENT HANDOVER DCN: XXX Title: Multi-Radio Power Management Analysis Date Submitted: March, 2008.
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho c-requirements-and-procedures Title: c Requirements and Procedures Date Submitted:
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Data Offload Service through Wireless P2P Networks based on IEEE Framework.
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx-00-MuGM Title: Demo Scenario Date Submitted: May, 16th, 2013 Presented at IEEE session in.
IEEE DCN: Title: Open SLMCP use case Date Submitted: January 10, 2015 IEEE session #66 in Atlanta, USA Authors or Source(s):
IEEE MEDIA INDEPENDENT HANDOVER DCN: SAUC Title: MIH Service Use Cases for Network-Assisted D2D Communication Date Submitted: September.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Analysis on Identifiers Date Submitted: January 9, 2006 Presented.
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Subscription ID Scope Date Submitted: June, 14 th, 2007 Presented.
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: sec Title: Message Flow Date Submitted: March 1, 2011 Authors or Source(s): Fernando Bernal-Hidalgo,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Handover Initiation Strategy Consistency Date Submitted: November,
Doc.: IEEE /0310r0 Submission Sept 2007 Srinivas Sreemanthula Slide 1 IEEE MEDIA INDEPENDENT HANDOVER DCN: MIH-Security-Options.ppt.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Notify high layer when events change Date Submitted: Jan, 06,
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Problem Scenario Date Submitted: September, 2007 Presented at.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Capability Discovery Amendment Date Submitted: April 20, 2006.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: FMCA MIH Work Item Date Submitted: March, 2009 Presented at IEEE.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Handover Initiation Strategy Consistency Date Submitted: November,
IEEE MEDIA INDEPENDENT HANDOVER DCN: SAUC Title: Media Independent Service Use Case for Open Screen Service Platform Date Submitted:
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Comments Date Submitted: Jan, 06, 2006 Presented at IEEE
IEEE MEDIA INDEPENDENT HANDOVER DCN: SAUC-Handover-Use-Case Title: Handover Use Case Date Submitted: January 22, 2014 To.
IEEE DCN: SAUC Title: Presentation of Open SLMCP use case Date Submitted: Sep 16, 2015 IEEE session #70 in Bangkok, Thailand.
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: IEEE c TG November 2012 Report and Agenda Date Submitted: November.
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: Consideration for MGW discovery Date Submitted: July 18, 2012 Presented at IEEE.
21-06-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: The amendment for the MIH_Scan primitive Date Submitted: April,
IEEE MEDIA INDEPENDENT HANDOVER DCN: XXXX Title: Handover Flow Diagrams for Annex A.6 Date Submitted: May 26, 2007.
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcst Title: Overview of Draft P802.21b/D0.01 Date Submitted: May 11, 2010 Presented at IEEE
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Registration Amendments Date Submitted: Nov.13, 2006 Submitted for discussion.
21-05-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Amendment for MIH_Handover_Initiate.request Date Submitted: April.
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: Title: New scenarios for Date Submitted: May 16, 2013 To be presented at… Authors or Source(s): Daniel.
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
Date Submitted: July 9, 2008 Radio States
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: Missing Gaps and Solutions for MGW Date Submitted: Presented at IEEE c TG Authors.
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Your Title Here
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
Presentation transcript:

IEEE MEDIA INDEPENDENT HANDOVER DCN: MISU Title: Proposal on new MIH service for Proximity Service Communications Date Submitted: July. 12, 2013 Presented at IEEE Session #57 –Geneva, Switzerland Authors or Source(s): Hyunho Park, Hyeong-Ho Lee, and Seung-Hwan Lee (ETRI) Abstract: This document proposes new MIH service for proximity service communications. 1

2 IEEE presentation release statements This document has been prepared to assist the IEEE 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 The contributor is familiar with IEEE patent policy, as stated in Section 6 of the IEEE-SA Standards Board bylaws and in Understanding Patent Issues During IEEE Standards Development Section 6 of the IEEE-SA Standards Board bylawshttp://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/board/pat/faq.pdf

Proximity Service Communications Proximity service (ProSe) communication in 3GPP TR ­ A communication between two UEs in proximity by means of a E-UTRAN communication path established between the UEs.  E.g., “direct mode” and “locally-routed” data path Proximity service communications ­ IEEE PAC (Peer Aware Communication), Wi-Fi Direct of Wi-Fi Alliance, ProSe of 3GPP, FlashLinQ of Qualcomm, etc. Needs for proximity service communications ‾ Public safety, data offload, social networking, etc. 3 Mobile node (MN) A MN B MN A MN B PoA (a) Direct mode data path (LTE D2D communications) (b) Locally-routed data path

Issues on Proximity Service Communications 4 1. Peer discovery ­ Conditions for the peer ­ A mobile node and a peer node should be in proximity. ­ A peer node can provide communication service that the MN wants to be served. ­E.g., If MN wants to receive some video file, the peer node must have the video file. ­ A mobile node and a peer node should communicate each other by using the same proximity service communication technologies. ­E.g., MN and peer node use Wi-Fi Direct. Cellular Network WLAN MN A MN B Example: If MN A and MN B in close proximity connect to different networks, how can they discover each other? MN A and MN B are in close proximity

Issues on Proximity Service Communications (Cont’d) 5 2. QoS degradation by interference ­ Interference between legacy network (e.g., cellular network) and proximity service communication.  E.g., Interference between LTE network and LTE D2D communication. ­ Interference between proximity service communications.  E.g., Interference between LTE D2D communications. MN A MN B LTE Network MN C eNB LTE cellular link LTE D2D link Interference from LTE cellular link Interference from LTE D2D link Example: Interference between LTE cellular link and LTE D2D link

New MIH services to solve the issues 6 1. Solution for peer discovery: Peer discovery by using MIH information server ­ The MIH information server provides information about peer of the MN. Cellular Network WLAN MN A MN B MN A and MN B are in close proximity You can connect to MN A by using LTE D2D. You can connect to MN B by using LTE D2D. 11 LTE D2D communications 2 MIH Information Server

New MIH services to solve the issues (Cont’d) 7 2. Solution for QoS degradation: Changing connection of proximity service communication technology ­ MIH information server helps the MN select the proximity service communication that can provide the best QoS. MN A LTE Network MN B eNB MIH Information Server 1 Bad LTE D2D link PAC will be better than LTE D2D for MN A and MN B. 2 3 PAC connection MN A LTE Network MN B eNB 1 Bad LTE D2D link 3 Wi-Fi Direct connection Let’s try to make Wi-Fi Direct connection! 2

Peer discovery by using MIH information server 8 Requirements of MIH information server for peer discovery ­ MIH information server should know proximity between mobile nodes.  Proximity between MNs can be derived by using MNs’ location information (e.g., GPS information).  Proximity between MNs can be derived by discovery signaling (e.g., beacon signaling of Wi-Fi Direct). ­ MIH information server should know communication services that MNs can provide.  MN’s peer can provide communication service (e.g., local information service, and file transmission, voice call) that the MN wants to be served. ­ MIH information server should know proximity service communication technologies that MNs can use.  MN and its peer should communicate by using the same proximity service communication technology.

Peer discovery by using MIH information server (Cont’d) 9 Information service messages can be used to notify an MN’s peer. New parameters and information elements for peer discovery ­ QUERIER_PROSE_TECHLIST: Available proximity service communication list (e.g., LTE D2D, Wi-Fi Direct, and PAC) of the MN that wants proximity service ­ QUERIER_PROSE_SERVICE: Communication services that MN wants to be served ­ IE_CORR_ID: Peer(i.e., corresponding node)’s identity (e.g., MAC address, IP address, and IMSI) ­ IE_PROSE_CONFIG: Information (e.g., frequency band) to help the MN configure its peer

Peer discovery by using MIH information server (Cont’d) 10 Mobile Node MIH information server 1. MIH_Get_Information (QUERIER_LOC, QUERIER_PROSE_SERVICE, QUERIE_PROSE_TECHLIST) request message :MN informs of its location (QUERIER_LOC), communication service (QUERIER_PROSE_SERVICE), and available proximity service communication (QUERIE_PROSE_TECHLIST) and requests proximity service communication. 2. MIH_Get_Information (IE_CORR_ID, IE_PROSE_CONFIG) response message :MIH information server responds with peer’s identity (IE_CORR_ID) and information (IE_PROSE_CONFIG) to configure peer.

Peer discovery by using MIH information server (Cont’d) MIH_Prose_Beacon message ­ The MN can check close proximity with its peer. ­ MIH_Prose_Beacon indication message is used for peer to send discovery signaling like beacon signaling of Wi-Fi Direct. ­ Parameters for MIH_Prose_Beacon  TXPower_Value: Transmission power value (Unit: dBW) for discovery signaling  TXPower_UpDn: Value (Unit: dB) to control transmission power. If TXPower_UpDn is +N, transmission power strength for the peer’s discovery signaling will increase by N dB. If TXPower_UpDn is -N, transmission power strength for the peer’s discovery signaling will decrease by N dB. 11

Peer discovery by using MIH information server (Cont’d) MIH_Prose_Beacon message (Cont’d) 12 MN’s Peer Network Infrastructure (e.g., LTE network and WLAN) 1. MIH_ProSe_Beacon indication (TXPower_Value (X)) MN requests the MN’s peer to transmit beacon with X dBW Mobile Node 2. MN’s peer sends beacon with X dBW strength. (Out of scope of IEEE standard) 3. MIH_ProSe_Beacon indication (TXPower_UnDn (+N)) MN requests the MN’s peer to increase power strength beacon of the peer by N dB. 4. MN’s peer sends beacon with X+N dBW strength. (Out of scope of IEEE standard) MN fails to receive beacon message from its peer because signal strength of beacon was too weak MN can receive beacon message from its peer.

Peer discovery by using MIH information server (Cont’d) MIH_Prose_TechList message ­ The MN and its peer should use the same proximity service communication technology. ­ MIH_Prose_TechList request message is used to know proximity service communication technologies that MN or its peer can use. ­ MIH_Prose_TechList response message is used to inform of proximity service communication technologies that MN or its peer can use. ­ Parameters for MIH_Prose_TechList  Prose_TechList: List of proximity service communication technologies that MN or its peer can use. 13

Peer discovery by using MIH information server (Cont’d) MIH_Prose_TechList message (Cont’d) 14 Mobile Node MIH Information Server or MIH PoS 1. MIH_Prose_TechList request message :MIH Information Server or MIH PoS requests list of MN’s available proximity service communication. 2. MIH_Prose_TechList (Prose_TechList) response message :MN responds with list of MN’s available proximity service communication technologies (e.g., LTE D2D, PAC, and Wi-Fi Direct).

Changing connection of proximity service communication technology MIH_Prose_Connection message –By using MIH_Prose_Connection message, MN and its peer can change connection of proximity service communication technology. –MIH_Prose_Connection request message is used to order MN or MN’s peer to connect each other by using some proximity service communication technology. –MIH_Prose_Connection response message is used to respond with results (e.g., Success or Fail) of connection between MN and its peer. –Parameters for MIH_Prose_Connection message  Prose_Tech: information of proximity service communication technologies that MN or its peer can use  Prose_Config: Information (e.g., frequency band) to help the MN configure its peer  Prose_Type: Type of proximity service communication (e.g., direct mode data path or locally routed data path)  Prose_MNID: Peer’s identity (e.g., MAC address, IP address, and IMSI)  Prose_PoAID: When locally routed data path is used, Prose_PoAID means the PoA that MN and its peer connect to. 15

Changing connection of proximity service communication technology MN’s Peer MIH Information Server or MIH PoS or Mobile Node 1. MIH_Prose_Connection (Prose_Tech, Prose_Config, Prose_Type, Prose_MNID, Prose_PoAID) request message :MIH Information Server or MIH PoS or MN requests MN’s peer to connect to MN by using some proximity service communication technology (e.g., PAC). 3. MIH_Prose_Connection response message :MN’s peer responds with connection result (success or fail). Mobile Node 0. Connection between MN and its peer by using proximity service communication (e.g., LTE D2D): Out of Scope 2. Changing connection between MN and its peer by using different proximity service communication (E.g., PAC): Out of Scope 16

This contribution showed solutions for issues on proximity service communication based on MIH framework. –Solution for peer discovery: Peer discovery by using MIH information server –Changing connection of proximity service communication technology Issues on proximity service communication can be solved by introducing new MIH messages, information element, and parameters based on the MIH framework. –New MIH messages: MIH_Prose_Beacon, MIH_Prose_TechList, MIH_Prose_Connection –New information elements: IE_CORR_ID, IE_PROSE_CONFIG Conclusions 17