Intelligence Support Systems Protocol Discovery for AAL2 Packets

Reference: Version: Status:

Last Modified:

e4260-90270-018 0.110.10 Draft

11 April, 201422 March, 20126 August, 2008

Agilent Technologies UK Limited Signal Networks Division South Queensferry West Lothian Scotland EH30 9TG Copyright 2007 Agilent Technologies UK Limited

Agilent Confidential WORKING COPY IF PRINTED

Protocol Discovery for AAL2 PacketsProtocol Discovery for AAL2 Packets

Formatted: English (U.K.)

Table of Contents 1 2 Version History....................................................................................................................... 3 Introduction ............................................................................................................................ 4 2.1 2.2 2.3 2.4 3 Background ....................................................................................................................... 4 References ......................................................................................................................... 4 Scope ................................................................................................................................. 4 Glossary & Acronyms....................................................................................................... 4

Design Overview ..................................................................................................................... 5 3.1 SSSAR Engine Module..................................................................................................... 7 3.1.1 Description................................................................................................................. 7 3.2 AAL2 Discovery & Filter Module .................................................................................... 8 3.2.1 ATM AAL2 Packet Structure: ................................................................................... 8 3.2.2 Discovery Algorithm ................................................................................................. 8 3.2.3 Decision on IuUP Frames ........................................................................................ 10 3.2.4 Table Data................................................................................................................ 11 3.2.5 State Diagram .......................................................................................................... 12

Assumptions and Constraints ............................................................................................. 13 4.1 Assumptions .................................................................................................................... 13 4.1.1 IuUP Frame Protocol ............................................................................................... 13 4.1.2 Iub RACH / FACH Frame Protocol ........................................................................ 13 4.1.3 VC.CID combination ............................................................................................... 13 4.1.4 Threshold for IuUP Frame receipt confidence check .............................................. 13 4.1.5 Timeouts Receiving complete SSSAR PDU ........................................................... 13 4.2 Outstanding Issues .......................................................................................................... 13 4.2.1 Storage of messages for a length of time ................................................................. 13 4.2.2 Destruction of idle streams ................................................................................... 14 4.2.3 Media Manager Plugins ........................................................................................... 14 4.2.4 Other AAL2 Formats ............................................................................................... 14

Formatted Formatted Formatted

Page 2 of 14

Ref: e4260-90270-018e4260-90270-018 Version: 0.110.110.10Status: DraftDraft Agilent Confidential

Protocol Discovery for AAL2 PacketsProtocol Discovery for AAL2 Packets

Formatted: English (U.K.)

1 Version History
Version 0.01 0.02 0.03 0.04 0.05 Summary of Change Initial draft More text Section added for ongoing discussions/issues More detail added regarding SSSAR reassembly Renumbering of sections required and some details added re. additional information to be stored in modules. More unknowns added regarding SSSAR (reassembly into SSSAR-PDUs) Changes made after document review. More changes made after document review. Logic updates needed to flow diagrams/state diagrams Add discovery of Iub Notes on DCCH discovery Written By Patricia Mitchell Patricia Mitchell Patricia Mitchell Patricia Mitchell Patricia Mitchell Approver N/A N/A N/A N/A N/A Date 21/02/07 28/02/07 1/3/07 7/3/07 7/3/07

0.06

Patricia Mitchell

N/A

15/3/07

0.07 0.08 0.09 0.10 0.11

Patricia Mitchell Patricia Mitchell Patricia Mitchell Garry Marshall Garry Marshall

N/A N/A N/A N/A N/A

16/3/07 19/3/07 10/4/07 3/5/07 6/8/08

Formatted Formatted Formatted

Page 3 of 14

Ref: e4260-90270-018e4260-90270-018 Version: 0.110.110.10Status: DraftDraft Agilent Confidential

Protocol Discovery for AAL2 PacketsProtocol Discovery for AAL2 Packets

Formatted: English (U.K.)

2 Introduction
2.1 Background
This document is a technical note which discusses the ERG software requirements (loose term) to support discovery of voice and video signals, specifically the ATM Adaptation Layer 2 (AAL2) type. It expands on the section entitled Asap discovery and filtering of reference [1]. AAL2 is designed to deal with asynchronous, non-time critical, variable length frames.

