hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.3.3.1 Overview | Information exchanges related to the medical evacuation of casualties (see figure 4.2) are depicted in figure 5.5. The holding area serves as buffer for arriving transport vehicles and emergency teams. ETSI ETSI TS 103 260-1 V1.1.1 (2015-05) 31 Figure 5.5: Health service information exchanges |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.3.3.2 Treatment and medical evacuation | The main objective of a mass casualty incident (MCI) logistics in the incident area and of medical evacuation logistics is keeping track of all casualties. Rough knowledge of all casualties' current locations is desirable, but detailed movement patterns are not required. An overview of remaining casualties in vicinity ... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.3.3.3 Temporary shelter and evacuation | Information exchanges related to temporary shelters and coordination of evacuation are listed in table 5.15. ETSI ETSI TS 103 260-1 V1.1.1 (2015-05) 36 Table 5.14: Temporary Shelter and Evacuation Source to destination(s) Type of information Main communications service Main Requirements SECC relevant authority/NGO temp... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.4 Characteristics of Emergency Communication Services | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.4.1 Speech services | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.4.1.1 General | Speech services are currently the most instinctive and most used communication services in emergencies, and this is likely to remain the case for years to come. For speech services several universal requirements exist, characterized by: Speech intelligibility and quality: that received speech is capable of being unders... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.4.1.2 PMR group call channels | The number of required voice channels depends on the number of involved emergency service disciplines and the command structure: • 1 group call channel jointly used by ECC, CFECC, and all FECCs; • 1 group call channel jointly used by each emergency service's FECC and all assigned SECCs; ETSI ETSI TS 103 260-1 V1.1.1 (2... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.4.2 Paging (short message) services | Paging services are used by a variety of authorities in order to contact their personnel, and paging services are available from a variety of networks and technologies. The network needs to be able to identify the requested authorized emergency agent(s), and then deploy the appropriate technology to contact them. This ... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.4.3 Status monitoring and location services | Status monitoring includes a wide variety of parameters, e.g. breathing air tank levels, accountability monitoring, distress buttons and vital signs monitoring. Location services provide real-time information regarding the position of personnel or vehicles to an emergency team leader. This information may also include ... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.4.4 Data services | Data services are used to provide a large number of applications which can have widely differing requirements in terms of capacity, timeliness and robustness of the data service [i.7]. Ideally, the communication networks should support the required data throughput and minimize end-to-end delay, especially for applicati... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 6 Topology model | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 6.1 General | Topology modelling is generally used to represent a network's layout and dynamics mathematically in terms of the topology of the network nodes, represented here by the scenario actors. Algorithms may be chosen to depict properties such as the location and motion of the nodes, and whether nodes switch on/off during the ... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 6.2 Model graphics | Figure 4.1 in clause 4.2.1 shows the physical layout of the incident area (i.e. the future incident area) before the EQ takes place. It illustrates the places that will be affected and the associated actors. Figure 6.1 illustrates a snapshot of the ramp-up of the scenario, including the first response actions, but excl... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 6.3 Model specification | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 6.3.1 Scenario quantities | This clause specifies the topology of the actors and physical locations involved, together with their properties and parameters. An implementation of the reference topology of this type of event shall conform to the following model, made of a set of tables and illustrations. It is specified here in a top down approach,... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 6.3.2 Locations | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 6.3.2.1 On-site | Table 6.2: On-site locations Location Requirements on position Time-variant parameters Time-invariant parameters Hazard area(s) Inside incident area. made of residential and industrial areas. For simplicity, stationary hazard areas are considered only n/a Centre coordinates, size CCP Outside hazard area, inside inciden... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 6.3.2.2 Off-site | Table 6.3: Off-site locations Location Notes Time-variant parameters Time-invariant parameters Ambulance station(s) There is an ambulance station on-site (partially destroyed) Journey time to incident area (CCP, TCC, holding area) Capacity (number of teams / ambulances available) Fire station(s) Journey time to inciden... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 6.3.3 On-site actors | On-site actors and their properties are listed in table 6.4. The notation for the topology properties are as follows: /P: Position /M: Mobility /B: Start condition /MT: Mid-term step /E: Stop condition Table 6.4: On-site actors Actor Requirements on position and mobility Requirements on behaviour and presence on site (... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 1 Scope | The present document contains the Abstract Test Suite (ATS) for 464XLAT technology as defined in RFC 6052 [1] and RFC 6877 [2] which address specific cable industry requirements as defined in ETSI TS 101 569-1 [10] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IE... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 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... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] IETF RFC 6052: "IPv6 addressing of IPv4/IPv6 translators". [2] IETF RFC 6877: "464XLAT: Combination of Stateful and Stateless Translation". [3] ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection ... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 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] ETSI EG 202 798: "Intelligent Transport Systems (ITS); Testing; Framework for conformance and interoperability testing". |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 3 Definitions and abbreviations | |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 101 569-1 [10], ISO/IEC 9646-1 [3] and ISO/IEC 9646-7 [6] apply. |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply. ALG Application Layer Gateway ASP Abstract Services Primitives ATM Abstract Test Method ATS Abstract Test Suite CLAT Customer-side XLAT CPE Customer Premises Equipment DHCP Dynamic Host Configuration Protocol DNS Domain Name System FTP File Tr... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 4 Abstract test method | This clause describes the ATM used to test the 464XLAT technology. |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 4.1 Abstract protocol tester | An abstract protocol tester presented in figure 1 is a process providing the test behaviour for testing an IUT. Thus it will emulate an entity which is capable of proving the IUT functionalities. This type of test architecture provides a situation of communication which is equivalent to real operation between real devi... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 4.2 Test configurations | The test suite for 464XLAT uses only a test configuration to cover the different test . Distinction between the two configurations is given by the two main components in 464XLAT, which are the Customer side XLAT (CLAT) and the Provider side XLAT (PLAT). |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 4.2.1 CF01: CLAT as IUT | In this configuration, the CLAT is the IUT and the test system simulates an IPv6 client in one side and a IPv4 server in the other side. CLAT - IUT Test system (TTCN-3) IPv4 Host - Simulated IPv6 Host - Simulated Figure 3: CF01, CLAT equipment is the IUT ETSI ETSI TS 103 242-3 V1.1.1 (2014-12) 10 |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 4.2.2 CF02: PLAT as IUT | In this configuration, the PLAT is the IUT and the test system simulates an IPv6 client in one side and a IPv4 server in the other side. PLAT - IUT Test system (TTCN-3) IPv4 Host - Simulated IPv6 Host - Simulated Figure 4: CF02, PLAT equipment is the IUT |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 4.3 TTCN-3 Test architecture | In general, a conformance test system architecture based on TTCN-3 is as figure 5 shows. 464XLAT Test System Test control 464XLAT Abstract Test Suite Codec Test adaptor Upper tester transport 464XLAT lower Layers SUT Upper tester application 464XLAT IUT 464XLAT lower Layers Upper tester transport Upper tester transport... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 4.4 Ports and ASPs (Abstract Services Primitives) | |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 4.4.1 TTCN-3 ports | The 464XLAT Test Suite implements the following ports: • Ipv6Port, to send and receive IPv6 packets. • Ipv4Port, to send and receive IPv4 packets. • SipPort, to trigger the following SIP actions: authentication and data sending. It can monitor incoming traffic. • RstpPort, to trigger the following RSTP actions: session... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 4.4.2 Abstract Service Primitives | Abstract service primitives are commands or actions that need to be performed on the IUT in order to trigger certain behaviour or to obtain information about the IUT state. The list of ASP used in the 464XLAT ATS is shown in table 1. Table 1: 464XLAT Abstract Service Primitives TTCN-3 text Action/Command Description Ar... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 5 Implemented Test Purposes | Table 2 shows the test purposes from [9] which have been implemented and included in the present document. Table 2: Implemented Test Purposes TP Identifier TC Identifier Group Subgroup PICS Untestable Implemented TP/464XLAT/CLAT/BF/BV/01 TC_464XLAT_CLAT_BF_BV_01 CLAT Basic Function Yes TP/464XLAT/CLAT/FRAG/BV/01 TC_464... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 6 ATS conventions | 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. |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 6.1 Naming conventions | This test suite follows the naming convention guidelines provided in [7] and [i.1]. |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 6.1.1 General guidelines | The naming convention is based on the following underlying principles: • Identifiers should be prefixed with a short alphabetic string (specified in table 3) indicating the type of TTCN-3 element it represents. • Suffixes should not be used except in those specific cases identified in table 3. • Prefixes and suffixes s... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 6.1.2 464XLAT specific TTCN-3 naming conventions | In addition to such general naming conventions, table 4 shows specific naming conventions that apply to the 464XLAT technololy TTCN-3 test suite. Table 4: 464XLAT specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier 464XLAT Module Use upper-case initial letter Ats464XLAT_ Ats4... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 6.1.3 Usage of Log statements | All TTCN-3 log statements use the following format: • Three asterisks followed by a blank character. • The TTCN-3 test case or function identifier in which the log statement is defined followed by a colon and a blank character. • One of the log categories: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT followed by a... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 6.1.4 Test Case (TC) identifier | The identifier of the TC is built according to table 5 as recommended in [7]. Table 5: TC naming convention for 464XLAT TC_<root>_<gr>_<sgr>_<x>_<nn> <root> = root 464XLAT 464XLAT <gr> = group CLAT CLAT as IUT PLAT PLAT as IUT <sgr> = sub-group BF Basic Function FRAG Fragmentation MSSC MSS Clamping NP NAT Pools AW Addr... |
1c21433cb30ff4a9ed91039ffb8ebd41 | 103 242-3 | 6.2 On line documentation | Using the T3D tool enables providing on-line documentation browser in HTML, by tagging TTCN-3 comments. These tags are defined in table 6. Table 6: TTCN-3 comment tags Tag Description @author Specifies the names of the authors or an authoring organization which either has created or is maintaining a particular piece of... |
43482e0dcacb34901bf97bce3440639b | 103 254 | 1 Scope | The purpose of the present document is to provide Test Suite Structure and Test Purposes (TSS&TP) for the conformance test suite for using XML and JSON Schema with TTCN-3 as defined in ETSI ES 201 873-1 [5] in compliance with the relevant guidance given in the pro forma for TTCN-3 reference test suite ETSI TS 102 995 [... |
43482e0dcacb34901bf97bce3440639b | 103 254 | 2 References | |
43482e0dcacb34901bf97bce3440639b | 103 254 | 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... |
43482e0dcacb34901bf97bce3440639b | 103 254 | 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... |
43482e0dcacb34901bf97bce3440639b | 103 254 | 3 Definition of terms, symbols and abbreviations | |
43482e0dcacb34901bf97bce3440639b | 103 254 | 3.1 Terms | For the purposes of the present document, the terms given in ISO/IEC 9646-1 [2], ISO/IEC 9646-7 [3], ETSI ES 201 873-1 [5] (TTCN-3) and the following apply: Abstract Test Suite (ATS): test suite composed of abstract test cases ICS pro forma: document, in the form of a questionnaire, which when completed for an implemen... |
43482e0dcacb34901bf97bce3440639b | 103 254 | 3.2 Symbols | Void. |
43482e0dcacb34901bf97bce3440639b | 103 254 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ATS Abstract Test Suite ICS Implementation Conformance Statement IUT Implementation Under Test IXIT Implementation eXtra Information for Testing JSON JavaScript Object Notation TC Test Case TCI TTCN-3 Control Interface ETSI ETSI TS 103 254 V1.... |
43482e0dcacb34901bf97bce3440639b | 103 254 | 4 Test Suite Structure (TSS) | The Test Suite Structure is in close alignment with ETSI ES 201 873-9 [1], containing: a) positive tests ("Pos_" test case name prefix); b) negative tests ("Neg_" test case name prefix). The execution order of the TTCN-3 tool conformance test cases is specified in the dependencies section of test purpose descriptions. ... |
b5457b8be983093e6711d5c33606672d | 103 253 | 1 Scope | The present document provides the Implementation Conformance Statement (ICS) pro forma for the conformance test suite for using XML and JSON Schema with TTCN-3 as defined in ETSI ES 201 873-1 [i.1] in compliance with the relevant guidance given in the pro forma for TTCN-3 reference test suite ETSI TS 102 995 [4]. In th... |
b5457b8be983093e6711d5c33606672d | 103 253 | 2 References | |
b5457b8be983093e6711d5c33606672d | 103 253 | 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... |
b5457b8be983093e6711d5c33606672d | 103 253 | 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... |
b5457b8be983093e6711d5c33606672d | 103 253 | 3 Definition of terms, symbols and abbreviations | |
b5457b8be983093e6711d5c33606672d | 103 253 | 3.1 Terms | For the purposes of the present document, the terms given in ISO/IEC 9646-1 [3], ISO/IEC 9646-7 [2], ETSI ES 201 873-1 [i.1] (TTCN-3) and the following apply: Abstract Test Suite (ATS): test suite composed of abstract test cases ICS pro forma: document, in the form of a questionnaire, which when completed for an implem... |
b5457b8be983093e6711d5c33606672d | 103 253 | 3.2 Symbols | Void. |
b5457b8be983093e6711d5c33606672d | 103 253 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ATS Abstract Test Suite ICS Implementation Conformance Statement IUT Implementation Under Test IXIT Implementation eXtra Information for Testing ETSI ETSI TS 103 253 V1.7.1 (2022-06) 7 JSON JavaScript Object Notation SUT System Under Test TS T... |
b5457b8be983093e6711d5c33606672d | 103 253 | 4 Conformance requirement concerning ICS | If it claims to conform to the present document, the actual ICS pro forma to be filled in by a supplier shall be technically equivalent to the text of the ICS pro forma given in annex A, and shall preserve the numbering/naming and ordering of the pro forma items. An ICS which conforms to the present document shall be a... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 1 Scope | The present document contains the Abstract Test Suite (ATS) for DS-Lite technology as defined in RFC 6333 [1] and addressing specific cable industry requirements as defined in ETSI TS 101 569-1 [11] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [5]. Th... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 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... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] IETF RFC 6333: "Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion". [2] ISO/IEC 9646-1 (1994): "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part ... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 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] ETSI EG 202 798: "Intelligent Transport Systems (ITS); Testing; Framework for conformance and interoperability testing". |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 3 Definitions and abbreviations | |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 101 569-1 [11], ISO/IEC 9646-1 [2] and ISO/IEC 9646-7 [5] apply. |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply. 3GPP Third Generation Partnership Project AFTR Address Family Transition Router ASP Abstract Services Primitives ATM Abstract Test Method ATS Abstract Test Suite B4 (DS-Lite) Basic Bridging BroadBand element CPE Customer Premises Equipment DHC... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 4 Abstract test method | This clause describes the ATM used to test the DS-Lite technology. |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 4.1 Abstract protocol tester | An abstract protocol tester presented in figure 1 is a process providing the test behaviour for testing an IUT. Thus it will emulate an entity which is capable of proving the IUT functionalities. This type of test architecture provides a situation of communication which is equivalent to real operation between real devi... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 4.2 Test configurations | The test suite for DS-Lite uses two test configurations in order to cover the different test scenarios. Distinction between the two configurations is given by the two main components in DS-Lite, which are B4 and AFTR. |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 4.2.1 CF01: B4 as IUT | In this configuration, the B4 is the IUT and the test system simulates an AFTR in one side and a IPv4 host in the other side. Figure 3: CF01, B4 equipment is the IUT B4 - IUT Test system (TTCN-3) Host - Simulated AFTR - Simulated Test System IPv4/IPv6 Ethernet System Under Test DS-Lite Functionality IPv4/IPv6 Ethernet ... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 4.2.2 CF02: AFTR as IUT | In this configuration, the AFTR is the IUT and the test system simulates a B4 equipment in one side and an IPv4 host in the other side. Figure 4: CF02, AFTR equipment is the IUT |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 4.3 TTCN-3 Test architecture | In general, a conformance test system architecture based on TTCN-3 is as figure 5 shows. Figure 5: Global test architecture The "System Under Test" (SUT) contains: • The "Implementation Under Test" (IUT), i.e. the object of the test. • The "Upper tester application" enables to trigger or capture some actions (i.e. high... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 4.4 Ports and ASPs (Abstract Services Primitives) | |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 4.4.1 TTCN-3 ports | The DS-Lite Test Suite implements the following ports: • Ipv6Port, to send and receive IPv6 packets. • Ipv4Port, to send and receive IPv4 packets. • DnsPort, to send and receive DNS messages. • Dhcpv6Port, to send and receive DHCPv6 messages. • FtpPort, to trigger the following FTP actions: login, logout, and data send... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 4.4.2 Abstract Service Primitives | Abstract service primitives are commands or actions that need to be performed on the IUT in order to trigger certain behaviour or to obtain information about the IUT state. The list of ASP used in the DS-Lite ATS is shown in table 1. Table 1. DS-Lite Abstract Service Primitives TTCN-3 text Action/Command Description Ar... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 5 Implemented Test Purposes | Table 2 shows the test purposes from ETSI TS 103 241-2 [10] which have been implemented and included in the present document. ETSI ETSI TS 103 241-3 V1.1.1 (2014-12) 14 Table 2: Implemented Test Purposes TP Identifier TC Identifier Group Subgroup PICS Untestable Implemented TP/DSLITE/B4/GWA/BV/001 TC_DSLITE_B4_GWA_BV_0... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 6 ATS conventions | 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. |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 6.1 Naming conventions | This test suite follows the naming convention guidelines provided in ISO/IEC 9646-6 [4] and ETSI EG 202 798 [i.1]. |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 6.1.1 General guidelines | The naming convention is based on the following underlying principles: • Identifiers should be prefixed with a short alphabetic string (specified in table 3) indicating the type of TTCN-3 element it represents. • Suffixes should not be used except in those specific cases identified in table 3. • Prefixes and suffixes s... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 6.1.2 DS-LITE specific TTCN-3 naming conventions | In addition to such general naming conventions, table 4 shows specific naming conventions that apply to the DS-Lite technology TTCN-3 test suite. Table 4: DS-LITE specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier Ds-Lite Module Use upper-case initial letter AtsDsLite_ AtsDs... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 6.1.3 Usage of Log statements | All TTCN-3 log statements use the following format: • Three asterisks followed by a blank character. • The TTCN-3 test case or function identifier in which the log statement is defined followed by a colon and a blank character. • One of the log categories: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT followed by a... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 6.1.4 Test Case (TC) identifier | The identifier of the TC is built according to table 5 as recommended in ETSI ETS 300 406 [6]. Table 5: TC naming convention for DS-Lite TC_<root>_<gr>_<sgr>_<x>_<nn> <root> = root DSLITE Dual-Stack Lite <gr> = group B4 B4 as IUT AFTR AFTR as IUT <sgr> = sub-group GWA Gateway Assignment BF Basic Function FRAG Fragmenta... |
6e4e6fbe2dae7bd4c42f9a86591a7acf | 103 241-3 | 6.2 On line documentation | Using the T3D tool enables providing on-line documentation browser in HTML, by tagging TTCN-3 comments. These tags are defined in table 6. Table 6: TTCN-3 comment tags Tag Description @author Specifies the names of the authors or an authoring organization which either has created or is maintaining a particular piece of... |
a87e1ef49a0ccda5a1fcab8ff4c3bad2 | 103 248 | 1 Scope | The present document defines port number values for the Basic Transport Protocol as specified in ETSI TS 103 836-5-1 [i.1]. |
a87e1ef49a0ccda5a1fcab8ff4c3bad2 | 103 248 | 2 References | |
a87e1ef49a0ccda5a1fcab8ff4c3bad2 | 103 248 | 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... |
a87e1ef49a0ccda5a1fcab8ff4c3bad2 | 103 248 | 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... |
a87e1ef49a0ccda5a1fcab8ff4c3bad2 | 103 248 | 3 Definition of terms, symbols and abbreviations | |
a87e1ef49a0ccda5a1fcab8ff4c3bad2 | 103 248 | 3.1 Terms | For the purposes of the present document, the following terms apply: destination port: port identifying the destination's protocol entity at the ITS facilities layer NOTE: Facilities layer services that do not expect replies either do not include a source port number in the header, or they set it to a default (usually ... |
a87e1ef49a0ccda5a1fcab8ff4c3bad2 | 103 248 | 3.2 Symbols | Void. |
a87e1ef49a0ccda5a1fcab8ff4c3bad2 | 103 248 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation One AT Authorization Ticket AVM Automated Vehicle Marshalling ETSI ETSI TS 103 248 V2.5.1 (2026-01) 7 BTP Basic Transport Protocol CA Cooperative Awareness CAM Cooperative Awareness Message CP Collective Percepti... |
a87e1ef49a0ccda5a1fcab8ff4c3bad2 | 103 248 | 4 Port number values for the Basic Transport Protocol | The Basic Transport Protocol (BTP) [i.1] multiplexes messages from the facilities layer to the networking & transport layer and de-multiplexes received GeoNetworking packets to corresponding entities in the facilities layer. At the networking & transport layer the messages need to be identified so that they can be deli... |
de34d3b9e0883c49b490a53d12878ff2 | 103 239-3 | 1 Scope | The present document contains the Abstract Test Suite (ATS) for MAP-E technology as defined in [1] and addressing specific cable industry requirements as defined in ETSI TS 101 569-1 [11] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [5]. The objective... |
de34d3b9e0883c49b490a53d12878ff2 | 103 239-3 | 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... |
de34d3b9e0883c49b490a53d12878ff2 | 103 239-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] Draft-ietf-softwire-map-12: "Mapping of Address and Port with Encapsulation (MAP)". [2] ISO/IEC 9646-1 (1994): "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Par... |
de34d3b9e0883c49b490a53d12878ff2 | 103 239-3 | 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] ETSI EG 202 798: "Intelligent Transport Systems (ITS); Testing; Framework for conformance and interoperability testing". |
de34d3b9e0883c49b490a53d12878ff2 | 103 239-3 | 3 Definitions and abbreviations | |
de34d3b9e0883c49b490a53d12878ff2 | 103 239-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 101 569-1 [11], ISO/IEC 9646-1 [2] and ISO/IEC 9646-7 [5] apply. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.