Huawei a Over TDM Test Case

Huawei A over TDM Test case

华为机密，未经许可不得扩散 1




Content

Content ........................................................................................................................ 1

T01 Basic Normal Function Acceptance .......................................................................... 2

T01-01 Location Update .....................................................................................................................2

T01-02 Short Message Handling ........................................................................................................4

T01-03 Block and Unblock .................................................................................................................7

T01-04 Reset ......................................................................................................................................8

T01-05 Basic Call ...............................................................................................................................9

T01-06 Handover..............................................................................................................................15

T01-07 Cipher and Authentication ....................................................................................................16

T02 Enhanced Function Acceptance .............................................................................. 19

T02-01 AMR .....................................................................................................................................19



T01 Basic Normal Function Acceptance

T01-01 Location Update

T01-0101 First Location Update

Objective

To test that the location update procedure after the MS switch on is normal..

References

3GPP 48.008 section 9.2.13/9.2.15 & 3GPP 48.008 section 3.2.1.32 & GSM 11.23 section

11.2.3.1.

Prerequisites

Call can proceed in the system normally.

There is no location information of the testing MS in the VLR.

MSC requires authentication and cipher mode setting procedure be executed while location updating

Procedure Expected Result

1. Trace the Signaling procedure in the A

interface；

Tracing is enabled normally.

2. Switch on the testing MS. Verify that MS can camp on the tested cell successfully, and the exact signal procedure can be observed in the A interface.

Message Sequence

Direction Observation Point

BSC MSC Layer n-2 Layer n-1 Layer n

BSC-MSC SCCP:

CR( Connection Request)

BSSMAP: Complete

Layer 3 Information

MM:Locate Update Request

(Location Updating Type = IMSI attach)

MSC-BSC SCCP: CC ( Connection Confirm)

MSC-BSC SCCP: DT1 MM: Authentication Request

BSC-MSC SCCP: DT1 MM: Authentication Response

MSC-BSC SCCP: DT1 BSSMAP: Cipher Mode Command

BSC-MSC SCCP: DT1 BSSMAP: Cipher Mode Complete

MSC-BSC SCCP: DT1 MM: Location Update Accept

BSC-MSC SCCP: DT1 MM:TMSI Reallocation Complete

MSC-BSC SCCP: DT1 BSSMAP: Clear



Command (cause = call control)

BSC-MSC SCCP: DT1 BSSMAP: Clear Complete

MSC-BSC SCCP: N_DISC_IND

BSC-MSC SCCP: N_CLEAR_SCCP_CC_IND

Remarks

After the MS powered on, a location update procedure is needed. And the authentication, cipher mode setting, TMSI reallocation procedures may be also needed according to the data configuration in MSC.

T01-0102 IMSI Detach

Objective

Check the process of IMSI detach.

References

3GPP 48.008 section 9.2.13/9.2.15 & 3GPP 48.008 section 3.2.1.32 & GSM 11.23 section

11.2.3.1

Prerequisites

MS has performed successful location update;

MSC requires authentication and cipher mode setting procedure be executed while location updating.



interface；


2. Switch off the MS; IMSI DETACH INDICATION message included in COMPLETE LAYER 3 INFORMATION Message can be seen in the A interface.

Message Sequence



BSC-MSC SCCP: CR( Connection Request)

BSSMAP: Complete Layer 3 Information

MM: IMSI Detach Indication

MSC-BSC SCCP: CC ( Connection



Confirm)

MSC-BSC SCCP: DT1 BSSMAP: Clear Command(cause =

call control)


Remarks

None.

T01-02 Short Message Handling

T01-0201 MS sends point-to-point short message

Objective

To test whether MS can send point-to-point short message normally.

References

3GPP TS 23.039, 23.040 and 24.011

Prerequisites

BSC、MSC and HLR system are running normally;

MS supports SMS, and keep MS as idle status;



interface；


2. MS transmit a short message to another

MS, the message should be 1 character long, observe the signal procedure in A interface;

The short message is sent successfully;

3. MS transmit a short message to another

MS, the message should be 140 character long, observe the signal procedure in A interface;


4. MS transmit a short message to another MS, the message should be arbitrary long, observe the signal procedure in A interface;


