oneM2M TS-0032Release Notes diff from v5.0.2 to v5.0.2oneM2M TS-0032Release Notes diff from v5.0.2 to v5.0.2For the purposes of the present document, the terms and definitions given in oneM2M TS-0011 [7], oneM2M TS0003 [2] and the following apply:
MAF Client: functionality for performing MAF procedures on behalf of an associated CSE or AE, or on behalf of CSE or AE(s) present on an associated Node
MAF interface: communication interface between a MAF and a MAF Client identified by reference point Mmaf
MEF Client: functionality for performing MEF procedures on behalf of an associated CSE or AE, or on behalf of CSE or AE(s) present on an associated Node, or an associated MAF
MEF interface: communication interface between a MEF and a MEF Client identified by reference point Mmef
For the purposes of the present document, the abbreviations given in oneM2M TS-0011 [7], oneM2M TS-0003 [2] and the following abbreviations apply:
ADN Application Dedicated NodeAE Application EntityAE-ID Application Entity IdentifierAPI Application Programming InterfaceASN Application Service NodeBBF Broadband ForumCDT Common Data TypesCRUD Create, Retrieve, Update, Delete (operation)CSE Common Services EntityCSE-ID Common Services Entity IdentifierDM Device ManagementDTLS Datagram Transport Layer SecurityFQDN Fully Qualified Domain NameHTTP Hypertext Transfer ProtocolIN Infrastructure NodeMAF M2M Authentication FunctionMEF M2M Enrolment FunctionMN Middle NodeMQTT Message Queue Telemetry TransportMTE M2M Trust EnablerNP Not PresentRSPF Remote Security Provisioning FrameworkRO Read-OnlyRW Read-WriteSEC SecuritySP Service ProviderSP-ID Service Provider IdentifierSUID Security Usage IdentifierTLS Transport Layer SecurityWO Write-OnlyXML Extensible Markup Language