Unit : 5 SERVICE LAYER

PROTOCOL
Unit Structure :
6.1 Objectives
6.2 OneM2M
6.3 ETSI & M2M
6.4 OMA
6.5 BBF
6.6 Summary
6.7 Questions
6.8 References

6.1 OBJECTIVES

At the end of this unit, the student will be able to

 Understand the concept of OneM2m, ETSI.
 Create differentiate between M2M and OneM2m.

1
. The Internet of Things (IoT) has enabled a wide range of connected devices, sensors, and
platforms to communicate with each other, creating a network of interconnected devices.
To achieve this interoperability and connectivity, a standardized framework is required.
2
. The oneM2M standard is an initiative that aims to provide a common platform for IoT
devices and services to communicate with each other. In this essay, we will discuss
oneM2M in the context of IoT, its architecture, and its benefits.
3
. oneM2M is a global standard for Machine to Machine (M2M) communications and the IoT.
It was established in 2012, and it is based on the work of a number of existing standards
organizations.
4 . oneM2M provides a common framework for IoT devices, platforms, and services to
communicate with each other. The main goal of oneM2M is to ensure interoperability
between different IoT devices and services.
 Illustrate the concept of OMA and BBF.

6.2 ONEM2M
5. oneM2M Architecture:

The oneM2M architecture is based on a horizontal layering approach that consists of four layers,
as shown below:
5.1 Application Layer: The application layer is responsible for managing the IoT applications
and services that interact with the oneM2M platform.

5.2 Platform Services Layer: The platform services layer provides a set of common services that
are used by IoT applications and services, such as security, device management, and data
management.

5.3 Infrastructure Layer: The infrastructure layer provides the underlying network and
computing infrastructure required to support IoT applications and services.

5.4 Device Layer: The device layer consists of the IoT devices and sensors that are connected to
the oneM2M platform.

Fig 1 OneM2m Functional Architecture

6. Benefits of oneM2M in IoT:

oneM2M offers several benefits when used in IoT applications. These include:
6.1 Interoperability: oneM2M provides a common platform for IoT devices and services to
communicate with each other, enabling interoperability between different IoT devices and
platforms.

6.2 Scalability: oneM2M can support a large number of devices and services, making it well
suited for large-scale IoT deployments.

6.3 Security: oneM2M provides a set of security mechanisms that can be used to secure IoT
communications and data.

6.4 Flexibility: oneM2M is a flexible standard that can be adapted to different IoT use cases and
requirements.

6.5 Global Reach: oneM2M is a global standard that can be used by IoT deployments
worldwide, ensuring compatibility between different regions and countries.
 6.6 oneM2M provides a common platform for IoT devices and services to communicate with
each other, enabling interoperability between different IoT devices and platforms. The
oneM2M architecture consists of four layers, providing a flexible and scalable framework
for IoT deployments. The benefits of oneM2M include interoperability, scalability, security,
flexibility, and global reach, making it a promising standard for the future of IoT.

6.7 OneM2M is a standard developed by a consortium of global organizations to provide a

common platform for the interoperability of different IoT devices and services. It is a
hierarchical architecture that enables seamless communication between different IoT
devices and services, regardless of the underlying network technology.

7 OneM2M has several features that make it well suited for IoT applications. These include:

7.1 Interoperability: OneM2M provides a common platform for different IoT devices and
services to communicate with each other, regardless of the underlying network technology.

7.2 Scalability: OneM2M is highly scalable, enabling it to support a large number of devices
and services.

7.3 Security: OneM2M provides built-in security features, including authentication,

authorization, and encryption.

7.4 Device management: OneM2M provides a standardized way of managing IoT devices,
including registration, discovery, and configuration.

8 Advantages of OneM2M in IoT:

OneM2M has several advantages when used in IoT applications. These include:
8.1 Interoperability: OneM2M's common platform enables different IoT
devices and services to communicate with each other, regardless of the underlying network
technology.

8.2 Scalability: OneM2M's scalability makes it well suited for large-scale IoT deployments.

8.3 Security: OneM2M's built-in security features provide a secure platform for IoT
communications.

8.4 Standardization: OneM2M provides a standardized platform that enables different IoT
devices and services to communicate with each other, reducing the complexity of integrating
different devices and services.

9 Limitations of OneM2M in IoT:

While OneM2M has several advantages, there are also some limitations to its use in IoT
applications. These include:
9.1 Complexity: OneM2M's hierarchical architecture can be complex to implement and
maintain.
9.2 Compatibility: OneM2M is not compatible with all IoT devices and services, requiring the
use of gateways or translators to translate between OneM2M and other protocols.
 9.3 Adoption: OneM2M is a relatively new standard, and its adoption may be limited in some
