hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 3 Definition of terms, symbols and abbreviations | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [i.2] and the following apply: CPE Proxier: CPE that is capable of proxying the communication between an ACS and a Proxied Device as defined in BBF TR-069 [4] |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 3.2 Symbols | Void. |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 111 [i.2] and the following apply: ACS Auto-Configuration Server ADN Application Dedicated Node AE Application Entity ASN Application Service Node BBF BroadBand Forum CMDH Communication Management and Delivery Handling CPE Customer Premise... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 4 Conventions | The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. ETSI ETSI TS 118 106 V3.6.2 (2021-02) 8 oneM2M TS-0006 version 3.6.2 Release 3 |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 5 Mapping of basic data types | BBF TR-106 [5] specifies the object structure supported by BBF TR-069 [4] enabled devices and specifies the structural requirements for the data hierarchy. This clause includes the mapping attribute data types to BBF TR-181 [6] parameters which follows the conventions of section 3 of BBF TR-106 [5] and data types descr... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 6 Mapping of identifiers | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 6.0 Introduction | The BBF TR-069 [4] specification defines three (3) types of devices, known as CPEs, that are capable of being managed from the perspective of the BBF TR-069 [4] agent: • CPE that hosts the BBF TR-069 [4] agent: Section A.3.3.1 Inform of BBF TR-069 [4] defines the required fields for a CPE to be identified. These fields... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 6.1 Mapping of Device identifiers to the Node Resource | Node Resources are identified for each instance of an ADN, ASN and MN node and are identified using the M2M Node Identifier (M2M-Node-ID) defined in ETSI TS 118 101 [1]. CPE Device identifiers shall map to the nodeID attribute of the <node> resource. The CPE Device identifiers are obtained from the contents of the foll... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 6.2 Identifier of an object instance | The BBF TR-069 [4] specification permits objects to have multiple object instances where each object instance is contained within the objectPath attribute of the Resource within the context of the Resource's objectId as defined in clause 7.1. In order to allow the AE or CSE that originated the request that manipulates ... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7 Mapping of resources | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.0 Introduction | This clause contains all information on how to map management resources from ETSI TS 118 104 [2] to managed objects and parameters as defined in the BBF TR-181 [6] data model or the Remote Procedure Calls (RPCs) in BBF TR-069 [4]. |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.1 General mapping assumptions | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.1.0 Introduction | BBF TR-069 [4] specifies a protocol for communication between a CPE (Customer Premises Equipment) and an ACS (Auto-Configuration Server). Any TR-069 enabled device has to follow the data model as described in the BBF TR-106 [5] and BBF TR-181 [6] as well as RPCs described in BBF TR-069 [4]. As BBF TR-181 [6] is the mod... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.1.1 Mapping of Device Identifiers | The Device identifiers for CPEs are mapped to the Resource Types [deviceInfo]. For CPE and Virtual Devices map their Device Identifiers (OUI-[PC-]SN) to the manufacturer, deviceType and deviceLabel attributes of the Resource [deviceInfo]. ETSI ETSI TS 118 106 V3.6.2 (2021-02) 10 oneM2M TS-0006 version 3.6.2 Release 3 F... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.1.2 Mapping of Embedded Devices | The BBF TR-181 [6] specification does not provide a mechanism where Embedded Devices provide information related to the Device.DeviceInfo objects and sub-objects. Instead the BBF TR-181 [6] provides this information in a manner that is reliant on the Embedded Device's underlying technology (e.g. ZigBee®, UpnP). As such... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.2 Resource [deviceInfo] | The Resource [deviceInfo] is a read-only Resource that shall map to the Device.DeviceInfo object of BBF TR-181 [6] for CPE and Virtual Devices. The information shall be retrieved using the GetParameterValues RPC of BBF TR-069 [4]. NOTE: The SerialNumber, ModelNumber, ProductClass attributes for a Virtual device are the... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.3 Resource [memory] | The Resource [memory] is a read-only Resource that shall map to the Device.DeviceInfo.MemoryStatus object of BBF TR-181 [6] for CPE and Virtual Devices. The information shall be retrieved using the GetParameterValues RPC of BBF TR-069 [4]. Attempts to modify the attributes of the memory Resource causes an error code "o... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.4 Resource [battery] | The Resource [battery] is a read-only Resource that shall map to an instance of Device.DeviceInfo.X_oneM2M_org_BatteryStatus.Battery.{i} object for CPE and Virtual Devices. The information shall be retrieved using the GetParameterValues RPC of BBF TR-069 [4]. Table 7.4-1: Resource [battery] Attribute Name of [battery] ... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.5 Resource [areaNwkInfo] | The Resource [areaNwkInfo] is a multi-instance Resource where each instance of the Resource shall map to an instance of Device.X_oneM2M_org_CSE.{i}.M2MareaNetwork.{i} object. As the Resource [areaNwkInfo] is a multi-instance Resource, the M2MareaNetwork object is a multi-object instance that can be created and deleted.... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.6 Resource [areaNwkDeviceInfo] | The Resource [areaNwkDeviceInfo] is a multi-instance Resource where each instance of the Resource shall map to an instance of Device.X_oneM2M_org_CSE.{i}.AreaNetworkDevice.{i} object. As the Resource [areaNwkDeviceInfo] is a multi-instance Resource, the AreaNetworkDevice object is a multi-object instance that can be cr... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.7 Resource [eventLog] | The Resource [eventLog] is a multi-instance Resource where each instance of the Resource shall map to an instance of Device.DeviceInfo.X_oneM2M_org_Diagnostics.EventLog.{i} object. The EventLog instance shall be created using the Add Object RPC of BBF TR-069 [4]. The EventLog instance shall be deleted using the Delete ... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.8 Resource [deviceCapability] | The Resource [deviceCapability] represents a capability of device that can be administratively enabled or disabled. The lists of capabilities that are managed are defined in the enumeration of the capabilityName attribute. BBF TR-181 [6] data model defines a subset of capabilities listed in the deviceCapability enumera... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.9 Resource [firmware] | The Resource [firmware] represents a firmware instance and is not considered a TR-069 managed entity within the device until the firmware Resource's update attribute has been written a value of "True". When this occurs, the BBF TR-069 [4] Download RPC shall be invoked. NOTE: In many instances, the server from which the... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.10 Resource [software] | The Resource [software] is a multi-instance Resource where each instance of the Resource maps directly to an instance of Device.SoftwareModules.DeploymentUnit.{i} object for the deployment aspects (install, uninstall) of the Resource [software]. The install and uninstall operation of the Resource [software] is performe... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.11 Resource [reboot] | The Resource [reboot] maps to either the Reboot RPC or FactoryReset RPC of BBF TR-069 [4]. When the reboot attribute of the Resource [reboot] is set to "True", the CSE shall execute the Reboot RPC of BBF TR-069 [4]. When the factoryReset attribute of Resource [reboot] is set to "True", the CSE shall execute the Factory... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.12 Resource [cmdhPolicy] | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.12.0 Introduction | The Resource [cmdhPolicy] represents a set of rules defining which CMDH parameters will be used by default when a request issued by a local originator contains the ec (event category) parameter but not all other CMDH parameters, see clause D.12 of ETSI TS 118 101 [1]. The Resource [cmdhPolicy] is a multi-instance Resou... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.12.1 Resource [activeCmdhPolicy] | The Resource [activeCmdhPolicy] provides a link to the currently active set of CMDH policies, see clause D.12.1 of ETSI TS 118 101 [1]. The Resource [activeCmdhPolicy] is mapped to the Enable parameter of the Device.X_oneM2M_org_CSE.{i}.CMDH.Policy.{i} object. The information of a Policy instance shall be updated using... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.12.2 Resource [cmdhDefaults] | The Resource [cmdhDefaults] defines default CMDH policy values, see clause D.12.2 of ETSI TS 118 101 [1]. The Resource [cmdhDefaults] is a multi-instance Resource where each instance of the Resource shall map to an instance of Device.X_oneM2M_org_CSE.{i}.CMDH.Default.{i} object. The Default instance shall be created us... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.12.3 Resource [cmdhDefEcValue] | The Resource [cmdhDefEcValue] represents a value for the ec (event category) parameter of an incoming request, see clause D.12.3 of ETSI TS 118 101 [1]. The Resource [cmdhDefEcValue] is a multi-instance Resource where each instance of the Resource shall map to an instance of Device.X_oneM2M_org_CSE.{i}.CMDH.DefaultECRu... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.12.4 Resource [cmdhEcDefParamValues] | The Resource [cmdhEcDefParamValues] represents a specific set of default values for the CMDH related parameters rqet (request expiration timestamp), rset (result expiration timestamp), oet (operational execution time), rp (response persistence) and da (delivery aggregation) that are applicable for a given ec (event cat... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.12.5 Resource [cmdhLimits] | The Resource [cmdhLimits] represents limits for CMDH related parameter values, see clause D.12.5 of ETSI TS 118 101 [1]. The Resource [cmdhLimits] is a multi-instance Resource where each instance of the Resource shall map to an instance of Device.X_oneM2M_org_CSE.{i}.CMDH.Limit.{i} object. The Limit instance shall be c... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.12.6 Resource [cmdhNetworkAccessRules] | The Resource [cmdhNetworkAccessRules] defines the usage of underlying networks for forwarding information to other CSEs during processing of CMDH-related requests in a CSE, see clause D.12.6 of ETSI TS 118 101 [1]. The Resource [cmdhNetworkAccessRules] is a multi-instance Resource where each instance of the Resource sh... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.12.7 Resource [cmdhNwAccessRule] | The Resource [cmdhNwAccessRule] define limits in usage of specific underlying networks for forwarding information to other CSEs during processing of CMDH-related requests, see clause D.12.7 of ETSI TS 118 101 [1]. The Resource [cmdhNwAccessRule] is a multi-instance Resource where each instance of the Resource shall map... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.12.8 Resource [cmdhBuffer] | The Resource [cmdhBuffer] represents limits in usage of buffers for temporarily storing information that needs to be forwarded to other CSEs during processing of CMDH-related requests in a CSE, see clause D.12.8 of ETSI TS 118 101 [1]. The Resource [cmdhBuffer] is a multi-instance Resource where each instance of the Re... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.13 Resource Type <mgmtCmd> | Each mgmtCmd Resource shall map to BBF TR-069 [4] RPC commands based on the value of cmdType. Accordingly, execReqArgs shall contain arguments related to the corresponding BBF TR-069 [4] RPCs. The details about corresponding procedure mapping are described in clause 8.2. Table 7.13-1: Resource Type <mgmtCmd> Attribute ... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.14 Resource Type <execInstance> | The <execInstance> resource from ETSI TS 118 104 [2] shall map to BBF CancelTransfer RPC commands when it is disabled/cancelled using a Update operation or deleted using a Delete operation. The details are described in clause 8.2. |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.15 Resource [registration] | The Resource [registration] represents the configuration information needed to register and AE or CSE with a Registrar CSE. The Resource [registration] is a multi-instance object where the key of the object is the originatorID (i.e. AE-ID, CSE-ID). The following rules are used to determine the object instance based on ... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.16 Resource [dataCollection] | The Resource [dataCollection] represents data collection (measurement) and transmittal (reporting) properties for an AE. The information shall be retrieved using the GetParameterValues RPC of BBF TR-069 [4]. The capabilities shall be enabled and disabled using the SetParameterValues RPC of BBF TR-069 [4]. Table 7.16-1:... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.17 Security Solutions | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.17.1 Introduction | Clauses 7.17.2 to 7.17.6 of the present document contains information on how to map the security specific management resources from ETSI TS 118 122 [8] to managed objects and parameters as defined in the BBF TR-181 [6] data model or the Remote Procedure Calls (RPCs) in BBF TR-069 [4]. |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.17.2 Resource [authenticationProfile] | The Resource [authenticationProfile] represents configuration information regarding establishing mutually-authenticated secure communications. The security principal using this configuration information can be a CSE or AE or the Managed ADN/ASN/MN acting as security principal on behalf of AEs on the Node, see clause 7.... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.17.3 Resource [trustAnchorCred] | The Resource [trustAnchorCred] represents configuration information regarding certificates provided by certificate authorities used be managed entities to authenticate peer endpoints, see clause 7.1.6 of ETSI TS 118 122 [8]. The Resource [trustAnchorCred] is a multi-instance Resource where each instance of the Resource... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.17.4 Resource [myCertFileCred] | The Resource [myCertFileCred] represents configuration information regarding certificates presented by the managed entity to remote entities for the establishment of secure communications, see clause 7.1.5 of ETSI TS 118 122 [8]. The Resource [myCertFileCred] is a multi-instance Resource where each instance of the Reso... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.17.5 Resource [MAFClientRegCfg] | The Resource [MAFClientRegCfg] represents configuration information that permits a MAF client to register with a MAF, see clause 7.1.7 of ETSI TS 118 122 [8]. The Resource [MAFClientRegCfg] is a multi-instance Resource where each instance of the Resource shall map to an instance of Device.X_oneM2M_org_SecuritySolution.... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 7.17.6 Resource [MEFClientRegCfg] | The Resource [MEFClientRegCfg] represents configuration information that permits a MEF client to register with a MEF, see clause 7.1.8 of ETSI TS 118 122 [8]. The Resource [MEFClientRegCfg] is a multi-instance Resource where each instance of the Resource shall map to an instance of Device.X_oneM2M_org_SecuritySolution.... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8 Mapping of procedures for management | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.0 Introduction | This clause contains all information on how to map management resource primitives from ETSI TS 118 104 [2] to the Remote Procedure Calls (RPCs) in BBF TR-069 [4]. |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1 Resource Type <mgmtObj> primitive mappings | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.0 Introduction | This clause contains all information on how to map Resource Type <mgmtObj> primitives from ETSI TS 118 104 [2] to the Remote Procedure Calls (RPCs) in BBF TR-069 [4]. |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.1 Alias-Based Addressing Mechanism | In order to utilize the Alias-Based Addressing Mechanism, the mechanism has to be supported by the ACS and CPE in order to map the M2M Service Layer identifier for the Resource instance to the CPE object instance. If the Alias-Based Addressing Mechanism feature is not supported by either the ACS or CPE, the CSE has to ... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.2 Create primitive mapping | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.2.0 Introduction | The Create Request and Response primitives shall map to the AddObject RPC. The AddObject RPC is defined in BBF TR-069 [4] as a synchronous RPC and returns a successful response or one of the following fault codes in table 8.1.2.0-1. ETSI ETSI TS 118 106 V3.6.2 (2021-02) 24 oneM2M TS-0006 version 3.6.2 Release 3 Table 8... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.2.1 M2M Service Layer Resource Instance Identifier mapping | When the Resource is a multi-instance Resource, the AddObject RPC should utilize the Alias-Based Addressing Mechanism as defined in section 3.6.1 of BBF TR-069 [4] in order to use the Resource instance value of the URI. |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.3 Delete primitive mapping | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.3.1 Delete primitive mapping for deletion of Object Instances | The Delete Request and Response primitives that results in the deletion of a Resource shall map to the DeleteObject RPC. The DeleteObject RPC is defined in BBF TR-069 [4] as a synchronous RPC and returns a successful response or one of the following fault codes in table 8.1.3.1-1. Table 8.1.3.1-1: DeleteObject Fault Co... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.3.2 Delete primitive mapping for software un-install operation | The Delete Request and Response primitives that results in a software un-install operation (e.g. Resource [software]) shall use the ChangeDUState mechanism defined in BBF TR-069 [4]. The ChangeDUState mechanism is an asynchronous command that consists of the synchronous ChangeDUState RPC for the un-installation request... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.4 Update primitive mapping | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.4.1 Update primitive mapping for Parameter modifications | The Update Request and Response primitives that modifies the value of Resource attributes shall map to the SetParameterValues RPC. The SetParametersValue RPC is defined in BBF TR-069 [4] as a synchronous RPC and returns a successful response or one of the following fault codes in table 8.1.4.1-1. Table 8.1.4.1-1: SetPa... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.4.2 Update primitive mapping for upload file transfer operations | The Update Request and Response primitives that results in an upload file transfer operation (e.g. logStop attribute of the Resource [eventLog]) shall use the Upload mechanism defined in BBF TR-069 [4]. The Upload mechanism is an asynchronous command that consists of the synchronous Upload RPC for the Upload and the as... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.4.3 Update primitive mapping for download file transfer operations | The Update Request and Response primitives that results in a download file transfer operation (e.g. update attribute of Resource [firmware]) shall use the Download mechanism defined in BBF TR-069 [4]. The Download mechanism is an asynchronous command that consists of the synchronous Download RPC for the Download and th... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.4.4 Update primitive mapping for reboot operation | The Update Request and Response primitives that results in a reboot operation (e.g. reboot attribute of Resource [reboot]) shall use the Reboot RPC defined in BBF TR-069 [4]. The Reboot RPC is asynchronous command. The Reboot RPC returns a successful response or one of the following fault codes in table 8.1.4.4-1. Tabl... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.4.5 Update primitive mapping for factory reset operation | The Update Request and Response primitives that results in a factory reset operation (e.g. factoryReset attribute of Resource [ reboot]) shall use the FactoryReset RPC defined in BBF TR-069 [4]. The FactoryReset RPC is an asynchronous command. The FactoryReset RPC returns a successful response or one of the following f... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.4.6 Update primitive mapping for software install operation | The Update Request and Response primitives that results in a software installation operation (e.g. install attribute of Resource [software]) shall use the ChangeDUState mechanism defined in BBF TR-069 [4]. The ChangeDUState mechanism is an asynchronous command that consists of the synchronous ChangeDUState RPC for the ... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.5 Retrieve primitive mapping | The Retrieve Request and Response primitives shall map to the GetParameterValues RPC. The GetParametersValue RPC is defined in BBF TR-069 [4] as a synchronous RPC and returns a successful response or one of the following fault codes in table 8.1.5-1. Table 8.1.5-1: GetParameterValues Fault Code Mapping Fault code Descr... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.6 Notify primitive mapping | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.6.0 Introduction | The NotifyRequest and Response primitives permit notifications to AE or CSEs that have subscribed to a Resource. While BBF TR-069 [4] has the capability to notify the subscribed ACS when an object's parameter has been modified, BBF TR-069 [4] does not have the capability for an ACS to be notified if any parameter withi... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.6.1 Procedure for subscribed Resource attributes. | When a <subscription> Resource for a <mgmtObj> Resource is Created, Deleted or Updated the CSE shall map to the SetParameterAttributes RPC in the following manner: • BBF TR-069 [4] provides the capability to subscribe to changes of a specific attribute through the use of the SetParameterAttributes RPC using the "Active... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.1.6.2 Notification primitive mapping | Notify Request and Response primitives shall map to the BBF TR-069 [4] notification mechanism. CPEs produce notifications for subscribed attributes using the BBF TR-069 [4] Inform method, the Inform method has an argument Event that has as one of the EventCodes with the value "4 VALUE CHANGE" indicating that a subscrib... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.2.1 Update (Execute) primitive for the <mgmtCmd> resource | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.2.1.0 Introduction | When the Update Request primitive for <mgmtCmd> resource addresses the execEnable attribute of the <mgmtCmd> resource, it effectively triggers an Execute <mgmtCmd> procedure. The Hosting CSE performs command conversion of its <execInstance> sub-resources. The mapping between the <execInstance> attributes and the BBF TR... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.2.1.1 Execute File Download | The download file transfer operation may use the Download mechanism defined in BBF TR-069 [4]. The Download mechanism is an asynchronous command which returns a successful response or one of the following fault codes mapped onto execResult values as detailed in table 8.2.1.1-1. A successful response to the Update primi... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.2.1.2 Execute File Upload Operations | The upload file transfer operation shall use the Upload mechanism defined in BBF TR-069 [4]. The Upload mechanism is an asynchronous command that consists of the synchronous Upload RPC for the Upload and the asynchronous TransferComplete RPC. The Upload RPC returns a successful response or one of the following fault co... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.2.1.3 Report Results using TransferComplete RPC | After a File Download or Upload has been attempted, the result of the operation is reported using the TransferComplete RPC. The TransferComplete RPC indicates a successful operation or one of the following fault codes mapped onto execResult values in table 8.2.1.3-1. Table 8.2.1.3-1: TransferComplete Fault Code Mapping... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.2.1.4 Execute Software Operations with ChangeDUState RPC | The software installation and uninstall operations shall use the ChangeDUState mechanism defined in BBF TR-069 [4]. The ChangeDUState mechanism is an asynchronous command that consists of the synchronous ChangeDUState RPC and returns a successful response or one of the fault codes mapped onto execResult values as detai... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.2.1.5 Report Results with ChangeDUStateComplete RPC | After software installation and uninstall operations using a ChangeDUState mechanism as defined in BBF TR-069 [4], the result of the state change operation is retrieved using the ChangeDUStateComplete RPC. The ChangeDUStateComplete RPC indicates a successful operation or one of the fault codes mapped onto execResult va... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.2.1.6 Execute Reboot operation | The reboot operation shall use the Reboot RPC defined in BBF TR-069 [4]. The Reboot RPC is a synchronous command. A successful response to the Update primitive triggering the Execute procedure means that the CPE has accepted the Reboot RPC. The Reboot RPC returns a successful response or one of the fault codes mapped o... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.2.1.7 Execute Factory Reset operation | The factory reset operation shall use the FactoryReset RPC defined in BBF TR-069 [4]. The FactoryReset RPC is a synchronous command. A successful response to the Update primitive triggering the Execute procedure means that the CPE has accepted the FactoryReset RPC. The FactoryReset RPC returns a successful response or ... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.2.2 Delete <mgmtCmd> resource primitive mapping | The Delete Request primitive for the <mgmtCmd> resource may initiate BBF TR-069 [4] RPC commands for the corresponding <execInstance> sub-resources as follows: • If there are no <execInstance> sub-resources with RUNNING execStatus, a successful response to the Delete primitive is returned and the <mgmtCmd> resource is ... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.2.3 Update (Cancel) <execInstance> primitive mapping | When the Update Request primitive for an <execInstance> sub-resource addresses the execDisable attribute of the <execInstance > sub-resource, it effectively triggers a Cancel <execInstance> resource procedure. The hosting CSE determines whether the <execInstance> resource has a RUNNING execStatus and weather the result... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.2.4 Delete <execInstance> primitive mapping | The Delete Request primitive for an <execInstance> sub-resource may initiate BBF TR-069 [4] RPC commands for the corresponding <execInstance> sub-resources as follows: • If the addressed <execInstance> sub-resource has an execStatus other than RUNNING, an successful Response to the Delete primitive is returned and the ... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.3 Resource [myCertFileCred] primitive mappings | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.3.1 Introduction | This clause contains information regarding the procedures for establishing a certificates presented by the managed entity in order for the peer to authenticate the managed entity. ETSI ETSI TS 118 106 V3.6.2 (2021-02) 38 oneM2M TS-0006 version 3.6.2 Release 3 |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.3.2 Creation of Resource [myCertFileCred] | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.3.2.1 Introduction | The creation of a [myCertFileCred] resource requires the use of the BBF TR-069 Download RPC to establish the credential on the managed entity. Once the managed entity has obtained the credential, the Device.Security.Certificate.{i} instance's SUIDs parameter is set from the [myCertFileCred] attribute using the BBF TR-0... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 8.3.2.2 Procedure for creation of Resource [myCertFileCred] | The Create Request and Response primitives for Resource [myCertFileCred] that results in a download file transfer shall use the Download mechanism defined in BBF TR-069 [4]. The Download mechanism is an asynchronous command that consists of the synchronous Download RPC for the Download and the asynchronous TransferComp... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9 Server Interactions | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9.0 Introduction | This clause specifies how the IN-CSE interacts with an ACS in order to manage the Resources described in the present document. The IN-CSE interaction with an ACS includes: • Establishment of the communication session between the IN-CSE and ACS. • Processing of requests and notifications between the IN-CSE and the ACS. ... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9.1 Communication Session Establishment | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9.1.1 IN-CSE to ACS Communication Session Establishment | When the IN-CSE detects that it has to delegate an interaction with a device resource to an ACS, the IN-CSE establishes a communication session with the ACS. The establishment of a communication session between the IN-CSE and ACS provides security dimensions for Access control, Authentication, Non-repudiation, Data con... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9.1.2 ACS to IN-CSE Communication Session Establishment | When the ACS detects a change to resources it manages that the IN-CSE has expressed interest, the ACS requests the IN-CSE to establish a session if a session does not exist for the resource being managed. The establishment of a communication session between the IN-CSE and ACS provides security dimensions for Access con... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9.1.3 ACS and IN-CSE Communication Session Requirements | When establishing a session from the ACS to the IN-CSE: • If a session does not exist between the IN-CSE and ACS, the ACS shall retain any notifications or changes in the resources based on an Event retention policy (i.e. time, number of events). • When an ACS to IN-CSE interaction is required and a session does not ex... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9.2 Processing of Requests and Responses | |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9.2.1 Request and Notification Formatting | Requests and Notifications mechanisms between the IN-CSE and the DM Server format the XML schema of the CPE methods defined in BBF TR-069 [4] as an ACS would format the CPE methods that it would pass to the CPE. The IN-CSE would then also process the CPE methods as defined in BBF TR-069 [4]. Likewise the ACS would send... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9.2.2 ACS Request Processing Requirements | When receiving requests from the IN-CSE the ACS shall be capable of defining mechanisms to support triggering of immediate operations to device. If the device is not available the ACS returns an appropriate error code. The ACS shall provide capability for the IN-CSE to indicate request policies to include: Retry policy... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9.2.3 ACS Notification Processing Requirements | When sending notifications to the IN-CSE: • The ACS shall be capable of providing a mechanism for the IN-CSE to subscribe to events. • The ACS shall be capable of providing a list of events for which the IN-CSE can subscribe. • The ACS shall be capable of providing a mechanism for the IN-CSE to unsubscribe from events.... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9.3 Discovery and Synchronization of Resources | For devices under management, the IN-CSE may discover resources of interest (metadata and values) within a device using the ACS. For resources of interest, the IN-CSE may also express an interest to be notified of a resource if a resource is changed (added, deleted, updated). ETSI ETSI TS 118 106 V3.6.2 (2021-02) 41 on... |
9ab246a740b04002bf9bf7eacc512119 | 118 106 | 9.4 Access Management |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.