Pages

Join our LinkedIn group

Showing posts with label TTCN. Show all posts
Showing posts with label TTCN. Show all posts

Thursday, 2 December 2010

The 3GPP release 8 IMS Implementation, Deployment & Testing workshop

The 3GPP release 8 IMS Implementation, Deployment & Testing workshop took place in Sophia Antipolis on 24-25 November 2010.

The event was attended by 70 delegates actively participating to the discussions.
Presenting companies included: Tel : A1 Telekom Austria, Alcatel Lucent, Codenomicon, Conformiq, Eircom, Elvior, ETSI, France Telecom, GSMA, Huawei, Huawei, Mobitel, NTT DoCoMo, SFR, Telecom Italia, TestingTech, TU Berlin, Wind, Wipro, ZTE.

Here are the highlights from the ETSI document:

Goals and Outcome for this workshop

Share exprience from IMS implementation
Highlight areas for further specifications, for
Standards and Testing
Learn of issues and possible resolutions

Comments from The IMS Network Testing Group

Develop IMS core network test specifications based upon 3GPP, for:
• Interoperability
• conformance
• network integration
Hold interoperability events (IMS Plugtests)
Coordinate with other organisations such as OMA, MSF, GSMA

Implementations

• Beyond small islands, second wave to replace unscalable, unmaintenable early VoIP systems
• Implementation options - Hybrid CS-GW for transition from CS to LTE, which already has 2 million subscribers on IMS/CS-GW/RNC
• Auto provisioning - to simplify complexity
• IMS functions must be implemented in the core – not in any access network, such as LTE, and can be used for non-Voice as well


Implementing RCS (Rich Communication Suite)

• RCS trial feedback - Good feedback from 400 trial users on RCS but difficult to configure SBC
• RCS implementations should include aggregation with SNS (Social Network Services)– eg contact list from Facebook
• Most appreciated feature of RCS is: - cross-operator interworking and compatibility with ordinary phones, not just smartphones


Specific Issues and Resolutions

• FAX – Delay and Jitter issues - FTTH will solve long delays etc
• Emergency and Lawful Intercept with IMS -There are standards and developed solutions available but Currently still falls back to CS /TDM
• Data Provisioning speed is important, to achieve no service interruption.
• 3GPP II-NNI: Inter-IMS Network to Network Interface - Two levels: Solx (service with control function) and Coix (connection – a pipe for media).
• “PathFinder” Global ENUM – like DNS for phone number; It is a solution to number portability and can optimise routing


About Services

• Most issues are Beyond IMS - integrating OSS/BSS, existing systems, inter-vendors interfaces
• IMS and IN - Pity the Standards did not bring IN and IMS close together; Need iFC enhancements, like in IN; Need to support combining services
• OTT and SNS dominate growth - occupies the minds of commercial people, GSMA-like services have slowed down
• Service layer (Wipro) – Telcos want one SDP to serve all - include IMS and non-IMS services, human and non-humans on NAB, context based, and charge only what is ‘consumed’


Testing Methods, Tools and Test Beds

• Integrate Conformance checking with interoperability testing
• Automation of interoperability trace checking – it can reduce costs by more than 50 % compared to manual validation
• Independent Test Bed- available EPC playground for prototyping applications
• Protocol message customisation tool - allows changing the message and customise the flow
• Security testing tool - testing by ‘fuzzing’, 100% TTCN free – everything is already build in
• IMS is a multi vendor environment - Testing and validation must be an integral part of the deployment process


Memorable Quotes

“IMS is a Journey, not a destination” (ALU)
“SDP is almost anything” (Matjas Bericic, Mobitel)
“Voice as an app versus Voice as a Service” is a challenge (Manuel Vexler, Huawei)
“IMS is not a box, it is a network” (Matjas Bericic, Mobitel)
“global ENUM is DNS for phone numbers” (Adrian Dodd, GSMA)
“Kill with one SIP” (Ari Takanen, Codenomicon)
“ IOP is the red thread running through the entire ETSI standards development process “ (Milan Zoric, ETSI)

All documents from this workshop is available at: http://docbox.etsi.org/Workshop/2010/201011_IMSWORKSHOP/

Friday, 15 May 2009

Testing UMTS protocols




Testing UMTS by Dan Fox, Anritsu

Its nearly three years since I wrote an FAQ on UMTS Testing. So when I got my hands on this book the other day, I so wanted to read it. It would be a while before I manage to go through the book in detail but my initial impression is that this book looks quite good.

Since the book deals with Protocol Testing, the testing has been grouped into three categories:

  1. Integration Testing
  2. Conformance Testing
  3. Interoperability Testing

There is a chapter explaining each of these. The Conformance testing is of interest to me as I have been involved directly and indirectly with this for quite some years now. The book explains the process, standards required and submission of tests to GCF/PTCRB.

For those whom testing does not hold much charm, they can gain greater understanding of the concepts by reading Part II of the book. One thing I really liked in this book is that the diagrams explain the concepts very well. Rather than copying them straight from the 3GPP specifications, they have been improved and re-done by the author. Basic things like 'Dynamic TFCI selection' and 'Layer 2 transport channel processing flow for the 12.2 kbps RMC' are explained clearly using the diagrams.

There is just the right amount of detail in the chapters for Physical Layer, Layer 2 (MAC, RLC, PDCP) and Layer 3 (RRC, NAS). Further chapters show message flow sequence charts explaining things like 'setting up of speech call' and 'location updating procedure'. I have some basic sequence diagrams for message flow in the Tutorial section but the ones in the book are comparatively more detailed.

The book mainly covers UMTS, with an introduction to HSPA. It would be worthwhile to have the next edition covering LTE in detail. The main reason being that there are lots of changes in the case of LTE. The Air Interface has changed, the channels are different. The NAS messages and entities are different. UMTS (and HSPA) use TTCN-2 for testing but LTE uses TTCN-3. UMTS does not use MIMO (MIMO available for HSPA from Release 7 onwards) but LTE would generally always use MIMO.

Overall, this seems to be a useful book and I am looking forward to reading it in detail.

Monday, 25 February 2008

Introduction to TTCN-3



This one is from Arvind's blog:


TTCN-3 core language is nothing more than simple text with well-defined syntax and semantics. The syntax is defined using Backus-Naur Form. What this means is that any text editor can be used to write TTCN-3 test cases. Such test cases are quite different in dynamic behaviour from C or Pascal. Still, it is quite easy for programmers well-versed with procedural languages to get used to TTCN-3 easily. There are many similarities - keywords, data types, variables, control statements, functions, operators, operator precedence, just to name a few.


The language is structured in a way that allows high level of flexibility. Test system definition is modular. In fact, an important unit of a test suite is a module which would contain one or more test cases or the control part of a test suite. Concurrency of operation is possible because components can execute in parallel. Of course, execution is serialized at the level of hardware unless the multi-processors are involved. Parameterization is possible just as it was possible in TTCN-2. Concepts of PICS and PIXIT still apply because they are fundamental to any conformance testing.

More Information is available at:

Finally, you may be wondering why I am discussing TTCN-3 on this blog. This is because those of us who work in testing side will know very well that most of the test scripts are written in TTCN. At present TTCN-2 is used and there is only one big player for that which is Telelogic. This is because they have some patents which restricts competetion. To bypass this, ETSI pioneered TTCN-3 which is open source and anybody can create a compiler for TTCN-3.

As a result, TTCN-3 is being widely adopted for testing now. Its already being used for WiMAX, IMS and SIP testing. In future it would be used for LTE as well.