Message Sequence





BSC-MSC SCCP: CR BSSMAP: Complete Layer 3 Information

RR:CM service Request

MSC-BSC SCCP: CC





MSC-BSC SCCP: DT1 MM: TMSI Reallocation Command


BSC-MSC SCCP: DT1 CM: CP-DATA SM: RP DATA

MSC-BSC SCCP: DT1 CM: CP ACK

MSC-BSC SCCP: DT1 CM: CP-DATA SM: RP ACK

BSC-MSC SCCP: DT1 CM: CP ACK

MSC-BSC SCCP: DT1 BSSMAP: Clear Command(cause = call

control)




Remarks

Service Access Point Identifier (SAPI) indicates the point which the data link layer provides services to layer 3. The SAP with SAPI equals to 0 is used to transfer Call Control signaling,

Mobility Management signaling and Radio Resource Management signaling; SAP with SAPI equals to 3 is used to Short Message Service. All other SAPIs are reserved.

T01-0202 MS receives point-to-point short message

Objective

To test whether MS can receive point-to-point short message normally

References

3GPP TS 23.039, 23.040 and 24.011

Prerequisites

BSC、MSC and HLR system are running normally;

MS supports SMS, and keep MS as idle status;





interface；


2. Another MS transmit a short message to tested MS, the message should be 1

character long, observe the signal procedure in A interface;

The short message is received successfully;

3. Another MS transmit a short message to tested MS, the message should be 140

character long, observe the signal procedure in A interface;

The short message is received successfully;

4. Another MS transmit a short message to tested MS, the message should be arbitrary long, observe the signal procedure in A interface;

When the short message is longer than 140 characters, the message is separated into several pages.

Message Sequence



MSC-BSC SCCP: UDT BSSMAP: Paging

BSC-MSC SCCP: CR BSSMAP: Complete Layer 3 Information

RR: Paging Response

MSC-BSC SCCP: CC





MSC-BSC SCCP: DT1 MM: TMSI Reallocation Command


BSC-MSC SCCP: DT1 CM: CP-DATA SM: RP DATA

MSC-BSC SCCP: DT1 CM: CP ACK

MSC-BSC SCCP: DT1 CM: CP-DATA SM: RP ACK

BSC-MSC SCCP: DT1 CM: CP ACK

MSC-BSC SCCP: DT1 BSSMAP: Clear Command(cause = call

control)




Remarks

None.



T01-03 Block and Unblock

T01-0301 BSC Originate blocking a single circuit and then unblock it

Objective

To test whether MSC can block and unblock a circuit normally.

References

3GPP TS 48.008 sections 3.1.2

Prerequisites

Communication status is normal in the A interface;

The circuit used in the test (refereed to designated circuit in the following description) is in normal condition;



interface；


2. In BSC, choose an idle circuit and block it;

The circuit is blocked successfully;

3. Observe the circuit state from MSC side; The circuit state in MSC side was ”REMOTE BLOCKED”;

4. In BSC, unblock the same blocked circuit;

The circuit is unblocked successfully;

5. Observe the circuit state from MSC side again;

The circuit state in MSC side was ”IDLE”;

Message Sequence



BSC-MSC SCCP: UDT BSSMAP: Block (cause = O&M intervention)

MSC-BSC SCCP: UDT BSSMAP: Block Acknowledge

(Circuit Identity Code)

MSC-BSC SCCP: UDT BSSMAP: Unblock

BSC-MSC SCCP: UDT BSSMAP:Unblocking Acknowledge

Remarks

The block & unblock procedure is used by the BSS to inform the MSC of availability of certain terrestrial circuit



T01-04 Reset

T01-0401 MSC reset Circuit with call established

Objective

To test whether the call will be cleared after a reset originated by MSC.

References

3GPP TS 48.008 section 3.1.4.2

Prerequisites


Call can be established normally;



interface；

Tracing is enabled normally;

2. Establish a MOC; The call is established successfully;

3. In BSC, find out the circuit number occupied by the call, and reset the circuit from the MSC side;

Reset relevant signal procedure can be observed in the A interface

4. Verify the connection resource is cleared;

The call is cleared normally;

5. Verify the circuit occupied by the call returns to idle state;

The circuit returned to idle state;

Message Sequence



… Call Establish Procedure…

MSC-BSC SCCP: UDT BSSMAP: Reset Circuit (cause = O&M intervention)

MSC-BSC SCCP: UDT BSSMAP: Clear Command

BSC-MSC SCCP: UDT BSSMAP: Clear Complete



BSC-MSC SCCP: UDT BSSMAP: Reset Circuit Acknowledge



Remarks

None.

T01-05 Basic Call

T01-0501 MS1 to MS2 call, B-side clears

Objective

To verify normal mobile to mobile call procedure, when B-side clears

References

3GPP TS 48.008

Prerequisites

GSM system is running normally;



interface；


2. Establish a call from MS1 to MS2; MS1 receives a ring tone, MS2 alerts, connection of speech channel established;

3. MS2 terminate the Call; The call was cleared properly after MS2 clears, and relevant messages can be observed in the A interface;

Message Sequence



BSC-MSC(MS1) SCCP: CR BSSMAP:Complete Layer 3 Information

MM: CM Service Request

MSC-BSC(MS1) SCCP: CC

MSC-BSC(MS1) SCCP: DT1 MM: CM Service Accept

MSC-BSC(MS1) SCCP: DT1 MM: Authentication Request

BSC-MSC(MS1) SCCP: DT1 MM: Authentication Response

MSC-BSC(MS1) SCCP: DT1 BSSMAP: Cipher Mode Command

BSC-MSC(MS1)

SCCP: DT1 BSSMAP: Cipher Mode Complete (Chosen Enc. Algorithm)

MSC-BSC(MS1) SCCP: DT1 MM: TMSI Reallocation Command

BSC-MSC(MS1) SCCP: DT1 CC: Setup

BSC-MSC(MS1) SCCP: DT1 MM: TMSI Reallocation Complete

MSC-BSC(MS1) SCCP: DT1 CC: Call Proceeding(Bearer



Capability)

MSC-BSC(MS2) SCCP: UDT BSSMAP: Paging

MSC-BSC(MS1) SCCP: DT1 BSSMAP: Assignment Request (Channel Type、Priority、CIC、DL DTX Flag)

BSC-MSC(MS1) SCCP: DT1 BSSMAP: Assignment Complete (RR Cause = normal event、Chosen channel、Circuit Pool、Speech

Version)


RR: Paging Response(Mobile station classmark 2、Mobile Identity)




BSC-MSC(MS2) SCCP: DT1 BSSMAP: Cipher Mode Complete



MSC-BSC(MS2) SCCP: DT1 CC: Setup(Bearer Capability、Calling

Party BCD Nr)

BSC-MSC(MS2) SCCP: DT1 CC: Call Confirmed

MSC-BSC(MS2) SCCP: DT1 BSSMAP: Assignment Request

BSC-MSC(MS2) SCCP: DT1 BSSMAP: Assignment Complete

BSC-MSC(MS2) SCCP: DT1 CC: Alerting

MSC-BSC(MS1) SCCP: DT1 CC: Alerting(Progress Identifier)

BSC-MSC(MS2) SCCP: DT1 CC: Connect

MSC-BSC(MS1) SCCP: DT1 CC: Connect(Connected Number)

BSC-MSC(MS1) SCCP: DT1 CC: Connect Acknowledge

MSC-BSC(MS2) SCCP: DT1 CC: Connect Acknowledge

... Talking ... BSC-MSC(MS2) SCCP: DT1 CC: Disconnect(Cause = normal

clearing )

MSC-BSC(MS2) SCCP: DT1 CC: Release(Cause = normal clearing )

MSC-BSC(MS1) SCCP: DT1 CC: Disconnect

BSC-MSC(MS2) SCCP: DT1 CC: Release Complete

BSC-MSC(MS1) SCCP: DT1 CC: Release

MSC-BSC(MS1) SCCP: DT1 CC: Release Complete (cause = normal clearing)

MSC-BSC(MS2) SCCP: DT1 BSSMAP: Clear Command (cause = call control)

BSC-MSC(MS2) SCCP: DT1 BSSMAP: Clear Complete

MSC-BSC(MS2) SCCP: N_DISC_IND

