hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.3 XSD template for sub-classes of Base Ontology class: Service | Specific XSD definition for class:Service to be substituted at the placeholder in the XSD skeleton in clause 7.2.1.2. The value of attribute containerDefinition of the specialization of the <flexContainer> shall be set as specified in table 1. EXAMPLE: <xs:element name="containerDefinition" type="//m2m.service.com/IN-C... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.4 XSD template for sub-classes of Base Ontology class: Operation | Specific XSD definition for class:Operation to be substituted at the placeholder in the XSD skeleton in clause 7.2.1.2. The value of attribute containerDefinition of the specialization of the <flexContainer> shall be set as specified in table 1. EXAMPLE: <xs:element name="containerDefinition" type="//m2m.service.com/IN... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 1 Scope | The present document specifies the detailed defined product profiles that can be used by manufactures and service providers where for each dedicated product, one of the defined product profile can be selected. The product profile would provide guidance to what features will be implemented, what features should be imple... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 2 References | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 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... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 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... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 3 Definition of terms, symbols and abbreviations | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 3.1 Terms | Void |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 3.2 Symbols | Void. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 6 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 3.3 Abbreviations | Void. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 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]. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5 Product service profiles | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.1 Introduction | This clause defines Product Profiles. Product may be Implementations of oneM2M specification. The Implementation is claimed to comply with one or multiple Product Profiles. Each profile is defined with fundamental feature set and extendable feature set. Fundamental feature set includes Features that shall be implemente... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.2 Constrained sensor as ADN | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.2.1 Profile description | The profile defines constraint sensor that is powered by battery and intended to be used for years after deployment without any human interference for maintenance. Therefore, the function of constraint sensor needs to be very limited. A sensor is intended to be reporting sensed data to the CSE periodically or according... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.2.2 Profile usage examples | The profile applies to constraint sensors that report periodically sensed data. Some example of this kind of product include: • Electricity, water, gas meters that report consumed amount of electricity, water or gas to the CSE. The meters are deployed inside houses and are powered by battery. ETSI ETSI TS 118 125 V2.0.... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.2.3 Fundamental feature sets | For constrained sensors, the features in the fundamental feature sets assume that the registration relationship between the ADN and the registrar CSE has been pre-configured beforehand. The <container> resource has also been pre-configured and the resource id of the <container> resource was provisioned to the ADN as we... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.2.4 Extendable feature sets | Table 5.2.4-1: Extendable feature sets for constrained sensor as ADN Function Feature Set Feature Remark REG AE/REG/00002 AE/REG/00002/00001 Create <AE> TP/oneM2M/AE/REG//CRE/001 TP/oneM2M/AE/REG/CRE/002_RR AE/GEN/00003/00001 Create <AE> with resourceName TP/oneM2M/AE/REG/CRE/002_RN AE/GEN/00003/00002 Create <AE> with ... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.3 Constrained actuator as ADN | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.3.1 Profile description | The profile defines constraint actuator that is powered by battery and intended to be used for years after deployment without any human interference for maintenance. Therefore, the function of constraint actuator needs to be very limited. An actuator is intended to be receiving control command from CSE via notification... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.3.2 Profile usage examples | Switches deployed along the street light to switch on or off the street light remotely. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 9 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.3.3 Fundamental feature sets | Table 5.3.3-1: Fundamental feature sets for constrained sensor as ADN Function Feature Set Feature Remark GEN AE/GEN/00001 At least one Resource identifiers TP/oneM2M/AE/GEN/CRE/001_CSR TP/oneM2M/AE/GEN/CRE/001_SPR TP/oneM2M/AE/GEN/CRE/001_ABS TP/oneM2M/AE/GEN/CRE/002_CSR TP/oneM2M/AE/GEN/CRE/002_SPR TP/oneM2M/AE/GEN/C... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.3.4 Extendable feature sets | Void. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.4 ADN profile 3 | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.4.1 Profile description | This profile defines features for normal sensor devices or software components that desire to implement oneM2M sensing services. The sensing services such as monitoring temperature, detecting illumination, collection of location information, etc. are characterized with collecting and uploading measurement data into a d... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.4.2 Profile usage examples | This profile applies to normal sensors deployed in non-critical environments have relative rich resources and are powered by electricity power or by battery that can be easily changed. This profile can also apply to software components that implements sensing services. Taking smart socket as an example, when a manufact... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.4.3 Fundamental feature sets | Container is used for storing the measurements of sensing device and whenever there is data measured from the sensing device, the data will be sent to the CSE for storage by sending a <contentInstance> create request from the originator where the encoded measurement is included within the payload of the <contentInstanc... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.4.4 Extendable feature sets | Void. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 11 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.5 ADN Profile 4 | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.5.1 Profile description | oneM2M provides several logical entity concepts called 'Node' to explain oneM2M Architecture in ETSI TS 118 101 [i.3]. And from the descriptions about the node types, it indicates some examples that particular node could match with physical oneM2M devices (e.g. ADN -> constraintedconstrained oneM2M Device). But for the... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.5.2 Profile usage examples | ADN Profile 1 could be the basic profile of oneM2M devices like sensor, actuator, etc. And also this profile could be used independently when developers want to implement oneM2M devices with special functions. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.5.3 Fundamental feature sets | Table 5.5.3-1: Feature set for ADN Profile 4 Function Feature Set Feature Remark GEN AE/GEN/00001 At least one Support one of the format of resource identification TP/oneM2M/AE/GEN/CRE/001_CSR TP/oneM2M/AE/GEN/CRE/001_SPR TP/oneM2M/AE/GEN/CRE/001_ABS TP/oneM2M/AE/GEN/CRE/002_CSR TP/oneM2M/AE/GEN/CRE/002_SPR TP/oneM2M/A... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.5.4 Extendable feature sets | Table 5.5.4-1 Funct ion Feature Set Feature Remark REG AE/REG/00002 AE/REG/00002/00001 Create <AE> with App-ID attribute TP/oneM2M/AE/REG/CRE/002_API VOID Create <AE> with ontologyRef attribute TP/oneM2M/AE/REG/CRE/002_OR VOID Update <AE> with ontologyRef attribute TP/oneM2M/AE/DMR/UPD/001_OR DMR AE/DMR/00001 AE/SEC/00... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.6 IN Profile | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.6.1 Profile description | oneM2M provides several logical entity concepts called 'Node' to explain oneM2M Architecture in ETSI TS 118 101 [i.3] . And from the descriptions about the node types, it indicates some examples that particular node could match with physical oneM2M devices (e.g. ADN -> constraintedconstrained oneM2M Device). But for th... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.6.2 Profile usage examples | IN Profile 1 could be the common profile of oneM2M devices like service server, etc. and also this profile could be used independently when developers want to implement oneM2M devices with special functions. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 15 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.6.3 Fundamental feature sets | Table 5.6.3-1: Fundamental feature set for IN Profile Function Feature Set Feature Remark GEN CE/GEN/00001 CE/GEN/00001/00001 Support Unstructured resource identifier TP/oneM2M/CSE/GEN/CRE/001_CSR TP/oneM2M/CSE/GEN/CRE/001_SPR TP/oneM2M/CSE/GEN/CRE/001_ABS TP/oneM2M/CSE/GEN/UPD/001_CSR TP/oneM2M/CSE/GEN/UPD/001_SPR TP/... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.6.4 Extendable feature sets | Table 5.6.4-1: Extendable feature set for IN Profile Function Feature Set Feature Remark DIS CE/DIS/00001 CE/DIS/00001/00001 Support the Discovery request with filterUsage equals to "Discovery" TP/oneM2M/CSE/DIS/001 TP/oneM2M/CSE/DIS/002 TP/oneM2M/CSE/DIS/003 TP/oneM2M/CSE/DIS/004 TP/oneM2M/CSE/DIS/005 TP/oneM2M/CSE/DI... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.7 Constrained actuator as ASN | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.7.1 Profile description | The profile defines constraint actuator that is powered by battery and intended to be used for years after deployment without any human interference for maintenance. Therefore, the function of constraint actuator needs to be very limited. An actuator is intended to to receive control command from CSE via notification o... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.7.2 Profile usage examples | Switches deployed along the street light to switch on or off the street light remotely. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 25 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.7.3 Fundamental feature sets | The fundamental feature set assumes that the resource id of the <container> resource needed for create <contentInstance> is pre-configured at the ASN-CSE and provisioned to the AEs that tends to send requests to the ASN-CSE. Table 5.7.3-1: Fundamental feature sets for constrained sensor as ASN Function Feature Set Feat... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.7.4 Extendable feature sets | Void. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.8 Gateway as MN | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.8.1 Profile description | The profile defines gateways that may support multiple different area network technologies and connect devices from the corresponding area networks. The devices may be oneM2M defined ADNs, ASNs or NoDNs which are not defined by oneM2M. The gateway hosts resources to enforce common services that devices in the area netw... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.8.2 Profile usage examples | Home gateways deployed in the home for smart home: • Sensors, actuators and home appliances are connected with the home gateway. Applications can be connected through the platform to access the smart home service as well as applications can be directly connected with the gateway to do the same thing. Head unit in conne... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.8.3 Fundamental feature sets | Table 5.8.3-1: Fundamental feature sets for gateway as MN Function Feature Set Feature Remark GEN CE/GEN/00001 CE/GEN/00001/00001 Unstructured resource id TP/oneM2M/CSE/GEN/CRE/001_CSR TP/oneM2M/CSE/GEN/CRE/001_SPR TP/oneM2M/CSE/GEN/CRE/001_ABS TP/oneM2M/CSE/GEN/UPD/001_CSR TP/oneM2M/CSE/GEN/UPD/001_SPR TP/oneM2M/CSE/G... |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.8.4 Extendable feature sets | Table 5.8.4-1: Extendable feature set for gateway as MN Function Feature Set Feature Remark DIS CE/DIS/00001 CE/DIS/00001/00001 Support the Discovery request with filterUsage equals to "Discovery" TP/oneM2M/CSE/DIS/001 TP/oneM2M/CSE/DIS/002 TP/oneM2M/CSE/DIS/003 TP/oneM2M/CSE/DIS/004 TP/oneM2M/CSE/DIS/005 TP/oneM2M/CSE... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 1 Scope | The present document specifies the detailed methods for oneM2M and OCF interworking using the architecture identified in ETSI TS 118 133 [5] and annex F of ETSI TS 118 101 [2] for the following scenario: • Interworking with full mapping of the semantics of the non-oneM2M data model to Mca, see scenario number 1 listed ... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 2 References | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 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... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 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... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 3 Definition of terms, symbols and abbreviations | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [1], ETSI TS 118 101 [2] and ETSI TS 118 133 [5] and the following apply. NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TS 118 111 [1], ETSI TS 118 101 [2] and ETSI TS 118 1... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 3.2 Symbols | Void. |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACP Access Control Policy AE Application Entity AE-ID Application Entity IDentifier CSE Common Services Entity GUI Graphical User Interface ETSI ETSI TS 118 124 V4.0.1 (2025-10) 8 oneM2M TS-0024 version 4.0.1 Release 4 ID Identification IoT In... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 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]. |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 5 Introduction to OCF interworking | OCF specifies an architecture enabling resource-based interactions among OCF devices, see OCF Core Specification [7]. OCF devices can expose aspects of the physical world like a lightbulb and/or logical entities like an application. The OCF devices in the OCF architecture can provide services - in that case they play t... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 6 OCF interworking architecture | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 6.1 Exposure of OCF functions to the oneM2M system | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 6.1.1 Summary of interworking architecture for exposure of OCF functions | An OCF-IPE exposing OCF functions to the oneM2M system is responsible for the creation of oneM2M resources representing the exposed OCF functions on its own Registrar-CSE. A single OCF-IPE may expose OCF functions provided by one or more OCF servers to the oneM2M system. A high-level summary of the relationship of OCF ... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 7 Representation of OCF and/or oneM2M functions | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 7.1 Representation of OCF functions by oneM2M resources | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 7.1.1 Representation of OCF devices by oneM2M <node> resources | An OCF device which provides functions that are exposed to the oneM2M system can be represented by a oneM2M <node> resource that contains device-specific information which can be used e.g. for the purpose of device management. Whether a specific OCF device shall be represented by a oneM2M <node> resource depends on the... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 7.1.2 Representation of OCF devices by oneM2M <AE> resources | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 7.1.2.1 OCF clients | The present document does not specify any normative procedure to represent OCF clients as oneM2M <AE> resources. Since the OCF specifications do not define any procedure for OCF clients needing to register themselves with any other entity or needing to respond to any discovery procedures before trying to consume servic... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 7.1.2.2 OCF servers | OCF devices playing the role of an OCF server can be represented by an <AE> resource that corresponds to an OCF-IPE, see figure 6.1.1-1. Depending on implementation and deployment needs, one or more OCF servers can be exposed on the oneM2M side by a single OCF-IPE with a single <AE> resource. Furthermore, an OCF-IPE ca... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 7.2 Representation of oneM2M services by OCF resources | Services provided by oneM2M devices can be exposed to an OCF Proximal IoT Network by an OCF-IPE acting as one or more OCF servers - see clause 6.2.1. The OCF servers instantiated by an OCF-IPE are termed virtual OCF servers in the present document. The OCF-IPE itself follows the concept of an OCF bridge device, see OCF... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8 OCF interworking procedures | 8.1 Procedures supporting exposure of OCF functions to the oneM2M system 8.1.1 Determination of OCF functions to be exposed to the oneM2M system In an OCF Proximal IoT Network, the specific setup and security parameters to be used by OCF clients or OCF servers - such as credentials to be used - are provisioned during a... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.2.2.0 Introduction | Clause 8.1.2.2 describes the procedures related to the use of <flexContainer> resources - and possibly any required child resources thereof - to represent exposed OCF servers to the oneM2M system. ETSI ETSI TS 118 124 V4.0.1 (2025-10) 26 oneM2M TS-0024 version 4.0.1 Release 4 |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.2.2.1 Parent resource and dependency on OCF Device Types | In line with ETSI TS 118 133 [5] and clause 7.1.3 of the present document, services provided by exposed OCF servers shall be represented by <flexContainer> resources on the oneM2M side - and possibly by child resources thereof. Which particular specialization of <flexContainer> resources shall be used to represent an O... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.2.2.2 Creation of <flexContainer> resources used to represent OCF servers | 8.1.2.2.2.1 Pre-requisites A pre-requisite to create <flexContainer> resources used to represent OCF servers is that the OCF-IPE has previously determined which specific OCF servers have to be exposed, see the description in clause 8.1.1 and sub-step a) of step 002 in clause 8.1.2.1. Proper determination of which OCF s... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.2.2.3 Deletion of <flexContainer> resources used to represent OCF servers | Reasons for deletion An OCF-IPE shall explicitly delete <flexContainer> resources it is using to represent OCF servers when the OCF-IPE detects that one or more OCF servers among the set of exposed OCF servers shall not be exposed to the oneM2M side any longer (e.g. due to removal from the OCF Proximal IoT Network), se... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.2.3 <node> and [deviceInfo] resources representing OCF devices | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.2.3.1 Creation | The physical hardware on which an OCF server is hosted is termed OCF platform in OCF specifications. It shall be represented by a <node> resource and a linked [deviceInfo] resource in line with the attribute settings defined in clause 7.1.1. Therefore, for each OCF server for which a <flexContainer> resource is getting... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.2.3.2 Linkage with <flexContainer> resources | A proper linkage between <flexContainer> resources representing OCF servers and a <node> resource representing the OCF platform hosting the respective OCF server shall be established. The nodeLink attribute of <flexContainer> resources representing OCF servers shall be set to the resource identifier of the <node> resou... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.2.3.3 Deletion | As long as a <node> resource representing an OCF platform is linked via its hostedServiceLinks attribute to at least one <flexContainer> resource representing an exposed OCF server, the <node> resource shall not be deleted. When all links to <flexContainer> resource representing an exposed OCF server have been removed ... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.3 Mirroring state of exposed OCF servers in oneM2M resources | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.3.1 Establishment of monitoring | Once the appropriate set of resources to represent an OCF server on the oneM2M side has been created, it is important to reflect accurate state information in the oneM2M resources so that they are kept consistent with the actual state of the OCF servers that they represent. In order to do so, the OCF-IPE shall establis... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.3.2 Mirroring of state information | Upon reception of state information of OCF resources via the previously established "observe" mechanism, the OCF- IPE shall identify the oneM2M resource that corresponds to the observed OCF resource and translate the received observation into the corresponding request to update the state of the oneM2M resource represen... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.3.3 Stop monitoring | When an OCF server shall no longer be exposed to the oneM2M side - this happens when step 005c and step 006 in clause 8.1.2.1 occur - then the previously established monitoring of the resources hosted by this particular OCF server using the OCF "observe" mechanism needs to be terminated to avoid any further responses b... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.4.1 Monitoring of oneM2M resources representing OCF servers | In order to find out when a properly authorized oneM2M entity would like to consume an OCF service, the OCF-IPE needs to rely on subscriptions to the oneM2M resources that are representing the exposed OCF servers. Subscriptions shall be established by the OCF-IPE to get notified whenever an authorized oneM2M entity is ... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.1.4.2 Invocation of OCF services | The procedure outlined in the present clause correspond to step 005a in clause 8.1.2.1. When the OCF-IPE has successfully established all pre-requisites for exposing a set of OCF servers to oneM2M - see step 002 in clause 8.1.2.1 - and when it has initiated the exposure - see step 003 and step 004 in clause 8.1.2.1 - i... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.2.2.1 High-level procedure to expose oneM2M services | When an OCF-IPE completes registration with its Registrar-CSE, an <AE> resource representing that OCF-IPE is created as a result of that registration. As specified in clause 7.1.2.2, the labels attribute of this <AE> resource shall reflect the fact that this AE is an OCF-IPE by adding a Key:Value pair set to "Iwked-Tec... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.2.2.2 Handling of virtual OCF server(s) representing exposed oneM2M service(s) | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.2.2.2.1 Instantiation of an OCF bridge device | The OCF-IPE shall instantiate an OCF server acting as an OCF bridge device with OCF Device Type set to "oic.d.bridge". The main responsibility for this device is to support the discovery of all the resources hosted by all virtual OCF servers instantiated to expose the selected oneM2M services to the OCF Proximal IoT Ne... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.2.2.2.2 Instantiation of virtual OCF servers | 8.2.2.2.2.1 Pre-requisites A pre-requisite to instantiate virtual OCF servers used to expose oneM2M services to the OCF Proximal IoT Network is that the OCF-IPE has previously determined which specific set of oneM2M resources representing oneM2M services have to be exposed, see the description in clause 8.2.1 and sub-s... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.2.2.2.3 Destruction of virtual OCF servers | Reasons for destruction An OCF-IPE shall destruct virtual OCF servers it is using to represent oneM2M services when the OCF-IPE detects that one or more oneM2M services among the set of exposed oneM2M services shall not be exposed to the OCF side any longer, e.g. due to deletion of the respective oneM2M resources repre... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.2.3.1 Establishment of monitoring | Once the virtual OCF server to represent an exposed oneM2M service on the OCF side has been instantiated, it is important to reflect accurate state information in the resources hosted by the virtual OCF server so that they are kept consistent with the actual state of the exposed oneM2M resources that they represent. In... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.2.3.2 Mirroring of state information | Upon detection of state changes of oneM2M resources via the previously established monitoring mechanism, the OCF-IPE shall identify the virtual OCF server that corresponds to the oneM2M resource for which a state change was detected and translate the received state change information of the oneM2M resource into a corre... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.2.3.3 Stop monitoring | When a oneM2M service shall no longer be exposed to the OCF side - this happens when step 005c and step 006 in clause 8.2.2.1 occur - then the previously established monitoring of the oneM2M resources representing the exposed services which are not to be exposed any longer according to clause 8.2.3.1 needs to be termin... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.2.4.1 Incoming requests to virtual OCF servers | In order to find out when a properly authorized OCF client would like to consume an exposed oneM2M service, the virtual OCF server responsible for exposing a given oneM2M service needs to listen to incoming requests via any of the supported transport protocols within the OCF Proximal IoT Network as outlined in OCF Core... |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 8.2.4.2 Invocation of oneM2M services | The procedure outlined in the present clause corresponds to step 005a in clause 8.2.2.1. When the OCF-IPE has successfully established all pre-requisites for exposing a set of oneM2M services to an OCF Proximal IoT Network - see step 002 in clause 8.2.2.1 - and when it has initiated the exposure - see step 003 and step... |
b00d6d6ec47d8cd692e67ae29e146ad3 | 119 164-3 | 1 Scope | The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to ASiC building blocks defined in ETSI EN 319 162-1 [1] and additional containers defined in ETSI EN 319 162-2 [2]. These test suites are agnostic of the PKI infrastructure. Any PKI infrastr... |
b00d6d6ec47d8cd692e67ae29e146ad3 | 119 164-3 | 2 References | |
b00d6d6ec47d8cd692e67ae29e146ad3 | 119 164-3 | 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... |
b00d6d6ec47d8cd692e67ae29e146ad3 | 119 164-3 | 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... |
b00d6d6ec47d8cd692e67ae29e146ad3 | 119 164-3 | 3 Definitions and abbreviations | |
b00d6d6ec47d8cd692e67ae29e146ad3 | 119 164-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TR 119 001 [i.1] and the following apply: negative test case: test case either for a container including signature(s) that are not extended CAdES signatures [i.3] or extended XAdES signatures [i.4] whose validation according to ETSI EN 31... |
b00d6d6ec47d8cd692e67ae29e146ad3 | 119 164-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.1] and the following apply: CS Container Structure SC Syntactical Conformance STV Signature Time-stamp token Value TC Test Case ETSI ETSI TS 119 164-3 V1.1.1 (2016-06) 7 4 ASiC additional container interoperability test specificatio... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.