CS8 Development Library UI. Appendix: Additional Custom API Reference

Transcription

1 CS8 Development Library UI Appendix: Additional Custom API Reference

2 Spirent 541 Industrial Way West Eatontown, NJ USA Web: AMERICAS SPIRENT EUROPE AND THE MIDDLE EAST +44 (0) ASIA AND THE PACIFIC This manual applies to CS8 Development Library Version 1.20 or higher. Page Part Number: , Version A1 Copyright 2012 Spirent. All Rights Reserved. All of the company names and/or brand names and/or product names referred to in this document, in particular, the name Spirent and its logo device, are either registered trademarks or trademarks of Spirent plc and its subsidiaries, pending registration in accordance with relevant national laws. All other registered trademarks or trademarks are the property of their respective owners. The information contained in this document is subject to change without notice and does not represent a commitment on the part of Spirent. The information in this document is believed to be accurate and reliable; however, Spirent assumes no responsibility or liability for any errors or inaccuracies that may appear in the document.

3 Table of Contents 1. Introduction Overview API Usage Description ConfigureLayer3MessageTimelineChart CPowerRampAction QueryLayer3MessageLogging CTransferQuery CRegisterQuery CRRStateQuery CActiveSetQueryCheck QueryLTEResultQueue Layer3MessageLogging... 5

4 1. Introduction 1.1. Overview This document provides additional information on the CS8 Development Library UI module. In addition to the basic functional APIs provided by Development Library Services (DLS) through the CS8 Development Library UI, there are nine additional custom APIs. These are integrated in the DLTestCaseSteps step assembly. Each API is developed from inherent DLS basic APIs. The additional custom APIs are: ConfigureLayer3MessageTimelineChart CPowerRampAction QueryLayer3MessageLogging CTransferQuery CRegisterQuery CRRStateQuery CActiveSetQuery QueryLTEResultQueue Layer3MessageLogging Note that the following APIs in DLTestCaseSteps step assembly are being reviewed and subject to change. Do not use the following APIs: LogEthernetPacket QueryPDNBearerRTPRelationship QueryRTPResultQueue QueryVOIPTrafficExistence QueryVoiceCodecInfo

5 CS8 Development Library UI: Appendix 3 2. API Usage Description 2.1. ConfigureLayer3MessageTimelineChart Define which message(s) will be finally displayed in the procedure chart of test results by filtering logged messages. In general, this step must be used with the step QueryLayer3MessageLogging in combination CPowerRampAction Trigger LTE or UMTS cell power to ramp up/down. It will read RAN_Name to decide which cell to ramp power, and then makes changes in a finite loop defined by Total_Steps. Other parameters are used for defining power ramp properties. Step Parameters RAN_Name Target cell, Cell 1 for UMTS, while ecell 1 for LTE. Starting_Power Step_Delay Step_Size Total_Steps Starting point of power ramp( Unit: dbm) Delay in seconds, to execute next ramp Ramp size in every step Cycle times 2.3. QueryLayer3MessageLogging Verify the message flow pattern or/and the counter pattern as shown in Figure 2-1. Verification is based on the monitored message configured in API Layer3MessageLogging discussed in Section 2.8 on page 5. Before verifying messages, configure them using the Layer3MessageLogging custom API. Editor Parameters Instances Max/Min Duration Tolerance The range of permissible message number Time span for checking message Positive or Negative difference from duration

6 4 CS8 Development Library UI: Appendix Figure 2-1: Query Editor Interactive UI 2.4. CTransferQuery Check if current data transfer is active (throughput is non-zero) or inactive (throughput is zero) CRegisterQuery Check if UE registration state matches the requested Registration Type. The property RAN_Name illustrates target cell of this step, Cell 1 for UMTS and ecell 1 for LTE CRRStateQuery Check if LTE RRC state matches the parameter SetRRCState CActiveSetQueryCheck Check if the UMTS active state matches the SetCurrentActiveSet parameter.

7 CS8 Development Library UI: Appendix QueryLTEResultQueue Check if a specified Result Type exists in Result Queue of CS8 Interactive Tester. Step Parameters Query Type FindFirstResult: Always find the requested result from the top* of Result Queue. FindNextResult: Find the requested result from current index of Result Queue. FindLastResult: Always find the requested result from the bottom of Result Queue. *The top means the first received result. TimeOut The number of seconds (a positive 32-bit integer) to wait for the result Layer3MessageLogging Filter and log selected LTE, UMTS, and GSM messages from Development Library Service trace. Select Logging>Layer3MessageLogging to edit logging property, as shown in Figure 2-2. Enable the desired messages in LoggingEditor, as shown in Figure 2-3. The Logging starts when LoggingEnabled property is set to True, and stops when the property is set to False. Figure 2-2: Layer3MessageLogging Interactive UI Figure 2-3: Logging Editor Interactive UI The following Log files are generated and saved in the corresponding Test Results folder while executing "Layer3MessageLogging" and "QueryLayer3MessageLogging" APIs:

8 6 CS8 Development Library UI: Appendix MMList.xml: List of Monitored Messages that includes all selected messages in the Logging Editor of the "Layer3MessageLogging" API. MessageQLoggerResult.xml: Logged message filtered by MMList.xml. QueryResultList.xml: Includes messages, counter patterns, and contents of MessageQLoggerResults.xml for all Query steps of given test case.