hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9.4.0 Introduction | Once a request has performed an Access Decision by the IN-CSE to allow the request, the IN-CSE shall select the appropriate ACS along with elements the ACS would need to implement access management within the ACS. These would include the Identity of the subject (oneM2M Originator) of the request which is needed in scen... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9.4.1 Access Management Requirements | • The ACS shall be capable of providing a mechanism for the IN-CSE to discover the Access Management elements used to authorize and authenticate access to resources controlled by the ACS. • The IN-CSE shall be capable of correlating Access Management elements provided by the ACS to Access Management elements used by th... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 10 New Management Technology Specific Resources | BBF TR-181 [6] provides a list of management objects that have been standardized by the Broadband Forum and where possible, clause 7 provides a mapping of the Resources to standardized management objects. This clause provides the oneM2M vendor specific extensions to the BBF TR-181 [6] data model. ETSI ETSI TS 118 106 V... |
10651370426c90bc406f33851f64d370 | 118 104 | 1 Scope | The present document specifies the communication protocol(s) for oneM2M compliant Systems, M2M Applications, and/or other M2M systems. The present document also specifies the common data formats, interfaces and message sequences to support reference points(s) defined by oneM2M. |
10651370426c90bc406f33851f64d370 | 118 104 | 2 References | |
10651370426c90bc406f33851f64d370 | 118 104 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
10651370426c90bc406f33851f64d370 | 118 104 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
10651370426c90bc406f33851f64d370 | 118 104 | 3 Definitions and abbreviations | |
10651370426c90bc406f33851f64d370 | 118 104 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 118 111 [25] and the following apply: complex data types: data type that has a child element enumeration type: data type that enables for a variable to be a set of predefined constants group hosting CSE: CSE where the addressed group r... |
10651370426c90bc406f33851f64d370 | 118 104 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 111 [25] and the following apply: 3GPP2 3rd Generation Partnership Project 2 ACP AccessControlPolicy AD Anno Domini AE-ID Application Entity Identifier ARC Architecture ASN-CSE Application Entity that is registered with the CSE at Applicat... |
10651370426c90bc406f33851f64d370 | 118 104 | 4 Conventions | The keywords "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. To improve readability: • The information elements of oneM2M Request/Response messages will be referred to as parameters. Parameter names will be wr... |
10651370426c90bc406f33851f64d370 | 118 104 | 5 Protocol design principles and requirements | The following clauses contain the design principles and requirements for the oneM2M protocol. |
10651370426c90bc406f33851f64d370 | 118 104 | 5.1 Introduction | The oneM2M architecture is resource-based (ETSI TS 118 101 [6] Functional Architecture). The functionality of the system is exposed by means of APIs over all reference points specified in ETSI TS 118 101 [6] Functional Architecture. Operations upon resources hosted by a CSE are carried over an established channel that ... |
10651370426c90bc406f33851f64d370 | 118 104 | 5.1.1 Interfaces to the underlying networks | The CSEs access the network service functions provided by the underlying networks such as 3GPP, 3GPP2 and WLAN via Mcn reference point. The following services are provided by the underlying networks: • Device triggering (see Annex B). • Location request (see Annex G). • Device Management (see clause 7.2.4). |
10651370426c90bc406f33851f64d370 | 118 104 | 5.2 API design guidelines | The following are the guidelines for designing APIs: 1) APIs shall follow the principle of RESTful architecture, as described in [i.2]. 2) APIs shall indicate which features are supported and not supported over the reference points specified in ETSI TS 118 101 [6] Functional Architecture. ETSI ETSI TS 118 104 V1.0.0 (2... |
10651370426c90bc406f33851f64d370 | 118 104 | 5.3 Primitives | |
10651370426c90bc406f33851f64d370 | 118 104 | 5.3.1 Introduction | Primitives are common service layer messages exchanged over the Mca, Mcc and Mcc' reference points. There are two use cases: • communication between an Originator and a Receiver which are collocated on the same M2M Node (e.g. ASN or MN) in the Common Service layer; • communication between an Originator and a remote Rec... |
10651370426c90bc406f33851f64d370 | 118 104 | 5.3.2 Primitives modelling | Primitives are modelled as follows. A primitive is represented in form of a data structure which defines with appropriate parameters specific procedures to be executed by both originator and receiver entities. The data structure of a primitive consists of two parts: • a control part, which contains parameters specifyin... |
10651370426c90bc406f33851f64d370 | 118 104 | 5.3.3 Primitive principles | Execution of one primitive shall finish completely before execution of a subsequent primitives starts that affects the same resource. When creating or updating the resource, its representation (full or partial) shall be contained in the content part of the primitive. Based on the representation of the resource, the Hos... |
10651370426c90bc406f33851f64d370 | 118 104 | 5.3.4. Serialization of primitives | When transferred over a oneM2M reference point while using a communication protocol such as HTTP, CoAP or MQTT, the way oneM2M Request and Response primitives are represented shall be defined by a specific oneM2M protocol binding that is being used for the message transfer. The originator and receiver of each primitive... |
10651370426c90bc406f33851f64d370 | 118 104 | 5.4 Design principles | |
10651370426c90bc406f33851f64d370 | 118 104 | 5.4.1 Introduction | The following clauses present the design principles which could wrap up the perspectives and ways in terms of definitions and procedures of APIs and resources for the oneM2M core protocol specified in this technical specification. These design principles shall cover all characteristics and advantages of oneM2M protocol... |
10651370426c90bc406f33851f64d370 | 118 104 | 5.4.2 Extensibility | The oneM2M protocols are designed to allow continued development and to facilitate changes by means of standardized extensions. The impact of the extensibility on the existing oneM2M protocol functions shall be minimized. Extensibility can be related to one or more of the following aspects: • Handling a wide range of t... |
10651370426c90bc406f33851f64d370 | 118 104 | 5.4.3 Scalability | For provisioning scalability as a requirement in the design of oneM2M protocols, one or several of the following mechanisms are used: • Ensuring direct addressability to the CSEs hosting target resources, to minimize network hops. • Asynchrony in terms of data processing, with the objective of minimizing the number of ... |
10651370426c90bc406f33851f64d370 | 118 104 | 5.4.4 Fault tolerance and robustness | One or more of the following mechanisms in terms of link availability can be exploited in the design of oneM2M protocols to account for a variety of exception conditions. • To provide reliable transmission of data packets, packet recovery will be dealt with by using mechanisms appropriate for the operating environment ... |
10651370426c90bc406f33851f64d370 | 118 104 | 5.4.5 Efficiency | oneM2M protocols are designed with consideration of efficiency for networking involved resource-constrained devices. • As energy consumption directly affects the overall system performance, oneM2M protocols should consider energy efficiency, especially in resource constrained environments with battery-powered oneM2M de... |
10651370426c90bc406f33851f64d370 | 118 104 | 5.4.6 Inter-operability | API inter-operability between different protocol stacks is expected. For example, oneM2M API over HTTP/TCP/IP needs to inter-operate with CoAP/UDP in a local network using oneM2M API. oneM2M protocols are specified to provision the API inter-operability. |
10651370426c90bc406f33851f64d370 | 118 104 | 5.4.7 Self-operation and self-management | Devices employing the oneM2M API inter-work with established management protocols (e.g. security, discovery, bootstrapping etc). The inter-working with legacy management protocols via the oneM2M API shall be carried out in self-operation methods. |
10651370426c90bc406f33851f64d370 | 118 104 | 6 oneM2M protocols/API overview | |
10651370426c90bc406f33851f64d370 | 118 104 | 6.1 Introduction | The present document describes message formats and procedures to communicate with oneM2M compliant M2M Platform System. The present document describes: • Data representation for communication protocol messages. • Normal and exceptional procedure. • Status codes. • Guidelines for drafting APIs. For wide acceptance by in... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.2 Addressing | This clause describes the method of addressing oneM2M entities (e.g. AE or CSE) and oneM2M resources using identifiers described in the ETSI TS 118 101 [6] Functional Architecture. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.2.1 Summary of oneM2M Identifiers | Shows the summary of M2M Identifers defined in ETSI TS 118 101 [6] Functional Architecture. ETSI ETSI TS 118 104 V1.0.0 (2015-02) 24 Table 6.2.1-1: M2M Identifiers Identifier Data Type Description M2M-SP-ID m2m:id (see clause 6.3.2) A globally unique ID as specified in [6] App-ID m2m:ID (see clause 6.3.2) The identifie... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.2.2 oneM2M Entity Addressing | The oneM2M entities (e.g. AE or CSE) are identified and addressable using M2M Identifiers. Since an M2M Identifier is protocol independent, an IN-CSE shall accommodate address resolution functionality to get actual PoA addresses for communicating with other M2M entities using a specific protocol binding. The present sp... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.2.3 oneM2M Resource Addressing | The authorized oneM2M entities can operate oneM2M Resourrce by specifying the Resource Identifier as the target address. There are 2 forms of oneM2M Resource Identifer is defined in clause 7.2 of the ETSI TS 118 101[6]. 1) Hierachical Address: the address which is constructed as relative path from the CSEBase resource ... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3 Common data types | The following clauses define the data format of resource attributes and parameters used in primitives. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.1 Simple data types incorporated from XML schema | The following 'built-in data types' are incorporated from XML Schema definition [3]. Note that name space identifier for 'http://www.w3.org/2001/XMLSchema' shall be referred to using the prefix xs: in the present document. Table 6.3.1-1: Data Types incorporated from XML Schema Data Type Description Notes xs:anyType A s... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.2 oneM2M simple data types | Table 6.3.2-1 describes oneM2M-specific simple data type definitions. XML Schema data type definitions for these data types can be found in the XSD file called CDT-commonTypes-v1_0_0.xsd. The types in table 6.3.2-1 are either: • Atomic data types derived from XML Schema data types by restrictions other than enumeration... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3 oneM2M enumerated data types | |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.1 Introduction | The oneM2M Enumeration Types are defined as extension from 'enumeration type' which is defined in XML Schema definition [3]. The oneM2M Enumeration Types are based on <xs:integer>, and the numeric values are interpreted as specified in clause 6.3.3.2. Table 6.3.3.1-1 shows the example of Enumeration Type definition for... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2 Enumeration type definitions | |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.1 m2m:resourceType | Table 6.3.3.2.1-1: Interpretation of resourceType Value Interpretation Note 1 accessControlPolicy 2 AE 3 container 4 contentInstance 5 CSEBase 6 delivery 7 eventConfig 8 execInstance 9 group 10 locationPolicy 11 m2mServiceSubscriptionProfile 12 mgmtCmd 13 mgmtObj 14 node 15 pollingChannel 16 remoteCSE 17 request 18 sch... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.2 m2m:cseTypeID | Used for cseType attribute of <CSEBase> resource. Table 6.3.3.2.2-1: Interpretation of cseTypeID Value Interpretation Note 1 IN_CSE 2 MN_CSE 3 ASN_CSE NOTE: See clause 7.3.4 "Resource Type remoteCSE". ETSI ETSI TS 118 104 V1.0.0 (2015-02) 32 |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.3 m2m:locationSource | Used for locationSource attribute of <locationPolicy> resource. Table 6.3.3.2.3-1: Interpretation of locationSource Value Interpretation Note 1 Network_based 2 Device_based 3 Sharing_based NOTE: See clause 7.3.9.2.4 "Resource Type locationPolicy". |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.4 m2m:stdEventCats | Used for ec parameter in request and eventCat attribute of <delivery> resource and cmdh policy resource types. Table 6.3.3.2.4-1: Interpretation of stdEventCats Value Interpretation Note 1 Default 2 Immediate 3 bestEffort 4 Latest NOTE: See clause 7.3.11 "Resource Type delivery" and clause D.12 "Resource cmdhPolicy". |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.5 m2m:operation | Used for Operation parameter in request and operation attribute in <request> resource as well as operationMonitor. Table 6.3.3.2.5-1: Interpretation of operation Value Interpretation Note 1 Create 2 Retrieve 3 Update 4 Delete 5 Notify NOTE: See clause 6.4.1 "Request message parameter data types". |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.6 m2m:responseType | Used for Response Type parameter (as a part of responseTypeInfo, See clause 6.3.4.29) in request. Table 6.3.3.2.6-1: Interpretation of responseType Value Interpretation Note 1 nonBlockingRequestSynch 2 nonBlockingRequestAsynch 3 blockingRequest NOTE: See clause 6.4.1 "Request message parameter data types". ETSI ETSI TS... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.7 m2m:resultContent | Used for Result Content parameter in request. Table 6.3.3.2.7-1: Interpretation of resultContent Value Interpretation Note 0 Nothing 1 Attributes 2 hierarchical address 3 hierarchical address and attributes 4 attributes and child resources 5 attributes and child resource references 6 child resource references 7 origina... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.8 m2m:discResType | Used in metaInformation attribute in <request> resource. Table 6.3.3.2.8-1: Interpretation of discResType Value Interpretation Note 1 hierarchical 2 Non_hierarchical 3 cseID and resourceID NOTE: See clause 6.4.1 "Request message parameter data types". |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.9 m2m:responseStatusCode | See clause 6.6.3 "Current Response Status Codes". Table 6.3.3.2.9-1: Interpretation of responseStatusCode Value Interpretation Note ('Numeric Code' in clause 6.6.3) ('Description' in clause 6.6.3) |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.10 m2m:requestStatus | Used for requestStatus attribute in <request> resource. Table 6.3.3.2.10-1: Interpretation of requestStatus Value Interpretation Note 1 COMPLETED 2 FAILED 3 PENDING 4 FORWARDED NOTE: See clause 7.3.12 "Resource Type request". ETSI ETSI TS 118 104 V1.0.0 (2015-02) 34 |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.11 m2m:memberType | Used for memberType attribute in <member> resource. Table 6.3.3.2.11-1: Interpretation of memberType Value Interpretation Note 1 accessControlPolicy 2 AE 3 Container 4 contentInstance 5 CSEBase 6 Delivery 7 eventConfig 8 execInstance 9 Group 10 locationPolicy 11 m2mServiceSubscription 12 mgmtCmd 13 mgmtObj 14 Node 15 p... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.12 m2m:consistencyStrategy | Used for consistencyStrategy attribute in <group> resource. Table 6.3.3.2.12-1: Interpretation of consistencyStrategy Value Interpretation Note 1 ABANDON_MEMBER 2 ABANDON_GROUP 3 SET_MIXED NOTE: See clause 7.3.13 "Resource Type group". |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.13 m2m:cmdType | Used for cmdType attribute in <mgmtCmd> resource. Table 6.3.3.2.13-1: Interpretation of cmdType Value Interpretation Note 1 RESET 2 REBOOT 3 UPLOAD 4 DOWNLOAD 5 SOFTWAREINSTALL 6 SOFTWAREUNINSTALL 7 SOFTWAREUPDATE NOTE: See clause 7.3.16 "Resource Type mgmtCmd". ETSI ETSI TS 118 104 V1.0.0 (2015-02) 35 |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.14 m2m:execModeType | Used for execModeType attribute in <mgmtCmd> and <execInstance> resource. Table 6.3.3.2.14-1: Interpretation of execModetType Value Interpretation Note 1 IMMEDIATEONCE 2 IMMEDIATEREPEAT 3 RANDOMONCE 4 RANDOMREPEAT NOTE: See clause 7.3.16 "Resource Type mgmtCmd" and clause 7.3.17 "Resource Type execInstance". |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.15 m2m:execStatusType | Used for execStatusType attribute in <execInstance> resource. Table 6.3.3.2.15-1: Interpretation of execStatusType Value Interpretation Note 1 INITIATED 2 PENDING 3 FINISHED 4 CANCELLING 5 CANCELLED 6 STATUS_NON_CANCELLABLE NOTE: See clause 7.3.17 "Resource Type execInstance". ETSI ETSI TS 118 104 V1.0.0 (2015-02) 36 |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.16 m2m:execResultType | Used for execStatusType attribute in <execInstance> resource. Table 6.3.3.2.16-1: Interpretation of execResultType Value Interpretation Note 1 STATUS_REQUEST_UNSUPPORTED 2 STATUS_REQUEST DENIED 3 STATUS_CANCELLATION_DENIED 4 STATUS_INTERNAL_ERROR 5 STATUS_INVALID_ARGUMENTS 6 STATUS_RESOURCES_EXCEEDED 7 STATUS_FILE_TRAN... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.17 m2m:pendingNotification | This is used for pendingNotification attribute in <subscription> resource. Table 6.3.3.2.17-1: Interpretation of pendingNotification Value Interpretation Note 1 sendLatest 2 sendAllPending NOTE: See clause 7.3.8 "Resource Type subscription". |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.18 m2m:notificationContentType | Table 6.3.3.2.18-1: Interpretation of notificationContentType Value Interpretation Note 1 modifiedAttributes 2 wholeResource 3 referenceOnly NOTE: See clause 7.3.8 "Resource Type subscription". ETSI ETSI TS 118 104 V1.0.0 (2015-02) 37 |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.19 m2m:resourceStatus | This is used for eventNotificationCriteria. Table 6.3.3.2.19-1: Interpretation of resourceStatus Value Interpretation Note 1 childCreated 2 childDeleted 3 Updated 4 Deleted NOTE: See clause 7.4.1.1 "Definition of Notification". |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.20 m2m:status | This is used for [software], [firmware] resources. Table 6.3.3.2.20-1: Interpretation of status Value Interpretation Note 1 Successful 2 Failure 3 In_Process NOTE: See clauses D.2 and D.3, firmware and software management. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.21 m2m:batteryStatus | This is used for [battery] resource. Table 6.3.3.2.21-1: Interpretation of batteryStatus Value Interpretation Note 1 NORMAL The battery is operating normally and not on power. 2 CHARGING The battery is currently charging. 3 CHARGING_COMPLETE The battery is fully charged and still on power. 4 DAMAGED The battery has som... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.22 m2m:mgmtDefinition | This is used for <mgmtObj> resource. Table 6.3.3.2.22-1: Interpretation of mgmtDefinition Value Interpretation Note 1001 [firmware] 1002 software 1003 memory 1004 areaNwkInfo 1005 areaNwkDeviceInfo 1006 battery 1007 deviceInfo 1008 deviceCapability 1009 reboot 1010 eventLog 1011 cmdhPolicy 1012 activeCmdhPolicy 1013 cm... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.23 m2m:logTypeId | Used for the logTypeId attribute of [eventLog] Management Resource. Table 6.3.3.2.23-1: Interpretation of logTypeId Value Interpretation Note 1 System 2 Security 3 Event 4 Trace 5 Panic |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.24 m2m:logStatus | Used for the logStatus attribute of [eventLog] Management Resource. Table 6.3.3.2.24-1: Interpretation of logStatus Value Interpretation Note 1 Started the logging activity is started 2 Stopped the logging activity is stopped 3 Unknown the current status of the logging activity is unknown. 4 NotPresent the log data is ... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.25 m2m:eventType | Used for eventType attribute in <eventConfig> resource. Table 6.3.3.2.25-1: Interpretation of eventType Value Interpretation Note 1 DATAOPERATION 2 STORAGEBASED 3 TIMERBASED NOTE: See clause 7.3.24 "Resource Type eventConfig". |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.26 m2m: statsRuleStatusType | Used for statsRuleStatusType attribute in <statsCollect> resource. Table 6.3.3.2.26-1: Interpretation of statsRuleStatusType Value Interpretation Note 1 ACTIVE 2 INACTIVE NOTE: See clause 7.3.25 "Resource Type statsCollect". |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.27 m2m:statModelType | Used for statModelType attribute in <statsCollect> resource. Table 6.3.3.2.27-1: Interpretation of statModelType Value Interpretation Note 1 EVENTBASED NOTE: See clause 7.3.25 "Resource Type statsCollect". |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.28 m2m:encodingType | Used for describing encoding type which is applied on the content attribute of the contentInstance resource. Table 6.3.3.2.28-1: Interpretation of encodingType Value Interpretation Note 0 Plain - no transfer encoding is applied 1 base64 encoding (see [9]) is applied on string data 2 base64 encoding (see [9]) is applied... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.29 m2m:accessControlOperations | Used for accessControlPolicys. Table 6.3.3.2.29-1: Interpretation of accessControlOperations Value Interpretation Note 1 CREATE 2 RETRIEVE 4 UPDATE 8 DELETE 16 DISCOVERY 32 NOTIFY NOTE: Combinations of these values are specified by adding them together. For example the value 5 is interpreted as "CREATE and UPDATE". |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.3.2.30 m2m:SRole-ID | Used for <m2mServiceSubscriptionProfile>. Table 6.3.3.2.30-1: Interpretation of SRole-ID Value Interpretation Note "01-001" Software Management "02-001" Device Configuration "02-002" Device Diagnostics and Management "02-003" Device Firmware Management "02-004" Device Topology "03-001" Location "04-001" Basic Data "05-... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4 Complex data types | The present clause defines structured information for specific use in oneM2M protocol. These types are defined to be xs:sequence complex types, unless specified otherwise. XML Schema data type definitions for these data types can be found in the XSD file called CDT-commonTypes-v1_0_0.xsd. In addition, each oneM2M resou... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.1 m2m:deliveryMetaData | Used for deliveryMetaData attribute in <delivery> resource. Table 6.3.4.1-1: Type Definition of m2m:deliveryMetaData Element Path Element Data Type Multiplicity Note tracingOption xs:boolean 1 tracingInfo m2m:listOfM2MID 0..1 ETSI ETSI TS 118 104 V1.0.0 (2015-02) 41 |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.2 m2m:aggregatedRequest | Used for aggregatedRequest attribute in <delivery> resource, and m2m:aggregatedRequest data type. Table 6.3.4.2-1: Type Definition of m2m:aggregatedRequest Element Path Element Data Type Multiplicity Note request (anonymous) 1..n request/operation m2m:operation 1 See clause 6.3.3.2.5 request/to xs:anyURI 1 request/from... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.3 m2m:metaInformation | Used for metaInformation attribute in <request> resource. Table 6.3.4.3-1: Type Definition of m2m:metaInformation Element Path Element Data Type Multiplicity Note resourceType m2m:resourceType 0..1 See clause 6.3.3.2.1 name xs:string 0..1 originatingTimestamp m2m:timestamp 0..1 requestExpirationTimestamp m2m:timestamp ... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.4 m2m:primitiveContent | Used for Content parameter in request/response primitive and the content attribute in <request> resource. See clauses 7.1.1.1 and 7.1.1.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.5 m2m:batchNotify | Used for batchNotify attribute in <subscription> resource. Table 6.3.4.5-1: Type Definition of m2m:batchNotify Element Path Element Data Type Multiplicity Note Number xs:nonNegativeInteger 0..1 Duration xs:duration 0..1 ETSI ETSI TS 118 104 V1.0.0 (2015-02) 42 |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.6 m2m:eventNotificationCriteria | Used for eventNotificationCriteria of a <subscription> resource. Table 6.3.4.6-1:Type Definition of m2m:eventNotificationCriteria Element Path Element Data Type Multiplicity Note createdBefore m2m:timestamp 0..1 createdAfter m2m:timestamp 0..1 modifiedSince m2m:timestamp 0..1 unmodifiedSince m2m:timestamp 0..1 stateTag... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.7 m2m:filterCriteria | Used indirectly in the <request> resource and for the Filter Criteria parameter in a request. Table 6.3.4.7-1: Type Definition of m2m:filterCriteria Element Path Element Data Type Mutiplicity Note createdBefore m2m:timestamp 0..1 createdAfter m2m:timestamp 0..1 modifiedSince m2m:timestamp 0..1 unmodifiedSince m2m:times... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.8 m2m:attribute | Used in m2m:eventNotificationCriteria and m2m:filterCriteria. Table 6.3.4.8-1: Type Definition of m2m:attribute Element Path Element Data Type Multiplicity Note @name xs:NCName 1 (base content) xs:anyType 1 ETSI ETSI TS 118 104 V1.0.0 (2015-02) 43 |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.9 m2m:attributeList | Used in the Content parameter of a Primitive. Table 6.3.4.9-1: Type Definition of m2m:attributeList Element Path Element Data Type Multiplicity Note attribute m2m:attribute 1..n |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.10 m2m:scheduleEntries | Table 6.3.4.10-1: Type Definition of m2m:scheduleEntries Element Path Element Data Type Multiplicity Note scheduleEntry m2m:scheduleEntry 1..n |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.11 m2m:aggregatedNotification | Used in the Notification Data Object. Table 6.3.4.11-1: Type Definition of m2m:aggregatedNotification Element Path Element Data Type Multiplicity Note notification m2m:notification 1..n |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.12 m2m:notification | Table 6.3.4.12-1: Type Definition of m2m:notification Element Path Element Data Type Multiplicity Note notificationEvent (anonymous) 0..1 notificationEvent/representation xs:anyType 0..1 Representation of resource modification in XML/JSON representation. notificationEvent/resourceStatus m2m:resourceStatus 0..1 notifica... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.13 m2m:actionStatus | Table 6.3.4.13-1: Type Definition of m2m:actionStatus Element Path Element Data Type Multiplicity Note action xs:anyURI 0..1 Reference to the action (represented by a resource attribute) being performed status m2m:status 0..1 Indicates the status of the operation is successful, failure or in process. See Table 6.3.2.2 ... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.14 m2m:anyArgType | Table 6.3.4.14-1: Type Definition of m2m:anyArgType Element Path Element Data Type Multiplicity Note name xs:NCName type xs:anyType |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.15 m2m:resetArgsType | Table 6.3.4.15-1: Type Definition of m2m:resetArgsType Element Path Element Data Type Multiplicity Note anyArg m2m:anyArgType 0..n |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.16 m2m:rebootArgsType | Table 6.3.4.16-1: Type Definition of m2m:rebootArgsType Element Path Element Data Type Multiplicity Note anyArg m2m:anyArgType 0..n |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.17 m2m:uploadArgsTypes | Table 6.3.4.17-1: Type Definition of m2m:uploadArgsType Element Path Element Data Type Multiplicity Note fileType xs:string 1 URL xs:anyURI 1 username xs:string 1 password xs:string 1 anyArg m2m:anyArgType 0..n |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.18 m2m:downloadArgsType | Table 6.3.4.18-1: Type Definition of m2m:downloadArgsType Element Path Element Data Type Multiplicity Note fileType xs:string 1 URL xs:anyURI 1 username xs:string 1 password xs:string 1 filesize xs:positiveInteger 1 targetFile xs:string 1 delaySeconds xs:positiveInteger 1 successURL xs:anyURI 1 startTime m2m:timestamp ... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.19 m2m:softwareInstallArgsType | Table 6.3.4.19-1: Type Definition of m2m:softwareInstallArgsType Element Path Element Data Type Multiplicity Note URL xs:anyURI 1 UUID xs:string 1 username xs:string 1 password xs:string 1 executionEnvRef xs:string 1 anyArg m2m:anyArgType 0..n |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.20 m2m:softwareUpdateArgsType | Table 6.3.4.20-1: Type Definition of m2m:softwareUpdateArgsType Element Path Element Data Type Multiplicity Note UUID xs:string 1 version xs:string 1 URL xs:anyURI 1 username xs:string 1 password xs:string 1 executionEnvRef xs:string 1 anyArg m2m:anyArgType 0..n |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.21 m2m:softwareUninstallArgsType | Table 6.3.4.21-1: Type Definition of m2m:softwareUninstallArgsType Element Path Element Data Type Multiplicity Note UUID xs:string 1 version xs:string 1 executionEnvRef xs:string 1 anyArg m2m:anyArgType 0..n |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.22 m2m:execReqArgsListType | Table 6.3.4.22-1: Type Definition of m2m:execReqArgsListType Element Path Element Data Type Multiplicity Note reset m2m:resetArgsType 0..n reboot m2m:rebootArgsType 0..n upload m2m:downloadArgsType 0..n download m2m:downloadArgsType 0..n softwareInstall m2m:softwareInstallArgsType 0..n softwareUpdate m2m:softwareUpdate... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.23 m2m:mgmtLinkRef | Table 6.3.4.23-1: Type Definition of m2m:mgmtLinkRef Element Path Element Data Type Multiplicity Note (base content) xs:anyURI 1 URI (of type xs:anyURI) with name and type attributes. @name xs:string 1 The name attribute represents the name of the referenced resource instance. @type m2m:mgmtDefinition 1 The type attrib... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.24 m2m:resourceWrapper | Table 6.3.4.24-1: Type Definition of m2m:resourceWrapper Element Path Element Data Type Multiplicity Note (base content) m2m:resource 1 Resource element as described in clause 7.3. @URI xs:anyURI 1 Hierarchical URI of the resource. Table 6.3.4.24-1, names of XML schema attributes are prefixed with a "@" character to di... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.25 m2m:setOfAcrs | Table 6.3.4.25-1: Type Definition of m2m:setOfAcrs Element Path Element Data Type Multiplicity Note accessControlRules m2m:accessControlRule 1..n Data type of privileges and selfPrivileges attributes |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.26 m2m:accessControlRule | Table 6.3.4.26-1: Type Definition of m2m:accessControlRule Element Path Element Data Type Multiplicity Note accesscControlOriginators list of xs:anyURI 1 accessControlOperations m2m:accessControlOperation s 1 accessControlContexts 0..1 accessControlContexts/accessControlWind ow m2m:scheduleEntry 0..n accessControlConte... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.27 m2m:locationRegion | Table 6.3.4.27-1: Type Definition of m2m:locationRegion Element Path Element Data Type Multiplicity Note circRegion List of 3 xs:float 0..1 The values represent latitude ( ±90 degrees), longitude (±180 degrees), and radius (metres) countryCode list of m2m:countryCode 0..1 This is an xs:choice. A locationRegion shall co... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.28 m2m:childResourceRef | Table 6.3.4.28-1: Type Definition of m2m:childResourceRef Element Path Element Data Type Multiplicity Note (base content) xs:anyURI 1 URI of the child resource @name xs:string 1 Gives the name of the child resource pointed to by the URI @type m2m:resourceType 1 Gives the resourceType of the child resource pointed to by... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.29 m2m:responseTypeInfo | Table 6.3.4.29-1: Type Definition of m2m:responseTypeInfo Element Path Element Data Type Multiplicity Note responseType m2m:responseType 1 See clause 6.3.3.2.6 notificationURI xs:anyURI 0..unbounded This element may be included only when the responseType is set to "2" (nonBlockingRequestAsynch) |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.