Common use of Scope and Objectives of the Partnership Clause in Contracts

Scope and Objectives of the Partnership. The Partners agree to co-operate in the production and maintenance of globally applicable Technical Specifications and Technical Reports related to M2M Solutions with the initial focus on Service Layer. Initially, oneM2M shall prepare, approve and maintain the necessary set of Technical Specifications and Technical Reports for:  Use cases and requirements for a common set of Service Layer capabilities;  Service Layer aspects with high level and detailed service architecture, in light of an access independent view of end-to-end services;  Protocols/APIs/standard objects based on this architecture (open interfaces & protocols);  Security and privacy aspects (authentication, encryption, integrity verification);  Reachability and discovery of applications;  Interoperability, including test and conformance specifications;  Collection of data for charging records (to be used for billing and statistical purposes);  Identification and naming of devices and applications;  Information models and data management (including store and subscribe/notify functionality);  Management aspects (including remote management of entities); and  Common use cases, terminal/module aspects, including Service Layer interfaces/APIs between: o Application and Service Layers; o Service Layer and communication functions.

Scope and Objectives of the Partnership. The Partners agree to co-operate in the production and maintenance of globally applicable Technical Specifications and Technical Reports related to M2M Solutions with the initial focus on Service Layer. Initially, oneM2M shall prepare, approve and maintain the necessary set of Technical Specifications and Technical Reports for:  • Use cases and requirements for a common set of Service Layer capabilities;  • Service Layer aspects with high level and detailed service architecture, in light of an access independent view of end-to-end services;  • Protocols/APIs/standard objects based on this architecture (open interfaces & protocols);  • Security and privacy aspects (authentication, encryption, integrity verification);  • Reachability and discovery of applications;  • Interoperability, including test and conformance specifications;  • Collection of data for charging records (to be used for billing and statistical purposes);  • Identification and naming of devices and applications;  • Information models and data management (including store and subscribe/notify functionality);  • Management aspects (including remote management of entities); and  • Common use cases, terminal/module aspects, including Service Layer interfaces/APIs between: o Application and Service Layers; o Service Layer and communication functions.