OPEN BASE STATION ARCHITECTURE INITIATIVE

Transcription

1 OPEN BASE STATION ARCHITECTURE INITIATIVE Conformance Test Cases Appendix C RP interface and TM module Version.00 Issue.00 (4)

2 FOREWORD OBSAI description and specification documents are developed within the Technical Working Group of the Open Base Station Architecture Initiative Special Interest Group (OBSAI SIG). Members of the OBSAI TWG serve voluntarily and without compensation. The description and specifications developed within OBSAI represent a consensus of the broad expertise on the subject within the OBSAI SIG. The OBSAI SIG uses the following terminology in the specifications: Ä Ä Ä "shall" expresses a provision that is binding "should" and "may" expresses non-mandatory provisions "will" expresses a declaration of purpose on the part of the OBSAI SIG. It may be necessary to use "will" in cases where the simple future tense is required Use of an OBSAI reference or specification document is wholly voluntary. The existence of an OBSAI Specification does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the OBSAI Specification. Furthermore, the viewpoint expressed at the time a specification is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the specification. Every OBSAI Specification is subjected to review in accordance with the Open Base Station Architecture Initiative Rules And Procedures. Implementation of all or part of an OBSAI Specification may require licenses under third party intellectual property rights, including without limitation, patent rights (such a third party may or may not be an OBSAI Member). The Promoters of the OBSAI Specification are not responsible and shall not be held responsible in any manner for identifying or failing to identify any or all such third party intellectual property rights. The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of OBSAI Member s customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of OBSAI Management Board. The document has been prepared for use by professional and properly trained personnel, and the customer assumes full responsibility when using it. OBSAI Management Board, Marketing Working Group and Technical Working Group welcome customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between OBSAI members. However, the OBSAI Management Board, Marketing Working Group or Technical Working Group have made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Issue.00 (4)

3 OBSAI liability for any errors in the document is limited to the documentary correction of errors. OBSAI WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it. This document and the product it describes are considered protected by copyright according to the applicable laws. OBSAI logo is a registered trademark of Open Base Station Architecture Initiative Special Interest Group. Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright Open Base Station Architecture Initiative Special Interest Group. All rights reserved. Users are cautioned to check to determine that they have the latest edition of any OBSAI Specification. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specific applications. When the need for interpretations is brought to the attention of OBSAI, the OBSAI TWG will initiate action to prepare appropriate responses. Since OBSAI Specifications represent a consensus of OBSAI Member s interests, it is important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason OBSAI and the members of its Technical Working Groups are not able to provide an instant response to interpretation requests except in those cases where the matter has previously received formal consideration. Comments on specifications and requests for interpretations should be addressed to: Peter Kenington Chairman, OBSAI Technical Working Group Linear Communications Consultants Ltd. pbk@linearcomms.com Issue.00 3 (4)

4 Contents Summary of changes...7 Scope RP/TM test cases Fast Ethernet Ports Throughput and Latency Gbits Ethernet Ports throughput and latency Fast Ethernet Ports throughput and latency requalification after overload Short circuit tolerance Clock Management Functions Test setups Glossary Abbreviations Definition of Terms... 6 References OBSAI IEEE IETF ITU-T...4 Issue.00 4 (4)

5 Figures Figure - OBSAI BTS System reference...8 Figure Test Setup F...9 Figure 3 Test Setup G...0 Issue.00 5 (4)

6 List of Tables Table - Abbreviations... Issue.00 6 (4)

7 Summary of changes Version Approved by Date 0.0 Approved by Test sub group with corrections 9-aug Updated according to review comments 07-dec Updated according to review comments 0-dec Test cases moved into Common test cases for all modules specification.00 Approved by MB -jan Issue.00 7 (4)

8 Scope This document specifies the test methods and conformance requirements for the OBSAI TM module and the RP interface. Also such test cases, which are common for all OBSAI modules and interfaces are specified in [OBSAI COMMON]. An OBSAI module and its RP interface will be deemed to have conformed to the common OBSAI specifications, if it fulfills the minimum acceptance criterion of all test cases presented in this document. RP RP3 Iub or Abis Transport Block BaseBand Block RF Block Power Proprietary Block RP4 RP 9 Control and Clock Block Control Traffic Clock Power 0 Figure - OBSAI BTS System reference Issue.00 8 (4)

9 3 3 RP/TM test cases This section contains test cases for the RP interface and the Transport module. Issue.00 9 (4)

10 3. Fast Ethernet Ports Throughput and Latency Test Case ID: Test Case status: Relevant to: Source reference: Test Purpose: Test Models: RP/TM_Fabric port test_345 Mandatory TM [OBSAI RP], [RFC 544], [RFC 4] This single test makes two RFC 544 measurements throughput and latency. The purpose of the test is to verify that the required throughput at various packet sizes can be maintained and the latency at that rate is within the required boundary. All ports as defined in class,,3 are involved and used in full-duplex manner. source 00% 00% 00% 00% 00% 00% 00% 00% 00% 00% destination L Packet Size 64 bytes 8 bytes 56 bytes 5 bytes 768 bytes 04 bytes 80 bytes 58 bytes Percentage values in the picture refer to the required load. The required load for all ports is selected and throughout the execution, the packet size is changed from its smallest to its largest value (see the above table). The Latency is measured for each port. Method of Test: Use a measurement device to generate packets from all source ports. At the destination ports the L latency and the received number of packets will be measured. Test Conditions: Ä Assumptions and Limitations: Ä Electrical conformance tests according to IEEE80.3 specification has been covered before this test case. Ä Conformance tests according to IPv6 (RFC460) and IPv4 (RFC79) has been covered before this test case. Ä DUT is up and running and connected to Test equipment and Test manager Ä Suitable Address table is inserted Ä All DUT ports are configured to fast Ethernet links (00Mbits) Procedure:. Send packets of a fixed size from all sources to all destinations. Test duration is a minimum of 0sec 3. Measure the number of packets transmitted and received on all streams to ensure that no packets are lost or switched to the wrong port 4. Measure the latency between all source and destination ports Issue.00 0 (4)

11 Repeat step -4 with all different packet sizes (see table above). Test setup: Test Inventory: - DUT - Tester backplane - Tester Power Supply - Test equipment with FE/GE ports - Test manager See Test Setup F Minimum acceptance criteria: - The transport module shall fulfill the latency requirement according to the OBSAI RP specification and optional packet loss requirement Parameters Value Limit Comments The Data Link layer latency Max 00µs Ethernet switching delay between any two interfaces. Packet loss No packet loss General quality measure (optional) Issue.00 (4)

12 3. Gbits Ethernet Ports throughput and latency Test Case ID: Test Case status: Relevant to: Source reference: Test Purpose: Test Models: RP/TM_Fabric port test_309 Mandatory TM [OBSAI RP], [RFC 544], [RFC 4] This single test makes two RFC 544 measurements throughput and latency. The purpose of the test is to verify that the required throughput at various packet sizes can be maintained and the latency at that rate is within the required boundary. All ports as defined in class,,3 are involved and used in full-duplex manner. source 00% 00% 00% 00% 00% 00% 00% 00% 00% 00% destination L Packet Size 64 bytes 8 bytes 56 bytes 5 bytes 768 bytes 04 bytes 80 bytes 58 bytes Percentage values in the picture refer to the required load. The required load for all ports is selected and throughout the execution, the packet size is changed from its smallest to its largest value (see the above table). The Latency is measured for each port. Method of Test: Use a measurement device to generate packets from all source ports. At the destination ports the L latency and the received number of packets will be measured. Test Conditions: Ä Assumptions and Limitations: Ä Electrical conformance tests according to IEEE80.3 specification has been covered before this test case. Ä Conformance tests according to IPv6 (RFC460) and IPv4 (RFC79) has been covered before this test case. Ä DUT is up and running and connected to Test equipment and Test manager Ä Suitable Address table is inserted Ä FP0 and FP DUT ports are configured to Gigabit Ethernet links (Gbits) Procedure:. Send packets of a fixed size from all sources to all destinations. Test duration is a minimum of 0sec 3. Measure the number of packets transmitted and received on all streams to ensure that no packets are lost or switched to the wrong port 4. Measure the latency between all source and destination ports Issue.00 (4)

13 Repeat step -4 with all different packet sizes (see table above). Test setup: Test Inventory: - DUT - Tester backplane - Tester Power Supply - Test equipment with FE/GE ports - Test manager See Test Setup F Minimum acceptance criteria: - The transport module shall fulfill the latency requirement according to OBSAI RP specification and optional packet loss requirement. Parameters Value Limit Comments The Data Link layer latency Max 00µs Ethernet switching delay between any two interfaces. Packet loss No packet loss General quality measure (optional) Issue.00 3 (4)

14 3.3 Fast Ethernet Ports throughput and latency requalification after overload Test Case ID: Test Case status: Relevant to: Source reference: Test Purpose: Test Models: RP/TM_Fabric port test_538 Optional TM [OBSAI RP], [RFC 544], [RFC 4] This single test makes two RFC 544 measurements throughput and latency. The purpose of the test is to verify that the required throughput at various packet sizes can be maintained and that the latency at that rate is within the required boundary. An overload condition is imposed using normal traffic (see diagram below). It will be checked that overload occurs, but that the switch still operates. After the overload behavior has been stopped the switch shall return to normal operation. All ports as defined in class,,3 are involved and used in full-duplex manner. source 00% 00% 00% 00% 00% 00% 00% 00% 00% 00% destination L Packet Size 64 bytes 8 bytes 56 bytes 5 bytes 768 bytes 04 bytes 80 bytes 58 bytes Percentage values in the picture refer to the required load. The overload situation: egress overload 00% 30% 80% 70% 00% 0% Issue.00 4 (4)

15 The required load for all ports is selected and throughout the execution, the packet size is changed from its smallest to its largest value (see the above table). After overload situation recover the normal traffic situation. The Latency is measured for each port. Method of Test: Use a measurement device to generate packets from all source ports. At the destination ports the L latency and the received number of packets will be measured. Test Conditions: Ä Assumptions and Limitations: Ä Electrical conformance tests according to IEEE80.3 specification has been covered before this test case. Ä Conformance tests according to IPv6 (RFC460) and IPv4 (RFC79) has been covered before this test case. Ä DUT is up and running and connected to Test equipment and Test manager Ä Suitable Address table is inserted Ä All DUT ports are configured to fast Ethernet links (00Mbits) Procedure:. Send packets of a fixed size from all sources to all destinations. Test duration is minimum 0sec 3. Measure the number of packets transmitted and received on all streams to ensure that no packets are lost or switched to the wrong port 4. Measure the latency between all source and destination ports Repeat step -4 with all different packet sizes (see table above). Test setup: Test Inventory: - DUT - Tester backplane - Tester Power Supply - Test equipment with FE/GE ports - Test manager See Test Setup F Minimum acceptance criteria: - The transport module should fulfill the latency requirement according to OBSAI RP specification and optional packet loss requirement. Parameters Value Limit Comments The Data Link Max 00µs layer latency Ethernet switching delay between any two interfaces. Packet loss No packet loss General quality measure (optional) 3 Issue.00 5 (4)

16 3.4 Short circuit tolerance Test Case ID: RP/TM_Timing&Sync_7 Test Case Optional status: Relevant to: TM Source [OBSAI TM] reference: Test Purpose: Connect Reference clock (RCLK0, RCLK) differential outputs: together, short to ground, short to voltage and verify that after tests the outputs are functioning within specified limits. Test Models:. Short to ground. Short to supply voltage 3. Short together Method of Test: Manual or automatic execution of shorts Test Conditions: Ä DUT is up and running and connected to Test equipment and Test manager Ä Suitable Address table is inserted Ä All DUT ports are configured to fast Ethernet links (00Mbits) Assumptions and Limitations: Ä Electrical conformance tests according to IEEE80.3 specification has been covered before this test case. Ä DUT is up and running and connected to Test equipment and test manager Ä Suitable Address table is inserted Ä All DUT ports are configured to fast Ethernet links (00Mbits) Procedure:. Connect RCLK0 output to ground. Connect RCLK0 output to supply voltage 3. Connect RCLK0 output lines together 4. Verify that RCLK0 output supplies specified signal, with frequency counter 5. Connect RCLK output to ground 6. Connect RCLK output to supply voltage 7. Connect RCLK output lines together 8. Verify that RCLK output supplies specified signal, with frequency counter Test setup: Test Inventory: - DUT - Frequency counter - Test manager Minimum acceptance criteria:. Reference clock output should supply specified signal after output short circuit test cases 3 Issue.00 6 (4)

