asciidoc added
diff --git a/doc/FS/SUA Protocol Emulations for TTCN-3 Toolset with TITAN, FS.adoc b/doc/FS/SUA Protocol Emulations for TTCN-3 Toolset with TITAN, FS.adoc
new file mode 100644
index 0000000..4b71023
--- /dev/null
+++ b/doc/FS/SUA Protocol Emulations for TTCN-3 Toolset with TITAN, FS.adoc
@@ -0,0 +1,254 @@
+---
+Author: Máté Csorba
+Version: 155 17-CNL 113 517, Rev. A
+Date: 2007-01-16
+
+---
+= SUA Protocol Emulation for TTCN-3 Toolset with TITAN, Function Specification
+:author: Máté Csorba
+:revnumber: 155 17-CNL 113 517, Rev. A
+:revdate: 2007-01-16
+:toc:
+
+== How to Read This Document
+
+This is the Function Specification for the SUA Protocol Emulation (SUA PE). The SUA PE is developed for the TTCN-3 Toolset with TITAN according to the requirement specification <<_5, [5]>>.
+
+== Scope
+
+The purpose of this document is to specify the functionality of the SUA Protocol Emulation (PE). Basic knowledge in TTCN-3 is advantage but not required when reading this document (see <<_1, [1]>>).
+
+This specification is based on specifications of Signaling Connection Control Part User Adaptation Layer (SUA) defined by IETF <<_6, [6]>>.
+
+This document only describes the differences and the restrictions related to the above references, but does not repeat their content.
+
+= General
+
+The SUA protocol emulation (PE) implements the SUA protocol specified by IETF <<_6, [6]>>. The emulation is performed in TTCN-3 <<_1, [1]>> and it requires the TTCN-3 Test Tool with TITAN test executor <<_2, [2]>> as environment.
+
+The SUA PE is developed for testing implementations of SCCP Users using TTCN and it uses the services of the underlying SUA layer (see figure below). It is assumed that the SUA layer of the peer conforms to the same specifications as SUA PE does.
+
+See service primitives in SUA_PE below:name: value
+
+image:images/Service primitives in SUA_PE.PNG[alt]
+
+The SUA PE itself is situated between the SUA and the SCCP-User (see figure above). SCCP user can communicate using SCCP ASP service primitives.
+
+= Function Specification
+
+== Routing Functionality
+
+Routing functionality is not performed. SUA PE emulates a signaling endpoint.
+
+== Service Classes
+
+Service primitives are implemented as messages in the test ports.
+
+There are four service classes in SCCP (see 6/Q.711 and 2/T1.112.1-2001) as follows:
+
+* 0 - Basic connectionless class
+
+* 1 - In-sequence delivery connectionless class
+
+* 2 - Basic connection-oriented class
+
+* 3 - Flow control connection-oriented class.
+
+The SUA PE supports classes 0,1,2 but doesn’t support class 3.
+
+There is no difference between class 0 and 1 because only one test port is being used.
+
+== SCCP ASPs
+
+SUA service primitives are received and sent across service access points. See SCCP ASPs handled by SUA PE in the table below:
+
+"Not implemented" primitives are discarded by SUA PE.
+
+[cols=",",options="header",]
+|========================================
+|SCCP ASP |Implementation info
+|`N_CONNECT_res` |received from SUA user
+|`N_CONNECT_req` |received from SUA user
+|`N_DATA_req` |received from SUA user
+|`N_DISCONNECT_req` |received from SUA user
+|`N_UNITDATA_req` |received from SUA user
+|`N_RESET_req` |not implemented
+|`N_RESET_resp` |not implemented
+|`N_CONNECT_ind` |sent to SUA user
+|`N_CONNECT_cfm` |sent to SUA user
+|`N_DATA_ind` |sent to SUA user
+|`N_DISCONNECT_ind` |sent to SUA user
+|`N_UNITDATA_ind` |sent to SUA user
+|`N_NOTICE_ind` |sent to SUA user
+|`N_STATE_ind` |not implemented
+|`N_RESET_ind` |sent to SUA user
+|`N_RESET_cfm` |sent to SUA user
+|========================================
+
+== SUA Messages
+
+User data fields of SUA PDUs received by SUA PE are mapped to N-service primitives that will be sent to the SCCP User(s).
+
+An SUA message received may be mapped to an N-service primitive or may invoke an exception handling procedure based on the state of the SUA PE. The supported message types and the related mappings are summarized in the table below:
+
+[width="100%",cols=",,^.^,^.^",options="header",]
+|================================================================================================================================================
+|SUA message ID |Name of message |This message is not supported by SUA PE. |Message handled and relayed towards SCCP-User layer if needed
+|`SUA_ERR` |Error |*X* |
+|`SUA_NTFY` |Notify |*X* |
+|`SUA_DUNA` |Destination Unavailable |*X* |
+|`SUA_DAVA` |Destination Available |*X* |
+|`SUA_DAUD` |Destination State Audit |*X* |
+|`SUA_SCON` |Signalling Congestion |*X* |
+|`SUA_DUPU` |Destination User Part Unavailable |*X* |
+|`SUA_DRST` |Destination Restricted |*X* |
+|`SUA_ASPUP` |ASP up |*X* |
+|`SUA_ASPDN` |ASP down |*X* |
+|`SUA_BEAT` |Heartbeat |*X* |
+|`SUA_BEAT_Ack` |Heartbeat Ack |*X* |
+|`SUA_ASPUP_Ack` |ASP up ack |*X* |
+|`SUA_ASPDN_Ack` |ASP down ack |*X* |
+|`SUA_ASPAC` |ASP Active |*X* |
+|`SUA_ASPIA` |ASP Inactive |*X* |
+|`SUA_ASPAC_Ack` |ASP Active Ack |*X* |
+|`SUA_ASPIA_Ack` |ASP Inactive |*X* |
+|`SUA_CLDT` |Connectionless Data Transfer | |*X*
+|`SUA_CLDR` |Connectionless Data REsponse | |*X*
+|`SUA_CORE` |Connection Request | |*X*
+|`SUA_COAK` |Connection Acknowledge | |*X*
+|`SUA_COREF` |Connection Refused | |*X*
+|`SUA_RELRE` |Release Request | |*X*
+|`SUA_RELCO` |Release Confirm | |*X*
+|`SUA_RESCO` |Reset Confirm | |*X*
+|`SUA_RESRE` |Reset Request | |*X*
+|`SUA_CODT` |Connection Oriented Data Transfer | |*X*
+|`SUA_CODA` |Connection Oriented Data Transfer |*X* |
+|`SUA_COERR` |Connection Oriented Data Transfer | |*X*
+|`SUA_COIT` |Connection Oriented Data Transfer | |*X*
+|`SUA_REGREQ` |Registration Request |*X* |
+|`SUA_REGRSP` |Registration Response |*X* |
+|`SUA_DEREGREQ` |Deregistration Request |*X* |
+|`SUA_DEREGRSP` |Deregistration Response |*X* |
+|================================================================================================================================================
+
+This table describes the types of messages SUA PE accepts from the lower layer. Details of SUA message translation into SCCP N-ASPs can be found in <<_6, [6]>>.
+
+== SCCP Primitives of the Connectionless Service
+
+SCCP can provide 2 classes of connectionless services (0 and 1) but there is no difference between them in this implementation (see 6/Q.711 and 2/T1.112.1-2001).
+
+The primitives to the upper layers and the corresponding parameters for connectionless service are implemented as follows:
+
+See primitives and their mappings for Connectionless Service below:
+
+[cols=",,",options="header",]
+|=============================================
+|Generic name |ASP name |Message mapping
+|N-UNITDATA |`N_UNITDATA_req` |send SUA CLDT
+|N-NOTICE |`N_NOTICE_ind` |SUA CLDR received
+|=============================================
+
+== SCCP Primitives for Connection-Oriented Services
+
+ See network service primitives and mapping for connection-oriented services below:
+
+[cols=",,",options="header",]
+|==============================================
+|Generic Name |ASP name |Message mapping
+|N-CONNECT |`N_CONNECT_req` |send SUA CORE
+|N-DATA |`N_DATA_req` |send SUA CODT
+|N-DISCONNECT |`N_DISCONNECT_req` |send SUA COREF
+|N-RESET |`N_RESET_ind` |SUA RESRE received
+|==============================================
+
+[[SUA_management_functionality]]
+== SUA Management Functionality
+
+SUA management functionality is implemented in the SUA Test Port. However, support for connection-oriented transfer is enabled by SUA PE by handling SUA CORE, COAK, COREF, RELRE, RELCO, RESCO, RESRE, COERR and COIT messages.
+
+== Message Sequence Control
+
+SUA PE maintains the order of messages between the upper and lower layer interfaces.
+
+== Flow Control
+
+Not supported by SUA PE.
+
+== Segmentation and Reassembly
+
+Segmentation is supported in as much as data received from the SCCP User layer can be transferred in SUA CODT messages using segmentation. Maximum allowed transfer message size can be altered using the module parameter `tsp_SUA_data_maxlen`, which is taken into account when transferring `N-DATA_req` messages. Also, incoming CODT messages are checked for segmentation and a receiving buffer is used if needed.
+
+== State Machine
+
+SUA PE maintains a state machine behavior for each connection-oriented services according to Figure 8/Q.711.
+
+== Global Title Translation
+
+Not supported.
+
+== Capacity and Limitation
+
+Few parameters are hardcoded in SUA PE implementation, here is the list of them:
+
+[width="100%",cols=",,",options="header",]
+|=====================================================================================================================================
+|*Feature* |*Restriction* |*Remark*
+|Fields `<translation type>`, `<numbering plan>` and `<nature of address>` |= 0 (unknown), if not specified otherwise |See 3.10.2.3. in <<_6, [6]>>
+|Management |Partially implemented |See <<SUA_management_functionality, SUA Management Functionality>> in this document
+|Field `<encoding scheme>` in a N-SCCP ASP Global Title |`= 1 or 2` |`1 if (<number of digits> mod 2 == 1), 2 otherwise`
+|Service class 3 |NOT IMPLEMENTED |
+|Routing |NOT IMPLEMENTED |SUA PE is a signaling endpoint
+|Message sequence control |NOT IMPLEMENTED |Indifferent
+|Flow control |NOT IMPLEMENTED |Because class 3 not supported
+|Global title translation |NOT IMPLEMENTED |
+|=====================================================================================================================================
+
+There shall be exactly one SCCP User test component instance for each SUA PE instance. An SUA PE instance is able to handle up to 16 SUA connections and 16 segmented N-UNITDATA messages at the same time.
+
+= Terminology
+
+*Protocol Emulation:* +
+An instance which implements messages and dynamic behavior of a given protocol layer.
+
+= Abbreviations
+
+ASP:: Abstract Service Primitive
+
+IETF:: Internet Engineering Task Force
+
+IUT:: Implementation Under Test
+
+PDU:: Protocol Data Unit
+
+PE:: Protocol Emulation
+
+SCCP:: Signalling Connection Control Part
+
+SUA:: SCCP User Adaptation Layer
+
+SUA PE:: SUA Protocol Emulation
+
+SS7:: Signalling System No 7
+
+TTCN-3:: Testing and Test Control Notation version 3.
+
+= References
+
+[[_1]]
+[1] ETSI ES 201 873-1 v2.2.1 (02/2003)The Testing and Test Control Notation version 3. Part 1: Core Language
+
+[[_2]]
+[2] User Guide for TITAN TTCN-3 Test Executor
+
+[[_3]]
+[3] Programmer´s Technical Reference for TITAN TTCN-3 Test Executor
+
+[[_4]]
+[4] Installation Guide for TITAN TTCN-3 Test Executor
+
+[[_5]]
+[5] TTCNv3 Requirement Specification for MSC R13
+
+[[_6]]
+[6] http://www.ietf.org/rfc/rfc3868.txt?number=3868[RFC 3868] +
+Signaling Connection Control Part User Adaptation Layer (SUA)
diff --git a/doc/FS/SUA Protocol Emulations for TTCN-3 Toolset with TITAN, FS.pdf b/doc/FS/SUA Protocol Emulations for TTCN-3 Toolset with TITAN, FS.pdf
new file mode 100644
index 0000000..89968af
--- /dev/null
+++ b/doc/FS/SUA Protocol Emulations for TTCN-3 Toolset with TITAN, FS.pdf
Binary files differ
diff --git a/doc/FS/images/Service primitives in SUA_PE.PNG b/doc/FS/images/Service primitives in SUA_PE.PNG
new file mode 100644
index 0000000..5ca7f87
--- /dev/null
+++ b/doc/FS/images/Service primitives in SUA_PE.PNG
Binary files differ
diff --git a/doc/SUA_CNL113517_FS.pdf b/doc/SUA_CNL113517_FS.pdf
deleted file mode 100644
index ef200f3..0000000
--- a/doc/SUA_CNL113517_FS.pdf
+++ /dev/null
Binary files differ
diff --git a/doc/SUA_CNL113517_UG.pdf b/doc/SUA_CNL113517_UG.pdf
deleted file mode 100644
index 9458c56..0000000
--- a/doc/SUA_CNL113517_UG.pdf
+++ /dev/null
Binary files differ
diff --git a/doc/UG/SUA Protocol Emulations for TTCN-3 Toolset with TITAN, UG.adoc b/doc/UG/SUA Protocol Emulations for TTCN-3 Toolset with TITAN, UG.adoc
new file mode 100644
index 0000000..95d8416
--- /dev/null
+++ b/doc/UG/SUA Protocol Emulations for TTCN-3 Toolset with TITAN, UG.adoc
@@ -0,0 +1,304 @@
+---
+Author: Máté Csorba
+Version: 198 17-CNL 113 517, Rev. A
+Date: 2007-01-16
+
+---
+= SUA Protocol Emulation for TTCN-3 Toolset with TITAN, User Guide
+:author: Máté Csorba
+:revnumber: 198 17-CNL 113 517, Rev. A
+:revdate: 2007-01-16
+:toc:
+
+== About This Document
+
+=== How to Read This Document
+
+This is the User Guide for the SUA Protocol Emulation (SUA PE). The SUA PE is developed for the TTCN-3 Toolset with TITAN according to the Requirement Specification <<_5, [5]>>. This document should to be read together with Function Specification <<_6, [6]>>.
+
+=== Presumed Knowledge
+
+The knowledge of the TITAN TTCN-3 Test Executor <<_2, [2]>> and the TTCN-3 language <<_1, [1]>> is essential.
+
+== System Requirements
+
+In order to operate the SUA PE the following system requirements must be satisfied:
+
+* The operation system shall be Sun Solaris 8.
+
+= The Protocol Emulation
+
+== Overview
+
+The SUA PE is developed for testing implementations of SCCP Users using TTCN-3 and it uses the services of the underlying SUA layer. It is assumed that the SCCP layer of the peer conforms to the same specifications as SUA PE does.
+
+See service primitives in SS7 below:
+
+image:images/Service primitives in SS7.PNG[alt]
+
+Generally, SUA PE is designed to supply the same interfaces and services for the SCCP user layer as in the previous product SCCP PE.
+
+== The User Interface: the N-Service Primitives
+
+SUA PE communicates with its user by means of N-Service primitives.
+
+These primitives are implemented as TTCN-3 records. Any SCCP User inserts its message in the field `"User Data"`. Their implementation can be found in file __SCCPasp_Types.ttcn__.
+
+== Installation
+
+Since SUA PE is used as a part of the TTCN-3 test environment this requires TTCN-3 Test Executor to be installed before any operation of the implementation. For more details on the installation of TTCN-3 Test Executor see <<_4, [4]>>.
+
+An implementation of the SUA test port is also needed for execution.
+
+=== Description of Files Implementing the SUA PE
+
+The SUA PE is implemented in the file __SUA_Emulation.ttcn__
+
+To build an executable test suite with TITAN <<_2, [2]>> that is using SUA PE the following files from other products shall be added to the related project:
+
+* __General_Types.ttcn__
+* __SCCPasp_Types.ttcn__
+* __SUA_EncDec.ccSUA_Types.ttcnSUAasp_EncDec.cc__
+* __SUAasp_PortType.ttcn__
+* __SUAasp_PT.cc__
+* __SUAasp_PT.hh__
+* __SUAasp_Types.ttcn__
+
+Their functionality is the following:
+
+* __Abstract_Socket.*__ - This is the implementation of the Abstract_Socket (CNL 113 384).
+
+* __General_Types.ttcn__ - General type definitions (CNL 113 368).
+
+* __SCCPasp_Types.ttcn__ - This file contains the interface between the SUA PE and the SCCP User. It contains the abstract service primitives implemented as TTCN-3 messages, templates and it contains the port definitions between the SCCP User and SUA.
+
+* __SUA_Emulation.ttcn__ - This file contains the dynamical part.
+
+* __SUA_EncDec.cc__ - This file contains functions for RAW encoding-decoding. For details see [*Error! Bookmark not defined.*].
+
+* __SUA_Types.ttcn__ - This file contains all other definitions used in SUA PE. It contains definitions of types, ports used between components SUA and SUA_EncDec and between SUA_EncDec and the IP layer.
+
+* __SUAasp_EncDec.cc__, __SUAasp_PT.cc__, __SUAasp_PT.hh__, __SUAasp_Types.ttcn__, __SUAasp_PortType.ttcn__ - These files contain the implementation of the lower SUA layer of the PE. Including test port, type definitions and port type definition (CNL 113 516).
+
+== Configuration
+
+The SUA PE uses module parameters for runtime configuration that can be set in the `[MODULE_PARAMETERS]` section of a TITAN RTE configuration file. On one hand side a few user configurable module parameters are defined, while on the other hand side there are a few timer settings that are not advised to be altered by the user.
+
+A list of configurable parameters is provided below.
+
+* `tsp_maxLocalReference`:
++
+Type: float
++
+Meaning: Max value of the field `Local Reference` .Local Reference = `0 .. (SUA.tsp_maxLocalReference-1)`.
++
+Possible values: `_0-16777216_`
++
+Default value: `_16777216.0_`
++
+OPTIONAL
+
+* `tsp_maxConnectionId`:
++
+Type:float
++
+Meaning: max value of ASP field `Connection Identification`. More exactly Connection Identification `=0.. (SCCP.tsp_maxConnectionId –1)`.
++
+Possible values: `_0-16777216_`
++
+Default value: `_16777216.0_`
++
+OPTIONAL
+
+* `tsp_SUA_data_maxlen`:
++
+Type: integer
++
+Meaning: On one hand the data reassembler buffer’s size for each connection is determined as 16 times this value, and on the other hand buffered transmission of user layer data is performed taking this setting into account.
++
+Possible values: any integer
++
+Default value: `_261_`
++
+OPTIONAL
+
+* `tsp_SSN` :
++
+Type: integer
++
+Meaning: If present, it is used in the examination of SUA CLDT message payload content.
++
+Possible values:= `_8..1532_`
++
+Default value: `_0_`
++
+OPTIONAL
+
+The additional parameters are used for the configuration of internal timers. Modification of their values is not recommended. The list of timer parameters follows:
+
+* `tspc_timer_T_conn_est`
+* `tspc_timer_T_ias`
+* `tspc_timer_T_iar`
+* `tspc_timer_T_rel`
+* `tspc_timer_T_repeat_rel`
+* `tspc_timer_T_int`
+* `tspc_timer_T_guard`
+* `tspc_timer_T_reset`
+* `tspc_timer_T_internal_reset`
+* `tspc_timer_guard`
+
+= Error Messages
+
+`*ERROR: Routing context was not received after map operation!*`
+
+The test port used by SUA PE should send the Routing Context associated with the instance and set in the runtime configuration file immediately after the map operation was issued. Check is the parameter is set correctly in the configuration file.
+
+= Warning Messages
+
+`*WARNING: maximum allowed buffer length exceeded!*`
+
+The maximum allowed reassembly buffer length has been exceeded during the assembly of a SUA CODT message. Try setting the parameter `tsp_SUA_data_maxlen`.
+
+`*WARNING: N-CONNECTres ASP received without a connection Id param.!*`
+
+For successful connection establishment in SUA PE the `N-CONNECTresp` primitive must convey a connection Id field.
+
+`*WARNING: N-DISCONNECT_req ASP received without a connection Id param.!*`
+
+For successful disconnection in SUA PE the `N-CONNECTresp` primitive must convey a connection Id field.
+
+= Examples
+
+This is a simple example configuration file for testing. The relevant information can be found under the sections `TESTPORT_PARAMETERS` and `MODULE_PARAMETERS`.
+
+[source]
+----
+[LOGGING]
+FileMask := LOG_ALL | TTCN_DEBUG | TTCN_MATCHING
+ConsoleMask := TTCN_WARNING | TTCN_ERROR | TTCN_TESTCASE | TTCN_PORTEVENT
+LogSourceInfo := Yes
+
+[TESTPORT_PARAMETERS]
+system.*.Hostname := "rhea.eth.ericsson.se" // SEA server name
+system.*.DestinationName := "testtest"
+system.*.HttpPort := "5000" // SEA http port
+system.*.SUAServiceType := "TargetSUA"
+system.*.TesterAPC := "1"
+system.*.EntityName := "SCTP-10.2.112.34:14001-10.2.112.32:14001" // SEA Entity
+system.*.RoutingContext0 := "1111"
+system.*.RoutingContext1 := "2222"
+system.*.RoutingContext2 := "3333"
+system.*.RoutingContext3 := "4444"
+
+// required for Target testing
+// location of SUA Server component
+system.*.socket_debugging := "yes"
+system.*.SUAtarget_TCP_IPAddr := "159.107.197.130"
+system.*.SUAtarget_TCP_Port := "17705"
+
+[MODULE_PARAMETERS]
+tsp_maxLocalReference := 16777216.0; //loc ref= 0...tsp_maxLocalReference-1
+tsp_max_ConnectionId := 16777216.0; //max connection id = 0..tsp_max_ConnectionId -1
+tsp_SUA_data_maxlen := 261;
+tsp_SSN := 0;
+
+tspc_timer_T_conn_est:=120.0;
+ //Delay to send a message on a conn IT on a
+ //connection section when there are no
+ //messages to send
+ //5 to 10 minutes
+
+tspc_timer_T_ias:=600.0;
+ //Waiting to receive a message on a connection
+ //section
+ //11 to 21 minutes
+
+tspc_timer_T_iar:=1260.0; //Waiting for release complete message -10 to 20 seconds
+
+tspc_timer_T_rel:=20.0;
+ //Waiting for release complete message; or to
+ //repeat sending released message after the
+ //initial T(rel) expiry
+ //10 to 20 seconds
+
+tspc_timer_T_repeat_rel:=20.0;
+ //Waiting for release complete message; or to
+ //release connection resources, freeze the LRN
+ //and alert a maintenance function after the
+ //initial T(rel) expiry
+ //extending to 1 minute
+
+tspc_timer_T_int:=60.0;
+ //Waiting to resume normal procedure for
+ //temporary connection sections during the
+ //restart procedure
+ //23 to 25 minutes
+
+tspc_timer_T_guard:=1500.0;
+ //Waiting to release temporary connection
+ //section or alert maintenance function after
+ //reset request message is sent
+ //10 to 20 seconds
+
+tspc_timer_T_reset:=20.0;
+ //Waiting to receive all the segments of the
+ //remaining segments single segmented
+ //message after receiving the first segment
+ //10 to 20 seconds
+
+tspc_timer_T_internal_reset:=0.0; //zero-only for sending internal signals!!
+tspc_timer_guard :=120.0 //the same as tspc_timer_T_conn_est:1 or 2 minutes
+
+[MAIN_CONTROLLER]
+TCPPort := 7000
+NumHCs := 1
+----
+
+= Terminology
+
+*SUA Protocol Emulation:* +
+Implementation of SUA as specified in <<_6, [6]>>.
+
+*SCCP User:* +
+Protocol that uses services of SCCP.
+
+= Abbreviations
+
+ASP:: Abstract Service Primitive
+
+PE:: Protocol Emulation
+
+SCCP:: Signalling Connection Control Part
+
+SUA:: SCCP User Adaptation Layer
+
+SUA PE:: SUA Protocol Emulation
+
+SS7:: Signalling System No 7
+
+TTCN-3:: Testing and Test Control Notation version 3.
+
+= References
+
+[[_1]]
+[1] ETSI ES 201 873-1 V2.2.1 +
+The Testing and Test Control Notation version 3. Part 1: Core Language
+
+[[_2]]
+[2] User Guide for TITAN TTCN-3 Test Executor
+
+[[_3]]
+[3] Programmer´s Technical Reference for TITAN TTCN-3 Test Executor
+
+[[_4]]
+[4] Installation Guide for TITAN TTCN-3 Test Executor
+
+[[_5]]
+[5] TTCNv3 Requirement Specification for MSC R13
+
+[[_6]]
+[6] SUA Protocol Emulation for TTCN-3 Toolset, Function Specification
+
+[[_7]]
+[7] http://www.ietf.org/rfc/rfc3868.txt?number=3868[RFC 3868] +
+Signaling Connection Control Part User Adaptation Layer (SUA)
diff --git a/doc/UG/SUA Protocol Emulations for TTCN-3 Toolset with TITAN, UG.pdf b/doc/UG/SUA Protocol Emulations for TTCN-3 Toolset with TITAN, UG.pdf
new file mode 100644
index 0000000..f610198
--- /dev/null
+++ b/doc/UG/SUA Protocol Emulations for TTCN-3 Toolset with TITAN, UG.pdf
Binary files differ
diff --git a/doc/UG/images/Service primitives in SS7.PNG b/doc/UG/images/Service primitives in SS7.PNG
new file mode 100644
index 0000000..a5dd255
--- /dev/null
+++ b/doc/UG/images/Service primitives in SS7.PNG
Binary files differ
diff --git a/doc/change.log b/doc/change.log
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/doc/change.log
