gcf edited

Test Case ID Test case Test Case Desc Initial Configuration Test Steps Expected Result

1 IMSI attach

2 IMSI detach MS is in idle mode

3

The MS shall correctly perform IMSI attach when switched on

1. MS should be in an allowed PLMN2. MS is switched ON

1. Check that the MS transmits IMSI attach information when switched on. Monitor the radio output from the MS (this can be done with a simple FM receiver). Confirm this by arranging for the MS to receive an incoming call2. Check that the MS does not display service before it is completely attached to the network3. Check that the MS is able to receive a call immediately (3 seconds) after IMSI Attach

1. MS transmits IMSI attach2. MS displays service after completely camping on to the network3. MS can receive an incoming call after IMSI attach

The MS shall correctly perform the IMSI detach procedure when switched off.

Switch off the MS. Monitor the radio output from the MS (this can be done with a simple FM receiver). Check that the MS transmits IMSI detach information before powering down

MS transmits IMSI detach information before powering down.

Normal Case (No GPRS attach)

The MS can successfully perform a normal location update after camping onto a serving cell with a different LAI.

1. MS is attached in Circuit mode2. MS is not GPRS attached

1. Move the MS from the initial cell into a cell with a different LAI till the MS performs a cell reselection2. The MS shall send a LOCATION UPDATE REPQUEST message to the network. Check whether the “location updating type” parameter holds the “normal” value3. The network shall then send a LOCATION UPDATE ACCEPT message to the MS. This message contains a new TMSI for the MS and the LAI for the new cell4. Check that the MS responds to paging in the new cell by calling the MS

1. MS sends a Location Update Request to the network2. The Location Updating Type parameter holds a normal value3. The network sends a Location Update Accept message to the MS including a new TMSI and LAI4. The MS performs a ‘Normal Location Update’ procedure and receives an incoming call.

4 MS is on an active voice call

5

Handover during an active call

The MS shall correctly perform handover when commanded to by the network.

Move from the coverage area of one cell to another. Ensure that the call is not dropped and that voice transmission is maintained in both directions. This procedure has to cover all the possible scenarios like:1. Operation on different frequency bands2. Handover between different codec types/rates3. Handover between cells with and without frequency hopping4. Handover between synchronised cells and handover between non-synchronised cells5. Handover moving between the coverage areas of two different MSCs6. Any possible combinations of the above.7. Any combination of the above, but with a circuit-switched call in progress for other services, such as data or fax.

1. After the handover, the MS maintains a connection on the traffic channel (speech or data) in both directions2. MS doesn’t drop the call within 30 seconds of the handover.

Normal Location Updating with TMSI

unknown in VLR

The MS successfully performs a normal location update procedure after camping onto a serving cell with a different LAI and a TMSI which us unknown to the VLR.

MS is attached in Circuit mode

1. Move the MS from the initial cell into a cell with a different LAI till the MS performs a cell reselection.2. The MS shall send a LOCATION UPDATE REPQUEST message to the network containing a TMSI which is not known by the network. Check whether the “location updating type” parameter holds the “normal” value.3. Check that the network initiates an Identification Procedure requesting the MS’s IMSI.4. Check that the MS sends its IMSI to the network.5. The network shall then send a LOCATION UPDATE ACCEPT message to the MS. This message contains a new TMSI for the MS and the LAI for the new cell.6. Check that the MS is not indicating loss of coverage.7. Check that the MS responds to paging in the new cell by calling the MS

1. MS sends a Location Update Request containing a TMSI to the network2. The Location Updating Type parameter holds a normal value3. The network initiates an Identification Procedure requesting the IMSI of the MS.4. The network sends a Location Update Accept message to the MS containing a new TMSI and LAI5. MS doesnt indicate loss of coverage6. The MS performs the ‘Normal Location Update’ procedure (including Identification Procedure) without coverage loss indication and receives an incoming call.

6 Normal Operation

7 Reset of T3212

8

The MS successfully performs a periodic location update after the expiry of the T3212 timer.

1. MS is attached in Circuit mode2. MS is in idle mode3. T3212 timer is reset

1. Wait for the T3212 timer to expire, and observe if the MS sends the network a LOCATION UPDATE REQUEST message. Check whether the “location updating type” parameter holds the “periodic updating” value.2. The network shall then send a LOCATION UPDATE ACCEPT message to the MS.3. Check that the MS responds to paging after the Location Update procedure

1. MS sends a Location Update Request message to the network after the T3212 timer expires2. The Location Updating Type parameter holds a periodic updating value3. The network sends a Location Update Accept message to the MS4. The MS performs a ‘Periodic Location Update’ procedure and receives an incoming call.

The MS successfully resets its periodic location update timer T3212.

1. MS is attached in Circuit mode2. MS is in idle mode3. T3212 timer is running

1. Check that T3212 is reset when a LOCATION UPDATING ACCEPT message is received2. Wait for the complete T3212 timer to expire, and observe that the MS does not send a LOCATION UPDATE REQUEST message until T3212 expired. When the MS performs the periodic location update procedure check whether the “location updating type” parameter holds the “periodic updating” value.3. Check that the MS responds to paging after the Location Update procedure

1. T3212 timer is reset when a Location Update Accept message is received2. The MS doesn’t send Location Update Request until the T3212 timer expires3. The Location Updating Type parameter holds a periodic updating value4. The MS receives an incoming call

1. MS is attached in Circuit mode2. MS is in idle mode3. T3212 timer is running4. An Authentication Reject message is received by the MS

1. Check that T3212 is reset when a LOCATION UPDATING ACCEPT message is received2. Wait for the complete T3212 timer to expire, and observe that the MS does not send a LOCATION UPDATE REQUEST message until T3212 expired. When the MS performs the periodic location update procedure check whether the “location updating type” parameter holds the “periodic updating” value.3. Check that the MS responds to paging after the Location Update procedure when an AUTHENTICATION REJECT message is received


9

10

11

1. MS is attached in Circuit mode2. MS is in idle mode3. T3212 timer is running4. An SMS is sent or received on the MS

1. Check that T3212 is reset when a LOCATION UPDATING ACCEPT message is received2. Wait for the complete T3212 timer to expire, and observe that the MS does not send a LOCATION UPDATE REQUEST message until T3212 expired. When the MS performs the periodic location update procedure check whether the “location updating type” parameter holds the “periodic updating” value.3. Check that the MS responds to paging after the Location Update procedure when a SMS is sent or received


1. MS is attached in Circuit mode2. MS is in idle mode3. T3212 timer is running4. A supplementary service procedure is operated at the MS end

1. Check that T3212 is reset when a LOCATION UPDATING ACCEPT message is received2. Wait for the complete T3212 timer to expire, and observe that the MS does not send a LOCATION UPDATE REQUEST message until T3212 expired. When the MS performs the periodic location update procedure check whether the “location updating type” parameter holds the “periodic updating” value.3. Check that the MS responds to paging after the Location Update procedure when a Supplementary Service procedure is operated


1. MS is attached in Circuit mode2. MS is in idle mode3. T3212 timer is running4. A call is setup or received on the MS

1. Check that T3212 is reset when a LOCATION UPDATING ACCEPT message is received2. Wait for the complete T3212 timer to expire, and observe that the MS does not send a LOCATION UPDATE REQUEST message until T3212 expired. When the MS performs the periodic location update procedure check whether the “location updating type” parameter holds the “periodic updating” value.3. Check that the MS responds to paging after the Location Update procedure when a call is set up or received


12

13

MS out of coverage and back in coverage before T3212 expiry

The MS does not reset its periodic location update timer T3212 when it gets out of coverage and back in coverage before T3212 expiry.

1. MS is attached in Circuit mode2. MS is in idle mode3. T3212 timer is running4. Move the MS out of coverage5. The out of coverage should last for 3/4 of the T3212 interval6. Bring the MS back to coverage before T3212 timer expires

1. Move the MS out of coverage (no other network available). The ‘out of coverage time’ should last for ¾ of the interval of T3212.2. Bring the MS back to coverage (same PLMN / Location Area as before) before T3212 expires. When gaining back coverage, check that the MS does not perform a Location Update procedure.3. Wait for the T3212 timer to expire, and observe if the MS sends the network a LOCATION UPDATE REQUEST message. Check whether the “location updating type” parameter holds the “periodic updating” value.4. Check that the MS responds to paging after the Location Update procedure

1. The MS sends a Location Update Request message to the network after the T3212 timer expires2. The Location Updating Type parameter holds a periodic updating value3. The MS receives an incoming call after completing the Location Update procedure

1. MS is attached in Circuit mode2. MS is in idle mode3. T3212 timer is running4. Move the MS out of coverage from the HPLMN but camped on another PLMN5. The MS is on Emergency Camping for atleast 3/4 of the T3212 interval6. Bring the MS back to coverage before T3212 timer expires

1. Move the MS out of coverage (no other network available). The ‘out of coverage time’ should last for ¾ of the interval of T3212.2. Bring the MS back to coverage (same PLMN / Location Area as before) before T3212 expires. When gaining back coverage, check that the MS does not perform a Location Update procedure.3. Wait for the T3212 timer to expire, and observe if the MS sends the network a LOCATION UPDATE REQUEST message. Check whether the “location updating type” parameter holds the “periodic updating” value.4. Check that the MS responds to paging after the Location Update procedure when the MS is performing Emergency Camping on a different PLMN while out of service.

1. The MS sends a Location Update Request message to the network after the T3212 timer expires2. The Location Updating Type parameter holds a periodic updating value3. The MS receives an incoming call after completing the Location Update procedure

14

15

16

MS out of coverage and back in coverage

after T3212 expiry

The MS performs the Periodic Location Update procedure immediately after regaining service when it gets out of coverage and back in coverage after T3212 expiry.

1. MS is attached in Circuit mode2. MS is in idle mode3. T3212 timer is running4. Move the MS out of coverage5. The out of coverage should last longer than the T3212 interval6. Bring the MS back to coverage

1. Move the MS out of coverage (no other network available). The ‘out of coverage time’ should last longer than the interval of T3212.2. Bring the MS back to coverage (same PLMN / Location Area as before) after T3212 expired. When gaining back coverage, check that the MS immediately performs a Location Update procedure.3. Check whether the “location updating type” parameter holds the “periodic updating” value.4. Check that the MS responds to paging after the Location Update procedure

1. The MS performs immediately a Location Update procedure after regaining service.2. The Location Updating Type parameter holds the periodic updating value3. The MS receives an incoming call after each test.

1. MS is attached in Circuit mode2. MS is in idle mode3. T3212 timer is running4. Move the MS out of coverage from the HPLMN but camped on another PLMN5. The MS is on Emergency Camping for a longer interval than the T3212 interval

1. Move the MS out of coverage (no other network available). The ‘out of coverage time’ should last longer than the interval of T3212.2. Bring the MS back to coverage (same PLMN / Location Area as before) after T3212 expired. When gaining back coverage, check that the MS immediately performs a Location Update procedure.3. Check whether the “location updating type” parameter holds the “periodic updating” value.4. Check that the MS responds to paging after the Location Update procedure when the MS is performing Emergency Camping on a different PLMN while out of service

1. The MS performs immediately a Location Update procedure after regaining service.2. The Location Updating Type parameter holds the periodic updating value3. The MS receives an incoming call after each test.

Device selects a prioritised network

(PLMNsel List on the SIM (<=rel98))

Verification that the device correctly selects a designated and prioritised network.

1. SIM has CS/PS enabled for roaming with access to all available networks2. MS is switched-off in Automatic Network Selection mode outside the HPLMN coverage3. MS is powered ON at some location where atleast 2 network providers should be available with signal strength > -85dBm

The device shall select the prioritised network in the EFPLMNsel and ignore non-prioritised PLMNs.

A17

Naresh.Ghanta: What should the testcase look like? Is it necessary for our project? What does this testcase actually mean?

17

18


(User controlled PLMNwAcT List on the SIM/USIM (>=rel99))


1. Preferred network and a second PLMN is available2. SIM has CS/PS enabled with access to all available networks3. MS is switched-off in Automatic Network Selection mode outside the HPLMN coverage4. MS is powered ON at some location where atleast 2 network providers should be available with signal strength > -85dBm

The device shall select the prioritised PLMN network and ignore the non-prioritised PLMNs.


(Operator controlled OPLMNwAcT List on the SIM (>=rel99))


1. Preferred network and a second PLMN is available2. SIM has CS/PS enabled with access to all available networks3. MS is switched-off in Automatic Network Selection mode outside the HPLMN coverage4. MS is powered ON at some location where atleast 2 network providers should be available with signal strength > -85dBm

The device shall select the prioritised PLMN and ignore the non-prioritised PLMNs.

A18


A19


19

20

Device re-selects a prioritised network.

HPLMN Timer expires in a coverage area

with no higher prioritised network

coverage

To identify the behaviour of the device if the HPLMN Search Period Timer expires in an area where no prioritised network is available.

1. The HPLMN Search Period Timer is set to 6 minutes ("01")2. MS is powered ON in Automatic Network Selection mode at some location where atleast 2 network providers should be available with signal strength > -85dBm3. The tester shall wait for a period of time greater than the HPLMN Search Period Timer (EFHPPLMN) to ensure a PLMN background scan is activated

It shall be checked that the device stays after expiry of HPLMN Search Period Timer (EFHPPLMN) on the same VPLMN

Device re-selects a higher prioritised

network when camping on a

prioritised network

To identify the behaviour of the device when it camps on a prioritised network and the HPLMN Search Period Timer (EFHPPLMN) expires in an area were a higher prioritised network is available.

1. The HPLMN Search Period Timer is set to 6 minutes ("01")2. MS is powered ON in Automatic Network Selection mode at some location where atleast 2 network providers should be available with signal strength > -85dBm3. While driving around the coverage of VPLMN A shall loose all radio coverage and camp on to less prioritised VPLMN B4. Drive to a location where VPLMN A and VPLMN B are available5. The tester shall wait for a period of time greater than the HPLMN Search Period Timer (EFHPPLMN) to ensure a PLMN background scan is activated

It shall be checked that the device selects VPLMN A after expiry of HPLMN Search Period Timer (EFHPPLMN).

A20


A21


21

22

23

Device re-selects a higher prioritised

network when camping on a non

prioritised network

To identify the behaviour of the device when it camps on a non prioritised network and the HPLMN Search Period Timer (EFHPPLMN) expires in an area were a higher prioritised network is available.

1. The HPLMN Search Period Timer is set to 6 minutes ("01")2. MS is powered ON in Automatic Network Selection mode at some location where atleast 2 network providers should be available with signal strength > -85dBm3. While driving around the coverage of VPLMN A shall loose all radio coverage and camp on to non prioritised VPLMN B4. Drive to a location where VPLMN A and VPLMN B are available5. The tester shall wait for a period of time greater than the HPLMN Search Period Timer (EFHPPLMN) to ensure a PLMN background scan is activated

It shall be checked that the device selects VPLMN A after expiry of HPLMN Search Period Timer (EFHPPLMN).

Manual Network selection

If in manual network selection mode, the MS shall list all available PLMNs. This behaviour is independent from the content of the preferred PLMN list.

1. MS is switched ON in Automatic Network Selection mode2. Manual Network Selection mode is selected

1. Select the manual network selection mode on the MS and ensure that the list of all available GSM PLMNs is displayed, and that the displayed networks can be selected, even if on the forbidden list. 2. Check that the preferred PLMN list is not changed after the manual network selection.3. Repeat the test with different entries in the preferred PLMN lists, including the empty list and lists of more than 32 entries

1. The MS shall display all available GSM PLMNs and it shall perform manual network selection on the chosen network.2. The preferred PLMN list is not changed after the manual network selection.

Selection mode following switch off

The MS shall be retain its configuration of automatic and manual network selection modes when switched off.

MS is switched ON in Automatic Network Selection mode

Change to manual network selection. Turn the MS off and on again. Check that the manual network selection mode is in use

MS has Manual Network Selection mode in use

A22


24

25

26

MS is switched ON in Manual Network Selection mode

Change to automatic network selection. Turn the MS off and on again. Check that the automatic network selection mode is in use

MS has Automatic Network Selection mode in use

Mobile Originated call complete

MS shall make an outgoing voice call

1. MS is in idle mode2. Attempt to call to an ISDN/ PSTN/ PBX/ Mobile number from the MS

1. Make a voice call to an ISDN number. Ensure that the call completes, and that the distant party receives the correct CLIP information.2. Make a voice call to a PSTN number. Ensure that the call completes.3. Make a voice call to a PBX extension. Ensure that the call completes.4. Make a voice call to a Mobile number. Ensure that the call completes.

Check that Call Waiting Notification, COLP and SS notification (such as "call is forwarded") is correctly displayed and does not disturb the call setup. Check that alerting tone is audible at the MS and that voice connection in both directions is established

1. MS call make voice call to the number, alerting indication is audible, voice connection is successful from both the directions, the call gets completed and the distant party gets the correct CLIP information2. MS displays Call Waiting notification correctly if the user is busy3. COLP is displayed correctly on the MS4. SS notification is correctly displayed on the MS

Mobile originated call to occupied phone

The MS shall make an outgoing voice call to a busy phone and correctly indicate the busy status.

1. MS is in idle mode2. The called busy subscriber should not have Call Waiting services activated

1. Make a voice call to a busy ISDN number. Ensure that the mobile correctly indicates the busy status of the distant party.2. Make a voice call to a busy PSTN number. Ensure that the mobile correctly indicates the busy status of the distant party.3. Make a voice call to a busy PBX extension. Ensure that the mobile correctly indicates the busy status of the distant party.4. Make a voice call to a busy Mobile number. Ensure that the mobile correctly indicates the busy status of the distant party.

Check that SS notification (such as "call is forwarded") is correctly displayed and does not disturb the call setup. Check that busy tone is audible at the MS

The MS can attempt calls to any number correctly, and SS notification information is correctly displayed and that busy indication is audible.

27 MS is in idle mode



Mobile originated call to international B-

subscriber (with "+")

The MS shall correctly make an international call using a number provided in the international format (using the + prefix)

Make a voice call to a number in another country, by using a number including the + international prefix and the full international number.


1. MS can make voice call to a Mobile number, alerting indication is audible, voice connection is successful from both the directions, the call gets completed and the distant party gets the correct CLIP information2. MS displays Call Waiting notification correctly if the user is busy3. COLP is displayed correctly on the MS4. SS notification is correctly displayed on the MS

Make a voice call to a number in the same country as the mobile, by using a number including the + international prefix and the full international number.


1. MS call make voice call to a Mobile number, alerting indication is audible, voice connection is successful from both the directions, the call gets completed and the distant party gets the correct CLIP information2. MS displays Call Waiting notification correctly if the user is busy3. COLP is displayed correctly on the MS4. SS notification is correctly displayed on the MS

Make a voice call to a stored international number, by using a number including the + international prefix and the full international number.




31

32 CLIP status is correctly displayed.

33 CLIR status is correctly displayed.

34 DTMF

Make a voice call to a stored number in the same country as the mobile, by using a number including the + international prefix and the full international number.



Mobile terminated calls

The MS shall present the correct CLIP information on an incoming call from a PSTN phone

1. MS is in idle mode2. Receive a call from an ISDN/ PSTN/ PBX/ Mobile phone

1. Receive a call from an analogue PSTN phone. If CLIP information is available, ensure it is correctly displayed. Answer the call and ensure that a connection has been made. 2. Receive a call from an ISDN phone. Ensure that CLIP information is correctly displayed. Answer the call and ensure that a connection has been made. 3. Receive a call from an PBX extension. Ensure that CLIP information is correctly displayed. Answer the call and ensure that a connection has been made.4. Receive a call from an Mobile phone Ensure that CLIP information is correctly displayed. Answer the call and ensure that a connection has been made.

CLIP information is correctly displayed, alerting indication is audible, and a voice connection in both directions is established when the user answers the call.

