hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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 use it efficiently. Two aspects should be considered: • The presence of several ITS applications and ITS message services requires to consider the impact of their information dissemination on other ITS applications and ITS message services. • The presence of other systems active in the same spectrum. In general, this should be arranged by spectrum regulation but should be reviewed and may lead to additional measures such as mitigation. Both aspects are out of scope of basic standards (toolbox) since they are ecosystem issues and need to be covered by profiling. In the context of direct V2X some related aspects are considered in the following clauses. |
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. Such means are referred to as "Congestion Control" (CC) and impacts all communication layers of the ITS-S architecture. Congestion management is usually realized with functionalities at the applications, the FL and/or the AL through means such as: • By informing the applications about the channel CC so that applications can limit message dissemination. • By resource management functionalities at the FL which dynamic re-route information to appropriate channel resources. Dynamic modification of repetition rate of periodic/repetitive messages. • By modification of AL parameters, on a frame-by-frame basis. In addition, it is quite common that there are mechanisms implemented at the AL as part of technology specific specifications and are unique for those specific technologies. ETSI ETSI TR 103 903 V2.1.1 (2026-03) 33 For the definition of application and /or FL layer CC related functionalities such as RM, the influence of these AL CC mechanisms should be considered. |
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 frequency band used. In case harmful interference could occur, mitigation methods could be applicable. Tolling systems realize their information exchange by means of Dedicated Short-Range Communication (DSRC) technologies, at the time of implementation not hampered by any spectrum receiver parameter requirements in regulations with the effect that related OBUs are sensitive for transmissions in adjacent channels. As ITS communications became later active in related adjacent channels, ITS equipment should ensure not to interfere with DSRC Tolling systems. As such it could be required to implement mitigation techniques At present service provider specific urban rail technical systems are deployed in restricted areas which can be adjacent to roads. This means that mitigation from R-ITS to Urban rail ITS (U-ITS) needs to be considered. |
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 backward compatible or not. For ITS this is not different. ETSI ITS standards are based on Releases, Release 1 being already frozen while Release 2 work has not been completed at the time of writing the present document. NOTE: While the Release 2 documents can be recognized by "Release 2" appearing in the title, Release 1 documents have no Release statement in their titles. The development of Release 1 focused on C-ITS realization, and the C-ITS extension in Release 2 do have to be backward compatible (see clause 6.3) with Release 1 according to EU regulation Directive 2010/40/EU [i.24] and Directive (EU) 2023/2661 [i.9]. Based on the experiences with Release 1 ITS specifications as identified in ETSI TR 101 607 [i.1], an updated Release 2 of the ETSI TR 101 607 [i.1] includes all Release 2 documents. ETSI TR 101 607 [i.1] is part of the set of framing documents. |
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 components. Re-use analyses of Release 1 documents for use in Release 2 showed the following misunderstandings: • There is back and forth (up and down) normative referencing. To avoid issues only one direction (downwards) normative referencing should be used. In case it can be proven that it is required for clear understanding and avoids errors informative referencing bottom up could be used. • Normative referencing is realized between different functionalities. Normative referencing to other functionalities should be avoided. In case one functionality could have an interface with another functionality this should only be generally identified and not specified. Only in case parameters which are defined in one functionality specification should be set in another functionality specification, can it be specified conditionally normative so that other possibilities are kept open. ETSI ETSI TR 103 903 V2.1.1 (2026-03) 34 • Consciously functionality specifications and sub-system specification should be kept separate and referenced one way or another. • There can only be normative references between functionality specifications in case those specifications are a subpart of one larger functionality. These specifications are entity specifications which together specify a functionality. In most cases such set of specifications is kept together by a functionality architecture specification specifying the overall operation and architecture of the functionality and therefore it will reference normatively to all other specifications of that functionality. Each of the entity specifications can informatively reference to the architecture specification. They should not reference to the other entity specifications. |
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 conform implementations. • A Release includes a set of specifications by which any user can realize an ITS implementation, possibly in combination with other specifications. A release should be seen as a toolbox by which any stakeholder, group of stakeholders or other organizations can realize an ITS system which realizes a specific set of ITS services in accordance with a specific set of ecosystem requirements in mind. • Functionality specifications should not reference to other functionality specifications except when in a functionality specification there are parameter values which are specified in other functionality specifications. In that case a normative reference to the specifications in which the parameters are specified could be made. • In addition to functionality specifications, sub-system specifications can exist. Sub-systems often are defined by combining several functionality specifications. As such, in sub-system specifications, normative referencing to functionality specifications is allowed, but circular referencing should be avoided. • A functionality can also be specified by a set of specifications, generally this happens when the functionality has components at more than one layer. In that case a top, often architectural normative specification is the leading document for that functionality which can have normative references to layer specific specifications. • A release could include ecosystem profiles in separate clauses and identified as examples in case there are also other profiles defined elsewhere. ITS Domain related principles: • For any functionality, the spectrum efficient use should always be considered at the ecosystem level and therefore in the related profile, to avoid the influence on other functionality operations in the same spectrum. • In case multiple ecosystems make use of the same spectrum, agreements are needed between those ecosystems to ensure correct operation of each of them. • A specific release is the extension of the previous release. It includes all elements which support the realization of ITS services as supported in the previous release(s). For the sale ITS services, A release is backward compatible with all previous releases. An ITS-S based on Release x+1 (Rx+1) is backward compatible with an ITS-S based on Release x (Rx) when: • Rx+1 is able to obtain the same level of services of Rx in an environment based on Rx (see also Figure 14); and • Rx+1 is specified in a such a way that Rx is able to maintain its full functionality in an environment based on Rx+1 (see also Figure 15). For C-ITS this is a regulatory requirement. At present there are no Backward compatibility regulatory requirements for other Ecosystems. ETSI ETSI TR 103 903 V2.1.1 (2026-03) 35 Figure 14: ITS stations implemented based on Release X+1 obtains the same level of services of a Release x station Figure 15: ITS stations implemented based on Release x maintains its full functionality in an environment based on Rx+1 |
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 are listed in ETSI TR 101 607 [i.1] which is one of the framing documents. For Release 1 this is ETSI TR 101 607 [i.1] V1.x.x (for maintenance reasons the present document could still be updated in future) while for Release 2 this will be in ETSI TR 101 607 [i.1] V 2.x.x (the first digit of the version number is in accordance with the release, so 2 is for Release 2) |
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 approved by the Technical Committee (TC), are included in an ERRATA document. An ERRATA document is release specific, but it is required to check all releases to see whether the CRs are applicable to a document part of any other release, in which case the CRs could affect ERRATA documents of other releases. The ERRATA documents are always publicly available. ETSI ETSI TR 103 903 V2.1.1 (2026-03) 36 |
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 Drafting Rules [i.3] provide the bases for qualitative standard creation. Within ETSI ITS, mainly the following types of documents are in use: European Norms (EN), Technical Specifications (TS) and Technical Reports (TR). The first 2 are normative specifications which provide requirements for specific functionalities, sub-systems or systems. The TR is an informative document type which can be used for clarifications of aspects specified in one or more TSs or ENs. It can also be used to reflect the results of a study to explain why a specification included specific requirements. ENs are specific for Europe and are always transposed at national level.. In addition, there are some ETSI ITS specific aspects which complement the ETSI Drafting Rules [i.3] and are added for quality and consistency reasons. Clause 7.2 provides a perspective on how the ETSI ITS deliverables should be seen as part of the equipment development process and how they relate to each other. The following clauses provide a guidance on how to look at the purpose of each of the clauses in the ETSI ITS deliverables in addition to the document templates as provided by ETSI. It should be noted that, in general a standard specification only includes interoperability and conformity requirements to allow each interested enterprise or consortium or group to create its own system specification and to allow them to differentiate in an open market following, for instance in Europe, the open market Regulation (EU) 2022/2065 [i.4]. Although a standard is a technical specification and therefore is technology specific, it should allow to add additional technical possibilities and maximize the technology neutrality. This technology neutrality does not need to be specific for a standard itself, but it is required in general, meaning that as long as it is possible to create another standard allowing other technologies, each of these standards can be considered technology agnostic. ETSI ITS standards follow the ETSI drafting rules [i.3] and by that comply with Regulation (EU) 2022/2065 [i.4]. |
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 proprietary specifications only, standards or both of them. In case the equipment of one vendor needs to be interoperable with the equipment of one or more other vendors, they can form a group to come to common interoperable specifications, often called profiles. Profiles can be managed by such groups themselves or be realized as a standard via an SDO such as ETSI. An example of ETSI ITS related Ecosystem profiles are the HMI ITS-Ecosystem MirrorLink® [i.5]specifications and the ITS Profiles for the sidelink LTE-V2X and sidelink 5G-NR profiles as captured in ETSI TS 103 723 [i.13]. Equipment could include a number of ICT systems from which several ITS related sub-systems. For instance, there is equipment which includes a C-ITS Eco-sub-system, ICT sensor sub-system and a DFRS Eco-sub-system. Four system interoperability levels can be distinguished. • Party specific equipment implementation specifications: All specifications up to the system architecture specification are proprietary, which means that solution and technical architectural requirements and exclusive for the specific party. They are not shared with other parties. • Private and/or public partnership system interoperability profiles: If applicable, related specifications are often realized in so called system design profiles based on common interest between the contributing parties. Such profiles can be maintained by a specific stakeholder in common agreement, by a defined organization, a Standardization Development Organization (SDO) or by an authority. ETSI ETSI TR 103 903 V2.1.1 (2026-03) 37 • Sub-system design specifications: Sub-system specifications have the objective to realize interoperability and conformity at a sub-system level. A sub-system is a specific composition of 2 or more functionalities (building blocks) which together realize a specific higher-level functionality which as a hole cannot operate by itself as it is not a system by itself. Sub- system specifications are technical specific and as much as possible technology agnostic to enable the use in different system configurations. • Functionality design specifications: Functionality specifications have the objective to realize interoperability and conformity at a building block level for a specific functionality so they can be used to realize private and public partnership profiles or be used in sub-system specifications. Functionality specifications are technical specific and as much technology agnostic as possible to enable the use in different system configurations. NOTE: In the above the terms system and sub-system are used the context of ITS-S system definition. To ensure that sub-system and functionality specifications can be combined without a specific system in mind some specific parameters should commonly be agreed. Within ETSI ITS at present the following supporting layer related specifications have been identified: Common Data Dictionary (CDD), encoding rules, AIDs, port-numbers and geographical area definitions. These common specifications can be normatively referenced in the functionality specifications. See clause 7.3 below. For the test and integration specifications there are 3 levels. • Party specific equipment testing specifications: For the verification and validation of equipment a party specifies system, sub-system and functionality testing specifications. These specifications are based on the party specific design specifications. • Private and/or public partnership system interoperability testing: If applicable, these testing specifications are based on the related system design profiles and are meant to test the system or sub-system aspects. Such testing specifications can be maintained by a specific stakeholder in common agreement, by a defined organization, a Standardization Development Organization (SDO) or by an authority. • Sub-system and functionality testing specifications: Sub-system testing and functionality testing specifications are directly linked to the related design specifications. In this case, compliance with the testing specifications implies compliance with the related interoperability and conformance requirements. Within the context of ETSI ITS, sub-system and functionalities are specified in TSs and ENs. |
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 design side of the V-model, framing, layer studies and specifications can be recognized. Framing documents provide context to the standards within the ITS domain. They provide information about how these standards could be used. Framing documents provide a general perspective and how the different aspects relate and should be seen in relation to each other. Part of a set of specifications are various study documents. Layer studies and specifications follow the ITS-S architecture structure as illustrated in clause 5.3.2. From a document perspective besides layer specific documents there are also cross layer functionalities which may reside at any layer depending on the implementation. ETSI ETSI TR 103 903 V2.1.1 (2026-03) 38 Figure 16 provides an overview of the document purposes and relations. Except for the contextual framework and system profiles, the other specifications and supporting documents are part of the ITS-Toolbox. A toolbox is a set of specifications to support the realization of ETSI based ITS ecosystem profile. Profiles can be part of the ETSI list of ITS release specifications or can be realized by other organizations such as C2C-CC [i.17] and C-Roads [i.16]. Figure 16: ITS Document purposes |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7.4 ETSI ITS standards structure | |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7.4.1 Introduction | This clause provides a structure of the ITS standards documents. There are several types of ETSI standard documents [i.19], but the main documents used in ITS are European Norms (EN), Technical Specifications (TS), and Technical Reports (TR). See ETSI drafting rules [i.3]. For the purpose of the framework in the following clauses the document approach within ITS is generally addressed. |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7.4.2 Document Title | The following structure for the title should be used for ETSI ITS deliverables: 1) Intelligent Transport Systems (ITS); 2) the document purpose (for clarification see clause 7.3): a) Framework; b) Access Layer, Networking & Transport Layer, Facilities Layer and Applications; c) Cross-Layers; d) Sub-System; e) Testing (identify whether this is profile, sub-system or functionality specific); f) Profile (which could be system and communication profiles); 3) the core functionality title; 4) the sub-functionality title (Sub-Part); 5) the sub-sub-functionality title (Sub-Sub-Part); and 6) Release x. The numbers 4 and 5 are not applicable for TRs. ETSI ETSI TR 103 903 V2.1.1 (2026-03) 39 |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7.4.3 The table of contents | All ETSI ITS documents should include an introduction (see clause 7.4.4). Except for Technical Reports, the ETSI ITS documents should not include a summary. A summary should be included in a Technical Report to sum up the results of the study. The following clauses are expected to be included in an ETSI ITS deliverable: 1) Scope. 2) Informative and/or Normative references as applicable. 3) Definitions of terms, symbols, and abbreviations. Generic ITS terms, symbols and abbreviations are defined in ETSI TR 103 902 [i.2]. Therefore, this clause should contain only terms, symbols, and abbreviations which are specific for the document. 4) Service introduction clause This clause is intended to provide a view of the service provided by the functionality/sub-system specified, context and/or background information. The context identifying the relation of the specified functionality or sub-system within one or several system configurations in which is expected to operate should be included. No requirements should be added in this clause. 5) Service description clause This clause is intended to describe the functionality/sub-system specified and its possible relation with other functionalities/sub-systems. The description is expected to be informative and could include general aspects of interfaces for which the requirements are expected to be specified elsewhere. 6) Requirements clause(s) The document should include at least one clause specifying mandatory/optional service specific interoperable requirements such as the component behavioural requirements and interface(s) requirements which are specific for the specified functionalities/sub-systems. Data formats, protocols etc, should also be included as applicable. It is advised to use separate clauses for the different items to be addressed. 7) Informative and Normative Annexes, as applicable. ETSI ITS Technical Reports (studies) cannot include any requirements, normative references or normative Annexes being, by definition, informative reports (see ETSI drafting rules [i.3]). More information on the content of the clauses is provided below. |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7.4.4 The Introduction | The introduction should provide a clarification of the intent of the document and how it relates to other ITS documents. It should not reflect the scope or the context as this is content related and should be part of the "body" of the document. |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7.4.5 Service introduction clause (the context) | This clause provides the user of the document an overview of the context in which the content of the document can be used and where to look for possible related documents. The context can consist of aspects like background, the origin or reason of having this document. Often in this part Ecosystem aspects relevant for the implementation are expressed. Enterprise or Solution architecture illustrations can be used to show such context. Further possible relations with other functionalities or systems from a general perspective can be of relevance to the user of the document. When it is relevant to indicate multiple architecture illustrations, Annexes should be used. The content of this clause should be limited to only those aspects which are required for the understanding of the implementation of the standard. Technical architecture illustrations are not applicable. ETSI ETSI TR 103 903 V2.1.1 (2026-03) 40 If the document intends to specify a specific part of a functionality while the whole functionality is specified in a set of documents, this set of documents has a leading architectural document including a normative functionality architecture specification. This document is the main one and should reference to the other documents normatively. The document specifying a part of the functionality (not the main one) should therefore clarify that it is part of a functionality "in an informative way". |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7.4.6 Service description clause (the functional description) | This clause should be seen as the introduction to the subsequent technical clauses of the study or specification and should provide a general explanation of the studied or specified functionality, of what it is composed and how it in general behaves. In case of normative specifications (EN or TS), the following should be considered for this clause: 1) Depending on whether functionality or sub-system specified is hardware or software dependent, specific terminology can be used. 2) In case the functionality being specified is software-oriented, UML modelling should be used to describe the internal components and interfaces. It can include UML flow diagrams to present behaviour. 3) In case the functionality is hardware oriented a hardware architecture could be used as illustration. Often UML flow diagrams are used to illustrate the possible behaviour. See clause 5.3.3 for more details. 4) In case a functionality specified includes both software and hardware both 2. and 3. above apply as long as it is ensured that the result is implementable. In case of Technical Reports (TR): Technical Reports are not normative and are mostly realized to provide study results and potential standardization items (pre-standardization). A TR therefore only includes descriptive clauses while the results are provided in a summary. |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7.4.7 Requirement clauses (functional specification) | For an EN or TS, these clauses define and specify the interoperable requirements. If a functionality consists of components or entities having internal and external interfaces, their behaviour, and data- and management flows should be defined. For readability the different aspects should be defined in separate clauses. Only when the internal interfaces are testable, should the requirement on these interfaces be included . In case the functionality is specified in a single specification, there should not be any normative or informative references to other ITS functional specifications. There can only be normative references to prescriptive documents such as the CDD, port-numbers or AIDs specifications. See clause 7.2 for more details. In case the functionality is specified in a set of specifications (and therefore a single specification defines only a part of the functionality), normative references to other specifications on the same set are possible (see clause 7.4.5). |
c302a8046c060680ec046ae93d26dccd | 103 903 | 7.4.8 Annexes | See the ETSI drafting rules [i.3] for more information on Annexes. ETSI ETSI TR 103 903 V2.1.1 (2026-03) 41 Annex A: Example of an ITS functionality architecture representation As an example, Figure A.1 shows what is expected in functionality specifications for the Cooperative Awareness Service. For that an implementer should use the appropriate specification. The architecture illustration allows the implementer to verify in the system specifications whether or not to support those interfaces identified and what related behaviour on these interfaces is expected. In Figure A.1, a system concept is presented identifying possible relations with other functionalities within the same and other layers. Interfaces could exist but not necessarily. Figure A.1: An example - CAS architecture A facilities layer service could be part of a communication system which includes a Management Information Base (MIB). In case an MIB exists, or possible other system management functions and system management interface can exist. A Management system is a functionality which can reside at any layer and is characterized being active at the management plane. Alternatively, communication aspects can be statically configured. In case there is no MIB, no RM and no LDM, the CAS has only data flow interfaces directly going to application layer sinking information and have sourcing and sinking interfaces to lower layers, all depending on the system configuration. As can be seen the layers are not drawn but are made clear in the descriptions included in the body text or the figures to realize simple diagrams. This way of illustrating functionality behaviour is similar to the processes in other SDOs. Application A+1 (Appl. Layer) Application A (Appl. Layer) Local Dynamic MAP (Facilities Layer) Security System management Lower layer functionalities management Cooperative Awareness Service (CAS, a Facilities layer service) Resource management Data Flow Management Flow It us up to the implementer at which layer the system aspects are considered ETSI ETSI TR 103 903 V2.1.1 (2026-03) 42 Annex B: UML models The Unified Modelling Language (UML) is a general-purpose visual modelling language that is intended to provide a standard way to visualize the design of a system. It delivers a standard notation for various types of diagrams e.g. behaviour diagrams, interaction diagrams, and structure diagrams. UML offers a way to visualize a system's architectural blueprints in a diagram, including elements e.g. activities (jobs), components of the system, how the system will operate, entities interact with each other and external interfaces. UML is not a development method by itself. UML provides a standardized partial graphical representation of a functionality or system. UML has many diagrams but the main three usable for standardization are the Component diagram, the Flow (or State) diagram and the Sequence diagram model. Specific for Use case descriptions, UML Use case diagrams are used and are also called actors diagrams. UML can be used at different abstraction levels. Within ETSI TC ITS documents UML drawing tools should be used to keep conformity among the different ETSI ITS deliverables. A component diagram illustrates the different entities part of a functionality and their relations internally and/or externally. See for an example Figure B.1. In standards the internal relation is only reflected in case there is an interoperability concern. Figure B.1: A CAS component diagram example A flowchart (see Figure B.2 for an example), shows the flow from one activity to another in a system or process. It is used to describe the different dynamic aspects of a system and is referred to as a 'behaviour diagram' because it describes what should happen in the modelled system. ETSI ETSI TR 103 903 V2.1.1 (2026-03) 43 Figure B.2: A PAS Flow (State) diagram example A sequence diagram(see Figure B.3 for an example) shows process interactions arranged in time sequences. A sequence diagram depicts the processes and actors involved and the sequence of messages exchanged as needed to realize a use case or carrying out a functionality. Figure B.3: A PAS service Sequence diagram example A use case diagram (see Figure B.4 for an example), is a graphical depiction of the actors' interactions. The processes are generally represented by either circles or ellipses and the actors are often shown as stick figures. ETSI ETSI TR 103 903 V2.1.1 (2026-03) 44 Figure B.4: A CAM dissemination Use case diagram example ETSI ETSI TR 103 903 V2.1.1 (2026-03) 45 Annex C: C-ITS Communication Architecture For the exchange of information between ITS stations, any communication method can be used as long as it satisfies the functional, operational, and legal requirements defined by the ITS services it should support. Figure C.1 shows the C-ITS communication architecture including information sharing via direct AdHoc communications and infrastructure-based cellular 3G, 4G, and 5G communications to enable also the information exchange via cellular networks within the same C-ITS Ecosystems. Figure C.1 shows that the information managed at the traffic management centre may use direct ad-hoc communication and/or cellular networks for its information distribution depending on the ITS service to be provided. Figure C.1: C-ITS Communications ETSI ETSI TR 103 903 V2.1.1 (2026-03) 46 History Version Date Status V2.1.1 March 2026 Publication |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.