Interoperability/ Conformance Test dpmr Mode 3

Transcription

1 Interoperability/ Conformance Test dpmr Mode 3 IOP test Mode 3 Copyright 2016 dpmr Association All Rights Reserved Version 1.0

2 Revision History Version Date Change By 0v0 29th Dec 2015 Initial Draft for review BCS 0v1 7 th April 2016 Responses from members PH,ICOM 0v2 27 th July 2016 Correct minor typos. Response to comments received BCS 0v3 18 th Aug 2016 RF tests now reference the existing document on the TWG ftp site DJL 0v4 20 th Sept 2016 Review All issues resolved BCS 1v0 27 th Feb 2017 Issued following meeting DJL 1. Scope This document was developed by the dpmr Association Technical Working Group. The purpose of this document is to provide the summary of Interoperability Tests for dpmr Mode 3 (trunked) operation. The tests contained in this document are intended to establish that a) MS will operate with infrastructure compliant to TS b) TS compliant MS from different manufacturers will inter-operate with different manufacturers of infrastructure The tests shall verify the following operational functions Beacon Channel Acquisition - Beacon Channel format/ broadcasts, Channel Code - MS hunting - System identity Code - MS Registration, registration accepted/ registration denied Random Access (mask, withdrawn slot, backoff) Voice operation both individual and talkgroup, broadcast calls Status Short Data 2

3 In each profile a number of optional features are supported, which, if implemented, must conform to this document. 2. Contents 1. Scope Contents Abbreviations References Purpose of the Tests Test System Message Log Infrastructure Under Test Infrastructure Configuration Radio Terminals Under Test Radio Terminal Configuration Radio Terminal ID s and Talkgroups Multi-band equipment Default Test Conditions Receiver Input Signal Level Acquisition state Idle state Network Parameters Value of Channel Code MS Personality MS Allocated to a Payload Channel Test Suite/Test Cases Test Suite Control Channel Acquisition Non registering System Description Expected Behaviour Test Suite Registration Description Expected Behaviour Initial Conditions Procedure Test Suite Voice Call Service, Talkgroup Description Expected behaviour Initial conditions Procedure Test Suite Voice Call Service, Individual Description Expected behaviour Initial conditions Procedure Test Suite - Multi-site call to a talkgroup Description

4 7.5.2 Expected behaviour Initial conditions Procedure Test Suite Voice Call Service, Individual, Multi-Site Description Expected behaviour Initial conditions Procedure Test Suite Status Service Delivery Description Expected behaviour Initial conditions Procedure Test Suite Short Data Message Description Expected behaviour Initial conditions Procedure Annex A - System Identity Codes A.1 Syscodes Used for the IOP Tests A.1.1 Tiny A.1.2 Small A.1.3 Large A.1.4 Huge Abbreviations c CSF EUT IE ISF m MS MSID o REF RF TPI TS conditional Configured Services Functionality Equipment under test Information Element Initial Services Functionality mandatory Mobile Station (radio terminal) Identity of an MS optional Reference Unit Radio Frequency Talking Party Identification Trunked Station (either a TSCC or payload channel) 4. References [i] ETSI TS version [ii] dpmr Assoc ftp site dpmr-ftp\twg\published\dpmr RF Test_1v0.doc 4

5 5. Purpose of the Tests The IOP tests have been designed to establish that MS and infrastructure from different manufacturers interoperate. The test cases reflect the functionality specified in the appropriate clauses of TS [i]. Tests are grouped into sections where particular functions are being tested. For each section guidance is provided to describe the expected behaviour of the MS(s) and infrastructure. The manufacturer seeking IOP approval shall submit all information necessary to configure the equipment for personality changes. The tests rely on both observations of the MS behaviour and the logging of the Air Interface PDUs between the MS and TS. 6. Test System Test equipment that may be employed as a reference is not commercially available.. Manufacturer s however have developed proprietary devices that enable the Air Interface PDUs to be logged. Air Interface logging shall display and record a) MI bits(72) (clause 11.5[i]) b) CCH data(41) (clause and 11.2[i]) f down f down f up f down f up f down f up f up BASE STATION FIXED EQUIPMENT BASE STATION f up Radio Site #1 WIRE INTERFACE (UNDEFINED) WIRE INTERFACE (UNDEFINED) f down Radio Site #2 Air Interface Logger Figure 1: Test System In most test cases, a single site system is assumed consisting of a Beacon channel and a payload Channel. 6.1 Message Log The log shall contain the control channel message transactions of the MS and infrastructure recorded from start to finish of the test. The test log shall contain the specific test case number, followed by the test number. 5

6 At the time of testing, an inspection of the log file will determine if specific PDU s are contradicting the test case. In the case of these PDU s contradicting the test case the test is failed, otherwise it is passed assuming the test procedure has passed. 6.2 Infrastructure Under Test Unless explicitly stated, the test radio site shall consist of a Beacon channel and one Payload channel. It shall be possible to configure the infrastructure equipment so that a) The parameters listed in the tables in this section may be changed ; b) Registration required/registration not required may be configured. If the system is configured as a registering network, the TSCC may accept the registration ( [i]) or deny the registration ( [i]) ; c) From the Idle state(see 5.4.3) a call attempt to Individual MS and talkgroups may be permitted, or refused (by an appropriate C_NACKD PDU) Infrastructure Configuration This initial network and MS configuration timers shall be - Mnemonic Value Description Mode 3 Trand_TC - 5 seconds Timeout for MS attempting Random Access T_Nosig - 4 seconds Timeout for entering hunting procedures if the Beacon is no longer received T_EMERG_TMR - Token 14 (30 seconds) See table 5.49 T_DATA_TMR - Token 11 (15 seconds) See table 5.Error! Reference source not found. T_MS-MS_TMR - Token 11 (15 seconds) See table 5.Error! Reference source not found. T_MS-LINE_TMR - Token 20 (60 seconds) See table 5.Error! Reference source not found. TP_Timer - 30 seconds Timeout for a calling MS waiting for a call that requires a payload channel TNP_Timer - Timeout for a calling MS waiting for a call that does not require a 20 seconds payload channel T_Awake - 0,1 s to 60 s Time MS stays awake after receiving a message (in steps of 0,1 s) TV_Item - 30 seconds Payload Voice Maximum Item Timer TV_Inactive - 20 seconds Payload Voice Inactivity Timer TD_Inactive - 20 seconds Payload Data inactivity Timer TD_Item - 7 seconds Payload Packet Data Maximum Item Timer T_Pending - 60 seconds Timeout for called MS after receiving AHOY T_dereg - 1 second Timer to de-register before abandon in 0,1 second steps T_BS_Inactive seconds Timer to hibernate if no inbound activity on an unregulated Beacon T_DENREG - 0 The denied registration timer is inactive T_MS_Timing - 30 ms to 35 ms Range of MS timing for MS transmissions T_Emer_Barr - Time an MS who is not party to an emergency call shall wait for 20 seconds the emergency call to end 6

7 6.3 Radio Terminals Under Test While it is understood that radio terminals may be fitted with or without a display, for the purposes of IOP tests, a manufacturer is more able to demonstrate correct behaviour if a display model is used A method such as an LED or display ICON that indicates the radio terminal is transmitting An indication that the radio terminal is receiving a RF carrier such as an RSSI indicator The requirements of dpmr RF Tests.doc must be satisfied. See dpmr Association ftp site for latest version of this document (ref [ii]) Radio Terminal Configuration This initial network and MS configuration constants shall be Mnemonic Value Description Mode 3 Ndefault_NW - 5 Nrand_Wait at MS switch on Nrand_NR - Number of random access attempts for a normal and high priority 6 service Nrand_NE - Number of random access attempts for a emergency priority 10 service N_Discon - Number of Disconnect + End messages transmitted by an MS to 4 clear down the payload channel Nmax_Ch - 50 Minimum Number of channels in Short Hunt List Nlow_Comp_Ch - See BAND, SEP, FR, Lowest channel frequency in use by the network Nhigh_Comp_Ch - FT Highest channel frequency in use by the network Comp_Flag - True/False Suppress Comprehensive Hunt (seets Annex B) NSYSerr - Number of B_SYScodes received that differ from the value 1 verified dpmrla - 10 Length of SYS_AREA information field from the B_SYScode N_kill_cntr - Number of framesets between an authentication check and a kill 10 procedure M3N_PreserveV - Number of preservation frames to transmit before the BS clears 4 down the call and reverts to idle for a normal priority voice call M3N_PreserveE - Number of preservation frames to transmit before the BS clears 4 down the call and reverts to idle from inactivity for an emergency priority voice call M3N_PreserveD - Number of preservation frames to transmit before the BS clears 4 down the call and reverts to idle from inactivity for a data or status request call M3N_PreserveP - Number of preservation frames to transmit before the BS clears 4 down the call and reverts to idle from inactivity for a packet data call M3N_Preserve_PI - Number of preservation frames to transmit before the BS goes to 4 idle for an packet data acknowledgement Ch_Pref - 50 List of Beacons that are marked as preferred for Vote Now Radio Terminal ID s and Talkgroups Mode 3 Radio Terminals Radio Terminals Tested 7

8 Manufacturer Model and Description Serial Number Software Version MS(A) MS(B) MS(C) MS(D) MS(E) MS(F) 8

9 Talkgroups Talkgroup #1 Talkgroup #2 Talkgroup #3 Talkgroup #4 Talkgroup #5 Air Interface (hex) Dial Talkgroup Valid Y Y Y Y N Radio Terminal #1 [MS(A)] MSID Air Interface (hex) Dial MSID valid YES Member of Talkgroup #1 Talkgroup #2 Radio Terminal #1 [MS(A)] MSID Air Interface (hex) Dial MSID valid YES Member of Talkgroup #1 Talkgroup #2 Radio Terminal #2 [MS(B)] MSID Air Interface (hex) Dial MSID valid YES Member of Talkgroup #1 Talkgroup #3 Radio Terminal #3 [MS(C)] MSID Air Interface (hex) Dial MSID valid YES Member of Talkgroup #1 Talkgroup #3 Radio Terminal #4 [MS(D)] MSID Air Interface (hex) Dial MSID valid YES Member of Talkgroup #1 Talkgroup #4 Radio Terminal #5 [MS(E)] 9

10 MSID Air Interface (hex) Dial MSID valid YES Member of Talkgroup #5 Radio Terminal #6 [MS(F)] MSID Air Interface (hex) Dial MSID valid NO Member of Talkgroup #1 6.4 Multi-band equipment Where a product is supplied in multiple RF bands all using the same protocol and control software, it is only necessary to perform the IOP tests on one band. The other bands shall be verified by executing the following sub-set on each variant using a two RF channel infrastructure (1 control and one traffic channel) : a) An individual MS to MS call b) A MS to talkgroup call 6.5 Default Test Conditions This section defines the test conditions that are to be taken as the default conditions unless otherwise specified Receiver Input Signal Level Unless otherwise stated the standard input signal power level measured at the MS shall be in the range - 65 to -100dBm. The power level of the equipment under test shall be adjusted such that the system offers a rational reciprocity Acquisition state A MS is in the acquisition state if it is hunting for a legitimate Beacon Channel on which it will register (if required to do so) or acquire if not required to register Idle state A MS is in the idle state if it has acquired a Beacon Channel and has successfully registered (if required to do so). In the idle state there are no signalling transactions. The MS manufacturer shall state what indication is presented to the user to notify the user that the MS is in the idle state. 10

11 6.5.4 Network Parameters Unless otherwise stated the values of the System Identity Code transmitted by the TSCC shall be a Small Model, Network ID 169, Site 1, as defined in Annex A System Personality SYScode Clause Ref [1] A 0x Value of Channel Code Unless otherwise stated the values of the Channel Code shall be automatically generated as specified in section of TS MS Personality The IDs and talkgroups of the MSs under test are not specified but the relative talkgroup membership of each MS is specified in section MS Allocated to a Payload Channel A MS is active on a payload channel if a transaction with the Beacon has resulted in allocation of a payload channel. The manufacturer shall state what audible or visual indication is provided to the tester to confirm the allocation of that payload channel. 7. Test Suite/Test Cases 7.1 Test Suite Control Channel Acquisition Non registering System Description A method for searching for a candidate control channel is described ints Annex B[i]. This annex is however informative, therefore manufacturers have the discretion in their MS designs to identify a physical radio channels that may be transmitting a Beacon Channel on which an MS may be permitted access. This test suite assumes that the MS carries a list of candidate Beacon Channels and the MS is able to search through the list listening for a Beacon Channel that it may be authorised to access. Clause [i].prescribes the step of checking the TSCC SYScode (verification) and signal quality. This test suite checks that a MS correctly reads the SYScode and verifies the SYScode against the MODEL and NET parameters in the MS. The test Syscodes and their relevant MODEL and NET are listed in Annex A Expected Behaviour The MS shall only enter the idle state (see 6.4.3) if the MODEL and NET parameter stored in the MS match the SYScode being transmitted by the TSCC. 11

12 As this is a non-registering system also tests that a de-registration is not sent when the MS is switched off Tiny Network MS(A) is programmed with the MODEL=0 and NET=169 parameters in A TSCC is configured as a non-registering system ( [i] Aloha Message Reg=0). SYScode=0x Initial Conditions Test Case 1; Tiny Network Procedure 1. Switch on MS(A) 2. Pass Criteria. The MS enters the idle state (see 6.5.3) (a delay may occur while the MS searches through the list of possible control channels 3. Switch off MS(A) 4. Pass Criteria. The MS powers off without making a transmission 5. Change the SYScode transmitted by the TSCC to 0x Switch on MS(A) 7. Pass Criteria. The MS does not enter the idle state as the NET does not match. 8. Switch off MS(A) Logging Messages Message Direction IE Reference None Small Network Initial Conditions MS(A) is programmed with the MODEL=1 and NET=42 parameters in A TSCC is configured as a nonregistering system ( [i] Aloha Message Reg=0). SYScode=0x Test Case 2: Small Network Procedure 1. Switch on MS(A) 2. Pass Criteria. The MS enters the idle state (a delay may occur while the MS searches through the list of possible control channels 3. Switch off MS(A) 4. Change the SYScode transmitted by the TSCC to 0x Switch on MS(A) 6. Pass Criteria. The MS does not enter the idle state as the NET does not match. 7. Switch off MS(A) 12

13 Logging Messages Message Direction IE Reference None Large Network Initial Conditions MS(A) is programmed with the MODEL=2 and NET=5 parameters in A TSCC is configured as a nonregistering system ( [i] Aloha Message Reg=0). SYScode=0x Test Case 3: Large Network Procedure 1. Switch on MS(A) 2. Pass Criteria. The MS enters the idle state (a delay may occur while the MS searches through the list of possible control channels 3. Switch off MS(A) 4. Change the SYScode transmitted by the TSCC to 0x Switch on MS(A) 6. Pass Criteria. The MS does not enter the idle state as the NET does not match. 7. Switch off MS(A) Logging Messages Message Direction IE Reference None Huge Network Initial Conditions MS(A) is programmed with the MODEL=3 and NET=4 parameters in A TSCC is configured as a nonregistering system ( [i] Aloha Message Reg=0). SYScode=0x Test Case 4: Huge Network Procedure 1. Switch on MS(A) 2. Pass Criteria. The MS enters the idle state (a delay may occur while the MS searches through the list of possible control channels 3. Switch off MS(A) 4. Change the SYScode transmitted by the TSCC to 0x Switch on MS(A) 6. Pass Criteria. The MS does not enter the idle state as the NET does not match. 7. Switch off MS(A) Logging Messages Message Direction IE Reference None 13

14 7.2 Test Suite Registration Note: The tests in this section only exercise a small subset of registration compliance. What is not tested is MS behaviour to changes in the SYScode, SYS_AREA and Access Authorisation. The registration tests assume that the TSCC is announcing that it is a registering system by setting Reg=1 in the outbound C_ALOHA messages [i] Aloha Message Reg=1).. Beacon Downlink B ID0+1=(A) ID2+3=REGI AL AK AL A MS(A) Uplink R ID0+1=REGI ID2+3=(A) Figure 1: Registration Description In a registering system, the normal procedure for a trunked MS is to register with a TSCC at start up before becoming Idle. By doing so it identifies itself to the trunked system which will either accept, or deny access Expected Behaviour Where required to do so it is expected the MS shall correctly register with the system Initial Conditions MS(A) is programmed with the MODEL=0 and NET=169 DMRLA=3 parameters in A TSCC is configured as a non-registering system ( [i] Aloha Message Reg=0). SYScode=0x0541 The TSCC is configured such that the MS registration attempt is acknowledged by a C_ACKD registration successful Procedure Test Case 5: Registration Accepted Procedure 1. Switch MS(A) on and verify that the MS makes a transmission 2. Pass criterion: The manufacturer specific indication shows that the MS has successfully registered. 3. Remove the TSCC downlink transmission and wait until the MS enters control channel acquisition (hunting) 4. Restore the TSCC downlink transmission 5. Pass criterion: MS(A) acquires the TSCC without making a repeated registration attempt 14

15 Beacon Logging Messages Direction Message IE Reference MT uplink B_RAND Reg_Dereg=1 2 ID0+1 REGI ID2+3 MSID MT= [i] downlink B_WACKD ID0+1 MSID B_ACKD ID2+3 REGI Reason Wait= Reg Accepted= Test Case 6: Registration Denied Procedure The TSCC is configured such that the MS registration attempt is acknowledged by a B_ACKD registration denied 1. Switch MS(A) on and verify that the MS makes a transmission. 2. Pass criterion: The manufacturer specific indication shows that the MS has been rejected registration. MS(A) does not make any further registration attempts. 3. Switch MS(A) off. 4. Switch MS(A) on and verify that the MS makes a transmission then becomes idle. 5. Pass criterion: The manufacturer specific indication shows that the MS has been rejected registration. MS(A) does not make any further registration attempts. 6. Switch MS(A) off Beacon Logging Messages Direction Message IE Reference uplink B_RAND MT ID0+1 REGI ID2+3 MSID Reg_Dereg=1 2 downlink B_WACKD MT= [i] B_ACKD ID0+1 MSID ID2+3 REGI Reason B_WACKD Wait= , B_NACKD Reg Denied= Test Case 7: Re-Registration on a site change Procedure This test follows test case 6 The TSCC is configured such that the MS registration attempt is acknowledged by a C_ACKD registration accepted. 1. Switch MS(A) on and verify that the MS makes a transmission 2. Pass criterion: The manufacturer specific indication shows that the MS has successfully registered. 3. Remove the TSCC downlink transmission and wait until the MS enters control channel acquisition (hunting) 4. Change the TSCC SYScode from 0x0541 to 0x0542 (Site change from to ) 5. Restore the TSCC downlink transmission 6. Pass criterion: MS(A) makes a transmission (registration attempt) then become idle 15

16 Beacon Logging Messages Direction Message IE Reference uplink B_RAND MT ID0+1 REGI ID2+3 MSID Reg_Dereg=1 2 downlink B_WACKD MT= [i] B_ACKD ID0+1 MSID ID2+3 REGI Reason Wait= Reg Accepted= Test Case 8: De-Registration on Switch Off Procedure 1. Switch MS(A) on and verify that the MS makes a transmission 2. Pass criterion: The manufacturer specific indication shows that the MS has successfully registered. 3. Switch MS(A) off 4. Pass criterion: MS(A) makes a deregistration transmission Beacon Logging Messages Direction Message IE Reference MT uplink B_RAND Reg_Dereg=0 2 ID0+1 REGI ID2+3 MSID MT= [i] downlink B_ACKD ID0+1 MSID ID2+3 REGI Reason DeReg Accepted= Test Suite Voice Call Service, Talkgroup Description These tests execute three group call scenarios. Group calls can be granted, refused or queued Expected behaviour a) It is expected that a group call will be immediately established if a payload channel is available. b) If no payload channel is available and the system has queuing enabled, the expectation is that the call is queued and will proceed when a payload channel becomes available within the group call timeout. This can be either achieved by the system restricting access to the payload channel or occupying the channel by a MS that is not part of the actual test. c) If a MS is trying to call a group that isn t valid or enabled on the system, the call is refused. 16

17 7.3.3 Initial conditions MS(A), (B), (C), (D) are switched on and idle Procedure Test Case 9: Talkgroup Voice Call - Payload Channel Available Procedure Call granted 1. Initiate a call set-up from MS(A) to Talkgroup#1 2. Pass criterion: MS(B), MS(C) and MS(D) can hear and clearly understand MS(A) s PTT items. MS(E) and MS(F) can not hear MS 1 s transmission. 3. End the PTT item by MS(A). i.e. release PTT. 4. Clear the call by MS(A) initiating an end of call 5. Pass criterion: MS(A) makes a transmission of the payload channel to end the call. MS((B),(C),(D) clear down. All MSs return to idle on the Beacon Channel 6. Initiate a call set-up from MS(A) to Talkgroup#1 7. Pass criterion: MS(B), MS(C) and MS(D) can hear and clearly understand MS(A) s PTT items. MS(E) and MS(F) can not hear MS 1 s transmission. 8. End the PTT item by MS(A). i.e. release PTT. 9. Clear the call by MS(B) initiating an end of call 10. Pass criterion: MS(B) does not make a transmission and returns to the Beacon channel. MS(A),(C),(D) remain in the call 11. Initiate a call set-up from MS(B) to Talkgroup#3 12. Pass criterion: MS(B) and MS(C) can hear and clearly understand MS(B) s PTT items. MS(A),(D),(E) and (F) can not hear either MS(B) or MS(C) s transmission. 13. Clear the call by MS(B) initiating an end of call Beacon Logging Messages Direction Message IE Reference MT [i] Uplink B_RAND M=000 2 ID0+1 Talkgroup#1 ID ID2+3 MSID(A) calling party B_WACKD Value= MT= [i] Downlink Goto ID0+1 Talkgroup#1 ID Channel ID2+3 MSID(A) calling party MI_TYPE Test Case 10: Talkgroup Voice Call - Payload Channel Busy Procedure Call Queued Create an environment that makes the payload channel busy. This may be by initiating a voice call that allocates the payload channel to that call 1. Initiate a group call from MS(A) to talkgroup#1 2. Pass criterion: The manufacturer specific indication on MS(A) indicates that no payload resource 17

18 available for MS(A) s request. (queued) 3. Confirm that MS(B) does not hear any transmission. 4. Make the payload channel available. (If the payload channel was busy from another call, clear that call) 5. Pass criterion: The manufacturer specific indication on MS(A) shows that there is now a traffic allocated to MS(A) and MS(B) (member of the talkgroup) 6. Start talking on MS(A) 7. Pass criterion: Confirm that MS(B) can hear and clearly understand MS(A) s transmission. 8. Clear the call by MS(A) initiating an end of call Beacon Logging Messages Direction Uplink Uplink Downlink Message IE Reference MT [i] B_RAND ID0+1 Talkgroup#1 ID ID2+3 MSID(A) calling party M=000 2 B_WACKD Value= B_QACKD Value= [i] MT= [i] Goto ID0+1 Talkgroup#1 ID Channel ID2+3 MSID(A) calling party MI_TYPE Test Case 11: Talkgroup Voice Call - Call Refused Call Refused Configure the system so that calls to talkgroup#1 are not permitted. 1. Initiate a group call on MS(A) to talkgroup#1 2. Pass criterion: The manufacturer specific indication shows that MS(A) group call attempt has been refused. 3. Configure the system so that calls to talkgroup#1 are again permitted Beacon Logging Messages Direction Message IE Reference MT [i] uplink B_RAND M=000 2 ID0+1 Talkgroup#1 ID ID2+3 MSID(A) calling party downlink B_NACKD 7.4 Test Suite Voice Call Service, Individual Description These tests execute three individual call scenarios. Individual calls can be granted, refused or queued. 18

19 7.4.2 Expected behaviour a) It is expected that an individual call will be immediately established if a payload channel is available. b) If no payload channel is available and the system has queuing enabled, the expectation is, the call is queued and will proceed when a payload channel becomes available within the individual call timeout. This can be either achieved by the system restricting access to the payload channel or occupying the channel by a MS that is not part of the actual test. c) If a MS is trying to call an individual MS that isn t valid or enabled on the system, the call is refused Initial conditions MS(A), (B), (C), (D) are switched on and idle Procedure Test Case 12: Individual Voice Call - Payload Channel Available Procedure Call granted 1. Initiate a call set-up from MS(A) to MS(B) 2. Pass criterion: MS(A) and MS(B) can hear and clearly understand their PTT items. 3. End the PTT items i.e release PTT. 4. Clear the call by MS(A) initiating an end of call 5. Pass criterion: MS(A) makes a transmission of the payload channel to end the call. MS(A) and MS(B) return to idle on the Beacon Channel 6. Initiate a call set-up from MS(A) to MS(B) 7. Pass criterion: MS(A) and MS(B) can hear and clearly understand their PTT items. 8. End the PTT items i.e release PTT. 9. Clear the call by MS(B) initiating an end of call 10. Pass criterion: MS(B) makes a transmission of the payload channel to end the call. MS(A) and MS(B) return to idle on the Beacon Channel Beacon Logging Messages Direction Message IE Reference MT [i] ID0+1 MSID(B) called party B_RAND Uplink ID2+3 MSID(A) calling party M=000 2 B_ACK B_AHOY B_WACKD Value= Downlink MT= [i] Goto ID0+1 MSID(B) Channel ID2+3 MSID(A) calling party MI_TYPE

20 Test Case 13: Individual Voice Call - Payload Channel Busy Procedure Call Queued Create an environment that makes the payload channel busy. This may be by initiating a voice call that allocates the payload channel to that call 1. Initiate a call from MS(A) to MS(B) 2. Pass criterion: The manufacturer specific indication on MS(A) indicates that no payload resource available for MS(A) s request. (queued) 3. Confirm that MS(B) does not hear any transmission. 4. Make the payload channel available. (If the payload channel was busy from another call, clear that call) 5. Pass criterion: The manufacturer specific indication on MS(A) shows that there is now a traffic allocated to MS(A) and MS(B) (member of the talkgroup) 6. Start talking on MS(A) 7. Pass criterion: Confirm that MS(B) can hear and clearly understand MS(A) s transmission. 8. Clear the call by MS(A) initiating an end of call Beacon Logging Messages Direction Uplink Uplink Downlink Message IE Reference B_RAND MT [i] ID0+1 MSID(B) ID2+3 MSID(A) calling party M=000 2 B_ACK B_AHOY B_WACKD Value= B_QACKD Value= [i] MT= [i] Goto ID0+1 MSID(B) Channel ID2+3 MSID(A) calling party MI_TYPE Test Case 14: Individual Voice Call - Call Refused Call Refused Configure the system so that calls to MS(B) are not permitted. 1. Initiate a group call on MS(A) to MS(B) 2. Pass criterion: The manufacturer specific indication shows that MS(A) call attempt has been refused. 3. Configure the system so that calls to MS(B) are again permitted. 20

21 Beacon Logging Messages Direction Message IE Reference MT [i] uplink B_RAND M=000 2 ID0+1 MSID(B) ID2+3 MSID(A) calling party downlink B_NACKD Any reason code is acceptable 7.5 Test Suite - Multi-site call to a talkgroup Description These tests exercise a talkgroup call involving two radio sites where participant to the talkgroup are located on the two sites. The tests execute two group call scenarios. The Group call is granted and the Group call is queued because a payload channel is not available on the radio site that is not the site on which the group call was initiated Expected behaviour a) It is expected that a group call will be immediately established if a payload channel is available on site #1 and site #2. b) If no payload channel is available and the system has queuing enabled, the expectation is, the call is queued and will proceed when a payload channel becomes available within the group call timeout. This can be either achieved by the system restricting access to the payload channel or occupying the channel by a MS that is not part of the actual test. c) If a MS is trying to call a group that isn t valid or enabled on the system, the call is refused Initial conditions MS(A), (B) are located on radio site #1, MS(C), (D) are located on radio site #2. All MS are switched on and idle Procedure Test Case 15: Talkgroup Voice Call - Payload Channel Available Procedure Call granted 1. Initiate a call set-up from MS(A) to Talkgroup#1 2. Pass criterion: MS(B), MS(C) and MS(D) can hear and clearly understand MS(A) s PTT items. 3. End the PTT item by MS(A). i.e. release PTT. Repeat for a PTT items from MS(B), MS(C) and MS(D) 4. Clear the call by MS(A) initiating an end of call 5. Pass criterion: MS(A) makes a transmission of the payload channel to end the call. MS((B),(C),(D) clear down. All MSs return to idle on the Beacon Channel 6. Initiate a call set-up from MS(A) to Talkgroup#1 7. Pass criterion: MS(B), MS(C) and MS(D) can hear and clearly understand MS(A) s PTT items. 8. End the PTT item by MS(A). i.e. release PTT. 9. Clear the call by MS(B) initiating an end of call 21

22 10. Pass criterion: MS(B) does not make a transmission and returns to the Beacon channel. MS(A),(C),(D) remain in the call 11. Initiate a call set-up from MS(A) to Talkgroup#1 12. Pass criterion: MS(B), MS(C) and MS(D) can hear and clearly understand MS(A) s PTT items. 13. End the PTT item by MS(A). i.e. release PTT. 14. Clear the call by MS(C) initiating an end of call 15. Pass criterion: MS(C) does not make a transmission and returns to the Beacon channel. MS(A),(B),(D) remain in the call Beacon Logging Messages for steps 1 to 6 Radio Site #1 Radio Site #2 Direction Message IE Reference MT [i] Uplink B_RAND ID0+1 Talkgroup#1 ID ID2+3 MSID(A) calling party M=000 2 Downlink B_WACKD Value= MT= [i] Goto ID0+1 Talkgroup#1 ID Channel ID2+3 MSID(A) calling party MI_TYPE MT= [i] Downlink Goto ID0+1 Talkgroup#1 ID Channel ID2+3 MSID(A) calling party MI_TYPE Test Case 16: Talkgroup Voice Call Multi-Site Payload Channel Busy on Site #2 Procedure Call Queued Create an environment that makes the payload channel on site #2 busy. This may be by initiating a voice call that allocates the payload channel to that call 1. Initiate a group call from MS(A) to talkgroup#1 2. Pass criterion: The manufacturer specific indication on MS(A) indicates that no payload resource available for MS(A) s request. (queued) 3. Confirm that MS(B) or MS(C) does not hear any transmission. 4. Make the payload channel available. (If the payload channel was busy from another call, clear that call) 5. Pass criterion: The manufacturer specific indication on MS(A) shows that there is now a traffic allocated to MS(A) and MS(B) on site #1 and to MS(C) and MS(D) on site #2 (members of the talkgroup) 6. Start talking on MS(A) 7. Confirm that MS(B), MS(C) and MS(D) can hear and clearly understand MS(A) s transmission. 8. Clear the call by MS(A) initiating an end of call 22

23 Beacon Logging Messages Radio Site #1 Radio Site #2 Direction Message IE Reference MT [i] Uplink B_RAND ID0+1 Talkgroup#1 ID ID2+3 MSID(A) calling party M=000 2 B_WACKD Value= B_QACKD Value= [i] Downlink MT= [i] Goto ID0+1 Talkgroup#1 ID Channel ID2+3 MSID(A) calling party MI_TYPE MT= [i] Downlink Goto ID0+1 Talkgroup#1 ID Channel ID2+3 MSID(A) calling party MI_TYPE Test Suite Voice Call Service, Individual, Multi-Site Description These tests execute two individual call scenarios. Individual calls can be granted, or queued Expected behaviour a) It is expected that an individual call will be immediately established if a payload channel is available. b) If no payload channel is available and the system has queuing enabled, the expectation is, the call is queued and will proceed when a payload channel becomes available within the individual call timeout. This can be either achieved by the system restricting access to the payload channel or occupying the channel by a MS that is not part of the actual test. c) If a MS is trying to call an individual MS that isn t valid or enabled on the system, the call is refused Initial conditions MS(A), (B) are located on radio site #1, MS(C), (D) are located on radio site #2. All MS are switched on and idle Procedure Test Case 17 Individual Voice Call Multi Site - Payload Channel Available Procedure Call granted 1. Initiate a call set-up from MS(A) to MS(C) 2. Pass criterion: MS(A) and MS(C) can hear and clearly understand their PTT items. 3. End the PTT items i.e release PTT. 23

24 4. Clear the call by MS(A) initiating an end of call 5. Pass criterion: MS(A) makes a transmission of the payload channel to end the call. MS(A) and MS(B) return to idle on the Beacon Channel 6. Initiate a call set-up from MS(A) to MS(C) 7. Pass criterion: MS(A) and MS(C) can hear and clearly understand their PTT items. 8. End the PTT items i.e release PTT. 9. Clear the call by MS(C) initiating an end of call 10. Pass criterion: MS(C) makes a transmission of the payload channel to end the call. MS(A) and MS(B) return to idle on the Beacon Channel Beacon Logging Messages Radio Site #1 Radio Site #2 Direction Message IE Reference MT [i] Uplink B_RAND ID0+1 MSID(B) called party ID2+3 MSID(A) calling party M=000 2 B_WACKD Value= [i] MT= [i] Downlink Goto ID0+1 MSID(B) Channel ID2+3 MSID(A) calling party MI_TYPE Uplink B_ACK B_AHOY MT= [i] Downlink Goto ID0+1 MSID(B) Channel ID2+3 MSID(A) calling party MI_TYPE Test Case 18: Individual Voice Call - Payload Channel Busy Procedure Call Queued Create an environment that makes the payload channel on site #2 busy. This may be by initiating a voice call that allocates the payload channel to that call 1. Initiate a group call from MS(A) to MS(C) 2. Pass criterion: The manufacturer specific indication on MS(A) indicates that no payload resource available for MS(A) s request. (queued) 3. Confirm that MS(C) does not hear any transmission. 4. Make the payload channel available. (If the payload channel was busy from another call, clear that call) 5. Pass criterion: The manufacturer specific indication on MS(A) shows that there is now a traffic allocated to MS(A) and MS(C) 6. Start talking on MS(A) 24

25 7. Pass criterion: Confirm that MS(C) can hear and clearly understand MS(A) s transmission. 8. Clear the call by MS(A) initiating an end of call Beacon Logging Messages Radio Site #1 Radio Site #2 Direction Message IE Reference MT [i] Uplink B_RAND ID0+1 MSID(B) called party ID2+3 MSID(A) calling party M=000 2 B_WACKD Value= B_QACKD Value= [i] Downlink MT= [i] Goto ID0+1 MSID(B) Channel ID2+3 MSID(A) calling party MI_TYPE Uplink B_ACK B_AHOY MT= [i] Downlink Goto ID0+1 MSID(B) Channel ID2+3 MSID(A) calling party MI_TYPE Test Suite Status Service Delivery Description The Status Message service enables a status value to be transmitted between dpmr entities on the Beacon channel. The status delivery service transports a status message from the initiator to a recipient. Six bits are transported. Status values 0 to 49 have a user defined meaning. Status values 50 to 63 are reserved Expected behaviour a) It is expected that the status value will be transferred so long as the recipient is not busy in another call (for example in a call on a payload channel) b) A single set of tests exercises both single site and multi site status delivery Initial conditions MS(A), (B) are located on radio site #1, MS(C), (D) are located on radio site #2. All MS are switched on and idle Procedure Test Case 19 Status Call Procedure Call granted 1. Initiate a status call (status value =3) from MS(A) to MS(B) [single site status delivery] 25

26 2. Pass criterion: MS(B) receives the status and correctly receives the status value. 3. Pass criterion: MS(A) receives a confirmation that the status has been received 4. Initiate a status call (status value =3) from MS(A) to MS(C) [multi-site status delivery] 5. Pass criterion: MS(C) receives the status and correctly receives the status value. 6. Pass criterion: MS(A) receives a confirmation that the status has been received 7. Initiate a status call (status value =22) from MS(A) to MS(B) [single site status delivery] 8. Pass criterion: MS(B) receives the status and correctly receives the status value. 9. Pass criterion: MS(A) receives a confirmation that the status has been received 10. Initiate a status call (status value =22) from MS(A) to MS(C) [multi-site status delivery] 11. Pass criterion: MS(C) receives the status and correctly receives the status value. 12. Pass criterion: MS(A) receives a confirmation that the status has been received 13. Initiate a status call (status value =49) from MS(A) to MS(B) [single site status delivery] 14. Pass criterion: MS(B) receives the status and correctly receives the status value. 15. Pass criterion: MS(A) receives a confirmation that the status has been received 16. Initiate a status call (status value =49) from MS(A) to MS(C) [multi-site status delivery] 17. Pass criterion: MS(C) receives the status and correctly receives the status value. 18. Pass criterion: MS(A) receives a confirmation that the status has been received 19. Initiate a status call (status value =50) from MS(A) to MS(B) [single site status delivery] 20. Pass criterion: MS(A) refuses to make the call attempt Beacon Logging Messages Status from MS(A) to MS(B) Radio Site #1 Radio Site #2 Direction Message IE Reference MT= [i] Uplink B_RAND ID0+1 MSID(B) called party ID2+3 MSID(A) calling party STATUSM3 B_WACKD Value= [i] B_ACK MT= [i] Downlink ID0+1 Talkgroup#1 ID B_AHOY ID2+3 MSID(A) calling party MI_TYPE STATUSM3 No signalling for this call Beacon Logging Messages Status from MS(A) to MS(C) 26

27 Radio Site #1 Radio Site #2 Direction Message IE Reference MT= [i] Uplink B_RAND ID0+1 MSID(B) called party ID2+3 MSID(A) calling party STATUSM3 Downlink B_WACKD Value= [i] B_ACK Uplink B_ACK MT= [i] ID0+1 Talkgroup#1 ID Downlink B_AHOY ID2+3 MSID(A) calling party MI_TYPE STATUSM3 7.8 Test Suite Short Data Message Description The Short Data Message service enables data to be transmitted between dpmr entities using the beacon channel. Up to 256 bits of data may be transported using this service in a number of formats including binary, BCD, 7 bit text, 8 bit characters, and NMEA (EN [Error! Reference source not found.]). Manufacturers must state the formats supported. It is expected that at least 7 bit and 8 bit is supported. These two formats are tested in this test suite Expected behaviour a) It is expected that the short data messages are received verbatim as sent. b) When the short data message has been received it is expected that the calling party will receive an acknowledgement that the message had been received Initial conditions MS(A), (B) are located on radio site #1, MS(C), (D) are located on radio site #2. All MS are switched on and idle Procedure Test Case 20 Short Data Call Procedure (Format=7 bit) Configure the MS(A) to send 7 bit format Short Data 1. Initiate a short data call (message= a ) from MS(A) to MS(B) [single site delivery] 2. Pass criterion: MS(B) receives the message. 3. Pass criterion: MS(A) receives a confirmation that the message has been received 4. Initiate a short data call (message= a ) from MS(A) to MS(C) [multi-site delivery] 5. Pass criterion: MS(C) receives the message. 6. Pass criterion: MS(A) receives a confirmation that the message has been received 7. Initiate a short data call (message value= abcdefghijkl ) from MS(A) to MS(B) [single site delivery] 27

28 8. Pass criterion: MS(B) receives the message. 9. Pass criterion: MS(A) receives a confirmation that the message has been received 10. Initiate a short data call (message value= abcdefghijkl ) from MS(A) to MS(C) [multi-site delivery] 11. Pass criterion: MS(C) receives the message. 12. Pass criterion: MS(A) receives a confirmation that the message has been received 13. Initiate a short data call (message value= abcdefghijklmnopqrstuvwxyz ) from MS(A) to MS(B) [single site delivery] 14. Pass criterion: MS(B) receives the message. 15. Pass criterion: MS(A) receives a confirmation that the message has been received 16. Initiate a short data call (short data value= abcdefghijklmnopqrstuvwxyz ) from MS(A) to MS(C) [multi-site delivery] 17. Pass criterion: MS(C) receives the message. 18. Pass criterion: MS(A) receives a confirmation that the message has been received Test Case 21 Short Data Call Procedure (Format=8 bit) Configure the MS(A) to send 8 bit format Short Data 1. Initiate a short data call (message= a ) from MS(A) to MS(B) [single site delivery] 2. Pass criterion: MS(B) receives the message. 3. Pass criterion: MS(A) receives a confirmation that the message has been received 4. Initiate a short data call (message= a ) from MS(A) to MS(C) [multi-site delivery] 5. Pass criterion: MS(C) receives the message. 6. Pass criterion: MS(A) receives a confirmation that the message has been received 7. Initiate a short data call (message value= abcdefghijkl ) from MS(A) to MS(B) [single site delivery] 8. Pass criterion: MS(B) receives the message. 9. Pass criterion: MS(A) receives a confirmation that the message has been received 10. Initiate a short data call (message value= abcdefghijkl ) from MS(A) to MS(C) [multi-site delivery] 11. Pass criterion: MS(C) receives the message. 12. Pass criterion: MS(A) receives a confirmation that the message has been received 13. Initiate a short data call (message value= abcdefghijklmnopqrstuvwxyz ) from MS(A) to MS(B) [single site delivery] 14. Pass criterion: MS(B) receives the message. 15. Pass criterion: MS(A) receives a confirmation that the message has been received 16. Initiate a short data call (short data value= abcdefghijklmnopqrstuvwxyz ) from MS(A) to MS(C) [multi-site delivery] 17. Pass criterion: MS(C) receives the message. 18. Pass criterion: MS(A) receives a confirmation that the message has been received 28

29 Beacon Logging Messages Short data from MS(A) to MS(B) Radio Site #1 Radio Site #2 Direction Message IE Reference MT= [i] ID0+1 MSID(B) called party B_RAND Uplink ID2+3 MSID(A) calling party STATUSM3 Head+data B_WACKD Value= [i] B_ACK MT= [i] Downlink ID0+1 MSID(B) B_AHOY ID2+3 MSID(A) calling party MI_TYPE STATUSM3 Head+data No signalling for this call Beacon Logging Messages Short Data from MS(A) to MS(C) Radio Site #1 Radio Site #2 Direction Message IE Reference MT= [i] ID0+1 MSID(B) called party B_RAND Uplink ID2+3 MSID(A) calling party STATUSM3 Head+Data B_WACKD Value= [i] Downlink B_AHOY B_ACK Uplink B_ACK Downlink Head+Data 29

30 Annex A - System Identity Codes A.1 Syscodes Used for the IOP Tests dpmr trunked networks may range from tiny systems consisting of a very small number of sites to very large systems covering a wide geographic area. To accommodate this wide range of networks, dpmr specifies four network Models, each with characteristics appropriate to each Model. Table A.1: Network Model Network Model Number of Number of Sites per dpmrla Model Coding Networks Network Tiny to 3 Small to 5 Large to 8 Huge to 10 In order to identify the network and site to MSs, a Beacon frequently transmits a SYScode in the SYScast1 message. MSs shall examine the SYScode to determine if they are permitted to become or remain active on the BS. The SYScode fields are structured as follows. Table A.2: Network Model Description Parameter Descriptor and section Description MODEL Network Model Tiny, Small, Large, Huge NET Network Identity Identifies a particular dpmr trunked network SITE The SITE parameter identifies a particular radio site within a network A.1.1 Tiny A Tiny NetworkID 169, Site 1 Parms MODEL 0 Network ID 168 SITE 1 bin x A Tiny NetworkID 170, Site 1 Parms MODEL 0 Network ID 169 SITE 1 bin x

31 A.1.2 Small A Small NetworkID 42, Site 1 Parms MODEL 1 Network ID 42 SITE 1 bin x A Small NetworkID 43, Site - 1 Parms MODEL 1 Network ID 43 SITE 1 bin x A Small NetworkID 43, Site - 0 Parms MODEL 1 Network ID 43 SITE 0 bin x A Small NetworkID 43, Site - 2 Parms MODEL 1 Network ID 43 SITE 2 bin x A.1.3 Large A Large NetworkID 5, Site 1 Parms MODEL 2 Network ID 5 SITE 1 bin x A.1.4 Huge A Huge NetworkID 1, Site 1 31

32 Parms MODEL 0 Net 1 SITE 1 bin x