~ 1

1509001:2015 I EffPrtiv" frnm 24 .0Q 7n1a , ''".

- · ·---··- •• -··· - · ·--•--4u ~" .-v.;,.;,.;, version- L.O Page 127 of 141
pocument Ti_!le: Functional Test Cases at System Level for Train Collision Avoidance System RDSO/SPN/196/2012 version 3.2
--i
TesflD/ Test Scenario System Level TEST CASES (RDSO)
Title/ Input Specification
Expected OutpuWalues I
Descrip Observed Output
\
tion (Pass/Fall)
17.46 To verify the track section
1. Make sure that Station shall have
speed (PSR) limit in FS Loco shall apply brakes for Section Speed
PSR configured for 90KMPH for
when SSP and MA are (PSR) at given absolute location as mentioned
800mtrs with Junction Tag within inSSP.
available (PSR configured range of PSR.
for 90KMPH for 800mtrs, Loco shall maintain the speed regulation I
2. Cab is active and loco is in TCAS
of in a Station with throughout the PSR range after passing the
territory and TCAS is healthy Junction RF Tag.
Junction Tag in with in 3. Move loco in Reverse direction and
PSR range) Make sure that loco is in FS mode with
MA and SSP are available.
4. Now configure the loco maximum
speed value such that it is morethan
the section speed (PSR)
5. Now simulate the condition such that
the loco speed is more than the section
speed value and shall pass the both
PSR sections in up direction.
18 TCAS_SYS_ 18 I
This test case checks that the. logging of 8Vf:ll"!ts in data logger i.e Loco TCAS & Stationary TCAS data \ogger. This
18.1 To verify logging of events
and faults in Loco TCAS

data !9ggmg may b~verifiedror-thetest case already carried out.

Simulate the following situations in Download the Log from Loco TCAS Data logger. \
\
Loco TCAS unit. Generate the Report by using PC Application
from Data logger Tool and check that event logging is done at
every 02 sec & occurrence of events.
a) Head On Collision Observe the following events with date, time &
b) Rear End Collision location stamp. This must be checked that
c) Manual SoS generation and stored data of mimimum 90 days. lastdate of availabi\ity
cancellation Date
d) Train Trip
a) Head-on Collision
\ Time
\
e) Side Collision I I I
f) Loco Pilot Alert Message on DMI b} Rear-end Collision
I I
c) Manual Sos generation and cancellation
I
d} Train Trip I I I
Representative of Firm ROSO Inspecting Official
.:~n . -~- ..... •.·· ':.': f"i-~'' __·~:.• ·. ._,_;yzq .·_:r-i,_
>'~1>-- '
.. · ··
.,,-> · ,) J~~-)· . '
v I\.
vi,; -~ •' ·-., · ·v
':i,·"~ft:,'·
r t \. '/~·.~
• ·. t . · ·
~ • ·,,.-d ! - .. - ''...!L....::!:: ~
 1SO9 001:2 01S
