Omniran-13-0016-02-0000 OmniRAN Proximity Service use case Date: [2013-03-16] Authors: NameAffiliationPhone Hyunho ParkETRI+82-42-860-4934

Slides:



Advertisements
Similar presentations
Omniran Wi-Fi Hotspot Roaming Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
Advertisements

Omniran GPP Trusted WLAN Access to EPC Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran IEEE 802 Enhanced Network Detection and Selection Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran OmniRAN Wi-Fi Hotspot Roaming Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
SDN-based OmniRAN Use Cases Date: [ ] Authors: NameAffiliationPhone Antonio de la OlivaUC3M+34 Juan Carlos ZúñigaInterDigital+1.
Privecsg Tracking of Link Layer Identifiers Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
WiFi Privacy network experiment at IETF91 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús Fabio
OmniRAN ecsg SDN-based Control Plane and Data Plane Separation in OmniRAN Network Reference Model Date: Authors: NameAffiliationPhone .
Omniran ZigBee SEP2 Smart Grid Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran OmniRAN Wi-Fi Hotspot Roaming Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran PtP Links across IEEE 802 Bridged Infrastructure Date: Authors: NameAffiliationPhone Max
IEEE MEDIA INDEPENDENT HANDOVER DCN: SAUC Title: MIH Service Use Cases for Dynamic Frequency Channel Allocation of IEEE WLANs.
Omniran ZigBee SEP2 Smart Grid Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
OmniRAN-15-00xx WLAN as a Component (WaaC) Date: xx Authors: NameAffiliationPhone Yonggang FangZTETX Bo SunZTE He HuangZTE Notice:
Proposal for an IEEE 802 EC OmniRAN Study Group Document Number: IEEE Shet Date Submitted: Source: Roger Marks (Consensii.
OmniRAN Specification – Structuring the effort Document Number: Omniran Date Submitted: Source: Max Riegel
Heterogeneous Networking – Setting the Scene
Omniran Orchestration of SON features for WiFi Offloading using Network Empowerment Mechanisms Date: Authors: NameAffiliationPhone .
Discussion on NRM Control Reference Points Information and Parameters Date: Authors: NameAffiliationPhone Antonio de la Oliva University.
Logical Interface Overview Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital Notice:
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: MISU Title: Proposal on new MIH service for Proximity Service Communications Date Submitted:
Privecsg ‹#› IEEE 802 Privacy concerns about 802c PAR Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZunigaInterDigital.
OmniRAN SDN-based OmniRAN Use Cases Summary Date: Authors: NameAffiliationPhone Antonio de la OlivaUC3M+34
An SDN-based approach for OmniRAN Reference Point mapping Date: [ ] Authors: NameAffiliationPhone Antonio de la
IEEE MEDIA INDEPENDENT HANDOVER DCN: SAUC Title: MIH Service Use Cases for Network-Assisted D2D Communication Date Submitted: September.
Omniran CF00 1 OmniRAN R3 Considerations Date: Authors: NameAffiliationPhone Max RiegelNSN
Text Proposals of HR-MS Forwarding in 16n Network IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16n-11/0074 Date Submitted:
Omniran CF CF Network Reference Model Introduction Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
Omniran Thoughts about the tenets in IEEE 802.1CF Date: Authors: NameAffiliationPhone Max RiegelNSN
Privecsg Tracking of Link Layer Identifiers Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
WiFi Privacy network experiment at IETF91 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús Fabio
Omniran CF00 1 Some Detailed Information for Network Reference Model Date: [ ] Authors: NameAffiliationPhone Su YiFujitsu R&D.
IEEE MEDIA INDEPENDENT HANDOVER Title: Use Cases, Security Study Group Date Submitted: Nov 13 th, 2007 Presented at: IEEE Security SG Authors.
Proposal of OmniRAN architecture for Data Offload Service through Wireless P2P Networks Document Number: omniran Date Submitted:
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 VLANs in relation to P802.1CF NRM Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Omniran CF00 1 CF ToC Refinements Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 Content and outline considerations for Annex: Applicability to non-IEEE 802 PHY layer technologies Date: Authors:
OmniRAN IEEE 802 OmniRAN Recommended Practice ToC Proposal Date: Authors: NameAffiliationPhone Yonggang
Omniran CF00 1 Key Concepts of Network Selection and Detection Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
OmniRAN CF00 1 IEEE 802 omniRAN Network Reference Model Amendment Date: Authors: NameAffiliationPhone Yonggang
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: Consideration for MGW discovery Date Submitted: July 18, 2012 Presented at IEEE.
Omniran OmniRAN SaMOG Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 Key Concepts of Network Selection and Detection Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
OmniRAN IEEE 802 OmniRAN Architecture Proposal Date: Authors: NameAffiliationPhone Yonggang Bo.
3GPP SA2 SaMOG Status Document Number: Omniran Date Submitted: Source: Antonio de la Oliva UC3M *
Control Procedure for Direct Communication IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16n-11/0054 Date Submitted:
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
Ad Hoc Relay Mode for Mobile Coverage Extension and Peer-to-Peer Communications IEEE Presentation Submission Document Number: IEEE S802.16m-07/260r2.
Omniran CF00 1 Key Concepts of Association and Disassociation Date: Authors: NameAffiliationPhone Max RiegelNokia
OmniRAN omniRAN Network Function Virtualization Date: Authors: NameAffiliationPhone Yonggang FangZTETX Zhendong.
Omniran Backhaul representation in OmniRAN SDN model Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 P802.1CF NRM Ambiguities Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Progressing OmniRAN Abstract
IEEE m SDD ToC for Inter RAT Handover
WLAN as a Component (WaaC)
An SDN-based approach for OmniRAN
IEEE 802 omniRAN R9c Reference Point
[place document title here]
IEEE 802 Scope of OmniRAN Abstract
An SDN-based approach for OmniRAN Reference Point mapping
[place document title here]
802.1CF ToC Refinements Abstract
OmniRAN SDN Use Case ToC
SDN-based OmniRAN Use Cases Summary
OmniRAN SDN Use Case ToC
IEEE 802 RAN Recommended Practice ToC Proposal
Presentation transcript:

omniran OmniRAN Proximity Service use case Date: [ ] Authors: NameAffiliationPhone Hyunho ParkETRI Hyeong-Ho LeeETRI Notice: This document does not represent the agreed view of the OmniRAN EC SG. It represents only the views of the participants listed in the ‘Authors:’ field above. It is offered as a basis for discussion. It is not binding on the contributor, who reserve the right to add, amend or withdraw material contained herein. Copyright policy: The contributor is familiar with the IEEE-SA Copyright Policy. Patent policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and. Abstract This document proposes Proximity Service as use cases of OmniRAN, and presents a new reference point (R XX : Reference point between MSs) of OmniRAN architecture for the Proximity Service. 1

OmniRAN Proximity Service use case Hyunho Park (ETRI), Hyeong-Ho Lee (ETRI) 2

3GPP Proximity Service (ProSe) Definition of Proximity Service Communication (from 3GPP TR [1]) ­ A communication between two UEs in proximity by means of a communication path established between the UEs. ­ The communication path could for example be established directly between the UEs or routed via local eNB(s). “Direct mode” data path “Locally routed” data path [1] 3GPP TR V ( ) 3

Standards for Proximity Service “Direct mode” data path “Locally routed” data path 4 Standard works for Proximity Service ­ IEEE PAC (Peer Aware Communication) ­ Wi-Fi Direct of Wi-Fi Alliance ­ ProSe (Proximity Service) of 3GPP  These standards can be used for contents sharing, data offload, local advertisements, social networking, etc. Inte rnet CNCN ANAN MS 1 MS 2 Inte rnet CNCN ANAN MS 1 MS 2 * MS: Mobile Station * AN: Access Network * CN: Core Network

OmniRAN for Proximity Service Communication Discovery and selection of the appropriate Proximity Service can be served by OmniRAN ­ Variety of communication standards (Wi-Fi Direct, IEEE , 3GPP ProSe, etc.) provide Proximity Service. ­ An appropriate Proximity Service depends on a mobile user’s environments.  Users using “direct mode” communications should use the same radio technology.  Selecting the radio technology that has the best QoS or consumes the lowest power is important.  OmniRAN as open mobile network interface platform can help discovery and selection of the appropriate Proximity Services among Wi-Fi Direct, IEEE , 3GPP ProSe, etc. 5

Deployment Domain: Proximity Service Internet ASP NSP NAP R5 R3 R2 R4 R1 Core Network AN  Application Service Provider (ASP): Provides contents. Contents: Video data, Pictures, etc.  Network Service Provider (NSP): Manages and Controls connections of networks. CSN (Core Service Network)  Network Access Provider (NAP): Controls access networks for mobile stations (MSs). ASN (Access Service Network)  Mobile Stations (MSs): Exchange data using “direct mode” data path or “locally routed” data path. R1 R2 Direct Mode Locally Routed MS Control Path Data Path 6

Use case 1: Data offload to Proximity Service Communications Mobile data traffic can be offloaded to Proximity Service communications. Example of the use case ­ Video clip “v” is very popular so that user of MS “A” want to receive it. If the video clip “v” is transferred through cellular or WiMAX network, the cellular or WiMAX networks can be busy. Although a network operator wants to offload the video clip “v” to other networks such as a WLAN, there is no WLAN access point. ­ The network operator informs the MS “A” of another MS “B” that received the video clip “v” through cellular or WiMAX network. ­ The video clip can be shared by Proximity Service communications such as WiFi-direct, IEEE , etc. Cellular or Wimax network NSP NAP MS “A” that received a video clip MS “B” that wants to receive a video clip 1 2 MS “A” received a video clip “v.” Connect to MS “A” by using Proximity Service “P” (WiFi-Direct, IEEE , 3GPP ProSe, etc.). MS “B” wants to receive a video clip “v.” Connect to MS “B” by using Proximity Service “P.” 4 MS “A” sends video clip through the Proximity Service “P.” Connection of MS “A” and “B” through Proximity Service. 3 7

Use case 2: Discovery and Selection of Proximity Service Communication MSs can discover and select Proximity Service communication. Example of the use case ­ MS “A” and MS “B” exchanged data each other through Proximity Service communication “P,” but throughput of the corresponding access link had been decreased because of signal interference. ­ MS “A” decides to change Proximity Service communication and searches for the most appropriate Proximity Service communication “Q.” ­ MSs change the Proximity Service “P” to the most appropriate Proximity Service communication “Q” and exchanges data through Proximity Service communication “Q.” MS “A” MS “B” Data exchanges through Proximity Service “P” (e.g. ProSe) MS “A” knows that Proximity Service “P” is getting worse because of signal interference. MS “A” discovers the most appropriate Proximity Service, “Q” (e.g. Wi-Fi Direct). Change Proximity Service “P” into Proximity Service “Q.” Connection through Proximity Service “Q.” Data exchanges through Proximity Service “Q” (e.g. Wi-Fi Direct) 8

OmniRAN Architecture Mapping for Proximity Service Communication Internet Core Network AN MS R3 R1 MS R2 Control Path Data Path R XX : Reference Point between MSs AN: Access Network 9

Requirements for OmniRAN R1: Reference point between AN and MS ­ Data path of R1: Existing access link between AN and MS ­ Control path of R1: Secured link setup between AN and MS R2: Reference point between Core Network (CN) and MS ­ Discovery and Selection of the corresponding MS: CN informs the requesting MS of the corresponding MS for Proximity Service communication. ­ Discovery and Selection of Proximity Service communication: CN informs the requesting and corresponding MSs of the most appropriate Proximity Service communication. R3: Reference point between CN and AN ­ Setup of AN: CN orders the AN to prepare Proximity Service. R XX : Reference point between MSs ­ Data path of R XX : Existing access link of Proximity Service communication (Wi- Fi Direct, IEEE , 3GPP ProSe, etc.) ­ Control path of R XX : Secured link setup between MSs  Functions of R XX for OmniRAN Discovery and Selection of the corresponding MS: For Proximity Service communication, the requesting MS discovers and selects the corresponding MS through R XX. Discovery and Selection of Proximity Service: The requesting MS discovers and selects the most appropriate Proximity Service communication (Wi-Fi Direct, IEEE , 3GPP ProSe, etc.). 10