2.2 References
[1] Iu Signaling Processing Overview document e4260-90270-007 [2] 3GPP TS 25.415 UTRAN Iu interface user plane protocols (Release 1999) [3] Iub and Iur Cell Identity Event Record Generator, e4260-90271-003 v0.06

2.3 Scope
This document should serve as a reference for technical leads and software engineers. It is an overall description of how ATM AAL2 streams will be handled. It is considered to be a working document, as more AAL2 stream types are implemented in the hardware.

2.4 Glossary & Acronyms

Term AAL AAL2 ASAP ATM CID CPS CRC Iub Iu UP PDU RAB SDU SSSAR UMTS VCI VPI Explanation ATM Adaptation Layer ATM Adaptation Layer Type 2 ATM / STM Acquisition Processor Asynchronous Transfer Mode Channel Identifier Common Part Sublayer Cyclic Redundancy Check Interface between an RNC and a Node B. Iu User Plane Protocol Data Unit Radio Access Bearer Service Data Unit Service-Specific Segmentation and Reassembly Universal Mobile Telecommunications System Virtual Channel Identifier Virtual Path Identifier

Formatted Formatted Formatted

Page 4 of 14

Ref: e4260-90270-018e4260-90270-018 Version: 0.110.110.10Status: DraftDraft Agilent Confidential

Protocol Discovery for AAL2 PacketsProtocol Discovery for AAL2 Packets

Formatted: English (U.K.)

3 Design Overview
Event Bus IssAAL2_CPSPacket

IssAAL2_CPSPacket

SSSAR Engine

IssAAL2_SSSAR_SDU

IssSSSAR_Unknown IssSSSAR_IuUPSupport AAL2 Discovery & Filter Asap Configuration

Figure 3-1 AAL2 Discovery Event Flow

1. Newly discovered AAL2 CPS Packet is published on the event bus. 2. The SSSAR Engine picks up the new AAL2 CPS Packet . If the CPS Packet contains a complete message (See Section 3.1.1) it will be reconfigured as an SSSAR PDU. If it is not a complete message it will be reassembled before reconfiguring it as an SSSAR PDU. 3. The SSSAR Engine will then publish the new SSSAR PDU to the event bus. 4. The AAL2 Discovery & Filter module will pick up the SSSAR PDU, and determine whether the SSSAR PDU contains a valid AAL2 message. Presently we are only concerned with: IuUP Frames, which have a checksum section in their headers (See diagram 3.3). If the checksum check works (on a predefined number of frames on the stream) , we assume the PDU is an IuUP frame, and that the related stream can be classified as passing IuUP data too. Iub Frames, which have a 7 bit header checksum, in addition to a flag indicating whether the packet is a data / control frame and a 5 bit Transport Format Indicator field which we can use classify Iub frames. 5. The AAL2 Discovery & Filter module will tell the configuration module to disable the stream if the data it is carrying is considered invalid (i.e. Unknown), and enable it if it is Page 5 of 14 Ref: e4260-90270-018e4260-90270-018 Version: 0.110.110.10Status: DraftDraft Agilent Confidential

Formatted Formatted Formatted

Protocol Discovery for AAL2 PacketsProtocol Discovery for AAL2 Packets carrying valid data (currently only IuUP data and Iub signalling, but the list of valid data types will be configurable) 6. The AAL2 Discovery & Filter module will then republish the valid SSSAR PDUs onto the event bus (event id ASAP_AAL2_CPS_PACKET), but the event names will be modified to one of IssSSSAR_IuUPSupported IssSSSAR_IubSupported or IssSSSAR_Unknown. Event Name
IssAAL2_CPSPacket

Formatted: English (U.K.)

Publishing Module
IssAsapDiscovery

Subscribing Module(s)
IssSSSAREngine

Description
Indicates that a new CPS Packet has been found. Reserved for future use Indicates that the CPS Packets have been reassembled into SSSAR PDUs (even if only one CPS Packet) Indicates that the SSSAR PDU for this event contains Iu UP data Indicates that the SSSAR PDU for this event contains an Iub message. Indicates that the SSSAR PDU for this event contains data of an unknown format

IssAAL2_CPSPacketContainer IssAAL2_SSSAR_PDU

IssAsapDiscovery IssSSSAREngine

TBD IssAAL2Discovery AndFilter

IssSSSAR_IuUPSupported

IssAAL2Discovery AndFilter

TBD

IssSSSAR_IubSupported

IssAAL2Discovery AndFilter

TBD

IssSSSAR_Unknown

IssAAL2Discovery AndFilter

TBD

Table 3-1 Events relating to AAL2 Streams

Formatted Formatted Formatted

Page 6 of 14

Ref: e4260-90270-018e4260-90270-018 Version: 0.110.110.10Status: DraftDraft Agilent Confidential

Protocol Discovery for AAL2 PacketsProtocol Discovery for AAL2 Packets

Formatted: English (U.K.)

3.1 SSSAR Engine Module 3.1.1 Description

If the AAL2 CPS Packet received indicates that it is not the complete message (i.e. UUI = 27) then the CPS Packets must be reassembled into complete SSSAR PDUs before being passed on. See Figure 3-2 for details of how this is done.
169 Bytes

SSSAR-PDU

45

CPS Packet

45

CPS Packet UUI = 27 LI = 45

45

CPS Packet

34

UUI = 26 LI = 34

CPS Packet

Figure 3-2 SSSAR Reassembly

If the AAL2 CPS Packet received is a complete message (i.e. UUI = 26) then the CPS Packet is reconfigured into an SSSAR-PDU (CPS Header is removed from all Packets) before being passed on.

Formatted Formatted Formatted

Page 7 of 14

Ref: e4260-90270-018e4260-90270-018 Version: 0.110.110.10Status: DraftDraft Agilent Confidential

Protocol Discovery for AAL2 PacketsProtocol Discovery for AAL2 Packets

Formatted: English (U.K.)

3.2 AAL2 Discovery & Filter Module 3.2.1 ATM AAL2 Packet Structure:
Presently we are only interested in Iu UP Frames, which we have reassembled/reconfigured into SSSAR PDUs. This PDU will contain the complete message, and if it is an Iu UP Frame then it will contain the structure outlined in Figure 3-3
SSSAR PDU containing Iu UP

Iu UP Header (4 octets)

Iu UP Payload

Iu UP Header

PDU Type ( 4 bits)

Frame Number (4 bits)

FQC (2 bits)

RFCI (6 bits)

Header CRC (6 bits)

Payload CRC (10 bits)

Figure 3-3 Structure of SSSAR PDU containing an IuUP Frame

3.2.2 Discovery Algorithm

Text in italics indicates information from reference [1] An AAL2 stream will consist of CPS Packets. The ERG software will need to parse the containers and extract the CPS packets directly. The original SSSAR SDU may need to be reconstructed, should it have been split across more than one CPS packet. Presently we are only concerned with IuUP and Iub Frames on the AAL2 stream, and these are converted into SSSAR PDUs within the SSSAR Engine module, even if the PDU only consists of one CPS Packet. To determine if the PDU we have received is an IuUP Frame, we will calculate the packet header checksum (HEC) using the formula determined in [2] Section 6.6.3.8, and compare it to the value held in the 6-bit section of the IuUP Frame Header (6 most significant bits of octet 3 of the header). If the checksums are as expected (across a consecutive number of messages received on a stream) then we can assume that the PDU does indeed contain an IuUP Frame, otherwise the protocol indication will be set to unknown. Similarly, to determine if the PDU we have received is an Iub Frame we can apply the following heuristics from [3]: For a RACH channel: o The Iub frame length should be one of 23, 28 or 36 octets o frame[0] == xxxxxxx0 (frame is a data frame, not a control frame) Page 8 of 14 Ref: e4260-90270-018e4260-90270-018 Version: 0.110.110.10Status: DraftDraft Agilent Confidential

Formatted Formatted Formatted