I
Effect ive from 24 -09.20 18
\ SIF :-0533 Versio
Docu ment Title : Funct ional Test n- 2 .0 \ Page 128 of 141
Cases at Syste m Level for Train
Collis ion Avoid ance Syste m ROSO
/SPN/ 196/2 012 versio n 3 .2
~yste m Level TESTCAS E S (ROS O)
Test ID/ I Test Scen ario Input Spec ificat ion
Title/ E x p ected O utput Nalue s
Desc rip
tion
e) Side Collis ion
f) Loco Pilot Alert Mess age on OM\
18.2 To verify loggin g of even ts Simu late the follow ing situat ions in
of failur e/abn orma l/spec ific Loco TCAS unit. Down load the Log 1rom Loco l"CAS data logge r
condi tion & recov ery of a) failur e of syste m to indica tethe Gene rate the Repo rt by using PC Appllc
atlon
faults in Loco TCAS or locati on l"ool
b) Obse Ne
Statio nary TCAS Relev ant comm unica tion failur e of Loco unit. the 1ollow ing event s with date, t\me and
data logge r. C)inp ut failur e locati on stamp . l"his must be check that
store d
d} failur e of TCAS unit due to any data of "\ 5 days.
reaso n shall be logge d in NMS ~)_ failur e of syste m to indica te the locati on
e) Brak e interf ace unit isolat ion b) comm unica tion failur e of Loco uni\.
f)all type of brake appli catio n actua ted ~)inp ut failur e
by TCAS unit with durat ion spee d & d) failur e of "TCP..S unit due lo any reaso
n shall
dista nce meas urem ent. be logge d in NMS
g) Rest art of TCAS unit due to any e) Brake interf ace unit isolat ion
reaso n h)AII f)all type of brake app\i ca\ion actua ted
failur e mess age 'oy "TCP..S
unit with durat ion spee d & dista nce
i) Non leadi ng mode meas urem ent.
j) Train lengt h g) Rest art of 1'Ct>.S unit due _to any reaso
assig nmen t/mea n
surem ent h )A.\\ failur e mess age
k) mod e trans ition i) Non leadi ng mode
I) MBT i) ,rain lengt h assig nmen \lmea
m) Ever y RFID tag detai ls surem en\ ·.-
" Loco unit shall log its locat ion at a resol ution of
bette r than 200 ms for last 20 Seco nds which
shall be used by Loco unit for preci se
locat ionfo r
train lengt h calcu lation ."
K) mod e \rans\\ion
\) MB,
'-
Rep rese ntati ve of Firm ROSO \nsp ect\n ~ Qtt\c\a\
 8
1SO9001:2015 I Effective from 24.09.2018 \ SIF :-0533 Version- 2.0
" \ Page 129 of 141
Document Title: Functional Test Cases at System Level for Train Collision Avoidance System RDSO/SPN/196/2012 version 3 .2
System Level TEST CASES (ROSO) \
Test ID/ Test Scenario Ex pected OutputNalues
\
Input Specification \ ObseNed Output
Tltle/ .. (Pass/Fail)
Descrip L l
tion
m) Every RFID tag details
\
18.3 To verify logging of events Simulate the following situations in D owntoad the Log from Loco TC"-S data togge, \
\
every 02 second or Loco TCAS unit. G enerate the Report by using PC Application
occurance of events in a)date T ool
Loco TCAS Relevant data b) time 0 bserve the following events with date ,time
logger. C) Loco ID This must be check that stored data of
d}speed minimum of 72 hours.
e) Absolute location a)date \ \
f}Train Movement (Nominal/Reverse) b) time \ \
g) Location of last RFID tag passed C}LOCO ID \ \
h}TIN d} speed \ \
i) Type of Brake application e) absolute location \ \
j) Systems fault f)Train Movement (Nominal/Reverse) \ \
g) Location of last RFIS tag passed \ \
h)TIN \ \
i) Type of Brake application \ \
j) Systems fault \ \
18.4 To verify logging of events Simulate the following situations in Download the Log from stationary TCA.S data
on occurance of events in stationary TCAS unit. logger
Stationary TCAS Relevant a)Date Generate the Report by using PC A.pplication
data logger b} time Tool
C)LOCO Radio packet received Observe the following events with date, time
d)status of all signalling inputs .This must be check that stored data of
e) Signalling information packets sent minimum of 72 hours.
f)stationary Emergency a)Date \ \
message(SOS) b) time \
\
g) System faults C)LOCO Radio packet received \
d)status of al\ signaling inputs \
e) Signa\ing information packets sent \
f)stationary Emergency messagetSOS) \
\
Representative of Firm ROSO \nspecting Ottkia\
 : 0l5 Effective from 24.09.2018 SIF :-0533 Version- 2.0
15O9001 2 Page 130 of 141
Document ntle: Functional Test Cases at System Level for Train Colllslon Avoidance System
RDSO/SPN/196/2012 version 3.2
System Level TEST CASES (ROSO)
Test scen ario Input Specification Expected OutputNalues Obstrved Outpu\
Test ID/
Title/ (P111/Fall)
Descrlp
tion
g) System faults
To verify trigger the Simulate the following situations in Download the Log from Loco TCAS data logger.
18.5 Loco TCAS unit.
logging of events Loco Generate the Report by using PC Application
TCAS Relevant data a) Update of Movement Authority Tool
logger b) Initiation of brake application . Observe the following events with date, time
c) Change of type of braking .This must also checked that stored data of
application .
minimum of 72 hours.
d) Removal of brake application.
e) Change in TCAS Mode. a) Update of Movement Authority
f) Acknowledgement by loco pilot b) Initiation of brake application .
g) Passing of RFID Tag. c) Change of type of braking application .
h) Change in TIN. d) Removal of brake application.
i) 1 RFID tag missing out of 2. e) Change In TCAS Mode.
j) Both (duplicated) RFID tags missing f) Acknowledgement by loco pilot
(only for Normal tags) g) Passing of RFID Tag.
k) Data mismatch between duplicated h) Change in TIN.
RFID tags. i) 1 RFID tag missing out of 2.
I) Change in Signal Aspect. j) Both (duplicated) RFID tags missing (only for
m) Passing of signal. Normal tags)
n) Transmission of emergency k) Data mismatch between duplicated RFID
messages. tags.
o) Reception of emergency messages I) Change in Signal Aspect.
m) Passing of signal.
\
I
\I
n) Transmission of emergency messages.
o) Reception of emergency message
\ \
I I
I
Representative of Firm ROSO Inspecting Official
, 1s09001,201s '"""" TTom 24.09.2018 SIF ,-0s33 ve,.fon- 2.0

(}
,,.. n1o1141
()ocument Title: Functional Test Cases at System Level !or Train Collision Avoidance System RDSO/SPN/196{2012 version 3.2
~

1
Test ID/ Test Scenario
j
Title/ System Level TEST CA SES (R OSO)
Input Specification
Descrip Expected OutpuWalues
tion
I
\°bHNed Output
I
18.6
To verify logging of events
every 02 second or
occurance of events in
Stationary TCAS Relevant

1. Loco TCAS & Station TCAS units

are healthy
2. Establish communication between
Download the Log from Loco TCAS data Logger. \
Generate the Report by using PC Application
Tool

(P ass/F ail)
\
data logger) Station TCAS and Loco TCAS and
ensue Loco TCAS is in FS mode
3. Loco TCAS unit shall transmit the Observe the Loco TCAS regular packet defined I
location of the train to the Stationary in the specification (Annex-3, Packet type 2) for
TCAS unit every 2 seconds in Full every 2 seconds in Radio Tx packet:
Supervision mode.
18.7
1. Loco TCAS & Station TCAS units
are healthy Download the Log from Station TCAS Event
\
Logger.
\
2. Establish communication between
Station TCAS and Loco TCAS and
ensue Loco TCAS is in FS mode
Generate the Report by using PC Application
Tool ,Observe the following information
a) Date
b)Time I
\
c) Loco radio packets received
I _\
I \
d) Change in the Status of signaling inputs
I \
e) Signaling information packets sent ((Annex-3, \
18.8 1. Loco TCAS & Station TCAS units
are healthy

Packet type 1 )
Download the Log TTom Loco TCAS data Logge,. \
\
\
Generate the Report by using PC Application
2. Establish communication between Tool, Observe the RFID tag data for below tags
Station TCAS and Loco TCAS and as specified in the specification (Annex 4).
ensure Loco TCAS is in FS mode
1) Normal Tag
\ \
2) Signal Foot Tag
I \
3) Signal Approach Tag
\ \
4) TIN discrimination Tag I
5) LC Gate Tag
\
\ j
6) Adjustment Tag/Junction Tag I \
7) Exit Tag I \
Representative of Firm ROSO Inspecting Official
 I Page 132 of 141
24 09 2018 1 SIF :-0S33 Ve rsio n- 2.0
Effective fro m - - 96/2012 version 3.2
I ce System RDSO/SPN/1 I
Trai_!l_ Co llis ion Av oid an
-·-
1S 09 00 1:2 01 5 t
at SyS elTl Le vel for
nc tio na l Te st Cases
Do cu me nt Tit le: Fu
I
CA SE S (ROSO)
Sy ste m Le ve l T EST es 0 bse rve d Ou t pu t
Inp ut Sp ec ific ati on Ex pe cte d Ou tpu t/V alu (Pass/Fall)
Te st ID / Te st Sc en ari o
Tit le/
De sc rip m Station TCAS data
fau lts/ eve nts in Do wn loa d the Log fro
tio n Sim ula te the fol low ing
en Lo co TC AS un it Lo gg er.
18 .9 Lo co TC AS un it, wh by using PC Appllcatlo
n
is he alt hy. Ge ne rat e the Report
To ol
information
to ind ica te the Ob ser ve the following
1) Fa ilu re of Sy ste m de fault: when two RF
ID
RF ID tag s wh en 1. Sy ste m Failure mo
loc ati on : Sw ipe tw o tag s are swiped at sta
ndstill
stil l
Lo co /tra in is at sta nd 2, FS B an d EB applica
tion for SPAD
ap plic ati on
2) All typ es of Bra ke 3. Re sta rt of TC AS un
it eve nt
it wit h du rat ion ,
ac tua ted by TC AS un 4. Tra in length measu
re value
ula te SP AD
sp ee d & dis tan ce : Sim to SR, SR to LS, LS to
5. Mo de transitions (SB
3) Re sta rt of TC AS
un it , PT to SR or PT toF S)
FS , FS to TP , TP to PT
4) Tra in Le ng th 6. MB T Re sul t
en t
As sig nm en t/m ea su rem . 7. Sw ipe d RF ID tag s
5) Mo de Tra ns itio n
T by pre ssi ng
6) MB T: Pe rfo rm MB
MB T so ftk ey on DM
I, wh en tra in isa t
\ JI
sta nd sti ll
 ! If
1SO9001:2015 1 Effective from 24.09.2018 I SIF :-0533 Version- 2.0 I Page 133 of 141
Document Title: Functional Test Cases at System Level for Train Collision Avoidance SystE!_m ROSO/SPN/19~2012 version 3 .2
System Level TEST CASES (ROSO) Observed Output
Input Specification Expected Output/Values
Test ID/ I Test Scenario (Pass/Fall)
Title/
Descri p
tion
1. Ensure Keys are not Communication should not be established
19.2 When the Stationary
available with Loco TCAS and Loco should continue to SR mode
TCAS unit communicating
the safety related data unit & keys are available
with Loco TCAS, it shall with Stationary TCAS unit.
verify that 2. Simulate a Loco movement
communication is in the Stationary TCAS unit
established with an vicinity.
authorized Loco TCAS
unit
19.3 After the above i.e. 19.2 , 1. Ensure Keys are available Communication should be established
authenticity and integrity with both Loco TCAS unit between the TCAS units, and Loco TCAS
of any information & Stationary TCAS unit. should transit from SR to LS/FS mode.
2. Simulate a Loco movement Same shall be observed on the DML
exchanged between Loco
TCAS and Stationary TCAS in the Stationary TCAS unit
unit shall also be vicinity.
verified.
19.4 After the above 1. Establish communication After recovery, Loco TCAS should send the
procedure shall take between Stationary TCAS Access request message and Stationary
place each time the Loco unit and Loco TCAS units. TCAS unit should respond with Access
TCAS and Stationary TCAS 2. Simulate a communication Authority message.
unit effectively start a failure and ensure Loco is in Further Loco and Station should
new communication LS/SR mode. communicate with regular packets.
session between them Recover the fault and check the
communication between the two Above message_s shall be observed in the
TCAS units. Loco & Station Logs.
Representative of Firm ROSO Inspecting Offlcia\
.:.:..- -
ISO9001 :2015 ) Effective from 24.09 .2018 \ SIF :-0533 Version - 2 .0 \ Page 1.34 of 1.41.
Document Title: Functional Test Cases at System Level for Train Collision Avoidance Syste_"'_ RDSO/SPN/1.96/2
01.2 version 3.2
§_ystem Leve\ TEST C ASE S lRD SO)
Test ID/ Test Sce n ari o Input Specification
Expected OutputNalues
Title/
Oescrip
tion
19.5 After each successful \ . E nsure Keys are avai\ab\e MAC code sha\\ be observed in the Radio
Identification with both Loco TCAS unit \og of both Stationary TCAS & Loco TCAS
&Authentication & Stationary TCASunit.
dialogue, the data shall 2. Simulate a Loco movement
be protected using a in the Stationary TCAS unit
Message Authentication vicinity.
Code 3. Check the MAC code in the
Radio log of both Stationary
TCAS & Loco TCAS units.
19.6 All messages in timeslots 1. Ensure Keys are not SOS message shall be received in the Loco
reserved for emergency available in both Loco TCAS unit and same shall be observed on
communication and Loco- TCAS unit & Stationary theDMl
to-Loco direct TCAS units.
communication , are not 2. Simulate a Loco movement
subjected l&A dialogue in the Stationary TCAS
due to nature of the vicinity.
information conveyed by 3. Generate SOS from
such messages. Stationary TCASunit
19.7 Stationary TCAS or Loco 1. Ensure Keys are available Query messages of Stationary 1:CA..S and
Representative of Firm ROSO \nspecting Ottkia\
( )
 li I!
Effective from 24.09.2018 SIF :-0533 Version- 2.0 Page 135 of 141
ISO9001:2015
Document Title: Functional Test Cases at System Level for Train Collision Avoidance System RDSO/SPN/196/2012 version 3.~
System Level TEST CASES (RD SO) \
Expected Output/Values 0 bserved Output
Test ID/ Test Scenario Input Specification (P ass/Fail)
Title/
Descrip
tion
TCAS unit shall send the with both Loco TCAS unit Loco TCAS shall be observed in KMS
Authentication query & Stationary TCAS unit. server log.
message to KMS every 6 2. Stationary TCAS and Loco
hours
\
TCAS should send a query
message to KMS for every 6
hours
19.8 If TCAS sub-systems find 1. Update the Key sets in KMS Keys status shall be updated in Stationary \
that new set of server. TCAS unit within 6Hrs 24minutes.
Authentication keys are 2. Stationary TCAS ( ID: 503)
available at KMS, it shall should send key request at Keys status shall be updated in Loco TCAS
send request to Key 23 minutes after getting unit within 6Hrs 15 minutes
Management Systemat updated keys status from
randomized time over KMS server.
next 2 hours. 3. Loco TCAS ( ID: 27854)
should send key request at
14 minutes after getting
Randomized request shall updated keys status from
be as follows : KMS server.
Request time in a day
minutes= (Loco ID or
Station ID) mod (2Hr * 60
min).
Representative of Firm ROSO Inspecting Official
 24 09 2 1 SIF :-0S33 Version - 2.0 , Page 1.36 of 141.
I Effectiv e from - - 0l8
150900 1:2015 t RDSO/ SPN/19 6/201.2 version 3 .2
em Level for Train Collisio n ~voida nce System
Docum ent Title: Functio nal Test Cases at SyS
~ystem Level TEST CASES (ROSO )
Test ID/ / Test Scena rio Input Specif ication
Expec ted Out putNa lues
Ti tle/
Descri p .r
tion
19.9 If the first reque st is not I. Updat e the Key sets in KMS ....
succes sful, it shall send server .
KMS log shall be observed that request for
reque st for every 30 2. . Chang e IP Adress to wrong every 30 minutes.
minute s until it receiv es KMS server
inform ation from Key 3. Loco TCAS should send the
Manag e ment System . reque st to KMS for every 30
minut es
19.10 Statio nary /Loco TCAS 1. Confi gure the IP addre ss of Log should be observ ed in the KMS server
shall have the follow ing KMS server in Statio nary
registe red URL
for the newly config ured TCAS units.
TCAS unit
2. Confi gure the IP addre ss of
KMS serve r in Loco TCAS
unit
Obse rve the Log ofKM S serve r for
the above confi gured T AS units
19.11 Statio nary TCAS or Loco 1. Remo ve the GSM anten nae 1. Log shall not be obser ved in the
TCAS shall send the of both Statio nary TCAS KMS server , when GSM antenn ae
aunth eticat ion reque st unit and Loco TCAS unit. are remov ed.
messa ge throu gh GPRS 2.Conf igure the IP addre ss in Log shall be obser ved in the KMS server ,
both the TCAS units when GSM anten nae are conne cted.
Conn ect the disco nnect ed GSM
anten nae
ROSO Inspec ting Offlcia\
Representative of Firm
Q
 ~ I!
