02-Chapter 2 Transport Network Layer Procedure Analysis PDF

Protocols and Signalling Analysis
HUAWEI UMTS Radio Access Network Table of Contents
Table of Contents
Chapter 2 Transport Network Layer Procedure Analysis ......................................................... 2-1

2.1 Overview ............................................................................................................................ 2-1
2.2 SAAL.................................................................................................................................. 2-1
2.2.1 Overview ................................................................................................................. 2-1
2.2.2 SSCOP.................................................................................................................... 2-2
2.2.3 SSCF....................................................................................................................... 2-7
2.2.4 CPCS ...................................................................................................................... 2-8
2.2.5 SAR ......................................................................................................................... 2-9
2.2.6 LM ........................................................................................................................... 2-9
2.2.7 SSCOP Message .................................................................................................. 2-11
2.3 MTP3-B............................................................................................................................ 2-12
2.3.1 Overview ............................................................................................................... 2-12
2.3.2 Function................................................................................................................. 2-13
2.3.3 Message Structure ................................................................................................ 2-15
2.3.4 Changeover, Changeback, and Management Prohibit ......................................... 2-20
2.3.5 Signalling Network Management and Signalling Link Status................................ 2-21
2.3.6 Signalling Network Management and Signalling Route Status............................. 2-24
2.3.7 MTP3-B Upper User Message .............................................................................. 2-25
2.3.8 MTP3-B Test Message ......................................................................................... 2-26
2.3.9 MTP3-B Management Message ........................................................................... 2-27
2.4 ALCAP ............................................................................................................................. 2-28
2.4.1 Overview ............................................................................................................... 2-28
2.4.2 Function................................................................................................................. 2-29
2.4.4 Establishment Request Message.......................................................................... 2-32
2.5 SCCP ............................................................................................................................... 2-33
2.5.1 Overview ............................................................................................................... 2-33
2.5.2 Function................................................................................................................. 2-34
2.5.4 Connection Request Message .............................................................................. 2-36
Huawei Technologies Proprietary
i
Protocols and Signalling Analysis Chapter 2
HUAWEI UMTS Radio Access Network Transport Network Layer Procedure Analysis
Chapter 2 Transport Network Layer Procedure

Analysis
2.1 Overview
In UTRAN, the transport network layer adopts a message adaptation and transfer
mechanism to provide transport service for the radio network layer. In this way, the
radio network layer can evolve without too much consideration for the transport
technology.
The transport network layer includes the following logical entities:
z Signalling ATM Adaptation Layer (SAAL)
z Message Transfer Part (Broadband) (MTP3-B)
z Access Link Control Application Part (ALCAP)
z Signalling Connection and Control Part (SCCP)
In this chapter, we will discuss the architecture and function of each entity.
2.2 SAAL
2.2.1 Overview
The SAAL converts various formats of signalling messages from the upper layer into a
format suitable for transmission in an AMT network.
NBAP STC MTP3-B
SAAL
SSCS
SSCF AT UNI SSCF AT NNI
SSCOP LM
CP
CPCS
SAR
Figure 2-1 SAAL structure
2-1
The structure of SAAL in BSC6800 is illustrated in Figure 2-1. The SAAL comprises
the following parts:
z Service Specific Convergence Sublayer (SSCS)
The SSCS includes Service Specific Coordination Function (SSCF) and Service
Specific Connection Oriented Protocol (SSCOP).
z Common Part (CP)
The CP adopts AAL adaptation layer 5 (AAL5). It comprises Common Part
Convergence Sublayer (CPCS) as well as Segmentation and Reassembly (SAR).
z Layer Management (LM)
Note:
z For details about SSCF, refer to ITU-T Q.2140.
z For details about SSCOP, refer to ITU-T Q.2110.
z For details about LM, refer to ITU-T Q.2144.
2.2.2 SSCOP
I. Overview
The SSCOP transmits information and control information between two peer entities.
II. Function
The SSCOP performs the following functions.

z Sequence Integrity. This function preserves the order of SSCOP Service Data
Units (SDUs) that were submitted for transfer by SSCOP.
z Error Correction by Selective Retransmission. Through a sequencing mechanism,
the receiving SSCOP entity can detect missing SSCOP SDUs. This function
corrects sequence errors through retransmission.
z Flow Control. This function allows an SSCOP receiver to control the rate at which
the peer SSCOP transmitter entity may send information.
z Error Reporting to Layer Management. This function indicates to layer
management errors which have occurred.
z Keep Alive. This function verifies that the two peer SSCOP entities participating in
a connection are remaining in a link connection established state even in the case
of a prolonged absence of data transfer.
z Local Data Retrieval. This function allows the local SSCOP user to retrieve
in-sequence SDUs which have not yet been released by the SSCOP entity.
2-2
z Connection Control. This function performs the establishment, release, and

resynchronization of an SSCOP connection. It also allows the transmission of
variable length user-to-user information without a guarantee of delivery.
z Transfer of User-Data. This function is used for the conveyance of user data
between users of the SSCOP. SSCOP supports both assured and unassured
data transfer.
z Protocol Error Detection and Recovery. This function detects and recovers from
errors in the operation of the protocol.
z Status Reporting. This function allows the transmitter and receiver peer entities to
exchange status information.
SSCOP Protocol Data Units (PDUs) are the message units transmitted between
SSCOP peer layers for connection setup and release and for reliable message
transmission. They include the following basic PDUs.
z BGN PDU (Begin), used to set up connection between two peer SSCOP entities.
It requests the peer SSCOP to clear data in the transmitter and receiver buffers,
to perform initialization of state variables and receiving/sending counters.
z BGAK PDU (Begin Acknowledge), used to acknowledge the connection request
from the peer end.
z BGREJ PDU (Begin Reject), used to reject the connection request from the peer
SSCOP entity.
z END PDU (End), used to release the connection between the two ends in
communication.
z ENDAK PDU (End Acknowledge), used to acknowledge the release action.
z RS PDU (Resynchronization), used to resynchronize the buffers and data transfer
state variables.
z RSAK PDU (Resynchronization Acknowledge), used to acknowledge the
resynchronization request originated from the peer entity.
z ER PDU (Error Recovery), used to recover errors in connection action.
z ERAK PDU (Error Recovery Acknowledge), used to acknowledge the recovery
request.
z SD PDU (Sequenced Data), used to send user service data to the peer entity
after SSCOP connection has been set up.
z POLL PDU (Status Request), used to request status information of the peer
SSCOP after SSCOP connection setup.
z STAT PDU (Solicited Status Response), used as the response for POLL PDU. It
is used to notify which SD PDUs have been received and which have not. It is
also used to update the location of sending window so as to control the sending
sequence No. of the max. SD PDU. The STAT PDU also includes the sending SN
of the POLL PDU(N(PS)), which is used as the response to the POLL PDU.
z USTAT PDU (Unsolicited Status Response). It is sent by the receiving end to
inform the peer end resending the lost SD PDUs when the receiving end detects
loss of SD PDUs after comparing the receiving SN of SD PDU. The USTAT PDU
2-3
also contains data for updating sending window of the peer end, but contains no
N(PS) segment.
z Unnumbered Data (UD). UD are transmitted between peer SSCOP users. The
in-progress connection oriented sequencing will not be affected, no counter or
status between the two entities will be altered, and no data will be retransmitted if
they get lost.
z Management Data (MD). Unnumbered MD is transmitted between two SSCOP
management entities. Similar to UD PDUs, no reliable receiving of the peer end is
guaranteed.
III. SSCOP Operation State
SSCOP operation states reflect the states of the SSCOP in information exchanges
with its user and peer respectively. It includes the following basic states:
z State 1 - Idle, the initial state of SSCOP. Each SSCOP entity turns to idle state
after initialization and connection release.
z State 2 - Outgoing Connection Pending, the state when the local SSCOP entity
has sent connection setup request and has not received acknowledgement from
the peer end.
z State 3 - Incoming Connection Pending, the state when the local SSCOP has
received a connection setup request from the peer end and is waiting for the
response from the local end user.
z State 4 - Outgoing Disconnection Pending, the state after the local SSCOP entity
requests to release the connection with the peer end and before the local end
receives the connection release acknowledgement message.
z State 5 - Outgoing Resynchronization Pending, the state when the local end is
waiting for the acknowledgement from the peer end for its connection
resynchronization request.
z State 6 - Incoming Resynchronization Pending, the state when the local end has
received the resynchronization request from the peer end and is waiting for the
response from its user.
z State 7 - Outgoing Recovery Pending, the state when the local end has sent
request to the peer end for connection recovery and is waiting for recovery
acknowledgement.
z State 8 - Recovery Response Pending, the state when the SSCOP entity has
recovered the connection and notified the user and is waiting for response from
the user.
z State 9 - Incoming Recovery Pending, the state when the SSCOP entity has
received the connection recovery request from the peer end and is waiting for
response from its user.
z State 10 - Data Transfer Ready: the state when the connection setup,
resynchronization or error recovery program has been successfully accomplished
and the two SSCOP entities are ready for reliable data transmission.
2-4
IV. SSCOP Connection Setup
The procedure of SSCOP connection setup is as follows:

1) To set up connection between two peer SSCOP entities, the SSCF sends to
SSCOP A an AA-ESTABLISH.req primitive, as is shown in Figure 2-2. The
primitive includes the BR and SSCOP-UU parameters used by the SSCOP entity
to generate a BGN message.
2) SSCOP A sends the BGN message to SSCOP B, where it is decoded, processed
and mapped to an AA-ESTABLISH.ind signal.
3) SSCOP B sends the AA-ESTABLISH.ind signal to the SSCF of the receiving
entity.
4) The SSCF responds to SSCOP A with AA-ESTABLISH.rsp primitive. The
AA-ESTABLISH.rsp primitive also includes the SSCOP-UU and BR parameters.
5) SSCOP B sends a BGAK message to SSCOP A, where the BGAK message is
decoded, processed.
6) SSCOP A sends AA-ESTABLISH.con to the SSCF of the originating entity.
Now connection is set up between the two SAAL entities.
SSCOP A SSCOP B
AA-ESTABLISH.req PDU BGN

AA-ESTABLISH.ind.
AA-ESTABLISH.rsp.
PDU BGAK
AA-ESTABLISH.con.
Figure 2-2 SSCOP connection setup
V. SSCOP Connection Release
The procedure of SSCOP connection release is as follows:

1) After SSCOP A receives AA-RELEASE.request, it sends END PDU to SSCOP B,
as shown in Figure 2-3.
2) SSCOP B sends AA-RELEASE.indication to the user.
3) After the connection is released, SSCOP B sends ENDAK PDU to SSCOP A.
4) SSCOP A sends AA-RELEASE.confirm to the SSCF to release the connection.
2-5
SSCOP A SSCOP B
AA-RELEASE.request
END
AA-RELEASE.indication
AA-RELEASE. confirm
ENDAK
Figure 2-3 SSCOP connection release
VI. SSCOP Data Transmission and Error Recovery
In this section, we will introduce the SSCOP data transmission and error recovery
mechanism through an example as shown in Figure 2-4.
1) SSCOP A sends 4 SD PDUs to SSCOP B, with their N(S) numbered from 0 to 3.
Only PDU1 and PDU2 properly reach SSCOP B. SSCOP B delivers PDU1 and
PDU2 to the user.
2) SSCOP A then sends a POLL PDU, which contains a N(S)=5 representing the
N(S) value of the next new SD PDU (the SD PDU to be transferred the next time).
The POLL PDU also contains a N(PS)=1, the sequence No. of the POLL PDU.
3) SSCOP B uses a STAT PDU as the response to the POLL PDU. The N(R) in the
STAT PDU is coded 3 for acknowledging PDU1 and PDU2 and for indicating its
expectation of the next PDU, that is, PDU3. The N (PS) segment in the STAT
PDU is the same as that in the corresponding POLL PDU. The list element in the
STAT PDU is set as (3, 5), which tells the SSCOP A:
- To resend PDU3 and PDU4;
- To release PDU1 and PDU2 from the buffer;

