1. 2016-12-06 Max Riegel, Nokia (TG Chair)
IEEE OmniRAN TG Conference call on 5G SC Action A (Industry Connections activity)
Max Riegel, Nokia
(TG Chair)

2. Guidelines for IEEE-SA 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.
If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at or visit
See IEEE-SA Standards Board Operations Manual, clause and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details.
This slide set is available at
March 2015
IEEE-SA Standards Board Patent Committee

3. Agenda
Introduction
IEEE SA Industry Connections
Industry Connections Activity Initiation Document (ICAID)
Plan for Jan ’17 Atlanta meeting
AoB

4. Motion at 802.1 Nov ’16 closing plenary
Authorize OmniRAN TG to create an ICAID proposal addressing the 5G SC Action A and authorize the chair to pre-circulate the ICAID proposal to the EC for consideration.
Moved: Max Riegel
Second: John Messenger
Vote: 22, 0, 1

5. 5G SC Action A

6. Action A: IEEE “5G” specification Candidate Approach6
Mentor DCN: EC GSG
11/8/2018
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
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

7. 7
Mentor DCN: EC GSG
11/8/2018
IMT-2020 (per ITU-R M.2083)

8. Could be called ‘IEEE ngci’
Scope of 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”
Could be called ‘IEEE ngci’
For further study

9. Who could be the ‘customers’?
Other operators of public communication networks than mobile network operators
MSO
FNO
Hotspot operators
‘Verticals’ represented in IEEE standards like
Smart Grid
Cloud Computing
Internet of Things (including Green Community Networks)
Intelligent Transportation Systems
eHealth
Smart Cities

10. What would we like to achieve?
Strengthen the IEEE 802 ecosystem by unifying technical approaches among various deployment domains.
More direct involvement of customers in the evolution of IEEE 802 technologies
Faster adoption of emerging trends into IEEE 802 standards by better understanding of market evolution
Already complete listing?
At least, no other proposal raised in call.

11. Who are the leading customers?
What do we miss?
What are the requirements and commonalities among the various deployment domains of IEEE 802 technologies?
Who are the leading customers?
No other issue mentioned in the call.

12. IEEE SA Industry Connections

13. IEEE SA Industry Connections activity
Aimed for technical group discussions (far) ahead of starting PAR discussions.
ICAID (Industry Connections Activity Initiation Document) request form for approval
Presentation by John:
Use of Industry Connections in IEEE 802
Further resources:

14. DRAFt ICAID

15. Revision with comments from John:
Draft ICAID
Initial draft text based on input from John and edited by Max available by
Revision with comments from John:

16. Way forward

17. Next steps
Chair invites for comments on draft ICAID for the upcoming meeting at the IEEE 802 interim. Text of ICAID will be revised at the meeting based on submitted comments.
Next F2F meeting: Atlanta, Jan 2017
Session on Wed, January 18th, PM2
Next conference call:
Tues, January 31st, 2017, 09:30-11:00AM ET
BTW: Submission deadline of ICAID for consideration in the March EC closing:
February 10th

18. Next steps & AoB
Could we start discussing the ICAID on the mailing list?
Response of the chair: Discussion on the mailing list is challenging, as there is no dedicated mailing list for the preparation of the ICAID. We use various mailing lists, like the list, the AANI list, and the IEEE 802 5G list. Therefore the continuation of the discussion is aimed for the Atlanta meeting.
AoB
None
Chair adjourned call at 11:00 AM ET.