industries.
10 In conclusion, OneM2M is a promising standard for IoT applications, offering several advantages
such as interoperability, scalability, security, and standardization. However, it also has some
limitations, particularly in terms of complexity, compatibility, and adoption. Overall, OneM2M is
well suited for IoT deployments where interoperability, security, and scalability are critical, and
where additional security measures can be implemented to ensure secure messaging.
6.3 ETSI

1. The Internet of Things (IoT) has gained significant attention in recent years as it has become
increasingly popular to use interconnected devices to automate and optimize a variety of processes.
2. To support this, a range of standards and protocols have been developed to ensure interoperability
and facilitate the development of IoT applications.
3. One of these standards is ETSI M2M. In this essay, we will discuss ETSI M2M in the context of
IoT, outlining its features, advantages, and limitations.
4. ETSI M2M is a standard developed by the European Telecommunications Standards Institute
(ETSI) to provide a common platform for the interoperability of different IoT devices and services.
It is a set of specifications and guidelines that define the requirements for M2M (machine-to-
machine) communication.
5. Features of ETSI M2M:
ETSI M2M has several features that make it suitable for IoT applications. These include:
5.1 Interoperability: ETSI M2M provides a common platform for different IoT devices and
services to communicate with each other, regardless of the underlying network technology.
5.2 Scalability: ETSI M2M is highly scalable, enabling it to support a large number of devices
and services.
5.3 Security: ETSI M2M provides built-in security features, including authentication,
authorization, and encryption.
5.4 Device management: ETSI M2M provides a standardized way of managing IoT devices,
including registration, discovery, and configuration.

6 Advantages of ETSI M2M in IoT:

ETSI M2M has several advantages when used in IoT applications. These include:
6.1 Interoperability: ETSI M2M's common platform enables different IoT devices and services
to communicate with each other, regardless of the underlying network technology.

6.2 Scalability: ETSI M2M's scalability makes it well suited for large-scale IoT deployments.

6.3 Security: ETSI M2M's built-in security features provide a secure platform for IoT
communications.

6.4 Standardization: ETSI M2M provides a standardized platform that enables different IoT
devices and services to communicate with each other, reducing the complexity of integrating
different devices and services.
7. Limitations of ETSI M2M in IoT:

7.1 While ETSI M2M has several advantages, there are also some limitations to its use in IoT
applications. These include:

7.2 Complexity: ETSI M2M's specifications and guidelines can be complex to implement and
maintain.

7.3 Compatibility: ETSI M2M is not compatible with all IoT devices and services, requiring the
use of gateways or translators to translate between ETSI M2M and other protocols.

7.4 Adoption: ETSI M2M is a relatively new standard, and its adoption may be limited in some
industries.

8 ETSI M2M is a promising standard for IoT applications, offering several advantages such as
interoperability, scalability, security, and standardization. However, it also has some limitations,
particularly in terms of complexity, compatibility, and adoption.

9 Overall, ETSI M2M is well suited for IoT deployments where interoperability, security, and
scalability are critical, and where additional security measures can be implemented to ensure
secure messaging.

10 The ETSI M2M architecture is designed to provide a standardized framework for machine-to-
machine (M2M) communications in the Internet of Things (IoT). It is a layered architecture that
defines the key components and interfaces necessary for M2M communications.
The ETSI M2M architecture comprises the following layers:
10.1 Application Layer: This layer includes the M2M applications that use the ETSI M2M
platform for communication. The applications communicate with the platform using
standard protocols, such as HTTP or CoAP, and use ETSI M2M APIs to interact with other
components of the architecture.

10.2 Service Layer: This layer provides services to M2M applications, such as device
management, data management, and security. The services are exposed as RESTful APIs,
and applications can use them to manage and interact with M2M devices.

10.3 Network Layer: This layer provides connectivity for M2M devices, including cellular
networks, Wi-Fi, Ethernet, and others. The network layer also includes gateways that
provide translation between different network technologies and protocols.

10.4 Device Layer: This layer includes M2M devices that connect to the network layer. The
devices can be sensors, actuators, or other types of devices that collect or act on data. The
devices are managed by the service layer and can be configured, monitored, and updated
remotely.

11 The ETSI M2M architecture also includes several interfaces that enable communication between
the layers. These interfaces include:

M2M Service Interface: This interface provides access to M2M services in the service layer.
11.1 Device Management Interface: This interface enables the service layer to manage M2M
devices in the device layer.
 11.2 Application Service Interface: This interface enables M2M applications to interact with the
service layer.

11.3 Network Service Interface: This interface provides access to network services in the
network layer.

Fig 2 ETSI Architecture

12 The ETSI M2M architecture is designed to be modular and flexible, allowing different
components to be added or removed as needed. It is also designed to be scalable and secure, with
built-in security features such as authentication, authorization, and encryption.

13 Overall, the ETSI M2M architecture provides a comprehensive framework for M2M
communications in the IoT, enabling interoperability, scalability, and security across different
devices, networks, and applications.

7.4 OMA

1. OMA (Open Mobile Alliance) is a standards organization that develops specifications for mobile
and IoT devices. In the context of
IoT, OMA has developed several standards that define communication protocols, data models, and
device management techniques. These standards are intended to enable interoperability between
different IoT devices and platforms.
2. Some of the key standards developed by OMA for IoT include:

2.1 Lightweight M2M (LwM2M): This is a device management protocol that enables remote
management of IoT devices. It is designed to be lightweight and efficient, making it suitable
for use in constrained environments. LwM2M defines a set of standard objects and
interfaces for device management, and it uses CoAP as its underlying protocol.

2.2 OMA DM (Device Management): This is a device management protocol that is used in
mobile devices and IoT devices. It enables remote management of devices over various
types of networks, including cellular, Wi-Fi, and Ethernet. OMA DM defines a set of
 standard objects and interfaces for device management, and it uses HTTP or CoAP as its
underlying protocol.

2.3 OMA Lightweight Machine-to-Machine (OMA LwM2M)

Enabler: This is a set of specifications that define a standardized framework for IoT device
management. It includes specifications for device management, data management, and
security.
2.4 OMA LwM2M Enabler is designed to be scalable and flexible, allowing it to support a wide
range of IoT devices and applications.

2.5 OMA SensorThings API: This is a standard API for IoT sensors and devices that collect
data. It provides a standardized way to access and manage sensor data, making it easier to
integrate data from different sources. SensorThings API is based on RESTful principles and
uses JSON as its data format.

3. Overall, the OMA standards for IoT provide a comprehensive set of specifications that enable
interoperability, security, and manageability in IoT devices and platforms. These standards are
widely used in the industry and are supported by a large ecosystem of vendors and developers.

4. OMA (Open Mobile Alliance) architecture for IoT is designed to enable interoperability, security,
and manageability in IoT devices and platforms. The OMA architecture is based on a client-server
model, where the IoT devices act as clients and the servers manage the devices and provide
services.

5. The OMA architecture consists of several layers, each with a specific function:

5.1 Application layer: This layer contains the applications and services that run on the IoT
devices. The application layer interacts with the services provided by the server layer.

5.2 Device layer: This layer consists of the hardware and firmware that make up the IoT
devices. The device layer interacts with the services provided by the server layer through the
application layer.

5.3 Server layer: This layer provides the services that manage and control the IoT devices. The
server layer consists of several components, including the device management server, data
management server, and security server.

5.4 Gateway layer: This layer provides connectivity between the IoT devices and the server
layer. The gateway layer may include devices such as routers, gateways, and access points.

6. The OMA architecture uses standardized protocols and data models to enable interoperability
between different IoT devices and platforms. Some of the key protocols and data models used in
the OMA architecture include:

6.1 Lightweight M2M (LwM2M): This protocol is used for device management and enables
remote management of IoT devices. LwM2M uses CoAP as its underlying protocol.

6.2 OMA DM (Device Management): This protocol is used for device management and enables
remote management of IoT devices. OMA DM uses HTTP or CoAP as its underlying
protocol.

6.3 OMA Lightweight Machine-to-Machine (OMA LwM2M)

 Enabler: This set of specifications defines a standardized framework for IoT device
management. It includes specifications for device management, data management, and
security.
6.4 OMA Sensor Things API: This API is used to access and manage sensor data from IoT
devices.

7 Overall, the OMA architecture provides a comprehensive framework for building and managing
IoT devices and platforms. It enables interoperability, security, and manageability, making it easier
to develop and deploy IoT solutions.

7.5 BBF

1. BBF (Broadband Forum) is a global consortium of over 100 industryleading companies that
develop and promote broadband network technologies, including those related to the Internet of
Things (IoT).

2. The BBF's work in the IoT space is focused on defining standards and best practices for
connecting IoT devices to broadband networks, enabling the development of more reliable,
scalable, and secure IoT solutions.

3. The BBF's IoT work is organized around several key areas:

3.1 Device management: The BBF's work in this area is focused on developing standards and
best practices for managing large numbers of IoT devices connected to broadband networks.
This includes defining protocols for device discovery, configuration, firmware updates, and
diagnostics.

3.2 Security: The BBF recognizes the importance of security in IoT deployments and has
developed a range of security standards and best practices for IoT devices and networks.
These include guidelines for securing IoT devices, as well as protocols for secure
communication between devices and the network.

3.3 Data analytics: The BBF is working to develop standards and best practices for collecting,
analyzing, and using data generated by IoT devices. This includes developing standards for
data formats, protocols for data transfer and storage, and best practices for data analytics and
machine learning.

