03 GSM - Gprs - Umts Terminals For The Operators of The TM Group Tests of Basic GSM Functionality

TESTS SPECIFICATIONS GSM/GPRS/UMTS TERMINALS FOR THE OPERATORS OF THE TM GROUP: TESTS OF BASIC GSM FUNCTIONALITY
CODE VERSION DATE
03 4 26/03/10
03 GSM/GPRS/UMTS TERMINALS FOR THE OPERATORS OF THE TM GROUP: TESTS OF BASIC GSM FUNCTIONALITY
SIGNATURE AND VERSION CONTROL TABLE
VERSION DATE
1
05/10/05
2
11;01/07
3
28/01/08
4
26/03/10
10
11
12
13
14
VERSION
DATE
PREPARED BY
REVIEWED BY
Carlos Crespo Arrabal
APPROVED BY
05/10/05 1 11/01/07 Daniel Cordoba Cornejo Thiago Arantes Suedan
Enrique Gallo
Carlos Melendo
Jos Maria Daz Carmona
28/01/08
Otvio Augusto Ribeiro Gonalves
26/03/10
Fernanda Contrucci Terra
RESPONSIBILITIES
DISTRIBUTION: Handsets and Smart Cards Direction is responsible for the distribution of this document FILLING: Handsets and Smart Cards Direction is responsible for the filling of this document UPDATING: Handsets and Smart Cards Direction is responsible for updating this document
Telefonica Moviles Proprietary and Confidential

