Samer Salam

Ethernet OAM: key enabler for carrier class metro ethernet services

The onset of Ethernet as a metropolitan and wide area networking, technology has driven the need for a new set of operations, administration, and maintenance protocols. Service provider networks are large and complex with a wide user base, and they often involve different operators that must work together in order to provide end-to-end services to enterprise customers. With enterprise end customer demands ever increasing, so have the requirements on service provider Ethernet networks increased, particularly in the areas of availability and mean time to repair. Ethernet OAM addresses these areas and more, and is a tool that translates directly to the competitiveness of the service provider. Ethernet OAM is a broad topic, but this article focuses on three main areas that are most in need by service providers and are rapidly evolving in the standards bodies: Service OAM, Link OAM and Ethernet LMI. These OAM protocols have unique objectives but are complementary to each other. Service OAM provides monitoring and troubleshooting of end-to-end Ethernet service instances, while link OAM allows a provider to monitor and troubleshoot an individual Ethernet link. There are of course many different ways to provide this type of functionality, but fortunately standards bodies such as ITU Study Group 13, IEEE 802.3 Clause 57 (formerly 802.3ah), IEEE 802.1ag Connectivity Fault Management, and the Metro Ethernet Forum are all driving toward consistent recommendations and standards for Ethernet OAM.

Provider backbone bridging and MPLS: complementary technologies for next-generation carrier ethernet transport

Although provider backbone bridging is sometimes cast as an alternative technology to MPLS for Ethernet transport, the fact is that both technologies can be leveraged to complement one another in a service provider network. This provides the network operator with the best of what each technology has to offer in terms of scalability, manageability, cost, and flexible support for services. An example of the two technologies working in unison is provider backbone bridging interoperating with H-VPLS over networks with an MPLS core. The combined infrastructure leverages the strengths of Ethernet and MPLS with the added advantage of addressing the major shortcomings of standard H-VPLS.

Internet of Things From Hype to Reality

ions, 98, 99 Acceleration sensors, 74 Access characteristics, 104, 105 Access points (APs), 39 Accounting and Billing, 7 Actuators analyzed data, 82 collecting and displaying data, 82 definition, 82 electric, 82 hydraulic actuators, 82–83 manual, 83 mechanical linear, 82 monitor and control IoT devices, 83 pneumatic, 83 power, 83 sensor-collection, 82 Address Resolution Protocol (ARP), 43 Advanced Encryption Standard (AES), 96 Advanced Message Queuing Protocol (AMQP), 139, 310 Advanced Research Projects Agency (ARPA), 28 Advanced Research Projects Agency Network (ARPANET), 28 Agriculture, 241, 264 Airbnb, 11, 12 Air pollution sensors, 73 AllSeen Alliance, 308 Amazon, 14 Amazon Web Services (AWS), 14 Analytics, 17–20 “Anything as a service”, 255 API Manager, 205 Application entity, 98 Application layer OSI, 37, 38 TCP/IP, 42 Application level interoperability abstractions, 98, 99 application entity, 98 cost, 98 IoT, 98 M2M deployments, 98 semantic, 99, 100 standard APIs, 98, 99 Application mobility identity vs. location addresses, 164 seamless mobility, 163 Application protocols AMQP, 139 blocking vs. non-blocking, 133, 134 CoAP, 138 communication paradigms publish/subscribe, 133 request/response, 132 data serialization formats, 132 DDS RTPS, 140 IEEE 1888, 140 MQTT, 139 QoS, 134, 136 REST, 137 SIP, 140 XMPP, 138 Application services layer data encoding, interpretation, and modeling, 150 device coupling, 142 ETSI M2M, 143–146 oneM2M, 146, 148, 149 search and discovery capabilities, 150 Index

Internet of Things (IoT) Overview

This chapter introduces the foundation of IoT and formulates a comprehensive definition. The chapter presents a framework to monitor and control things from anywhere in the world and provides business justifications on why such monitoring and control of things is important to businesses and enterprises. It then introduces the 12 factors that make IoT a present reality

IoT Protocol Stack: A Layered View

This chapter defines the IoT protocol stack and compares it to the existing Internet protocol stack. It provides a layer-by-layer walkthrough of that stack, and, for each such layer, discusses the challenges brought forward by the IoT requirements of the previous chapter, the industry progress made to address those challenges and the remaining gaps that require future work.

Industry Organizations and Standards Landscape

This chapter starts with an overview of the IoT standardization landscape and then provides an overview of the main standards defining organizations involved in IoT and a snapshot of the projects that they are undertaking. It covers the following industry organizations: IEEE, IETF, ITU, IPSO Alliance, OCF, IIC, ETSI, oneM2M, AllSeen Alliance, Thread Group, ZigBee Alliance, TIA, Z-Wave Alliance, OASIS, and LoRa Alliance. Finally, the chapter concludes with a summary of the standards gaps and provides a scorecard of the progress to date.

IoT Services Platform: Functions and Requirements

This chapter introduces the IoT Service Platform, which is considered to be the cornerstone of successful IoT solutions. It illustrates that the Service Platform is responsible for many of the most challenging and complex tasks of the solution. It automates the ability to deploy, configure, troubleshoot, secure, manage and monitor IoT entities, ranging from sensors to applications, in terms of firmware installation, patching, debugging and monitoring to name just a few. The Service Platform also provides the necessary functions for data management and analytics, temporary caching, permanent storage, data normalization, policy-based access control and exposure. Given the complexity of the Services Platform in IoT, the chapter groups the core capabilities into 11 main areas: Platform Manager, Discovery & Registration Manager, Communication (Delivery Handling) Manager, Data Management & Repository, Firmware Manager, Topology Management, Group Management, Billing and Accounting Manager, Cloud Service Integration Function / Manager, API Manager and finally Element Manager addressing Configuration Management, Fault Management, Performance Management and Security Management across all IoT entities.

The Things in IoT: Sensors and Actuators

This chapter first defines the “Things” in IoT and then describes the key requirements for things to be able communicate over the Internet.

IoT Vertical Markets and Connected Ecosystems

This chapter describes IoT Vertical Markets and Connected Ecosystems. It first introduces the top IoT verticals that include Agriculture & Farming, Energy, Enterprise, Finance, Healthcare, Industrial, Retail and Transportation. Such verticals include a plethora of sensors producing a wealth of new information about device status, location, behavior, usage, service configuration, and performance. The chapter then presents a new business model driven mainly by the new information, and illustrates the new business benefits to the companies that manufacture, support and service IoT products, especially in terms of customer satisfaction. It then presents the key requirements to deliver “Anything as a Service” in IoT followed by a specific use case.

IoT Requirements for Networking Protocols

The success of the Internet is attributed, in part, to the Internet Protocol stack that offers two key characteristics: A normalization layer (the IP layer), which guarantees system interoperability while accommodating a multitude of link layer technologies, in addition to a plethora of application protocols. IP constitutes the thin waist of the proverbial hourglass that is the Internet’s protocol stack. Layered abstractions that hide the specifics of a given layer from the one above or below it. Such abstractions define contracts or “slip surfaces” allowing innovations in one layer to proceed independent of the adjacent layersIn this chapter, we will discuss the key IoT requirements and their impact on each of the layers of the protocol stack.