Hi All,

I am facing some issue in checking of optional fields in receiving messag= e
which contains some optional fields.
I am working in LTE and having some Message flow between eNB and MME.
I want to make it generic so it should support optional field also.
As one eNB can send optional field 1 and second can send optional field 2= in a
same message.
At this time MME should receive both messages without mismatch.

eNB1 --message with opt field 1 -- > MME
eNB2 --message with opt field 2 -- > MME

How to put this check in TTCN-3 language ?

As in TTCN3 core language spec keywork ifpresent is given to check for optional
field, but it is compiling correctly but at run time it is not a= ble to match
it correctly.

Please do give me some hints on this.

Hi,
Can you send the actual code you are using?

Thanks,
Claude

Hi Claude,
Thanks for showing interest.

I want to do it for eNB configuration update message sent from eNB to MME= .
Given in 3GPP TS 36.413 V8.6.1 (2009-06) page no - 163, Suppose i want to make
this message generic, so that MME can recieve any number of optional fields.

ENBConfigurationUpdateIEs S1AP-PROTOCOL-IES ::= {
{ ID id-eNBname CRITICALITY ignore TYPE ENBname PRESENCE optional }|
{ ID id-SupportedTAs CRITICALITY reject TYPE SupportedTAs PRESENCE
optional }|
{ ID id-CSG-IdList CRITICALITY reject TYPE CSG-IdList PRESENCE optional= }|
{ ID id-DefaultPagingDRX CRITICALITY ignore TYPE PagingDRX
PRESENCE optional },
...
}

So how to use 'ifpresent' for all optional fields in this message.

Thanks,

Hi Bheemashankar,

I suppose you are emulating MME. You can go two ways:
1) Just define two receiving branches in an alt statement, one is catching = the
message received from one eNB, the other is catching the message from t= he
other eNB. Actually, if they are received on different ports, there is n= o
other alternative. In this case you also can take different actions in ca= se of
the two different events.
2) If you have one port only on the simulated MME side AND you don't care w=
hich eNB have sent the message, you can define your receiving template as a=
template list and put both messages, the one that you are expecting from eNB1 and the one you are expecting from eNB2, as elements of the list. See m= ore
details in clause B.1.2.1 of Part-1, ES 201 873-1.

Regards, Gyorgy