July 2011 Smart Grid ad hoc - IEEE Standards Association

July 2011 Smart Grid ad hoc - IEEE Standards Association

doc.: IEEE 802.11-11/0975r1 July 2011 Smart Grid ad hoc July 2011 Name Company Address Phone email Bruce Kraemer Marvell 5488 Marvell Lane, Santa Clara, CA, 95054 +1-321-751-3988 [email protected] Date: 21 July 2011 Discussions during July Plenary meeting in San Francisco Tuesday Abstract: Thursday Abstract: 1 SGIP 2 - NIST PAP2 3- ITU Liaison

1- FERC 2 - NIST PAP2 3- ITU Liaisons [WG18 docs 49,51,57 Submission Slide 1 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 FERC Order FERC Issues Order on Smart Grid Interoperability Standards The FERC issued its Order on Smart Grid Interoperability Standards,and it has concluded that there is "insufficient consensus" on the initial five families of standards that were sent by NIST for FERC adoption in accordance with the Energy Independence and Security Act of 2007. Furthermore, the FERC encouraged stakeholders to actively participate in the NIST interoperability framework process to develop standards for interoperability and to refer to that process for guidance on smart grid standards. Finally, FERC terminated its proceeding in docket RM11-2-000. In reaching its conclusion not to institute a rulemaking proceeding to adopt the standards, the Commission agreed with comments that registered concerns about cyber security deficiencies and potential unintended consequences from premature adoption of individual standards. The Commission did express its support for the NIST process and did encourage active participation by stakeholders, citing planned improvements to the NIST process including "an enhanced SGIP role in reviewing existing as well as new smart grid interoperability standards, the establishment of a preliminary testing process, the establishment of a process to identify cyber security design principles, and efforts to better address reliability and implementation concerns within the SGIP process."

Submission x Slide 2 Bruce Kraem doc.: IEEE 802.11-11/0975r1 FERC decision of July 19 FERC Terminates Consideration of Smart Grid Interoperability Standards July 20, 2011 On July 19, 2011, following a lengthy consideration of the smart grid interoperability standards proposed by the National Institute of Standards and Technology (NIST), FERC terminated its consideration of the five families of proposed interoperability standards, concluding that there was a lack of consensus regarding the standards. NIST had initiated the development of smart grid interoperability standards following the Energy Independency and Security Act of 2007 (EISA). Under the EISA, if FERC is satisfied that there is sufficient consensus surrounding the standards developed and proposed by NIST, FERC must institute a rulemaking to adopt those standards and protocols necessary to insure smart-grid functionality and interoperability. Last fall, NIST filed the results of its work on smart grid interoperability standards with FERC. FERC then held two technical conferences and asked for comments from industry stakeholders on the NIST proposal. Following this process, FERC concluded that there is insufficient consensus to adopt the proposed standards at this time, pointing to nearly unanimous comments from the industry regarding cyber security concerns and the potential unintended consequences from adopting such standards too soon. For these reasons, FERC stated that it would not institute a rulemaking proceeding regarding the proposed smart grid interoperability standards. Nevertheless, FERC reiterated its support for the NIST process, and urged stakeholders to actively participate in NISTs work on smart grid interoperability standards, particularly in those areas related to cyber security. FERC terminated its proceeding in docket RM11-2-000. http://ferc.morganlewis.com/2011/07/20/ferc-terminates-consideration-of-smart-grid-interoperability-standards/

Submission April 2011 doc.: IEEE 802.11-11/0975r1 FERC Order http://www.nerc.com/files/Order_Smart_Grid_Interoperability_standards.pdf SUMMARY: Section 1305(d) of the Energy Independence and Security Act of 2007 directs the Commission to institute a rulemaking proceeding to adopt such standards and protocols as may be necessary to insure smart-grid functionality and interoperability in interstate transmission of electric power, and regional and wholesale electricity markets once it is satisfied that the work of the National Institute of Standards and Technology has led to sufficient consensus on smart grid interoperability standards. The Commission finds that there is insufficient consensus for the five families of standards under consideration. For this reason, the Commission will not institute a rulemaking proceeding at this time with respect to these standards and terminates this docket. In this order, the Commission encourages stakeholders to actively participate in the NIST interoperability framework process to work on the development of interoperability standards and to refer to that process for guidance on smart grid standards. Submission April 2011 doc.: IEEE 802.11-11/0975r1 PAP02- Phase 2-SDO Proposal r0 July 21 topic Intro

Thanks to Ron Cunningham for his diligent preparation of requirements for completion of Phase 2. We propose that it is time for the SDOs to take a more active role in constructing the analytic Proposal/Request We request authorization from PAP2 members to form an SDO subcommittee committed to completing delivery of an operational analysis framework , and related descriptive text, in time for presentation to the Dec 05, 2011 SGIP board meeting. Goals Deliverables will include: Definition of propagation model, ability to calculate quantity of wireless equipment required to cover a given demographic/topographic area and description of statistical confidence in reported numbers Utility/GRID Input Requirements Information regarding actor quantities by type, relative locations, topography, data traffic loads Synchronization SDO subcommittee will report progress to during currently scheduled biweekly PAP2 calls Logistics SDO subcommittee will convene a series of teleconferences scheduled to optimize SDO participation but open to all PAP2. SDO subcommittee will self organize , assign/delegate work. develop a milestone based project schedule. Webinar facilities will be needed. Membership SDO subcommittee is a volunteer group initially underwritten by WiMAX, IEEE 802, ATIS & CTIA. Additional wireless SDO participants will be recruited Submission doc.: IEEE 802.11-11/0975r1 Feedback on ITU Liaisons Any feedback during July meeting? Continue to collect comments on conference calls Submission doc.: IEEE 802.11-11/0975r1 July 2011

ITU SMART GRID LIAISONS WG18 Documents https:// mentor.ieee.org/802.18/dcn/11/18-11-0058-00-0000-summaryof-itu-r-documents.pptx https:// mentor.ieee.org/802.18/dcn/11/18-11-0049-01-0000-working-d ocument-towards-a-preliminary-draft-new-report-itu-r-sm-s mart-grid.docx Submission Slide 7 Bruce Kraem doc.: IEEE 802.11-11/0975r1 July 2011 ITU SMART GRID LIAISONS WG18 Document 51 DRAFT NEW QUESTION ITU-R [PWRGRD]/1 Impact on radiocommunication systems from wireless and wired data transmission technologies used for the support of power grid management systems. Submission Slide 8 Bruce Kraem doc.: IEEE 802.11-11/0975r1

July 2011 ITU SMART GRID LIAISONS WG18 Document 51 decides that the following Questions should be studied What are the technical and operating features and the characteristics of wireless technologies and devices in support of power grid management systems? What are the data rates, bandwidths, frequency bands and spectrum requirements needed support of power grid management systems? What are the interference considerations to radiocommunications associated with the implementation of wireless and wired technologies and devices used in support of power grid management systems? How will spectrum availability be affected by interference associated with widespread deployment of such technologies and devices? further decides that the results of the above studies should be included in Recommendations(s) and/or Report(s); that the above studies should be completed by 2016. Submission Slide 9 Bruce Kraem doc.: IEEE 802.11-11/0975r1 July 2011 ITU SMART GRID LIAISONS WG18 Document 57 Scope

This Recommendation provides the objectives, system characteristics, functional requirements, service applications and fundamental network functionalities for mobile wireless access systems providing communications to a large number of ubiquitous sensors and/or actuators scattered over wide areas in the land mobile service. The key objective of WASN systems is to support machine-to-machine service applications irrespective of machine locations. Objectives 2.1 Support of M2M service applications The mobile wireless access system should support a variety of machine-tomachine (M2M) service applications such as automation and efficiency enhancement of business works, environment observation, remote control of plant facilities, social security and the reduction of environmental impact, irrespective of their locations. Submission Slide 10 Bruce Kraem doc.: IEEE 802.11-11/0975r1 July 2011 SAMPLE FROM 049R1 Smart grid communication network technologies Various types of communication networks may be used in smart grid implementation. Such communication networks, however, need to provide sufficient capacity for basic and advanced smart grid applications that exist today as well as those that will be available in the near future. Assessing communications needs of various smart grid applications requires an understanding of 1) the control loop timeline of the application, 2) the amount of data that needs to be transferred at any particular time, 3) the number and location of devices with which communications must be maintained, and 4) the overall communication capacity of the proposed communication system. An applications timeline and tolerance for latency in transferring and analysing data or control signals is critical to determining appropriate communications capability. For example, the gathering of metering data for daily meter collection can tolerate a latency period of many hours (and even a period

of several days in the case of monthly billing). But real-time, control-oriented applications such as voltage control, integration of distributed generation resources, and distribution switching require latency periods of no more than two seconds. The control loop timeline refers to the overall length of time to make a decision and initiate action relevant to a particular control application. For instance, a control decision that needs to be made with real-time information every 30 seconds cannot utilize a communications link that takes 60 seconds to transfer the related data. For example, distributed protection systems use multiple isolating switches and relays that disconnect power from a section of the electric distribution system in the event of a failure or short circuit. Such disconnection helps reduce the size and impact of any resulting outage, prevent widespread damage to the system, and minimize public safety hazards. In order to make control decisions, these systems rely on widely dispersed devices that access information about real-time conditions at other devices connected to the distribution grid. Distributed protection systems respond to events of only several milliseconds in duration and must communicate information just as quickly in order to perform their functions effectively. Submission Slide 11 Bruce Kraem doc.: IEEE 802.11-11/0975r1 July 2011 SGIP Submission Slide 12 Bruce Kraem SGIP MONTHLY REPORT Prepared by: SGIP Plenary Leadership and SGIP PMO Report covers activities for May, 2011

