| draft-hou-sigtran-tua-00 Description: Request For Comments
You can download source copies of the file as follows:
Listed below is the contents of file draft-hou-sigtran-tua-00.txt.
TERNET-DRAFT Jianxing Hou
Internet Engineering Task Force Ming Lin
Huawei Technologies
Issued: 1 April 2001
Expires: 1 October 2001
SS7 TCAP-User Adaptation Layer (TUA)
<draft-hou-sigtran-tua-00.txt>
Status of This Memo
This document is in full conformance with all provisions of Section
10 of RFC 2026.Internet-Drafts are working ocuments of the Internet
Engineering Task Force (IETF), its areas,and its working groups.
Note that other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as 'work in progress.'
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
To learn the current status of any Internet-Draft, please check the
'1id-abstracts.txt' listing contained in the Internet- Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or
ftp.isi.edu (US West Coast).
Abstract
This document defines a protocol for the transport of any SS7
TCAP-User signaling (e.g.,INAP,MAP , etc.) over IP using the
Stream Control Transport Protocol. The protocol should be
modular and symmetric, to allow it to work in diverse
architectures, such as a Signaling Gateway to IP Signaling
Endpoint architecture . Protocol elements are added to allow
seamless operation between peers in the SS7 and IP domains.
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
Abstract.............................................................1
1. Introduction......................................................2
1.1 Scope...........................................................3
1.2 Terminology.....................................................3
1.3 Signaling Transport Architecture................................5
1.4 Services Provided by the TUA Layer.............................10
1.5 Internal Functions Provided in the TUA Layer...................10
1.6 Definition of TUA Boundaries...................................12
2. Conventions......................................................14
3. Protocol Elements................................................14
3.1 Common Message Header..........................................15
3.2 TUA Message Header............................................18
3.3 Dialogue Handling(DH)Message..................................18
3.4 Component Handling(CH) Message.................................26
3.5 SS7 Signaling Network Management Messages......................31
3.6 Application Server Process Maintenance Messages................34
3.7 ASP Traffic Maintenance Messages...............................36
3.8 Management Messages............................................39
3.9 SGP Traffic Maintenance (SGPTM) Messages.......................40
3.10 Common Parameters.............................................40
3.11 TUA-Specific parameters.......................................50
4. Procedures.......................................................62
4.1 TCAP _ TUA Interworking at the SG..............................62
4.2 Primitives received from the local TUA-User....................63
4.3 Layer Management Procedures....................................63
4.4 TUA Management Procedures......................................64
5. Examples of TUA Procedures.......................................74
5.1 Establishment of Association and Traffic between SGPs and ASPs.74
5.2 IP-IP Architecture.............................................79
6. Security.........................................................81
6.1 Introduction...................................................81
6.2 Threats........................................................81
6.3 Protecting Confidentiality.....................................82
7. IANA Considerations..............................................82
7.1 SCTP Payload Protocol ID.......................................82
7.2 Protocol Extensions............................................82
8. Timer Values.....................................................83
9. Acknowledgements.................................................83
10. Authors' Addresses..............................................83
11. References......................................................84
Jianxing Hou, et al [Page 2]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
1. Introduction
1.1 Scope
There is on-going integration of SCN networks and IP networks.
Network service providers are designing all IP architectures which
include support for SS7 and SS7-like signaling protocols. IP provides
an effective way to transport user data and for operators to expand
their networks and build new services. In these networks, there may
be some need for interworking between the SS7 and IP domains.
This document details the delivery of TCAP-user messages and new third
generation network protocol messages over IP between two signaling
endpoints.Consideration is given for the transport from an SS7
Signaling Gateway (SG) to an IP signaling node (such as an IP-resident
Database) as described in the Framework Architecture for Signaling
Transport [2719].
The delivery mechanism SHOULD meet the following criteria:
* Support for transfer of SS7 TCAP-User Part messages (e.g.,INAP,
MAP, etc.)
* Support for the seamless operation of TCAP-User protocol peers
* Support for the management of SCTP transport associations between
a SG and one or more IP-based signaling nodes.
* Support for distributed IP-based signaling nodes.
* Support for the asynchronous reporting of status changes to
management
The protocol is modular in design,allowing different implementations
to be made, based upon the environment that needs to be supported.
1.2 Terminology
Signaling Gateway (SG) - Network element that terminates SCN signaling
and transports TCAP-User signaling over IP to an IP signaling endpoint.
Signalling Gateway Process (SGP) - A process instance of a Signalling
Gateway. It serves as an active, standby or load-sharing process of a
Signalling Gateway.
Application Server (AS) - A logical entity serving a specific Routing
Key.An example of an Application Server is a virtual IP database
element handling all request for a TCAP-user. The AS contains a set
of one or more unique Application Server Processes,of which one or more
is normally actively processing traffic.
Jianxing Hou, et al [Page 3]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
Application Server Process (ASP) - An Application Server Process serves
as an active or standby process of an Application Server(e.g., part of
a distributed signaling node or database element). Examples of ASPs are
MGCs,IP SCPs, or IP-based HLRs. An ASP contains an SCTP end-point and
may be configured to process traffic within more than one Application
Server.
Association - An association refers to an SCTP association. The
association provides the transport for the delivery of TCAP-User
protocol data units and TUA adaptation layer peer messages.
Routing Key - The Routing Key describes a set of SS7 parameter and/or
parameter-ranges that uniquely defines the range of signaling traffic
configured to be handled by a particular Application Server.An example
would be where a Routing Key consists of a TCAP DID and SCCP SSN for
which all traffic would be directed to a particular Application Server.
Routing Keys are mutually exclusive in the sense that a received SS7
signaling message cannot be directed to more than one Routing Key. In
the case of TUA, the Routing Key should be limited to TCAP SSN or a
combination of TCAP DID and SCCP SSN to identify an AS,in order to more
easily support TCAP management procedures.
Routing Context - An Application Server Process may be configured to
process traffic within more than one Application Server.In this case,
the Routing Context parameter is exchanged between two ASPs,identifying
the relevant Application Server. From the perspective of an ASP, the
Routing Context uniquely identifies the range of traffic associated
with a particular Application Server, which the ASP is configured to
receive.There is a 1:1 relationship between a Routing Context value and
a Routing Key within an AS. Therefore the Routing Context can be viewed
as an index into an AS Table containing the AS Routing Keys.
Fail-over - The capability to re-route signaling traffic as required to
an alternate Application Server Process, or group of ASPs, within an
Application Server in the event of failure or unavailability of a
currently used Application Server Process. Fail-back may apply upon the
return to service of a previously unavailable Application Server
Process.
Network Appearance - The Network Appearance identifies protocol's type
(ITU or ANSI ect)an SS7 network context (network ID) for the purposes
of logically separating the signaling traffic between the SG and the
Application Server Processes over a common SCTP Association. This
partitioning is necessary where an SG is logically partitioned to
appear as an end-node elements in multiple separate national SS7
networks, in which case there is a separate network appearance for each
Jianxing Hou, et al [Page 4]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
SS7 network. It is also necessary when an SG is configured as an STP
and hosts multiple point codes within the same network,in which case
each point code is a separate network appearance.
Network Byte Order - Most significant byte first, a.k.a. Big Endian.
Layer Management - Layer Management is a nodal function in an SG or ASP
that handles the inputs and outputs between the TUA layer and a local
management entity.
Host - The computing platform that the ASP process is running on.
Stream - A stream refers to an SCTP stream; a uni-directional logical
channel established from one SCTP endpoint to another associated SCTP
endpoint,within which all user messages are delivered in-sequence
except for those submitted to the un-ordered delivery service.
Transport address - an address which serves as a source or destination
for the unreliable packet transport service used by SCTP. In IP
networks, a transport address is defined by the combination of an IP
address and an SCTP port number. Note, only one SCTP port may be
defined for each endpoint, but each SCTP endpoint may have multiple IP
addresses.
1.3 Signaling Transport Architecture
The framework architecture that has been defined for SCN signaling
transport over IP [2719] uses multiple components, including an IP
transport protocol,a signaling common transport protocol and an
adaptation module to support the services expected by a particular SCN
signaling protocol from its underlying protocol layer.
1.3.1 Protocol Architecture
In this architecture, the TCAP and TUA layers interface in the SG.
There needs to be interworking between the TCAP and TUA layers to
provide for the seamless transfer of the user messages as well as
the management messages.
******** SS7 *************** IP ********
* SEP *---------* *--------* *
* or * * SG * * ASP *
* STP * * * * *
******** *************** ********
+------+ +------+
| TC_U | | TC_U |
Jianxing Hou, et al [Page 5]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
+------+ +------+------+ +------+
| TCAP | | TCAP | TUA | | TUA |
+------+ +------+------+ +------+
| SCCP | | SCCP | | | |
+------+ +------+ | | |
| MTP3 | | MTP3 | SCTP | | |
+------| +------+ | | SCTP |
| MTP2 | | MTP2 | | | |
+------+ +------+------+ +------+
| L1 | | L1 | IP | | IP |
+------+ +------+------+ +------+
| | | |
+---------------+ +------------+
TC_U - TCAP USER (e.g. - MAP/INAP)
STP - SS7 Signaling Transfer Point
In this case, the TCAP messages are routed on SSN or SSN+DID. The
TCAP-User identified by SSN or SSN+DID is regarded as local to the
SG. This means from SS7 point of view, the TCAP-user is located at
the SG.
By means of configuration, the SG knows the local TCAP-user is
actually representing an AS, serviced by a set of ASPs working in
n+k redundancy mode. An ASP is selected and a TCAP message is sent
on the appropriate SCTP association/stream.
Actually, the primitive interface between TCAP and TCAP-user is
transported here over TUA. An example for a INAP/MAP message
exchange between SEP and ASP is given below.
Address information in message from SG to ASP :
- Network appearance : based on SS7 network ID and Protocol Type,
- Source address : valid combination of SSN, PC and GT, as
needed for back-routing,
- Destination address : at least SSN , to select the
TCAP-user at the ASP.
The Network Appearance is needed if the SG operates in more than one
SS7 network or protocol type(ITU or ANSI,etc), since PC and SSN only
have meaning within a specific SS7 network. If SG receives a message
from SS7 network,it will determine which AS the message is sent to
(based on SSN or SSN+DID within the message),then it will select an
active ASP based on implementation,and select a Stream ID for the
message,and then the message can be sent to proper ASP.
Address information in message from ASP to SG :
Jianxing Hou, et al [Page 6]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
- Network appearance : as received in previous message,
- Source address : unique ASP address that when used as
SCCP called party address in the SEP, MUST yield the
same ASP again; the SSN could be sufficient,
- Destination address : copied from source address in received
and response message.
When ASP receives a message from TCAP-User,it will select a SGP
through TCAP DID based on implementation,then select a Stream ID to
the message,and then the message can be sended to SG.
1.3.2 All IP Architecture
This architecture can be used to carry a protocol which uses the
transport services of TCAP, but is contained with an IP network.
This allows extra flexibility in developing networks, especially
when interaction between legacy signaling is not needed. The
architecture removes the need for signaling gateway functionality.
******** IP ********
* *--------* *
* AS * * AS *
* * * *
******** ********
+------+ +------+
| AP | | AP |
+------+ +------+
| TUA | | TUA |
+------+ +------+
| SCTP | | SCTP |
+------+ +------+
| IP | | IP |
+------+ +------+
| |
+----------------+
AP - Application Protocol (e.g. - MAP/INAP)
The SCTP protocol takes care about the case where a collision occurs
during initiation.
1.3.3 Generalized Point-to-Point Network Architecture
Figure 1 shows an example network architecture which can support
robust operation and failover support. There needs to be some
management resources at the AS to manage traffic.
Jianxing Hou, et al [Page 7]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
***********
* AS1 *
* +-----+ * SCTP Associations
* |ASP1 +-------------------+
* +-----+ * | ***********
* * | * AS3 *
* +-----+ * | * +-----+ *
* |ASP2 +-----------------------------------------+ASP1 | *
* +-----+ * | * +-----+ *
* * | * *
* +-----+ * | * +-----+ *
* |ASP3 | * +--------------------------+ASP2 | *
* +-----+ * | | * +-----+ *
*********** | | ***********
| |
*********** | | ***********
* AS2 * | | * AS4 *
* +-----+ * | | * +-----+ *
* |ASP1 +--------------+ +---------------------+ASP1 | *
* +-----+ * * +-----+ *
* * * *
* +-----+ * * +-----+ *
* |ASP2 +-----------------------------------------+ASP1 | *
* +-----+ * * +-----+ *
* * ***********
* +-----+ *
* |ASP3 | *
* +-----+ *
* *
***********
Figure 1: Generalized Architecture
In this example, the Application Servers are shown residing within
one logical box, with ASPs located inside. In fact, an AS could be
distributed among several hosts. In such a scenario, the host
should share state as protection in the case of a failure.
Additionally, in a distributed system, one ASP could be registered
to more than one AS. This draft should not restrict such systems -
though such a case in not specified.
1.3.4 Generalized Signaling Gateway Network Architecture
When interworking between SS7 and IP domains is needed, the SG
acts as the gateway node between the SS7 network and the IP network.
Jianxing Hou, et al [Page 8]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
The SG will transport TCAP-user signaling traffic from the SS7
network to the IP-based signaling nodes(for example IP-resident
Databases). The Signaling Gateway can be considered as a group of
Application Servers with additional functionality to interface
towards an SS7 network.
The TUA protocol should be flexible enough to allow different
configurations and transport technology to allow the network operators
to meet their operation, management and performance requirements.
Figure 2 shows a possible realization of this architecture, with
Signaling Gateway functionality.
Signaling Gateway
************
* SG * AS1
* ******** * **************
* * *_*________________________________________* ******** *
* * * * _________* * ASP1 * *
* * SGP1 * * SCTP Associations | * ******** *
* * *_*______________________ | * *
* ******** * | | * ******** *
* * | | * * ASP2 * *
* * | | * ******** *
* * | | * . *
* * | | * . *
* * | | * . *
* ******** * | | * ************
* * *_*______________________|_______|
* * * * |
* * SGP2 * * SCTP Associations |
* * *_*___________ |
* * * * | | AS2
* ******** * | | **************
* * | |_________________* ******** *
* * |____________________________* * ASP1 * *
* * * ******** *
* * * *
************ * ******** *
* * ASP2 * *
* ******** *
* . *
* . *
* . *
**************
Figure 2: Signaling Gateway Architecture
Jianxing Hou, et al [Page 9]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
1.3.5 ASP Fail-over Model and Terminology
The TUA protocol supports ASP fail-over functions in order to support
a high availability of transaction processing capability.An Application
Server can be considered as a list of all ASPs configured/registered to
handle TCAP-user messages within a certain range of routing information,
known as a Routing Key. One or more ASPs in the list may normally be
active to handle traffic, while others may be inactive but available in
the event of failure or unavailability of the active ASP(s).
1.4 Services Provided by the TUA Layer
1.4.1 Support for the transport of TCAP-User Messages
The TUA needs to support the transfer of TCAP-user messages.The TUA
layer at the SG needs to seamlessly transport the user messages.
1.4.2 Native Management Functions
The TUA layer may provide management of the underlying SCTP layer to
ensure that transport is available according to the degree specified by
the TCAP-user application.
The TUA layer provides the capability to indicate errors associated
with the TUA-protocol messages and to provide notification to local
management and the remote peer as is necessary.
1.4.3 Support for passing the SCCP management message
The TUA layer should provide passing transparently availability and
non-availability of SCCP (local or remote) between the SCN network and
the IP network. (see ITU-T Q.771 chap 2.2.3) It should:
-Provide an indication to the TCAP-user at an ASP that a remote SS7
endpoint/peer is unreachable.
-Provide an indication to the TCAP-user at an ASP that a remote SS7
endpoint/peer is reachable.
-Provide congestion indication to TCAP-user at an ASP.
1.5 Internal Functions Provided in the TUA Layer
1.5.1 Address Translation and Mapping at the SG
The SG MUST provide address translation and mapping functions to
direct messages received from the SS7 network to the appropriate IP
Jianxing Hou, et al [Page 10]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
destination.
In order to support message distribution,the SG maintains an address
translation table, which maps the incoming SS7 messages to the
appropriate AS. The relevant fields of the incoming SS7 message is
compared to the existing Routing Keys. The Routing Keys reference an
Application Server,which will have one or more ASPs processing traffic
for the AS. The availability and status of the ASPs is handled by TUA
ASP management messages.
Possible SS7 address/routing information that comprise a Routing Key
entry includes, for example,SCCP subsystem number, or TCAP transaction
ID. Some possibilities include:
SSN
SSN+TCAP DID
An Application Server maintains a list of ASPs that are available to
process the traffic. The list is dynamic, based upon the availability
of the individual ASPs in the list.TUA ASP management messages are used
to convey the status of these ASPs and their availability in failover
situations.
Normally, one or more ASPs is active in the ASP (i.e., currently
processing traffic) but in certain failure and transition cases it is
possible that there may not be an active ASP available.Both
load-sharing and backup scenarios are supported.
If there is no Routing Key match for an incoming SS7 message, a
default treatment MUST be specified. Possible solutions are to provide
a default Application Server to direct all unallocated traffic to a
(set of) default ASP(s), or to drop the messages and provide a
notification to management.The treatment of unallocated traffic is
implementation dependent.
1.5.2 Address Translation and Mapping at the ASP
In order to direct messages to the SS7 network, the ASP must choose
the proper SGP for a given message. This is accomplished by observing
SGP availability and is implementation dependent.
A remote Signaling Gateway may be composed of one or more SGPs that
are capable of routing SS7 traffic.As is the case with ASPs, a dynamic
list of SGPs in an SG can be maintained, taking into account the
availability status of the individual SGPs, configuration changes and
fail-over mechanisms. There is, however, no TUA messaging to manage the
status of an SGP. Whenever an SCTP association to an SGP exists, it is
assumed to be available. Also, every SGP of one SG communicating with
one ASP regarding one AS provides identical SS7 connectivity to this
ASP.
Jianxing Hou, et al [Page 11]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
1.5.3 SCTP Stream Mapping
The TUA supports SCTP streams. The SG/AS needs to maintain a list of
SCTP and TUA-users for mapping purposes.TCAP-users requiring sequenced
message transfer need to be sent over a stream supporting sequenced
delivery.
TUA MUST use stream 0 for TUA management messages. It is recommended
that sequenced delivery be in order to preserve the order of management
message delivery.
1.5.4 TCAP DID Mapping
Because Both TCAP and TCAP-User can assign DID independently,it is
possible that TCAP and TCAP-User assign same value to different
message at the same time, but it brings some problems. To solve this
problem, TUA need support TCAP DID mapping. The TUA needs to maintain
a list of incoming message's DID and outgoing message's DID for
mapping purposes.The solution in more details will be lodged via
discussion.
1.6 Definition of TUA Boundaries
1.6.1 Definition of the upper boundary
The following primitives are supported between the TUA and an
TCAP-user (a reference to ITU and ANSI sections where these primitives
and corresponding parameters are described, is also given).
1.6.1.1 Primitives for ITU
Name | Type | Reference (ITU) | TUA Message
----------------------------------------------------------------------
TC-UNI | Request | ITU-Q.711 chap3.1.2.2.1 |Unidirectional
|Indication | |
----------------------------------------------------------------------
TC-BEGIN | Request |ITU-Q.711 chap3.1.2.2.2.1 | Query
|Indication | |
----------------------------------------------------------------------
TC-CONTINUE | Request | ITU-Q.711 chap3.1.2.2.2.2| Conversation
| Indication | ITU-Q.711 chap3.1.2.2.2.3|
----------------------------------------------------------------------
TC-END | Request | ITU-Q.711 chap3.1.2.2.2.4| End
|Indication | |
----------------------------------------------------------------------
TC-U-ABORT | Request | ITU-Q.711chap3.1.2.2.2.4 | U-Abort
|Indication | |
----------------------------------------------------------------------
TC-P-ABORT |Indication | ITU-Q.711 chap3.1.4.2 | P_Abort
Jianxing Hou, et al [Page 12]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
---------------------------------------------------------------------
TC-NOTICE | Indication | ITU-Q.711 chap3.1.2.2.3 | Notice
----------------------------------------------------------------------
TC_INVOKE | Request | ITU-Q.711 chap3.1.3.2 | Invoke
| Incation | |
----------------------------------------------------------------------
TC_RESULT_L | Request | ITU-Q.711 chap3.1.3.3 | Result
---------------| | |
TC_RESULT_NL | Indication | |
----------------------------------------------------------------------
TC_U-ERROR | Request | ITU-Q.711 chap3.1.3.4 | U_Error
|Indication | |
----------------------------------------------------------------------
TC_U_REJECT | Request | ITU-Q.711 chap3.1.3.5 |
|Indication | |
----------------------------| |
TC_L_REJECT | Request | | Reject
|Indication | |
----------------------------| ITU-Q.711 chap3.1.4.1 |
TC_R_REJECT | Request | |
| Indication | |
----------------------------------------------------------------------
TC-U-CANCEL | Request | |
---------------| | ITU-Q.711 chap3.1.3.6 | Cancel
TC-L-CANCEL |Indication | |
----------------------------------------------------------------------
TC_TIMER_RESET | Request | ITU-Q.711 chap3.1.3.6 | Timer_Reset
----------------------------------------------------------------------
1.6.1.2 Messages for ANSI
TCAP Message | TUA Message
--------------------------------------------------------------------
Undirectional | Unidirectional
-------------------------------------------------------------------
Query with Permission |
--------------------------------| Query
Query without Permission |
--------------------------------------------------------------------
Conversation with Permission |
--------------------------------| Conversation
Conversation without Permission |
--------------------------------------------------------------------
Respone | End
--------------------------------------------------------------------
U_Abort | U_Abort
--------------------------------------------------------------------
Jianxing Hou, et al [Page 13]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
P_Abort | P_Abort
--------------------------------------------------------------------
Invoke Last |
--------------------------------| Invoke
Invoke Not Last |
--------------------------------------------------------------------
Return Result(Last) |
--------------------------------| Result
Return Result( Not Last) |
--------------------------------------------------------------------
Return Error | U_Error
--------------------------------------------------------------------
Reject | Reject
--------------------------------------------------------------------
1.6.2 Definition of the lower boundary
The upper layer primitives provided by the SCTP are provided in
[SCTP].
2 Conventions
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when
they appear in this document, are to be interpreted as described in
[RFC2119].
In this document, the following conventions are used to describe how
a parameter is used in the message :
M parameter is mandatory in this message.
O parameter is optional in this message.
(A) parameter is applicable only in the ANSI TCAP message .
(I) parameter is applicable only in the ITU TCAP message.
(Ind) parameter is applicable only when this message's type is
Indication.
(Req) parameter is applicable only when this message's type is
Request.
3 Protocol Elements
The general message format includes a Common Message Header together
with a list of zero or more parameters as defined by the Message Type.
For forward compatibility, all Message Types may have attached
parameters even if none are specified in this version.
Jianxing Hou, et al [Page 14]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
3.1 Common Message Header
The protocol messages for the TCAP-User Adaptation Protocol requires
a message structure which contains a version, message type, message
length and message contents.This message header is common among all
signaling protocol adaptation layers:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Reserved | Message Class | Message Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| msg data |
Note that the 'data' portion of TUA messages SHALL contain TCAP-User
data, not the encapsulated TCAP message.
Optional parameters can only occur at most once in an TUA message.
3.1.1 TUA Protocol Version
The version field (ver) contains the version of the TUA adaptation
layer. The supported versions are:
01 TUA version 1.0
3.1.2 Message Classes
0 Management (MGMT) Message
1 Reserved
2 SS7 Signaling Network Management (SSNM) Messages
3 ASP State Maintenance (ASPSM) Messages
4 ASP Traffic Maintenance (ASPTM) Messages
5 Dialogue Handling(DH) Message
6 Component Handling(CH) Message
7 SGP Traffic Maintenance (SGPTM) Messages
8 - 127 Reserved by the IETF
128 - 255 Reserved for IETF-Defined Message Class Extensions
3.1.3 Message Types
TUA Management Messages
0 Error (ERR)
1 Notify (NTFY)
2 - 127 Reserved by the IETF
Jianxing Hou, et al [Page 15]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
128- 255 Reserved for IETF-Defined Message Class Extensions
SS7 Signaling Network Management (SSNM) Messages
0 Reserved
1 Destination Unavailable (DUNA)
2 Destination Available (DAVA)
3 SS7 Network Congestion (SCON)
4 Destination User Part Unavailable (DUPU)
5 - 127 Reserved by the IETF
128 - 255 Reserved for IETF-Defined Message Class Extensions
Application Server Process Maintenance (ASPM) Messages
0 Reserved
1 ASP Up (UP)
2 ASP Down (DOWN)
3 ASP Up Ack (UP ACK)
4 ASP Down Ack (Down ACK)
5 - 127 Reserved by the IETF
128 - 255 Reserved for IETF-Defined Message Class Extensions
ASP Traffic Maintenance (ASPTM) Messages
0 Reserved
1 ASP Active (ACTIVE)
2 ASP Inactive (INACTIVE)
3 ASP Active Ack (ACTIVE ACK)
4 ASP Inactive Ack (INACTIVE ACK)
5 - 127 Reserved by the IETF
128 - 255 Reserved for IETF-Defined Message Class Extensions
Dialogue Handling(DH) Message
0 Unidirectional(UNI)
1 Query
2 Conversation (CON)
3 End
4 U_Abort
5 P_Abort
6 Notice
7 - 127 Reserved by the IETF
128 - 255 Reserved for IETF-Defined Message Class Extensions
Component Handling(CH)Message
0 Invoke
1 Result
2 U_Error
3 Reject
Jianxing Hou, et al [Page 16]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
4 Cancel
5 Timer_Reset
6 - 127 Reserved by the IETF
128 - 255 Reserved for IETF-Defined Message Class Extensions
SGP Traffic Maintenance (SGPTM) Messages
0 Reserved
1 SGP Active(SGP Act)
2-277 Reserved by the IETF
3.1.4 Message Length
The Message Length defines the length of the message in octets,
including the header.
3.1.5 Tag-Length-Value Format
TUA messages consist of a Common Header followed by zero or more
parameters, as defined by the message type. The Tag-Length-Value
(TLV) parameters contained in a message are defined in a Tag-
Length-Value format as shown below.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Tag | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Parameter Value /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Tag: 16 bits (unsigned integer)
Tag field is a 16-bit identifier of the type of parameter. It
takes a value of 0 to 65534.
Parameter Length: 16 bits (unsigned integer)
The Parameter Length field contains the size of the parameter
in bytes, including the Parameter Tag, Parameter Length, and
Parameter Value fields. The Parameter Length does not include
any padding bytes.
Parameter Value: variable-length.
Parameter Value field contains the actual information to be
transferred in the parameter.The total length of a parameter
(including Tag, Parameter Length and Value fields) MUST be a
Jianxing Hou, et al [Page 17]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
multiple of 4 bytes. If the length of the parameter is not a
multiple of 4 bytes, the sender pads the Parameter at the end
(i.e., after the Parameter Value field) with all zero bytes.
The length of the padding is NOT included in the parameter length
field.A sender should NEVER pad with more than 3 bytes.The receiver
MUST ignore the padding bytes.
Implementation note: the use of TLV in principle allows the parameters
to be placed in a random order in the message. However, some
guidelines should be considered for easy processing in the
following order :
- parameters needed to correctly process other message parameters,
preferably should precede these parameters (such as Network
Appearance), mandatory parameters preferably should precede any
optional parameters,
- the data parameter will normally be the final one in the message.
3.2 TUA Message Header
In addition to the common message header, there will be a specific
message header for TUA Diagolue Handling messages and Component
Handling messages. The TUA message header will immediately follow the
Common header in these messages.
This message header contains the Dialogue ID(DID) and SSN.The format of
the DID parameter and SSN parameter are integer.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0502 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0501 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Dialogue ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.3 Dialogue Handling(DH)Message
The following section describes the TUA dialogue handling messages
and parameter contents. The general message format includes a Common
Message Header together with a list of zero or more parameters as
defined by the Message Type.All Message Types can have attached
parameters.
Jianxing Hou, et al [Page 18]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
3.3.1 Unidirectional(UNI)
A UNI request message is for transmission of one,or several components
invoking class 4 operations or reporting protocol errors in these
invocations, grouped in a message to the remote TCAP-user.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Originatiting Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Components present |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0101 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Quality of Service |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Application context name /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ User information /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0301 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Security Context /
\ \
Jianxing Hou, et al [Page 19]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0302 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Confidentiality /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Destination address M
Originating address M
Components present M(Ind)
Network Appearance O
Quality of Service O
Application context name O
User information O
Security Context O(A)
Confidentiality O(A)
3.3.2 Query
The Query request message may be issued prior to passing any component
to the Component sublayer.At the receiving side, the destination
TCAP-user is informed that a new dialogue starts by means of a Query
indication message.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Originatiting Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Components present |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0506 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Query Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
Jianxing Hou, et al [Page 20]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0101 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Quality of Service |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Application context name /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ User information /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0301 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Security Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0302 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Confidentiality /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Destination address M
Originating address M
Query Type M(A)
Components present M(Ind)
Network Appearance O
Quality of Service O
Application context name O
User information O
Security Context O(A)
Confidentiality O(A)
3.3.3 Conversation
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0503 | Length |
Jianxing Hou, et al [Page 21]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Conversation Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Components present |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0101 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Quality of Service |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Application context name /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Originatiting Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ User information /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0301 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Security Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0302 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Confidentiality /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Conversation Type M(A)
Components present M(Ind)
Network Appearance O
Quality of Service O
Jianxing Hou, et al [Page 22]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
Application context name O
Originating address O
User information O
Security Context O(A)
Confidentiality O(A)
3.3.4 End
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Components present |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0107 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Termination |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0101 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Quality of Service |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Application context name /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ User information /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0301 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Security Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0302 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Confidentiality /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Jianxing Hou, et al [Page 23]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
Parameters
Components present M(Ind)
Termination M(Req)
Network Appearance O
Quality of Service O
Application context name O
User information O
Security Context O(A)
Confidentiality O(A)
3.3.5 U_Abort
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0101 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Quality of Service |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Application context name /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ User information /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0401 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Abort reason |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0301 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Security Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0302 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Confidentiality /
Jianxing Hou, et al [Page 24]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0303 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ User Abort Information /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Network Appearance O
Quality of Service O
Application context name O
User information O
Abort Reason O(I)
Security Context O(A)
Confidentiality O(A)
User Abort Information O(A)
3.3.6 P_Abort
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0108 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| P-Abort |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0101 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Quality of Service |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
P-Abort M
Network Appearance O
Quality of Service O
3.3.7 Notice
Jianxing Hou, et al [Page 25]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0109 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Report cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Originatiting Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Report cause M
Network Appearance O
Destination address O
Originating address O
3.4 Component Handling(CH) Message
The following section describes the TUA Component handling
messages and parameter contents. The general message format
includes a Common Message Header together with a list of zero or
more parameters as defined by the Message Type. All Message Types
can have attached parameters.
3.4.1 Invoke
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0201 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Invoke ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0204 | Length |
Jianxing Hou, et al [Page 26]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Operation /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0504 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Invoke Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0203 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Last component |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0202 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timeout |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0402 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0205 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Parameters /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0208 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Invoke ID M
Operation M
Invoke Type M(A)
Last component M(Ind)
Timeout M(Req)
Class M(I)(Req)
Network Appearance O
Parameters O
Correlation ID O
3.4.2 Result
Jianxing Hou, et al [Page 27]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0201 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Invoke ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0203 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Last component |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0204 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Operation /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0205 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Parameters /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0208 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Invoke ID M
Last component M(Ind)
Network Appearance O
Operation O
Parameters O
Correlation ID O(A)
3.4.3 U_Error
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0201 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Invoke ID |
Jianxing Hou, et al [Page 28]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0206 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Error /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0203 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Last component |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0205 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Parameters /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0208 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Invoke ID M
Error M
Last component M(Ind)
Network Appearance O
Parameters O
Correlation ID O(A)
3.4.4 Reject
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0207 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Problem code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0203 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Last component |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0505 | Length |
Jianxing Hou, et al [Page 29]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reject Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0201 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Invoke ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0208 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0205 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Parameters /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Problem code M
Last component M(Ind)
Reject Type M(I)
Network Appearance O
Invoke ID O
Correlation ID O(A)
Parameters O(A)
3.4.5 Cancel
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0201 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Invoke ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Jianxing Hou, et al [Page 30]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
Invoke ID M
Network Appearance O
3.4.6 Timer_reset
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0201 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Invoke ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Invoke ID M
Network Appearance O
3.5 SS7 Signaling Network Management Messages
3.5.1 Destination Unavailable (DUNA)
In the scope of TUA, this message is covered by the PC state
indication passed between TCAP and local TCAP-user. The DUNA message is
sent from the SG to all concerned ASPs (servicing TCAP-usersconsidered
local to the SG), when an SS7 destination has become unreachable. The
TUA-User at the ASP is expected to stop traffic to the affected
destination through the SG initiating the DUNA.
The format for DUNA Message parameters is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0005 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
Jianxing Hou, et al [Page 31]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Affected Point Code M
Network Appearance O
Info String O
3.5.2 Destination Available (DAVA)
In the scope of TUA, this message is covered by the PC state
indication passed between TCAP and local TCAP-user. The DAVA message is
sent from the SG to all concerned ASPs (servicing TCAP-users considered
local to the SG) to indicate that an SS7 destination is now reachable.
The ASP TUA-User protocol is expected to resume traffic to the affected
destination through the SG initiating the DAVA.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0005 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Affected Point Code M
Network Appearance O
Info String O
3.5.3 SS7 Network Congestion (SCON)
Jianxing Hou, et al [Page 32]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
The SCON message can be sent from the SG to all concerned ASPs to
indicate that the congestion level in the SS7 network to a specified
destination has changed.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0010 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Congestion Level |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000E | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ Affected PC \
/ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ info string /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Congestion Level M
Affected PC M
Network Appearance O
Info String O
3.5.4 Destination User Part Unavailable (DUPU)
The DUPU message is used in local broadcast procedures (TUA for TCAP
- TCAP user interface).The format for DUPU Message parameters is as
follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause/User |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0005 | Length |
Jianxing Hou, et al [Page 33]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ info string /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Cause/User M
Affected Point Code M*
Network Appearance O
Info String O
Note *: In the DUPU message, the Affected Point Code Parameter
MUST contain, at most, a single Affected Point Code.
3.6 Application Server Process Maintenance Messages
3.6.1 ASP Up (UP)
The ASP UP (UP) message is used to indicate to a remote TUA peer
that the Adaptation layer is up and running.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0109 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Capabilities |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
ASP Capabilities O
Info String O
Jianxing Hou, et al [Page 34]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
3.6.2 ASP Up Ack (UP ACK)
The ASP UP Ack message is used to acknowledge an ASP-Up message
received from a remote TUA peer.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0109 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Capabilities |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
ASP Capabilities O
Info String O
3.6.3 ASP Down (DN)
The ASP Down (DN) message is used to indicate to a remote TUA peer
that the adaptation layer is not running.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000A | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reason |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Reason M
Info String O
3.6.4 ASP Down Ack (DOWN ACK)
Jianxing Hou, et al [Page 35]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
The ASP DOWN Ack message is used to acknowledge an ASP-Down message
received from a remote TUA peer.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000A | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reason |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Reason M
Info String O
3.7 ASP Traffic Maintenance Messages
3.7.1 ASP Active (ACTIVE)
The ASPAC message is sent by an ASP to indicate to a remote TUA peer
that it is Active and ready to process signaling traffic for a
particular Application Server
The format for the ACTIVE message is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000B | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Jianxing Hou, et al [Page 36]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
Parameters
Traffic Mode Type M
Routing Context O
Info String O
3.7.2 ASP Active Ack (ACTIVE ACK)
The ASPAC Ack message is used to acknowledge an ASP-Active message
received from a remote TUA peer.
The format for the ACTIVE Ack message is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000B | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000F | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SGP Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Traffic Mode Type M
Routing Context O
Info String O
The format of the Traffic Mode Type and Routing Context parameters
is the same as for the ASP-Active message.
The format and description of the optional Info String parameter is
the same as for the ASP-Active message.
3.7.3 ASP Inactive (INACTIVE)
Jianxing Hou, et al [Page 37]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
The INACTIVE message is sent by an ASP to indicate to a remote TUA
peer that it is no longer processing signaling traffic within a
particular Application Server.
The format for the ASPIA message parameters is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ INFO String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Routing Context O
INFO String O
3.7.4 ASP Inactive Ack (INACTIVE ACK)
The INACTIVE Ack message is used to acknowledge an ASP-Inactive
message received from a remote TUA peer.
The format for the INACTIVE Ack message is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ INFO String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Jianxing Hou, et al [Page 38]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
Routing Context O
INFO String O
The format of the Traffic Mode Type and Routing Context parameters
is the same as for the ASP-Active message.
The format and description of the optional Info String parameter is
the same as for the ASP-Active message.
3.8 Management Messages
These messages are used for managing TUA .
3.8.1 Error (ERR)
The ERR message is sent between two TUA peers to indicate an error
situation. The Data parameter is optional, possibly used for error
logging and/or debugging.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000C | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0007 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Diagnostic Info /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters
Error Code M
Diagnostic Info O
3.8.2 Notify (NTFY)
The Notify message used to provide an autonomous indication of TUA
events to an TUA peer.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000D | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type/ID |
Jianxing Hou, et al [Page 39]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The NTFY message contains the following parameters:
Parameters
Status Type/ID M
Routing Context O
Info String O
3.9 SGP Traffic Maintenance (SGPTM) Messages
3.9.1 SGP Active
This messages is used to notify ASP that SGP's status is changed.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000F | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SGP Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The message contains the following parameters:
Parameters
SGP Status M
3.10 Common Parameters
These TLV parameters are common across the different adaptation
layers.
Parameter Name Parameter ID
============== ============
Network Appearance 0x0001
Not used in TUA 0x0002
Not used in TUA 0x0003
Jianxing Hou, et al [Page 40]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
Info String 0x0004
Affected Point Code 0x0005
Routing Context 0x0006
Diagnostic Info 0x0007
Not used in TUA 0x0008
Cause/User 0x0009
Reason 0x000A
Traffic Mode Type 0x000B
Error Code 0x000C
Status Type 0x000D
Congestion Level 0x000E
SGP Status 0x000F
3.10.1 Network Appearance
The Network Appearance parameter identifies the SS7 network context
for the message, for the purposes of logically separating the
signaling traffic between the SG and the Application Server Process
over a common SCTP Association. An example is where an SG is
logically partitioned to appear as an element in several different
national SS7 networks.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| network appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Network Appearance implicitly defines the SS7 Point Code format
used, the SS7 Network Indicator value and SCCP protocol
type/variant/version used within the SS7 network partition. Where
an SG operates in the context of a single SS7 network, or individual
SCTP associations are dedicated to each SS7 network context, the
Network Appearance parameter is not required.
The Network Appearance parameter value is of local significance
only, coordinated between the SG and ASP.
Where the optional Network Appearance parameter is present, it must
be the first parameter in the message as it defines the format of
the Protocol Data field.
3.10.2 Not used
Parameter ID 0x02 is not used in TUA.
Jianxing Hou, et al [Page 41]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
3.10.3 Not used
Parameter ID 0x03 is not used in TUA.
3.10.4 Info String
The INFO String parameter can carry any meaningful 8-BIT ASCII
character string along with the message. Length of the INFO String
parameter is from 0 to 255 characters. No procedures are presently
identified for its use but the INFO String may be used by Operators
for debugging purposes.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ info string /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.10.5 Affected Point Code
The Affected Point Code parameter contains one or more Affected
Destination Point Codes, each a three-octet parameter to allow for
4-, 16- and 24-bit binary formatted SS7 Point Codes. Affected Point
codes that are less than 24-bits, are padded on the left to the 24-
bit boundary.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0005 | length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected PC 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ . . . /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The encoding is shown below for ANSI and ITU Point Code examples.
ANSI 24-bit Point Code:
0 1 2 3-->
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
Jianxing Hou, et al [Page 42]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Network | Cluster | Member |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|MSB-----------------------------------------LSB|
ITU 14-bit Point Code:
0 1 2 3-->
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask |0 0 0 0 0 0 0 0 0 0|Zone | Region | SP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|MSB--------------------LSB|
It is optional to send an Affected Pointe Code parameter with more
than one Affected PC but it is mandatory to receive it. All the
Affected PCs included must be within the same Network Appearance.
Including multiple Affected PCs may be useful when reception of an
management message or a linkset event simultaneously affects the
availability status of a list of destinations at an SG.
Mask: 8-bits
The Mask parameter can be used to identify a contiguous range of
Affected Destination Point Codes, independent of the point code
format. Identifying a contiguous range of Affected PCs may be
useful when reception of an MTP3 management message or a linkset
event simultaneously affects the availability status of a series of
destinations at an SG.
The Mask parameter is an integer representing a bit mask that can be
applied to the related Affected PC field. The bit mask identifies
how many bits of the Affected PC field is significant and which are
effectively "wild-carded". For example, a mask of "8" indicates
that the last eight bits of the PC is "wild-carded". For an ANSI
24-bit Affected PC, this is equivalent to signaling that all PCs in
an ANSI Cluster are unavailable. A mask of "3" indicates that the
last three bits of the PC is "wild-carded". For a 14-bit ITU
Affected PC, this is equivalent to signaling that an ITU Region is
unavailable.
3.10.6 Routing Context
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
Jianxing Hou, et al [Page 43]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Routing Context parameter contains (a list of) 4-byte unsigned
integers indexing the Application Server traffic that the sending
ASP is configured/registered to receive. There is one-to-one
relationship between an index entry and a SG Routing Key or AS Name.
Since an AS can only appear in one Network Appearance, the Network
Appearance parameter is not required in the ASP Active message.
An Application Server Process may be configured to process traffic
for more than one logical Application Server. From the perspective
of an ASP, a Routing Context defines a range of signaling traffic
that the ASP is currently configured to receive from the SG.
3.10.7 Diagnostic Information
The Diagnostic Information can be used to convey any information
relevant to an error condition, to assist in the identification of
the error condition. In the case of an Invalid Network Appearance,
Adaptation Layer Identifier or Traffic Handling Mode, the Diagnostic
information includes the received parameter.In the other cases,
the Diagnostic information may be the first 40 bytes of the
offending message.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0007 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Diagnostic Information* /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.10.8 Not Used
Parameter ID 0x08 is not used in TUA.
3.10.9 Cause/User
0 1 2 3
Jianxing Hou, et al [Page 44]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause | User |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Unavailability Cause field: 16-bits (unsigned integer)
The Unavailability Cause parameter provides the reason for the
unavailability of the TUA-User. The valid values for the
Unavailability Cause parameter are shown in the following table.
0 Unknown
1 Unequipped Remote User
2 Inaccessible Remote User
User Identity field: 16-bits (unsigned integer)
The User Identity describes the specific TUA-User that is
unavailable. Some of the valid values for the User Identity are
shown below.
0 - 2 Reserved by M3UA
3 SCCP/SUA
4 - 10 Reserved by M3UA
11 TCAP/TUA
3.10.10 Reason
The Reason parameter indicates the reason that the remote TUA
adaptation layer is unavailable.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause | User |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Reason: 32-bit (unsigned integer)
The valid values for Reason are shown in the following table.
0 Unspecified
Jianxing Hou, et al [Page 45]
Internet Drift SS7 TCAP-User Adaptation Layer April1,2001
1 User Unavailable
2 Management Blocking
3 ASP Fault
3.10.11 Traffic Mode Type
The Traffic Mode Type parameter identifies the traffic mode of
operation of the ASP within an AS.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000B | length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Type are shown in the following table.
1 Over-ride
2 Load-share
3 Over-ride (Standby)
4 Loadshare (Standby)
Within a Routing Context, Over-ride and Loadshare Types cannot be
mixed. The Over-ride value indicates that the ASP is operating in
Over-ride mode, and the ASP wishes to take over all traffic for an
Application Server (i.e., primary/back-up operation), over-riding
any currently active ASP in the AS. In Load-share mode, the ASP
wishes to share in the traffic distribution with any other currently
active ASPs. The Standby versions of the Over-ride and Loadshare
Types indicate that the ASP is declaring itself ready to accept
traffic but leaves it up to the sender as to when the traffic is
started. Over-ride (Standby) indicates that the traffic sender
continues to use the currently active ASP until it can no longer
send/receive traffic (i.e., the currently active ASP transitions to
Down or Inactive). At this point the sender may immediately move
the ASP to Active and commence traffic. Loadsha |
Documentation