802.1CF perspective on planned Industry Connections activity

Slides:



Advertisements
Similar presentations
(omniran TG) Short introduction into OmniRAN P802.1CF Date: Authors: NameAffiliationPhone Max RiegelNokia.
Advertisements

OmniRAN Smart Grid use case Document Number: Omniran Date Submitted: Source: Max Riegel Nokia.
Omniran OmniRAN Wi-Fi Hotspot Roaming Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
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 CF00 1 OmniRAN R3 Considerations Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran Thoughts about the tenets in IEEE 802.1CF 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 CF00 1 P802.1CF NRM Backhaul Considerations Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Omniran Backhaul representation in OmniRAN SDN model Date: Authors: NameAffiliationPhone Max RiegelNSN
Progressing OmniRAN Abstract
Layer-2 Network Virtualization
Max Riegel, Nokia Bell Labs (TG Chair)
Network instantiation
Layer-2 Network Virtualization
Relation between information modeling and network operation
P802.1CF NRM Mapping to real networks
P802.1CF User Service Information Model
omniRAN Virtual Access Network Instantiation
P802.1CF architectural considerations for EM and NM
omniRAN Network Function Virtualization
P802.1CF NRM Refinements Abstract
P802.1CF NRM Discussions Abstract
Network reference model for access network virtualization
Max Riegel, Nokia (TG Chair)
Chapter 7.1 Restructuring Proposal
WLAN as a Component (WaaC)
Max Riegel, Nokia (TG Chair)
Layer-2 Network Virtualization
802.1CF-D1.0 WG ballot comment remedies
Max Riegel, Nokia Bell Labs (TG Chair)
802.1CF-D1.0 WG ballot comment remedies
Date: < yyyy-mm-dd >
An SDN-based approach for OmniRAN
Transmission Modes for Multi-Radio Access in Hierarchical Networks
P802.1CF D1.0 Figure Proposals Abstract
Max Riegel, Nokia Bell Labs (TG Chair)
Network instantiation
Brief Introduction to OmniRAN P802.1CF
SDN Functional Decomposition
P802.1CF architectural considerations for EM and NM
Terminology clean-up User/Subscriber
Max Riegel, Nokia (OmniRAN TG Chair)
Max Riegel, Nokia Bell Labs (TG Chair)
Terminology clean-up User/Subscriber
P802.1CF Information Model Structure
P802.1CF operational models
omniRAN Network Function Virtualization
Key concepts of authorization, QoS, and policy control
IEEE 802 omniRAN R9c Reference Point
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
Privacy Recommendation PAR Proposal
Max Riegel, Nokia Bell Labs (TG Chair)
IMT-2020/5G SC Proposal Date: Authors: July 2016
An SDN-based approach for OmniRAN Reference Point mapping
January 2013 Summary Report for OmniRAN EC SG
[place document title here]
802.1CF ToC Refinements Abstract
Max Riegel, Nokia (TG Chair)
IMT-2020/5G SC Proposal Date: Authors: July 2016
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:

802.1CF perspective on planned Industry Connections activity Date: 2017-01-15 Authors: Name Affiliation Phone Email Max Riegel Nokia +491732938240 maximilian.riegel@nokia.com Notice: This document does not represent the agreed view of the IEEE 802.1 OmniRAN TG. 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 <http://standards.ieee.org/IPR/copyrightpolicy.html>. Patent policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: <http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and <http://standards.ieee.org/guides/opman/sect6.html#6.3>. Abstract OmniRAN TG currently prepares the authorization of an Industry Connections activity to determine potentials to initiate standardization of advanced communication services for markets outside the established mobile network operations. The presentation raises questions, how OmniRAN may prepare for introduction of 802.1CF to a bigger industry.

802.1CF perspective on planned Industry Connections activity Max Riegel (Nokia BellLabs)

Action A: IEEE “5G” specification Candidate Approach 3 Action A: IEEE “5G” specification Candidate Approach • specify an 802 access network could be based on P802.1CF “network reference model defines a generic foundation for the description of IEEE 802 access networks, which may include multiple network interfaces, multiple network access technologies, and multiple network subscriptions, aimed at unifying the support of different interface technologies, enabling shared network control and use of software-defined networking (SDN) principles” provides an external view into general 802 access network could support many 802 MACs and PHYs could plug into incumbent mobile operator networks for example, expand the notion of LWA so that the cellular network supports 802 rather than 802.11 gives 802 a strong supporting role in cellular 5G networks could support integration into other operator networks e.g. cable TV or fixed telecom gives 802 a central role in non-cellular 5G networks feasible for 802 access network to support both need not promote it as an “IEEE 5G” network

Refined scope of 5G SC Action A “IEEE next generation communication infrastructure specifications that support enhanced broadband, massive machine type communication and ultra-reliable and low latency communications not belonging to mobile networks” Well sounding brand name missing. For further study Could we somehow reuse ‘OmniRAN’?

Source: IEEE 802-EC-16-0083-00-5GSG “P802.1CF Interface option to 5G” Source: IEEE 802-EC-16-0083-00-5GSG Does this picture work well to address all the other deployments aside of mobile networks?

6 IMT-2020 (per ITU-R M.2083)

What are the deployments aside of mobile networks? Other operators of public communication networks than mobile network operators MSO FNO Hotspot operators ‘Verticals’ represented in IEEE standards like Smart Grid http://standards.ieee.org/develop/msp/smartgrid.pdf Cloud Computing http://standards.ieee.org/develop/msp/cloudcomputing.pdf Internet of Things (including Green Community Networks) http://standards.ieee.org/develop/msp/iot.pdf Intelligent Transportation Systems http://standards.ieee.org/develop/msp/its.pdf eHealth http://standards.ieee.org/develop/msp/ehealth.pdf Smart Cities http://standards.ieee.org/develop/msp/smartcities.pdf

Getting in touch with the verticals? Can IEEE SA headquarter help to establish communications to the verticals? Who are the staff liaisons for the verticals? Can we do a kind of structured assessment to determine where P802.1CF matters most? Are P802.1CF-like networks already deployed? Could P802.1CF networks make a difference? How would we initiate discussions? Presentations at standardization meetings? Workshops on IEEE conferences?

Our goals? Make new deployments of IEEE 802 happen by better serving deployment needs Unifying technical approaches among various deployment domains by better communications Development of further amendments to fulfill particular requirements. Faster adoption of emerging trends to IEEE 802 standards by better understanding of market evolution. More direct involvement of “customers” in the evolution of IEEE 802 technologies

How could we prepare for the Industry Connections activity? OmniRAN P802.1CF topic How could we prepare for the Industry Connections activity? What kind of ‘marketing material’ should OmniRAN TG prepare? Any particular enhancement to P802.1CF specification text required to make specification more ‘acceptable’? How could we introduce P802.1CF to a bigger industry? Do we have sufficient answers to ‘security, reliability, privacy’ in the text?

Going forward Should we actively push forward P802.1CF into the Industry Connections activity? Are we willing to spend the extra effort? Who are the volunteers?