doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 1 +1 (321) Marvell Lane, Santa Clara, CA, Name Company Address Phone Bruce Kraemer Marvell Smart Grid ad hoc Meeting Information - March 2010 Date: Authors: Abstract: Information on Smart Grid of interest to WG11 – March 2010

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 2 Meeting Agenda & Context - NIST PAP#2 NIST is going to use (require) a model to demonstrate performance when operating in typical Smart Grid domains Details are to be found at the URL on Slide 2 Goal today is to: Promote awareness of Model Collect Model questions or change suggestions Plan for subsequent discussion on future calls and in March plenary

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 3 Outline 1.Overview of NIST PAPs 2.PAP#2 goals and sub tasks 3.PAP#2 Task 6 plan 4.IEEE approach to Task 6

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 4 Background The NIST interoperability process identifies a number of high priority issues including the role of IP and the use of wireless communications: –April 2009 workshop sggrid/bin/view/_SmartGridInterimRoadmap/InterimRoadmapWorks hop1 –May 2009 workshop sggrid/bin/view/_SmartGridInterimRoadmap/InterimRoadmapWorks hop2 –EPRI report to NIST, June e.pdf NIST convenes an SDO workshop in August 2009 in order to develop plans to address priority issues sggrid/bin/view/_SmartGridInterimRoadmap/PriorityActionPlans

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 5 The Current Priority Action Plans 0 Meter Upgradeability StandardMeter Upgradeability Standard 1 Role of IP in the Smart GridRole of IP in the Smart Grid 2 Wireless Communications for the Smart GridWireless Communications for the Smart Grid 3 Common Price Communication ModelCommon Price Communication Model 4 Common Scheduling MechanismCommon Scheduling Mechanism 5 Standard Meter Data ProfilesStandard Meter Data Profiles 6 Common Semantic Model for Meter Data TablesCommon Semantic Model for Meter Data Tables 7 Electric Storage Interconnection GuidelinesElectric Storage Interconnection Guidelines 8 CIM for Distribution Grid ManagementCIM for Distribution Grid Management 9 Standard DR and DER SignalsStandard DR and DER Signals 10 Standard Energy Usage InformationStandard Energy Usage Information 11 Common Object Models for Electric TransportationCommon Object Models for Electric Transportation 12 IEC Objects/DNP3 MappingIEC Objects/DNP3 Mapping 13 Time Synchronization, IEC Objects/IEEE C HarmonizationTime Synchronization, IEC Objects/IEEE C Harmonization 14 Transmission and Distribution Power Systems Model MappingTransmission and Distribution Power Systems Model Mapping 15 Harmonize Power Line Carrier Standards for Appliance Communications in the HomeHarmonize Power Line Carrier Standards for Appliance Communications in the Home 16 Wind Plant CommunicationsWind Plant Communications

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 6 Issue: Use of Wireless Communications in the Smart Grid There are a number of advantages for using wireless communications including: –Untethered access to information –Mobility –Interoperability –Reduced cost and complexity –Availability of technologies with different characteristics to choose from A number of challenges remain to be addressed: –How to choose among technologies with different characteristics? –How do we know which technology to use for what Smart Grid application? –Are there any implications for using a certain wireless technology in a certain environment? –Are there any deployment? Interference issues?

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 7 7 Review of PAP#2 tasks 1.Develop Smart Grid application communication requirements and devise a taxonomy for applications with similar network requirements –Draft under development and available for review sggrid/pub/SmartGrid/PAP02Wireless/app_matrix_pap.xlshttp://collaborate.nist.gov/twiki- sggrid/pub/SmartGrid/PAP02Wireless/app_matrix_pap.xls 2.Develop terminology and definitions 3.Compile and communicate use cases and develop requirements –is part of Task 1 4.Create an attribute list and performance metrics for wireless standards –Draft developed and available for reviewhttp://collaborate.nist.gov/twiki- sggrid/pub/SmartGrid/PAP02Wireless/NIST_PAP2-_Wireless_Characteristics-IEEE802- v_02.xlshttp://collaborate.nist.gov/twiki- sggrid/pub/SmartGrid/PAP02Wireless/NIST_PAP2-_Wireless_Characteristics-IEEE802- v_02.xls 5. Create an inventory of wireless technologies and standards that are identified by each SDO –Feedback is expected by December 6, Conduct an evaluation of the wireless technologies based on the application requirements –Perform a gap analysis and developing guidelines for the use of wireless technologies. 7

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 8 NIST PAP#2 Goals/Events Modeling introduced February 4 at SFO Hilton – Joint with UCAIug OpenSG Next meeting to review progress and address questions: March 31 at NIST Gaithersburg At least partial analytic results based upon execution of models against high priority Use Cases by June Neded: Clarification of how these results will be used. How are they coupled into SmartGrid Policy or Law/ What is the role of FERC?

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 9 Approach to PAP#2 Task #6 Task 6 is to perform the mapping and conduct an evaluation of the wireless technologies based on the application communication requirements developed in Task 1 and the inventory of wireless technologies and their associated characteristics collected in Task 5. During the February 4, 2010 PAP2 meeting that was held in San Francisco in conjunction with the OpenSG meetings, it was agreed that an evaluation methodology similar to the one presented by NIST and discussed by the group be used to perform Task 6. The group has also decided to issue a call for contribution of modeling tools and resources to assist in conducting the evaluation:OpenSG Indication of interest by February 19, 2010 to assist in conducting the evaluation. Contribution of wireless technologies modeling tools by February 19, The tools contributed must be made available on the NIST twiki and available for use by all parties. Contribution of measurement and experimental data for validating the performance evaluation results.

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 10 NIST Modeling Presentation Detailed description of the modeling approach can be found at: sggrid/pub/SmartGrid/PAP02Wireless/PAP2m odeling.ppthttp://collaborate.nist.gov/twiki- sggrid/pub/SmartGrid/PAP02Wireless/PAP2m odeling.ppt

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 11 OpenSG Information Input from Open SG SG-NET received on February 22, 2010: The reference architecture models locations are: ease_2/SG-NET-diagram-r0.4e-with-Xflows.pdfhttp://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Interium_Rel ease_2/SG-NET-diagram-r0.4e-with-Xflows.pdf ease_2/SG-NET-diagram-r0.4e.pdfhttp://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Interium_Rel ease_2/SG-NET-diagram-r0.4e.pdf The SG-Network functional requirements spreadsheet location is: ease_2/SG-Net_TF_%20funct-volumteric-reqs_v2.xlshttp://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Interium_Rel ease_2/SG-Net_TF_%20funct-volumteric-reqs_v2.xls The SG-Network system requirements specification locations is: ease_2/SG%20Network%20System%20Requirements%20Specification %20v2.dochttp://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Interium_Rel ease_2/SG%20Network%20System%20Requirements%20Specification %20v2.doc

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 12 NIST Modeling Tools provided by NIST and used in presentation PAP2modeling.ppt PAP2modeling.ppt nist_80211_mac.m: Matlab code for 80211_MAC_Modelnist_80211_mac.m nist_80211_MAC_readme.pdf: Readme file for using the model Matlab codenist_80211_MAC_readme.pdf SNRcdf.m: Matlab code for computing SNR probability at wireless receiverSNRcdf.m SNRcdfCell.m: Matlab code for coverage analysisSNRcdfCell.m nist_phy_model_readme.pdf: Readme file for using Matlab code for SNRcdf and SNRcdfCellnist_phy_model_readme.pdfSNRcdfCell nist_channel_propagation_models.pdf: Channel propagation modelsnist_channel_propagation_models.pdf

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide Meter Reporting Application: Mean Delay versus Offered Load

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 14 Initial Questions from Ted Booth As part of the PHY model, it’s not clear how NIST derived interference (I 0 ) first introduced on slide 16. In access methods, usually, interference means signals from other BSS or other device's signal emission on the operating channel. However, it’s not clear what NIST assumes here. Comments? Regarding Transmit Power Control (TPC) (slide 17), Sony believes most of the current devices do not apply dynamic transmit power control. What’s your assessment here? The NIST Models allow for either approach. Comments? Looking again at TPC in the MAC Model, traditionally most implementations try to use the best MCS to achieve higher throughput; this will significantly impact results out of the Model. How should the Model properly takes this into account?

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 15 Future Smart Grid ad hoc calls Schedule plan was for Wednesdays at 2pm EST Feb 10 Feb 17 March 3 March 10 Plenary meeting March Joint WG discussion during 802 Plenary in Orlando on Thursday March 24 Future call plans will be discussed during March Plenary

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 16 EPRI Whitepaper Whitepaper I_ ConceptsAdvancementDER.pdfhttp:// I_ ConceptsAdvancementDER.pdf

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 17 Information Source Links

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 18 NIST Next PAP#2 meetings 1 day at NIST HQ on March 31

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 19 NIST mailing list General access portal sggrid/bin/view/SmartGrid/PriorityActionPlanshttp://collaborate.nist.gov/twiki- sggrid/bin/view/SmartGrid/PriorityActionPlans PAP Lists lists have been establish for each PAP. These lists support self registration using the links below. They will replace the current set. Where possible, the SGIP Administrator will autoregister those presently on the list. If you have any question, please self register and this will ensure that you are on the desired list.SGIP

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 20 OpenSG

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 21 Prior meeting material

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 22 Background information High Level Questions National Smart Grid Perspective –EPRI View What has previously transpired? NIST PAP#2 What is happening over the next two months Longer term goals, events, project plans. Observations/Assumptions/Conclusions/Discussion Steps needs to take to fit into the Smart Grid plan

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 23 High Level Questions What is happening in Smart Grid arena? Is properly positioning its existing and pending standards and amendments for acceptance in SG? Participation in key Smart Grid activities Are there any identifiable additions or changes that should be considered to make more useful in SG domains?

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 24 Observation/Assumption/Conclusion #1 Dozens of organizations are involved but our focus is primarily on: NIST SGIP sggrid/bin/view/SmartGrid/PriorityActionPlanshttp://collaborate.nist.gov/twiki- sggrid/bin/view/SmartGrid/PriorityActionPlans IEEE P2030 Discussion: Other 802 groups such as , , , 802.1, 802.3

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 25 Observation #2 There is a substantial amount of material already created by NIST and other long term SmartGrid participants that describe Application Domains and Use Cases. There is no need for to duplicate this work. There is a need to make these data flow models more complete/quantitative. Task 1 of NIST PAP#2 intends to supply this information. Discussion:

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 26 AMI Use Case Report to NIST on Smart Grid Interoperability Roadmap Source: Report to NIST on Smart Grid Interoperability Roadmap

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 27 Source: Report to NIST on Smart Grid Interoperability Roadmap NIST Roadmap Description of a Domain

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 28 Other examples of Requirements Example #1 - description of need for Home Area Network ements/OpenHAN%20Specification%20Dec.ppthttp://osgug.ucaiug.org/sgsystems/openhan/HAN%20Requir ements/OpenHAN%20Specification%20Dec.ppt

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 29 Observation #3 The NIST PAP#2 Tasks deserve considerable attention Discussion:

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 30 NIST PAP Overview (1) Priority Action Plans (PAPs) Described PAPs arise from the analysis of the applicability of Standards to the Use Cases of the Smart Grid. PAPs include identified experts in relative SDOs, known as the PAP Working Group Management Team. Specifically, a PAP addresses either: A gap where a standard or standard extension is needed: The need for meter image-download requirements is an example of a non-existing standard needed to fill an identified gap. An overlap where two complementary standards address some information that is in common but different for the same scope of an Application: An example of this is metering information where CIM, 61850, ANSI C12.19, SEP 1&2 all have non-equivalent methods of representing revenue meter readings. PAPs should only be created when the SGIP determines there is a need for interoperability coordination on some urgent issue. The PAPs themselves are executed within the scope of the SDOs and Users Groups that sign up for tasks that implement the plans. The duty of the SGIP is to facilitate this process, ensure that all PAP materials are publicly available in real time on the TWiki (that is, not entirely within the domain of the SDOs which prevents all but membership access), and provides guidance when the participants in the PAP are at odds or unsure of its goals.SGIP

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 31 NIST PAP Overview (2) It will often be the case that the SDOs that are executing the PAP tasks (as part of the PAP Working Group Execution Team) diverge from the original intent of the PAP. This is due to their natural, and correct, orientation towards their own specific goals and needs. The PAPs arise from the broader stakeholder involvement in the Smart Grid problem space and such has identified goals that come from this broader scope. In these cases, the parties are brought together under the auspices of the SGIP and an attempt to resolve the differences is pursued. The possibility could arise where this is not sufficient to move the PAP forward. In this case the PAP WG or the SGIP can:SGIP Revise the PAP to accommodate the concerns of the implementers, or, Can redistribute the tasks of the PAP to organizations more in line with the needs of the scope of the PAP. Rescind the PAP judging that it is no longer in the interest of the SGIP to pursue.SGIP

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 32 NIST PAP2 Wireless Communications for the Smart Grid (6.1.5) sggrid/bin/view/SmartGrid/PAP02Wirelesshttp://collaborate.nist.gov/twiki- sggrid/bin/view/SmartGrid/PAP02Wireless 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.

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 33 NIST PAP#2 Description: Review existing documentation and ongoing work to assess the capabilities and weaknesses of wireless technologies operating in both licensed and unlicensed bands and to develop guidelines on their use for different Smart Grid application requirements.

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 34 NIST PAP#2 Objectives: Identify requirements for use of wireless technologies for the Smart Grid. Identify guidelines for effectively, safely, and securely employing wireless technologies for the Smart Grid. Identify approaches to define the strengths and weaknesses of candidate wireless technologies to assist Smart Grid design decisions. Analyze co-channel interference issues and develop coexistence guidelines for operation in unlicensed bands. Identify key issues to be addressed in wireless assessments and development for the Smart Grid.

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 35 NIST PAP#2 Why: Wireless technologies are one of many types of media that could meet many Smart Grid requirements by enabling access where other media are too costly or otherwise not workable. However, different types of wireless technologies also have different availability, time-sensitivity, and security characteristics that may constrain what applications they are suitable for. Therefore, different wireless technologies must be used with knowledge of their varying capabilities and weaknesses in all plausible conditions of operation. This work provides objective information on the appropriateness of use.

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 36 NIST PAP#2 Where: Wireless can be used in field environments across the Smart Grid including generation plants, transmission systems, substations, distribution systems, and customer premises communications. The choice of wireless or non-wireless, as well as type of wireless must be made with knowledge of the appropriate use of the technology.

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 37 NIST PAP#2 – Next Meeting PAP 2 session at OpenSG Users Group, San Fransisco, February 4, 2010:OpenSG A face-to-face meeting will take place on February 4th, 2010, starting at 8am until 3:00pm. This meeting is collocated with the OpenSG User Group meetings in San Fransisco during the week of February 1, Information about registration and the hotel venue can be found at:OpenSG

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 38 NIST PAP#2 Tasks Task 1: Segment the smart grid and wireless environments into a minimal set of categories for which individual wireless requirements can be identified. Task 2: Develop Terminology and definitions. Task 3: Compile & communicate use cases and develop requirements for all smart grid domains in terms that all parties can understand

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 39 NIST PAP#2 Tasks Task 4: Compile and communicate a list of capabilities, performance metrics, etc. in a way that all parties can understand. - Not quantifying any standard, just defining the set of metrics. Task 5: Create an inventory of wireless standards and their associated characteristics (defined in previous task) for the environments identified in task 1. Task 6:Perform the mapping and conduct an evaluation of the wireless technologies based on the criteria and metrics developed in task 4.

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 40 NIST PAP#2 -Network Information Both IP and wireless communications priority action plans include as a first task the development of network requirements for Smart Grid applications. Identifying these requirements is key in order to develop guidelines for the use of IP and wireless communications in the context of the Smart Grid.

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 41 NIST PAP#2 Functional Requirements sggrid/pub/SmartGrid/PAP01InternetProfile/SG_Com munications_funct-reqs_v1-draft.xlshttp://collaborate.nist.gov/twiki- sggrid/pub/SmartGrid/PAP01InternetProfile/SG_Com munications_funct-reqs_v1-draft.xls

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 42 NIST PAP#2 – Task 5 Guidance Task 5 calls for the collection of an inventory of wireless technologies, based on the parameters and metrics developed in Task 4, to be filled by each SDO. The purpose of the row entries in the wireless capability matrix NIST_PAP2- _Wireless_Characteristics-IEEE802-v_02.xls developed in Task 4 is to allow high level assessment of the suitability of particular wireless standard based technologies for use in various applications and domains of the Smart Grid.NIST_PAP2- _Wireless_Characteristics-IEEE802-v_02.xls Since many of the parameters in the matrix have dependencies on each other, e.g. data throughput, range and mobility, the matrix should be filled out by providing a consistent set of parameter values, rather then best case values for each parameter. By a “consistent set” we mean that one picks some “operating point” for the technology and provides parameter values (for those that depend on operating point) that are consistent. For example, maximum data rate will not be delivered at maximum range. A column entry is expected to provide values for the error rate, range, throughput, mobility and other interrelated parameters consistent with the chosen operating point. It would be appropriate to complete more than one column for an individual technology to display the results for more than one operating point.

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 43 NIST PAP#2 – Task 5 so far

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 44 Observation #4 The Matrix rows were adequate for collecting information from SDOs. Discussion: The rows do/do not require further modification.

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 45 Observation #5 The operating points used were chosen by the SDOs. This was adequate for collecting first response information. Discussion: The operating point should be “standardized” to allow useful comparisons.

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 46 Observation #6 Within WG11, reporting on Smart Grid activities in an ad hoc forum once time block per session is adequate. Discussion:

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 47 Plans for Thursday One more session Thursday am1 Topics to be addressed: 1. Review the operating options /selections needed for Task 5. Process or completion. –Process for moving on thru Task 6 2. OpenSG/PAP2 activity planning Mhz ISM reband for (Halasz presentation) 4. Coordination mechanism with 15.4g? 5. Link to Emergency Services? 6. Plan for March…. Plan for ad hoc: Avoid overlap with 15.4g – coordinate with 15.4g Suggestion: Tuesday pm1 and Thursday am1 Cybersecurity EC SG

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 48 NIST PAP#2 – Next Meeting PAP 2 session at OpenSG Users Group, San Fransisco, February 4, 2010:OpenSG A face-to-face meeting will take place on February 4th, 2010, starting at 8am until 3:00pm. This meeting is collocated with the OpenSG User Group meetings in San Fransisco during the week of February 1, Information about registration and the hotel venue can be found at:OpenSG

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 49 Planning for OpenSG venue PAP#2 face to face meeting February 4 at SFO Hilton How much data traffic flow characterization information will be available? Will there be any matrix row changes? How do we establish a common set of “operating points”?

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 50 Operating Point How should operating points be described to ensure common understanding. How to choose “operating points” with some degree of commonality across a diverse set of radio technologies and operating scenarios to allow comparison without requiring full channel models and simulations?

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 51 Operating Point – Discussion starter Maximize link margin, maximize range, accept low date rate BPSK, 1 Mbps, single antenna Medium range, moderate data rate Clause 20, 64QAM,single stream, single antenna, OFDM, 40 MHz channel, 120 Mbps Short range, maximum data rate Clause 20, four stream, four antenna OFDM, 40 MHz channel, 600 Mbps

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 52 Operating Point Group Discussion Harmonize operating point based upon: Operating environment 1.Inside a house –Primary: Range, data rate, latency, noise environment –Secondary (QoS): Reliability, availability (need to include additional layers) (bit, packet) 2. Sub-station & generating plant –Range, data rate, latency, noise environment 3. Collection – back haul - long range –Range, data rate, latency, noise environment

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 53 Operating Point Group Discussion Regarding request that operating point include Availability and Reliability, how to measure these parameters? Group conclusion: reuse terms from matrix E.g., Link availability is measured as failure rate per 1000 sessions

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 54 Consideration of NIST Link budget Method GENERAL PURPOSE LINK BUDGET CALCULATOR For arbitrary wireless communication radio links, this calculator explains the terms in the link budget and gives the user the opportunity to enter or change the parameters. Macros invoked by clicking on buttons guide the user through the various options for selecting and entering the parameters. For definiteness, the calculator uses the Hata outdoor propagation loss model. The calculator was developed as an Excel spreadsheet application by Leonard Miller. It uses a new method for calculating the link margin needed to achieve a desired reliability when there is both lognormal shadowing and Rayleigh fading.new method SOFTWARE DOWNLOAD FILE Excel spreadsheet: download request form Version 1.24, added reminder to recalculate noise power when rate is changed 1/17/06 (Complete revision history listed on page 1 of spreadsheet)download request form

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 55 LinkCalc: NIST Link Budget Calculator The performance of a digital radio system, in terms of its bit error rate (BER) or probability of bit error (Pe), is related to the bit energy-to-noise density ratio (Eb/No) at the receiver, where "noise" may include interference in addition to the thermal noise generated in the receiver. Theoretical analysis of system performance is based on postulating a value for the signal-to-noise power ratio (SNR) at the receiver, which can be converted to received Eb/No. When assessing the actual system performance in a particular application, it is necessary to calculate the actual received SNR. This calculation requires a "link budget," which simply is a careful accounting of the various terms in the following equation for received SNR expressed in dB units: SNR(dB) = Received signal power(dBm) - receiver noise power(dBm) where, as illustrated in the diagram, the link gains include antenna gains and the link losses can be grouped into three cate- gories: transmission losses (Lt), propagation loss (Lp), and reception losses (Lr).

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 56 LinkCalc: NIST Link Budget Calculator Options FOR A POSITIVE SURPLUS, you can - decrease the transmitter power - use less directive antennas or a cheaper receiver - use lower antennas or a longer link distance FOR A NEGATIVE SURPLUS, you can - increase the transmitter power - use more directive antennas or a better receiver - use higher antennas or a shorter link distance

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 57 Teleconference suggestion There is 1 work weeks between this IEEE session and the OpenSG/PAP#2 meeting. IEEE 802 has an opportunity to further develop the matrix rows, explanations and operating points to enhance their utility in moving into task 6. When further details on the data flow characterisitics become available, there will be a need to map technology against application domain.

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 58 Establish Smart Grid ad hoc Provide a forum for on-going /timely review of Smart Grid topics –Encourage participation from other 802 groups 1. Assist in the development & completion of PAP#2 2. Refine the 900 MHz project proposal 3. Coordination with 15.4g Indentify other projects that would serve Smart Grid requirements Other topics? Leadership? Conference calls? Wednesdays at 2pm Eastern starting on Feb 10 (no call on Feb 24)

doc.: IEEE /0213r2 Submission March 2010 Bruce Kraemer, MarvellSlide 59 Information sources NIST twiki sggrid/pub/SmartGrid/WebPreferences/TWiki_NIST.pnghttp://collaborate.nist.gov/twiki- sggrid/pub/SmartGrid/WebPreferences/TWiki_NIST.png NIST Link Budget Calculator tmlhttp:// tml