hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 6.1 General | The execution of a CABCA cycle involves several distinct phases, driven by specific triggers and resulting in a documented conformity status. The overall process flow, including variations based on the assessment mode, is visualised in Figure 6.1‑1. ETSI ETSI TS 104 008 V1.1.1 (2026-01) 19 An assessment cycle can be co... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 6.2 Process Variations Based on CABCA Modes | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 6.2.1 Self-Assessment Path | In the Self-Assessment Path, the AI system provider acts as the auditing party to internally validate conformity. The primary input for this path shall be the Assessment Report. As shown in Figure 6.2-1, the AI system provider (acting as the auditing party) shall directly proceed to "Provider Reviews Results/Report". B... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 6.2.2 Third-Party Assessment Path | The Third-Party Assessment Path involves an independent external body and uses the Assessment Report as its primary input. The process, shown in Figure 6.2-2, begins when the AI system provider shall execute the step "Provider Makes Results/Report Available to Third-Party". The external body then shall proceed to "Thir... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 6.2.3 Certification Path | CABCA facilitates the optional Certification Path by providing the continuous stream of evidence generated through either the Self-Assessment or Third-Party Assessment modes. As detailed in Figure 6.2-3, the final Assessment Report from one of these preceding paths shall serve as the auditable proof of ongoing complian... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 6.3 Roles in Process Execution | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 6.3.1 General | The CABCA process execution shall involve distinct roles with specific responsibilities as defined in clauses 6.3.2 to 6.3.4. The allocation of these roles shall be dependent on the CABCA mode (Self-assessment, Third-party assessment, or Certification support) being implemented. |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 6.3.2 Auditee | The entity acting as the Auditee, typically the AI System Provider, shall be responsible for the AI system undergoing CABCA. Core Responsibilities (Applicable in all Modes): a) The Auditee shall define the scope of the CABCA implementation, including the specific AI system(s) and the applicable conformity specification... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 6.3.3 Auditing Party | The entity acting as the Auditing Party shall be responsible for conducting the assessment of the AI system's conformity. The Auditing Party shall be the Auditee itself in Self-Assessment mode, or an independent external body in Third-Party Assessment or Certification modes: a) The Auditing Party shall conduct assessme... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 6.3.4 Entity for Attestation of Conformity | The entity responsible for attesting to the conformity status of the AI system shall provide the official conformity statement to stakeholders: a) The Entity for Attestation of Conformity shall communicate the confirmed conformity status to relevant stakeholders. b) In Self-Assessment mode, the Auditee shall act as the... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 7 Scoping (Identification of Conformity Specifications) | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 7.1 General | Before the CABCA methodology can be operationalized, an organization should conduct a foundational Scoping process. This process involves the systematic identification, selection, and compilation of all relevant requirements that apply to a specific AI system. This activity is a fundamental practice in any robust compl... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 7.2.1 Sources of Conformity Specifications | The Scoping process relies on identifying and selecting appropriate conformity specifications from various sources. This clause first identifies the diverse sources from which these specifications can originate and then details the essential criteria a specification should meet to be selected for inclusion in the final... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 7.2.2 Criteria for Integrating Conformity Specifications in CABCA | For a source document to be included in the final Conformity Specification and be effectively used by the CABCA framework, it should meet the following minimum requirements (criteria): • Operationalizability: The conformity specification, which represents the quality objective to be achieved, for example an essential r... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1 Process of Operationalization | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1.1 General | Operationalization is the cornerstone of the CABCA methodology. It is the process that takes the "Conformity Specification", as defined in the Scoping phase (see clause 7) and transforms its abstract, high-level requirements into concrete, measurable, and auditable requirements and metrics for a specific AI system and ... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1.2 Identification of Quality Dimensions | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1.2.1 Requirements for Defining Quality Dimensions | Quality dimensions are the foundation of the operationalization process. They define the key aspects of an AI system under which specific requirements should be evaluated to ensure alignment with conformity specifications. These dimensions reflect societal, regulatory, and technical expectations and serve as entry poin... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1.2.2 Criteria for Defining Quality Dimensions | The definition of quality dimensions shall adhere to the following criteria: • Granularity: Quality dimensions shall be defined in a way that supports decomposition into manageable subcomponents for targeted assessment. • Suitability: Quality dimensions shall be adaptable to evolving technologies, application contexts,... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1.3 Identification of Risks | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1.3.1 Requirements for Defining Risks | Risks linked to each quality dimension need to be documented to contextualize potential harms or non-conformities. This step ensures that all assessments are risk-informed and traceable to their underlying rationale in the conformity specification: • For each identified quality dimension, the operationalization process... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1.3.2 Criteria for Identifying Risks | The identification and documentation of risks shall adhere to the following criteria: • Mitigatability: Risks shall be evaluated based on the ability to implement risk mitigation strategies. Or the risk is accepted, then itis not part of the assessment. • Risk traceability: Each mitigation action shall be demonstrably ... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1.4 Deriving Measurable Compliance Requirements and Metrics | 8.1.4.1 Requirements for Deriving Measurable Compliance Requirements and Metrics To assess risks effectively, concrete and measurable compliance requirements should be derived. These requirements should be directly traceable to risks and quality dimensions, and measurable using well-defined metrics. This formalization ... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1.4.2 Criteria for Deriving Measurable Compliance Requirements | The derivation of measurable compliance requirements shall adhere to the following criteria: • Relevance: Requirements shall be directly relevant to the AI system's intended purpose and application context. • Clarity: Requirements shall be defined in a clear and unambiguous manner to prevent misinterpretation. • Measur... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1.4.3 Criteria for Deriving Metrics | The derivation of metrics shall adhere to the following criteria: • Precision: Metrics shall be defined with sufficient clarity and precision to ensure unambiguous interpretation. • Relevance: Each metric shall be directly and demonstrably related to the requirement and quality dimension being measured. • Unit specific... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1.5 Implementing Measurements | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1.5.1 Requirements for Implementing Measurements | To enable automated and continuous assessment, concrete measurement methods should be defined for each metric. These methods serve as the procedural and technical basis for conformity checks and allow repeatable evaluations across time and system versions: • For each defined metric, the operationalization process shall... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.1.5.2 Criteria for Implementing Measurements | The implementation of measurements shall adhere to the following criteria: • Automation: Measurements shall be implemented with a high degree of tool-based automation to ensure repeatability and efficiency. • Output unit consistency: The output unit of a measurement shall be consistent with the unit defined for the cor... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.2 The Operationalization Specification | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.2.1 General | To address both human and machine processing needs, the Operationalization Specification is captured as a single, structured, machine-readable specification. From this source of truth, a human-readable documentation is rendered to inform stakeholders, while the specification itself is used directly to configure automat... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.2.2 Requirements for the Operationalization Specification | The operationalization specification shall adhere to a defined structure that translates high-level Conformity Specifications into specific documentation items. This structure shall facilitate the creation of actionable, machine-readable records for continuous assessment and auditing by meeting the following requiremen... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 8.2.3 Criteria for the Operationalization Specification | The structuring of the Operationalization Specification shall adhere to the following criteria, which ensure the overall quality and utility of the documentation: a) Transparency: The specification shall clearly outline the process of translating Conformity Specifications into operational steps, thus eliminating ambigu... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 9 Continuous Assessment Process | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 9.1 Continuous Evidence Gathering & Measurement | CABCA is designed to provide an ongoing assessment of AI systems to ensure they meet conformity specifications, quality goals, and manage risks effectively. This clause explains the steps involved in the CABCA assessment, focusing on how the operationalization documentation serves as a configuration file for the assess... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 9.2 Assessment Evidence | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 9.2.1 General | The continuous assessment process within CABCA shall utilize evidence derived from operational outputs, system states and records: a) Relevant operational outputs, system states, and records, along with their pertinent characteristics (information elements), shall be systematically captured and structured to constitute... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 9.2.2 Sources of Evidence During Development and Training | Evidence for the development and training stages of an AI system shall include, as applicable: a) Documentation of Log Files: This shall capture information elements related to system logs, application logs, and audit logs reflecting operational behaviour and interactions during development. b) Documentation of Model W... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 9.2.3 Sources of Evidence During Operation | Evidence for the operational stage of an AI system shall include, as applicable: a) Documentation of Log Files: This shall capture information elements from system, application, and audit logs detailing operational behaviour in a live environment. b) Documentation of Loaded Model Weights: This shall capture information... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 9.3 Persistence of Assessment Results | The results of each CABCA assessment shall be stored persistently for future reference, quality tracking, and for proving compliance in audits. The scope of this persistence shall include: • Measurement results: All metrics, along with their corresponding values, are systematically stored. This includes data on system ... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 9.4 Updating Conformity Status | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 9.4.1 Conformity Status Updates | The outcome of quality assessments in CABCA is a critical component, involving a detailed evaluation of measurement results. These results shall be derived from various artifacts such as log files and model weights, and shall be assessed against predefined values. These values shall be based on expert knowledge and ris... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 9.4.2 Transparency in Reporting and Updates | Transparency is a cornerstone of CABCA, especially in the documentation and communication of assessment outcomes to stakeholders. This process shall entail: • Clear system identification: Including unambiguous references to the AI system name, type, and additional identification details for full traceability. • Provide... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 9.4.3 Effective Communication with Stakeholders | Communication in CABCA is designed to be clear, consistent, and tailored to the needs of various stakeholders. This involves defining specific communication channels and the scope of each, ensuring that stakeholders receive the most relevant and up-to-date information. The frequency and granularity of communication upd... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 9.4.4 Building and Maintaining Stakeholder Trust | CABCA strengthens stakeholder trust by maintaining a steady flow of reliable information about the AI system's compliance status. This is achieved through the regular publication of Assessment Reports and updates on any changes in the conformity status. By ensuring open and clear communication and providing objective e... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 10.1 General | CABCA directly supports the documentation obligations under the EU Artificial Intelligence Act (AI Act) by enabling traceable, evidence-based assessments of AI systems against conformity requirements. It operationalizes continuous conformity monitoring and supports the production of living documentation that reflects t... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 10.2 CABCA Documentation Items | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 10.2.1 General | In line with ETSI TR 104 119 [i.11], documentation items refer to the specific artifacts, workflows, or components of CABCA that require structured and traceable documentation to support transparency, accountability, and regulatory compliance. Importantly, a documentation item is not the document itself, but rather the... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 10.2.2 Conformity Specification | This documentation item, which is the output of the Scoping process (clause 7), shall serve as basis to document the normative and contextual basis for CABCA. Documentation derived from the conformity specification shall include the following information elements: • Sources of requirements: Legal (e.g. EU AI Act), Regu... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 10.2.3 Operationalization Specification | This documentation item shall serve as a basis to document how conformity requirements are translated into measurable quality constructs and embedded into the continuous assurance cycle. Documentation derived from the operationalization specification shall include the following information elements: • Quality dimension... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 10.2.4 Measurement Results and Evidence | This documentation item shall serve as a basis to document the results of assessment activities performed through CABCA's measurement pipeline. It shall include the following information items: • Assessment outputs: Metric results contextualized by time and version. • Interpretation and scoring: Deviation from expectat... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 10.3 Traceability and Consistency | CABCA shall ensure bidirectional traceability throughout the documentation stack: • Results → Metrics → Quality Dimensions → Risks → Conformity Requirements. • All artefacts are version-controlled and machine/human-readable. • Integrity checks support data provenance and auditability. ETSI ETSI TS 104 008 V1.1.1 (2026-... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 10.4 Stakeholder Documentation Profiles | CABCA shall support customized documentation profiles for different stakeholders as mandated by ETSI TR 104 119 [i.11]. Table 10.4-1: Documentation Profiles for different Stakeholders Stakeholder Documentation Items AI Provider (Developer) All documentation items (i.e. conformity specification, operationalization speci... |
941346d7292bbb3cbcd6a2c87ca69d21 | 104 149-2 | 1 Scope | The present document provides the Implementation Conformance Statement (ICS) pro forma for testing Server implementations for compliance to the Mission Critical Services over LTE protocol requirements defined by 3GPP, and in accordance with the relevant guidance given in ISO/IEC 9646-1 [i.3] and ISO/IEC 9646-7 [2]. The... |
941346d7292bbb3cbcd6a2c87ca69d21 | 104 149-2 | 2 References | |
941346d7292bbb3cbcd6a2c87ca69d21 | 104 149-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. Referenced documents which a... |
941346d7292bbb3cbcd6a2c87ca69d21 | 104 149-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. NOTE: While any hyperlinks i... |
941346d7292bbb3cbcd6a2c87ca69d21 | 104 149-2 | 3 Definition of terms, symbols and abbreviations | |
941346d7292bbb3cbcd6a2c87ca69d21 | 104 149-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 121 905 [i.1] (3GPP TR 21.905) and the following apply: NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TR 121 905 [i.1] (3GPP TR 21.905). Moreover, some terms defined in ISO/IEC 9646... |
941346d7292bbb3cbcd6a2c87ca69d21 | 104 149-2 | 3.2 Symbols | Void. |
941346d7292bbb3cbcd6a2c87ca69d21 | 104 149-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 121 905 [i.1] (3GPP TR 21.905) and the following apply: NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in ETSI TR 121 905 [i.1] (3GPP TR 21.905). EUTRA Evolved UMTS ... |
941346d7292bbb3cbcd6a2c87ca69d21 | 104 149-2 | 4 Recommended Test Case Applicability | The applicability of each individual test is identified in Table 4-1 (MCData Server). This is just a recommendation based on the purpose for which the test case was written. The applicability of every test is formally expressed by the use of Boolean expression that are based on parameters (ICS) included in annex A of t... |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 1 Scope | The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) pro forma for the test specification for the IP/ICMP Translation Algorithm as specified in IETF RFC 7915 [1] in compliance with the relevant requirements and in accordance with the rele... |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 2 References | |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 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... |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 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... |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 3 Definition of terms, symbols and abbreviations | |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 3.1 Terms | For the purposes of the present document, the terms given in ISO/IEC 9646-7 [i.2] and IETF RFC 7915 [1] apply. |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 3.2 Symbols | Void. |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [i.1], ISO/IEC 9646-6 [4], ISO/IEC 9646-7 [i.2], IETF RFC 7915 [1] and the following apply: ATM Abstract Test Method ATS Abstract Test Suite CF Configuration GE Generation of ICMPv4/ICMPv6 Error messages ICMP Internet Control Message Pr... |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 4 Abstract Test Method (ATM) | |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 4.1 Introduction | This clause describes the ATM used to test the IP/ICMP Translation Algorithm at the translator. |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 4.2 Test architecture | |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 4.2.1 Test method | Void. |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 4.2.2 Test machine configuration | Following configurations are simplified to highlight tested interface and involved entities. Figure 1: Test configuration CF_XLAT_SIIT |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 5 ATS conventions | |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 5.1 Introduction | The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS. The ATS conventions contain two clauses, the testing conventions an... |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 5.2 Testing conventions | |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 5.2.1 Test cases Preamble and Postamble | As described in the ETSI TS 104 153-2 [3], the test tool is required to emulate both an IPv4 node and an IPv6 node. It must handle traffic conversion in two directions: IPv4-to-IPv6 (T46) and IPv6-to-IPv4 (T64). For that reason, the test case preambles and postambles are named as follows: IUT is an XLAT (example TC_XLA... |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 5.3 Naming conventions | |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 5.3.1 General guidelines | The naming conventions are based on the following underlying principles: • In most cases, identifiers should be prefixed with a short alphabetic string (specified in table 1) indicating the type of TTCN-3 element it represents. • Suffixes should not be used except in those specific cases identified in table 1. • Prefix... |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 5.3.2 Test case grouping | The ATS structure is based on the Test Purposes for the IP/ICMP Translation Algorithm as defined in ETSI TS 104 153-2 [3]. |
a32e74849246f00b60e7850e364e069e | 104 153-3 | 5.3.3 Test case identifiers | The test cases have been divided according to the functionalities into several groups. The test case names are built up according to the following scheme. Table 2: TC identifier naming convention scheme Identifier: <TC>_<scope>_<nn> <tc> = Test Case: fixed to "TC" <interface or protocol> Interface or protocol: stateles... |
4df6e2656e25a6f3246b032b84b99976 | 104 161 | 1 Scope | The present document is a transposition of Recommendation ITU-T Q.4077 [1] without modifications. |
4df6e2656e25a6f3246b032b84b99976 | 104 161 | 2 References | |
4df6e2656e25a6f3246b032b84b99976 | 104 161 | 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... |
4df6e2656e25a6f3246b032b84b99976 | 104 161 | 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... |
4df6e2656e25a6f3246b032b84b99976 | 104 161 | 3 Definition of terms, symbols and abbreviations | |
4df6e2656e25a6f3246b032b84b99976 | 104 161 | 3.1 Terms | For the purposes of the present document, the terms given in Recommendation ITU-T Q.4077 [1] apply. |
4df6e2656e25a6f3246b032b84b99976 | 104 161 | 3.2 Symbols | Void. |
4df6e2656e25a6f3246b032b84b99976 | 104 161 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in Recommendation ITU-T Q.4077 [1] apply. ETSI ETSI TS 104 161 V1.1.1 (2025-12) 6 |
4df6e2656e25a6f3246b032b84b99976 | 104 161 | 4 Endorsement notice | All elements of Recommendation ITU-T Q.4077 [1] apply. Recommendation ITU-T Q.4077 [1] is contained in archive ts_104161v010101p0.zip which accompanies the present document. ETSI ETSI TS 104 161 V1.1.1 (2025-12) 7 History Version Date Status V1.1.1 December 2025 Publication |
666bafb4e85109224934d34b2ddcd853 | 104 164 | 1 Scope | The present document is a transposition of ITU-T Technical Report QSTR-TFR [i.1] without modifications. |
666bafb4e85109224934d34b2ddcd853 | 104 164 | 2 References | |
666bafb4e85109224934d34b2ddcd853 | 104 164 | 2.1 Normative references | Normative references are not applicable in the present document. |
666bafb4e85109224934d34b2ddcd853 | 104 164 | 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... |
666bafb4e85109224934d34b2ddcd853 | 104 164 | 3 Definition of terms, symbols and abbreviations | |
666bafb4e85109224934d34b2ddcd853 | 104 164 | 3.1 Terms | For the purposes of the present document, the terms given in ITU-T Technical Report QSTR-TFR [i.1] apply. |
666bafb4e85109224934d34b2ddcd853 | 104 164 | 3.2 Symbols | Void. |
666bafb4e85109224934d34b2ddcd853 | 104 164 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ITU-T Technical Report QSTR-TFR [i.1] apply. |
666bafb4e85109224934d34b2ddcd853 | 104 164 | 4 Endorsement notice | All elements of ITU-T Technical Report QSTR-TFR [i.1] apply. ITU-T Technical Report QSTR-TFR [i.1] is contained in archive tr_104164v010101p0.zip which accompanies the present document. ETSI ETSI TR 104 164 V1.1.1 (2025-12) 6 History Version Date Status V1.1.1 December 2025 Publication |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.