SCCP:Architecture
(added missing image) |
m (needs revising edit) |
||
| Line 22: | Line 22: | ||
| − | |||
| − | + | 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 | + | |
Revision as of 09:14, 3 April 2018
The SCCP software supports these functions:
- Connectionless Service
- Management
- Routing
- Traffic Limitation and Congestion Control (ITU-96)
- 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 MTP Level 3 (as shown in the figure immediately below).
A SCCP layer has a Network section which represents a network identifier for a specific protocol
variant. For a Network you must define:
- LSAP(s)
- Routes (for a specific or range of destination point codes (DPC))
- Userpart
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 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.
