hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
10651370426c90bc406f33851f64d370 | 118 104 | 7.3.29.2.4 Delete | Originator: No change from the generic procedures in clause 7.1.2.1. Receiver: No change from the generic procedures in clause 7.1.2.2. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.4 Primitive-specific procedures and definitions | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.4.1 Notification data object and procedures | |
10651370426c90bc406f33851f64d370 | 118 104 | 7.4.1.1 Notification data object | Notification procedures represent a special case of the generic procedures defined in clause 7.1.2, where the Operation parameter of the request primitive is set to value "N" (Notify). In this case, the request primitive is referred to as Notify request primitive, and the associated response primitive is denoted as Not... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.4.1.2 Notification procedures | Notification procedures shall be employed for the following use cases: • to notify Receiver(s) of modifications of a resource for an associated <subscription> resource; • to request Receiver(s) to perform resource subscription verification; • to notify deletion of the <subscription> resource; • to notify Receiver(s) fo... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.4.1.2.1 Notification for modification of subscribed resources | When the notification message is forwarded or aggregated by transit CSEs, the Originator or a transit CSE shall check whether there are notification policies to enforce between subscription resource Hosting CSE and the notification target. In that case, the transit CSE as well as the Originator shall process Notify req... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.4.1.2.2 Subscription Verification during Subscription Creation | Originator: When the Originator is triggered to perform subscription verification (clause 7.3.8.2.1) during <subscription> creation procedure, it performs the following in order. 1) Set the verificationRequest element of the notification data object as TRUE in the Notify request primitive. 2) Set the creator element of... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.4.1.2.3 Notification for Subscription Deletion | Originator: When the <subscription> resource is deleted, the Originator shall send a Notify request primitive with subscriptionDeletion element of the notification data object set as TRUE and subscriptionReference element set as the URI of the <subscription> resource. |
10651370426c90bc406f33851f64d370 | 118 104 | 7.4.1.2.4 Notification for Asynchronous Non-blocking Request | Originator: When the requested operation for a nonBlockingAsynch request is completed, the Originator (=hosting CSE of the resource) shall send a Notify request primitive to inform the final result of requested operation against the oneM2M resource. 1) The Originator shall compose a Request primitive with following par... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.4.1.2.5 Notification for subscription via group | Whenever the subscribed to resources' modification triggers a notification procedure as definedin clause 7.4.1.2.1 and the subscription relationship is established through group resource, the following procedure shall be performed. The Member hosting CSE shall perform the steps defined in 7.4.1.2.1. The Group hosting C... |
10651370426c90bc406f33851f64d370 | 118 104 | 7.4.2 Elements contained in the primitive Content | Clauses 7.1.1.1 and 7.1.1.2 enumerate the forms that the primitive Content parameter takes in various Request and Response cases. This clause details the Objects (elements) used in some of these cases. in the tables below. The following elements are defined for use in the content parameter of a request: Table 7.4.2-1: ... |
10651370426c90bc406f33851f64d370 | 118 104 | 8 Representation of primitives in data transfer | 8.1 Introduction This clause defines the representation of request and response primitives as XML documents or JSON texts. The process of translating objects (i.e. primitives in the present context) into a format that can be stored or exchanged between network entities is commonly denoted as serialization or marshallin... |
10651370426c90bc406f33851f64d370 | 118 104 | 8.2 Short names | |
10651370426c90bc406f33851f64d370 | 118 104 | 8.2.1 Introduction | XML and JSON representations require the explicit encoding of the names of primitive parameters, resource attributes, (in the case of XML) resource types and complex data types members. Whenever a protocol binding transfers such a name over a oneM2M reference point, it shall use a shortened form of that name, rather th... |
10651370426c90bc406f33851f64d370 | 118 104 | 8.2.2 Primitive parameters | In protocol bindings primitive parameter names shall be translated into short names of Table 8.2.2-1. Table 8.2.2-1: Primitive parameter short names Parameter Name Occurs in Short Name Operation Request op To Request, Response to From Request, Response fr Request Identifier Request, Response rqi Resource Type Request t... |
10651370426c90bc406f33851f64d370 | 118 104 | 8.2.3 Resource attributes | In protocol bindings resource attributes names shall be translated into short names of Table 8.2.3-1. Table 8.2.3-1: Resource attribute short names (1/5) Attribute Name Occurs in Short Name accessControlPolicyIDs All except accessControlPolicy, contentInstance acpi announcedAttribute accessControlPolicy, AE, container,... |
10651370426c90bc406f33851f64d370 | 118 104 | 8.2.4 Resource types | In protocol bindings resource type names shall be translated into short names of Table 8.2.4-1. Table 8.2.4-1: Resource and specialization type short names Resource Type Name Short Name accessControlPolicy acp accessControlPolicyAnnc acpA AE ae AEAnnc aeA container cnt containerAnnc cntA contentInstance cin contentInst... |
10651370426c90bc406f33851f64d370 | 118 104 | 8.2.5 Complex data types members | In protocol bindings complex data types member names shall be translated into short names of Table 8.2.5-1. Table 8.2.5-1: Complex data types members short names Parameter Name Occurs in Short Name createdBefore filterCriteria, eventNotificationCriteria crb createdAfter filterCriteria, eventNotificationCriteria cra mod... |
10651370426c90bc406f33851f64d370 | 118 104 | 8.3 Canonical XML serialization | |
10651370426c90bc406f33851f64d370 | 118 104 | 8.3.1 Method | XML serialization of request or response primitives refers to the process of representing the primitive as an XML document. The XML document shall be a well-formed XML document compliant with W3C XML 1.0 [1]. It shall be restricted to Unicode characters and encoded using UTF-8 as described in IETF RFC 3629 [21]. The st... |
10651370426c90bc406f33851f64d370 | 118 104 | 8.3.2 Examples | An example that shows a request primitive serialized into an XML document is shown below. This example shows the create request for an instance of a <contentInstance> resource. Only mandatory primitive parameters and resource attributes are shown. <?xml version="1.0" encoding="UTF-8"?> <m2m:req xmlns:m2m="http://www.on... |
10651370426c90bc406f33851f64d370 | 118 104 | 8.4 JSON serialization | |
10651370426c90bc406f33851f64d370 | 118 104 | 8.4.1 Terminology | The following conventions are used in the clause that follows. • The italicized terms object, member, name, array, number, string, boolean and null are to be interpreted as in IETF RFC 7159 [19]. • The italicized term element is to be interpreted to encompass oneM2M Primitive Parameters, Resource Attributes and other e... |
10651370426c90bc406f33851f64d370 | 118 104 | 8.4.2 Method | The primitive shall be encoded as a JSON object, conforming to the requirements of IETF RFC 7159 [19]. This JSON object shall be restricted to Unicode characters defined in The Unicode Standard and encoded using UTF-8 as described in IETF RFC 3629 [21]. The names in each object in the JSON shall be unique. The structur... |
10651370426c90bc406f33851f64d370 | 118 104 | 8.4.3 Examples | Here is an example that shows the payload of a request message serialized using JSON: • {"op": "1", "fr": "//xxxxx/2345", "to": "//xxxxx/99", "ri": "A1234", "pc": {"se": "* 0-5 2,6,10 * * *"}, "ty": 20} - op: operation (in this case it is Create). - fr: ID of the Originator (either the AE or CSE). - to: URI of the targ... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 1 Scope | The reporting of Global KPIs in accordance with ETSI EN 305 200-3-1 [2] requires the collection of data to enable the calculation of the following aspects: • objective KPI relating to the total energy consumption (KPIEC); • objective KPI relating to the use of energy performance (KPIEP) which combines KPIEC with other ... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 2 References | |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 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... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 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... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 3 Definition of terms, symbols and abbreviations | |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 305 200-3-1 [2] apply. |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI EN 305 200-3-1 [2] apply. |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI EN 305 200-3-1 [2] and the following apply: NGO Non-Governmental Organization |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4 Global KPIs of ETSI EN 305 200-3-1 | |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.1 ICT sites | The ICT sites addressed by ETSI EN 305 200-3-1 [2] and the present document are Operator Sites (OSs) and Network Data Centres (NDCs). It should be noted that an OS that is only connected to the core network is considered to be an NDC. The schematic of an ICT site used in the present document is shown in Figure 1 (taken... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2 KPIs for energy management | |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.1 Global KPI (KPIDCEM) for ICT sites | From ETSI EN 305 200-3-1 [2], KPIDCEM is a combination of two separate KPIs, for a common assessment period k, as follows: 1) the Objective KPI for energy consumption expressed as KPIEC (see clause 4.2.2.1); 2) a combination of three Objective KPIs for energy performance expressed as KPIEP: KPIEP = KPITE x ((1 - WREUSE... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.2 Objective KPIs | |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.2.1 Energy consumption (KPIEC) | From ETSI EN 305 200-3-1 [2], KPIEC for the assessment period k, KPIEC (k) is defined mathematically as: ( ) ( ) ( ) 1 S k k k EC s s KPI C C = = = or ( ) ( ) 1 N k k EC n n KPI C = = (when applied to groups of ICT sites) where, for the assessment period k: C(k) = total energy consumption by the ICT site Cn(k) = tota... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.2.2 Task effectiveness (KPITE) | From ETSI EN 305 200-3-1 [2], KPITE for the assessment period k, KPITE (k) is defined mathematically as: ( ) ( ) ( ) k k TE k C KPI L = or ( ) ( ) 1 ( ) 1 N k n k n TE N k n n C KPI L = = = (when applied to groups of ICT sites) where, for the assessment period k: C(k) = total energy consumption of the ICT site Cn(k... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.2.3 Energy reuse (KPIREUSE) | From ETSI EN 305 200-3-1 [2], KPIREUSE for the assessment period k, KPIREUSE(k) is defined mathematically as: ( ) ( ) ( ) k k REUSE REUSE k EC KPI C = or ( ) ( ) 1 ( ) 1 n N k REUSE k n REUSE N k n n EC KPI C = = = (when applied to groups of ICT sites) where, for the assessment period k: C(k) = total energy consump... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.2.4 Renewable energy (KPIREN) | From ETSI EN 305 200-3-1 [2], KPIREN for the assessment period k, KPIREN (k) is defined mathematically as: ( ) ( ) ( ) k k REN REN k EC KPI C = or ( ) ( ) 1 ( ) 1 n N k REN k n REN N k n n EC KPI C = = = (when applied to groups of ICT sites) where, for the assessment period k: C(k) = total energy consumption of the... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.3 Underlying principles | |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.3.1 Energy consumption | ETSI EN 305 200-3-1 [2] and the present document support the reduction in the energy consumption required to provide a given level of service as a primary objective. The KPIEC may be improved by local actions within individual ICT sites and/or global actions applied to the group under common governance. |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.3.2 Task effectiveness | ETSI EN 305 200-3-1 [2] and the present document support the improvement in task effectiveness as a primary objective. KPITE is the ratio of the total energy consumption of the ICT site to the energy consumption of the ICT equipment in the ICT site. KPITE is dimensionless and has the following properties: • KPITE ≥ 1; ... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.3.3 Energy re-use | |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.3.3.1 Objective | ETSI EN 305 200-3-1 [2] and the present document support re-use of energy as a secondary objective. KPIREUSE is the ratio of re-used energy by facilities, external to the ICT site, to the total energy consumption of the ICT site. Thermal energy can be reused in different forms, liquid or gas (air). KPIREUSE shall be me... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.3.3.2 Measurement | KPIREUSE can only be assessed and included in subsequent calculation and presentation of KPIDCEM if the energy re-used is measurable at the intended point of delivery i.e. any losses in the delivery system shall not be included. In addition to the text of ETSI EN 305 200-3-1 [2] it should be noted that losses in the sy... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.3.4 Renewable energy | |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.3.4.1 Objective | ETSI EN 305 200-3-1 [2] and the present document support the use of renewable energy as a secondary objective. KPIREN is the ratio of energy consumption from renewable sources to the total energy consumption of the ICT site. It is a dimensionless number. A simple comparison between KPIREN and Renewable Energy Factor of... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.2.3.4.2 Measurement | Only the sources contributing to KPIEC will be taken into account, whether dedicated or shared. KPIREN takes account of renewable energy that is produced by: a) sources dedicated to and directly serving an ICT site; b) sources (an ICT site or generator) under common governance with the ICT site(s) they serve and from w... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.3 Energy management trends | The Global KPI, KPIDCEM, is primarily intended to indicate the success of a defined energy management policy, independent of the site or location under consideration. The use of bands as described in clause 6 does not generally allow the trend analysis but the reporting (see clause 7) of the Objective KPIs and the rele... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 4.4 Energy management practices | An increase in either KPITE or KPIREN represents an improvement in energy management of the ICT sites - although individual improvements of KPITE and KPIREN are not comparable. Requirements and recommendations in relation to the improvement of the energy management of ICT sites are contained within ETSI EN 305 174-2 [i... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 5 Data collection | |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 5.1 General | Measurement points and procedures have been described in detail in ETSI EN 305 200-3-1 [2]. However, there are some cases where these are difficult to apply either because of scale or lack of instrumentation. This clause describes the methods and restrictions that apply in such cases. |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 5.2 Estimated measurements | |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 5.2.1 Large groups of ICT sites | While in large ICT sites, measurement of energy consumption is easy using a small number of meters as described in ETSI EN 305 200-3-1 [2], the measurement of consumption in large groups of smaller ICT sites would be costly with regard to the number of counters to be implemented. Objective KPIs for such a group of ICT ... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 5.2.2 Power measurements | Power consumption measurements can only be accepted as a palliative solution as compared to energy consumption measurements. This is because such measurements are periodic samples, typically obtained technician visits, and are less dependable than continuous energy consumption measurements which integrate over time the... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 6 Weighting and banding constants | |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 6.1 The use of weighting factors to reflect policy objectives | In general, the Global KPIs of the ETSI EN 305 200 series [1] are designed to measure or map the performance of a infrastructure of broadband deployment to a specific policy, normally created by its owner or a third party, with regard to energy management. The present document supports ETSI EN 305 200-3-1 [2] which spe... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 6.2 The use of bands for DCG and DCCLASS | ETSI EN 305 200-3-1 [2] specifies that KPIDCEM is presented as two Objective KPIs (KPIEC and KPIEM) which are classified within bands (DCG and DCCLASS respectively). This simplified description of energy management performance allows an ICT site or group of ICT sites to be easily positioned in comparison to its neighbo... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 6.3 Values | Table 3 shows banding values that have been obtained from a survey of ICT sites in France and are applied for all members of Non-Governmental Organization (NGO) eG4U. It is clear from Table 3 that a consistent policy objective is applied to all values of KPIEC (and therefore DCG). ETSI ETSI TS 105 200-3-1 V1.2.1 (2019-... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 7 Trend analysis | Trending can only be significant when comparing data using the same policy. Note that a change of KPIEC band may change the two weighting parameters (WREN, WREUSE). Banded values of KPIEC (i.e. DCG) are not particularly useful for assessing trends, but banded values for KPIEP (i.e. DCCLASS) as defined in ETSI EN 305 20... |
01cd6ebc349e0889678e3746d8ba2764 | 105 200-3-1 | 8 Reporting templates | For public reporting purposes Table 5 shall be used. All assessment periods shall be one year including allowable inaccuracies as defined in ETSI EN 305 200-3-1 [2]. Table 5: Template to be used for public reporting Name of ICT site (or group of ICT sites) See note 1 End of assessment period See note 2 Statistical accu... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 1 Scope | The present document defines security solutions applicable within the M2M system. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 2 References | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 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... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 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... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 3 Definition of terms, symbols and abbreviations | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [2] and the following apply: additional authenticated data [14]: data that is authenticated, but not encrypted by an authenticated encryption with associated data algorithm AE-ID Certificate: certificate with a certificate chain to a trust anc... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: || Concatenation |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 111 [2] and the following apply: (D)TLS-PSK (D)TLS Pre-Shared Key (ciphersuites) 3GPP2 3rd Generation Partnership Project 2 ETSI ETSI TS 118 103 V4.7.1 (2026-03) 23 oneM2M TS-0003 version 4.7.1 Release 4 AAA Authentication, Authorization a... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 4 Conventions | The keywords "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]. |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 5 Security Architecture | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 5.1 Overview | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 5.1.0 Introduction | Figure 5.1.0-1 provides a high level overview of the Security architecture. The architecture consists of following layers: • Security Functions layer: - This layer contains a set of security functions that are exposed at reference point Mca and Mcc. These security functions can be classified into six categories; they a... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 5.1.1 Identification and Authentication | The Identification and Authentication function is in charge of identification and mutual authentication of CSEs and AEs. Identification is the process of checking if the identity provided for authentication is valid. How to perform an identification process will depend on the purpose of authentication. For example, in ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 5.1.2 Authorization | The Authorization function is responsible for authorizing services and data access to authenticated entities according to provisioned Access Control Policies (ACPs) and assigned roles. Access control policy is defined as sets of conditions that define whether entities are permitted access to a protected resource. The a... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 5.1.3 Identity Management | The Identity Management function provides oneM2M identities/identifiers to the requesting entity in case those identities are stored within the secure environment. oneM2M identifiers as defined in the oneM2M Architecture (ETSI TS 118 101 [1]) can also be treated as sensitive data that are accessible to AEs or CSEs and ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 5.2 Security Layers | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 5.2.1 Security Service Layer | The security service layer provides the following services: • Access Management: - Identification and Authentication. ETSI ETSI TS 118 103 V4.7.1 (2026-03) 27 oneM2M TS-0003 version 4.7.1 Release 4 - Authorization. - Access Control. • Sensitive Data Handling: - Sensitive Functions protection. - Secure Storage. • Trust ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 5.2.2 Secure Environment Abstraction Layer | The Secure Environment Abstraction Layer (not specified in the present document) provides access to the Secure Environment via a general Security Transport API. A Plug-in associated to the type of Secure Environment provides physical/logical connectivity to the secure environment. The Secure Environment Abstraction Lay... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 5.3 Integration within overall oneM2M architecture | Security services are provided within the following architectural components and interact on the different reference points as described in ETSI TS 118 101 [1]. AE AE Mca Mca Mca Mcc Mcn Mcn CSE CSE NSE NSE Field Domain Infrastructure Domain To Infrastructure Domain of other Service Provider Mcc’ Figure 5.3-1: oneM2M F... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6 Security Services and Interactions | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.1 Security Integration in oneM2M flow of events | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.1.1 Interactions between layers | Before any M2M Common Services layer procedure can take place, connectivity has to be established in the underlying Network Services Layer, which may involve independent provisioning and service registration procedures specified by the underlying network. The Service Layer Security provisioning (security pre-provisioni... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.1.2 High level sequence of events | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.1.2.1 Enrolment phase | M2M equipment typically requires provisioning and configuration phases before being put in actual operation. This can be performed by a pre-provisioning that can be integrated in the manufacturing or product deployment phase, or by means of a security bootstrapping procedure (i.e. remote security provisioning) that tak... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.1.2.2 Operational phase | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.1.2.2.1 M2M Service Access | M2M services are offered by CSEs to AEs and/or other CSEs. To be able to use M2M services offered by one CSE, the AEs and/or CSEs need to be mutually identified and authenticated with that CSE, in order to provide protection from unauthorized access and Denial of Service attacks. This mutual authentication enables to a... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.1.2.2.2 Authorization to access M2M resources | Once an AE or CSE has been granted access to M2M services, the Access Control decision procedure specified in clause 7.1.5 of the present document is executed before accessing an M2M resource, as specified in ETSI TS 118 101 [1]. M2M Entity A M2M Entity B UN-SP Domain Field Domain 3rd Party Domain or M2M-SP Infrastruct... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.1.2.2.3 Security for multicast group fanout procedures | Multicast group fan out is specified in ETSI TS 118 101 [1]. When this procedure is employed, request primitives originating from a Group Hosting CSE and received by Member Hosting CSEs are transferred on the Mcc reference point over a multicast capable underlying network such as 3GPP MBMS (ETSI TS 123 246 [77]). The m... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.2 Security Service Layer | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.2.1 Access Management | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.2.1.1 Identification and Authentication | This component provides authentication services to the Application Layer. Annex B provides a general description of Authentication mechanisms. oneM2M mutual authentication schemes allow oneM2M entities to prove that they know related credentials such as Master Credentials, without having to exchange value of those cred... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.2.2 Authorization Architecture | Figure 6.2.2-1 provides a high level overview of a generic authorization architecture. This architecture comprises four subcomponents that are described as follows: • Policy Enforcement Point (PEP): - PEP intercepts resource access requests, makes access control decision requests, and enforces access control decisions.... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.2.3 Security Administration | |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.2.3.0 Introduction | The Security Administration service provides the capability to manage the Security functions, resources and attributes. This includes management of resources provided via the secure environment. In addition it can provide functions to manage sensitive data with their associated identifiers and subscriptions on behalf o... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.2.3.1 Security Pre-Provisioning of SE | Several sensitive data and associated objects are often configured by pre-provisioning of a secure environment (see clause 6.3.1) prior to deploying the M2M device it is associated with. UICCs specified in ETSI TS 102 671 [23] and ETSI TS 102 221 [24] are commonly used for such purpose because their use is required to ... |
a34b68cd8fd97fbe671d4316d3bc89c1 | 118 103 | 6.2.3.2 Remote security administration of SE | Security sensitive data and functions that are protected and isolated within the SE may remain remotely accessible to legitimate security administrators after deployment. Remote security administration differs from standard device management by the expectation that a secure channel is intended to be established between... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.