SCCP:Architecture - Revision history

Allyntree: /* References */

2018-04-03T14:15:24Z

References

← Older revision		Revision as of 10:15, 3 April 2018
Line 41:		Line 41:
	*[[SCCP:Interworking\|Interworking]]		*[[SCCP:Interworking\|Interworking]]
	*[[SCCP:Messages\|Messages]]		*[[SCCP:Messages\|Messages]]


	~~[[category:Needs revising]]~~

Allyntree at 14:15, 3 April 2018

2018-04-03T14:15:10Z

← Older revision		Revision as of 10:15, 3 April 2018
Line 26:		Line 26:


	SCCP Userpart can be used in conjunction with an above local TCAP layer and can be used as a standalone and communicates with remote ~~TCAP8~~ layer (host application). See the connection mode table in the SCCP Userpart Configuration section.		SCCP Userpart can be used in conjunction with an above local TCAP layer and can be used as a standalone and communicates with remote TCAP layer (host application). See the connection mode table in the SCCP Userpart Configuration section.

Allyntree: needs revising edit

2018-04-03T14:14:47Z

needs revising edit

← Older revision		Revision as of 10:14, 3 April 2018
Line 22:		Line 22:


	~~[[Image:filename\|widthpx\| ]]~~

			SCCP LSAP must be associated with one MTP3 Userpart via a 1-to-1 association. A SCCP Route indicates a DPC that is accessible from this SCCP configuration node and their [[SSN]].
	SCCP LSAP must be associated with one MTP3 Userpart via a 1-to-1 association. A SCCP Route indicates a DPC that is an accessible from this SCCP configuration node and their [[SSN]].

Ktrueman: added missing image

2009-11-27T21:45:40Z

added missing image

← Older revision		Revision as of 17:45, 27 November 2009
Line 12:		Line 12:


	[[Image:~~filename~~\|~~widthpx~~\| ]]		[[Image:SCCP architecture.JPG\|750px\| ]]

Ktrueman: added links

2009-09-10T17:07:25Z

added links

← Older revision		Revision as of 13:07, 10 September 2009
Line 32:		Line 32:

	A SCCP layer has a Userpart section which represents a sub-system number.		A SCCP layer has a Userpart section which represents a sub-system number.


			== References ==
			*[[SCCP:Connectionless Service\|Connectionless Service]]
			*[[SCCP:Management\|Management]]
			*[[SCCP:Addressing\|Addressing]]
			*[[SCCP:Global Title Translation Association\|Global Title Translation Association]]
			*[[SCCP:Routing\|Routing]]
			*[[SCCP:Traffic Limitation and Congestion Control\|Traffic Limitation and Congestion Control]]
			*[[SCCP:Interworking\|Interworking]]
			*[[SCCP:Messages\|Messages]]


			[[category:Needs revising]]

Ktrueman: initial content

2009-08-11T13:16:41Z

initial content

New page

The SCCP software supports these functions:

*[[SCCP:Connectionless Service|Connectionless Service]]
*[[SCCP:Management|Management]]
*[[SCCP:Routing|Routing]]
*[[SCCP:Traffic Limitation and Congestion Control|Traffic Limitation and Congestion Control]] (ITU-96)
*[[SCCP:Interworking|Interworking]]

SCCP provides the functions and procedures to transfer data across an [[SS7]] network. SCCP is a
service provider to [[TCAP]] and a service user of [[MTP3 Layer|MTP Level 3]] (as shown in the figure immediately below).

[[Image:filename|widthpx| ]]

A SCCP layer has a Network section which represents a network identifier for a specific protocol
variant. For a Network you must define:
*[[LSAP|LSAP(s)]]
*Routes (for a specific or range of [[DPC|destination point codes (DPC)]])
*Userpart

[[Image:filename|widthpx| ]]

SCCP LSAP must be associated with one MTP3 Userpart via a 1-to-1 association. A SCCP Route indicates a DPC that is an accessible from this SCCP configuration node and their [[SSN]].

SCCP Userpart can be used in conjunction with an above local TCAP layer and can be used as a standalone and communicates with remote TCAP8 layer (host application). See the connection mode table in the SCCP Userpart Configuration section.

A SCCP layer has a Userpart section which represents a sub-system number.