1509001:2015 I Effective from 24.09.2018 I SIF :-0533 Version- 2 .0 I Page 137 of 141
Document Title: Functiona l Test Cases at System Level for Train Collision Avoidance System RDSO/SPN/196/2012 version 3 .2
System Level TEST CASES (ROSO) I
1
\
Test ID/ Test Scenario In put Specification Expected OutpuWalues O bserved Output
Ti tle/ {Pass/Fall)
Descrip
tion I
19.12 Stationary TCAS or Loco l. Update the keys at KMS Stationary TCAS or Loco TCAS
TCAS shall send the server. identification message shall be observed in
the KMS log
\
Identification message to 2. Stationary TCAS or Loco
KMS when new set of TCAS should send the
Keys are to be delivered. identification message to get
the updated keys.
\
19.13 TCAS system shall store
the authentication key in
I. Ensure latest key sets are Communication should be established
between the two TCAS units.
\ \
available in Loco
non- volatile memory. Loco TCAS unit should switch from SR to
TCAS/Stationary TCAS
Power off and check for
the same 2. Switch OFF the Power for LS/FS mode. Same shall be observed on the
Loco TCAS/Stationary DMI
TCAS
3. Switch ON the Power for
Loco TCAS/Stationary
TCAS
Simulate a Loco movement in
I stationary TCAS unit vicinity
19.14 Computation of session Input for Stationary TCAS to be
key (Ks) decided by OEM
Ks= AES(KA. { Rs/RL)/
Input for Loco TCAS to be decided by
Rs/RL )/ ( RLIRS )/
OEM
(RL/RS)
19.15 Generic Authentication
Calculation ( CBC-MAC)
Input for Loco TCAS to be decided by
OEM \ \
Input for Loco TCAS
\ \
19.16 Cipher block chanining 1. Simulate a Loco movement 1. Communication should not be
\ \
\
I Representative of Firm ROSO Inspecting Officia\ \
 24 09 1 ~IF :-0533 Versio n- 2.0 1 Page 138 of 141