17 3.5 Clock Management Functions Test Case ID: Test Case status: Relevant to: Source reference: Test Purpose: Test Models: RP/TM_Timing&Sync_966 Mandatory TM [OBSAI RP], [G80] Verify that TM is able to extract and insert the SSM (synchronization status messages) into the selected network interface. TM verifies the clock according to the SSM information. ITU-T/ETSI ANSI Accuracy SSM Value Description Usability for BTS System clock Unknown 0000 (0) The quality level could not be determined No G.8 Stratum Å Ç0 000 () Sync. path traceable to Yes (Level ) G.8 source G.8 Transit Stratum Å8,6 Ç0 000 (4) Sync. path traceable to Yes (Level ) G.8 source G.8 Local Stratum 3 Å6 4,6 Ç0 000 (8) Sync. Path traceable to No (Level 3) G.8 source SETS Stratum 4 Å5 3, Ç0 0 () Sync Path traceable to No SETS source DNU (5) Do Not Use No Method of Test: Test Conditions: Assumptions and Limitations: The TM shall provide the SSM synchronization information (Synchronization Status Messages) derived from the Network Interface to a test PC. SW in the test PC monitors the synchronization messages. The Test PC shall provide the SSM to the TM, to be inserted in the line interface message. Ä Ä Electrical conformance tests according to IEEE80.3 specification has been covered before this test case. Ä DUT is up and running and connected to Test equipment and Test manager Ä DUT has at least one of the interface types E, T, STM/OC3 Procedure:. Test equipment sends SSM information in the data frames from network analyzer to TM. TM extracts the SSM and verifies the Clock 3. TM reports test result to PC 4. Repeat -3 with other SSM values 5. Set TM to send SSM information with the data frames 6. Network analyzer reads the data and extracts SSM 7. Network analyzer reports the test result to PC 8. Repeat 5-7 with other SSM values Test setup: Test Inventory: - DUT Issue.00 7 (4)

18 - Tester backplane - Tester Power Supply - Network analyzer with Transport interface (E, T, STM/OC3) - Test manager See Test Setup G Minimum acceptance criteria:. TM shall forward the SSM information to the Test system. Issue.00 8 (4)

19 4 Test setups These are the simplified test setups referenced in the test cases. 00% 00% 00% 00% tested traffic 00% 00% 00% 00% 00% 00% background traffic 3 4 Figure Test Setup F 5 6 Issue.00 9 (4)

20 Network Analyzer DUT Power Test Manager 3 Figure 3 Test Setup G 4 Issue.00 0 (4)

21 5 Glossary Abbreviations For the purposes of the present document, the following abbreviations apply: ABBREVIATION DESIGNATION BBM Base Band Module BTS Base Transceiver Station CCM Clock and Control Module GND Ground LVDS Low Voltage Differential Signaling OBSAI Open Base Station Architecture Initiative RFM Radio Frequency Module RP Reference Point RP Reference Point RP3 Reference Point 3 SW Software TM Transport Module 5 Table - Abbreviations Definition of Terms For the purposes of the present document, the following terms and definitions apply: Common Signals: Common Signals are common to all modules and shall be supported. Common Signals are assigned to fixed pin positions at the Data Connector(s) which are present at all modules. Issue.00 (4)

22 Module Type Specific Signals: Module Type Specific Signals are specific to a certain module type (TM, CCM, BBM, RFM, PM) and shall be supported. Module Type specific Signals shall be assigned to fixed pin positions at the Data Connector(s). Module Type Unspecified Signals: Module Type Unspecified Signals are optional. Their functional and electrical characteristics are not specified. If present, Module Type Unspecified Signals shall be assigned to a range of pin positions at the Data Connector(s). The range of pin positions shall be fixed for a certain module type, but may differ between module types. Signal Group: A group of signals forming a functional entity e.g. a fabric port. High Impedance State: Issue.00 (4)

23 6 References OBSAI [OBSAI System] OBSAI System Reference Document V.00 [OBSAI RP] OBSAI Reference Point Specification V.00 [OBSAI RP] OBSAI Reference Point Specification V.00 [OBSAI TM] OBSAI Transport Module Specification V [OBSAI CCM] OBSAI Clock and Control Module Specification V [OBSAI TEST] OBSAI Conformance Test Specification V.00 [OBSAI COMMON] OBSAI Conformance Test Cases Common for all modules V IEEE 3 4 [IEEE 80.3] IEEE Std, 80.3, Local and Metropolitan Area Networks, IETF 6 [RFC79] Internet Protocol, September [RFC4] [RFC65] Benchmarking terminology for network interconnection devices Service Location Protocol (SLP) Request For Comments [RFC460] Internet Protocol, Version 6, December 998 Issue.00 3 (4)

24 [RFC544] Benchmarking methodology for network interconnect devices ITU-T [G80] [G84] [G83] [G85] Definitions and terminology for synchronization networks The control of Jitter and wander of 544kbit/s The control of Jitter and wander of 048kbit/s The control of Jitter and wander of SDH Issue.00 4 (4)