Acceptance Test Cases for VIP-SGSN

Acceptance Manual

HUAWEI SGSN9810 Serving GPRS Support Node

Table of ContentsTable of ContentsiPart II Two Operation Guide1T01 Hardware1T01-01 Hardware1T01-02 Power-on Acceptance Items4T02 Mobility Management5T02-01 Attach5T02-02 Detach8T02-03 Routing Area Update (RAU)10T03 Security Management12T03-01 Authentication12T03-02 Subscriber Data and Signaling Encryption13T03-03 Data Integrality15T04 Subscriber Data Management16T04-01 Inserting Mobile Subscriber Data16T04-02 Deleting Mobile Subscriber Data17T04-03 Modifying Mobile Subscriber Data18T05 Session Management19T05-01 PDP Context Activation19T05-02 PDP Context Modification21T05-03 PDP Context Deactivation22T05-04 PDP Context Preservation24T06 Charging Function25T06-01 S-CDR Generation25T06-02 S-CDR Temporary Storage26T06-03 M-CDR Generation27T06-04 Configuration of Sending CDRs to CG27T06-05 Configuration in Festivals, Weeks, and Tariff Periods28T07 QoS and Flow Management31T07-01 QoS Service Bearer of Background Type31T07-02 QoS Service Bearer of Interactive Type32T07-03 QoS Service Bearer of Streaming Type33T07-04 Resource Reserve34T08 Reliability Function35T08-01 Board Lock and System Shutdown35T08-02 Board Redundancy Backup, Automatic Fault Detection and Self Healing36T08-03 Redundancy Networking40T09 Operation and Maintenance Function44T09-01 Alarm Management44T09-02 Equipment Management48T09-03 Security Management52T10 Iu-PS Interface54T10-01 RAB Management54T10-02 Iu Connection Management55T11 Path Management56T11-01 Path Management56T12 2G/3G Switchover57T12-01 Inter-SGSN 2G/3G Switchover57T12-02 Inter-SGSN 3G/2G Switchover59T12-03 Switchover Between Authentication Triplet and Quintuple61T13 Tracing Management62T13-01 Subscriber Tracing62T13-02 Interface Tracing63T14 SS7 OVER IP66T14-01 Gs Interface Test66T15 Gs Interface68T15-01 Initiating GPRS Detach from MSC/VLR68T15-02 CS Paging70T16 ODB72T16-01 Packet Service Barring72T17 Secondary PDP Context Activation73T17-01 Secondary PDP Context Activation73T18 Iu Over IP74T18-01 Iu Over IP74T19 SSH75T19-01 SSH75

Acceptance Test Cases----SGSNT01 HardwareT01-01 HardwareT01-0101 BoardObjectiveTo verify the board installation.

Serial number of test networking diagram

Prerequisites1. The related cabinets are power-off.2. The boards to be verified are installed in the cabinets.

Test procedureExpected results

3. Open the door of the cabinet.The cabinet door can be opened smoothly.

4. Check the positions, quantity, and types of the boards in the cabinet.The positions, quantity, and types of the boards in the cabinet comply with the system configuration.

5. Check the settings of the DIP switches on the UEPI and UTPI boards.The settings of the DIP switches on the UEPI and UTPI boards are correct.

6. Check the settings of the DIP switches on the UBIU boards.The settings of the DIP switches on the UBIU boards are correct.

7. Close the door of the cabinet.The cabinet door can be closed smoothly.

Test descriptionNone

T01-0102 Network CablesObjectiveTo verify the installation of the SGSN network cables.


Prerequisites


8. Check the connection of the network cable.The network cables are well connected.

9. Check if the network cable is tied onto the cabinet.The network cable is tied up to the cabinet.

10. Check the labels on both ends of the network cable.Both ends of the network cable are attached with correct labels.


T01-0103 Power Cables, Grounding Cables, and Protection Grounding CablesObjectiveTo verify the settings of the power cables, grounding cables, and protection grounding cables.


Prerequisites


11. Check if the of power cables and grounding cables are connected through the DC distribution cabinet.The DC distribution cabinet is used to connect the power cables and grounding cables.

12. Check if all the power cables are reliably connected. Check if the polarities of the power cables are correct. In addition, each cable must be a whole piece without any joint.All the power cables are reliably connected. The polarities of the power cables are correct. Each cable is a whole piece without any joint.

13. Check if the cables connecting the DC distribution cabinet and SGSN are proved by Huawei.The cables connecting the DC distribution cabinet and SGSN are proved by Huawei.

14. If the power cables and grounding cables are laid inside racks, check if they run from the top of the cabinets along the sides of the cabinets. Check if the cabling is straight and the binding is tight.The power cables and grounding cables run from the top of the cabinets and along the sides of the cabinets. The cabling is straight and the binding is tight.

15. Check if the power cables and the grounding cables outside the racks are laid separately from other cables.The power cables and the grounding cables outside the racks are laid separately from other cables.

16. If copper lugs are used at both ends of the power cables and grounding cables, make sure no naked cables or lug stems are exposed.No copper lugs, naked power cables or naked grounding cables are exposed.

17. Check the connections of the grounding cables and power cables.The connections of the grounding cables and power cables are correct.

18. Check the copper lug weld joints on the grounding cables and power cables.The copper lug weld joints on the grounding cables and power cables are in good condition.

19. Check the labels at both ends of each power cable and grounding cable.Both ends of a power cable or grounding cable are attached with labels.


T01-0104 Trunk CablesObjectiveTo verify the trunk cable installation in the SGSN.


Prerequisites


20. Check if any trunk cable is damaged or broken.No trunk cable is broken or damaged. The connector of the trunk cable is in good condition.

21. Check if the trunk cable is tied onto the cabinet.The trunk cable is correctly and tightly tied onto the cabinet.

22. Check the excessive part of the trunk cable at the cable distribution frame.Margins are left at turns of each trunk cable at the distribution frame. The margins comply with the operator's requirement.

23. Check the binding of the cable.The trunk cables are bound separately from the power cables in the grooves.

24. Check the arrangement of the cables.The trunk cables are arranged in proper order on the distribution frame. Any faulty cable can be identified easily according to its number label.

25. Check the wiring of the cable in the wiring channel.The trunk cables inside the cabinets are in the wiring grooves.

26. Check the position and length of the cable.The trunk cables are in correct positions and proper length.

27. Check the labels at both ends of the cable.Both ends of each trunk cable are attached with legible labels.


T01-0105 Optical FibersObjectiveTo verify the installation of the SGSN fibers.


Prerequisites


28. Check the binding condition of the fiber.The fiber is not bound tight at turns and the fiber pairs are bound in good order.

29. Check the curvature radius of the fiber.The curvature radius of each fiber is greater than 3.5 cm.

30. Check the protection of the fiber.The fiber laid outside the cabinet is protected by corrugated plastic tubes. Both ends of the corrugated plastic tube are bound and fixed.

31. Check the labels on the fiber.The labels are legible and stuck to both ends of each optical fiber.


T01-0106 Internal Signal CablesObjectiveTo verify the installation of the SGSN internal signal cables.


Prerequisites


32. Check the connections between the internal clock cable and the serial port cable.The internal clock cable and serial port cable are well connected.

33. Check the binding of the internal clock cable or serial port cable on the cabinet.The internal clock cables and serial port cables are correctly tied up to the cabinet.

34. Check the labels on both ends of the internal clock cable or serial port cable.Both ends of each internal clock cable or serial port cable are attached with legible labels.


T01-02 Power-on Acceptance ItemsT01-0201 Power Distribution BoxObjectiveTo verify the installation of the SGSN power distribution boxes.


PrerequisitesThe input and output of the power distribution box in each cabinet are normal.


35. Check the power supply of the power distribution box.The power distribution box normally supplies power to the subracks.

36. Check the output switch of the power distribution box.The output switch of the power distribution box works normally.

37. Check the mute switch on the power distribution box.If a visual and audio alarm is generated to report a fault in the cabinet power supply, the sound can be turned off by turning the mute switch.


T01-0202 FansObjectiveTo verify the fans in the fan drawer.


PrerequisitesThe fans are power-on.


38. Check the running status of the fan.The fans runs normally in a long term.

39. Check the cooling and ventilation status of the fan.The cooling status and ventilation status of the fans are normal.


T02 Mobility ManagementT02-01 AttachT02-0101 GPRS Attach Initiated by a Normal Subscriber Using IMSIObjectiveTo verify the SGSN function of GPRS attach initiated by a normal subscriber using IMSI.


Figure I

Prerequisites40. The SGSN and LMT run normally.41. The SGSN does not store the subscriber information. The execution result of DSP MMBYIMSI: IMSI="" shows that there is no such record.

42. The MS is a normal subscriber in the HLR and subscribed GPRS services.43. A subscriber trace task and Iu interface trace task are created.


44. Switch on the MS. The MS initiates a GPRS attach using IMSI.The MS is attached to the SGSN.

45. Execute DSP MMBYIMSI on the LMT to query the status of the subscriber.The subscriber is in PMM-IDLE state in the SGSN.

Test descriptionThe figure below shows the message flow:

The MS sends Attach Request (MS identity = IMSI) to the SGSN to initiate an attach. If the SGSN does not have an available authentication quintuple, the SGSN sends Send Authentication Info (imsi) to the HLR. The HLR then returns Send Authentication Info Ack with an authentication quintuple. After obtaining the authentication quintuple, the SGSN sends Authentication and Ciphering Request to the MS. The MS sends Authentication and Ciphering Response to the SGSN. The SGSN sends Update Location (SGSN Number, SGSN Address, IMSI) to the HLR. The HLR sends Insert Subscriber Data (IMSI, GPRS Subscription Data) to the SGSN. The SGSN returns Insert Subscriber Data Ack. The SGSN sends Attach Accept (P-TMSI, P-TMSI Signature to the MS). The MS sends Attach Complete to the SGSN.

T02-0102 GPRS Attach Initiated by a Normal Subsciber Using P-TMSI Switch on the MS. The MS initiates an attach by P-TMSI.The SGSN assigns a new P-TMSI for the MS to attach to the SGSN.

108. Execute DSP MMBYIMSI: IMSI="" on the LMT to query the P-TMSI of the subscriber.The P-TMSI signature is different from the one in the result in step 1.

Test description The figure below shows the message flow:

The MS sends Attach Request to the SGSN to initiate an attach procedure. The SGSN sends an authentication and encryption request to the MS, the MS then returns an authentication and encryption response. The SGSN sends Security Mode Command with encryption algorithm of UEA1 to the RNC. The RNC sends Security Mode Complete to the SGSN.

T03-03 Data IntegralityT03-0301 Data IntegralityObjectiveTo verify the SGSN function of supporting data integrality.


Figure I

Prerequisites109. The SGSN and LMT run normally.110. The SIM subscriber has subscribed GPRS services in the HLR.111. The SGSN stores the subscriber information. Execute DSP MMBYIMSI: IMSI="" on the LMT to query the information. 112. Execute SET PMM on the LMT where the NAC is YES, CIPH is YES, and CIPHALG is UEA1.113. A subscriber trace task and Iu interface trace task are created.


114. Switch on the MS. The MS initiates an attach.The MS is attached to the SGSN.


The MS sends Attach Request to the SGSN to initiate an attach procedure. The SGSN sends an authentication and encryption request to the MS, the MS then returns an authentication and encryption response. The SGSN sends Security Mode Command with encryption algorithm of UEA1 to the RNC. The RNC sends Security Mode Complete to the SGSN.

T04 Subscriber Data ManagementT04-01 Inserting Mobile Subscriber DataT04-0101 Inserting Mobile Subscriber DataObjectiveTo verify the SGSN function of inserting mobile subscriber data.


Figure I

Prerequisites115. The SGSN and LMT run normally116. The subscriber has subscribed GPRS services in the HLR.117. The SGSN does not store any subscriber information. The execution result of DSP MMBYIMSI: IMSI="" shows that there is no such record.118. A user trace task and Gr interface trace task are created.



120. Execute DSP MMBYIMSI: IMSI= on the LMT to query the subscriber data. The inserted subscriber data is displayed.


The HLR sends Inset Subscriber Data (IMSI, PS Subscription Data) to the SGSN. The SGSN returns Insert Subscriber Data Ack (IMSI) to the HLR.

T04-02 Deleting Mobile Subscriber DataT04-0201 Deleting Mobile Subscriber DataObjectiveTo verify the SGSN function of deleting mobile subscriber data.


Figure I

Prerequisites121. The SGSN and LMT run normally.122. The subscriber has subscribed GPRS services in the HLR.123. The SGSN does not store any subscriber information. The execution result of DSP MMBYIMSI: IMSI="" shows that there is no such record.124. A subscriber trace task and Gr interface trace task are created.



126. Execute DSP USPUPDP: IMSI= on the LMT to query the subscriber PS data. The inserted subscriber PS data is displayed.

127. Delete part of the subscriber PS data from the HLR.The HLR deletes the subscriber PS data.

128. Execute DSP USPUPDP: IMSI= on the LMT to query the subscriber PS data. The deleted subscriber PS data in the HLR in step 3 is also deleted in the SGSN.

Test description The figure below shows the message flow

The HLR sends Delete Subscriber Data to the SGSN. The SGSN returns Delete Subscriber Data Ack (IMSI) to the HLR.

T04-03 Modifying Mobile Subscriber DataT04-0301 Modifying Mobile Subscriber DataObjectiveTo verify the SGSN function of modifying mobile subscriber data.


Figure I

