Вы находитесь на странице: 1из 8

ATM - Based High-Speed Signaling Link

High Speed Signaling Links provide a High Capacity, high speed, signaling link to the MTP.Two types of HSL exist, those are: HSL based on ATM and HSL based on Q.703 HSL Based on ATM: They consist of a High Speed Signaling Terminal based on the hardware platform RPP and the application software SAAL and ATM. Each RPP provides one HSL, with a Digital Link version 2 (DL2) interface to the Group Switch.

MTP 3b
MTP 2 MTP 1

SSC F

SSCOP

AAL5/ATM
G.80 4

64kbit

HDLC Protocol stack for HSL based on ATMMTP

2Mbit/s ATM on E1

G.804: ITU-T standard G.804 specifies the mapping of ATM cells into PDH
/ SDH systems. AAL - ATM Adaptation Layer: Provides a conversion function to and from ATM for various types of information, including voice, video, and data. There are several versions of AAL, each applicable to a given information type. All of them convert elements of an information stream (such as voice frames and data packets) into cells, giving ATM the versatility to carry many different types of data, from constant rate voice data to highly bursty messages generated by LAN, all within the same cell format.

Signaling ATM Adaptation Layer (SAAL):

Service Specific Coordination Function (SSCF)


SSCF is the uppermost sub layer in the protocol stack for SAAL. The following is a list of the services offered by SSCF: Flow Control: SSCF is informed of congestion by an implementation dependant function and SAAL user is notified about this congestion. Change Link Status: SSCF receives primitives from MTP3 or signals from SSCOP and maintains local variables pertaining to the status of the link it may also generate MTP3 primitives or SSCOP signals. Reporting to Layer Management: Upon release of an SSCOP connection SSCF indicates that situation to SAAL User. The reason either received from SSCOP or determined by SSCF. Processor Outage: When local processor outage condition arises, SSCF is notified about the situation by Layer Management Alignment Procedure: Started during establishment of the connection of SAAL user. The alignment procedure is applied to verify the quality of the link before it is put into service. Message Transmission: Used by SAAL user in order to request sending on PDUs to the remote end. Transmission Used by SAAL in order to send messages received by the remote end to SAAL user.

Service Specific Connection Oriented Protocol (SSCOF)


SSCOP is a peer-to-peer protocol which provides the following functions: Transfer of user data with sequence integrity Error correction with selected retransmission Flow control Connection control Error reporting to layer management Connection maintenance on the prolonged absence of data transfer Local data retrieval by the user Error detection of protocol error information, and status reporting Definition of ATM based HSL between MGw & BSC BSC: Define new RPP's, EM's and SNTs for HSL

DBTRI; DBTSI: TAB=RPSRPBSPOS, RPADDR=68, BRNO=2, MAGNO=00, SLOTNO=7, BUSCONN=NO; DBTRE: COM; EXRPI: RP=68, TYPE=RPPS1; !C7STH! EXRUI:RP=68, SUID="9000/CXC 146 03 EXRUI:RP=68, SUID="9000/CXC 146 05 EXRUI:RP=68, SUID="9000/CXC 146 089 EXRUI:RP=68, SUID="9000/CXC 146 070 EXRUI:RP=68, SUID="9000/CXC 146 08

R1A08"; R1A03"; R1A05"; R2C01"; R2A01";

! RPIFDR ! ! RPFDR ! ! INETR ! ! RPEXR ! ! C7STHR ! R2A01";

EXEMI:EQM=C7STH-0&&-31, RP=68, EM=0, SUID="9000/CXC 146 08 BLEME:RP=68,EM=0; BLRPE:RP=68; NTCOI:SNT=C7SNTH-0, SNTP=MUX3-14-0, SNTV=1; !RP 68; EXDUI:DEV=C7SNTH-0&&-31; NTBLE: SNT=C7SNTH-0; C7STI:ST=C7STH-1,ITYPE=12; STDEP:DEV=RALT-129&&-159; BLODI:DEV=RALT-129&&-159; STDEP:DEV=C7STH-1&&-31; BLODI:DEV=C7STH-1&&-31 ; EXSPI:NAME=MGW2,NUMCH=31; ; EXSSI:DEV1= RALT-129, CH16; EXSSI:DEV2= C7STAH-1,CH16; EXSPE; EXSCI:NAME= MGW2,DEV=RALT-129;

C7SLI:LS=3-501,SLC=0,ACL=A1,ST=C7STH-1 ,SDL="RALT-129 ,C7STH-1,MGW2",PARMG=17;

MGW R4.2: Define MOs AtmPort, VplTp, VpcTp, VclTp, Aal5TpVccTp, NniSaalTp, Mtp3bSpItu, Mtp3bSrs, Mtp3bSr, Mtp3bSls, and Mtp3bSlItu. Note: For adding additional HSL MO Scripts AtmPort, VplTp, VpcTp, VclTp, Aal5TpVccTp, NniSaalTp and Mtp3bSlItu is enough. Example Scripts :Atmport Script:
//================= ECHO "==>> Creating ATMPort" CREATE ( parent "ManagedElement=1,TransportNetwork=1" identity "MAIN-27-1" moType AtmPort exception none nrOfAttributes 2 userLabel String "MAIN-27-1"

uses Ref "ManagedElement=1,Equipment=1,Subrack=1,Slot=27,PlugInUnit=1,ExchangeTerminal=1,E1PhysPathTerm= MAIN-27-1" )

VplTp: //============================== ECHO "==>> Creating VplTp CREATE ( parent "ManagedElement=1,TransportNetwork=1,AtmPort=MAIN-27-1" identity "Vp0" moType VplTp exception none nrOfAttributes 3 userLabel String "MAIN-27-1_Vp0" atmTrafficDescriptor Reference "ManagedElement=1,TransportNetwork=1,AtmTrafficDescriptor=C1Q1P4500M0_1" externalVpi Integer "0" )

