27.22.7 EVENT DOWNLOAD
3GPP51.010-4Mobile Station (MS) conformance specificationPart 4: Subscriber Identity Module (SIM) application toolkit conformance test specificationRelease 17TS
27.22.7.1 MT Call Event
27.22.7.1.1 MT Call Event (normal)
27.22.7.1.1.1 Definition and applicability
See clause 3.2.2.
27.22.7.1.1.2 Conformance requirement
The ME shall support the EVENT: MT Call event as defined in:
– TS 11.14 [15] clause 4.7, clause 5.2, clause 6.4.16, clause 6.8, clause 11, clause 11.1 and clause 12.25.
27.22.7.1.1.3 Test purpose
To verify that the ME informs the SIM that an Event: MT Call has occurred using the ENVELOPE (EVENT DOWNLOAD – MT Call) command.
27.22.7.1.1.4 Method of test
27.22.7.1.1.4.1 Initial conditions
The ME is connected to the SIM Simulator and the System Simulator.
The ME shall be powered on and perform the PROFILE DOWNLOAD procedure.
27.22.7.1.1.4.2 Procedure
Expected Sequence 1.1 (EVENT DOWNLOAD -MT Call event)
|
Step |
Direction |
Message / Action |
Comments |
|
1 |
SIM ME |
PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.1.1 |
|
|
2 |
ME SIM |
FETCH |
|
|
3 |
SIM ME |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1 |
|
|
4 |
ME SIM |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1 |
|
|
5 |
SS ME |
CALL SET UP without CLI |
[MT Call Set Up Without CLI] |
|
6 |
ME SIM |
ENVELOPE: EVENT DOWNLOAD – MT Call 1.1.1 |
|
|
7 |
SS ME |
CALL DISCONNECT |
|
|
8 |
SS ME |
CALL SET UP with CLI |
[MT Call Set Up With CLI] |
|
9 |
ME SIM |
ENVELOPE: EVENT DOWNLOAD – MT Call 1.1.2 |
|
|
10 |
SS ME |
CALL DISCONNECT |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: SIM
Destination device: ME
Event list
Event 1: MT call
Coding:
|
BER-TLV: |
D0 |
0C |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
81 |
82 |
99 |
|
01 |
00 |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
EVENT DOWNLOAD – MT CALL 1.1.1
Logically:
Event list: MT call event
Device identities
Source device: Network
Destination device: SIM
Transaction identifier:
Ti value: 0 (bit 5-7)
Ti flag: 0 (bit 8)
Coding:
|
BER-TLV: |
D6 |
0A |
19 |
01 |
00 |
82 |
02 |
83 |
81 |
1C |
01 |
00 |
EVENT DOWNLOAD – MT CALL 1.1.2
Logically:
Event list: MT call event
Device identities
Source device: Network
Destination device: SIM
Transaction identifier:
Ti value: 0 (bit 5-7)
Ti flag: 0 (bit 8)
Address:
TON Unknown
NPI "ISDN / telephone numbering plan"
Dialling number string "9876"
Coding:
|
BER-TLV: |
D6 |
0F |
19 |
01 |
00 |
82 |
02 |
83 |
81 |
1C |
01 |
00 |
|
86 |
03 |
81 |
89 |
67 |
27.22.7.1.1.5 Test requirement
The behaviour of the test is as defined in ‘Expected Sequence 1.1’.
27.22.7.2 Call Connected Event
27.22.7.2.1 Call Connected Event (MT and MO call)
27.22.7.2.1.1 Definition and applicability
See clause 3.2.2.
27.22.7.2.1.2 Conformance requirement
The ME shall support the EVENT: Call Connected event as defined in:
– TS 11.14 [15] clause 4.7, clause 5.2, clause 6.4.16, clause 6.8, clause 11, clause 11.2 and clause 12.25.
27.22.7.2.1.3 Test purpose
To verify that the ME informs the SIM that an Event: Call Connected has occurred using the ENVELOPE (EVENT DOWNLOAD -Call Connected) command.
27.22.7.2.1.4 Method of test
27.22.7.2.1.4.1 Initial conditions
The ME is connected to the SIM Simulator and the System Simulator.
The ME shall be powered on and perform the PROFILE DOWNLOAD procedure.
27.22.7.2.1.4.2 Procedure
Expected Sequence 1.1 (EVENT DOWNLOAD -CALL CONNECTED)
|
Step |
Direction |
Message / Action |
Comments |
|
1 |
SIM ME |
PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.1.1 |
|
|
2 |
ME SIM |
FETCH |
|
|
3 |
SIM ME |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1 |
[EVENT: Call Connected active] |
|
4 |
ME SIM |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1 |
|
|
5 |
SS ME |
SETUP |
[MT Call] Ti = 0 |
|
6 |
USER ME |
Accept Call Set Up |
|
|
7 |
MESS |
CONNECT |
|
|
8 |
ME SIM |
ENVELOPE: EVENT DOWNLOAD – Call Connected 1.1.1 |
|
|
9 |
SS ME |
DISCONNECT |
|
|
10 |
USER ME |
Initiate Call to "123" |
|
|
11 |
ME SS |
SETUP |
[MO Call] Ti = 0 |
|
12 |
SS ME |
CONNECT |
|
|
13 |
ME SIM |
ENVELOPE: EVENT DOWNLOAD – Call Connected 1.1.2 |
|
|
14 |
USER ME |
End Call |
|
|
15 |
ME SS |
DISCONNECT |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: SIM
Destination device: ME
Event list
Event 1: Call Connected
Coding:
|
BER-TLV: |
D0 |
0C |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
81 |
82 |
99 |
|
01 |
01 |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
EVENT DOWNLOAD – CALL CONNECTED 1.1.1
Logically:
Event list: Call connected
Device identities
Source device: ME
Destination device: SIM
Transaction identifier:
Ti value: 0 (bit 5-7)
Ti flag: 1 (bit 8)
Coding:
|
BER-TLV: |
D6 |
0A |
19 |
01 |
01 |
82 |
02 |
82 |
81 |
1C |
01 |
80 |
EVENT DOWNLOAD – CALL CONNECTED 1.1.2
Logically:
Event list: Call connected
Device identities
Source device: Network
Destination device: SIM
Transaction identifier:
Ti value: 0 (bit 5-7)
Ti flag: 1 (bit 8)
Coding:
|
BER-TLV: |
D6 |
0A |
19 |
01 |
01 |
82 |
02 |
83 |
81 |
1C |
01 |
80 |
27.22.7.2.1.5 Test requirement
The behaviour of the test is as defined in ‘Expected Sequence 1.1’.
27.22.7.2.2 Call Connected Event (ME supporting SET UP CALL)
27.22.7.2.2.1 Definition and applicability
See clause 3.2.2.
27.22.7.2.2.2 Conformance requirement
Additionally the ME shall support the SET UP CALL Proactive SIM Command as defined in:
– TS 11.14 [15] clause 11.2.2, clause 6.4.13 and clause 6.6.12.
27.22.7.2.2.3 Test purpose
To verify that the ME informs the SIM that an Event: Call Connected has occurred using the ENVELOPE (EVENT DOWNLOAD -Call Connected) command.
27.22.7.2.2.4 Method of test
27.22.7.2.2.4.1 Initial conditions
The ME is connected to the SIM Simulator and the System Simulator.
The ME shall be powered on and perform the PROFILE DOWNLOAD procedure.
27.22.7.2.2.4.2 Procedure
Expected Sequence 2.1 (EVENT DOWNLOAD -CALL CONNECTED, ME supporting SET UP CALL)
|
Step |
Direction |
Message / Action |
Comments |
|
1 |
SIM ME |
PROACTIVE COMMAND PENDING: SET UP EVENT LIST 2.1.1 |
|
|
2 |
ME SIM |
FETCH |
|
|
3 |
SIM ME |
PROACTIVE COMMAND: SET UP EVENT LIST 2.1.1 |
[EVENT: Call Connected active] |
|
4 |
ME SIM |
TERMINAL RESPONSE: SET UP EVENT LIST 2.1.1 |
|
|
5 |
SIM ME |
PROACTIVE COMMAND PENDING |
|
|
6 |
ME SIM |
FETCH |
|
|
7 |
SIM ME |
PROACTIVE COMMAND: SET UP CALL 2.1.1 |
[SAT Call] |
|
8 |
ME USER |
ME displays "+012340123456" during the user confirmation phase. |
ME BEHAVIOUR: SET UP CALL |
|
9 |
USER ME |
Confirm call set up |
|
|
10 |
ME SS |
SETUP |
Ti=0 |
|
11 |
SS ME |
CONNECT |
|
|
12 |
ME SIM |
TERMINAL RESPONSE: SET UP CALL 2.1.1 |
|
|
13 |
ME SIM |
ENVELOPE: CALL CONNECTED 2.1.1 |
PROACTIVE COMMAND: SET UP EVENT LIST 2.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: SIM
Destination device: ME
Event list
Event 1: Call Connected
Coding:
|
BER-TLV: |
D0 |
0C |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
81 |
82 |
99 |
|
01 |
01 |
TERMINAL RESPONSE: SET UP EVENT LIST 2.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
PROACTIVE COMMAND: SET UP CALL 2.1.1
Logically:
Command details
Command number: 1
Command type: SET UP CALL
Command qualifier: Only if not currently busy on another call
Device identities
Source device: SIM
Destination device: Network
Alpha identifier: "+012340123456"
Address
TON: International
NPI: "ISDN / telephone numbering plan"
Dialling number string "012340123456"
Coding:
|
BER-TLV: |
D0 |
21 |
81 |
03 |
01 |
10 |
00 |
82 |
02 |
81 |
83 |
|
05 |
0D |
2B |
30 |
31 |
32 |
33 |
34 |
30 |
31 |
32 |
|
|
33 |
34 |
35 |
36 |
86 |
07 |
91 |
10 |
32 |
04 |
21 |
|
|
43 |
65 |
TERMINAL RESPONSE: SET UP CALL 2.1.1
Logically:
Command details
Command number: 1
Command type: SET UP CALL
Command qualifier: Only if not currently busy on another call
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
10 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
EVENT DOWNLOAD – CALL CONNECTED 2.1.1
Logically:
Event list: Call connected
Device identities
Source device: Network
Destination device: SIM
Transaction identifier:
Ti value: 0 (bit 5-7)
Ti flag: 1 (bit 8)
Coding:
|
BER-TLV: |
D6 |
0A |
19 |
01 |
01 |
82 |
02 |
83 |
81 |
1C |
01 |
80 |
27.22.7.2.2.5 Test requirement
The behaviour of the test is as defined in ‘Expected Sequence 2.1’.
27.22.7.3 Call Disconnected Event
27.22.7.3.1 Call Disconnected Event
27.22.7.3.1.1 Definition and applicability
See clause 3.2.2.
27.22.7.3.1.2 Conformance requirement
The ME shall support the EVENT: Call Disconnected event as defined in:
– TS 11.14 [15] clause 4.7, clause 5.2, clause 6.4.16, clause 6.8, clause 11, clause 11.3 and clause 12.25.
27.22.7.3.1.3 Test purpose
To verify that the ME informs the SIM that an Event: Call Disconnected has occurred using the ENVELOPE (EVENT DOWNLOAD -Call Disconnected) command.
27.22.7.3.1.4 Method of test
27.22.7.3.1.4.1 Initial conditions
The ME is connected to the SIM Simulator and the System Simulator.
The ME shall be powered on and perform the PROFILE DOWNLOAD procedure.
27.22.7.3.1.4.2 Procedure
Expected Sequence 1.1 (EVENT DOWNLOAD -CALL DISCONNECTED)
|
Step |
Direction |
Message / Action |
Comments |
|
1 |
SIM ME |
PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.1.1 |
|
|
2 |
ME SIM |
FETCH |
|
|
3 |
SIM ME |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1 |
[EVENT: Call Disconnected active] |
|
4 |
ME SIM |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1 |
|
|
5 |
SS ME |
SETUP |
[ incoming call ] Ti=0 |
|
6 |
USER ME |
Accept Call Set Up |
|
|
7 |
SS ME |
RELEASE |
[MT RELEASE] |
|
8 |
ME SIM |
ENVELOPE: CALL DISCONNECTED 1.1.1 |
|
|
9 |
SS ME |
SETUP |
[ incoming call ] Ti=0 |
|
10 |
USER ME |
Accept Call Set Up |
|
|
11 |
SS ME |
RELEASE COMPLETE |
[MT RELEASE COMPLETE] |
|
12 |
ME SIM |
ENVELOPE: CALL DISCONNECTED 1.1.1 |
|
|
13 |
SS ME |
SETUP |
[ incoming call ] Ti=0 |
|
14 |
USER ME |
Accept Call Set Up |
|
|
15 |
USER ME |
End Call |
|
|
16 |
ME SS |
DISCONNECT |
[MO DISCONNECT] |
|
17 |
ME SIM |
ENVELOPE: CALL DISCONNECTED 1.1.2A or ENVELOPE: CALL DISCONNECTED 1.1.2B or ENVELOPE: CALL DISCONNECTED 1.1.2C |
|
|
18 |
SS ME |
SETUP |
[ incoming call ] Ti=0 |
|
19 |
USER ME |
Accept Call Set Up |
|
|
20 |
SS ME |
DISCONNECT |
[MT DISCONNECT + CAUSE: normal call clearing ] |
|
21 |
ME SIM |
ENVELOPE: CALL DISCONNECTED 1.1.3A or ENVELOPE: CALL DISCONNECTED 1.1.3B |
|
|
22 |
SS ME |
SETUP |
Ti=0 |
|
23 |
USER ME |
Accept Call Set Up |
|
|
24 |
SS |
TX POWER to XX |
[RADIO LINK FAILURE] |
|
25 |
ME SIM |
ENVELOPE: CALL DISCONNECTED 1.1.4A or 1.1.4B |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: SIM
Destination device: ME
Event list
Event 1: Call Disconnected
Coding:
|
BER-TLV: |
D0 |
0C |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
81 |
82 |
99 |
|
01 |
02 |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
EVENT DOWNLOAD – CALL DISCONNECTED 1.1.1
Logically:
Event list: Call Disconnected
Device identities
Source device: Network
Destination device: SIM
Transaction identifier:
Ti value: 0 (bit 5-7)
Ti flag: 0 (bit 8)
Cause:
Coding:
|
BER-TLV: |
D6 |
0A |
19 |
01 |
02 |
82 |
02 |
83 |
81 |
1C |
01 |
00 |
EVENT DOWNLOAD – CALL DISCONNECTED 1.1.2A
Logically:
Event list: Call Disconnected
Device identities
Source device: ME
Destination device: SIM
Transaction identifier:
Ti value: 0 (bit 5-7)
Ti flag: 1 (bit 8)
Coding:
|
BER-TLV: |
D6 |
0A |
19 |
01 |
02 |
82 |
02 |
82 |
81 |
1C |
01 |
80 |
EVENT DOWNLOAD – CALL DISCONNECTED 1.1.2B
Logically:
Event list: Call Disconnected
Device identities
Source device: ME
Destination device: SIM
Transaction identifier:
Ti value: 0 (bit 5-7)
Ti flag: 1 (bit 8)
Cause: normal call clearing
Coding:
|
BER-TLV: |
D6 |
0E |
19 |
01 |
02 |
82 |
02 |
82 |
81 |
1C |
01 |
80 |
|
9A |
02 |
60 |
90 |
EVENT DOWNLOAD – CALL DISCONNECTED 1.1.2C
Logically:
Event list: Call Disconnected
Device identities
Source device: ME
Destination device: SIM
Transaction identifier:
Ti value: 0 (bit 5-7)
Ti flag: 1 (bit 8)
Cause: normal call clearing
Coding:
|
BER-TLV: |
D6 |
0E |
19 |
01 |
02 |
82 |
02 |
82 |
81 |
1C |
01 |
80 |
|
9A |
02 |
E0 |
90 |
EVENT DOWNLOAD – CALL DISCONNECTED 1.1.3A
Logically:
Event list: Call Disconnected
Device identities
Source device: Network
Destination device: SIM
Transaction identifier:
Ti value: 0 (bit 5-7)
Ti flag: 0 (bit 8)
Cause: normal call clearing
Coding:
|
BER-TLV: |
D6 |
0E |
19 |
01 |
02 |
82 |
02 |
83 |
81 |
1C |
01 |
00 |
|
9A |
02 |
60 |
90 |
EVENT DOWNLOAD – CALL DISCONNECTED 1.1.3B
Logically:
Event list: Call Disconnected
Device identities
Source device: Network
Destination device: SIM
Transaction identifier:
Ti value: 0 (bit 5-7)
Ti flag: 0 (bit 8)
Cause: normal call clearing
Coding:
|
BER-TLV: |
D6 |
0E |
19 |
01 |
02 |
82 |
02 |
83 |
81 |
1C |
01 |
00 |
|
9A |
02 |
E0 |
90 |
EVENT DOWNLOAD – CALL DISCONNECTED 1.1.4A
Logically:
Event list: Call Disconnected
Device identities
Source device: ME
Destination device: SIM
Transaction identifier:
Ti value: 0 (bit 5-7)
Ti flag: 1 (bit 8)
Cause: radio link failure
Coding:
|
BER-TLV: |
D6 |
0C |
19 |
01 |
02 |
82 |
02 |
82 |
81 |
1C |
01 |
80 |
|
9A |
00 |
EVENT DOWNLOAD – CALL DISCONNECTED 1.1.4B
Logically:
Event list: Call Disconnected
Device identities
Source device: ME
Destination device: SIM
Transaction identifier:
Ti value: 0 (bit 5-7)
Ti flag: 0 (bit 8)
Cause: radio link failure
Coding:
|
BER-TLV: |
D6 |
0C |
19 |
01 |
02 |
82 |
02 |
82 |
81 |
1C |
01 |
00 |
|
9A |
00 |
27.22.7.3.1.5 Test requirement
The behaviour of the test is as defined in ‘Expected Sequence 1.1’.
27.22.7.4 Location Status Event
27.22.7.4.1 Location Status Event (normal)
27.22.7.4.1.1 Definition and applicability
See clause 3.2.2.
27.22.7.4.1.2 Conformance requirement
The ME shall support the EVENT: Location Status event as defined in:
– TS 11.14 [15] clause 11.4 and clause 6.4.16.
27.22.7.4.1.3 Test purpose
To verify that the ME informs the SIM that an Event: MM_IDLE state has occurred using the ENVELOPE (EVENT DOWNLOAD – Location Status) command.
27.22.7.4.1.4 Method of test
27.22.7.4.1.4.1 Initial conditions
The ME is connected to the SIM Simulator and the System Simulator.
The ME shall be powered on and perform the PROFILE DOWNLOAD procedure.
The GSM parameters of the system simulator are:
– Mobile Country Code (MCC) = 001;
– Mobile Network Code (MNC) = 01 ;
– Location Area Code (LAC) = 0001;
– Cell Identity value = 0001;
The PCS 1900 parameters of the system simulator are:
– Mobile Country Code (MCC) = 001;
– Mobile Network Code (MNC) = 011;
– Location Area Code (LAC) = 0001;
– Cell Identity value = 0001.
Two cells are defined. Cell 1 has location area code 1 and cell 2 has location area code 2.
MS is in service on Cell 1.
27.22.7.4.1.4.2 Procedure
Expected Sequence 1.1(EVENT DOWNLOAD -LOCATION STATUS)
|
Step |
Direction |
Message / Action |
Comments |
|
1 |
SIM ME |
PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.1.1 |
|
|
2 |
ME SIM |
FETCH |
|
|
3 |
SIM ME |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1 |
|
|
4 |
ME SIM |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1 |
IF A.1/100 THEN ME sends a ENVELOPE: EVENT DOWNLOAD – Location Status 1.1.1A [apply for GSM parameters] or ENVELOPE: EVENT DOWNLOAD – Location Status 1.1.1B [apply for PCS1900 parameters]. |
|
5 |
SS |
Cell 1 is switched off |
|
|
6 |
ME SIM |
ENVELOPE: EVENT DOWNLOAD – Location Status 1.1.1 |
|
|
7 |
SS |
Cell 2 is switched on after Location Status “No service” has been received in step 6 |
|
|
8 |
ME |
ME performs cell reselection to cell 2 |
|
|
9 |
ME SS |
Location Updating Request |
|
|
10 |
SS ME |
Location updating accept |
|
|
11 |
ME SIM |
ENVELOPE: EVENT DOWNLOAD – Location Status 1.1.2A or ENVELOPE: EVENT DOWNLOAD – Location Status 1.1.2B |
[Option A shall apply for GSM parameters] [Option B shall apply for PCS1900 parameters] [Note: The inclusion of the location information is optional: (If location status indicates normal status) |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: SIM
Destination device: ME
Event list
Event 1: Location status
Coding:
|
BER-TLV: |
D0 |
0C |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
81 |
82 |
99 |
|
01 |
03 |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
EVENT DOWNLOAD – LOCATION STATUS 1.1.1
Logically:
Event list: Location status
Device identities
Source device: ME
Destination device: SIM
Location status: No service
Coding:
|
BER-TLV: |
D6 |
0A |
19 |
01 |
03 |
82 |
02 |
82 |
81 |
1B |
01 |
02 |
EVENT DOWNLOAD – LOCATION STATUS 1.1.1A
Logically:
Event list: Location status
Device identities
Source device: ME
Destination device: SIM
Location status: normal service
Location Information
MCC & MNC the mobile country and network code (00F110)
LAC the location Area Code (0001)
Cell ID Cell Identity Value (0001)
Coding:
|
BER-TLV: |
D6 |
13 |
19 |
01 |
03 |
82 |
02 |
82 |
81 |
1B |
01 |
00 |
|
13 |
07 |
00 |
F1 |
10 |
00 |
01 |
00 |
01 |
EVENT DOWNLOAD – LOCATION STATUS 1.1.1B
Logically:
Event list: Location status
Device identities
Source device: ME
Destination device: SIM
Location status: normal service
Location Information
MCC & MNC the mobile country and network code (001110)
LAC the location Area Code (0001)
Cell ID Cell Identity Value (0001)
Coding:
|
BER-TLV: |
D6 |
13 |
19 |
01 |
03 |
82 |
02 |
82 |
81 |
1B |
01 |
00 |
|
13 |
07 |
00 |
11 |
10 |
00 |
01 |
00 |
01 |
EVENT DOWNLOAD – LOCATION STATUS 1.1.2A
Logically:
Event list: Location status
Device identities
Source device: ME
Destination device: SIM
Location status: normal service
Location Information
MCC & MNC the mobile country and network code (00F110)
LAC the location Area Code (0002)
Cell ID Cell Identity Value (0002)
Coding:
|
BER-TLV: |
D6 |
13 |
19 |
01 |
03 |
82 |
02 |
82 |
81 |
1B |
01 |
00 |
|
13 |
07 |
00 |
F1 |
10 |
00 |
02 |
00 |
02 |
EVENT DOWNLOAD – LOCATION STATUS 1.1.2B
Logically:
Event list: Location status
Device identities
Source device: ME
Destination device: SIM
Location status: normal service
Location Information
MCC & MNC the mobile country and network code (001110)
LAC the location Area Code (0002)
Cell ID Cell Identity Value (0002)
Coding:
|
BER-TLV: |
D6 |
13 |
19 |
01 |
03 |
82 |
02 |
82 |
81 |
1B |
01 |
00 |
|
13 |
07 |
00 |
11 |
10 |
00 |
02 |
00 |
02 |
27.22.7.4.1.5 Test requirement
The behaviour of the test is as defined in ‘Expected Sequence 1.1’.
27.22.7.5 User Activity Event
27.22.7.5.1 User Activity Event (normal)
27.22.7.5.1.1 Definition and applicability
See clause 3.2.2.
27.22.7.5.1.2 Conformance Requirement
The ME shall support the EVENT DOWNLOAD -USER ACTIVITY as defined in:
– TS 11.14 [15] clause 5.2, clause 6.4.16, clause 6.8, clause 6.6.16, clause 6.11, clause 11, clause 11.5, clause 12.6 and clause 12.25.
27.22.7.5.1.3 Test purpose
To verify that the ME performed correctly the procedure of USER ACTIVITY EVENT.
27.22.7.5.1.4 Method of Test
27.22.7.5.1.4.1 Initial conditions
The ME is connected to the SIM Simulator.
The elementary files are coded as Toolkit default.
Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.
The ME screen shall be in its normal stand-by display.
27.22.7.5.1.4.2 Procedure
Expected Sequence 1.1 (EVENT DOWNLOAD -USER ACTIVITY)
|
Step |
Direction |
MESSAGE / Action |
Comments |
|
1 |
SIM → ME |
PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.1.1 |
[set up event list: event User Activity] |
|
2 |
ME → SIM |
FETCH |
|
|
3 |
SIM → ME |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1 |
[set up event list: event User Activity] |
|
4 |
ME → SIM |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1 |
[command performed successfully] |
|
5 |
USER → ME |
press any key |
|
|
6 |
ME → SIM |
ENVELOPE EVENT DOWNLOAD -USER ACTIVITY 1.1.1 |
|
|
7 |
USER → ME |
press any key |
check if no envelope Event Download-User activity sending to the SIM ( this event is reported once) |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: RFU
Device identities
Source device: SIM
Destination device: ME
Event list User Activity
Coding:
|
BER-TLV: |
D0 |
0C |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
81 |
82 |
99 |
|
01 |
04 |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: RFU
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
EVENT DOWNLOAD -USER ACTIVITY 1.1.1
Logically:
Event list User Activity
Device identities
Source device: ME
Destination device: SIM
Coding:
|
BER-TLV: |
D6 |
07 |
19 |
01 |
04 |
82 |
02 |
82 |
81 |
27.22.7.5.1.5 Test requirement
The ME shall operate in the manner defined in expected sequence 1.1.
27.22.7.6 Idle screen available event
27.22.7.6.1 Idle Screen Available (normal)
27.22.7.6.1.1 Definition and applicability
See clause 3.2.2.
27.22.7.6.1.2 Conformance requirement
The ME shall support the EVENT: IDLE SCREEN AVAILABLE event as defined in:
– TS 11.14 [15] clause 4.7, clause 5.2, clause 6.4.16, clause 6.8, clause 11, clause 11.1 and clause 12.25.
27.22.7.6.1.3 Test purpose
To verify that the ME informs the SIM that an Event: Idle Screen Available has occurred using the ENVELOPE (EVENT DOWNLOAD – IDLE SCREEN AVAILABLE) command.
27.22.7.6.1.4 Method of test
27.22.7.6.1.4.1 Initial conditions
The ME is connected to the SIM Simulator and the System Simulator.
The elementary files are coded as SIM Application Toolkit default.
Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure and be in updated idle mode on the System Simulator.
27.22.7.6.1.4.2 Procedure
Expected Sequence 1.1 (EVENT DOWNLOAD – IDLE SCREEN AVAILABLE)
|
Step |
Direction |
MESSAGE / Action |
Comments |
|
1 |
USER → ME |
Select screen other than the ME idle screen |
|
|
2 |
SIM → ME |
PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.1.1 |
[set up event list: idle screen available] |
|
3 |
ME → SIM |
FETCH |
|
|
4 |
SIM → ME |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1 |
[set up event list: idle screen available] |
|
5 |
ME → SIM |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1 |
[command performed successfully] |
|
6 |
USER → ME |
Select ME idle screen |
|
|
7 |
ME → SIM |
ENVELOPE: IDLE SCREEN AVAILABLE 1.1.1 |
|
|
8 |
USER → ME |
Select screen other than the ME idle screen |
|
|
9 |
USER → ME |
Select ME idle screen |
|
|
10 |
ME → SIM |
ENVELOPE: IDLE SCREEN AVAILABLE shall not be sent to the SIM |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: SIM
Destination device: ME
Event list
Event 1: idle screen available
Coding:
|
BER-TLV: |
D0 |
0C |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
81 |
82 |
99 |
|
01 |
05 |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
EVENT DOWNLOAD – IDLE SCREEN AVAILABLE 1.1.1
Logically:
Event list Idle screen available
Device identities
Source device: Display
Destination device: SIM
Coding:
|
BER-TLV: |
D6 |
07 |
19 |
01 |
05 |
82 |
02 |
02 |
81 |
27.22.7.6.1.5 Test requirement
The ME shall operate in the manner defined in expected sequence 1.1.
27.22.7.7 Card reader status event
27.22.7.7.1 Card Reader Status (normal)
27.22.7.7.1.1 Definition and applicability
See clause 3.2.2.
27.22.7.7.1.2 Conformance requirement
The ME shall support the EVENT: Call Card Reader Status event as defined in:
– TS 11.14 [15] clause 4.7, clause 4.9, clause 5.2, clause 6.4.16, clause 6.8, clause 11, clause 11.7, clause 12.25, clause 12.33, annex G, annex H, clause 12.25 and clause 12.7.
27.22.7.7.1.3 Test purpose
To verify that the ME informs the SIM that an Event: Card Reader Status has changed using the ENVELOPE (EVENT DOWNLOAD – Card Reader Status) command.
The ME-Manufacturer can assign the card reader identifier from 0 to 7.
This test applies for MEs with only one additional card reader.
In this particular case the card reader identifier 1 is chosen.
27.22.7.7.1.4 Method of test
27.22.7.7.1.4.1 Initial conditions
The ME is connected to the SIM Simulator.
The ME shall be powered on and perform the PROFILE DOWNLOAD procedure.
27.22.7.7.1.4.2 Procedure
Expected Sequence 1.1 (EVENT DOWNLOAD, Card reader status, Card reader 1, card reader attached, no card inserted)
|
Step |
Direction |
Message / Action |
Comments |
|
1 |
SIM ME |
PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.1.1 |
|
|
2 |
ME SIM |
FETCH |
|
|
3 |
SIM ME |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1 |
[EVENT: Card Reader Status] |
|
4 |
ME SIM |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1 |
[Successfully] |
|
5 |
User ME |
Insert a card in Reader |
|
|
6 |
ME SIM |
ENVELOPE: CARD READER STATUS 1.1.1a or ENVELOPE: CARD READER STATUS 1.1.1b Or ENVELOPE: CARD READER STATUS 1.1.1c Or ENVELOPE: CARD READER STATUS 1.1.1d |
|
|
7 |
User ME |
Remove the card from Reader |
|
|
8 |
ME SIM |
ENVELOPE: CARD READER STATUS 1.1.2a Or ENVELOPE: CARD READER STATUS 1.1.2b Or ENVELOPE: CARD READER STATUS 1.1.2c Or ENVELOPE: CARD READER STATUS 1.1.2d |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: SIM
Destination device: ME
Event list
Event 1: Card Reader Status
Coding:
|
BER-TLV: |
D0 |
0C |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
81 |
82 |
|
99 |
01 |
06 |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
ENVELOPE: EVENT DOWNLOAD CARD READER STATUS 1.1.1a
Logically:
Event list
Event 1: Card Reader Status
Device identities
Source device: ME
Destination device: SIM
Card reader status
Identity of card reader: 01
Card reader removable: Yes
Card reader present: Yes
Card reader ID-1 size: Yes
Card present in reader: Yes
Card powered: No
Coding:
|
BER-TLV: |
D6 |
0A |
99 |
01 |
06 |
82 |
02 |
82 |
81 |
A0 |
01 |
79 |
ENVELOPE: EVENT DOWNLOAD CARD READER STATUS 1.1.1b
Logically:
Event list
Event 1: Card Reader Status
Device identities
Source device: ME
Destination device: SIM
Card reader status
Identity of card reader: 01
Card reader removable: Yes
Card reader present: Yes
Card reader ID-1 size: No
Card present in reader: Yes
Card powered: No
Coding:
|
BER-TLV: |
D6 |
0A |
99 |
01 |
06 |
82 |
02 |
82 |
81 |
A0 |
01 |
59 |
ENVELOPE: EVENT DOWNLOAD CARD READER STATUS 1.1.1c
Logically:
Event list
Event 1: Card Reader Status
Device identities
Source device: ME
Destination device: SIM
Card reader status
Identity of card reader: 01
Card reader removable: No
Card reader present: Yes
Card reader ID-1 size: Yes
Card present in reader: Yes
Card powered: No
Coding:
|
BER-TLV: |
D6 |
0A |
99 |
01 |
06 |
82 |
02 |
82 |
81 |
A0 |
01 |
71 |
ENVELOPE: EVENT DOWNLOAD CARD READER STATUS 1.1.1d
Logically:
Event list
Event 1: Card Reader Status
Device identities
Source device: ME
Destination device: SIM
Card reader status
Identity of card reader: 01
Card reader removable: No
Card reader present: Yes
Card reader ID-1 size: No
Card present in reader: Yes
Card powered: No
Coding:
|
BER-TLV: |
D6 |
0A |
99 |
01 |
06 |
82 |
02 |
82 |
81 |
A0 |
01 |
51 |
ENVELOPE: EVENT DOWNLOAD CARD READER STATUS 1.1.2a
Logically:
Event list
Event 1: Card Reader Status
Device identities
Source device: ME
Destination device: SIM
Card reader status
Identity of card reader: 01
Card reader removable: Yes
Card reader present: Yes
Card reader ID-1 size: Yes
Card present in reader: No
Card powered: No
Coding:
|
BER-TLV: |
D6 |
0A |
99 |
01 |
06 |
82 |
02 |
82 |
81 |
A0 |
01 |
39 |
ENVELOPE: EVENT DOWNLOAD CARD READER STATUS 1.1.2b
Logically:
Event list
Event 1: Card Reader Status
Device identities
Source device: ME
Destination device: SIM
Card reader status
Identity of card reader: 01
Card reader removable: Yes
Card reader present: Yes
Card reader ID-1 size: No
Card present in reader: No
Card powered: No
Coding:
|
BER-TLV: |
D6 |
0A |
99 |
01 |
06 |
82 |
02 |
82 |
81 |
A0 |
01 |
19 |
ENVELOPE: EVENT DOWNLOAD CARD READER STATUS 1.1.2c
Logically:
Event list
Event 1: Card Reader Status
Device identities
Source device: ME
Destination device: SIM
Card reader status
Identity of card reader: 01
Card reader removable: No
Card reader present: Yes
Card reader ID-1 size: Yes
Card present in reader: No
Card powered: No
Coding:
|
BER-TLV: |
D6 |
0A |
99 |
01 |
06 |
82 |
02 |
82 |
81 |
A0 |
01 |
31 |
ENVELOPE: EVENT DOWNLOAD CARD READER STATUS 1.1.2d
Logically:
Event list
Event 1: Card Reader Status
Device identities
Source device: ME
Destination device: SIM
Card reader status
Identity of card reader: 01
Card reader removable: No
Card reader present: Yes
Card reader ID-1 size: No
Card present in reader: No
Card powered: No
Coding:
|
BER-TLV: |
D6 |
0A |
99 |
01 |
06 |
82 |
02 |
82 |
81 |
A0 |
01 |
11 |
27.22.7.7.1.5 Test requirement
The behaviour of the test is as defined in ‘Expected Sequence 1.1’.
27.22.7.7.2 Card Reader Status(detachable card reader)
27.22.7.7.2.1 Definition and applicability
See clause 3.2.2.
27.22.7.7.2.2 Conformance requirement
The ME shall support the EVENT: Call Card Reader Status event as defined in:
– TS 11.14 [15] clause 4.7, clause 4.9, clause 5.2, clause 6.4.16, clause 6.8, clause 11, clause 11.7, clause 12.25, clause 12.33, annex G, annex H, clause 12.25 and clause 12.7.
27.22.7.7.2.3 Test purpose
To verify that the ME informs the SIM that an Event: Card Reader Status has changed using the ENVELOPE (EVENT DOWNLOAD – Card Reader Status) command.
The ME-Manufacturer can assign the card reader identifier from 0 to 7.
This test applies for MEs with only one additional card reader.
In this particular case the card reader identifier 1 is chosen as an example.
27.22.7.7.2.4 Method of test
27.22.7.7.2.4.1 Initial conditions
The ME is connected to the SIM Simulator.
The ME shall be powered on and perform the PROFILE DOWNLOAD procedure.
27.22.7.7.2.4.2 Procedure
Expected Sequence 2.1 (EVENT DOWNLOAD, Detachable reader, Card reader 1, detachable card reader not attached, no card inserted)
|
Step |
Direction |
Message / Action |
Comments |
|
1 |
SIM ME |
PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.1.1 |
|
|
2 |
ME SIM |
FETCH |
|
|
3 |
SIM ME |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1 |
[SET UP EVENT: Card Reader Status] |
|
4 |
ME SIM |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1 |
[Successfully] |
|
5 |
User ME |
Attach the Card Reader to ME |
|
|
6 |
ME SIM |
ENVELOPE: CARD READER STATUS 2.1.1a Or ENVELOPE: CARD READER STATUS 2.1.1b |
|
|
7 |
User ME |
Detach the Card Reader from ME |
|
|
8 |
ME SIM |
ENVELOPE: CARD READER STATUS 2.1.2a Or ENVELOPE: CARD READER STATUS 2.1.2b |
ENVELOPE: EVENT DOWNLOAD CARD READER STATUS 2.1.1a
Logically:
Event list
Event 1: Card Reader Status
Device identities
Source device: ME
Destination device: SIM
Card reader status
Identity of card reader: 01
Card reader removable: Yes
Card reader present: Yes
Card reader ID-1 size: Yes
Card present in reader: No
Card powered: No
Coding:
|
BER-TLV: |
D6 |
0A |
99 |
01 |
06 |
82 |
02 |
82 |
81 |
A0 |
01 |
39 |
ENVELOPE: EVENT DOWNLOAD CARD READER STATUS 2.1.1b
Logically:
Event list
Event 1: Card Reader Status
Device identities
Source device: ME
Destination device: SIM
Card reader status
Identity of card reader: 01
Card reader removable: Yes
Card reader present: Yes
Card reader ID-1 size: No
Card present in reader: No
Card powered: No
Coding:
|
BER-TLV: |
D6 |
0A |
99 |
01 |
06 |
82 |
02 |
82 |
81 |
A0 |
01 |
19 |
ENVELOPE: EVENT DOWNLOAD CARD READER STATUS 2.1.2a
Logically:
Event list
Event 1: Card Reader Status
Device identities
Source device: ME
Destination device: SIM
Card reader status
Identity of card reader: 01
Card reader removable: Yes
Card reader present: No
Card reader ID-1 size: Yes
Card present in reader: No
Card powered: No
Coding:
|
BER-TLV: |
D6 |
0A |
99 |
01 |
06 |
82 |
02 |
82 |
81 |
A0 |
01 |
29 |
ENVELOPE: EVENT DOWNLOAD CARD READER STATUS 2.1.2b
Logically:
Event list
Event 1: Card Reader Status
Device identities
Source device: ME
Destination device: SIM
Card reader status
Identity of card reader: 01
Card reader removable: Yes
Card reader present: No
Card reader ID-1 size: No
Card present in reader: No
Card powered: No
Coding:
|
BER-TLV: |
D6 |
0A |
99 |
01 |
06 |
82 |
02 |
82 |
81 |
A0 |
01 |
09 |
27.22.7.7.1.5 Test requirement
The behaviour of the test is as defined in ‘Expected Sequence 2.1’.
27.22.7.8 Language selection event
27.22.7.8.1 Language selection event (normal)
27.22.7.8.1.1 Definition and applicability
See clause 3.2.2.
27.22.7.8.1.2 Conformance requirement
The ME shall support the EVENT: LANGUAGE SELECTION event as defined in:
– TS 11.14 [15] clause 4.7, clause 5.2, clause 6.4.16, clause 6.8, clause 11, clause 11.8 and clause 12.25.
27.22.7.8.1.3 Test purpose
To verify that the ME informs the SIM that an Event: Language selection has occurred using the ENVELOPE (EVENT DOWNLOAD – LANGUAGE SELECTION ) command.
27.22.7.8.1.4 Method of test
27.22.7.8.1.4.1 Initial conditions
The ME is connected to the SIM Simulator.
The elementary files are coded as SIM Application Toolkit default.
Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.
The current language shall have been set to English. Another language has to be supported, German is an example.
27.22.7.8.1.4.2 Procedure
Expected Sequence 1.1 (EVENT DOWNLOAD – LANGUAGE SELECTION)
|
Step |
Direction |
MESSAGE / Action |
Comments |
|
1 |
SIM → ME |
PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.1.1 |
[set up event list: language selection] |
|
2 |
ME → SIM |
FETCH |
|
|
3 |
SIM → ME |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1 |
[set up event list: language selection] |
|
4 |
ME → SIM |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1 |
[command performed successfully] |
|
5 |
USER → ME |
Change the language to German. |
|
|
6 |
ME → SIM |
ENVELOPE: LANGUAGE SELECTION 1.1.1 |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: SIM
Destination device: ME
Event list
Event 1: language selection
Coding:
|
BER-TLV: |
D0 |
0C |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
81 |
82 |
99 |
|
01 |
07 |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
EVENT DOWNLOAD – LANGUAGE SELECTION 1.1.1
Logically:
Event list Language selection
Device identities
Source device: ME
Destination device: SIM
Language
Language ‘de’🡪64 65 (German)
Coding:
|
BER-TLV: |
D6 |
0B |
19 |
01 |
07 |
82 |
02 |
82 |
81 |
2D |
02 |
64 |
|
65 |
27.22.7.8.1.5 Test requirement
The ME shall operate in the manner defined in expected sequence 1.1.
27.22.7.9 Browser termination event
27.22.7.9.1 Browser termination (normal)
27.22.7.9.1.1 Definition and applicability
This test is only applicable to ME’s that support the EVENT: browser termination event driven information.
27.22.7.9.1.2 Conformance requirement
The ME shall support the EVENT: Browser termination event as defined in:
– TS 11.14 [15] clause 4.7, clause 5.2, clause 6.4.16, clause 6.8, clause 11, clause 11.9, clause 12.25, clause 12.51, annex G and clause 12.7.
27.22.7.9.1.3 Test purpose
To verify that the ME informs the SIM of an Event: Browser termination using the ENVELOPE (EVENT DOWNLOAD – Browser Termination) command.
This test applies for MEs which have a browser.
27.22.7.9.1.4 Method of test
27.22.7.9.1.4.1 Initial conditions
The ME is connected to the SIM Simulator and the System Simulator.
The ME shall be powered on and perform the PROFILE DOWNLOAD procedure.
A valid access to a Wap gateway is required. The default browser parameters (IP address, gateway/proxy identity, called number…) of the tested mobile shall be properly filled to access that gateway.
The Bearer Parameters defined in 27.22.4.26.1.4.1 shall be used.
27.22.7.9.1.4.2 Procedure
Expected Sequence 1.1 (EVENT DOWNLOAD – Browser termination)
|
Step |
Direction |
Message / Action |
Comments |
|
1 |
SIM ME |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1 PENDING |
|
|
2 |
ME SIM |
FETCH |
|
|
3 |
SIM ME |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1 |
[EVENT: Browser termination Status] |
|
4 |
ME SIM |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1 |
[Successfully] |
|
5 |
UserME |
Launch the browser with URL selected by the user. |
|
|
6 |
MESS |
The ME attempts to launch the session with the default browser parameters and the URL selected by the user. |
|
|
7 |
UserME |
Stop the session and the browser. |
|
|
8 |
ME SIM |
ENVELOPE: BROWSER TERMINATION 1.1.1 |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: SIM
Destination device: ME
Event list
Event 1: Browser termination
Coding:
|
BER-TLV: |
D0 |
0C |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
81 |
82 |
|
99 |
01 |
08 |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
ENVELOPE: EVENT DOWNLOAD BROWSER TERMINATION 1.1.1
Logically:
Event list
Event 1: Browser termination
Device identities
Source device: ME
Destination device: SIM
Browser termination cause: User termination
Coding:
|
BER-TLV: |
D6 |
0A |
99 |
01 |
08 |
82 |
02 |
82 |
81 |
B4 |
01 |
00 |
27.22.7.9.1.5 Test requirement
The ME shall operate in the manner defined in expected sequence 1.1.
27.22.7.10 Data available event
27.22.7.10.1 Definition and applicability
See clause 3.2.2.
27.22.7.10.2 Conformance requirements
The ME shall support the class "e" commands as defined in:
– TS 11.14 [15].
Additionally the ME shall support ENVELOPE (EVENT DOWNLOAD – Data available).
27.22.7.10.3 Test purpose
To verify that the ME shall send an ENVELOPE (EVENT DOWNLOAD – Data available) to the SIM after the ME receives a packet of data from the server by the BIP channel previously opened.
27.22.7.10.4 Method of test
27.22.7.10.4.1 Initial conditions
The ME is connected to the SIM Simulator and only connected to the System Simulator if the System Simulator is mentioned in the sequence table.
Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure. The SIM must have sent the SET UP EVENT LIST to the ME to supply a set of events (event Data available).
For MEs supporting BIP related to GPRS in UDP (i.e condition C121 in table B.1), The PROACTIVE COMMAND: OPEN CHANNEL 1.1.1 shall be executed to open a channel successfully at the beginning of the test. The corresponding Terminal Response shall be TERMINAL RESPONSE: OPEN CHANNEL 1.1.1A or TERMINAL RESPONSE: OPEN CHANNEL 1.1.1B.
The PROACTIVE COMMAND: SEND DATA 1.1.1 shall be performed successfully to detect the ME’s port number, which has to be addressed by the network simulator when data has to be transmitted to the card. The corresponding Terminal Response shall be TERMINAL RESPONSE: SEND DATA 1.1.1.
The channel identifier value used for these tests is set to 1 as an example.
This channel identifier is dependent on the ME’s default channel identifier as declared in table A.2/6.
The following Bearer Parameters used are those defined in the default Test PDP context3, as specified in TS 51.010-1 [12], for test cases using packet services:
Bearer Parameters: Same Bearer Parameters as defined in 27.22.4.27.2.4.1
GPRS Parameters: Same GPRS Parameters as defined in 27.22.4.27.2.4.1
SIM/ME interface transport level: Same SIM/ME transport interface level as defined in 27.22.4.27.2.4.1
Data destination address : Same Data Destination Address as defined in 27.22.4.27.2.4.1.
27.22.7.10.4.2 Procedure
Expected sequence 1.1 (EVENT DOWNLOAD – Data available)
|
Step |
Direction |
MESSAGE / Action |
Comments |
|
1 |
SIM → ME |
PROACTIVE COMMAND PENDING: OPEN CHANNEL 1.1.1 |
See initial conditions |
|
2 |
ME → SIM |
FETCH |
|
|
3 |
SIM → ME |
PROACTIVE COMMAND: OPEN CHANNEL 1.1.1 |
[Command performed successfully] |
|
4 |
ME → USER |
The ME may display channel opening information |
|
|
5 |
ME → SS |
PDP context activation request |
|
|
6 |
SS → ME |
PDP context activation accept |
|
|
7 |
ME → SIM |
TERMINAL RESPONSE: OPEN CHANNEL 1.1.1A or TERMINAL RESPONSE: OPEN CHANNEL 1.1.1B |
|
|
8 |
SIM → ME |
PROACTIVE COMMAND PENDING: SEND DATA 1.1.1 |
|
|
9 |
ME → SIM |
FETCH |
|
|
10 |
SIM → ME |
PROACTIVE COMMAND: SEND DATA (immediate) 1.1.1 |
|
|
11 |
ME → SS |
Transfer of 8 Bytes of data to the SS through channel 1 |
[To retrieve ME’s port number] |
|
12 |
ME → SIM |
TERMINAL RESPONSE: SEND DATA (immediate) 1.1.1 |
[Command performed successfully] |
|
13 |
SS → ME |
Data sent through the BIP channel using the ME’s port number, which was retrieved in step 11 |
|
|
14 |
ME → SIM |
ENVELOPE 1.1.1 (Event-Data Available) |
PROACTIVE COMMAND: OPEN CHANNEL 1.1.1
Logically:
Command details
Command number: 1
Command type: OPEN CHANNEL
Command qualifier: immediate link establishment
Device identities
Source device: SIM
Destination device: ME
Bearer
Bearer type: GPRS
Bearer parameter:
Precedence Class: 02
Delay Class: 04
Reliability Class: 05
Peak throughput class: 05
Mean throughput class: 31
Packet data protocol: 02 (IP)
Buffer
Buffer size: 1000
Network access name: TestGp.rs
Text String: UserLog (User login)
Text String: UserPwd (User password)
SIM/ME interface transport level
Transport format: UDP
Port number: 44444
Data destination address 01.01.01.01
Coding:
|
BER-TLV |
D0 |
42 |
81 |
03 |
01 |
40 |
01 |
82 |
02 |
81 |
82 |
35 |
|
07 |
02 |
02 |
04 |
05 |
05 |
1F |
02 |
39 |
02 |
03 |
E8 |
|
|
47 |
0A |
06 |
54 |
65 |
73 |
74 |
47 |
70 |
02 |
72 |
73 |
|
|
0D |
08 |
F4 |
55 |
73 |
65 |
72 |
4C |
6F |
67 |
0D |
08 |
|
|
F4 |
55 |
73 |
65 |
72 |
50 |
77 |
64 |
3C |
03 |
01 |
AD |
|
|
9C |
3E |
05 |
21 |
01 |
01 |
01 |
01 |
TERMINAL RESPONSE: OPEN CHANNEL 1.1.1A
Logically:
Command details
Command number: 1
Command type: OPEN CHANNEL
Command qualifier: immediate link establishment
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Channel status Channel identifier 1 and link established or PDP context activated
Bearer description
Bearer type: GPRS
Bearer parameter:
Precedence Class: 02
Delay Class: 04
Reliability Class: 05
Peak throughput class: 05
Mean throughput class: 31
Packet data protocol: 02 (IP)
Buffer
Buffer size: 1000
Coding:
|
BER-TLV: |
81 |
03 |
01 |
40 |
01 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
|
38 |
02 |
81 |
00 |
35 |
07 |
02 |
02 |
04 |
05 |
05 |
1F |
|
|
02 |
39 |
02 |
03 |
E8 |
TERMINAL RESPONSE: OPEN CHANNEL 1.1.1B
Logically:
Command details
Command number: 1
Command type: OPEN CHANNEL
Command qualifier: immediate link establishment
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Channel status Channel identifier 1 and link established or PDP context activated
Bearer description
Bearer type: GPRS
Bearer parameter:
Precedence Class: 00
Delay Class: 04
Reliability Class: 05
Peak throughput class: 05
Mean throughput class: 31
Packet data protocol: 02 (IP)
Buffer
Buffer size: 1000
Coding:
|
BER-TLV: |
81 |
03 |
01 |
40 |
01 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
|
38 |
02 |
81 |
00 |
35 |
07 |
02 |
00 |
04 |
05 |
05 |
1F |
|
|
02 |
39 |
02 |
03 |
E8 |
PROACTIVE COMMAND: SEND DATA 1.1.1
Logically:
Command details
Command number: 1
Command type: SEND DATA
Command qualifier: Send Immediately
Device identities
Source device: SIM
Destination device: Channel 1
Channel Data
Channel Data: 00 01 .. 07 (8 Bytes of data)
Coding:
|
BER-TLV: |
D0 |
13 |
81 |
03 |
01 |
43 |
01 |
82 |
02 |
81 |
21 |
B6 |
|
08 |
00 |
01 |
02 |
03 |
04 |
05 |
06 |
07 |
TERMINAL RESPONSE: SEND DATA 1.1.1
Logically:
Command details
Command number: 1
Command type: SEND DATA
Command qualifier: Send Immediately
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Channel data length: More than 255 bytes of space available in the Tx buffer
Coding:
|
BER-TLV: |
81 |
03 |
01 |
43 |
01 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
|
B7 |
01 |
FF |
ENVELOPE: EVENT DOWNLOAD – Data available 1.1.1
Logically:
Event list
Event: Data available
Device identities
Source device: ME
Destination device: SIM
Channel status
Channel status: Channel 1 open, link established
Channel Data Length
Channel data length: 8 Bytes available in Rx buffer
Coding:
|
BER-TLV: |
D6 |
0E |
99 |
01 |
09 |
82 |
02 |
82 |
81 |
B8 |
02 |
81 |
|
00 |
B7 |
01 |
08 |
27.22.7.10.1.5 Test requirement
The ME shall operate in the manner defined in expected sequence 1.1.
27.22.7.11 Channel Status event
27.22.7.11.1 Definition and applicability
See clause 3.2.2.
27.22.7.11.2 Conformance requirements
The ME shall support the class "e" commands as defined in:
– TS 11.14 [15].
Additionally the ME shall support ENVELOPE (EVENT DOWNLOAD – Channel Status).
27.22.7.11.3 Test purpose
To verify that the ME shall send an ENVELOPE (EVENT DOWNLOAD – Channel Status) to the SIM after the link dropped between the NETWORK and the ME.
27.22.7.11.4 Method of test
27.22.7.11.4.1 Initial conditions
The ME is connected to the SIM Simulator and the System Simulator. The elementary files are coded as Toolkit default.
Prior to this test the ME shall have been powered on and performed the PROFILE DOWNLOAD procedure.
For MEs supporting BIP related to GPRS in UDP (i.e condition C121 in table B.1), The PROACTIVE COMMAND: OPEN CHANNEL 1.1.1 shall be executed to open a channel successfully at the beginning of the test. The corresponding Terminal Response shall be TERMINAL RESPONSE: OPEN CHANNEL 1.1.1A or TERMINAL RESPONSE: OPEN CHANNEL 1.1.1B.
The channel identifier value used for these tests is set to 1 as an example.
This channel identifier is dependent on the ME’s default channel identifier as declared in table A.2/6.
The following Bearer Parameters used are those defined in the default Test PDP context3, as specified in TS 51.010-1 [12], for test cases using packet services:
Bearer Parameters: Same Bearer Parameters as defined in 27.22.4.27.2.4.1
GPRS Parameters: Same GPRS Parameters as defined in 27.22.4.27.2.4.1
SIM/ME interface transport level: Same SIM/ME transport interface level as defined in 27.22.4.27.2.4.1
Data destination address : Same Data Destination Address as defined in 27.22.4.27.2.4.1.
27.22.7.11.4.2 Procedure
Expected sequence 1.1 (EVENT DOWNLOAD – Channel Status on a link dropped)
|
Step |
Direction |
MESSAGE / Action |
Comments |
|
1 |
SIM → ME |
PROACTIVE COMMAND PENDING: SET UP EVENT LIST 1.1.1 |
|
|
2 |
ME SIM |
FETCH |
|
|
3 |
SIM ME |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1 |
[EVENT: channel status] |
|
4 |
ME → SIM |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1 |
[command performed successfully] |
|
5 |
SIM → ME |
PROACTIVE COMMAND PENDING: OPEN CHANNEL 1.1.1 |
See initial conditions |
|
6 |
ME → SIM |
FETCH |
|
|
7 |
SIM → ME |
PROACTIVE COMMAND: OPEN CHANNEL 1.1.1 |
|
|
8 |
ME → USER |
The ME may display channel opening information |
|
|
9 |
ME → SS |
PDP context activation request |
|
|
10 |
SS → ME |
PDP context activation accept |
|
|
11 |
ME → SIM |
TERMINAL RESPONSE: OPEN CHANNEL 1.1.1A or TERMINAL RESPONSE: OPEN CHANNEL 1.1.1B |
[Command performed successfully] |
|
12 |
SS → ME |
Link dropped |
|
|
13 |
ME → SIM |
ENVELOPE 1.1.1 (Event-Channel Status) |
PROACTIVE COMMAND: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: SIM
Destination device: ME
Event list
Event 1: Channel Status
Coding:
|
BER-TLV: |
D0 |
0C |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
81 |
82 |
|
99 |
01 |
0A |
TERMINAL RESPONSE: SET UP EVENT LIST 1.1.1
Logically:
Command details
Command number: 1
Command type: SET UP EVENT LIST
Command qualifier: ’00’
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Coding:
|
BER-TLV: |
81 |
03 |
01 |
05 |
00 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
PROACTIVE COMMAND: OPEN CHANNEL 1.1.1
Logically:
Command details
Command number: 1
Command type: OPEN CHANNEL
Command qualifier: immediate link establishment
Device identities
Source device: SIM
Destination device: ME
Bearer
Bearer type: GPRS
Bearer parameter:
Precedence Class: 02
Delay Class: 04
Reliability Class: 05
Peak throughput class: 05
Mean throughput class: 31
Packet data protocol: 02 (IP)
Buffer
Buffer size: 1000
Network access name: TestGp.rs
Text String: UserLog (User login)
Text String: UserPwd (User password)
SIM/ME interface transport level
Transport format: UDP
Port number: 44444
Data destination address 01.01.01.01
Coding:
|
BER-TLV |
D0 |
42 |
81 |
03 |
01 |
40 |
01 |
82 |
02 |
81 |
82 |
35 |
|
07 |
02 |
02 |
04 |
05 |
05 |
1F |
02 |
39 |
02 |
03 |
E8 |
|
|
47 |
0A |
06 |
54 |
65 |
73 |
74 |
47 |
70 |
02 |
72 |
73 |
|
|
0D |
08 |
F4 |
55 |
73 |
65 |
72 |
4C |
6F |
67 |
0D |
08 |
|
|
F4 |
55 |
73 |
65 |
72 |
50 |
77 |
64 |
3C |
03 |
01 |
AD |
|
|
9C |
3E |
05 |
21 |
01 |
01 |
01 |
01 |
TERMINAL RESPONSE: OPEN CHANNEL 1.1.1A
Logically:
Command details
Command number: 1
Command type: OPEN CHANNEL
Command qualifier: immediate link establishment
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Channel status Channel identifier 1 and link established or PDP context activated
Bearer description
Bearer type: GPRS
Bearer parameter:
Precedence Class: 02
Delay Class: 04
Reliability Class: 05
Peak throughput class: 05
Mean throughput class: 31
Packet data protocol: 02 (IP)
Buffer
Buffer size: 1000
Coding:
|
BER-TLV: |
81 |
03 |
01 |
40 |
01 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
|
38 |
02 |
81 |
00 |
35 |
07 |
02 |
02 |
04 |
05 |
05 |
1F |
|
|
02 |
39 |
02 |
03 |
E8 |
TERMINAL RESPONSE: OPEN CHANNEL 1.1.1B
Logically:
Command details
Command number: 1
Command type: OPEN CHANNEL
Command qualifier: immediate link establishment
Device identities
Source device: ME
Destination device: SIM
Result
General Result: Command performed successfully
Channel status Channel identifier 1 and link established or PDP context activated
Bearer description
Bearer type: GPRS
Bearer parameter:
Precedence Class: 00
Delay Class: 04
Reliability Class: 05
Peak throughput class: 05
Mean throughput class: 31
Packet data protocol: 02 (IP)
Buffer
Buffer size: 1000
Coding:
|
BER-TLV: |
81 |
03 |
01 |
40 |
01 |
82 |
02 |
82 |
81 |
83 |
01 |
00 |
|
38 |
02 |
81 |
00 |
35 |
07 |
02 |
00 |
04 |
05 |
05 |
1F |
|
|
02 |
39 |
02 |
03 |
E8 |
ENVELOPE: EVENT DOWNLOAD – Channel Status 1.1.1
Logically:
Event list
Event: Channel Status
Device identities
Source device: ME
Destination device: SIM
Channel status
Channel status: Channel 1, link dropped
Coding:
|
BER-TLV: |
D6 |
0B |
99 |
01 |
0A |
82 |
02 |
82 |
81 |
B8 |
02 |
01 |
|
05 |
27.22.7.11.1.5 Test requirement
The ME shall operate in the manner defined in expected sequence 1.1.