hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.5 An overview on Interfaces of a DE | The DE Model shows the Interface Names and what is happening on each interface, as well as the Primitives that should be supported by a particular DE Interface. A Management Interface of the DE is presented with its sub-interfaces and the Management Primitives that should be supported. The DE Model and Interfaces is ad... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.6 E_I sub-interface of the Management Interface: Effector Interface | This sub-interface shall be used by either an upper DE or by some special Tool in the GANA Governance Interface in the case of a Network Level DE (a Knowledge Plane DE) to manage the DE and its operations/behaviours. More details on this subject can be found in ETSI GS AFI 002 [2]. The following primitives should be su... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.7 S_I sub-interface of the Management Interface: Sensory_Interface | A DE shall expose "Views" in form of sensory information to its upper DE through the "Sensory Interface" (S_I) sub interface of its Management Interface. The same "Views" may be shared by the DE to another DE(s) via this interface or the DE2DE_I (DE-PeerDE) interface. The following primitives should be supported by thi... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.12 Other_Int_Iinterface of a DE: OtherInteraction_Interface | The OtherInteraction_Interface shall be used for communications between a DE and other entities that are not its ME or a DE. For example entities within the environment, such as monitoring tools/components, databases or entities in the underlying substrate of an ME of the DE (e.g. lower layer protocol stack providing s... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.13 DE2DE_I Interface of a DE : DE-PeerDE_Interface | As a DE may need to interact with others entities such as MEs or other DEs not directly under its responsibilities, a DE-Peer-DE interface may be required on a DE for interactions with peering DEs. ETSI ETSI TS 103 195-2 V1.1.1 (2018-05) 61 This interface shall be used by a DE to communicate with another DE at the same... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.14 Summary of Interfaces of a DE Model | NOTE: The Management Interface of a DE and the sub-interfaces of the Management Interface are enablers for DE Programmability. Table 2: Summary of Interfaces of a DE Model Interface Sub- interface Full name of the sub- interface Caller and Callee/Consumer Primitives Reference Clause in the present document Management i... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.15.1 Concept of "ownership" of MEs in GANA | The "Concept of Ownership" of MEs and their configurable and controllable parameters is a feature of the intrinsic stability attributes that shall be considered for autonomic network architecture (as is also defined in GANA). This concept requires that every ME is managed by a single DE, i.e. no two DEs (i.e. control l... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.16.2 GANA level 1 DE (the lowest)-called "Protocol" Level DE | Protocol Level DE relates to any Managed Entity (ME) such as protocol, network service enabler, software components, and other fundamental mechanisms that may exhibit intrinsic control-loops and associated DE Logic, as it is the case for most of today's protocols such as the routing protocol, OSPF (Open Shortest Path F... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.16.3 GANA level-2 DE-called "Function" Level DE | 5.1.3.16.3.1 A General Characterization of GANA Level 2 DEs (called Function-Level DEs) A Function Level DE relates to a DE for collective autonomic management and control of a group of protocols and mechanisms that are abstracted (viewed like a bundle) by a particular "networking or a management/control function". MEs... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.16.4 GANA Level-3 DE-called Node-Main-DE | 5.1.3.16.4.1 A General Characterization of GANA Level 3 DEs (collectively called the Node-Main- DE (consisting of the sub-DEs)) The Node-Main-DE orchestrates and manages DEs on the Function Level DE and may manage MEs not managed by the Function-level-DE. The Node-Main-DE relates to a DE for autonomic management and co... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.16.5 GANA Level-4 DE (the highest level)-called "Network" Level-DE | 5.1.3.16.5.1 A General Characterization of GANA Level 4 DEs (called Network-Level DEs) The Network Level DE relates to a DE for autonomic management and control of those aspects that cover network- wide views and the management andcontrol of the GANA Nodes which embed lower levels DEs (node level DE, function level DE ... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.5 Model Based Translation Service (MBTS) | NOTE 1: The description and characterization of the MBTS provided in this clause is an extract from the corresponding MBTS related clauses in ETSI GS AFI 002 [2]. This means that description and characterization of the MBTS features provided in this clause are to be complemented by the MBTS related details provided in ... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.6.2 Categories of Information that could be stored and shared through ONIX | Implementers of ONIX should consider the following criteria in designing, dimensioning and deploying the ONIX- pertaining to the information that could be stored and shared through ONIX: 1) The type of raw data and information to be stored into ONIX and exchanged/shared with entities which subscribe to receive such inf... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.6.3 Information Services that should be provided by ONIX | The following services shall be provided by the ONIX: • Storing and Retrieving Information: - Push and Pull models supported. - Different classes of information. - Add, remove or replace operation supported. - Information is described using rules to process data such as those defined in RDF or other mark-up language (e... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.6.4 Information Subscription Mechanism | Any authorized entity may query the ONIX system for data or may subscribe to ONIX to retrieve information of interest when the information becomes available in ONIX. A subscription is defined by the requestor, the information requested and the trigger to gather and send the information. For defining what information to... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.6.5 Bootstrapping information | ONIX should also be used to store bootstrapping data for the autonomic network. Bootstrapping is a self-sustaining process employed by a behaviour-exhibiting entity (e.g. a network element or node) that progresses without (or with limited) external help. In an autonomic networking environment, bootstrapping requires th... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.6.6 On Federation of ONIX systems, and other characteristics of ONIX | The ONIX system, as a distributed system, may be scoped, owned and policed (i.e. governed) by a particular administrative domain. This implies that different ONIX systems (ONIXs') may exist and so inter-domain Information/Knowledge sharing may be required. NOTE 1: The clauses in the present document that discuss federa... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.3 Summary Table of Reference Points in GANA | Table 4 provides a summary of the Reference Points in GANA, which are further described in the clauses that follow and with complementary details in ETSI GS AFI 002 [2]. ETSI ETSI TS 103 195-2 V1.1.1 (2018-05) 92 NOTE: In addition to the Reference Points summarized in this clause there are other Reference Points (Rfps)... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.4 GANA DE-to-DE and DE-to-ME Reference points (Rfps) | 6.4.1 Vertical Reference Points and Horizontal Reference Points in GANA, GANA integration with Legacy Management Systems, and Federated AMC Reference Points Regarding DE reference points, a VRP is a hierarchical reference point between peer DEs in different GANA DE levels and a HRP is a horizontal reference point betwe... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.4.2 Vertical Reference Points in GANA | 6.4.2.1 DeMe: reference point between the Node-Main-DE or Function Level DEs and Managed Entities (MEs) in the resources layer of a GANA node (NE) Figure 13: Rfp DeMe: Node-Main-DE_or_Function-Level-DE to Fundamental Managed Entities (MEs) An ME communicates "Views" such as event notifications (event detections) and mo... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.4.2.3 NeMe: Vertical Reference Point Network-Level-DE-to-NodeMainDE | Figure 15: Rfp_NeMe: Reference Point between a Network Level DE and Node Main DEs Information (e.g. state information) from a Network Element (NE) that is autonomically managed by network level DEs may be conveyed to the DEs through this reference point, e.g. some state information may be conveyed to a particular netwo... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.4.2.4 OsDe: Vertical Reference Point: OSS/BSS-to-Network-Level-DE | Figure 16: Rpf_OsDe Reference Point between OSS/BSS and Network Level DEs Views (Characteristic Information) exchange: OSS/BSS may be used to send and update the GANA Profile to DEs in the Knowledge Plane such that the DEs augment the GANA Profile with additional configuration data necessary. Information (e.g. configur... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.4.2.5 NeM Vertical Reference Point: Network Element-to-AMC-MBTS | Figure 17: Rfp_NeM Reference Point between Network Element and KP through AMC-MBTS Views (Characteristic Information) exchange: KP DEs (Network-Level-DEs) retrieve information from an NE and send commands for policy enforcements to Network Element through the AMC-MBTS, which also translates the information retrieved fr... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.4.3.1 FuDe: Horizontal Reference Point: FunctionLevelDE-to-FunctionLevelDE | Figure 19: Rfp_FuDe Reference point Between Function level DEs Views (characteristic information) exchange: Reference point used for interactions between Function Level DEs within the same administrative domain. Description: information exchange between Function-Level-DEs via the DE-2-DE interactions to achieve a "netw... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.4.3.2 NoDe: Horizontal Reference Point: NodeMainDE-to-NodeMainDE | Figure 20: Rfp_NoDe: Reference Point between Node Main DEs Views (characteristic information) exchange: This Reference point (Rfp) is used for interactions between Node Main DEs and within the same administrative domain. Description: Similar types of Characteristic Information as in the case of the Reference Point "Rfp... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.4.3.3 NeDe Horizontal Reference Point: NetworkLevelDE-to-NetworkLevelDE | Figure 21: Rfp_NeDe Reference Point between Network level DEs Views (characteristic information) exchange: Reference Point used for interactions between Network Level DEs within the same administrative domain. Similar types of Characteristic Information as in the case of the Reference Point "Rfp_FunctionLevelDE-to-Func... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.4.4 AMC Federation Reference Points | 6.4.4.1 A General Characterization of Reference Points (Rfps) pertaining to Federated AMC across Domains NOTE: In the federation of Autonomic Management and Control (AMC) of Networks and Services, "domain" in the diagrams in clauses 6.4.4.2 to 6.4.4.6 means either "Administrative Domain", or "Technical or Technology" D... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.5.1 NoI Reference Point: GANA Node-Main-DE-to-ONIX Rfp | Figure 27: Rfp_NoI Reference Point between Node-Main-DE and ONIX The Rfp implements Operations/Messages for Storing and Retrieving Information into/from the ONIX system. The Node-Main-DE shall use the publish/subscribe services of the ONIX that enable Advanced Auto-Discovery of Information and Resources, to retrieve In... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.5.2 NeI Reference Point: NetworkLevelDE-to-ONIX Rfp | Figure 28: Rfp_NeI Reference Point between Network Level DE and ONIX Through this Rfp a Network Level DE may retrieve and store information in the ONIX system based on the services of the ONIX and the information stored in the ONIX and information required to be stored into ONIX by KP DEs. The Rfp should implement Oper... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.6.3 ONIX as Network Inventory | A GANA node may register itself to the ONIX and self-describe its capabilities and the capabilities of its associated MEs and DEs within the GANA Node and possibly with Peers GANA Nodes as well, its connections with other GANA Nodes, and with the KP. The GANA Node may describe its current configuration, if it has defau... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 6.6.4 Auto-Configuration of DEs and MEs | A default configuration may be available in the Knowledge Plane for each DE and MEs of a GANA Node. If the GANA node has already a default configuration it may start the next steps in getting operational. The default configuration of the GANA node may be used to create, connect and test the interactions between entitie... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 7.1 Main Conclusion Points/Remarks | The present document has presented the GANA Reference Model for Autonomic Networking, Cognitive Networking and Self-Management for communication networks and services. The present document is based on the ETSI GS AFI 002 [2]-a document that complementarily describes the GANA. The difference being that the present docum... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 7.2 Further Work | Regarding Further Work, the following are some of the aspects that should be addressed by the Standards communities by SDOs/Fora and Open Source Communities, in creating work items that should work on these aspects and any other aspects that may be identified in that process: NOTE: ETSI should create a RACI matrix to h... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 1 Scope | The present document contains a description of scenarios, use cases, and definition of requirements for the autonomic/self-managing future internet. Scenarios and use cases selected in the present document reflect real-world problems which can benefit from the application of autonomic/self-management principles. Two ty... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 2 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 reference document (including any amendments) applies. Referenced documents which ar... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. Not applicable. |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] P. Horn. Autonomic Computing: "IBM's perspective on the State of Information Technology" October 2001, IBM Corp. NOTE: Available at http://people.scs.... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 3 Definitions and abbreviations | |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: automated management: automation of the processes involved in the creation of network configuration input using specialized Task Automation Tools, e.g. scripts, network planning tools, policy generators for conflict-free policies Auton... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project AB Autonomic Behaviour ABGet Available Bandwidth Get AC Admission Control AC_ME Admission Control Managed Entity AF Autonomic Function AFI Autonomic network engineering for the self-managing Future Inter... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 4.5 AFI Requirement template | Table 1 depicts the template defined in order to capture relevant data related to the requirements with respect to the given scenarios (clause 5) . It is composed of the following fields: • Player • Network Environment • Requirement Identity (RQ ID). An arbitrary sequential number (without any normative meaning) alloca... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 4.6.1 Basic requirements an Autonomic Network shall support | An Autonomic Network shall support the following Self-functions [i.22]: • Self healing • Self optimization • Self protecting • Self organizing • Self Configuration • Self-Diagnosis • Self awareness In addition, the Autonomic Network or its internal functions may support the following Self* features: • Self-advertise • ... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 4.6.2 Requirements for specific network environments | Based on the master template of the table 1, tables 2 to 7 are the instantiations of this template to relevant scenarios identified in the present document. This classification is players-oriented: • User player requirement (table 2) • Manufacturer requirement (table 3) • Access Network requirement (table 4) • Access a... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 5 Use Case and Scenarios | |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 5.1 Use Case and Scenario Template | Template Table 10 depicts the template defined in order to capture relevant data related to the AFI Use Case and Scenarios. It is composed of the following fields: • Title • Description/Story • Network Environment(s) • Problems • Functions Impacted • Systems Involved • Indicators / Evaluation criteria /Metrics • Player... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 5.2 Autonomics in legacy network (NGN) | Table 11: Autonomic in legacy network (NGN) Title Autonomic in legacy network Description/Story Use Case The legacy network is composed of a panel of players which need to cooperate in order to provide user services with associated QoS and security as prerequisite for launching a service. The number of equipment and pl... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 5.6 Coordination of Self-* mechanisms in autonomic networks | Table 15: Coordination of Self-* mechanisms in autonomic networks Title Coordination of Self-* mechanisms in objectives autonomic networks Description/Story Use Case The goal of this scenario is to capture the requirements stemming from the introduction of various Self-* mechanisms in to the network elements. In partic... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 5.7 Autonomic Network Monitoring | Table 16: Autonomic Network Monitoring Title Autonomic Network Monitoring Scenario Description/Story Use Case The scenario refers to autonomic network monitoring in a dynamic environment. Other services may also be deployed following similar principles, as discussed below (see also figure 1). In the following scenario,... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 5.8 Scenarios Overlay Virtual Network Service Breakdown | Table 17: Scenarios Overlay Virtual Network (OVN) Service Breakdown Title Overlay Virtual Network (OVN) Service Breakdown Description/Story Use Case This scene focuses on how a network can react to problems disrupting the consumption of a given OVN service, for example photo sharing (an OVN is a virtual network allowin... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 5.10 Monitoring in Carrier Grade Wireless Mesh Networks | Table 19: Monitoring in Carrier Grade Wireless Mesh Networks Title Monitoring in Carrier Grade Wireless Mesh Networks (CARMEN) Description/Story Use Case Mesh networking technology provides a cost effective and efficient alternative for realizing backhaul networks to provide mobile users with high quality services. Wir... |
e8f124f48f83ee3a7b8bbf3c1758f5e4 | 103 194 | 5.13 Scenarios, requirements and references relationship | To sum up, table 22 lists the relationships between Scenarios and derived requirements. It also mentions the references (European Research projects, SDOs) if any. ETSI ETSI TS 103 194 V1.1.1 (2014-10) 63 Table 22: Use cases, Scenarios and references relationships Scenarios Requirement Identifier: RQ ID Reference Scenar... |
c9feba6b0ee1a301fa99477c67ab19ba | 103 169 | 1 Scope | Recent work in the ETSI Technical Committee Rail Telecommunications (TCRT) has uncovered implementation options in the ETSI standards for VGCS calls which must be clarified by the Railways in order to ensure interoperability between GSM-R networks across Europe. The present document replaces the former A 01T 0004 1 [i.... |
c9feba6b0ee1a301fa99477c67ab19ba | 103 169 | 2 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 reference document (including any amendments) applies. Referenced documents which ar... |
c9feba6b0ee1a301fa99477c67ab19ba | 103 169 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI EN 301 515 (V2.3.0): "Global System for Mobile communication (GSM); Requirements for GSM operation on railways". [2] ETSI TS 102 281 (V2.1.0): "Railways Telecommunications (RT); Global System for Mobile communications... |
c9feba6b0ee1a301fa99477c67ab19ba | 103 169 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] A 01T 0004 1: "MORANE/UIC - ASCI options for interoperability". NOTE: Available at: http://www.uic.org/IMG/pdf/MORANE_ASCI_Options_for_Interoperabilit... |
c9feba6b0ee1a301fa99477c67ab19ba | 103 169 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASCI Advanced Speech Call Items BSS Base Station Subsystem CCCH Common Control Channel DRX Discontinuous Reception FACCH Fast Access Control Channel GSM-R Global System Mobile-Railways MS Mobile Station NCH Notification Channel NLN Notificatio... |
c9feba6b0ee1a301fa99477c67ab19ba | 103 169 | 4 ASCI Options for Interoperability | This table summarizes the ASCI options required for GSM-R implementations as referred in the corresponding specifications listed in [1], [2] and [3] and necessary to fulfil the amendments in [i.2] to the specifications referred in [i.1]. Table 1 Required for interoperability NSS BSS MS Notification process Notification... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 1 Scope | The present document provides parts of the Test Suite Structure and Test Purposes (TSS & TP) for ITS Interoperability scenarios. The objective of the present document is to provide a basis for automated interoperability testing. |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 2 References | |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-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... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 3 Definition of terms, symbols and abbreviations | |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 3.1 Terms | For the purposes of the present document, the following terms apply: host vehicle: vehicle equipped with an OBU |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 3.2 Symbols | Void. |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ATS Abstract Test Suite BO Inopportune test events for Behaviour tests BTP Basic Transport Protocol BV Valid test events for Behaviour tests CA Cooperative Awareness CAM Cooperative Awareness Message CBF Contention Based Forwarding CCH Control... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 4 Conventions | |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 4.1 Interoperability test process | |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 4.1.1 Introduction | The goal of interoperability test is to check that devices resulting from protocol implementations are able to work together and provide the functionalities provided by the protocols. As necessary, one message may be checked during a test, when a successful functional verification may result from an incorrect behaviour... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5 Test configuration | |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5.1 Areas definitions | The clauses below describes the different radio configurations required to execute the AUTO_IOT tests. Different areas are considered for these tests, e.g.: • The Geonetworking area which is the radio curvature area. • The Relevance area which is an area defined for each protocol message such as DENM. NOTE: The default... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5.2 Common rules | |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5.2.0 General | All the tests require usage of common rules. |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5.2.1 Radio rules definitions | In the case of using of ITS G5 [i.1] radio access layer, all messages defined in the present document shall be sent on the channel type G5-CCH with the channel number 180, as specified in ETSI EN 302 663 [4]. On-link: EUTs are in radio range and have exchanged CAMs and built a neighbour table. ETSI ETSI TS 103 192-2 V1... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5.2.2 GPS rules definitions | All messages indicating fixed or relative GPS coordinates shall contain well-formatted data, this include the altitude and confident data. |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5.2.3 Conformance checks rules definitions | The following basic conformance checks apply for all interoperability tests: • CAM protocol: - ItsPduHeader check - Mandatory protocol IEs • DENM protocol: - ItsPduHeader check - Mandatory protocol IEs • BTP protocol: - BTP-A/BTP-B type - Destination port • Geonetworking protocol: - GN address - Position vector content... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5.3 Triggered messages | Triggered messages are used to indicate: 1) An action to be executed on the EUT (from the Test System to the EUT) 2) Or to confirm the execution of an action (from the EUT to the Test System) 3) Or to indicate an event at the HMI level (from the EUT to the Test System) 4) Or to indicates any unsolicited message (from t... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5.4 Test configuration overview | |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5.4.0 General | The clauses below describe the different radio configurations required to execute the AUTO_IOT tests. |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5.4.1 CF-01: Verify complete forwarding message scenario | There are two independent geonetworking areas defined: 1) EUT1 is the source 2) EUT2 is closer to TARGET_GEOAREA than EUT3 3) EUT4 is in the destination area (TARGET_GEOAREA) 4) EUT1, EUT2 and EUT3 are on-link 5) EUT2, EUT3 and EUT4 are on-link 6) EUT1 and EUT4 are off-link Figure 1: DEN message forward |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5.4.2 CF-02: Road Works Warning configuration | 1) EUT1 and EUT2 are on-link. 2) EUT1 and EUT2 are located in the same Geonetworking area. 3) EUT1 acts as a RSU. 4) EUT2 acts as a vehicle. 5) EUT2 is moving from Start position to End position. Start End POS0 POS1 POS2 POS4 POS3 Figure 2: Road Works Warning configuration |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5.4.3 CF-03: CA messages | 1) EUT1, EUT2 and EUT3 are on-link. 2) EUT1, EUT2 and EUT3 are located in the same Geonetworking area. ETSI ETSI TS 103 192-2 V1.2.1 (2022-02) 12 3) EUT1, EUT2 and EUT3 act as vehicle. 4) EUT1, EUT2 and EUT3 are moving. |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 5.4.4 CF-04: Intersection Collision Warning configuration | 1) EUT1 and EUT2 are on-link. 2) EUT1 and EUT2 are located in the same Geonetworking area. 3) EUT1 (vehicle) in moving from Start1 position to End1 position. 4) EUT2 (vehicle) in moving from Start2 position to End2 position. 5) Positions POS0 and POS1 are located at the same distance from the intersection. 6) EUT1 resp... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 6 Test Suite Structure (TSS) | |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 6.1 Structure of tests | Table 1 shows the AUTO_IOT Test Suite Structure (TSS) including its subgroups defined for conformance testing. ETSI ETSI TS 103 192-2 V1.2.1 (2022-02) 13 Table 1: TSS for AUTO_IOT Root Group Sub-group Category AUTO_IOT DENM protocol Forwarding Valid and Inopportune Road Works Warning Valid and Inopportune Road Hazard S... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 6.2 Test groups | |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 6.2.0 General | The test suite has a total of three levels. The first level is the root. The second level separates the root into various functional areas. The third level is the standard ISO conformance test categories. |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 6.2.1 Root | The root identifies AUTO_IOT Abstract Test Suite. |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 6.2.2 Test group | This level identifies the major ITS protocol referred by the test. |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 6.2.3 Test sub-group | This level identifies the sub categories of each Group. |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 6.2.4 Categories | This level contains the standard ISO conformance test categories: behaviour for valid, invalid, inopportune events and timers. |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7 Test Description (TD) | |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7.1 Introduction | |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7.1.1 TD definition conventions | The TDs are defined by the rules shown in Table 2. Table 2: TD definition rules TD Id The TD ID is a unique identifier. It shall be specified according to the TD naming conventions defined in clause 6.1. Test scenario Short description of test purpose objective according to the requirements from the base standard. Refe... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7.1.2 TD Identifier naming conventions | The identifier of the TD is built according to Table 3. Table 3: TD naming convention Identifier: TD_<root>_<gr>_<x>_<nn> <root> = root AUTO_IOT ITS interoperability testing <gr> = group CAM CAM messages testing DENM DENM message testing <sgr> = sub-group MFW Message forwarding RWW Road Works Warning RHS Road Hazard Si... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7.2 Test purposes | |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7.2.1 Introduction | The legend below applies for all figures of this clause. GREEDY EUT in configured to use Greedy algorithm CBF EUT in configured to use CBF algorithm SIMPLE EUT in configured to use SIMPLE algorithm Contention timer started (CBF algorithm only) Contention timer stopped (CBF algorithm only) Message discarded (duplicated ... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7.2.2 DEN message - Forwarding | Figure 4: GREEDY/GREEDY/GREEDY forwarding TD Id TD_AUTO_IOT_DENM_MFW_BV_01 Test scenario Verify complete forwarding message scenario (GREEDY, GREEDY, GREEDY) - See Figure 4 Reference ETSI EN 302 636-4-1 [1], annex D and clause E.2 Config Id CF-01 PICS Selection Pre-test conditions • itsGnNonAreaForwardingAlgorithm of E... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7.2.3 DEN message - Road Works Warning | TD Id TD_AUTO_IOT_DENM_RWW_BV_01 Test objective Verify complete Road Works Warning scenario Reference ETSI EN 302 637-3 [3] Config Id CF-02 PICS Selection Pre-test conditions • EUT1 (RSU) sends RWW DENMs D1, D2 and D3 • EUT2 (vehicle) is outside the relevance area • EUT2 (vehicle) is moving from Start position to End p... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7.2.4 DEN message - Road Hazard Signals | TD Id TD_AUTO_IOT_DENM_RHS_BV_01 Test objective Verify complete Road hazard Signals scenario Reference ETSI EN 302 637-3 [3] Config Id CF-02 PICS Selection Pre-test conditions • EUT1 (RSU) sends RHS DENMs D1 • EUT2 (vehicle) is outside the relevance area • EUT2 (vehicle) is moving from Start position to End position • ... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7.2.5 DEN message - Stationary Vehicle Warning | TD Id TD_AUTO_IOT_DENM_SVW_BV_01 Test objective Verify complete Stationary Vehicle Warning scenario Reference ETSI EN 302 637-3 [3] Config Id CF-02 PICS Selection Pre-test conditions • EUT2 (vehicle) is outside the relevance area • EUT2 (vehicle) is moving from Start position to End position • EUT1 (RSU) sends RHS DENM... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.