Protocol Standardization for loT Vinton Cerf is one of the inventors of TCP/IP (transmission control protocol/Internet protocol) around 1978 - TCP/IP became the required protocol of ARPANET (Advanced Research Projects Agency Network) in 1983 + It also allowed ARPANET to expand into the Internet, facilitating features like remote login via Telnet, and later, the WWW.Protocol Standardization for loT Tim Berners-Lee was the man leading the development of WWW, defining of HTML, HTTP, and URL used to create web pages - For many people who are not tech savvy, the Internet and Web are one and the same * Many people believe Tim Berners-Lee is the father of the Internet due to the success of the World Wide Web * As the Internet existed long before the World Wide Web, Tim» Berners-Lee is only “old enough” to be the father of the Web.Difference between Internet and World Wide Web * Internet is the massive interconnection of the computer networks around the world eee RM) aN ile] Meola acoso elm M1 t iain enol gd more computers * World Wide Web is the general name for accessing the Internet via HTTP, thus www.anything.something * It is just one of the connection protocols that is available in the Internet, and not,the only one.Difference between Internet and World Wide We * Internet is large container, and web is a part within the container cee’ ee aWeb of Things vs. Internet of Things * The key to make the loT takes off is the WoT — the killer applications’ platform or base of the loT - WoT is the next logical step in this loT evolution toward global networks of sensors and actuators, enabling new applications and providing new opportunities * WoT explores the layer on top of connectivity with things and addresses issués such as fast prototyping, data integration, and interaction with objects.Web of Things vs. Internet of Things * WoT is a version where things become seamlessly integrated into the web - There are also many other WoT applications around the world. Some of them are, SCL) Deen cay Sanur 7 CRN Cur MN rum maces CeesTwo Pillars of the Web + Application Server (AS) became the foundation that helped build widely SECM ee RTT aecliene - AS acts as set of components accessible to software developer through an API defined by the middleware itself ERR oes Pied icle Rolin Lt-e- eal ite ca ae User Interface Client Connectivity SS Connectivity Application Application Log Server AOS) Database Connectivity ——— RDBMS Database Data ServerTwo Pillars * Protocols HTML/HTTP/URL and the software will continue to be TaN TT ETS aeLI Eve eul fan) lela co (Mm l Cella od applications. Webo Things | Waa Internet of Mgkimedi Webi Taternet of Documents —]M2M and WSN Protocols * Most M2M applications are developed today in a highly customized fashion + High-level M2M architecture from M2M Standardization Task Force (MSTF) does include fixed & other non cellular wireless networks * Means it’s generic, holistic loT architecture even though it is M2M architecture + M2M and loT sometimes are used interchangeably in the United Ry] K oeM2M and WSN Protocols Other M2M standards activities include: Data transport protocol standards - M2MXML, JavaScript Object Notation (JSON), BITXML, WMP, MDMP are ROMERO tna PMR Urey crear ur cunt tac NA eRe Ciel a Peony Neetu Mien eetacu Neo ea eta eke tcl Dene CnC use et tah ct Veec Open REST-based API for M2M applications.China Mobile’s WMMP StandardM2M and WSN Protocols * One of the benefits of using sensor data is that data typically can be reused many times thereby reducing cost & maximizing benefit SASS S ferrari Slam melee 4 Plume Modeling Insurance Risk Analysis Ski Area Location Decisions And so on...M2M and WSN Protocols * Hundreds of sensor manufacturers build sensors for specific fo ster) - Often using their own language or encodings, different metadata, and so forth Standard data representation (together with WSN middleware) is the key to materialize data integration and increase interoperability * There are a number of standardization bodies in the field of WSNs. Pee! eeeM2M and WSN Protocols The IEEE focuses on the physical and MAC layers; the IETF works on layers 3 and above + IEEE 1451 - Set of smart transducer interface standards developed by Deir eM tol o eee na alee MK ecole Neo el Technology Technical Committee Dee eee uM anette Cur ecciuLa ie interfaces for connecting transducers (sensors or actuators) to microprocessors instrumentation systems, and control/field networks.M2M and WSN Protocols * One of the key elements of these standards is the definition of transducer electronic data sheets (TEDS) for each transducer - The TEDS is a memory device attached to the transducer, which stores transducer identification, calibration, correction data, and Tricot eect Mace) e Lael * Goal of the IEEE 1451 family of standards is to allow the access of transducer data through a common set of interfaces.Cee Pena cans Sea aed See eee eed ee ee ea eed Ce ene teeny ns = ny ry Se eee eee aa eee ey es etn SY Ce ee Se os Poe Poe eeM2M and WSN Protocols * Cross-network (e.g., between Bluetooth and ZigBee) standards are not popular in WSN community compared to other systems - It make most WSN systems incapable of direct communication with each other * Contents on WSN discussed are more devices or network focused * OGC (Open Geospatial Consortium) and W3C has been doing research and standardization work following a data-focused approach.M2M and WSN Protocols EMSS Week So NSEC Sirah ole untrcithtstecaceles 1c] based on OGC SWE (Sensor Web Enablement) emo NMI -asC muesli eye allele ol mel cele Uel-re le) OL CLOR) a Working Group Be Secu mean eRe Rear egy Or ee cae eR recess eee saad * Observations & Measurements (O&M)—models and schema for packaging observation Rote * Transducer Markup Language (TML)—models and schema for multiplexed data from Re CLES o xeGSCADA and RFID Protocols * Supervisory Control And Data Acquisition * One of loT pillars to represent whole industrial automation arena * IEEE created standard specification called Std C37.1™, for SCADA & automation systems in 2007 * In recent years, network-based industrial automation has greatly Vo) Ne) * With the use of intelligent electronic devices (IEDs), or loT devices i in our terms, in substations and power stations.SCADA and RFID Protocols IEEE Std. C37.1 rer\B)AY ArchitectureSCADA and RFID Protocols * The processing is now distributed + Functions that used to be done at control center can now be done by IED i.e. M2M between devices * Due to restructuring of electric industry, traditional vertically integrated electric utilities are replaced by many entities such as Pamela ee crue akeou cing + TRANSCO (Transmission Company), See eoN (Sur Mune e Pee eN tee so ane co aeSCADA and RFID Protocols * OPC stands for OLE (Object Linking and Embedding) for Process Control - Original name for a standard specification developed in 1996 by an industrial automation industry task force * The standard specifies the communication of real-time plant data between control devices from different manufacturers * OPC is managed by the OPC Foundation with more than 220 members worldwide. bSCADA and RFID Protocols Before OPC After OPC Application Applic ¥ ation Server A Server| B Server c Application x OPC Interface Application Y OPC Interface OPC Server A OPC Server B OPC Server CcSCADA and RFID Protocols * OPC originated from DDE (dynamic data exchange) technologies based on DOS for PCs UML Min) ocd Ulos Col RoLA AU Lale Cone ROM A eS) ¢Muat-ro LMU Lae (ola) toto MET ire meols elim el lacel aii) * Providing the ability for a PC to run multiple applications simultaneously and a standard mechanism for those applications PORE n Cee Raa eae 7 ee eeSCADA and RFID Protocols * Wonderware’s InTouch™ SCADA software had the greatest impact for the transition from DDE to OPC - It introduced a means of networking DDE traffic (NetDDE™, which was later taken up by Microsoft) * OLE (based on COM, common object model) and OCX (now ActiveX based on .NET) were launched in 1992 * OPC was designed to provide a common bridge for Windows-based software applications and process control hardware.SCADA and RFID Protocols * OPC has achieved great success in many application areas, most of them closely related to or part of loT applications - For example, standard OPC DA (data access) is based on Microsoft’s COM and DCOM technology and is consequently restricted to the Windows operating system * In addition, DCOM communication is easily blocked by firewalls that prevent OPC clients from accessing data over a wide-aréa network and the World Wide Web.SCADA and RFID Protocols RFID protocols and data formats are relatively well defined, mostly by EPCglobal - Unified compared with protocols and formats of the other three pillars of loT * Common RFID protocols are PML, Object Naming Service [ONS], Edgeware, EPC Information Service [EPCIS], Application Level Event CNS icon eetSCADA and RFID Protocols * Smart cards with contactless interfaces are becoming increasingly popular for payment and ticketing applications such as mass transit and stadiums * Visa and MasterCard have agreed to an easy-to-implement version deployed in the United States * Smart cards are also being introduced in personal identification & entitlement schemes at regional, national, anid international levels. ee! coe esSCADA and RFID Protocols * Citizen cards, drivers’ licenses, and patient card schemes Standard for contactless smart card communications is ISO/IEC EeLe} + It defines two types of contactless cards (A and B) and allows for communications at distances up to 10 cm * An alternative standard for contactless smart cards is ISO/IEC 15693, which allows communications at distances up to 50 cm.SCADA and RFID Protocols Host Controller Interface (08 and Switch Mode Module ISO/IEC RE ISO/IEC T 14443/15693 dels R ° swe || 1s0 7816 stave | Slave RFECMA 340 [Master] ] Master + ver || Driver Reade river river Smart Card Driver] |Ds ard Es ad Ds D Standards vice wp Secure MasterModbus Protocol * Many protocols have been designed for the needs of industrial automation and metering - These protocols generally use simple query/response models and allow for extremely simple implementations * Many protocols derived from the frame formats defined by IEC 870-5 such as T101 (IEC 870-5-101), DNP 3.0, M-Bus, Profibus, etc. * Other protocols developed independently into de-facto standards, such as ModBus.Modbus Protocol * Very common protocol used in many industrial and HVAC (heating, ventilating, and air conditioning) installations + Trademark of Modicon inc. (Schneider Electric group) * An application layer messaging protocol that provides client/server communication between devices connected on different types of buses or networks Because of its simplicity, ModBus has become one of the de-facto Se E camer eae message-based communications since 1979.* ModBus devices communicate Modbus Protocol * ModBus typically runs ontop of penis RS 232, RS 442 point to point or RS 485 point to multipoint links —___ * ModBus/TCP specification, gee Reta) published in 1999 defines an IP- Eoxchek byt) Response based link layer for ModBus frames using a master-slave model.ModBus Message Framing + ModBus Addresses: ModBus messages begin by target 8-bit address that can take any decimal value between 1 and 247 Ois used for broadcasts Address field of message frame contains 2 characters in ASCII mode Each query contains address of a specific slave When it responds, slave includes its own address in message.ModBus Message Framing + ModBus Functions: The function code field contains two characters in ASCII mode, ETN R Mice MOM aLele (3 Can take any decimal value between 1 and 255 Selected based on the device application profile For example, 0x02: Read Input Status, 0x11: Report Slave ID.ModBus Message Framing + ModBus Data Field: * Provides application level information, as required by the ModBus function * When a given ModBus function requires variable size data, the data field begins with the “byte count” of the data.ModBus/TCP Provides TCP/IP access to the ModBus functionality Each ModBus Request/response is sent over a TCP connection Deen Lo ecuiencucat ev CmchYaeaer) TCP connection may reused for several query/response exchange Byte content of the ModBus request and response frames is simply transported over the TCP connection.ZigBee IEEE 802.15.4-based specification for a suite of high-level communication protocols Used to create personal area networks with small, low-power digital radios ZigBee based applications * Home Automation . Caer eater Reo] cas) Semel a lie el mol ale lite iy . « ZigBee versions Pars PAIL} Sera Pr PartZigBee Architecture oer Eevee ees espren Divided into three sections: IEEE 802.15.4 which consists of MAC and eee ca eee ey network layer, the ZigBee device object (ZDO), the application sublayer, and Pee mCUeT cued EWM Cea selec oe ELC aed pace eee Una ea Erato ikem ee rae enn ice ae aaZigBee Architecture ZigBee and 802.15.4 ZigBee sits on top of 802.15.4 physical (PHY) and medium-access control (ON REN ZigBee uses only the 2003 version of 802.15.4 ONeill waa oa Re A ae Cl aoe SL EPO) 0) lela Role -it/ae bore me (oleae eM oHaLLal UCoLa onesie frequencies 2006 version adds improved data-transfer rates for 868 and 900 MHz 802.15.4 offers 16 channels on the 2.4 GHz, numbered 11 to 26.ZigBee Architecture * ZigBee Protocol Layers rate Mee aC ee RRs ela ea La adding the missing mesh routing protocol to 802.15.4 It also encapsulates the network formation primitives of the 802.15.4 MAC layer (network forming and joining) The rest of the ZigBee protocol layers do not follow the OSI model,ZigBee Architecture Application Support Sublayer (APS) Layer: Multiplexing/demultiplexing: It forwards the network layer messages to the appropriate application objects, according to their endpoint ID (each application is allocated an endpoint ID) Binding: Maintains local binding table i.e. records remote nodes & Pa SMS EN ace ROes aur oun eat Tg 64-bit IEEE to 16-bit ZigBee network node address mapping Management of end to end acknowledgementsZigBee Architecture Application Support Sublayer (APS) Layer: Multiplexing/demultiplexing: It forwards the network layer messages to the appropriate application objects, according to their endpoint ID (each application is allocated an endpoint ID) CTT aN Ete re Tat uy eel aM ede tC ee Ere ea eMac kedc es) Ciuc une Rur Soi Meal aa oe ed ya ened dale eG eseenuel yaar Management of end to end acknowledgements Fragmentation, Group addressing, Security.ZigBee Architecture ZigBee Device Object (ZDO) Layer: Specific application running on endpoint 0 Designed to manage the state of the ZigBee node ZDO application implements the interfaces defined by ZigBee device profile (ZDP) These primitives encapsulate the 802.15.4 network formation primitives of the ZigBee network layer as well as additional primitives supporting the concept of binding.ZigBee Architecture - ZigBee Cluster Library (ZCL): Late addition to ZigBee, specified in a separate document eee e RM Cee ole laa eee Te Ba ELLs Pan gece talcceie teri es Nees Cc ekg ud cet R Pac OM Ceca Ra POM Creu Mellman relate okt network interface for group formation and management.ZigBee Architecture * Application Framework Layer: * Provides the API environment of ZigBee application developers Sisto feel Cen al LL CTL * Each application is assigned an Endpoint ID - ZigBee Node Types * ZigBee End-Device (ZED) SRS Rees ea RE eRe et ACen oo Se ea so M ea ho nce cc)ZigBee Architecture - ZigBee Node Types Dee aececa ca 4 SRS ee ees oe ne OS Re ed a) Seg cn ee ca Ce ue ed Dead + ZigBee Coordinator (ZC) See CEES Cem ean iat) See eee Oe ORs See EDC eg MEL te ‘Also contains the trust center, which is responsible for admission of new nodes on the network and CUS Cue6LOWPAN IP 4 Igo ole) 9 ]MATT (Secure) Protocol BU leres-t{ Olay C(t ala Lela - Lightweight publish/subscribe messaging protocol designed for M2M telemetry in low bandwidth environments * Designed by Andy Stanford-Clark (IBM) and Arlen Nipper in 1999 for connecting Oil Pipeline telemetry systems over satellite * Although it started as a proprietary protocol it was released Royalty free in 2010 and became an OASIS standard in 2014. ee ee eeeMATT (Secure) Protocol Original MQTT, designed in 1999, has been in use for many years and is designed for TCP/IP networks = (anol caren neentrontes As of release 1.6 the mosquitto broker supports MQTT SMUT [iol OOM Ere a F marrys. | Paho Python client v 1.5 now supports for v5 MaqTT v5 MQTT-SN which was specified in around 2013, and designed to work over UDP, ZigBee & other transportsMATT (Secure) Protocol lola mel Tc Bere elmo ne nase eee oR oe ea Co no need to assign addresses to clients like most messaging systems do For MQTT v3.1.1, there is client software available in almost all programming languages and for the main operating systems Linux, Windows, Mac from the Eclipse erage NOUN een ed Sea ON eee CIC Sar ee oe oe eee + There are free self hosted brokers, the most popular being Mosquitto and commercial ones like HiveMQ Pe URS CA CRU CUE SUL UC)eeeee e eeee ek eee o eee6LOWPAN Protocol * |IPv6 over Low power Wireless Personal Area Networks * Internet Engineering Task Force (IETF) GLoWPAN Working Group was formed in 2004 * To design an adaptation layer for IPv6 when running over 802.15.4 low-power and lossy networks. * The work included a detailed review of requirements, which were released in 2007 (RFC 4919). :6LOWPAN Protocol * Not restricted to radio links only, it can be extended to run over Celta) - 802.15.4 and most low-power transmission technologies must rely on mesh networking to create large networks * Two techniques may be used: Caan Lae * Route over6LOWPAN Protocol * Link layer (layer 2) supporting IP network takes care of mesh networking and packet forwarding * IP layer sees a large subnet, Example: GeoNET * IP level (layer 3) mesh routing * Used if multiple underlying networking technologies need to be used simultaneously or when the underlying networking technology supports only point to point or local broadcast link layer communication capabilities