hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 8.3.3.2 Dynamic labels | For dynamic labels, the text control field replaces the 4-bit Rfa field in the control field when the C flag = 0 and the first flag = 1, see ETSI EN 300 401, clause 7.4.5.2 [1], and figure 7. NOTE: The next revision to ETSI EN 300 401 [1] will include this change. Figure 7: Structure of the X-PAD data group for each dy... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 8.4 Decoding and presenting text labels | Different geographical regions have different requirements for text support, based on the languages in common use by the broadcasters of the region. The capability of receivers to decode and present text labels is therefore an important factor in making a successful digital radio launch and deployment. For any region t... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 8.5 Display of RTL and bi-directional labels | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 8.5.1 Introduction | Labels which contain RTL text will have the base direction set to RTL and/or the bidi flag set to 1. These flags allow a receiver to determine whether it has the capabilities to display the label. Table 5 provides an overview of the required capabilities. Table 5: Receiver capability requirements Bidi flag Base directi... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 8.5.2 Minimum RTL implementation | Receivers that do not implement the Unicode bidirectional algorithm may choose to implement the minimum RTL implementation. This implementation allows labels signalled as bidi flag = 0, base direction = 1 to be correctly formatted (although the settings of the contextual flag and combining flag may still mean that the ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 8.5.3 Simplified bidirectional algorithm | Receivers that do not implement the Unicode bidirectional algorithm may choose to implement the simplified bidirectional algorithm in order to achieve basic support for bidirectional text created by service providers according to the rules of the simplified bidirectional algorithm. This implementation allows labels sig... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 1 Scope | The present document specifies the functionality of the decentralized congestion control (DCC) entity residing in the management plane for the ITS-G5A, ITS-G5B, and ITS-G5D radio interfaces, collectively known as the 5 GHz ITS frequency band. The purpose of the DCC operation is to evaluate the load of the active radio ... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 2 References | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 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 reference document (including any amendments) applies. Referenced documents which ar... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 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 reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 3 Definitions, symbols and abbreviations | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in IEEE 802.11-2012 [1], ETSI EN 302 665 [6], ETSI EN 302 663 [7], ETSI EN 302 571 [8] and the following apply: burst of messages: set of one or more messages that the gatekeeper transfers to the ITS-G5 radio at one time CBR target value: value u... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: α Parameter of the linear adaptive algorithm β Parameter of the linear adaptive algorithm CBR Channel Busy Ratio CBRa Available CBR percentage per radio channel and per ITS-S (output of DCC algorithm) CBRtarget Target CBR in the linear adaptive algo... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN Abstract Syntrax Notation AWGN Additive White Gaussian Noise CA Cooperative Awareness (basic service) CAM Cooperative Awareness Message ETSI ETSI TS 103 175 V1.1.1 (2015-06) 10 CBR Channel Busy Ratio CEN Comité Européen de Normalisation CL... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 4 Introduction | The aim with the Decentralized Congestion Control (DCC) is to adapt the transmit parameters of the ITS station (ITS-S) given the present radio channel conditions, in order to maximize the probability of a successful reception at intended receivers. The DCC attempts to provide equal access to the channel resources among... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 5 DCC architecture | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 5.1 Overview | ETSI EN 302 665 [6] provides the ITS reference architecture for an ITS-S. The present document provides details of the DCC_CROSS entity residing in the management plane. The DCC functionality, including interfaces mapped to the ITS-S architecture, is shown in Figure 1. It is distributed between the following entities: ... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 5.2 DCC_ACC | REQ001: The access layer of an ITS-S that transmits on an ITS-G5 radio channel shall include a DCC_ACC entity, as specified in ETSI TS 102 687 [2], containing the access layer specific DCC functionalities such as those described in Annex B. ETSI ETSI TS 103 175 V1.1.1 (2015-06) 12 |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 5.3 DCC_NET | REQ002: If GeoNetworking over ITS-G5 is in place, as described in ETSI EN 302 636-4-1 [3], the network and transport layer of an ITS-S that transmits on an ITS-G5 radio channel shall include the DCC_NET entity, specified in ETSI TS 102 636-4-2 [4], which contains the networking & transport layer specific DCC functional... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 5.4 DCC_FAC | The facilities layer of an ITS-S optionally includes a DCC_FAC entity containing the facilities layer specific DCC functionalities such as those described in Annex B. |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 5.5 DCC_CROSS | REQ003: The management plane of an ITS-S that transmits on an ITS-G5 radio channel shall include a DCC_CROSS entity. It contains the management specific DCC functionalities: • DCC parameter evaluation. It computes the DCC internal parameters which indicate the available channel resources based on CBR values collected b... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 6 DCC management entity | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 6.1 Overview | The DCC_CROSS entity is illustrated in the left side of Figure 2, configured for multi-channel operation and global DCC information, as described in ETSI TR 101 612 [i.1]. The right part illustrates the functions in the data layers interacting with the DCC_CROSS. For simplification of the figure, the DCC_ACC, DCC_NET, ... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 6.2 DCC parameter evaluation | Figure 3: DCC parameter evaluation function ETSI ETSI TS 103 175 V1.1.1 (2015-06) 14 REQ004: The DCC parameter evaluation function shall calculate the available channel resources to meet the requirements as specified in clause 7. REQ005: The DCC parameter evaluation function shall obtain the local CBR from the DCC_ACC ... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 6.3 DCC_CROSS_Access | Figure 4: DCC_CROSS_Access function REQ011: The specified DCC_CROSS_Access function shall be implemented in every ITS-S that is sending messages on an ITS-G5 radio channel. REQ012: The DCC_CROSS_Access function shall provide the idle time Toff per radio channel to the DCC_ACC (DCC flow control parameters as shown in fi... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 6.4 DCC_CROSS_Net | Figure 5: DCC_CROSS_Net function REQ018: If GeoNetworking over ITS-G5 in accordance with ETSI EN 302 636-4-1 [3] is used at the networking and transport layer, then the implementation of DCC_CROSS_Net is mandatory. Otherwise, the implementation of the DCC_CROSS_Net function is optional. REQ019: When present, the DCC_CR... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 6.5 DCC_CROSS_Facilities | Figure 6: DCC_CROSS_Facilities function The implementation of a DCC_CROSS_Facilities function is optional. When implemented, its purpose is the reduction of the message rate already at generation time. ETSI ETSI TS 103 175 V1.1.1 (2015-06) 17 REQ020: When present, the DCC_CROSS_Facilities function shall distribute the ... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 7 DCC limits specification | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 7.1 Overview | The objective of the DCC algorithms is to efficiently schedule traffic of the same class among ITS-S, as well as of multiple traffic classes per ITS-S. The ITS applications are differentiated into several traffic classes according to their required share of the channel resources. Among all ITS applications potentially ... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 7.2 Requirements | REQ021: An individual ITS-S shall be able to limit its individual transmission in order not to exceed its transmit ratio. In addition, the transmit power level may optionally be used to control its own contribution to the aggregate channel utilization. REQ022: The idle time shall be equal to or greater than the minimum... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8 Interfaces | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.1 Overview | The DCC_CROSS entities offer the interfaces illustrated in Figure 1. The primitives transferred over these interfaces are compliant with ETSI TS 102 723-1 [5]. |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2 Interface (1) with DCC_ACC (MI SAP) | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2.1 MI-GET.request | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2.1.1 Function | This primitive allows retrieving parameters from the access layer, as described in clauses 6.2 and 6.3. ETSI ETSI TS 103 175 V1.1.1 (2015-06) 19 |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2.1.2 Semantics | The parameters of the primitive MI-GET.request shall be as follows: MI-GET.request ( MAC-ID, CommandRef, Sequence of I-Param.No ) Table 1: Parameters of the MI-GET.request for DCC Name ASN.1 type Valid range Description MAC-ID Structure as specified in ETSI TS 102 723-1 [5] Specified in ETSI TS 102 723-1 [5] Unique ide... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2.2 MI-GET.confirm | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2.2.1 Function | This primitive reports the result of a previous MI-GET.request. |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2.2.2 Semantics | The parameters of the primitive MI-GET.confirm shall be as follows: MI-GET.confirm ( MAC-ID, CommandRef, Sequence of I-Param ) Table 2: Parameters of the MI-GET.confirm for DCC Name ASN.1 type Valid range Description MAC-ID Structure as specified in ETSI TS 102 723-1 [5] Specified in ETSI TS 102 723-1 [5] Unique identi... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2.3 MI-SET.request | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2.3.1 Function | This primitive allows setting of a parameter in the access layer, as described in clauses 6.2 and 6.3. ETSI ETSI TS 103 175 V1.1.1 (2015-06) 20 |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2.3.2 Semantics | The parameters of the management service primitive MI-SET.request shall be as follows: MI-SET.request ( MAC-ID, CommandRef, Sequence of I-Param ) Table 3: Parameters of the service primitive MI-SET.request Name ASN.1 type Valid range Description MAC-ID Structure as specified in ETSI TS 102 723-1 [5] Specified in ETSI T... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2.4 MI-SET.confirm | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2.4.1 Function | This primitive reports the result of a previous MI-SET.request. |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2.4.2 Semantics | The parameters of the management service primitive MI-SET.confirm shall be as follows: MI-SET.confirm ( MAC-ID, CommandRef, Sequence of Errors OPTIONAL ) Table 4: Parameters of the service primitive MI-SET.confirm Name ASN.1 type Valid range Description MAC-ID Structure as specified in ETSI TS 102 723-1 [5] Specified i... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.2.5 DCC Parameters at the MI-SAP | Table 5: List of I-Param for DCC interface at MI SAP I-Param.No Name of I-Param Access Format Description 52 Channel Number R/W 1 octet, Range from 1 to 7 Identifies the radio channel number in the ITS-G5A, G5B or G5D bands. A write to this parameter selects the channel number for consecutive reads or writes. A read fr... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3 Interface (2) with DCC_NET (MN SAP) | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3.1 MN-GET.request | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3.1.1 Function | This primitive allows retrieving parameters from the network layer, as described in clause 6.2. |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3.1.2 Semantics | The parameters of the primitive MN-GET.request shall be as follows: MN-GET.request ( NT-ID, CommandRef, Sequence of N-Param.No ) Table 6: Parameters of the MN-GET.request for DCC Name ASN.1 type Valid range Description NT-ID INTEGER Integer number Unique identifier of the Network Interface (e.g. GN, IP, etc.) CommandRe... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3.2 MN-GET.confirm | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3.2.1 Function | This primitive reports the result of a previous MN-GET.request. |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3.2.2 Semantics | The parameters of the primitive MN-GET.confirm shall be as follows: MN-GET.confirm ( NT-ID, CommandRef, Sequence of N-Param ) Table 7: Parameters of the MN-GET.confirm for DCC Name ASN.1 type Valid range Description NT-ID INTEGER Integer number Unique identifier of the Network Interface (e.g. GN, IP, etc.) CommandRef I... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3.3 MN-SET.request | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3.3.1 Function | This primitive allows setting of a parameter in the network layer, as described in clauses 6.2 and 6.4. |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3.3.2 Semantics | The parameters of the management service primitive MN-SET.request shall be as follows: MN-SET.request ( NT-ID, CommandRef, Sequence of N-Param ) Table 8: Parameters of the service primitive MN-SET.request Name ASN.1 type Valid range Description NT-ID INTEGER Integer number Unique identifier of the Network Interface (e.... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3.4 MN-SET.confirm | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3.4.1 Function | This primitive reports the result of a previous MN-SET.request. ETSI ETSI TS 103 175 V1.1.1 (2015-06) 23 |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3.4.2 Semantics | The parameters of the management service primitive MN-SET.confirm shall be as follows: MN-SET.confirm ( NT-ID, CommandRef, Sequence of Errors OPTIONAL ) Table 9: Parameters of the service primitive MN-SET.confirm Name ASN.1 type Valid range Description NT-ID INTEGER Integer number Unique identifier of the Network Inter... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.3.5 DCC Parameters at the MN-SAP | Table 10: List of N-Param for DCC interface at MN SAP N-Param.No Name of N-Param Access Format Description 0 Global CBR R 1 octet, range from 0 to 100 Global CBR of the selected channel number (as specified in ETSI TS 102 636-4-2 [4]). 1 Channel Number R/W 1 octet, Range from 1 to 7 Identifies the radio channel number ... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.4 Interface (3) with DCC_FAC (MF SAP) | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.4.1 MF-SET.request | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.4.1.1 Function | This primitive allows setting of a parameter in the facilities layer, as described in clause 6.5. |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.4.1.2 Semantics | The parameters of the management service primitive MF-SET.request shall be as follows: MF-SET.request ( FAC-ID, CommandRef, Sequence of F-Param ) Table 11: Parameters of the service primitive MF-SET.request Name ASN.1 type Valid range Description FAC-ID INTEGER Integer number Unique identifier of the Facilities Interfa... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.4.2 MF-SET.confirm | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.4.2.1 Function | This primitive reports the result of a previous MF-SET.request. |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.4.2.2 Semantics | The parameters of the management service primitive MF-SET.confirm shall be as follows: MF-SET.confirm ( FAC-ID, CommandRef, Sequence of Errors OPTIONAL ) Table 12: Parameters of the service primitive MF-SET.confirm Name ASN.1 type Valid range Description FAC-ID INTEGER Integer number Unique identifier of the Facilities... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 8.4.3 DCC Parameters at the MF-SAP | Table 13: List of F-Param for DCC interface at MF SAP F-Param.No Name of F-Param Access Format Description 0 Channel Number R/W 1 octet, Range from 1 to 7 Identifies the radio channel number in the ITS-G5A, G5B or G5D bands. A write to this parameter selects the channel number for consecutive reads or writes A read fro... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 9 Test procedures | |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 9.1 Introduction | The objective is to define some test cases where the device under test (DUT) receives different signals emulating a certain amount of channel load and to verify the corresponding reaction of the transceiver to the radio channel status. This verification can be performed by monitoring the transmit ratio of the DUT. The ... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 9.2 General Test requirements | REQ026: The device manufacturer shall declare which DCC operation the equipment supports: • Local CBR. • Global CBR. • Single Channel. • Multi-Channel. ETSI ETSI TS 103 175 V1.1.1 (2015-06) 27 Based on the declared DCC operational mode the corresponding test cases and parameter sets are to be chosen. Table 2 provides a... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 9.5 Test case 3: Sensitivity threshold correction | The objective of this test is to verify the sensitivity and the threshold correction of the CBR value sent in the GN header according to different antenna gains and power levels. • Set the signal generator to emulate different channel loads ranging from 0 % up to 80 % in 5 % steps. • AWGN channel only with thermal nois... |
f33d71515d504f64e2b2f66941771c6b | 103 175 | 9.6 Test case 4: DCC stability | The objective of this test case is to verify that the DCC implementation does not introduce instable behaviour into the distributed control loop and the evaluation of an efficient limitation of the transmit ratio. • Set DUT in a mode with the highest possible duty cycle (e.g. CAM rate 10 Hz) and use a fixed message len... |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 1 Scope | The present document provides parts of the Abstract Test Suite (ATS) for ITS Interoperability scenarios. The objective of the present document is to provide a basis for automated interoperability testing. |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 2 References | |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 3 Definition of terms, symbols and abbreviations | |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 302 637-2 [i.2], ISO/IEC 9646-1 [i.3] and ISO/IEC 9646-7 [i.5] apply. |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 3.2 Symbols | Void. |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ATM Abstract Test Method ATS Abstract Test Suite BO Inopportune test events for Behaviour tests BV Valid test events for Behaviour tests CA Cooperative Awareness CAM Cooperative Awareness Message CAN Controller Area Network CF Configuration CO... |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 4 Abstract Test Method (ATM) | |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 4.1 Test Configuration | |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 4.1.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 |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 4.1.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. Figure 2: Road Works Warning configuration TARGET_GEOAREA EUT1 EUT2 EUT3 EUT4 Start End POS0 POS1 POS2 POS4 POS3 ETSI ETSI T... |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 4.1.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. 3) EUT1, EUT2 and EUT3 act as vehicle. 4) EUT1, EUT2 and EUT3 are moving. |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 4.1.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... |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 4.2 Ports and ASPs (Abstract Services Primitives) | |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 4.2.1 Introduction | Two ports are used by the GeoNetworking ATS: • The geoNetworkingPort, of type GeoNetworkingPort • The utPort of type UpperTesterPort • The hmiPort of type HmiPort End2 POS2 Start1 End1 POS1 POS3 Start2 ETSI ETSI TS 103 192-3 V1.2.1 (2022-02) 10 |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 4.2.2 Primitives of the geoNetworkingPort | Two types of primitives are used in the geoNetworkingPort: • The geoNetworkingInd primitive used to receive messages of type GeoNetworkingPacket • The geoNetworkingReq primitive used to send messages of type GeoNetworkingPacket |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 4.2.3 Primitives of the utPort | This port uses two types of primitives: • The UtGnInitialize primitive used to initialize EUT • The UtTrigger primitive used trigger upper layer events in EUT |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 4.2.4 Primitives of the hmiPort | This port uses two types of primitives: • The HmiInitialize primitive used to initialize HMI EUT • The HmiTrigger primitive used trigger upper layer events in HMI EUT |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 4.2.5 Primitives of the taPort | This port uses the following primitives to trigger special behaviour in Test adapter: • AcStartBeaconing: Test adapter shall start sending beacon messages for a simulated ITS node • AcStopBeaconing: Test adapter shall stop sending beacon messages for a simulated ITS node • AcStartPassBeaconing: Test adapter shall trans... |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 5 Untestable Test Purposes | Table 1 gives a list of TP, which are not implemented in the ATS due to the restriction of the chosen ATM. Table 1: Untestable TP Test purpose Reason None ETSI ETSI TS 103 192-3 V1.2.1 (2022-02) 11 |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 6 ATS conventions | |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 6.1 Introduction | The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS. The ATS conventions contain two clauses, the testing conventions an... |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 6.2 Testing conventions | |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 6.2.1 Testing states | |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 6.2.1.1 Initial state | All test cases start with the function f_prInitialState. This function brings the EUT in an "initialized" state by invoking the upper tester primitive UtInitialize. |
4edb75e6f4ad78671fe7cead6bdeed6f | 103 192-3 | 6.2.1.2 Final state | All test cases end with the function f_poDefault. This function brings the EUT back in an "idle" state. As no specific actions are required for the idle state in the base standard, the function f_ poDefault does not invoke any action. As necessary, further actions may be included in the f_poDefault function. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.