Introduction to M2M
What is M2M?
The Business of M2M
Accelerating M2M Maturity
M2M Standards
The Business of M2M
The M2M Market
The M2M Market Adoption: Drivers and Barriers
The M2M Value Chain
Market Size Projections
Business Models
M2M Business Metrics
Market Evolution
Early M2M Deployments
M2M Requirements and High-Level Architectural Principles
Use-Case-Driven Approach to M2M Requirements
Smart Metering Approach in ETSI M2M
eHealth Approach in ETSI M2M
High-Level Architecture Principles for M2M Communication
ETSI M2M Services Architecture
High-Level System Architecture
ETSI TC M2M Service Capabilities Framework
ETSI TC M2M Release 1 Scenarios
ETSI M2M Service Capabilities
Introducing REST Architectural Style for M2M
ETSI TC M2M Resource-Based M2M Communication and Procedures
M2M Optimizations in Public Mobile Networks
M2M Over a Telecommunications Network
Network Optimizations for M2M
The Role of IP in M2M
IPv6 for M2M
6LoWPAN
Routing Protocol for Low-Power and Lossy Networks (RPL) CoRE
M2M Security
Trust Relationships in the M2M Ecosystem
Security Requirements
Which Types of Solutions are Suitable?
Standardization Efforts on Securing M2M and MTC Communications
M2M Terminals and Modules
M2M Module Categorization
Hardware Interfaces
Temperature and Durability Services
Software Interface
Cellular Certification
Congestion and overload control techniques in massive M2M systems: a surveyapnegrao
Lilatul Ferdouse1, Alagan Anpalagan1* and Sudip Misra2
1 WINCORE Lab, Department of Electrical and Computer Engineering, Ryerson University, Toronto, Canada
2 School of Information Technology, Indian Institute of Technology, Kharagpur, India
M2M Optimizations in Public Mobile Networks
M2M Over a Telecommunications Network
Network Optimizations for M2M
The Role of IP in M2M
IPv6 for M2M
6LoWPAN
Routing Protocol for Low-Power and Lossy Networks (RPL) CoRE
M2M Security
Trust Relationships in the M2M Ecosystem
Security Requirements
Which Types of Solutions are Suitable?
Standardization Efforts on Securing M2M and MTC Communications
M2M Terminals and Modules
M2M Module Categorization
Hardware Interfaces
Temperature and Durability Services
Software Interface
Cellular Certification
Congestion and overload control techniques in massive M2M systems: a surveyapnegrao
Lilatul Ferdouse1, Alagan Anpalagan1* and Sudip Misra2
1 WINCORE Lab, Department of Electrical and Computer Engineering, Ryerson University, Toronto, Canada
2 School of Information Technology, Indian Institute of Technology, Kharagpur, India
Study on Infrastructure Developments of Mobile Generationsijtsrd
Nowadays, as Mobile communication systems have been developing in various ways, people can get better communications and mobility. A long way in a remarkably short time has been achieved in the history of wireless. The first generation 1G has fulfilled the basic mobile voice while the second generation 2G has introduced capacity and coverage. This is followed by the third generation 3G , which has requested data at higher speeds to open the gates for truly "mobile broadband" experience. Furthermore, the fourth generation will be realized as the next generation. 4G provides access to a wide range of telecommunication services, including advanced mobile services, supported by mobile and fixed networks, which are increasingly packet based. This paper explains about the required components of infrastructure in mobile generations from 1G to 4G and also describes the performance of each portion in evolutions of 1G to 4G infrastructure. And then, people can study the introduction of the infrastructure requirements of 5G network technology. Aye Myat Myat Myo | Zar Chi Soe "Study on Infrastructure Developments of Mobile Generations" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-3 | Issue-5 , August 2019, URL: https://www.ijtsrd.com/papers/ijtsrd26570.pdfPaper URL: https://www.ijtsrd.com/engineering/electronics-and-communication-engineering/26570/study-on-infrastructure-developments-of-mobile-generations/aye-myat-myat-myo
Optimization of Quality of Service in 4G Wireless NetworksIDES Editor
4G radio access technologies should be able to
provide different types of IP services. These services rang from
narrow-band to broadband, from non-real-time to real-time,
and from unicast to multicast broadcast applications. When
the need arises for different levels of user mobility the access
systems are required with advanced capabilities of radio
resource management and Quality of Service (QoS). We
present, in this paper, the different QoS approaches by the
various wireless and connectivity’s networks as well as the
issues that will face their implementations in 4G.
Video streaming over Ad hoc on-demand distance vector routing protocoljournalBEEI
Video streaming is content sent in compressed form over the netwoks and viwed the users progressively. The transmission of video with the end goal that it can be prepared as consistent and nonstop stream. The point is that to give client support to client at anyplace and at whatever time. Mobile Ad hoc Networks (MANETs) are considered an attractive nertwork for information transmission in many applications where the customer programme can begin showing the information before the whole record has been transmitted.
Ad hoc On-demand Distance Vector (AODV) protocol is considered as one of the most important routing protocols in MANET. However, routing protocols assume a crucial part in transmission of information over the network. This paper investigates the performance of AODV Routing Protocol under video traffic over PHY IEEE 802.11g. The protocol model was developed in OPNET. Different outcomes from simulation based models are analyzed and appropriate reasons are also discussed. A different scenarios of video streaming were used. The metric in terms of throughput, end to end delay, packet delivery ratio and routing overhead were measured.
A comparision with GRP and GRP are also reported.
Jana Eggers of NaraLogics talks at BoS Conference USA 2016
See all talks here: http://businessofsoftware.org/2016/07/all-talks-from-business-of-software-conferences-in-one-place-saas-software-talks/
Laura talks about not letting the past limit your future at BoS USA 2016.
See all talks here: http://businessofsoftware.org/2016/07/all-talks-from-business-of-software-conferences-in-one-place-saas-software-talks/
Study on Infrastructure Developments of Mobile Generationsijtsrd
Nowadays, as Mobile communication systems have been developing in various ways, people can get better communications and mobility. A long way in a remarkably short time has been achieved in the history of wireless. The first generation 1G has fulfilled the basic mobile voice while the second generation 2G has introduced capacity and coverage. This is followed by the third generation 3G , which has requested data at higher speeds to open the gates for truly "mobile broadband" experience. Furthermore, the fourth generation will be realized as the next generation. 4G provides access to a wide range of telecommunication services, including advanced mobile services, supported by mobile and fixed networks, which are increasingly packet based. This paper explains about the required components of infrastructure in mobile generations from 1G to 4G and also describes the performance of each portion in evolutions of 1G to 4G infrastructure. And then, people can study the introduction of the infrastructure requirements of 5G network technology. Aye Myat Myat Myo | Zar Chi Soe "Study on Infrastructure Developments of Mobile Generations" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-3 | Issue-5 , August 2019, URL: https://www.ijtsrd.com/papers/ijtsrd26570.pdfPaper URL: https://www.ijtsrd.com/engineering/electronics-and-communication-engineering/26570/study-on-infrastructure-developments-of-mobile-generations/aye-myat-myat-myo
Optimization of Quality of Service in 4G Wireless NetworksIDES Editor
4G radio access technologies should be able to
provide different types of IP services. These services rang from
narrow-band to broadband, from non-real-time to real-time,
and from unicast to multicast broadcast applications. When
the need arises for different levels of user mobility the access
systems are required with advanced capabilities of radio
resource management and Quality of Service (QoS). We
present, in this paper, the different QoS approaches by the
various wireless and connectivity’s networks as well as the
issues that will face their implementations in 4G.
Video streaming over Ad hoc on-demand distance vector routing protocoljournalBEEI
Video streaming is content sent in compressed form over the netwoks and viwed the users progressively. The transmission of video with the end goal that it can be prepared as consistent and nonstop stream. The point is that to give client support to client at anyplace and at whatever time. Mobile Ad hoc Networks (MANETs) are considered an attractive nertwork for information transmission in many applications where the customer programme can begin showing the information before the whole record has been transmitted.
Ad hoc On-demand Distance Vector (AODV) protocol is considered as one of the most important routing protocols in MANET. However, routing protocols assume a crucial part in transmission of information over the network. This paper investigates the performance of AODV Routing Protocol under video traffic over PHY IEEE 802.11g. The protocol model was developed in OPNET. Different outcomes from simulation based models are analyzed and appropriate reasons are also discussed. A different scenarios of video streaming were used. The metric in terms of throughput, end to end delay, packet delivery ratio and routing overhead were measured.
A comparision with GRP and GRP are also reported.
Jana Eggers of NaraLogics talks at BoS Conference USA 2016
See all talks here: http://businessofsoftware.org/2016/07/all-talks-from-business-of-software-conferences-in-one-place-saas-software-talks/
Laura talks about not letting the past limit your future at BoS USA 2016.
See all talks here: http://businessofsoftware.org/2016/07/all-talks-from-business-of-software-conferences-in-one-place-saas-software-talks/
Promise Phelon of TapInfluence at BoS Conference USA 2016.
See all talks here: http://businessofsoftware.org/2016/07/all-talks-from-business-of-software-conferences-in-one-place-saas-software-talks/
Patrick Campbell of ProfitWell talks at BoS Conference USA 2016.
See all talks here: http://businessofsoftware.org/2016/07/all-talks-from-business-of-software-conferences-in-one-place-saas-software-talks/
Zack Urlocker of Duo Security talks at BoS Conference USA 2016
See all talks here: http://businessofsoftware.org/2016/07/all-talks-from-business-of-software-conferences-in-one-place-saas-software-talks/
Relationship of body mass index, fat and visceral fat among adolescentsSports Journal
In the present study the researcher studied out the correlation of Body mass index, Fat and visceral fat
among adolescents. Data was statically analyzed using descriptive statistics and Pearson Product Multi
Correlation Coefficient was used (PPMCC). It was find out that body mass index was significantly
correlated with fat and visceral fat and on the other hand fat was also significantly correlated with
visceral fat among adolescents.
Intro to IoT & the role of LwM2M Technologies (Internet of Things World 2017,...Open Mobile Alliance
Presentation for the LwM2M Ecosystem Workshop during the Internet of Things Show 2017 in Santa Clara, CA,, title: "Introduction to IoT and role Light weight machine to machine Technologies"
Presentation given by:
*Vasu Kadambi - Dean’s Executive Professor, Leavey School of Business, Santa Clara University
*Shivakumar Mathapathi - Co-Founder and CTO, Dew Mobility / Industry Advisor, Electrical Engineering / Guest Lecture, IoT and Mobile application development, Santa Clara University / Industry Advisor, Electrical Science, Sonoma State University
M2M (Machine to Machine) & MVNOs - Mobile telecommunications in 2014Martyn Taylor
Presentation on machine to machine (M2M) and mobile virtual network operators (MVNO) in the context of mobile telecommunications. Explanation of business models; overview of legal and regulatory issues; case studies
This is to declare that this is a compiled presentation made from the materials available in public domain on Internet irrespective of the exclusive references in each and every slide given or missed.
Smart Grid Systems Based Survey on Cyber Security IssuesjournalBEEI
The future power system will be an innovative administration of existing power grids, which is called smart grid. Above all, the application of advanced communication and computing tools is going to significantly improve the productivity and consistency of smart grid systems with renewable energy resources. Together with the topographies of the smart grid, cyber security appears as a serious concern since a huge number of automatic devices are linked through communication networks. Cyber attacks on those devices had a direct influence on the reliability of extensive infrastructure of the power system. In this survey, several published works related to smart grid system vulnerabilities, potential intentional attacks, and suggested countermeasures for these threats have been investigated.
A lot has been said and written about M2M communication over the last few years. The idea behind this paper is to present the concept in a lucid and compact manner, to understand its potential impact, and to clear the misconceptions surrounding the acronym.
Machine to machine (M2M) is a broad label that can be used to describe any technology that enables networked devices to exchange information and perform actions without the manual assistance of humans.
Primarily M2M and IoT are similar in upper layer such as hardware, networking or devices. But they differ in system architecture, types of applications and underlying Technologies.
This will be helpful for GTU IOT subject course understanding too!
If you like the video please subscribe to our channel and turn notifications on for future videos.
Follow us on:
Website: http://www.edtechnology.in/
Instagram: https://www.instagram.com/ed.tech/
Facebook: https://www.facebook.com/Edtech18/
Metaverse - Let's learn to understand when business becomes virtual and when ...Arief Gunawan
https://www.youtube.com/watch?v=G1GsJPqRCww
This session will dissect the main architecture of the Metaverse. This will provide enlightenment for participants to understand when business becomes virtual and when virtual becomes business. This session will begin to discuss the transition to the Metaverse, how the Metaverse world itself is, and how business is in the Metaverse.
APWiMob 2014 (Bali, 28-30 August 2014) CFPArief Gunawan
About APWiMob
APWiMob is international event in Asia Pacific designed for audience working in the wireless communications and mobile technology communities. As the Asia Pacific conference focusing on wireless and mobile technologies, APWiMob is very suitable for wireless communications researchers, industry professionals, and academics interested in the latest development and design of wireless systems and mobile technologies.
Sponsored by the IEEE Communications Society Indonesia Chapter, APWiMob has a strong foundation of bringing together industry and academia. In 2014, Bali will become the wireless foundation by hosting APWiMob 2014. The conference will include technical sessions, tutorials, and technology and business panels. You are invited to submit papers in all areas of wireless communications and mobile technologies, networks, services, and applications.
Prof Ekram Hossain on DLT 2013 in IndonesiaArief Gunawan
IEEE Communications Society (COMSOC) Indonesia Chapter proudly presest Prof Ekram Hossain on DLT 2013 in Bandung, Jakarta, Yogyakarta and Banten.
Institut Teknologi Telkom, Bandung, 27 August.
Universitas Mercu Buana, Jakarta, 28 August.
Universitas Gadjah Mada, Yogyakarta, 29 August.
Universitas Multimedia Nusantara, Banten, 30 August.
Lectures:
"Radio Resource Management in Multi-tier Cellular Wireless Networks"
and
"Modeling, Analysis, and Design of Multi-tier and Cognitive Cellular Wireless Networks"
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
1. Syllabus Day one : Business and Architectures
Introduction to M2M
What is M2M?
The Business of M2M
Accelerating M2M Maturity
M2M Standards
The Business of M2M
The M2M Market
The M2M Market Adoption: Drivers and Barriers
The M2M Value Chain
Market Size Projections
Business Models
M2M Business Metrics
Market Evolution
Early M2M Deployments
M2M Requirements and High-Level Architectural Principles
Use-Case-Driven Approach to M2M Requirements
Smart Metering Approach in ETSI M2M
Syllabus Day Two : Deployment
M2M Optimizations in Public Mobile Networks
M2M Over a Telecommunications Network
Network Optimizations for M2M
The Role of IP in M2M
IPv6 for M2M
6LoWPAN
Routing Protocol for Low-Power and Lossy Networks (RPL) CoRE
M2M Security
Trust Relationships in the M2M Ecosystem
Security Requirements
Which Types of Solutions are Suitable?
Standardization Efforts on Securing M2M and MTC Communications
M2M Terminals and Modules
M2M Module Categorization
Hardware Interfaces
Temperature and Durability ServicesSmart Metering Approach in ETSI M2M
eHealth Approach in ETSI M2M
High-Level Architecture Principles for M2M Communication
ETSI M2M Services Architecture
High-Level System Architecture
ETSI TC M2M Service Capabilities Framework
ETSI TC M2M Release 1 Scenarios
ETSI M2M Service Capabilities
Introducing REST Architectural Style for M2M
ETSI TC M2M Resource-Based M2M Communication and Procedures
Temperature and Durability Services
Software Interface
Cellular Certification
2. 6 April 20136 April 2013
Day one : Business and ArchitecturesDay one : Business and Architectures
3. Syllabus Day one : Business and Architectures
Introduction to M2M
What is M2M?
The Business of M2M
Accelerating M2M Maturity
M2M Standards
The Business of M2M
The M2M Market
The M2M Market Adoption: Drivers and Barriers
The M2M Value Chain
Market Size Projections
Business Models
M2M Business Metrics
Market Evolution
Early M2M Deployments
M2M Requirements and High-Level Architectural PrinciplesM2M Requirements and High-Level Architectural Principles
Use-Case-Driven Approach to M2M Requirements
Smart Metering Approach in ETSI M2M
eHealth Approach in ETSI M2M
High-Level Architecture Principles for M2M Communication
ETSI M2M Services Architecture
High-Level System Architecture
ETSI TC M2M Service Capabilities Framework
ETSI TC M2M Release 1 Scenarios
ETSI M2M Service Capabilities
Introducing REST Architectural Style for M2M
ETSI TC M2M Resource-Based M2M Communication and Procedures
Arief Hamdani GunawanArief Hamdani Gunawan
4. The Essence of M2M (1/2)
• The role of M2M is to establish the
conditions that allow
– a device to (bidirectionally) exchange
informationinformation
– with a business application
– via a communication network,
– so that the device and/or application
can act as the basis for this information
exchange.
5. The Essence of M2M (2/2)
• The basic way to describe M2M is
shown in the “essence” of M2M.
– The role of M2M is to establish the
conditions that allow a device to
(bidirectionally) exchange information
with a business application via awith a business application via a
communication network, so that the
device and/or application can act as the
basis for this information exchange.
– In this definition, the communication
network has a key role:
a collocated application and device can hardly
be considered as having an M2M relationship.
6. Group of Devices in an M2M Relationship (1/2)
• In many cases,
–M2M involves a group of similar
devices interacting with a single
application.
7. Group of Devices in an M2M Relationship (2/2)
• In many cases, M2M involves a group
of similar devices interacting with a
single application.
• Fleet management is an example of
such an application, where devices are,
for example, trucks, and the
communication network is a mobile
network.
8. The Mediated M2M Relationship (1/2)
• In some cases,
– the devices in the group may not
directly interact with the
application owing to having onlyapplication owing to having only
limited capacities.
• The relationship is mediated by
another device (e.g., a gateway)
– that enables some form of
consolidation of the
communication.
9. The Mediated M2M Relationship (2/2)
• In some cases, the devices in the
group may not directly interact with
the application owing to having only
limited capacities.
• In this scenario, the relationship is
mediated by another device (e.g., amediated by another device (e.g., a
gateway) that enables some form of
consolidation of the communication.
• “Smart metering” is an example of
such an application where the devices
are smart meters and the
communication network can be a
mobile network or the public Internet
10. M2M area network
• The term “M2M area network” has been introduced
by the European Telecommunication Standards
Institute (ETSI).
• An M2M area network provides
– physical and
– MAC layer connectivity
between different M2M devices connected
to the same M2M area network,
thus allowing M2M devices to gain access
to a public network via a router or a gateway.
11. Characteristic
• M2M's unique characteristic is largely
due to the key role of the end-device.
• Devices are not new in the world of information and
communication technologies (ICT), butcommunication technologies (ICT), but
with M2M that market is seeing a new family of
devices with very specific characteristics.
• These characteristics are further discussed below,
particularly their impact on the requirements
for applications and networks
that have not until now been fully taken into
account.
12. Characteristic : Multitude
• This is the most advocated change brought about by
M2M.
• It is generally agreed that the number of “devices”
connected in M2M relationships will soon largely
exceed the sum of all those that directly interact withexceed the sum of all those that directly interact with
humans (e.g., mobile phones, PCs, tablets, etc.).
• An increased order of magnitude in the number of
devices results in significantly more pressure on
applications architectures, as well as on network load,
creating in particular scalability problems on systems
that have been designed to accommodate fewer
“actors” and far greater levels and types of traffic.
13. Characteristic : Variety
• There are already a particularly large number of
documented possible use cases for M2M that apply
to a variety of contexts and business domains.
• The initial implementations of M2M applications
have already led to the emergence of a large variety
of devices with extremely diverse requirements in
terms of data exchange rate, form factor, computing,
or communication capabilities.
• One result of the wide variety is heterogeneity, which
is in itself a major challenge to interoperability.
14. Characteristic : Invisibility
• This is a strong requirement in many M2M
applications: the devices have to routinely deliver
their service with very little or no human control.
• In particular, this is preventing humans from
correcting mistakes (and also from creating new
ones).
• As a result, device management more than ever
becomes a key part of service and network
management and needs to be integrated seamlessly.
15. Characteristic : Critically
• Some devices are life-savers, such as in the field of
eHealth (blood captors, fall detectors, etc.).
• Some are key elements of life-critical infrastructures,
such as voltage or phase detectors, breakers, etc, in
the Smart Grid.
• Their usage places stringent requirements upon
latency or reliability, which may challenge or exceed
the capabilities of today's networks
16. Characteristic : Intrusiveness
• Many new M2M devices are designed with the
explicit intention to “better manage” some of the
systems that deal with the end-users' well-being,
health, etc.
• Examples are the eHealth devices already
mentioned, smart meters for measuring and/or
controlling electrical consumption in the home, etc.
• This in turn leads to issues of privacy.
17. Specificities of M2M devices
• In addition to the above-listed characteristics and their
impact on the architecture of M2M systems, it is
important to consider the other specificities of M2M
devices that put additional constraints on the way they
communicate through the network, it is important tocommunicate through the network, it is important to
consider the other specificities of M2M devices that
put additional constraints on the way they
communicate through the network.
• This may require new ways to group the devices
together.
• Among other things, devices can be:
18. Limited in functionality
• Most M2M devices have computational capabilities
several orders of magnitude below what is currently
present in a modern portable computer or a smart
phone.
• In particular, devices may be lack remote software• In particular, devices may be lack remote software
update capabilities.
• One of the main reasons for this design choice is
cost, often because the business model requires very
competitively priced devices (e.g., smart meters in
many cases).
19. Low-powered
• Although many M2M devices are connected to a
power network, many of them have to be powered
differently (often on batteries) for a variety of
reasons.
• For instance, a large number of them are, or will be,• For instance, a large number of them are, or will be,
located outdoors and cannot be easily connected to
a power supply (e.g., industrial process sensors,
water meters, roadside captors).
• This will reduce the amount of interaction between
such devices and the M2M applications (e.g., in the
frequency and quantity of information exchanged).
20. Embedded
• Many devices are, and will be, deployed in systems
with specific (hostile, secure) operating conditions
that will make them difficult to change without a
significant impact on the system itself.
• Examples are systems embedded in buildings or in
cars that are hard to replace (e.g., when they are
soldered to the car engine, as is the case with some
M2M devices).
21. Here to stay
• Last but not least, many of the new M2M devices are and
will be deployed in non-ICT applications with very
different lifetime expectancy.
• The rate of equipment change in many potential M2M
business domains may be lower than in the ICT industry.
• This may be linked to cost issues due to different• This may be linked to cost issues due to different
business models (e.g., no subsidization of devices by the
operators), to the fact that they are embedded, but also
to the complexity of evolution of the industrial process in
which the device is operating (e.g., criticality of the
service makes changing equipment in a electricity
network very difficult, which leads to long life cycle of
equipment in the field).
25. Challenges: Fragmentation
1. Fragmentation of solutions
In the vast majority of cases,
the solutions developed and implemented
to date have been addressingto date have been addressing
specific vertical applications requirements
in isolation from all others.
26. Challenges: Network Misalignment
2. Network misalignment
As already stated,
communication networks
have been designedhave been designed
with many requirements
that differ substantially
from those of M2M.
27. Challenges: Security
3. Security
As already outlined,
some of the most promising M2 applications
(eHealth, Smart Grids)(eHealth, Smart Grids)
are safety-critical and must be made robust
against a large variety
of security threats.
28. Challenges: Privacy
4. Privacy
To develop and resolve
the sensitive issue of privacy,
both regulationboth regulation
(an essential precondition)
and standardization
are required.
29. Challenges: Service Capabilities
5. Service capabilities
In order to deal with the fragmented market,
it is necessary to outline capabilities
that can be reusedthat can be reused
across several applications.
30. Challenges: Testing, certification
6. Testing, certification
A large number of M2M solutions
will have to be developed
outside of the traditional service silos,outside of the traditional service silos,
integrated with other M2M
or traditional applications.
31. Accelerators
Taking into account the above challenges, “Stages of M2M industry maturity”
also outlines three major maturity accelerators for M2M, namely:
1. high-level frameworks – This refers to an emerging set of standards-
based architectures, platforms, and technologies integrated in a way that
allows for the development of “non-silo,” future-proof applications.
2. policy and government incentives – Based on the realization that some
M2M challenges may not be addressed by the industry alone, public
authorities and governments have started to play an active role both in
M2M challenges may not be addressed by the industry alone, public
authorities and governments have started to play an active role both in
stimulating the investment by setting up ambitious incentive programs
and in policy-making.
3. standards – A large number of credible industrial partners, large and
small, from various industries (including but not only ICT) have started to
work together in order to create the new standards required to address
M2M at the global system level.
32. Accelerating M2M Maturity:
High-Level M2M Frameworks
• The largest part of the challenge facing the
M2M actors is to transform vertical silos into a
set of easily developable and incrementally
deployable applications.deployable applications.
• “Stages of M2M Industry Maturity” shows
that the transition to the phase two of M2M
maturity will be marked by the advent and
deployment of horizontal platforms.
33. Accelerating M2M Maturity:
High-Level M2M Frameworks
• What is meant by “horizontal” is a coherent
framework valid across a large variety of
business domains, networks, and devices, that
is, a set of technologies, architectures, andis, a set of technologies, architectures, and
processes that will enable functional
separations, in particular application and
network layers, as depicted in “An M2M
challenge: emergence of the M2M service
layer”
34. Inverting The Pipes
existing proprietary
vertical applications…
applications share common infrastructure,
environments and network elements
36. Accelerating M2M Maturity:
Policy and Government Incentives
• After initial slow progress, public authorities and
governments have now realized that they have a key
role to play in the take-off of M2M communications,
especially because M2M is an integral element in many
of the new systems that are deemed to be essential for
the future of their countries or regions.the future of their countries or regions.
• Several lessons have been learnt and measures applied
in the definition of incentives regarding, in particular,
the role of standards to allow for infrastructure
optimization, or the positive effect of economies of
scale and reusability of service capabilities as a major
enabler for mainstream deployments.
37. M2M Standards
• Unlike in several other ICT segments where it may be
possible to deploy operational systems despite a lack of
standards, several M2M market segments demand strong
standards to ensure long-term investment protection.
• For several M2M applications, including smart metering or
Smart Grids, there is an expectation that the installedSmart Grids, there is an expectation that the installed
equipment will be deployed for more than 20 years.
• While such a lifetime may appear unrealistic (or at least
unusual) for traditional Telco deployments, the
infrastructures deployed by utilities have very long
deployment cycles that could dramatically influence their
design and henceforth the related standards.
39. ZigBee alliance
• A set of specifications of communication
protocols (but also data models) using small
low-power radio devices based on the IEEE
802.15.4.802.15.4.
• Target applications include switches with
lamps, electricity meters with in-home
displays, consumer electronics equipment,
etc.
40. KNX
• A purpose-built radio frequency standard
developed for home and building control.
• It is approved as an International Standard
(ISO/IEC 14543-3) as well as a European(ISO/IEC 14543-3) as well as a European
Standard (CENELEC EN 50090 and CEN EN
13321-1) and Chinese Standard (GB/Z 20965).
41. Home grid
• Based on the ITU-T specification suite known
as G.hn that is designed to provide
communications within the home
environment, making use of existing wiresenvironment, making use of existing wires
such as powerline, coax cable or copper pairs.
42. IETF protocol suite
• Based on 802.15.4 providing a specification
for L1 and L2 WPAN, the IETF has developed a
set of protocols aimed at bringing native IP
support to constrained devicesupport to constrained device
43. Syllabus Day one : Business and Architectures
Introduction to M2M
What is M2M?
The Business of M2M
Accelerating M2M Maturity
M2M Standards
The Business of M2M
The M2M Market
The M2M Market Adoption: Drivers and Barriers
The M2M Value Chain
Market Size Projections
Business Models
M2M Business Metrics
Market Evolution
Early M2M Deployments
M2M Requirements and High-Level Architectural Principles
Use-Case-Driven Approach to M2M Requirements
Smart Metering Approach in ETSI M2M
eHealth Approach in ETSI M2M
High-Level Architecture Principles for M2M Communication
ETSI M2M Services Architecture
High-Level System Architecture
ETSI TC M2M Service Capabilities Framework
ETSI TC M2M Release 1 Scenarios
ETSI M2M Service Capabilities
Introducing REST Architectural Style for M2M
ETSI TC M2M Resource-Based M2M Communication and Procedures
Muhammad Ary MurtiMuhammad Ary Murti
44. The Business of M2M
M2M: Architecture and Applications
BTP, Bandung, 6-7 April 2013.
Muhammad Ary Murti
m_ary_murti@ieee.org
45. The Business of M2M
• The M2M Market
• Market Size Projections
• Market Evolution
• The M2M Market Adoption: Drivers and Barriers• The M2M Market Adoption: Drivers and Barriers
• The M2M Value Chain
• M2M Business Metrics
• Business Models
• Early M2M Deployments
m_ARy_murti@ieee.org, 6-7 April 2013
47. ICT arena is changing very quickly
• about a decade ago, headlines were
dominated by companies like Vodafone,
Orange, Telefonica, Nokia, Ericsson, Siemens,
etcetc
• today, headlines are only dominated by
companies like Google, Apple, Facebook
• ICT infrastructures and technologies have
been sidelined to facilitators/enablers!
m_ARy_murti@ieee.org, 6-7 April 2013
48. A few additional observations from
these latest trends
• whoever provides only hardware & infrastructure is
loosing out on the long run being close to the user (or
to the problem) is paramount (see Apple’s iPhone)
• allowing for true scalability via ability for 3rd parties to
capitalize on entire system, i.e. hardware and softwarecapitalize on entire system, i.e. hardware and software
and services, is key (see App Store concept which Steve
Jobs by the way was against)
• having a hand on the data is absolute key (see Google
who search, but also IBM who store, Cisco who route,
etc)
m_ARy_murti@ieee.org, 6-7 April 2013
50. M2M solutions deliver many compelling benefits
Measures that drive investments in M2M vary greatly across
different industries and applications
Source: Harbor Research, Inc., September 2010
m_ARy_murti@ieee.org, 6-7 April 2013
51. Identifying the Potential of the e-Health Vertical
User types:
–Personal fitness/health
–Worried wells
–Telemedicine
–First responders
–Connected medical environments–Connected medical environments
–Remote monitoring
–Assisted living
–Trials
These user types are projected to
have roughly 774 million connected
devices by 2020
Source: Machina Research
m_ARy_murti@ieee.org, 6-7 April 2013
52. Growing Cellular M2M Market
Predictions on M2M LTE:
• minor market until 2014
• 2.5% (1.7M) of total M2M
market
• LTE module = twice 3G
costcost
Predictions on Automotive:
• primary market on M2M
cellular
• unique (short-term)
market for M2M LTE
m_ARy_murti@ieee.org, 6-7 April 2013
53. • The M2M Value Chain
• M2M Business Metrics
• Business Models• Business Models
m_ARy_murti@ieee.org, 6-7 April 2013
54. ETSI: TC M2M Architecture
m_ARy_murti@ieee.org, 6-7 April 2013
55. ETSI: TC M2M Architecture
m_ARy_murti@ieee.org, 6-7 April 2013
57. Value shift
• Today, CSPs are doing what they do easily and
very well– selling connectivity. This represents
almost 90% of M2M revenue in the current
market
• Tomorrow, certainly within three years – revenue• Tomorrow, certainly within three years – revenue
distribution will make an inexorable shift to what
end users want to do with M2M:
— Support business decisions with M2M data
intelligence.
— Secure and manage M2M data.
— Identify and create new applications for M2M.
m_ARy_murti@ieee.org, 6-7 April 2013
59. Revenue models
• “To avoid being a bit pipe, operators must find a
way to play a greater role. The only way forward
is to develop partnerships with M2M developers
based on revenue sharing.” – Operator, Eastern
EuropeEurope
— Most CSPs function as M2M data wholesalers.
— Only one in every 10 CSPs actively runs revenue-
sharing models with partners.
— Fewer than one in 10 routinely offers service-
level or application-based pricing for M2M.
m_ARy_murti@ieee.org, 6-7 April 2013
61. WAN Dominates the Wireless Connection Space
Mobile networks are
expected to host
roughly 86 million
connections
• Fixed installations• Fixed installations
are usually short
range to a home hub
• Greater demand for
mobility, faster data
speeds and remote
monitoring
Source: Machina Research
m_ARy_murti@ieee.org, 6-7 April 2013
62. M2M Module Price Comparison
Source: Harbor Research, Inc., September 2010
m_ARy_murti@ieee.org, 6-7 April 2013
63. M2M mobile traffic revenues by service type
MNOs to Realize Revenues in the Billions
Source: Machina Research
m_ARy_murti@ieee.org, 6-7 April 2013
64. M2M mobile traffic revenues by M2M player
e-Health is a Good Opportunity for Many Players
Source: Machina Research
m_ARy_murti@ieee.org, 6-7 April 2013
65. New Dynamics for M2M (1 of 3)
m_ARy_murti@ieee.org, 6-7 April 2013
66. New Dynamics for M2M (2 of 3)
m_ARy_murti@ieee.org, 6-7 April 2013
67. New Dynamics for M2M (3 of 3)
m_ARy_murti@ieee.org, 6-7 April 2013
68. Top 10 things you need to know
1. The total opportunity will be huge
2. Addressing the opportunity requires tailored
solutions
3. Impossible for one company to serve all3. Impossible for one company to serve all
verticals: partnerships will abound
4. Traffic: M2M (generally) does not need new,
high capacity networks
5. QoS guarantees may be pre-requisite for
some industrial applications
m_ARy_murti@ieee.org, 6-7 April 2013
69. Top 10 things you need to know
6. Energy and e-Health are the targets for
investment
7. Distribution channels, billing, brand, etc. are
all significant assets for MNOsall significant assets for MNOs
8. MNOs can increase margins with network
capabilities
9. Revenues for a wide range of industry players
10. The industry is in a period of disruption
m_ARy_murti@ieee.org, 6-7 April 2013
71. Starting with a Customer Centric View
to Develop the Value Proposition
m_ARy_murti@ieee.org, 6-7 April 2013
72. What is it others want?
- The Value Proposition
Needs – How do you get access to the
customer?
• listen to your customer carefully before and
during the design
• pick him up and accompany him to Needs
growing with him
Product - What is „this“ at all?
• Physical, tangible Object
• Service
• Feelings ( Peace of Mind, Safety, Comfort,
Belonging )
-> Customer Experience (Customer Journey)
The whole is more than the sum of its parts.
m_ARy_murti@ieee.org, 6-7 April 2013
73. What the Customers Expect from Us
The results of the customer insights (interviews) strongly influence product
design (customer experience design) and thus the business model.
m_ARy_murti@ieee.org, 6-7 April 2013
74. One technical solution – two very different products
Allianz: Crash Recorder versus Help Box
The whole is more than the sum of its parts.
m_ARy_murti@ieee.org, 6-7 April 2013
75. Fleshing out the Business Model looking at the
interactions between the blocks
m_ARy_murti@ieee.org, 6-7 April 2013
76. Many individuals need to be reached
Many individual needs need to be reached
m_ARy_murti@ieee.org, 6-7 April 2013
78. The five critical M2M success factors for CS P success
[Source: Analysys Mason, 2012]
m_ARy_murti@ieee.org, 6-7 April 2013
79. Recommendations for
communication service providers (CSPs)
• Combine partnership, resale, and acquisition
models to bring M2M solutions to market. The go-to-market approach for each CS
P will vary according to specific competencies, but sales of a more end-to-end
solution require a fairly strong presence across the supply chain. Partnerships,
particularly at the applications layer, will be critical for most CS Ps.
• Prioritize M2M solutions based on revenue
and profitability metrics. There are more M2M applications in the enterprise and
consumer worlds than may be addressed profitably. Pick the top solutions andconsumer worlds than may be addressed profitably. Pick the top solutions and
focus your resources.
• Dedicate human resources to an M2M business unit
Treat M2M like a start-up business unit and dedicate staff and budget to the
group. Reconsider the placement of human resources – whether in corporate
functions or in the field. Allocate profit and loss responsibility accordingly.
• Create an M2M identity based on existing,
enterprise perceptions and brand awareness. M2M is a solution in which
communications – with growing emphasis on mobility – and IT overlap. It will be
important in creating an M2M identity for a CS P to understand the enterprise IT
buyer’s impressions of its overall enterprise capabilities.
m_ARy_murti@ieee.org, 6-7 April 2013
82. M2M at Sea
• Most of the world’s cargo transportation needs are• Most of the world’s cargo transportation needs are
served by ocean transport, yet these vast areas
have been cut off from communication, as no
network has been able to supply connectivity
• With Ericsson’s technology, vessel fleets in the
middle of the ocean are essentially running their own
wireless networks via satellite uplink.
m_ARy_murti@ieee.org, 6-7 April 2013
83. M2M at Sea
• Achieving
Benefits Across
the Sea
• Making• Making
Containers Smart
• Creating
Industry-Wide
Efficiencies
m_ARy_murti@ieee.org, 6-7 April 2013
84. M2M at Sea
Achieving
Benefits Across
the Sea
•This kind of communication also paves the way for immediate access to remote•This kind of communication also paves the way for immediate access to remote
expertise, resulting in extended access to information and, in turn, improved
efficiency in vessels’ daily operations.
•Shipping companies will have real-time access to information about vessel
operation, bunker fuel consumption, and electric conditions. They will also be
able to monitor and prevent any difficulties in systems on board before they
happen.
•One of the primary benefits for shipping companies will come from their ability
to proactively manage bunker consumption through real-time data, which will
create significant operational savings.
m_ARy_murti@ieee.org, 6-7 April 2013
85. M2M at Sea
• Making
Containers Smart
•A full view of every container will be available,•A full view of every container will be available,
whether a vessel is in the middle of the ocean or at a
dock in a port.
•Once docked, the device connectivity of containers
will switch to a local operator network so that the
tracking can continue when the next leg of trucking
transportation begins.
m_ARy_murti@ieee.org, 6-7 April 2013
86. M2M at Sea
• Creating
Industry-Wide
Efficiencies
• Machine-to-machine (M2M) solutions, such as the one• Machine-to-machine (M2M) solutions, such as the one
described here, will help shipping companies employ new
and efficient ways of addressing fleet management.
• This technology will help manage delivery times, improve
interaction with vessels, and increase the efficiency of the
global supply chain. Shipping companies will be able to
proactively resolve issues, promptly share information with
customers, and even improve energy efficiency
m_ARy_murti@ieee.org, 6-7 April 2013
87. Speed Up Traffic with M2M
Improving logistics in the Port of Hamburg
• second largest port in Europe, the size of 7,000
soccer fields and welcomes up to 40,000 trucks a
day, each carrying six or twelve containers.
• Physical expansion was not an option, since the
city of Hamburg surrounds the port.city of Hamburg surrounds the port.
• The port’s road infrastructure – over 80 miles
(130 kilometers) – is restricted, and offers very
limited ability to expand.
• What was needed was an efficient traffic
management system.
m_ARy_murti@ieee.org, 6-7 April 2013
88. • partnered with SAP and Deutsche Telekom in its Smart
Port Logistics pilot project. During an initial three-
month trial, 30 trucks were fitted with
tabletsconnected to the prototype Smart Port Logistics
System.
• The system receives and integrates three sources of
Speed Up Traffic with M2M
Improving logistics in the Port of Hamburg
• The system receives and integrates three sources of
information in real time:
1. traffic information;
2. infrastructure information, including parking and the
status of tunnels and moving bridges;
3. location of participating trucks approaching or within
the Port of Hamburg.
m_ARy_murti@ieee.org, 6-7 April 2013
89. Smart Port Logistics
Drivers receive automated, personalized text-based messages with relevant traffic information
and details about available parking, allowing them to take optimal routes and avoid long waits.
As an added benefit, participating freight forwarding companies are also able to track their
transport orders in real time.
waiting times for trucks will decrease, and there will be fewer traffic jams within the port area
and on the approach roads.
m_ARy_murti@ieee.org, 6-7 April 2013
91. Syllabus Day one : Business and Architectures
Introduction to M2M
What is M2M?
The Business of M2M
Accelerating M2M Maturity
M2M Standards
The Business of M2M
The M2M Market
The M2M Market Adoption: Drivers and Barriers
The M2M Value Chain
Market Size Projections
Business Models
M2M Business Metrics
Market Evolution
Early M2M Deployments
M2M Requirements and High-Level Architectural Principles
Use-Case-Driven Approach to M2M RequirementsUse-Case-Driven Approach to M2M Requirements
Smart Metering Approach in ETSI M2M
eHealth Approach in ETSI M2M
High-Level Architecture Principles for M2M Communication
ETSI M2M Services Architecture
High-Level System Architecture
ETSI TC M2M Service Capabilities Framework
ETSI TC M2M Release 1 Scenarios
ETSI M2M Service Capabilities
Introducing REST Architectural Style for M2M
ETSI TC M2M Resource-Based M2M Communication and Procedures
Arief Hamdani GunawanArief Hamdani Gunawan
92. M2M Requirements and High-Level Architectural Principles
• Most standards organizations, including 3GPP, 3GPP2, and
ETSI, have adopted a use-case-driven approach as a means
with which to derive the set of requirements that further
define the service architecture. ETSI, however, has adopted
a more formal way of describing the use cases.
• In addition to the use-case-driven approach, it became very• In addition to the use-case-driven approach, it became very
clear that all network optimization matters, both
equipment features and the design or operational
networks, also have to take into account fundamental
characteristics of M2M-generated traffic and growth
patterns.
• Both issues put forward new and particularly challenging
requirements on the access and core network
93. What is a Use Case?
• The term use case is very commonly used.
However, a commonly agreed definition is more
difficult to find. The Object Management Group
(OMG) provides an excellent definition and(OMG) provides an excellent definition and
approach regarding the description of use cases.
• According to the OMG, a use case describes the
interactions between one or more actors on the
one hand and the system under consideration on
the other.
94. ETSI M2M Work on Use Cases
• The ETSI Technical Committee (TC) M2M was
created in January 2009 and aims to provide
an end-to-end view of M2M communication
architecture.architecture.
• This end-to-end view does not mean that all
elements of an M2M system are specified by
ETSI TC M2M.
97. Smart Metering Approach in ETSI M2M
• General Use Case Description
– A smart metering information system is configured to support the pre-
payment functionality as defined by the billing entity. The use case
describes occasions where the pre-payment functionality is managed
locally on the smart metering information system as well as instances
where the management is performed remotely by the billing entity.
• Stakeholders• Stakeholders
– Billing Entity: Organization responsible for billing the consumer(s).
– Consumer: Organization or person consuming the electricity, gas, heat,
or water at the premise location. The consumer may also be the
organization or person contracted with the billing entity to pay the bill.
– Asset Entity: Organization responsible for the installation,
configuration, operation, and maintenance of the smart metering
information system assets (e.g., meters communication devices, smart
metering gateway)
101. eHealth Approach in ETSI M2M:
General Use Case Description
• In a remote patient monitoring scenario where low
voltage body signals need to be acquired for remote
health monitoring purposes, the acquisition process
could be disturbed by radio transmission activities,
such as GSM/GPRS, that can take place on the nearestsuch as GSM/GPRS, that can take place on the nearest
co-located radio parts of the same M2M device.
• Where the health monitoring process is continuously
applied to the patient, for example, discovering
arrhythmias, the acquisition activity could be disrupted
by typical cellular radio communication activities
performed by the M2M device
102. eHealth Approach in ETSI M2M:
Stakeholders: Patient
• The patient may be any individual or surrogate
who could use a remote monitoring device
(RMD) to gather measurements, data, or
events.
• The patient measurements may be taken in
various clinical settings, such as a hospital, or
non-clinical settings, such as at home, at work,
at school, while traveling, or in assisted-living
facilities.
103. eHealth Approach in ETSI M2M:
Stakeholders: Remote Monitoring Device (RMD)
• An electronic M2M device with a sensor, user
interface and/or actuator, and an interface
into the M2M network.
• The device collects patient information and• The device collects patient information and
communicates to the appropriate M2M
service-capability provider and/or M2M
application via the M2M network.
• An RMD may also communicate with these
entities via an M2M gateway.
104. eHealth Approach in ETSI M2M:
Stakeholders: M2M service capability provider
• A network entity that provides M2M
communication services to the M2M
application entities.
• These applications may support specific• These applications may support specific
functional capabilities that assist in facilitating
health information-exchange activities.
• Additionally, the M2M service-capability
provider communicates with the RMD to
collect data or send commands.
105. eHealth Approach in ETSI M2M:
Stakeholders: M2M application entity
• A term created to bundle together, and treat as a single
system element, stakeholders above the M2M scope.
• High-level applications such as free-standing or
geographic health information exchanges, data analysis
centers, integrated care-delivery networks, providercenters, integrated care-delivery networks, provider
organizations, health record banks, or public health
networks, and/or specialty networks are all examples
of M2M application entities.
• The term M2M application entity also includes the
following typical RPM stakeholders.
106. High-Level Architecture Principles
for M2M Communications
• Lessons have been learned from early M2M
deployments.
• First, vertically integrated applications are hard to
develop, deploy and test.
Not only do these need to deal with the application– Not only do these need to deal with the application
business logic, but they must also include a large
number of network-aware functionalities.
– Looking at the M2M applications requirements, it is
clear that they all rely on a set of similar building
blocks, particularly when it comes to all aspects
related to communications and underlying networks
107. High-Level Architecture Principles
for M2M Communications
• Second, M2M is all about cost-effectiveness.
M2M is known to generate a fraction of the ARPU
(average revenue per user) of other consumer
handsets such as smart phones.
– However, all analysts agree that the number of– However, all analysts agree that the number of
deployed M2M devices will be an order of magnitude
higher than personal communication devices.
– As a result, the network has to become M2M-aware
and take advantage of all traffic characteristics of
M2M in order to provide the level of scaling and cost
that matches projected M2M devices and ARPU
structure.
111. Closing
• It clearly shows that M2M imposes very specific
requirements on the network in order to achieve
lower investment and operational costs that
match ARPU constraints imposed by M2M
communications.communications.
• Such a horizontal platform also provides easier
access to network enablers, such as location,
QoS, and addressing, which would otherwise be
difficult to access because of the multiplicity of
interfaces and the complexity involved in building
business relationships with multiple operators.
112. Syllabus Day one : Business and Architectures
Introduction to M2M
What is M2M?
The Business of M2M
Accelerating M2M Maturity
M2M Standards
The Business of M2M
The M2M Market
The M2M Market Adoption: Drivers and Barriers
The M2M Value Chain
Market Size Projections
Business Models
M2M Business Metrics
Market Evolution
Early M2M Deployments
M2M Requirements and High-Level Architectural Principles
Use-Case-Driven Approach to M2M Requirements
Smart Metering Approach in ETSI M2MSmart Metering Approach in ETSI M2M
eHealth Approach in ETSI M2M
High-Level Architecture Principles for M2M Communication
ETSI M2M Services Architecture
High-Level System Architecture
ETSI TC M2M Service Capabilities Framework
ETSI TC M2M Release 1 Scenarios
ETSI M2M Service Capabilities
Introducing REST Architectural Style for M2M
ETSI TC M2M Resource-Based M2M Communication and Procedures
Arief Hamdani GunawanArief Hamdani Gunawan
121. Glossary of M2M Capabilities
• Application Enablement (xAE),
• Generic Communication (xGC),
• Reachability, Addressing and Repository (xRAR),
• Communication Selection (xCS),
• Remote Entity Management (xREM),
• SECurity (xSEC),
History and Data Retention (xHDR),• History and Data Retention (xHDR),
• Transaction Management (xTM),
• Compensation Broker (xCB),
• Telco Operator Exposure (xTOE),
• Interworking Proxy (xIP)
• Service Capability Layer (xSCL)
where x is:
• N for Network,
• G for Gateway.
• D for Device
123. Device Types (1/2)
The following device types
• Gateway (G) is an ETSI M2M device specialized to
directly manage M2M area networks of ETSI M2M
devices; the gateway directly communicates with an
ETSI M2M core network via the mId reference point.
• Device (D) is an ETSI M2M device that can directly• Device (D) is an ETSI M2M device that can directly
communicate with an ETSI M2M core network or with
an ETSI M2M gateway.
• Device' (D') is an ETSI M2M device that does not
implement ETSI M2M SCs. It interacts indirectly with
the M2M core via the use of SCs in the M2M gateway
(G).
124. Device Types (2/2)
• Gateway' (G') is an ETSI M2M gateway that provides
connectivity to both D and D' devices. Note that G' is
not handled within the ETSI TC M2M Release 1
specification.
• Additionally, there is a non-ETSI M2M-compliant device
(d) belonging to an M2M area network managed by an
ETSI M2M compliant device or gateway entities. The
(d) type devices cannot access M2M SCs directly.
However, interworking with ETSI-compliant entities is
possible via the xIP (interworking proxy)
125. Scenarios (1/2)
• Legacy cases (legacy case 1, 2, 3, and 2+) relate to legacy
devices, referred to as “d” device (lower case d), that are
not ETSI TC M2M-compliant. These devices can be
integrated within the ETSI TC M2M architecture via an xIP
service capability where x could be N for network, G for
gateway, or D for device. xIP (NIP, GIP, DIP) is a specific
capability that makes a non-compliant device looks like an
gateway, or D for device. xIP (NIP, GIP, DIP) is a specific
capability that makes a non-compliant device looks like an
ETSI-compliant M2M device through the implementation of
the mId reference point. Note, however, that the ETSI TC
M2M specification does not say how the interworking is
done. The details of such interworking are not standardized
and are left for individual implementations.
126. Scenarios (2/2)
• Case 1 shows a D device which is defined as a device that
implements M2M SCs and runs DAs. The D device
interfaces with the M2M SCs in the network and
applications domain, making use of the mId reference point
• Case 2 shows a D' device which is an ETSI TC M2M-
compliant device but that does not implement M2M SCs.compliant device but that does not implement M2M SCs.
Instead, it relies on SCs in an M2M gateway, referred to as
“G”, via the dIa external (in this case) reference point.
• Case 2+ relates to D devices connecting to the M2M SCs in
the network and applications domain via an M2M gateway,
G. The motivation for such a case is to allow a D device to
make use of WAN connectivity but also when needed— for
example, in the case of mobile devices—reuse existing
WAN connectivity provided by a gateway.
127. ETSI M2M Service Capabilities
• Reachability, Addressing, and Repository Capability (xRAR)
is the cornerstone of the ETSI TC M2M SC work. It has
resulted from the merger of two other capabilities
introduced in the early stages of the ETSI TC M2M work:
– Device application repository: originally introduced to maintain
a record of registered DAs.a record of registered DAs.
– Naming addressing and reachability: originally introduced to
provide address translation functions and to keep track of
reachability status of devices or applications running on those
devices.
• The merging of these two capabilities, resulting in xRAR,
simplifies the structure and avoids the need for
unnecessary frequent exchanges of messages between the
two capabilities.
128. REST Architectural Style for M2M
• REST (representational state transfer) is an
architectural style defined by Roy T. Fielding in
2000.
• It is a set of principles that enables distributed• It is a set of principles that enables distributed
systems to achieve greater scalability and
allow distributed applications to grow and
change over time, thanks to the loose
coupling of components and stateless
interactions.
129. Main Concept of REST
• The main concept of REST is that a distributed application is
composed of resources, which are stateful pieces of information
residing on one or more servers.
• Regardless of their content, in REST it is possible to manipulate
resources through a uniform interface that is composed of four
basic interactions: CREATE, UPDATE, DELETE, and READ.
• Each of these operations is composed of request and response• Each of these operations is composed of request and response
messages, and, with the exception of CREATE, they are idempotent,
meaning that the end result of each operation is unchanged
regardless of how many times the operation itself is repeated.
• In other words, these operations do not have side effects, meaning
that it is possible to distribute resources and to use proxy functions.
The lack of side effects allows more efficient use of caching and
greater scalability.
130. REST Basics
• REST is an architectural style that relies heavily
on HTTP, and conceptualizes the idea of web-
accessible resources.
• A resource, in REST terms, could be any entity• A resource, in REST terms, could be any entity
that can be addressed using a HTTP URI
134. ETSI TC M2M Resource-Based M2M
Communication and Procedures
• In ETSI TC M2M, it is assumed that all three
normative reference points defined in the
M2M architecture, namely mIa, mId, and dIa,
will use REST, although there may be some
exceptions.exceptions.
• For instance, on the mId reference point,
device management is performed using
existing protocols such as BBF TR069 and OMA
DM that are RPC-based.
135. Primitives
• ETSI TC M2M did not assume that the HTTP
protocol would be the protocol to be used for
implementation, although HTTP is the natural
choice until CoAP (more adapted for constrained
devices) becomes widely deployed.devices) becomes widely deployed.
• To avoid the use of specific HTTP primitives, this
section will mostly use the four primitives:
– Create: create a resource.
– Retrieve: read the content of the resource.
– Update: write the content of the resource.
– Delete: delete the resource.
136. CRUD Methods
• Those methods are referred to as the CRUD
methods below.
• In addition to these basic methods, it is often also
useful to define methods for subscribing to a
change of a resource (S) and a notification aboutchange of a resource (S) and a notification about
a change of a resource (N) included in a more
general RESTful architecture.
• It is assumed in what follows that CRUD and SN
are applicable to the resources used in the SCL
(service capability layer).
137. Use of SCL and REST architectural style for data exchange.
Source: ETSI TS 102 690
138. Use of SCL and REST architectural style for data exchange.
Source: ETSI TS 102 690
• Step 1 shows how a DA can request that the particular
data be stored under the NSCL (network service
capability layer). Since the DA does not speak directly
with the NSCL, storing this data under the NSCL is
facilitated by the local SCL—the DSCL in this case. The
DA can either use an update or a create primitive toDA can either use an update or a create primitive to
this end.
• In Step 2, which is optional, the NSCL notifies the NA
that some data is available. This step assumes that the
NA has already subscribed to be notified when data
matching a certain criterion becomes available.
• Step 3 consists of reading the data received by the NA.
139. Closing
• A description of the capabilities for the ETSI TC M2M
Release 1 was provided along with the resource structure
and an overview of the most important procedures through
an example.
• ETSI TC M2M specifications represent an important step
forward for providing the foundation standards for aforward for providing the foundation standards for a
horizontal M2M service platform. While the initial release
mostly tackled data mediation, security, and device
management, it is expected that future releases will go the
extra mile in standardizing the other service capabilities.
• At the time of writing, ETSI M2M specifications are still
evolving, so some details may have slightly changed.
140. End of Day OneEnd of Day One
NextNext
Day Two: DeploymentDay Two: Deployment