1 / 13

TTA Views on Technical Scope of M2M Consolidation

TTA Views on Technical Scope of M2M Consolidation. 17 August 2011 TTA . M2MCons02_16 ( Agenda 4.3). Technical Scope of M2M Consolidation (1/11). Architectural Framework Use-cases and Requirements Analysis Functional Service Entities and Data model

alia
Download Presentation

TTA Views on Technical Scope of M2M Consolidation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. TTA Views on Technical Scope ofM2M Consolidation 17 August 2011 TTA M2MCons02_16 (Agenda 4.3)

  2. Technical Scope of M2M Consolidation (1/11) • Architectural Framework • Use-cases and Requirements Analysis • Functional Service Entities and Data model • Identification & Naming of M2M Devices & Applications • Authentication, Authorization, Accounting and Charging • Security & Privacy • Maintenance and Management • Interoperability and Conformance Testing • Application Interfaces and/or APIs to M2M System components • Embedded Module Design

  3. Technical Scope of M2M Consolidation (2/11) • An example of M2M Architecture Vertical Market Areas WPAN Gateway Service provider Identification & Naming Networks Authentication, Authorization, Accounting and Charging Security & Privacy Maintenance & Management M2M device

  4. Technical Scope of M2M Consolidation (3/11) • Use-cases and Requirements Analysis • Use-cases from each M2M domain (e.g., Smart Grid, Smart metering, Healthcare, Automotive, etc.) shall be identified • Requirements for M2M services based on use-cases shall be analyzed

  5. Technical Scope of M2M Consolidation (4/11) • Functional service entities and data model • Various service entities may be identified such as location management, time synchronization, identification, authentication, and accounting/billing • Some of service entities may reside only on M2M devices; some of them may reside on both M2M devices and M2M application/service systems; and some of them may reside only on M2M application/service systems • Each service entity requires a communication interface. • A common data model may be required among relevant service entities and M2M application/service data may be shared transparently among them • Ex: OGC’s SWE (Sensor Web Enablement) Common Data Model ??

  6. Technical Scope of M2M Consolidation (5/11) • Identification & Naming of M2M Devices & Applications • M2M devices and applications shall be identified and relevant identifiers may be required • Various M2M identifiers shall be distinguished each other and identified uniquely and utilized within M2M system • What the scope of M2M system is ?? ToR of M2M TC in ETSI • The relationship/mapping between Identification and Naming needs to be clarified in M2M system • How to apply M2M identifiers in existing networks (e.g., 3G/4G, WiFi, WPAN, etc.) needs to be described • M2M Identifier  MSISDN or IPv6 or ??

  7. Technical Scope of M2M Consolidation (6/11) • AAA and Charging • Authentication: M2M devices shall be access-controlled by both tele-communication and M2M service providers • Authorization: M2M data may be required to be access-controlled according to access privileges • Accounting: M2M communication traffics and M2M data usages may be required to be monitored and accounted according to accounting policies (e.g. data types such as weather information or surveillance; real-time or event-driven; and private or public sector)  • Charging: M2M service usages may be charged according to accounting results and pricing policies

  8. Technical Scope of M2M Consolidation (7/11) • Security and Privacy Aspects • M2M data may be required to support encryption, integrity, authentication and non-repudiation. For example, health information from an M2M device shall be protected • M2M data may be privacy-sensitive such as location information. Privacy protection for M2M data shall be considered

  9. Technical Scope of M2M Consolidation (8/11) • Maintenance and Management • M2M devices and M2M area network need to be monitored and managed remotely • Relevant interfaces and management information base are consideration points • Some of M2M devices may be required to be highly reliable • Self-healing of M2M devices and M2M area network, and dynamic route re-arrangement are consideration points

  10. Technical Scope of M2M Consolidation (9/11) • Interoperability and conformance testing • Conformance testing verifies globally-interoperable M2M devices and application systems according to interface standards • Conformance test suites shall be provided for each interface standard • Interoperability testing assures globally-interoperable M2M devices and application systems. Interoperability test procedures shall be provided • Collaboration of Certifications between ICT and Vertical Products is needed

  11. Technical Scope of M2M Consolidation (10/11) • Application interfaces and/or APIs to M2M system components • Application interfaces between functional service entities shall be specified • APIs may be specified between functional service entities and M2M applications • APIs may be open to the public where so-called Open APIs may be provided

  12. Technical Scope of M2M Consolidation (11/11) • M2M Device & Embedded Modules/Terminal • Common requirements for M2M devices of all different vertical markets • Identifier, Device Management Protocol, Software SIM, Security, etc • Requirements for M2M Device per different vertical markets • Embedded Module Designs for M2M vertical markets • Connectivity, RF + Base Band, Frequency Band, Power, UICC, Antenna, I/O, Common API, etc • Smart Grid, Connected Health, Connected Car, Connected CE, etc • GSMA recently released the guidelines for embedded module. But, there is no single standard.

  13. Thank you for your attention.

More Related