ISO IEC 20161 pdf download – Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Use of QSIG at the C reference point between a PINX and an Interconnecting Network
8.2Basic Aceess (2xB,4+Dyo
When a basic access is offered at the C reference point ITU-TRecommendation 1.430 applies to both sides of the interface.Asthe requirement for the basic access is depending on a particular PINX configuration, public networks claiming conformance tothis International Standard shall generally offer the capability for application of basic rate interfaces.
lt is recommended to keep Layer 1 permancntly active.
NOTE4-This recommendation is made in order to avoid frequent synehronization and re-synchronization of the attached PINX.In aditionan 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 acall.
The Dy-channel allocation to time slots shall be fixed according to sub-clauses 8.1.2∶8.2.1.2 of Standard ECMA-226.8.3Primary Rate Access
When a primary ratc access is offered at the C reference point ITU-T Recommendation I.431 applies to both sides of theinterface. As the requirement for the primary rate access is depending on a particular PINX configuration, public networksclaiming conformance to this International Standard shall generally offer the capability for application of one of the followingprimary ratc intcrfaces.
NOTE 5 – In casc of cither primary ratc access, layer 1 is always permanently active.8.3.1 2048 kbit/s Primary Rate Access (30xBea+Dei)
The D,-channel allocation to time slots shall be fixed to timeslot 16 according to sub-clauses 8.1.1 / 8.2.1.1 of StandardECMA-226.
8.3.21544 kbit’s Primary Rate Interface (23xB,,+Do4)
The Dr-channel allocation to time slots shall be fixed to timeslot 24 according to ISO/IEC 14474.9Layer 2 Requirements
The following layer 2 requirements apply at interfaces at the C reference point:
Layer 2 on the D,r-channel shall be according to the symmetrical application in Annex A of ITU-TRec. Q.920,Amendment l:2000, and Annex J of ITU-T Rec.Q.921,Amendment 1: 2000 , and master i slave shall be configurable.
The SM / SREJ option, defined in Annex Eof ITU-T Rec.Q.921, shall not apply.
While the PINX side has the choice of applying the TEl Management according to ITU-T Rec. 0.921 Annex A, wherealternatively no TEl management is required for point-to-point configurations with TEl 0, the virtual transit PINX shall beconfigurable to accept both alternatives.
While the PINX side has the choice of applying the limited TEl Management as for the T relference point, the virtual transitPINX 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 l,3 or 7, respectively,under the assumption that both sides when interconnected have chosen the same value.
10Layer 3 Requirements
10.1 General
The following layer 3 requirements apply at interfaces at the C reference point. lf a functionality which is qualified as optionalis provided, it shall be in accordance with the referenced standards.
10.1.1Addressing and Routeing
The support of addressing according to Standard ECMA-I55 is mandatory for attached PINXs as well as for virtual transitPINXs.
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 managementfunctionality which is out of scope of this Intcrnational Standard.
lf explicit numbering plan (E.164 or PNP) is supported, a virtual transit PINX shall support all values of the type of numberfields in the calling, called, and connected party number information elements and in numbers in SS/ANF APDUs. The actualtype of number value to be used is determined by the requirements of the corporate network. Whichever value is supplied, avirtual transit PINX shall process it without modification.
Number information (e.g. called / calling / connected party number, including numbers in SSANF APDUs) shall not bescreened, 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.2Basic Call
The following standards for Basic Call(BC) are further referred to as QSIG / PSS1 BC.ISO/IEC 11572 shall apply to both sides of the interface.
NOTE 7-For the purpose of this Profile Standard, interface implementations complying with ISOIEC 11572:1997(Edition 2, includingAmendment 1, Amendment 2 and Defect Report 0) or later, can be considered to comply with the above requirement. lmplementations of thelst edition of ISOIEC 11572 or of the 2nd edition without the mentioned amendments and defect report cannot meet the requirements ofthis Profile Standard.
Implementations complying with EN 300 172 (Version 1.4.1 or later) or ECMA-143 (3rd edition, 1997 or later) can also be considered tocomply.
In particular, if not otherwise stated in this Intermational Standard, the “Transit PINX procedures” specified in the standardsmentioned 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 inresponse 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 attachedPINX 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 CONNECTACKNOWLEDGE message, even if by mutual agreement timer T313 is not implemented.($ 10.1.6).
10.2.1 Segmentation and reassembly
Application of the QSIG / PSsl segmentation and reassembly procedure is mandatory for the virtual transit PINX. Theimplementation shall support the maximum segment length of 260 octets and 8 segments as defined for QSIG/PSSI BC.
For the attached PINX the support of reassembly and segmentation is optional.
10.2.2 Channel ldentification
In addition to the specifications made by the base standard for QSIG / PSS1 BC, the support of Channel map is mandatory forthe virtual transit PINX.
10.2.3 En-bloc, Overlap Sending / Receiving
NOTE 8 – Despite the typical restrictions on the number length (e.g. in E.164), a particular PISN may request the transport of longer ditssequences 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 transitPINXs.
ISO IEC 20161 pdf download – Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Use of QSIG at the C reference point between a PINX and an Interconnecting Network
