annex 3 technical details

Upload: faizakram

Post on 26-Feb-2018

224 views

Category:

Documents


0 download

TRANSCRIPT

  • 7/25/2019 Annex 3 Technical Details

    1/23

    Annex 3 to Request for Proposal

    May-2012

    Annex 3: Technical Specifications

    VivaCell-MTS requires network and service convergence solutions separated into 3

    different lots:

    !T ": #C$% solution!T &: '#( solution!T 3: C#S solution

    Important Notes to All Lots:

    The sa)e Applicant is a*le to *id for an+ or all of the lots,

    The Applicant should provide a separate proposal for each lot,

    The Applicant should provide State)ent of Co)pliance of each ite) of this

    Annex 3,

    Further technical details including network diagrams, software

    versions, hardware versions, current architecture can be providedupon request to the procurement and after signing of NDA Non!Disclosure Agreement"#

    1

  • 7/25/2019 Annex 3 Technical Details

    2/23

    Annex 3 to Request for Proposal

    May-2012

    L$% &: '()F *$L+%I$N

    '()F *olution

    $verview and usiness $b-ectives

    VivaCell-MTS requires a #C$% #olic+ Charging $ules %unction. solution:

    To align *usiness require)ents with #C$% functionalities, To create polic+-*ased services *ased on usage/ application/ location/

    device/ network t+pe etc,

    To integrate the #C$% with *illing and C$M s+ste)s,

    To integrate with the current '#( platfor),

    To i)ple)ent the possi*le scenarios of network and service convergence,

    To )axi)i0e the functionalit+ of 1ricsson !CS !nline Charging S+ste)s.,

    To centrali0e rating/ charging and *undle functionalities on the 1ricsson

    !CS,

    To pave the wa+ for possi*ilities of i)ple)enting 1&1 polic+ )anage)ent,

    To )igrate the current su*scri*ers and policies to the new solution,

    .#/odules *pecification

    .# 'rovisioning of polic0!based services

    The proposed solution should support provisioning of polic+-*ased services *ased

    on the co)*ination of various para)eters/ including:

    Ti)e/

    'ata Volu)e/

    Su*scri*er2s location/

    'evice T+pe/

    etwork $esource Availa*ilit+/

    Su*scri*er $oa)ing/

    etwork T+pe/

    #rotocol4Application used *+ the su*scri*er/

    Content T+pe/

    Service/

    5e* Address 6$-*ased./

    2

  • 7/25/2019 Annex 3 Technical Details

    3/23

    Annex 3 to Request for Proposal

    May-2012

    ocation-*ased/

    Su*scri*er2s #rofile/

    7oS,

    Tariff plan

    A)ount of used traffic per hour/ da+/ )onth.

    Ti)e of service usage da+4night/ period of ti)e.

    1quip)ent t+pe

    AN1 combination of the parameters enumerated above#

    #olicies should *e applied *oth individuall+ for each su*scri*er and for the

    group of su*scri*ers,

    .#.# Networks

    The proposed solution will *e *earer network agnostic/ *eing a*le to full+ interface

    with an+ t+pe of carrier network/ including *ut not li)ited to:

    T1/

    8SM/

    6MTS/

    5i%i

    'S

    %TTx

    .#2# Deep 'acket Inspection

    The proposed solution should *e co)pati*le with an+ of the *elow '#(:

    Sandvine #TS switches

    1ricsson SAS

    Cisco SC1

    .#3# /igration

    The proposed solution should include policies/ rules/ price plan )igration fro) the

    current s+ste),

    .#4# *tatistics

    The proposed solution should support collection of statistics *ased on the *elow

    attri*utes:

    etwork protocols

    A)ount of the used traffic per hour/ da+/ and )onth. according to the t+pe

    of network protocols,

    3

  • 7/25/2019 Annex 3 Technical Details

    4/23

    Annex 3 to Request for Proposal

    May-2012

    Tariff plans and services

    Su*scri*er2s location

    .#5# (ustomer self!care

    The proposed solution should support self-care A#(s which will *e integrated with

    the current self-care channels, The A#( should support we* service such as

    S!A#,

    Self-registration

    Account Maintenance

    Change account details/ such as address and other contact infor)ation

    7uota usage

    6sage 9istor+

    #arental Control configuration

    A*ilit+ to purchase other services

    !ther invoice details,

    6ser dash*oards

    Su*scri*er notification over SMS and4or 5e* #age redirect

    Solution should support the notification of the su*scri*er on the cost of

    access to services in case of excess of various threshold values ; asic training should *e provided *+ the Applicant to ensure proper trialing of

    the solution,

    4

  • 7/25/2019 Annex 3 Technical Details

    5/23

    Annex 3 to Request for Proposal

    May-2012

    The trial scope is non-negotia*le

    The trial will de)onstrate the technical functionalities of the solution

    The trial solution upon can have live traffic for load testing/ onl+ after showing

    satisfactor+ results and VivaCell-MTS2s approval

    The current '#( s+ste) used is Sandvine #TS switches, The Applicant can

    propose a different '#( s+ste) as long as it is %!C *asis,

    .#9# +se!cases for the trial

    The proposed solution should support the *elow use-cases:

    +sage!based:6nli)ited " )onth with fair usage polic+ set at " 8>, %irst "

    8> *est effort and a*ove " 8> to downgrade to &?@ k*ps +sage!based:";; M> >undle additional " M> to *e charged at x AM' 4 M>,

    +sage!based:Convergent *undle of voice and data *ased on units, >undle

    is x units, !nnet voice calls rated at " unit per second and data calls rated "unit per M>,

    Location!based:6nli)ited *est effort usage in all cells/ except few defined

    cells, This will *e the cells on the roof top of VivaCell-MTS 97,

    Application!based: 1)ail ";; M> *undle +ahoo/ g)ail/ )sn., !ther

    protocols are charged per M>,

    Famil0 plans: !ne parent account to have a quota ";; M> *undle/ the

    availa*le quota can *e transferred to the child accounts having "; M> *undle/upon receiving a co))and fro) the self-care,

    +)L!based:All traffic to vivacell,a) to *e charged free, !ther 6$s will *e

    charged at x AM' per M>,

    +sage!based with peakoff!peak hours: 6nli)ited usage during the da+

    :;; AM to @:;; #M/ li)ited usage during the night @:;; #M to :;; AM,

    Device!based charging: i#ad traffic to *e charged x AM' per M>/ while

    other devices + AM' per M>, There will *e a single (M1( defined as i#addevice,

    earer network:8 traffic to *e charged at x AM' per M>/ while &8438 to

    *e charged at + AM' per M>, (dentification of *earer network is *ased on88S and 85 (#s which is present as $A'(6S AS-(dentifier attri*ute.

    %urbo utton:ow *andwidth su*scri*ers who occasionall+ need high-speed

    access eg, for ga)ing/ strea)ing/ downloading/ etc,. upon fee pa+)ent will*e granted a pre)iu) high *andwidth for a specified period of ti)e or trafficvolu)e,

    (ontent Filtering: The platfor) )ust support the a*ilit+ to appl+ usage

    li)itations *ased on 6$ address4application t+pe4content t+pe and4or ti)econstrains,

    )oaming (ost (ontrol: The platfor) )ust ena*le the operator to set default

    or personali0ed )axi)u) charging li)its and notif+ su*scri*ers when

    approaching 4 reaching quota threshold, Must *e B>ill Shock proofD,

    5

  • 7/25/2019 Annex 3 Technical Details

    6/23

    Annex 3 to Request for Proposal

    May-2012

    .#&;# (ompliance

    The proposed solution should support the *elow standards:

    38## $= co)pati*le Support for 8x/ 8+/ Sp/ $x/ S=

    Act as a 8+ 'CCA prox+

    Should support ";8 optical interfaces scala*le up to ;8 traffic

    Should support ";;/;;; si)ultaneous sessions scala*le up to ?;;/;;;

    sessions

    Must support (#V and (#v@

    Carrier-grade

    .#& Alerts

    The proposed solution should provide an ad)inistration and )onitoring s+ste) *+

    generating s+ste) alar)s and alerts, This can *e using technologies such as SM#

    agents and SM# traps,

    .#&.# (D) /anagement

    The proposed solution should generate C'$ files which should include: MS(S'/(MS(/ source (#/ 'estination (#/ A#/ duration/ charging infor)ation and other data/

    received as a result of the anal+sis and an esti)ation of the traffic,

    .#&2# Integration

    The proposed solution should support the *elow integrations:

    Access servers:

    o 1ricsson 88S

    o #85 #acket 8atewa+.

    $A'(6S servers

    '#( 'eep #acket (nspection.

    1ricsson !CS !nline Charging S+ste).

    >illing and C$M s+ste)s

    MMSC and 5A# gatewa+

    MS >i0Talk Server working as 1S> 1nterprise Service >us.

    A'MS via online or offline.

    Congestion Manage)ent S+ste)

    The solution should support we* services A#( and4or S'E for future addition of new

    )odule and4or extending the current functionalit+

    6

  • 7/25/2019 Annex 3 Technical Details

    7/23

    Annex 3 to Request for Proposal

    May-2012

    The proposed solution should provide the necessar+ tools to develop connectors to

    integrate with undefined s+ste)s

    .#&3# )eporting

    The proposed solution should provide a full-functional report-design environ)ent

    ena*ling the eas+ creation of ta*ular and graphical reports fed *+ the operational

    data of the solution,

    1xport to external files such as text/ CSV/ 1xcel/ FM and #'%

    $eports generation *ased on )ultiple criteria

    A*ilit+ to design and generate reports

    A*ilit+ to schedule of sending report to )ultiple recipients *+ e)ail

    $epositor+ of readil+ availa*le/ off-the-shelf report te)plates designed

    in advance to cover the )ost frequentl+ addressed reporting needs,

    .#&4# *ecurit0 hierarch0

    The proposed solution should support granular and advanced securit+ access

    )odel, (n other words/ all unauthori0ed )enu ite)/ reports/ dash*oard ite)s/ views/

    etc will *e hidden fro) the user,

    - A*ilit+ to define ver+ granular privileges- Support of *uilt-in user groups or roles *ased on *est practices- A*ilit+ for users to change their passwords and profile- All user profiles and passwords are encr+pted in the data*ase- A*ilit+ to generate audit trail logs of all actions perfor)ed including the

    ad)inistrator role

    .#&5# %echnical )equirements

    5e*-*ased using SS technologies

    %ast/ eas+ and secure access to the application

    #refera*le to have )ini)al ad)inistration !perating s+ste): inux or Solaris preferred

    The s+ste) should have open architecture/ use open interfaces of the

    s+ste)2s functional *locks interaction,

    .#&6#

  • 7/25/2019 Annex 3 Technical Details

    8/23

    Annex 3 to Request for Proposal

    May-2012

    The Applicant should provide evidence that the proposed hardware will guarantee

    perfor)ance, (n case if the hardware provided did not )eet the perfor)ance criteria/

    then the Applicant will take full responsi*ilit+ *+ replacing the hardware with no

    additional cost,

    The hardware solution should co)pl+ with the "G" or G" protection

    principles

    The hardware solution should incorporate a load *alancing and failover

    )echanis)s

    .#&8# %raining

    The solution should include training to the users and ad)inistrators, The trainings

    should *e conducted onsite,

    The training should include *asic and advanced trainings, (n addition/ training is

    required for develop)ent of new data sources using S'Es,

    .#&9# /anuals and documentation

    The solution should include user guides/ operation )anuals and deplo+)ent guides

    in electronic for)at, #rinted )anuals are optional,

    .#.;# 'ro-ect /anagement

    The solution should include proHect )anage)ent and professional services to

    i)ple)ent the proHect,

    The Applicant should provide a proHect schedule plan for the proHect i)ple)entation,

    .#. %echnical support and maintenance

    The proposed solution should include the staffing details for nor)al operations of the

    s+ste), (n addition to define roles *ased on *est practices and standards,

    The solution should include technical support and )aintenance with &xI hot line

    and online ticketing s+ste), The first 3 +ears technical support will need to *e part of

    the solution or the co))ercial proposal,

    L$% .: D'I *$L+%I$N

    8

  • 7/25/2019 Annex 3 Technical Details

    9/23

    Annex 3 to Request for Proposal

    May-2012

    2. D'I Data 'ackage Inspection" *olution

    .#&$verview and usiness $b-ectives

    VivaCell-MTS requests a co)plete traffic )anage)ent solution that includes the

    develop)ent of network design/ equip)ent suppl+/ installation/ s+ste) integration,

    The functional JTraffic Manage)entJ in ter)s of equip)ent and use of traffic

    anal+sis4 definition of policies should include:

    A*ilit+ to anal+0e (nternet traffic level protocols4 applications.

    The possi*ilit+ of charging user data *ased on the traffic anal+sis to

    support prepaid4 postpaid service )odels

    The possi*ilit+ of i)posing restrictions on the use of individual su*scri*ers

    of network protocols

    The possi*ilit+ of li)iting the speed of (nternet access

    A*ilit+ to prioriti0e network protocols

    A*ilit+ to restrict su*scri*er access to the 51>-resources *locking

    access/ partial *locking *+ ti)e of da+/ volu)e of traffic generated fro)this resource.

    To align *usiness require)ents with the '#( functionalities

    To create polic+-*ased services *ased on usage/ application/ location/

    device/ network t+pe etc

    To create polic+ enforce)ent policies

    To create advanced anal+tical reports of network/ su*scri*er/ protocol

    usage

    The solution should work with an+ vendorKs equip)ent/ 88S/ the standards of

    38## $ and at the stage of further develop)ent of the s+ste) to )aintain the

    functionalit+ of #' - 8atewa+ to the ter)s of the S+ste) Architecture 1volution

    SA1.

    .#./odules *pecification

    .#.#& 'rovisioning of polic0!based services

    The proposed solution should support provisioning of polic+-*ased services *ased

    on the co)*ination of various para)eters/ including:

    Ti)e/

    'ata Volu)e/ Su*scri*er2s location/

    9

  • 7/25/2019 Annex 3 Technical Details

    10/23

    Annex 3 to Request for Proposal

    May-2012

    'evice T+pe/

    etwork $esource Availa*ilit+/

    Su*scri*er $oa)ing/

    etwork T+pe/

    #rotocol4Application used *+ the su*scri*er/

    Content T+pe/

    Service/

    5e* Address 6$-*ased./

    ocation-*ased/

    1quip)ent t+pe

    AN1 combination of the parameters enumerated above#

    #olicies should *e applied *oth individuall+ for each su*scri*er and for the

    group of su*scri*ers,

    The solution should support packet inspection and anal+sis 5A#",x4&,;, The

    following para)eters should *e deter)ined *+ the decision: MS(S'/ 6$/

    6plink Traffic/ 'ownlink Traffic/ Status Code/ and Content-T+pe,

    The solution )ust support the inspection and anal+sis of the 9TT# protocol

    packet 9TT#",; and 9TT#",", The following para)eters should *e

    deter)ined *+ the decision: MS(S'/ 6$/ 6plink Traffic/ 'ownlink Traffic/

    Status Code/ and Content-T+pe,

    The solution )ust inspect and anal+0e signaling and )edia protocols such as

    $TS# and $T# 4 $TC# *ased on $%C &3&@ $TS#., The following

    para)eters should *e deter)ined *+ the decision: MS(S'/ 6$/ 6plink

    traffic/ 'ownlink traffic/ Start ti)e/ Stop ti)e/ Valid duration,

    The solution )ust support the transfer of MMS over 5A#",F 5S#. and

    5A#&,; 9TT#","., The following !ptions have deter)ined 'ecision:

    $ecipient t+pe 4 ('/ Content - T+pe 4 M(M1 t+pe/ 1rror Code/ Attach)ent T+pe,

    The solution )ust inspect and anal+0e protocols (MA#/ SMT#4#!#3, The

    following para)eters should *e deter)ined *+ the decision: MS(S'/ 6$/

    6plink traffic/ 'ownlink traffic/ and 1rror code,

    The solution )ust inspect and anal+0e # and V!(# protocols/ *ased onsignature services,

    The solution )ust support the use of )asks and regular expressions in all the

    6$ fields/ such as do)ain/ path and para)eters,

    The solution )ust provide the function of *andwidth )anage)ent in downlink/

    and in the uplink,

    The solution )ust provide the following functions for )anaging *andwidth:

    8x interface can *e used to quer+ the #C$% a*out the redefinition of the

    *andwidth,

    10

  • 7/25/2019 Annex 3 Technical Details

    11/23

    Annex 3 to Request for Proposal

    May-2012

    The solution should provide a*ilit+ to ena*le 4 disa*le the su))ation of the

    unspent a)ount of traffic within one *illing c+cle to the volu)e of traffic in the

    new c+cle,

    Access rules should *e *ased on d+na)ic and static infor)ation a*out the

    user/ the destination 6$/ the service record/ ti)e, Access rules should have

    priorit+/ which can *e taken into account when appl+ing these rules,

    The solution )ust support the *illing in real ti)e/ using the protocol

    '(AM1T1$,

    .#.#. Networks

    The proposed solution will *e *earer network agnostic/ *eing a*le to full+ interface

    with an+ t+pe of carrier network/ including *ut not li)ited to:

    T1/

    8SM/

    6MTS/

    5i%i

    'S

    %TTx

    $egularl+ update the list of protocols protocol signatures. that are su*Hect to

    restrictions/ as well as adding operational )odifications of existing protocols

    A*ilit+ to per)it su*scri*ers to use separate network protocols #/ Vo(#/ (M/%T#/ etc,. on a co))ercial *asis/ i)ple)ented as a plug-periodic service

    A*ilit+ to connect the su*scri*er services/ including the use of a specific

    protocol or include packaged offers for exa)ple: Vo(# onl+/ Vo(# G #.,

    i)iting the *andwidth )ust *e applied individuall+ for each su*scri*er/ as well

    as for the group

    (nfor)ing +ou of the introduction 4 re)oval of li)iting the *andwidth in the

    provision of su*scri*er service data packet

    A*ilit+ to disa*le 4 ena*le the service to infor) +ou of the introduction of li)iting

    the data rate

    A*ilit+ to cancel this li)itation rate for a certain period of ti)e or for a certaina)ount of traffic *ased on the connected services,

    $educing the *andwidth for certain t+pes of traffic e,g, #. when the

    threshold is configura*le *andwidth of the total traffic,

    .#.#2 *tatistics

    The proposed solution should support collection of statistics *ased on the *elow

    attri*utes:

    etwork protocols

    11

  • 7/25/2019 Annex 3 Technical Details

    12/23

    Annex 3 to Request for Proposal

    May-2012

    A)ount of the used traffic per hour/ da+/ and )onth. according to the t+pe

    of network protocols,

    Tariff plans and services

    Su*scri*er2s location

    .#.#3 7+I interfaces and dashboards

    The proposed solution should support user-friendl+ we* 86( interfaces and user

    dash*oards,

    6ser-friendl+ 86( ena*ling to define ad-hoc policies without the intervention of

    the vendor

    5e* 86( which allows the ad)inistrator to access and )anage all policies

    and statistical reporting

    .#.#4 /igration

    The proposed solution should include policies and rules )igration fro) the current

    s+ste),

    .#.#5 (ompliance

    The proposed solution should support the *elow standards:

    38## $= co)pati*le Support for 8x/ 8+

    To support '#( of MMS *ased on destination nu)*er/ sender/ content t+pe/

    content si0e/ nu)*er of recipients

    To support '#( of 5A# v" and 5A#v& *ased on destination 6$ and user-

    agent t+pe,

    Should support ";8 optical interfaces scala*le up to ;8 traffic

    Should support ";;/;;; si)ultaneous sessions scala*le up to ?;;/;;;

    sessions

    Must support (#V and (#v@

    Carrier-grade solution

    38## TS &3,;": J8#$S 1nhance)ents for 1-6T$A AccessJ,

    38## TS &3,&3: J38## S+ste) to 5ireless ocal Area etwork 5A.

    (nterworkingL S+ste) 'escriptionJ,

    (1T% $%C 33/ JMo*ilit+ Support for (#vJ,

    38## TS &3,;;&: Technical Specification 8roup Services and S+ste)

    AspectsL etwork Architecture,

    38## TS &3,;;3: Ju)*ering/ addressing and identificationJ,

    38## TS &3,&;3: J#olic+ and Charging Control ArchitectureJ,

    12

  • 7/25/2019 Annex 3 Technical Details

    13/23

    Annex 3 to Request for Proposal

    May-2012

    38## TS &&,&I: JService require)ents for evolution of the s+ste)

    architectureJ,

    38## TS &3,;@;: J8#$S Tunneling #rotocol 8T#. across the 8n and 8p

    interfaceJ,

    38## TS &=,&"&: J#olic+ and charging control over 8x reference pointJ,

    (1T% $%C &I=: JMo*ile (# etwork Access (dentifier 1xtension for (#vJ,

    38## TS 33,;&: J38## S+ste) Architecture 1volution: Securit+ aspects

    of non-38## accessesJ,

    38## TS March &, April &: JArchitecture enhance)ents for non-38##

    accessesJ,

    $%C 3? - 'ia)eter >ase #rotocolL

    $%C 3?= - 'ia)eter Co))and Codes for Third 8eneration #artnership

    #roHect 38##. $eleaseL

    $%C ;; - 'ia)eter Mo*ile (#v ApplicationL $%C ;;? - 'ia)eter etwork Access Server ApplicationL

    $%C ;;@ - 'ia)eter Credit-Control ApplicationL

    $%C ;I& - 'ia)eter 1xtensi*le Authentication #rotocol 1A#. Application

    optional.L

    $%C I; - 'ia)eter Session (nitiation #rotocol S(#. Application optional.L

    $%C ?&& - 'ia)eter #olic+ #rocessing ApplicationL

    $%C ?3" - 'ia)eter (T6-T $w #olic+ 1nforce)ent (nterface ApplicationL

    $%C ??"@ - 'ia)eter Co))and Code $egistration for the Third 8eneration

    #artnership #roHect 38##. 1volved #acket S+ste) 1#S.L

    38## $I TS &=,&3;: 'ia)eter applicationsL 38## specific codes and

    identifiers,

    $%C "=? 9TT# ",;.

    $%C &@"@/ &"I 9TT# ",".

    .#.#6 Alerts

    The proposed solution should provide an ad)inistration and )onitoring s+ste) *+

    generating s+ste) alar)s and alerts, This can *e using technologies such as SM#agents and SM# traps,

    .#.#8 Integration

    The proposed solution should support the *elow integrations:

    Access servers:

    o 1ricsson 88S

    o

    #85 #acket 8atewa+. $A'(6S servers

    13

  • 7/25/2019 Annex 3 Technical Details

    14/23

    Annex 3 to Request for Proposal

    May-2012

    The solution should support we* services A#( and4or S'E for future addition of new

    )odule and4or extending the current functionalit+

    The proposed solution should provide the necessar+ tools to develop connectors to

    integrate with undefined s+ste)s

    .#.#9 )eporting

    The proposed solution should provide a full-functional report-design environ)ent

    ena*ling the eas+ creation of ta*ular and graphical reports fed *+ the operational

    data of the solution,

    1xport to external files such as text/ CSV/ 1xcel/ FM and #'%

    $eports generation *ased on )ultiple criteria

    A*ilit+ to design and generate reports A*ilit+ to schedule of sending report to )ultiple recipients *+ e)ail

    $epositor+ of readil+ availa*le/ off-the-shelf report te)plates designed

    in advance to cover the )ost frequentl+ addressed reporting needs,

    .#.#&; *ecurit0 hierarch0

    The proposed solution should support granular and advanced securit+ access

    )odel, (n other words/ all unauthori0ed )enu ite)/ reports/ dash*oard ite)s/ views/

    etc will *e hidden fro) the user,

    - A*ilit+ to define ver+ granular privileges- Support of *uilt-in user groups or roles *ased on *est practices- A*ilit+ for users to change their passwords and profile- All user profiles and passwords are encr+pted in the data*ase- A*ilit+ to generate audit trail logs of all actions perfor)ed including the

    ad)inistrator role

    .#.#&& %echnical )equirements

    5e*-*ased using SS technologies

    %ast/ eas+ and secure access to the application

    #refera*le to have )ini)al ad)inistration

    !perating s+ste): inux or Solaris preferred

    The s+ste) should have open architecture/ use open interfaces of the

    s+ste)2s functional *locks interaction,

    All hardware )ust confor) to the principles or " G" G"/ ie stop the

    operation of a network ele)ent should not *e a reason for stopping the

    service,

    The solution )ust confor) to the principle of ==,===< five =-s.

    availa*le,

    14

  • 7/25/2019 Annex 3 Technical Details

    15/23

    Annex 3 to Request for Proposal

    May-2012

    All i)portant data such as s+ste) configuration files and personal user

    settings/ data*ase/ etc,. )ust *e *acked up on an external device at

    least once a da+,

    After a forced 4 restart and uncontrolled s+ste)s/ network ele)ents s

    restoration of full functioning of the co)plex should occur auto)aticall+

    The data*ases used in the s+ste) should *e *ased on the clustering

    solution to avoid a single point of failure,

    The whole s+ste) should also not *e a single point of failure/ and its

    failure should not affect the provision of services to su*scri*ers that are

    active at the ti)e of failure,

    %ailure of an+ co)ponent of the solutions )ust *e JtransparentJ to the

    su*scri*er/ i,e, not require further action,

    (n the event of failure of an+ s+ste) co)ponents should *e included

    )ode Jworkaround,J The s+ste) should support )echanis)s for re)ote disaster recover+,

    The s+ste) should have as architecture/ providing a growing nu)*er of

    su*scri*ers/ traffic volu)e/ etc,

    The solution )ust provide for the existence of )echanis)s for load

    *alancing and failover occurring in the case of s+ste) overload,

    .#.#&.

  • 7/25/2019 Annex 3 Technical Details

    16/23

    Annex 3 to Request for Proposal

    May-2012

    The training should include *asic and advanced trainings, (n addition/ training is

    required for develop)ent of new data sources using S'Es,

    .#.#&3 /anuals and documentation

    The solution should include user guides/ operation )anuals and deplo+)ent guides

    in electronic for)at, #rinted )anuals are optional,

    .#.#&4 'ro-ect /anagement

    The solution should include proHect )anage)ent and professional services to

    i)ple)ent the proHect,

    The Applicant should provide a proHect schedule plan for the proHect i)ple)entation,

    .#.#&5 %echnical support and maintenance

    The proposed solution should include the staffing details for nor)al operations of the

    s+ste), (n addition to define roles *ased on *est practices and standards,

    The solution should include technical support and )aintenance with &xI hot lineand online ticketing s+ste), The first 3 +ear technical support will need to *e part of

    the solution or the co))ercial proposal,

    16

  • 7/25/2019 Annex 3 Technical Details

    17/23

    Annex 3 to Request for Proposal

    May-2012

    L$% 2: (=N%)ALI>=D')$?I*I$NIN7*$L+%I$N

    3. (entrali@ed 'rovisioning *olution

    2#&$verview and usiness $b-ectives

    VivaCell-MTS requires a C#S Centrali0ed #rovisioning Solution.:

    To align *usiness require)ents with the C#S functionalities

    To create consolidate and centrali0e all provisioning s+ste)s

    To create provisioning rules *ased on *usiness processes

    To converge network co))ends

    To create advanced anal+tical reports of network/ su*scri*er/ protocol

    usage

    2#./odules *pecification

    2#.#& 'rovisioning services

    The proposed solution should support Service !riented Architecture *ased on

    1nterprise Service >us 1S>. construct, The platfor) )ust support convergent

    service provisioning capa*ilit+, (t should *e capa*le to provision services across at

    least the following t+pe of networks:

    8SM/

    x'S/

    5iMAF/ 8

    (MS/

    'igital 1xchanges

    (# TV

    The platfor) )ust support two )aHor environ)ents, !ne including the runti)e

    environ)ent/ while the second one/ shall include a full+ interopera*le and

    platfor) in-depended 'esign and 'evelop)ent environ)ent ena*ling the

    develop)ent of new *usiness services and network adapters,

    17

  • 7/25/2019 Annex 3 Technical Details

    18/23

    Annex 3 to Request for Proposal

    May-2012

    ew >usiness Services should *eing )odeled and designed using a standard

    >#1 Service workflow graphical tool, This tool )ust ena*le the fast

    introduction and )aintenance of *usiness services, 1ver+ function of a

    *usiness service should *e )odeled on a workflow *asis that )aps the steps

    required to provision these services as workflow nodes,

    The platfor) shall support the deco)position of service orders to

    transactional ato)ic actions or sets of ato)ic actions 1 co))ands. that

    co))unicate with external network ele)ents4(T s+ste)s, The+ should *e

    designed with a network adapter designer tool that )ust support a wide range

    of co))unication protocols and interfaces with network ele)ents,

    The platfor) shall support )odular architecture, >usiness services should *e

    the higher level la+erL network adapter shall *e used as parts of the services/undertaking the co))unication with networks ele)ents and external

    data*ases4network inventor+ s+ste)s respectivel+,

    The platfor) shall support invocations such as selection/ addition/ deletion/

    queries. either to the platfor)2s e)*edded data*ase or to external data*ases/

    data warehouse and inventor+ s+ste) in order to extract infor)ation for

    capturing/ validation and enrich)ent of co)plex provisioning orders

    1ach service workflow node shall *e a*le to )odel single or *undle services

    using graphical environ)ent,

    The platfor) shall supports an+ possi*le co)*ination of provisioning

    co))ands/ on an+ nu)*er of etwork 1le)ents,

    An+ ar*itrar+ logic shall *e a*le to *e )odeled and orchestrated inside a

    service workflow using a graphical environ)ent, >oth s+nchronous and

    as+nchronous co))and execution should *e supported through the use of

    the appropriate service workflow,

    etwork adapter designer should support a user-friendl+ 86( supporting the

    creation of an adapter according to a generic adapter )odel, This generic

    should *e custo)i0a*le *+ te)plate-*ased code generators that are specific

    to particular underl+ing technologies, $oll*ack support functionalit+/ at adapter

    lever/ shall *e supported,

    The s+ste) shall support hot-deplo+)ent upon existing *usiness service and

    network adapter )odification or re)oval,

    An+ change in deplo+ed services or network adapter shall not affect platfor)operation,

    18

  • 7/25/2019 Annex 3 Technical Details

    19/23

    Annex 3 to Request for Proposal

    May-2012

    2#.#. Alerts

    The proposed solution should provide an ad)inistration and )onitoring s+ste) *+generating s+ste) alar)s and alerts, This can *e using technologies such as SM#

    agents and SM# traps,

    2#.#2 Integration

    The proposed solution should support the *elow integrations:

    %or co))unication with !SS4>SS s+ste)s and 1s/ the platfor) shall support the

    following technologies:

    o http

    o tcp

    o %T#4%ile >ased

    o sftp

    o %TAM

    o &11 and4or 11

    o T"

    o ssh

    o rsh

    o telneto MM

    o ava $M(

    o Cor*a TM%-"

    o Socket

    o '>C

    o 1A( Message 7ueues

    o FM over MS

    o !SS4

    o 5e* Service

    o S!A#o 1>

    %or co))unication with !SS4>SS s+ste)s and 1s/ the platfor) shall support the

    following *uilt-in adapters:

    o 1ricsson Multi-Activation

    o Cisco routers

    o Cisco switches

    o Microsoft Active 'irector+

    o Microsoft 1xchange Server

    19

  • 7/25/2019 Annex 3 Technical Details

    20/23

    Annex 3 to Request for Proposal

    May-2012

    The platfor) should support reception of CSV files through local or ftp file-

    s+ste). for *ulk provisioning

    The platfor) should support Bplug-and-pla+D integration via we*-services with

    upstrea) downstrea) s+ste)s,

    The platfor) should have the a*ilit+ to connect to an external data*ase or

    network inventor+ s+ste) in order to enrich activation request with external

    data,

    The platfor) should ena*le the auto)atic transfer via ftp or sftp of N*ulk2

    provisioning files including service activation orders/ parse the N*ulk2

    provisioning file/ execute activation co))ands in )ultithreaded fashion and

    return execution results to upstrea) s+ste),

    The s+ste) shall support graphicall+ configured scheduler co)ponent

    supporting the scheduled execution of *atch processes

    The platfor) should support reception of inco)ing requests

    %ro) several upstrea) s+ste)s i,e, Self Care #ortal/ !rder 1ntr+ s+ste).

    si)ultaneousl+

    6sing several upstrea) interfaces as FM over MS/ !SS4/ 1A(

    si)ultaneousl+,

    The proposed solution should provide the necessar+ tools to develop

    connectors to integrate with undefined s+ste)s

    2#.#3 /igration

    The proposed solution should include )igration fro) the current s+ste),

    2#.#4 *ervice Activation 'rocess

    Support for full+ transactional activation including configura*le roll*ack when

    errors in activation process occur,

    There should *e configuration on the network adapter level concerning if

    co))ands can *e executed s+nchronousl+ or as+nchronousl+ in theele)ents,

    20

  • 7/25/2019 Annex 3 Technical Details

    21/23

    Annex 3 to Request for Proposal

    May-2012

    The s+ste) shall support workflow deco)position to independent individual

    workflows/ as well as the co)position of a workflow fro) existing individual

    workflows,

    There should *e configuration capa*ilit+ on the network adapter level

    concerning ti)eout and retr+ to esta*lish connection )echanis)s in case of

    connectivit+ pro*le)s with 1s,

    The proposed platfor) shall e)plo+ a 51>-*ased 86( providing advanced

    )onitoring and reporting capa*ilities for *oth s+ste) operation and deplo+ed

    services, More specificall+ the 51>->ased 86( shall allow to:o Monitor deplo+ed Serviceso Monitor the status of service activation requests

    o View service request statistics per provisioning do)ain/ service

    request t+pe/ )anage)ent do)ain/ ti)e periodo 8enerate aggregated reports

    o Auditing of failed activation requests

    o Test new services and activation adapters

    o Set configuration para)eters

    The s+ste) shall support functionalit+ for log file housekeeping,

    The s+ste) shall support prioriti0ation of inco)ing service requests, The

    priorities shall *e configura*le via the s+ste) 86(,

    The s+ste) shall support capa*ilit+ to select and retr+ failed activation

    requests via the 86(,

    The s+ste) should support internal traffic shaping )echanis)s according to

    configura*le rules safeguarding the s+ste) perfor)ance,

    2#.#5 *ecurit0 hierarch0

    The proposed solution should support granular and advanced securit+ access

    )odel, (n other words/ all unauthori0ed )enu ite)/ reports/ dash*oard ite)s/ views/

    etc will *e hidden fro) the user,

    - A*ilit+ to define ver+ granular privileges- Support of *uilt-in user groups or roles *ased on *est practices- A*ilit+ for users to change their passwords and profile- All user profiles and passwords are encr+pted in the data*ase- A*ilit+ to generate audit trail logs of all actions perfor)ed including the

    ad)inistrator role

    21

  • 7/25/2019 Annex 3 Technical Details

    22/23

    Annex 3 to Request for Proposal

    May-2012

    2#.#6 %echnical )equirements

    5e*-*ased using SS technologies

    %ast/ eas+ and secure access to the application #refera*le to have )ini)al ad)inistration

    !perating s+ste): inux or Solaris preferred

    The s+ste) should have open architecture/ use open interfaces of the

    s+ste)2s functional *locks interaction,

    Must support (#V and (#v@

    2#.#8

  • 7/25/2019 Annex 3 Technical Details

    23/23

    Annex 3 to Request for Proposal

    May-2012

    The solution should include proHect )anage)ent and professional services to

    i)ple)ent the proHect,

    The Applicant should provide a proHect schedule plan for the proHect i)ple)entation,

    2#.#&. %echnical support and maintenance

    The proposed solution should include the staffing details for nor)al operations of the

    s+ste), (n addition to define roles *ased on *est practices and standards,

    The solution should include technical support and )aintenance with &xI hot line

    and online ticketing s+ste), The first 3 +ear technical support will need to *e part of

    the solution or the co))ercial proposal,

    23