BSC-MSC(MS2) SCCP: N_CLEAR_SCCP_CC_IND







Remarks

None.

T01-0502 MS1 to MS2 call, MS2 Does not Answer

Objective

To verify exact network behavior in case that B-side does not answer.

References

3GPP TS 48.008

Prerequisites


Call can be established normally;



interface；


2. Establish a call from MS1 to MS2; MS1 receives a ring tone, MS2 alerts;

3. MS2 does not answer; After some time MS1 changes to the busy tone and the call will be released. Relevant

messages can be observed in the A interface;

Message Sequence










BSC-MSC(MS1)





MSC-BSC(MS1) SCCP: DT1 CC: Call Proceeding(Bearer



Capability)


MSC-BSC(MS1) SCCP: DT1 BSSMAP: Assignment Request (Channel Type、Priority、CIC、DL DTX Flag)

BSC-MSC(MS1) SCCP: DT1 BSSMAP: Assignment Complete (RR Cause = normal event、Chosen channel、Circuit Pool、Speech

Version)










Party BCD Nr)






BSC-MSC(MS2) SCCP: DT1 CC: Disconnect(Cause = user alerting, no answer )







MSC-BSC(MS1) SCCP: DT1 CC: Disconnect(Cause = user alerting, no answer)







Remarks

None.



T01-0503 MS1 to MS2 call, A_side Clears

Objective

To verify normal mobile to mobile call procedure, when A-side clears

References

3GPP TS 48.008

Prerequisites




interface；


2. Establish a call from MS1 to MS2; MS1 receives a ring tone, MS2 alerts, connection of speech channel established;

3. MS1 terminate the Call; The call was cleared properly after MS1 clears, and relevant messages can be observed in the A interface;

Message Sequence










BSC-MSC(MS1)





MSC-BSC(MS1) SCCP: DT1 CC: Call Proceeding(Bearer Capability)


MSC-BSC(MS1) SCCP: DT1 BSSMAP: Assignment Request (Channel Type、Priority、

CIC、DL DTX Flag)

BSC-MSC(MS1) SCCP: DT1 BSSMAP: Assignment Complete (RR Cause = normal event、Chosen channel、



Circuit Pool、Speech

Version)










Party BCD Nr)






BSC-MSC(MS2) SCCP: DT1 CC: Connect

MSC-BSC(MS1) SCCP: DT1 CC: Connect(Connected Number)

BSC-MSC(MS1) SCCP: DT1 CC: Connect Acknowledge

MSC-BSC(MS2) SCCP: DT1 CC: Connect Acknowledge

... Talking ...

BSC-MSC(MS1) SCCP: DT1 CC: Disconnect(Cause = normal clearing )


MSC-BSC(MS2) SCCP: DT1 CC: Disconnect












Remarks

None.



T01-06 Handover

T01-0601 Internal inter-cell handover

Objective

To test whether inter-cell handover procedure is normal.

References

3GPP TS 48.008 section 3.1.7

Prerequisites


Two cells (CELL1 and CELL2, MS handover from CELL1 to CELL2) belong to one BSC and configured as neighbor cells;

Normal call and handover between them can be carried out.



interface；Trace the Signaling procedure

in the A interface;


2. Make a MOC in CELL1; The call is established successfully;

3. In BSC, make handover easily to

happen, for example, set “DL quality Thresh” to 0;

The configuration is OK;

4. Observe the timeslot, frequency and CGI showing on the MS, observe message traced in A interface.

MS can show the right information of frequency, timeslot and CGI( belong to CELL2 ), HANDOVER PERFORMED message can be observed through A-interface;

Message Sequence



BSC-MSC SCCP: DT1 BSSMAP: Handover Performed

(cause、Cell Identifier、Chosen Channel、Speech

Version)

Remarks

The Purpose of the handover procedure is to completely modify the channels allocated to the mobile station in order to supply continuous coverage and better conversation. Internal inter-cell handover occurs between channels pertaining to different cells of the same BSS.

Because handover decision is performed by BSC, so most messages are focus in A-bis

and Um interface, there’s only HANDOVER PERFORMED message can be observed in A



interface.

Additionally, in order to trigger the handover, you can do force handover through BTS.

T01-07 Cipher and Authentication

