Smart Grid Technology Discussions 2010

1. Smart Grid Technology Discussions 2010 Date: 2010-September-13 Abstract: Discussion NIST PAP#2 Report Discussion of other industry & standards activities Bruce Kraemer, Marvell

2. Monday Meeting Agenda • Outline of plan for the week & process to generate comments on the content of the NIST PAP#2 report, r5. - 10 min • Bluetooth Smart Energy Initiative – Tom Siep – 20 min • Comment preparation – 80 min • Tuesday meeting plan – 10 min • Other? Bruce Kraemer, Marvell

3. Monday Agenda Item 4.1.12 Smart Grid Meetings to prepare commentson NIST PAP#2 Wireless Report Bruce Kraemer, Marvell

4. NIST Report • R5 was posted at: • http://collaborate.nist.gov/twiki-sggrid/pub/SmartGrid/PAP02Wireless/NIST_Priority_Action_Plan_2_r05.pdf Bruce Kraemer, Marvell

5. July 28, 2010 Draft 0.5 August 4, 2010 Call for Input to Section 6 September 15, 2010 End of draft 0.5 review period September 16, 2010 SGIP face-to-face, St Louis Tentative PAP 2 meeting NIST Timeline September 30, 2010 Release of draft 0.6 October 29, 2010 End of draft 0.6 review period November 4, 2010 OpenSG meeting, Miami Tentative PAP 2 meeting SGIP face-to-face, Chicago PAP 2 meeting December 3, 2010 Release of Version 1 Bruce Kraemer, Marvell

6. NIST Expectations • Release 0.6 contains mature contents for all sections • Minor changes are expected between release 0.6 and 1.0 to allow for NIST internal review process • Technical contributions in the form comments to current draft and/or new material shall be posted on the twiki and made publicly available • Technical contributions will be processed as they are received up to the end of the review period • Allow time to provide comment resolution and reach consensus prior to the close of the review period. Bruce Kraemer, Marvell

7. Next NIST PAP 2 meetings • SGIP meeting in St Louis, September 16, 2010 • Is there a need for a PAP 2 meeting? • Co-located with OpenSG meeting, November 4, 2010, Miami FL. • SGIP meeting, December 1-3, 2010, Chicago, IL Bruce Kraemer, Marvell

8. Teleconference discussion topics for August - September 08 Smart Grid ad hoc calls: • Document 955 r6 • https://mentor.ieee.org/802.11/dcn/10/11-10-0955-06-0000-smart-grid-ad-hoc-summer-2010-plans.ppt Bruce Kraemer, Marvell

9. Introduction to Smart Energy • Smart Energy Tom Siep Bruce Kraemer, Marvell

10. NIST PAP#2 Report Comments Bruce Kraemer, Marvell

11. Comment #01 • Section 4.2.1.3 talks about Coverage Area. It is important to discuss coverage in conjunction with data rates and link margin for example, in order to avoid associations between inconsistent pieces of information, e.g., citing the largest coverage area achievable by a given technology along with the highest data rate achievable by the technology is incorrect – generally the two have a reverse relationship and the highest coverage is achievable at the lowest data rate. • Suggested text change: Agreed to text change: • Add the following text at the end of Section 4.2.1.3: When comparing coverage areas between different technologies, it is important to take into account the link budgets used in the coverage computation. Note that the largest coverage area achievable by a specific technology typically requires transmission at the lowest data rate used by that technology. Bruce Kraemer, Marvell

12. Comment #02a • Section 4.2.1.4 talks about Mobility. It would be useful to mention the data rates achievable at various mobility levels to avoid assumptions that mobile devices can communicate at the highest data rates used by a specific technology. • Suggested text change: • Add the following text at the end of Section 4.2.1.4: Comparisons between the capabilities of different mobile technologies have to take into account the maximum data rate achievable at each mobility level -- mobile devices may not be able to communicate at the highest available data rates when moving at high speeds. Bruce Kraemer, Marvell

13. Comment #03 • Section 4.2.1.5 talks about Data Rates. • Suggested text change: Agree in principle. Xxxcast terms need to be defined either here or in Section 2. Also need a description of block tranmission. • Add the following text at the end of Section 4.2.1.5: Additional factors to consider when discussing data rates: • Throughput must be considered in conjunction with packet size, coverage range and rate of mobility (if any). • It is important to distinguish between unicast, multicast and broadcast rates, as they may not be the same for a given wireless technology. • (This text needs some rework ) Throughput depends on medium access scheduling, including the capability to provide block transmissions (whereby multiple data packets can be sent in succession with minimum or no individual medium access operations per packet except before the first packet is sent), and/or block acknowledgements (whereby a single acknowledgement packet can acknowledge multiple preceding data packets). The capability and flexibility to optimize block transmissions and acknowledgements can have a significant effect on GoodPut. • Move this to another section • The use of rate adaptation mechanisms, where the data rate on a link is reduced when the quality of the link degrades and increased otherwise, which (results change to can result) in higher throughput than using a constant data rate. Bruce Kraemer, Marvell

