oneM2M Logo transparent 196x130

Standards for M2M and the Internet of Things

  • 1
  • 2
  • 3
  • 4
  • 5

Cross Sector Standards

oneM2M's architecture and standards for M2M communications are designed to be applied in many different industries, and take account of input and requirements from any sector

  • Default
  • Title
  • Date
  • Random
  • eHealth and Telemedicine

    Groundbreaking M2M security means oneM2M standards are ready for use in eHealth and Telemedicine deployments
  • Industrial Automation

    A scalable archtitecture and a focus on interoperability allows oneM2M to be deployed where industrial-grade solutions are called for
  • Home Automation

    oneM2M's architecture can integrate current and future home and building control technology, federating the range of different protocols in use

Global partners and members

  • 8 ICT standards bodies
  • 5 global fora and SDOs
  • 200 members

Eight of the worlds leading regional ICT standards bodies have come together to create oneM2M

ARIB homepage logoATIS homepage logoCCSA homepage logoETSI homepage logo

TIA homepage logoTSDSI homepage logoTTA homepage logoTTC homepage logo

The regional standards bodies are joined by five globally active industry consortia and SDOs

BBF homepage logoCEN homepage logoCENELEC homepage logoGlobalPlatform homepage logo

OMA homepage logo

oneM2M's over 200 members form a broad cross-section of the M2M and the Internet of Things.

oneM2M is open to new members and partners joining and contributing to the work.

Find out more in our membership pages!

Home

Membership FAQ

Question: How can I become active in oneM2M?
Answer: See How to join page.

Question: Could you clarify the process for joining oneM2M? Does an organization nominate itself to join oneM2M? Can an organization determine which partnership level it would join at, or is that determined by the current members of oneM2M?
Answer: The application process depends on the profile of your organization. For details please see the How to join page.

Question: Could you clarify how patents and copyright ownership are addressed under oneM2M?
Answer: Section 7 and Annex 1 of the Partnership Agreement address intellectual property rights.
Copywrite
As stated in Section 7.1, Partners Type 1 jointly own the copyrights to oneM2M Technical Specifications and Technical Reports.
While Partners Type 2 and oneM2M Members would retain any copyright they may have in contributed materials, Section 7.5 of the Partnership Agreement explains that, in order to allow the development and dissemination of oneM2M Technical Specifications and Technical Reports, it is necessary that each Partner Type 2 and oneM2M member contributing to the technical work of oneM2M grant a perpetual, worldwide, royalty-free, nonexclusive license to: (i) incorporate text, graphics or other material whether oral or written from the contributed material in oneM2M Technical Specifications and Technical Reports; and (ii) publish the contributed material in Technical Specifications and Technical Reports and in the resulting Partners Type 1 deliverables, which may include translation or derivative thereof.
Patents
Essential patent disclosures are addressed primarily in Annex 1. Under the IPR principles governing oneM2M work described in this Annex, it is noted that all Partners Type 1 have IPR policies that support a FRAND IPR regime. oneM2M Members are required to comply with the policies of the admitting Partner(s) Type 1 IPR policy(ies) related to the disclosure of Essential IPRs and the availability of FRAND licenses. For more information, see Article 4.1 and Annex 1 of the Partnership Agreement.

Question: Does oneM2M have a policy to address competing standards projects?
Answer: Under Section 3.1 of the Partnership Agreement, all oneM2M Partners Type 1 shall avoid the development of work that overlaps the work of oneM2M to prevent fragmentation of a global oneM2M solution. In addition, as noted in Section 11, all oneM2M Participants are encouraged to provide reports on related M2M activities and to work toward the harmonization of M2M solutions wherever possible.
There is no specific oneM2M policy regarding competing standards projects undertaken by organizations that are not oneM2M Partners. It is anticipated that the oneM2M Partners would reach out to such organizations to encourage a harmonized global M2M solution.

Question: Is there an adoption process for oneM2M specifications where there are multiple SDOs within a country?
Answer: As noted in Section 3.1 of the Partnership Agreement, Partners Type 1 convert/transpose/publish relevant Technical Specifications and Technical Reports resulting from the work in oneM2M into its own relevant deliverables through the Partner's normal processes. As also noted in this section, Partners Type 1 in the same geographic region may coordinate such conversion/transposition/publication in that region to avoid unnecessary duplication.

Partner Application Form


Please complete the form below in order to apply to become a oneM2M Partner Type 1 or Partner Type 2.

Organization Name(*)
Invalid Input

Address Line 1
Invalid Input

Address Line 2
Invalid Input

City(*)
Invalid Input

State/Province
Invalid Input

Postcode / Zipcode
Invalid Input

Country(*)
Invalid Input

Website(*)
Invalid Input

Industry(*)
Invalid Input

Name of CEO
Invalid Input

Partner Type

Please specify the type of oneM2M partnership you are applying for:

Select(*)

Invalid Input

Contact Information

Please identify the main point of contact with regards to your application for Partnership in oneM2M

Name(*)
Invalid Input

Title(*)
Invalid Input

Invalid Input

Address Line 1
Invalid Input

Address Line 2
Invalid Input

City
Invalid Input

State/Province
Invalid Input

Postcode / Zipcode
Invalid Input

Country
Invalid Input

Office Phone
Invalid Input

Mobile Phone
Invalid Input

E-mail address
Invalid Input

Alternate Contact Information

Please identify an alternate point of contact with regards to your application for Partnership in oneM2M. The alternate shall be copied on all membership-related correspondence sent from oneM2M

Name(*)
Invalid Input

Title(*)
Invalid Input

Invalid Input

Address Line 1
Invalid Input

Address Line 2
Invalid Input

City
Invalid Input

State/Province
Invalid Input

Postcode / Zipcode
Invalid Input

Country
Invalid Input

Office Phone
Invalid Input

Mobile Phone
Invalid Input

E-mail address
Invalid Input

Please note that participation as a Partner Type 1 requires an organization to have an IPR Policy that complies with the oneM2M Partnership Agreement, specifically Section 7 and Annex A. Participation as a oneM2M Partner Type 2 requires an organization to either: (1) have an IPR Policy that complies with the oneM2M Partnership Agreement, specifically Section 7 and Annex A; or (2) provide written assurance that: (a) its oneM2M contributions are made in accordance with a Partner Type 1 IPR Policy; and (b) its members are bound by such an IPR Policy relative to any oneM2M contribution

  

Associate Member

An Associate Member is any government or regulatory agency that has an interest in oneM2M. 

An Associate Member has the right to attend and provide input to meetings of the Technical Plenary and its subgroups. However, this is limited to clarifications regarding regulatory matters and informational contributions.

Become an Associate Member

Partner Type 2

A Partner Type 2 is any legal entity which is member based and has acknowledged competency in developing standards in oneM2M's area of work. A Partner Type 2 provides strategic direction to oneM2M.

A Partner Type 2 can  attend, participate in and vote in the oneM2M Steering Committee and the oneM2M Technical Plenary and its subgroups.

How to become a Partner Type 2

Upcoming Events

No events
Subscribe to oneM2M News Please enter your name and email address, then click on submit.
Alternatively, you can send an email from your preferred email application with a blank subject to
[email protected] with subscribe oneM2M_News in the message body.

Subscribe to oneM2M News

Your Name(*)
Please let us know your name.

Your Email(*)
Please let us know your email address.