Dear all,

I'm very happy to have received the below attached news via the Eclipse
bugzilla.

This is great, as it permits us to have "real" SI rest octet as well as
RLC/MAC support in our TTCN3 test suites while still using declarative
RAW codec syntax.

Just to be clear there's no misunderstanding: This doesn't mean that
CSN.1 syntax can be parsed by TITAN.  It just means that we can use RAW
codec annotations to describe something that matches the CSN.1 encoding.

Regards,
        Harald
-- 
- Harald Welte <[email protected]>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)
--- Begin Message ---
https://bugs.eclipse.org/bugs/show_bug.cgi?id=548969
Product/Component: Titan / Core


Botond Baranyi <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #1 from Botond Baranyi <[email protected]> ---
Implemented new variant attribute "CSN.1 L/H" for the RAW codec.

>From the reference guide:

Attribute syntax: `CSN.1 L/H`

Default value: unset

Can be used with: all basic types, `records`/`sets`/`unions` (in which case the
attribute is set for all fields of the `record`/`set`/`union`)

Description: If set, the bits in the bitfield are treated as the relative
values `L` and `H` from `CSN.1` instead of their absolute values (`0` is
treated as `L` and `1` is treated as `H`). These values are encoded in terms of
the default padding pattern '2B'O ('00101011'B), depending on their position in
the bitstream.

Practically the bits in the bitfield are XOR-ed with the pattern '2B'O before
being inserted into the stream.

Example:

type integer uint16_t
with { variant "FIELDLENGTH(16)" variant "CSN.1 L/H" }

const uint16_t c_val := 4080;
// Without the variant attribute "CSN.1 L/H" this would be encoded as '11110000
00001111'B
// With the variant attribute "CSN.1 L/H" this would be encoded as '11011011
00100100'B

-- 
You are receiving this mail because:
You are on the CC list for the bug.

--- End Message ---

Reply via email to