Doc# 726832126
Group Name:*
Title:*
Source:*
Contact:
Date:*
Abstract:*
ARC WG
A CSF description for Identification
KT, NEC
Francisco Sang-Eon Kim (kim.sangon@kt.com)
JaeSeung Song (JaeSeung.Song@neclab.eu)
Michael hs, Yang (hayang@lguplus.co.kr)
2013-07-xx
This contribution proposes to include a CSF description for
Identification.
Agenda Item:* Drafting CSF WG2
Work item(s):
Document(s)
Impacted*
Intended purpose of document:*
Decision requested or recommendation:* oneM2M-WI-0002 oneM2M-TS-0001 oneM2M Functional Architecture
Decision
Discussion
Information
Other <specify>
For discussions and adoption in Functional Architecture Technical
Specifications
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.
© 2012 oneM2M Partners Page 1 (of 3)

Doc# 726832126
The requirement TS, oneM2M-TS-Requirements-V-0.4.0, specifies the related to identification as follows:

OSR-023: The M2M System shall be capable of identifying the M2M Services to be used by M2M service subscriptions.

OSR-024: The M2M System shall be capable of identifying the devices used by M2M service subscriptions.

OSR-025: The M2M System shall be capable of identifying the M2M Applications used by M2M service subscriptions.

OSR-026: If provided by the Underlying Network, the M2M System shall be capable of associating the device used by a M2M System with the device identifiers offered by the Underlying Network and the device.

MGR-013; The M2M System shall be able to identify and manage M2M Service status of M2M Devices.

SER-015: The M2M System should support mechanisms to provide User identity to authorized and authenticated M2M Applications (e.g., police center) when the M2M System has the User’s consent.
In the TP#5, WG2 listed a set of CSFs that resides in CSE. One of CSFs is for a identification function provided by the oneM2M System as follows:
CSF Name Supported Capabilities
Identification
 Identity
Note: more functionalities are expected here (cf. for example oneM2M-
ARC-2013-0277)
This contribution proposes a CSF description for identification.
===================== 1 st Change =========================
8.1.x Identification
The goal of the Identification CSF is to provide information for distinction, confirmation, indication, improvement, retrieval, deletion, management and access to physical and logical elements in M2M environment. The logical element is entities of related to software such as
Application, CSE and datum. The physical element is hardware related entities such as
© 2012 oneM2M Partners Page 2 (of 3)

Doc# 726832126 underlying network interface and M2M node/Intermediate node/Infrastructure node. The
Identification CSF is involved in the procedures for M2M identifier provisioning and M2M
Application addressing.
The identification is unique information or name or tag or label as an identifier which has identical meaning to the same type of information in M2M environment. The one identifier shall not be assigned to two or more different entities. The identifier is used as a reference to entities during the lifetime between Applications, CSEs, Data, network interfaces and node/Intermediate node/Infrastructure node. These identifiers provide information for association with other identifiers. It uses in the procedures for M2M service provisioning, exchange data between M2M Application and so on.
Identification of M2M Application is information (or name or tag or label) of the M2M application either by hand or automatically when the application is installed. It provides information for association which is mapping with other identifiers such as CSE identifier, network identifier, node identifier and so on.
M2M Application addressing is to reach the M2M CSE with which the target M2M application is registered and ultimately the correct application on the Device/Intermediate Node on which the target application is resident. This is a common principle to all applications in
Device and Intermediate Node.
Reachability and routing from/to Applications on Device Node and Intermediate Node is always associated with the Identification CSF in the CSE, with which these applications are registered, and which is resident on Device/Intermediate Node connected to the access network. Reaching an application shall be performed through reaching the CSE the application registered to. The Identification CSF shall provide the set of information needed to reach a CSE from a network perspective.
Identification of CSE is information (or name or tag or label) of CSE either by hand or automatically when M2M system initialize.
Identification of M2M data is information on data identifier or uniform resource identifier (URI) when it generates form sensing data or receiving data through other CSEs. It is used for reference to exchange of data.
Identification of network interface is information (or name or tag or label) when the M2M system boots up. It is used for association with network address which is Internet Protocol
(IP) address because M2M system is independent of wired or wireless network.
The Identification CSF provides a function resolving identifiers into network addresses which are used for communication between entities in the M2M System. The identifiers that are used in the M2M System are shown in Section X.X.
Identification of M2M node/intermediate node/infrastructure node is information (or name or tag or label) when the node boots up. It is used for distinction among the nodes at service provider or between service providers.
================== End of 1 st Change ======================
© 2012 oneM2M Partners Page 3 (of 3)