Interrogation for the CLIP status (*#30#)

An MS shall permit interrogation of CLIP status

1. MS is in idle mode2. Dial *#30# from the phone and interrogate the CLIP status

1. Dial *#30#, and ensure that the phone correctly indicates the CLIP status.2. Interrogate the CLIP status using the phone menus, and ensure that the phone correctly indicates the CLIP status.

Interrogation for the CLIR status (*#31#)

The MS shall correctly indicate its CLIR status in response to a command from the user.

1. MS is in idle mode2. Dial *#31# from the phone and interrogate the CLIP status

1. Dial *#31#, and ensure that the phone correctly indicates the CLIR status. 2. Repeat procedure 1, but using the phone's menus to send the command.

The MS shall correctly send DTMF digits when engaged in a call.

1. MS is connected to an active voicemail system or other DTMF receiver2. Press any digits from 0-9 or #

1. Check that the voicemail system responds correctly to the digits 0-9, * and #.2. Check by sending DTMF digits stored in the phonebook memory.

The voicemail system responds correctly to the digits sent by the MS.

35

36

Emergency calls, with SIM/USIM, no

emergency number stored

The UE shall make an outgoing emergency call.

1. SIM is inserted in the MS2. No Emergency Number information stored on the SIM3. MS is switched-ON and key pad is unlocked/ locked4. Attempt emergency call to international emergency numbers 112 and 911, national emergency numbers 100, 101, 102, 108, etc. or successively dial 08, 100, 108, 110, 119, etc.

1. Make an emergency call to the international emergency numbers 112 and 9112. Make an emergency call dialling successively 08, 000, 110, 118, 119, 9993. Make an emergency call dialling any other specific national emergency number of the country4. Make an emergency call without dialling any dedicated number, if the UE MMI allows so (such as use of the menu, of a ‘special button’, etc.)

1. The MS shall complete the call correctly, display specific emergency call set-up MMI correctly2. Alerting indication should be audible, and a voice connection in both directions should be established with the emergency services.(No call should be established for the successive dialling of the emergency numbers)

1. SIM is inserted in the MS2. No Emergency Number information stored on the SIM3. MS is switched-ON4. FDN is either activated or deactivated5. Attempt emergency call to international emergency numbers 112 and 911, national emergency numbers 100, 101, 102, 108, etc. or successively dial 08, 100, 108, 110, 119, etc.



37

38

1. SIM is inserted in the MS2. No Emergency Number information stored on the SIM3. MS is switched-ON4. MS camped on a Forbidden PLMN5. Attempt emergency call to international emergency numbers 112 and 911, national emergency numbers 100, 101, 102, 108, etc. or successively dial 08, 100, 108, 110, 119, etc.



1. SIM is inserted in the MS2. No Emergency Number information stored on the SIM3. MS is switched-ON4. IMSI is unknown in HLR5. Attempt emergency call to international emergency numbers 112 and 911, national emergency numbers 100, 101, 102, 108, etc. or successively dial 08, 100, 108, 110, 119, etc.



39

40

1. SIM is inserted in the MS2. No Emergency Number information stored on the SIM3. MS is switched-ON4. PIN1 is blocked5. Attempt emergency call to international emergency numbers 112 and 911, national emergency numbers 100, 101, 102, 108, etc. or successively dial 08, 100, 108, 110, 119, etc.



1. SIM is inserted in the MS2. No Emergency Number information stored on the SIM3. MS is switched-ON4. PUK is blocked5. Attempt emergency call to international emergency numbers 112 and 911, national emergency numbers 100, 101, 102, 108, etc. or successively dial 08, 100, 108, 110, 119, etc.



41

42

Emergency calls, with SIM/USIM, emergency

numbers stored on EFECC

The UE shall make an outgoing emergency call.

1. SIM is inserted in the MS2. Emergency Number information is stored on the SIM3. MS is switched-ON4. PIN protection is activated5. Attempt emergency call to international emergency numbers 112 and 911, national emergency numbers 100, 101, 102, 108, etc. or successivley dial all numbers stored on the SIM or successively dial 08, 100, 108, 110, 119, etc.

1. Make an emergency call to the international emergency numbers 112 and 9112. Make an emergency call dialling successively all numbers stored in SIM/USIM (EFECC)3. Make an emergency call dialling successively 08, 000, 110, 118, 119, 999 except if this number is stored in EFECC4. Make an emergency call dialling any other specific national emergency number of the country5. Make an emergency call without dialling any dedicated number, if the UE MMI allows so (such as use of the menu, of a ‘special button’, etc.)

1. The MS shall complete the call correctly, display specific emergency call set-up MMI correctly2. Alerting indication should be audible, and a voice connection in both directions should be established with the emergency services.(No call should be established for the successive dialling of the emergency numbers but for successive dialling from stored numbers, it will work fine)

1. SIM is inserted in the MS2. Emergency Number information is stored on the SIM3. MS is switched-ON4. PIN protection is activated5. Key pad is locked6. Attempt emergency call to international emergency numbers 112 and 911, national emergency numbers 100, 101, 102, 108, etc. or successivley dial all numbers stored on the SIM or successively dial 08, 100, 108, 110, 119, etc.



43

44

1. SIM is inserted in the MS2. Emergency Number information is stored on the SIM3. MS is switched-ON4. PIN protection is activated5. FDN is activated6. Attempt emergency call to international emergency numbers 112 and 911, national emergency numbers 100, 101, 102, 108, etc. or successivley dial all numbers stored on the SIM or successively dial 08, 100, 108, 110, 119, etc.



1. SIM is inserted in the MS2. Emergency Number information is stored on the SIM3. MS is switched-ON4. PIN protection is activated5. MS camped on FPLMN6. Attempt emergency call to international emergency numbers 112 and 911, national emergency numbers 100, 101, 102, 108, etc. or successivley dial all numbers stored on the SIM or successively dial 08, 100, 108, 110, 119, etc.



45

46

1. SIM is inserted in the MS2. Emergency Number information is stored on the SIM3. MS is switched-ON4. PIN protection is activated5. IMSI is unknown in HLR6. Attempt emergency call to international emergency numbers 112 and 911, national emergency numbers 100, 101, 102, 108, etc. or successivley dial all numbers stored on the SIM or successively dial 08, 100, 108, 110, 119, etc.



1. SIM is inserted in the MS2. Emergency Number information is stored on the SIM3. MS is switched-ON4. PIN protection is activated5. PIN1 is blocked6. Attempt emergency call to international emergency numbers 112 and 911, national emergency numbers 100, 101, 102, 108, etc. or successivley dial all numbers stored on the SIM or successively dial 08, 100, 108, 110, 119, etc.



47

48

49

1. SIM is inserted in the MS2. Emergency Number information is stored on the SIM3. MS is switched-ON4. PIN protection is activated5. PUK is blocked6. Attempt emergency call to international emergency numbers 112 and 911, national emergency numbers 100, 101, 102, 108, etc. or successivley dial all numbers stored on the SIM or successively dial 08, 100, 108, 110, 119, etc.



Emergency calls, without SIM/USIM

The device shall make an outgoing emergency call even without SIM/USIM.

1. No SIM is inserted in the MS2. MS is switched-ON

Attempt emergency call to international emergency numbers 112 and 911, or successively dial 08, 100, 108, 110, 119, etc.

1. The MS shall complete the call correctly, display specific emergency call set-up MMI correctly2. Alerting indication should be audible, and a voice connection in both directions should be established with the emergency services.

Registration without basic service

Registration of the Call Forwarding supplementary services, without reference to a specific Basic Service.

1. MS is in idle mode2. Supplementary service is not registered

1. Dial the code string and check that the mobile displays a response indicating that the service has been registered. Check also that the service has been registered by performing an interrogation.2. Check using menu commands also

1. When attempted to dial the code strings for activating different supplementary services, the MS registers the supplementary service and displays the fact correctly2. The MS also registers supplementary services through menu commands3. The interrogation for supplementary services should return the correct value.

A49

Naresh.Ghanta: Doubt: In previous testcases, successively dialling 08,100,108,110 etc. connection doesn’t get established but in this how does it happen?

A50

Naresh.Ghanta: Doubt: What is provisioned basic service?

50

51

52

53

54

55

56

57

Registration with provisioned basic

service

Registration of the Call Forwarding supplementary services, using a provisioned basic service.

1. MS is in idle mode2. Supplementary service is not registered

1. Dial the code string for a basic service offered by the phone and check that the mobile displays a response indicating that the service has been registered. Repeat for up to three basic services, if offered by the phone. Check also that the service has been registered by performing an interrogation2. Check using menu commands also

1. When attempted to dial the code strings for activating different supplementary services, the MS registers the supplementary service and displays the fact correctly2. The MS also registers supplementary services through menu commands3. The interrogation for supplementary services should return the correct value.

Display message of registered and activated call

forwarding during MOC setup

Display an indication of call forwarding status when making an MOC call

1. MS is in idle mode2. CFU is activated

Make an outgoing call, and check that the call forwarding status is displayed during call setup

The SS status is correctly displayed during MOC setup.

1. MS is in idle mode2. CFB is activated



1. MS is in idle mode2. CFNRy is activated



1. MS is in idle mode2. CFNRc is activated



1. MS is in idle mode2. All conditional CF is activated



Activation without basic service

Activation of call barring services without reference to a specific basic service

1. MS is in idle mode2. Call Barring service is not registered

1. Dial the code string for BAOC *33*PW# (where PW is the current password) and check that the mobile displays a response indicating that the service has been activated. Check also that the service has been activated by attempting to make an outgoing call to a barred number2. Check using menu commands also

1. When attempted to dial the code strings for activating different Call Barring services, the MS displays a response indicating that the service has been activated2. MS indicates barring for outgoing and incoming calls for the respective code strings entered

1. Dial the code string for BOIC *331*PW# (where PW is the current password) and check that the mobile displays a response indicating that the service has been activated. Check also that the service has been activated by attempting to make an outgoing call to a barred number2. Check using menu commands also


58

59

60

61

1. Dial the code string for BOIC-exHC *332*PW# (where PW is the current password) and check that the mobile displays a response indicating that the service has been activated. Check also that the service has been activated by attempting to make an outgoing call to a barred number2. Check using menu commands also


1. Dial the code string for BAIC *35*PW# (where PW is the current password) and check that the mobile displays a response indicating that the service has been activated. Check also that the service has been activated by attempting to make an outgoing call to a barred number. Check that the service has been activated by attempting to make an incoming call from a barred number2. Check using menu commands also


1. Dial the code string for BAIC-R *351*PW# (where PW is the current password) and check that the mobile displays a response indicating that the service has been activated. Check also that the service has been activated by attempting to make an outgoing call to a barred number2. Check using menu commands also


Activation for a provisioned basic

service

Activation of call barring services using a provisioned basic service

1. MS is in idle mode2. Call Barring service is not registered

1. Dial the code string for BAOC with a provisioned basic service *33*PW*BS# (where PW is the current password and BS is the code for the basic service) and check that the mobile displays a response indicating that the service has been activated. Repeat for up to three basic services if implemented on the MS. Check also that the service has been activated by attempting to make an outgoing call to a barred number.2. Check using menu commands as well


62

63

64

65

1. Dial the code string for BOIC *331*PW*BS# (where PW is the current password and BS is the code for the basic service) and check that the mobile displays a response indicating that the service has been activated. Repeat for up to three basic services if implemented on the MS. Check also that the service has been activated by attempting to make an outgoing call to a barred number2. Check using menu commands as well


1. Dial the code string for BOIC-exHC *332*PW*BS# (where PW is the current password and BS is the code for the basic service) and check that the mobile displays a response indicating that the service has been activated. Repeat for up to three basic services if implemented on the MS. Check also that the service has been activated by attempting to make an outgoing call to a barred number2. Check using menu commands as well


1. Dial the code string for BAIC *35*PW*BS# (where PW is the current password and BS is the code for the basic service) and check that the mobile displays a response indicating that the service has been activated. Repeat for up to three basic services if implemented on the MS. Check also that the service has been activated by attempting to make an outgoing call to a barred number2. Check using menu commands as well


1. Dial the code string for BAIC-R *351*PW*BS#2 (where PW is the current password and BS is the code for the basic service) and check that the mobile displays a response indicating that the service has been activated. Repeat for up to three basic services if implemented on the MS. Check also that the service has been activated by attempting to make an outgoing call to a barred number2. Check using menu commands as well



67

68

69

70

Activation without basic service (SIM

without CB)

Activation of call barring services without reference to a specific basic service

1. Dial the code string for BAOC *33*PW# (where PW is the current password) and check that the mobile displays a response indicating that the command has failed.2. Check using menu commands as well

1. When attempted to dial the code strings for activating different Call Barring services, the MS displays a response indicating that the command has failed2. The MS displays the correct status of the call barring service when attempted through menu commands as well

1. Dial the code string for BOIC *331*PW# (where PW is the current password) and check that the mobile displays a response indicating that the command has failed2. Check using menu commands as well


1. Dial the code string for BOIC-exHC *332*PW# (where PW is the current password) and check that the mobile displays a response indicating that the command has failed2. Check using menu commands as well


1. Dial the code string for BAIC *35*PW# (where PW is the current password) and check that the mobile displays a response indicating that the command has failed2. Check using menu commands as well


1. Dial the code string for BAIC-R *351*PW# (where PW is the current password) and check that the mobile displays a response indicating that the command has failed2. Check using menu commands as well


71

72

73

Deactivation without basic service

Deactivation of call barring services without reference to a specific basic service

1. MS is in idle mode2. Call Barring service is activated

1. Dial the code string for BAOC #33*PW# (where PW is the current password) and check that the mobile displays a response indicating that the service has been deactivated. Check also that the service has been deactivated by attempting to make an outgoing call to a previously barred number.2. Check using menu commands as well

1. When attempted to dial the code strings for deactivating different Call Barring services, the MS displays a response indicating that the service has been deactivated2. The MS displays a response indicating that the service has been deactivated when attempted through menu commands as well3. MS permits a call attempt to a previously barred number

1. Dial the code string for BOIC #331*PW# (where PW is the current password) and check that the mobile displays a response indicating that the service has been deactivated. Check also that the service has been deactivated by attempting to make an outgoing call to a previously barred number2. Check using menu commands as well


1. Dial the code string for BOIC-exHC #332*PW# (where PW is the current password) and check that the mobile displays a response indicating that the service has been deactivated. Check also that the service has been deactivated by attempting to make an outgoing call to a previously barred number2. Check using menu commands as well


74

75

76

1. Dial the code string for BAIC #35*PW# (where PW is the current password) and check that the mobile displays a response indicating that the service has been deactivated. Check also that the service has been deactivated by attempting to make an outgoing call to a previously barred number2. Check using menu commands as well


1. Dial the code string for BAIC-R #351*PW# (where PW is the current password) and check that the mobile displays a response indicating that the service has been deactivated. Check also that the service has been deactivated by attempting to make an outgoing call to a previously barred number2. Check using menu commands as well


Deactivation for a provisioned basic

service

Deactivation of call barring services using a provisioned basic service


1. Dial the code string for BAOC with a provisioned basic service #33*PW*BS# (where PW is the current password and BS is the code for the basic service) and check that the mobile displays a response indicating that the service has been deactivated. Repeat for up to three basic services if implemented on the MS. Check also that the service has been deactivated by attempting to make an outgoing call to a previously barred number2. Check using menu commands as well


77

78

79

1. Dial the code string for BOIC #331*PW*BS# (where PW is the current password and BS is the code for the basic service) and check that the mobile displays a response indicating that the service has been deactivated. Repeat for up to three basic services if implemented on the MS. Check also that the service has been deactivated by attempting to make an outgoing call to a previously barred number2. Check using menu commands as well


1. Dial the code string for BOIC-exHC #332*PW*BS# (where PW is the current password and BS is the code for the basic service) and check that the mobile displays a response indicating that the service has been deactivated. Repeat for up to three basic services if implemented on the MS. Check also that the service has been deactivated by attempting to make an outgoing call to a previously barred number2. Check using menu commands as well


1. Dial the code string for BAIC #35*PW*BS# (where PW is the current password and BS is the code for the basic service) and check that the mobile displays a response indicating that the service has been deactivated. Repeat for up to three basic services if implemented on the MS. Check also that the service has been deactivated by attempting to make an outgoing call to a previously barred number2. Check using menu commands as well


80

81 Interrogation

82

83

1. Dial the code string for BAIC-R #351*PW*BS# (where PW is the current password and BS is the code for the basic service) and check that the mobile displays a response indicating that the service has been deactivated. Repeat for up to three basic services if implemented on the MS. Check also that the service has been deactivated by attempting to make an outgoing call to a previously barred number2. Check using menu commands as well


Interrogation of call barring services without reference to a specific basic service


1. When attempted to dial the code strings for interrogating different Call Barring services, the MS displays the correct status of the call barring service2. The MS displays the correct status of the call barring service when attempted through menu commands as well

General deactivation of barring services

Deactivation of all currently activated barring services

1. MS is in idle mode2. One or more Call Barring service is activated

1. Dial the code string #330*PW# (where PW is the current password) and check that the mobile displays a response indicating that all barring services have been deactivated. Check also that the service has been deactivated by attempting to make an outgoing call to a previously barred number2. Check using menu commands as well

1. When attempted to dial the code strings for deactivating all Call Barring services, the MS displays a response that all the Call Barring services have been deactivated2. The MS displays a response that all the Call Barring services have been deactivated when attempted through menu commands as well3. The MS permits a call attempt to or from a previously barred number



84

85 Change of password

86

87



Change of call barring password

1. MS is in idle mode2. Call Barring password is configured

1. Dial the code string *03**OLD* NEW*NEW# (where OLD is the old password and NEW is the new password) and check that the mobile displays a response indicating that the password has been changed2. Change the password using menu commands and check that the mobile displays a response indicating that the password has been changed

1. When attempted to dial the code strings for changing the password for Call Barring services, the MS displays a response that the password has been changed2. The MS displays a response that the password has been changed when attempted through menu commands as well

1. Dial the code string **03**OLD*NEW*NEW# (where OLD is the old password and NEW is the new password) and check that the mobile displays a response indicating that the password has been changed2. Change the password using menu commands and check that the mobile displays a response indicating that the password has been changed


1. Dial the code string *03*330*OLD*NEW*NEW# (where OLD is the old password and NEW is the new password) and check that the mobile displays a response indicating that the password has been changed2. Change the password using menu commands and check that the mobile displays a response indicating that the password has been changed


88

89

90

91

Change of password, old password wrong

Failure of call barring password change caused by wrong old password


1. Dial the code string *03**OLD*NEW*NEW# (where OLD is an incorrect old password and NEW is the new password) and check that the mobile displays a response indicating that the old password was incorrect2. Change the password using menu commands and check that the mobile displays a response indicating that the password has been changed

1. When attempted to dial the code strings for changing the password for Call Barring services, and an incorrect old password is entered, the MS displays a response that the old password is incorrect2. The MS displays a response that the old password is incorrect when attempted through menu commands as well

1. Dial the code string **03**OLD*NEW*NEW# (where OLD is an incorrect old password and NEW is the new password) and check that the mobile displays a response indicating that the old password was incorrect2. Change the password using menu commands and check that the mobile displays a response indicating that the password has been changed


1. Dial the code string *03*330*OLD*NEW*NEW# (where OLD is an incorrect old password and NEW is the new password) and check that the mobile displays a response indicating that the old password was incorrect2. Change the password using menu commands and check that the mobile displays a response indicating that the password has been changed


Change of password; wrong repeating of

new password

Failure of call barring password change caused by wrong repetition of new password


1. Dial the code string *03**OLD*NEW1*NEW2# (where OLD is the old password and NEW1 and NEW2 are different from each other) and check that the mobile displays a response indicating that the new password has not been verified2. Change the password using menu commands and check that the mobile displays a response indicating that the password has been changed

1. When attempted to dial the code strings for changing the password for Call Barring services, new password and confirm new password are different, the MS displays a response that the new password has not been verified2. The MS displays a response that the new password has not been verified when attempted through menu commands as well

92

93

94

95

1. Dial the code string **03**OLD*NEW1*NEW2# (where OLD is the old password and NEW1 and NEW2 are different from each other) and check that the mobile displays a response indicating that the new password has not been verified2. Change the password using menu commands and check that the mobile displays a response indicating that the password has been changed


1. Dial the code string *03*330**OLD*NEW1*NEW2# (where OLD is the old password and NEW1 and NEW2 are different from each other) and check that the mobile displays a response indicating that the new password has not been verified2. Change the password using menu commands and check that the mobile displays a response indicating that the password has been changed


Change of password; new password wrong

(3 digits long)

Failure of call barring password change caused by the new password being too short


1. Dial the code string *03**OLD*NEW*NEW# (where OLD is the old password and NEW is the new password only three digits long) and check that the mobile displays a response indicating that the new password has not been verified2. Change the password using menu commands and check that the mobile displays a response indicating that the password has been changed

1. When attempted to dial the code strings for changing the password for Call Barring services, new password is entered only 3 digits long, the MS displays a response that the new password has not been verified2. The MS displays a response that the new password has not been verified when attempted through menu commands as well

1. Dial the code string **03**OLD*NEW*NEW# (the old password and NEW is the new password only three digits long) and check that the mobile displays a response indicating that the new password has not been verified2. Change the password using menu commands and check that the mobile displays a response indicating that the password has been changed


96

97

98

99

100

1. Dial the code string *03*330*OLD*NEW*NEW# (the old password and NEW is the new password only three digits long) and check that the mobile displays a response indicating that the new password has not been verified2. Change the password using menu commands and check that the mobile displays a response indicating that the password has been changed


Normal operation, waiting call indication

Normal operation of Call Waiting

1. Call waiting service is activated on the MS2. MS is on an active call

Arrange for an incoming call to be received. Ensure that call waiting indication (appropriate tone and display) occurs. Clear the existing call and ensure that the phone alerts after the first call was cleared, and that the waiting call can be accepted

The MS provides an appropriate tone and display, and allows the waiting call to be accepted.

Arrange for an incoming call to be received. Ensure that call waiting indication (appropriate tone and display) occurs. Place the existing call on hold and ensure that the waiting call can be accepted


Arrange for an incoming call to be received. Ensure that call waiting indication (appropriate tone and display) occurs. Have the distant party clear the existing call and ensure that the waiting call can be accepted


Activation without basic service

Activation of Call Waiting without reference to a specific basic service

1. MS is in idle mode2. Call waiting is not activated

1. Dial the code string *43# and check that the mobile displays a response indicating that the service has been activated2. Repeat the procedure using menu commands instead

1. When attempted to dial the code strings for activating the Call Waiting service, the MS displays a response indicating that the service has been activated2. The MS displays a response that the Call Waiting service has been activated when attempted through menu commands as well

101

102 Call Hold Operation of Call Hold MS is on an active voice call The distant party hears the call go on hold

103

104

105

106

107 Multi Party MultiParty call handling All parties can speak to each other

108

109 All parties can speak to each other

110

Deactivation without basic service

Deactivation of Call Waiting without reference to a specific basic service

1. MS is in idle mode2. Call waiting is activated

1. Dial the code string #43# and check that the mobile displays a response indicating that the service has been deactivated2. Repeat procedure 1, but using menu commands instead

1. When attempted to dial the code strings for deactivating the Call Waiting service, the MS displays a response indicating that the service has been deactivated2. The MS displays a response that the Call Waiting service has been deactivated when attempted through menu commands as well

1. Using code 2SEND, place the call on hold, and then retrieve the call using code 1SEND. Check that the distant party heard the call go on hold2. Check using menu commands as well

1. Using code DNSEND (where DN s the number called), place the call on hold and make a second call. Using code 2SEND place the active call on hold and retrieve the held call. Ensure that conversation is possible on the new call2. Check using menu commands as well

The two calls are alternated and conversation is possible on the new call

Check that if the party on hold releases the call, the MS indicates that the call has ended

If the party on hold releases the call, the MS indicates that the call has ended.

Check that is the distant party releases the call during the attempt to retrieve it, the MS indicates that the call has ended

If the distant party releases the call during the attempt to retrieve it, the MS indicates that the call has ended

Check that if distant party releases the active call, the held call can still be retrieved

If the distant party releases the active call, the held call can still be retrieved

MS is active on one call and has one call on hold

Dial the code 3 SEND to join the calls. Check that all three parties can speak to each other

After completing procedure 1, arrange for a further incoming call to be made. Check that the call is indicated, and then answer it, placing the multiparty call on hold (code 2 SEND). Check that conversation is possible on the new call.

An additional incoming call can join the multiparty call already in progress

After completing procedure 2, dial the code 3 SEND to join the calls. Check that all four parties can speak to each other.

After completing procedure 3, place the multiparty call on hold, and make a new outgoing call (DN SEND). Check that conversation is possible on the new call.

Keeping the current multiparty call on hold, another outgoing call can be placed

111


113


115

116

117

118

119

After completing procedure 4, place the new call on hold, and retrieve the multiparty call (2 SEND). Check that conversation is possible between all parties of the multiparty call.

Keeping the new call on hold, the previous mulitparty call can be retrieved

After completing procedure 5, dial the code 3 SEND to join the calls. Check that all five parties can speak to each other.

After completing procedure 6, place the multiparty call on hold, and make a new outgoing call (DN SEND).

Joining the new outgoing call to the previously placed mulitparty call

After completing procedure 7, dial the code 3 SEND to join the calls. Check that all six parties can speak to each other

After completing procedure 8, arrange for a new incoming call to be made, place the multiparty on hold, and accept the new incoming call (2 SEND).

Keeping the current multiparty call on hold, another incoming call can be accepted

After completing procedure 9, dial the code 3 SEND to join the calls. Check that the attempt fails, and that the mobile indicates that the maximum number of participants has been exceeded

When the number of participants has exceeded 6, no new incoming/ outgoing call can be joined with the current multiparty call

After completing procedure 10, create a private communication with one of the distant parties (Code 2X SEND), placing the remainder of the parties on hold. Check that conversation is possible with the chosen party, and that the correct party has been selected.

Private communication with one of the distant party is possible after placing the remainder of the parties on hold

After completing procedure 11, make the distant party release the call during private conversation. Check that the call can be switched back to the multi party call (2 SEND).

Switch between the private party and the remainder parties is possible

After completing procedure 12, select another party for a private conversation (2X SEND) and make this party release the call during the attempt to switch to the private conversation. Check that the call can be switched back to the multi party call (2 SEND).

During switching, if the private party ends the call, then the multiparty call on hold should be retrieved

120

121 Idle mode MO USSD

122

123

124

125

126

After completing procedure 13, have one of the distant parties clear the call. Ensure that the multiparty call is not disturbed for the remaining participants

If one of the distant parties ends the call, the remaining multiparty call should not disconnect

Ensure that MS-initiated USSD operations are carried out correctly.

1. MS is in idle mode2. MMI clock display is enabled3. SMS-CB is enabled

By means of appropriate MMI commands, invoke a USSD request. Check to see whether the network feature invoked responds as expected

USSD request invoked by means of appropriate MMI commands should respond correctly

By means of appropriate MMI commands, invoke a USSD request containing atleast 25 digits

USSD request containing at least 25 digits when invoked by MMI commands should be sent successfully by the MS

By means of appropriate MMI commands, invoke a USSD request that will invoke a network request containing 182 characters (using 7-bit default alphabet)

USSD request that will invoke a network response containing 182 characters (including 7-bit default alphabet) should be displayed completely by the MS

By means of appropriate MMI commands, invoke a USSD string containing an international + symbol

USSD request containing an international '+' symbol should be sent by the MS in the correct sequence

By means of appropriate MMI commands, invoke a USSD string where the total number of characters to be sent equals (8n-1) and there are 7 spare bits at the end of the message

USSD request with the total number of characters equalling (8n-1) and 7 spare bits at the end should be correctly sent by the MS. The MS shall avoid confusing 7 binary zero pad bits as the @ character

By means of appropriate MMI commands, invoke a USSD request that will delay the network response about 60 seconds

MS shall wait for the network's response and shall avoid sending a Release Complete message to the network when an USSD is used that will delay the network response by 60 seconds

127 FDN activated on the MS

128 FDN deactivated on the MS MS should allow to call any numbers

129 Status report

130

Correct operation of FDN

Procedure to check correct operation of FDN

1. Establish a non-FDN call then clear it.2. Set the following conditions and attempt to establish a call for each condition: a. a number is stored in the ADN list b. a number is stored in the last number dialled list c. a number is stored in the missed call list d. a short message is stored which contains a directory number which can be extracted from the message3. Select the FDN option, verify PIN2, enable FDN and enter a valid number in FDN[1], where FDN[1] is not one of the numbers used in 1) or 2) above i.e. ADN, LND, Missed Call List and SMS number. Check that the MS indicates that FDN is active4. Power MS off then on5. Attempt to establish a call to the numbers used in 1) or 2) above. Check that the MS prevents the calls from being set up

