In this section we explore the new CGIN-based support for SS7 by considering CGIN APIs and resource adaptors in contrast to our previous offerings for SS7 — INCC-based APIs and resource adaptors in the IN Connectivity pack.
CGIN approach to SS7 APIs and resource adaptors
-
OpenCloud’s new architecture
-
One resource adaptor for all protocols
-
Resource APIs, resource adaptor types, and resource adaptor implementation are auto-generated by the CGIN toolchain
-
All "TCAP libraries" are auto-generated by the CGIN toolchain
-
Only integration with Signalware TCAP is needed
-
Any protocol with an ASN.1 definition is supported by the CGIN toolchain. For example, vendor variants and customisations of standard protocols can be supported.
-
Available in the CGIN Connectivity Pack
INCC approach to SS7 APIs and resource adaptors
-
OpenCloud’s earlier architecture
-
Resource adaptor per protocol
-
Resource APIs, resource adaptor types, and resource adaptor implementations were all developed by hand
-
Utilised Ulticom’s "TCAP libraries" for protocols such as CAP, INAP, and MAP
-
Hand-crafted integration with the Signalware stack is required for each protocol
-
Limited to the protocols supported by the SS7 stack vendor. For example, vendor variants and customisations are unlikely to be supported.
-
Available in the IN Connectivity Pack
The following sections compare and contrast the new CGIN unified resource adaptor to the deprecated INCC based resource adaptors in terms of Resource Adaptor Architecture and Resource Adaptor APIs.