14. Comment #03a • The use of rate adaptation mechanisms, where the data rate on a link is reduced when the quality of the link degrades and increased otherwise, which may result in a higher throughput than using a constant data rate. Bruce Kraemer, Marvell

15. Unicast • From Wikipedia, the free encyclopedia • In computer networking, unicast transmission is the sending of messages to a single network destination identified by a unique address. http://en.wikipedia.org/wiki/Unicast Bruce Kraemer, Marvell

16. Unicast Proposal Unicast is a form of transmission where a message from a source is sent to a specific associated destination node. Bruce Kraemer, Marvell

17. Multicast • In computer networking, multicast is the delivery of a message or information to a group of destination computers simultaneously in a single transmission from the source creating copies automatically in other network elements, such as routers, only when the topology of the network requires it. http://en.wikipedia.org/wiki/Multicast Bruce Kraemer, Marvell

18. Multicast Proposal • Multicast is a form of transmission where a message from a single source is sent simultaneously to a specific set of associated destination nodes. Bruce Kraemer, Marvell

19. Broadcast • In computing, broadcasting refers to a method of transferring a message to all recipients simultaneously. • In computer networking, broadcasting refers to transmitting a packet that will be received by every device on the network. In practice, the scope of the broadcast is limited to a broadcast domain. Broadcast a message is in contrast to unicast addressing in which a host sends datagrams to another single host identified by a unique IP address. http://en.wikipedia.org/wiki/Broadcasting_(computing) Bruce Kraemer, Marvell

20. Broadcast Proposal • Broadcast is a form of transmission where a message from a single source is sent simultaneously to all of the associated destination nodes. Bruce Kraemer, Marvell

21. Broadcast Options • Broadcast is a form of transmission where a message from a single source is sent simultaneously to any destination node. • Broadcast is a form of transmission where a message from a single source is sent simultaneously to all nodes. • Broadcast is a form of transmission where a message from a single source is sent to all destination nodes. • Broadcast is a form of message transmission where a message from a single source is sent to all destination nodes. • Broadcast is a form of message transmission where a message is sent from a single source to all potential receiving nodes. Bruce Kraemer, Marvell

22. Comment #04 • Section 4.2.1.6 talks about RF utilization. • Suggested text change: • Add the following text at the end of Section 4.2.1.6: • Agree in principle– needs rewrite to improve clarity. Consider the power level regulations for the different channels used by a particular technology, e.g., some Unlicensed National Information Infrastructure (UNII) channels at 5GHz have lower maximum allowed power levels from the maximum allowed for unlicensed band operation. • Accepted: Consider the impact of Dynamic Frequency Selection (DFS) regulations on the channels used by a particular technology, e.g., certain UNII channels are subject to DFS regulation which requires wireless devices to change channel when they detect the use of radar on their current channel. Bruce Kraemer, Marvell

23. Comment 04a • Add the following text at the end of Section 4.2.1.6: • Consider the power level regulations for the different channels used by a particular technology. • Consider the impact of Dynamic Frequency Selection (DFS) regulations on the channels used by a particular technology, e.g., certain UNII channels are subject to DFS regulation which requires wireless devices to change channel when they detect the use of radar on their current channel. Bruce Kraemer, Marvell

24. Comment #05 • Section 4.2.1.7 talks about Data Frames and Packets. It is important to consider frame duration in conjunction with data rate and size of the frame. Also, we need to consider multicast and broadcast frames in addition to unicast frames. • Suggested text change: Agreed • Modify item “a)” in Section 4.2.1.7 as follows: • What is the maximum frame duration for a unicast, multicast and broadcast frame respectively, and what are the corresponding frame size and data rate at which each type of frame was sent? • Modify item “b)” in Section 4.2.1.7 as follows: • What is the maximum packet size that can be sent in one unicast, multicast and broadcast radio frame respectively? • Modify item “c)” in Section 4.2.1.7 as follows: • Does the radio system support segmentation of unicast, multicast and broadcast packets respectively, when the payload size exceeds the capacity of one radio frame? Bruce Kraemer, Marvell