VpcTp: //============================== ECHO "==>> Creating VpcTp" CREATE ( parent "ManagedElement=1,TransportNetwork=1,AtmPort=MAIN-27-1,VplTp=Vp0" identity "1" moType VpcTp exception none nrOfAttributes 2 userLabel String "MAIN-27-1_Vp0_Vpc1" alarmReport Integer "7" )

VclTp: //============================== ECHO "==>> Creating VclTp" CREATE ( parent "ManagedElement=1,TransportNetwork=1,AtmPort=MAIN-27-1,VplTp=Vp0,VpcTp=1" identity "Vc32" moType VclTp exception none nrOfAttributes 3 userLabel String "MAIN-27-1_Vp0_Vc32" atmTrafficDescriptorId Reference "ManagedElement=1,TransportNetwork=1,AtmTrafficDescriptor=C3Q3P4000M3999_1" externalVci Integer "32" )

Aal5TpVccTp: //================== ECHO "=====>> Creating Aal5TpVccTp " CREATE ( parent "ManagedElement=1,TransportNetwork=1" identity "MAIN-27-1-Vp0-Vc32" moType Aal5TpVccTp exception none nrOfAttributes 7 userLabel String "VC_ CMGW02_BSC05_CPCS_1" vclTpId Reference "ManagedElement=1,TransportNetwork=1,AtmPort=MAIN-27-1, VplTp=Vp0, VpcTp=1, VclTp=Vc32" fromUserMaxSduSize Integer "2044" toUserMaxSduSize Integer "2044" processorId Reference "ManagedElement=1,Equipment=1,Subrack=1,Slot=6,PlugInUnit=1" continuityCheck Boolean "TRUE" alarmReport Integer "2" ) NniSaalTp: //================== ECHO "===>> Creating NniSaalTp" ECHO "=====>> Creating NniSaalTp " CREATE ( parent "ManagedElement=1,TransportNetwork=1" identity "MAIN-27-1-Vp0-Vc32" moType NniSaalTp exception none nrOfAttributes 4 userLabel String "CMGW02_BSC05_CPCS_1" nniSaalProfileId Reference "ManagedElement=1,TransportNetwork=1,NniSaalProfile=7040" aal5TpVccTpId Reference "ManagedElement=1,TransportNetwork=1,Aal5TpVccTp=MAIN-27-1-Vp0-Vc32" maxSduSize Integer "2040" ) Mtp3bSpItu: //================== ECHO "===>> Creating Mtp3bSpItu" ECHO "=====>> Creating Mtp3bSpItu " CREATE ( parent "ManagedElement=1,TransportNetwork=1" identity "3-502" moType "Mtp3bSpItu" exception none nrOfAttributes 6 userLabel String "3-502" networkInd Integer "3" signallingPointCode Integer "502" testPatternSltm String "A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5"

nodeBehaviour Integer "5" rpuId Ref "ManagedElement=1,SwManagement=1,ReliableProgramUniter=200" )

Mtp3bSrs: //================== ECHO "=====>> Creating Mtp3bSrs " CREATE ( parent "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=3-502" identity "3-901" moType Mtp3bSrs exception none nrOfAttributes 3 userLabel String "SRS_CMSCs01" destPointCode Integer "901" autoReroute Boolean false )

Mtp3bSls: //================== ECHO "=====>> Creating Mtp3bSls" CREATE ( parent "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=3-502" identity "3-4006_1" moType Mtp3bSls exception none nrOfAttributes 2 userLabel String "SLS_BSC05" mtp3bSrsId Reference "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=3-502,Mtp3bSrs=3-4006" )

Mtp3bSr: ECHO "=====>> Creating Mtp3bSr " CREATE ( parent "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=3-502,Mtp3bSrs=3-4006" identity "Sr1" moType Mtp3bSr exception none nrOfAttributes 3 userLabel String "SR_BSC05" priority Integer "1" linkSetM3uId Reference "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=3-502,Mtp3bSls=3-4006_1" )

Mtp3bSlItu: //================== ECHO "=====>> Creating Mtp3bSlItu" CREATE ( parent "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=3-502,Mtp3bSls=3-4006_1" identity "3-4006_1_Slc0" moType "Mtp3bSlItu" exception none nrOfAttributes 3 userLabel String "BSC05_0" tpId Reference "ManagedElement=1,TransportNetwork=1,NniSaalTp=MAIN-27-1-Vp0-Vc32" signLinkCode Integer "0" ) NniSaalProfile: ECHO "Profile 440" CREATE ( parent "ManagedElement=1,TransportNetwork=1" identity "440" moType "NniSaalProfile" exception none nrOfAttributes 2 userLabel String "Profile 440" profileData Struct nrOfElements 26 mps Integer "2" nrOfPDUsDuringProving Integer "310" initialCredit Integer "110" maxCC Integer "4" maxPD Integer "60" maxStat Integer "67" maxNRP Integer "0" congestionLevel1Abatement Integer "60" congestionLevel1OnSet Integer "70" congestionLevel2Abatement Integer "70" congestionLevel2OnSet Integer "80" congestionLevel3Abatement Integer "80" congestionLevel3OnSet Integer "90" discardMessagesLevel1 Integer "80" discardMessagesLevel2 Integer "90" discardMessagesLevel3 Integer "100" timerPoll Integer "225" timerKeepAlive Integer "450" timerNoResponse Integer "1500" timerIdle Integer "450" timerCC Integer "200" timerNoCredit Integer "1500" timerRepeatSrec Integer "3600000"

timerT1 Integer "5000" timerT2 Integer "30000" timerT3 Integer "16" )

Вам также может понравиться