hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.1.2 Resource type-specific procedure conventions | This clause describes resource type specific procedures referring generic procedures defined in clause 7.1.2. Each operation specific procedure describes procedures for the Originator and the Receiver. If the resource and operation specific procedure is the same as the generic procedure, the Originator and Receiver pro... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.2 Resource type <accessControlPolicy> | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.2.1 Introduction | The <accessControlPolicy> resource is comprised of privileges and selfPrivileges attributes which represent a set of access control rules defining which entities (defined as accessControlOriginators) have the privilege to perform certain operations (defined as accessContolOperations) within specified contexts (defined ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.2.2 accessControlPolicy resource specific procedure on CRUD operations | This clause describes accessControlPolicy resource specific behaviour for CRUD operations. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.2.2.1 Create | Originator: No changes from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.2.2.2 Retrieve | Originator: No changes from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.2.2.3 Update | Originator: No change from the generic procedures in clause 7.1.2.1. ETSI ETSI TS 118 104 V1.0.0 (2015-02) 81 Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.2.2.4 Delete | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.3 Resource Type <CSEBase> | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.3.1 Introduction | A <CSEBase> resource shall represent a CSE. This <CSEBase> resource shall be the root for all the resources that are residing on the CSE. The detailed description can be found in clause 9.6.3 in ETSI TS 118 101 [6] Functional Architecture). Table 7.3.3.1-1: Data Type Definition of <CSEBase> resource Data Type ID File N... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.3.2 <CSEBase> resource specific procedure on CRUD operations | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.3.2.1 Create | Originator: The <CSEBase> 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 ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.3.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.3.2.3 Update | Originator: The <CSEBase> 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 ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.3.2.4 Delete | Originator: The <CSEBase> resource shall not be DELETEed 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... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.4 Resource Type <remoteCSE> | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.4.1 Introduction | A <remoteCSE> resource shall represent a remote CSE that is registered to the Registrar CSE. <remoteCSE> resources shall be located directly under the <CSEBase>. Conversely each registered CSE shall also be represented as a sub-set of <remoteCSE> resource in the registering CSE's <CSEBase>. The detailed description can... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.4.2 <remoteCSE> resource specific procedure on CRUD operations | The entire CSE registration procedure including <CSE> resource creation procedure below is defined in clause 10.1.1.2.1 [6] ("CSE registration procedure"). |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.4.2.1 Create | Originator: No change from the generic procedures in clause 7.1.2.1 with the following exception: • An AE shall not originate a Create <remoteCSE> resource request. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received over the Mca reference point, the ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.4.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.1. ETSI ETSI TS 118 104 V1.0.0 (2015-02) 85 |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.4.2.3 Update | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.1. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.4.2.4 Delete | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.1. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.5 Resource Type <AE> | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.5.1 Introduction | The <AE> resource represents information about an Application Entity known to a given Common Services Entity. The detailed description can be found in clause 9.6.5 in ETSI TS 118 101 [6] Functional Architecture. Table 7.3.5.1-1: Data type definition of <AE> resource Data Type ID File Name Note AE CDT-AE-v1_0_0.xsd XSD ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.5.2 <AE> resource specific procedure on CRUD+N operations | This clause describes AE resource specific behaviour for CRUD+N operations. The entire AE registration procedure including <AE> resource creation procedure below is defined in clause 10.1.1.2.2 of the ETSI TS 118 101 [6] ("Application Entity registration procedure"). |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.5.2.1 Create | Originator: No change from the generic procedures in clause 7.1.2.1 with the with the following exception: • A CSE shall not originate a Create <AE> resource request. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) If the request is received over Mcc or Mcc' reference point... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.5.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.5.2.3 Update | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. ETSI ETSI TS 118 104 V1.0.0 (2015-02) 87 |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.5.2.4 Delete | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.5.2.5 Notify | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.6 Resource Type <container> | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.6.1 Introduction | This resource represents a container for data instances. It is used to share information among other entities and potentially to track the data. A <container> resource has no associated content, only attributes and child resources. The detailed description can be found in clause 9.6.6 in ETSI TS 118 101 [6] Functional ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.6.2 <container> resource specific procedure on CRUD operations | This clause describes container resource specific behaviour for CRUD operations. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.6.2.1 Create | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.6.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.6.2.3 Update | Originator: No change from the generic procedures in clause 7.1.2.1. ETSI ETSI TS 118 104 V1.0.0 (2015-02) 89 Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.6.2.4 Delete | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.7 Resource Type <contentInstance> | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.7.1 Introduction | The <contentInstance> resource represents a data instance in the container. The detailed description can be found in clause 9.6.7 in ETSI TS 118 101 [6] Functional Architecture. Table 7.3.7.1-1: Data type definition of <contentInstance> resource Data Type ID File Name Note contentInstance CDT-contentInstance-v1_0_0.xsd... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.7.2 <contentInstance> resource specific procedure on CRUD operations | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.7.2.1 Create | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. The Originator may omit the name of the <contentInstance> resource unless the Originator need to refer specific content later. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.7.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. The Originator may omit the name of the targeted <contentInstance> resource when the latest version of stored content is requested. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.7.2.3 Update | Originator: The <contentInstance> resource shall not be Updated 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. a) "Create an unsuccessful Response primitive" with the Response St... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.7.2.4 Delete | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.8 Resource Type <subscription> | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.8.1 Introduction | 7.3. |
10651370426c90bc406f33851f64d370 | 118 104 | 8.1 Introduction | The <subscription> resource contains subscription information for its subscribed-to resource. The subscription resource is a child of the subscribed to resource. The detailed description can be found in clause 9.6.8 in ETSI TS 118 101 [6] Functional Architecture. ETSI ETSI TS 118 104 V1.0.0 (2015-02) 91 Table 7.3.8.1-1... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.8.2 <subscription> resource specific procedure on CRUD operations | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.8.2.1 Create | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: The following are additional Hosting CSE procedures to the generic resource handling procedures (figure 7.2.1.2.2-2 in clause 7.2.1.2.2). The additional procedures shall be inserted from Recv-6.2 to Recv-6.8 as below. ETSI ETSI TS 118 104 V1... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.8.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.8.2.3 Update | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. ETSI ETSI TS 118 104 V1.0.0 (2015-02) 93 |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.8.2.4 Delete | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.9 Resource Type <schedule> | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.9.1 Introduction | The <schedule> resource shall represent scheduling information in the context of its parent resource. If a <schedule> resource is not present as a child resource then there are no time-constraints on the context of its parent resource. An Originator shall have the same access control privileges to the <schedule> resour... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.9.2 <schedule> resource specific procedure on CRUD operations | This clause describes <schedule> resource specific behaviour for CRUD operations. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.9.2.1 Create | Originator: No change from the generic procedures in clause 7.1.2.1. If <schedule> is created then scheduleElement (L) shall be created. ETSI ETSI TS 118 104 V1.0.0 (2015-02) 95 Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.9.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.9.2.3 Update | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.9.2.4 Delete | Originator: No change from the generic procedures in clause 7.1.2.1. If <schedule> is deleted then scheduleElement (L) shall be deleted. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.10 Resource Type <locationPolicy> | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.10.1 Introduction | The <locationPolicy> resource represents the method for obtaining and managing geographical location information of an M2M Node. The detailed description can be found in the clause 9.6.10 in ETSI TS 118 101 [6] Functional Architecture. Table 7.3.10.1-1: Data type definition of <locationPolicy> resource Data Type ID Fil... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.10.2 <locationPolicy> resource specific procedure on CRUD Operations | This clause describes <locationPolicy> resource specific primitive behaviour for CRUD operations. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.10.2.1 Create | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: The following <locationPolicy> resource type specific procedures shall be performed after Recv-6.5 and before Recv-6.6 generic procedures. 1) After the successful creation of <locationPolicy> resource, the Hosting CSE shall create <container... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.10.2.2 Retrieve | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. ETSI ETSI TS 118 104 V1.0.0 (2015-02) 98 |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.10.2.3 Update | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.10.2.4 Delete | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: The procedure of the Receiver written in the clause 7.1.2.2 (from Rcv-D-1.0 to Rcv-D-10.0) shall be the same as initial steps. A following step is the <locationPolicy> resource type specific procedure for DELETE operation. 1) Once the <locat... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.11 Resource Type <delivery> | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.11.1 Introduction | In order to be able to initiate and manage the execution of data delivery in a resource-based manner, resource type delivery is defined. This resource type shall be used for forwarding requests from one CSE to another CSE when the Delivery Aggregation parameter in the request is set to ON. The detailed description can ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.11.2 <delivery> resource specific procedure on CRUD operations | This clause describes <delivery> resource specific behaviour for CRUD operations. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.11.2.1 Create | Originator: An AE shall not originate a Create <delivery> resource request. Primitive specific operation on Orig-1.0 "Compose Request primitive": 1) The Originator shall use a blocking request (i.e. Response Type=blockingRequest). 2) The Originator shall provide the content of the <delivery> resource. No change for the... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.11.2.2 Retrieve | Originator: Primitive specific operation on Orig-1.0 "Compose Request primitive": 1) The Originator shall use a blocking request (i.e. Response Type=blockingRequest). No change for the remaining steps from the generic procedures in clause 7.1.2.1. ETSI ETSI TS 118 104 V1.0.0 (2015-02) 100 Receiver: No change from the g... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.11.2.3 Update | Originator: An AE shall not originate a Create <delivery> resource request. Primitive specific operation on Orig-1.0 "Compose Request primitive": 1) The Originator shall use a blocking request (i.e. Response Type=blockingRequest). 2) The Originator shall provide the content of the <delivery> resource. No change for the... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.11.2.4 Delete | Originator: An AE shall not originate a Create <delivery> resource request. Primitive specific operation on Org-1.0 "Compose Request primitive": 1) The Originator shall use a blocking request (i.e. Response Type=blockingRequest). No change for the remaining steps from the generic procedures in clause 7.1.2.1. Receiver:... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.12 Resource Type <request> | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.12.1 Introduction | The <request> resource is used to represent information on locally issued requests (i.e. issued by an AE or CSE internal). This allows for robust synchronous and asynchronous request processing coping with various constraints on maximum blocking time. When an AE or CSE issues a request for targeting any other resource ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.12.2 <request> resource specific procedure on CRUD operations | This clause describes request resource specific procedure on Resource Hosting CSE for CRUD operations. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.12.2.1 Create | Originator: The <request> resource shall not be created via API. See clause 7.2.2.2 Create <request> resource locally. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) "Create an unsuccessful Response primitive" with a Response Status Code indicating 'OPERATION_NOT_ALLOWED' ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.12.2.2 Retrieve | Originator: The procedure of the Originator is the same as the clause 7.1.2.1. Receiver: The procedure of the Receiver is the same as the clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.12.2.3 Update | Originator: The <request> resource shall not be updated via API. See clause 7.2.2.5 Update <request> resource. Receiver: Primitive specific operation on Recv-1.0 "Check the syntax of received message": 1) "Create an unsuccessful Response primitive" with a Response Status Code indicating 'OPERATION_NOT_ALLOWED' error. 2... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.12.2.4 Delete | Originator: The procedure of the Originator is the same as the clause 7.1.2.1 Receiver: The procedure of the Receiver is the same as the clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.13 Resource Type <group> | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.13.1 Introduction | The <group> resource represents a group of resources of the same or mixed types. The <group> resource can be used to do bulk manipulations on the resources represented by the memberID attribute. The <group> resource contains an attribute that represents the members of the group and a virtual resource (the <fanOutPoint>... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.13.2 <group> resource specific procedure on CRUD operations | This clause describes <group> resource specific procedure on Resource Hosting CSE for CRUD operations. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.13.2.1 Create | Primitive specific operation after Recv-C-6.4 "Check validity of resource representation for the given resource type" and before Recv-C-6.5 "Create/Update/Retrieve/Delete/Notify operation is performed ". See clause 7.1.2.2. 1) Primitive specific operation: Validate the provided attributes. It shall also check whether t... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.13.2.2 Retrieve | No primitive specific operations. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.13.2.3 Update | 3) Primitive specific operation after Recv-6.4 "Check validity of resource representation for the given resource type" and before Recv-6.5 "Create/Update/Retrieve/Delete/Notify operation is performed ". See clause 7.1.2.2. Primitive specific operation: If the memberType attribute of the <group> resource is not "MIXED",... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.13.2.4 Delete | No primitive specific operations. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.14 Resource Type <fanOutPoint> | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.14.1 Introduction | The <fanOutPoint> resource is a virtual resource because it does not have a representation. It is the child resource of a <group> resource. Whenever the request is sent to the <fanOutPoint> resource, the request is fanned out to each of the members of the <group> resource indicated by the memberID attribute of the <gro... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.14.2 <fanOutPoint> operations | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.14.2.1 Validate the member types | Validate the provided attributes. If the memberType attribute of the addressed parent resource is not "MIXED", the group hosting CSE may check whether the type of resource to be created is consistent with the addressed parent resource. i.e. if the To parameter was …/fanOutPoint without any suffix, then the memberType a... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.14.2.2 Sub-group creation for members residing on the same CSE | The group hosting CSE shall obtain URIs of addressed resources from the attribute memberID of the parent <group> resource. The group hosting CSE may determine that multiple member resources belong to the same remote member hosting CSE, and may perform as an Originator to request to create a sub-group containing the spe... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.14.2.3 Assign URI for aggregation of notification | In the case the created resource is <subscription> resource, the group hosting CSE shall validate if the subscription resource in the received request contains an notificationForwardingURI attribute. On successful validation, the group hosting CSE shall assign a new notificationForwardingURI to the attribute for receiv... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.14.2.4 Fanout Request to each member | For each member hosting CSE, the group hosting CSE shall perform the following steps: a) The primitive parameters From and To shall be mapped to the primitive parameters of the corresponding Request to be sent out to each member of the group. The primitive parameter From shall be directly used. The prefix of primitive ... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.14.3 <fanOutPoint> resource specific procedure on CRUD operations | This clause describes <fanOutPoint> resource specific behaviour for CRUD operations. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.14.3.1 Create | The primitives create the content of all member resources belonging to an existing <group> resource. Originator: Primitive specific operation after Orig-1.0 "Compose Request primitive" and before Orig-2.0 "Send the Request to the receiver CSE": In the case the Originator wants to subscribe to all the member resources o... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.14.4 Retrieve | The primitives retrieve the content of all <member> resources belonging to an existing <group> resource. Originator: No primitive specific operations. Receiver: Primitive specific operation after Recv-6.2 "Check existence of the addressed resource" and before Recv-6.3 "Check authorization of the Originator": The To par... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.14.4.1 Update | The primitives update the content of all member resources belonging to an existing <group> resource. Originator: No primitive specific operations. Receiver: Primitive specific operation after Recv-6.2 "Check existence of the addressed resource" and before Recv-6.3 "Check authorization of the Originator": The To paramet... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.14.4.2 Delete | The primitives delete the content of all member resources belonging to an existing <group> resource. Originator: No primitive specific operations. Receiver: Primitive specific operation after Recv-6.2 "Check existence of the addressed resource" and Recv-6.3 "Check authorization of the Originator": The To parameter cons... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.15 Resource Type <mgmtObj> |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.