3.4 Interoperability: The BBF is committed to promoting interoperability between IoT devices
and networks. This includes developing standards for device interoperability, as well as
protocols for interoperable data exchange and communication.

3.5 One of the BBF's key contributions to the IoT space is its Open Broadband – IoT (OB-IoT)
project, which aims to define a standardized architecture for IoT deployments on broadband
networks. The OB-IoT architecture consists of several layers, each with a specific function:

3.6 Device layer: This layer consists of the IoT devices themselves, as well as the software and
firmware that enable them to connect to broadband networks. The BBF has developed
standards and best practices for device management, security, and data analytics in this
layer.
 3.7 Gateway layer: This layer provides connectivity between IoT devices and the broadband
network. Gateways may be dedicated devices or integrated into broadband modems or
routers. The BBF has developed standards and best practices for gateway management,
security, and interoperability.

3.8 Network layer: This layer includes the broadband network infrastructure, including
switches, routers, and other network devices. The BBF has developed standards and best
practices for network management, security, and interoperability.

3.9 Application layer: This layer includes the applications and services that run on top of the
broadband network, including cloud-based services and analytics platforms. The BBF has
developed standards and best practices for application development, security, and
interoperability.

4 The OB-IoT project is supported by a range of BBF members, including network operators,
equipment vendors, and service providers. The project aims to accelerate the development and
deployment of IoT solutions on broadband networks, promoting interoperability, security, and
scalability.

5 In addition to the OB-IoT project, the BBF is involved in a range of other initiatives related to IoT,
including the development of standards and best practices for smart home networks, smart cities,
and industrial IoT deployments.

6 Overall, the BBF's work in the IoT space is focused on defining standards and best practices that
enable the development of more reliable, scalable, and secure IoT solutions. The OB-IoT project is
a key part of this work, providing a standardized architecture for IoT deployments on broadband
networks. With the support of its members, the BBF is well-positioned to drive innovation and
promote interoperability in the IoT space.

7. Provide an overview of the BBF's work in IoT, focusing on the key standards and
specifications developed by the consortium.

8. TR-069 is a specification developed by the BBF for the management of broadband

networks. It provides a standard protocol for the remote management of network devices,
including IoT devices.

9. The TR-069 specification enables the management of devices over a wide range of
network types, including Ethernet, Wi-Fi, and cellular networks. The specification supports a
range of management functions, including configuration, software updates, and performance
monitoring.

10. The TR-069 specification has been widely adopted by the industry and is used by many
service providers to manage their IoT networks. It has also been adopted by the European
Telecommunications Standards Institute (ETSI) as a standard for the management of IoT devices.

11. The User Services Platform (USP) is a specification developed by the BBF for the
management of IoT devices. USP is designed to provide a standard, secure, and scalable
framework for the management of IoT devices, including those that are deployed in homes and
businesses.
12. The USP specification is based on the TR-069 protocol and provides a standardized
framework for the management of IoT devices, regardless of the type of network they are
connected to.

13. USP includes a range of management functions, including device discovery,

configuration, and software updates. It also includes support for remote diagnostics,
troubleshooting, and security management.

14. USP has been adopted by the industry and is being used by many service providers to
manage their IoT networks. It is also being promoted by the BBF as a standard for the
management of IoT devices.

15. G.hn is a standard developed by the BBF for the provision of highspeed broadband
services over any wired home network, including powerline, coaxial, and telephone line networks.

16. G.hn provides a standard protocol for the transmission of data over these networks,
enabling the delivery of high-speed broadband services to IoT devices.

17. The G.hn standard has been widely adopted by the industry and is being used by many
service providers to deliver broadband services to homes and businesses.

18. It is also being used to provide connectivity for IoT devices, enabling the deployment of
IoT solutions over existing home networks.

19. FAN (Fixed Access Network) is a specification developed by the BBF for the
management of broadband access networks. FAN provides a standardized framework for the
management of broadband access networks, including those that are used for the delivery of IoT
services.

20. FAN includes a range of management functions, including network discovery, topology
discovery, and service discovery. It also includes support for network security, device
management, and service management.

21. FAN has been adopted by the industry and is being used by many service providers to
manage their broadband access networks. It is also being used to manage IoT networks, providing
a standardized framework for the management of IoT devices.

22. Open Broadband - Broadband Access Abstraction (OB-BAA)-OBBAA is a specification

developed by the BBF for the management of broadband access networks.

23. OB-BAA provides a standardized framework for the management of broadband access
networks, including those that are used for the delivery of IoT services.

24. OB-BAA includes a range of management functions, including network discovery,

topology discovery, and service discovery. It also includes support for network security, device
management, and service management.

25. OB-BAA is being promoted by the BBF as a standard for the management of broadband
access networks.
Fig 3 USP Agent and controller Architecture