R4G 20 Ste Con Cos 208

EUBD-000041
Ed. 00
RIL
OSS Interface Specification
COPYRIGHT
This manual is proprietary to SAMSUNG Electronics Co., Ltd. and is protected by copyright.
No information contained herein may be copied, translated, transcribed or duplicated for any commercial
purposes or disclosed to the third party in any form without the prior written consent of SAMSUNG Electronics
Co., Ltd.
TRADEMARKS
Product names mentioned in this manual may be trademarks and/or registered trademarks of their respective
companies.
This manual should be read and used as a guideline for properly installing and operating the product.
This manual may be changed for the system improvement, standardization and other technical reasons without prior
notice.
If you need updated manuals or have any questions concerning the contents of the manuals, contact our Document
Center at the following address or Web site:
Address: Document Center 3rd Floor Jeong-bo-tong-sin-dong. Dong-Suwon P.O. Box 105, 416, Maetan-3dong
Yeongtong-gu, Suwon-si, Gyeonggi-do, Korea 442-600
Homepage: http://www.samsungdocs.com
2011 SAMSUNG Electronics Co., Ltd.
All rights reserved.
RILMobile WiMAX OSS Interface Specification/User Manaul
Introduction
Purpose
This document specifies Samsung Operations Support System (OSS) Interface with
services to be provided by EMS for the operation and management of Samsung system
network.
It also explains the operation and management method of the OSS Agent that provides the
OSS interworking function.
Document Content and Organization

This manual consists of 2 Chapters and Abbreviation used.
CHAPTER 1. Introduction
Management Data
Management Interface
CHAPTER 2. Management
Configuration Management
Fault Management
Performance Management
CSL Management
ABBREVIATION
Describes the acronyms used in this manual.
SAMSUNG Electronics Co., Ltd.
Introduction
Conventions
The following types of paragraphs contain special information that must be carefully read
and thoroughly understood. Such information may or may not be enclosed in a rectangular
box, separating it from the main text, but is always preceded by an icon and/or a bold title.
NOTE
Indicates additional information as a reference.
Revision History
II
EDITION
DATE OF ISSUE
REMARKS
01
09. 2012.
First Edition
02
05.2013
Second Edition
TABLE OF CONTENTS
Introduction I
PurposeI
Document Content and Organization..................................................................................................... I
Conventions........................................................................................................................................... II
Revision History..................................................................................................................................... II
1-1
1.1
Management Data ................................................................................................................. 1-1
1.2
Interface Point ....................................................................................................................... 1-1
1.3
Interface Type ........................................................................................................................ 1-1
CHAPTER 2. Management Function

2.1
2-5
Configuration Management ................................................................................................. 2-5

2.1.1
Bulk Configuration Data Transmission ................................................................................ 2-5
2.1.2
NE Control and Query Command ...................................................................................... 2-7
2.1.3 Inventory Management ............................................................................................................ 2-7

2.2
Fault Management ............................................................................................................... 2-10

2.2.1
Real Time Alarm Transmission ........................................................................................... 2-10
2.2.2 History Alarm ............................................................................................................................. 2-1

2.2.3 Lost Alarm detection .................................................................................................................. 2-3
2.3 Performance Management ........................................................................................................ 2-7
2.3.1 Performance Data Transmission ............................................................................................... 2-7
2.3.2 Statistics File .............................................................................................................................. 2-7
2.4 CSL ( Call Summary Log) Management ................................................................................... 2-9
2.4.1 CSL File ...................................................................................................................................... 2-9
2.4.2 CSL Data .................................................................................................................................. 2-10
ABBREVIATION
A
III
TABLE OF CONTENTS
II
II
II
II
II
II
II
II
II
LIST OF FIGURES
.
LIST OF TABLES
Table 1 OSS Interface Summary ............................................................................................... 1-2
Table 2 SNMP definition ............................................................................................................ 1-2
Table 3 FTP definition ................................................................................................................ 1-3
Table 4 CLI definition ................................................................................................................. 1-4
Table 5-1 SNMP Trap OID Information .................................................................................... 2-11
Table 5-2 SNMP Trap OID Information .................................................................................... 2-12
Table 6 Alarm File Content ........................................................................................................ 2-2
Table 7 Lost Alarm Detection Case............................................................................................ 2-3
Table 8 CSL Data Item............................................................................................................. 2-10
IV
1.1 Management Data
OSS can collects and manages below data from NE(Network Element).
Configuration Data
Fault Data (Alarm, Call Summary Log Data)
Performance Data (Raw data from NE)
Inventory Data(H/W, S/W Inventory)
1.2 Interface Point