- To preserve PDU3 and PDU4, because there is still no sufficient information
about the results of PDU3 and PDU4.
Note:
The odd element (the value is 3 in this example) represents a PDU within a certain
loss interval, while the even element represents the first PDU in the next sequence
properly received.
2-6
Action Tx Rx Delivered
1 (0)
2 (0) 1 X
3 (0) 2 X
4 (0) X
POLL(5,1)
X
5 (1)
6 (1)
7 (1)
5})
N(MR), {3,
STAT(3, 1, X
X
Free 1, 2
7
Figure 2-4 SSCOP data transmission
2.2.3 SSCF
I. Overview
As shown in Figure 2-1, the SSCF functions as the adaptation layer of the SSCOP and
upper layer applications. The upper layer applications include NBAP, MTP3-B and
Signalling Transport Converter (STC).
The MTP3-B is used for network-to-network interface (NNI), which has higher link
quality. The SAAL is required to support link quality check and to help the MTP3-B to
perform link switchover.
However, the NBAP is used for User-to-Network Interface (UNI), which has poorer link
quality and greater delay.
Therefore, the SSCF is divided into SSCF-NNI and SSCF-UNI to cater to different
upper layer applications.
z SSCF-NNI is used for adapting the SSCOP and the upper layer MTP3-B. It maps
primitives from the MTP3-B to SSCOP signals as required, or reversely. The
SSCF-NNI acts as a medium for signal transferring between SSCOP and
MTP3-B. The SSCF does not send PDUs to the peer SSCF of the receiver. It
transfers the information through SSCOP PDUs. Besides primitive mapping, the
SSCF-NNI also implements local data retrieval, link state maintenance, and link
quality check. It reports link information to the LM.
z SSCF-UNI is used for adapting the SSCOP and the upper layer NBAP or STC. It
implements error-free sequential data transmission by the SSCOP. Similar to the
SSCF-NNI, the SSCF-UNI maps primitives from the NBAP/STC to SSCOP
signals as required. It differs from SSCF-NNI in that it does not implement link
alignment and data retrieval functions. The SSCF-UNI accomplishes primitive
mapping, SAAL link setup and release, and data transmission acknowledgement.
2-7
II. Function
The SSCF performs the following functions.

z Primitive mapping
The SSCF maps primitives from the MTP3-B to SSCOP signals as required, or
reversely.
z Local data retrieval
In the case of link failure, the SSCF retrieves unsent data from the link before link
switchover, and then sends the data to another link for transmission.
z Flow control
The SSCF reports to the user the congestion level (or no congestion) to prevent
the loss of cells. It also adjusts certain PDUs to the lower layer to prevent
congestion at the peer end.
z Link state maintenance
According to primitives received from the MTP3-B and SSCOP, the SSCF
maintains information about link states, such as Out Of Service and In Service.
Using the information, it can provide primitives/signals to the MTP3-B and
SSCOP for link management.
z Reporting to LM
The SCCF sends Management AAL (MAAL) primitives to the LM. For example,
the SSCF reports link fault to the LM when a link gets faulty. It monitors errors
with the help of the LM.
z Link alignment
2.2.4 CPCS
CPCS-PDU
PAD UUI CPI LI CRC
payload
0~47bytes 8 bits 8 bits 16 bits 32bits

CPCS-PDU tail
Figure 2-5 CPCS-PDU format
As shown in Figure 2-5, the CPCS-PDU includes three parts, CPCS-PDU payload,
PAD and CPCS-PDU tail.
The length of CPCS-PDU payload is variable within 1–65535 bytes.
The bytes filled in PAD make the length of CPCS-PDU the integer times of 48 bytes.
The length of CPCS-PDU tail is 8 bytes, including the following parts:
2-8
z User-to-User Indication (UUI), used for the transparent transmission of

information between CPCS users.
z CPCS Part Indication (CPI), used to make the length of CPCS-PDU tail as 8
bytes.
z Length Indication (LI), used to indicate the length of CPCS-PDU payload.
z Cyclic Redundancy Check (CRC), used to check the content of CPCS-PDU,
including CPCS-PDU payload, PAD, UUI, CPI and LI.
2.2.5 SAR
The Segment and Reassemble (SAR) sublayer in the AAL5 segments the CPCS-PDU
into 48-byte SAR-PDU without any overheads. The reassembly function is performed
during SDU receiving.
2.2.6 LM
I. Overview
The LM interacts directly with SAAL sublayers to accomplish Operation Administration
and Maintenance (OAM) functions. No interactions are defined between CPCS and
SAR, because both CPCS and SAR are hardware dependent. The SSCS LM is
responsible for the following tasks:
z The SSCS LM determines whether a link shall exit or enter service status.
z The SSCS LM conducts multiple measurements periodically. For example, it
counts each link’s service life, fault frequency, congestion frequency, and so on.
The LM can be in any of the following states:
z Out Of Service
z Alignment
z Proving
z Aligned Ready
z In Service
II. Function
The LM provides three algorithms for error monitoring. These algorithms can detect
burst errors lasting more than 400 ms.
z Algorithm 1 applies to heavy load. If the data volume to be sent is too large, the
receiving end does not have enough time to process them so that data in the
buffer cannot be released on time and the sending queue keeps increasing.
When the sending queue is increased to a certain value, links will be released.
z Algorithm 2 applies to medium load. Algorithm 2 monitors the number of data
retransmissions. Within a certain period, if the number of data retransmissions
exceeds the threshold, the link quality must be very poor. When the transmission
delay cannot be tolerated by the system, links will be released.
2-9
z Algorithm 3 applies to light load. The number of STAT PDUs lost is the difference
between the number of POLL PDUs sent and the number of STAT PDUs
received. If this value exceeds a certain value within a certain period, it means the
link quality is very poor and links will be released.
2-10
2.2.7 SSCOP Message
I. Message Parameters
Parameters Comments
N(S) VT(S) is mapped to N(S) whenever a new SD or POLL PDU is

generated.
Information field The information field of an SD, MD, or UD PDU is mapped

from the “Message unit” parameter of an AA-DATA,
MAA-UNITDATA, or AA-UNITDATA request, respectively. It is
mapped to a “Message unit” parameter of an AA-DATA,
MAA-UNITDATA, or AA-UNITDATA indication, respectively.
N(PS) VT(PS) (after VT(PS) has been incremented) is mapped to

N(PS) whenever a POLL PDU is generated. The receiver of a
POLL PDU maps the received POLL.N(PS) into the field
STAT.N(PS). In addition, to facilitate error recovery
procedures, the current value of VT(PS) is mapped into N(PS)
and stored in the transmitter buffer with the corresponding SD
PDU whenever a SD PDU is sent.
N(R) VR(R) is mapped to N(R) whenever a STAT or USTAT PDU is

generated.
N(MR) VR(MR) is mapped to N(MR) whenever a STAT, USTAT, RS,

RSAK, ER, ERAK, BGN, or BGAK PDU is generated. This is
the basis for credit granting by the receiver.
SSCOP-UU The SSCOP-UU in a BGN, BGAK, BGREJ, END or RS PDU is

mapped to and from the “SSCOP-UU” parameter of the
corresponding SSCOP signal.
Source (S) bit In an END PDU this bit conveys whether the originator of the
release was the SSCOP or the SSCOP user. When the
transmission of an END PDU is stimulated by the user, this bit
is set to 0. When the transmission of an END PDU is
stimulated by the SSCOP, this bit is set to 1.
N(SQ) This field carries the connection sequence value. VT(SQ) is

mapped to N(SQ) whenever a new BGN, RS, or ER PDU is
transmitted. This field is used by the receiver together with
VR(SQ) to identify retransmitted BGN, RS, and ER PDUs
PDU Type field PDU type
2-11
II. Example
2.3 MTP3-B
2.3.1 Overview
Based on Message Transfer Part Layer 3 (MTP3), the MTP3-B is the protocol
specification aiming at ATM features. It performs message exchange through the
services provided by SAAL.
The MTP3-B module performs MTP3-B protocol functions, including signalling
message handling and signalling network management, as shown in Figure 2-6.
z Signalling message handling part
2-12
This part guarantees the signalling message generated at the user part of a
signalling point (SP) can be transmitted to the corresponding user part of the
destination specified by the related field in message signalling unit (MSU). There
are only two user parts at Iu/Iur interface, that is, SCCP and STC. Functionally the
function of this part may be further subdivided into message discrimination,
message routing and message distribution.
z Signalling network management part
This part performs re-networking for a signalling network in case of failure. With
the increase of signalling network traffic and signalling link load, the signalling
network might be congested. Therefore, this part also performs congestion
control function. The signalling network management function can be classified
as signalling traffic management, signalling link management and signalling route
management.
Figure 2-6 MTP3-B protocol structure
2.3.2 Function
I. Message Discrimination
Message Discrimination is to identify the destination of a signalling message by

analyzing the destination signalling point code (DPC) in the signalling message routing
label.
When a signalling message arrives at Layer 3 (MTP3-B) from Layer 2 (SAAL), this
function first processes it and determines its next destination. If the local SP is the
destination, the message will be handed over to the message distribution function for
2-13
subsequent handling. If the local SP is not the destination and is capable of

transferring, the message routing function will be enabled. If the local SP does not
have the transferring capability, the signalling network management function will be
informed to handle the message as an illegal one.
II. Message Distribution
Message Distribution is to distribute the signalling message to the corresponding user

part of the local SP. As the MTP3-B of the SP has to serve multiple user parts, it is
required to decide to which user part the signalling message will be distributed by
analyzing the service indicator (SI) in the service information octet (SIO) of the
signalling message.
When the SI field equals 0000 or 0001 (i.e., the message to be distributed is a
signalling network management message or a maintenance and test message), the
codes of the herder, H0 and H1, will be analyzed so as to specify by which signalling
network management part the message is to be handled.
III. Message Routing
Message Routing is to select a proper route for the message according to the header
information. It processes the message as follows:
z For the message sent from the upper layer, the message routing function finds an
available route, if any, to send it.
z For the message sent from another SP, it will be sent out if the SP receiving it has
the signalling transfer function and the Destination Signalling Point (DSP) of this
message exists in the DSP table of this SP.
z For the message that does not belong to a SP, it will be discarded if this SP has
the signalling transfer function but the DSP of this message does not exist in the
DSP table of this SP.
IV. Signalling Traffic Management
Signalling Traffic Management is to transfer signalling traffic over signalling links or

routes or temporarily reduce traffic in case of congestion. Signalling traffic
management covers the following procedures:
z If a signalling link gets unavailable (for example, faulty, disconnected or inhibited),
the traffic over the signalling link will be changed over to another one or more
links.
z When the link becomes available (reconnected or uninhibited), the traffic will be
changed back to this link.
z If a signalling route gets unavailable, the traffic over this route will be changed
over to the substitute route by means of forcible rerouting.
z When the route becomes available, the traffics will be changed back to this route
by the controlled rerouting program.
2-14
z If a signalling route is restricted, the traffic over this route will be changed over to
the substitute route by the controlled rerouting program.
To limit the traffic of signalling sources in case of congestion, the signalling traffic flow
control program is used.
V. Signalling Route Management
Signalling route management is to ensure reliable interchange of signalling route

availability information among SPs.
VI. Signalling Link Management
Signalling link management is to stop using an unavailable or unreliable link and

repeatedly restart it to make it available. Besides, it also provides the link test function
to periodically test links for confirmation of the usability of these links.
2.3.3 Message Structure
The structure of MTP3-B is the same as that of MTP3. Service Information Octet (SIO)
and Service Information Field (SIF) are also included in Its MSU.
I. Service Information Octet (SIO)
SIO comprises Service Indicator (SI) and Sub-Service Field (SSF), as shown in Figure
2-7. The length of SIO is eight bits, among which SI and SSF occupy four bits
respectively.
2-15
Figure 2-7 SIO format and codes
z Service Indicator (SI)

SI is used to indicate to which specified user part a transmitted message belongs. In
the MTP of the signalling network, the signalling message handling function distributes
the message to the specified user part according to the indication of SI.
The code of SI is illustrated in Figure 2-7. The capacity of SI can be used to indicate 16
different user parts. The figure only shows several of them.
z Sub-Service Field (SSF)
It is made up of 4 bits, of which the higher two bits act as the network indicator, and the
lower two bits, coded 00, are reserved presently.
The network indicator serves to distinguish the network attribute of the transmitted
message, that is, to distinguish between an international signalling network message
and a national signalling network message, as shown in Figure 2-7.
II. Signalling Information Field (SIF)
SIF includes two parts, addressing label and signalling message, as shown in Figure
2-8.
z Label
2-16
Label includes the necessary information needed to send the message to its
destination. The length of standard routing label is 32 bits, it locates in the beginning of
the SIF. Label includes Destination Point Code (DPC), Originating Signalling Point
Code (OPC) and Signalling Link Selection Code (SLS).
DPC is digital address, which is the code used to identify each signalling point
uniquely in the SS7. When the DPC of the message represents the accepting
signalling point, the message is sent to the corresponding user part that the service
indicator of the SIO indicates (for instance, the SCCP).
SLS is used to:
- Guarantee the message order. Any two messages with the same SLS reach their
destination in the same order they are sent.
- Allow all the available links to share the traffic load equally. If a user part sends
messages periodically, and distributes the SLS in a cyclic way, then all the service
levels at the destination shall be the same.
SIF SIO First bit transmitted
Signaling message SL OP DP
S C C
Figure 2-8 SIF format
z Signalling message
The signalling message part is also called service information part. This part can be
further divided into several sub-fields. These sub-fields can be mandatory or optional.
The length of them can be fixed or flexible to meet the demands of various functions or
expansion. Therefore, this part applies to different user messages and enables
transmitting different user messages in the common channel.
The most important signalling message of MTP layer is the signalling network
management message. In the following, we will focus on it.
III. Format of Signalling Network Management Message
Signalling network management messages, originating from Level 3 (peer or local

end), mainly apply to signalling traffic management, signalling link management and
signalling route management.
A signalling network management message is identified, in a signalling network, by the
SI of the SIO in the signal message unit, where SI equals 0000.
This message is composed of n x 8 (nƒ0) bits. It may contain one or more signalling or
indicator codes, yet with a total length of integer number of octets.
2-17
Being one of MSUs, the signalling information of signalling network management

messages is transmitted in the SIF, with the structure illustrated in Figure 2-9.
Management H1 H0 SLC OPC DPC

information First bit transmitted
8n 4 4 4 4 24/14 24/14
( n = 0)
Figure 2-9 General format of a signalling network management message
z Label
Composed of DPC, OPC and SLC, as stated before
z Heading code
The heading code is made up of two 4-digit bits: H0 and H1.
H0 identifies the management message group, and H1 determines the messages in a

message group. H0 and H1 occupy 4 bits respectively. They can represent 265 kinds
of messages, that is, there are 16 message groups and each of them has 16 types of
messages.
Table 2-1 Description of heading code H0
H0 Description
0000 Reserved
0001 Changeover and changeback messages (CHM)
0010 Emergency changeover message (ECM)
Transfer controlled and signalling route set congestion

0011
messages (FCM)
0100 Transfer-prohibited-allowed-restricted messages (TFM)
0101 Signalling-route-set-test messages (RSM)
0110 Management inhibit messages (MIM)
0111 Traffic restart allowed message (TRM)
1001 Spare
1010 User part flow control messages (UFC)
1011–1111 Spare
2-18
The signalling network management message and its heading code allocation are
described in Table 2-2 in details.
Table 2-2 Network management messages of the third function level of SS7
Message H1 10 10 10 11 11 11 11
0000 0001 0010 0011 0100 0101 0110 0111 1000
Group 01 10 11 00 01 10 11
H0
0000
CHM 0001 XCO XCA CBD CBA
ECM 0010 ECO ECA
FCM 0011 RCT TFC
TFM 0100 TFP TFR TFA
RSM 0101 RST RSR
MIM 0110 LIN LUN LIA LUA LID LFU LLT (LRT)
TRM 0111 (TRA)
DLM 1000
1001
UFC 1010 (UPU)
1011
1100
1101
1110
1111
CBA: Changeback-acknowledgement signal

CBD: Changeback-declaration signal
XCA: Extended Changeover Acknowledgement
XCO: Extended Changeover Order
ECA: Emergency-changeover-acknowledgement signal
ECO: Emergency-changeover-order signal
RCT: Signalling-route-set-congestion-test signal
2-19
RSR: Signalling-route-set-test signal for restricted destination (national option),

RST: Signalling-route-set-test signal for prohibited destination
TFR: Transfer-restricted signal (national option)
TFA: Transfer-allowed signal
TFC: Transfer-controlled signal
TRA: Traffic-restart-allowed signal
TFP: Transfer-prohibited signal
LID: Link inhibit denied signal
LFU: Link forced uninhibit signal
LIN: Link inhibit signal
LIA: Link inhibit acknowledgement signal
LUA: Link uninhibit acknowledgement signal
LUN: Link uninhibit signal
LLT: Link local inhibit test signal
LRT: Link remote inhibit test signal
UPU: User Part Unavailable signal
2.3.4 Changeover, Changeback, and Management Prohibit
I. Changeover
Changeover refers to the signalling traffic management process which shifts the
signalling traffic from a signalling link, when it turns from normal operation into
unavailable (such as signalling link fault, blocking or out of service), to one or more
alternative signalling links.
II. Changeback
Generally, signalling traffic in the signalling network are carried on normal signalling
links, while alternative signalling links only take over the signalling traffic from the
signalling links that are "temporarily" faulty. Therefore, signalling traffic must be
changed back to normal signalling links once the “temporarily” faulty links are available
again.
III. Management Prohibit
Management prohibit is a signalling traffic management function, which is used to

maintain and test the signalling network.
Signalling link prohibit can be started by the management function of the signalling link
terminal. During the inhibited period, any link status of the second function level does
2-20
not change. However, the signalling link is marked as “inhibited”, and the signalling
traffic on the inhibited link is stopped temporarily. You can carry out tests periodically.
If necessary, the inhibited link can be un-inhibited by the MML command or signalling
route control function.
2.3.5 Signalling Network Management and Signalling Link Status
MTP3-B usually regards a signalling link as either available or unavailable. A signalling

link can transmit signalling traffic only when it is available.
There are the following three causes for a signalling link to become unavailable:
z Signalling link faulty
z Signalling link inhibited
z Signalling link not working
In the signalling network, the status of a signalling link may change as a result of the
following:
z Signalling link faulty
z Signalling link restored
z Signalling link disconnected
z Signalling link connected
z Signalling link inhibited or uninhibited
If a signalling link is identified as "Faulty", "Disconnected", or "Inhibited", it will become
unavailable. If the signalling link is identified as "Restored", "Connected” or
"Uninhibited", it will again become available.
I. Signalling Link Faulty
In any of the following cases, the signalling link is deemed faulty and becomes
unavailable:
z The SAAL gives the fault indication “Out of Service”.
z A request from the management system indicates this link is faulty.
z A changeover command from the peer end requests to change over the signalling
traffic to another signalling link.
II. Signalling Link Restored
The process to remove the fault of a signalling link and make the signalling link ready
for transmitting signalling traffic is referred to as signalling link restoration. When the
fault is removed and initial alignment is successfully completed at both ends of the
faulty signalling link, the signalling link becomes available again.
2-21
III. Signalling Link Disconnected
The process to stop traffic of a signalling link set or a signalling link is defined as
signalling link disconnection.
Signalling link may be disconnected upon the request of the operation and
maintenance system or by the signalling link management function as well.
IV. Signalling Link Connected
The process to make the signalling link ready for signalling traffic transmission is
defined as signalling link connection.
When a disconnected signalling link has its signalling data link or signalling terminal
connected again and the initial alignment is completed successfully, the once
disconnected signalling link is regarded as being connected.
Table 2-3 shows general processes of signalling network management upon change
of signalling link status.
Table 2-3 Signalling network management processes upon change of signalling link
status
Signalling network management

Signalling
link status Signalling traffic Signalling link Signalling route
management management management
Starts the
changeover When a signalling
procedure (or link is faulty, the
emergency signalling link
The signalling route
changeover management
function is disabled if
procedure when function will,
the signalling link fault
necessary) to shift according to the
does not result in any
the signalling traffic status of the
change of signalling
Faulty on the unavailable signalling link set,
route set status.
(becomes signalling link to one connect another
Otherwise, the
unavailable) or more alternative signalling link in the
transfer-prohibited
signalling links. The signalling link set,
process or
process above and then prepare
transfer-restricted
mentioned includes for the restoration of
process has to be
specifying the the faulty signalling
started.
alternative signalling link and its
link, recovering the signalling
messages sent yet transmission
not acknowledged.
2-22

Signalling
If another signalling
The changeback
link in the same link
process, when
set is connected
necessary, is
during the signalling
activated to shift the
link fault, then the The signalling route
signalling traffic from
stop process is function is disabled if
the one or more
used to change the the signalling link fault
alternative signalling
signalling link set does not result in any
links back to the link
status back to that change of signalling
Restored that recovers to be
before the fault route set status.
available. It includes
occurs, and to Otherwise, the
the process to
disconnect the transfer-allowed
specify the signalling
operating link process has to be
traffic that can be
connected during started.
changed back to and
the signalling link
to maintain the
fault, regarding it
correct message
unable to transmit
sequence.
signalling.
Normally, when a When one

signalling link is to be signalling link is
disconnected, the disconnected, if the
signalling traffic has number of signalling
The same procedure
already been links operating in
Disconnected as that after a
transferred. If it is not the link set is less
signalling link is faulty
yet transferred, the than the necessary
signalling traffic number, another
changeover process link will be
shall be executed. connected.
When the signalling

link is connected, if
the number of
The same procedure The same procedure
connected
as that after a as that after a
Connected signalling links in
signalling link is signalling link is
the link set is
restored restored
greater than the
necessary number,
another link will be
2-23

Signalling
disconnected.
If a signalling route set

becomes unavailable
or restricted, due to
link inhibit, it cannot
The same procedure
perform the
Inhibited as that after a None
transfer-prohibited
signalling link is faulty
process on the STP
which can select
routes for relevant
messages.
When a signalling
route set becomes
The same procedure
available again due to
as that after a
Uninhibited None link uninhibit, the
signalling link is
transfer-allowed
restored
process will be
employed.
2.3.6 Signalling Network Management and Signalling Route Status
For the signalling traffic to a destination, the signalling route may be in one of these
two states: available, unavailable.
When a transfer-prohibited message is received, indicating that the signalling traffic to
a destination can no longer be transmitted via the STP sending out relevant messages,
the signalling route will become unavailable.
When a transfer-allowed message is received, indicating that the signalling traffic to a
destination can be transmitted via the STP sending out the transfer-allowed message,
the signalling route will again become available.
Table 2-4 shows the processes of signalling network management upon change of
signalling route status.
2-24
Table 2-4 Signalling network management processes upon change of signalling route
status
Signalling Signalling network management

route Signalling traffic
status Signalling route management
management
When a signalling route becomes

The forcible rerouting process
unavailable, the transfer-prohibited
is performed so that the
process will be started, informing one
signalling traffic to a
or more adjacent signalling points that
destination is changed over
Unavailable this STP can no longer transmit
from the link set which
messages. Meanwhile, the route set
includes the unavailable route
test process or the route set
to the alternative route
congestion test process will be
connecting another STP.
started accordingly.
The controlled rerouting

process is performed so that The transfer-allowed process will be
the signalling traffic to a started, informing one or more
destination is changed back adjacent signalling points that this
Available from the signalling link set STP can transmit messages again.
which includes the alternative Meanwhile, the route set test process
signalling route to the or the route set congestion test
signalling link set which process will be stopped.
includes the recovered route.
2.3.7 MTP3-B Upper User Message
I. Message Structure
Refer to section 2.3.3 “Message Structure”.
2-25
II. Example
2.3.8 MTP3-B Test Message
2-26
II. Example
2.3.9 MTP3-B Management Message
2-27
II. Example
2.4 ALCAP
2.4.1 Overview
Q. AAL2
ALCAP
SAAL STC MTP3-B STC
SAAL UNI MTP3-B
Figure 2-10 ALCAP structure in the BSC6800 system
2-28
Access Link Control Application Part (ALCAP) is also called Q.AAL2 protocol. It is the
protocol of the control plane of the transport network layer on the Iub, Iur, and Iu-CS
interfaces. The signalling bearers are of SAAL UNI type and MTP3-B type.
As shown in Figure 2-10, the ALCAP consists of a Q.AAL2 protocol processing layer
and two STC adaptation layers. The former performs all protocol functions while the
latter adapts primitives and shields bottom-layer (SAAL and MTP3-B) differences.
The basic function of ALCAP is to establish and release AAL2 connection between two
SPs. Besides, it maintains and manages such resources as micro channel.
The ALCAP of BSC6800 complies with ITU-T Q.2630.1.
2.4.2 Function
I. AAL2 Connection Establishment and Release
The establishment and release of an AAL2 connection is initiated by the ALCAP at the
RNC side (“RNC ALCAP” for short hereinafter), as shown in Figure 2-11.
Figure 2-11 AAL2 connection establishment and release procedure
The procedure to establish an AAL2 connection is as follows:

1) The RNC ALCAP sends an ESTABLISH REQUEST message to the ALCAP at
the peer end (“peer RNC” for short hereinafter).
2) The peer ALCAP sends an ESTABLISH INDICATION primitive to the service
layer after resource allocation and starts the wait timer.
3) After receiving an ESTABLISH response from the service layer before the time
expires, it sends an ESTABLISH confirm to the RNC ALCAP.
The release procedure is similar to the establishment procedure.
2-29
II. AAL2 Path Block and Unblock
To prevent a new connection from being established over an AAL2 path, the O&M
system can initiates a path block procedure.
When a path is blocked, the originating end is in a locally blocked state and the peer
end is in a remotely blocked state. If the peer end also initiates a block procedure, both
ends of the path are in a locally blocked state. The test connection can be set up over
the path in a blocked state.
The blocked AAL2 path may be unblocked through an unblock procedure. The
unblock procedure can be initiated by local end or remote end.
The procedure of blocking and unblocking a path is shown in Figure 2-12.
O&M RNC ALCAP ALCAP
BLOCK REQUEST
BLOCK REQUEST
BLOCK CONFIRM
BLOCK CONFIRM
UNBLOCK REQUEST
UNBLOCK REQUEST
UNBLOCK CONFIRM
UNBLOCK CONFIRM
Figure 2-12 AAL2 path block and unblock procedure
The procedure to block a path is as follows:

1) The RNC O&M system initiates a BLOCK REQUEST to the RNC ALCAP.
2) The RNC ALCAP sends a BLOCK REQUEST to the peer ALCAP.
3) After analyzing the message, the peer ALCAP sets the path in blocked status,
generates a BLOCK CONFIRM message, and sends it to the RNC ALCAP.
4) The RNC ALCAP sends the message to the O&M system.
The unblock procedure is similar to the block procedure.
III. AAL2 Connection/Path Reset
The reset procedure can help to release AAL2 connection or AAL2 PATH in confused
state. This procedure can reset an AAL2 connection, an AAL2 PATH, or all AAL2
PATHs between two SPs.
The reset procedure is shown in Figure 2-13.
2-30
O&M RNC ALCAP ALCAP Service
RESET REQUEST
RESET REQUEST
RELEASE INDICATION
RESET CONFIRM
RESET CONFIRM
Figure 2-13 AAL2 connection/path reset procedure
The reset procedure is as follows:

1) The RNC O&M system initiates a RESET REQUEST to the RNC ALCAP.
2) The RNC ALCAP sends a RESET REQUEST to the peer ALCAP.
3) After analyzing the message, the peer ALCAP sends a RESET CONFIRM
message to the RNC ALCAP. If there is any connection in the micro channel or
path, the connection will be released and a RELEASE INDICATION will be
reported to the service layer.
4) The RNC ALCAP sends the message to the O&M system.
The length of an ALCAP message is variable and the message header is 6 bytes long
fixedly. The parameters in the message are classified as mandatory parameters and
optional parameters. The parameters can also be divided into fixed-length parameters
and variable-length parameters. The first byte of the variable-length field in a
variable-length parameter indicates the length of the field. The structure is shown in
Figure 2-14.
2-31
Signaling related ID
Message ID
Message compatability field
Message length
ID of parameter A
Compatability field for parameter A

Length of parameter A
Field a in parameter A
Field b in parameter A
Length of field c in parameter A
Field c in parameter A
Parameter B
Figure 2-14 ALCAP message structure
2.4.4 Establishment Request Message
2-32
II. Example
2.5 SCCP
2.5.1 Overview
Signalling Connection Control Part (SCCP) is used to enhance the functions of
Message Transfer Part (MTP). The addressing function of MTP can only be used to
transmit messages to nodes, providing only connectionless message transfer. The
SCCP is able to provide the addressing function to identify each SCCP user in a node
using DPC and subsystem number (SSN).
The SCCP in the BSC6800 system complies with ITU-T Q711-716.
2-33
2.5.2 Function
The SCCP performs network service, routing and management functions.
I. Network Service Function
The SCCP provides three classes of protocols:

z Class 0: Basic connectionless class
z Class 1: In-sequence delivery connectionless class
z Class 2: Basic connection-oriented class
Class-0 and class-1 protocols are used in connectionless services, while class-2
protocol is used in connection-oriented services.
z Connectionless services
Connectionless services are implemented in the case that the user directly transmits
data information in the signalling network by means of SCCP and MTP routing
functions without prior establishment of signalling connections, featuring flexibility and
simpleness and applicable to the transmission of small quantities of data. Among them,
class-0 service does not ensure the messages can be transmitted in sequence but
class-1 service is able to do that depending on the cooperation of the signalling link
selection code (SLS) and MTP.
Connectionless services implement user data transmission using Unit Data (UDT) and
Enhanced Unit Data (XUDT) messages. The UDT message cannot be segmented and
reassembled and it can transmit up to 255 octets. The XUDT message can be
segmented and reassembled and it can transmit up to 2k octets.
z Connection-oriented services
Connection-oriented services are implemented only after the user establishes
signalling connections (virtual connections) between the OSP and DSP by answer
mode before transmitting signalling messages. In this way, the data can be transmitted
via the established signalling connections instead of the routes selected via the SCCP
routing function. Upon the completion of the data transmission, the user can release
the connections with the primitive N_DISCONNECT_REQ.
Connection-oriented services are applicable to the transmission of large quantities of

data. The reason is that the DSP is confirmed to be able to receive data prior to data
transmission to avoid invalid transmission of large quantities of data. Furthermore, the
pre-established connections make the SCCP routing function unnecessary to the
subsequent transmissions, thus effectively reducing the batch transmission delay.
The implementation procedure of connection-oriented services includes connection
establishment, data transmission and connection release. Capable of setting up
coupling connections, the BSC6800 system provides the local reference function of
freezing the local node to prevent disordered connections when releasing the local
connection reference source.
2-34
II. Routing Function
The routing function of the BSC6800 system is to implement the addressing for SCCP
address information, more universal than the DPC routing function.
The SCCP address information covers:
z DPC
z DPC+SSN
Where, DPC is the one adopted by MTP while SSN is used to identify different SCCP
users (for example, ISUP, MAP, TCAP, and so on) in a node so as to compensate for
shortage of MTP users and broaden the addressing scope, thus to be applicable for
new services in the future. The routing function of the BSC6800 system can obtain
DPC+SSN or DPC by translation as required.
Upon receiving a message from the MTP, the SCCP route control part analyzes the
called address. If this node is the destination of this message, the SCCP will distribute
the message to the destination user. Otherwise, the SCCP will translate the address of
the message to form a new route flag and potential new called address and then send
them to the MTP.
Upon receiving a message from the connection-oriented control part or the
connectionless control part, the SCCP performs route analysis and then sends it to the
MTP part, the connection-oriented control part or the connectionless control part for
processing.
III. Management Function
The SCCP management function implements network maintenance by rerouting or

