Technical Specifications (Annex 3)

1. General requirements..................................................................................................................................... 2 2. Requirements to the Project implementation.................................................................................................. 3 3. Project services requirements........................................................................................................................ 3 4. Powering of the SYS !"............................................................................................................................... 4 #. $ntegration of the SYS !"............................................................................................................................. 4 %. &ccess to the SYS !".................................................................................................................................. 4 '. &(ministration of the SYS !"....................................................................................................................... 4 ). *ac+up of the SYS !".................................................................................................................................. # ,. Requirements to the (ocumentation of the SYS !".....................................................................................# 1-. Performance of the SYS !"....................................................................................................................... # 11. Supporte( interface t.pes............................................................................................................................ # 12. Supporte( interfaces.................................................................................................................................... % 13. Supporte( protocols..................................................................................................................................... % 14. /Protocol &nal.0er1....................................................................................................................................... % 1#. /2all race1.................................................................................................................................................. ' 1%. /3etwor+ Performance "onitoring1............................................................................................................... ' 1'. /Roaming an( interconnect1......................................................................................................................... ) 1). /Reporting1................................................................................................................................................... ) 1,. /GPRS1 measurement mo(e...................................................................................................................... 12-. Geo location .............................................................................................................................................. 121. "ar+eting speciali0e( reporting ................................................................................................................. 11 22. 2ustomer 2are speciali0e( tool................................................................................................................. 12 23. &larm reporting.......................................................................................................................................... 14 24. 3etwor+ topolog. ....................................................................................................................................... 1# 2#. 4arrant. an( service terms....................................................................................................................... 1# 2%. S.stem acceptance.................................................................................................................................... 1% 2'. raining...................................................................................................................................................... 1% 2). SYS !" management............................................................................................................................... 1' 2,. 5ault tolerance........................................................................................................................................... 1' 3-. Securit....................................................................................................................................................... 1' 31. "onitoring center implementation ............................................................................................................. 1' &ppen(i6 17 /89 elecom1 2:S2 2ore networ+ topolog...................................................................................1) &ppen(i6 27 Statement of 2ompliance ;S<2=................................................................................................. 1, &ppen(i6 3 $nterface t.pes> quantities an( loa(.............................................................................................. 2&ppen(i6 4 *asic reports for 8P$s an( counters ............................................................................................ 21

1.

General requirements

