hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.1.1.1.4 Incoming accepted calls list | Total number of 10 entries in the list. Table 3: Incoming accepted calls test list content Number Name Date Time Line name Line id 02298951214 J.LAGADEC 07/09/09 12:12:12 Provider 1 0, 0 0321259514 LE BIHAN 06/09/09 18:36:18 Provider 2 0, 1 0308980764 06/09/09 08:24:24 Provider 1 0, 0 0581321185 K.BORDONADO 06/09/09 08... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.1.1.1.5 All calls list | Total number of 30 entries in the list. ETSI ETSI TS 102 841 V1.5.1 (2014-01) 15 Table 4: All calls test list content Call Type Number Name Date and time Line name Line id Missed 497312456897 JENDREZEJZAK 09/09/09 06:45:00 Provider 1 0, 0 Outgoing 008989945270 UWE 08/09/09 13:13:13 Provider 1 0, 0 Accepted 02298951214 ... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.1.1.1.6 Contact list | Total number of 10 entries in the list. Table 5: Contact list test content Name First name Contact number1 Contact number2 (note 1) Associated Melody (note 2) Line id ALEXANDER Christian (fixed) 00441324778824 (work) 00449876543210 1 3, 2 ALEXANDER Christina (fixed) 00441324778812 2 3, 2 ALOUSSI RAMIN (fixed) 015689124... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.1.1.1.7 Internal names list | Total number of 4 entries in the list. Table 6: Internal names test list content Number Name Call interception 31H Kitchen 30H 32H Living-room 30H 33H Office 31H 39H Boby room 30H Properties - Number field: editable=0, internal=1, own=0 (see note), PIN code protected=0. - Name field: editable=1. - Call interception fie... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.1.1.1.8 DECT system settings list | Table 7: DECT system settings test list content Entry identifier Settings Editable PIN protected Value 1 Current PIN code 1 0 FFH, FFH, 12H, 34H Clock master 1 0 30H (FP) Base reset 1 1 30H (No) FP IP address / type 1 0 DHCP=0, Static=1 FP IP address / value 1 0 IPv4/6=0, 'C0A8D40C'H (192.168.212.12) FP IP address / su... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.1.1.1.9 Line settings list | Total number of 2 entries in the list. Table 8: Line settings test list content Entry identifier Settings Editable PIN protected Value 1 Line Name 1 0 "Provider VoIP1" Line id 0 0 3, 0 Attached handsets 1 1 Nb=03H, bitmap=03H, 82H (PP1, PP2, PP9) Dialling Prefix 1 0 "" FP melody 1 0 07H FP volume 1 0 30H Blocked number... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.1.1.1.10 All incoming calls list | Total number of 20 entries in the list. Table 9: All incoming calls test list content Number Name Date and time Unread Line name Line id Nb of calls 497312456897 JENDREZEJZAK 09/09/09 06:45:00 1 Provider 1 0, 0 2 02298951214 J.LAGADEC 07/09/09 12:12:12 0 Provider 1 0, 0 1 0145567897 06/09/09 18:48:00 1 Provider 1 0, 0 ... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.1.2 FP test platform | The fixed part under test shall be connected to a network when running the tests suite. It shall be ready to initiate an outgoing call or to receive an incoming call. An example of FP test platform is depicted on Figure 3. ETSI ETSI TS 102 841 V1.5.1 (2014-01) 20 NOTE 1: PP1 and PP2 behave either as a NG PP, a legacy G... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.1.2.1 List content for tests | When running List access FP test cases, the 'Current PIN code' field shall be set to (FFH, FFH, 12H, 34H). Thus, the test equipment can automatically edit and save the 'Current PIN code' field of 'DECT system settings' list before editing 'PIN protected' field (see Clause 5.1). |
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.1.3 NG-DECT Part 1 backward compatibility test platform | It is crucial to ensure interoperability between NG-DECT Part 3 devices and legacy NG-DECT Part 1 devices. In order to gain maximum interoperability to the NG-DECT Part 1 devices a test against the legacy Golden Devices (FT and PT) is absolutely necessary. In order to keep the required effort as low as possible, it is ... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.2 Hypothesis | Protocol layers tested Network and application features are only tested. DLC, MAC, and PHY procedures used by new DECT generation standard are supposed to be tested when testing network features. Speech services tested Device under test is required to support only mandatory speech services. The optional codecs are out ... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.3 Test groups | |
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.3.1 Network features | See TS 102 527-3 [14], Clauses 5.2, 6.4 and 6.10. |
730619fa10ecf5a507276e670e1be223 | 102 841 | 4.3.2 Application features | See TS 102 527-3 [14], Clauses 5.7, 6.9 and 6.13. |
730619fa10ecf5a507276e670e1be223 | 102 841 | 5 Test Cases (TCs) | |
730619fa10ecf5a507276e670e1be223 | 102 841 | 5.1 TC definition conventions | The TCs are defined following particular rules as shown in Table 10. Table 10: TC definition rules TC Id according to the TC naming conventions Test case objective Reference: The reference should contain the references of the subject to be validated by the actual TC (specification reference, clause, paragraph, flow cha... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 5.1.1 Test equipment implementation requirements | This clause specifies the general requirements to be implemented by the test equipment. The requirements listed below can be valid either for several features on one side, or for one feature on both sides, PP and FP side. Specific requirements for a single feature are given in the related section describing the sub tes... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 5.2 TC naming conventions | Each feature to be tested corresponds to a group of test cases identified by its standard feature number. The identifier of the TC is built according to Table 11. Table 11: TC naming convention TC_<rt>_<fn>_<tt>_<ppnn> <rt> = type of radio termination FT Fixed radio Termination PT Portable radio Termination <fn> = feat... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 5.3 Portable Part TC purposes | 5.3.1 List of New Generation DECT Part 3 PT tests cases related to NG-DECT Part 1 features This clause gives the list of NG-DECT Part 3 test cases related to the DECT "Wideband speech" (part 1) (TS 102 527-1 [13]) features. In other words, theses test cases shall be implemented with the NG-DECT Part 3 requirements (see... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 5.3.2 List of New Generation DECT Part 3 PT tests cases | This clause gives the list of NG-DECT Part 3 test cases related to the DECT "Extended Wideband Speech Services" (TS 102 527-3 [14]) features. Table 13: NG-DECT Part 3 PT Test Case Index NG-DECT Part 3 PT test case index Test Group Reference Test Case Id Description Status NG1.N.1 Codec negotiation M TC_PT_NG1.N.1 TC_PT... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 5.4 Fixed Part TC purposes | 5.4.1 List of New Generation DECT Part 3 FT tests cases related to NG-DECT Part 1 features This clause gives the list of NG-DECT Part 3 test cases related to the DECT "Wideband speech" (part 1) (TS 102 527-1 [13]) features. In other words, theses test cases shall be implemented with the NG-DECT Part 3 requirements (see... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 5.4.2 List of New Generation DECT Part 3 FT tests cases | This clause gives the list of NG-DECT Part 3 test cases related to the DECT "Extended Wideband Speech Services" (TS 102 527-3 [14]) features. Table 15: NG-DECT Part 3 FT Test Case Index NG-DECT Part 3 FT test case index Test Group Reference Test Case Id Description Status NG1.N.1 Codec negotiation M TC_FT_NG1.N.1 TC_FT... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6 Portable Part Test specification | This clause includes lists of the test groups relevant for a NG-DECT portable part. Test cases are ordered like network features followed by application features (TS 102 527-3 [14], Clauses 6.4 and 6.9). |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.1 TC_PT_NG1.N.1 Codec negotiation tests cases | Test subgroup objectives: to check the IUT's behaviours when negotiating a codec. TC_PT_NG1.N.1_BV_101 NG-DECT Part 1 capability during subscription registration Reference: TS 102 527-1 [13], Clauses 7.3.1 and 7.3.7 EN 300 175-5 [5], Clause 7.7.41 Initial condition: No access rights. Stimulus: A44 set to 1 on TS_1. Per... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.2 TC_PT_NG1.N.2 Codec switching tests cases | Test subgroup objectives: to check the IUT's behaviours during codec switching. TC_PT_NG1.N.2_BV_101 Codec switching from G.722 to G.726 Reference: TS 102 527-1 [13], Clauses 7.3.4, 7.3.5, D.1.4.1 and Figure D.10 Initial condition: T-10 (IUT+TS_1) in G.722 Stimulus: Perform a codec change from TS_1 Pass criteria: Verif... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.3 TC_PT_NG1.N.3 Missed call notification tests cases | Test subgroup objectives: to check the IUT's behaviours when receiving missed call notification. TC_PT_NG1.N.3_BV_201 Missed call notification, activation Reference: TS 102 527-3 [14], Clause 7.4.1.3, Table 15 Initial condition: T-00 Stimulus: Send a {FACILITY} message with IE <<EVENTS NOTIFICATION= <Missed call, A new... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.6 TC_PT_NG1.N.6 Parallel calls tests cases | Test subgroup objectives: to check the IUT's behaviours regarding parallel calls common requirements taking into account the following considerations: • As NG1.N.6_2 "Control messages" and NG1.N.6_3 "Sending keypad information" procedures are tested implicitly when testing NG1.N.7 "Common parallel call procedures (exte... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.8 TC_PT_NG1.N.8 Call transfer tests cases | Test subgroup objectives: to check the IUT's behaviours regarding call transfer procedures. In the following test cases, TS_1 plays the role of a FP where a virtual NG PP2 is registered TC_PT_NG1.N.8_BV_101 Call transfer (external) – announced Reference: TS 102 527-3 [14], Clauses 7.4.3.6 and 7.4.15.2.1 Initial conditi... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.10 TC_PT_NG1.N.10 Intrusion call tests cases | Test subgroup objectives: to check the IUT's behaviours regarding Intrusion call. Declarations (see Annex A): • NG1.N.10 "Intrusion call" feature is optional on PP side, so the manufacturer shall declare if it is supported. • If the call intrusion feature is supported, supplier shall declare at least one of the 2 follo... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.12 TC_PT_NG1.N.12 Line identification tests cases | Test subgroup objectives: to check the IUT's behaviours regarding line identification with the following consideration: • NG1.N.12_7 "Line identification for a first external incoming call" is tested with NG1.N.13_3 "Call identifier assignment on incoming call (FP to PP)" procedure. TC_PT_NG1.N.12_BV_201 Line identific... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.13 TC_PT_NG1.N.13 Call identification tests cases | Test subgroup objectives: to check the IUT's behaviours regarding call identification with the following consideration: • NG1.N.13_1 "Call identification general requirements" and NG1.N.13_4 "Call status indication to the handset (FP to PP)" procedures are tested with NG1.N.13_2 "Call identifier assignment on outgoing ... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.14 TC_PT_NG1.N.14 Multiple lines tests cases | Test subgroup objectives: to check the IUT's behaviours regarding multiple lines with the following consideration: • NG1.N.14_1 "Multiple lines general requirements" procedure requires that PP implements NG1.N.7 "Common parallel call procedures (external or internal)" feature. So there is no test case defined for this ... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.15 TC_PT_NG1.N.15 Multiple calls tests cases | Test subgroup objectives: to check the IUT's behaviours regarding multiple calls procedures with the following consideration: • NG1.N.15_1 "Multiple calls general requirements" procedure requires that PP implements NG1.N.7 "Common parallel call procedures (external or internal)" feature. So there is no test case define... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.16 TC_PT_NG1.N.16 List access service tests cases | Test subgroup objectives: to check the IUT's behaviours regarding list access service procedures with the following considerations: • NG1.N.6_2 "List change notification" procedure is not tested because there is no requirement on PP side related to the expected behaviour of the PP when it is notified. • As "Negative Ac... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.19 TC_PT_NG1.N.19 DTMF handling tests cases | Test subgroup objectives: to check the IUT's behaviours regarding DTMF handling with the following considerations: • As NG1.N.19_3 "Downlink DTMF reception" procedure includes only FP requirements, there is no test case defined for this procedure. • As NG1.N.19_4 "Local DTMF feedback of dialled digits" procedure includ... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.20 TC_PT_NG1.N.20 Tones provision tests cases | Test subgroup objectives: to check the IUT's behaviours regarding tone provision with the following considerations: • The PT shall support two methods for providing tones: IE <<SIGNAL>> signal method (NG1.N.20_2 "Tones provision by the system" procedure) and in band method (NG1.N.20_3 "Transparency to tones provision b... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.21 TC_PT_NG1.N.21 Headset management tests cases | Test subgroup objectives: to check the IUT's behaviours regarding headset management with the following consideration: • As NG1.N.21_6 "Switching headset to handset (headset initiated)" procedure is tested together with NG1.N.21_3 "Headset incoming call" procedure, there is no test case defined for this procedure. Decl... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.24 TC_PT_GAP.N.31 Internal call tests cases | Test subgroup objectives: to check the IUT's behaviours when handling internal call with the following consideration: • As GAP.N.31_2 "Internal call keypad" is tested implicitly when testing GAP.N.31_1 "Internal call setup", there is no test case defined for this procedure. • As GAP.N.31_5 "UTF-8 CNIP" is tested implic... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.26 TC_PT_GAP.N.35 Enhanced security tests cases | Test subgroup objectives: to check the IUT's behaviours regarding Enhanced security features with the following consideration: • As GAP.N.35_4 "subscriptions requirements" procedure specifies only FP requirements, there is no test case defined for this procedure. Test equipment implementation requirements for enhanced ... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.27 TC_PT_NG1.A.1 Easy PIN code registration tests cases | Test subgroup objectives: to check the IUT's behaviours regarding easy PIN-code registration. Declarations (see Annex A): • NG1.A.1_3 "Base station name selection" procedure is optional. So the manufacturer shall declare if it is supported. TC_PT_NG1.A.1_BV_101 Registration mode automatic access Reference: TS 102 527-3... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.28 TC_PT_NG1.A.2 Easy pairing registration tests cases | Test subgroup objectives: to check the IUT's behaviours regarding easy pairing registration taking into account the following considerations: • As NG1.A.2_1 "Easy pairing description" is tested implicitly when testing NG1.A.2_4 "Searching mode request", there is no test case defined for this procedure. • As NG1.A.2_2 "... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 6.29 TC_PT_NG1.A.3 Handset locator tests cases | Test subgroup objectives: to check the IUT's behaviours regarding handset locator. TC_PT_NG1.A.3_BV_101 Handset locator Reference: TS 102 527-3 [14], Clause 7.10.2 Initial condition: T-00, IUT ringing capabilities enabled Stimulus: Send a {CC-SETUP} message from TS_1 with IE <<BASIC-SERVICE>> specifying <Call class = N... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7 Fixed Part Test specification | This clause includes lists of the test groups relevant for a NG-DECT fixed part. Test cases are ordered like network features followed by application features (TS 102 527-3 [14], Clauses 6.4 and 6.9). The NG-DECT fixed part under test shall be connected to a network when running the tests suite. |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.1 TC_FT_NG1.N.1 Codec negotiation tests cases | Test subgroup objectives: to check the IUT's behaviours when negotiating a codec. TC_FT_NG1.N.1_BV_101 Exchange of codec list during subscription registration Reference: TS 102 527-1 [13], Clauses 7.3.1 and 7.3.7 Initial condition: F-00. Stimulus: Perform an access rights request from TS_1 Pass criteria: Verify that th... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.2 TC_FT_NG1.N.2 Codec switching tests cases | Test subgroup objectives: to check the IUT's behaviours during codec switching with the following consideration: • As a codec change initiates by a PP during an established communication does not correspond to a common use case, there is no test case defined for this feature on FP side. |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.3 TC_FT_NG1.N.3 Missed call notification tests cases | Test subgroup objectives: to check the IUT's ability to handle missed call notification with the following consideration: • NG1.N.3_2 "Missed call notification" procedure is also tested when testing NG1.N.16_17 "Missed calls list" procedure due to the "Simultaneous 'list change indication'" requirement. TC_FT_NG1.N.3_B... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.5 TC_FT_NG1.N.5 Date and time synchronization tests cases | Test subgroup objectives: to check the IUT's behaviours regarding date and time synchronization. TC_FT_NG1.N.5_BV_101 FT initiated Date and Time synchronization Reference: TS 102 527-3 [14], Clauses 7.4.2.1 and 7.4.2, Table 16 Initial condition: F-00, "Clock master" field equal to "FP" Stimulus: Provide date and time t... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.6 TC_FT_NG1.N.6 Parallel calls tests cases | Test subgroup objectives: to check the IUT's behaviours regarding parallel calls common requirements with the following consideration: • As NG1.N.6_2 "Control messages" and NG1.N.6_3 "Sending keypad information" procedures are tested implicitly when testing NG1.N.7 "Common parallel call" procedures (external or interna... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.8 TC_FT_NG1.N.8 Call transfer tests cases | Test subgroup objectives: to check the IUT's behaviours regarding call transfer. Test equipment implementation requirements in case the call transfer fails Test equipment shall allow implementations, where after final pass criteria, the IUT represents the original call to the TS_1 (as an incoming CC-SETUP) in case the ... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.10 TC_FT_NG1.N.10 Intrusion call tests cases | Test subgroup objectives: to check the IUT's behaviours regarding Intrusion call. Declarations (see Annex A): • NG1.N.10 "Intrusion call" feature is optional on FP side, so the manufacturer shall declare if it is supported. • When NG1.N.14 "Multiple lines" procedure is declared, following behaviours and corresponding t... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.12 TC_FT_NG1.N.12 Line identification tests cases | Test subgroup objectives: to check the IUT's behaviours regarding line identification with the following considerations: • NG1.N.12_3 "Line identification for a first external outgoing call using <<CALL-INFORMATION>> IE" procedure in {CC-SETUP} message is tested with NG1.N.13_2 "Call identifier assignment on outgoing c... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.13 TC_FT_NG1.N.13 Call identification tests cases | Test subgroup objectives: to check the IUT's behaviours regarding call identification with the following consideration: • NG1.N.13_1 "Call identification general requirements" and NG1.N.13_4 "Call status indication to the handset (FP to PP)" procedures are tested with NG1.N.13_2 "Call identifier assignment on outgoing ... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.14 TC_FT_NG1.N.14 Multiple lines tests cases | Test subgroup objectives: to check the IUT's behaviours regarding multiple lines with the following considerations: • NG1.N.14_1 "Multiple lines general requirements" procedure requires that FP implements NG1.N.7 "Common parallel call procedures (external or internal)" feature. So there is no test case defined for this... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.15 TC_FT_NG1.N.15 Multiple calls tests cases | Test subgroup objectives: to check the IUT's behaviours regarding multiple calls procedure. Declarations (see Annex A): Following behaviours and corresponding test cases are exclusive: • FP implements 'non early CC-CONNECT': TC_FT_NG1.N.15_BV_205. • FP implements 'early CC-CONNECT':TC_FT_NG1.N.15_BV_206. TC_FT_NG1.N.15... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.16 TC_FT_NG1.N.16 List access service tests cases | Test subgroup objectives: to check the IUT's behaviours regarding list access service procedures with the following considerations: • Some test cases shall be run in a given order. In that case, the test case reference to be run before is indicated in the initial condition. • NG1.N.6_2 "List change notification" proced... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.19 TC_FT_NG1.N.19 DTMF handling tests cases | Test subgroup objectives: to check the IUT's behaviours regarding DTMF handling with the following considerations: • There is no test case defined for NG1.N.19_1 "Uplink DTMF transmission at call setup when FP connected to classic switching network" procedure and for NG1.N.19_2 "Uplink DTMF transmission when connected"... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.20 TC_FT_NG1.N.20 Tones provision tests cases | Test subgroup objectives: to check the IUT's behaviours regarding tones provision procedures. Declarations (see Annex A): • NG1.N.20_2 "Tones provision by the system" procedure and NG1.N.20_3 "Transparency to tones provision by the network or PABX" procedure are exclusive for external call, so the manufacturer shall de... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.21 TC_FT_NG1.N.21 Headset management tests cases | Test subgroup objectives: to check the IUT's behaviours regarding headset management with the following consideration: • As NG1.N.21_1 "Headset considerations" is tested implicitly when running NG1.A.1 "Easy PIN-code registration" test cases, there is no test case defined for this procedure. • As NG1.N.21_3 "Headset in... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.24 TC_FT_GAP.N.31 Internal call tests cases | Test subgroup objectives: to check the IUT's behaviours when handling internal call with the following consideration: • As GAP.N.31_2 "Internal call keypad" is tested implicitly when testing NG1.N.7 "Common parallel call procedures (external or internal)", there is no test case defined for this procedure. TC_FT_GAP.N.3... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.26 TC_FT_GAP.N.35 Enhanced security tests cases | Test subgroup objectives: to check the IUT's behaviours regarding Enhanced security features with the following consideration: • As GAP.N.35_5 "Enhanced security regarding legacy devices" procedure is tested when testing GAP.N.35_1 "Encryption of all calls" procedure, there is no test case defined for this procedure. •... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.27 TC_FT_NG1.A.1 Easy PIN code registration tests cases | Test subgroup objectives: to check the IUT's behaviours regarding easy PIN-code registration taking into account the following considerations: • As NG1.A.1_3 "Base station name selection" is tested when testing NG1.A.2_5 "Base station name selection", there is no test case defined for this procedure in following clause... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.28 TC_FT_NG1.A.2 Easy pairing registration tests cases | Test subgroup objectives: to check the IUT's behaviours regarding easy pairing registration taking into account the following considerations: • As NG1.A.2_6 "Registration user feedback" is tested when testing NG1.A.1_4 "Registration user feedback", there is no test case defined for this procedure. Declarations (see Ann... |
730619fa10ecf5a507276e670e1be223 | 102 841 | 7.29 TC_FT_NG1.A.3 Handset locator tests cases | Test subgroup objectives: to check the IUT's behaviours regarding handset locator. Declarations (see Annex A): • NG1.A.3 "Handset locator" feature is optional on FP side, so the manufacturer shall declare if it is supported. ETSI ETSI TS 102 841 V1.5.1 (2014-01) 293 TC_FT_NG1.A.3_BV_101 Handset locator Reference: TS 10... |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 1 Scope | The present document provides the Test Suite Structure and Test Purposes (TSS&TP) for Transmission of IP packets over GeoNetworking as defined in ETSI EN 302 636-6-1 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.4]. The ISO standard for the meth... |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 2 References | |
23979cc9c958e19be81c08d280342f2a | 102 859-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... |
23979cc9c958e19be81c08d280342f2a | 102 859-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... |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 3 Definition of terms, symbols and abbreviations | |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 302 636-6-1 [1], ISO/IEC 9646-1 [i.2] and in ISO/IEC 9646-7 [i.4] apply. |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 3.2 Symbols | Void. |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: BI Invalid Behaviour BV Valid Behaviour DEPV Destination Position Vector DGVL Dynamic Geographical Virtual Link EUI Extended Unique Identifier EVI Expired virtual interfaces GVL Geographical Virtual Link HT Header Type IID Interface Identifier... |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 4 Test Suite Structure (TSS) | |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 4.1 Structure for IPV6overGEONET tests | Table 1 shows the IPV6overGEONET Test Suite Structure (TSS) including its subgroups defined for conformance.testing. Table 1: TSS for IPV6overGEONET Root Group Sub-group category IPv6GEO Message Generation GVL Valid behaviour TVL Valid behaviour Message Reception GVL Valid behaviour TVL Valid behaviour Virtual Interfac... |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 4.2 Test groups | |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 4.2.1 Root | The root identifies the Transmission of IP packets over GeoNetworking given in ETSI EN 302 636-6-1 [1]. |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 4.2.2 Groups | This level contains three functional areas identified as: Message Generation, Message Reception, and Virtual Interface Management. |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 4.2.3 Sub-groups | This level contains four sub-functional areas identified as: GVL, TVL, New virtual interfaces, and Expired virtual interfaces. |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 4.2.4 Categories | This level contains the standard ISO conformance test categories limited to the valid behaviour. ETSI ETSI TS 102 859-2 V1.3.1 (2022-02) 8 |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5 Test Purposes (TP) | |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.1 Introduction | |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.1.1 TP definition conventions | The TPs are defined by the rules shown in table 2. Table 2: TP definition rules TP Header TP ID The TP ID is a unique identifier. It shall be specified according to the TP naming conventions defined in clause 5.1.2. Test objective Short description of test purpose objective according to the requirements from the base s... |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.1.2 TP Identifier naming conventions | The identifier of the TP is built according to table 3. Table 3: TP naming convention Identifier: TP/<root>/<gr>/<sgr>/<x>/<nn> <root> = root IPv6GEO IPv6 over GeoNetworking <gr> = group MG Message Generation MR Message Reception VM Virtual Interface Management <sgr> = subgroup GVL GVL TVL TVL NVI New virtual interface... |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.1.3 Rules for the behaviour description | The description of the TP is built according to ETSI EG 202 798 [i.1]. |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.1.4 Sources of TP definitions | All TPs shall be specified according to ETSI EN 302 636-6-1 [1]. ETSI ETSI TS 102 859-2 V1.3.1 (2022-02) 9 |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.1.5 Mnemonics for PICS reference | To avoid an update of all TP tables when the PICS document is changed, the following table introduce mnemonics name and the correspondence with the real PICS item number. Table 4: Mnemonics for PICS reference Mnemonic PICS item PICS_SGVL A.6/1 [2] PICS_DGVL A.6/2 [2] PICS_TVL A.6/3 [2] PICS_Ethernet A.7/1 [2] |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.2 Test purposes for IPV6overGEONET | |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.2.1 Message Generation | |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.2.1.1 GVL | TP Id TP/IPv6GEO/MG/GVL/BV/01 Test objective Checks that an IPv6 link-local multicast message is carried out over a GeoBroadcast message into the correct geographical area, when sent over an SGVL Reference ETSI EN 302 636-6-1 [1], clauses 8.2.1 and 9.2.1 PICS Selection PICS_SGVL Initial conditions with { the IUT having... |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.2.1.2 TVL | TP Id TP/IPv6GEO/MG/TVL/BV/01 Test objective Checks that an IPv6 unicast message is carried out over a GeoUnicast when using a TVL virtual interface with address resolution Reference ETSI EN 302 636-6-1 [1], clause 8.2.1 PICS Selection PICS_TVL Initial conditions with { the IUT having a configured TVL (TVL1) the IUT's ... |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.2.2 Message Reception | |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.2.2.1 GVL | TP Id TP/IPv6GEO/MR/GVL/BV/01 Test objective Checks handling of a received GeoBroadcast message containing an IPv6 packet, which has destination area corresponding to an existing SGVL of the IUT Reference ETSI EN 302 636-6-1 [1], clause 8.2.2 PICS Selection PICS_SGVL Initial conditions with { the IUT having configured ... |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.2.2.2 TVL | TP Id TP/IPv6GEO/MR/TVL/BV/01 Test objective Checks handling of a received link-local IPv6 Unicast message, when using a TVL associated to an NBMA type virtual interface Reference ETSI EN 302 636-6-1 [1], clause 8.2.2 PICS Selection PICS_TVL Initial conditions with { the IUT having a configured TVL (TVL1) } Expected be... |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.2.3 Virtual Interface Management | |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.2.3.1 New virtual interfaces | TP Id TP/IPv6GEO/VM/NVI/BV/01 Test objective Checks the Router Advertisement-triggered creation of a new SGVL associated to an Ethernet V2.0/IEEE 802.3™ [3] LAN type virtual interface Reference ETSI EN 302 636-6-1 [1], clauses 8.2.2 and 10.2.1 PICS Selection PICS_SGVL and PICS_Ethernet Initial conditions with { the IUT... |
23979cc9c958e19be81c08d280342f2a | 102 859-2 | 5.2.3.2 Expired virtual interfaces | TP Id TP/IPv6GEO/VM/EVI/BV/01 Test objective Checks the removal of an expired SGVL and its associated virtual interface Reference ETSI EN 302 636-6-1 [1], clause 8.2.2 PICS Selection PICS_SGVL and PICS_Ethernet Initial conditions with { the IUT having configured a SGVL (SGVL1) derived from a received RA } Expected beha... |
2d520303cd2976db96cb1a2e37effa96 | 102 859-1 | 1 Scope | The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for Conformance test specifications for Geonetworking Basic Transport Protocol as defined in TS 102 636-6-1 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-... |
2d520303cd2976db96cb1a2e37effa96 | 102 859-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... |
2d520303cd2976db96cb1a2e37effa96 | 102 859-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 636-6-1 (V1.1.1): "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 6: Internet Integration; Sub-part 1: Transmission of IPv6 Packets over GeoNetworking Protocols". [2] ISO/IEC... |
2d520303cd2976db96cb1a2e37effa96 | 102 859-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. Not applicable. ETSI ETSI TS 102 859-1 V1.1.1 (2011-03) 6 |
2d520303cd2976db96cb1a2e37effa96 | 102 859-1 | 3 Definitions and abbreviations |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.