ATIS-1000112.1-2005

1

Scope and field of application

2

Services provided by the SCCP

Partial

Class 2 and class 3 services are not implemented.

2.1

Connection-Oriented Services

None

Connection-oriented services are not supported.

2.1.1

Temporary Signaling Connections

None

See 2.1

2.1.1.1

Description

None

See 2.1

2.1.1.1.1

Connection Establishment Phase

None

See 2.1

2.1.1.1.2

Data Transfer Phase

None

See 2.1

2.1.1.1.3

Connection Release Phase

None

See 2.1

2.1.1.2

Network Service Primitives and Parameters

None

See 2.1

2.1.1.2.1

Overview

None

See 2.1

2.1.1.2.2

Connection Establishment Phase

None

See 2.1

2.1.1.2.3

Data Transfer Phase

None

See 2.1

2.1.1.2.4

Release Phase

None

See 2.1

2.1.1.2.5

Notice Service

None

See 2.1

2.1.1.3

Additional SCCP primitive and interface elements

None

See 2.1

2.1.1.3.1

Overview

None

See 2.1

2.1.1.3.2

Connection establishment interface elements

None

See 2.1

2.1.2

Permanent Signaling Connections

None

See 2.1

2.1.2.1

Description

None

See 2.1

2.1.2.2

Primitives and Parameters

None

See 2.1

2.2

Connectionless Service

Full

2.2.1

Description

Full

2.2.2

Primitives and Parameters of the Connectionless Service

Full

2.2.2.1

Overview

Full

2.2.2.2

Parameters

2.2.2.2.1

Address

Full

2.2.2.2.2

Quality of service parameter set

Full

2.2.2.2.3

Reason for Return

Full

2.2.2.2.4

User Data

Full

2.2.2.3

Primitives

2.2.2.3.1

N-UNITDATA

Full

2.2.2.3.2

N-NOTICE

Full

2.3

SCCP Management

2.3.1

Description

Full

2.3.2

Primitives and Parameters of the SCCP Management

2.3.2.1

Overview

Partial

N-COORD and N-TRAFFIC not supported

2.3.2.2

Parameters

2.3.2.2.1

Address

Full

2.3.2.2.2

Affected User

Full

2.3.2.2.3

User Status

None

Parameter ignored

2.3.2.2.3A

Traffic Mix

None

Parameter ignored

2.3.2.2.4

Subsystem Multiplicity Indicator

None

Parameter ignored

2.3.2.2.5

Affected DPC

Full

2.3.2.2.6

Signaling Point Status

Full

2.3.2.2.7

Confirm Status

None

Parameter ignored

2.3.2.3

Primitives

2.3.2.3.1

N-COORD

None

Not supported

2.3.2.3.2

N-STATE

Full

2.3.2.3.3

N-TRAFFIC

None

Not supported

2.3.2.3.4

N-PCSTATE

Full

3

Services Assumed from the MTP

Full

3.1

Description

Full

3.2

Primitives and Parameters

Full

3.2.1

MTP-TRANSFER

Full

3.2.2

MTP-PAUSE

Full

3.2.3

MTP-RESUME

Full

3.2.4

MTP-STATUS

Full

4

Functions Provided by the SCCP

Full

4.1

Connection-Oriented Functions

None

Connection-oriented functions are not implemented. See also 2.1

4.1.1

Functions for Temporary Signaling Connections

4.1.1.1

Connection Establishment Functions

None

Not compliant - see 4.1

4.1.1.2

Data Transfer Phase Functions

None

Not compliant - see 4.1

4.1.1.3

Release Phase Functions

None

Not compliant - see 4.1

4.1.2

Functions for Permanent Signaling Connections

4.1.2.1

Connection Establishment Phase and Connection Release Phase Functions

None

Not compliant - see 4.1

4.1.2.2

Data Transfer Phase Functions

None

Not compliant - see 4.1

4.2

Connectionless Service Functions

Full

1

Scope, Purpose and Application

2

Signaling Connection Control Part Message

Partial

Connection-oriented service messages are not supported.

2.1

Connection Confirm

None

Not compliant - see 2

2.2

Connection Request

None

Not compliant - see 2

2.3

Connection Refused

None

Not compliant - see 2

2.4

Data Acknowledgement

None

Not compliant - see 2

2.5

Data Form 1

None

Not compliant - see 2

2.6

Data Form 1

None

Not compliant - see 2

2.7

Expedited Data

None

Not compliant - see 2

2.8

Expedited Data Acknowledgement

None

Not compliant - see 2

2.9

Inactivity Test

None

Not compliant - see 2

2.10

Protocol Data Unit Error

None

Not compliant - see 2

2.11

Released

None

Not compliant - see 2

2.12

Release Complete

None

Not compliant - see 2

2.13

Reset Confirmation

None

Not compliant - see 2

2.14

Reset Request

None

Not compliant - see 2

2.15

Unitdata

Full

2.15A

Extended Unitdata

Full

2.15B

Long UnitData

Partial

Sending of LUDT is not implemented

2.16

Unitdata Service

Full

2.16A

Extended Unitdata Service

Full

2.16B

Long UnitData Service

Full

3

Messages for SCCP Subsystem Management

Partial

Subsystem-out-of-service-request, Subsystem-out-of-service-grant, system-backup-routing and system-normal-routing messages are not supported.

3.1

Subsystem Allowed

Full

3.2

Subsystem Prohibited

Full

3.3

Subsystem Status Test

Full

3.4

Subsystem Out Of Service Request

None

Message not supported

3.5

Subsystem Out Of Service Grant

None

Message not supported

3.6

Subsystem Backup Routing

None

Message not supported

3.7

Subsystem Normal Routing

None

Message not supported

3.8

Subsystem Routing Status Test

None

Message not supported

4

SCCP Parameters

4.1

Calling/Called Party Address

Full

4.2

Credit

None

Parameter not supported

4.3

Data

Full

4.4

Diagnostic

None

Parameter not supported

4.5

End of optional parameters

Partial

Only XUDT supports encoding this parameter.

4.6

Error cause

None

Not compliant - see 2

4.7

Local reference number (source/destination)

None

Parameter not supported.

4.8

Message type code

Full

4.9

Protocol class

Full

4.10

Receive sequence number

None

Not compliant - see 2

4.11

Refusal cause

None

Not compliant - see 2

4.12

Release cause

None

Not compliant - see 2

4.13

Reset cause

None

Not compliant - see 2

4.14

Return cause

None

Not compliant - see 2

4.15

Segmenting/reassembling

None

Not compliant - see 2

4.16

Segquencing/segmenting

None

Not compliant - see 2

4.17

SCCP hop counter

Partial

Parameter value is ignored

4.18

Segmentation

Full

4.19

Intermediate Signaling Network Identification

Partial

Parameter value is ignored

4.20

Long Data

Partial

Encoding is not implemented

4.21

Intermediate Network Selection

Partial

Parameter value is ignored

4.22

Message Type Interworking

Partial

Parameter value is ignored

5

Parameters For SCCP Subsystem Management

Full

5.1

Affected Subsystem Number

Full

5.2

Affected Point Code

Full

5.3

Subsystem Multiplicity Indicator

Full

6

Inclusion of Fields in the Messages

Full

1

Scope, Purpose and Applications

1.1

Routing label

Full

1.2

Message type code

Full

1.3

Formatting principles

Full

1.4

Mandatory fixed part

Full

1.5

Mandatory variable part

Full

1.6

Optional part

Full

1.7

End of optional parameters octet

Full

1.8

Order of transmission

Full

1.9

Coding of spare bits

Full

1.10

National message types and parameters

Full

2

Coding of the general parts

2.1

Coding of the message type

Partial

Class 3 and class 4 messages are not supported.

2.2

Coding of the length indicator

Full

2.3

Coding of the pointers

Full

3

SCCP Parameters

Partial

Only the parameters related to messages of class 0 and class 1 are supported.

3.1

End of optional parameters

Full

3.2

Destination local reference

None

Not compliant - see 3

3.3

Source local reference

None

Not compliant - see 3

3.4

Called party address

Full

3.4.1

Address indicator

Full

3.4.2

Address

Full

3.4.2.1

Subsytem number

Full

3.4.2.2

Signaling point code

Full

3.4.2.3

Global title

Full

3.4.2.3.1

Global Title Indicator = 0001

Full

3.4.2.3.2

Global Title Indicator = 0010

Full

3.5

Calling party address

Full

3.6

Protocol class

Full

3.7

Segmenting/reassembling

None

Not compliant - see 3

3.8

Receive sequence number

None

Not compliant - see 3

3.9

Sequencing/segmenting

None

Not compliant - see 3

3.10

Credit

None

Not compliant - see 3

3.11

Release cause

None

Not compliant - see 3

3.12

Return cause

None

Not compliant - see 3

3.13

Reset cause

None

Not compliant - see 3

3.14

Error cause

None

Not compliant - see 3

3.15

Refusal cause

None

Not compliant - see 3

3.16

Data

None

Not compliant - see 3

3.17

SCCP Hop Counter

Full

3.18

Segmentation

Full

3.19

Intermediate Signaling Network Identification

Partial

Encoding is not implemented

3.20

Long Data

Partial

Encoding is not implemented

3.21

Intermediate Network Selection

Partial

Encoding is not implemented

3.22

Message Type Interworking

Partial

Encoding is not implemented

4

SCCP Messages and Codes

4.1

General

4.2

Connection Request

None

Not compliant - see 3

4.3

Connection Confirm

None

Not compliant - see 3

4.4

Connection Refused

None

Not compliant - see 3

4.5

Released

None

Not compliant - see 3

4.6

Release Complete

None

Not compliant - see 3

4.7

Data Form 1

None

Not compliant - see 3

4.8

Data Form 2

None

Not compliant - see 3

4.9

Data Acknowledgement

None

Not compliant - see 3

4.10

Unitdata

Full

4.10A

Extended Unitdata

Full

4.10B

Long Uditdata

Partial

Encoding is not implemented

4.11

Unitdata Service

Full

4.11A

Extended Unitdata Service

Full

4.11B

Long Unitdata Service

Partial

Encoding is not implemented

4.12

Expedited Data

None

Not compliant - see 3

4.13

Expedited Data Acknowledgement

None

Not compliant - see 3

4.14

Reset Request

None

Not compliant - see 3

4.15

Reset Confirmation

None

Not compliant - see 3

4.16

Protocol Data Unit Error

None

Not compliant - see 3

4.17

Inactivity Test

None

Not compliant - see 3

5

SCCP Management Messages and Codes

5.1

General

Full

5.1.1

SCMG format identifier

Full

5.2

SCMG Message Parameters

5.2.1

End of Optional Parameters

5.2.2

Affected SSN

Full

5.2.3

Affected PC

Full

5.2.4

Subsystem multiplicity indicator

Partial

Encoding is not implemented.

5.3

SCMG Messages

Full

A.1

Introduction

Whilst normative, this is not applicable to the SCCP implementation

A.2

Assumptions

A.3

Definitions

A.4

Guidelines for Assigning Internetwork Translation Type Code Values

A.4.1

Constraints and Logistics

A.4.2

Determining Translation Type Needs

A.4.3

Determining the Application/Translation Group

A.5

Procedures for Requesting a Translation Type Code Assignment

A.5.1

Content of Proposal

A.5.2

Assignment of Translation Type Codes

1

Scope, Purpose and Application

1.1

General Characteristics of Signaling Connection Control Procedures

1.1.1

Purpose

1.1.2

Protocol Classes

Partial

Class 2 and class 3 are not supported

1.1.2.1

Protocol Class 0

Full

1.1.2.2

Protocol Class 1

Full

1.1.2.3

Protocol Class 2

None

1.1.2.4

Protocol Class 3

None

1.1.3

Signaling Connections

None

Connection-oriented protocol classes are not supported

1.1.4

Compatibility and Handling of Unrecognized Information

1.1.4.1

Rules for Forwards Compatibility

Full

1.1.4.2

Handling of Unrecognized Messages or Parameters

Full

1.1.4.3

Handling of Unsupported Optional Parameter Value

Full

1.1.4.4

Treatment of Spare Fields

Full

1.1.4.5

Handling of Gaps

Full

1.2

Overview of Procedures for Connection-Oriented Services

1.2.1

Connection Establishment

None

Connection-oriented services are not implemented

1.2.2

Data Transfer

None

Connection-oriented services are not implemented

1.2.3

Connection Release

None

Connection-oriented services are not implemented

1.3

Overview of Procedures for Connectionless Services

1.3.1

General

Partial

Acting as a relay node is not supported

1.4

Structure of the SCCP and Contents of Specification

Partial

Connection-oriented control is not implemented

2

Addressing and Routing

2.1

SCCP Addressing

Full

2.2

SCCP Routing Principles

Full

2.2.1

Receipt of SCCP Message Transferred by the MTP

Full

2.2.2

Messages from Connection-Oriented or Connectionless Control to SCCP Routing Control

Partial

Connection-oriented control is not implemented

2.2.2.1

DPC Present

Full

2.2.2.2

Translation Required

Full

2.3

SCCP Routing

2.3.1

Receipt of SCCP Message Transferred by the MTP

Partial

Connection-oriented services are not supported

2.3.2

Messages from Connectionless or Connection-Oriented Control to SCCP Routing Control

Partial

Connection-oriented control is not implemented

2.4

Routing Failures

Partial

Connection-oriented messages are not supported

2.5

Compatibility Test

Partial

Sending of LUDT messages is not supported

3

Connection-Oriented Procedures

Connection-oriented procedures are not supported

3.1

Connection Establishment

3.1.1

General

None

Not supported - see 3

3.1.2

Local Reference Numbers

None

Not supported - see 3

3.1.3

Negotiation Procedures

3.1.3.1

Protocol Class Negotiation

None

Not supported - see 3

3.1.3.2

Flow Control Credit Negotiation

None

Not supported - see 3

3.1.4

Actions at the Originating Node

3.1.4.1

Initial Actions

None

Not supported - see 3

3.1.4.2

Subsequent Actions

None

Not supported - see 3

3.1.5

Actions at a Relay Node with Coupling

3.1.5.1

Initial Action

None

Not supported - see 3

3.1.5.2

Subsequent Actions

None

Not supported - see 3

3.1.6

Actions at the Destination Node

3.1.6.1

Initial Actions

None

Not supported - see 3

3.1.6.2

Subsequent Actions

None

Not supported - see 3

3.2

Connection Refusal

None

Not supported - see 3

3.2.1

Actions at Node Initiating Connection Refusal

None

Not supported - see 3

3.2.1.1

Initiating Connection Refusal at the Destination Node

None

Not supported - see 3

3.2.1.2

Initiating Connection Refusal at a Relay Node

None

Not supported - see 3

3.2.1.3

Initiating Connection Refusal at the Originating Node

None

Not supported - see 3

3.2.2

Actions at a Relay Node Not Initiating Connection Refusal

None

Not supported - see 3

3.2.3

Actions at the Originating Node Not Initiating Connection Refusal

None

Not supported - see 3

3.3

Connection Release

Not supported - see 3

3.3.1

General

None

Not supported - see 3

3.3.2

Frozen Reference

None

Not supported - see 3

3.3.3

Actions at an End Node Initiating Connection Release

Not supported - see 3

3.3.3.1

Initial Actions

None

Not supported - see 3

3.3.3.2

Subsequent Actions

None

Not supported - see 3

3.3.4

Actions at a Relay Node

None

Not supported - see 3

3.3.4.1

Initial Actions

None

Not supported - see 3

3.3.4.2

Subsequent Actions

None

Not supported - see 3

3.3.5

Actions at an End Node Not Initiating Connection Release

None

Not supported - see 3

3.4

Inactivity Control

None

Not supported - see 3

3.5

Data Transfer

Not supported - see 3

3.5.1

General

None

Not supported - see 3

3.5.1.1

Actions at the Originating Node

None

Not supported - see 3

3.5.1.2

Actions at a Relay Node

None

Not supported - see 3

3.5.1.3

Actions at the Destination Node

None

Not supported - see 3

3.5.2

Flow Control

Not supported - see 3

3.5.2.1

General

None

Not supported - see 3

3.5.2.2

Sequence Numbering

None

Not supported - see 3

3.5.2.3

Flow Control Window

None

Not supported - see 3

3.5.2.4

Flow Control Procedures

Not supported - see 3

3.5.2.4.1

Transfer of DT 2 Messages

None

Not supported - see 3

3.5.2.4.2

Transfer of AK Messages

None

Not supported - see 3

3.5.2.4.3

Reception of a Data or AK Message

None

Not supported - see 3

3.5.3

Segmenting and Reassembly

None

Not supported - see 3

3.6

Expedited Data Transfer

3.6.1

General

None

Not supported - see 3

3.6.2

Actions at the Originating Node

None

Not supported - see 3

3.6.3

Actions at a Relay Node

None

Not supported - see 3

3.6.4

Actions at the Destination Node

None

Not supported - see 3

3.7

Reset

3.7.1

General

None

Not supported - see 3

3.7.2

Action at an End Node Initiating the Reset Procedure

3.7.2.1

Initial Actions

None

Not supported - see 3