adjusting traffic volume in case of network fault or congestion. This function is realized
via the transmission of the SCCP management messages (by class-0 UDT) and
primitives. The SCCP management includes SP management, subsystem
management, harmonization between active/standby subsystems, broadcast of status
information, and status test of faulty subsystem.
If the SI of an MSU equals 0011, it means the message is an SCCP message. The
content of the SCCP message is located in the SIF of the MSU, as shown in Figure
2-15. The route flag of SCCP includes DPC, OPC and SLS.
2-35
Figure 2-15 SCCP message structure
2.5.4 Connection Request Message
2-36
II. Example
2-37

02-Chapter 2 Transport Network Layer Procedure Analysis PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

02-Chapter 2 Transport Network Layer Procedure Analysis PDF

Uploaded by

Copyright:

Available Formats

Protocols and Signalling Analysis

HUAWEI UMTS Radio Access Network Table of Contents

Chapter 2 Transport Network Layer Procedure Analysis ......................................................... 2-1

Huawei Technologies Proprietary

Chapter 2 Transport Network Layer Procedure

NBAP STC MTP3-B

Figure 2-1 SAAL structure

Huawei Technologies Proprietary

The SSCOP performs the following functions.

Huawei Technologies Proprietary

z Connection Control. This function performs the establishment, release, and

