Machine to Machine Communications (M2M)

1
Machine to Machine Communications(M2M)
Global Standards Collaboration (GSC) 14
DOCUMENT GSC14-PLEN-014
FOR Presentation
SOURCE TIA
AGENDA ITEM PLEN Agenda Item 7 NNT Machine-To-Machine
CONTACT(S) Anil Kripalani, TIA DEL, WirefreeCom (akripalani_at_WirefreeCom.net)

• Anil Kripalani, TIA

2
The Need For M2M/Smart Embedded Device
Communications Standards

• The pervasive network of intelligent and
  connected devices is coming
• The Internet of Things (source EC Commissioner
  Redding)
• THE Smarter Planet (source IBM)
• Grouping all under Machine-to-Machine (M2M)
  communications neglects recognition of the need
  for interoperable interfaces that enable
  intelligence gathering and associated action for
  different uses
• Recognize market segments and industry verticals
• With higher-level business intelligence and asset
  management applications
• Requiring support for a variety of devices,
• Allowing a variety of connectivity media
• e.g., Smart buildings and power meters may be
  connected through the power transmission lines,
  WIFI, Wired or Wireless broadband services
• Deliver event-based information reliably to a
  higher-level entity (in the Cloud)
• Immense market opportunity for wired and wireless
  devices
• Suggest Smart Embedded Device Communications
  may be a more encompassing category/label for
  this emerging HIS
• Includes categories of Consumer Electronics and
  Telematic Devices, besides Autonomous M2M
• Need standards For Smart Embedded Device
  Communications

Source Fred Yentz, CEO, ILS Technologies,
Private Communication, June 2009
3
Some PSOs have already recognized this need for
Standards

• ETSIs M2M ad hoc group delivered Conclusions and
  Results to ETSI Board
• ETSI/B69(08)29r1
• Conclusions from ETSI Report
• Many disjointed or vertical industry standardized
  solutions
• No group looking at the end-to-end view
• Nobody dealing with end-to-end interoperability
• Need to interface different wireless sensor
  capillary networks with existing wide-area
  networks
• Gateway and API standardization required
• Operators need standardization to avoid
  implementing many vertical solutions
• Operators currently developing value-added
  end-to-end solutions
• Need an ETSI Technical Committee for M2M
  standardization
• Proposal for ETSI TC M2M developed by ad-hoc
  group
• Board requested to approve the creation of a TC
  M2M
• Source ETSI input to TIA for the NNT

4
New ETSI TC M2METSI/B69(08)27

• TC M2M shall have responsibility (copied from
  Draft ToR)
• to collect and specify M2M requirements from
  relevant stakeholders
• to develop and maintain an end-to-end overall
  high-level architecture for M2M
• to identify gaps where existing standards do not
  fulfil the requirements and provide
  specifications and standards to fill these gaps,
  where existing standards bodies or groups are
  unable to do so
• to provide the ETSI main centre of expertise in
  the area of M2M
• to coordinate ETSIs M2M activity with that of
  other standardization groups and fora.
• 13 ETSI Members supporting
• Airbiquity Incorporated, Alcatel-Lucent,
  Cinterion, Cisco, France Telecom, Freescale,
  Gemalto, Orange SA, Telecom Italia, Telefonica,
  Telenor, Telit, Wavecom
• Chairman
• Mrs. Marylin Arndt, Orange S.A.

5
Smart Embedded Devices / M2M Industry Segments
A Growing List

• Industry Automation and Monitoring
• Telemedicine and Healthcare ICT
• Security and Surveillance
• Utility Metering and Telemetry
• Asset Tracking
• Fleet Management
• Consumer Telematics
• Advertising
• Consumer Applications
• Wireless Data Modules (embedded)

6
Industry Segments For Embedded Communications
Modules

• Industrial Automation and Monitoring
• Factory Line Equipment Operation/Usage
  Tracking/Diagnostics/Service requests,
• Telemedicine and Healthcare ICT
• Body Sensor and Diagnostic Reporting
• Remote Physician consultation (non-voice, patient
  vitals/xray data access)
• Security and Surveillance
• Home and enterprise security sensor monitoring,
  alerts, remote access thermostat control, video
  feeds
• Telemetry
• Smart Meters, Sensors for energy industry,
• Asset Tracking
• Inventory control, Geo-fencing
• Fleet Management
• location and availability, Repossession and
  lockdown, Sales Force Tracking
• Consumer Telematics
• In-vehicle entertainment/navigation, remote
  Diagnostics/Safety/Concierge Services, Vehicle
  Diagnostics
• Advertising
• Digital billboards, in-store offers, special
  events
• Consumer Applications
• Home monitoring, Financial and Retail POS/Kiosks

Source Requirements for Embedded CDMA Modules
and Specialty Devices, CDG Document 176 V1,
Chintan Turakhia et al, to be published
7
Smart Embedded Device Communications Types Of
Devices - 1

• Autonomous M2M Applications
• These devices typically communicate autonomously
  with other machines connected to the Internet, or
  directly.
• The device would typically be single-function
• There will usually be no end-user interaction
  with the device itself
• Would support monitoring, tracking, autonomous
  management, feedback/reporting
• These devices will typically be stationary, not
  nomadic
• Examples Industrial Automation, Smart Meters,
  Home automation controllers, Automated Meter
  Infrastructure, Security and Surveillance,
  Point-of-Sale machines, etc

Source Requirements for Embedded CDMA Modules
and Specialty Devices, CDG Document 176 V1,
Chintan Turakhia, Doug Martel et al, to be
published, 2009
8
Smart Embedded Device Communications Types Of
Devices - 2

• Consumer Electronic (CE) Applications
• These devices would communicate with application
  servers and other CE devices connected to the
  Internet through autonomous or user-initiated
  mechanisms.