MS should only allow to call to the numbers listed in the FDN list

Access the FDN option, deactivate FDN and set up a call to the numbers used in 1) or 2) above. Check that the MS permits the calls to be set up

Enter the status report parameter

1.MS should support status report for a message delivery2. MS is in idle mode

Using MMI commands, set the Status Report in the MS. Send an MO SM with the Status Report parameter included. Check that the message reaches its destination, and that the Status report is returned by the network and correctly received by the MS

Status report is returned by the network and correctly received by the MS after the message reaches its destination

Input SM (160 characters) when

using MMI language of Default 7-bit

alphabet

Ensure that an SMS message of 160 characters can be stored and sent

1. MS is in idle mode2. MMI alphabet is set to default 7-bit coding

Using the MMI procedures defined by the manufacturer, create and send an SMS message of 160 characters. Check that it is correctly received at its destination

The message sent from the MS is correctly received at its destination

131

132

133


Default 7-bit alphabet (over 160 characters)

Ensure that an SMS message longer than 160 characters can be stored and sent. Ensure that the MS correctly displays the number of short messages which are sent. Ensure that the MS actually sends the indicated number of SMS

1. MS is in idle mode2. MMI alphabet is set to default 7-bit coding3. MS supports SMS concatenation

Using the MMI procedures defined by the manufacturer, create and send concatenated SMS messages supporting the text (longer than 160 characters and max. capacity). Check the display if the number of sent messages is indicated and correct. Check that the SMS are correctly received at their destination, and that the entire text (longer than 160 characters and max. capacity) can be read without missing characters or redundancy

1. The MS indicates correctly how many messages are sent2. The messages are correctly received at its destination and the entire text can be read without missing characters or redundancy

Extended default 7-bit alphabet (over 140

Bytes)

Ensure that an SMS message longer than 160 characters can be stored and sentEnsure that the MS correctly displays the number of short messages which are sent. Ensure that the MS actually sends the indicated number of SMS

1. MS is in idle mode2. MMI alphabet is set to default 7-bit coding3. MS supports SMS concatenation

Using the MMI procedures defined by the manufacturer, create and send concatenated SMS messages supporting the text (longer than 140 Bytes and max. capacity). Check the display if the number of sent messages is indicated and correct. Check that the SMS are correctly received at their destination, and that the entire text (longer than 140 Bytes and max. capacity) can be read without missing characters or redundancy


UCS-2 alphabet (over 70 characters)

Ensure that an SMS message longer than 70 UCS-2 characters can be stored and sent. Ensure that the MS displays the number of short messages which are sent. Ensure that the MS actually sends the indicated number of SMS

1. MS is in idle mode2. MMI alphabet is set to UCS-2 character coding3. MS supports SMS concatenation

Using the MMI procedures defined by the manufacturer, create and send concatenated SMS messages supporting the text (longer than 70 UCS-2 characters and max. capacity). Check the display if the number of sent messages is indicated and correct. Check that the SMS are correctly received at their destination, and that the entire text (longer than 70 UCS-2 characters and max. capacity) can be read without missing characters or redundancy


During mobile in idle mode

Ensure that an SMS message can be received while the MS is in idle mode

Arrange for an SMS message (class 2) to be sent to the MS. Check that the message is received and the contents are correctly displayed

The message is received and the contents are correctly displayed



137 MS is in idle mode The SMS is received and stored in the MS

138 MS is in idle mode The SMS is received and stored in the SIM

139

140 Delete SM on the SIM MS is in idle mode

Return call to the originating number

Where the MS has an option to dial the originating number of an SM, ensure that the correct number is dialled

Arrange for an SMS message to be sent to the MS. By means of the MMI commands in the MS, call the originating number. Check that the correct number has been dialled

The SMS is received, and the correct number is dialled

SM class 0 (accept and displayed, but not

stored)

Ensure that a Class 0 SM is accepted and displayed but not stored

Arrange for a Class 0 SM to be sent to the MS. By means of the MMI commands in the MS, display the SM and ensure that it has been correctly received. Turn the MS off and on again, and check that the SM is not in the message storage memory

The SM is received but not stored, and not available after the MS is switched off and on again

SM class 1 (storing in ME and displaying)

Ensure that a Class 1 SM is accepted, displayed and stored in the ME

Arrange for a Class 1 SM to be sent to the MS. By means of the MMI commands in the MS, display the SM and ensure that it has been correctly received. Turn the MS off, and replace the SIM. Turn on the MS and check that the SM is still in the mobile message storage memory. Place the original SIM in another MS and ensure that the message is not in the message storage memory on the new MS

SM class 2 (storing in SIM and displaying)

Ensure that a Class 2 SM is accepted, displayed and stored in the SIM

Arrange for a Class 2 SM to be sent to the MS. By means of the MMI commands in the MS, display the SM and ensure that it has been correctly received. Turn the MS off, and replace the SIM. Turn on the MS and check that the SM is not in the message store. Place the original SIM in another MS and ensure that the message is in the message store on the new MS

Store SM on the SIM; when SIM memory full

Attempt to store a message on the SIM when the SIM memory is full

1. MS is in idle mode2. No memory space is available on the SIM

Create a new MO-SM and attempt to store it on the SIM. Check that the MS responds with a SIM memory full indication and does not overwrite an existing message in the SIM

The MS responds with a SIM memory full indication and does not overwrite an existing message in the SIM

Delete a message from the SIM

Create a new MO-SM and store it on the SIM. Then delete it. Turn off the MS and turn it on again. Check that the SM is no longer stored

The SM is no longer stored on the SIM after being deleted

141 SM Validity Period The SMS message is not delivered

142 During call MS is active on a voice call

143 When out of coverage MS is out of coverage area

Enter the SM Validity period

1. MS is in idle mode2. SMSC supports validity period parameter handling

Using the MMI procedures defined by the manufacturer, enter a valid SM Validity Period. Send an SMS message to another MS. Check the Validity period in the SMSC or via the Status Report facility of the MS and/or the network. Ensure that the receiving MS remains turned off until after the SM Validity Period has expired. When turning on the receiving MS, ensure that the SMS message has not been delivered

Ensure that an SMS message can be sent while the MS is engaged in a call

1. Using the MMI procedures defined by the manufacturer, create and send an SMS message. If the mobile supports EMS all the supported EMS content type shall be tested. Ensure that the message is sent and is correctly received at its destination.2. Repeat procedure 1, but with a Circuit Switched Data Call in progress.3. Repeat procedure 1, but with a FAX Call in progress.4. Repeat procedure 1, but with a GPRS Data Call in progress

The message is sent and is correctly received at its destination when the MS has:1. a Circuit-Switched Data Call in progress2. a FAX Call in progress3. a GPRS Data Call in progress

Ensure that an SMS message can be prepared while the MS is out of coverage, and that the message is sent when the MS returns to the coverage area.

Using the MMI procedures defined by the manufacturer, create and send an SMS message. Move to an area with coverage. Ensure that the message is sent and is correctly received at its destination

The message is sent and is correctly received at its destination

144

145 During call

146

Reception of unsupported SM types

The incoming SM shall not cause the crash of the MS software even if it is not supported or contains invalid information in the standard or in the user data header fields

1. MS is in idle mode2. There are atleast 2 free locations in SM memory

Arrange for all unsupported message type from the list below to be sent to the MS under test. Check that the message is received and the mobile software does not freeze.• 8 bit encoded message• UCS encoded message• Concatenated messages• NOKIA smart messages• ALCATEL TDD messages• SIEMENS OTA messages• Messages that activate / deactivate fax, email, voice mail icons on the MS display• WAP configuration messages

The software of the MS shall not freeze. If applicable the MS shall store the message. The MS may display the text content of the message. If forwarding generally supported the MS shall be able to forward the message

Ensure that an SMS message can be received while the MS is engaged in a call

1. MS is active on a voice call2. There is atleast 1 free location in SM memory

Arrange for an SMS message (class 2) to be sent to the MS. If the mobile supports EMS all the supported EMS content type shall be included in the SM. Check that the message is received and the contents are correctly displayedRepeat this test for the following conditions, if the features are supported1. When the MS is in the active state of a circuit-switched data call2. When the MS is in the active state of a fax call.3. When the MS is sending and receiving data using GPRS (active data transfer).

The message is received and the contents are correctly displayed in each of the following cases:1. MS is in the active state of a Circuit-Switched Data Call2. MS is in the active state of a FAX Call3. MS is in the active state of a GPRS Data Call

Acoustic signal, after new short message (no Class) arrived

Where the MS can be configured to give an acoustic alert when an SM is received, ensure that the alert does in fact occur.

1. MS is in idle mode2. There is atleast 1 free location1 in SM memory

Arrange for an SMS message to be sent to the MS. Check that the message is received and the alert is audible.Repeat this test for the following conditions, if the features are supported1. When the MS is in the active state of a circuit-switched data call.2. When the MS is sending and receiving data using GPRS.

The message is received and the alert is audible in each of the following cases:1. MS is in the active state of a Circuit-Switched Data Call2. MS is in the active state of a GPRS Data Call

147 MS is in idle mode The correct number is dialled by the MS

148 Short Message type 0

149


Call a number included in the text of

the SM

Where the MS has an option to dial a number included in the text of the SM, ensure that the correct number is dialled.

Arrange for an SMS message to be sent to the MS. By means of the MMI commands in the MS, call the number included in the text of the SM. Check that the number which has been dialled was the right one presented by the MMI

Ensure that a type 0 short message is correctly received and acknowledged to the network. This means that:1. the MS is able to receive the type 0 short message irrespective of whether there is memory available in the SIM or ME 2. the MS does not indicate the receipt of the type 0 short message to the user3. the type 0 short message shall not be automatically stored in the SIM or ME.

1. MS is in idle mode2. There is atleast 1 free location1 in SM memory

Arrange for a type 0 SMS message to be sent to the MS. Check that the successful reception of the message is acknowledged to the network. Check that the MS does not indicate the receipt of this message to the user and that the message is not stored in the SIM or ME

The message content shall be discarded but the successful reception of the type 0 SM is acknowledged to the network

1. MS is in idle mode2. There is no free space in the SM memory

Arrange for a type 0 SMS message to be sent to the MS. Check that the successful reception of the message is acknowledged to the network. Check that the MS does not indicate the receipt of this message to the user and that the message is not stored in the SIM or ME

The message content shall be discarded but the successful reception of the type 0 SM is acknowledged to the network

Store MO-SM on the SIM and verify the contents of the SM

data fields on the SIM

Ensure that an outgoing SM is correctly stored on the SIM

Using MMI commands, enter a new MO SM and store it without sending it. Remove the SIM from the MS and check the contents using a SIM reader to ensure that the message is stored in the correct data field in the SIM

The MO SM is stored in the correct data field in the SIM




154 Message storage MS is in idle mode

Store MT-SM (read) on SIM and verify content of the SM

data fields on the SIM

Ensure that a Class 2 MT-SM that has been read is correctly stored on the SIM

Arrange to receive a Class 2 MT-SM. Using MMI commands, display the SM and check that it has been received correctly. Remove the SIM from the MS and check the contents using a SIM reader to ensure that the message is stored in the correct data field in the SIM, with a correct indication of the contents and status of the SM

The MT SM is stored in the correct data field in the SIM, with a correct indication of the contents and status of the SM

Store MT-SM (unread) on SIM and verify

contents of the SM data fields on the SIM

Ensure that a Class 2 MT-SM that has not been read is correctly stored on the SIM

Arrange to receive a Class 2 MT-SM. Without displaying the SM, remove the SIM from the MS and check the contents using a SIM reader to ensure that the message is stored in the correct data field in the SIM, with a correct indication of the contents and status of the SM

The MT SM is stored in the correct data field in the SIM, with a correct indication of the contents and status of the SM

Delete SM on the SIM and verify the

contents of the SM data fields on the SIM

Ensure that a Class 2 MT-SM that has been read and deleted is correctly removed from the SIM (to be checked by a SIM reader)

Arrange to receive a Class 2 MT-SM. Using MMI commands, display the SM and check that it has been received correctly, and then delete the SM. Remove the SIM from the MS and check the contents using a SIM reader to ensure that the message has been deleted and no longer remains on the SIM

The message is deleted and no longer remains on the SIM

Ensure that it is possible to include all the characters of the extended default 7-bit alphabet when creating a new SM, depending on which characters of the extended default alphabet are claimed to be supported by the mobile phone

Using MMI commands, create a message containing all the characters of the extended default 7-bit alphabet (such as ‘^, {, }, \, |, [, ~, ], €’), and store the message. Retrieve the message and ensure that the characters are correctly displayed.The maximum depends on the combination of default and extended default 7-bit characters based on the following rule:N <= 140Byteswith N=2X+Y, (X: extended default 7-bit character, Y: default 7-bit character) can be written in one SMS

The extended default 7-bit characters (such as ^, {, }, \, |, [, ~, ], € ) are correctly displayed in the retrieved message

155 Message transmission MS is in idle mode

156 Message reception MS is in idle mode

157 Character Counter MS is in idle mode

158 Message storage MS is in idle mode

Ensure that all the characters of the extended default 7-bit alphabet are correctly transmitted in an SM as claimed to be supported by the mobile phone

Using MMI commands, send the message created in the previous test to another MS. Ensure that the message is correctly received, and that all the characters (such as ‘^, {, }, \, |, [, ~, ], €’) are correctly displayed, matching the characters entered.The maximum depends on the combination of default and extended default 7-bit characters based on the following rule:N <= 140Byteswith N=2X+Y, (X: extended default 7-bit character, Y: default 7-bit character) can be written in one SMS