Hardware and software components of the Network Quality of Service (QoS) monitoring system (hereafter SYSTE ) are intended for monitoring of signaling and data e!change as well as radio network performance in the network of "#$Telecom% &'S& and will (e accommodated in c) Yerevan* The core network elements are distri(uted (etween two different locations in c) Yerevan as shown in +ppendi! ,* The radio network elements are collocated with core network elements as well as in remote regional sites* The &ontractor must ensure compati(ility of the supplied system and its components with e!isting -./ 0. and 1. (2TE) networks and corresponding interfaces/ protocols* The &ontractor must have at least 0 years of proven e!perience in the field of monitoring systems integration into mo(ile operator networks and sufficient e!pertise in mo(ile networks audit* 3ption of porta(le pro(es for signaling traffic capturing on remote locations should (e provisioned (particularly for +(is and 4u( monitoring)* E5uipment must have ,6 inch form factor and (e installa(le in standard industrial racks* 3ffered e5uipment for traffic capture on network element interfaces and the diagram of connections must (e agreed with and approved (y the &ustomer* 7etailed cost ta(le should (e presented (y the &ontractor reflecting costs for e5uipment (servers/ pro(es/ ports/ ca(les/ etc))/ services (implementation/ training/ system e!pansion/ licenses/ post$warranty support/ etc))/ software applications/ change re5uests implantation/ etc) The SYSTE must (e dimensioned with at least 089 spare capacity (including traffic capturing/ processing/ storage/ etc))* Taking into account the rapid growth of data services usage and conse5uent need of the SYSTE e!pansion to handle increased load/ the &ontractor should present the SYSTE upgrade scenario) The cost of upgrade must (e reflected the cost ta(le* 7uring the SYSTE e!pansion and moderni:ation/ cost of the interfaces and licenses must (e fi!ed as defined in the frame contract for e5uipment supply/ in accordance with tender offer* The &ontractor can suggest pro;ect implementation scenario in phases depending on the availa(ility of hardware or software functionality ((ased on roadmap)/ or other reasona(le conditions) 4n this case the implementation period of each phase must (e presented with detailed cost information* The &ontractor can suggest additional services or system components that can enhance the SYSTE performance and overall network performance monitoring/ reporting/ analysis and trou(leshooting process) The cost for enhancement implementation/ services/ and post$warranty terms must (e specified e!plicitly* Statement of &ompliance (S3&) provided in +ppendi! - must (e provided (y the &ontractor) &ompliance of the offer to each item in S3& must (e specified (y the &ontractor in terms "Noted%/ "&ompliant%/ "<artially &ompliant%/ "Not &ompliant%) &omments must (e provided for the "<artially &ompliant% and "Not &ompliant% items) 4f the a(ove mentioned statements are not presented for the specific point/ then "Not compliant% statement will (e applied for this particular re5uirement) The S3& will (e used during the offer evaluation and later will (e attached to the contract as a separate appendi!)

 +ll proposals presented within the frame of the current process shall include as a minimum= 3fficial Technical 7atasheets and <roduct 7escription information a(out presented solutions) 4t shall contain all technical information for all the elements integrating the overall solution (Hardware platforms/ products/ network elements/ S>/ etc))* .eneric Solution +rchitecture 7iagrams/ with the ma!imum level of detail in terms of architecture and interfaces* 7etailed roadmap of the solution and planned new products* ?eferences in terms of already operating solutions within the 4ndustry* +cceptance @ Testing Standard document* Training catalog* 3ptional aintenance policy terms and conditions after the warranty period* +ny other information that may (e considered of relevance within the current ?A< process) 2. Requirements to the Project implementation Aollowing actions should (e performed (y the &ontractor (efore starting the <ro;ect implementation works= 7evelop technical re5uirements specification of the <ro;ect (ased on the technical re5uirements of the &ustomer* 7evelop and confirm with &ustomer the <ro;ect 4mplementation <lan (<4<)) Aollowing on the terms specified in the confirmed <4< is a mandatory condition) <enalties must (e foreseen in the contract for the case of <4< terms violation* <erform site survey on the sites where the e5uipment will (e installed* +ppoint a responsi(le specialist for pro;ect management/ and o(lige the manager to control the follow$up on <4< terms and works implementation process as agreed with the &ustomer* The &ontractor should provide responsi(ility matri! for the <ro;ect services/ to (e confirmed with the &ustomer* The &ontractor provides all necessary information for the e5uipment installation/ powering and integration including e5uipment components/ si:e and weight/ powering options/ power consumption/ heat dissipation/ cooling mechanism/ etc) The &ontractor ensures delivery of all re5uired installation materials for the whole scope of <ro;ect implementation works) +ll the materials should (e availa(le on sites (efore the start of installation works) 3. Project ser ices requirements The implementation works duration for the SYSTE installation/ integration and configuration according to the &ustomerBs re5uirements (including configuration of #<4s/ alarm thresholds/ etc)) should not e!ceed two months from the date of e5uipment delivery* The &ontractor should present initial engineering data no later than ,8 weeks in prior the works completion act signing date* The &ontractor provides the installation and integration works completion act within five days duration from the date of signing of the last +cceptance Test act* +ll the works should (e performed (y a company having all proper licenses of the ?epu(lic of +rmenia for corresponding works performance) The licenses should (e valid for
3

not less than 08 days after the works completion data as indicated in the <4< presented (y the &ontractor* The specialists working on e5uipment powering should have proper certificates for operations with carriers up to ,888C* The &ontractor must provide all re5uired information regarding the authori:ed su(contractor organi:ations involved in the pro;ect implementation works* The &ontractor (ears all responsi(ility for the actions of su(contractor organi:ation/ authori:ed (y the &ontractor for the <ro;ect installation and integration works* +ll the e!penses of the &ontractor in the scope of <ro;ect reali:ation works (services costs) should (e included in the tender offer and reflected in the cost ta(le* The &ontractor guarantees system integration works implementation without any impact (outage or degradation) on the &ustomerBs network* !. Po"erin# of the S$ST%& 4t is preferred to use $1DC 7& power supply for the SYSTE components* -08C +& power supply may (e used upon necessity with allowed fluctuations in the range -,ECF-0EC* The servers/ pro(es and other components of the SYSTE should have redundancy for power supply) The e5uipment must (e capa(le to function without any degradation in case of loss of any one direction of power supply) 4nstallation materials (power ca(le/ ca(le terminals/ fuses/ (reakers/ etc)) for connection to the e!isting power supply system should (e delivered (efore the start of installation works* <rovide information on e5uipment power consumption (servers/ pro(es/ T+<s/ etc))) '. (nte#ration of the S$ST%& The SYSTE should have possi(ility of integration with 3SS systems for Ericsson and Huawei e5uipment/ with support of &3?G+* Signaling information storage servers of the SYSTE should provide possi(ility of signaling information provisioning to information platforms from other vendors/ which can (e integrated in the &ustomerBs network) ). Access to the S$ST%& 2icense for not less than -8 simultaneous users of the SYSTE should (e provided* +ll applications of the SYSTE should support multiuser access with user rights differentiation* SYSTE access control mechanism should (e implemented) *. A+ministration of the S$ST%& The SYSTE should have convenient/ intuitive and easy$to$use graphical interface for ad;usting or changing all necessary parameters of the SYSTE H threshold values/ timers/ prefi!es/ etc) <ossi(ility to have full network view on one screen* <ossi(ility to configure user groups with corresponding access rules to predefined reports/ functions/ etc)
4

,. -ac.up of the S$ST%& The SYSTE should support automatic full and incremental (ackup of configuration data and operation system according to the configura(le time ta(le* The SYSTE should support automatic (ackup of all indicators and #<4s according to the configura(le time ta(le* The SYSTE (ackup copies storage time should (e not less than I8 days) /. Requirements to the +ocumentation of the S$ST%& +t the end of pro;ect reali:ation the &ontractor provides full documentation of the SYSTE in hard and electronic formats in English language) The completeness/ composition and format of the documentation should (e defined (y the &ustomer) The SYSTE documentation should include= .eneral description of the SYSTE * 7etailed description of the network part* 7etailed description of the H> e5uipment part* Technical documentation on e!ploitation and configuration* <roduct description with detailed documentation on the SYSTE structure/ its logical modules/ description of internal and e!ternal interfaces/ configuration rules and administration of the modules and interfaces* 7ocumentation on configuration and monitoring of alarm messages* 7escription of statistical information collection and analysis methods* ?eference documentation sufficient for the SYSTE e!ploitation should (e integrated into the SYSTE ) 10. Performance of the S$ST%&

inimal storage time for all unprocessed data in signaling data capturing servers should (e not less than seven days* inimal storage time for !7?s not less than 1E days* <rocessing capacity for load up to 8/1ErlJchannel and up to ,ErlJchannel in (usy hour on E, interface/ and up to ,.(ps on Ethernet interface* The SYSTE should have practical reali:ation on mo(ile operator networks with su(scri(er (ase not less than - 888 888) ?eali:ation description and references should (e provided* The SYSTE should (e scala(le the way to ena(le further increasing of interfaces for data capturing and processing* The SYSTE should have distri(uted architecture with capa(ility to install porta(le pro(es for data capturing* +ll the relevant SYSTE components should support centrali:ed time synchroni:ation for correct time stamping of !7?s* <ossi(ility to e!port !7?s to other platforms or e!ternal media* Ale!i(le configuration of e!ported !7? fields and parameters) 11. Supporte+ interface t1pes
5

 2S2JHS2 on ST $,JS7H interface* Sigtran @ Co4< Ethernet interface (,88/ ,888 (ps copper and optical)* ,8 .(ps Ethernet optical interface* Arame ?elay* <?4 (Q)60,)* 4nformation on interface connection type licensing (if applica(e) should (e provided with corresponding costs* <ossi(ility of co$location of different interfaces inside one pro(e must (e specified* The cost each interface should (e fi!ed (y mutual agreement of the <arties and should not (e increased during ,8 years* 4nterface 5uantities/ types and utili:ation are presented in the +ppendi! 0) 12. Supporte+ interfaces 4nformation on licensing for any interface (if applica(le) should (e provided with corresponding costs* 4nterfaces to (e supported should include= +/ &/ 7/ E/ A/ c/ Nc/ N(/ 4u(/ 4u&S/ .r/ .s/ .p) 4u<S (&ontrol <lane) .( Arame ?elay/ .( over 4< .n (.T<$K/ .T<$L)/ .i S,/ S,+</ SI+/ S,8/ S,,/ M-/ S.i +(is over T7 / +(is over 4</ 4u( (Huawei/ Ericsson)) Aor +(is and 4u( interfaces a solution with porta(le pro(es should (e provisioned/ which could (e fully integrated into monitoring and statistical systems to ena(le full correlation of signaling messages with the measurements data from the porta(le pro(es) 13. Supporte+ protocols 4nformation on licensing for any protocol (if applica(le) should corresponding prices* <rotocols to (e monitored should include= Sigtran (S&T</ -L+/ SL+)/ T</ S&&</ +< (ver) ,/ -/ 0)/ T&+</ 7T+</ &+< (<hase ,/ GSS +</ ?+N+</ 4SL</ ?$4SL</ S4</ G4&&/ H)-1D/ 4N+< (Ericsson &S ?+74LS/ 74+ ETE?/ HTT</ S << 0)1JE)8* G.< (.?M links)* NG+</ 2+<7) 1!. 2Protocol Anal13er4 Supported decoding protocols= NG+</ 2+<7/ GSS+</ GSS +</ &+< ph,$1/ 7T+</ +< v,/ v-/ v0/ E.+&3 (H)-1D)/ H)0-0/ G4&&/ T<-/ T<0/ ?+N+</ S&&</ S4</ S4.T?+N (S&T</ -L+/ -<+/ 0L+/ 4L+/ SL+)/ T&+</ 74+ ETE?/ G.< (.?M links)/ S++2/ +2&+</ 7NS/ 7H&</ ?+74LS/ HTT</ S << 0)1JE)8/ 4S7N$<?44SL</ 4SL<$?-888/ 4L<JGTNL</ .&</ ?-$Signalling/ ?T&</ ?TS</ ?T</ L7</ T&</ 4< (v1/ vI)/ 4& </ +?</ GSS.</ 27+</ S,+</ .T<$L v,/ .T<$& v-/ M-+</ N+S* <ossi(ility to perform search in the signaling messages (ased on any field value ("&alled <arty Num(er%/ "&alling <arty Num(er%/ "3riginal &alling Num(er%/ "?edirecting
6

(e provided with 0L+/ 4L+/ -<+/ -/ 0/ 1)/ GSS+</ ,N)/ 7NS/ 7H&</

Num(er%/ +$4 S4/ G$4 S4/ etc))/ time stamp of the signaling message/ type of signaling message/ protocol/ etc) <ossi(ility to make com(inations of different filters using Goolean functions "+N7%/ "3?%/ "N3T%* 3n$2ine and 3ff$2ine analysis modes availa(ility* Support of signaling point code la(els/ not only 3<&J7<& values* <ossi(ility to save and load custom filters* Support of messages color coding ((ased on direction/ protocol/ etc))* <ossi(ility to e!port data to TMT/ &SC/ M2S/ etc) formats* Aunctionality of message correlation for any particular call or transaction* !7? viewing capa(ility for any particular call* 7elay in trace result viewing from the moment of signaling information receipt on the pro(es should not (e more than 08 seconds* <ossi(ility to switch from <rotocol +naly:er view to &all Trace view* <ossi(ility to use the full functionality of <rotocol +naly:er (y several users simultaneously* 4nterface types are presented in +ppendi! -) 1'. 25all Trace4 <ossi(ility to perform search in the signaling messages (ased on any field value ("&alled <arty Num(er%/ "&alling <arty Num(er%/ "3riginal &alling Num(er%/ "?edirecting Num(er%/ +$4 S4/ G$4 S4/ cause/ etc))/ time stamp of the call attempt/ call answer/ disconnection/ call duration/ etc) <ossi(ility to make com(inations of different filters using Goolean functions "+N7%/ "3?%/ "N3T%* 3n$2ine and 3ff$2ine analysis modes availa(ility* Support of signaling point code la(els/ not only 3<&J7<& values* <ossi(ility to save and load custom filters* <ossi(ility to e!port data to TMT/ &SC/ M2S/ etc) formats* .raphical representation of the messages of a call of transaction (message flow chart)* .4S integration for +(is and 4u( signaling messages mapping/ possi(ility of interaction with .oogle Earth* Aunctionality of correlation of signaling data from different interfaces relating to one call or transaction* Aunctionality of cross$protocol correlation* Aunctionality of data correlation (etween 2TE/ -. and 0. networks* <ossi(ility to switch to signaling tracing mode* <ossi(ility to view messages of all logical layers a(ove physical* 4 S4$T S4 correspondence for the su(scri(ers registered in the network* a!imum num(er of simultaneous call trace tasks supported (y the system should (e specified) 1). 26et"or. Performance &onitorin#4

 3n$2ine and 3ff$2ine modes of network performance analysis (5uantity of different messages/ num(er of errors/ re;ects/ success rates/ etc))/ statistics/ monitoring of a set of signaling channels/ separate channels/ signaling point* Ale!i(le monitoring time intervals H E/ ,E/ 08/ I8 min) Ciewed information filtering possi(ility* <ossi(ility to view information in graphical as well as ta(le formats* <ossi(ility to e!port information* <ossi(ility to perform network #<4 decomposition to network elements #<4 level (drill down)* <ossi(ility to switch to call trace or protocol analy:er modes for detailed analysis) 1*. 2Roamin# an+ interconnect4 3n$2ine and 3ff$2ine modes of monitoring* Statistics for in(ound and out(ound roamers* onitoring on the level of country and operator (prefi!es/ .Ts/ etc))* Statistics of events/ messages and main #<4s* 7ata e!port functionality* &onfigura(le measurements time intervals H ,E min/ I8 min/ -1 hr* 7ata sorting and filtering functionality* .raphical reporting of statistical and 5ualitative figures* <ossi(ility to configure counters for S&&< messages for inter$operator e!change* &ounter for inter$operator SL e!change* <ossi(ility to configure anchors for S4S7N/ 4 S4/ 4< address/ S&&< .T to specific operators* <ossi(ility to perform #<4 decomposition to network elements #<4 level (drill down)* <ossi(ility to switch to call trace or protocol analy:er modes for detailed analysis* <ossi(ility to e!port data) 1,. 2Reportin#4 Aollowing reporting functionality should (e supported (y the SYSTE = Statistics (ased on any field of !7? records/ with possi(ility to apply filters and (uild graphs* !7? specification with corresponding descriptions of all fields should (e provided* ?eports (ased on= &ounters (i)e) num(er of call attempts)* 7efined ratios (i)e) +S?)* Statuses* <ossi(ility to create custom reports using counters/ #<4s and save them as templates* <ossi(ility to configure #<4s aggregation (hourly/ daily/ weekly/ monthly/ etc))* <ossi(ility to modify #<4 formulas and add new #<4s and reports* +vaila(ility of logical/ mathematical and date functions* Time interval for updating the report (,E min/ I8 min/ -1 hr/ month) must (e configura(le for each report* .L4 interface for creating custom #<4s with the use of counters and formulas*
8

 <ossi(ility to integrate reference data (i)e) user e5uipment specifications)* Thresholds definition for counters and #<4s (to define degradation/ partial or full unavaila(ility)* +vaila(ility of reports for radio conditions (coverage) and capacity analysis for -./ 0. and 1. (2TE) networks including= &ell neigh(oring relations analysis* &ell coverage and load analysis* HS7<+JHSL<+ performance and mo(ility analysis* HS<+N/ 7& (7ual &arrier)/ 4 3 analysis* 4ntegration with geo location applications (or integrated .4S) for radio measurements and #<4s visual mapping with serving cells and sites* +utomatic report updating and distri(uting (via email) functionality* +vaila(ility of standard reports for all data types availa(le to a user) The list of these reports should (e provided* <ossi(ility to use graphical as well as ta(le format reports* <ossi(ility to create different types of graphs H linear/ pie charts/ histogramsJ(ar charts in com(ination of -./ 0. and 1. (2TE) data* <ossi(ility to create comparative reports with graphs for different data types* <ossi(ility of generating the reports using= Search* Ailtering* Sorting* .rouping* Time (relative/ a(solute)* Calue filtering for including or e!cluding defined values* <arallel working (simultaneous viewing or working with several reports)* Gest and worst #<4s* ?eport planning functionality) Scheduled sending of reports to email addresses= 4nformation panel H dash(oard creation possi(ility/ which will include a set of monitored #<4s with possi(ility of further detailing* onitored #<4 aggregation possi(ility on different levels= 3n network element level ( S&) GS&/ etc)) .eographical/ can (e (ased on e!ternal 7G or file (i)e) cells cluster/ GS&J?N& clusters/ etc))* Network level H -./ 0./ 1.* Su(scri(er group (postpaid/ prepaid/ etc))* Terminal e5uipment model and type* <ossi(ility to control graph a!is parameters) Gy default M a!is should (e the time* <ossi(ility to switch to trending view (comparison with previous reporting periods results on the same graph)* 7rill down functionality to switch from #<4 reporting mode to #<4 decomposition and down to call trace mode* +ll the #<4s and counters that will not (e implemented in supplied software version and will (e availa(le in the future/ should (e provided to the &ustomer free of charge* Quality measurements should (e implemented according to the 4TL$T Q)OE- and E)1-- recommendations*
9

 ?eporting for protocols S,+</ .T<v-* &onfigured reports for the #<4s and counters re5uested the &ustomer including the ones defined in +nne! 1* ?eporting for LSS7 transactions= Statistics on LSS7 re5uests/ re5uest codes* Ale!i(le options for filtering on LSS7 code fields values* Statistics on LSS7 re5uest processing results (successful/ fail/ error/ unknown service/ etc))* LSS7 response message (ody analysis* ?eport e!porting functionality including M2S/ S&C/ <7A/ HT 2/ '<E. formats* +ccess to all performance indicators used in #<4 composition* ?eference data availa(ility for all #<4s and timers* Storage terms for #<4s= Hourly #<4s H 1E days* 7aily #<4s H I months* >eekly #<4s H , year* onthly #<4s H 0 years* +ny limiting factor in the ?eporting system should (e specified (i)e) ma! num(er of reports created/ ma! num(er of custom #<4s supported/ ma! num(er of defined thresholds/ ma! storage time/ etc))) 1/. 2GPRS4 measurement mo+e <ossi(ility to perform search in the signaling messages (ased on any field value ( S4S7N/ 4 S4/ L?2/ +<N/ LSE? 4</ disconnection cause/ etc))/ time stamp of the session activation attempt/ disconnection/ session duration/ etc) <ossi(ility to make com(inations of different filters using Goolean "+N7%/ "3?%/ "N3T% functions* <rotocol decoding functionality on interfaces= .(/ .r/ .s/ .n/ .i/ .p/ 4u<S* ?aw signaling storage time not less than O days* 3n$2ine and 3ff$2ine modes availa(ility* &ustom filters saving and loading functionality* 7ata e!port functionality (TMT/ &SC/ M2S/ HT 2/ etc))* essage correlation functionality for any given transaction or call* Lser plane monitoring and analysis on .n interface (including ?TT/ retransmission rate and other related measurements)* +nalysis possi(ilities (ased on L?2/ +<N/ user agent/ user application/ user 4< addressJrange/ service type/ etc) 20. Geo location Aunctionality to ena(le geo location of the network events using signaling information on NE interfaces* Lser position definition algorithm accuracy (in meters) must (e specified* Aull integration into monitoring and reporting system with support of drill down functionality* Easy switching to call trace/ protocol analy:er and reporting views*
10

 Aunctionality of #<4s mapping on physical map (?S&< levels/ setup inefficiency/ drops/ H3 success rate/ call density/ pilot pollution/ etc))* <ossi(ility to apply filters on mapped dataJ#<4s (su(scri(er groups/ time interval/ etc))* ?eportsJmaps e!porting functionality) 21. &ar.etin# speciali3e+ reportin# Aollowing reporting functionality should (e supported (y the SYSTE = &ustomer e5uipment (enchmarking* &ustomer applications usage statistics* &ustomer services usage statistics* 7<4 data analysis= Cisited L?2s <rotocols used +pplications used &ustomer generated traffic/ its composition (y customer e5uipment/ application/ service/ L?2/ etc)* &ustomer (ehavior in terms of device usage (analysis (ased on 4 E4/ S4S7N/ 4 S4)* +7 S features= 7evice vendor/ model Growser info 3perating system Service supporting info (e)g) video call/ S/ etc))* 7uration stats (session/ call)* 2ocation stats (cell 47 with map overlaying)* 2atency info* +verage throughput* Total (andwidth utili:ed* <eak and off$peak info (voice/ data)* +<Ns load statistics* +<N usage stats* <ossi(ility to apply filters (date/ time/ duration/ etc))* <ossi(ility to create custom reports and save them as templates* <ossi(ility to create different types of graphs H linear/ pie charts/ histogramsJ(ar charts in com(ination of -./ 0. and 1. (2TE) data* <ossi(ility to create reports with comparative graphs for different data types* <ossi(ility of report viewing with following functionality= Search Ailtering Sorting .rouping Time (relative/ a(solute) Calue filtering for including or e!cluding defined values* <arallel working (simultaneous viewing or working with several reports)* Gest and worst #<4 onitored #<4 aggregation possi(ility on different levels*
11

 <ossi(ility to switch to trending view (comparison with previous reporting periods results on the same graph)* 7rill down functionality to switch from #<4 reporting mode to #<4 decomposition view* ?eport e!porting wide functionality including M2S/ S&C/ <7A/ HT 2/ '<E. formats) 22. 5ustomer 5are speciali3e+ tool ?e5uirements for Coice services reporting= +vaila(ility of search functionality using 4 S4/ S4S7N/ 4 E4/ etc) &ustomer deviceJphone model and type identification* ?eference data availa(ility for user e5uipment (capa(ilities/ supported standards/ modes/ etc))* +ctivity start @ end time/ total duration in seconds* Traffic case name (originating or terminating)* &alled num(er network identification (home network or international destinations)* &alled num(er mo(ile operator identification ((ased on e!ternal reference data)* &harging category description (on net calls/ <STN/ etc))* 4ntegration with chargingJ(illing platform for price plan identification/ charged amount definition/ (alance (eforeJafter processed activity* 4n case of free callJS S reasonBs visi(ility (hot line/ from availa(le any free airtime or (onuses/ etc))* .S num(erBs current status identification (oth for prepaid and postpaid* Transaction cell and site identification* Network type -./ 0./ 2TE and used service type (.<?S/ E7.E/ HS7<+/ HS<+N/ >&7 +/ 2TE) identification* TransactionJactivity final status (failed/ error/ success)* 4n case of originating S S check @ note e!istence of S S4> agreement/ third part carrier ((ased on e!ternal reference data)* ?eporting for LSS7 transactions= Statistics on LSS7 re5uests/ re5uest codes* Ale!i(le options for filtering on LSS7 code fields values* Statistics on LSS7 re5uest processing results (successful/ fail/ error/ unknown service/ etc))* LSS7 response message (ody analysis* ?e5uirements for 7ata services reporting= +vaila(ility of search functionality (y 4 S4/ S4S7N/ 4 E4/ etc) &ustomer deviceJphone model and type identification* ?eference data availa(ility for user e5uipment (capa(ilities/ supported standards/ modes/ etc))* Session duration in seconds* Serving cell and site identification* Serving +<N identification* Lser (rowser identification* Cisited L?2 identification* 4< address identification (real/ dynamic/ etc))* +ctivity start time @ end time*
12

Total trafficJL2N72 #G* ean throughput on 72 (#(JS)* ean throughput on L2(#(JS)* +verage 2atency* &urrent 2atency* <ossi(ility of integration with chargingJ(illing platforms for (alance identification (eforeJafter processed activity* .S num(erBs current status identification (oth for prepaid and postpaid* .S num(er <rice <lan identification* Serving network type -./ 0./ 2TE (.<?S/ E7.E/ HS7<+/ HS<+N/ >&7 +/ 2TE)* Quality of E!perience evaluation* 7ata products specific price plan (<<) details should (e taken into account in order to have correct statistical data interpretation/ since there are some restrictions/ special re5uirements and privileges which are applied on monthly (asis (high traffic packages/ speed limitations/ etc))* 7evice anagement= 4dentification of customer device vendor/ model/ 4 E4/ used +<N/ 3S* ?eference data availa(ility for user e5uipment (capa(ilities/ supported standards/ modes/ S @ .<?S capa(le/ streaming/ video call/ <TT capa(le/ etc))* Cisited we( sites analysis* +vaila(ility of search functionality (y 4 E4/ 4 S4/ S4S7N* Total trafficJL2N72 #G* ean throughput 72(#(Js)* ean throughput L2(#(Js)* 4ntegration option with +7 S platform for provisionign of SJ.<?S configuration information via this interface* ?eports generation capa(ility (ased on devices vendors/ models/ etc)* C34< services reporting= +ll options listed a(ove for Coice services* &alled num(ersB mo(ile operator and country identification* 7ialed num(er formula checking (with prefi! OO or not)* <ossi(ility to check @ indicate e!istence of C34< agreement to the called direction (reference data importing interface should (e foreseen)* ?oaming (4n(ound/ 3ut(ound)= +vaila(ility of search functionality (y 4 S4 num(er/ S4S7N/ 4 E4* 7evice vendor and model identification* 3S identification* +ctivity start time @ end time* +ctivity duration in sec)* Host mo(ile operator indication/ availa(ility of reference data regarding thee!istence of ?oaming agreement with the particular operator* 4dentification of destination num(er network (home network or international destinations)* 7estination num(ersB mo(ile operator identification ((ased on reference data)* Session duration in seconds* Lsed +<N*
13

Lsed (rowser identification* ?e5uested L?2 identification* Total trafficJL2N72 #G ean throughput 72 (#(Js) ean throughput L2 (#(Js) <ossi(ility to import references data regarding e!isting current roaming agreements with other operators* <ossi(ility to monitor >elcome message receipt for out(ound roamers (welcome messages are sent from our network)* C4< customer care Support of C4< customer listsJgroups (ased on S4S7N/ 4 S4/ 4 E4* Special interface for constant monitoring of each C4< customerJgroup #<4s (voice and data separately) with alarming capa(ility in case of #<4 degradation* Easy navigation to other reporting tools) ?eporting Ale!i(le solution for trending reports generation (ased on different filteringJgrouping criteria H <</ e5uipment vendor and model/ visited L?2s/ service type/ cell 47/ etc* Ale!i(le report period ad;ustment capa(ility H ,E min/ I8 min/ -1 hr/ etc)* ?eport e!porting capa(ility in graphical as well as ta(le formats* &ustomi:ation of user interface including (ut not limited to the monitored #<4s list/ reports/ graphs/ lists/ user interface organi:ation should (e foreseen during the SYSTE adaptation and testing period) The term and conditions for customi:ation services should (e specified) 23. Alarm reportin# The SYSTE should support following alarm representation possi(ilities= Several classes of alarms severities (minimum 0)* &olor coding of alarm messages (ased on alarm severity* a!imum delay of alarm reporting to user interface from the moment of meeting alarm triggering condition H E seconds* The SYSTE should support following possi(ilities of alarm messages configuration and reporting= <ossi(ility to create alarm messages and triggering conditions (ased on any availa(le or custom created #<4* Lni5ue identifier e!istence for each alarm message* +larm message resetting possi(ility in case of solving alarm triggering pro(lem* +larm message (ody configuration possi(ility* Aunctionality of alarm triggering thresholds configuration (ased on values set for each indicator= Threshold for counters values* Threshold for counter or indicator ratio* Threshold for the deviation value of a counter or indicator from defined normal (ehavior pattern (i)e) dayJnight pattern)* +vaila(ility of standard predefined alarm messages and possi(ility to configure all alarm message fields* <ossi(ility to create and use different threshold values for different periods/ days (seasonal thresholds)*
14

 <ossi(ility to reflect following fields in the alarm message= +larm rising time* +larm clearing time* +larm severity* Te!t message (including the triggering condition)* +larm num(er* +larm repeat counter* &omments (to (e filled (y the userJoperator)* Handling suggestions (to (e configura(le (y the operator or administrator)* Each change in the alarm state should fi!ed and (rought to the operator attention* +larm short and detailed views availa(ility* <ossi(ility to initiate S S or email sending upon triggering event (configura(le)* +larm e!porting functionality to other (um(rella) monitoring system* 7etection and alarm generation in case of fault or loss of connection with any part (H> or S>) of the SYSTE or detection of pro(lems on traffic capturing ports* 7etection and alarm generation in case of loss of a capturing port/ protocol or particular NE messages ((ased on functional network topology)* +larm messages storage time in the SYSTE should (e not less than I months* +ny limiting factors in +larm reporting system should (e specified (i)e) ma! num(er of storedJraised alarms/ custom created alarms/ configura(le thresholds/ etc))) 2!. 6et"or. topolo#1 The SYSTE should have network topology visuali:ation tool for network elements and corresponding connections mapping) >hereas= +utomatic discovery and identification of new added elements (ased on S<& andJor 4< address* +utomatic discovery of connectionsJlinks (etween network elements* .rouping functionality of different logical elements with different S<& codes* Ale!i(le updating of NE la(els (ased on S&< andJor 4< address* Cisuali:ation of alarm status of links and NEs* Network topology and links manual editing possi(ility* ?eference data availa(ility for network elements with corresponding S<&s/ 4< addresses/ etc) 2'. 7arrant1 an+ ser ice terms >arranty for all hardware and software components of the system should (e not less than 0 years* Technical support for the SYSTE should (e availa(le during 0IE days per year/ -1 hours a day) Technical pro(lems neutrali:ation and resolution terms will depend on the pro(lem severity and priority and need to e!plicitly specified in the S2+* <ost$warranty support of the SYSTE (all components) should (e not less than O years* <ost$warranty service cost will (e defined in the frame contract and is not su(;ect to (e increased later*

15

 <ost$warranty service terms and conditions need to presented (including contract template) with detailed cost ta(le and payment terms* The &ontractor will supply the latest software release officially availa(le for deployment* 4n the warranty period the &ontractor will ensure delivery and installation of all new software releases and upgrades to the SYSTE for improvement of performance/ and ensures compati(ility of new software with e!isting hardware parts* <rovide the periodicity and appro!imate cost of software upgrades for post warranty period* 4n the warranty period the &ontractor will (ear responsi(ility for free of charge repair (or replacement) of the hardware e5uipment or its parts/ software upgrades/ discovered software and hardware defects elimination* Terms for SYSTE change re5uests implementation concerning the customi:ation or changes in the user interface and system (ehavior should (e specified* The &ontractor will provide the procedure for sending faulty e5uipment for repair and receiving the repaired ones* The &ontractor will provide the Technical +ssistance &enter (T+&) contacts and interaction procedure* The &ontractor will provide remote technical assistance through C<N connection* The &ontractor must provide the cost of post warranty support in the costs ta(le* The &ontractor shall evaluate and provide the list of spare parts with corresponding 5uantities to ensure uninterrupted operation of SYSTE * ?oadmap of the products and services should (e presented including future software and hardware releases/ implemented protocols/ applications/ tools/ etc)* 3ptionally annual network technical audit can (e offered (y the &ontractor) 4n this case network performance assessment criteria should (e specified in the offer) 4n the outcome following points must (e included= o <resentation of network performance audit report with description of performed measurements and methodology* o Evaluation of results and identification of network performance degradations/ (ottlenecks and deviations from normalJcommon (ehavior* o ?ecommendations for improvement and optimi:ation) 2). S1stem acceptance + fully integrated and configured system should (e presented for acceptance/ including #<4 reports configuration specified in +ppendi! 1* +cceptance test should (e performed (y the &ontractor representative in presence of the specialists from "#$Telecom% &'S&* +cceptance test cases and scenarios should (e presented (y the &ontractor and approved (y the &ustomer* Gased on acceptance test results the &ontractor makes a Ainal +cceptance act) 2*. Trainin# +vaila(le trainings catalog must (e provided (y the &ontractor* Training of 1 specialists for system administration level) The &ontractor will provide the list of re5uired trainings (architecture/ functional description/ development/ administration/
16

e!ploitation servicing)/ suggested locations and include it in the technical and commercial offer* Training of -8 specialists for system operator level* The &ontractor will (ear all the e!penses for the &ustomer specialists training (travel/ accommodation/ visa e!penses/ etc))) The cost of re5uired training must (e included in the offer) 2,. S$ST%& mana#ement The platform should have management system with support of following modules= &onfiguration module* Statistics collection module* <rotocol analy:er module* &all trace module* ?oaming module* System monitoring module (&<L load/ memory usage/ etc))* +larm module with mandatory support of SN <* ?emote administering) 2/. 8ault tolerance The platform should ensure the performance of mainJkey functions according to the following normative= Signaling messages capture and analysis= 66)6O9 of time +vaila(ility of the SYSTE = 66)6O9 of time 30. Securit1 Security configuration options should (e foreseen in the SYSTE to limit access (ased not only on authentication (usernameJpassword)/ (ut also (ased on 4< address) 31. &onitorin# center implementation +n optional offer for video$wall set$up can (e made for visuali:ation of monitoring systemBs output (dash(oards/ trend reports/ etc)))

17

Appen+ix 19 2:;Telecom4 5<S5 5ore net"or. topolo#1

Yerevan

1 MSC %S&1 HLR / AUC

"PRS net#!rk

Yerevan

$ HLR / AUC

, VAS etc .

MSC % S&(
Service net#!rk

MSC % S&$

IP C!re

MSC % S&'

OSS

M %M"#&1
VMS , IVR etc .

PST

M %M"#&(

PLM

M %M"#&$

M %M"#&'

RA
ATM links TDM links

RA
IP links

18

Appen+ix 29 Statement of 5ompliance (S=5)

Statement_of_Compl iance.xlsx

19

Appen+ix 3 (nterface t1pes> quantities an+ loa+

(nterface S4.T?+N ;S22P> "&P> 2&P> *SS&P> *SS"&P> R&3&P> $S?P> S$P> *$22> etc.= .n (&<NL<) .i (&<NL<) .( A? .( 4< 4u$<S (&< N L<) S, S.i +(is 4<PP 4u( 4<PP +(is T7 PP 4u( +T PP

Port t1pe ,. electrical ,8. optical ,. electrical ,8. optical ST , optical ,. electrical ,. optical ,. optical ,. electrical ,. electrical ,. optical ST , optical ST , optical

6um?er of Ports 1P 1 ,D -

&ean loa+ (total) ,88 (ps -)E .(ps -)E .(ps O8 (ps E8 (ps -)0 .(ps -88 (ps -88 (ps -88 (ps O88 (ps -88 (ps -88 (ps

Pea. loa+ (totoal) -88 (ps 0 .(ps 0 .(ps ,88 (ps 68 (ps 0 .(ps , .(ps , .(ps 188 (ps , .(ps 088 (ps 088 (ps

@ wo ports in site Yerevan 1> two ports in site Yerevan 2 @@ &Ais an( $uA information is provi(e( for (imensioning purposes for one controller with up to 12- * S ;more than 2--- RBs= an( 12- 3o(e*s configure(.

20

Appen+ix ! -asic reports for :P(s an+ counters 2G @oice &all Setup Success ?ate E7+C T&H Glocking ?ate GH E7+C 7rop &all ?ate E7+C <aging SSS SL&&ESS (Switch Su(system Success ?ate) Lnsuccessful &alls directed to international operators Lnsuccessful calls directed to local operators 7rop &all 7efects &ells ?ate 3G @oice &all Setup Success ?ate LT?+N Glok Sp ?ate LT?+N 7rop Sp ?ate LT?+N SSS SL&&ESS (Switch Su(system Success ?ate) Lnsuccessful &alls directed to international operators Lnsuccessful calls directed to local operators <aging 7rop &all 7efects &ells ?ate 2ocation Lpdate success ?ate &SS? 7efects &ells ?ate Glock T&H 7efects &ells ?ate H? 7efect &ells ?ate &SS? 7efects Traffic ?ate Glock T&H 7efects Traffic ?ate 7rop &all 7efects Traffic ?ate H? 7efects Traffic ?ate E5uipment 7owntime
21

&SS? Cideo LT?+N Glok Cideo ?ate LT?+N 7rop Cideo ?ate LT?+N Roamin# :P( ?3+ 4N. +S? A3?E4.N +S? T?+NS4T +S? ?3+ 4N. NE? A3?E4.N NE? T?+NS4T NE? E? E? L2 2ocation Lpdate @oice an+ @i+eo Traffic SL 23+7 GS& T&HQTrafficQGHQE7+C T&HQTrafficQE7+C T?+AAQS<EE&H T?+AAQC47E3 2G Aata <S +ttach Success ?ate .<?S <7< conte!t activation Success ?ate TGA Esta(lishment Success ?ate TGA 7rop ?ate +ll &ause TGA Esta(lishment Aail ?ate due to congestion Lser 7ata Throughput TGA +verage L2 Lser 7ata Throughput TGA +verage 72 7etach Success ?ate 4ntra S.SN ?+L Success ?ate
22

4nter S.SN ?+L Success ?ate -. &7? (&ells ?ate non$fulfilling the re5uirements) -. &7T? (Traffic ?ate in cells non$fulfilling the re5uirements) -. <S Setup Time .<?S Time 7elay ?ate -. -. ean Throughput L2 ean Throughput 72

3G Aata &SS? ??& (&onnection Setup Success ?ate) 7rop ??& ?ate 0. <S Glok ?ate 0. <S Success ?ate 0. <S +ttach Success ?ate 0. <7< conte!t activation Success ?ate 72 7ata ?66 throughput at GH 72 7ata HS7<+ throughput at GH 0. <S 7rop 7ata ?ate 0. <S 7etach Success ?ate 0. 4ntra S.SN ?+L (?outing +rea Lpdate) Success ?ate 0. &7? (&ells ?ate non$fulfilling the re5uirements) 0. &7T? (Traffic ?ate in cells non$fulfilling the re5uirements) 4?+T H3 <S 3LT HS7<+ &H Success ?ate 0. <S Setup Time 0. <S 0. <S 0. <S ean Throughput L2 ean Throughput 72 ean Throughput L2 HS<+
23

0. <S

ean Throughput 72 HS<+

?66 Time 7elay ?ate HS<+ Time 7elay ?ate HS<+ ?etransmission ?ate ?66 ?etransmission ?ate Aata Traffic Total .<?S 72 Traffic Total .<?S L2 Traffic Total 0. 72 Traffic Total 0. L2 Traffic ?66 7ata 72 Traffic HS<+ 7ata 72 Traffic BT% 2ontrol Plane 8P$ +ttach +ttach re5uest +ttach accept +ttach complete +ttach success rate +ttach +ccept rate +ttach completion rate C< B2 Ho re5uest H3 re5uest ack H3 complete (sur M- ue c!t release) H3 cancel preparation phase H3 failure preparation phase H3 cancel completion phase H3 &ompletion phase failure due to Treloc E!piry H3 preparation success rate H3 completion success rate H3 success rate rac+ing area up(ate T+ update re5uest T+ update re5uest with S, conte!t T+ update +ccept T+ Lpdate re;ect T+ update fail T+ update success rate T+ update preparation Success rate
24

T+ update &ompletion success rate ?ser Plane 8P$ Services Traffic load Service Type= R7NSR/ RAT<R/ RHTT<R/ R S$HTT<R/ R S$>+<R/ R3ther <SR/ R<3<0R/ RS T<R/ RStreamingR or R>+<R Total 4< volume (72 N L2) (.G) 72 Colume (.G) L2 Colume (.G) Traffic load (9) ?RD Num(er of ,st page downloads Num(er of o(;ects on ,st page +verage duration of ,st page download (sec) +verage duration of <7< activation and ,st page download (sec) ?ate of <7< activation and ,st page download over ,8s Protocol Traffic distri(ution Service Type= R7NSR/ RAT<R/ RHTT<R/ R S$HTT<R/ R S$>+<R/ R3ther <SR/ R<3<0R/ RS T<R/ RStreamingR or R>+<R <rotocol name (HTT</ HTT<S/ AT</ AT<$7+T+/ 4&$7S/ NETG43SF) Total 4< volume e!changed (L2N72) (.G) Ra+io CoS &Ais 8P$ S7&&H &ongestion 4mmediate +ssignment Efficiency T&H +ssignment Efficiency 4ncoming H3 Efficiency ?M 2ev (efore call 7rops ?M QualJT+ (efore call 7rops ?M 2ev (efore H3 ?M QualJT+ (efore H3 &all drop causes &ell metrics per ?Mlev 72 Quality per ?M 2ev L2 Quality per ?M 2ev 2ink Galance per 72 ?M 2ev 2ink Galance 7istri(ution and ?!Qual &ell metrics per T+ Timing +dvance 7istri(ution ?M 2evel per Timing +dvance ?M 2evel <& &ompensated per Timing +dvance ?M Quality per Timing +dvance 2ink Galance per Timing +dvance T&HJ&all drops per Timing +dvance S7&&H Statistics per +ccess 7elay 4mmediate +ssignment Aailures per +ccess 7elay 2ocation Lpdate Aailures per +ccess 7elay 3 S S Aailures per +ccess 7elay T S S Aailures per +ccess 7elay
25

3!$GC*<?RC<<E statistics Neigh(orhood statistics Neigh(orhood 3ptimi:ation Courl. statistics S7&&H &ongestion S7&&H traffic T&H traffic &apture &heck &apture &onsistency ??& connection setup inefficiency $uA in(icators ??& connection setup inefficiency 7rops of connections in &E22Q7&H 7rops of connections in &E22QA+&H 7rops of connections in &ompressed ode ?adio 2ink Synchroni:ation pro(lems ?adio 2ink Setup failure rates ?adio 2ink Setup failure causes ?adio 2ink +ddition failure rates ?adio 2ink +ddition failure causes Synchroni:ed ?adio 2ink ?econfiguration failures ?adio 2ink ?econfiguration failure causes +ctive set life duration and si:e &ells characteristics statistics (EcJNo at connection re5uest* EcJNo vs distance at connection re5uest* ??& connection success rate vs EcJNo* 7istance* S4? target* L2 G2E?* Transmitted code <ower/ etc)) Neigh(or set statistics (0.J-. H3 per 0. cell* 0.J-. H3 per -. cell* 0. neigh(or cells per couple* 0. candidate cells for a (est server* 0. (est servers for a candidate cell* -. Neigh(oring per 0.J-. cells couples* -. Neigh(oring for 0. cell* 0. Neigh(oring for -. cell) ?2& 7+T+ ?ound Trip Time ?N& ?2& 7+T+ latency HS<+ ?adio Gearer Setup Efficiency &ellQ A+&H to &ellQ7&H channel type switching efficiency HS<+ o(ility Efficiency HS<+ Sta(ility HS<+ o(ility <rofile

26