hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
820e628e9b7939c14d7949fb74366cce | 102 950-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... |
820e628e9b7939c14d7949fb74366cce | 102 950-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... |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 3 Definition of terms, symbols and abbreviations | |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 3.1 Terms | For the purposes of the present document, the terms given in ISO/IEC 9646-1 [4], ISO/IEC 9646-7 [7], ETSI ES 201 873-1 [1] (TTCN-3) and the following apply: Abstract Test Method (ATM): description of how an IUT is to be tested, given at an appropriate level of abstraction to make the description independent of any part... |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 3.2 Symbols | Void. |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASCII American Standard Code for Information Interchange ATM Abstract Test Method ATS Abstract Test Suite BNF Backus-Naur Form ETS Executable Test Suite HTML HyperText Markup Language ICS Implementation Conformance Statement ISO International ... |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 4 Abstract Test Method (ATM) | This clause describes the ATM used to test the conformance of TTCN-3 tool implementations as described in part 1 of the TTCN-3 core language standard ETSI ES 201 873-1 [1]. In the ATM, the work is performed on two levels: • The TTCN-3 tool level. In TTCN-3 conformance tests, it is the TTCN-3 tool which is under test, i... |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 5 The ATS development process | |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 5.1 Requirements and test purposes | For each test purpose there is a table defined in clause A.2 of ETSI TS 102 950-2 [8]. The requirements applicable to this TP are given by a reference to ETSI ES 201 873-1 [1]. There are no explicit formulations of requirements. |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 5.2 ATS structure | |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 5.2.1 Test case grouping | The ATS structure defined in table 1 is based on the structuring of Test Purposes in clause A.2 of ETSI TS 102 950-2 [8]. The group names in columns 1 to 3 of table 1 are those assigned in the ATS; they are based on the names provided in clause A.2 of ETSI TS 102 950-2 [8], but use the naming conventions defined for th... |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 5.2.2 Test case identifiers | The test case names are built up according to the following scheme: <"TC">"_"<Group index>"_"<TC number> where: a) double quotes (") are used to enclose literal strings; b) <Group index> containing positive and negative syntactic and semantic test, refers to ETSI ES 201 873-1 [1] clause numbers and names; c) <TC number... |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 5.3 ATS specification framework | |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 5.3.1 Use of TTCN-3 | |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 5.3.1.1 General | TTCN-3, as defined in ETSI ES 201 873-1 [1], is used as the ATS specification language. A number of requirements have been identified for the development and production of the TTCN-3 specification for the ATS: 1) Top-down design. 2) A uniquely defined testing architecture and test method. 3) Uniform TTCN-3 style and na... |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 5.3.1.2 TTCN-3 naming conventions | Like in other software projects using a programming language, the use of naming conventions supports or increases: a) the readability; b) the detection of semantic errors; c) the shared work of several developers; d) the maintainability. The naming conventions applied to Reference Test suite ATS are based on the follow... |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 5.3.1.3 TTCN-3 comment tags | Any TTCN-3 definition in the Test Suite Repository or Library should contain embedded comment tags, according to ETSI ES 201 873-10 [2]. These comment tags can be used by tools to extract information from the TTCN-3 code to create, for example, a HTML-based reference documentation. Comment tags which cover one or more ... |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 5.4 ATS archive | Annex A contains the ATS archive (zip file expanding to text files with TTCN-3 code). |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 6 PIXIT conformance | A test realizer, producing an executable test suite for the Abstract Test Suite (ATS) specification, is required, as specified in ISO/IEC 9646-4 [5], to produce an augmented partial PIXIT pro forma conformant with this partial PIXIT pro forma specification. An augmented partial PIXIT pro forma which conforms to this pa... |
820e628e9b7939c14d7949fb74366cce | 102 950-3 | 7 ATS conformance | The test realizer, producing a Means Of Testing (MOT) and Executable Test Suite (ETS) for the present document, shall comply with the requirements of ISO/IEC 9646-4 [5]. In particular, these concern the realization of an Executable Test Suite (ETS) based on each ATS. The test realizer shall provide a statement of confo... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 1 Scope | The present document provides the Test Suite Structure and Test Purposes (TSS & TP) for the test specifications for the channel congestion control algorithms operating in the 5,9 GHz range as specified in TS 102 687 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in I... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 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... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 687: "Intelligent Transport Systems (ITS); Decentralized Congestion Control Mechanisms for Intelligent Transport Systems operating in the 5 GHz range; Access layer part". [2] ETSI TS 102 724: "Intelligent Trans... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 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. Not applicable. ETSI ETSI TS 102 917-2 V1.1.1 (2013-01) 7 |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 3 Definitions and abbreviations | |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 102 687 [1] and the following apply: Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [6]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [6]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [6]. IN: name of the interface be... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 102 687 [1], TS 102 724 [2] and the following apply: ACT ACTive state ASP Abstract Service Primitive ATS Abstract Test Suite CCH Control Channel CH CHannel DCC Decentralized Congestion Control DP DCC Profile ITS Intelligent Transport System ITS-G5 ... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 4 Test configurations | |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 4.1 Test architecture | The test architecture depicted in figure 1 is proposed. The aim of this test architecture is the testing of the access layer which acts as the implementation under test (IUT). As the MI_SAP is considered a non-observable interface the management entity is included in the system under test (SUT). ETSI ETSI TS 102 917-2 ... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 4.2 Radio Control and Observation Points | The following two testing reference points may be co-located in the same radio test equipment. |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 4.2.1 Radio Control Point PC_RTX | The radio point of control (PC) PC_RTX (Radio Transmission) will be used to trigger the entry of CCH and SCHs into the different DCC_access states. This is done via an Upper Tester (UT) that sends an abstract service primitives (ASP) of type SetDCC_AccessState to the Test System (TS). The UT will typically be realised ... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 4.2.1.1 SetDCC_AccessState - Description | This ASP is used to set the DCC_Access state. Management MI_SAP IN_SAP DCC Access A C - B E A C - B K A C - V O A C - V I PCO_IN PO_RRX PC_RTX SUT IUT ETSI ETSI TS 102 917-2 V1.1.1 (2013-01) 9 4.2.1.2 SetDCC_AccessState – Fields Table 1: SetDCC_AccessState Name Value Channel 0: CCH 1: SCH1 2: SCH2 3: SCH3 4: SCH4 State... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 4.2.2 Radio Observation Point PO_RRX | The radio point of observation (PO) PO_RRX (Radio Reception) will be used to examine the traffic generated by the SUT. This is done via a UT that receives ASPs of type Traffic_Characteristics from the TS. 4.2.2.1 Traffic_Characteristics – Description This ASP is used to report the traffic characteristics. 4.2.2.2 Traff... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 4.3.1 IN_Request - Description | This ASP is used to request the transmission of frames on the radio interface, see also TS 102 723-010 [4] clause 5.2. ETSI ETSI TS 102 917-2 V1.1.1 (2013-01) 10 4.3.2 IN_Request – Fields Table 3: IN_Request Name Value Command reference Integer (0 to 255) Message Octetstring Requested send power Ptx Value in dBm DCC pr... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 4.3.3 IN_Status - Description | This ASP is used to report the status related to the transmission (or non-transmission) of frames on the radio interface, see also TS 102 723-010 [4] clause 5.4. 4.3.4 IN_Status – Fields Table 4: IN_Status Name Value Command reference Integer(0 to 255) Channel 0: CCH 1: SCH1 2: SCH2 3: SCH3 4: SCH4 Transmission success... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5 Test Suite Structure (TSS) and Test Purposes (TP) | |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.1 Test Suite Structure | |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.1.1 TP naming convention | TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. ETSI ETSI TS 102 917-2 V1.1.1 (2013-01) 11 Table 5: TP identifier naming convention scheme Identifier: <TP>_<channel>_<channel_state>_<nn> <tp> = Test Purpose: fixed to "TP" <config> = STS for single transceiver station MTS... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.1.2 Test strategy | As the base standards TS 102 687 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard of TS 102 723-3 [3], T S 102 723-10 [4] and TS 102 724 [2] and of the PICS specification TS 102 917-1 [5]. |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.1.3 TP structure | Each TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPs more readable and checkable. A particular structure has been used which is illustrated in table 6. Table 6 should be read in conjunction with any TP, i.e. please use a TP as an example to facilitate the... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2 Test Purposes | All PICS items referred to in this clause are as specified in TS 102 917-1 [5] unless indicated otherwise by another numbered reference. PICS items are only meant for test selection, therefore only PICS items with status optional or conditional are explicitly mentioned. |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.1 Single Transceiver ITS Station Tests | |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.1.1 CCH in the relaxed channel state | TP Id TP_STS_REL_01 Test objective Verify that the single transceiver IUT can correctly send frames with priority VAL_DP at a rate of VAL_Message_Interval on the CCH in state relaxed when PTx < PCCH_rel. Reference 5.4.3.2, table 1 PICS Selection A.2/1 Initial conditions CCH = Relaxed PCCH_rel = PICS A.5/1 PTx = PIXIT_P... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.1.2 CCH in the active channel state | TP Id TP_STS_ACT_01 Test objective Verify that the single transceiver IUT can correctly send frames with priority VAL_DP at a rate of VAL_Message_Interval on the CCH in state active when PTx < PCCH_act. Reference 5.4.3.2, table 1 PICS Selection A.2/1 Initial conditions CCH = Active PCCH_act = PICS A.5/2 PTx = PIXIT_PTx... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.1.3 CCH in the restrictive channel state | TP Id TP_STS_RES_01 Test objective Verify that the single transceiver IUT can correctly send frames with priority VAL_DP at a rate of VAL_Message_Interval on the CCH in state restrictive when PTx < PCCH_res. Reference 5.4.3.2, table 1 PICS Selection A.2/1 Initial conditions CCH = Restrictive PCCH_res = PICS A.5/3 PTx =... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.2.1 CCH related tests | |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.2.1.1 CCH in variable channel states | TP Id TP_MTS_CCH_01 Test objective Verify that the multiple transceivers IUT can drop frames with priority VAL_DP when the request frame rate is higher than the maximum allowed VAL_Message_Interval of the CCH in state VAL_State_CCH and with SCH1 in state VAL_State_SCH1. Reference 5.4.3.2, table 1, table 2 PICS Selectio... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.2.1.2 CCH in the active channel state | TP Id TP_MTS_ACT_01 Test objective Verify that the multiple transceivers IUT can transmit frames with priority VAL_DP on CCH and SCH1 when the request frame rate is higher than the maximum allowed VAL_Message_Interval of the CCH in state active and with SCH1 in state VAL_State_SCH1. Reference 5.4.3.2, table 1, table 2 ... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.2.1.3 CCH in the restrictive channel state | TP Id TP_MTS_RES_01 Test objective Verify that the multiple transceivers IUT can transmit frames with priority VAL_DP on CCH and SCH1 when the request frame rate is higher than the maximum allowed VAL_Message_Interval of the CCH in state restrictive and with SCH1 in state VAL_State_SCH1. Reference 5.4.3.2, table 1, tab... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.2.2 SCH1 related tests | |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.2.2.1 SCH1 in the relaxed channel state | TP Id TP_MTS_SCH1_01 Test objective Verify that the multiple transceiver IUT can correctly send frames with priority VAL_DP at a rate of VAL_Message_Interval on the SCH1 in state relaxed when PTx < PSCH1_rel. Reference 5.4.3.2, table 2 PICS Selection A.2/2, A.4/2 Initial conditions CCH = Status irrelevant SCH1 = Relaxe... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.2.2.2 SCH1 in the active channel state | TP Id TP_MTS_SCH1_05 Test objective Verify that the multiple transceiver IUT can correctly send frames with priority VAL_DP at a rate of VAL_Message_Interval on the SCH1 in state active when PTx < PSCH1_act. Reference 5.4.3.2, table 2 PICS Selection A.2/2, A.4/2 Initial conditions CCH = Status irrelevant SCH1 = Active ... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.2.2.3 SCH1 in the restrictive channel state | TP Id TP_MTS_SCH1_09 Test objective Verify that the multiple transceiver IUT can correctly send frames with priority VAL_DP at a rate of VAL_Message_Interval on the SCH1 in state restrictive when PTx < PSCH1_res. Reference 5.4.3.2, table 2 PICS Selection A.2/2, A.4/2 Initial conditions CCH = Status irrelevant SCH1 = Re... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.2.3 SCH2 related tests | |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.2.3.1 SCH2 in the relaxed channel state | TP Id TP_MTS_SCH2_01 Test objective Verify that the multiple transceiver IUT can correctly send frames with priority VAL_DP at a rate of VAL_Message_Interval on the SCH2 in state relaxed when PTx < PSCH2_rel. Reference 5.4.3.2, table 3 PICS Selection A.2/2, A.4/3 Initial conditions CCH = Status irrelevant SCH1 = Restri... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.2.3.2 SCH2 in the active channel state | TP Id TP_MTS_SCH2_05 Test objective Verify that the multiple transceivers IUT can correctly send frames with priority DP11 at a rate of 0,1 Hz on the SCH2 in state active when PTx < PSCH2_act. Reference 5.4.3.2, table 3 PICS Selection A.2/2, A.4/3 Initial conditions CCH = Status irrelevant SCH1 = Restrictive SCH2 = Act... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.3.1 CCH related tests | TP Id TP_G5B_CCH_01 Test objective Verify that the multiple transceivers IUT can drop all frames with priority DP4 when CCH is in a channel state other than the relaxed state. Reference 5.5.3, table 1, table 4, table 5 PICS Selection A.2/2, A.3/2 Initial conditions CCH = VAL_State_CCH SCH3 = Status irrelevant SCH4 = St... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.3.2 SCH3 related tests | |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.3.2.1 SCH3 in the relaxed channel state | TP Id TP_G5B_SCH3_01 Test objective Verify that the multiple transceiver IUT can correctly send frames with priority VAL_DP at a rate of VAL_Message_Interval on the SCH3 in state relaxed when PTx < PSCH3_rel. Reference 5.5.3, table 4 PICS Selection A.2/2, A.3/2, A.4/4 Initial conditions CCH = Status irrelevant SCH3 = R... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.3.2.2 SCH3 in the active channel state | TP Id TP_G5B_SCH3_05 Test objective Verify that the multiple transceiver IUT can correctly send frames with priority VAL_DP at a rate of VAL_Message_Interval on the SCH3 in state active when PTx < PSCH3_act. Reference 5.5.3, table 4 PICS Selection A.2/2, A3/2 A.4/4 Initial conditions CCH = Status irrelevant SCH3 = Acti... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.3.2.3 SCH3 in the restrictive channel state | TP Id TP_G5B_SCH3_10 Test objective Verify that the multiple transceiver IUT can correctly send frames with priority VAL_DP at a rate of VAL_Message_Interval on the SCH3 in state restrictive when PTx < PSCH3_res. Reference 5.5.3, table 4 PICS Selection A.2/2, A.3/2, A.4/4 Initial conditions CCH = Status irrelevant SCH3... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.3.3 SCH4 related tests | |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.3.3.1 SCH4 in the relaxed channel state | TP Id TP_G5B_SCH4_01 Test objective Verify that the multiple transceiver IUT can correctly send frames with priority VAL_DP on the SCH4 in state relaxed when PTx < PSCH4_rel. Reference 5.5.3, table 5 PICS Selection A.2/2, A.3/2, A.4/5 Initial conditions CCH = Status irrelevant SCH3 = VAL_State_SCH3 SCH4 = Relaxed PSCH4... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.3.3.2 SCH4 in the active channel state | TP Id TP_G5B_SCH4_04 Test objective Verify that the multiple transceiver IUT can correctly send frames with priority VAL_DP at a rate of VAL_Message_Interval on the SCH4 in state active when PTx < PSCH4_act. Reference 5.5.3, table 5 PICS Selection A.2/2, A3/2 A.4/5 Initial conditions CCH = Status irrelevant SCH3 = VAL_... |
26e19b85385d3b23663c7c72ee4a0818 | 102 917-2 | 5.2.3.3.3 SCH4 in the restrictive channel state | TP Id TP_G5B_SCH4_08 Test objective Verify that the multiple transceiver IUT can correctly send frames with priority VAL_DP at a rate of VAL_Message_Interval on the SCH4 in state restrictive when PTx < PSCH4_res. Reference 5.5.3, table 5 PICS Selection A.2/2, A3/2 A.4/5 Initial conditions CCH = Status irrelevant SCH3 =... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 1 Scope | The present document defines the functional architecture for the facilities layer of the ITS station as defined in [1] and provides functional requirements and specifications for main identified facilities. The identified facilities are required to support BSA as defined in [i.1]. Other proprietary facilities might be ... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 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... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI EN 302 665 (V1.1.1): "Intelligent Transport Systems (ITS); Communications Architecture". [2] ETSI EN 302 637-2: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 2: Specif... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 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 TR 102 638 (V1.1.1): "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Definitions". [i.2] ETSI TS 102 6... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 3 Definitions and abbreviations | |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in [1] and the following apply: application support: sub set of facilities, providing support elements for ITS applications backend systems: system that includes middleware in the generic domain, providing back end support and functions for BSA I... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AID Application identifier ALERT-C Advice and problem Location for European Road Traffic API Application Programming Interface ASN.1 Abstract Syntax Notation One BSA Basic Set of Application C2C-CC Car to Car Communication Consortium CA Cooper... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 4 ITS application overview | The overall ITS environment comprises ITS stations (ITS-S) that may communicate directly as follows: • From Vehicle to Vehicle, via ad-hoc (or cellular) communication or based on Infrastructure involvement; • From Vehicle to Infrastructure; and • From Infrastructure to Vehicle. ITS-Ss may communicate with each other th... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 4.1 ITS architecture and ITS stations | Four ITS-S types are defined in [1], namely: • Central ITS-S: A central ITS-S provides centralized ITS applications. A central ITS-S may play the role of traffic operator, road operator, services provider or content provider. Furthermore, a central ITS-S may require further connection with backend systems via e.g. Inte... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 4.2 Application layer overview | ITS applications are defined within the application layer. An ITS application makes use of the underlying facilities and communication capacities provided by the ITS-S. The applications layer provides ITS services. Three classes of applications have been defined in [i.1]: road safety, traffic efficiency and other appli... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 5 Facilities layer functional architecture | |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 5.1 ITS-S external gateways | In order to connect with external systems, an ITS-S may provide gateway functions for these external systems to exchange information with the facilities layer of the ITS-S. For BSA, one or multiple gateway functions may need to be developed in order to satisfy the application requirements. ETSI ETSI TS 102 894-1 V1.1.1... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 5.1.1 Vehicle ITS-S gateway to in vehicle network | For a vehicle ITS-S, the facilities layer is connected to the in-vehicle network via an in-vehicle data gateway as illustrated in figure 5.1. The facilities and applications of a vehicle ITS-S receive from this gateway the required in-vehicle data in order to construct messages (e.g. CAM and DENM) and for the applicati... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 5.1.2 Road side ITS-S gateway to central ITS-Ss | A roadside ITS-S is in general connected to a central ITS-S e.g. traffic management centre or road operator centre. In a possible road side ITS-S deployment scenario, road side ITS-Ss are managed by a private road infrastructure management network. Specific protocols for the traffic management, for the roadside equipme... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 5.1.3 Road side ITS-S or central ITS-S gateway to road equipment | An ITS applications may require data related to the traffic regulation (e.g. rail-road intersection, traffic light status, speed limit), or require support from the road side detection capacities (e.g. road side sensors). This requires that road side equipment exchanges information with central or roadside ITS-S. For e... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 5.1.4 ITS-S gateway to back end systems | An ITS-S (e.g. road side ITS-S or central ITS-S) may need to connect to a back end system via a generic networks such as Internet. The back end systems provide required services, service support or service content to the ITS-S in order to satisfy the requirements of the ITS applications. In a possible implementation, a... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 5.1.5 Personal ITS-S gateway to vehicle ITS station | When a personal ITS-S is located in a vehicle, this personal ITS-S may be considered as a vehicle ITS-S under the condition that the personal ITS-S satisfies some predefined requirements. In particular for a personal ITS-S to support the road safety applications, a connection to the vehicle electronics may be required.... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 5.2 Facilities layer functional architecture | The general functional architecture of the facilities layer is illustrated in figure 5.5. A set of facilities are identified in order to support the BSA, these facilities can be classified into two categories as below: • Common facilities: Common facilities provide basic core services to support the reliable operation ... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 5.3 List of facilities | Based on BSA functional requirements as provided in [i.2], a set of facilities are identified. The common facilities are listed in table 5.1, the domain facilities are listed in table 5.2. The present document provides functional descriptions for each of the facilities listed in table 5.1 and table 5.2, as well as the ... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6 Common facilities functional requirements | Common facilities are facilities that are required by the operation of the ITS-S and/or provide support for communication interoperability. Moreover, certain common facilities provide cross layer information to the management and the security entities as defined in [1], therefore, these common facilities are management... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.1 Management facilities functional requirements | |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.1.1 CF001: Traffic class management | This facility deals with assignment of a traffic class value to each message transmitted by the applications and facilities layer of an ITS-S. The traffic class level is used by the management layer to select the appropriate communication protocol and access technologies to be used for the message transmission. Further... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.1.2 CF002: ITS-S ID management | This facility manages the identifier of an ITS-S being used within the application and facilities layer of the ITS-S. The identifier of an ITS-S shall allow unambiguous identification of an ITS-S from other ITS-Ss in the network. Given the security and privacy protection requirements as identified in [i.5], this ITS-S ... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.1.3 CF003: AID Management | This common facility manages the Application Identifier (AID) being used within the application and facilities layer. An AID is the identifier of a message or the identifier of an ITS application. An AID can be updated and new AIDs can be added if the ITS-S is informed by an authorized application management entity whi... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.1.4 CF004: Security access | This common facility enables the data exchanges between the applications, the facilities layer and the security entity of the ITS-S. It provides the transmitted and received message or the application data to the appropriate security mechanism in the security entity that will process the message or data accordingly. De... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.2 Application support facilities functional requirements | |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.2.1 CF005: HMI support | This common facility provides gateway function between the ITS applications and the Human Machine Interface (HMI) devices equipped by an ITS-S. It enables the dispatching of the application information to the HMI devices. One or more ITS applications active in the ITS-S send application processing results to the HMI de... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.2.3 CF006: Time service | This common facility provides support for dealing with time and time synchronization for all available time stamped data being used within message and ITS applications. A common unified and standardized time reference is defined and used for all ITS-Ss. Referring to this common ITS time definition, different time stamp... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.2.4 CF007: Application/facilities status management | This common facility manages a list of available applications and facilities in the ITS-S. It also keeps the corresponding configuration information for each ITS application and facility. This common facility also monitors the functioning status of the applications and facilities of the ITS-S. In case of the malfunctio... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.2.5 CF008: Service announcement message (SAM) processing | This common facility supports the service management function of the management layer as specified in [i.4], it constructs and transmits the service announcement message (SAM) at the request of the ITS-S management layer, in order to announce the available user services as well as the communication access technology be... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.3 Information support facilities functional requirements | |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.3.1 CF009: Station type/capabilities | This common facility provides information to describe a profile of an ITS-S to be used in the applications and the facilities layer, in particular: • The ITS-S type: vehicle ITS-S, road side ITS-S, personal ITS-S or central ITS-S. • The role that is currently played by the ITS-S: operation status of an emergency vehicl... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.3.2 CF010: ITS-S positioning service | This common facility provides and updates the geographical positioning of an ITS-S in real time. Different technologies can be used to determine in real time the geographic position, with variable accuracy level. The Global Navigation Satellite System (GNSS) may be used as primary positioning means in the ITS co-operat... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.3.3 CF011: Location referencing | This common facility provides location referencing information of a geographic location that allows the association of a geographical location with regards to road network and surrounding environment. Depending on the application requirement(s), the information needed for location referencing may vary in different leve... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.3.4 CF012: Common data dictionary | This common facility manages a common data dictionary for data elements being commonly used in the messages and/or by the ITS applications and facilities e.g. vehicle data, position data, time, location referencing data, road topology data, traffic regulation data, etc. The data dictionary may be organized in multiple ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.