hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.24.2.4 Delete | Originator: No change from the generic procedure in clause 7.2.2.1. Receiver: No change from the generic procedure in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.25 Resource Type <statsCollect> | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.25.1 Introduction | The <statsCollect> resource controls the collection of statistics information on an IN-CSE. Information in an associated <eventConfig> resource shall be used by the IN-CSE or IN-AE to define specific event-related triggers. Additional description of the <statsCollect> resource is contained in clauses 9.6.25 and 10.2.15 of ETSI TS 118 101 [6]. Table 7.4.25.1-1: Data type definition of <statsCollect> Data Type ID File Name Note statsCollect CDT-statsCollect-v2_7_0.xsd Table 7.4.25.1-2: Universal/Common Attributes of <statsCollect> resource Attribute Name Request Optionality Create Update @resourceName O NP resourceType NP NP resourceID NP NP parentID NP NP accessControlPolicyI Ds O O creationTime NP NP expirationTime O O lastModifiedTime NP NP labels O O creator O NP dynamicAuthorization ConsultationIDs O O ETSI ETSI TS 118 104 V2.7.1 (2016-10) 170 oneM2M TS-0004 version 2.7.1 Release 2 Table 7.4.25.1-3: Resource Specific Attributes of <statsCollect> resource Attribute Name Request Optionality Data Type Default Value and Constraints Create Update statsCollectID NP NP xs:string Unique ID (within SP domain) for each instance of collected statistics No default collectingEntityID M NP m2m:ID Unique ID of entity (e.g. IN-AE, IN-CSE) requesting the collection of statistics No default collectedEntityID M NP m2m:ID Unique ID of entity (e.g. AE, CSE) for which statistics will be collected No default statsRuleStatus M O m2m:statsRuleStatusTy pe ACTIVE INACTIVE No default statModel M O m2m:statModelType EVENTBASED Default=EVENTBASE D collectPeriod O O m2m:scheduleEntries No default (see Table 7.4.9.1-3for string format) eventID O O xs:string Uniquely identifies a configurable event No default (present when statModel is set to EVENTBASED; corresponds to an eventID attribute in an <eventConfig> resource that defines a specific event for collection) Table 7.4.25.1-4: Child Resources of <statsCollect> resource Child Resource Type Child Resource Name Multiplicity Ref. to Resource Type Definition <subscription> [variable] 0..n Clause 7.4.8 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.25.2 <statsCollect> resource-specific procedure on CRUD operations | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.25.2.1 Create | Originator: This procedure follows the Generic Resource Request Procedure for Originator specified in clause 7.2.2.1, with the following <statsCollect> resource-specific updates. Resource-specific operation before Orig-1.0: 1) The Originator shall generate and populate a representation of the <statsCollect> resource to produce the desired collection scenario, with the exception of statsCollectID (which is populated by the IN-CSE). If statModel is set to EVENT-BASED then the Originator shall provide a value for eventID that corresponds to an eventID value stored in an <eventConfig> resource (which defines the event triggers to be used). See Table 7.4.25.1-3 for value restrictions and default settings pertaining to the attributes of <statsCollect>. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 171 oneM2M TS-0004 version 2.7.1 Release 2 Receiver: This procedure follows the Generic Request Procedure for Receiver specified in clause 7.2.2.2, with the following <statsCollect> resource-specific updates. Resource-specific operation before Recv-6.2: 1) If the to primitive parameter addresses a receiver CSE that is not an IN-CSE, then the request shall be rejected with a Response Status Code indicating "BAD_REQUEST" error. Resource-specific operation before Recv-6.6 and after Recv-6.5: 1) The receiver IN-CSE shall generate and store a unique (within the Service Provider domain) value for statsCollectID. 2) If status is set to ACTIVE, the IN-CSE shall begin monitoring the conditions defined by the <statsCollect> resource and generating Service Statistics Collection Records as the conditions are met. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.25.2.2 Retrieve | Originator: This procedure follows the Generic Resource Request Procedure for Originator specified in clause 7.2.2.1. Receiver: This procedure follows the Generic Request Procedure for Receiver specified in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.25.2.3 Update | Originator: This procedure follows the Generic Resource Request Procedure for Originator specified in clause 7.2.2.1. Receiver: This procedure follows the Generic Request Procedure for Receiver specified in clause 7.2.2.2, with the following <statsCollect> resource-specific updates. Resource-specific operation before Recv-6.6 and after Recv-6.5: 1) If status is set to ACTIVE, the IN-CSE shall begin monitoring the conditions defined by the <statsCollect> resource and generating Service Statistics Collection Records as the conditions are met. 2) If status is set to INACTIVE, the IN-CSE shall stop monitoring the conditions defined by the <statsCollect> resource. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.25.2.4 Delete | Originator: This procedure follows the Generic Resource Request Procedure for Originator specified in clause 7.2.2.1. Receiver: This procedure follows the Generic Request Procedure for Receiver specified in clause 7.2.2.1. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.26 Announced resource types | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.26.1 Introduction | Instances of certain resource types can be announced by the Hosting CSE to one or more remote CSEs to inform the remote CSEs of the existence of the original resource instance. Table 7.4.26.1-1 lists the resource types which are announceable together with its resource type identifier and the name of the XSD file that specifies its data type. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 172 oneM2M TS-0004 version 2.7.1 Release 2 Resource-specific attributes of a resource type may be declared announceable (mandatory or optional) or not announceable. Clause 9.6 in ETSI TS 118 101 [6] defines which attributes of each resource type are announceable. The universal/common attributes of an announced resource type are listed in table 7.4.26.1-2, together with their request optionality in Create and Update requests (see clause 7.4.1). The announced resource includes a common attribute link which represents a link to the original resource hosted by the original resource-Hosting CSE. The child resources applicable to each announced resource type are listed in Table 9.6.26.1-1 of ETSI TS 118 101 [6]. Table 7.4.26.1-3: Data type definition of announced Resource types Data Type ID File Name Note accessControlPolicyAnnc CDT-accessControlPolicy-v2_7_0.xsd remoteCSEAnnc CDT-remoteCSE-v2_7_0.xsd AEAnnc CDT-AE-v2_7_0.xsd containerAnnc CDT-container-v2_7_0.xsd [flexContainer]Annc See Annex J and ETSI TS 118 123 [39] Announced variants of flexContainer specializations contentInstanceAnnc CDT-contentInstance-v2_7_0.xsd scheduleAnnc CDT-schedule-v2_7_0.xsd locationPolicyAnnc CDT-locationPolicy-v2_7_0.xsd groupAnnc CDT-group-v2_7_0.xsd nodeAnnc CDT-node-v2_7_0.xsd semanticDescriptorAnnc CDT-semanticDescriptor-v2_7_0.xsd timeSeriesAnnc CDT-timeSeries-v2_7_0.xsd timeSeriesInstanceAnnc CDT-timeSeriesInstance-v2_7_0.xsd trafficPatternAnnc CDT-trafficPattern-v2_7_0.xsd genericInterworkingServic e CDT-genericInterworkingService-v2_7_0.xsd genericInterworkingOpera tionInstance CDT-genericInterworkingOperationInstance- v2_7_0.xsd svcObjWrapper CDT-svcObjWrapper-v2_7_0.xsd svcFwWrapper CDT-svcFwWrapper-v2_7_0.xsd allJoynApp CDT-allJoynApp-v2_7_0.xsd allJoynSvcObject CDT-allJoynSvcObject-v2_7_0.xsd allJoynInterface CDT-allJoynInterface-v2_7_0.xsd allJoynMethod CDT-allJoynMethod-v2_7_0.xsd allJoynMethodCall CDT-allJoynMethodCall-v2_7_0.xsd allJoynProperty CDT-allJoynProperty-v2_7_0.xsd Table 7.4.26.1-4: Universal/Common Attributes of announcedResource Attribute Name Request Optionality Create Update @resourceName NP NP resourceType NP NP resourceID NP NP parentID NP NP accessControlPolicyI Ds O O creationTime NP NP expirationTime M O lastModifiedTime NP NP labels O O link M O Each announced resource type has the resource specific attributes that is the subset of the original resource. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 173 oneM2M TS-0004 version 2.7.1 Release 2 Table 7.4.26.1-5: Resource Specific Attributes of announcedResource Attribute Name Request Optionality Data Type Default Value and Constraints Create Update Name of attribute specified as MA M O Same data type as defined for the original resource This attribute shall be set to the same value with the attribute at the original resource Name of attribute specified as OA O O Same data type as defined for the original resource This attribute shall be set to the same value with the attribute at the original resource The procedures defined in the following clause 7.4.26.2 apply to all announced resources regardless of the resource type. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.26.2 Resource specific procedure on CRUD operations | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.26.2.1 Introduction | This clause describes announced resource specific procedure for CRUD operations. The original resource Hosting CSE shall create/update/delete the announced resource as specified at the clause 7.3.3.10 and clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.26.2.2 Create | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.26.2.3 Retrieve | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. In case of the Result Content information is set to the "original-resource", the Recv-6.5 shall be changed as follows: Recv-6.5 "Read the original resource whose address is provided by the link attribute of the announced resource" |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.26.2.4 Update | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2, except that Recv-6.3 is replaced as follows: Recv-6.3 "Check if the value of the From parameter in Request message is identical to the CSE-ID included in the link attribute in the announced resource". ETSI ETSI TS 118 104 V2.7.1 (2016-10) 174 oneM2M TS-0004 version 2.7.1 Release 2 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.26.2.5 Delete | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2, except that Recv-6.3 is replaced as follows: Recv-6.3 "Check if the value of the From parameter in Request message is identical to the CSE-ID included in the link attribute in the announced resource". |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.27 Resource Type latest | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.27.1 Introduction | The <latest> resource is a virtual resource because it does not have a representation. It is a child resource of the <container> resource. Whenever a request addresses the <latest> resource, the Hosting CSE shall apply the request to the latest <contentInstance> resource among all existing <contentInstance> resources of the <container> resource. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.27.2 <latest> Resource Specific Procedure on CRUD Operations | 7.4.27.2.0 Introduction This sub-clause describes <latest> resource specific behaviour for operations. Among operations, only Retrieve and Delete operations shall be allowed for the <latest> resource. 7.4.27.2.1 Create Originator: The <latest> resource shall not be created via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received, the Receiver CSE shall execute the following steps in order. a) "Create an unsuccessful Response primitive" with the Response Status Code indicating "OPERATION_NOT_ALLOWED" error. 2) "Send the Response primitive". 7.4.27.2.2 Retrieve Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.1 except the following modification: Recv-6.2 Check the existence of the latest <contentInstance> resource among all existing <contentInstance> resources in the parent <container> resource. If the resource exists, the subsequent procedures of the Receiver (i.e. after Recv-6.2) shall be performed for the resource. If the resource does not exist, the Hosting CSE shall reject the request with a Response Status Code indicating "NOT_FOUND" error. Recv-6.3: Addion on normal procedure of Recv-6.3 "Check authorization of the Originar", Check the value of disableRetrieval attribute, and if the value is True then the Hosting CSE shall reject the request with a Response Status Code indicating "OPERATION_NOT_ALLOWED" error. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 175 oneM2M TS-0004 version 2.7.1 Release 2 7.4.27.2.3 Update Originator: The <latest> resource shall not be updated via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received, the Receiver CSE shall execute the following steps in order. a) "Create an unsuccessful Response primitive" with the Response Status Code indicating "OPERATION_NOT_ALLOWED" error. b) "Send the Response primitive". 7.4.27.2.4 Delete Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.1 except the following modification: Recv-6.2 Check the existence of the latest <contentInstance> resource among all existing <contentInstance> resources in the parent <container> resource. If the resource exists, the subsequent procedures of the Receiver (i.e. after Recv-6.2) shall be performed for the resource. If the resource does not exist, the Hosting CSE shall reject the request with a Response Status Code indicating "NOT_FOUND" error. Recv-6.3: Addion on normal procedure of Recv-6.3 "Check authorization of the Originar", Check the value of disableRetrieval attribute, and if the value is True then the Hosting CSE shall reject the request with a Response Status Code indicating "OPERATION_NOT_ALLOWED" error. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.28 Resource Type oldest | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.28.1 Introduction | The <oldest> resource is a virtual resource because it does not have a representation. It is a child resource of the <container> resource. Whenever a request addresses the <oldest> resource, the Hosting CSE shall apply the request to the oldest <contentInstance> resource among all existing <contentInstance> resources of the <container> resource. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.28.2 <oldest> Resource Specific Procedure on CRUD Operations | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.28.2.0 Introduction | Among operations, only Retrieve and Delete operations shall be allowed for the <oldest> resource. 7.4.28.2.1 Create Originator: The <oldest> resource shall not be created via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received, the Receiver CSE shall execute the following steps in order. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 176 oneM2M TS-0004 version 2.7.1 Release 2 a) "Create an unsuccessful Response primitive" with the Response Status Code indicating "OPERATION_NOT_ALLOWED" error. b) "Send the Response primitive". 7.4.28.2.2 Retrieve Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.1 except the following modification: Recv-6.2 Check the existence of the oldest <contentInstance> resource among all existing <contentInstance> resources in the parent <container> resource. If the resource exists, the subsequent procedures of the Receiver (i.e. after Recv-6.2) shall be performed for the resource. If the resource does not exist, the Hosting CSE shall reject the request with a Response Status Code indicating "NOT_FOUND" error. Recv-6.3: Addion on normal procedure of Recv-6.3 "Check authorization of the Originar", Check the value of disableRetrieval attribute, and if the value is True then the Hosting CSE shall reject the request with a Response Status Code indicating "OPERATION_NOT_ALLOWED" error. 7.4.28.2.3 Update Originator: The <oldest> resource shall not be updated via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received, the Receiver CSE shall execute the following steps in order. a) "Create an unsuccessful Response primitive" with the Response Status Code indicating "OPERATION_NOT_ALLOWED" error. b) "Send the Response primitive". 7.4.28.2.4 Delete Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.1 except the following modification: Recv-6.2 Check the existence of the oldest <contentInstance> resource among all existing <contentInstance> resources in the parent <container> resource. If the resource exists, the subsequent procedures of the Receiver (i.e. after Recv-6.2) shall be performed for the resource. If the resource does not exist, the Hosting CSE shall reject the request with a Response Status Code indicating "NOT_FOUND" error. Recv-6.3: Addion on normal procedure of Recv-6.3 "Check authorization of the Originar", Check the value of disableRetrieval attribute, and if the value is True then the Hosting CSE shall reject the request with a Response Status Code indicating "OPERATION_NOT_ALLOWED" error. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 177 oneM2M TS-0004 version 2.7.1 Release 2 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.29 Resource Type <serviceSubscribedAppRule > | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.29.1 Introduction | The <serviceSubscribedAppRule> resource represents a rule that defines allowed App-ID and AE-ID combinations that are acceptable for registering an AE on a Registrar CSE. The detailed description can be found in the clause 9.6.29 in ETSI TS 118 101 [6]. Table 7.4.29.1-1: Data type definition of <serviceSubscribedAppRule> resource Data Type ID File Name Note serviceSubscribedAppRule CDT-serviceSubscribedAppRule-v2_7_0.xsd Table 7.4.29.1-2: Universal/Common Attributes of <serviceSubscribedAppRule> resource Attribute Name Request Optionality Create Update resourceType NP NP resourceID NP NP parentID NP NP expirationTime O O accessControlPolicyIDs O O creationTime NP NP lastModifiedTime NP NP labels O O dynamicAuthorizationCon sultationIDs O O Table 7.4.29.1-3: Resource Specific Attributes of <serviceSubscribedAppRule> resource Attribute Name Request Optionality Data Type Default Value and Constraints Create Update applicableCredIDs O O m2m:listOfM2MID allowedApp-IDs O O m2m:listOfM2MID allowedAEs O O m2m:listOfM2MID Table 7.4.29.1-4: Child resources of <serviceSubscribedAppRule> resource Child Resource Type Child Resource Name Multiplicity Ref. to Resource Type Definition <subscription> [variable] 0..n Clause 7.4.8 7.4.29.2 <serviceSubscribedAppRule> resource specific procedure on CRUD operations |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.29.2.0 Introduction | This clause describes <serviceSubscribedAppRule> resource specific primitive behaviour for CRUD operations. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.29.2.1 Create | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 178 oneM2M TS-0004 version 2.7.1 Release 2 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.29.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.29.2.3 Update | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.29.2.4 Delete | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.30 Resource Type <notificationTargetMgmtPolicyRef> | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.30.1 Introduction | This is a child resource of a <subscription> resource. This resource represents reference(s) to the policy to be followed by the Hosting CSE to manage Notification Targets of a resource subscription. The detailed description can be found in clause 9.6.31 in ETSI TS 118 101 Functional Architecture [6]. Table 7.4.30.1-1: Data type definition of <notificationTargetMgmtPolicyRef> resource Data Type ID File Name Note notificationTargetMgmtPolicyRef CDT-notificationTargetMgmtPolicyRef- V2_7_0.xsd Table 7.4.30.1-2: Universal/Common Attributes of <notificationTargetMgmtPolicyRef> resource Attribute Name Request Optionality Create Update @resourceName O NP resourceType NP NP resourceID NP NP parentID NP NP expirationTime O O accessControlPolicyIDs O O creationTime NP NP lastModifiedTime NP NP labels O O ETSI ETSI TS 118 104 V2.7.1 (2016-10) 179 oneM2M TS-0004 version 2.7.1 Release 2 Table 7.4.30.1-3: Resource Specific Attributes of <notificationTargetMgmtPolicyRef> resource Attribute Name Request Optionality Data Type Default Value and Constraints Create Update notificationTargetURI M O list of xs:anyURI No default notificationlPolicyID O O xs:anyURI Table 7.4.30.1-4: Child resources of <notificationTargetMgmtPolicyRef> resource Child Resource Type Child Resource Name Multiplicity Ref. to Resource Type Definition <subscription> [variable] 0..n Clause 7.4.8 7.4.30.2 <notificationTargetMgmtPolicyRef> resource specific procedure on CRUD operations |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.30.2.0 Introduction | This clause describes <notificationTargetMgmtPolicyRef> resource specific primitive behaviour for CRUD operations. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.30.2.1 Create | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2, but with one additional checking to the Recv-6.4 "Check validity of resource representation": 1) The Hosting CSE shall check if Notification Targets in the notificationTargetURI in the request primitive is already exists in other <notificationTargetMgmtPolicyRefs> resources which are the children of targeted <subscription> resource. If so, the Hosting CSE shall send the response with Response Status Code indicating "CONFLICT" error. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.30.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.30.2.3 Update | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.30.2.4 Delete | Originator: No change from the generic procedures in clause 7.2.2.1. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 180 oneM2M TS-0004 version 2.7.1 Release 2 Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.31 Resource Type <notificationTargetPolicy> | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.31.1 Introduction | This is a child resource of the <CSEBase> resource. This resources represents a policy to be followed by the Hosting CSE to manage Notification Targets of a resource subscription. Each policy has Notification Target deletion rules. The detailed description can be found in clause 9.6.32 in ETSI TS 118 101 Functional Architecture [6]. Table 7.4.31.1-1: Data type definition of <notificationTargetPolicy> resource Data Type ID File Name Note notificationTargetPolicy CDT- notificationTargetPolicy -v2_7_0.xsd Table 7.4.31.1-2: Universal/Common Attributes of <notificationTargetPolicy> resource Attribute Name Request Optionality Create Update @resourceName O NP resourceType NP NP resourceID NP NP parentID NP NP expirationTime O O accessControlPolicyIDs O O creationTime NP NP lastModifiedTime NP NP labels O O creator O NP Table 7.4.31.1-3: Resource Specific Attributes of <notificationTargetPolicy> resource Attribute Name Request Optionality Data Type Default Value and Constraints Create Update action O NP m2m:notificationTargetPol icyAction No default policyLabel O O xs:token No default rulesRelationship O O m2m:logicalOperator This attribute shall have a value either "AND" or "OR" when more than one <policyDeletionRules > child resource is specified. Table 7.4.31.1-4: Child resources of <notificationTargetPolicy> resource Child Resource Type Child Resource Name Multiplicity Ref. to Resource Type Definition <policyDeletionRules> [variable] 0..2 Clause 7.4.32 <subscription> [variable] 0..n Clause 7.4.8 ETSI ETSI TS 118 104 V2.7.1 (2016-10) 181 oneM2M TS-0004 version 2.7.1 Release 2 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.31.2 <notificationTargetPolicy> resource specific procedure on CRUD operations | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.31.2.0 Introduction | This clause describes <serviceSubscribedAppRule> resource specific primitive behaviour for CRUD operations. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.31.2.1 Create | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.31.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.31.2.3 Update | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.31.2.4 Delete | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.32 Resource Type <policyDeletionRules> | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.32.1 Introduction | This is a child resource of a <notificationTargetPolicy> resource. This resources represents rules to be applied by the Hosting CSE during Notification Target policy execution. Multiple rules are combined with AND or OR logical operation. The detailed description can be found in clause 9.6.33 in ETSI TS 118 101 Functional Architecture [6]. Table 7.4.32.1-1: Data type definition of <policyDeletionRules> resource Data Type ID File Name Note policyDeletionRules CDT- policyDeletionRules -v2_7_0.xsd ETSI ETSI TS 118 104 V2.7.1 (2016-10) 182 oneM2M TS-0004 version 2.7.1 Release 2 Table 7.4.32.1-2: Universal/Common Attributes of <policyDeletionRules> resource Attribute Name Request Optionality Create Update @resourceName O NP resourceType NP NP resourceID NP NP parentID NP NP expirationTime O O accessControlPolicyIDs O O creationTime NP NP lastModifiedTime NP NP labels O O Table 7.4.32.1-3: Resource Specific Attributes of <policyDeletionRules> resource Attribute Name Request Optionality Data Type Default Value and Constraints Create Update deletionRules O NP m2m:deletionContexts No default deletionRulesRelation O O m2m:logicalOperator "OR" operation Table 7.4.32.1-4: Child resources of <policyDeletionRules> resource Child Resource Type Child Resource Name Multiplicity Ref. to Resource Type Definition <subscription> [variable] 0..n Clause 7.4.8 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.32.2 <policyDeletionRules> resource specific procedure on CRUD operations | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.32.2.0 Introduction | This clause describes <policyDeletionRules> resource specific primitive behaviour for CRUD operations. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.32.2.1 Create | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2, but with one additional checking to the Recv-6.2 "Check existence of the addressed resource": 1) The Hosting CSE shall check if there are more than two existing <policyDeletionRules> resources as the children of the targeted <notificationTargetPolicy> resource. If so, the Hosting CSE shall send the response with Response Status Code indicating "CONFLICT" error. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.32.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 183 oneM2M TS-0004 version 2.7.1 Release 2 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.32.2.3 Update | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.32.2.4 Delete | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.33 Resource Type <notificationTargeSelfReference> | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.33.1 Introduction | This is a child resource of a <subscription> resource. It is a virtual resource type so it has no resource representation nor XSD. Only the Delete operation is applicable targeting this resource. 7.4.33.2 <notificationTargetSelfReference> resource specific procedure on CRUD operations |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.33.2.0 Introduction | This clause describes <serviceSubscribedAppRule> resource specific primitive behaviour for CRUD operations. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.33.2.1 Create | The <latest> resource is not created via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received, the Receiver CSE shall execute the following steps in order. a) "Create an unsuccessful Response primitive" with the Response Status Code indicating "OPERATION_NOT_ALLOWED" error. 2) "Send the Response primitive". |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.33.2.2 Retrieve | The <latest> resource is not created via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received, the Receiver CSE shall execute the following steps in order. a) "Create an unsuccessful Response primitive" with the Response Status Code indicating "OPERATION_NOT_ALLOWED" error. b) "Send the Response primitive". ETSI ETSI TS 118 104 V2.7.1 (2016-10) 184 oneM2M TS-0004 version 2.7.1 Release 2 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.33.2.3 Update | The <latest> resource is not created via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received, the Receiver CSE shall execute the following steps in order. a) "Create an unsuccessful Response primitive" with the Response Status Code indicating "OPERATION_NOT_ALLOWED" error. b) "Send the Response primitive". |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.33.2.4 Delete | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2 except the Recv-6.5 "Create/Update/Retrieve/Delete/Notify operation is performed". The Hosting CSE shall perform the Delete operation procedure for this resource type as follows: 1) Check if the Originator is listed as one of the Notification Targets in the notificationTargetURI attribute of a < notificationTargetMgmtPolicyRef > resource which is the sibling resource of the targeted <notificationTargetSelfReference > resource. If there is a resource, then the Hosting CSE shall fetch the <notificationTargetPolicy> resource linked from notificationPolicyID attribute. If there is no such resource, then the Hosting CSE shall fetch the default <notificationTargetPolicy> resource among children of the <CSEBase> resource as: a) The Hosting CSE shall find a <notificationTargetPolicy> resource which has the policyLabel attribute set as "Default" and the creator attribute set as the Originator ID. 2) If there is no such resource in step a), then the Hosting CSE shall find the <notificationTargetPolicy> resource which has the policyLabel attribute set as "Default". Note that there is always the default <notificationTargetPolicy> resource created by the M2M Service Provider. 3) When there is one <policyDeletionRules> resource as a child of the fetched <notificationTargetPolicy> resource, the Hosting CSE evaluates the <policyDeletionRules> resource and perform action as specified in the action attribute. When there are two <policyDeletionRules> resources as a children of the fetched <notificationTargetPolicy> resource, the Hosting CSE evaluates the two <policyDeletionRules> resources and perform logical operation(i.e. AND or OR) as specified in the rulesReleationShip attribute for the two evaluation results. If the logical operation result is TRUE, then the Hosting CSE shall perform the action as specified in the action attribute. The action is performed as follows: a) If the action is the "accept request", the Hosting CSE shall remove the Originator in the notificationURI attribute in the <subscription> resource. 4) If the action is the "reject request", the Hosting CSE shall send the response with Response Status Code indicating "ORIGINATOR_HAS_NO_PRIVILEGE" error. 5) If the action is the "seek authorization from subscription originator before responding", the Hosting CSE shall send the Notify request with the information of the indication for Notification Target deletion, the Originator ID and the subscription reference from the Originator's request to the <subscription> resource creator (i.e. the creator attribute of the <subscription> resource). If the Hosting CSE gets the response from the creator with Notification Target removal allowance indication, then the Hosting CSE shall remove the Originator in the notificationURI attribute in the <subscription> resource. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 185 oneM2M TS-0004 version 2.7.1 Release 2 6) If the action is the "inform the subscription originator without taking any action", the Hosting CSE shall send the Notify request with the information of the indication for Notification Target deletion, the Originator ID and the subscription reference from the Originator's request to the <subscription> resource creator(i.e. the creator attribute of the <subscription> resource) and send the response to the Originator with Response Status Code indicating "ORIGINATOR_HAS_NO_PRIVILEGE" error. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.34 Resource Type <semanticDescriptor> | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.34.1 Introduction | The <semanticDescriptor> resource is used to store a semantic description pertaining to a resource and potentially sub- resources. Such a description shall be according to subject-predicate-object triples as defined in the RDF graph-based data model [4]. The detailed description can be found in clause 9.6.34 in ETSI TS 118 101 Functional Architecture [6]. Table 7.4.34.1-1: Data type definition of <semanticDescriptor> resource Data Type ID File Name Note semanticDescriptor CDT- semanticDescriptor -v2_7_0.xsd Table 7.4.34.1-2: Universal/Common Attributes of <semanticDescriptor> resource Attribute Name Request Optionality Create Update @resourceName O NP resourceType NP NP resourceID NP NP parentID NP NP expirationTime O O accessControlPolicyIDs O O creationTime NP NP lastModifiedTime NP NP labels O O announceTo O O announcedAttribute O O creator O NP Table 7.4.34.1-3: Resource Specific Attributes of <semanticDescriptor> resource Attribute Name Request Optionality Data Type Default Value and Constraints Create Update descriptorRepresenat ion M O m2m:descriptorRepresent ation application/rdf+xml:1 semanticOpExec NP O m2m:sparql No default descriptor M O xs:base64Binary No default ontologyRef O O xs:anyURI No default relatedSemantics O O List of xs:anyURI No default Table 7.4.34.1-4: Child resources of <semanticDescriptor> resource Child Resource Type Child Resource Name Multiplicity Ref. to Resource Type Definition <subscription> [variable] 0..n Clause 7.4.8 ETSI ETSI TS 118 104 V2.7.1 (2016-10) 186 oneM2M TS-0004 version 2.7.1 Release 2 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.34.2 <semanticDescriptor> resource specific procedure on CRUD operations | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.34.2.0 Introduction | This clause describes <semanticDescriptor> resource specific primitive behaviour for CRUD operations. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.34.2.1 Create | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2 with the following exception: 1) Primitive specific operation on Recv-6.4 "Check validity of resource representation for the given resource type": a) The Hosting CSE shall check that the descriptor attribute conforms to the RDF/XML syntax as defined in RDF 1.1 XML Syntax [33] b) If the descriptor attribute does not conform, the Hosting CSE shall return failure information with additional error information as defined in clause 7.2.1.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.34.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2 with the following exception: • The semanticOpExec attribute is never returned in the response. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.34.2.3 Update | Originator: No change from the generic procedures in clause 7.2.2.1 with the following exception: • The descriptor attribute can be updated using SPARQL as follows: Primitive specific operation on Orig-1.0 "Compose Request primitive": The originator creates a request to update the semanticOpExec attribute. The value of this attribute is set to a SPARQL request that includes INSERT, DELETE, or DELETE/INSERT with conditional SPARQL statements as defined in the SPARQL query language [w]. Receiver: No change from the generic procedures in clause 7.2.2.2 with the following exceptions: 1) Primitive specific operation on Recv-6.4 "Check validity of resource representation for the given resource type": a) If both semanticOpExec and descriptor attributes exist, the Receiver shall generate a Response Status Code indicating a "NOT_ACCEPTABLE" error. b) If semanticOpExec attribute exists in the Request check that the syntax of its content corresponds to a valid SPARQL query request [33]. If the content does not correspond to a valid SPARQL query request, the Receiver shall generate a Response Status Code indicating a "NOT_ACCEPTABLE" error. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 187 oneM2M TS-0004 version 2.7.1 Release 2 c) If the descriptor attribute exists in the Request, check that the syntax of its content corresponds to a valid the RDF/XML syntax as defined in RDF 1.1 XML Syntax [34]. If the content does not correspond to a valid RDF/XML syntax, the Receiver shall generate a Response Status Code indicating a "NOT_ACCEPTABLE" error. 2) Primitive specific operation on Recv-6.5 "Create/Update/Retrieve/Delete/Notify operation is performed": a) If semanticOpExec attribute exists in the Request, the Hosting CSE shall update the semantic triples in the descriptor attribute according to SPARQL update request in the content attribute. If the SPARQL update request can not be executed, the Hosting CSE shall create an unsuccessful Response primitive" with the Response Status Code indicating "SPARQL_UPDATE_ERROR", otherwise proceed to step Recv-6.6. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.34.2.4 Delete | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.35 Resource Type <semanticFanOutPoint> | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.35.1 Introduction | The <semanticFanOutPoint> resource is a virtual resource because it does not have a representation; there are no common attributes, resource specific attributes or xsd. It is the child resource of a <group> resource. A <semanticFanOutPoint> can be addressed in one of two ways: • Using the URI retrieved from its parent <group> resource; or • Using a hierarchical URI formed by taking the hierarchical URI of the parent <group> and appending the string /semanticFanOutPoint to that URI Only Retrieve requests to the <semanticFanOutPoint> resource are valid, the other operations are not allowed based on the syntax check step at the Receiver. When a Retrieve request is received by the <semanticFanOutPoint> it triggers a semantic discovery procedure. Semantic resource discovery is used to find resources in a CSE based on the semantic descriptions contained in the descriptor attribute of <semanticDescriptor> resources. Since an overall semantic description (forming a graph [i.5]) may be distributed across a set of <semanticDescriptor> resources, the semantic descriptions have to be retrieved (before or as needed) during the execution of the discovery request. When using <semanticFanOutPoint>, the graph is distributed across the descriptors of the members of the parent <group> resource. The Group Hosting CSE indicates support for and availability of semantic functionality by setting the semanticSupportIndicator attribute of the <group> resource to TRUE. Targeting the <semanticFanOutPoint> virtual resource results in creating and distributing retrieve operations to all the member resources. The results of the retrieve requests are used to form an aggregated semantic description containing the overall graph, on which the graph pattern matching is performed. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.35.2 <semanticFanOutPoint> resource specific procedure on CRUD operations | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.35.2.0 Introduction | This clause describes <semanticFanOutPoint> resource specific primitive behaviour for CRUD operations. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 188 oneM2M TS-0004 version 2.7.1 Release 2 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.35.2.1 Create | Originator: The <semanticFanOutPoint> resource shall not support Create operations via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": If the request is received, the Receiver CSE shall execute the following steps in order. 1) "Create an unsuccessful Response primitive" with the Response Status Code indicating "OPERATION_NOT_ALLOWED" error. 2) "Send the Response primitive". |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.35.2.2 Retrieve | Originator: No primitive specific operations. Receiver: The Receiver shall follow the steps from Recv-1.0 to Recv-6.2 specified in clause 7.2.2.2 Generic Resource Request Procedure for Receiver, with the following primitive specific operations: After Recv-1.0 "Check the validity of received request primitive": check that the syntax of the semanticsFilter corresponds to a valid SPARQL query request [33]. If the semanticsFilter entry does not correspond to a valid SPARQL query request, the Receiver shall generate a Response Status Code indicating a "NOT_ACCEPTABLE" error. After Recv-6.2 "Check existence of the addressed resource": 1) Check that the semanticSupportIndicator of the parent <group> resource is set to TRUE. 2) Check the authorization of the Originator based on the membersAccessControlPolicyIDs of the parent group resource. In the case the membersAccessControlPolicyIDs is not provided, the accessControlPolicyIDs of the parent group resource shall be used. 3) Fanout <semanticDescriptor> Retrieve Requests to each CSE hosting sub-groups or members as follows: For each group member, the Hosting CSE shall perform the following steps: a) The primitive parameters From and To shall be mapped to corresponding Retrieve Requests to be sent out to each member of the group. The primitive parameter From shall be directly used. The prefix of primitive parameter To i.e. <URI of group resource>/semanticFanOutPoint shall be replaced by hierarchical URIs derived from the attribute memberIDs of the group resource. 7) The group hosting CSE shall execute "Compose Request primitives" using the primitive parameter semanticsFilter set to FALSE. 8) "Send the Request to the receiver CSE". 9) "Wait for Response primitives". Once the Responses to the Retrieve Requests have been received, proceed to the following step. 4) Aggregate the descriptors from the Retrieve Responses and deliver the content for SPARQL processing, along with the semanticFilter content 5) Wait for a SPARQL processing response. 6) Perform Recv-6.7 "Create a success response" where the Response shall include the SPARQL processing result. 7) Perform Recv-6.8 and the procedure is terminated. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 189 oneM2M TS-0004 version 2.7.1 Release 2 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.35.2.3 Update | Originator: The < semanticFanOutPoint> resource shall not support Update operations via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": If the request is received, the Receiver CSE shall execute the following steps in order. 1) "Create an unsuccessful Response primitive" with the Response Status Code indicating "OPERATION_NOT_ALLOWED" error. 2) "Send the Response primitive". |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.35.2.4 Delete | Originator: The < semanticFanOutPoint> resource shall not support Delete operations via API. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": If the request is received, the Receiver CSE shall execute the following steps in order. 1) "Create an unsuccessful Response primitive" with the Response Status Code indicating "OPERATION_NOT_ALLOWED" error. 2) "Send the Response primitive". |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.36 Resource Type <dynamicAuthorizationConsultation> | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.36.1 Introduction | A < dynamicAuthorizationConsultation> resource shall be used by a CSE to perform consultation-based dynamic access control to resources as specified in the present document and in ETSI TS 118 103 [7]. The detailed description can be found in clause 9.6.43 in ETSI TS 118 101 Functional Architecture [6]. Table 7.4.36.1-1: Data type definition of <dynamicAuthorizationConsultation> resource Data Type ID File Name Note dynamicAuthorizationConsultation CDT-dynamicAuthorizationConsultaiton- v2_7_0.xsd ETSI ETSI TS 118 104 V2.7.1 (2016-10) 190 oneM2M TS-0004 version 2.7.1 Release 2 Table 7.4.36.1-2: Universal/Common Attributes of <dynamicAuthorizationConsultation > resource Attribute Name Request Optionality Create Update @resourceName O NP resourceType NP NP resourceID NP NP parentID NP NP expirationTime O O accessControlPolicyIDs O O creationTime NP NP lastModifiedTime NP NP labels O O dynamicAuthorizationCon sultationIDs O O Table 7.4.36.1-3: Resource Specific Attributes of <dynamicAuthorizationConsultation> resource Attribute Name Request Optionality Data Type Default Value and Constraints Create Update dynamicAuthorization Enabled M O xs:boolean No default dynamicAuthorization PoA O O list of xs:anyURI No default dynamicAuthorization Lifetime O O m2m:timestamp No default 7.4.36.2 <dynamicAuthorizationConsultation> resource specific procedure on CRUD operations |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.36.2.0 Introduction | This clause describes <dynamicAuthorizationConsultation> resource specific primitive behaviour for CRUD operations. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.36.2.1 Create | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.36.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.36.2.3 Update | Originator: No change from the generic procedures in clause 7.2.2.1. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 191 oneM2M TS-0004 version 2.7.1 Release 2 Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.36.2.4 Delete | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.37 Resource Type <flexContainer> | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.37.1 Introduction | This resource represents a customizable container for data instances. It is a template for the definition of flexible specializations of data containers. The detailed description can be found in clause 9.6.35 in ETSI TS 118 101 [6]. There are multiple specializations of <flexContainer> specified by oneM2M. Each of these specializations has its own schema file. There is no separate schema file just for <flexContainer>, however the XML schema types for the specializations all conform to the pattern described in this clause. The XSD of <flexContainer> specializations may use a targetNamespace other than the one identified by the m2m: prefix. Specializations of <flexContainer> which employ the namespace prefix m2m: are defined in annex J. Specialization of <flexContainer> which employ the namespace prefix hd: for Home Domain use cases are specified in ETSI TS 118 123 [39]. The following resource types are allowed to include <flexContainer> specializations as children: <CSEBase>, <AE>, <remoteCSE> and <container>. Table 7.4.37.1-1: Universal/Common Attributes of <flexContainer> resource Attribute Name Request Optionality Create Update @resourceName O NP resourceType NP NP resourceID NP NP parentID NP NP accessControlPolicyIDs O O creationTime NP NP expirationTime O O lastModifiedTime NP NP stateTag NP NP labels O O announceTo O O announcedAttribute O O creator O NP dynamicAuthorizationConsultationIDs O O ETSI ETSI TS 118 104 V2.7.1 (2016-10) 192 oneM2M TS-0004 version 2.7.1 Release 2 Table 7.4.37.1-2: Resource Specific Attributes of <flexContainer> resource Attribute Name Request Optionality Data Type Default Value and Constraints Create Update containerDefinition M NP xs:anyURI No default ontologyRef O O xs:anyURI No default [customAttribute] O O Name and data type are defined in the specification document or XSD file identified by the value of containerDefinition attribute. No default. Table 7.4.37.1-3: Child Resources of <flexContainer> resource Child Resource Type Child Resource Name Multiplicity Ref. to in Resource Type Definition <semanticDescriptor> [variable] 0..n Clause 7.4.34 <subscription> [variable] 0..n Clause 7.4.8 <container> [variable] 0..n Clause 7.4.6 <flexContainer> [variable] 0..n Clause 7.4.37 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.37.2 <flexContainer> resource specific procedure on CRUD operations | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.37.2.0 Introduction | This clause describes <flexContainer> resource specific behaviour for CRUD operations. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.37.2.1 Create | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2, |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.37.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.37.2.3 Update | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 193 oneM2M TS-0004 version 2.7.1 Release 2 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.37.2.4 Delete | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.38 Resource Type <timeSeries> | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.38.1 Introduction | The resource represents a container for Time Series Data instances. It is used to share information with other entities and potentially to track, detect and report the missing data in Time Series. A <timeSeries> resource has no associated content, only attributes and child resources. The detailed description can be found in clause 9.6.36 in ETSI TS 118 101 [6]. Table 7.4.38.1-1: Data type definition of <timeSeries> resource Data Type ID File Name Note timeSeries CDT-timeSeries-v2_7_0.xsd Table 7.4.38.1-2: Universal/Common Attributes of <timeSeries> resource Attribute Name Request Optionality Create Update @resourceName O NP resourceType NP NP resourceID NP NP parentID NP NP accessControlPolicyI Ds O O creationTime NP NP expirationTime O O lastModifiedTime NP NP stateTag NP NP labels O O announceTo O O announcedAttribute O O creator O NP ETSI ETSI TS 118 104 V2.7.1 (2016-10) 194 oneM2M TS-0004 version 2.7.1 Release 2 Table 7.4.38.1-3: Resource Specific Attributes of <timeSeries> resource Attribute Name Request Optionality Data Type Default Value and Constraints Create Update maxNrOfInstances O O xs:nonNegativeInteger No default maxByteSize O O xs:nonNegativeInteger No default maxInstanceAge O O xs:nonNegativeInteger No default currentNrOfInstances NP NP xs:nonNegativeInteger No default (This is generated by the Hosting CSE and limited by the maxNrOfInstances) currentByteSize NP NP xs:nonNegativeInteger No default (This is generated by the Hosting CSE and limited by the maxByteSize) periodicInterval O O xs:nonNegativeInteger No default missingDataDetect O O xs:boolean No default missingDataMaxNr O O xs:nonNegativeInteger No default missingDataList NP NP m2m:missingDataList No default missingDataCurrentNr NP NP xs:nonNegativeInteger No default (This is generated by the Hosting CSE and limited by the missingDataMaxNr) missingDataDetectTimer O O xs:nonNegativeInteger No default (This is in units of milliseconds.) ontologyRef O O xs:anyURI No default Table 7.4.38.1-4: Child Resources of <timeSeries> resource Child Resource Type Child Resource Name Multiplicity Ref. to in Resource Type Definition <timeSeriesInstance> [variable] 0..n Clause 7.4.39 <subscription> [variable] 0..n Clause 7.4.8 <semanticDescriptor> [variable] 0..n Clause 7.4.34 |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.38.2 <timeSeries> resource specific procedure on CRUD operations | |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.38.2.0 Introduction | This clause describes <timeSeries> resource specific behaviour for CRUD operations. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.38.2.1 Create | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: Primitive specific operation after Recv-C-6.5 "Create/Update/Retrieve/Delete/Notify operation is performed". See clause 7.2.2.2. In the case that the periodicInterval is set and the missingDataDetect is TRUE, the Hosting CSE shall monitor the Time Series Data based on its periodicInterval. The Hosting CSE shall consider the expecting Time Series Data be lost when the amount of time equal to missingDataDetectTimer has passed relative to its expecting generation time when the data was generated by the AE/CSE. ETSI ETSI TS 118 104 V2.7.1 (2016-10) 195 oneM2M TS-0004 version 2.7.1 Release 2 When the Hosting CSE detects a missing data point, the dataGenerationTime of the missing data point is inserted into the missingDataList attribute and the missingDataCurrentNr shall be increased by one. When the missingDataCurrentNr reaches the missingDataMaxNr, the oldest dataGenerationTime shall be removed from missingDataList to enable the insertion of the new missing data point information. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.38.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.38.2.3 Update | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.38.2.4 Delete | Originator: No change from the generic procedures in clause 7.2.2.1. Receiver: No change from the generic procedures in clause 7.2.2.2. |
cbf164e0a9061a5bee8f92b0fb68219c | 118 104 | 7.4.39 Resource Type <timeSeriesInstance> |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.