• These devices would perform multiple functions
  depending on the type of device.
• There may be significant end-user interaction
  with the device itself.
• These devices can be stationary and/or nomadic.
• Examples Digital cameras, e-book readers,
  netbooks and tablet PCs, digital media players,
  and gaming devices. Special attention to
  Healthcare ICT devices

Source Requirements for Embedded CDMA Modules
and Specialty Devices, CDG Document 176 V1,
Chintan Turakhia, Doug Martel et al, to be
published, 2009
9
Smart Embedded Device Communications Types Of
Devices - 3

• Telematic and Public Safety Applications
• These devices will typically communicate with
  application servers connected to the Internet or
  emergency services personnel and first
  responders.
• These devices would perform autonomous functions
  such as vehicle diagnostics, location tracking,
  or crash incident reporting, as well as
  user-initiated functions such as vehicle
  navigation, and concierge services.
• There will be some end-user interaction with the
  device itself.
• These devices will typically be nomadic
• They may require support for inter-operator
  wireless roaming.
• Examples Vehicle diagnostics, Navigation, and
  Asset Tracking

Source Requirements for Embedded CDMA Modules
and Specialty Devices, CDG Document 176 V1,
Chintan Turakhia, Doug Martel et al, to be
published, 2009
10
Smart Embedded Device Communications Standards

• Like ETSI an interest in TIA for developing
  interoperability and interface standards for
  Smart Embedded Devices (SED)
• Partitioning of wide array of market segments to
  manage standards definition
• Healthcare monitoring, surveillance, industrial
  automation, telematics are the highest interest

11
Highlight of Current Activities

• CDG and 3GPP2 TSG-C are developing specifications
  for embedded devices covering
• Service Requirements
• Wireless connectivity only
• Reuse of existing air interfaces (cdma2000 1X
  data, 1XEV-DO data)
• Position Location Requirements
• Data Service Requirements
• Security Aspects
• Broader treatment of this area should include all
  applicable wireless and wired connectivity means

12
Key System Aspects

• Combination of services (e.g., data, and LBS)
  that an application/device can potentially use
• For common communications modules, various
  applications will utilize the embedded module
  differently
• Best practices and considerations such as network
  loading, end-user throughput, and connection
  delays should be taken into account when
  implementing an application
• Power Efficiency for Polled Devices, for Periodic
  Update Devices, for Continuous Monitoring Devices
• Security architecture

13
Strategic Direction

• TIA will be working with 3GPP2 and CDG to develop
  interoperability standards for Embedded Devices,
  encompassing Autonomous M2M, as well as Consumer
  Devices that operate with user interaction, also
  Telematics and Public Safety Devices
• Collaboration needed with ITS, the Wireless
  Healthcare fora, the Energy Technology interest
  groups, the Smart Buildings modeling groups, the
  Smart Grid initiative, OPC (Open Connectivity in
  industrial automation http//www.opcfoundation.org
  / )

14
Challenges

• Extremely broad scope of applicability, across
  many industry segments
• To develop efficient protocols
• Potential deployment numbers targeted in billions
• Standards development to be driven by market
  opportunity
• To remove/minimize fragmentation of standards
• To reuse what works and is licensed (e.g., in
  wireless)
• Standards development to be responsive to market
  needs
• Not years

15
Next Steps/Actions

• Begin specifying detailed North American
  requirements for higher priority industry
  segments, system architecture for standards
  development
• Collaborate with other SDOs to avoid fractured
  ecosystems and disparate interfaces
• Given the interest in at least two PSOs already,
  TIA and ETSI, should this be a HIS for GSC-15?

16
Supplementary Slides
17
The Smart Embedded Device (SED)
Communications Requirements

• The Smart Embedded Device becomes a point of
  convergence.
• The Smart Embedded Device must be able to
  identify events from the set of data they collect
  and act on
• The Smart Embedded Device must be able to respond
  to a query from the network and higher level
  systems regarding heath and status of the device.
• The Smart Embedded Device must be able to provide
  native connectivity to the information processing
  points in the application stack
• The Smart Embedded Devices allow the real time
  physical domain to communicate simply and
  natively with the higher level systems.

18
SED/M2M Operational Requirements Wireless
Frequency Bands /modes

• Wireless standards being addressed by CDG / 3GPP2
  for use with Embedded Devices

Wireless Technology Frequency Band
CDMA IS-856/IS-2000/IS-95A, Band Class 0 800MHz (A and B bands)
CDMA IS-856/IS-2000/IS-95A, Band Class 0 800MHz Korean Cellular (channel support 1011 - 779)
CDMA IS-856/IS-2000/IS-95A, Band Class 1 1900MHz
CDMA IS-856/IS-2000/IS-95A Band Class 5/11 450MHz
CDMA IS-856/IS-2000/IS-95A Band Class 6 2100MHz

• Other wireless standards to be considered at a
  later stage

19
SED/M2M Communications Standards Requirements

• The common requirements that are applicable to
  all wireless devices include
• Frequency Bands/Modes
• Mobile Station Class
• External Interfaces
• Antenna
• System Selection and PRL
• Roaming
• Information Encoding and presentation
• OTA Provisioning Functions
• NAM Requirements
• AT Commands
• Conformance Tests
• Debug Menus

Source Requirements for Embedded CDMA Modules
and Specialty Devices, CDG Document 176 V1,
Chintan Turakhia, Doug Martel et al, to be
published, 2009
20
Functional Components of the Framework

• From ETSI supplemental inputs to NNT.
• The high level illustration of M2M systems and of
  its components as given in the Figure 1

21
M2M System Abstraction

• From ETSI supplemental inputs to NNT.
• The functional components of the high level
  architecture may be isolated and abstracted as
  depicted in Figure 2.