hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.11.4.1 Initial Conditions | A 1/2 inch pressure microphone is calibrated using a known sound source and mounted at the MRP, without the LRGP head present. A frequency analyser is calibrated to enable the sound pressure levels at the microphone to be determined in 1/3rd octave bands.
Flood the room in which the measurement is to be made with the selected noise file, and adjust the level such that the noise level at the MRP is 70 dBA. A single noise file of real noise, covering the various noise environments that the MS could be subjected to, is used. This file is three minutes long and also commences with a three minute signal. Once this tone has been adjusted to a level of 70 dBA, the average level of the noise will be 70 dBA. The resulting sound spectrum is Prn dBPa, measured in 1/3rd octave bands.
To ensure that the sound field is diffuse enough, the following apply:
- The diffuse sound field is calibrated in the absence of any local obstacles. The averaged field shall be uniform to within ±3 dB within a radius of 0,15 m of the MRP, when measured in one-third octave bands from 100 Hz to 3,15 Khz.
- Where more than one loudspeaker is used to produce the desired sound field, the loudspeakers may require to be fed with non-coherent signals to eliminate standing waves and other interference effects.
- Position an LRGP in the correct relative position to the MRP and mount the MS under test. Recalibrate the 1/3rd octave frequency analyser using a known voltage source to facilitate the analysis of the Voltage Vrn, where Vrn is the voltage at the audio output of the System Simulator (SS) due to the noise spectrum input. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.11.4.2 Procedure | Set up a full rate speech path between the MS and the SS.
The SS determines, as a function of frequency, using the frequency analyser, in 1/3rd octave bands, the electrical output Vrn, (expressed as dB rel 1V) at the audio output of the SS for the applied acoustic pressure Prn (expressed as dB rel 1Pa) at the MRP. Since, the MS sending sensitivity is not defined above 3,4 kHz and below 300 Hz the measurement shall be cut off at 3,4 kHz and for the bands below 300 Hz. The noise level shall be referenced to the speech level at 300 Hz to yield the DELSM.
The room noise sensitivity is defined as:
- Smj rn = Vrn (dBV) - Prn (dBPa).
The ambient noise send sensitivity has now been determined.
The MS speech send sensitivity is now required. The required sensitivity is defined as the electrical output from the MS, measured at the audio output of the SS, as a function of the free field sound pressure at the MRP of the artificial mouth.
The measurement is made using an artificial speech source at the MRP of the artificial mouth. The 1/2 inch pressure microphone is calibrated using a known sound source. The frequency analyser is calibrated to measure in 1/3rd octave bands. The artificial mouth output shall be in accordance with the ITU-T Recommendation P.50 male artificial voice. Whilst maintaining the ITU-T Recommendation P.50 'male' spectrum, the total signal level is adjusted to -4,7 dBPa. The resulting sound spectrum is P0dBpa, measured in 1/3rd octave bands. The 1/3rd octave frequency analyser shall be re-calibrated, using a known voltage source, to facilitate the analysis of the voltage Vj. Where Vj is the voltage at the audio output of the SS due to the speech spectrum input. A speech path is setup between the MS and the SS. The function of the frequency is determined using the frequency analyser, and in 1/3rd octave bands, the electrical output Vj, (expressed as dB rel. 1V), at the audio output of the SS for the applied acoustic pressure, P0, (expressed as dB rel. 1Pa/V), at the MRP.
The sending sensitivity is expressed as:
The DSM for the MS is determined as:
DSM = Smj rn - Smjs (dB). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.11.5 Test Requirement | The MS ambient noise rejection, calculated as a single figure DELSM (SFDELSM) shall be greater than or equal to 0 dB. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.12 Sending sensitivity/frequency response | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.12.1 Definition | The sending sensitivity frequency response is, as a function of the input test signal frequency, the ratio expressed in dB between the output level at the Digital Audio Interface (DAI) or at the audio output of the reference speech decoder of the SS and the input sound pressure in the artificial mouth required to obtain this. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.12.2 Conformance requirement | The sending sensitivity frequency response shall be within the mask given in 3GPP TS 26.131.
3GPP TS 26.131, subclause 5.4.1, table 1 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.12.3 Test purpose | To verify that the sending sensitivity frequency response is conforming to the specification in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.12.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.12.5 Test requirement | The sending sensitivity frequency response shall be within the mask specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.13 Sending loudness rating | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.13.1 Definition | The Sending Loudness Rating (SLR) is a means of expressing the sending frequency response based on objective measurements in a way which relates to how a speech signal would be perceived by a listener. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.13.2 Conformance requirement | The conformance requirement shall be as specified in 3GPP TS 26.131.
3GPP TS 26.131; subclause 5.2.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.13.3 Test Purpose | To verify that the Sending Loudness Rating (SLR) is conforming to the specification in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.13.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.13.5 Test requirement | The Sending Loudness Rating (SLR) shall be within the limits specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.14 Receiving sensitivity/frequency response | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.14.1 Definition | The receiving sensitivity frequency response is, as a function of the input test signal frequency, the ratio expressed in dB between the output sound pressure in the artificial ear and the input level, represented by the PCM bit stream at the Digital Audio Interface (DAI) or the level at the SS audio input, required to obtain this. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.14.2 Conformance requirement | When measured with the type 1 artificial ear (only release 4 handsets) the receiving sensitivity frequency response shall be within the mask given in 3GPP TS 43.050.
3GPP TS 43.050; subclause 6.8.1.2, table 2.
When measured with 3.x artificial ear (release 4 and later handsets) the receiving sensitivity frequency response shall be within the mask given in 3GPP TS 26.131.
3GPP TS 26.131; subclause 5.4.2, table 2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.14.3 Test purpose | To verify that the receiving sensitivity frequency response is within the mask given in 3GPP TS 43.050; subclause 3.8.1.2, table 2 when measured with the type 1 artificial ear (release 4 handsets only) or within the mask given in 3GPP TS 26.131; subclause 5.4.2, table 2 when measured with a type 3.x artificial ear. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.14.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.14.4.1 Initial conditions | When measured from the DAI:
a) The handset is mounted in the LRGP and the earpiece is sealed to the knife-edge of the artificial ear.
b) A digital signal generator is connected at the digital interface delivering a signal equivalent to a pure tone level of ‑16 dBm0, see ITU-T Recommendation P.64.
c) The DAI of the MS is connected to the SS and is set to the operating mode "Test of acoustic devices and A/D & D/A".
When measured from the input of the reference speech encoder of the SS:
a) The handset is mounted as specified in 3GPP TS 26.132 section 7.4.2.
b) A full rate speech call is set up between the MS and the SS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.14.4.2 Procedure | When measured from the DAI:
- Measurements are made at one twelfth-octave intervals as given in the R.40 series of preferred numbers in ISO 3 for frequencies from 100 Hz to 4 kHz inclusive. At each frequency, the sound pressure in the artificial ear is measured by connecting a suitable measuring set to the artificial ear.
When measured from the input of the reference speech encoder of the SS:
- The test shall be performed according to the test specification as described in 3GPP TS 26.132. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.14.5 Test requirement | When measured in the type 1 artificial ear (allowed for release 4 handsets only) the receiving sensitivity/frequency response shall be within the mask given by table 30.8. The mask can be drawn with straight lines between the breaking points in the following table on a logarithmic (frequency) vs linear (dB sensitivity) scale.
All sensitivity levels are dB on an arbitrary scale.
Table 30.8
Frequency (Hz)
Upper Limit (dB)
Lower Limit (dB)
100
‑12
200
0
300
2
‑7
500
see note
‑5
1 000
0
‑5
3 000
2
‑5
3 400
2
‑10
4 000
2
Note: The limit at intermediate frequencies lies on a straight line drawn between the given values on a log (frequency) vs linear (dB) scale.
When measured in a type 3.x artificial ear, the receiving sensitivity/frequency response shall be within the mask specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.15 Receiving loudness rating | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.15.1 Definition | The Receiving Loudness Rating (RLR) is a means of expressing the receiving frequency response based on objective measurements in a way which relates to how a speech signal would be perceived by a listener. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.15.2 Conformance requirement | 3GPP TS 26.131; subclause 5.2.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.15.3 Test purpose | To verify that the Receiving Loudness Rating (RLR) is conforming to the specification in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.15.4 Method of test | The test method shall be as specified in 3GPP TS 26.132 section 7.2.2.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.15.5 Test requirement | The Receiving Loudness Rating (RLR) shall be within the limits specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.16 Side Tone Masking Rating (STMR) LRGP | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.16.1 Definition | The sidetone loudness ratings are a means of expressing the path loss from the artificial mouth to the artificial ear based on objective single tone measurements in a way that relates to how a speaker will perceive his own voice when speaking (talker sidetone, expressed by the sidetone masking rating - STMR), or how a listener will perceive the background noise picked up by the microphone (listener sidetone rating - LSTR). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.16.2 Conformance requirement | The conformance requirement is specified in 3GPP TS 26.131.
3GPP TS 26.131; subclause 5.5.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.16.3 Test purpose | To verify that the requirement for STMR stated in TS 26.131 is met. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.16.4 Method of test | The test method shall be as specified in 3GPP TS 26.132 section 7.5.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.16.5 Test requirement | The STMR shall be within the limits specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.17 Telephone Acoustic coupling Loss (TAL) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.17.1 Echo Loss (EL) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.17.1.1 Definition | The echo loss is the path loss from the input of the reference speech encoder of the SS to the output of the reference speech decoder of the SS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.17.1.2 Conformance requirement | The echo loss from the input to the output of the reference speech codec in the SS shall be as specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.17.1.3 Test purpose | To verify that the echo loss from the input to the output of the reference speech codec in the SS is as specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.17.1.4 Method of test | The method of test shall be as specified in 3GPP TS 26.132. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.17.1.5 Test requirement | The echo loss from the input to the output of the reference speech codec in the SS shall be as specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.17.2 Stability margin | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.17.2.1 Definition | The receive-transmit stability margin is a measure of the gain that would have to be inserted between the go and return paths of the reference speech coder in the SS for oscillation to occur. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.17.2.2 Conformance requirement | The stability margin shall be as specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.17.2.3 Test purpose | To verify that the stability margin is as specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.17.2.4 Method of test | The method of test shall be as specified in 3GPP TS 26.132. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.17.2.5 Test requirement | The minimum stability margin shall be as specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.18 Sending Distortion | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.18.1 Definition | The transmit signal to total distortion ratio is a measure of the linearity of the transmitter equipment. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.18.2 Conformance requirement | Distortion shall be measured between MRP and the SS audio output (output of the reference speech decoder of the SS). The ratio of signal to total distortion power measured with the proper noise weighting (see table 4 of ITU T Recommendation G.223) shall be above the limits given in table 7.
3GPP TS 03.50; subclause 5.8.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.18.3 Test purpose | To verify that the ratio of signal to total distortion power in the sending direction measured with psophometric noise weighting is as specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.18.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.18.5 Test requirement | The ratio of signal to total distortion power in the sending direction measured with psophometric noise weighting shall be as specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.19 Ambient Noise Rejection | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.19.1 Definition | An MS that supports speech will typically be operated within an area of high ambient acoustic noise. A level of noise rejection will therefore be required. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.19.2 Conformance Requirement | The conformance requirement shall be as specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.19.3 Test Purpose | To verify that ambient noise rejection is conforming to the specification in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.19.4 Method of Test | The test method shall be as specified in 3GPP TS 26.132. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.19.5 Test Requirement | The MS ambient noise rejection shall be as specified in 3GPP TS 26.132. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.20 Side Tone Masking Rating (STMR) HATS | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.20.1 Definition | The sidetone loudness ratings are a means of expressing the path loss from the artificial mouth to the artificial ear based on objective single tone measurements in a way that relates to how a speaker will perceive his own voice when speaking (talker sidetone, expressed by the sidetone masking rating - STMR), or how a listener will perceive the background noise picked up by the microphone (listener sidetone rating - LSTR). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.20.2 Conformance requirement | The conformance requirement is specified in 3GPP TS 26.131. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.20.3 Test purpose | To verify that the requirement for STMR stated in TS 26.131 is met. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.20.4 Method of test | The method of test shall be as specified in 3GPP TS 26.132 section 7.5.1.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 30.20.5 Test requirement | The STMR shall be within the limits specified in 3GPP TS 26.131.
31 Test of supplementary services
The general aspects of the specification of supplementary services at the layer 3 radio interface are given in 3GPP TS 04.10.
The formats and coding are given in 3GPP TS 04.80. If the value of a parameter of an uplink message (MS to network) is specified in a test, the implicit meaning is that it has to be checked; if the value is not specified, it is not to be checked unless otherwise stated.
Unless otherwise stated, the MS shall be in the idle updated state at the beginning of each test (including repetition of a test).
In each test, before the MS sends the first REGISTER message, a MM connection is established.
3GPP TS 04.81 to 3GPP TS 04.88 give the procedures used at the radio interface for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of supplementary services.
The supplementary services are described in 3GPP TS 02.04 and 3GPP TS 02.81 to 3GPP TS 02.88.
Whenever activation via the standard MMI is mentioned, if the MS does not support it but supports a different procedure, this different procedure is used. In the supplementary services tests, only the applicable (see 3GPP TS 02.8x series) MMI service code groups (3GPP TS 02.30 annex 4), of the basic service code in 3GPP TS 09.02,which are supported by the MAP, will be used. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1 Number identification supplementary services | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.1 CLIP | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.1.1 Normal operation | Conformance requirement:
3GPP TS 04.81 subclause 1.1.
Purpose:
To test that the MS presents to the user the calling number presented to it in an incoming SETUP message.
Specific PICS Statements
- Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIXIT Statements
- Description of display for CLIP.
- Support of displaying the calling party subaddress.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The SIM in the MS under test has CLIP enabled.
Foreseen final state of the MS
State U7
Maximum duration of test
30 s.
Procedure:
Set up an MT call to the MS under test. The SETUP message shall include a calling party BCD number information element and a calling party subaddress information element.
Expected sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST
SS sends paging
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
(SDCCH)
4
MS -> SS
PAGING RESPONSE
5
SS -> MS
AUTHENTICATION REQUEST
6
MS -> SS
AUTHENTICATION RESPONSE
7
SS -> MS
CIPHERING MODE COMMAND
8
MS -> SS
CIPHERING MODE COMPLETE
9
SS -> MS
SETUP
Shall include a valid calling party BCD number and calling party subaddress
10
MS -> SS
CALL CONFIRMED
11
MS -> SS
ALERTING
12
MS
Depending on the PICS, the MS shall display the calling party BCD number and calling party subaddress |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.1.2 Interrogation | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.1.2.1 Interrogation accepted | Conformance requirement:
3GPP TS 04.81 subclause 1.2.
Test purpose
To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of successful interrogation.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is "idle updated".
Specific PICS Statements
-
PIXIT Statements
- Description of the user's commands and of display of the answers from the network for interrogation of CLIP.
Foreseen final state of the MS
The MS is "idle updated".
Test procedure
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of CLIP for all basic service groups.
Upon receipt of the operation (in a REGISTER message), the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the return result of the InterrogateSS operation.
The SS transaction is released and the dedicated channel is released.
Maximum duration of test
3 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate an interrogation of CLIP (all)
2
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
REGISTER
7
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Return_result
8
SS -> MS
CHANNEL RELEASE
Specific message content
step 6 - CLIP
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation
Supplementary service code = CLIP.
Basic service code: no Bearer Service present, no teleservice present. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.1.2.2 Interrogation rejected | Conformance requirement
3GPP TS 04.81 subclause 1.2.
Test purpose
To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of an error response and an invoke problem.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC state U10.
Specific PICS Statements
-
PIXIT Statements
- Description of the user's commands and of display of the answers from the network for interrogation of CLIP.
Foreseen final state of the MS
The MS is in CC state U10.
Test procedure
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of CLIP for all basic service groups.
Upon receipt of the operation (in a REGISTER message),the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing a Return_error(error: SS not available) of the InterrogateSS operation.
The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.
Then again, by means of appropriate MMI functions as defined by the basic public MMI described in 3GPP TS 02.30, the user requests interrogation of CLIP for all basic service groups.
Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message (same PD and TI that in the REGISTER message) with the Facility information element containing a reject(invoke_problem: resource limitation) of the InterrogateSS operation.
The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.
Maximum duration of test
3 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate an interrogation for CLIP (all)
2
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
3
SS -> MS
CM SERVICE ACCEPT
4
MS -> SS
REGISTER
5
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Return_error
6
SS -> MS
STATUS ENQUIRY
7
MS -> SS
STATUS
CC state U10
8
MS
The MS is made to initiate an interrogation of CLIP (all)
9
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
10
SS -> MS
CM SERVICE ACCEPT
11
MS -> SS
REGISTER
12
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Reject
13
MS
provide correct MMI user indication
14
SS -> MS
STATUS ENQUIRY
15
MS -> SS
STATUS
CC state U10
Specific message content
step 4, 11 - CLIP
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation
Supplementary service code = CLIP.
Basic service code:no Bearer Service present, no teleservice present.
step 5 - CLIP
- protocol discriminator: non call related SS message.
- transaction identifier: same TI as previous REGISTER message.
- message type: RELEASE COMPLETE.
- facility:
return error code: SS not available.
For the return error the invoke ID must be the same as in the invoke of the InterrogateSS operation.
step 12 -
- protocol discriminator: non call related SS message.
- transaction identifier: same TI as previous REGISTER message.
- message type: RELEASE COMPLETE.
- facility:
reject code: resource limitation.
For the reject the invoke ID must be the same as in the invoke of the InterrogateSS operation. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.2 CLIR | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.2.1 Normal operation - requesting presentation of CLI | Conformance requirement:
3GPP TS 04.81 subclause 2.2.
Test Purpose
To test that when the CLIR presentation mode is temporary (presentation restricted), it is possible for the subscriber to present his CLI on a per call basis.
Method of test
Specific PICS Statements
- Supported MO circuit switched basic services (TSPC_AddInfo_MOsvc)
PIXIT Statements
-
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The SIM in the MS under test has CLIR enabled with CLIR presentation mode "temporary (presentation restricted)".
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U0.1 by using table 26.8.1.2/1.
Foreseen final state of the MS
U1, call initiated.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Using MMI commands, the MS is made to initiate an outgoing call with CLI presented. When the MS is requesting a MM-connection, the SS will indicate acceptance by sending a CM SERVICE ACCEPT message. The MS shall respond with SETUP. The SETUP message shall contain the CLIR suppression information element.
Expected sequence
Step
Direction
Message
Comments
1
SS -> MS
CM SERVICE ACCEPT
2
MS -> SS
SETUP
with CLIR suppression information element |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.2.2 Normal operation - requesting restriction of CLI presentation | Conformance requirement:
3GPP TS 04.81 subclause 2.3.
Test Purpose
To test that when the CLIR presentation mode is temporary (presentation allowed), it is possible for the subscriber to present his CLI on a per call basis.
Procedure
Using MMI commands, the MS is made to initiate an outgoing call with CLI restricted.
Requirements:
The SETUP message sent by the MS shall include the CLIR invocation information element.
Method of test
Specific PICS Statements
- Supported MO circuit switched basic services (TSPC_AddInfo_MOsvc)
PIXIT Statements
-
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The SIM in the MS under test has CLIR enabled with CLIR presentation mode "temporary (presentation allowed)".
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U0.1 by using table 26.8.1.2/1.
Foreseen final state of the MS
U1, call initiated.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Using MMI commands, the MS is made to initiate an outgoing call with CLI restricted. When the MS is requesting a MM-connection, the SS will indicate acceptance by sending a CM SERVICE ACCEPT message. The MS shall respond with SETUP. The SETUP message sent by the MS shall include the CLIR invocation information element.
Expected sequence
Step
Direction
Message
Comments
1
SS -> MS
CM SERVICE ACCEPT
2
MS -> SS
SETUP
with CLIR invocation information element |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.2.3 Interrogation | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.2.3.1 Interrogation accepted | Conformance requirement:
3GPP TS 04.81 subclause 2.4.
Applicability
MS supporting the CLIR supplementary service.
Test purpose
To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of successful interrogation.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is "idle updated".
Specific PICS Statements
-
PIXIT Statements
- Description of the user's commands and of display of the answers from the network for interrogation of CLIR.
Foreseen final state of the MS
The MS is "idle updated".
Test procedure
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of CLIR for all basic service groups.
Upon receipt of the operation (in a REGISTER message), the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the return result of the InterrogateSS operation.
The SS transaction is released and the dedicated channel is released.
Maximum duration of test
3 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate an interrogation of CLIR (all)
2
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
REGISTER
7
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Return_result
8
SS -> MS
CHANNEL RELEASE
Specific message content
step 6 - CLIR
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation:
Supplementary service code = CLIR.
Basic service code: no Bearer Service present, no teleservice present. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.2.3.2 Interrogation rejected | Conformance requirement
3GPP TS 04.81 subclause 2.4.
Test purpose
To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of an error response and an invoke problem.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC state U10.
Specific PICS Statements
-
PIXIT Statements
- Description of the user's commands and of display of the answers from the network for interrogation of CLIR.
Foreseen final state of the MS
The MS is in CC state U10.
Test procedure
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of CLIR for all basic service groups.
Upon receipt of the operation (in a REGISTER message),the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing a Return_error(error: SS not available) of the InterrogateSS operation.
The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.
Then again, by means of appropriate MMI functions as defined by the basic public MMI described in 3GPP TS 02.30, the user requests interrogation of CLIR for all basic service groups.
Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message (same PD and TI that in the REGISTER message) with the Facility information element containing a reject(invoke_problem: resource limitation) of the InterrogateSS operation.
The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.
Maximum duration of test
3 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate an interrogation for CLIR (all)
2
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
3
SS -> MS
CM SERVICE ACCEPT
4
MS -> SS
REGISTER
5
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Return_error
6
SS -> MS
STATUS ENQUIRY
7
MS -> SS
STATUS
CC state U10
8
MS
The MS is made to initiate an interrogation of CLIR (all)
9
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
10
SS -> MS
CM SERVICE ACCEPT
11
MS -> SS
REGISTER
12
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Reject
13
MS
provide correct MMI user indication
14
SS -> MS
STATUS ENQUIRY
15
MS -> SS
STATUS
CC state U10
Specific message content
step 4, 11 - CLIR
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation:
Supplementary service code = CLIR.
Basic service code:no Bearer Service present, no teleservice present.
step 5 - CLIR
- protocol discriminator: non call related SS message.
- transaction identifier: same TI as previous REGISTER message.
- message type: RELEASE COMPLETE.
- facility:
return error code: SS not available.
For the return error the invoke ID must be the same as in the invoke of the InterrogateSS operation.
step 12 -
- protocol discriminator: non call related SS message.
- transaction identifier: same TI as previous REGISTER message.
- message type: RELEASE COMPLETE.
- facility:
reject code: resource limitation.
For the reject the invoke ID must be the same as in the invoke of the InterrogateSS operation. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.3 COLP | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.3.1 Normal operation | Conformance requirement:
3GPP TS 04.81 subclause 3.1.
Purpose:
To test that the MS displays the connected number presented to it in an incoming CONNECT message.
Method of test
Specific PICS Statements
- Supported MO circuit switched basic services (TSPC_AddInfo_MOsvc)
PIXIT Statements
- Description of display for COLP.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The SIM in the MS under test has COLP enabled.
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U1 by using table 26.8.1.2/4.
Foreseen final state of the MS
U10, call active.
Maximum duration of test
30 s.
Test procedure
1. An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U4. The SS sends a CONNECT message to the MS containing a connected number information element and a connected party subaddress information element. The MS shall respond by sending a CONNECT ACKNOWLEDGE message. The MS shall correctly display the connected line information.
Expected sequence, procedure 1
Step
Direction
Message
Comments
1
SS -> MS
CONNECT
See specific message contents
2
MS -> SS
CONNECT ACKNOWLEDGE
3
MS
The MS shall correctly display the connected line information
Specific message contents
CONNECT
Connected number information element
Presentation indicator
Presentation allowed
Screening indicator
User provided, not screened
Connected subaddress
Any valid subaddress |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.3.2 Interrogation | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.3.2.1 Interrogation accepted | Conformance requirement:
3GPP TS 04.81 subclause 3.2.
Test purpose
To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of successful interrogation.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is "idle updated".
Specific PICS Statements
-
PIXIT Statements
- Description of the user's commands and of display of the answers from the network for interrogation of COLP.
Foreseen final state of the MS
The MS is "idle updated".
Test procedure
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of COLP for all basic service groups.
Upon receipt of the operation (in a REGISTER message), the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the return result of the InterrogateSS operation.
The SS transaction is released and the dedicated channel is released.
Maximum duration of test
3 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate an interrogation of COLP (all)
2
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
REGISTER
7
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Return_result
8
SS -> MS
CHANNEL RELEASE
Specific message content
step 6 - COLP
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation:
Supplementary service code = COLP.
Basic service code: no Bearer Service present, no teleservice present. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.3.2.2 Interrogation rejected | Conformance requirement
3GPP TS 04.81 subclause 3.2.
Test purpose
To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of an error response and an invoke problem.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC state U10.
Specific PICS Statements
-
PIXIT Statements
- Description of the user's commands and of display of the answers from the network for interrogation of COLP.
Foreseen final state of the MS
The MS is in CC state U10.
Test procedure
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of COLP for all basic service groups.
Upon receipt of the operation (in a REGISTER message),the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing a Return_error(error: SS not available) of the InterrogateSS operation.
The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.
Then again, by means of appropriate MMI functions as defined by the basic public MMI described in 3GPP TS 02.30, the user requests interrogation of COLP for all basic service groups.
Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message (same PD and TI that in the REGISTER message) with the Facility information element containing a reject(invoke_problem: resource limitation) of the InterrogateSS operation.
The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.
Maximum duration of test
3 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate an interrogation for COLP (all)
2
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
3
SS -> MS
CM SERVICE ACCEPT
4
MS -> SS
REGISTER
5
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Return_error
6
SS -> MS
STATUS ENQUIRY
7
MS -> SS
STATUS
CC state U10
8
MS
The MS is made to initiate an interrogation of COLP (all)
9
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
10
SS -> MS
CM SERVICE ACCEPT
11
MS -> SS
REGISTER
12
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Reject
13
MS
provide correct MMI user indication
14
SS -> MS
STATUS ENQUIRY
15
MS -> SS
STATUS
CC state U10
Specific message content
step 4, 11 - COLP
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation:
Supplementary service code = COLP.
Basic service code:no Bearer Service present, no teleservice present.
step 5 - COLP
- protocol discriminator: non call related SS message.
- transaction identifier: same TI as previous REGISTER message.
- message type: RELEASE COMPLETE.
- facility:
return error code: SS not available.
For the return error the invoke ID must be the same as in the invoke of the InterrogateSS operation.
step 12 -
- protocol discriminator: non call related SS message.
- transaction identifier: same TI as previous REGISTER message.
- message type: RELEASE COMPLETE.
- facility:
reject code: resource limitation.
For the reject the invoke ID must be the same as in the invoke of the InterrogateSS operation. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.4 COLR | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.4.1 Interrogation | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.4.1.1 Interrogation accepted | Conformance requirement:
3GPP TS 04.81 subclause 4.2.
Test purpose
To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of successful interrogation.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is "idle updated".
Specific PICS Statements
-
PIXIT Statements
- Description of the user's commands and of display of the answers from the network for interrogation of COLR.
Foreseen final state of the MS
The MS is "idle updated".
Test procedure
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of COLR for all basic service groups.
Upon receipt of the operation (in a REGISTER message), the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the return result of the InterrogateSS operation.
The SS transaction is released and the dedicated channel is released.
Maximum duration of test
3 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate an interrogation of COLR (all)
2
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
REGISTER
7
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Return_result
8
SS -> MS
CHANNEL RELEASE
Specific message content
step 6 - COLR
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation:
Supplementary service code = COLR.
Basic service code: no Bearer Service present, no teleservice present. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.4.1.2 Interrogation rejected | Conformance requirement
3GPP TS 04.81 subclause 4.2.
Test purpose
To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of an error response and an invoke problem.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC state U10.
Specific PICS Statements
-
PIXIT Statements
- Description of the user's commands and of display of the answers from the network for interrogation of COLR.
Foreseen final state of the MS
The MS is in CC state U10.
Test procedure
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of COLR for all basic service groups.
Upon receipt of the operation (in a REGISTER message),the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing a Return_error(error: SS not available) of the InterrogateSS operation.
The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.
Then again, by means of appropriate MMI functions as defined by the basic public MMI described in 3GPP TS 02.30, the user requests interrogation of COLR for all basic service groups.
Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message (same PD and TI that in the REGISTER message) with the Facility information element containing a reject(invoke_problem: resource limitation) of the InterrogateSS operation.
The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.
Maximum duration of test
3 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate an interrogation for COLR (all)
2
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
3
SS -> MS
CM SERVICE ACCEPT
4
MS -> SS
REGISTER
5
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Return_error
6
SS -> MS
STATUS ENQUIRY
7
MS -> SS
STATUS
CC state U10
8
MS
The MS is made to initiate a interrogation of COLR (all)
9
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
10
SS -> MS
CM SERVICE ACCEPT
11
MS -> SS
REGISTER
12
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Reject
13
MS
provide correct MMI user indication
14
SS -> MS
STATUS ENQUIRY
15
MS -> SS
STATUS
CC state U10
Specific message content
step 4, 11 - COLR
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation:
Supplementary service code = COLR.
Basic service code:no Bearer Service present, no teleservice present.
step 5 - COLR
- protocol discriminator: non call related SS message.
- transaction identifier: same TI as previous REGISTER message.
- message type: RELEASE COMPLETE.
- facility:
return error code: SS not available.
For the return error the invoke ID must be the same as in the invoke of the InterrogateSS operation.
step 12 -
- protocol discriminator: non call related SS message.
- transaction identifier: same TI as previous REGISTER message.
- message type: RELEASE COMPLETE.
- facility:
reject code: resource limitation.
For the reject the invoke ID must be the same as in the invoke of the InterrogateSS operation. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.4.2 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.5 CNAP | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.5.1.1 Normal Operation – Name indication contained in Setup message | Conformance requirements
3GPP TS 24.096 subclause 4.1
Purpose
To test that the MS presents to the user the name information of the calling party to the called party at call setup time for all incoming calls.
Specific PICS Statements
- Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIXIT Statements
- Description of display for CNAP.
Initial Conditions
System Simulator:
1 cell, default parameters
Mobile Station:
The MS is in MM-state “idle, updated” with valid TMSI and CKSN
Foreseen final state of the MS
Stae U7
Maximum Duration of Test
3 minutes.
Procedure
Set up an MT Call to the MS under test. The SS sends the Name Indication in the Facilty IE of the CC Setup
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST
SS sends paging
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
(SDCCH)
4
MS -> SS
PAGING RESPONSE
5
SS -> MS
AUTHENTICATION REQUEST
6
MS -> SS
AUTHENTICATION RESPONSE
7
SS -> MS
CIPHERING MODE COMMAND
8
MS -> SS
CIPHERING MODE COMPLETE
9
SS -> MS
SETUP
Shall include Facility (Invoke = NotifySS (CNAP, nameIndicator ))
Signal IE included
10
MS -> SS
CALL CONFIRMED
11
MS -> SS
ALERTING
12
MS
Depending on the PICS, the MS shall display the calling nameIndicator
Specific message content
step 9 – CNAP nameIndicator settings:
- namePresentationAllowed
- NameSet: “TESTNAME” |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.5.1.2 Normal Operation – Name indication contained in Facility message | Conformance requirements
3GPP TS 24.096 subclause 4.1
Purpose
To test that the MS presents to the user the name information of the calling party to the called party at call setup time for all incoming calls.
Specific PICS Statements
- Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIXIT Statements
- Description of display for CNAP.
Initial Conditions
System Simulator:
1 cell, default parameters
Mobile Station:
The MS is in MM-state “idle, updated” with valid TMSI and CKSN
Foreseen final state of the MS
Stae U7
Maximum Duration of Test
3 minutes.
Procedure
Set up an MT Call to the MS under test. The SS sends the Name Indication in a Facilty message
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST
SS sends paging
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
(SDCCH)
4
MS -> SS
PAGING RESPONSE
5
SS -> MS
AUTHENTICATION REQUEST
6
MS -> SS
AUTHENTICATION RESPONSE
7
SS -> MS
CIPHERING MODE COMMAND
8
MS -> SS
CIPHERING MODE COMPLETE
9
SS -> MS
SETUP
Signal IE included
10
MS -> SS
CALL CONFIRMED
11
MS -> SS
ALERTING
12
SS -> MS
FACILITY
Facility (Invoke=NotifiSS (CNAP, nameIndicator))
13
MS
Depending on the PICS, the MS shall display the calling nameIndicator
Specific message content
step 10 – CNAP nameIndicator settings:
- namePresentationAllowed
- NameSet: “TESTNAME” |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.5.2.1 Interrogation accepted | Conformance requirements
3GPP TS 24.096 subclause 4.2
Purpose
To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of successful interrogation
Initial Conditions
System Simulator:
1 cell, default parameters
Mobile Station:
The MS is “Idle Updated”
Specific PICS Statements
-
PIXIT Statements
- Description of the user's commands and of display of the answers from the network for interrogation of CNAP.
Forseen final state of the MS
The MS is Idle Updated
Maximum Duration of Test
3 minutes.
Procedure
By mean´s of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the users requests interrogation of CNAP for all basic service groups.
Upon receipt of the operation (in a register message), the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the return result of the InterrogtaeSS operation .
The SS transaction is released and the dedicated channel is released
Expected Sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate an interrogation of CNAP (all)
2
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
REGISTER
Facility (Invoke = InterrogateSS (CNAP))
7
SS -> MS
RELEASE COMPLETE
Facility (Return Result = InterrogateSS (ss-status))
8
SS -> MS
CHANNEL RELEASE
Specific message content
step 6 - CNAP
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation
Supplementary service code = CNAP.
Basic service code: no Bearer Service present, no teleservice present. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.1.5.2.2 Interrogation rejected | Conformance requirements
3GPP TS 24.096 subclause 4.2
Purpose
To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of an error response and an invoke problem.
Specific PICS Statements
-
PIXIT Statements
- Description of the user's commands and of display of the answers from the network for interrogation of CNAP.
Initial Conditions
System Simulator:
1 cell, default parameters
Mobile Station:
The MS is in CC state U10
Maximum Duration of Test
3 minutes.
Procedure
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of CNAP for all basic service groups.
Upon receipt of the operation (in a REGISTER message),the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing a Return_error (error: SS not available) of the InterrogateSS operation.
The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.
Then again, by means of appropriate MMI functions as defined by the basic public MMI described in 3GPP TS 02.30, the user requests interrogation of CNAP for all basic service groups.
Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message (same PD and TI that in the REGISTER message) with the Facility information element containing a reject (invoke_problem: resource limitation) of the InterrogateSS operation.
The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.
Expected Sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate an interrogation for CNAP (all)
2
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
3
SS -> MS
CM SERVICE ACCEPT
4
MS -> SS
REGISTER
5
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Return_error
6
SS -> MS
STATUS ENQUIRY
7
MS -> SS
STATUS
CC state U10
8
MS
The MS is made to initiate an interrogation of CNAP (all)
9
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
10
SS -> MS
CM SERVICE ACCEPT
11
MS -> SS
REGISTER
12
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Reject
13
MS
provide correct MMI user indication
14
SS -> MS
STATUS ENQUIRY
15
MS -> SS
STATUS
CC state U10
Specific message content
step 4, 11 - CNAP
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation
Supplementary service code = CNAP.
Basic service code:no Bearer Service present, no teleservice present.
step 5 - CNAP
- protocol discriminator: non call related SS message.
- transaction identifier: same TI as previous REGISTER message.
- message type: RELEASE COMPLETE.
- facility:
return error code: SS not available.
For the return error the invoke ID must be the same as in the invoke of the InterrogateSS operation.
step 12 -
- protocol discriminator: non call related SS message.
- transaction identifier: same TI as previous REGISTER message.
- message type: RELEASE COMPLETE.
- facility:
reject code: resource limitation.
For the reject the invoke ID must be the same as in the invoke of the InterrogateSS operation. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2 Call offering supplementary services | The following abbreviations are used:
CF: Call Forwarding (common name for CFU, CFB, CFNRy and CFNRc).
CFB: Call Forwarding on mobile subscriber Busy
CFC: Call Forwarding Conditional (common name for CFB, CFNRy and CFNRc)
CFNRc: Call Forwarding on mobile subscriber Not Reachable
CFNRy: Call Forwarding on No Reply
CFU: Call Forwarding Unconditional
NOTE: These abbreviations are also used to represent the corresponding SS-Code; e.g. CFC is the SS-Code for all conditional forwarding services. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1 Call forwarding supplementary services | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.1 Registration | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.1.1 Registration accepted | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.1.1.1 Conformance requirements | For registration of any type of call forwarding with any parameters, the MS shall transmit successively:
1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user";
2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation";
3) and then the REGISTER message containing a facility IE that includes an invoke of the RegisterSS operation with parameter values according to the user's request (MMI action);
4) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the manufacturer).
References
1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9.
2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3.
3) 3GPP TS 04.82, 3GPP TS 04.80 subclauses 2.3 and 3.6.
4) 3GPP TS 02.30 subclause 4.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.1.1.2 Test purpose | 1) To check that the MS correctly requests a supplementary service transaction for registration of call forwarding in CHANNEL REQUEST message.
2) To check that the MS correctly requests a supplementary service transaction for registration of call forwarding in the subsequent CM SERVICE REQUEST.
3) To check that the MS sends a REGISTER message containing the invoke of the RegisterSS operation with the expected parameter values for registration of call forwarding.
4) To check that upon receipt of the result of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer).
These checks are done for:
a) CFNRy, for basic service group speech.
b) CFU, for basic service group all facsimile. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.1.1.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is "idle updated".
Specific PICS Statements
-
PIXIT Statements
- Description of the user's commands and of display of the answers from the network for call forwarding.
Foreseen final state of the MS
The MS is "idle updated".
Test procedure
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests registration of CFNRy for Speech, to a number arbitrarily selected and with a no reply time value arbitrarily selected.
Upon receipt of the operation (in a REGISTER message), the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the return result of the RegisterSS operation.
The SS transaction is released and the dedicated channel is released.
Then again, by means of appropriate MMI functions as defined by the basic public MMI described in 3GPP TS 02.30, the user requests registration of CFU for all facsimile, to a number arbitrarily selected.
Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing the return result of the RegisterSS operation.
Maximum duration of test
3 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate a registration of call forwarding service for CFNRy (Speech)
2
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
REGISTER
7
SS -> MS
RELEASE COMPLETE
CNFRySS operation Return_result
8
SS -> MS
CHANNEL RELEASE
9
MS
Provide correct MMI user indication after step 7
10
MS
The MS is made to initiate a registration of call forwarding service for CFU (all facsimile)
11
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
12
SS -> MS
IMMEDIATE ASSIGNMENT
13
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
14
SS -> MS
CM SERVICE ACCEPT
15
MS -> SS
REGISTER
16
SS -> MS
RELEASE COMPLETE
RegisterSS operation Return result
17
SS -> MS
CHANNEL RELEASE
18
MS
Provide correct MMI user indication after step 16
Specific message content
step 6 - CFNRy
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Registration:
Supplementary service code = CFNRy.
Forwarded to number: as selected.
No reply condition time: as selected.
Basic service code: TeleService AllSpeechTransmissionServices (TS10) or Telephony (TS 11), no Bearerservice present.
step 7 - CFU
- protocol discriminator: non call related SS message.
- transaction identifier: same as at step 6.
- message type: RELEASE COMPLETE.
- facility:
Return Result = Registration:
Supplementary service code = CFNRy.
Forwarded to number.
No Reply condition time.
Basic service code: TeleService AllSpeechTransmissionServices (TS10) or Telephony (TS 11), no Bearerservice present.
step 15 - CFU
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Registration:
Supplementary service code = CFU.
Forwarded to number: as selected.
Basic service code: no bearer service present, teleservice (all facsimile).
step 16 - CFU
- protocol discriminator: non call related SS message.
- transaction identifier: same as at step 15.
- message type: RELEASE COMPLETE.
- facility:
Return Result = Registration:
Supplementary service code = CFU.
Forwarded to number.
Basic service code: TeleService (all facsimile), no Bearerservice present. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.