3.1 ESTUDIO DEL ESPACIO ANTES DEL PROYECTO
3.1.6 MEDIO SOCIOECONÓMICO
This procedure allows the MSC to request resources from a BSS in a manner similar to that used for the assignment case and terminates the handover seen from the MS. It is used during handover with the new BSS for allocation of the necessary resources before the MS accesses the BSS and covers the following procedures:
- handover resource allocation, defined in GSM 08.08 [10];
- physical channel establishment, defined in GSM 04.08 [4];
- handover completion, defined in GSM 04.08 [4].
8.1.3.8.1.1 Normal Case Test Purpose
To verify the normal external handover procedure.
Test Case Initial Setup
O&M-messages as defined by the operator or the manufacturer shall be input on the OMC-interface setting the timer T3105 to an appropriate value B, the parameter Ny1 to an appropriate value C, restricting the BSS to choose only one dedicated channel and disabling queuing on handover requests, if supported.
Description
1. A HANDOVER REQUEST message shall be input on the MSC-interface. The message shall contain an indication of the type of channel needed and the terrestrial resource to be used. The channel shall be a TCH and the terrestrial resource to be used shall be A. The response on any interface shall be recorded.
2. HANDOVER ACCESS messages shall be input continuously on the radio interface on the correct physical channel with the same handover reference number (PAR1) as in the HANDOVER REQUEST ACKNOWLEDGE message output in step 1. The response on any interface shall be recorded.
3. LAPDm SABM frame shall be input on the radio interface on the main signalling link before the time C x B. The response on any interface shall be recorded.
4. A HANDOVER COMPLETE message shall be input on the radio interface on the main signalling link. The response on any interface shall be recorded.
Message flow
MS BSS MSC HAND REQ
HAND REQ ACK
--->
HAND ACC
--->
HAND ACC
--->
. .
PHYS INFO HAND DET
<---*--->
PHYS INFO T3105 < .
. Ny1
PHYS INFO
SABM
- - - >
UA
< HAND COM
--->
HAND COM
--->
The messages from the BSSTE will be:
1. HANDOVER REQUEST on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.8, with:
Channel type = TCH Circuit identity code = A
2. HANDOVER ACCESS on the Air interface, coded as specified in GSM 04.08 [4], 9.1.14, with:
Handover reference = PAR1
3. SABM LAPDm frame on the Air interface, coded as specified in GSM 04.06 [3].
4. HANDOVER COMPLETE on the Air interface, coded as specified in GSM 04.08 [4], 9.1.16.
Conformance Requirement
In the case of step 1, a HANDOVER REQUEST ACKNOWLEDGE message shall occur at the MSC-interface. No messages shall occur on the radio interface.
In the case of step 2, a HANDOVER DETECT message shall occur on the MSC-interface and PHYSICAL INFORMATION messages shall occur on the radio interface on the main signalling link with an interval of B.
In the case of step 3, a LAPDm UA frame shall occur on the radio interface on the main signalling link.
In the case of step 4, a HANDOVER COMPLETE message shall occur on the MSC-interface.
The messages from the BSS shall be:
1. HANDOVER REQUEST ACKNOWLEDGE on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.10, with:
Layer 3 information = HAND CMD (as in GSM 04.08 [4], 9.1.15)
2. HANDOVER DETECT on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.40.
2. PHYSICAL INFORMATION on the Air interface, coded as specified in GSM 04.08 [4], 9.1.28.
3. UA LAPDm frame on the Air interface, coded as specified in GSM 04.06 [3].
4. HANDOVER COMPLETE on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.12.
Requirement reference
GSM 04.08 [4], 3.4.4.2.2 and 3.4.4.3 GSM 08.08 [10], 3.1.5.2.1
8.1.3.8.1.2 No LAPDm connection Test Purpose
To verify the external handover procedure when the mobile does not send a SABM LAPDm frame.
Test Case Initial Setup
O&M-messages as defined by the operator or the manufacturer shall be input on the OMC-interface setting the timer T3105 to an appropriate value B, the parameter Ny1 to an appropriate value C, restricting the BSS to choose only one dedicated channel and disabling queuing on handover requests, if supported.
Description
1. A HANDOVER REQUEST message shall be input on the MSC-interface. The message shall contain an indication of the type of channel needed and the terrestrial resource to be used. The channel shall be a TCH and the terrestrial resource to be used shall be A. The response on any interface shall be recorded.
2. HANDOVER ACCESS messages shall be input on the radio interface on the correct physical channel with the same handover reference number (PAR1) as in the HANDOVER REQUEST ACKNOWLEDGE message output in step 1. The response on any interface shall be recorded. No further messages shall be input.
The messages from the BSSTE will be:
1. HANDOVER REQUEST on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.8, with:
Channel type = TCH Circuit identity code = A
2. HANDOVER ACCESS on the Air interface, coded as specified in GSM 04.08 [4], 9.1.14, with:
Handover reference = PAR1 Conformance Requirement
In the case of step 1, a HANDOVER REQUEST ACKNOWLEDGE message shall occur at the MSC-interface. No messages shall occur on the radio interface.
In the case of step 2, a HANDOVER DETECT message shall occur on the MSC-interface and C+1 PHYSICAL INFORMATION messages shall occur on the radio interface on the main signalling link with an interval of B. Then, a CLEAR REQUEST message shall occur on the MSC-interface with the cause value
"radio interface message failure".
The messages from the BSS shall be:
1. HANDOVER REQUEST ACKNOWLEDGE on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.10, with:
Layer 3 information = HAND CMD (as in GSM 04.08 [4] 9.1.15)
2. HANDOVER DETECT on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.40 2. PHYSICAL INFORMATION on the Air interface, coded as specified in GSM 04.08 [4], 9.1.28 2. CLEAR REQUEST on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.20 Requirement reference
GSM 04.08 [4], 3.4.4.2.2 and 3.4.4.4 GSM 08.08 [10], 3.1.5.3.1
8.1.3.8.1.3 Wrong Handover Reference Test Purpose
To verify the external handover procedure when the mobile sends a wrong Handover Reference in the HANDOVER ACCESS message.
Test Case Initial Setup
O&M-messages as defined by the operator or the manufacturer shall be input on the OMC-interface setting the timer T3105 to an appropriate value B, the parameter Ny1 to an appropriate value C, restricting the BSS to choose only one dedicated channel and disabling queuing on handover requests, if supported.
Description
1. A HANDOVER REQUEST message shall be input on the MSC-interface. The message shall contain an indication of the type of channel needed and the terrestrial resource to be used. The channel shall be a TCH and the terrestrial resource to be used shall be A. The response on any interface shall be recorded.
2. HANDOVER ACCESS messages shall be input on the radio interface on the correct physical channel with a different handover reference number (PAR1) than the one sent in the HANDOVER REQUEST ACKNOWLEDGE message output in step 1. The response on any interface shall be recorded.
Message flow
MS BSS MSC HAND REQ
HAND REQ ACK
--->
HAND ACC
--->
HAND ACC
--->
The messages from the BSSTE will be:
1. HANDOVER REQUEST on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.8, with:
Channel type = TCH Circuit identity code = A
2. HANDOVER ACCESS on the Air interface, coded as specified in GSM 04.08 [4], 9.1.14, with:
Handover reference = PAR2 Conformance Requirement
In the case of step 1, a HANDOVER REQUEST ACKNOWLEDGE message shall occur at the MSC-interface. No messages shall occur on the radio interface.
In the case of step 2, the BSS shall ignore the incoming HANDOVER ACCESS messages and no messages shall occur on any interface.
The messages from the BSS shall be:
1. HANDOVER REQUEST ACKNOWLEDGE on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.10, with:
Layer 3 information = HAND CMD (as in GSM 04.08 [4] 9.1.15) Requirement reference
GSM 04.08 [4], 3.4.4.2.2
GSM 08.08 [10], 3.1.5.2.1 and 3.1.5.3.1
8.1.3.8.1.4 Wrong physical channel Test Purpose
To verify the external handover procedure when the mobile sends the HANDOVER ACCESS message on a wrong physical channel.
Test Case Initial Setup
O&M-messages as defined by the operator or the manufacturer shall be input on the OMC-interface setting the timer T3105 to an appropriate value B, the parameter Ny1 to an appropriate value C, restricting the BSS to choose only one dedicated channel and disabling queuing on handover requests, if supported.
Description
1. A HANDOVER REQUEST message shall be input on the MSC-interface. The message shall contain an indication of the type of channel needed and the terrestrial resource to be used. The channel shall be a TCH and the terrestrial resource to be used shall be A. The response on any interface shall be recorded.
2. HANDOVER ACCESS messages shall be input on the radio interface, but on the wrong physical channel according to the HANDOVER REQUEST ACKNOWLEDGE message output in step 1. The response on any interface shall be recorded. No further messages shall be input.
Message flow
MS BSS MSC HAND REQ
HAND REQ ACK
--->
HAND ACC
--->
HAND ACC
--->
The messages from the BSSTE will be:
1. HANDOVER REQUEST on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.8, with:
Channel type = TCH Circuit identity code = A
2. HANDOVER ACCESS on the Air interface, coded as specified in GSM 04.08 [4], 9.1.14
Conformance Requirement
In the case of step 1, a HANDOVER REQUEST ACKNOWLEDGE message shall occur at the MSC-interface. No messages shall occur on the radio interface.
In the case of step 2, no message shall occur on any interface.
The messages from the BSS shall be:
1. HANDOVER REQUEST ACKNOWLEDGE on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.10, with:
Layer 3 information = HAND CMD (as in GSM 04.08 [4], 9.1.15) Requirement reference
GSM 04.08 [4], 3.4.4.4 GSM 08.08 [10], 3.1.5.2.1
8.1.3.8.1.5 No radio resources available Test Purpose
To verify the external handover procedure when there are no radio resources available.
Test Case Initial Setup
O&M-messages as defined by the operator or the manufacturer shall be input on the OMC-interface restricting the BSS to choose only one dedicated channel and disabling queuing on handover requests, if supported.
An O&M-message as defined by the operator or the manufacturer shall be input on the OMC-interface commanding the BSS to put all TCHs out of service.
Description
1. A HANDOVER REQUEST message shall be input on the MSC-interface. The message shall contain an indication of the type of channel needed and the terrestrial resource to be used. The channel shall be a TCH and the terrestrial resource to be used shall be A. The response on any interface shall be recorded.
Message flow
MS BSS MSC HAND REQ
HAND FAILURE
--->
The messages from the BSSTE will be:
1. HANDOVER REQUEST on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.8, with:
Channel type = TCH Circuit identity code = A Conformance Requirement
In the case of step 1, a HANDOVER FAILURE message shall occur on the MSC-interface with the cause value: "No radio resource available".
The messages from the BSS shall be:
1. HANDOVER FAILURE on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.16 Cause = "No radio resource available"
Requirement reference GSM 08.08 [10], 3.1.5.2.2
8.1.3.8.1.6 Clear Command from the MSC Test Purpose
To verify the external handover procedure when the MSC sends a CLEAR COMMAND before the mobile has completed the handover.
Test Case Initial Setup
O&M-messages as defined by the operator or the manufacturer shall be input on the OMC-interface setting the timer T3105 to an appropriate value B, the parameter Ny1 to an appropriate value C, restricting the BSS to choose only one dedicated channel and disabling queuing on handover requests, if supported.
Description
1. A HANDOVER REQUEST message shall be input on the MSC-interface. The message shall contain an indication of the type of channel needed and the terrestrial resource to be used. The channel shall be a TCH and the terrestrial resource to be used shall be A. The response on any interface shall be recorded.
2. After the HANDOVER REQUEST ACKNOWLEDGE message from the BSS, a CLEAR COMMAND message with the cause value "call control" shall be input on the MSC-interface. The response on any interface shall be recorded.
Message flow
MS BSS MSC HAND REQ
HAND REQ ACK
--->
CLEAR COMMAND
CLEAR COMPLETE
--->
The messages from the BSSTE will be:
1. HANDOVER REQUEST on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.8, with:
Channel type = TCH Circuit identity code = A
2. CLEAR COMMAND on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.21 Cause = as in text
Conformance Requirement
In the case of step 1, a HANDOVER REQUEST ACKNOWLEDGE message shall occur at the MSC-interface. No messages shall occur on the radio interface.
In the case of step 2, a CLEAR COMPLETE message shall occur on the MSC-interface.
The messages from the BSS shall be:
1. HANDOVER REQUEST ACKNOWLEDGE on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.10, with:
Layer 3 information = HAND CMD (as in GSM 04.08 [4], 9.1.15)
2. CLEAR COMPLETE on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.22 Requirement reference
GSM 08.08 [10], 3.1.5.3.1 and 3.1.5.3.2
8.1.3.8.1.7 No terrestrial resource available Test Purpose
To verify the external handover procedure when there are no terrestrial resources available.
Test Case Initial Setup
O&M-messages as defined by the operator or the manufacturer shall be input on the OMC-interface restricting the BSS to choose only one dedicated channel and disabling queuing on handover requests, if supported.
An O&M-message as defined by the operator or the manufacturer shall be input on the OMC-interface commanding the BSS to block the terrestrial resource A.
Description
1. A HANDOVER REQUEST message shall be input on the MSC-interface. The message shall contain an indication of the type of channel needed and the terrestrial resource to be used. The channel shall be a TCH and the terrestrial resource to be used shall be A. The response on any interface shall be recorded.
Message flow
MS BSS MSC HAND REQ
HAND FAILURE
--->
BLOCK
--->
The messages from the BSSTE will be:
1. HANDOVER REQUEST on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.8, with:
Channel type = TCH Circuit identity code = A Conformance Requirement
In the case of step 1, a HANDOVER FAILURE message shall occur on the MSC-interface with the cause value: " Requested terrestrial resource unavailable". A single global BLOCK message shall be sent for that concerned terrestrial circuit.
The messages from the BSS shall be:
1. HANDOVER FAILURE on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.16 Cause = " Requested terrestrial resource unavailable"
1. BLOCK on the A-interface, coded as specified in GSM 08.08 [10], 3.2.1.4 CIC = A
Cause = "Requested terrestrial resource unavailable"
Requirement reference
GSM 08.08 [10], 3.1.2.2 and 3.1.5.2.3
8.1.3.8.1.8 Handover - CLM2 Test Purpose
Before a MSC controlled Handover is started the MSC gets the Classmark Information from the MS proceeding the Classmark Interrogation Procedure. The HANDOVER REQUEST message is sent by the MSC with "Classmark Information 2 " element and a different encryption algorithm. The BSS shall choose the appropriate algorithm and inform the MSC about the selection.
Test Case Initial Setup
Set up a dedicated resource between Um-interface and A-interface and proceed the Classmark Interrogation procedure.
Description
1. The BSSTE sends a HANDOVER REQUEST message on the A-interface. The response on any interface shall be recorded.
MS BSS MSC HANDOVER REQ
HANDOVER REQUEST ACK --->
The messages from the BSSTE will be:
1. HANDOVER REQUEST - GSM 08.08 [10], 3.2.1.8 Encryption information
Classmark information 2 Conformance Requirements
In case of step 1, a HANDOVER REQUEST ACKNOWLEDGE message shall occur on the A-interface.
The messages from the BSS shall be:
1. HANDOVER REQUEST ACKNOWLEDGE - GSM 08.08 [10], 3.2.1.10 Chosen encryption algorithm
Requirement reference GSM 04.08 [4], 3.4.4 GSM 08.08 [10], 3.1.5
8.1.3.8.1.9 Handover - CLM2 and CLM3 Test Purpose
Before a MSC controlled Handover is started the MSC gets the Classmark Information from the MS proceeding the Classmark Interrogation Procedure. The HANDOVER REQUEST message is sent by the MSC with "Classmark Information 2" and "Classmark Information 3" element and a different encryption algorithm. The BSS shall choose the appropriate algorithm and inform the MSC about the selection.
Test Case Initial Setup
Set up a dedicated resource between Um-interface and A-interface and proceed the Classmark Interrogation procedure.
Description
1. The BSSTE sends a HANDOVER REQUEST message on the A-interface. The response on any interface shall be recorded.
MS BSS MSC HANDOVER REQ
HANDOVER REQUEST ACK --->
The messages from the BSSTE will be:
1. HANDOVER REQUEST - GSM 08.08 [10], 3.2.1.8 Encryption information
Classmark information 2 Classmark information 3 Conformance Requirements
In case of step 1, a HANDOVER REQUEST ACKNOWLEDGE message shall occur on the A-interface.
The messages from the BSS shall be:
1. HANDOVER REQUEST ACKNOWLEDGE - GSM 08.08 [10], 3.2.1.10 Chosen encryption algorithm
Requirement reference GSM 04.08 [4], 3.4.4 GSM 08.08 [10], 3.1.5
8.1.3.8.2 Synchronized network Test Purpose
NOTE: All test specified for the Non-synchronized case also apply for Synchronized, Pseudo-synchronized and Pre- synchronized Networks.
However, it should be mentioned that only 4 Handover Access Information messages will be transmitted by the BSSTE and that no Physical Information messages will be transmitted by the BTS.
For further information see:
GSM 04.08 [4], 3.4.4.2.1 GSM 04.08 [4], 3.4.4.2.3 GSM 04.08 [4], 3.4.4.2.4