hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 7.7 Mechanical performance | Mechanical performance for ADU should conform to Table 7.4. Table 7.4: Mechanical performance for ADU No Test Severity Requirement 1 Shock IEC 61300-2-9 [i.30] • ≤ 0,125 kg: 5 000 m/s2 • 0,125 kg < Mass of the sample ≤ 0,225 kg: 2 000 m/s2 • 0,225 kg < Mass of the sample ≤ 1 kg: 500 m/s2 Waveforms: Half sine waveform D... |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 7.8 Environmental performance | Environmental performance for ADU needs to conform to Table 7.5. Table 7.5: Environmental performance for ADU No Test Severity Requirement 1 Dry heat-High temperature IEC 61300-2-18 [i.32] 85 °C (±2 °C)，duration: 96 h No corrosion for the metal parts. No mechanical damages on the appearances, such as deformation, crack... |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 7.10 Fire safety performance | For the shell made of plastic materials, the V0 requirements should comply with UL 94 [i.52]. Fire safety tests are conducted to confirm whether the product poses fire hazards or equipment burnout risks under abnormal conditions such as abnormally high voltage or water dripping. Fire safety performance for ADU should c... |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 8 Deployment | |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 8.1 General | The IFDN hybrid cabling system is with the features including fully pre-connected, optical and electrical ports integrated, plug and play, quick deployment and reliable connection. Before cabling, the following tools need to be prepared: optical power meter, voltage detection meter, and other auxiliary materials for co... |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 8.2 Details to be noted | It is advisable to pay attention to the following items when routing cables: • Before routing a cable, mark the labels at both ends for easy management and maintenance. • When routing the branch cable, protect the cable and do not pull the cable with excessive force to avoid damaging the cable. Do not wind, twist, or s... |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 8.3 Acceptance items | |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 8.3.1 Electrical performance acceptance | During the cable routing, the ADU need not work and affect the remote power supply. The following method can be used to verify the issue: 1) Route the cables, and connect the other end of the hybrid connector to the voltage detection meter as described in Figure 8.1. 2) Turn on the ADU to check if the light of normal w... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 1 Scope | The present document presents an analysis of the user expectations, with respect to the study of data driven technologies (Artificial Intelligence (AI), deep learning, Machine Learning (ML)) to present the definition and concept of the User Information System (UIS), that enables Smart Customized Services (SCS) from bot... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 2 References | |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 2.1 Normative references | Normative references are not applicable in the present document. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 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... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 3 Definition of terms, symbols and abbreviations | |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 3.1 Terms | For the purposes of the present document, the following terms apply: Architecture Communication Information Function Organization (ACIFO) model: framework for interpreting and analysing complex systems whole through the five dimensions that characterize it artificial intelligence: ability of a system to handle represen... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 3.2 Symbols | Void. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: aaS as a Service ACIFO Architecture Communication Information Function Organization AI Artificial Intelligence API Application Programming Interface AR Augmented Reality DaaS Device as a Service DAC Discretionary Access Control DMA Digital Mar... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 4 Smart Customized Services for UIS | |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 4.1 Identification of the problem to be solved | Users of digital services have historically had limited ability to control the use of personal data by digital services and how a service shares that data with other services, nor is there usually fine-grained control of what is given in terms of personal data, rather there is often a "share all" approach to how data i... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 4.2 Application of the ACIFO model in SCS | The Venn diagram of Figure 1 is expanded first into the model given below in Figure 2 which illustrates the role of elements of each domain on SCS. In the context of Smart Customized Services (SCS), personalization is not limited to the adaptation of content or functionality to an individual. Analysis, through the ACIF... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 5 Use cases for User Information Systems | 5.1 Introduction to use cases for UIC and their service composition The present document adopts the model given in ETSI TR 103 477 [i.18] where it is stated that use cases are developed to examine problem statements that are a concise description of issues that need to be solved in the context of the use case. The purp... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 5.2 Urban mobility use case (Smart Urban Mobility Assistant) | Taking the general model suggested in clause 5.1 above the following outlines the role of SUMA. • What is the problem that SUMA seeks to solve in the UIS/SCS context? - Existing methods of determining an optimized personal travel plan are deficient in addressing in-depth the personal preferences and context of the user... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 5.3 Agriculture | Taking the general model suggested in clause 5.1 above the following outlines the role of UIS/SCS applied to an instance of an agricultural problem. • What is the problem that UIS/SCS seeks to solve in the agricultural context? - Agriculture faces significant challenges, including climate change, resource depletion, wa... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 5.4 Health | ETSI TR 103 477 [i.18] identifies use cases and actors for each of diagnostic and therapeutic interventions. The present document extends the characterizations from [i.18] with many of the actors being present as persistent AI entities in the health system. Thus applying the use case purpose identified in [i.18] to the... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 6.1 Data governance | In giving user control, where the user is disassociated from the service by their persistent entity, their User Digital Representation (UDR), in the network, the user has to have assurance that the data gathered, exchanged and processed on their behalf is trustworthy. There are many discussions of trust, and models of ... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 6.2 Privacy and data protection | The UIS/SCS has to conform to societal expectations of privacy protection and to also conform to any legal restrictions. To achieve this some security capabilities are required (shown in more detail in clause 7.2 below), and it is expected that the overall system conforms to expectations of the GDPR [i.20] or equivalen... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 6.3 Security | In regulatory terms there are a large number of instruments in place that serve to lower the risk to users of actions they take online. These include the Cyber Resilience Act [i.36], the Network Information Security Directive [i.37] and many of the other legislative instruments that address privacy and the content of d... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 6.4 Data semantics and ontology | The process of data portability, and of data interoperability, can be enabled by assuring that data is described semantically and to which a context can be attached, This requires that data has been structured to add meaning to it. In common practice an ontology is used to explicitly define the concepts and relationshi... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 6.5 Accessibility | Any implementation of UIS/SCS should comply with the European Accessibility Act [i.5], a legal instrument that aims to improve the functioning of the internal market for accessible products and services by removing barriers created by divergent rules in Member States. A detailed review of the impact of [i.15] and relat... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 6.6 Ethics Considerations | With SCS enabling highly personalized experiences for consumers the advent of AI-driven personalization presents opportunities to improve user engagement and experience. However, this gives rise to concerns and issues about the ethical use of AI, potential risks and hazards, and the need for suitable safeguards to prot... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1 General requirements for the Digital Ecosystem | |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1.1 Overview and introduction | The digital ecosystem (see Figure 9), is given as a digital representation of "reality", independent of applications, and is built on the following characteristics: • Core paradigms: - "softwarization/programmability" (software-defined infrastructure, APIs, IaC); - the "as-a-service" operating model (platform thinking ... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1.2 The architectural dimension | The architectural dimension defines the overall structure designed to achieve predefined objectives. This structure is characterized by specific properties, and compliance with the architecture implies adherence to these properties, making any architecture inherently semantic. The overall system architecture integrates... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1.3 The communication dimension | The UIS/SCS is expected to be a persistent object in the system and to interact with the "conventional" APIs that represent any component service's configuration and personalization entity with the added consideration that the UIS adopts a common exchange protocol (i.e. there is an expectation that each component servi... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1.4 The Informational Dimension: | At the foundation lies data, which serves as the informational backbone of personalization. This dimension integrates: • Smart Identity: Complete representation of users, i.e. their potential profile where their preferences are found, behaviour patterns and knowledge. • External Data: Environmental conditions, service-... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1.5 The functional Dimension | To ensure a seamless and coherent user experience, the functional dimension relies on SCS. The application is constructed following an as-a-Service composition model (see ETSI TR 103 437 [i.25], page 13), enabling service components to be independently added, removed, or composed without compromising the global service... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1.6 The Organizational Dimension | The organizational dimension determines data responsibility, where, and how data is processed and stored, spanning the dew, edge, fog, and cloud continuums. The key elements of this process are: • Data Governance: Establishing control mechanisms to manage data integrity, access rights, and retention. • Security and Pri... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.2 UIS/SCS requirements User side (userware) | |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.2.1 Userware Interactions with the ecosystem components | To outline and highlight indicative requirements of UIS/SCS on the user-side within a digital ecosystem, the organizational model should define "who does what", according to the user's chosen autonomy level (see "the cursor" [i.25]). The userware and its interface should make simple and explainable controls, exposing w... |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.2.2 User Centric Vision | According to user-centric vision, a connected ecosystem is designed to deliver seamless digital services through multiple interacting layers (Figure 10). Figure 10: User vision of integrated ecosystem Service providers offer digital services supported by an underlying network layer that ensures reliable connectivity. A... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 1 Scope | The present document defines a data model for lists of trusted entities, as well as bindings of such lists in various syntaxes allowing relying parties to establish and process lists of trusted entities. NOTE: The data model for a list of trusted entities aims to be an abstract generalization of the existing specificat... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 2 References | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 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... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 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... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 3 Definition of terms, symbols and abbreviations | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 119 001 [i.6] and the following apply: list of trusted entity scheme operator: body that is responsible for the operation and/or management of the approval scheme under which the corresponding LoTE is published provider of person identity data: As def... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 3.2 Symbols | Void. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 10 |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CC Country Code EU European Union HTTP HyperText Transfer Protocol LoTE List of Trusted Entities LoTESO List of Trusted Entities Scheme Operator MS Member State PID Person Identity Data Pub-EAA Electronic Attestation of Attribute issued by a p... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4 General concepts | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.1 List of Trusted Entities (LoTE) | List of Trusted Entities are intended to convey trust in a set of entities that are providing services within a given approval scheme. They take the form of a list of entities that have been granted a particular status under the given approval scheme. They represent the outcome of a process of approval, whereby the lis... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.2 Approval scheme | An approval scheme is any organized process of supervision, monitoring, approval or such practices that are intended to apply oversight with the objective of ensuring adherence to specific criteria in order to maintain confidence in the services under the scope of the scheme. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.3 Trusted entities | A trusted entity is an entity that is recognized as trustworthy within a given approval scheme for a specific scope or purpose. Trusted entities can be legal or natural entities, or objects. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.4 Trusted entity services | Entities that are listed in a list of trusted entities are entities that are recognized as being trustworthy within the LoTE scheme for a specific scope. The scope for which this recognition is granted is materialized in the LoTE through "trusted entity service" entries, which are associated to a specific type identifi... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.5 List of Trusted Entities Scheme Operator | The scheme operator of a List of Trusted Entities (LoTESO) is the body that is responsible for the operation and/or management of the approval scheme under which the corresponding LoTE is published. In particular, the LoTESO is the body responsible for establishing, maintaining and publishing the LoTE. LoTESO can be an... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.6 Syntax bindings | A Syntax binding is an instantiation of the LoTE data model into a given syntax such as XML, JSON, CBOR, etc. The present document provides such XML and JSON bindings in Annex A. There may be several different bindings in the same syntax. EXAMPLE: Different bindings can be defined, for instance, for an implicit scheme ... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.7 LoTE profiles | An LoTE profile is set of scheme-defined constrains on the elements of a LoTE. Such constrains can take the form of additional requirements regarding the values of the elements of a LoTE, or the absence or presence of those elements (e.g. making the presence of an element mandatory or forbidden when it is optional unde... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 5 Overall structure of lists of trusted entities | The logical model of a list of trusted entities is shown in Figure 1. It has the following logical component parts. There shall be only one occurrence of the first two and last components (i.e. 1., 2. and 6.). The other components may be replicated as illustrated in Figure 1: 1) A list of trusted entities tag (Tag): Th... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6 List of trusted entities components | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.1 General principles for lists of trusted entities | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.1.1 Formats of list of trusted entities | The present document provides bindings in XML and JSON for list of trusted entities in Annex A, which may be used for issuing list of trusted entities. Additional bindings may be provided in subsequent versions of the present document. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.1.2 Use of Uniform Resource Identifiers | In the definitions of LoTE fields given in the present document, many use uniform resource identifiers (URIs) to indicate the meaning of the field concerned. Within these definitions a "common name" may be used to broadly and simply describe the specific values or meanings of the field. These common names are linked to... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.1.3 Date-time indication | All fields carrying date-time values shall comply with the following rules: 1) the date-time values shall be a character string formatted according to ISO 8601 [8]; and 2) the date-time value shall be expressed as Coordinated Universal Time (UTC): its value shall contain year with four digits, month, day, hour, minute,... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.1.4 Language support | Lists of trusted entities shall be issued supporting at least the UK English language, using the 'en' language code as specified in IETF RFC 5646 [11] and Annex G. Lists of trusted entities may also be issued supporting multiple (national) languages. For all the fields where support of multiple language is applicable, ... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.1.5 Value of Country Code fields | All fields carrying Country Codes values, denoted by "CC", shall be in capital letters and in accordance with either: a) ISO 3166-1 [2] Alpha 2 codes with the following exceptions: 1) the Country Code for United Kingdom shall be "UK"; 2) the Country Code for Greece shall be "EL"; 3) when the scope of the field is the E... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.2 List of trusted entities tag | Description: The LoTE is tagged to facilitate its identification during electronic searches. Format: The LoTETag component shall be a character string which indicates that the data structure is a LoTE. This shall be the character representation of the LoTE Tag URI. Semantics: This value of this string shall be a unique... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3 List and scheme information | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.0 General | Description: This ListAndSchemeInformation component provides information on the list of trusted entities and its issuing scheme. Information about the scheme within which the LoTE is issued may be provided either implicitly or explicitly. NOTE: Scheme information can be implicitly known when, for instance, it is provi... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.1 LoTE version identifier | Description: The LoTEVersionIdentifier component specifies the version of the LoTE format for a specific syntax binding. Format: The LoTEVersionIdentifier component shall contain an integer. Semantics: The value of this integer shall be incremented only when the rules for parsing the LoTE in a specific syntax change, e... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.2 LoTE sequence number | Description: The LoTESequenceNumber component specifies the sequence number of the LoTE. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 18 Format: The LoTESequenceNumber component shall contain an integer. Semantics: At the first release of the LoTE, the value of the sequence number shall be 1. The value shall be incremented at... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.3 LoTE type | Description: The LoTEType component specifies the type of the list of trusted entities. It permits a parser to determine the form of any following field to expect according to a specific syntax binding and profile. Format: The LoTEType component shall contain an indicator expressed as a URI. Semantics: Each LoTE profil... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.4 Scheme operator name | Description: The SchemeOperatorName component specifies the name of the entity in charge of establishing, publishing, signing and maintaining the list of trusted entities. Format: The SchemeOperatorName component shall contain a sequence of multilingual character strings (see clause 6.1.4). Semantics: The name of the s... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.5 Scheme operator address | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.5.0 General | Description: The SchemeOperatorAddress component specifies the address of the legal entity or mandated organization identified in the 'Scheme operator name' component (clause 6.3.4) for both postal and electronic communications. Format: This component shall contain: 1) the PostalAddresses element specified in clause 6.... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.5.1 Scheme operator postal address | Description: The PostalAddresses component specifies the postal address of the legal entity identified in clause 6.3.4, with the provision for the inclusion of the address in multiple languages. Format: This component shall contain sequence(s) of multilingual PostalAddress components (see clause 6.1.4). The PostalAddre... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.5.2 Scheme operator electronic address | Description: The ElectronicAddress component specifies the email address, the web-site URI and optional telephone number of the legal entity identified in clause 6.3.4 for electronic communications. Format: The ElectronicAddress component shall contain a sequence of multilingual character strings (see clause 6.1.4). Se... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.6 Scheme name | Description: The SchemeName component specifies the name under which the scheme operates. Format: This component shall contain a sequence of multilingual character strings (see clause 6.1.4), defined as follows: • The English version shall be a character string structured as follows: - CC:EN_name_value; where: - 'CC' i... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.7 Scheme information URI | Description: The SchemeInformationURI component specifies the URI(s) where users (relying parties) can obtain scheme- specific information. Format: This component shall be a sequence of multilingual pointers (see clause 6.1.4). Semantics: This component may contain be zero or more URIs leading to archived versions of t... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.8 Status determination approach | Description: The StatusDeterminationApproach component specifies the identifier of the status determination approach. Format: The StatusDeterminationApproach component shall contain an indicator expressed as a URI. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.9 Scheme type/community/rules | Description: The SchemeTypeCommunityRules component specifies the URI(s) where users (relying parties) can obtain scheme type/community/rules information against which the trusted entities and the trusted entity services included in the list are approved and assessed, and from which the type of scheme or community may ... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.10 Scheme territory | Description: The SchemeTerritory component specifies the country or territory in which the scheme is established and applies. Format: The SchemeTerritory component shall contain a character string in accordance with clause 6.1.5. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.11 LoTE policy/legal notice | Description: The PolicyOrLegalNotice component specifies the scheme's policy or provides a notice concerning the legal status of the scheme or legal requirements met by the scheme for the jurisdiction in which the scheme is established and/or any constraints and conditions under which the LoTE is maintained and publish... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.12 Historical information period | Description: The HistoricalInformationPeriod component specifies the duration over which historical information in the LoTE is maintained once it has been included. Format: This component shall contain an integer. Semantics: When the value of this integer is set to '65535', this signifies that historical information pr... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.13 Pointers to other LoTEs | Description: The PointersToOtherLoTE component references any relevant list of trusted entities or any relevant list of lists of trusted entities. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 23 Format: The PointersToOtherLoTE component shall contain a sequence of one or more OtherLoTEPointer elements, each OtherLoTEPointer e... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.14 List issue date and time | Description: The ListIssueDateTime component specifies the date and time on which the list of trusted entities was issued. Format: The ListIssueDateTime component shall contain a date-time value (see clause 6.1.3). Semantics: The ListIssueDateTime value shall be the Coordinated Universal Time (UTC) at which the LoTE wa... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.15 Next update | Description: The NextUpdate component specifies the date and time by which, at the latest, an update of the LoTE will be made available by the scheme operator or be null to indicate a closed LoTE. Format: The NextUpdate component shall contain a date-time value (see clause 6.1.3). Semantics: The NextUpdate value shall ... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.16 Distribution points | Description: When used, the DistributionPoints component specifies locations where the current LoTE is published and where updates to the current LoTE can be found. Format: The DistributionPoints component shall contain a non-empty sequence of URIs. Semantics: Dereferencing the given URI will always deliver the latest ... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.17 Scheme extensions | Description: The SchemeExtensions component provides specific scheme-related information and enhancements that do not require a change in the version identifier, which can be interpreted by all accessing parties according to the specific scheme's rules. Format: The SchemeExtensions component shall contain a sequence of... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.4 Trusted Entities List | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.4.0 General | Presence: If no trusted entity is or was approved in the context of the list of trusted entities scheme, this component shall not be present. If one or more trusted entity services are or were approved under the LoTE scheme, this component shall be present. Description: The TrustedEntitiesList component provides a list... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.4.1 Trusted entity | Description: The TrustedEntity component provides information about a trusted entity and its corresponding services approved in accordance with the list of trusted entities scheme. Format: This component shall contain the below components: • The TrustedEntityInformation element (see clause 6.5) The TrustedEntityService... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.4.2 Trusted entity services | Description: The TrustedEntityServices component contains a sequence identifying each of the TE's recognized services and the approval status (and history of that status) of that service. Format: This component shall be a sequence of TrustedEntityService components. Semantics: When historical information is to be retai... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.4.3 Trusted entity service | Description: The TrustedEntityService component provides information about a trusted entity service approved in accordance with the list of trusted entities scheme. Format: • This component shall contain the below components: - The ServiceInformation element (see clause 6.6.0). ETSI ETSI TS 119 602 V1.1.1 (2025-11) 26 ... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.4.4 Service history | Description: The ServiceHistory component specifies historical information on listed trusted entity services as a sequence of all previous status entries which the scheme has recorded for the given TE service. Format: The ServiceHistory component shall be a sequence of ServiceHistoryInstance elements (see clause 6.7). ... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5 Trusted entity information | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.0 General | Description: The TrustedEntityInformation component provides information about a trusted entity. Format: This component shall contain the below components: • The TEName element (see clause 6.5.1). • The TEAddress element (see clause 6.5.3). • The TEInformationURI element (see clause 6.5.4). This component may optionall... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.1 TE name | Description: The TEName component specifies the name of the legal entity, or when applicable the natural person, responsible for the TE's services that are or were recognized by the scheme, in particular for the TE's services that are or were approved under the applicable scheme. Format: The TEName component shall be a... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.2 TE trade name | Description: The TETradeName component specifies an official registration identifier as registered in official records, where such a registered identifier exists, that unambiguously identifies the TE. It may additionally be used to specify an alternative name under which the TE identifies itself in the specific context... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.3 TE address | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.3.0 General | Description: The TEAddress component specifies the address of the legal entity or mandated organization, or when applicable the natural person, identified in the 'TE name' field (clause 6.5.1) for both postal and electronic communications. Format: The TEAddress component shall contain the below sub-components: • The TE... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.3.1 TE postal address | Description: The TEPostalAddress component specifies the postal address of the TE identified in clause 6.5.1, with the provision for the inclusion of the address in multiple languages. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 28 Format: As specified in clause 6.3.5.1. Semantics: This shall be a postal address at which the... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.3.2 TE electronic address | Description: The TEElectronicAddress component specifies an email address, a web-site URI, and an optional telephone number of the TE identified in clause 6.5.1, to be used for electronic communications. Format: As specified in clause 6.3.5.2. Semantics: The e-mail address, and the telephone number when present, shall ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.