omniran17 0002 01 00 TG IEEE 802 1

omniran-17 -0002 -01 -00 TG IEEE 802. 1 Omni. RAN TG January 2017 F 2 F Meeting Atlanta, GA 2017 -01 -16 Max Riegel, Nokia Bell Labs (TG Chair) 1

omniran-17 -0002 -01 -00 TG January 2017 F 2 F Meeting • Venue: – Grand Hyatt Atlanta in Buckhead 3300 Peachtree Road NE Atlanta, GA 30305, USA • Meeting room: – Mon, Tue, Wed: – Thu: Highland Ballroom I, Lobby Chicago, Third • Sessions: – – Mon, Tue, Wed, Thu, Jan 16 th, 13: 30 -18: 00 Jan 17 th, 13: 30 -18: 00 Jan 18 th, 16: 00 -18: 00 special session on ICAID Jan 19 th, 08: 00 -12: 30 2

omniran-17 -0002 -01 -00 TG Jan 2017 Agenda Graphics Mon 1/16 08: 00 802. 11/802. 15 Tue 1/17 802. 11 WNG Wed 1/18 Thu 1/19 802. 11 ARC Fri 1/20 802. 11 Closing Opening plenaries 10: 00 10: 30 802. 11/802. 15 Mid-week Plenaries Omni. RAN closing 802. 11 ARC 12: 30 13: 30 Omni. RAN opening 15: 30 16: 00 Omni. RAN ICAID Special Session 18: 00 Newcomer’s session 3

omniran-17 -0002 -01 -00 TG Agenda proposal for January 2017 F 2 F • • • Review of minutes Reports Contributions to Industry Connections activity Comments’ resolution on P 802. 1 CF-D 0. 3 Revised and new P 802. 1 CF contributions – Contributions proposing new content • Plan for 802. 1 CF-D 0. 4 draft – Plan and timeline for next revision • Conference calls until Mar F 2 F • Status report to IEEE 802 WGs • AOB 4

omniran-17 -0002 -01 -00 TG Participants, Patents, and Duty to Inform All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. • • Participants [Note: Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6. 2]: • “Shall inform the IEEE (or cause the IEEE to be informed)” of the identity of each “holder of any potential Essential Patent Claims of which they are personally aware” if the claims are owned or controlled by the participant or the entity the participant is from, employed by, or otherwise represents • “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of potential Essential Patent Claims” (that is, third parties that are not affiliated with the participant, with the participant’s employer, or with anyone else that the participant is from or otherwise represents) The above does not apply if the patent claim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group Early identification of holders of potential Essential Patent Claims is strongly encouraged No duty to perform a patent search 5

omniran-17 -0002 -01 -00 TG Patent Related Links • All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development. • Patent Policy is stated in these sources: – IEEE-SA Standards Boards Bylaws http: //standards. ieee. org/develop/policies/bylaws/sect 6 -7. html#6 – IEEE-SA Standards Board Operations Manual http: //standards. ieee. org/develop/policies/opman/sect 6. html#6. 3 – Material about the patent policy is available at http: //standards. ieee. org/about/sasb/patcom/materials. html If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee. org or visit http: //standards. ieee. org/about/sasb/patcom/index. html This slide set is available at https: //development. standards. ieee. org/myproject/Public/mytools/mob/slideset. ppt 6

omniran-17 -0002 -01 -00 TG Call for Potentially Essential Patents • If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance: – Either speak up now or – Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or – Cause an LOA to be submitted 7

omniran-17 -0002 -01 -00 TG Other Guidelines for IEEE WG Meetings • All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws. • • Don’t discuss the interpretation, validity, or essentiality of patents/patent claims. Don’t discuss specific license rates, terms, or conditions. • Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings. • • Technical considerations remain primary focus Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets. • Don’t discuss the status or substance of ongoing or threatened litigation. • Don’t be silent if inappropriate topics are discussed … do formally object. -------------------------------- See IEEE-SA Standards Board Operations Manual, clause 5. 3. 10 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details. 8

omniran-17 -0002 -01 -00 TG Resources – URLs • Link to IEEE Disclosure of Affiliation – http: //standards. ieee. org/faqs/affiliation. FAQ. html • Links to IEEE Antitrust Guidelines – http: //standards. ieee. org/resources/antitrust-guidelines. pdf • Link to IEEE Code of Ethics – http: //www. ieee. org/web/membership/ethics/code_ethics. html • Link to IEEE Patent Policy – http: //standards. ieee. org/board/pat-slideset. ppt 9

