Download - Northbound Data Export Guide (UMTS CHR Standard Signaling)

Nastar V600R010

Northbound Data Export Guide (UMTS CHR Standard Signaling)

Issue 02

Date 2012-10-15

HUAWEI TECHNOLOGIES CO., LTD.

Issue 02 (2012-10-15) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd. i

Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior

written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective

holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not be

within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,

information, and recommendations in this document are provided "AS IS" without warranties, guarantees or

representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

http://www.huawei.com/

mailto:[email protected]

Nastar

Northbound Data Export Guide (UMTS CHR Standard

Signaling) About This Document


Copyright © Huawei Technologies Co., Ltd.

ii

About This Document

Overview

This documents describes the method of exporting Nastar UMTS CHR standard signaling

data through the northbound interface and the structure and contents of the UMTS CHR data

file.

Product Version

The following table lists the product versions corresponding to this document.

Product Name Product Version

Nastar V600R010C00

Intended Audience

This document is intended for network planning and optimization engineers

Change History

02 (2012-10-15)

This issue is the second official release. Compared with 01(2012-06-16), this issue has the

content description optimized.

01 (2012-06-16)

This issue is the first official release.

Nastar


Signaling) Contents



iii

Contents

About This Document .................................................................................................................... ii

1 Introduction to CHR Standard Signalling Northbound Data Export .............................. 1-1

1.1 Nastar Networking Architecture .................................................................................................................... 1-2

1.2 Working Principles of Data Export ............................................................................................................... 1-3

2 Flowchart for Data Export ........................................................................................................ 2-1

3 Requirements for System Specifications .............................................................................. 3-1

4 Subscribing to the Northbound Data..................................................................................... 4-1

5 Obtaining the UMTS CHR Standard Signalling Northbound Data ............................... 5-1

6 Parsing the UMTS CHR Standard Signalling Northbound Data .................................... 6-1

7 Maintaining the Northbound Data ........................................................................................ 7-1

8 Appendix ..................................................................................................................................... 8-1

8.1 Structure of the CHR Standard Signalling Northbound Data File ................................................................. 8-1

8.2 Contents of the CHR Standard Signalling Northbound Data File ................................................................. 8-3

Nastar


Signaling) Figures



iv

Figures

Figure 1-1 Nastar networking architecture ......................................................................................................... 1-2

Figure 1-2 Working principles of the data export function in direct networking scenario ................................. 1-4

Figure 1-3 Working principles of the data export function in relay-based networking scenario ........................ 1-4

Figure 2-1 Flowchart for data export .................................................................................................................. 2-1

Nastar


Signaling) Tables



v

Tables

Table 1-1 Description of each functional unit in the networking architecture diagram ...................................... 1-3

Table 2-1 Flowchart description ......................................................................................................................... 2-2

Table 3-1 System Specification .......................................................................................................................... 3-1

Table 4-1 Parameters for setting data subscription ............................................................................................. 4-2

Table 5-1 Description of fields in the data file name .......................................................................................... 5-2

Table 8-1 File structure ....................................................................................................................................... 8-1

Table 8-2 MI field description ............................................................................................................................ 8-3

Table 8-3 MI data type ........................................................................................................................................ 8-4

Table 8-4 Types of standard signaling messages ................................................................................................ 8-4

Nastar


Signaling)

1 Introduction to CHR Standard Signalling Northbound

Data Export



1-1

1 Introduction to CHR Standard Signalling Northbound Data Export

About This Chapter

With mobile operators embarking on building their own radio network optimization platform,

it is required that equipment manufacturers provide the call history record (CHR) data for

network analysis.

The Nastar provides the northbound CHR data (created during one call) of RAN13 and earlier

versions. As the northbound CHR data depends on NE logs, it has the following

shortcomings:

Multiple radio access bearers (RABs) are not supported. Multiple RABs is common for

the smart terminal.

The switch information is incomplete. Only two switches are recorded during one call.

The data timeliness is poor. Data is recorded and reported only after a call ends.

Data is not standard. The data is recorded in the NE proprietary log. The extracted

information element (IE) content and recording format vary according to the NE version.

Due to the preceding problems, the original northbound CHR data cannot meet the customer's

requirement for network analysis. Therefore, the CHR content and format are redesigned in

RAN14 or later.

For the Huawei RAN14, the Nastar takes the CHR open standard signaling as the northbound

data source and provides rich standard message types to meet the customization requirement

of operators. In addition, the Nastar will provide more standard, efficient, and dependable

interfaces with better compatibility.

1.1 Nastar Networking Architecture

