oneM2M-ARC-2013-0202R05-Unified_stack_and_more_than_just_IP_for_M2M_systems.DOC - oneM2M-ARC-2013-0202R010202R05

OneM2M-ARC-2013-0202R05-Unified_stack_and_more_than_just_IP_for_M2M_systems.DOC

This preview shows page 1 - 3 out of 11 pages.

oneM2M-ARC-2013- 0202R01 0202R0 5 Unified_stack_and_more_than_just_IP_for_M2M_systems INPUT CONTRIBUTION Group Name:* ARC-WG during TP#3 Title:* Unified stack and more than just IP for M2M systems Source:* Nicolas Damour, Sierra Wireless SA ( [email protected] ) Enrico Scarrone, Telecom Italia Rajesh Bhalla, ZTE Corporation Jaeseung Song, NEC Europe Ltd . Mihai Voicu, ILS Technology LLC Guang Lu, Interdigital Communications Patricia Martigne, France Telecom R&D Beijing Co. Ltd . Walter Featherstone, Motorola Mobility UK Ltd. Josef Blanz, Qualcomm UK Ltd. Lionel Florit, Cisco Systems Belgium Dragan Vujcic, Oberthur Technologies Hongbeom Ahn, LG Electronics Contact: Nicolas Damour ([email protected]) Date:* 2013-02- 18 28 Abstract:* Proposal to unify the M2M stack between the device, gateway and server Proposal to assert IP as the common but not necessarily the only network protocol Agenda Item:* To be defined Work item(s): M2M Architecture Document(s) Impacted* Architecture TS (number to be assigned) Intended purpose of document:* Decision Discussion Information Other <specify> Decision requested or recommendation:* It is proposed to discuss the rationale of the submitted suggestions as well as and to adopt the conclusions. oneM2M IPR STATEMENT © 2013 oneM2M Partners Page 1 (of 11)
Image of page 1
oneM2M-ARC-2013- 0202R01 0202R0 5 Unified_stack_and_more_than_just_IP_for_M2M_systems Participation in, or attendance at, any activity of oneM2M, constitutes acceptance of and agreement to be bound by all provisions of IPR policy of the admitting Partner Type 1 and permission that all communications and statements, oral or written, or other information disclosed or presented, and any translation or derivative thereof, may without compensation, and to the extent such participant or attendee may legally and freely grant such copyright rights, be distributed, published, and posted on oneM2M’s web site, in whole or in part, on a non-exclusive basis by oneM2M or oneM2M Partners Type 1 or their licensees or assignees, or as oneM2M SC directs. 1 Introduction In the months between OneM2M TP#1 and OneM2M TP#3, the current state of work on M2M service layer standardization originating from the different partners type 1 has been presented and, to some extent, analysed. This work is still under progress and it is the purpose of the first part of the Technical Report on M2M Architecture to summarize the results of this analysis. However, from the discussions and reflections that already took place on this subject so far, as well as from some input received as use cases and requirements, there are two considerations that we would like to submit to the architecture group for further thinking and refinement. Our first consideration is that most high-level architecture documents so far have a reference to a “network domain”, “application domain” or “server domain” on one side, and to a “device domain”, “sensor domain”, “gateway domain” or even “M2M domain” on the other side. However, we
Image of page 2
Image of page 3

You've reached the end of your free preview.

Want to read all 11 pages?

  • Spring '13
  • L
  • IP address, oneM2M Partners, oneM2M-ARC

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

Stuck? We have tutors online 24/7 who can help you get unstuck.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes