CVP - BTS - FAP - CNE - v1 1

BTS 3G Network in a Box
Conformance Verification Plan

Version 1.1
Continuous Computing Corporation

Tel: +1 (858) 882-8800
Fax: +1 (858) 777-3389
Email: [email protected]
http://www.ccpu.com
BTS 3G Network in a Box
Conformance Verification Plan
9021285 1.1
Trillium, Continuous Computing, and TAPA are registered trademarks of Continuous Computing
Corporation. Other referenced trademarks are trademarks (registered or otherwise) of the respective
trademark owners. This document is confidential and proprietary to Continuous Computing
Corporation. No part of this document may be reproduced, stored, or transmitted in any form by any
means without the prior written permission of Continuous Computing Corporation.
Information furnished herein by Continuous Computing Corporation, is believed to be accurate and
reliable. However, Continuous Computing Corporation assumes no liability for errors that may
appear in this document, or for liability otherwise arising from the application or use of any such
information or for any infringement of patents or other intellectual property rights owned by third
parties which may result from such application or use. The products, their specifications, and the
information appearing in this document are subject to change without notice.
To the extent this document contains information related to software products you have not licensed
from Continuous Computing Corporation, you may only apply or use such information to evaluate
the future licensing of those products from Continuous Computing Corporation. You must determine
whether or not the information contained herein relates to products licensed by you from Continuous
Computing Corporation prior to any application or use.
Contributors: Continuous Computing Development Team, Naveen D’cruz.
Printed in U.S.A.
Copyright 1989-2011. Continuous Computing Corporation. All rights reserved.
Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Proprietary and Confidential Page 2 of 34 9021285 1.1
1. CONTENTS
1. Contents .................................................................................................................................3
2. Figure .....................................................................................................................................6
3. Tables ....................................................................................................................................7
4. Preface ...................................................................................................................................8
4.1. Objective ................................................................................................................................. 8
4.2. Audience................................................................................................................................. 8
4.3. Document Organization ....................................................................................................... 8
Table 1: Document Organization .................................................................................................8
Table 2: Acronyms.......................................................................................................................8
4.4. Release History ..................................................................................................................... 9
Table 3: Release History .............................................................................................................9
5. Introduction........................................................................................................................... 10
5.1. Scope .................................................................................................................................... 10
5.2. Assumptions & Dependencies .......................................................................................... 10
5.3. Limitations & Constraints ................................................................................................... 10
6. Test overview and Architecture............................................................................................. 11
6.1. Architecture .......................................................................................................................... 11
Figure 1: Test Architecure ......................................................................................................... 11
6.2. Interface Coupling ............................................................................................................... 11
6.3. Target Environment ............................................................................................................ 11
6.3.1. Type of Testing ...................................................................................................................11
6.3.2. Hardware ............................................................................................................................12
6.3.3. Operating System ...............................................................................................................12
6.3.4. Compiler .............................................................................................................................12
7. Description of Test Cases: .................................................................................................... 13
7.1. Robustness Testing ............................................................................................................ 13
Testcase [2]. Successful cleanup when MSC restarts ............................................................... 13
Testcase [3]. Successful cleanup when SGSN restarts ............................................................. 13
Testcase [4]. Successful cleanup when HNBGW restarts .......................................................... 14
Testcase [5]. FAP goes down and restarts when CS/PS are running ........................................ 14
Testcase [6]. FAP goes down and restarts when no CS/PS are running.................................... 15
Testcase [7]. UE goes out of coverage ...................................................................................... 16
Testcase [8]. UE goes out of coverage when CS call is going on .............................................. 16
Testcase [9]. UE goes out of coverage when PS call is going on............................................... 16
Testcase [10]. UE goes out of coverage when SIM call ............................................................. 16
Testcase [11]. IMSI over IMSI Attach (without detach) .............................................................. 17
Testcase [12]. GMM over GMM Attach (without detach) ............................................................ 17
Testcase [13]. Repeated UE Power ON and Power OFF........................................................... 17
Testcase [14]. Repeated UE Power ON and Power OFF when CS call is ongoing .................... 17
Testcase [15]. Repeated UE Power ON and Power OFF when PS call is ongoing .................... 17
Testcase [16]. Attach/detach scenario with real UE for 3 days. ................................................. 18

Testcase [17]. Simultaneous CS/PS attach ............................................................................... 18
Testcase [18]. Reset for CS domain .......................................................................................... 18
Testcase [19]. Reset for PS domain .......................................................................................... 19
Testcase [20]. Reset towards both HNB and CN ....................................................................... 19
Testcase [21]. Test for Debug Logging Enhancements ............................................................. 20
Testcase [22]. Case for Enabling the Debug Mask .................................................................... 20
Testcase [23]. Case for Enabling the Debug Mask selectively ................................................... 20
Testcase [24]. Case for Disabling the Debug Mask ................................................................... 21
7.2. Soak Testing ........................................................................................................................ 21
Testcase [25]. Long Duration of 1 CS voice call ........................................................................ 21
Testcase [26]. Long Duration of 2 CS voice call ........................................................................ 21
Testcase [27]. Long Duration of 1 CS video call ........................................................................ 21
Testcase [28]. Long Duration of 2 CS video call ........................................................................ 22
Testcase [29]. Make and release of 10 CS voice calls ............................................................... 22
Testcase [30]. Make and release of 10 CS video calls ............................................................... 22
Testcase [31]. Make and release of 10 PS64 calls .................................................................... 22
Testcase [32]. Make and release of 10 PS128 calls .................................................................. 22
Testcase [33]. Make and release of 10 PS384 calls .................................................................. 23
Testcase [34]. Make and release of 10 HSDPA calls ................................................................. 23
Testcase [35]. Make and release of 10 HSUPA calls ................................................................. 23
Testcase [36]. Long duration of 4 HSDPA calls ......................................................................... 23
Testcase [37]. Long duration of 2 HSDPA and 2 HSUPA calls .................................................. 24
Testcase [38]. Long duration of 2 HSDPA and 1 CS voice calls ................................................ 24
Testcase [39]. Long duration of 2 HSUPA and 1 CS voice calls ................................................ 24
Testcase [40]. Long duration of 2 HSUPA and 1 CS video calls ................................................ 24
Testcase [41]. 2 HSPA and 1 CS calls multiple times from different UEs ................................... 25
Testcase [42]. CS/PS call multiple times between the UE’s back to back ................................. 25
7.3. Capacity Testing.................................................................................................................. 25
Testcase [43]. 6 UE CS voice call.............................................................................................. 25
Testcase [44]. 6 UE CS video calls ............................................................................................ 25
Testcase [45]. 6 UE PS call ....................................................................................................... 26
Testcase [46]. 6 UE doing CS and PS call ................................................................................. 26
7.4. Performance Testing .......................................................................................................... 26
Testcase [47]. CPU Usage measurement for 6 UE CS calls ...................................................... 26
Testcase [48]. CPU Usage measurement for 6 UE PS calls ...................................................... 26
7.5. Packaging ............................................................................................................................. 27
7.6. Licensing .............................................................................................................................. 27
7.7. Documentation .................................................................................................................... 27
8. Configuration ........................................................................................................................ 28
8.1. Creating configuration Files............................................................................................... 28
8.2. Sample configInfo.txt .......................................................................................................... 28
8.3. Sample protocol configuration file. ................................................................................... 29

8.4. Sample HLR database configuration ............................................................................... 29
9. Test Completion and Stop Criteria ........................................................................................ 32
10.References ........................................................................................................................... 33

2. FIGURE
Figure 1: Test Architecure ...............................................................................................................11

3. TABLES
Table 1: Document Organization ..................................................................................................... 8
Table 2: Acronyms ........................................................................................................................... 8
Table 3: Release History.................................................................................................................. 9

4. PREFACE
4.1. Objective
Battlefield Telecommunications Systems (BTS) wants to build Complete NiB (Network in a Box)
using Trillium 3G NodeB, collapsed RNC, SGSN, GGSN and HLR softwares as a 3G field
deployable femtocell/picocell solution to provide mobile communication for Government and
Military organizations running on small form factor computer capable for use in mobile
applications using a customized 64 bit Linux operating system.
This document presents the Conformance Verification Plan for the BTS FAP – CNE network
solution. In this document, the Test Cases are mentioned which need to be executed on the
Integrated Stack.
4.2. Audience
Continuous Computing assumes the readers of this document are familiar with the 3G protocols.
4.3. Document Organization

This document is organized into the following sections:
Table 1: Document Organization
Section Description
1. Introduction <Describes the objectives of the document and lists the
definitions and acronyms used.>
2. Test Overview and Architecture <Describes the test overview and architecture.>
3. Description of Test Cases <Describes the Test Cases execution details.>
4 Test Completion and Stop Criteria <Explains the conditions to conclude the testing>
Table 2: Acronyms
Acronym Description
FAP Femto Access Points
HNB Home NodeB
HNBGW HNB Gateway
MSC Mobile Switching Centre
SGSN Serving Gateway Support Node
GGSNC GPRS Gateway Support Node – (Control Plane)
GGSNU GPRS Gateway Support Node – (User Plane)
HLR Home Location Register
UE User Equipment

CS Call Circuit Switched Call
PS Call Packet Switched Call
4.4. Release History

The following table lists the history of changes in successive revisions to this document.
Table 3: Release History
Version Date Author (s) Reviewer Description

1.0 July 13, 2011 Geetha, Roshan Hari, Moses, Initial draft.
Sachin
1.1 Nov 7, 2011 Vivek Sinha Hari, Moses, Updated for Phase 2
Sachin, BTS Dec’11 Delivery
Enhancements

5. INTRODUCTION
Battlefield Telecommunications Systems (BTS) plans to develop a collapsed FAP-CNE network
solution that can be deployed as a single node.
The project aims to build a commercial field deployable solution focused on robustness and some
new features. The features contains for Phase 1 and Phase 2 are:-
Feature List for Phase -1:
 Robustness of the network elements
 Support for commercial SIM Authentication Algorithm
 Support for resource handling using RANAP RESET and RESET RESOURCE procedures
 Support for dynamic OVSF code allocation implementation.
 Simultaneous CS and PS calls
Feature List for Phase -2:

 System uptime requirement up to 3 days
 Simultaneous CS/PS attach
 Porting to Octasic 1010 platform
5.1. Scope
The scope of this document is limited to the test procedure Integration of all 3G network
components on BTS selected platform. This test plan will be used to test the product in CCIN labs.
5.2. Assumptions & Dependencies

This document describes test cases valid for FAP, HNBGW and Core network elements. The
testing at CCPU labs will be done on PicoChip PC7312 and Octasic 1010 Band5 platform.
5.3. Limitations & Constraints

Limitations:
 Femtocell node will interface to Continuous Computing provided CNE (which executes
limited procedures). Femtocell node will not be tested with real or any other CN.
 CCPU will not test extra-ordinary error conditions that may occur due to disruptions
triggered by external modules such as a proprietary module added by BTS which interacts
with CCPU Femtocell solution.
Constraints:
 Testing would be done using maximum of 6 mobiles available for phase2 testing at CCIN
lab.
 Phase 2 will continue to support the same capacity as Phase 1 through PC312 board.
 Configuration of the Femtocell applications and stacks shall be done using configuration text
files only. There will be no remote configuration supported.

6. TEST OVERVIEW AND ARCHITECTURE
6.1. Architecture
The BTS FemtoNode solution shall work as a collapsed node containing the FAP and the CNE
components in one box. The Femtocell shall support high speed data exchange in DL and shall use
various architecture options for core network access.
The solution comprises of Continuous Computing provided Software that will run over Pico chip
provided platform having PHY capability and provides C Callable API. The node interfaces with
UE on radio interface (i.e. Uu) and on Iu interface towards Core network. Iu interface uses IP
transport to carry Iu Control data and Iu User Data.
Figure 1: Test Architecure
Iu SGSN
Iuh Interface Iu Interface GGSN
FAP HNBGW
HLR
IU MSC
6.2. Interface Coupling
Trillium Relay software will be used for sending and receiving data between FAP, HNBGW and
core network elements.
6.3. Target Environment
6.3.1. Type of Testing

Acceptance and Integration Testing

6.3.2. Hardware
PicoChip 7312 platform is used for Phase 1 and Octasic platform for the phase 2 and beyond.
6.3.3. Operating System

Linux OS
6.3.4. Compiler
gcc

7. DESCRIPTION OF TEST CASES:
Below are the descriptions of the test cases for BTS FAP–CNE network solution. The tests
below are defined for 3G network. The Test Cases includes for Phase 1 and for Phase 2.
7.1. Robustness Testing
Testcase [1]. : Successful Bring up association between FAP,HNBGW,CNE in any order
Purpose Test successful association between FAP,HNBGW and CNE in any order
Configuration FAP,HNBGW,CNE nodes are up and running
Test Steps Description
1. Initialization and Configuration of FAP,HNBGW and CNE nodes
2. Bring up the nodes in the order HLR, SGSN, MSC, GGSNU, GGSNC,
HNBGW and FAP respectively.
3. Stop and start the nodes in any order
4. Expect association between FAP and HNBGW,HNBGW and CNE
nodes in any order
5. Check successful association among all nodes
6. Verify the logs
Testcase [2]. Successful cleanup when MSC restarts
Purpose Test successful cleanup when MSC restarts

Configuration FAP, HNBGW and CNE nodes are running
1. Kill the MSC binary.
2. Check that HNBGW detects MSC going down.
3. Check that HNBGW sends RANAP Reset Resource towards all HNBs
having active Iu context for CS Domain. If no CS Calls are running then
there shall be not Reset Resource Msg.
4. HNBGW shall receive RANAP Reset Resource Ack from HNBs.
5. Check that HNBGW clears its local Iu connections.
6. Start the MSC binary.
7. Expect the association between HNBGW and MSC.
8. Check successful association establishment and RANAP Reset being
exchanged between HNBGW and MSC.
9. Check for successful CS call among HNBGW and MSC
10. Verify the logs for expected reply.
Testcase [3]. Successful cleanup when SGSN restarts

Purpose Test successful cleanup when SGSN restarts
1. Kill the SGSN binary
2. Check that HNBGW detects SGSN going down.
3. Check that HNBGW sends RANAP Reset Resource towards all HNBs
having active Iu context for PS Domain. If no PS calls are running there
shall be no Reset Resource msg.
4. HNBGW shall receive RANAP Reset Resource Ack from HNBs.
5. Check that HNBGW clears its Iu Connections.
6. Start the SGSN binary.
7. Expect the association between HNBGW and SGSN .
8. Check successful association and RANAP RESET being exchanged
between HNBGW and SGSN.
9. Check for successful PS call among HNBGW and SGSN
10. Verify the logs for expected reply
Testcase [4]. Successful cleanup when HNBGW restarts
Purpose Test successful cleanup when HNBGW restarts

1. Kill the HNBGW binary.
2. Check that FAP detects HNBGW association going down.
3. Check that FAP clears its local control blocks and corresponding User
plane resources.
4. Check that MSC and SGSN detects HNBGW going down.
5. Check that MSC and SGSN will clear its local control blocks and
corresponding User Plane resources..
6. Restart the HNBGW binary.
7. Expect the association between FAP and HNBGW.
8. Expect association between MSC, SGSN and HNBGW.
9. FAP and HNBGW should exchange RANAP RESET message.
10. MSC,SGSN and HNBGW should exchange RANAP RESET message.
Testcase [5]. FAP goes down and restarts when CS/PS are running

Purpose FAP goes down and comes up again when either CS/PS calls running
1. Kill the FAP binary
2. Check that HNBGW detects FAP going down.
3. Check that HNBGW sends RANAP Resource reset.
4. Check that HNBGW does Local Cleanup.
5. Check that HNBGW sends Reset Resource to the CN nodes for which
active Iu connection exist.
6. Check that MSC receives RANAP Reset Resource message from
HNBGW.
7. MSC builds and send RANAP Reset Resource Acknowledgement to
HNBGW.
8. Clean Iu control blocks and set state to IDLE for CC and MM.
9. Check that SGSN receives RANAP Reset Resource message.
10. SGSN build and send RANAP Reset Resource Acknowledgement to
HNBGW
11. Clean Iu control blocks.
12. Send tunnel management message to delete local tunnel and to send
Delete tunnel request to remote for each Iu Connection.
13. Check that GGSN receives Tunnel Delete Message.
14. Check that tunnels are deleted with its associated control blocks
15. Start the HNB binary
16. Expects the association between FAP and HNBGW
17. Check that FAP sends HNB registration to HNBGW
18. FAP and HNBGW shall exchange RANAP RESET message.
Testcase [6]. FAP goes down and restarts when no CS/PS are running
Purpose FAP goes down and comes up again when no CS/PS calls running
Configuration HNBGW and CNE running
1. Kill the FAP binary
2. Check that HNBGW detects FAP going down
3. Check that HNBGW should not send any RANAP Reset Resource
message
4. Start the FAP binary
5. Expects the association between FAP and HNBGW

6. Check that FAP sends HNB registration to HNBGW
7. FAP and HNBGW shall exchange RANAP RESET message.
8. Verify the logs for expected reply.
Testcase [7]. UE goes out of coverage
Purpose Test successful when UE going out of coverage

Configuration FAP, HNBGW and CNE running
1. Take the UE out of FAP coverage area
2. Check that FAP sends RL setup failure
3. Verify the log for expected test scenario
Testcase [8]. UE goes out of coverage when CS call is going on
Purpose Test successful when UE going out of coverage when CS call is going on
2. Check that FAP sends Radio Link failure indication and cleans up the
existing resources
3. Check that the UE comes into the coverage area, it has to attach again.
Testcase [9]. UE goes out of coverage when PS call is going on
Purpose Test successful when UE going out of coverage when PS call is going on
existing resources
Testcase [10]. UE goes out of coverage when SIM call
Purpose Test successful when UE going out of coverage during simultaneous CS

and PS call
existing resources

Testcase [11]. IMSI over IMSI Attach (without detach)
Purpose Test successful IMSI over IMSI attach (without detach)

1. Perform a UE CS Attach
2. Restart the UE and repeat the CS Attach
3. Make sure that the attach happens successfully.
Testcase [12]. GMM over GMM Attach (without detach)
Purpose Test successful GMM over GMM attach (without detach)

3. Make sure that the Attach happens successfully.
Testcase [13]. Repeated UE Power ON and Power OFF
Purpose Test successful Repeated UE Power ON and Power OFF

3. Make sure that Attach happens successfully.
Testcase [14]. Repeated UE Power ON and Power OFF when CS call is ongoing
Purpose Test successful Repeated UE Power ON and Power OFF when CS call is
ongoing
1. Establish a CS call.
2. Abort the call by powering off the UE.
3. Switch on the UE again and reestablish the CS call.
4. Repeat procedure 10 times and verify successful call setup.
Testcase [15]. Repeated UE Power ON and Power OFF when PS call is ongoing

Purpose Test successful Repeated UE Power ON and Power OFF when PS call is
ongoing
1. Establish a PS call.
2. Abort the call by powering off the UE.
3. Switch on the UE again and reestablish the PS call.
4. Repeat procedure 10 times and verify successful call setup.
Testcase [16]. Attach/detach scenario with real UE for 3 days.
Purpose To test System uptime requirement up to 3 days

1. A minimum of 100 attaches/100 detaches per day using 4 UEs
2. A minimum of 100 PS calls per day using 4 UEs
3. A minimum of 100 CS calls per day using 4 UEs
4. A minimum of 100 Simultaneous CS + PS calls per day using 4 UEs
5. A minimum of 100 MB user plane data download per day
Testcase [17]. Simultaneous CS/PS attach
Purpose To test simultaneous CS and PS attach and simultaneous CS and PS

detach
Configuration FAP HNBGW and CNE is running
1. Simultaneous CS and PS attach and verify time duration For that.
2. Execute simultaneous CS and PS detach followed by attach for 10
iterations
3. Execute CS/PS call setup
4. Robustness testing for CS/PS call and verify the logs for call stability.
For Ex: do call up then down for 10 times.
Testcase [18]. Reset for CS domain
Purpose To verify Reset Resources for CS domain

Configuration FAP,HNBGW and CNE is running
1. CS/PS call are running simultaneously

2. Kill MSC and restarts.
3. Verify HNBGW sends Reset Resource for CS domain for iuSigConId for
which calls running
4. HNB Receives Reset Resource, Clears all resources and build and send
Reset Resource Ack, check PS calls shall still be active
5. HNBGW Receives Reset Resource Ack
6. Make calls to see next call go through same UE
Testcase [19]. Reset for PS domain
Purpose To verify Reset resources for PS domain

Configuration FAP,HNBGW and CNE is running
1. CS/PS calls running simultaneously
2. Kill SGSN and restart
3. Verify HNBGW sends Reset Resource for PS domain for iuSigConId
for which calls running
4. HNB Receives Reset Resource, Clears all resources and build and send
Reset Resource Ack, check CS calls shall still be active
5. HNBGW Receives Reset Resource Ack

6. Make calls to see next PS call go through same UE
Testcase [20]. Reset towards both HNB and CN
Purpose To verify RESET towards HNB and CN

Configuration FAP, HNBGW and CNE is running
1. CS/PS calls running simultaneously
2. Kill HNBGW and restart
3. Verify HNBGW sends Reset towards both HNB and core network
4. HNB and MSC sends Reset Ack
5. Make CS and PS calls which shall be successful

Testcase [21]. Test for Debug Logging Enhancements
Purpose Make sure all the modules are up and running with the “Debug
Logging” enhancements without the introduction of “Debug Mask”
field in the layer configuration files
Configuration Layer Generic Configuration files without the “dbgMask” field
1. Compile each module with the compile time flag “DEBUGP” enabled
in the respective make files.
2. Bring up all the modules with the layer’s “gencfg” files not having the
“dbgMask” (Generic Configuration Field used to Enable/Disable Debug
Mask) field.
3. Make sure all the modules are brought up successfully.
4. Verify that none of the debug prints are seen on the console/logs.
Testcase [22]. Case for Enabling the Debug Mask
Purpose Testing with debug mask enabled

Configuration Layer Generic Configuration files with the “dbgMask” field 0xFF
1. Compile each module namely HLR, MSC, SGSN, GGSN, HNBGW and
finally FAP with the compile time flag “DEBUGP” enabled in the
respective make files
2. Bring up all the modules with the layer’s “gencfg” files having the
“dbgMask” field 0xFF
4. Verify that all the debug prints are seen on the console/logs.
Testcase [23]. Case for Enabling the Debug Mask selectively
Purpose Debug Mask Enabled Selectively

Configuration Layer Generic Configuration files with the “dbgMask” field having
selected masks.
“dbgMask” field having selected masks (SI/MI/UI/LI/LYR = 1/2/4/8/16)
8. Verify that all the debug prints seen are only for those whose masks are
enabled.

Testcase [24]. Case for Disabling the Debug Mask
Purpose Debug Mask Disabled

Configuration Layer Generic Configuration files with the “dbgMask” field disabled
“dbgMask” field disabled [ Zero ]
4. Verify that none of the debug prints are seen on the console/logs.
7.2. Soak Testing

Testcase [25]. Long Duration of 1 CS voice call
Purpose Test successful long duration of 1 CS voice call (24 hours) with 2 UEs
1. Set up a CS call between 2 UEs
2. Verify that a CS call lasts for 24 hours duration
3. Verify the logs for call stability and stable data rates.
Testcase [26]. Long Duration of 2 CS voice call
1. Set up a CS voice call between 4 UEs
2. Verify that 2 CS voice call lasts for 24 hours duration
Testcase [27]. Long Duration of 1 CS video call
1. Set up a CS video call between 2 UEs
2. Verify that CS video call lasts for 24 hours duration
Testcase [28]. Long Duration of 2 CS video call
1. Set up a 2 CS video call between 4 UEs
2. Verify that 2 CS video call lasts for 24 hours duration
Testcase [29]. Make and release of 10 CS voice calls
Purpose Test successful make and release of 10 CS voice calls back to back using
2 UEs
1. Set up a CS voice call between 2 UEs repeatedly for 10 times
2. Verify that CS voice call happen for 10 times
Testcase [30]. Make and release of 10 CS video calls
Purpose Test successful make and release of 10 CS video calls back to back using
2 UEs
1. Set up a CS video call between 2 UEs repeatedly for 10 times
2. Verify that CS video call happen for 10 times
Testcase [31]. Make and release of 10 PS64 calls
Purpose Test successful make and release of 10 PS64 calls back to back using 1
UE
1. Set up a PS64 call between 1 UE repeatedly for 10 times
2. Verify that PS64 call happen for 10 times

UE
UE
Testcase [34]. Make and release of 10 HSDPA calls
Purpose Test successful make and release of 10 HSDPA calls back to back using
1 UE
1. Set up a HSDPA call between 1 UE repeatedly for 10 times
2. Verify that HSDPA call happen for 10 times
Testcase [35]. Make and release of 10 HSUPA calls
Purpose Test successful make and release of 10 HSUPA calls back to back using
1 UE
1. Set up a HSUPA call between 1 UE repeatedly for 10 times
2. Verify that HSUPA call happen for 10 times
Testcase [36]. Long duration of 4 HSDPA calls
Purpose Test successful long duration of 4 HSDPA calls using 4 UEs


1. Set up a HSDPA call between 4 UEs
2. Verify that HSDPA call lasts for 2 hours duration
Testcase [37]. Long duration of 2 HSDPA and 2 HSUPA calls
Purpose Test successful long duration of 2 HSDPA and 2 HSUPA calls using 4
UEs. HSUPA calls are not possible with Octasic 1010 as it does not
support them.
1. Set up a HSDPA call between 2 UEs and 2HSUPA calls between 2 UEs
2. Verify that 2 HSDPA and 2 HSUPA call lasts for 2 hours duration
Testcase [38]. Long duration of 2 HSDPA and 1 CS voice calls
Purpose Test successful long duration of 2 HSDPA and 1 CS voice calls using 4
UEs
1. Set up a HSDPA call between 2 UEs and 1CS voice calls between 2 UEs
2. Verify that 2 HSDPA and 1 CS voice call lasts for 2 hours duration
Testcase [39]. Long duration of 2 HSUPA and 1 CS voice calls
Purpose Test successful long duration of 2 HSUPA and 1 CS voice calls using 4
UEs. This test case does not apply to Octasic 1010 since HSUPA calls
are not supported.
1. Set up a HSUPA call between 2 UEs and 1CS voice calls between 2 UEs
2. Verify that 2 HSUPA and 1 CS voice call lasts for 2 hours duration
Testcase [40]. Long duration of 2 HSUPA and 1 CS video calls
Purpose Test successful long duration of 2 HSUPA and 1 CS video calls using 4
are not supported.
1. Set up a HSUPA call between 2 UEs and 1CS video calls between 2 UEs
2. Verify that 2 HSUPA and 1 CS video call lasts for 2 hours duration
Testcase [41]. 2 HSPA and 1 CS calls multiple times from different UEs
Purpose Test successful 2 HSPA and 1 CS calls multiple times from 2 different
are not supported
1. Set up a HSUPA call between 2 UEs and 1CS call between 2 UEs
2. Make and break the CS calls between 2 UEs multiple times
3. Verify that 2 HSUPA and multiple time of 1 CS call happen
Testcase [42]. CS/PS call multiple times between the UE’s back to back
Purpose To test make and release of 10 CS and PS calls back to back

1. Set up a CS/PS call between 2 UEs repeatedly for 10 times
2. Verify that CS/PS call happen for 10 times
7.3. Capacity Testing
Testcase [43]. 6 UE CS voice call
Purpose Test successful capacity of 6 UE CS voice calls

4. Set up a 6 CS voice call between 6 UEs
5. Check for the capacity of 6 CS calls lasts
6. Verify the logs for stable data rates.
Testcase [44]. 6 UE CS video calls
Purpose Test successful capacity of 6 UE CS video calls

1. Set up a 6 CS video call between 6 UEs
2. Check for the capacity of 6 CS calls lasts
Testcase [45]. 6 UE PS call
Purpose Test successful capacity of 6 UE PS calls

1. Set up a PS call among all 6 UEs
2. Check for the capacity of 6 UEs doing PS call
Testcase [46]. 6 UE doing CS and PS call
Purpose Test successful capacity of 6 UE doing CS and PS call

1. Set up a CS and PS call among all 6 UEs
2. Check for the capacity of 6 UEs doing CS and PS calls
7.4. Performance Testing
Testcase [47]. CPU Usage measurement for 6 UE CS calls
Purpose Test successful CPU usage measurement for 6 UEs CS calls

1. Set up a 6 CS call between 6 UEs
2. Check for the 6 CS calls lasts
3. Check for the CPU usage for 6 UEs
Testcase [48]. CPU Usage measurement for 6 UE PS calls
Purpose Test successful CPU usage measurement for 6 UEs PS calls