Huawei Technologies Proprietary

III. SSCOP Operation State

Huawei Technologies Proprietary

IV. SSCOP Connection Setup

The procedure of SSCOP connection setup is as follows:

AA-ESTABLISH.req PDU BGN

Figure 2-2 SSCOP connection setup

V. SSCOP Connection Release

The procedure of SSCOP connection release is as follows:

Huawei Technologies Proprietary

Figure 2-3 SSCOP connection release

VI. SSCOP Data Transmission and Error Recovery

- To release PDU1 and PDU2 from the buffer;

Huawei Technologies Proprietary

Figure 2-4 SSCOP data transmission

Huawei Technologies Proprietary

The SSCF performs the following functions.

0~47bytes 8 bits 8 bits 16 bits 32bits

Figure 2-5 CPCS-PDU format

The length of CPCS-PDU payload is variable within 1–65535 bytes.

Huawei Technologies Proprietary

z User-to-User Indication (UUI), used for the transparent transmission of

Huawei Technologies Proprietary

Huawei Technologies Proprietary

2.2.7 SSCOP Message

N(S) VT(S) is mapped to N(S) whenever a new SD or POLL PDU is

Information field The information field of an SD, MD, or UD PDU is mapped

N(PS) VT(PS) (after VT(PS) has been incremented) is mapped to

N(R) VR(R) is mapped to N(R) whenever a STAT or USTAT PDU is

N(MR) VR(MR) is mapped to N(MR) whenever a STAT, USTAT, RS,

SSCOP-UU The SSCOP-UU in a BGN, BGAK, BGREJ, END or RS PDU is

N(SQ) This field carries the connection sequence value. VT(SQ) is

PDU Type field PDU type

Huawei Technologies Proprietary

Huawei Technologies Proprietary

Figure 2-6 MTP3-B protocol structure

Message Discrimination is to identify the destination of a signalling message by

Huawei Technologies Proprietary

subsequent handling. If the local SP is not the destination and is capable of

II. Message Distribution

Message Distribution is to distribute the signalling message to the corresponding user

III. Message Routing

IV. Signalling Traffic Management

Signalling Traffic Management is to transfer signalling traffic over signalling links or

Huawei Technologies Proprietary

V. Signalling Route Management

Signalling route management is to ensure reliable interchange of signalling route

VI. Signalling Link Management

Signalling link management is to stop using an unavailable or unreliable link and

2.3.3 Message Structure

I. Service Information Octet (SIO)