This section describes the Nastar networking architecture and CHR Standard Signalling

Northbound Data sources on the network.

1.2 Working Principles of Data Export

This section describes the working principles for the Nastar system to export CHR Standard

Signalling Northbound Data in the direct and relay-based networking schemes.

Nastar


Signaling)


Data Export



1-2

1.1 Nastar Networking Architecture

This section describes the Nastar networking architecture and CHR Standard Signalling

Northbound Data sources on the network.

Figure 1-1 shows the Nastar networking architecture, and the red box shows the saving

position of CHR Standard Signalling Northbound Data on the network.

Figure 1-1 Nastar networking architecture

Nastar


Signaling)


Data Export



1-3

Table 1-1 describes each functional unit in the networking architecture diagram.

Table 1-1 Description of each functional unit in the networking architecture diagram

Functional Unit Description

Nastar The Nastar system is used to locate and analyze the quality

problems of wireless networks. This system supports

multi-user operations and multiple performance analysis.

Therefore, the system serves as a fundamental support

platform for further analysis of wireless networks and problem

location.

eSAU Is a data summarization unit and a mandatory component of

the Nastar system. The unit is deployed on the OSS side as a

ATAE-based or HP PC server, summarizes the analysis data

preprocessed by the SAU, and exports the summarized CHR

data to the Nastar server.

During the northbound data export process, the eSAU

receives, summarizes the data, and then compresses and stores

the data.

M2000 Is a uniform management platform of Huawei mobile

networks. It manages the mobile NEs manufactured by

Huawei. The M2000 provides performance data and

configuration data for the Nastar system.

During the northbound data export process, the M2000

provides the relay function for commands and data.

SAU The service aware unit (SAU) is an optional component of the

Nastar system. The SAU is installed on the base station

controller (BSC) as the board, such as SAUc, and

preprocesses the raw data from NEs as required by the Nastar

system for analysis.

During the northbound data export process, the SAU

preprocesses the data collected from the RNC and upload the

data to the eSAU.

1.2 Working Principles of Data Export

This section describes the working principles for the Nastar system to export CHR Standard

Signalling Northbound Data in the direct and relay-based networking schemes.

The Nastar system provides two networking schemes to meet operators' different

requirements: direct networking and relay-based networking. Operators select the networking

scheme as required.

In the direct networking scheme, the eSAU directly obtains analysis data from NEs,

which reduces the impact on the performance of M2000 servers.

In the relay-based networking scheme, the eSAU must obtain analysis data from NEs

through the M2000. The M2000 functions as a relay server between the eSAU and NEs,

which enhances NEs' data security.

Nastar


Signaling)


Data Export



1-4

Figure 1-2 shows the working principles of the data export function in direct networking

scenario, and Figure 1-3 shows the working principles of the data export function in the

relay-based networking scenario.

Figure 1-2 Working principles of the data export function in direct networking scenario

Figure 1-3 Working principles of the data export function in relay-based networking scenario

Nastar


Signaling) 2 Flowchart for Data Export



2-1

2 Flowchart for Data Export

This section describes the flowchart for data export.

Figure 2-1 shows the flowchart for data export.

Figure 2-1 Flowchart for data export

Table 2-1 describes each operation in Figure 2-1.

Nastar


Signaling) 2 Flowchart for Data Export



2-2

Table 2-1 Flowchart description

No. Procedure Description Reference

1 Subscribe to

the

northbound

data.

Delivers northbound

subscription on the Nastar

client.

4 Subscribing to the

Northbound Data

2 Obtain the

northbound

data.

Obtains required data from the

eSAU and upload the data to a

local PC in SFTP mode.

5 Obtaining the UMTS CHR

Standard Signalling

Northbound Data

3 Parse the

northbound

data.

Develops a tool that is used to

parse data for other analysis

according to file rules.

6 Parsing the UMTS CHR

Standard Signalling

Northbound Data

Nastar


Signaling) 3 Requirements for System Specifications



3-1

3 Requirements for System Specifications

Before exporting data, check whether the Nastar system meet the requirements, including

version, bandwidth, and storage space requirements.

Version Mappings

Before exporting data, check whether the NE and OSS versions meets requirements.

The NE and OSS version required for the northbound function is consistent with the Nastar

software mapping relationship.

For detailed mapping relationship, see the release notes corresponding to the Nastar software

installed on the site.

Obtain the Nastar V600R010 release notes in the version mapping documentation package.

Obtaining method on the http://support.huawei.com: Documentation > Wireless > Wireless

Performance & RNP & RNO > Wireless RNP & RNO Tools > Release Documentation > GENEX

Nastar > GENEX Nastar V600R010.

Specifications Evaluation

The transmission bandwidth requirement varies because the amount of data varies with the

network scale and the selected types of standard signaling messages to be exported.

Specifications evaluation shown in Table 3-1 is for reference only.

Table 3-1 System Specification

Item Unit

UMTS MAX (=100%)

UMTS AVG1 (<=40%)

UMTS AVG2 (<=10%))

Description

BHCA K 5300 2120 530 Traffic Model:

MAX indicates that the Nastar is

deployed based on the maximum

specifications of six subracks.

AVG indicates that the Nastar is

deployed based on 40% and 10% of

the maximum specification.

Busy-H

our

Traffic

per

RNC

(CS)

Erl 167500 67000 16750

Nastar





3-2

Item Unit

UMTS MAX (=100%)

UMTS AVG1 (<=40%)

UMTS AVG2 (<=10%))

Description

Busy-H

our

Traffic

per

RNC

(PS)

Gb

ps 40 16 4

Amount

of the

Raw

CHR

data

from

Each

RNC

During

Busy

Hours

GB 13.5 5.4 1.35

If the RNC is of the RAN14 version,

the raw CHR data amount needs to be

multiplied by 0.7. Amount

of the

Northbo

und

Data

from

Each

RNC

During

Busy

Hours

GB 9.45 3.78 0.945

Convert

ed

Amount

of the

Northbo

und

Data

from

Each

RNC

During

One

Day

GB 136.08 54.43 13.61

The 14.4 busy hours are obtained by

using the following formula: 24 hours x

0.6 = 14.4 busy hours.

Number

of Cells

Under

Each

RNC

NA 5100 3400 1700 The RNC configurations are estimated

based on the traffic model.

Nastar





3-3

Item Unit

UMTS MAX (=100%)

UMTS AVG1 (<=40%)

UMTS AVG2 (<=10%))

Description

Number

of

RNCs

converte

d from

400

equivale

nt NEs

NA 10 15 29 400 equivalent NEs for the Nastar

correspond to 50,000 UMTS cells.

Amount

of the

Northbo

und

Data

from

400

Equival

ent NEs

per

Hour

GB 94.5 56.7 27.405

On the Nastar server, the space used for

storing northbound result files is less

than or equal to 200 GB by default. The

maximum configuration is 600 GB. For

details, see "Policies for Deleting

Stored Data." Northbound users need to

obtain data in time based on actual

network storage conditions, thereby

preventing data from being lost because

the amount of data stored on the Nastar

server exceeds the specified space

threshold.

Amount

of the

Northbo

und

Data

from

400

Equival

ent NEs

During

One

Day

GB 1360.8 816.48 394.632

Amount

of the

Northbo

und

Data

from

400

Equival

ent NEs

During

Three

Days

GB 4082.4 2449.44 1183.89

6

Nastar





3-4

Item Unit

UMTS MAX (=100%)

UMTS AVG1 (<=40%)

UMTS AVG2 (<=10%))

Description

Northbo

und

Bandwi

dth

Require

ment

(On the

RNC/S

AU

Side)

Mb

ps 22 9 2.2

The required bandwidth is obtained and

rounded up based on the bandwidth

required during busy hours. Northbo

und

Bandwi

dth

Require

ment

(On the

eSAU

Side)

Mb

ps 220 135 64

Data

Transmi

ssion

Delay

Mi

n 15 15 15 -

The Nastar exports CHR data by means of source code streams which carry information of the standard

signaling messages collected from NEs. This not only enriches the content exported but also improves

the timeliness of data transmission. In addition, for the same number of NEs originally managed by the

earlier version of Nastar, the Nastar raises higher requirements on bandwidth and storage overheads

because the content of code streams is much more than that of key IEs processed on the device side.

Therefore, customers are advised to obtain data by a smaller frequency and parse the data in real time in

order to reduce the pressure for the Nastar server to store data and the pressure for third-party tools to

analyze data.

Nastar


Signaling) 4 Subscribing to the Northbound Data



4-1

4 Subscribing to the Northbound Data

The Nastar system provides the function of setting the data subscription task that is used to

export CHR data for analysis and processing by operators.

Prerequisite You have logged in to the Nastar client.

Context

The Nastar provides the northbound data subscription function. To subscribe to the

northbound data, MML commands are issued to enable the NE function, and then the theme

function is delivered to subscribe to related northbound data information.

Procedure

Step 1 Perform the following procedure to issue MML commands to enable the NE function.

1. On the menu bar of the Nastar client, choose Maintenance > Data Subscription

Management and select the UMTS tab in the left pane.

2. Click the Basic Subscription Management tab.

3. In the NE object navigation tree of the UMTS tab page, select the required NEs.

4. Click Set on the Basic Subscription Management tab page.

5. In the CHR Customized Northbound Data drop-down list of the displayed Basic

Subscription Management dialog box, select ON. In the Advanced Parameters

Settingdialog box, customize the standard signaling type to be exported by NEs through

the northbound interface and click OK.

Nastar





4-2

Step 2 Perform the following procedure to deliver the theme function and subscribe to related

northbound data.

1. Click the CHR Standard Signalling Northbound Data tab and click ON. The

Parameter Setting dialog box is displayed. Modify the parameters as required.

For descriptions of the NastarUMTS data subscription parameters, see Table 4-1.

Table 4-1 Parameters for setting data subscription

Parameter Description

Time Setting Is used to set the data subscription period.

Busy Hours

Setting

Is used to set the busy hours of data subscription.

Select All Day to collect data of the entire day; select Busy Hour to collect

data in the specified period.

Storage

Position

Is used to set the path for saving data.

The path for storing the northbound customization data of UMTS CHR

Standard Signalling Northbound Data on the eSAU server is

export/home/northdata/UCHRStdSignal.

2. After the setting is complete,click Next. Customize the standard signaling message type

to be exported and click Complete.

Nastar





4-3

3. Check whether the northbound data subscription is successful.

View the task execution in Logs in the lower part of the Data Subscription

Management tab page. If Action Result is Succeed, the northbound data subscription is

successful. If the northbound data subscription fails, verify that the procedure is correct

and subscribe to the northbound data again or contact Huawei technical support.

----End

Nastar


Signaling)

5 Obtaining the UMTS CHR Standard Signalling

Northbound Data



5-1

5 Obtaining the UMTS CHR Standard Signalling Northbound Data

This section describes how to download the northbound data in the specified directory on the

eSAU server to the local PC in FTP mode for later analysis.

Prerequisite You have subscribed to the UMTS CHR Standard Signalling Northbound Data. For

details, see 4 Subscribing to the Northbound Data.

You have obtained the password of user northuser.

The tool supporting SFTP is available. You are advised to use the PSFTP tool provided

by Huawei.

The PSFTP software can be downloaded at http://support.huawei.com.

Obtain the PSFTP software by choosing Software Center > Controlled Tool

(Mini-Tool Software) > Wireless Product Line > Wireless Performance & RNP &

RNO > iManager Nastar > Nastar Tools.

The PC communicates properly with the eSAU server, and the eSAU server works

properly.

Context User northuser is used to access the export/home/northdata directory. During the

installation of the eSAU server software, user northuser is automatically created in the

system, and therefore you do not need to create user northuser manually.

The initial password of user northuser is Changeme_123. For details about

password-related problems, contact Huawei technical support.

The format of data storage directory:

export/home/northdata/UCHRStdSignal/[NeName], in which [NeName] indicates the

RNC name.

For example, export/home/northdata/UCHRStdSignal/RNC16.

The naming convention of the data file:

RNC%RNCID[%FILETYPE%]%SubrackNo%Log%StartTime%_%EndTime%.log.zip.

dat. If the data file has been compressed, the file name extension is .gz.

Table 5-1 describes the field meanings.

Nastar


Signaling)


Northbound Data



5-2

Table 5-1 Description of fields in the data file name

Field Name

Length Meaning

RNC 3 Character type. Fill in RNC by default.

RNCID 4 Digit type. Fill in the actual RNC ID of the NE.

FILETYPE 4 Character type. Fill in PCHR by default.

SubrackNo 2 Digit type. It indicates the subrack number.

Log 3 Character type. Fill in Log by default.

StartTime 14 Digit type. The format is YYYYMMDDHHMMSS.

EndTime 14 Digit type. The format is YYYYMMDDHHMMSS.

For example,

RNC0161_[PCHR]00Log20120406100511_20120406101011.log.zip.dat.gz.

Procedure

Step 1 Run the following command to connect to the server:

1. Double-click psftp.exe to start PSFTP.

2. Run the following command to start the FTP connection.

psftp> open eSAU server IP address

3. Enter user northuser and its password, and press Enter.

Step 2 Perform the following command to check whether CHR data is available in the

export/home/northdata directory:

psftp> ls

If... Then...

Data is unavailable in the

directory

Perform Step 3 to resolve the problem and perform the

subsequent operations.

Data is available in the

directory

Skip Step 3 and perform the subsequent operations.