5. Set up 6 PS call
6. Check for the 6 PS calls lasts
7. Check for the CPU usage for 6 UEs
7.5. Packaging
On installation of package, the following directories are created within / 9000285/:
• build – All FAP, HNBGW and CNE nodes make files
• config – Static configuration files.
• fap – Source files of fap.
• ggsnc – Source files of ggsnc
• ggsnu – Source files of ggsnu
• hlr – Source files of hlr
• hnbgw – Source files files of hnbgw
• lib – FAP,HNBGW and CNE nodes libraries
• msc – Source files of msc
• scripts – scripts
• sgsn – Source files of sgsn
• src – Source files of common and layer manager files
7.6. Licensing
Depending upon the feature set requested, appropriate license file (license.txt) must be
copied to /opt/ss7card/config/ folder. To obtain or upgrade license.txt, contact Continuous
Computing sales representative.
7.7. Documentation
Following documents are available:
[1] CCPU Document No. 1092206: “RRC Service Definition”
[2] CCPU Document No. 1092204: “RLC Service Definition”
[3] CCPU Document No. 1092241: “MAC Service Definition”
[4] CCPU Document No. 1092180: “RANAP Service Definition”
[5] CCPU Document No. 1092207: “SUA Service Definition”
[6] CCPU Document No. 1092291: “SCTP Service Definition”
[7] CCPU Document No. 1092158: “TUCL Service Definition”
[8] CCPU Document No. 1092362: “IuUP Service Definition”
[9] CCPU Document No. 1100044: “RPT Interface Service Definition”
[10] CCPU Document No. 1100035: “HRT Interface Service Definition”
[11] CCPU Document No. 1100055: “RRU Interface Service Definition”
[12] CCPU Document No. 1100052: “RLU Interface Service Definition”
[13] CCPU Document No. 1100062: “FPU Interface Service Definition”
[14] CCPU Document No. 1100077: “LXT Interface Service Definition”
8. CONFIGURATION
8.1. Creating configuration Files.
Every product will have a creCfg file and an optional configInfo.txt file. These files are
responsible for creating the configuration files. The creCfg script reads the configInfo.txt to set
variable parameters such as IP address and PLMN Id.
8.2. Sample configInfo.txt
Below is a sample configInfo.txt file taken from SGSN product.
1 # IP ADDRESSES
2 # ---------------
3 # Change the IP addresses in this section
4 # as appropriate
5 # ---------------
6 SGSN_IPADDR 192.168.1.102
7 HLR_IPADDR 192.168.1.103
8 HNBGW1_IPADDR 192.168.1.105
9 HNBGW2_IPADDR 192.168.0.94
10 GGSNC_IPADDR 192.168.1.104
11 GGSNU_IPADDR 192.168.1.104
12
13
14
15 #HNBGW specific data
16 #-----------------
17 # The following parameters do not need to be changed
18 # for the demo purposes
19 #-----------------
20 RNCID_HNBGW1 257
21 MCC_HNBGW1 256
22 MNC_HNBGW1 144
23 LAC_HNBGW1 4660
24 RAC_HNBGW1 86
25 DPC_HNBGW1 256
26
27 RNCID_HNBGW2 400
28 MCC_HNBGW2 256
29 MNC_HNBGW2 144
30 LAC_HNBGW2 4660
31 RAC_HNBGW2 86
32 DPC_HNBGW2 128

8.3. Sample protocol configuration file.
The creCfg script generates configuration files for each protocol layers. They contain the
configuration values of each protocol layer. A sample configuration file (it.genCfg) is shown
below.
#############################################
# IT (M3UA) general
#############################################
beginCfg itGen
nodeType = 2 #LIT_TYPE_ASP
dpcLrnFlag = 1 #TRUE
maxNmbNSap = 1
maxNmbSctSap = 1
maxNmbNwk = 1
maxNmbRtEnt = 15
maxNmbDpcEnt = 25
maxNmbPs = 10
maxNmbPsp = 10
maxNmbMsg = 20
drkmSupp = 0
drstSupp = 0
qSize = 2000
congLevel1 = 500
congLevel2 = 1000
congLevel3 = 1500
tmrRestart TRUE 5
tmrMtp3Sta TRUE 5
tmrAsPend TRUE 10
tmrHeartbeat FALSE 15
tmrAspUp1 TRUE 2
tmrAspUp2 TRUE 2
nmbAspUp1 = 3
tmrAspDn TRUE 2
tmrAspM TRUE 2
tmrDaud TRUE 5
tmrDrkm TRUE 5
maxNmbRkTry = 3
tmrDunaSettle TRUE 5
timeRes = 1000
endCfg
8.4. Sample HLR database configuration

The HLR database is currently organized as a flat file. Its sample configuration is shown below.
#########################################
# HLR UE Database
#########################################

beginCfg ueDB
numUEEntries = 4
# UE 0
########################
UE_Entry = 1
IMSI_numDigits = 15
IMSI 0 0 2 0 2 0 0 0 8 6 7 5 3 4 0
TMSI = 135
MSISDN 9 8 4 5 0 0 0 3 4 0
LAC = 4660
Authentication_Key 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15
15 15 15 15 15 15 15 15 15 15 15 15 15 15
SQN 2 6 2 6 3 0 0 0 1 3 15 0
UE_Status = 1
# UE 1
########################
UE_Entry = 2
IMSI_numDigits = 15
IMSI 3 1 0 5 2 0 0 0 8 6 7 5 3 3 1
TMSI = 208
MSISDN 9 8 4 5 0 0 0 3 3 1
LAC = 4660
15 15 15 15 15 15 15 15 15 15 15 15 15 15
SQN 2 6 2 6 3 0 0 0 1 4 0 1
UE_Status = 1
# UE 2
########################
UE_Entry = 3
IMSI_numDigits = 15
IMSI 3 1 0 5 2 0 0 0 8 6 7 5 3 0 9
TMSI = 243
MSISDN 9 8 4 5 0 0 0 3 0 9
LAC = 4660
15 15 15 15 15 15 15 15 15 15 15 15 15 15
SQN 2 6 2 6 2 6 0 0 0 8 15 3
UE_Status = 1
# UE 3
########################
UE_Entry = 4
IMSI_numDigits = 15
IMSI 0 0 1 0 9 0 1 2 3 4 5 6 2 0 9
TMSI = 146

MSISDN 9 8 4 5 0 0 0 2 0 9
LAC = 4660
Authentication_Key 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 10 10 11 11 12
12 13 13 14 14 15 15
SQN 2 11 0 0 0 0 0 0 9 0 6 11
UE_Status = 1
endCfg

9. TEST COMPLETION AND STOP CRITERIA
All the test cases mentioned above for FAP and CNE Integrated solution must be passed to
conclude the testing as complete.

10. REFERENCES
[1] 3GPP TS 25.401: “UTRAN Overall Description”.
[2] 3GPP TS 23.110: “UMTS Access Stratum Services and Functions”.
[3] 3GPP TS 25.412: “UTRAN Iu Interface Signalling Transport”.
[4] 3GPP TS 25.413 – v5.12.0: “UTRAN Iu Interface RANAP Signalling”.
[5] 3GPP TS 25.414 – 5.7.0: “UTRAN Iu Interface Data Transport and Transport Signalling”
[6] 3GPP TS 25.415: “UTRAN Iu Interface User Plane Protocols”.
[7] 3GPP TS 25.301: “Radio Interface Protocol Architecture”.
[8] 3GPP TS 25.401: “UTRAN overall description”.
[9] 3GPP TS 25.321 – v5.14.0: “Medium Access Control (MAC) protocol specification”.
[10] 3GPP TS 25.322 – v5.13.0: “Radio Link Control (RLC) protocol specification”
[11] 3GPP TS 25.331 – v5.22.1: “Radio Resource Control (RRC) protocol specification”.
[12] 3GPP TS 24.008 – v5.16.0: “Mobile radio interface Layer3 specification; Core network
protocols”.
[13] PC83xx-078 v1.4: “PC83xx Layer1 API Specification from picoChip”

9450 Carroll Park Drive
San Diego, CA 92121-2256
858-882-8800
www.ccpu.cm

CVP - BTS - FAP - CNE - v1 1

Uploaded by

Copyright:

Available Formats

CVP - BTS - FAP - CNE - v1 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CVP - BTS - FAP - CNE - v1 1

Uploaded by

Copyright:

Available Formats

BTS 3G Network in a Box

Conformance Verification Plan

Continuous Computing Corporation

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

4.3. Document Organization

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

4.4. Release History

Version Date Author (s) Reviewer Description

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Feature List for Phase -2:

5.2. Assumptions & Dependencies

5.3. Limitations & Constraints

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Figure 1: Test Architecure

6.2. Interface Coupling

6.3. Target Environment

6.3.1. Type of Testing

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

6.3.3. Operating System

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

7.1. Robustness Testing

Testcase [1]. : Successful Bring up association between FAP,HNBGW,CNE in any order

Testcase [2]. Successful cleanup when MSC restarts

Purpose Test successful cleanup when MSC restarts

Testcase [3]. Successful cleanup when SGSN restarts

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Testcase [4]. Successful cleanup when HNBGW restarts

Purpose Test successful cleanup when HNBGW restarts

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Testcase [7]. UE goes out of coverage

Purpose Test successful when UE going out of coverage

Testcase [8]. UE goes out of coverage when CS call is going on

Testcase [9]. UE goes out of coverage when PS call is going on

Testcase [10]. UE goes out of coverage when SIM call

Purpose Test successful when UE going out of coverage during simultaneous CS

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Testcase [11]. IMSI over IMSI Attach (without detach)

Purpose Test successful IMSI over IMSI attach (without detach)

Testcase [12]. GMM over GMM Attach (without detach)

Purpose Test successful GMM over GMM attach (without detach)

Testcase [13]. Repeated UE Power ON and Power OFF

Purpose Test successful Repeated UE Power ON and Power OFF

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Testcase [16]. Attach/detach scenario with real UE for 3 days.

Purpose To test System uptime requirement up to 3 days

Testcase [17]. Simultaneous CS/PS attach

Purpose To test simultaneous CS and PS attach and simultaneous CS and PS

Testcase [18]. Reset for CS domain

Purpose To verify Reset Resources for CS domain

Continuous Computing Corporation Conformance Verification Plan BTS Network in a Box

Testcase [19]. Reset for PS domain

Purpose To verify Reset resources for PS domain

5. HNBGW Receives Reset Resource Ack