File: 03-Basic GSM Functionality Tests.doc Page 1 of 40
CODE VERSION DATE
03 4 26/03/10
SUMMARY OF CHANGES
VERSION: POINT GSM 4 DATE: March 26th, 2010
CHANGES REGARDING PREVIOUS VERSION Insertion of new requirements codes (2010Q1).
File: 03-Basic GSM Functionality Tests.doc
Page 2 of 40
CODE VERSION DATE
03 4 26/03/10
INDEX
1 2 3 4 5 INTRODUCTION ..........................................................................................................................................................................4 RELATED DOCUMENTS............................................................................................................................................................4 DEFINITIONS AND ABBREVIATIONS ...................................................................................................................................4 CONDITIONS FOR THE REALIZATION OF THE TESTS..................................................................................................4 TESTS SPECIFICATIONS...........................................................................................................................................................5
5.1 FUNCTIONAL TESTS ......................................................................................................................................................................5 5.1.1 VIVO NETWORK / MOBILE EQUIPMENT INTERACTION TESTS...................................................................................5 5.1.2 CLIP/CLIR TESTS (POLICE FUNCTION) .........................................................................................................................12 5.1.3 PHONEBOOK NUMBERS IDENTIFICATION ..................................................................................................................16 5.1.4 DTMF TONES ......................................................................................................................................................................20 5.1.5 INTERNATIONAL ROAMING TESTS .................................................................................................................................22 5.1.6 PHONE BOOK .....................................................................................................................................................................24 5.1.7 SUPPLEMENTARY SERVICES ...........................................................................................................................................25 5.1.8 DISPLAY OF THE CALLING NUMBER IDENTITY ..........................................................................................................34 5.1.9 CONCEALMENT OF OWN NUMBER................................................................................................................................35 5.1.10 OTHER TESTS.................................................................................................................................................................36 5.2 LOAD TESTS................................................................................................................................................................................40 5.3 INTEGRATION TESTS ...................................................................................................................................................................40 5.4 BUG TOLERANCE TESTS .............................................................................................................................................................40 5.5 INTEROPERABILITY TESTS WITH OTHER SERVICES .....................................................................................................................40 5.6 OTHER TESTS..............................................................................................................................................................................40 6 7 OTHER ..........................................................................................................................................................................................40 ANNEX ..........................................................................................................................................................................................40
Page 3 of 40
CODE VERSION DATE
03 4 26/03/10
INTRODUCTION
This document describes the tests of basic GSM functionality that GSM/GPRS terminals must pass to be certificated by Vivo. 2 RELATED DOCUMENTS TM ERD specifications. 3 DEFINITIONS AND ABBREVIATIONS 4 DuT: Device under Test ETSI: European Telecommunications Standard Institute GPRS: General Packet Radio Service SAT: SIM Application Toolkit SIM: Subscriber Identity Module HLR: Home Location Register
CONDITIONS FOR THE REALIZATION OF THE TESTS
Not applicable.
Page 4 of 40
TESTS SPECIFICATIONS GSM/GPRS/UMTS TERMINALS FOR THE OPERATORS OF THE TM GROUP TESTS OF BASIC GSM FUNCTIONALITY
CODE VERSION DATE
03 4 26/03/10
5 5.1
TESTS SPECIFICATIONS Functional Tests VIVO NETWORK / MOBILE EQUIPMENT INTERACTION TESTS
5.1.1
These tests consist in checking the basic interaction mechanisms of the mobile equipment with the Vivo network. The tests are concerned with turning the terminal on/off, call establishment, failures in communication, etc. 5.1.1.1 PRESENCE OF THE MOBILE TELEPHONE IN THE VIVO NETWORK
RESPONSIBLE
TEST TYPE
CRITICAL DEGREE
TEST DEPENDENCE
Vendor Vendor - Remote Access Vendor - TM Resources Support TM
Conformance Interoperability End to End Service X
High Medium Low
Page 5 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION
ADDITIONAL INFO
1. Insert the SIM Card from another To perform this test the operator inside the handset and turn the terminal must be terminal on. unlocked to another 2. Choose (on the terminal settings) Vivo operators.
PROCEDURE:
as the terminal default network. 3. The terminal couldnt connect to the Vivo network. 4. The message Location Update Reject must be sent to the terminal. The terminal couldnt connect to the Vivo network. The message Location Update Reject must be sent to the terminal. 1. Getting a log file, turn on the DuT and check that it connects to the network almost immediately.
GSM.A.1.2
Logging in of the mobile TR-GENERphone in another operator REJCT-001a (location update reject)
EXPECTED RESULT:
PROCEDURE:
2. Check this point by successfully making a call to the mobile phone. Note: this test needs log software in order to check the Location Update message and IMSI ATTACH message in the layer 3.
GSM.A.2.1
Logging in of the mobile phone (IMSI attach)
The mobile phone must log in to the VIVO network correctly (it completes a EXPECTED RESULT: Location Update that corresponding to IMSI ATTACH).
Page 6 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION 1. Getting a log file, turn on the DuT and check that it connects to the network almost immediately, check that the mobile phone is connected to the network and indicates that there is coverage. 2. Try to call the mobile from a telephone in the fixed network. When the call has been completed, finish it and turn the mobile off. 3. Try to call the mobile again and confirm that the VIVO network responds with the message that the mobile phone is not in operation. Note: this test needs log software in order to check the IMSI Detach message in the layer 3. The mobile phone must log off from the
EXPECTED RESULT: VIVO network correctly (it completes an
ADDITIONAL INFO
PROCEDURE:
GSM.A.3.1
Logging off of the mobile phone (IMSI detach)
IMSI Detach) when it is turned off.
5.1.1.2 MOBILE ORIGINATED CALLS
RESPONSIBLE
TEST TYPE
CRITICAL DEGREE
TEST DEPENDENCE
Vendor
Conformance
High
X
Page 7 of 40
CODE VERSION DATE
03 4 26/03/10
Vendor - Remote Access Vendor - TM Resources Support TM TEST CODE REQ. CODE TEST NAME
Interoperability End to End Service
Medium Low
DESCRIPTION 1. From a fixed network telephone dial the number of the tested mobile. 2. Confirm that the terminal emits the incoming call tone.
PROCEDURE:
ADDITIONAL INFO
GSM.B.1.3
Mobile terminated 1 calls made from the fixed network
3. Press the send key to establish communication. Confirm that the call is successfully established. 4. Once the call is established, press the mobiles hang up key. Check that the communication has been cut off and that the terminal goes into standby mode.
1. A call shall be successfully established from the fixed network to the mobile EXPECTED RESULT: telephone. 2. The mobile must be able to end a call established from the fixed network.
Page 8 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION 1. Enter an international telephone number using the + key and the destination country code.
ADDITIONAL INFO
GSM.B.3.1
Mobile originated international call
PROCEDURE:
2. Confirm that communication is established. 3. The international call must be established.
EXPECTED RESULT:
Voice call to international correctly established. 1. In the DuT, dial a local telephone number and press the send key.
GSM.B.4.1
Finishing of the call by the mobile phone during the establishment stage
PROCEDURE:
2. Before communication is established, cut off the call with the hang up key. 3. Confirm that the destination telephone does not ring and that the mobile displays VIVO so that another call may be made.
The DuT must finish the call when the EXPECTED RESULT: Hang up key is pressed during the establishment of the call. 1. In the DuT, dial a local telephone number and press the send key. GSM.B.5.1 Finishing of a call in progress by the mobile phone
PROCEDURE:
2. Once the communication is established, press the hang up key. 3. Check that the mobile goes into standby mode and displays the signal level and the message VIVO.
Page 9 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
EXPECTED RESULT:
DESCRIPTION The DuT must be able to finish a call when the hang up key is pressed. 1. In the DuT, dial a local telephone number and press the send key.
ADDITIONAL INFO
GSM.B.8.1
Finishing of a call due to the PROCEDURE: mobile phone being turned off in the course of a call
2. Once communication is established, turn the mobile off. 3. Turn the telephone on again and check that the terminal is in standby mode and displays the signal level received and the message VIVO. The DuT must finish the call correctly if it is turned off in the course of a call. 1. In the DuT, dial a local telephone number and press the send key.
EXPECTED RESULT:
GSM.B.9.1
Finishing of a call due to PROCEDURE: withdrawal of the battery of the mobile phone in the course of a call
2. Once the call is established, withdraw the battery. 3. Turn the mobile on. Check that the mobile goes into standby mode and displays the signal level and the message VIVO. The DuT must finish the call correctly when the battery is withdrawn.
EXPECTED RESULT:
Page 10 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION 1. Dial a fixed network telephone number and press the send key. 2. Confirm that the calling tone can be heard at the destination telephone. 3. Once communication is established, hang up the fixed network telephone. Indicate the time that the mobile takes to go into standby mode. 4. Indicate if any message is displayed. Then check that the terminal goes into standby mode and displays the signal level received and the message VIVO. 5. Repeat the steps 1 to 4, but dial the number of the DuT from fixed network telephone. 1. A call shall be successfully established. 2. The mobile phone must finish a call
EXPECTED RESULT: correctly when it is the fixed network
ADDITIONAL INFO
PROCEDURE:
GSM.B.10.1
Finishing of a call by a fixed network telephone
telephone that cuts off the call, in both cases, when the fixed network phone or DuT originating the call.
Page 11 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION 1. Perforn an outgoing voice call from DuT to a busy fixed network number not having Call Waiting service activated.
ADDITIONAL INFO
GSM.B.11.1
TR-SERVC- Call to an engaged fixed VOICE-002a network number
PROCEDURE:
2. Check that the mobile correctly indicates the busy status of the distant party, emiting the "engaged" tone (unless the other telephone supports the call waiting function). The DuT must be informed that the distant party is busy.
EXPECTED RESULT:
5.1.2 CLIP/CLIR TESTS (POLICE FUNCTION) These tests require associating the supplementary services CLIP and SOCLIP to the terminal that performs the call (ME1), while CLIP and SOCLIP shall be associated to the terminal which is called to (ME2). The possible values according to these options are the following: CLIR (Calling Line Identification Restriction): - 0: not activated (the calling terminal does not hide its identity) - 1: activated (the calling terminal hides its identity) SOCLIR (Subscription Option Calling Line Identification Restriction): - 0: permanent mode (whatever CLIR option indicates is applied, therefore CLIR option prevails) - 1: temporal mode, restricted presentation (if CLIR is activated, the calling terminal hides its identity unless it sends the code *31# as the prefix of the called number) - 2: temporal mode, permitted presentation (if CLIR is activated, the calling terminal does not hide its identity unless it sends the code *31# as the prefix of the called number)
File: 03-Basic GSM Functionality Tests.doc Page 12 of 40
CODE VERSION DATE
03 4 26/03/10
CLIP (Calling Line Identification Presentation): - 0: not activated (the called terminal does not present the identity of the calling terminal) - 1: activated (the called terminal presents the identity of the calling terminal) SOCLIP (Subscription Option Calling Line Identification Presentation): - 0: without override category (whatever CLIP option indicates is applied, therefore CLIR option prevails) - 1: with override category (the identity is presented independently of the calling number restrictions) For each possible combination of the values of these parameters, the final result must be as specified in the EXPECTED PRESENTATION column. The codes *31# and #31# that appear when SOCLIR = 1 or 2 are prefixes that precede the called number and allow to hide or not the calling terminals identity. When SOCLIR = 1, the calling terminal hides its identity by default, unless the prefix *31# is written before the called number. When SOCLIR = 2, calling terminal does not hide its identity, unless the prefix #31# is written before the called number. Thus, these two modes (SOCLIR = 1,2) are called temporal mode. They can activate or deactivate the calling number occultation whenever the caller wants. The option SOCLIP = 1 in the called terminal allows acting like the police displaying the identity of the calling number, although it keeps its identity hidden by means of the CLIR option.
Page 13 of 40
CODE VERSION DATE
03 4 26/03/10
ME1 CLIR X 0 1 1 1 SOCLIR X X 0 without code *31# 1 2 without code #31# 0 1 1 1 X 0 without code *31# 1 2 without code #31# 1 1
ME2 CLIP SOCLIP 0 X EXPECTED PRESENTATION Not presented Presented Not presented 0 Not presented Presented Presented Not presented Presented Presented 1 Presented Presented Presented Presented
Table 1: CLIP/CLIR tests
Page 14 of 40
RESPONSIBLE TEST TYPE CRITICAL DEGREE
CODE VERSION DATE
03 4 26/03/10
TEST DEPENDENCE
Vendor Vendor - Remote Access Vendor - TM Resources Support TM TEST CODE REQ. CODE TEST NAME X
High Medium Low X
DESCRIPTION 1. Dial *31# (Interrogation), and ensure that the phone correctly indicates the CLIR status as not active. 2. Use ME1 to call ME2. Dial #31# before ME2 number.
PROCEDURE:
ADDITIONAL INFO
GSM.D.1.1
TR-SERVCCLIP/CLIR Tests SUPPL-005a
3. Check that the ME1 number is shown as "unknown" on ME2. 4. Repeat the same procedure but using the ME1 menu instead the code for changing CLIR status. 5. Check that the ME1 number is shown as "unknown" on ME2.
Check that the ME1 number is shown as EXPECTED RESULT: "unknown" on ME2 using both procedures, code and menu.
Page 15 of 40
CODE VERSION DATE
03 4 26/03/10
5.1.3 PHONEBOOK NUMBERS IDENTIFICATION The objective of the next test is check how many digits of a number stored in the SIM card phonebook (ADN) or in the phone memory phonebook (Phone Memory) can be recognized by the terminal.
RESPONSIBLE TEST TYPE CRITICAL DEGREE TEST DEPENDENCE
High Medium Low
Page 16 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION
ADDITIONAL INFO
GSM.E.1.1
Identification of the phonebooks (ADN & Phone PROCEDURE: Memory) numbers when Making a Call
1. Store a phone number of 13 digits in Example: DuT's phonebook (ADN, phone Number of 8 digits: memory) 9696 0236 2. Dial with 8 digits to the stored number, Number of 11 digits: but modifying its first digit and check if 011 9696 0236 the handset does or does not show the Number of 13 digits: alphanumeric identifier. 01511 9696 0236 3. In case this identifier is shown, you have to repeat this test, also modifying the following digit pressed as many times necessary until the handset does not show the alphanumeric identifier 4. Check which numbers need to be changed for not showing the alphanumeric identifier. 5. Repeat steps 2, 3 and 4, dialing with 11 and 13 digits to the stored phonebook number.
Page 17 of 40
CODE VERSION DATE
03 4 26/03/10
The DuT should recognize the dialled number. Please, indicate how many numbers need to be changed for not showing the alphanumeric identifier. - For 8 digits dialed: The handset MUST NOT show the identifier, case any of the following digits pressed has been changed: 3rd up to 8th. - For 11 digits dialed: The handset MUST NOT show the identifier, case any of the following digits pressed has been changed: 6th up to 11th. - For 13 digits dialed: The handset MUST NOT show the identifier, case any of the following digits pressed has been changed: 8th up to 13th.
EXPECTED RESULT:
Page 18 of 40
CODE VERSION DATE
03 4 26/03/10
1. Store a phone number of 13 digits in Example: DuT's phonebook (ADN, phone Number of 8 digits: memory). 9696 0236 2. Perform a voice call from stored phone Number of 11 digits: to DuT. 011 9696 0236 3. Check that the incoming call is Number of 13 digits: identified by its alphanumeric identifier. 01511 9696 0236 4. Store the number but modifying its first digit and check if the handset does or does not show the alphanumeric identifier for the incoming call. 5. In case this identifier is shown, you have to repeat this test, also modifying the following digit stored as many times necessary until the handset does not show the alphanumeric identifier. 6. Repeat the steps 3, 4 and 5 changing to 11 and 8 digits the stored phonebook number.
GSM.E.1.2
Identification of the phonebooks (ADN & Phone PROCEDURE: Memory) numbers when Receiving a Call
Page 19 of 40
CODE VERSION DATE
03 4 26/03/10
The DuT should recognize the incoming number. Please, indicate how many numbers need to be changed for not showing the alphanumeric identifier. For 8 digits stored: The handset MUST NOT show the identifier, case any of the following digits EXPECTED RESULT: has been changed: 3rd up to 8th. - For 11 digits stored: The handset MUST NOT show the identifier, case any of the following digits has been changed: 6th up to 11th. For 13 digits stored: The handset MUST NOT show the identifier, case any of the following digits has been changed: 8th up to 13th.
5.1.4 DTMF TONES


High Medium Low
Page 20 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION
ADDITIONAL INFO
PROCEDURE:
GSM.F.1.1
Sending DTMF tones

EXPECTED RESULT:
1. Check that the voicemail system Initial configuration responds correctly to the digits 0-9, * and MS in active state, on a #. call to a voicemail 2. Repeat procedure 1, sending DTMF system or other DTMF digits stored in the phonebook memory. receiver. The voicemail system responds correctly to the digits sent by the MS.
Page 21 of 40
CODE VERSION DATE
03 4 26/03/10
5.1.5 INTERNATIONAL ROAMING TESTS

Vendor Vendor - Remote Access Vendor - TM Resources Support TM X
High Medium Low
Page 22 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION 1. Insert SIM card allowing roaming with several available PLMNs 2. Once the DuT is powered on, check that it registers in a PLMN. 3. Go into preferred networks menu of device. 4. Insert into the list another PLMN for which the SIM has roaming agreements. This PLMN must be different from the one where the DuT is camped. 5. Make sure that the DuT is in automatic network selection mode. 6. Wait for Higher Priority PLMN search period. 7. Check that the DuT camps automatically into the new PLMN. 8. Try to make a voice call and check that the call can be established. The DuT camps into a higher priority PLMN once Higher Priority PLMN search EXPECTED RESULT: period has expired. The DuT can make establish a call in registered PLMN
ADDITIONAL INFO
PROCEDURE:
GSM.G.1.1
Automatic network TR-GSMRQselection with favorite GENER-007a networks stored in the SIM
Page 23 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION 1. Insert SIM card allowing roaming with several available PLMNs 2. Once the DuT is powered on, check that it registers in a PLMN. 3. Go into preferred networks menu of device. 4. Insert into the list another PLMN for which the SIM has roaming agreements. This PLMN must be different from the one where the DuT is camped. 5. Make sure that the DuT is in manual network selection mode. 6. Wait for Higher Priority PLMN search period. 7. Check that the DuT remains into the initial PLMN. 8. Try to make a voice call and check that the call can be established.
EXPECTED RESULT:
ADDITIONAL INFO
GSM.G.3.1
Manual network selection TR-GSMRQwith favorite networks GENER-007a stored in the SIM
PROCEDURE:
The DuT remains in the manually selected PLMN nd can establish a call.
5.1.6 PHONE BOOK

RESPONSIBLE
TEST TYPE
CRITICAL DEGREE
TEST DEPENDENCE
Page 24 of 40
CODE VERSION DATE
03 4 26/03/10
Vendor Vendor - Remote Access Vendor - TM Resources Support TM TEST CODE REQ. CODE TEST NAME
High Medium Low
DESCRIPTION 1. Verify that the DuT allows introducing a number in the phone book (ADN, phonebook). 2. Verify that the number can be recovered and modified, introducing again the changes in the phonebook. Phonebook registers can be recorded and modified 1. Select a register in DuT's phonebook (ADN, phone memory).
ADDITIONAL INFO
GSM.I.1.1
PROCEDURE: Introduction and modification of registers in the phone book EXPECTED RESULT:
GSM.I.2.1
Removing registers from the phone book
PROCEDURE:
2. Verify that the DuT allows deleting the register in the phone book. 3. Once deleted, check that the register is not present in the phonebook
EXPECTED RESULT: Phonebook register can be deleted
5.1.7 SUPPLEMENTARY SERVICES

RESPONSIBLE
TEST TYPE
CRITICAL DEGREE
TEST DEPENDENCE
Page 25 of 40
CODE VERSION DATE
03 4 26/03/10
Vendor Vendor - Remote Access Vendor - TM Resources Support TM TEST CODE REQ. CODE GSM.J.1.0 TEST NAME Call forwarding
High Medium Low
DESCRIPTION The aim of these tests is to check the calls to the handset are forwarded to a predefined number when this option is active. The details will change depending on the activated kind of forwarding. 1. Dial the code string (CFU) with a number phone to which calls shall be forwarded, 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 by code string.
ADDITIONAL INFO
CFU: Code **21*DN# (Activation of unconditional forwarding)
GSM.J.1.1
TR-SERVCSUPPL-003b
Unconditional forwarding
PROCEDURE:
2. Make calls from any terminal to the DuT. The calls Code #21# should be forwarded to the indicated number. (Deactivation of 3. Deactivate unconditional forwarding by code string unconditional and make calls to check it. The DuT must receive the forwarding) calls. 4. Repeat procedure 1 to 3, but using menu commands instead. Code *#21#
Page 26 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION
ADDITIONAL INFO
1. The MS registers the supplementary service and (Status) displays the fact correctly. 2. Activation: The calls should be forwarded to the EXPECTED RESULT: indicated number. 3. Deactivation: The DuT must receive the calls The results obtained by the two procedures shall be identical. 1. Dial the code string (CFBy) with a number phone to which calls shall be call forwarding when busy, 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 by code string. 2. Make a call from the DuT to a support terminal. GSM.J.1.2 TR-SERVCSUPPL-003b Call forwarding when busy
PROCEDURE:
CFBy: Code **67*DN# (Activation of forward when busy) Code #67# (Deactivation of forward when busy)
3. While the DuT is busy, make a call from any terminal to it. The call should be forwarded to the indicated number in the code string.
4. Deactivate forward when busy by code string and Code *#67# repeat the procedure 2 and 3, but now the call should (Status) no longer be forwarded. 5. Repeat procedure 1 to 4, but using menu commands instead..
Page 27 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION 1. The MS registers the supplementary service and displays the fact correctly. 2. Activation:The call must be forwarded when busy to the indicated number.
EXPECTED RESULT: 3. Deactivation: The call must be forwarded to the
ADDITIONAL INFO
voice mail. The results obtained by the two procedures shall be identical. For this test the "call waiting" must be disable. 1. Dial the code string (CFNRy) with a number phone to which calls shall be call forwarding if no answer, 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. GSM.J.1.3 TR-SERVCSUPPL-003b Call forwarding if no PROCEDURE: answer CFNRy: Code **61*DN# (Activation of forward if no answer)
2. Make a call from any terminal to the DuT, but don't Code #61# answer the call. The call should be forwarded to the (Deactivation of forward if no answer) indicated number. 3. Deactivate forward if no answer by code string and repeat the procedure 2 , but now the call should no Code *#61# (Status) longer be forwarded. 4. Repeat procedure 1 to 3, but using menu commands instead.
Page 28 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION 1.The MS registers the supplementary service and displays the fact correctly. 2. Activation: The call must be forwarded if no answer to the indicated number. 3. Deactivation: The call should no longer be forwarded. The results obtained by the two procedures shall be identical. 1. Dial the code string (CFNRc) with a number phone to which calls shall be call forwarding when phone off or no coverage, 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 by code string. 2. Turn the DuT off or put in a no coverage area.
ADDITIONAL INFO
EXPECTED RESULT:
CFNRc: Code **62*DN# (Activation of forward when phone off or no coverage).
GSM.J.1.4
TR-SERVCSUPPL-003b
Call forwarding when phone off or PROCEDURE: no coverage
Code #62# (Deactivation of forward 3. Make calls from any terminal to the DuT. The calls when phone off or no must be forwarded to the indicated number. coverage). 4. Deactivate call forwarding when phone off or no coverage and repeat procedure 2 and 3. The call Code *#62# should no longer be forwarded. (Status) 5. Repeat procedure 1 to 4, but using menu commands instead.
Page 29 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION 1. The MS registers the supplementary service and displays the fact correctly. 2. Activation: The calls must be forwarded when phone off or no coverage to the indicated number. 3. Deactivation: The calls should no longer be forwarded. The results obtained by the two procedures shall be identical. 1. 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.
PROCEDURE:
ADDITIONAL INFO
EXPECTED RESULT:
GSM.J.3.1
TR-SERVCCall waiting SUPPL-002a
2. 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. 3. 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.
EXPECTED RESULT:
The MS provides an appropriate tone and display, and allows the waiting call to be accepted.
Page 30 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION Ms with an active call in progress. 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 hold. 2. 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 call. 3. Repeat procedures 1 & 2 using menu commands. 4. Check that if the party on hold releases the call, the MS indicates that the call has ended. 5. Check that is the distant party releases the call during the attempt to retrieve it, the MS indicates that the call has ended. 6. Check that if distant party releases the active call, the held call can still be retrieved. 1. The distant party hears the call go on hold. 2. The two calls are alternated and conversation is possible on the new call.
EXPECTED RESULT: 3. As for 1 & 2.
ADDITIONAL INFO
PROCEDURE:
GSM.J.4.1
TR-SERVCCall hold SUPPL-002a
4. The MS indicates that the call has ended. 5. The MS indicates that the call has ended. 6. The held call can still be retrieved.
Page 31 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION 1. Dial the code 3 SEND to join the calls. Check that all three parties can speak to each other 2. 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. 3. After completing procedure 2, dial the code 3 SEND to join the calls. Check that all four parties can speak to each other. 4. 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.
ADDITIONAL INFO
GSM.J.5.1
TR-SERVC- Multi-conference SUPPL-010b
PROCEDURE:
5. 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. 6. After completing procedure 5, dial the code 3 SEND to join the calls. Check that all five parties can speak to each other. 7. After completing procedure 6, place the multiparty call on hold, and make a new outgoing call (DN SEND). 8. After completing procedure 7, dial the code 3 SEND to join the calls. Check that all six parties can speak to each other
Page 32 of 40
CODE VERSION DATE
03 4 26/03/10
TEST CODE REQ. CODE
TEST NAME
DESCRIPTION 9. 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). 10. 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. 11. 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. 12. 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). 13. 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). 14. 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.
EXPECTED RESULT:
ADDITIONAL INFO
The MS behaves as described in the test procedure.
Page 33 of 40
CODE VERSION DATE
03 4 26/03/10
5.1.8 DISPLAY OF THE CALLING NUMBER IDENTITY

High Medium Low
DESCRIPTION 1. Call the DuT from a mobile terminal that does not have the concealment of own number service activated. 2. Check that the DuT displays the number of the mobile that originated the call. The DuT should show the calling number on the display.
ADDITIONAL INFO
GSM.K.1.1
Display of the calling number identity
PROCEDURE:
EXPECTED RESULT:
Page 34 of 40
CODE VERSION DATE
03 4 26/03/10
5.1.9 CONCEALMENT OF OWN NUMBER

High Medium Low
DESCRIPTION 1. In the DuT, by means of the menu activate the "Concealment of own number" option.
ADDITIONAL INFO
GSM.L.1.1
Concealment of own number
PROCEDURE:
2. Establish a call to a terminal that supports the "Display identity of the calling number" service, and check that the number of the DuT does not appear on the display. The DuT must not send its number to the called telephone.
EXPECTED RESULT:
Page 35 of 40
TESTS SPECIFICATIONS GSM/GPRS/UMTS TERMINALS FOR THE OPERATORS OF THE TM GROUP TESTS OF BASIC GSM FUNCTIONALITY 5.1.10 OTHER TESTS These tests try to analise some general features of the handset.
RESPONSIBLE TEST TYPE CRITICAL DEGREE
CODE VERSION DATE
03 4 26/03/10
TEST DEPENDENCE
High Medium Low
1. Check if the voicemail account has been created for the MSISDN. Case it doesnt exist, create a voicemail account (Call to *555) 2. Leave 5 voice messages in the voicemail account of the terminal. 3. The terminal must display a notification of new voicemail message recorded (ex. Icon). 4. Access the voicemail account and listen to 5 voice messages recorded, deleting them one by one.
GSM.R.1.1
Voice Mail
PROCEDURE:
Page 36 of 40
CODE VERSION DATE
03 4 26/03/10
All the messages must be properly listened and the notification icon must be shown. After listening to the voicemail EXPECTED RESULT: messages and deleting them, the terminal must delete the voicemail message notification (icon). 1. Turn Off and On the terminal.
PROCEDURE:
2. Write down the Cell Broadcast message displayed. 3. A Cell Broadcast message must be displayed. A Cell Broadcast message must be displayed.
GSM.R.2.1
TR-SERVCCell Broadcast CBCRQ-002b

