SCF Function Blocks

3.16.1 SSI

SSI is part of the kernel and responsible for service script processing. It contains the database memory to allow fast access to service logic and service data modules, but is not responsible for the database and mainte-nance functions.

3.16.2 SST

SST contains the external controltypes listed under tables.

3.16.3 SSINT

SSINT contains the basic controltypes, which are mostly internal con-troltypes (except for JUMP). SSINT subscribes these concon-troltypes to the kernel at restart.

3.16.4 SSINT2

SSINT2 contains basic controltypes set 2, which are all internal con-troltypes except the relative timer. SSINT2 subscribes these concon-troltypes to the kernel at restart.

3.16.5 SSINT3

SSINT3 holds basic controltypes set 3, which are external controltypes (except for Explicit monitoring, Explicit monitoring type 2, Explicit event handling and Release resource).

3.16.6 SSINT4

SSINT4 contains the basic controltypes set 4, which are internal con-troltypes, except MANDM. SSINT4 will also support the INM interface, since it has a full command interface for the controltypes.

3.16.7 SSINT5

This block contains the basic controltypes set 5, containing MODSTR, NUM2STR and NR2NR. SSINT5 will also support the INM interface, since it has a full command interface for the controltypes.

3.16.8 SSIA

SSIA is responsible for the administrative part of the kernel, that is, the database maintenance and allocation functions. It contains the service data reference tables and is responsible for the consistency of the database.

3.16.9 SSIEXT

SSIEXT contains the subscription interface for controltypes to the kernel.

It distributes part of the subscription data, the data which is needed during service processing, to SSI. Together with SSIA it forms the administrative part of the external controltype interface (that is administration of service

3.16.10 SSINMIO

The block SSINMIO handles the TCP/IP connections between SCF and SMAS. The block is responsible for establishing and closing connections and transferring messages. These actions are initiated by commands.

3.16.11 SSINMOX

The block SSINMOX translates the incoming INM operations to actions on the SCF database.

3.16.12 SSIC1

SSIC1 contains the command interface for definition of service logic and service logic modules.

3.16.13 SSIC2

SSIC2 takes care of the printing commands for service logic and the removal of service logic. It is responsible for service logic registration and access.

3.16.14 SSIC3

SSIC3 contains the commands to define, connect, remove and print serv-ice administrators. It also holds some of the minor administrative com-mands for service administrators. Administration for service

administrators is implemented here as well, for instance, registration of references to service administrators from other parts of the database.

3.16.15 SSIC4

SSIC4 contains the commands for definition and printing of service data.

It is responsible for the administration of global service data modules.

3.16.16 SSIC5

SSIC5 contains the commands to define, remove and print service custom-ers. Administration for service customers is implemented here as well, for instance, registration of references to service customers from other parts of the database and registration of the service customers.

3.16.17 SSIC6

SSIC6 contains the commands for definition, removal and printing of serv-ice data connections as well as the commands for manual setting of servserv-ice data modules.

3.16.18 SSSTR

SSSTR contains the report controltypes. Also the timequeue function for periodic reports and the interface to SSOUT are located in SSSTR.

3.16.19 SSNAX

SSNAX contains the extended number analysis controltype and the analy-sis tables.

3.16.20 SSOUT

SSOUT handles the requests for output to file or printer from SSSTR, SSSTC and SSCC. It will generate an alarm if a fault occurs during output handling or if buffer congestion occurs in one of its users.

3.16.21 SSPRINT

Requests for output to a printer are handed over to SSPRINT. SSPRINT takes care of the printout formatting and printing.

3.16.22 SSSTC

SSSTC contains the actual controltypes which are subscribed by SSSTCA.

Also the timequeue function for periodic statistic reports and the interface to SSOUT are located in SSSTC.

3.16.23 SSSTCA

SSSTCA contains the subscription interface for the statistic controltypes.

3.16.24 SSCC1

SSCC1 contains the traffic part of the Service Script Customer Control function. Customer Control covers the facilities to offer a subscriber the possibility to enable or disable a service and to manipulate some part of its Service Data.

3.16.25 SSCC2

SSCC2 contains the administration of Change Code data modules and sub-scription of controltypes for customer control.

3.16.26 SCFSM

SCFSM is the Session Manager, which handles the processes in the SCF.

This means that it manages the relation between (multiple) dialogues and the service instance.

3.16.27 SCFDH

SCFDH is the Data Handler, which handles the conversion of data between the different formats used for protocol operations and internal SCF data.

3.16.28 SSIQ

SSIQ contains the queuing controltype and the data structures for storage of the queues.

3.16.29 SSINAP

SSINAP contains some controltypes used for sending INAP operations.

3.16.30 SSINAP2

SSINAP2 contains some internal controltypes used for sending INAP operations. The controltypes are: CHARLIM, RELCPC,

RECON, HOLDCPC, RELEASE, COLLECT, CANCEL, CALLINF, EXMON3,

CONTINU, and DIFCON.

3.16.31 SSCREAP

SSCREAP contains the controltype NPROCES and the related Call Instance Data. SSCREAP handles the external traffic functions of the con-troltype, mainly the administration of the order queue where the requested new processes are stored. The new process will be triggered by SSCREAP at the desired start time.

3.16.32 SSUPRT

SSUPRT handles the controltypes RETRIEV, UPDAT and DEFAPPL.

These controltypes are used to read data from and write data to an external database or SDF, comprising a more flexible way of defining read/write applications. The controltype DEFAPPL can be used for defining and maintaining applications and the format belonging to them.