Omniran-13-0019-00-0000 1 OmniRAN Wi-Fi Hotspot Roaming Use Case Date: 2013-03-17 Authors: NameAffiliationPhone Max RiegelNSN+49 173 293

Slides:



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

(omniran TG) Short introduction into OmniRAN P802.1CF Date: Authors: NameAffiliationPhone Max RiegelNokia.
Omniran Network Detection and Selection Date: Authors: NameAffiliationPhone Max RiegelNSN
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 Smart Grid use case Document Number: Omniran Date Submitted: Source: Max Riegel Nokia.
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 OmniRAN Proximity Service use case Date: [ ] Authors: NameAffiliationPhone Hyunho ParkETRI
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
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:
OmniRAN Specification – Structuring the effort Document Number: Omniran Date Submitted: Source: Max Riegel
Omniran CF00 1 P802.1CF NRM Discussions Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Heterogeneous Networking – Setting the Scene
Discussion on NRM Control Reference Points Information and Parameters Date: Authors: NameAffiliationPhone Antonio de la Oliva University.
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
Omniran CF00 1 OmniRAN R3 Considerations Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 P802.1CF NRM Mapping to real networks Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Omniran CF CF Network Reference Model Introduction Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
WiFi Privacy network experiment at IEEE 802 Berlin Plenary and IETF92 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús
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
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 IEEE 802 OmniRAN EC SG Results and Outlook Date: Authors: NameAffiliationPhone Max RiegelNSN
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 Authentication and Trust Establishment Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
Omniran CF00 1 Key Concepts of Network Selection and Detection Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
Omniran OmniRAN SaMOG Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 P802.1CF NRM Backhaul Considerations Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
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.
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
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
802.1CF perspective on planned Industry Connections activity
P802.1CF NRM Mapping to real networks
P802.1CF architectural considerations for EM and NM
P802.1CF NRM Discussions Abstract
Network reference model for access network virtualization
P802.1CF D1.0 Figure Proposals Abstract
Brief Introduction to OmniRAN P802.1CF
P802.1CF architectural considerations for EM and NM
Terminology clean-up User/Subscriber
Terminology clean-up User/Subscriber
P802.1CF operational models
P802.1CF D1.0 Figure Proposals Abstract
P802.1CF NRM Refinements Abstract
[place document title here]
IEEE 802 Scope of OmniRAN Abstract
P802.1CF NRM Refinements 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
Presentation transcript:

omniran OmniRAN Wi-Fi Hotspot Roaming Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN 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 The presentation addresses the deployment of the OmniRAN architecture for the specification of open interfaces for roaming between Wi-Fi hotspot operators. The possibility to get access to communication services in other service providers’ networks has been one of the main reasons for the overwhelming success of cellular communication and is considered as necessary function also for public Wi-Fi access networks.

omniran Wi-Fi Hotspot Roaming Use Case OmniRAN use case contribution Max Riegel, NSN

omniran Roaming is a well know functionality in cellular networks allowing us to use our cellular phones worldwide without hassle. Roaming among Wi-Fi hotspots belonging to different operators is seen a prerequisite to further develop Wi-Fi access service to a cellular like experience Deployment Domain: Wi-Fi Roaming Wireless ISPs AC 3GPP2 MNO HLR 3GPP MNO Home ISP Roaming Broker Users

omniran Use case description: Joe’s Seamless Wi-Fi Service Joe is a road worrier always keen to make best use of the time he has to spend for traveling and sitting around waiting for the next flight or ride. Therefore he has a subscription with a local Wi-Fi service provider which has best coverage throughout his home town due to a phletora of Wi-Fi APs installed in nearly every public place in town including the airport and public transport vehicles, which Joe frequently uses. As Joe is regularly using Wi-Fi for making phone calls and participating in conference calls, he went for the premium subscription option providing him a priorized traffic path over Wi-Fi to his VoIP provider. Luckily his Wi-Fi provider is early adopter of the Hotspot 2.0 technology providing not only secured air links but also seamless service experience when moving around in his home town. Due to the many roaming contracts, which Joe’s local Wi-Fi operator has established some major Wi-Fi operator and hugh Wi-Fi roaming consortia, Joe’s seamless Wi-Fi service does not break when he is out of town. Usually his Wi-Fi devices just automatically connect to available Wi-Fi by making use of the enhanced network detection and selection features of Hotspot 2.0 and the credentials, he got from his Wi-Fi service provider, for automatic log-on. Even more, Joe enjoys the same high quality VoIP connectivity when he is roaming into the networks of the major Wi-Fi operators with direct contracts to his home Wi-Fi service provider.

omniran Wi-Fi Roaming Scenarios The following roaming scenarios are considered: 1.Home operator has roaming agreement with other operator. Traffic is routed via other operator’s core into the Internet 2.Home operator has roaming agreement with other operator. Traffic is routed back to the home operator’s core network. 3.Home operator has Wi-Fi access sharing agreement with other operator allowing to serve customers like within the own access infrastructure 4.Home operator has agreement with roaming consortia which enables to use credentials for access to all other operators’ Wi-Fi access, which belong to the roaming consortia.

omniran OmniRAN Architecture Mapping Core Internet R1 R3 Terminal R2 Access Home Operator Core Internet R3 R5 Access Other Operator w/ own core Access Access OperatorR3

omniran Home operator has roaming agreement with other operator. Traffic is routed via other operator’s core into the Internet Core Internet R1 R3 Terminal R2 Access Home Operator Core Internet R3 R5 Access Other Operator w/ own core R2 only control

omniran Home operator has roaming agreement with other operator. Traffic is routed back to the home operator’s core network. Core Internet R1 R3 Terminal R2 Access Home Operator Core Internet R3 R5 Access Other Operator w/ own core R2

omniran Home operator has Wi-Fi access sharing agreement with other operator allowing to serve customers like by the own access infrastructure Core Internet R1 R3 Terminal R2 Access Home Operator Access Access Operator R3

omniran Home operator has agreement with roaming consortia which enables to use credentials for access to all other operators’ networks belong to the roaming consortia. Core Internet R1 R3 Terminal R2 Access Home Operator Core Internet R3 R5 Access Other Operator w/ own core Core R5 Roaming Consortia

omniran Requirements for OmniRAN: All different flavors of Wi-Fi roaming can be handled with just 2 Reference Points of the OmniRAN architecture: –R3, when terminal is anchored in the home network Default router in the home network –R5, when terminal is anchored in the visited network Default router in the visited network When terminal is anchored in the visited network, it doesn’t matter for OmniRAN whether traffic is routed back into the home network or not –Routing is statically configured and independent of terminal attachment There may be configurations, which require further considerations, but can still be handled by OmniRAN A Roaming Consortium usually deploys R5 for inter- connection of all the involved operators.

omniran Conclusion OmniRAN provides the specifications to establish Wi-Fi Roaming with all its different flavors. R5 is mainly a AAA interface designed for inter-operator roaming. R3 can be used when forced traffic forwarding into the home is required.