SAAL SSCF SSCOP for ITU

1	General
1.1	Introduction
1.2	Terms
1.3	Concept
1.4	History
2	Compliance Lists
2.1	SSCOP (ITU Q.2110)
3	Notes
Reference List

1 General

1.1 Introduction

Ericsson AB SSCOP ITU version R1 is compliant with the ITU-T standard Reference [1] according to the table in this document.

1.2 Terms

ATM		Asynchronous Transfer Mode

B-ISDN		Broadband Integrated Services Network

CPCS		Common Part Convergence Sublayer

ITU		International Telecommunication Union

PC		Protocol Capabilities

PDU		Protocol Data Unit

PICS		Protocol Implementation Conformance Statement

SDL		Specification and Description Language

SDU		Service Data Unit

SoC		Statement of Compliance

SP		System Parameters

SSCF		Service Specific Coordination Function

SSCOP		Service Specific Connection Oriented Protocol

SSCS		Service Specific Convergence Sublayer

1.3 Concept

This section will explain the different concepts that will be used in the compliance lists. The terms that are used are:

C		Ericsson module complies with the specified paragraph in the standard.

N		Ericsson module does not comply with the specified paragraph in the standard.

P		Ericsson module complies partly with the specified paragraph in the standard. Specify in a note what in the module that does comply and what that does not.

-		There is nothing to implement in the referred paragraph (used in column “C”).

1.4 History

Table 1 Revision History
Revision	Date	Author	Comment
A	2002–08–16	Mats Jarlstedt	Approved after document inspection.
B	2007-02-19	XMRALBA	Converted to XML format
C	2007-09-27	XMREVEF	Minor changes

2 Compliance Lists

2.1 SSCOP (ITU Q.2110)

Table 2 Compliance List, SSCOP (ITU Q.2110)
References		C	P	Comments
1.	Scope	-
2.	Normative references	-
3.	Abbreviations	-
4.	General	-
5.	Functions of the SSCOP	X
6.	Elements for layer to layer communication	-
6.1	Signals between SSCOP and SSCF, and SSCOP and SSCS layer management	X
6.1.1	Signal definition	X
6.1.2	Parameter definition	X
6.2	State transition diagram for sequences of signals	X
6.3	Signals between SSCOP and CPCS	X
7.	Protocol elements for peer-to-peer communications	-
7.1	SSCOP PDUs	X
7.2	SSCOP PDU formats	X
7.2.1	Coding conventions	X
7.2.2	Padding (PAD) field	X
7.2.3	Reserved field	X
7.2.4	PDU length	X
7.2.5	STAT and USTAT PDU codings	X
7.3	States of SSCOP protocol entity	X
7.4	SSCOP state variable	X
7.5	SSCOP PDU parameters	X
7.6	SSCOP timers	X
7.7	SSCOP parameters	X
7.8	SSCOP credit and flow control	X
7.8.1	Credit and peer-to-peer flow control	X
7.8.2	Local flow control		X	See Note 1.
8.	Specification of SSCOP	-
8.1	Overview	X
8.1.1	Idle	X
8.1.2	Establishment and release	X
8.1.3	Bidirectional re-synchronization	X
8.1.4	Recovery	X
8.1.5	Data transfer	X
8.2	SDL diagrams	X
Annex A, Management error indications		-
Annex B, Protocol Implementation conformance Statement (PICS) pro forma to Recommendation Q.2110		-
B.1	General	-
B.2	Abbreviations and special symbol	-
B.3	Instructions for completing the PICS proforma	-
B.4	Global statement of conformance	-
B.5	SSCOP Q.2110	-
B.5.1	Protocol Capabilities (PC) SSCOP	-
B.5.2	SSCOP PDUs Protocol Data Units (PD)	-
B.5.3	SSCOP System Parameters (SP)	-
Annex I, Concepts and terminology		-
Annex II, Examples of SSCOP operation		-
Annex III, Summary of buffer and state variable management		-
Annex IV, Default window size for SSCOP		-

3 Notes

Note:: Flow control of PDUs to layer 1 is not implemented in SSCOP. The interface to layer 1 is hardware dependent. Transmission priority between connection and data signals is not supported.

Reference List

ITU Standards
[1] [ITU-1] International Telecommunication Union, Telecommunication Standardization Sector of ITU. Broadband ISDN. B-ISDN ATM Adaptation Layer - Service Specific Connection Oriented Protocol (SSCOP), ITU-T, Recommendation Q.2110 (07/94)