Version 1.0
This document describes a well defined header for decoding messages from various radio access technologies in the IDM. By placing this header before a message the IDM will have the information needed to decode the particular message, as well as the ability to display optional information such as the timestamp, source, and destination.
The out of band data should be placed before the OTA message:
| Field | Length (bits) |
|---|---|
| Out of Band data | variable |
| OTA Message | variable |
The OOB data is described in the following sections.
The following fields shall be included first for every message:
| Field | Length (bits) |
|---|---|
| Timestamp included | 1 |
| Source and Destination included | 1 |
| Reserved | 1 |
| Technology | 5 |
| Timestamp | 0 or 64 |
| Source ID | 0 or 16 |
| Destination ID | 0 or 16 |
| RAT Specific Fields | variable |
Timestamp included : If set to 1 the Timestamp field will be included in this message.
Source and Destination included : If set to 1 the Source and Destination fields will be included in this message.
Reserved : Reserved for future use. Set this to 0.
Technology : Radio access technology indicator. Set this to the appropriate RAT based on the table below.
| Value | Radio Access Technology |
|---|---|
| 1 | cdma2000 |
| 2 | UTRA |
| 3 | LTE |
| 4 | IP Header |
Timestamp : Timestamps must be in the form of a 64 bit number that represents time from 12:00:00 midnight, January 1, 0001 A.D. through 11:59:59 P.M., December 31, 9999 A.D. measured in 100-nanoseconds units. This is the time representation used by .Net. The IDM SDK, included in the IDM distribution, provides a freely available C++ header file, DateTime.h, that can aid in the generation of these timestamps. A timestamp of 0 is the same as not providing a timestamp.
Source ID : A numeric value indicating the source of this message.
Destination ID : A numeric value indicating the destination of this message.
RAT Specific Fields : The following sections describe the various RAT Specific fields.
For a Technology of type 1 the following fields shall be included:
| Field | Length (bits) |
|---|---|
| Sublayer | 8 |
| Sublayer specific fields | variable |
Sublayer : The sublayer indicator. This shall be set to the sublayer type of this message as specified in the following table:
| Value | Sublayer |
|---|---|
| 1 | 1xRTT (C.S0001 to C.S0006/IS-2000.1 to IS-2000.6) |
| 2 | EVDO Signaling (C.S0024-A/IS-856A) |
| 3 | EVDO Packet Data |
Sublayer specific fields : Sublayer specific fields as specified in the above table and defined in the following sections.
For a Sublayer of type 1 the following fields shall be included:
| Field | Length (bits) |
|---|---|
| Channel | 8 |
| 1xRTT PDU | variable |
Channel : The channel indicator. This shall be set to the channel type of this message as specified in the following table:
| Value | Channel |
|---|---|
| 0 | f-sync |
| 1 | f-csch forward common signaling logical channel (F-SYNC, F-PCH) |
| 2 | f-dsch forward dedicated signaling logical channel (F-TCH) |
| 3 | r-csch reverse common signaling logical channel (R-ACCH) |
| 4 | r-dsch reverse dedicated signaling logical channel (R-TCH) |
1xRTT PDU : The 1xRTT message as defined in 3GPP2 C.S0004-E.
For a Sublayer of type 2 the following fields shall be included:
| Field | Length (bits) |
|---|---|
| Reserved | 6 |
| Direction | 1 |
| In Use/In Config flag | 1 |
| Protocol Type | 8 |
| Length | 32 |
| EVDO PDU | variable |
Reserved : Reserved for future use. Set this to 0.
Direction : The Direction indicator. Set this to the appropriate direction as specified in the table below:
| Value | Direction |
|---|---|
| 0 | Forward |
| 1 | Reverse |
In Use/In Config : The In Use/In Config flag. Set this to the appropriate value as specifed in the table below:
| Value | In Use/In Config |
|---|---|
| 0 | In Use |
| 1 | In Configuration |
Protocol Type : Protocol Type as specified in 3GPP2 C.S0024-B Table 2.5.4-1.
Length : Length in bytes of the PDU.
EVDO PDU : The EVDO message as defined in 3GPP2 C.S0024-B.
For a Technology of type 2 the following fields shall be included:
| Field | Length (bits) |
|---|---|
| Sublayer | 8 |
| Sublayer specific fields | 0 or variable |
Sublayer : The sublayer indicator. This shall be set to the sublayer type of this message as specified in the following table:
| Value | Sublayer |
|---|---|
| 0 | Radio Resource Control (RRC) |
| 1 | System Information Block (SIB) |
| 2 | Non-Access Stratum (NAS) |
| 3 | Radio Resource (RR) Layer 2 |
| 4 | Radio Resource (RR) Short |
Sublayer specific fields : Sublayer specific fields as specified in the above table and defined in the following sections.
For a sublayer of type 0 the following fields shall be included:
| Field | Length (bits) |
|---|---|
| Channel | 8 |
| RRC PDU | variable |
Channel : The channel indicator. This shall be set to the channel type of this message as specified in the following table:
| Value | Channel |
|---|---|
| 0 | Downlink Dedicated Control Channel (DL-DCCH) |
| 1 | Uplink Dedicated Control Channel (UL-DCCH) |
| 2 | Downlink Common Control Channel (DL-CCCH) |
| 3 | Uplink Common Control Channel (CUL-CCH) |
| 4 | Paging Control Channel (PCCH) |
| 5 | Downlink Shared Control Channel (DL-SHCCH) |
| 6 | Uplink Shared Control Channel (UL-SHCCH) |
| 7 | Broadcast Control Channel (BCCH) Forward Access Channel (FACH) |
| 8 | Broadcast Control Channel (BCCH) Broadcast Channel (BCH) |
| 11 | Handover To UTRAN Command |
RRC PDU : The RRC PDU as defined in 3GPP TS 25.331 Release 9
For a sublayer of type 1 the following fields shall be included:
| Field | Length (bits) |
|---|---|
| SIB Type | 8 |
| SIB | variable |
SIB Type : The SIB type. This shall be set to the SIB type of this message as specified in the following table:
| Value | SIB |
|---|---|
| 0 | masterInformationBlock |
| 1 | systemInformationBlockType1 |
| 2 | systemInformationBlockType2 |
| 3 | systemInformationBlockType3 |
| 4 | systemInformationBlockType4 |
| 5 | systemInformationBlockType5 |
| 6 | systemInformationBlockType6 |
| 7 | systemInformationBlockType7 |
| 8 | systemInformationBlockType8 |
| 9 | systemInformationBlockType9 |
| 10 | systemInformationBlockType10 |
| 11 | systemInformationBlockType11 |
| 12 | systemInformationBlockType12 |
| 13 | systemInformationBlockType13 |
| 14 | systemInformationBlockType13_1 |
| 15 | systemInformationBlockType13_2 |
| 16 | systemInformationBlockType13_3 |
| 17 | systemInformationBlockType13_4 |
| 18 | systemInformationBlockType14 |
| 19 | systemInformationBlockType15 |
| 20 | systemInformationBlockType15_1 |
| 21 | systemInformationBlockType15_2 |
| 22 | systemInformationBlockType15_3 |
| 23 | systemInformationBlockType16 |
| 24 | systemInformationBlockType17 |
| 25 | systemInformationBlockType15_4 |
| 26 | systemInformationBlockType18 |
| 27 | schedulingBlock1 |
| 28 | schedulingBlock2 |
| 29 | systemInformationBlockType15_5 |
| 30 | systemInformationBlockType5bis |
| 31 | extensionType |
SIB : The SIB PDU as defined in 3GPP TS 25.331 Release 9.
For a sublayer of type 2 the following fields shall be included:
| Field | Length (bits) |
|---|---|
| Reserved | 7 |
| Direction | 1 |
| NAS PDU | variable |
Reserved : Reserved for future use. Set this to 0.
Direction : The Direction indicator. Set this to the appropriate direction as specified in the table below:
| Value | Direction |
|---|---|
| 0 | Downlink, network to mobile station |
| 1 | Uplink, mobile station to network |
NAS PDU : The NAS PDU as defined in 3GPP TS 24.008 Release 9.
For a sublayer of type 3 the following fields shall be included:
| Field | Length (bits) |
|---|---|
| Reserved | 7 |
| Direction | 1 |
| RR Layer 2 PDU | variable |
Reserved : Reserved for future use. Set this to 0.
Direction : The Direction indicator. Set this to the appropriate direction as specified in the table in section 3.3.
RR Layer 2 PDU : The RR Layer 2 PDU as defined in 3GPP TS 44.018.
For a sublayer of type 4 the following fields shall be included:
| Field | Length (bits) |
|---|---|
| Reserved | 7 |
| Direction | 1 |
| RR Short PDU | variable |
Reserved : Reserved for future use. Set this to 0.
Direction : The Direction indicator. Set this to the appropriate direction as specified in the table in section 3.3.
RR Short PDU : The RR Short PDU as defined in 3GPP TS 44.018.
For a Technology of type 3 the following fields shall be included:
| Field | Length (bits) |
|---|---|
| Sublayer | 8 |
| Channel | 8 |
| Sublayer specific fields | variable |
Sublayer : The sublayer indicator. This shall be set to the sublayer type of this message as specified in the following table:
| Value | Sublayer |
|---|---|
| 0 | Radio Resource Control (RRC) |
| 1 | Non-Access Stratum (NAS) |
Channel : The channel indicator. This shall be set to the channel type of this message as specified in the following table:
| Value | Channel |
|---|---|
| 1 | UL-CCCH |
| 2 | UL-DCCH |
| 3 | DL-CCCH |
| 4 | DL-DCCH |
| 5 | PCCH |
| 6 | BCCH-DL-SCH |
| 7 | BCCH-BCH |
Sublayer specific fields : Sublayer specific fields as specified in the above table and defined in the following sections.
For a Sublayer of type 0 the following fields shall be included:
| Field | Length (bits) |
|---|---|
| LTE RRC PDU | variable |
LTE RRC PDU : The LTE RRC PDU as defined in 3GPP2 TS 36.331 Release 8.
For a Sublayer of type 1 the following fields shall be included:
| Field | Length (bits) |
|---|---|
| LTE NAS PDU | variable |
LTE NAS PDU : The LTE NAS PDU as defined in 3GPP2 TS 24.301 Release 8.
For a Technology of type 4 the following fields shall be included:
| Field | Length (bits) |
|---|---|
| Reserved | 8 |
| IP Header | variable |
Reserved : Reserved for future use. Set this to 0.
IP Header : The IP Header as defined in tbd.