OSS interface point is located between RILs OSS system and Samsungs EMS system.
EMS manages network elements and provides management information to OSS.
OSS
OSS Interface Point
EMS
NE
1.3 Interface Type

Interface type is defined as follows.
OSS Interface Protocol

Data Type
Pattern
Protocol
Port
Connection
Direction
Configuration
data
File
FTP
21
Oriented
Bi-Direction
Once a day
CLI
TELNET
23
Oriented
Bi-Direction
Request/resp
Remark
1-1
onse
Alarm data
Notification
SNMP
Connection
less
Uni-direction
Alarm
transmission
Performance
data
File
FTP
21
Oriented
Bi-Direction
15 minute
statistics
Inventory data
File
FTP
21
Oriented
Bi-Direction
HW, SW
Table 1 OSS Interface Summary
OSS
EMS
Configu
ration
FTP / TELNET
SNMPv2
Fault
Perform
ance
FTP
Configu
ration
Fault
Perform
ance
SNMP
Item
Description
SNMP Version
SNMPv2
Agent
EMS
Manager
OSS
Trap Listening Port
162 / UDP
Remark
Table 2 SNMP definition
1-2
Mobile WiMAX OSS Interface Specification/User Manaul/Ed.00
Notification Flow
SNMP
Manager
SNMP
Agent
EMS
OSS
Alarms are
detected
Notification
FTP
Item
Remark
Description
Client
OSS
Server
EMS
Transmission Method
EMS
Get / Put
OSS
Get.
Table 3 FTP definition
EMS
OSS
Login Request
Account Request
Account Response
Password Request
Password Response
Login Response
1-3
CLI
Item
Remark
Description
Client
OSS
Server
EMS
Protocol
SSH or Telnet
Table 4 CLI definition
EMS
OSS
Login Request
Account Request
Account Response
Password Request
Password Response
Login Response
1-4
2.1 Configuration Management

2.1.1 Bulk Configuration Data Transmission
EMS works as FTP server for the bulk CM data transmission.

EMS provides bulk CM data file for all NEs which are managed.
Bulk CM data for all NEs are generated by the inside scheduler which is waked up
once a day.
Configuration Data Flow
EMS
OSS
Files are
generated
FTP Access
FTP Get
[Configuration Data File]

1
Location
/log/conf/<ENB Type>/<ENB ID>
Configuration Data
Directory of NE
Name
<ENB_ID>_<c>_sync_all.xml
Each NE CM data File
ENB Type: ENodeB type

-. ENB / MCE / SCHR
ENB ID: ENodeB Identifier
Bulk Session Id : BulkCM Session Id
2-5
[Example]
1
Name
/log/conf/ENB/101
101_1_sync_all.xml
[File Format]
XML Tag
Example
<RackConf>
<en:RackConf xmlns:en="CPS-ENB">
< AttributeId >
<en:RackId>0
</en:RackId>
[Configuration Example]
<cn:bulkCmConfigDataFile
xmlns:xt="samsungNrmBase"
xmlns:en="CPS-ENB"
xmlns:cn="ENB-CONFIG">
<cn:fileHeader
fileFormatVersion="1.0.0" senderName="CPS-ENB"
vendorName="SAMSUNG"/>
<cn:configData>
<en:samsungTelecomCommonMgmt xmlns:en="CPS-ENB"
xmlns:xt="samsungNrmBase">
<en:commonMgmtFunction>
</en:commonMgmtFunction>
<en:commonMgmtProgramLoadData>
<en:common>
<en:sCommonPlatform>
.
<en:RackConf>
<en:attributes>
<en:RackId>0</en:RackId>
<en:Status>1</en:Status>
<en:administrativeState>0</en:administrativeState>
<en:RackType>0</en:RackType>
<en:MaxShelfNumber>5</en:MaxShelfNumber>
</en:attributes>
</en:RackConf>
.
</en:sCommonPlatform>
2-6
</cn:configData>
<cn:fileFooter dateTime="2013-04-25T19:15:24Z"/>
</cn:bulkCmConfigDataFile>
2.1.2
NE Control and Query Command
OSS can connect EMS through telnet or ssh in order to control NE and to retrieve NE
status. EMS receives OSSs request and responds with its result.
[CLI Execution]
1
SYNTAX
cmd <Node Name> <COD_SYNTAX>;
Command
cmd eNB_1234 RTRV-SYS-CONF;
Result
eNB_1234 2012-08-13 MON 22:19:47