The message is correctly received, and all the characters extended default 7-bit characters (such as ^, {, }, \, |, [, ~, ], € ) are correctly displayed, matching the characters entered

Ensure that all the characters of the extended default 7-bit alphabet are correctly received and displayed in an SM, depending on which characters of the extended default alphabet are claimed to be supported by the mobile phone

Arrange for an SM containing all the characters of the extended default 7-bit alphabet to be sent from another MS. Ensure that the message is correctly received, and that all the characters (such as ‘^, {, }, \, |, [, ~, ], €’) are correctly displayed, matching the characters entered

The message is correctly received, and all the characters extended default 7-bit characters (such as ^, {, }, \, |, [, ~, ], € ) are correctly displayed, matching the characters entered

Ensure that character counter increments/decrements correctly 2 digits when typing a SMS using an extended default 7-bit character

Write a SMS with at least one extended default 7-bit character. The character counter should increment/decrement correctly by 2 digits per extended default 7-bit character. Check that the maximum of 80 extended default 7-bit characters can be written in one SMS

The counter will increment/decrement correctly when using extended default 7-bit characters and the maximum of 80 default 7-bit characters can be written in one SMS

Ensure that it is possible to include all the characters of the UCS-2 alphabet when creating a new SM, depending on which characters of the default alphabet are claimed to be supported by the mobile phone

Using MMI commands, create a message containing all the characters of the UCS-2 alphabet, and store the message. Retrieve the message and ensure that the characters are correctly displayed

The characters are correctly displayed in the retrieved message

159 Message transmission MS is in idle mode

160 Message reception MS is in idle mode

161 Character Counter MS is in idle mode

Ensure that all the characters of the UCS-2 alphabet are correctly transmitted in an SM as claimed to be supported by the mobile phone

Using MMI commands send the message created in the previous test to another MS. Ensure that the message is correctly received, and that all the characters are correctly displayed, matching the characters entered

The message is correctly received, and all the characters are correctly displayed, matching the characters entered

Ensure that all the characters of the UCS-2 alphabet are correctly received and displayed in an SM, depending on which characters of the default alphabet are claimed to be supported by the mobile phone

Arrange for an SM containing all the characters of the UCS-2 alphabet to be sent from another MS. Ensure that the message is correctly received, and that all the characters are correctly displayed, matching the characters entered

The message is correctly received, and all the characters are correctly displayed, matching the characters entered

Ensure that character counter increments/decrements correctly when typing a SMS using a UCS-2 character

Write a SMS with at least one UCS-2 character. The character counter should increment/decrement correctly. Check that the maximum of 70 UCS-2 characters can be written in one SMS

The counter will increment/decrement correctly when using UCS-2 characters and the maximum of 70 UCS-2 characters can be written in one SMS

Test Case ID DG 11 Ref. No. Test case Test Case Desc

1 20.3.1

2

Combined Attach and Detach; Successful

The UE shall successfully perform the combined attach

and detach procedures.

3

4 9.2.1

5

6

GPRS Service Indication

(registered to the network)

Ensure that the MS displays the GPRS service indication when it

is attached to the GPRS network and, if automatic

attach is supported, that the registration to the GPRS follows

the GSM registration in an acceptable time

7 9.2.4

8 9.2.5

9

10 9.2.6

11

GSM and GPRS roaming allowed

Verify that the MS handles the roaming procedure correctly

GPRS Attach/ PLMN not allowed

Verify that the MS behaves correctly when the PLMN rejects the GPRS attach

procedure with the cause IMSI unknown in HLR

