Scribd
Upload
6 views2 pages

Spide Note

The document explains how the UFDL code processes a specific 4-byte chunk of binary data from a network stream, detailing the parsing of each byte and the resulting structured Usage Detail Record (UDR). It outlines the steps for creating a UDR View configuration, including selecting fields and saving the view. The example illustrates how raw data is transformed into a structured format for easier analysis.

Uploaded by

Eshaprasad
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
6 views2 pages

Spide Note

The document explains how the UFDL code processes a specific 4-byte chunk of binary data from a network stream, detailing the parsing of each byte and the resulting structured Usage Detail Record (UDR). It outlines the steps for creating a UDR View configuration, including selecting fields and saving the view. The example illustrates how raw data is transformed into a structured format for easier analysis.

Uploaded by

Eshaprasad
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

This is spiderman

To illustrate how the UFDL code in the image works, let's look at how it would process a specific
4-byte chunk of binary data from a network stream.
1. The Binary Data Example
Imagine the incoming data stream contains the following four bytes (shown in hexadecimal):
84 00 0A C1
2. How the Code Parses This Data
The editor's definition tells the system exactly how to "read" these bytes:
 Byte 1 (84):
o The system checks the first byte. Because RecordIdentifier == 0x84 (Line 2), it
identifies this as a valid AMA_Record.
o It assigns this value to the field RecordIdentifier (Line 5).
 Bytes 2 & 3 (00 0A):
o The code defines RecordLength as a 2-byte integer with lsb_lo (Least Significant
Byte Lowest) ordering (Line 6).
o In hex 00 0A, the decimal value is 10.
o The dynamic_size(RecordLength) instruction (Line 3) now knows this entire
record is 10 bytes long. It will continue reading 6 more bytes after this initial
header.
 Byte 4 (C1):
o The code encounters a bit_block of 1 byte (Line 8).
o Hex C1 in binary is 1100 0001.
o The mapping (Lines 9-16) extracts individual bits as separate fields:
o F18 (Bit 7): 1
o F17 (Bit 6): 1
o F16 (Bit 5): 0
o F15 (Bit 4): 0
o F14 (Bit 3): 0
o F13 (Bit 2): 0
o F12 (Bit 1): 0
o F11 (Bit 0): 1
3. The Resulting UDR
After parsing, the raw hex 84 00 0A C1 is transformed into a structured Usage Detail Record
(UDR) object that looks like this:
1. In the UDR View configuration, click Browse... to open the UDR Internal Format
Browser dialog. Select the UDR type you want to create a view for and click OK.
2. Click the Add button to open another view of the UDR Internal Format Browser dialog.
3. Select the field in the selected UDR you want to add to the view, click Apply, and repeat
for all fields you want to add.
4. Click OK or Cancel to close the dialog.
5. You can now rearrange the order of the fields by selecting them and clicking the Up and
Down buttons.
6. When your view is finished, click Save As to save your UDR View.
In the UDR File Editor, you can now select the saved UDR View to display the configured fields
as columns in the order you have specified.

You might also like