hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.3.1 Resource SEReboot | The [SEReboot] resource shall be used to reboot a Secure Environment. The [SEReboot] resource is a specialization of the <mgmtObj> resource. The [SEReboot] resource shall contain the child resources specified in table 7.3.1-1. Table 7.3.1-1: Child resources of [SEReboot] resource Child Resources of [SEReboot] Child Res... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.4 Sensitive Data Storage | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.4.1 <sensitiveDataObject> resource | Secure Environments shall provide a service to store and protect sensitive data. Sensitive data objects are represented as SE-resources and are created and managed within the Secure Environment. Requests to SE-resources are using absolute addressing. A <sensitiveDataObject> resource shall represent sensitive data and r... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.4.2 <sensitiveDataObject> Resource Procedures | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.4.2.1 CREATE <sensitiveDataObject> | This procedure shall be used for creating a <sensitiveDataObject> resource. Table 7.4.2.1-1: <sensitiveDataObject> CREATE <sensitiveDataObject> CREATE request message parameters Associated Reference Point Mcs Information in Request message Following parameters shall exist within the Create request: Operation To: contai... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.4.2.2 RETRIEVE <sensitiveDataObject> | This procedure shall be used for retrieving a <sensitiveDataObject> resource. Table 7.4.2.2-1: <sensitiveDataObject> RETRIEVE <sensitiveDataObject> RETRIEVE request message parameters Associated Reference Point Mcs Information in Request message Following parameters shall exist within the RETRIEVE request: Operation To... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.4.2.3 UPDATE <sensitiveDataObject> | This procedure shall be used for updating the attributes and actual data of a <sensitiveDataObject> resource. Table 7.4.2.3-1: <sensitiveDataObject> UPDATE <sensitiveDataObject> UPDATE request message parameters Associated Reference Point Mcs Information in Request message Following parameters shall exist within the UP... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.4.2.4 DELETE <sensitiveDataObject> | This procedure shall be used for deleting a <sensitiveDataObject> resource. Table 7.4.2.4-1: <sensitiveDataObject> DELETE <sensitiveDataObject> DELETE request message parameters Associated Reference Point Mcs Information in Request message Following parameters shall exist within the DELETE request: Operation To: contai... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5 Sensitive Cryptographic Functions | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.1 <cipher> resource | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.1.0 Introduction | Secure Environments shall provide a service for cryptographic operations. A <cipher> resource shall represent sensitive data and related information owned by a creator. ETSI ETSI TS 118 116 V4.0.1 (2023-11) 22 oneM2M TS-0016 version 4.0.1 Release 4 The <cipher> resource shall contain the child resources specified in ta... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.1.1 <cipher> Resource Procedures | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.1.1.1 CREATE <cipher> | This procedure shall be used for creating a <cipher> resource. Table 7.5.1.1.1-1: <cipher> CREATE <cipher> CREATE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the specific details for: To: contains M2M-... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.1.1.2 RETRIEVE <cipher> | This procedure shall be used for retrieving the generated output from all/last input data of the <Cipher> resource. Table 7.5.1.1.2-1: <cipher> RETRIEVE <cipher> RETRIEVE request message parameters Associated Reference Point Mcs Information in Request message According to clause 10.1.2 of ETSI TS 118 101 [2] with the s... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.1.1.3 UPDATE <cipher> | This procedure shall be used for updating the <cipher> resource with data to encrypt or decrypt. It may be necessary to use this procedure several times until all data is transmitted. Table 7.5.1.1.3-1: <cipher> UPDATE <cipher> UPDATE request message parameters Associated Reference Point Mcs Information in Request mess... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.1.1.4 DELETE <cipher> | This procedure shall be used for deleting a <cipher> resource. Table 7.5.1.1.4-1: <cipher> DELETE <cipher> DELETE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the specific details for: To: contains M2M-... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.1.2 <encrypt> Resource | The <encrypt> resource is a virtual resource because it does not have a representation. It is the child resource of a <cipher> resource. When a RETRIEVE request addresses the <encrypt> resource, the sensitiveData of the <cipher> resource shall be encrypted and the result shall be stored in calculatedData. The <encrypt>... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.1.3 <decrypt> Resource | The <decrypt> resource is a virtual resource because it does not have a representation. It is the child resource of a <cipher> resource. When a RETRIEVE request addresses the <decrypt> resource, the sensitiveData of the <cipher> resource shall be decrypted and the result shall be stored in calculatedData. The <decrypt>... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.1.4 <generateKey> Resource | The <generateKey> resource is a virtual resource because it does not have a representation. When a RETRIEVE request addresses the <generateKey> resource, the keyData attribute shall be filled with a key generated according to the algorithm attribute. The <generateKey> resource inherits access control policies that appl... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.1.5 <algorithmSpecificParameter> Resource | The <algorithmSpecificParameter> contains parameter required for the different algorithm. The <algorithmSpecificParameter> resource shall inherit the same access control policies of the parent <cipher> resource, and shall not have its own accessControlPolicyIDs attribute. Attributes in <algorithmSpecificParameter> are ... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.2 <rand> resource | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.2.0 Introduction | A <rand> resource shall represent random data owned by a creator. The <rand> resource shall contain the child resources specified in table 7.5.2.0-1. Table 7.5.2.0-1: Child resources of <rand> resource Child Resources of <rand> Child Resource Type Multiplicity Description <randAnnc> Child Resource Types generateRand <g... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.2.1 <rand> Resource Procedures | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.2.1.1 CREATE <rand> | This procedure shall be used for creating a <rand> resource. Table 7.5.2.1.1-1: <rand> CREATE <rand> CREATE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the specific details for: To: contains M2M-SE-ID ... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.2.1.2 RETRIEVE <rand> | This procedure shall be used for retrieving the random numbers. Table 7.5.2.1.2-1: <rand> RETRIEVE <rand> RETRIEVE request message parameters Associated Reference Point Mcs Information in Request message According to clause 10.1.2 of ETSI TS 118 101 [2] with the specific details for To: contains M2M-SE-ID or SE hosted ... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.2.1.3 UPDATE <rand> | This procedure shall be used for setting the amount of random data which is requested. Table 7.5.2.1.3-1: <rand> UPDATE <rand> UPDATE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the specific details fo... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.2.1.4 DELETE <rand> | This procedure shall be used for deleting a <rand> resource. Table 7.5.2.1.4-1: <rand> DELETE <rand> DELETE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the specific details for: To: contains M2M-SE-ID ... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.2.2 <generateRand> Resource | The <generateRand> resource is a virtual resource because it does not have a representation. When a RETRIEVE request addresses the <generateRand> resource, the randomData attribute shall be filled with random numbers from a random number generator according to the rngType attribute. The <generateRand> resource inherits... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.3 <hash> resource | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.3.0 Introduction | Secure Environments shall provide a service for calculating hashes. A <hash> resource shall represent sensitive data and related information owned by a creator. ETSI ETSI TS 118 116 V4.0.1 (2023-11) 30 oneM2M TS-0016 version 4.0.1 Release 4 The <hash> resource shall contain the child resources specified in table 7.5.3.... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.3.1 <hash> Resource Procedures | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.3.1.1 CREATE <hash> | This procedure shall be used for creating a <hash> resource. Table 7.5.3.1.1-1: <hash> CREATE <hash> CREATE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the specific details for: To: contains M2M-SE-ID ... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.3.1.2 RETRIEVE <hash> | This procedure shall be used for retrieving the calculated hash. Table 7.5.3.1.2-1: <hash> RETRIEVE <hash> RETRIEVE request message parameters Associated Reference Point Mcs Information in Request message According to clause 10.1.2 of ETSI TS 118 101 [2] with the specific details for: To: contains M2M-SE-ID or SE hoste... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.3.1.3 UPDATE <hash> | This procedure shall be used for updating the <hash> resource with data to be hashed. Table 7.5.3.1.3-1: <hash> UPDATE <hash> UPDATE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the specific details for... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.3.1.4 DELETE <hash> | This procedure shall be used for deleting a <hash> resource. Table 7.5.3.1.4-1: <hash> DELETE <hash> DELETE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the specific details for: To: contains M2M-SE-ID ... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.3.2 <calculateHash> Resource | The <calculateHash> resource is a virtual resource because it does not have a representation. When a RETRIEVE request addresses the <calculateHash> resource, the hashValue attribute shall be filled with the hash calculated over the data in the message attribute according to the algorithm attribute. The <calculateHash> ... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.4 <signature> resource | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.4.0 Introduction | Secure Environments shall provide a service for signing messages and verifying signatures. A <signature> resource shall represent sensitive data and related information owned by a creator. The <signature> resource shall contain the child resources specified in table 7.5.4.0-1. Table 7.5.4.0-1: Child resources of <signa... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.4.1 <signature> Resource Procedures | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.4.1.1 CREATE <signature> | This procedure shall be used for creating a <signature> resource. Table 7.5.4.1.1-1: <signature> CREATE <Signature> CREATE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the specific details for: To: cont... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.4.1.2 RETRIEVE <signature> | This procedure shall be used for retrieving either the calculated signature of the <Signature> resource or the result of the verification of a signature. Table 7.5.4.1.2-1: <signature> RETRIEVE <signature> RETRIEVE request message parameters Associated Reference Point Mcs Information in Request message According to cla... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.4.1.3 UPDATE <signature> | This procedure shall be used for updating the <signature> resource with the message to be signed or to be verified and in the case of verification the signature to be verified. Table 7.5.4.1.3-1: <signature> UPDATE <signature> UPDATE request message parameters Associated Reference Point Mcs Information in Request messa... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.4.1.4 DELETE <signature> | This procedure shall be used for deleting a <signature> resource. Table 7.5.4.1.4-1: <signature> DELETE <signature> DELETE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the specific details for: To: cont... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.4.2 <calculateSignature> Resource | The <calculateSignature> resource is a virtual resource because it does not have a representation. It is the child resource of a <signature> resource. When a RETRIEVE request addresses the <calculateSignature> resource, the signature shall be calculated and written in the signature attribute of the <signature> resource... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.4.3 <verifySignature> Resource | The <verifySignature> resource is a virtual resource because it does not have a representation. It is the child resource of a <signature> resource. When a RETRIEVE request addresses the <verifySignature> resource, signature attribute of the <signature> resource shall be verified and the result shall be stored in verifi... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.5.4.4 <generateKey> Resource | The <generateKey> resource is a virtual resource because it does not have a representation. When a RETRIEVE request addresses the <generateKey> resource, the keyData attribute shall be filled with a key generated according the algorithm attribute. The <generateKey> resource inherits access control policies that apply t... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6 Secure Connection Establishment | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.1 <secureConnection> resource | Secure Environments shall provide a service to AEs or CSEs to establish a secure connection to a dedicated communication partner. The <secureConnection> resource shall represent the services offered by the Secure Environment to enable the establishment of a secure connection to a communication partner. The services inc... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.2 <secureConnection> Resource Procedures | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.2.1 CREATE <secureConnection> | This procedure shall be used for creating a <secureConnection> resource. Table 7.6.2.1-1: <secureConnection> CREATE <secure Connection> CREATE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the specific d... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.2.2 RETRIEVE <secureConnection> | This procedure shall be used for retrieving information about the <secureConnection> resource. Table 7.6.2.2-1: <secureConnection> RETRIEVE <secureConnection> RETRIEVE request message parameters Associated Reference Point Mcs Information in Request message According to clause 10.1.2 of ETSI TS 118 101 [2] with the spec... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.2.3 UPDATE <secureConnection> | This procedure shall be used for sending payload data via an established secure connection. Table 7.6.2.3-1: <secureConnection> UPDATE <secureConnection> UPDATE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply w... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.2.4 DELETE <secureConnection> | This procedure shall be used for deleting a <secureConnection> resource. Deleting a <secureConnection> resource shall close an established secure connection between the originator (creator) and the destination. Table 7.6.2.4-1: <secureConnection> DELETE <secureConnection> DELETE request message parameters Associated Re... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.3 <connectionInstance> resource | The <connectionInstance> resource represents a data instance in the <secureConnection> resource. The <connectionInstance> resource inherits the same access control policies of the parent <secureConnection> resource, and does not have its own accessControlPolicyIDs attribute. The services shall include the following: • ... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.4 <connectionInstance> Resource Procedures | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.4.1 CREATE <connectionInstance> | This procedure shall be used for creating a <connectionInstance> resource. Table 7.6.4.1-1: <connectionInstance> CREATE <connectionInstance> CREATE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the speci... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.4.2 RETRIEVE <connectionInstance> | This procedure shall be used for retrieving payload data from a communication partner or to retrieve the negotiated key. Table 7.6.4.2-1: <connectionInstance> RETRIEVE <connectionInstance> RETRIEVE request message parameters Associated Reference Point Mcs Information in Request message According to clause 10.1.2 of ETS... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.4.3 UPDATE <connectionInstance> | This procedure shall be used for sending payload data via an established secure connection. Table 7.6.4.3-1: <connectionInstance> UPDATE <connectionInstance> UPDATE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] app... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.4.4 DELETE <connectionInstance> | This procedure shall be used for deleting a <connectionInstance> resource. Deleting a <connectionInstance> resource closes an established secure connection between the originator (creator) and the destination. Table 7.6.4.4-1: <connectionInstance> DELETE <connectionInstance> DELETE request message parameters Associated... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.5 <connect> Resource | The <connect> resource is a virtual resource because it does not have a representation. When a RETRIEVE request addresses the <connect> resource, a connection shall be established to the destination URI. If <negotiatedKey> exists the negotiated key shall be stored in this attribute. The <connect> resource inherits acce... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.6 <send> Resource | The <send> resource is a virtual resource because it does not have a representation. When a RETRIEVE request addresses the <send> resource, the value of outgoingPayloadData shall be sent to the destination URI. The <send> resource inherits access control policies that apply to the parent resource. |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.6.7 <generateKey> Resource | The <generateKey> resource is a virtual resource because it does not have a representation. When a RETRIEVE request addresses the <generateKey> resource, the keyData attribute shall be filled with a key generated according the algorithm attribute. The <generateKey> resource inherits access control policies that apply t... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.7 Authentication and Identification | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.7.1 <identity> resource | Secure Environments shall provide a service to AEs or CSEs to establish an Identity and provide authentication of this Identity. The <identity> resource shall represent the services offered by the Secure Environment to enable the establishment of a secure Identity. The services include the following: • generation of an... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.7.2 <identity> Resource Procedures | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.7.2.1 CREATE <identity> | This procedure shall be used for creating a <identity> resource. Table 7.7.2.1-1: <identity> CREATE <identity> CREATE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the specific details for: To: contains ... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.7.2.2 RETRIEVE <identity> | This procedure shall be used for retrieving the identity and retrieve authentication data according the used authentication protocol. Table 7.7.2.2-1: <identity> RETRIEVE <identity> RETRIEVE request message parameters Associated Reference Point Mcs Information in Request message According to clause 10.1.2 of ETSI TS 11... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.7.2.3 UPDATE <identity> | This procedure shall be used for updating the <identity resource> and sending authentication data according the used authentication protocol. Table 7.7.2.3-1: <identity> UPDATE <identity> UPDATE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.7.2.4 DELETE <identity> | This procedure shall be used for deleting an <identity> resource. Table 7.7.2.4-1: <identity> DELETE <Identity> DELETE request message parameters Associated Reference Point Mcs Information in Request message All parameters defined in table 8.1.2-3 of ETSI TS 118 101 [2] apply with the specific details for: To: contains... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.7.3 <authenticate> Resource | The <authenticate> resource is a virtual resource because it does not have a representation. It is the child resource of an <identity> resource. When a RETRIEVE request addresses the <authenticate> resource, the originatorAuthenticationData, keyData and idData shall be used to calculate a value which shall be stored in... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 7.7.4 <generateKey> Resource | The <generateKey> resource is a virtual resource because it does not have a representation. When a RETRIEVE request addresses the <generateKey> resource, the keyData attribute shall be filled with a key generated according the algorithm attribute. ETSI ETSI TS 118 116 V4.0.1 (2023-11) 47 oneM2M TS-0016 version 4.0.1 Re... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 8 Physical Interface | The present release does not specify how the Mcs reference point can be bound to physical interfaces used by specific Secure Environments. Organizations specifying technologies applicable for Secure Environments, such as GlobalPlatform, specify bindings that can be applicable. |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 9 Resource type definitions for the Mcs reference point | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 9.1 Mcs specific enumeration values of m2m:resourceType | The following values are defined specifically for the Mcs interface, as an extension to applicable values inherited from ETSI TS 118 104 [14]. Table 9.1-1: Mcs enumeration values Value Resource type 20001 algorithmSpecificParameter 20002 cipher 20003 connectionInstance 20004 hash 20005 identity 20007 rand 20008 secureC... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 9.2 senv:SEType | The values in table 9.2-1 are defined as per table 7.2.1-2. Table 9.2-1: SEType defined values Value Meaning 1 UICC as per ETSI 2 GlobalPlatform Secure Element 3 TEE as per GlobalPlatform 4 Software cryptographic library |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 9.3 senv:securityLevel | The values in table 9.3-1 are defined as per clause 6.2. Table 9.3-1: securityLevel defined values Value Meaning 1 Low security 2 Medium security 3 High security ETSI ETSI TS 118 116 V4.0.1 (2023-11) 48 oneM2M TS-0016 version 4.0.1 Release 4 |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 9.4 senv:rebootType | The values in table 9.4-1 are defined. Table 9.4-1: rebootType defined values Value Meaning 1 Cold Reset as defined in ISO/IEC 7816-3 [7] 2 Warm Reset as defined in ISO/IEC 7816-3 [7] |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 9.5 senv:cipherLabel | The values in table 9.5-1 are defined. Table 9.5-1: cipherLabel defined values Value Meaning 1 EXPORTER-oneM2M-Bootstrap 2 EXPORTER-oneM2M-Connection |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 9.6 senv:cipherAlgorithm | The values in table 9.6-1 are defined. Table 9.6-1: cipherAlgorithm defined values Value Meaning 1001 ALG_AEAD_AES_128_GCM 1002 ALG_AEAD_AES_256_GCM 1003 ALG_AEAD_AES_128_CCM 1004 ALG_AEAD_AES_256_CCM 1018 ALG_AEAD_AES_128_CCM_8 1019 ALG_AEAD_AES_256_CCM_8 13 ALG_AES_BLOCK_128_CBC_NOPAD 22 ALG_AES_CBC_ISO9797_M1 23 ALG... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 9.7 senv:rngType | The values in table 9.7-1 are defined. Table 9.7-1: rngType defined values Value Meaning 1 Pseudo RNG 2 True (physical) RNG |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 9.8 senv:hashAlgorithm | The values in table 9.8-1 are defined. ETSI ETSI TS 118 116 V4.0.1 (2023-11) 49 oneM2M TS-0016 version 4.0.1 Release 4 Table 9.8-1: hashAlgorithm defined values Value Meaning 4 SHA256 5 SHA384 6 SHA512 NOTE: These values were taken from the JavaCard API. |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 9.9 senv:signatureAlgorithm | The values in table 9.9-1 are defined. Table 9.9-1: signatureAlgorithm defined values Value Meaning 49 ALG_AES_CMAC_128 18 ALG_AES_MAC_128_NOPAD 33 ALG_ECDSA_SHA_256 34 ALG_ECDSA_SHA_384 38 ALG_ECDSA_SHA_512 25 ALG_HMAC_SHA_256 26 ALG_HMAC_SHA_384 27 ALG_HMAC_SHA_512 NOTE: These values were taken from the JavaCard API. |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 9.10 senv:connectionTypeID | The values in table 9.10-1 are defined. Table 9.10-1: connectionTypeID defined values Value Meaning 1 TLS 2 DTLS 3 SMS 4 E2EKey |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 10 Short Name definitions for the Mcs reference point | |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 10.1 Short Names for Mcs specific resource attributes | The mapping between the full names and their shortened form is given in the following clauses. These names are case-sensitive. A oneM2M implementation shall use the letter casing given in these clauses. In protocol bindings, resource attributes names shall be translated into short names shown in table 10.1-1. All attri... |
fca3cac42b688b0e5246c551f4c213c2 | 118 116 | 10.2 Short Names for Mcs specific resource types | In protocol bindings resource type names shall be translated into short names of table 10.2-1. ETSI ETSI TS 118 116 V4.0.1 (2023-11) 51 oneM2M TS-0016 version 4.0.1 Release 4 Table 10.2-1: Mcs Resource type short names Resource Type Name Short Name SE Senv SEReboot Srbt sensitiveDataObject Sdo cipher Cph encrypt Enc de... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 1 Scope | The present document specifies a testing framework defining a methodology for development of conformance and interoperability test strategies, test systems and the resulting test specifications for oneM2M standards. |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 2 References | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 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... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 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... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 3 Definitions and abbreviations | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: conformance: compliance with requirements specified in applicable standards ISO/IEC 9646 [i.2] ETSI ETSI TS 118 115 V2.0.0 (2016-09) 7 (oneM2M TS-0015 version 2.0.0 Release 2) conformance testing: process for testing that an implementa... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 3.2 Abbreviations | For the purposes of the present document, the terms and definitions given in ETSI TS 118 001 [1] and the following apply: API Application Programming Interface APT Abstract Protocol Tester ATS Abstract Test Suite BI Invalid Behaviour BO Inopportune Behaviour BV Valid Behaviour CoAP Constrained Application Protocol EUT ... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 4 Conventions | The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 5 Introduction to the oneM2M testing methodology | The present document provides: • Identification of the implementations under test (IUT) for conformance testing and the device under test (DUTs) for interoperability, i.e. answering the question "what is to be tested". • Definition of the applicable test procedures, i.e. answering the question "how is it to be tested".... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6 Conformance testing | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.1 Introduction | The clause 6 shows how to apply the oneM2M conformance testing methodology in order to properly produce oneM2M conformance test specifications. The Conformance testing can show that a product correctly implements a particular standardized protocol, that is, it establishes whether or not the implementation under test me... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.2 Test architecture | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.2.1 Selection of Implementation Under Test | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.2.1.1 Definition | The "Implementation Under Test" (IUT) is a protocol implementation considered as an object for testing. This means that the test process will focus on verifying the compliance of this protocol implementation (IUT) with requirements set up in the related base standard. An IUT normally is implemented in a "System Under T... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.