hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.30 m2m:rateLimit | Used in <subscription>. Table 6.3.4.30-1: Type Definition of m2m:rateLimit Element Path Element Data Type Multiplicity Note maxNrOfNotify xs:nonNegativeInteger 0..1 timeWindow xs:duration 0..1 |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.31 m2m:operationResult | Used for operationResult attribute in <request> resource. ETSI ETSI TS 118 104 V1.0.0 (2015-02) 48 Table 6.3.4.31-1: Type Definition of m2m:operationResult Element Path Element Data Type Multiplicity Note Content primitiveContent 0..1 See clause 6.3.4.4 Event Category m2m:eventCat 0..1 See clause 6.3.4.1 From m2m:ID 0.... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.4.32 m2m:aggregatedResponse | Used when aggregating responses by a group. Table 6.3.4.32-1: Type Definition of m2m:aggregatedResponse Element Path Element Data Type Multiplicity Note responsePrimitive See table 6.4.2-1 for detail. 1..n |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.5 Universal and Common attributes | ETSI TS 118 101 [6] Functional Architecture defines a number of Universal Attributes (which appear in all resources) and Common Attributes (which appear in more than one resource and have the same meaning whenever they do appear). The type and values shall be supported according to the description given in Table 6.3.5-... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.6 Filter criteria | The request message parameter Filter Criteria shall be specified as combination of following sub-parameters. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.6.1 creationTime condition | The condition matches with the resources which the creationTime attribute is chronologically in specified range. Table 6.3.6.1-1: Defition of Create Time condition Format Variants Definition Note createdBefore m2m:timestamp created After m2m:timestamp NOTE: Both createdBefore and createdAfter may be specified same time... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.6.2 lastModifiedTime condition | The condition matches with the resources which the lastModifiedTime attribute is chronologically in specified range. Table 6.3.6.2-1: Defition of LastModified Time condition Format Variants Definition Note modifiedSince m2m:timestamp unmodifiedSince m2m:timestamp NOTE: Both modifiedSince and unmodifiedSince may be spec... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.6.3 State Tag condition | The condition matches with the <contentInstance> resources which the stateTag attribute is in specified numeric value range. Table 6.3.6.3-1 Defition of State Tag condition Format Variants Definition Note stateTagSmaller xsd:positiveInterger stateTagBigger xsd:nonNegativeInteger NOTE: ETSI ETSI TS 118 104 V1.0.0 (2015-... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.6.4 expirationTime condition | The condition matches with the expirationTime attribute of the resources is chronologically in specified chnological time range. Table 6.3.6.4-1: Defition of ExirationTime condition Format Variants Definition Note exprieBefore m2m:timestamp expireAfter m2m:timestamp NOTE: Both expireBefore and expireAfter may be specif... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.6.5 labels Match condition | The condition matches with the resource which labels attribute contains the specified value. Table 6.3.6.5-1: Defition of Lebel Match condition Format Variants Definition Note label contains xs:token any of label matches list of xs:token separator of list elements shall be specified in protocol bindings NOTE: |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.6.6 resourceType Match condition | The condition matches with the resource which resourceType attribute value is specified value. Table 6.3.6.6-1: Defition of Resource Type Match condition Format Variants Definition Note single type m2m:resourceType multiple types list of m2m:resourceType separator of list elements shall be specified in protocol binding... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.6.7 contentSize condtion | The condition matches with the contentSize attribute of the <contentInstance> resources is in range of specified numerica value range. Table 6.3.6.7-1: Defition of Content Size Match condition Format Variants Definition Note sizeBelow xs:nonNegativeInteger sizeAbove xs:nonNegativeInteger NOTE: |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.6.8 typeOfContent condition | The condition matches with the typeOfContent attribute of the <contentInstance> resource is the specified value. Table 6.3.6.8-1: Defition of Content Type Match condition Format Variants Definition Note content type xs:token The one of the Content-Type string shall be specified content sub-types xs:token after ':' char... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.6.9 attribute Match condition | The condition matches with the resources which all attribute/value pairs are specified combination. Table 6.3.6.9-1: Defition of Attribute Match condition Format Variants Definition Note single pair concatenation of xs:token with ':' character first token shall be shortname of attribute and second token shall be its va... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.6.10 Limit results request parameter | Limitation the number of matching resources to the specified value. Table 6.3.6.10-1: Defition of Limit conditions Format Variants Definition Note limits xs:nonNegativeInteger NOTE: |
10651370426c90bc406f33851f64d370 | 118 104 | 6.3.6.11 Filter Usage request parameter | Indicates how the filter criteria is used. E.g. if this parameter is not provided, the Retrieve operation is for generic retrieve operation. Table 6.3.6.11-1: Definition of Filter Usage Value Interpretation Note 1 Discovery Criteria 2 Event Notification Criteria NOTE: |
10651370426c90bc406f33851f64d370 | 118 104 | 6.4 Message parameter data types | |
10651370426c90bc406f33851f64d370 | 118 104 | 6.4.1 Request primitive parameter data types | The data types of request primitive parameters are specified in this clause. Detailed request primitive parameter descriptions and usage can be found in clause 8.1.2 of the ETSI TS 118 101 [6] Functional Architecture. Further details on the representation of primitives are specified in clauses 7.1.1.1 and 7.4.2. ETSI E... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.4.2 Response primitive parameter data types | The data types of response primitive parameters are specified in this clause. Detailed response message parameter descriptions and usage can be found in clause 8.1.3 of ETSI TS 118 101 [6] Functional Architecture. Further details on the representation of primitives are specified in clauses 7.1.1.1 and 7.4.2. Table 6.4.... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5 Resource data types | |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.1 Description | Each oneM2M Resource Data Type is defined using XML Schema (XSD), and supplied as a separate XSD document. This XML Schema defines the attributes of the Resource in accordance with ETSI TS 118 101 [6] Functional Architecture. It represents an entire resource. In other words if and only if a requestor retrieves an entir... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.2 Resource | |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.2.1 Description | This XSD type definition includes the six universal attributes that are present in all oneM2M resource type definitions. It forms the root of the resource inheritance hierarchy. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.2.2 Reference | See table 6.3.5-2. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.2.3 Usage | This type is used indirectly by all resource types. It is used directly just by the <CSEBase> resource type. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.3 regularResource | |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.3.1 Description | This type definition includes the universal and common attributes used by the non-annouceable M2M resources. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.3.2 Reference | See table 6.3.5-2. ETSI ETSI TS 118 104 V1.0.0 (2015-02) 55 |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.3.3 Usage | This type is used by the following resource types: • <delivery>, <eventConfig>, <execInstance>, <m2mServiceSubscriptionProfile>, <mgmtCommand>, <pollingChannel>, <request>, <serviceSubscribedNode>, <statsCollect>, <statsConfig>, <subscription>, <serviceSubscribedAppRule>. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.4 announceableResource | |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.4.1 Description | This type definition includes the universal and common attributes used by M2M resource types that are capable of being announced. In addition to the attributes of a regularResource, it includes (as optional) the common attributes that are used by the announcement mechanism. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.4.2 Reference | See table 6.3.5-2. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.4.3 Usage | This type is used by the following resource types: • AE>, <container>, <group>, <locationPolicy>, <node>, <remoteCSE> It is also used by the specializations of <mgmtObj>. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.5 announcedResource | |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.5.1 Description | This type definition includes the universal and common attributes used by a resource that is announcing an announceable resource. In addition to the attributes of a regularResource, it includes (as optional) the link common attribute. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.5.2 Reference | See table 6.3.5-2. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.5.3 Usage | This type is used by the following resource types: • <AEAnnc>, <containerAnnc>, <groupAnnc>, <locationPolicyAnnc>, <nodeAnnc>, <remoteCSEAnnc>. It is also used by the xxxAnnc variants of the <mgmtObj> specializations. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.6 announceableSubordinateResource | |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.6.1 Description | This type definition includes the common attributes used by resource types that are subordinate children of other resource types. It excludes attributes like accessControlPolicyIDs, as this attribute is defined for such resources. ETSI ETSI TS 118 104 V1.0.0 (2015-02) 56 |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.6.2 Reference | See table 6.3.5-2. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.6.3 Usage | This type is used by the following resource types: • <AEAnnc>, <containerAnnc>, <groupAnnc>, <locationPolicyAnnc>, <nodeAnnc>, <remoteCSEAnnc>. It is also used by the xxxAnnc variants of the <mgmtObj> specializations. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.7 announcedSubordinateResource | |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.7.1 Description | This type definition includes the common attributes used by the Announced variants of the resource types that are subordinate children of other resource types. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.7.2 Reference | See table 6.3.5-2. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.5.7.3 Usage | This type is used by the following resource types: • <accessControlPolicyAnnc>, <contentInstanceAnnc>, <scheduleAnnc>. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.6 Response status codes | |
10651370426c90bc406f33851f64d370 | 118 104 | 6.6.1 Introduction | The present clause specifies the assignment of oneM2M Response Status Code (RSC) values, which are returned in the Response Status Code parameter of Response primitive. The RSC may be delivered as oneM2M defined structured data, or the mapped native status code for transport protocol binding (e.g. HTTP, CoAP, MQTT). |
10651370426c90bc406f33851f64d370 | 118 104 | 6.6.2 RSC framework overview | The RSCs are categorised as one of 6 classes: Table 6.6.2-1: Definition of Response Status Code class Status Class Codeclass Interpretation Informational 1xxx The request is successfully received, but the request is still on process. Success 2xxx The request is successfully received, understood, and accepted. Redirecti... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.6.3 Definition of Response Status Codes | |
10651370426c90bc406f33851f64d370 | 118 104 | 6.6.3.1 Overview | The tables in the following clauses specify the RSCs for oneM2M releases. Each RSC includes: a response status innumeric code. The supplemental information may be returned when it is needed. |
10651370426c90bc406f33851f64d370 | 118 104 | 6.6.3.2 Informational response class | Table 6.6.3.2-1 specify the RSCs for acknowledgement responses for each release. Table 6.6.3.2-1: Informational Responses class Numeric Code Description 1000 ACCEPTED |
10651370426c90bc406f33851f64d370 | 118 104 | 6.6.3.3 Successful response class | Table 6.6.3.3-1 specify the RSCs for successful responses. Table 6.6.3.3-1: RSCs for Successful response class Numeric Code Description 2000 OK 2001 CREATED 2002 DELETED 2004 CHANGED |
10651370426c90bc406f33851f64d370 | 118 104 | 6.6.3.4 Redirection response class | Not defined any values in this response class. Table 6.6.3.4-1: RSCs for Redirection response class Numeric Code Description |
10651370426c90bc406f33851f64d370 | 118 104 | 6.6.3.5 Originator Error response class | Table 6.6.3.5-1 specify the RSCs for Originator Error responses. Table 6.6.3.5-1: RSCs for Originator Error response class Numeric Code Description 4000 BAD_REQUEST 4004 NOT_FOUND 4005 OPERATION_NOT_ALLOWED 4008 REQUEST_TIMEOUT 4101 SUBSCRIPTION_CREATOR_HAS_NO_PRIVILEGE– 4102 CONTENTS_UNACCEPTABLE 4103 ACCESS_DENIED 41... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.6.3.6 Receiver Error response class | Table 6.6.3.6-1 specify the RSCs for Receiver Error responses. Table 6.6.3.6-1: RSCs for Receiver Error response class Numeric Code Description 5000 INTERNAL_SERVER_ERROR 5001 NOT_IMPLEMENTED 5103 TARGET_NOT_REACHABLE 5105 NO_PRIVILEGE 5106 ALREADY_EXISTS 5203 TARGET_NOT_SUBSCRIBABLE 5204 SUBSCRIPTION_VERIFICATION_INIT... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.6.3.7 Network System Error response class | Table 6.6.3.7-1 specify the RSCs for when the External System reported some errors. Table 6.6.3.7-1: RSCs for Network Service Error response class Numeric Code Description 6003 EXTENAL_OBJECT_NOT_REACHABLE 6005 EXTENAL_OBJECT_NOT_FOUND 6010 MAX_NUMBERF_OF_MEMBER_EXCEEDED 6011 MEMBER_TYPE_INCONSISTENT 6020 MGMT_SESSION_... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.7 oneM2M specific MIME media types | The present sub-clause defines oneM2M specific MIME media types which may be used by protocol bindings. The oneM2M specific MIME media types are defined under the vendor tree of "application" mediate type which is prefixed with 'application/vnd.onem2m-'. Table 6.7-1: oneM2M specific MIME media types oneM2M specific MIM... |
10651370426c90bc406f33851f64d370 | 118 104 | 6.8 Virtual Resources | A virtual resource is used to trigger processing and/or retrieve results, but does not have a permanent representation in a CSE. Table 6.8-1 lists the Virtual Resources. Table 6.8-1: Virtual Resources Virtual Resource Type resourceName Parent Resource Notes <latest> latest <container> See clause 7.3.27 <oldest> oldest ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7 oneM2M procedures | The following clauses describe prerequisites such as primitive format and procedure outline with three generic scenarios that are Originator, Receiver, and Resource Handling in accordance with CRUD+N operations. In addition, for specific resource type they provide common or resource specific attributes, data type defin... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.1 Primitive format and generic procedure | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.1.1 Primitive format | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.1.1.1 Request primitive format | Table 7.1.1.1-1 summarizes the primitive parameters of the Request primitive, indicating their presence depending on the C, R, U, D or N operations. "M" indicates mandatory, "O" indicates optional, "NP" indicates not present. Refer to clause 8.1.2 of the ETSI TS 118 101 [6] for additional information on the request pri... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.1.1.2 Response primitive format | Table 7.1.1.2-1 summarizes the primitive parameters for Response primitive, indicating their presence depending on the C, R, U, D or N operations of the associated Request primitive and whether this operation was successful or caused an error. "M" indicates mandatory, "O" indicates optional, "NP" indicates not present.... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.1.2 Description of generic procedures | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.1.2.1 Generic resource request procedure for originator | A generic resource Request procedure shall be comprised of the following actions. Additional actions specific to individual procedures are listed in the respective sections by referencing these actions and providing additional steps. The Originator shall execute the following steps in order. ETSI ETSI TS 118 104 V1.0.0... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.1.2.2 Generic request procedure for receiver | The Receiver shall execute the following steps in order. In case of error in any of the steps below, the Receiver shall execute "Create an error response" (refer to clause 0 for details) and then "Send Response primitive" (refer to clause 7.2.2.4 for details). The corresponding Response code shall be included in the Re... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2 Common operations | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.1 Originator actions | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.1.1 Compose request primitive | The originator shall compose a Request message that shall be mapped to a specific protocol. The Request shall include the From and To parameters to indicate the identifier of the originator of the request and the targeted receiver of the request. The Request shall include the other attributes in case needed depend on t... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.1.2 Send a request to the receiver CSE | The originator shall determine the receiver CSE. The receiver of the Request shall be the registrar CSE of the originator in case the originator is not IN-CSE. If the originator is the IN-CSE, the receiver of the Request shall be the CSE whose identifier is the prefix of the To parameter of the Request. ETSI ETSI TS 11... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.1.3 Wait for response primitive | The originator shall wait for the Response primitive from the receiver that corresponds to the Request primitive that was sent by the originator. Correlation between the Request and the corresponding Response is handled by the transport layer or by Request Identifier parameter of the primitive.. If no Response primitiv... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.1.4 Retrieve the <request> resource | When the Originator needs to retrieve information about an associated previously issued non-blocking request, the Originator shall request to RETRIEVE the attributes of the <request> resource. The Originator shall compose the Request primitive with the following parameters and send the Request to the Receiver CSE. See ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.2 Receiver CSE actions | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.2.1 Check the validity of received request primitive | The validity checking of the message carrying the received request primitive is specified by the protocol mapping Technical Specifications (CoAP binding [22], HTTP binding [23] and MQTT binding [24]). The received resource representation (e.g. in plain XML, binary XML or JSON) shall be validated against the provided sc... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.2.2 Create <request> resource locally | Creation of a <request> resource can only be done on a Receiver CSE implicitly. When the Receiver CSE receives a request for targeting any other resource type or requesting a notification in non-blocking mode, i.e. the Response Type parameter of the request is set to either 'nonBlockingRequestSynch' or 'nonBlockingRequ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.2.3 Create a success response (acknowledgement) | The Receiver CSE shall create a Response primitive. The Receiver CSE shall include the following parameters in the Response primitive. Table 7.2.2.3-1: Response primitive parameter settings Parameter Name Value Response Status Code "ACCEPTED" Request Identifier The value of the parameter Request Identifier in the assoc... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.2.4 Send response primitive (acknowledgement) | A Response primitive shall be sent back to the originator. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.2.5 Update <request> resource | Changes in the attributes of a <request> resource shall be done by the Hosting CSE implicitly due to changes of the status (requestStatus) of the associated non-blocking request or due to the reception of an operation result (operationResult) in response to the associated non-blocking request. The Receiver CSE shall up... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.2.6 Forwarding | If the To parameter in the request does not start with the CSEBase URI of the receiver, the receiver CSE shall forward the request or shall serve the request locally (see below). If the To parameter in the request starts with the CSEBase URI of the receiver, then the receiver CSE shall handle the request locally. Actin... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.2.7 Check Service Subscription Profile | The receiver shall check if the originator's <serviceSubscriptionProfile> has S-RoleID in serviceRoles attribute that allows to create resource type specified in resource type parameter. The receiver shall find a proper <serviceSubscribedNode> including CSE-ID of the receiver and determine serviceRoles from the parent ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3 Hosting CSE actions | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.1 Check existence of the addressed resource | The hosting CSE shall check if the resource addressed by the To parameter exists in the repository. If the resource does not exist, the hosting CSE shall reject the request with a Response Status Code indicating "NOT_FOUND" error. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.2 Check validity of resource representation for CREATE | The handling below shall apply to each attribute in the resource for CREATE request primitives and the handling depends on the "presence in CREATE request" column of the resource table. If the request is rejected based on the rules below, then the other attributes do not have to be checked. If no resource representatio... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.3 Check validity of resource representation for UPDATE | The handling below shall apply to each attribute in the resource for UPDATE request primitives and the handling depends on the "presence in UPDATE request" column of the resource table. If the request is rejected based on the rules below, then the other attributes do not have to be checked. If the expirationTime attrib... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.4 Create the resource | A new resource shall be created and correlated to the addressed and existing parent resource. As the result of the resource creation, the lastModifiedTime attribute of the parent resource shall be set to the same value as the creationTime attribute of the created resource. The following rules shall be applied. The URI ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.5 Retrieve the resource | When the resource is read to provide a response to Retrieve request primitives: Full retrieve request: the request target is a resource given in the To parameter The content of the Response to the Retrieve Request shall comply to the Result Content parameter in the Request. If the Result Content is not provided in the ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.6 Update the resource | Attributes that are not included in the Content parameter of the addressed resource shall not be changed by the hosting CSE. For attributes provided in the Content parameter, their content shall be updated while the following rules apply. If the announceTo attribute or announcedAttribute attribute of the resource is re... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.7 Delete the resource | The addressed resource with all its attributes shall be deleted. Any expiration timer shall be stopped. This same procedure shall be invoked (recursively) for each child resource of the deleted resource in case the child resource is only linked to the deleted resource. The parent resource of the addressed resource shal... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.8 Notify re-targeting | When the Hosting CSE receives a Notify request primitive targeting (i.e. To parameter) its <AE> resource, the Hosting CSE re-targets the primitive to the AE if the <AE> resource does not have any <pollingChannel> resource as a child. 1) Get pointOfAccess attribute value of the corresponding <AE> resource. If there is n... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.9 Announce the resource or attribute | If CREATE request that contains an announceTo attribute is received: • Compose the CREATE Request primitive as follows: - Link is set to the URI of the original resource. - If accessControlPolicyIDs of the original resource is not present, accessControlPolicyIDs is set to the same value with the parent resource or from... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.10 De-announce the resource or attribute | If UPDATE Request that deletes the URI from the announceTo attribute is received: • Compose the DELETE Request primitive. • Send a DELETE Request to the CSE(s) represented by URI(s) in the announceTo attribute of the resource, which is not included in the announceTo of the request. The To parameter in the DELETE Reques... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.11 Create a success response | The Hosting CSE shall create a success response primitive with a Response Status Code indicating: • "CREATED" in case of Create operation. If the Hosting CSE assigned attribute(s) not provided or modified any of the provided attributes as provided in the Request, the Content parameter shall include the assigned and/or ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.12 Create an error response | The receiver shall create an error response primitive with a Response Status Code indicating the detected error condition. NOTE: Possible error codes and its error handling is described in resource specific procedure. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.13 Resource discovery procedure | A resource discovery is used to discover resources in a CSE. A Resource discovery request is done by sending RETRIEVE request with filterUsage, one of the filterCriteria parameters, configured as "discovery" and the request may include other filterCriteria parameters as well. A resource discovery request procedure shal... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.3.14 Check authorization of the originator | Depending on the target resource type, the Hosting CSE shall use accessControlPolicyIDs of the different resources. • For <schedule> resource, the Hosting CSE shall evaluate the accessControlPolicyIDs of the parent resource. • For <latest>, <oldest> and <contentInstance> resource, the Hosting CSE shall evaluate the acc... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.4 Management common operations | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.2.4.1 Identify the managed entity and the management protocol | The Hosting CSE shall identify the managed entity to be managed via the <node> resource which is the parent resource in case of an addressed <mgmtObj> resource. In case of a <mgmtCmd> resource the entity to be managed is indicated in the execTarget attribute which addresses either a <node> resource or a group of resour... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3 Resource type-specific procedures and definitions | The reference point applicability of each resource-specific procedure for the following sub-clauses is described in the corresponding procedure specification in clause 10.2 (Resource Type-Specific Procedures) [6]. E.g. Applicable reference points of <container> resource creation procedure (clause 7.3.6.2.1) in present ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.1 Resource type specification conventions | This clause describes how to understand the following clauses for resource type-specific procedures and definitions. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.1.1 Resource type definition conventions | Table 7.3.1.1-1 includes the information of XSD data type definition files for the corresponding resource type. Table 7.3.1.1-1: Data type definition of <resourceType> Data Type ID File Name Note Actual Data Type ID XSD file name Table 7.3.1.1-2 includes the information of universal/common attributes of the resource ty... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.