hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.2.3 Procedures | @startuml Title Software Inventory autonumber "[0]" participant "PNF Software MnS Consumer" as NMS participant "PNF Software MnS Provider" as ME NMS <-> ME : Establish NETCONF Session NMS -> ME: NETCONF <rpc> <get><filter> Note over ME : Retrieve Software Inventory Information ME --> NMS: NETCONF <rpc-reply> <data> NMS <-> ME : Terminate NETCONF Session @enduml ETSI ETSI TS 104 043 V11.0.0 (2024-06) 53 Figure 6.8.2.3-1: Software Inventory Procedure: 1) PNF Software MnS Consumer establishes NETCONF session with PNF Software MnS Provider. The NETCONF session has authorized read privileges into the identified section of the data store. 2) PNF Software MnS Consumer sends NETCONF <rpc> <get><filter> to retrieve an optionally filtered subset configuration from the running configuration datastore. <filter> can be used to identify the software package MOIs. GET retrieves configuration and operational state of softwarePackage MOIs: a) PNF Software MnS Provider retrieves software inventory information. 3) PNF Software MnS Provider returns requested data in NETCONF <rpc-reply> response. 4) PNF Software MnS Consumer terminates NETCONF session with PNF Software MnS Provider. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.3 Software Download | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.3.1 Description | Software Download triggers the download of a specific software package to the PNF Software MnS Provider. This download service includes integrity checks on the downloaded software and the installation of the software into the software slot corresponding to the softwarePackage MOI. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.3.2 Requirements | REQ-SWD-FUN-1: The PNF software management service provider shall have the capability to allow its authorized consumer to specify the location of software that is to be downloaded and to specify into which softwarePackage the software is to be stored. REQ-SWD-FUN-2: The PNF software management service provider shall have the capability to verify if a software download is in progress and the ability to reject subsequent download commands until the one in progress completes. REQ-SWD-FUN-3: The PNF software management service provider shall have the capability to deny download of software if the download request is not valid for the PNF software management service provider. REQ-SWD-FUN-4: The PNF software management service provider shall have the capability to download needed files from a software server at a specified location. REQ-SWD-FUN-5: The PNF software management service provider shall have the capability to perform integrity checks on downloaded software. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 54 REQ-SWD-FUN-6: The PNF software management service provider shall have the capability to notify the PNF software management consumer with the software download result. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.3.3 Procedures | @startuml skin rose Title Software Download autonumber "[0]" participant "PNF Software MnS Consumer" as NMS participant "PNF Software MnS Provider" as ME participant "Software Server" as SWS NMS <-> ME : Establish NETCONF Session NMS -> ME: NETCONF <rpc><software-download><remote-file-path><softwarePackage> Note over ME : Validate Request ME --> NMS: NETCONF <rpc-reply><software-download-status> NMS <-> ME : Terminate NETCONF Session ME -> SWS : <<FTPeS, SFTP or HTTPS>> file download Note over ME : Integrity check SW Note over ME : Store SW in a persistent location Note over ME : Update softwarePackage Opt Download Progress Notifications ME ->> NMS : <<HTTP/TLS>> downloadFile Event End ||| ME ->> NMS : <<HTTP/TLS>> downloadFile Event @enduml Figure 6.8.3.3-1: Software Download Procedure: 1) PNF Software MnS Consumer establishes NETCONF session with PNF Software MnS Provider. The NETCONF session has authorized execution privileges for retrieve file list and file-download rpcs. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 55 2) PNF Software MnS Consumer sends NETCONF <rpc><software-download><remote-file- path><softwarePackage> to trigger a download of the software located at remoteFilePath and save its information in softwarePackage: a) PNF Software MnS Provider validates the request. Validation includes determining if the operation can be performed. This is PNF Software MnS Provider specific but could include things like: checking that there is not a software download already in progress, softwarePackage is runningState = passive and softwareType = operational, etc. 3) PNF Software MnS Provider returns NETCONF <rpc-reply><software-download-status>. 4) PNF Software MnS Consumer terminates NETCONF session with PNF Software MnS Provider. 5) PNF Software MnS Provider initiates SFTP, FTPES or HTTPS connection and downloads the software package from remoteFilePath. SFTP is authenticated with username/password, SSH keys or X.509 certificates. FTPES is authenticated with X.509 certificates. HTTPS is mutually authenticated with X.509 certificates. PNF Software MnS Provider understands the software package format and downloads all the files it needs from the package. PNF Software MnS Provider decides where to store the software internally. This is PNF Software MnS Provider specific but could be a temporary location like /tmp: a) PNF Software MnS Provider integrity checks the downloaded software. This is PNF Software MnS Provider specific but could include checking checksum, correct software for the hardware, etc. b) PNF Software MnS Provider stores the software in a persistent location. c) PNF Software MnS Provider updates softwarePackage attributes for the downloaded software. 6) (Optional) If the download takes a long time, PNF Software MnS Provider may send periodic downloadFile notifications to the PNF Software MnS Consumer with the current status of the download (download in progress, integrity checks passed, install complete). 7) When download operation completes, PNF Software MnS Provider sends downloadFile event notification to PNF Software MnS Consumer with the final status of the download (success or the reason for failure). |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.3.4 Operations and Notifications | A File Download notification shall be in one of the following formats: - SDO O1 format: - Either a 3GPP-specified notifyFileDownload or a O-RAN-specified o1NotifyFileDownload notification should be defined. - VES O1 format: - A Harmonized VES event, as specified in the VES Event Listener Specification [18], containing stndDefinedFields with a "data" element that contains either a 3GPP-specified notifyFileDownload or a O-RAN-specified o1NotifyFileDownload notification. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.4 Software Activation Pre-Check | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.4.1 Description | Activation Pre-check is an optional Use Case that the Service Provider can choose to utilize prior to software activation to confirm that the PNF Software MnS Provider is in a good state to activate the new software and provide information needed for planning the timing of the software replacement--such as whether a reset or a data migration is required. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.4.2 Requirements | REQ-SPC-FUN-1: The PNF software management service provider shall have the capability to confirm that the software in the passive slot targeted for activation is good. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 56 REQ-SPC-FUN-2: The PNF software management service provider shall have the capability to determine whether the activation of the targeted software requires a reset and/or data migration. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.4.3 Procedures | @startuml Title Activation Pre-Check autonumber "[0]" participant "PNF Software MnS Consumer" as NMS participant "PNF Software MnS Provider" as ME NMS <-> ME : Establish NETCONF Session NMS -> ME: NETCONF <rpc><activation-pre-check><softwarePackage> Note over ME : Perform Pre-Check ME --> NMS: NETCONF <rpc-reply> <data> NMS <-> ME : Terminate NETCONF Session @enduml Figure 6.8.4.3-1: Software Activation Pre-Check Procedure: 1) PNF Software MnS Consumer establishes NETCONF session with PNF Software MnS Provider. 2) PNF Software MnS Consumer sends NETCONF <rpc><activation-pre-check><softwarePackage> to trigger a pre-check of the software stored in softwarePackage and to return the results of the pre-check: a) PNF Software MnS Provider performs the activation pre-check which includes validating that the software in softwarePackage is good, whether the activation of the software in softwarePackage will result in a reset and whether data migration is needed, etc. 3) PNF Software MnS Provider returns NETCONF <rpc-reply> to the PNF Software MnS Consumer with the results of the pre-check. 4) PNF Software MnS Consumer terminates NETCONF session with PNF Software MnS Provider. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.5 Software Activate | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.5.1 Description | PNF Software MnS Consumer triggers the activation of a software package on the PNF Software MnS Provider including data migration and reset if needed. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 57 |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.5.2 Requirements | REQ-SWA-FUN-1: The PNF software management service provider shall have the capability to allow its authorized consumer to activate valid software in a specific softwarePackage. REQ-SWA-FUN-2: The PNF software management service provider shall have the capability to verify whether a software activation is in progress and deny a concurrent activation of software. REQ-SWA-FUN-3: The PNF software management service provider shall have the capability to deny activation of software if the activation request is not valid for the PNF software management service provider. REQ-SWA-FUN-4: The PNF software management service provider shall have the capability to activate the softwarePackage. REQ-SWA-FUN-5: The PNF software management service provider shall have the capability to reset the PNF software management service provider if the software activation requires it. REQ-SWA-FUN-6: The PNF software management service provider shall provide the capability for the PNF software management service provider to send a re-set reason notification to its authorized consumer if the activation results in a reset. REQ-SWA-FUN-7: The PNF software management service provider shall have the capability to perform data migration on the PNF software management service provider if the software activation requires it. REQ-SWA-FUN-8: The PNF software management service provider shall have the capability to fallback to the previously active software if the new software cannot be activated. REQ-SWA-FUN-9: The PNF software management service provider shall have the capability to fallback to the factory software if the new and the previously active software can not be activated. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.5.3 Procedures | @startuml Title Software Activate autonumber "[0]" participant "PNF Software MnS Consumer" as NMS participant "PNF Software MnS Provider" as ME NMS <-> ME : Establish NETCONF Session NMS -> ME: NETCONF <rpc><software-activate><softwarePackage> Note over ME : Validate request ME --> NMS: NETCONF <rpc-reply> <status> NMS <-> ME : Terminate NETCONF Session Note over ME : Activate Software Alt if Data Migration or Reset are needed then Alt if Data Migration Needed then Note over ME : Migrate Data if needed ||| End Alt if Reset Needed then Note over ME : Reset ME ->> NMS : <<HTTP/TLS>> resetReason Event ||| End ||| End Alt if Activation fails then Note over ME : Fallback if failure ||| End Opt Activation Progress Notifications ME ->> NMS : <<HTTP/TLS>> softwareActivate Event End ||| ME ->> NMS : <<HTTP/TLS>> softwareActivate Event Note over ME : Config change occurs ME ->> NMS : <<HTTP/TLS>> notifyMOIAttributeValueChange Event Note over NMS : Reconcile Database @enduml ETSI ETSI TS 104 043 V11.0.0 (2024-06) 58 Figure 6.8.5.3-1: Activate Software ETSI ETSI TS 104 043 V11.0.0 (2024-06) 59 Procedure: 1) PNF Software MnS Consumer establishes NETCONF session with PNF Software MnS Provider. 2) PNF Software MnS Consumer sends NETCONF <rpc><software-activate><softwarePackage> to trigger an activation of the software in softwarePackage: a) PNF Software MnS Provider validates the request. This is PNF Software MnS Provider specific but could include things like checking that there is not a software activation already in progress, softwarePackage is runningState = passive and integrityStatus = valid, etc. 3) PNF Software MnS Provider returns status to the PNF Software MnS Consumer in the NETCONF <rpc- reply> response: a) PNF Software MnS Provider performs the steps needed to make the softwarePackage the active one. This is PNF Software MnS Provider specific but includes things like updating the runningState of the about-to-be-active and previously-active software packages. 4) PNF Software MnS Consumer terminates NETCONF session with PNF Software MnS Provider. (Optional) PNF Software MnS Provider performs data migration if necessary. PNF Software MnS Provider knows whether this is necessary. 5) (Optional) PNF Software MnS Provider performs reset if necessary. PNF Software MnS Provider knows whether reset is necessary. If a reset occurs, PNF Software MnS Provider sends a resetReason notification to the PNF Software MnS Consumer with the reason for the reset; in this case software activation. (Optional) If the PNF Software MnS Provider can not activate the software, PNF Software MnS Provider has recovery logic to fallback to the previously active software and potentially fallback to the factory software in a worst-case scenario. 6) (Optional) If the activation takes a long time, PNF Software MnS Provider sends periodic softwareActivate notifications to PNF Software MnS Consumer with the current status of the activation (e.g. activation in progress, data migration successful). 7) After activation operation completes, PNF Software MnS Provider sends a softwareActivate notification to PNF Software MnS Consumer with the final status of the activation. 8) PNF Software MnS Provider sends notifyMOIAttributeValueChange to the PNF MnS Consumer updating the active software running on the PNF. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.5.4 Operations and Notifications | A Software Activate notification shall be in one of the following formats: - SDO O1 format: - Either a 3GPP-specified notifySoftwareActivate or an O-RAN-specified o1NotifySoftwareActivate notification should be defined. - VES O1 format: - A Harmonized VES event, as specified in the VES Event Listener Specification [18], containing stndDefinedFields with a "data" element that contains either a 3GPP-specified notifySoftwareActivate or an O-RAN-specified o1NotifySoftwareActivate notification. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.9 PNF Reset Management Services | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.9.0 Overview | PNF Reset Management Services allow a PNF Reset MnS Consumer to trigger a reset of a HW unit of a PNF Reset MnS Provider on command. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 60 |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.9.1 PNF Reset Command | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.9.1.1 Description | The PNF Reset Command procedure allows a PNF Reset MnS Consumer to trigger a reset of a HW unit of a PNF Reset MnS Provider on command. Any HW unit that is resettable via a reset command is represented by a Managed Object Instance (MOI) and is able to be identified by a Distinguished Name (DN). The NETCONF RPC <reset> command identifies the unit to reset by the DN. The unit to reset can be the entire PNF or a resettable HW subcomponent of the PNF. A resettable HW subcomponent of a PNF is a subcomponent of a PNF that is able to be independently reset and whose PNF Reset MnS Provider supports a reset command for the subcomponent. It is vendor and PNF-specific whether a PNF has resettable HW subcomponents. The reset command also has an attribute to identify the type of reset requested. The types of reset commands that a PNF supports are vendor and PNF specific. O-RAN O1 Interface Specification specifies two mandatory reset command types that every PNF supports: conditional and forced. A conditional reset command can be rejected by the PNF Reset MnS Provider depending on the conditions on the PNF, for example if the unit to reset is not in a proper state to reset, such as, if there is an emergency call in progress on the unit. A valid forced reset command cannot be rejected. Valid means that the unit to reset supports a reset command. Invalid forced resets will be rejected, for example, if the unit to reset is not a resettable HW unit, such as a cell. Vendors are allowed to extend the O1 specified reset command types to add vendor and PNF specific reset command types. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.9.1.2 Requirements | REQ-RM-FUN-1: The PNF Reset MnS Provider shall support the capability for a PNF Reset MnS Consumer to trigger a reset of a HW unit of the PNF Reset MnS Provider on command. REQ-RM-FUN-2: The PNF Reset MnS Provider shall support reset command types conditional and forced. REQ-RM-FUN-3: The PNF Reset MnS Provider shall be allowed to reject a conditional reset command type. NOTE 1: The validations performed and the reasons for a conditional reset rejection, if any, are vendor and PNF specific. REQ-RM-FUN-4: The PNF Reset MnS Provider shall not be allowed to reject a valid forced command reset type. NOTE 2: Valid means that the unit to reset supports a reset command. Invalid forced resets will be rejected, for example, if the unit to reset is not a resettable HW unit, such as a cell. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.9.1.3 Procedures | This procedure shows how a PNF Reset MnS Consumer triggers a reset of a HW unit of a PNF Reset MnS Provider on command. The HW unit to reset is identified by the <unitToReset> input attribute. The type of reset command is identified by the <resetCommandType> input attribute. The <status> output attribute returned in the NETCONF response indicates whether the reset command has been accepted. The unit is reset after the NETCONF response is returned. The reason for the reset (e.g. conditional reset command or forced reset command) is persistently stored by PNF Reset MnS Provider before executing the reset. @startuml Title PNF Reset Command participant "PNF Reset MnS Consumer" as NMS participant " PNF Reset MnS Provider" as ME NMS -> ME: 1 NETCONF <rpc><reset><unitToReset><resetCommandType> Note over ME : 2 Validate command \n Save reset reason ME --> NMS: 3 NETCONF <rpc-reply><reset><status> Note over ME : 4 Reset unit @enduml ETSI ETSI TS 104 043 V11.0.0 (2024-06) 61 Figure 6.9.1.3-1: PNF Reset Command Pre-conditions: - PNF Reset MnS Consumer has established a NETCONF session to the PNF Reset MnS Provider as specified in Provisioning Management Services, clause 6.1.8. The NETCONF session has authorized execution privileges for <reset> RPC. - (Optionally) PNF Reset MnS Consumer has locked the appropriate DS of the PNF Reset MnS Provider as specified in Provisioning Management Services, clause 6.1.10. Procedure: 1) PNF Reset MnS Consumer sends NETCONF <rpc> <reset> <unitToReset><resetCommandType> to PNF Reset MnS Provider, indicating the unit to reset and the type of reset command. 2) PNF Reset MnS Provider validates the command. Validation is vendor and PNF specific but typically includes verifying that the <unitToReset> is resettable and can be reset at this time. A conditional reset command type allows the PNF Reset MnS Provider to reject the reset command, depending on the conditions on the PNF, for example if an emergency call is in progress. The conditions are vendor and PNF specific. A valid forced reset command type cannot be rejected. Valid means that the unit to reset supports a reset command. Invalid forced resets will be rejected, for example if the unit to reset is not a resettable HW unit, such as a cell. If the reset command is accepted, the reset reason (e.g. conditional reset command or forced reset command) is stored persistently on the PNF Reset MnS Provider. 3) PNF Reset MnS Provider responds, indicating in the <status> attribute whether the command is accepted. If the command is rejected, the <rpc-reply> contains an <rpc-error> element with the reason for the rejection. 4) Unit is reset. Post-conditions: - (Optionally) PNF Reset MnS Consumer unlocks the DS of the PNF Reset MnS Provider after sending the reset command, as specified in Provisioning Management Services, clause 6.1.11. - (Optionally) PNF Reset MnS Consumer terminates the NETCONF session to the PNF Reset MnS Provider after sending the reset command, as specified in Provisioning Management Services, clause 6.1.9. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.9.1.4 Operations | Information Model and YANG solution set for the NETCONF RPC <reset> command and its attributes will be specified in the O-RAN Information Model and Data Models Specification [i.14]. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 62 |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.9.2 Notifications | REQ-RN-FUN-1: A PNF MnS Provider shall support the capability to inform a PNF MnS Consumer that a reset has occurred and the reason that a HW unit has reset. REQ-RN-FUN-2: A PNF MnS Provider shall save the reason for a reset persistently before resetting. NOTE 1: This requirement applies to resets that occur under the control of the PNF. REQ-RN-FUN-3: If a reset reason has not been saved persistently, the PNF MnS Provider shall set the reset reason to unknown in the notification. NOTE 2: This requirement applies to resets that occur unexpectedly before the reset reason could be stored. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.10 Cloudified NF Registration Management Service | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.10.0 Overview | The Cloudified NF Registration Management Service supports the registration of a Cloudified NF Registration Management Service Provider to the Cloudified NF Registration Management Service Consumer after the Cloudified NF instantiation via the O2 has completed and the NF application has initialized and is ready for final configuration and management (e.g. ready to be put in service). Application initialization includes things like setting up the NETCONF server, creating MOIs for the NF, and perhaps some vendor specific steps which can take place after the Cloudified NF instantiation completes. The Cloudified NF Registration MnS is applicable to VNFs and CNFs and supports the NF informing the SMO when it has completed its initialization steps and is ready to be managed. Without this service, the SMO would have to poll the NF until the NF responded that it had completed its application initialization and was ready for final configuration (if needed) and management. Registration is accomplished by sending a Cloudified NF Registration notification. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.10.1 Cloudified NF Registration Notification | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.10.1.1 Description | To register, the Cloudified NF Registration MnS Provider sends an asynchronous o1NotifyCloudNFRegistration event to a Cloudified NF Registration MnS Consumer to notify the Cloudified NF Registration MnS Consumer of a new Cloudified NF Registration MnS Provider to be managed. The Cloudified NF Registration Provider will periodically send the o1NotifyCloudNFRegistration event (at vendor specified intervals) until a NETCONF session is established. This indicates that the Cloudified NF Registration MnS Provider has registered, and the Cloudified NF Registration MnS Consumer can begin managing the Cloudified NF Registration MnS Provider and bring the Cloudified NF Registration MnS Provider to an operational state. NOTE: The o1NotifyCloudNFRegistration notification does not require a subscription. It is sent after the application comes up if a Cloudified NF Registration MnS Consumer address (e.g. IP@ or FQDN) is obtained during instantiation or is pre-provisioned. The o1NotifyCloudNFRegistration notification is also sent after a restart for the VNF/CNF. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.10.1.2 Requirements | REQ-CNFR-FUN-1: The Cloudified NF Registration MnS Provider shall support the capability to send a o1NotifyCloudNFRegistration notification to the Cloudified NF Registration MnS Consumer when it has completed instantiation and application initialization and is ready for final configuration and to be managed by the Cloudified NF Registration MnS Consumer. REQ-CNFR-FUN-2: The Cloudified NF Registration MnS Provider shall support the capability to send a o1NotifyCloudNFRegistration notification to the Cloudified NF Registration MnS Consumer when it completes a restart. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 63 |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.10.1.3 Procedures | The Cloudified NF Registration MnS Provider sends an asynchronous HTTP/TLS o1NotifyCloudNFRegistration notification to the Cloudified NF Registration MnS Consumer after it has been instantiated via the O2 interface, completed application initialization and is ready for final configuration and to be managed (put into service). @startuml Title Cloudified NF Registration participant "Cloudified NF Registration MnS Consumer" as NMS participant "Cloudified NF Registration MnS Provider" as ME Note over ME : NF has completed instantiation and application initialization and is ready to be managed ME ->> NMS : 1 <<HTTP/TLS>> o1NotifyCloudNFRegistration Notification @enduml Figure 6.10.1.3-1: Cloudified NF Registration Procedure Pre-condition: - NF has been instantiated via the O2. - Cloudified NF Registration MnS Consumer address is obtained during instantiation or is pre-provisioned. - Cloudified NF Registration MnS Provider has completed application initialization and is ready to be managed. Procedure: 1) Cloudified NF Registration MnS Provider sends o1NotifyCloudNFRegistration notification to Cloudified NF Registration MnS Consumer over HTTP/TLS. Mutual certificate authentication is performed. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.10.1.4 Operations and Notifications | A Cloudified NF Registration notification shall be in one of the following formats: - SDO O1 format: - An O-RAN-specified o1NotifyCloudNFRegistration notification as will be specified in the O-RAN Information Model and Data Models Specification [i.14]. - VES O1 format: - A Harmonized VES event, as specified in the VES Event Listener Specification [18], containing stndDefinedFields with a "data" element that contains an O-RAN-specified o1NotifyCloudNFRegistration notification. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 64 Annex A (informative): O-RAN Performance Measurement Definition Example A.1 ETSI TS 132 404 PM Template Usage in O-RAN A.1.0 Overview Examples are presented below to illustrate how to use the ETSI TS 132 404 [10], clause 3.3 template or template required information to specify O-RAN defined O1 compliant performance measurements. The O-RAN defined O1 compliant performance measurement will be defined using this template and documented in the appropriate O1 Interface Specification, e.g. O1 Interface Specification for Near-RT RIC [i.10], O1 Interface Specification for O-CU-UP and O-CU-CP [i.11] and O1 Interface Specification for O-DU [i.12]. NOTE: This PM template applies to O1 complaint nodes, specifically Near-RT RIC, O-CU-CP, O-CU-UP and O- DU. The MF-specific O1 Interface Specifications will contain a template similar to clause A.1.1.1 for each counter defined and that these tables will be part of the official documentation. There are three scenarios when O-RAN defines its own measurement or extends other SDO, for example, 3GPP specified measurement: 1) O-RAN defines a new measurement: a) Measurement Name follows the guidance of ETSI TS 132 404 [10], clause 3.3, is descriptive and begins with "OR". For example, "OR O-DU counter UL…". b) Measurement Type follows the guidance of ETSI TS 132 404 [10], clause 3.3 and in addition has "OR." prefix. For example, in format of OR.RLC.xxxx. 2) O-RAN extends the definition of an existing 3GPP measurement which does not have subcounter defined: a) A new O-RAN measurement needs to be defined. b) For example, A.1.3 Example 3 O-RAN extends 3GPP measurement "UL Total PRB Usage" is given. 3) O-RAN defines new subcounters to an existing 3GPP measurement which has subcounters defined: a) A new O-RAN measurement needs to be defined. b) Existing filters (or called additional items in ETSI TS 132 404 [10], clause 3.3) for a 3GPP measurement that the new O-RAN measurement is based on, can be re-defined in the new O-RAN measurement's Measurement Type. This enables supporting of combination of existing filters and the new filter. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 65 A.1.1 Example 1 O-DU counter UL PDCP PDUs transmitted via F1-U UL GTP-U tunnel A.1.1.1 PM Template Measurement Name OR UL PDCP PDUs transmitted via F1-U Description This counter provides the number of the UL PDCP PDUs transmitted via F1-U UL GTP-U tunnel It is optional counter for O-DU Collection Method CC (Cumulative Counter) Condition Measurement subcounter is incremented by 1 whenever the UL PDCP PDU is transmitted via F1 U UL GTP-u tunnel when the QCI of the UL PDCP PDU is group of subcounter.Pmgroup Measurement Result Integer number (U32) Measurement Type OR.F1.UlPdcpPduTxF1UUl.Pmgroup where PmGroup is PmCountGroup number: 0: #0 1: #1 … 19: #19 Measurement Object Class gNBDUFunction Switching Technology Packet Switched Generation 5GS Purpose Network Operator's Traffic Engineering Community A.1.2 Example 2 O-DU counter Received UL RLC PDU volume A.1.2.1 PM Template Measurement Name OR received UL RLC PDU Vol Description This counter provides the received UL RLC PDU volume It is recommended to support for O-DU Collection Method SI (Status Inspection) Condition Measurement subcounter is incremented by the volume of the UL RLC PDU whenever the UL RLC PDU is received when the QCI of the UL RLC PDU is group of subcounter.Pmgroup Measurement Result kilobyte (U32) Measurement Type OR.RLC.RxUlRlcPduVol.Pmgroup where Pmgroup is PmCountGroup number: 0: #0 1: #1 … 19: #19 Measurement Object Class gNBDUFuncton Switching Technology Packet Switched Generation 5GS Purpose Network Operator's Traffic Engineering Community ETSI ETSI TS 104 043 V11.0.0 (2024-06) 66 A.1.3 Example 3 O-RAN extends 3GPP measurement "UL Total PRB Usage" A.1.3.1 PM Template alternative 1 Measurement Name OR UL Total PRB Usage Description (a) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.a Collection Method (b) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.b Condition (c) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.c Measurement Result (d) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.d Additionally, the measurement is performed per PLMN ID Measurement Type (e) The short form measurement name has the form OR.RRU.PrbTotUl _Filter, Where filter is PLMN ID Measurement Object Class (f) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.f Switching Technology (g) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.g Generation (h) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.h Purpose (i) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.i. Additional for each PLMN ID A.1.3.2 PM Template alternative 2 x.y.z OR UL Total PRB Usage a) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.a b) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.b c) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.c d) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.d Additionally, the measurement is performed per PLMN ID e) The short form measurement name has the form OR.RRU.PrbTotUl _filter Where filter is PLMN ID f) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.f g) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.g h) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.h i) Refer to 3GPP TS 28.552 [i.5] clause 5.1.1.2.i. Additionally for each PLMN ID ETSI ETSI TS 104 043 V11.0.0 (2024-06) 67 Annex B (informative): Guidelines and Example for stndDefined VES Events B.1 Guidelines for use of stndDefined VES for sending 3GPP-specified or O-RAN-specified O1 notifications A stndDefined VES event, as specified in VES Event Listener Specification [18], allows a VES event to carry, as its payload, a notification specified by an SDO. In the case of O-RAN O1 Interface Specification, a harmonized stndDefined VES event carries either a 3GPP-specified O1 notification or an O-RAN-specified O1 notification as its payload. 3GPP has published an informative Annex B in ETSI TS 128 532 [3] providing guidelines for the integration of 3GPP- specified notifications with VES. This annex expands on the information provided by 3GPP, including information on how to include O-RAN-specified O1 notifications in a VES stndDefined event. When an O-RAN and 3GPP compliant ME supports VES stndDefined events for sending asynchronous notifications, a3GPP-specified O1 notification, as defined by 3GPP, or an O-RAN-specified O1 notification, as defined by O-RAN, is included in the event. A VES common event header, as defined by VES Event Listener Specification [18], is added to the notification. In VES, the domain field in the common event header is used to route the event to the proper consumers and to map to a schema for the event payload. VES Event Listener Specification [18] added a new domain field enumeration value called stndDefined that indicates that the event is complying with a schema defined by a standards body. An additional field was added to the VES common event header called stndDefinedNamespace, which contains a valid namespace as defined by the standards body. This field is only populated when the domain is stndDefined. 3GPP has defined four namespaces in ETSI TS 128 532 [3] Annex B; namely 3GPP-Provisioning, 3GPP-Heartbeat, 3GPP- FaultSupervision and 3GPP-PerformanceAssurance. O-RAN has defined a namespace for the notifications it defines. Refer to clause 5.2.2 for details. A VES collector uses the stndDefinedNamespace, along with the stndDefined domain, to route the event to the correct consumer. A stndDefined VES event has a field structure called stndDefinedFields, specified in VES Event Listener Specification [18]. This structure contains three properties: - schemaReference (type = string, format = uri) - data (JSON object which is identical to the 3GPP or O-RAN notification) - stndDefinedFieldsVersion (type = string, format = enum) The schemaReference, if present, is used to verify that the notification content is correct. 3GPP is publishing the notification schemas defined using OpenAPI, to a public repository, (https://forge.3gpp.org/rep/sa5) so that schema references can be included in the event. Likewise, O-RAN will define its notification schemas using OpenAPI and publish them in a public repository. This repository is still to be created. The data element contains either a 3GPP-specified O1 notification, in JSON format, as specified in ETSI TS 128 532 [3] or an O-RAN-specified O1 notification, in JSON format, as specified in O-RAN Information Model and Data Models Specification [i.14]. The stndDefinedFieldsVersion provides the version of the stndDefinedFields structure, as defined by VES Event Listener Specification [18]. Clause B.2 provides an example of a stndDefined VES event for a new alarm notification. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 68 B.2 Example stndDefined VES event for a new alarm notification The following example illustrates the population of a new alarm notification using a stndDefined VES event. The VES Common Header is shown from line 44 through line 58. It contains: - the domain set to stndDefined; - the stndDefinedNamespace set to 3GPP-FaultSupervision. The stndDefinedFields structure begins on line 59. It contains: - the 3GPP schema reference for the 3GPP fault notification type - the data element which contains the full 3GPP notifyNewAlarm fault notification - the version of the stndDefinedFields { "event": { "commonEventHeader": { "domain": "stndDefined", "eventId": "stndDefined-gNB-Nokia-000001", "eventName": "stndDefined-gNB-Nokia", "lastEpochMicrosec": 1594909352208000, "priority": "Normal", "reportingEntityName": "NOKb5309", "sequence": 0, "sourceName": "NOKb5309", "startEpochMicrosec": 1594909352208000, "stndDefinedNamespace": "3GPP-FaultSupervision", "version": "4.1", "timeZoneOffset": "UTC-05.00", "vesEventListenerVersion": "7.2" }, "stndDefinedFields": { "schemaReference":https://forge.3gpp.org/rep/sa5/5G_APIs/blob/REL- 17/(…)/faultNotifications.json#definitions/notifyNewAlarm-NotifType, "data": { "href": 1, "uri": "xyz", "notificationId": "123", "notificationType": "notifyNewAlarm", "eventTime": "xyz", "systemDN": "xyz" "probableCause": "High Temperature", "perceivedSeverity": "Major", "rootCauseIndicator": false, "specificProblem": "7052", "backedUpStatus": true, "backUpObject": "xyz", "trendIndication": "No change", "thresholdInfo": {}, "stateChangeDefinition": {}, "monitoredAttributes": [], "proposedRepairActions": "xyz", "additionalText": "xyz", "additionalInformation": [], "alarmId": "15", "alarmType": "Environmental Alarm" } }, "stndDefinedFieldsVersion": "1.0" } } ETSI ETSI TS 104 043 V11.0.0 (2024-06) 69 Annex C (informative): Streaming Trace Management Activation Example Example with Management-based Trace Activation, Data Reporting and Deactivation for Streaming Trace follows. The sequence below is based on 3GPP specifications which are referred in clause 6.4 of the present document. @startuml skin rose Title Streaming Trace Connection Establishment, Data Reporting and Deactivation autonumber "[0]" participant "Provisioning MnS Consumer" as NMS participant "Trace MnS Provider" as ME participant "Trace MnS Consumer" as TMC NMS --> ME : Trace Job Configuration create traceJob MOI ME --> NMS : notifyMOIChanges Opt (No connection to the Trace Mns Consumer exists) ME -> TMC : establishStreamingConnection (HTTP POST request (SourceID, Trace Session Information)) TMC -> ME : HTTP: response (Connection ID) ME -> TMC : HTTP GET request(Connection ID, Upgrade Header) TMC -> ME : HTTP: response (Sec-WebSocket-Accept) End Opt ME -> TMC: AddStream Operation (HTTP ADD) End ||| ME -> ME: Start Trace Session ME -> TMC: Trace Session Start administrative message loop (while trace session is active) Opt (trace stream heartbeat) ME -> ME: Hearbeat sending criteria are met Note right The criteria for sending heartbeat administrative messages are implementation specific End note ME -> TMC: Trace Stream Heartbeat administrative message End loop (Trace recording session handling) ME -> ME: "start" triggering event detected ME -> ME: Start Trace Recording Session and allocate new TRS (embedded in a reportStreamData Operation) ME -> TMC : Trace Recording Session Start administrative message loop (until "stop" triggering event is detected) loop (until reporting condition is satisfied) ME -> ME: Capture trace record End ME -> TMC: "reportStreamData(traceRecords)" End ME -> ME: Recording session complete/stop criteria are met ME -> ME: Stop trace recording session ME -> TMC: Trace Recording Session Stop administrative message End End NMS --> ME: Trace Session Deactivation/Configuration ME -> ME: Stop Trace Session loop (for each on-going Trace Recording Session) ME -> ME : Stop Trace Recording Session Opt (there are outstanding trace records) ME -> TMC: "reportStreamData(traceRecords)" End ME -> TMC: Trace Recording Session Stop administrative message ETSI ETSI TS 104 043 V11.0.0 (2024-06) 70 End ME -> TMC: Trace Session Stop administrative message Opt (multiple streams exist) ME -> TMC: deleteStream Operation (HTTP DELETE) End Opt ME -> TMC: terminateStreamingConnection(WebSocket Close Frame) ME <<->> TMC: Terminate Connection End @enduml ETSI ETSI TS 104 043 V11.0.0 (2024-06) 71 Figure C-1: Streaming Trace Connection Establishment, Data Reporting and Deactivation Example Scenario: - Provisioning Management Service Consumer activates/configures Trace Session on Trace Provider. This will be accomplished using Provisioning Management services described in clause 6.1 of the present document. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 72 - Trace Provider sends a notifyMOIChanges to indicate the new MOI is created. Steps 3-6 are optional when no connection to trace MnS consumer exist. - Trace Provider needs to establish a connection to the Trace Consumer to set up a streaming connection (streams are active at this time between the Provider and Consumer). This is done using the establishStreamingConnection Operation via an HTTP POST request containing MetaData associated with this Trace Session. - Trace Consumer responds with an acknowledgement that contains the ConnectionID needed by the Provider when requesting that the connection be upgraded to a WebSocket to support streaming of the trace data. - Trace Provider requests the upgrade of the connection to a WebSocket using the ConnectionID and an HTTP GET operation. - Trace Consumer accepts the upgrade and WebSocket is established. WebSocket will remain connected until the last streaming trace session active on the Trace Provider is ended. NOTE: In this example, only one streaming trace session is active. - Optionally addStream operation is used to add a stream to the trace connection. - Trace Provider starts trace session, waiting for triggering event to occur. - Trace Provider sends trace session start administrative message to Trace MnS Consumer. - Heartbeat sending criteria are met. The criteria about when to send Trace stream heartbeat administrative message are implementation specific. - Trace stream heartbeat administrative message is sent to Trace consumer repeatedly. Trace stream heartbeat administrative message is used for monitoring whether the trace session connection is alive and can be executed parallel to other loops. - "start" triggering event detected. - A new trace recording session is started on the Trace Provider. Each trace recording session has a unique Trace Recording Session (TRS) Reference associated with it. - Trace recording session start administrative message is sent from Trace MnS Provider to Trace MnS Consumer. - While this trace record is active, and the reporting criteria are not fulfilled, the Trace MnS Provider collects trace data. - When the reporting criteria are fulfilled, either timer expires or the buffer fills, or the buffer has data and the "stop" triggering event is detected, the Trace Provider sends a trace data report to the Trace Consumer containing trace record data for active recording sessions in a trace session. These records are the payload of the reportStreamData operation. - The criteria for the trace recording session completion or stop occurs (call ends, etc.). - The Trace Provider stops collecting data for this trace recording session. - Trace Provider sends trace recording session stop administrative message to Trace MnS Consumer. - Provisioning Management Service Consumer deactivates the trace via procedures defined in clause 6.1 of the present document. Deactivation means that the trace data collection ceases, and the Trace Provider stops all active trace recording sessions and sends data that it has collected up to this point, if any, for each active trace recording to the Trace Consumer. - Trace Provider initiates the termination of the trace session. - For each active trace recording session, Trace Provider initiates a Stop Trace Recording Session. - Optionally if there are outstanding record(s) for this trace recording session that have not been streamed to the Trace Consumer, Trace Provider sends them as the payload of the reportStreamData operation. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 73 - Trace Provider informs the Trace Consumer that this Trace Recording Session has ended by sending the trace record termination administrative message. The producer repeats this until all trace recording sessions for this trace session have been terminated. - Trace MnS Provider sends the trace session stop administrative message to Trace MnS Consumer. - Optionally the Trace Provider sends the Trace Consumer the deleteStream operation indicating that the stream has been removed in case the connection is used for multiple streams. - Optionally when all active Trace Sessions between Trace Provider and Trace Consumer have ended, the WebSocket connection is to be torn down. Trace MnS Provider sends the Trace MnS Consumer the terminateSignalingConnection Operation which is a WebSocket close frame. - Terminate connection. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 74 Annex D (normative): Recommendation for UE Identifier Format in Trace Header Specification 3GPP TS 32.423 [13], clause 5.2.2 defines vendorExtension IE in Trace Header as an Arraylist of String. The Trace Record Header should be encoded using GPB in Annex G of 3GPP TS 32.423 [13]. Based on Annex G, Trace Record Header in GPB is defined as: message TraceRecordHeader { int64 time_stamp = 1; string nf_instance_id = 2; string nf_type = 3; bytes trace_reference = 4; bytes trace_recording_session_ref = 5; TraceRecordType trace_rec_type_id = 6; bytes ran_ue_id = 7; string payload_schema_uri = 8; GlobalGnbId global_gnb_id = 9; map<string, string> vendor_extension = 10; } Several UE identifiers and node identifiers are identified as necessary for trace record correlation. Refer to O-RAN architecture description [15], clause 5.5 for detailed information. To enable trace record correlation, a new map entry is defined for vendor_extension to be used to send O-RAN UE/Node identifiers. Defined TraceRecordHeader field vendor-extension is in following format: map<string, string> vendor_extension = 10; The map entry should be added for UE identifier and node identifiers is as below: First string in the map entry: value = "oranUENodeIdentifiers" Second string in the map entry: value = result of "print string" of message OranUEAndNodeIdentifiers NOTE: The O-RAN defined map entry for O-RAN UE/Node identifiers "oranUENodeIdentifiers" can co-exist with other vendor defined vendor-extension map entries. O-RAN defined map entry "oranUENodeIdentifiers" can be add in any position in the vendor_extension map. message OranUEAndNodeIdentifiers { optional OranConnectedEntity connected_entity_id =1; optional OranUEId originator_ue_id = 2; optional OranUEId connected_entity_ue_id =3; } Message OranUEId{ optional int64 amf_ue_ngap-id = 1; optional int64 ran_ue_ngap_id =2; optional int64 mme_ue_s1ap_id = 3; optional int64 gnb_cu_ue_f1ap_id = 4; optional int64 gnb_cu_cp_ue_e1ap_id = 5; optional int64 gnb_cu_up_ue_e1ap_id= 6; optional int64 traced_ng_ran_node_ue_xnap_id = 7; optional int64 connected_ng_ran_node_ue_xnap_id = 8; optional int64 m_enb_ue_x2ap_id = 9; optional int64 c_rnti = 10; } Message OranConnectedEntity { oneof connected_entity_id { bytes ng_connected_guami = 1; // AMF ID of the connected AMF Guami ng_connected_guami_decoded = 2; // AMF ID of the connected AMF GlobalGnbId xn_connected_global_gnb_id = 3; // ID of neighbouring gNB-CU-CP OranGlobalEnbId xn_connected_global_enb_id = 4; // ID of neighbouring ng-eNB node OranGlobalEnbId x2_connected_global_enb_id = 5; // ID of connected NSA eNB node bytes s1_connected_mme= 6; // ID of connected MME Gummei s1_connected_mme_decoded= 7; // ID of connected MME int64 f1_connected_du_id = 8; // ID of connected gNB-DU int64 e1_connected_cuup_id = 9; // ID of connected gNB-CU-UP } ETSI ETSI TS 104 043 V11.0.0 (2024-06) 75 } message GlobalEnbId { bytes plmn_identity = 1; int64 enb_id = 2; } Message Guami { bytes plmn_identity =1; string amf_region_id=2; string amf_set_id=3; string amf_pointer=4; } Message Gummei { bytes plmn_identity =1; string mme_grp_id=2; string mme_code=3; } Based on the value nf_type (for example, gNB-CU-CP, gNB-CU-UP, gNB-DU) in the TraceRecordHeader, different types of UE identifiers and node identifier can be reported. For detail, refer to O-RAN architecture description [15], clause 5.5. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 76 Annex E (informative): Change history Date Revision Description 2019.03.18 0.01.00.00 First draft of O-RAN OAM Interface Specification. 2019.03.28 0.01.01.00 Updates from review remarks received. 2019.05.21 0.01.01.01 Fault Supervision, Performance Assurance and File Management updates. 2019.05.28 0.01.01.02 References, Abbreviations, Definitions, Provisioning, Communication Surveillance, PNF Start Up and Registration updates. 2019.06.13 0.01.01.03 Diagrams for File Management converted to UML, Performance Assurance UML, PNF Software Management Updates. 2019.06.17 0.01.01.04 Provisioning Updates. 2019.07.01 01.00 Review Comments Addressed TSC approved copy. 2019.09.27 02.00 Updates for late review comments, additional CM notifications, NETCONF requirements and updated references to 3GPP SA5 Rel-16. 2020.03.03 03.00 Update Heartbeat Management Service. New clauses for Subscription Control, Streaming PM, O-RAN Defined PM Measurements and an Annex showing examples for using the specified template for O-RAN defined PM Measurements. 2020.08.18 04.00 Update Introductory Material, Provisioning, Fault Supervision, Performance Assurance, Trace Management, and Heartbeat Management to incorporate 3GPP Rel 16 CRs. Add Annex B for stndDefined event example and Annex C for Streaming Trace example. 2020.08.31 04.00 Update document with comments from WG1 review. 2021.03.11 04.01 Incorporate approved CRs to prepare for v05.00. Update Provisioning with approved CR 10. Update Fault Supervision with approved CR 11. 2021.04.27 04.02 Update Software Download with approved CR 13. 2021.05.24 04.03 Incorporate approved Updates and Corrections CR 14. Updates to References, Security Protocols and Trace. 2021.06.21 04.04 Incorporate approved YANG Module Discovery CR 15. 2021.06.22 05.00 O1v5 incorporating CRs from 04.01.00 through 04.04.00. 2021.10.25 06.00 Incorporate approved CRs: PNF Reset CR 16, Performance Management CR 17, Cloudified NF Registration CR 18, Notify Alarm List Rebuilt CR 19, O1 Notifications CR 20 and References Updates CR 21. 2022.03.15 07.00 Incorporate approved CRs: PM Streaming Format Correction CR 22, 3GPP specified Notification VES format support CR 23, Annex C Streaming Trace Management CR 24, PNF Registration Notification CR 25, Rearrange PNF Reset Notification Requirements CR 26, Clarify counter naming requirement CR 27 and Notification capability CR 28. 2022.07.18 08.00 Incorporate approved CRs: O-RAN counter name clarification CR 29, File management update CR 30, O1 Notification CR 31, Plug and Connect uplift CR 32, UE Identifiers for Trace header CR 33 and CM Notifications uplift CR 34. Editorial changes related to the copyright clarification. 2022.08.31 08.00.01 Incorporate approved CR 36 resolving outdated 3GPP references. 2022.11.01 09.00.00 Incorporate approved CRs: Alignment with 3GPP and editorial modifications CR37, PM file format for NR measurements CR38. Editorial changes related to the new document naming format. Editorial changes related to application of embedded O-RAN styles template. 2022.11.21 09.00.01 Editorial CR39 introduced changes for alignment with ODR, O-RAN TS Template and ETSI PAS - re-arranged and re-numbered clauses. Removal of author information from the history table. 2023.01.31 09.00.02 Incorporate approved CRs: UE Identifier schema CR40, Measurement job control clarification CR41 and File management correction CR42. 2023.03.06 10.00 Incorporate approved CRs: Clean-up of 3GPP TS 28.532 reference CR43, Correction of 3GPP TS 28.533 reference CR44, O-RU change in O1 introduction CR45, Split of normative and informative references CR46, Clean-up references CR47, Clean-up of introduction CR48, Remove out of scope Fault Notification requirements CR49 and Clean-up Fault Supervision Control Requirements CR50. 2023.07.11 11.00 Incorporate approved CRs: Reference update to O-RAN internal specifications CR33, Normative language clean-up CR52. 2024.06 11.0.0 First published ETSI/O-RAN version. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 77 History Document history V11.0.0 June 2024 Publication |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 1 Scope | The present document details measures which may be taken to improve the energy efficiency of access networks for broadband deployment. The present document: • identifies the standardization bodies working on diverse aspects of the access networks infrastructures interfaces, cabling, installation, operation, etc.; • outlines some of the principal access network topographies and their differences in respect of energy consumption; • provides strategic analysis of energy consumption trends within access networks. This enables the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of the present document to provide detailed standardized solutions for network architecture. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 2 References | |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-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 reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://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. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-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 reference 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] "EC Code of Conduct on Energy Consumption of Broadband Equipment" V5. [i.2] Recommendation ITU-T G.984.1 (03/2008): "Gigabit-capable passive optical networks (GPON): General characteristics". [i.3] Recommendation ITU-T G.984.2 (03/2008): "Gigabit-capable passive optical networks (GPON): Physical Media Dependent (PMD) layer specification". [i.4] Recommendation ITU-T G.984.3 (04/2012): "Gigabit-capable passive optical networks (GPON): Transmission convergence layer specification". [i.5] Recommendation ITU-T G.984.5 (10/2009): "Enhancement band for gigabit capable optical access networks". [i.6] Recommendation ITU-T G.984.6 (05/2012): "Gigabit-capable passive optical networks (GPON): Reach extension". ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 7 [i.7] Recommendation ITU-T G.992.1 (03/2003): "Asymmetric digital subscriber line (ADSL) transceivers - Annex A: Specific requirements for an ADSL system operating in the frequency band above POTS". [i.8] Recommendation ITU-T G.992.3 (06/2008): "Asymmetric digital subscriber line transceivers 2 (ADSL2) - Annex J: All digital mode ADSL with improved spectral compatibility with ADSL over ISDN". [i.9] Recommendation ITU-T G.992.5 (01/2009): "Asymmetric digital subscriber line (ADSL) transceivers - Extended bandwidth ADSL2 (ADSL2plus)". [i.10] ETSI TS 105 174-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 1: Overview, common and generic aspects". [i.11] Recommendation ITU-T G.987.1 (04/2012): "10 Gigabit-capable passive optical networks (XG-PON): General requirements". [i.12] Recommendation ITU-T G.987.2 (02/2012): "10-Gigabit-capable passive optical networks (XG-PON): Physical media dependent (PMD) layer specification". [i.13] Recommendation ITU-T G.987.3 (06/2012): "10-Gigabit-capable passive optical networks (XG-PON): Transmission convergence (TC) layer specification". [i.14] Recommendation ITU-T G.987.4 (06/2012): "10-Gigabit-capable passive optical networks (XG-PON): Reach Extension". [i.15] Recommendation ITU-T G.989.1 (03/2013): "40-Gigabit-capable passive optical networks (NG-PON2): General requirements". [i.16] Recommendation ITU-T G.985 (01/2009): "100 Mbit/s point-to-point Ethernet based optical access system". [i.17] Recommendation ITU-T G.986 (01/2009): "1 Gbit/s point-to-point Ethernet-based optical access system". [i.18] ETSI GS OEU 012: "Operational energy Efficiency for Users (OEU); Technical Global KPIs for Fixed Access Networks". [i.19] ETSI EN 300 132 series: "Environmental Engineering (EE); Power supply interface at the input to telecommunications and datacom (ICT) equipment". [i.20] ETSI EN 300 132-3-1: "Environmental Engineering (EE); Power supply interface at the input to telecommunications and datacom (ICT) equipment; Part 3: Operated by rectified current source, alternating current source or direct current source up to 400 V; Sub-part 1: Direct current source up to 400 V". [i.21] ETSI TS 105 174-2: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management Part 2: ICT sites". [i.22] IEEE 802.3-2012 - "IEEE Standard for Ethernet". [i.23] IEEE 802.11-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". [i.24] ETSI ES 205 200-3: "Access, Terminals, Transmission and Multiplexing (ATTM); Energy management; Global KPIs; Operational infrastructures; Part 3: Global KPIs of ICT Sites". ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 8 |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 3 Definitions, symbols and abbreviations | |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: access circuit: telecommunications circuit connecting the operator site to the subscriber's premises access network: part of the network that is deemed to include the last active component at the relevant operator site and the first active element at the subscriber's premises access point: termination point on a telecommunications network allowing access by nomadic devices to obtain telecommunications services to which they have subscribed elsewhere active element: network component that requires externally supplied electric power to enable it to perform its network function community network: communications network, usually wireless, established by and for a local community often to compensate for lack of publicly available access to relevant facilities customer: person or entity using a telecommunications service and who may or may not be the subscriber Digital Access Carrier System (DACS): 0+2 pair gain system providing two separate telephone lines over one copper pair using digital technology Digital Subscribers Line (xDSL): access circuit over which information is carried in a digital format and where the upstream and downstream transmission rates may be the symmetrical (SDSL) or asymmetrical (ADSL) energy consumption: measure of the energy consumed by the operation of the electronic devices necessary to provide a specific communications service enterprise network: network established by a large company or similar enterprise to serve its internal telecommunications needs with connectivity to one or more public networks Ethernet: frame-based local area networking technology standardized as IEEE 802.3 [i.22] fibre to the cabinet: optical fibre distribution network providing connectivity from the network operator's site to a shared distribution node close to the end-user's premises firewall: security measure designed to prevent unauthorized electronic access to a networked computer system flexibility point: device in the access network where access circuits can be configured to their intended destination by cross connecting metallic pairs home network: network that supports and distributes within the home, those services to which a customer subscribes intrusion detection system: mechanism by which any attempt by an unauthorized user or terminal to gain access to a communications network is detected meshed network: communications network, usually wireless, in which every node has connectivity with a number of other nodes thus enabling a variety of possible communication paths between nodes network gateway: device which will enable the interconnecting of two networks which inherently use different and incompatible protocols packet: information block identified by a label at layer 3 of the OSI reference model peripheral: peripheral is a device attached to a host computer whose primary functionality is dependent upon the host, and which expands the host's capabilities, but is not part of the core architecture of the system point-to-multi-point: communications link operating between a network operator's site and a number of other locations point-to-point: communications link operating between two, usually fixed, locations service: provision of a defined functionality in a computer systems or telecommunications environment ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 9 sub-loop: secondary access circuit from a street cabinet or similar access node used to deliver one or more services to a customer subscriber: person or entity responsible for paying for a telecommunications service Subscribers Loop Carrier (SLC): equipment providing multiple telephone circuits over one or two standard subscriber's telephone lines (see also DACS) triple play (telecommunications): provision of cable TV, telephony and broadband data as a combined service offering, possibly using a single bearer medium Watt (W): unit of power, the rate at which work is done; in electrical terms it is the product of the supply voltage (volts) and the current passed (amps) Watt-hour (Wh): unit of energy used or work done; the product of the rate at which work is done and the time for which it done NOTE: The terms "Watt" and "Watt-hour" are frequently confused. WiFi: technology defined by the IEEE 802.11 standards [i.23] |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: DCG Data Centre Gauge DCP Data Centre Performance ECDC Total of energy consumptions by a data centre over a year ECFEN Consumption of locally generated electricity based on fossil energy ECHE Total of energy consumptions by equipment processing data, for purposes of calculating, storing or transporting, over a year ECREN Consumption of locally generated electricity based on renewable sources ECREUSE Total of energy consumption from reused energy EER Energy Efficiency Ratio expressed as thermal kWh extracted by one electrical kWh KPIDCEM Global KPI for data centre energy management KPIEC Objective KPI for "Energy Consumption" KPIREN Objective KPI for "Renewable Energy" KPIREUSE Objective KPI for "Energy Reuse" KPITE Objective KPI for "Task Efficiency" WREN Mitigation factor for KPIREN WREUSE Mitigation factor for KPIREUSE |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AC Alternative Current ADSL Asymmetrical Digital Subscribers Line NOTE: See Recommendation ITU-T G.992.1 [i.7]. ADSL2 Second generation ADSL with extended upstream bandwidth NOTE: See Recommendation ITU-T G.992.3 [i.8]. ADSL2+ Second generation ADSL with extended downstream bandwidth NOTE: See Recommendation ITU-T G.992.5 [i.9]. BEF Building Entrance Facility CATV Cable Television ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 10 CGIC Co-ordination Group on Installations and Cabling CO Central Office CPE Customer Premises Equipment DACS Digital Access Carrier System NOTE: See also SLC. DC Data Centre DCEM Dataprocessing and Communication Energy Management DPU Distribution Point unit NOTE: ONU for FTTdp architectures. DSL Digital Subscriber Line EC European Commission EE Environmental Engineering EMC Electro Magnetic Compatibility ENTI External Network Test Interface FAN Fixed Access Node FDM Frequency Division Multiplex FTTB Fibre To The Building FTTC Fibre To The Curb FTTCab Fibre To The Cabinet FTTdp Fibre To The distribution point FTTD Fibre To The Door FTTH Fibre To The Home GPON Gigabit Passive Optical Network HD Home Distribution HEF Home Entrance Facility HFC Hybrid Fibre Coaxial ICT Information and Communications Technology IEEE Institution of Electrical and Electronics Engineers (USA) ISDN Integrated Services Digital Network ISG Industry Specification Group ITU International Telecommunications Union ITU-T ITU's Telecommunication standardization sector KPI Key Performance Indicator KPIEC Key Performance Indicator Energy Consumption KPIECG Key Performance Indicator total consumption of energy by the Group LT Line Termination NGN Next Generation Network NTP Network Termination Point OIE Operator Independent Equipment OLT Optical Line Terminal ONT Optical Network Termination for single user residential users (FTTH) ONU Optical Network Unit for collective or in case of secondary transmission (e.g.: DSL) OSE Operator Specific Equipment PON Passive Optical Network POTS Plain Old Telephone Service PUE Power Usage Effectiveness RPF Reverse Power Feeding SDSL Symmetric Digital Subscriber Line SLC Subscribers Line Carrier (system) NOTE: See also DACS. TDM Time Division Multiplex UPS Uninterruptible Power Supply VAC Voltage in an Alternating Current VDC Voltage in a Direct Current VDSL Very high-speed Digital Subscriber Line VHBB Very High BroadBand W Watt ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 11 WDM Wavelength Division Multiplex Wh Watt hour xDSL Digital Subscriber Line (generic title) XG-PON 10 Gigabit Passive Optical Network |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4 Overview of access network solutions | |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4.1 Customer access point | For the purposes of the present document, the access network is deemed to include the last active component at the relevant operator site and the first active element at the subscriber's premises. The connection between the operator's access network and the home distributor as shown in figure 1 (or the equivalent in non-generic cabling) is provided by network access cabling and some type of network telecommunication equipment. Figure 1: Network access cabling and equipment The access network normally includes a Network Termination Point (NTP) at the customer's premises. In the case of a broadband connection this typically comprises a passive interface (ENTI) and an optional item of apparatus. The apparatus may either be specific to the network operator (OSE) such as CATV modems or FTTH modems. Some OSE may have functionality beyond that which is strictly necessary to provide adequate service termination. For example, a DSL or cable modem may have an inbuilt router or WiFi terminal. When determining the energy efficiency in these cases, it has to be determined how to identify what proportion of the total power requirement of the device should be taken into account for the purposes of the calculation. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4.2 Principal access technologies | |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4.2.1 Introduction | Clause 4.2 examines the principal access network topologies used for the delivery of NGN services and describes them in sufficient detail to define their typical power requirements. It should be appreciated that each of the topographies to be described has a number of variants. 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-4-1 V1.2.1 (2015-09) 12 |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4.2.2 Metallic Loop | The traditional access network or local distribution network has comprised a copper based network with each subscriber or in some cases, each service, having a dedicated copper twisted pair from the operator site ("telephone exchange") to the customer's premises. Such connections are normally made via a number of "flexibility points" in the copper plant allowing the pairs to be routed appropriately; discussion of this is outside the scope of the present document. Some networks incorporate conductors made from other metals (typically aluminium or bronze) but these are very much in the minority as pair gains systems or regenerating technologies are and as such will not be further discussed. This passive plant was originally conceived for voice telephony and has remained virtually unchanged apart from improvements having been made in its physical construction and the materials used. The network is essentially passive, power normally being required only to feed the customer POTS terminal. Its application has been extended to include multiple channel telephony (for example, ISDN2 and DACS based services); although these are not seen as major revenue making services, they are expected to exist for a considerable time, thus necessitating the continued existence of the metallic network. These networks have been and are expected to continue to be used for broadband services using xDSL in support of the NGN. These have typically operated up to approximately 8 Mbit/s using older DSL technology, this being principally dependent upon the line length, but up to a few tens of Mbit/s using ADSL2+ and VDSL2, though only relatively short subscriber lines can support the enhanced download speeds recommended by ITU-T as the equipment capability, thus limiting the overall gain of the more advanced DSL technologies. Lines carrying xDSL services usually serve a single terminal or a small home or enterprise network for a single subscriber. G.Fast technologies are now developed in ITU-T to reach up to 1 000 Mbit/s over short distances on existing twisted pairs. For such technology, hybrid architecture combining optical and copper at the distribution point (aka FTTdp) is considered. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4.2.3 Other metallic-based solutions | There are several variants of the copper based local access network, some based on similar copper and others on coaxial cable. These are mostly suited to short access circuits and are more frequently used in customer networks especially by cable operating companies. Coaxial copper cables are sometimes being used in the access network for circuits serving business premises requiring substantial communications capacity and/or a resilient network connection. Such connections have typically carried multi-channel TDM or FDM systems or Ethernet-based services and were usually arranged on a "point-to-point" basis, duplicated when resilience was required. Such metallic solutions are now considered as drop technologies in hybrid architectures (aka FTTdp) to play a part in NGN access networks, either with twisted pairs or coaxial cables. For example, coaxial cables are frequently used for this application in CATV networks using a variety of Hybrid Fibre Coaxial (HFC) architectures. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4.2.4 Optical Fibre | |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4.2.4.1 General discussion | Optical fibre is undoubtedly the medium of choice for NGN broadband transmission. It is inherently stable with no EMC sensitivity and has a very wide transmission bandwidth with low signal loss. Hence it is capable of carrying prodigious amounts of data over long distances without intermediate active (power consuming) equipment. It is essentially a transparent conduit for information flow and can support a wide range of protocols, dependent only on the connected terminal equipment. Optical fibres may be employed in pairs (go and return) with each optical fibre also being capable of illumination at a number of discrete wavelengths or frequencies ("colours") using Wavelength Division Multiplexing (WDM). Alternatively, a single optical fibre may be used, with different go and return wavelengths (called Diplex or WDM), though this may limit the total bandwidth carried on that optical fibre. Each wavelength can carry different traffic types independently of the others within some global restrictions. Each wavelength can also carry numerous independent communications channels multiplexed together in one of a number of different ways, currently dominated by TDM/TDMA. ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 13 Optical fibre systems can both be deployed in point-to-point as outlined in Recommendations ITU-T G.985 [i.16] and G.986 [i.17] or point-to-multi-point configurations. The former provides a dedicated fibre connection between each port of the access network operator's site system and a single location, a single living unit, a building, at curb sites, distribution points or street cabinet. A point-to-multi-point configuration provides connectivity between each port of the access network operator's site system and a number of living units, at building sites, curb sites, distribution points or street cabinets, using achromatic passive optical splitting techniques or wavelength dependant ones to separate the relevant traffic for each of the terminations. A Passive Optical Network (PON) is a point-to-multi-point architecture in which passive (unpowered) optical splitters are used to enable a single optical fibre to serve multiple premises. A PON consists of an Optical Line Terminal (OLT) at the operator site and a number of Optical Network Units (ONUs) near or within customer premises. A PON configuration greatly reduces the amount of optical fibre and active ports in the operator site equipment, thus the power consumption, compared with point-to-point architectures. Systems using WDM and capable of carrying 2,5 Gbit/s and up to 40 Gbit/s are described in Recommendations ITU-T: G-PON in Recommendation ITU-T G.984 series [i.2], [i.3], [i.4], [i.5] and [i.6] XG-PON1 in Recommendation ITU-T G.987 series [i.11], [i.12], [i.13] and [i.14] and NG-PON2 in Recommendation ITU-T G.989 series [i.15], respectively. From the energy prospective the variants to be investigated are differentiated by the number of users accommodated, the ONU location in the network and its powering scheme. Hence gross differentiation is given in table 1. Table 1: VHBB Technologies Technologies Number of users Indoor/Outdoor User/operator powered FTTCab Hundreds Indoor In remote CO Operator FTTC Tens Outdoor Operator FTTB Tens Indoor Operator FTTdp Up to 24 Indoor/Outdoor End users reverse or remote powered FTTD One Indoor/Outdoor End user reverse FTTH One Indoor End user FTT Wireless/Antenna One termination outdoor Operator |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4.2.4.2 Fibre To The Cabinet (FTTCab) | The bandwidth available from optical fibre transmission systems makes them ideal as a shared medium to carry the traffic of a very large number of customers between the operator's site and the customer premises. As a shared medium, it becomes necessary to separate those traffic streams for delivery to their respective customers without being dependent on any one subscriber's facilities (accommodation, power, etc.), in accommodation provided by the access network operator. This usually takes the form of an equipment cabinet located in the street and maintained by the network operator (described as the last cabinet in figures 2a and 2b) which marks the boundary between the transport and distribution parts of the access network. The distribution of the individual customer services comprises secondary transmission systems or sub-loops. ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 14 Fibre To The Cabinet (FTTCab) systems may be connected on a point-to-point basis between the operator site and the street cabinet adjacent to customers' premises but in view of the capacity of such systems customers sometimes require a more resilient solution, if only to protect their traffic against mechanical disruption. Thus, one or more additional optical fibre connections may be necessary between the operator site and each street cabinet using a different cable routing. More commonly, several street cabinets may be connected to a ring infrastructure operated via protected point to point systems over which traffic can be carried in either direction to and from the operator site. Other resilient solutions may also be implemented depending on the access network operator's policies and the customers' requirements. Such resilient solutions always have a greater total energy requirement than a simple point-to-point configuration but this is easily justified on grounds of the need for high levels of system integrity. New systems are expected to appear in which the optical fibres may be illuminated at a number of different wavelengths using WDM, each providing an independent transmission path. Each wavelength requires some additional launched optical power at the operator's site since filtering is required. This is normally a passive process requiring no power source and the separated wavelengths can be extended via separate fibres to their respective destination without the necessity for power. WDM therefore has the potential to vastly increase the bandwidth available in the distribution network, with a relatively modest increase in the energy consumption, thus resulting in improved overall energy efficiency. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4.2.4.3 Fibre To The distribution point (FTTdp) | The bandwidth available from optical fibre transmission systems makes them a very cost-effective medium to carry the traffic of subscriber(s) requiring high capacity between their access network operator's site and the premises served using a hybrid fibre/copper infrastructure. This usually takes the form of equipment (Distribution Point Unit) located close to the distribution point which marks the boundary between the optical transport network and the copper distribution network (last drop). The DPU may serve a single customer or several customers considering that it can be connected to single copper pair or several. FTTdp architecture usually embarks Reverse Power Feeding from customer premises; power feeding that may be shared among active users in the case of Multiple Dwelling Unit. RPF is required for DPU as a power source may not be found easily close to Distribution points (pole, manhole, shaft in particular). NOTE: an ENTI for an operator network may be connected to more than one NTP, within the premises, each of which is service-specific FTTH Transport Distribution Access network Customer network Access network (internal) Access network (external) NTP ENTI NTP ENTI BEF Last cabinet NOTE 1: dotted line indicates non-optical fibre media , that is metallic (balanced or coaxial) cabling or wireless transmission NTP ENTI Customer network Access network Access network (internal) Access network (external) Transport Distribution FTTC1 FTTB1 ENTI HEF NTP HEF BEF HEF Last cabinet Operator site Operator site Multi-tenant premises Single tenant premises Large single tenant premises Multi-tenant premises Figure 2b: FTTH access network functional description Figure 2a: FTTB/C access network functional description ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 15 As transmission techniques over copper are able to offer a very high bit rate over short distance, the copper distribution point is an adequate location for DPU as final drop cable are less than a few hundred metres long. Consequently, very high bit rate traffic can reach customer premises without fibre installation inside customer premises. Several copper drop pairs may leave the distribution point to reach several customer premises with sometimes a partial common path between some copper pairs. To prevent impact on bit rate due to coupling between copper drop cables sharing partially a same path, DPU may embed a vectoring function. From an energy consumption point of view, DPU is limited to a few customer (1 to 8) considering power restrictions associated to RPF that currently limits total power launched from a single customer to the DPU to 15 W. Resiliency is not requested at this time on fibre transport network or on copper distribution network as this increases power consumption that DPU cannot afford. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4.2.4.4 Fibre to the Building (FTTB) | The bandwidth available from optical fibre transmission systems makes them a very cost-effective medium to carry the traffic of subscribers requiring high capacity between their access network operator's site and the premises served. However, where the building accommodates multiple domestic or small commercial organizations, the service delivered to individual subscribers within the building is restricted by the transmission medium between the FTTB interface and the subscriber. There is generally no requirement for resilient solutions between individual subscribers and the operator's site since although certain subscribers may have significant demands for high data throughput there is no lifeline quality required for those residential "best effort" services. Where the building accommodates more demanding commercial entities it may be necessary to provide a resilient solution to ensure service continuity. Thus, in a similar manner to that noted for the FTTCab case outlined in clause 4.2.4.2, two or more optical fibre connections may be needed to such premises using different cable routings. These diverse routings may even be connected to different operator sites, and possibly even to different operator networks where extreme reliability is a business necessity. Other resilient solutions may also be implemented depending on the access network operator's policies and the customer's particular requirements. Any such resilient solutions invariably have a greater total energy requirement than the single attachment configuration, and depending on the protection scheme may go up to twice the figure applicable in an unprotected access network or even higher if such requirement remains low. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4.2.4.5 Fibre to the Home (FTTH) | The bandwidth available from optical fibre transmission systems makes Fibre a very cost-effective medium to carry the traffic of subscribers requiring considerable capacity between their access network operator's site and the individual subscribers served. There is generally no requirement for resilient solutions between the subscriber and the operator site since although certain subscribers may have significant demands for data throughput, primarily for entertainment purposes, the criticality of those services is comparatively low. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4.2.5 Other access technologies | A number of other telecommunications access technologies are available including power line transmission systems, point to point laser-based links and satellite access systems, Each of these suffers from one or more of a variety of disadvantages (low bandwidth, poor reliability, high cost, etc.) and whilst they are all valuable in certain niche markets, none is generally suitable for high-bandwidth, high-reliability, low-cost, mass-market communications systems. Such applications are not expected to be significant consumers of energy in the access network and thus are not discussed further in the present document. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 4.3 Up to 400 VDC versus AC | The increase of service and of energy density of the telecommunications and datacom (ICT) equipment has led to more equipment in the same existing premises and higher power consumption. The telecom equipment are commonly powered in 48 VDC and the servers in AC, e.g. three phases 400 VAC distribution and 230 VAC single phase at 50 Hz in Europe. ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 16 Therefore, the A3 power interface voltage ranges proposed in ETSI EN 300 132 series [i.19] have been defined with consideration to the: • Need to unify the power supply to all telecommunications and datacom (ICT) Equipment. • Reduction of the power losses as well as copper cross-section area in the power distribution wires. • Need to maintain a highly reliable power source for telecommunications and datacom. ETSI EN 300 132-3-1 [i.20] defines the requirements for the up to 400 VDC power interface at the input of the telecommunications and datacom (ICT) equipment fed from the site power plant, and includes requirements relating to its stability and measurement. The up to 400 VDC power feeding solution for ICT sites and other building using the up to 400 VDC power interface, are well adapted to renewable energy or distributed sources or new micro-grids (see ETSI TS 105 174-2 [i.21], clause 10.2.3), most of them being more complex in AC than in DC. The DC allows great simplification by avoiding frequency synchronization. Many documents, studies, and standards suggest that direct DC can generate some savings from 5 % to 15 % depending on several conditions. Such as generation of AC equipment, load of the site, etc. Technically, telecom equipment from main vendors could accept direct up to 400 VDC voltage range defined in ETSI EN 300 132-3-1 [i.20] and such equipment progressively gets available. In the meantime, the solution proposed by energy vendors is using very high efficiency DC interface converters A3/A from up to 400 VDC range to -48 VDC range as defined in ETSI EN 300 132 series [i.19]. The benefit is a strong reduction of copper use in the distribution (typically a factor 10 in mass), while reducing losses from 1 % or 2 %, which is compensating the losses in the converters of about 1 % or 2 % also. The cost saving of copper is so big that it can pay the over cost of these converters even when they are redundant. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 5 Energy efficiency standards and metrics | |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 5.1 Review of activities outside ETSI | |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 5.1.1 Broadband Code of Conduct | The Broadband Code of Conduct [i.1] provides the power consumption objectives of the Fixed Access Nodes according to the technology (DSL, PON or POTS). The Broadband Code of Conduct [i.1] sets out the basic principles to be followed by all parties involved in broadband equipment, in respect of energy efficient equipment. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 5.2 Monitoring of energy management | |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 5.2.1 Generalities | ETSI ES 205 200-3 [i.24] has been developed by ETSI ATTM with the support of ETSI ISG OEU members (ICT world Users) in order to define the most efficient tools. ETSI ES 205 200-3 [i.24] defines the so-called Global Key Performance Indicators (Global KPIs), it shall enable the monitoring of ICT sites energy management. ETSI ES 205 200-3 [i.24] proposes a single Global KPI (DCEM), Data processing and Communication Energy Management, which combines four Objective KPIs. The energy management efficiency of ICT sites of the whole industry shall be benchmarked by these Global KPIs. ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 17 |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 5.2.2 Objective Key Performance Indicators | |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 5.2.2.1 Definitions | The Objective KPIs described in ETSI GS OEU 012 [i.18] relate to specific elements of energy management for operational infrastructures under the control of operators as follows: • energy consumption (KPIEC): the total consumption of energy by an operational infrastructure; • task efficiency (KPITE): a measure of the work done for a given amount of energy consumed (closer to former PUE); • energy re-use (KPIREUSE): is the yearly energy reuse rate transfer or conversion of energy produced by the operational infrastructure to do other work; • renewable energy (KPIREN): is the yearly use rate of energy coming from dedicated generation systems using resources that are naturally replenished. The set of Objective KPIs are used to define a Global KPI (KPIDCEM) that allows benchmarking the energy management efficiency of ICT sites depending on their gauge. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 5.2.2.2 Energy consumption in FAN sites | As given in ETSI GS OEU 012 [i.18]: KPIEC = ECDC And HE DC TE EC EC KPI = |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 5.2.3 Global KPI | |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 5.2.3.1 DCEM in a site | The Global operational KPI reflects the overall performance of the operational infrastructures against wider energy management targets. KPIDCEM is composed of two values, DCG and DCP, where: • DCG defines the energy consumption gauge of the DC; • DCP defines the performance of the DC for the relevant gauge. Table 2: Default Gauges (DCG) DCG KPIEC range XXS KPIEC ≤ 0,04 GWh XS 0,04 GWh < KPIEC ≤ 0,2 GWh S 0,2 GWh < KPIEC ≤ 1 GWh M 1 GWh < KPIEC ≤ 5 GWh L 5 GWh < KPIEC ≤ 25 GWh XL 25 GWh < KPIEC ≤ 100 GWh XXL KPIEC > 100 GWh ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 18 Table 3: Default Classes of DCP DC commissioning date since 2005 (see note) before 2005 (see note) DCP DCP Class ≥ < ≥ < A 0,70 1,00 B 0,70 1,00 1,00 1,40 C 1,00 1,30 1,40 1,70 D 1,30 1,50 1,70 1,90 E 1,50 1,70 1,90 2,10 F 1,70 1,90 2,10 2,30 G 1,90 2,10 2,30 2,50 H 2,10 2,40 2,50 2,70 I 2,40 2,70 NOTE: Year of Kyoto Protocol entering into force. The following formula applies to the calculation of DCP for all the gauges: ( ) ( ) REN REN REUSE REUSE TE P KPI W KPI W KPI DC × − × × − × = 1 1 Where: WREUSE = Mitigation factor for KPIREUSE (the value may vary depending on the gauge within the range 0 to 1, the default value is 0,5). WREN = Mitigation factor for KPIREN (the value may vary depending on the gauge within the range 0 to 1, the default value is 0,5). The Global KPIDCEM is presented as a combination of the two values, DCG and DCP, in the following form: Gauge (see table 2), Class (see table 3), e.g. M, C. All measurement points and processes of all KPI(s) for sites are described in ETSI GS OEU 012 [i.18]. |
790e7653f50fec0cf220fbd3059fc6ab | 105 174-4-1 | 5.2.3.2 Global KPI (KPIDCEM) for a group of ICT sites | The set of Objective KPIs as defined in clause 5.2 are used to define a Global KPI (KPIDCEM) for a group of sites. That allows benchmarking the energy management efficiency of a group of Broadband fixed access sites depending on its gauge. DCEM is composed of two values: Energy consumption Gauge and Class. The Gauge depends on the global energy consumption by all the fixed access sites in the group and the Class is a weighted average of all classes. For a Group of Broadband fixed access sites: = for site i. KPIECG is the total consumption of energy by the group of sites. The default number of DCG gauges is seven as shown in table 4 and can be adapted by the user of the KPIDCEM. Table 4: Default Gauges (DCG) DCG KPIECG range XXS KPIEC ≤ 0,4 GWh XS 0,4 GWh < KPIEC ≤ 2 GWh S 2 GWh < KPIEC ≤ 10 GWh M 10 GWh < KPIEC ≤ 50 GWh L 50 GWh < KPIEC ≤ 250 GWh XL 250 GWh < KPIEC ≤ 1 000 GWh XXL KPIEC > 1 000 GWh ∑ = = n i EC ECG i KPI KPI 1 ) ( EC KPI ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 19 The class associated with a group of fixed access sites is a weighted average of all sites classes and the DCp is the same as the table 3. Where: • n = the number of sites in the group of fixed access sites. • NumClass (i) = class number for the site (i) which takes the values between A to I (see table 3). ) ( ) ( * ) ( 1 1 i KPI i KPI i NumClass NumClassG n i EC EC n i ∑ ∑ = = = ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 20 Annex A (informative): Relationship between KPI(s) Operational Global and Objective KPIs are fundamentally different from the Technical KPIs applied to products and systems at the design and engineering stages. The former are used to monitor and drive user behaviour whereas the latter are substantial indications of potential operational performance. Technical KPIs can be applied to the clause 5 by assessing energy consumption for a number of specific operating conditions and also across a combination of such operating conditions. Assuming those operating conditions reflect the probable operating environment for the component, sub-assembly or product, a customer may make valued judgements in relation to the appropriateness of the Technical KPI. It is therefore important to support, but differentiate, the role of the Technical KPIs from the Objective and Global operational KPIs. Figure A.1: The relationship of energy-related Technical, Objective and Global KPIs More complex products may contain hardware and/or software which automatically reduce energy consumption under specific operating conditions by putting certain functions into "idle" states if not required. Components Sub-assemblies Products Systems Energy consumption Task efficiency TECHNICAL KPI TECHNICAL KPI PRODUCT AND SYYSTEM CAPABILITY Energy consumption Task efficiency OBJECTIVE KPI OBJECTIVE KPI INSTALLATION, CONFIGURATION AND OPERATION FOR EXTENDED PERIOD Energy re-use Renewable contribution OBJECTIVE KPI OBJECTIVE KPI Energy management GLOBAL KPI DESIGN AND ENGINEERING SYSTEM OPERATION ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 21 Annex B (informative): Factors impacting energy efficiency The factors shown in table B.1 contribute to poor energy efficiency and, consequently, high energy consumption. Table B.1: Principle factors leading to poor energy efficiency Power distribution systems Power distribution units which result in under-utilization of components. N + 1 or 2N redundant designs. Decreased efficiency of Uninterruptible Power Supply (UPS) equipment when run at low loads. Cooling systems Air conditioners forced to consume extra power to drive air at high pressures over long distances. Pumps with flow rate automatically adjusted by valves (which reduces the pump efficiency). N + 1 or 2N redundant designs, which result in under-utilization of components. Access node Lack of low power mode in the broadband access nodes; equipment in active mode 24/24, 7/7 but only used at certain hours of the day and/or on certain days. under-utilization of line cards: equipped ratio of the LT card could be too low Old generations of access nodes, with a low computing power/electrical consumption ratio. ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 22 Annex C (informative): Bibliography ETSI TR 102 530: "Environmental Engineering (EE); The reduction of energy consumption in telecommunications equipment and related infrastructure". ETSI TS 102 533: "Environmental Engineering (EE); Measurement Methods and limits for Energy Consumption in Broadband Telecommunication Networks Equipment". Recommendation ITU-T G.983.1 (05/2005): "Broadband optical access systems based on Passive Optical Networks (PON)". Recommendation ITU-T G.983.2 (01/2007): "ONT management and control interface specification for B-PON". Recommendation ITU-T G.983.3 (07/2005): "A broadband optical access system with increased service capability by wavelength allocation". Recommendation ITU-T G.983.4 (01/2005): "A broadband optical access system with increased service capability using dynamic bandwidth assignment". Recommendation ITU-T G.983.5 (01/2002): "A broadband optical access system with enhanced survivability". Recommendation ITU-T G.988 (10/2012): "Optical network unit management and control interface specification". ETSI TS 105 174-5-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 5: Customer network infrastructures; Sub-part 1: Homes (single-tenant)". ETSI ES 205 200-2-2: "Access, Terminals, Transmission and Multiplexing (ATTM); Energy management; Global KPIs; Operational infrastructures; Part 2: Specific requirements; Sub-part 2: Fixed Broadband access networks". ETSI ETSI TS 105 174-4-1 V1.2.1 (2015-09) 23 History Document history V1.1.1 October 2009 Publication as TR 105 174-4 V1.2.1 September 2015 Publication |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 1 Scope | The present document details the test specifications for the Smart Secure Platform (SSP) integrated into an SoC, also known as iSSP. It specifies the test environment to verify conformance requirements for services running in the Smart Secure Platform and in any terminal hosting a Smart Secure Platform application as defined in ETSI TS 103 666-1 [9] focusing on the specific attributes that are defined for the iSSP in ETSI TS 103 666-2 [10]. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 2 References | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 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. • In the case of a reference to a TC SCP document, a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 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. [1] ANSI X9.62-2005: "Public Key Cryptography for the Financial Services Industry, The Elliptic Curve Digital Signature Algorithm (ECDSA)". [2] BSI-CC-PP-0084-2014: "Security IC Platform Protection Profile with Augmentation Packages". [3] BSI TR-03111: "Elliptic Curve Cryptography", Version 2.10. [4] ETSI TS 102 221: "Smart Cards; UICC-Terminal interface; Physical and logical characteristics". [5] ETSI TS 102 223: "Smart Cards; Card Application Toolkit (CAT)". [6] ETSI TS 102 226: "Smart Cards; Remote APDU structure for UICC based applications". [7] ETSI TS 102 241: "Smart Cards; UICC Application Programming Interface (UICC API) for Java Card™". [8] ETSI TS 103 465: "Smart Secure Platform (SSP); Requirements Specification". [9] ETSI TS 103 666-1: "Smart Secure Platform (SSP); Part 1: General characteristics". [10] ETSI TS 103 666-2: "Smart Secure Platform (SSP); Part 2: Integrated SSP (iSSP) characteristics". [11] ETSI TS 103 999-1: "Smart Secure Platform (SSP); Part 1: Test Specification, general characteristics". [12] GlobalPlatform Technology: "Card Specification", Version 2.3.1. [13] GlobalPlatform Technology: "Open Firmware Loader for Tamper Resistant Element", Version 1.3. [14] GlobalPlatform Technology: "Virtual Primary Platform - Firmware Format", Version 1.0.1. [15] GlobalPlatform Technology: "VPP - Concepts and Interfaces", Version 1.0.1. [16] GlobalPlatform Technology: "VPP - OFL VNP Extension", Version 1.0. [17] IETF draft-shen-sm2-ecdsa-02: "SM2 Digital Signature Algorithm". ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 14 Release 15 [18] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". [19] IETF RFC 4122: "A Universally Unique IDentifier (UUID) URN Namespace". [20] IETF RFC 4868: "Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPsec". [21] IETF RFC 5280: "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". [22] IETF RFC 5480: "Elliptic Curve Cryptography Subject Public Key Information". [23] IETF RFC 5639: "Elliptic Curve Cryptography (ECC) Brainpool Standard Curves and Curve Generation". [24] IETF RFC 5754: "Using SHA2 Algorithms with Cryptographic Message Syntax". [25] IETF RFC 5758: "Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSA". [26] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)". [27] IETF RFC 8446: "The Transport Layer Security (TLS) Protocol Version 1.3". [28] ISO/IEC 10118-3:2018: "IT Security techniques - Hash-functions - Part 3: Dedicated hash functions". [29] ISO/IEC 14888-3:2018: "IT Security techniques - Digital signatures with appendix - Part 3: Discrete logarithm based mechanisms". [30] ISO/IEC 9646-7:1995: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [31] NIST 800-56A (May 2013): "Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography (Revision 2)". [32] NIST 800-108: "Recommendation for Key Derivation Using Pseudorandom Functions". [33] NIST SP 800-38B (May 2005): "Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication". [34] ETSI SCP forge repository - ETSI TS 103 999-2 Projects:. ‑ ETSI TS 103 999-2 iSSP Test Specification; available at: https://forge.etsi.org/rep/scp/ts_103999-2_issp_testspec ‑ ETSI TS 103 999-2 iSSP Test Tool; available at: https://forge.etsi.org/rep/scp/ts_103999- 2_issp_Testtool ‑ ETSI TS 103 999-2 iSSP eGCM; available at: https://forge.etsi.org/rep/scp/ts_103999- 2_iSSP_eGCM ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 15 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 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. • In the case of a reference to a TC SCP document, a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 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. Not applicable. 3 Definition of terms, symbols, abbreviations and formats |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 465 [8], ETSI TS 103 666-1 [9] and ETSI TS 103 666-2 [10] apply. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 103 465 [8], ETSI TS 103 666-1 [9] and ETSI TS 103 666-2 [10] apply. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 465 [8], ETSI TS 103 666-1 [9], ETSI TS 103 666-2 [10] and the following apply: ARP Access Right Pattern CI Certificate Issuer LBA Local Bundle Assistant SCL SSP Common Layer SKID Subject Key IDentifier SPBL Secondary Platform Bundle Loader SPBM Secondary Platform Bundle Manager SSP Smart Secure Platform SUT System Under Test TT Test Tool ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 16 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 3.4 Formats | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 3.4.1 Format of the conformance requirement tables | The columns in the requirement tables in clause 5 of the present document have the following meaning: Table 3.1: Format of the conformance requirement tables Column Meaning Req.ID This column shows the ordinal term assigned to a requirement identified in the referenced specification. The following syntax has been used to define the unique requirement terms: RQ<XX><YY>_<ZZZ> or RQ<XX><YY>_<ZZZA> XX: Main clause of the core specification in which the conformance requirement is listed. YY: Subclause of the main clause in the core specification in which the conformance requirement is listed. ZZZ: Continuously increasing number starting with '001'. ZZZA: Sub-numbering (alphabetic) used if an identified requirement is split for clarification. Clause The "Clause" column helps to identify the location of a requirement by listing the clause hierarchy down to the subclause the requirement is located in. Description In this column the requirement text is shown. Where the text can either be a copy of the original requirement as found in ETSI TS 103 666-2 [10] or a text analogous to the requirement text (e.g.: if the requirement text is descriptive and can be shortened or truncated). |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 3.4.2 Format of the applicability table | The columns in the applicability table, Table 4.1, have the following meaning: Table 3.2: Format of the applicability table Column Meaning Test ID A reference to the test description identification detailed in the present document and required to validate the implementation of the corresponding item in the "Description" column. Description A short non-exhaustive description of the test purpose is given here. In general, the description text used will equal the test description name used in the present document. Release Number of the version the tested feature was introduced in. Rel-<x> For a given Release, the corresponding "Rel-<x>" column lists the tests required for the SPI to be declared compliant to this Release. Each entry shows the status following notations defined in ISO/IEC 9646-7 [30]: M mandatory - the capability is required to be supported. O optional - the capability may be supported or not. N/A not applicable - in the given context, it is impossible to use the capability. X prohibited (excluded) - there is a requirement not to use this capability in the given context. Oi qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies a unique group of related optional items and the logic of their selection which is defined immediately following the table. Ci conditional - the requirement on the capability ("M", "O", "X" or "N/A") depends on the support of other optional or conditional items. "i" is an integer identifying a unique conditional status expression which is defined immediately following the table. For nested conditional expressions, the syntax "IF ... THEN (IF ... THEN ... ELSE ...) ELSE ..." shall be used to avoid ambiguities. Support Is blank in the pro forma and is to be completed by the manufacturer in respect of each particular requirement to indicate the choices which have been made in the implementation. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 17 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 3.4.3 Numbers and Strings | The conventions used for decimal numbers, binary numbers and strings. Table 3.3: Convention of Numbering and Strings Convention Description nnnnn A decimal number, e.g. PIN value or phone number 'b' A single digit binary number 'bbbbbbbb' An 8-bit binary number 'hh' A single octet hexadecimal number 'hh hh…hh' A multi-octet hexadecimal number or string "SSSS" A character string NOTE: If an 'X' is present in a binary or hexadecimal number, then the digit might have any allowed value. This 'X' value does not need to be interpreted within the particular coding shown. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 3.4.4 Format of test description clauses | In general clauses with test descriptions use the following basic format: X.Y. Group of test descriptions for a particular topic X.Y.1 Configurations This header is to be used in every clause that includes configuration descriptions. It may be followed by a sentence explaining that there are no specific configurations required for this particular topic or: X.Y.1.1 C<aaa>_<y>1<n> <optional> Where each sub-header of a required configuration is built from a leading 'C' followed by <aaa>, a minimum three-digit abbreviation for the configuration description group, an underscore, an <y> for the clause number, a '1' for the 'Configurations' clause, and <n>, a minimum one-digit configuration number. This sub-header may include explanatory text following the identification. Whenever a configuration exists it is presented in a table of the following format: Configuration ID C<aaa>_<y>1<n> Configuration description Host Domain Identifier (TESTER) Host Identifier Application Identifier Gate Identifier . . . Host Domain Identifier (SUT) Host Identifier Service Identifier Gate Identifier . . . Example: Connection A Configuration description shows a drawing representing the entities involved and the connections available between instances. It does not include explanatory text. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 18 Release 15 X.Y.2 Procedures This header is to be used in every clause that includes procedure descriptions. It may be followed by a sentence explaining that there are no specific procedures required for this particular topic or: X.Y.2.1 P<aaa>_<y>2<n> <optional> Where each sub-header of a required procedure is built from a leading 'P' followed by <aaa>, a minimum three-digit abbreviation for the procedure description group, an underscore, an <y> for the clause number, a '2' for the 'Procedures' clause, and <n>, a minimum one-digit configuration number. This sub-header may include explanatory text following the identification. Whenever a procedure exists it is presented in a table of the following format: Procedure ID P<aaa>_<y>2<n> Procedure objectives Description of the procedure objectives. Configuration reference C<aaa>_<y>1<n> See note 1. Initial conditions Text and/or list of procedure IDs identifying the initial conditions that need to be fulfilled before the procedure sequence defined in this table can be executed. See note2. Procedure sequence Step Description 1 Description of procedure step #1 … … n Description of procedure step #n NOTE 1: Reference to the appropriate configuration. NOTE 2: Procedure IDs can be referenced if the integration of existing procedure sequences can avoid required procedure steps duplication to achieve the initial conditions. Referenced procedures are intended to be executed in given order. Procedures are sequences that are executed to prepare specific initial conditions for a test. As such they do not include verifications of any requirements. X.Y.3 Test descriptions This header is to be used for every clause that includes test descriptions. It may be followed by: X.Y.3.1 <aaa>_<y>3<optional s><n> <optional> Where each sub-header of a test description is built from <aaa>, a minimum three-digit abbreviation for the test description group, an underscore, an <y> for the clause number, a '3' for the 'Test descriptions' clause, a clause number <s> (optional – only added if test descriptions are structures in sub-subclauses) and <n>, a one-digit configuration number. This sub-header may include explanatory text following the identification. Whenever a test description exists it is presented in a table of the following format: Test ID <aaa>_<y>3<s><n> or <aaa>_<y>3<n> Test objectives Description of the test objectives. See note 1. Configuration reference C<aaa>_<y>2<n> See note 2. Initial conditions Text and/or list of procedure IDs identifying the initial conditions that need to be fulfilled before the test sequence defined in this table can be executed. See note 3. Test sequence ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 19 Release 15 Step Description Req.ID 1 Description of test step #1 … … RQ<XX><YY>_<ZZZ> n Description of test step #n NOTE 1: The descriptions should reflect the objectives of the requirements verified. NOTE 2: Reference to the appropriate configuration. NOTE 3: If possible the initial conditions for the test sequence shall be defined by existing procedures. Referenced procedures are intended to be executed in given order. Requirement IDs listed in the Req.ID tab are references to the requirements listed in clause 5.x of the present document. A requirement listed in the test sequence is handled as verified if the response related to the listed requirement has the expected contents or if the described test step could be executed successfully. Req.IDs are always assigned to a response step. If there are no test descriptions defined for a group of tests, but related requirements are available, an appropriate clause shall inform about the status of the requirements. E.g.: X.Y.3.Z Requirements not testable, implicitly verified or verified elsewhere The header of this clause shall be adjusted depending on which condition applies for the identified requirements. Example text for requirements referenced from another standardization body: The following requirements identified in <XYZ> are not tested in accordance with the present document, as they are referencing requirements from another standardization body (<NAME>): <XX><YY>_<ZZZ>, … Example text for requirements implicitly tested: The following requirements identified in <XYZ> are generated from descriptive text. An explicit verification is not possible but with correct execution of the related function the requirements can be handled as implicitly verified: <XX><YY>_<ZZZ>, … Example text for requirements not tested: The following requirements identified in <XYZ> are either generated from descriptive text or not testable in the defined test environment. A verification of the listed requirements is not possible: <XX><YY>_<ZZZ>, …The clause with explanatory text for the untested or implicitly tested requirements is the last clause in the Test description clause. Nevertheless, it can be provided as the first clause if no executable test sequences are defined. The hierarchy given in this example structure is not fixed. If building sub-groups is useful this may be done on any level of the test description hierarchy. Furthermore, it is not required to generate sub-groups for all the three main sections (Configurations, Procedures, Test descriptions) if adding a sub-group is useful in any of these sections. E.g.: common Configurations on hierarchy level 3, common Procedures on hierarchy level 3 but subgroups for the test descriptions with a new group header on level 4 and the test descriptions on level 5. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 3.4.5 Dynamic content validation in ASN.1 structure | In certain test descriptions dynamic content returned by the DUT (e.g.: value within ASN.1 structure, signature, integer, …) is processed according to the following grammar: operations ::= '<' operation ( logical_operator operation)* '>' operation ::= operation_Identifier ' (' variable_identifier (', ' parameter)* ') ' operation_identifier ::= 'STORE'|'REPLACE'|'COMPARE'|'ISFIELDNOTEXIST' logical_operator ::= 'AND'|'OR'|'XOR' variable_identifier ::=([A-Z]|[a-z])+[0-9]* ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 20 Release 15 where: • Operation_identifier: is identifying the operation to be performed on dynamic content of aFieldName as: - STORE: store the dynamic content of an aFieldName into a test tool variable identified by the Variable_identifier. - REPLACE: retrieve a variable identified by the Variable_identifier and replace the content of aFieldName with the content of the variable. - COMPARE: compare the content of aFieldName with the content of a variable and return 'true' or 'false' as a result to the test tool. This operator requires one or more parameters. If more than one parameter is used, the parameters are OR concatenated. Possible parameters are: GT: the content of the aFieldName shall be strictly greater than the content of a variable LS: the content of the aFieldName shall be strictly less than the content of a variable EQ: the content of the aFieldName shall be equal to the content of a variable DIF: the content of the aFieldName shall be different from the content of a variable - ISFIELDNOTEXIST: return 'true', if aFieldName field does not exist. • Variable_identifier: variable identifier managed by the test tool. The variable identifier shall consist of a set of alphanumeric characters only. The operations are inserted within a comment associated to a field as follows: aFieldName … /* operations */ For example: aHandleNotificationHeader { aNotificationReceiverId eFUNCTION-REQUESTER-ID-1, aNotificationCallId '00000000'H /* <COMPARE(aEMPTY,DIF)>*/, }, where: aEMPTY OCTET STRING ::= ''H /*<STORE(aEMPTY)>*/ |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4 Test environments | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.1 Test environments for the different test aspects | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.1.0 General overview on the iSSP ecosystem to be tested | The general architecture of the iSSP ecosystem is defined in ETSI TS 103 666-1 [9], clause 12.1. A representation of the iSSP ecosystem is shown in Figure 4.1 to ease the identification of entities required and interfaces tested in accordance with the present document. Interfaces (Si1, Si2, Si3 and Si4) involved in Secondary Platform Bundle management are highlighted. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 21 Release 15 Figure 4.1: iSSP ecosystem |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.1.1 Evaluation Assurance Level certification | The support of a certification by composition from the SSP Primary Platform Evaluation Assurance Level is defined in ETSI TS 103 666-1 [9], clause 11.2.1. SSP Evaluation Assurance Level certification is out of scope of the present document. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.1.2 Test environment for Secondary Platform Bundle services | The test environment defined in Figure 4.2 illustrates the perspective of the tests of a service running in the SSP from an application running on the terminal. Figure 4.2: Tests of a service in the SSP All tests defined in ETSI TS 103 999-1 [11] are applicable. This test environment is valid for testing the SPB loader service described in ETSI TS 103 999-1 [11], clause 12 and will support the Si3 interface. NOTE: The test environment defined for testing a service in the SSP in the present document is similar to the one defined for testing a service in the SSP in ETSI TS 103 999-1 [11], clause 4, Figure 4.3. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 22 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.1.3 Test environment for Secondary Platform Bundle Manager services | The test environment defined in Figure 4.3 illustrates the perspective of the tests of services running in the SPBM (SUT). Figure 4.3: Tests of a service in the SPBM The applications running in the test tool are functionally equivalent to: • The LBA running on the terminal via Si2 and Si4. • The service provider via the Si1. As the list of functions table 12.4 in ETSI TS 103 666-2 [10] does not define any service in the LBA, no test descriptions for testing the LBA are needed. The test tool connector is the Si1 and Si2 interfaces as defined in ETSI TS 103 666-2 [10], clauses 12.6.3 and 12.6.4. The SPBM shall be prepared for test purposes in supporting a set of certificates for ETSI tests. These certificates shall be compliant to what is defined in ETSI TS 103 666-2 [10], clause 12.2.1. The SPBM is a certified functional block for which no invasive test tool connector is allowed. Consequently, the Si4 interface functionality is tested with negative cases, deducing the transfer of protocol elements required for authorization, mutual authentication, integrity and confidentiality. The testing of the Si6 interface connecting the CI and the SPBM is out of the scope of the present document. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.1.4 Test environment for Primary Platform services | Figure 4.4.4 illustrates the perspective of the tests of a service running in the primary platform from an application running on the primary platform point of view (here a SPB). Figure 4.4: Tests of a service in the primary platform The primary platform can only be tested from a SPB via the interface defined in ETSI TS 103 666-2 [10], clause 8. The iSSP shall enable the SPB and then be capable to address test content to the Primary Platform. The SPB Test Service interprets commands from the test application running in the test tool. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 23 Release 15 Tests related to the kernel functions of the ABI/API and to the communication service interface of the Primary Platform are out of the scope of the present document. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.1.5 Principles of the data exchange | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.1.5.1 Data Format verification | The verification of the data exchanged between the SPBL, the SPBM and the LBA is globally performed by comparing the data in question with the ASN.1 model defined in ETSI TS 103 666-2 [10]. The application acts as data issuer when the connected service is the data receiver and vice versa. The data flow from the data issuer to the data receiver is illustrated in Figure 4.5. The data format verification throws an exception if the exchanged data are not fully compliant with the ASN.1 model. Data Issuer Data Format Verification Data Receiver ? OK/NOK Figure 4.5: Data format verification The data format verification on the presentation layer of the Si2 interface as shown in Figure 4.5 is done for ASN.1 compliance only. The correctness of the data contents conveyed by the Si2 presentation layer are verified by the TT by analysing the received data. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.1.5.2 Data contents verification | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.1.5.2.1 SUT test concept | The TT always acts as the application. As the SUT (service) appears as a "black box", checking its functionalities is done by stimulating the SUT with invalid data contents provided in an appropriate ASN.1 model, expecting the SUT to throw errors and/or exceptions. To verify that the SUT is doing data contents verification software tools allowing to provide invalid or incorrect data using the appropriate ASN.1 model are provided. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.1.5.2.2 Software tools for clause 12 | Example software tools associated with the Si2 test descriptions provided in the present document are available in the ETSI forge repository [34]. All PDU use the DER format. The provided software tools enable a TT to generate: • The SPBL certification path (authentic) leading to a correct certification path. • The SPBM certification path (fake) leading to a wrong certification path. • The SPBL certification path (authentic) leading to a correct certification path. • The SPBM certification path (fake) leading to a wrong certification path. • The Si2GetSpbmCertificate command according to parameters. • The Si2GetSpbmCertificate response according to parameters. • The Si2GetBoundSpbImage command according to parameters. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 24 Release 15 • The Si2GetBoundSpbImage response according to parameters. • The Si2HandleNotification command according to parameters. • The Si2HandleNotification response according to parameters. The provided software tools enable a TT to verify: • The Si2GetSpbmCertificate response according to parameters. • The Si2GetBoundSpbImage response according to parameters. • The Si2HandleNotification response according to parameters. Software tools associated with these test descriptions do not deal with the firmware as defined by GlobalPlatform in Virtual Primary Platform - Firmware Format, [14]. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.1.5.3 Public Key Infrastructure for tests | Figure 4.6 defines the PKI used for the test descriptions of the Si4 interface. SSPM CI SSPM-SUB-CI SSPM SSPM-SUB SPBL SPBM CI SPBM-SUB-CI SPBM SPBM-SUB SPBM-DS1 SPBM-DS2 SPBM-DS1-KA EE CA CA CA CA CA CA CA CA EE EE EE CERT.ETSI-SSP-SSPM-CI-CA.ECDSA CERT.ETSI-SSP-SPBM-CI-CA.ECDSA CERT.ETSI-SSP-SSPM-CA.ECDSA CERT.ETSI-SSP-SPBM-CA.ECDSA CERT.ETSI-SSP-SPBM-SUB- CA.ECDSA CERT.ETSI-SSP-SSPM-SUB-CA.ECDSA CERT.ETSI-SSP-SPBL-EE.ECDSA CERT.ETSI-SSP-SPBM-DS1-KA-EE.ECKA CERT.ETSI-SPBM_DS1-EE.ECDSA CERT.ETSI-SPBM_DS2-EE.ECDSA CERT.ETSI-SSP-SPBM-SUB-CI-CA.ECDSA CERT.ETSI-SSP-SSPM-SUB-CI-CA.ECDSA CA: Certification Authority EE: End Entity Figure 4.6: PKI for tests The hierarchical list of the digital certificates in the certification path of the SSPM CI is the following: • CERT.ETSI-SSP-SSPM-CI-CA.ECDSA • CERT.ETSI-SSP-SSPM-SUB-CI-CA.ECDSA • CERT.ETSI-SSP-SSPM-CA.ECDSA ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 25 Release 15 • CERT.ETSI-SSP-SSPM-SUB-CA.ECDSA • CERT.ETSI-SSP-SPBL-EE.ECDSA The hierarchical list of the digital certificates in the certification path of the SPBM CI is the following: • CERT.ETSI-SSP-SPBM-CI-CA.ECDSA • CERT.ETSI-SSP-SPBM-SUB-CI-CA.ECDSA • CERT.ETSI-SSP-SPBM-CA.ECDSA • CERT.ETSI-SSP-SPBM-SUB-CA.ECDSA • CERT.ETSI-SSP-DS1-EE.ECDSA, CERT.ETSI-SSP-DS2-EE.ECDSA, CERT.ETSI-SSP-DS1-KA- EE.ECKA For tests purposes only, a set of private keys compliant with the public key lengths supported by the ETSI TS 103 666-2 [10] is available in the ETSI forge repository as defined in SCP iSSP tooling [34]. The Si4 security protocol is independent of the ECC key lengths as well the Si4 test descriptions. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.1.6 Common ASN.1 coding | ETSITestGlobalDefinitions { id-issp test(3) } DEFINITIONS AUTOMATIC TAGS EXTENSIBILITY IMPLIED ::= BEGIN EXPORTS ALL; IMPORTS UUID, id-issp FROM ISSPDefinitions; /* Imports */ id-issp-test OBJECT IDENTIFIER ::= {id-issp test(3)} issp-egcm OBJECT IDENTIFIER ::= {id-issp-test egcm (1)} issp-egcm-aes-128 OBJECT IDENTIFIER ::= {issp-egcm egcm-aes-128 (1)} issp-egcm-aes-256 OBJECT IDENTIFIER ::= {issp-egcm egcm-aes-256 (2)} /*Custodian for tests*/ issp-acustodian-oid OBJECT IDENTIFIER ::= {id-issp-test acustodian-oid (2)} issp-acustodian-oid-telecom OBJECT IDENTIFIER ::= {issp-acustodian-oid telecom (1)} id-globalplatform OBJECT IDENTIFIER ::= {iso(1) member-body(2) us(840) globalplatform(114283)} id-part-number OBJECT IDENTIFIER ::= {id-globalplatform ofl(10) pn(1)} /*FamilyId Oid*/ id-family-id-test OBJECT IDENTIFIER ::= {id-issp-test id-family-id(3)} id-family-id-test-1 OBJECT IDENTIFIER ::= {id-family-id-test family(1)} id-family-id-test-2 OBJECT IDENTIFIER ::= {id-family-id-test family(2)} /* Family UUIDv5 for tests*/ /*URN: urn:ttf001.etsi.org:id-family-id-test-1*/ eFamilyIdTest1 UUID ::= 'FF334CCD9D055649B517C6ECBB1B5383'H /*URN: urn:ttf001.etsi.org:id-family-id-test-2*/ eFamilyIdTest2 UUID ::= '58DBFEA315355BBAA732D43F6C0A2956'H /* SPBId UUIDv5 for tests*/ /*URN: urn:ttf001.etsi.org:codem:47929dd4-9854-4f71-8dd8-e247fd909e13 */ eSPBIdTest1 UUID ::= 'E044EB70B41359DD9399F3D4124555E0'H /*URN: urn:ttf001.etsi.org:codem:83e58fe0-35ea-47f6-9b74-bdb7a5ecb772 */ eSPBIdTest2 UUID ::= '1266BF3477E251BEB02D23C7478B5AAD'H END ASN.1 coding/SCP iSSP tooling can be found in a sub-folder of [34] at: https://forge.etsi.org/rep/scp/ts_103999- 2_issp_testspec/raw/master/TS103999-2.asn. NOTE: Opening to the referenced file might only work if entered into the address bar of your internet browser. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 26 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 4.2 Applicability Table | The applicability tables in this clause are formatted as described in clause 3.4.2. Table 4.1: Applicability table Test ID Description Release Rel-15 Support PSVC_322 Primary Platform - Open a pipe session on the SPBL Service Gate Rel-15 M SVC_3311 - SVC_33110 Secondary Platform Bundle Loader Rel-15 M iSP_4341 - iSP_4344 Secondary Platform - Capability exchange Rel-15 M SI1_63311 - SI1_63317 Si1 interface - Si1.CreateSPReference Rel-15 M SI1_63321 - SI1_63328 Si1 interface - Si1.SelectSpb Rel-15 M SI1_63331 - SI1_63333 Si1 interface - Si1.FinalizePreparation Rel-15 M SI1_63341 - SI1_63347 Si1 interface - Si1.CancelPreparation Rel-15 M SI1_63351 Si1 interface - Si1.HandleNotification Rel-15 M SI2_64311 - SI2_643110 Si2 interface - Si2.GetSpbmCertificate Rel-15 M SI2_64321 - SI2_64327 Si2 interface - Si2.GetBoundSpbImage Rel-15 M SI2_64331 Si2 interface - Si2.HandleNotificatio Rel-15 M SI3_65311 - SI3_65314 Si3 interface - Si3.GetSspInfo Rel-15 M SI3_65321 Si3 interface - Si3.SetSpbmCredential Rel-15 M SI3_65331 Si3 interface - Si3.LoadBoundSpbInfo Rel-15 M SI3_65341 Si3 interface - Si3.LoadBoundSpbSds Rel-15 M SI3_65351 Si3 interface - Si3.LoadBoundSpbSeg Rel-15 M SI3_65361 Si3 interface - Si3.GetSspCredential Rel-15 M SI3_65371 - SI3_65372 Si3 interface - Si3.EnableSpb Rel-15 M SI3_65381 Si3 interface - Si3.DisableSpb Rel-15 M SI3_65391 Si3 interface - Si3.DeleteSpb Rel-15 M SI3_653101 Si3 interface - Si3.GetSpbMetadata Rel-15 M SI3_653111 Si3 interface - Si3.UpdateSpbState Rel-15 M SI3_653121 Si3 interface - Si3.GetSpbState Rel-15 M SI3_653131 Si3 interface - Si3.SwitchSpb Rel-15 M SI3_653141 Si3 interface - SPB Management Operations Rel-15 M SI3_65321 Si3 interface - Si3.SetSpbmCredential Rel-15 M SI4_66311 Si4 interface - Si4.SPBL service Rel-15 M SI4_66321 Si4 interface - Si4.SPB Manager service Rel-15 M |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5 Conformance requirements | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.1 Conformance requirement references | The conformance requirements that apply to the test descriptions defined in the present document are derived from the specification named in the reference text preceding each conformance requirement listing. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.2 Juxtaposition of terminologies | ETSI TS 103 666-2 [10] is using a different terminology than the Open Firmware Loader (OFL) specification [13] from Global Platform. As the Global Platform specification is referenced for various commands and functions, the juxtaposition of the used terms shall help to understand the test descriptions defined within the present document. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 27 Release 15 Table 4.2: Juxtaposition of ETSI and Global Platform terms ETSI OLF SSP Maker TRE maker SSP TRE SPBL OFL SPB container Firmware SPL certificate OFL certificate (CERT.OFL.ECDSA) SPBM (SPB Manager) IDS (Image Delivery Server) SPBM KA certificate CERT.IDS1.ECKA Primary Platform identifier No equivalence in OFL Si1.SelectSpb Out of the scope of GlobalPlatform Si1.CreateSPReference Out of the scope of GlobalPlatform Si3.GetSspInfo ANY_GET_PARAMETER with parameters for reading the registry Si2.GetSpbmCertificate Out of the scope of GlobalPlatform Si3.SetSpbmCredential ANY_SET_PARAMETER with parameter for IDS_CREDENTIALS Si2.GetBoundSpbImage Out of the scope of GlobalPlatform aSspInfoProtected ANY_GET_PARAMETER with TRE_CREDENTIALS aBoundSpbImageByTransacId Out of the scope of GlobalPlatform Si3.LoadBoundSpbInfo OFL_DO_OPERATE(VNP) Si3.LoadBoundSpbSds OFL_CHANGE_SEGMENT(VNP) Si3.LoadBoundSpbSeg OFL_LOAD_SEGMENT(VNP) aChangeSegmentParameter SDS (Segment Descriptor Structure) aDoOperateParameter IMD (Image Descriptor) aLoadSegmentParameter FFS LBA OFL Agent bound Secondary Platform Bundle image Bound Image Si3.EnableSpb OFL_ENABLE_FIRMWARE (VNP) Si3.DisableSpb OFL_DISABLE_FIRMWARE Si3.DeleteSpb OFL_DELETE_SESSION Si3.GetSpbMetadata ANY_GET_PARAMETER with register SPB_STATE ANY_GET_PARAMETER with the OFL_STATE register Si2.HandleNotification Out of scope of OFL aPartNumberId ANY_GET_PARAMETER with the PART_NUMBER register aPpIdentifier No match in OFL aFamilySpecificSspInfo No match in OFL Si3.GetSspCredential ANY_GET_PARAMETER with the TRE_CREDENTIAL_PARAMETER register aChallengeS CHALLENGE_S aIdTransac ID_TRANSAC aEPkSpblKa PK.OFL.ECKA aM-SSP M1, H1 aImageOwnerId IMOL aNumberSegment NUM_SEG in IMD aEncryptionType In the ATK.IDS2.ECDHE aImageMakerId UUIDI aM-IMD M2, H2 aM-ARP M3, H3 aM-TimeStamp M4, H4 aSpbmToken ATK.IDS2.ECDHE ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 28 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.3 Overview - Security requirements | Reference: ETSI TS 103 666-2 [10], clause 5.2. Req.ID Clause Description RQ0502_001 5.2 The provisions of ETSI TS 103 666-1 [9], clause 6.11 shall apply. RQ0502_002 5.2 The software and sensitive data of the iSSP shall never be exposed from the iSSP to any external component in plain text. RQ0502_003 5.2 The protection of software and sensitive data shall provide privacy, confidentiality, integrity, protection against rollback attacks, and protection against side-channel attacks. RQ0502_004 5.2 In the case where software and sensitive data are stored outside the iSSP, they shall also be protected in a way to achieve perfect forward secrecy and they shall be securely bound to that given iSSP instance, in accordance to clause 7.1.3.4 of ETSI TS 103 666-2 [10]. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.4 iSSP Architecture | Reference: ETSI TS 103 666-2 [10], clause 6. Req.ID Clause Description 6.1 Overview RQ0601_001 6.1 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 2.1 shall apply. 6.2 Functional architecture RQ0602_001 6.2 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clauses 5.1 and 5.2 shall apply. 6.3 Security perimeters RQ0603_001 6.3 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.3 shall apply. 6.4 Unprivileged execution model RQ0604_001 6.4 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.4 shall apply. 6.5 Unprivileged virtual address space RQ0605_001 6.5 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.5 shall apply. 6.6 Run time model RQ0606_001 6.6 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.6 shall apply. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.5 Primary Platform | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.5.1 Hardware Platform | Reference: ETSI TS 103 666-2 [10], clause 7.1. Req.ID Clause Description 7.1.1 Architecture RQ0701_001 7.1.1 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.1 shall apply with the exception that the presence of the SoC shown in figure 3-1 of [15] is mandatory. RQ0701_002 7.1.1 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.1 shall apply with the exception that the iSSP shall contain an autonomous and independent clock system. RQ0701_003 7.1.1 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.1 shall apply with the exception that the iSSP shall contain communication functions. RQ0701_004 7.1.1 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.1 shall apply with the exception that the iSSP may contain the data protection hardware function. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 29 Release 15 Req.ID Clause Description 7.1.3 Security functions RQ0701_005 7.1.3.1 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.4.1 SREQ19 shall apply. RQ0701_006 7.1.3.2 The Primary Platform shall provide a Memory Management Function (MMF) to avoid dependency of the Secondary Platform Bundle design with respect to the execution memory addressing. RQ0701_007 7.1.3.2 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clauses 3.2.2 and 3.5 shall apply. RQ0701_008 7.1.3.3 The hardware platform shall provide a hardware function for protecting its long term keys as defined in GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.4.3. RQ0701_009 7.1.3.3 The key protection function shall perform key derivation, as specified in NIST 800-108 [32], with robustness of the PRF equivalent to or greater than HMAC-SHA- 256 as defined in IETF RFC 4868 [20] or CMAC as defined in NIST SP 800-38B [33]. RQ0701_010 7.1.3.3 The long-term seed value shall be accessible only by the hardware platform. The probability that two distinct hardware platforms have the same long term seed shall be negligible. RQ0701_011 7.1.3.3 The hardware platform shall provide a data path for the key protection function output. RQ0701_012 7.1.3.3 The key protection function output shall be made available for the data protection hardware function described in ETSI TS 103 666-2 [10] clause 7.1.3.4, if that clause is supported, or to the cryptographic functions described in ETSI TS 103 666-2 [10] clause 7.1.7. RQ0701_013 7.1.3.4 The support of a hardware function performing the encryption to export software and data outside the iSSP shall only be accessible by the low-level Operating System in the Primary Platform. If this hardware function is supported, the provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.4.2 shall apply. RQ0701_014 7.1.3.4 For the purpose of storing and verifying software and data outside the iSSP only keys provided by the key protection function shall be used. If this hardware function is supported, the provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.4.2 shall apply. RQ0701_015 7.1.3.5 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.2.6 shall apply. RQ0701_016 7.1.3.6 The hardware platform shall protect against the disclosure of keys managed by the Primary Platform, when using test functions of the SoC or test equipment. RQ0701_017 7.1.3.5 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.7 shall apply. RQ0701_018 7.1.3.8 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.4.4 shall apply. 7.1.4 Memories RQ0701_019 7.1.4.1 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.2.3 shall apply. RQ0701_020 7.1.4.1 The Primary Platform shall provide the Secondary Platform with direct memory-mapped access to the NVM, whether the NVM is integrated in the iSSP (iNVM) or accessed remotely (rNVM). RQ0701_021 7.1.4.2 The Primary Platform shall provide the Secondary Platform with direct memory-mapped access to the volatile memory, whether the memory is integrated in the iSSP (iRAM) or accessed remotely (rRAM). 7.1.7 Cryptographic functions RQ0701_022 7.1.7 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.2.7 shall apply. 7.1.8 Clock RQ0701_023 7.1.8 The iSSP shall embed an autonomous and independent clock system in conformance with the Protection Profile BSI-CC-PP-0084-2014 [2]. RQ0701_024 7.1.8 The provisions of ETSI TS 103 666-1 [9], clause 6.3 shall apply. 7.1.9 SSP internal interconnect RQ0701_025 7.1.9 All elements contained in the iSSP shall only be physically connected to other elements in the iSSP, except as specified in clause 7.1.5 of ETSI TS 103 666-1 [9]. 7.1.10 Secure CPU RQ0701_026 7.1.10 The hardware platform shall contain one or more dedicated CPUs, which are inside the iSSP and separated from the rest of the SoC. RQ0701_027 7.1.10 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.2.1 shall apply. RQ0701_028 7.1.10 The CPU(s) shall be based at least on a 32-bit architecture. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 30 Release 15 Req.ID Clause Description 7.1.11 Random Number Generator RQ0701_029 7.1.11 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 3.2.8 shall apply. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.5.2 Low-level Operating System | Reference: ETSI TS 103 666-2 [10], clause 7.2. Req.ID Clause Description 7.2.1 Introduction RQ0702_001 7.2.1 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.8 (without its subclauses) shall apply. 7.2.2 Kernel objects RQ0702_002 7.2.2 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.8.1 shall apply. 7.2.3 Global requirements and mandatory Access Control rules RQ0702_003 7.2.3 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.8.2 shall apply. 7.2.4 Process states diagram RQ0702_004 7.2.4 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.8.3 shall apply. 7.2.5 Definition of the process states RQ0702_005 7.2.5 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.8.4 shall apply. 7.2.6 Mandatory access control RQ0702_006 7.2.6 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.11 shall apply. RQ0702_007 7.2.6 The low-level operating system shall only have non-shareable memory regions. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.5.3 Services | Reference: ETSI TS 103 666-2 [10], clause 7.3. Req.ID Clause Description 7.3.1 Secondary Platform Bundle Loader RQ0703_001 7.3.1.1 The Primary Platform shall support a Secondary Platform Bundle Loader as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13] with the exception that the OFL ARP state shall be UNLOCKED. RQ0703_002 7.3.1.1 The Secondary Platform Bundle Loader shall be a system Secondary Platform Bundle and shall support the requirements defined in the augmented package loader 2 in BSI-CC-PP-0084-2014 [2]. RQ0703_003 7.3.1.2 The Secondary Platform Bundle Loader shall implement at least the registry entries of the OFL service gate as listed in Table 7.1: Registry entry in the OFL Service Gate of ETSI TS 103 666-2 [10]. RQ0703_004 7.3.1.2 The Secondary Platform Bundle Loader shall implement the registry entries of the OFL service gate as listed in Table 7.2: Additional registry entry in the OFL Service Gate of ETSI TS 103 666-2 [10]. RQ0703_005 7.3.1.2 If the iSSP contains or is intended to contain at least one Telecom Secondary Platform Bundle, TELECOM_CAPABILITY shall be set at the time of manufacturing. It shall contain the maximum number of distinct concurrent 3GPP network registrations based on different subscriber identifiers, supported by the terminal. RQ0703_006 7.3.1.3 The Secondary Platform Bundle Loader shall support the commands defined in GlobalPlatform VPP - OFL VNP Extension [13]. RQ0703_007 7.3.1.3 The Secondary Platform Bundle Loader shall support the commands listed in Table 7.3: Additional commands supported by the OFL Service Gate of ETSI TS 103 666-2 [10]. RQ0703_008 7.3.1.4 The Secondary Platform Bundle Loader shall support the responses defined in GlobalPlatform VPP - OFL VNP Extension [13]. RQ0703_009 7.3.1.4 The OFL service gate shall support the responses listed in Table 7.4: Additional responses supported by the OFL Service Gate of ETSI TS 103 666-2 [10]. • eSPBL_E_NO_CI_FOR_SPBM_VERIFICATION ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 31 Release 15 Req.ID Clause Description RQ0703_010 7.3.1.4 The OFL service gate shall support the responses listed in Table 7.4: Additional responses supported by the OFL Service Gate of ETSI TS 103 666-2 [10]. • eSPBL_E_NO_CI_FOR_SPBL_VERIFICATION RQ0703_011 7.3.1.4 The OFL service gate shall support the responses listed in Table 7.4: Additional responses supported by the OFL Service Gate of ETSI TS 103 666-2 [10]. • eSPBL_E_NO_CI_FOR_KEYAGREEMENT RQ0703_012 7.3.1.4 The OFL service gate shall support the responses listed in Table 7.4: Additional responses supported by the OFL Service Gate of ETSI TS 103 666-2 [10]. • eSPBL_E_NO_SUPPORTED_CRYPTO RQ0703_013 7.3.1.4 The OFL service gate shall support the responses listed in Table 7.4: Additional responses supported by the OFL Service Gate of ETSI TS 103 666-2 [10]. • eSPBL_E_INVALID_SPBM_CERT RQ0703_014 7.3.1.4 The OFL service gate shall support the responses listed in Table 7.4: Additional responses supported by the OFL Service Gate of ETSI TS 103 666-2 [10]. • eSPBL_E_EXCEED_TELECOM_CAPABILITY RQ0703_015 7.3.1.5 The Secondary Platform Bundle Loader shall manage firmware sessions as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13], section 2.2.1 as per the Secondary Platform Bundles installed in the iSSP. RQ0703_016 7.3.1.5 The Secondary Platform Bundle Loader shall manage the notification counter value as additional parameter of the firmware session. The 4 bytes integer value which is used when the Secondary Platform Bundle Loader generates the notification token as defined in clause 12.6.2.8 of ETSI TS 103 666-2 [10]. The notification counter of the Secondary Platform Bundle shall be pre-incremented by one by Secondary Platform Bundle Loader at each generation of a token. The initial value of the counter is '1'. RQ0703_-017 7.3.1.5 The Secondary Platform Bundle Loader shall manage the Secondary Platform Bundle private identifier as defined in clause 9.4.5 of ETSI TS 103 666-2 [10]. RQ0703_018 7.3.1.5 The Secondary Platform Bundle Loader shall manage the SPB metadata as defined in clause 12.6.2.6 of ETSI TS 103 666-2 [10] for the Secondary Platform Bundle container. When the firmware session is created, the SPB metadata contained in the bound SPB image shall be stored. RQ0703_019 7.3.1.5 The Secondary Platform Bundle Loader shall manage the SPB state as additional parameter of the firmware session providing the current state of the Secondary Platform Bundle. The value shall be one of 'Disabled (0)' and 'Enabled (1)'. 7.3.2 Communication service RQ0703_020 7.3.2 The Primary Platform shall provide communication service for the use of the Secondary Platform Bundle to communicate with entities outside the iSSP. The interface is defined in clause 8.2. 7.3.3 Management service RQ0703_021 7.3.3 The Primary Platform shall provide management service for the exclusive use of the Secondary Platform Bundle Loader. RQ0703_022 7.3.3 The management service provides the interface to manage: • the life cycle of a Secondary Platform Bundle. RQ0703_023 7.3.3 The management service provides the interface to manage: • the installation and management of a Secondary Platform Bundle by a Secondary Platform Bundle Loader. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.