• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
M2M Day One
 

M2M Day One

on

  • 682 views

Introduction to M2M ...

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

Statistics

Views

Total Views
682
Views on SlideShare
682
Embed Views
0

Actions

Likes
5
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    M2M Day One M2M Day One Presentation Transcript

    • Syllabus Day one : Business and ArchitecturesIntroduction to M2MWhat is M2M?The Business of M2MAccelerating M2M MaturityM2M StandardsThe Business of M2MThe M2M MarketThe M2M Market Adoption: Drivers and BarriersThe M2M Value ChainMarket Size ProjectionsBusiness ModelsM2M Business MetricsMarket EvolutionEarly M2M DeploymentsM2M Requirements and High-Level Architectural PrinciplesUse-Case-Driven Approach to M2M RequirementsSmart Metering Approach in ETSI M2MSyllabus Day Two : DeploymentM2M Optimizations in Public Mobile NetworksM2M Over a Telecommunications NetworkNetwork Optimizations for M2MThe Role of IP in M2MIPv6 for M2M6LoWPANRouting Protocol for Low-Power and Lossy Networks (RPL) CoREM2M SecurityTrust Relationships in the M2M EcosystemSecurity RequirementsWhich Types of Solutions are Suitable?Standardization Efforts on Securing M2M and MTC CommunicationsM2M Terminals and ModulesM2M Module CategorizationHardware InterfacesTemperature and Durability ServicesSmart Metering Approach in ETSI M2MeHealth Approach in ETSI M2MHigh-Level Architecture Principles for M2M CommunicationETSI M2M Services ArchitectureHigh-Level System ArchitectureETSI TC M2M Service Capabilities FrameworkETSI TC M2M Release 1 ScenariosETSI M2M Service CapabilitiesIntroducing REST Architectural Style for M2METSI TC M2M Resource-Based M2M Communication and ProceduresTemperature and Durability ServicesSoftware InterfaceCellular Certification
    • 6 April 20136 April 2013Day one : Business and ArchitecturesDay one : Business and Architectures
    • Syllabus Day one : Business and ArchitecturesIntroduction to M2MWhat is M2M?The Business of M2MAccelerating M2M MaturityM2M StandardsThe Business of M2MThe M2M MarketThe M2M Market Adoption: Drivers and BarriersThe M2M Value ChainMarket Size ProjectionsBusiness ModelsM2M Business MetricsMarket EvolutionEarly M2M DeploymentsM2M Requirements and High-Level Architectural PrinciplesM2M Requirements and High-Level Architectural PrinciplesUse-Case-Driven Approach to M2M RequirementsSmart Metering Approach in ETSI M2MeHealth Approach in ETSI M2MHigh-Level Architecture Principles for M2M CommunicationETSI M2M Services ArchitectureHigh-Level System ArchitectureETSI TC M2M Service Capabilities FrameworkETSI TC M2M Release 1 ScenariosETSI M2M Service CapabilitiesIntroducing REST Architectural Style for M2METSI TC M2M Resource-Based M2M Communication and ProceduresArief Hamdani GunawanArief Hamdani Gunawan
    • The Essence of M2M (1/2)• The role of M2M is to establish theconditions that allow– a device to (bidirectionally) exchangeinformationinformation– with a business application– via a communication network,– so that the device and/or applicationcan act as the basis for this informationexchange.
    • The Essence of M2M (2/2)• The basic way to describe M2M isshown in the “essence” of M2M.– The role of M2M is to establish theconditions that allow a device to(bidirectionally) exchange informationwith a business application via awith a business application via acommunication network, so that thedevice and/or application can act as thebasis for this information exchange.– In this definition, the communicationnetwork has a key role:a collocated application and device can hardlybe considered as having an M2M relationship.
    • Group of Devices in an M2M Relationship (1/2)• In many cases,–M2M involves a group of similardevices interacting with a singleapplication.
    • Group of Devices in an M2M Relationship (2/2)• In many cases, M2M involves a groupof similar devices interacting with asingle application.• Fleet management is an example ofsuch an application, where devices are,for example, trucks, and thecommunication network is a mobilenetwork.
    • The Mediated M2M Relationship (1/2)• In some cases,– the devices in the group may notdirectly interact with theapplication owing to having onlyapplication owing to having onlylimited capacities.• The relationship is mediated byanother device (e.g., a gateway)– that enables some form ofconsolidation of thecommunication.
    • The Mediated M2M Relationship (2/2)• In some cases, the devices in thegroup may not directly interact withthe application owing to having onlylimited capacities.• In this scenario, the relationship ismediated by another device (e.g., amediated by another device (e.g., agateway) that enables some form ofconsolidation of the communication.• “Smart metering” is an example ofsuch an application where the devicesare smart meters and thecommunication network can be amobile network or the public Internet
    • M2M area network• The term “M2M area network” has been introducedby the European Telecommunication StandardsInstitute (ETSI).• An M2M area network provides– physical and– MAC layer connectivitybetween different M2M devices connectedto the same M2M area network,thus allowing M2M devices to gain accessto a public network via a router or a gateway.
    • Characteristic• M2Ms unique characteristic is largelydue to the key role of the end-device.• Devices are not new in the world of information andcommunication technologies (ICT), butcommunication technologies (ICT), butwith M2M that market is seeing a new family ofdevices with very specific characteristics.• These characteristics are further discussed below,particularly their impact on the requirementsfor applications and networksthat have not until now been fully taken intoaccount.
    • Characteristic : Multitude• This is the most advocated change brought about byM2M.• It is generally agreed that the number of “devices”connected in M2M relationships will soon largelyexceed the sum of all those that directly interact withexceed the sum of all those that directly interact withhumans (e.g., mobile phones, PCs, tablets, etc.).• An increased order of magnitude in the number ofdevices results in significantly more pressure onapplications architectures, as well as on network load,creating in particular scalability problems on systemsthat have been designed to accommodate fewer“actors” and far greater levels and types of traffic.
    • Characteristic : Variety• There are already a particularly large number ofdocumented possible use cases for M2M that applyto a variety of contexts and business domains.• The initial implementations of M2M applicationshave already led to the emergence of a large varietyof devices with extremely diverse requirements interms of data exchange rate, form factor, computing,or communication capabilities.• One result of the wide variety is heterogeneity, whichis in itself a major challenge to interoperability.
    • Characteristic : Invisibility• This is a strong requirement in many M2Mapplications: the devices have to routinely delivertheir service with very little or no human control.• In particular, this is preventing humans fromcorrecting mistakes (and also from creating newones).• As a result, device management more than everbecomes a key part of service and networkmanagement and needs to be integrated seamlessly.
    • Characteristic : Critically• Some devices are life-savers, such as in the field ofeHealth (blood captors, fall detectors, etc.).• Some are key elements of life-critical infrastructures,such as voltage or phase detectors, breakers, etc, inthe Smart Grid.• Their usage places stringent requirements uponlatency or reliability, which may challenge or exceedthe capabilities of todays networks
    • Characteristic : Intrusiveness• Many new M2M devices are designed with theexplicit intention to “better manage” some of thesystems that deal with the end-users well-being,health, etc.• Examples are the eHealth devices alreadymentioned, smart meters for measuring and/orcontrolling electrical consumption in the home, etc.• This in turn leads to issues of privacy.
    • Specificities of M2M devices• In addition to the above-listed characteristics and theirimpact on the architecture of M2M systems, it isimportant to consider the other specificities of M2Mdevices that put additional constraints on the way theycommunicate through the network, it is important tocommunicate through the network, it is important toconsider the other specificities of M2M devices thatput additional constraints on the way theycommunicate through the network.• This may require new ways to group the devicestogether.• Among other things, devices can be:
    • Limited in functionality• Most M2M devices have computational capabilitiesseveral orders of magnitude below what is currentlypresent in a modern portable computer or a smartphone.• In particular, devices may be lack remote software• In particular, devices may be lack remote softwareupdate capabilities.• One of the main reasons for this design choice iscost, often because the business model requires verycompetitively priced devices (e.g., smart meters inmany cases).
    • Low-powered• Although many M2M devices are connected to apower network, many of them have to be powereddifferently (often on batteries) for a variety ofreasons.• 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 toa power supply (e.g., industrial process sensors,water meters, roadside captors).• This will reduce the amount of interaction betweensuch devices and the M2M applications (e.g., in thefrequency and quantity of information exchanged).
    • Embedded• Many devices are, and will be, deployed in systemswith specific (hostile, secure) operating conditionsthat will make them difficult to change without asignificant impact on the system itself.• Examples are systems embedded in buildings or incars that are hard to replace (e.g., when they aresoldered to the car engine, as is the case with someM2M devices).
    • Here to stay• Last but not least, many of the new M2M devices are andwill be deployed in non-ICT applications with verydifferent lifetime expectancy.• The rate of equipment change in many potential M2Mbusiness 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 differentbusiness models (e.g., no subsidization of devices by theoperators), to the fact that they are embedded, but alsoto the complexity of evolution of the industrial process inwhich the device is operating (e.g., criticality of theservice makes changing equipment in a electricitynetwork very difficult, which leads to long life cycle ofequipment in the field).
    • M2M World of Connected Services
    • Stages of M2M Industry Maturity
    • ChallengesDespite progress in M2M technologies,there remain many challenges,the most pressing ones being:
    • Challenges: Fragmentation1. Fragmentation of solutionsIn the vast majority of cases,the solutions developed and implementedto date have been addressingto date have been addressingspecific vertical applications requirementsin isolation from all others.
    • Challenges: Network Misalignment2. Network misalignmentAs already stated,communication networkshave been designedhave been designedwith many requirementsthat differ substantiallyfrom those of M2M.
    • Challenges: Security3. SecurityAs already outlined,some of the most promising M2 applications(eHealth, Smart Grids)(eHealth, Smart Grids)are safety-critical and must be made robustagainst a large varietyof security threats.
    • Challenges: Privacy4. PrivacyTo develop and resolvethe sensitive issue of privacy,both regulationboth regulation(an essential precondition)and standardizationare required.
    • Challenges: Service Capabilities5. Service capabilitiesIn order to deal with the fragmented market,it is necessary to outline capabilitiesthat can be reusedthat can be reusedacross several applications.
    • Challenges: Testing, certification6. Testing, certificationA large number of M2M solutionswill have to be developedoutside of the traditional service silos,outside of the traditional service silos,integrated with other M2Mor traditional applications.
    • AcceleratorsTaking 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 thatallows for the development of “non-silo,” future-proof applications.2. policy and government incentives – Based on the realization that someM2M challenges may not be addressed by the industry alone, publicauthorities and governments have started to play an active role both inM2M challenges may not be addressed by the industry alone, publicauthorities and governments have started to play an active role both instimulating the investment by setting up ambitious incentive programsand in policy-making.3. standards – A large number of credible industrial partners, large andsmall, from various industries (including but not only ICT) have started towork together in order to create the new standards required to addressM2M at the global system level.
    • Accelerating M2M Maturity:High-Level M2M Frameworks• The largest part of the challenge facing theM2M actors is to transform vertical silos into aset of easily developable and incrementallydeployable applications.deployable applications.• “Stages of M2M Industry Maturity” showsthat the transition to the phase two of M2Mmaturity will be marked by the advent anddeployment of horizontal platforms.
    • Accelerating M2M Maturity:High-Level M2M Frameworks• What is meant by “horizontal” is a coherentframework valid across a large variety ofbusiness domains, networks, and devices, thatis, a set of technologies, architectures, andis, a set of technologies, architectures, andprocesses that will enable functionalseparations, in particular application andnetwork layers, as depicted in “An M2Mchallenge: emergence of the M2M servicelayer”
    • Inverting The Pipesexisting proprietaryvertical applications…applications share common infrastructure,environments and network elements
    • An M2M challenge:emergence of the M2M service layer
    • Accelerating M2M Maturity:Policy and Government Incentives• After initial slow progress, public authorities andgovernments have now realized that they have a keyrole to play in the take-off of M2M communications,especially because M2M is an integral element in manyof the new systems that are deemed to be essential forthe future of their countries or regions.the future of their countries or regions.• Several lessons have been learnt and measures appliedin the definition of incentives regarding, in particular,the role of standards to allow for infrastructureoptimization, or the positive effect of economies ofscale and reusability of service capabilities as a majorenabler for mainstream deployments.
    • M2M Standards• Unlike in several other ICT segments where it may bepossible to deploy operational systems despite a lack ofstandards, several M2M market segments demand strongstandards to ensure long-term investment protection.• For several M2M applications, including smart metering orSmart Grids, there is an expectation that the installedSmart Grids, there is an expectation that the installedequipment will be deployed for more than 20 years.• While such a lifetime may appear unrealistic (or at leastunusual) for traditional Telco deployments, theinfrastructures deployed by utilities have very longdeployment cycles that could dramatically influence theirdesign and henceforth the related standards.
    • M2M Standards Landscape
    • ZigBee alliance• A set of specifications of communicationprotocols (but also data models) using smalllow-power radio devices based on the IEEE802.15.4.802.15.4.• Target applications include switches withlamps, electricity meters with in-homedisplays, consumer electronics equipment,etc.
    • KNX• A purpose-built radio frequency standarddeveloped 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 EuropeanStandard (CENELEC EN 50090 and CEN EN13321-1) and Chinese Standard (GB/Z 20965).
    • Home grid• Based on the ITU-T specification suite knownas G.hn that is designed to providecommunications within the homeenvironment, making use of existing wiresenvironment, making use of existing wiressuch as powerline, coax cable or copper pairs.
    • IETF protocol suite• Based on 802.15.4 providing a specificationfor L1 and L2 WPAN, the IETF has developed aset of protocols aimed at bringing native IPsupport to constrained devicesupport to constrained device
    • Syllabus Day one : Business and ArchitecturesIntroduction to M2MWhat is M2M?The Business of M2MAccelerating M2M MaturityM2M StandardsThe Business of M2MThe M2M MarketThe M2M Market Adoption: Drivers and BarriersThe M2M Value ChainMarket Size ProjectionsBusiness ModelsM2M Business MetricsMarket EvolutionEarly M2M DeploymentsM2M Requirements and High-Level Architectural PrinciplesUse-Case-Driven Approach to M2M RequirementsSmart Metering Approach in ETSI M2MeHealth Approach in ETSI M2MHigh-Level Architecture Principles for M2M CommunicationETSI M2M Services ArchitectureHigh-Level System ArchitectureETSI TC M2M Service Capabilities FrameworkETSI TC M2M Release 1 ScenariosETSI M2M Service CapabilitiesIntroducing REST Architectural Style for M2METSI TC M2M Resource-Based M2M Communication and ProceduresMuhammad Ary MurtiMuhammad Ary Murti
    • The Business of M2MM2M: Architecture and ApplicationsBTP, Bandung, 6-7 April 2013.Muhammad Ary Murtim_ary_murti@ieee.org
    • 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 Deploymentsm_ARy_murti@ieee.org, 6-7 April 2013
    • The M2M MarketThe M2M Marketm_ARy_murti@ieee.org, 6-7 April 2013
    • ICT arena is changing very quickly• about a decade ago, headlines weredominated by companies like Vodafone,Orange, Telefonica, Nokia, Ericsson, Siemens,etcetc• today, headlines are only dominated bycompanies like Google, Apple, Facebook• ICT infrastructures and technologies havebeen sidelined to facilitators/enablers!m_ARy_murti@ieee.org, 6-7 April 2013
    • A few additional observations fromthese latest trends• whoever provides only hardware & infrastructure isloosing out on the long run being close to the user (orto the problem) is paramount (see Apple’s iPhone)• allowing for true scalability via ability for 3rd parties tocapitalize on entire system, i.e. hardware and softwarecapitalize on entire system, i.e. hardware and softwareand services, is key (see App Store concept which SteveJobs by the way was against)• having a hand on the data is absolute key (see Googlewho search, but also IBM who store, Cisco who route,etc)m_ARy_murti@ieee.org, 6-7 April 2013
    • Popular M2M Marketsm_ARy_murti@ieee.org, 6-7 April 2013
    • M2M solutions deliver many compelling benefitsMeasures that drive investments in M2M vary greatly acrossdifferent industries and applicationsSource: Harbor Research, Inc., September 2010m_ARy_murti@ieee.org, 6-7 April 2013
    • Identifying the Potential of the e-Health VerticalUser types:–Personal fitness/health–Worried wells–Telemedicine–First responders–Connected medical environments–Connected medical environments–Remote monitoring–Assisted living–TrialsThese user types are projected tohave roughly 774 million connecteddevices by 2020Source: Machina Researchm_ARy_murti@ieee.org, 6-7 April 2013
    • Growing Cellular M2M MarketPredictions on M2M LTE:• minor market until 2014• 2.5% (1.7M) of total M2Mmarket• LTE module = twice 3GcostcostPredictions on Automotive:• primary market on M2Mcellular• unique (short-term)market for M2M LTEm_ARy_murti@ieee.org, 6-7 April 2013
    • • The M2M Value Chain• M2M Business Metrics• Business Models• Business Modelsm_ARy_murti@ieee.org, 6-7 April 2013
    • ETSI: TC M2M Architecturem_ARy_murti@ieee.org, 6-7 April 2013
    • ETSI: TC M2M Architecturem_ARy_murti@ieee.org, 6-7 April 2013
    • M2M Supply Chain• Telecom operator• MNVO (mobile virtual network operator)• MVNE (Mobile Virtual Network Enabler)• Satellite operator• Telecom software vendor / ISV• Telecom software vendor / ISV• Cloud services provider• Telecom equipment vendor• Device. module, chipset maker• Integrator / consultancym_ARy_murti@ieee.org, 6-7 April 2013
    • Value shift• Today, CSPs are doing what they do easily andvery well– selling connectivity. This representsalmost 90% of M2M revenue in the currentmarket• Tomorrow, certainly within three years – revenue• Tomorrow, certainly within three years – revenuedistribution will make an inexorable shift to whatend users want to do with M2M:— Support business decisions with M2M dataintelligence.— Secure and manage M2M data.— Identify and create new applications for M2M.m_ARy_murti@ieee.org, 6-7 April 2013
    • Value shiftm_ARy_murti@ieee.org, 6-7 April 2013
    • Revenue models• “To avoid being a bit pipe, operators must find away to play a greater role. The only way forwardis to develop partnerships with M2M developersbased on revenue sharing.” – Operator, EasternEuropeEurope— 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
    • Operational focus areas for M2M service providersm_ARy_murti@ieee.org, 6-7 April 2013
    • WAN Dominates the Wireless Connection SpaceMobile networks areexpected to hostroughly 86 millionconnections• Fixed installations• Fixed installationsare usually shortrange to a home hub• Greater demand formobility, faster dataspeeds and remotemonitoringSource: Machina Researchm_ARy_murti@ieee.org, 6-7 April 2013
    • M2M Module Price ComparisonSource: Harbor Research, Inc., September 2010m_ARy_murti@ieee.org, 6-7 April 2013
    • M2M mobile traffic revenues by service typeMNOs to Realize Revenues in the BillionsSource: Machina Researchm_ARy_murti@ieee.org, 6-7 April 2013
    • M2M mobile traffic revenues by M2M playere-Health is a Good Opportunity for Many PlayersSource: Machina Researchm_ARy_murti@ieee.org, 6-7 April 2013
    • New Dynamics for M2M (1 of 3)m_ARy_murti@ieee.org, 6-7 April 2013
    • New Dynamics for M2M (2 of 3)m_ARy_murti@ieee.org, 6-7 April 2013
    • New Dynamics for M2M (3 of 3)m_ARy_murti@ieee.org, 6-7 April 2013
    • Top 10 things you need to know1. The total opportunity will be huge2. Addressing the opportunity requires tailoredsolutions3. Impossible for one company to serve all3. Impossible for one company to serve allverticals: partnerships will abound4. Traffic: M2M (generally) does not need new,high capacity networks5. QoS guarantees may be pre-requisite forsome industrial applicationsm_ARy_murti@ieee.org, 6-7 April 2013
    • Top 10 things you need to know6. Energy and e-Health are the targets forinvestment7. Distribution channels, billing, brand, etc. areall significant assets for MNOsall significant assets for MNOs8. MNOs can increase margins with networkcapabilities9. Revenues for a wide range of industry players10. The industry is in a period of disruptionm_ARy_murti@ieee.org, 6-7 April 2013
    • Key Question:“How to make money with IoT?”m_ARy_murti@ieee.org, 6-7 April 2013
    • Starting with a Customer Centric Viewto Develop the Value Propositionm_ARy_murti@ieee.org, 6-7 April 2013
    • What is it others want?- The Value PropositionNeeds – How do you get access to thecustomer?• listen to your customer carefully before andduring the design• pick him up and accompany him to Needsgrowing with himProduct - 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
    • What the Customers Expect from UsThe results of the customer insights (interviews) strongly influence productdesign (customer experience design) and thus the business model.m_ARy_murti@ieee.org, 6-7 April 2013
    • One technical solution – two very different productsAllianz: Crash Recorder versus Help BoxThe whole is more than the sum of its parts.m_ARy_murti@ieee.org, 6-7 April 2013
    • Fleshing out the Business Model looking at theinteractions between the blocksm_ARy_murti@ieee.org, 6-7 April 2013
    • Many individuals need to be reachedMany individual needs need to be reachedm_ARy_murti@ieee.org, 6-7 April 2013
    • Key success factorsm_ARy_murti@ieee.org, 6-7 April 2013
    • The five critical M2M success factors for CS P success[Source: Analysys Mason, 2012]m_ARy_murti@ieee.org, 6-7 April 2013
    • Recommendations forcommunication service providers (CSPs)• Combine partnership, resale, and acquisitionmodels to bring M2M solutions to market. The go-to-market approach for each CSP will vary according to specific competencies, but sales of a more end-to-endsolution 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 revenueand profitability metrics. There are more M2M applications in the enterprise andconsumer worlds than may be addressed profitably. Pick the top solutions andconsumer worlds than may be addressed profitably. Pick the top solutions andfocus your resources.• Dedicate human resources to an M2M business unitTreat M2M like a start-up business unit and dedicate staff and budget to thegroup. Reconsider the placement of human resources – whether in corporatefunctions 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 whichcommunications – with growing emphasis on mobility – and IT overlap. It will beimportant in creating an M2M identity for a CS P to understand the enterprise ITbuyer’s impressions of its overall enterprise capabilities.m_ARy_murti@ieee.org, 6-7 April 2013
    • Early M2M Deploymentsm_ARy_murti@ieee.org, 6-7 April 2013
    • Vehicle Tracking Systemm_ARy_murti@ieee.org, 6-7 April 2013
    • M2M at Sea• Most of the world’s cargo transportation needs are• Most of the world’s cargo transportation needs areserved by ocean transport, yet these vast areashave been cut off from communication, as nonetwork has been able to supply connectivity• With Ericsson’s technology, vessel fleets in themiddle of the ocean are essentially running their ownwireless networks via satellite uplink.m_ARy_murti@ieee.org, 6-7 April 2013
    • M2M at Sea• AchievingBenefits Acrossthe Sea• Making• MakingContainers Smart• CreatingIndustry-WideEfficienciesm_ARy_murti@ieee.org, 6-7 April 2013
    • M2M at SeaAchievingBenefits Acrossthe 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 remoteexpertise, resulting in extended access to information and, in turn, improvedefficiency in vessels’ daily operations.•Shipping companies will have real-time access to information about vesseloperation, bunker fuel consumption, and electric conditions. They will also beable to monitor and prevent any difficulties in systems on board before theyhappen.•One of the primary benefits for shipping companies will come from their abilityto proactively manage bunker consumption through real-time data, which willcreate significant operational savings.m_ARy_murti@ieee.org, 6-7 April 2013
    • M2M at Sea• MakingContainers 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 adock in a port.•Once docked, the device connectivity of containerswill switch to a local operator network so that thetracking can continue when the next leg of truckingtransportation begins.m_ARy_murti@ieee.org, 6-7 April 2013
    • M2M at Sea• CreatingIndustry-WideEfficiencies• Machine-to-machine (M2M) solutions, such as the one• Machine-to-machine (M2M) solutions, such as the onedescribed here, will help shipping companies employ newand efficient ways of addressing fleet management.• This technology will help manage delivery times, improveinteraction with vessels, and increase the efficiency of theglobal supply chain. Shipping companies will be able toproactively resolve issues, promptly share information withcustomers, and even improve energy efficiencym_ARy_murti@ieee.org, 6-7 April 2013
    • Speed Up Traffic with M2MImproving logistics in the Port of Hamburg• second largest port in Europe, the size of 7,000soccer fields and welcomes up to 40,000 trucks aday, each carrying six or twelve containers.• Physical expansion was not an option, since thecity 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 verylimited ability to expand.• What was needed was an efficient trafficmanagement system.m_ARy_murti@ieee.org, 6-7 April 2013
    • • partnered with SAP and Deutsche Telekom in its SmartPort Logistics pilot project. During an initial three-month trial, 30 trucks were fitted withtabletsconnected to the prototype Smart Port LogisticsSystem.• The system receives and integrates three sources ofSpeed Up Traffic with M2MImproving logistics in the Port of Hamburg• The system receives and integrates three sources ofinformation in real time:1. traffic information;2. infrastructure information, including parking and thestatus of tunnels and moving bridges;3. location of participating trucks approaching or withinthe Port of Hamburg.m_ARy_murti@ieee.org, 6-7 April 2013
    • Smart Port LogisticsDrivers receive automated, personalized text-based messages with relevant traffic informationand 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 theirtransport orders in real time.waiting times for trucks will decrease, and there will be fewer traffic jams within the port areaand on the approach roads.m_ARy_murti@ieee.org, 6-7 April 2013
    • Terima Kasihm_ARy_murti@ieee.org, 6-7 April 2013
    • Syllabus Day one : Business and ArchitecturesIntroduction to M2MWhat is M2M?The Business of M2MAccelerating M2M MaturityM2M StandardsThe Business of M2MThe M2M MarketThe M2M Market Adoption: Drivers and BarriersThe M2M Value ChainMarket Size ProjectionsBusiness ModelsM2M Business MetricsMarket EvolutionEarly M2M DeploymentsM2M Requirements and High-Level Architectural PrinciplesUse-Case-Driven Approach to M2M RequirementsUse-Case-Driven Approach to M2M RequirementsSmart Metering Approach in ETSI M2MeHealth Approach in ETSI M2MHigh-Level Architecture Principles for M2M CommunicationETSI M2M Services ArchitectureHigh-Level System ArchitectureETSI TC M2M Service Capabilities FrameworkETSI TC M2M Release 1 ScenariosETSI M2M Service CapabilitiesIntroducing REST Architectural Style for M2METSI TC M2M Resource-Based M2M Communication and ProceduresArief Hamdani GunawanArief Hamdani Gunawan
    • M2M Requirements and High-Level Architectural Principles• Most standards organizations, including 3GPP, 3GPP2, andETSI, have adopted a use-case-driven approach as a meanswith which to derive the set of requirements that furtherdefine the service architecture. ETSI, however, has adopteda 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 veryclear that all network optimization matters, bothequipment features and the design or operationalnetworks, also have to take into account fundamentalcharacteristics of M2M-generated traffic and growthpatterns.• Both issues put forward new and particularly challengingrequirements on the access and core network
    • What is a Use Case?• The term use case is very commonly used.However, a commonly agreed definition is moredifficult to find. The Object Management Group(OMG) provides an excellent definition and(OMG) provides an excellent definition andapproach regarding the description of use cases.• According to the OMG, a use case describes theinteractions between one or more actors on theone hand and the system under consideration onthe other.
    • ETSI M2M Work on Use Cases• The ETSI Technical Committee (TC) M2M wascreated in January 2009 and aims to providean end-to-end view of M2M communicationarchitecture.architecture.• This end-to-end view does not mean that allelements of an M2M system are specified byETSI TC M2M.
    • ETSI M2M Specifications Work
    • Typical deployment scenario of smart metering systems
    • 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 casedescribes occasions where the pre-payment functionality is managedlocally on the smart metering information system as well as instanceswhere 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 theorganization 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 meteringinformation system assets (e.g., meters communication devices, smartmetering gateway)
    • Technical Report
    • e-Health
    • eHealth: Portable Sensors
    • eHealth Approach in ETSI M2M:General Use Case Description• In a remote patient monitoring scenario where lowvoltage body signals need to be acquired for remotehealth monitoring purposes, the acquisition processcould 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 nearestco-located radio parts of the same M2M device.• Where the health monitoring process is continuouslyapplied to the patient, for example, discoveringarrhythmias, the acquisition activity could be disruptedby typical cellular radio communication activitiesperformed by the M2M device
    • eHealth Approach in ETSI M2M:Stakeholders: Patient• The patient may be any individual or surrogatewho could use a remote monitoring device(RMD) to gather measurements, data, orevents.• The patient measurements may be taken invarious clinical settings, such as a hospital, ornon-clinical settings, such as at home, at work,at school, while traveling, or in assisted-livingfacilities.
    • eHealth Approach in ETSI M2M:Stakeholders: Remote Monitoring Device (RMD)• An electronic M2M device with a sensor, userinterface and/or actuator, and an interfaceinto the M2M network.• The device collects patient information and• The device collects patient information andcommunicates to the appropriate M2Mservice-capability provider and/or M2Mapplication via the M2M network.• An RMD may also communicate with theseentities via an M2M gateway.
    • eHealth Approach in ETSI M2M:Stakeholders: M2M service capability provider• A network entity that provides M2Mcommunication services to the M2Mapplication entities.• These applications may support specific• These applications may support specificfunctional capabilities that assist in facilitatinghealth information-exchange activities.• Additionally, the M2M service-capabilityprovider communicates with the RMD tocollect data or send commands.
    • eHealth Approach in ETSI M2M:Stakeholders: M2M application entity• A term created to bundle together, and treat as a singlesystem element, stakeholders above the M2M scope.• High-level applications such as free-standing orgeographic health information exchanges, data analysiscenters, integrated care-delivery networks, providercenters, integrated care-delivery networks, providerorganizations, health record banks, or public healthnetworks, and/or specialty networks are all examplesof M2M application entities.• The term M2M application entity also includes thefollowing typical RPM stakeholders.
    • High-Level Architecture Principlesfor M2M Communications• Lessons have been learned from early M2Mdeployments.• First, vertically integrated applications are hard todevelop, deploy and test.Not only do these need to deal with the application– Not only do these need to deal with the applicationbusiness logic, but they must also include a largenumber of network-aware functionalities.– Looking at the M2M applications requirements, it isclear that they all rely on a set of similar buildingblocks, particularly when it comes to all aspectsrelated to communications and underlying networks
    • High-Level Architecture Principlesfor 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 consumerhandsets such as smart phones.– However, all analysts agree that the number of– However, all analysts agree that the number ofdeployed M2M devices will be an order of magnitudehigher than personal communication devices.– As a result, the network has to become M2M-awareand take advantage of all traffic characteristics ofM2M in order to provide the level of scaling and costthat matches projected M2M devices and ARPUstructure.
    • M2M from initial to mainstream deployments
    • Simplified M2M Architecture
    • …based on Existing Technologies
    • Closing• It clearly shows that M2M imposes very specificrequirements on the network in order to achievelower investment and operational costs thatmatch ARPU constraints imposed by M2Mcommunications.communications.• Such a horizontal platform also provides easieraccess to network enablers, such as location,QoS, and addressing, which would otherwise bedifficult to access because of the multiplicity ofinterfaces and the complexity involved in buildingbusiness relationships with multiple operators.
    • Syllabus Day one : Business and ArchitecturesIntroduction to M2MWhat is M2M?The Business of M2MAccelerating M2M MaturityM2M StandardsThe Business of M2MThe M2M MarketThe M2M Market Adoption: Drivers and BarriersThe M2M Value ChainMarket Size ProjectionsBusiness ModelsM2M Business MetricsMarket EvolutionEarly M2M DeploymentsM2M Requirements and High-Level Architectural PrinciplesUse-Case-Driven Approach to M2M RequirementsSmart Metering Approach in ETSI M2MSmart Metering Approach in ETSI M2MeHealth Approach in ETSI M2MHigh-Level Architecture Principles for M2M CommunicationETSI M2M Services ArchitectureHigh-Level System ArchitectureETSI TC M2M Service Capabilities FrameworkETSI TC M2M Release 1 ScenariosETSI M2M Service CapabilitiesIntroducing REST Architectural Style for M2METSI TC M2M Resource-Based M2M Communication and ProceduresArief Hamdani GunawanArief Hamdani Gunawan
    • Typical components of a horizontal M2M service platform
    • ETSI M2M Network
    • ETSI M2M Network Architecture
    • High-level system architectureETSI TS 102 690
    • M2M High Level System Overview
    • M2M High Level System
    • Technical Specification
    • M2M service capabilities functional architecture framework
    • 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
    • Service capabilities functional architecture framework
    • Device Types (1/2)The following device types• Gateway (G) is an ETSI M2M device specialized todirectly manage M2M area networks of ETSI M2Mdevices; the gateway directly communicates with anETSI 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 directlycommunicate with an ETSI M2M core network or withan ETSI M2M gateway.• Device (D) is an ETSI M2M device that does notimplement ETSI M2M SCs. It interacts indirectly withthe M2M core via the use of SCs in the M2M gateway(G).
    • Device Types (2/2)• Gateway (G) is an ETSI M2M gateway that providesconnectivity to both D and D devices. Note that G isnot handled within the ETSI TC M2M Release 1specification.• Additionally, there is a non-ETSI M2M-compliant device(d) belonging to an M2M area network managed by anETSI M2M compliant device or gateway entities. The(d) type devices cannot access M2M SCs directly.However, interworking with ETSI-compliant entities ispossible via the xIP (interworking proxy)
    • Scenarios (1/2)• Legacy cases (legacy case 1, 2, 3, and 2+) relate to legacydevices, referred to as “d” device (lower case d), that arenot ETSI TC M2M-compliant. These devices can beintegrated within the ETSI TC M2M architecture via an xIPservice capability where x could be N for network, G forgateway, or D for device. xIP (NIP, GIP, DIP) is a specificcapability that makes a non-compliant device looks like angateway, or D for device. xIP (NIP, GIP, DIP) is a specificcapability that makes a non-compliant device looks like anETSI-compliant M2M device through the implementation ofthe mId reference point. Note, however, that the ETSI TCM2M specification does not say how the interworking isdone. The details of such interworking are not standardizedand are left for individual implementations.
    • Scenarios (2/2)• Case 1 shows a D device which is defined as a device thatimplements M2M SCs and runs DAs. The D deviceinterfaces with the M2M SCs in the network andapplications 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 inthe network and applications domain via an M2M gateway,G. The motivation for such a case is to allow a D device tomake use of WAN connectivity but also when needed— forexample, in the case of mobile devices—reuse existingWAN connectivity provided by a gateway.
    • ETSI M2M Service Capabilities• Reachability, Addressing, and Repository Capability (xRAR)is the cornerstone of the ETSI TC M2M SC work. It hasresulted from the merger of two other capabilitiesintroduced in the early stages of the ETSI TC M2M work:– Device application repository: originally introduced to maintaina record of registered DAs.a record of registered DAs.– Naming addressing and reachability: originally introduced toprovide address translation functions and to keep track ofreachability status of devices or applications running on thosedevices.• The merging of these two capabilities, resulting in xRAR,simplifies the structure and avoids the need forunnecessary frequent exchanges of messages between thetwo capabilities.
    • REST Architectural Style for M2M• REST (representational state transfer) is anarchitectural style defined by Roy T. Fielding in2000.• It is a set of principles that enables distributed• It is a set of principles that enables distributedsystems to achieve greater scalability andallow distributed applications to grow andchange over time, thanks to the loosecoupling of components and statelessinteractions.
    • Main Concept of REST• The main concept of REST is that a distributed application iscomposed of resources, which are stateful pieces of informationresiding on one or more servers.• Regardless of their content, in REST it is possible to manipulateresources through a uniform interface that is composed of fourbasic 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 responsemessages, and, with the exception of CREATE, they are idempotent,meaning that the end result of each operation is unchangedregardless of how many times the operation itself is repeated.• In other words, these operations do not have side effects, meaningthat it is possible to distribute resources and to use proxy functions.The lack of side effects allows more efficient use of caching andgreater scalability.
    • REST Basics• REST is an architectural style that relies heavilyon 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 entitythat can be addressed using a HTTP URI
    • Addressing a REST resource
    • Proxy caching the temperature value
    • Sensor updating its samples using HTTP PUT
    • ETSI TC M2M Resource-Based M2MCommunication and Procedures• In ETSI TC M2M, it is assumed that all threenormative reference points defined in theM2M architecture, namely mIa, mId, and dIa,will use REST, although there may be someexceptions.exceptions.• For instance, on the mId reference point,device management is performed usingexisting protocols such as BBF TR069 and OMADM that are RPC-based.
    • Primitives• ETSI TC M2M did not assume that the HTTPprotocol would be the protocol to be used forimplementation, although HTTP is the naturalchoice until CoAP (more adapted for constraineddevices) becomes widely deployed.devices) becomes widely deployed.• To avoid the use of specific HTTP primitives, thissection 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.
    • CRUD Methods• Those methods are referred to as the CRUDmethods below.• In addition to these basic methods, it is often alsouseful to define methods for subscribing to achange of a resource (S) and a notification aboutchange of a resource (S) and a notification abouta change of a resource (N) included in a moregeneral RESTful architecture.• It is assumed in what follows that CRUD and SNare applicable to the resources used in the SCL(service capability layer).
    • Use of SCL and REST architectural style for data exchange.Source: ETSI TS 102 690
    • 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 particulardata be stored under the NSCL (network servicecapability layer). Since the DA does not speak directlywith the NSCL, storing this data under the NSCL isfacilitated by the local SCL—the DSCL in this case. TheDA can either use an update or a create primitive toDA can either use an update or a create primitive tothis end.• In Step 2, which is optional, the NSCL notifies the NAthat some data is available. This step assumes that theNA has already subscribed to be notified when datamatching a certain criterion becomes available.• Step 3 consists of reading the data received by the NA.
    • Closing• A description of the capabilities for the ETSI TC M2MRelease 1 was provided along with the resource structureand an overview of the most important procedures throughan example.• ETSI TC M2M specifications represent an important stepforward for providing the foundation standards for aforward for providing the foundation standards for ahorizontal M2M service platform. While the initial releasemostly tackled data mediation, security, and devicemanagement, it is expected that future releases will go theextra mile in standardizing the other service capabilities.• At the time of writing, ETSI M2M specifications are stillevolving, so some details may have slightly changed.
    • End of Day OneEnd of Day OneNextNextDay Two: DeploymentDay Two: Deployment