`

Subject:

Autoplex 1000 CDMA FOA Method of Procedure (MOP) for Fid-12606.5 MSC Supports Missed Call Alert Service and Provides Announcement to A Party, Phase II for Reliance in India.

Technical Memorandum

1.

INTRODUCTION

This document provides the Method of Procedure for feature FID-12606.5 MSC Supports Missed Call Alert Service and Provides Announcement to A Party, Phase II. This feature is targeted for ECP Release R29.0 SU-2 or later.

2.

FEATURE DESCRIPTION

The FID-12606.5 feature is an enhancement of FID-12606.1 MSC Supports Missed Call Alert Service and Provides Announcement to A Party OMSC4MCA feature originally developed for India Reliance customer. In phase I implementation, when A-party calls B-party who has MCA service, if B-party is power-off or doesn't respond the page at Serving MSC, after HLR returns locreq to originating MSC, ALU MSC(Originating MSC) will notify MCA platform with one same reason "Mobile subscriber not reachable". Furthermore, when originating MSC plays announcement to A-party, the announcements for above two cases are the same. In phase II implementation, when HLR returns locreq and indicates the reason that access cannot be given to B-party by including AccessDeniedReason(ADR) parameter, ALU MSC will be capable of differentiating the redirection reason in IAM message to MCA platform, then play appropriate announcement respectively for power-off and "No Page Response" case, thus customer can get a better experience of this MCA service. In case HLR doesn't include ADR parameter in locreq, ALU MSC will still follow phase I implementation behavior. In addition, when A calls B and B is roaming at Serving MSC(ALU MSC), if B cancel the call (by pressing end button), in 12606.1 feature, ALU MSC populates the RedirectionReason parameter in REDREQ message with the cause "No Page Response". In this 12606.5 feature, ALU MSC changes this value to "No Answer". Then originating MSC will follow existing "No Answer" logic to handle this "B cancel call" case. . 3. FEATURE SCENARIOS

3.1 Subscriber Perspective: After feature 12606.5 has been deployed, A-party will hear the different announcements respectively for B-party No Page Response or Power switch off cases if the called party has the MCA service. 3.2 System Perspective The functionality of MCA Service for Reliance has been divided into two phases. For 1st phase, MCA service applies to the cases when only DMH_REDIND parameter is taken by locreq or tranumreq; for 2nd phase, MCA service applies to other cases when both DMH_REDIND and ACCDEN parameters are taken by locreq.

-1-

3.2.1 Early forward to MCS as B-party is Switched Power-off

3.2.2 Early forward to MCS as B-party is No Page Response

-2-

3.2.3 Incall MSC and Serving MSC are different for No Answer

3.2.4. Incall MSC is the same as Serving MSC for No Answer

-3-

3.3 System Support 3.3.1 ALU MSC Values in Original Redirection Reason (ORR) and Redirection Reason (RR) in IAM B-Party switched-off B-Party switched-off B-Party no-page-response (early forward) B-Party no-page-response (early forward) B-Party no-answer B-Party no-answer B-Party no-page-response (late forward) B-Partyno-page-response (late forward) Note: If there is RR before, just copy it into ORR. If not, then populate it as the same as RR. 3.3.2 REL cause values returned from MSC platform to original MSC under corresponding scenarios switched-off (early forward) no-page-response (early forward) no-page-response (late forward) No Answer 20 10/18 10/18 19 The announcement corresponding power-off, provisioned by customer The announcement corresponding NPR, provisioned by customer The announcement corresponding NPR, provisioned by customer The announcement corresponding NA, provisioned by customer to to to to Original Redirection Reason Redirection Reason Original Redirection Reason Redirection Reason Original Redirection Reason Redirection Reason Original Redirection Reason Redirection Reason Not Available Not Available Mobile subscriber reachable Mobile subscriber reachable No Reply No Reply Mobile subscriber reachable Mobile subscriber reachable

not not

not not

3.3.3 RC/V Impacts 3.3.3.1 dplan form provisioning dplan form must set the Call type field to value 58 and DN Modification Type filed to Null
__________________________________________________________________________________ | FLEXENT | | Wireless Dialing Plan (dplan) Screen 1 of 2 | | Networks | | | | Dialing Plan..................*1) ___ | | Pattern Number................*2) ____ (Optional) | | Query by Pattern..............*3) ________________________________ (Optional) | | Pattern........................4) ________________________________ | | Call Type......................5) 58 | | Destination Index..............6) _____ | | Prefix Type....................7) _ | | Number of Digits to Delete.....8) __ | | Re-analyze after deleting......9) n | | DN Modification Type..........10) __ Note: must be NULL (blank) | | Feature/Carrier Code: | | Starting Position........11) _ | | Length...................12) _ | | Termination Address for feature code: | | Starting Position........13) __ | | Cancel Subscriber Validation..14) n | | WPS Emergency Number..........15) n | | | | | | | |________________________________________________________________________________|

-4-

3.3.3.2 cco form provisioning cco form filed Provide NoAnswer instead of NPR when mobile cancels call to y only if OMSC4MCAP2 faf is activated.
__________________________________________________________________________________ | FLEXENT | | Wireless CUSTOMER CONTROLLED OPTIONS (cco) Screen 6 of 24| | Networks | | IS41 TCAP Messages (cont.): | | TCAP Message Timeout Indications Feature Activation............... 74) n | | Report Call Processing Profile Timeout............................ 75) n | | Report TCAP Return Error Messages Received........................ 76) n | | Report TCAP Reject Messages Received.............................. 77) n | | Report TCAP Timeout/TCAP Late Response Messages................... 78) 0 | | TCAP Opcode....................................................... 81) | | [1] __ [3] __ [5] __ [7] __ [9] __ | | [2] __ [4] __ [6] __ [8] __ [10] __ | | Send MSC's E.212 Address to SMSMC................................. 90) n | | Send MSC's E.212 Address to HLR/AC................................ 91) n | | Send MSC's E.212 Address to Other MSC............................. 92) n | | Send MSC's E.212 Address to SCP................................... 93) n | | MEID Validation in compliance with IS928.......................... 94) n | | Send Busy for Pre-Paging Glare Condition.......................... 95) n | | Provide No Mobile Service Announcement for LOCREQ RR No DN........ 96) n | | Provide NoAnswer instead of NPR when mobile cancels call.......... 97) n | | | | | | | | | |________________________________________________________________________________|

Note: For the references, other than FID-8069.0 RC/V has the provisioning in No Page Response, No Answer cases, we need to add Power-off case to support OMSC4MCAP2 feature. 4. The FAF for this feature is ON TAMAP form is provisioned for No Page Response (REL Value = 18) TAMAP form is provisioned for No Answer from User (REL Value = 19) TAMAP form is provisioned for Power-off (REL Value = 20) TONE form is provisioned for No Page Response (REL Value = 18) TONE form is provisioned for No Answer from User (REL Value = 19) TONE form is provisioned for Power-off (REL Value = 20) FEATURE INTERACTIONS

The MSC Supports MCA Service and Provides Announcement to A-party features do not support Inter-DCS Call Delivery. They support Intra-DCS Call Delivery and Inter-MSC Call Delivery. Important! The MSC Supports MCA Service and Provides Announcement to A-party, Phase 2 feature (FID 12606.5) requires that the SHLR can return both the Redirection Indicator and Access Deny Reason parameter with the following value in the IS41 LocationRequest Return Result message: Mobile powered Off Redirection Indicator Value = CFNA Access Deny Reason = INACTIVE (value=20) Mobile No Page Response Redirection Indicator Value = CFNA Access Deny Reason = NPR (value=18) 5. FEATURE REQUIREMENTS

The following resources will be needed to deploy and verify the OMSC4MCAP2 feature.

-5-

5.1 Software Requirements: The FID-12696.5 OMSC4MCAP2 feature requires ECP Release 29.0 SU-2 or later. MSC Supports MCA Service and Provides Announcement to A-party feature (FID 12606.1) should work correctly on site. If A-Party is in an ALU MSC, make sure that FAF 973 MSC Provides Tone/Announcement upon Receiving Backward REL after ACM (TARELAACM) (FID-8069.0) is activated. If both OMSC and IMSC is an ALU MSC, then FAF 977 Mapping REL(18,19) into two different Tone/Announcements (MRELTA) (FID-8069.0) is activated. In order to have total MCA service, this OMSC4MACP2 feature (FID 12606.5) also requires the feature Playing Tone/Announcement Base on ISUP Backward REL Cause Value feature (FID 9216.3) to be activated and provisioned with the announcement for mobile powered-off case.

5.2 Hardware Requirements: The MSC Supports MCA Service and Provides Announcement to A-party features require no hardware beyond the standard hardware in a CDMA network. 5.3 Network Requirements: The MSC Supports MCA Service and Provides Announcement to A-party features only apply to networks with ISUP signaling. TUP, R1 and MFC R2 signalling protocols are excluded. 5.4 Test equipment requirements: UXcptrace/UXprint - tools to capture messages between ECP and 5E-DCS, and ECP and Cells. TCmon tool need to capture IS-41 inter-MSCs messages.

5.5 FAF requirements: The MCA Service FID-12606.5 feature is controlled by faf entry OMSC4MCAP2, slot 1648 1649. Phase II of MSC Supports Missed Call Alert Service and Provides Announcement to A Party (OMSC4MCAP2)

The dependent FAFs are FID-12606.1 feature with its faf entry OMSC4MCA, slot 1622. FID-12606.0 feature with its faf entry ISUPPRR, slot 1572. FID-8069.0 feature with its faf entry TARELAACM, slot 972 and entry MRELTA, slot 976 1623. MSC Supports Missed Call Alert Service and Provides Announcement to A Party (OMSC4MCA) MSC Provides Tone/Announcement upon Receiving Backward REL after ACM (TARELAACM) Mapping REL(18,19) into two different Tone/Announcements (MRELTA)

1573. ISUP Proprietary Redirecting Reason (ISUPPRR) 973. 977.

-6-

8. Test ID Number

FOA TEST EXECUTION Scenarios to verify feature - FID12606.5 MSC Supports Missed Call Alert Service and Provides Announcement to A Party, Phase II Reliance or LCS Alcatel Lucent

Result

FOA Feature Test Verify that MSC plays Power Off announcement to the calling party when cf7964 the called party is power off. Verify that MSC plays No Page Response announcement to the calling cf7965 party when the called party has no page response (early forward). Verify that MSC plays No Page Response announcement to the calling cf7966 party if the called party is power off and ACCDEN is not returned in locreq. Verify that MSC plays No Page Response announcement to the calling cf7967 party if the called party has no page response (early forward) and ACCDEN is not returned in locreq. Verify that MSC plays No Answer announcement to the calling party if cf7968 the called party cancel the call and O-MSC!=S-MSC. Verify that MSC plays No Answer announcement to the calling party if cf7969 the called party cancel the call and O-MSC==S-MSC. With the control field in cco form set to no, verify that MSC shall play cf7970 No Page Response to REL=18 and No Answer to REL=19 announcement respectively to the calling party if the called party cancels the call. Verify that MSC plays Power off announcement to the calling party of cf7971 TWC when the third party is poweroff. Verify that MSC plays No Page Response announcement to the calling cf7972 party of TWC when the third party has no page response. Verify that MSC plays No Answer announcement to the calling party of cf7974 TWC if the called party cancels the call. Feature Regression Test Verify that MSC plays Call Forwarding announcement (1) to the calling cf7976 party if the called party is busy. B-party, with Call Waiting active, is in a stable talk and the third party cf7978 calls B-party. Verify that No Answer announcement is played to the third party if B-party doesnt answer the incoming call. Verify that MSC plays Call Forwarding announcement (1) to the calling cf7980 party if the called party doesnt answer for call forwarding case. Verify that MSC plays Call Forwarding announcement (1) to the calling cf7982 party if the called party has no page response for call forwarding case. With FAF OMSC4MCA on, verify that MSC plays No Page Response cf7985 announcement to the calling party if the called party has no page response (late forward). With FAF OMSC4MCA on, verify that MSC plays No Answer cf7986 announcement to the calling party is the called party doesnt answer. With FAF OMSC4MCA on, verify that MSC plays corresponding cf7987 announcement to the calling party if the called party cancels the call.

-7-

cf7988

With FAF OMSC4MCA on, verify that ECP shall time out the call if ACCDEN is returned in locreq. HLR should be configured to send or not send ACCDEN in locreq for the above test cases ACKNOWLEDGEMENT OF SUCCESSFUL TEST COMPLETION

Note: 9.

These features will be considered to have completed testing once the above tests have been successfully executed, all service impacting issues have been resolved, and all non-service impacting issues have been properly documented with ARs.

__________________________________ Reliance

__________________________________ Lucent Technologies

-8-