hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.1.1.2 Credential Configuration of M2M Authentication Functions | Table 9.1.1.2-1 lists the parameters configured to M2M Authentication Functions in the Credential Configuration phase. The M2M Authentication Function's identifier (MAF-ID) is presumed to have been configured prior to the Credential Configuration phase. Table 9.1.1.2-1: Parameters configured to a M2M Authentication Fun... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.1.2 Association Configuration Procedures and Parameters | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.1.2.0 Introduction | The following Association Configuration procedures are described in this clause: • Association Configuration of Entity A, see clause 9.1.2.1.1. • Association Configuration of Entity B, see clause 9.1.2.1.2. • Association Configuration of M2M Authentication Functions, see clause 9.1.2.2. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.1.2.1 Association Configuration of Entity A and Entity B | 9.1.2.1.1 Association Configuration of Entity A Table 9.1.2.1.1-1 lists the parameters configured to Entity A in the Association Configuration phase and which are common to all Security Association Establishment Frameworks. Table 9.1.2.1.1-1: Parameters configured to Entity A during the Association Configuration phase ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.1.2.1.2 Association Configuration of Entity B | Table 9.1.2.1.2-1 lists the parameters configured to the Registrar (Entity B) in the Association Configuration phase. Table 9.1.2.1.2-1: Parameters configured to Entity B during the Association Configuration phase Security Association Establishment Framework Parameters specific to the Security Association Establishment... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.1.2.2 Association Configuration of M2M Authentication Functions | Table 9.1.2.2-1 lists the parameters configured to M2M Authentication Functions in the Association Configuration phase. Table 9.1.2.2-1: Parameters configured to a M2M Authentication Functions during the Association Configuration phase Security Association Establishment Framework Parameter MAF-Based A-to-MAF Authentica... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.2.1 Bootstrap Credential Configuration Procedures and Parameters | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.2.1.0 Introduction | The following Bootstrap Credential Configuration procedures are described in this clause: • Bootstrap Credential Configuration of Enrolees and Enrolment Targets (except for the GBA-Based case as discussed below), see clause 9.2.1.1. • Bootstrap Credential Configuration of M2M Enrolment Functions (except for the GBA-Bas... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.2.1.1 Bootstrap Credential Configuration of Enrolee | Table 9.2.1.1-1 lists the parameters configured to Enrolees in the Bootstrap Credential Configuration phase for authentication with the M2M Enrolment Function in the Pre-Provisioned Symmetric Enrolee Key Remote Security Provisioning Framework and Certificate-Based Remote Security Provisioning Framework. Table 9.2.1.1-1... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.2.1.2 Bootstrap Credential Configuration of M2M Enrolment Functions | It is assumed that an M2M Enrolment Function already knows its FQDN. Table 9.2.1.2-1 lists the parameters configured to M2M Enrolment Functions in the Bootstrap Credential Configuration phase for mutual authentication with Enrolees and Enrolment Targets using the Pre-Provisioned Symmetric Enrolee Key Remote Security Pr... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.2.2 Bootstrap Instruction Configuration Procedures and Parameters | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.2.2.0 Introduction | The following Bootstrap Instruction Configuration procedures are described in this clause: • Bootstrap Instruction Configuration of Enrolees, see clause 9.2.2.1. • Bootstrap Instruction Configuration of M2M Enrolment Functions, see clause 9.2.2.3. • Bootstrap Instruction Configuration of Underlying Network Service Prov... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.2.2.1 Bootstrap Instruction Configuration of Enrolees | Table 9.2.2.1-1 lists the parameters configured to an Enrolee during the Bootstrap Instruction Configuration phase which are common to all Remote Security Provisioning Frameworks. Table 9.2.2.1-1: Parameters configured to an Enrolee during the Bootstrap Instruction Configuration phase of which are common to all Remote ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.2.2.2 Void | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.2.2.3 Bootstrap Instruction Configuration of M2M Enrolment Functions | Table 9.2.2.3-1 lists the parameters configured to an M2M Enrolment Function during the Bootstrap Instruction Configuration phase which are common to the Pre-Provisioned Symmetric Enrolee Key Remote Security Provisioning Framework and Certificate-Based Remote Security Provisioning Framework. ETSI ETSI TS 118 103 V4.7.1... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.2.2.4 Bootstrap Instruction Configuration of UNSP Authentication Server | Table 9.2.2.4-1 lists the parameters configured to an Underlying Network Service Provider authentication server (e.g. HLR, HSS or AAA) during the Bootstrap Instruction Configuration phase of the GBA-Based Remote Security Provisioning Framework. Table 9.2.2.4-1: Parameters configured to M2M Enrolment Functions during th... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.2.3 End-to-End Credential Configuration Procedures and Parameters | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.2.3.0 Introduction | The following End-to-End Credential Configuration procedures are described in this clause: • End-to-End Credential Configuration of Source ESF End-Points and Target ESF End-Points, see clause 9.2.3.1. ETSI ETSI TS 118 103 V4.7.1 (2026-03) 196 oneM2M TS-0003 version 4.7.1 Release 4 • End-to-End Credential Configuration ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 9.2.3.2 End-to-End Credential Configuration at the M2M Trust Enabling Functions | It is assumed that the Trust Enabling Function is configured with the identities of the entities (ESF Source and Target End-Points) and appropriate parameters specific to the Remote Security Provisioning Frameworks as described in clause 9.2. ETSI ETSI TS 118 103 V4.7.1 (2026-03) 197 oneM2M TS-0003 version 4.7.1 Releas... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10 Protocol and Algorithm Details | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1 Certificate-Based Security Framework Details | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.1 Certificate Profiles | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.1.0 General | NOTE: These certificate profiles are compliant with the CoAP specification IETF RFC 7252 [i.21]. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.1.1 Common Certificate Details | All certificates shall conform to the following profile: • Certificates shall conform to IETF RFC 5280 [34]. • The certificate shall include a SubjectPublicKeyInfo that indicates an algorithm of id-ecPublicKey with namedCurves secp256r1 [34]; this curve is equivalent to the NIST P-256 curve [39]. • The public key forma... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.1.2 Raw Public Key Certificate Profile | Raw public key certificates shall conform to clause 10.1.1.1 and IETF RFC 7250 [37]. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.1.3 Details Common to Certificates with Certificate Chains | Certificates with Certificate Chains shall conform to the following description: • These certificates shall conform to clause 10.1.1.1. • Certificates shall be signed with ECDSA using secp256r1 or optionally RSA using at least 2048 key length, and the signature shall use SHA-256. • Certificate chains should limit the n... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.1.4 Profile for Device Certificates and their Certificate Chains | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.1.4.1 Profile for Device Certificates | Device certificates shall conform to the following description: • Device certificates shall conform to clause 10.1.1.3. • The subjectAltName extension of device certificates shall include one or more globally unique hardware instance identifiers. EXAMPLE: Annex H "Object Identifier Based M2M Device Identifier" ETSI TS ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.1.4.2 Profile for Certificate Authority Certificates for Device Certificates | Certificate Authority Certificates in the certificate chain for a device certificate shall conform to the following description: • These certificates shall conform to clause 10.1.1.3. • Certificate Authority Certificates for device certificates are recommended to use the name constraints extension (see clause 4.2.1.10 ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.1.5 Profile for AE-ID Certificates and their Certificate Chains | AE-ID certificates and all other certificates in the corresponding certificate chain shall conform to clause 10.1.1.3. ETSI ETSI TS 118 103 V4.7.1 (2026-03) 200 oneM2M TS-0003 version 4.7.1 Release 4 The full URI representation of the AE-ID shall be included in the subjectAltName extension. The certificate used to sign... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.1.6 Profile for FQDN Certificates and their Certificate Chains | FQDN Certificates and all other certificates in the corresponding certificate chain shall conform to clause 10.1.1.3. An FQDN Certificate shall include the FQDN of the subject M2M Enrolment Function in the subjectAltName extension. FQDN Certificates shall not include wildcards. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.1.7 Profile for CSE-ID Certificates and their Certificate Chains | CSE-ID certificates and all other certificates in the corresponding certificate chain shall conform to clause 10.1.1.3. The subjectAltName extension shall include the public domain name representation of the CSE-ID as defined in ETSI TS 118 101 [1]. CSE-ID certificates shall not include wildcards. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.1.8 Profile for Node-ID Certificates and their Certificate Chains | Node-ID certificates and all other certificates in the corresponding certificate chain shall conform to clause 10.1.1.3. The subjectAltName extension shall include the Node-ID as defined in ETSI TS 118 101 [1]. Node-ID certificates shall not include wildcards. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.2 Public Key Identifiers | The public key identifier for a raw public key certificate shall calculated as described in section 2 of IETF RFC 6920 [40] using the SHA-256 hash algorithm. The public key identifier shall be generated using one of the sha-256-120, sha-256-128 or sha-256 hash algorithms specified in IETF RFC 6920 [40]. It is recommend... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.3 Support Requirements for each Public Key Certificate Flavour | Table 10.1.3-1 lists, for each of the various types of entity (Field Domain CSE, Field Domain AE, IN-CSE, IN-AE, M2M Authentication Function and M2M Enrolment Function), the flavour of certificate that may be issued to the entity and the flavour of other entity's certificates that the entity is required to be able to p... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.1.4 Certificate Signing Request Profile | A Certificate Signing Request (CSR) is a signed object provided to the Certificate Provisioning server (EST Server or SCEP Server) to request the issuing of a certificate. Certificate Provisioning as specified in clause 8.3.6 may be used to issue a certificate to an Node, CSE or AE. The certificate signing request shal... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.2 TLS and DTLS Details | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.2.1 TLS and DTLS Versions | Where TCP payloads are to be secured, TLS v1.2 [5] shall be used. Where UDP payloads are to be secured, DTLS v1.2 [6] shall be used, noting that the DTLS v1.2 ciphersuites are identical to the TLS v1.2 ciphersuites. All implementations shall support the Server Name Indication (SNI) to indicate their authority in the SN... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.3 Key Export and Key Derivation Details | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.3.1 TLS Key Export Details | TLS Key Export Details for Enrolment Key Following successful TLS authentication between the Enrolee and M2M Enrolment Function, see clause 8.3.1.2, the Enrolment Key (Ke) and RelativeKeID are generated from the (D)TLS session secrets by the Enrolee and M2M Enrolment Function by applying TLS Key Export (IETF RFC 5705 [... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.3.2 Derivation of Master Credential from Enrolment Key | This clause describes the details when generating a Master Credential (Km) from an Enrolment Key (Ke) in Security Bootstrap Frameworks. The following information shall be used when generating Km from Ke: • the value of the Enrolment Key (Ke); • the M2M Authentication Function Identifier (MAF-ID) shall be encoded to an ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.3.4 Generating KeID | The KeID value shall be formed as: • KeID = hexBinary(RelativeKeID)@MEF-FQDN: where: • hexBinary(RelativeKeID) denotes the hexadecimal representation of the binary value of RelativeKeID; and • MEF-FQDN denotes the FQDN of the M2M Enrolment Function. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.3.5 Generating Key Identifier for the MAF Security Framework | The Key Identifier value shall be formed as: • Key Identifier = RelativeKeyID@MAF-FQDN; where: • RelativeKeyID = hexBinary(KcID) denotes the hexadecimal representation of the binary value of KcID; and • MAF-FQDN denotes the FQDN of the M2M Authentication Function. 10.3.6 Derivation of End-to-End Master Key from Provisi... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.3.6.1 Introduction | This clause describes the details when generating an End-to-End Master Key (Ke2e_master) based on a successful establishment of security association between a Source ESF End-Point and Target ESF End-Point using a Remote Security Provisioning Framework as described in clause 8.3. The mechanisms to generate the End-to-En... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.3.6.2 Key Extraction and Expansion of End-to-End Master Key | The End-to-End Master Key (Ke2e_master) is used to generate the security protection-specific keys. The Key Extraction and Expansion parameters along with the scope are used to generate the various keys. The Key extraction and expansion is performed according to the specifications defined in IETF RFC 5869 [48]. A list o... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.3.8 sessionESPrimKey Derivation Algorithms | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.3.8.1 Introduction | The sessionESPrimKey is used in End-to-End Security of Primitives (ESPrim), and derived from pairwiseESPrimKey, receiverESPrimRandObject, originatorESPrimRandObject, see clause 8.4.2. Clause 10.3.8 specifies the algorithms used for derivation of the sessionESPrimKey used in ESPrim. The available algorithms are listed i... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.3.8.2 HMAC-SHA256 sessionESPrimKey Derivation Algorithm | The sessionESPrimkey is derived as sessionESPrimKey = HMAC-SHA256 (pairwiseESPrimKey, receiverESPrimRandObject || originatorESPrimRandObject || "oneM2M HMAC-SHA256 sessionESPrimKey derivation algorithm"), where HMAC-SHA-256 is defined in IETF RFC 2104 [33]. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.4 Credential-ID Details | The Credential-ID has two parts: • A type-ID part. The type-ID part is a positive integer defined by datatype sec:credIDTypeID. • A value part which contains a globally-unique identifier for the entity's credential. The value part may use the Roman alphabet, numerals, '.', '_', '-', and '@'. The Credential-ID is formed... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.5 KpsaID | The KpsaID shall be of the form: • KpsaID = Issuer_Relative_KpsaID@Issuer-FQDN; where: • Issuer_Relative_KpsaID is composed of the Roman alphabet, numerals, '.', '_' and '-' characters. The issuer of KpsaID shall ensure that no two Kpsa have identical Issuer_Relative_KpsaID. • Issuer-FQDN is an FQDN representing the st... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.6 KmID Format | The KmID shall be of the form: • KmID = MAF_RELATIVE_KmID@MAF-FQDN; ETSI ETSI TS 118 103 V4.7.1 (2026-03) 207 oneM2M TS-0003 version 4.7.1 Release 4 where: • MAF_RELATIVE_KmID is composed of the Roman alphabet, numerals, '.', '_' and '-' characters. The MAF_RELATIVE_KmID is not case sensitive. The MAF shall ensure that... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 10.7 Enrolment Expiry | Enrolment Expiry is the life time to be applied for the key generated, i.e. Ke as part of the Pre-Provisioned Symmetric Key Remote Security Provisioning. Keys that are generated for establishing security associations between Enrolees and the Enrolment Targets (i.e. Km or Kpsa) based upon the enrolment key Ke will not b... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.1 Introduction | This clause provides an architecture for the Privacy Policy Manager (PPM). PPM is a distributed authorization privacy protection architecture using M2M Service Subscriber's privacy preference and service's privacy policy. The PPM is a personal data management framework based on the M2M Service Subscriber's privacy pref... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.2 Components of PPM | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.2.1 Privacy Preference and Privacy Policy | The PPM shall manage privacy preferences and privacy policies. • Privacy preference: - Privacy preference is M2M Service Subscriber's preference regarding the provision of his own personal data to third parties. - M2M Service Subscriber creates a M2M Service Subscriber's privacy preference and registers it to the PPM. ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.2.2 Functions of PPM | The PPM may comprise the following functions. • Sophisticated consent mechanism for matching a M2M Service Subscriber's privacy preference with the ASP's privacy policy: - Privacy policy describes required personal data to provide a service to a M2M Service Subscriber by a M2M Service Provider. - When the M2M Service S... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3 Privacy Policy Management Architecture | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3.1 Introduction | The PPM manages M2M Service Subscriber's preference and service's privacy policy of an M2M Application Service Provider. Basically, one M2M Application Service Provider have one PPM in infrastructure domain and manage status of M2M Service Subscriber consent in the PPM. There are four procedures in the use of the PPM. ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3.2 Involved Entities | • M2M Service Subscriber: - An M2M Service Subscriber can make use of M2M services by subscribing to a service of an ASP which provides functions that control access to information handled by the M2M Service Provider. - When an M2M Service Subscriber subscribes to service provided by an ASP, the M2M Service Subscriber ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3.3 Management Flow in PPM Architecture | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3.3.0 Introduction | This clause describes the case where a M2M Service Provider stores personal data. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3.3.1 Subscribe to a M2M Service Provider | When a M2M Service Subscriber subscribes to a M2M Service Provider, the M2M Service Subscriber configures privacy preferences using the PPM. A privacy preference / policy explains what data is intended to be used by ASPs and allowed by consent to be shared with other service subscribers. Figure 11.3.3.1-1 illustrates t... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3.3.2 Subscription to a service by ASP | The M2M Service Subscriber can subscribe to various kinds of services provided by ASPs through the M2M Service Provider. Service lists are registered on an M2M portal and the M2M Service Subscriber can select services to subscribe to. When the M2M Service Subscriber subscribes to a service, the M2M Service Subscriber n... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3.3.3 Request for personal data to the Hosting CSE | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3.3.3.1 Implementation options | When the ASP collects personal data to provide the service, it requests the personal data from a Hosting CSE in the M2M Service Provider's domain. Access to the personal data is controlled by the PPM which may work either as PDP, PRP or DAS Server as detailed below: • If the PPM works as PDP, the Hosting CSE acts as PE... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3.3.3.2 Option 1: PPM works as PDP | For this option, the PPM shall be implemented as CSE and shall provide an interface that enables access control for personal data using the PPM as PDP. AE Hosting CSE M2M Service Provider ASP’s application CSE Access Control Policies Privacy Policy Manager PDP PEP Personal Data (1)Request Personal Data (2)Request <auth... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3.3.3.3 Option 2: PPM works as PRP | For this option, the PPM shall be implemented as CSE and shall provide an interface that enables access control for personal data using the PPM as PRP. AE Hosting CSE M2M Service Provider ASP’s application CSE Access Control Policies Privacy Policy Manager PRP PEP Personal Data (1)Request Personal Data (2)Request <auth... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3.3.3.4 Option 3: PPM works as DAS Server | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3.3.3.4.1 Option 3.1: Direct Dynamic Authorization | For this option, the PPM shall be implemented as AE and shall provide an interface that enables access control for personal data using the PPM as DAS Server. AE Hosting CSE ASP’s application IN-AE Access Control Policies Privacy Policy Manager Personal Data (1)Request Personal Data (2)Request <dynamicACPInfo> or <token... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.3.3.3.4.2 Option 3.2: Indirect Dynamic Authorization | For this option, the PPM shall be implemented as AE and shall provide an interface that enables access control for personal data using the PPM as DAS Server. In this clause, some optional procedures of indirect dynamic authorization are omitted and focused on procedures related to the PPM. ETSI ETSI TS 118 103 V4.7.1 (... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.4 Privacy Policy Manager Implementation Models | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.4.1 Using Terms and Conditions Mark-up Language | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.4.1.0 Introduction | Provider 2 T&C Provider n T&C Application/Device 1 to n Descriptors Application/Device 1 to n Provider 1 T&C Application/Device 1 to n User #1 Preferences Application/Device 1 to n Legal 1 e.g. City Application/Device 1 to n Legal 2 e.g. State Application/Device 1 to n Legal 3 e.g. country Application/Device 1 to n Oth... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.4.1.1 Registration of Application Service Provider Privacy Policy | 1) Optional registration of an applications Privacy Policy shall be part of the process of obtaining a Registered App-ID for each application and version and presenting a security certificate to the oneM2M Registration Authority that is used to authenticate the application and version. 2) The ASP shall download an appl... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.4.1.2 Registration of End User Privacy Preferences | 1) When an end user subscribes to a service provided by an application service provider, the end user becomes a data subject, and the data subject downloads or views the end user privacy preferences template from the PPM Portal. 2) The template used by the end user to state their privacy preferences shall align with th... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 11.4.1.3 Creating a customized Privacy Policy for each end user | 1) To make it easy for the data subject to confirm differences between the privacy preference and the privacy policy: a) If the ASP's selection of the feature represented by the tag value matches the privacy preference selected by the user for that Application/Device, then the corresponding "presented to user" indicato... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12. Security-Specific oneM2M Data Type Definitions | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.1 Introduction | Clause 12 contains data type definitions used only within the oneM2M security specifications. Any data types of XML elements defined for use only within oneM2M security specifications shall use the namespace: • https://www.onem2m.org/technical/specifications. The present document, and any XML or XML Schema Documents pr... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.2 Simple Security-Specific oneM2M Data Types | Table 12.2-1 describes simple data type definitions specific to security. The types in table 12.2-1 are either: • Atomic data types derived from XML Schema data types by restrictions other than enumeration. • List data types constructed from other XML Schema or oneM2M-defined atomic data types. Table 12.2-1: Security-s... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.3 Enumerated Security-Specific oneM2M Data Types | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.3.1 Introduction | The enumerated security-specific oneM2M data types are treated identically to the enumerated oneM2M data types defined in clause 6.3.4 of ETSI TS 118 104 [4]. These data types are based on <xs:integer>, with the numeric values interpreted as specified in clause 12.3.2. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.3.2 Enumeration type definitions | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.3.2.1 sec:credIDTypeID | The sec:credIDTypeID enumeration type is used in sec:credentialID to identify the type of the identified credential. ETSI ETSI TS 118 103 V4.7.1 (2026-03) 220 oneM2M TS-0003 version 4.7.1 Release 4 Table 12.3.2.1-1: Interpretation of the sec:credIDTypeID enumeration type Value Interpretation Note 10 Symmetric key used ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.3.2.2 sec:devMgmtID | The sec:devMgmtID enumeration type is used in sec:deviceConfigURI as an identifier of the device management technology used for field device configuration (cf. ETSI TS 118 122 [57]). The sec:devMgmtID enumeration type is also used in the devMgmtID element of the devCfgArgs element of the cmdArgs of the MEF Client Comma... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.3.2.3 sec:cmdClassID | The sec:cmdClassID enumeration type is used in the MEF Client Command cmdDescription element (see clause 8.3.9.4) to indicate the cmdClass of the cmdDescription. The cmdDescription is an attribute of the <mefClientCmd> resource type specified in ETSI TS 118 132 [58]). Table 12.3.2.3-1: Interpretation of the sec:cmdClas... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.3.2.4 sec:cmdStatusCode | The sec:cmdStatusCode enumeration type is used by the cmdStatusCode element to indicate the status of an MEF Client Command. The cmdStatus is an attribute of the <mefClientCmd> resource type specified in ETSI TS 118 132 [58]. Table 12.3.2.4-1: Interpretation of the sec:cmdStatusCode enumeration type Value Interpretatio... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.3.2.5 sec:certProvProtocolID | The sec:certProvProtocolID enumeration type is used for the certProvProtocolID element of the certProvCmdArgs element of the cmdArgs element of the MEF Client Command cmdDescription element (see clause 8.3.9.7) to indicate the Certificate Provisioning protocol to be used. The cmdDescription is an attribute of the <mefC... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.3.2.6 sec:certSubjectType | The sec:certSubjectType enumeration type is used for the certSubjectType element of the certProvCmdArgs element of the cmdArgs element of the MEF Client Command cmdDescription element (see clause 8.3.9.7) to indicate if the subject of the provisioned certificate will be a Node, CSE or AE. The cmdDescription is an attri... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.3.2.7 sec:objectTypeID | The sec:objectTypelID enumeration type is used for the objectTypelID element of the MONodeCmdArgs element of the cmdArgs element of the MEF Client Command cmdDescription element (see clause 8.3.9.9) to indicate the type of an MO Node. The cmdDescription is an attribute of the <mefClientCmd> resource type specified in E... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.4 Complex Security-Specific oneM2M Data Types | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.4.1 MAF and MEF client configuration data | Table 12.4.1-1 defines the assignment of data types to the four data containers which are used in MAF and MEF client registration and key registration configuration procedures. Note that these data containers are not defined in the form of resource types since the information is not remotely accessible. The information... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.4.2 sec:clientRegCfg | Data type sec:clientRegCfg applies to the mefClientRegCfg and mafClientRegCfg data containers used in MEF Client Registration Configuration and MAF Client Registration Configuration, see clause 8.3.7.2 and clause 8.8.3.2, respectively. Table 12.4.2-1: Type definition of sec:clientRegCfg Element Path Element Type Multip... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.4.3 sec:keyRegCfg | Data type sec:keyRegCfg applies to the mefKeyRegCfg and mafKeyRegCfg data containers used in MEF Key Registration Configuration and MAF Key Registration Configuration, see clause 8.3.7.3 and clause 8.8.3.3, respectively. Table 12.4.3-1: Type definition of sec:keyRegCfg Element Path Element Type Multiplicity Notes expir... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.4.4 sec:cmdDescription | The sec:cmdDescription complex type is used by the cmdDescription element to describe an MEF Client Command, described in clause 8.3.9.5. The cmdDescription is an attribute of the <mefClientCmd> resource type specified in ETSI TS 118 132 [58]. Table 12.4.4-1: Type definition of sec:cmdDescription Element Path Element T... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.4.5 sec:cmdArgs | The sec:cmdArgs complex type is used by the cmdArgs element of datatype sec:cmdDescription. Table 12.4.5-1: Type definition of sec:cmdArgs Element Path Element Type Multiplicity Notes noMoreCmdArgs sec:noMoreCmdArgs 0..1 See clause 12.4.6 certProvCmdArgs sec:certProvCmdArgs 0..1 See clause 12.4.7 devCfgCmdArgs sec:devC... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.4.6 sec:noMoreCmdArgs | The sec:noMoreCmdArgs complex type is used in sec:cmdDescription. Table 12.4.6-1: Type definition of sec: noMoreCmdArgs Element Path Element Type Multiplicity Notes retryDuration xs:duration 1 |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.4.7 sec:certProvCmdArgs | The sec:certProvCmdArgs complex type is used in sec:cmdDescription. Table 12.4.7-1: Type definition of sec:certProvCmdArgs Element Path Element Type Multiplicity Notes certProvProtocolID sec:certProvProtocolID 1 See clause 12.3.2.5 URI xs:anyURI 1 certSubjectType sec:certSubjectType 1 See clause 12.3.2.6 certSubjectID ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.4.8 sec:devCfgCmdArgs | The sec:devCfgCmdArgs complex type is used in sec:cmdDescription. Table 12.4.8-1: Type definition of sec:devCfgCmdArgs Element Path Element Type Multiplicity Notes deviceConfigURI sec:deviceConfigURI 1 See clause 12.2 |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 12.4.9 sec:MONodeCmdArgs | The sec:MONodeCmdArgs complex type is used in sec:cmdDescription. Table 12.4.9-1: Type definition of sec:MONodeCmdArgs Element Path Element Type Multiplicity Notes objectPath xs:anyURI 1 objectTypeID sec:objectTypeID 1 See clause 12.3.2.7 objectTypeSpecifcArgs sec:authProfileMONodeArgs 0..1 See clause 12.4.10 ETSI ETSI... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 1 Scope | The reporting of Global KPIs in accordance with ETSI EN 305 200-2-2 [2] requires the collection of data to enable the calculation of the following aspects: • Objective KPI relating to task efficiency (KPITE) based on data_volume and total energy consumption (KPIEC). • Objective KPI relating to the use of renewable ener... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.