5 Scope

This Work Item aims to develop a Technical Report investigating the interworking of the oneM2M standard and the Model Context Protocol (MCP).

The objectives of the work item are structured as followed:

Providing a technical analyses of Model Context Protocol

Describe use cases that demonstrate how the diverse features of oneM2M can be utilized for AI in the context of MCP, including relevant interworking scenarios that are not limited to, but may involve IoT, networks, and workflows with a focus on scenarios of interest to key communities within the oneM2M and broader SDO ecosystem.

Define a technical solution for interworking between the two standards, which may involve different levels of integration, including:

Basic data forwarding / API wrapping

Simple bridging of data between the two protocols without interpreting or translating its meaning. This can involve transferring payloads or invoking APIs from one side to the other in a transparent, "black box" manner.

Semantic interworking

Mapping the structure and meaning (semantics) of messages or data models from one protocol to the other. This includes translating message formats, aligning identifiers, or converting contextual metadata to ensure mutual understanding.

Behavioral interworking

Emulating or responding to protocol-specific behaviors such as session handling, heartbeat mechanisms (e.g., pings), or control flows. This may require actively interpreting incoming messages and triggering appropriate actions, even if the target protocol does not natively support those behaviors.

Security, authentication, authorization, and licensing aspects

Identify and address security-related requirements for interworking, including data protection, access control, trust management, and the handling of licensing and rights management when data is exchanged or reused across systems.

Furthermore, based on the findings of the Technical Report, subsequent normative work may be initiated as a standalone Technical Specification to enable MCP interworking.