(Reject Cause #11)

GSM roaming allowed/ GPRS

roaming not allowed in this

PLMN

Verify that the MS correctly handles GPRS roaming not

allowed in this PLMN(Reject Cause #14)

12 9.2.7

13 9.2.8

14 9.4.1

GSM roaming allowed/ GPRS

roaming not allowed

Verify that the MS correctly handles GPRS roaming not

allowed(Reject Cause #7)

GPRS detach scenarios

Verify that during power off and manual requests the MS

performs correctly the operation of GPRS detach.

Verify that after battery removal procedure the MS is able to register to the GPRS

network

MO PDP context activation for

WAP application

Verify that the MS performs correctly the PDP context

activation for WAP(test to be performed with and

without PBCCH)

15 9.4.2

16 9.4.3

17 9.4.4

18 9.5.1

MO PDP context activation for

Modem application


activation for Modem applications

(test to be performed with and without PBCCH)

Two simultaneous MO PDP context

activations


activation for WAP and Modem applications simultaneously

PDP context modification

Verify the behaviour of the MS upon receipt of a “modify PDP

context request” message(the trigger of this message

depends on the network implementation)

Manual MO PDP context

deactivation

Verify that the MS performs correctly the manual PDP

context deactivation procedure

19 9.5.2

20 9.5.3

21 10.1.1

22 10.1.2

23 10.1.3

No MO PDP context

deactivation without user

action

Verify that the MS doesn’t deactivate the PDP context by

itself (without user action)

Network initiated PDP context deactivation

To verify that the MS performs correctly the PDP context

deactivation when it receives the appropriate network

command

Stationary Downlink

Throughput

Verify the downlink data throughput of EGPRS

implementation in live networks

Stationary Downlink Data

Transfer StabilityVerify the stability of EGPRS MS during downlink data transfer

Stationary Uplink Throughput

Verify the uplink data throughput of EGPRS

implementation in live networks

24 9.8.3.1

25 9.8.3.2

Reselection with no GPRS data

transfer(Idle Mode Circuit

Switched 2G Reselection

Packet Attached (No PDPc))

The device should perform a reselection as expected

Idle Mode Circuit Switched 2G Reselection

Packet Attached (PDPc Active, No

Data Transfer)

The device should perform a reselection as expected

26 9.8.4.1

27 25.1.3.2 PIN1 handling

28 25.1.3.3 PIN2 handling

29 25.1.2.1

GPRS Reselection while

Transmitting DataThe device should perform a

reselection as expected

PIN1 handling in UICC with USIM

PIN2 handling in UICC with USIM

Read SMSP(Short Message

Service Parameter)

Procedure for testing support of Short message service

parameters already stored on the UICC with USIM

B31

Naresh.Ghanta: What should the testcase look like? Is it necessary for testing for our project?

30 25.1.2.2

31 25.1.4.1

32 25.3.2

33 25.4.2.1

Write SMSP (e.g. check correct

storing of SMSP parameters)

Procedure for testing support of storing Short message

service parameters on the UICC with USIM

Reading/ Writing/ Deleting ADNs

Procedure for reading, storing and deleting of alpha

identifiers and BCD numbers on the UICC with USIM’s phone

book

MSISDN saved on USIM

Procedure for testing support of MSISDN entries

Terminals using ICC/UICC with

SIM in 3G network

Test the terminals with ICCs with SIM and UICCs with SIM but no USIM in 3G networks which allow the use of a SIM

B32


B33


B34


34 43.1.1.1

35 43.1.1.2

36 43.1.1.3

MMS Mobile Originated with

different MSISDN address formats

Verification that the MS sends correctly the message, when

the international, the national and the short MSISDN address

formats are used

Send MMS when the sender is anonymous

Verification that the MS correctly sends an anonymous

MMS

Send message with MSISDN

recipient using the “To”, the “Cc” or the “Bcc” field

Verification that the MS correctly sends the message

when one of the “To” , the “Cc” or the “Bcc” address fields is

used

37 43.1.1.4

38 43.1.1.5

39 43.1.1.6

Send message with email

recipient using the “To”, the “Cc” or the “Bcc” field


when the “To”, the “Cc” or the “Bcc” address field is used to

insert the email address format

Send message with multiple

recipients

Verification that it is possible to send a MMS to more than one

recipient

Send message with multiple and

unsubscribed recipient

Verification that the MMS will be sent, when a legacy user

and an MMS unsubscribed user is inserted as recipient

40 43.1.2.1

41 43.1.2.2

42 43.1.2.3

43 43.1.2.4

44 43.1.2.5

Send message with subject (maximum

length)

Verification that the maximum length of the subject field is

correctly supported

Send message with text

(maximum length)

Verification that the maximum length of the text field is

correctly supported

Send message with sound object

(iMelody)

Verification that the sound object “iMelody” is correctly

supported

Send message with polyphonic

sound object (MIDI)

Verification that the polyphonic sound object “MIDI” is

correctly supported

Send message with AMR sound

Verification that the AMR sound object is correctly

supported

45 43.1.2.6

46 43.1.2.7

47 43.1.2.8

48 43.1.2.9

Send message with GIF image (different sizes)

Verification that different GIF images are correctly supported

Send message with animated

GIF image (different sizes)

Verification that animated GIF images are correctly supported

Send message with JPEG image (different sizes)

Verification that JPEG images are correctly supported

Send message with WBMP

image (different sizes)

Verification that WBMP images are correctly supported

49 43.1.2.10

50 43.1.2.11

51 43.1.2.12

52 43.1.2.13

Send message with different

objects

Verification that it is possible to send a MMS with different

objects

Send message with Business Card attached

Verification that it is possible to send a MMS with an attached

Business Card

Send message with appointment

attached


appointment from the organizer

Send message with VNotes

attached


VNote from the organizer

53 43.1.2.14

54 43.1.2.15

55 43.1.3.1

Send message with different

objects to email client

Verification that it is possible to send a MMS with different objects to an email client

Send message with Business Card to email

client


Business Card to an email client

Send message with NORMAL

priority

Verification that the MMS priority is correctly supported

by the MS

56 43.1.3.2

57 43.1.3.3

58 43.1.4.1

59 43.1.4.2

Send message with LOW priority


by the MS

Send message with HIGH priority


by the MS

Reply to message with single recipient

Verification that the MS correctly supports the reply to a MMS with a single recipient

Reply to message with multiple

recipients

Verification that the MS correctly supports the reply to a MMS with multiple recipients

60 43.1.4.3

61 43.2.1.1

62 43.2.1.2

Forward a received message

Verification that the MS correctly supports the

forwarding of a received MMS

Receive MMS notification with

message size indicated

Verification that the MS correctly supports the MMS notification with indicated

message size

Receive message from MSISDN

sender using the “To”, the “Cc” or

the “Bcc” field

Verification that the MS correctly supports the receiving

of a MMS from a MSISDN sender using the “To”, “Cc” or

“Bcc” address field

63 43.2.1.3

64 43.2.1.4

65 43.2.2.1

66 43.2.2.2

Receive message from email client

Verification that the MS correctly supports the receiving of a MMS from an email client

Receive message to multiple

recipients using the fields “To”, “Cc” and “Bcc”


of a MMS with multiple recipients using the fields “To”,

“Cc” and “Bcc”

Receive message with subject (maximum

length)

Verification that the MS correctly supports the receiving of a MMS containing a subject

with maximum length

Receive message with text

(maximum length)


of a MMS containing a text with maximum length

67 43.2.2.3

68 43.2.2.4

69 43.2.2.5

Receive message with sound object

(iMelody)


of a MMS containing an iMelody sound object

Receive message with polyphonic

sound object (MIDI)


of a MMS containing a MIDI sound object

Receive message with AMR sound

object


of a MMS containing an AMR sound object

70 43.2.2.6

71 43.2.2.7

Receive message with GIF image (different sizes)


of a MMS containing a GIF image

Receive message with animated

GIF image (different sizes)


of a MMS containing an animated GIF image

72 43.2.2.8

73 43.2.2.9

74 43.2.2.10

Receive message with JPEG image (different sizes)


of a MMS containing a JPEG image

Receive message with WBMP

image (different sizes)

Verification that the MS correctly supports the receiving of a MMS containing a WBMP

image

Receive message with different

objects

Verification that the MS correctly supports the receiving of a MMS containing different

objects

75 43.2.2.11

76 43.2.2.12

77 43.2.2.13

Receive message with Business Card attached

Verification that the MS correctly supports the receiving of a MMS containing a Business

Card

Receive message with an

appointment attached


of a MMS containing an appointment

Receive message with VNotes

attached


of a MMS containing a Vnote

78 43.2.2.14

79 43.2.3.1

80 43.2.3.2

Receive message with different objects from email client

Verification that the MS correctly supports the receiving of a MMS containing different objects from an email client

Receive message with NORMAL

Priority


of a MMS with “normal” priority

Receive message with LOW Priority


of a MMS with “low” priority

81 43.2.3.3

82 43.2.3.4

83 43.2.4.1

Receive message with HIGH Priority

Verification that the MS correctly supports the receiving of a MMS with “high” priority

Receive message with the MS

profile “Meeting or silence”

Verification that when the profile “Meeting” or “Silence“ is activated in the MS, it shall

not automatically play a sound object of a MMS and that the

MS shall be mute

Receive MMS when Auto

Download is set to “Off“ / Reject

MMS

Verification that when Auto Download is set to “Off“ in the

MS, it shall be possible to reject the receiving of the MMS. The

MS shall not automatically download the MMS

84 43.2.4.2

85 43.2.4.3

86 43.2.4.4

87 43.2.4.5


Download is set to “Confirm”

Verification that when Auto Download is set to “Confirm“ in

the MS, it shall be possible to defer the receiving of the MMS


Download is set to “On”

Verification that when Auto Download is set to “On“ in the MS, the MMS is automatically

downloaded by the MS


Download is set to “On” and the

MS memory is full

Verification that when Auto Download is set to “On“ in the MS and the MS memory is full,

the download of the MMS is automatically deferred by the

MS and an appropriate notification is given to the user


Download is set to “On” and the

sender is anonymous

Verification that when Auto Download is set to “On“ in the

MS and the sender is anonymous, it is possible to

deny the MMS

88 43.2.4.6

89 43.3.1.1

90 43.3.1.2

91 43.3.1.3


Download is set to “Off”

Verification that when Auto Download is set to “Off“ in the MS, it is possible to download

the MMS at a later time

Send MMS with Delivery Report

set to “On“

Verification that the MS correctly supports indicating

the Delivery Report request to the network

Send MMS with Delivery Report

set to “Off“


the Delivery Report request to the network

Receive a Delivery Report when the

MMS was retrieved / Successful

Verification that the MS correctly supports the receipt of the MMS Delivery Report

92 43.3.1.4

93 43.3.1.5

94 43.3.1.6

95 43.3.1.7

Receive a Delivery Report when the

MMS was rejected


Receive a Delivery Report were the

MMS was expired


Receive a Delivery Report when the MMS was sent to

multiple recipients


Receive a Delivery Report when the recipient MSISDN

is directly forwarded to a

different MSISDN


96 43.3.1.8

97 43.3.2.1

98 43.3.2.2

99 49.1.1.1

Deny Delivery Report

Verification that the MS correctly supports the deny of

the MMS Delivery Report

Sending a Message with

Read Reply set to “On”


the Read Reply Report request to the network

Sending a Message with

Read Reply set to “Off”


the Read Reply Report request to the network

Send E-Mail with email recipient using the “To”, the “Cc” or the

“Bcc” field


when the “To”, the “Cc” or the “Bcc” address field is used to

insert the email address format

100 49.1.1.2

101 49.1.1.3

102 49.1.2.1

103 49.1.2.2

Send E-Mail with multiple

recipients

Verification that it is possible to send an e-mail message to

more than one recipient

Send E-Mail to an address book

recipient

Verification that the e-mail will be sent to an address book

recipient

Send E-Mail with subject

(maximum length)

Verification that the maximum length of the subject field is

correctly supported

Send E-Mail with text (maximum

length)

Verification that the maximum length of the text field is

correctly supported

104 49.1.2.3

105 49.1.2.4

106 49.1.2.5

107 49.1.2.6

108 49.1.2.7

Send E-Mail with different objects (iMelody / MIDI /

AMR sound / GIF / Animated

GIF / JPEG / WBMP - max.

size)

Verification that the object “iMelody / MIDI / AMR sound /

GIF / Animated GIF / JPEG / WBMP” with max. size is

correctly supported

Send E-Mail with different objects

Verification that it is possible to send an e-mail with different

objects

Send E-Mail with Business Card

attached

Verification that it is possible to send an E-Mail with an attached Business Card

Send message with appointment

attached

Verification that it is possible to send a e-mail with an attached

appointment from the organizer

Send e-mail with VNotes attached

Verification that it is possible to send an e-mail with an

attached VNote from the organizer

109 49.1.2.8

110 49.1.3.1

111 49.5.1

112 49.5.2

113 49.4.2.1

Send E-Mail with too long mail

address recipient (exceed 255 characters)

Verification that an e-mail with too long e-mail address

recipient (exceeding 255 characters) could not be sent

Send E-Mail with NORMAL / LOW / LOWEST / HIGH / HIGHEST / priority

Verification that the e-mail priority is correctly supported

by the MS

E-Mail Setting with POP3 protocol

Verification that E-Mail settings with POP3 protocol works

properly

E-Mail Setting with IMAP4

protocol

Verification that E-Mail settings with IMAP4 protocol works

properly

Incoming Voice Call during

downloading E-Mail

Verification that it is possible to receive a Voice Call during the download session for e-mail

without losing the e-mail notification

114 49.4.2.2

115 49.4.2.3

116 49.4.2.4

Incoming CS Short Message during downloading E-

Mail

Verification that it is possible to receive a Short Message (CS mode) during the download session for e-mail without

losing the e-mail notification

Incoming E-Mail during an active

call

Verification that it is possible to receive an e-mail notification

during an active call

Receiving an E-Mail during an

active WAP Session

Verification that it is possible to receive an E-Mail notification

during an active call

117 20.6.4 Manual Mode

118 20.6.5

If in manual network selection mode, the UE shall list all

available PLMNs. This behaviour is independent from

the content of the preferred PLMN list

Selection mode following switch

off

The UE shall be retain its configuration of automatic and

manual network selection modes when switched off

Initial Configuration Test Steps

1. MS is powered OFF2. Its the first time the handset attaches on the network, previously it was on some other network

1. Power on the MS2. Verify that the MS sends a combined ATTACH REQUEST to the network3. Check that in the ATTACH REQUEST message, the “Attach type” parameter holds the “Combined GPRS / IMSI attach” value4. Check that in the ATTACH ACCEPT message, the “Attach result“ parameter holds the “Combined GPRS / IMSI attached” value5. Check that in the ATTACH REQUEST message the “type of identity” parameter holds the “IMSI” value

1. MS is powered OFF2. Its not the first time the handset attaches on the network

1. Power on the MS2. Verify that the MS sends a combined ATTACH REQUEST to the network3. Check that in the ATTACH REQUEST message, the “Attach type” parameter holds the “Combined GPRS / IMSI attach” value4. Check that in the ATTACH ACCEPT message, the “Attach result“ parameter holds the “Combined GPRS / IMSI attached” value5. Check that in the ATTACH REQUEST message the “type of identity” parameter holds the “TMSI/ P-TMSI” value6. If the ATTACH ACCEPT contained a new “TMSI/P-TMSI” value, then verify that the UE acknowledges this message by sending an ATTACH COMPLETE. Otherwise, no ATTACH COMPLETE shall be sent

MS is powered ON

Power off the MS and verify that the UE sends a DETACH REQUEST that in the DETACH REQUEST message, the “Detach type” parameter holds the “power switched off, combined GPRS / IMSI detach” value. If the detach is not done at power off, the “Detach type” parameter will hold the “normal, combined GPRS / IMSI detach” value and the network will answer back to the DETACH REQUEST with a DETACH ACCEPT message

1. MS is switched OFF2. MS has a valid IMSI3. The GPRS attach is performed automatically at power ON

1. Switch on the MS. The MS perform the IMSI ATTACH then the GPRS ATTACH2. Observe the elapsed time between the GSM attach and the GPRS one (it must be only few seconds)3. Verify that the GPRS registration status is indicated on the display

1. MS is switched OFF2. MS has a valid IMSI3. The GPRS attach is performed only upon service request i.e. for the establishment of a PDP context and the MS remains attached after PDP context deactivation

1. Switch on the MS. The MS perform the IMSI ATTACH2. Launch the WAP browser, ensure that the operation is successful than quit the browser3. Verify that the GPRS registration status is indicated on the display

1. MS is switched OFF2. MS has a valid IMSI3. The GPRS attach is not automatic

1. Switch on the MS. The MS perform the IMSI ATTACH2. Perform the manual ATTACH through the use of the appropriate AT command (+CGATT) and make sure that the MS executes correctly the requested operation3. Verify that the GPRS registration status is indicated on the display

1. MS is switched OFF2. SIM with GSM and GPRS roaming enabled

Switch on the MS in a roaming network. The MS should perform IMSI and GPRS attach

1. MS is switched OFF2. SIM without a valid IMSI3. Automatic Attach is enabled on the MS

1. Activate the MS and perform a GPRS attach2. Note the display and error message displayed3. Power cycle the MS

1. MS is in idle mode2. SIM without a valid IMSI3. Manual Attach is enabled on the MS

1. Activate the MS and perform a GPRS attach2. Note the display and error message displayed3. Power cycle the MS

1. MS is switched OFF2. SIM with a valid IMSI in the roaming network3. GSM Roaming is enabled in the visited PLMN4. GPRS roaming is not enabled5. Automatic Attach is enabled on the MS

1. The MS is powered on in the HOME PLMN and performs IMSI attach (GSM attach successful) and GPRS attach (GPRS attach successful)2. The MS is moved to the VISITED PLMN and shall attempt to register to the VISITED SGSN (GPRS attach does not succeed)3. The MS is moved back to the HOME PLMN and shall attempt the GPRS attach (GPRS attach successful)

1. MS is in idle mode2. SIM with a valid IMSI in the roaming network3. GSM Roaming is enabled in the visited PLMN4. GPRS roaming is not enabled5. Manual Attach is enabled on the MS

1. The MS is powered on in the HOME PLMN and performs IMSI attach (GSM attach successful) and GPRS attach (GPRS attach successful)2. The MS is moved to the VISITED PLMN and shall attempt to register to the VISITED SGSN (GPRS attach does not succeed)3. The MS is moved back to the HOME PLMN and shall attempt the GPRS attach (GPRS attach successful)

MS is in standby or ready state

1. MS is switched OFF2. SIM with a valid IMSI in the roaming network3. GSM Roaming is enabled in the visited PLMN4. GPRS roaming is not enabled in the VPLMN5. Automatic Attach is enabled on the MS

1. The MS is powered on in the HOME PLMN and performs IMSI attach (GSM attach successful) and GPRS attach (GPRS attach successful)2. The MS is moved to the VISITED PLMN and shall attempt to register to the VISITED SGSN (GPRS attach does not succeed)3. The MS is moved back to the HOME PLMN and shall not attempt the GPRS attach4. The MS is powered off then on. The MS shall perform GSM and GPRS attach successfully

1. MS is switched ON2. MS is GPRS Attached

1. GPRS detach normal (at power off)2. GPRS detach normal (after leaving the WAP browser, if this procedure is foreseen for the MS under test)3. GPRS detach while PDP context activated (through AT command)4. GPRS detach while PDP context activated (battery removal), GPRS attach. Verify that the MS is able to perform the attach procedure correctly5. GPRS detach while transfer being performed (through AT command).6. GPRS detach while transfer being performed (battery removal), GPRS attach

After the GPRS attach try to connect to the WAP network using the WAP browser of the MS



Verify that the MS performs correctly all the operation related to the PDP context activation for modem application with specified APN. Particularly verify the following case: 1. different APN2. different QoS (try to change the QoS and analyze if the MS can support it): The test shall be done changing the reliability class from 3 to 2

1. Activate the first PDP context for WAP application and try to browse in the WAP network2. During this operation try to establish a WEB connection. The MS must be able to manage the two different PDP contexts. Ensure that no error message pass through the Gb interface

MS is in standby or ready state with the PDP context activated

The user must activate a PDP context. A “modify PDP context request” message is then sent to the MS from the SGSN (the trigger of this message depends on the network implementation) with a QoS that is acceptable to the MS


Verify that the MS can do, after manual commands, the PDP context deactivation. Particularly it’s important to verify the following cases:1. Manual MO PDP context deactivation/activation cycle (10s between deactivation and activation) 2. Manual PDP context deactivation/activation cycle (10s between deactivation and activation) while transfer being performed


During several WAP, WEB or FTP session, the MS should not deactivate the PDP context by itself (PDP context should stay active for at least 20min)


If the network sends the PDP context deactivation to the MS, it must perform correctly all the operation related to this command

1. MS is GPRS and IMSI attached2. MS is used in tethered mode as a modem for laptop3. The strong, medium and weak signal areas are identified

1. Activate PDP Context2. Use DOS FTP to download a 1MB file. If possible, utilize a server with minimal latency to the GGSN.3. Repeat the file download 5 times, record the average throughput

1. MS is GPRS and IMSI attached2. MS is used in tethered mode as a modem for laptop3. The medium signal areas are identified

1. Activate PDP Context2. Use DOS FTP to download a 15MB file. 3. After download is complete, start a web browser and go to a few sites4. Repeat steps 1-3 three times

1. MS is GPRS and IMSI attached2. MS is used in tethered mode as a modem for laptop3. The medium signal areas are identified

1. Activate PDP Context2. Use DOS FTP to upload a 1MB file. If possible, utilize a server with minimal latency to the GGSN.3. Repeat the file upload 5 times, record the average throughput4. If extended dynamic allocation is supported, take MS log to verify uplink TS usage and peak/average uplink throughput

1. There must be an appropriate number of 2G cells available on the same PLMN2. The device should be in idle mode3. The device should be IMSI attached, and Packet attached but with no PDP context

Move between the coverage areas of different cells, ideally on a long test route covering the following scenarios:1. Between cells sharing a LAI and RAI2. Between cells sharing a LAI but not sharing RAI3. Between cells not sharing a LAI4. Between cells belonging to the same BSC5. Between cells belonging to different BSCs6. Between cells utilising the same GSM frequency band7. Between cells belonging to differerent GSM frequency bands8. In areas of poor signal strength

1. There must be an appropriate number of 2G cells available on the same PLMN2. The device should be in idle mode3. The device should be IMSI attached, and Packet attached, with a PDP context, but not transmitting any data

Move between the coverage areas of different cells, ideally on a long test route covering the following scenarios:1. Between cells sharing a LAI and RAI2. Between cells sharing a LAI but not sharing RAI3. Between cells not sharing a LAI4. Between cells utilising the same GSM frequency band5. Between cells belonging to differerent GSM frequency bands6. In areas of poor signal strength

MS is in idle mode

MS is in idle mode

SMSP is available

1. There must be an appropriate number of 2G cells available on the same PLMN2. The device should be in idle mode3. The device should be IMSI attached, and Packet attached with a PDP context active

Move between the coverage areas of different cells, ideally on a long test route covering the following scenarios:1. Between cells sharing a LAI and RAI2. Between cells sharing a LAI but not sharing RAI3. Between cells not sharing a LAI4. Between cells belonging to different BSCs5. Between cells utilising the same GSM frequency band6. Between cells belonging to differerent GSM frequency bands7. In areas of poor signal strength

1. Change of PIN12. Change of PIN1, wrong repeating of new PIN13. Change of PIN1, old PIN1 wrong4. Change of PIN1, new PIN1 wrong (3 digits long)5. Deactivation of PIN16. Change of PIN1, when deactivated7. Activation of PIN18. Change of PIN1, when blocked9. Unblocking of blocked PIN1

1. Change of PIN22. Change of PIN2, wrong repeating of new PIN23. Change of PIN2, old PIN2 wrong4. Change of PIN2, new PIN2 wrong (3 digits long)5. Change of PIN2, when blocked6. Unblocking of blocked PIN2

SMSP is available

MS is in idle mode

1. Storage of directory number and name2. Storage of international number ('+')3. Storage of SSC string (including international number: '**21*+49DN#'4 Change directory number and name5. Storage of SIM Data after Location Update accept6. MCC, MNC deleted from forbidden PLMN list7. Storage of SIM Data after LUP reject; IMSI unknown in HLR8. Storage of SIM Data after LUP reject; Authentication error9. Storage of SIM Data after LUP reject; PLMN not allowed10. Storage in forbidden PLMN list without loss of information in list11. Storage of SIM Data after LUP reject; LA not allowed

MS is in idle mode

MS is in idle mode

MS is in idle mode

1. Create a new MMS message, add a MSISDN recipient with the national MSISDN address format (for example: 0172 123456...). Then send the message. The MS displays a message that the MMS has been sent. Verify that the message is correctly received by the B-subscriber2. Repeat the test using the international MSISDN address format (for example: +49 172 123456...)3. Repeat the test using the short MSISDN address format (for example: 1234…)

Create a new MMS and select from the menu option “send as anonymous”. Then send the message. The MS displays a message that the MMS has been sent. Verify that the message will be received and the sender’s address is not visible

1. Create a new MMS message, add a MSISDN recipient only to the “To“ address field. Send the message. The MS displays a message that the MMS has been sent. Verify that the message is correctly received by the B-subscriber2. Repeat the test using only the “Cc” address field3. Repeat the test using only the “Bcc” address field

MS is in idle mode

MS is in idle mode

1. Create a new MMS with a text, picture and sound object, then add an email recipient to the “To” address field. Then send the MMS. The MS displays a message that the MMS has been sent. Verify that the email recipient receives the message and that the address fields and the email body are correctly used2. Repeat the test using the “Cc” address field3. Repeat the test using the “Bcc” address field

Create a new MMS with a text, picture and sound object, add 20 recipients from the phonebook, using both email and phone number address format. Use all three address fields (To, Cc, and Bcc). Send the MMS. The MS displays a message that the MMS has been sent. Verify that the MMS recipients receive the message and that the MMS / email is correctly received

1. MS is in idle mode2. MMS unsubscribed recipient and legacy recipient available

Create a new MMS with a text, picture and sound object, add some recipients from the phonebook. Use all three address fields (To, Cc, and Bcc). Add at least one legacy and one MMS unsubscribed recipient. Send the MMS. For the unsubscribed user the MS displays a message that the Recipient is not subscribed. For the valid recipients the MS displays a message that the MMS has been sent. Verify that the valid MMS recipients receive the message and that the MMS is correctly received

MS is in idle mode

MS is in idle mode

Create a new MMS and insert a text object. Fill the subject field with the maximum length of 40 characters. Send the message. The MS displays a message that the MMS has been sent. Verify that all characters of the subject are sent to the recipient

Create a new MMS and insert a text object. Fill the text object with the maximum length of 1000 characters. Send the message. The MS displays a message that the MMS has been sent. Verify that all characters of the text are sent to the recipient

1. MS is in idle mode2. iMelody available in the sound browser of the MS

Create a new MMS and insert an iMelody sound object. Send the message. The MS displays a message that the MMS has been sent. Verify that the iMelody is played at the recipient while the MMS is viewed and that the sound between the two MSs is comparable

1. MS is in idle mode2. MIDI available in the sound browser of the MS

Create a new MMS and insert a MIDI sound object. Send the message. The MS displays a message that the MMS has been sent. Verify that the MIDI is played at the recipient while the MMS is viewed and that the sound between the two MSs is comparable

1. MS is in idle mode2. AMR sound available in the sound browser of the MS

Create a new MMS and insert an AMR sound object. Send the message. The MS displays a message that the MMS has been sent. Verify that the sound is played at the recipient while the MMS is viewed and that the sound between the two MSs is comparable

1. MS is in idle mode2. GIF image available in the picture browser of the MS

1. Create a new MMS and insert a GIF image object. Send the message. The MS displays a message that the MMS has been sent. Verify that the image can displayed at the recipient while the MMS is viewed2. Repeat the test using different GIF image sizes

1. MS is in idle mode2. An animated GIF image available in the picture browser of the MS

1. Create a new MMS and insert an animated GIF image object. Send the message. The MS displays a message that the MMS has been sent. Verify that the image can displayed and that it is animated at the recipient while the MMS is viewed2. Repeat the test using different animated GIF image sizes

1. MS is in idle mode2. JPEG image available in the picture browser of the MS

1. Create a new MMS and insert a JPEG image object. Send the message. The MS displays a message that the MMS has been sent. Verify that the image can displayed at the recipient while the MMS is viewed2. Repeat the test using different JPEG image sizes

1. MS is in idle mode2. WBMP image available in the picture browser of the MS

1. Create a new MMS and insert a WBMP image object. Send the message. The MS displays a message that the MMS has been sent. Verify that the image can displayed at the recipient while the MMS is viewed2. Repeat the test using different WBMP image sizes

1. MS is in idle mode2. At least 2 different pictures and 2 different sound objects available in the MS

Create a new MMS and insert at least 2 different text, 2 different picture and 2 different sound objects. Send the message. The MS displays a message that the MMS has been sent. Verify that all objects are correctly available at the recipient while the MMS is viewed

1. MS is in idle mode2. A Business Card available in the organiser of the MS

Create a new MMS and attach a Business Card or add a contact from the phonebook as attachment. Send the message. The MS displays a message that the MMS has been sent. Verify that the Business Card can be displayed at the recipient while the MMS is viewed

1. MS is in idle mode2. An appointment is available in the organiser of the MS

Create a new MMS and attach an appointment from the organizer. Send the message. The MS displays a message that the MMS has been sent. Verify that the appointment can be displayed at the recipient while the MMS is viewed

1. MS is in idle mode2. VNote available in the organiser of the MS

Create a new MMS and attach a VNote from the organizer. Send the message. The MS displays a message that the MMS has been sent. Verify that the VNote can be displayed at the recipient while the MMS is viewed

MS is in idle mode

1. MS is in idle mode2. JPEG-, GIF-, WBMP-, AMR- and melody objects are available in the organiser of the MS

1. Create a new MMS with a text object. Send the message to an email recipient. The MS displays a message that the MMS has been sent. Verify that the email recipient receives the message and that the text object is embedded in the email.2. Repeat the test with a JPEG object3. Repeat the test with a GIF object4. Repeat the test with a WBMP object5. Repeat the test with an AMR sound object6. Repeat the test with an iMelody object7. Repeat the test with a MIDI object8. Repeat the test with multiple pages and different objects

1. MS is in idle mode2. A Business Card is available in the organiser of the MS

Create a new MMS and attach a Business Card. Send the message to an email client. The MS displays a message that the MMS has been sent. Verify that the Business Card is attached to email received by the recipient

1. Create a new MMS and set the priority to “normal”. Send the message. The MS displays a message that the MMS has been sent. Verify that the message received by the recipient has “normal” priority2. Repeat the test using an email client as recipient

MS is in idle mode

MS is in idle mode

1. Create a new MMS and set the priority to “low”. Send the message. The MS displays a message that the MMS has been sent at “low” priority. Verify that the message received by the recipient has “low” priority.2. Repeat the test using an email client as recipient

1. Create a new MMS and set the priority to “high”. Send the message. The MS displays a message that the MMS has been sent at “high” priority. Verify that the message received by the recipient has “high” priority2. Repeat the test using an email client as recipient

1. MS in idle mode2. MS received MMS with various email and MSISDN recipients in the “To”-, “Cc”- and “Bcc”-address field in the MMS message store

1. Create a new MMS by replying to one recipient having a MSISDN address. Send the message to an email client. The MS displays a message that the MMS has been sent. Verify that the message is received by the correct recipient2. Repeat the test replying to one recipient having an email address3. Repeat the test replying to one recipient in the “Cc” address field4. Repeat the test replying to one recipient in the “Bcc” address field

1. MS in idle mode2. MS received MMS with various email and MSISDN recipients in the “To”-, “Cc”- and “Bcc”-address field in the MMS message store

Create a new MMS by replying to all recipients. Send the message. The MS displays a message that the MMS has been sent. Verify that the message is received by the previous sender and all recipients in the “To”-, “Cc”- and “Bcc”-address field

MS is in idle mode

1. MS in idle mode2. MS received MMS available in the message store of the MS

1. Receive a new MMS. Display the message and select the “forwarding” function. Enter a new recipient and send the message. Verify that the message will be received by the recipient and that the MMS is marked as being forwarded2. Repeat the test forwarding the message to multiple recipients

1. MS is in idle mode2. Auto Download is set to “Off”

1. Receive a MMS notification of a MMS. The MS shall indicate the MMS notification to the user. Verify that the message size is displayed in the MMS notification. Download the MMS and check whether the real message size of the MMS is the same as it was displayed in the notification2. Repeat the test when having received several MMS notifications without downloading the MMSs. Verify that all individual MMS notifications are saved in the MS and that the individual MMS can be downloaded

1. Receive a MMS from a MS where the “To” address field was used as MSISDN address format. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the sender and the message content is correctly displayed2. Repeat the test receiving a MMS from a MS where the “Cc” address field was used as MSISDN address format3. Repeat the test receiving a MMS from a MS where the “Bcc” address field was used as MSISDN address format

MS is in idle mode

MS is in idle mode

MS is in idle mode

MS is in idle mode

Receive a MMS from an email client. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the sender and the message content is correctly displayed

1. Receive a MMS with multiple recipients in which the test recipient is addressed in the “To” address field. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the sender and the message content is correctly displayed2. Repeat the test receiving a MMS with multiple recipients in which the test recipient is addressed in the “Cc” address field3. Repeat the test receiving a MMS with multiple recipients in which the test recipient is addressed in the “Bcc” address field

Receive a MMS containing a subject field with maximum length of 40 characters. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the subject field is complete and correctly displayed

Receive a MMS containing a text field with maximum length of 1000 characters. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the text field is complete and correctly displayed

MS is in idle mode

MS is in idle mode

MS is in idle mode

Receive a MMS containing an iMelody sound object. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the iMelody sound object is correctly played (i.e. that it is comparable to the sent iMelody) while viewing the MMS. Save the iMelody sound object to the designated data folder of the MS

Receive a MMS containing a MIDI sound object. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the MIDI sound object is correctly played (i.e. that it is comparable to the sent MIDI) while viewing the MMS. Save the MIDI sound object to the designated data folder of the MS

Receive a MMS containing an AMR sound object. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the AMR sound object is correctly played while viewing the MMS. Save the AMR sound object to the designated data folder of the MS

MS is in idle mode

MS is in idle mode

1. Receive a MMS containing a GIF image. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the GIF image is correctly displayed while viewing the MMS. If the GIF image size is exceeding the screen size the MS shall either show a part of the image and provide a scroll option or fit the image to the display screen. Save the GIF image to the designated data folder of the MS2. Repeat this test receiving a MMS with different GIF image sizes

1. Receive a MMS containing an animated GIF image. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the animated GIF image is correctly displayed and animated while viewing the MMS. If the animated GIF image size is exceeding the screen size the MS shall either show a part of the image and provide a scroll option or fit the image to the display screen. Save the animated GIF image to the designated data folder of the MS2. Repeat this test receiving a MMS with different animated GIF image sizes

MS is in idle mode

MS is in idle mode

MS is in idle mode

1. Receive a MMS containing a JPEG image. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the JPEG image is correctly displayed while viewing the MMS. If the JPEG image size is exceeding the screen size the MS shall either show a part of the image and provide a scroll option or fit the image to the display screen. Save the JPEG image to the designated data folder of the MS2. Repeat this test receiving a MMS with different JPEG image sizes

1. Receive a MMS containing a WBMP image. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the WBMP image is correctly displayed while viewing the MMS. If the WBMP image size is exceeding the screen size the MS shall either show a part of the image and provide a scroll option or fit the image to the display screen. Save the WBMP image to the designated data folder of the MS2. Repeat this test receiving a MMS with different WBMP image sizes

Receive a MMS containing at least 2 different text, 2 different picture and 2 different sound objects. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that all objects are correctly available and can be played/displayed while viewing the MMS. Save the objects to their designated data folders of the MS

MS is in idle mode

MS is in idle mode

MS is in idle mode

Receive a MMS with a Business Card attached. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the Business Card is displayed when viewing the MMS. Save the Business Card to the directory of the MS

Receive a MMS containing an appointment. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the appointment is displayed when viewing the MMS. Save the appointment to the organizer of the MS

Receive a MMS containing a VNote. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the VNote is displayed when viewing the MMS. Save the VNote to the organizer of the MS

MS is in idle mode

MS is in idle mode

MS is in idle mode

1. Receive a MMS containing a text object from an email client. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the object is played/displayed when viewing the MMS. Save the object(s) to its/their designated data folder(s) of the MS2. Repeat the test with a JPEG object3. Repeat the test with a GIF object4. Repeat the test with a WBMP object5. Repeat the test with an AMR sound object6. Repeat the test with an iMelody object7. Repeat the test with a MIDI object8. Repeat the test with multiple pages and different objects

1. Receive a MMS with the priority set to “normal”. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the MMS is indicating the priority set to “normal”2. Repeat the test receiving the MMS from an email client

1. Receive a MMS with the priority set to “low”. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the MMS is indicating the priority set to “low”2. Repeat the test receiving the MMS from an email client

MS is in idle mode

1. Receive a MMS with the priority set to “high”. The MS shall indicate the receipt of a new MMS. Open the received message. Verify that the MMS is indicating the priority set to “high”.2. Repeat the test receiving the MMS from an email client

1. MS is in idle mode2. Profile is set to “Meeting” or “Silence”

Receive a MMS containing a sound object. The MS shall indicate the receipt of a new MMS in silent/meeting mode. Open the received message. Verify that the MS is not automatically playing the sound object of the MMS and that the MS is mute

1. MS is in idle mode2. Auto Download is set to “off”

Receive a MMS notification of a MMS. The MS shall indicate the MMS notification to the user:1. Verify that the MS is not automatically downloading the MMS. Reject the receiving of the MMS2. Verify that the MS sends a M_Notify_Resp with X-MMS-Status set to “reject” to the network3. Verify that the MS does not send a new notification for this message to the user

1. MS is in idle mode2. Auto Download is set to “Confirm”

Receive a MMS notification of a MMS. The MS shall indicate the MMS notification to the user:1. Verify that the MS is not automatically downloading the MMS. Defer the receiving of the MMS2. Verify that the MS sends a “defer” message to the network. Download the deferred message from the server. Open the message and verify that the downloaded message is exactly the one which was previously deferred

1. MS is in idle mode2. Auto Download is set to “On”

Receive a MMS notification of a MMS. The MS shall indicate the MMS notification to the user. Verify that the MS is automatically downloading the MMS and after receipt, the message can be displayed by the user

1. MS is in idle mode2. Auto Download is set to “On”, MMS memory of the MS is full

Receive a MMS notification of a MMS. The MS shall indicate that a new MMS is available to the user but that there is not enough memory in the MS to receive the message. Verify that the MS sends a “defer” message to the network. Clear the memory of the MS, then download the deferred message from the server. Open the message and verify that the downloaded message is exactly the one which was previously deferred

1. MS is in idle mode2. Auto Download is set to “On”, Receive option is set to “Deny message when anonymous sender”

Receive a MMS notification of a MMS. The MS shall indicate that a new MMS is available to the user but that the sender is anonymous. Verify that the MS is not automatically downloading the MMS

1. MS is in idle mode2. Auto Download is set to “Off”

Receive a MMS notification of a MMS. The MS shall indicate that a new MMS is available to the user. Verify that the MS is not automatically downloading the MMS but sending a defer message to the network. Download the deferred message from the server. Open the message and verify that the downloaded message is exactly the one which was previously deferred

1. MS is in idle mode2. Delivery report is set to “On” in the MS

Create a new MMS. Send the message using an MSISDN in national format. The MS displays a message that the MMS has been sent. Ensure that the recipient has successfully received the MMS. Verify that the Delivery Report is sent back to the sender of the MMS. Verify that the MS correctly displays the Delivery Report

1. MS is in idle mode2. Delivery report is set to “Off” in the MS

Create a new MMS. Send the message using an MSISDN in national format. The MS displays a message that the MMS has been sent. Ensure that the recipient has successfully received the MMS. Verify that the Delivery Report is sent back to the sender of the MMS. Verify that the MS correctly displays the Delivery Report


Create a new MMS. Send the message. The MS displays a message that the MMS has been sent. Ensure that the recipient has successfully received the MMS. Verify that the Delivery Report is received by the sender of the MMS. Verify that the MS correctly indicates the status of the sent message as “delivered”


Create a new MMS. Send the message. The MS displays a message that the MMS has been sent. Ensure that the recipient rejects the MMS. Verify that the Delivery Report is received by the sender of the MMS. Verify that the MS correctly indicates the status of the sent message as “rejected”


Create a new MMS. Send the message. The MS displays a message that the MMS has been sent. Ensure that the recipient does not receive the MMS and that the MMS delivery timer expires. Verify that then the Delivery Report is received by the sender of the MMS. Verify that the MS correctly indicates the status of the sent message as “Timer expired”


Create a new MMS to multiple recipients. Send the message. The MS displays a message that the MMS has been sent. Ensure that some recipients reject, defer of retrieve the message. Verify that for each recipient the Delivery Report is received by the sender of the MMS. Verify that the MS correctly indicates the various states of the sent message

1. MS is in idle mode2. Delivery Report is set to “On” in the MS3. Recipient has enabled “Directly Forwarding” to another MSISDN

Create a new MMS to multiple recipients. Send the message. The MS displays a message that the MMS has been sent. Ensure that the recipient has retrieved the MMS from the forwarded MSISDN. Verify that the Delivery Report is received by the sender of the MMS. Verify that the MS correctly indicates the status of the sent message as “delivered”

MS is in idle mode

1. MS is in idle mode2. Delivery report is set to “On” in the sending MS3. Deny Delivery Report is set to “on” in the retrieving MS

Retrieve a MMS and verify that the sending MS will not receive a Delivery Report

1. MS in idle mode2. Read Reply Report is set to “On” in the MS

Create a new MMS. Send the message to an MSISDN in national format. The MS displays a message that the MMS has been sent. Ensure that the recipient has successfully received the MMS. When the recipient has read the message, verify that the Read Reply Report is sent back to the sender of the MMS. Verify that the MS correctly displays the Read Reply Report

1. MS in idle mode2. Read Reply Report is set to “Off” in the MS

Create a new MMS. Send the message. The MS displays a message that the MMS has been sent. Ensure that the recipient has successfully received the MMS. When the recipient has read the message, verify that no Read Reply Report is sent back to the sender of the MMS

1. Create a new E-Mail message with a text, then add an email recipient to the “To” address field. Then send the e-mail. The MS displays a message that the e-mail has been sent. Verify that the email recipient receives the message and that the address fields and the email body are correctly used2. Repeat the test using the “Cc” address field3. Repeat the test using the “Bcc” address field

MS is in idle mode

MS is in idle mode

MS is in idle mode

Create a new e-mail message with a text, add 20 different recipients, using the e-mail format recipients. Use all three address fields (To, Cc, and Bcc). Send the e-mail message. The MS displays a message that the e-mail has been sent. Verify that the e-mail recipients receive the message and that the email is correctly received

1. MS in idle mode2. Address book recipient available

Create a new e-mail message with a text, add recipients that already exist in the phone address book (as e-mail recipients). Use all three address fields (To, Cc, and Bcc). Send the e-mail. For the valid existing address book recipients the MS displays a message that the e-mail has been sent

Create a new E-Mail and insert a text object. Fill the subject field with the maximum length of 40 characters. Send the message. The MS displays a message that the e-mail has been sent. Verify that all characters of the subject are sent to the recipient

Create a new e-mail and insert a text object. Fill the text object with the maximum length as defined by the vendor of terminal. Send the message. The MS displays a message that the e-mail has been sent. Verify that all characters of the text are sent to the recipient

1. MS is in idle mode2. iMelody available in the sound browser of the MS

1. Create a new e-mail and insert an iMelody sound object. Send the message. The MS displays a message that the e-mail has been sent. Verify that the iMelody is played at the recipient while the e-mail is viewed and that the sound between the two MSs is comparable2. Repeat this test process for the other objects: MIDI / AMR sound / GIF / Animated GIF / JPEG / WBMP

1. MS is in idle mode2. At least 2 different pictures and 2 different sound objects available in the MS

Create a new e-mail and insert at least 2 different text, 2 different picture and 2 different sound objects. Send the message. The MS displays a message that the e-mail has been sent. Verify that all objects are correctly available at the recipient while the e-mail is viewed

1. MS in idle mode2. Business Card is available in the organiser of the MS

Create a new e-mail and attach a Business Card or add a contact from the phonebook as attachment. Send the message. The MS displays a message that the e-mail has been sent. Verify that the Business Card can be displayed at the recipient while the e-mail is viewed

1. MS is in idle mode2. Appointment is available in the organiser of the MS

Create a new e-mail and attach an appointment from the organizer. Send the message. The MS displays a message that the e-mail has been sent. Verify that the appointment can be displayed at the recipient while the e-mail is viewed

1. MS is in idle mode2. VNote is available in the organiser of the MS

Create a new e-mail and attach a VNote from the organizer. Send the message. The MS displays a message that the e-mail has been sent. Verify that the VNote can be displayed at the recipient while the e-mail is viewed

MS is in idle mode

1. MS is in idle mode2. Too long e-mail address recipient (exceeding 255 characters) is available

Create a new e-mail and enter the too long e-mail address recipient (exceeding 255 characters). Send the message. The MS displays a message that the e-mail recipient has a too long address field and verify that the mail could not be sent

1. Create a new e-mail and set the priority to “normal”. Send the message. The MS displays a message that the e-mail has been sent. Verify that the message received by the recipient has “normal” priority2. Repeat this test procedure with “ Low / Lowest / High / Highest “ priorities

1. MS with POP3 protocol settings is available2. MS is in idle mode

All related POP3 settings with the ISP’s settings is set in the MS. After the settings are completed , try to send and receive an e-mail

1. MS with IMAP4 protocol settings is available2. MS is in idle mode

All related IMAP4 protocol settings with the ISP’s settings is set in the MS. After the settings are completed , try to send and receive an e-mail

1. MS is in idle mode2. Incoming CS calls during active GPRS session are supported by the network

Receive an e-mail and start to download the message. During the download session receive an incoming Voice Call. Answer the call. The download session shall be interrupted. End the call and verify that the e-mail notification is still available and that it is possible to download the e-mail again

MS is in active call mode

MS is in a WAP session

1. MS is in idle mode2. Incoming Short Message (CS) during active GPRS session is supported by the network

Receive an e-mail and start to download the message. During the download session receive Short Message on the CS channel. Read the Short Message. The download session shall be interrupted. Verify that the e-mail notification is still available and that it is possible to download the e-mail again

1. Perform a Voice Call. During the call receive an e-mail. When receiving the e-mail notification, the call shall not be interrupted. End the call and verify that the notification of the e-mail is still available and that it is possible to download the e-mail2. Repeat the test performing a CS Data Call

Start a WAP session. While the WAP session is active, receive an e-mail. The MS shall save the e-mail notification while the WAP session is still active. Then check the e-mail notification and start to download the new e-mail. The MS shall close the active WAP session and start to connect to the e-mail browser to download the message. Verify that the e-mail is completely downloaded

UE switched on, in automatic selection mode in an area with coverage from both GSM and UMTS networks

1. Select the manual network selection mode on the UE and ensure that the list of all available PLMNs is displayed, and that the displayed networks can be selected, even if on the forbidden list2. Check that the preferred PLMN list is not changed after the manual network selection3. Repeat the test with different entries in the preferred PLMN lists, including the empty list and lists of more than 32 entries

1. MS is in idle mode2. Automatic network selection mode is configured

1. Change to manual network selection. Turn the UE off and on again. Check that the manual network selection mode is in use2. Change to automatic network selection. Turn the UE off and on again. Check that the automatic network selection mode is in use

Expected Result Actual Result Verdict Remarks

1. When powered ON, the MS sends a combined Attach Request to the network2. The Attach Type parameter shall hold the value: Combined GPRS/ IMSI attach3. In the Attach Accept message, the Attach Parameter shall hold the value: Combined GPRS/ IMSI attached

1. When powered ON, the MS sends a combined Attach Request to the network2. The Attach Type parameter shall hold the value: TMSI/ P-TMSI3. If the Attach Accept message contains a new TMSI/ P-TMSI value, the MS acknowledges this message by sending an Attach Complete message

1. When powered OFF, the MS sends a Detach Request message to the network2. The Detach Type parameter holds the value: power switched off, combined GPRS/ IMSI detach3. If the detach is not done at power OFF mode, the Detach Type parameter shall hold the value: normal, combined GPRS/ IMSI detach. The network responds back with a Detach Accept message

1. When powered ON, the MS performs the IMSI Attach2. MS performs GPRS Attach after IMSI Attach3. The elapsed time between GSM Attach and GPRS Attach should be only a few seconds4. The GPRS registration status shall be indicated on the display

1. When powered ON, the MS performs the IMSI Attach2. WAP Browser can be launched successfully and exited successfully3. The GPRS registration status shall be indicated on the display

1. When powered ON, the MS performs the IMSI Attach2. MS executes the manual attach through the use of appropriate AT commands (+CGATT) correctly3. The GPRS registration status shall be indicated on the display

When switched ON, the MS shall successfully register to the roaming network and shall offer unrestricted GPRS functionality

1. When powered ON, the MS shall attempt to perform a GPRS attach, and shall display an appropriate error message2. After power cycle, the MS shall reattempt GPRS attach

1. When powered ON, the MS shall attempt to perform a GPRS attach, and shall display an appropriate error message2. After power cycle, the MS shall reattempt GPRS attach

1. When powered ON in the HPLMN, the MS performs IMSI Attach and GPRS Attach successfully2. When moved from HPLMN to VPLMN, the MS attempts to register on the Visited SGSN but doesn’t succeed3. When moved back to the HPLMN, the MS shall successfully register and GPRS Attach should be successful

1. When powered ON in the HPLMN, the MS performs IMSI Attach and GPRS Attach successfully2. When moved from HPLMN to VPLMN, the MS attempts to register on the Visited SGSN but doesn’t succeed3. When moved back to the HPLMN, the MS shall successfully register and GPRS Attach should be successful

1. When powered ON in the HPLMN, the MS performs IMSI Attach and GPRS Attach successfully2. When moved from HPLMN to VPLMN, the MS attempts to register on the Visited SGSN but doesn’t succeed3. When moved back to the HPLMN, the MS shall not attempt GPRS Attach4. After power cycle, the MS shall perform GSM and GPRS Attach successfully

1. When powered OFF, MS should initiate GPRS detach procedure2. When leaving WAP browser, MS should initiate GPRS detach procedure3. When PDP context is activated through AT commands4. Battery is removed while the PDP context is active, GPRS detach shall occur correctly. And also after MS is powered ON, GPRS Attach shall occur correctly5. While data transfer is in progress, and GPRS detach is activated with the help of AT commands6. Battery is removed while the data transfer is in progress, GPRS detach shall occur correctly. And also after MS is powered ON, GPRS Attach shall occur correctly

MS shall perform the PDP context activation correctly when attempted to connect to the WAP browser after GPRS attach

MS shall perform the PDP context activation correctly for Modem application with:1. specified APN2. different APN3. different QoS

The MS must be able to manage the two different PDP contexts ensuring no error message pass through the air interface

When a “modify PDP context request” message is then sent to the MS from the SGSN, with a QoS that is acceptable to the MS, the MS shall send a "modify PDP context accept" message in return. If the QoS are not acceptable from the MS, it shall send a "Deactivate PDP context request" message in return

The MS shall perform the PDP context deactivation correctly:1. during no file transfer2. during file transfer

During several WAP, WEB or FTP session, the MS should not deactivate the PDP context by itself (PDP context should stay active for at least 20min)

The MS performs correctly the PDP context deactivation when it receives the appropriate network command

1. The average throughput shall be at least: a. 40kbps per timeslot in strong signal area b. 25kbps per timeslot in medium signal area c. 15kbps per timeslot in weak signal area2. The GPRS connection and file download shall be stable

1. The GPRS connection shall be stable2. The file download shall complete

1. The average throughput shall be at least: a. 40kbps per timeslot in strong signal area b. 25kbps per timeslot in medium signal area c. 15kbps per timeslot in weak signal area2. The GPRS connection and file download shall be stable

1. MS should perform reselections correctly, without losing service2. MS should be able to receive calls before and after the reselections

1. MS should perform reselections correctly, without losing service2. MS should be able to receive calls before and after the reselections

1. MS should perform reselections correctly, without losing service2. Data transfer may pause during reselection but resume on the new cell3. MS shall be able to receive calls after the reselections (which may pause data transfer without DTM)4. The data session shall resume after releasing the voice call5. The data rate shall be as expected for the data bearer type assigned by the network throughout the test, i.e. data rates proportional to the data bearer and signal quality shall be achieved both before and after the cell reselections

MS shall support all the PIN1 handling procedures correctly

MS shall support all the PIN2 handling procedures correctly

All the test procedures should work appropriately

The message is sent and correctly received by the B-subscriber

The message is sent and correctly received by the B-subscriber. The sender’s address is not visible

The message is correctly sent and received by the B-subscriber

The message is correctly sent and received by the email recipient indicating the appropriate address fields

The message is correctly sent and received by all recipients indicating the appropriate address fields

The message is sent with the appropriate display messages and received by all valid recipients indicating the appropriate address fields

The message is correctly sent and received by the recipient with the complete subject field

The message is correctly sent and received by the recipient with the complete text field

The message is correctly sent and received by the recipient with the appropriate iMelody sound

The message is correctly sent and received by the recipient with the appropriate MIDI sound

The message is correctly sent and received by the recipient with the appropriate sound object

The message is correctly sent and received by the recipient with the correct GIF image

The message is correctly sent and received by the recipient with the correctly animated GIF image

The message is correctly sent and received by the recipient with the correct JPEG image

The message is correctly sent and received by the recipient with the correct WBMP image

The message is correctly sent and received by the recipient with all objects

The message is correctly sent and received by the recipient with the Business Card

The message is correctly sent and received by the recipient with the attached appointment

The message is correctly sent and received by the recipient with the attached Vnote

The message is correctly sent and received by the email recipient with the appropriate embedded objects

The message is correctly sent and received by the email recipient with the Business Card

The message is correctly sent and received by the recipient with the appropriate priority



The message is correctly sent and received by the appropriate recipient

The message is correctly sent and received by all recipients

The message is correctly forwarded and received by the recipient(s) with the “forwarding marker”

The Notification(s) are saved in the MS, its/their message size is correctly displayed and the correct MMS is downloaded

The sender and the message content is correctly displayed



The subject field is complete and correctly displayed

The text field is complete and correctly displayed

The iMelody sound object is correctly played and can be saved to the appropriate data folder of the MS

The MIDI sound object is correctly played and can be saved to the appropriate data folder of the MS

The AMR sound object is correctly played and can be saved to the appropriate data folder of the MS

The GIF image is correctly displayed and can be saved to the appropriate data folder of the MS

The animated GIF image is correctly displayed and animated and can be saved to the appropriate data folder of the MS

The JPEG image is correctly displayed and can be saved to the appropriate data folder of the MS

The WBMP image is correctly displayed and can be saved to the appropriate data folder of the MS

All objects can be played/displayed and can be saved to the appropriate data folders of the MS

The Business Card can be displayed and saved to the directory of the MS

The appointment can be displayed and saved to the organiser of the MS

The VNote can be displayed and saved to the organiser of the MS

The various objects can be played/displayed and saved to its/their designated data folder(s) of the MS

The received MMS is indicating the priority set to “normal”

The received MMS is indicating the priority set to “low”

The received MMS is indicating the priority set to “high”

The MS is not automatically playing the sound object of the MMS

The MS is not automatically downloading the MMS. On reject by the user, the MS sends a M_Notify_Resp with X-MMS-Status set to “reject” to the network.The MS does not send a new notification for this message to the user

The MS is not automatically downloading the MMS. On defer by the user, the MS sends a “defer” message to the network. On downloading, the MS receives exactly the MMS which was previously deferred

The MS is automatically downloading the MMS. After receipt, the message can be displayed by the user

The MS is indicating to the user that its MMS memory is full. The MS sends a “defer” message to the network. On downloading, the MS receives exactly the MMS which was previously deferred

The MS is not automatically downloading the MMS

The MS is not automatically downloading the MMS. On receipt of the MMS notification, the MS sends a “defer” message to the network. On downloading, the MS receives exactly the MMS which was previously deferred

The MS is correctly displaying the Delivery Report

The MS is not receiving a Delivery Report

The MS is displaying the delivery status of the sent message as “delivered”

The MS is displaying the delivery status of the sent message as “rejected”

The MS is displaying the delivery status of the sent message as “Timer expired”

The MS is correctly displaying the various delivery states of the sent message

The MS is displaying the delivery status of the sent message as “delivered”

The retrieving MS is denying the Delivery Report and the sending MS is not receiving a Delivery Report

The MS is correctly sending the Read Reply Report request

The MS is not sending a Read Reply Report request

The message is correctly sent and received by the email recipient indicating the appropriate address fields

The message is correctly sent and received by all recipients indicating the appropriate address fields

The message is sent for all addressor recipients with the appropriate display messages and received by all valid address book recipients indicating the appropriate address fields

The message is correctly sent and received by the recipient with the complete subject field

The message is correctly sent and received by the recipient with the complete text field

The message is correctly sent and received by the recipient with the appropriate object

The message is correctly sent and received by the recipient with all objects

The message is correctly sent and received by the recipient with the Business Card

The message is correctly sent and received by the recipient with the attached appointment

The message is correctly sent and received by the recipient with the attached Vnote

The message could not be sent since the recipient’s mail address is too long


After settings completed e-mail sending & receiving is working properly

After settings completed e-mail sending & receiving is working properly

The MMS notification is still available and it is possible to download the MMS again

The e-mail notification is still available and it is possible to download the e-mail again

The call does not drop. The e-mail notification is still available and it is possible to download the e-mail

The e-mail notification is still available and it is possible to download the complete e-mail

The UE shall display all available PLMNs and it shall perform manual network selection on the chosen network. The preferred PLMN list is not changed after the manual network selection.The UE shall display all available GSM and UMTS networks

The UE has the same selection mode when switched on that it had when switched off

gcf edited

Documents