DOCSLIB.ORG

VULA L2 Transparens POI 0-3X

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
VULA L2 Transparens POI 0-3X VULA Generel L2 Transparens & POI 0-3 Møde i WG for VULA videreudvikling 23. maj 2013 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 1 Agenda • Data Transmission OSI Lag 1 – 3 • Lag 2 Transparens • Ethernet Rammer • MTU & VPN tuneller • Trafiktyper (Unicast / Multicast) • Link Protokoller • Cisco Lag 2 protokoller • IPv4 / IPv6 på Lag 2 • IPv4 / IPv6 Multicast på Lag 2 • QinQ • TDC Aggregerings net & Udfordringer • Net Ressourcer • Mac adresser • Vlans • L2 Aggregering • OAM • POI 1 – 3 Contended • ISAM MPLS • Nyt Lag 3 Aggregerings net • POI 0 Uncontended • Kapacitet • ISAM L2 transparens • Lag 2 / Lag 3 Kunde terminerings udstyr 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 L2 Tranparens POI 0-3 2 Data Transmission OSI Lag 1 - 3 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 L2 Tranparens POI 0-3 3 OSI LAG 1-2-3 Fysisk (Lag 1) • Beskriver Bitkodning, kabel-typer og stik. • Koder binære 0´er og 1´er fra DataLink laget til spændinger • Afkoder spændinger til binære 0´er og 1´er, sendes til DataLink OSI 7 LAGS MODEL • Signaler kan være spændinger, lys eller radiobølger. • Ethernet(ex. 10Base-5,1000Base-ZX), RS232, ATM etc. • Ingen adressering Data Link (Lag 2) • Koder og afkoder data pakker til bits. • Pålidelig data overførsel, og fejl håndtering (CRC/FCS). • Flow kontrol, bit, byte, og ramme synkronisering. • Yderligere opdelt i 2 lag: Media Access Control (MAC) og Logical Link Control (LLC) • MAC laget kontrollerer hvordan man får fat I data, og tilladelse til at sende det (CSMA/CD, Ethernet 802.3, CSMA/CA,WIFI 802.11). • LLC: ramme/pakke synkronisering, flow kontrol og fejl check (LLC 802.2, HDLC, SDLC). • L2 Adressering, Skiftes ud hop-by-hop Netværk (Lag 3) • Entydig adressestruktur, der bevares ende-til-ende. • Routning og sammenbinding af netværk • Fejl håndtering, overbelastning kontrol, pakke fragmentering. • (IPv4, IPv6, IPX) Routnings protokoller IGP(OSPF, ISIS, EIGRP), EGP(BGP) 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 L2 Tranparens POI 0-3 4 Lag 2 Transparens • Ethernet Rammer • MTU & VPN tuneller • Trafiktyper (Unicast / Multicast) • Link Protokoller • Cisco Lag 2 Protokoller • IPv4 / IPv6 på Lag 2 • IPv4 / IPv6 Multicast på Lag 2 • OAM 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 L2 Tranparens POI 0-3 5 Ethernet Ramme Struktur Ethernet Ramme Struktur Ethernet 802.3 Ramme Length < 0x600 (1536) Ethernet 802.3 SNAP Ramme Type/Length < 0x600 (1536) DSAP=0xAA SSAP=0xAA Ethernet II Ramme Type/Length > 0x600 Type=next header (0x0800=ip, 0x8847=mpls-uni) etc.) Ethernet II Ramme Type=0x8100 (.1Q) Next Type=0x8100 (QinQ) Next type=next header IPSEC (VPN) Indkapslet Ramme Hvis IP payload stadig skal være 1500 bliver det til store Ethernet rammer. Dette stiller krav til Ethernet MTU størrelse, hvor Baby Giants (> 1500 < 9K)/ Jumbo Frames (9K) er påkrævet 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 L2 Tranparens POI 0-3 6 MTU & VPN tuneller 1500 byte packet becomes 1552 bytes: 20 bytes IPsec header (tunnel mode) 4 bytes SPI (ESP header) 4 bytes Sequence (ESP Header) 8 byte IV (IOS ESP-DES/3DES) 2 byte pad (ESP-DES/3DES 64 bit) 1 byte Pad length (ESP Trailer) 1 byte Next Header (ESP Trailer) 12 bytes ESP MD5 96 digest IPsec overhead IPsec Transform Set IPsec Overhead esp-aes-(256 or 192 or 128) esp-sha-hmac or md5 73 esp-aes (256 or 192 or 128) 61 esp-3des, esp-des 45 esp-(des or 3des) esp-sha-hmac or md5 57 esp-null esp-sha-hmac or md5 45 ah-sha-hmac or md5 44 L3 IP MTU SIZE 1573 L2 Frame: 1587 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 L2 Tranparens POI 0-3 7 MTU Både L2 og L3 Aggregering, og i dag • ISAM termineres i 4500 Non-Blocking Gigabit port (Jumbo Frames 9K) • Der tages forbehold for enkelte lokationer, som er forbundet via radiokæde systemer og lignende • AO POI Kan bestilles med stor MTU, NB-Gigabit (Jumbo Frames 9K) • ISAM SHUB NB 24 GB Switch med Jumbo Frame support (9K) • ISAM 4.2 NALT (ADSL LT-Kort) support for MTU=1600 (L2 MTU/Frame Size) • ISAM 4.2 NVLT (VDSL LT-Kort) support for MTU=1600 (L2 MTU/Frame Size) 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 L2 Tranparens POI 0-3 8 IEEE 802 MAC Adresse • 48 Bit, 6 Bytes • Første 3 Bytes = Vendor Code • Sidste 3 Bytes = Løbenummer • Canonical: Per byte swapping. Mindst betydende bit først (Ethernet 802.3) • Unicast / Multicast Trafiktyper der benyttes på Lag 2 • Ethernet Unicast (L2, IPv4, IPv6) • Lag 2 Multicast (IEEE, CISCO kendte Multicast adresser) • Lag 3 (IPv4) Multicast (Bliver til L2 Multicast) • Lag 3 (IPv6) Multicast (Bliver til L2 Multicast) 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 L2 Tranparens POI 0-3 9 Udsnit af Velkendte Ethernet Multicast Adresser IEEE Reserverede Kontrol MAC Multicastadresser Protocol MAC Address Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), 01:80:C2:00:00:00 and Multiple Spanning Tree Protocol (MSTP) Kan være svære at gøre transparente, da Link Aggregation Control Protocol (LACP) 01:80:C2:00:00:02 TDC selv gør brug af Ethernet OAM Protocol IEEE 802.3ah (0x8809) 01:80:C2:00:00:02 disse. Kan kræve yderligere IEEE Std 802.1X PAE address 01:80:C2:00:00:03 funktionalitet i udstyr Ethernet local management interface (E-LMI) 01:80:C2:00:00:07 Spanning Tree Protocol (provider bridges) IEEE 802.1AD 01:80:C2:00:00:08 Link Layer Discovery Protocol (LLDP) 01:80:C2:00:00:0E ISIS-all-level-1-IS's 01:80:C2:00:00:14 ISIS-all-level-2-IS's 01:80:C2:00:00:15 Multiple MAC Registration Protocol (MMRP) 01:80:C2:00:00:20 MVRP VLAN Registration Protocol (MVRP) 01:80C2:00:00:21 Cisco Reserverede Kontrol MAC Multicastadresser Protocol MAC Address Inter Switch Link (ISL) 01:00:0C:00:00:00 Cisco Discovery Protocol (CDP) 01:00:0C:CC:CC:CC Unidirectional Link Detection (UDLD) 01:00:0C:CC:CC:CC VLAN Trunking Protocol (VTP) 01:00:0C:CC:CC:CC Dynamic Trunk Protocol (DTP) 01:00:0C:CC:CC:CC Port Aggregation Protocol (PAgP) 01:00:0C:CC:CC:CC Per VLAN Spanning Tree Protocol (PVST+) 01:00:0C:CC:CC:CD Cisco Andre Gamle (ex CGMP etc.) 01:00:0C:XX:XX:XX 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 L2 Tranparens POI 0-3 10 IPv4 / IPv6 Unicast på Lag 2 IPv4 til Mac adresse (ARP) IPv6 til Mac adresse (ND) • Broadcast sendes til alt og alle • ICMPv6 Multicast sendes kun til IPv6 enheder • ARP er en protokol mellem Lag 2 og Lag 3 • ND foregår på rent IPv6 Multicast • Herefter sendes pakkerne via Unicast trafik • IPv6 er altså afhængig af multicast trafik • Herefter sendes pakkerne via Unicast trafik 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 L2 Tranparens POI 0-3 11 IPv4 Multicast (Class D 1110) 224.0.0.0/4 ends at 238.255.255.255 224.0.0.0 – 224.0.0.255 /24 (Local Network Control Block) 224.0.0.0 Base address (reserved) The All Hosts multicast group addresses all hosts on the 224.0.0.1 same network segment. The routing multicast group addresses all routers on the 224.0.0.2 same network segment. 224.0.0.4 This address is used to address multicast routers. The (OSPF) All OSPF Routers address is used to send Hello 224.0.0.5 packets to all OSPF routers on a network segment. The OSPF All Designated Routers ""(DR)"" address is used to 224.0.0.6 send OSPF routing information to designated routers on a network segment. The (RIP) version 2 group address is used to send routing 224.0.0.9 information to all RIP2-aware routers on a network segment. The (EIGRP) group address is used to send routing 224.0.0.10 information to all EIGRP routers on a network segment. 224.0.0.19 - 21 IS-IS over IP 224.0.0.22 Internet Group Management Protocol (IGMP) Version 3 233.0.0.0 - 233.251.255.255 (16515072) GLOP Block Autonomous system number mapped into MC addresses 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 L2 Tranparens POI 0-3 12 IPv4 Multicast (Class D 1110) på Lag 2 IPv4 MC mappes til Lag 2 MAC Multicast 01:00:5E:XX:XX:XX Benyttes til IPv4 MC på Lag 2 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 L2 Tranparens POI 0-3 13 IPv6 Multicast ICMPv6, ND, SLAAC, MLD IPv6 Multicast adresse rum ff00::/16-ff0f::/16 Reserved ffxe::/16 Global Scope, Eligible to be routed over the public internet. Velkendte IPv6 Multicast adresser ff02::1 All nodes on the local network segment ff02::2 All routers on the local network segment ff02::5 OSPFv3 All SPF routers ff02::6 OSPFv3 All DR routers ff02::8 IS-IS for IPv6 routers ff02::9 RIP routers ff02::a EIGRP routers ff02::d PIM routers ff02::16 MLDv2 reports (defined in RFC 3810) All DHCP servers and relay agents on the local network ff02::1:2 segment (defined in RFC 3315) 23. maj 2013 Møde i WG for VULA videreudvikling 23. maj 2013 L2 Tranparens POI 0-3 14 IPv6 Multicast på Lag 2 IPv6 MC Mapning til Lag 2 Mac Multicast • 33:33:XX:XX:XX:XX Benyttes til IPv4 MC på Lag 2 23.
Load more

Recommended publications
  • Medianet 2015
    konferencia szemle HTE MediaNet 2015 Diákszekció 2015. október konferencia szemle TARTALOM H T E M E DIAN et 2 0 1 5 KO N F E R en CIA | DIÁKSZEKCIÓ EREDMÉNYEK A TÖBBUTAS HÁLÓZATI KOMMUNIKÁCIÓS TECHNOLÓGIÁK TERÜLETÉN 2 Fejes Ferenc, Katona Róbert, Püsök Levente PARAMÉTERBECSLÉS 802.11AD RENDSZEREKBEN 8 Csuka Barna és Kollár Zsolt MODERN TECHNOLÓGIÁKON ALAPULÓ OTTHONI FELÜGYELő RENDSZER 15 Kalmár György, Balázs Péter A GOOGLE ÚJ, KÍSÉRLETI QUIC PROTOKOLLJÁNAK TELJESÍTMÉNYELEMZÉSe 21 Krämer Zsolt, Megyesi Péter, Molnár Sándor INTEGRÁLT TÖMEGFELÜGYELETI RENDSZER OKOS VÁROSOKBAN 29 Nagy Attila Mátyás KÉPOSZTÁLYOZÁS EMBERI ÉS GÉPI TANULÁS ESETÉN 36 Papp Dávid H T E M EDIANet2 0 1 5 KONFERENCIA SZEMLE 1 H T E ME DIAN et 2 0 1 5 KONF E RenC I A DIÁKSZEKCIÓ EREDMÉNYEK A TÖBBUTAS HÁLÓZATI KOmmUNIKÁCIÓS teChnOLÓGIÁK teRÜLetÉN 1 2 használva (vezeték nélküli IEEE 802.11 illetve a vezetékes (Medium Access Control) van jelen, elrejtve az alatta lévo˝ EredményekEredmények a a többutastöbbutas hálózati hálózati kommunikációs kommunikációs IEEE 802.3 Ethernet valamelyik verziója). További lehetoség˝ heterogén hálózatot. Egyetlen EUI-48 MAC címet használ, egy HomePlug [6] kompatibilis (IEEE 1901 Broadband Pow- az erre érkezo˝ és errol˝ elküldött kereteket az AL-ben helyet erline Standard szabványt [7] támogató) eszköz beszerzése, foglaló továbbításért felelos˝ entitás (forwarding entity) képezi technológiáktechnológiák területén területén ezzel már a ház villanyáram hálózatát is használhatjuk adat- le az alárendelt interfészekre. A protokoll képes felderíteni
    [Show full text]
  • Vision of the Smart Home, the Services Concepts That Will Emerge and the Capabilities Needed to Support These Services on a Commercially Viable Basis
    Vision of Smart Home The Role of Mobile in the Home of the Future Contents Foreword Foreword Over the past decade, consumers the These services address consumers desire to manage their home 1 Executive Summary 1 world over have rapidly embraced mobile environment while becoming greener through lower energy telecommunications; connectivity has consumption and greater awareness of their CO2 footprint. The smart 2 Introduction 3 home concept, while it is still in its infancy, is set to become one of the allowed them to stay more and more in 3 Smart Home Vision 5 most significant consumer lifestyle developments of this decade. touch with their friends and colleagues. Smart Home Services 6 The smart home market is forecast to exceed $44bn in five years’ Stages in the Evolution of Smart Home Services 9 Now, the addition of connectivity to home time, bringing with it new opportunities for mobile network 4 Smart Home Landscape 13 appliances and the arrival of new online operators and the rest of the mobile ecosystem. The ubiquity of Supplier Ecosystem 13 energy management tools are creating mobile networks makes them indispensable for connecting smart home devices and Technology and Interoperability Landscape 17 the right environment for a new market in home energy management gateways, just as mobile phones are emerging as the main interface for home energy management applications. Smart Home - Growth Prospects in Vertical Segments 20 smart home services. 5 Smart Home Services and Requirements 25 We recognise, however, that the conversion of a home to a “smart” ecosystem is not going to happen without collaboration and cross-industry effort.
    [Show full text]
  • January 2019 Defining Iot…
    IoT: What and Why? January 2019 Defining IoT… The Internet of Things, IoT… Even technology researchers and commentators cannot agree on what it is. The most consistent is Gartner’s definition below. The Internet of Things (IoT) is the network of physical objects that contain embedded technology to communicate and sense or interact with their internal states or the external environment. Gartner. Defining IoT… Other definitions: Thing: An object of our everyday life placed in our everyday environment. A thing can be a car, fridge but can also be abstracted to a complete house or city depending on the use case. Device: A sensor, actuator or tag. Usually the device is part of a thing. The thing processes the devices’ context information and communicates selected information to other things. Furthermore, the thing can pass actions to actuators. What is IoT and Why are we doing this? The ‘What’ is the definitions and technologies. The ‘Why’ is the value and benefits. What is IoT? Technologies enabling connection to traditionally unconnected devices: a) Receiving information from the devices b) Where possible, controlling the device What is IoT and Why are we doing this? Examples of IoT devices that receive information, and respond to controls: • Drinking Water dispensers; • Lighting based on telemetrics; • Heating systems; • Conveyer belt systems; • Driverless vehicles; • Advertising boards. What is IoT and Why are we doing this? Why are we doing this? IoT technology means we can now receive information about things that traditionally was impossible or impractical to achieve. Therefore, the value and benefits are derived from the ‘Information of Things’.
    [Show full text]
  • Deliverable 1.4 SODALES Simulations
    Ref. Ares(2015)10335 - 05/01/2015 Deliverable D1.4 Project SODALES Doc Simulations Date 29/12/2014 Grant Agreement No.: 318600 SODALES SOftware-Defined Access using Low-Energy Subsystems Funding Scheme: Small or medium-scale focused research project STREP - CP-FP- INFSO Activity: ICT-8-1.1 - Future Networks D1.4 Simulations and physical layer validations Due date of the Deliverable: Month 24 Actual submission date: 29th December 2014 Start date of project: November 1st 2012 Duration: 36 months Project Manager: Carlos Bock | i2CAT Version: 1.0 Author List: Carlos Bock (i2CAT), Jordi Ferrer Riera (i2CAT), Eduard Escalona (i2CAT), Michael C. Parker (UEssex) Project co-funded by the European Commission in the 7th Framework Programme (2007-2013) Dissemination Level PU Public PP Restricted to other programme participants (including the Commission Services) RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services) Page 1 of 68 Deliverable D1.4 Project SODALES Doc Simulations Date 29/12/2014 This page is intentionally left blank. Page 2 of 68 Deliverable D1.4 Project SODALES Doc Simulations Date 29/12/2014 Abstract Deliverable 1.4 aims to demonstrate the benefits of deploying the SODALES convergent access infrastructure combining fixed and mobile access, by means of traffic studies and simulations. The objective of the work is to validate the SODALES architecture and to achieve a solid solution that supports high speed connectivity services in a robust manner, carefully analysing the requirements of present and future transmission services and studying the trends and behaviours of end users.
    [Show full text]
  • Closing Plenary July 2020
    Closing Plenary November 2020 Glenn Parsons – IEEE 802.1 WG Chair [email protected] 1 802.1 WG plenary agenda Monday, November 2nd opening Tuesday, November 10th closing • Copyright Policy • Copyright Policy • Call for Patents • Call for Patents • Participant behavior • Participant behavior • Administrative • Membership status • Membership status • Future Meetings • Future Meetings • Sanity check – current projects • 802 EC report • TG reports • Sanity check – current projects • Outgoing Liaisons • TG agendas • Motions for EC • Motions for 802.1 • Any other business 2 2 INSTRUCTIONS FOR CHAIRS OF STANDARDS DEVELOPMENT ACTIVITIES At the beginning of each standards development meeting the chair or a designee is to: .Show the following slides (or provide them beforehand) .Advise the standards development group participants that: .IEEE SA’s copyright policy is described in Clause 7 of the IEEE SA Standards Board Bylaws and Clause 6.1 of the IEEE SA Standards Board Operations Manual; .Any material submitted during standards development, whether verbal, recorded, or in written form, is a Contribution and shall comply with the IEEE SA Copyright Policy; .Instruct the Secretary to record in the minutes of the relevant meeting: .That the foregoing information was provided and that the copyright slides were shown (or provided beforehand). .Ask participants to register attendance in IMAT: https://imat.ieee.org 3 IEEE SA COPYRIGHT POLICY By participating in this activity, you agree to comply with the IEEE Code of Ethics, all applicable laws, and all IEEE policies and procedures including, but not limited to, the IEEE SA Copyright Policy. .Previously Published material (copyright assertion indicated) shall not be presented/submitted to the Working Group nor incorporated into a Working Group draft unless permission is granted.
    [Show full text]
  • Maxlinear Corporate Update
    ENVISIONING • EMPOWERING • EXCELLING G.HN STANDARDIZATION: PRESENT AND FUTURE ISPLC - April 2019 Marcos Martínez / Salvador Iranzo MaxLinear Confidential & Proprietary AGENDA • G.hn present • G.hn history: Main milestones • G.hn Recommendation ecosystem • G.hn Reference model • G.hn PHY Layer • G.hn MAC Layer • G.hn management • G.hn future: G.hn2 • New fields of application & ecosystem • New features • Ghn2 vs G.hn 2 G.HN PRESENT ENVISIONING • EMPOWERING • EXCELLING 3 G.HN RECOMMENDATION ECOSYSTEM ITU-T Application Recommendations Core Recommendations Coexistence Recommendations G.9978 (Secure admission) G.9961 (DLL) G.9977 (DSL Coexistence) G.9979 (IEEE 1905 compatibility) G.9960 (PHY) G.9963 (MIMO)G.9963 G.9972 (PLC Coexistence) Management Recommendations G.9964 (PSD) G.9962 (Management) BBF HGF Models Test plans Implementation Certification test TR-181 (TR-069 models) TR-208 (Performance) specification TR-374 (Yang models) Implementation guidelines 4 G.HN HISTORY: MAIN MILESTONES Provide Inclusion in Management control from larger home We´re ready Dealing with included the upper networks to move to Proof of interferences: (G.9962) layers: LCMP (G.9979) the next step! concept NDIM Ghn foundation G.hn G.hn2 paper SISO system Deal with (G.9960/G.9961) interferences to xDSL systems (G.DPM) MIMO system Security (G.9963) framework 5 (G.9978) G.HN REFERENCE MODEL Standard Ethernet Primitives Data Link Layer ITU-T Application Protocol Ethernet encapsulation Convergence G.9961 AES 128 Security, Relaying Logical Link Control and Retransmissions
    [Show full text]
  • Networking Layer Protocols for Internet of Things: 6Lowpan And
    NetworkingNetworking LayerLayer ProtocolsProtocols forfor InternetInternet ofof Things:Things: . 6LoWPAN6LoWPAN andand RPLRPL Raj Jain Washington University in Saint Louis Saint Louis, MO 63130 [email protected] These slides and audio/video recordings of this class lecture are at: http://www.cse.wustl.edu/~jain/cse570-15/ Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse570-15/ ©2015 Raj Jain 13-1 OverviewOverview 6LowPAN Adaptation Layer Address Formation Compression RPL RPL Concepts RPL Control Messages RPL Data Forwarding Note: This is part 3 of a series of class lectures on IoT. Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse570-15/ ©2015 Raj Jain 13-2 IoTIoT EcosystemEcosystem Applications Smart Health, Smart Home, Smart Grid Security Management Smart Transport, Smart Workspaces, … TCG, Session MQTT, CoRE, DDS, AMQP , … IEEE 1905, Oath 2.0, IEEE 1451, Routing 6LowPAN, RPL, 6Lo, 6tsch, Thread, SMACK, … 6-to-nonIP , … SASL, ISASecure, Datalink WiFi, Bluetooth Smart, Zigbee Smart, ace, Z-Wave, DECT/ULE, 3G/LTE, NFC, CoAP, Weightless, HomePlug GP, 802.11ah, DTLS, 802.15.4, G.9959, WirelessHART, Dice DASH7, ANT+ , LoRaWAN, … Software Mbed, Homekit, AllSeen, IoTvity, ThingWorks, EVRYTHNG , … Operating Systems Linux, Android, Contiki-OS, TinyOS, … Hardware ARM, Arduino, Raspberry Pi, ARC-EM4, Mote, Smart Dust, Tmote Sky, … Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse570-15/ ©2015 Raj Jain 13-3 IEEEIEEE 802.15.4802.15.4 Wireless Personal Area Network (WPAN) Allows mesh networking. Full function nodes can forward packets to other nodes. A PAN coordinator (like WiFi Access Point) allows nodes to join the network.
    [Show full text]
  • Management Platforms and Protocols for Internet of Things: a Survey
    sensors Article Management Platforms and Protocols for Internet of Things: A Survey Jonathan de C. Silva 1, Joel J. P. C. Rodrigues 1,2,3,* , Jalal Al-Muhtadi 3,4, Ricardo A. L. Rabêlo 5 and Vasco Furtado 6 1 National Institute of Telecommunications (Inatel), Santa Rita do Sapucaí MG 37540-000, Brazil; [email protected] 2 Instituto de Telecomunicações, 1049-001 Lisboa, Portugal 3 College of Computer and Information Sciences, King Saud University, Riyadh 11653, Saudi Arabia; [email protected] 4 Center of Excellence in Information Assurance, King Saud University, Riyadh 11653, Saudi Arabia 5 Department of Computing (DC), Graduate Program in Computer Science (PPGCC), Federal University of Piaui (UFPI), Ministro Petronio Portela Campus, Teresina 64049-550, Piauí, Brazil; [email protected] 6 Graduate Program in Applied Informatics, University of Fortaleza (UNIFOR), Fortaleza CE 60811-905, Brazil; [email protected] * Correspondence: [email protected]; Tel.: +55-(35)-3471-9200 Received: 13 December 2018; Accepted: 12 January 2019; Published: 7 February 2019 Abstract: Internet of Things (IoT) management systems require scalability, standardized communication, and context-awareness to achieve the management of connected devices with security and accuracy in real environments. Interoperability and heterogeneity between hardware and application layers are also critical issues. To attend to the network requirements and different functionalities, a dynamic and context-sensitive configuration management system is required. Thus, reference architectures (RAs) represent a basic architecture and the definition of key characteristics for the construction of IoT environments. Therefore, choosing the best technologies of the IoT management platforms and protocols through comparison and evaluation is a hard task, since they are difficult to compare due to their lack of standardization.
    [Show full text]
  • Ghn for Smart Grid and Industrial Apps IEEE ISPLC May 2020
    www.homegridforum.org “G.hn Technology for Industrial and Smart Grid Applications. ITU-T Roadmap and HomeGrid Forum Certification Update ” Marcos Martínez Vázquez Chair CWG, HomeGrid Forum Principal Communication Systems Engineer, MaxLinear Inc. IEEE ISPLC, May 13, 2020 1 – HomeGrid Forum progress 2 – ITU-T Q18/15 progress 3 – HomeGrid Forum certification 4 – Deployment examples 5 – Summary HomeGrid Forum™ 2 HomeGrid Forum progress 3 Homegrid Forum: Introduction • HomeGrid Forum (HGF) is an industry • BOARD OF DIRECTORS alliance that started in 2008. • HGF brings together technology innovators, silicon vendors, system manufacturers and service providers to promote G.hn technology. • G.hn provides a flexible connectivity • PROMOTER MEMBERS solution across any wire. • G.hn is a globally recognized ITU-T standard. 4 Homegrid Forum: Profiles Smart Grid GiGAWire-XF Connectivity Home G.hn GiGAWire Networking GiGAWire-VB Wireless backhauling IoT Li-Fi Industrial HomeGrid Forum™ 5 Homegrid Forum: Q18/15 relationship • White papers • Tutorials MWG • ITU-T Recommendations CWG Q18/15 • Technical papers C&I • Compliance, Interoperability and Performance test specifications • Product level constraints • Profiles • Contributions to standards HomeGrid Forum™ 6 ITU-T Q18/15 progress 7 ITU-T Q18/15 Recommendation (Home networking ecosystem) ITU-T Application Recommendations Core Recommendations Coexistence Recommendations G.9978 (Secure admission) G.9961 (DLL) G.9977 (DSL Coexistence) G.9979 (IEEE 1905 compatibility) G.9960 (PHY) G.9963 (MIMO) G.9963
    [Show full text]
  • ENERGY STAR Small Network Equipment Draft 1 Comment
    ENERGY STAR Small Network Equipment Draft 1 Stakeholder Comments and EPA Response Index Comment EPA Response # The immediate effective date cannot be implemented in EU. The EU will require some EPA will work with the EU to incorporate small network equipment into the current agreement as 1 months, to allow for the appropriate administrative processes before the specification can necessary. EPA believes it acceptable for the EU effective date to follow the effective date in the US. come into effect. A normal design cycle would require a minimum of 1 year to make product available, the The specification is intended to identify efficient products that are currently in the market. There are 2 Effective date needs to be more than a year out plus a reasonable transition period to products on the market that can meet the levels set forth in the specification. When other models have product meeting the requirements. 18 to 24 months is appropriate for the market. that meet the requirements become available they can be certified as ENERGY STAR as well. The exclusion for products with SFP sockets will encompass a broad range of products. There needs to be a manner for such products to be included as part of a program. There are two possible solutions: Products with fewer than 12 ports including SFP sockets would have to be explicitly EPA requests specific examples of products using SFP sockets to determine whether these products 3 included in the LNE program. This may be problematic, given different approaches in that should be covered in Version 1.0, or the upcoming LNE specification.
    [Show full text]
  • TR-181 Device Data Model
    TECHNICAL REPORT TR-181 Device Data Model Issue: 2 Amendment 14 Issue Date: November 2020 © Broadband Forum. All rights reserved. Device Data Model TR-181 Issue 2 Amendment 14 Notice The Broadband Forum is a non-profit corporation organized to create guidelines for broadband network system development and deployment. This Technical Report has been approved by members of the Forum. This Technical Report is subject to change. This Technical Report is owned and copyrighted by the Broadband Forum, and all rights are reserved. Portions of this Technical Report may be owned and/or copyrighted by Broadband Forum members. Intellectual Property Recipients of this Technical Report are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of this Technical Report, or use of any software code normatively referenced in this Technical Report, and to provide supporting documentation. Terms of Use 1. License Broadband Forum hereby grants you the right, without charge, on a perpetual, non-exclusive and worldwide basis, to utilize the Technical Report for the purpose of developing, making, having made, using, marketing, importing, offering to sell or license, and selling or licensing, and to otherwise distribute, products complying with the Technical Report, in all cases subject to the conditions set forth in this notice and any relevant patent and other intellectual property rights of third parties (which may include members of Broadband Forum). This license grant does not include the right to sublicense, modify or create derivative works based upon the Technical Report except to the extent this Technical Report includes text implementable in computer code, in which case your right under this License to create and modify derivative works is limited to modifying and creating derivative works of such code.
    [Show full text]
  • Management Protocols For
    Data-Link Layer and Management . Protocols for IoT Raj Jain Washington University in Saint Louis Saint Louis, MO 63130 [email protected] These slides and audio/video recordings of this class lecture are at: http://www.cse.wustl.edu/~jain/cse570-18/ Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse570-18/ ©2018 Raj Jain 12-1 Overview Recent Protocols for IoT Power Line Communication (PLC) HomePlug, HomePlug AV, HomePlug AV2, BPL, Netricity IEEE 1905.1 Management, Security, and Configuration Smart Cards Note: This is part 2 of a series of class lectures on IoT. Wireless datalink protocols are covered in CSE 574 Wireless Network Class. More protocols are covered in other parts of this series. Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse570-18/ ©2018 Raj Jain 12-2 Recent Protocols for IoT MQTT, SMQTT, CoRE, DDS, Security Management AMQP , XMPP, CoAP, IEC, IEEE Session 1888, … IEEE 1888.3, IEEE 1905, TCG, IEEE 1451, Encapsulation 6LowPAN, 6TiSCH, Oath 2.0, IEEE 1377, 6Lo, Thread… SMACK, IEEE P1828, Network Routing RPL, CORPL, CARP SASL, IEEE P1856 WiFi, Bluetooth Low Energy, EDSA, Z-Wave, ZigBee Smart, ace, DECT/ULE, 3G/LTE, NFC, DTLS, Weightless, HomePlug GP, Dice, … Datalink 802.11ah, 802.15.4e, G.9959, WirelessHART, DASH7, ANT+, LTE-A, LoRaWAN, ISA100.11a, DigiMesh, WiMAX, … Ref: Tara Salman, Raj Jain, "A Survey of Protocols and Standards for Internet of Things," Advanced Computing and Communications, Vol. 1, No. 1, March 2017, http://www.cse.wustl.edu/~jain/papers/iot_accs.htm Washington University in St.
    [Show full text]