Way forward discussion: SM Optics feedback

Slides:



Advertisements
Similar presentations
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Capability Discovery Amendment Date Submitted: April 20, 2006.
Advertisements

Document Title Author Affiliation. Release/Patent P&P Release: The contributor acknowledges and accepts that this contribution is subject to the IEEE.
[Document Title] [Contributor name and affiliation]
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE 1914 NGFI IEEE RoE TF Closing Report
[Insert Document Title Here]
IEEE 1914 NGFI IEEE RoE TF Opening Report
Unoccupied RBs Richard Maiden - Intel.
IEEE 1914 NGFI WG September 2018 Meeting Logistics v1.0
Network Diagrams for HMD based VR Service
[IEEE P3079 Session #6 WG Closing Plenary]
Jan 2016 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: KMP TG9 Opening Report Atlanta 2016 Date Submitted:
[IEEE P3079 Session #5 WG Closing Plenary]
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
Network instantiation
[IEEE P Session #2 WG Closing Plenary]
IEEE MEDIA INDEPENDENT HANDOVER DCN:
[Document title] [Author Name and affiliation].
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
[Framework of Evaluation and Assessment for the VR Sickness of VR Content] [Beom-Ryeol Lee/ETRI]
IEEE 1914 NGFI IEEE Status Update
November 2015 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: KMP TG9 Opening Report Dallas 2015 Date.
IEEE 802 omniRAN R9c Reference Point
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
[IEEE P3079 Session #7 WG Closing Plenary]
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
[place document title here]
IEEE MEDIA INDEPENDENT SERVICES DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
[IEEE P3079 Session #3 WG Closing Plenary]
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE 1914 NGFI IEEE RoE TF Closing Report
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
Jan 2014 Robert Moskowitz, Verizon
IEEE MEDIA INDEPENDENT HANDOVER DCN:
[IEEE P3079 Session #8 WG Closing Plenary]
[IEEE P3079 Session #8 WG Closing Plenary]
[user requirement for VR sickness editing]
IEEE 1914 NGFI IEEE RoE TF Opening Report
[Draft Document Naming Convention]
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcst
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx
Sept 2014 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: KMP TG9 Opening Report Athens 2014 Date Submitted:
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx
[Draft Document Naming Convention]
[place document title here]
802.1CF ToC Refinements Abstract
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
OmniRAN SDN Use Case ToC
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
[IEEE P3079 Session #9 WG Closing Plenary]
Robert Moskowitz, Verizon
Robert Moskowitz, Verizon
Report of TGm Comment Resolution Meeting – August 2005
[Scope of IEEE 3079 standard version 1
Submission Title: TG9ma Opening Report for July Meeting
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
Submission Title: IG SEC Opening Report for July 2014 Session
Sept 2014 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: KMP TG9 Opening Report Athens 2014 Date Submitted:
Submission Title: TG9ma Opening Report for September Meeting
Submission Title: TG9ma Opening Report for September Meeting
[IEEE P3079 Session #10 WG Closing Plenary]
Presentation transcript:

Way forward discussion: SM Optics feedback Vincenzo Sestito, SM Optics May 9th, 2017

Compliance with IEEE Standards Policies and Procedures Subclause 5.2.1 of the IEEE-SA Standards Board Bylaws states, "While participating in IEEE standards development activities, all participants...shall act in accordance with all applicable laws (nation-based and international), the IEEE Code of Ethics, and with IEEE Standards policies and procedures." The contributor acknowledges and accepts that this contribution is subject to The IEEE Standards copyright policy as stated in the IEEE-SA Standards Board Bylaws, section 7, http://standards.ieee.org/develop/policies/bylaws/sect6-7.html#7, and the IEEE-SA Standards Board Operations Manual, section 6.1, http://standards.ieee.org/develop/policies/opman/sect6.html The IEEE Standards patent policy as stated in the IEEE-SA Standards Board Bylaws, section 6, http://standards.ieee.org/guides/bylaws/sect6-7.html#6, and the IEEE-SA Standards Board Operations Manual, section 6.3, http://standards.ieee.org/develop/policies/opman/sect6.html

Next Generation Fronthaul Interface IEEE 1914 Next Generation Fronthaul Interface Jinri Huang, huangjinri@chinamobile.com Way forward discussion: SM Optics feedback Date: 2017-05-09 Author(s): Name Affiliation Phone [optional] Email [optional] Vincenzo Sestito SM Optics vincenzo.sestito@sm-optics.com

Q1: could we agree on the suggested 4 perspectives? Proposed framework organization from Dallas meeting SMO proposal for organization/contents change Perspective 1: NGFI network Perspective 1: NGFI Node Network scope Perspective 3: O&M / Resiliency Perspective 4: Security Perspective 5: Synchronization Perspective 2: NGFI network Perspective 2: NGFI Node Node scope Perspective 3: O&M SM Optics proposal is for a «top-down» approach, which identifies first the network suitable for NGFI transport (layers, technologies, functionalities, topologies), addressing as a consequence, the requested features at node level. Our proposal is for including in the framework, resiliency and synchronization, as well. Perspective 4: Security

Q2: Could we agree on the requirement classification for perspective 1 (NGFI node) Proposed Perspective 1 requirements from Dallas meeting SMO comments: All of these points should be developed at network level, first, resulting consequently in requirements for NGFI node, as well. O&M Resiliency Security Synchronization Requirements coming from Perspectives 1, 3, 4, 5 need to be considered for NGFI node, as well. Insert Title here Insert Date here

Q3: who can lead the requirement development for each perspective? Proposed framework organization SMO comments: We are available to contribute on the following perspectives: Perspective 1, 3, 5 (at network level) Perspective 2 (at node level) Insert Title here Insert Date here