1、 KSKSKSKS KSKSKSK KSKSKS KSKSK KSKS KSK KS KS X 4305 KS X 4305:2008 2008 10 31 http:/www.kats.go.krKS X 4305:2008 : ( ) ( ) () ()SJ ( ) : (http:/www.standard.go.kr) ： ： 1998 12 31 ： 2008 10 31 2008-0734 ： ： ( 025097262) (http:/www.kats.go.kr). 10 5 , . KS X 4305:2008 Information technology Telecommu
2、nications and information exchange between systems Private Integrated Services NetworkGeneric functional protocol for the support of supplementary services Inter-exchange signalling procedures and protocol 1995 1 ISO/IEC 11582, Information technology Telecommunications and information exchange betwe
3、en systems Private Integrated Services Network Generic functional protocol for the support of supplementary services Inter-exchange signalling procedures and protocol . 6. . 1 Q (ANF) . 1(PSS1) . Q (PISN) (PINX) , KS X 4309 1 . ANF . KS X 4308 Q 3 (call) . KS X 4308 . 2 PINX A (PICS) . 3 . . ( ) . K
4、S X 4304, 64 kbit/s , ISO/IEC 11574： 1994, Information technology Telecommunications and information exchange KS X 4305:2008 2 between systems Private Integrated Services Network Circuit-mode 64 kbit/s bearer servicesService descriptions, functional model and information flows . KS X 4308, ISO/IEC 1
5、1572： 1994, Information technology Telecommunications and information exchange between systems Private Integrated Services Network Circuit mode bearer services Inter-exchange signaling procedures and protocol KS X 4309 1, 1： ISO/IEC 11579 1 ： 1994, Information Technology Telecommunications and infor
6、mation exchange between systems Private Integrated Services network Part 1 ： Reference configuration for PISN Exchanges(PINX) CCITT Rec.I.112： 1988, Vocabulary of terms for ISDNs(Blue Book, Volume III, Fascicle III 7) CCITT Rec.I.210： 1988, CCITT Recommendation： Principles of Telecommunication Servi
7、ces Supported by an ISDN and the Means to Describe Them(Blue Book) CCITT Rec.X.208： 1988, Specification of Abstract Syntax Notation One(ASN. 1)(Blue Book) CCITT Rec.X.209： 1988, Encoding Rules for Abstract Syntax Notation One(ASN. 1)(Blue Book) CCITT Rec.X.217： 1988, Association control service defi
8、nition for Open Systems Interconnection for CCITT Applications(Blue Book) CCITT Rec.X.219： 1988, Remote Operations Model, Notation and Service(Blue Book) CCITT Rec.X.227： 1988, Association control protocol specification for Open Systems Interconnection for CCITT Applications(Blue Book) CCITT Rec.X.2
9、29： 1988, Remote Operations Protocol Specification(Blue Book) 4 KS X 4309 1 CCITT Rec.I.112 . 4.1 . (object identifier) CCITT Rec. X.208 (PINX) KS X 4309 1 (PISN) KS X 4309 1 (service) CCITT Rce.I.112 (signalling) CCITT Rec.I.112 (user) KS X 4304 4.2 (additional network feature) PISN , . 4.3 PINX (a
10、djacent PINX) PINX 4.4 PINX (destination PINX) 2 PINX KS X 4305:2008 3 4.5 PINX (end PINX) PINX 4.6 PINX (gateway PINX) PINX PINX 4.7 PINX (inter-PINX link) Q 4.8 PINX (next PINX) PDU PINX 4.9 PINX (originating PINX) PINX 4.10 PINX (preceding PINX) PDU PINX 4.11 1 (private signalling system No.1) Q
11、4.12 PINX (source PINX) 2 PINX 4.13 PINX (subsequent PINX) PDU PINX 4.14 (supplementary service) CCITT Rec.I.210 . ANF . 4.15 (supplementary service control entity) PINX . 4.16 PINX (terminating PINX) PINX 4.17 PINX (transmit PINX) PINX , PINX KS X 4305:2008 4 5 ACSE (Association Service Element) AE
12、 (Application Entity) ANF (Additional Network Feature) APDU (Application Protocol Data Unit) ASN. 1 1(Abstract Syntax Notation One) BER (Basic Encoding Rules) DSE (Dialogue Service Element) DSS1 1(Digital Subscriber Signalling No.1) FIE (Facility Information Element) GFT (Generic Functional Transpor
13、t) ICD (International Code Designator) MSI (Manufacturer Specific Information) NFE (Network Facility Extension) PC (Protocol Control) PICS (Protocol Implementation Conformance Statement) PISN (Private Integrated Services Network) PINX (Private Integrated Services Network Exchange) PSSI 1(Private Sig
14、nalling System No.1) RO (Remote Operations) ROSE (Remote Operations Service Element) RTSE (Reliable Transfer Service Element) SCM (Signalling Carriage Mechanism) SS (Supplementary Service) 6 PISN . PINX Q . 6.1 . . 6.2 KS X 4308 . (ROSE), (ACSE), (DSE) . (GFT) . 6.3 SS PINX PINX SS . KS X 4305:2008
15、5 6.4 ROSE ROSE ROSE SS . 6.5 ACSE ACSE . 6.6 DSE DSE , , , SS . 6.7 GET SS ACSE, ROSE, DSE . 6.8 GET GET , , . 6.9 KS X 4308 . 7 GET 7.1 APDU APDU GET . , GET PINX , PINX , PINX . 7.2 APDU PINX APDU GET . , GET PINX , PINX , PINX . 7.3 APDU PINX APDU , , . , KS X 4305:2008 6 SDL . PINX . 7.4 PISN ,
16、 , GET . 8 8.1 . PINX APDU PINX APDU . 8.2 ROSE CCITT Rec.X.229 7. ROSE . 8.3 ACSE CCITT Rec.X.227 7. ACSE . 8.4 DSE PINX DSE . PINX , PINX , , , , . 8.5 SS SS , . 9 1 PINX . PISN . , , . 10 , , , , , , , , , . 11 . , , ASN.1 . KS X 4305:2008 7 A( ) (PICS) PICS . PICS , , PICS . B( ) ASN.1 ASN.1 . C
17、( ) . . , . D( ) PISN . CCITT Rec. X. 219/X.229 . E( ) ROSE CCITT Rec. X.219 , OPERATION ERROR . F( ) . G( ) . H( ) . I( ) . INTERNATIONAL STANDARD ISO/IEC 11582 First edition 1995-07-01 Information technology - Telecommunications and information exchange between Systems - Private Integrated Service
18、s Network - Generic functional protocol for the support of supplementary Services - Inter-exchange signalling procedures and protocol Technologies de Iinformation - Tbkcommunications et khange d in forma tions en tre sys tkmes - Rbseau privk 5 integration de Services - Protocole gP 0 1. r i i L ” ,
19、i i i _ j i j I L 1 _ i ” I_ . S -La _. *- fl-J- _ ,_ -,- . ,: c .:.,. ;. - . -u .V.C.! ,.:,.V,.,.,;,.,.;, UL - * :. ” -_ P. 1 / :. * r, .- e - rw -1-1 -_ * - -.-., _. - I . -. i r -. I_ - - ; ” _ Liii. L-r i. b. c5. L .d - Y. .L* k” -,CT. - “/ -Zz. .c Si- LLL L - 7. . r k_ - .15.“-” . . . . End PIN
20、X (Terminating or Originating, depending on direction of FIE) 2 End PINX (Originating or Terminating) = addressed PINX Required coding of NetworkFacilityExtension for each identified case Encoding of Encoding of Encoding of Encoding of sourceEntity sourceEntityAddress destinationEntity destinationEn
21、tityAddress endPINX NOT inclided endPINX NOT included (Note) endPINX NOT included anyTypeOfPINX Pl NX Address (Note) 3 End PINX endPINX NOT included anyTypeOf PINX NOT included (Originating or (Note) Terminating) = Next PINX which u nderstands contents 4 Transit PINX = anyTypeOfPINX PINX Address end
22、PINX NOT included Terminating or Originating PINX (depending on direction of FIE) 5 Transit PINX = anyTypeOfPINX PINX Address anyTypeOfPINX Pl NX Address addressed PINX 6 Transit PINX = anyTypeOfPINX PINX Address anyTypeOfPINX NOT included addressed PINX NOTE - The value endPINX for the sourceEntity
23、 should be avoided if there is any possibility that the PINX tan cease to be an End PINX (e.g. through the use of certain Supplementary Services) Prior to a response (e.g. a Reject APDU) being received. 10 0 ISO/IEC endPINX and erroneously includes a destinationEntityAddress element, the PINX shall
24、ignore the contents of the destinationEntityAddress field and treat the contents of the Facility information element as if only the destinationEntity element was present; - if the destinationEntity element of the NFE indicates endPINX, and the Transit PINX is capable of acting as an End PINX for all
25、 Services indicated in the Facility information element, it may become the Destination PINX for that Facility information element.; NOTE 1 - In this case, the Source of the information will have no knowledge that the information has been inter- cepted, as the Transit PINX will act as if it were an E
26、nd PINX. This may occur, for example, when a PINX at a PISN numbering domain boundary wishes to translate numbering information contained within an APDU. - in all cases where the PINX does not become the Destination PINX, the Facility information element shall be passed on unchanged to the Next PINX
27、. If the received NFE does not conform to the encoding and structure defined in clause 11, the entire Facility informa- tion element shall be discarded and no Facility information element shall be passed on to the Next PINX. NOTE 2 - Processing of a Facility information element at a Transit PINX doe
28、s not preclude another Facility information element, which may have similar contents to that received by the Transit PINX, being sent to the Next PINX as a result of that intemal processing. 7.1.2.3 Actions at a Destination PINX All APDUs in the received Facility information element shall be deliver
29、ed to the Coordination Function at a Destination PINX in the Order in which they were received in the Facility information element together with an indication of the pro- Primitive received from Coordination Function Primitive to Protocol (1 transfer Control to initiate FIE a-!j Start of Macro Exit
30、from Macro I/l Calling a Macro ISO/IEC 11582 : 1995 (E) tocol Profile. If the Protocol Profile (octet 3) in the received Facility infor- mation element does not indicate Networking Extensions, the indication of the protocol Profile to the Coordination Function shall reflect the contents of the Proto
31、col Profile. If the Protocol Profile (octet 3) in the received Facility infor- mation element indicates Networking Extensions, and a Network Protocol Profile (as determined by the tag value) is present in the received Facility information element immediately following the NFE, if present, or immediately following octet 3, the indication of protocol Profile to the Coordination Function shall reflect the contents of the Net- work Protocol Profile. If the Protocol Profile (octet 3) in the received Facility infor- mation element indicates Networking Extensions,
