hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.2.4 Method of test
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.2.4.1 Initial conditions
|
The ME shall be connected to the SIM simulator, with all elementary files coded as default with the exception of:
EFSST (SIM Service Table)
Logically: CHV1 disable function allocated and activated.
Abbreviated dialling numbers allocated and activated.
PLMN selector allocated and activated.
Fixed dialling numbers not activated.
AoC allocated and activated.
Coding:
B1
B2
B3
B4
Value (binary)
xx0x1111
0011xx11
xxxxxxxx
0000xxxx
The coding of EFSST shall conform with the capabilities of the SIM used.
EFACM (Accumulated call meter)
Logically: 50 units
EFACMmax (Accumulated call meter maximum)
Logically: 150 units
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.2.4.2 Procedure
|
a) The MS is made to initiate a call. The call is established with AoCC e-parameters sent in a Facility IE in the CONNECT message, as given below. The MS returns the AoCC acknowledgement within 1 second of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the MS before or after the CONNECT ACKNOWLEDGE.
b) The call is maintained for 90 s, then terminated by the SS. During the call, the SIM-simulator monitors the time intervals between successive INCREMENT commands. As the final INCREMENT command will have occurred as a result of call termination, the time interval calculated since the prior INCREMENT command shall be ignored.
Maximum Duration of Test:
2 minutes.
Expected Sequence:
Step
Direction
Message
Comments
1
MS
The MS is made to initiate a call
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
SETUP
7
SS -> MS
CALL PROCEEDING
8
SS -> MS
ASSIGNMENT COMMAND
to a supported channel type
9
MS -> SS
ASSIGNMENT COMPLETE
10
SS -> MS
ALERTING
11
SS -> MS
CONNECT
As default message except contains Facility IE with contents as indicated in i below
Either A or B branch is taken
A12
MS -> SS
CONNECT ACKNOWLEDGE
A13
MS -> SS
FACILITY
As default message except contains Facility IE with contents as indicated in ii below
B12
MS -> SS
FACILITY
As default message except contains Facility IE with contents as indicated in ii below
B13
MS -> SS
CONNECT ACKNOWLEDGE
14
call duration 90 s after CAI information sent by SS,
15
SS -> MS
DISCONNECT
16
MS -> SS
RELEASE
17
SS -> MS
RELEASE COMPLETE
18
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeInformation component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3.
For ASN.1 description see default message contents in subclause 31.6.1.3.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below:
e-parameters
parameter
1
2
3
4
5
6
7
value
1
1
1
0
0
0
0
Values shown in table are in the format and have units as in 3GPP TS 02.24 subclause 3.
ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.
For ASN.1 description see default message contents in subclause 31.6.1.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.2.5 Test requirement
|
The MS shall, during a call, send INCREMENT commands to the SIM every 5 s.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.3 Call terminated when ACM greater than ACMmax
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.3.1 Definition
|
ACMmax gives the maximum value of ACM, at which the current calls shall be terminated and no further outgoing calls and charged incoming calls may be made (except emergency calls).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.3.2 Conformance requirement
|
ACM shall be incremented by the value of CCM.
If the ACMmax is valid, and the ACM becomes equal to or exceeds the value of the ACMmax, then all calls in progress, chargeable to the user, shall be terminated by the MS with cause value #68, once the chargeable interval determined by the CAI has elapsed, (except emergency calls).
Reference:
3GPP TS 02.24, subclause 4.3 part h and subclause 4.2.2.
3GPP TS 04.86, subclause 2.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.3.3 Test purpose
|
1. To verify that the ME increments the ACM by the correct number of units, even though this may take ACM above ACMmax.
2. To verify that the ME terminates the call with cause value #68.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.3.4 Method of test
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.3.4.1 Initial conditions
|
The ME shall be connected to a SIM or the SIM simulator, with all elementary files coded as default with the exception of:
EFSST (SIM Service Table)
Logically: CHV1 disable function allocated and activated.
Abbreviated dialling numbers allocated and activated.
PLMN selector allocated and activated.
Fixed dialling numbers not activated.
AoC allocated and activated.
Coding:
B1
B2
B3
B4
Value (Binary)
xx0x1111
0011xx11
xxxxxxxx
0000xxxx
The coding of EFSST shall conform with the capabilities of the SIM used.
EFACM (Accumulated call meter)
Logically: 80 units
EFACMmax (Accumulated call meter maximum)
Logically: 94 units
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.3.4.2 Procedure
|
a) The MS is made to initiate a call. The call is established with AoCC e-parameters sent in a Facility IE in the CONNECT message, as given below. The MS returns the AoCC acknowledgement within 1 second of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the MS before or after the CONNECT ACKNOWLEDGE.
b) The call is maintained until cleared by the MS (after 30 s) with cause value #68.
c) The contents of ACM are checked.
Maximum Duration of Test:
2 minutes.
Expected Sequence:
Step
Direction
Message
Comments
1
MS
The MS is made to initiate a call
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
SETUP
7
SS -> MS
CALL PROCEEDING
8
SS -> MS
ASSIGNMENT COMMAND
to a supported channel type
9
MS -> SS
ASSIGNMENT COMPLETE
10
SS -> MS
ALERTING
11
SS -> MS
CONNECT
As default message except contains Facility IE with contents as indicated in i below
Either A or B branch is taken
A12
MS -> SS
CONNECT ACKNOWLEDGE
A13
MS -> SS
FACILITY
As default message except contains Facility IE with contents as indicated in ii below
B12
MS -> SS
FACILITY
As default message except contains Facility IE with contents as indicated in ii below
B13
MS -> SS
CONNECT ACKNOWLEDGE
14
call duration 30 s after CAI information sent by SS
15
MS -> SS
DISCONNECT
Cause value #68
16
SS -> MS
RELEASE
17
MS -> SS
RELEASE COMPLETE
18
MS -> SS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeInformation component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3.
For ASN.1 description see default message contents in subclause 31.6.1.3.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below:
e-parameters
parameter
1
2
3
4
5
6
7
value
10
10
1
0
0
0
0
Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3.
ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.
For ASN.1 description see default message contents in subclause 31.6.1.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.3.5 Test requirement
|
1) The MS shall terminate the call correctly 30 s after CAI was sent.
2) The value of ACM shall be 100 units.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.4 Response codes of increase command
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.4.1 Definition
|
ACM has a maximum value in terms of coding, and an attempt by the ME to exceed that value by sending an INCREASE command shall result in an error message from the SIM.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.4.2 Conformance requirement
|
The ME shall perform the increasing procedure, sending the amount to be increased.
The running accumulated charge shall be stored in the ACM of the SIM.
Where this charge cannot be stored in the MS, use of the telecommunications service shall be prevented.
References:
3GPP TS 11.11, subclause 11.5.3; 3GPP TS 02.86, subclauses 2.2.1 and 2.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.4.3 Test purpose
|
To verify that the ME clears a charged call if the SIM indicates that the ACM cannot be increased.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.4.4 Method of test
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.4.4.1 Initial conditions
|
The ME shall be connected to the SIM simulator, with all elementary files coded as default with the exception of:
EFSST (SIM Service Table)
Logically: CHV1 disable function allocated and activated.
Abbreviated dialling numbers allocated and activated.
PLMN selector allocated and activated.
Fixed dialling numbers not activated.
AoC allocated and activated.
Coding:
B1
B2
B3
B4
Value (binary)
xx0x1111
0011xx11
xxxxxxxx
0000xxxx
The coding of EFSST shall conform with the capabilities of the SIM used.
EFACM (Accumulated call meter)
Logically: (Maximum‑10) units
EFACMmax (Accumulated call meter maximum)
Logically: (Maximum‑2) units
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.4.4.2 Procedure
|
a) The MS is made to initiate a call. The call is established with AoCC e-parameters sent in a Facility IE in the CONNECT message, as given below. The MS returns the AoCC acknowledgement within 1 second of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the MS before or after the CONNECT ACKNOWLEDGE.
b) After an interval has elapsed, the ME increments the ACM. When an INCREASE command is received, the SIM-sim sends back the error "98 50".
c) Conditions are reset to those described in the initial conditions. Steps a) and b) of the test are repeated, except that the error code sent by the SIM simulator at step b) is now "6F xx".
d) Conditions are reset to those described in the initial conditions. Steps a) and b) of the test are repeated, except that the error code sent by the SIM simulator at step b) is now "92 40".
Maximum Duration of Test:
3 minutes.
Expected Sequence:
Step
Direction
Message
Comments
1
MS
The MS is made to initiate a call
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
SETUP
7
SS -> MS
CALL PROCEEDING
8
SS -> MS
ASSIGNMENT COMMAND
to a supported channel type
9
MS -> SS
ASSIGNMENT COMPLETE
10
SS -> MS
ALERTING
11
SS -> MS
CONNECT
As default message except contains Facility IE with contents as indicated in i below
Either A or B branch is taken
A12
MS -> SS
CONNECT ACKNOWLEDGE
A13
MS -> SS
FACILITY
As default message except contains Facility IE with contents as indicated in ii below
B12
MS -> SS
FACILITY
As default message except contains Facility IE with contents as indicated in ii below
B13
MS -> SS
CONNECT ACKNOWLEDGE
14
call duration approx 10s after CAI information sent by SS
15
MS -> SS
DISCONNECT
16
SS -> MS
RELEASE
17
MS -> SS
RELEASE COMPLETE
18
MS -> SS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeInformation component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below:
e-parameters
parameter
1
2
3
4
5
6
7
value
20
10
1
0
0
0
0
Values shown in table are in the format and have units as in 3GPP TS 02.24 subclause 3.
ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
27.21.4.5 Test requirement
|
In each of the three cases, as described in steps b), c) and d) of the procedure, the MS shall terminate the call correctly when it receives an indication from the SIM that the ACM cannot be incremented.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
28 Test of autocalling restrictions
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
28.1 General
|
It is essential that all autocalling apparatus is prevented from continuously dialling a given number, to avoid machines repeatedly disturbing PSTN subscribers in error, or numerous repeat attempts to unobtainable numbers which cause waste of valuable network resources. Therefore autocalling restrictions are defined by 3GPP TS 02.07.
The tests shall be performed using all of the call methods specified by the supplier in the PIXIT statement (annex 3). The supplier shall state any autocalling procedures implemented and how many times they can be repeated to a single number and the minimum re-attempt interval(s), i.e. the complete re-try schedule or algorithm with parameter values. The supplier shall further describe any automatic methods for making repeated calls to a single number. The supplier shall also state in the PIXIT statement (annex 3) the number of B-party numbers that can be stored on the list of blacklisted numbers as described in 3GPP TS 02.07, annex A.
For an external R-interface the supplier shall state in the PIXIT statement (annex 3) the procedure for autocalling restrictions for that interface and the possible parameter settings for the number of times the LTE can make a re-attempt and the minimum accepted time between re-attempts accepted by the MS. The conditions for clearing the autocalling constraints shall be stated in the PIXIT statement (annex 3).
For external interfaces the LTE must be programmed so that it clearly attempts to violate the autocalling constraints.
28.2 Constraining the access to a single number (3GPP TS 02.07 category 3)
During this test the SETUP messages shall contain the same B-party number.
No manual intervention shall be performed except to initiate and end the test.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
28.2.1 Conformance requirement
|
A repeat call attempt may be made when a call attempt is unsuccessful for the reasons listed below (as defined in 3GPP TS 04.08 / 3GPP TS 24.008).
These reasons are classified in three major categories:
1. "Busy destination".
2. "Unobtainable destination - temporary".
3. "Unobtainable destination - permanent/long term".
NOTE: Cause values for each category are defined in 3GPP TS 02.07, annex A.
The table below describes a repeat call restriction pattern to any B number. This pattern defines a maximum number (n) of call repeat attempts; when this number n is reached, the associated B number shall be blacklisted by the MT until a manual re-set at the MT is performed in respect of that B number. When a repeat attempt to anyone B number fails, or is blacklisted, this does not prevent calls being made to other B numbers.
For the categories 1 and 2 above, n shall be 10; for category 3, n shall be 1.
Call attempt
Minimum duration between call attempts
Initial call attempt
-
1st repeat attempt
5 s
2nd repeat attempt
1 min
3rd repeat attempt
1 min
4th repeat attempt
1 min
5th repeat attempt
3 min
.
.
nth repeat attempt
3 min
Reference:
3GPP TS 02.07, annex A.
Purpose of the test
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
28.2.2 Test purpose
|
To ensure the correct behaviour of the MS to 3GPP TS 02.07 Category 3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
28.2.3 Method of test
|
Initial condition.
There shall be no numbers in the list of blacklisted numbers in the MS. The time set between the first re-attempt and the next re-attempt is set to the minimum value possible. The number of re-attempts is set to the lowest possible number greater than 1 that is supported by the MS. The autocalling function is invoked for the B-party number to be used during the test.
Specific PICS statements:
• Implementation of cause number 27 of busy autocalling in category 2 (TSPC_AddInfo_Impl_CNr27_Cat2)
• Implementation of cause number 27 of busy autocalling in category 3 (TSPC_AddInfo_Impl_CNr27_Cat3)
PIXIT statements:
- Description of auto calling management:
- selection of the auto calling;
- indication that the call failed and a re-try is attempted;
- indication that a call finally failed;
- number of B-party numbers that can be stored in the list of blacklisted numbers
- Non standard keystroke sequences to be used on the EMMI (in line with 3GPP TS 11.10, clause 36).
Foreseen Final State of the MS
The MS has a valid TMSI. It is "idle updated".
Test Procedure
A MS initiated generic call setup is performed up to and including CIPERING MODE COMPLETE. The SS then releases the establishment with a cause value from Category 3 3GPP TS 02.07 annex A.
The MS will make one further generic call setup attempt invoked by the auto calling function after a channel release is sent out by the SS.
Step
Direction
Message
Comments
1
MS
"called number" entered
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "originating call".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM.
5
SS -> MS
AUTHENTICATION REQUEST
6
MS -> SS
AUTHENTICATION RESPONSE
7
SS -> MS
CIPHERING MODE COMMAND
8
MS -> SS
CIPHERING MODE COMPLETE
9
SS
SS starts ciphering.
10
MS -> SS
SETUP
11
SS -> MS
CIPHERING MODE COMMAND
12
MS -> SS
CIPHERING MODE COMPLETE
13
SS
SS stops ciphering
14
SS -> MS
RELEASE COMPLETE
Cause value from category 3 of 3GPP TS 02.07, annex A.
15
SS -> MS
CHANNEL RELEASE
The main signalling link is released
16
The MS is invoking the auto calling function. The time between step 15 and 17 must be minimum 5 sec.
17
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "originating call".
18
SS -> MS
IMMEDIATE ASSIGNMENT
19
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM.
20
SS -> MS
AUTHENTICATION REQUEST
21
MS -> SS
AUTHENTICATION RESPONSE
22
SS -> MS
CIPHERING MODE COMMAND
23
MS -> SS
CIPHERING MODE COMPLETE
24
SS
SS starts ciphering.
25
MS -> SS
SETUP
26
SS -> MS
CIPHERING MODE COMMAND
27
MS -> SS
CIPHERING MODE COMPLETE
28
SS
SS stops ciphering
29
SS -> MS
RELEASE COMPLETE
Cause value from category 3 of 3GPP TS 02.07, annex A.
30
SS -> MS
CHANNEL RELEASE
The main signalling link is released
31
MS
Clear the auto calling constraint by manual intervention after a minimum of 2 minutes from step 30.
28.3 Constraining the access to a single number (3GPP TS 02.07 categories 1 and 2)
During this test the SETUP messages shall contain the same B-party number.
No manual intervention shall be performed except to initiate and end the test.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
28.3.1 Conformance requirement
|
The MS must fulfil the requirements for category 1 and 2, see subclause 28.2.1
Reference:
3GPP TS 02.07, annex A.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
28.3.2 Test purpose
|
To ensure the correct behaviour of the MS to 3GPP TS 02.07 Categories 1 and 2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
28.3.3 Method of test
|
Initial condition.
There shall be no numbers in the list of blacklisted numbers in the MS. The re-try scheme is set to give the shortest possible intervals between re-tries. The number of re-attempts is set to the maximum possible number (N) that is supported by the MS. The autocalling function is invoked for the B-party number to be used during the test.
Specific PICS statements:
• Implementation of cause number 27 of busy autocalling in category 2 (TSPC_AddInfo_Impl_CNr27_Cat2)
• Implementation of cause number 27 of busy autocalling in category 3 (TSPC_AddInfo_Impl_CNr27_Cat3)
PIXIT statements:
- Description of auto calling management:
- selection of the auto calling;
- indication that the call failed and a re-try is attempted;
- indication that a call finally failed;
- number of B-party numbers that can be stored in the list of blacklisted numbers
- Non standard keystroke sequences to be used on the EMMI (in line with 3GPP TS 11.10, clause 36).
Foreseen Final State of the MS
The MS has a valid TMSI. It is "idle updated".
Test Procedure
A, MS initiated, generic call setup is performed up to and including CIPHERING MODE COMPLETE. The SS then releases the establishment with a cause value from category 1 or 2 ( 3GPP TS 02.07, annex A).
The MS is continuously making new generic call setup attempts invoked by the auto calling function after each CHANNEL RELEASE from the SS.
Step
Direction
Message
Comments
1
MS
"called number" entered
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "originating call".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM.
5
SS -> MS
AUTHENTICATION REQUEST
6
MS -> SS
AUTHENTICATION RESPONSE
7
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
8
MS -> SS
CIPHERING MODE COMPLETE
9
SS
SS starts ciphering.
10
MS -> SS
SETUP
11
SS -> MS
CIPHERING MODE COMMAND
12
MS -> SS
CIPHERING MODE COMPLETE
13
SS
SS stops ciphering
14
SS -> MS
RELEASE COMPLETE
Cause value from category 1 or 2 of 3GPP TS 02.07, annex A. This shall be chosen randomly, from both categories. Cause no. 27 shall be excluded if the MS has implemented in category 3 of 3GPP TS 02.07, as declared in PIXIT statement
15
SS -> MS
CHANNEL RELEASE
The main signalling link is released
16
The MS is invoking the auto calling function. 1: At the first re-attempt the time between step 15 and 17 must be minimum 5 sec. 2: At the 2nd, 3rd and 4th re-attempt the time between step 15 and 17 must be minimum 1 min. 3: At the 5th to 10th re-attempt the time between step 15 and 17 must be minimum 3 min.
17
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "originating call".
18
SS -> MS
IMMEDIATE ASSIGNMENT
19
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM.
20
SS -> MS
AUTHENTICATION REQUEST
21
MS -> SS
AUTHENTICATION RESPONSE
22
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
23
MS -> SS
CIPHERING MODE COMPLETE
24
SS
SS starts ciphering.
25
MS -> SS
SETUP
26
SS -> MS
CIPHERING MODE COMMAND
27
MS -> SS
CIPHERING MODE COMPLETE
28
SS
SS stops ciphering
29
SS -> MS
RELEASE COMPLETE
Cause value from category 1 or 2 of 3GPP TS 02.07, annex A. This shall be chosen randomly, from both categories. Cause no. 27 shall be excluded if the MS has implemented in category 3 of 3GPP TS 02.07, as declared in PIXIT statement
30
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
31
The auto calling function shall repeat step 16 to 30 (N‑1) times. The MS shall not make more than maximum 10 re-attempts.
32
MS
Clear the auto calling constraint by manual intervention after a minimum of 4 minutes from step 31. Following the final completion of step 31 the MS initiate a call prior to manual intervention.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
28.4 Behaviour of the MS when its list of blacklisted numbers is full
|
The number of B-party numbers that can be stored in the list of blacklisted numbers, as stated in the PIXIT statement (annex 3), is M.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
28.4.1 Conformance requirement
|
The number of B numbers that can be held in the blacklist is at the manufacturer’s discretion but there shall be at least 8. However, when the blacklist is full the MT shall prohibit further automatic call attempts to any one number until the blacklist is manually cleared at the MT in respect of one or more B numbers.
Reference:
3GPP TS 02.07, annex A.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
28.4.2 Test purpose
|
To ensure the correct behaviour of the MS when its list of blacklisted numbers is full.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
28.4.3 Method of test
|
Initial condition.
The list of blacklisted numbers, in the MS, shall be full. This may be achieved as described in the procedure in subclause 28.2, applied to M B-party numbers.
Specific PICS statements:
• Implementation of cause number 27 of busy autocalling in category 2 (TSPC_AddInfo_Impl_CNr27_Cat2)
• Implementation of cause number 27 of busy autocalling in category 3 (TSPC_AddInfo_Impl_CNr27_Cat3)
PIXIT statements:
- Description of auto calling management:
- selection of the auto calling;
- indication that the call failed and a re-try is attempted;
- indication that a call finally failed;
- number of B-party numbers that can be stored in the list of blacklisted numbers.
- Non standard keystroke sequences to be used on the EMMI (in line with 3GPP TS 11.10, clause 36).
Foreseen Final State of the MS
The MS has a valid TMSI. It is "idle updated".
Test Procedure
The autocalling function is invoked for a B-party number that is not in the list of blacklisted numbers.
Clear the autocalling constraint by manual intervention after a minimum of 2 minutes.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
28.4.4 Test requirements
|
The MS must not initiate a call.
Step
Direction
Message
Comments
1
MS
"called number" entered
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "originating call".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM.
5
SS -> MS
AUTHENTICATION REQUEST
6
MS -> SS
AUTHENTICATION RESPONSE
7
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
8
MS -> SS
CIPHERING MODE COMPLETE
9
SS
SS starts ciphering.
10
MS -> SS
SETUP
11
SS -> MS
CIPHERING MODE COMMAND
SS stops deciphering after sending the message.
12
MS -> SS
CIPHERING MODE COMPLETE
13
SS
SS stops ciphering.
14
SS -> MS
RELEASE COMPLETE
Cause value from category 3 of 3GPP TS 02.07, annex A. This shall be chosen randomly. Cause no. 27 shall be excluded if the MS has implemented in category 2 of 3GPP TS 02.07, as declared in PIXIT statement
15
SS -> MS
CHANNEL RELEASE
The main signalling link is released
16
The MS is invoking the auto calling function. The time between step 15 and 17 must be minimum 5 sec.
17
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "originating call".
18
SS -> MS
IMMEDIATE ASSIGNMENT
19
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM.
20
SS -> MS
AUTHENTICATION REQUEST
21
MS -> SS
AUTHENTICATION RESPONSE
22
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
23
MS -> SS
CIPHERING MODE COMPLETE
24
SS
SS starts ciphering.
25
MS -> SS
SETUP
26
SS -> MS
CIPHERING MODE COMMAND
SS stops deciphering after sending the message.
27
MS -> SS
CIPHERING MODE COMPLETE
28
SS
SS stops ciphering.
29
SS -> MS
RELEASE COMPLETE
Cause value from category 3 of 3GPP TS 02.07, annex A. This shall be chosen randomly. Cause no. 27 shall be excluded if the MS has implemented in category 2 of 3GPP TS 02.07, as declared in PIXIT statement
30
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
31
The test shall be repeated from steps 1 to 30 using a different B party number each time until the blacklist is full as declared in PIXIT statement. The MS shall not make more than a maximum of 1 re-attempt on each number.
32
The test shall be repeated from steps 1 to 15 using a non-blacklisted B party number
33
SS
The SS verifies that the MS does not initiate an automatic re-attempt for a minimum of 2 minutes from step 32.
34
MS
Clear the auto calling constraint by manual intervention.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29 Testing of bearer services
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.1 General
|
In 3GPP TS 07.01, subclause 2 the reference configurations for access to the data services of a GSM PLMN are described. For testing purposes only the following classifications are used:
- MT2 configuration (Um- and R-interface available for testing).
- Configurations (only Um-interface available for testing) where it is possible to enable the MS to issue or accept a data call and send data over the Um-interface. An MT1 connected to an ISDN TE belongs to this type.
- For efficient testing it is essential that such configurations have some means to specifically activate every function towards the Um-interface the MS will perform during operation.
- The correctness of the data bits transferred to the Um-interface will not be tested in these configurations. However the correctness of the 3GPP TS 04.21 frames sent by the MS will be tested.
Testing the S-interface for the MT1 configuration is for further study.
For some tests it is of no importance whether the call is MO or MT. However, there might be configurations allowing the call to be established only from one side. In this case the appropriate actions shall be taken to establish the call.
In all other cases the data call shall be set up by the SS (i.e. MT) with an appropriate BC-IE which is supported by the MS.
At the beginning of all tests the MS shall be in the idle updated state.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2 Testing of transparent data services
|
During all the tests the 3GPP TS 04.21 frames received as output of the channel coder in the SS shall be checked for correctness against 3GPP TS 04.21; this means checking that:
- S bits are coded as zeroes unless otherwise specified;
- the E bits have the correct value (for the synchronous services);
- the data bits correctly include the start and stop bits (for the asynchronous services).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.1 Verification of synchronization
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.1.1 Definition
|
-29.2.1.2 Conformance requirement
A Mobile Stations in MT2 configuration has to comply with all requirements whilst for other configurations some of the requirements are not relevant. These restrictions are explicitly indicated in subclause 29.2.1.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.1.3 Test purpose
|
This test verifies the correct synchronization procedure of user data and status information which are mapped on modified ITU-T Recommendation V.110 frames (as per 3GPP TS 04.21).
As V-series interfaces are supported in full duplex mode, it will test the capability to synchronize these frames in the direction from the TAF to the IWF and vice versa.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.1.4 Method of test
|
The test shall be carried out under ideal radio conditions for all bearer services and user rates in transparent mode that are supported by the MS in case of mobile originated and terminated calls and in-call modification. The setting of Bearer Capability Information Elements in signalling messages sent to the MS by the SS must be supported by the MS for the bearer service(s) to be tested.
NOTE 1: Since "steady state" is implementation dependent, there is no means to define a test "steady state detected". However, the whole testing procedure is limited to 1s. This includes an implicit upper time limit for the MS to detect a steady state. A MS failing this test is highly estimated to never detect a steady state under real radio conditions.
NOTE 2: ti, as used in the description of the test procedures, are points of time, not timers.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.1.4.1 Procedure for Mobile Originated Calls
|
a) The MS is connected to the System Simulator at the Um interface and to the LTE using the appropriate R interface in case of MT2 only.
b) The MS is configured for data transmission. In the case of MT2 configurations, the LTE shall set the signalling lines of the R interface Ct 105, Ct 108.2 for V-series interface to ON.
c) A mobile originated call shall be set up.
d) At the reception of the SETUP message sent by the MS the SS shall send a CONNECT message and starts sending "1/OFF". t1 is at the completion of the CONNECT message.
e) The reception of "1/OFF" at the SS side (see table 29‑1) defines t2. t2 will be reset at the reception of again "1/OFF" after an interruption of continuous "1/OFF" pattern.
f) The SS checks bits S1, S3, S6 and S8 of the modified ITU-T Recommendation V.110 frames (as described in 3GPP TS 04.21). Let t3 be the time when all four bits change from OFF to ON (i.e. if t<t3, (S1,S3,S6,S8) <> (0,0,0,0) and t>=t3,(S1,S3,S6,S8) = (0,0,0,0)).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.1.4.2 Procedure for Mobile Terminated Calls
|
a) The MS is connected to the System Simulator at the Um interface and to the LTE using the appropriate R interface in case of MT2 only.
b) The MS is configured for data transmission. In the case of MT2 configurations, The LTE shall set the signalling lines of the R interface Ct. 105, Ct 108.2 for V-series interface to ON.
c) A mobile terminated call shall be set up.
d) At the reception of CONNECT the SS sends CONNECT ACKNOWLEDGE. t1 is at the completion of the CONNECT ACKNOWLEDGE message.
e) The reception of "1/OFF" at the SS side (see table 29‑1) defines t2. t2 will be reset at the reception of again "1/OFF" after an interruption of continuous "1/OFF" pattern.
f) The SS checks bits S1, S3, S6 and S8 of the modified ITU-T Recommendation V.110 frames (as described in 3GPP TS 04.21). Let t3 be the time when all four bits change from OFF to ON (i.e. if t<t3, (S1,S3,S6,S8) <> (0,0,0,0) and t>=t3,(S1,S3,S6,S8) = (0,0,0,0)).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.1.4.3 Procedure for In Call Modification
|
a) The MS is connected to the System Simulator at the Um interface and to the LTE using the appropriate R interface in case of MT2 only.
b) The MS is configured for data transmission. In the case of MT2 configurations, the LTE shall set the signalling lines of the R interface Ct. 105, Ct 108.2 for V-series interface to ON.
c) A speech call shall be established with a SETUP message containing two bearer capabilities for speech and the bearer service to be tested.
d) The MS shall start the ICM procedure with a bearer capability information element supporting the bearer service to be tested.
e) At the reception of the MODIFY message sent by the MS the SS shall send a CHANNEL MODE MODIFY message.
f) At the reception of the CHANNEL MODE MODIFY ACKNOWLEDGE message the SS shall send a MODIFY COMPLETE message. t1 is at the completion of the MODIFY COMPLETE message.
g) The reception of "1/OFF" (see table 29‑1) defines t2. t2 will be reset at the reception of again "1/OFF" after an interruption of continuous "1/OFF" pattern.
h) The SS checks bits S1, S3, S6 and S8 of the modified ITU-T Recommendation V.110 frames (as described in 3GPP TS 04.21). Let t3 be the time when all four bits change from OFF to ON (i.e. if t<t3, (S1,S3,S6,S8) <> (0,0,0,0) and t>=t3,(S1,S3,S6,S8) = (0,0,0,0)).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.1.5 Test requirements
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.1.5.1 Test requirements for Mobile Originated Calls
|
1) After step b) Cts 106, 107, 109 must be in the "OFF" condition, data line 104 shall be set to "1".
2) At t1 + 500 ms Ct 107 must still be in the "OFF" condition.
3) Between t1 + 500 ms and t1 + 1 000 ms Ct 107 must switch to the "ON" condition. This indicates successful synchronization of TAF towards IFE.
4) Between t2 and t3 the SS must receive continuous "1/OFF" frames.
5) The time between t2 and t3 must be more than 450 ms.
6) At t1 +1000ms the SS must check 3GPP TS 04.21 frames sent by the MS with SA and SB bits (i.e. bits S1, S3, S4, S6, S8 and S9) set to "ON". This indicates successful synchronization of IFE towards TAF. At this point of time the whole synchronization procedure has been completed successfully.
NOTE: If the MS is not MT2, only requirements 4 to 6 apply.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.1.5.2 Test requirements for Mobile Terminated Calls
|
1) After step b) Cts 106, 107, 109 must be in the "OFF" condition, data line 104 shall be set to "1".
2) At t1 + 500 ms Ct 107 must still be in the "OFF" condition.
3) Between t1 + 500 ms and t1 + 1 000 ms Ct 107 must switch to the "ON" condition. This indicates successful synchronization of TAF towards IFE.
4) Between t2 and t3 the SS must receive continuous "1/OFF" frames.
5) The time between t2 and t3 must be more than 450 ms.
6) At t1 +1000 ms the SS must check 3GPP TS 04.21 frames sent by the MS with SA and SB bits (i.e. bits S1, S3, S4, S6, S8 and S9) set to "ON". This indicates successful synchronization of IFE towards TAF. At this point of time the whole synchronization procedure has been completed successfully.
NOTE: If the MS is not MT2, only requirements 4 to 6 apply.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.1.5.3 Test requirements for In Call Modification
|
1) After step b) Cts 106, 107, 109 must be in the "OFF" condition, data line 104 shall be set to "1".
2) At t1 + 500 ms Ct 107 must still be in the "OFF" condition.
3) Between t1 + 500 ms and t1 + 1 000 ms Ct 107 must switch to the "ON" condition. This indicates successful synchronization of TAF towards IFE.
4) Between t2 and t3 the SS must receive continuous "1/OFF" frames.
5) The time between t2 and t3 must be more than 450 ms.
6) At t1 +1 000 ms the SS must check 3GPP TS 04.21 frames sent by the MS with SA and SB bits (i.e. bits S1, S3, S4, S6, S8 and S9) set to "ON". This indicates successful synchronization of IFE towards TAF. At this point of time the whole synchronization procedure has been completed successfully.
NOTE: If the MS is not MT2, only requirements 4 to 6 apply.
Table 29-1: Definition of synchronization pattern "1/OFF"
3GPP TS 04.21 60 bits frame
Synch-Frame
Data-Frame
1
1
1
1
1
1
1
D1
D2
D3
D4
D5
D6
S1
1
1
1
1
1
1
1
D7
D8
D9
D10
D11
D12
X
1
1
1
1
1
1
1
D13
D14
D15
D16
D17
D18
S3
1
1
1
1
1
1
1
D19
D20
D21
D22
D23
D24
S4
1
1
1
1
1
1
1
E4
E5
E6
E7
D25
D26
S27
1
1
1
1
1
1
1
D28
D29
D30
S6
D31
D32
S33
1
1
1
1
1
1
1
D34
D35
D36
X
D37
D38
S39
1
1
1
1
1
1
1
D40
D41
D42
S8
D43
D44
S45
1
1
1
1
D46
D47
D48
S9
Table 29-1: Definition of synchronization pattern "1/OFF"
3GPP TS 04.21 36 bits frame
Synch-Frame
Data-Frame
1
1
1
1
1
1
1
1
D1
D2
D3
S1
D4
D5
D6
X
1
1
1
1
1
1
1
1
D7
D8
D9
S3
D10
D11
D12
S4
1
1
1
1
1
1
1
1
E4
E5
E6
E7
D13
D14
D15
S6
1
1
1
1
1
1
1
1
D16
D17
D18
X
D19
D20
D21
S8
1
1
1
1
1
D22
D23
D24
S9
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.2 Filtering of channel control information for transparent BCs
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.2.1 Definition
|
-29.2.2.2 Conformance requirement
An MS supporting data services shall decode and filter channel control information received over the Um-interface.
1. 3GPP TS 04.21, clause 7;
2. 3GPP TS 07.01, subclause 8.2.2;
3. 3GPP TS 07.02, subclause 3.2.1 (for asynchronous bearer services only);
4. 3GPP TS 07.03, subclauses 4.2.1 and 4.2.2 (for synchronous bearer services only).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.2.3 Test purpose
|
The purpose of this test is to verify the correct decoding and filtering of channel control information from the 3GPP TS 04.21 frames to the V.24/X.21 interface circuits. The tests apply after synchronization has been completed.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.2.4 Method of test
|
The Test shall be carried out for all user data rates supported by the MS (see below) and the circuits CT106 (V.24) (interface circuit bit X) and CT109 (V.24) (interface circuit bit SB) and I (X.21) (S-bits). The test shall be carried out only for those frame formats and circuits which are supported by the MS. The test is to be repeated for all circuits.
Let T(ON-OFF) and T(OFF-ON) be the timers to integrate the ON-OFF and the OFF-ON transition respectably for the circuit to be tested as stated in 3GPP TS 07.01, subclause 8.2.2.
Procedure:
a) A data call shall be set up between the SS and the MS with a combination of BCIEs (see below) supported by the MS. The interface circuit bit(s) in the 3GPP TS 04.21 frame shall be set to OFF. The next step shall be entered 6 s after CT107 has been set to ON by the MS.
b) The SS shall set the interface circuit bit(s) to continuously ON, wait half of T(OFF-ON) and then set the interface circuit bit(s) again to continuously OFF. The SS shall wait 6 s before entering the next step.
c) The SS shall set the interface circuit bit(s) to continuously ON, wait twice T(OFF-ON) and then set the interface circuit bit(s) again to continuously OFF. The SS shall wait 6 s before entering the next step.
d) The SS shall set interface circuit bit(s) to continuously ON and wait 6 s before entering the next step
e) The SS shall set the interface circuit bit(s) to continuously OFF, wait half of T(ON-OFF) and then set the interface circuit bit(s) again to continuously ON. The SS shall wait 6 s before entering the next step.
f) The SS shall set the interface circuit bit(s) to continuously OFF, wait twice T(ON-OFF) and then set the interface circuit bit(s) again to continuously ON. The SS shall wait 6 s before entering the next step.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.2.5 Test requirements
|
1) After step a) the interface circuit at the R-interface shall be OFF.
2) During step b) the interface circuit at the R-interface shall not change.
3) During step c) the interface circuit at the R-interface shall change to ON and then again to OFF.
4) After step d) the interface circuit at the R-interface shall be ON.
5) During step e) the interface circuit at the R-interface shall not change.
6) During step f) the interface circuit at the R-interface shall change to OFF and then again to ON.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.2.6 BCIE
|
The following combinations shall be considered (ref. 3GPP TS 07.01, annex 2):
a) User Rate = 9,6 kbit/s;
b) User Rate = 4,8 kbit/s;
c) User Rate = 2,4 kbit/s;
d) User Rate = 1,2 kbit/s;
e) User Rate = 1 200/75 bit/s (only with asynchronous Bearer Services);
f) User Rate = 300 bit/s (only with asynchronous Bearer Services).
The remaining parameters of the BCIE and the channel type (FR/HR) shall be set to a value supported by the MS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3 Correct Terminal Compatibility Decision
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.1 Negotiation of Radio Channel Requirement (RCR)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.1.1 Test purpose
|
To verify that the MS ignores the RCR field in a mobile terminating setup and negotiates according to its capabilities and to the service requested. A Dual Rate support MS shall accept the channel rate chosen be the network in the ASSIGNMENT COMMAND message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.1.2 Initial conditions
|
For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question.
Specific PICS statements:
-
PIXIT statements:
- Way to receive the call
- Features which must be activated by MMI before an incoming call can be accepted.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.1.3 Test method
|
a) The SS transmits a SETUP message containing a BC-IE among those declared as supported by the MS and with the RCR field set to "01".
b) The SS sends a ASSIGNMENT COMMAND message with a channel type set to "Full Rate" unless the CALL CONFIRM message indicates "dual rate mobile station/full rate preferred". In that case, the channel type is set to "Half Rate".
c) The call is released and steps a) and b) are repeated with RCR field set to "00".
d) The call is released and steps a) and b) are repeated with RCR field set to "10".
e) The call is released and steps a) and b) are repeated with RCR field set to "11".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.1.4 Test requirements
|
1) After step a), the MS shall send a CALL CONFIRM message. If present, the BC-IE shall be coded according to 3GPP TS 07.01. If any other parameters than those listed below have different values than those of the BC-IE included in the SETUP, then the test shall be failed:
- Number of stop bits, number of data bits, parity;
- Connection Element, Structure, Intermediate rate, User Information Layer 2 Protocol, Modem Type, NIRR;
- Radio Channel Requirement.
2) After step b), the MS shall answer to the ASSIGNMENT COMMAND message with an ASSIGNMENT COMPLETE message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.2 Negotiation of Connection Element (CE)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.2.1 Test purpose
|
To verify that the MS accepts a CE equal to "Both, Transparent Preferred" or "Both Non Transparent Preferred" and indicates its choice in the CALL CONFIRM message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.2.2 Initial condition
|
For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question.
Specific PICS statements:
•
PIXIT statements:
- Way to receive the call
- Features which must be activated by MMI before an incoming call can be accepted.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.2.3 Test method
|
a) The SS transmits a SETUP message containing a BC-IE among those declared as supported by the MS and with the CE field set to "Both Transparent Preferred". The RCR parameter shall be set to "Full Rate". The UIL2P is not included (i.e. octet 7 is absent). The NIRR is set to "no meaning" (i.e. 0). The IR is set to "16 kbit/s". The modem type is any according to declared capabilities. The user rate is any according to declared capabilities and modem type.
b) The call is released and step a) is repeated with CE field set to "Both Non Transparent Preferred".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.2.4 Test requirements
|
After step a), the MS shall send a CALL CONFIRM message. The BC-IE shall be present and shall be coded according to 3GPP TS 07.01 and shall correspond to a Bearer Service or Teleservice supported by the MS. The CE shall be set to either "Transparent" or "Non Transparent" If any other parameters than those listed bellow have different values than those of the BC-IE included in the SETUP, then the test shall be failed:
- number of stop bits, number of data bits, parity;
- Connection Element, Structure, Intermediate rate, User Information Layer 2 Protocol, Modem Type, NIRR;
- Radio Channel Requirement.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.3 Negotiation of Number of Stop Bits, Number of Data bits, and Parity
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.3.1 Test purpose
|
To verify that the MS accepts any value for the parameters Number of Stop Bits, Number of Data bits, and Parity in a mobile terminating Setup and negotiates according to its capabilities and to the service requested.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.3.2 Initial condition
|
For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question.
Specific PICS statements:
-
PIXIT statements:
- Way to receive the call
- Features which must be activated by MMI before an incoming call can be accepted.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.3.3 Test method
|
a) The SS transmits a SETUP message containing a BC-IE among those declared as supported by the MS and corresponding to an asynchronous Bearer Service, and with the Number of Stop Bits (NSB) field set to "1 bit", the Number of Data Bits (NDB) field set to "8 bits", and the Parity field set to "none".
b) The call is released and step a) is repeated with the Number of Stop Bits (NSB) field set to "2 bit", the Number of Data Bits (NDB) field set to "7 bits", and the Parity field set to "odd".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.3.4 Test requirements
|
After steps a) and b), the MS shall send a CALL CONFIRMED message. If present, the BC-IE shall be coded according to 3GPP TS 07.01 and shall correspond to a Bearer Service supported by the MS. If any other parameters than those listed bellow have different values than those of the BC-IE included in the SETUP, then the test shall be failed:
- Number of stop bits, number of data bits, parity;
- Connection Element, Structure, Intermediate rate, User Information Layer 2 Protocol, Modem Type, NIRR;
- Radio Channel Requirement.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.4 Negotiation of Modem Type
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.4.1 Test purpose
|
To verify that the MS accepts the value "autobauding type 1" for the parameter Modem Type in a mobile terminating Setup and negotiates according to its capabilities and to the service requested.
NOTE: It is not clear if the MS should also accept any possible value for the Modem Type field.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.4.2 Initial condition
|
For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question.
Specific PICS statements:
-
PIXIT statements:
- Way to receive the call
- Features which must be activated by MMI before an incoming call can be accepted.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.4.3 Test method
|
a) The SS transmits a SETUP message containing a BC-IE among those declared as supported by the MS and corresponding to a non transparent Bearer Service (the Connection Element field is coded "Non transparent"), and with the Modem Type field set to "autobauding type 1".
b) The call is released and step a) is repeated with the same BC in the SETUP message, but with the Connection Element set to "both, non-transparent preferred".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.4.4 Test requirements
|
After steps a) and b), the MS shall send a CALL CONFIRMED message. If present, the BC-IE shall be coded according to 3GPP TS 07.01 and shall correspond to a Bearer Service or Teleservice supported by the MS. If any other parameters than those listed bellow have different values than those of the BC-IE included in the SETUP, then the test shall be failed:
- Number of stop bits, number of data bits, parity;
- Connection Element, Structure, Intermediate rate, User Information Layer 2 Protocol, Modem Type, NIRR;
- Radio Channel Requirement.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.5 Negotiation of Intermediate Rate
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.5.1 Test purpose
|
To verify that the MS responds correctly to a request for a negotiation of the Intermediate Rate parameter in a mobile terminating Setup and negotiates according to its capabilities and to the service requested.
NOTE: The MS may support these services with a 6 Kbit/s or (non exclusive) 12 Kbit/s radio interface rate.
29,2,3.5.2 Initial condition
For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question.
Specific PICS statements:
-
PIXIT statements:
- Way to receive the call
- Features which must be activated by MMI before an incoming call can be accepted.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.5.3 Test method
|
a) The SS transmits a SETUP message containing a BC-IE among those declared as supported by the MS and corresponding to a non transparent Bearer Service (the Connection Element field is coded "Non transparent") with the user rate lower to or equal 4,8 kbit/s, and with the NIRR field set to "No meaning". The RCR field is set to "full rate", and the Intermediate Rate field is set to "16 kbit/s".
b) The call is released and step a) is repeated with the same BC in the SETUP message, but with the Connection Element set to "both, non-transparent preferred".
c) The call is released and steps a) and b) are repeated with the NIRR field of the SETUP message set to "6 kbit/s".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.5.4 Test requirements
|
1) After steps a), b) and c), the MS shall send a CALL CONFIRMED message. If present, the BC-IE shall be coded according to 3GPP TS 07.01 and shall correspond to a Bearer Service or Teleservice supported by the MS. If any other parameters than those listed bellow have different values than those of the BC-IE included in the SETUP, then the test shall be failed:
- Number of stop bits, number of data bits, parity;
- Connection Element, Structure, Intermediate rate, User Information Layer 2 Protocol, Modem Type, NIRR;
- Radio Channel Requirement.
2) If the BC-IE is present in the CALL CONFIRMED message after step c) and if the Connection Element field contains the value "non transparent", the Intermediate Rate field shall indicate:
- 8 kbit/s if the NIRR field is set to "6 kbit/s";
- 16 kbit/s if the NIRR field is set to "no meaning".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.6 Negotiation of User Information Layer 2 Protocol
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.6.1 Test purpose
|
To verify that the MS accepts any value (including the absence of) the UIL2P parameter in a mobile terminating Setup and negotiates according to its capabilities and to the service requested.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.6.2 Initial condition
|
For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question.
Specific PICS statements:
-
PIXIT statements:
- Way to receive the call
- Features which must be activated by MMI before an incoming call can be accepted.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.6.3 Test method
|
a) The SS transmits a SETUP message containing a BC-IE among those declared as supported by the MS and corresponding to a non transparent Bearer Service (the Connection Element field is coded "Non transparent") and with no UIL2P parameter (i.e. octet 7 of the BC IE is absent).
b) The call is released and step a) is repeated with the same BC in the SETUP message, but with the value "ISO6429, codeset 0 (DC1/DC3)" in the UIL2P parameter.
c) The call is released and step b) is repeated with the same BC in the SETUP message, but with the value "COPnoFLCt" in the UIL2P parameter.
d) The call is released and steps a), b) and c) are repeated with the same BC in the SETUP message, but with the Connection Element set to "both, non-transparent preferred".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.6.4 Test requirements
|
1) After steps a), b) and c), the MS shall send a CALL CONFIRMED message. If present, the BC-IE shall be coded according to 3GPP TS 07.01 and shall correspond to a Bearer Service or Teleservice supported by the MS. If any other parameters than those listed bellow have different values than those of the BC-IE included in the SETUP, then the test shall be failed:
- Number of stop bits, number of data bits, parity;
- Connection Element, Structure, Intermediate rate, User Information Layer 2 Protocol, Modem Type, NIRR;
- Radio Channel Requirement.
2) If the BC-IE is present in the CALL CONFIRMED message, and if the Connection Element is set to "transparent", octet 7 (containing the UIL2P parameter) shall be absent.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.7 Negotiation between TS 61 and TS 62: Mobile Originated call
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.7.1 Test purpose
|
To verify that the MS accepts a negotiation from TS 61 to TS 62.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.7.2 Initial condition
|
For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully set up a call for TS 61.
Specific PICS statements:
-
PIXIT statements:
- Way to set up the call
- Features which must be activated by MMI before an outgoing call can be set up.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.7.3 Test method
|
a) The MS is made to set up a call for TS 61. If the MS supports it, the first phase of the call is speech.
b) The SS responds to the SETUP message with a CALL PROCEEDING message containing a BC-IE coded according to 3GPP TS 07.01 and corresponding to TS 62.
c) The SS sends an ALERTING message followed by a CONNECT message.
d) If the MS supports it, steps a), b) and c) are repeated with a call setup for TS 61 with the first phase of the call being fax.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.7.4 Test requirements
|
1) After step b), the MS shall accept the call (i.e. it shall not reject the call with a DISCONNECT message).
2) After step c), the MS shall answer with a CONNECT ACKNOWLEDGE message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.8 Negotiation between TS 61 and TS 62: Mobile Terminated call
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.8.1 Test purpose
|
To verify that an MS that does not support TS 61 accepts a Mobile Terminated call setup request for TS 61 and negotiates the demand to TS 62.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.8.2 Initial condition
|
For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question.
Specific PICS statements:
•
PIXIT statements:
- Way to receive the call
- Features which must be activated by MMI before an incoming call can be accepted.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.8.3 Test method
|
a) The SS transmits a SETUP message containing two BC-IEs: the first BC shall indicate speech, the second BC shall indicate fax group 3.
b) The call is released, and the SS transmits a SETUP message containing two BC-IEs: the first BC shall indicate fax group 3, the second BC shall indicate speech.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.3.8.4 Test requirements
|
After steps a) and b), the MS shall send a CALL CONFIRMED message with one and only one BC-IE. The BC-IE shall be coded according to 3GPP TS 07.01 and shall correspond to TS 62.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.4 Data Rate Adaptation for Synchronous Transparent Bearer Capabilities
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.4.1 Definition
|
-29.2.4.2 Conformance requirement
An MS supporting synchronous transparent bearer capabilities shall perform data rate adaptation and support the frames at the Um-interface according to the following specifications:
1. 3GPP TS 04.21, clauses 5 and 7.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.4.3 Test purpose
|
The purpose of these tests is to verify:
- that the format and the data bits of the 3GPP TS 04.21 frames sent by the MS are consistent with the data input and data rate at the R-interface; and
- that the data bits output by the MS at the R-interface are consistent with the received 3GPP TS 04.21 frames.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.4.4 Method of test
|
The Test shall be carried out for all possible user data rates which are supported by the MS (see below). In case of an MT2 configuration, the interface circuits CT105 and CT108 shall be set to the ON condition from the start.
Procedure:
a) A data call shall be set up between the SS and the MS with a BCIE (see below) supported by the MS. The next step shall be entered immediately after TCH synchronization has been completed at the SS side.
b) The interface circuit bit(s) in the 3GPP TS 04.21 frame shall be set to ON and the SS shall start to transmit pseudo random data bits in the 3GPP TS 04.21 frames over the Um-interface to the MS.
c) MT2 configuration: The SS shall input pseudo random data over the R-interface of the MS.
MT0 configuration: the transmission of data from the MS over the Um-interface shall be stimulated (if it does not start automatically).
d) Approximately 5 s after the data have been received by the SS over the Um-interface the test shall be stopped.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.4.5 Test requirements
|
1) During the test no 3GPP TS 04.21 frame with incorrect format (i.e. format not compliant to 3GPP TS 04.21 (see conformance requirement) or not corresponding to the user data rate currently under test) shall have been received by the SS.
2) Only MT2 configuration: the user data stream input to the R-interface shall match bit-exactly the user data stream sent to the SS over the Um-interface and the user data stream output from the R-interface shall match bit-exactly the user data stream sent by the SS over the Um-interface.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.4.6 BCIE
|
The following combinations shall be considered (ref. 3GPP TS 07.01, annex 2):
a) User Rate = 9,6 kbit/s;
b) User Rate = 4,8 kbit/s;
c) User Rate = 2,4 kbit/s;
d) User Rate = 1,2 kbit/s.
The remaining parameters of the BCIE and the channel type (FR/HR) shall be set to a value supported by the MS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
29.2.5 Network Independent Clocking
|
For further study.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.