http://collaborate.nist.gov/twiki-sggrid/pub/SmartGrid/PMO/2011-05_SGIP_Monthly_Report_FINAL_V1.0.pptx Standards Being Addressed by PAPs Priority Action Plan doc.: IEEE 802.11-11/0975r1 Standard(s) or Guideline(s) PAP 0 - Meter Upgradeability Standard NEMA Meter Upgradability Standard: SG-AMI 1-2009 PAP 1 - Role of IP in the Smart Grid Informational IETF RFC PAP 2 - Wireless Communications for the Smart Grid IEEE 802.x, 3GPP, 3GPP2, ATIS, TIA PAP 3 - Common Price Communication Model OASIS EMIX, ZigBee SEP 2, NAESB PAP 4 - Common Scheduling Mechanism OASIS WS-Calendar PAP 5 - Standard Meter Data Profiles AEIC V2.0 Meter Guidelines (addressing use of ANSI C12) PAP 6 - Common Semantic Model for Meter Data Tables

ANSI C12.19-2008, MultiSpeak V4, IEC 61968-9 PAP 7 - Electric Storage Interconnection Guidelines IEEE 1547.4, IEEE 1547.7, IEEE 1547.8, IEC 61850-7-420, ZigBee SEP 2 PAP 8 - CIM for Distribution Grid Management IEC 61850-7-420, IEC 61968-3-9, IEC 61968-13,14, MultiSpeak V4, IEEE 1547 PAP 9 - Standard DR and DER Signals NAESB WEQ015, OASIS EMIX, OpenADR, ZigBee SEP 2 PAP 11 - Common Object Models for Electric Transportation NAESB Energy Usage Information, OpenADE/NAESB ESPI, ZigBee SEP 2, IEC 619689, ASHRAE SPC 201P ZigBee SEP 2, SAE J1772, SAE J2836/1-3 , SAE J2847/1-3, ISO/IEC 15118-1,3, SAE J2931, IEEE P2030-2, IEC 62196 PAP 12 - IEC 61850 Objects/DNP3 Mapping IEEE Std 1815 (DNP3); IEEE P1815.1 (plus anticipated dual logo with the IEC) PAP 13 - Time Synchronization, IEC 61850 Objects/IEEE C37.118 Harmonization IEEE PC37.238; IEEE C37.118.1; IEEE C38.118.2; IEC 61850-90-5 (plus anticipated dual logo with the IEEE) PAP 14 - Transmission and Distribution Power Systems Model Mapping IEC 61968-3, MultiSpeak V4 PAP 15 - Harmonize Power Line Carrier Standards for Appliance

Communications in the Home DNP3 (IEEE 1815), HomePlug AV, HomePlug C&C, IEEE P1901 and P1901.2, ISO/IEC 12139-1, G.9960 (G.hn/PHY), G.9961 (G.hn/DLL), G.9972 (G.cx), G.hnem, ISO/IEC 14908-3, ISO/IEC 14543, EN 50065-1 PAP 16 - Wind Plant Communications IEC 61400-25 PAP 17 - Facility Smart Grid Information Standard New Facility Smart Grid Information Standard ASHRAE SPC 201P PAP 18 - SEP 1.x to SEP 2 Transition and Coexistence SEP 1.0, 1.x, 2.0, Transition and Coexistence Best Practices PAP 10 - Standard Energy Usage Information Submission May 2011 Activities - PMO Monthly Report doc.: IEEE 802.11-11/0975r1 Key SGIP Program Activities Upcoming Governing Board Votes

CoS Process Vote ended May 12, Approved PAP 05 July, 2011 AEIC Metering Guideline PAP 11 July, 2011 Communication between Plug-in Vehicles and the Utility Grid PAP 04 Sept, 2011 OASIS WS-Calendar PAP 12 Sept, 2011 IEEE 1815 (DNP) PAP 15 Sept, 2011 Broadband PLC standards (IEEE and ITU-T) Upcoming Plenary Membership Votes June 14 to July 7 PAP 00 PAP 01 PAP 02 PAP 10 PAP 11 PAP 11 NEMA Meter Upgradability Standard Role of IP in the Smart Grid Wireless Guidelines NISTIR Standard Energy Usage Information SAE J1772 - Electric Vehicle and Plug in Hybrid Electric Vehicle Conductive Charge Coupler SAE J2836 - Use Cases for Communication Between Plug-in Vehicles and the Utility Grid 2011 SGIP Meetings F2F Meetings July 12-14: Face-to-Face in Montreal December 5-8: Face-to-Face in Phoenix Virtual Meetings:

Sep 16; Nov 10 Additional Major Activities and Milestones NIST Framework V2 collaboration/development/input with SGIP organizations Identifying key testing and certification programs to address in 2011 Creating conceptual architecture based on prior work; conceptual model, national goals workshops, and requirements workshops Submission May 2011 Activitie - PMO Monthly Report doc.: IEEE 802.11-11/0975r1 July 2011 Upcoming SGIP Governing Board Meetings (attendance not required) Date Time Location Registration July 11 & 12 Informational: 6:30pm to 9:00pm Eastern; Business: 8am to 11:30am Eastern the Summer Face-to-Face, Montreal, QC. Sept. 8 1pm to 4pm Eastern Virtual Nov. 10 1pm to 4pm Eastern Virtual Dec. 5 8am to Noon Local Part of the Winter Face-to-Face, Phoenix, AZ Submission Slide 16 Part of

Bruce Kraem doc.: IEEE 802.11-11/0975r1 Key SGIP Program Activities Upcoming Governing Board Votes CoS Process Vote ended May 12, Approved PAP 04 July, 2011 OASIS WS-Calendar PAP 05 July, 2011 AEIC Metering Guideline PAP 11 July, 2011 Communication between Plug-in Vehicles and the Utility Grid PAP 12 July, 2011 IEEE 1815 (DNP) PAP 15 July, 2011 Broadband PLC standards (IEEE and ITU-T) Upcoming Plenary Membership Votes PAP 00 PAP 01 PAP 02 PAP 10 PAP 11 PAP 11

NEMA Meter Upgradability Standard Role of IP in the Smart Grid Wireless Guidelines NISTIR Standard Energy Usage Information SAE J1772 - Electric Vehicle and Plug in Hybrid Electric Vehicle Conductive Charge Coupler SAE J2836 - Use Cases for Communication Between Plug-in Vehicles and the Utility Grid 2011 SGIP Meetings F2F Meetings July 12-14: Face-to-Face in Montreal December 5-8: Face-to-Face in Phoenix Virtual Meetings: May 26; Sep 16; Nov 10 Additional Major Activities and Milestones NIST Framework V2 collaboration/development/input with SGIP organizations Identifying key testing and certification programs to address in 2011 Creating conceptual architecture based on prior work; conceptual model, national goals workshops, and requirements workshops http://collaborate.nist.gov/twiki-sggrid/pub/SmartGrid/PMO/2011-04_SGIP_Monthly_Report_FINAL_V1.0.pptx Submission April 2011 doc.: IEEE 802.11-11/0975r1 May 2011 Timeline Status Milestone: Milestone: Milestone: Milestone: Milestone:

SSO Identified GB PAP Requirements Handoff Standards Handback GB/SGIP Vote Initiation GB Decision PAPWG Startup Develop Requirements SSO Standards Development Milestone: Plenary Vote Milestone: Milestone: Post to Close PAP Catalog or IKB Reviews: GB Plenary PAP, CSWG,Recommendation Decision SGAC, PMO PAP 6

PAP 3 PAP 11 PAP 8 PAP 4 PAP 12 PAP 1 PAP 14 PAP 7 PAP 13 PAP 18 PAP 2 PAP 8 PAP 15 PAP 9 PAP 16 PAP 11 PAP 18

PAP 12 PAP 13 PAP 15 Note: Some PAPs are in multiple places due to the status of separate standards they are involved in. Submission PAP 16 PAP 17 PAP 5 PAP 0 PAP 10 PAP 11 PAP Closure Paperwork PAP StopLight Status Schedule Priority Action Plan doc.: IEEE 802.11-11/0975r1 Deliverables PAP 00 - Meter Upgradability Standard (TASKING COMPLETE) PAP 01 - Role of IP in the Smart Grid (TASKING COMPLETE) PAP 02 - Wireless Communications for the Smart Grid PAP 03 - Common Price Communication Model PAP 04 - Common Scheduling Mechanism PAP 05 - Standard Meter Data Profiles

PAP 06 - Common Semantic Model for Meter Data Tables PAP 07 - Electric Storage Interconnection Guidelines PAP 08 - CIM for Distribution Grid Management PAP 09 - Standard DR and DER Signals PAP 10 - Standard Energy Usage Information (TASKING COMPLETE) PAP 11 - Common Object Models for Electric Transportation PAP 12 - IEC 61850 Objects/DNP3 Mapping PAP 13 - Time Synchronization, IEC 61850 Objects/IEEE C37.118 Harmonization PAP 14 - Transmission and Distribution Power Systems Model Mapping PAP 15 - Harmonize Power Line Carrier Standards for Appliance Communications in the Home PAP 16 - Wind Plant Communications PAP 17 - Facility Smart Grid Information Standard PAP 18 - SEP 1.x to SEP 2 Transition and Coexistence =Complete/Closed =On Target =Tasking Complete Submission =Caution =Late May 2011 Activities - PMO Monthly Report Resources doc.: IEEE 802.11-11/0975r1

PAP Planned Completions by Quarter 200 9 PAP PAP 00 - Meter Upgradeability Standard PAP 01 - Role of IP in the Smart Grid PAP 02 - Wireless Communications for the Smart Grid 2010 2011 2012 Q QQQQQQQQQQQQQ 3 41 2 3 4 1 2 3 4 1 2 3 4 Highlights Remote meter upgradeability (COMPLETE). Bringing to GB for a vote in March. X IETF Smart Grid Internet Protocols RFC. GB recommended addition to CoS Dec 2010. (COMPLETE) X Wireless Guidelines Report (NISTIR) complete Dec 2010. Version 1 COMPLETE Jan 2011. Board introduction in April, 2011. Vote by GB in April. Currently in public comment period at OASIS. Seeking more utility involvement. X

PAP 03 - Common Price Communication Model X PAP 04 - Common Scheduling Mechanism X PAP 05 - Standard Meter Data Profiles Out of final public comment period at OASIS. SDO voting soon. AEIC guideline completed. PMO requested additional work to address technical issues raised by 5 meter manufacturers. AEIC plans to meet with them in April. X PAP 06 - Common Semantic Model for Meter Data Tables Addressing scope to ensure alignment with NIST and PAP team objectives. Difficulty getting participation from vendors and utilities. X PAP 07 - Electric Storage Interconnection Guidelines PAP 08 - CIM for Distribution Grid Management X Developing requirements affecting IEEE 1547 and IEC 61850-7-420 Close to public review at OASIS. Seeking additional utility stakeholder involvement. X PAP 09 - Standard DR and DER Signals

Awaiting standards handback from SDOs X PAP 10 - Standard Energy Usage Information X *NAESB Energy Usage Information Model complete in February 2011. PAP to close in Q1 of 2011. PAP 11 - Interoperability Standards to Support Plug-in Electric Vehicles X 2/3 SAE standards completed and voted on positively by Governing Board. Last standard should be done Q2-2011 PAP 12 - IEC 61850 Objects/DNP3 Mapping X PAP 13 - Time Synchronization, IEC 61850 Objects/IEEE C37.118 Harmonization X PAP 14 - Transmission and Distribution Power Systems Model Mapping IEEE and IEC currently working on standards development Requirements completed. Drafting standards in SDO committees. Working on use cases and requirements X PAP 15 - Harmonize Power Line Carrier Standards for Appliance Communications

in the Home X Completed BroadBand Coexistence. Working Narrow Band. BB standards under review, with GB introduction imminent. PAP 16 - Wind Plant Communications X Use cases and requirements complete. Guideline development by PAP team complete. Passing to SDO when maintenance team established. PAP 17 - Facility Smart Grid Information Standard PAP 18 - SEP 1.x to SEP 2 Transition and Coexistence X Facility Smart Grid Information Standard X PAP has just started work; 1 0 0 0 0 1 3 1 7 5 1 http://collaborate.nist.gov/twiki-sggrid/pub/SmartGrid/PMO/2011-04_SGIP_Monthly_Report_FINAL_V1.0.pptx Submission April 2011

doc.: IEEE 802.11-11/0975r1 CSWG Standards Review Queue 1. PAP 13: IEEE PC 37.238, IEEE 1588, and IEEE 61850-90-5 will complete in May. 2. PAP 18: SEP 1.0, 1.1, and 2.0. Having issue getting the right copies of SEP 1.0 and 1.1. CSWG actively participating in PAP 18. 3. PAP 11: SAE J2847 needs updated final review. Awaiting SAE to provide approved version to post to ANSI portal. 4. PAP 15 (broadband requirements): IEEE 1901 and ITU-T G9972. Awaiting IEEE to provide approved copy of 1901 to post to ANSI portal. Also awaiting assistance from a representative to assist CSWG in exact scope of IEEE 1901 used in PAP 15. 5. PAP 12: IEEE 1815 (DNP3). Ready for review, but is low in queue. 6. PAP 16: IEC 61400-25 review requested, but CSWG awaiting details on which parts to review since there are many parts. Submission April 2011 doc.: IEEE 802.11-11/0975r1 July 2011 Catalog of Standards Process http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/SGIPCatalogOfStandards Submission Slide 22 Bruce Kraem

May 2011 doc.: IEEE 802.11-11/0975r1 NIST PAP#2 History Abstract: This work area investigates the strengths, weaknesses, capabilities, and constraints of existing and emerging standards-based physical media for wireless communications. The approach is to work with the appropriate standard development organizations (SDOs) to determine the characteristics of each technology for Smart Grid application areas and types. Results are used to assess the appropriateness of wireless communications technologies for meeting Smart Grid applications. http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/PAP02Wireless Submission Slide 23 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 PAP2 Links

PAP02: Wireless Communications for the Smart Grid (6.1.5) Contents of this topicUseful Hot LinksAbstract: Status of PAP02: Wireless Communications for the Smart Grid (6.1.5) Task Details: Description: Objectives: Why: Where: Who: 2011 Upcoming Meetings May 10 - Teleconference 2:30pm ET May 24, June 7, June 21, July 5, July 19, Aug 2, Aug 16, Aug 30 - Teleconferenc e 2:00pm ET July 12-14, 2011 - SGIP Summer Meeting, Montreal Canada Submission Slide 24 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 Subscription to NIST PAP#2 To see the complete NIST Priority Action Plan list go here:

http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/ PriorityActionPlans#Individual_PAP_Lists To subscribe to PAP#2 mailing list go here: http://www.smartgridlistserv.org/cgi/wa.exe?SUBED1=SGIP -PAP02WG&A=1 Submission Slide 25 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 OpenSG SharePoint Documents http://osgug.ucaiug.org/UtiliComm/Shared%20Docum ents/Forms/AllItems.aspx Submission Slide 26 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1

NIST Timeline (Anticipated) August , 2009 July 28, 2010 August 4, 2010 September 15, 2010 September 16, 2010 September 30, 2010 October 29, 2010 November 4, 2010 Project initiation Draft 0.5 Call for Input to Section 6 End of draft 0.5 review period SGIP face-to-face, St Louis Tentative PAP 2 meeting Release of draft 0.6 End of draft 0.6 review period OpenSG + PAP2 meeting, Fort Lauderdale Extended edit period December 3, 2010 January 15, 2011 Release of Version 1 Continuation of project to extend findings ? December 2011 ? Submission Release of Version 2 Slide 27 Bruce

Kraem May 2011 doc.: IEEE 802.11-11/0975r1 NIST Timeline (Anticipated) January 15, 2011 Release of Version 1 Continuation of project to extend findings ? December 2011 ? Submission Release of Version 2 Slide 28 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 PAP#2 Version 1 Guideline for Assessing Wireless Standards for Smart Grid Applications Version 1.0 released Jan 13, 2011 http://collaborate.nist.gov/twiki-sggrid/pub/SmartGrid/PAP 02Objective3/NIST_PAP2_Guidelines_for_Assessing_Wirele ss_Standards_for_Smart_Grid_Applications_1.0.pdf

