200 likes | 311 Views
802.24 Vertical Applications TAG. January 2019 St. Louis, MO, USA. 802.24 Overview. Officers TAG Chair: Tim Godfrey Secretary & TAG Vice Chair: Ben Rolfe Task Groups 802.24.1 Smart Grid TG Tim Godfrey 802.24.2 IoT TG Chris DiMinico 26 Voting Members Agenda: 24-19-0001-00
E N D
802.24 Vertical Applications TAG January 2019 St. Louis, MO, USA Tim Godfrey, EPRI
802.24 Overview • Officers • TAG Chair: Tim Godfrey • Secretary & TAG Vice Chair: Ben Rolfe • Task Groups • 802.24.1 Smart Grid TG Tim Godfrey • 802.24.2 IoT TG Chris DiMinico • 26 Voting Members • Agenda: 24-19-0001-00 • Meetings for the Week • Wednesday PM2 24.1 • Thursday PM2 24.1 • Manual attendance tracking for 802.1 & 802.3 members
Agenda – 802.24-19-0001r0 Tim Godfrey, EPRI
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 patcom@ieee.org or visit http://standards.ieee.org/about/sasb/patcom/index.html 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. This slide set is available at https://development.standards.ieee.org/myproject/Public/mytools/mob/preparslides.ppt IEEE 802 Executive Committee
Participation in IEEE 802 Meetings Participation in any IEEE 802 meeting (Sponsor, Sponsor subgroup, Working Group, Working Group subgroup, etc.) is on an individual basis • Participants in the IEEE standards development individual process shall act based on their qualifications and experience. (https://standards.ieee.org/develop/policies/bylaws/sb_bylaws.pdf section 5.2.1) • IEEE 802 Working Group membership is by individual; “Working Group members shall participate in the consensus process in a manner consistent with their professional expert opinion as individuals, and not as organizational representatives”. (subclause 4.2.1 “Establishment”, of the IEEE 802 LMSC Working Group Policies and Procedures) • Participants have an obligation to act and vote as an individual and not under the direction of any other individual or group. A Participant’s obligation to act and vote as an individual applies in all cases, regardless of any external commitments, agreements, contracts, or orders. • Participants shall not direct the actions or votes of any other member of an IEEE 802 Working Group or retaliate against any other member for their actions or votes within IEEE 802 Working Group meetings, see https://standards.ieee.org/develop/policies/bylaws/sb_bylaws.pdf section 5.2.1.3 and the IEEE 802 LMSC Working Group Policies and Procedures, subclause 3.4.1 “Chair”, list item x. By participating in IEEE 802 meetings, you accept these requirements. If you do not agree to these policies then you shall not participate. (Latest revision of IEEE 802 LMSC Working Group Policies and Procedures: http://www.ieee802.org/devdocs.shtml ) Slide 5 IEEE 802 Executive Committee
Administration • Attendance take on IMAT • Reciprocal rights for most WGs • Web page • http://www.ieee802.org/24 • Mailing list • stds-802-24@listserv.ieee.org • 802-24-voters@listserv.ieee.org (voters list) • Document archive • http://mentor.ieee.org/802.24/documents • IEEE 802 announcement reflector, stds-802-all@listserv.ieee.org • Send email to listserv@listserv.ieee.org with no subject and with the • following 2 lines appearing first in the body of the message Subscribe stds-802-all end Tim Godfrey, EPRI
802.24 TAG • Approve November minutes • 24-18-0029r0 • TAG Action Items from November: Tim Godfrey, EPRI
Sub 1 GHz White Paper • Requested that the paper title was changed from "IEEE 802.24 Vertical Applications TAG“ to "Smart Grid Standards for Operation in Sub 1 GHz Bands“ Tim Godfrey, EPRI
Wednesday 802.24.1 Smart Grid TG Tim Godfrey, EPRI
ITU and Radio Regulatory Items • Update from 802.18 – Jay Holcomb • Discussion: Ireland consultation on 400 MHz • Further Consultation on the Release of the 410 – 415.5 / 420 – 425.5 MHz Sub-band • ComReg 18/92 • 1.4 GHz spectrum recently announced is being used for telemetry in oil/gas industry with 802.16s • Traditional license model – geographic ownership • Part 90 Tim Godfrey, EPRI
TSN White Paper • Comment Collection • The 802.24 TAG and 802.1 TSN TG solicit comments on 802.24-18-0011-00-sgtg "Utility Applications of Time Sensitive Networking White Paper" • Comment submittal spreadsheet provided • Will remain open until Meeting • Expect to finalize in March and start publishing process Tim Godfrey, EPRI
Collaboration with 802.21 • 'Network Enablers for Seamless HMD-based VR (Virtual Reality)’ • Subir Das Tim Godfrey, EPRI
Thursday 802.24TAG Tim Godfrey, EPRI
“Network Integration” action item • Action assigned from 802 EC leadership conference in July. • Discussion on role and positioning of IEEE 802 in standards, especially with respect to 3GPP and the publicity on “5G” • What is meant by Network Integration? • Does the IEEE 802 architecture provide a unique value to vertical market? • Is IEEE 802 more suited to deployment in the communication infrastructure of private enterprise, industry, and the individual user? (Compared to 3GPP, which is more oriented towards service providers?) • The IEEE 802 architecture enables networks that are like Ethernet: Well understood, mature, predictable. A “cleaner” integration of disparate technologies under the common architecture and addressing. • Can we develop a clearer definition and description of this distinction and the value for the user / implementer? • Can this be developed into a white paper? Tim Godfrey, EPRI
Network Integration: Notes from November • Max Riegel contribution 24-18-0026r0 • Thoughts on IEEE 802 network integration with respect to P802.1CF • Based on many discussions of the place of 802.11 in 5G. • 5G SC • Conclusions – AANI integrating 802.11 into 5G domain. Nothing corresponding in 3GPP • Industry connections – NENDICA • Flexible Factory IoT, Data Center Bridging • What’s missing – a picture of 802 as a peer to 5G • 5G promises they will do “everything” • But, they don’t do anything wired • 5G requires an extensive PLMN to support it. • It is designed to help the cellular operator grow their market • Verticals might not want an operator in the middle of their network • Value proposition: 802 networks are customer-owned • Example – Santa Clara Emergency services issues Tim Godfrey, EPRI
“Low latency” White Paper • Achieving low latency with IEEE 802 standards • Including wired and wireless communications • An alternative (or complement) to 5G URLLC • A set of vertical applications enabled by low latency • The challenges of reliable low latency in unlicensed spectrum. • Adapting TSN’s “FRER” feature • Adapting 802 wireless to licensed spectrum? • Operating over multiple bands or channels? • Special cases for high data rates for immersive video • Several people interested in contributing • Action: • Post call for contributions • Start reviewing contributions in January • Contribution from Oliver Holland (who cannot attend in January) Tim Godfrey, EPRI
Liaison with IEC SEG8 • Scope of SEG8: • Assess, provide an overview and prioritization of the evolution of technical development and standardization in the field of communication technologies and architectures • The report includes aspects relevant to both Smart Grid and IoT. • Document shared in 802.24 Private Area • IEC_SEG8_Deliverable2_draft_181118_ext_clean.pdf • Updated version uploaded to private area with annotations • Key chapters relevant to input from 802.24 • IoT Technologies • Single-pair Ethernet (SPE) • Deterministic Networking • Low-Power Wide-Area Networks (LPWAN) • V2V, V2I, V2P and V2N communication technologies • Call for other 802 WGs to participate in review and provide comments Tim Godfrey, EPRI
802.15.4g and 802.11ah Coexistence • 802.24 will develop a whitepaper/document for application-specific use cases. Identifying where each standard is most suitable, and how to make best use of other changes. • Identify use cases where 802.15.4g is not sufficient and both are needed • Could be choices of applications, channel guidelines, duty cycle, • Avoid perception that 802 standards are unable to coexist • Evaluate and describe potential application-level implications of delay/latency increases due to mutual interference • If NS-3 simulation models can be shared, others in IEEE 802 could progress that work. • MERL will share simulation models on Github. • New modules for 11ah 15.4g Tim Godfrey, EPRI
2019 TAG Activity Plan • “Low latency” White Paper • Start in January • A whitepaper/document for application-specific use cases of Sub 1GHz standards 802.15.4g and 802.11ah. Identifying where each standard is most suitable, and how to make best use of mechanisms proposed in 802.19 TG. • Can this also include applying 802.15.4s in sub-1GHz spectrum? • 802.24 white paper on IoT and P2413 • P2413 entering Sponsor Ballot • Update of first Smart Grid white paper to address latest amendments of 802.15.4 u, v, w, x, y • Nendica – Collaborate on Nendica Factory IoT? Tim Godfrey, EPRI
802.24 TAG closing • Action Items from this meeting • Any New Business? Tim Godfrey, EPRI