Protocol Discovery for AAL2 PacketsProtocol Discovery for AAL2 Packets o frame[2] == xxx00000 (TFI is 0) o VC direction is UPLINK o 7 bit FP header checksum matches calculated header checksum For a FACH channel: o The Iub frame length should be one of 27, or 33, 48 or 69 3 octets o frame[0] == xxxxxxx0 (frame is a data frame, not a control frame) o For the 27 and 33 octet case frame[2] == xxx00001 (TFI is 1), For the 48 octet case frame[2] == xxx00002 (TFI is 2), For the 69 octet case frame[2] == xxx00003 (TFI is 3).1 o VC direction is DOWNLINK o 7 bit FP header checksum matches calculated header checksum For a DCCH on DCH channel: o The Iub frame length should be one of 22, 24 or 26 octets o Frame[0] == xxxxxxx0 (frame is a data frame, not a control frame) o Frame[2] == xxx00001 (TFI is 1) o VC direction is DOWNLINK for the 22 octet case, UPLINK or DOWNLINK for the 24 octet case (the two 24 octet forms can be distinguished by checking the payload CRC for the downlink case), the 26 octet case is UPLINK. o 7 bit FP header checksum matches calculated header checksum. Currently, we are not interested in non RACH / FACH / DCCH Iub frames.

Formatted: English (U.K.)

Formatted

Formatted
1

FACH channels can also be defined as having 2x168 bit transport blocks (TFI == 2), but the first version of the software is unlikely to support this configuration.

Formatted Formatted

Page 9 of 14

Ref: e4260-90270-018e4260-90270-018 Version: 0.110.110.10Status: DraftDraft Agilent Confidential

Protocol Discovery for AAL2 PacketsProtocol Discovery for AAL2 Packets

Formatted: English (U.K.)

3.2.3 Decision on IuUP Frames

New SSSAR PDU received Obviously this is more complicated because we will possibly be receiving PDUs on all 248 channels within all streams. Yes Is IuUP Counter > Confidence Threshold

No Is this PDU to be sampled anyway (i.e. count of PDUs % sample rate = 0)?

Yes

X = Calculate HEC from Iu UP Frame Header (first 4 octets of data)

No Is X = 3rd byte of data Publish PDU with event name IssSSSAR_ IuUPSupported Increment IuUP counter (capped) Is IuUP Counter > Confidence Threshold

Yes

No Update Counters. (Increment unknown count, decrement IuUP Count)

Yes

No

Is Counter > Unknown Count? Yes

No

Publish PDU with event name IssSSSAR_ Unknown

Tell Config module to disable stream Update Table Data

Data will be held for each Channel ID on each ATM stream

Figure 3-4 IuUP Frame Discovery

Formatted Formatted Formatted

Page 10 of 14

Ref: e4260-90270-018e4260-90270-018 Version: 0.110.110.10Status: DraftDraft Agilent Confidential

Protocol Discovery for AAL2 PacketsProtocol Discovery for AAL2 Packets

Formatted: English (U.K.)

3.2.4 Table Data

The following data will be stored within the AAL2 Discovery & Filter Module to give other users access to the states of the AAL2 streams. Name VCI/VPI/CID Start Time Traffic Type Type AtmChanID Description Contains unique reference to ATM Stream. VPI/VCI/CID/Tributary/Bearer/Card. Timespec Time stream discovered. AtmBuffer:: Indication of discovered protocol on this channel, tProtocolIndication either IuUP, Iub(RACH | FACH | DCCH) or Unknown. Uint64_t Count of frames on this channel since starting. Enabled or Disabled (or Unknown ?) Length of Time before recheck of disabled stream is tried again. Number of consecutive frames which havent been classified. Level of confidence that this channel in this stream has been qualified to IuUP.
Table 3-2 AAL2 Discovery Data

Number of Frames Seen Stream State Timeout Unknown Count Confidence Level

Timespec Uint32_t Uint16_t

Formatted Formatted Formatted

Page 11 of 14

Ref: e4260-90270-018e4260-90270-018 Version: 0.110.110.10Status: DraftDraft Agilent Confidential

Protocol Discovery for AAL2 PacketsProtocol Discovery for AAL2 Packets

Formatted: English (U.K.)

3.2.5 State Diagram

The following state diagram attempts to explain the possible states of an ATM Stream (Virtual Channel) STREAMING BLOCKED IUUP UNKNOWN TIMEOUT ATM Stream enabled, data expected to be IuUP or Iub. ATM Stream Disabled, data format unknown (once unknown count has reached pre-defined threshold [nominally 100]). Format on ATM Stream is known (thought) to be IuUP or Iub. Format on ATM Stream Unknown, i.e. Not IuUP or Iub. Defined by the configuration or overridden by the AAL2 Discovery & Filter Module, which determines when a blocked ATM Stream should be rechecked. Although ATM Stream was previously transmitting IuUP or Iub data, it should be rechecked periodically to ensure that it is still doing so. Determining which type of data is on this ATM Stream. Check unknown state is continuous for at least a predefined threshold (nominally 100), before blocking.

RE-SAMPLE CHECKING COUNTING

Streaming

Blocked

TIMEOUT IUUP

RE-SAMPLE UNKNOWN Checking

UNKNOWN

Counting

Figure 3-5 State Diagram of ATM Stream (Virtual Channel)

Formatted Formatted Formatted

Page 12 of 14

Ref: e4260-90270-018e4260-90270-018 Version: 0.110.110.10Status: DraftDraft Agilent Confidential

Protocol Discovery for AAL2 PacketsProtocol Discovery for AAL2 Packets

Formatted: English (U.K.)

4 Assumptions and Constraints

4.1 Assumptions 4.1.1 IuUP Frame Protocol
Assume that no other protocol has a 4 octet header with the same 6 bit header checksum at Octet 3. According to 3GPP Specs 25.415 v 3.2.0 (15th Mar 2000) IuUP Version 0 frames (for PDU type 0) have exactly the same format as IuUP Version 1 frames (3GPP Spec 25.415 v3.12.0 26th Sept 2002)

4.1.2 Iub RACH / FACH / DCCH Frame Protocol

Assume that the frequency of RACH / FACH / DCCH data frames within an ATM stream is high enough that an interesting stream will not be disabled because of a high number of consecutive non RACH/FACH / DCCH data frames.

4.1.3 VC.CID combination

VC.CID combination should be valid across all voice calls, the stream personality will not change mid-transmit. However, due to sampling it is possible that the format of data will change before we continue to sample, so there is a possibility that some data will be lost.

4.1.4 Threshold for IuUP Frame receipt confidence check

This will be low (maybe only 2 initially), and will be a resource/configuration value.

4.1.5 Timeouts Receiving complete SSSAR PDU

The Asap Configuration Module determines if a stream has been idle for a pre-configured length of time, and will disable it, placing an event on the bus informing the other MEB modules it is doing so. The SSSAR Engine and AAL2 Discovery & Filter modules will delete all existing pointers & update data relating to that stream. It is possible that the AAL2 Discovery & Filter module will override the timeout for individual ATM Streams.

4.2 Outstanding Issues 4.2.1 Storage of messages for a length of time

We may have to store AAL2 messages up for a length of time in case clients request them, to avoid loss of data. If the time limit is set to zero then no data will be stored. We initially think the time range should be set from 0 to 10 seconds.
Formatted Formatted Formatted

Page 13 of 14

Ref: e4260-90270-018e4260-90270-018 Version: 0.110.110.10Status: DraftDraft Agilent Confidential

Protocol Discovery for AAL2 PacketsProtocol Discovery for AAL2 Packets

Formatted: English (U.K.)

4.2.2 Destruction of idle streams

The Asap Config module knows when a stream is quiet, so will monitor the stream and if it determines that the stream is idle, will publish an event saying that stream destruction is imminent. The AAL2 Discovery & Filter module will then have to delete any pointers and stored data relative to that stream, to avoid memory leakage.

4.2.3 Media Manager Plugins

Still to look at what is needed for AAL2 media manager plugins for AAL2 IuUP. Also discussion required on what the Unknown AAL2 messages will need for Media Manager plugin.

4.2.4 Other AAL2 Formats

Discussion needed on formats other than IuUP or Iub. << END OF DOCUMENT >>

Formatted Formatted Formatted

Page 14 of 14

Ref: e4260-90270-018e4260-90270-018 Version: 0.110.110.10Status: DraftDraft Agilent Confidential