hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 11.5.4.2 AE Indirect Authorization Relationship Update | The parameters exchanged for Indirect Authorization Relationship Update, and the corresponding processing, are specified in clause 7.3.2.7.2 of ETSI TS 118 103 [2]. The present clause specifies the transportation of parameters when oneM2M primitives are used. Further details for each step in the present clause can be obtained by examining the corresponding steps in clause 7.3.2.7.2 of ETSI TS 118 103 [2]. The message flow for the Indirect Authorization Relationship Update is shown in figure 11.5.4.2-1, which is described in the following text. Hosting CSE DAS Server AE 1. Original request: new AE-ID, Token or TokenID, resourceID 2. Perform access control 4. Request DAS server process AuthorRelationship update using its Token or TokenID, if DAS server finds a AuthorRelMapRecord for this Token, DAS server response the Originator with AuthorSignReqInfo 3. Response refuse 5. 1. Request DAS server process AuthorRelatioship update again using Token, AuthorSign, Hosting CSE Response Dertermine if there is a AuthorRelMapRecord for this Token 5.2. Verify the AuthorSign and update AuthorRelMapRecord 5.3.Update Request to Hosting CSE process AuthorRelatioship update: Token-ID, new AE-ID, AE AE 5.4. Update the cached Token Figure 11.5.4.2-1: AE Indirect Authorization Relationship Update • The AE sends a request to the Hosting CSE. This request may include the new AE-ID, and Token or TokenID issued for it. • The Hosting CSE performs the access decision for the request from the Originator. This call flow assumes that the Token or Token identified by the TokenID is valid and the holder attribute of the cached Token is not equal to the new AE-ID of the originator. • The Hosting CSE shall send, to the Originator, an unsuccessful resource access. • The AE requests DAS Server to update the authorization relationship using the Token or TokenID, and DAS server shall search if there is an Authorization Relationship Mapping Record of which the Token parameter or TokenID of the Token parameter is the same as the Token or TokenID received from AE. If the result is ok, DAS server shall return an AuthorSignReqInfo to AE to request the AuthorSign for the Token. • The AE provides the AuthorSign to prove the possession of the token: 5.1 The AE sends the update request containing Hosting CSE ID, AuthorSign, resourceID and Token. 5.2 After receiving the AuthorSign, the DAS Server shall check if this AuthorSign is equal to Signature stored in the Authorization Relationship Mapping Record corresponding to this Token. 5.3 If the result in step 5.2 is ok, the DAS Server AE shall send an Update request primitive to the Hosting CSE to update the cached Token. NOTE: Before the update action, DAS Server AE may get the resource ID of the cached Token locally stored on the Hosting CSE through discovery or other offline ways, there is no limitation on how to get the resource ID of the cached Token. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 503 (oneM2M TS-0001 version 4.15.0 Release 4) 5.4 The Hosting CSE updates the cached Token as described in clause 7.3.2.7.2 of ETSI TS 118 103 [2]. 11.6 Functional Architecture Specifications for Distributed Authorization |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 11.6.1 Distributed Authorization Reference Model | The Distributed Authorization reference model is shown in figure 11.6.1-1. This reference model comprises four subcomponents: • Policy Enforcement Point (PEP): This component intercepts resource access requests, makes access control decision requests, and enforces access control decisions. The PEP coexists with the entity that needs authorization services. • Policy Decision Point (PDP): This component interacts with the PRP and PIP to get applicable authorization polices and attributes needed for evaluating authorization policies respectively, and then evaluates access request using authorization policies for rendering an access control decision. • Policy Retrieval Point (PRP): This component obtains applicable authorization policies according to an access control decision request. These applicable policies should be combined in order to get a finial access control decision. • Policy Information Point (PIP): This component provides attributes that are needed for evaluating authorization policies, for example the IP address of the requester, creation time of the resource, current time or location information of the requester. Figure 11.6.1-1: Distributed Authorization reference model A Distributed Authorization system may comprise any of the subcomponents: PDP, PRP and/or PIP. This means that the subcomponents PEP, PRP, PDP and PIP may be distributed across different nodes. For example the PEP is located in an ASN/MN and the PDP is located in the IN. The generic distributed authorization procedure is described in clause 7 of ETSI TS 118 103 [2]. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 11.6.2 Interactions between Authorization Components | Interactions with PDP A CSE that acts as a PEP or PDP may send an access control decision request to another CSE that acts as a PDP. The access control decision request and response shall be encapsulated into UPDATE request and response respectively. The UPDATE request shall address an <authorizationDecision> resource. The relevant details are provided in clause 9.6.41. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 504 (oneM2M TS-0001 version 4.15.0 Release 4) In the case the access control decision requester is the Hosting CSE, it obtains the address of an <authorizationDecision> resource from the authorizationDecisionResourceIDs attribute of the <accessControlPolicy> resource that is bound to the target resource that the Originator wants to access. In other cases how the access control decision requester obtains the address of an <authorizationDecision> resource is out of scope of the present document. See clause 7 of ETSI TS 118 103 [2] for further details. Interactions with PRP A CSE that acts as a PDP or PRP may send an access control policy request to another CSE that acts as a PRP. The access control policy request and response shall be encapsulated into UPDATE request and response respectively. The UPDATE request shall address an <authorizationPolicy> resource. The relevant details are provided in clause 9.6.42. In the case the access control policy requester is the Hosting CSE, it obtains the address of an <authorizationPolicy> resource from the authorizationPolicyResourceIDs attribute of the <accessControlPolicy> resource that is bound to the target resource that the Originator wants to access. In other cases how the access control policy requester obtains the address of an <authorizationPolicy> resource is out of scope of the present document. See clause 7 of ETSI TS 118 103 [2] for further details. Interactions with PIP A CSE that acts as a PDP or PIP may send an access control information request to another CSE that acts as a PIP. The access control information request and response shall be encapsulated into UPDATE request and response respectively. The UPDATE request shall address an <authorizationInformation> resource. The relevant details are provided in clause 9.6.43. In the case the access control information requester is the Hosting CSE, it obtains the address of an <authorizationInformation> resource from the authorizationInformationResourceIDs attribute of the <accessControlPolicy> resource that is bound to the target resource that the Originator wants to access. In other cases how the access control policy requester obtains the address of an <authorizationPolicy> resource is out of scope of the present document. See clause 7 of ETSI TS 118 103 [2] for further details. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12 Information Recording | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.1 M2M Infrastructure Node (IN) Information Recording | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.1.0 Overview | Various informational elements have to be recorded by the M2M infrastructure nodes for a variety of reasons including but not limited to statistics, charging, maintenance, diagnostics, etc. This clause describes a framework for recording the necessary information by infrastructure nodes. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.1.1 Information Recording Triggers | Triggers have to be configured in the IN node by the M2M service provider to initiate information recording. The M2M infrastructure nodes shall be able to initiate recording based on any of the following triggers: • A request received by the M2M IN over the Mcc reference point. • A request received by the M2M IN over the Mca reference point. • A request initiated by the M2M IN over any reference point. • Timer- based triggers for non- request based information recording. This trigger is used only when the memory size of a container over a period of time is required. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 505 (oneM2M TS-0001 version 4.15.0 Release 4) More than one trigger can be simultaneously configured. The recording triggers may also be configurable, for example, as follows: • On a per CSE basis, or a group of CSEs for requests originating/arriving from/at the M2M IN. • On a per AE basis or a group of AEs. • The default behaviour is that no CSEs/AEs are configured. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.1.2 M2M Recorded Information Elements | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.1.2.1 Unit of Recording | A unit of recording refers to a number of informational elements recorded by the IN and that can be used as a basis for additional post-processing for a specific purpose such as generating Charging Data Records (CDRs), statistics, etc. In that respect, each unit of recording can be thought of as an M2M information record. The actual informational elements that make up a recording unit shall be described later. For request-based triggers, as defined in clause 12.1.1, the unit of recording shall include a request and its response. A unit of recording shall be referred to as an M2M Event Record. This shall apply to all recording triggers as defined in clause 12.1.1. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.1.2.2 Information Elements within an M2M Event Record | The information elements within an M2M event record are defined in table 12.1.2.2-1. Every M2M event record shall be tagged to depict its content according to the following classification: • Data related procedures: represent procedures associated with data storage or retrieval from the M2M IN (e.g. Container related procedures). • Control related procedures: represent all procedures that are not associated with data storage/retrieval from the M2M IN with the exclusion of group and device management related procedures (e.g. subscription procedures, registration). • Group related procedures: represent procedures that handle groups. The group name may be derived from the target resource in these cases. • Device Management Procedures. • Occupancy based trigger for recording the occupancy as described in clause 12.1.1. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 506 (oneM2M TS-0001 version 4.15.0 Release 4) Table 12.1.2.2-1: Information Elements within an M2M Event Record Information Element For request based triggers Mandatory / optional For timer based triggers Mandatory / optional Description M2M Service Subscription Identifier M M The M2M Service Subscription Identifier associated with the request. This is inserted by the IN (see clause 12.1.3) Application Entity ID CM (when applicable) NA The M2M Application Entity ID if applicable External ID CM (when Applicable) NA The external ID to communicate over Mcn where applicable Receiver M NA Receiver of an M2M request (can be any M2M Node) Originator M NA Originator of the M2M request (can be any M2M Node) Hosting CSE-ID O NA The hosting CSE-ID for the request in case the receiver is not the host, where applicable Target ID M NA The target URL for the M2M request if available. Alternatively can be the target resource identifier Protocol Type O NA Used Protocol Binding (e.g. HTTP, CoAP, MQTT) Request Operation O NA Request Operation as defined in clause 8.1.2 Request Headers size O NA Number of bytes for the headers in the Request (All Request parameters of the used protocol per the Protocol Type information element) Request Body size O NA Number of bytes of the body transported in the Request if applicable Response Headers size O NA Number of bytes for the headers in the Response (All Response parameters of the used protocol per the Protocol Type information element) Response Body size O NA Number of bytes of the body transported in the Response if applicable Response Status Code O NA Time Stamp M M Time of recording the M2M event M2M-Event-Record-Tag M M A Tag for the M2M event record for classification purposes. This tag is inserted by the IN and is M2M SP specific Control Memory Size O NA Storage Memory (in bytes), where applicable, to store control related information associated with the M2M event record(excludes data storage associated with container related operations) Data Memory Size O NA Storage Memory (in bytes), where applicable, to store data associated with container related operations Access Network Identifier O O Identifier of the access network associated with the M2M event record Additional Information O Vendor specific information Occupancy NA M Overall size (in Bytes) of the containers generated by a set of AEs identified by the M2M Service Subscription Identifier Group Name CM NA • The Group name (not necessarily unique) shall be included by the IN-CSE in the case where the fanning operations initiated by the M2M IN-CSE maxNrOfMembers O NA Maximum number of members of the group for Create and Update operation currentNrOfMembers O NA Current number of members in a group. The request shall be logged and information elements shall be recorded from the request before processing it or sending it out. After obtaining corresponding response, currentNrOfMembers shall be updated with the values from the response Subgroup Name CM NA • Subgroup name (not necessarily unique) shall be included i in the case when the IN-CSE initiates a fanning operation M2M-Node-Id M NA The node Id for the node generating the Accounting- Record-Number for the Diameter ACR. This shall be set to the CSE-ID for the IN-CSE node ETSI ETSI TS 118 101 V4.15.0 (2022-09) 507 (oneM2M TS-0001 version 4.15.0 Release 4) The choice for the mandatory elements is motivated by the need to include all M2M identifiers within an M2M event record so that it is possible to support multiple charging scenarios. For all non-mandatory elements, the M2M IN shall be configurable by the M2M service provider to select any additional desired information to be recorded in addition to the mandatory elements. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.1.3 Identities Associations in Support of Recorded Information | To enable the M2M IN to record the necessary information, as described above, the following associations shall be maintained by the M2M service provider: • The CSE-ID (for all M2M Nodes in the M2M framework) and the allocated M2M Service Subscription Identifier. • The AE-ID and the allocated M2M Service Subscription Identifier. For established associations, as described above, the M2M IN shall derive the appropriate M2M Service Subscription Identifier for insertion in the M2M record event. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2 Offline Charging | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.1 Architecture | Figure 12.2.1-1 depicts the charging architecture. Charging information, in the form of charging data records (CDRs), shall be derived from recorded information, and transferred to a Charging Server. As such, it is essential that all information required for charging shall be first selected for recording. There shall be a 1 to 1 mapping between a M2M Event Record and a CDR. The Charging Function (CHF included within the SCA CSF) embedded within the M2M IN is responsible for interaction with the Charging Server using the Mch reference point. Billing aspects are out of scope. Figure 12.2.1-1: Offline Charging Architecture ETSI ETSI TS 118 101 V4.15.0 (2022-09) 508 (oneM2M TS-0001 version 4.15.0 Release 4) Communication flows which transfer CDRs generated by the IN to an external charging server cross the Mch reference point. The Mch reference point may be mapped to reference points of other specifications. E.g. for a 3GPP Underlying Network, the Mch reference point maps to the Rf reference point enabling a 3GPP charging server to be used for oneM2M CDRs. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.2 Filtering of Recorded Information for Offline Charging | Recorded information is the basis for offline charging. To fulfil the needs of different billing systems not all recorded information is required in all cases. Hence, the M2M Charging Function shall be configurable to only select the desired information from the recorded information for transfer to the Charging Server. This configuration shall support selecting the desired information based on the following capabilities: • On a per CSE basis, or a group of CSEs, for requests originating/arriving from/at the IN. This applies to all M2M Nodes within the M2M framework. • On a per AE basis or a group of AEs. • The default behaviour is that no CSEs/AEs are configured. The charging function shall ensure that information selected for transfer to the charging server has also been selected for recording before a configuration is deemed acceptable for execution. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.3 Examples of Charging Scenarios | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.3.0 Overview | Charging scenarios refer to scenarios for which an M2M entity can be billed if the scenario is deemed billable by the M2M service provider. Some charging scenarios may require single CDR. Other scenarios may require multiple CDRs, and suitable correlation information shall have to be identified to select the CDRs for the charging scenario in this case. The following clause lists some potential charging scenarios as examples only. Each scenario shall require the appropriate configuration of the CHF, and for that matter the M2M recording functions, to ensure that all pertinent data is available. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.3.1 Example Charging Scenario 1 - Data Storage Resource Consumption | In this scenario, the M2M entity that stores application data, using container procedures for that purpose, will be billed, for storage resources within the M2M IN, until such time as the resources are deleted. This scenario will require correlation between multiple CDRs to identify the entity that stored the data, the entity that deleted the same data, and the duration and amount of storage. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.3.2 Example Charging Scenario 2 - Data transfer | In this scenario, the M2M entity that retrieves/stores container data will be billed for the amount of transferred data. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.3.3 Example Charging Scenario 3 - Connectivity | This scenario is relevant for an M2M entity that contacts the M2M IN frequently to transfer small amounts of data for storage. In this scenario, the M2M entity will be charged for the connectivity as opposed to the stored amount of data. The same applies to an M2M entity that also contacts frequently the M2M IN to retrieve stored data. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.4 Definition of Charging Information | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.4.0 Overview | Charging information in the form of CDR is essentially a subset of the information elements within the M2M event records recorded by the M2M IN for transmission over the Mch reference point. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 509 (oneM2M TS-0001 version 4.15.0 Release 4) |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.4.1 Triggers for Charging Information | The charging function within the M2M IN shall initiate transmission of CDRs if configured for that purpose in accordance with clause 12.2.2. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.4.2 Charging Messages over Mch Reference Point | The Mch shall be used in case the CDRs are to be transferred to an external Charging Server. It is assumed that the Mch is equivalent to the Rf reference point as defined in [i.15] and [i.16]. Hence, every CDR shall be transferred in a single message, namely Accounting-Request and that elicits a response, namely Accounting-Answer. Table 12.2.4.2-1 describes the use of these messages for offline charging. Table 12.2.4.2-1: Offline charging messages reference table Request-Name Source Destination Abbreviation Accounting-Request M2M IN Charging Server ACR Accounting-Answer Charging Server M2M IN ACA |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.4.3 Structure of the Accounting Message Formats | |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.4.3.1 Accounting-Request Message | Table 12.2.4.3.1-1 illustrates the basic structure of an ACR message generated from the M2M IN for offline charging in accordance with [i.15], [i.16], [i.8] and [i.11]. Table 12.2.4.3.1-1: Accounting-Request (ACR) message contents Informational Element Category Description Session-Id M This field identifies the operation session. The usage of this field is left to the M2M SP. Origin-Host M This field contains the identification of the source point of the operation and the realm of the operation Originator. Origin-Realm M This field contains the realm of the operation Originator. Destination-Realm M This field contains the realm of the operator domain. The realm will be addressed with the domain address of the corresponding public URI. Accounting-Record-Type M This field defines the transfer type: This field shall always set to event based charging. Accounting-Record- Number M This field contains the sequence number of the transferred messages. Acct-Application-Id OC Advertises support for accounting for M2M. Origin-State-Id OC This is a monotonically increasing value that is advanced whenever a Diameter entity restarts with loss of previous state, for example upon reboot. Event-Timestamp O Defines the time when the event occurred. Destination-Host OC This is the intended destination for the message. Proxy-Info OC Includes host information about a proxy that added information during routing of the message. Route-Record OC This field contains an identifier inserted by a relaying or proxying charging node to identify the node it received the message from. Service-Context-Id M This field identifies the M2M domain. Service-Information M This is a grouped field that holds the M2M specific parameters. Subscription-Id M Identifies the M2M Service Subscription Identifier. M2M Information M This parameter holds the M2M informational element specified in table 12.1.2.2-1 with the exception of the M2M Service Subscription Identifier. Proprietaryinformation O This is for proprietary information. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 510 (oneM2M TS-0001 version 4.15.0 Release 4) Informational Element Category Description OC This is a parameter that, if provisioned by the service provider to be present, shall be included in the CDRs when the required conditions are met. In other words, an OC parameter that is configured to be present is a conditional parameter. |
2bd691fcce98b96819b9b3b005c72741 | 118 101 | 12.2.4.3.2 Accounting-Answer Message | Table 12.2.4.3.2-1 illustrates the basic structure of an ACA message generated by the charging server as a response to an ACR message. Table 12.2.4.3.2-1: Accounting-Answer (ACA) message contents Information element Category Description Session-Id M Same as table 12.2.4.3.1-1 Origin-Host M Same as table 12.2.4.3.1-1 Origin-Realm M Same as table 12.2.4.3.1-1 Accounting-Record-Type M Same as table 12.2.4.3.1-1 Accounting-Record-Number M Same as table 12.2.4.3.1-1 Acct-Application-Id OC Same as table 12.2.4.3.1-1 Origin-State-Id OC This is a monotonically increasing value that is advanced whenever a Diameter entity restarts with loss of previous state, for example upon reboot Event-Timestamp O Same as table 12.2.4.3.1-1 Proxy-Info OC Same as table 12.2.4.3.1-1 Proprietary Information O Same as table 12.3.4.3.1-1 Result-Code M Indicates whether a particular request was completed successfully or whether an error occurred OC This is a parameter that, if provisioned by the operator to be present, shall be included in the CDRs when the required conditions are met. In other words, an OC parameter that is configured to be present is a conditional parameter. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 511 (oneM2M TS-0001 version 4.15.0 Release 4) Annex A (informative): Mapping of Requirements with CSFs Table A-1 illustrates the mapping of the Requirements specified in ETSI TS 118 102 [i.1] with the CSFs specified in the present document. Table A-1: Mapping of Requirements to CSFs CSF Name Supported Sub-Functions Associated Requirements Notes Addressing and Identification (AID) • Management of identifiers OSR-026 OSR-023 OSR-024 OSR-025 Overlap w/: DIS for OSR-023, OSR-024, and OSR-025 Communication Management/Delivery Handling (CMDH) • Providing communications with other CSEs, AEs, and NSEs • Communications management: best effort • Communications policy management • Underlying Network connectivity management • Communications management: data store and forward • Ability to trigger off-line device OSR-001 OSR-002 OSR-005 OSR-006 OSR-008 OSR-009 OSR-012 OSR-013 OSR-014 OSR-015 OSR-018 OSR-019 OSR-021 OSR-027 OSR-032 OSR-035 OSR-038 OSR-039 OSR-040 OSR-048 OSR-049 OSR-050 OSR-053 OSR-062 OSR-063 OSR-064 OSR-065 OSR-066 OSR-067 OSR-068 CRPR-001 CRPR-002 CRPR-003 MGR-016 Overlap w/: DMR for OSR-001, OSR-009, OSR-021, OSR-032 SSM for OSR-009 LOC for OSR-006 GMG for OSR-006 NSSE for OSR-006, OSR-027 SSM for OSR-009 Data Management and Repository (DMR) • Data storage and management • Semantic support • Data aggregation • Data analytics • Device data backup and recovery OSR-001 OSR-007 OSR-009 OSR-016 OSR-020 OSR-021 OSR-032 OSR-034 OSR-036 OSR-058 SMR-006 SER-015 Overlap w/: CMDH for OSR-001, OSR-009, OSR-021, OSR-032 SUB for OSR-016 GMG for OSR-020 ETSI ETSI TS 118 101 V4.15.0 (2022-09) 512 (oneM2M TS-0001 version 4.15.0 Release 4) CSF Name Supported Sub-Functions Associated Requirements Notes Device Management (DMG) • Configuration Management • Diagnostics and Monitoring • Firmware management • Software management • Device Area Network topology management OSR-017 OSR-069 OSR-070 OSR-071 OPR-001 OPR-002 OPR-003 MGR-001 MGR-003 MGR-004 MGR-006 MGR-007 MGR-008 MGR-009 MGR-011 MGR-012 MGR-013 MGR-014 MGR-015 MGR-019 MGR-020 MGR-021 SER-013 SER-014 Overlaps w/: GMG for OSR-017 SEC for SER-013 Discovery (DIS) • Discover resource • Local discovery (within CSE) • Directed remote discovery OSR-023 OSR-024 OSR-025 OSR-059 OSR-060 OSR-061 MGR-002 SMR-004 Overlaps w/: AID for OSR-023, OSR-024, OSR-025 Group Management (GMG) • Management of a group and its membership • CRUD • Use Underlying Network group capabilities • Bulk operations • Access control OSR-006 OSR-017 OSR-020 OSR-029 OSR-030 OSR-031 OSR-037 OSR-047 MGR-005 Overlaps w/: CMDH for OSR-006 LOC for OSR-006 GMG for OSR-006 NSSE for OSR-006, OSR-037 DMR for OSR-020 DMG for OSR-017 Location (LOC) • Location management • Network-provided • GPS-provided • Confidentiality enforcement as it relates to location OSR-006 OSR-051 OSR-052 SER-026 Network Service Exposure /Service execution and triggering (NSSE) • Access Underlying Network service • Location • Device triggering • Small data • Policy and charging • Support multiple Underlying Network functions OSR-006 OSR-011 OSR-027 OSR-037 OSR-054 OSR-055 OSR-056 MGR-017 MGR-018 OPR-004 OPR-005 OPR-006 Overlaps w/: CMDH for OSR-027 GMG for OSR-006, OSR-037 LOC for OSR-006 Registration (REG) • CSE registration • Application registration • Device registration • ID correlation MGR-010 Overlaps w/: SEC ETSI ETSI TS 118 101 V4.15.0 (2022-09) 513 (oneM2M TS-0001 version 4.15.0 Release 4) CSF Name Supported Sub-Functions Associated Requirements Notes Security (SEC) • Sensitive Data Handling • Secure storage • Secure execution • Independent environments • Security administration • Pre-provisioning • Dynamic bootstrap • Network bootstrap • Security association • Link level • Object level • Authorization and access • Identity protection SER-001 SER-002 SER-003 SER-004 SER-005 SER-006 SER-007 SER-008 SER-009 SER-010 SER-011 SER-012 SER-013 SER-016 SER-017 SER-018 SER-019 SER-020 SER-021 SER-022 SER-023 SER-024 SER-025 MGR-010 Overlap w/: DMG for SER-013 REG for MGR-010 SSM for SER-007 Service Charging and Accounting (SCA) • Charging enablers • Sending charging information to charging server • Subscription-based charging • Event-based charging • Session-based charging • Service-based charging • Correlation with Underlying Network • Charging management • Offline charging • Online charging CHG-001, CHG-002a, CHG-002b, CHG-003, CHG-004, CHG-005 Service Session Management (SSM) • Service Session Management (CSE to CSE, AE to CSE, and AE to AE) • Session persistence over link outage • Session context handling • Assignment of session ID • Session routing • Multi-hop session management • Session policy management OSR-003 OSR-004 OSR-009 OSR-045 SER-007 Overlap w/: CMDH and DMR for OSR-009 SEC for SER-007 Subscription/Notification Support (SUB) • Subscribe (CSE, AE) • Local • Remote • Subscription to a group • Notification • Synchronous • Asynchronous OSR-010 OSR-016 OSR-033 Overlaps w/: DMR for OSR-016 ETSI ETSI TS 118 101 V4.15.0 (2022-09) 514 (oneM2M TS-0001 version 4.15.0 Release 4) Annex B: Void ETSI ETSI TS 118 101 V4.15.0 (2022-09) 515 (oneM2M TS-0001 version 4.15.0 Release 4) Annex C (informative): Interworking between oneM2M System and 3GPP2 Underlying Networks C.1 General Concepts Interworking between oneM2M System and 3GPP2 Underlying Networks is based on 3GPP2X.P0068 [i.17]. In order to provide M2M services, interworking between oneM2M System and the 3GPP2 Underlying Network is required. M2M Applications (AEs) in the M2M UEs (M2M Nodes such as the ASNs, MNs, and ADNs) and the M2M Applications in the external network (Infrastructure Domain) use services provided by the 3GPP2 Underlying Network, and optionally the services provided by an M2M Server (IN-CSE). The 3GPP2 Underlying Network provides transport and communication services, including 3GPP2 bearer services, IMS and SMS. 3GPP2 Underlying Network supports several interworking models, such as the following: • Direct Model - Direct Communication provided by the 3GPP2 Network Operator: - The M2M Applications in the external network connect directly to the M2M Applications in the UEs used for M2M via the 3GPP2 Underlying Network without the use of any M2M Server. • Indirect Model - M2M Service Provider controlled communication: - Uses an M2M Server that is an entity outside the 3GPP2 Underlying Network operator domain for enabling communications between the Applications in the external network and at the UEs used for M2M. Tsp interface or SMS interface is an external interface that the third party M2M Server supports with the entities that are within the 3GPP2 Underlying Network domain. • Indirect Model - 3GPP2 Operator controlled communication: - Uses an M2M Server that is an entity inside the 3GPP2 Underlying Network operator domain for enabling communications between the Applications in the external network and at the UEs used for M2M. Tsp interface or SMS interface is an internal interface that the 3GPP2 Underlying Network operator controlled M2M Server supports with other entities within the 3GPP2 Underlying Network domain. • Hybrid Model: - Direct and Indirect models are used simultaneously in the hybrid model i.e. performing Control Plane signalling using the Indirect Model and connecting the M2M Applications in the external network and at the UEs used for M2M over User Plane using the Direct Model. C.2 M2M Communication Models In the indirect and hybrid models, the deployment of an M2M Server (IN-CSE) may be inside or outside the 3GPP2 Underlying Network operator domain as illustrated in figures C.2-1 and C.2-2. When the M2M Server is part of the 3GPP2 Underlying Network operator domain (figures C.2-1(C) and C.2-2), the M2M Server is considered a 3GPP2 Underlying Network operator internal network function, is operator controlled, and may provide operator value-added services. In this case, security and privacy protection for communication between the M2M-IWF and the M2M Server (IN-CSE) is optional. When the M2M Server is deployed outside the 3GPP2 Underlying Network operator domain (figures C.2-1(B) and C.2-2), the M2M Server is M2M Service Provider controlled. In this case, security and privacy protection for communication between the M2M-IWF and the M2M Server (IN-CSE) is needed. In the direct model (figure C.2-1(A)), there is no external or internal M2M Server in the communication path. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 516 (oneM2M TS-0001 version 4.15.0 Release 4) Figure C.2-1: M2M Communication Models ETSI ETSI TS 118 101 V4.15.0 (2022-09) 517 (oneM2M TS-0001 version 4.15.0 Release 4) M2M Server M2M Server M2M Application 3GPP2 Network M2M Device 3GPP2 Opertaor Boundary Indirect Model M2M Application Figure C.2-2: Multiple M2M Applications Using Diverse Communication Models A 3GPP2 network operator may deploy the hybrid model with a combination of no internal and external M2M Server (as in the Direct Model) and internal and/or external M2M Server (as in the Indirect Model). As shown in figure C.2-2, a UE (an M2M Node such as ASN/MN or ADN-AE) may be in communication with multiple M2M Servers which can be made up of a combination of 3GPP2 Underlying Network operator controlled and M2M Service Provider controlled M2M Servers. In that scenario, the M2M Service Provider controlled M2M Server, and the 3GPP2 Underlying Network operator controlled M2M Server may offer different capabilities to the M2M Applications. Though not illustrated, it is also possible that in the Indirect Service Model with 3GPP2 network operator controlled M2M Server; the M2M Application may be inside the 3GPP2 network operator domain and under 3GPP network operator control. C.3 3GPP2 Architectural Reference Model for M2M Figure C.3-1 shows the architecture for a UE used for M2M connecting to the 3GPP2 Underlying Network. The architecture supports various architectural models described in clause C.2. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 518 (oneM2M TS-0001 version 4.15.0 Release 4) Figure C.3-1: Enhanced 3GPP2 Network Architecture for Supporting M2M The M2M Server (IN-CSE) is the entity which connects to the 3GPP2 Underlying Network for providing communication with the UEs used for M2M. The M2M Server offers capabilities for use by one or multiple M2M Applications (AEs) hosted by the UE (ASN/MN or ADN-AE). The corresponding M2M Applications in the external network (Infrastructure Domain) are hosted by one or multiple M2M Application platform(s). The M2M Server interfaces with the 3GPP2 Underlying Network entities located in the home domain of the UE used for M2M via the Tsp and IP interfaces. M2M Server encompasses the IN-CSE entity specified by oneM2M. M2M Server interfaces with the M2M-IWF via Tsp Interface for Control Plane communications. User plane interactions between the M2M Server and 3GPP2 Underlying Network entities such as the PDSN and/or HA/LMA is via native-IP. With this configuration, oneM2M reference points Mcn and Mcc map to 3GPP2 reference points Tsp and IP respectively. C.4 Communication between oneM2M Service Layer and 3GPP2 Underlying Network Communication between the M2M Server (IN-CSE) and the entities in the 3GPP2 Underlying Network make use of the User Plane and the Control Plane communication paths, as needed for different 3GPP2 M2M communication models. User Plane communication path uses IP transport between the M2M Server (IN-CSE) and the ADN-AE or the CSE in the UE used for M2M (ASN/MN-CSE). The User Plane maps to oneM2M Mcc reference point. Control Plane communication path is over Tsp interface and maps to oneM2M Mcn reference point. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 519 (oneM2M TS-0001 version 4.15.0 Release 4) Figure C.4-1: User Plane and Control Plane Communication Paths C.5 Information Flows C.5.0 Overview 3GPP2 X.P0068 [i.17] specifies several system optimizations that can be used for M2M applications. Such optimizations include the following: • Interaction of M2M Server with M2M-IWF for device triggering. • Device trigger using SMS. • Device trigger using broadcast SMS. • Device trigger using IP transport. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 520 (oneM2M TS-0001 version 4.15.0 Release 4) C.5.1 Tsp Interface Call Flow Figure C.5.1-1 is the high level call flow illustrating device triggering using Tsp interface. Figure C.5.1-1: Tsp Interface Call Flow 1) M2M Server (IN-CSE) receives a request from an M2M Application Server (AE in Infrastructure Domain) to deliver data to a UE used for M2M (ASN/MN-CSE or ADN-AE) located in the 3GPP2 Underlying Network. Knowing the CSE-ID or AE-ID of the destination M2M Node, IN-CSE deduces its 3GPP2 External Identifier. 2) M2M Server (IN-CSE) may perform DNS query to obtain the IP address of the M2M-IWF for reaching the destination M2M Node. 3) M2M Server sends Device Trigger Request message to the M2M-IWF that includes destination M2M Node External ID and other information. 4) M2M-IWF checks that the M2M Server is authorized to send trigger requests and performs other tasks such as verifying that the M2M Server has not exceeded its quota or rate of trigger submission over Tsp. If such checks fail, the MTC-IWF sends a Device Trigger Confirm message with a cause value indicating the reason for the failure condition and the call flow stops at this step. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 521 (oneM2M TS-0001 version 4.15.0 Release 4) Otherwise, the MTC-IWF continues to interact with HAAA/HLR for obtaining 3GPP2 Internal ID for the M2M Node and other information for reaching the M2M Node in the 3GPP2 Underlying Network. M2M-IWF also determines the device trigger mechanisms (e.g. Mechanism 1, Mechanism 2, etc.) supported by the M2M Node. The flow continues with step 5. 5) M2M-IWF decides to deliver device trigger using e.g. Mechanism 1 and performs appropriate 3GPP2 Underlying Network specific procedures. 6) M2M-IWF may try alternative device trigger delivery mechanism (e.g. Mechanism 2) if Mechanism 1 fails. Or both Mechanisms 1 and 2 can be performed in parallel. 7) M2M-IWF performs appropriate 3GPP2 Underlying Network specific procedures for delivering device trigger using Mechanism 2. 8) M2M-IWF sends Device Trigger Report to the M2M Server upon receiving the acknowledgment from the M2M Node that it has received M2M device trigger. 9) The M2M Node and the M2M Server/AS take actions in response to the device trigger as needed. C.5.2 Point to Point Device Triggering 3GPP2 Underlying Network supports the following point-to-point device triggering mechanisms: • SMS on common channel. • SMS on 1xCS traffic channel. • Device trigger using IP interface. Device trigger using IP interface assumes that PPP sessions has been established and maintained between the M2M Node and the PDSN. An IP address has been assigned to the M2M Node by the IP anchor (PDSN/HA/LMA) and is maintained by the M2M Node and by other entities (e.g. HAAA) in the 3GPP2 Underlying Network. Upon receiving device trigger from the M2M Server, the M2M-IWF obtains the IP address assigned to the M2M Node from the M2M-AAA/HAAA. After that, the M2M-IWF sends device trigger to the M2M Node through IP routing via IP interface to the HA/LMA for MIP and PMIP operation, or to the PDSN for Simple IP operation. C.5.3 Broadcast Device Triggering 3GPP2 Underlying Network supports the following broadcast device triggering mechanisms: • SMS broadcast. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 522 (oneM2M TS-0001 version 4.15.0 Release 4) Annex D (normative): <mgmtObj> Resource Instances Description D.1 oneM2M Management Functions This clause describes the management functions supported by oneM2M. These functions are fulfilled by defining specializations of <mgmtObj> resources. These specializations can be regarded as "sub-types" of the <mgmtObj> resource type with specific designing to support different management capabilities through operations defined by oneM2M. These specializations are service layer information models for the purpose of management. They can be used within the M2M service layer or they can be further mapped to existing management technologies such as OMA DM [i.3], OMA LWM2M [i.4] and BBF TR-069 [i.2] to enable the management of devices with OMA or BBF compliant management clients. NOTE: The resources defined in this annex represent specializations of the <mgmtObj> resource as a result of introducing specializations of the [objectAttribute] attribute. The mgmtDefinition attribute carries the name of the resource type specialization. The names of instantiations of these resource specializations are not fixed. D.2 Resource firmware The [firmware] resource is used to share information regarding the firmware on the device. The [firmware] resource is a specialization of the <mgmtObj>resource. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 523 (oneM2M TS-0001 version 4.15.0 Release 4) [firmware] 1 mgmtDefinition 0..1 description 1 version 1 name 1 URL <subscription> 0..n 1 update 1 updateStatus 0..1 (L) objectIDs 0..1(L) objectPaths <semanticDescriptor> 0..n Figure D.2-1: Structure of [firmware] resource The [firmware] resource shall contain the child resources specified in table D.2-1. Table D.2-1: Child resources of [firmware] resource Child Resources of [firmware] Child Resource Type Multiplicity Description [variable] <subscription> 0..n See clause 9.6.8 where the type of this resource is described. [variable] <semanticDescriptor> 0..n See clause 9.6.30. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 524 (oneM2M TS-0001 version 4.15.0 Release 4) The [firmware] resource shall contain the attributes specified in table D.2-2. Table D.2-2: Attributes of [firmware] resource Attributes of [firmware] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RW See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "firmware" to indicate the resource is for firmware management. objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. version 1 RW The version of the firmware. This attribute is a specialization of [objectAttribute] attribute. name 1 RW The name of the firmware to be used on the device. This attribute is a specialization of [objectAttribute] attribute. URL 1 RW The URL from which the firmware image can be downloaded. This attribute is a specialization of [objectAttribute] attribute. update 1 RW The action that downloads and installs a new firmware in a single operation. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of [objectAttribute] attribute. updateStatus 1 RW Indicates the status of the update. This attribute is a specialization of [objectAttribute] attribute. D.3 Resource software The [software] resource is used to share information regarding the software on the device. The [software] resource is a specialization of the <mgmtObj>resource. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 525 (oneM2M TS-0001 version 4.15.0 Release 4) [software] 1 URL <subscription> 0..n 1 mgmtDefinition 0..1 description 1 version 1 softwareName 1 install 1 uninstall 1 installStatus 0..1 activate 0..1 deactivate 0..1 activeStatus 0..1 (L) objectIDs 0..1 (L) objectPaths <semanticDescriptor> 0..n Figure D.3-1: Structure of [software] resource The [software] resource shall contain the child resource specified in table D.3-1. Table D.3-1: Child resources of [software] resource Child Resources of [software] Child Resource Type Multiplicity Description [variable] <subscription> 0..n See clause 9.6.8 where the type of this resource is described. [variable] <semanticDescriptor> 0..n See clause 9.6.30. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 526 (oneM2M TS-0001 version 4.15.0 Release 4) The [software] resource shall contain the attributes specified in table D.3-2. Table D.3-2: Attributes of [software] resource Attributes of [software] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RW See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "software" to indicate the resource is for software management. objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. version 1 RW The version of the software. This attribute is a specialization of [objectAttribute] attribute. softwareName 1 RW The name of the software to be used on the device. This attribute is a specialization of [objectAttribute] attribute. URL 1 RW The URL from which the software package can be downloaded. This attribute is a specialization of [objectAttribute] attribute. install 1 RW The action that downloads and installs new software in a single operation. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of [objectAttribute] attribute. uninstall 1 RW The action that un-installs the software. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of [objectAttribute] attribute. installStatus 1 RW Indicates the status of the install or uninstall action. This attribute is a specialization of [objectAttribute] attribute. activate 0..1 RW The action that activates software previously installed. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of [objectAttribute] attribute. deactivate 0..1 RW The action that deactivates software. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of [objectAttribute] attribute. activeStatus 0..1 RW The status of the activate or deactivate action. This attribute is a specialization of [objectAttribute] attribute. Figure D.3-2 defines the legal state transitions of the installStatus attribute of the [software] resource as well as the criteria for each state transition. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 527 (oneM2M TS-0001 version 4.15.0 Release 4) IN_PROCESS SUCCESSFUL UNINITIALIZED FAILURE install / uninstall set to TRUE software successfully installed / uninstalled install / uninstall set to FALSE install / uninstall set to FALSE software unsuccessfully installed / uninstalled Figure D.3-2: State machine for software install / uninstall Figure D.3-3 defines the legal state transitions of the activeStatus attribute of the [software] resource as well as the criteria for each state transition. IN_PROCESS SUCCESSFUL UNINITIALIZED FAILURE activate / deactivate set to TRUE software successfully activated / deactivated activate / deactivate set to FALSE activate / deactivate set to FALSE software unsuccessfully activated / deactivated Figure D.3-3: State machine for software activation / deactivation D.4 Resource memory The [memory] resource is used to share information regarding the memory on the device. The [memory] resource is a specialization of the <mgmtObj>resource. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 528 (oneM2M TS-0001 version 4.15.0 Release 4) [memory] 1 mgmtDefinition 0..1 description 1 memAvailable 1 memTotal <subscription> 0..n 0..1 (L) objectIDs 0..1 (L) objectPaths <semanticDescriptor> 0..n Figure D.4-1: Structure of [memory] resource The [memory] resource shall contain the child resources specified in table D.4-1. Table D.4-1: Child resources of [memory] resource Child Resources of [memory] Child Resource Type Multiplicity Description [variable] <subscription> 0..n See clause 9.6.8 where the type of this resource is described. [variable] <semanticDescriptor> 0..n See clause 9.6.30. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 529 (oneM2M TS-0001 version 4.15.0 Release 4) The [memory] resource shall contain the attributes specified in table D.4-2. Table D.4-2: Attributes of [memory] resource Attributes of [memory] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RW See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "memory" to indicate the resource is for memory management. objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. memAvailable 1 RW The current available amount of memory. This attribute is a specialization of [objectAttribute] attribute. memTotal 1 RW The total amount of memory. This attribute is a specialization of [objectAttribute] attribute. D.5 Resource areaNwkInfo The [areaNwkInfo] resource is a specialization of the <mgmtObj>resource. [areaNwInfo] 1 mgmtDefinition 0..1 description 1 areaNwkType 1 listOfDevices <subscription> 0..n 0..1 (L) objectIDs 0..1 (L) objectPaths <semanticDescriptor> 0..n Figure D.5-1: Structure of [areaNwkInfo] resource ETSI ETSI TS 118 101 V4.15.0 (2022-09) 530 (oneM2M TS-0001 version 4.15.0 Release 4) The [areaNwkInfo] resource shall contain the child resource specified in table D.5-1. Table D.5-1: Child resources of [areaNwInfo] resource Child Resources of [areaNwkInfo] Child Resource Type Multiplicity Description [variable] <subscription> 0..n See clause 9.6.8 where the type of this resource is described. [variable] <semanticDescriptor> 0..n See clause 9.6.30. The [areaNwkInfo] resource shall contain the attributes specified in table D.5-2. Table D.5-2: Attributes of [areaNwkInfo] resource Attributes of [areaNwkInfo] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RW See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "areaNwkInfo" to indicate the resource is for area network information. objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. areaNwkType 1 RW The areaNwkType is a value that indicates the type of M2M Area Network. This attribute is a specialization of [objectAttribute] attribute. It identifies network technologies e.g. zigbee, lora, etc. The content of this attribute is a URN following the definition in IETF RFC 8141 "Uniform Resource Names (URNs)" [19] e.g. urn:onem2m:mgmt:nwkType:zigbee:1. The format of this attribute is defined in ETSI TS 118 104 [3]. It also allows vendors to use their own URN formats e.g. urn:x-vendor:example:technology. listOfDevices 0..1 (L) RW Indicates the list of devices in the M2M Area Network. The attribute contains references to [areaNwkDeviceInfo] resource. From listOfDevices, the topology of the area network can be discovered and retrieved. This attribute is a specialization of [objectAttribute] attribute. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 531 (oneM2M TS-0001 version 4.15.0 Release 4) D.6 Resource areaNwkDeviceInfo The [areaNwkDeviceInfo] resource is a specialization of the <mgmtObj>resource. [areaNwkDeviceInfo] 1 mgmtDefinition 0..1 (L) objectIDs 0..1 description 1 devId 1 devType 1 areaNwkId <subscription> 0..n 0..1 sleepInterval 0..1 sleepDuration 0..1 status 1 listOfNeighbors 0..1 (L) objectPaths <semanticDescriptor> 0..n Figure D.6-1: Structure of [areaNwkDeviceInfo] resource The [areaNwkDeviceInfo] resource shall contain the child resources specified in table D.6-1. Table D.6-1: Child resources of [areaNwkDeviceInfo] resource Child Resources of [areaNwkDeviceInfo] Child Resource Type Multiplicity Description [variable] <subscription> 0..n See clause 9.6.8 where the type of this resource is described. [variable] <semanticDescriptor> 0..n See clause 9.6.30. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 532 (oneM2M TS-0001 version 4.15.0 Release 4) The [areaNwkDeviceInfo] resource shall contain the attributes specified in table D.6-2. Table D.6-2: Attributes of [areaNwkDeviceInfo] resource Attributes of [areaNwkDeviceInfo] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RW See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "areaNwkDeviceInfo" to indicate the resource is for area network device information. objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. devId 1 RW Indicates the id of the device. It could be the id of the hardware or nodeId. This attribute is a specialization of [objectAttribute] attribute. devType 1 RW Indicates the type of the device. The attribute also indicates the functions or services that are provided by the device. Examples include temperature sensor, actuator, Zigbee® coordinator or Zigbee® router. This attribute is a specialization of [objectAttribute] attribute. areaNwkId 1 RW The reference to an areaNwkInfo resource which this device associates with. This attribute is a specialization of [objectAttribute] attribute. sleepInterval 0..1 RW The interval between two sleeps. This attribute is a specialization of [objectAttribute] attribute. sleepDuration 0..1 RW The time duration of each sleep. This attribute is a specialization of [objectAttribute] attribute. status 0..1 RW The status of the device (sleeping or waked up). listOfNeighbors 0..1 (L) RW Indicates the neighbour devices of the same area network. When modified, the connection relationship of the devices shall be modified accordingly. This attribute is a specialization of [objectAttribute] attribute. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 533 (oneM2M TS-0001 version 4.15.0 Release 4) D.7 Resource battery The [battery] resource is used to share information regarding the battery. The [battery] resource is a specialization of the <mgmtObj> resource. [battery] 1 mgmtDefinition 0..1 description 1 batteryLevel 1 batteryStatus <subscription> 0..n 0..1 (L) objectIDs 0..1 (L) objectPaths <semanticDescriptor> 0..n Figure D.7-1: Structure of [battery] resource The [battery] resource shall contain the child resources specified in table D.7-1. Table D.7-1: Child resources of [battery] resource Child Resources of [battery] Child Resource Type Multiplicity Description [variable] <subscription> 0..n See clause 9.6.8 where the type of this resource is described. [variable] <semanticDescriptor> 0..n See clause 9.6.30. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 534 (oneM2M TS-0001 version 4.15.0 Release 4) The [battery] resource shall contain the attributes specified in table D.7-2. Table D.7-2: Attributes of [battery] resource Attributes of [battery] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RW See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. This attribute shall have the fixed value "battery". objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. batteryLevel 1 RW The current battery level. This attribute is a specialization of [objectAttribute] attribute. batteryStatus 1 RW Indicates the status of the battery. This attribute is a specialization of [objectAttribute] attribute. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 535 (oneM2M TS-0001 version 4.15.0 Release 4) D.8 Resource deviceInfo The [deviceInfo] resource is used to share information regarding the device. The [deviceInfo] resource is a specialization of the <mgmtObj> resource. Figure D.8-1: Structure of [deviceInfo] resource ETSI ETSI TS 118 101 V4.15.0 (2022-09) 536 (oneM2M TS-0001 version 4.15.0 Release 4) The [deviceInfo] resource shall contain the child resources specified in table D.8-1. Table D.8-1: Child resources of [deviceInfo] resource Child Resources of [deviceInfo] Child Resource Type Multiplicity Description [variable] <subscription> 0..n See clause 9.6.8 where the type of this resource is described. [variable] <semanticDescriptor> 0..n See clause 9.6.30. The [deviceInfo] resource shall contain the attributes specified in table D.8-2. Table D.8-2: Attributes of [deviceInfo] resource Attributes of [deviceInfo] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RW See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. This attribute shall have the fixed value "deviceInfo". objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. deviceLabel 1 RW Unique device label assigned by the manufacturer. This attribute is a specialization of [objectAttribute] attribute. The value of the attribute typically exposes the device's serial number that is specific to a manufacturer and possibly further restricted within the manufacturer by a deviceType or model. This attribute shall be formatted as either single value-only string or a string format that contains a list of key-value pairs. When this attribute contains a list of key-value pairs, the list of key-value pairs is identified by a "|"(vertical line) character as the first character in the string. Within the list of key-value pairs, each key and value shall be separated by ":"(colon) and each pair shall be separated by " (SPACE(U+0020))". An example for the key-value string about OMA DWAPI is "|systemID:0123 serviceID:xyz". When using reserved characters (e.g. SPACE, ":", "%", or "|") within a key or value element, the reserved characters are escaped by identifying the ascii value of the character with a percent escape character preceding the ascii value. For example if the previous examples systemID key's value included a SPACE character the string is represented as "|systemID:01%2023 serviceID:xyz". It is also possible to use a list of URNs. manufacturer 1 WO The name/identifier of the device manufacturer. This attribute is a specialization of [objectAttribute] attribute. manufacturerDetailsLink 0..1 RW URL to manufacturer's website. This attribute is a specialization of [objectAttribute] attribute. manufacturingDate 0..1 WO Manufacturing date of device. This attribute is a specialization of [objectAttribute] attribute. model 1 WO The name/identifier of the device mode assigned by the manufacturer. This attribute is a specialization of [objectAttribute] attribute. subModel 0..1 WO Device sub-model name. This attribute is a specialization of [objectAttribute] attribute. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 537 (oneM2M TS-0001 version 4.15.0 Release 4) Attributes of [deviceInfo] Multiplicity RW/ RO/ WO Description deviceType 1 RW The type (e.g. cell phone, photo frame, smart meter) or product class (e.g. X-series) of the device. This attribute is a specialization of [objectAttribute] attribute. deviceName 0..1 RW Device name. This attribute is a specialization of [objectAttribute] attribute. fwVersion 0..1 RW The firmware version of the device (see note). swVersion 0..1 RW The software version of the device. This attribute is a specialization of [objectAttribute] attribute. hwVersion 0..1 WO The hardware version of the device. This attribute is a specialization of [objectAttribute] attribute. osVersion 0..1 RW Version of the operating system (defined by manufacturer). This attribute is a specialization of [objectAttribute] attribute. country 0..1 WO Country code of the device. It could be manufacturing country, deployment country or procurement country. This attribute is a specialization of [objectAttribute] attribute. location 0..1 RW Location where the device is installed. It may be configured via the user interface provided by the 'presentationURL' property or any other means. This attribute is a specialization of [objectAttribute] attribute. systemTime 0..1 RW Reference time for the device. This attribute is a specialization of [objectAttribute] attribute. supportURL 0..1 RW URL that points to product support information of the device. This attribute is a specialization of [objectAttribute] attribute. presentationURL 0..1 RW To quote UPnP: "the control point can retrieve a page from this URL, load the page into a web browser, and depending on the capabilities of the page, allow a user to control the device and/or view device status. The degree to which each of these can be accomplished depends on the specific capabilities of the presentation page and device". This attribute is a specialization of [objectAttribute] attribute. protocol 0..1(L) RW A list of MIME types for all supported communication protocol(s) of the device. EXAMPLE: application/x-alljoin;version=1.0 application/x- echonet-lite;version=1.0 indicates the device supports both AllJoyn v1.0 and Echonet Lite v1.0. This attribute is a specialization of [objectAttribute] attribute. NOTE: If the device only supports one kind of Software this is identical to swVersion. This attribute is a specialization of [objectAttribute] attribute. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 538 (oneM2M TS-0001 version 4.15.0 Release 4) D.9 Resource deviceCapability The [deviceCapability] resource represents each device's capability. The [deviceCapability] resource is a specialization of the <mgmtObj> resource. [deviceCapability] 0..1 description 1 capabilityName 1 attached 1 capabilityActionStatus 0..1 enable <subscription> 0..n 0..1 disable 1 mgmtDefinition 0..1 (L) objectIDs 0..1 (L) objectPaths 1 currentState <semanticDescriptor> 0..n Figure D.9-1: Structure of [deviceCapability] resource The [deviceCapability] resource shall contain the child resources specified in table D.9-1. Table D.9-1: Child resources of [deviceCapability] resource Child Resources of [deviceCapability] Child Resource Type Multiplicity Description [variable] <subscription> 0..n See clause 9.6.8 where the type of this resource is described. [variable] <semanticDescriptor> 0..n See clause 9.6.30. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 539 (oneM2M TS-0001 version 4.15.0 Release 4) The [deviceCapability] resource shall contain the attributes specified in table D.9-2. Table D.9-2: Attributes of [deviceCapability] resource Attributes of [deviceCapability] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RW See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. This attribute shall have the fixed value "deviceCapability". objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. capabilityName 1 WO The name of the capability. This attribute is a specialization of [objectAttribute] attribute. attached 1 RO Indicates whether the capability is attached to the device or not. This attribute is a specialization of [objectAttribute] attribute. capabilityActionStatus 1 RO Indicates the status of the Action (including a performed action and the corresponding final state). This attribute is a specialization of [objectAttribute] attribute. currentState 1 RO Indicates the current state of the capability (e.g. enabled or disabled). This attribute is a specialization of [objectAttribute] attribute. enable 0..1 WO The action that allows enabling the device capability. This attribute is a specialization of [objectAttribute] attribute. disable 0..1 WO The action that allows disabling the device capability. This attribute is a specialization of [objectAttribute] attribute. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 540 (oneM2M TS-0001 version 4.15.0 Release 4) D.10 Resource reboot The [reboot] resource is used to reboot a device. The [reboot] resource is a specialization of the <mgmtObj> resource. [reboot] 1 mgmtDefinition 0..1 description 1 reboot 1 factoryReset <subscription> 0..n 0..1 (L) objectIDs 0..1 (L) objectPaths <semanticDescriptor> 0..n Figure D.10-1: Structure of [reboot] resource The [reboot] resource shall contain the child resources specified in table D.10-1. Table D.10-1: Child resources of [reboot] resource Child Resources of [reboot] Child Resource Type Multiplicity Description [variable] <subscription> 0..n See clause 9.6.8 where the type of this resource is described. [variable] <semanticDescriptor> 0..n See clause 9.6.30. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 541 (oneM2M TS-0001 version 4.15.0 Release 4) The [reboot] resource shall contain the attributes specified in table D.10-2. Table D.10-2: Attributes of [reboot] resource Attributes of [reboot] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RW See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. This attribute shall have the fixed value "reboot". objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. reboot 1 RW The action that allows rebooting the device. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of [objectAttribute] attribute. factoryReset 1 RW The action that allows making the device returning to the factory settings. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of [objectAttribute] attribute. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 542 (oneM2M TS-0001 version 4.15.0 Release 4) D.11 Resource eventLog The [eventLog] resource is used to record the event log for a device. The [eventLog] resource is a specialization of the <mgmtObj> resource. [eventLog] 1 mgmtDefinition 0..1 description 1 logTypeId 1 logData 1 logStatus <subscription> 0..n 1 logStart 1 logStop 0..1 (L) objectIDs 0..1 (L) objectPaths <semanticDescriptor> 0..n Figure D.11-1: Structure of [eventLog] resource The [eventLog] resource shall contain the child resources specified in table D.11-1. Table D.11-1: Child resources of [eventLog] resource Child Resources of [eventLog] Child Resource Type Multiplicity Description [variable] <subscription> 0..n See clause 9.6.8 where the type of this resource is described. [variable] <semanticDescriptor> 0..n See clause 9.6.30. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 543 (oneM2M TS-0001 version 4.15.0 Release 4) The [eventLog] resource shall contain the attributes specified in table D.11-2. Table D.11-2: Attributes of [eventLog] resource Attributes of [eventLog] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RW See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. This attribute shall have the fixed value "eventLog". objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. logTypeId 1 RW Identifies the types of logs to be recorded. E.g. security log, system log. This attribute is a specialization of [objectAttribute] attribute. logData 1 RW Diagnostic data logged upon event of interests defined by this diagnostic function. This attribute is a specialization of [objectAttribute] attribute. logStatus 1 RW Indicates the status of the logging process. E.g. Started, Stopped. This attribute is a specialization of [objectAttribute] attribute. logStart 1 RW The action that allows starting the log corresponding to the mentioned logTypeId. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of [objectAttribute] attribute. logStop 1 RW The action that allows stopping the log corresponding to the mentioned logTypeId. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of [objectAttribute] attribute. D.12 Resource cmdhPolicy D.12.0 Overview A [cmdhPolicy] resource is defined as a specialization of the <mgmtObj> resource type as specified in clause 9.6.15. It includes a number of child resources which are referenced by means of mgmtLink attributes. Each of these linked child resources represents itself a specialization of the <mgmtObj> resource type. These child resources and their child resources are defined in clauses D.12.1 to D.12.8. The [cmdhPolicy] resource represents a set of rules associated with a node hosting a specific CSE or a specific ADN that govern the behaviour of that CSE communication behaviour of that node regarding rejecting, buffering and sending request or response messages via the Mcc or Mca reference point between a CSE and its Registrar - in case of a node hosting a CSE - or via the Mca reference point - in case of an ADN. The reference point between an associated CSE and its Registrar CSE - in case the [cmdhPolicy] resource is associated with a node hosting a CSE - or the Mca reference point used by the associated ADN - in case the [cmdhPolicy] resource is associated with an ADN - is termed "associated reference point" in what follows. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 544 (oneM2M TS-0001 version 4.15.0 Release 4) The rules contained in a [cmdhPolicy] resource are sub-divided into rules represented by different linked child resources with different purposes as follows: • Defaults: Defines which CMDH related parameters will be used by default when a request or response message issued by a registrar of the associated CSE or the associated CSE itself to be sent across the associated reference point contains the Event Category parameter but not all other CMDH related parameters and which default Event Category parameter shall be used when none is given in the request or response. • Limits: Defines the allowed limits for CMDH related parameters in request or response messages to be sent across the associated reference point with a given Event Category value. • Network usage: Defines the conditions when usage of specific Underlying Networks is allowed for request or response messages to be sent across the associated reference point with a given Event Category value. • Buffering: Defines limits of supported buffer size to be used for storing pending messages with a given Event Category value and their priorities when deletion cannot be avoided. Buffering of messages to be sent across an associated reference point form an ADN supporting CMDH to other nodes is optional. The relationships of [cmdhPolicy] resources with other resources and the position within the overall resource structure are depicted in figure D.12.0-1. One or several [cmdhPolicy] resources can be assigned as child resources under a parent of <node> resource type. The <node> resource carrying CMDH policies is linked by means of a nodeLink attribute from an instance of a <remoteCSE> resource type or an instance of an <AE>resource type representing an Application Entity on an ADN. This nodeLink attribute as well as the reverse hostedCSELink or hostedAELinks attribute in the <node> resource define to which AE(s) or node the set of CMDH policies apply whenever this CSE receives requests or response messages that need to be forwarded over Mcc reference point sent across the associated reference point to or from the indicated entities. Since only one particular set of CMDH rules can be active for a given node at any given point in time, an [activeCMDHPolicy] child resource for CMDH policies shall be applied is used to point to the active [cmdhPolicy] resource that shall be effective for that particular node. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 545 (oneM2M TS-0001 version 4.15.0 Release 4) Figure D.12.0-1: Relationships between [cmdhPolicy] resource and other resources When employing external management technology, the [cmdhPolicy] resources are assigned under instances of the <node> resources that represent the remotely managed field nodes in the IN-CSE performing device management for these nodes. In this scenario, the [cmdhPolicy] resources are transferred to the field node by means of the external device management technology applicable for that specific node. When a field domain node is managed via the Mcc reference point, the [cmdhPolicy] resources are provisioned directly to instances of the <node> resources in the respective field domain CSE from an IN-CSE responsible for the device/entity management. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 546 (oneM2M TS-0001 version 4.15.0 Release 4) Figure D.12.0-2: Structure of [cmdhPolicy] resource The [cmdhPolicy] resource shall contain attributes specified in table D.12.0-1. Table D.12.0-1: Attributes of [cmdhPolicy] resource Attributes of [cmdhPolicy] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RO See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "cmdhPolicy" to indicate the resource is for CMDH policy management. objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. cmdhPolicyName 1 RW A name under which the CMDH policy will be referred. This attribute is a specialization of [objectAttribute] attribute. mgmtLink 1 (L) RW A list containing at least 4 links: • 1 link to [cmdhDefaults] resource; • At least 1 or more link(s) to [cmdhLimits] resource(s); • At least 1 or more link(s) to [cmdhNetworkAccessRules] resource(s); • At least 1 or more link(s) to [cmdhBuffer] resource(s). ETSI ETSI TS 118 101 V4.15.0 (2022-09) 547 (oneM2M TS-0001 version 4.15.0 Release 4) D.12.1 Resource activeCmdhPolicy A managed node can have one or more sets of [cmdhPolicy] resources assigned as children. The [activeCmdhPolicy] resource is used to provide a link to the currently active set of CMDH policies. This identifies which set of CMDH policies is currently actively in use in the corresponding CSE node. It allows the device management technology to activate a policy set independently of the download of a new set of CMDH policies in order to avoid potential race conditions. The [activeCmdhPolicy] and [cmdhPolicy] resources are children of the same <node> resource to which these policies apply. Figure D.12.1-1: Structure of [activeCmdhPolicy] resource The [activeCmdhPolicy] resource shall contain attributes specified in table D.12.1-1. Table D.12.1-1: Attributes of [activeCmdhPolicy] resource Attributes of [activeCmdhPolicy] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RO See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "activeCmdhPolicy". objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. activeCmdhPolicyLink 1 RW The resource ID of the [cmdhPolicy] resource instance containing the CMDH policies that are currently active for the associated node that is represented by the parent <node> resource. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 548 (oneM2M TS-0001 version 4.15.0 Release 4) D.12.2 Resource cmdhDefaults The [cmdhDefaults] resource is used to define default values that shall be used for CMDH-related parameters when request or response messages issued by Originators (registered AEs or functions inside the CSE itself) need to be sent across the associated reference point do not contain a value for the parameters Event Category, Request Expiration Timestamp, Result Expiration Timestamp, Operation Execution Time, Result Persistence, and/or Delivery Aggregation. Upon receiving When a request or response message needs to be sent across the associated reference point, the entity performing the CMDH processing shall first look if the Event Category parameter is set. If not, the CSE shall use the [cmdhDefEcValue] resources (see below) to determine a value that should be used for Event Category. Then, if any of the parameters Request Expiration Timestamp, Result Expiration Timestamp, Operation Execution Time, Result Persistence or Delivery Aggregation is not set, the entity performing the CMDH processing shall use the [cmdhEcDefParamValues] resources (see below) to populate the missing parameters supported by the respective message type (and only the missing ones). Figure D.12.2-1: Structure of [cmdhDefaults] resource The [cmdhDefaults] resource shall contain attributes specified in table D.12-2-1. Table D.12.2-1: Attributes of [cmdhDefaults] resource Attributes of [cmdhDefaults] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RO See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "cmdhDefaults". objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. mgmtLink 1 (L) RW A list containing at least 2 links: • One or more link(s) to [cmdhDefEcValue] resource(s); and • One or more link(s) to [cmdhEcDefParamValues] resource(s). ETSI ETSI TS 118 101 V4.15.0 (2022-09) 549 (oneM2M TS-0001 version 4.15.0 Release 4) D.12.3 Resource cmdhDefEcValue The [cmdhDefEcValue] resource is used to define a value for the Event Category parameter of an incoming request or response message that needs to be sent across the associated reference point when it is not defined. Upon receiving when a request or response message needs to be sent across the associated reference point, the entity performing the CMDH processing CSE will go through all the [cmdhDefEcValue] resources (in the order of their order attribute), check the requestOrigin and any present requestContext and requestCharacteristics attributes to see if they match (see description of matching), and if they all do, assign the value stored in the defEcValue attribute to the Event Category parameter. Figure D.12.3-1: Structure of [cmdhDefEcValue] resource The [cmdhDefEcValue] resource shall contain attributes specified in table D.12.3-1. Table D.12.3-1: Attributes of [cmdhDefEcValue] resource Attributes of [cmdhDefEcValue] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RO See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "cmdhDefEcValue". objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. order 1 RW The index indicating in which order the [cmdhDefEcValue] resource will be treated by the entity performing the CMDH processing to determine a value for the Event Category parameter. This attribute is a specialization of [objectAttribute] attribute. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 550 (oneM2M TS-0001 version 4.15.0 Release 4) Attributes of [cmdhDefEcValue] Multiplicity RW/ RO/ WO Description defEcValue 1 RW The actual value to use for the Event Category parameter if the conditions expressed in the requestOrigin attribute all match. This attribute is a specialization of [objectAttribute] attribute. requestOrigin 1 RW The requestOrigin attribute is a list of zero or more local AE-IDs, App-IDs, or the strings 'localAE' or 'thisCSE'. When an AE-ID appears in the requestOrigin attribute, the default Event Category value defined inside the defEcValue attribute is applicable for the Event Category if a request message was issued by that specific Application Entity or if a response message is targeting that specific Application Entity. When an App-ID appears in the requestOrigin attribute, the default Event Category value defined inside the defEcValue attribute is applicable for the Event Category if a request message was issued by an AE with that App-ID or if a response message is targeting an AE with that App-ID unless covered by another associated [cmdhDefEcValue] resource with a requestOrigin attribute containing its specific AE-ID. When the string 'localAE' appears in the requestOrigin attribute, the default Event Category value defined inside the defEcValue attribute is applicable for the Event Category for request messages issued by any local AEs or for response messages targeting any local AEs hosted on the node associated to this CMDH policy unless covered by another [cmdhDefEcValue] resource with a requestOrigin attribute containing the specific AE-ID or App-ID of the Originator of the request. When the string 'thisCSE' appears in the requestOrigin attribute, the default Event Category value defined inside the defEcValue attribute is applicable for the Event Category for request messages that are originating from the CSE hosted on the node associated to this CMDH policy or for response messages targeting that CSE. This is only valid if the associated node is an ASN or MN. The set of CMDH policies associated with a particular node shall contain at least one [cmdhDefEcValue] resource that contains 'localAE' in the requestOrigin attribute. The set of CMDH policies associated with a particular ASN or MN shall contain at least one [cmdhDefEcValue] resource that contains 'thisCSE' in the requestOrigin attribute. This attribute is a specialization of [objectAttribute] attribute. D.12.4 Resource cmdhEcDefParamValues The [cmdhEcDefParamValues] resource is used to represent a specific set of default values for the CMDH related parameters Request Expiration Timestamp, Result Expiration Timestamp, Operation Execution Time, Result Persistence and Delivery Aggregation that are applicable for a given Event Category if any of the applicable these parameters are not specified in the request or response. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 551 (oneM2M TS-0001 version 4.15.0 Release 4) Figure D.12.4-1: Structure of [cmdhEcDefParamValues] resource The [cmdhEcDefParamValues] resource shall contain attributes specified in table D.12.4-1. Table D.12.4-1: Attributes of [cmdhEcDefParamValues] resource Attributes of [cmdhEcDefParamValues] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RO See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "cmdhEcDefParamValues". objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. applicableEventCategory 1 RW This attribute defines the event categories for which this set of default parameters defined in this [cmdhEcDefParamValues] resource is applicable. This attribute is a list of zero or more Event Category values, or the string 'default'. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 552 (oneM2M TS-0001 version 4.15.0 Release 4) Attributes of [cmdhEcDefParamValues] Multiplicity RW/ RO/ WO Description When an Event Category value appears in the applicableEventCategory attribute, the set of default parameters defined in this [cmdhEcDefParamValues] resource is applicable for requests associated with that specific Event Category value. When the string 'default' appears in the applicableEventCategory attribute, the set of default parameters defined in this [cmdhEcDefParamValues] resource is applicable for all requests whose associated Event Category value is not listed in the applicableEventCategory attribute of any other provisioned [cmdhEcDefParamValues] resource linked to from the same [cmdhDefaults] resource. A specific Event Category value shall appear at most once in any of the applicableEventCategory attributes of any of the provisioned [cmdhEcDefParamValues] resources linked to from the same [cmdhDefaults] resource. The string 'default' shall appear exactly once in any of the applicableEventCategory attributes of any of the provisioned [cmdhEcDefParamValues] resources linked to from the same [cmdhDefaults] resource. This attribute is a specialization of [objectAttribute] attribute. defaultRequestExpTime 1 RW Default value for the Request Expiration Timestamp parameter in a request when the Request Expiration Timestamp parameter of the request is not set. This attribute is a specialization of [objectAttribute] attribute. defaultResultExpTime 1 RW Default value for the Result Expiration Timestamp parameter in a request or response when the Result Expiration Timestamp parameter of the request or response is not set. This attribute is a specialization of [objectAttribute] attribute. defaultOpExecTime 1 RW Default value for the Operation Execution Time parameter in a request when the Operation Execution Time parameter of the request is not set. This attribute is a specialization of [objectAttribute] attribute. defaultRespPersistence 1 RW Default value for the Result Persistence parameter in a request when the Result Persistence parameter of the request is not set. This attribute is a specialization of [objectAttribute] attribute. defaultDelAggregation 1 RW Default value for the Delivery Aggregation parameter in a request when the Delivery Aggregation parameter of the request is not set. This attribute is a specialization of [objectAttribute] attribute. D.12.5 Resource cmdhLimits The [cmdhLimits] resource is used to define limits for CMDH related parameter values used in requests or response messages to be sent across the associated reference points by Originators (registered AEs or functions inside the CSE itself). When an incoming request or response is processed that does not comply with the limits defined by the corresponding [cmdhLimits] resource, the request message shall be rejected by the CSE. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 553 (oneM2M TS-0001 version 4.15.0 Release 4) Figure D.12.5-1: Structure of [cmdhLimits] resource The [cmdhLimits] resource shall contain attributes specified in table D.12.5-1. Table D.12.5-1: Attributes of [cmdhLimits] resource Attributes of [cmdhLimits] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RO See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "cmdhLimits". objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 554 (oneM2M TS-0001 version 4.15.0 Release 4) Attributes of [cmdhLimits] Multiplicity RW/ RO/ WO Description order 1 RW The index indicating in which order the [cmdhLimits] resource will be treated by the CSE to determine a value for the limit parameters. This attribute is a specialization of [objectAttribute] attribute. requestOrigin 1 RW The requestOrigin attribute is a list of zero or more local AE-IDs, App-IDs, or the strings 'localAE' or 'thisCSE'. When an AE-ID appears in the requestOrigin attribute, the CMDH parameter limits defined inside [cmdhLimits] resources are applicable for requests issued by that specific Application Entity or for responses targeting that specific Application Entity. When an App-ID appears in the requestOrigin attribute, the CMDH parameter limits defined inside [cmdhLimits] resources are applicable for requests issued by an AE or responses targeting an AE with that App-ID unless already covered by another [cmdhLimits] resource with a requestOrigin attribute containing its specific AE-ID. When the string 'localAE' appears in the requestOrigin attribute, CMDH parameter limits defined inside [cmdhLimits] resources are applicable for all local AEs hosted on the node associated to this CMDH policy unless covered by another [cmdhLimits] resource with a requestOrigin attribute containing the specific AE-ID or App-ID of the Originator of the request. When the string 'thisCSE' appears in the requestOrigin attribute, CMDH parameter limits defined inside [cmdhLimits] resources are applicable for all requests that are originating from the CSE hosted on the node associated to this CMDH policy. This is only valid if the associated node is an ASN or MN. The set of CMDH policies associated with a particular node shall contain at least one [cmdhLimits] resource that contains 'localAE' in the requestOrigin attribute. The set of CMDH policies associated with a particular ASN or MN shall contain at least one [cmdhLimits] resource that contains 'thisCSE' in the requestOrigin attribute. This attribute is a specialization of [objectAttribute] attribute. limitsEventCategory 1 RW Allowed values for the Event Category parameter) in a request from or response to any of the Originators indicated in the requestOrigin attribute. This attribute is a specialization of [objectAttribute] attribute. limitsRequestExpTime 1 RW Range of allowed values for the Request Expiration Timestamp parameter in a request of any of the Originators indicated in the requestOrigin attribute. This attribute is a specialization of [objectAttribute] attribute. limitsResultExpTime 1 RW Range of allowed values for the Result Expiration Timestamp parameter in a request from or response to any of the Originators indicated in the requestOrigin attribute. This attribute is a specialization of [objectAttribute] attribute. limitsOpExecTime 1 RW Range of allowed values for the Operation Execution Time parameter in a request of any of the Originators indicated in the requestOrigin attribute. This attribute is a specialization of [objectAttribute] attribute. limitsRespPersistence 1 RW Range of allowed values for the Result Persistence parameter in a request of any of the Originators indicated in the requestOrigin attribute. This attribute is a specialization of [objectAttribute] attribute. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 555 (oneM2M TS-0001 version 4.15.0 Release 4) Attributes of [cmdhLimits] Multiplicity RW/ RO/ WO Description limitsDelAggregation 1 RW List of allowed values for the Delivery Aggregation parameter in a request of any of the Originators indicated in the requestOrigin attribute. This attribute is a specialization of [objectAttribute] attribute. D.12.6 Resource cmdhNetworkAccessRules The [cmdhNetworkAccessRules] resource is used to define the rules for usage of Underlying Networks for forwarding information across the associated reference point of the node associated to this set of CMDH policies to other CSEs during processing of CMDH-related requests in a CSE. When request or response messages need to be sent across the associated reference point, the associated node, an incoming request is processed by a CSE, it can only use Underlying Networks for forwarding any information to other CSEs in compliance with the rules defined by the corresponding [cmdhNetworkAccessRules] resource. If a pending request cannot be successfully completed in compliance with the rules defined in the corresponding [cmdhNetworkAccessRules] resource, that request shall be responded to with an unsuccessful response in case it has not already been accepted by the Receiver CSE or it has to be purged. Error reporting on failed CMDH processing depends on error reporting parameters. Figure D.12.6-1: Structure of [cmdhNetworkAccessRules] resource If a [cmdhNetworkAccessRules] resource has no mgmtLink attribute to [cmdhNwAccessRules] resources (i.e. multiplicity of 0), request or response messages that match with the applicableEventCategories attribute (see description of attributes in table D.12.6-1) will not be allowed to use any Underlying Network for forwarding information, i.e. such messages need to be rejected. The [cmdhNetworkAccessRules] resource shall contain attributes specified in table D.12.6-1. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 556 (oneM2M TS-0001 version 4.15.0 Release 4) Table D.12.6-1: Attributes of [cmdhNetworkAccessRules] resource Attributes of [cmdhNetworkAccessRules] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RO See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "cmdhNetworkAccessRules". objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. applicableEventCategories 1 RW This attribute defines for which requests or responses the rules contained in [cmdhNwAccessRule] resources linked from this [cmdhNetworkAccessRules] resource shall be applied. This attribute is a list of zero or more Event Category values, or the string 'default'. When an Event Category value appears in the applicableEventCategories attribute, the network usage rules defined inside [cmdhNwAccessRule] child resources are applicable for requests or responses associated with that specific Event Category value. When the string 'default' appears in the applicableEventCategories attribute, the network usage rules defined inside [cmdhNwAccessRule] child resources are applicable for all requests or responses whose associated Event Category value is not listed in the applicableEventCategories attribute of any other provisioned [cmdhNetworkAccessRules] resource linked to from the same [cmdhPolicy] resource. A specific Event Category value shall appear at most once in any of the applicableEventCategories attributes of any of the provisioned [cmdhNetworkAccessRules] resources linked to from the same [cmdhPolicy] resource. The string 'default' shall appear exactly once in any of the applicableEventCategories attributes of any of the provisioned [cmdhNetworkAccessRules] resources linked to from the same [cmdhPolicy] resource. This attribute is a specialization of [objectAttribute] attribute. mgmtLink 0..1 (L) RW List of link(s) to [cmdhNwAccessRule] resource(s). D.12.7 Resource cmdhNwAccessRule The [cmdhNwAccessRule] resource is used define limits in usage of specific Underlying Networks for forwarding information to other CSEs during processing of CMDH-related requests across the associated reference point. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 557 (oneM2M TS-0001 version 4.15.0 Release 4) Figure D.12.7-1: Structure of [cmdhNwAccessRule] resource Requests or responses matching the applicableEventCategories attribute of the parent [cmdhNetworkAccessRules] resource of this [cmdhNwAccessRule] resource are processed for forwarding via the associated reference points to other CSEs. The Underlying Network(s) subject to the rules represented by an instance of the [cmdhNwAccessRule] resource allowed for potential communication of those requests or responses are indicated by the targetNetwork attribute. The allowed schedule is indicated by the <schedule> resource pointed at by the mgmtLink attribute (see description of attributes in table D.12.7-1). ETSI ETSI TS 118 101 V4.15.0 (2022-09) 558 (oneM2M TS-0001 version 4.15.0 Release 4) The [cmdhNwAccessRule] resource shall contain attributes specified in table D.12.7-1. Table D.12.7-1: Attributes of [cmdhNwAccessRule] resource Attributes of [cmdhNwAccessRule] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RO See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "cmdhNwAccessRules". objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. targetNetwork 1 RW The targetNetwork attribute defines for which Underlying Networks the usage limits contained in this [cmdhNwAccessRule] resource shall be applied. The targetNetwork attribute is a list of one or more strings identifying identifiers of Underlying Networks or response messages or the string 'default'. When an identifier of an Underlying Network appears in the targetNetwork attribute, the usage limits contained in this [cmdhNwAccessRule] resource shall be applied for usage of that specific Underlying Network when processing request or response messages matching with the parent [cmdhNetworkAccessRules] resource's applicableEventCategories attribute. When the string 'default' appears in the targetNetwork attribute, the usage limits contained in this [cmdhNwAccessRule] resource shall be applied for usage of all Underlying Networks that are not listed with their specific identifiers in the targetNetwork attribute of any other [cmdhNwAccessRule] linked to from the same parent [cmdhNetworkAccessRules] resource when processing request or response messages matching with the associated [cmdhNetworkAccessRules] resource's targetNetwork attribute. Each Underlying Network identifier or the string 'default' shall appear at most once in any of the targetNetwork attributes of any of the provisioned [cmdhNwAccessRule] child resources linked to by the same parent [cmdhNetworkAccessRules] resource. This attribute is a specialization of [objectAttribute] attribute. minReqVolume 1 RW Minimum amount of data that needs to be aggregated before any of the Underlying Networks matching with the targetNetwork attribute of this [cmdhNwAccessRule] resource can be used for forwarding information. spreadingWaitTime 1 RW • This parameter consists of a number SWT such that before accessing the underlying network (typically to forward an incoming request), the CSE will wait for an additional amount of time randomly chosen between 0 and SWT. This attribute is a specialization of [objectAttribute] attribute. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 559 (oneM2M TS-0001 version 4.15.0 Release 4) Attributes of [cmdhNwAccessRule] Multiplicity RW/ RO/ WO Description backOffParameters 1 RW Parameters that define how usage of any of the Underlying Networks matching with the targetNetwork attribute of this [cmdhNwAccessRule] resource shall be handled by field nodes when attempts to use such networks have failed. These parameters only apply to communication attempts by field nodes. The backOffParameters attribute can either: - Consist of the following values: • An initial back-off time IBT that defines how long a CSE needs to wait before attempting to use a specific Underlying Network again after a first failed attempt. • An additional back-off time ABT increment that defines by how much the back-off time shall be increased after each additional consecutive failed attempt to use the same Underlying Network without success. • A maximum back-off time MBT that defines the maximum wait time before attempting to use an Underlying Network again after previous failures. • An optional random back-off time RBT that will make the network access actually occur randomly in a time window starting at IBT+n.ABT and ending at IBT+n.ABT+RBT (if RBT is not present, then no randomization occurs and the access takes place at IBT+n.ABT). • In which case the back-off timers apply for any action attempted onto the network (registration to the network, opening of data session, etc.). - Or consist of an array of several elements, each composed like this [NWA, IBT, ABT, MBT, (optional RBT)] where IBT, ABT, MBT and RBT are defined above, and where NWA is the name of a specific action that is actually attempted on the network. The present document defines the following network action names, that can be used when the CSE knows that it uses an underlying network where these actions are valid: • "cellular-registration" for an IMSI CS-Registration onto 3GPP-compliant cellular networks. • "cellular-attach" for a GPRS Attach onto 3GPP-compliant cellular networks. • "cellular-pdpctxact" for a PDP Context Activation onto 3GPP-compliant cellular networks. • "cellular-sms" for SMS originating from this CSE onto 3GPP-compliant cellular networks. • "default" for all other actions not already declared in this backOffParameters attribute (this action will be used by the CSE when it does not know which kind of underlying network it uses). • In which case the back-off timers apply only for the specified actions. This attribute is a specialization of [objectAttribute] attribute. otherConditions 0..1 (L) RW List of additional conditions that need to be fulfilled before any of the Underlying Networks matching with the targetNetwork attribute of this [cmdhNwAccessRule] resource can be used for forwarding information to other CSEs. This attribute is a specialization of [objectAttribute] attribute. mgmtLink 1 RW Link to an instance allowedSchedule of a <schedule> resource as defined in clause 9.6.9. The linked <schedule> instance shall be a child of the <node> resource to which this resource corresponds. This attribute is a specialization of [objectAttribute] attribute. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 560 (oneM2M TS-0001 version 4.15.0 Release 4) D.12.8 Resource cmdhBuffer The [cmdhBuffer] resource is used to define limits in usage of buffers for temporarily storing information that needs to be forwarded to other nodes during processing of CMDH-related requests in a CSE. When an incoming request or response message needs to be sent is processed by a node, it can only use buffers for temporary storage in compliance with the rules defined by the corresponding [cmdhBuffer] resource. If a request cannot be processed in compliance with the rules defined in the corresponding [cmdhBuffer] resource, that request shall either be rejected in case it has not already been accepted by the Receiver CSE or it has to be purged. Error reporting on failed CMDH processing depends on error reporting parameters. Figure D.12.8-1: Structure of [cmdhBuffer] resource The [cmdhBuffer] resource shall contain attributes specified in table D.12.8-1. Table D.12.8-1: Attributes of [cmdhBuffer] resource Attributes of [cmdhBuffer] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RO See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "cmdhBuffer". objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. applicableEventCategory 1 RW The applicableEventCategory attribute defines for which request or response messages the limits contained in this [cmdhBuffer] resource shall be applied. The applicableEventCategory attribute is a list of zero or more Event Category values, or the string 'default'. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 561 (oneM2M TS-0001 version 4.15.0 Release 4) Attributes of [cmdhBuffer] Multiplicity RW/ RO/ WO Description When an Event Category value appears in the applicableEventCategory attribute, the buffer usage limits defined inside this [cmdhBuffer] resource are applicable for request or response messages associated with that specific Event Category value. When the string 'default' appears in the applicableEventCategory attribute, the buffer usage limits defined inside this [cmdhBuffer] resource are applicable for all request or response messages whose associated Event Category values not listed in the applicableEventCategory attribute of any other provisioned [cmdhBuffer] resource linked to from the same [cmdhPolicy] resource. A specific Event Category value shall appear at most once in any of the applicableEventCategory attributes of any of the provisioned [cmdhBuffer] resources linked to from the same [cmdhPolicy] resource. The string 'default' shall appear exactly once in any of the applicableEventCategory attributes of any of the provisioned [cmdhBuffer] resources linked to from the same [cmdhPolicy] resource. This attribute is a specialization of [objectAttribute] attribute. maxBufferSize 1 RW Maximum amount of memory that can be used for buffering requests matching with the applicableEventCategory attribute of this [cmdhBuffer] resource. This attribute is a specialization of [objectAttribute] attribute. storagePriority 1 RW Storage priority for data that is stored for buffering request or response messages matching with the applicableEventCategory attribute of this [cmdhBuffer] resource. The storage priority defines the how to handle purging of buffered data when buffer memory is exhausted and buffered request or response messages need to be purged. Buffered request or response messages associated with a lower storage priority shall be purged before buffered request or response messages with a higher storage priority. The range of storage priority is from 1 to 10. This attribute is a specialization of [objectAttribute] attribute. D.13 Resource storage The [storage] resource is used to share information regarding the storage on the device. The resource for [storage] Management Object is to be recreated after each storage media change. The [storage] resource is a specialization of the <mgmtObj>resource. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 562 (oneM2M TS-0001 version 4.15.0 Release 4) Figure D.13-1: Structure of [storage] resource The [storage] resource shall contain the child resources specified in table D.13-1. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 563 (oneM2M TS-0001 version 4.15.0 Release 4) Table D.13-1: Child resources of [storage] resource Child Resources of [storage] Child Resource Type Multiplicity Description [variable] <subscription> 0..n See clause 9.6.8 where the type of this resource is described. [variable] <semanticDescriptor> 0..n See clause 9.6.30. The [storage] resource shall contain the attributes specified in table D.13-2. Table D.13-2: Attributes of [storage] resource Attributes of [storage] Multiplicity RW/ RO/ WO Description resourceType 1 RO See clause 9.6.1.3. resourceID 1 RO See clause 9.6.1.3. resourceName 1 WO See clause 9.6.1.3. parentID 1 RO See clause 9.6.1.3. expirationTime 1 RW See clause 9.6.1.3. accessControlPolicyIDs 0..1 (L) RW See clause 9.6.1.3. creationTime 1 RO See clause 9.6.1.3. lastModifiedTime 1 RO See clause 9.6.1.3. labels 0..1(L) RW See clause 9.6.1.3. mgmtDefinition 1 WO See clause 9.6.15. Has fixed value "storage" to indicate the resource is for memory management. objectIDs 0..1 (L) WO See clause 9.6.15. objectPaths 0..1 (L) WO See clause 9.6.15. description 0..1 RW See clause 9.6.15. UUID 0..1 WO The uuid of the storage device. This attribute is a specialization of [objectAttribute] attribute. storageType 0..1 RO Indicates the type of storage. 0 indicates internal and 1 indicates external. This attribute is a specialization of [objectAttribute] attribute. writeSpeed 0..1 RO Indicates the write speed of storage device. This attribute is a specialization of [objectAttribute] attribute. readSpeed 0..1 RO Indicates the read speed of storage device. This attribute is a specialization of [objectAttribute] attribute. availStorage 1 RO Indicates the current available amount of memory. 1 MB = 106 bytes. This attribute is a specialization of [objectAttribute] attribute. totalStorage 1 RO Indicates the total amount of memory available for the. 1 MB = 106 bytes. This attribute is a specialization of [objectAttribute] attribute. storagePresence 0..1 RW Indicates current presence status of memory card. 0 indicates card is ejected, 1 indicates card is inserted. This attribute is a specialization of [objectAttribute] attribute. status 0..1 RW Indicates current operation status of storage. 1 - indicates storage is ready, 0 indicates storage is busy. This attribute is a specialization of [objectAttribute] attribute. numberOfMounts 0..1 RO Indicates number of successful mounts of the storage. This attribute is a specialization of [objectAttribute] attribute. numberOfForcedUnmou nts 0..1 RO Indicates number of forced unmounts of the storage. This attribute is a specialization of [objectAttribute] attribute. fileSystem 0..1 RW Indicates the filesystem type used on the mounted storage. This attribute is a specialization of [objectAttribute] attribute. storageName 0..1 RW Indicates name of the mounted storage. This attribute is a specialization of [objectAttribute] attribute. mountingPoint 0..1 RW Indicates mounting point of the mounted storage. This attribute is a specialization of [objectAttribute] attribute. format 0..1 RW The action that allows to format the mounted storage. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of [objectAttribute] attribute. unmount 0..1 RW The action that allows to safety eject storage device. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of [objectAttribute] attribute. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 564 (oneM2M TS-0001 version 4.15.0 Release 4) Attributes of [storage] Multiplicity RW/ RO/ WO Description mountOptions 0..1 RO Indicates additional file system specific and file system independent mount options that indicate specific behaviours of the mount point as well as the capabilities of the underlying file system. writable 1 RO Indicates whether the storage volume is mounted as read/write ("TRUE") or read-only ("FALSE"). This attribute is a specialization of [objectAttribute] attribute. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 565 (oneM2M TS-0001 version 4.15.0 Release 4) Annex E (informative): CSE Minimum Provisioning The present clause defines the minimum set of resources instantiated in a CSE node with the scope to make it ready to provide services to entities that will register to. For the purpose of the initial configuration two roles are identified: • superuser: this role allows the full CSE control according to infrastructure provider policies. Only one superuser role is allowed per CSE; • user: is the role associated to an AE that will register itself to Registrar CSE. More than one user roles are allowed per CSE. More than one application can access to CSE with the same role. Superuser role may be created with the following associated resources: 1) Definition or assignment of CSE-ID name that may be unique in the node hosting the CSE to be instantiated. 2) Creation of <CSEBase> resource with name equal to CSE-ID. 3) Creation of following child resources belonging to a tree with <CSEBase> as root: a) <accessControlPolicy> child resource enabling full access control for superuser's invoked operations to the tree resources. Subsequent created resources may have accessControlPolicyIDs attribute addressing this <accessControlPolicy> resource. b) <AE> child resource to be used as registered AE dedicated to superuser related activities. Each user role may be created with the following associated resources: 1) Definition or assignment of an AE name that may be unique in the CSE. 2) Creation of <AE> child resource of <CSEBase> resource named as described in step 1, to be used as registered application dedicated to user related activities. 3) Creation of following child resources belonging to a tree with <AE> as root: a) <accessControlPolicy> resource enabling partial access control (e.g. these resources cannot be deleted be the user, superuser's resources can only be read by user) for user's invoked operations to the tree resources. <AE> resource can be updated with accessControlPolicyIDs attribute addressing <accessControlPolicy> resource. The above described operations may be executed in the node in order provide the elements and the access control privileges required to provide the initial access to resource operations. Same user can create more than one <AE> resources and other child resource types. Once user role resource trees have been created the registered AE associated to <AE> resource (defined for a user role in step 2) is able to create its own <container> resource to store business logic application data that can be shared to other registered AEs in a controlled way acting on its own <accessControlPolicy> resource. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 566 (oneM2M TS-0001 version 4.15.0 Release 4) Annex F (informative): Interworking/Integration of non-oneM2M solutions and protocols F.1 Introduction Non-oneM2M solutions are currently installed and will continue to evolve and to be adopted in future for specific deployments. Some of these solutions are the evolution of M2M that have a long history and significant mass installations (e.g. the PLC-related protocols commonly used in building and industrial automation), and are also significantly represented by proprietary solutions, especially in terms of semantic of the data model. The non-oneM2M solutions are potentially used for: • Legacy deployment: such solutions can make use of both, proprietary or standard protocols; often proprietary data models and functionality are combined with the use of standard protocol. • New system deployment that privileges the vertical optimization rather the horizontal aspects. • Area network deployment for which native IP based oneM2M is perceived as not optimized respect to the used technology. For those non-oneM2M solutions oneM2M needs to provide a means to enable: • Mixed deployment that are partially oneM2M compliant and partially not, where the oneM2M System provides the solution to integrate multiple technologies (e.g. to add new technologies on top of old installations). • Hybrid deployment that are still using non-oneM2M protocol (proprietary/standard) and want to use at the same time some of the oneM2M functionalities. A typical case is the exchange of heavy data traffic outside the CSE (e.g. for video surveillance), together with the use of CSE services for control and light traffic exchange. • Behaviour of such non-oneM2M solution is out of scope in present document, but there is some market need to communicate with devices in non-oneM2M domain (so called 'NoDN'). Since NoDN does not have any knowledge about the oneM2M system, AE will take responsibility to bridge those two worlds which are Interworking Proxy Entities (IPEs). • The present annex provides oneM2M guidance regarding how to implement interworking between the oneM2M solution and external non-oneM2M systems. F.2 Interworking with non-oneM2M solutions through specialized interworking applications The solution is based on the use of specialized interworking Application Entities that are interfaced to the CSE via standard Mca reference points. Such specialized applications are named Inter-working Proxy and are described in figure F.2-1. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 567 (oneM2M TS-0001 version 4.15.0 Release 4) Figure F.2-1: Interworking Proxy The Inter-working Proxy Application Entity (IPE) is characterized by the support of a non-oneM2M reference point, and by the capability of remapping the related data model to the oneM2M resources exposed via the Mca reference point. This is typically supported via a full semantic inter-working of the data model used by the non oneM2M and a related protocol inter-working logic, and, depending on the complexity of the non oneM2M data model, can imply the definition of a complex set of resources built via the basic oneM2M ones, or a simple direct mapping of the communication via the containers and its variants (e.g. <container>, <flexContainer>, and <timeSeries>). The approach enables a unique solution for enabling communications among different protocols, catering for different level of inter-working including protocol inter-working, semantic information exchange, data sharing among the different solution and deployments. And enables the offering additional values respect to what is today available via existing protocols and proprietary service exposures. Figure F.2-2 shows the typical scenarios supported by the oneM2M architecture in the context of inter-working. The combination of the different scenarios allows mixed deployments. NOTE: The additional option of an inter-working proxy embedded in the CSE as a module with an internal specified interface is under consideration. Figure F.2-2: Scenarios Supported by oneM2M Architecture These scenarios are applicable to the CSE with the AE as application dedicated node, in the application Service Node, in the Middle Node and in the infrastructure Node. Non oneM2M interface AE: Interworking Proxy Mca Non oneM2M interface Proxy Mca Hybrid Application CSE(s) Non oneM2M interface Mca Inter-working Proxy Mca ( 1) Hybrid Application Non oneM2M interface Mca Non oneM2M Application Non oneM2M interface Inter-working Proxy Mca oneM2M native Application Mca ETSI ETSI TS 118 101 V4.15.0 (2022-09) 568 (oneM2M TS-0001 version 4.15.0 Release 4) Figure F.2-3 provides an example of the use of such capabilities an area network adopting specific protocols, e.g. Zigbee Telco Profile and Mbus using COSEM Data model. Figure F.2-3: Translation of non-oneM2M Data Model to oneM2M Specific Data Model There exist three variants of how interworking through an Inter-working Proxy Application Entity over Mca can be supported: 1) Interworking with full mapping of the semantic of the non-oneM2M data model to Mca. This is typically supported via a full semantic inter-working of the data model used by the non-oneM2M solution and the generic data model used in oneM2M (based on usage of containers and its variants) for exchanging application data. The IPE includes the related protocol inter-working logic. Depending on the complexity of the non-oneM2M data model, this can imply that the Inter-working Proxy Application Entity constructs a complex set of resources (built from the basic oneM2M resources) in the CSE. These resources are oneM2M representations of the non-oneM2M data model and are exposed by the IPE on Mca. They enable CSEs and AEs to access the entities in the non-oneM2M via the IPE. The benefit of this level of interworking is that it offers a unique solution for enabling communications among different protocols. The data model of the non-oneM2M solution determines its representation (the names, data types and structure of the oneM2M sub resources) in the M2M System. It caters for different levels of inter- working including protocol inter-working, semantic information exchange, data sharing among the different solution and deployments. It enables offering additional values with respect to what is today available via existing protocols and proprietary service exposures. NOTE: With this level of interworking an M2M Application can access non-oneM2M solutions without the need to know the specific protocol encoding for these solutions. A drawback is that the IPE also potentially needs to interwork between a non-oneM2M security solution and oneM2M security. E.g. it needs to be the termination point of any non-oneM2M specific encryption. 2) Interworking using containers for transparent transport of encoded non-oneM2M data and commands via Mca. In this variant non-oneM2M data and commands are transparently packed by the Inter-working Proxy Application Entity into containers for usage by the CSEs and AEs. In this case the CSE or AE needs to know the specific protocol encoding rules of the non-oneM2M Solution to be able to en/de-code the content of the containers. 3) Interworking using a retargeting mechanism. This is typically supported via gateway system which is capable to map operations on oneM2M world into non-oneM2M world. Sensor/Meter CSE Mbus/COSEM AE Inter-working Proxy Mca Utility Application Mca Sensor/Meter Zigbee telco Profile AE Inter-working Proxy Mca Application Service Node CSE Mcc Infrastructure Node specific Data model Awareness Common Data model Awareness ETSI ETSI TS 118 101 V4.15.0 (2022-09) 569 (oneM2M TS-0001 version 4.15.0 Release 4) Either CSE or AE provided mapped interface as oneM2M resource structure, and when the operation is executed on the resource structure, the operations will be retargeted to the IPE. This mapping may be provided for reverse direction, like status change of the non-oneM2M device will be reflected as the UPDATE on the oneM2M container or its variants. F.3 Interworking versus integration of non-oneM2M solutions Interworking: With the approach given above - where specialized interworking applications (IPEs) allow to interact with any non- oneM2M system via the Mca interface - proprietary non-oneM2M solutions as well as non-oneM2M solutions that follow open standards can be interworked with the oneM2M System. Integration: When it is desired to make a certain type of non-oneM2M solution (e.g. some type of non-IP based Area Network) a permanent part of the deployed oneM2M Solution then the functionality of the Inter-working Proxy Application Entity can be integrated into the CSE of an Application Node. This is called "Integration" non-oneM2M solutions. F.4 Entity-relation representation of non-IP based M2M Area Network F.4.0 Overview Figure F.4.0-1 provides an entity-relation model that represents a non-IP based M2M area network as well as its relationship to an Interworking Proxy Application Entity (IPE). ETSI ETSI TS 118 101 V4.15.0 (2022-09) 570 (oneM2M TS-0001 version 4.15.0 Release 4) Figure F.4.0-1: Generic entity-relation diagram for an IPE and an M2M Area Network running legacy devices This entity-relation diagram is e.g. applicable to the following M2M Area Networks: • ZigBee area network. • DLMS/COSEM area network. • Zwave area network. • BACnet area network. • ANSI C12 area network. • Mbus area network. F.4.1 Responsibilities of Interworking Proxy application Entity (IPE) More specifically, the IPE is responsible to: • create oneM2M resources representing the M2M Area Network structure (devices, their applications and interfaces) in the oneM2M Service Capability Layer, accessible via Mca; • manage the oneM2M resources in case the M2M Area Network structure changes; • discover the M2M Area Network structure and its changes automatically if this is supported by the technology of the M2M Area Network. NOTE: Mapping principles of the none-oneM2M information model into oneM2M resources are not specified in this version of the specification. IPE M2M Area Network 1 n device Application Interface Data Field Method 1 1 1 1 1 n n n n n ETSI ETSI TS 118 101 V4.15.0 (2022-09) 571 (oneM2M TS-0001 version 4.15.0 Release 4) Annex G: Void ETSI ETSI TS 118 101 V4.15.0 (2022-09) 572 (oneM2M TS-0001 version 4.15.0 Release 4) Annex H (informative): Object Identifier Based M2M Device Identifier H.1 Overview of Object Identifier In M2M systems, it is required for devices to be distinguishable from one another through some kind of ID system. In other words, the ID which is allocated to the device is globally unique to ensure the proper operation of M2M systems, such as finding and connecting devices. In relation to this requirement, the use of Object Identifiers may provide a convenient method to ensure the global uniqueness of M2M devices. The Object Identifier (OID) is an identification mechanism jointly developed by ITU-T and ISO/IEC which can be applied to objects, concepts, and all kinds of tangible or intangible things. OID uses a hierarchical tree structure and is represented as a sequence of integer values, as shown in figure H.1-1. OID consists of several segments called arcs which provide placeholders for identification and description in the hierarchal tree. The first arc can take the following values: • itu-t (0); • iso (1); and • joint-iso-itu-t (2). An OID is hierarchically allocated to an entity (e.g. an organization, a country, etc.) which has the authority to define lower arcs. For example, ITU-T can manage and allocate lower arcs below itu-t (0), and ISO can allocate lower arcs below iso (1). The general procedure regarding the use of OID is described in Recommendation ITU-T X.660 | ISO/IEC 9834-1 [i.24]. Root 0 (ITU-T) 1 (ISO) 2 (Joint ISO/ ITU-T) 0 2 … 39 0 2 … 39 0 27 ... 450 480 481 410 1 Root Arc 1 st Arc 2nd Arc 3rd Arc Figure H.1-1: International OID Tree H.2 OID Based M2M Device Identifier H.2.0 Overview An M2M device will be identified individually through a globally unique ID system. This clause explains how to allocate a globally unique ID to each M2M device by using the OID scheme. M2M device ID is an example which shows that OID can be applied to any M2M identifiers which need globally unique IDs. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 573 (oneM2M TS-0001 version 4.15.0 Release 4) The M2M device ID consists of a higher arc and a sequence of four arcs. It takes the form of {(higher arc) (x) (y) (z) (a)} as illustrated in figure H.2.0-1. The higher arc is defined and managed according to the OID procedure. Each arc in the remaining sequence of four arcs represents the manufacturer ID, product model ID, serial number ID, and expanded ID, respectively. (higher arc) (x) (y) (z) (a) M2M Device Indication ID Manufacturer ID Model ID Serial No ID . Expanded ID Figure H.2.0-1: M2M Device ID H.2.1 M2M Device Indication ID - (higher arc) The M2M Device Indication ID (higher arc) represents a globally unique identifier for the M2M device. The composition of the highest arc is variable and may be composed of several sub-arcs. The higher arc is assigned and managed by ITU-T or ISO. H.2.2 Manufacturer ID - (x) The 1st arc (x) among the sequential 4 arcs is used to identify the manufacturer which produces the M2M device. The first arc (x) is managed and allocated by the authority related with (higher arc). H.2.3 Model ID - (y) The 2nd arc (y) among the sequential 4 arcs identifies the device model produced by the manufacturer x. The second arc is managed and allocated by the manufacturer represented by the (x) arc. H.2.4 Serial Number ID - (z) The 3rd arc (z) among the sequential 4 arcs is for identifying the serial number of the device model y. The third arc is managed and allocated by the manufacturer represented by the (x) arc. H.2.5 Expanded ID - (a) The 4th arc (a) among the sequential 4 arcs is for identifying the legacy device which operates under the M2M device. The 4th arc for Expanded ID is allocated by the M2M device by adding a 4th arc to its device ID {(higher arc) (x) (y) (z)}. Therefore, the ID of legacy device which operates under the M2M device takes the form of {(higher arc) (x) (y) (z) (a)}. The fourth arc is managed and allocated by the M2M device. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 574 (oneM2M TS-0001 version 4.15.0 Release 4) H.3 Example of M2M device ID based on OID Assume an M2M Device ID of {0 2 481 1 100 3030 10011}. The M2M device ID can be interpreted as follows: • (0 2 481 1) in {0 2 481 1 100 3030 10011} - represents the M2M Device Indication ID (higher arc): - (0) in {0 2 481 1 100 3030 10011} - identifies the managing organization ITU-T. - (2) in {0 2 481 1 100 3030 10011} - identifies "Administration". - (481) in {0 2 481 1 100 3030 10011} - identifies the data country code for Korea. - (1) in {0 2 481 1 100 3030 10011} - identifies an M2M device. • (100) in {0 2 481 1 100 3030 10011} - identifies the device Manufacturer. • (3030) in {0 2 481 1 100 3030 10011} - identifies the device Model. • (10011) in {0 2 481 1 100 3030 10011} - identifies the device Serial number. ETSI ETSI TS 118 101 V4.15.0 (2022-09) 575 (oneM2M TS-0001 version 4.15.0 Release 4) Annex I: Void ETSI ETSI TS 118 101 V4.15.0 (2022-09) 576 (oneM2M TS-0001 version 4.15.0 Release 4) Annex J (normative): Syntaxes for content based discovery of <contentInstance> J.1 Introduction This annex specifies the syntax for contentFilterQuery filterCriteria (see clause 8.1.2). The syntax of string for contentFilterQuery parameter shall be chosen by contentFilterSyntax parameter. J.2 'jsonpath' query syntax This syntax of query is applicable in the case of stored data in the <contentInstance> resource which is indicated as JSON based according to the contentInfo attribute value. The target of evaluation shall be located by JSON path like addressing, which is constructed following rules: • The entire data shall be referred by '$(dollar sign)' character. • The notation '[n]' shall refer n-th member of JSON Array. • The operator '.(dot)' followed by name shall refer member of JSON Objects. • The name shall be surrounded with '"(quote)' characters when the name contains special characters, such as '$', '.', ' (space)', '[', ']', '{', and '}'. • The ' (space)' character shall be inserted between reserved keyword and other component of query string. The following keywords shall be used to construct query string when contentFilterSyntax parameter was 'JSON-path'. Table J.2-1: Reserved keywords for JSON-Path query syntax Keyword Condition Applicability EQ (Equals) When the target value equals with query. String or number NE (Not Equals) When the target value does not equal with query. String or number GT (Greater Than) When the target value was greater than number given as query. Number only LT (Less Than) When the target value was less than number given as query. Number only GE (Greater or Equals) When the targeted value was greater or equals with number given as query. Number only LE (Less or Equals) When the targeted value was less or equals with number given as query. Number only MATCH When the targeted value contains given string. String only AND Concatenation of query which evaluated as AND combination logic. Query-string OR Concatenation of query-string which evaluated as OR combination logic. Query-string ETSI ETSI TS 118 101 V4.15.0 (2022-09) 577 (oneM2M TS-0001 version 4.15.0 Release 4) Annex K (informative): Bibliography • IETF RFC 6874: "Representing IPV6 Zone Identifiers in Address Literals and Uniform Resources Identifiers". ETSI ETSI TS 118 101 V4.15.0 (2022-09) 578 (oneM2M TS-0001 version 4.15.0 Release 4) History Document history V4.15.0 September 2022 Publication |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 1 Scope | The present document supports the requirements of ETSI EN 305 174-8 [9] providing a framework for, and detailing, the necessary implementation procedures. The present document specifically extends the end-of-life aspects of ICT equipment to the treatment of components and sub-assemblies replaced during maintenance procedures. With reference to Figure 2 (from ETSI EN 305 174-8 [9]), which is a schematic representation of the different broadband networks implemented by telecommunications operators, the ICT equipment covered comprises the ITE and NTE in ICT sites together with the Terminal Equipment (TE) and Network Interface Unit (NIU) at the Customer Premises (CP) together with other User Equipment (UE) such as mobile telephones and other devices. Figure 2: Schematic of fixed and mobile communication networks Annex A details all actions in terms of treatment of e-waste, in accordance with the standards, from the perspective of recycler. |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 2 References | |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. Terrestrial mobile access infrastructure NDC1 OS2 OS2 Non “IT End-use” equipment Transport network Distribution network Access network LOC TE Backhaul network Core network UE “End-use IT” equipment Fixed access infrastructure Satellite UE “End-use IT” equipment OS2 FN NIU “End-use IT” equipment Cable access infrastructure Satellite mobile access infrastructure Customer premises (CP) BS site R Access network 1 For cable access networks this is termed “Master head-end/OS” 2 For cable access networks this is termed “Local head-end/OS” NDN NDN NDN NDN NDN NDN NDN NDN ETSI ETSI TS 105 174-8 V1.2.1 (2019-12) 9 The following referenced documents are necessary for the application of the present document. [1] CENELEC EN 50614: "Requirements for the preparing for re-use of waste electrical and electronic equipment". [2] CENELEC EN 50625-1: "Collection, logistics & Treatment requirements for WEEE - Part 1: General treatment requirements". [3] CENELEC EN 50625-2-1: "Collection, logistics & Treatment requirements for WEEE - Part 2-1: Treatment requirements for lamps". [4] CENELEC EN 50625-2-2: "Collection, logistics & Treatment requirements for WEEE - Part 2-2: Treatment requirements for WEEE containing CRTs and flat panel displays". [5] CENELEC EN 50625-2-3: "Collection, logistics & Treatment requirements for WEEE - Part 2-3: Treatment requirements for temperature exchange equipment and other WEEE containing VFC and/or VHC". [6] CENELEC CLC/TS 50625-3-1: "Collection, logistics & Treatment requirements for WEEE - Part 3-1: Specification for de-pollution - General". [7] CENELEC CLC/TS 50625-3-2: "Collection, logistics & Treatment requirements for WEEE - Part 3-2: Technical specification for de-pollution - Lamps". [8] Directive 2012/19/EU of the European Parliament and of the Council of 4 July 2012 on waste electrical and electronic equipment (WEEE). [9] ETSI EN 305 174-8: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Lifecycle Resource Management; Part 8: Management of end of life of ICT equipment (ICT waste/end of life)". |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 105 174-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 1: Overview, common and generic aspects". [i.2] CENELEC CLC/TS 50625-3-3: "Collection, logistics & treatment requirements for WEEE. Technical Specification for de-pollution. WEEE containing CRTs and flat panel displays". [i.3] CENELEC TS 50625-4: "Collection, logistics & treatment requirements for WEEE - Technical Specification for the collection and logistics associated with WEEE". [i.4] CENELEC TS 50625-5: "Collection, logistics & Treatment requirements for WEEE - Technical Specification for the final treatment of WEEE fractions - Copper and precious metals". [i.5] CENELEC EN 50625-2-4: "Collection, logistics & Treatment requirements for WEEE. Treatment requirements for photovoltaic panels". [i.6] CENELEC CLC/TS 50625-3-4: "Collection, logistics & treatment requirements for WEEE. Technical Specification for de-pollution. Temperature exchange equipment". [i.7] CENELEC CLC/TS 50625-3-5: "Collection, logistics & Treatment requirements for WEEE. Technical specification for de-pollution - Photovoltaic panels". ETSI ETSI TS 105 174-8 V1.2.1 (2019-12) 10 [i.8] CENELEC CLC/TS 50625-6: "Collection, logistics & treatment requirements for WEEE - Report on the alignment between Directive 2012/19/EU and EN 50625 series standards and EN 50614". |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 3 Definition of terms, symbols and abbreviations | |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 305 174-8 [9] apply. NOTE: ETSI EN 305 174-8 [9] uses the terms "reuse" and "re-use" as synonyms whereas the present document adopts the sole use of the term "re-use". |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI EN 305 174-8 [9] apply. |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI EN 305 174-8 [9] and the following apply: VFC Volatile FlouroCarbons VHC Volatile HydroCarbons |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 4 EoL process involvement | |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 4.1 General | When looking at the whole process from equipment delivery to the ICT user to the EoL and the recycling of all the components and materials, several actors are involved and all actors shall respect the rules and the standards applying to the sustainable management of ICT. The level of involvement of each actor is not the same level but all actors has responsibilities for the storage and transport of WEEE. Obviously, the recyclers, who are the last link of the EoL chain have the greatest involvement. As shown schematically in Figure 3, the main actors involved in the lifecycle of an ICT equipment are: • the Manufacturer (see clause 4.2); • the Vendor (see clause 4.2); • the ICT user (see clause 4.3); • the Maintenance Company during the lifecycle of the equipment (see clause 4.4); • the Recycler: responsible for the equipment EoL (see clause 4.5). ETSI ETSI TS 105 174-8 V1.2.1 (2019-12) 11 Figure 3: Actors of the ICT equipment lifecycle and involvement in the EoL cycle |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 4.2 Vendor | The vendor of the ICT equipment can be the manufacturer, or any other subsidiary or reseller. Their responsibilities are to ship, deliver and install the equipment in the user's facility. The vendor will have to produce all necessary guarantees of compliance with the standards related to transport (national or trans-boundary), especially in case of hazardous materials (RoHS) or pollutants. The procurement between the vendor and the user shall include a clause specially focused on the equipment EoL. In order to comply with Extended Producer Responsibility rules of the WEEE Directive [8], the vendor can either: • implement an individual collection and treatment scheme subject to approval by public authorities; or • join an approved Producer Responsibility Organisation responsible for the collection and treatment of household equipment., to remove from site any obsolete equipment delivered by the vendor, and guarantee that the next steps of the EoL process will be done in accordance with the standards. |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 4.3 ICT User | The ICT user is the organization (e.g. the telecommunications operator) that operates the ICT equipment to provide the function for which it is deployed. An ICT user does not have to manage all aspects asked of vendors or maintenance companies. The user is not directly involved in the recycling process, but shall ensure that every stakeholder involved in the process (from shipping to EoL) are in line with the standards and recommendations referenced in ETSI EN 305 174-8 [9]. This should be clearly specified in all contracts between the equipment manufacturer, vendor, the maintenance company and the recycler. The user can assume that the equipment will be installed in a secure place, compliant with the standards related to ICT sites. At EoL, the equipment or, in the case of maintenance, its components and/or subassemblies, will be moved from operation at the ICT site and stored in a location provided by the user pending removal by the recycler for processing at in their facilities. The location shall be compliant with the standards in terms of e-waste storage, especially in case of hazardous equipment or pollutants substances. To summarize a user's responsibility is to: • have a clear view of its own ICT equipment assets; • provide the appropriate processes for tracking all ICT equipment assets including operational and maintenance status during their lifecycle; • dispose from sufficient and appropriate facilities to store the obsolete materials waiting transportation to the recycler facilities, in accordance with European standards related to WEEE and e-waste transportation and storage. The user has no responsibility for the management of the equipment after its EoL. Manufacturer/Vendor shipping, transport and delivery ICT User Re-use, EoL warehouses and transport Maintenance Company e-waste storage, repair, refurbish, transport Recycler Transport, sort, repair, refurbish, dismantle, recycle ETSI ETSI TS 105 174-8 V1.2.1 (2019-12) 12 |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 4.4 Maintenance company | The maintenance company is often a subsidiary of the manufacturer or an agreed company and assumes the maintenance for the ICT equipment under its responsibility during its "lifetime". All items of ICT equipment, components or subassemblies replaced by the maintenance company, due to upgrade or malfunction, shall be removed from the ICT user's location and transported to its own facilities. The contract established between the maintenance company and the ICT user shall clearly specify the compliance with the standards related to transport and storage of e-waste, including hazardous materials such as mercury lamps, batteries, and all pollutant substances. The maintenance company can impose, on the ICT user, the installation and operating conditions (including conditions of location, security, temperature and humidity ranges). Such conditions shall be specified in the maintenance contract. |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 4.5 Recycler | The recycler in the main actor in the EoL process for ICT equipment. The recycler has a direct relationship with all the other actors (as indicated in Figure 3). The recycler is involved in different steps of the EoL process for any equipment or component including transportation, storage, sorting, repairing, dismantling/disassembly, refurbishing and recycling. Recycling can address different types of materials (common or rare metals, plastic, rare earth, hazardous material, pollutants, etc.). The recycler is the most deeply involved in the respect of all standards related to the type of waste. When a recycling company deals with another company, the contract shall refer to the standards related to the type of material processed (e.g. plastic, metals, integrated circuits, batteries, lamps, etc.). The recycler shall compliance with the present document and has to be regularly audited by an independent certification body. Treatment facilities have to be certified against the relevant CENELEC standards for WEEE treatment (see clauses 2.1 and 2.2). |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 4.6 Summary | Table 1 presents the standards applying for each actor involved in the WEEE EoL process. Table 1: WEEE standards and relevance to actors Relevant document WEEE topic Vendor User Maintenance company Recycler CENELEC EN 50625-1 [2] Collection, logistics & Treatment requirements for WEEE. General treatment requirements ✓ ✓ ✓ ✓ CENELEC EN 50625-2-1 [3] Collection, logistics & Treatment requirements for WEEE. Treatment requirements for lamps ✓ ✓ ✓ X CENELEC EN 50625-2-2 [4] Collection, logistics & Treatment requirements for WEEE. Treatment requirements for WEEE containing CRTs and flat panel displays ✓ ✓ ✓ X CENELEC EN 50625-2-3 [5] Technical Specification for de-pollution. WEEE containing CRTs and flat panel displays ✓ ✓ ✓ X CENELEC CLC/ TS 50625-3-1 [6] Transport and logistics - Temperature exchange equipment and other WEEE containing volatile flouro- or hydro- carbons (VFC and/or VHC) X X X X CENELEC CLC/ TS 50625-3-2 [7] Collection, logistics & Treatment requirements for WEEE. Specification for de-pollution - General X X X X ETSI EN 305 174-8 [9] Management of EoL of ICT equipment ✓ ✓ ✓ ✓ Table 2 presents the ACTIONS applying for each actor involved in the WEEE EoL process. ETSI ETSI TS 105 174-8 V1.2.1 (2019-12) 13 Table 2: WEEE standards and relevance to actors Action Vendor User Maintenance company Recycler Collection of obsolete ICT equipment, components or sub- assemblies ✓ ✓ ✓ ✓ Storage of obsolete ICT equipment, components or sub-assemblies ✓ ✓ ✓ ✓ Transportation of e-waste ✓ ✓ ✓ ✓ Re-use of ICT equipment, components or sub-assemblies x ✓ ✓ x Repair of ICT equipment, components or sub-assemblies x ✓ ✓ x Refurbishment of ICT equipment, components or sub-assemblies x x ✓ x Sorting of obsolete ICT equipment, components or sub-assemblies x x x ✓ Dismantling/disassembly of obsolete ICT equipment, components or sub-assemblies x x x ✓ Depollution of obsolete ICT equipment, components or sub-assemblies x x x ✓ Recovery of basic elements x x x ✓ Final treatment x x x ✓ Reporting and assessment ✓ ✓ ✓ ✓ Production of KPIs ✓ ✓ ✓ ✓ 5 ICT domains to promote best practices for WEEE treatment The objective of the present document is to provide practical guidance on the implementation of requirements and recommendations to improve collection, transport, treatment, recycling and recovery for WEEE coming from ICT sector as shown in Table 3. Table 3: Types, and examples, of ICT equipment ICT domain Equipment types Examples of equipment ICT sites (including datacentres, OS, NDN) NTE Core network equipment Access network equipment Base stations ITE Server Switch Routers Disk Arrays Backup robots Hard disk drives (HDD) Solid state drives (SSD) Overhead function Fixed PC and laptops Monitors, screens Printers, scanners Accessories Other peripherals External infrastructure NIU WiFI hotspots, Radio Units, antennas Customer premises TE Fixed telephones, Internet boxes, TV boxes, connected devices including those for IoT UE Mobile telephones, laptops, tablets and other connected devices including IoT Although there are many differences between components of ITE and NTE in terms of usage and function, all ICT equipment is composed of the same materials and electronics and shall respect the same standards with regard to management of EoL. ETSI ETSI TS 105 174-8 V1.2.1 (2019-12) 14 As indicated in Figure 3, the vendor or the maintenance company should engage contractually with the recycler to guarantee conformance to the relevant CENELEC standards (see clauses 2.1 and 2.2). 6 Operational recommendations for maintenance during usage phase |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 6.1 General | Maintenance is an essential element in the operational lifecycle for ICT equipment. This also applies to the equipment for power supply and distribution, environmental control and other security systems within ICT sites supporting core networks and both fixed and mobile access networks. There are two main reasons for which hardware maintenance is imperative in the lifecycle of ICT equipment: • Evolution of the equipment, by upgrading (e.g. boards, memory) or replacing existing components or sub-assemblies with those of a newer generation. • Correction of a hardware issue if a component is to be repaired or replaced. |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 6.2 ITE and NTE | In the case of a replacement of an ITE or NTE component or sub-assembly, due to an evolution of the hardware, the recommendation for the changed component or sub-assembly follows the same rules as for all other ICT equipment. In such a case, re-use (if possible), refurbish or repair will be the priorities for the recycler. If any of these methods are available, the component will have to follow the process and the standards applied to EoL of WEEE. This will concern the equipment vendor, who will have to put in place the adequate processes for treatment of its equipment directly or through recyclers. The ICT user shall ensure these standards are applied by the recycler. This can be implemented by audits performed by a certified assessor (either on demand by the ICT user or periodically). The maintenance contract shall specify these points in accordance with the necessary list of standards to be applied. In case of replacement of a component or the whole equipment, due to hardware issues, the above process shall be applied for the total recycling phase. |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 6.3 Other WEEE in ICT sites | For all equipment other than ITE or NTE components, the applicable rules are those related to the type of the equipment including: • Cathode Ray Tubes (CRT) and flat panel displays: CENELEC EN 50625-2-2 [4]; • lamps: CENELEC EN 50625-2-1 [3], CENELEC CLC/TS 50625-3-2 [7]; • printers, scanners: for further study. The existing standards for those kinds of material should be applied for all equipment related to the power supply systems, such as transformers, rectifiers, UPS, batteries then. The present document does not address the ICT user's technical environment such as power supply and distribution, environmental control and other security systems within ICT sites. In the case of risks of contamination of people or property, the appropriate standard shall be applied. ETSI ETSI TS 105 174-8 V1.2.1 (2019-12) 15 7 Operational recommendations for each domain for the End-of-Life |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 7.1 General | Figure 4 shows the framework for EoL of ICT equipment of Table 3 together with references to the relevant CENELEC standard or Technical Specification. It is clear that the main part of the EoL actions such as sorting, dismantling/disassembling etc. is the responsibility of the recycler unless the ICT equipment is re-used directly by the ICT user. Figure 4: Framework for EoL processing of ICT equipment |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 7.2 The "4R" strategy for ICT equipment | |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 7.2.1 General | EoL of an ICT equipment from the current ICT user does not automatically mean EoL for the ICT equipment. An item of ICT equipment is not necessarily obsolete just because it is no longer able to meet current needs. It may be possible to extend its life and it can be re-used (in part or in total) for other purposes or by other ICT users (either internal or external to the current ICT user's organization). In such a case, other processes such as re-use (see clause 7.2.2), repair (see clause 7.2.3) and refurbishment (see clause 7.2.4) can extend the life of the equipment and avoid generation of e-waste and the associated recycling process. In case of true obsolescence, and if there are no other alternatives, the EoL recycling process (see clause 7.2.5) will apply. |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 7.2.2 Re-use | ETSI EN 305 174-8 [9] defines re-use as "any operation by which products or components that are not waste are used again for the same purpose for which they were conceived". Collection and logistics CLC/TS 50625-4 Dismantling/disassembly and sorting processes Re-use, refurbish or repair CENELEC EN 50614 Treatment of CRT and flat panel displays CENELEC EN 50625-2-2 Removal, treatment and depollution CENELEC EN 50625-1, -2-1, -2-3 Final treatment Copper and precious metals CLC/TS EN 50625-5 Second-hand market ETSI ETSI TS 105 174-8 V1.2.1 (2019-12) 16 Re-use of ICT equipment could be considered as a "second life" for the whole equipment, its components or subassemblies. It could be re-used directly by the ICT user for another purpose or support its new operational cycle towards a more optimal use. Alternatively, the ICT equipment can be sold on the second-hand market. NOTE: Re-use may involve specific additional services such data destruction and the provision of a new environmental certification. Re-use of ICT equipment brings value by extending equipment life, by reducing waste generation and by creating value for the owner. However, it should be noted that the energy efficiency of older equipment may be significantly worse than that of newer products. Further information is provided in CENELEC EN 50614 [1]. |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 7.2.3 Repair | In the context of this clause, repair focusses on correction of a hardware malfunction. Repair of the ICT equipment comprises the replacement of one or more components or sub-assemblies. This may be undertaken on-site during the operational period of the ICT equipment through the maintenance process (see clause 5) or be undertaken by the maintenance company if the ICT equipment, component or subassembly is removed from the operational site. Once repaired, the equipment is fully operational for the ICT user or can be sold on the second-hand market. |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 7.2.4 Refurbish | Refurbishment can be defined as "any operations to ICT equipment considered as waste to operate again including both hardware and software functions". The refurbishing company may be a vendor's affiliate, or any other company (brokers, maintenance, recyclers) operating in the market for second-hand ICT equipment. In addition to physical re-conditioning, the refurbishment process can be split in two stages: 1) to check all hardware functionalities, to remove old data and software, and to install the hardware components to be changed or upgraded; 2) to install new operating system(s) and applications software. Those undertaking refurbishment shall ensure that components and sub-assemblies (e.g. batteries, boards, power supplies) removed from ICT equipment are stored in appropriate facilities and processed as described in the relevant CENELEC standards (see clauses 2.1 and 2.2). Specifically: • all equipment, component or sub-assemblies destined for re-use shall be handled and stored in a suitable manner to preserve their value and avoid risks of pollution, where they exist; • all equipment, component or sub-assemblies destined for recovery and recycling shall be stored in safe and secure locations that are compliant with the relevant standards (e.g. hazardous equipment storage). |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 7.2.5 Recycle | If neither re-use, repair or refurbishment are viable, recycling begins with the dismantling/disassembly of the ICT equipment. As ICT equipment comprises a large variety of materials, components, the first steps of dismantling/disassembly generally focus on: • the removal of hazardous components, such as ink cartridges from printers, printed circuit boards, mercury lamps from scanners, batteries, etc.; • the removal, for re-use where possible, of valuable components like hard disks, memory, cards, power supplies, etc. ETSI ETSI TS 105 174-8 V1.2.1 (2019-12) 17 This process is followed by the sorting of the components and sub-assemblies. The first step in the sorting process is to isolate groups of common components. Subsequent sorting prepares specific types of component for separate recycling and treatment processing in accordance with the relevant standards applying for that material. |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 8 Collection of data | |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 8.1 General | For having a clear view of generated e-waste, the ICT user will have to know precisely what types and quantities of e-waste are produced. The ICT user shall also define the processes to determine the appropriate application of the 4R strategy (see clause 7.2). The ICT user shall track, from the receipt of ICT equipment (including any components or sub-assemblies used for repair) to either its re-use internally or its storage until the recycler collects the ICT equipment (including any components or sub-assemblies). For ICT equipment these requirements are generally the responsibility of the "IT department". However, for large telecommunications operators the separate responsibilities for ITE and NTE can be split across different departments. For all other e-waste, the responsibility lies with the department allocated the role of reporting of corporate sustainability actions. The information from the "IT department" is considered part of the overall reporting. |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 8.2 What data is to be collected? | It is necessary to have a clear and comprehensive view of the type and quantity of e-waste that will be generated by the EoL of the ICT equipment. This can be obtained from a simple asset management process. The vendor, the ICT user and the maintenance company shall track and store information including: • the source of waste; • the type of waste; • the quantity of waste for each type (kg per annum). Suitable software with asset management functionality can ensure a global and clear tracking of the equipment and identify equipment which is approaching its EoL. The recycler requires the following information for calculation of the KPIs (see clause 9): • quantity of WEEE processed (kg per annum) - WEEE processed in ETSI EN 305 174-8 [9]; • quantity of WEEE prepared for re-use (kg per annum) - WEEE prepared for reuse in ETSI EN 305 174-8 [9]; • quantity of WEEE re-used for parts (kg per annum) - WEEE reused by parts in ETSI EN 305 174-8 [9]; • quantity of WEEE recycled (kg per annum) - WEEE recycled in ETSI EN 305 174-8 [9]; • quantity of WEEE from which energy is recovered energy (kg per annum) - WEEE recovered energy in ETSI EN 305 174-8 [9]; • quantity of WEEE destroyed (kg per annum) - WEE E destroyed in ETSI EN 305 174-8 [9]. In addition to these values, the recycler will have to produce an overall assessment of the recovered resources such as metals (nickel, lithium, steel, aluminium, copper, lead, gold, etc.), plastics, and other resources such as rare earth materials. ETSI ETSI TS 105 174-8 V1.2.1 (2019-12) 18 |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 9 Operational KPIs in WEEE treatment | |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 9.1 Reporting by the recycler | ETSI EN 305 174-8 [9] specifies the following KPIs: • WEEE treated; • Reuse and recycling rate; • Valorisation/recovery rate. The recycler shall prepare annual reports for the three KPIs, for each category, by dividing the weight of the WEEE that enters the recovery or recycling/preparing for re-use facility, after proper treatment in accordance with Article 8(2) of WEEE 2012/19/EU Directive [8] with regard to recovery or recycling, by the weight of all separately collected WEEE for each category, expressed as a percentage. |
08ad76446372a1c339a3fcb3dec7841f | 105 174-8 | 9.2 Reporting by other actors | The reporting by vendors, ICT users and maintenance companies provides a clear view of the total quantities (kg per annum) and the ratios of equipment re-used, repaired and refurbished (as appropriate) or stored waiting treatment by the recycler. The following values, in addition to those described in clause 8.1, shall be reported by the actor: • Number and type of equipment under maintenance contract. • Number and type of equipment entering EoL process. • Ratio of re-used equipment/Number of equipment entering EoL process. • Ratio of repaired equipment/Number of equipment entering EoL process. • Ratio of refurbished equipment/Number of equipment entering EoL process. ETSI ETSI TS 105 174-8 V1.2.1 (2019-12) 19 Annex A (normative): Recommendations for the different stages in the treatment of e-waste Table A.1 provides guidance on requirements concerning handling and storage of ICT equipment defined as WEEE. Table A.1: Handling and storage of WEEE Domain Handling of Devices/WEEE Requirements Handling equipment adapted to the devices. Avoid Breaking of screens, lamps, temperature exchanges devices. Damaged devices impossible to depollute or valorise. Emissions of pollutants/hazardous substances. Domain Storage of WEEE Requirements CENELEC EN 50625-1 [2] requires that: • the maximum quantity of stored WEEE is the maximum of the quantity that can be processed in 12 months; • the premises shall have impervious surfaces with water collection; • some devices and some fractions shall be stored under cover to avoid damage and/or result in the emission of pollutants. Avoid Excessive levels of stocks. Pollutant leaks. Damage to the devices. Table A.2 provides guidance on requirements concerning depollution of ICT equipment defined as WEEE. Table A.2: Actions and associated requirements for depollution Action Protection against accidents to, and contamination of, personnel by dangerous substances Requirements A management system shall be in place and up to date for all health and safety activities. There shall be a process of identification and risk management to limit or eliminate risks which includes places and activities that require personal protective equipment and operating procedures. Relevant personnel shall have undertaken training (in the situations and risks of the installation). Avoid Risk situations for operators. Action Depollution procedures for the ICT equipment. Requirements There shall be procedures for the identification of WEEE to be cleaned up and actions to be taken for the depollution. The depollution shall not damage the components to extract or disperse the polluting substances to the other fractions. Avoid Imperfect depollution. Emissions of pollutants into the environment or other fractions. Action Monitoring of depollution activity including: • incoming, processed, outgoing quantities; • downstream processing. Requirements The quantities managed by the recyclers shall be recorded as well as the sources and destinations of the inputs and outputs. Recyclers shall provide documented information on fractions and their recovery, according to their typology. Recyclers shall employ a process for depollution performance monitoring which uses a systematic approach that documents each step of the process. Avoid Activity not mastered. Resumption of fractions not adapted. Imperfect depollution. ETSI ETSI TS 105 174-8 V1.2.1 (2019-12) 20 History Document history V1.1.1 January 2018 Publication as ETSI EN 305 174-8 V1.2.1 December 2019 Publication |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 1 Scope | The present document details measures which may be taken to improve the energy efficiency within homes (single-tenant) by virtue of broadband deployment. Clauses 2 and 3 contain references, definitions of terms and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Within the present document: • clause 4 describes the nature of customer premises networks in homes (single tenant), defines the interfaces to those networks and identifies the standardization bodies working on the design and installation of those networks; • clause 5 describes the strategies that may be employed within homes (single tenant) to both increase the energy efficiency of installed information technology equipment and to use the facilities offered by information technology services to reduce overall energy consumption. This will enable the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of this multi-part deliverable to provide detailed standardized solutions for home broadband network architecture. |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 2 References | |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. Not applicable. |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] European Commission: "DG-JRC Code of Conduct on Energy Consumption of Broadband Equipment". [i.2] CENELEC EN 50090 series: "Home and Building Electronic Systems (HBES)". [i.3] CENELEC EN 50173-1: "Information technology - Generic cabling systems - Part 1: General requirements". [i.4] CENELEC EN 50173-4: "Information technology - Generic cabling - Part 4: Homes". ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 7 [i.5] CENELEC EN 50174-1: "Information technology - Cabling installation - Part 1: Installation specification and quality assurance". [i.6] CENELEC EN 50174-2: "Information technology - Cabling installation - Part 2: Installation planning and practices inside buildings". [i.7] CENELEC EN 50090-2-1: "Home and Building Electronic Systems (HBES) - Part 2-1: System overview - Architecture". [i.8] CENELEC EN 50090-2-2: "Home and Building Electronic Systems (HBES) - Part 2-2: System overview - General technical requirements". [i.9] CENELEC EN 50090-2-3: "Home and Building Electronic Systems (HBES) - Part 2-2: System overview - General functional safety requirements for products intended to be integrated in HBES". [i.10] CENELEC EN 50090-3-1: "Home and Building Electronic Systems (HBES) - Part 3-1: Aspects of application - Introduction to the application structure". [i.11] CENELEC EN 50090-3-2: "Home and Building Electronic Systems (HBES) - Part 3-2: Aspects of application - User process for HBES Class 1". [i.12] CENELEC EN 50090-3-3: "Home and Building Electronic Systems (HBES) - Part 3-3: Aspects of application - HBES Interworking model and common HBES data types". [i.13] CENELEC EN 50090-4-1: "Home and Building Electronic Systems (HBES) - Part 4-1: Media independent layers - Application layer for HBES Class 1". [i.14] CENELEC EN 50090-4-2: "Home and Building Electronic Systems (HBES) - Part 4-2: Media independent layers - Transport layer, network layer and general parts of data link layer for HBES Class 1". [i.15] CENELEC EN 50090-4-3: "Home and Building Electronic Systems (HBES) - Part 4-3: Media independent layers - Communication over IP". [i.16] CENELEC EN 50090-5-1: "Home and Building Electronic Systems (HBES) - Part 5-1: Media and media dependent layers - Power line for HBES Class 1". [i.17] CENELEC EN 50090-5-2: "Home and Building Electronic Systems (HBES) - Part 5-2: Media and media dependent layers - Network based on HBES Class 1, Twisted Pair". [i.18] CENELEC EN 50090-5-3: "Home and Building Electronic Systems (HBES) - Part 5-3: Media and media dependent layers - Radio frequency". [i.19] CENELEC prTS 50090-6-4: "Home and Building Electronic Systems (HBES) - Part 6-4: Interfaces - Residential gateway model for a home and building electronic system". [i.20] CENELEC EN 50090-7-1: "Home and Building Electronic Systems (HBES) - Part 7-1: System management - Management procedures". [i.21] CENELEC EN 50090-8: "Home and Building Electronic Systems (HBES) - Part 8: Conformity assessment of products". [i.22] CENELEC EN 50090-9-1: "Home and Building Electronic Systems (HBES) - Part 9-1: Installation requirements - Generic cabling for HBES Class 1 Twisted Pair". [i.23] CENELEC TR 50090-9-2: "Home and Building Electronic Systems (HBES) - Part 9-2: Installation requirements - Inspection and testing of HBES installation". [i.24] CENELEC EN 50491-2: "General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) -- Part 2: Environmental conditions". [i.25] CENELEC EN 50491-3: "General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) -- Part 3: Electrical safety requirements". ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 8 [i.26] CENELEC EN 50491-5-1: "General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) -- Part 5-1: EMC requirements, conditions and test set-up". [i.27] CENELEC EN 50491-5-2: "General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) -- Part 5-2: EMC requirements for HBES/BACS used in residential, commercial and light industry environment". [i.28] CENELEC EN 50491-5-3: "General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) -- Part 5-3: EMC requirements for HBES/BACS used in industry environment". [i.29] CENELEC EN 50491-6: "General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) -- Part 6: Design, planning and installation". [i.30] ETSI TS 102 973: "Access Terminals, Transmission and Multiplexing (ATTM); Network Termination (NT) in Next Generation Network architectures". [i.31] IEEE 802.3af™: "IEEEE Standard for Information Technology - Telecommunications and Information Exchange Between Systems - Local and Metropolitan Area Networks - Specific Requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications - Data Terminal Equipment (DTE) Power Via Media Dependent Interface (MDI)". [i.32] IEEE 802.3at™: "Standard for Information Technology Telecommunications and Information Exchange Between Systems Local and Metropolitan Area Networks Specific Requirements Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications Amendment: Data Terminal Equipment (DTE) Power Via the Media Dependent Interface (MDI) Enhancements". [i.33] IEEE 802.3az™: "IEEE Standard for Information Technology - Telecommunications and Information Exchange Between Systems - Local and Metropolitan Area Networks - Specific Requirements Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications - Amendment: Media Access Control Parameters, Physical Layers and Management Parameters for Energy-Efficient Ethernet". [i.34] ISO/IEC 15018: "Information technology - Generic cabling for homes". [i.35] Commission Regulation (EC) No 1275/2008 of 17 December 2008, implementing Directive 2005/32/EC of the European Parliament and of the Council with regard to "ecodesign requirements for standby and off mode electric power consumption of electrical and electronic household and office equipment". [i.36] ETSI TS 105 174-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 1: Overview, common and generic aspects". [i.37] CENELEC EN 60603-7 series: "Connectors for electronic equipment -- Part 7: Detail specification for 8-way". [i.38] CENELEC EN 50491-4 (in development): "General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS); Part 4: Functional safety requirements". [i.39] ETSI TR 105 174-4: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 4: Access networks". [i.40] ETSI TS 105 175-1 (V2.0.0): "Access, Terminals, Transmission and Multiplexing (ATTM); Plastic Optical Fibre System Specifications for 100 Mbit/s and 1 Gbit/s". [i.41] ETSI TS 105 175-1-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Plastic Optical Fibres; Part 1: Plastic Optical Fibre System Specifications for 100 Mbit/s and 1 Gbit/s; Sub-part 1: Application requirements for physical layer specifications for high-speed operations over Plastic Optical Fibres". ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 9 [i.42] ETSI TS 105 175-1-2: "Access, Terminals, Transmission and Multiplexing (ATTM); Plastic Optical Fibres; Part 1: Plastic Optical Fibre System Specifications for 100 Mbit/s and 1 Gbit/s; Sub-part 2: 1 Gbit/s and 100 Mbit/s physical layer for Plastic Optical Fibres". [i.43] CENELEC EN 50173 series: "Information technology - Generic cabling systems". |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 3 Definition of terms, symbols and abbreviations | |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 3.1 Terms | For the purposes of the present document, the following terms apply: application: system, with its associated transmission method that is supported by telecommunications cabling (this corresponds to a Layer One application in the OSI 7-layer model) Broadcast Communication Technology (BCT) application: system, with its associated transmission method using the HF band (3 MHz to 30 MHz), the VHF band (30 MHz to 300 MHz) and the UHF band (300 MHz to 3 000 MHz) dedicated to the transmission of sound radio, TV and two-way data services, as well as for in-home inter-networking NOTE: See CENELEC EN 50173-1 [i.3] modified. BCT service: transmission of sound radio, TV and two-way data NOTE: See CENELEC EN 50173-1 [i.3] modified. Control, Command and Communications in Building (CCCB) application: system, with its associated transmission method dedicated to providing appliance control and building control NOTE: See CENELEC EN 50173-1 [i.3] modified. CCCB services: appliance control and building control NOTE: See CENELEC EN 50173-1 [i.3] modified. Information Communication Technology (ICT) applications: system, with its associated transmission method for the communication of information ICT services: creation, communication dissemination, storage and management of information network convergence: ability of a network, by virtue of the applications it supports, to deliver multiple ICT, BCT and CCCB services |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 3.2 Symbols | Void. |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACP Area Connection Point BACS Building Automation and Control Systems BCT Broadcast Communications Technology BO Broadcast Outlet CAT CATegory CATV CAble Television CCCB Command Control and Communications in Buildings CGIC ETSI CLC Co-ordination Group on Installations and Cabling CO Control Outlet DC Dedicated Control ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 10 DSL Digital Subscriber Line DTE Data Terminal Equipment EC European Commission EEE Energy Efficient Ethernet EMC Electro-Magnetic Compatibility ENTI External Network Termination Interface EU European Union FTTH Fibre To The Home HBES Home and Building Electronic Systems HD Home Distributor HDMI High Definition Media Interface HD/SHD Home Distributor / Secondary Home distributor ICT Information and Communication Technology IEC International Electrotechnical Commission LAN Local Area Network LPI Low Power Idle MATO Multi-Application Telecommunications Outlet MDI Media-Dependent Interface NGN Next Generation Network OF Optical Fiber OIE Operator Independent Equipment OSE Operator Specific Equipment PC Personal Computer PDA Personal Digital Assistant PoE Power over Ethernet POF Plastic Optical Fibre RJ Registered Jack SHD Secondary Home Distributor SI Step Index SI-POF Step Index Plastic Optical Fibre TO Telecommunications Outlet TR Technical Report TV TeleVision |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 4 Customer networks in homes (single-tenant) | |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 4.1 Overview of home network infrastructures | |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 4.1.1 General | Homes, both as single-tenant and multi-tenant premises, are unique with respect to cabling infrastructures for the following reasons: • they represent the largest constituency for broadband services; • there are limited or non-existent cabling infrastructures within the home for the distribution of external network telecommunications services or internally generated information technology services; • residents are either willing to physically move within the home, or install service-specific wireless systems to access the primary telecommunications equipment; • residents tend to situate their living space(s) according to the availability of the BCT service; • the ongoing development of BCT services and the consequent requirements of the local cabling (HDMI, etc.) restrict distribution of those services within the home since a significant percentage of installations have been changed by the user and which restrict the capability of the infrastructure to support upgraded services. ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 11 The growth of ICT applications within the home and the advent of broadband services allowing access to BCT services using ICT applications has failed to encourage large scale installation of home cabling infrastructures as a means of distribution since: • aesthetic considerations have prominence in domestic premises; • refurbishment of the building structures is uncommon; • residents expect temporal flexibility in access to services. Instead there has been a substantial investment in wireless infrastructures within the home. These systems lie outside the scope of this multi-part document. |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 4.1.2 Network convergence | Within the home, telecommunications services fall into three groups: • ICT (also referred to as HBES Class 2): for example, telephone, local area network; • BCT (also referred to as HBES Class 3): for example, broadcast television; • Other services technology, known as CCCB (also referred to as HBES Class 1): for example, security alarms, surveillance and door access control, environmental controls, IoT. Annex A includes details of the types of services and the group into which they fall. Access networks providing ICT services are also supporting BCT and CCCB services using ICT applications. Access networks providing BCT services also support ICT services using embedded ICT applications. Within customer premises, the range of networks has, in the past, reflected the diversity of the services with: • ICT services being delivered over a variety of cabling infrastructures ranging from those suitable only for basic telephony through to those used for generic cabling (see clause 4.2.1); • BCT services being delivered over application-specific coaxial cabling systems; • CCCB services being delivered over a variety of cabling infrastructures ranging from application-specific solutions described in general terms in clause 4.2.2, often including those combining power with control systems, through to those used for generic cabling (see clause 4.2.1). However, the network convergence seen in the access network may also extend into the customer premises. Within customer premises, the opportunity for network convergence is further enhanced by the development of ICT networking standards that support delivery of Power over Ethernet (PoE). These can typically provide approximately 13 W via IEEE 802.3af [i.31] and approximately 25 W via IEEE 802.3at [i.32]) when using ICT applications such as 10/100/1000BASE-T. The emergence and further development of PoE is expected to encourage the use of cabled infrastructure installations since: • both existing residents and developers of new homes will recognize the benefits of being able to control and provide power to a wide range of equipment (for example, surveillance systems, door access control, environmental control system) that can be managed from a central location and via a common infrastructure; • residents will see an increase in equipment specified for connection to PoE without the need for external power supplies and with a common connection style (CENELEC EN 60603-7 series [i.37], also known as the RJ-45). By these means, ICT applications, such as 10/100/1000BASE-T, are able to support ICT, BCT and CCCB services within the home. In order to meet the potential need for a common infrastructure to support network convergence within the home, CENELEC TC215 developed CENELEC EN 50173-4 [i.4], covering the design and specification of generic cabling. ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 12 |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 4.2 Infrastructure standardization activities | |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 4.2.1 Generic cabling designs in accordance with CENELEC EN 50173-4 | |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 4.2.1.1 Infrastructure layers | CENELEC EN 50173-4 [i.4] specifies two layers of infrastructure as shown in figure 1. Both layers are fed from a Home Distributor (HD) or, if the dimensions of the home, its configuration or the complexity of the network supports their use, Secondary Home Distributors (SHD) as shown in figure 2. Figure 2 shows that generic cabling of CENELEC EN 50173-4 [i.4] not only provides distribution of broadband services delivered over cabled media via the access network but also supports the reception of BCT services using antennae. NOTE: CENELEC EN 50173-4 [i.4], first published in 2007, has a similar scope to that of ISO/IEC 15018 [i.34] produced by ISO/IEC JTC1 SC25. However, the two documents contain different requirements and are therefore not identical at a technical level. It should be noted that within multi-tenant premises the network telecommunications equipment and access network cabling shown in figure 1 and figure 2 may be replaced by other equipment and a private backbone cabling infrastructure operated by the premises owner or other party. ©CENELEC, reproduced with permission Figure 1: Dual layer infrastructure of CENELEC EN 50173-4 [i.4] Network telecommunications equipment Access network CCCB applications BCT applications ICT applications ICT/BCT/CCCB applications ACP CO CO CO CO CO ACP CO CO CO CO BO TO SHD HD MATO ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 13 ©CENELEC, reproduced with permission Figure 2: Examples of generic cabling within the home according to CENELEC EN 50173-4 [i.4] |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 4.2.1.2 CCCB infrastructure | The provision of CCCB services is achieved by the connection of: • control devices (e.g. sensors and/or actuators) at the Control Outlets (CO); • the relevant system control equipment at the HD/SHD as shown in figure 3 (as in CENELEC EN 50173-4 [i.4]). A CO may be connected directly (i.e. point-to-point) to the HD/SHD or may be connected via an Area Connection Point (ACP) which allows a range of point-to-multipoint topologies in a given area where required by the needs of that area and as allowed by the CCCB system serving that area. ©CENELEC, reproduced with permission Figure 3: CCCB cabling topologies of CENELEC EN 50173-4 [i.4] Single home with Secondary Home Distributor HD Single home without Secondary Home Distributors Access network SHD HD ENI Network access cabling Network access cabling Network telecommunications equipment Access network Network telecommunications equipment ENI = point of loop closure KEY: Area feeder cabling subsystem ACP HD/SHD CO CO Loop CO CO CO CO CO CO CO CO CO CO CO CO CO Tree and branch Coverage area subsystem ACP CO CO CO Star CO CO CO CO Bus CO CO CO CO CO CO CO CO ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 14 The type of cabling components and the installed transmission performance is defined by CENELEC EN 50173-4 [i.4]. This allows a wide range of CCCB applications to be supported but inevitably not all CCCB applications are supported over such an infrastructure. Other cabling design standards exist to support these applications (see clause 4.2.2). NOTE: The ACP also supports the implementation of wireless sensor networks. |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 4.2.1.3 ICT and BCT infrastructure | The provision of ICT and BCT services is achieved by the connection of: • terminal equipment (e.g. telephones, computers and television receivers) at the Telecommunications Outlet (TO) and Broadcast Outlet (BO) respectively - both of which adopt a point-to-point star topology to the relevant distributor; • the relevant system equipment at the HD/SHD as shown in figure 4 (as in CENELEC EN 50173-4 [i.4]). NOTE: The Multi-Application Telecommunications Outlet (MATO) is a co-location of BO, TO and ACP/CO. ©CENELEC, reproduced with permission Figure 4: BCT/ICT cabling topologies of CENELEC EN 50173-4 [i.4] |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 4.2.1.4 Cabling | The ICT and CCCB infrastructures are implemented using balanced cabling. There is a common minimum transmission performance between the HD (or SHD) and the TO and ACP (defined as Class D of CENELEC EN 50173-1 [i.3]). Class D cabling of CENELEC EN 50173-1 [i.3] is capable of supporting applications up to and including 1000BASE-T and incorporating power distribution to the TO or ACP in accordance with IEEE 802.3at [i.32]. Although the BCT infrastructure may be implemented using coaxial cabling or balanced cabling, the ultimate objective of network convergence is achieved by delivering both CCCB and BCT services using ICT applications. 4.2.2 Cabling installation in accordance with CENELEC EN 50174 standards CENELEC EN 50174-1 [i.5] and CENELEC EN 50174-2 [i.6] contain requirements and recommendations for the specification, quality assurance, planning and installation practices that apply to all information technology cabling media in all premises. Clause 10 of CENELEC EN 50174-2 [i.6] specifies the additional/amended requirements and recommendations that apply within the home. In recognition of the domestic environment described in clause 4.1, clause 10 of CENELEC EN 50174-2 [i.6] focuses on the provision of spaces and pathways to house the cabling infrastructures in support of both CENELEC EN 50173-4 [i.4] and CENELEC EN 50491 standards [i.24] to [i.29]. It is planned that CENELEC EN 50174-1 [i.5] and CENELEC EN 50174-2 [i.6] will support the essential aspects of planning and installation and this will be reflected in external references from CENELEC EN 50491-6 [i.29]. Home cabling subsystem Secondary home cabling subsystem TO/BO TO/BO SHD TO/BO HD MATO TO/BO TO/BO SHD Home cabling subsystem HD TO/BO TO/BO MATO ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 15 |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 4.3 Network access infrastructure | 4.3.0 Energy Efficiency in network access cabling and equipment The connection between the operator's access network and the home distributor as shown in figure 2 (or the equivalent in non-generic cabling) is provided by network access cabling and some type of network telecommunication equipment as shown in figure 5. The network telecommunications equipment typically comprises a passive interface (ENTI) and an optional item of apparatus. The apparatus may be specific to the network operator (OSE) or may be operator independent (OIE) as described in the following examples: • OIE: DSL modem, FTTH modem (where interoperability standard exists). NOTE: See ETSI TS 102 973 [i.30]. • OSE: CATV modem, FTTH modem (where no interoperability standard exists). The OSE is part of the access network whereas the OIE is part of the customer premises infrastructure. Figure 5: Network access cabling and equipment In most cases the OIE, or some part of it, may be powered from the access network. In some cases the OSE may be powered from the customer premises. For this reason, the energy efficiency of the access network takes into account any power required to maintain the functionality at the service interface, whether or not it is part of the access network (and is covered in ETSI TR 105 174-4 [i.39]). The EU Code of Conduct on Energy Consumption of Broadband Equipment [i.1] provides a framework for ensuring operational energy efficiency consumption of network telecommunication equipment. 4.3.1 Cabling designs in accordance with CENELEC EN 50090 and CENELEC EN 50491 series The CENELEC EN 50090 series of standards [i.2] specifies system solutions for the provision of Home and Building Electronic Systems (HBES). HBES support the distribution of CCCB, ICT and BCT services which are designated Class 1, Class 2 and Class 3 respectively. ENTI OIE Distribution ENTI OSE Distribution Access network Network access cabling in EN 50173-x standards Service interface Service interface ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 16 Some of the HBES Class 1 systems are supported over generic cabling for CCCB described in clause 4.2.1 and shown in figure 3. Others have specific requirements for cabling design that fall outside the provision of generic cabling. HBES Class 1 applications between the equivalent of the HD/SHD and CO of CENELEC EN 50173-4 [i.4] typically adopts a bus topology (see figure 6) although tree (see figure 7), star (see figure 8) and combined topologies are also supported by certain HBES Class 1 implementations as shown in figure 9. Figure 6: Bus topology for HBES cabling and device connection Figure 7: Tree topology for HBES cabling and device connection Figure 8: Star topology for HBES cabling and device connection Figure 9: Combined topologies for HBES cabling and device connection Once HBES devices are connected to the infrastructure, it is necessary for them to be configured to exercise their function via simple or complex commands (scenarios). Device configurations include set points and timing for temperature controllers, zone partitioning for temperature and alarm controllers and scenario definition in control units. The CENELEC EN 50491 series of standards is entitled "General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS)" and contains requirements for HBES devices including: • environmental performance, CENELEC EN 50491-2 [i.24]; • safety, CENELEC EN 50491-3 [i.25]; • functional safety, CENELEC EN 50491-4 [i.38]; • EMC, CENELEC EN 50491-5 series [i.26], [i.27] and [i.28]; • design, planning and installation, CENELEC EN 50491-6 [i.29]. The CENELEC EN 50491 series is in the process of replacing the existing CENELEC EN 50090 series [i.2] of standards entitled "Home and Building Electronic Systems (HBES)" covering the following areas: • system overview, CENELEC EN 50090-2 series [i.7], [i.8] and [i.9]; • aspects of application, CENELEC EN 50090-3 series [i.10], [i.11] and [i.12]; bus tree star ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 17 • media independent layers, CENELEC EN 50090-4 series [i.13], [i.14] and [i.15]; • media and media dependent layers, CENELEC EN 50090-5 series [i.16], [i.17] and [i.18]; • interfaces, CENELEC EN 50090-6-4 [i.19]; • system management, CENELEC EN 50090-7 series [i.20]; • conformity assessment of products, CENELEC EN 50090-8 series [i.21]; • installation requirements, CENELEC EN 50090-9 series [i.22] and [i.23]. |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 5 Energy efficiency | |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 5.1 General | It is not possible to determine Key Performance Indicators (KPIs) for the energy efficiency of information technology networks within homes (single tenant). However, it is relevant to identify strategies for the improvement of energy efficiency of information technology infrastructures in the home (see clause 5.2) and also to introduce short term and medium term actions, based on the use of information technology networks, to reduce the overall energy consumption within homes (see clause 5.3). |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 5.2 Energy efficiency of information technology infrastructures | The principal strategy to be adopted involves: • the use of devices in accordance with the Energy Efficient Ethernet project (IEEE 802.3az [i.33]); • the use of low consumption visual interfaces; • the use of common visual interfaces (acting as displays for ICT and BCT services, independent of the type of application used to deliver the BCT service); • not just using standby modes for attached devices (opting to turn them off instead). NOTE: The future provision of equipment meeting the requirements of European Commission Regulation (EC) No 1275/2008 [i.35] will assist in observing this strategy. 5.3 The use of information technology to reduce total energy consumption |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 5.3.1 Infrastructure | The creation of appropriate network infrastructures can assist in reducing energy consumption by minimizing the energy wasted due to poor control of attached equipment. Examples include: • the use of PoE and PoE Plus, representing power on demand: - encouraging the use of equipment options with lower power consumption; - replacing permanently connected, "on" all the time, equipment (including DC converters in mains sockets); NOTE: It is recognized that PoE may not be as energy efficient as a means of powering an individual device but it is considered that the benefit of PoE will lie in the control of usage that its fixed infrastructure provides. ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 18 • the implementation of wireless access technologies to allow portable access to information technology services rather than duplicating equipment. |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 5.3.2 Applications | CCCB services offer significant opportunities to reduce energy consumption (e.g. light and heating levels in unoccupied areas) which can be further enhanced by integration with broadband delivery to monitor and control energy usage via those CCCB systems. The marketing of such "intelligent" home systems has, to date, concentrated on the features of such systems rather than on the benefits of using them. As energy costs rise, the opportunity exists to re-focus on potential energy savings offered by information technology solutions. The ability to monitor, in real time, the energy usage in the home, either as a total or more specifically as related to individual circuits (lighting, heating) or components (ovens, refrigerators) and to display this information using a common visual interface using an ICT application both within the home (see clause 5.2) or remotely may contribute significantly to the reduction of energy consumption within the home. The opportunity presented by PoE suggests that optical fibre in the home may not be as advantageous as one might think despite the ultimate bandwidth limitations of the copper cabling specified in CENELEC EN 50173-4 [i.4] (specified today to support 1000BASE-T, Class D). |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 5.3.3 Green issues | The use of high bandwidth broadband deployment to support true "home working" (enabling effective "telepresence") allows the "carbon footprint" of employees to be reduced. A variety of studies, including those undertaken in the United Kingdom by The Carbon Trust, shows that home working provides substantial beneficial impact. An increased focus by employers on "mobility", requiring equivalent access to corporate networks, applications and tasks independent of the location from which they are accessed, recognizes home working as offering reductions in both capital and operational expenditure in terms of office space, corporate infrastructure and energy consumption. However, true mobility requires provision of high speed broadband delivery which can replicate, effectively, the office-based environment in the remote location. |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 5.4 The POF cabling case: ETSI TS 105 175-1-1 | |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 5.4.0 Generalities | According to ETSI TS 105 175-1-1 [i.41] one of the possible solutions for home networking cabling is the use of POF. This clause describes, how the use of that TS is an optimum strategy for energy reduction. |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 5.4.1 ETSI TS 105 175-1-1 | ETSI TS 105-175-1-1 [i.41] describes a home network architecture based in a gigabit back-bone of SI-POF using the ETSI TS 105 175-1-2 [i.42] physical layer. ETSI TS 105-175-1-1 [i.41] and ETSI TS 105 175-1-2 [i.42] fulfil the requirements of the ETSI TS 105 175-1 [i.40]. The Plastic Optical Fibre might be installed between wall-plugs, connecting the home devices to the network either by RJ-45 wall plug connectors or Wi-Fi repeaters in every wall-plug. |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 5.4.2 Typical power consumption values | Table 1 shows power consumption of the POF application compared with 802.3 1000BASE-T and 802.3 1000BASE- SX solutions. ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 19 Table 1: Typical power consumption values per link Name EEE PoE/Po E+ Power Consumption 100 % Traffic 50 % Traffic 10 % Traffic No Traffic Idle mode ETSI TS 105 175-1-1 [i.41] Yes No 650 mW 375 mW 150 mW 100 mW < 1 mW 802.3 1000BASE-T Yes Yes 1000 mW 800 mW 300 mW 100 mW < 1 mW 802.3 1000BASE-SX No No 600 mW 600 mW 600 mW 600 mW - This values coming from market product datasheet are best market values at the time of writing. 50 % and 10 % traffic values are estimated values. |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 5.4.3 Low Power Idle mode | The use of Energy Efficient Ethernet (EEE) technics can reduce significantly the power consumption in the home network. In the case of the POF system, the energy efficient operation is called Low Power Idle (LPI). Figure 10 shows a comparison between 1000 Base-T (EEE-1G) and POF LPI (EE-POF): Figure 10: Comparison between 1000BASE-T (EEE-1G) and POF LPI (EE-POF) |
414d3895bfa074030c99bc3994daf200 | 105 174-5-1 | 5.4.4 Idle mode - Wake up functionality | Each component in the POF network is an active component acting as bridges between the POF back-bone and the home devices connected via CAT x cables or Wi-Fi. It is important to have and idle & wake-up functionality in the active components to reduce power consumption when connected devices are powered off, or no Wi-Fi connections are done. In this case, the optimum solution is the disable of the giga-bit back-bone connection switching off completely the optical transceivers. Local or remote wake-up functionality might be implemented in the case of traffic, reconnection of devices, or powering on of devices. Implementation of the idle-mode and wake-up functionality is not standardized, but is strongly recommended by the present document. ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 20 Annex A (informative): Services within the home Within table A.1, the access network refers to the distribution infrastructure technology. Table A.1: Services, applications and required infrastructure Access network - coaxial Access network - balanced/OF Set Top Box Home Gateway TV PC Home server Residential network Sensors BCT Services Entertain ment BCT Applications Television and radio X X X ICT Applications Television and radio X X X X ICT Services ICT Applications Entertainment Entertainment: Multimedia X X X X X X Entertainment: Photo/video Photo frames X X X Entertainment: Photo/video (shared) Photo frames, mobile TV terminals, videophone X X X X X Entertainment: Audio-HiFi Audio players (dedicated MP3 player, mobile terminals, etc.) X X X X Entertainment: Audio-HiFi (shared) Audio players (dedicated MP3 player, mobile terminals, etc.) X X X X X X Entertainment: Game Game console X X Entertainment: Game (shared) Game console X X X X X Socio-cultural Telelearning Video-communication terminals, biomedical terminals X X X X Teleworking, cooperative working Phone terminals, video-communication terminals X X X X Home news, Info-push and virtual community Video telephony X X X X Home banking, and on-line purchases Video telephony X X X X Telecommunica tions Remote access to corporate LAN X X X X Integration with mobile phones, PDA, etc. PDA, etc, mobile terminals, femtocell X X X Telephone services Phone terminals (fixed and mobile) X X X Videocommunication Video-communication terminals X X X X E-mail Phone terminals (fixed and mobile) X X X Health and wellbeing Homecare Video-communication terminals, biomedical terminals X X X Remote assistance Video-communication terminals, biomedical terminals X X X Remote monitoring Video-communication terminals, biomedical terminals X X X X Telemedicine Video-communication terminals, biomedical terminals X X X X ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 21 Access network - coaxial Access network - balanced/OF Set Top Box Home Gateway TV PC Home server Residential network Sensors CCCB Services CCCB or ICT Applications Security: Anti-intrusion Security: Access control X X X X Safety: Ambient control (e.g. fire, gas, etc.) X X X X X X Programming and controlling white goods X X X X X X Motor control (e.g. rolling shutter) Lighting (scenarios) Heating/Air-conditioning Energy management: Load control Heating/Air-conditioning Lighting (automatic switch off) ETSI ETSI TS 105 174-5-1 V1.4.1 (2020-01) 22 History Document history V1.1.1 October 2009 Publication as ETSI TR 105 174-5-1 V1.3.1 July 2018 Publication as ETSI EN 305 174-5-1 V1.4.1 January 2020 Publication |
3fe5352ea29484004b7f0a2cc1be07d5 | 110 174-2-1 | 1 Scope | The present document details measures which may be taken to ease the deployment of smart new services and their multiservice street furniture of digital multiservice city within the IP network of a single city or an association of cities administratively clustered. Furthermore, the suggested measures will enable to engineer a reliable common networking infrastructure which can improve the Total Cost of Ownership (TCO) for the public administration while improving the energy efficiency of the overall deployment. The present document also lists the requirements which have led to this common architecture. Clause 4 presents a suggestion of an engineered digital multiservice city. Clause 5 introduces the active role categorized urban assets can play in the delivery of digital services across the territory of the city. Clause 6 reviews the spread efforts within the standardization organizations for the digital multiservice city. Clause 7 suggests both the common engineering required to transform an urban asset into an active network nodes of the digital multiservice city while presenting a concrete illustration of network design for one of the categories. This will enable the proper introduction and implementation of a new service, application or content within the city digital portfolio on a unified energy efficient network, though it is not the goal of the present document to provide detailed standardized solutions for network architecture. |
3fe5352ea29484004b7f0a2cc1be07d5 | 110 174-2-1 | 2 References | |
3fe5352ea29484004b7f0a2cc1be07d5 | 110 174-2-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. Not applicable. |
3fe5352ea29484004b7f0a2cc1be07d5 | 110 174-2-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 110 174-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Sustainable Digital Multiservice Cities (SDMC); Broadband Deployment and Energy Management; Part 1: Overview, common and generic aspects of societal and technical pillars for sustainability". [i.2] ETSI TS 105 174-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 1: Overview, common and generic aspects". ETSI ETSI TS 110 174-2-1 V1.1.1 (2018-11) 7 [i.3] ETSI TR 105 174-4: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 4: Access networks". [i.4] ETSI TS 105 174-4-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 4: Access Networks; Sub-part 1: Fixed access networks (excluding cable)". [i.5] ETSI TS 102 973: "Access Terminals, Transmission and Multiplexing (ATTM); Network Termination (NT) in Next Generation Network architectures". [i.6] ETSI TR 103 375: "SmartM2M IoT Standards landscape and future evolutions". [i.7] AIOTI Recommendations for future collaborative work in the context of the Internet of Things Focus Area in Horizon 2020. NOTE: Available at https://ec.europa.eu/digital-single-market/en/news/aioti-recommendations-future- collaborative-work-context-internet-things-focus-area-horizon-2020. [i.8] Light Fidelity TED Talk: "Wireless data from every light bulb". NOTE: Available at http://www.ted.com/talks/harald_haas_wireless_data_from_every_light_bulb. [i.9] IEEE 802.11™: "IEEE Standard for Information technology -- Telecommunications and information exchange between systems Local and metropolitan area networks--Specific requirements -- Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications". [i.10] IEEE 802.11s™: "IEEE Standard for Information Technology -- Telecommunications and information exchange between systems--Local and metropolitan area networks--Specific requirements -- Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 10: Mesh Networking". [i.11] IEEE 802.15™: "Visible Light Communications (VLC)". [i.12] IEEE 802.15.4™: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 15.4: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low Rate Wireless Personal Area Networks (WPANs)". [i.13] IEEE 802.11ah™: "IEEE Draft Standard for Information Technology -- Telecommunications and Information Exchange Between Systems-Local and Metropolitan Area Networks-Specific Requirements -- Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications: Amendment 2: Sub 1 GHz License Exempt Operation". [i.14] IETF RFC 3031: "Multiprotocol Label Switching Architecture". [i.15] IETF RFC 4761: "Virtual Private LAN Service Using Label Distribution Protocol (LDP) Signaling". [i.16] IETF RFC 4762: "Virtual Private LAN Service Using BGP for Auto-Discovery and Signaling". [i.17] IEEE 802.3™: "Ethernet". [i.18] IEEE 802.3az™: "IEEE Standard for Information technology -- Local and metropolitan area networks -- Specific requirements -- Part 3: CSMA/CD Access Method and Physical Layer Specifications -- Amendment 5: Media Access Control Parameters, Physical Layers, and Management Parameters for Energy-Efficient Ethernet". [i.19] IEEE 802.3ab™: "IEEE Standard for Information Technology -- Telecommunications and information exchange between systems -- Local and Metropolitan Area Networks -- Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications -- Physical Layer Parameters and Specifications for 1000 Mb/s Operation over 4 pair of Category 5 Balanced Copper Cabling, Type 1000BASE-T". ETSI ETSI TS 110 174-2-1 V1.1.1 (2018-11) 8 [i.20] IEEE 802.3u™: "IEEE Standards for Local and Metropolitan Area Networks-Supplement -- Media Access Control (MAC) Parameters, Physical Layer, Medium Attachment Units and Repeater for 100Mb/s Operation, Type 100BASE-T (clauses 21-30)". [i.21] IEEE 802.3z™: " Media Access Control Parameters, Physical Layers, Repeater and Management Parameters for 1,000 Mb/s Operation, Supplement to Information Technology -- Local and Metropolitan Area Networks -- Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications". [i.22] IEEE 802.3af™: " IEEEE Standard for Information Technology - Telecommunications and Information Exchange Between Systems -- Local and Metropolitan Area Networks - Specific Requirements -- Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications -- Data Terminal Equipment (DTE) Power Via Media Dependent Interface (MDI)". [i.23] IEEE 802.3at™: "IEEE Standard for Information technology -- Local and metropolitan area networks -- Specific requirements -- Part 3: CSMA/CD Access Method and Physical Layer Specifications -- Amendment 3: Data Terminal Equipment (DTE) Power via the Media Dependent Interface (MDI) Enhancements". [i.24] IEEE 802.1q™: "EEE Standard for Local and metropolitan area networks--Bridges and Bridged Networks". [i.25] Guide Pratique - Déploiement de la Boucle Locale Optique Mutualisée sur support aérien. NOTE: Available at https://www.objectif-fibre.fr/wp-content/uploads/2015/12/121115-Guide-pratique- BLOM.pdf. [i.26] IETF RFC 1034: "Domain Names - Concepts and Facilities". [i.27] IETF RFC 1035: "Domain Names - Implementation and Specification". [i.28] UEFI Forum: "ACPI specification". NOTE: Available at http://www.uefi.org/specifications. [i.29] IETF RFC 2474: "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". [i.30] IETF RFC 2475: "An Architecture for Differentiated Services". [i.31] Recommendation ITU-T G.9959: "Short range narrow-band digital radiocommunication transceivers - PHY, MAC, SAR and LLC layer specifications". [i.32] IEEE 802.1D™-2004: "IEEE Standard for Local and metropolitan area networks: Media Access Control (MAC) Bridges". [i.33] IEEE 802.11e™-2005: "IEEE Standard for Information technology -- Local and metropolitan area networks -- Specific requirements -- Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications -- Amendment 8: Medium Access Control (MAC) Quality of Service Enhancements". [i.34] IEEE 802.11ad™-2012: "IEEE Standard for Information technology -- Telecommunications and information exchange between systems--Local and metropolitan area networks--Specific requirements -- Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications -- Amendment 3: Enhancements for Very High Throughput in the 60 GHz Band". [i.35] IEEE 802.11ac™: "IEEE Standard for Information technology -- Telecommunications and information exchange between systems -- Local and metropolitan area networks -- Specific requirements -- Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications -- Amendment 4: Enhancements for Very High Throughput for Operation in Bands below 6 GHz". [i.36] IEEE 802.3bv™: "IEEE Standard for Ethernet Amendment: Physical Layer Specifications and Management Parameters for 1000 Mb/s Operation Over Plastic Optical Fiber". ETSI ETSI TS 110 174-2-1 V1.1.1 (2018-11) 9 [i.37] 3GPP specifications. NOTE: Available at http://www.3gpp.org/specifications/specifications. |
3fe5352ea29484004b7f0a2cc1be07d5 | 110 174-2-1 | 3 Definition of terms and abbreviations | |
3fe5352ea29484004b7f0a2cc1be07d5 | 110 174-2-1 | 3.1 Terms | For the purposes of the present document, the following terms apply: digital multiservice cities: cities using digital infrastructure which consists of a single unified high-speed networking infrastructure that allows the ICT systems of the complete city services departments to interconnect seamlessly and securely to each other street furniture: collective term for objects and pieces of equipment (subcategory of the urban assets), installed on city streets, city roads, and public areas under responsibility of the city for various purposes NOTE: These objects and equipment belong to the wider terminology of the urban assets as named by cities. urban asset: collective term to qualify the physical assets which belong to a city and which are located across its territory, in streets, roads, public parks and associated urban constructions |
3fe5352ea29484004b7f0a2cc1be07d5 | 110 174-2-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACPI Advance Configuration and Power Interface AIOTI Alliance for the Internet of Things Innovation NOTE: In particular AIOTI WG3 on IoT Standardization. AP Access Point ATTM Access, Terminals, Transmission and Multiplexing BTS Base Transceiver Station CCTV Closed-Circuit TeleVision DNS Domain Name Service Gbit/s Giga bits per second HMI Human Machine Interface ICT Information and Communication Technology IEC International Electrotechnical Commission IEEE Institute for Electrical and Electronics Engineers IETF Internet Engineering Task Force IIC Industrial Internet Consortium IMT International Mobile Telecommunications IoT Internet of Things IP Internet Protocol ISM Industrial, Scientific, and Medical ISO International Organization for Standardization ISP Internet Service Provider IT Information Technology ITU International Telecommunication Union JTC Joint Technical Committee Kbit/s Kilo bits per second LAN Local Area Network LP-LAN Low-Power Local-Area Network LP-WAN Low-Power Wide-Area Network LR-WPAN Low-Rate Wireless Personal Area Networks LSP Label Switch Path M2M Machine to Machine ETSI ETSI TS 110 174-2-1 V1.1.1 (2018-11) 10 MAC Media Access Control MAN Metropolitan Area Network MPLS Multiprotocol Label Switching NFC Near Field Communication NGN Next Generation Network NT Network Termination OASIS Organization for the Advancement of Structured Information Standards OCF Open Connectivity Foundation oneM2M Partnership Project oneM2M launched by a number of SSOs including ETSI ONVIF Open Network Video Interface Forum OS Operating System PoE Power over Ethernet POF Plastic Optical Fiber PSIA Physical Security Interoperability Alliance QoS Quality of Services RF Radio Frequency RFC Request For Comments SLA Service Level Agreement SP Service Provider SSID Service Set IDentifiers STF Special Task Force TR Technical Report TxRx Transceiver equipment UEFI Unified Extensible Firmware Interface UHD Ultra High Definition UTP Universal Twister Pair VLAN Virtual Local Area Network VLC Visible Light Communications VPLS Virtual Private LAN Service W3C World Wide Web Consortium WAN Wide Area Network Wi-Fi Wireless Fidelity WiGig Wireless Gigabit WMM Wi-Fi Multimedia WSN Wireless Sensor Network |
3fe5352ea29484004b7f0a2cc1be07d5 | 110 174-2-1 | 4 Multiservice digital infrastructure | |
3fe5352ea29484004b7f0a2cc1be07d5 | 110 174-2-1 | 4.1 A shared digital infrastructure as core foundation | The core foundation for a digital multiservice city is strongly tightened to the ability that the components of its ICT systems have to interoperate. To achieve this goal, a city should install a shared communications infrastructure that will allow the ICT systems of the complete services departments to interconnect seamlessly and securely to each other. 4.2 Management of the various network cabling infrastructures of the city Performant ICT requires the access to a high-speed network. To achieve the goal of an ubiquitous digital access the city network backbone should span across the entire territory. When seen through the silos approach, the deployment of such a broadband network architecture, mainly composed of optical fibre and most probably high-speed wireless point to point links, on a large geographical scale is a complex and expensive civil engineering challenge. However, when seen through the cross-domain approach, evidence demonstrates the benefit of sharing passive infrastructure amongst different city departments of city partners such as utilities. Numerous city network infrastructures can be leveraged to achieve this strategy: • Access to electrical power distribution infrastructure. ETSI ETSI TS 110 174-2-1 V1.1.1 (2018-11) 11 • Access to ducts, trenches. • Access to lighting infrastructure. • Access to water distribution infrastructure. • Access to traffic control infrastructure (e.g. traffic lights, signs, pipes, etc.). • Access to gas distribution infrastructure. • Access to district heating infrastructure. • Access to sewer collecting infrastructure. • Access to city infrastructure of private users/operators (e.g. telecommunications and cable operators) through renting pipe spaces, access to poles/masts, etc.). Furthermore, other passive city assets such as real estate properties (technical room facility), conduits, manholes, cabinets, lampposts, poles, masts, antennaes, towers and other supporting constructions could also play an important role in the design of the digital multiservice city infrastructure. Best practices in network architectures organize the infrastructure topology into a multi layered structure which spans across the geographical area to deserve at city scale or urban metropolis scale: • Layer 1: Digital multiservice city core network: - The core network provides high-speed and redundant forwarding services to move the data packet between the distribution nodes which span across the city area. The core nodes (usually routers) are commonly the most powerful, in terms of forwarding power; they define the Wide Area Network (WAN). When city communication networks interconnect to each other, some of these nodes also acts as Metropolitan Area Network (MAN) inter-exchanges nodes. Current appropriated bandwidth are high speed links such as Gigabit and 10 Gigabits or higher speeds. • Layer 2: Digital multiservice city distribution Network: - The distribution network is often referred as the multiservice delivery level which offer several smart layers' functionalities for the various policies related to data packet routing, data packet filtering and Quality of Services (QoS). The distribution nodes (usually routers and switches) are mainly dedicated to connecting the network sites (LAN) to each other; their links to the network sites are often referred as last mile connections. Appropriate dispersal of these network nodes across the city geographical area makes them also an appropriate place to connect special delivery network elements, such as the municipality urban assets. Current appropriated bandwidth are high speed links such as Gigabit (and potentially 10 Gigabits). • Layer 3: Digital multiservice city access Network: - The access network is often referred to the desktop layer. The access nodes (usually switches) have the main concern to connect the end hosts (workstation, server, enterprise devices: wireless access point (AP), printer, scanner, IP phone/camera, etc) to the city network infrastructure. The proximity of these nodes to the end devices makes them also an appropriate place to deliver secured electricity power (Power over Ethernet, PoE IEEE 802.3af [i.22] or IEEE 802.3at [i.23]) to low consumption devices (Wi-Fi AP, IP phone/camera, IoT gateway, etc). Current appropriated bandwidth are high speed Gigabit connections. When reaching the network site layer, the hierarchy of the infrastructure topology can be further organized in stratums to fit the actual architectural structure of the local area (single or multi floors house/building, a multi constructions administrative district/campus) to be served. Typical network topology for LAN access includes star, mesh, tree, and clusters. The digital multiservice delivery across the city-wide area implies to cope with multiple distances ranges. Core node links can deal with long distances which ranges from km to tens of km whereas distribution nodes links deal with distances from hundreds of metres to a km. ETSI ETSI TS 110 174-2-1 V1.1.1 (2018-11) 12 Off course, the transmission capability to achieve such distances depends on the physical communication medium: optical fibre is nowadays the preferred media to succeed in the delivery of multi (tens/hundreds) gigabits in long distances (core/distribution) links through optical transmissions. However, in various cases electrical transmissions over copper (twisted pair or coax) or wireless links can still be delivering acceptable high-speed data rate for distribution network links. ETSI TR 105 174-4 [i.3] and ETSI TS 105 174-4-1 [i.4] detail measures which may be taken to improve the energy management of access networks for broadband deployment. As far as possible, the city should do everything to have total control over its digital multiservice city infrastructure. In other words, it is valuable and advantageous for the city to deploy its own physical networking fibre connectivity links when technically feasible. When considered in a mid (3 years) to long term (10 years) strategic vision, having the ownership of the networking links is smarter than having contractual access to a service provider (SP) infrastructure. Besides such economical considerations, there are various technical reasons which drive the city to deploy its own physical fibre network infrastructure or to contract, from a carrier, for dark (unlit) fibre links or to rent ducts from third parties to install its own cables: • Freedom of the optical transmission standard: network bandwidth depends of the fibre transceivers which are bound at the extremities of the fibre link and the length of this one. According to the link needs, the municipality can lit the fibre with the most appropriate transceiver (from a single wavelength to wavelength- division multiplexing, from gigabit to multigigabits). Should a link speed need to increase, the municipality has the freedom to upgrade the transceivers. • Freedom of the digital transmission standard: digital data transmissions can be operated by various technologies such as Ethernet, MPLS, etc. According to the engineering of the digital services and the requirement for network resilience one can be more suitable than the other. Network size, number of digital services, security concerns, multi-homing requirement, etc. are concerns which drives the choice of the optimal transmission standard. • Ease of introduction of new digital services: to leverage a single physical network infrastructure sharing while delivering to each digital service within its own controlled environment, the municipality can either chose to introduce a new IP service by the means of a complementary VLAN in Ethernet, a complementary LSP in MPLS, or even by the assignment of a specific light wavelength which virtualizes the link at the optical level. • Freedom of the choice of ISP: different Internet access might be required to be served by different service providers. While public administration agents require access to specific Internet service providers with specified technical SLA (redundancy, low latency, security, etc.), schools, libraries, police, citizen free public Internet, IoT sensors, etc. may use other service providers. ETSI TS 105 174-1 [i.2] focuses on the best practices for cabling and installations and transmission implementation independently from the ownership of these infrastructures. ETSI TS 102 973 [i.5] describes a proposal of requirements for a Network Termination (NT) device in Next Generation Access Networks. Deploying networking links includes planning and routing, obtaining permissions, creating ducts and channels for the cables, and finally installation and connection. When the situation permits, aerial links installation has to be preferred instead of digging the streets or sidewalks. In that concern, Objectif Fibre organization from the Federation des Industries Electriques, Electroniques et de Communication (FIEEC) has published a practical guide to deploy shared local optical infrastructure over aerial support [i.25]. However, there are various situations in which completely following such a strategy is simply unfeasible. In such cases, when contracting with an SP, passive network links (e.g. dark fibres) have to be preferred over active network links (e.g. leased line). Digital service end points are usually distant from their access nodes in range from a few metres to a few hundred metres. As for the other communication layers, speed, achieved distance and access flexibility depend on the physical medium in use. Cable free connectivity offered by wireless technologies such as Wi-Fi (Electromagnetic Communication, EM) or Li-Fi [i.8] (an improvement of Visible Light Communication, IEEE VLC [i.11]) deliver suitable speeds, to the user desktop. From hundreds of gigabits over a few metres with LiFi (under certain conditions) up to multi-gigabits over hundreds of meters for existing contemporary IEEE Wi-Fi standards (e.g. IEEE 802.11ac [i.35]: 1 Gbit/s, IEEE 802.11ad [i.34]/WiGig [i.13]: 4 Gbit/s). ETSI ETSI TS 110 174-2-1 V1.1.1 (2018-11) 13 Current trends raised by the fields of IoT and M2M give to low speed (few kbit/s or hundred kbit/s) wireless communication technologies a significant role to play into the digital multiservice city infrastructure. Connectivity in this low speed and low power wireless network access can be categorized into two main viewpoints: short distance (LR-WPAN, LP-LAN) and long distance (LP-WAN). In the former viewpoint, connected objects join the IoT wireless (mainly in unlicensed RF ISM band) gateway hooked to the city infrastructure at the Access Network layer whereas in the later viewpoint the connected objects join the IoT Base Transceiver Station (BTS) of a mobile operator network infrastructure (using its licenced RF band). ETSI TR 103 375 [i.6] provides a complete landscape view on these IoT technologies for Smart Cities. Regarding the data transport technology, it is clear that IP (v4 and v6) and Ethernet [i.17] are the most suitable addressing and data transmission protocols to be deployed for the digital multiservice city infrastructure layers. Appropriate addressing plan, network hierarchy, security policies such as packet filtering and firewalling rules as well as and related QoS support have to be well engineered to achieve the design of a digital multiservice city delivery infrastructure. Furthermore, although Ethernet has been proven to be a good transport technology for WAN, large city core network may need to consider other types of carrier class transport technologies such as Multiprotocol Label Switching (MPLS, IETF RFC 3031 [i.14]) or Virtual Private LAN Service (VPLS, IETF RFC 4761 [i.15] and IETF RFC 4762 [i.16]). However, these considerations as well as engineering details on optical network architectures are outside the scope of the present document. |
3fe5352ea29484004b7f0a2cc1be07d5 | 110 174-2-1 | 5 Digital services delivery through the urban assets | |
3fe5352ea29484004b7f0a2cc1be07d5 | 110 174-2-1 | 5.1 Leveraging street furniture with digital technologies | Street furniture is a collective term for objects and pieces of equipment installed on city streets and city roads for various purposes. These urban assets include the objects listed in the following clauses. Many of these city urban assets can be leveraged to either contribute as: • network access nodes within the multilayer mesh which constitute the unified digital communication infrastructure; • a service distribution and wireless AP node towards end users or connected objects (sensors, actuators) of the IoT world. 5.2 Usages of billboards, streetlamps, bollards and various poles, benches and picnic tables Most of these urban assets can play a role in the enhancement of the sustainability of the city. These assets can be promoted to a role which provides additional services beyond the native one. For instance, these urban assets can be the operation points for: • Communications as transmitter/receiver points for data communications through Li-Fi. • Provide public Wi-Fi services as a new city infrastructure. • Public security, through use of CCTVs (IP video security) on posts. • Control of light attenuation levels. • Environmental sensing (air quality, noise pollution monitoring). • Environmental management through CCTVs. • Traffic control through through CCTVs or radar. • Parking (monitoring) availability and access through sensors and actuators. ETSI ETSI TS 110 174-2-1 V1.1.1 (2018-11) 14 • Smart meters reading. • Sound level monitoring through sensors. • Movement activity monitoring through motion sensors of CCTVs. • Image sensing (proximity, pedestrian counter). • Digital signage (way finding, traffic direction, civic information). • Water level/flood monitoring. • Etc. Through these various data sources, intelligent cross domain analysis and processing (most probably through Big Data platform) can be leveraged to offer useful services to the city and it is audiences. Typical example includes the adaptation of the streetlamp illumination level according to environmental parameters such as lighting condition, proximity of a user, detection of an abnormal incident. Offering to the citizen a better quality of life could be a simple as sharing the harvested information related to the quality of the air or the presence of high levels of flower pollens in resting areas, green parks and other child playgrounds. Beside data harvesting functions, these urban assets can be considered as information delivery points, to the proximity users, either through local display mechanism (e.g. info kiosks, interactive or not) either through digital service delivery pushing the contextualized information directly into the user mobile terminal (e.g. smartphone, tablet) via locally generated wireless access point (e.g. Wi-Fi, Bluetooth, Near Field Communication (NFC)) or through voice and data communication over cellular networks (e.g. via small cells). |
3fe5352ea29484004b7f0a2cc1be07d5 | 110 174-2-1 | 5.3 Usages of bus or tram stops, taxi stands and phone boxes | Most of these urban assets can play a role in the enhancement of the sustainability of the city and the operations of their partners. These assets can be promoted to a role which provides additional services beyond the native one. These urban assets have in common the particularity of being in places which concentrate significate numbers of individuals who standing there for a while and often expect precise details related to the service delivery (e.g. real- time-schedule, availability, traffic conditions, etc.). One-dimensional approach for connecting such urban assets to the digital multiservice city network can be to connect dynamic display boards, CCTV camera or Wi-Fi hotspot. By adopting a multi-dimensional approach, innovative and sustainable new type of operation can be offered. Local facts such as the number of persons, the presence of disabled persons can be valuable information that can be taken into account by the IT system to take decisions and improve the dynamic operation of the transportation system. Furthermore, as a place which concentrates significant number of individuals in a defined area, these urban assets may be considered as an appropriate location to deliver cellular network communications (e.g. via small cells). This would represent on one side the opportunity to improve the overall performances of the mobile network while opening a complementary channel for (geo)localized digital service information delivery directly into the user mobile terminal. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.