hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.7.2 Forwarder operations | If a GAGH receives a LS Request packet and the Request GN_ADDR field in the LS Request header does not match its GN_ADDR, the GAGH shall handle the packet according to the packet handling procedure for TSB (clause 10.3.9.3), except step 7 for passing the payload of the GN-PDU to the upper protocol entity. If a GAGH rec... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.7.3 Destination operations | On reception of a LS Request packet, the GAGH shall check the Request GN_ADDR field. If this MID field matches the MID field of its GN_ADDR, the GAGH shall execute the following operations: 1) Basic Header processing (clause 10.3.3); 2) Common Header processing (clause 10.3.5); 3) execute DPD as specified in clause A.2... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.8 GUC packet handling | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.8.1 General | This clause specifies the operations of a GAGH to handle a GUC packet. The following clauses define the operations of the source, forwarder and destination. GeoUnicast forwarding applies the algorithm selected by the setting of the value in the GN protocol constant itsGnNonAreaForwardingAlgorithm and specified in annex... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.8.2 Source operations | On reception of a service primitive TRANSP_CORE.request with a Packet transport type parameter set to GeoUnicast, the source shall execute the following operations: 1) create a GN-PDU with the T/GN6-SDU as payload and a GUC packet header (clause 9.8.2): a) set the fields of the Basic Header (clause 10.3.2); b) set the ... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.8.3 Forwarder operations | On reception of a GUC packet, a GAGH shall check the GN_ADDR field in the DE PV of the GUC packet header. If this address does not match its GN_ADDR, the GAGH shall execute the following operations: 1) Basic Header processing (clause 10.3.3); 2) Common Header processing (clause 10.3.5); 3) if the GN protocol constant i... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.8.4 Destination operations | On reception of a GUC packet, the GeoAdhoc router shall check the GN_ADDR field in the DE PV of the GUC packet header. If this address matches its GN_ADDR, the GeoAdhoc router shall execute the following operations: 1) Basic Header processing (clause 10.3.3); 2) Common Header processing (clause 10.3.5); ETSI ETSI TS 10... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.9 TSB packet handling | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.9.1 General | This clause specifies the operations of a GAGH to handle a TSB packet. The following clauses define the operations of the source and forwarder/receiver. ETSI ETSI TS 103 836-4-1 V2.1.1 (2022-11) 55 NOTE: In TSB, a forwarder is also always a receiver. Therefore, the roles are not distinguished. |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.9.2 Source operations | On reception of a service primitive TRANSP_CORE.request with a Packet transport type parameter set to TSB, the source shall execute the following operations: 1) create a GN-PDU with the T/GN6-SDU as payload and a TSB packet header (clause 9.8.3): a) set the fields of the Basic Header (clause 10.3.2); b) set the fields ... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.9.3 Forwarder and receiver operations | On reception of a TSB packet, the GAGH shall execute the following operations: 1) Basic Header processing (clause 10.3.3); 2) Common Header processing (clause 10.3.5); 3) execute DPD as specified in clause A.2; if the TSB packet is a duplicate, discard the packet and omit the execution of further steps; 4) execute DAD ... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.10.1 General | This clause specifies the operations of a GAGH to handle a SHB packet. The following clauses define the operations of the source and receiver. NOTE: SHB packets are not forwarded. Therefore, no forwarder operations are specified. |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.10.2 Source operations | On reception of a service primitive TRANSP_CORE.request with a Packet transport type parameter set to SHB, the source shall execute the following operations: 1) create a GN-PDU with the T/GN6-SDU as payload and a SHB packet header (clause 9.8.4): a) set the fields of the Basic Header (clause 10.3.2); b) set the fields ... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.10.3 Receiver operations | On reception of a SHB packet, the GAGH shall execute the following operations: 1) Basic Header processing (clause 10.3.3); 2) Common Header processing (clause 10.3.5); 3) execute DAD as specified in clause 10.2.1.5; 4) update the PV in the SO LocTE with the SO PV fields of the SHB Extended Header (clause C.2); 5) updat... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.11.1 General | This clause specifies the operations of a GAGH to handle a GBC packet. The following clauses define the operations of the source and forwarder/receiver. NOTE: In GBC, a forwarder inside the target area acts also always as a receiver. Therefore, the roles are not distinguished. |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.11.2 Source operations | On reception of a service primitive TRANSP_CORE.request with a Packet transport type parameter set to GeoBroadcast, the source shall execute the following operations: 1) create a GN-PDU with the T/GN6-SDU as payload and a GBC packet header (clause 9.8.5): a) set the fields of the Basic Header (clause 10.3.2); b) set th... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.11.3 Forwarder and receiver operations | On reception of a GBC packet, the GAGH shall execute the following operations: 1) Basic Header processing (clause 10.3.3); 2) Common Header processing (clause 10.3.5); 3) determine function F(x,y) as specified in ETSI TS 103 899 [1] clause 5: a) if ( ) 0 , < y x F (GeoAdhoc router is outside the geographical area) and ... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.12.1 General | This clause specifies the operations of a GAGH to handle a GAC packet. The following clauses define the operations of the source and forwarder/receiver. The operations for GAC packet handling are similar to those for GBC packet. |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.12.2 Source operations | The operations of the source of a GAC packet are identical with the source of a GBC packet as specified in clause 10.3.11.2. NOTE: The procedure ensures that the GAC packet is sent at least once when the GeoAdhoc router is inside or at the border of the geographical area. |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.12.3 Forwarder and receiver operations | On reception of a GAC packet, the GAGH shall execute the following operations: 1) Basic Header processing (clause 10.3.3); 2) Common Header processing (clause 10.3.5); 3) execute DPD as specified in clause A.2; if the GAC packet is a duplicate, discard the packet and omit the execution of further steps; 4) execute DAD ... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.4 MCO management | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.4.1 Overview | The Networking & Transport layer MCO functionalities are all part of the MCO_NET service. MCO_NET has interfaces with the GN Core, GN ALI group handlers, and the Facilities and Access layer functionalities. The entities realizing MCO_NET required functionalities are (see figure 23): • MCO Parameters Updates (MPU) (clau... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.4.2 MCO Parameters Updates (MPU) | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.4.2.1 Overview | Each ALI group at the Access layer is associated with a GAGH at the Networking & Transport layer. The state of a GAGH depends on the state of its associated ALI group (see ETSI TS 103 695 [i.7]). MCO_NET shall support MCO parameters update requests (e.g. to update an ALI group status) from the Facilities layer and shal... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.4.2.2 GAGH state | A GAGH shall maintain a state machine with the following states: • Active: an active GAGH performs GN protocol operations and maintains GN data structures and buffers. A GAGH is active as long its associated ALI group is in an active state. • Inactive: an inactive GAGH does not perform GN protocol operations but mainta... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.4.2.3 GAGH state update | The MCO_NET shall provide the possibility to the Facilities layer to request MCO parameters updates at the lower layers and to receive MCO parameter updates from the lower layers. When receiving a request to configure MCO parameters from the Facilities layer, the MPU shall forward the request to the Access layer. This ... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.4.3 Network Updates (NU) | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.4.3.1 Overview | To efficiently allocate resources at the Facilities layer, the MCO_NET shall provide network updates to the Facilities layer. EXAMPLE: The network updates may contain the CLRs perceived locally and by neighboring stations. The information contained in the network update shall be media-independent. ETSI ETSI TS 103 836-... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.4.3.2 Access layer update | When receiving an Access layer update from the NET_ACC_MMT interface, the NU entity shall perform the following operations: 1) Send the CLR to the associated GAGH via the GAGH_MCO interface (annex M) when needed. 2) In case an Access Layer notification is indicated, the NU entity forwards the notification to the Facili... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.4.3.3 Network updates to the Facilities layer | To provide better knowledge of the current communication capabilities, the NU entity collects network-related information from the GAGHs and the Access layer. The network update provided by the NU entity to the Facilities layer via the MCO_FAC_NET_MMT interface shall be media-independent. NOTE: To provide media-indepen... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.4.4 ALI Request Handler (ARH) | When a packet dissemination is requested by the transport layer protocol entities, GN Core shall perform the following operations: 1) Check that the AliID indicated for the packet is associated to an active GAGH. 2) If the AliID is associated to an active GAGH, the GN Core sends the packet to the associated GAGH with t... |
ee305dc1e014895a09ec7878b1e84a29 | 103 898 | 1 Scope | The present document is the baseline for the definition of the Release 2 ITS communications architecture. |
ee305dc1e014895a09ec7878b1e84a29 | 103 898 | 2 References | |
ee305dc1e014895a09ec7878b1e84a29 | 103 898 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
ee305dc1e014895a09ec7878b1e84a29 | 103 898 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
ee305dc1e014895a09ec7878b1e84a29 | 103 898 | 3 Definition of terms, symbols and abbreviations | |
ee305dc1e014895a09ec7878b1e84a29 | 103 898 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 302 665 [1] apply. |
ee305dc1e014895a09ec7878b1e84a29 | 103 898 | 3.2 Symbols | Void. |
ee305dc1e014895a09ec7878b1e84a29 | 103 898 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI EN 302 665 [1] apply. ETSI ETSI TS 103 898 V2.0.0 (2022-07) 6 4 Use of references and numbering in Release 2 specifications TC ITS specifications are developed in Releases and each Release needs to be self-consistent. The following rules apply: •... |
ee305dc1e014895a09ec7878b1e84a29 | 103 898 | 5 Normative Provisions | ETSI EN 302 665 [1] shall apply altogether. ETSI ETSI TS 103 898 V2.0.0 (2022-07) 7 History Document history V2.0.0 July 2022 Publication |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 1 Scope | The present document specifies a conformance assessment methodology for Home Gateway devices of their security risk mitigation and privacy protection measures against ETSI TS 103 848 [1], addressing the mandatory provisions as well as conditions and complements of the standard by defining test cases and assessment crit... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 2 References | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 3 Definition of terms, symbols and abbreviations | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 848 [1] apply. ETSI ETSI TS 103 928 V1.3.1 (2025-03) 12 |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 3.2 Symbols | Void. |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 848 [1] and ETSI TS 103 701 [2] apply. |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4 Conformance assessment methodology | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.1 Overview and document structure | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.1.0 General overview of the present document | Clause 4.2 describes the relevant roles and objects for the conformance assessment procedure. Clause 4.3 describes the assessment procedure. Clause 4.4 describes how to declare the conformity of the Home Gateway device to the provisions of ETSI TS 103 848 [1] in the Implementation Conformance Statement (ICS). Clause 4.... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.1.1 Handling of test groups | Each provision in ETSI EN 303 645 [i.1] corresponds to a test group in ETSI TS 103 701 [2]. ETSI TS 103 848 [1] contains modified and/or added provisions based on ETSI EN 303 645 [i.1], which correspond respectively to a test group in the present document. ETSI TS 103 645 Technical Specification “Cyber Security for Con... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.1.2 Handling of IXIT entries | The following three bullet points explain how IXIT entries are handled in the present document based on the modified or added provisions in ETSI TS 103 848 [1]: • An existing IXIT entry (as defined in ETSI TS 103 701 [2]) is modified and added to an existing IXIT table or list from ETSI TS 103 701 [2]. • A new IXIT ent... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.1.3 Naming conventions | The test group names within the TSOs in the present document are aligned with the provision names in ETSI TS 103 848 [1]. New IXIT entries defined in the present document are labelled with "(added)". |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.2 Roles and objects | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.2.1 Device Under Test (DUT) | The text in clause 4.2.1 of ETSI TS 103 701 [2] also applies in the present document. |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.2.2 Supplier Organization (SO) | The text in clause 4.2.2 of ETSI TS 103 701 [2] also applies in the present document except for the fact that the SO requests a specific DUT to be tested against the provisions of ETSI TS 103 848 [1]. |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.2.3 Test Laboratory (TL) | The text in clause 4.2.3 of ETSI TS 103 701 [2] also applies in the present document except for the fact that the reference to ETSI EN 303 645 [i.1] is to be replaced by the reference to ETSI TS 103 848 [1]. |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.3 Assessment procedure | The text in clause 4.3 of ETSI TS 103 701 [2] also applies in the present document except for the fact that the reference to ETSI EN 303 645 [i.1] is to be replaced by the reference to ETSI TS 103 848 [1]. In addition, the ICS form is in Annex B of ETSI TS 103 848 [1] and the matching table listing required IXIT entrie... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.4 Implementation Conformance Statement (ICS) | The text in clause 4.4 of ETSI TS 103 701 [2] also applies in the present document except for the fact that the reference to ETSI EN 303 645 [i.1] is to be replaced by the reference to ETSI TS 103 848 [1]. In addition, the ICS form is in Annex B of ETSI TS 103 848 [1]. |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.5 Implementation eXtra Information for Testing (IXIT) | The text in clause 4.5 of ETSI TS 103 701 [2] also applies in the present document. The matching table listing required IXIT entries for each provision (see Table B.1) is in Annex B of the present document. |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.6 Assignment of verdicts | The text in clause 4.6 of ETSI TS 103 701 [2] also applies in the present document. |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.7 Usage of external evidences | The text in clause 4.7 of ETSI TS 103 701 [2] also applies in the present document. |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 4.8 Assessment scheme amendments | The text in clause 4.8 of ETSI TS 103 701 [2] also applies in the present document except for the fact that the reference to ETSI EN 303 645 [i.1] is to be replaced by the reference to ETSI TS 103 848 [1] and the reference to ETSI TS 103 701 [2] is to be replaced by the present document, respectively. 5 Test groups for... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.0 TSO 4: Reporting implementation | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.0.1 Test group HG 4-1 (extended) | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.0.1.0 Test group objective | The present Test group HG 4-1 (extended) has the same objective as the Test group 4-1 in ETSI TS 103 701 [2]. The only difference is given by the fact that the present Test group HG 4-1 (extended) addresses the provision 4-1 (extended) of ETSI TS 103 848 [1] instead of the provision 4-1 of ETSI EN 303 645 [i.1]. |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.0.1.1 Test case HG 4-1-1 (conceptual) | Test purpose The purpose of this test case is the conceptual assessment of the justifications for recommendations that are considered to be not applicable for or not fulfilled by the DUT. Test units a) The TL shall check whether a justification is given in the ICS for each recommendation that is considered to be not ap... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1 TSO 5.1: No universal default passwords | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.1 Test group HG 5.1-1 (extended) | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.1.0 Test group objective | The test group addresses the provision HG 5.1-1 (Extended). This test group addresses the Wi-Fi® or administrator passwords preconfigured in factory default. |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.1.1 Test case HG 5.1-1 (extended)-1 (conceptual) | Test purpose The purpose of this test case is the conceptual assessment of the uniqueness of preconfigured passwords in factory default state. Test units a) For each authentication mechanism concerning Wi-Fi® or administrator (i.e. an administrator that performs management actions on the HG) in IXIT 1-AuthMech using fa... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.1.2 Test case HG 5.1-1 (extended)-2 (functional) | Test purpose The purpose of this test case is the functional assessment of the uniqueness of preconfigured passwords in factory default state. Test units a) For each authentication mechanism concerning Wi-Fi® or administrator (i.e. an administrator that performs management actions on the HG) in IXIT 1-AuthMech using pr... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.2 Test group HG 5.1-4 (extended)-a | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.2.0 Test group objective | The present Test group HG 5.1-4 (extended)-a has the same content as the Test group 5.1-4 in ETSI TS 103 701 [2]. The only difference is given by the fact that the present Test group HG 5.1-4 (extended)-a in combination with Test group HG 5.1-4 (extended)-b and Test group HG 5.1-4 (extended)-c addresses the provision H... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.2.1 Test case HG 5.1-4 (extended)-a-1 (conceptual) | Test purpose The purpose of this test case is the conceptual assessment of the capability to set the password in Wi-Fi® based on authentication mechanisms. Test units a) The TL shall assess whether the authentication mechanism in IXIT 1-AuthMech where "Description" indicates that the mechanism is used for user authenti... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.3 Test group HG 5.1-4 (extended)-b | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.3.0 Test group objective | The present Test group HG 5.1-4 (extended)-b has the same content as the Test group 5.1-4 in ETSI TS 103 701 [2]. The only difference is given by the fact that the present Test group HG 5.1-4 (extended)-b in combination with Test group HG 5.1-4 (extended)-a and Test group HG 5.1-4 (extended)-c addresses the provision H... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.3.1 Test case HG 5.1-4 (extended)-b-1 (conceptual) | Test purpose The purpose of this test case is the conceptual assessment of the mechanisms to change the Wi-Fi® password. Test units a) The TL shall assess whether the authentication mechanism in IXIT 1-AuthMech where "Description" indicates that the mechanism is used for user authentication with Wi-Fi®, the resource of... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.3.2 Test case HG 5.1-4 (extended)-b-2 (functional) | Test purpose The purpose of this test case is the functional assessment of each mechanism to change the Wi-Fi® password. Test units a) The TL shall perform a change of each Wi-Fi® password for the user authentication mechanism with Wi-Fi® in IXIT 1-AuthMech as documented in the resource from "Documentation of Change Me... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.4 Test group HG 5.1-4 (extended)-c | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.4.0 Test group objective | The present Test group HG 5.1-4 (extended)-c has the same content as the Test group 5.1-4 in ETSI TS 103 701 [2]. The only difference is given by the fact that the present Test group HG 5.1-4 (extended)-c in combination with Test group HG 5.1-4 (extended)-a and Test group HG 5.1-4 (extended)-b addresses the provision H... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.4.1 Test case HG 5.1-4 (extended)-c-1 (conceptual) | Test purpose The purpose of this test case is the conceptual assessment of each mechanism to change the administrator password. Test units a) The TL shall assess whether IXIT 1-AuthMech contains the description of the authentication mechanism used for administrator authentication according to the "Description" entry of... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.4.2 Test case HG 5.1-4 (extended)-c-2 (functional) | Test purpose The purpose of this test case is the functional assessment of each mechanism to change the administrator password. Test units a) The TL shall perform a change of the administrator password for each administrator authentication mechanism in IXIT 1-AuthMech as documented in the resource from "Documentation o... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.1.5 Test group HG 5.1-5 (refined) | The present Test group HG 5.1-5 (refined) has the same content as the Test group 5.1-5 in ETSI TS 103 701 [2]. The only difference is given by the fact that the present Test group HG 5.1-5 (refined) addresses the mandatory provision HG 5.1-5 (refined) of ETSI TS 103 848 [1] instead of the conditional provision 5.1-5 of... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2 TSO 5.3: Keep software updated | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.1 Test group HG 5.3-1 (extended)-a | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.1.0 Test group objective | The test group addresses the provision HG 5.3-1 (extended)-a. This test group addresses the components that are not updatable. |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.1.1 Test case HG 5.3-1 (extended)-a-1 (conceptual) | Test purpose The purpose of this test case is the conceptual assessment of components that are not updateable. Test units a) For each software component in IXIT 6-SoftComp with an empty list in "Update Mechanism", the TL shall assess whether it has been noted and indicated in the resource from "Publication of Non-Updat... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.2 Test group HG 5.3-1 (extended)-b | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.2.0 Test group objective | The test group addresses the provision HG 5.3-1 (extended)-b. This test group addresses the software version control for HG update. |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.2.1 Test case HG 5.3-1 (extended)-b-1 (conceptual) | Test purpose The purpose of this test case is the conceptual assessment of the software version control for HG update. Test units a) The TL shall assess that for each operation of the update mechanism in IXIT 7-UpdMech, the software version control in the update mechanism verifies that the version of a provided softwar... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.2.2 Test case HG 5.3-1 (extended)-b-2 (functional) | Test purpose The purpose of this test case is the functional assessment of the version control for HG update. Test units a) For each update mechanism in IXIT 7-UpdMech, the TL shall perform an update with an invalid software version, but with a correct signature in order to test the rejection of invalid versions based ... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.3 Test group HG 5.3-2 (refined) | The present Test group HG 5.3-2 (refined) has the same content as the Test group 5.3-2 in ETSI TS 103 701 [2]. The only difference is that the present Test group HG 5.3-2 (refined) addresses the mandatory provision HG 5.3-2 (refined) of ETSI TS 103 848 [1] instead of the conditional provision 5.3-2 of ETSI EN 303 645 [... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.4 Test group HG 5.3-5 (refined) | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.4.1 Test group objective | The test group addresses the provision HG 5.3-5 (refined). The focus of the provision is on the ability to check for security updates for the software of the DUT. This case is given if the check for updates is activated by default and each software component is updatable with at least one update mechanism checking for ... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.4.2 Test case HG 5.3-5 (refined)-1 (conceptual) | Test purpose The purpose of this test case is the conceptual assessment of the update mechanisms concerning the checks for available security updates after initialization and then at least daily and its activation by default. Test units a) For each software component in IXIT 6-SoftComp, the TL shall assess whether at l... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.4.3 Test case HG 5.3-5 (refined)-2 (functional) | Test purpose The purpose of this test case is the functional assessment of the update mechanisms concerning the checks for available security updates after initialization and then at least daily and its activation by default. Test units a) For each update mechanism in IXIT 7-UpdMech, which is referenced by IXIT 6-SoftC... |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.5 Test group HG 5.3-6 (extended) | |
15d92f34f6eb50979e3fbca82fa8ff70 | 103 928 | 5.2.5.1 Test group objective | The test group addresses the provision HG 5.3-6 (extended). This test group addresses the default state of the update functionality and the ability to configure it. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.