8 Subscription independent tests
31.1213GPPRelease 16TSUICC-terminal interfaceUniversal Subscriber Identity Module (USIM) application test specification
8.1 Phone book procedures
8.1.1 Recognition of a previously changed phonebook
8.1.1.1 Definition and applicability
If the UICC is inserted into a GERAN Rel-4 or earlier terminal, the phonebook may have been altered in this GSM session. If the ADN entry has been changed or deleted, the GSM terminal will not be able to change the appropriate additional phonebook entries (e.g. EFANR Additional Number). In that case the UICC shall set a flag in the appropriate EFPBC (phonebook Control). If the UICC is inserted in a 3G or GERAN Terminal, the 3G or GERAN Terminal shall recognise the flag and the phonebook shall be synchronised by the Terminal. Once the Terminal recognise the set flag in the EFPBC, the Terminal shall update the Change Counter in the EFCC.
8.1.1.2 Conformance requirement
The 3G or GERAN Terminal shall recognise the set flag in the EFPBC and then synchronise the phonebook. The Terminal shall also update EFCC (Change Counter).
– TS 31.102 [4], clause 4.4.2.
8.1.1.3 Test purpose
1) To verify that the Terminal has recognised that the phonebook has been altered by a GSM Terminal.
2) To verify that the Terminal does the synchronising of the changed phonebook entries.
3) To verify that the Terminal updates the EFPBC and EFCC.
8.1.1.4 Method of test
8.1.1.4.1 Initial conditions
No USS is needed for this test.
The default UICC is used with the following exception:
EFADN (Abbreviated Dialling Number)
Logically:
Record 1: Length of alpha identifier: 32 characters;
Alpha identifier: "ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEF";
Length of BCD number: "03";
TON and NPI: Telephony and Unknown;
Dialled number: 123;
CCI: None;
Ext1: None.
Record 1:
|
Coding: |
B1 |
B2 |
B3 |
… |
B32 |
B33 |
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
… |
B46 |
|
Hex |
41 |
42 |
43 |
… |
46 |
03 |
81 |
21 |
F3 |
FF |
FF |
FF |
… |
FF |
EFPBC (Phonebook Control)
Logically:
Record 1: The ADN Record No. 1 has been hanged by a GSM terminal.
Related ADN record is not hidden.
|
Coding: |
B1 |
B2 |
|
Hex |
01 |
00 |
EFCC (Change Counter)
Logically: "000F"
|
Coding: |
B1 |
B2 |
|
Hex |
00 |
0F |
The UICC is installed into the Terminal
8.1.1.4.2 Procedure
a) The Terminal is powered on.
b) The Terminal shall stay powered on until the phonebook synchronisation procedures are finished. If the synchronisation is indicated by the Terminal, the Terminal shall only powered down after this indication is vanished.
8.1.1.5 Acceptance criteria
After step b) the USIM shall contain the following values:
EFPBC (Phonebook Control)
Logically:
Record 1: The entry control information is reset.
Related ADN record is not hidden.
|
Coding: |
B1 |
B2 |
|
Hex |
00 |
00 |
EFCC (Change Counter)
Logically: The counter is incremented to "0010"
|
Coding: |
B1 |
B2 |
|
Hex |
00 |
10 |
8.1.2 Update of the Phonebook Synchronisation Counter (PSC)
8.1.2.1 Definition and applicability
The phonebook synchronisation Counter is used to unambiguously identify the status of the phonebook. Every time the phonebook is reset/deleted or the UID and/or the CC has run out of range, the PSC shall be regenerated.
The PSC is a part of the phonebook identifier.
8.1.2.2 Conformance requirement
Every time either the UID or the CC is incremented by the Terminal, the value of the contend of the appropriate EF shall be tested. If either UID or CC has reached "FF FF", the related EF shall be set to "00 01" and the PSC is incremented.
– TS 31.102 [4], clause 4.4.2.12.2.
8.1.2.3 Test purpose
1) To verify that the Terminal has recognised that the values of UID and CC has changed.
2) To verify that the Terminal resets the value of EFUID and EFCC.
3) To verify that the Terminal updates EFPSC.
8.1.2.4 Method of test
8.1.2.4.1 Initial conditions
No USS is needed for this test.
The default UICC is used with the following exception:
EFUID (Unique Identifier)
Logically: one record is set to "FF FF"
|
Coding: |
B1 |
B2 |
|
Hex |
FF |
FF |
EFPUID (Previous Unique Identifier)
Logically: is set to "FF FF"
|
Coding: |
B1 |
B2 |
|
Hex |
FF |
FF |
EFCC (Change Counter)
Logically: set to "FF FF"
|
Coding: |
B1 |
B2 |
|
Hex |
FF |
FF |
EFPSC (Phonebook Synchronisation Counter)
Logically: set to "00 00 FF FF"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
|
Hex |
00 |
00 |
FF |
FF |
At least one phonebook entry shall be empty and available for creating a new entry (e.g. an appropriate ADN record).
The UICC is installed into the Terminal and the UE is powered on and the correct PIN is entered.
8.1.2.4.2 Procedure
a) A new phonebook entry shall be created.
NOTE 1: This may be done by storing a new telephone number in an empty ADN record.
b) The UE shall have given the time to perform the regeneration of the UID records.
NOTE 2: It is assumed that the UE will indicate the time it needs to perform the regeneration by displaying a busy signal to the user.
8.1.2.5 Acceptance criteria
After step b) the USIM shall contain the following values:
The EFUID (Unique Identifier) shall have been regenerated with UID values starting with "00 01". The UID values may be stored in any order, but shall be unique. The entry in EFUID with value FF FF (the maximum value) shall have been replaced by an appropriate value which shall be distinguishable to the maximum value. EFPUID shall contain a UID value (other than FFFF) that is present in EFUID.
EFCC (Change Counter)
Logically: set to "00 01"
|
Coding: |
B1 |
B2 |
|
Hex |
00 |
01 |
EFPSC (Phonebook Synchronisation Counter)
Logically: set to "00 01 00 00"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
|
Hex |
00 |
01 |
00 |
00 |
8.1.3 Phonebook content handling
8.1.3.1 Handling of BCD number/ SSC content extension
8.1.3.1.1 Definition and applicability
The length of BCD number/SSC contents in EFADN byte gives the number of bytes of the following two data items containing actual BCD number/SSC information. This means that the maximum value is 11, even when the actual ADN/SSC information length is greater than 11. When an ADN/SSC has extension, it is indicated by the extension1 identifier being unequal to ‘FF’. The remainder is stored in the EFEXT1 with the remaining length of the additional data being coded in the appropriate additional record itself.
8.1.3.1.2 Conformance requirement
The terminal shall support the BCD number/ SSC extension for EFADN as defined in TS 31.102 [4], clauses 4.4.2.3 and 4.4.2.4.
Reference:
– TS 31.102 [4], clauses 4.4.2.3 and 4.4.2.4.
8.1.3.1.3 Test purpose
1) To verify that the terminal is able to read and update BCD numbers/ SSC content with and without extension correctly in EFADN and EFEXT1.
8.1.3.1.4 Method of test
8.1.3.1.4.1 Initial conditions
The terminal is connected to the USIM Simulator.
Prior to the test execution the terminal manufacturer shall state the maximum number of BCD digits (excluding TON/NPI), which are supported by the terminal for global phonebook updating.
The default USIM is used with the following exceptions:
Only the global phonebook is present.
The global phonebook shall contain:
EFPBR (Phonebook reference file)
Logically: Only EFADN and EFEXT1 are present in the global phonebook.
EFADN (Abbreviated dialling numbers)
Logically:
10 records, each record non-empty and unique. Unless otherwise stated, the ADN records shall not use extended BCD numbers/SSC strings.
Record 1: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact001";
Length of BCD number: 11;
TON and NPI: Telephony and International;
Dialled number: "00112233445566778899";
CCI: ‘FF’;
Ext1: 01.
Record 1:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
31 |
FF |
… |
FF |
0B |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
B40 |
B41 |
B42 |
B43 |
B44 |
B45 |
B46 |
||
|
91 |
00 |
11 |
22 |
33 |
44 |
55 |
66 |
77 |
88 |
99 |
FF |
01 |
Record 2: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact002";
Length of BCD number: 11;
TON and NPI: Telephony and International;
Dialled number: "01234567890123456789";
CCI: ‘FF’;
Ext1: ‘FF’.
Record 2:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
32 |
FF |
… |
FF |
0B |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
B40 |
B41 |
B42 |
B43 |
B44 |
B45 |
B46 |
||
|
91 |
10 |
32 |
54 |
76 |
98 |
10 |
32 |
54 |
76 |
98 |
FF |
FF |
Record 3: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact003";
Length of BCD number: 11;
TON and NPI: Telephony and International;
Dialled number: "99887766554433221100";
CCI: ‘FF’;
Ext1: ’02’.
Record 3:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
33 |
FF |
… |
FF |
0B |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
B40 |
B41 |
B42 |
B43 |
B44 |
B45 |
B46 |
||
|
91 |
99 |
88 |
77 |
66 |
55 |
44 |
33 |
22 |
11 |
00 |
FF |
02 |
Record 4: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact004";
Length of BCD number: 9;
TON and NPI: Telephony and International;
Dialled number: "1212121212121212";
CCI: ‘FF’;
Ext1: ‘FF’.
Record 4:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
34 |
FF |
… |
FF |
09 |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
B40 |
B41 |
B42 |
B43 |
B44 |
B45 |
B46 |
||
|
91 |
21 |
21 |
21 |
21 |
21 |
21 |
21 |
21 |
FF |
FF |
FF |
FF |
Record 7: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact007";
Length of BCD number: 3;
TON and NPI: Telephony and International;
Dialled number: "678";
CCI: ‘FF’;
Ext1: ‘FF’.
Record 7:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
37 |
FF |
… |
FF |
03 |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
B40 |
B41 |
B42 |
B43 |
B44 |
B45 |
B46 |
||
|
91 |
76 |
F8 |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
EFEXT1 (Extension 1)
Logically: 4 records
Record 1: Record type: ’02’
Extension data: "01234567890123456789";
Identifier: ‘FF’.
Record 1:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
B13 |
|
|
Hex |
02 |
0A |
10 |
32 |
54 |
76 |
98 |
10 |
32 |
54 |
76 |
98 |
FF |
Record 2: Record type: ’02’
Extension data: "99887766554433221100";
Identifier: ’03’.
Record 2:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
B13 |
|
|
Hex |
02 |
0A |
99 |
88 |
77 |
66 |
55 |
44 |
33 |
22 |
11 |
00 |
03 |
Record 3: Record type: ’02’
Extension data: "11p12345";
Identifier: ‘FF’.
Record 3:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
B13 |
|
|
Hex |
02 |
04 |
11 |
1C |
32 |
54 |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
Record 4: Record type: ’00’
Extension data: empty;
Identifier: ‘FF’.
Record 4:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
B13 |
|
|
Hex |
00 |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
8.1.3.1.4.2 Procedure
a) The terminal is switched on and the USIM application shall be activated.
b) The user shall use an MMI dependent procedure to select the global phonebook.
c) The user shall change the BCD number of the entry "Contact002" to "22446622446622446600777888999". If the maximum number of BCD digits supported for the global phonebook update is less than in the requested input BCD number string, then the user shall enter the BCD number string as requested, but only up to the maximum number of BCD digits which are supported for updating.
d) The user shall extend the BCD number of the entry "Contact007" to "01234567890123456789777888999".. If the maximum number of BCD digits supported for the global phonebook update is less than in the requested input BCD number string, then the user shall enter the BCD number string as requested, but only up to the maximum number of BCD digits which are supported for updating.
e) The user shall delete the phonebook entry "Contact001".
f) The user shall set the BCD number of the entry "Contact002" to "22446622446600"
g) The user shall create the new phonebook entry "NewContact" with the BCD number "1234567890123456789012345678901234567890123456789012".. If the maximum number of BCD digits supported for the global phonebook update is less than in the requested input BCD number string, then the user shall enter the BCD number string as requested, but only up to the maximum number of BCD digits which are supported for updating.
h) The user shall delete the phonebook entry "Contact003".
i) The terminal is switched off.
8.1.3.1.5 Acceptance criteria
1) After step a) the terminal shall have activated the USIM application.
2) After step b) the terminal shall have selected the global phonebook and shall have read EFPBR in the global phonebook.
3) After step c) the global phonebook shall contain a record with "22446622446622446600" as BCD number and "04" as extension record identifier. EFEXT1 shall contain a record with "Additional data" as record type, the BCD number extension "777888999" and "FF" as identifier to indicate the end of the chain. If the maximum number of BCD digits supported for global phonebook updating is less than in the requested input BCD number, then EFADN and EFEXT1 shall contain the BCD number as entered on the MMI.
4) After step d) the terminal shall have taken action to prevent storage of the extended BCD number, e.g. by giving an indication to the user or not allowing to enter the extended number. EFEXT1 shall have not been updated and the extension record identifier of the entry "Contact007"shall remain as "FF".
5) After step e) records of EFADN and EFEXT1 which were used to store the data for the phonebook entry "Contact001" shall be empty, i.e. the EFADN record shall be "FF… FF" and the EFEXT1 record shall be "00FF… FF."
6) After step f) the record of EFEXT1 which was used to store the BCD number extension "777888999" shall be empty and the record used for storing the entry with the alpha identifier "Contact002" of EFADN shall contain the BCD number "22446622446600" and the extension record identifier "FF".
7) After step g) a record of EFADN shall contain "NewContact" as alpha identifier, "12345678901234567890" as BCD number and shall use an extension record identifier unequal to "FF".
The EFEXT1 record which was indicated in the EFADN record used in this case shall contain "Additional data" as record type, "12345678901234567890" as BCD number and an extension record identifier unequal to "FF", while the EFEXT1 record used to continue the chain inside EFEXT1 shall contain "Additional data" as record type, "123456789012" as BCD number and "FF" as extension record identifier.
If the maximum number of BCD digits supported for global phonebook updating is less than the requested input BCD number, then EFADN and EFEXT1 shall contain the BCD number as entered on the MMI.
8) After step h) the record of EFADN which was used to store the data for "Contact003" and the related records of EFEXT1 shall be empty.
8.1.4 Phonebook selection
8.1.4.1 Definition and applicability
The UICC may contain a global phonebook, or application specific phonebooks, or both in parallel. When both phonebook types co-exist, they are independent and no data is shared. In this case, it shall be possible for the user to select which phonebook the user would like to access.
8.1.4.2 Conformance requirement
The terminal shall support the global and the application specific phonebooks as defined in TS 31.102 [4], clause 4.4.2.
Reference:
– TS 31.102 [4], clause 4.4.2.
8.1.4.3 Test purpose
1) To verify that the terminal offers a possibility to select which phonebook the user would like to select if both, the global and the local phonebook, co-exist.
2) To verify that the data contained in the local phonebook can be read and updated correctly.
3) To verify that the data contained in the global phonebook can be read and updated correctly.
8.1.4.4 Method of test
8.1.4.4.1 Initial conditions
The terminal is connected to the USIM Simulator.
The default USIM is used with the following exceptions:
The local and the global phonebook are both present.
The local phonebook shall contain:
EFPBR (Phonebook reference file)
Logically: Only EFADN and EFEXT1 are present in the local phonebook.
EFADN (Abbreviated dialling numbers)
Logically: 10 records, each record non-empty and unique.
Record 4: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact004";
Length of BCD number: "03";
TON and NPI: Telephony and International;
Dialled number: 004;
CCI: ‘FF’;
Ext1: ‘FF’.
Record 4:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
34 |
FF |
… |
FF |
03 |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
… |
B46 |
|||||||
|
91 |
00 |
F4 |
FF |
FF |
FF |
… |
FF |
Record 5: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact005";
Length of BCD number: "03";
TON and NPI: Telephony and International;
Dialled number: 1234;
CCI: ‘FF’;
Ext1: None.
Record 5:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
35 |
FF |
… |
FF |
03 |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
… |
B46 |
|||||||
|
91 |
21 |
43 |
FF |
FF |
FF |
… |
FF |
The global phonebook shall contain:
EFPBR (Phonebook reference file)
Logically: Only EFADN is present in the global phonebook.
EFADN (Abbreviated dialling numbers)
Logically: 8 records, records 3 and 6 empty, each non-empty record unique.
Record 1: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact001";
Length of BCD number: "03";
TON and NPI: Telephony and International;
Dialled number: 001;
CCI: ‘FF’;
Ext1: ‘FF’.
Record 1:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
31 |
FF |
… |
FF |
03 |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
… |
B46 |
|||||||
|
91 |
00 |
F1 |
FF |
FF |
FF |
… |
FF |
Record 2: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact002";
Length of BCD number: "03";
TON and NPI: Telephony and International;
Dialled number: 002;
CCI: ‘FF’;
Ext1: ‘FF’.
Record 2:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
32 |
FF |
… |
FF |
03 |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
… |
B46 |
|||||||
|
91 |
00 |
F2 |
FF |
FF |
FF |
… |
FF |
Record 4: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact004";
Length of BCD number: "03";
TON and NPI: Telephony and International;
Dialled number: 0041;
CCI: ‘FF’;
Ext1: ‘FF’.
Record 4:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
34 |
FF |
… |
FF |
03 |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
… |
B46 |
|||||||
|
91 |
00 |
14 |
FF |
FF |
FF |
… |
FF |
Record 5: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact005";
Length of BCD number: "03";
TON and NPI: Telephony and International;
Dialled number: 1234;
CCI: ‘FF’;
Ext1: ‘FF’.
Record 5:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
35 |
FF |
… |
FF |
03 |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
… |
B46 |
|||||||
|
91 |
21 |
43 |
FF |
FF |
FF |
… |
FF |
Record 7: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact007";
Length of BCD number: "03";
TON and NPI: Telephony and International;
Dialled number: 007;
CCI: ‘FF’;
Ext1: ‘FF’.
Record 7:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
37 |
FF |
… |
FF |
03 |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
… |
B46 |
|||||||
|
91 |
00 |
F7 |
FF |
FF |
FF |
… |
FF |
Record 8: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact008";
Length of BCD number: "03";
TON and NPI: Telephony and International;
Dialled number: 008;
CCI: ‘FF’;
Ext1: ‘FF’.
Record 8:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
38 |
FF |
… |
FF |
03 |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
… |
B46 |
|||||||
|
91 |
00 |
F8 |
FF |
FF |
FF |
… |
FF |
8.1.4.4.2 Procedure
a) The terminal is switched on and the USIM application shall be activated.
b) The user shall use an MMI dependent procedure to select the global phonebook.
c) The global phonebook record with the alpha identifier "Contact005" and the associated dialling number shall be read by the user.
d) The dialling number of the global phonebook record with the alpha identifier "Contact005" shall be set to "+1122330".
e) A new entry with the values "Contact006" as alpha identifier and "+9876543210" as associated dialling number shall be added to the global phonebook.
f) The user shall use an MMI dependent procedure to select the local phonebook.
g) The local phonebook record with the alpha identifier "Contact005" and the associated dialling number shall be read by the user.
h) The dialling number of the local phonebook record with the alpha identifier "Contact005" shall be set to "+11223345".
i) The user shall try to add a new entry with the values "Contact007" as alpha identifier and "+007" as associated dialling number to the local phonebook.
j) The user shall delete the entry "Contact004" from the local phonebook.
k) The user shall add a new entry with the values "Contact007" as alpha identifier and "+007" as associated dialling number to the local phonebook.
l) The user shall use an MMI dependent procedure to select the global phonebook.
m) The user shall delete the entry "Contact007" from the global phonebook.
n) The terminal is switched off.
8.1.4.5 Acceptance criteria
1) After step a) the terminal shall have activated the USIM application, shall have read the status of the local Phonebook in EFUST.
2) After step b) the terminal shall have selected the global phonebook and shall have read EFPBR in the global phonebook.
3) After step c) the terminal shall have read the global phonebook record which is used to store the enrty "Contact005" and shall have presented the alpha identifier "Contact005" and the dialling number "+1234" to the user.
4) After step d) EFADN in the global phonebook shall contain a record with the alpha identifier "Contact005" with the new dialling number "+1122330" and the terminal shall have given an indication to the user that the phonebook update has been performed successfully.
5) After step e) a new record shall have been added to EFADN in the global phonebook with the alpha identifier "Contact006" and the dialling number string "+9876543210".
6) After step f) the terminal shall have selected the local phonebook and shall have read EFPBR in the local phonebook.
7) After step g) the terminal shall have read the local phonebook record which is used to store the entry "Contact005" and shall have presented the alpha identifier "Contact005" and the dialling number "+1234" to the user.
8) After step h) EFADN in the local phonebook shall contain a record with the alpha identifier "Conatct005" and with new dialling number "+11223345" and the terminal shall have given an indication to the user that the phonebook update has been performed successfully.
9) After step i) the terminal shall have given an indication that update of the local phonebook can’t be performed. EFADN shall have not been updated.
10) After step j) the local phonebook record which was used to store the entry "Contact004" shall be empty and the terminal shall have indicated that the deletion of the phonebook entry was performed successfully.
11) After step k) a new record shall have been added to EFADN in the local phonebook with the alpha identifier "Contact007" and the dialling number string "+007"
12) After step l) the terminal shall have selected the global phonebook and shall have read EFPBR in the global phonebook.
13) After step m) the global phonebook record which was used to store the entry "Contact007" shall be empty and the terminal shall have indicated that the deletion of the phonebook entry was performed successfully.
8.1.5 Local Phonebook handling
8.1.5.1 Definition and applicability
The UICC may contain a global phonebook, or application specific phonebooks, or both in parallel.
8.1.5.2 Conformance requirement
The terminal shall support the local phonebook as defined in TS 31.102 [4], clause 4.4.2.
Reference:
– TS 31.102 [4], clause 4.4.2.
8.1.5.3 Test purpose
1) To verify that the terminal supports the local phonebook without existence of the global phonebook.
2) To verify that the data contained in the local phonebook can be read and updated correctly.
8.1.5.4 Method of test
8.1.5.4.1 Initial conditions
The terminal is connected to the USIM Simulator.
The default USIM is used with the following exceptions:
The local phonebook is present, the global phonebook is not present.
The local phonebook shall contain:
EFPBR (Phonebook reference file)
Logically: Only EFADN and EFEXT1 are present in the local phonebook.
EFADN (Abbreviated dialling numbers)
Logically: 10 records, each record non-empty and unique.
Record 4: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact004";
Length of BCD number: "03";
TON and NPI: Telephony and International;
Dialled number: 004;
CCI: ‘FF’;
Ext1: ‘FF’.
Record 4:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
34 |
FF |
… |
FF |
03 |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
… |
B46 |
|||||||
|
91 |
00 |
F4 |
FF |
FF |
FF |
… |
FF |
Record 5: Length of alpha identifier: 32 characters;
Alpha identifier: "Contact005";
Length of BCD number: "03";
TON and NPI: Telephony and International;
Dialled number: 1234;
CCI: ‘FF’;
Ext1: ‘FF’.
Record 5:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
… |
B32 |
B33 |
|
Hex |
43 |
6F |
6E |
74 |
61 |
63 |
74 |
30 |
30 |
35 |
FF |
… |
FF |
03 |
|
B34 |
B35 |
B36 |
B37 |
B38 |
B39 |
… |
B46 |
|||||||
|
91 |
21 |
43 |
FF |
FF |
FF |
… |
FF |
8.1.5.4.2 Procedure
a) The terminal is switched on and the USIM application shall be activated.
b) The user shall use an MMI dependent procedure to select the phonebook on the USIM (local phonebook).
c) The local phonebook record with the alpha identifier "Contact005" and the associated dialling number shall be read by the user.
d) The dialling number of the local phonebook record with the alpha identifier "Contact005" shall be set to "+11223345" and the alpha identifier shall be changed to "Contact8901234567890123456789012".
e) The user shall try to add a new entry with the values "Contact007" as alpha identifier and "+007" as associated dialling number to the local phonebook.
f) The user shall delete the entry "Contact004" from the local phonebook.
g) The user shall add a new entry with the values "Contact007" as alpha identifier and "+007" as associated dialling number to the local phonebook.
h) The terminal is switched off.
8.1.5.5 Acceptance criteria
1) After step a) the terminal shall have activated the USIM application, shall have read the status of the local Phonebook in EFUST.
2) After step b) the terminal shall have selected the local phonebook and shall have read EFPBR in the local phonebook.
3) After step c) the terminal shall have read the local phonebook record which is used to store the entry "Contact005" and shall have presented the alpha identifier "Contact005" and the dialling number "+1234" to the user.
4) After step d) EFADN in the local phonebook shall contain a record with the new alpha identifier "Contact8901234567890123456789012" and the dialling number "+11223345" and the terminal shall have given an indication to the user that the phonebook update has been performed successfully.
5) After step e) the terminal shall have given an indication that update of the local phonebook can’t be performed. EFADN shall have not been updated.
6) After step f) the local phonebook record which was used to store the entry "Contact004" in the local phonebook shall be empty and the terminal shall have indicated that the deletion of the phonebook entry was performed successfully.
7) After step g) a new record shall have been added to EFADN in the local phonebook with the alpha identifier "Contact007" and the dialling number string "+007"
8.2 Short message handling report
8.2.1 Correct storage of a SM on the USIM
8.2.1.1 Definition and applicability
Once a SMS is received by the UE, the Terminal shall store the SM on the USIM, if this is indicated by the class 2 of the SMS (USIM specific SM). For this it is assumed, that at least one relevant SMS field are available on the USIM and they are indicated as empty.
8.2.1.2 Conformance requirement
The received class 2 SMS shall be stored on the USIM in EFSMS. The status of a received SMS, which has not been read yet, shall be set to "3" (SMS to be read).
– TS 23.038 [3], clause 4.
– TS 23.040 [13], clause 10.1, operation 6;
– TS 24.011, clauses 8.2.2, 8.2.3 and 8.2.5.4, Table 8.4 (part 2)
– TS 31.102 [4], clauses 4.2.25.
8.2.1.3 Test purpose
1) To verify that the Terminal stored correctly the class 2 SMS on the USIM.
2) To verify that the Terminal sets the status of a received, and not yet read SMS to "3" (SMS to be read)
8.2.1.4 Method of test
8.2.1.4.1 Initial conditions
The default UICC is used with the following exceptions:
1) EFUST (USIM Service Table)
Logically: Local Phone Book available
User controlled PLMN selector available
Fixed dialling numbers available
Barred dialling numbers available
The GSM Access available
The Group Identifier level 1 and level 2 not available
SMS available
SMS Status available
Service n 33 (Packed Switched Domain) shall be set to ‘1’
Enabled Services Table available
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
|
Binary |
xx1x xx11 |
xxxx X11x |
xxxx 1×00 |
xxxx x1xx |
xxxx xx11 |
The coding of EFUST shall conform with the capabilities of the USIM used.
1) EFSMS (Short Message Service) and EFSMSS (SMS Status) as defined in 8.2.4.4.1.
The USS (in case of a Terminal accessing UTRAN)/SS (in case of a Terminal accessing a GERAN) transmits on the BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 246/081/0001.
– Access control: unrestricted.
The USS/SS transmits the class 2 short message with the parameters as defined in 8.2.4.4.1.
User Equipment:
The UE is connected to the USIM-Simulator and the USS/SS.
8.2.1.4.2 Procedure
CS related sequence for UTRAN/GERAN
Perform the "CS related procedure" and continue with "Generic Procedure 1" as defined clause 8.2.4.4.2 as test "8.2.1" with the following parameters:
– Applicable Network Simulator (NWS): USS (UMTS System Simulator or System Simulator)
– CS is used to send and receive short messages
– ME supports UTRAN or GERAN
CS related procedure:
a) The ME is switched on and will perform the Profile Download, USIM initialization and network registration.
b) Continue with step c) of the Generic Procedure 1 as defined in 8.2.4.4.2.
8.2.1.5 Acceptance criteria
1) After step c) the record of the USIM EFSMS which was empty, shall contain the values as defined in 8.2.4.5
8.2.2 Correct reading of a SM on the USIM
8.2.2.1 Definition and applicability
A SM which is stored but not yet read, is indicated as Status "3" (SMS to be read ) on EFSMS. The Terminal may indicate the user this status. After the SMS is read by the user, the status of the SMS shall be changed to "1" (SMS read).
8.2.2.2 Conformance requirement
A received SM was stored on the USIM in EFSMS. At the time the SMS is read by the user, the status of a received SMS, shall be changed to "1" (SMS read).
– TS 23.038 [3], clause 4.
– TS 23.040 [13];
– TS 31.102 [4], clauses 4.2.25 and 4.2.28.
8.2.2.3 Test purpose
1) To verify that the Terminal read correctly the SMS on the USIM.
2) To verify that the Terminal changes the status of a read SMS to "1" (SMS read).
8.2.2.4 Method of test
8.2.2.4.1 Initial conditions
The default UICC is used with the following exception:
EFUST (USIM Service Table)
Logically: Local Phone Book available
User controlled PLMN selector available
Fixed dialling numbers available
Barred dialling numbers available
The GSM Access available
The Group Identifier level 1 and level 2 not available
SMS available
SMS Status available
Service n 33 (Packed Switched Domain) shall be set to ‘1’
Enabled Services Table available
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
|
binary |
xx1x xx11 |
xxxx X11x |
xxxx 1×00 |
xxxx x1xx |
xxxx xx11 |
The coding of EFUST shall conform with the capabilities of the USIM used.
EFSMSS (SMS Status)
Logically: Last used TP-MR not set.
Memory capacity available (flag unset b1="1").
|
Coding: |
B1 |
B2 |
|
Hex |
FF |
FF |
EFSMS (Short Message Service)
Logically: Status byte set to SMS to be read.
A chosen test is written in the text body of the EFSMS.
Record 1:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex |
03 |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
… |
xx |
NOTE: "xx" shall be the appropriate text using the SMS default 7-bit coded alphabet as defined in TS 23.038 [3] which represents the stored SMS.
At least 9 records.
Logically: Status byte set to empty
no text is written (Remainder Bytes set to "FF").
Record:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex |
00 |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
… |
FF |
A USS (in case of a Terminal accessing UTRAN) or a SS (in case of a Terminal accessing GERAN) is only needed to bring the UE into a defined idle mode. The USS/SS transmits on the BCCH:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 246/081/0001.
– Access control: unrestricted.
User Equipment:
The UE is in MM-state "idle, updated".
8.2.2.4.2 Procedure
a) After the UE has brought in idle state, the SMS shall be read.
b) The UE is powered off.
8.2.2.5 Acceptance criteria
1) After a) the correct text of the SMS shall be read from the UE display.
2) After step b) the EFSMS record 1 shall contains the following values:
Logically: Status byte set to SMS read.
The entire content of the SMS shall be unchanged.
Record 1:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex |
01 |
xx |
xx |
Xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
… |
xx |
NOTE: "xx" shall be the appropriate text using the SMS default 7-bit coded alphabet as defined in TS 23.038 [3] which represents the stored SMS.
8.2.3 SM memory capacity exceeded handling
8.2.3.1 Definition and applicability
Once a SMS is received by the UE, the Terminal shall store the SM on the USIM, if this is indicated by the class 2 of the SMS (USIM specific SM). For this it is assumed, that at least one relevant SMS field are available on the USIM and they are indicated as empty. If all SMS data field are full and furthermore all memory capacity reserved for SMS inside the ME is filled up to maximum and a SM was rejected, then this shall be indicated in the SMS Status file.
8.2.3.2 Conformance requirement
The received class 2 SMS shall be stored on the USIM in EFSMS. The status of a received SMS, which has not been read yet, shall be set to "3" (SMS to be read). If the terminal notifies the network that the terminal has been unable to accept a short message because its memory capacity has been exceeded, then the ME shall set the Memory Capacity Exceeded Notification Flag in the EFSMSS.
– TS 23.038 [3], clause 4.
– TS 23.040 [13], clause 10.1, operation 6;
– TS 24.011, clauses 8.2.2, 8.2.3 and 8.2.5.4, Table 8.4 (part 2)
– TS 31.102 [4], clauses 4.2.25 and 4.2.28.
8.2.3.3 Test purpose
1) To verify that the Terminal stored correctly the class 2 SMS on the USIM.
2) To verify that the Terminal sets the status of a received, and not yet read SMS to "3" (SMS to be read).
3) To verify that the Terminal sets the memory full flag in EFSMSS if the terminal notifies the network that the terminal has been unable to accept a short message because its memory capacity has been exceeded.
8.2.3.4 Method of test
8.2.3.4.1 Initial conditions
The default UICC is used with the following exception:
EFUST (USIM Service Table)
Logically: Local Phone Book available
User controlled PLMN selector available
Fixed dialling numbers available
Barred dialling numbers available
The GSM Access available
The Group Identifier level 1 and level 2 not available
SMS available
SMS Status available
Service n 33 (Packed Switched Domain) shall be set to ‘1’
Enabled Services Table available
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
|
binary |
xx1x xx11 |
xxxx X11x |
xxxx 1×00 |
xxxx x1xx |
xxxx xx11 |
The coding of EFUST shall conform with the capabilities of the USIM used.
EFSMS (Short Message Service)
At least 10 records.
Record 1 shall be empty.
Logically: Status byte set to empty.
Record 1:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex |
00 |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
… |
FF |
All other Record shall be full.
Logically: Status byte set to SMS read.
The text body of the record shall be filled with any appropriate text.
Records:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex |
01 |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
… |
xx |
NOTE: "xx" shall be the appropriate text using the SMS default 7-bit coded alphabet as defined in TS 23.038 [3] which represents the received SMS.
EFSMSS (SMS Status)
Logically: Last used TP-MR not defined.
Memory capacity available (flag unset b1="1").
|
Coding: |
B1 |
B2 |
|
Hex |
FF |
FF |
The USS (in case of a Terminal accessing UTRAN) /SS (in case of a Terminal accessing a GERAN) transmits on the BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 246/081/0001.
– Access control: unrestricted.
The USS/ SS transmits the short messages with the following parameters:
Logically:
Class 2 SM:TS-Service Centre Address:
Bit 8: 1
Type-Of-Number: International number
Numbering-Plan-Identification: ISDN/telephony numbering plan
Address value: 112233445566
SMS TPDU:
TP-Message-Type-Indicator: SMS-DELIVER (in the direction SC to MS)
TP-More-Messages-to-Send: No more messages are waiting for the MS in this SC
TP-Reply-Path: TP-Reply-Path parameter is not set in this SMS-DELIVER
TP-User-Data-Header-Indicator: The TP-UD field contains only the short message
TP-Status-Report-Indication: A status report shall be returned to the SME
Bits 4-3: 00
TP-Originating-Address:
Bit 8: 1
Type-Of-Number: International number
Numbering-Plan-Identification: ISDN/telephony numbering plan
Address value: 012344556677
TP-Protocol-Identifier: No interworking, but SME-to-SME protocol
TP-Data-Coding-Scheme:
Bits 8-7: General Data Coding
Bit 6: Text is uncompressed
Bit 5: Bits 2-1 have a message class meaning
Bits 4-3: GSM 7 bit default alphabet
Bits 2-1: Class 2: (U)SIM specific message
TP-Service-Centre-Time-Stamp: 02-03-04 09:13:06 GMT + 1
TP-User-Data-Length: 160
TP-User-Data:
"Once a SMS is received by the UE, the Terminal shall store the SMS on the USIM, if this is indicated by the class 2 of the SMS (USIM specific SMS). For this…"
Class 1 SM:
The same content as for the Class 2 SMS except :
SMS TPDU:
TP-More-Messages-to-Send: More messages are waiting for the MS in this SC
TP-Data-Coding-Scheme:
Bits 2-1: Class 1: default meaning: ME-specific
TP-Service-Centre-Time-Stamp: Always set to current time of the system simulator
User Equipment:
The UE is in MM-state "idle, updated". If there is ME storage capacity available the storage for SMS inside the ME shall be able to allow for at least one more mobile terminated (e.g. Class 1) SM.
8.2.3.4.2 Procedure
a) After the UE is set to idle mode, the defined class 2 SM defined in 8.2.1.4.1 with 160 characters shall be sent to the UE.
b) After the UE has indicated that a SM was received, the SM shall not be read.
c) The USS starts sending Class 1 SMs as defined in 8.2.1.4.1 until the UE sends an RP-ERROR message with cause "Memory capacity exceeded".
d) The UE is powered off.
8.2.3.5 Acceptance criteria
1) After step b) the record of the EFSMS which was empty, shall contain the following values:
Logically: Status byte set to SMS to be read
The text of the received SMS shall be present in the record.
Record 1:
Logically:
Status:
RFU bits 8-6: 000
Status: Used space, message received by UE from network, message to be read
TS-Service Centre Address:
Bit 8: 1
Type-Of-Number: International number
Numbering-Plan-Identification: ISDN/telephony numbering plan
Address value: 112233445566
SMS TPDU:
TP-Message-Type-Indicator: SMS-DELIVER (in the direction SC to UE)
TP-More-Messages-to-Send: No more messages are waiting for the UE in this SC
TP-Reply-Path: TP-Reply-Path parameter is not set in this SMS-DELIVER
TP-User-Data-Header-Indicator: The TP-UD field contains only the short message
TP-Status-Report-Indication: A status report shall be returned to the SME
Bits 4-3: 00
TP-Originating-Address:
Bit 8: 1
Type-Of-Number: International number
Numbering-Plan-Identification: ISDN/telephony numbering plan
Address value: 012344556677
TP-Protocol-Identifier: No interworking, but SME-to-SME protocol
TP-Data-Coding-Scheme:
Bits 8-7: General Data Coding
Bit 6: Text is uncompressed
Bit 5: Bits 2-1 have a message class meaning
Bits 4-3: GSM 7 bit default alphabet
Bits 2-1: Class 2: (U)SIM specific message
TP-Service-Centre-Time-Stamp: 02-03-04 09:13:06 GMT + 1
TP-User-Data-Length: 160
TP-User-Data:
"Once a SMS is received by the UE, the Terminal shall store the SMS on the USIM, if this is indicated by the class 2 of the SMS (USIM specific SMS). For this …"
|
Coding: |
||||||||||||||||
|
Hex |
03 |
07 |
91 |
11 |
22 |
33 |
44 |
55 |
66 |
24 |
0C |
91 |
10 |
32 |
44 |
55 |
|
66 |
77 |
00 |
12 |
20 |
30 |
40 |
90 |
31 |
60 |
40 |
A0 |
4F |
F7 |
B8 |
0C |
|
|
0A |
83 |
A6 |
CD |
29 |
28 |
3D |
07 |
C9 |
CB |
E3 |
72 |
DA |
5E |
26 |
83 |
|
|
C4 |
79 |
10 |
1D |
5D |
06 |
55 |
8B |
2C |
10 |
1D |
5D |
06 |
51 |
CB |
F2 |
|
|
76 |
DA |
1D |
66 |
83 |
E6 |
E8 |
30 |
9B |
0D |
9A |
D3 |
DF |
F2 |
32 |
88 |
|
|
8E |
2E |
83 |
A6 |
CD |
29 |
E8 |
ED |
06 |
D1 |
D1 |
65 |
50 |
75 |
9A |
6C |
|
|
B2 |
40 |
69 |
33 |
88 |
8E |
4E |
CF |
41 |
E9 |
39 |
28 |
ED |
26 |
A7 |
C7 |
|
|
61 |
7A |
99 |
0C |
12 |
E7 |
41 |
74 |
74 |
19 |
34 |
66 |
87 |
E7 |
73 |
90 |
|
|
0C |
F4 |
36 |
83 |
E8 |
E8 |
32 |
68 |
DA |
9C |
82 |
50 |
D5 |
69 |
B2 |
09 |
|
|
9A |
C3 |
CB |
E3 |
B4 |
39 |
3D |
06 |
4D |
9B |
D3 |
94 |
0B |
64 |
7C |
CB |
|
|
41 |
74 |
74 |
7A |
0E |
72 |
B9 |
5C |
After step d) the Memory Capacity Exceeded Notification Flag in the EFSMSS shall be set to exceeded.
EFSMSS (SMS Status)
Logically: Last used TP-MR shall be set to any appropriate value.
Memory capacity exceeded (flag set b1="0").
|
Coding: |
B1 |
B2 |
|
Hex |
xx |
FE |
8.2.4 Correct storage of an SM on the UICC
8.2.4.1 Definition and applicability
For IMS: When a SIP MESSAGE request including a short message in the "vnd.3gpp.sms" payload is delivered and the extracted RP-DATA payload contains a Class 2 SM (USIM specific SM) the terminal shall store the SM on the USIM or ISIM. For this it is assumed, that at least one relevant SMS field are available on the USIM or ISIM and they are indicated as empty.
That the UE correctly implemented the role of an SMS-over-IP receiver is tested in clause 18.2 of TS 34.229-1 [33].
8.2.4.2 Conformance requirement
As TS 31.103[32] and TS 31.102[4] do not indicate in which of both applications a SM received via IMS shall be stored, the received Class 2 SM received via IMS shall be stored in EFSMS either on the USIM or on the ISIM. The status of a received SMS, which has not been read yet, shall be set to "3" (SMS to be read).
– TS 23.038 [3], clause 4.
– TS 23.040 [13], clause 10.1, operation 6;
– TS 24.011, clauses 7.3.1.1, 8.2.2, 8.2.3 and 8.2.5.4, Table 8.4 (part 2)
– TS 31.102 [4], clauses 4.2.25,
– TS 31.103 [32], clauses 4.2.12,
– TS 34.229 [33], Annexes C.2, C.18 and 18.2.
8.2.4.3 Test purpose
1) To verify that the Terminal stored correctly the class 2 SMS on the USIM or the ISIM.
2) To verify that the Terminal sets the status of a received, and not yet read SMS to "3" (SMS to be read).
8.2.4.4 Method of test
8.2.4.4.1 Initial conditions
The E-UTRAN/EPC ISIM-UICC is used with the following exception:
Logically: Local Phone Book available
User controlled PLMN selector available
Fixed dialling numbers available
Barred dialling numbers available
The GSM Access available
The Group Identifier level 1 and level 2 not available
SMS available
SMS Status available
Service n 33 (Packed Switched Domain) shall be set to ‘1’
Enabled Services Table available
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
|
Binary |
xx1x xx11 |
xxxx X11x |
xxxx 1×00 |
xxxx x1xx |
xxxx xx11 |
The coding of EFUST shall conform with the capabilities of the USIM used.
EFSMS (Short Message Service) – For USIM and ISIM
At least 10 records.
Record 1 shall be empty.
Logically: Status byte set to empty.
Record 1:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex |
00 |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
… |
FF |
All other Record shall be full.
Logically: Status byte set to SMS read.
The text body of the record shall be filled with any appropriate text.
Records:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex |
01 |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
… |
xx |
NOTE: "xx" shall be the appropriate text using the SMS default 7-bit coded alphabet as defined in TS 23.038 [3] which represents the received SMS.
EFSMSS (SMS Status) – For USIM and ISIM
Logically: Last used TP-MR not defined.
Memory capacity available (flag unset b1="1").
|
Coding: |
B1 |
B2 |
|
Hex |
FF |
FF |
The NWS transmits on the BCCH, with the following network parameters:
– Attach/detach: disabled.
– USS LAI (MCC/MNC/LAC): 246/081/0001 (For UTRAN testing only)
– E-USS TAI (MCC/MNC/TAC): 246/081/0001 (For E-UTRAN testing only)
– Access control: unrestricted.
The NWS transmits the short messages with the following parameters:
Logically:
Class 2 SM: TS-Service Centre Address:
Bit 8: 1
Type-Of-Number: International number
Numbering-Plan-Identification: ISDN/telephony numbering plan
Address value: 112233445566
SMS TPDU:
TP-Message-Type-Indicator: SMS-DELIVER (in the direction SC to MS)
TP-More-Messages-to-Send: No more messages are waiting for the MS in this SC
TP-Reply-Path: TP-Reply-Path parameter is not set in this SMS-DELIVER
TP-User-Data-Header-Indicator: The TP-UD field contains only the short message
TP-Status-Report-Indication: A status report shall be returned to the SME
Bits 4-3: 00
TP-Originating-Address:
Bit 8: 1
Type-Of-Number: International number
Numbering-Plan-Identification: ISDN/telephony numbering plan
Address value: 012344556677
TP-Protocol-Identifier: No interworking, but SME-to-SME protocol
TP-Data-Coding-Scheme:
Bits 8-7: General Data Coding
Bit 6: Text is uncompressed
Bit 5: Bits 2-1 have a message class meaning
Bits 4-3: GSM 7 bit default alphabet
Bits 2-1: Class 2: (U)SIM specific message
TP-Service-Centre-Time-Stamp: 02-03-04 09:13:06 GMT + 1
TP-User-Data-Length: 160
TP-User-Data:
"Once a SMS is received by the UE, the Terminal shall store the SMS on the USIM, if this is indicated by the class 2 of the SMS (USIM specific SMS). For this…"
8.2.4.4.2 Procedure
Sequence A for IMS on UTRAN
a) The ME activates the required bearer, discovers the P-CSCF, and registers with the values from the ISIM with the IMS services (see Note 2).
b) Continue with step c) in the Generic Procedure 1.
Sequence B for IMS on E-UTRAN
a) The ME activates the required bearer, discovers the P-CSCF, and registers with the values from the ISIM with the IMS services (see Note 3).
b) Continue with step c) in the Generic Procedure 1.
Generic Procedure 1
c) After the UE is set to idle mode, the defined class 2 SM defined in 8.2.1.4.1 with 160 characters shall be sent to the UE (see Note 1) as specified in clause 18.2 of TS 34.229-1 [33] and use the SM payload defined in 8.2.1.4.1 in the Message-body of MESSAGE defined in clause A.7.1 in TS 34.229-1 [33].
d) After the UE has indicated that a SM was received, the SM shall not be read.
e) The UE is powered off.
Note 1: In case of IMS the Short Message is contained in the message body of the SIP MESSAGE.
Note 2: For E-UTRAN: The EPS bearer context activation according to the procedures defined in TS 34.229-1 [33], Annex C.2 and C.18 is performed.
Note 3: For UTRAN: For SMS-over-IP a PDP context activation according to the procedures defined in TS 34.229-1 [33], Annex C.2 and C.17 is performed.
8.2.4.5 Acceptance criteria
1) After step d) the record of the EFSMS (on either the ISIM or USIM) which was empty, shall contain the following values:
Logically: Status byte set to SMS to be read
The text of the received SMS shall be present in the record.
Record 1:
Logically:
Status:
RFU bits 8-6: 000
Status: Used space, message received by UE from network, message to be read
TS-Service Centre Address:
Bit 8: 1
Type-Of-Number: International number
Numbering-Plan-Identification: ISDN/telephony numbering plan
Address value: 112233445566
SMS TPDU:
TP-Message-Type-Indicator: SMS-DELIVER (in the direction SC to UE)
TP-More-Messages-to-Send: No more messages are waiting for the UE in this SC
TP-Reply-Path: TP-Reply-Path parameter is not set in this SMS-DELIVER
TP-User-Data-Header-Indicator: The TP-UD field contains only the short message
TP-Status-Report-Indication: A status report shall be returned to the SME
Bits 4-3: 00
TP-Originating-Address:
Bit 8: 1
Type-Of-Number: International number
Numbering-Plan-Identification: ISDN/telephony numbering plan
Address value: 012344556677
TP-Protocol-Identifier: No interworking, but SME-to-SME protocol
TP-Data-Coding-Scheme:
Bits 8-7: General Data Coding
Bit 6: Text is uncompressed
Bit 5: Bits 2-1 have a message class meaning
Bits 4-3: GSM 7 bit default alphabet
Bits 2-1: Class 2: (U)SIM specific message
TP-Service-Centre-Time-Stamp: 02-03-04 09:13:06 GMT + 1
TP-User-Data-Length: 160
TP-User-Data:
"Once a SMS is received by the UE, the Terminal shall store the SMS on the USIM, if this is indicated by the class 2 of the SMS (USIM specific SMS). For this …"
|
Coding: |
||||||||||||||||
|
Hex |
03 |
07 |
91 |
11 |
22 |
33 |
44 |
55 |
66 |
24 |
0C |
91 |
10 |
32 |
44 |
55 |
|
66 |
77 |
00 |
12 |
20 |
30 |
40 |
90 |
31 |
60 |
40 |
A0 |
4F |
F7 |
B8 |
0C |
|
|
0A |
83 |
A6 |
CD |
29 |
28 |
3D |
07 |
C9 |
CB |
E3 |
72 |
DA |
5E |
26 |
83 |
|
|
C4 |
79 |
10 |
1D |
5D |
06 |
55 |
8B |
2C |
10 |
1D |
5D |
06 |
51 |
CB |
F2 |
|
|
76 |
DA |
1D |
66 |
83 |
E6 |
E8 |
30 |
9B |
0D |
9A |
D3 |
DF |
F2 |
32 |
88 |
|
|
8E |
2E |
83 |
A6 |
CD |
29 |
E8 |
ED |
06 |
D1 |
D1 |
65 |
50 |
75 |
9A |
6C |
|
|
B2 |
40 |
69 |
33 |
88 |
8E |
4E |
CF |
41 |
E9 |
39 |
28 |
ED |
26 |
A7 |
C7 |
|
|
61 |
7A |
99 |
0C |
12 |
E7 |
41 |
74 |
74 |
19 |
34 |
66 |
87 |
E7 |
73 |
90 |
|
|
0C |
F4 |
36 |
83 |
E8 |
E8 |
32 |
68 |
DA |
9C |
82 |
50 |
D5 |
69 |
B2 |
09 |
|
|
9A |
C3 |
CB |
E3 |
B4 |
39 |
3D |
06 |
4D |
9B |
D3 |
94 |
0B |
64 |
7C |
CB |
|
|
41 |
74 |
74 |
7A |
0E |
72 |
B9 |
5C |
2) The UE shall pass the requirements which are verified in the MT SMS test case specified in clause 18.2 of TS 34.229-1 [33].
8.2.5 Correct reading of a SM on the USIM if USIM and ISIM are present
8.2.5.1 Definition and applicability
A SM which is stored but not yet read, is indicated as Status "3" (SMS to be read) on EFSMS. The Terminal may indicate the user this status. After the SMS is read by the user, the status of the SMS shall be changed to "1" (SMS read). This applies to short messages stored on the USIM and to short messages stored on the ISIM.
8.2.5.2 Conformance requirement
A received SM was stored in EFSMS on the ISIM and another SM was stored in EFSMS on the USIM. The user shall be able to read short messages stored on the USIM. At the time the SMS is read by the user, the status of a received SMS, shall be changed to "1" (SMS read).
– TS 23.038 [3], clause 4.
– TS 23.040 [13];
– TS 31.102 [4], clauses 4.2.25 and 4.2.28,
– TS 31.103 [32], clauses 4.2.12 and 4.2.13.
8.2.5.3 Test purpose
1) To verify that the Terminal correctly reads the SMS on the USIM if the USIM and ISIM are both present.
2) To verify that the Terminal changes the status of a read SMS to "1" (SMS read) of the message read from the USIM.
8.2.5.4 Method of test
8.2.5.4.1 Initial conditions
The E-UTRAN/EPC ISIM-UICC is used with the following exception:
EFUST (USIM Service Table)
As defined in in clause 4.5.2 with the expection that services n°10 (Short Message Storage) and n°11 (SMS Status Report) are available.
EFSMSS (SMS Status) on the USIM and on the ISIM
Logically: Last used TP-MR not set.
Memory capacity available (flag unset b1="1").
|
Byte: |
B1 |
B2 |
|
Hex: |
FF |
FF |
EFSMS (Short Message Service) on the USIM
Logically: Status byte set to SMS to be read.
A chosen test is written in the text body of the EFSMS. This content shall be different from the content stored in EFSMS in the ISIM.
Record 1:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex |
03 |
xx |
xx |
xx |
Xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
… |
xx |
NOTE: "xx" shall be the appropriate text using the SMS default 7-bit coded alphabet as defined in TS 23.038 [3] which represents the stored SMS.
At least 9 records.
Logically: Status byte set to empty
no text is written (Remainder Bytes set to "FF").
Record:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex |
00 |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
… |
FF |
EFSMS (Short Message Service) on the ISIM
Logically: Status byte set to SMS to be read.
A chosen test is written in the text body of the EFSMS. This content shall be different from the content stored in EFSMS in the USIM.
Record 1:
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex: |
03 |
yy |
yy |
yy |
Yy |
yy |
yy |
yy |
yy |
yy |
yy |
yy |
… |
yy |
NOTE: "yy" shall be the appropriate text using the SMS default 7-bit coded alphabet as defined in TS 23.038 [3] which represents the stored SMS.
At least 9 records.
Logically: Status byte set to empty
no text is written (Remainder Bytes set to "FF").
Record:
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex: |
00 |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
… |
FF |
EFSMS on the USIM and EFSMS on the ISIM shall not share the same memory.
EFSMSS on the USIM and EFSMSS on the ISIM shall not share the same memory.
User Equipment:
The User Equipment is connected to the E-UTRAN/EPC ISIM-UICC.
8.2.5.4.2 Procedure
a) The UE is switched on.
b) The user shall read the SMS stored on the USIM.
c) The UE is switched off
8.2.5.5 Acceptance criteria
1) After b) the correct text of the SMS on the USIM shall be read and be displayed to the user.
2) After step b) the EFSMS record 1 of the USIM shall contains the following values:
Logically: Status byte set to SMS read.
The entire content of the SMS shall be unchanged.
Record 1:
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex: |
01 |
xx |
xx |
xx |
Xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
… |
xx |
3) After step b) the EFSMS and EFSMSS on the ISIM shall remain unchanged.
NOTE: "yy" shall be the appropriate text using the SMS default 7-bit coded alphabet as defined in TS 23.038 [3] which represents the stored SMS.
8.2.6 Correct reading of a SM on the ISIM if USIM and ISIM are present
8.2.6.1 Definition and applicability
A SM which is stored but not yet read, is indicated as Status "3" (SMS to be read) on EFSMS. The Terminal may indicate the user this status. After the SMS is read by the user, the status of the SMS shall be changed to "1" (SMS read). This applies to short messages stored on the USIM and to short messages stored on the ISIM.
8.2.6.2 Conformance requirement
A received SM was stored in EFSMS on the ISIM and another SM was stored in EFSMS on the USIM. The user shall be able to read short messages stored on the ISIM. At the time the SMS is read by the user, the status of a received SMS, shall be changed to "1" (SMS read).
– TS 23.038 [3], clause 4.
– TS 23.040 [13];
– TS 31.102 [4], clauses 4.2.25 and 4.2.28,
– TS 31.103 [32], clauses 4.2.12 and 4.2.13.
8.2.6.3 Test purpose
1) To verify that the Terminal correctly reads the SMS on the ISIM if the USIM and ISIM are both present.
2) To verify that the Terminal changes the status of a read SMS to "1" (SMS read) of the message read from the ISIM.
8.2.6.4 Method of test
8.2.6.4.1 Initial conditions
The E-UTRAN/EPC ISIM-UICC is used with the following exception:
EFUST (USIM Service Table)
As defined in in clause 4.5.2 with the expection that services n°10 (Short Message Storage) and n°11 (SMS Status Report) are available.
EFSMSS (SMS Status) on the USIM and on the ISIM
Logically: Last used TP-MR not set.
Memory capacity available (flag unset b1="1").
|
Byte: |
B1 |
B2 |
|
Hex: |
FF |
FF |
EFSMS (Short Message Service) on the USIM
Logically: Status byte set to SMS to be read.
A chosen test is written in the text body of the EFSMS. This content shall be different from the content stored in EFSMS in the ISIM.
Record 1:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex |
03 |
xx |
xx |
xx |
Xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
… |
xx |
NOTE: "xx" shall be the appropriate text using the SMS default 7-bit coded alphabet as defined in TS 23.038 [3] which represents the stored SMS.
At least 9 records.
Logically: Status byte set to empty
no text is written (Remainder Bytes set to "FF").
Record:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex |
00 |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
… |
FF |
EFSMS (Short Message Service) on the ISIM
Logically: Status byte set to SMS to be read.
A chosen test is written in the text body of the EFSMS. This content shall be different from the content stored in EFSMS in the USIM.
Record 1:
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex: |
03 |
yy |
yy |
yy |
Yy |
yy |
yy |
yy |
yy |
yy |
yy |
yy |
… |
yy |
NOTE: "yy" shall be the appropriate text using the SMS default 7-bit coded alphabet as defined in TS 23.038 [3] which represents the stored SMS.
At least 9 records.
Logically: Status byte set to empty
no text is written (Remainder Bytes set to "FF").
Record:
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex: |
00 |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
… |
FF |
EFSMS on the USIM and EFSMS on the ISIM shall not share the same memory.
EFSMSS on the USIM and EFSMSS on the ISIM shall not share the same memory.
User Equipment:
The User Equipment is connected to the E-UTRAN/EPC ISIM-UICC.
8.2.6.4.2 Procedure
a) The UE is switched on.
b) The user shall read the SMS stored on the USIM.
c) The UE is switched off
8.2.6.5 Acceptance criteria
1) After b) the correct text of the SMS on the ISIM shall be read and be displayed to the user.
2) After step b) the EFSMS record 1 of the ISIM shall contains the following values:
Logically: Status byte set to SMS read.
The entire content of the SMS shall be unchanged.
Record 1:
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
… |
B176 |
|
Hex: |
01 |
yy |
yy |
yy |
yy |
yy |
yy |
yy |
yy |
yy |
yy |
yy |
… |
Yy |
3) After step b) the EFSMS and EFSMSS on the USIM shall remain unchanged.
8.2.7 Correct storage of an SM on the UICC
8.2.7.1 Definition and applicability
Once a SMS is received by the UE, the Terminal shall store the SM on the USIM, if this is indicated by the class 2 of the SMS (USIM specific SM). For this it is assumed, that at least one relevant SMS field is available on the USIM and indicated as empty
8.2.7.2 Conformance requirement
The received class 2 SMS shall be stored on the USIM in EFSMS. The status of a received SMS, which has not been read yet, shall be set to "3" (SMS to be read).
– TS 23.038 [3], clause 4.
– TS 23.040 [13], clause 10.1, operation 6;
– TS 24.011, clauses 7.3.1.1, 8.2.2, 8.2.3 and 8.2.5.4, Table 8.4 (part 2)
– TS 31.102 [4], clauses 4.2.25.
– TS 24.301 [26], clauses 5.6.3, 5.6.3.3.
8.2.7.3 Test purpose
1) To verify that the Terminal stored correctly the class 2 SMS on the USIM.
2) To verify that the Terminal sets the status of a received, and not yet read SMS to "3" (SMS to be read).
8.2.7.4 Method of test
8.2.7.4.1 Initial conditions
The default E-UTRAN UICC is used with the following exceptions
1) EFSMS (Short Message Service) and EFSMSS (SMS Status) as defined in 8.2.4.4.1.
The NB-SS transmits on the BCCH, with the following network parameters:
– Attach/detach: disabled.
– TAI (MCC/MNC/TAC): 246/081/0001
– Access control: unrestricted.
The NB-SS transmits the class 2 short message with the parameters as defined in 8.2.4.4.1.
8.2.7.4.2 Procedure
a) The ME is switched on and will perform USIM initialization and network registration.
b) SMS over SGs (DOWNLINK NAS TRANSPORT and UPLINK NAS TRANSPORT messages) is used to send and receive short messages.
c) Continue with step c) of the Generic Procedure 1 as defined in 8.2.4.4.2.
8.2.7.5 Acceptance criteria
1) After step c) the record of the USIM EFSMS which was empty, shall contain the values as defined in 8.2.4.5
8.3 MMS related tests
8.3.1 UE recognising the priority order of MMS Issuer Connectivity Parameters
8.3.1.1 Definition and applicability
An MMS User Agent shall use the MMS related information stored in the USIM, if present, unless otherwise specified by the user. Some of these sets of MMS connectivity parameters are preset by the issuer of the USIM with the first supported set being the default. This information is used to connect to the network for purpose of accessing the MMS Relay/Server.
The MMS connectivity information on the USIM includes preferences for the selection of Interface to Core Network and Bearer parameters. If these are stored on the USIM the MMS-capable UE shall automatically select the Interface to Core Network and Bearer parameters based on their order of precedence defined on the USIM unless otherwise specified by the user.
MMS user preferences information, which is stored on the USIM, shall be used by an MMS User Agent for user assistance in preparation of terminal-originated MMs (e.g. default values for parameters that are often used).
8.3.1.2 Conformance requirement
The Terminal’s MMS User Agent shall use the MMS connectivity parameters stored first in the supported parameter sets of EFMMSICP as default parameters to connect to the network for MMS purposes (i.e. sending an User generated MM).
– TS 31.102 [4], clauses 4.2.69 and 5.3.30;
– TS 23.140 [23], clause 7.1.14 and Annex F.
MMS user preferences information, which is stored on the USIM, shall be used by an MMS User Agent for user assistance in preparation of terminal-originated MMs.
– TS 31.102 [4], clauses 4.2.70 and 5.3.31;
– TS 23.140 [23], clause 7.1.14 and Annex F.
8.3.1.3 Test purpose
1) To verify that the Terminal’s MMS User Agent uses the MMS connectivity parameter stored on the USIM to connect to the network for MMS purposes.
2) To verify that the Terminal’s MMS User Agent uses the first stored set of supported parameters in EFMMSICP as default.
3) To verify that the Terminal’s MMS User Agent uses the MMS user preference information stored on the USIM for user assistance in preparation of terminal-originated MMs.
8.3.1.4 Method of test
8.3.1.4.1 Initial conditions
Four MMS Relays/Servers are available:
MMS Relay/Server 1:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator1.com"
Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+496998625"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "B2B_OTS1"
Authentication pw: "B2B_password1"
Gateway
Address: "170.187.51.3"
Type of address: "Ipv4"
Port : "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user1"
Authentication pw: "gateway_password1"
MMS Relay/Server 2:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator1.com"
Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+496998626"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "B2C_OTS2"
Authentication pw: "B2C_password2"
Gateway
Address: "170.187.51.3"
Type of address: "Ipv4"
Port : "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user1"
Authentication pw: "gateway_password1"
MMS Relay/Server 3:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator1.com"
Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2B-operator1.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "B2B_OTS1"
Authentication pw: "B2B_password1"
Gateway
Address: "170.187.51.3"
Type of address: "Ipv4"
Port : "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user1"
Authentication pw: "gateway_password1"
MMS Relay/Server 4:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator1.com"
Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2C-operator1.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "B2C_OTS2"
Authentication pw: "B2C_password2"
Gateway
Address: "170.187.51.3"
Type of address: "Ipv4"
Port : "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user1"
Authentication pw: "gateway_password1"
The default UICC is used with the following exceptions:
EFUST (USIM Service Table)
Logically: Local Phone Book available
User controlled PLMN selector available
Fixed dialling numbers available
Barred dialling numbers available
The GSM Access available
The Group Identifier level 1 and level 2 not available
SMS available
SMS Status available
Service no. 33 (Packed Switched Domain) shall be set to ‘1’
Service no. 52 Multimedia Messaging Service available
Service no. 55 MMS User Connectivity Parameters not available
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
|
Binary |
xx1x xx11 |
x11x xxxx |
xxxx 1×00 |
xxxx x1xx |
xxxx xxx1 |
xxxx xxxx |
x0xx 1xxx |
EFMMSN
Logically:
MMS Status: Free space
MMS Implementation : "00"
MMS Notification: "FF FF … FF" (251 bytes)
Extension file record number: "FF"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
… |
B254 |
B255 |
|
00 |
00 |
00 |
FF |
FF |
FF |
FF |
EFMMSICP
Logically:
MMS Connectivity Parameters
MMS Implementation
MMS Implementation Information : "WAP"
MMS Relay/Server
MMS Relay/Server Address "http://mms-operator1.com"
1st Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+496998625"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "B2B_OTS1"
Authentication pw: "B2B_password1"
2nd Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+496998626"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "B2C_OTS2"
Authentication pw: "B2C_password2"
3rd Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2B-operator1.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "B2B_OTS1"
Authentication pw: "B2B_password1"
4th Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2C-operator1.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "B2C_OTS2"
Authentication pw: "B2C_password2"
Gateway:
Address: "170.187.51.3"
Type of address: "Ipv4"
Port : "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user1"
Authentication pw: "gateway_password1"
|
Coding: |
AB |
82 |
01 |
47 |
80 |
01 |
01 |
81 |
18 |
68 |
74 |
74 |
|
70 |
3A |
2F |
2F |
6D |
6D |
73 |
2E |
6F |
70 |
65 |
72 |
|
|
61 |
74 |
6F |
72 |
31 |
2E |
63 |
6F |
6D |
82 |
2F |
10 |
|
|
AA |
08 |
2B |
34 |
39 |
36 |
39 |
39 |
38 |
36 |
32 |
35 |
|
|
00 |
09 |
87 |
25 |
C5 |
0A |
90 |
0C |
9A |
0D |
42 |
32 |
|
|
42 |
11 |
4F |
54 |
53 |
31 |
00 |
0E |
42 |
32 |
42 |
11 |
|
|
70 |
61 |
73 |
73 |
77 |
6F |
72 |
64 |
31 |
00 |
82 |
2F |
|
|
10 |
AA |
08 |
2B |
34 |
39 |
36 |
39 |
39 |
38 |
36 |
32 |
|
|
36 |
00 |
09 |
87 |
25 |
C5 |
0A |
90 |
0C |
9A |
0D |
42 |
|
|
32 |
43 |
11 |
4F |
54 |
53 |
32 |
00 |
0E |
42 |
32 |
43 |
|
|
11 |
70 |
61 |
73 |
73 |
77 |
6F |
72 |
64 |
32 |
00 |
82 |
|
|
43 |
10 |
AB |
08 |
03 |
77 |
61 |
70 |
0D |
42 |
32 |
42 |
|
|
2D |
6F |
70 |
65 |
72 |
61 |
74 |
6F |
72 |
31 |
03 |
63 |
|
|
6F |
6D |
00 |
09 |
89 |
0A |
90 |
31 |
03 |
37 |
70 |
38 |
|
|
06 |
33 |
60 |
36 |
08 |
0C |
9A |
0D |
42 |
32 |
42 |
11 |
|
|
4F |
54 |
53 |
31 |
00 |
0E |
42 |
32 |
42 |
11 |
70 |
61 |
|
|
73 |
73 |
77 |
6F |
72 |
64 |
31 |
00 |
82 |
43 |
10 |
AB |
|
|
08 |
03 |
77 |
61 |
70 |
0D |
42 |
32 |
43 |
2D |
6F |
70 |
|
|
65 |
72 |
61 |
74 |
6F |
72 |
31 |
03 |
63 |
6F |
6D |
00 |
|
|
09 |
89 |
0A |
90 |
31 |
03 |
37 |
70 |
38 |
06 |
33 |
60 |
|
|
36 |
08 |
0C |
9A |
0D |
42 |
32 |
43 |
11 |
4F |
54 |
53 |
|
|
32 |
00 |
0E |
42 |
32 |
43 |
11 |
70 |
61 |
73 |
73 |
77 |
|
|
6F |
72 |
64 |
32 |
00 |
83 |
43 |
20 |
31 |
37 |
30 |
2E |
|
|
31 |
38 |
37 |
2E |
35 |
31 |
2E |
33 |
00 |
21 |
85 |
23 |
|
|
39 |
32 |
30 |
31 |
00 |
24 |
CB |
19 |
9C |
1A |
67 |
61 |
|
|
74 |
65 |
77 |
61 |
79 |
11 |
75 |
73 |
65 |
72 |
31 |
00 |
|
|
1B |
67 |
61 |
74 |
65 |
77 |
61 |
79 |
11 |
70 |
61 |
73 |
|
|
73 |
77 |
6F |
72 |
64 |
31 |
00 |
EFMMSUP
Logically:
MMS Implementation
MMS implementation information: "WAP"
MMS User Preference Profile Name: "Greeting cards"
MMS User Information Preference Information
Visibility: "hide"
Delivery report: "yes"
Read-reply: "yes"
Priority: "normal"
Delivery-Time:
Value (absolute): "1-Jan-2003, 12:00:00 AM GMT"
Expiry:
Value (relative): 1104537600 seconds
|
Coding: |
80 |
01 |
01 |
81 |
0E |
47 |
72 |
65 |
65 |
74 |
69 |
6E |
|
67 |
20 |
63 |
61 |
72 |
64 |
73 |
82 |
19 |
14 |
80 |
06 |
|
|
80 |
10 |
80 |
0F |
81 |
07 |
07 |
80 |
05 |
00 |
3E |
12 |
|
|
2F |
80 |
08 |
06 |
81 |
04 |
41 |
D5 |
E8 |
00 |
The UICC is installed into the Terminal and the user has indicated the data stored in EFMMSICP as default.
8.3.1.4.2 Procedure
a) The Terminal is powered on and the PIN shall be entered.
b) When the Terminal is in idle mode the user shall generate an MM using the MMS User Agent on the Terminal with the default MMS connectivity settings provided by the card issuer and the MMS user preference information stored in the card and send it to "+0123456789".
8.3.1.5 Acceptance criteria
1) After step b) the Terminal shall have read the set of supported MMS connectivity parameters stored first in EFMMSICP.
2) After step b) the Terminal shall have sent the MM to "+0123456789" using the MMS connectivity parameters stored first in the supported parameter sets in EFMMSICP.
3) After step b) the Terminal shall have sent the MM to "+0123456789" using the MMS user preference information stored in EFMMSUP.
8.3.2 UE recognising the priority order of MMS User Connectivity Parameters
8.3.2.1 Definition and applicability
An MMS User Agent shall use the MMS related information stored in the USIM, if present, unless otherwise specified by the user. The MMS connectivity parameters determined by the user, with the first supported set being the default, shall be used to connect to the network for purpose of accessing the MMS Relay/Server.
The MMS connectivity information on the USIM includes preferences for the selection of Interface to Core Network and Bearer parameters. If these are stored on the USIM the MMS-capable UE shall automatically select the Interface to Core Network and Bearer parameters based on their order of precedence defined on the USIM unless otherwise specified by the user.
MMS user preferences information, which is stored on the USIM, shall be used by an MMS User Agent for user assistance in preparation of terminal-originated MMs (e.g. default values for parameters that are often used).
8.3.2.2 Conformance requirement
When using the MMS User Connectivity Parameters to connect to the network for MMS purposes (i.e. sending an User generated MM), the Terminal’s MMS User Agent shall use the MMS User Connectivity Parameters with the highest priority (as defined by its position in EFMMSUCP) unless otherwise specified by the user.
– TS 31.102 [4], clauses 4.2.71 and 5.3.32;
– TS 23.140 [23], clause 7.1.14 and Annex F.
MMS user preferences information, which is stored on the USIM, shall be used by an MMS User Agent for user assistance in preparation of terminal-originated MMs.
– TS 31.102 [4], clauses 4.2.70 and 5.3.31;
– TS 23.140 [23], clause 7.1.14 and Annex F.
8.3.2.3 Test purpose
1) To verify that the Terminal’s MMS User Agent uses the MMS connectivity parameter stored on the USIM to connect to the network for MMS purposes.
2) To verify that when using the MMS User Connectivity Parameters to connect to the network for MMS purposes the Terminal’s MMS User Agent uses the set of supported parameters in EF MMSUCP with the highest priority (as defined by its position in EFMMSUCP).
3) To verify that the Terminal’s MMS User Agent uses the MMS user preference information stored on the USIM for user assistance in preparation of terminal-originated MMs.
8.3.2.4 Method of test
8.3.2.4.1 Initial conditions
Four MMS Relays/Servers are available:
MMS Relay/Server 1:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator2.com"
Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+495251699"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "UDO_OTS1"
Authentication pw: "Udo_password1"
Gateway
Address: "170.187.51.4"
Type of address: "Ipv4"
Port : "9203"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user7"
Authentication pw: "gateway_password7"
MMS Relay/Server 2:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator2.com"
Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+495251700"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "UDO_OTS2"
Authentication pw: "Udo_password2"
Gateway
Address: "170.187.51.4"
Type of address: "Ipv4"
Port : "9203"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user7"
Authentication pw: "gateway_password7"
MMS Relay/Server 3:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator2.com"
Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2B-operator2.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "UDO_OTS1"
Authentication pw: "Udo_password1"
Gateway
Address: "170.187.51.4"
Type of address: "Ipv4"
Port : "9203"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user7"
Authentication pw: "gateway_password7"
MMS Relay/Server 4:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator2.com"
Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2C-operator2.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "UDO_OTS2"
Authentication pw: "Udo_password2"
Gateway
Address: "170.187.51.4"
Type of address: "Ipv4"
Port : "9203"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user7"
Authentication pw: "gateway_password7"
The default UICC is used with the following exceptions:
EFUST (USIM Service Table)
Logically: Local Phone Book available
User controlled PLMN selector available
Fixed dialling numbers available
Barred dialling numbers available
The GSM Access available
The Group Identifier level 1 and level 2 not available
SMS available
SMS Status available
Service no. 33 (Packed Switched Domain) shall be set to ‘1’
Service no. 52 Multimedia Messaging Service available
Service no. 55 MMS User Connectivity Parameters available
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
|
Binary |
xx1x xx11 |
x11x xxxx |
xxxx 1×00 |
xxxx x1xx |
xxxx xxx1 |
xxxx xxxx |
x1xx 1xxx |
EFMMSN
Logically:
MMS Status: Free space
MMS Implementation : "00"
MMS Notification: "FF FF … FF" (251 bytes)
Extension file record number: "FF"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
… |
B254 |
B255 |
|
00 |
00 |
00 |
FF |
FF |
FF |
FF |
EFMMSICP
Logically: Empty
|
Coding: |
B1 |
B2 |
… |
Bxx |
|
FF |
FF |
FF |
EFMMSUP
Logically:
MMS Implementation
MMS implementation information: "WAP"
MMS User Preference Profile Name: "Greeting cards"
MMS User Information Preference Information
Visibility: "hide"
Delivery report: "yes"
Read-reply: "yes"
Priority: "normal"
Delivery-Time:
Value (absolute): "1-Jan-2003, 12:00:00 AM GMT"
Expiry:
Value (relative): 1104537600 seconds
|
Coding: |
80 |
01 |
01 |
81 |
0E |
47 |
72 |
65 |
65 |
74 |
69 |
6E |
|
67 |
20 |
63 |
61 |
72 |
64 |
73 |
82 |
19 |
14 |
80 |
06 |
|
|
80 |
10 |
80 |
0F |
81 |
07 |
07 |
80 |
05 |
00 |
3E |
12 |
|
|
2F |
80 |
08 |
06 |
81 |
04 |
41 |
D5 |
E8 |
00 |
EFMMSUCP
Logically:
MMS Connectivity Parameters
MMS Implementation
MMS Implementation Information : "WAP"
MMS Relay/Server
MMS Relay/Server Address "http://mms-operator2.com"
1st Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+495251699"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "UDO_OTS1"
Authentication pw: "Udo_password1"
2nd Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+495251700"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "UDO_OTS2"
Authentication pw: "Udo_password2"
3rd Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2B-operator2.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "UDO_OTS1"
Authentication pw: "Udo_password1"
4th Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2C-operator2.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "UDO_OTS2"
Authentication pw: "Udo_password2"
Gateway:
Address: "170.187.51.4"
Type of address: "Ipv4"
Port : "9203"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user7"
Authentication pw: "gateway_password7"
|
Coding: |
AB |
82 |
01 |
47 |
80 |
01 |
01 |
81 |
18 |
68 |
74 |
74 |
|
70 |
3A |
2F |
2F |
6D |
6D |
73 |
2E |
6F |
70 |
65 |
72 |
|
|
61 |
74 |
6F |
72 |
32 |
2E |
63 |
6F |
6D |
82 |
2F |
10 |
|
|
AA |
08 |
2B |
34 |
39 |
35 |
32 |
35 |
31 |
36 |
39 |
39 |
|
|
00 |
09 |
87 |
25 |
C5 |
0A |
90 |
0C |
9A |
0D |
55 |
44 |
|
|
4F |
11 |
4F |
54 |
53 |
31 |
00 |
0E |
55 |
64 |
6F |
11 |
|
|
70 |
61 |
73 |
73 |
77 |
6F |
72 |
64 |
31 |
00 |
82 |
2F |
|
|
10 |
AA |
08 |
2B |
34 |
39 |
35 |
32 |
35 |
31 |
37 |
30 |
|
|
30 |
00 |
09 |
87 |
25 |
C5 |
0A |
90 |
0C |
9A |
0D |
55 |
|
|
44 |
4F |
11 |
4F |
54 |
53 |
32 |
00 |
0E |
55 |
64 |
6F |
|
|
11 |
70 |
61 |
73 |
73 |
77 |
6F |
72 |
64 |
32 |
00 |
82 |
|
|
43 |
10 |
AB |
08 |
03 |
77 |
61 |
70 |
0D |
42 |
32 |
42 |
|
|
2D |
6F |
70 |
65 |
72 |
61 |
74 |
6F |
72 |
32 |
03 |
63 |
|
|
6F |
6D |
00 |
09 |
89 |
0A |
90 |
31 |
03 |
37 |
70 |
38 |
|
|
06 |
33 |
60 |
36 |
08 |
0C |
9A |
0D |
55 |
44 |
4F |
11 |
|
|
4F |
54 |
53 |
31 |
00 |
0E |
55 |
64 |
6F |
11 |
70 |
61 |
|
|
73 |
73 |
77 |
6F |
72 |
64 |
31 |
00 |
82 |
43 |
10 |
AB |
|
|
08 |
03 |
77 |
61 |
70 |
0D |
42 |
32 |
43 |
2D |
6F |
70 |
|
|
65 |
72 |
61 |
74 |
6F |
72 |
32 |
03 |
63 |
6F |
6D |
00 |
|
|
09 |
89 |
0A |
90 |
31 |
03 |
37 |
70 |
38 |
06 |
33 |
60 |
|
|
36 |
08 |
0C |
9A |
0D |
55 |
44 |
4F |
11 |
4F |
54 |
53 |
|
|
32 |
00 |
0E |
55 |
64 |
6F |
11 |
70 |
61 |
73 |
73 |
77 |
|
|
6F |
72 |
64 |
32 |
00 |
83 |
3B |
20 |
31 |
37 |
30 |
2E |
|
|
31 |
38 |
37 |
2E |
35 |
31 |
2E |
34 |
00 |
21 |
85 |
23 |
|
|
39 |
32 |
30 |
31 |
00 |
24 |
CB |
19 |
9C |
1A |
67 |
61 |
|
|
74 |
65 |
77 |
61 |
79 |
11 |
75 |
73 |
65 |
72 |
37 |
00 |
|
|
1B |
67 |
61 |
74 |
65 |
77 |
61 |
79 |
11 |
70 |
61 |
73 |
|
|
73 |
77 |
6F |
72 |
64 |
37 |
00 |
The UICC is installed into the Terminal and the user has indicated the data stored in EFMMSUCPas default.
8.3.2.4.2 Procedure
a) The Terminal is powered on and the PIN shall be entered.
b) When the Terminal is in idle mode the user shall generate an MM using the MMS User Agent on the Terminal with the default MMS User Connectivity Parameters and the MMS user preference information stored in the card and send it to "+0123456789".
8.3.2.5 Acceptance criteria
1) After step b) the Terminal shall have read the first supported set of MMS connectivity parameters stored in EFMMSUCP.
2) After step b) the Terminal shall have sent the MM to "+0123456789" using the MMS User Connectivity Parameter set with the highest priority (as defined by its position in EFMMSUCP), which can be used to access an available MMS Relay/Server.
3) After step b) the Terminal shall have sent the MM to "+0123456789" using the MMS user preference information stored in EFMMSUCP.
8.3.3 UE recognising the priority order of MMS Issuer Connectivity Parameters over the MMS User Connectivity Parameters
8.3.3.1 Definition and applicability
An MMS User Agent shall use the MMS related information stored in the USIM, if present, unless otherwise specified by the user. This information comprises MMS connectivity information, MMS user preferences and MMS notifications.
MMS user preferences information, which is stored on the USIM, shall be used by an MMS User Agent for user assistance in preparation of terminal-originated MMs (e.g. default values for parameters that are often used).
8.3.3.2 Conformance requirement
MMS connectivity information, on the USIM includes a number of sets of MMS connectivity parameters. Some of these sets of MMS connectivity parameters are preset by the issuer of the USIM with the first set being the default. Such default preset MMS connectivity parameter set shall be selected unless otherwise specified by the user.
– TS 31.102 [4], clauses 4.2.69, 4.7.71, 5.3.30 and 5.3.32;
– TS 23.140 [23], clause 7.1.14 and Annex F
8.3.3.3 Test purpose
1) To verify that the Terminal’s MMS User Agent uses the MMS connectivity parameter stored on the USIM to connect to the network for MMS purposes.
2) To verify that a MMS Issuer Connectivity Parameter set with lower priority (as defined by its position in EFMMSICP) takes precedence over a MMS User Connectivity Parameter set with a higher priority.
8.3.3.4 Method of test
8.3.3.4.1 Initial conditions
Four MMS Relays/Servers are available:
MMS Relay/Server 1:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator3.com"
Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+495251699"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "UDO_OTS1"
Authentication pw: "Udo_password1"
Gateway
Address: "170.187.51.5"
Type of address: "Ipv4"
Port : "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user9"
Authentication pw: "gateway_password9"
MMS Relay/Server 2:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator3.com"
Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2P-operator3.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "UDO_OTS1"
Authentication pw: "Udo_password1"
Gateway
Address: "170.187.51.5"
Type of address: "Ipv4"
Port : "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user9"
Authentication pw: "gateway_password9"
MMS Relay/Server 3:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator3.com"
Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+496998626"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "B2C_OTS2"
Authentication pw: "B2C_password2"
Gateway
Address: "170.187.51.5"
Type of address: "Ipv4"
Port : "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user9"
Authentication pw: "gateway_password9"
MMS Relay/Server 4:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator3.com"
Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2C-operator3.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "B2C_OTS2"
Authentication pw: "B2C_password2"
Gateway
Address: "170.187.51.5"
Type of address: "Ipv4"
Port : "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user9"
Authentication pw: "gateway_password9"
The default UICC is used with the following exceptions:
EFUST (USIM Service Table)
Logically: Local Phone Book available
User controlled PLMN selector available
Fixed dialling numbers available
Barred dialling numbers available
The GSM Access available
The Group Identifier level 1 and level 2 not available
SMS available
SMS Status available
Service no. 33 (Packed Switched Domain) shall be set to ‘1’
Service no. 52 Multimedia Messaging Service available
Service no. 55 MMS User Connectivity Parameters available
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
|
Binary |
xx1x xx11 |
x11x xxxx |
xxxx 1×00 |
xxxx x1xx |
xxxx xxx1 |
xxxx xxxx |
x1xx 1xxx |
EFMMSN
Logically:
MMS Status: Free space
MMS Implementation : "00"
MMS Notification: "FF FF … FF" (251 bytes)
Extension file record number: "FF"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
… |
B254 |
B255 |
|
00 |
00 |
00 |
FF |
FF |
FF |
FF |
EFMMSICP
Logically:
MMS Connectivity Parameters
MMS Implementation
MMS Implementation Information : "WAP"
MMS Relay/Server
MMS Relay/Server Address "http://mms-operator3.com"
1st Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+496998625"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "B2B_OTS1"
Authentication pw: "B2B_password1"
2nd Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+496998626"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "B2C_OTS2"
Authentication pw: "B2C_password2"
3rd Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2B-operator3.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "B2B_OTS1"
Authentication pw: "B2B_password1"
4th Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2C-operator3.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "B2C_OTS2"
Authentication pw: "B2C_password2"
Gateway:
Address: "170.187.51.5"
Type of address: "Ipv4"
Port : "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user9"
Authentication pw: "gateway_password9"
|
Coding: |
AB |
82 |
01 |
47 |
80 |
01 |
01 |
81 |
18 |
68 |
74 |
74 |
|
70 |
3A |
2F |
2F |
6D |
6D |
73 |
2E |
6F |
70 |
65 |
72 |
|
|
61 |
74 |
6F |
72 |
33 |
2E |
63 |
6F |
6D |
82 |
2F |
10 |
|
|
AA |
08 |
2B |
34 |
39 |
36 |
39 |
39 |
38 |
36 |
32 |
35 |
|
|
00 |
09 |
87 |
25 |
C5 |
0A |
90 |
0C |
9A |
0D |
42 |
32 |
|
|
42 |
11 |
4F |
54 |
53 |
31 |
00 |
0E |
42 |
32 |
42 |
11 |
|
|
70 |
61 |
73 |
73 |
77 |
6F |
72 |
64 |
31 |
00 |
82 |
2F |
|
|
10 |
AA |
08 |
2B |
34 |
39 |
36 |
39 |
39 |
38 |
36 |
32 |
|
|
36 |
00 |
09 |
87 |
25 |
C5 |
0A |
90 |
0C |
9A |
0D |
42 |
|
|
32 |
43 |
11 |
4F |
54 |
53 |
32 |
00 |
0E |
42 |
32 |
43 |
|
|
11 |
70 |
61 |
73 |
73 |
77 |
6F |
72 |
64 |
32 |
00 |
82 |
|
|
43 |
10 |
AB |
08 |
03 |
77 |
61 |
70 |
0D |
42 |
32 |
42 |
|
|
2D |
6F |
70 |
65 |
72 |
61 |
74 |
6F |
72 |
33 |
03 |
63 |
|
|
6F |
6D |
00 |
09 |
89 |
0A |
90 |
31 |
03 |
37 |
70 |
38 |
|
|
06 |
33 |
60 |
36 |
08 |
0C |
9A |
0D |
42 |
32 |
42 |
11 |
|
|
4F |
54 |
53 |
31 |
00 |
0E |
42 |
32 |
42 |
11 |
70 |
61 |
|
|
73 |
73 |
77 |
6F |
72 |
64 |
31 |
00 |
82 |
43 |
10 |
AB |
|
|
08 |
03 |
77 |
61 |
70 |
0D |
42 |
32 |
43 |
2D |
6F |
70 |
|
|
65 |
72 |
61 |
74 |
6F |
72 |
33 |
03 |
63 |
6F |
6D |
00 |
|
|
09 |
89 |
0A |
90 |
31 |
03 |
37 |
70 |
38 |
06 |
33 |
60 |
|
|
36 |
08 |
0C |
9A |
0D |
42 |
32 |
43 |
11 |
4F |
54 |
53 |
|
|
32 |
00 |
0E |
42 |
32 |
43 |
11 |
70 |
61 |
73 |
73 |
77 |
|
|
6F |
72 |
64 |
32 |
00 |
83 |
3B |
20 |
31 |
37 |
30 |
2E |
|
|
31 |
38 |
37 |
2E |
35 |
31 |
2E |
35 |
00 |
21 |
85 |
23 |
|
|
39 |
32 |
30 |
31 |
00 |
24 |
CB |
19 |
9C |
1A |
67 |
61 |
|
|
74 |
65 |
77 |
61 |
79 |
11 |
75 |
73 |
65 |
72 |
39 |
00 |
|
|
1B |
67 |
61 |
74 |
65 |
77 |
61 |
79 |
11 |
70 |
61 |
73 |
|
|
73 |
77 |
6F |
72 |
64 |
39 |
00 |
EFMMSUP
Logically:
MMS Implementation
MMS implementation information: "WAP"
MMS User Preference Profile Name: "Greeting cards"
MMS User Information Preference Information
Visibility: "hide"
Delivery report: "yes"
Read-reply: "yes"
Priority: "normal"
Delivery-Time:
Value (absolute): "1-Jan-2003, 12:00:00 AM GMT"
Expiry:
Value (relative): 1104537600 seconds
|
Coding: |
80 |
01 |
01 |
81 |
0E |
47 |
72 |
65 |
65 |
74 |
69 |
6E |
|
67 |
20 |
63 |
61 |
72 |
64 |
73 |
82 |
19 |
14 |
80 |
06 |
|
|
80 |
10 |
80 |
0F |
81 |
07 |
07 |
80 |
05 |
00 |
3E |
12 |
|
|
2F |
80 |
08 |
06 |
81 |
04 |
41 |
D5 |
E8 |
00 |
EFMMSUCP
Logically:
MMS Connectivity Parameters
MMS Implementation
MMS Implementation Information : "WAP"
MMS Relay/Server
MMS Relay/Server Address "http://mms-operator3.com"
1st Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+495251699"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "UDO_OTS1"
Authentication pw: "Udo_password1"
2nd Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+495251700"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "UDO_OTS2"
Authentication pw: "Udo_password2"
3rd Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2P-operator3.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "UDO_OTS1"
Authentication pw: "Udo_password1"
4th Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2C-operator3.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "UDO_OTS2"
Authentication pw: "Udo_password2"
Gateway:
Address: "170.187.51.5"
Type of address: "Ipv4"
Port : "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user9"
Authentication pw: "gateway_password9"
|
Coding: |
AB |
82 |
01 |
47 |
80 |
01 |
01 |
81 |
18 |
68 |
74 |
74 |
|
|
70 |
3A |
2F |
2F |
6D |
6D |
73 |
2D |
6F |
70 |
65 |
72 |
||
|
61 |
74 |
6F |
72 |
33 |
2E |
63 |
6F |
6D |
82 |
2F |
10 |
||
|
AA |
08 |
2B |
34 |
39 |
35 |
32 |
35 |
31 |
36 |
39 |
39 |
||
|
00 |
09 |
87 |
25 |
C5 |
0A |
90 |
0C |
9A |
0D |
55 |
44 |
||
|
4F |
11 |
4F |
54 |
53 |
31 |
00 |
0E |
55 |
64 |
6F |
11 |
||
|
70 |
61 |
73 |
73 |
77 |
6F |
72 |
64 |
31 |
00 |
82 |
2F |
||
|
10 |
AA |
08 |
2B |
34 |
39 |
35 |
32 |
35 |
31 |
37 |
30 |
||
|
30 |
00 |
09 |
87 |
25 |
C5 |
0A |
90 |
0C |
9A |
0D |
55 |
||
|
44 |
4F |
11 |
4F |
54 |
53 |
32 |
00 |
0E |
55 |
64 |
6F |
||
|
11 |
70 |
61 |
73 |
73 |
77 |
6F |
72 |
64 |
32 |
00 |
82 |
||
|
43 |
10 |
AB |
08 |
03 |
77 |
61 |
70 |
0D |
42 |
32 |
50 |
||
|
2D |
6F |
70 |
65 |
72 |
61 |
74 |
6F |
72 |
33 |
03 |
63 |
||
|
6F |
6D |
00 |
09 |
89 |
0A |
90 |
31 |
03 |
37 |
70 |
38 |
||
|
06 |
33 |
60 |
36 |
08 |
0C |
9A |
0D |
55 |
44 |
4F |
11 |
||
|
4F |
54 |
53 |
31 |
00 |
0E |
55 |
64 |
6F |
11 |
70 |
61 |
||
|
73 |
73 |
77 |
6F |
72 |
64 |
31 |
00 |
82 |
43 |
10 |
AB |
||
|
08 |
03 |
77 |
61 |
70 |
0D |
42 |
32 |
43 |
2D |
6F |
70 |
||
|
65 |
72 |
61 |
74 |
6F |
72 |
33 |
03 |
63 |
6F |
6D |
00 |
||
|
09 |
89 |
0A |
90 |
31 |
03 |
37 |
70 |
38 |
06 |
33 |
60 |
||
|
36 |
08 |
0C |
9A |
0D |
55 |
44 |
4F |
11 |
4F |
54 |
53 |
||
|
32 |
00 |
0E |
55 |
64 |
6F |
11 |
70 |
61 |
73 |
73 |
77 |
||
|
6F |
72 |
64 |
32 |
00 |
83 |
3C |
20 |
31 |
37 |
30 |
2E |
||
|
31 |
38 |
37 |
2E |
35 |
31 |
2E |
35 |
00 |
21 |
85 |
23 |
||
|
39 |
32 |
30 |
31 |
00 |
24 |
CB |
19 |
9C |
1A |
67 |
61 |
||
|
74 |
65 |
77 |
61 |
79 |
11 |
75 |
73 |
65 |
72 |
39 |
00 |
||
|
1B |
67 |
61 |
74 |
65 |
77 |
61 |
79 |
11 |
70 |
61 |
73 |
||
|
73 |
77 |
6F |
72 |
64 |
39 |
00 |
|||||||
The UICC is installed into the Terminal and the user hasn’t specified a default MMS connectivity parameter set.
8.3.3.4.2 Procedure
a) The Terminal is powered on and the PIN shall be entered.
b) When the Terminal is in idle mode the user shall generate an MM using the MMS User Agent on the Terminal with the default MMS connectivity parameter set and send it to "+0123456789". If no MMS Relay/Server is available for this parameter set, the next MMS connectivity parameter set offered by the MMS User Agent shall be used to send the MM.
8.3.3.5 Acceptance criteria
After step b) the Terminal shall have sent the MM to "+0123456789" using the first supported MMS connectivity parameter set, which can be used to access an available MMS Relay/Server and is stored in EFMMSICP.
8.3.4 Usage of MMS notification
8.3.4.1 Definition and applicability
An MMS User Agent shall use the MMS related information stored in the USIM, if present, unless otherwise specified by the user. This information comprises MMS connectivity information, MMS user preferences and MMS notifications. MMS notifications should be stored on the USIM together with an associated status by a MMS User Agent according to TS 23.140 [23].
8.3.4.2 Conformance requirement
A Terminal supporting MMS notification storage on the USIM shall store MMS notifications together with an associated status on the USIM.
– TS 31.102 [4], clauses 4.2.67 and 5.3.29;
– TS 23.140 [23], clauses 7.1.12, 7.1.14, 8.1.4 and Annex F.
8.3.4.3 Test purpose
To verify that the Terminal stores and updates MMS notifications with the associated status on the USIM correctly.
8.3.4.4 Method of test
8.3.4.4.1 Initial conditions
Two MMS Relays/Servers are available:
MMS Relay/Server 1:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator1.com"
Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+496998625"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "B2B_OTS1"
Authentication pw: "B2B_password1"
Gateway
Address: "170.187.51.3"
Type of address: "Ipv4"
Port: "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user1"
Authentication pw: "gateway_password1"
MMS Relay/Server 2:
MMS Connectivity Parameters
MMS implementation information: "WAP"
MMS Relay/Server
MMS Relay/Server information: "http://mms-operator1.com"
Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2B-operator1.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "B2B_OTS1"
Authentication pw: "B2B_password1"
Gateway
Address: "170.187.51.3"
Type of address: "Ipv4"
Port: "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user1"
Authentication pw: "gateway_password1"
The default UICC is used with the following exceptions:
EFUST (USIM Service Table)
Logically: Local Phone Book available
User controlled PLMN selector available
Fixed dialling numbers available
Barred dialling numbers available
The GSM Access available
The Group Identifier level 1 and level 2 not available
SMS available
SMS Status available
Service no. 33 (Packed Switched Domain) shall be set to ‘1’
Service no. 52 Multimedia Messaging Service available
Service no. 53 Extension 8 available
Service no. 55 MMS User Connectivity Parameters not available
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
|
Binary |
xx1x xx11 |
x11x xxxx |
xxxx 1×00 |
xxxx x1xx |
xxxx xxx1 |
xxxx xxxx |
x0x1 1xxx |
EFMMSN
Logically:
MMS Status: Free space
MMS Implementation : "00"
MMS Notification: "FF FF … FF" (251 bytes)
Extension file record number: "FF"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
… |
B254 |
B255 |
|
00 |
00 |
00 |
FF |
FF |
FF |
FF |
EFMMSUP
Logically:
MMS Implementation
MMS implementation information: "WAP"
MMS User Preference Profile Name: "Greeting cards"
MMS User Information Preference Information
Visibility: "hide"
Delivery report: "yes"
Read-reply: "yes"
Priority: "normal"
Delivery-Time:
Value (absolute): "1-Jan-2003, 12:00:00 AM GMT"
Expiry:
Value (relative): 1104537600 seconds
|
Coding: |
80 |
01 |
01 |
81 |
0E |
47 |
72 |
65 |
65 |
74 |
69 |
6E |
|
67 |
20 |
63 |
61 |
72 |
64 |
73 |
82 |
19 |
14 |
80 |
06 |
|
|
80 |
10 |
80 |
0F |
81 |
07 |
07 |
80 |
05 |
00 |
3E |
12 |
|
|
2F |
80 |
08 |
06 |
81 |
04 |
41 |
D5 |
E8 |
00 |
EFMMSICP
Logically:
MMS Connectivity Parameters
MMS Implementation
MMS Implementation Information : "WAP"
MMS Relay/Server
MMS Relay/Server Address "http://mms-operator1.com"
1st Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+496998625"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "B2B_OTS1"
Authentication pw: "B2B_password1"
2nd Interface to Core Network and Bearer
Bearer: "GSM-CSD"
Address: "+496998626"
Type of address: "E164"
Speed: "Autobauding"
Call type: "ANALOG_MODEM"
Authentication type: "PAP"
Authentication id: "B2C_OTS2"
Authentication pw: "B2C_password2"
3rd Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2B-operator1.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "B2B_OTS1"
Authentication pw: "B2B_password1"
4th Interface to Core Network and Bearer
Bearer: "GSM-GPRS"
Address: "wap.B2C-operator1.com"
Type of address: "APN"
Call type: "ANALOG_MODEM"
Delivery of erroneous SDU: "No"
Residual Bit Error Rate: "1*10-5"
SDU-Error-Ratio: "1*10-6"
Traffic-class: "Interactive class"
Maximum bit rate for downlink: "8 kbps"
Authentication type: "PAP"
Authentication id: "B2C_OTS2"
Authentication pw: "B2C_password2"
Gateway:
Address: "170.187.51.3"
Type of address: "Ipv4"
Port: "9201"
Service: "CO-WSP"
Authentication type: "HTTP BASIC"
Authentication id: "gateway_user1"
Authentication pw: "gateway_password1"
|
Coding: |
AB |
82 |
01 |
47 |
80 |
01 |
01 |
81 |
18 |
68 |
74 |
74 |
|
70 |
3A |
2F |
2F |
6D |
6D |
73 |
2E |
6F |
70 |
65 |
72 |
|
|
61 |
74 |
6F |
72 |
31 |
2E |
63 |
6F |
6D |
82 |
2F |
10 |
|
|
AA |
08 |
2B |
34 |
39 |
36 |
39 |
39 |
38 |
36 |
32 |
35 |
|
|
00 |
09 |
87 |
25 |
C5 |
0A |
90 |
0C |
9A |
0D |
42 |
32 |
|
|
42 |
11 |
4F |
54 |
53 |
31 |
00 |
0E |
42 |
32 |
42 |
11 |
|
|
70 |
61 |
73 |
73 |
77 |
6F |
72 |
64 |
31 |
00 |
82 |
2F |
|
|
10 |
AA |
08 |
2B |
34 |
39 |
36 |
39 |
39 |
38 |
36 |
32 |
|
|
36 |
00 |
09 |
87 |
25 |
C5 |
0A |
90 |
0C |
9A |
0D |
42 |
|
|
32 |
43 |
11 |
4F |
54 |
53 |
32 |
00 |
0E |
42 |
32 |
43 |
|
|
11 |
70 |
61 |
73 |
73 |
77 |
6F |
72 |
64 |
32 |
00 |
82 |
|
|
43 |
10 |
AB |
08 |
03 |
77 |
61 |
70 |
0D |
42 |
32 |
42 |
|
|
2D |
6F |
70 |
65 |
72 |
61 |
74 |
6F |
72 |
31 |
03 |
63 |
|
|
6F |
6D |
00 |
09 |
89 |
0A |
90 |
31 |
03 |
37 |
70 |
38 |
|
|
06 |
33 |
60 |
36 |
08 |
0C |
9A |
0D |
42 |
32 |
42 |
11 |
|
|
4F |
54 |
53 |
31 |
00 |
0E |
42 |
32 |
42 |
11 |
70 |
61 |
|
|
73 |
73 |
77 |
6F |
72 |
64 |
31 |
00 |
82 |
43 |
10 |
AB |
|
|
08 |
03 |
77 |
61 |
70 |
0D |
42 |
32 |
43 |
2D |
6F |
70 |
|
|
65 |
72 |
61 |
74 |
6F |
72 |
31 |
03 |
63 |
6F |
6D |
00 |
|
|
09 |
89 |
0A |
90 |
31 |
03 |
37 |
70 |
38 |
06 |
33 |
60 |
|
|
36 |
08 |
0C |
9A |
0D |
42 |
32 |
43 |
11 |
4F |
54 |
53 |
|
|
32 |
00 |
0E |
42 |
32 |
43 |
11 |
70 |
61 |
73 |
73 |
77 |
|
|
6F |
72 |
64 |
32 |
00 |
83 |
3C |
20 |
31 |
37 |
30 |
2E |
|
|
31 |
38 |
37 |
2E |
35 |
31 |
2E |
33 |
00 |
21 |
85 |
23 |
|
|
39 |
32 |
30 |
31 |
00 |
24 |
CB |
19 |
9C |
1A |
67 |
61 |
|
|
74 |
65 |
77 |
61 |
79 |
11 |
75 |
73 |
65 |
72 |
31 |
00 |
|
|
1B |
67 |
61 |
74 |
65 |
77 |
61 |
79 |
11 |
70 |
61 |
73 |
|
|
73 |
77 |
6F |
72 |
64 |
31 |
00 |
EFEXT8
Logically:
At least 10 records.
Record 1 to 10: Free space with 253 bytes for extension data
Record 1:
|
Coding: |
B1 |
B2 |
B3 |
B4 |
… |
… |
B255 |
|
Hex |
00 |
FF |
FF |
FF |
FF |
The UICC is installed into the Terminal and the user hasn’t specified a default MMS connectivity parameter set.
8.3.4.4.2 Procedure
a) The terminal is powered on and the PIN shall be entered.
b) When the terminal is in idle mode a MM shall be sent to the terminal via the MMS Relay/Server 1 or 2, dependent on the bearer supported by the terminal. This MMS Relay/Server shall then generate a notification to the Terminal’s MMS User Agent. With the MM notification the MMS User Agent shall receive a message reference that can be used for retrieving the MM from this MMS Relay/Server.
The MM shall result in a MMS notification with the following predefined values:
X-Mms Message Type: "m-notification-ind" (0x82)
X-Mms-Transaction-ID: "01"
X-Mms-MMS-Version: "1.0"
From: not present (hidden)
Subject: "MM for you"
X-Mms-Content-Location: "http://mms-operator1/MMBox/ID-007-12345678"
c) The user shall read the MMS notification stored on the USIM.
d) The user shall retrieve the MM stored on the MMS Relay/Server used in step b).
e) The user shall forward the MM to "+0123456789" using the default MMS Issuer Connectivity Parameters stored on the USIM.
f) A MM shall be sent to the terminal via the same MMS Relay/Server as in step b). This MMS Relay/Server shall then generate a notification to the Terminal’s MMS User Agent. With the MM notification the MMS User Agent shall receive a message reference that can be used for retrieving the MM from this MMS Relay/Server.
The MM shall result in a MMS notification with the following predefined values:
X-Mms Message Type: "m-notification-ind" (0x82)
X-Mms-Transaction-ID: "02"
X-Mms-MMS-Version: "1.0"
From: "+0987123654"
Subject: "Urgent MM"
X-Mms-Content-Location: "http://mms-operator1/MMBox/ID-007-02468024"
g) The user shall read the MMS notification stored on the USIM.
h) The user shall reject the MM stored on the MMS Relay/Server used in step b).
8.3.4.5 Acceptance criteria
1) After step b) the MMS User Agent on the terminal shall have stored the MMS notification on the USIM with the values defined in step b) of 8.4.4.4.2, the associated status shall have been set to "Used space, notification not read, MM not retrieved" and the MMS User Agent shall indicate to the user that a MMS notification has been received.
2) After step c) the status of the MMS notification stored on the USIM shall have been set to "used space, notification read, MM not retrieved".
3) After step d) the MMS user agent shall have retrieved the MM from the MMS Relay/Server 1 and the status of the MMS notification stored on the USIM shall have either been set to "used space, notification read, MM retrieved" or the MMS notification shall have been deleted and the associated shall have been set to "Free space".
4) After step e) the terminal shall have read the set of MMS Issuer Connectivity Parameters stored first in EFMMSICP and shall have forward the MM to "+0123456789" using the MMS Relay/Server 1. The MMS notification shall have either been set to "used space, notification read, MM forwarded" or the MMS notification shall have been deleted and the associated shall have been set to "Free space".
5) After step f) the MMS User Agent on the terminal shall have stored the MMS notification on the USIM with the values defined in step f) of 8.4.4.4.2, the associated status shall have been set to "Used space, notification not read, MM not retrieved" and the MMS User Agent shall indicate to the user that a MMS notification has been received.
6) After step g) the status of the MMS notification stored on the USIM shall have been set to "used space, notification read, MM not retrieved".
7) After step h) the MMS user agent shall have not retrieved the MM from the MMS Relay/Server 1 and the status of the MMS notification stored on the USIM shall have either been set to "used space, notification read, MM rejected" or the MMS notification shall have been deleted and the associated shall have been set to "Free space".
8.4 UICC presence detection
8.4.1 Definition and applicability
To ensure that the UICC has not been removed during a card session, the Terminal sends in case of inactivity on the UICC-Terminal interface, at frequent intervals, a STATUS command during each call.
This procedure shall be used in addition to a mechanical or other devices used to detect the removal of a UICC.
8.4.2 Conformance requirement
A STATUS command shall be issued within all 30 second periods of inactivity on the UICC-Terminal interface during a call. Inactivity in this case is defined as starting at the end of the last communication or the last issued STATUS command. If no response data is received to this STATUS command, then the call shall be terminated as soon as possible but at least within 5s after the STATUS command has been sent. If the DF indicated in response to a STATUS command is not the same as that which was indicated in the previous response, or accessed by the previous command, then the call shall be terminated as soon as possible but at least within 5 seconds after the response data has been received. Here a call covers a circuit switched call, and/or an active PDP context.
The ME may suspend the UICC presence detection based on STATUS commands in case it has an active PDP context, but has not exchanged any data with the network within a 30s period of inactivity on the UICC-ME interface, and resume it as soon as data is exchanged with the network, sending immediately a new STATUS command.
– TS 31.102 [4], clauses 5.1.9
– ETSI TS 102 221 [5], clause 14.5.2.
8.4.3 Test purpose
1) To verify that there are no periods of inactivity on the UICC‑Terminal interface greater than 30 seconds during a call.
2) To verify that the terminal terminates a call within 5 s at the latest after having received an invalid response to the STATUS command.
8.4.4 Method of test
8.4.4.1 Initial conditions
The terminal shall be connected to the UICC simulator. All elementary files shall be coded as default.
8.4.4.2 Procedure
a) A call shall be set up using the generic call setup for circuit switched call or to activate a PDP context.
NOTE: In case of PDP context for a terminal that supports Rel-12 or later, exchange of data with the network may be required to guarantee the correct result of the test.
b) The UICC simulator shall monitor the time of periods of inactivity on the UICC-Terminal interface.
c) After 3 minutes, the call or PDP context shall be cleared.
d) A call shall be set up using the generic call setup for circuit switched call or to activate a PDP context.
NOTE: In case of PDP context for a terminal that supports Rel-12 or later, exchange of data with the network may be required to guarantee the correct result of the test.
e) After one minute after the call was successfully set up, the UICC simulator shall respond to a STATUS command with the response data indicating a DF different from the current DF.
8.4.5 Acceptance criteria
1) During step b), the time of periods of inactivity on the UICC-Terminal interface shall not be longer than 30 seconds.
2) After step e), the Terminal shall terminate the call or PDP context within 5 s at the latest after having received the wrong response to the STATUS command.
8.5 UICC presence detection when connected to E-UTRAN/EPC
8.5.1 Definition and applicability
To ensure that the UICC has not been removed during a card session, the Terminal sends in case of inactivity on the UICC-Terminal interface, at frequent intervals, a STATUS command during each call or active PDP context.
8.5.2 Conformance requirement
A STATUS command shall be issued within all 30 second periods of inactivity on the UICC-Terminal interface during an active PDP context. Inactivity in this case is defined as starting at the end of the last communication or the last issued STATUS command. If no response data is received to this STATUS command, then the active PDP context shall be terminated as soon as possible but at least within 5s after the STATUS command has been sent. If the DF indicated in response to a STATUS command is not the same as that which was indicated in the previous response, or accessed by the previous command, then the active PDP context shall be terminated as soon as possible but at least within 5 seconds after the response data has been received.
The ME may suspend the UICC presence detection based on STATUS commands in case it has an active EPS bearer context, but has not exchanged any data with the network within a 30s period of inactivity on the UICC-ME interface, and resume it as soon as data is exchanged with the network, sending immediately a new STATUS command.
There is 1:1 mapping between one PDP context and one EPS Bearer.
– TS 31.102 [4], clauses 5.1.9
– ETSI TS 102 221 [5], clause 14.5.2.
– TS 23.060 [25], clause 9.2.1A.
8.5.3 Test purpose
1) To verify that there are no periods of inactivity on the UICC‑Terminal interface greater than 30 seconds during an active PDP context.
2) To verify that the terminal terminates the default EPS Bearer within 5 s at the latest after having received an invalid response to the STATUS command.
8.5.4 Method of test
8.5.4.1 Initial conditions
The terminal is connected to the USIM Simulator and the E-USS/NB-SS.
The default E-UTRAN UICC is used.
8.5.4.2 Procedure
a) The terminal is switched on, performs the Attach procedure to the E-USS/NB-SS and establishes the default EPS bearer.
NOTE: For a terminal that supports Rel-12 or later, exchange of data with the network may be required to guarantee the correct result of the test.
b) The UICC simulator shall monitor the time of periods of inactivity on the UICC-Terminal interface.
c) Step b) shall be performed for 3 minutes.
d) After one minute after the end of step c), the UICC simulator shall respond to a STATUS command with the response data indicating a DF different from the current DF.
8.5.5 Acceptance criteria
1) During step c), the time of periods of inactivity on the UICC-Terminal interface shall not be longer than 30 seconds.
2) After step d), the Terminal shall terminate the default EPS bearer within 5 s at the latest after having received the wrong response to the STATUS command.