Step 3 If CHR Standard Signalling Northbound Data is unavailable in the directory, perform the

following operations to resolve the problem:

1. On the Nastar client, choose Maintenance > Data Subscription Management and

select the UMTS tab in the left pane. Click Set on the Basic Subscription Management

tab page. In the displayed Basic Subscription Management dialog box, confirm

whether ON is selected from the CHR Customized Northbound Data drop-down list.

If no, select ON.

Nastar


Signaling)


Northbound Data



5-3

2. If no data is available, the NE CHR function may not be enabled. Contact Huawei

technical support.

Step 4 Perform the following operations to obtain the northbound CHR Standard Signalling

Northbound Data source from the export/home/northdata directory.

1. Run the following command to set the save path on the local PC. Assume that the local

save path is D:\.

psftp> lcd D:\

The save path of the data files on the local PC cannot contain any space or Chinese character.

In the Microsoft Windows operating system, the desktop path contains spaces, for example,

C:\Document sand Settings\Administrator\Desktop. Therefore, do not store data files on the

desktop.

2. Run the following command to switch to the data file directory to be downloaded on the

eSAU server.

psftp> cd data file directory

For example, cd export/home/northdata/UCHRStdSignal/RNC16

3. Run the following command to download data files to the local PC:

psftp> get data file name

For example, get

RNC0161_[PCHR]00Log20120406100511_20120406101011.log.zip.dat.gz

You can download all files of a folder by running the command: get -r data folder.

4. Enter exit after the file is downloaded to exit the PSFTP software.

----End

Nastar


Signaling)

6 Parsing the UMTS CHR Standard Signalling

Northbound Data



6-1

6 Parsing the UMTS CHR Standard Signalling Northbound Data

The exported data is stored in binary mode. Operators can parse the exported CHR Standard

Signalling Northbound Data based on the description of the data file format.

Procedure

Step 1 Operators can parse data using the self-developed tool based on the CHR Standard Signalling

Northbound Data file structure and contents.

For details about the CHR Standard Signalling Northbound Data file structure and contents,

see 8.1 Structure of the CHR Standard Signalling Northbound Data Fileand8.2 Contents of the

CHR Standard Signalling Northbound Data File.

----End

Nastar


Signaling) 7 Maintaining the Northbound Data



7-1

7 Maintaining the Northbound Data

This section describes how to set the northbound data storage period by time or space.

Prerequisite You have the permission to maintain the northbound data.

You have logged in to the Nastar client.

Context Time Dimension

By default, the CHR Standard Signalling northbound data is stored for one days in the

Nastar system. Operators can change the storage period as required.

Space Dimension

By default, the space specification provided by the eSAU is 200 GB. Operators can

configure it as required.

When the data stored by the eSAU exceeds any specification (time or space), the system

deletes the data automatically.

Automatic Data Deletion Mechanism

The system checks the data once upon the system startup and every hour later.

The system checks whether the northbound data files expire by time and exceed the

specified size by space.

If the files expire or exceed the specified size, the system deletes them. The files are

deleted in the sequence of their generation time, and the earliest file is deleted first.

Procedure

Step 1 Choose Maintenance > Data Maintenance Management.

Nastar


Signaling) 7 Maintaining the Northbound Data



7-2

Step 2 Select the data node (for example, UMTS CHR Customized Northbound Data) of which

the time specification needs to be modified from the navigation tree in the left pane, and then

select Delete Data in the right pane.

Step 3 Enter the number of data storage days (a maximum of seven days) in Storage Period Setting

（Days） and click Storage Period Setting.

The system compares the files creation time, the number of data storage days, and the current

time to check whether the files expire.

Step 4 Click Immediately Maintain Data.

----End

Nastar


Signaling) 8 Appendix



8-1

8 Appendix

About This Chapter

This appendix describes the structure and contents of CHR files.

8.1 Structure of the CHR Standard Signalling Northbound Data File

This section describes the structure of the CHR Standard Signalling Northbound Data source

file. You can refer to this section when parsing the CHR Standard Signalling Northbound Data

file.

8.2 Contents of the CHR Standard Signalling Northbound Data File

This section describes the contents of the CHR Standard Signalling Northbound Data source


file.

8.1 Structure of the CHR Standard Signalling Northbound Data File

This section describes the structure of the CHR Standard Signalling Northbound Data source


file.

Table 8-1 File structure

Structure Type

Length Component Description

File dword Flag Indicates the identifier (ID)

showing whether the file is intact

(EFEFEFEF).

dword MuNum Indicates the number of

measurement units (MUs).

- MuFileTimeInfo muTime Indicates the time information of

the file.

Nastar





8-2

Structure Type


- MuResultInfo muRes[] Indicates the MU content.

MuFileTim

eInfo

dword period Indicates the statistical period

(second).

By default, the valid value is 0.

- MuDstTimeType

StartTime

Indicates the start time.

- MuDstTimeType

EndTime

Indicates the end time.

MuDstTime

Type

- MuFileDateTimeType dt Indicates the date.

byte isDst Indicates whether to enable the

Daylight Saving Time (DST).

l 0 indicates that the DST is not

enabled.

1 1 indicates that the DST is

enabled.

word timezone Indicates the time zone (which

might be a negative number). The

unit is minute.

word DstOffset Indicates the DST offset (which

might be a negative number). The

unit is minute.

MuFileDate

TimeType

short year Indicates the year.

byte month Indicates the month.

byte day Indicates the day.

byte hour Indicates the hour.

byte minute Indicates the minute.

byte second Indicates the second.

MuResultIn

fo

word MUID Indicates the MU ID.

dword RecordNum Indicates the number of MU

records.

dword Mulength Indicates the bytes in an MU.

- MITypeVecInfo MIList Indicates the MI information

contained in an MU.

byte MORst[] Indicates the CHR or MR data.

MITypeVec word MINum Indicates the number of MIs.

Nastar





8-3

Structure Type


Info - MIInfo MIList[] Indicates the MI description.

MIInfo word MIID Indicates the MI ID.

byte MIType Indicates the type of MI data.

dword MILength Indicates the length of MI data.

8.2 Contents of the CHR Standard Signalling Northbound Data File

This section describes the contents of the CHR Standard Signalling Northbound Data source


file.

Currently the content that is collected from the RAN14 of NE and then transmitted over the

northbound interface includes only one type of events, standard signaling events (EventID=0).

The number of MIs exported for one event of this type is 9. When the file content is being

parsed, the message type of each event is identified based on MsgType (MIID=0x1004), and

the content of key IEs contained in the message is obtained based on MsgContent

(MIID=0x1006). The message content is source code streams encoded by using ASN1, and

includes all the MU and MI fields (which are derived from standard protocols) for the internal

CHRs collected from the RAN12 or RAN13 of NEs.

The following table lists all the MIs.

Table 8-2 MI field description

MI Name

MI ID Type Length Description

ConnSetu

pTime 0x0001 6 8

Time when the signaling connection is

set up.

SrncIdent

ity 0x0002 0 2

Temporary radio network identity of the

user equipment (UE) under its serving

radio network controller (SRNC).

Srnti 0x0003 0 4 Temporary serving radio network

identity of the UE.

MsgRecv

Time 0x1001 6 8

Time when the radio network controller

(RNC) receives the message and starts

decoding the message by using the

ASN1.

MsgItfTy

pe 0x1002 0 1

Type of the message interface. Value

range: 0-IU, 1-IUR, 2-IUB, and 3-UU.

Nastar





8-4

MI Name

MI ID Type Length Description

MsgDir 0x1003 0 1

Direction to which the message is

sent. Value range: 0-to CN, 1-from

CN, 2-to other RNC, 3-from other RNC,

4-to NODEB, 5-from NODEB, 6-to UE,

7-from UE, 8-to SAS, and 9-from SAS.

MsgType 0x1004 0 2

Type of the message. The value of

MsgType is unique for one interface and

is consistent with the value that the

ASN1 defines for each standard

interface. For details about the mapping

between the Key value and message

type, see Table 8-4.

MsgLeng

th 0x1005 0 2

Length of the message before being

decoded by using the ASN1.

MsgCont

ent 0x1006 2

MsgLeng

th

Source code stream that the RNC

receives but has not started decoding by

using the ASN1.

Remarks

1. Each event contains three MI fields, including ConnSetupTime, SrncIdentity, and Srnti,

and these fields are used for combining events during one call into an event.

2. The following table describes the MI data type.

Table 8-3 MI data type

Enumerated Value Data Type Description

0 INT Integer without symbol

1 BYTESTRING Byte stream

2 STRING Character string

6 DATETIME Time type

3. The MsgType field is used to identify the type of each exported message. For the types

of standard signaling messages that the Nastar supports, see the attachment. The Nastar

enables users to subscribe to and export data by message type.

Table 8-4 Types of standard signaling messages

ItfType Key Value

IU 1 RANAP_RAB_ASSIGNME

NT_REQ

Nastar





8-5

ItfType Key Value

IU 2 RANAP_IU_RELEASE_C

OMMAND

IU 3 RANAP_RELOCATION_C

OMMAND

IU 4 RANAP_RELOCATION_P

REPARATION_FAILURE

IU 5 RANAP_RELOCATION_R

EQ


ANCEL_ACK

IU 7 RANAP_SRNS_CONTEXT

_REQ

IU 8 RANAP_SRNS_DATA_FO

RWARD_COMMAND

IU 9 RANAP_PAGING

IU 10 RANAP_COMMON_ID

IU 12 RANAP_SECURITY_MO

DE_COMMAND

IU 13 RANAP_LOCATION_REP

ORTING_CONTROL

IU 16 RANAP_LOCATION_REL

ATED_DATA_REQ

IU 17 RANAP_RAB_ASSIGNME

NT_RESP

IU 18 RANAP_RAB_RELEASE_

REQ

IU 19 RANAP_IU_RELEASE_R

EQUEST

IU 20 RANAP_IU_RELEASE_C

OMPLETE


EQUIRED


EQ_ACK

IU 23 RANAP_RELOCATION_F

AILURE

IU 24 RANAP_RELOCATION_D

ETECT

Nastar





8-6

ItfType Key Value


OMPLETE


ANCEL

IU 27 RANAP_SRNS_CONTEXT

_RESP


DE_COMPLETE


DE_REJECT

IU 30 RANAP_LOCATION_REP

ORT

IU 32 RANAP_INITIAL_UE_ME

SSAGE

IU 33 RANAP_RAB_MODIFY_R

EQ


ATED_DATA_RESP


ATED_DATA_FAIL

IU 36 RANAP_FORWARD_SRN

S_CONTEXT

IU 37 RANAP_DIRECT_TRANS

FER

IU 41 RANAP_ERR_IND

IUR 1 RNSAP_RL_SETUP_REQ

IUR 2 RNSAP_RL_SETUP_RSP

IUR 3 RNSAP_RL_SETUP_FAIL

IUR 4 RNSAP_RL_ADD_REQ

IUR 5 RNSAP_RL_ADD_RSP

IUR 6 RNSAP_RL_ADD_FAIL

IUR 7 RNSAP_RL_DEL_REQ

IUR 8 RNSAP_RL_DEL_RSP

IUR 9 RNSAP_RL_RECFG_PRE

P

IUR 10 RNSAP_RL_RECFG_REA

DY

Nastar





8-7

ItfType Key Value

IUR 11 RNSAP_RL_RECFG_COM

MIT

IUR 12 RNSAP_RL_RECFG_FAIL

IUR 13 RNSAP_RL_RECFG_CAN

CEL

IUR 14 RNSAP_RL_RECFG_REQ

IUR 15 RNSAP_RL_RECFG_RSP

IUR 16 RNSAP_RL_FAIL_IND

IUR 17 RNSAP_RL_RESTORE_IN

D

IUR 18 RNSAP_DL_PWR_CTRL_

REQ

IUR 19 RNSAP_PH_CH_RECFG_

REQ


CMD


FAIL

IUR 22 RNSAP_UL_SIG_TRANSF

_IND

IUR 23 RNSAP_DL_SIG_TRANSF

_REQ

IUR 24 RNSAP_RELOC_COMMI

T

IUR 25 RNSAP_PAGING_REQ

IUR 26 RNSAP_DEDIC_MEAS_I

NIT_REQ


NIT_RSP


NIT_FAIL

IUR 29 RNSAP_DEDIC_MEAS_R

PRT

IUR 30 RNSAP_DEDIC_MEAS_T

ERMNT_REQ

IUR 31 RNSAP_DEDIC_MEAS_F

AIL_IND

Nastar





8-8

ItfType Key Value

IUR 36 RNSAP_COMPRS_MODE

_CMD

IUR 37 RNSAP_ERR_IND

IUR 38 RNSAP_RL_PREEMPTIO

N_REQUIRED_IND

IUR 58 RNSAP_DIR_INFO_TRAN

SF

IUR 59 RNSAP_RL_PARAM_UPT

_IND

IUB 1 NBAP_RL_SETUP_REQ

IUB 2 NBAP_RL_ADD_REQ

IUB 3 NBAP_RL_RECFG_PREP

IUB 4 NBAP_RL_RECFG_COM

MIT

IUB 5 NBAP_RL_RECFG_CANC

EL

IUB 6 NBAP_RL_RECFG_REQ

IUB 7 NBAP_RL_DEL_REQ

IUB 8 NBAP_DL_PWR_CTRL_R

EQ

IUB 9 NBAP_DEDIC_MEAS_INI

T_REQ

IUB 10 NBAP_DEDIC_MEAS_TE

RMNT_REQ

IUB 11 NBAP_COMPRS_MODE_

CMD

IUB 12 NBAP_RL_SETUP_RSP

IUB 13 NBAP_RL_SETUP_FAIL

IUB 14 NBAP_RL_ADD_RSP

IUB 15 NBAP_RL_ADD_FAIL

IUB 16 NBAP_RL_RECFG_READ

Y

IUB 17 NBAP_RL_RECFG_FAIL

IUB 18 NBAP_RL_RECFG_RSP

IUB 19 NBAP_RL_DEL_RSP

Nastar





8-9

ItfType Key Value


T_RSP


T_FAIL

IUB 22 NBAP_DEDIC_MEAS_RP

RT

IUB 23 NBAP_DEDIC_MEAS_FA

IL_IND

IUB 24 NBAP_RL_FAIL_IND

IUB 25 NBAP_RL_RESTORE_IN

D

IUB 60 NBAP_ERR_IND_COMM

IUB 70 NBAP_RL_PREEMPT_RE

Q_IND

IUB 75 NBAP_RL_ACT_CMD

IUB 76 NBAP_RL_PARA_UPDAT

E_IND

UU 1 RRC_ACTIVE_SET_UPD

ATE

UU 2 RRC_ASSIST_DATA_DEL

IV

UU 3 RRC_CELL_CHANGE_OR

DER_FROM_UTRAN

UU 4 RRC_CELL_UPDATE_CO

NFIRM

UU 5 RRC_CNTER_CHECK

UU 6 RRC_DL_DIRECT_TRAN

SF

UU 7 RRC_HO_FROM_UTRAN

_CMD_GSM


_CMD_CDMA2000

UU 9 RRC_MEAS_CTRL

UU 10 RRC_PAGING_TYPE2

UU 11 RRC_PH_CH_RECFG

UU 13 RRC_RB_RECFG

UU 14 RRC_RB_REL

Nastar





8-10

ItfType Key Value

UU 15 RRC_RB_SETUP

UU 16 RRC_RRC_CONN_REL

UU 17 RRC_SECURITY_MODE_

CMD

UU 18 RRC_SIG_CONNECT_RE

L

UU 19 RRC_TR_CH_RECFG

UU 20 RRC_TFC_CTRL

UU 21 RRC_UE_CAP_ENQUIRY

UU 22 RRC_UE_CAP_INFO_CO

NFIRM

UU 24 RRC_URA_UPDATE_CO

NFIRM

UU 25 RRC_UTRAN_MOBIL_IN

FO


_CMD_GERANIU


ATE_CMP


ATE_FAIL

UU 54

RRC_CELL_CHANGE_OR

DER_FROM_UTRAN_FAI

L

UU 55 RRC_CNTER_CHECK_RS

P

UU 57 RRC_INIT_DIRECT_TRA

NSF


_FAIL

UU 59 RRC_MEAS_CTRL_FAIL

UU 60 RRC_MEAS_RPRT

UU 61 RRC_PH_CH_RECFG_CM

P

UU 62 RRC_PH_CH_RECFG_FAI

L

UU 63 RRC_RB_RECFG_CMP

Nastar





8-11

ItfType Key Value

UU 64 RRC_RB_RECFG_FAIL

UU 65 RRC_RB_REL_CMP

UU 66 RRC_RB_REL_FAIL

UU 67 RRC_RB_SETUP_CMP

UU 68 RRC_RB_SETUP_FAIL

UU 69 RRC_RRC_CONN_REL_C

MP

UU 70 RRC_RRC_CONNECT_SE

TUP_CMP

UU 71 RRC_RRC_STATUS


CMP


FAIL

UU 74 RRC_SIG_CONNECT_RE

L_IND

UU 75 RRC_TR_CH_RECFG_CM

P

UU 76 RRC_TR_CH_RECFG_FAI

L

UU 77 RRC_TFC_CTRL_FAIL

UU 78 RRC_UE_CAP_INFO

UU 79 RRC_UL_DIR_TRANSF


FO_CONFIRM


FO_FAILURE

UU 103 RRC_RRC_CONN_REJ

UU 105 RRC_RRC_CONN_SETUP

UU 122 RRC_CELL_UPDATE

UU 123 RRC_RRC_CONNECT_RE

Q

UU 124 RRC_URA_UPDATE

UU 183 RRC_SYS_INFO_CHANG

E_IND

Nastar





8-12

Download - Northbound Data Export Guide (UMTS CHR Standard Signaling)

Top Related