TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä The Mythical IUT How to support automatic...

24
TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä The Mythical IUT How to support automatic testing in standardization OBSAI conformance testing as an example TTCN-3 User Conference 6-8th June 2005 Sophia Antipolis, France

Transcript of TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä The Mythical IUT How to support automatic...

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

The Mythical IUT

How to support automatic testing in standardization

OBSAI conformance testing as an example

TTCN-3 User Conference

6-8th June 2005

Sophia Antipolis, France

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Contents

> Testability in general

> Automated testing

> Design for testability

> Standardization for testability

> OBSAI

> Testability in OBSAI

> Achievements

> Future work

> Lesson learned

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

The Mythical IUT

Just test it!

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Testability in General

> Control: The better we can control it, the more the testing can be automated and optimized.

> Visibility: What we see is the what we can test.

> Operability: The better it works, the more efficiently it can be tested.

> Simplicity: The less there is to test, the easier we can test it.

> Understandability: The more information we have, the smarter we test.

> Suitability: The more we know about the intended use of the IUT, the better we can organize our testing to find important bugs.

> Stability: The fewer the changes, the fewer the disruptions to testing.

[Bach, James (1999). “Heuristics of Software Testability]

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Automated Testing

> Automated test generation

> Automated test adaptation

> Automated test execution

> Automated verification of the results

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

OBSAI Open Base Station Architacture Initiativewww.obsai.org

> OBSAI is an organization formed among leading base station vendors, module and component manufacturers to create a set of open specifications for base station architecture.

> Promotor Companies: Hyundai Syscomm, LG Electronics, Nokia, Samsung, ZTE

> 118 members

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Goals of OBSAI

> Define and agree on Base Station Architecture on a modular level

> Develop and provide interface specifications between the main functional modules

> An OBSAI base station consists of

– Cabin with standardized backplane

– A set of modules

“Make it like a PC”

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Simplified OBSAI Architecture

CONTROL & CLOCK MODULE

RP1

RP2 RP3

ControlTrafficClock

NetworkInterface

AirInterface

TRANSPORTMODULE

BASEBANDMODULE

RFMODULE

© OBSAI TWG

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Transport Module

> External Network Interface Functions

> Internal Networking Functions (IP & CML Router)

> QoS Functions

> Network Interface Protocol Termination

> Synchronization Functions

> OAM&P Functions

> Security Functions

CONTROL & CLOCK MODULE

RP1

RP2 RP3

ControlTrafficClock

NetworkInterface

AirInterface

TRANSPORTMODULE

BASEBANDMODULE

RFMODULE

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Baseband ModuleWCDMA>Channel encoding/decoding>Interleaving>Rate matching>Multiplexing/demultiplexing>Spreading>Power weighting & summing of physical channels>RAKE reception>MUD alternative>Interference cancellation>Interference Rejection Cancellation>Frame protocol processing>Higher layer processing (L2 & L3)>CRC

CONTROL & CLOCK MODULE

RP1

RP2 RP3

ControlTrafficClock

NetworkInterface

AirInterface

TRANSPORTMODULE

BASEBANDMODULE

RFMODULE

GSM>Channel encoding/decoding>Interleaving/de-interleaving>Bit detection>Frequency hopping>Ciphering/deciphering>DL diversity transmission (MIMO, etc.)>UL diversity reception, IRC reception, SA reception>Protocol frame processing

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

RF Module

> Modulation> D/A & A/D conversion> Up/down conversion> Carrier selection> Linear power amplification> Antenna interface> Transmit / receive RF filtering> RF combining> Transmit / receive RF filtering> Diversity transmit> Diversity receive (duplexing, etc.)> Low noise amplification> Peak power reduction> OAM&P Functions CONTROL & CLOCK

MODULE

RP1

RP2 RP3

ControlTrafficClock

NetworkInterface

AirInterface

TRANSPORTMODULE

BASEBANDMODULE

RFMODULE

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Control & Clock Module

> Congestion Control

> Admission Control

> BTS Level OAM&P Functions

> BTS Configuration Management and Control

> Radio Resource Management

> Multi-vendor Configurations

> RF Scheduling

> Iub/Abis Signalling Termination

> System Clock Generation and Distribution

CONTROL & CLOCK MODULE

RP1

RP2 RP3

ControlTrafficClock

NetworkInterface

AirInterface

TRANSPORTMODULE

BASEBANDMODULE

RFMODULE

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Logical Interfaces

RP1

Management-plane

Control-plane

IPv6 (IPv4 opt)

802.3 MAC

802.3 100Base-TX

RP2

User-plane

Pv6 (IPv4 opt)

802.3 MAC

802.3 100 Base-TX (1000 Base-TX opt)

RP3

App: type mapping

Transport: Routing

Data Link: Framing

2 level framing

9 to 9 addressing

CML 1.6 Gb/s

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Testability in OBSAI comes from:

> Clearly defined IUT

> Clearly defined interfaces

> Clearly defined test setups

> Control

– Test mode

– Test categories

– Test functions

– Test control messages

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

The IUT

>The IUT is always an OBSAI module.

>A reference design shall be offered to get compliance for a chipset.

>Every module have to support RP1 interface

>RP1 was selected as standard test control port.

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Generic Test Setup

IUT: OBSAI module

Module agentR

P1/

eth

ern

et

RP

n

OBSAI tester

testadapter

HW

RP

n

RP

1/et

her

net

proprietary test control messages

OAM&Pmessages

OBSAItest

control messagesTM

TE

SA

Test functionality

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Test Mode and Test Categories

normal operational mode

test mode

category 1

category 2

category 3

s

<setTestModeReq> “on”

module startup andmodule ready indication

<setTestModeReq> “off”

<setTestModeReq> “on”

normal operational mode

test mode

category 1

category 2

category 3

s

<setTestModeReq> “on”

module startup andmodule ready indication

<setTestModeReq> “off”

<setTestModeReq> “on”

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Test Categories

Functions Normal op

Cat1 Cat2 Cat3 …

Normal functions

Function 1 M M M M M

Function 2 M O O O O

Function 3 M O M O O

… M O O

Function n M O O O M

Test functions

Test func.1 M M

Test func 2 M

Test func 3 M

Test func m M M

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Test Functions

>Implemented by the Module Agent

>Activation of a loopback

>Activation of a test signal

>Activation of a measurement

>Activation of a procedure

Implemented by the Module Agent

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Test Control Messages

>SOAP Messages

>Valid only in test mode

>Activation of test functions

>Triggering of standard procedures

>Retrieval of measurements

>State & event indications

From the Test Manager

to the Module Agent

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Achievements so far

> The 1st release of OBSAI specifications includes

– Compliance process specification

– Test messages specification

– Generic conformance test specification

– Several focused test specifications

> Modules of different vendors can be tested with generic testers?

Plug and test approach

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Future work for release 2

> More formal approach is needed

– Formalization of interface specifications

– Formalization of configuration management

– Formalization of test specifications

– Provide TTCN-3 test suites

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä

Lesson Learned

> Whatever you specify, make it testable by:

– specifying visibility• interfaces• points for observation

– specifying controllability• test setups• test clients, test agents• test control interfaces• test functions• test sequences

TTCN-3 User Conference, 6-8 June 2005 Hannu Rytilä