Descripción de los casos de uso

Signaling messages to be traced include the following messages:

l Subscriber signaling messages

l Cell signaling messages

l Signaling messages at standard interfaces

l Signaling messages in protocol of transport network layer

Before tracing signaling, you are recommended to adjust the BAM time and time on the test computer.

I. Tracing Subscriber Signaling Messages

Subscriber signaling messages include the following messages:

l Single subscriber signaling messages at standard interface

l Single subscriber signaling messages at subscriber and signaling plane

l IOS messages

1) Tracing single subscriber signaling messages at standard interfaces. The interfaces include lu, lur, lub, Uu interface. After typing the UE identity (IMSI, TMSI,

2007-12-13 All rights reserved Page185 , Total220 P-TMSI, or IMEI) and selecting the standard interface, you can trace the single subscriber signaling messages at standard interfaces. You can obtain UE IMSI by consulting the customer service center of the carrier or querying it from HLR. In addition, you can confirm IMSI by RANAP COMMON ID message. TMSI and P-TMSI change after TMSI relocation. If you need trace them, you can obtain them from RRC CONN REQUEST message. After UE reset and expiration of TMSI reconfiguration timer, TMSI or P-TMSI change. Therefore you must retrace them.

You can obtain IMEI from UE vendor. You can trace emergency subscriber without SIM module by it. In case of RAB assignment failure, RAB release failure, paging failure, lu release failure, safety mode control failure, initial UE message failure, and transition failure, you can locate the obstacle and solve the problem by analyzing messages at lu interface. In case of radio link setup failure, radio link adding failure, radio link removal, common transmission channel resource release failure, downlink power control failure, and paging failure, you can locate the obstacle and solve the problem by analyzing messages at lub or lur interface. In case of RRC connection setup failure, RB setup failure, PCH reallocation failure, and cell update failure, you can locate the obstacle and solve the problem by analyzing messages at Uu interface. The lu interface messages (RANAP protocol messages) and lur interface messages (RANSAP protocol message) of the task UE tracing (standard interface messages) are connection-oriented messages, not non-connection messages. The lub interface messages (NBAP protocol message) of the task UE tracing (standard interface messages) are dedicated NBAP messages, but not common NBAP messages. If you trace single subscriber by using IMSI, and the RRC CONNECT REQUEST message includes the consistent IMSI when UE is accessing the network, you can trace the single subscriber by tracing messages after RRC CONN REQUEST message. If you trace single subscriber by using IMSI, the RANAP COMMON ID message, but not RRC CONNECT REQUEST, include the IMSI when UE is accessing the network, you can trace the single subscriber by tracing messages after RANAP COMMON ID message. The messages before RANAP COMMON ID message are dropped.

The index USER on the traced result displayed in the UE Tracing (Standard Interface Messages) task view window means differently to different interfaces.

For lu and lur interface messages, USER is DPC ID. For lub interface messages, USER is NodeB ID. For Uu interface messages, USER is invalid (oxFFFFFFFF).

On the message view window, right click. In the displayed menu, you can select Board Response List, and can view all WSPU information of unreceived response messages and received response messages.

2) Tracing single subscriber signaling messages at subscriber and signaling plane The messages are at signaling and user plane at standard interfaces related to specific tracing event during calling by specified UE. You can type the UE identity (IMSI, TMSI, P-TMSI, or IMEI) and select the specific events. Tracing this type of messages has something in common with the task UE tracing (standard interface messages): the messages to be traced are related and triggered in tracing specified UE in calling. Yet they are different. The task UE tracing (standard interface messages) involves signaling messages at four standard interfaces. The task UE tracing (subscriber and signaling plane) involves standard messages at signaling plane, self-defined information at signaling plane, and reported data at user plane. It divides the traced messages according to report information content.

Namely, you can select different traced messages by selecting different events.

The task UE tracing (subscriber and signaling plane) involves much information, which impacts system operation. Therefore, reduce the traced events as possible.

The RNC can trace 6 UEs at most. If the task UE tracing (standard interface messages) can meet the requirements, use this task as possible.

2007-12-13 All rights reserved Page186 , Total220 3) IOS tracing. IOS tracing is tracing all subscribers meeting default conditions. By IOS tracing, you continuously traced the calls of specified number (the number is specified at beginning of the task) which access the network in specified cell. The content to be traced is the messages generated during calling. Select the types of traced messages by selecting traced events. Only the subscribers access the cell by RRC or migrate (including inter-system handover) to the cell. Stopping tracing is triggered when RRC is released or the subscribers migrate out of the cell.

Type the number of continuous calls to be traced, sampling standard, and tracing time. The sampling standard is defined according to RAB parameter restriction.

The RAB parameter restriction is valid only when tracing a new call starts. If a call meets the sampling standard, the call keeps being traced despite that the RAB parameters are modified after starting the call. If the RAB parameters does not meet sampling standard at the beginning but meet sampling standard after modification, the call will not be traced. The task IOS tracing involves much information, which impacts system operation. The index of the upper limit of number of calls traced simultaneously must be smaller than 6. Tracing all events at a time is not recommended. In addition, use the task as less frequently as possible.

II. Tracing Cell Signaling Messages

Tracing cell signaling messages is tracing NBAP common messages or

USER_VOLUMN events in specified cells. The USER_VOLUMN events include self-defined messages, reflecting statistics information of UE in the cell. Specify the cell by typing cell ID. Select the type of messages to be traced by selecting traced events.

The cells to be traced must be activated first.

The task cell tracing involves much information, which impacts system operation. The system supports tracing 32 cells at most simultaneously. If lub interface tracing meets requirements, use it as possible.

III. Tracing Signaling Messages at Standard Interfaces

The interfaces include Uu, lub, lur, and lu interface. When the subscribers are in a large number, the signaling to be traced at standard interfaces is much. This impacts system operation. Solve the problem by using testability log and tracing single subscriber.

1) Tracing Uu interface messages.

This traces all or partial signaling messages at Uu interface in the selected cell. The USER displayed in the traced result on the message view window is the cell that tr ansmits or receives the message.

2) Tracing lub interface messages.

This traces standard messages at lub interface, including NBAP dedicated messages and common messages. The USER displayed in the traced result on the task message view window is the opposite NodeB ID. The NodeB ID is queried by executing LST NODEB command. The NCP and CCP port number are queried by executing LST IUBP command.

3) Tracing lur interface messages.

This traces standard messages at lur interface, including connection-oriented and non-connection messages. The USER in the traced result displayed task message view window is the DPC ID of opposite RNC. Query DPC ID by executing LST N7DPC command.

4) Tracing lu interface messages This traces standard messages at lu interface, including connection-oriented and non-connection messages. The USER in the traced result displayed task message

2007-12-13 All rights reserved Page187 , Total220 view window is the DPC ID of opposite CN. Query DPC ID by executing LST N7DPC command.

IV. Signaling Messages in Protocol of Transport Network Layer

The messages include QAAL2, SCCP, MTP3B, and SAAL protocol messages. Tracing these messages helps analyze failure at interface link.

In case of RAB assignment failure, RRC setup failure, and cell setup failure, you can locate the obstacle and solve the problem by tracing QAAL2 protocol messages. When the CN side cannot receive direct transmission messages and the RNC cannot receive paging messages sent by CN:

l If the target signaling point is reachable, you can locate the obstacle and solve the problem by tracing SCCP protocol messages.

l If the target signaling point is unreachable or MTP3B link is unavailable, you can locate the obstacle and solve the problem by tracing MTP3B protocol messages.

l If the SAAL link is unavailable, you can locate the obstacle and solve the problem by tracing SAAL protocol messages.