Submission Slide 29 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 Priority Action Plan for Wireless communications (PAP#2) Activity Summary Calls every two weeks details on NIST Twiki Version 1 paper approved by SGIP board Procedures approved Current primary tasks Propagation model Census Tracks Re-work Section 4 - and Matrix material Submission Slide 30 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 2011 NIST PAP2 Meeting History

Date & Time Date & Time 6/21/11 2:00PM ET 6/07/11 2:00PM ET 5/24/11 2:00PM ET 5/10/11 2:30PM ET 4/26/11 2:00PM ET 4/12/11 2:30PM ET 3/29/11 6:00PM ET 3/10/11 8:00AM PT 2/25/11 3:00PM ET 2/11/11 1:00PM ET Agenda & Slides Presented Approved Meeting Minutes Agenda & Slides Presented Approved Meeting Minutes Download Download (unapproved) Download Download Download, Download Detailed Framework Proposal (Cunni ngham) Download, Download Framework Proposal (Cunningham), Propagation Models (Gray), Spreadsheet of Propagation Models ( Gray)

Download Download Download Download Download, Download Rural Area Propagation Analysis, Spreadsheet Download Download Download, Download PAP02 Proposed Operating Procedure s Download Download http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/PAP02Wireless Submission Slide 31 Bruce Kraem doc.: IEEE 802.11-11/0975r1 July 2011 PAP2 Work Proposal http:// osgug.ucaiug.org/UtiliComm/Shared%20Documents/SG-NET%20PAP%20work-in-pro gress/PAP02-post-assessment-v1.0-work/PAP02-Extnd-work-framework-r0.3.pdf

Submission Slide 32 Bruce Kraem doc.: IEEE 802.11-11/0975r1 July 2011 PAP2 COMPLETION PLANS It is important to the utility companies to get some kind of equipment count that they can use to calculate their capex/opex. This is a reasonable request. However, as I indicated in one of my emails below, the best ATIS can do is to provide cell/sector count. The rest of the network is very access specific and, even worse, it is implementation specific in that access technology. For example, in LTE, we know how many logical entities we need for the core network to support n cells/sectors. These logical entities, however, can be implemented in one or many boxes. Standard does not dictate how the functional elements are to be implemented which results in different configurations depending on the infrastructure manufacturer. I would like to open up the discussion to other interested parties/SDOs. I am curious to hear if it is possible to calculate the actual equipment count in other access technologies beyond the cell/sector calculation. I realize that the timing is not the best since a number of folks are on holidays for the long weekend. But, I thought it may be good to get this email out before our PAP02 call next week. Submission Slide 33 Bruce Kraem doc.: IEEE 802.11-11/0975r1

July 2011 PAP2 COMPLETION PLANS It is important to the utility companies to get some kind of equipment count that they can use to calculate their capex/opex. This is a reasonable request. However, as I indicated in one of my emails below, the best ATIS can do is to provide cell/sector count. The rest of the network is very access specific and, even worse, it is implementation specific in that access technology. For example, in LTE, we know how many logical entities we need for the core network to support n cells/sectors. These logical entities, however, can be implemented in one or many boxes. Standard does not dictate how the functional elements are to be implemented which results in different configurations depending on the infrastructure manufacturer. I would like to open up the discussion to other interested parties/SDOs. I am curious to hear if it is possible to calculate the actual equipment count in other access technologies beyond the cell/sector calculation. Submission Slide 34 Bruce Kraem doc.: IEEE 802.11-11/0975r1 July 2011 OpenSG Payloads DRAFT1D CANDIDATE FOR V5.0 REQUIREMENTS TABLE HAS BEEN POSTED IN THE SG NETWORK TF PAP WORK-IN-PROGRESS "RQMT-TABLE-WIP" FOLDER. THIS VERSION MERGED THE PREVIOUS DRAFT1C 2ND TAB OF ADDITIONAL PAYLOADS INTO THE 1ST TAB "REQMTS-COMBINED" AND ALL OF THE "RQMT REF" CELLS HAVE BEEN POPULATED WITH VALUES. THE PREVIOUS HIDDEN COPY OF PIVOT TABLES HAVE BEEN UPDATED, AND THIS VERSION IS

SUITABLE FOR USE BY THE REFERENCE DIAGRAM TO REQUIREMENTS TABLE MACRO VETTING TOOL THAT IS BEING DEVELOPED. KEY STATS: 19 PAYLOAD-GROUPINGS (USECASES) 204 PAYLOADS 500 PAYLOAD-PARENT-SETS 7877 REQUIREMENT ROWS (INCLUDING PARENTS AND 2 ROWS FLAGGED FOR DELETION) http://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Forms/AllItems.aspx?RootFolder=%2fUtiliComm%2fShared%20Documents%2fSG%2dNET% 20PAP%20work%2din%2dprogress%2fRqmt%2dTable%2dwip&FolderCTID=&View=% 7bDB95205C%2d1142%2d45B1%2d97C0%2dA4DD7F9EC4DA%7d Submission Slide 35 Bruce Kraem doc.: IEEE 802.11-11/0975r1 July 2011 ITU SMART GRID LIAISONS WG18 Documents https:// mentor.ieee.org/802.18/dcn/11/18-11-0058-00-0000-summaryof-itu-r-documents.pptx https:// mentor.ieee.org/802.18/dcn/11/18-11-0049-01-0000-working-d ocument-towards-a-preliminary-draft-new-report-itu-r-sm-s mart-grid.docx Submission Slide 36

Bruce Kraem doc.: IEEE 802.11-11/0975r1 July 2011 SAMPLE FROM 049R1 Smart grid communication network technologies Various types of communication networks may be used in smart grid implementation. Such communication networks, however, need to provide sufficient capacity for basic and advanced smart grid applications that exist today as well as those that will be available in the near future. Assessing communications needs of various smart grid applications requires an understanding of 1) the control loop timeline of the application, 2) the amount of data that needs to be transferred at any particular time, 3) the number and location of devices with which communications must be maintained, and 4) the overall communication capacity of the proposed communication system. An applications timeline and tolerance for latency in transferring and analysing data or control signals is critical to determining appropriate communications capability. For example, the gathering of metering data for daily meter collection can tolerate a latency period of many hours (and even a period of several days in the case of monthly billing). But real-time, control-oriented applications such as voltage control, integration of distributed generation resources, and distribution switching require latency periods of no more than two seconds. The control loop timeline refers to the overall length of time to make a decision and initiate action relevant to a particular control application. For instance, a control decision that needs to be made with real-time information every 30 seconds cannot utilize a communications link that takes 60 seconds to transfer the related data. For example, distributed protection systems use multiple isolating switches and relays that disconnect power from a section of the electric distribution system in the event of a failure or short circuit. Such disconnection helps reduce the size and impact of any resulting outage, prevent widespread damage to the system, and minimize public safety hazards. In order to make control decisions, these systems rely on widely dispersed devices that access information about real-time conditions at other devices connected to the distribution grid. Distributed protection systems respond to events of only several milliseconds in duration and must communicate information just as quickly in order to perform their functions effectively. Submission Slide 37

Bruce Kraem doc.: IEEE 802.11-11/0975r1 July 2011 Submission Slide 38 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 NIST PAP#2 Previous Work May 24 - Teleconference 2:00pm ET Agenda & Presentation http://collaborate.nist.gov/twiki-sggrid/pub/SmartGrid/PAP02Wireless/Presentation_05242011.pptx Detailed Framework Proposal (Cunningham) http://collaborate.nist.gov/twiki-sggrid/pub/SmartGrid/PAP02Wireless/Frmwrk-Tool-Dtls-r0.1.xls June 7, June 21, July 5, July 19, Aug 2, Aug 16 - Teleconference 2:00pm ET July 12-14, 2011 - SGIP Summer Meeting, Montreal Canada http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/PAP02Wireless Submission Slide 39

Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 PAP2 Framework Comments The following is derived from a discussion conducted in the IEEE 802 meetings held May 9-13. The document used during the meeting can be found at: https://mentor.ieee.org/802.11/dcn/11/11-11-0720-02-0000-s mart-grid-ad-hoc-may-2011.ppt These slides further explain the understanding on what is being asked for in the Framework document and provides some views on how those requirements might be fulfilled. Submission Slide 40 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 Framework Observation & Guideline-1 In order to analyze an operational scenario we would need to have additional information on the number of nodes and their physical relationship. For example, in the DAP example below, how many nodes are

