Datasets:

OrganizedProgrammers
/

3GPPSpecContent

Dataset card Data Studio Files Files and versions Community

Split (1)

train · 466k rows

hash stringlengths 32 32	doc_id stringlengths 5 12	section stringlengths 4 595	content stringlengths 0 6.67M
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3.1.2 Test purpose	1) To check that the MS correctly requests a supplementary service transaction for activation of a specific call restriction service in CHANNEL REQUEST message. 2) To check that the MS correctly requests a supplementary service transaction for activation of call restriction service in the subsequent CM SERVICE REQUEST. 3) To check that the MS sends a REGISTER message containing the invoke of the ActivateSS operation with the expected parameter values for activation of a specific call restriction service. 4) To check that upon receipt of FACILITY message requiring the password, the MS is able to send a password by sending a FACILITY. 5) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (which is to be described by the manufacturer). These checks are done for: a) BAOC, for basic service group "all synchronous services". b) BICRoam, for all basic service groups.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3.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 barring. 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 activation of BAOC, for basic service group "all synchronous services". Upon receipt of the operation (in a REGISTER message), the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the current password. If the manufacturer defined MMI has been used to request the activation of BAOC, then the MS may, by means of appropriate manufacturer defined MMI functions, prompt the user to give a password, depending on the implementation of the manufacturer defined MMI functions. Upon receipt of the FACILITY message, the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the Return_result of the ActivateSS operation. The SS transaction and the dedicated channel are released. Then again, by means of appropriate MMI functions, the user requests activation of BICRoam, for all basic service groups. Upon receipt of the operation (in a REGISTER message), the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the current password. If the manufacturer defined MMI has been used to request the activation of BICRoam, then the MS may, by means of appropriate manufacturer defined MMI functions, prompt the user to give a password, depending on the implementation of the manufacturer defined MMI functions. Upon receipt of the FACILITY message, the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the Return_result of the ActivateSS operation. 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 a activation of BAOC(all synchronous services) 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 FACILITY GetPassword 8 MS -> SS FACILITY Getpassword operation Return Result 9 SS -> MS RELEASE COMPLETE ActivateSS operation Return_result 10 SS -> MS CHANNEL RELEASE 11 MS Provide correct MMI user indication after step 9 12 MS The MS is made to initiate an activation of BICRoam(all basic service groups), 13 MS -> SS CHANNEL REQUEST with establishment cause "Other procedures which can be completed with an SDCCH" 14 SS -> MS IMMEDIATE ASSIGNMENT 15 MS -> SS CM SERVICE REQUEST cause: "supplementary service activation" 16 SS -> MS CM SERVICE ACCEPT 17 MS -> SS REGISTER 18 SS -> MS FACILITY GetPassword 19 MS -> SS FACILITY Getpassword operation Return Result 20 SS -> MS RELEASE COMPLETE ActivateSS operation Return result 21 SS -> MS CHANNEL RELEASE 22 MS Provide correct MMI user indication after step 20 Specific message contents step 6 - BAOC - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = Activation: Supplementary service code = BAOC. Basic service code: Bearer Service (all synchronous services), no teleservice present. step 17 - BICRoam - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = Activation: Supplementary service code = BICRoam. Basic service code: no bearer service present, no teleservice present. steps 7, 18 - - protocol discriminator: non call related SS message. - transaction identifier: in FACILITY same as previous REGISTER message. - message type: FACILITY. - facility: invoke = GetPassword: Guidance info: Password.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3.2 Activation rejected
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3.2.1 Rejection after invoke of ActivateSS operation
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3.2.1.1 Conformance requirements	1) A transaction of any kind being already established, for activation of one specific barring services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation". 2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the ActivateSS operation with parameter values according to the user's request (MMI action). 3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected. 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.88, 3GPP TS 04.80 subclauses 2.3 and 3.6. 4) 3GPP TS 02.30 subclause 4.5.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3.2.1.2 Test purpose	1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of specific call barring service, sending a CM SERVICE REQUEST. 2) To check that the MS sends a REGISTER message containing the invoke of the ActivateSS operation with the expected parameter values for specific call barring service. 3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected. 4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer). Those checks are performed with a call transaction already established for: - BOIC, the RELEASE COMPLETE message being sent at the beginning of the procedure with a facility IE containing a return_error(error) where error is "SS subscription violation".
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3.2.1.3 Method of test	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 call barring. 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 activation of BOIC. Upon receipt of the operation (in a REGISTER message), the system simulator answers with the RELEASE COMPLETE (PD and TI of the SS transaction) message with the Facility information element containing a Return_error(error: SS subscription violation) of the ActivateSS operation. The system simulator then sends STATUS ENQUIRY, and the MS responds with STATUS message indicating CC state U10. Maximum duration of test 2 minutes. Expected sequence Step Direction Message Comments 1 MS The MS is made to initiate an activation of BOIC 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 RegisterPassword operation Return_error 6 MS provide correct MMI user indication 7 SS -> MS STATUS ENQUIRY 8 MS -> SS STATUS CC state U10 Specific message content step 4 - - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = ActivateSS: Supplementary service code = BOIC. step 5 - - protocol discriminator: non call related SS message. - transaction identifier: same TI as previous REGISTER message. - message type: RELEASE COMPLETE. - facility: return error code: SS subscription violation. For the return error the invoke ID must be the same as in the invoke of the ActivateSS operation.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3.2.2 Rejection after use of password procedure
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3.2.2.1 Conformance requirements	1) A transaction of any kind being already established, for activation of any specific call restriction services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation". 2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the ActivateSS operation with parameter values according to the user's request (MMI action). 3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected. 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.88, 3GPP TS 04.80 subclauses 2.3 and 3.6. 4) 3GPP TS 02.30 subclause 4.5.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3.2.2.2 Test purpose	1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of activation of one specific call restriction service, sending a CM SERVICE REQUEST. 2) To check that the MS sends a REGISTER message containing the invoke of the ActivateSS operation with the expected parameter values for activation of one specific call restriction service. 3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected. 4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer). Those checks are performed with a call transaction already established for: - BAIC, the RELEASE COMPLETE message being sent at the end of the procedure with a facility IE containing a return_error(error) where error is "NegativePasswordCheck".
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3.2.2.3 Method of test	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 call barring. 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 activation of BAIC. Upon receipt of the REGISTER message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the current password. If the manufacturer defined MMI has been used to request the activation of BAIC, then the MS may, by means of appropriate manufacturer defined MMI functions, prompt the user to give a password, depending on the implementation of the manufacturer defined MMI functions. Upon receipt of the FACILITY message, the system simulator sends RELEASE COMPLETE message (PD and TI of the SS transaction) with the Facility information element containing a Return_error(error: NegativePasswordCheck) of the GetPassword 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 a registration of BAIC 2 MS -> SS CM SERVICE REQUEST cause: "supplementary service activation" 3 SS -> MS CM SERVICE ACCEPT 4 MS -> SS REGISTER 5 SS -> MS FACILITY Invoke = GetPassword (password) 6 MS -> SS FACILITY GetPassword operation Return Result 7 SS -> MS RELEASE COMPLETE Register Password operation ReturnError 8 MS provide correct MMI user indication 9 SS -> MS STATUS ENQUIRY 10 MS -> SS STATUS CC state U10 Specific message content step 4 - BAIC - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = Activation: Supplementary service code = BAIC. step 5 - All Barring services - protocol discriminator: non call related SS message. - transaction identifier: in FACILITY same as previous REGISTER message. - message type: FACILITY. - facility: invoke = GetPassword: Guidance info: Password (step 5). step 8 - - protocol discriminator: non call related SS message. - transaction identifier: same TI as previous REGISTER message. - message type: RELEASE COMPLETE. - facility: reject code: NegativePasswordCheck. For the reject the invoke ID must be the same as in the invoke of the GetPassword operation.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4 Deactivation
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4.1 Deactivation accepted
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4.1.1 Conformance requirements	1) For deactivation of any group of call restriction services with any parameters, the MS shall transmit successively 1.1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user"; 1.2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation"; 1.3) and then the REGISTER message containing a facility IE that includes an invoke of the DeactivateSS operation with parameter values according to the user's request (MMI action). 2) Upon receipt of FACILITY message requiring the password, the MS shall be able to send a password by sending a FACILITY message. 3) 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.2.9. 2) 3GPP TS 04.88, 3GPP TS 04.80 subclauses 2.3 and 3.6. 3) 3GPP TS 02.30 subclause 4.5.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4.1.2 Test purpose	1) To check that the MS correctly requests a supplementary service transaction for deactivation of a group of call barring services in CHANNEL REQUEST message. 2) To check that the MS correctly requests a supplementary service transaction for deactivation of a group of call barring services in the subsequent CM SERVICE REQUEST. 3) To check that the MS sends a REGISTER message containing the invoke of the DeactivateSS operation with the expected parameter values for deactivation of a group of call restriction services. 4) To check that upon receipt of FACILITY message requiring the password, the MS is able to send a password by sending a FACILITY message. 5) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (which is to be described by the manufacturer). These checks are done for: a) all restrictions, for basic service group "speech". b) barring of outgoing calls, for all facsimile.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4.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 barring. 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 deactivation of all restrictions, for speech. Upon receipt of the operation (in a REGISTER message), the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the current password. If the manufacturer defined MMI has been used to request the deactivation of all restrictions for speech, then the MS may, by means of appropriate manufacturer defined MMI functions, prompt the user to give a password, depending on the implementation of the manufacturer defined MMI functions. Upon receipt of the FACILITY message, the system simulator answers with the FACILITY message with the Facility information element containing the Return_result of the DeactivateSS operation. The SS transaction and the dedicated channel are released. Then again, by means of appropriate MMI functions, the user requests deactivation of barring of outgoing calls, for all facsimile. Upon receipt of the operation (in a REGISTER message), the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the current password. If the manufacturer defined MMI has been used to request the deactivation of barring of outgoing calls for all facsimile, then the MS may, by means of appropriate manufacturer defined MMI functions, prompt the user to give a password, depending on the implementation of the manufacturer defined MMI functions. Upon receipt of the FACILITY message, the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the Return_result of the DeactivateSS operation. The dedicated channel is released. Maximum duration of test 5 minutes. Expected sequence Step Direction Message Comments 1 MS The MS is made to initiate a deactivation of all call restrictions(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 FACILITY GetPassword 8 MS -> SS FACILITY Getpassword operation Return Result 9 SS -> MS RELEASE COMPLETE DeactivateSS operation Return_result 10 SS -> MS CHANNEL RELEASE 11 MS The MS is made to initiate a deactivation of barring of outgoing calls(all facsimile), 12 MS -> SS CHANNEL REQUEST with establishment cause "Other procedures which can be completed with an SDCCH" 13 SS -> MS IMMEDIATE ASSIGNMENT 14 MS -> SS CM SERVICE REQUEST cause: "supplementary service activation" 15 SS -> MS CM SERVICE ACCEPT 16 MS -> SS REGISTER 17 SS -> MS FACILITY GetPassword 18 MS -> SS FACILITY Getpassword operation Return Result 19 SS -> MS RELEASE COMPLETE DeactivateSS operation Return result 21 SS -> MS CHANNEL RELEASE 21 MS Provide correct MMI user indication after step 19 Specific message contents step 6 - all call restrictions: - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = Deactivation: Supplementary service code = B. Basic service code: no Bearer Service present, Tele Service AllSpeechTransmissionServices (TS10) or Telephony (TS 11). step 16 - barring of outgoing calls, - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = Deactivation: Basic service code: no bearer service present, teleservice: all facsimile. steps 7, 17 - - protocol discriminator: non call related SS message. - transaction identifier: in FACILITY same as previous REGISTER message. - message type: FACILITY. - facility: invoke = GetPassword: Guidance info: Password.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4.2 Deactivation rejected
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4.2.1 Rejection after invoke of DeactivateSS operation
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4.2.1.1 Conformance requirements	1) A transaction of any kind being already established, for deactivation of a group of call restriction services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation". 2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the DeactivateSS operation with parameter values according to the user's request (MMI action). 3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected. 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.88, 3GPP TS 04.80 subclauses 2.3 and 3.6. 4) 3GPP TS 02.30 subclause 4.5.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4.2.1.2 Test purpose	1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of a group of call barring services, sending a CM SERVICE REQUEST. 2) To check that the MS sends a REGISTER message containing the invoke of the DeactivateSS operation with the expected parameter values for a group of call barring services. 3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected. 4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer). These checks are performed with a call transaction already established for: BOIC, the RELEASE COMPLETE message being sent at the beginning of the procedure with a facility IE containing a return_error(error) where error is "SS subscription violation".
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4.2.1.3 Method of test	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 call barring. 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 deactivation of incoming calls. Upon receipt of the operation (in a REGISTER message), the system simulator answers with the RELEASE COMPLETE (PD and TI of the SS transaction) message with the Facility information element containing a Return_error(error: SS subscription violation) of the DeactivateSS operation. The system simulator then sends STATUS ENQUIRY, and the MS responds with STATUS message indicating CC state U10. Maximum duration of test 30 s. Expected sequence Step Direction Message Comments 1 MS The MS is made to initiate a deactivation for bi 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 DeactivateSS operation Return_error 6 MS provide correct MMI user indication 7 SS -> MS STATUS ENQUIRY 8 MS -> SS STATUS CC state U10 Specific message content step 4 - - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = DeactivateSS: Supplementary service code = bi. step 5 - - protocol discriminator: non call related SS message. - transaction identifier: same TI as previous REGISTER message. - message type: RELEASE COMPLETE. - facility: return error code: SS subscription violation. For the return error the invoke ID must be the same as in the invoke of the DeactivateSS operation.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4.2.2 Rejection after use of password procedure
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4.2.2.1 Conformance requirements	1) A transaction of any kind being already established, for deactivation of a group of call restriction services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation". 2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the DeactivateSS operation with parameter values according to the user's request (MMI action). 3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected. 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.88, 3GPP TS 04.80 subclauses 2.3 and 3.6. 4) 3GPP TS 02.30 subclause 4.5.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4.2.2.2 Test purpose	1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of deactivation of a group of call restriction services, sending a CM SERVICE REQUEST. 2) To check that the MS sends a REGISTER message containing the invoke of the DeactivateSS operation with the expected parameter values for deactivation of a group of call restriction service. 3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected. 4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer). Those checks are performed with a call transaction already established for: BOICExHC, the RELEASE COMPLETE message being sent at the end of the procedure with a facility IE containing a return_error(error) where error is "NegativePasswordCheck".
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.4.2.2.3 Method of test	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 call barring. 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 deactivation of a group of call restriction services. Upon receipt of the REGISTER message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the DeactivateSS operation requiring the current password. If the manufacturer defined MMI has been used to request the deactivation of a group of call restriction services, then the MS may, by means of appropriate manufacturer defined MMI functions, prompt the user to give a password, depending on the implementation of the manufacturer defined MMI functions. Upon receipt of the FACILITY message, the system simulator sends RELEASE COMPLETE message (PD and TI of the SS transaction) with the Facility information element containing a Return_error(error: NegativePasswordCheck) of the GetPassword 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 a deactivation of BoicExHC 2 MS -> SS CM SERVICE REQUEST cause: "supplementary service activation" 3 SS -> MS CM SERVICE ACCEPT 4 MS -> SS REGISTER 5 SS -> MS FACILITY Invoke = GetPassword (password) 6 MS -> SS FACILITY GetPassword operation Return Result 7 SS -> MS RELEASE COMPLETE Register Password operation ReturnError 8 MS provide correct MMI user indication 9 SS -> MS STATUS ENQUIRY 10 MS -> SS STATUS CC state U10 Specific message content step 4 - - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = DeactivateSS: Supplementary service code = BOICExHC. step 7 - - protocol discriminator: non call related SS message. - transaction identifier: same TI as previous REGISTER message. - message type: RELEASE COMPLETE. - facility: reject code: NegativePasswordCheck. For the reject the invoke ID must be the same as in the invoke of the DeactivateSS operation. step 5 - - protocol discriminator: non call related SS message. - transaction identifier: in FACILITY same as previous REGISTER message. - message type:FACILITY. - facility: invoke = GetPassword: Guidance info: Password (step 5).
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.5 Invocation	Invocation is not applicable.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.6 Interrogation
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.6.1 Interrogation accepted
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.6.1.1 Conformance requirements	1) For interrogation of any specific call restriction service with any parameters, the MS shall transmit successively: 1.1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user"; 1.2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation"; 1.3) and then the REGISTER message containing a facility IE that includes an invoke of the InterrogateSS operation with parameter values according to the user's request (MMI action). 2) 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.88, 3GPP TS 04.80 subclauses 2.3 and 3.6. 4) 3GPP TS 02.30 subclause 4.5.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.6.1.2 Test purpose	1) To check that the MS correctly requests a supplementary service transaction for interrogation of a specific call barring service in CHANNEL REQUEST message. 2) To check that the MS correctly requests a supplementary service transaction for interrogation of a call barring service in the subsequent CM SERVICE REQUEST. 3) To check that the MS sends a REGISTER message containing the invoke of the InterrogateSS operation with the expected parameter values for interrogation of one call restriction service. 4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (which is to be described by the manufacturer). These checks are done for: a) BAIC, the result of the operation being a Basic Service code if supported by the MS. b) BOICExHC, the result of the operation being a SS-status if supported by the MS.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.6.1.3 Method of test	Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is "idle updated". Specific PICS Statements - Support of Barring of All Incoming Calls (TSPC_Serv_SS_BAIC) - Support of Barring of Outgoing International Calls except those directed to the Home PLMN Country (TSPC_Serv_SS_BOICexHC) PIXIT Statements - Description of the user's commands and of display of the answers from the network for call barring. 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 BAIC if supported by the MS. 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 (basic service) of the InterrogateSS operation. The SS transaction and the dedicated channel are released. By means of appropriate MMI functions, the user requests interrogation of BOICExHC if supported by the MS. 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(SS-status) of the InterrogateSS operation. The dedicated channel is released. Maximum duration of test 3 minutes. Expected sequence Step Direction Message Comments Steps 1-9 are applicable if MS supports BAIC (TSPC_Serv_SS_BAIC) and steps 10-18 are applicable if MS supports BOICExHC (TSPC_Serv_SS_BOICexHC). 1 MS The MS is made to initiate a interrogation of BAIC 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 9 SS -> MS CHANNEL RELEASE 9 MS Provide correct MMI user indication after step 7 10 MS The MS is made to initiate a interrogation of call forwarding service for BOICExHC, 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 InterrogateSS operation Return result 17 SS -> MS CHANNEL RELEASE 18 MS Provide correct MMI user indication after step 16 Specific message contents step 6 - BOIC - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = Interrogation: Supplementary service code = BAIC. step 14 - BOICExHC - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = Interrogation: Supplementary service code = BOICExHC.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.6.2 Interrogation rejected
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.6.2.1 Conformance requirements	1) A transaction of any kind being already established, for interrogation of any specific call barring with any parameters, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation". 2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the InterrogateSS operation with parameter values according to the user's request (MMI action). 3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected. 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.88, 3GPP TS 04.80 subclauses 2.3 and 3.6. 4) 3GPP TS 02.30 subclause 4.5.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.6.2.2 Test purpose	1) To check that the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of interrogation of a specific call barring service message, sending a CM SERVICE REQUEST. 2) To check that the MS sends a REGISTER message containing the invoke of the InterrogateSS operation with the expected parameter values for interrogation of call barring. 3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected. 4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer). These checks are performed with a call transaction already established for: a) BICRoam, the RELEASE COMPLETE message being sent with a facility IE containing a return_error(error) where error is "SS not available". b) BOIC, the RELEASE COMPLETE message being sent with a facility IE containing a reject(invoke_problem) where invoke_problem is "resource limitation".
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.6.2.3 Method of test	Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in CC state U10. Specific PICS Statements - Barring of Outgoing International Calls (TSPC_Serv_SS_BOIC) Barring of Incoming Calls when Roaming Outside the Home PLMN Country (TSPC_Serv_SS_BICRoam) PIXIT Statements - Description of the user's commands and of display of the answers from the network for call barring. 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 BICRoam if supported by the MS. 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. By means of appropriate MMI functions, the user requests interrogation of BOIC if supported by the MS. 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 Steps 1-8 are applicable if MS supports BICRoam (TSPC_Serv_SS_BICRoam) and Steps 9-16 are applicable if MS supports BOIC(TSPC_Serv_SS_BOIC). 1 MS The MS is made to initiate a interrogation of call barring service for BICRoam 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 MS provide correct MMI user indication 7 SS -> MS STATUS ENQUIRY 8 MS -> SS STATUS CC state U10 9 MS The MS is made to initiate a interrogation of call barring service for BOIC 10 MS -> SS CM SERVICE REQUEST cause: "supplementary service activation" 11 SS -> MS CM SERVICE ACCEPT 12 MS -> SS REGISTER 13 SS -> MS RELEASE COMPLETE InterrogateSS operation Return_reject 14 MS provide correct MMI user indication 15 SS -> MS STATUS ENQUIRY 16 MS -> SS STATUS CC state U10 Specific message content step 4 - BICRoam - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = Interrogation: Supplementary service code = BICRoam. step 5 - - 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 11 - BOIC - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = Interrogation: Supplementary service code = BOIC. 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.8.7 Normal operation	In case of barring of outgoing call the calling mobile receives information about the activation of supplementary services subscribed. In case of barring of incoming call the calling mobile receives information about the activation of supplementary services subscribed by the other party (the mobile called).
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.7.1 Conformance requirements	Upon receipt of the RELEASE COMPLETE message the MS shall provide the appropriate user indication (which is to be described by the manufacturer). References
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.7.2 Test purpose	To check that upon receipt of the RELEASE COMPLETE message the MS provides the appropriate user indication (as described by the manufacturer). This is tested in the case of an MS making a call to a mobile with incoming calls barred.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.7.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 barring. Foreseen final state of the MS The MS is "idle updated". Test procedure The MS is made to initiate a call. Upon receipt of the SETUP message, the system simulator answers with the negative acknowledgement RELEASE COMPLETE (to simulate a case where call barring is activated). Maximum duration of test 1 minute. Expected sequence Step Direction Message Comments 1 MS -> SS CHANNEL REQUEST 2 SS -> MS IMMEDIATE ASSIGNMENT 3 MS -> SS CM SERVICE REQUEST 4 SS -> MS CM SERVICE ACCEPT 5 MS -> SS SETUP 6 SS -> MS RELEASE COMPLETE 7 SS -> MS CHANNEL RELEASE 8 MS Provide correct MMI user indication after step 8 Specific message content RELEASE COMPLETE - protocol discriminator. - transaction identifier. - message type. - cause: cause value #8. - facility: invoke = notification: SS code = BI. SS status = activation indicator (indicating: Provisioned, registered and active).
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.9 Handling of undefined (future) GSM supplementary services
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.9.1 Mobile station initiated Unstructured supplementary service data operation
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.9.1.1 ProcessUnstructuredSS-request/accepted	Conformance requirements 1) The mobile station shall invoke an USSD request by sending a REGISTER message to the network containing a ProcessUnstructuredSS-Request invoke component. This message will contain the alphabet indicator set to "SMS default alphabet" and the language indicator set to "language unspecified". The ussd-string parameter shall contain the following digits and symbols depending on the operation initiated: Activation: NN(N)# (no supplementary information included) NN(N)SI# (one field of supplementary infor. included) NN(N)SIASIB# (two fields of supplementary infor. included) Deactivation: #NN(N)# #NN(N)SI# #NN(N)SIASIB# Interrogation: #NN(N)# #NN(N)SI# #NN(N)SIASIB# Registration NN(N)# NN(N)SI# *NN(N)SIASIB# Erasure ##NN(N)# ##NN(N)SI# ##NN(N)SIASIB# Operations not yet: see conformance requirement 2). defined in 3GPP TS 02.30. NN(N) features a set of service codes which have not yet been allocated for GSM supplementary services (see 3GPP TS 02.30 for service codes already specified). N is a digit within 1..9 and SI, SIA, SIB strings of characters. 2) Concerning operations which are not yet specified in 3GPP TS 02.30, the MS shall proceed as follows: The entry of 1 or 2 characters defined in the 3GPP TS 03.38 default alphabet followed by "SEND" shall be interpreted by the MS as an USSD request unless the MS is not engaged in a call and the first of the two character entry followed by "SEND" is a "1". Except if the 1 or 2 characters are MS manufacturer defined procedure in idle mode. 3) For supplementary service procedures independent of any call, the initiating side shall establish a MM-connection between the network and the mobile station according to the rules given in 3GPP TS 04.08 / 3GPP TS 24.008. 4) Within a call, the MS shall transmit a USSD request from the user if any. See 3GPP TS 04.07 and 3GPP TS 04.08 / 3GPP TS 24.008 for the handling of multiple MM connections. 5) Upon receipt of the RELEASE COMPLETE message, the MS shall display the information contained to the user in a way described by the manufacturer. References Conformance requirement 1: 3GPP TS 04.90 subclause 6.1, 3GPP TS 02.30 subclause 4.5.2, and 3GPP TS 02.90 subclause 4.1.1. Conformance requirement 2: 3GPP TS 02.30 subclause 4.5.3.2. Conformance requirement 3: 3GPP TS 04.10 subclause 3.2.1. Conformance requirement 4: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.5.1.1. Conformance requirement 5: 3GPP TS 03.90 subclause 6.2.1. Test Purpose 1) To verify that the mobile station invokes an USSD request by sending a REGISTER message to the network containing a ProcessUnstructuredSS-Request invoke component. This message will contain the alphabet indicator set to "SMS default alphabet" and the language indicator set to "language unspecified". The ussd-string parameter shall contain the following digits and symbols depending on the operation initiated: Activation NN(N)# (no supplementary information included) NN(N)SI# (one field of supplementary infor. included) NN(N)SIASIB# (two fields of supplementary infor. included) Deactivation #NN(N)# #NN(N)SI# #NN(N)SIASIB# Interrogation #NN(N)# #NN(N)SI# #NN(N)SIASIB# Registration NN(N)# NN(N)SI# *NN(N)SIASIB# Erasure ##NN(N)# ##NN(N)SI# ##NN(N)SIASIB# Operations not yet: see 2). defined in 3GPP TS 02.30 NN(N) features a set of service codes which have not yet been allocated for GSM supplementary services (see 3GPP TS 02.30 for service codes already specified). N is a digit within 1..9 and SI, SIA, SIB strings of characters. 2) To check that the entry of 1 or 2 characters defined in the 3GPP TS 03.38 default alphabet followed by "SEND" shall be interpreted by the MS as an USSD request unless the MS is not engaged in a call and the first of the two character entry followed by "SEND" is a "1". Except if the 1 or 2 characters are MS manufacturer defined procedure in idle mode. 3) To verify that, for supplementary service procedures independent of any call, the initiating side must establish a MM-connection between the network and the mobile station according to the rules given in 3GPP TS 04.07 and 3GPP TS 04.08 / 3GPP TS 24.008. 4) To verify that, within a call the MS shall transmit a USSD request if any. See 3GPP TS 04.07 and 3GPP TS 04.08 / 3GPP TS 24.008 for the handling of multiple MM connections. 5) To check that upon receipt of the RELEASE COMPLETE message, the MS shall display the information contained to the user in a way described by the manufacturer. Specific PICS Statements - PIXIT Statements - Description of the user's commands and of display of USSD. - Identification of the short strings defining MS manufacturer defined procedure in idle mode (1 or 2 characters defined in the 3GPP TS 03.38 default alphabet followed by "SEND"). Initial Conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in the MM-state "idle updated". Foreseen final state of the MS MM-state "idle updated". Test Procedure By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI) the mobile is made to initiate an Unstructured SS data operation. The mobile first establishes a MM-connection with the SS. Then, a REGISTER message is sent to the SS. Upon receipt of this message, the system simulator answers with the RELEASE COMPLETE message. Then a CHANNEL RELEASE message is sent to the MS to release the main signalling link. The mobile station is forced to originate a call. After the MS has received a CONNECT ACKNOWLEDGE, MMI keys are depressed on the mobile in order to initiate an Unstructured SS data operation. Then a REGISTER message is sent to the SS. Upon receipt of this message, the system simulator answers with the RELEASE COMPLETE message. Finally, the main signalling link is released by transferring a CHANNEL RELEASE message to the MS. Expected Sequence The sequence is executed for execution counters c=1,..,16. The second part of the sequence, namely from step 9 to step 18, is executed for execution counter c=17. Counter c determines the ussd-string selected by the user and sent by the MS (see specific message contents concerning the REGISTER message). Step Direction Message Comments 1 MS The user presses appropriate MMI keys to initiate the desired unstructured SS data operation. 2 MS -> SS CHANNEL REQUEST with establishment cause set to "Other procedures which can be completed with an SDCCH". 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST "Supplementary service activation". 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS REGISTER The SS checks that the content of this message matches specific message content i). 7 SS -> MS RELEASE COMPLETE It terminates the transaction used to initiate the desired unstructured SS data operation. 8 SS -> MS CHANNEL RELEASE The main signalling link is released. MS During step 7 and 8 it is checked that the ussd string, if any, is displayed by the MS in a way described by the manufacturer. See ii). 9 MS The MS is brought to state U10 by initiating a Mobile originating call 10 Specific MMI keys are depressed to initiate the desired undefined SS service operation. DTMF signalling may occur. 11 MS -> SS CM SERVICE REQUEST "Supplementary service activation". 12 SS -> MS CM SERVICE ACCEPT 13 MS -> SS REGISTER The MS starts the transaction on the radio interface. The SS checks that REGISTER matches i). 14 SS -> MS RELEASE COMPLETE It terminates the transaction used to activate the desired undefined SS data operation. See specific message contents ii). 15 SS -> MS DISCONNECT 16 MS -> SS RELEASE 17 SS -> MS RELEASE COMPLETE See message contents iii). 18 SS -> MS CHANNEL RELEASE The main signalling link is released. Specific message contents. i) REGISTER message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call independent)" Transaction identifier Register message type As 3GPP TS 04.80 Facility Information Element See below SS version indicator As specified in 3GPP TS 04.80 Facility Information Element with Invoke = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of FIE contents Component type tag Invoke from 3GPP TS 04.80 Component length depending on the length of ussd-string InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID Arbitrary (1 octet) Operation Code tag From 3GPP TS 04.80 Operation Code length 1 Operation Code ProcessUnstructuredSS-Request ussd-dataCodingScheme 1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" ussd-string c=1, 60# (Activation with no supplementary information included) c=2, 20135# (Activation with one field of supplementary information included) c=3, 70635562# (Activation with two fields of supplementary information included) c=4, #60# (Deactivation with no supplementary information included) c=5, #20135# (Deactivation with one field of supplementary information included) c=6, #70635562# (Deactivation with two fields of supplementary information included) c=7, #60# (Interrogation with no supplementary information included) c=8, #20135# (Interrogation with one field of supplementary information included) c=9, #70635562# (Interrogation with two fields of supplementary information included) c=10, 60# (Registration with no supplementary information included) c=11, 20135# (Registration with one field of supplementary information included) c=12, *70635562# (Registration with two fields of supplementary information included) c=13, ##60# (Erasure with no supplementary information included) c=14, ##20135# (Erasure with one field of supplementary information included) c=15, ##70635562# (Erasure with two fields of supplementary information included) in idle mode : c=16, 1 or 2 characters defined in the 3GPP TS 03.38 default alphabet followed by "SEND" (related to conformance requirement 2). This short string shall not be a MS manufacturer defined procedure as identified in PIXIT statements and shall not be in the format 1x in active call : c=16, 36 ( related to conformance requirement 2) in active call : c=17, 7 (related to conformance requirement 2) ii) RELEASE COMPLETE message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call independent)" Transaction identifier the transaction value is the same as REGISTER transaction value but the transaction flag is different Release Complete message type As 3GPP TS 04.80 Cause omitted. Facility Information Element See below Facility information element with Return Result = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of IE contents Component type tag Return Result from 3GPP TS 04.80 Component length depending on the length of the ussd-string Invoke ID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID The same as the invoke of the ProcessUnstructuredSS-Request Sequence Identifier From 3GPP TS 04.80 Operation Code tag From 3GPP TS 04.80 Operation Code length 1 Operation Code ProcessUnstructuredSS-Request ussd-dataCodingScheme 1 octet long. Alphabet indicator set to "default alphabet" Language indicator set to "undefined" ussd-string chosen at random iii) RELEASE COMPLETE message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call control)" Transaction identifier same as current call. Release Complete message type As 3GPP TS 04.08 / 3GPP TS 24.008
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.9.1.2 ProcessUnstructuredSS-request/cross phase compatibility and error handling	Conformance requirements 1) If a mobile initiated USSD request using protocol version 2 is rejected by the network, and the reason for the rejection is indicated either by the problem code "unrecognized operation" or a cause "facility rejected", the mobile station shall assume that the network only supports protocol version 1 of USSD operations. The mobile station shall re-attempt the request by using the appropriate protocol version 1 USSD operation without a SS version indicator if the unstructured data entered by the user can be coded as an IA5 string. 2) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the manufacturer). If ussd-String information is included this shall be given to the user (in a way described by the manufacturer). References Conformance requirement1: 3GPP TS 04.90 subclause 6.2.1. Conformance requirement2: 3GPP TS 03.90. Test Purpose 1) To verify that If a mobile initiated USSD request using protocol version 2 is rejected by the network, and the reason for the rejection is indicated either by the problem code "unrecognized operation" or a cause "facility rejected", the mobile station shall assume that the network only supports protocol version 1 of USSD operations. The mobile station shall re-attempt the request by using the appropriate protocol version 1 USSD operation without a SS version indicator if the unstructured data entered by the user can be coded as an IA5 string. 2) To check that, upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the manufacturer). If ussd-String information is included this shall be given to the user (in a way described by the manufacturer). Specific PICS Statements - PIXIT Statements - Initial Conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in the MM-state "idle updated". Foreseen final state of the MS MM-state "idle updated". Test Procedure Appropriate MMI keys are pressed on the mobile in order to activate an USSD service. The mobile first establishes a MM-connection with the SS. Then, a REGISTER message is sent to the SS. Upon receipt of this message, the system simulator answers with the RELEASE COMPLETE message with the problem code set to "unrecognized operation", the main signalling link is released. Then the SS checks that the MS re-establishes a MM-connection and re-attempts the request by using a REGISTER message containing an invoke of the ProcessUnstructuredData operation. The SS answers with a normal RELEASE COMPLETE to terminate the transaction. Finally the main signalling link is released by transferring to the MS a CHANNEL RELEASE. Appropriate MMI keys are pressed on the mobile in order to activate an USSD service. The mobile first establishes a MM-connection with the SS. Then, a REGISTER message is sent to the SS. Upon receipt of this message, the system simulator answers with the RELEASE COMPLETE message with the cause element set to "Facility rejected", the main signalling link is released. Then the SS checks that the MS re-establishes a MM-connection and re-attempts the request by using a REGISTER message containing an invoke of the ProcessUnstructuredData operation. Then the SS answers with a normal RELEASE COMPLETE to terminate the transaction. Finally the main signalling link is released by transferring to the MS a CHANNEL RELEASE. The mobile station is forced to originate a call. After the SS has sent a CONNECT ACKNOWLEDGE, MMI keys are pressed on the mobile in order to activate an USSD service. A REGISTER message is sent to the SS. Upon receipt of this message, the system simulator answers with the RELEASE COMPLETE message containing a return error with an error or a reject with a problem. Then the radio link is release by transferring to the MS a CHANNEL RELEASE message. This subtest is repeated with different errors and problems in the RELEASE COMPLETE message. Expected Sequence Step Direction Message Comments 1 MS The user presses appropriate MMI keys to initiate the desired undefined supplementary service operation. 2 MS -> SS CHANNEL REQUEST with establishment cause set to "Other procedures which can be completed with an SDCCH". 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST "Supplementary service activation". 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS REGISTER See specific message contents i).Operation code set to "ProcessUnstructuredSS-Request" 7 SS -> MS RELEASE COMPLETE See specific message contents ii). 8 SS -> MS CHANNEL RELEASE The main signalling link is released. 9 MS -> SS CHANNEL REQUEST with establishment cause set to "Other procedures which can be completed with an SDCCH". 10 SS -> MS IMMEDIATE ASSIGNMENT 11 MS -> SS CM SERVICE REQUEST "Supplementary service activation". 12 SS -> MS CM SERVICE ACCEPT 13 MS -> SS REGISTER Operation code is set to "ProcessUnstructuredSS-Data". See specific message content i). 14 SS -> MS RELEASE COMPLETE normal release of the transaction. See iiia). 15 SS -> MS CHANNEL RELEASE The main signalling link is released. 16 MS The user presses appropriate MMI keys to initiate the desired undefined supplementary service. 17 MS -> SS CHANNEL REQUEST with establishment cause set to "Other procedures which can be completed with an SDCCH". 18 SS -> MS IMMEDIATE ASSIGNMENT 19 MS -> SS CM SERVICE REQUEST "Supplementary service activation". 20 SS -> MS CM SERVICE ACCEPT 21 MS -> SS REGISTER See specific message contents i).Operation code is set to "ProcessUnstructureSS- Request". See i). 22 SS -> MS RELEASE COMPLETE see iii).cause is set to "facility rejected" 23 SS -> MS CHANNEL RELEASE The main signalling link is released. 24 MS -> SS CHANNEL REQUEST with establishment cause set to "Other procedures which can be completed with an SDCCH". 25 SS -> MS IMMEDIATE ASSIGNMENT 26 MS -> SS CM SERVICE REQUEST "Supplementary service activation". 27 SS -> MS CM SERVICE ACCEPT 28 MS -> SS REGISTER Operation code is "ProcessUnstructuredSSdata". See specific message contents i). 29 SS -> MS RELEASE COMPLETE normal release of the transaction. See iiia). 30 SS -> MS CHANNEL RELEASE The main signalling link is released. For k=1 to 10, go through steps 31 to 40. Counter k deals with different kinds of general and invoke problems in step 36. 31 MS The MS is brought to state U10 by initiating a Mobile originating call 32 Specific MMI keys are pressed to initiate the desired undefined supplementary service. DTMF signalling may occur. 33 MS -> SS CM SERVICE REQUEST "supplementary service activation" 34 SS -> MS CM SERVICE ACCEPT 35 MS -> SS REGISTER The MS starts the transaction on the radio interface. See specific message contents i).The operation code is set to "ProcessUnstructuredSS-Request". 36 SS -> MS RELEASE COMPLETE different errors and problems are sent. See specific message contents iiib) and iiic). 37 SS -> MS DISCONNECT 38 MS -> SS RELEASE 39 SS -> MS RELEASE COMPLETE See message contents iv). 40 SS -> MS CHANNEL RELEASE The main signalling link is released. Specific message contents. i) REGISTER message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call independent)" Transaction identifier Register message type As 3GPP TS 04.80 Facility Information Element See below SS version indicator As specified in 3GPP TS 04.80 for version 2 protocol Always omitted for version 1 protocol For steps 6, 21 and 35, Facility Information Element with Invoke = ProcessUnstructuredSS-Request (for version 2 protocol) component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For steps 13 and 28, Facility Information Element with Invoke = ProcessUnstructuredSS-Data (for version 1 protocol) as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of FIE contents Component type tag Invoke from 3GPP TS 04.80 Component length Depending on the length of ussd-string InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID Arbitrary (1 octet) Operation Code tag From 3GPP TS 04.80 Operation Code length 1 Operation Code ProcessUnstructuredSS-Request (for version 2 protocol) ProcessUnstructuredSS-Data (for version 1 protocol) ussd-dataCodingScheme 1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" ussd-string 70635*562# ii) RELEASE COMPLETE message. Contents Value/remark Protocol Discriminator Set to "Supplementary service (call independent)" Transaction identifier The transaction value is the same as the REGISTER transaction value but the transaction flag is different Facility message type As 3GPP TS 04.80 Facility Information Element See below Facility Information Element with Reject = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.6. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of FIE contents Component type tag Reject from 3GPP TS 04.80 Component length Depending on the length of ussd-string InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID The same as the invoke of the ProcessUnstructuredSS- Request Problem Code tag As 3GPP TS 04.80 Problem Code length General Problem code Unrecognized operation iii) RELEASE COMPLETE message. Contents Value/remark Protocol Discriminator Set to "Supplementary service (call independent)" Transaction identifier The transaction value is the same as the REGISTER transaction value but the transaction flag is different Release complete message type As 3GPP TS 04.80 Cause For step 22, cause is set to "facility rejected" and FIE is omitted. For steps 14, 29 and 36 this field is omitted. Facility Information Element For step 14 and 29 see iiia). For step 36 see iiib) and iiic). For step 22 this field is omitted. iiia) For steps 14 and 29, Facility Information Element with Return Result = ProcessUnstructuredSS-Data component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of FIE contents Component type tag ReturnResult from 3GPP TS 04.80 Component length InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID The same as the invoke of the ProcessUnstructuredSS- Data Sequence Tag As 3GPP TS 04.80 / 3GPP TS 24.080 Table 3.4 Sequence length As 3GPP TS 04.80 / 3GPP TS 24.080 Table 3.4 Operation Code Tag As 3GPP TS 04.80 / 3GPP TS 24.080 Table 3.4 Operation Code Length As 3GPP TS 04.80 / 3GPP TS 24.080 Table 3.4 Operation Code ProcessUnstructuredSS-Data Parameters As 3GPP TS 04.80 / 3GPP TS 24.080 Table 3.4 iiib) Facility Information Element with Return Error = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.5. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of FIE contents Component type tag Return Error from 3GPP TS 04.80 Component length InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID The same as the invoke of the ProcessUnstructuredSS- Request Error Code tag As 3GPP TS 04.80 Error Code length Error Code k=1, system failure k=2, data missing k=3, unknown alphabet k=4, unexpected data value iiic) Facility Information Element with Reject = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.6. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of FIE contents Component type tag Reject from 3GPP TS 04.80 Component length InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID The same as the invoke of the ProcessUnstructuredSS- Request Problem Code tag As 3GPP TS 04.80 Problem Code length General Problem code Invoke Problem code k=5, Unrecognized component k=6, Mistyped component k=7, Badly structured component k=8, Mistyped parameter k=9, Resource limitation k=10, Initiating release iv) RELEASE COMPLETE message. Contents Value/remark Protocol Discriminator Set to "Supplementary service (call control)" Transaction identifier Same as current call. Release Complete message type As 3GPP TS 04.08 / 3GPP TS 24.008
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.9.2 Network initiated unstructured supplementary service operations
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.9.2.1 UnstructuredSS-Notify/accepted	Conformance requirements 1) For a USSD notification, the MS shall display the text provided and await user input. The MS shall acknowledge the operation by sending a FACILITY message containing an empty result component to the network. 2) The MS shall include alphabet and language indicators in the response to the network. The alphabet indicator shall indicate "SMS default alphabet". The language indicator shall indicate "language unspecified". 3) At any stage while the MS is registered with a network, the network may send an unstructured string to the MS. So, the MS shall be able to process the operation during a call or out of a call. References Conformance requirement 1: 3GPP TS 04.90 subclause 5.2.1. Conformance requirement 2: 3GPP TS 02.90 subclause 4.2.2. Conformance requirement 3: 3GPP TS 02.90 subclause 4.2.1. Test Purpose 1) To verify that for a USSD notification, the MS shall display the text provided and await user input. If the user enters a response, the MS shall acknowledge the operation by sending a FACILITY message containing an empty result component to the network. 2) To verify that the MS shall include alphabet and language indicators in the response to the network. The alphabet indicator shall indicate "SMS default alphabet". The language indicator shall indicate "language unspecified". 3) To check that the MS shall be able to process the operation during a call or out of a call. Specific PICS Statements - PIXIT Statements - Initial Conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in the MM-state "idle updated". Foreseen final state of the MS MM-state "idle updated". Test Procedure - The MS is paged and a RR-connection is established. Then, the SS sends a REGISTER message containing a facility information element with operation code set to ProcessUnstructuredSS-Notify. The user checks that the ussd string sent by the SS is correctly displayed by the MS. The MS has to send a FACILITY message with an empty return result component. - Then the SS originates a call to the MS. When the MS is in the U10 state, the SS releases the transaction identifier concerning USSD transaction by sending a RELEASE COMPLETE. The SS initiates a new ussd transaction by sending a REGISTER message containing a facility information element with operation code set to UnstructuredSS-Notify. The user checks that the ussd string sent by the SS is correctly displayed by the MS. The MS has to send a FACILITY message with an empty return result component. Finally the SS releases both MM connections and the radio link. Step Direction Message Comments 1 SS -> MS PAGING REQUEST TYPE 1 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT a SDCCH is allocated to the MS. 4 MS -> SS PAGING RESPONSE 5 SS -> MS REGISTER initiation of the transaction concerning the USSD notification operation. See i). 6 The MS has to display the USSD string sent from the network. 7 MS -> SS FACILITY signalling message sent by the MS as the response. The SS checks that it matches ii). 8 SS -> MS SETUP incoming call. 9 MS -> SS CALL CONFIRMED 10 MS -> SS ALERTING 11 MS -> SS CONNECT 12 SS -> MS ASSIGNMENT COMMAND a TCH is allocated to the MS. 13 MS -> SS ASSIGNMENT COMPLETE 14 SS -> MS CONNECT ACKNOWLEDGE 15 SS -> MS RELEASE COMPLETE this message releases the transaction concerning the USSD operation. See iii). 16 SS -> MS REGISTER initiation of a USS request operation during a call. See specific message contents i). 17 The MS has to display the USSD string received from the SS. 18 MS -> SS FACILITY The SS checks that this message matches ii). 19 SS -> MS RELEASE COMPLETE It releases he transaction identifier concerning the ussd operation. 20 SS -> MS DISCONNECT call release initiation. see iv). 21 MS -> SS RELEASE 22 SS -> MS RELEASE COMPLETE 23 SS -> MS CHANNEL RELEASE Specific message contents. i) REGISTER message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call independent)" Transaction identifier Register message type As 3GPP TS 04.80 Facility Information Element See below Facility Information Element with Invoke = UnstructuredSS-Notify component type as defined in 3GPP TS 04.90, subclause 5.2.1. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of FIE contents Component type tag Invoke from 3GPP TS 04.80 Component length depending on the length of ussd-string InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID Arbitrary (1 octet) Operation Code tag From 3GPP TS 04.80 Operation Code length 1 Operation Code UnstructuredSS-Notify ussd-dataCodingScheme 1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" ussd-string arbitrary chosen by the SS ii) Facility message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call independent)" Transaction identifier the transaction value is the same as REGISTER transaction value but the transaction flag is different Facility message type As 3GPP TS 04.80 Facility Information Element See below Facility Information Element with Return Result = empty result component according to 3GPP TS 04.90, subclause 5.2.1, figure 5.3. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of FIE contents Component type tag Return Result from 3GPP TS 04.80 Component length InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID The same as the invoke of the UnstructuredSS-Notify iii) RELEASE COMPLETE message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call independent)" Transaction identifier the transaction value is the same as REGISTER transaction flag is different Release Complete message type As 3GPP TS 04.80 Facility Information Element omitted iv) RELEASE COMPLETE message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call control)" Transaction identifier same as current call. Release Complete message type As 3GPP TS 04.08 / 3GPP TS 24.008
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.9.2.2 UnstructuredSS-Notify/rejected on user busy	Conformance requirements 1) When the mobile station receives an USSD operation in parallel to any call independent supplementary transaction, it shall respond with a return error component in a RELEASE COMPLETE message, containing the "USSD-Busy" error. References Conformance requirement 1: 3GPP TS 04.90 subclause 5.1.1. Test Purpose 1) To verify that when the mobile station receives an USSD operation in parallel to any call independent supplementary transaction, it responds with a return error component in a RELEASE COMPLETE message, containing the "USSD-Busy" error. Specific PICS Statements - PIXIT Statements - Initial Conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in the MM-state "idle updated". Foreseen final state of the MS MM-state "idle updated". Test Procedure - The MS is paged and a RR-connection is established. Then, the SS sends a REGISTER message containing a facility information element with operation code set to UnstructuredSS-Notify. The SS initiates an other USSD transaction by sending a REGISTER message with transaction identifier different form the previous one. The SS checks that the MS answers with a RELEASE COMPLETE message with an error component set to "USSD busy". Then the SS releases the radio link. Test Procedure Step Direction Message Comments 1 SS -> MS PAGING REQUEST TYPE 1 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT a SDCCH is allocated to the MS. 4 MS -> SS PAGING RESPONSE 5 SS -> MS REGISTER initiation of the transaction concerning the USSD notification operation. See i). 6 The MS has to display the USSD string sent from the SS. 7 MS -> SS FACILITY See ii). 8 SS -> MS REGISTER initiation of an other USSD notification. The transaction identifier is different from that in step 5.See i). 9 MS -> SS RELEASE COMPLETE error set to "USSD busy". Transaction initiated in step 6 by the network is rejected by the MS. See iii). 10 SS -> MS RELEASE COMPLETE normal release of transaction initiated in step 5.See iii). 11 SS -> MS CHANNEL RELEASE release of the main signalling link. Specific message contents. i) REGISTER message. See subclause 31.9.2.1. ii) FACILITY message. See subclause 31.9.2.1. iii) RELEASE COMPLETE message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call independent)" Transaction identifier for step 10, same as REGISTER transaction identifier for step 9, the transaction value is the same as REGISTER transaction value but the transaction flag is different. Release complete message type As 3GPP TS 04.80 Facility Information Element for step 9 see iiib). for step 10, see iiia). iiia) Facility Information Element with Return Result = UnstructuredSS-Notify component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of FIE contents Component type tag Return Result from 3GPP TS 04.80 Component length InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID The same as the invoke of the UnstructuredSS-Notify in step 5 iiib) Facility Information Element with Return Error = UnstructuredSS-Notify component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.5. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 Length of FIE contents Component type tag Return Result from 3GPP TS 04.80 Component length InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID The same as the invoke of the UnstructuredSS-Notify in step 8 Error Code tag As 3GPP TS 04.80 Error Code length Error Code USSD Busy
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.9.2.3 UnstructuredSS-Request/accepted	Conformance requirements 1) For a USSD request, the MS shall display the text provided and await user input. if the user enters a response, the MS shall return the response to the network, maintaining the transaction. 2) The MS shall include alphabet and language indicators in the response to the network. The alphabet indicator shall indicate "SMS default alphabet". The language indicator shall indicate "language unspecified". 3) At any stage while the MS is registered with a network, the network may send an unstructured string to the MS. So, the MS shall be able to process the operation during a call or out of a call. References Conformance requirement 1: 3GPP TS 03.90 subclause 5.2.5. Conformance requirement 2: 3GPP TS 02.90 subclause 4.2.2. Conformance requirement 3: 3GPP TS 02.90 subclause 4.2.1. Test Purpose 1) To test that, for a USSD request, the MS shall display the text provided and await user input. if the user enters a response, the MS shall return the response to the network, maintaining the transaction. 2) To verify that the MS shall include alphabet and language indicators in the response to the network. The alphabet indicator shall indicate "SMS default alphabet". The language indicator shall indicate "language unspecified". 3) To check that the MS shall be able to process the operation during a call or out of a call. Specific PICS Statements - PIXIT Statements - Initial Conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in the MM-state "idle updated". Foreseen final state of the MS MM-state "idle updated". Test Procedure - The MS is paged and a RR-connection is established. Then, the SS sends a REGISTER message containing a facility information element with operation code set to ProcessUnstructuredSS-Request. The user checks that the ussd string sent by the SS is correctly displayed by the MS and answers the request by depressing MMI keys. Then the MS has to send a FACILITY message with ussd string exactly containing the digits and symbols expressed on the mobile equipment keypad. - Then the SS originates a call to the MS. When the MS is in the U10 state, the SS releases the transaction identifier concerning USSD transaction by sending a RELEASE COMPLETE. The SS initiates a new ussd transaction by sending a REGISTER message containing a facility information element with operation code set to UnstructuredSS-Request. The user checks that the ussd string sent by the SS is correctly displayed by the MS and answers the request by depressing MMI keys. Then the MS has to send a FACILITY message with ussd string exactly containing the digits and symbols expressed on the mobile equipment keypad. Finally the SS releases both MM connections and the radio link. Step Direction Message Comments 1 SS -> MS PAGING REQUEST TYPE 1 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT a SDCCH is allocated to the MS. 4 MS -> SS PAGING RESPONSE 5 SS -> MS REGISTER initiation of the transaction concerning the USSD Request operation. See i). 6 The MS has to display the USSD string sent from the network and waits for the user response. By depressing MMI keys followed by SEND the user answers 7 MS -> SS FACILITY signalling message sent by the MS as the response. See ii). 8 SS -> MS SETUP incoming call. 9 MS -> SS CALL CONFIRMED 10 MS -> SS ALERTING 11 MS -> SS CONNECT 12 SS -> MS ASSIGNMENT COMMAND a TCH is allocated to the MS. 13 MS -> SS ASSIGNMENT COMPLETE 14 SS -> MS CONNECT ACKNOWLEDGE 15 SS -> MS RELEASE COMPLETE this message releases the transaction concerning the USSD operation. See iii). 16 SS -> MS REGISTER initiation of a USS request operation during a call. See specific message contents i). 17 The MS has to display the USSD string received from the SS. By depressing MMI keys followed by SEND, the user answers. DTMF signalling may occur. 18 MS -> SS FACILITY See ii). 19 SS -> MS RELEASE COMPLETE It releases the transaction identifier concerning the ussd operation. 20 SS -> MS DISCONNECT 21 MS -> SS RELEASE 22 SS -> MS RELEASE COMPLETE call release initiation. see iv). 23 SS -> MS CHANNEL RELEASE Specific message contents i) REGISTER message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call independent)" Transaction identifier Register message type As 3GPP TS 04.80 Facility Information Element See below Facility Information Element with Invoke = UnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of FIE contents Component type tag Invoke from 3GPP TS 04.80 Component length depending on the length of ussd-string InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID Arbitrary (1 octet) Operation Code tag From 3GPP TS 04.80 Operation Code length 1 Operation Code UnstructuredSS-Request ussd-dataCodingScheme 1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" ussd-string arbitrary chosen by the SS ii) Facility message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call independent)" Transaction identifier the transaction identifier value is the same as REGISTER transaction value but the transaction flag is different. Facility message type As 3GPP TS 04.80 Facility Information Element See below Facility Information Element with Return Result = UnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of FIE contents Component type tag Return Result from 3GPP TS 04.80 Component length depending on the length of ussd-string InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID The same as the invoke of the UnstructuredSS-Request Sequence Identifier Sequence length Operation Code tag 1 Operation Code length 1 Operation Code UnstructuredSS-Request ussd-dataCodingScheme 1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" ussd-string contains exactly the digits and symbols expressed on the mobile equipment keypad. iii) RELEASE COMPLETE message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call independent)" Transaction identifier same as REGISTER transaction identifier Release Complete message type As 3GPP TS 04.80 Facility Information Element omitted iv) RELEASE COMPLETE message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call control)" Transaction identifier same as current call. Release Complete message type As 3GPP TS 04.08 / 3GPP TS 24.008
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.9.2.4 UnstructuredSS-Request/rejected on user busy	Conformance requirements 1) When the mobile station receives an USSD operation in parallel to any call independent supplementary transaction, it shall respond with a return error component in a RELEASE COMPLETE message, containing the "USSD-Busy" error. References Conformance requirement 1: 3GPP TS 04.90 subclause 5.1.1. Test Purpose 1) To verify that when the mobile station receives an USSD operation in parallel to any call independent supplementary transaction, it responds with a return error component in a RELEASE COMPLETE message, containing the "USSD-Busy" error. Specific PICS Statements - PIXIT Statements - Initial Conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in the MM-state "idle updated". Foreseen final state of the MS MM-state "idle updated". Test Procedure - The MS is paged and a RR-connection is established. Then, the SS sends a REGISTER message containing a facility information element with operation code set to UnstructuredSS-Request. The SS initiates an other USSD transaction by sending a REGISTER message with transaction identifier different form the previous one. The SS checks that the MS answers with a RELEASE COMPLETE message with an error component set to "USSD busy". Then the SS releases the radio link. Test Procedure Step Direction Message Comments 1 SS -> MS PAGING REQUEST TYPE 1 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT a SDCCH is allocated to the MS. 4 MS -> SS PAGING RESPONSE 5 SS -> MS REGISTER initiation of the transaction concerning the USSD Request operation. See i). 6 The MS has to display the USSD string sent from the network and waits for the user response. By depressing MMI keys followed by SEND the user answers. 7 MS -> SS FACILITY signalling message sent by the MS as the response to the request. See ii). 8 SS -> MS REGISTER initiation of an other USSD request. The transaction identifier is different from that in step 5.See i). 9 MS -> SS RELEASE COMPLETE error set to "USSD busy". Transaction initiated in step 6 by the network is rejected by the MS. See iii). 10 SS -> MS RELEASE COMPLETE normal release of transaction initiated in step 5. See iii). 11 SS -> MS CHANNEL RELEASE release of the main signalling link. Specific message contents i) REGISTER message. See subclause 31.9.2.3. ii) FACILITY message. See subclause 31.9.2.3. iii) RELEASE COMPLETE message. Contents Value/remark Protocol Discriminator set to "Supplementary service (call independent)" Transaction identifier the transaction identifier value is the same as REGISTER transaction value but the transaction flag is different. Release complete message type As 3GPP TS 04.80 Facility Information Element for step 9 see iiib). for step10 see iiia). iiia) Facility Information Element with Return Result = UnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of FIE contents Component type tag Return Result from 3GPP TS 04.80 Component length depending on the length of ussd-string InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID The same as the invoke of the UnstructuredSS-Request iiib) Facility Information Element with Return Error = UnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.5. Contents Value/remark Facility IE identifier As 3GPP TS 04.08 / 3GPP TS 24.008 Length of FIE contents Component type tag Return Error from 3GPP TS 04.80 Component length depending on the length of ussd-string InvokeID tag From 3GPP TS 04.80 Invoke ID length 1 Invoke ID The same as the invoke of the UnstructuredSS-Request Error Code tag As 3GPP TS 04.80 Error Code length Error Code USSD Busy
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.10 MMI input for USSD
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.10.1 Conformance requirements	If the MS cannot interpret the MMI input as a defined GSM Supplementary Services, SIM control procedure or MS manufacturer-defined procedure, and if the MMI input is in the form: - "entry of any characters defined in the 3GPP TS 03.38 Default Alphabet (up to the maximum defined in 3GPP TS 04.80) followed by #SEND"; or - "entry of 1 or 2 characters defined in the 3GPP TS 03.38 Default Alphabet followed by SEND"; then it shall be interpreted by the MS as Unstructured SS Data and sent transparently towards the network, unless the MS is not engaged in a call and the first digit of the 2 character entry, followed by SEND, is a "1". In this case the MS shall transmit this as a call-setup request. References 3GPP TS 02.30 subclause 4.5.3.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.10.2 Test purpose	To check that the entry of 2 digits in the form 1X (X in the set 0,...9) followed by SEND is accepted by the mobile station in idle mode as a normal call establishment for the 1X number. It is checked that the MS sends a CHANNEL REQUEST, sends CM SERVICE REQUEST message for mobile originated call (after having received an IMMEDIATE ASSIGNMENT), and then sends the SETUP message containing the 1X phone number as called number (after having received the CM SERVICE ACCEPT message).
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.10.3 Method of test	Initial conditions System Simulator: 1 cell, default parameters. Mobile Station The MS is "idle updated"; Specific PICS Statements - PIXIT Statements - Foreseen final state of the MS: The MS is "idle updated. Test procedure The user requests call establishment successively for every 2 digit phone number of the 1X form (X in the set 0,...9) allowing ten seconds between each attempts. Maximum duration of test 3 minutes. Expected Sequence The following sequence is executed for execution counter k = 1 to 10. Step Direction Message Comments 1 MS The MS is made to initiate call establishment for phone number 1X (where X = k‑1) 2 MS -> SS CHANNEL REQUEST with establishment cause related to mobile originating call 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST "mobile originating call" 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP called BCD number is 1X 7 SS -> MS RELEASE COMPLETE 8 Wait for 10 seconds Specific message contents. None.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.11 Specific message contents and ASN.1 codings	Introduction In this subclause a mixed form of ASN.1 coding has been used in ASN.1 components within the messages. Some components use the indefinite form of coding, and some use the short definite form. An example of a FACILITY message using indefinite form of coding is described below. The same message using short definite form of coding is described in Test 31.2.1.1.1 Step 7 of this subclause. Contents Value/remark Coding Length of FIE contents 43 2B Component type tag Return Result A2 Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence tag 30 Sequence length indefinite 80 Operation Code tag 02 Operation Code length 1 01 Operation Code RegisterSS 0A SS-Information Forwarding Info tag Tag=A0 A0 Forwarding Info length indefinite 80 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFNRy 2A Forwarding Feature List Seq. 30 Length Indicator indefinite 80 Forwarding Feature Seq. 30 Forwarding Feature length indefinite 80 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code AllSpeechTransmissionServices 10 SS-Status Tag=84 84 SS-Status length 1 01 SS-Status code Prov., Registered, Active 07 Forwarded To Number identifier Tag=85 85 ISDN-AddressString length 5 05 AddressString type Unknown 81 AddressString TBCD-String: 00431234 00 34 21 43 NoReplyConditionTime Tag=87 87 Length Indicator 1 01 NoReplyConditionTime 5 05 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.2.1.1.1. Registration accepted MMI sequence: *6100431234115# Step 6: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 26 1A Component type tag Invoke A1 (note 1) Component length 24 18 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code RegisterSS 0A RegisterSS-Arg Seq. 30 (note 1) RegisterSS-Arg length 16 10 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFNRy 2A Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code AllSpeechTransmissionServices 10 Forwarded To Number identifier Tag=84 84 AddressString length 5 05 AddressString type Unknown 81 AddressString TBCD-String: 00431234 00 34 21 43 NoReplyConditionTime tag Tag=85 85 NoReplyConditionTime length 1 01 NoReplyConditionTime 5 05 NOTE 1: This component may use the indefinite form. Step 7: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 35 23 Component type tag Return Result A2 (note 1) Component length 33 21 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence tag 30 (note 1) Sequence length 28 1C Operation Code tag 02 Operation Code length 1 01 Operation Code RegisterSS 0A SS-Information Forwarding Info tag Tag=A0 A0 (note 1) Forwarding Info length 23 17 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFNRy 2A Forwarding Feature List Seq. 30 (note 1) Length Indicator 18 12 Forwarding Feature Seq. 30 (note 1) Forwarding Feature length 16 10 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code AllSpeechTransmissionServices 10 SS-Status Tag=84 84 SS-Status length 1 01 SS-Status code Prov., Registered, Active 07 Forwarded To Number identifier Tag=85 85 ISDN-AddressString length 5 05 AddressString type Unknown 81 AddressString TBCD-String: 00431234 00 34 21 43 NoReplyConditionTime Tag=87 87 Length Indicator 1 01 NoReplyConditionTime 5 05 MMI sequence: *210043123413# Step 15: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 23 17 Component type tag Invoke A1 (note 1) Component length 21 15 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code RegisterSS 0A RegisterSS-Arg Seq. 30 (note 1) RegisterSS-Arg length 13 0D SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFU 21 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code All Facsimile Services 60 Forwarded To Number identifier Tag=84 84 AddressString length 5 05 AddressString type Unknown 81 AddressString TBCD-String: 00431234 00 34 21 43 Step 16: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 42 2A Component type tag Return Result A2 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence tag 30 (note 1) Sequence length indefinite 80 Operation Code tag 02 Operation Code length 1 01 Operation Code RegisterSS 0A SS-Information Forwarding Info tag Tag=A0 A0 (note 1) Forwarding Info length indefinite 80 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFU 21 Forwarding Feature List Seq. 30 (note 1) Length indicator indefinite 80 Forwarding Feature Seq. 30 (note 1) Forwarding Feature length indefinite 80 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code All Facsimile Services 60 SS-Status Tag=84 84 SS-Status length 1 01 SS-Status code Prov., Registered, Active 07 Forwarded To Number identifier Tag=85 85 ISDN-AddressString length 5 05 AddressString type Unknown 81 AddressString TBCD-String: 00431234 00 34 21 43 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.2.1.1.2. Registration rejected MMI sequence: 670043123421# Step 4: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 23 17 Component type tag Invoke A1 (note 1) Component length 21 15 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code RegisterSS 0A RegisterSS-Arg Seq. 30 (note 1) RegisterSS-Arg length 13 0D SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFB 29 Basic Service Code identifier BearerserviceCode 82 Bearerservice length 1 01 Bearerservice code AllAsynchronousServices 60 Forwarded To Number identifier Tag=84 84 AddressString length 5 05 AddressString type Unknown 81 AddressString TBCD-String: 00431234 00 34 21 43 Step 5: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 8 08 Component type tag Return Error A3 (note 1) Component length 6 06 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Error Code tag 02 Error Code length 1 01 Error Code BearerServiceNot Provisioned 0A MMI sequence: 0020043123413# Step 11: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 23 1715 Component type tag Invoke A1 (note 1) Component length 21 15 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code RegisterSS 0A RegisterSS-Arg 30 (note 1) RegisterSS-Arg length 13 0D SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CF 20 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code All Facsimile Services 60 Forwarded To Number identifier Tag=84 84 AddressString length 5 05 AddressString type Unknown 81 AddressString TBCD-String: 00431234 00 34 21 43 Step 12: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 8 08 Component type tag Reject A4 (note 1) Component length 6 06 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Invoke Problem tag Tag=81 81 Invoke Problem length 1 01 Invoke Problem code Resource limitation 03 Test 31.2.1.2.1. Erasure accepted MMI sequence: ##00413# Step 6: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 16 10 Component type tag Invoke A1 (note 1) Component length 14 0E Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code EraseSS 0B SS-ForBS Seq. 30 (note 1) SS-ForBS length 6 06 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFC 28 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code All Facsimile Services 60 Step 7: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 31 1F Component type tag Return Result A2 (note 1) Component length 29 1D Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence tag 30 (note 1) Sequence length 24 18 Operation Code tag 02 Operation Code length 1 01 Operation Code EraseSS 0B SS-Information Forwarding Info tag Tag=A0 A0 (note 1) Forwarding Info length indefinite 80 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFC 28 Forwarding Feature List Seq. 30 (note 1) Length Indicator indefinite 80 Forwarding Feature Seq. 30 (note 1) Forwarding Feature length indefinite 80 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code All Facsimile Services 60 SS-Status Tag=84 84 SS-Status length 1 01 SS-Status code Provisioned 04 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 MMI sequence: ##62# Step 15: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 13 0D Component type tag Invoke A1 (note 1) Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code EraseSS 0B SS-ForBS Seq. 30 (note 1) SS-ForBS length 3 03 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFNRc 2B Step 16: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 22 16 Component type tag Return Result A2 (note 1) Component length 20 14 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence tag 30 (note 1) Sequence length 15 0F Operation Code tag 02 Operation Code length 1 01 Operation Code EraseSS 0B SS-Information Forwarding Info tag Tag=A0 A0 (note 1) Forwarding Info length 10 0A SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFNRc 2B Forwarding Feature List Seq. 30 (note 1) Length Indicator 5 05 Forwarding Feature Seq. 30 (note 1) Forwarding Feature length 3 03 SS-Status Tag=84 84 SS-Status length 1 01 SS-Status code Provisioned 04 Test 31.2.1.2.2. Erasure rejected MMI sequence: ##2111# Step 4: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 16 10 Component type tag Invoke A1 (note 1) Component length 14 0E Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code EraseSS 0B SS-ForBS 30 (note 1) SS-ForBS length 6 06 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFU 21 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code AllSpeechTransmissionServices 10 Step 5: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 8 08 Component type tag Return Error A3 (note 1) Component length 6 06 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Error Code tag Tag=2 02 Error Code length 1 01 Error Code TeleserviceNotProvisioned 0B MMI sequence: ##6113# Step 11: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 16 10 Component type tag Invoke A1 (note 1) Component length 14 0E Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code EraseSS 0B SS-ForBS 30 (note 1) SS-ForBS length 6 06 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFNRy 2A Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code All Facsimile Services 60 Step 12: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 10 0A Component type tag Reject A4 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Invoke Problem tag 81 Invoke Problem length 1 01 Invoke Problem Resource limitation 03 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.2.1.3. Activation MMI sequence: 002*22# Step 6: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 16 10 Component type tag Invoke A1 (note 1) Component length 14 0E Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code ActivateSS 0C SS-ForBS 30 (note 1) SS-ForBS length 6 06 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CF 20 Basic Service Code identifier BearerserviceCode 82 Bearerservice length 1 01 Bearerservice code AllSynchronousServices 68 Step 7:SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 29 1D Component type tag Return Result A2 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence tag 30 (note 1) Sequence length 20 14 Operation Code tag 02 Operation Code length 1 01 Operation Code ActivateSS 0C SS-Information Forwarding Info tag Tag=A0 A0 (note 1) Forwarding Info length indefinite 80 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CF 20 Forwarding Feature List Seq. 30 (note 1) Length Indicator 8 08 Forwarding Feature Seq. 30 (note 1) Forwarding Feature length 6 06 Basic Service Code identifier BearerserviceCode 82 Bearerservice length 1 01 Bearerservice code AllSynchronousServices 68 SS-Status Tag=4 84 SS-Status length 1 01 SS-Status code Prov., Registered, Active 07 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 MMI sequence: 21# Step 15: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 13 0D Component type tag Invoke A1 (note 1) Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code ActivateSS 0C SS-ForBS Seq. 30 (note 1) SS-ForBS length 3 06 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFU 21 Step 16: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 26 1A Component type tag Return Result A2 (note 1) Component length 24 18 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence tag 30 (note 1) Sequence length indefinite 80 Operation Code tag 02 Operation Code length 1 01 Operation Code ActivateSS 0C SS-Information Forwarding Info tag Tag=A0 A0 (note 1) Forwarding Info length indefinite 80 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFU 21 Forwarding Feature List Seq. 30 (note 1) Length Indicator 5 05 Forwarding Feature Seq. 30 (note 1) Forwarding Feature length 3 03 SS-Status Tag=84 84 SS-Status length 1 01 SS-Status code Prov. Registered, Active 07 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.2.1.4. Deactivation MMI sequence: #00411# Step 6: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 16 10 Component type tag Invoke A1 (note 1) Component length 14 0E Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code DeactivateSS 0D SS-ForBS Seq. 30 (note 1) SS-ForBS length 6 06 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFC 28 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code AllSpeechTransmissionServices 10 Step 7: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 29 1D Component type tag Return Result A2 (note 1) Component length 27 1B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence tag 30 (note 1) Sequence length 22 16 Operation Code tag 02 Operation Code length 1 01 Operation Code DeactivateSS 0D SS-Information Forwarding Info tag Tag=A0 A0 (note 1) Forwarding Info length indefinite 80 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFC 28 Forwarding Feature List Seq. 30 (note 1) Length Indicator indefinite 80 Forwarding Feature Seq. 30 (note 1) Forwarding Feature length 6 06 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code AllSpeechTransmissionServices 10 SS-Status Tag=84 84 SS-Status length 1 01 SS-Status code Provisioned, Registered 06 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 MMI sequence: #6213# Step 15: MS -> SS REGISTER Contents Value/remark Coding Same header as Step 6 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFNRc 2B Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code All Facsimile Services 60 Step 16: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 27 1B Component type tag Return Result A2 (note 1) Component length 25 19 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence tag 30 (note 1) Sequence length 20 14 Operation Code tag 02 Operation Code length 1 01 Operation Code DeactivateSS 0D SS-Information Forwarding Info tag Tag=A0 A0 (note 1) Forwarding Info length 15 0F SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFNRc 2B Forwarding Feature List Seq. 30 (note 1) Length Indicator 10 0A Forwarding Feature Seq. 30 (note 1) Forwarding Feature length indefinite 80 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code All Facsimile Services 60 SS-Status Tag=4 84 SS-Status length 1 01 SS-Status code Provisioned, Registered 06 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.2.1.6.1. Interrogation accepted MMI sequence: #67# Step 6: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 13 0D Component type tag Invoke A1 (note 1) Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code InterrogateSS 0E SS-ForBS 30 (note 1) SS-ForBS length 3 03 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFB 29 Step 7: SS -> MS RELEASE COMPLETE Contents Value/Remark Coding Length of FIE contents 13 0D Component type tag Return Result A2 (note 1) Component length 11 0B Invoke ID tag Tag=02 02 Invoke ID length 1 01 Invoke ID As received 03 Sequence tag 30 (note 1) Sequence length 6 06 Operation code tag Tag=02 02 Operation code length 1 01 Operation code InterrogateSS 0E InterrogateSS-Res Choice SS-Status Tag=80 80 SS-Status length 1 01 SS-Status Provisioned 04 MMI sequence: #61*11# Step 15: MS -> SS REGISTER Contents Value/Remark Coding Length of FIE contents 16 10 Component type tag Invoke A1 (note 1) Component length 14 0E Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code InterrogateSS 0E SS-ForBS Seq 30 (note 1) SS-ForBS length 6 06 SS code tag Tag=4 04 SS code length 1 01 SS code CFNRy 2A Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code AllSpeechTransmissionServices 10 Step 16: SS -> MS RELEASE COMPLETE Contents Value/Remark Coding Length of FIE contents 26 1A Component type tag Return Result A2 (note 1) Component length 24 18 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received 03 Sequence tag 30 (note 1) Sequence length 19 13 Operation code tag 02 Operation code length 1 01 Operation code InterrogateSS 0E InterrogateSS-Res Choice Forwarding Feature List Seq. A3 (note 1) length indicator 14 0E Forwarding Feature tag Seq. 30 (note 1) Forwarding Feature length 12 0C Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code AllSpeechTransmissionServices 10 SS-Status Tag=84 84 SS-Status length 1 01 SS-Status code Prov. Registered Active 07 Forwarded To Number Identifier Tag=85 85 ISDN-AddressString length 4 04 AddressString type International Number 91 AddressString TBCD-String: 431234 34 21 43 Test 31.2.1.6.2. Interrogation rejected MMI sequence: #62# Step 4: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 13 0D Component type tag Invoke A1 (note 1) Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code InterrogateSS 0E SS-ForBS 30 (note 1) SS-ForBS length 3 03 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code CFNRc 2B Step 5: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 8 08 Component type tag Return Error A3 (note 1) Component length 6 06 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Error Code tag 02 Error Code length 1 01 Error Code SS-NotAvailable 12 MMI sequence: #6713# Step 11: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 16 10 Component type tag Invoke A1 (note 1) Component length 14 0E Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code InterrogateSS 0E SS-ForBS Seq 30 (note 1) SS-ForBS length 6 06 SS code tag Tag=04 04 SS code length 1 01 SS code CFB: CF on MS Busy 29 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code AllFacsimileServices 60 Step 12: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 8 08 Component type tag Reject A4 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Problem code tag Tag=81 81 Problem code length 1 01 Invoke problem Resource limitation 03 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.2.1.7.1.1. Notification during an incoming call Step 10 and 15: SS -> MS FACILITY Contents Value/remark Coding Length of FIE contents 18 12 Component type tag Invoke A1 (note 1) Component length 16 10 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code NotifySS 10 SS-ForBS 30 (note 1) SS-ForBS length indefinite 80 SS-Code tag Tag=81 81 SS-Code length 1 01 SS-Code CFB 29 SS-Notification tag Tag=85 85 SS-Notification length 1 01 SS-Notification Incoming call forwarded 02 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.2.1.7.1.2. Notification during an outgoing call Step 9 : SS -> MS ALERTING Contents Value/remark Coding Length of FIE contents 18 12 Component type tag Invoke A1 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary 00 Operation code tag 02 Operation code length 1 01 Operation code NotifySS 10 NotifySS-Arg tag Seq. 30 (note 1) NotifyBS-Arg length 6 06 SS code tag Tag=81 81 SS code length 1 01 SS code CFU: Forw Unconditional 21 SS-Status Tag=84 84 SS-Status length 1 01 SS-Status code Prov. Registered Active 07 End-Of-Content Tag 0 00 Length Indicator 0 00 Step 10 : SS -> MS CONNECT Contents Value/remark Coding Length of FIE contents 18 12 Component type tag Invoke A1 (note 1) Component length 16 10 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary 01 Operation code tag 02 Operation code length 1 01 Operation code NotifySS 10 NotifySS-Arg tag Seq. 30 (note 1) NotifyBS-Arg length indefinite 80 SS code tag Tag=81 81 SS code length 1 01 SS code CFC: Conditional Forw. 28 SS-Status Tag=84 84 SS-Status length 1 01 SS-Status code Prov. Registered Active 07 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.2.1.7.2. Forwarded-to mobile subscriber side Step 5 : SS -> MS SETUP Contents Value/remark Coding Length of FIE contents 18 12 Component type tag Invoke A1 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary 00 Operation code tag 02 Operation code length 1 01 Operation code NotifySS 10 NotifySS-Arg tag Seq. 30 (note 1) NotifyBS-Arg length 6 06 SS code tag Tag=81 81 SS code length 1 01 SS code CFNRc MS not reachable 2B SS-Notification tag Tag=85 85 SS-Notification length 1 01 SS-Notification Forwarded call 01 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.6.1.1. AOC time related charging/MS originated call k=1 Step 11: SS -> MS CONNECT Contents Value/remark Coding Length of FIE contents 41 29 Component type tag Invoke A1 (note 1) Component length 39 27 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code ForwardChargeAdvice 7D ForwardChargeAdviceArg Seq. 30 (note 1) ForwardChargeAdviceArg length indefinite 80 SS code tag Tag=80 80 SS code length 1 01 SS code AoC-Charging 72 Charging Information Tag=a1 A1 (note 1) Charging Information length 24 18 e1 tag Tag=81 81 e1 length 1 01 e1 Value = 6,0 3C e2 tag Tag=82 82 e2 length 2 02 e2 Value = 14,0 00 8C e3 tag Tag=83 83 e3 length 1 01 e3 Value = 1,0 64 e4 tag Tag=84 84 e4 length 2 02 e4 Value = 25,0 00 FA e5 tag Tag=85 85 e5 length 1 01 e5 Value = 0,0 00 e6 tag Tag=86 86 e6 length 1 01 e6 Value = 0,0 00 e7 tag Tag=87 87 e7 length 2 02 e7 Value = 60,0 02 58 End-Of-Content Tag 0 00 Length Indicator 0 00 Step A13/B12: MS -> SS FACILITY Contents Value/remark Coding Length of FIE contents 5 05 Component type tag Return Result A2 (note 1) Component length 3 03 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- k=1...5: e-parameters e-parameter values k-value e1 e2 e3 e4 e5 e6 e7 1 6 14 1 25 0 0 60 2 0 0 1 100 0 0 0 3 250 16 2 500 0 0 60 4 1 1 1 0 10 10 1 5 12,5 30 1 25 10 10 30 e-parameter coding k-value e1 e2 e3 e4 e5 e6 e7 1 3C 00 8C 64 00 FA 00 00 02 58 2 00 00 64 03 E8 00 00 00 3 09 C4 00 A0 00 C8 13 88 00 00 02 58 4 00 0A 00 0A 00 64 00 00 00 64 00 0A 00 0A 5 7D 01 2C 64 00 FA 64 0A 01 2C Test 31.6.1.2. AOC time related charging/MS terminated call k=1...5 Step 12: SS -> MS FACILITY e-parameters e-parameter values k-value e1 e2 e3 e4 e5 e6 e7 1 0 0 0 0 0 0 0 2 0 0 1 100 0 0 0 3 6 14 1 25 0 0 60 4 1 1 1 0 0 0 1 5 12,5 30 1 25 0 0 30 e-parameter coding k-value e1 e2 e3 e4 e5 e6 e7 1 00 00 00 00 00 00 00 2 00 00 64 03 E8 00 00 00 3 3C 00 8C 64 00 FA 00 00 02 58 4 0A 0A 64 00 00 00 0A 5 7D 01 2C 00 64 FA 00 00 01 2C Test 31.6.1.5. Change in charging information during a call Step A12: SS -> MS FACILITY (initial CAI message) Contents Value/remark Coding CAI header element e1 tag Tag=81 81 e1 length 1 01 e1 Value = 10,0 64 e2 tag Tag=82 82 e2 length 2 02 e2 Value = 28,0 01 18 e3 tag Tag=83 83 e3 length 1 01 e3 Value = 1,0 64 e4 tag Tag=84 84 e4 length 1 01 e4 Value = 10,0 64 e5 tag Tag=85 85 e5 length 1 01 e5 Value = 0,0 00 e6 tag Tag=86 86 e6 length 1 01 e6 Value = 0,0 00 e7 tag Tag=87 87 e7 length 2 02 e7 Value = 60,0 02 58 Step A12: SS -> MS FACILITY (subsequent CAI message) Contents Value/remark Coding CAI header element e1 Value = 10,0 64 e2 Value = 14,0 00 8C e3 Value = 1,0 64 e4 Value = 5,0 32 e5 Value = 0,0 00 e6 Value = 0,0 00 e7 Value = 60,0 02 58 Test 31.6.1.6. Different formats of charging information k=1 SS -> MS FACILITY Contents Value/remark Coding CAI header element e1 Value = 10,0 64 e2 Value = 40,0 01 90 e3 Value = 1,0 64 e4 Value = 0,0 00 e5 Value = 0,0 00 e6 Value = 0,0 00 e7 Value = 0,0 00 00 k=2 SS -> MS FACILITY Contents Value/remark Coding Length of FIE contents 27 1B Component type tag Invoke A1 (note 1) Component length 25 19 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code forwardChargeAdvice 7D ForwardChargeAdviceArg Seq. 30 (note 1) ForwardChargeAdviceArg length 17 11 SS code tag Tag=80 80 SS code length 1 01 SS code AoC-Charging 72 Charging Information Tag=a1 A1 (note 1) Charging Information length indefinite 80 e1 tag Tag=81 81 e1 length 1 01 e1 Value = 10,0 64 e2 tag Tag=82 82 e2 length 2 02 e2 Value = 40,0 01 90 e3 tag Tag=83 83 e3 length 1 01 e3 Value = 1,0 64 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.6.1.7. AOC on a Call Hold call Step 11: SS -> MS CONNECT Contents Value/remark Coding CAI header element e1 Value = 7,0 46 e2 Value = 40,0 01 90 e3 Value = 1,0 64 e4 Value = 0,0 00 e5 Value = 0,0 00 e6 Value = 0,0 00 e7 Value = 0,0 00 Step 20: SS -> MS CONNECT Contents Value/remark Coding CAI header element e1 Value = 13,0 00 82 e2 Value = 40,0 01 90 e3 Value = 1,0 64 e4 Value = 0,0 00 e5 Value = 0,0 00 e6 Value = 0,0 00 e7 Value = 0,0 00 Test 31.6.1.8. AOC on a Multi-party call Step 11 & 20: SS -> MS CONNECT e-parameter values k-value e1 e2 e3 e4 e5 e6 e7 1 19 40 1 0 0 0 0 2 29 40 1 0 0 0 0 e-parameter coding k-value e1 e2 e3 e4 e5 e6 e7 1 00 BE 01 90 64 00 00 00 00 2 01 22 01 90 64 00 00 00 00 Step 23: MS -> SS FACILITY Contents Value/remark Coding Length of FIE contents 8 08 Component type tag Invoke A1 (note 1) Component length 6 06 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code BuildMPTY 7C Step 24: SS -> MS FACILITY Contents Value/remark Coding Length of FIE contents 7 07 Component type tag Return Result A2 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.6.2. Charge Storage 31.6.2.1 Removal of SIM during an active call and 31.6.2.2 Interruption of power supply during an active call and 31.6.2.3 MS going out of coverage during an active AoCC call Step A11: SS -> MS CONNECT Contents Value/remark Coding Length of FIE contents 39 27 Component type tag Invoke A1 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code forwardChargeAdvice 7D ForwardChargeAdviceArg Seq. 30 (note 1) ForwardChargeAdviceArg length 27 1B SS code tag Tag=80 80 SS code length 1 01 SS code AoC-Charging 72 Charging Information Tag=a1 A1 (note 1) Charging Information length 22 16 e1 tag Tag=81 81 e1 length 1 01 e1 Value = 10,0 64 e2 tag Tag=82 82 e2 length 2 02 e2 Value = 55,0 02 26 e3 tag Tag=83 83 e3 length 1 01 e3 Value = 1,0 64 e4 tag Tag=84 84 e4 length 1 01 e4 Value = 10,0 64 e5 tag Tag=85 85 e5 length 1 01 e5 Value = 0,0 00 e6 tag Tag=86 86 e6 length 1 01 e6 Value = 0,0 00 e7 tag Tag=87 87 e7 length 1 01 e7 Value = 10,0 64 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.6.2.4. ACMmax operation/Mobile Originating k=1 Step A11: SS -> MS FACILITY Contents Value/remark Coding Length of FIE contents 41 29 Component type tag Invoke A1 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code ForwardChargeAdvice 7D ForwardChargeAdviceArg Seq. 30 (note 1) ForwardChargeAdviceArg length 27 1B SS code tag Tag=80 80 SS code length 1 01 SS code AoC-Charging 72 Charging Information Tag=a1 A1 (note 1) Charging Information length 22 16 e1 tag Tag=81 81 e1 length 1 01 e1 Value = 1,0 0A e2 tag Tag=82 82 e2 length 2 02 e2 Value = 30,0 01 2C e3 tag Tag=83 83 e3 length 1 01 e3 Value = 1,0 64 e4 tag Tag=84 84 e4 length 1 01 e4 Value = 0,0 00 e5 tag Tag=85 85 e5 length 1 01 e5 Value = 0,0 00 e6 tag Tag=86 86 e6 length 1 01 e6 Value = 0,0 00 e7 tag Tag=87 87 e7 length 1 01 e7 Value = 0,0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 k=2 Step A11: SS -> MS FACILITY Contents Value/remark Coding Length of FIE contents 40 28 Component type tag Invoke A1 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code ForwardChargeAdvice 7D ForwardChargeAdviceArg Seq. 30 (note 1) ForwardChargeAdviceArg length 26 1A SS code tag Tag=80 80 SS code length 1 01 SS code AoC-Charging 72 Charging Information Tag=a1 A1 (note 1) Charging Information length 21 15 e1 tag Tag=81 81 e1 length 1 01 e1 Value = 0,0 00 e2 tag Tag=82 82 e2 length 1 01 e2 Value = 0,0 00 e3 tag Tag=83 83 e3 length 1 01 e3 Value = 0,0 00 e4 tag Tag=84 84 e4 length 1 01 e4 Value = 0,0 00 e5 tag Tag=85 85 e5 length 1 01 e5 Value = 0,0 00 e6 tag Tag=86 86 e6 length 1 01 e6 Value = 0,0 00 e7 tag Tag=87 87 e7 length 1 01 e7 Value = 0,0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.6.2.5 ACMmax operation/Mobile Terminating k=1 Step A13: SS -> MS FACILITY, k=2 Step B13: SS -> MS FACILITY Contents Value/remark Coding Length of FIE contents 41 29 Component type tag Invoke A1 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code ForwardChargeAdvice 7D ForwardChargeAdviceArg Seq. 30 (note 1) ForwardChargeAdviceArg length 27 1B SS code tag Tag=80 80 SS code length 1 01 SS code AoC-Charging 72 Charging Information Tag=a1 A1 (note 1) Charging Information length 28 1C e1 tag Tag=81 81 e1 length 1 01 e1 Value = 1,0 00 0A e2 tag Tag=82 82 e2 length 2 02 e2 Value = 30,0 01 2C e3 tag Tag=83 83 e3 length 1 01 e3 Value = 1,0 64 e4 tag Tag=84 84 e4 length 1 01 e4 Value = 0,0 00 e5 tag Tag=85 85 e5 length 1 01 e5 Value = 0,0 00 e6 tag Tag=86 86 e6 length 1 01 e6 Value = 0,0 00 e7 tag Tag=87 87 e7 length 1 01 e7 Value = 0,0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 k=3 Step A13: SS -> MS FACILITY Contents Value/remark Coding Length of FIE contents 40 28 Component type tag Invoke A1 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code ForwardChargeAdvice 7D ForwardChargeAdviceArg Seq. 30 (note 1) ForwardChargeAdviceArg length 26 1A SS code tag Tag=80 80 SS code length 1 01 SS code AoC-Charging 72 Charging Information Tag=a1 A1 (note 1) Charging Information length 21 15 e1 tag Tag=81 81 e1 length 1 01 e1 Value = 0,0 00 e2 tag Tag=82 82 e2 length 1 01 e2 Value = 0,0 00 e3 tag Tag=83 83 e3 length 1 01 e3 Value = 0,0 00 e4 tag Tag=84 84 e4 length 1 01 e4 Value = 0,0 00 e5 tag Tag=85 85 e5 length 1 01 e5 Value = 0,0 00 e6 tag Tag=86 86 e6 length 1 01 e6 Value = 0,0 00 e7 tag Tag=87 87 e7 length 1 01 e7 Value = 0,0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.8.1.1. Registration of a password accepted MMI sequence:03330123498769876# Step 6: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 11 0B Component type tag Invoke A1 (note 1) Component length 9 09 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code RegisterPasswordSS 11 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code B: All barring services 90 Step 7: SS -> MS FACILITY Contents Value/remark Coding Length of FIE contents 14 0E Component type tag Invoke A1 (note 1) Component length 12 0C Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Linked ID tag 80 Linked ID length 1 01 Linked ID As received -- Operation Code tag 02 Operation Code length 1 01 Operation Code GetPasswordSS 12 Guidance information Enumerated 0A Guidance length 1 01 Guidance enter password 00 Step 9: MS -> SS FACILITY Contents Value/remark Coding Length of FIE contents 16 10 Component type tag Return Result A2 (note 1) Component length 14 0E Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Contents Value/remark Coding Sequence tag 30 (note 1) Sequence length 9 09 Operation Code tag 02 Operation Code length 1 01 Operation Code GetPasswordSS 12 Password tag Numeric String 12 Password length 4 04 Password Password = 1234 31 32 33 34 Step 10 & 12: FACILITY Contents Value/remark Coding Guidance Enter New Password 01 Contents Value/remark Coding Password Password = 9876 39 38 37 36 Step 13 & 15: FACILITY Contents Value/remark Coding Guidance EnterNewPasswordAgain 02 Contents Value/remark Coding Password Password = 9876 39 38 37 36 Step 16: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 20 14 Component type tag Return Result A2 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence tag 30 (note 1) Sequence length indefinite 80 Operation Code tag 02 Operation Code length 1 01 Operation Code RegisterPasswordSS 11 Password tag Numeric String 12 Password length 4 04 Password Password = 1234 31 32 33 34 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.8.1.2. Registration of a password rejected MMI sequence:0333012349876987X# Test 31.8.1.2.1. Rejection after invoke of the RegisterPassword operation Step 4: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 11 0B Component type tag Invoke A1 (note 1) Component length 9 09 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code RegisterPasswordSS 11 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code B: All barring services 90 Step 5: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 8 08 Component type tag Return Error A3 (note 1) Component length 6 06 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Error Code tag Tag=2 02 Error Code length 1 01 Error Code SS subscription violation 13 Test 31.8.1.2.2. Rejection after password check with negative result Step 6: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 10 0A Component type tag Return Error A3 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Error Code tag Tag=2 02 Error Code length 1 01 Error Code Negative Password Check 26 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.8.1.2.3. Rejection after new password mismatch Step 14: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 11 0B Component type tag Return Error A3 (note 1) Component length 9 09 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Error Code tag Tag=2 02 Error Code length 1 01 Error Code PW-Registration Failure 25 pw-Registration Failure cause Tag=04 04 (note 2) pw-Registration Failure length 1 01 pw-Registration Failure New Password Mismatch 02 NOTE 2: This element is described in Rec. 3GPP TS 04.80 subclause 4.3.2.12, but there is no ASN.1 description in subclause 4.5. Description given in the informative annex A should be put at the end of subclause 4.5. Test 31.8.3.1. Activation accepted MMI sequence: 33123422# Step 6: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 16 10 Component type tag Invoke A1 (note 1) Component length 14 0E Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary (01) -- Operation code tag 02 Operation code length 1 01 Operation code ActivateSS 0C SS-ForBS Seq. 30 (note 1) SS-ForBS length 6 06 SS code tag Tag=04 04 SS code length 1 01 SS code BAOC 92 Basic Service Code identifier BearerserviceCode 82 BearerService length 1 01 BearerService code AllSynchronousServices 68 Step 7: SS -> MS FACILITY Contents Value/remark Coding Length of FIE contents 14 0E Component type tag Invoke A1 (note 1) Component length 12 0C Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary (02) -- Linked ID tag 80 Linked ID length 1 01 Linked ID As received (01) -- Operation code tag 02 Operation code length 1 01 Operation code Getpassword 12 Guidance tag Enumerated 0a Guidance length 1 01 Guidance Enter Password 00 Step 8: MS -> SS FACILITY Contents Value/remark Coding Length of FIE contents 16 10 Component type tag Return Result A2 (note 1) Component length 14 0E Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received (02) -- Sequence tag 30 (note 1) Sequence length 9 09 Operation code tag 02 Operation code length 1 01 Operation code Getpassword 12 Password tag NumericString 12 Password length 4 04 Password Password = 1234 31 32 33 34 Step 9: SS -> MS RELEASE COMPLETE This message is coded to give a complete answer to the MS request. Shorter message can also be used (see last paragraph). Contents Value/remark Coding Length of FIE contents 29 1D Component type tag Return Result A2 (note 1) Component length 27 1B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received (01) -- Sequence tag 30 (note 1) Sequence length indefinite 80 Operation code tag 02 Operation code length 1 01 Operation code ActivateSS 0C SS information CallBarringInfo Tag=a1 A1 (note 1) CallBarringInfo length indefinite 80 SS code tag Tag=04 04 SS code length 1 01 SS code BAOC 92 CallBarringFeature List Seq. 30 (note 1) Length indicator 8 08 CallBarring Feature tag Seq. 30 (note 1) CallBarring Feature length 6 06 Basic Service Code identifier BearerserviceCode 82 BearerService length 1 01 BearerService code AllSynchronousServices 68 SS-Status Tag=84 84 SS-Status length 1 01 SS-Status code Prov. Registered Active 07 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 MMI sequence: 3511234# Step 17: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 13 0D Component type tag Invoke A1 (note 1) Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code ActivateSS 0C SS-ForBS Seq 30 (note 1) SS-ForBS length 3 03 SS code tag Tag=04 04 SS code length 1 01 SS code BICRoam 9B Step 20: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 26 1A Component type tag Return Result A2 (note 1) Component length 24 18 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence identifier 30 (note 1) Sequence length 19 13 Operation code tag 02 Operation code length 1 01 Operation code ActivateSS 0C SS-Information CallBarringInfo Tag=a1 A1 (note 1) CallBarringInfo length 14 0E SS code tag Tag=04 04 SS code length 1 01 SS code BICRoam 9B CallBarringFeature List Seq. 30 (note 1) Length indicator indefinite 80 CallBarring Feature tag Seq. 30 (note 1) CallBarring Feature length indefinite 80 SS-Status Tag=84 84 SS-Status length 1 01 SS-Status code Prov. Registered Active 07 End-Of-Content Tag 0 00 Length Indicator 0 00 End-Of-Content Tag 0 00 Length Indicator 0 00 Step 9 & 20: short messages Step 10 and 22 messages can be coded using this shorter form: Message containing only the "Return result" Contents Value/remark Coding Length of FIE contents 5 05 Component type tag Return Result A2 (note 1) Component length 3 03 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Message containing the "Return result" and the "Operation Code" Contents Value/remark Coding Length of FIE contents 12 0C Component type tag Return Result A2 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence identifier 30 (note 1) Sequence length 3 03 Operation code tag 02 Operation code length 1 01 Operation code ActivateSS 0C End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.8.3.2.1. Rejection after invoke of ActivateSS operation MMI sequence: 3311234# Step 4: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 13 0D Component type tag Invoke A1 (note 1) Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code ActivateSS 0C SS-ForBS Seq 30 (note 1) SS-ForBS length 3 03 SS code tag Tag=04 04 SS code length 1 01 SS code BOIC 93 Step 5: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 8 08 Component type tag Return Error A3 (note 1) Component length 6 06 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Error code tag 02 Error code length 1 01 Error code SS Subscription Violation 13 Test 31.8.3.2.2. Rejection after use of password procedure MMI sequence: 351234# Step 4: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 13 0D Component type tag Invoke A1 (note 1) Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code ActivateSS 0C SS-ForBS Seq 30 (note 1) SS-ForBS length 3 03 SS code tag Tag=04 04 SS code length 1 01 SS code BAIC 9A Step 7: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 10 0A Component type tag Return Error A3 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Error code tag 02 Error code length 1 01 Error code NegativePasswordCheck 26 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.8.4.1. Deactivation accepted MMI sequence: #330123411# Step 6: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 16 10 Component type tag Invoke A1 (note 1) Component length 14 0D Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code DeactivateSS 0D SS-ForBS Seq 30 (note 1) SS-ForBS length 3 03 SS code tag Tag=04 04 SS code length 1 01 SS code B: All barring services 90 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code AllSpeechTransmission 10 Step 10: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 21 15 Component type tag Return Result A2 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence identifier 30 (note 1) Sequence length 12 0C Operation code tag 02 Operation code length 1 01 Operation code DeactivateSS 0D SS-Information CallBarringInfo Tag=a1 A1 (note 1) CallBarringInfo length 7 07 CallBarringFeature List Seq. 30 (note 1) Length indicator 5 05 CallBarring Feature tag Seq. 30 (note 1) CallBarring Feature length 3 03 Basic Service Code Identifier TeleserviceCode 83 Teleservice Length 1 01 Teleservice code AllSpeechTransmission 10 End-Of-Content Tag 0 00 Length Indicator 0 00 MMI sequence: #333123413# Step 17: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 16 10 Component type tag Invoke A1 (note 1) Component length 14 0E Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code DeactivateSS 0D SS-ForBS Seq 30 (note 1) SS-ForBS length 6 06 SS code tag Tag=04 04 SS code length 1 01 SS code BO 91 Basic Service Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code AllFacsimileServices 60 Step 21: MS -> SS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 21 15 Component type tag Return Result A2 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence identifier 30 (note 1) Sequence length 12 0C Operation code tag 02 Operation code length 1 01 Operation code DeactivateSS 0D SS-Information CallBarringInfo Tag=a1 A1 (note 1) CallBarringInfo length 7 07 CallBarringFeature List Seq. 30 (note 1) Length indicator 5 05 CallBarring Feature tag Seq. 30 (note 1) CallBarring Feature length 3 03 Basic Service Code Identifier TeleserviceCode 83 Teleservice Length 1 01 Teleservice code AllFacsimileServices 60 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.8.4.2.1. Deactivation rejected after invoke operation MMI sequence: #3531234# Step 4: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 13 0D Component type tag Invoke A1 (note 1) Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code DeactivateSS 0D SS-ForBS Seq 30 (note 1) SS-ForBS length 3 03 SS code tag Tag=04 04 SS code length 1 01 SS code BI 99 Step 5: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 10 0A Component type tag Return Error A3 (note 1) Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Error code tag 02 Error code length 1 01 Error code SS Subscription Violation 13 End-Of-Content Tag 0 00 Length Indicator 0 00 Test 31.8.4.2.2. Deactivation rejection after password operation MMI sequence: #3321234# Step 4: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 13 0D Component type tag Invoke A1 (note 1) Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code DeactivateSS 0D SS-ForBS Seq 30 (note 1) SS-ForBS length 3 03 SS code tag Tag=04 04 SS code length 1 01 SS code BOICExHome 94 Step 7: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 8 08 Component type tag Return Error A3 (note 1) Component length 6 06 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Error code tag 02 Error code length 1 01 Error code NegativePasswordCheck 26 Test 31.8.6.1. Interrogation accepted MMI sequence: #35# Step 6: MS -> SS REGISTER Contents Value/remark Coding Length of FIE contents 13 0D Component type tag Invoke A1 (note 1) Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code InterrogateSS 0E SS-ForBS Seq 30 (note 1) SS-ForBS length 3 03 SS code tag Tag=04 04 SS code length 1 01 SS code BAIC 9A Step 10: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE Contents 15 0F Component type tag Return Result A2 Component length 13 0D Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence tag 30 Sequence length 8 08 Operation Code tag 02 Operation Code length 1 01 Operation Code InterrogateSS 0E InterrogateSS-Res Choice BasicServiceGroupList tag Seq. A2 BasicServiceGroupList length 3 03 BasicService Code identifier TeleserviceCode 83 Teleservice length 1 01 Teleservice code Telephony 11 MMI sequence: #332# Step 17: MS -> SS REGISTER Contents Value/remark Coding Length of FIE Contents 13 0D Component type tag Invoke A1 Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code InterrogateSS 0E SS-ForBS Seq 30 SS-ForBS length 3 03 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code BOICExHome 94 Step 21: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE Contents 13 0D Component type tag Return Result A2 Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Sequence tag 30 Sequence length 6 06 Operation Code tag 02 Operation Code length 1 01 Operation Code InterrogateSS 0E InterrogateSS-Res Choice SS-Status Tag=80 80 SS-Status length 1 01 SS-Status Prov., Registered, Deactive 06 Test 31.8.6.2. Interrogation rejected MMI sequence: #351# Step 4: MS -> SS REGISTER Contents Value/remark Coding Length of FIE Contents 13 0D Component type tag Invoke A1 Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code InterrogateSS 0E SS-ForBS Seq 30 SS-ForBS length 3 03 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code BICRoam 9B Step 5: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE Contents 10 0A Component type tag Return Error A3 Component length indefinite 80 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Error code tag 02 Error code length 1 01 Error code SS_NotAvailable 12 End-Of-Content Tag 0 00 Length Indicator 0 00 MMI sequence: #331# Step 11: MS -> SS REGISTER Contents Value/remark Coding Length of FIE Contents 13 0D Component type tag Invoke A1 Component length 11 0B Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code InterrogateSS 0E SS-ForBS Seq 30 SS-ForBS length 3 03 SS-Code tag Tag=4 04 SS-Code length 1 01 SS-Code BOIC 93 Step 12: SS -> MS RELEASE COMPLETE Contents Value/remark Coding Length of FIE Contents 8 08 Component type tag Reject A4 Component length 6 06 Invoke ID tag 02 Invoke ID length 1 01 Invoke ID As received -- Problem code tag Tag=81 81 Problem code length 1 01 Invoke problem code Resource limitation 03 Test 31.8.7. Normal operation Incoming call Step 6: MS -> SS RELEASE COMPLETE Contents Value/remark Coding Length of FIE contents 16 10 Component type tag Invoke A1 (note 1) Component length 14 0E Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation code tag 02 Operation code length 1 01 Operation code NotifySS 10 NotifySS-Arg tag Seq. 30 (note 1) NotifySS-Arg length 6 06 SS code tag Tag=81 81 SS code length 1 01 SS code BI 99 SS-Status Tag=84 84 SS-Status length 1 01 SS-Status code Prov. Registered Active 07 Test 31.9. Registration accepted of a USSD MMI sequence: 00# Contents Value/remark Coding Length of FIE contents 15 0F Component type tag Invoke A1 (note 1) Component length 13 0D Invoke ID tag 02 Invoke ID length 1 01 Invoke ID Arbitrary -- Operation Code tag 02 Operation Code length 1 01 Operation Code ProcessUSSDSS 0A IA5 String tag Tag=16 16 IA5 String length 5 05 Content 00# 2A 2A 30 30 23 31.12 eMLPP Service This subclause is applicable to the mobile stations supporting eMLPP service. The eMLPP is applicable to teleservices 1x, 6x, 9x and bearer services 2x, 3x, 4x, 5x. For an MS supporting speech the test procedures in subclauses 31.12.1 and 31.12.2 are performed for full rate speech (teleservice 11, telephony). For an MS not supporting speech but supporting at least one of telecommunication services (TS6x, BS2x, BS3x, BS4x, BS5x), for each of the test procedures 31.12.1 and 31.12.2 a full rate service supported by the MS (see PICS/PIXIT statement) is chosen, and the test is performed corresponding to that service. 31.12.1 eMLPP Service / priority level of MO call
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.12.1.1 Conformance requirement	For the MS supporting MO calls: 1. Mobile stations indicate the priority of their call in the signalling that takes place during the call establishment process. 2. The MS shall verify the selected priority level against the priority levels stored in the SIM. If the selected priority is not allowed, then the priority of the call shall be modified to that of the nearest allowed priority level below the requested level. 3. In case of no priority selection or use of a non-compatible Mobile Station the Mobile Station shall send a standard service request message. 4. Signalling information required for the prioritisation at mobile originating call establishment. (see figure 1 of 3GPP TS 04.67 subclause 4.1.1) and Signalling information between the network and the calling mobile station required for the prioritisation in case of a VGCS or VBS call (figure 4 of 3GPP TS 04.67 subclause 4.1.4). 5. The user or the network may wish to omit or postpone authentication and ciphering in order to provide for a faster call set-up. Reference(s) 3GPP TS 03.67 subclauses 11.3.1.1, 11.3.1.2, 11.6 and 11.3.1.3. 3GPP TS 02.67 clause 4. 3GPP TS 04.67 subclauses 4.1.1 and 4.1.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.12.1.2 Test purpose	For the MS supporting MO, to verify that: 1. When user selects priority level for normal MO call, the priority level is indicated in the signalling message. 2. The MS verifies the selected priority level against the priority levels stored in the SIM. If the selected priority is not allowed, then the priority of the call shall be modified to that of the nearest allowed priority level below the requested level. 3. If the user does not select a priority level, the priority level is not indicated in the signalling message. 4. If a priority selection is performed by the user the MS provides the priority level information element in L3-MM CM SERVICE REQUEST message when a group call is initiated. 5. The mobile is able to establish a normal MO call with a priority level or a group call with a priority level according to the procedure specified in 3GPP TS 04.67 subclause 4.1.1 and the procedure in 3GPP TS 04.67 subclause 4.1.4. 6. The mobile is able to initiate a fast call set-up without authentication and ciphering.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.12.1.3 Method of test	Initial Conditions System Simulator: 1 cell with default parameters. Mobile Station: The MS is in idle mode with SIM in which the available priority levels are level 2, level 3, and level 4 Specific PICS Statements - Support mobile originating call (TSPC_AddInfo_MOsvc) - Support mobile emergency call (TSPC_Serv_TS12) - Support VGCS originating (TSPC_AddInfo_VGCS_Originating) - Support VBS originating (TSPC_AddInfo_VBS_Originating) PIXIT Statements - Way to select a priority level. Foreseen Final State of the MS "Idle, updated". Test Procedure The test steps 1 to 26 are repeated for k=1, 2, 3. After the repetition is finished the steps 27 to 71 are performed. The test steps 1 to 7 are performed if the mobile station supports normal MO call. The steps 8 to 13 are executed if the MS supports TS12. The test steps 20 to step 26 are executed for k= 1, 2, 3, if the mobile station supports VGCS/VBS originating. An allowed priority level (level 3) or a priority level (level 1) higher than allowed level or no priority level is selected by MMI action (for k=1, 2, 3 respectively). An MO call is attempted. It is checked that the MS indicates the selected priority level (for k=1) or the nearest allowed priority level below the selected level (for k=2) or no priority level (for k=3) in the signalling message. A normal MO call is attempted with an allowed priority level (level 3). It is checked that the MS establishes completely this call. If the mobile station supports VGCS/VBS originating a VGCS/VBS call is initiated via the MMI by using the SETUP procedure. A MO VGCS/VBS call is attempted with the allowed priority level 0. It is checked that the MS establishes completely this call using the immediate setup procedure without authentication and ciphering. Maximum Duration of Test 5 minutes. Expected Sequence Step Direction Message Comments 1 MS for k=1, MMI action to select a priority level 3 for k=2, MMI action to select a priority level 0 for k=3, no MMI action to select priority level 2 MS to initiate a normal MO call 3 MS -> SS CHANNEL REQUEST 4 SS -> MS IMMEDIATE ASSIGNMENT 5 MS -> SS CM SERVICE REQUEST for k=1, containing priority IE with the selected priority for k=2, containing priority IE with a priority level nearest allowed priority level below the requested one (level 2) for k=3, containing no priority IE 6 SS -> MS CM SERVICE REJECT 7 SS -> MS CHANNEL RELEASE 8 MS to initiate a normal MO emergency call 9 MS -> SS CHANNEL REQUEST 10 SS -> MS IMMEDIATE ASSIGNMENT 11 MS -> SS CM SERVICE REQUEST for k=1, containing priority IE with the selected priority for k=2, containing priority IE with a priority level nearest allowed priority level below the requested one (level 2) for k=3, containing no priority IE 12 SS -> MS CM SERVICE REJECT 13 SS -> MS CHANNEL RELEASE 20 MS for k=1, MMI action to select a priority level 3 for k=2, MMI action to select a priority level 0 for k=3, no MMI action to select priority level 21 MS to initiate a VGCS call by setup procedure, if supporting VGCS originating. to initiate a VBS call by setup procedure, if supporting only VBS originating. 22 MS -> SS CHANNEL REQUEST 23 SS -> MS IMMEDIATE ASSIGNMENT 24 MS -> SS CM SERVICE REQUEST for k=1, containing priority IE with the selected priority for k=2, containing priority IE with a priority level nearest allowed priority level below the requested one (level 2) for k=3, containing no priority IE 25 SS -> MS CM SERVICE REJECT 26 SS -> MS CHANNEL RELEASE 27 MS MMI action to select a priority level 3 28 MS initiate a normal MO call 29 MS -> SS CHANNEL REQUEST 30 SS -> MS IMMEDIATE ASSIGNMENT 31 MS -> SS CM SERVICE REQUEST containing priority IE with a priority level nearest allowed priority level below the requested one (level 3) 32 SS -> MS AUTHENTICATION REQUEST 33 MS -> SS AUTHENTICATION RESPONSE 34 SS -> MS CIPHERING MODE COMMAND no ciphering 35 MS -> SS CIPHERING MODE COMPLETE 36 MS -> SS SETUP 37 SS -> MS CALL PROCEEDING 38 SS -> MS ASSIGNMENT COMMAND 39 MS -> SS ASSIGNMENT COMPLETE 40 SS -> MS ALERTING 41 SS -> MS CONNECT 42 MS -> MS CONNECT ACKNOWLEDGE 43 SS -> MS DISCONNECT 44 MS -> SS RELEASE 45 SS -> MS RELEASE COMPLETE 46 SS -> MS CHANNEL RELEASE Steps 47 – 71 are performed if the MS supports VGCS/VBS originating 47 MS MMI action to select a priority level 3 and initiate a VGCS/VBS call by setup procedure 49 MS -> SS CHANNEL REQUEST 50 SS -> MS IMMEDIATE ASSIGNMENT 51 MS -> SS CM SERVICE REQUEST containing priority IE with a priority level nearest allowed priority level below the requested one (level 3) 52 SS -> MS AUTHENTICATION REQUEST 53 MS -> SS AUTHENTICATION RESPONSE 54 SS -> MS CIPHERING MODE COMMAND no ciphering 55 MS -> SS CIPHERING MODE COMPLETE 56 MS -> SS SETUP 57 SS -> MS CHANNEL MODE MODIFY 58 MS -> SS CHANNEL MODE MODIFY ACKNOWLEDGE 59 SS -> MS CONNECT 60 SS Verify that TCH is through connected 61 SS -> MS TERMINATION 62 SS -> MS CHANNEL RELEASE 63 MS MMI action to select a priority level 0, MMI action to initiate VGCS/VBS call. 64 MS -> SS CHANNEL REQUEST 65 SS -> MS IMMEDIATE ASSIGNMENT TCH/F, single RF channel GSM 450: 275 GSM 480: 322 GSM 900: 50 DCS 1800: 750 PCS 1 900: 650 GSM 710, GSM 750, T-GSM 810: 470 GSM 850: 177 66 MS -> SS IMMEDIATE SETUP L2: SABM / UA 67 SS -> MS CHANNEL MODE MODIFY very early assignment 68 MS -> SS CHANNEL MODE MODIFY ACKNOWLEDGE 69 SS -> MS CONNECT verify that the TCH is through connected 70 SS Verify that TCH is through connected 70 SS -> MS TERMINATION 71 SS -> MS CHANNEL RELEASE Special Message Contents CM SERVICE REQUEST in step 5 and step 24 for k=1, 2 Information Element value/remark as default except: CM Service Type not checked Ciphering key sequence number not checked Mobile station classmark not checked Priority Information element identifier 0001 Spare 0 Call priority 010 for k=1 011 for k=2 for k=3 Information Element value/remark as default except: CM Service Type not checked Ciphering key sequence number not checked Mobile station classmark not checked Priority not present CM SERVICE REQUEST in step 11 for k=1, 2 Information Element value/remark as default except: CM Service Type "emergency call establishment" Ciphering key sequence number not checked Mobile station classmark not checked Priority Information element identifier 0001 Spare 0 Call priority 010 for k=1 for k=3 Information Element value/remark as default except: CM Service Type "emergency call establishment" Ciphering key sequence number not checked Mobile station classmark not checked Priority not present 31.12.2 eMLPP Service / automatic answering point-to-point MT call 31.12.2.1 Conformance requirement For the MS supporting MT call: 1. Automatic answering or, if necessary, called-party pre-emption has to be performed by the Mobile Station as defined in the following: - point-to-point calls: If the user is in idle mode, the Mobile Station shall automatically connect to an incoming call of a sufficient priority level. If the user is in dedicated mode and has a subscription to Call Waiting, a Call Waiting indication including the priority level of the call shall be given to the Mobile Station which automatically accepts the waiting call. 2. In dedicated mode, in the case where the called subscriber has a subscription for eMLPP and for Call Waiting and is using a compatible Mobile Station, the Mobile Station shall be informed of the priority of the new call together with the call waiting indication. The Mobile Station will then consult the internal service configuration list stored on the SIM to establish whether it should automatically accept the waiting call without consulting the user, or whether the call waiting facility will be used as normal. 3. In the case where the called subscriber has a subscription for eMLPP and for CW, the mobile station shall be informed of the priority of the new call together with the CW indication. On reception of the set-up message the compatible mobile station decides on called party pre-emption. If called party pre-emption applies, the mobile station shall automatically accept the waiting call and send a hold message to the network. If a hold acknowledge is received, the waiting call is accepted. If a hold reject is received for any reason, e.g. there is no subscription for hold, the other call shall be released and the waiting call accepted. If the ongoing call is not a TS11 call, the mobile station should not send a hold message to the network but release the call and accept the waiting call. Reference(s) 3GPP TS 02.67 subclause 4, 5.9. 3GPP TS 03.67 clause 4, subclauses 11.3.2.4, 11.3.2.5 and 11.6. 3GPP TS 04.67 subclause 4.1.3. 3GPP TS 04.83 subclauses 1.1 and 1.2.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.12.2.2 Test purpose	For the MS supporting MT call, to verify that: 1. In idle mode the MS automatically accepts an incoming point-to-point call of priority level for which automatic answering is enabled. 2. In idle mode the MS alerts an incoming point-to-point call of a priority level for which automatic answering is disabled. 3. In dedicated mode and supporting Call Waiting, when a Call Waiting indication includes a level for which automatic answering is enabled and the priority level is higher than the ongoing point-to-point call, the MS automatically confirms the waiting call and sends a hold message to the network. If a hold reject is received the other call is released and the waiting call is accepted. 4. In dedicated mode and supporting Call Waiting, when a Call Waiting indication includes a priority level for which automatic answering is enabled and the priority level is equal or lower than the priority level of the ongoing call, the MS indicates the waiting call. 5. In group receive mode the MS automatically responds to the paging message containing a priority level for which automatic answering is enabled and the priority level is higher than the priority level of the ongoing call. 6. In group receive mode the MS indicates an incoming point-to-point call of a priority level for which automatic answering is enabled and the priority level is equal or lower than the priority level of the ongoing call.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.12.2.3 Method of test	Initial Conditions System Simulator: 1 cell with default parameters. Mobile Station: The MS is in idle mode. The auto answering priority level is set to higher than priority level 2. Specific PICS Statements - Support VGCS listening (TSPC_AddInfo_VGCS_Listening) - Support VBS listening (TSPC_AddInfo_VBS_Listening) PIXIT Statements - Way to configure automatic answering. - Way to indicate a call has been automatically answered. Foreseen Final State of the MS "Idle, updated". Test Procedure The call waiting is activated. The MS is in idle mode and automatic answering for priority level 2 is disabled. A PAGING REQUEST message containing priority level 2 is sent. It is checked that the MS indicates the incoming call to the user. The automatic answering for level 1 is enabled. A PAGING REQUEST message with priority level 2 is sent. It is checked that the MS automatically accepts the incoming normal call. The call is released. A PAGING REQUEST message without priority level is sent, and during the call set-up the SETUP message contains priority level 1. It is checked that the MS automatically accepts the incoming normal call. The MS is in dedicated mode (If the MS supports TS11, TS11service shall be selected for the dedicated mode testing). a SETUP message with priority level higher enough for auto answering is sent by the SS. It is checked that the MS automatically accepts the incoming normal call. A SETUP message containing low priority level without auto answering is sent. It is checked that the MS indicates the incoming call to the user. The MS is in group receive mode, a NOTIFICATION/FACCH message containing paging information and a PAGING REQUEST message with priority level 0 are sent. It is checked that the MS automatically accepts the incoming normal call. The MS is brought into group receive mode. A NOTIFICATION/FACCH message containing paging information and a PAGING REQUEST message containing low priority level are sent. It is checked that the MS indicates the incoming call to the user. Maximum Duration of Test 5 minutes. Expected Sequence Step Direction Message Comments 0 MS the MS is in idle mode and auto answering for priority level 2 is disabled 1 SS -> MS PAGING REQUEST TYPE 1 with priority level 2 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT SDCCH 4 MS -> SS PAGING RESPONSE 5 SS -> MS SETUP containing priority level 2, but no signal IE 6 MS -> SS CALL CONFIRMED 7 SS -> MS ASSIGNMENT COMMAND TCH 8 MS -> SS ASSIGNMENT COMPLETE 9 MS -> SS ALERTING 10 MS An alerting indication as defined in a PICS/PIXIT statement is given by the MS 11 MS The MS is made to accept the call in the way described in a PICS/PIXIT statement 12 MS -> SS CONNECT 13 SS -> MS CONNECT ACKNOWLEDGE 14 SS -> MS DISCONNECT 15 MS -> SS RELEASE 16 SS -> MS RELEASE COMPLETE 17 SS -> MS CHANNEL RELEASE return to idle mode 21 SS -> MS PAGING REQUEST TYPE 1 containing priority level 1 22 MS -> SS CHANNEL REQUEST 23 SS -> MS IMMEDIATE ASSIGNMENT SDCCH 24 MS -> SS PAGING RESPONSE 25 SS -> MS SETUP containing priority level 1, but no signal IE 26 MS -> SS CALL CONFIRMED 27 MS -> SS CONNECT automatic connection 28 SS -> MS ASSIGNMENT COMMAND TCH 29 MS -> SS ASSIGNMENT COMPLETE 30 SS -> MS CONNECT ACKNOWLEDGE 31 MS to check that the MS gives an indication as defined in a PICS/PIXIT statement for call automatically answered 32 SS -> MS DISCONNECT 33 MS -> SS RELEASE 34 SS -> MS RELEASE COMPLETE 35 SS -> MS CHANNEL RELEASE return to idle mode 36 SS -> MS PAGING REQUEST TYPE 1 containing no priority level 37 MS -> SS CHANNEL REQUEST 38 SS -> MS IMMEDIATE ASSIGNMENT SDCCH 39 MS -> SS PAGING RESPONSE 40 SS -> MS SETUP containing priority level 3, but no signal IE 41 MS -> SS CALL CONFIRMED 42 MS -> SS CONNECT automatic connection 43 SS -> MS ASSIGNMENT COMMAND TCH 44 MS -> SS ASSIGNMENT COMPLETE 45 SS -> MS CONNECT ACKNOWLEDGE 51 SS -> MS SETUP new transaction, containing priority level 1 and Signal Information Element with value #7 52 MS -> SS CALL CONFIRMED on new transaction with cause #17 53a MS -> SS HOLD on old transaction for service TS11 53b no signalling for services other than TS11 54a SS -> MS HOLD REJECT on old transaction for service TS11 with cause #69 54b no signalling for services other than TS11 55 MS -> SS DISCONNECT on old transaction, cause = ‘Normal call clearing’ 56 SS -> MS RELEASE on old transaction 57 MS -> SS RELEASE COMPLETE on old transaction 58 MS -> SS CONNECT on new transaction 59 SS -> MS CONNECT ACKNOWLEDGE on new transaction 60 SS -> MS SETUP another new transaction different from step 51, containing priority level 1 and Signal Information Element with value #7 61 MS -> SS CALL CONFIRMED on the same transaction as step 60, with cause #17 62 MS -> SS ALERTING on the same transaction as step 60 63 MS to check that the MS gives incoming call indication 64 SS -> MS DISCONNECT on the same transaction as step 51 65 MS -> SS RELEASE on the same transaction as step 51 66 SS -> MS RELEASE COMPLETE on the same transaction as step 51 67 SS -> MS CHANNEL RELEASE 70 MS the MS is in group receive mode, the priority level of current call is level 3 72 SS -> MS PAGING REQUEST TYPE 1 containing priority level 0 73 MS -> SS CHANNEL REQUEST 74 SS -> MS IMMEDIATE ASSIGNMENT SDCCH 75 MS -> SS PAGING RESPONSE 76 SS -> MS SETUP without priority level and signal IE 77 MS -> SS CALL CONFIRMED 78 MS -> SS CONNECT automatic connection 79 SS -> MS ASSIGNMENT COMMAND TCH 80 MS -> SS ASSIGNMENT COMPLETE 81 SS -> MS CONNECT ACKNOWLEDGE 82 SS -> MS DISCONNECT 83 MS -> SS RELEASE 84 SS -> MS RELEASE COMPLETE 85 SS -> MS CHANNEL RELEASE 86 MS the MS is brought into group receive mode with the priority level 3 88 SS -> MS PAGING REQUEST TYPE 1 containing priority level 3 89 MS to check that the MS gives incoming call indication 90 SS -> MS CHANNEL RELEASE UI format 31.12.3 eMLPP Service / automatic answering MT VGCS or VBS call 31.12.3.1 Conformance requirement For the MS supporting VGCS/VBS listening: 1. Automatic answering or, if necessary, called-party pre-emption has to be performed by the Mobile Station as defined in the following: - voice group calls and voice broadcast calls: Notifications for other voice group calls, voice broadcast calls or information on paging for point-to-point calls shall be given to the Mobile Stations involved in on-going voice group calls or voice broadcast calls as defined in 3GPP TS 03.68 and 3GPP TS 03.69, respectively. The notifications include the related priority level of the call. In case of a notified call with higher priority where called-party pre-emption applies, the Mobile Station shall automatically leave the on-going voice group call or voice broadcast call and react according to the type of the notified call type. 2. In dedicated mode, in the case where the called subscriber has a subscription for eMLPP and for Call Waiting and is using a compatible Mobile Station, the Mobile Station shall be informed of the priority of the new call together with the call waiting indication. The Mobile Station will then consult the internal service configuration list stored on the SIM to establish whether it should automatically accept the waiting call without consulting the user, or whether the call waiting facility will be used as normal. 3. In the case where the called subscriber has a subscription for eMLPP and for CW, the mobile station shall be informed of the priority of the new call together with the CW indication. On reception of the notification message the compatible mobile station decides on called party pre-emption. If called party pre-emption applies, the mobile station shall automatically release the call and join the new call. Reference(s) 3GPP TS 02.67 clause 4. 3GPP TS 03.68 clause 4, subclauses 11.3.1.3 and 11.3.1.4. 3GPP TS 03.67 clause 4. 3GPP TS 04.67 subclause 4.1.5.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.12.3.2 Test purpose	For the MS supporting VGCS/VBS listening, to verify that: 1. In idle mode the MS automatically accepts an incoming VGCS or VBS call of sufficient priority level. 2. In idle mode the MS indicates an incoming VGCS or VBS call of priority level not high enough for automatic answering. 3. In dedicated mode, the MS automatically accepts an incoming VGCS or VBS call of sufficient priority level. 4. In dedicated mode, the MS indicates an incoming VGCS or VBS call of priority level not high enough for automatic answering. 5. In group receive mode the MS automatically accepts an incoming VGCS or VBS call of sufficient priority level. 6. In group receive mode the MS indicates an incoming VGCS or VBS call of priority level not high enough for automatic answering.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.12.3.3 Method of test	Initial Conditions System Simulator: 1 cell with default parameters. Mobile Station: The MS is in idle mode. The auto answering priority level is set to higher than priority level 2. Specific PICS Statements - PIXIT Statements - Way to configure automatic answering. - Way to indicate that a VGCS/VBS call has been automatically accepted. Foreseen Final State of the MS "Idle, updated". Test Procedure The MS is in idle mode. a NOTIFICATION/NCH message with priority level higher enough for auto answering is sent. It is checked that the MS automatically accepts the incoming VGCS/VBS call. The call is released. A NOTIFICATION/NCH message containing low priority level without auto answering is sent. It is checked that the MS indicates the incoming VGCS/VBS call to the user. The MS is in dedicated mode. a NOTIFICATION/FACCH message with priority level higher enough for auto answering is sent. It is checked that the MS automatically accepts the incoming VGCS/VBS call. A NOTIFICATION/FACCH message containing low priority level without auto answering is sent. It is checked that the MS indicates the incoming VGCS/VBS call to the user. The MS is in group receive mode. a NOTIFICATION/FACCH message with priority level higher enough for auto answering and containing VGCS/VBS channel description is sent. It is checked that the MS automatically accepts the incoming VGCS/VBS call. A NOTIFICATION/FACCH message containing priority level not higher enough for auto answering and containing VGCS/VBS channel description is sent. It is checked that the MS indicates the incoming VGCS/VBS call to the user. Maximum Duration of Test 5 minutes. Expected Sequence Step Direction Message Comments 1 MS the MS is in idle mode 2 SS -> MS NOTIFICATION/NCH containing priority level 1 3 MS to check that the MS automatically accepts the VGCS/VBS call 4 SS stop sending NOTIFICATION/NCH 5 SS -> MS CHANNEL RELEASE UI format, release VGCS/VBS channel 6 SS -> MS NOTIFICATION/NCH containing priority level 3 7 MS to check that the MS indicates the VGCS/VBS call to the user 8 SS stop sending NOTIFICATION/NCH 15 MS the MS is in dedicated mode, the priority level of current call is level 3 16 SS -> MS NOTIFICATION/FACCH containing priority level 2 17 MS -> SS DISCONNECT 18 SS -> MS RELEASE 19 MS -> SS RELEASE COMPLETE 20 SS -> MS CHANNEL RELEASE 21 MS to check that the MS automatically accepts the VGCS/VBS call 22 SS -> MS CHANNEL RELEASE UI format, release VGCS/VBS channel 23 MS the MS is brought into dedicated mode, the priority level of current call is level 3 24 SS -> MS NOTIFICATION/FACCH containing priority level 4 25 MS to check that the MS indicates the VGCS/VBS call to the user 26 SS stop sending NOTIFICATION/FACCH 27 SS -> MS DISCONNECT 28 MS -> SS RELEASE 29 SS -> MS RELEASE COMPLETE 30 SS -> MS CHANNEL RELEASE I format, release dedicated channel 31 MS the MS is in group receive mode, the priority level of current call is level 3 32 SS -> MS NOTIFICATION/FACCH containing priority level 1 and with VGCS/VBS channel description 33 MS to check the MS automatically accepts the incoming VGCS/VBS call 34 SS -> MS NOTIFICATION/FACCH containing priority level 4 and with VGCS/VBS channel description 35 MS to check the MS indicates the incoming VGCS/VBS call to the user 36 SS -> MS CHANNEL RELEASE UI format, release VGCS/VBS channel 31.12.4 eMLPP Service / registration
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.12.4.1 Conformance requirement	For registration of eMLPP default priority level, 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. An eMLPP registration request from a mobile user shall include the SS-Code of the eMLPP service and the default priority level. Reference(s) 3GPP TS 04.67 subclause 4.2 (figure 6). 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.2 and 9.1.8. 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1 and 9.2.9.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.12.4.2 Test purpose	To check that the MS: 1. Correctly requests a supplementary service transaction for registration of eMLPP in CHANNEL REQUEST message. 2. Correctly requests a supplementary service transaction for registration of eMLPP in the subsequent CM SERVICE REQUEST. 3. Then sends a REGISTER message containing the invoke of the RegisterSS operation with the expected parameter values for registration of eMLPP default priority level. 4. Provides the appropriate user indication (as described by the manufacturer) upon receipt of the result of the operation (in a RELEASE COMPLETE message).
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.12.4.3 Method of test	Initial Conditions System Simulator: 1 cell with default parameters. Mobile Station: the MS is in idle mode Specific PICS Statements - PIXIT Statements - Way to select a priority level. - Way to initiate eMLPP registration. - Way to indicate the result of the eMLPP registration. Foreseen Final State of the MS "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 eMLPP for a default priority level DefaultPriorityLevel 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 check the MS provides a correct user indication. Maximum Duration of Test 3 minutes. Expected Sequence Step Direction Message Comments 1 MS The MS is made to initiate a registration of eMLPP default priority level 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 RegisterSS(eMLPP, DefaultPriorityLevel) 7 SS -> MS RELEASE COMPLETE RegisterSS operation Return_result 8 SS -> MS CHANNEL RELEASE 9 MS Provide correct MMI user indication after step 7 Special Message Contents REGISTER: Information Element value/remark as default except: Facility invoke RegisterSS Supplementary service code eMLPP Default Priority arbitrary 31.12.5 eMLPP Service / interrogation
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.12.5.1 Conformance requirement	For interrogation of eMLPP default priority level, 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 InterrogateSS operation with parameter values eMLPP (MMI action) (see figure 7 of 3GPP TS 04.67 subclause 4.5). Reference(s) 3GPP TS 04.67 subclause 4.5 (figure 7). 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.2 and 9.1.9. 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1 and 9.2.9.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.12.5.2 Test purpose	To check that the MS: 1. Correctly requests a supplementary service transaction for interrogation of eMLPP in CHANNEL REQUEST message. 2. Correctly requests a supplementary service transaction for interrogation of eMLPP in the subsequent CM SERVICE REQUEST. 3. Then sends a REGISTER message containing the invoke of the InterrogateSS operation with the expected parameter values for interrogation of eMLPP default priority level. 4. Provides the appropriate user indication (as described by PIXIT) upon receipt of the result of the operation (in a RELEASE COMPLETE message).
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.12.5.3 Method of test	Initial Conditions System Simulator: 1 cell with default parameters. Mobile Station: the MS is in idle mode Specific PICS Statements - PIXIT Statements - Way to select a priority level. - Way to initiate eMLPP interrogation. - Way to indicate the result of the eMLPP interrogation. Foreseen Final State of the MS "Idle, updated". Test Procedure 1. By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of eMLPP. 2. 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. 3. The SS transaction is released and the dedicated channel is released. 4. Then check the MS provides a correct user indication. Maximum Duration of Test 3 minutes. Expected Sequence Step Direction Message Comments 1 MS The MS is made to initiate a interrogation of eMLPP default priority level 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 InterrogateSS(eMLPP) 7 SS -> MS RELEASE COMPLETE InterrogateSS operation Return_result containing SS-Status, MaximumPriorityLevel, DefaultPriorityLevel 8 SS -> MS CHANNEL RELEASE 9 MS Provide correct MMI user indication after step 7 Special Message Contents REGISTER: Information Element value/remark as default except: Facility invoke InterrogateSS Supplementary service code eMLPP
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.13 Explicit Call Transfer (ECT)	NOTE: In this subclause, Subscriber A is the MS under test, and subscribers B and C are distant parties to the calls made during the tests.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.13.1 Explicit Call Transfer invocation
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.13.1.1 Explicit Call Transfer invocation, successful case, both calls active, clearing using DISCONNECT	Conformance requirement 3GPP TS 04.91 subclauses 4.1 and 4.2. Applicability MS supporting the Explicit Call Transfer supplementary service. Test purpose To test that the MS invokes explicit call transfer between two active calls by sending a FACILITY message with the correct invoke component, and reacts correctly on receipt of a DISCONNECT response from the network. Method of test Specific PICS Statements - PIXIT Statements - Method of performing Explicit Call transfer on two active calls. Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1. Foreseen final state of the MS Call A-B, state U0. Call A-C, state U0. Maximum duration of test 30 s. Procedure Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state. On receipt of a DISCONNECT message with respect to one of the calls containing a return result component, followed by a DISCONNECT message for the other call, the MS shall respond with a RELEASE message for each call. On receipt of a RELEASE COMPLETE message for each call, the MS shall enter state U0 "Null". The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value". Expected sequence Step Direction Message Comments 1 MS Using MMI commands, perform and explicit call transfer 2 MS -> SS FACILITY TI for Call A-B or Call A-C, ExplicitCT Invoke component 3 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B 4 MS -> SS STATUS Transaction identifier of Call A-B, state U10, auxiliary state "Call held" 5 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C 6 MS -> SS STATUS Transaction identifier of Call A-C, state U10, no auxiliary state 7 SS -> MS DISCONNECT Transaction identifier of Call A-B 8 MS -> SS RELEASE Transaction identifier of Call A-B 9 SS -> MS DISCONNECT Transaction identifier of Call A-C 10 MS -> SS RELEASE Transaction identifier of Call A-C 11 SS -> MS RELEASE COMPLETE Transaction identifier of Call A-B 12 SS -> MS RELEASE COMPLETE Transaction identifier of Call A-C 13 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B 14 MS -> SS RELEASE COMPLETE Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value" 15 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C 16 MS -> SS RELEASE COMPLETE Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.13.1.2 Explicit Call Transfer invocation, successful case, both calls active, clearing using RELEASE	Conformance requirement 3GPP TS 04.91 subclauses 4.1 and 4.2. Applicability MS supporting the Explicit Call Transfer supplementary service. Test purpose 1. To test that the MS invokes explicit call transfer between two active calls by sending a FACILITY message with the correct invoke component, and reacts correctly on receipt of a RELEASE response from the network. Method of test Specific PICS Statements - PIXIT Statements - Method of performing Explicit Call transfer on two active calls. Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1. Foreseen final state of the MS Call A-B, state U0. Call A-C, state U0. Maximum duration of test 30 s. Procedure Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state. On receipt of a RELEASE message with respect to one of the calls containing a return result component, followed by a RELEASE message for the other call, the MS shall respond with a RELEASE COMPLETE message for each call and shall enter state U0 "Null". The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value". Expected sequence Step Direction Message Comments 1 MS Using MMI commands, perform and explicit call transfer 2 MS -> SS FACILITY TI for Call A-B or Call A-C, ExplicitCT Invoke component 3 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B 4 MS -> SS STATUS Transaction identifier of Call A-B, state U10, auxiliary state "Call held" 5 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C 6 MS -> SS STATUS Transaction identifier of Call A-C, state U10, no auxiliary state 7 SS -> MS RELEASE Transaction identifier of Call A-B 8 MS -> SS RELEASE COMPLETE Transaction identifier of Call A-B 9 SS -> MS RELEASE Transaction identifier of Call A-C 10 MS -> SS RELEASE COMPLETE Transaction identifier of Call A-C 11 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B 12 MS -> SS RELEASE COMPLETE Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value" 13 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C 14 MS -> SS RELEASE COMPLETE Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.13.1.3 Explicit Call Transfer invocation, successful case, both calls active, clearing using RELEASE COMPLETE	Conformance requirement 3GPP TS 04.91 subclauses 4.1 and 4.2. Applicability MS supporting the Explicit Call Transfer supplementary service. Test purpose 1. To test that the MS invokes explicit call transfer between two active calls by sending a FACILITY message with the correct invoke component, and reacts correctly on receipt of a RELEASE COMPLETE response from the network. Method of test Specific PICS Statements - PIXIT Statements - Method of performing Explicit Call transfer on two active calls. Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1. Foreseen final state of the MS Call A-B, state U0. Call A-C, state U0. Maximum duration of test 30 s. Procedure Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state. On receipt of a RELEASE COMPLETE message with respect to one of the calls containing a return result component, followed by a RELEASE COMPLETE message for the other call, the MS shall enter state U0 "Null". The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value". Expected sequence Step Direction Message Comments 1 MS Using MMI commands, perform and explicit call transfer 2 MS -> SS FACILITY TI for Call A-B or Call A-C, ExplicitCT Invoke component 3 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B 4 MS -> SS STATUS Transaction identifier of Call A-B, state U10, auxiliary state "Call held" 5 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C 6 MS -> SS STATUS Transaction identifier of Call A-C, state U10, no auxiliary state 7 SS -> MS RELEASE COMPLETE Transaction identifier of Call A-B 8 SS -> MS RELEASE COMPLETE Transaction identifier of Call A-C 9 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B 10 MS -> SS RELEASE COMPLETE Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value" 11 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C 12 MS -> SS RELEASE COMPLETE Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.13.1.4 Explicit Call Transfer invocation, successful case, second call alerting	Conformance requirement 3GPP TS 04.91 subclauses 4.1 and 4.2. Applicability MS supporting the Explicit Call Transfer supplementary service. Test purpose 1. To test that the MS invokes explicit call transfer between an active held call and an alerting call by sending a FACILITY message with the correct invoke component, and reacts correctly on receipt of clearing messages from the network. Method of test Specific PICS Statements - PIXIT Statements - Method of performing Explicit Call transfer on an active call and an alerting call. Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U4 "Call Delivered" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1. Foreseen final state of the MS Call A-B, state U0. Call A-C, state U0. Maximum duration of test 30 s. Procedure Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state. On receipt of a DISCONNECT message with respect to one of the calls containing a return result component, followed by a DISCONNECT message for the other call, the MS shall respond with a RELEASE message for each call. On receipt of a RELEASE COMPLETE message for each call, the MS shall enter state U0 "Null". The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value". Expected sequence Step Direction Message Comments 1 MS Using MMI commands, perform and explicit call transfer 2 MS -> SS FACILITY TI for Call A-B or Call A-C, ExplicitCT Invoke component 3 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B 4 MS -> SS STATUS Transaction identifier of Call A-B, state U10, auxiliary state "Call held" 5 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C 6 MS -> SS STATUS Transaction identifier of Call A-C, state U4 7 SS -> MS DISCONNECT Transaction identifier of Call A-B 8 MS -> SS RELEASE Transaction identifier of Call A-B 9 SS -> MS DISCONNECT Transaction identifier of Call A-C 10 MS -> SS RELEASE Transaction identifier of Call A-C 11 SS -> MS RELEASE COMPLETE Transaction identifier of Call A-B 12 SS -> MS RELEASE COMPLETE Transaction identifier of Call A-C 13 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B 14 MS -> SS RELEASE COMPLETE Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value" 15 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C 16 MS -> SS RELEASE COMPLETE Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.13.1.5 Explicit Call Transfer invocation, unsuccessful case	Conformance requirement 3GPP TS 04.91 subclauses 4.1 and 4.2 Applicability MS supporting the Explicit Call Transfer supplementary service. Test purpose 1. To test that the MS invokes explicit call transfer between two active calls by sending a FACILITY message with the correct invoke component, and returns both calls to their original states on receipt of an error or reject response. Method of test Specific PICS Statements - PIXIT Statements - Method of performing Explicit Call transfer on two active calls. Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS shall have Call A-B in state U10 "Active"with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1. Foreseen final state of the MS Call A-B, state U10, auxiliary state "Call held". Call A-C, Call A-C, state U10, no auxiliary state. Maximum duration of test 30 s. Procedure Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state. On receipt of a FACILITY message using the same transaction identifier and including a return error component, the MS shall not send any further messages in respect of the transfer attempt, and shall remain in the same call state for both calls. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state. Using suitable MMI commands, the MS shall again invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state. On receipt of a FACILITY message using the same transaction identifier and including a reject component, the MS shall not send any further messages in respect of the transfer attempt, and shall remain in the same call state for both calls. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state. Expected sequence Step Direction Message Comments 1 MS Using MMI commands, perform an explicit call transfer 2 MS -> SS FACILITY TI for Call A-B or Call A-C, ExplicitCT Invoke component 3 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B 4 MS -> SS STATUS Transaction identifier of Call A-B, state U10, auxiliary state "Call held" 5 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C 6 MS -> SS STATUS Transaction identifier of Call A-C, state U10, no auxiliary state 7 SS -> MS FACILITY TI same as step 2, Return Error component 8 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B 9 MS -> SS STATUS Transaction identifier of Call A-B, state U10, auxiliary state "Call held" 10 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C 11 MS -> SS STATUS Transaction identifier of Call A-C, state U10, no auxiliary state 12 MS Using MMI commands, perform an explicit call transfer 13 MS -> SS FACILITY TI for Call A-B or Call A-C, ExplicitCT Invoke component 14 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B 15 MS -> SS STATUS Transaction identifier of Call A-B, state U10, auxiliary state "Call held" 16 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C 17 MS -> SS STATUS Transaction identifier of Call A-C, state U10, no auxiliary state 18 SS -> MS FACILITY TI same as step 2, Reject component 19 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B 20 MS -> SS STATUS Transaction identifier of Call A-B, state U10, auxiliary state "Call held" 21 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C 22 MS -> SS STATUS Transaction identifier of Call A-C, state U10, no auxiliary state
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.13.1.6 Explicit Call Transfer invocation, expiry of T(ECT)	Conformance requirement 3GPP TS 04.91 subclauses 4.1 and 4.2. 3GPP TS 04.80 subclause 4.2. Applicability MS supporting the Explicit Call Transfer supplementary service. Test purpose To test that the MS invokes explicit call transfer between an active held call and an alerting call by sending a FACILITY message with the correct invoke component, and returns both calls to their original states on expiry of T(ECT). Method of test Specific PICS Statements - PIXIT Statements - Method of performing Explicit Call transfer on two active calls. Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1. Foreseen final state of the MS Call A-B, state U10, auxiliary state "Call held". Call A-C, Call A-C, state U10, no auxiliary state. Maximum duration of test 45 s. Procedure Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state. Between 5s and 15s after sending the FACILITY message, the MS shall either: - remain in the same call states and indicate failure to the user; or - send another FACILITY message with the same contents. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state. Expected sequence Step Direction Message Comments 1 MS Using MMI commands, perform an explicit call transfer 2 MS -> SS FACILITY TI for Call A-B or Call A-C, ExplicitCT Invoke component 3 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B 4 MS -> SS STATUS Transaction identifier of Call A-B, state U10, auxiliary state "Call held" 5 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C 6 MS -> SS STATUS Transaction identifier of Call A-C, state U10, no auxiliary state 7 SS Wait 15 s from receiving FACILITY message Take this branch if no message is received within 15 s A8 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B A9 MS -> SS STATUS Transaction identifier of Call A-B, state U10, auxiliary state "Call held" A10 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C A11 MS -> SS STATUS Transaction identifier of Call A-C, state U10, no auxiliary state Take this branch if a message is received within 15 s B8 MS -> SS FACILITY Same as Step 2. Message shall not be received less than 5 s after the first FACILITY message B9 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-B B10 MS -> SS STATUS Transaction identifier of Call A-B, state U10, auxiliary state "Call held" B11 SS -> MS STATUS ENQUIRY Transaction identifier of Call A-C B12 MS -> SS STATUS Transaction identifier of Call A-C, state U10, no auxiliary state
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14 User-to-User Signalling (UUS)	This subclause applies to mobile station supporting User-to-User Signalling (UUS). The objective of this clause is to test UUS concerned procedures. Unless indicated in individual sub-clauses, the default message contents in subclause 26.8.4 are applied for CC calls and default message contents in subclause 26.14.10 are applied for VGCS/VBS calls.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14.1 UUS / Implicit UUS1
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14.1.1 UUS / Implicit UUS1 / CC MO call
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14.1.1.1 Conformance requirement	The UUI service is activated implicitly by the presence of UUI in the set-up request from the mobile station. To activate UUS1 implicitly, the MS shall include a User-user information element in the SETUP message as part of a normal call request. The MS shall accept the presence of User-user information element in the ALERTING, CONNECT, DISCONNECT, RELEASE or RELEASE COMPLETE messages (as indicated in 3GPP TS 24.087, figure 1 in subclause 4.1.1). References 3GPP TS 23.087 subclauses 4.1.1 and 5.2.1.2.1. 3GPP TS 24.087 subclause 4.1.1.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14.1.1.2 Test purpose	1. To verify that upon initiation of an outgoing basic call with implicit UUS1 by the user, the MS includes a User-user information element in the SETUP message. 2. To verify that inclusion of the User-user information element with different data length in either of the downlink messages ALERTING, CONNECT, DISCONNECT or RELEASE COMPLETE, causes no adverse effects on the operation of the MS.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14.1.1.3 Method of test	Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in MM-state "idle, updated" with valid TMSI and CKSN. Specific PICS Statements - Support MO telephony (TSPC_AddInfo_MOsvc ) - Support UUS (TSPC_Serv_SS_UUS) PIXIT Statements - Way to activate implicit UUS1. - Description of display of the User-user data received from the network. Foreseen final state of the MS The MS is in MM-state "idle, updated" with valid TMSI. Test procedure By means of appropriate MMI function, the user requests implicit UUS1 and enters a string, which shall be included in the UUS1. Then MS is made to initiate a call. In the SETUP message, the User-user information element shall be present and shall include the requested string. Then, SS releases the call. The MS is made to initiate a second call with implicit UUS1. In the SETUP message, the User-user information element shall be present with the requested string. SS releases the call, by sending a RELEASE COMPLETE message including a User-user information element with a long data value. It is checked that the MS is not disturbed by the optional User-user information element. The MS is made to initiate a third call with implicit UUS1. In the SETUP message, the User-user information element shall be present with the requested string. Then SS shall include User-user information element in the ALERTING and in the CONNECT message with respectively short and long data value, it is checked that MS does not respond adversely to the inclusion of the optional User-user information element. After 10 seconds, SS initiates call clearing. SS sends DISCONNECT and RELEASE COMPLETE messages with User-user information element respectively without data and with a short data value, again the MS shall not respond adversely to the inclusion of the User-user information element, but shall continue to clear down the call normally. Maximum Duration of Test 2 minutes. Expected Sequence Step Direction Message Comments/actions/next state 0 MS The MS is in idle mode. MMI actions to initiate a CC call with implicit UUS1 including the string 'abc0123456'. 1 MS -> SS CHANNEL REQUEST 2 SS -> MS IMMEDIATE ASSIGNMENT SDCCH4 3 MS -> SS CM SERVICE REQUEST 4 MS -> SS SETUP Check User-user IE is included. See specific message contents 5 SS -> MS RELEASE COMPLETE 6 SS -> MS CHANNEL RELEASE The main signalling link shall be released by the MS (L2: DISC/UA). 10 MS MMI actions to initiate a CC call with implicit UUS1 including the string 'abc' 11 MS -> SS CHANNEL REQUEST 12 SS -> MS IMMEDIATE ASSIGNMENT SDCCH4 13 MS -> SS CM SERVICE REQUEST 14 MS -> SS SETUP Check User-user IE is included. See specific message contents 15 SS -> MS RELEASE COMPLETE Message contains the User-user IE with a long data value, see Specific message contents 16 SS -> MS CHANNEL RELEASE The main signalling link shall be released by the MS (L2: DISC/UA). 17 MS Is is checked that the MS, in a way described by the manufacturer, displays user-user data after step 15 20 MS MMI actions to initiate a CC call with implicit UUS1 including the string '123497'. 21 MS -> SS CHANNEL REQUEST 22 SS -> MS IMMEDIATE ASSIGNMENT SDCCH4 23 MS -> SS CM SERVICE REQUEST 24 MS -> SS SETUP Check User-user IE is included. See specific message contents 25 SS -> MS AUTHENTICATION REQUEST 26 MS -> SS AUTHENTICATION RESPONSE 27 SS -> MS CALL PROCEEDING 28 SS -> MS ASSIGNMENT COMMAND TCH 29 MS -> SS ASSIGNMENT COMPLETE 30 SS -> MS ALERTING Message contains the User-user IE with a short data value, see Specific message contents 31 MS It is checked that the MS, in a way described by the manufacturer, displays user-user data. 32 SS -> MS CONNECT Message contains the User-user IE with a long data value, see Specific message contents 33 MS It is checked that the MS, in a way described by the manufacturer, displays user-user data. 34 MS -> SS CONNECT ACKNOWLEDGE 35 SS -> MS DISCONNECT Without Progress Indication IE Including the User-user IE without data, see Specific message contents 36 MS It is checked that the MS, in a way described by the manufacturer, displays no user-user data. 37 MS -> SS RELEASE 38 SS-> MS RELEASE COMPLETE Message contains the User-user IE with a short data value, see Specific message contents 39 SS -> MS CHANNEL RELEASE The main signalling link shall be released by the MS (L2: DISC/UA). 40 MS It is checked that the MS, in a way described by the manufacturer, displays user-user data after step 38 Specific message contents: SETUP As default message contents as defined in subclause 26.8.4 (mobile station to network direction), except: Information Element value/remark User-user - IEI '7E'O - length 1 + the entered string length - PD User specific protocol - user-user The string as entered coded in IA5 characters ALERTING As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 2 - PD User specific protocol - user-user The following string coded in IA5 characters: "A" CONNECT As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 101 - PD User specific protocol - user-user The following string with a length of 100 octets coded in IA5 characters: "abcdefghijklmnopqrstuvwxyz0123456789abc………." DISCONNECT As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 1 - PD User specific protocol - user-user - RELEASE COMPLETE – step 15 As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 37 - PD User specific protocol - user-user The following string coded in IA5 characters: "0123456789abcdefghijklmnopqrstuvwxyz" RELEASE COMPLETE – step 38 As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 17 - PD User specific protocol - user-user The following string coded in IA5 characters: "RELEASE COMPLETE"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14.1.2 UUS / Implicit UUS1 / CC MT call
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14.1.2.1 Conformance requirement	The MS shall accept the presence of User-user information element in the SETUP and DISCONNECT messages (as indicated in 3GPP TS 23.087, figure 5.2.1.2.1.1). The MS may include User-user information element in the ALERTING or CONNECT messages (as indicated in 3GPP TS 23.087, figure 5.2.1.2.1.1). References 3GPP TS 23.087 subclause 5.2.1.2.1. 3GPP TS 24.087.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14.1.2.2 Test purpose	1. To verify that, the receipt of SETUP message including user-user information element with a short or large data value causes no adverse effects on the call establishment operation of the MS. 2. To verify that MS could include User-user information element in either of the uplink messages ALERTING or CONNECT. 3. To verify that inclusion of the User-user information element with different data length in either of the downlink message DISCONNECT or RELEASE COMPLETE, causes no adverse effects on the operation of the MS.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14.1.2.3 Method of test	Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in MM-state "idle, updated" with valid TMSI and CKSN. Specific PICS Statements - Support MT telephony (TSPC_AddInfo_MTsvc) - Support UUS (TSPC_Serv_SS_UUS) PIXIT Statements - Support the sending of UUS1 information element in ALERTING message - Support the sending of UUS1 information element in CONNECT message - Way to activate implicit UUS1. - Description of display of the User-user data received from the network. Foreseen final state of the MS The MS is in MM-state "idle, updated" with valid TMSI. Test procedure SS initiates a call. In the SETUP message, the User-user information element shall be present. It is checked that the MS, in a way described by the manufacturer, displays the user-user data. Then, SS releases the call immediately after the MS call confirmation. The SS initiates a second call and in the SETUP message, the User-user information element shall contain a larger data value. It is checked that the MS, in a way described by the manufacturer, displays the user-user data. Then the SS releases the call immediately after the MS call confirmation. In the RELEASE COMPLETE message, the User-user information element shall also contain a large data value. It is checked that the MS is not disturbed by the User-user optional information element. By means of appropriate MMI function and if MS supports User-user information element in ALERTING or CONNECT messages, the user enters a string, which shall be included in the UUS1. The SS initiates a third call and in the SETUP message, the User-user information element shall be included without data. After the MS call confirmation and depending on the MS capability, it is checked that the MS sends in the User-user information element of the ALERTING message the string as requested. When the TCH is allocated and depending on the MS capability, it is checked that the MS sends in the User-user information element of the CONNECT message the string as requested. When the call is established, the SS releases the call and shall include in the DISCONNECT message the optional User-user information element. It is checked that the MS is not disturbed by the User-user information element. The SS shall also include in the RELEASE COMPLETE message the optional User-user information element. It is checked that the MS is not disturbed by the User-user information element. Maximum Duration of Test 2 minutes. Expected Sequence Step Direction Message Comments/actions/next state 0 MS The MS is in idle mode. 1 SS -> MS PAGING REQUEST 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT U0, SDCCH4 4 MS -> SS PAGING RESPONSE 7 SS -> MS SETUP User-user IE included with a short data value, see Specific message contents 8 MS Check that the MS, in a way described by the manufacturer, displays the User-user data value. 9 MS -> SS CALL CONFIRMED 10 SS -> MS RELEASE COMPLETE 11 SS -> MS CHANNEL RELEASE The main signalling link shall be released by the MS (L2: DISC/UA). 15 SS -> MS PAGING REQUEST 16 MS -> SS CHANNEL REQUEST 17 SS -> MS IMMEDIATE ASSIGNMENT U0, SDCCH4 18 MS -> SS PAGING RESPONSE 21 SS -> MS SETUP User-user IE included with a large data value, see Specific message contents 22 MS Check that the MS, in a way described by the manufacturer, displays the User-user data value. 23 MS -> SS CALL CONFIRMED 24 SS -> MS RELEASE COMPLETE Message contains the User-user IE with a long data value, see Specific message contents. 25 SS -> MS CHANNEL RELEASE The main signalling link shall be released by the MS (L2: DISC/UA). 26 MS Check that the MS, in a way described by the manufacturer, displays the user-user data value after step 24 If supported, MMI actions to initiate implicit UUS1 with the string '12346aA' 30 SS -> MS PAGING REQUEST 31 MS -> SS CHANNEL REQUEST 32 SS -> MS IMMEDIATE ASSIGNMENT U0, SDCCH4 33 MS -> SS PAGING RESPONSE 34 SS -> MS AUTHENTICATION REQUEST 35 MS -> SS AUTHENTICATION RESPONSE 36 SS -> MS SETUP User-user IE included without data. See Specific message contents. 37 MS Check that the MS, in a way described by the manufacturer, displays no User-user data value. 38 MS -> SS CALL CONFIRMED 39 MS -> SS ALERTING If MS support User-user IE in ALERTING message, then check the presence of this IE. See specific message contents. 40 MS -> SS CONNECT If MS support User-user IE in CONNECT message, then check the presence of this IE. See specific message contents. 41 SS -> MS ASSIGNMENT COMMAND TCH 42 MS -> SS ASSIGNMENT COMPLETE 43 SS -> MS CONNECT ACKNOWLEDGE 44 SS -> MS DISCONNECT With the User-user IE with a long data value, see Specific message contents 45 MS Check that the MS, in a way described by the manufacturer, displays the User-user data value. 46 MS -> SS RELEASE 47 SS-> MS RELEASE COMPLETE Message contains the User-user IE with a short data value, see Specific message contents. 48 SS -> MS CHANNEL RELEASE The main signalling link shall be released by the MS (L2: DISC/UA). 49 MS Check that the MS, in a way described by the manufacturer, displays the User-user data value after step 47 Specific message contents: SETUP – step 7 As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 4 - PD User specific protocol - user-user The following string coded in IA5 characters :"012" SETUP – step 21 As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 33 - PD User specific protocol - user-user The following string coded in IA5 characters : "abcdefghijklmnopqrstuvwxyz012345’" SETUP – step 36 As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 1 - PD User specific protocol - user-user - RELEASE COMPLETE – step 24 As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 37 - PD User specific protocol - user-user The following string coded in IA5 characters : "abcdefghijklmnopqrstuvwxyz0123456789" RELEASE COMPLETE – step 47 As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 2 - PD User specific protocol - user-user The following string coded in IA5 characters: "A" ALERTING As default message contents as defined in subclause 26.8.4 (mobile station to network direction), except: Information Element value/remark User-user - IEI '7E'O - length 8 - PD User specific protocol - user-user The string '12346aA' coded in IA5 characters CONNECT As default message contents as defined in subclause 26.8.4 (mobile station to network direction), except: Information Element Value/remark User-user - IEI '7E'O - length 8 - PD User specific protocol - user-user The string '12346aA ' coded in IA5 characters DISCONNECT As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element Value/remark User-user - IEI '7E'O - length 37 - PD User specific protocol - user-user The following string coded in IA5 characters : "abcdefghijklmnopqrstuvwxyz0123456789"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14.1.3 UUS / Implicit UUS1 / Interactions with Call Waiting and call HOLD supplementary services
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14.1.3.1 Conformance requirement	There are no interactions between UUS and the Call hold (HOLD) and Call waiting (CW) supplementary services. To activate UUS1 implicitly, the MS shall include a User-user information element in the SETUP message as part of a normal call request. The MS shall accept the presence of User-user information element in the SETUP and DISCONNECT messages (as indicated in 3GPP TS 23.087, figure 5.2.1.2.1.1). References 3GPP TS 23.087 subclauses 4.1.1, 5.2.1.2.1.1 and 5.2.1.2.1. 3GPP TS 24.087 subclauses 4.1.1, 6.4 and 6.5.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14.1.3.2 Test purpose	1. To verify that when in active Call State and supporting Call Hold, to initiate a second call with implicit UUS1, the MS places the first call on hold and sends a SETUP message with the User-user information element. Verify that the second call is successfully established. 2. In call active state and supporting Call Waiting, when a Call Waiting indication includes a User-user information element, the MS accepts the waiting call and places the first call on hold and successfully establishes the second call.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.14.1.3.3 Method of test	Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS has a call ("Call A-B") in the active state. The SIM in the MS under test has Call Waiting enabled. Specific PICS Statements - Support MO telephony (TSPC_AddInfo_MOsvc) - Support MT telephony (TSPC_AddInfo_MTsvc) - Support UUS (TSPC_Serv_SS_UUS) - Support hold (TSPC_Serv_SS_HOLD) PIXIT Statements - Way to activate implicit UUS1. - Description of display of the User-user data received from the network. Foreseen final state of the MS The MS is in MM-state "idle, updated" with valid TMSI. Test procedure A call is established between the MS and SS. This call is the active call named Call A-B. Using suitable MMI commands, the MS shall request that the call A-B be placed on hold. The MS shall send a HOLD message and enter auxiliary state "hold request". On receipt of a HOLD ACKNOWLEDGE message from the SS, the MS is made to initiate a second call with implicit UUS1. It is checked that the MS includes the User-user information element in the SETUP message. Then the SS sends an ALERTING message including the optional User-user information. It is checked that the MS, in a way described by the manufacturer, displays the User-user data value. Then the SS sends a CONNECT message including the optional User-user information element. It is checked that the MS, in a way described by the manufacturer, displays the User-user data value. on receipt of a CONNECT ACKNOWLEDGE message, MS shall enter state U10 "Active". The SS releases the second call A-C and shall include in the DISCONNECT message the optional User-user information element. It is checked that the MS is not disturbed by the User-user information element. The SS shall also include in the RELEASE COMPLETE message the optional User-user information element. It is checked that the MS is not disturbed by the User-user information element. The Call A-B is still alive. By means of appropriate MMI function, the user enters a string, which shall be included in the UUS1 sent by the MS. The SS sends a SETUP message including a User-user information element and indicating the request of a new call, named Call C-A. It is checked with the appropriate MMI function, that the MS displays the contents of the User-user information element. Then the MS shall place Call A-B on hold, and answer Call C-A. The MS shall send a HOLD message to the SS using the transaction identifier of Call A-B. On receipt of a HOLD ACKNOWLEDGE from the SS, the MS shall send a CALL CONFIRMED message and an ALERTING message to the SS, using the transaction identifier of Call C-A, and depending on the MS capability including the optional User-user information element as requested by the user. Then the MS shall send a CONNECT message to the SS, using the transaction identifier of Call C-A, and depending on the MS capability including the optional User-user information element as entered by the user. on receipt of a CONNECT ACKNOWLEDGE message, MS shall enter state U10 "Active". The SS releases the call C-A and shall include in the DISCONNECT message the optional User-user information element. It is checked that the MS is not disturbed by the User-user information element. The SS shall also include in the RELEASE COMPLETE message the optional User-user information element. It is checked that the MS is not disturbed by the User-user information element. Then SS releases the first call A-B. Maximum Duration of Test 2 minutes. Expected Sequence Step Direction Message Comments/actions/next state 0 MS Active call state with call A-B. 1 MS If supported, MMI actions to initiate implicit UUS1 with the string '12345'. 2 MS Call A-C is requested using MMI commands and Call A-B is placed on hold using MMI commands 3 MS -> SS CM SERVICE REQUEST Transaction identifier of Call A-C 4 SS -> MS CM SERVICE ACCEPT Transaction identifier of Call A-C 5 MS -> SS SETUP Check User-user IE is included, transaction identifier of Call A-C, see Specific message contents. 6 SS -> MS ALERTING Message contains the User-user IE with a short data value, transaction identifier of Call A-C, see Specific message contents 7 MS Check that the MS, in a way described by the manufacturer, displays the User-user data value. 8 MS -> SS HOLD Transaction identifier of Call A-B 9 SS -> MS HOLD ACKNOWLEDGE Transaction identifier of Call A-B 10 SS -> MS CONNECT Message contains the User-user IE with a long data value, transaction identifier of Call A-C, see Specific message contents 11 MS Check that the MS, in a way described by the manufacturer, displays the User-user data value. 12 MS -> SS CONNECT ACKNOWLEDGE Transaction identifier of Call A-C 13 SS -> MS DISCONNECT Without Progress Indication IE, transaction identifier of Call A-C. With the User-user IE without data, see Specific message contents 14 MS Check that the MS, in a way described by the manufacturer, displays the User-user data value. 15 MS -> SS RELEASE 16 SS-> MS RELEASE COMPLETE Message contains the User-user IE with a short data value, transaction identifier of Call A-C, see Specific message contents 17 SS Call A-B is released 18 SS -> MS CHANNEL RELEASE The main signalling link shall be released by the MS (L2: DISC/UA). 19 MS Check that the MS, in a way described by the manufacturer, displays the User-user data value after step 16 20 Active call state with call A-B. 21 MS MMI actions to initiate implicit UUS1 with the string '201'. 22 SS -> MS PAGING REQUEST 23 MS -> SS PAGING RESPONSE 31 SS->MS SETUP User-user IE is included, see Specific message contents. Transaction identifier of Call C-A 32 MS Check that the MS, in a way described by the manufacturer, displays the User-user data value. Call A-B is placed on hold using MMI commands. 34 MS -> SS HOLD Transaction identifier of Call A-B 35 SS -> MS HOLD ACKNOWLEDGE Transaction identifier of Call A-B 36 MS Call C-A is answered using MMI commands 37 MS -> SS CALL CONFIRMED Transaction identifier of Call C-A 38 MS -> SS ALERTING If MS support User-user IE in ALERTING message, then check the presence of this IE. Transaction identifier of Call C-A 39 MS -> SS CONNECT If MS supports User-user IE in CONNECT message, then check the presence of this IE. Transaction identifier of Call C-A 40 SS -> MS CONNECT ACKNOWLEDGE Transaction identifier of Call C-A 41 SS -> MS DISCONNECT With the User-user IE without data, transaction identifier of Call C-A, see Specific message contents. 42 MS Check that the MS, in a way described by the manufacturer, displays the User-user data value. 43 MS -> SS RELEASE 44 SS-> MS RELEASE COMPLETE Message contains the User-user IE with a short data value, see Specific message contents. Transaction identifier of Call C-A 45 MS Check that the MS, in a way described by the manufacturer, displays the User-user data value. Specific message contents: SETUP – step 5 As default message contents as defined in subclause 26.8.4 (mobile station to network direction), except: Information Element value/remark User-user - IEI '7E'O - length 1 + the entered string length - PD User specific protocol - user-user The string as entered, coded in IA5 characters SETUP – step 31 As default message contents as defined in subclause 26.8.4 (network direction to mobile station), except: Information Element value/remark User-user - IEI '7E'O - length 4 - PD User specific protocol - user-user The following string coded in IA5 characters : "012" ALERTING– step 6 As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 4 - PD User specific protocol - user-user The following string coded in IA5 characters : "012" ALERTING– step 38 As default message contents as defined in subclause 26.8.4 (mobile station to network direction), except: Information Element value/remark User-user - IEI '7E'O - length 1 + the entered string length - PD User specific protocol - user-user The string as entered, coded in IA5 characters CONNECT– step 10 As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 37 - PD User specific protocol - user-user The following string coded in IA5 characters : "abcdefghijklmnopqrstuvwxyz0123456789" CONNECT– step 39 As default message contents as defined in subclause 26.8.4 (mobile station to network direction), except: Information Element value/remark User-user - IEI '7E'O - length 1 + the entered string length - PD User specific protocol - user-user The string as entered in IA5 characters DISCONNECT As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 1 - PD User specific protocol - user-user - RELEASE COMPLETE As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except: Information Element value/remark User-user - IEI '7E'O - length 2 - PD User specific protocol - user-user The following string coded in IA5 characters: "A"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.15 Follow Me (FM)	This subclause applies to mobile station supporting Follow Me (FM). The objective of this clause is to test FM concerned procedures. Unless indicated in individual sub-clauses, the default message contents in subclause 31.11 are applied.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.15.1 Follow Me (FM) / Registration
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.15.1.1 Conformance requirement	1. The initiating subscriber registers the Follow Me feature with respect to a particular remote party. The initiating subscriber shall provide the following information to the network: the number of the remote party. The initiating subscriber shall receive an indication if the FM registration request was accepted or rejected by the network. 2. MS shall behave as indicated in the Information flow as indicated in 3GPP TS 23.094, figure 4.1. 3. As an operator's option additional information (such as passwords) for registration may be required from the initiating subscriber. This information shall be coded as a USSD string with a length not exceeding 30 characters. 4. All the messages between MS and the mobile network and internal to the mobile network, which are used for control of Follow Me, are USSD Phase 2 messages. 5. If a mobile initiated USSD request using protocol version 2 is rejected by the network, and the reason for the rejection is indicated either by the problem code "unrecognized operation" or a cause "Facility rejected", the MS shall assume that the network only supports protocol version 1 of USSD operations. The MS shall re‑attempt the request by using the appropriate protocol version 1 USSD operation without an SS version indicator if the unstructured data entered by the user can be coded as an IA5 string. References 3GPP TS 22.094 subclause 6.3. 3GPP TS 23.094 subclauses 4.1, 4.2 and 4.4. 3GPP TS 24.090 subclause 6.1.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.15.1.2 Test purpose	1. To check that the MS correctly requests a supplementary service transaction for registration of FM in CHANNEL REQUEST message and in the subsequent CM SERVICE REQUEST. 2. To check that the MS sends a REGISTER message using USSD phase 2 and containing the FM-request control message for registration. 3. To check that upon receipt of the result or the error of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer). 4. To check that upon receipt of a rejection from the network with the problem code "unrecognized operation" or a cause "Facility rejected", the MS re-attempt the request by using USSD version 1.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.15.1.3 Method of test	Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in MM-state "idle, updated" with valid TMSI and CKSN. Specific PICS Statements - PIXIT Statements - Way to activate the registration of FM. - Description of display of the FM answers from the network. Foreseen final state of the MS The MS is in MM-state "idle, updated" with valid TMSI. Test procedure By means of appropriate MMI functions, the user requests registration of FM for a remote number. Upon receipt of the REGISTER message, SS answers with the RELEASE COMPLETE message with an unsuccessful FM-result information. Check that the MS provides the appropriate user indication (as described by the manufacturer). Then SS transaction is released. This procedure is executed for all possible error values. The user requests registration of FM for another remote subscriber. Upon receipt of the operation (in a REGISTER message), SS answers with a RELEASE COMPLETE message with a successful FM-response information. Check that the MS provides the appropriate user indication (as described by the manufacturer). The SS transaction is released. Then user request again two registrations, upon receipt of the REGISTER message, SS answers with a RELEASE COMPLETE message including a rejection with respectively the problem code "unrecognized operation" or a cause "facility rejected". Check that MS re-attempt the request by using USSD version 1: without the SS version indicator information element included in the REGISTER message. Maximum Duration of Test 2 minutes. Expected Sequence Test steps 1 to 10 are executed for k=1 to 13 with respectively the following error values: 1. Illegal interaction with incoming barring. 2. Unauthorised request. 3. Unknown remote party. 4. FM not subscribed. 5. Remote party already registered. 6. Unauthorised changes to remote party. 7. Illegal interaction with call forwarding. 8. Illegal interaction with call barring. 9. Request to own MSISDN not possible. 10. Forwarded-to number is invalid directory number. 11. Insufficient information. 12. Forwarded-to number is a special code. 13. Conflicting situation with other supplementary services. Step Direction Message Comments 0 MS The MS is in idle mode. 1 MS The MS is made to initiate a registration of FM 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 Check that the content of this message matches specific message contents. 7 SS -> MS RELEASE COMPLETE With an unsuccessful FM-result info with the following error value: k=1: Illegal interaction with incoming barring (code 21) k=2: Unauthorised request (code 22) k=3: Unknown remote party (code 41) k=4: FM not subscribed (code 42) k=5: Remote party already registered (code 61) k=6: Unauthorised changes to remote party (code 64) k=7: Illegal interaction with call forwarding (code 65) k=8: Illegal interaction with call barring (code 66) k=9: Request to own MSISDN not possible (code 67) k=10: Forwarded-to number is invalid directory number (code 80) k=11: Insufficient information (code 81) k=12: Forwarded-to number is a special code (code 82) k=13: Conflicting situation with other supplementary services (code 83) See specific message contents. 8 SS -> MS CHANNEL RELEASE 9 MS Check that the MS, in a way described by the manufacturer, displays the error after step 7 15 MS The MS is made to initiate a registration of FM 16 MS -> SS CHANNEL REQUEST With establishment cause "Other procedures which can be completed with an SDCCH" 17 SS -> MS IMMEDIATE ASSIGNMENT 18 MS -> SS CM SERVICE REQUEST Cause: "supplementary service activation" 19 SS -> MS CM SERVICE ACCEPT 20 MS -> SS REGISTER Check that the content of this message matches specific message contents. 21 SS -> MS RELEASE COMPLETE With a successful FM-result. See specific message contents. 22 SS -> MS CHANNEL RELEASE 23 MS It is checked that the MS, in a way described by the manufacturer, displays the positive result after step 21 30 MS The MS is made to initiate a registration of FM 31 MS -> SS CHANNEL REQUEST With establishment cause "Other procedures which can be completed with an SDCCH" 32 SS -> MS IMMEDIATE ASSIGNMENT 33 MS -> SS CM SERVICE REQUEST Cause: "supplementary service activation" 34 SS -> MS CM SERVICE ACCEPT 35 MS -> SS REGISTER Check that the content of this message matches specific message contents. 36 SS -> MS RELEASE COMPLETE Including a rejection with the problem code "unrecognized operation" 37 SS -> MS CHANNEL RELEASE 38 MS -> SS CHANNEL REQUEST With establishment cause "Other procedures which can be completed with an SDCCH" 39 SS -> MS IMMEDIATE ASSIGNMENT 40 MS -> SS CM SERVICE REQUEST Cause: "supplementary service activation" 41 SS -> MS CM SERVICE ACCEPT 42 MS -> SS REGISTER Check that SS version indicator IE is not included. See specific message contents. 43 SS -> MS RELEASE COMPLETE With a successful FM-result. See specific message contents. 44 SS -> MS CHANNEL RELEASE 45 It is checked that the MS, in a way described by the manufacturer, displays the positive result after step 43 50 MS The MS is made to initiate a registration of FM 51 MS -> SS CHANNEL REQUEST With establishment cause "Other procedures which can be completed with an SDCCH" 52 SS -> MS IMMEDIATE ASSIGNMENT 53 MS -> SS CM SERVICE REQUEST Cause: "supplementary service activation" 54 SS -> MS CM SERVICE ACCEPT 55 MS -> SS REGISTER The SS checks that the content of this message matches specific message contents. 56 SS -> MS RELEASE COMPLETE Including a rejection with the cause value Facility rejected. See specific message contents. 57 SS -> MS CHANNEL RELEASE 58 MS -> SS CHANNEL REQUEST With establishment cause "Other procedures which can be completed with an SDCCH" 59 SS -> MS IMMEDIATE ASSIGNMENT 60 MS -> SS CM SERVICE REQUEST Cause: "supplementary service activation" 61 SS -> MS CM SERVICE ACCEPT 62 MS -> SS REGISTER Check that SS version indicator IE is not included. See specific message contents. 63 SS -> MS RELEASE COMPLETE With a successful FM-result. See specific message contents. 64 SS -> MS CHANNEL RELEASE 65 MS It is checked that the MS, in a way described by the manufacturer, displays the positive result after step 63 Specific message contents: REGISTER Information Element value/remark Supplementary service protocol discriminator Supplementary service (call independent) Transaction identifier '1011'B Message type As 3GPP TS 24.080 Facility 1C See below SS version indicator As specified in 3GPP TS 24.080 For steps 42 and 62 omitted For steps 6, 20, 35 and 55, Facility Information Element with Invoke = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.3. Contents Value/remark Facility IE identifier As 3GPP TS 24.080 Length of FIE contents depending on the length of ussd-string Component type tag Invoke CS/C/tag=1 Component length depending on the length of ussd-string InvokeID tag From 3GPP TS 24.080 Invoke ID length 1 Invoke ID Arbitrary (1 octet) Operation Code tag From 3GPP TS 24.080 Operation Code length 1 Operation Code UnstructuredSS-Request Ussd-dataCodingScheme 1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" Ussd-string For step 6 *21404965878*# For step 20 21404969# For steps 35 and 55 21431245688**# RELEASE COMPLETE Information Element value/remark Supplementary service protocol discriminator Supplementary service (call independent) Transaction identifier the transaction value is the same as the REGISTER transaction value but the transaction flag is different Message type As 3GPP TS 24.080 Cause For step 56, cause is set to "facility rejected" and FIE is omitted. For steps 7,21,43,63,36 this field is omitted. Facility Information Element See below (omitted for step 56) SS version indicator As specified in 3GPP TS 24.080 For steps 7, 21, 43 and 63, Facility Information Element with Return result = ProcessUnstructuredSS-Request return result component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.6. Contents Value/remark Facility IE identifier As 3GPP TS 24.080 Length of FIE contents depending on the length of ussd-string Component type tag Return result Component length depending on the length of ussd-string InvokeID tag From 3GPP TS 24.080 Invoke ID length 1 Invoke ID The same as the invoke of the ProcessUnstructuredSS-Request Ussd-dataCodingScheme 1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" Ussd-string For step 7: value of the error code For steps 21 43 and 63: 01 For step 36, Facility Information Element with Reject = ProcessUnstructuredSS-Request return result component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.6. Contents Value/remark Facility IE identifier As 3GPP TS 24.080 Length of FIE contents depending on the length of ussd-string Component type tag Reject Component length depending on the length of ussd-string InvokeID tag From 3GPP TS 24.080 Invoke ID length 1 Invoke ID The same as the invoke of the ProcessUnstructuredSS-Request Problem Code tag As 3GPP TS 24.080 Problem Code length 1 General Problem code Unrecognized operation
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.15.2 Follow Me (FM) / Interrogation
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.15.2.1 Conformance requirement	1. An initiating subscriber (also the FM service supervisor) shall be able to interrogate the Follow Me data of any remote party, for which she is authorised to become initiating subscriber. 2. In case the remote party corresponds to a subscriber the remote party shall be able to interrogate her own Follow Me data stored in the network. 3. As an operator's option additional information (such as passwords) for interrogation may be required from the subscriber. The registration procedure shall transport this information from the subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters. 4. All the messages between MS and the mobile network and internal to the mobile network, which are used for control of Follow Me, are USSD Phase 2 messages. 5. MS shall behave as indicated in the Information flow as indicated in 3GPP TS 23.094, figure 4.1. References 3GPP TS 22.094 subclauses 6.8 and 7.3. 3GPP TS 23.094 subclauses 4.1, 4.2 and 4.4. 3GPP TS 24.090 subclause 6.1.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.15.2.2 Test purpose	1. To check that the MS (as initiating subscriber or remote party) correctly requests a supplementary service transaction for interrogation of FM in CHANNEL REQUEST message and in the subsequent CM SERVICE REQUEST. 2. To check that the MS sends a REGISTER message using USSD version 2 and containing the FM-request control message for interrogation. 3. To check that upon receipt of the result or the error of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer).
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.15.2.3 Method of test	Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in MM-state "idle, updated" with valid TMSI and CKSN. The MS is registered to FM with respect to a remote party B. Specific PICS Statements - PIXIT Statements - Way to activate the interrogation of FM. - Description of display of the FM answers from the network. Foreseen final state of the MS The MS is in MM-state "idle, updated" with valid TMSI. Test procedure MS is registered to FM. By means of appropriate MMI functions, the user requests interrogation of FM for a remote number. Upon receipt of the REGISTER message, SS answers with the RELEASE COMPLETE message with an unsuccessful FM-result in a facility information element. Check that the MS provides the appropriate user indication (was described by the manufacturer). Then SS transaction is released. This procedure is executed for all possible error values. The user requests interrogation of FM for another remote subscriber. Upon receipt of the operation (in a REGISTER message), SS answers with a RELEASE COMPLETE message with a successful FM-response information. Check that the MS provides the appropriate user indication (as described by the manufacturer). The SS transaction is released. Maximum Duration of Test 2 minutes. Expected Sequence Test steps 1 to 10 are executed for k=1 to 6 with respectively the following error values: 1. Illegal interaction with incoming barring. 2. Unauthorised request. 3. Unknown remote party. 4. FM not subscribed. 5. FM not registered to remote party. 6. Conflicting situation with other supplementary services. Step Direction Message Comments 0 MS The MS is in idle mode. MS is registered to FM with respect to a remote party B. 1 MS The MS is made to initiate an interrogation of FM of remote subscriber other than B. 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 Check that the content of this message matches specific message contents. 7 SS -> MS RELEASE COMPLETE With an unsuccessful FM-result info with the following error value: k=1: Illegal interaction with incoming barring (code 21) k=2: Unauthorised request (code 22) k=3: Unknown remote party (code 41) k=4: FM not subscribed (code 42) k=5: FM not registered to remote party (code 62) k=6: Conflicting situation with other supplementary services (code 83) See specific message contents. 8 SS -> MS CHANNEL RELEASE 9 MS It is checked that the MS, in a way described by the manufacturer, displays the error after step 7 15 MS The MS is made to initiate an interrogation of FM of remote party B. 16 MS -> SS CHANNEL REQUEST With establishment cause "Other procedures which can be completed with an SDCCH" 17 SS -> MS IMMEDIATE ASSIGNMENT 18 MS -> SS CM SERVICE REQUEST Cause: "supplementary service activation" 19 SS -> MS CM SERVICE ACCEPT 20 MS -> SS REGISTER Check that the content of this message matches specific message contents. 21 SS -> MS RELEASE COMPLETE With a successful FM-result. See specific message contents. 22 SS -> MS CHANNEL RELEASE 23 MS Check that the MS, in a way described by the manufacturer, displays the positive result after step 21 Specific message contents: REGISTER Information Element value/remark Supplementary service protocol discriminator Supplementary service (call independent) Transaction identifier ‘1011’B Message type As 3GPP TS 24.080 Facility 1C See below SS version 7F As 3GPP TS 24.080 For steps 6 and 20, Facility Information Element with Invoke = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.3. Contents Value/remark Facility IE identifier As 3GPP TS 24.080 Length of FIE contents depending on the length of ussd-string Component type tag CS/C/tag=1 Component length depending on the length of ussd-string InvokeID tag From 3GPP TS 24.080 Invoke ID length 1 Invoke ID Arbitrary (1 octet) Operation Code tag From 3GPP TS 24.080 Operation Code length 1 Operation Code ProcessUnstructuredSS-Request Ussd-dataCodingScheme 1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" Ussd-string For step 6: #21445896# For step 20: #21431245688# RELEASE COMPLETE Information Element value/remark Supplementary service protocol discriminator Supplementary service (call independent) Transaction identifier the transaction value is the same as the REGISTER transaction value but the transaction flag is different Message type As 3GPP TS 24.080 Cause Omitted. Facility Information Element See below SS version indicator As specified in 3GPP TS 24.080 For steps 7 and 21, Facility Information Element with Return result = ProcessUnstructuredSS-Request return result component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.6. Contents Value/remark Facility IE identifier As 3GPP TS 24.080 Length of FIE contents depending on the length of ussd-string Component type tag Return result Component length depending on the length of ussd-string InvokeID tag From 3GPP TS 24.080 Invoke ID length 1 Invoke ID The same as the invoke of the ProcessUnstructuredSS-Request Ussd-dataCodingScheme 1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" Ussd-string For step 7: value of the error code For steps 21: 03 31245688
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.15.3 Follow Me (FM) / Erasure
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.15.3.1 Conformance requirement	A previous FM registration can be erased in either of the following ways: a) The initiating subscriber can specifically erase her previous registration with an appropriate control procedure. b) In case the remote party corresponds to a subscriber the remote party can erase any previous registration with an appropriate control procedure. c) The FM service supervisor can erase any previous registration to any remote party with an appropriate control procedure (forced erasure). The subscriber who initiates the FM erase request shall be informed of the outcome of the request by the network. As an operator's option additional information (such as passwords) for erasure may be required from the subscriber. The registration procedure shall transport this information from the subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters. MS shall behave as indicated in the Information flow as indicated in 3GPP TS 23.094, figure 4.1. All the messages between MS and the mobile network and internal to the mobile network, which are used for control of Follow Me, are USSD Phase 2 messages. References 3GPP TS 22.094 subclause 6.4. 3GPP TS 23.094 subclauses 4.1, 4.2 and 4.4. 3GPP TS 24.090 subclause 6.1.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.15.3.2 Test purpose	1. To check that the MS, acting as an initiating subscriber or as a remote party, correctly requests a supplementary service transaction for erasure of FM in CHANNEL REQUEST message and in the subsequent CM SERVICE REQUEST. 2. To check that the MS as initiating subscriber or remote party sends a REGISTER message containing the FM-request control message for erasure. 3. To check that the MS, acting as a supervisor, correctly requests a supplementary service transaction for erasure of FM in CHANNEL REQUEST message and in the subsequent CM SERVICE REQUEST 4. To check that the MS as supervisor sends a REGISTER message containing the FM-request control message for forced-erasure. 5. To check that upon receipt of the result or the error of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer).

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.