hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-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... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 3 Definition of terms, symbols and abbreviations | |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 104 158-1 [1] apply. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 104 158-1 [1] apply. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 104 158-1 [1] apply. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4 AICIE Common Container Record | |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1 AICIE Common Container Record Format and Values | |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.1 Introduction | The AICIE Common Container Record format is depicted in Figure 4.1-1 and captures a set of minimum essential information concerning an AI incident reporting resource. BOLD field names are mandatory, enum=enumeration, cb=checkbox and "…" indicates free-form content. The AICE Common Container JSON record format is define... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.2 AICIECCversion | This required value describes the present AICIE Common Container Record specification version being used and expressed as three numbers separated by commas and set initially to 1.0.0. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.3 AICIECCtitle | This required value without any constraints describes a title for the AI incident. ETSI ETSI TS 104 158-2 V1.1.1 (2026-03) 10 |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.4 AICIECCincidentDescription | This required value without any constraints describes the AI incident. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.5 AICIECCsystemRelationship | This required value describes the how the AI system(s) are related to the incident using one or more of the following non-case-sensitive enumerations, including an unconstrained free-form option. direct cause contributing factor failure to act overreliance and intentional misuse human error legal obligation omission … ... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.6 AICIECCsubmitterInformation | This required value describes the information without any constraints for the entity submitting the incident report including entity name, affiliation, physical address, a useable email address, stakeholder group, including one or more of the following non-case sensitive affiliation enumerations. government or regulato... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.7 AICIECCdateFirstOccurred | This optional value describes the date of first known occurrence of the AI incident in Coordinated Universal Timenumbers [year]-[month]-[day]. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.8 AICIECCincidentCountry | This optional value describes the countries where the AI incident occurred as an enumerated string of country identifiers separated by commas. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.9 AICIECCincidentMaterial | This required value without any constraints describes the AI incident supporting materials address location - preferably as a persistent, precise, accessible Uniform Resource Location (URL) or a link capable of providing the resource. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.10 AICIECCaiProduct | This optional value without any constraints describes a title for the name and version of the AI system(s) or product(s) that gave rise to the reported AI incident. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.11 AICIECCaiSystemDeveloper | This optional value without any constraints describes the organisation(s) that developed and/or deployed the AI product(s) or services that gave rise to the reported AI incident. ETSI ETSI TS 104 158-2 V1.1.1 (2026-03) 11 |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.12 AICIECCseverity | This required value describes the assessed severity of the AI incident reported using one or more of the following non-case-sensitive enumerations, or other using an unconstrained free-form option. serious hazard hazard incident serious incident incident … (free-form content) |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.13 AICIECCharmType | This required value describes the harm type of the AI incident reported using one or more of the following non-case-sensitive enumerations, including an unconstrained free-form option. physical psychological reputational economic/property environmental public interest critical infrastructure human or fundamental rights... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.14 AICIECCharmConsequence | This optional value describes, if applicable, a quantification of the harm using one or more of the following non-case-sensitive enumerations, including an unconstrained free-form option. economic losses death injury compensation quantification … (free-form content) |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.15 AICIECCintentionality | If applicable using an indicator flag, this optional value describes without any constraints how an AI incident was linked in an unintended or wrongful way to an AI system and how. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.16 AICIECCpartiesAffected | This optional value describes, if applicable, the affected parties using one or more of the following non-case-sensitive enumerations, including an unconstrained free-form option. consumer children workers business trade union government civil society general public … (free-form content) ETSI ETSI TS 104 158-2 V1.1.1 (... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.17 AICIECChumanRightsImpact | If applicable using an indicator flag, this optional value describes without any constraints any adverse impacts on human rights or fundamental values. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.18 AICIECCprinciplesAffected | This optional value describes associated AI principles using one or more of the following non-case-sensitive enumerations. accountability fairness inclusivity privacy data governance respect of human rights robustness digital security safety environmental sustainability transparency explainability democracy human auton... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.19 AICIECCindustry | This optional value describes industries associated with the AI incident using a string of comma separated numbers of industry classifications using International Standard Industrial Classification of All Economic Activities (ISIC) [i.33]. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.20 AICIECCbusinessFunction | This optional value describes business functions where the AI incident occurred using one or more of the following non-case-sensitive enumerations. human resource management sales ICT management and information security marketing and advertisement logistics citizen/customer service procurement maintenance accounting mo... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.21 AICIECCcriticalInfrastructure | If applicable, if critical infrastructure capabilities are significantly affected this optional value indicates those critical infrastructures using one or more of the following non-case-sensitive enumerations. ETSI ETSI TS 104 158-2 V1.1.1 (2026-03) 13 energy, including oil and gas water supply and wastewater manageme... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.22 AICIECCdeploymentBreadth | This optional value describes the breadth of AI system deployment associated with the AI incident occurred using one of the following non-case-sensitive enumerations. pilot project (e.g. team/small group) narrow deployment (e.g. company/city) broad deployment (e.g. sector/country widespread deployment (e.g. sectors/cou... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.23 AICIECCtrainingDataLink | If applicable using an indicator flag, where the AI incident is linked to the training data, this optional value describes without any constraints how the incident is linked. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.24 AICIECCincidentModelLink | If applicable using an indicator flag, where the AI incident is linked to the AI model, this optional value describes without any constraints how the incident is linked. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.25 AICIECCusageRights | This optional value describes the usage rights associated with the AI system giving rise to the incident using one or more of the following non-case-sensitive enumerations. one-time license fee-based research purposes only non-commercial restricted access free of charge creative commons open source/permissive copyleft/... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.26 AICIECCmultipleSystems | If applicable using an indicator flag, where the AI incident is linked to multiple AI systems, this optional value describes without any constraints how the incident is linked. ETSI ETSI TS 104 158-2 V1.1.1 (2026-03) 14 |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.27 AICIECCaiTasks | This optional value describes the tasks associated with the AI system giving rise to the incident using one or more of the following non-case-sensitive enumerations. recognition/object detection organisation/recommenders event/anomaly detection forecasting/prediction interaction support/chatbots goal-driven organisatio... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.28 AICIECCautonomyLevel | This optional value describes the maximum autonomy level associated with the AI system giving rise to the incident using one of the following non-case-sensitive enumerations. no-action autonomy (human support) low-action autonomy (human-in-the-loop) medium-action autonomy (human-on-the-loop) high-action autonomy (human... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.29 AICIECCactionTaken | This optional value describes the actions taken, if any, in response to the AI incident using one or more of the following non-case-sensitive enumerations. prevention mitigation ceasing remediation … (free-form content) |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.30 AICIECCstepsReproduced | If applicable, this optional value without any constraints describes the steps taken to reproduce the AI incident. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 4.1.31 AICIECCadditionalInfo | This optional value without any constraints describes any other information associated with the AI incident. ETSI ETSI TS 104 158-2 V1.1.1 (2026-03) 15 Annex A (normative): AICIE Common Container JSON record Format V1.0.1 { "$schema": "http://[tbd]", "title": "JSON Schema for AI Common Incident Expression Common Record... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 1 Scope | The present document identifies the ITS domain and its elements. It provides the ITS architectural and ecosystem context. The present document complements and extends the ETSI drafting rules [i.3] and identifies consistency aspects related to the protocol stack layering and referencing between the ITS specifications an... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 2 References | |
c302a8046c060680ec046ae93d26dccd | 103 903 | 2.1 Normative references | Normative references are not applicable in the present document. |
c302a8046c060680ec046ae93d26dccd | 103 903 | 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... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 3 Definition of terms, symbols, and abbreviations | |
c302a8046c060680ec046ae93d26dccd | 103 903 | 3.1 Terms | For the purposes of the present document, the following terms apply: backward compatibility: ability of a newer system to interoperate with an older system NOTE: An ITS-S based on Release x+1 (Rx+1) is backward compatible with Release x when, Rx+1 is able to obtain the same level of services of a Rx station in an envir... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 3.2 Symbols | Void. |
c302a8046c060680ec046ae93d26dccd | 103 903 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 5G-NR 5th Generation New Radio AD Automated Driving ADAS Advanced Driver Assistance Systems AID Application Identifier AL Access Layer ALI Access Layer Instance ASIL Automative Safety Integrity Level ASN Abstract Syntax Notation B2B Business t... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4 The ITS Context | |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4.1 In general | The purpose of communication standardization is to enable participants in the communication, to exchange data in a conform and interoperable way. Such standardization encourages competition in an open market, as referred to in European single market Regulation (EU) 2022/2065 [i.4]. The development of standards requires... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4.2 The ITS Communications Domain | Intelligent Transport Systems (ITS) are systems that combine and apply ICT and electromechanical technologies with the intend to improve traffic flow, traffic safety and transport efficiency. In principle, it covers transport systems for road, water and rail covering e.g. logistics, fleet resource management, traffic i... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4.3 ICT architectures | In Information and Communication Technologies (ICT) the following architectural levels are defined, allowing users to identify related communication requirements. The Open Group Architecture Framework (TOGAF) ISO/IEC 10746 [i.20]) defined three main architecture types. • Enterprise Architecture (EA) level. This is the ... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4.4 Ecosystems | |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4.4.1 Introduction | ITS ecosystems encompass all ITS related policies, strategies, processes, information, technologies, applications, and stakeholders that together make up the requirements, and it is realized in a specific trusted technical environment for a country, region, government, or enterprise. Most importantly, an ICT ecosystem ... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4.4.2 ITS ecosystems | |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4.4.2.1 Introduction | Within ITS there are various ITS ecosystems in operation e.g. Traffic light infrastructure systems, Tolling systems, Logistics systems and safety related ITS. The present ETSI ITS releases (Release 1 and 2) do not cover the above mentioned ITS ecosystems but focus on safety related ITS ecosystems e.g. road traffic safe... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4.4.2.2 The Cooperative-ITS (C-ITS) ecosystem | As referenced, the C-ITS ecosystem is defined by Directive (EU) 2023/2661 [i.9] and its amendment (EU) 2023/2661 [i.9]. As such the term C-ITS when used in the domain of ITS in Europe, is legally limited to what is defined by this EU regulation. The C-ITS ecosystem is intended to increase traffic safety and traffic eff... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4.4.2.3 The DFRS ecosystem | At present Data for Traffic Safety (DFRS) [i.14], facilitated by ERTICO, has defined their DFRS ecosystem in their technical specification [i.29]. The Commission Delegated Regulation (EU) No 886/2013 (SRTI) [i.25] is realized not only by DFRS [i.14] but also by NAPCORE [i.15], C-ROADS [i.16] and C2C-CC [i.17]. The DFRS... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4.4.2.4 The NAPCORE ecosystem | The National Access Point Coordination Organisation for Europe (NAPCORE) [i.15] project started in 2022, to work on a better alignment of the implementation of EU specifications in the European Member States. NAPCORE is a Programme Support Action co-funded by the EU under the Connecting Europe Facility. NAPCORE [i.15] ... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4.4.2.5 The MirrorLink® ITS ecosystem | At present, MirrorLink® is an ITS Ecosystem which was specified by the Car Connectivity Consortium (CCC). It is a smartphone-to-vehicle integration system that works similarly to other systems such as Android Auto® and Apple CarPlay®. A smartphone can be linked to the vehicle's infotainment display using MirrorLink®. O... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4.5 ITS Services | At present there is a large base of ITS services operational such as process or information management related services (Logistics) but also safety related services. Each of these ITS service classes have their own dynamics, functional and technical requirements. Some of these services encompasses both management as we... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 4.6 ITS Systems and ITS Stations | As clarified in clause 4.2, different ITS Systems are and further can be realized in the ITS Domain. ITSs are Information and Communications Technology (ICT) systems with an ITS purpose. An ITS is formed by more than one piece of equipment's communicating to each other. ITS in which the software and hardware in these e... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5 ITS technical architectures | |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.1 Introduction | As described in clause 4.3, a Technical Architecture (TA) provide a detailed view that specifies the technical design, technology standards, protocols, and products, used to implement functions and layers of an ecosystem. Technical architectures are used to implement and realize equipment. In general TAs specify specif... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.2 ITS implementation architectures | In the ITS domain, ITS-Ss exchange information via various implementation communication architectures. The overall architecture as illustrated in Figure 6 shows the collection of presently implemented or envisioned ITS ecosystems for the EU. The following aspects are recognized: • The Service Provider (SP) ITS strategi... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3 Technical architectures in ITS standardization | |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.1 Introduction | As explained in clause 5.1, although profiles can be part of ETSI ITS releases, TAs in ETSI ITS standards of a release are informative or illustrative only. However, a basic ITS architecture identifying the basic ITS communication between ITS-Ss (sometimes also referred to as ITS nodes) can be defined. This ITS basic a... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.2 The ITS-S technical architecture | The ITS-S architecture is a simplified model derived from the ISO Information Basic Model (ISO-IBM, ISO/IEC 7498-1 [i.12]) and is provided in Figure 9. This architecture is intended to provide a structure in which components can relate to each other. Information flows between components belonging to the same layer or t... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.3 Other Architectural models (UML) | Components can be realized in soft- and hardware or be realized by a mixture of soft- and hardware. In principle, the higher the component is placed in the ITS-S architecture the more it will be realized by software. In case component descriptions could be used to realize software solutions, UML is often used to specif... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.4 Common Layer aspects | The common aspects are mainly related to the use of terminology. The terminology is dependent on the layer. Figure 10 provides an overview. Data are bits whose meaning is not directly of relevance or not known. Information is data from which the meaning is known. At the applications and Facilities Layer (FL), it is abo... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.5 ITS Applications | This clause defines general ITS application possible additional aspects, e.g. classification, prioritization and channel assignment, registration and secure maintenance, in the context of ITS. An ITS application can be a single functionality above the FL in one ITS-S, making use of collected information received from a... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.6 Access Layer | As shown in Figure 11, the Access Layer (AL) identified as part of the ITS-S architecture in clause 5.4, is decomposed into the Data Link Layer (DLL) and the Physical Layer (PHY). The DLL can be further decomposed into a Media Access Control (MAC) which manages the access to the communication medium, and below it, the ... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.7 Networking & Transport Layer | The Networking & Transport Layer (NTL) is shown in Figure 12. Figure 12: The generalized Networking & Transport Layer composition ETSI ETSI TR 103 903 V2.1.1 (2026-03) 27 The NTL contains components from the OSI network layer and the OSI transport layer. It can include one or several networking protocols, one or severa... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.8 Facilities Layer | The Facilities Layer (FL) is shown in Figure 13. Figure 13: The generalized Facilities Layer composition The basic components of the FL are application support, information support and application/FL management. Security related component can additionally reside at the FL layer depending on the ITS ecosystem. The FL in... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.9 Predictable ITS Communication behaviour | In a communication system the communication is always limited by the limited availability of radio spectrum or by interference of any kind and therefore is characterized by having a certain level of predictable behaviour of being able to transmit or receive information. To realize higher levels of predictability in ITS... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.10 ITS-Station management | |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.10.1 Introduction | ITS-S management is an ITS-S internal aspect and therefore mostly an implementation aspect. Depending on the ecosystem required communication architecture, it could be important to realize some of the management functionalities in an interoperable way and therefore it could be of relevance to standardize those function... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.10.2 Application management | ITS application management manages the installation and configuration of ITS-S applications and is responsible for the updating of these applications. The application management supports the error handling of ITS-S applications. It can include safeguarding mechanisms alleviating harmful application behaviours. In gener... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.10.3 Resource management | In ITS, information exchange possibilities could be limited by the available radio or spectrum resources. At present in ITS it is recognized being of interest to manage these radio resources. In future, possibly also other resources could be managed. In internet communication, the routing of data is managed at the Netw... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.10.4 Message forwarding | Message forwarding is a mechanism which is helpful in direct (AdHoc) communication environments as the source could possibly not reach the destination. In such case an ITS-S which sinks packets from other ITS_Ss can source the packets toward the final destination. This is not applicable for internet-based communication... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.10.5 Network management | Message forwarding at the NTL is a functionality which directly forwards packages without providing knowledge about the forwarding to the FL. In case a RM functionality is implemented at the FL, the RM gets only aware about the forwarding of packets at the NTL in a reactive manner via the ALI dynamic collection compone... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.11 ITS security | |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.11.1 Introduction | The type of security that needs to be implemented is defined by the ecosystem requirements and therefore the security requirements often differ from ecosystem to ecosystem. In many cases the security is covered by a commonly agreed model and authority. For example, in the C-ITS ecosystem, this is covered by European se... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.11.2 Security related ecosystem dependencies | A security solution depends on various requirements related to trust, data privacy, safety or functional impact and system security impact requirements. Some of these requirements are part of national or regional regulations. A number of these aspects are system specific and could be seen as static requirements, howeve... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.11.3 Security in the ITS architecture | As identified, the required security mechanism depends on the ecosystem to be supported. In principle security functionalities could exist at any layer of the ITS architecture. At present there are no general architectural considerations being identified. The security architecture should be considered as an ecosystem i... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.11.4 Security functionalities | The ITS-S security includes security functionalities related to the ecosystem specific ITS communication protocol stack, the ITS-S and ITS applications, e.g.: • firewall and intrusion management; • authentication, authorization and profile management; ETSI ETSI TR 103 903 V2.1.1 (2026-03) 32 • identity, crypto key and ... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.3.12 Local Dynamic Map | For the purpose of direct traffic manoeuvrer and traffic safety services, the knowledge about the presence of other ITS-Ss in the direct neighbourhood is essential for manoeuvrer and safety decision making. Relevant information about the equipment's ITS-S kinematic state, e.g. position, speed and heading can be capture... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.4 ITS Radio Spectrum | |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.4.1 Introduction | In the context of ITS, there are ITS ecosystems which make use of IP networks and ITS ecosystems which make use of specific ITS allocated spectrum. This clause concerns only those ITS ecosystems which make use of specific ITS allocated spectrum. Radio spectrum is a scarce resource and therefore ITS applications should ... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.4.2 Congestion management | Physical communication channels have limited bandwidth. In operational environments, a large number of directly communicating ITS-Ss accessing the ITS spectrum can lead to excessive load on the physical channel. Mechanisms avoiding such excessive load should therefore be considered to ensure proper operation of ITS. Su... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 5.4.3 Interference management | In general, any radio system should comply with all the spectrum related requirements which are applicable for the used spectrum. Equipment should therefore comply with all applicable world, regional and national spectrum regulations and avoid any unwanted interference with other existing systems in and outside of the ... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 6 ITS Standards Releases | |
c302a8046c060680ec046ae93d26dccd | 103 903 | 6.1 Introduction | A product has its lifecycle, from research and product definition to development, production to maintenance. When the product definition changes, this can be seen as a product upgrade but also as a new product. Often this is recognized as going from one generation to the next generation products. This shift can be back... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 6.2 Release 1 findings | The restructuring into Releases was initiated when going from Release 1 to Release 2. In Release 1 there were circular references which basically defined a system and limited the use of the Release 1 specifications. As result in following releases, normative referencing is limited to only the functionality specific com... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 6.3 Release principles | To support going from one release to another, some release principles for the ITS Domain are needed. The following ITS release related principles are defined: • Maximize the technology neutrality within and between releases and only be specific when this is strictly required for the realization of interoperable and con... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 6.4 Release management | A Release represents a toolbox including functionality, cross-layer sub-system and testing specifications as well as context and study reports. Besides the toolbox, system specifications and system profiles could complement the toolbox as system implementation specifications. All the specifications part of a Release ar... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 6.5 Release processes | Release management consists of two main processes: a) The development process in which specifications part of a release are developed and updated following test and validation. b) The maintenance process once a given release is "frozen" in which corrections are included with Change Requests (CRs). These CRs, once appro... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7 ETSI ITS deliverables | |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7.1 Introduction | ETSI deliverables have different purposes within the equipment development process, see ETSI drafting rules [i.3]. These documents follow the standard template formats. For users of the standards, it gives a recognizable format allowing easy reading. For standardization experts the template complemented with the ETSI D... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7.2 ITS documents in the development process | In the equipment realization process, the V-model identifies the definition, testing and possibly integration specifications (profiles). A single or a set of specifications could define a single functionality up to a complete system. Equipment in general is vendor specific while the realization can be based on propriet... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7.3 ITS documents - purpose in perspective | The various documents in a release all have a specific role in the development process. The most basic difference is identifiable in the development process V-model. In the V-model the design specifications are separated from the testing (verification and validation) related compliance specifications. Further at the de... |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7.4 ETSI ITS standards structure |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.