This appendix is informative.
This appendix shows an example of the use of system sets. It illustrates the overall architecture of a typical application system that provides service management functionalities and how each component of the application system is specified in terms of system sets.
The objective of the application system described here is to provide customers with diverse network services in a consistent way, in a shorter time, and at less cost. To meet this objective, the application system provides service management functionalities common to network services.
The example application system consists of five types of element as
Note that more than one Network Service Support, Management Terminal and Network Service Controller can be included in a system depending on the type of network service.
Network Service Supports, Control Terminal, Gateway 1 and Gateway 2 are linked by an FDDI network using TCP/IP as the Lower Layer Protocols. Gateway 1 and Operation Terminals are also linked by leased lines using TCP/IP as the Lower Layer Protocols. In contrast, Gateway 2 and Network Service Controllers are linked by leased lines using the OSI Lower Layer Protocols. Operation Terminals use DCE to invoke procedures in Gateway 1, then they call procedures in Network Service Supports using TxRPC. Management Terminal uses SNMP to manage the FDDI network, including Network Service Supports, Gateway 1 and Gateway 2. Events from Network Service Controllers are sent to Gateway 2 using CMIP, then they are reported to Network Service Supports using SNMP. Protocol conversion is done at Gateway 2. Data necessary to operate Network Service Controllers is downloaded from Network Service Supports to Gateway 2 using FTP, then sent to Network Service Controllers using FTAM.
This section briefly explains which system sets are used for each element of the application system, then gives more detail of the system sets used for Network Service Supports. Finally, other information required to create a complete procurement specification is presented.
First, the choices of system sets made for each element are shown. Transactional Server and Manager were chosen as the system sets for Network Service Support to execute application programs in a transactional environment and receive SNMP events from Gateway 2. For Management Terminal, Manager was chosen as the system set to manage the FDDI network. Non-transactional Client system set was chosen for Operation Terminal, because it requires a human user interface for interaction with service operators but does not need transaction processing. Both Non-transactional Server and Manager system sets were chosen for Gateway 2 to send and receive CMIP/SNMP events and files.
Second, additions and removals of specifications made to the system sets for Network Service Supports are shown. To meet actual requirements, a few optional specifications were mandated and a few mandatory specifications were deleted, as listed below:
Agent profile using TCP/IP was added to make Network Service Supports manageable by Management Terminal.
All presentation services were removed because operators do not use Network Service Supports directly, but through Operation Terminals.
The FDDI component set was chosen as the Internet Transport and Lower Layer component set for the FDDI network.
COBOL was removed and C++ was added for developing this application system.
The transmission codeset for Japan was removed because this application system operates outside Japan.
Alphanumeric and ISO Latin 1 were chosen as coded character sets for the same reason as above.
Finally, the following additional requirements were included to complete the procurement specification for Network Service Supports: