Empty cells are descriptive text only

Description Compliance Notes

1

Introduction

1.1

General characteristics of signalling connection control procedures

1.1.1

Purpose

1.1.2

Protocol classes

Partial

Connection-oriented services are not implemented.

1.1.2.1

Protocol class 0

Full

1.1.2.2

Protocol class 1

Full

1.1.2.3

Protocol class 2

None

Connection-oriented services are not implemented.

1.1.2.4

Protocol class 3

None

Connection-oriented services are not implemented.

1.1.3

Signalling connections

Full

1.1.4

Compatibility and handling of unrecognized information

1.1.4.1

Rules for compatibility

Full

1.1.4.2

Handling of unrecognized messages or parameters

Full

1.1.4.3

Handling of non-mandatory unsupported parameter values

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.3.2

Segmentation/reassembly

Full

1.4

Structure of the SCCP and contents of this Recommendation

Partial

Connection-oriented control is not implemented.

2

Addressing and routing

2.1

SCCP addressing principles

Full

2.2

SCCP routing principles

Full

2.2.1

Receipt of SCCP message transferred by the MTP

Full

2.2.2

Messages passed from connection-oriented or connectionless control to SCCP routing control

Full

2.2.2.1

DPC present

Full

2.2.2.2

DPC not present

Full

2.3

SCCP routing procedures

2.3.1

Receipt of SCCP messages transferred by the MTP

Partial

Connection-oriented services are not implemented.

2.3.2

Messages from connectionless or connection-oriented control to SCCP routing control

Partial

Connection-oriented control is not implemented.

2.4

Global title translation

2.4.1

General characteristics of the GTT

Full

2.4.2

Terminology definitions

2.4.2.1

GT information

Full

2.4.2.2

Other definitions used in the GTT function

Full

2.4.3

Input of the GTT function

Full

2.4.3.1

Local information (mandatory input)

Full

2.4.3.2

GT information (mandatory input)

Full

2.4.3.3

SSN (mandatory input if present)

Full

2.4.3.4

Loadsharing information

Full

2.4.4

Output of the GTT function

Full

2.4.5

Global title translation function

Full

2.5

Compatibility test

Partial

Sending of LUDT/LUDTS messages is not supported.

2.6

Traffic limitation mechanism

Full

2.6.1

General

Full

2.6.2

Importance of a message

Partial

Acting as a relay node is not supported.

2.6.3

Handling of messages to a congested node

Full

2.7

Calling party address treatment

2.7.1

Address indicator

Full

2.7.2

Calling party address in the international network

None

For further study.

2.7.3

Routing indicator

Full

2.7.4

Screening

None

Screening is not supported

2.7.5

Inclusion of OPC in the calling party address

Full

2.7.5.1

LUDT or FullUDT or UDT message

Full

2.7.5.2

CR message

None

Connection-oriented services are not implemented.

2.8

Routing failures

Partial

Connection-oriented services are not implemented.

2.8.1

No translation for an address of such nature

Full

2.8.2

No translation for this specific address

Full

2.8.3

MTP/SCCP/subsystem failure

Full

2.8.4

MTP/SCCP/subsystem congestion

Partial

Only as N-NOTICE.

2.8.5

Unequipped user

Full

2.8.6

Hop counter violation

None

Hop counting 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 actions

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

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

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

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

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

3.5.2.4.1

Transfer of DT2 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.7.4

Actions at an end node not initiating the reset procedure

None

Not supported - see 3

3.7.5

Handling of messages during the reset procedures

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.8.3

Actions at the non-failed far end node

None

Not supported - see 3

3.8.3.1

Permanent signalling connections

None

Not supported - see 3

3.8.3.2

Abnormalities

3.8.3.3

General

None

Not supported - see 3

3.8.4

Syntax error

None

Not supported - see 3

3.8.5

Action tables

None

Not supported - see 3

3.8.6

Actions 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

Full

4.1.1.1.2

Normal procedures

Partial

LUDT is not supported.

4.1.1.1.3

Message return procedure

Partial

LUDT and LUDTS are not supported.

4.1.1.1.3.1

Segmentation not supported.

Full

4.1.1.1.3.2

Segmentation failed

None

LUDT is 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

Message return procedure

Partial

LUDT is not supported.

4.1.1.2.3.1

Destination cannot perform reassembly

Full

4.1.1.2.3.2

Error in message transport

Full

4.1.1.2.3.3

Error in local processing

Full

4.1.1.2.3.4

No buffer space to perform reassembly

Full

4.1.2

Message change

Partial

Only LUDTS in UDTS.

4.2

Message return procedure

Full

4.3

Syntax error

Full

5

SCCP management procedures

5.1

General

Full

5.2

Signalling point status management

5.2.1

General

Full

5.2.2

Signalling point prohibited

Full

5.2.3

Signalling point allowed

Full

5.2.4

Signalling point congested

Full

5.2.5

Local MTP network availability

Full

5.2.6

Local MTP network unavailability

None

MTP restart procedure not supported

5.2.7

SCCP reports of SCCP and nodal congestion

Full

5.2.7.1

Actions in the congested SCCP node

None

SSC message sending is not supported

5.2.7.2

Action in a relay or originating node

Full

5.2.8

Inter- and Intra- SCMG congestion reports procedure

Full

5.3

Subsystem status management

5.3.1

General

Full

5.3.2

Subsystem prohibited

Full

5.3.2.1

Receipt of messages for a prohibited subsystem (response method)

Full

5.3.2.2

Receipt of Subsystem-Prohibited message or N-STATE request primitive or local user failed

Partial

N-STATE not supported.

5.3.3

Subsystem allowed

Partial

N-STATE not supported.

5.3.4

Subsystem status test

5.3.4.1

General

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

Not supported.

5.3.5.1

General

None

Not compliant. Procedure is not supported

5.3.5.2

Actions at the requesting node

None

Not compliant - see 5.3.5.1

5.3.5.3

Actions at the requested node

None

Not compliant - see 5.3.5.1

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

Signalling point inaccessible

None

Not compliant - see 5.3.6.1

5.3.6.5

Signalling point or remote SCCP accessible

None

Not compliant - see 5.3.6.1

5.3.6.6

Restricted importance level reporting

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

MTP/SCMG restart

Full

Previous page Next page