hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7.2.6 DEN message - Geo-broadcast message caching | Caching On-link Off-link Figure 12: Geo-broadcast message caching scenario TD Id TD_AUTO_IOT_DENM_GMC_BV_01 Test scenario Verify complete Geo-broadcast message caching scenario - See Figure 12 Reference ETSI EN 302 636-4-1 [1], clause 9.3.11, annex D and clause E.2 Config Id CF-01 with EUT4 off-link PICS Selection Pre-... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7.2.7 CA message - Neighbours detection | TD Id TD_AUTO_IOT_CAM_NBD_BV_01 Test scenario Verify complete neighbours detection scenario based on CA messages and/or beacons Reference ETSI EN 302 637-2 [2] Config Id CF-03 PICS Selection Pre-test conditions • EUT1, EUT2 and EUT3 send CA/beacon messages Test sequence Test Sequence: Step Type Description 1 stimulus E... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7.2.8 CA message - Collision Risk Warning | TD Id TD_AUTO_IOT_CAM_CRW_BV_01 Test scenario Verify complete longitudinal collision risk scenario based on CA messages Reference ETSI EN 302 637-2 [2] Config Id CF-02 PICS Selection Pre-test conditions • EUT1 (vehicle) sends CA messages, C1 • EUT1 (vehicle) is moving slowly between positions POS1 and POS2 • EUT2 (vehi... |
3b939c9b7e64657a9a866654d0a2656b | 103 192-2 | 7.2.9 GN message - Duplicate address detection | TD Id TD_AUTO_IOT_GN_DAD_BV_01 Test scenario Verify complete resolution of duplicate address conflict scenario based on GN messages Reference ETSI EN 302 636-4-1 [1], clause 9.2.1.5 Config Id CF-01 PICS Selection Pre-test conditions • EUT1 (vehicle) and EUT2 (vehicle) are configured with the same GN address • EUT1 (veh... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 1 Scope | The present document describes key performance indicators and benchmarking methods for the spectrum of potential applications. All access technologies offered by the operator under test are considered. The offer of new NGN services requires new: • KPIs; • QoS measurement; and • benchmarking methods which are needed to ... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 2 References | |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 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... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 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... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 3 Definition of terms, symbols and abbreviations | |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 3.1 Terms | For the purposes of the present document, the terms given in Recommendation ITU-T E.800 [1] and the following apply: benchmark: evaluation of performance value/s of a parameter or set of parameters for the purpose of establishing value/s as the norm against which future performance achievements may be compared or asses... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 3.2 Symbols | Void. |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAC Advanced Audio Coding CS Circuit Switched GSMA GSM Association HDTV High-Definition Television HEVC High Efficiency Video Coding HTTP HyperText Transfer Protocol IP Internet Protocol IPDV IP Delay Variation IPLR IP Packet Loss Ratio IPTD I... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 4 Management Summary | The assessment of IPTV QoS and QoE from an end-user perspective is performed through MOS values for the video and audio signals in the transmitted streams while using the set-top box and the associated remote control. A benchmark shall be the evaluation of performance value/s of a parameter or set of parameters for the... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5 Reference Benchmarking | |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.1 Introduction | To determine the quality of IPTV, WebTV and RCS-e the following measurement values are determined. Table 1: Overview of quality benchmarks for IPTV measurements IPTV 1. IPTV Quality (Recommendations ITU-T P.1201 [4], P.1202 [6]) 2. IPTV STB Startup Response Time 3. IPTV STB Startup Time 4. IPTV STB Startup Failure Rati... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.2 IPTV Quality | |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.2.1 Audiovisual quality | The IPTV audiovisual quality is estimated by bitstream/parametric models, which have no access to a reference signal (see note) and are therefore called non-intrusive. An audiovisual, packet-header-based quality model is described in Recommendation ITU-T P.1201.2 [5] and two differently complex bitstream-based video qu... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.2.2 Functional QoS parameters of the video channel | One functional QoS parameter of the video channel is recommended in this case, namely streaming service access time. It is defined as follows: where tstream request is the time when a stream is requested and treception of first data packet is the time when a first data packet is received. Table 4 shows trigger points, ... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.2.3 Network performance parameters in the video channel | The following parameters between UNI and UNI in both directions of transmission shall be monitored during the period when the end-to-end audiovisual quality and QoS parameters are being tested: • UNI-to-UNI one way packet delay over time. • UNI-to-UNI one way packet delay variation over time. • UNI-to-UNI one way packe... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.3 IPTV benchmark measurements | |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.3.1 IPTV STB Startup Response Time | This measurement is used to show the time in milliseconds needed for the first communication between the Set-Top Box (STB) and the IPTV headend. IPTV STB Startup Response Time is defined in the context of the present document as the time that elapses from the sending of the first packet of the STB to the receipt of the... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.3.2 IPTV STB Startup Time | This measured value shows the time in seconds which a set-top box requires to start from the standby mode. IPTV STB Startup Time is defined in the context of the present document as the time from the sending of the infrared code for the switch-on signal to the set-top box until the video on the first channel shown afte... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.3.3 IPTV STB Startup Failure Ratio | If the trigger points defined in Figure 1 are not detected during the test, the STB Startup is regarded as unsuccessful. The ratio of failed starts of the STB to the total initiated starts of STB is represented by the STB failure ratio as a percentage. Figure 1: Measurement of the IPTV STB Startup Time |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.3.4 IPTV Zapping Response Time | This measured value shows the time in milliseconds which is needed for the first communication between the Set-Top Box (STB) and the IPTV headend during a channel change. STB IPTV zapping response time is defined in the context of the present document as the time which elapses from the sending of the first packet of th... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.3.5 IPTV Zapping Time | This measuring value shows the time in milliseconds that is required for a channel change. IPTV Zapping Time is defined as the time that elapses from the sending of the infrared code for a channel change to the set-top box until the video on the requested channel is fluently played (this event is called "Full Screen" i... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.3.6 IPTV Zapping Failure Ratio | The Zapping Failure Ratio depicts the ratio of failed channel changes to the total initiated channel changes, as a percentage. |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.3.7 IPTV Packet Loss | The IPTV Packet Loss defines the number of lost IPTV packets of an IPTV stream in percent. Correction mechanisms are taken into account and only the packets are reported that are actually lost. IPTV Continuity Error Video/Audio: The IPTV Continuity Error is calculated from the Continuity Counter of the MPEG-TS Header a... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.3.8 IPTV Bitrate Video/Other/Total | The IPTV Bitrate in Mbit/s is divided into: 1) video bitrate 2) other 3) total The video bitrate and the other bitrate are detected by the IPTV measuring unit. The total bitrate is calculated from the sum of the video bitrate and the other bitrate: The other bitrate includes both the audio and the data streams. |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.4 WebTV | |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.4.1 Introduction | There are two major delivery technologies for Web TV video, which result in two measurement scenarios that are similar in setup, but require different analysis. For Web TV streaming, the audiovisual content is typically encapsulated in the HTTP protocol and can include different media containers and codecs. For example... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.4.2 Progressive Download | |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.4.2.1 Introduction | The client requests a single resource from the server, which is downloaded progressively through HTTP until it is completely loaded. Client playback may begin when a playout buffer threshold is reached. Playback will stop when the playout buffer is depleted, e.g. due to bad network performance and buffer-emptying durin... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.4.2.2 WebTV Quality | The overall audiovisual quality is estimated using the approach described in Recommendation ITU-T P.1201 Amd. 2 [8], Appendix III which aims at estimating the overall quality impairments due to audio and video coding as well as initial loading time and rebuffering/stalling events. The model receives as input meta-infor... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.4.2.3 WebTV Initial Loading Time | This value corresponds to the time in milliseconds from the playback intent to the first start of the media presentation. Delays due to page loading and player initialization are not included. In other words, this corresponds to the time the user would see a "loading" indicator shown in the player window. |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.4.2.4 WebTV Number of Stalling Events | The number of stalling events in the session, excluding the initial loading time. |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.4.2.5 WebTV Average Duration of Stalling Events | The average duration of stalling events in the session, excluding the initial loading time. ETSI ETSI TS 103 222-4 V1.2.1 (2025-02) 15 |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.4.2.6 WebTV QoS parameters | The relevant QoS parameters for a Progressive Download WebTV service are described in [i.1], Table 1. The following parameters are identified: • Player IP Service Access Failure Ratio • Player IP Service Access Time • Player Download Cut-off Ratio • Player Download Time • Player Session Failure Ratio • Player Session T... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.4.3 Adaptive Streaming | |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.4.3.1 Introduction | Adaptive streaming is increasingly used in the context of web-based video delivery. Here, the client requests the media in several chunks from the server. Each chunk corresponds to a specific segment of the original media, encoded at a specific representation. Typically, individual segments are from 2 to 10 seconds lon... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.4.3.2 WebTV Quality | For adaptive streaming, the audiovisual quality model algorithm needs to factor in the possibility of fluctuating quality in addition to initial loading and stalling events. Hence, models targeted at progressive download services may not be accurate enough in their predictions. NOTE: For estimating the audiovisual MOS,... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.4.3.3 WebTVQoS parameters | The QoS parameters 1.1, the metrics defined in clause 5.4.2.2 are applicable to adaptive streaming services. |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.5 RCS-e Video Share | |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.5.1 Introduction | Rich Communications Suite enhanced, abbreviated RCS-e and branded under the name "joyn" is a technical standard for communication services published by the industry association of international mobile operators (GSMA). Among other things, the standard enables the transmission of text messages, files, voice, and video. ... |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.5.2 RCS-e Video Share Setup Time | To determine the Video Share Setup Time, the time in seconds is measured from the SIP INVITE message of the Video Share on the smartphone on the "A" side until arrival of the SIP 200 OK message on the "A" side. ETSI ETSI TS 103 222-4 V1.2.1 (2025-02) 17 Figure 4: Measurement of the Video Share Setup Time |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.5.3 RCS-e Video Share Setup Failure Ratio | If the trigger points defined in Figure 4 are not detected during the test, the RCS-e Video Share Setup is deemed to have failed. The ratio of failed Video Share Setups to the total Video Share Setups initiated is represented by the Video Share Setup Failure Ratio as a percentage. |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.5.4 RCS-e Bitrate Video/Total | The RCS-e Bitrate in Mbit/s is divided into Bitrate for Video Share and Total. The Bitrate Video and Bitrate Total are detected by the RCS-e measuring unit. The Bitrate Total is the entire bitrate of the stream. |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.5.5 RCS-e Video Share I-/P-/B-Slices | The number of RCS-e I-/P-/B Slices are captured from the H.264 video stream and represented as a percentage frequency. ETSI ETSI TS 103 222-4 V1.2.1 (2025-02) 18 |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.5.6 RCS-e Video Share Packet Loss | The RCS-e packet loss defines the number of lost IP packets of a RCS-e stream in percent. Here, correction mechanisms are taken into account and only the packets are shown that are actually lost. |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.5.7 RCS-e Video Quality Score | The RCS-e Video Quality Score is measured according to Recommendation ITU-T P.1201 [4]. |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.5.8 RCS-e Video Share Drop Ratio | The ratio of dropped Video Shares to the total number of connections initiated is represented by the RCS-e Video Share Drop Ratio as a percentage. |
cf200c3844efca0e8107959c532b9038 | 103 222-4 | 5.5.9 RCS-e Video Share Failure Ratio | If the trigger points defined in Figure 5 are not detected during the test, or the video is not received within 10 seconds, the RCS-e Video Share is deemed to have failed. The ratio of failed Video Shares to the total number of Video Shares initiated is represented by the RCS-e Service Failure Ratio as a percentage. Fi... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 1 Scope | The present document contains the Abstract Test Suite (ATS) for MAPEM-SPATEM, IVIM, SREM-SSEM and RTCMEM as defined in ETSI TS 103 301 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.7]. The objective of the present document is to provide a basis ... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 2 References | |
cc9d79129d7224a4502e04d31754e370 | 103 191-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... |
cc9d79129d7224a4502e04d31754e370 | 103 191-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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 3 Definition of terms, symbols and abbreviations | |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 3.1 Terms | For the purposes of the present document, the terms given ETSI TS 103 301 [1], ISO/IEC 9646-1 [i.4] and in ISO/IEC 9646-7 [i.7] apply. |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 3.2 Symbols | Void. |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN Abstract Syntax Notation ASP Abstract Services Primitives ATM Abstract Test Method ATS Abstract Test Suite BI Invalid Syntax or Behaviour Tests BV Valid Behaviour tests CA Certification Authority DSRC Dedicated Short-Range Communications E... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4 Abstract Test Method (ATM) | |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.1 Abstract protocol tester | The abstract protocol tester used by this test suite is described in figure 1. The test system simulates valid and invalid protocol behaviour, and analyses the reaction of the IUT. ETSI ETSI TS 103 191-3 V1.3.1 (2021-11) 9 Figure 1: Abstract protocol tester - MAPEM SPATEM case |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.2 Test Configuration | This test suite uses a unique test configuration in order to cover the different test scenarios. In this configuration, the tester simulates one ITS station implementing the MAPEM SPATEM protocol. |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.3 Test architecture | The present document implements the general TTCN-3 test architecture described in ETSI EG 202 798 [i.1], clauses 6.3.2 and 8.3.1. Figure 2 shows the test architecture used in for the MAPEM SPATEM ATS case. The MAPEM SPATEM test component requires using only the Main Test Component (MTC). The MTC communicates with the M... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4 Ports and ASPs (Abstract Services Primitives) | |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4.1 Introduction | Two ports are used by the MAPEM SPATEM ATS: • The mapemSpatemPort, of type MapemSpatemPort. • The utPort, of type UpperTesterPort. Two ports are used by the IVIM ATS: • The ivimPort, of type IvimPort. • The utPort, of type UpperTesterPort. Two ports are used by the SREM SSEM ATS: • The sremSsemPort, of type SremSsemPor... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4.2 MAPEM SPATEM ATS | |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4.2.1 Primitives of the mapemSpatemPort | Four types of primitives are used in the mapSpatPort: • The MapemInd primitive used to receive messages of type MapemMsg (MAPEM_PDU + RawData). • The SpatemInd primitive used to receive messages of type SpatemMsg (SPATEM_PDU + RawData). • The MapemReq primitive used to send messages of type MAPEM_PDU. • The SpatemReq p... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4.2.2 Primitives of the utPort | This port uses six types of primitives: • The UtInitialize primitive used to initialize IUT. • The UtMapemSpatemTrigger primitive used to trigger upper layer events in IUT. • The UtInitializeResult primitive used to receive upper layer result of initialization in IUT. • The UtMapemSpatemTriggerResult primitive used to ... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4.3 IVIM ATS | |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4.3.1 Primitives of the ivimPort | Two types of primitives are used in the ivimPort: • The ivimInd primitive used to receive messages of type IvimMsg (IVIM_PDU + RawData). • The IvimReq primitive used to send messages of type IVIM_PDU. These two primitives use the IVIM_PDU type, which is declared in the ETSI_TS_103301.asn ASN.1 module contained in the a... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4.3.2 Primitives of the utPort | This port uses five types of primitives: • The UtInitialize primitive used to initialize IUT. • The UtIvimtrigger primitive used to trigger upper layer events in IUT. • The UtInitializeResult primitive used to receive upper layer result of initialization in IUT. • The UtIvimTriggerResult primitive used to receive upper... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4.4 SREM SSEM ATS | |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4.4.1 Primitives of the mapemSsemPort | Four types of primitives are used in the mapSpatPort: • The SremInd primitive used to receive messages of type SremMsg (SREM_PDU + RawData). • The SsemInd primitive used to receive messages of type SsemMsg (SSEM_PDU + RawData). • The SremReq primitive used to send messages of type SREM_PDU. • The SsemReq primitive used... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4.4.2 Primitives of the utPort | This port uses six types of primitives: • The UtInitialize primitive used to initialize IUT. • The UtSremSsemTrigger primitive used to trigger upper layer events in IUT. • The UtInitializeResult primitive used to receive upper layer result of initialization in IUT. • The UtSremSsemTriggerResult primitive used to receiv... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4.5 RTCMEM ATS | |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4.5.1 Primitives of the rtcmemPort | Two types of primitives are used in the mapSpatPort: • The RtcmemInd primitive used to receive messages of type RtcmmMsg (RTCMEM_PDU + RawData). • The RtcmmReq primitive used to send messages of type RTCMEM_PDU. These two primitives use the RTCMEM_PDU type, which is declared in the ETSI_TS_103301.asn ASN.1 module conta... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.4.5.2 Primitives of the utPort | This port uses five types of primitives: • The UtInitialize primitive used to initialize IUT. • The UtRtcmemTrigger primitive used to trigger upper layer events in IUT. • The UtInitializeResult primitive used to receive upper layer result of initialization in IUT. • The UtRtcmmTriggerResult primitive used to receive up... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.5 Executing CA tests in secured mode | All the CA tests, with the exeception of the SSP tests, can be executed with security enabled or with security disabled. The choice of running the CA tests in secured or non-secured mode has no impact on the result of the CA tests because the test verdicts assess CA protocol behaviour only. The SSP tests can only be ex... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 4.6 ETSI test adapter | All information of the ETSI test adapter is described in ETSI TR 103 099 [i.3]. |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 5 Untestable Test Purposes | Table 1 gives a list of TPs, which are not implemented in the ATS Road & Lane Topology due to the chosen ATM or other restrictions. Table 1: Untestable TPs for Road & Lane Topology Test purpose Reason TC_IS_RLT_GEN_COM_BV_02 Removed TP_IS_RLT_GEN_SEC_BV_02 Security elements to be verified are part of Network & Transpor... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 6 ATS conventions | |
cc9d79129d7224a4502e04d31754e370 | 103 191-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... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 6.2 Testing conventions | |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 6.2.1 Testing states | |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 6.2.1.1 Initial state | All test cases start with the function f_prInitialState. This function brings the IUT in an "initialized" state by invoking the upper tester primitive UtInitialize. |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 6.2.1.2 Final state | All test cases end with the function f_poDefault. This function brings the IUT back in an "idle" state. As no specific actions are required for the idle state in ETSI TS 103 301 [1], the function f_poDefault does not invoke any action. As necessary, further actions may be included in the f_poDefault function. ETSI ETSI... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 6.2.2 Message types - ASN.1 definitions | ASN.1 definitions from ETSI TS 103 301 [1] are directly imported in TTCN-3 using the ASN.1 import method specified in ETSI ES 201 873-7 [i.10]. The following example shows the TTCN-3 import statement used to import ASN.1 definitions in the TTCN-3 modules: import from DSRC language "ASN.1:1997" all; Generic ASN.1 defini... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 6.3 Naming conventions | |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 6.3.1 Introduction | This test suite follows the naming convention guidelines provided in the ETSI EG 202 798 [i.1]. |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 6.3.2 General guidelines | The naming convention is based on the following underlying principles: • in most cases, identifiers should be prefixed with a short alphabetic string (specified in table 4) indicating the type of TTCN-3 element it represents; • suffixes should not be used except in those specific cases identified in table 2; • prefixes... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 6.3.3 ITS specific TTCN-3 naming conventions | Next to such general naming conventions, table 5 shows specific naming conventions that apply to the ITS TTCN-3 test suite. Table 5: ITS specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier ITS Module Use upper-case initial letter Its"IUTname"_ ItsMapemSpatem_ Module containin... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 6.3.4 Usage of Log statements | All TTCN-3 log statements use the following format using the same order: • Three asterisks. • The TTCN-3 test case or function identifier in which the log statement is defined. • One of the categories of log: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT. • Free text. • Three asterisks. EXAMPLE 1: log("*** " & test... |
cc9d79129d7224a4502e04d31754e370 | 103 191-3 | 6.3.5 Test Case (TC) identifier | Table 6 shows the test case naming convention, which follows the same naming convention as the test purposes. ETSI ETSI TS 103 191-3 V1.3.1 (2021-11) 18 Table 6: TC naming convention Identifier TP_<root>_<gr>_<dir>_<x>_<nn> <root> = root IS_TLM <dir> = direction GEN Message Generation behaviour RCV Message Receiving be... |
7d72f0431baea8a0831c08648909ba20 | 103 222-2 | 1 Scope | The offer of new NGN services requires new KPIs, QoS measurement and benchmarking methods which are needed to ensure the quality of new services. To ensure the comparability of test results, reference benchmarking methods and background traffic load profiles are needed. The present document describes key performance in... |
7d72f0431baea8a0831c08648909ba20 | 103 222-2 | 2 References | |
7d72f0431baea8a0831c08648909ba20 | 103 222-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... |
7d72f0431baea8a0831c08648909ba20 | 103 222-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... |
7d72f0431baea8a0831c08648909ba20 | 103 222-2 | 3 Definition of terms, symbols and abbreviations | |
7d72f0431baea8a0831c08648909ba20 | 103 222-2 | 3.1 Terms | For the purposes of the present document, the following term given in Recommendation ITU-T E.800 [1] applies: benchmark: evaluation of performance value/s of a parameter or set of parameters for the purpose of establishing value/s as the norm against which future performance achievements may be compared or assessed ETS... |
7d72f0431baea8a0831c08648909ba20 | 103 222-2 | 3.2 Symbols | Void |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.