Table of Contents

1     Scope          
 2     References
 3     Definitions
        3.1     Terms defined elsewhere       
        3.2     Terms defined in this Recommendation           
        3.3 Abbreviations and acronyms 
 4     Conventions            
 5     Protocol design principles and requirements             
        5.1     General introduction
        5.2     Introduction 
        5.3     API design guidelines
        5.4     Primitives      
        5.5     Design principles         
 6     oneM2M protocols/API overview   
        6.1     Introduction 
        6.2     Addressing    
        6.3     Common data types  
        6.4     Message parameter data types            
        6.5     Resource data types  
        6.6     Response status codes             
        6.7     oneM2M specific MIME media types 
        6.8     Virtual resources        
 7     oneM2M procedures           
        7.1     Introduction 
        7.2     Primitive format and generic procedure           
        7.3     Common operations 
        7.4     Resource type-specific procedures and definitions      
        7.5     Primitive-specific procedures and definitions 
        7.6     Security procedures  
 8     Representation of primitives in data transfer             
        8.1     Introduction 
        8.2     Short names 
        8.3     XML serialization        
        8.4     JSON serialization       
        8.5     CBOR serialization      
Annex A – Binding Mch to diameter for charging    
        A.1     Introduction 
        A.2     Diameter commands on Mch
        A.3     Mapping of M2M recorded information elements to AVPs      
        A.4     Summary of AVPs used           
        A.5     oneM2M specific AVP usage 
Annex B – 3GPP MTC interworking device triggering    
        B.1     Device triggering        
        B.2     Configuration of AESE Communication Patterns            
Annex C .    
Annex D – <mgmtObj> Resource specializations    
        D.1     Introduction
        D.2     Resource [firmware]
        D.3     Resource [software] 
        D.4     Resource [memory]  
        D.5     Resource [areaNwkInfo]         
        D.6     Resource [areaNwkDeviceInfo]           
        D.7     Resource [battery]    
        D.8     Resource [deviceInfo]              
        D.9     Resource [deviceCapability]  
       D.10     Resource [reboot]   
       D.11     Resource [eventLog]
       D.12     Resource [cmdhPolicy]          
Annex E              
Annex F               
Annex G – Location request    
        G.1     Introduction
        G.2     Location request by means of OMA-REST-NetAPI-TerminalLocation interface 
Annex H – CMDH message processing    
        H.1     Pre-requisites             
        H.2     CMDH processing: processing request or response messages requiring the receiver CSE to forward information to another CSE    
Annex I                
Annex J – Specializations of <flexContainer> resource    
        J.1     Introduction  
        J.2     Resource type [genericInterworkingService]   
        J.3     Resource type [genericInterworkingOperationInstance]            
        J.4     Resource type [svcObjWrapper]           
        J.5     Resource type [svcFwWrapper]            
        J.6     Resource type [allJoynApp]    
        J.7     Resource type [allJoynSvcObject]         
      Page
        J.8     Resource type [allJoynInterface]          
        J.9     Resource type [allJoynMethod]            
       J.10     Resource type [allJoynMethodCall]    
       J.11     Resource type [allJoynProperty]         
Annex K – oneM2M Specification update and maintenance control procedure    
Annex L               
Appendix I – XML examples    
       I.1      XML schema for container resource type          
       I.2      Container resource that conforms to the Schema given above (see clause I.1)   
Appendix II – Procedures for accessing resources    
      II.1      Accessing resources in CSEs – blocking requests            
      II.2      Accessing resources in CSEs - non-blocking requests    
Appendix III – Guidelines for oneM2M resource type XSD    
Appendix IV – Guidelines for using XSD files in AE and CSE code    
      IV.1      Usage of the oneM2M developed XSD files    
      IV.2      Example AE/CSE implementation featuring mapping between short and long names for XML serialization    
      IV.3      Example AE/CSE implementation featuring mapping between short and long names for JSON serialization    
Bibliography