6.3 MEF Interface

The MEF Interface generic resource request procedure for originators and receivers conforms to clauses 7.2.2.1 and 7.2.2.2 of oneM2M TS-0004 [3] with the following clarification:

• The MEF Client acts as the originator, and the MEF acts as the receiver and resource hosting entity.
• The MEF Handshake procedure (clause 8.3.5.2.2 of oneM2M TS-0003 [2]) is used for mutual authentication of the MEF Client and MEF.
• The operation shall be one of the CRUD operations.
• The request and response parameters shall conform to table 5.2.2-1 and table 5.2.2-2.
• "Blocking Mode" communication method shall be used.
• The step Recv-6.3: "Check authorization of the Originator" is replaced by the authorization processes described in the MEF Interface resource-type specific procedures in clause 8.

The originator actions, receiver actions and Hosting CSE actions conform to clause 7.3 of [3], with clause 7.3.3.15 of [3] replaced by the authorization processes described in the MEF Interface resource-type specific procedures in clause 8.

The management common operations in clause 7.3.4 of [3] do not apply to the MEF Interface.

The resource-type-specification conventions apply to the specification in clause 8, but the remainder of clause 7.4 of [3] does not apply to the MEF Interface.

Clause 7.5.1 of [3] (regarding Notification) does not apply to the MEF Interface. Elements contained in the Content primitive parameter conform to clause 7.5.2 of [3].

The representation of MEF Interface primitives in data transfer conforms to clause 8. Clause 9 contains additional short names specific to the both the MAF and MEF Interfaces.