Prerequisites129. The SGSN and LMT run normally.130. {0>The subscriber has subscribed GPRS services in the HLR.

131. {0>The SGSN does not store the subscriber information. The execution result of DSP MMBYIMSI: IMSI= shows that there is no such record. The MS initiates a PDP context activation.The PDP context is activated.

144. {0> Execute DSP USPUPDP on the LMT to query the PDP context.The PDP context and address assigned to the subscriber are displayed.


The MS sends Activate PDP Context Request to the SGSN, which does not contain a PDP address. The SGSN sends Create PDP Context Request (PDP Type, APN, QoS) to the GGSN. The GGSN returns Create PDP Context Response (QoS, PDP address). The SGSN sends RAB assignment request to the RNC, the RNC returns RAB Assignment Response.

The SGSN sends Activate PDP Context Accept to the MS.

T05-0102 PDP Context Activation with a Static Address Initiated by a SubscriberObjectiveTo verify the SGSN function of supporting PDP context activation with a static address intiated by a subscriber.


Figure I

Prerequisites145. The RNC and NodeB run normally. Switch on the MS. The MS initiates an attach.The MS is attached to the WCDMA network.

151. {0> The MS initiates a PDP context activation with a static address. The PDP context is activated.

152. {0> Execute DSP USPUPDP on the LMT to query the PDP context.The PDP context is displayed.


The MS sends Activate PDP Context Request to the SGSN. The PDP address is a static address. The SGSN sends Create PDP Context Request (PDP Type, PDP address, APN, QoS) to the GGSN. The GGSN returns Create PDP Context Response (QoS). The SGSN sends RAB assignment request to the RNC, the RNC returns RAB Assignment Response.

The SGSN sends Activate PDP Context Accept to the MS.

T05-02 PDP Context ModificationT05-0201 SGSN-initiated PDP Context ModificationObjectiveTo verify the SGSN function of supporting PDP context modification initiated by the SGSN.


Figure I

Prerequisites153. The RNC and NodeB run normally. The MS initiates a PDP context activation.The PDP context is activated.

159. Modify the QOS in the subscriber data in the HLR to start a SGSN-initiated PDP context activation.The SGSN-initiated PDP context modification succeeds.


The HLR sends Insert Subscriber Data (IMSI, GPRS Subscription Data) to the SGSN after modifying the QOS in the subscriber data. The SGSN returns Insert Subscriber Data Ack. The SGSN sends Update PDP Context Request (TEID, NSAPI, QoS) to the GGSN. The GGSN returns Update PDP Context Response (TEID, QoS, Cause) to the SGSN. The SGSN initiates a PDP context modification procedure by sending Modify PDP Context Request (TI, QoS) to the MS. The MS returns Modify PDP Context Accept. The SGSN sends RAB Assignment Request (RABs To Be Setup Or Modified List) to theRNC. The RNC sends RAB Assignment Response (RABs Setup Or Modified List) to the SGSN.

T05-03 PDP Context DeactivationT05-0301 PDP Context Deactivation Initiated by a SubscriberObjectiveTo verify the SGSN function of supporting PDP context deactivation initiated by a subscriber.


Figure I

Prerequisites160. {0>The RNC and NodeB run normally. The MS initiates a PDP context activation.The PDP context is activated.

166. The MS initiates a PDP context deactivation.The PDP context is deactivated.


The MS sends Deactivate PDP Context Request (TI) to the SGSN to initiate a deactivation procedure.

The SGSN sends Delete PDP Context Request (TEID, NSAPI) to the GGSN.

The GGSN returns Delete PDP Context Response (TEID) to the SGSN. The SGSN sends Deactivate PDP Context Accept (TI) to the MS. The SGSN sends RAB Assignment Request (RABs To Be Released List) to the RNC. The RNC returns RAB Assignment Response (RABs Released List).

T05-0302 PDP Context Deactivation Initiated by SGSNObjectiveTo verify the SGSN function of supporting PDP context deactivation initiated by the SGSN.


Figure I


173. Delete the PDP data in the HLR to start a SGSN-initiated PDP context deactivation.The SGSN-initiated PDP context deactivation succeeds.


The HLR sends Delete Subscriber Data (IMSI, GPRS Subscription Data Withdraw) to the SGSN after deleting PDP data of the MS. The SGSN returns Delete Subscriber Data Ack. The SGSN sends Delete PDP Context Request (TEID, NSAPI) to the GGSN. The GGSN returns Delete PDP Context Response (TEID) to the SGSN. The SGSN sends Deactivate PDP Context Request (TI) to the MS. The MS returns Deactivate PDP Context Accept (TI) to the SGSN. The SGSN sends RAB Assignment Request (RABs To Be Released List) to the RNC. The RNC returns RAB Assignment Response (RABs Released List).

T05-04 PDP Context Preservation T05-0401 RAB ReleaseObjectiveTo verify the SGSN function of RAB release.


Figure I


181. Execute TRG RABREL on the LMT of the RNC to initiate a RAB release procedure. The RAB is released. Execute DSP USPUPDP and you can observe the PDP context is preserved.

If there is only one RAB on Iu connection, Iu connection is also released after the RAB is released.


UTRAN sends RAB Release Request to the SGSN after the RNC sends RAB release request. The SGSN sends RAB Assignment Request to the UTRAN. The UTRAN sends RAB Assignment Response to the SGSN.

T06 Charging FunctionT06-01 S-CDR GenerationT06-0101 S-CDR GenerationObjectiveTo verify the SGSN function of generating the S-CDRs.


Figure I

Prerequisites182. The SGSN and LMT run normally.183. {0>The subscriber has subscribed GPRS services in the HLR. The charging characteristic of PDP is Normal.TheTTheS-CDR generated in step 3 is displayed on the CG. The cause for CDR closing is Normal Release.


T06-02 S-CDR Temporary StorageT06-0201 S-CDR Temporary StorageObjectiveTo verify if the SGSN can temporarily store S-CDRs during the period of communication interruption with the CG and send the CDRs after the period.


Figure I

Prerequisites190. The SGSN and LMT run normally.191. {0>The subscriber has subscribed GPRS services in the HLR. The charging characteristic of PDP is Normal.Execute DSP CHGFILE on the LMT to query the CDR files on the UCDR hard disk.The number of the CDR files is 0.

195. Interrupt the communication between the SGSN and the CG, and execute DSP CHGCG.The status of the CG is communication interrupted.


197. The MS initiates a PDP context activation.The PDP context for the MS is activated.

198. The MS initiates a PDP context deactivation.The PDP context for the MS is deactivated.

199. {0> Execute DSP CHGFILE on the LMT to query the CDR files on the UCDR hard disk.The number of the CDR files is 1.

200. Resume the communication between the SGSN and the CG, and execute DSP CHGCG.The status of the CG is normal.

201. Browse the CDR through LMT of the CG.The S-CDR generated in step 5 is displayed on the CG. The cause for CDR closing is Normal Release.


T06-03 M-CDR GenerationT06-0301 M-CDR GenerationObjective{0>To verify the SGSN function of generating M-CDRs.


Figure I

Prerequisites202. The SGSN and LMT run normally.203. {0>The subscriber has subscribed GPRS services in the HLR. The charging characteristic of PDP is Normal.The subscriber has subscribed GPRS services in the HLR. 211. Execute SET CHGGA: UCR=R98, CHGVER98=GSM1215V760 on the LMT, and set the UMTS CDR version to 12.15 V7.6.0.212. The SGSN connects well with two CGs supporting 12.15 V7.6.0 CDR version. CG1 has higher level than CG2.



214. Switch off the MS. The MS initiates a detach.The MS is detached from the SGSN.

215. Browse the CDR through LMT of the CG.The M-CDR generated in step 2 is displayed on the CG1. The cause for CDR closing is Normal Release.

216. Execute DSP CHGCG to interrupt the communication between the SGSN and the CG1.The status of the CG is communication interrupted.


218. Switch off the MS. The MS initiates a detach.The MS is detached from the SGSN.

219. Browse the CDR through LMT of the CG2.The M-CDR generated in step 6 is displayed on CG2. The cause for CDR closing is Normal Release.


T06-05 Configuration in Festivals, Weeks, and Tariff PeriodsT06-0501 Configuration in Festivals and Tarrif PeriodsObjectiveTo verify the SGSN function of supporting configuration in festivals and tariff periods and recording correct charging information in the CDR.


Figure I

Prerequisites220. The SGSN and LMT run normally.221. {0>The subscriber has subscribed GPRS services in the HLR. The charging characteristic of PDP is Normal.2. The subscriber has subscribed GPRS services in the HLR. The charging characteristic of PDP is Normal.The subscriber has subscribed GPRS services in the HLR. The charging characteristic of PDP is Normal.The RNC and NodeB systems run normally.The RNC and NodeB systems run normally.The RNC and NodeB systems run normally.The RNC and NodeB systems run normally., SN=< active UGFU slot >, DIP="" to query the status of the GTP user panel.The SGSN can receive the GGSN Ping packet response and the GTP control panel is in normal status.

The SGSN can receive the GGSN Ping packet response and the GTP user panel is in normal status.

349. Execute UIN UPIU_PORT: SRN=, SN=, PN= on the LMT to allow using the active Gn and Gp ports.

Execute DSP UPIU_PORT on the LMT to query the status of the Gn and Gp ports.The new standby Gn and Gp ports are allowed to use.

The active and standby functions of Gn and Gp ports remain unchanged. The two ports are in normal status.

350. Execute PING IP: SRN=, SN=, DIP="" on the LMT to query the status of the GTP control panel.

Execute PING IP: SRN=< active UGFU subrack>, SN=< active UGFU slot >, DIP="" on the LMT to query the status of the GTP user panel.The SGSN can receive the GGSN Ping packet response and the GTP control panel is in normal status.

The SGSN can receive the GGSN Ping packet response and the GTP user panel is in normal status.


T08-0303 Ga Interface Redundancy Backup

ObjectiveTo verify the SGSN function of supporting redundancy backup of the Ga interface.


None

Prerequisites351. The SGSN and LMT run normally.352. There are active and standby UGFU/UPIU boards in the system. The active and standby Ga ports are configured on the two UPIU boards by SET UPIU_PORT command.353. The Ga interface between the SGSN and CG runs normally.


354. Execute PING: SRN=, SN=, IP="" to query the status to the CG.The SGSN can receive the CG Ping packet response and the communication to the CG is in normal status.

355. Execute INH UPIU_PORT: SRN=, SN=, PN= on the LMT to forbid using the active Ga port.

Execute DSP UPIU_PORT on the LMT to query the status of the Ga port.The active Ga port is forbidden to use.

The active and standby Ga ports change the status with each other.


357. Execute UIN UPIU_PORT: SRN=, SN=, PN= on the LMT to allow using the new standby Ga port.

Execute DSP UPIU_PORT on the LMT to query the status of the active and standby Ga ports.The new standby Ga port is allowed to use.

The active and standby functions of Ga port remain unchanged. The two ports are in normal status.



T08-0304 Iu Interface Redundancy Backup

ObjectiveTo verify the SGSN function of supporting redundancy backup of the Iu interface.


None

Prerequisites359. The SGSN and LMT run normally.360. There are active and standby UGFU/UPIU boards in the system. The active and standby Iu ports are configured on the two UPIU boards by SET UPIU_PORT command.361. The MTP3B links between the SGSN and RNC run normally.


362. Execute DSP MTP3BLNK: SRT=ALL on the LMT to query the status of the MTP3B links.The MTP3B links are in normal status.

363. Execute UIN UPIU_PORT: SRN=, SN=, PN= on the LMT to inhibit the active Iu port.

Execute DSP UPIU_PORT on the LMT to query the status of the active/standby Iu ports.The active Iu port is forbidden to use.

The active and standby Iu ports change the function with each other.


365. Execute INH UPIU_PORT: SRN=, SN=, PN= on the LMT to uninhibit the new standby Iu port.

Execute DSP UPIU_PORT on the LMT to query the status of the active/standby Iu ports.The new standby Iu port is allowed to use.

The active and standby functions of Iu port remain unchanged. The two ports are in normal status.



T08-0305 Active/Standby MTP3 Redundancy Backup

ObjectiveTo verify the SGSN function of supporting redundancy backup of the active/standby MTP3.


None

Prerequisites367. The SGSN and LMT run normally.368. There are active and standby USPU/USS7/UEPI boards in the system. The UEPI/UTPI port backup type is USS7_Share.

369. One MTP3 link connecting the SGSN and STP runs normally. The link is configured on the lower USS7 sub-board.


370. Execute DSP N7LNK: SRT=ALL on the LMT to query the status of the MTP3 link.The MTP3 link is in normal status.

371. Execute SWP BRD: SRN=, SN= on the LMT to manually switch over the two USPU boards.The switchover of the boards succeeds.

The active and standby status of the USPU boards change with each other.

372. Execute DSP N7LNK: SRT=ALL on the LMT to query the status of the MTP3 link.The MTP3 link is in normal status.

373. Switch on the 3G MS. The MS initiates an attach.The MS is attached to the SGSN.


T09 Operation and Maintenance Function

T09-01 Alarm ManagementT09-0101 Querying History AlarmsObjectiveTo verify the SGSN function of querying history alarms.

Serial number of test networking diagramNone

Prerequisites374. The SGSN system runs well.375. The LMT communicates well with the SGSN.376. If querying history fault alarms, at least one history fault alarm record must exist.377. If querying history event alarms, at least one history event alarm record must exist.


378. Execute LST ALMLOG: almtp=ALL, sortseg=ASC, cnt=1000 to query all history alarms.The command succeeds and all the history alarms are displayed.

379. Execute LST ALMLOG: almtp=ALL, alvl=, sd=, ed=, st=, et= to query alarms of the specified levels in specified time.The command succeeds and all the history alarms of the specified levels in specified time are displayed.

Test descriptionIf the number of history alarms exceeds 1000, only the early 1000 alarms are displayed.

T09-0102 Querying Active AlarmsObjectiveTo verify the SGSN function of querying active alarms.


Prerequisites380. The SGSN system runs well.381. The LMT communicates well with the SGSN.382. At least one active alarm exists in the system.


383. Execute LST ALMAF: cnt=1000 on the LMT to query active alarms.The command succeeds and all the active alarms are displayed.

384. Execute LST ALMAF: SRN=, SN= to query alarms of the specified board.The command succeeds and the active alarms of the specified board are displayed.

Test descriptionIf the number of history alarms exceeds 1000, only the early 1000 alarms are displayed.

T09-0103 Board AlarmsObjectiveTo verify the SGSN function of reporting board alarms.


Prerequisites385. The SGSN system runs well.386. The LMT communicates well with the SGSN.

387. The SGSN alarm management system is open.


388. Execute LST BRD: RS=STANDBY to query the information of standby boards.The information of standby boards is displayed.

389. Execute RST BRD: OT=BRD, SRN=, SN, BP=IO on the LMT to reset a standby board.The reset command succeeds.

390. Check if Board Fault alarms are displayed in the alarm management system.There are alarm records on the alarm management system, which are generated by the board reset in step 2.

391. Execute LST BRD: SRN=< Subrack number > SN=, BP=IO on the LMT to check if the reset board in step 2 is in normal status.The reset board in step 2 is in normal status.

If it is not in normal status, carry out this step later to ensure that the reset board is in normal status.

392. Query if the Board Fault alarms in the alarm management system are cleared.After the reset board runs normally, the Board Fault alarm is cleared.


T09-0104 Communication Between CG and SGSN InterruptedObjectiveTo verify the function of reporting the communication between CG and SGSN interrupted alarm.


Prerequisites393. The SGSN system runs well.394. The LMT communicates well with the SGSN.

395. The SGSN alarm management system is open.396. At least one CG communicates well with the SGSN.

397. Execute LST BRD: BT=UCDR, RS=ACTIVE to query the information of the UCDR board.


398. Execute DSP CHGCG: SRN=, SN= to query the communication between all CGs and the SGSN.The status of communication between all CGs and the SGSN is displayed, including the CG communicating well with the SGSN.

399. Execute INH UPIU_PORT: SRN=, SN=, PN= to inhibit the ports on the UPIU, back board of the UGFU from connecting to the CG communicating well with the SGSN.The command to inhibit the ports succeeds.

400. Execute DSP UPIU_PORT: QT=PORT, PN= to query all ports connecting to the CG.The status of the ports is forbidden to use.

401. Query if there is any alarm of Communication between the SGSN and CG Interrupted in the alarm management system.There is an alarm of Communication between the SGSN and CG Interrupted in the alarm management system.

402. Execute UIN UPIU_PORT: SRN=, SN=, PN= to uninhibit the ports on the UPIU, back board of the UGFU from connecting to the CGThe command to uninhibit the ports succeeds.

403. Execute DSP UPIU_PORT: QT=PORT, PN= to query all ports connecting to the CG.The status of the ports is able to use.

404. Query if the alarm of Communication between the SGSN and CG Interrupted in the alarm management system is cleared.The alarm of Communication between the SGSN and CG Interrupted in the alarm management system is cleared.


T09-0105 GTP-C Tunnel Path BrokenObjectiveTo verify the SGSN function of reporting the GTP-C tunnel path broken alarm.


Prerequisites405. The system runs normally and all the interfaces are in normal status.406. The HLR connected with the SGSN runs normally. The MS has subscribed GPRS services in the HLR.407. The SGSN system runs well.408. The SGSN alarm management system is open.409. Execute SET GTPPUB: PMNTM=ECHO, ECHOSIG=ON on the LMT to turn on the ECHO switch.


410. Switch on the MS. The MS initiates an attach.The MS is attached to the system.

411. The MS initiates a PDP context activation.The PDP context for the MS is activated.

412. Execute INH UPIU_PORT: SRN=, SN=, PN= to inhibit all the ports on the UPIU, back board of the UGFU from connecting to the GGSN.The command to inhibit the ports succeeds.

413. Execute DSP UPIU_PORT: QT=PORT, PN= to query the ports connecting to the GGSN.The status of the ports is forbidden to use.

414. Query if there is any alarm of GTP-C Tunnel Path Broken in the alarm management system.There is an alarm of GTP-C Tunnel Path Broken in the alarm management system.

415. Execute UIN UPIU_PORT: SRN=, SN=, PN= to uninhibit all the ports on the UPIU, back board of the UGFU from connecting to the GGSN.The command to uninhibit the ports succeeds.

416. Execute DSP UPIU_PORT: QT=PORT, PN= to query the ports connecting to the GGSN.The status of the ports is able to use.

417. Query if the alarm of GTP-C Tunnel Path Broken in the alarm management system is cleared.The alarm of GTP-C Tunnel Path Broken in the alarm management system is cleared.


T09-02 Equipment ManagementT09-0201 Querying Board StatusObjectiveTo verify the SGSN function of querying status of the boards in the SGSN system.


Prerequisites418. The SGSN system runs normally.419. The SGSN communicates well with the LMT.420. All the boards are in normal status in the system.


421. Execute LST BRD to query the information of all the boards.The information of all the boards is displayed.

422. Execute LST BRD: SRN=, SN=, BP=IO to query the information of a specified board.The information of the specified board is displayed. The operation state of the board is enable.

423. Execute RST BRD: OT=BRD, SRN=< Subrack number >, SN=< Slot number >, BP=IO to reset the board in step 2.The command to reset the board succeeds.

424. Execute LST BRD: SRN=< Subrack number >, SN=< Slot number >, BP=IO to query the information of the reset board.The information of the reset board is displayed the operation state of the board is disable.

Test descriptionThe interval between step 3 and step 4 must be short; otherwise after the board resumes working, the operation state of the board is enable.

T09-0202 Querying E1/T1 Port Status

ObjectiveTo verify the SGSN function of querying the E1/T1 port status.


Prerequisites425. The SGSN system runs well.426. The LMT communicates well with the SGSN.427. The UEPI configuration and E1/T1 cable connections are correct. The E1/T1 configuration complies with the reality.


Execute DSP UEPIUTPILNK: SRN= to query all the ports status in the specified subrack.The Information of all the E1/T1 ports in the specified subrack is displayed.


T09-0203 Querying UPIU Ports StatusObjectiveTo verify the SGSN function of querying the UPIU ports status.

Serial number of test networking diagram None.

Prerequisites428. The SGSN system runs well.429. The LMT communicates well with the SGSN.430. The active/standby UFCU, UPIU, UAIC, and UEEC boards run normally.

431. The active/standby UFCU/UPIU/UAIC boards run normally.

432. The active/standby UGFU/UPIU/UAIC/UEEC/UEFC boards run normally.


433. Execute LST UPIU_PORT to query the configuration information of all the UPIU ports.The configuration information of all the UPIU ports is displayed.

434. Execute DSP UPIU_PORT: SRN=, SN=, QT=PORT, PN= to query the status of one UPIU port.The status of the specified UPIU port is displayed.

Test descriptionNone.

T09-0204 Querying M3UA Destination entity

ObjectiveTo verify the SGSN function of querying a M3UA destination entity.


Prerequisites435. The SGSN system runs normally.

436. The LMT communicates well with the SGSN.437. The M3UA destination entity is configured in the system.


Execute DSP M3DE to query the status of all the MTP destination signaling points.The status of all the M3UA destination entity is displayed.


T09-0205 Board Reset and Switchover

ObjectiveTo verify the SGSN function of supporting board reset and switchover.

Serial number of test networking diagramNone.


439. The LMT communicates well with the SGSN.

440. The active/standby USPU boards are configured in the system441. The active/standby USPU borads meet switchover conditions.


442. Execute LST BRD: BT=USPU to query the information of all the USPU boards.The information of all the USPU boards is displayed.

443. Execute RST BRD: OT=BRD, SRN=, SN=, BP=IO to reset an active USPU board.The USPU board is reset.

444. Execute LST BRD: BT=USPU to query the information of the USPU board.The information of all the USPU boards is displayed.

After the board is reset in step 2, the active and standby functions of the board change with each other.

445. After the reset board in step 2 runs normally, execute SWP BRD: SRN=< Subrack number >, SN=< Slot number > to enter the subrack number, slot number, and switch over the USPU board. The USPU board switchover succeeds.

446. Execute LST BRD: BT=USPU to query the information of all the USPU boards.The information of all the USPU boards is displayed.

After the switchover, the active and standby functions of the swapped board change with each other again.


T09-0206 Testing GTP-C PathObjectiveTo verify the SGSN function of testing a GTP-C path.




449. The Gn interface is configured in the system.450. The Gn interface between SGSN and GGSN is normal.


451. Execute LST BRD: BT=UGTP to query the information of all the UGTP boards.The information of all the UGTP boards is displayed.

452. Execute LST BRD: SRN=, SN= to query the detailed information of a board in step 1.The information of the UGTP board indicates it is of GTP type.

If GTP type is GTPC or GTPC_GTPU, terminate the query.

If GTP type is GTPU, repeat the step until the result is GTPC or GTPC_GTPU.

453. Execute TST GTPCPATH: SRN=< Subrack number >, SN=, IPT=IPV4, PIP4="" to enter the location of the GTPC or GTPC_GTPU board in step 2 and test the communication between the specified SGSN and GGSN.If the path is in good condition, the version information of the GTP path is displayed. Otherwise, timeout is displayed.


T09-03 Security ManagementT09-0301 Operator Management

ObjectiveTo verify the SGSN function of supporting the admin to manage other operators.



455. The LMT communicates well with the SGSN. The user name for login is admin.

456. There are only two operators, admin and guest in the system.


457. Execute LST OP to query all the operators in the system.There are two operators, admin and guest in the system.

458. Execute ADD OP: op="", pwd="", cfm="", UG=Operator, DATE=NOLIMIT, TIME=NOLIMIT, WEEK=NOLIMIT to add an operator.The operator is added.

459. Execute LST OP: op="" to query the operator added in step 2.The detailed information of the new operator is displayed.

460. Select System > Exit to exit the LMT.The LMT disconnects from the SGSN.

461. Log in to the LMT using the new operator added in step 2.The login to the LMT succeeds.

462. Execute LST BRD to query the information of the boards in the system.The command succeeds and the information of all the boards is displayed.

463. Execute ADD OP: op="", pwd="", cfm="", UG=Operator, DATE=NOLIMIT, TIME=NOLIMIT, WEEK=NOLIMIT to add an operator.The command fails and prompts lack of authority.


465. Log in to the LMT using admin.The login to the LMT succeeds.

466. Execute RMV OP: op="" to remove the operator added in step 2.The command to remove the operator succeeds.

467. Execute LST OP to query the information of all the operators,The information of the operator added in step 2 is not displayed.


469. Log in to the LMT using the operator removed in step 9.The login fails and prompts the operator does not exist.

Test descriptionWhen you exit the LMT, the operation information may lose, so ensure saving the information before exit.

T09-0302 LMT Lock

ObjectiveTo verify the SGSN function of supporting the LMT lock.





472. Select System > System SettingThe System Setting dialog box pops up.

473. Select Terminal to observe the existing automatically locked time.The time can be observed.

474. Select System > Lock to lock the LMT.The LMT is locked and any operation is unavailable.

475. Press Ctrl+Alt+U and enter the password.The LMT is unlocked.

476. Select System > System SettingThe System Setting dialog box pops up.

477. Select Terminal > Automatically locked, and set the automatically locked time to one minute. The setting of automatically locked time succeeds.

478. Carry out no operation on the LMT for one minute.The LMT is automatically locked.

479. Press Ctrl+Alt+U and enter the password.The LMT is unlocked.

480. Select Terminal to set the automatically locked time the same as the time observed in step 2The setting succeeds.


T09-0303 Querying Operation LogsObjectiveTo verify the SGSN function of querying operation logs on the LMT.





483. Execute LSTOPTLOG to query the current operation logs.The current operation logs are displayed.

484. Execute LST OPTLOG: SD=, ST=, ED=, ET= to query the operation logs in a specified period.The operation logs in a specified period are displayed.

Test description485. If many records are displayed, add conditions to query the logs.

486. The querying operation cannot be displayed in the operation logs.

T010 Iu-PS Interface

T010-01 RAB ManagementT010-0101 RAB ManagementObjectiveTo verify the SGSN function of RAB resource management.

Serial number of test networking diagramFigure I

Prerequisites487. The RNC and the NodeB run normally.488. The SGSN and the GGSN run normally.489. The subscriber has subscribed to the GPRS service.490. Create a user tracing task and an Iu interface tracing task.

Test procedureExpected Result

491. Switch on the UE.The subscriber is attached to the WCDMA network.

492. Activate a PDP context.The PDP context is activated. The RAB is set up on the Iu interface.

493. Deactivate the PDP context.The PDP context is deactivated. The RAB on the Iu interface is released.


NoteThis is a basic test item.

T010-02 Iu Connection ManagementT010-0201 Iu Connection ManagementObjectiveTo verify the SGSN function of Iu connection management.


Prerequisites494. The RNC and the NodeB run normally.495. The SGSN and the GGSN run normally.496. The subscriber has subscribed to the GPRS service.497. Create a user tracing task and an Iu interface tracing task.

Test procedureExpected Result

498. Switch on the UE.The subscriber is attached to the WCDMA network.

499. Initiate a PDP context activation.The PDP context is activated. The Iu connection is set up.

500. Execute TRG IUREL on the LMT of the RNC to release the Iu connection.The Iu connection is released.


NoteThis is an optional test item.

T011 Path ManagementT011-01 Path ManagementT011-0101 Path DetectionObjectiveTo verify the SGSN function of path detection.


Prerequisites501. The RNC and NodeB systems run normally.

502. The SGSN and GGSN systems run normally. 503. The subscriber has subscribed GPRS services in the HLR.

504. Create a user tracing task, Iu interface tracing task, GTPC interface tracing task, and GTPU interface tracing task where the peer addresses are the ones of the RNC and GGSN.


505. Execute SET GTPPUB: ECHOSIG=ON, GTPUGNGPECHO=ON; to turn on the ECHO switch.The ECHO switch is turned on, the default is on.


507. The MS initiates a PDP context activation The PDP context is activated.

508. Execute DSP USPUPDP and DSP GTPUPDP on the USPU and UGTP-U boards to observe the PDP context. The PDP context is displayed.

509. Observe the GTPC and GTPU trace windows.In the GTPC and GTPU trace windows, the SGSN sends Echo Request to the GGSN or RNC. If the SGSN receives Echo Request from the GGSN or RNC, the SGSN returns Echo Response.

Test description

The figure below shows the message flow:

The SGSN sends Echo Request to the GGSN or, the GGSN or RNC returns Echo Response. If the SGSN receives Echo Request from the GGSN or RNC, the SGSN returns Echo Response.

T012 2G/3G SwitchoverT012-01 Inter-SGSN 2G/3G SwitchoverT012-0101 Subscriber Inter SGSN Inter-System Switchover from 2G GPRS to 3G UMTS With PDP Context Activated and FTP Data TransmissionObjectiveTo verify if a subscriber can perform inter-SGSN inter-system switchover from 2G GPRS to 3G UMTS with the PDP context activated and FTP data transmission.

Serial number of test networking diagramSGSN Test Networking Figure v

Prerequisites510. Configure two SGSNs. One is configured with a 2G routing area and the other is configured with a 3G routing area.511. Use ADD IPv4DNSH on the 2G SGSN to configure DHSH of the 3G SGSN. The format is RACPPPP.LACXXXX.MNCYYYY.MCCZZZZ.GPRS, where PPPP is RAC, XXXX is LAC,YYYY is MNC No., ZZZZ is MCC No., and the address is the signaling address of the peer 3G SGSN.

512. Use ADD IPv4DNSH on the 3G SGSN to configure DHSH of the 2G SGSN. The format is RACPPPP.LACXXXX.MNCYYYY.MCCZZZZ.GPRS, where PPPP is RAC No., XXXX is LAC NO., YYYY is MNC No., ZZZZ is MCC No., and the address is the signaling address of the peer 2G SGSN.

513. The MS subscribes to GPRS service in HLR.

514. Trace the signaling message of the MS, GTPC interface, and Iu interface on LMT of the 2G SGSN. Trace the signaling message of the MS, GTPC interface and Iu interface on LMT of the 3G SGSN.


515. Switch on the MS in the coverage of the 2G GPRS network and originate attach.The MS is attached.

516. The MS activates PDP context after being attached and starts FTP transmission.The PDP context is activated. The FTP data transmission is started.

517. The MS roams to the 3G routing area.The MS initiates RAU procedure and performs RAU.

518. Execute DSP MMBYIMSI on the new LMT.The MS is attached to the 3G UMTS network.

519. Execute DSP USPUPDP on the new LMT.The PDP context of the MS keeps active.

520. Observe the data transmission.The MS continues the FTP data transmission.

Test descriptionThe message flow chart is listed below:

The MS sends Routing Area Update Request (old RAI, old P-TMSI, old P-TMSI signature, update type) to the 3G SGSN. The new 3G SGSN sends SGSN Context Request (old RAI, old P-TMSI, old P-TMSI signature, new SGSN address) to the 2G SGSN to get the MM and PDP contexts of the MS. The old 2G SGSN gives SGSN Context Response (MM Context, PDP Contexts). The new 3G SGSN sends SGSN Context Acknowledge to the old 2G SGSN. The old 2G SGSN sends GTP PDUs to the new 2G SGSN through the tunnel. The 3G SGSN sends Update PDP Context Request (new SGSN Address, TEID, QoS) to the GGSN. The GGSN updates the PDP context domain and then returns Update PDP Context Response (TEID). The new 3G SGSN sends Update GPRS Location (SGSN Number, SGSN Address, IMSI) to HLR for the change of HLRSGSN. The HLR sends Cancel Location (IMSI) to the old 2G-SGSN. The old 2G SGSN confirms the message. The HLR sends Insert Subscriber Data (IMSI, GPRS Subscription Data) to the new 3G SGSN. The 3G-SGSN creates MM context for the MS and return Insert Subscriber Data Ack (IMSI) to the HLR. The HLR returns Update GPRS Location Ack (IMSI) to the 3G SGSN to confirm the updated location of the GPRS. The new 3G SGSN responds to the MS through Routing Area Update Accept (P-TMSI, P-TMSI Signature). The MS returns Routing Area Update Complete to the SGSN to confirm the new P-TMSI. The MS sends Service Request. The new 3G SGSN sends RAB Assignment Request to SRNS for none line access bearer. The SRNS sends Radio Bearer Setup Request (PDCP-SNUs). The MS responses Radio Bearer Setup Complete (PDCP-SNDs). The SRNS sends RAB Assignment Response.

T012-02 Inter-SGSN 3G/2G SwitchoverT012-0201 Subscriber Inter SGSN Inter-System Switchover from 3G UMTS to 2G GPRS With PDP Context Activated and FTP Dtaa TransmissionObjectiveTo verify if a subscriber can perform inter-SGSN inter-system switchover from 3G GPRS to 2G UMTS with PDP context activated and with FTP data transmission.

Serial number of test networking diagramSGSN Test Networking Figure v

Prerequisites521. Configure two SGSNs. One is configured with a 2G routing area and the other is configured with a 3G routing area.522. Use ADD IPv4DNSH on the 2G SGSN to configure DHSH of the 3G SGSN. The format is RACPPPP.LACXXXX.MNCYYYY.MCCZZZZ.GPRS, where PPPP is RAC, XXXX is LAC,YYYY is MNC No., ZZZZ is MCC No., and the address is the signaling address of the peer 3G SGSN. 523. Use ADD IPv4DNSH on the 3G SGSN to configure DHSH of the 2G SGSN. The format is RACPPPP.LACXXXX.MNCYYYY.MCCZZZZ.GPRS, where PPPP is RAC No., XXXX is LAC NO., YYYY is MNC No., ZZZZ is MCC No., and the address is the signaling address of the peer 2G SGSN.

524. The MS subscribes to GPRS service in HLR.

525. Trace the signaling message of the MS, GTPC interface and Iu interface on LMT of the 2G SGSN. Trace the signaling message of the MS, GTPC interface and Iu interface on LMT of the 3G SGSN.


526. Switch on the MS under the coverage of the 3G UMTS network. The MS is attached.

527. Activate the PDP context after and then start the FTP data transmission.The PDP context is activated. The FTP data transmission is started.

528. The MS moves to the 2G routing area.The MS initiates RAU procedure and performs RAU.

529. Execute DSP MMBYIMSI on the new LMT.The MS is attached to the 2G GPRS network.

530. Execute DSP USPUPDP on the new LMT.The PDP context of the MS keeps active.

531. Observe the data transmission.The MS continues the FTP data transmission.


The MS sends Routing Area Update Request (old RAI, old P-TMSI signature, update type) to the 2G SGSN.

The new 2G SGSN sends SGSN Context Request (old RAI, TLLI, old P-TMSI signature, new SGSN address) to the 3G SGSN to obtain the MM and PDP contexts of the MS.

With the MS being PMM-CONNECTED, the old 3G SGSN sends SRNS Context Request (IMSI) to SRNS. The SRNS sends SRNS Context Response (IMSI, GTP-SNDs, GTPSNUs, PDCP-SNDs, PDCPSNUs). The old 3G SGSN sends SGSN Context Response (MM Context, PDP Context). {0>The new 2G SGSN sends SGSN Context Acknowledge to the old 3G SGSN.

The 3G SGSN sends SRNS Data Forward Command (RAB ID, Transport Layer Address, Iu Transport Association) to the SRNS. The SRNS starts the data-forward timer. The old 3G SGSN sends GTP PDUs to the new 2G SGSN through the tunnel The 2G SGSN sends Update PDP Context Request (new SGSN Address, TEID, QoS) to the GGSN. The GGSN updates the PDP context domain and then returns Update PDP Context Response (TEID). The new 2G SGSN sends Update GPRS Location (SGSN Number, SGSN Address, IMSI) to the HLR for the change of HLRSGSN. The HLR sends Cancel Location (IMSI) to the old 3G SGSN. The old 3G-SGSN confirms the message. The HLR sends Insert Subscriber Data (IMSI, GPRS Subscription Data) to the new 2G SGSN. The 2G SGSN creates MM context for the MS and returns Insert Subscriber Data Ack (IMSI) to the HLR. The HLR returns Update GPRS Location Ack (IMSI) to the 2G-SGSN to confirm the updated location of the GPRS. The new 2G SGSN responds to the MS through Routing Area Update Accept. The MS returns Routing Area Update Complete to the SGSN to confirm the new P-TMSI. The 2G SGSN and the BSS process the BSS Packet Flow Contex.

T012-03 Switchover Between Authentication Triplet and QuintupleT012-0301 Switchover Between Authentication Triplet and QuintupleObjectiveTo verify the switchover between the authentication triplet and quintuple.


Prerequisites532. The SGSN and LMT run normally.533. The SGSN does not store the subscription data.534. The subscriber is a USIM user, and has subscribed to the GPRS service.535. Execute SET PMM to enable the authentication and encryption.536. Create a user tracing task and an Iu interface tracing task on the LMT of the SGSN.


Switch on the MS.The subscriber is attached to the SGSN.

The Send Authentication Info Res message that the HLR sends to the SGSN carries the authentication triplet RAND, SRES, and KC. The Security Mode Command message sent by the SGSN to the RNC carries IK and CK.


T013 Tracing ManagementT013-01 Subscriber Tracing

T013-0101 User Tracing Based on IMSI

ObjectiveTo verify the user tracing based on IMSI.


Prerequisites537. The SGSN system runs normally.538. The SGSN communicates well with the LMT.539. Tracing management is permitted by the license.


540. Click the Maintenance window on the LMT. Double-click Trace Management, then double-click User Trace Task , and then double-click User Trace Task.The User Trace dialog box is open.

541. Enter the IMSI of the subscriber and other information for the trace task. Click OK.The subscriber tracing task is created.

542. Switch on the MS. The MS initiates an attach and PDP context activation. Observe the messages traced in the tracing window.The attach and PDP context activation messages are displayed in the tracing window.

543. Double-click one message in the tracing window.The details of the message are displayed.


T013-0102 Tracing User Based on MSISDNObjectiveTo verify the user tracing based on MSISDN.



545. The SGSN communicates well with the LMT.

546. Tracing management is permitted by the license.


Click the Maintenance window on the LMT. Double-click Trace Management and then double-click Subscriber Trace Task.The Subscriber Trace dialog box is open.

2. Enter the MSISDN of the subscriber and other information for the trace task. Click OK.The subscriber tracing task is created.

Switch on the MS. The MS initiates an attach and PDP context activation. Observe the messages traced in the tracing window.The attach and PDP context activation messages are displayed in the tracing window.

Double-click one message in the tracing window.The details of the message are displayed.


T013-02 Interface TracingT013-0201 Iu Interface TracingObjectiveTo verify the SGSN function of Iu interface tracing.

Serial number of test networking diagramFigure I.

Prerequisites547. The SGSN system runs normally.548. The SGSN communicates well with the LMT.549. Tracing management is permitted by the License.550. Execute LST RNC: to view the RNC information.551. Execute LST BRD BT=UICP, RS=ACTIVE; to find the active UICP board.


552. Click the Maintenance window on the LMT. Double-click Trace Management and then double-click Interface Trace Task.All the interface tracing tasks that can be created are displayed.

553. Double-click Iu Interface Trace.The Iu Interface Trace dialog box is open.

554. Enter the location of the active UICP board and the RNC index to the Iu Interface Trace dialog box. Click OK.The Iu interface tracing task is created.

555. Switch on the MS. The MS initiates a attach. Observe the message tracing on the Iu interface.The attach request is displayed in the Iu Interface Trace window.



T013-0202 Gr Interface TracingObjectiveTo verify the SGSN function of Gr interface tracing.


Prerequisites557. The SGSN system runs normally.558. The SGSN communicates well with the LMT.559. Tracing management is permitted by the License.560. The SGSN communicates well with the HLR.561. Execute LST BRD BT=USPU, RS=ACTIVE; to find the active USPU board.562. Execute DSP MMBYIMSI: IMSI="" to display the subscribers in the SGSN system. If the subscriber is on the list, execute RMV USRBYIMSI: IMSI="" to remove it.


563. Click the Maintenance window on the LMT. Double-click Tracing Management and then double-click Interface Trace Task.All the interface tracing tasks that can be created are displayed.

564. Double-click Gr Interface Tracing.The Gr Interface Trace dialog box is open.

565. Enter the active USPU board information, and IMSI. Click OK.The Gr interface tracing task is created.

566. Switch on the MS, and then the MS initiates an attach. Switch off the MS. Repeat this procedure for several times. Observe the message tracing on the Gr interface.The messages between the SGSN and HLR are displayed in the Gr Interface Tracing window.



T013-0203 Ga Interface Tracing

ObjectiveTo verify the SGSN function of Ga interface tracing.


Prerequisites568. The SGSN system runs normally.569. The SGSN communicates well with the LMT.570. Tracing management is permitted by the License.571. The SGSN communicates well with the CG.572. Execute LST CHGCG to obtain the IP address of the CG.573. Execute LST BRD BT=UCDR, RS=ACTIVE; to find the active UCDR board.574. Execute SET CHGCHAR: CC=, MP=YES, MPCP=NO to generate an M-CDR rather than the periodic generation.



576. Double-click Ga Interface Trace.The Ga Interface Trace dialog box is open.

577. Enter the active UCDR board information, and CG IP address. Click OK.The Ga interface tracing task is created.

578. Switch on the MS, and then the MS initiates an attach. Repeat this for several times. Observe the message tracing on the Ga interface.The charging information that the SGSN sends to the CG is displayed in the Ga Interface Trace window.



T013-0204 Gs Interface TracingObjectiveTo verify the SGSN function of Gs interface tracing.

Serial number of test networking diagramFigure II

Prerequisites580. The SGSN system runs normally.581. The SGSN communicates well with the LMT.582. Tracing management is permitted by the License.583. The SGSN communicates well with the MSC/VLR.584. Execute LST BRD BT=USPU, RS=ACTIVE; to find the active USPU board.585. Execute LST LAIVAL to obtain the number of the VLR for a LAI.586. Set the network at the RAN to mode I.587. The subscribed network mode in the HLR is bothMSCAndSGSN.



589. Double-click Gs Interface Trace.The Gs Interface Trace dialog box is open.

590. Enter the active USPU board information, and VLR number. Click OK.The Gs interface tracing task is created.

591. Switch on the MS, and then the MS initiates an attach. Switch off the MS. Repeat this procedure for several times. Observe the message tracing on the Gs interface.The messages between the SGSN and MSC/VLR are displayed in the Gs Interface Tracing window.



T014 SS7 OVER IP

T014-01 Gs Interface TestT014-0101 Combined AttachObjectiveTo verify the combined attach procedure when the Gs interface transmits signalling over IP.


Prerequisites593. The SGSN system and its LMT are in normal operation.594. The Gs interface on the SGSN bears the IP transmission. The Gs interface is functional.595. The SGSN license defines that the SS7 OVER IP service is supported.596. The network works in mode I.597. The UE has subscribed to GPRS services and non-GPRS services in the HLR.598. Trace the signaling message of the UE and Gs interface on the LMT.


599. Switch on the UE. The subscriber originates a combined attach. The subscriber is attached. The Gs interface tracing shows that the SGSN sends the Location Update Request message.

600. Execute DSP MMBYIMSI with the IMSI of this subscriber to view the MM context on the LMT.The LMT of the SGSN displays the dynamic MM context, where the user Gs interface association state is associated.


The SGSN sends Location Update Request to the MSC. The MSC responses Location Update Accept. If the TMSI does not change, the SGSN responses TMSI Relocation Complete to the MSC.

T014-0102 CS PagingObjectiveTo verify the CS paging procedure when the Gs interface transmits signalling over IP.


Prerequisites601. The SGSN system and its LMT are in normal operation.602. The Gs interface on the SGSN bears the IP transmission. The Gs interface is functional.603. The SGSN license defines that the SS7 OVER IP service is supported.604. The network works in mode I.605. The UE has subscribed to GPRS services and non-GPRS services in the HLR.606. Trace the signaling message of the UE and Gs interface on the LMT.


607. Switch on the UE. The UE originates a combined attach. The UE combined attach succeeds.

608. Execute DSP MMBYIMSI with the IMSI of the subscriber to view the MM context on the LMT.The LMT of the SGSN displays the dynamic MM context of this subscriber, where the user Gs interface association state is Gs-associated.

609. Subscriber B initiates a CS call to subscriber A.Subscriber A rings. The CS call is established when the phone is picked up.

610. Observe the signaling messages in the Gs interface tracing window.The SGSN receives the Paging Request message from the MSC.

Test descriptionThe figure below shows the message flow: SHAPE \* MERGEFORMAT

The MSC sends Paging Request to the SGSN.

T015 Gs InterfaceT015-01 Initiating GPRS Detach from MSC/VLR

T015-0101 GPRS DetachObjectiveTo verify if combined-attached subscribers can initiate GPRS detach.


Prerequisites611. The SGSN and LMT run normally.612. The network works in mode I.613. The license defines that the SGSN supports the Gs interface tracing and message tracing.614. The UE has subscribed to GPRS services and non-GPRS services in the HLR.615. Create a user tracing task and a Gs interface tracing task on the LMT.616. All the interfaces on the SGSN are functional.


617. Switch on the UE and originate combined attach.The UE combined attach succeeded.

618. The UE originates GPRS detach.The GPRS is detached.

619. Execute DSP MMBYIMSI: IMSI="" on the LMT to display the status of the UE.The UE is IDLE in the SGSN. The DETACH status of the UE is DETACHED.

620. Open Subscriber Tracing window to observe the signaling messages of the UE and Gs interface on the LMT.During the process of GPRS detach, the SGSN sends BSSAP+-GPRS-DETACH-INDICATION to the MSC/VLR. The MSC/VLR returns BSSAP+-GPRS-DETACH-ACK.


The UE sends Detach Request to the SGSN with detach type indicating GPRS Detach only. The SGSN originates a GPRS detach procedure to the MSC/VLR. During the process of GPRS detach, the SGSN sends BSSAP+-GPRS-DETACH-INDICATION to the MSC/VLR. The MSC/VLR returns BSSAP+-GPRS-DETACH-ACK to the SGSN. If the UE indicates switching on detach, the SGSN sends Detach Accept to the UE.

T015-0102 IMSI DetachObjectiveTo verify if combined-attached subscribers can originate IMSI detach.


Prerequisites621. The SGSN and LMT run normally.622. The network works in mode I.623. The UE has subscribed to GPRS services and non-GPRS services in the HLR.624. The license defines that the SGSN supports the Gs interface tracing and message tracing.625. Create a user tracing task and a Gs interface tracing task on the LMT.626. All the interfaces on the SGSN are functional.



628. Switch off the UE.The IMSI is detached.

629. Execute DSP MMBYIMSI: IMSI="" on the LMT to display the combined status of the UE.The UE is in the state of detached.

630. Observe the signaling messages in the user tracing window and the Gs interface tracing window.During the process of IMSI detach, the SGSN sends BSSAP+-IMSI-DETACH-INDICATION to the MSC/VLR. The MSC/VLR returns BSSAP+-IMSI-DETACH-ACK.


The UE sends Detach Request to the SGSN. The SGSN originates IMSI detach procedure to the MSC/VLR. During the process of IMSI detach, the SGSN sends BSSAP+-GPRS-DETACH-INDICATION to the MSC/VLR. The MSC/VLR returns BSSAP+-GPRS-DETACH-ACK to the SGSN.

T015-02 CS PagingT015-0201 CS PagingObjectiveTo verify if SGSN can deliver CS paging messages of combined-attached subscribers.


Prerequisites631. The SGSN and LMT run normally.632. The network works in mode I.633. The UE has subscribed to GPRS services and non-GPRS services in the HLR.634. The license defines that the SGSN supports the Gs interface tracing and message tracing.635. Create a user tracing task and a Gs interface tracing task on the LMT.636. All the interfaces on the SGSN are functional.



638. Another UE initiates an CS call to this UE.Answer the phone. The CS call is connected.

639. Observe the signaling messages in the user tracing window and the Gs interface tracing window.After receiving BSSAP+-PAGING-REQUEST sent by the MSC/VLR, the SGSN sends the CS paging message to the UE.


The MSC/VLR sends CS Paging to the SGSN. The SGSN sends Paging to the UTRAN (CN Domain). The UTRAN originates Paging (CN Domain) to the UE. The UE sends Paging response to the MSC/VLR.

T016 ODB

T016-01 Packet Service BarringT016-0101 Packet Service BarringObjectiveTo verify the packet service barring by the ODB.


Prerequisites640. The SGSN and LMT run normally.641. The license defines that the SGSN supports the message tracing.642. The subscriber has subscribed to the packet services in the HLR.643. Create a user tracing task on the LMT.644. All the interfaces on the SGSN are functional.645. The HLR supports the ODB function in the packet domain.


646. Change the ODB setting in the HLR to bar all the packet domain services.The new setting is effective.

647. Execute SET MAPFUNC: APS=YES to set the barAllPacketServices parameter.The function is set.

648. Execute LST MAPFUNC: to view the MAP function flow chart.The parameter barAllPacketServices is Yes.

649. Switch on the UE.The subscriber is attached.

650. The subscriber initiates a PDP context activation.The PDP context activation fails. The Iu interface tracing shows that the SGSN sends Activate PDP Context Reject to the UE with the cause value of ODB.


The UE sends Activate PDP Context Request to the SGSN. The SGSN sends Activate PDP Context Reject to the UE with the cause value of ODB.

T017 Secondary PDP Context ActivationT017-01 Secondary PDP Context ActivationT017-0101 Secondary PDP Context ActivationObjectiveTo verify if the SGSN can activate the PDP context with a dynamic address for a common subscriber.


Prerequisites651. The RNC and NodeB system run normally.

652. The SGSN and GGSN run normally.

653. The HLR stores the GPRS and PDP subscription data of the test subscriber.654. Create a user tracing task and an Iu interface tracing task on the LMT.655. The UE supports the secondary PDP context activation function.656. The SGSN license defines that the SGSN supports the secondary PDP context activation.


657. Switch on the UE. The subscriber initiates an attach to the WCDMA network.The subscriber is attached.

658. The subscriber initiates a PDP context activation, such as visit a web site.The PDP context is activated.

659. Select a multi-media file to play on the UE to trigger a secondary PDP context activation.The PDP context is activated.

Execute DSP USPUPDP on the LMT. The result shows that there are two PDP contexts for this UE with the same address.

Test descriptionThe figure below shows the message flow::

The UE sends Activate Secondary PDP Context Request to the SGSN, with the linked TI but not the PDP address or the APN. The SGSN sends Create PDP Context Request to the GGSN. The GGSN responses Create PDP Context Response.

The SGSN sends RAB assignment request to the RNC. The RNC returns RAB Assignment Response. The SGSN sends Activate Secondary PDP Context Accept to the UE.

T018 Iu Over IP

T018-01 Iu Over IP

T018-0101 Iu Over IP

ObjectiveTo verify that the SGSN supports the Iu over IP function.


Prerequisites660. The SGSN runs normally and connected to the LMT.661. The license supports the message tracing and Iu over IP.662. Create a user tracing and a M3UA tracing task on the LMT.663. The Iu over IP is configured.664. All ports on the SGSN are in good condition.665. The HLR stores the PDP context subscription data.666. The RNC supports Iu over IP.


667. Switch on the UE.The subscriber is attached.

668. Visit a web page to initiate a PDP context activation.The PDP context is activated. The web page is open.

669. Execute DSP GTPUPDP: IMSI="" to view the subscriber information.The details of the activated PDP context are displayed.


The UE sends Attach Request to the SGSN. The SGSN sends Update Location Request to the HLR. The HLR sends Insert Subscriber Data to the SGSN with the IE of gprsSubscriptionData. The SGSN sends Insert Subscriber Data ACK to the HLR, and then the HLR sends Update Location ACK to the SGSN. The SGSN sends Attach Accept to the UE. The UE sends Activate PDP Context Request to the SGSN. The SGSN sends Create PDP Context Request to the GGSN, and then the GGSN responses Create PDP Context Response. The SGSN sends Activate PDP context Accept to the UE.

T019 SSH

T019-01 SSHT019-0101 SSH

Objective

To verify if the SGSN can support SSH function.


None.

Prerequisites

670. The SGSN system runs normally, and LMT has connected with SGSN normally.

671. The license of the SGSN supports SSH function, and the SSH client has been installed.

672. Execute the command ADD SSHUSER to configure SSH users name, execute the command DLD SSHPUBKEY: SIP=, UNM=, PWD=, DIR=, FNM= to download pubilc key file.

673. Configure the parameters of SSH client according to configuration guide, set maintenance port (6000), alarm port (6001) and data port (6006) as listeners, enable maintenance port and alarm ports encryption function.674. The SGSN alarm management system is open.


1. Configure IP of PC installing LMT as the agent of LMT, and then logon LMT.Logon LMT successfully

2. Execute the command LST BRD. The information of board can be displayed.

3. Execute the command RST BRD: OT=BRD, SRN=, SN=, BP=IO to reset one standby board, and check whether board fault alarm is displayed on alarm management system. The command executes successfully, and the board fault alarm is displayed.

Test description

None.

Paging Request

MSC

SGSN

TMSI Relocation Complete

Location Update Accept

Location Update Request

MSC

SGSN

Should be deleted because we will not use MTP3 links to connect to HLR. We use M3UA link connect HLR through MSC

Should be deleted, according to the ip plan, we use load share instead of redundancy backup

Should be deleted, because according to the ip network plan, we use load share for two ports instead of redundancy backup

Should be deleted, We will not use MTP3 link to connect HLR

Should be deleted, before swap PCU to huawei SGSN, there is not E1 port work

Modified because we use M3UA links to connect HLR through MSC

i

_1210486976.vsd

_1218472506.vsdMS

SGSN

HLR

Attach Request

Update Location

RNC

Insert Subscriber Data

Insert Subscriber Data Ack

Attach Accept

Update Location Ack

Attach Complete

Authentication and Ciphering Request

Authentication and Ciphering Response

Security Mode Command

Security Mode Complete

Send Authentication Inf

Send Authentication Info Ack

_1218472590.vsdMS

SGSN

Detach Request

Detach Accept

RNC

Paging

Paging

Service Request(Paging Response)

_1218472691.vsdMS

SGSN

Routeing Area Update Request

RNC

Routeing Area Update Accept

Routeing Area Update Complete

_1218472713.vsdMS

SGSN

Routeing Area Update Request

RNC

Routeing Area Update Accept

Routeing Area Update Complete

_1218472638.vsdMS

SGSN

HLR

Detach Request

Detach Accept

RNC

Cancel Location

Cancel Location Ack

Paging

Paging

Service Request(Paging Response)

_1218472559.vsdMS

SGSN

Attach Request

RNC

Attach Accept

Attach Complete

Authentication and Ciphering Request

Authentication and Ciphering Response

Security Mode Command

Security Mode Complete

_1212311584.vsd

_1218441891.vsd

_1218449791.vsd

_1210487006.vsd

_1210233008.vsd

_1210426460.vsd

_1210486931.vsd

_1210255872.vsd

_1210399875.vsd

_1210255334.vsd

_1184588287.vsd

_1184656839.vsd

_1191504861.vsd

_1209890292.vsd

_1184672081.vsd

_1184649356.vsd

_1184574713.vsd

Documents

Acceptance Test Cases for VIP-SGSN