hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.4.5.3 M2M Service Connection Parameter Delivery Procedure Primitives | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.4.5.3.1 connectionParamSetExecuteRequestIndication | This request is used by the D/G M2M Node to request the MAS to establish an M2M Service Connection with the Network M2M Node containing an identified NSCL. The primitive shall comply with table 7.2. The format of the primitive attributes shall conform to clauses 11.6 and 12.3. Table 7.2: connectionParamSetExecuteReques... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.4.5.3.2 connectionParamSetExecuteResponseConfirm (successful case) | This primitive confirms the establishment of an M2M Service Connection with the Network M2M Node containing an identified NSCL, and contains the parameters associated with the established M2M Service Connection. The primitive shall comply with table 7.3. The format of the primitive attributes shall conform to clause 11... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.4.5.3.3 connectionParamSetExecuteResponseConfirm (unsuccessful case) | The connectionParamSetExecuteRequestIndication primitive triggers this response. The primitive shall comply with table 7.4. The format of the primitive attributes shall conform to clause 11.6. Table 7.4: connectionParamSetExecuteResponseConfirm (unsuccessful case) connectionParamSetExecute Primitive: connectionParamSet... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.4.5.4 M2M Service Connection Parameter Delivery Procedure Pre-Conditions | The following pre-conditions are necessary for a successful connectionParamSetExecute exchange: 1) The MAS shall be able to determine the set of mId Security Procedures supported by the identified Network M2M Node, and shall be able to determine the order of preference for any subset of those mId Security Procedures. T... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.4.5.6 M2M Service Connection Parameter Delivery Sequence of Events | The D/G M2M Node shall perform the following actions in sequence: 1) The D/G M2M Node shall compose connectionParamSetExecuteRequestIndication primitive (as defined in table 7.2). ETSI ETSI TS 102 921 V1.3.1 (2014-09) 65 2) The D/G M2M Node shall encode the connectionParamSetExecuteRequestIndication according to the ap... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.5 IVal security attributes in connection establishment | If the M2M Service Provider supports Integrity Validation (IVal), the Network M2M Node shall retrieve the IVal security attributes of the connecting D/G M2M Node from the MAS during M2M Service Connection establishment. The IVal security attributes of the D/G M2M Node shall include IValCapability and an IValKey. NOTE 1... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 8 M2M Secure Communication over mId | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 8.1 Access Network Based Security | If the M2M deployment relies on the access network security, then Kmc is not needed for mId security. The mId procedures defined in the present document may be used without any cryptographic protection when they rely on mechanisms for security not include in the present document. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 8.2 Channel Security | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 8.2.1 Supported Channel Security Methods | The Channel-TLS-Kmc method secures TCP payloads using TLS in RFC 4346 [28] or RFC 5246 [35] with the TLS handshake conforming to TLS-PSK in RFC 4279 [27]. ETSI ETSI TS 102 921 V1.3.1 (2014-09) 69 The Channel-DTLS-Kmc method secures UDP payloads using DTLS in RFC 6347 [72] with the TLS handshake conforming to TLS-PSK as... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 8.2.1.1 Negotiation to use a Channel Security Method | NOTE: Since the M2M Service Connection procedure using GBA (clause 7.2.1) incorporates TLS-PSK as specified in TS 133 222 [7] for mId security, Channel-TLS method is not applicable in this case. A Channel Security method shall be used only if it is negotiated as part of either: • an M2M Service Connection procedure usi... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 8.2.1.3 Details of the DTLS/TLS Handshake | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 8.2.1.3.1 Applicability to DTLS and TLS | NOTE: The DTLS handshake reuses the TLS handshake messages. The Channel-TLS-Kmc method shall conform to all subclauses of clause 8.2.1.3. The Channel-DTLS-Kmc method shall conform to all subclauses of clause 8.2.1.3. ETSI ETSI TS 102 921 V1.3.1 (2014-09) 70 |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 8.2.1.3.2 TLS ClientHello.server_name Field Details For Channel Security Methods | The D/G M2M Node shall include the TLS Extension server_name field (see references to TLS Extensions specifications in clause 8.2.1.2) in the TLS ClientHello Message, and the server_name field shall include the FQDN of the Network M2M Node (this FQDN is presumed to be identical to the FQDN part of the NSCL URI). The Ne... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 8.3 Object Security | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 8.3.1 Securing CoAP-based mId | Securing CoAP using object security is discussed in annex H. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 8.3.2 Securing XML-based mId | If the mId interface is using text-based or binary XML only (i.e. application/xml, application/exi, application/fastinfoset), and an object security mechanism is desired, XML signatures [61] and/or XML encryption v1.1 XML-ENCv1.1 [73] shall be used. If the mId interface is used for content types other than XML (e.g. JS... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 9 Resources | In stage 3 each sub-resource of multiplicity 1 is modelled as an attribute containing a reference to the sub-resource, i.e. containing its resource URI of the sub-resource. Each sub-resource of multiplicity "0..unbounded" is represented as one collection attribute that contains a list of references to the resource URIs... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10 SCL Primitives | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.1 Introduction | The structure of the clause is as follows: • Clause 10.3 describes the common operations of the Create, Retrieve, Update and Delete request and response primitives. These common operations are referenced from the primitive specific handling as described in the primitive specific clauses below. • Clauses 10.4 to 10.39 d... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.2 General aspects | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.2.1 SCL primitives | M2M shall support mIa, dIa and mId, i.e. the support of the API on mIa, dIa and mId as described in the present document is mandatory. The SCL primitives shall apply to the M2M REST interfaces; dIa, mIa and mId. The applicability of per specific primitive is defined in the primitive definition clauses. Each primitive i... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.2.2 Asynchronous and semi-asynchronous processing | The primitives in the following clauses are described in the synchronous processing model, i.e. a RequestIndication is received by the SCL, the receiving SCL performs some actions and sends a ResponseConfirm which indicates either success or error. Although this is the typical interaction, there are cases where the rec... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3 Common operations | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.1 Issuer actions | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.1.1 Compose RequestIndication primitive | The issuer shall compose a RequestIndication message that shall be mapped to a specific protocol. In case the request issuer is a DA, GA or NA and the request is targeting resource(s) not hosted on the local SCL, then the RequestIndication may contain the following additional attributes for store-and-forward (SAF) hand... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.1.2 Send a RequestIndication to the Receiver SCL | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.1.2.1 Determination of the Receiver SCL | The issuer shall determine the receiver SCL. If the issuer is an application, a DSCL registered to an NSCL or a GSCL registered to an NSCL, then receiver SCL shall be the local SCL, i.e. the SCL where the issuer is registered. If the issuer is an NSCL, the receiver SCL is determined based on the targetID as follows; th... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.1.2.2 Selection of communication channel | 10.3.1.2.2.1 Issuer is an M2M Application In case the issuer is an Application the selection of the communication channel and the routing towards the local SCL is not included in the present document: • A DA on a D-type M2M Device or a GA on M2M Gateway is expected to be co-located with the DSCL and GSCL respectively a... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.1.3 Wait for ResponseConfirm primitive | The issuer shall wait for the a ResponseConfirm primitive from the receiver that corresponds to the RequestIndication primitive that was sent by the issuer. Correlation between the RequestIndication and the corresponding ResponseConfirm is handled by the transport layer. If no ResponseConfirm primitive is received with... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2 Hosting SCL actions | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.1 Check existence of the addressed resource | The hosting SCL shall check if the resource addressed by the targetID exists in the repository. If the resource does not exist, the hosting SCL shall reject the request with a "STATUS_NOT_FOUND". |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.2 Check the syntax of received message | Message validity is specified by the protocol mapping annexes. Annex C and by validating the received resource representation (e.g. in plain XML, binary XML or JSON) against the provided schema definitions in annex B. If the message is not valid, the request shall be rejected with a "STATUS_BAD_REQUEST". |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.3 Check validity of resource representation for CREATE | The handling below shall apply t to each attribute in the resource for CREATE request primitives and the handling depends on the "presence in CREATE request" column of the resource table. If the request is rejected based on the rules below, then the other attributes do not have to be checked. If no resource representat... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.4 Check validity of resource representation for UPDATE | The handling below shall apply to each attribute in the resource for UPDATE request primitives and the handling depends on the "presence in UPDATE request" column of the resource table. If the request is rejected based on the rules below, then the other attributes do not have to be checked. ETSI ETSI TS 102 921 V1.3.1 ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.5 Check authorization of the requestingEntity based on accessRightID | Check if the requestingEntity is authorized for the requested action. The authorization is based on the accessRightID attribute of the resource addressed in the targetID. The accessRight resource whose resource URI matches the accessRightID shall be retrieved using the accessRightRetrieveRequestIndication primitive. In... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.6 Check authorization of the requestingEntity based on selfPermission | Check if the requestingEntity, is authorized for the requested action. The authorization is based on the selfPermissions attribute of the accessRight resource. If the accessRight resource is retrieved successfully, the following rules shall apply: • RetrieveRequestIndication: the requestingEntity shall be one of the pe... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.7 Check authorization of the requestingEntity based on default access rights | The default access permissions shall grant all permissions (i.e. the full set of permissionsFlags) to the following permission holders depending on the prefix of URI of the addressed resource; the permissionHolders for prefixes from most specific to least specific are as follows: • <sclBase>/scls/<scl>/applications/<ap... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.8 Announce resource | If an announceable resource contains the announceTo attribute in its representation, the actions described in clause 10.3.2.8.1 shall be applied, even if the announceTo attribute contains an empty list of sclBase resource URIs. If the announceTo attribute is not present in the resource representation, then the actions ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.8.1 Update of announce on request of application | This action shall apply if the following conditions are met: • A new announceable resource is created in the local SCL and the CREATE request contains an announceTo attribute. • The announceTo attribute of the announceable resource is added/changed. The local SCL keeps track of the SCLs where the resource is currently ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.8.2 Update of announce on request of local SCL | This action shall apply if the following conditions are met: • A new announceable resource is created in the local SCL, the CREATE request does not contain an announceTo attribute. • The announceTo attribute is removed from the resource representation by an XXXupdateRequestIndication (where XXX represents the resource ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.8.3 Create announced Resource | The receiver shall execute the following steps in order. In case of error in any of the steps below, the receiver shall execute "Create an unsuccessful ResponseConfirm" (clause 10.3.2.13) and then "Send ResponseConfirm primitive" (clause 10.3.2.17). The corresponding statusCode, as indicated in enumeration StatusCode i... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.8.4 Retrieve announced Resource | The receiver shall execute the following steps in order. In case of error in any of the steps below, the receiver shall execute "Create an unsuccessful ResponseConfirm" (clause 10.3.2.13) and then "Send ResponseConfirm primitive" (clause 10.3.2.17). The corresponding statusCode, as indicated in enumeration StatusCode i... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.8.5 Update announced Resource | The receiver shall execute the following steps in order. In case of error in any of the steps below, the receiver shall execute "Create an unsuccessful ResponseConfirm" (clause 10.3.2.13) and then "Send ResponseConfirm primitive" (clause 10.3.2.17). The corresponding statusCode as indicated in enumeration StatusCode in... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.8.6 Delete announced Resource | The receiver shall execute the following steps in order. In case of error in any of the steps below, the receiver shall execute "Create an unsuccessful ResponseConfirm" (clause 10.3.2.13) and then "Send ResponseConfirm primitive" (clause 10.3.2.17). The corresponding statusCode as indicated in enumeration StatusCode in... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.9 DeAnnounce resource | Deannouncing a resource corresponds to removing the announcement from all the SCLs where the resource is announced. The procedure for deannouncing is the same as the procedure for updating an announcement, where the sclList element is set to the empty list. ETSI ETSI TS 102 921 V1.3.1 (2014-09) 89 |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.10 Create the resource | A new resource shall be created and added to the addressed and existing parent resource. This shall modify the resource representation of the addressed parent resource, specifically, if the parent resource has a lastModifiedTime attribute this shall be set to same value as the creationTime attribute of the created reso... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.11 Create a collection resource representation | The SCL shall construct a resource representation of the collection resource as follows: For each child resource the collection resource representation shall include the URI identifying the child resource. However, the URI is only included if the requestingEntity has discovery permission on the child resource, i.e. the... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.12 Create a successful ResponseConfirm | The receiver shall create a successful ResponseConfirm primitive with a statusCode indicating "STATUS_OK". The response shall include the representation of the addressed resource, if the hosting SCL modified any of the provided attributes as provided in the RequestIndication. The ResponseConfirm shall also include the ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.13 Create an unsuccessful ResponseConfirm | The receiver shall create an unsuccessful ResponseConfirm primitive with a statusCode indicating the detected error condition. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.14 Read the addressed resource | An existing and accessible resource is addressed. The content of its attributes and a references to its sub-resources shall be read in form of resource representation. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.15 Update the addressed resource | An existing and accessible resource is addressed. The content of its attributes shall be updated with the following rules in UPDATE request primitives: M attribute If the provided value is accepted, the server shall use the provided value in the resource representation of the updated resource. If the provided value is ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.16 Delete the addressed resource | An existing and accessible resource is addressed. The resource with all its attributes shall be deleted. Any expiration timer shall be stopped. This same procedure shall then be invoked (recursively) for each sub-resource of the deleted resource. The parent resource of the addressed resource shall be updated to remove ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.17 Send ResponseConfirm primitive | A ResponseConfirm primitive shall be sent back to the issuer. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.18 Identify the managed remote entity and the management protocol | The hosting SCL shall identify the remote entity to be managed via the <scl> resource in the URI path as provided in the targetID primitive attribute. Then the hosting SCL shall determine the management protocol to be used for communicating with the remote entity based on the mgmtProtocolType attribute of the <scl> res... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.19 Locate the MO information to be managed on the remote entity | The hosting SCL shall locate the MO information to be managed on the remote entity by the originalMO attribute of the <mgmtObj> or <parameters> resource addressed by the URI provided in the targetID primitive attribute. In the case that the targetID addresses an <moAttribute> or a <parameters> resource without original... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.20 Establish a management session with the remote entity | If there is no existing management session between the hosting SCL and the remote entity to be managed, the hosting SCL shall also trigger the remote entity to establish a management session with the hosting SCL by sending triggering message to the address provided in the remTriggerAddr attribute of the parent resource... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.22 Identify the managed remote entity and the management protocol | After the hosting SCL (i.e. NSCL) establishes a management session with the remote entity, it shall enter into this step to convert the received mgmtCmd-related primitives to corresponding BBF TR-069 [49] RPC and shall send the converted RPC to the remote entity via the established management session. Management comman... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.2.23 SCL retargeting to an application | The SCL shall check if the following conditions apply: • the targetID does not identify a resource that is stored in the local SCL; and • the targetID in the received request is hierarchically subordinate to the <application> resource; and • the targetID does not correspond to an attribute in the <application> resource... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.3 Receiver SCL actions | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.3.3.1 Re-targeting | If the targetID in the request does not start with the sclBase URI of the receiver , the receiver SCL shall forward the request or shall serve the request locally (see below). If the targetID in the request starts with the sclBase URI of the receiver, then the receiver SCL shall handle the request locally. Acting as an... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.4 <sclBase> resource and management procedures | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.4.1 <sclBase> resource | The sclBase resource shall contain the following sub-resources and attributes. Table 10.6: Attributes and resource for the sclBase AttributeName Presence in createReq Presence in updateReq Presence in response Description sclsReference N/A NP M Reference to sub-resource "scls" in table 11.37 applicationsReference N/A N... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.4.2 sclBaseCreate | The <sclBase> resource shall not be created via the API. Instead the <sclBase> resource is created by out-of-band means (e.g. a service provider may have administrative commands to create an sclBase resource or the sclBase is created when the device or gateway is first started) . When the sclBase is created, all its ch... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.4.3 sclBaseRetrieve | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.4.3.1 sclBaseRetrieveRequestIndication | This primitive is used to retrieve an <sclBase> Resource. The SCL primitive shall comply with the following. Table 10.7: Applicability of the primitive Primitive applicability Applicable interfaces mIa dIa mId Issuer Application Application SCL Receiver Local SCL Local SCL Hosting SCL Table 10.8: Primitive sclBaseRetri... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.4.3.2 sclBaseRetrieveResponseConfirm (successful case) | Confirms the retrieval of an sclBase Resource. The SCL primitive shall comply with the following. Table 10.9: sclBaseRetrieveResponseConfirm, successful case SCL primitive: sclBaseRetrieveResponseConfirm Primitive attribute Mandatory/Optional Description primitiveType M Indicates the type of primitive: SCLBASE_RETRIEVE... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.4.3.3 sclBaseRetrieveResponseConfirm (unsuccessful case) | This response is triggered by an error in the sclBaseRetrieveRequestIndication procedure. The SCL primitive shall comply with table 10.10. Table 10.10: sclBaseRetrieveResponseConfirm, unsuccessful case SCL primitive: sclBaseRetrieveResponseConfirm Primitive attribute Mandatory/Optional Description primitiveType M SCLBA... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.4.4 sclBaseUpdate | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.4.4.1 sclBaseUpdateRequestIndication | This clause describes the full update of an sclBase resource. The SCL primitive shall comply with the following. Table 10.11: Applicability of the primitive Primitive applicability Applicable interfaces mIa dIa mId Issuer Application Application SCL Receiver Local SCL Local SCL Hosting SCL Table 10.12: Primitive sclBas... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.4.4.2 sclBaseUpdateResponseConfirm (successful case) | Confirms the update of an sclBase Resource. The SCL primitive shall comply with the following. Table 10.13: sclBaseUpdateResponseConfirm, successful case SCL primitive: sclBaseUpdateResponseConfirm Primitive attribute Mandatory/Optional Description primitiveType M SCLBASE_UDPATE_RESPONSE statusCode M STATUS_OK Resource... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.4.4.3 sclBaseUpdateResponseConfirm (unsuccessful case) | This response is triggered by the sclBaseRetrieveRequestIndication. The SCL primitive shall comply with table 10.14. Table 10.14: sclBaseUpdateResponseConfirm, unsuccessful case SCL primitive: sclBaseUpdateResponseConfirm Primitive attribute Mandatory/Optional Description primitiveType M SCLBASE_UPDATE_RESPONSE errorIn... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.4.5 sclBaseDelete | The <sclBase> resource shall not be deleted via the API. The receiver shall: 1) "Create an unsuccessful ResponseConfirm" with statusCode STATUS_METHOD_NOT_ALLOWED. 2) "Send ResponseConfirm primitive". ETSI ETSI TS 102 921 V1.3.1 (2014-09) 102 Instead the sclBase may be deleted via some out-of-band means. When the sclBa... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.5 scls resource and management procedures | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.5.1 scls resource | The scls resource shall contain the following sub-resources and attributes. Table 10.15: Attributes and primitive for scls AttributeName Presence in createReq Presence in updateReq Presence in response Description sclCollection N/A NP M References to sub-resources "<scl> in table 11.37 subscriptionsReference N/A NP M R... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.5.2 sclsCreate | The scls collection resource shall not be created directly via the API. It is created whenever the parent sclBase resource is created. The attributes are set to their default values as specified in table 10.15. The accessRightID is initialized to same value as the accessRightID in the parent. Note that since the sclBas... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.5.3 sclsRetrieve | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.5.3.1 sclsRetrieveRequestIndication | This primitive is used to retrieve an scls collection Resource. The SCL primitive shall comply with table 10.16. Table 10.16: Applicability of the primitive Primitive applicability Applicable interfaces mIa dIa mId Issuer Application Application SCL Receiver Local SCL Local SCL Hosting SCL ETSI ETSI TS 102 921 V1.3.1 (... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.5.3.2 sclsRetrieveResponseConfirm (successful case) | Confirms the retrieval of an sclBase Resource. The SCL primitive shall comply with table 10.18. Table 10.18: sclsRetrieveResponseConfirm, successful case SCL primitive: sclsRetrieveResponseConfirm Primitive attribute Mandatory/Optional Description primitiveType M SCLS_RETRIEVE_RESPONSE statusCode M STATUS_OK Resource M... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.5.3.3 sclsRetrieveResponseConfirm (unsuccessful case) | This response is triggered by the sclsRetrieveRequestIndication. The SCL primitive shall comply with table 10.19. Table 10.19: sclsRetrieveResponseConfirm, unsuccessful case SCL primitive: sclsRetrieveResponseConfirm Primitive attribute Mandatory/Optional Description primitiveType M SCLS_RETRIEVE_RESPONSE errorInfo M P... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.5.4 sclsUpdate | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.5.4.1 sclsUpdateRequestIndication | It updates the provided attributes of an existing collection resource in a Service Capability Layer. This primitive describes the full update. In addition to a full update, it is also possible to update a single attribute or part of an attribute. See clause 10.39.5 for details. The SCL primitive shall comply with table... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.5.4.2 sclsUpdateResponseConfirm (successful case) | Successful response on updating of an existing Collection resource in a Service Capability Layer. Table 10.22: sclsUpdateResponseConfirm, successful case SCL Primitive: sclsUpdateResponseConfirm Primitive attribute Mandatory/Optional Description primitiveType M Indicates the SCLS_UPDATE_RESPONSE statusCode M STATUS_OK ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.5.4.3 sclsUpdateResponseConfirm (unsuccessful case) | Unsuccessful response after an attempt to update an Collection resource in a Service Capability Layer. Table 10.23: sclsUpdateResponseConfirm, unsuccessful case SCL Primitive: sclsUpdateResponseConfirm Primitive attribute Mandatory/Optional Description primitiveType M SCSLS_UPDATE_RESPONSE errorInfo M Provides error in... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.5.5 sclsDelete | The scl collection resource shall not be deleted via the API. The receiver shall: 1) "Create an unsuccessful ResponseConfirm" with statusCode STATUS_METHOD_NOT_ALLOWED. 2) "Send ResponseConfirm primitive". ETSI ETSI TS 102 921 V1.3.1 (2014-09) 106 |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6 <scl> resource and management procedures | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6.1 <scl> resource | The structure of the <scl> resource depends on whether the resource is hosted by an NSCL or a D/GSCL. When hosted in an NSCL the <scl> resource shall contain the following sub-resources and attributes. Table 10.24: Resource description for <scl> (NSCL) AttributeNames Presence in createReq Presence in updateReq Presence... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6.2 sclCreate | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6.2.1 sclCreateRequestIndication | This procedure is used for creating an SCL resource of the Issuer-SCL at the Hosting-SCL. The primitive shall comply with table 10.25. The Hosting SCL shall use default values for optional parameters that are not specified. If the receiver supports integrity validation, the receiver shall have retrieved the security at... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6.2.2 sclCreateReponseConfirm(successful case) | This response is triggered by the sclCreateRequestIndication. The primitive shall comply with table 10.27. Optional parameters shall be returned in the response if hosting SCL over-wrote the settings that were specified in the request in order to bring the attributes in line with SCL policies. Table 10.27: sclCreateRes... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6.2.3 sclCreateReponseConfirm(unsuccessful case) | This response is triggered by the sclCreateRequestIndication. The SCL primitive shall comply with table 10.28. Optional parameters shall be returned in the response if hosting SCL over-wrote the settings that were specified in the request in order to bring the attributes in line with SCL policies. Table 10.28: sclCreat... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6.3 sclRetrieve | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6.3.1 sclRetrieveRequestIndication | This request is used for retrieving the content of an SCL resource. The SCL primitive shall comply with table 10.29. Table 10.29: Applicability of the primitive Primitive applicability Applicable interfaces mIa dIa mId Issuer Application Application SCL Receiver Hosting SCL Hosting SCL Hosting SCL ETSI ETSI TS 102 921 ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6.3.2 sclRetrieveResponseConfirm (successful case) | This response is triggered by the sclRetrieveRequestIndication. The SCL primitive shall comply with table 10.31. Table 10.31: sclRetrieveResponseConfirm, successful case SCL primitive: sclRetrieveResponseConfirm Primitive Attribute Mandatory/Optional Description primitiveType M SCL_RETREIVE_RESPONSE statusCode M STATUS... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6.3.3 sclRetrieveResponseConfirm (unsuccessful case) | This response is triggered by the sclRetrieveRequestIndication. The SCL primitive shall comply with table 10.32. Table 10.32: sclRetrieveResponseConfirm, unsuccessful case SCL primitive: sclRetrieveResponseConfirm Primitive Attribute Mandatory/Optional Description primitiveType M SCL_RETRIEVE_RESPONSE errorInfo M Provi... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6.4 sclUpdate | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6.4.1 sclUpdateRequestIndication | This request is part of the SCL Update procedure. This request is used for updating one or more SCL attributes. The SCL primitive shall comply with table 10.33. Table 10.33: Applicability of the primitive SCL Primitive: sclUpdateRequestIndication Applicable interfaces mIa dIa mId Issuer Application Application SCL Rece... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6.4.2 sclUpdateResponseConfirm (successful case) | This response is triggered by the sclUpdateRequestIndication. The SCL primitive shall comply with table 10.35. If the Hosting SCL did not accept the attribute values in the sclUpdateRequestIndication, then the attribute values that were used shall be included in the response. Table 10.35: sclUpdateResponseConfirm, succ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.6.4.3 sclUpdateResponseConfirm (unsuccessful case) | This response is triggered by the sclUpdateRequestIndication. The SCL primitive shall comply with table 10.36. If the SCL did not accept the attribute values in the SclUpdateRequestIndication , then the attribute values that were used shall be included in the response. Table 10.36: sclUpdateResponseConfirm, unsuccessfu... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.