1. Proposal for App Id and Service Provider Id registration Group Name: Shelby Source: Shelby, iconectiv / Ericsson, skiewel@iconectiv.comskiewel@iconectiv.com Meeting Date: 2014-09-22

2. Introduction Application ID – Scope of Identifier – Method of administration of identifier – Implications of Approach's Service Provider ID – Scope of Identifier – Method of administration of identifier – Potential Adjustment of identifier to be oneM2M Company ID © 2014 oneM2M Partners 2

3. Service Provider ID Companies which operate in the oneM2M space: – Service Providers – Software Companies – Hardware Companies Require company legal documents to establish an identifier Register company name, headquarters location and contact information Associate a unique mnemonic code to be used when identifing the company

4. Service Provider Id are provided by registrar and follow a procedure to select the mnemonic code which models the Company Name where possible Example Service Provider Id

5. Application Id Applications are registered along with the following information – Registry: multiple registries could be operating at once – Application Purpose (or function): Sensor, Data Store – Payload: HTML, JSONP, SOAP, XML – Service Provider Code – Version – Contract Interface details – Service Provider Specific: Yes, No Users and oneM2M nodes can query the registry to determine available applications Application Ids can identify either individual function calls or entire suites of functionality

6. Example App Ids Connect Many to Many has registered 2 App Ids – App Id: RegA-SENS-XML-GENR-00001 was registered in registry A for software which primarily is involved in sensing. The XML contract interface is open to everyone (or Generic) and can be accessed from the App Id record – App Id: RegA-SENS-XML-ATXT-00001 was registered in registry A for software which primarily is involved in sensing. The XML contract interface is AT&T proprietary and can not be inspected

7. Single/Multiple Registries With a single registrar, the identifiers would be able to associate to the oneM2M namespace With multiple registrar’s, complexity in management of the identifiers becomes difficult – Advanced coordination between the repositories would be required – Maintaining the uniqueness of the identifier requires real-time validation between registries – Separate API’s, processes, interfaces, agreements, and more would be necessary for providers of oneM2M applications

8. Application Purpose An indication of the primary function served by the application would be inventoried by the registrar Proposed primary application values are: – Analysis (ANAL) – concerned with the analysis of information – Data Store (DTST) – amass and manage information repositories of information – Integration (INTG) – involved in integrating information from different sources – Processor (PROC) – sum, tabulate, consolidate larger numbers of inputs into summarized information – Management (MGMT) – concerned with the oversight and management of other nodes – Monitor (MNTR) – monitor the function of the oneM2M network – Security (SECU) – authorize and authenticate oneM2M communications – Sensor (SENS) – collection the value of one or more attributes

9. Payload Request and response messages can be provided in different formats. – Potential payload formats: HTML, JSONP, SOAP or XML – Request/response scheme would be included in the application record

10. Service Provider Code Companies requesting an App Id must have a Service Provider Code Questions and issues surround the App Id usage and performance can be directed to responsible party, i.e. Service Provider

11. Versioning Software version of the App Id. – The App Id will potentially change for each release. – The App Id will allow consumers to identify prerelease versions – alpha and beta. Version and backward compatibility will also allow automated decisions about whether upgrading version is feasible or warranted within the oneM2M system.

12. Contract Interface The contract interface will be uploaded and analyzed for adherence to oneM2M standards and validated for uniqueness A SOAP interface, for example, could upload the WSDL

13. Contract Interface - Example Temperature: Request http://schemas.xmlsoap.org/soap/envelope/ Temperature: Response 0.000032431 32 5,000 ft

14. Service Provider Specific The App Id is intended to be Generic and freely reusable within the oneM2M ecosystem. App Id’s which are generic and open will be clearly indicated in the App Id identifier e.g. –GENR- Potential Method of Application Segregation – A Service Provide may optionally retain the proprietary nature of their application. They would submit the Contract Interface to the registrar, but this information would not be made available to people querying App Ids

15. Thank you for your attention