Cap3 Gprs Overview

07/04/23 TestData CAP3 GPRS1

Test DataCAP3 GPRS


Contents• Overview• Introduction• CAP3 GPRS Overview• CAP3 GPRS Testing Environment• CAP3 GPRS Test Cases• CAP3 GPRS Features• Practical Exercises• Questionnaire• Conclusion• Forms to be filled out


Overview• Presenter : Tina Cadogan• Duration: 2 hours• Material delivery and format:

• PPT, • KT pages <http://link>• Test cases <http://link>• Questionnaire <http://link>

• Main sections of KT for CAP3 GPRS:– PPT Presentation : 1 hour

• Provides an overview of CAP3 GPRS Testing

– Test specification: 1 hour• Example of Test Specification• Sample Test Cases

– Practicals: 3 Hours• Configuring the system• Running Test Cases

– Exercises: 20 min• Questionnaire

http://link/


Introduction• CAP3 GPRS Overview• CAP3 GPRS Test Environment• Tracing on a Test Environment• CAP3 GPRS Test Cases• CAP3 GPRS Features• After this section the attendees will understand the following

– Understand CAP3 GPRS– Know how to execute test cases– Write/expand testcases for CAP3 GPRS


CAP3 GPRS Overview• Requests to charge for a GPRS Session are delivered over SS7 to the

TecnoTree PrePaid system• A GPRS Session will consist of 1 Create & Reserve message, multiple Debit

& Reserve messages and either 1 Debit & Release or Release message• The Create & Reserve message sends a request to the Prepaid system to

create a GPRS session. The Prepaid system will grant x amount of Volume in the Reserve part for this GPRS session

• The Debit & Reserve message will indicate how much Volume was used in the Debit part and again the Prepaid system will grant x amount Volume in the Reserve part

• The Debit & Release message will indicate how much Volume was used in the Debit part. The Release part will indicate to the Prepaid system that this GPRS session should be terminated


CAP3 GPRS Overview• A Release message on it’s owns also indicates to the Prepaid system that

this GPRS session should be terminated• The PrePaid system rates/charges for the CAP3 GPRS Session• The PrePaid system generates CDRs (Call Detail Records) which indicate

the cost of the GPRS Session, the number of Debits in the GPRS Session and balances that were charged.

– A CDR of Transaction Type 308 is produced for every Debit in the GPRS session– A CDR of Transaction Type 310 is produced to give an overall summary of the GPRS

session• The PrePaid system returns a response to the network indicating if the

charge was successful or not


CAP3 GPRS Testing Environment 1

• The following environment is used to test CAP3 GPRS

IOP cardTorus/GPRS

Proxy

CGW

SDPProtoProto Test

Hardness


CAP3 GPRS Testing Environment 2

• Proto is a test harness and is used to generate a GPRS session. It is built into the Torus process

• The IOP card is used to route the GPRS to the Charging Gateway (CGW)• CGW is used to rate and charge for the GPRS, generate CDRs

– The GPRS is handled by the Payment Engine on the CGW• The Payment Engine verifies the Subscriber, Account Balances• The Payment Engine requests a rate from the Rating Engine• The Payment Engine generates the CDR and updates the Account Balances • The Payment Engine returns a result to the IOP card indicating success/failure

• SDP is the database where the Subscriber and Rating Information is stored


Tracing on CAP3 GPRS Test Environment

• When running a CAP3 GPRS Test, the majority of the tracing is done on the CGW

• On the CGW tracing is performed on the Payment Engine and the Rating Engine

• To enable tracing the following steps must be performed– Using the seer, enable tracing (t 5 command)– On the CGW, “cd $CHARGING_HOME/trace”– “tail –f PaymentEngine_1.trace_PaymentEngine_1”– This will output the tracing to the console window– To trace on the Rating Engine, “tail –f RatingEngine_1.trace_RatingEngine_1”

• Link to Sample Payment Engine trace• Link to Sample Rating Engine trace


CAP 3 GPRS Test Cases• CAP3 GPRS Test Cases are defined in a Word Document• A CAP3 GPRS test case has the following format:

– Setup the Database (Subscriber Balances, any other fields)– Send the CAP3 GPRS session using Proto– Verify the CDR generated is correct and what is expected– Verify the Subscribers balance has been correctly updated– Reset the Database to a known state (Reset Balances, Fields to known states)

• Link to Sample Test Case


CAP 3 GPRS Features 1• CAP3 GPRS has a number of different features that are tested• Subscriber Life Cycle

– A Subscriber can be in a Valid/Invalid Account Status– A Subscriber can be in a Valid/Invalid Service Status

• Packages– A Subscriber can have a number of different Packages that they can use– Example Packages are Tailored Commercial, Included Commercial,

Promotional• Rating

– The GPRS is charged different Rates depending on the Subscriber Location, Time of day, tariff plans, profiles


CAP 3 GPRS Features 2• Error Test Cases

– GPRS received for an Unknown Subscriber– Subscriber has Insufficient Funds for the cost of the GPRS

• Statistics– Verify that statistics are correctly updated


Practical Exercises• The practical exercises consist of the following

– Run an existing test case using Proto– Get the test case to pass– Modify a parameter in the DB that will cause the test case to fail– Re-run the test case and verify it failed for the correct reason– Reset the DB parameter and verify the test case passes– Write a new CAP3 GPRS test case


Questionnaire• 10 multiple choice questions • 20 minutes to complete• Based on contents of KT material• Expect 80% pass rate


Conclusion• CAP3 GPRS Overview• CAP3 GPRS Test Environment• Tracing on Test Environment• CAP3 GPRS Test Cases• CAP3 GPRS Features


Forms to be filled out• Attendance

– Passed around

• Feedback form– feedback form


Further Reading• Some extra reading links:

• GPRS CAP3 Charging

Cap3 Gprs Overview

Documents

Transcript of Cap3 Gprs Overview