there, where are they and what is the characteristic terrain class within which they are located? Answer: The method used to compute the number of nodes an area will be based upon area x density. For example, if the area under consideration is 1 square miles and the density is 200 nodes per square mile then there would be 200 nodes in the area. The location will not be placed or copied from an actual map. However their locations in the grid space could be calculated using a pair of x-y random number generators. To ensure that all SDOs analyze the same problem, the node location calculations should be performed exactly once for each scenario and the grided node locations would be fixed and common for all rounds of analysis for all SDOs and technologies. y 1 0.9 0.8 0.7 0.6 0.5 0.4 0.3 0.2 0.1 0 0 0.1 0.2

0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 200 node example generated with random numbers Submission Slide 41 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 Framework Observation & Guideline- 2 Can it be assumed that all analysis would be based upon single technology deployment. Was there an expectation that a mixed technology deployment be analyzed?

Analyses will be performed using a single deployment technology. Submission Slide 42 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 Framework Observation & Guideline- 3 The analysis of the suitability of a deployment requires a calculation of a link budget. Link budget calculations require using radio performance numbers that are not defined by technology standards documents but are vendor specific. Hence, there may be some differences between individual suppliers radio performance numbers. It is proposed that each technology use a single representative set of radio performance numbers. The chosen set of parameters needs to be specified and approved by PAP2. Additionally, the parameter values would be proposed by each SDO and approved by PAP2. E.g. Receive Antenna pattern and gain profile Transmit Antenna pattern and gain profile Receiver sensitivity Transmit power It is proposed that each technology use a single set of radio performance numbers that represent best practice implementations. It is typically true that radio technology offer a range of functional modes. Perhaps the most familiar reason for the modes being the ability to optimize data rate at a given range (which translates to rate at a given link margin). Step 1 would be to agree on the set of parameters within PAP2. Step 2 would involve each SDO proposing the values they would use for the selected parameters. Step 3

would be PAP2 approval of the SDO specific parameter values for each mode of operation to be analyzed. Analyses will be performed using a single set of parameter values for each operational mode. Submission Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 Framework Observation & Guideline- 4 The analysis of deployment performance is presumed to be based upon a point to point relationship between a transmitter receiver pair. No analysis of repeaters or mesh links would be performed. Phase 1 Analysis Analyses performed using a DAP to node model would be denoted as Phase 1 and should be provided by each SDO. However, technologies providing repeater or mesh capabilities would most likely wish to produce Phase 2 analyses based upon these additional capabilties. Note that an additional requirement for meaningful comparison of Phase 2 results will be unambiguous definitions of terms such as repeater and mesh as these were not established in Guideline Version 1. Submission Slide 44

Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 Framework Observation & Guideline 5d The analysis of deployment performance could be based upon only the relationship between a transmitter receiver pair with messages being transferred from one radio MAC to another. Unfortunately this approach would not provide realistic throughput or latency analysis. Realism requires the inclusion of MAC behavior to represent both technology standard features and typical implementations. PHY MAC PHY MAC It is proposed that the PAP2 community needs to review parameters for inclusion. Candidates include: MAC queues, Buffer overflows, Packet loss/retry, transport protocol reliability (e.g. UDPvs httpACK/retry) , Packet size/fragmentation, media access/collision/backoff/retry, latency, etc. Step 1 would be to agree within PAP2 on the set of behavioral characteristics to be used. Step 2 would involve each SDO proposing the values they would use for the selected parameters.. Analyses will be performed using a single set of parameter values for each operational mode. Submission Bruce Kraem May

2011 doc.: IEEE 802.11-11/0975r1 Framework Observation & Guideline- 6 There is no data traffic volume specified. It is presumed that some portion of the OpenSG requirements would be selected to quantify the representative data traffic to be used for analysis. Please identify the traffic flow. Node quantity and type will be generated as generally described in Guideline #1. The network traffic will be determined by selecting a number of transaction types from the OpenSG Requirements spreadsheet. Submission Slide 46 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 Framework Observation & Guideline- 7 The initial Framework Basics document states: Minimum output: quantity of wireless std/tech/spectrum network gear required by endpoint density category, incremental gear type/count for RF propagation factors & engineering work-arounds for subscribers, and no endpoint coverage conditions Using the analysis guidelines 1-6 the results will show: How many nodes are reachable

How many (which?) nodes are actually designated as serviceable and are included in the performance analysis Packet reliability for each serviceable node Data throughput for serviceable node System latency Submission Slide 47 Bruce Kraem May 2011 doc.: IEEE 802.11-11/0975r1 Framework Observation & Guideline- - 8 How does the Framework Basics document relate to Guideline version 1? Where and How do the deliverables called for fit into the context of Wireless Guidelines version 2? The analysis results would be added to Wireless Guideline version 1 as a new Chapter. Submission Slide 48 Bruce Kraem doc.: IEEE 802.11-11/0975r1

Update on Modified-Erceg/SUI Path Loss Model May 24, 2011 Prepared by Doug Gray Consultant to WiMAX Forum Submission doc.: IEEE 802.11-11/0975r1 Outline Can Modified Erceg/SUI model be considered for lower (700 MHz) and possibly higher (6000 MHz) frequency? Addresses question from Bill Godwin Short answer: Yes, it looks reasonable Link Budget: The next step in wireless range prediction and coverage analysis 50 Submission doc.: IEEE 802.11-11/0975r1 Modified Erceg-SUI & Hata-Okumura at 700 MHz BS Antenna: 30 m SS Antenna: 2 m Good agreement between Erceg B & C & Hata Suburban Good agreement between

Erceg A & Hata Urban for Path Length > 3.5 km Within 10 dB for Path Length < 3.5 km Large difference between Hata-Okumura Model: Valid from 150 MHz to 1500 MHz Hata Rural and Erceg Type C BS Antenna >30 m (higher than rooftops) 51 Submission doc.: IEEE 802.11-11/0975r1 Modified Erceg-SUI & WINNER II at 6000 MHz BS Antenna: 25 m SS Antenna: 1.5 m Good agreement between WINNER II (Urban) and Erceg (Type A) Large difference between WINNER Rural and Erceg Type C WINNER II Model: Formulation similar to Hata-Okumura Valid from 2000 MHz to 6000 MHz BS Antenna much higher than mean building height 52

Submission doc.: IEEE 802.11-11/0975r1 Summary of Common Large Scale Models Path Loss Model Erceg-SUI Model - Modified ?700 to 6000? MHz Erceg-SUI Model 1700 to 2700 MHz ITU-R M.2135-1 N-LoS Rural Macro 2000 to 6000 MHz ITU-R M.1225 - Vehicular Path Loss 2000 +/- MHz COST231 Walfisch-Ikegami (N-LOS) 800 to 2000 MHz COST231 - Hata 1500 to 2000 MHz Hata-Okumura 150 to 1500 (1920) MHz WINNER II 2000 to 6000 MHz Egli Model (Rolling Hills no Foliage) 50 to 3000 MHz Foliage Weissberger Model Obstacles Epstein-Peterson Model 53 Submission BS

Relative to Antenna Mean Frequency Height Rooftop MHz 1500 1500 2000 hb hh 30 10 30 10 17 10 ? ? ? ? 5 -2 5 0.2 0 -2 >0 >0 >0

>0 >>0 >>0 2000 1500 1500 1500 2000 10 8 50 30 50 30 50 25 2000 2000 0m -1m Excess Loss Distance Dependence dB per Decade Excess Loss Frequency Dependence dB per Octave Type A or Type B or Type C or Type A or Type B or Type C or Urban Suburban Rural Urban Suburban Rural

28.0 37.9 28.0 37.9 19.2 20.0 -2.0 1.8 15.2 13.8 13.8 15.2 13.8 15.7 23.8 36.5 23.8 36.5 19.6 20.3 21.2 35.5 21.2 35.5 19.6 20.3 0.0 0.0 5.5 5.6 4.2

4.2 1.9 -2.0 1.8 15.7 13.8 2.9 5.1 1.8 1.8 5.1 5.1 20.0 0.9 0.9 2.8 4.7 1.8 1.8 0.0 0.0 2.7 4.4 1.8 1.8 0.0 0.0

3.5 3.6 1.9 0.9 0.9 0.4 0.4 0.0 5 to 27 dB/decade 1.7 to 5.3dB/Octave 6 dB/obstacle 25 dB/obstacle 0.0 dB/Octave 3.0 dB/Octave doc.: IEEE 802.11-11/0975r1 Link Budget: The Next Step for Range & Coverage Analysis System Gain (DL Data Channel, UL Data Channel, & Control Channels) Technology Specific, Max EIRP may be frequency band-specific BS & SS/terminal/actor: Tx Power, Antenna Gain, Rx Sensitivity, Smart antenna enhancements, etc Some SS parameters will vary with application Account for SG requirements for BER & Minimum Cell-Edge Thruput Fade Margin Value selected for desired SG Availability (99.9%, 99.99%, or ??)

Typical values: 8 to 12 dB Penetration Loss Necessary for outdoor-to-indoor or indoor-to-outdoor transmission Varies with frequency, wall material, & number of walls 54Submission Issues with Existing Simulations 55 Typical methodology: 3GPP2, 802.16m, ITU-R M.2135, etc. Technology specific with focus on mobility SG requirements dominated by fixed terminals Cluster of 19 base stations with specific BS to BS spacing Typically close resulting in higher channel capacity Applicable for specific frequency band 900, 2000 MHz SG looking for solutions from 700 to 6000 MHz Generally depend on path loss models assuming high BS antenna height (above roof-top): Hata, Cost231, WINNER II, etc. Not consistent with SG requirements: Erceg-Modified a better choice Relatively few active users/terminals per sector/cell: 10 users per sector (30 per BS) is typical This is not representative of a typical SG deployment (ex: SMs will number in the 1000s) Some Discussion Materials for July 5, 2011 PAP2 Call Prepared by Doug Gray Consultant to WiMAX Forum Copyright 2011 WiMAX Forum. All rights reserved.

Outline 1. Items that should be added or expanded in Version 2.0 Section 5 Items include: Link budget, & recommended allowances for fading, interference, & bldg penetration loss Estimating channel capacity w/o depending on technology-specific simulations 2. Prioritizing wireless performance features and attributes specifically for SG applications Section 4: Wireless Capabilities Matrix 3. Appendix 57 Link Budget Analysis System Gain (SysGn): Technology, vendor-specific well see a range based on the standards, antenna configurations, etc. Also SG application/usage-specific Rx Sensitivity related to required BER and cell-edge data rate Minimum of DL, UL, or Control Channel Fade Margin (Fm) Interference Margin (Im) Penetration Loss (Lp) Link Budget (LB): LB = SysGn (FM + Im + LP) 58 Can be a large number big impact on range Fading and Fade Margin

Shadow fading slow or medium-term fading Primarily due to obstructions Log-Normal Distribution May vary with terrain-type: Urban, Suburban, Rural, Indoor, etc Fast fading Primarily due to multipath (greater with mobile users) Rician distributed when dominant signal is present (LoS or Near LoS) Rayleigh distributed when no dominant signal present (sum of Gaussian variables) Different fade margins may be necessary for different technologies Impact of fading mitigated by various technology attributes 10+ dB may be necessary to achieve desired availability Significant impact on range and coverage 59 Log-Normal Shadow Fade Margin Some Examples Reference 3GPP2 PL Model Urban Hata 8.9 dB ITU-R M.1225 (Guidelines for IMT-2000)

Suburban Rural 10 dB 12 dB NGMN 8 dB ITU-R M.2135 (Guidelines for IMT-Advanced) 6 dB 8 dB 8 dB 8 dB 8 dB 8 dB 3.2 dB to 10 dB 5.56 dB Up to 11.2 dB

IEEE 808.16m Various Papers 60 Cost231 OutdoorIndoor 7 dB Interference Margin Interference Margin (Im): Self-interference and inter-operator interference (in some bands) Will differ with selected frequency reuse pattern Impacted by BS to BS spacing (closer spacing greater potential for self-interference) May differ with technology DFS, etc Typical values 0.5 dB for Reuse factor of 3 to 2 dB for a reuse factor of 1 Chan A Chan B Chan C 61 Reuse 3

Each sector has dedicated channel Requires more spectrum Chan A Chan A Chan A Reuse 1 One channel reused in each sector Must manage intersector interference Penetration Loss Penetration Loss (Lp): For indoor to outdoor transmission Will vary with: Frequency Wall material, thickness, number of walls, & angle of incidence ITU-R M.1225 OD to ID Generic Model predicts 11-12 dB at 2000 MHz with Std Dev = 8 dB NTIA Report 94-206 at 900 MHz Measurement Venue 62

Mean Std Dev Storeroom with metal siding 24.3 dB 6.3 dB NTIA Radio Bldg: 2 to 3 walls 18.9 dB 6.4 dB NTIA Radio Bldg: > 3 walls 28.8 dB 5.1 dB Residence (one wall) 3.2 dB 5.4 dB Residence (two walls) 6.6 dB 6.6 dB Going Forward

Version 2 should provide a table of suitable or recommended values for: Fade margins Interference Margin Penetration Loss Question 1: Can we come to a consensus within PAP2 for the above via published reports, papers, field experience, etc.? I think we can Question 2: How to fairly estimate channel capacity w/o using technology-specific simulations? 63 Estimating Channel Capacity: Three Alternatives 1) Accept estimates from SDOs based on their specific evaluation methodologies a) Parameter assumptions not consistent with SG use cases b) Results in apples-to-oranges comparisons 2) Develop a simulation methodology within PAP2 specific to SG to apply to all wireless alternatives a) Time-consuming process & may be difficult to reach consensus b) Probably beyond the scope of PAP2 - Version 2 3) Use a coverage area vs. S/N ratio approach a) Assumes uniform distribution of stationary end-user terminals b) Assumes all terminals are non-LOS c) Requires a table of S/N vs. data rate for each technology 64 S/N Ratio Increases with Decreased

