network protocols handbook.pdf

More documents

Recommendations

Info

308Protocols GuideSS7 / C7 ProtocolProtocol NameISUP: ISDN User PartProtocol DescriptionThe ISDN User Part (ISUP), a key protocol in the SS7 / C7 signallingsystem, defines the protocol and procedures used toset-up, manage, and release trunk circuits that carry voice anddata calls over the public switched telephone <strong>network</strong> (PSTN)between different switches. ISUP is used for both ISDN andnon-ISDN calls. A simple call flow using ISUP signaling is asfollows:Call set up: When a call is placed to an out-of-switch number,the originating SSP transmits an ISUP initial address message(IAM) to reserve an idle trunk circuit from the originating switchto the destination switch. The destination switch rings the calledparty line if the line is available and transmits an ISUP addresscomplete message (ACM) to the originating switch to indicatethat the remote end of the trunk circuit has been reserved. TheSTP routes the ACM to the originating switch which rings thecalling party’s line and connects it to the trunk to complete thevoice circuit from the calling party to the called party.Call connection: When the called party picks up the phone, thedestination switch terminates the ringing tone and transmits anISUP answer message (ANM) to the originating switch via itshome STP. The STP routes the ANM to the originating switchwhich verifies that the calling party’s line is connected to thereserved trunk and, if so, initiates billing.Call tear down: If the calling party hangs-up first, the originatingswitch sends an ISUP release message (REL) to release thetrunk circuit between the switches. The STP routes the REL tothe destination switch. If the called party hangs up first, or if theline is busy, the destination switch sends an REL to the originatingswitch indicating the release cause (e.g., normal release orbusy). Upon receiving the REL, the destination switch disconnectsthe trunk from the called party’s line, sets the trunk state toidle, and transmits an ISUP release complete message (RLC) tothe originating switch to acknowledge the release of the remoteend of the trunk circuit. When the originating switch receives (orgenerates) the RLC, it terminates the billing cycle and sets thetrunk state to idle in preparation for the next call.Protocol StructureThe ANSI and ITU-T have slightly different ISUP format. ITU-TISUP message format:Routing label (5bytes)Circuit identification code (2 bytes)Message type code (1 byte)Parameters – varies according to message type values• Routing label - The routing label is used by the relevantuser part to identify particulars to which the messagerefers. It is also used by the Message TransferPart (MTP) to route the message towards its destinationpoint.• Circuit identification code - The allocation of circuitidentification codes to individual circuits is determinedby bilateral agreement and/or in accordancewith applicable predetermined rules.• Message type code - The message type code uniquelydefines the function and format of each ISDN UserPart message. Each message consists of a numberof parameters. Message types may be:Address completeAnswerBlockingBlocking acknowledgementCall progressCircuit group blockingCircuit group blocking acknowledgementCircuit group queryCircuit group query responseCircuit group resetCircuit group reset acknowledgementCircuit group unblockingCircuit group unblocking acknowledgementCharge informationConfusionConnectContinuityContinuity check requestFacilityFacility acceptedFacility rejectForward transferIdentification requestIdentification responseInformationInformation requestInitial addressLoop back acknowledgementNetwork resource managementOverloadPass-alongReleaseRelease completeReset circuitResumeSegmentationSubsequent addressSuspendUnblockingUnblocking acknowledgementUnequipped CIC
309Protocols GuideSS7 / C7 ProtocolUser Part availableUser Part testUser-to-user information• Parameters - Each parameter has a name which iscoded as a single octet. The length of a parametermay be fixed or variable, and a length indicator foreach parameter may be included.Related <strong>protocols</strong>SS7, ASP, BICC, BISUP, DUP, MTP, SCCP, TCAP, TUP, MAPSponsor SourceISUP is defined by ITU-T Q.763 documents.Referencehttp://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-Q.763SS7 ISDN User Part
Page 1 and 2:
www.dbeBooks.com - An Ebook Library
Page 3 and 4:
ITable of ContentsTable of Contents
Page 6 and 7:
IVTable of ContentsCR-LDP: Constrai
Page 8 and 9:
VITable of ContentsCOPS: Common Ope
Page 10 and 11:
VIIITable of ContentsGARP: Generic
Page 12 and 13:
XTable of ContentsIGRP: Interior Ga
Page 14 and 15:
XIIFigureFigureFigure 1-1: Communic
Page 16 and 17:
XIVPerfacePrefaceWe are living in t
Page 18 and 19:
2Network Communication Architecture
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
10Network Communication Architectur
Page 28 and 29:
12Protocols GuideTCP/IP Protocolspo
Page 30 and 31:
14Protocols GuideTCP/IP - Applicati
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
52Protocols GuideTCP/IP - Session L
Page 70 and 71:
54Protocols GuideTCP/IP - Transport
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
64Protocols GuideTCP/IP - Network L
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
98Protocols GuideTCP/IP - Data Link
Page 116 and 117:
100Protocols GuideTCP/IP - Data Lin
Page 118 and 119:
102Protocols GuideSecurity and VPNP
Page 120 and 121:
104Protocols GuideSecurity and VPN
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
120Protocols GuideVoice Over IP(VOI
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
150Protocols GuideWANOtherxDSL: Dig
Page 168 and 169:
152Protocols GuideWAN - ATM Protoco
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
170Protocols GuideWAN - Broadband A
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
178Protocols GuideWAN - PPP Protoco
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
188Protocols GuideWAN - Other WAN P
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
196Protocols GuideLAN - Ethernet Pr
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
204Protocols GuideLAN - Virtual LAN
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
210Protocols GuideLAN - Wilress LAN
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
216Protocols GuideLAN - Other Proto
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
222Protocols GuideMAN ProtocolsProt
Page 240 and 241:
224Protocols GuideMAN Protocols(0).
Page 242 and 243:
226Protocols GuideStorage Area Netw
Page 244 and 245:
228Protocols GuideSAN ProtocolsProt
Page 246 and 247:
230Protocols GuideSAN ProtocolsThe
Page 248 and 249:
232Protocols GuideSAN Protocols•
Page 250 and 251:
234Protocols GuideSAN ProtocolsSpon
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
240Protocols GuideISO Protocols in
Page 258 and 259:
242Protocols GuideISO Protocols - A
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275: 258Protocols GuideISO Protocols - A
Page 276 and 277: 260Protocols GuideISO Protocols - A
Page 278 and 279: 262Protocols GuideISO Protocols - N
Page 284 and 285: 268Protocols GuideCisco ProtocolsPr
Page 294 and 295: 278Protocols GuideCisco Protocolsti
Page 296 and 297: 280Protocols GuideNovell NetWare an
Page 304 and 305: 288Protocols GuideIBM ProtocolsSNAT
Page 306 and 307: 290Protocols GuideIBM ProtocolsProt
Page 308 and 309: 292Protocols GuideIBM ProtocolsSNA
Page 316 and 317: 300Protocols GuideAppleTalk: Apple
Page 318 and 319: 302Protocols GuideDECnet and Protoc
Page 320 and 321: 304Protocols GuideSS7 / C7 Protocol
Page 334 and 335: 318Protocols GuideOther Protocols
Page 336 and 337: 320Protocols GuideOther ProtocolsPr
Page 338 and 339: 322Protocols GuideOther ProtocolsPr
Page 340 and 341: 324Network Protocols Dictionary: Fr
Page 358 and 359: 342Network Communication Protocols
show all

network protocols handbook.pdf

Create successful ePaper yourself

Delete template?

Save as template?