IS090 01:20 15 I Effect ive from - -2018 n 3.2
ance Syste m RDSO /SPN/ 196/2 012 versio
at Syste m Level for Train Collis ion Avoid
Docu ment Title: Funct ional Test Cases
Syste m L~vel TEST CASE S (ROS O)
I Test Scen ario In put Spec ificat ion Expe cted Outp uWal ues Obs erved Outpu t
Test I D/
Title/ (Pass /Fall)
Desc rip
t i on
mess age aunth etlcat ion in the Stati onary TCA S unit estab lishe d and Loco shoul d
code (CBC -MAC ) vicin ity (Key s are not conti nue to SR mode .
Applic ation
avail able with Loco TCA S Com muni catio n shou ld be estab lishe d, Loco
unit & keys are avail able TCA S shou ld switc h from SR to LS/F S
with Stati onary TCA S unit) mode .
2 . Simu late a Loco move ment
in the Stati onary TCA S unit
vicin ity ((Ke ys avail able in
both Loco TCA S unit &
Stati onar y TCA S unit)
19. 17 Claus e no 5.4.3 .7.1.9 1. Set the 'fO' frequ ency as 1. Com muni catio n shou ld not be
diffe rent in Loco TCA S and estab lishe d and Loco shou ld
On ente ring into Stati onar y TCA S. Simu late a conti nue to SR mode .
"Com mun icatio n Loco mov emen t in the 2. Com muni catio n shou ld be
man dato ry Zone " in Stati onar y TCA S unit estab lishe d, Loco TCA S shou ld
vicin ity of Stati onar y vicin ity. switc h from SR to LS/F S mode .
TCAS territ ory, Loco TCAS 2. Set the ' fO ' frequ ency as
unit send s the Access same in Loco TCA S and
Requ est pack et to Stati onar y TCA S. Simu late a
Stati onar y TCAS syste m in Loco mov eme nt in the
"fo" frequ ency . Stati onar y TCA S unit
vicin ity.
\
ROSO \nspe cting Off1tia\ J
Repr esen tative of Firm
it
IS09001:2015

n
I Effective from 24.09.2018 I SIF :-0533 Version- 2.0

8
I Page 139 of 141
Document Title: Functional Test Cases at System Level for Train Collision Avoidance System RDSO/SPN/196/2012 version 3.2
System Level TEST CASES (ROSO)
Test ID/ Test Scenari o Input Specification Expected OutpuWalues Observed Output
Title/ (Pass/Fail)
Descrip
tion
19.18 5.4.3.7.1.10 1. Simulate a Loco movement Access Authority packet should contain
On reception of Access in the Stationary TCAS unit Random Number (RS) and MAC code.
Request Packet from vicinity. Same shall be observed in Loco Radio Log
Loco TCASUnit, 2. Loco should sendAccess
Stationary TCAS unit request message.
generates its own 3. Station should send Access
Random Number (Rs) and Authority packet
computes the session key
Ksand transmits the
AccessAuthoritymessage
with CBC-MAC code.
Access Authority message
contains frequency pair
and Random Number Rs.
Representative of Firm RDSO Inspecting Official
 1S09001 :2015 \ Effective from 24.09.20 18
Docume nt Title: Function al Test Cases at System Level for Train
\ SIF :-0533 Version- 2.0 \ Page 140 of 141.
Collision Avoidan ce System ROSO/S PN/1.96/ 2012 version 3 .2

l
System Level TEST CASES (ROSO)
Test ID/ I Test Scen ario Input Speclflc atlon
Title/ Expecte d OutputN alues
Descrip
tion
19.19 Loco TCAS unit receives 1. Simula te a Loco movem ent-
the Access Authori ty Commu nication shou\d be estab\is hed, Loco
in the Station ary TCAS unit
messag e packet and vicinity . TCAS should switch from SR to LS/rS
mode
comput e the session key 2. Loco should send Access
Ks. The CBC-MA C will be request messag e.
comput ed for the Access 3. Station should send Access
Author ity messag e packet Author ity packet
and verify with receive d 4 . Loco should respon d with
CBC-MA C. If CBC-MA C is Regula r packet
success ful, Loco starts
commu nicating the
regular packet and stops
sending the Access
Reques t Packet.
Repres entativ e of Firm ROSO \nspect ing Ottkia\
1
,,
l
 5 IJ
IS09001:2015 Effective from 24.09.2018 SIF :-0533 Version- 2.0 Page 141 of 141
Document Title: Functional Test Cases at System Level for Train Collision Avoidance System RDSO/SPN/196/2012 version
3.2
System Level TEST CASES (ROSO)
Test ID/ Test Scenario Input Specification Expected OutputNalues Ob served Output
Title/ (P ass/Fail)
Descrip
tion
19.20 When Stationary TCAS l. Simulate a Loco movement Sequence of packet transmissions shall be
receives the loco regular in the Stationary TCAS unit observed in the Loco Radio log.
packet, it stops vicinity. After getting the Regular packet from
communicatin g the 2. Loco should sendAccess Stationary TCAS, Access Authority packet
Access Authority message request message. shall not be observed in the Loco Radio log.
and initiates the 3. Station should send Access
Stationary regular packet Authority packet
and static speed profile 4. Loco should respond with
packet transmission . Regular packet
5. Station TCAS should stop
sending the Access authority .
packets and start sending the
Station regular packet
19.21 Further, Stationary TCAS 1. Simulate a Loco movement 1. Communication should not be
and Loco TCAS units in the Stationary TCAS unit established and Loco should
verify the CBC-MAC code vicinity (Keys are not continue to SR mode.
for every message before available with Loco TCAS Communication should be established, Loco
processing. unit & keys are available TCAS should switch from SR to LS/FS
with Stationary TCAS unit) mode.
2. Simulate a Loco movement
in the Stationary TCAS unit
vicinity ((Keys available in
both Loco TCAS unit &
Stationary TCAS unit)
I
Representativ e of Firm
RDSO Inspecting Official