[电信]EWSDPME-02010ReleaseNote.doc

Release Note for PME-02-010-OEnhanced Black/White list function1. Project Summay:Enhanced Black/White list function in V15s the calling and called party number shall be correlative with trunk.B600 plan date: 15, Oct/2002Release Date: 20, Aug/2002Developer: Wang TaoSystem Test: Qu YiFR: CP3226Solution: CA699L4D.A0A02. Feature DescriptionIn the environment of multiple telecommunication operators, the normal black/white feature at GW is no longer enough for handling complex situations. For instance, to the same calling party/called party number, the call processing of black/white list will be different when the call is go through in different trunk group. In another words, every trunk group should have its own black/white list, the call processing has to be done according to the black/white list property of calling party number/ called party number at this trunk group. This feature is implemented based on enhanced black/white list feature and it is the improvement of the latter. The feature could be called as black/white list with trunk group.3. SolutionAssigning each trunk group a unique indicator, which actually is prefix number. When the call goes through a trunk group, the calling party and called party number will get prefix from the trunk group and build up new calling party number/called party number. Because the prefix number is unique, the new calling party and called party number with the prefix will be unique too. By doing this, the relationship between calling party/called party and trunk group has built up. According to the black/white list property of new calling party number and called party number, the call will be continued or be released. Relation with other B/W patches:1) CD675 is a blocking patch for all special isl features for China2) CD678 is enable patch for normal b/w list, if CD675 exist3) CA699 is feature patch for adding enhanced b/w list function based on normal b/w function. The enhanced and normal b/w functions can co-exist. 4. Basic Database Testbed TD3 DB example:/* ENABLE BW FUNC./*DACT LTGPRPCH:ID=T0xxCD675L4Z;/* check patch CA696 and BZ534 must incooperatedDISP C7USER: USNAME= SCCP;CR C7USER: USNAME=SCCP, DPC=0-12-0, NETNAME= MNET1;DISP SIGPOINT;sCR SIGPOINT: NET ID=1, NET NAME=MNET1, SPC=0-11-0 /*own spc* /DISP SPLNKLOC; CR SPLNKLOC: SPLNKLOC NAME=ISLLOC, NET ID=1, SEGM.REASS. FLAG=FASLE, UPPER LIMIT SEGM. =255;/*ENTRSCDATA:SPC=0-0-3, NETIND=NAT0, MAXSGLEN=255, USEXUDT=NO, SCCLSR=WB; */DISP SPAPLOC;CR SPAPLOC: SPAPLOC Name= ISLSPAP, SSN=240, Cong.Ctrl.Decr.Timer=2,#Cong.Ctrl.Incr.Timer=2, Cong.Ctrl.No.Levels=10,Sccp STFS Timer=0,# SPAP STFS Timer=0, SSID=IN Application In SSP 5, VMS=OFF; /*CR SCUSER: SSID=IN5, NETIND=NAT0, SSN=240, TCAPUS=Y; */DISPSPSSN;CRSPSSN: SPLNKCLOC NAME=ISLLOC, SSN=240, SPSSN NAME=ISLAPL, SSID=IN Application In SSP 5;/* CR SCSS: SSID=IN5, SPC=0-0-2, NETIND=NAT0; */* 997CR INTRIG: PRID=BWLT, SKEY=997, SSID=IN5, ACNSEL=0, PROT=CS2, CHGINF=NOINTV, RTGP=SPC, DPC=0-11-0, NETIND=NAT0, DACTINC=SNA4, GENPROP=CLIREQ;/*ACT INTRIG: PRID=BWLT;CR INSCM: SCMID=BWLT, TYPE=TDP3, PRID= BWLT, COLDIG=6, PREFIX=000102;CR INSCM: SCMID=BW, TYPE=TDP3, PRID= BWLT, COLDIG=6, PREFIX=000103;CR INSCMREF: SCMID=BWLT, TGNO=IS2LB0(incoming trunk);ACT INSCMREF: TYPE=TDP3, TGNO= IS2LB0;CR INSCMREF: SCMID=BW, TGNO=IS2LB1ACT INSCMREF: TYPE=TDP3, TGNO= IS2LB1;/* Incoming trunk is triggered:Prerequisite: No GCOS= Prop30 or Prop 31 should be present at this trunk*/* A number B/W attribute value is described in following table:Calling partyCalled partyNoneWhite listBlack listNoneNoneACCL-4ACCL-8White listACCL-2ACCL-6ACCL-10Black listACCL-3ACCL-7ACCL- 11CR DN: DN=AA000&AA999, LAC=022;CR CPT: CODE=AA, LAC=022, TRATYP=CPTDN;CR ZOPT: CODE=AA, ZOCHA=NOPULSE;/* CR SUB: LAC=022, DN=AA000, CAT=TXS;CR SUB: LAC=022, DN=AAxxx, CAT=TXS, COSDAT=ACCL-x;CR INAUTH: ANS=, TXSPROF= 022-AAxxx;5. Test StrategyTest configurations:C1: A(3230241)-701(IS2LB0)B(3230242) ISUP localC2: A(3230241)-703(IS2LB0)- 0705-B(3230242)ISUP-ISUP tollC3: A(3230241)-0411(I3A41L)- 608-B(3230242)MFC-TUP tollC4: A(3230241)-614(BTBLA4)-00610-B(3230242)TUP-ITUP tollD1: A1- A (DIVI-7013230242)-BD2: A1- A(DIVDA-70307053230242)- BE1: A(3230241)-701(IS2LB1)B(3230242) Route 2; Prefix=000103E2: A(3230241)-703(IS2LB4) 0705 -B(3230242) Route 2; Prefix=000103Test case: B/W ScenarioConfigResultDatabase modificationBWC1Connect(AMA OK)CRINAUTH:ANS=0001023230241,ACCL-3;CRINAUTH:ANS=0001023230242,ACCL-4;D1ConnectBnoneE1ReleaseBlock route-1of C1CRINAUTH:ANS=0001033230241,ACCL-3;CRINAUTH:ANS=0001033230242, A000;BWC2Connect(AMA OK)ANS=0001023230241, ACCL-3;ANS=0001020705, ACCL-4;D1ConnectBBE2ReleaseBlock route-1of C2ANS=0001033230241,ACCL-3;ANS=0001033230242, ACCL-11;Bnone/BC1, C2ReleaseANS=0001023230241, ACCL-3;ANS=0001033230242, A000ANS=0001033230242, ACCL-10ANS=0001020705, A000WBC1, C2ConnectANS=0001023230241, ACCL-10ANS=0001033230242, ACCL-10ANS=0001020705, ACCL-10BnoneC3ReleaseANS=0001023230241, ACCL-7ANS=000102608, A000BWC4ConnectANS=000102(022)3230241, ACCL-7ANS=00010200610, ACCL-76. Limitation/Technical dataB/W list with trunk group will have following restriction /notification points:1) The maximum digit length of calling/called party number, which the b/w list property could be determined, is 18.2) All features (999/998/997/997/995) will share the same DB area. The whole size of DB can contain 1 millions entries