Subscriber Session Trace Functional Description; Operation; Trace Session; Trace Recording Session - Cisco ASR 5000 Series Administration Manual

▀ Subscriber Session Trace Functional Description

Subscriber Session Trace Functional Description
This section describes the various functionality involved in tracing of subscriber session on EPC nodes:

Operation

The session trace functionality is separated into two steps - activation and trigger.
Before tracing can begin, it must be activated. Activation is done either via management request or when a UE initiates
a signaled connection. After activation, tracing actually begins when it is triggered (defined by a set of trigger events).

Trace Session

A trace session is the time between trace activation and trace de-activation. It defines the state of a trace session,
including all user profile configuration, monitoring points, and start/stop triggers. It is uniquely identified by a Trace
Reference.
The Trace Reference id is composed of the MCC (3 digits) + the MNC (3 digits) + the trace Id (3 byte octet string).

Trace Recording Session

A trace recording session is a time period in which activity is actually being recorded and traceable data is being
forwarded to the TCE. A trace recording session is initiated when a start trigger event occurs and continues until the
stop trigger event occurs and is uniquely identified by a Trace Recording Session Reference.

Network Element (NE)

Network elements are the functional component to facilitate subscriber session trace in mobile network.
The term network element refers to a functional component that has standard interfaces in and out of it. It is typically
shown as a stand-alone AGW. Examples of NEs are the MME, S-GW, and P-GW.
Currently subscriber session trace is not supported for co-located network elements in EPC network.

Activation

Activation of a trace is similar whether it be via the management interface or via a signaling interface. In both cases, a
trace session state block is allocated which stores all configuration and state information for the trace session. In
addition, a (S)FTP connection to the TCE is established if one does not already exist (if this is the first trace session
established, odds are there will not be a (S)FTP connection already established to the TCE).
If the session to be traced is already active, tracing may begin immediately. Otherwise, tracing activity concludes until
the start trigger occurs (typically when the subscriber/UE under trace initiates a connection). A failure to activate a trace
(due to max exceeded or some other failure reason) results in a notification being sent to the TCE indicating the failure.
▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide
100
Configuring Subscriber Session Tracing
OL-22987-01