ITU-T Q 86 3-1993 Stage 2 Description for Charging Supplementary Services Clause 3 - Reverse Charging (REV) - General Recommendations on Telephone Switching and Signalling FunctionSDN《.pdf

《ITU-T Q 86 3-1993 Stage 2 Description for Charging Supplementary Services Clause 3 - Reverse Charging (REV) - General Recommendations on Telephone Switching and Signalling FunctionSDN《.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 86 3-1993 Stage 2 Description for Charging Supplementary Services Clause 3 - Reverse Charging (REV) - General Recommendations on Telephone Switching and Signalling FunctionSDN《.pdf（50页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION)45G134 1 TELECOMMUNICATION (03/93)STANDARDIZATION SECTOROF ITU%.%2!,G0G02%#/-%.$!4)/.3G0G0/.G0G04%,%0(/.%37)4#().G0G0!.$G0G03).!,).b) the calling user, on a per call basis, to request that the call be charged to the called party from a timeduring the active phas

2、e of the call and the called party has the opportunity to accept or reject thosecharges; andc) the called user, on a per call basis, to request to be charged for the call from a time during the activephase.Recommendation Q.86 (03/93) 1Recommendation Q.86Recommendation Q.86 (03/93)STAGE 2 DESCRIPTION

3、 FOR CHARGING SUPPLEMENTARY SERVICES(Helsinki, 1993)3 Reverse Charging (REV)3.1 ScopeThis Recommendation defines the Stage 2 of the Integrated Services Digital Network (ISDN) as provided by thetelecommunications operators for the Reverse Charging (REV) supplementary service. Stage 2 identifies the f

4、unctionalcapabilities and the information flows needed to support the service description. The Stage 2 description also identifiesuser operations not directly associated with a call (see Recommendation I.130 1).This Recommendation is defined according to the methodology specified in Recommendation Q

5、.65 2.This Recommendation does not formally describe the relationship between this supplementary service and the basic callbut, where possible this information is included for guidance.In addition, this Recommendation does not specify the requirements where the service is provided to the user via ap

6、rivate ISDN. This Recommendation does not specify the requirements for the allocation of defined functional entitieswithin a private ISDN; it does however, define which functional entities may be allocated to a private ISDN.This Recommendation does specify the additional requirements where the servi

7、ce is provided to the user via aTelecommunications network that is not an ISDN.The Reverse Charging supplementary service is applicable to all telecommunication services.This Recommendation is applicable to the Stage 3 Recommendation for the Reverse Charging supplementary service, asdescribed in Rec

8、ommendation I.130 1.3.2 ReferencesThese references are cited at the appropriate places in the text and the publications are listed hereafter. Dated references,subsequent amendments to, or revisions of any of these publications apply to this Recommendation only whenincorporated in it by amendment or

9、revision. For undated references the latest edition of the publication referred toapplies.1 CCITT Recommendation Method for the characterization of telecommunication services supported by an ISDNand network, Rec. I.130, 1988.2 CCITT Recommendation Stage 2 of the method for the characterization of se

10、rvices supported by an ISDN,Rec. Q.65, 1988.3 CCITT Recommendation Reverse Charging (REV) supplementary service; service description, Rec. I.256.3.4 CCITT Recommendation Integrated Services Digital Network (ISDN); Basic call handling for circuit switchedbearer services; Functional capabilities and i

11、nformation flows, Rec. Q.71, 1992.5 CCITT Recommendation Vocabulary of terms for ISDNs, Rec. I.112, 1988.6 CCITT Recommendation Principles of telecommunication services supported by an ISDN and the means todescribe them, Rec. I.210, 1988.3.3 DefinitionsFor the purpose of this Recommendation, the fol

12、lowing definitions apply:Integrated Services Digital Network (ISDN): see 2.3/I.112 definition 308 5.Service: telecommunication service: see 2.2/I.112 definition 2015.Supplementary service: see 2.4/I.210 6.2 Recommendation Q.86 (03/93)3.4 Symbols and abbreviationsFor the purpose of this Recommendatio

13、n the following abbreviations are used:CC Call ControlCCA Call Control AgentFE Functional EntityFEA Functional Entity ActionISDN Integrated Services Digital NetworkLE Local ExchangePNX Private Network ExchangeREV Reverse ChargingTE Terminal Equipment3.5 Description3.5.1 General descriptionReverse Ch

14、arging is a service allowing a called user to be charged for the actual communication, that is for usage-basedcalls.There are four cases of Reverse Charging: Case A Reverse Charging requested by the calling user at the call set-up time. Case B Reverse Charging requested by the calling user during th

15、e active phase of the call. Case C Reverse Charging for the entire call requested by the called user during the active phase of theCase C call. Case D Reverse Charging unconditional.3.5.1.1 Case AThis supplementary service allows a calling user, on a per-call basis, to request Reverse Charging at th

16、e call set-up timeand the called user to accept or reject the charges including in the set-up response. If the called user accepts the request,the network starts charging the called user with notification of acceptance to the calling user and proceeds with the call.If the called user rejects or igno

17、res the request, the network notifies the calling user and disconnects the call.When a calling user does not explicitly request Reverse Charging, the calling user is charged as usual.In order to use this service, the originating terminal needs to have the capability for requesting Reverse Charging w

18、hilethe destination terminal needs to have the capability for accepting or rejecting Reverse Charging.3.5.1.2 Case BThis supplementary service allows a calling user, on a per-call basis, to request Reverse Charging during the activephase of the call and the called user to accept or reject the charge

19、s. If the called user accepts the request, the networkstarts charging the called user from that very moment on with notification of acceptance to the calling user and proceedswith the call.If the called user rejects or ignores the request, the network notifies the calling user while the existing cal

20、l remainsunaffected and the calling user is charged continuously.In order to use this service, the originating terminal needs to have the capability for requesting Reverse Charging whilethe destination terminal needs to have the capability for accepting or rejecting Reverse Charging.Recommendation Q

21、.86 (03/93) 33.5.1.3 Case CThis supplementary service allows a called user, on a per-call basis, to request Reverse Charging during the active phaseof the call.When a called user does not explicitly request Reverse Charging, the calling user is charged as usual.With this service the usage-based char

22、ges are charged to the called user.In order to use this service, the destination terminal needs to have the capability for requesting Reverse Charging.3.5.1.4 Case DRegardless whether a calling/called user requests Reverse Charging or not, all usage-based charges or some of them forselected services

23、 are charged to the called user.With this service the usage-based charges are charged to the called user, even if the calling user is not an ISDN user.3.5.2 Specific terminologyThroughout the Stage 2 description for Reverse Charging, the following terminology will be used: No Transfer mode This repr

24、esents that the charging function is done at the originating side when the NoReverse Charging is invoked. Transfer mode This represents that the charging function is done at the destination side when theReverse Charging is invoked.3.5.3 Qualification on the applicability to telecommunication service

25、sThis service is applicable to all telecommunication services.3.6 Derivation of the functional model3.6.1 Functional model descriptionThe functional model used for illustrating the Reverse Charging service procedures is shown in Figure 3-1.FE1 FE2 FE3 FE4T1134550-91/d01rarbrcFIGURE 3-1/Q.86Functiona

26、l Model for Reverse ChargingFIGURE 3-1/Q.86.D01 = 3.5 CM3.6.2 Description of the functional entityThe functional entities required by the Reverse Charging service in addition to those of the basic call are as follows:FE1: Originating Reverse Charging AgentThis represents the entity that requests Rev

27、erse Charging service at the originating side.FE2: Originating Reverse Charging Control EntityThis represents the entity that controls Reverse Charging service at originating side.4 Recommendation Q.86 (03/93)FE3: Destination Reverse Charging Control EntityThis represents the entity that controls Re

28、verse Charging service at destination side.FE4: Destination Reverse Charging AgentThis represents the entity that accepts/rejects/requests Reverse Charging service at the destination side.Both FE2 and FE3 has only the function that controls Reverse Charging service since the entity collecting the de

29、tail of acall for charging will be defined somewhere relating to the basic call control based on the future D-SeriesRecommendations.3.6.3 Relationship with the basic serviceRelationship functional model for Reverse Charging to basic service is shown in Figure 3-2.FE1 FE2 FE3 FE4CCA CC CC CC CCAT1134

30、560-91/d02r1r2r2r3rarbrcCCCCACall ControlCall Control AgentFIGURE 3-2/Q.86Relationship to a basic serviceFIGURE 3-2/Q.86.D02 = 5 CM3.7 Information flows3.7.1 Information flow diagramsThis subclause contains the information flow diagrams for not only successful cases but also unsuccessful cases(i.e.

31、rejection, ignoring).Two modes (i.e. No Transfer mode, Transfer mode) are given for each Case (Case A-Case D). No Transfer mode isdefined as a basic mode in this service while Transfer mode may be adopted as a service provider option.3.7.1.1 Information flows for Case A Figure 3-3: Successful inform

32、ation flows for Case A (No Transfer mode) Figure 3-4: Successful information flows for Case A (Transfer mode) Figure 3-5: Unsuccessful information flows for Case A (Reject) Figure 3-6: Unsuccessful information flows for Case A (Ignoring)3.7.1.2 Information flows for Case B Figure 3-7: Successful inf

33、ormation flows for Case B (No Transfer mode) Figure 3-8: Successful information flows for Case B (Transfer mode) Figure 3-9: Unsuccessful information flows for Case B (Reject) Figure 3-10: Unsuccessful information flows for Case B (Ignoring)Recommendation Q.86 (03/93) 53.7.1.3 Information flows for

34、Case C Figure 3-11: Successful information flows for Case C (No Transfer mode) Figure 3-12: Successful information flows for Case C (Transfer mode)3.7.1.4 Information flows for Case D Figure 3-13: Successful information flows for Case D (No Transfer mode) Figure 3-14: Successful information flows fo

35、r Case D (Transfer mode)921911922941FE1FE2FE3 FE493193293393N93493P93592492592J926912T1143920-92/d03942927211211 221221 241241 25125124524522422432142192392IrarbrcSETUPreq.SETUPreq. ind.INFORM 1req. ind.SETUPreq. ind.INFORM 2req. ind.SETUPreq. ind.INFORM 3req. ind.SETUPresp. conf.INFORM 3resp. conf.

36、SETUPresp. conf.INFORM 2resp. conf.SETUPresp. conf.INFORM 1resp. conf.DISCONNECTreq. ind.SETUP conf.(REVacceptance)RELEASEreq. ind.SETUP ind.(REV req.)(REVacceptance)SETUP resp.FIGURE 3-3/Q.86Successful information flows for Case A (No Transfer mode)(REV req.)FIGURE 3-3/Q.86.D03 = 18 CM6 Recommendat

37、ion Q.86 (03/93)921911941FE1 FE2 FE3 FE492392I93393H93592J926912931932936942924928938T1143930-92/d0493493P937211211 221221 241241 251245245224224341 441rarbrcSETUPreq. ind.INFORM 1req. ind.SETUPreq. ind.INFORM 2req. ind.SETUPreq. ind.INFORM 3req. ind.SETUPresp. conf.INFORM 3resp. conf.SETUPresp. con

38、f.INFORM 2resp. conf.SETUPresp. conf.INFORM 1resp. conf.SETUP conf.(REVacceptance)RELEASEreq. ind.SETUP ind.(REV req.)(REVacceptance)SETUP resp.FIGURE 3-4/Q.86Successful information flows for Case A (Transfer mode)DISCONNECTreq. ind.SETUP req.(REV req.)FIGURE 3-4/Q.86.D04 = 17 CMRecommendation Q.86

39、(03/93) 7FE1 FE2 FE3 FE493493P92691294293593M924921929FE1 FE2 FE3 FE492694293593M93493P93992492JT1143940-92/d05245245421421421411912421411rarcrarcrbrbSETUP resp.(REV reject)SETUPresp. conf.RELEASEreq. ind.INFORM 3resp. conf.RELEASEreq. ind.INFORM 2resp. conf.DISCONNECTreq. ind.INFORM 1resp. conf.REL

40、EASE ind.(REV reject)SETUP resp.(REV reject)SETUPresp. conf.RELEASEreq. ind.INFORM 3resp. conf.RELEASEreq. ind.INFORM 2resp. conf.DISCONNECTreq. ind.INFORM 1resp. conf.RELEASE ind.(REV reject)AG9G0.OG04RANSFERG0-ODEBG9G04RANSFERG0-ODENOTE These information flows follow the Reverse Charging request i

41、nformation flows which are shown in Figure 3-3(No Transfer mode) and Figure 3-4 (Transfer mode).FIGURE 3-5/Q.86Unsuccessful information flows for Case A (Reject)FIGURE 3-5/Q.86.D05 = 22 CM PAGE PLEINE8 Recommendation Q.86 (03/93)FE1 FE2 FE3 FE492691292IFE1 FE2 FE3 FE492691292492J930935930939935T1143

42、950-92/d06924929245421421411245421421411rarbrcrarbrcSETUP resp.SETUPresp. conf.RELEASEreq. ind.RELEASEreq. ind.INFORM 2resp. conf.DISCONNECTreq. ind.INFORM 1resp. conf.RELEASE ind.(REV ignore)SETUP resp.(REV reject)SETUPresp. conf.RELEASEreq. ind.RELEASEreq. ind.INFORM 2resp. conf.DISCONNECTreq. ind

43、.INFORM 1resp. conf.RELEASE ind.(REV ignore)AG9G0.OG04RANSFERG0-ODEBG9G04RANSFERG0-ODENOTE These information flows follow the Reverse Charging request information flows which are shown in Figure 3-3(No Transfer mode) and Figure 3-4 (Transfer mode).FIGURE 3-6/Q.86Unsuccessful information flows for Ca

44、se A (Ignore)FIGURE 3-6/Q.86.D06 = 22 CM PAGE PLEINERecommendation Q.86 (03/93) 9921911941FE1 FE2 FE3 FE493591294292392093193293393A93493B92492A92B925926927T1143960-92/d07321 421rarbrcREV req.INFORM 1req. ind.INFORM 2req. ind.INFORM 3req. ind.INFORM 3resp. conf.REV req.REVacceptanceINFORM 2resp. con

45、f.REVacceptanceINFORM 1resp. conf.DISCONNECTreq. ind.RELEASEreq. ind.FIGURE 3-7/Q.86Successful information flows for Case B during active phaseof a call (No Transfer mode)FIGURE 3-7/Q.86.D07 = 17 CM10 Recommendation Q.86 (03/93)921911941FE1FE2FE3FE491294292392093393A93493B92493193293693793592A92B926

46、T1143970-92/d08938341 441rbrcraREV req.INFORM 1req. ind.INFORM 2req. ind.INFORM 3req. ind.INFORM 3resp. conf.REV req.REVacceptanceINFORM 2resp. conf.REVacceptanceINFORM 1resp. conf.RELEASEreq. ind.FIGURE 3-8/Q.86Successful information flows for Case B during active phaseof a call (Transfer mode)DISC

47、ONNECTreq. ind.FIGURE 3-8/Q.86.D08 = 17 CMRecommendation Q.86 (03/93) 11FE1 FE2 FE3 FE493591294292492A92693493BFE1 FE2 FE3 FE491294293493B939935T1143980-92/d0992492A926rarcrbrarcrbINFORM 3resp. conf.INFORM 2resp. conf.INFORM 1resp. conf.BG9G04RANSFERG0-ODENOTE These information flows follow the Reve

48、rse Charging request information flows which are shown in Figure 3-7(No Transfer mode) and Figure 3-8 (Transfer mode).FIGURE 3-9/Q.86Unsuccessful information flows for Case B duringactive phase of a call (Reject)REV rejectREV rejectINFORM 3resp. conf.INFORM 2resp. conf.INFORM 1resp. conf.REV rejectR

49、EV rejectAG9G0.OG04RANSFERG0-ODEFIGURE 3-9/Q.86.D09 = 18 CM12 Recommendation Q.86 (03/93)FE1 FE2 FE3 FE493591292492A92693CFE1 FE2 FE3 FE491293C939935T1143990-92/d1092492A926rarcrbrarcrbINFORM 2resp. conf.INFORM 1resp. conf.BG9G04RANSFERG0-ODENOTE These information flows follow the Reverse Charging request information flows which are shown in Figure 3-7(No Transfer mode) and Figure 3-8 (Transfer mode).FIGURE 3-10/Q.86Unsuccessful information flows for Case B duringactive phase