EXPECTED RESULT:
Example: Tests in SP city: VIVO SP 11 Tests in RJ city: VIVO RJ 21 1. Turn Off and On the terminal
PROCEDURE:
GSM.R.3.1
PLMN
2. Check if the PLMN (MCC + MNC) code received from the network is converted to "Vivo" and displayed by terminal.
The PLMN (MCC + MNC) code received EXPECTED RESULT: from the network must be converted to Vivo and displayed by terminal.
Page 37 of 40
CODE VERSION DATE
03 4 26/03/10
1. Check what type the voice ciphering algorithms are active in the network. 2. Establish a voice call and get a log file. 3. The DuT must keep a voice call with an algorithm supported by itself and the network. 4. If the DuT doesnt support the NW ciphering it must keep the voice call without ciphering (A5/0). Note: this test needs log software in order to check the ciphering algorithms used by the DuT.
EXPECTED RESULT: DuT uses ciphering according to network
GSM.R.4.1
Voice Ciphering
PROCEDURE:
1. Set a wrong Time and Date on the terminal; 2. Enable the feature that automatically actualizes on terminal, the time and date information received from network;
PROCEDURE:
GSM.R.6.1
TR-CPREQ- Time and Date Actualization SELFC-005a (NITZ Parameter)
3. Turn off and turn on the terminal; 4. Start a WAP session. 5. The terminal must actualize and display the date e time information received from network.
The terminal must actualize and display EXPECTED RESULT: the date e time information received from network.
Page 38 of 40
CODE VERSION DATE
03 4 26/03/10
1. Enable the feature CSP, through SIM Card applicative Vivo DDD (Path: VIVO Chip->Facilidades->Vivo DDD->Ativar 2. Enable the feature (in the terminal 1 menu) that hides the terminal 1 ID number.
PROCEDURE:
3. Make a call to a terminal 2 that has another area code XX. Ex. 0XXYYYYYYYY 4. Disable the feature (in the terminal 1 menu) that hides the terminal 1 ID number. 5. Hide the terminal 1 ID number (with the code #31#) and make a call to a terminal 2 that has another area code XX. Ex. #31#0XXYYYYYYYY The calling must be completed and the
GSM.R.9.1
CSP (Vivo DDD) + Hidden ID
EXPECTED RESULT: terminal 1 number must be hidden on the
terminal 2 display.
Page 39 of 40
CODE VERSION DATE
03 4 26/03/10
5.2
Load Tests
Not applicable. 5.3 Integration Tests
Not applicable. 5.4 Bug Tolerance Tests
Not applicable. 5.5 Interoperability Tests with other services
Not applicable. 5.6 Other Tests
Not applicable 6 7 OTHER ANNEX
Page 40 of 40

03 GSM - Gprs - Umts Terminals For The Operators of The TM Group Tests of Basic GSM Functionality

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

03 GSM - Gprs - Umts Terminals For The Operators of The TM Group Tests of Basic GSM Functionality

Enviado por

Direitos autorais:

Formatos disponíveis

TESTS SPECIFICATIONS GSM/GPRS/UMTS TERMINALS FOR THE OPERATORS OF THE TM GROUP: TESTS OF BASIC GSM FUNCTIONALITY

CODE VERSION DATE

05/10/05 1 11/01/07 Daniel Cordoba Cornejo Thiago Arantes Suedan

Jos Maria Daz Carmona

Otvio Augusto Ribeiro Gonalves

Fernanda Contrucci Terra

Telefonica Moviles Proprietary and Confidential

CODE VERSION DATE

CHANGES REGARDING PREVIOUS VERSION Insertion of new requirements codes (2010Q1).

File: 03-Basic GSM Functionality Tests.doc

CODE VERSION DATE

File: 03-Basic GSM Functionality Tests.doc

CODE VERSION DATE

CONDITIONS FOR THE REALIZATION OF THE TESTS

File: 03-Basic GSM Functionality Tests.doc

CODE VERSION DATE

Vendor Vendor - Remote Access Vendor - TM Resources Support TM

Conformance Interoperability End to End Service X

High Medium Low

File: 03-Basic GSM Functionality Tests.doc

CODE VERSION DATE

TEST CODE REQ. CODE

Logging in of the mobile phone (IMSI attach)

File: 03-Basic GSM Functionality Tests.doc

CODE VERSION DATE

TEST CODE REQ. CODE

Logging off of the mobile phone (IMSI detach)

IMSI Detach) when it is turned off.

5.1.1.2 MOBILE ORIGINATED CALLS

CODE VERSION DATE

Interoperability End to End Service

Mobile terminated 1 calls made from the fixed network

File: 03-Basic GSM Functionality Tests.doc

CODE VERSION DATE

TEST CODE REQ. CODE

Mobile originated international call

2. Confirm that communication is established. 3. The international call must be established.

File: 03-Basic GSM Functionality Tests.doc

CODE VERSION DATE

TEST CODE REQ. CODE

File: 03-Basic GSM Functionality Tests.doc

CODE VERSION DATE

TEST CODE REQ. CODE

Finishing of a call by a fixed network telephone

File: 03-Basic GSM Functionality Tests.doc

CODE VERSION DATE

TEST CODE REQ. CODE

TR-SERVC- Call to an engaged fixed VOICE-002a network number

CODE VERSION DATE

File: 03-Basic GSM Functionality Tests.doc

CODE VERSION DATE

Table 1: CLIP/CLIR tests

File: 03-Basic GSM Functionality Tests.doc

CODE VERSION DATE

Conformance Interoperability End to End Service X

High Medium Low X

TR-SERVCCLIP/CLIR Tests SUPPL-005a

File: 03-Basic GSM Functionality Tests.doc

CODE VERSION DATE

Vendor Vendor - Remote Access Vendor - TM Resources Support TM

Conformance Interoperability End to End Service X

High Medium Low

File: 03-Basic GSM Functionality Tests.doc