3.7.2.2

Subsequent Actions

None

Not supported - see 3

3.7.3

Actions at a Relay Node

3.7.3.1

Initial Actions

None

Not supported - see 3

3.7.3.2

Subsequent Actions

None

Not supported - see 3

3.8

Restart

3.8.1

General

None

Not supported - see 3

3.8.2

Actions at the Recovered Node

3.8.2.1

Initial Actions

None

Not supported - see 3

3.8.2.2

Subsequent Actions

None

Not supported - see 3

3.9

Permanent Signaling Connections

None

Not supported - see 3

3.10

Abnormalities

3.10.1

General

None

Not supported - see 3

3.10.2

Syntax Error

None

Not supported - see 3

3.10.3

Action Tables

None

Not supported - see 3

3.10.4

Action Upon the Reception of an ERR Message

None

Not supported - see 3

4

Connectionless Procedures

Full

Relax usage of LUDT/LUDTS messages

4.1

Data Transfer

Partial

Only UDT, UDTS, XUDT and XUDTS messages are sent

4.1.1

Segmentation/Reassembly

4.1.1.1

Segmentation

4.1.1.1.1

General

Partial

LUDT is not supported

4.1.1.1.2

Normal Procedures

Partial

LUDT is not supported

4.1.1.1.3

Return on Error Procedures

Partial

LUDT and LUDTS are not supported

4.1.1.2

Reassembly

4.1.1.2.1

General

Partial

LUDT is not supported

4.1.1.2.2

Normal Procedures

Partial

LUDT is not supported

4.1.1.2.3

Return on Error Procedures

Full

LUDT and LUDTS are not supported

4.1.2

Message Change

None

4.1.2.1

UDT(S)/XUDT(S) Change Procedures

None

Message change is not supported

4.1.2.1.1

SCCP Relay Node

4.1.2.1.1.1

UDT(S) to XUDT(S) Message Change

None

Relay Node operation is not supported

4.1.2.1.1.2

XUDT(S) to UDT(S) Mesasge Change

None

Relay Node operation is not supported

4.1.2.1.2

XUDT(S) capable end node

None

Message change is not supported

4.1.2.1.3

Message Change Error Procedures

None

Message change is not supported

4.2

Message Return

Full

4.3

Syntax Error

Full

5

SCCP Management Procedures

5.1

General

Full

5.2

Signaling Point Status Management

5.2.1

General

Full

5.2.2

Signaling Point Prohibited

Partial

Traffic Information Management is not supported

5.2.3

Signaling Point Allowed

Partial

Traffic Information Management is not supported

5.2.4

Signaling Point Congested

Full

5.2.5

SCCP Reaction to Local MTP Restart

Full

5.3.2

Subsystem Prohibited

5.3.2.1

Receipt of Message for a Prohibited Subsystem

Full

5.3.2.2

Receipt of Subsystem-Prohibited Message or N-STATE Request Primitive or Local User Failed

Partial

Traffic Information Management is not supported

5.3.3

Subsystem Allowed

Partial

Traffic Information Management is not supported

5.3.4

Subsystem Status Test

5.3.4.1

General

Full

5.3.4.2

Actions at the Initiating Node

Full

5.3.4.3

Actions at the Receiving Node

Full

5.3.5

Coordinated State Change

5.3.5.1

General

None

Coordinated state change is not supported

5.3.5.2

Actions at the Requesting Node

None

Coordinated state change is not supported

5.3.5.3

Actions at the Requested Node

None

Coordinated state change is not supported

5.3.6

Local Broadcast

5.3.6.1

General

None

Not compliant. Procedure is not supported.

5.3.6.2

User-out-of-service

None

Not compliant - see 5.3.6.1

5.3.6.3

User-in-service

None

Not compliant - see 5.3.6.1

5.3.6.4

Signaling Point Inaccessible

None

Not compliant - see 5.3.6.1

5.3.6.5

Signaling Point Accessible

None

Not compliant - see 5.3.6.1

5.3.6.6

Signaling Point Congested

None

Not compliant - see 5.3.6.1

5.3.6.7

SCCP Inaccessible

None

Not compliant - see 5.3.6.1

5.3.6.8

SCCP Accessible

None

Not compliant - see 5.3.6.1

5.3.7

Broadcast

5.3.7.1

General

Full

5.3.7.2

Subsystem Prohibited

Partial

Only for local subsystem

5.3.7.3

