1. TS0001 Identifiers way forward Group Name: WG2 Source: Elloumi, Foti, Scarrone, Lu (tbc), Jeong (tbc) Meeting Date: 2014-06-07 Agenda Item: ARC11/PRO11 Identifiers

2. Problem statements – AE-ID and CSE-ID must be globally unique without the need for a central coordination point – Need to ensure oneM2M architecture supports the needs of multi- user applications – AE-ID and CSE-ID Identifiers lenghth could become an issue, in particular for constrained networks/devices – Need to shorten the length of URIs / identifiers in particular for constrained devices – Specification allows for hierarchical and non hierachical URIs, but the use of both formats brakes the ACP (no means to go from one format to another)

3. Solution principles – For a given request, use relative identifiers of AE-ID and CSE-ID: – The relative identifier is defined as the part of the ID that allows the receiving entity (CSE) to derive the globally unique identifier (from the context in which the request is received) – Use only hierarchical URIs for AE or CSE resources – Hierarchial and Non hierarchival URIs can be used for other resources – Multi user applications are supported by means of multiple registrations

4. CSE-ID M2M-SP-ID CSEBase Provided by SP during provisioning (see section 11.2.1) Relative CSE-ID – Relative CSE-ID used within M2M SP domain Requests – except for the to parameter when the target resource resides in a different M2M SP domain – except for the from parameter when the request is originated in another M2M SP domain – M2M-SP-ID is mapped in the current version of the TS to a FQDN (guaranteeing global uniqueness for identifiers) – The following are valid identifiers for a CSE: – /CSEBase1/ - relative CSE identifier – FQDN M2M SP1/CSEBase1

5. AE-ID M2M-SP-ID CSEBase Provided by a CSE (ASN-CSE, MN-CSE or IN-CSE) at application registration – Instance is assigned by a CSE at application registration time. – Regardless of the App-ID, regardless of the ADN – AE-ID: FQDN M2M SP1/CSEBase1/App-ID1_Instance1 – Relative AE-ID could be: – App-ID1_Instance1 – CSEBase1/App-ID1_Instance1 – See table on the use of AE-ID (relative, global unique) App-ID_Instance

6. ACP – Originator in an ACP (CSE-ID or AE-ID ) – shall always store global unique identifiers when the originator is belonging to a domain that is different from the domain where the ACP resides: – FQDN M2M SP1/CSEBase1/App-ID1_Instance1 – FQDN M2M SP1/CSEBase 1 – Shall always store the following relative identifiers when the orginator is belonging to the same domain where the ACP resides – /CSEBase1/App-ID1_Instance1 – /CSEBase 1

7. Multi user applications – An application shall perform an application registration, one for each user.

8. Example1 MN- CSE AE (ADN ) IN- CSE Create rt=remoteCSE (from: /MN-CSEBASE1/ to: /IN-CSEBASE1/) OK Create rt=application (from: App-ID* to: /MN-CSEBASE1/) FQDN M2M SP1/MN-CSEBase1/App-ID_Intance1 Create rt=container, «meter1234» (from: App-ID_Instance1 to: /App-ID_Instance1/) URI (Hierarchical URI): App-ID_Intance1/meter1234 Resource representaion contains Non hierarchical URI: /12Uyzag MN-CSEBase1IN-CSEBase1 …

9. Example1 cntd. MN- CSE AE (ADN ) IN- CSE Create rt=container «meter1234» (from: App-ID_Instance1 to: /IN-CSEBASE1/App-ID_Instance12345/) URI (Hierarchical URI): /IN-CSEBASE1/App-ID_Instance12345/meter1234 Resource representation - Non hierarchical URI: /IN-CSEBASE1/212Uyzag Create rt=container «meter1234» (from: MN-CSEBase1/App-ID_Instance1 to: /IN-CSEBASE1/App-ID_Instance12345/) URI (Hierarchical URI): /IN-CSEBASE1/App-ID_Instance12345/meter1234 Resource representaion - Non hierarchical URI: /IN-CSEBASE1/212Uyzag MN-CSEBASE1IN-CSEBASE1

10. Example2 MN- CSE AE (ADN ) IN- CSE MN-CSEBASE1IN-CSEBASE1 IN- CSE IN-CSEBASE2 Mcc’ Retrieve (from: App-ID_Instance1 to: M2M SP2 FQDN/IN-CSEBASE2/App-ID_Instance543/meter654) Retrieve (from: /MN-CASEBASE1/App-ID_Instance1 to: M2M SP2 FQDN/IN-CSEBASE2/App-ID_Instance543/meter654) Retrieve (from: IN-CASEBASE1/MN-CASEBASE1/App-ID_Instance1 to: M2M SP2 FQDN/IN-CSEBASE2/App-ID_Instance543/ meter654)