TIA EIA IS-826 1-2000 Wireless Intelligent Network Capabilities for Pre-Paid Charging Chapter 1 Overview《预付费业务无线智能网络功能 第1章 概述 亦可参见TIA-826-A》.pdf

《TIA EIA IS-826 1-2000 Wireless Intelligent Network Capabilities for Pre-Paid Charging Chapter 1 Overview《预付费业务无线智能网络功能 第1章 概述 亦可参见TIA-826-A》.pdf》由会员分享，可在线阅读，更多相关《TIA EIA IS-826 1-2000 Wireless Intelligent Network Capabilities for Pre-Paid Charging Chapter 1 Overview《预付费业务无线智能网络功能 第1章 概述 亦可参见TIA-826-A》.pdf（16页珍藏版）》请在麦多课文档分享上搜索。

1、TIAIEIA INTERIM STANDARD Wireless Intelligent Network Capabilities for Pre-Paid Charging Chapter 1 Overview TIA/EIA/IS-826.1 AUGUST 2000 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Representing the tekcommunications indushy in association with the Electronic Industries Alance Elsctrrrnir industrim Allia

2、nce NOTICE TIA/EIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with min

3、imum delay the proper product for his particular need. Existence of such Standards and Publications shall not in any respect preclude any member or nonmember of TIA/EIA from manufacturing or selling products not conforming to such Standards and Publications, nor shall the existence of such Standards

4、 and Publications preclude their voluntary use by those other than TIA/EIA members, whether the standard is to be used either domestically or internationally. Standards and Publications are adopted by TIA/EIA in accordance with the American National Standards Institute (ANSI) patent policy. By such

5、action, TIA/EIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. TIA/EIA INTERIM STANDARDS TIA/EIA Interim Standards contain information deemed to be of technical value to the industry, and are published at

6、 the request of the originating Committee without necessarily following the rigorous public review and resolution of comments which is a procedural part of the development of a TIA/EIA Standard. TIA/EIA Interim Standards should be reviewed on an annual basis by the formulating Committee and a decisi

7、on made on whether to proceed to develop a TIA/EIA Standard on this subject. TIA/EIA Interim Standards must be cancelled by the Committee and removed from the TIA/EIA Standards Catalog before the end of their third year of existence. Publication of this TIA/EIA Interim Standard for trial use and com

8、ment has been approved by the Telecommunications Industry Association. Distribution of this TIA/EIA Interim Standard for comment shall not continue beyond 36 months from the date of publication. It is expected that following this 36 month period, this TIA/EIA Interim Standard, revised as necessary,

9、will be submitted to the American National Standards Institute for approval as an American National Standard. Suggestions for revision should be directed to: Standards Telecommunications Industry Association; June 1996 ANSZLZMEZA-41 -D, Cellular Radiotelecommunications Intersystem Operations; Teleco

10、mmunications Industry Association; 1997 Telecommunications Industry Association; February 1998 TZMEZMZS-771, Wireless Intelligent Network; Telecommunications Industry Association; December 1998 TZMEZMZS-751, TZMEZA-41-D Modifications to Support IMSI; 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 2

11、0 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Foreword TINEINIS-826 Rev. O 1 Date Remarks June 2000 Initial Publication : REVISION HISTORY 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 3

12、4 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Revision History TINEINIS-826 Revision History (This page intentionally left blank.) 1 -iv 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46

13、47 48 49 50 51 52 53 54 55 56 57 58 59 60 TINEINIS-826 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 1 INTRODUCTION 1 .I 1.2 1.3 Pre-Paid Charging (PPC) allows the subscriber

14、to pay for voice telecommunication services prior to usage. This document presents a recommended plan for the implementation of Wireless Intelligent Network (WIN) capabilities that support PPC. The WIN capabilities that support PPC are for use in the Wireless Radiotelephone Service. GENERAL This doc

15、ument describes the WIN capabilities needed for PPC and the intersystem operations to enable a wireless subscriber to use the intelligent network capabilities in systems into which the subscriber roams. OBJECTIVE The purpose of this document is to describe the WIN capabilities needed for PPC and to

16、specify the WIN operation so that a roaming wireless subscriber can access the intelligent network capabilities in a seamless manner. The purpose of this document is also to describe the modifications to WIN operations (including the WIN operations initially specified in TZMEZMZS-771) needed to supp

17、ort IMSI. O RG A N I ZAT I O N This document is organized as follows: Chapter 2 provides Stage 1 feature descriptions for PPC according to the structure of TZMEZA -664. Chapter 3 provides the modifications and additions to TZMEZA-41-D Chapter 1 “Functional Overview for PPC. Chapter 43 provides the m

18、odifications and additions to TZMEZA-41 -D Chapter “Automatic Roaming Information Flows” for PPC. Chapter 55 provides the modifications and additions to TZMEZA-41 -D Chapter “Signaling Protocol” for PPC. Chapter 66 provides the modifications and additions to TZMEZA-41 -D Chapter “Signaling Procedure

19、s” for PPC. Chapter 7 provides the modifications and additions to TZMEZMZS-771 Chapter 7 “Distributed Functional Plane” for PPC. 1-1 Introduction TINEINIS-826 single vertical change bar: indicates TZMEZMZS-771 additions or deletions double vertical change bar: indicates additions or deletions for th

20、is Interim Standard 1.4 EDITORIAL CONVENTIONS 24 25 26 1 2 The following editorial conventions are used in this Interim Standard for Chapters 1, 2, 3, 4,5 and 7: 3 4 5 underline: additions eesseut: deletions single vertical change bar: indicates additions or deletions new sub-sections are identified

21、 in the sub-section heading 9 I lo I 11 12 13 14 15 for clarity, new sub-sections are shown with single vertical change bars but are not underlined 16 17 The following editorial conventions are used in this Interim Standard for Chapter 6: underline: TZMEZMZS-771 additions double underline: additions

22、 for this Interim Standard 18 19 20 21 not underlined 1.5 ASSUMPTIONS The following assumptions were used in the development of this standard: 31 32 33 34 35 36 37 38 39 40 41 1. Pre-Paid Charging (PPC) is invoked before any other services are invoked to verify a positive account balance. If the sub

23、scribers account balance is at or below threshold, all services may be blocked. A PPC subscriber with a balance at or below threshold, may be connected to a customer service representative automatically when attempting to originate any call so that the account can be refilled. An announcement may be

24、 played when an MS originates a call to inform the subscriber of his or her account balance. The account balance may be presented to the subscriber as the amount of time remaining in the account. The call routing information needed to rate the call must be available to PPC service logic before the a

25、nnouncement can be played. 2. 42 43 44 45 46 47 48 49 50 51 3. A subscriber (or surrogate) is notified of a low account balance by a “low balance” tone or optionally a switch-based announcement being played during a call. The subscriber is expected to end the current call in a timely fashion and to

26、refill the PPC account. End-of-Call announcements are not provided to the PPC subscriber at the end of an incoming call. 52 53 54 56 55 4. 57 58 59 60 Introduction 1-2 TINEINIS-826 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43

27、 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. PPC service logic may end the current subscriber call (or calls). A “disconnect warning” tone or announcement is played to the subscriber (or surrogate) before the call is disconnected. The cha

28、rges for a call may start when the call is answered or as determined by the service provider. The charges for a call may stop when the call is disconnected. The PPC service logic has access to all the subscriber profile information needed to provide the service (e.g., subscribers preferred language)

29、. A subscribers PPC account is identified by the subscribers MSID or MDN or both. Call rating for call delivery involves the time of day in both the originating and the serving systems. Long distance charges are based on home system time. Local and air time charges are based on serving system time.

30、The time of day of the Originating MSC is included in the query message sent to the PPC service logic program instance (SLPI) when a routing address is available (Le., at the Analyzed-Information DP). This information is used by the SLPI to calculate an approximate rate for the call using “nominal”

31、local charges at the Serving MSC. When the call is answered by the mobile subscriber, the query message to the PPC SLPI includes the time of day at the Serving MSC enabling the PPC SLPI to have the accurate local charge information needed to rate the call. Call rating for mobile originated calls inv

32、olves the time of day in the serving system. Some calls may be free (e.g., calls to customer service). Only voice telecommunications services are considered. The interaction of the Call Transfer service and the PPC service is not considered. The interaction of the Conference Calling service and the

33、PPC service is not considered. Impacts of Wireless Number Portability Phase II (TZMEZMZS-756-A) have not been considered (e.g., signaling procedures). PPC information may be sent to an MS for display. This information is conveyed in the DisplayText parameter using the Text e.g., ASCII Display Tag va

34、lue (see ANSI T1.610). When the subscriber is engaged in a three-way call with one leg of the call to a locally allowed number (e.g., 9-1-1) which the PPC SCF may not be aware of, the MSC ignores any ActionCode parameter value received from the SCF in a CallControlDirective INVOKE. The MSC indicates

35、 that no action was taken due to the locally allowed call to the SCF in the CallControlDirective RETURN RESULT. SIM relay of a CallControlDirective INVOKE is not considered in this standard. SIM relay of an UnreliableCallData INVOKE is not considered in this standard. 1-3 Introduction TINEINIS-826 1

36、.6 DFP IMPACTS The following WIN DFP modifications are described in this standard: a. b. C. d. e. f. The Origination-AttemptAuthorized trigger has been defined for the Origination-Attempt-Authorized DP. This trigger can be used to invoke PPC for an MS originated call after the MSC authorizes the MS

37、origination and determines that the call is not to a locally allowed number (e.g., 9-1-1). The Origination-Attempt-Authorized trigger is armed as a TDP-R for the scenarios in this standard. The OriginationRequest operation is used to query service logic when the Origination-Attempt-Authorized trigge

38、r is encountered. The TriggerType parameter is set to indicate the trigger was encountered. The Initial-Termination trigger has been defined for the Analyzed-Information DP. This trigger is armed for the called subscriber by the TriggerAddressList parameter received in the locreq returned to the MSC

39、 after the Mobile-Termination trigger was encountered. The Initial-Termination trigger is armed as a TDP-R for the scenarios in this standard. The Analyzedhformation operation is used to notify the SLPI that a call is requested to be delivered to a pre-paid subscriber. The TriggerType parameter is s

40、et to indicate this trigger was encountered. The CallingRouting-Address-Available trigger has been defined for the Analyzed-Information DP. This trigger is armed for the calling PPC subscriber. It is used to convey a routing address and call type to the SLPI. The Calling-Routing-Address-Available tr

41、igger is armed as a TDP-R for the scenarios in this standard. The Analyzedhformation operation is used to notify service logic of the availability of a routing address. The TriggerType parameter is set to indicate this trigger was encountered. The Called-Routing-Address-Available trigger has been de

42、fined for the Analyzed-Information DP. This trigger is armed for the called pre-paid subscriber. It is used to convey a routing address and call type to the SLPI. The Called-Routing-Address-Available trigger is armed as a TDP-R for the scenarios in this standard. The Analyzedhformation operation is

43、used to notify service logic of the availability of a routing address. The TriggerType parameter is set to indicate this trigger was encountered. The O-Answer trigger has been defined for the O-Answer DP. This trigger (an existing CS-2 trigger) can be used to notify the SLPI of call answer for a cal

44、l originated at an MSC (e.g., MS origination) or for a call forwarded by the MSC. The O-Answer trigger is armed as a TDP-N for the calling PPC subscriber for scenarios illustrated in this standard. The new OAnswer operation is used to notify the SLPI of the call answer. The T-Answer trigger has been

45、 defined for the T-Answer DP. This trigger (an existing CS-2 trigger) can be used to notify service logic of call answer for a call terminated at an MSC (e.g., MS terminated call). 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43

46、 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Introduction 1-4 TINEINIS-826 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 The T-Answer trigger is armed as a TDP-N for th

47、e PPC scenarios illustrated in this standard. The new TAnswer operation is used to notify service logic for the call answer by a called PPC subscriber. The O-Disconnect trigger has been defined for the O-Disconnect DP. This trigger (an existing CS-2 trigger) can be used to notify the SLPI of call di

48、sconnect for a call originated at an MSC (e.g., MS origination) or for a call forwarded by the MSC. The O-Disconnect trigger is armed as a TDP-R for a calling subscriber for the PPC scenarios illustrated in this standard. The new ODisconnect operation is used to query the SLPI upon call disconnect.

49、The T-Disconnect trigger has been defined for the T-Disconnect DP. This trigger (an existing CS-2 trigger) can be used to notify the SLPI of call disconnect for a call terminated at an MSC (e.g., MS terminated call). The T-Disconnect trigger is armed as a TDP-R for the called subscriber for the PPC scenarios illustrated in this standard. The new TDisconnect operation is used to query the SLPI upon call disconnect. g. h. i. The Locally-Allowed-Specific-Digit-String trigger has been defined for the Origination-Attempt-Authorized DP. This Office-based trigger can be used to invoke servi