Subsystem Allowed

Partial

Only for local subsystem

5.4

Traffic Information Management

None

Traffic Information Management is not implemented

5.4.1

General

None

Not compliant - see 5.4

5.4.2

Traffic Mix Procedures

None

Not compliant - see 5.4

5.4.2.1

End-Node/Database

5.4.2.1.1

Traffic-Mix Information

None

Not compliant - see 5.4

5.4.2.1.2

Subsystem Backup Routing

None

Not compliant - see 5.4

5.4.2.1.3

Subsystem Normal Routing

None

Not compliant - see 5.4

5.4.3

Calculation of Traffic-Mix Information

5.4.3.1

General

None

Not compliant - see 5.4

5.4.3.2

End-Node/Database

None

Not compliant - see 5.4

5.4.4

Subsystem Routing Status Test

5.4.4.1

General

None

Not compliant - see 5.4

5.4.4.2

Actions at the Initiating Node

None

Not compliant - see 5.4

5.4.4.3

Actions at the Receiving Node

None

Not compliant - see 5.4

5.5

SCCP Flow Control

5.5.1

General

Full

5.5.2

SCCP Prohibited Control

Full

5.5.3

SCCP Allowed Control

Full

5.5.4

SCCP Status Test

Full

5.6

SCCP Restart

Full

D

Intermediate Signaling Network Identification Features

None

ISNI is not implemented

D.1

Protocol and Procedural Assumptions

None

Not compliant - see D

D.2

Procedures for ISNI Constrained Routing

None

Not compliant - see D

D.2.1

Actions at the Origination SEP

None

Not compliant - see D

D.2.2

Actions at an ISNI-Capable SCCP Relay Node

D.2.2.1

Invocation of the ISNI Routing Function

None

Not compliant - see D

D.2.3

Actions at a Not-ISNI-Capable SCCP Relay Node

None

Not compliant - see D

D.2.4

Actions at the Destination SEP

None

Not compliant - see D

D.2.5

Error Conditions

None

Not compliant - see D

D.3

Procedures for Identification

D.3.1

Actions at the Origination SEP

None

Not compliant - see D

D.3.2

Actions at an ISNI-Capable SCCP Relay Node

D.3.2.1

Invocation of the Identification Function

None

Not compliant - see D

D.3.3

Actions at a Not-ISNI-Capable SCCP Relay Node

None

Not compliant - see D

D.3.4

Actions at the Destination SEP

None

Not compliant - see D

D.3.5

Error Conditions

None

Not compliant - see D

D.4

Error Handling Procedures (Message Return)

None

Not compliant - see D

D.4.1

Procedures for Deriving the XUDTS Message

None

Not compliant - see D

D.4.2

Procedures at SCCP Relay Nodes

D.4.2.1

Actions at an ISNI-Capable SCCP Relay Node

D.4.2.1.1

Invocation of the ISNI Routing Function

None

Not compliant - see D

D.4.2.1.2

Invocation of the ISNI Identification Function

None

Not compliant - see D

D.4.2

Actions at a Not-ISNI-Capable SCCP Relay Node

None

Not compliant - see D

D.4.3

Actions at the Destination Node

None

Not compliant - see D

E

Intermediate Signaling Network Identification SDL

None

Not compliant - see D

F

Examples of ISNI Message Content

None

Not compliant - see D

G.

Intermediate Network Signaling (INS) Procedures

None

INS is not implemented

G.1

Protocol and Procedural Assumptions

None

Not compliant - see G

G.2

Formats of the Optional SCCP INS Parameter

None

Not compliant - see G

G.3

Procedures for Routing Using the INS Capability

G.3.1

Actions at the Origination SEP

None

Not compliant - see G

G.3.2

Actions at the INS Capable SCCP Relay Node

G.3.2.1

Invocation of the INS Function

None

Not compliant - see G

G.3.3

Actions at a Non-INS-Capable SCCP Relay Node

None

Not compliant - see G

G.3.4

Actions at the Destination SEP

None

Not compliant - see G

G.3.5

Abnormal Procedures

G.3.5.1

Actions at an INS-Capable SCCP Relay Node

None

Not compliant - see G

G.3.6

Error Conditions

None

Not compliant - see G

G.4

Error Handling Procedures

None

Not compliant - see G

G.5

Procedures for Deriving the XUDTS Message

None

Not compliant - see G

G.6

SDL

None

Not compliant - see G