hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6 oneM2M Architecture Aspects | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.1 Configurations supported by oneM2M Architecture | The possible configurations of inter-connecting the various entities supported within the oneM2M system are illustrated in figure 6.1-1. The illustration does not constrain the multiplicity of the entities nor require that all relationships shown are present. Figure 6.1-1: Configurations supported by oneM2M Architecture Nodes: Nodes are logical entities that are individually identifiable in the oneM2M System. Nodes are either CSE-Capable or Non-CSE-Capable: • A CSE-Capable Node is a logical entity that contains one oneM2M CSE and contains zero or more oneM2M AEs. The ASN, IN and MN are examples of CSE-Capable Nodes. • A Non-CSE-Capable Node is a logical entity that does not contain a oneM2M CSE and contains zero or more oneM2M AEs. The ADN and Non-oneM2M Node are examples of Non-CSE-Capable Nodes. CSEs resident in different Nodes can be different and are dependent on the services supported by the CSE and the characteristics (e.g. different memory, firmware) of the physical entity that contains the CSE's Node. Description of Node types: The oneM2M architecture enables the following types of Nodes. As logical objects, such Nodes may or may not be mapped to physical objects. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 29 (oneM2M TS-0001 version 4.15.0 Release 4) Application Service Node (ASN): An ASN is a Node that contains one CSE and contains at least one Application Entity (AE). There may be zero or more ASNs in the Field Domain of the oneM2M System. The CSE in an ASN communicates over the Mcc reference point with one CSE residing in a MN or in an IN. An AE in an ASN communicates over the Mca reference point with the CSE residing in the same ASN. An ASN communicates over Mcn with NSEs. Example of physical mapping: an ASN could reside in an M2M Device. Application Dedicated Node (ADN): An ADN is a Node that contains at least one AE and does not contain a CSE. There may be zero or more ADNs in the Field Domain of the oneM2M System. An AE in the ADN communicates over the Mca reference point with a CSE residing in a MN or in an IN. Example of physical mapping: an Application Dedicated Node could reside in a constrained M2M Device. Middle Node (MN): A MN is a Node that contains one CSE and contains zero or more AEs. There may be zero or more MNs in the Field Domain of the oneM2M System. The CSE in a MN communicates over the Mcc reference point with one CSE residing in a MN or in an IN and with one or more other CSEs residing in MNs or in ASNs. In addition, the CSE in the MN can communicate over the Mca reference point with AEs residing in the same MN or residing in an ADN. A CSE in a MN communicates over Mcn with NSEs. Example of physical mapping: a MN could reside in an M2M Gateway. Infrastructure Node (IN): An IN is a Node that contains one CSE and contains zero or more AEs. There is exactly one IN in the Infrastructure Domain per oneM2M Service Provider. A CSE in an IN may contain CSE functions not applicable to other node types. The CSE in the IN communicates over the Mcc reference point with one or more CSEs residing in MN(s) and/or ASN(s). The CSE in the IN communicates over the Mca reference point with one or more AEs residing in the same IN or residing in an ADN. The CSE in the IN communicates over the Mcn reference point with NSEs, and over the Mcc' reference point with CSEs residing in the INs of other M2M Service Providers. Example of physical mapping: an IN could reside in an M2M Service Infrastructure. Non-oneM2M Node (NoDN): A non-oneM2M Node is a Node that does not contain oneM2M Entities (neither AEs nor CSEs). Such Nodes represent devices attached to the oneM2M system for interworking purposes, including management. A Non-oneM2M Node communicates (as shown by dotted lines in figure 6.1-1) with the oneM2M System according to annex F. Domain Types: The Infrastructure Domain of any particular M2M Service Provider contains exactly one Infrastructure Node. The Field Domain of any particular M2M Service Provider can contain Application Service Nodes, Application Dedicated Nodes, Middle Nodes and Non-oneM2M Nodes. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 30 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2 Common Services Functions | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.0 Overview | This clause describes the services provided by the Common Services Layer in the M2M System. Such services reside within a CSE and are referred to as Common Services Functions (CSFs). The CSFs provide services to the AEs via the Mca reference point and to other CSEs via the Mcc reference point. CSEs interact with the NSE via the Mcn reference point. An instantiation of a CSE in a Node comprises a subset of the CSFs from the CSFs described in the present document. The CSF descriptions in this clause are provided for the understanding of the oneM2M Architecture functionalities and are informative. The CSFs contained inside the CSE can interact with each other but how these interactions take place are not specified in the present document. Mca Reference Point Mcn Reference Point Underlying Network Service Entity (NSE) Common Services Entity (CSE) Mcc Reference Point Data Management & Repository Location Security Communication Management/ Delivery Handling Registration Device Management Service Charging & Accounting Discovery Network Service Exposure/Service Ex+Triggering Group Management Application Entity (AE) Subscription and Notification Application and Service Layer Management Semantics Time Management Transaction Management Session Management Process Management Figure 6.2.0-1: Common Services Functions |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.1 Application and Service Layer Management | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.1.1 General Concepts | The Application and Service Layer Management (ASM) CSF provides management of the AEs and CSEs on the ADNs, ASNs, MNs and INs. This includes capabilities to configure, troubleshoot and upgrade the functions of the CSE, as well as to upgrade the AEs. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 31 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.1.2 Detailed Descriptions | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.1.2.0 Overview | The ASM CSF provides management capabilities for CSEs and AEs. Figure 6.2.1.2.0-1: Management Layers and Function The ASM CSF utilizes the functions provided by the Device Management (DMG) CSF for interaction with the Management Server. The management functions include: • Configuration Function (CF): This function enables the configuration of the capabilities and features of the CSE (e.g. CMDH policies). • Software Management Function (SMF): This function provides lifecycle management for software components and associated artifacts (e.g. configuration files) for different entities such as CSE and AE. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.1.2.1 Software Management Function | The Software Management Function (SMF) provides the capability to manage software components (e.g. Software Package, Software Module) for AEs and CSEs. The ASM CSF provides the capability to manage the lifecycle of the Software Packages for a CSE or an AE. AE Software Packages may be deployed on any Node that supports the AE; including those on the MNs, ADNs and ASNs. The lifecycle of a Software Package consists of states (e.g. Installing, Installed, Updating, Uninstalling and Uninstalled) that transition when an action (e.g. Download, Install, Update and Remove) is applied to the Software Package. When a Software Package is installed into an execution environment the software component that is capable of executing in the Execution Environment is called a Software Module. The lifecycle of a Software Module consists of states (e.g. Idle, Starting, Active, Stopping) that transition when an action (e.g. Start, Stop) is applied to the Software Module. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.2 Communication Management and Delivery Handling | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.2.1 General Concepts | The Communication Management and Delivery Handling (CMDH) CSF provides communications with other CSEs, AEs and NSEs. The CMDH CSF decides at what time to use which communication connection for delivering communications (e.g. CSE-to-CSE communications) and, when needed and allowed, to buffer communication requests so that they can be forwarded at a later time. This processing in the CMDH CSF is carried out per the provisioned CMDH policies and delivery handling parameters that can be specific to each request for communication. For communication using the Underlying Network data transport services, the Underlying Network can support the equivalent delivery handling functionality. In such case the CMDH CSF uses the Underlying Network, and it may act as a front end to access the Underlying Network equivalent delivery handling functionality. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 32 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.2.2 Detailed Descriptions | The service that AEs or CSEs can request from the CMDH CSF is to transport some data to a specific target (CSE or AE), according to given delivery parameters while staying within the constraints of provisioned communication management and delivery handling policies. The content of the data provided by the Originator does not influence the CMDH CSF behaviour. Consequently, the CMDH CSF is not aware of the specific operation requested at the target entity, including the parameters passed to the operation at the destination CSF. This means that all attributes intended to be delivered to the destination entity (e.g. which CSF is the destination on the target entity, what that CSF does with the data, etc.) are hidden to the CMDH CSF. The target entity may be reached either directly or via the CSE(s) of a MN(s). As part of the delivery request, the CMDH CSF can be provided with acceptable delivery parameters for the Originator (e.g. acceptable expiration time for delivery). The functions supported by the CMDH CSF are as follows: • Ability for the M2M Service Provider to derive CMDH policies describing details for the usage of the specific Underlying Network(s). These policies may be based on the M2M Service Subscription associated with Application and Common Service Entities (AEs and CSEs) in the Field Domain and on the agreements on usage of Underlying Network communication resources. CMDH Policies can be provisioned into the respective CSEs in the Field Domain. • For the delivery of communication, ability to select appropriate communication path to use at any given time in line with provisioned CMDH policies and with CMDH-related parameters set by the Originator of requests, and when needed and allowed, how long to buffer communication requests so that they can be forwarded at a later time. This policy-driven use of communication resources allows an M2M Service Provider to control which Originators of requests are allowed to consume communication resources at certain times. • For the delivery of communication, ability to detect a disconnection of communication channel. If the communication channel can be established by receiver-side only, it also detects a reconnection of the communication channel. • For the delivery of communication, ability to be aware of the availability of the Underlying Networks. • Ability to manage the proper use of buffers for store-and-forward processing through use of CMDH policies. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.3 Data Management and Repository | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.3.1 General Concepts | One of the purposes of CSEs is to enable AEs to exchange data with each other. The Data Management and Repository (DMR) CSF is responsible for providing data storage and mediation functions. It includes the capability of collecting data for the purpose of aggregating large amounts of data, converting this data into a specified format, and storing it for analytics and semantic processing. The data can be either raw data transparently retrieved from an M2M Device, or processed data which is calculated and/or aggregated by M2M entities. NOTE: Collection of large amounts of data is known as the Big Data Repository and is not part of the present document. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 33 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.3.2 Detailed Descriptions | The DMR CSF provides the capability to store data such as Application data, subscriber information, location information, device information, semantic information, communication status, access permission, etc. The data stored by the DMR CSF enables management of the data and provides the foundation of Big Data. The following are examples of DMR CSF functionalities: • Ability to store data in an organized fashion so it is discernible. This includes storage of contextual information such as data types, semantic information, time stamps, location, etc., to complement the data stored in order to access and search the data based on a set of parameters. This is part of data semantics capability which is not part of the present document. • Provides the means to aggregate data received from different entities. • Ability to grant access to data from remote CSEs and AEs based on defined access control policies, and trigger data processing based on data access. • Ability to provide the means to perform data analytics on large amount of data to allow service providers to provide value-added services. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.4 Device Management | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.4.1 General Concepts | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.4.1.0 Overview | The Device Management (DMG) CSF provides management of device capabilities on MNs (e.g. M2M Gateways), ASNs and ADNs (e.g. M2M Devices), as well as devices that reside within an M2M Area Network. Application Entities (AE) can manage the device capabilities on those Nodes by using the services provided by the DMG CSF alleviating the need for the AE to have knowledge of the technology specific protocols or data models. While the AE does not require an understanding of the technology specific protocols or data models, this information is provided to the AE so that an AE can utilize this information for administrative purposes (e.g. diagnostics, troubleshooting). In order to manage the CSE and device capabilities of the MNs, ASNs and ADNs, the DMG can utilize existing technology specific protocols (e.g. BBF TR-069 [i.2], OMA-DM [i.3], and LWM2M [i.4]) in addition to resource operations across the Mcc and Mca reference points. When non-oneM2M protocols are used to manage oneM2M Nodes the DMG of an IN or MN translates or adapts the management related oneM2M requests to/from the corresponding technology via a Management Adapter. The existing technology then supports operations between Management Servers and Management Clients. Architectural details regarding the use of non-oneM2M technology protocols is provided in clause 6.2.4.1.1. The architectural model for the native Device Management uses the generic oneM2M architecture and reference points. Both Device Management options (native oneM2M or non-oneM2M) use resources maintaining information and relationships that are specific to Device Management (i.e. Device Management Resources), as well as general purpose resources. Device Management Resources maintain information and relationships used to: • Manage technology specific data model objects via a Management Server which requires the information necessary to identify and access the Management Server. • Invoke the security mechanism of the Management Server in order to authorize access to the technology specific data model objects. Procedures for managing Device Management Resources are further detailed in clause 10.2.8 and apply to both Device Management options. For Device Management using external technologies, at most one Management Server is able to Create, Delete or Update addressable elements of a Management Resource. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 34 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.4.1.1 Device Management using other existing technologies | 6.2.4.1.1.1 Architecture When non-oneM2M technologies are used to manage devices oneM2M resource operations need to be adapted to the specific protocol used (e.g. BBF TR-069 [i.2], OMA-DM [i.3], and LWM2M [i.4]). In order to perform the translation and adaptation functions, the DMG has a functional component termed the Management Adapter (figure 6.2.4.1.1.1-1). The Management Adapter in the DMG of the management server hosting M2M Node (e.g. IN-DMG-MA) performs the adaptation between the DMG and Management Servers using the ms interface; while the Management Adapter in the DMG of the management client hosting M2M Node (e.g. MN-DMG-MA or ASN-DMG-MA) performs translation and adaptation between the DMG and the Management Client using the la interface. Only one Management Adapter is shown in the DMG although it can interact with Management Server using different technology specific protocols. The interface between Management Server and Management Client (figure 6.2.4.1.1.1-1) is the mc interface which is subject to the technology specific protocol that is used (e.g. BBF TR-069 [i.2] or LWM2M [i.4]). The mc interface is technology dependent and is outside the scope of the present document. The DMG in the MNs or ASNs can be used to manage devices in the M2M Area Network. In this case, the DMG is deployed with proxy functionality that interacts with the Proxy Management Client using the mp interface. The mp interface is technology dependent and is outside the scope of the present document. The Management Server and Management Client can be implemented as an entity external to the Node or they can be implemented as an entity embedded within the Node (figure 6.2.4.1.1.1-1). The Management Server and the Management Client are located on the boundary of the Node to indicate this situation as well as to depict that an IN can utilize multiple Management Servers from various M2M and Network Service Providers. Figure 6.2.4.1.1.1-1: Device Management Architecture ETSI ETSI TS 118 101 V4.15.0 (2022-09) 35 (oneM2M TS-0001 version 4.15.0 Release 4) 6.2.4.1.1.2 Management Server Interaction The DMG CSF in the IN has the capability to utilize Management Servers from technology specific protocols (e.g. BBF TR-069 [i.2], OMA DM [i.3], LWM2M [i.4]) to implement the Device Management functions. The Management Adapter in the DMG of the management server hosting M2M Node (e.g. IN-DMG-MA) communicates with the Management Server using the ms interface of the Management Server. Note that ms interface is outside the scope of the present document. The IN-DMG-MA takes the following roles: • Protocol Translation between DMG and the Management Server: - After the DMG receives the requests from the request Originator, the Management Adapter in the DMG of the management server hosting M2M Node (e.g. IN-DMG-MA) translates the requests from the request Originator to requests with associated identifiers that can be understood by the Management Server. Likewise, the Management Adapter in the DMG of the management server Host (e.g. IN-DMG- MA) translates events from the Management Server and delivers the events to M2M Entities (e.g. AE, CSE) that are subscribed to the event. When the Management Server is embedded within the DMG, the Management Adapter translates the request and accepts events in the protocol understood by the Management Client. • Interaction with the Management Server: - By using ms interface, the Management Adapter in the DMG of the management server hosting M2M Node (e.g. IN-DMG-MA) can communicate with the Management Server. This is for delivering the requests from the request Originator to the Management Server, or receiving information from the Management Server that will be notified to subscribing M2M Entities (e.g. AE, CSE). The communication between the Management Adapter and the Management Server requires an establishment of a session which provides security dimensions for Access Control, Authentication, Non-repudiation, Data confidentiality, Communication security, Data integrity and Privacy. The Management Adapter in the DMG of the management server Host (e.g. IN-DMG-MA) can utilize a policy that defines when a session with the Management Server is established and torn down. • Management Server selection: - When the Management Adapter in the DMG of the management server hosting M2M Node (e.g. IN- DMG-MA) communicates with multiple Management Servers that have different level of access control privileges to resources from the Management Server,the Management Adapter selects the proper Management Server that has the access control privileges to perform the management requests. The access control policy information for resources from Management Servers may be discovered using the ms interface. • Discovery of technology specific data model objects: - When the Management Adapter in the DMG of the management server Host (e.g. IN-DMG-MA) maintains information (i.e. metadata, values) of the technology specific data model objects managed by a Management Server using the ms interface, the Management Adapter will be capable of discovering and keep up to date the technology specific data model object's information that are managed by the DMG and a Management Server. A Management Server can be located in the Underlying Network using the Mcn reference point as depicted in figure 6.2.4.1.1.2-1 or the Management Server can be located in the M2M Service Layer as depicted in figure 6.2.4.1.1.2-2. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 36 (oneM2M TS-0001 version 4.15.0 Release 4) Figure 6.2.4.1.1.2-1: Management Server in Underlying Network Figure 6.2.4.1.1.2-2: Management Server in M2M Service Layer The ms interface is functionally the same interface regardless if the Management Server resides in the Underlying Network or the Service Layer. However, the access control privileges that the Management Server has for resources from the technology specific protocol can be different depending whether the Management Server resides in the Underlying Network or in the Services Layer. For example, in figure 6.2.4.1.1.2-1, the Management Server in the Underlying Network controls access of the exposed resources from the technology specific protocol, while, in the figure 6.2.4.1.1.2-2, the Management Server in the M2M Service Layer controls access to the resources. 6.2.4.1.1.3 Management Server - Access Permissions When an operation on an M2M Service Layer Resource is performed and if the access to the Resource is granted and the operation for the Resource utilizes a Management Server external to the service layer, the DMG CSF of the management server Host selects one or more among the authenticated Management Servers necessary to access the requested resources. The procedure for the selection of Management Servers is implementation specific and outside the scope of the present document. The DMG CSF management functions that cause impacts to the Underlying Network utilize access permissions that are delegated from the provider of the network service layer. 6.2.4.1.1.4 Management Server - External management object discovery The Management Adapter of the Management Server Host (e.g. IN-DMG-MA) discovers information of the technology specific data model objects managed by a Management Server using the ms interface. The discovery of this information includes: • The M2M devices, devices in the M2M Area Network and M2M Applications to which the Management Server has access. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 37 (oneM2M TS-0001 version 4.15.0 Release 4) • The metadata associated with the technology specific data model objects associated the M2M devices, devices in the M2M Area Network and M2M Applications. This metadata includes items such as the supported data/object model. The Management Adapter of the Management Server Host (e.g. IN-DMG-MA) is capable of being kept up-to-date of the changes in the M2M Devices, devices in the M2M Area Network and M2M Applications or the metadata of the technology specific data model objects associated with those entities. In addition, the Management Adapter of the Management Server Host can maintain the value associated technology specific data model objects, associated the M2M devices, devices in the M2M Network and M2M Applications. 6.2.4.1.1.5 Management Client Interaction The DMG CSF in the Management Client Host (e.g. MN or ASN) can use the Management Client from existing management technologies (e.g. BBF TR-069 [i.2], OMA DM [i.3], LWM2M [i.4]) to implement the Device Management functions. The Management Adapter in the Management Client Host (e.g. MN-DMG-MA, ASN-DMG-MA) communicates with the Management Client using the la interface (e.g. DM-7, 8, 9 ClientAPI in OMA DM [i.3]) that is provided by the Management Client. Note that the la interface is outside the scope of the present document. The Management Adapter in the Management Client Host takes the following roles: • Interaction with the Management Client: - By using la interface, the Management Adapter can communicate with the Management Client to discover the technology specific data model objects supported by the Management Client. • Mapping between the DMG and Management Client: - After the Management Adapter discovers the technology specific data model objects supported by the Management Client; the Management Adapter performs the mapping between the technology specific data model objects to resources. The DMG in the Management Client Host can create those resources in the Management Server hosting CSE, and the resources can be used by the device management AE to manage the device capabilities pertaining to the managed node. Figure 6.2.4.1.1.5-1: Management Client Interaction using "Ia" interface |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.4.2 Detailed Descriptions | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.4.2.0 Overview | The DMG CSF provides capabilities for the purpose of managing M2M Devices/Gateways as well as devices in M2M Area Networks. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 38 (oneM2M TS-0001 version 4.15.0 Release 4) Figure 6.2.4.2.0-1: Device Management Entities and Functions Such capabilities include: • Device Configuration Function (DCF): This function includes the configuration of the capabilities of the M2M Device, M2M Gateway or device in the M2M Area Network. • Device Diagnostics and Monitoring Function (DDMF): This function includes the troubleshooting through the use of diagnostic tests and retrieval of operational status and statistics associated with the M2M Device, M2M Gateway or device in the M2M Area Network. • Device Firmware Management Function (DFMF): This function provides the software lifecycle management for firmware components and associated artefacts for the M2M Device, M2M Gateway or device in the M2M Area Network. • Device Topology Management Function (DTMF): This function provides the management of the topology of the M2M Area Network. An M2M Area Network is comprised of ADNs and other devices in the M2M Area Network. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.4.2.1 Device Configuration Function | The Device Configuration Function (DCF) provides the configuration of device capabilities that are necessary to support M2M Services and AEs in M2M Devices, M2M Gateways or devices in an M2M Area Network. These device configuration capabilities include: • Discovery of a device's management objects and attributes. • Ability to enable or disable a device capability. • Provisioning configuration parameters of a device. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.4.2.2 Device Diagnostics and Monitoring Function | The Device Diagnostics and Monitoring Function (DDMF) permits the troubleshooting of device capabilities that are necessary to support M2M Services and AEs in M2M Devices, M2M Gateways or devices in an M2M Area Network. These device diagnostic and monitoring capabilities include: • Configuration of diagnostics and monitoring parameters on the device. • Retrieval of device information that identifies a device and its model and manufacturer. • Retrieval of device information for the software and firmware installed on the device. • Retrieval of information related to a battery within the device. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 39 (oneM2M TS-0001 version 4.15.0 Release 4) • Retrieval of information associated with the memory in use by a device. • Retrieval of the event logs from a device. • Device reboot diagnostic operation. • Device factory reset diagnostic operation. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.4.2.3 Device Firmware Management Function | The Device Firmware Management Function (DFMF) provides lifecycle management for firmware associated with a device. Device firmware is comprised of firmware modules and artefacts (e.g. configuration files) that are maintained on a device. A device can maintain more than one firmware image and the capability to manage individual firmware images. The firmware lifecycle includes actions to download, update or remove a firmware image. In addition, firmware could be downloaded and updated within the same action. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.4.2.4 Device Topology Management Function | The Device Topology Management Function (DTMF) is a function that is specific to M2M Gateways where an M2M Gateway maintains zero or more M2M Area Networks. These device topology management capabilities include: • Configuration of the topology of the M2M Area Network. • Retrieval of information related to the devices attached to the M2M Area Network. • Retrieval of information that describes the transport protocol associated with the M2M Area Network. • Retrieval of information that describes the characteristics associated with online/offline status of devices in the M2M Area Network. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.5 Discovery | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.5.1 General Concepts | The Discovery (DIS) CSF searches information about applications and services as contained in attributes and resources. The result of a discovery request from an Originator depends upon the filter criteria and is subject to access control policy allowed by M2M Service Subscription. An Originator could be an AE or another CSE. The scope of the search could be within one CSE, or in more than one CSE. The discovery results are returned back to the Originator. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.5.2 Detailed Descriptions | The DIS CSF uses the Originator provided filter criteria (e.g. a combination of keywords, identifiers, location and semantic information) that can limit the scope of information returned to the Originator. The discovery request indicates the address of the resource where the discovery is to be performed. Upon receiving such request, the DIS CSF discovers, identifies, and returns the matching information regarding discovered resources according to the filter criteria. A successful response includes the discovered information or address(es) pertaining to the discovered resources. In the latter case the Originator can retrieve the resources using such discovered address. Based on the policies or Originator request, the CSE which received the discovery request can forward the request to other registered ASN-CSEs, MN-CSEs or IN-CSEs. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 40 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.6 Group Management | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.6.1 General Concepts | The Group Management (GMG) CSF is responsible for handling group related requests. The request is sent to manage a group and its membership as well as for the bulk operations supported by the group. When adding or removing members to/from a group, it is necessary to validate whether the group member complies with the purpose of the group. Bulk operations include read, write, subscribe, notify, device management, etc. Whenever a request or a subscription is made via the group, the group is responsible for aggregating its responses and notifications. The members of a group can have the same role with regards to access control policy control towards a resource. In this case, access control is facilitated by grouping. When the Underlying Network provides broadcasting and multicasting capability, the GMG CSF is able to utilize such capability. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.6.2 Detailed Descriptions | The GMG CSF enables the M2M System to perform bulk operations on multiple devices, applications or resources that are part of a group. In addition, the GMG CSF supports bulk operations to multiple resources of interest and aggregates the results. It facilitates access control based on grouping. When needed and available, the GMG CSF can leverage the existing capabilities of the Underlying Network including broadcasting/multicasting. When facilitating access control using a group, only members with the same access control policy towards a resource are included in the same group. Also, only AEs or CSEs which have a common role with regards to access control policy are included in the same group. This is used as a representation of the role when facilitating role based access control. The service functions supported by the GMG CSF are as follows: • Handles the requests to create, retrieve, update, and delete a group. An AE or a CSE may request the creation/retrieve/update/deletion of a group as well as the addition and deletion of members of the group. • Creates one or more groups in CSEs in any of the Nodes in oneM2M System for a particular purpose (e.g. facilitation of access control, device management, fan-out common operations to a group of devices, etc.). • Handles the requests to retrieve the information (e.g. address, metadata, etc.) of a group and its associated members. • Manages group membership and handles requests to add or remove members to and from a group's member list. A member may belong to one or more groups. A group may be a member of another group. When new members are added to a group, the GMG CSF validates if the member complies with the purpose of the group. • Leverages the capabilities of other CSFs in order to fulfill the functionalities supported by the GMG CSF service functions. Examples include: Security CSF for authentication and authorization. • Forwards requests to all members in the group. In case the group contains another group as a member, the forwarding process is done recursively, i.e. the nested group forwards the request to its members. After forwarding the request to all members in the group, the GMG CSF generates an aggregated response by aggregating the corresponding responses from the Group members. • Supports subscriptions to individual groups. Subscriptions to a group is made only if the subscriber is interested in all members of the group. If subscription to a group is made, the GMG CSF aggregates the notifications from the group members, and notifies the subscriber with the aggregated notification. Responses and event notifications relevant to a subscription may be selectively filtered by filtering criteria. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.7 Location | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.7.1 General Concepts | The Location (LOC) CSF allows AEs to obtain geographical location information of Nodes (e.g. ASN, MN) for location-based services. Such location information requests can be from an AE residing on either a local Node or a remote Node. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 41 (oneM2M TS-0001 version 4.15.0 Release 4) NOTE: Geographical location information can include more than simply the longitude and the latitude information. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.7.2 Detailed Descriptions | The LOC CSF obtains and manages geographical location information based on requests from AEs residing on either a local Node or a remote Node. The LOC CSF interacts with any of the following: • a location server in the Underlying Network; • a GPS module in an M2M device; or • information for inferring location stored in other Nodes. In order to update the location information, an AE can configure an attribute (e.g. update period). Based on such defined attributes, the LOC CSF can update the location information using one of the location retrieval mechanisms listed above. NOTE: The location technology (e.g. Cell-ID, assisted-GPS, and fingerprint) used by the Underlying Network depends on its capabilities. The functions supported by the LOC CSF are as follows: • Requests other Nodes to share and report their own or other Nodes' geographical location information with the requesting AEs. • Provides means for protecting the confidentiality of geographical location information. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.8 Network Service Exposure, Service Execution and Triggering | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.8.1 General Concepts | The Network Service Exposure, Service Execution and Triggering (NSSE) CSF manages communications with the Underlying Networks for accessing network service functions over the Mcn reference point. The NSSE CSF uses the available/supported methods for service "requests" on behalf of AEs. The NSSE CSF shields other CSFs and AEs from the specific technologies and mechanisms supported by the Underlying Networks. NOTE: The NSSE CSF provides adaptation for different sets of network service functions supported by various Underlying Networks. The network service functions provided by the Underlying Network include service functions such as, but not limited to, device triggering, small data transmission, location notification, policy rules setting, location queries, IMS services, device management. Such services do not include the general transport services. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.8.2 Detailed Descriptions | The NSSE CSF manages communication with the Underlying Networks for obtaining network service functions on behalf of other CSFs, remote CSEs or AEs. The NSSE CSF uses the Mcn reference point for communicating with the Underlying Networks. The M2M System allows the Underlying Networks to control network service procedures and information exchange over the Underlying Networks while providing such network services. For example, some Underlying Network can choose to provide the network services based on control plane signalling mechanisms. Other CSFs in a CSE that need to use the services offered by the Underlying Network use the NSSE CSF. The service functions supported by the NSSE CSF are as follows: • The NSSE CSF shields other CSFs and AEs from the specific technology and mechanisms supported by the Underlying Networks. NOTE: The NSSE CSF provides adaptation for different sets of network service functions supported by various Underlying Networks. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 42 (oneM2M TS-0001 version 4.15.0 Release 4) • The NSSE CSF maintains the necessary connections and/or sessions over the Mcn reference point, between the CSE and the Underlying Network when local CSFs are in need of a network service. • The NSSE CSF provides information to the CMDH CSF related to the Underlying Network so the CMDH CSF can include that information to determine proper communication handling. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.9 Registration | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.9.1 General Concepts | The Registration (REG) CSF processes a request from an AE or another CSE to register with a Registrar CSE in order to allow the registered entities to use the services offered by the Registrar CSE. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.9.2 Detailed Descriptions | Registration is the process of delivering AE or CSE information to another CSE in order to use M2M Services. An AE on an ASN, an MN or an IN performs registration locally with the corresponding CSE in order to use M2M services offered by that CSE. An AE on an ADN performs registration with the CSE on an MN or an IN in order to use M2M services offered by that CSE. An IN-AE performs registration with the corresponding CSE on an IN in order to use M2M services offered by that IN CSE. An AE can have interactions with its Registrar CSE (when it is the target CSE) without the need to have the Registrar CSE register with other CSE. The CSE on an ASN performs registration with the CSE in the MN in order to be able to use M2M Services offered by the CSE in the MN. As a result of successful ASN-CSE registration with the MN-CSE, the CSEs on the ASN and the MN establish a relationship allowing them to exchange information. The CSE on an MN performs registration with the CSE of another MN in order to be able to use M2M Services offered by the CSE in the other MN. As a result of successful MN-CSE registration with the other MN-CSE, the CSEs on the MNs establish a relationship allowing them to exchange information. The CSE on an ASN or on an MN perform registration with the CSE in the IN in order to be able to use M2M Services offered by the CSE in the IN. As a result of successful ASN/MN registration with the IN-CSE, the CSEs on ASN/MN and IN establish a relationship allowing them to exchange information. Following a successful registration of an AE to a CSE, the AE is able to access, assuming access privilege is granted, the resources in all the CSEs that are potential targets of request from the Registrar CSE. The capabilities supported by the REG CSF are as follows: • ability for AE to register to its Registrar CSE where the hop count is zero, as per table 6.4-1; • ability for CSE to register to its Registrar CSE where the hop count is zero, as per table 6.4-1; • ability for an ASN-CSE/MN-CSE or ADN-AE to register association of its M2M-Ext-ID (if available) with its CSE-ID or AE-ID (see clause 7.1.8); • ability for an ASN-CSE/MN-CSE or ADN-AE to register association of its Trigger-Recipient-ID (if available) with its CSE-ID or AE-ID (see clause 7.1.10). When Trigger-Recipient-ID is not present, it is assumed that the ADN-AE or CSE is not able to receive triggers. NOTE: Such registrations are applicable to a single M2M Service Provider Domain. Registration information for a Node includes: • Identifier of the Node. • Reachability schedules; which are elements of a Node's policy, and specify when messaging can occur between Nodes. Reachability schedules can be used in conjunction with other policy elements. When reachability schedules are not present in a Node then that Node is expected to be always reachable. • Managing connection state of communication channel to the registered AE or CSE. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 43 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.10 Security | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.10.1 General Concepts | The Security (SEC) CSF comprises the following functionalities: • Sensitive data handling. • Security administration. • Security association establishment. • Remote security provisioning. • Identification and authentication. • Authorization. • Identity management. Sensitive data handling functionality in the SEC CSF protects the local credentials on which security relies during storage and manipulation. Sensitive data handling functionality performs other sensitive functions such as security algorithms. This functionality is able to support several cryptographically separated security environments. Those secure environments are accessible via the Mcs reference point. This reference point abstracts different types of secure environments and is defined in ETSI TS 118 116 [9]. Security management capabilities are provided by the Security Administration functionality as specified in ETSI TS 118 103 [2]. NOTE: ASM and DMG CSFs do not include security management capabilities of the SEC CSF. Security administration functionality enables services such as the following: • Creation and administration of dedicated security environment supported by Sensitive Data Handling functionality. • Post-provisioning of a root credential protected by the security environment. • Provisioning and administration of subscriptions related to M2M Common Services and M2M Application Services. Security association establishment functionality establishes security association between corresponding M2M Nodes, in order to provide services such as confidentiality and integrity. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.10.2 Detailed Descriptions | The functionalities supported by the SEC CSF are as follows: • Sensitive data handling: - Provides the capability to protect the local credentials on which security relies during storage and manipulation. - Extends sensitive data handling functionality to other sensitive data used in the M2M Systems such as subscription related information, access control policies and personal data pertaining to individuals. - Performs other sensitive functions as well, such as security algorithms running in cryptographically separated secure environments. • Security administration: - Creates and administers dedicated secure environment supported by sensitive data handling functionality. - Post-provisions master credentials protected by the secure environment. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 44 (oneM2M TS-0001 version 4.15.0 Release 4) NOTE 1: The secure environment can also be pre-provisioned with a master credentials prior to deployment; therefore this capability is not always required. Post-provisioning is required when secure remote provisioning needs to be performed or re-initiated after deployment. • Provisioning and administration of subscriptions related to M2M Services and M2M application services. Besides the associated master credentials, a subscription includes other information classified as sensitive data such as authorization roles and identifiers for access control management. • Security association establishment: - Establishes security associations between corresponding M2M Nodes in order to provide specific security services (e.g. confidentiality, integrity, or support for application level signature generation and verification) involving specified security algorithms and sensitive data. This involves key derivation based on provisioned master credentials. This functionality of the SEC CSF is mandatory when security is supported. • MAF-based security association establishment: - These security frameworks use a M2M Authentication Function (MAF) to provide authentication and distribution of symmetric key for use by a Source End-Point initiating establishment of the symmetric key, and one or more target end-points. The symmetric key can be used in one of Security Association Establishment Framework, End-to-End Security of Data (ESData) and End-to-End Security of Primitives (ESPrim). • End-to-End Security of Data (ESData) and Primitives (ESPrim): - End-to-End Security of Primitives (ESPrim) allows a Hosting CSE or AE to authenticate the Originator of a request primitives that are handled by other CSEs. ESPrim also provides confidentiality and integrity protection of these request and response primitives. End-to-End Security of Data (ESData) provides an interoperable framework for protecting data such that it can be transported via transit CSEs which do not need to be trusted. • Remote Security Provisioning: - Remote Security Provisioning Frameworks (RSPFs) enable an M2M Enrolment Function (MEF) to provision credentials to an Enrolee, which is a CSE or AE, as part of the Enrolment of the Enrolee to an M2M SP or third party M2M Trust Enabler (MTE). The credentials are either a symmetric key shared by the Enrolee and an Enrolment Target or Certificate(s) for which the Enrolee knows the corresponding private key, and a set of trust anchors for authenticating the M2M SP or MTE's MAF or other entities enrolled with the M2M SP or MTE. • Authorization: - Role Based Access Control (RBAC) allows the Hosting CSE to authorize accesses on resources according to the roles assigned to the Originators. - Token Based Access Control allows the Hosting CSE to authorize accesses on resources according to the authorization information in tokens provided by the Originators. - Dynamic Authorization provides an interoperable framework for an Originator to be dynamically issued with temporary permissions providing the Originator with access to one or more resources on one or more CSEs at runtime. - The entire authorization function can be split into four sub-functions: Policy Enforcement Point (PEP), Policy Decision Point (PDP), Policy Retrieval Point (PRP) and Policy Information Point (PIP). Distributed Authorization provides an interoperable framework which allows PEP, PDP, PRP and PIP to be distributed in different CSEs. - Privacy Policy Manager (PPM) provides a standardized list of privacy attribute value pairs, automatic comparison of a user''s privacy preferences with applications privacy policies and management of related access control policies. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 45 (oneM2M TS-0001 version 4.15.0 Release 4) • Identity management: - Identity management in the oneM2M context covers the lifecycle (creation, storage and destruction) of identifiers related to oneM2M entities. NOTE 2: This functionality is not part of the present release. Detailed functionalities are described in the ETSI TS 118 103 [2]. Sensitive security functions and information within a node are protected by local Secure Environments (SEs). A Secure Environment is an abstraction of a secure area, within a computing system on a node (ADN, ASN, MN or IN), that provides a defined level of protection for code and data at rest, i.e. in storage, and in use, i.e. during process execution or data manipulation, as specified in ETSI TS 118 116 [9]. An SE provides resources for the purposes described above that can be manipulated via the Mcs reference point. Details on the SE resources can be found in ETSI TS 118 116 [9]. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.11 Service Charging and Accounting | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.11.1 General Concepts | The Service Charging and Accounting (SCA) CSF provides charging functions for the Service Layer. It supports different charging models which also include online real time credit control. The SCA CSF manages service layer charging policies and configuration capturing service layer chargeable events, generating charging records and charging information. The SCA CSF can interact with the charging System in the Underlying Network also. The SCA CSF in the IN-CSE handles the charging information. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.11.2 Detailed Descriptions | The SCA CSF performs information recording corresponding to a chargeable event based on the configured charging policies. The SCA CSF sends the charging information transformed from the specific recorded information to the billing domain by the use of a standard or proprietary interface for charging purposes. The SCA CSF supports "independent service layer charging" and "correlated charging with the Underlying Network" charging system. For independent service layer charging, only charging functions in the M2M service layer are involved. For correlated charging, charging functions in both the service layer and the Underlying Network are involved. The SCA CSF supports one or multiple charging models, such as the following: • Subscription based charging: A service subscriber is charged based on service layer subscriptions. • Event based charging: Charging is based on service layer chargeable events. A chargeable event refers to the discrete transactions. For example, an operation on data (Create, Update, Retrieve) can be an event. Chargeable event can also be timer based. Chargeable events are configurable to initiate information recording. More than one chargeable event can be simultaneously configured and triggered for information recording. The Service Layer charging system consists of the following logical functions: • Charging management function: This function handles charging related policies, configurations, function communications and interacting with the charging system in the Underlying Network. Charging related policies. • Charging triggering function: This function resides in the service layer. It captures the chargeable event and generates recorded information for charging. Recorded information may contain mandatory and optional elements. • Offline charging function: This function handles offline charging related operations. Offline charging does not affect services provided in real time. Charging triggering information is generated at the CSFs where the chargeable transaction happens. The offline charging function generates service charging records based on recorded information. A service charging record is a formatted collection of information about a chargeable event (e.g. amount of data transferred) for use in billing and accounting. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 46 (oneM2M TS-0001 version 4.15.0 Release 4) NOTE: Charging triggering and offline charging function are based on charging policies. The system may record information for other purposes such as for event logging. Some of such information may be applicable for charging purposes. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.12 Subscription and Notification | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.12.1 General Concepts | The Subscription and Notification (SUB) CSF provides notifications pertaining to a subscription that tracks event changes on a resource (e.g. deletion of a resource). A subscription to a resource is initiated by an AE or a CSE, and is granted by the Hosting CSE subject to access control policies. During an active resource subscription, the Hosting CSE sends a notification regarding a notification event to the address(es) where the resource subscriber wants to receive it. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.12.2 Detailed Descriptions | The SUB CSF manages subscriptions to resources, subject to access control policies, and sends corresponding notifications to the address(es) where the resource subscribers want to receive them. An AE or a CSE is the subscription resource subscriber. AEs and CSEs subscribe to resources of other CSEs. A subscription Hosting CSE sends notifications to the address(es) specified by the resource subscriber when modifications to a resource are made. The scope of a resource subscription includes tracking changes of attribute(s) and direct child resource(s) of the subscribed-to resource. It does not include tracking the change of attribute(s) of the child resource(s). Furthermore, the scope includes tracking operations on attributes and direct child resources, but does not include tracking operations on attributes of child resources. Each subscription may include notification policies that specify which, when, and how notifications are sent. These notification policies may work in conjunction with CMDH policies. A subscription is represented as resource subscription in the CSE resource structure. The functions supported by the SUB CSF are as follows: • Inclusion of the resource subscriber ID, the hosting CSE-ID and subscribed-to resource address(es) per resource subscription request. It may also include other criteria (e.g. resource modifications of interest and notification policy) and the address(es) where to send the notifications. • Ability to subscribe to a single resource via a single subscription, or subscribe to multiple resources via a single subscription when they are grouped and represented as a single group resource. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.13 Transaction Management | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.13.1 General Concepts | The Transaction Management (TMG) CSF assists applications with the atomic and consistent processing of oneM2M request primitives. The TMG CSF supports scheduling of a transaction, locking and unlocking of resources targeted by a transaction, the atomic and consistent execution of a transaction on targeted resources, the committal of successful transaction results, and the abort and rollback of non-successful transactions. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.13.2 Detailed Descriptions | The TMG CSF uses an Originator provided transaction consisting of set of multiple oneM2M request primitives targeting multiple oneM2M resources. The targeted resources may reside on one or more CSEs. The TMG CSF handles the atomic and consistent processing of the set of request primitives such that all the requests are completed successfully. If one or more requests do not complete successfully, then the TMG CSF handles rolling back all the targeted resources to the state they were in prior to the transaction being processed. NOTE: Rollback of a transaction after it is committed (commonly referred to as revoking or reversing) is not supported by the TMG CSF. Only rollback of a transaction before it is committed is supported. The TMG CSF also supports the capability to schedule the execution of the oneM2M request primitives defined within a transaction. The TMG CSF may use an Originator specified transaction lock time, execution time and/or committal time to schedule when the processing of the transaction is to take place. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 47 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.14 Semantics | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.14.1 General Concepts | The Semantics (SEM) CSF enables applications to manage semantic information and provides functionalities based on this information. Thus the SEM CSF brings value-added features related to the meaning of data and resources. The SEM CSF functionality is based on semantic descriptions and supports features such as: annotation, resource filtering and discovery, querying, validation, mash-up, reasoning, mapping, analytics, etc. The SEM CSF also provides input for Access Control applied to semantic content and is responsible for the management of ontologies. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.14.2 Detailed Descriptions | The SEM CSF uses semantic descriptions pertaining to resources based on ontologies which annotate the corresponding resources. The SEM CSF handles the processes of discovery of resources and querying of semantic information, respectively, based on syntactic, semantic and structural information contained in semantic content data (such as RDF triples). When executing semantic operations and accessing RDF triple content, the SEM CSF uses access control information applicable to resources. The SEM CSF enables also the creation, execution and result retrieval of functions based on semantic mashup, the validation of semantic content, the use and management of ontologies, and the semantic mapping between ontologies. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.15 Time Management | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.15.1 General Concepts | The Time Management CSF (TIMG CSF) provides capabilities to enable entities in the M2M system to synchronize their current time values with one another. Due to various limitations and constraints of some M2M deployments, some M2M entities (e.g. resource constrained devices) may lack support for synchronizing their current time values with the current time values of other entities in the M2M system. In addition, existing time synchronization mechanisms such as NTP, PTP, and GPS may not always be available and /or may not be best suited for all types of M2M system deployments. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.15.2 Detailed Descriptions | The Time Management CSF (TIMG CSF) supports a set of time management capabilities for M2M entities to select and use to help them synchronize and manage their current time values with respect to one another. Without adequate time synchronization, entities hosted on different nodes in the M2M system may be unable to maintain time synchronization with one another. For example, a lack of synchronization between AEs and/or CSEs can result in one AE or CSE not sending a message to another AE or CSE in the proper scheduled time window. In another example, AEs timestamping data (e.g. sensor measurements) which they share with other AEs may result in information which is incorrectly processed or misinterpreted. The TIMG CSF enables a CSE to make its current time value available such that other entities can retrieve and use it to synchronize their current time value to the CSE's. The TIMG CSF also supports the capability to send out time beacon notifications that include the current time value of a CSE to other entities in the M2M system such that they can use it to synchronize their current time value to the CSE's. The TIMG CSF also supports the capability to perform time compensation on behalf of other entities by adjusting time related metadata sourced from or targeted towards these entities such that they do not need to perform time management operations themselves. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.16 Session Management | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.16.1 General Concepts | The Session Management CSF (SMG CSF) provides capabilities to establish, configure and manage sessions between oneM2M entities (i.e. session endpoints). These sessions define session descriptions and policies used to enable message exchanges between the session endpoints. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 48 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.16.2 Detailed Descriptions | In the present document, the SMG CSF supports managing two types of sessions: 1) An end-to-end QoS session - The SMG CSF enables establishment and configuration of a session that is used to ensure a required level of end-to-end QoS is maintained for the end-to-end exchange of oneM2M primitives between designated oneM2M entities. This session is configured with policies that define QoS requirements. Once configured, the SMG CSF uses these policies to actively manage the exchange of oneM2M primitives between the designated oneM2M entities. For example, the SMG CSF uses the session policies to configure and manage the establishment and tear-down of QoS session(s) in underlying network(s) used by the oneM2M entities. The SMG CSF also uses the session policies to manage the scheduling and store-and-forwarding of oneM2M request and response primitives exchanged between the oneM2M entities over oneM2M defined reference points and protocols. 2) A multimedia session - The SMG CSF enables AEs to exchange and agree upon a session description defining the configuration of a multimedia session that the AEs then establish between themselves. Once the AEs agree upon the session description via the SMG CSF, the AEs then establish the multimedia session and exchange messages via the multimedia session using non-oneM2M defined reference points and protocols. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.17 Process Management | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.17.1 General Concepts | Many IoT use cases (e.g. home automation, manufacturing, logistics and agriculture) require processes to be performed. The processes typically involve operations such as collecting data produced by sensor devices, analysing this data, and performing actions such as issuing a command to actuator device(s) or sending a notification to an application when certain values or thresholds for the data have been met. The Process Management (PMG) CSF provides capabilities for an AE to define and offload a process to the PMG CSF. Offloading a process to the PMG CSF can simplify and reduce overhead on an AE. Offloading a process can also help reduce load on a network by reducing the number of messages exchanged between an AE and CSE. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.2.17.2 Detailed Descriptions | Processes supported by the PMG CSF consist of one or more states. Each state includes state transition criteria used by the PMG CSF to control transitioning between the different states of a process. While in a particular state of a process, the PMG CSF monitors a set of action criteria used to control if/when the PMG CSF performs an action defined for the state. The action criteria consist of subject and dependency resources, conditions to be met for these resources, and one or more defined actions. When the conditions on the subject and dependency resources are met, the PMG CSF performs the one or more defined actions. In addition, an AE can monitor a process that is managed by the PMG CSF. For example, an AE can subscribe and receive notifications from the PMG CSF when it transitions between different states in a process. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.3 Security Aspects | oneM2M TR-0008 [i.25] on Analysis of Security Solutions for the oneM2M System differentiates security domains related to the transport layer (Underlying Network), service layer (M2M common services) and Application Layer. It also considers possible trust scenarios involving these different security domains, and investigates countermeasures to threats that potentially affect the security of the M2M System. Each of the security domains may provide their own set of security capabilities. The oneM2M security solution shall provide configurable security services through an API for upper security domains to leverage, or enable the use of the exposed security features of other security domains when appropriate. As a result, beyond providing security solutions that protect the integrity of the M2M Service Layer, the oneM2M architecture exposes, through its APIs, further security services that are made available to M2M Applications. This enables M2M Applications to benefit from security solutions deployed in the M2M Service Architecture, without adding redundant and/or proprietary security solutions. NOTE: It remains the responsibility of M2M Application Service Providers to perform their own risk assessment process to identifying the specific threats affecting them and derive their actual security needs. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 49 (oneM2M TS-0001 version 4.15.0 Release 4) Security aspects are described in ETSI TS 118 103 [2]. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.4 Intra-M2M SP Communication | Within the same SP domain, a CSE shall perform registration with another CSE over the Mcc reference point to be able to use M2M Services offered by that CSE and to allow the other CSE to use its services. As a result of successful registration the CSEs establish a relationship allowing them to exchange information. An AE shall perform registration with a CSE in order to be able to use M2M Services offered by that CSE. As a result of successful AE registration, the AE and the CSE establish a relationship allowing them to exchange information. Table 6.4-1 shows which oneM2M entity types shall be able to register with which other entity types. Table 6.4-1: Entity Registration Originator (Registree) Receiver (Registrar) Registration Procedure ADN-AE MN-CSE, IN-CSE AE registration procedure see clause 10.2.2.2 ASN-AE ASN-CSE MN-AE MN-CSE IN-AE IN-CSE ASN-CSE MN-CSE, IN-CSE CSE registration procedure see clause 10.2.2.7 MN-CSE MN-CSE, IN-CSE The Originator (Registree) in table 6.4-1 requests the registration and the Receiver (Registrar) is responsible for verifying the request, and checking the authentication and authorization of the Originator in order to establish a peer relationship: • An AE shall not be registered to more than one CSE (ASN-CSE, MN-CSE or IN-CSE). • An ASN-CSE shall be able to be registered to at most one other CSE (MN-CSE or IN-CSE). • An MN-CSE shall be able to be registered to at most one other CSE (MN-CSE or IN-CSE). An MN-CSE shall be able to support only a single registration towards another MN-CSE or an IN-CSE. A concatenation (registration chain) of multiple uni-directional registrations shall not form a loop. E.g. two MN-CSEs A and B, cannot register with each other. Three MN-CSEs A, B and C, where A registers to B, and B registers to C, then C cannot register to A. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.5 Inter-M2M SP Communication | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.5.1 Inter M2M SP Communication for oneM2M Compliant Nodes | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.5.1.0 Overview | To enable M2M entities (e.g. CSE, AE) in different M2M Service Provider (SP) domains to communicate, configuration within the M2M domain determines if such a communication is allowed. If allowed, the M2M System shall support routing of the traffic across the originating M2M SP domain and within the target M2M SP domain. Communication between different M2M SPs which occurs over the reference point Mcc', is subject to business agreements. The offered functionality is typically a subset of the functionality offered over the Mcc reference point. Any interM2M SP communication in support of a request originating from one M2M SP domain shall be processed and forwarded through the Infrastructure Node of the originating M2M domain towards the Infrastructure Node of the target M2M SP domain and finally forwarded to its target CSE, if different from the Infrastructure Node. Hence the Infrastructure Node in both M2M domains shall be the exit and entry points, respectively, for all inter M2M SP communication traffic. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 50 (oneM2M TS-0001 version 4.15.0 Release 4) In this configuration approach, public DNS shall be used to support traffic routing for inter M2M SP communication in accordance with [i.13] his relies on public domain names being allocated to communicating CSE entities within the oneM2M architecture, and to whom access across domains is permitted through policies. To that effect, an M2M SP supporting inter- M2M SP communication shall ensure that the public domain names for the CSEs whose functionality is available across domains are held in its public DNS and shall always point to the IP address associated with the Infrastructure Node for the domain (being the entry point) for accessibility purposes. The M2M SP could optionally also have additional policies (e.g. black list or white list) that governs accessibility from other domains to CSE functionality located within its own domain. These policies are however out of scope of the present document. The public domain names of CSEs to whom access from other domains is allowed by policies, shall be created in the DNS of the M2M SP by the Infrastructure Node at registration time of these CSEs, and shall be removed at de-registration. DNS entries for CSEs can also be created/removed for registered CSEs at any time by the M2M SP through administrative means to handle dynamic policies. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.5.1.1 Public Domain Names and CSEs | To enable the usage of public DNSs as described above, there is a need for a naming convention for public names for CSEs. This naming convention facilitates the creation of the necessary entries of the public domain names of CSEs in the DNS by the infrastructure node. CSEs public domain names shall be a sub-domain of the Infrastructure Node's public domain name. This naming convention allows the Infrastructure Node to include the needed DNS entry corresponding to the CSE to whom access from other domains is allowed. This would typically occur when the CSE registers with the Infrastructure Node, subject to policies, or administratively. Accordingly, the structure of the public domain of the CSEs in IN/MN/ASN shall follow the following naming convention, which relies on the CSE identifier (CSE-ID) as part of the naming convention to facilitate the DNS entry creation: • Infrastructure Node CSE public domain name: <Infrastructure Node CSE Identifier>.<M2M Service Provider domain name>. • Middle Node CSE public domain name: <Middle Node CSE Identifier>.<Infrastructure Node public domain name>. • Application Service Node CSE public domain name: <Application Service Node CSE Identifier>.<Infrastructure Node public domain name>. Both the MN-CSE and the ASN-CSE public domain names are sub-domains of the Infrastructure Node public domain name. The A/AAAA records in the DNS, as per [i.7], [i.9] and [i.12] shall consist of the public domain name of the CSE and the IP address of the M2M Infrastructure Node, since the M2M Infrastructure Node is the entry point of the M2M Service Provider domain name where it belongs to. Note that entries in the public domain names of the three nodes depicted above do not imply that the actual CSE- Identifier allocated for that node has to be used in the DNS entry. Rather any name, including indeed the CSE Identifier for the node, can be used there as long as the entry resolves to the intended Node. EXAMPLE: These 3 host entries are valid entries in the DNS: - MN-CSEID.IN-CSEID.m2m.myoperator.org - node1.node2.m2m.myoperator.org - MN-CSEID.node22.m2m.myoperator.org ETSI ETSI TS 118 101 V4.15.0 (2022-09) 51 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.5.2 Inter M2M SP Generic Procedures | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.5.2.0 Overview | This clause describes the behaviour of the M2M Nodes in support of inter-M2M SP procedures. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.5.2.1 Actions of the Originating M2M Node in the Originating Domain | The Originator in the originating domain can be any M2M Node such as ADN, an MN, or an ASN, and shall send a request to the Registrar CSE to retrieve a resource located in another M2M SP domain. The Originator shall use any of the options defined in clause 9.3.1 to identify the target host and resource for that purpose. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.5.2.2 Actions of the Receiving CSE in the Originating Domain | The receiving CSE in the originating domain shall check if the addressed resource is locally available. If the addressed resource is not locally available, then the request shall be forwarded to the next CSE. If the receiving CSE is on an IN, it shall check if the addressed resource is locally available within its domain. If the addressed resource is not located within its own domain, then the IN shall perform a DNS lookup by using the target hostname provided in the RETRIEVE request. A successful DNS lookup shall return to the origin IN in the originating domain the IP address of the M2M IN residing in the target M2M SP domain. Subsequently, the IN in the originating domain shall forward the request to the IN of the target domain. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.5.2.3 Actions in the IN of the Target Domain | The IN is the entry point of the target M2M SP domain. The IN shall check if the addressed resource is a local resource. If it is not a local resource it shall forward the request to the appropriate CSE, after identifying the Hosting CSE within its domain, using the pointOfAccess attribute. Once the request reaches the target Hosting CSE, the CSE shall apply the access control policies applicable to the request. Consequently, the Hosting CSE shall forward the response for the incoming request following the same path of the incoming request. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.5.3 DNS Provisioning for Inter-M2M SP Communication | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.5.3.0 Overview | As specified previously, any M2M SP supporting inter-M2M SP communication shall ensure that the public domain names for the CSEs whose functionality is available across domains are held in the M2M SP's DNS and shall always point to the IP address associated with the Infrastructure domain CSE (being the entry point) for accessibility purposes. This implies that the IN-CSE shall be responsible for creating the appropriate entry in the DNS for a successfully registered CSE in the IN-CSE, if the M2M SP policies do allow access to the CSE across multiple M2M domains. Similarly, the IN-CSE shall be responsible for deleting the appropriate entry in the M2M SP's DNS for a successfully de-registered CSE in the IN-CSE if the M2M SP policies do allow access to the CSE across multiple M2M domains. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.5.3.1 Inter-M2M SP Communication Access Control Policies | Additional M2M SP policies that further restrict access to CSEs to requests originating from configured M2M SPs only, can complement the DNS entries created by the IN-CSE. These policies are out of scope of the present document. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 52 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.5.4 Conditional Inter-M2M Service Provider CSE Registration | Inter-M2M Service Provider CSE registration shall be supported to enable M2M entities (e.g. CSE, AE) in peer M2M Service Provider (SP) domains with the ability to create and operate resources with the equivalent set of possibilities as offered in the intra-M2M Service Provider domain, subject to the following: • The AE or CSE in either domain requires a representation of its own domain, notably the IN-CSE of its domain, in the peer domain to create resources in the peer domain. As an example, when it is required for an AE or a CSE to create and operate under the representation of an IN-CSE resource from a different M2M SP Domain. This enables the AE or CSE to have a behaviour that is identical in both the intra- and inter-M2M SP cases. An AE or CSE that does not require to use the remoteCSE representations of the other domain as parent resources, can create resources in the peer domain if it knows the parent of the resource to be created and as such does not require IN to IN registration. Hence creating subscriptions within a peer M2M SP shall not require IN to IN registration between peer domains (but remains subject to inter -M2M SP business agreements, and access control policies). Registration between M2M SPs occurs over the reference point Mcc', and is subject to business agreements. These agreements can limit the offered functionalities in comparison to those offered over the Mcc reference point. No additional security is required respect to the basic procedure as described in clauses 6.5.1, 6.5.2 and 6.5.3. Table 6.5.4-1 shows which oneM2M entity types can register with which other entity types across the Mcc' reference point. Table 6.5.4-1: Inter M2M SP Entity Registration Originator (Registree) Receiver (Registrar) Registration Procedure IN-CSE IN-CSE CSE registration procedure. See clause 10.2.2.7 An IN-CSE is allowed to register to the IN-CSE of multiple different M2M SP domains in the oneM2M System. Any inter-M2M SP communications in support of a request originating from one M2M SP domain shall be processed and forwarded through the IN of the originating M2M domain towards the IN of the target M2M SP domain and finally forwarded to its target CSE, if different from the target domain's IN. Hence the IN in both M2M domains shall be the exit and entry points, respectively, for all inter-M2M SP communication traffic. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 6.6 M2M Service Subscription | The M2M Service Subscription defines the technical part of the contract between an M2M Subscriber (typically an M2M Application Service Provider) and an M2M Service Provider. Each M2M Service Subscription shall have a unique identifier, the M2M-Sub-ID, as specified in clause 7.1.6. An M2M Service Subscription establishes a link between one or more AEs; one or more M2M Nodes. How to authorize the request operation based on M2M Service Subscription resource are defined in ETSI TS 118 103 [2]. An M2M Service Subscription shall be used for the following purposes: • Serve as a basis for authorization for resource operations. • Serve as the basis for charging. • Identify which Nodes are part of this M2M Service Subscription. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 53 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7 M2M Entities and Object Identification | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1 M2M Identifiers | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.0 Overview | This clause provides a list of identifiers required for the purpose of interworking within the oneM2M architectural model. An M2M identifier is a sequence of characters used to refer to an entity (such as CSE or an AE), a resource (such as defined in clause 9) or an object (such as an M2M Service Provider or an M2M Node) defined in oneM2M. An M2M identifier has a consistent meaning when applied (i.e. it refers consistently to the same resource, entity or object for the duration of their lifetime, as defined in clause 7.2) in a particular context. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.1 M2M Service Provider Identifier (M2M-SP-ID) | An M2M Service Provider shall be uniquely identified by the M2M Service Provider Identifier (M2M-SP-ID). This is a static value assigned to the Service Provider. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.2 Application Entity Identifier (AE-ID) | An Application Entity Identifier (AE-ID) uniquely identifies an AE resident on an M2M Node, or an AE that requests to interact with an M2M Node. An AE-ID shall identify an Application Entity for the purpose of all interactions within the M2M System. The AE-ID is globally unique and when used internally within a specific M2M SP domain, it is sufficient to be unique within that M2M Service Provider domain. It is extended to become globally unique when used outside the M2M Service Provider boundaries. The IN-CSE shall perform this task of adding or removing identifier portions (identifying the M2M SP) according to clause 7.2. The AE-ID, when used in the context of a specific CSE where the AE is registered, it is sufficient to be unique within the scope of that specific CSE. It is extended to become M2M Service Provider unique when used outside such specific CSE. The Hosting CSE of the AE shall perform this task of adding or removing the identifier portions according to clause 7.2. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.3 Application Identifier (App-ID) | An Application Identifier (App-ID) uniquely identifies an M2M Application in a given context. More precisely, there are two types of App-ID: registration authority defined App-ID (registered App-ID) and non-registered App-ID. The establishment of the registered App-ID is guaranteed to be globally unique; the non-registered App-ID is not guaranteed to be globally unique. The detail format is described in clause 7.2. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.4 CSE Identifier (CSE-ID) | A CSE shall be identified by a unique identifier, the CSE-ID, when instantiated within an M2M Node in the M2M System. The CSE-ID is unique in an M2M Service Provider Domain. It becomes globally unique when the M2M-SP-ID is added in front. The CSE-ID in a resource identifier (e.g. the To parameter) indicates the Hosting CSE of the resource. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.5 M2M Node Identifier (M2M-Node-ID) | An M2M Node, hosting a CSE and/or Application(s) shall be identified by a globally unique identifier, the M2M-Node-ID. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 54 (oneM2M TS-0001 version 4.15.0 Release 4) The M2M System shall allow the M2M Service Provider to set the CSE-ID and the M2M-Node-ID to the same value. The M2M-Node-ID enables the M2M Service Provider to bind a CSE-ID to a specific M2M Node. Examples of allocating a globally unique M2M-Node-ID include the use of Object Identity (OID) and IMEI. For details on OID, see annex H. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.6 M2M Service Subscription Identifier (M2M-Sub-ID) | The M2M-Sub-ID enables the M2M Service Provider to bind a M2M Service Subscriber, M2M Service Users, application(s), M2M Nodes, CSEs and services identified by service identifiers, as well as administrative information, such as billing address, etc., to a particular M2M Service Subscription between an M2M Service Subscriber and the M2M Service Provider. The M2M-Sub-ID is unique for every M2M Service Subscriber. The M2M Service Subscription Identifier has the following characteristics: • is assigned by the M2M Service Provider; • identifies the subscription to an M2M Service Provider; • enables communication with the M2M Service Provider; • can differ from the M2M Underlying Network Subscription Identifier. There can be multiple M2M Service Subscription Identifiers per M2M Underlying Network subscription. When used internally within the M2M Service Provider Domain that assigned it, a M2M-Sub-ID is sufficient to be unique within that M2M Service Provider Domain. When used externally outside the M2M Service Provider Domain that assigned it, a M2M-Sub-ID shall be globally unique by including the M2M-SP-ID within the M2M-Sub-ID. Care should be taken (e.g. proper configuration of ACPs) to not expose the M2M-Sub-ID to untrusted entities. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.7 M2M Request Identifier (M2M-Request-ID) | The M2M-Request-ID tracks a Request initiated by an AE over the Mca reference point, and by a CSE over the Mcc reference point, if applicable, end to end. It is also included in the Response to the Request over the Mca or Mcc reference points. To enable an AE to track Requests and corresponding Responses over the Mca reference point, AEs shall include a distinct M2M Request Identifier per request over the Mca Reference point to the CSE for any initiated request. The CSE shall make such M2M Request Identifier unique by prepending the AE-ID-Stem (see clause 7.2) and slash ('/') in front of it (e.g. C190XX7T/001). If the CSE creates an M2M Request Identifier, then the CSE shall maintain a binding between the M2M Request Identifier received from the AE and the M2M Request Identifier it created in its interactions towards other peer CSEs. The CSE shall include the M2M Request Identifier received from the AE in its Response to the AE. This binding shall be maintained by the CSE until the Request message sequence is completed. Note that the Request initiated by the CSE could be the result of an application Request, or a request initiated autonomously by the CSE to fulfil a service. In case an IN-CSE needs to send a request to a receiving CSE or ADN-AE that is not reachable over any of the underlying networks, the IN-CSE initiates the procedure for "waking up" the Node hosting the receiving CSE or ADN-AE by using procedures such as device triggering over the Mcn reference point. For Device Triggering, the triggering reference number to co-relate device triggering response is independent of the M2M Request Identifier. An IN-CSE may use the same value of an M2M-Request-Identifier in an incoming request for the triggering reference number in its interaction with the underlying network. A CSE receiving a Request from a peer CSE shall include the received M2M Request Identifier in all additional Requests unspanned (i.e. 1:1) it has to generate (including propagation of the incoming Request) and that are associated with the incoming Request, where applicable. If a Receiver CSE receives a request from an Originator for which another request with the same Request Identifier is already pending, the request shall be rejected. Otherwise - even if the same Request Identifier was already used by the same Originator sometime in the past, the request shall be treated as a new request. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 55 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.8 M2M External Identifier (M2M-Ext-ID) | The M2M-Ext-ID is used by an M2M Service Provider (M2M SP) when services targeted to a M2M Device, are requested from the Underlying Network. The M2M External Identifier allows the Underlying Network to identify the M2M Device (e.g. ADN, ASN, MN). To that effect, the Underlying Network maps the M2M-Ext-ID to the Underlying Network specific Identifier it allocated to the target M2M Device. In addition, the M2M SP shall maintain the association between the CSE-ID or AE-ID, the M2M-Ext-ID and the identity of the Underlying Network. Both pre-provisioned and dynamic association between the M2M-Ext-ID with the CSE-ID or ADN AE-ID are supported. NOTE 1: For each CSE-ID or ADN AE-ID, there is only one M2M-Ext-ID for a specific UNetwork-ID. Hence an M2M SP interworking with multiple Underlying Networks has different M2M-Ext-IDs associated with the same CSE-ID or ADN AE-ID, one per Underlying Network and selects the appropriate M2M-Ext-ID for any service request it initiates towards an Underlying Network. NOTE 2: The mapping by the Underlying Network of the M2M-Ext-ID to the M2M Device is Underlying Network specific. NOTE 3: The Underlying Network provider and the M2M Service Provider collaborate for the assignment of an M2M-Ext-ID to each M2M Device. At the same time, the Underlying Network provider maintains association of the M2M-Ext-ID with the Underlying Network specific Identifier allocated to the M2M Device that hosts such CSE. For pre-provisioned M2M-Ext-IDs, the M2M-Ext-ID along with the associated CSE-ID or ADN AE-ID shall be made available at the Infrastructure Node. The CSE or AE at M2M Device does not need to have knowledge of the M2M- Ext-ID assigned to it. For dynamic M2M-Ext-IDs, the M2M-Ext-ID specific to the Underlying Network shall be made available at the M2M Device in the Field Domain. Such M2M-Ext-ID shall be conveyed to the IN-CSE during Registration. The M2M-Ext-ID is to be used by the underlying network to identify an AE for verification when an AE retrieves the location information of a remote M2M device from a network-based location server of the underlying network (e.g. the 3GPP location server GMLC). NOTE 4: The mapping by the Underlying Network of the M2M-Ext-ID to the AE is Underlying Network specific. And how the underlying network performs the privacy control is out of the scope. NOTE 5: When the M2M-Ext-ID is targeted to an AE, the format is defined by the Underlying Network. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.9 Underlying Network Identifier (UNetwork-ID) | The UNetwork-ID is used for identifying an Underlying Network. UNetwork-ID is a static value and unique within a M2M Service Provider domain. One or more Underlying Networks may be available at an M2M Node offering different sets of capabilities, availability schedules, etc. Based on the "policy" information at the Node and the capabilities offered by the available Underlying Networks, appropriate Underlying Network can be chosen by using UNetwork-ID. For example, based on "policy", scheduling of traffic triggered by a certain event category in certain time periods may be allowed over Underlying Network "WLAN" but may not be allowed over Underlying Network "2G Cellular". |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.10 Trigger Recipient Identifier (Trigger-Recipient-ID) | The Trigger-Recipient-ID is used when device triggering services are requested from the Underlying Network, to identify an instance of an ASN/MN-CSE or ADN-AE on an execution environment, to which the trigger is routed. EXAMPLE: When 3GPP device triggering is used, the Trigger-Recipient-ID maps to the Application-Port- Identifier (ETSI TS 123 682 [i.14]). NOTE 1: For pre-provisioned M2M-Ext-IDs, Trigger-Recipient-ID is provisioned at the Infrastructure Node along with the M2M-Ext-ID and the associated CSE-ID or ADN AE-ID. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 56 (oneM2M TS-0001 version 4.15.0 Release 4) NOTE 2: For dynamic M2M-Ext-IDs, Trigger-Recipient-ID specific to the Underlying Network is provisioned at each M2M Device in the Field Domain. Such Trigger-Recipient-ID is conveyed to the IN-CSE during Registration. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.11 Void | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.12 Void | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.13 M2M Service Profile Identifier (M2M-Service-Profile-ID) | An M2M Service Profile Identifier defines applicable rules governing the AEs registering with M2M Nodes and the AEs residing on these nodes. Every M2M Service Profile is allocated an identifier so it can be retrieved for verification purposes. The M2M-Service-Profile-ID enables the M2M Service Provider to bind AE(s), applicable rules to these AEs, as well as M2M Service Roles to M2M nodes. An M2M-Service-Profile-ID shall be allocated to every M2M Node. The M2M Service Profile Identifier has the following characteristics: • belongs to the M2M Service Provider; • identifies applicable rules governing AEs registering with an M2M node. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.14 Role Identifier (Role-ID) | A Role identifier (Role-ID) is an identifier that a request originator may use in order to allow the CSE to enforce access control for resources. An originator may only use a Role-ID that is allowed by his service subscription profile. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.15 Token Identifier (Token-ID) | • A Token identifier (Token-ID) is the identifier for a Token. The Token-ID is assigned by the issuer of the Token. • Token-IDs shall meet the following criteria: - A Token-ID shall identify the issuer of the Token. - The Token-ID's uniqueness shall be global, with the proviso that a Token-ID value assigned to a Token may be assigned to another Token once the former Token has expired. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.16 Local Token Identifier (Local-Token-ID) | • A local token identifier (Local-Token-ID) is an identifier for a Token which can be assigned by a Hosting CSE making an accessing decision when it receives a request from an Originator which includes that Token or Token-ID in the request parameters (see clause 11.5.3). • In these scenarios, the request from the Originator included either the Token or the Token's Token-ID assigned by the Token's Issuer (see clause 7.1.15). In the latter case the Hosting CSE retrieves the Token using the Token-ID. The Hosting CSE assigns a Local-Token-ID to the Token. In the corresponding response message, the Hosting CSE provides the Originator with the mapping from the Local-Token-ID to the corresponding Token-ID. In subsequent requests to the Hosting CSE, the Originator can provide the Local-Token-ID in the place of the corresponding Token-ID or Token. The intention is that the Local-Token-ID would be significantly shorter than the Token or issuer-assigned Token-ID in order to reduce the size of the subsequent request messages. For more details regarding the use of Local-Token-ID, see clause 11.5.3. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 57 (oneM2M TS-0001 version 4.15.0 Release 4) Local-Token-IDs shall meet the following criteria: • The Local-Token-ID shall be assigned by the Hosting CSE making access decisions using the corresponding Token. • The Local-Token-ID's uniqueness shall be local to the Hosting CSE, with the proviso that a Local-Token-ID value assigned to a Token may be assigned to another Token once the former Token has expired. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 7.1.17 M2M Service Subscriber Identifier (M2M-SS-ID) | A M2M Service Subscriber is a stakeholder that establishes a M2M Service Subscription with a M2M Service Provider. A M2M-SS-ID uniquely identifies a M2M Service Subscriber and shall be assigned by a M2M Service Provider. A M2M-SS-ID uniquely identifies a M2M Service Subscriber within the M2M Service Provider Domain of the M2M Service Subscriber. When used in a different M2M Service Provider Domain, a M2M-SS-ID shall be extended to make it globally unique by pre-pending the M2M-SP-ID of the M2M Service Subscriber's M2M Service Provider. Note, a M2M Service Subscriber may also be assigned a M2M-User-ID such that the M2M Service Subscriber can function as a M2M Service User and take advantage of user-based operations in the oneM2M system (e.g. user-based access control privileges). For simplicity, the M2M-User-ID of a M2M Service Subscriber may be configured with the same value as its M2M-SS-ID. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.