M0850 RETRIEVE SYSTEM CONFIGURATION : COMPLD
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------SYS_ID
STATUS
USER_LABEL
HEIGHT
ADMINISTRATIVE_STATE
SW_VERSION
LATITUDE
TYPE
SYS_TYPE
LONGITUDE
AC_COMM_FAIL_TX_FLAG
SMART_CELL_TYPE
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------12003
EQUIP
unlocked
SMART_INDOOR_DIST_TYPE eNB_1234
127:02:31.640
133.16m
ENB
1.2.0
N 037:30:07.359
RF_ON
SMARTCELL_TYPE_E
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------COUNT = 1
;
2.1.3 Inventory Management

[CLI Execution]
eNB CLI command (UPLD-INVT) can be used to generate eNB inventory files through
telnet or ssh. The directory of /log/system/inventory/ is recommended to use for
inventory upload files, because this directory will be cleaned periodically by cron job.
2-7
SYNTAX
cmd <Node Name> <COD_SYNTAX>;
Command
cmd 26408 UPLDINVT:FILE_NAME="/log/system/inventory/ENB/26408/IM26403_201303251500

.xml"
FILE_NAM : It carries the inventory file name including directory path to be
saved.
Result
26406 2013-03-25 MON 15:52:02
M0166 UPLOAD INVENTORY : COMPLD
RESULT : OK
;
[Inventory File Format]

eNB inventory files has XML format and below XML tags.
XML tab
Meaning
Example
configStatus
0:N_EQUIP, 1:EQUIP
unitType
Unit Type
UMP
unitId
Unit Id
vendorUnitFamilyType
Vendor Unit Family Type
UMP
vendorUnitTypeNumber
Vendor Unit Family Number
0x7022
hwVersionNumber
HW Version
1-1
vendorName
Vendor Name
SAMSUNG
serialNumber
Serial Number
S61C638241
dateOfManufacture
Date of Manufacture
2012-06-19
10
installDate
Install Data
0000-00-00
11
dateOfLastService
Date of Last Service
12
lastServiceData
Last Service Data
13
unitPosition
Unit Position
ENB[26406]/SHELF[0]/SLOT[0]
14
manufacturerData
Manufacture Data
15
CLEI
CLEI
[Inventory File Example]

<inventory>
<unit>
<configStatus>1</configStatus>
<unitType>UMP</unitType>
<unitId>0</unitId>
<vendorUnitFamilyType>UMP</vendorUnitFamilyType>
<vendorUnitTypeNumber>0x7022</vendorUnitTypeNumber>
2-8
<hwVersionNumber>1-1</hwVersionNumber>
<vendorName>SAMSUNG</vendorName>
<serialNumber>S61C638241</serialNumber>
<dateOfManufacture>2012-06-19</dateOfManufacture>
<installDate>0000-00-00</installDate>
<dateOfLastService>-</dateOfLastService>
<lastServiceData>-</lastServiceData>
<unitPosition>ENB[26406]/SHELF[0]/SLOT[0]</unitPosition>
<manufacturerData>-</manufacturerData>
<CLEI>-</CLEI>
</unit>
<unit>
<configStatus>1</configStatus>
<unitType>ECP</unitType>
<unitId>0</unitId>
<vendorUnitFamilyType>ECP</vendorUnitFamilyType>
<vendorUnitTypeNumber>0x5021</vendorUnitTypeNumber>
<hwVersionNumber>0-0</hwVersionNumber>
<vendorName>SAMSUNG</vendorName>
<serialNumber>-</serialNumber>
<dateOfManufacture>0000-00-00</dateOfManufacture>
<installDate>0000-00-00</installDate>
<dateOfLastService>-</dateOfLastService>
<lastServiceData>-</lastServiceData>
<unitPosition>ENB[26406]/SHELF[0]/SLOT[1]</unitPosition>
<manufacturerData>-</manufacturerData>
<CLEI>-</CLEI>
</unit>
</inventory>
2-9
2.2 Fault Management

2.2.1 Real Time Alarm Transmission
EMS notifies Alarms through SNMP trap when EMS detects Alarms.
Alarm Transmission Flow
SNMP
Manager
SNMP
Agent
EMS
OSS
Alarms are
detected
Notification
[Alarm Notification Information]

networkElementAlarm
Type
OID
(SAMSUNG_EMS-MIB)
sysUpTime
1.3.6.1.2.1.1.3.0
TrapOid
1.3.6.1.6.3.1.1.4.1.0
Range
Comment
SNMP Agent running time

OID
Trap Oid:
networkElementAlarm(
1.3.6.1.4.1.236.4.3.101.1.2.0.8)
emsAlarmLocation
1.3.6.1.4.1.236.4.3.101.1.2.1.2.1.2.0
UTF8String
Alarm Location
Ex) /264_RIL_IPV4_SIT/eNB_71
emsAlarmEventTime
1.3.6.1.4.1.236.4.3.101.1.2.1.2.1.3.0
DateAndTim
Alarm Time(raised/cleared)
Alarm detail
e
emsAlarmText
1.3.6.1.4.1.236.4.3.101.1.2.1.2.1.5.0
UTF8String
information(ProbableCause)
Ex) MME COMMUNICATION
FAIL
emsAlarmPerceivedSeverit
y
1.3.6.1.4.1.236.4.3.101.1.2.1.2.1.6.0
ENUM
Alarm Severity:
indeterminate(0),
critical(1),
2-10
major(2),
minor(3),
warning(4),
cleared(5)
emsAlarmEventType
1.3.6.1.4.1.236.4.3.101.1.2.1.2.1.9.0
ENUM
Alarm Type:
unknown(0),
communicationsAlarm(1),
processingErrorAlarm(2),
environmentalAlarm(3),
qualityOfServiceAlarm(4),
equipmentAlarm(5)
emsAlarmNotificationId
1.3.6.1.4.1.236.4.3.101.1.2.1.4.0
Integer32
1..21474
Trap identification
83647
emsAlarmProbableCause
1.3.6.1.4.1.236.4.3.101.1.2.1.2.1.11.0
UTF8String
emsAlarmNeType
1.3.6.1.4.1.236.4.3.101.1.2.1.2.1.12.0
DisplayString
emsAlarmClei
1.3.6.1.4.1.236.4.3.101.1.2.1.2.1.13.0
DisplayString
Alarm Probable Cause

Ex) 2199600
SIZE
(0..8)
NE or EMS type:
Ex) macro_outdoor_dist
SIZE
Reserved Field
(0..128)
Table 5-1 SNMP Trap OID Information
[Status Notification Information]

networkElementAlarm
Type
OID
(SAMSUNG_EMS-MIB)
sysUpTime
1.3.6.1.2.1.1.3.0
TrapOid
1.3.6.1.6.3.1.1.4.1.0
Range
Comment
SNMP Agent running time

OID
Trap Oid:
networkElementAlarm(
1.3.6.1.4.1.236.4.3.101.1.2.0.1
0)
emsAlarmLocation
1.3.6.1.4.1.236.4.3.101.1.2.1.2.1.2.0
UTF8String
Event Location
Ex)
/264_RIL_IPV4_SIT/eNB_71
emsAlarmEventTime
1.3.6.1.4.1.236.4.3.101.1.2.1.2.1.3.0
DateAndTim
Event Time(raised/cleared)
Event detail
e
emsAlarmText
1.3.6.1.4.1.236.4.3.101.1.2.1.2.1.5.0
UTF8String
information(ProbableCause)
Ex) NOTIFY ATTRIBUTE
CHANGE (IPAddrConf)
emsAlarmNotificationId
1.3.6.1.4.1.236.4.3.101.1.2.1.4.0
Integer32
1..21474
Trap identification
2-11
83647
emsAlarmProbableCause
1.3.6.1.4.1.236.4.3.101.1.2.1.2.1.11.0
UTF8String
emsAlarmNeType
1.3.6.1.4.1.236.4.3.101.1.2.1.2.1.12.0
DisplayString
Alarm Probable Cause

Ex) 50
SIZE
(0..8)
NE or EMS type:
Ex) macro_outdoor_dist
Table 6-2 SNMP Trap OID Information
2-12
2.2.2 History Alarm

EMS stores all autonomous messages from NEs into file every hour. OSS can use these
files for synchronization and restoration.
[Alarm File Name Information]

1
Location
/log/msg/noti
File Name
noti- <YYYYMMDD.hh>.log
Format
noti-20120918.12.log
Example
< YYYYMMDD > Collection Date(Year, Month, Day)

< hh> Collection Start Time (Hour)
[Alarm File Content]

Line
Description
Meaning
Example
[2012-09-18 12:37:10]
RTech_BTower_NEID_8 2012-09-18 TUE 12:37:10
** A2116376 CPRI FAIL ALARM
LOC = RACK[0]/SHELF[0]/SLOT[1]-ECP[0]/PORT[2]
INF = ;
1
Event Time
EMS Time
[2012-09-18 12:37:10]
[YYYY-MM-DD hh:mm:ss]
2
NE name
Event Time
RTech_BTower_NEID_8
eNB Time
2012-09-18 TUE 12:37:10
YYYY-MM-DD WWW
hh:mm:ss
3
Severity
* : Minor
** : Major
*** : Critical
# : Minor clear
## : Major clear
### : Critical clear
Event Code
A <code> : Alarm code
A2116376
S<code> : Status
Probable Cause
4
Location
CPRI FAIL ALARM

LOC
LOC = RACK[0]/SHELF[0]/SLOT[1]ECP[0]/PORT[2]
Information
INF
6~
More line can be
INF = -
2-1
appended for additional

information
End
Terminator
line
Table 7 Alarm File Content
[Alarm File Content Example]
[2012-09-18 12:37:10]
** A2116376 CPRI FAIL ALARM
INF = ;
[2012-09-18 12:37:11]
*** A2199460 SERVICE OFF ALARM
LOC =
INF = ;
[2012-09-18 12:37:31]
## A2116376 CPRI FAIL ALARM
INF = ;
[2012-09-18 12:37:31]
### A2199460 SERVICE OFF ALARM
LOC =
INF = ;
[2012-09-18 12:37:37]
S0058 NOTIFY STATE CHANGE
OBJ_CLASS
OBJ_INST
NOTI_ID
2-2
= StateChangeNotificationObjects
= cellNum : 2
= 132
EVENT_TIME
= 2012-09-18 12:37:36
SYSTEM_DN
= 100.127.132.33
STATION_ID
= 131
LOCATION
= CELL[2]
NOTI_STATE_TYPE
= OperationState
OPERATIONAL_STATE = enabled
;
2.2.3 Lost Alarm detection

SNMP traps can be lost during data transmission because they are based on UDP. Thus, a
lost alarm detection mechanism is required. Samsung EMS system uses notification Id for
OSS to detect lost alarm.
EMS sends SNMP traps with notification Id which is increased by one when
SNMP traps are sent to OSS.
Heartbeat messages are used for SNMP agent alive check and lost alarm detection.
Heartbeat traps include last notification Id of the last sent SNMP trap.
OSS can detect lost alarm using SNMP trap notification Id, heartbeat nonfiction Id
and heartbeat time interval.
Lost Alarm Detection Case

Case
1
Detection
Alarm trap notification Id
Description
When OSS receives two SNMP traps which have nonconsecutive notification Id.
Heartbeat trap notification Id
When OSS receives heartbeat traps with nonconsecutive notification Id compared to the last one
that has been received through SNMP trap
Heartbeat trap interval
When OSS doesnt receive heartbeat trap at predefined interval. There may be lost alarms or not.
Table 8 Lost Alarm Detection Case
2-3
Case 1 : detected by Alarm trap notification Id
EMS
OSS
Alarm Trap (Noti Id = n)
Heartbeat Trap (Noti Id = n)
Start time
Alarm Trap (Noti Id = n+1)

H-Period
(Heartbeat
Interval)

Heartbeat Trap (Noti Id = n+2)
Synchronizing using Alarm
history over FTP
2-4
End time
Lost alarm
Detected
Case 2 : detected by Heartbeat trap notification Id
EMS
OSS
Start time

H-Period
(Heartbeat
Interval)

Synchronizing using Alarm

history over FTP
End time
Lost alarm
Detected
2-5
Case3 : detected by Heartbeat trap interval
EMS
OSS
Heartbeat
Interval
Start time
Synchronizing Alarm history

over FTP
2-6
End time
Lost alarm
Detected
2.3 Performance Management

EMS collects all performance data and provides them to OSS.
2.3.1 Performance Data Transmission
EMS acts as FTP server for the performance management interface.

EMS provides raw statistics files for all NEs which are managed.
Statistics files are collected and generated every 15 minutes.
Time interval is xx:00, xx:15, xx:30 and xx:45. [xx means 2 digit hour (00 ~ 23)]
Performance data files have CSV format and are made by the unit of statistics
category. Commas , is used for separator and content of component does not
include ,.
Generated statistics files are bundled with one file using tar and saved at
designated location for OSS transmission. EMS locates statistics file after
collection is completely finished for OSS not to collect files being generated.
OSS collects statistics files every 15 minutes using FTP get.
2.3.2 Statistics File

The file name and location is as follows
[Statistics File Information]

1
Location
/log/pm/oss/raw
File Name
<EMS-ID> -15MIN- <YYYYMMDD>-<hhmm>.tar
Bundle file
<hhmm>-<hhmm>- <Measurement Group.csv
Each statistics file
<EMS ID> :EMS Identifier

< hhmm> Collection Start Time (Hour, Minute)
< hh/mm> Collect End Time(Hour, Minute)
< Measurement Group> Statistics Group
[Statistics File Example]

1
File Name
LSM0001-15MIN-20120911-0015.tar
2330-2345-Inter-RAT UTRAN PS Handover OUT1.2.0.csv
2-7
[Statistics File Content]

Refer to the separated document for details.
Column
Example
Statistics type
RESOURCE
NE versiopn
1.0.0
NE_ID
88
NE_NAME
ENB_88
EVENT_TIME
2011-06-29 22:45
6~11
Statistics LOC
shelfId0,slotId0,UAMA,,,,
12~
Statistics value
72.58,72.56,72.64,6532.45,90,4.82,4,25,434,9
0,13.78,13.74,13.81,1239.75,90
[Statistics File Content Example]

RESOURCE,1.0.0,88,ENB_88,2011-06-29 22:45,
shelfId0,slotId0,UAMA,,,,72.58,72.56,72.64,6532.45,90,4.82,4,25,434,90,13.78,13.74,13.
81,1239.75,90
RESOURCE,1.0.0,88,ENB_88,2011-06-29 22:45,
shelfId0,slotId1,L9CA,,,,68.4,68.4,68.4,6155.99,90,2.38,0,9,214,90,20.9,20.9,20.9,1881,9
0
2-8
2.4 CSL ( Call Summary Log) Management

When each call is exited, the Call Summary Log (CSL) data are collected and EMS stores
the raw data to the /log/csl directory for abnormal call.
The CSL data includes various information for a call. It includes a total of 10 information
items: call information, common item information, connection information, release
information, handover information, throughput information, RF information, adjacency
information, UE history information, and call debugging information.
2.4.1 CSL File

[Statistics File Information]
1
Location
/log/csl
File Name
CSL_YYYYMMDD.hhmm.csl
Every 5 minutes
CSL_20120917.1630.csl
Example

< hhmm> Collection Start Time (Hour, Minute)
[CSL File Content Example]

v2|0|255|0xFF|255|4|0xFFFFFFFF|-1|2|0xFFFFFFFF|65535|255|1|0xFF42003F|0|1|0xFF42003F|0|2303|eNB_2303|0x00000300|2012-09-17
16:31:21:980|-|40|0xFF42003F|589568|303|11|0|1|1|-1|255.255.255.255|1|255.255.255.255|0|2012-09-17
16:31:23:091|303|0xFF42003F|589568|40|1|11|0|2|1|-
1|255.255.255.255|-1|255.255.255.255|0|0xFFFFFFFF|-1|-1|1|255.255.255.255|0xFFFFFFFF|-1|-1|0xFFFF|0|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|-1|109|0|-1|-1|65535|0|0xFFFFFFFF|-1|-1|-1|-1|1|0xFFFFFFFF|-1|-1|-1|-1|-1|0xFFFFFFFF|-1|-1|-1|-1|1|1|0xFF42003F|589568|3|1|0xFFFFFFFF|-1|-1|-1|0xFFFFFFFF|-1|-1|-1|0xFFFFFFFF|-1|1|-1|0xFFFFFFFF|-1|-1|-1|1|1|0x0000D900|176|2|0|-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1|0x0042
2-9
2.4.2 CSL Data

CSL Data Items is as follows.
CSL Data Item
Call Information
Data Name
cslEvent
Description
The information for the CSL event
- 0: RRC Release
- 1: Outgoing Handover
sTmsi
The STMSI information for the call

This consists of the 1-byte mmeCode information and the
4-byte mTmsi value.
mmeUeS1APId
The S1AP ID of the call allocated by the MME
enbUeS1APId
The S1AP ID of the call allocated by the eNB
Table 9 CSL Data Item
2-10
(Continued)
CSL Data Item
Common Item
Data Name
mmeId
Information
Description
This global unique compatible MME ID consists of reserved
(1 byte) + PLMN ID (3 bytes) + MME group (2 bytes) +
MME code (1 byte).
tai
The tracking area ID which consists of PLMN ID (3 bytes) +

TAC (1 byte)
enbId
The eNBID to create the CSL consists of reserved (1 byte)

+ PLMN ID (3 bytes) + enbType (4 bytes) + eNBid (4 bytes).
enbType: 0 (Macro enb), 1 (Home enb)
enbName
The eNB that created the CSL. Max 20 bytes
callReleaseCause
The reason for call failure
Connection
attemptYear
The year/month/day on which the call is connected
Information
attemptMon
attemptMday
attemptHour
The time at which the call is connected
attemptMin
(hour/minute/second)
attemptSec
attemptMillisec
setupHour
The time at which the DRB was established
setupMin
(hour/minute/second)
setupSec
setupMillisec
freqBandIndicator
The bandclass when the target call is released

(e.g. 1.5 G or 800 M, etc.)
cgi
The cell ID when the target call is connected

(CGI: Cell Global ID)
reserved (1 byte), PLMN ID (3 bytes) + Cell ID (28 bits)
pci
The cell ID when the target call is connected

(PCI: Physical Cell ID)
mmeIpAddr
The information for the upper equipment communicated
sGateIpAddr
when the call is connected (ID and IP address, etc.)
TA
The round-trip delay time (distance) between the UE and

eNB when the call is connected
cardId
The resource information for the channel card accessed

when the target call is connected
transmitMode
The transmission antenna mode when the call is connected
callType
Identifies the type of the call, such as origination,

termination, or handover call.
2-11
(Continued)
CSL Data Item
Connection
Information
Release
Information
Data Name
Description
mmeIpAddr
The information for MMEs upper equipment communicated

when the call is connected (ID and IP address, etc.
sGateIpAddr
The information for S-GW communicated when the call is

connected (ID and IP address, etc.)
reserved
reserved
reserved1
reserved
year
The year/month/day on which the call is released
month
mday
hour
The time at which the call is released (hour/minute/second)
min
sec
millisec
Handover
Information
2-12
pci
The cell ID when the target call is released

(PCI: Physical Cell ID)
cgi
The cell ID when the target call is released

freqBandIndicator
The bandclass when the target call is released

(e.g. 1.5 G or 800 M, etc.)
cqi
The CQI reported by the UE before the call is released
TA
Round-trip delay time (distance) between the UE and eNB

when the call is released
cardId
The card information for the node accessed when the

target call is released
pA
The downlink power control parameter PA when the call is

released
transmitMode
Transmission antenna mode when the call is released
mmeIpAddr
sGateIpAddr
The information for the upper equipment communicated

when the call is connected (ID and IP address, etc.)
reserved
reserved
enbId
The eNBID of the target eNB when handover is performed.

This consists of PLMN ID (3 bytes) + enbType (4 bytes) +
eNBid (4 bytes).
enbType: 0 (Macro enb), 1 (Home enb)
enbIpAddr
The IP address of the target eNB when handover is performed
cgi
The cell ID of the target cell when handover is performed

PLMN ID (3 bytes) + Cell ID (28 bits).
pci
The physical cell ID of the target cell when handover is

performed (PCI: Physical Cell ID)
(Continued)
CSL Data Item
Data Name
Description
Throughput
rbId
RB ID
Information
epsbearerId
E-RAB ID
txDataToSG
The total bytes of data sent to the upper node during the
time between connection and release
qci
QoS class identifier
rxDataFromSG
The total bytes of data received from the upper node during
the time between connection and release
txDataToUE
The total bytes of data sent to the UE during the time

between connection and release
reTxDataToUE
The total bytes of data resent to the UE during the time

between connection and release
rxDataFromUE
The total bytes of data received from the UE during the

time between connection and release
RF Information
Adjacency
txPower
The power sent from the eNB
ueTxPower
The power sent from the UE
rsrp
Reference signal received power
rsrq
Reference signal received quality
cgi
The cell ID of the cell with the highest PSRP among the
Information
adjacent cells reported by the UE (CGI: Cell Global ID)

PLMN ID (3 bytes) + Cell ID (28 bits)
pci
The physical cell ID of the cell which has the highest RSRP
of the adjacent cells reported by the UE
UE History
rsrp
RSRP of the adjacent cell ID #1
rsrq
RSRQ of the adjacent cell ID #1
cgi
The cell global ID of the cell to which the UE belonged
Information
Call Debugging
PLMN ID (3 bytes) + Cell ID (28 bits)

cellSize
The size of the cell to which the UE belonged
stayTime
The time for which the UE belongs to the cell
stateCmd
The state which changes according to the message
Information
received externally
callState
The ECCB state which changes according to the message

received internally and externally
msgId
The ID of the message with which the call failure occurred
cslsequenceNum
The sequence number of the CSL generated
callId
Call ID
Imsi
ID used to distinguish UE in CN
(IMSI: International Mobile Subscriber Identity)
C-RNTI
ID used to distinguish UE in the cell
2-13
2-14
This page is intentionally left blank.
2-15
ABBREVIATION
A
AAA
Authentication Authorization Accounting
BS
Base Station (= eNB)
BSS
Business Support System
CSL
Call Summary Log
CSV
Comma Separated Value
DHCP
Dynamic Host Configuration Protocol
DL
Downlink
DNS
Domain Name Server
EMS
Element Management System
EPC
Evolved Packet Core
FTP
File Transfer Protocol
GUI
Graphic User Interface
IETF
Internet Engineering Task Force
IP
Internet Protocol
B
C
D
E
F
G
I
J
ABBREVIATION
JAR
Java ARchive file
LSM
LTE System Manager
LTE
Long Term Evolution
MAC
Media Access Control
MIB
Management Information Base
MS
Mobile Station (=PSS: Personal Subscriber Station)
NE
Network Element
NMS
Network Management System
OSS
Operations Support System
PDU
Protocol Data Unit
QoS
Quality of Service
SNMP
Simple Network Management Protocol
TCP
Transmission Control Protocol
UDP
User Datagram Protocol
UL
Uplink
N
O
P
Q
S
T
U
II
RIL OSS
Interface Specification/
2009 Samsung Electronics Co., Ltd.
All rights reserved.
Information in this manual is proprietary to SAMSUNG
Electronics Co., Ltd.
No information contained here may be copied, translated,
transcribed or duplicated by any form without the prior written
consent of SAMSUNG.
Information in this manual is subject to change without notice.

R4G 20 Ste Con Cos 208

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

R4G 20 Ste Con Cos 208

Enviado por

Direitos autorais:

Formatos disponíveis

EUBD-000041

OSS Interface Specification

2011 SAMSUNG Electronics Co., Ltd.

All rights reserved.

RILMobile WiMAX OSS Interface Specification/User Manaul

Document Content and Organization

SAMSUNG Electronics Co., Ltd.

SAMSUNG Electronics Co., Ltd.

RILMobile WiMAX OSS Interface Specification/User Manaul

Management Data ................................................................................................................. 1-1

Interface Point ....................................................................................................................... 1-1

Interface Type ........................................................................................................................ 1-1

CHAPTER 2. Management Function

Configuration Management ................................................................................................. 2-5

Bulk Configuration Data Transmission ................................................................................ 2-5

NE Control and Query Command ...................................................................................... 2-7

2.1.3 Inventory Management ............................................................................................................ 2-7

Fault Management ............................................................................................................... 2-10

Real Time Alarm Transmission ........................................................................................... 2-10

2.2.2 History Alarm ............................................................................................................................. 2-1

SAMSUNG Electronics Co., Ltd.

SAMSUNG Electronics Co., Ltd.

RILMobile WiMAX OSS Interface Specification/User Manaul

1.2 Interface Point

1.3 Interface Type

OSS Interface Protocol

SAMSUNG Electronics Co., Ltd.

Table 1 OSS Interface Summary

Trap Listening Port

Table 2 SNMP definition

SAMSUNG Electronics Co., Ltd.

Mobile WiMAX OSS Interface Specification/User Manaul/Ed.00

Table 3 FTP definition

SAMSUNG Electronics Co., Ltd.

Table 4 CLI definition

SAMSUNG Electronics Co., Ltd.

Mobile WiMAX OSS Interface Specification/User Manaul/Ed.00

CHAPTER 2. Management Function

2.1 Configuration Management

EMS works as FTP server for the bulk CM data transmission.

Configuration Data Flow

[Configuration Data File]

/log/conf/<ENB Type>/<ENB ID>

Each NE CM data File

ENB Type: ENodeB type

SAMSUNG Electronics Co., Ltd.

CHAPTER 3. Management Function

< AttributeId >

SAMSUNG Electronics Co., Ltd.

Mobile WiMAX OSS Interface Specification/User Manaul/Ed.00

NE Control and Query Command

cmd <Node Name> <COD_SYNTAX>;

cmd eNB_1234 RTRV-SYS-CONF;

eNB_1234 2012-08-13 MON 22:19:47

2.1.3 Inventory Management

SAMSUNG Electronics Co., Ltd.

CHAPTER 3. Management Function

cmd <Node Name> <COD_SYNTAX>;

cmd 26408 UPLDINVT:FILE_NAME="/log/system/inventory/ENB/26408/IM26403_201303251500

[Inventory File Format]

Vendor Unit Family Type

Vendor Unit Family Number

Date of Last Service