Range Erceg model predicts 57.85dB per decade at 1800 MHz for Type A terrain with 10m BS antenna height Value decreases with higher BS antenna height 3.5 dB S/N at cell edge corresponds to Rx sensitivity for QPSK with coding (1.0 bit/Hz) Range and coverage area is dependent on link budget and required cell-edge data rate 65 -4.3 dB S/N at cell edge corresponds to Rx sensitivity for QPSK with coding & 6 repetitions (0.17 bits/Hz) Look-Up Table Required for each wireless technology DL Bit Rate UL Bit Rate (Mbps) (Mbps) Mod/Coding Req S/N* QPSK 1/2 Rep 6 -4.3

0.54 0.51 QPSK 1/2 Rep 4 -2.5 0.81 0.77 QPSK 1/2 Rep 2 0.5 1.61 1.54 QPSK 1/2 Rep 0 3.5 3.23 3.07 QPSK 3/4 16QAM 1/2 6.8 8.9

4.84 6.45 4.61 6.14 16QAM 3/4 13.0 9.68 9.22 64QAM 1/2 13.9 9.68 9.22 64QAM 2/3 17.3 12.90 12.29 64QAM 3/4 18.5 14.52

13.82 64QAM 5/6 20.3 * 1 Tx, 1 Rx Antenna DL:UL = 1.05 Channel BW= 10 16.13 15.36 WiMAX Example: TDD 10 MHz Channel BW 1024 sub-carriers DL/UL Ratio = 1.05 Permutation = AMC 768 data sub-carriers Rates shown in table are net after FEC, pilot, and control carriers 66 Copyright 2011 WiMAX Forum. All rights reserved. Estimating Average Channel Capacity Over Coverage Area Graph for WiMAX with10 MHz TDD channel, DL:UL ratio = 1.05 & AMC permutation For a 2.24 Mbps channel UL data rate at cell edge, avg UL channel capacity is 8.53 Mbps

UL Channel capacity is the area under the curve (I used area increments of 10%) Result takes account Terrain Type and BS antenna height The range and coverage area are dependent of link budget and frequency 67 For a 0.37 Mbps channel UL data rate at cell edge, avg UL channel capacity is 4.66 Mbps 45% increased range but lower channel capacity Section 4: Wireless Features Matrix Can we prioritize the wireless features? High, Medium, or Low Some examples: UL data rate & capacity more important than DL capacity Cell edge data rate more important than channel peak rate Mobility performance is not a high priority What role and priority for video surveillance with regard to security and disaster recovery? Etc. , etc.

There may be differences between WAN, FAN, & HAN Priorities will give SDOs areas on which to focus or provide more information Will indicate areas that may need more detail or explanation in Version 2 of the Wireless Guidelines document 68 APPENDIX 6 9 Copyright 2011 WiMAX Forum. All rights reserved. Estimating Channel Capacity: Slide 12 in Tabular Form QPSK 1/2 Rep 6 d/D 1.00 0.95 0.89 0.84 0.77 0.71 0.63 0.55 0.45 0.32 0.054 S/N

-4.3 -2.98 -1.50 0.18 2.12 4.41 7.21 10.82 15.92 24.63 68.93 Avg Data Rate UL Data Rate 0.51 0.51 0.77 0.77 1.54 3.07 4.61 6.14 9.22 15.36 15.36 4.66 QPSK 1/2 Rep 0 % of Coverage Area 100% 90.0% 80.0%

70.0% 60.0% 50.0% 40.0% 30.0% 20.0% 10.0% 0.29% S/N UL Data Rate 3.5 4.82 6.30 7.98 9.92 12.21 15.01 18.62 23.72 32.43 76.73 Avg Data Rate 3.07 3.07 3.07 4.61 6.14 6.14 9.22 13.82

15.36 15.36 15.36 8.53 70 Copyright 2011 WiMAX Forum. All rights reserved. Issues with Existing Simulations 71 Typical methodology: 3GPP2, 802.16m, ITU-R M.2135, etc. Technology specific with focus on mobility SG requirements dominated by fixed terminals Cluster of 19 base stations with specific BS to BS spacing Typically close resulting in higher channel capacity Applicable for specific frequency band 900, 2000 MHz SG looking for solutions from 700 to 6000 MHz Generally depend on path loss models assuming high BS antenna height (above roof-top): Hata, Cost231, WINNER II, etc. Not consistent with SG requirements: Erceg-Modified a better choice Relatively few active users/terminals per sector/cell: 10 users per sector (30 per BS) is typical This is not representative of a typical SG deployment (ex: SMs will number in the 1000s) 7 2 Copyright 2011 WiMAX Forum. All rights reserved.

Recently Viewed Presentations

  • PYTHON - CS Home

    PYTHON - CS Home

    CS 331 python Simple Python is a simple and minimalistic language in nature Reading a good python program should be like reading English Its Pseudo-code nature allows one to concentrate on the problem rather than the language Easy to Learn...
  • Soc. St. - bement.k12.il.us

    Soc. St. - bement.k12.il.us

    Soc. St. Chapter 9 & 10. The written language developed in Aryan villages - Sanskrit ... Which was a nomadic people that entered the Indus River valley around 1500 B.C.? Aryans . 19) The Indian subcontinent is part of the...
  • Highgate Converter Overview Prepared by Joshua Burroughs &

    Highgate Converter Overview Prepared by Joshua Burroughs &

    The converter transformers determine magnitude of the voltage on the dc side and therefore the maximum possible DC voltage. Harmonics are produced because of the 12-pulse current steps compared to sinusoidal currents. Basic Principle. 6 pulse, 10° firing angle (15°...
  • OCS Architecture Talk - Joinup.eu

    OCS Architecture Talk - Joinup.eu

    OCS Architecture Talk How, why, using what? Daniel CHIRIȚĂ - DIGIT.B1 29th of November 2012 Online Collection System - part of ECI Tool for helping organizers collect the 1 million required signatures What is OCS? What is OCS? You wish...
  • Aristotle  an influential Greek philosopher 2500 years ago

    Aristotle an influential Greek philosopher 2500 years ago

    proposed the "raisin bun" model which was soon replaced with a more accurate model. Positively charged atom. electron. Ernest Rutherford. scientist from New Zealand (1871-1937) designed an experiment to look inside atoms.
  • Coastal management 1 Coastal defence (management) against flooding

    Coastal management 1 Coastal defence (management) against flooding

    Cliff . regrading - extending it forward, making slope longer and less steep. Reduces the risk of mass movement. Rip rap placement - Large boulders at the base of the cliff to resist wave attack and dissipate wave energy. Drainage...
  • Right Triangle Trigonometry

    Right Triangle Trigonometry

    Trigonometric Functions: The Unit Circle Section 4.2 Objectives Find a point on the unit circle given one coordinate and the quadrant in which the point lies. Determine the coordinates of a point on the unit circle given a point on...
  • Planning Big Events - Ministry-To-Children

    Planning Big Events - Ministry-To-Children

    Step 3: Build a Team. Directors over each area. Registration. Advertising. Stuff/Resources. Volunteers. Set-Up/Décor/Tear Down