S tandard ECMA-318 December 2000
Standardizing Information
and
Communication
Systems
Private Integrated Services Network (PISN) Use of QSIG at the C Reference Point between a PINX and an Interconnecting Network
Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected]
.
Draft S tandard ECMA-318 December 2000
Standardizing
Information
and
Communication
Systems
Private Integrated Services Network (PISN) Use of QSIG at the C Reference Point between a PINX and an Interconnecting Network
Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected] IW
ECMA-318.DOC
30-01-01 13,59
.
Brief History
This Standard is one of a series of ECMA Standards defining services and signalling protocols applicable to Private Integrated Services Networks (PISNs). The series uses ISDN concepts as developed by ITU-T and conforms to the framework of International Standards for Open Systems Interconnection as defined by ISO/IEC. It has been produced under ETSI work item DEN/ECMA-00213. This Standard specifies the functional profile for interconnecting Private Integrated services Network eXchanges (PINX) to VPN service centers to permit interoperability between equipment from different vendors and service providers. This Standard is based upon the practical experience of ECMA member companies and the results of their active and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and regional standardization bodies. It represents a pragmatic and widely based consensus. This ECMA Standard is contributed to ISO/IEC JTC1 under the terms of the fast-track procedure, for adoption as an ISO/IEC International Standard. Thereafter it is proposed to ETSI for endorsement as an EN by means of the One Step Approval Procedure (OAP).
This ECMA Standard has been adopted by the General Assembly of December 2000.
- i -
Table of contents 1
Scope
1
2
Conformance
1
3 3.1 3.2
References (normative) Re f e r e n c e s o f g e n e r a l s i g n i f i c a n c e Re f e r e n c e s to s u p p le me n ta r y s e r v ic e s a n d A N F s
1 2 3
4.1 4.2 4.3
Definitions E x te r n a l d e f in itio n s I n te r c o n n e c tin g N e tw o r k Virtual Transit PINX
3 3 4 4
5
Acronyms
4
6
Specification framework Scenarios
5 5
Physical interfaces and protocol stack at the C reference point
6
4
6.1 7 8
9
La y e r 1 R e q u i r e m e n t s 8.1 General 8 . 2 Ba s i c A c c e s s ( 2 x B 6 4 + D 1 6 ) 8 . 3 P r i ma r y R a t e A c c e s s 8.3.1 2 0 4 8 k b i t / s P r i ma r y R a t e A c c e s s ( 3 0 x B 6 4 + D 6 4 ) 8.3.2 1 5 4 4 k b i t / s P r i ma r y R a t e I n t e r f a c e ( 2 3 x B 6 4 + D 6 4 ) La y e r 2 R e q u i r e m e n t s
10 Layer 3 Requirements 10.1 General 10.1.1 A d d r e s s in g a n d Ro u te in g 10.2 Ba s i c C a l l 10.2.1 S e g me n ta tio n a n d r e a s s e mb ly 10.2.2 Ch a n n e l I d e n tif ic a tio n 10.2.3 En-bloc, Overlap Sending / Receiving 10.2.4 S u b - a d d r e s s in g 10.2.5 Ca u s e s 10.2.6 Be a r e r S e r v i c e s 10.2.7 P r o g r e s s I n d ic a to r 10.2.8 Co d e s e t 10.3 G e n e r ic F u n c tio n a l P r o to c o l ( G F ) 10.3.1 I mp o r ta n t is s u e s f r o m th e P I S N p o in t o f v ie w
6 6 6 6 7 7 7 7 7 7 7 8 8 8 8 8 8 8 9 9 9
- ii -
10.4 S u p p l e me n t a r y S e r v i c e s a n d A d d i t i o n a l N e t w o r k F e a t u r e s 10 10.4.1 P r o c e d u r e s r e q u ir e d a t th e v ir tu a l tr a n s it P I N X f o r A d v ic e o f Ch a r g e ( A O C) 10 10.4.2 P r o c e d u r e s r e q u ir e d a t th e v ir tu a l tr a n s it P I N X f o r Ca ll D iv e r s io n ( CF B, CF N R, CFU) 10 10.4.3 P r o c e d u r e s r e q u ir e d a t th e v ir tu a l tr a n s it P I N X f o r Ca ll T r a n s f e r ( CT ) 10 10.4.4 P r o c e d u r e s r e q u i r e d a t t h e v i r t u a l t r a n s i t P I N X f o r P a t h R e p l a c e me n t ( P R ) 10 10.4.5 P r o c e d u r e s r e q u ir e d a t th e v ir tu a l tr a n s it P I N X f o r Ca ll I n te r c e p tio n ( CI N T ) 10 10.4.6 P r o c e d u r e s r e q u ir e d a t th e v ir tu a l tr a n s it P I N X f o r T r a n s it Co u n te r ( T C) 10 10.4.7 P r o c e d u r e s r e q u ir e d a t th e v i r t u a l tr a n s i t P I N X f o r P r i v a t e U s e r Mo b i l i t y - Ca l l H a n d lin g ( P U MCH ) 11 10.4.8 P r o c e d u r e s r e q u ir e d a t th e v i r t u a l tr a n s i t P I N X f o r C o r d l e s s T e r mi n a l Mo b i l i t y Call Handling (CTMI / CTMO) 11 10.4.9 P r o c e d u r e s r e q u ir e d a t th e v ir tu a l tr a n s it P I N X f o r S in g le S te p Ca ll T r a n s f e r (SSCT) 11 1 0 . 4 . 1 0 P r o c e d u r e s r e q u ir e d a t th e v ir tu a l tr a n s it P I N X f o r Ca ll P r io r ity I n te r r u p tio n (CPI) 11 10.5 K e yp a d a n d F e a tu r e k e y P r o c e d u r e s 11 Annex A - Requirements List (RL)
13
Annex B - Profile specific ICS proforma
21
1
Scope This Profile Standard specifies the combination of base standards, together with the selection of appropriate options and parameter values, necessary to specify how QSIG / PSS1 can be used to provide digital signalling capabilities at interfaces at the C reference point between a Private Integrated services Network eXchange (PINX) and an Interconnecting Network (ICN) to permit interoperability between equipment from different vendors and different public or private service providers. NOTE 1 PINX in the sense of this Standard is used in the meaning of a PINX directly attached to the ICN. This Standard is applicable to attached PINXs and Interconnecting Networks (ICN). This Standard identifies the necessary or optional employment of particular functions, procedures and services when provided: -
physical and electrical characteristics (physical layer) of the interfaces to the transmission systems to be employed;
-
data link layer procedures;
-
network layer procedures; and
-
supplementary services and additional network features to meet specific corporate network user requirements.
This Standard states requirements upon attached PINXs and Interconnecting Network (ICN) implementations in order to achieve interoperability between equipment in PISNs serving as Corporate telecommunication Networks (CNs). NOTE 2 Implementation of this Standard does not preclude a manufacturer from offering other means of interconnection. It also does not preclude a VPN service provider to offer basic call communications between a PINX and other networks like PSTN or ISDN. ISO/IEC TR 14475 specifies various access arrangements between a PINX and a public network where reference points C and T reside either at a single or at separate interfaces. The scope of this Standard is limited to cover the C reference point aspects at a separate interface. The current version of this Standard does not intend to specify any gateway or end PINX requirements for the ICN side of the interface. Therefore it typically uses the term "virtual transit PINX" instead of Interconnecting Network (ICN).
2
Conformance A system conforms to this Standard if it correctly performs all the mandatory capabilities defined in the requirement list (RL) (annex A) and the profile specific ICS (annex B). NOTE 3 For the purpose of this Standard capabilities marked as optional in the base standards may be mandatory or excluded.
3
References (normative) The following standards contain provisions which, through reference in this text, constitute provisions of this Standard. All standards are subject to revision, and parties involved are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. Standards organizations maintain registers of currently valid standards. In the case of references to ECMA Standards that are aligned with ISO/IEC International Standards, the number of the appropriate ISO/IEC International Standard is given in brackets after the title of the ECMA reference. For the purpose of this Standard dated references point at the earliest applicable editions.
- 2 -
3.1
References of general significance ECMA-133
Private Integrated Services Network (PISN) - Reference Configuration for PISN Exchanges (PINX) (1998) (International Standard ISO/IEC 11579-1)
ECMA-143
Private Integrated Services Network (PISN) - Circuit Mode Bearer Services - InterExchange Signalling Procedures and Protocol (1997) (International Standard ISO/IEC 11572)
ECMA-155
Private Integrated Services Network - Addressing (1997) (International Standard ISO/IEC 11571)
ECMA-165
Private Integrated Services Network (PISN) - Generic Functional Protocol for the Support of Supplementary Services - Inter-Exchange Signalling Procedures and Protocol (1997) (International Standard ISO/IEC 11582)
ECMA-226
Private Integrated Services Network (PISN) - Mapping Functions for the Employment of Dedicated Circuit Mode Connections as Inter-PINX Connections (1995)
ECMA-253
Private Integrated Services Network (PISN) - Mapping Functions for the Employment of 64 kbit/s Circuit Mode Connections with 16 kbit/s Sub-Multiplexing (2000)
EN 300 172
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit mode basic services [ISO/IEC 11572 (1996) modified] (1997)
ETS 300 239
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Generic functional protocol for the support of supplementary services [ISO/IEC 11582 (1995) modified] (1995)
EN 300 402-4
Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 4: Protocol Implementation Conformance Statement (PICS) proforma specification for the general protocol (1999)
ISO/IEC 9646-7
Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements (1995)
ISO/IEC 11572
Information technology - Telecommunications and information exchange between systems - Private Integrated Services Network - Circuit mode bearer services Inter-exchange signalling procedures and protocol (1997)
ISO/IEC 11572
Amendment 1: Segmentation and reassembly (1997)
ISO/IEC 11572
Amendment 2: Additional progress descriptions (1997)
ISO/IEC 11582
Information technology - Telecommunications and information exchange between systems - Private Integrated Services Network - Generic functional protocol for the support of supplementary services - Inter-exchange signalling procedures and protocol (1995)
ISO/IEC 14474
Information technology - Telecommunications and information exchange between systems - Private Integrated Services Network - Functional requirements for static circuit-mode inter-PINX connections (1998)
ISO/IEC TR 14475
Information technology - Telecommunications and information exchange between systems - Private Integrated Services Network - Architecture and Scenarios for Private Integrated Services Networking (1996)
ITU-T Rec. E.164
The international public telecommunication numbering plan (1997)
ITU-T Rec. I.112
Vocabulary of terms for ISDNs (1993)
ITU-T Rec. I.130
Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN (Blue Book) (1988)
- 3 -
ITU-T Rec. I.140
Attribute technique for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN (1993)
ITU-T Rec. I.210
Principles of telecommunication services supported by an ISDN and the means to describe them (1993)
ITU-T Rec. I.430
Basic user-network interface - Layer 1 specification (1995)
ITU-T Rec. I.431
Primary rate user-network interface - Layer 1 specification (1993)
ITU-T Rec. Q.920
Digital Subscriber Signalling System No. 1 (DSS1) - ISDN user-network interface data link layer - General aspects (1993)
Amendment to Q.920 New Annex A (2000) ITU-T Rec. Q.921
ISDN user-network interface - Data link layer specification (1997)
Amendment to Q.921 New Annex J (2000)
3.2
4
References to supplementary services and ANFs ECMA-174
Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Call Diversion Supplementary Services (CFB, CFNR, CFU) (International Standard ISO/IEC 13873)
ECMA-176
Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Path Replacement Additional Network Feature (PR) (International Standard ISO/IEC 13874)
ECMA-178
Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Call Transfer Supplementary Service (CT) (International Standard ISO/IEC 13869)
ECMA-212
Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Advice of Charge Supplementary Services (AOC) (International Standard ISO/IEC 15050)
ECMA-215
Private Integrated Services Network (PISN) - Cordless Terminal Mobility (CTM) Inter-Exchange Signalling Protocol - Cordless Terminal Incoming Call Additional Network Feature (CTMI, CTMO)
ECMA-221
Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Call Interception Additional Network Feature (CINT) (International Standard ISO/IEC 15054)
ECMA-225
Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Transit Counter Additional Network Feature (TC) (International Standard ISO/IEC 15056)
ECMA-264
Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Call Priority Interruption and Call Priority Interruption Protection Supplementary Services (SSCPI) (International Standard ISO/IEC 15992)
ECMA-284
Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Private User Mobility (PUM) - Call Handling Additional Network Feature (PUMCH) (International Standard ISO/IEC 17878)
ECMA-300
Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Single Step Call Transfer Supplementary Service (SSCT) (International Standard ISO/IEC DIS 19460)
Definitions For the purposes of this Standard, the following definitions apply.
4.1
External definitions This Standard uses the following terms defined in other documents:
- 4 -
4.2
– Attached PINX
(ISO/IEC 14475)
– Destination PINX
(ECMA-165)
– End PINX
(ECMA-165)
– Gateway PINX
(ECMA-143)
– Incoming Call
(ECMA-143)
– Inter-PINX Connection
(ECMA-253)
– Inter-PINX Link
(ECMA-253)
– Originating PINX
(ECMA-143)
– Outgoing Call
(ECMA-143)
– Preceding PINX
(ECMA-165)
– Private Integrated Services Network (PISN)
(ECMA-133)
– Private Integrated Services Network Exchange (PINX)
(ECMA-133)
– C reference point
(ECMA-133)
– Q reference point
(ECMA-133)
– Side, Incoming Side and Outgoing Side
(ECMA-143)
– Source PINX
(ECMA-165)
– Subsequent PINX
(ECMA-165)
– Terminating PINX
(ECMA-143)
– Transit PINX
(ECMA-143)
Interconnecting Network Interconnecting Network (ICN): That part of a third party provided network, e.g. a public network, which provides the functions needed to interconnect PINXs. The functionality of the ICN includes transit PINX functionality, associated transmission capabilities and may include gateway PINX functionality.
4.3
Virtual Transit PINX Virtual Transit PINX: an Interconnecting Network performing only Transit PINX functions.
5
Acronyms ANF
Additional Network Feature
APDU
Application Protocol Data Unit
ASN.1
Abstract Syntax Notation One
BC
Basic Call
CN
Corporate telecommunication Network
EN
European Norm
ETS
European Telecommunication Standard
GF
Generic Functional protocol (for the support of supplementary services)
GW
GateWay
i
Irrelevant
ICN
InterConnecting Network
M, m
Mandatory
MP
MaPping
- 5 -
6
N/A, n/a
Not Applicable
NFE
Network Facility Extension
O, o
Optional
o.i
Optional, qualified
PINX
Private Integrated services Network eXchange
PISN
Private Integrated Services Network
PNP
Private Numbering Plan
PSTN
Public network infrastructure
QSIG
Q reference point SIGnalling system
RL
Requirements List
SS
Supplementary Service
SM/SREJ
Set Mode / Selective REJect
TCC
Transit Call Control
TEI
Terminal Endpoint Identifier
UDI
Unrestricted Digital Information
VPN
Virtual Private Network
X
Not supported / not used
x
eXcluded
Specification framework
6.1
Scenarios Figure 1 below shows an example scenario where the Interconnecting Network (ICN) is located within a public network and provides virtual transit PINX functionality.
T GW TE
S
Public network / PSTN
S/T TE
Public ISDN
PINX A
C C
Q
PINX B
ICN
TE
S
MP C
PINX C
TE
S
Scope of this Standard
F ig u r e 1 - Ex a m p le S c e n a r io
- 6 -
7
Physical interfaces and protocol stack at the C reference point Figure 1 above also shows the "C reference points" at which physical interfaces may occur. This Standard defines the required behaviour at a physical interface at the C reference point. Figure 2 below shows the protocol stack applicable at the C reference point.
PISN User Plane (User information) Data
PISN Control Plane (Signalling) Voice
PISN Call Control and Supplementary Services as referenced in clause 10.4 (SSs and ANFs)
Network layer
QSIG / PSS1 Protocol Control as referenced in clause 10.2 (Basic Call) and 10.3 (GF)
Data link layer
Symmetric LAP-D as referenced in clause 9
Physical layer
User (B-) Channel: 64 kbit/s / Signalling (D-) Channel: 16/64 kbit/s (Basic or Primary Rate Interface) as referenced in clause 8 Physical Transmission Medium F ig u r e 2 - P r o t o c o l S t a c k
8 8.1
Layer 1 Requirements General Typical customer networks (e.g. branch offices etc.) require interconnections of differently scaled PINXs via the ICN. Therefore the ICN shall support both, Primary Rate Access and Basic Access. In general the configuration parameters for the T reference point as specified in ITU-T Recommendations I.430 for Basic Access and I.431 for Primary Rate Interface shall also apply at interfaces at the C reference point, with the restrictions as stated below.
8.2
Basic Access (2xB 6 4 +D 1 6 ) When a basic access is offered at the C reference point ITU-T Recommendation I.430 applies to both sides of the interface. As the requirement for the basic access is depending on a particular PINX configuration, public networks claiming conformance to this Standard shall generally offer the capability for application of basic rate interfaces. It is recommended to keep Layer 1 permanently active. NOTE 4 This recommendation is made in order to avoid frequent synchronization and re-synchronization of the attached PINX. In addition an active layer 1 allows the attached PINX to easily choose a line for the establishment of a call and it helps decreasing the setup time for a call. The D Q -channel allocation to time slots shall be fixed according to sub-clauses 8.1.2 / 8.2.1.2 of Standard ECMA-226.
8.3
Primary Rate Access When a primary rate access is offered at the C reference point ITU-T Recommendation I.431 applies to both sides of the interface. As the requirement for the primary rate access is depending on a particular PINX configuration, public networks claiming conformance to this Standard shall generally offer the capability for application of one of the following primary rate interfaces.
- 7 -
NOTE 5 In case of either primary rate access, layer 1 is always permanently active. 8.3.1
2048 kbit/s Primary Rate Access (30xB64+D64) The D Q -channel allocation to time slots shall be fixed to timeslot 16 according to sub-clauses 8.1.1 / 8.2.1.1 of Standard ECMA-226.
8.3.2
1 5 4 4 k b it /s P r im a r y R a t e I n t e r f a c e ( 2 3 x B 6 4 + D 6 4 ) The D Q -channel allocation to time slots shall be fixed to timeslot 24 according to ISO/IEC 14474.
9
Layer 2 Requirements The following layer 2 requirements apply at interfaces at the C reference point: Layer 2 on the D Q -channel shall be according to the symmetrical application in Annex A of ITU-T Rec. Q.920, Amendment 1: 2000, and Annex J of ITU-T Rec. Q.921, Amendment 1: 2000, and master / slave shall be configurable. The SM / SREJ option, defined in Annex E of ITU-T Rec. Q.921, shall not apply. While the PINX side has the choice of applying the TEI Management according to ITU-T Rec. Q.921 Annex A, where alternatively no TEI management is required for point-to-point configurations with TEI 0, the virtual transit PINX shall be configurable to accept both alternatives. While the PINX side has the choice of applying the limited TEI Management as for the T reference point, the virtual transit PINX shall be configurable to accept both alternatives. For use at basic accesses the window size (k) shall be 1. The window size for primary rate interfaces shall be configurable for 1, 3 or 7, respectively, under the assumption that both sides when interconnected have chosen the same value.
10
Layer 3 Requirements
10.1
General The following layer 3 requirements apply at interfaces at the C reference point. If a functionality which is qualified as optional is provided, it shall be in accordance with the referenced standards.
10.1.1
Addressing and Routeing The support of addressing according to Standard ECMA-155 is mandatory for attached PINXs as well as for virtual transit PINXs. The virtual transit PINX shall support numbering plan identifications set to “E.164” and to “unknown”. The virtual transit PINX may also support numbering plan identification set to “PNP”. The choice of selecting among the available options is up to the attached PINX side of the interface. NOTE 6 For the virtual transit PINX the support of each customer's numbering plan (PNP or "unknown") requires management functionality which is out of scope of this Standard. If explicit numbering plan (E.164 or PNP) is supported, a virtual transit PINX shall support all values of the type of number fields in the calling, called, and connected party number information elements and in numbers in SS/ANF APDUs. The actual type of number value to be used is determined by the requirements of the corporate network. Whichever value is supplied, a virtual transit PINX shall process it without modification. Number information (e.g. called / calling / connected party number, including numbers in SS/ANF APDUs) shall not be screened, modified nor truncated by the virtual transit PINX. Numbering plan identification and type of number shall not be modified by the virtual transit PINX.
10.2
Basic Call The following standards for Basic Call (BC) are further referred to as QSIG / PSS1 BC.
- 8 -
ECMA-143 (3rd edition, 1997 or later) shall apply to both sides of the interface. NOTE 7 Customers may request to interconnect PINXs with implementations of different standards via an interconnecting network to form a PISN. Therefore, if parties involved agree, either ISO/IEC 11572: 1997 (Edition 2) together with Amendment 1, Amendment 2 and Defect Report 0, or EN 300 172 (Version 1.4.1), "ISO/IEC 11572 modified" may alternatively be applied due to their limited minor deviations. In particular, if not otherwise stated in this Standard, the "Transit PINX procedures" specified in the standards mentioned above (§ 10.4) shall be supported by the virtual transit PINX. A virtual transit PINX shall through-connect the B-channel in both directions of transmission on receipt of the first message in response to SETUP indicating the B-channel to be used (§ 10.4.5). A virtual transit PINX shall not discard any PROGRESS message received in the TCC_Call Active state (§ 10.4.9). A virtual transit PINX, on receipt of a DISCONNECT, RELEASE, or RELEASE COMPLETE message from the attached PINX prior to reaching the TCC_Call Alerting state shall not attempt "other (unspecified) procedures" (§ 10.4.10.1). A virtual transit PINX, on receipt of a CONNECT message from the attached PINX, shall send a CONNECT ACKNOWLEDGE message, even if by mutual agreement timer T313 is not implemented. (§ 10.1.6). 10.2.1
S e g m e n t a t io n a n d r e a s s e m b ly Application of the QSIG / PSS1 segmentation and reassembly procedure is mandatory for the virtual transit PINX. The implementation shall support the maximum segment length of 260 octets and 8 segments as defined for QSIG/PSS1 BC. For the attached PINX the support of reassembly and segmentation is optional.
10.2.2
C h a n n e l I d e n t if ic a t io n In addition to the specifications made by the base standard for QSIG / PSS1 BC, the support of Channel map is mandatory for the virtual transit PINX.
10.2.3
En - b l o c , O v e r l a p S e n d i n g / R e c e i v i n g NOTE 8 Despite the typical restrictions on the number length (e.g. in E.164), a particular PISN may request the transport of longer digits sequences by means of overlap sending.
10.2.4
Sub-addressing For sub-addressing information elements the maximum length of 23 octets shall be transported transparently by virtual transit PINXs.
10.2.5
Causes Causes as defined in QSIG/PSS1 BC shall apply. All causes received from an attached PINX shall be passed transparently through the virtual transit PINX. Certain situations (e.g. congestion within the ICN) require the generation of specific causes by the virtual transit PINX. Location information for such causes shall be "transit network".
10.2.6
Be a r e r S e r v i c e s The bearer services speech, 3.1kHz audio and UDI (unrestricted digital information) shall be supported by the virtual transit PINX. Additional bearer services may be offered based on mutual agreement. NOTE 9 Within virtual transit PINXs the use of compression may be restricted due to the indicated Bearer Service and the Quality of Service demands.
10.2.7
P r o g r e s s I n d ic a t o r All progress indications received from an attached PINX shall be passed transparently through the virtual transit PINX. Certain situations (e.g. congestion within the ICN) require the generation of
- 9 -
progress indicator #8 by the virtual transit PINX. Location information for this progress indication shall be "transit network". Additional Progress descriptions (according to Annex ZB of ECMA-143 (3rd edition, 1997 or later)) shall not be generated by virtual transit PINXs. The maximum number of progress indicators transported by one QSIG / PSS1 message shall be supported by the virtual transit PINX. 10.2.8
10.3
Codeset The support of all codesets from codeset 0 to 7 is mandatory.
Generic Functional Protocol (GF) The following standards for Generic Functional Protocol are further referred to as QSIG/PSS1 GF. ECMA-165 (3rd edition, 1997 or later) shall apply to both sides of the interface. NOTE 10 Customers may request to interconnect PINXs with implementations of different standards via an interconnecting network to form a PISN. Therefore, if parties involved agree, either ISO/IEC 11582: 1995 (Edition 1), or ETS 300 239: 1995 (Edition 2), "ISO/IEC 11582 modified", may alternatively be applied due to their limited minor deviations. ECMA-165 Edition 1 should not be used, due to its incompatibility with later editions and ISO/IEC Standards. However, it is recommended to apply the same Standard at all interfaces at all C reference points of the virtual transit PINX used by a single PISN, to avoid possible restrictions in terms of functionality. Additionally it is recommended, that only corresponding standards for Generic Functional Protocol and Basic Call are applied together as combinations, i.e. either -
ISO/IEC 11582 for GF with ISO/IEC 11572 for Basic Call, or
-
ECMA-165 for GF with ECMA-143 for Basic Call, or
-
ETS 300 239 for GF with EN 300 172 for Basic Call.
In particular, if not otherwise stated in this Standard, the "Transit PINX procedures" specified in the standards mentioned above shall be supported by the virtual transit PINX. 10.3.1
I m p o r t a n t is s u e s f r o m t h e P I S N p o in t o f v ie w In context with implementations at interfaces at the C reference point the following functions require special consideration.
10.3.1.1
Call related transport mechanism Call related signalling shall be supported.
10.3.1.2
Connectionless call independent transport mechanism Connectionless call independent signalling may be supported by the virtual transit PINX based on mutual agreement between the parties involved.
10.3.1.3
Connection oriented call independent transport mechanism Connection oriented call independent signalling shall be supported by the virtual transit PINX.
10.3.1.4
Manufacturer Specific Information Transport of manufacturer specific information shall be supported by the virtual transit PINX. New (proprietary) operations shall be treated as manufacturer specific information according to ECMA-165.
10.3.1.5
Notify and Facility Messages Unless otherwise specified in section 10.4 of this Standard, NOTIFY and FACILITY messages shall be transported transparently by the virtual transit PINX.
- 10 -
10.3.1.6
N o t if ic a t io n I n d ic a t o r I n f o r m a t io n Ele m e n t The transparent transport of notification information shall be supported by the virtual transit PINX.
10.3.1.7
Facility Information Element The maximum length of facility information element as specified in QSIG/PSS1 GF shall be supported by the virtual transit PINX. The number of facility information elements shall be limited only by the max. layer 3 message length, thereby considering the applicability of the message segmentation procedure leading to a maximum of 8 segments.
10.4
Supplementary Services and Additional Network Features The virtual transit PINX shall act as a Transit PINX for supplementary services and ANFs. Typically, apart from the transport of APDUs, the application of a supplementary service or ANF in the attached PINXs requires no special procedures by the virtual transit PINX, with the exceptions specified in the subclauses below. NOTE 11 Customers may request to interconnect PINXs with implementations of different standards for SSs and ANFs via an interconnecting network to form a PISN. Such applications are not precluded. However, it is recommended to apply the same standards at all interfaces at all C reference points of the virtual transit PINX used by a single PISN, in order to avoid possible restrictions in terms of functionality. Additionally it is recommended, that only corresponding standards for supplementary services and ANFs, Generic Functional Protocol, and Basic Call are applied together as combinations, i.e. either
10.4.1
-
ISO/IEC supplementary services and ANFs with ISO/IEC 11582 for GF and ISO/IEC 11572 for Basic Call, or
-
ECMA supplementary services and ANFs with ECMA-165 for GF and ECMA-143 for Basic Call, or
-
ETSI supplementary services and ANFs with ETS 300 239 for GF and EN 300 172 for Basic Call. Procedures required at the virtual transit PINX for Advice of Charge (AOC) The transparent transport of QSIG / PSS1 AOC information is mandatory. The virtual transit PINX shall not generate any Advice of Charge information. NOTE 12 If applicable, AOC received at a gateway PINX is interworked according to QSIG / PSS1 procedures before being transported through the virtual transit PINX.
10.4.2
P r o c e d u r e s r e q u i r e d a t t h e v i r t u a l t r a n s i t P I N X f o r C a l l D i v e r s i o n ( C F B, C F N R , CFU) If the virtual transit PINX acts as Rerouteing PINX, it shall support all interactions with other supplementary services and ANFs.
10.4.3
Procedures required at the virtual transit PINX for Call Transfer (CT) If the virtual transit PINX acts as Rerouteing PINX, it shall support all interactions with other supplementary services and ANFs.
10.4.4
Procedures required at the virtual transit PINX for Path Replacement (PR) If the virtual transit PINX acts as Inviting PINX, it shall support all interactions with other supplementary services and ANFs.
10.4.5
Procedures required at the virtual transit PINX for Call Interception (CINT) If the virtual transit PINX acts as Intercepting PINX, it shall support all interactions with other supplementary services and ANFs.
10.4.6
Procedures required at the virtual transit PINX for Transit Counter (TC) Support of Standard ECMA-225 is mandatory for the virtual transit PINX. The transit counter value shall be incremented by 1 by the virtual transit PINX.
- 11 -
10.4.7
P r o c e d u r e s r e q u i r e d a t t h e v ir t u a l t r a n s i t P I N X f o r P r i v a t e U s e r M o b i l i t y - C a l l H a n d lin g ( P U M C H ) If the virtual transit PINX acts as PUMI Rerouteing PINX, it shall support all interactions with other supplementary services and ANFs.
10.4.8
Procedures required at the virtual transit PINX for Cordless Terminal Mobility C a l l H a n d l i n g ( C T M I / C TM O ) If the virtual transit PINX acts as CTMI detect PINX, it shall support all interactions with other supplementary services and ANFs.
10.4.9
Procedures required at the virtual transit PINX for Single Step Call Transfer (SSCT) If the virtual transit PINX acts as Rerouteing PINX, it shall support all interactions with other supplementary services and ANFs.
10.4.10 Procedures required at the virtual transit PINX for Call Priority Interruption (CPI) If the virtual transit PINX acts as Interrupting PINX, it shall support all interactions with other supplementary services and ANFs.
10.5
Keypad and Feature key Procedures The application of either the keypad or the feature key procedure as specified in various standards for the S and S/T reference point shall not be supported at the C reference point.
- 12 -
- 13 -
Annex A (normative)
Requirements List (RL) A.1
General Use of this Standard imposes requirements on the implementation that go beyond those of the base standards referred to by this Standard. These result in modifications to the requirements expressed in the PICS proformas for the base standards. This annex specifies the modifications (the Requirements List - RL) that apply to the status of the items affected in each PICS proforma, with consequently modified requirements on the answers to be provided. The status notation used in this annex is that defined in ISO/IEC 9646-7. In summary, the meaning of the notations is as follows: i
Irrelevant or out-of-scope - this capability is outside the scope of this profile and is not subject to conformance testing in this context.
m
Mandatory - the capability is required to be supported.
n/a
Not Applicable - in the given context, it is impossible to use the capability.
o
Optional - the capability may be supported or not.
o.i
qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer that identifies an unique group of related optional items and the logic of their selection, defined below the table.
x
eXcluded or prohibited - there is a requirement not to support this capability in this profile.
The Requirements List in this Annex shall be used to restrict the permitted support answers in the corresponding PICS.
A.2
Relationship between RL and corresponding PICS proformas In the context of the profile specification contained in this Standard, PICS proformas of the base protocol standards contain items in 3 categories. The 3 categories are: -
those proforma items where this profile does not restrict the permitted support answers;
-
those proforma items where this profile restricts the permitted support answers;
-
those proforma items that are not relevant to this profile.
The Requirements List consists of the items falling into the second category, with an indication of the modified status in those items.
- 14 -
A.3
Requirements List
A.3.1
Tables for the data link layer (control plane) Item number and references refer to annex B of EN 300 402-4.
A . 3 . 1 . 1 R o le s Item
Question/Feature
Reference
Protocol Status
Profile Status attached PINX
Profile Status virtual transit PINX
R6.1
basic access
A.6
o.2
o.2
o.2
R6.2
primary rate access
A.6
o.2
o.2
o.2
A.3.2
Tables for the network layer (control plane)
A . 3 . 2 . 1 Ba s ic C a ll Item numbers and references refer to ECMA-143 (ISO/IEC 11572). A . 3 . 2 . 1 . 1 Be a r e r s s u p p o r t e d Item
Question/Feature
Reference
Protocol Status
Profile Status attached PINX
Profile Status virtual transit PINX
Z1
Support of the 64 kbps unrestricted bearer
14.5.5
o.1
o.3
m
Z2
Support of the 64 kbps bearer with speech transfer capability
14.5.5
o.1
o.3
m
Z3
Support of the 64 kbps bearer with 3.1 kHz audio transfer capability
14.5.5
o.1
o.3
m
Z4
Support of the Multi-rate Unrestricted Bearer
14.5.5
o.1
o.3
o
- 15 -
A.3.2.1.2 Circuit switched call control Item
Question/Feature
Reference
Protocol Status
Profile Status attached PINX
Profile Status virtual transit PINX
B1
Is the implementation capable of functioning as an Originating PINX ?
10.5
o.2
o.4
x
B2
Is the implementation capable of functioning as an Incoming Gateway PINX ?
10.7
o.2
o.4
x
B3
Is the implementation capable of functioning as a Transit PINX ?
10.4
o.2
o.4
m
B4
Is the implementation capable of functioning as a Terminating PINX ?
10.6
o.2
o.4
x
B5
Is the implementation capable of functioning as an Outgoing Gateway PINX ?
10.8
o.2
o.4
x
B6
Support procedures for call request
10.1.1
(B1 OR B2 OR B3): m
(B1 OR B2 OR B3): m
B3: m
B9
Overlap Receiving procedures
10.1.3
(B3 OR B4 OR B5): m
(B3 OR B4 OR B5): m
B3: m
B10
Overlap Sending procedures
10.1.3
(B1 OR B2 OR B3): m
(B1 OR B2 OR B3): m
B3: m
B17
Sending of call progress information during call establishment
10.1.7
(B3 OR B4 OR B5): o
(B3 OR B4 OR B5): o
B3: m
- 16 -
A.3.2.1.3 Messages and information elements for general procedures Item
Question/Feature
Reference
Protocol Status
Profile Status attached PINX
Profile Status virtual transit PINX
J21
Support of channel map
14.5.12
o
o
m
J21A
Numbering plan identification supported: E.164 PNP Unknown Type of number supported for ISDN/Telephony Numbering Plan (E.164) in calling and connected party number: Unknown International number National number Subscriber number
14.5.7
o o.5 o.5 o.5
m o m
o.6 o.6 o.6 o.6
m m m m
Type of number supported for Private Numbering Plan in calling and connected party number: Unknown Level 2 regional number Level 1 regional number PISN specific number Level 0 regional number Abbreviated number
14.5.7
o.7 o.7 o.7 o.7 o.7 o.7
m m m m m m
J22A
J23A
14.5.7
o
o
A.3.2.2 Generic Functional Protocol Item numbers and references refer to annex A of ECMA-165 (ISO/IEC 11582). A.3.2.2.1 Call related protocol control and GFT-Control requirements Item
Question/Feature
Reference
Protocol Status
Profile Status attached PINX
Profile Status virtual transit PINX
A7
Can the PINX act as an Originating, Terminating, Incoming or Outgoing Gateway PINX as defined in ECMA-143 (ISO/IEC 11572) ?
4 & ECMA143 (ISO/IEC 11572)
o.1
o.8
x
A10
Can the PINX act as a Transit PINX as defined in ECMA-143 (ISO/IEC 11572) ?
4 & ECMA143 (ISO/IEC 11572)
o.1
o.8
m
A12
Can the implementation generate notification information ?
7.4
o
o
n/a
- 17 -
A . 3 . 2 . 2 . 2 C o n n e c t io n le s s A D P U t r a n s p o r t m e c h a n is m Item
Question/Feature
Reference
Protocol Status
Profile Status attached PINX
Profile Status virtual transit PINX
B1
Does the PINX support Connectionless APDU transport?
7.2
o
o
o
B7
Actions as a Source PINX
7.2.2.1
B1: o
B1: o
n/a
A . 3 . 2 . 2 . 3 C o n n e c t io n o r ie n t e d A P D U t r a n s p o r t m e c h a n is m Item
Question/Feature
Reference
Protocol Status
Profile Status attached PINX
Profile Status virtual transit PINX
C1
Does the PINX support connection-oriented APDU transport?
7.3
o
o
m
C2
Can the implementation act as a Source PINX for APDUs when supporting the Connection oriented APDU transport mechanism ?
7.3
C1: o
C1: o
o
C4
Actions at an Originating PINX
7.3.3.1
C1: o
C1: o
x
C6
Actions at a Terminating PINX
7.3.3.3
C1: o
C1: o
x
A.3.2.2.4 Manufacturer specific information Item
Question/Feature
Reference
Protocol Status
Profile Status attached PINX
Profile Status virtual transit PINX
H1
Manufacturer specific operations
9.1
o
o
n/a
H2
Manufacturer specific additions to standardized operations
9.2
o
o
n/a
H3
Manufacturer specific notifications
9.3
o
o
n/a
- 18 -
A.3.3
Supplementary Services and ANFs Item numbers, except C2, refer to annexes A of the ECMA standards mentioned in the Reference column. Item number C2 refers to section A.3.2.2.3 in this Standard.
Item
Question/Feature
Reference
Protocol Status
Profile Status attached PINX
Profile Status virtual transit PINX
A1, A2
Support of QSIG / PSS1 Advice of Charge (AOC)
ECMA-212 ISO/IEC 15050
o
o
m
o
x
o
C2: o
Generation of any Advice of Charge information B3
Behaviour as a Rerouteing PINX for Call Diversion SSs (CFB, CFNR, CFU, CD)
ECMA-174 ISO/IEC 13873
E1 - J10
Support of interactions of CFB, CFNR, CFU, CD with other SSs and ANFs
ECMA-174 ISO/IEC 13873
C1
Behaviour as a Rerouteing PINX for Call Transfer (CT)
ECMA-178 ISO/IEC 13869
E1 - F4
Support of interactions of CT with other SSs and ANFs
ECMA-178 ISO/IEC 13869
A7
Behaviour as an Inviting PINX for Path replacement (PR)
ECMA-176 ISO/IEC 13874
E1
Support of interactions of PR with other SSs and ANFs
ECMA-176 ISO/IEC 13874
B4, B5
Behaviour as an Intercepting PINX for Call Interception CINT)
ECMA-221 ISO/IEC 15054
D1 - K2
Support of interactions of CINT with other SSs and ANFs
ECMA-221 ISO/IEC 15054
A5, A6
Behaviour as a Transit PINX for ANF Transit Counter (TC)
ECMA-225 ISO/IEC 15056
o
o
m
Incrementation of transit counter value
ECMA-225 ISO/IEC 15056
o
o
m
A8
Behaviour as a PUMI rerouteing PINX for Private User Mobility Call Handling (PUMCH)
ECMA-284 ISO/IEC 17878
o
o
C2: o
E1 - Q3
Support of interactions of PUMCH with other SSs and ANFs
ECMA-284 ISO/IEC 17878
A1
Behaviour as a CTMI detect PINX for Cordless Terminal Mobility Incoming Call Handling (CTMI)
ECMA-215
E1 - I2
Support of interactions of CTMI with other SSs and ANFs
ECMA-215
A2
Behaviour as a Rerouteing PINX for Single Step Call Transfer (SSCT)
ECMA-300
o
B3: m
o
o
C2: o C1: m
o
o
C2: o A7: m
o
o
C2: o B4,B5: m
A8: m o
o
C2: o
A1: m o
o
C2: o
- 19 -
E1 - M3
Support of interactions of SSCT with other SSs and ANFs
ECMA-300
A5
Behaviour as Interrupting PINX for Call Priority Interruption (CPI)
ECMA-264
E1 - L3
Support of interactions of CPI with other SSs and ANFs
ECMA-264
A.3.4
A2: m o
o
C2: o A5: m
Keypad and Feature key Procedures
Item
Question/Feature
Reference
Protocol Status
Profile Status attached PINX
Profile Status virtual transit PINX
Support of Keypad Procedures as specified for the S and S/T reference point
o
x
x
Support of Feature key Procedures as specified for the S and S/T reference point
o
x
x
- 20 -
- 21 -
Annex B (normative)
Profile specific ICS proforma B.1
General The layout and content of this annex is guided by ISO/IEC 9646-7. The supplier of a profile implementation that is claimed to conform to this Standard shall complete the Profile specific Implementation Conformance Statement (ICS) proforma contained in this annex. NOTE The supplier is also required to complete a copy of the PICS proformas provided in each of the protocol standards referred to by this Standard. A completed Profile specific ICS proforma is the ICS for the implementation in question. The ICS is a statement of which capabilities and options of the profile have been implemented. The ICS can have a number of uses, including use:
B.2 B.2.1
-
by the profile implementer, as a check list to reduce the risk of failure to conform to the Standard through oversight;
-
by the supplier and acquirer (or potential acquirer) of the implementation, as a detailed indication of the capabilities of the implementation, stated relative to the common basis for understanding provided by the standard ICS proforma;
-
by the user (or potential user) of the implementation, as a basis for initially checking the possibility of interworking with another implementation (note that, while interworking cannot be guaranteed, failure to interwork can often be predicted from incompatible ICS);
-
by a protocol tester, as the basis for selecting appropriate test suites against which to assess the claim for conformance of the implementation.
Instruction for completing the ICS proforma General structure of the ICS proforma The ICS proforma is a fixed format questionnaire divided into subclauses each containing a group of individual items. Each item is identified by an item number, the name of the item (question to be answered), and the reference(s) to either the base standard, or a specific clause in a base standard, or specifying the item in the main body of this Standard (if no base standard is listed in the reference column). The "Status" column indicates whether an item is applicable and if so whether support is mandatory or optional. The following terms are used: m
mandatory (the capability is required for conformance to the profile);
o
optional (the capability is not required for conformance to the profile but if the capability is implemented it is required to conform to the profile specification);
o.<n>
optional, but support of at least one of the group of options labelled by the same numeral <n> is required;
<item>:m simple-conditional requirement, the capability being mandatory if item number <item> is supported, otherwise not applicable; <item>:o
simple-conditional requirement, the capability being optional if item number <item> is supported, otherwise not applicable;
x
prohibited;
c.<cond> conditional requirement, depending on support for the item listed in condition <cond>.
- 22 -
Answers to the questionnaire items are to be provided in the "Support" column, by simply marking an answer to indicate a restricted choice (Yes or No), or in the "Not Applicable" column (N/A).
B.2.2
Additional Information Items of Additional information allow a supplier to provide further information intended to assist the interpretation of the ICS. It is not intended or expected that a large quantity will be supplied, and an ICS can be considered complete without any such information. Examples might be an outline of the ways in which a (single) implementation can be set up to operate in a variety of environments and configurations. References to items of Additional information may be entered next to any answer in the questionnaire, and may be included in items of Exception Information.
B.2.3
Exception Information It may occasionally happen that a supplier will wish to answer an item with mandatory or prohibited status (after any conditions have been applied) in a way that conflicts with the indicated requirements, No preprinted answer will be found in the Support column for this. Instead, the supplier is required to write into the support column an x.<i> reference to an item of Exception Information, and to provide the appropriate rationale in the Exception item itself. An implementation for which a Exception item is required in this way does not conform to this Standard. A possible reason for the situation described above is that a defect in the Standard has been reported, a correction for which is expected to change the requirement not met by the implementation.
- 23 -
B.3
ICS proforma
B.3.1
Implementation Identification
Supplier Contact point for queries about the ICS Implementation Name(s) and Version(s) (NOTE) Other information necessary for full identification, e.g. name(s) and version(s) for machines and/or operating systems; system name(s) Have any exception items been required?
No[ ] Yes[ ] (The answer Yes means that the implementation does not conform to this Standard)
Date of Statement
NOTE The terms "Name" and "Version" should be interpreted appropriately to correspond with a suppliers terminology (e.g., Type, Series, Model).
B.3.2
Roles
Item
Question/Feature
Reference
Status
N/A
Support
R1
Attached PINX
o.1
Yes [ ] No [ ]
R2
Virtual Transit PINX
o.1
Yes [ ] No [ ]
- 24 -
B.3.3
Physical Layer
Item
Question/Feature
Reference
Status
PH1
Support of Basic Access
8.2
R1: o.2 R2: m
Yes [ ] No [ ]
PH2
Support of 2048 kbit/s Primary Rate Access
8.3.1
R1: o.2 R2: o.3
Yes [ ] No [ ]
PH3
Support of 1544 kbit/s Primary Rate Interface
8.3.2
R1: o.2 R2: o.3
Yes [ ] No [ ]
PH4
Support of permanently active Layer 1 at Basic Access
8.2
R1: n/a R2: o
[]
PH5
Support of DQ Channel allocation at Basic access
8.2
PH1: m
[]
Yes [ ]
PH6
Support of DQ Channel allocation to timeslot 16 at Primary rate access
8.3.1
PH2: m
[]
Yes [ ]
PH7
Support of DQ Channel allocation to timeslot 24 at Primary rate interface
8.3.2
PH3: m
[]
Yes [ ]
N/A
Support
B.3.4
N/A
Support
Yes [ ] No [ ]
Layer 2
Item
Question/Feature
Reference
Status
DL1
Support of TEI Management according to Q.921
9.1
R1: o R2: m
Yes [ ] No [ ]
DL2
Support of limited TEI Management as for the T reference point
9.1
R1: o R2: m
Yes [ ] No [ ]
DL3
Support of configurable window size (1, 3, or 7) at Primary Rate Access
9.1
m
Yes [ ]
- 25 -
B.3.5
Layer 3, Basic Call
Item
Question/Feature
Reference
Status
N/A
BC1
Through-connection of the B-channel on receipt of the first response to SETUP indicating the B-channel to be used
10.2
R1: n/a R2: m
[]
Not discard any PROGRESS message received in the TCC_Call Active state
10.2
R1: n/a R2: m
[]
Not attempt "other (unspecified) procedures" on receipt of a DISCONNECT, RELEASE, or RELEASE COMPLETE message prior to reaching the TCC_Call Alerting state
10.2
R1: n/a R2: m
[]
Sending of a CONNECT ACKNOWLEDGE message on receipt of a CONNECT message
10.2
R1: n/a R2: m
[]
Transport of sub-addressing information elements with the maximum length of 23 octets
10.2.4
R1: n/a R2: m
[]
Transparent transport of all causes
10.2.5
R1: n/a R2: m
[]
R1: n/a R2: m
[]
BC2 BC3
BC4
BC5
BC6 BC7
Support Yes [ ]
Yes [ ] Yes [ ]
Yes [ ]
Yes [ ]
Yes [ ]
Generation of specific causes with location "transit network"
10.2.5
BC8
Use of progress description #8, if applicable
10.2.7
R1: o R2: m
Yes [ ] No [ ]
BC9
Use of location "transit network", if applicable
10.2.7
R1: o R2: m
Yes [ ] No [ ]
BC10
Support of codesets 0 to 7
10.2.8
R1: m R2: m
Yes [ ]
B.3.6
Yes [ ]
Generic Functional Protocol
Item
Question/Feature
Reference
Status
N/A
GF1
Transparent transport of notification information
10.3.1.6
R1: n/a R2: m
[]
Support of the maximum length of the Facility information element
10.3.1.7
R1: n/a R2: m
[]
Transport of manufacturer specific extensions and operations
10.3.1.4
R1: n/a R2: m
[]
GF2 GF3
Support Yes [ ] Yes [ ] Yes [ ]
.
.
Free printed copies can be ordered from: ECMA 114 Rue du Rhône CH-1204 Geneva Switzerland Fax: Email:
+41 22 849.60.01 [email protected]
Files of this Standard can be freely downloaded from the ECMA web site (www.ecma.ch). This site gives full information on ECMA, ECMA activities, ECMA Standards and Technical Reports.
ECMA 114 Rue du Rhône CH-1204 Geneva Switzerland See inside cover page for obtaining further soft or hard copies.