1. omniran-15-0026-01-CF00 1 P802.1CF NRM Discussions Date: 2015-05-07 Authors: NameAffiliationPhoneEmail Max RiegelNokia Networks+49 173 293 8240maximilian.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: and.http://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/guides/opman/sect6.html#6.3 Abstract This revision: The document provides further refinements for the specification of the NRM based on the results of the confcall on April 16 th. Initial revision: This document provides additional input on conclusions on the definitions of the NRM interfaces R1, R3, R8.

2. omniran-15-0026-01-CF00 2 P802.1CF NRM discussions 2015-05-07 Max Riegel (Nokia Networks)

3. omniran-15-0026-01-CF00 3 NRM discussions at March 2015 F2F as captured by the minutes P802.1CF Network reference model https://mentor.ieee.org/omniran/dcn/15/omniran-15-0008-02-CF00-nrm-refinements.pptx –No final conclusion about the content of the R8c/R1c reference point in relation to the R1d reference point What functionality belongs to the “data path” reference point? –Agreement reached that R1 and R3 should become symmetric, as both may be either wired or wireless No conclusion about which label should be used for R3c; group did not like the idea to introduce 2-digit reference point indices, i.e. R10c https://mentor.ieee.org/omniran/dcn/15/omniran-15-0014-00-CF00-revision-proposal-of- omniran-14-0083.docxhttps://mentor.ieee.org/omniran/dcn/15/omniran-15-0014-00-CF00-revision-proposal-of- omniran-14-0083.docx –Edits presented to the group, but no final conclusion was reached, as no conclusion was reached either for treating the reference points between TEC – ANC – CNC, nor on replacement of term “Core Network” –Introductory section appreciated, as well as presentation of fewer variations. More details required on treating control interfaces as well as definition of functional content of data path interfaces. https://mentor.ieee.org/omniran/dcn/15/omniran-15-0013-00-CF00-r9c-reference-point- discussion.pptxhttps://mentor.ieee.org/omniran/dcn/15/omniran-15-0013-00-CF00-r9c-reference-point- discussion.pptx –Usage of “Core network” for the endpoint of the data path leads to ambiguities regards location of CIS Chair proposed to look for other term replacing “Core Network,” e.g. by “Network Service” –It remains unclear to which 802.19.1 interface the R9c reference point refers. Further clarifications necessary.

4. omniran-15-0026-01-CF00 4 Core Network/ Network Service Access Network Terminal Discussion status of the NRM Terminal Interface R1d Coordination and Information Service R2cR9c R8c/1c AN CtrlTE Ctrl Subscription Service Core Network Interface R3d R4c CN Ctrl R3c NABackhaul R6d R6cR7c R5c

5. omniran-15-0026-01-CF00 5 Some thoughts on differentiation between R1/R8c and R3d/R3c, respectively R1 should comprise the whole PHY+MAC+LLC interface as specified by IEEE 802 specification R8c covers information exchanges related to managed objects R3d should become R3, respectively. R3c should be identified by a different suffix.

6. omniran-15-0026-01-CF00 6 Network ServiceAccess Network Terminal For discussion: Re-labeling the NRM Terminal Interface R1 Coordination and Information Service R2R10 R8 AN CtrlTE Ctrl Subscription Service Network Service Interface R3 R4 NS Ctrl R9 NABackhaul R6 R5R7 R11

7. omniran-15-0026-01-CF00 7 NRM discussions at April 16 th 2015 confcall as captured by the minutes P802.1CF Network reference model –NRM amendment https://mentor.ieee.org/omniran/dcn/15/omniran-15-0024-00-CF00-nrm- amendment.pptxhttps://mentor.ieee.org/omniran/dcn/15/omniran-15-0024-00-CF00-nrm- amendment.pptx Group discussion: –The current NRM does not cover the use case when the AN control function is distributed throughout the AN. This use case could potentially require a new Reference point definition or an explanation in the text considering a collocation of ANC and NA functions in a single box. The situation of the Backhaul would still need to be considered for the latter case. The fat AP case can be accommodated with current NRM, in which all interfaces are internal. –Discussion on CNC CIS interface. Doubts on the need of such interface. Open still for discussion. –Further discussion on definition of reference points R1, R3 https://mentor.ieee.org/omniran/dcn/15/omniran-15-0026-00-CF00-nrm- discussions.pptxhttps://mentor.ieee.org/omniran/dcn/15/omniran-15-0026-00-CF00-nrm- discussions.pptx –The proposal is to change the naming convention on the Reference points and remove the letters. This change together with a text definition should help in clarifying confusions about the functionalities of each one of the Reference points. A new document will be worked out in preparation for the teleconference on May 8. –Author of the contribution to provide a clearer description in written regarding the different reference points.

8. omniran-15-0026-01-CF00 8 Some thoughts on resolving the remaining issues Definition of reference points –R1, R3, R6 represent ports according to IEEE 802 understanding Addition of a general introductory section may help to understand the meaning –R2, R4, R5, R7, R8, R9, R10, R11 address functionalities represented by the Layer Management Interfaces Terminology adjustment for ‘core network/network service’ –‘Access Router’ Or would ‘Access Gateway’ be better?

9. omniran-15-0026-01-CF00 9 Medium Data Link Physical Network Transport Application DL Phy DL Phy Data Link Physical Network Transport Application Network Medium Data Link Physical Data Link Physical Access Network Terminal Access Router Information Server DL Phy DL Phy DL Phy DL Phy Medium Backhaul End-to-end communication network topology Subscription Service R1 Network Reference Model Schematic Terminal Access Network Access Router Subscription Service R3 R4 R2 Scope of Network Reference Model in the protocol layer architecture Node of Attachment Terminal Interface Access Router Interface Scope of P802.1CF NRM overview

10. omniran-15-0026-01-CF00 10 Access RouterAccess Network Terminal For confirmation: Basic NRM Terminal Interface R1 R2 R8 AN CtrlTE Ctrl Subscription Service Access Router Interface R3 R4 AR Ctrl R9 R11

11. omniran-15-0026-01-CF00 11 Access RouterAccess Network Terminal For confirmation: Basic NRM w/ CIS Terminal Interface R1 Coordination and Information Service R2R10 R8 AN CtrlTE Ctrl Subscription Service Access Router Interface R3 R4 AR Ctrl R9 R11

12. omniran-15-0026-01-CF00 12 Access RouterAccess Network Terminal For confirmation: NRM Terminal Interface R1 Coordination and Information Service R2R10 R8 AN CtrlTE Ctrl Subscription Service Access Router Interface R3 R4 AR Ctrl R9 NABackhaul R6 R5R7 R11