Signalling Connection Control Part: Difference between revisions

Revision as of 18:11, 19 June 2008

Revision as of 18:17, 19 June 2008

Line 6:

The base SCCP specification is defined by the [[ITU-T]], in recommendations [http://www.itu.int/rec/T-REC-Q.711/en/ Q.711] to [http://www.itu.int/rec/T-REC-Q.714/en/ Q.714], with additional information to implementors provided by [http://www.itu.int/rec/T-REC-Q.715/en/ Q.715] and [http://www.itu.int/rec/T-REC-Q.716/en/ Q.716].<ref name="qseries">[http://www.itu.int/rec/T-REC-Q/en/ ITU-T Q-Series Recommendations].</ref> There are, however, regional variations defined by local standards bodies. In the United States, [[ANSI]] publishes its modifications to [http://www.itu.int/rec/T-REC-Q.713/en/ Q.713] as ANSI T1.112. The [[Telecommunication Technology Committee|TTC]] publishes as JT-Q.711 to JT-Q.714, and Europe [[ETSI]] publishes ''[http://webapp.etsi.org/workprogram/Report_WorkItem.asp?WKI_ID=6605 ETSI EN 300-009-1]:'' both of which document their modifications to the [[ITU-T]] specifications.

==Routing facilities beyond MTP-3==

Although [[Message Transfer Part|MTP-3]] provides routing capabilities based upon the [[Point Code]], SCCP allows routing using a [[Point Code]] and [[Subsystem number]] or a [[Global Title]].

A Point Code is used to address a particular node on the network, whilstwhereas a [[Subsystem number]] addresses a specific application available on that node. SCCP employs a process called [[Global Title Translation]] (which is similar to [[Domain name system|DNS]] resolution in [[Internet Protocol|IP]] networks) in order to determine [[Point CodesCode]]s from [[Global TitlesTitle]]s so as to instruct [[Message Transfer Part|MTP-3]] on where to route messages.

SCCP messages contain parameters which describe the type of addressing used, and how the message should be routed: