hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.11.3 Retrieve <subscription> | This procedure shall be used to retrieve attributes and child resource information of a <subscription> resource. The generic retrieve procedure is described in clause 10.1.2. Table 10.2.11.3-1: <subscription> RETRIEVE <subscription> RETRIEVE Associated Reference Point Mca, Mcc and Mcc' Information in Request message Al... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.11.4 Update <subscription> | This procedure shall be used to update an existing subscription, e.g. extension of its lifetime or the modification of the list of notificationURI(s). The generic update procedure is described in clause 10.1.3. Table 10.2.11.4-1: <subscription> UPDATE <subscription> UPDATE Associated Reference Point Mca, Mcc and Mcc' I... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.11.5 Delete <subscription> | This procedure shall be used to unsubscribe an existing subscription. The generic delete procedure is described in clause 10.1.4.1. Table 10.2.11.5-1: <subscription> DELETE <subscription> DELETE Associated Reference Point Mca, Mcc and Mcc' Information in Request message All parameters defined in table 8.1.2.1-1 apply P... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.12.1 Procedure for Originator of Notifications | When a CSE receives a <subscription> creation request which needs verification (see clause 10.2.11.2), the CSE may become an Originator of a notification to perform verification. In this case, the notification shall include the Originator ID of the <subscription> resource creation. When there is an event for a <subscri... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.12.2 Procedure for Target Receivers of Notifications | If the Notify request requests resource subscription verification to the Receiver by including the Originator ID of the subscription creation, the Receiver shall check if the Notify Originator and the corresponding <subscription> creation Originator have NOTIFY privilege. • If either of the two checks are not successfu... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.13.1 Introduction | An AE or a CSE that is request unreachable cannot receive a request from other entities directly. Instead this AE/CSE can retrieve requests that others sent to this AE/CSE once it created <pollingChannel> resource on a request reachable CSE. This clause consist of manipulation procedures of <pollingChannel> resource, r... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.13.2 Create <pollingChannel> | Table 10.2.13.2-1: <pollingChannel> CREATE <pollingChannel> CREATE Associated Reference Point Mca and Mcc Information in Request message All parameters defined in table 8.1.2.1-1 apply with the specific details for: To: Address of <AE> or <remoteCSE> resource Content: attributes of the <pollingChannel> resource as defi... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.13.3 Retrieve <pollingChannel> | This procedure is used to retrieve a <pollingChannel> resource and an AE/CSE can be an Originator. Table 10.2.13.3-1: <pollingChannel> RETRIEVE <pollingChannel> RETRIEVE Associated Reference Point Mca and Mcc Information in Request message All parameters defined in table 8.1.2.1-1 apply with the specific details for: C... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.13.4 Update <pollingChannel> | This procedure is used to update a <pollingChannel> resource and an AE/CSE can be an Originator. Table 10.2.13.4-1: <pollingChannel> UPDATE <pollingChannel> UPDATE Associated Reference Point Mca 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.13.5 Delete <pollingChannel> | This procedure is used to delete a <pollingChannel> resource and an AE/CSE can be an Originator. Table 10.2.13.5-1: <pollingChannel> DELETE <pollingChannel> DELETE Associated Reference Point Mca and Mcc Information in Request message All parameters defined in table 8.1.2.1-1 apply Processing at Originator before sendin... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.13.6 Re-targeting Requests to Polling Channel | This procedure is used to re-target a request targeting a request-unreachable AE/CSE. When a <pollingChannel> Hosting CSE receives a request to the request-unreachable AE/CSE, it internally re-targets the request to the <pollingChannel> of the AE/CSE. It is assumed that the request-unreachable AE/CSE already set its re... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.13.7 Long Polling on Polling Channel | This procedure is originated by a request-unreachable entity to poll requests from a polling channel. Once the Originator starts Long Polling on a polling channel by sending a RETRIEVE request, the Receiver who is the <pollingChannel> Hosting CSE holds the request until it has any requests to return to the Originator. ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.14.1 Create <node> | This procedure shall be used for creating a <node> resource. NOTE: The creation of the <node> resource is on discretion of the Originator. In general the resource is created when the Originator is not always reachable and therefore it is convenient that the entity that the Originator is registered to is aware of the ch... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.14.2 Retrieve <node> | This procedure shall be used for retrieving the attributes of a <node> resource. Table 10.2.14.2-1: <node> RETRIEVE <node> 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 Processing at Origi... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.14.3 Update <node> | This procedure shall be used for updating the attributes and the actual data of a <node> resource and its child resources. Table 10.2.14.3-1: <node> UPDATE <node> DELETE 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 ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.14.4 Delete <node> | This procedure shall be used for deleting an existing <node> resource. Table 10.2.14.4-1: <node> DELETE <node> 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 clause 10.1.4 Pro... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.1 Introduction | Clause 10.2.15.1 is informative and provides a use case example to explain how the Infrastructure Node provides statistics for AEs using the <statsConfig> and <statsCollect> resources as defined in clauses 9.6.23, 9.6.24.and 9.6.25. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 206 |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.1.1 Service Event-based Statistics Collection for Applications | Figure 10.2.15.1-1 shows an example of service layer event-based charging based on the Infrastructure Node. Step 1-2: A statistics collection resource called <statsConfigSCA1> was created at the IN-CSE by a billing application. Note that the <statsConfig> can also be provisioned. In this use case, the <statsConfigSCA1>... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.2 Create <statsConfig> | This procedure shall be used for the Originator to establish a set of configurations for statistics collection at the Receiver. The configurations shall be stored at the <statsConfig> resource and each instance of the <statsConfig> resource shall represent a specific configuration. The Originator shall be an AE that wa... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.3 Retrieve <statsConfig> | The RETRIEVE procedure shall be used for the Originator to retrieve the existing <statsConfig> resource from the Receiver. The Originator shall be an AE that is allowed to retrieve configuration information available for AEs within an IN-CSE. The Receiver shall be the IN- CSE containing the <statsConfig> resource. Tabl... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.4 Update <statsConfig> | This procedure shall be used for updating <statsConfig> resource. An UPDATE procedure on the <statsConfig> resource is used for the Originator to update charging related policies at the Receiver. The Originator shall be the AE that created the <statsConfig> resource. The same AE shall be able to update the resource. Th... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.5 Delete <statsConfig> | This procedure shall be used for deleting <statsConfig> resource. The Originator shall be the AE that created the <statsConfig> resource. The Receiver shall be a CSE containing the <statsConfig> resource. Table 10.2.15.5-1: <statsConfig> DELETE <statsConfig> DELETE Associated Reference Points Mca Information in Request... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.7 Retrieve <eventConfig> | The RETRIEVE procedure shall be used for the Originator to retrieve the existing <eventConfig> resource from the Receiver. The Originator shall be an AE that is allowed to retrieve configuration information available for AEs within an IN-CSE. The Receiver shall be the IN-CSE containing the <eventConfig> resource. Table... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.8 Update <eventConfig> | This procedure shall be used for updating an existing <eventConfig> resource. The Originator shall be the AE that created the <eventConfig> resource. The same AE shall be able to update the resource. The Receiver shall be the IN-CSE containing the <eventConfig> resource. Table 10.2.15.8-1: <eventConfig> UPDATE <eventCo... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.9 Delete <eventConfig> | This procedure shall be used for deleting <eventConfig> resource. The Originator shall be the AE that created the <eventConfig> resource. The Receiver shall be the IN-CSE containing the <eventConfig> resource. Table 10.2.15.9-1: <eventConfig> DELETE <eventConfig> DELETE Associated Reference Points Mca Information in Re... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.10 Create <statsCollect> | This procedure shall be used for the Originator to establish collection scenarios at the Receiver. The collection scenarios are stored at the <statsCollect> resource. Multiple collection scenarios can be created based on one instance of <statsConfig>. The Receiver shall be an IN-CSE. The Receiver shall validate whether... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.11 Retrieve <statsCollect> | The RETRIEVE procedure shall be used for the Originator to retrieve the existing <statsCollect> resource from the Receiver. The Originator shall be an AE that is allowed to retrieve the collection scenario information from the IN-CSE. The Receiver shall be the IN- CSE containing the <statsCollect> resource. ETSI ETSI T... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.12 Update <statsCollect> | An UPDATE procedure on the <statsCollect> resource shall be used for the Originator to update chargeable scenarios at the Receiver. The Originator shall be the AE that created the <statsCollect> resource. The same AE shall be able to update the resource. The Receiver shall be the IN-CSE containing the <statsCollect> re... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.13 Delete <statsCollect> | This procedure shall be used for deleting <statsCollect> resource. The Originator shall be the AE that created the <statsCollect> resource. The Receiver shall be a CSE containing the <statsCollect> resource. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 214 Table10.2.15.13-1: <statsCollect> DELETE <statsCollect> DELETE Associa... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.15.14 Service Statistics Collection Record | When the Service Statistics Collection is supported, the Information Elements shall be generated according to table 10.2.15.14-1. The contents of each Service statistics collection record are decided by the specific collection scenario that triggered the information recording. Transfer of the Statistics Collection Reco... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.16.1 Create <m2mServiceSubscriptionProfile> | This procedure shall be used for creating a <m2mServiceSubscriptionProfile> resource. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 215 Table 10.2.16.1-1: <m2mServiceSubscriptionProfile> CREATE <m2mServiceSubscriptionProfile> CREATE Associated Reference Point Mca and Mcc Information in Request message All parameters defined in... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.16.2 Retrieve <m2mServiceSubscriptionProfile> | This procedure shall be used for retrieving the attributes of a <m2mServiceSubscriptionProfile> resource. Table 10.2.16.2-1: <m2mServiceSubscriptionProfile> RETRIEVE <m2mServiceSubscriptionProfile> RETRIEVE Associated Reference Point Mca, Mcc, Mcc' Information in Request message All parameters defined in table 8.1.2.1-... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.16.3 Update <m2mServiceSubscriptionProfile> | This procedure shall be used for updating the attributes of a <m2mServiceSubscriptionProfile> resource. Table 10.2.16.3-1: <m2mServiceSubscriptionProfile> UPDATE <m2mServiceSubscriptionProfile> UPDATE Associated Reference Point Mca and Mcc Information in Request message All parameters defined in table 8.1.2.1-1 are app... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.16.4 Delete <m2mServiceSubscriptionProfile> | This procedure shall be used for deleting a <m2mServiceSubscriptionProfile> resource residing under a <m2mServiceSubscriptionProfile> resource. Table 10.2.16.4-1: <m2mServiceSubscriptionProfile> DELETE <m2mServiceSubscriptionProfile> DELETE Associated Reference Point Mca and Mcc Information in Request message All param... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.17.1 Create <serviceSubscribedNode> | This procedure shall be used for creating a <serviceSubscribedNode> resource which is sub-resource of <m2mServiceSubscriptionProfile> resource. Table 10.2.17.1-1: <serviceSubscribedNode> CREATE <serviceSubscribedNode> CREATE Associated Reference Point Mca and Mcc Information in Request message All parameters defined in... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.17.2 Retrieve <serviceSubscribedNode> | This procedure shall be used for retrieving the attributes of a <serviceSubscribedNode> resource which is sub-resource of <m2mServiceSubscriptionProfile> resource. Table 10.2.17.2-1: <serviceSubscribedNode> RETRIEVE <serviceSubscribedNode> RETRIEVE Associated Reference Point Mca, Mcc and Mcc' Information in Request mes... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.17.3 Update <serviceSubscribedNode> | This procedure shall be used for updating the attributes of a <serviceSubscribedNode> resource which is sub-resource of <m2mServiceSubscriptionProfile> resource. Table 10.2.17.3-1: <serviceSubscribedNode> UPDATE <serviceSubscribedNode> UPDATE Associated Reference Point Mca and Mcc Information in Request message All par... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.17.4 Delete <serviceSubscribedNode> | This procedure shall be used for deleting a <serviceSubscribedNode> resource residing under a <m2mServiceSubscriptionProfile> resource. Table 10.2.17.4-1: <serviceSubscribedNode> DELETE <serviceSubscribedNode> DELETE Associated Reference Point Mca and Mcc Information in Request message All parameters defined in table 8... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.18.1 Procedure for AE and CSE to initiate Creation of an Announced Resource | This clause describes the procedure for an AE or a CSE to initiate the creation of an announced resource. The Originator of a Request for initiating resource announcement can be either an AE or a CSE. Two methods are supported for initiating the creation of an announced resource. • CREATE: The Originator can initiate t... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.18.3 Procedure for AE and CSE to initiate Deletion of an Announced Resource | This clause describes the procedure that shall be used for an AE or a CSE (not the original resource Hosting CSE) to initiate the deletion of an announced resource. The Originator of a Request for initiating resource de-announcement can be either an AE or a CSE. Two methods are supported for initiating resource de-anno... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.18.6 Procedure for AE and CSE to initiate the Creation of an Announced Attribute | This clause describes the procedure that shall be used for an AE and CSE (not the original resource Hosting CSE) to initiate the creation of an announced attribute (attribute announcement). The Originator of a Request, for initiating attribute announcement, can be either AE or CSE (not the original resource Hosting CSE... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.18.7 Procedure for AE and CSE to initiate the Deletion of an Announced Attribute | This clause describes the procedure that shall be used for an AE and CSE (not the original resource Hosting CSE) to initiate the deletion of announced attributes (attribute de-announcement). The Originator of a Request, for initiating attribute de-announcement, can be either AE or CSE (not the original resource Hosting... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.18.8 Procedure for original resource Hosting CSE for Announcing Attributes | This clause describes procedure that shall be used by the original resource Hosting CSE to create announced attributes at the remote announced resources (i.e. the attribute announcement). The Originator of this Request shall be the original resource Hosting CSE. Table 10.2.18.8-1: Original Resource Hosting CSE to Annou... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.18.9 Procedure for original resource Hosting CSE for De-Announcing Attributes | This clause describes procedure that shall be used by the original resource Hosting CSE to remove announced attributes at remote announced resources (i.e. the attribute de-announcement). The Originator of this Request shall be the original resource Hosting CSE. Table 10.2.18.9-1: Original Resource Hosting CSE to De-Ann... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.18.10 Notification Procedure targeting an AE Announced Resource | This clause describes handling of notifications received at an <AEAnnc> resource Hosting CSE. Table 10.2.18.10-1: Notification Procedure for AE Announced Resource Notification Procedure for AE Announced Resource Associated Reference Point Mcc Information in Request message Notification message made according to clause ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.19.1 Introduction | This clause describes the management procedures for the <contentInstance> resource. Since <contentInstance> resource is immutable once created, there is no procedure for updating it. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.19.2 <contentInstance> CREATE | This procedures shall be used for creating a <contentInstance> resource. Table 10.2.19.2-1: <contentInstance> CREATE <contentInstance> 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 ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.19.3 <contentInstance> RETRIEVE | This procedure shall be used for retrieving the attributes of a <contentInstance> resource. Table 10.2.19.3-1: <contentInstance> RETRIEVE <contentInstance> RETRIEVE Associated Reference Point Mca, Mcc and Mcc'. Information in Request message According to clause 10.1.2. Processing at Originator before sending Request Ac... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.19.4 <contentInstance> UPDATE | The Update operation shall not apply to <contentInstance> resource. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.19.5 <contentInstance> DELETE | This procedure shall be used for deleting a <contentInstance> resource residing under a <container> resource. Table 10.2.19.5-1: <contentInstance> DELETE <contentInstance> 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 Or... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.20.1 Create <request> | As specified in clause 9.6.12, creation of a <request> resource can only be done on a Receiver CSE implicitly when a Registree AE or a Registree/Registrar CSE of the Receiver CSE issues a request to the Receiver CSE for targeting any other resource type or requesting a notification in non-blocking mode. Therefore, the ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.20.2 Retrieve <request> | This procedure shall be used for retrieving the attributes of a <request> resource. Table 10.2.20.2-1: <request> RETRIEVE <request> 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 Pre-Proces... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.20.3 Update <request> | For a <request> resource explicit update requests shall not be supported. Changes in the attributes of a <request> resource can only be done by the Hosting CSE due to changes of the status of the associated non-blocking request that implied the creation of this <request> resource or due to reception of an operation res... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.20.4 Delete <request> | This procedure shall be used for deleting an existing <request> resource. Deletion of an existing <request> resource shall terminate any further processing of an associated pending non-blocking request that implied the creation of this <request> resource if the pending request was not already completed or forwarded. Ta... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.21.1 Create <accessControlPolicy> | This procedure shall be used to create an <accessControlPolicy> resource. Table 10.2.21.1-1: <accessControlPolicy> CREATE <accessControlPolicy> CREATE Associated Reference Point Mca, Mcc and Mcc'. Information in Request message Same as clause 10.1.1. Pre-Processing at Originator Same as clause 10.1.1. Processing at Rec... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.21.2 Retrieve <accessControlPolicy> | This procedure shall be used to retrieve attributes and child resource information of the <accessControlPolicy> resource. Table 10.2.21.2-1: <accessControlPolicy> RETRIEVE <accessControlPolicy> RETRIEVE Associated Reference Point Mca, Mcc and Mcc'. Information in Request message Same as clause 10.1.2. Pre-Processing at... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.21.3 Update <accessControlPolicy> | This procedure shall be used to update attributes information of the <accessControlPolicy> resource. Table 10.2.21.3-1: <accessControlPolicy> UPDATE <accessControlPolicy> UPDATE Associated Reference Point Mca, Mcc and Mcc'. Information in Request message Same as clause 10.1.3. Pre-Processing at Originator Same as claus... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.21.4 Delete <accessControlPolicy> | This procedure shall be used to delete the <accessControlPolicy> resource. Table 10.2.21.3-1: <accessControlPolicy> DELETE <accessControlPolicy> DELETE Associated Reference Point Mca, Mcc and Mcc' Information in Request message Same as clause 10.1.4. Pre-Processing at Originator Same as clause 10.1.4. Processing at Rec... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.22.1 Retrieve <latest> | This procedure shall apply to the latest <contentInstance> resource among all existing <contentInstance> resources in the parent <container> resource. If there is no <contentInstance> resource in the parent, then the Receiver shall responsed with an error. This procedure is the same as the procedures in clause 10.2.19.... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.22.2 Delete <latest> | This procedure shall apply to the latest <contentInstance> resource among all existing <contentInstance> resources in the parent <container> resource. If there is no <contentInstance> resource in the parent, then the Receiver shall responsed with an error. After deletion, the <latest> contentInstance will point to the ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.23.1 Retrieve <oldest> | This procedure shall apply to the oldest <contentInstance> resource among all existing <contentInstance> resources in the parent <container> resource. If there is no <contentInstance> resource in the parent, then the Receiver shall responsed with an error. This procedure is the same as the procedures in clause 10.2.19.... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.23.2 Delete <oldest> | This procedure shall apply to the oldest <contentInstance> resource among all existing <contentInstance> resources in the parent <container> resource. If there is no <contentInstance> resource in the parent, then the Receiver shall responsed with an error. After deletion, the <oldest> contentInstance will point to the ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.24.1 Create <serviceSubscribedAppRule> | This procedure shall be used for creating an <serviceSubscribedAppRule> resource. The information represented in the attributes of a <serviceSubscribedAppRule> resource impacts the Application Entity Registration procedure as outlined in clause 10.1.1.2.2. Instances of <serviceSubscribedAppRule> resources are associate... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.24.2 Retrieve <serviceSubscribedAppRule> | This procedure shall be used for retrieving the representation of the <serviceSubscribedAppRule> resource. Table 10.2.24.2-1: <serviceSubscribedAppRule> RETRIEVE <serviceSubscribedAppRule> RETRIEVE Associated Reference Point Mca Mcc and Mcc' Information in Request message All parameters defined in table 8.1.2.1-1 apply... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.24.3 Update <serviceSubscribedAppRule> | This procedure shall be used for updating the attributes of the <serviceSubscribedAppRule> resource. Table 10.2.24.3-1: <serviceSubscribedAppRule> UPDATE <serviceSubscribedAppRule> UPDATE Associated Reference Point Mca and Information in Request message All parameters defined in table 8.1.2.1-1 apply with the specific ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 10.2.24.4 Delete <serviceSubscribedAppRule> | This procedure shall be used for deleting the <serviceSubscribedAppRule> resource with all related information. Table 10.2.24.4-1: <serviceSubscribedAppRule> DELETE <serviceSubscribedAppRule> DELETE Associated Reference Point Mca, Mcc Information in Request message All parameters defined in table 8.1.2.1-1 apply with t... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 11 Trust Enabling Architecture | The Trust Enabling Architecture serves the purpose of establishing security and trust between all parties involved in the M2M ecosystem. It comprises the following infrastructure functions which may be external to the CSEs: • M2M Enrolment functions, which manage the enrolment of M2M Nodes and M2M applications for acce... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 11.2 M2M Initial Provisioning Procedures | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 11.2.1 M2M Node Enrolment and Service Provisioning | M2M service provisioning is the process by which M2M Nodes are loaded with the specific information needed to seamlessly access the M2M Services offered by an M2M Service Provider. This is an initial step performed only when an M2M Node is enrolled for using the M2M services of an M2M Service Provider. Though this proc... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 11.2.2 M2M Application Enrolment | This procedure is an optional step that enables the M2M SP and/or M2M application provider to control which applications are allowed to use the M2M services. It assumes that M2M applications obtains or registers credentials to be used for controlling authorization with an M2M application registration authority (see cla... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 11.3 M2M Operational Security Procedures | This clause introduces high level procedures that shall be performed before any other procedure on Mcc and Mca can take place. Figure 11.3-1. High Level Procedures on Mcc or Mca ETSI ETSI TS 118 101 V1.0.0 (2015-02) 237 |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 11.3.1 Identification of CSE and AE | Identification is the process of identifying CSEs and AEs with the associated M2M service subscription to an M2M Authentication Function. The Identification procedure shall be implemented as specified in the oneM2M Security Solutions Technical Specification [1]. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 11.3.2 Authentication of CSE and AE | Prior to granting access to M2M services, the credentials resulting from the M2M Node and M2M application enrolment procedures shall be used, together with the identities supplied in the identification step, to perform mutual authentication of the entities (AEs or CSEs) with an M2M Authentication Function. Upon mutual ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 11.3.3 M2M Security Association Establishment | The M2M Security Association Establishment procedure is performed to generate a security credential (M2M Connection key) shared between communicating AEs/CSEs, when an AE/CSE on one node initiates communication with an AE/CSE on another node. This procedure is performed as part of Security Context Establishment (see fi... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 11.3.4 M2M Authorization Procedure | The M2M authorization procedure controls access to resources and services by CSEs and AEs. This procedure requires that the Originator has been identified to an M2M Authentication Function and mutually authenticated and associated with an M2M Service Subscription. Authorization depends on: • The privileges set by the M... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12 Information Recording | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.1 M2M Infrastructure Node (IN) Information Recording | Various informational elements have to be recorded by the M2M infrastructure nodes for a variety of reasons including but not limited to statistics, charging, maintenance, diagnostics, etc. This clause describes a framework for recording the necessary information by infrastructure nodes. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.1.1 Information Recording Triggers | Triggers have to be configured in the IN node by the M2M service provider to initiate information recording. The M2M infrastructure nodes shall be able to initiate recording based on any of the following triggers: • A request received by the M2M IN over the Mcc reference point. • A request received by the M2M IN over t... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.1.2 M2M Recorded Information Elements | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.1.2.1 Unit of Recording | A unit of recording refers to a number of informational elements recorded by the IN and that can be used as a basis for additional post-processing for a specific purpose such as generating Charging Data Records (CDRs), statistics, etc. In that respect, each unit of recording can be thought of as an M2M information reco... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.1.2.2 Information Elements within an M2M Event Record | The information elements within an M2M event record are defined in table 12.1.2.2-1. Every M2M event record shall be tagged to depict its content according to the following classification: • Data related procedures: represent procedures associated with data storage or retrieval from the M2M IN (e.g. Container related p... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.1.3 Identities Associations in Support of Recorded Information | To enable the M2M IN to record the necessary information, as described above, the following associations shall be maintained by the M2M service provider: • The CSE-ID (for all M2M Nodes in the M2M framework) and the allocated M2M subscription ID. • The AE-ID and the allocated M2M subscription ID. For established associ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.2 Offline Charging | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.2.1 Architecture | Figure 12.2.1-1 depicts the charging architecture. Charging information, in the form of charging data records (CDRs), shall be derived from recorded information, and transferred to a Charging Server. As such, it is essential that all information required for charging shall be first selected for recording. There shall b... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.2.2 Filtering of Recorded Information for Offline Charging | Recorded information is the basis for offline charging. To fulfil the needs of different billing systems not all recorded information is required in all cases. Hence, the M2M Charging Function shall be configurable to only select the desired information from the recorded information for transfer to the Charging Server.... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.2.3 Examples of Charging Scenarios | Charging scenarios refer to scenarios for which an M2M entity can be billed if the scenario is deemed billable by the M2M service provider. Some charging scenarios may require single CDR. Other scenarios may require multiple CDRs, and suitable correlation information shall have to be identified to select the CDRs for t... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.2.3.1 Example Charging Scenario 1 - Data Storage Resource Consumption | In this scenario, the M2M entity that stores application data, using container procedures for that purpose, will be billed, for storage resources within the M2M IN, until such time as the resources are deleted. This scenario will require correlation between multiple CDRs to identify the entity that stored the data, the... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.2.3.2 Example Charging Scenario 2 - Data transfer | In this scenario, the M2M entity that retrieves/stores container data will be billed for the amount of transferred data. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.2.3.3 Example Charging Scenario 3 - Connectivity | This scenario is relevant for an M2M entity that contacts the M2M IN frequently to transfer small amounts of data for storage. In this scenario, the M2M entity will be charged for the connectivity as opposed to the stored amount of data. The same applies to an M2M entity that also contacts frequently the M2M IN to retr... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.2.4 Definition of Charging Information | Charging information in the form of CDR is essentially a subset of the information elements within the M2M event records recorded by the M2M IN for transmission over the Mch reference point. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.2.4.1 Triggers for Charging Information | The charging function within the M2M IN shall initiate transmission of CDRs if configured for that purpose in accordance with clause 12.2.2. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.2.4.2 Charging Messages over Mch Reference Point | The Mch shall be used in case the CDRs are to be transferred to an external Charging Server. It is assumed that the Mch is equivalent to the Rf reference point as defined in [i.16] and [i.17]. Hence, every CDR shall be transferred in a single message, namely Accounting-Request and that elicits a response, namely Accoun... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.2.4.3 Structure of the Accounting Message Formats | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.2.4.3.1 Accounting-Request Message | Table 12.2.4.3.1-1 illustrates the basic structure of an ACR message generated from the M2M IN for offline charging in accordance with [i.16], [i.17], [i.9] and [i.12]. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 243 Table 12.2.4.3.1-1: Accounting-Request (ACR) message contents Informational Element Category Description Sess... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 12.2.4.3.2 Accounting-Answer Message | Table 12.2.4.3.2-1 illustrates the basic structure of an ACA message generated by the charging server as a response to an ACR message. Table 12.2.4.3.2-1: Accounting-Answer (ACA) message contents Information element Category Description Session-Id M Same as table 12.2.4.3.1-1 Origin-Host M Same as table 12.2.4.3.1-1 Or... |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 1 Scope | The present document supports the requirements of ETSI EN 305 174-8 [9] providing a framework for, and detailing, the necessary implementation procedures. The present document specifically extends the end-of-life aspects of ICT equipment to the treatment of components and sub-assemblies replaced during maintenance proc... |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 2 References | |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 3 Definition of terms, symbols and abbreviations |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.