25. Comment #06 • Section 4.2.2.4 talks about Connection Topologies. The Bus and Ring topology need to be removed, they are not wireless topologies. One way to characterize wireless topologies is as single hop and multi-hop (statically configured or mesh), and wireless links as point-to-point, point-to-multipoint, and omnidirectional. We need to add figures that correspond to the text we end up with. • Suggested text change: Agree in principle. Need to explain differences between single hop, multi-hop and mesh. Also need t explain static configured and dynamically configured. • Remove the Bus and Ring figures, re-label the Star figure as “Point-to-Multipoint Link”, re-label the Mesh figure as “Mesh Network Topology” and replace the current text in Section 4.2.2.4 with the following: Wireless network topologies can be divided into single hop and multi-hop, where a multi-hop topology can be statically configured, or can be dynamic and self-forming, e.g., a mesh. A wireless link can be point-to-point, point-to-multipoint, or omnidirectional. Bruce Kraemer, Marvell

26. First paragraph from Wikipedia on Mesh networking • Mesh networking is a type of networking wherein each node in the network may act as an independent router, regardless of whether it is connected to another network or not. It allows for continuous connections and reconfiguration around broken or blocked paths by “hopping” from node to node until the destination is reached. A mesh network whose nodes are all connected to each other is a fully connected network. Mesh networks differ from other networks in that the component parts can all connect to each other via multiple hops, and they generally are not mobile. Mesh networks can be seen as one type of ad hoc network. Mobile ad hoc networks (MANET) and mesh networks are therefore closely related, but MANET also have to deal with the problems introduced by the mobility of the nodes. Mesh networks are self-healing: the network can still operate when one node breaks down or a connection goes bad. As a result, the network may typically be very reliable, as there is often more than one path between a source and a destination in the network. Although mostly used in wireless scenarios, this concept is also applicable to wired networks and software interaction. The animation at the right illustrates how wireless mesh networks can self form and self heal. For more animations see History of Wireless Mesh Networking http://en.wikipedia.org/wiki/Mesh_network Bruce Kraemer, Marvell

27. MESH and Hop Definitions • Proposed PAP2 Guidelines Document Definitions • Hop: The term hop is used to signify a link between a pair of devices that a frame or packet needs to traverse to reach one device from the other. • Single-Hop Network: A single-hop network is one in which devices can only communicate with each other directly, e.g., over a single hop (link), and do not have the capability to forward traffic on each other’s behalf. • Multi-Hop Network: A multi-hop network is one in which devices have the capability to forward traffic on each other’s behalf and can thus communicate along paths composed of multiple hops. Bruce Kraemer, Marvell

28. Configuring • Statically Configured Multi-Hop Network: A multi-hop network can be statically configured, such that each node’s forwarding decisions are dictated by configuration. • Dynamic and Self-Configuring Multi-Hop Network: A multi-hop network can be dynamic and self-configuring, such that network devices have the ability to discover (multi-hop) forwarding paths in the network and make their own forwarding decisions based on various pre-configured constraints and requirements, e.g., lowest delay or highest throughput. These types of networks are typically referred to as ad hoc or mesh networks, the difference between the two being that an ad hoc network is more likely to be disconnected from other networking infrastructure and to include mobile network devices, whereas a mesh network is typically part of the network infrastructure and is less likely to include mobile network devices. Some of the potential advantages of ad hoc and mesh networks are the ability of devices to optimize forwarding decisions based on propagation conditions and interference, automatic re-routing around failed links or devices, and ability to maintain multi-hop connectivity in a network with a dynamically changing topology, e.g., where one, multiple or all devices may be moving. Bruce Kraemer, Marvell

29. MESH Definition • Mesh Network: An ad hoc or mesh network is a dynamic self-configuring network composed of devices that can forward traffic on each other’s behalf, have the ability to discover (multi-hop) forwarding paths in the network and make their own forwarding decisions based on various pre-configured constraints and requirements, e.g., lowest delay or highest throughput. The difference between an ad hoc and a mesh network is that an ad hoc network is more likely to be disconnected from other networking infrastructure and to include mobile network devices, whereas a mesh network is typically part of the network infrastructure and is less likely to include mobile network devices. Some of the potential advantages of ad hoc and mesh networks are the ability of devices to optimize forwarding decisions based on propagation conditions and interference, automatic re-routing around failed links or devices, and ability to maintain multi-hop connectivity in a network with a dynamically changing topology, e.g., where one, multiple or all devices may be moving. Bruce Kraemer, Marvell

30. Comment #07 • Section 4.2.2.5 talks about Connection Management. The section needs to mention what aspects of “connection management” can be used to compare different wireless technologies. For example, we can evaluate the latency to join a network, available security mechanisms employed when joining a network, and overhead to join the network (number of control packets exchanged). Perhaps section titles such as “Network Participation Mechanisms” or “Joining the Network” are more descriptive of the content of this section. • Suggested text change: Agree in principle. Add sentence referring to rejoining after link drop. • Add the following text at the end of Section 4.2.2.5: It is important to evaluate the time it takes for a device to join a particular network, and the overhead required to do so, along with the overhead required to maintain membership in the network after the initial admission into the network. Also to be considered is the overhead associated with optimizing connectivity, e.g., in mesh-based topologies. Bruce Kraemer, Marvell

31. Comment 07a • Add the following text at the end of Section 4.2.2.5: It is important to evaluate the time it takes for a device to join a particular network, and the overhead required to do so, the time and overhead required to rejoin the network when a device becomes disconnected from the network, along with the overhead required to maintain membership in the network after the initial admission into the network. Also to be considered is the overhead associated with optimizing connectivity, e.g., in mesh-based topologies. Bruce Kraemer, Marvell

32. Comment #08 • Section 4.2.3.2 talks about Location Characterization. It seems like many of the techniques applicable to this section are not technology-specific but implementation-specific and as such can be incorporated across different wireless technologies even if they are not currently incorporated into the products of a specific wireless technology. It would be helpful to make the distinction between technology-specific properties and product-specific properties in the text. • Suggested text change: Agreed • Add the following text at the end of Section 4.2.3.2: It is important to distinguish between technology-specific location characterization mechanisms and those that are applicable across technologies or communication topologies, and can easily be added to products that may not currently support them. Bruce Kraemer, Marvell

33. Comment #09 • A category that is missing from Section 4 is one that characterizes the deployment complexity of each technology. I have some initial proposed text below but I would like to solicit the group’s input on how to characterize deployment complexity in a measurable way. • Suggested text change: Agree in principle. No volunteers yet identified to provide text. • Add the following text after Section 4.2.4.1: • 4.2.5 Group 22: Deployment Complexity • It is important to evaluate the complexity of installing, and maintaining a given wireless system, including ease of integration with other, possibly existing, networks, and augmenting the wireless network footprint over time. Bruce Kraemer, Marvell

34. Comment #10 • Agree in principle. Need someone to create text. • It might be helpful to have some tables and text summarizing the information in Section 5, and to move a lot of the discussions/derivations to an appendix. Otherwise, the message/conclusions/recommendations get lost in the text. Bruce Kraemer, Marvell

35. Comment #11 • Agree in principle. Need someone to create text. Review OpenSG use cases to verify current topics covered. • Section 4.2.1.2 (p. 24) talks about voice and video traffic over the smart grid. I think that we need more use cases motivating why we would want to have voice and video traffic over the smart grid network. The only video example given in the text is one of surveillance of affected outage areas. It would seem that voice and video might be of lower priority during outages, e.g., caused by disasters or weather-related events, since the network would require a high degree of availability for its regular functions. In addition, surveillance is generally part of the public safety infrastructure and there is spectrum allocated for such use so I am not convinced that we should be discussing this kind of application in the context of the smart grid. • Applications such as voice and video have requirements that even broadband network providers are struggling with (wireless and landline) and making them part of the smart grid infrastructure requires significant justification. Bruce Kraemer, Marvell

36. PAP#2 _ Report_r5 –Preface Para 2 • The decision to apply wireless technologies for any given set of applications is a local decision that must take into account several important elements including both technical and business considerations. Smart Grid applications requirements must be defined with enough specificity to quantitatively define communications traffic loads, levels of performance and quality of service. Applications requirements must be combined with as complete a set of management and security requirements for the life-cycle of the system. These requirements can then used to assess the suitability of various wireless technologies to meet the requirements in the particular applications environment. Bruce Kraemer, Marvell

37. Para 2 Recommended change • Reword to incorporate the idea that SG application requirements evolve over time, yielding to experience rather than remain locked in 1989 or 1999 or 2009 economics. • Smart Grid application requirements must be defined with enough specificity to quantitatively define communications traffic and levels of performance over the lifetime of the applications.  Applications requirements must be combined with as complete a set of management and security requirements for the life-cycle of the equipment.  The decisions to apply wireless for any given set of applications can then be based on expected performance and costs over the projected useful lifetimes of the spectrum and equipment.  Bruce Kraemer, Marvell

38. Incomplete text changes from August 25 Telecon Bruce Kraemer, Marvell

39. Peter Ecclesine comments – Aug 11 == Prepared definitions • Definition of Packet Radio should be removed. • Rate adaptation should be replaced by Link adaptation, including changing Modulation, Coding Scheme, smart antennas, hopping patterns, http://en.wikipedia.org/wiki/Link_adaptation • Link adaptation from Wikipedia, the free encyclopedia • Link adaptation, or adaptive coding and modulation (ACM), is a term used in wireless communications to denote the matching of the modulation, coding and other signal and protocol parameters to the conditions on the (e.g. thepathloss, the interference due to signals coming from other transmitters, the sensitivity of the receiver, the available transmitter power margin, etc.). • For example, EDGE uses a rate adaptation algorithm that adapts the modulation and coding scheme (MCS) according to the quality of the radio channel, and thus the bit rate and robustness of data transmission. The process of link adaptation is a dynamic one and the signal and protocol parameters change as the radio link conditions change -- for example in HSDPA in UMTS this can take place every 2 ms. • Adaptive modulation systems invariably require some channel state information at the transmitter. This could be acquired in time division duplex systems by assuming the channel from the transmitter to the receiver is approximately the same as the channel from the receiver to the transmitter. Alternatively, the channel knowledge can also be directly measured at the receiver, and fed back to the transmitter. Adaptive modulation systems improve rate of transmission, and/or bit error rates, by exploiting the channel state information that is present at the transmitter. Especially over fading channels which model wireless propagation environments, adaptive modulation systems exhibit great performance enhancements compared to systems that do not exploit channel knowledge at the transmitter. Bruce Kraemer, Marvell

40. Link adaptation - Continued from Wikipedia • An Example of Link Adaptation • In HSDPA link adaptation is performed by: • choice of modulation type -- the link can employ QPSK for noisy channels and 16QAM for clearer channels. The former is more robust and can tolerate higher levels of interference but has lower transmission bit rate. The latter has twice higher bit rate but is more prone to errors due to interference and noise hence it requires stronger FEC (forward error correction) coding which in turn means more redundant bits and lower information bit rate; choice of FEC -- the FEC code used has a rate of 1/3, but it can be varied effectively by bit puncturing and HARQ with incremental redundancy. When the radio link conditions are good more bits are punctured and the information bit rate is increased. In poor link conditions all redundant bits are transmitted and the information bit rate drops. In very bad link conditions retransmissions occur due to HARQ which ensure correct reception of the sent information but further slow down the bit rate. • Thus HSDPA adapts to achieve very high bit rates, of the order of 14 megabit/s, on clear channels using 16-QAM and close to 1/1 coding rate. On noisy channels HSDPA adapts to provide reliable communications using QPSK and 1/3 coding rate but the information bit rate drops to about 2.4 megabit/s. This adaptation is performed up to 500 times per second. Bruce Kraemer, Marvell

41. Peter Ecclesine comments – Aug 11 == Prepared definitions • == Definitions to refine or remove: • (unused) Generally Accepted Privacy Principles – include Web accessed groups like Truste and Better Business Bureau. (look at AT&T and Verizon Privacy Web pages) • http://www22.verizon.com/privacy/ • http://www.att.com/gen/privacy-policy?pid=2506 • How to use the references?? • Web Portal Bruce Kraemer, Marvell

42. Needs more development • Section 5.1.1 Indoor-indoor radio propagation models • There should be a 5.1.2 with indoor-indoor noise including basement/garage woodworking tools, sheetmetal shop, garage door opener, washer/dryer, hair-dryer, etc. Let there be man-made noise or our models work in a vacuum. Bruce Kraemer, Marvell

43. Peter Ecclesine comments – Aug 11 • == Prepared definitions • (Remove, unused) Last Gasp – all are proprietary, none scale • Discussion: This is a term used in utilities. There is industry text on the term,e.g: • http://http://ewh.ieee.org/conf/tdc/IEEE_-_Outage_Management_-_042308_FINAL.pdf Leave in – review text Bruce Kraemer, Marvell

44. Call for Contributions to Section 6 • Suggested Outline • Factors affecting performance, i.e. reliability, delay, throughput • Channel conditions such as distance, transmitted power, interference, propagation environment • Traffic load • Number of users • Seeking volunteers? Bruce Kraemer, Marvell

45. Section 6 – Default Suggestions • 6. Findings / Results • Does wireless technology X meet SG-Network requirements • Performance Metrics • Reliability • Latency • Scalability • meets throughput needs • handles the number of devices needed • range • interference immunity • By actor to actor / Link by link which is the best to use • How does its work in urban, sub-urban, rural • How well does it propagate (e.g. walls, basements, vaults, clutter, hills) • scalability over a quantity of end points • Equipment required to operate • Include processing time between actor to actor Bruce Kraemer, Marvell