hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.17 Resource Type execInstance | The <execInstance> resource represents a successful instance of <mgmtCmd> execution request, which had been triggered by a M2M network application using the UPDATE method to the attribute execEnable of <mgmtCmd> resource. <execInstance> 1 execStatus 1 execResult 0..1 execDisable 1 execTarget 0..1 execMode 0..1 execFreq... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.18 Resource Type node | The <node> resource represents specific information that provides properties of an M2M Node that can be utilized by other oneM2M operations. The <node> resource has specialization of the <mgmtObj> as its child resources. These resources represent the Node's context information (e.g. memory and battery), network topolog... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.19 Resource Type m2mServiceSubscriptionProfile | The <m2mServiceSubscriptionProfile> resource represents an M2M Service Subscription. It is used to represent all data pertaining to the M2M Service Subscription, i.e. the technical part of the contract between an M2M Application Service Provider and an M2M Service Provider. <m2mService SubscriptionProfile> 0..1 (L) ser... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.20 Resource Type serviceSubscribedNode | The <serviceSubscribedNode> resource represents M2M Node information that is needed as part of the M2M Service Subscription resource. It shall contain information about the M2M Node as well as application identifiers of the Applications running on that Node. Figure 9.6.20-1: Structure of <serviceSubscribedNode> resourc... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.21 Resource Type pollingChannel | The <pollingChannel> resource represents a channel that can be used for a request-unreachable entity (i.e. an AE or a CSE which is behind NAT so it cannot receive a request from other Nodes). The request-unreachable entity creates a <pollingChannel> resource on a request-reachable CSE, and then polls any type of reques... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.22 Resource Type pollingChannelURI | The <pollingChannelURI> virtual resource is the child resource of the <pollingChannel> resource and is used to perform service layer long polling. The creator of the <pollingChannel> resource sends a Retrieve request targeting the <pollingChannelURI> resource as a service layer long polling request. The long polling re... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.23 Resource Type statsConfig | The <statsConfig> resource is used to store policies of statistics for AEs. The <statsConfig> resource may be established by the IN-CSEs or by IN-AEs. The <statsConfig> resource shall be located directly under <CSEBase>. Figure 9.6.23-1: Structure of <statsConfig> resource The <statsConfig> resource shall contain the c... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.24 Resource Type eventConfig | <eventConfig> sub-resource shall be used to define events that trigger statistics collection. Below are some examples of events that can be generated: • Collection based on a certain operation: collects any RETRIEVE operations on the data (i.e. resources) stored in the IN-CSE. • Collection based on storage size: collec... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.25 Resource Type statsCollect | The <statsCollect> resource shall be used to collect information for AEs using the <eventConfig> resource as the triggers in the IN-CSE. Multiple triggers can be established at IN-CSE for the same AE. . Each trigger may be activated or de-activated independently of others. The <statsCollect> resource shall be located d... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.26 Resource Announcement | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.26.1 Overview | A resource can be announced to one or more remote CSEs to inform the remote CSEs of the existence of the original resource. An announced resource can have a limited set of attributes and a limited set of child resources from the original resource. The announced resource includes a link to the original resource hosted b... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.26.2 Universal Attributes for Announced Resources | Table 9.6.26.2-1 lists the universal attributes for the announced resources. If an attribute is marked "NA" in the original resource type or it is marked "OA" and is not provided by the Originator, then the value for the corresponding attribute in the announced resource is provided by the <remote CSE> resource. Table 9... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.26.3 Common Attributes for Announced Resources | Table 9.6.26.3-1 lists the common attributes for the announced resources. If an attribute is marked "NA" in the original resource type or it is marked "OA" and is not provided by the Originator, then the value for the corresponding attribute in the announced resource is provided by the <remote CSE> resource. Table 9.6.... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.27 Resource Type latest | The <latest> resource is a virtual resource because it does not have a representation. It is the child resource of a <container> resource. When a request addresses the <latest> resource, the Hosting CSE shall apply the request to the latest <contentInstance> resource among all existing <contentInstance> resources of th... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.28 Resource Type oldest | The <oldest> resource is a virtual resource because it does not have a representation. It is the child resource of a <container> resource. When a request addresses the <oldest> resource, the Hosting CSE shall apply the request to the oldest <contentInstance> resource among all existing <contentInstance> resources of th... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.29 Resource Type serviceSubscribedAppRule | 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 rule in a <serviceSubscribedAppRule> resource shall apply for CSEs for which the associated <serviceSubscribeNode> resource is linked with the <s... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10 Information Flows | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1 Basic Procedures | As a pre-condition to the execution of the following procedures, M2M operational security procedures as specified in clauses 11.3.1 through 11.3.3 shall have been performed. In case of failure, the error shall be reported as specified in ETSI TS 118 104 [i.2]. The procedures in the following clauses assume blocking req... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1.1 CREATE (C) | The CREATE procedure shall be used by an Originator CSE or AE to create a resource on a Receiver CSE (also called the Hosting CSE). The description of CREATE procedure has been divided in two separate clauses, since there is a need to distinguish between Registration related Create and Non-Registration related Create p... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1.1.1 Non-registration related CREATE procedure | This procedure is valid for all resources which are not related to registration. Originator requests to create a resource by using the CREATE method. See clause 8.1.2 for the parameters to be included in the Request message. Registrar CSE, when the Originator is an AE, shall validate the create request based on the Res... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1.1.2 Registration related CREATE procedure | This clause describes the CREATE procedure for <remoteCSE> and <AE> resource type. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1.1.2.1 CSE Registration procedure | The procedure for CSE Registration follows the procedure described in clause 10.1.1.1, but with some deviations. Below is the detailed description on how to perform the CSE Registration and which part of the procedure deviates from the one described in clause 10.1.1.1. The Registration procedure requires the creation o... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1.1.2.2 Application Entity Registration procedure | The procedure for AE registration follows the message flow description depicted in figure 10.1.1.2.2-1. It defines in which cases additional procedures need to be initiated by the Registrar CSE for creating or updating of <AEAnnc> resources hosted on the M2M SP's IN-CSE in case an AE-ID-Stem starting with an 'S' charac... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1.2 RETRIEVE (R) | The RETRIEVE operation shall be used for retrieving the information stored for any of the attributes for a resource at the Receiver CSE. The Originator CSE or AE may request to retrieve a specific attribute by including the name of such attribute in the Content parameter in the request message. Originator requests retr... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1.3 UPDATE (U) | The UPDATE operation shall be used for updating the information stored for any of the attributes at a target resource. Especially important is the expirationTime, since a failure in refreshing this attribute may result in the deletion of the resource. The Originator CSE or AE can request to update, create or delete spe... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1.4 DELETE (D) | The DELETE operation shall be used by an Originator CSE or AE to delete a resource on a Receiver CSE (also called the Hosting CSE). The description of DELETE procedure has been divided in two separate clauses, since there is a need to distinguish between Deregistration related Delete and Non-Deregistration related Dele... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1.4.1 Non-deregistration related DELETE procedure | This procedure is valid for all resources which are not related to deregistration. The DELETE operation shall be used by an Originator CSE or AE to delete a resource at a Receiver CSE. For such operation, the DELETE procedure shall consist of the deletion of all related information of the target resource. Originator re... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1.4.2 Deregistration related DELETE procedure | This clause describes the CREATE procedure for <remoteCSE> and <AE> resource type. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1.4.2.1 CSE Deregistration procedure | The procedure for CSE Deregistration follows the procedure described in clause 10.1.4.1, but with some exceptions. Below is the detailed description on how to perform the CSE Deregistration and which part of the procedure deviates from the one described in clause 10.1.4.1. The Deregistration procedure accompanies the d... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1.4.2.2 Application Entity Deregistration procedure | Application Entity Deregistration is performed by requesting a Delete operation for the <AE> resource representing the Application Entity. In case an <AE> resource with AE-ID-Stem starting with "S" is requested to be deleted, the <AEAnnc> resource that was created on the IN-CSE during the initial registration of the as... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.1.5 NOTIFY (N) | The NOTIFY operation shall be used for notifying information. Originator: The Originator requests to notify an entity by using NOTIFY method. See clause 8.1.2 for the information to be included in a Request message. Receiver: The Receiver responds to the Originator with the operation results as specified in clause 8.1.... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2 Resource Type-Specific Procedures | The basic procedure for the corresponding operations as specified in clause 10.1 shall be performed with the modifications specific to the resource type procedures as described in clause 10.2. For resources without defined resource type-specific operations, the basic operations in clause 10.1 shall apply. NOTE: Where t... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.1 <AE> Resource Procedures | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.1.1 Create <AE>, aka Application Registration | This procedure shall be used for creating an <AE> resource. This operation is part of the registration procedure for AEs on the Registrar CSE (which is also the Hosting CSE), as described in clause 10.1.1.2.2. Table 10.2.1.1-1: <AE> CREATE <AE> CREATE Associated Reference Point Mca Information in Request message All pa... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.1.2 Retrieve <AE> | This procedure shall be used for retrieving the representation of the <AE> resource. Table 10.2.1.2-1: <AE> RETRIEVE <AE> RETRIEVE Associated Reference Point Mca, Mcc and Mcc' Information in Request message All parameters defined in table 8.1.2.1-1 Processing at Originator before sending Request According to clause 10.... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.1.3 Update <AE> | This procedure shall be used for updating the attributes and the actual data of an <AE> resource. Table 10.2.1.3-1: <AE> UPDATE <AE> UPDATE Associated Reference Point Mca, Mcc and Mcc' Information in Request message All parameters defined in table 8.1.2.1-1 apply with the specific details for: Content: attributes of th... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.1.4 Delete <AE> | This procedure shall be used for deleting the <AE> resource with all related information. Table 10.2.1.4-1: <AE> DELETE <AE> DELETE Associated Reference Point Mca, Mcc and Mcc' Information in Request message All parameters defined in table 8.1.2.1-1 apply Processing at Originator before sending Request According to cla... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.2 <remoteCSE> Resource Procedures | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.2.1 Create <remoteCSE>, aka CSE Registration | This procedure shall be used for creating a <remoteCSE> resource. It is part of the registration procedure for remote CSEs on the Registrar CSE (which is also the Hosting CSE), as described in clause 10.1.1.2.1. Table 10.2.2.1-1: <remoteCSE> CREATE <remoteCSE> CREATE Associated Reference Point Mcc and Mcc' Information ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.2.2 Retrieve <remoteCSE> | This procedure shall be used for retrieving the representation of the <remoteCSE> resource with its attributes. Table 10.2.2.2-1: <remoteCSE> RETRIEVE <remoteCSE> RETRIEVE Associated Reference Point Mca, Mcc and Mcc' Information in Request message All parameters defined in table 8.1.2.1-1 apply Processing at Originator... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.2.3 Update <remoteCSE> | This procedure shall be used for updating the attributes and the actual data of an <remoteCSE> resource. Table 10.2.2.3-1: <remoteCSE> UPDATE <remoteCSE> UPDATE Associated Reference Point Mcc and Mcc' Information in Request message All parameters defined in table 8.1.2.1-1 apply with the specific details for: Content: ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.2.4 Delete <remoteCSE> | This procedure shall be used for deleting the <remoteCSE> resource with all related information. Table 10.2.2.4-1: <remoteCSE> DELETE <remoteCSE> DELETE Associated Reference Point Mca, Mcc and Mcc' Information in Request message All parameters defined in table 8.1.2.1-1 apply Processing at Originator before sending Req... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.3 <CSEBase> Resource Procedures | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.3.1 Create <CSEBase> | The Create procedure shall be not apply to <CSEBase>. <CSEBase> can be created via management operation not defined in this version of the specification. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 162 |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.3.2 Retrieve <CSEBase> | This procedure shall be used for retrieving the representation of the <CSEBase> resource with its attributes. Table 10.2.3.2-1: <CSEBase> RETRIEVE <CSEBase> RETRIEVE Associated Reference Point Mca, Mcc and Mcc' Information in Request message All parameters defined in table 8.1.2.1-1 apply Processing at Originator befor... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.3.3 Update <CSEBase> | The Update procedure shall not apply to <CSEBase>. <CSEBase> can be updated via management operation not defined in this version of the specification. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.3.4 Delete <CSEBase> | The Delete procedure shall not apply to <CSEBase>. <CSEBase> can be deleted via management operation not defined in this version of the specification. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.4 <container> Resource Procedures | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.4.1 Create <container> | This procedure shall be used for creating a <container> resource. Table 10.2.4.1-1: <container> CREATE <container> CREATE Associated Reference Point Mca, Mcc and Mcc' Information in Request message All parameters defined in table 8.1.2.1-1 apply with the specific details for: Content: The resource content shall provide... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.4.2 Retrieve <container> | This procedure shall be used for retrieving the attributes of a <container> resource. Table 10.2.4.2-1: <container> RETRIEVE <container> RETRIEVE Associated Reference Point Mca, Mcc and Mcc' Information in Request message All parameters defined in table 8.1.2.1-1 apply with the specific details for: Content: void Proce... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.4.3 Update <container> | This procedure shall be used for updating the attributes and the actual data of a <container> resource. Table 10.2.4.3-1: <container> UPDATE <container> UPDATE Associated Reference Point Mca, Mcc and Mcc' Information in Request message All parameters defined in table 8.1.2.1-1 apply with the specific details for: Conte... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.4.4 Delete <container> | This procedure shall be used for deleting a <container> resource residing under a <container> resource. Table 10.2.4.4-1: <container> DELETE <container> DELETE Associated Reference Point Mca, Mcc and Mcc' Information in Request message All parameters defined in table 8.1.2.1-1 apply Processing at Originator before send... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.5 Access to Remotely Hosted Resources via <delivery> | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.5.1 Introduction to usage of <delivery> resource type | In this introduction an example for delivering information from a source CSE to a target CSE via the use of the <delivery> resource is explained. The information flow depicted in figure 10.2.5.1-1 defines the exchange of Requests/Responses for processing an original request targeting a resource that is not hosted on th... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.5.2 Create <delivery> | This procedure shall be used for requesting a CSE to take responsibility to deliver the provided data to a target CSE in line with CMDH parameters and provisioned CMDH policies in case <delivery> resource based CMDH processing is used. If indicated by the Originator, the Receiver shall confirm the acceptance of deliver... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.5.3 Retrieve <delivery> | This procedure shall be used for requesting a CSE to provide information on a previously created <delivery> resource which represents delivery of data to a target CSE. Table 10.2.5.3-1: <delivery> RETRIEVE <delivery> RETRIEVE Associated Reference Point Mcc and Mcc' Information in Request message All parameters defined ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.5.4 Update <delivery> | This procedure shall be used for requesting a CSE to update information on a previously created <delivery> resource which represents a pending delivery of data to a target CSE. The update may have impact on further processing of the delivery. Table 10.2.5.4-1: <delivery> UPDATE <delivery> UPDATE Associated Reference Po... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.5.5 Delete <delivery> | This procedure shall be used for requesting a CSE to cancel a pending delivery of data to a target CSE or to delete the <delivery> resource of an already executed delivery. Table 10.2.5.5-1: <delivery> DELETE <delivery> DELETE Associated Reference Point Mcc and Mcc' Information in Request message All parameters defined... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.6 Resource Discovery Procedures | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.6.1 Introduction | The resource discovery procedures allow discovering of resources residing on a CSE. The use of the Filter Criteria parameter allows limiting the scope of the results. Resource discovery shall be accomplished using the RETRIEVE method by an Originator which shall also include the root of where the discovery begins: e.g.... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.6.2 Discovery procedure via Retrieve Operation | This procedure shall be used for the discovery of resources under <CSEBase> that match the provided Filter Criteria parameter. The discovery result shall be returned to the Originator using a successful Response message. Table 10.2.6.2-1: Discovery procedure via Retrieve Operation <resource> RETRIEVE Associated Referen... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.7 Group Management Procedures | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.7.1 Introduction | This clause describes different procedures for managing membership verification, creation, retrieval, update and deletion of the information associated with a <group> resource as well as the bulk management of all group member resources by invoking the corresponding operations upon the virtual resource <fanOutPoint> of... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.7.2 Create <group> | This procedure shall be used for creating a <group> resource. Table 10.2.7.2-1: <group> CREATE <group> CREATE Associated Reference Point Mcc, Mca and Mcc' Information in Request message From: Identifier of the AE or the CSE that initiates the Request To: The address of the <CSEBase>, <AE>, or <remoteCSE> where the <gro... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.7.3 Retrieve <group> | This procedure shall be used for retrieving <group> resource. Table 10.2.7.3-1: <group> RETRIEVE <group> RETRIEVE Associated Reference Point Mcc, Mca and Mcc' Information in Request message From: Identifier of the AE or the CSE that initiates the Request To: The address of the <group> resource Processing at Originator ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.7.4 Update <group> | This procedure shall be used for updating an existing <group> resource. Table 10.2.7.4-1: <group> UPDATE <group> UPDATE Associated Reference Point Mca, Mcc and Mcc' Information in Request message From: Identifier of the AE or the CSE that initiates the Request To: The address of the <group> resource Processing at Origi... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.7.5 Delete <group> | This procedure shall be used for deleting an existing <group> resource. Table 10.2.7.5-1: <group> DELETE <group> DELETE Associated Reference Point Mcc, Mca and Mcc' Information in Request message From: Identifier of the AE or the CSE that initiates the Request To: The address of the <group> resource Processing at Origi... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.7.6 <fanOutPoint> Management Procedures | Figure 10.2.7.6-1 illustrates how the <fanOutPoint> virtual resource works on the group Hosting CSE. The procedures in the figure apply to clauses 10.2.7.6 to 10.2.7.9. 007: response 001: access resource Local CSE/Hosting CSE Member Hosting CSEs Originator 002: Local processing (CSE checks access right of group resourc... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.7.7 Create <fanOutPoint> | This procedure shall be used for creating the content of all members resources belonging to an existing <group> resource. Table 10.2.7.7-1: <fanOutPoint> CREATE <fanOutPoint> CREATE Associated Reference Point Mca, Mcc and Mcc' Information in Request message From: Identifier of the AE or the CSE that initiates the Reque... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.7.8 Retrieve <fanOutPoint> | This procedure shall be used for retrieving the content of all member resources belonging to an existing <group> resource. Table 10.2.7.8-1: <fanOutPoint> RETRIEVE <fanOutPoint> RETRIEVE Associated Reference Point Mca, Mcc and Mcc' Information in Request message From: Identifier of the AE or the CSE that initiates the ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.7.9 Update <fanOutPoint> | This procedure shall be used for updating the content of all member resources belonging to an existing <group> resource. Table 10.2.7.9-1: <fanOutPoint> UPDATE <fanOutPoint> UPDATE Associated Reference Point Mca, Mcc and Mcc' Information in Request message From: Identifier of the AE or the CSE that initiates the Reques... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.7.10 Delete <fanOutPoint> | This procedure shall be used for deleting the content of all members resources belonging to an existing <group> resource. Table 10.2.7.10-1: <fanOutPoint> DELETE <fanOutPoint> DELETE Associated Reference Point Mca, Mcc and Mcc' Information in Request message From: Identifier of the AE or the CSE that initiates the Requ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.7.11 Subscribe and Un-Subscribe <fanOutPoint> of a group | This procedure shall be used for receiving information about modifications of all member resources belonging to an existing <group> resource. Table 10.2.7.11-1: <fanOutPoint> Subscribe/Un-subscribe <fanOutPoint> Subscribe/Un-subscribe Associated Reference Point Mca, Mcc and Mcc' Information in Request message From: Ide... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.7.12 Aggregate the Notifications by group | This procedure shall be used for the group Hosting CSE to aggregate the notifications from member hosting CSEs and forward the aggregated notification to the subscriber. Table 10.2.7.12-1: Aggregation of Notifications by group Aggregate Notifications by group Associated Reference Point Mca, Mcc and Mcc' Information in ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.8 <mgmtObj> Resource Procedures | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.8.1 Introduction | This clause describes the management procedures over Mca and Mcc reference points. If external management technologies are used for management, different operations addressing a <mgmtObj> resource (or its attributes or child resources) shall be translated into existing management commands and procedures performed on th... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.8.2 Create <mgmtObj> | This procedure shall be used to create a specific <mgmtObj> resource in the Hosting CSE to expose the corresponding management function of a managed entity (i.e. M2M Device/Gateway) over the Mca reference point. Depending on the data model being used, the created <mgmtObj> resource may be a partial or complete mapping ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.8.3 Retrieve <mgmtObj> | This procedure shall be used to retrieve information from an existing <mgmtObj> resource. The procedure in the following table shall be used when management is performed using external management technologies. If the management is performed by service layer entities, the procedure is the same as generic retrieve proced... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.8.4 Update <mgmtObj> | This procedure shall be used to update information of an existing <mgmtObj> resource. The procedure in the following table shall be used when management is performed using external management technologies. If the management is performed by service layer entities, the procedure is the same as generic update procedure de... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.8.5 Delete <mgmtObj> | This procedure shall be used to delete an existing <mgmtObj> resource. An IN-AE uses this procedure to remove the corresponding external management object (e.g. an obsolete software package) from the managed entity. The procedure in the following table shall be used when management is performed using external managemen... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.8.6 Execute <mgmtObj> | This procedure shall be used to execute a management command on a managed entity through an existing <mgmtObj> resource on the Hosting CSE. Table 10.2.8.6-1: <mgmtObj> EXECUTE <mgmtObj> EXECUTE Associated Reference Point Mcc and Mca Information in Request message From: Identifier of the IN-AE, or the CSE that initiates... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.9 External Management Operations through <mgmtCmd> | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.9.1 Introduction | This clause describes how RESTful management operations may be performed using <mgmtCmd> resources over the Mca and Mcc reference points. The <mgmtCmd> resource, together with its attributes or sub-resources, may be used in the process of translating between RESTful operations and management commands and procedures fro... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.9.2 Create <mgmtCmd> | A CREATE request shall be used by an Originator to create a specific <mgmtCmd> resource in a Hosting CSE. The created <mgmtCmd> resource will be mapping a RESTful method to management commands and/or procedures which may be translated from existing management protocols (e.g. BBF TR-069 [i.3]). At run-time the Hosting C... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.9.3 Retrieve <mgmtCmd> | This procedure shall be used for retrieving all or part information from a previously created <mgmtCmd> resource on a target CSE. The Originator may be: • An AE. • A CSE. The Receiver shall be an IN-CSE. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 186 Table 10.2.9.3-1: <mgmtCmd> RETRIEVE <mgmtCmd> RETRIEVE Associated referen... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.9.4 Update <mgmtCmd> | This procedure shall be used for updating all or part information of an existing <mgmtCmd> resource with new attributes. The Originator may be: • An AE. • A CSE. The Receiver shall be an IN-CSE. Table 10.2.9.4-1: <mgmtCmd> UPDATE <mgmtCmd> UPDATE Associated reference point Mcc and Mca Information in Request message Acc... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.9.5 Delete <mgmtCmd> | This procedure shall be used for deletion of an existing <mgmtCmd> resource on a Hosting CSE. An AE may also use this procedure to cancel any initiated <execInstance> of an <mgmtCmd> if applicable. The Originator may be: • The CSE on the manageable entity: In this case, the CSE issues the request to the Hosting CSE to ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.9.6 Execute <mgmtCmd> | The Execute procedure shall be used by an Originator for execution of a specific management command on a managed entity, through an existing <mgmtCmd> resource on the Hosting CSE. The Originator shall request to execute a specific management command which is represented by an existing <mgmtCmd> resource by using an UPD... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.9.7 Cancel <execInstance> | The Cancel procedure shall be used by an originating AE to disable/stop/cancel an initiated management command execution on the remote entity, through an existing <execInstance> resource on the Hosting CSE. The Originator shall be an AE. The Receiver shall be an IN-CSE. Table 10.2.9.7-1: <execInstance> CANCEL <execInst... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.9.8 Retrieve <execInstance> | This procedure shall be used for retrieving all or part information from an <execInstance> resource on a target CSE. The Originator shall be an AE. The Receiver shall be an IN-CSE. Table 10.2.9.8-1: <execInstance> RETRIEVE <execInstance> RETRIEVE Associated Reference Points Mca Information in Request message According ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.9.9 Delete <execInstance> | The DELETE request procedure shall be used by an originating AE to delete an existing <execInstance> resource on a Receiver IN-CSE. The Originator shall be an AE. NOTE 1: The Receiver IN-CSE in the network domain could also delete an <execInstance> resource locally by itself. This internal procedure is out of scope. NO... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.10.1 Procedure related to <locationPolicy> resource | This clause introduces the procedures for obtaining and managing a target M2M Node's location information, which are associated with the <locationPolicy> resource that contains the method for obtaining and managing location information. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.10.1.1 Create <locationPolicy> | This procedure shall be used for creating a <locationPolicy> resource. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 192 Table 10.2.10.1.1-1: <locationPolicy> CREATE <locationPolicy> CREATE Associated Reference Point Mca, Mcc and Mcc' Information in Request message From: Identifier of the AE or the CSE that initiates the Reque... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.10.1.2 Retrieve <locationPolicy> | This procedure shall be used for retrieving an existing <locationPolicy> resource. Originator: The Originator shall request to obtain <locationPolicy> resource information by using RETRIEVE operation. The Originator is either an AE or a CSE. Receiver: The Receiver shall check if the Originator has RETRIEVE permission o... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.10.1.3 Update <locationPolicy> | This procedure shall be used for updating an existing <locationPolicy> resource. Originator: The Originator shall request to update attributes of an existing <locationPolicy> resource by using an UPDATE operation. The request shall address the specific <locationPolicy> resource of a CSE. The Originator may be either an... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.10.1.4 Delete <locationPolicy> | This procedure shall be used for deleting an existing <locationPolicy> resource. Originator: The Originator shall request to delete an existing <locationPolicy> resource by using the DELETE operation. The Originator may be either an AE or a CSE. This request can be occurred when the locationSource attribute of the crea... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.10.2.1 Procedure for <container> resource that stores the location information | This procedure is mainly triggered by the creation of <locationPolicy> resource. Based on the defined attributes related to the <container> resource such as 'locationContainerID' and 'locationContainerName', the Hosting CSE will create <container> resource to store the location information in its child resource, <conte... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.10.2.2 Procedure for <contentInstance> resource that stores location information | After the <container> resource that stores the location information is created, each instance of location information will be stored in the different <contentInstance> resources. In order to store the location information in the <contentInstance> resource, the Hosting CSE firstly checks the defined locationUpdatePeriod... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.11.1 Introduction | An Originator may create a <subscription> resource on a subscribed-to resource Hosting CSE to be notified when the resource is modified. After successful <subscription> resource creation, the Hosting CSE shall notify the Originator of a subscribed-to resource modification that meets conditions configured in the <subscr... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.11.2 Create <subscription> | This procedure shall be used to request the creation of a new <subscription> resource to be notified for the modifications of a subscribed-to resource. The generic create procedure is described in clause 10.1.1.1. Table 10.2.11.2-1: <subscription> CREATE <subscription> CREATE Associated Reference Point Mca, Mcc and Mcc... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.