1、TIA/EIA INTERIM STANDARD Wireless Intelligent Network Capabilities for Pre-Paid Charging Chapter 7 Modifications to TIAEIAIS-771 Distributed Functional Plane TIAEIAIS-826.7 AUGUST 2000 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Representing the telecommunications indushy in association with the Electro
2、nic Industries Aiance Elsctrrrnr industrim Alliance 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 t
3、he purchaser in selecting and obtaining with minimum 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 Publica
4、tions, nor shall the existence of such Standards 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 St
5、andards Institute (ANSI) patent policy. By such 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 techn
6、ical value to the industry, and are published at 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
7、 basis by the formulating Committee and a decision 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 thi
8、s TIA/EIA Interim Standard for trial use and comment 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
9、TIA/EIA Interim Standard, revised as necessary, will be submitted to the American National Standards Institute for approval as an American National Standard. Suggestions for revision should be directed to: Standards or, ii) a call-rejected indication is received from the terminating half BCSM (T-Ale
10、rting PIC) that does not specify busy. - An indication is received from the terminating half BCSM that the terminating party does not answer. (DP: ONo-Answer). An indication is received from the terminating half BCSM that the terminating party is being alerted. (DP: OTerm-Seized). An indication is r
11、eceived from the terminating half BCSM that the call is accepted and answered by the terminating party. (DP: O-Answer DP). A route-failure event is detected when: - - - 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 a 21 22 23 24 25 28 27 2% 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
12、48 49 50 51 52 53 54 56 56 57 58 58 60 Originating BCSM 7-8 TINEINIS-771.7 Modifications 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 a 21 22 23 24 25 28 27 2% 29 30 31 32 33 34 35 36 37 38 39 40 4 42 43 44 45 46 47 48 49 50 51 52 53 54 56 56 57 58 58 60 i) ii) iii) TINEINIS-826 an indication of
13、a TBusy event specifying route busy; is received from the terminating half BCSM, or an indication of a call-rejected event specifying route busy (received when the route is found to be busy at a switch other than the local switch) is received from the terminating half BCSM (T-Alerting PIC). an indic
14、ation of a presentation-failure event specifying route busy is received from the terminating half BCSM (PresentLCall PIC). In all these cases, the originating half BCSM returns to the Select-Route PIC. This event is not detected at a DP. Note: The route-failure event takes precedence over the O-Call
15、ed-PartyBusy and ONo-Answer events. An indication is received from the RCF of a service feature request by the originating MS. (DP: OMid-Call). For SS7-supported trunk interface, the authorization-route-failure event occurs when the continuity check procedure results in failure. This event causes a
16、transition to the OException PIC. Originating party abandons the call. (DP: O-Abandon). - - - O-Alerting Entry Event: - An indication is received from terminating half BCSM that the terminating party is being alerted. (DP: OTern-Seized). Functions: - - Continue processing of call setup. Waiting for
17、indication from the terminating half BCSM that the call has been answered by the terminating party. Exit Event: - A route failure event is detected when all of the following conditions are met: i) the O-Called-PartyBusy event or ONo-Answer event occurs as specified below, ii) call forwarding applies
18、, iii) there are more called party numbers left to try. Note: the RouteFailure event takes precedence over the O-Called-PartyBusy and ONo-Answer events. In this case the originating call portion returns to the Select-Route PIC. This event is not detected at a DP in WIN. An indication is received fro
19、m the terminating half BCSM that the terminating party does not answer within a specified time period. (DP: ONo-Answer). An indication is received from the terminating half BCSM that the call is accepted and answered by the terminating party. (DP: O-Answer). - - TINEINIS-771.7 Modifications 7-9 Orig
20、inating BCSM TINEINIS-826 - From this PIC, the O-Called-PartyBusy event occurs either when: i) an indication of a call-rejected event specifying user busy is received from the terminating half BCSM (T-Alerting PIC), or ii) an indication of a call-rejected event not specifying user busy is received f
21、rom the terminating half BCSM (T-Alerting PIC). For example, the terminating party may reject the call. The originating half BCSM moves to the O-Called-PartyBusy DP. An indication is received from the RCF of a service feature request by the originating MS. (DP: OMid-Call). Originating party abandons
22、 the call. (DP: O-Abandon) - - O Active Entry Event: - An indication is received from the terminating half BCSM that the call is accepted and answered by the terminating party. (DP: O-Answer). Functions: - Connection established between originating and terminating party. Message accountingkharging d
23、ata may be collected. Call supervision is being provided. Exit Event: - An indication is received from the RCF of a service feature request by the originating MS. (DP: OMid-Call). - A disconnect indication is received from the originating party. (DP: O-Disconnect). - A disconnect indication is recei
24、ved from the terminating DartY via the terminating half BCSM. (DP: O Disconnect). A suspenddktmmxe indication is received from the terminating party via the terminating half BCSM. (DP: O-Suspend). A connection failure occurs. This event causes a transition to the OException PIC. - - O-Suspended Entr
25、y Event: - A suspenddktmmxe indication is received from the terminating party via the terminating half BCSM. (DP: O-Suspend). Functions (the function of this PIC is not currently supported for MS originated calls): - The connection with the originating party is maintained and depending on the incomi
26、ng access connection, appropriate signaling takes place. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 a 21 22 23 24 25 28 27 2% 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 56 56 57 58 58 60 Originating BCSM 7-1 O TINEINIS-771.7 Modifications TINEINIS-826 1 2 3 4
27、5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 a 21 22 23 24 25 28 27 2% 29 30 31 32 33 34 35 36 37 38 39 40 4 42 43 44 45 46 47 48 49 50 51 52 53 54 56 56 57 58 58 60 i) In case that a disconnect indication is received from the terminating half BCSM, this PIC is immediately exited to the O-Disconnect DP w
28、ithout any action. As an option for MS originated calls, the call can be continued for an appropriate period in order to offer follow-on initiated by OMid-Call. ii) If the re-answer indication from the terminating half BCSM is received, the originating and terminating parties are reconnected. iii) O
29、ther features may be required during this PIC (for further study). Exit Event: - Connection to the terminating party is resumed. The originating half BCSM returns to the O-Active PIC. (DP: O-Re-answer). Note: This transition to the O-Active PIC is not applicable for wireless calls. An indication is
30、received from the RCF of a service feature request by the originating MS. (DP: OMid-Call). (DP: O-Disconnect). - - A disconnection indication is received from the originating party. - A disconnection indication is received from the terminating party. (DP: O-Disconnect). An exception event is encount
31、ered. This event causes a transition to the OException PIC. An indication of expiration of the timer waiting for re-answer request is received from the terminating half BCSM. (DP: O-Disconnect). A trigger at O-Mid-Call is not initiated during an appropriate period. (DP: O-Disconnect). - - - O-Except
32、ion Entry Event: - An exception event is encountered as described above for each PIC. Functions: - Default handling of the exception condition is being provided. This includes general actions necessary to ensure no resources remain inappropriately allocated, such as: i) If any relationships exist be
33、tween the SSF and SCF(s), send an error information flow to the SCF(s) closing the relationships and indicating that any outstanding call handling instructions will not run to completion. ii) The SSF/CCF should make use of vendor-specific procedures to ensure release of resources so that radio, trun
34、k, and other resources are made available for new calls. TINEINIS-771.7 Modifications 7-1 1 Originating BCSM TINEINIS-826 Originating BCSM Exit Event: 1 - Default handling of the exception condition by SSFKCF completed. 2 (Transition to ONull PIC) 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 a 21 22
35、23 24 25 28 27 2% 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 56 56 57 58 58 60 7-1 2 TINEINIS-771.7 Modifications TINEINIS-826 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 a 21 22 23 24 25 28 27 2% 29 30 31 32 33 34 35 36 37 38 39 40 4 42 43 44 45 46 47 48 49 50
36、 51 52 53 54 56 56 57 58 58 60 5.2.2.2 Terminatina BCSM (TINEINIS-771, page 7-35) The terminating half of the BCSM corresponds to that portion of the BCSM associated with the terminating party (see Figure 9). The description for each of the PICS in the terminating half of the BCSM are described belo
37、w: r T-AbandonDP . Termination-Attempt-DP Facility-Selectedand-Available DP presentation-fail Ure Present-Call 1 1 1 + T-Alerting T-No-Answer DP call-rejected , T-Answer DP Re-answer DP U T-Disconnect DP 1 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38、. . . . . . . . . . . . . . . . . . No WIN triggers defined for the DP in this standard . . . . . . . . . . . . . . . . Figure 9 Terminating Call Model TINEINIS-771.7 Modifications 7-13 Terminating BCSM TINEINIS-826 T Null Entry Event: - - Default handling of the exception condition by SSFKCF comple
39、ted. Disconnect and clearing of a previous call (DPs: T-Disconnect or T-Abandon) (Transition from T-Exception PIC). Functions: - Clear any resources allocated to the terminating MS. Exit Event: - An indication of incoming call is received from the originating half BCSM. (DP: Termination-Attempt). Th
40、e following exception exit event is applicable to this PIC: Tebandon. i) - The T-Abandon occurs when an indication of call disconnection is received from the originating half BCSM. If the call encounters T-Abandon during PIC processing, the exception event is not visible because there is no correspo
41、nding DP. Authorize-Termination-Attempt Entry Event: - Indication of incoming call received from the originating half BCSM. (DP: Termination-Attempt) Functions: - Authority to route the call to the terminating access (e.g., MS or trunk group) is being verified, e.g., check business group restriction
42、s, restricted incoming access to line, or bearer capability compatibility. Exit Event: - Termination-Attempt-Authorized event. This event occurs when the MSC has verified the authority to terminate the call to the terminating access. (DP: Termination-Attempt-Authorized). The Termination Denied event
43、 occurs when the authority to route these call to the terminating user is denied. (This causes a transition to the T-Exception The T-Abandon event occurs when an indication of clearing is received from the originating half BCSM. (DP: T-Abandon). - PIC). - 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
44、 19 a 21 22 23 24 25 28 27 2% 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 56 56 57 58 58 60 Terminating BCSM 7-14 TINEINIS-771.7 Modifications TINEINIS-826 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 a 21 22 23 24 25 28 27 2% 29 30 31 32 33 34 35 36 37 38 39 40
45、4 42 43 44 45 46 47 48 49 50 51 52 53 54 56 56 57 58 58 60 Select-Facility Entry Event: - Termination-Attempt-Authorized event. This event occurs when the MSC has verified the authority to terminate the call to the terminating access. (DP: Termination-Attempt-Authorized). An SS7 failure occurs causi
46、ng a re-attempt. The SS7 failure in the PresentLCall PIC can be caused by a timer expiry upon sending the first Circuit Reservation Message (CRM) or a continuity check failure. - Functions: - A particular network resource is being selected. It is possible that all resources in the group could be bus
47、y or unavailable. A single resource is considered a group of one. For MS termination, the terminating half BCSM sends an indication to the RACF to select facilities (e.g., page the MS, MS page response, trunk to cell, radio channel within cell) for the call. The MS is assigned to the radio channel.
48、The busyhdle status of the terminating access is determined. i) - - For termination to an MS, the MS is treated as user busy if it is already involved in an existing call and cannot receive another call (e.g., call waiting is not active). ii) For termination to an MS, the MS is treated as network bu
49、sy if no radio channels are available or a routing failure occurs while attempting to complete the call. iii) For termination to an MS, the MS is treated as unavailable if it is not available for call termination, an indication that the MS does not respond to a page is received from the RACF2, or an indication of a failure to assign the MS to a radio channel is received from the RACF. iv) For calls routed out of this SSFKCF, network-determined user busy is the detection of terminating party busy. For calls routed out of this SSFKCF, network busy is when all trunks within the selected
