《ISO-13241-1997.pdf》由会员分享，可在线阅读，更多相关《ISO-13241-1997.pdf（21页珍藏版）》请在三一文库上搜索。
1、INTERNATIONAL STANDARD ISO/IEC 13241 First edition 1997-06-l 5 Information technology - Telecommunications and information exchange between systems - Private Integrated Services Network - Inter-exchange signalling protocol - Route Restriction Class additional network feature Technologies de /informa
2、tion - T 3outeRestrictionClass := OPERATION ARGUMENT RAC 3AC - - SEQUENCE rat INTEGER (099), extension CHOICE l IMPLICIT Extension, 2 IMPLICIT SEQUENCE OF Extension OPTIONAL I outeRestrictionClass RouteRestrictionClass:= 83 :ND - of Route-Restriction-Class-Operations 6.3.2 Information elements 6.3.2
3、.1 Facility information element APDUs of the operations defined in 6.3.1 shall be coded in the Facility information element in accordance with ISO/IEC 11582. Apart from the exceptions specified in 6.8.3 and 6.8.10, when conveying the invoke APDU of operation routeRestrictionClass, the destinationEnt
4、ity data element of the NFE shall contain value anyTypeOfPINX and the destinationEntityAddress data element shall be omitted. NOTE 1 This allows the invoke APDU to be passed through any Transit PINX that does not recognise it. When conveying the invoke APDU of operation routeRestrictionClass, the In
5、terpretation APDU shall be included and shall have the value discardAnyUnrecognisedInvokePdu. 4 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/19/2007 06:12:14 MDTNo reproduction or net
6、working permitted without license from IHS -,-,- OISO/IEC ISOAEC 13241:1997(E) 6.3.3 Messages The Facility information element shall be conveyed in a SETUP message as specified in ISO/IEC 11582. 6.4 ANF-RRC state definitions No additional states beyond those identified in ISO/IEC 11572 and 11582 are
7、 needed for ANF-RRC. 6.5 ANF-RRC signalling procedures The signalling procedures specified below are in support of sending and receiving the RAC. 6.5.1 Actions at the Originating PINX The SDL representation of procedures at the Originating PINX is shown in Figure B. 1 of Annex B. 6.5.1 .l Normal pro
8、cedures A call shall be allowed to be established only if the calling users RAC is such that any facilities required for routeing out of the Originating PINX have FRCs that are allowed to be used by that RAC. If establishment is allowed, the SETUP message shall contain a routeRestrictionC1ass invoke
9、 APDU containing the calls RAC value. 6.5.1.2 Exceptional procedures If the RAC associated with the calling user does not permit call establishment, the Originating PINX shall not proceed with call establishment. 6.5.2 Actions at a Transit PINX The SDL representation of procedures at the Transit PIN
10、X is shown in Figure B.2 of Annex B. 6.5.2.1 Normal procedures On receipt of a SETUP message containing a routeRestrictionClass invoke APDU, the Transit PINX shall make use of the RAC received in that APDU. On receipt of a SETUP message containing no routeRestrictionC1ass invoke APDU, the Transit PI
11、NX may use a default RAC based on the particular incoming route. If an RAC is being used, the Transit PINX shall allow the call to be routed further only if the RAC is such that any facilities required have FRCs that are allowed to be used by that RAC. If further routeing is allowed, the SETUP messa
12、ge sent on the next inter-PINX link shall contain a routeRestrictionC1ass invoke APDU containing the calls RAC value. 6.5.2.2 Exceptional procedures If the RAC used does not permit further routeing, the Transit PINX shall initiate release of the call using an appropriate cause value from the range 3
13、3 to 47 (resource unavailable class), e.g. cause 34 “no circuit/channel available”. NOTE 2 Interactions with other supplementary services or ANFs that are not described in 6.8 can lead to alternative actions in this situation (e.g. interception to an attendant). 6.5.3 Actions at a Terminating PINX A
14、 routeRestrictionC1ass invoke APDU shall be discarded by the Terminating PINX. 6.6 ANF-RRC impact of interworking with Public ISDNs 6.6.1 Actions at an Incoming Gateway PINX 6.6.1 .l Normal procedures On receipt of a call establishment request from a public ISDN, the Incoming Gateway PINX may use a
15、default RAC based on the particular incoming route or an RAC provided by the other network. If an RAC is being used, the Incoming Gateway PINX shall allow the call to be routed further only if the RAC is such that any facilities required have FRCs that are allowed to be used by that RAC. If further
16、routeing is allowed, the SETUP message sent on the inter-PINX link shall contain a routeRestrictionC1ass invoke APDU containing the calls RAC value. 5 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not fo
17、r Resale, 04/19/2007 06:12:14 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 13241:1997(E) OISO/IEC 6.6.1.2 Exceptional procedures If the RAC used does not permit further routeing, the Incoming Gateway PINX shall not allow call establishment to proceed. 6.6.2 Actio
18、ns at an Outgoing Gateway PINX 6.6.2.1 Normal procedures On receipt of a SETUP message containing a routeRestrictionClass invoke APDU, the Outgoing Gateway PINX shall make use of the RAC received in that APDU. On receipt of a SETUP message containing no routeRestrictionClass invoke APDU, the Outgoin
19、g Gateway PINX may use a default RAC based on the particular incoming route. If an RAC is being used, the Outgoing Gateway PINX shall allow the call to be routed to the public ISDN only if the RAC is such that any facilities required have FRCs that are allowed to be used by that RAC. 6.6.2.2 Excepti
20、onal procedures If the RAC used does not permit routeing to the public ISDN, the Outgoing Gateway PINX shall initiate release of the call using an appropriate cause value from the range 33 to 47 (resource unavailable class), e.g. cause 34 “no circuit/channel available”. NOTE 3 Interactions with othe
21、r supplementary services or ANFs that are not described in 6.8 can lead to alternative actions in this situation (e.g. interception to an attendant). 6.7 ANF-RRC impact of interworking with non-ISDNs 6.7.1 Actions at an Incoming Gateway PINX 6.7.1 .l Normal procedures On receipt of a call establishm
22、ent request from a non-ISDN, the Incoming Gateway PINX may use a default RAC based on the particular incoming route or an RAC provided by the other network. If an RAC is being used, the Incoming Gateway PINX shall allow the call to be routed further only if the RAC is such that any facilities requir
23、ed have FRCs that are allowed to be used by that RAC. If further routeing is allowed, the SETUP message sent on the inter-PINX link shall contain a routeRestrictionClass invoke APDU containing the calls RAC value. 6.7.1.2 Exceptional procedures If the RAC used does not permit further routeing, the I
24、ncoming Gateway PINX shall not allow call establishment to proceed. 6.7.2 Actions at an Outgoing Gateway PINX 6.7.2.1 Normal procedures On receipt of a SETUP message containing a routeRestrictionClass invoke APDU, the Outgoing Gateway PINX shall make use of the RAC received in that APDU. On receipt
25、of a SETUP message containing no routeRestrictionClass invoke APDU, the Outgoing Gateway PINX may use a default RAC based on the particular incoming route. If an RAC is being used, the Outgoing Gateway PINX shall allow the call to be routed to the non-ISDN only if the RAC is such that any facilities
26、 required have FRCs that are allowed to be used by that RAC. NOTE 4 The RAC value can be forwarded to the non-ISDN, if applicable. 6.7.2.2 Exceptional procedures If the RAC used does not permit routeing to the non-ISDN, the Outgoing Gateway PINX shall initiate release of the call using an appropriat
27、e cause value from the range 33 to 47 (resource unavailable class), e.g. cause 34 “no circuit/channel available”. NOTE 5 Interactions with other supplementary services or ANFs that arc not described in 6.8 can lead to alternative actions in this situation (e.g. interception to an attendant). Copyrig
28、ht International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/19/2007 06:12:14 MDTNo reproduction or networking permitted without license from IHS -,-,- OISO/IEC ISO/IEC 13241:1997(E) 6.8 Protocol interactio
29、ns between ANF-RRC and other supplementary services and ANFs This clause specifies protocol interactions with other supplementary services and ANFs for which stage 3 Standards had been published at the time of publication of this International Standard. For interactions with supplementary services a
30、nd ANFs for which stage 3 Standards are published subsequent to the publication of this International Standard, see those other stage 3 Standards. Additional interactions that have no impact on the signalling protocol at the Q reference point can be found in the relevant stage 1 specifications. 6.8.
31、1 Interaction with Calling Name Identification Presentation (SS-CNIP) No interaction. 6.8.2 Interaction with Connected Name Identification Presentation (SS-CONP) No interaction. 6.8.3 Interaction with Call Forwarding Unconditional (SS-CFU) In the case of call diversion by rerouteing, the SS-CF Serve
32、d User PINX shall include the routeRestrictionClass Invoke APDU in the same message as the CallRerouteing Invoke APDU. The RAC value used shall be either that of the served user or that of the calling user. The destinationEntity data element of the NFE shall contain the value endPINX. If the Reroute
33、ing PINX receives a routeRestrictionClass Invoke APDU, it shall utilize the received RAC and proceed in accordance with 6.5.1.1 or 6.5.2.1, as appropriate, when rerouteing the call. If the Rerouteing PINX does not receive a routeRestrictionClass Invoke APDU, the Rerouteing PINX is responsible for as
34、signing the RAC to be used for the rerouteing for the call (e.g. the RAC for the calling user). 6.8.4 Interaction with Call Forwarding Busy (SS-CFB) As for SS-CFU (6.8.3). 6.8.5 Interaction with Call Forwarding No Reply (SS-CFNR) As for SS-CFU (6.8.3). 6.8.6 Interaction with Call Deflection (SS-CD)
35、The protocol interactions with Call Deflection Immediate shall be as specified in 6.8.3 for interaction with SS-CFU. The protocol interactions with Call Deflection from Alert shall be as specified in 6.8.5 for interaction with SS-CFNR. 6.8.7 Interaction with Call Transfer (SS-CT) No interaction. 6.8
36、.8 Interaction with Completion of Calls to Busy Subscriber (SS-CCBS) No interaction. 6.8.9 Interaction with Completion of Calls on No Reply (SS-CCNR) No interaction. 6.8.10 Interaction with Path Replacement (ANF-PR) 6.8.10.1 Actions at the ANF-PR Requesting PINX The Requesting PINX may include a rou
37、teRestrictionClass invoke APDU in the FACILITY message in which the pathReplacePropose invoke APDU is sent, in order to indicate an RAC that may be used for establishment of the new connection. The RAC can, for example, be the RAC of the local user. The destinationEntity data element of the NFE shal
38、l contain the value endPINX. 7 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/19/2007 06:12:14 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 13241:19
39、97(E) OISO/IEC A routeRestrictionClass invoke APDU in a SETUP message containing a pathReplaceSetup invoke APDU shall be discarded by the Requesting PINX. 6.8.10.2 Actions at the ANF-PR Cooperating PINX If the received FACILITY message containing the pathReplacePropose invoke APDU contains a routeRe
40、strictionClass invoke APDU, the RAC contained in that invoke APDU may be used for establishment of the new connection. Otherwise, the Cooperating PINX may assign an RAC, which can, for example, be the RAC associated with the local user. If an RAC is being used, the new connection shall be allowed to
41、 be established only if the RAC is such that any facilities required for routeing out of the Cooperating PINX have FRCs that are allowed to be used by that RAC. If establishment is allowed, the SETUP message containing the pathReplaceSetup invoke APDU shall contain a routeRestrictionClass invoke APD
42、U containing the new connections RAC value. If the Cooperating PINX attempts to retain some or all or the existing connection, it shall include the RAC in a routeRestrictionClass invoke APDU with no NFE in the FACILITY message containing the pathReplaceRetain invoke APDU with no NFE. 6.8.10.3 Action
43、s at a Transit PINX on the path of the new connection The procedures of 6.5.2 shall apply. 6.8.10.4 Actions at a Transit PINX on the path of the retained connection On receipt of a FACILITY message containing a pathReplaceRetain invoke APDU and a routeRestrictionClass invoke APDU, the Transit PINX s
44、hall make use of the RAC received in that APDU. On receipt of a FACILITY message containing a pathReplaceRetain invoke APDU but no routeRestrictionClass invoke APDU, the Transit PINX may use a default RAC based on the particular incoming route. If an RAC is being used, the Transit PINX shall allow a
45、 new connection to be established only if the RAC is such that any facilities required have FRCs that are allowed to be used by that RAC. If establishment is allowed, the SETUP message sent on the next inter-PINX link shall contain a routeRestrictionClass invoke APDU containing the new connections R
46、AC value. If an RAC is being used and the Transit PINX is able to retain the old connection as far as the subsequent PINX, the Transit PINX shall include a routeRestrictionClass invoke APDU in the FACILITY message containing the pathReplaceRetain invoke APDU. If the RAC used does not permit establis
47、hment of a new connection and the Transit PINX is unable to retain that part of the old connection as far as the subsequent PINX, the Transit PINX shall return a pathReplaceRetain return error APDU. 6.8.11 Interaction with Call Offer (SS-CO) No interaction. 6.8.12 Interaction with Call Intrusion (SS
48、-Cl) No interaction. 6.8.13 Interaction with Do Not Disturb (SS-DND) No interaction. 6.8.14 Interaction with Do Not Disturb Override (SS-DNDO) No interaction. 6.9 ANF-RRC parameter values (Timers) No interaction. Copyright International Organization for Standardization Provided by IHS under license
49、with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/19/2007 06:12:14 MDTNo reproduction or networking permitted without license from IHS -,-,- OISO/IEC ISO/IEC 13241: 1997(E) Annex A (normative) Protocol Implementation Conformance Statement (PICS) proforma A.1 Introduction The supplier of a protocol implementation which is claimed to