hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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 ha... |
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 M... |
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 ... |
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 re... |
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... |
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... |
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 an... |
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... |
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]... |
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> ... |
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 b... |
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 th... |
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 ... |
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 fin... |
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... |
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 Clou... |
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 se... |
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 ... |
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.; • out... |
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 ar... |
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 in... |
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 ac... |
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... |
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 generatio... |
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 no... |
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 Distributi... |
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 "flex... |
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... |
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) ... |
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 ... |
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 ... |
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 organiz... |
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 betwe... |
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... |
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 ... |
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 equipmen... |
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. ... |
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 w... |
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: De... |
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 de... |
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 d... |
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... |
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... |
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 Loade... |
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 ... |
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... |
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-... |
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 ... |
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)* ') '... |
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 Sec... |
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... |
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 th... |
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 T... |
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 is... |
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 verifica... |
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 SPB... |
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-S... |
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... |
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_43... |
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 th... |
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... |
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 ... |
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 provisio... |
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 Int... |
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... |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.5.4 Minimum level of interoperability | Reference: ETSI TS 103 666-2 [10], clause 7.4. Req.ID Clause Description RQ0704_001 7.4 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 7 and its subclauses shall apply. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 32 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.5.5 Primary Platform identification | Reference: ETSI TS 103 666-2 [10], clause 7.5. Req.ID Clause Description RQ0705_001 7.5 The Primary Platform instance is identified by a Primary Platform identifier. The Primary Platform identifier is a sequence of 32 characters, divided in 8 groups of 4 characters each, with a dash between each group. RQ0705_002 7.5 T... |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.5.6 Provisioning of Primary Platform software | Reference: ETSI TS 103 666-2 [10], clause 7.6. Req.ID Clause Description RQ0706_001 7.6 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.7 REQ85 shall apply. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.