T01-0701 Authentication and Encryption in Location Update(A5/1)

Objective

To verify the authentication and encryption procedure in location update

References

3GPP 24.008 section 4.3.24/4.7.1.2 & 3GPP 24.008 section 4.7.7/10.5.12/10.5.5.3

Prerequisites


Enable the A5/1 encryption algorithm and the authentication function of the MSC side;

On BSC, choose A5/ to be used for tested cell;


1. Enable A interface tracing function on BSC;

The tracing is enabled successfully.

2. Restart the VLR of the MSC or clear the

test data from the VLR to ensure that no data about the test MS exists in the VLR.

The operation is successful.

3. Insert the SIM card into the test MS and power on the MS in the tested cell.

The test MS accesses the network normally.

4. View the messages traced on the A interfaces.

The messages are normally traced on the interfaces. The corresponding location update, authentication, and encryption

messages are traced on the A interface.

Message Sequence





MM: Locate Update Request (Location Updating Type = IMSI attach)







BSC-MSC SCCP: DT1 BSSMAP: Cipher Mode Complete(A5/1)



MSC-BSC SCCP: DT1 BSSMAP: Clear Command (cause = call control)




Remarks

Consult with the customer about the MSC configuration in prerequisite 3.

T01-0702 Calling/Called Procedure Authentication Encryption (A5/1)

Objective

To verify the authentication and encryption procedure in calling/called procedure

References

3GPP 24.008 section 4.3.24/4.7.1.2 & 3GPP 24.008 section 4.7.7/10.5.12/10.5.5.3

Prerequisites


Enable the A5/1 encryption algorithm and the authentication function of the MSC side;

BSC is configured with two cells: Cell 1 and Cell 2. The cells run normally;

On BSC, choose A5/1 to be used for tested cell;




1. Enable A interface tracing function on BSC;

The tracing is enabled successfully.

2. The calling MS accesses the network in Cell1 and the called MS accesses the network in Cell2. Use the calling MS to call the called MS and hold the call.

The call is set up successfully and the conversation is normal.

3. View the messages traced on the A interfaces.

The messages of the normal calling/called procedure are traced on the interfaces. The authentication encryption messages can be

observed on the A interface of the caller and the called. The encryption algorithm in the encryption completion message is A5/1.

Message Sequence





MM: Locate Update Request (Location Updating Type = IMSI attach)





BSC-MSC SCCP: DT1 BSSMAP: Cipher Mode Complete(A5/1)



MSC-BSC SCCP: DT1 BSSMAP: Clear Command (cause = call control)




Remarks

Consult with the customer about the MSC configuration in prerequisite 3.



T02 Enhanced Function Acceptance

T02-01 AMR

T02-0101 Successful AMR mobile terminating call

Objective

To verify that it is possible to perform a mobile terminating call with Speech Version 3(AMR).

References

3GPP 48.008 section 3.2.1&3.2.2 and 3GPP TS 24.008 section 10.5.4.5 and 3GPP TS 46.076

Prerequisites


Configure MSC support AMR;

Configure BSC support AMR;

MS supports AMR;



interface；Trace the Signaling procedure

in the A interface;


2. Establish a MTC to the tested MS; The call is established successfully, and Speech Version IEs are included correctly in the A interface message;

Message Sequence



BSC-MSC SCCP: DT1 BSSMAP:Paging

BSC-MSC SCCP: CR BSSMAP:Complete Layer 3 Information






MSC-BSC SCCP: DT1 CC: Setup(Bearer Capability 、 Calling

Party BCD Nr)

BSC-MSC SCCP: DT1 CC: Call Confirmed

MSC-BSC SCCP: DT1 BSSMAP: Assignment Request(Channel Type IE, permitted speech versions)

BSC-MSC SCCP: DT1 BSSMAP: Assignment Complete(Speech version = GSM Speech full rate version 3)

BSC-MSC SCCP: DT1 CC: Connect



MSC-BSC SCCP: DT1 CC: Connect(Connected Number)

Remarks

In order to optimise the test coverage it is recommended to perform this test case with Full Rate V3. If it is not possible to use this speech version, alternatives can be used to suit the available equipment.

Huawei a Over TDM Test Case

Documents