omniran-17 -0002 -01 -00 TG Business #1 • Call Meeting to Order – Chair called meeting to order at 13: 40 • Minutes taker: – Walter volunteered to take notes. • Roll Call Name Affiliation Max Riegel Nokia Wang Hao Fujitsu Walter Pienciak IEEE Yonggang Fang ZTETX Roger Marks Eth. Air. Net Assoc. Su Yi Fujitsu Hyeong-Ho Lee ETRI Name Affiliation 10

omniran-17 -0002 -01 -00 TG Call for Potentially Essential Patents • If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance: – Either speak up now or – Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or – Cause an LOA to be submitted • Nobody spoke up in the meeting. 11

omniran-17 -0002 -01 -00 TG Agenda for January 2017 F 2 F • Review of minutes – – • • Reports Contributions to Industry Connections activity – • – https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0006 -00 -CF 00 -mapping-accounting-and-monitoring-to-ieee-802 technologies. docx https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0007 -00 -CF 00 -mapping-fdm-to-ieee-802 -technologies. docx Plan for 802. 1 CF-D 0. 4 draft – • • • https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0081 -02 -CF 00 -802 -1 cf-d 0 -3 -collected-comments. xls https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0073 -00 -CF 00 -virtual-access-network-instantiation. docx https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0001 -00 -CF 00 -answer-to-chapter-8 -1 -comments. docx https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0004 -00 -CF 00 -chapter-7 -1 -restructuring. docx https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0005 -00 -CF 00 -chapter-7 -1 -text-revision. docx Section 7. 5. 7 Revision Proposal (to be uploaded) Revised and new P 802. 1 CF contributions (Contributions proposing new content) – • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0008 -00 -CF 00 -p 802 -1 cf-perspective-on-industry-connectionsactivity. pptx Comments’ resolution on P 802. 1 CF-D 0. 3 – – – • https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0096 -00 -00 TG-dec-13 th-2016 -confcall-minutes. docx https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0090 -00 -00 TG-nov-2016 -f 2 f-meeting-minutes. docx Plan and timeline for next revision Conference calls until Mar F 2 F Status report to IEEE 802 WGs AOB 12

omniran-17 -0002 -01 -00 TG Schedules • Mon – – – • Review of minutes • https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0096 -00 -00 TG-dec-13 th-2016 -confcall-minutes. docx • https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0090 -00 -00 TG-nov-2016 -f 2 f-meeting-minutes. docx Reports Comments’ resolution on P 802. 1 CF-D 0. 3 • https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0081 -02 -CF 00 -802 -1 cf-d 0 -3 -collected-comments. xls • https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0073 -00 -CF 00 -virtual-access-network-instantiation. docx Tue – – Comments’ resolution on P 802. 1 CF-D 0. 3 • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0004 -00 -CF 00 -chapter-7 -1 -restructuring. docx • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0005 -00 -CF 00 -chapter-7 -1 -text-revision. docx Contributions to Industry Connections activity • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0008 -00 -CF 00 -p 802 -1 cf-perspective-on-industry-connectionsactivity. pptx • Thu – – – Comments’ resolution on P 802. 1 CF-D 0. 3 • https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0081 -02 -CF 00 -802 -1 cf-d 0 -3 -collected-comments. xls • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0001 -00 -CF 00 -answer-to-chapter-8 -1 -comments. docx • Section 7. 5. 7 Revision Proposal (to be uploaded) Revised and new P 802. 1 CF contributions (Contributions proposing new content) • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0006 -00 -CF 00 -mapping-accounting-and-monitoring-to-ieee-802 technologies. docx • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0007 -00 -CF 00 -mapping-fdm-to-ieee-802 -technologies. docx Plan for 802. 1 CF-D 0. 4 draft • Plan and timeline for next revision Conference calls until Mar F 2 F Status report to IEEE 802 WGs AOB 13

omniran-17 -0002 -01 -00 TG Business #1 • Schedule over the week – Chair discussed availabilities of the contributors and preferences to discuss the various topics. The 5 GAA related contribution will be discussed on Tue PM 2. – Schedule over the week agreed as shown on the previous slide. • Review of minutes – https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0096 -00 -00 TG-dec-13 th-2016 confcall-minutes. docx – https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0090 -00 -00 TG-nov-2016 -f 2 fmeeting-minutes. docx • Chair quickly went over minutes and asked for comments. No comments were raised to either of the minutes. • Reports – Chair shortly reported about ongoing activities with IEEE SA to document 5 G related standardization efforts. – http: //5 g. ieee. org/ was presented as common portal of IEEE SA to present its 5 G related activities. P 802. 1 CF showed up under the ongoing standardization projects. – Paul Nicolich currently collects further details on ongoing 5 G related standardization activities. 14

omniran-17 -0002 -01 -00 TG Business #2 • Comments’ resolution on P 802. 1 CF-D 0. 3 – https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0081 -02 -CF 00 -802 -1 cf-d 0 -3 collected-comments. xls • Chair brought up latest status of comments database to check for remaining open comments. • Comments related to section 7. 1 might be closed as part of presentation and discussion of restructured and revised text. • Remaining open comments might be closed at the end of the meeting. – https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0073 -00 -CF 00 -virtual-accessnetwork-instantiation. docx • Proposed text contributed by Yonggang was brought up for presentation and discussion. Text was reviewed and jointly edited to reach consensus on the scope and description of the section 8. 3 on AN instantiation. • Basic consensus on terminology was imported from https: //mentor. ieee. org/omniran/dcn/16/omniran-16 -0071 -01 -CF 00 -key-concepts-of-aninstantiation. pptx, which was discussed and agreed in the previous F 2 F meeting. Recommendation was made to introduce the basic terminology on virtual AN vs. virtualized AN, as well as the concept of an instance created from a template. Hao Wang noted, that there was agreement in the November meeting not to address subnetwork instances, as mentioned in the NGMN whitepaper on network slicing. The slides also confirmed, that network functions denote entities of the NRM which carry forward Ethernet frames, i. e. TE, NA, BH, and AR. • Consensus was reached that instantiation is initiated out of the OSS of the AN operator, and instantiation is performed by an Orchestrator, which might reside outside of the domain of the AN operator. When issuing the instantiation of a new AN, the AN operator establishes an NMS, to which the newly created AN instance in associated with, and which initiates the network initialization as defined in chapter 7. 1 • Running out of time it was concluded to stop the discussion on the contribution and to come back at a later time, when the schedule allows for it. • The chair offered to create a text proposal for the addition of the definitions to chapter 6. 7, as well as to create alternative version of the figure on slide 14 showing more functional details within the Infrastructure Provider. 15

omniran-17 -0002 -01 -00 TG Business #3 • Comments’ resolution on P 802. 1 CF-D 0. 3 – https: //mentor. ieee. org/omniran/dcn/17/omnira n-17 -0004 -00 -CF 00 -chapter-7 -1 restructuring. docx – https: //mentor. ieee. org/omniran/dcn/17/omnira n-17 -0005 -00 -CF 00 -chapter-7 -1 -textrevision. docx 16

omniran-17 -0002 -01 -00 TG Business#4 • Contributions to Industry Connections activity – https: //mentor. ieee. org/omniran/dcn/17/omnira n-17 -0008 -00 -CF 00 -p 802 -1 cf-perspective-onindustry-connections-activity. pptx 17

omniran-17 -0002 -01 -00 TG Business#5 • Comments’ resolution on P 802. 1 CF-D 0. 3 – https: //mentor. ieee. org/omniran/dcn/16/omnira n-16 -0081 -02 -CF 00 -802 -1 cf-d 0 -3 -collectedcomments. xls – https: //mentor. ieee. org/omniran/dcn/17/omnira n-17 -0001 -00 -CF 00 -answer-to-chapter-8 -1 comments. docx – Section 7. 5. 7 Revision Proposal (to be uploaded) 18

omniran-17 -0002 -01 -00 TG Business#6 • Revised and new P 802. 1 CF contributions (Contributions proposing new content) – https: //mentor. ieee. org/omniran/dcn/17/omnira n-17 -0006 -00 -CF 00 -mapping-accounting-andmonitoring-to-ieee-802 -technologies. docx – https: //mentor. ieee. org/omniran/dcn/17/omnira n-17 -0007 -00 -CF 00 -mapping-fdm-to-ieee-802 -technologies. docx 19

omniran-17 -0002 -01 -00 TG Business#7 • Plan for 802. 1 CF-D 0. 4 draft – Plan and timeline for next revision • Conference calls until Mar F 2 F • Status report to IEEE 802 WGs • AOB 20