Montreal

TR45.2/2001.07.09.___

TITLE:

PN4925changestosupportGSMCallForwarding
SOURCE: JackNasielski QUALCOMMIncorporated Phone:+18586513294 Fax:+18586582113 jackn@qualcomm.com ABSTRACT: GAITproceduresrequiretheIIFtopretendtoforwardcallstoobtaincallforwardingnumbers foranANSI41userroaminginaGSMnetwork.TR45.2shouldconsiderhavingtheHLR sendcallforwardinginstructionswhenitdeliversaprofiletotheIIF. RECOMMENDATIONS: Reviewandaccept.

Notice 2001 QUALCOMM Incorporated. The information contained in this contribution is provided for the sole purpose of promoting discussion within the TIA and is not binding on the contributor. The contributor reserves the right to add to, amend or withdraw the statements contained herein. The contributor grants a free, irrevocable license to the Telecommunications Industry Association (TIA) to incorporate text or other copyrightable material contained in this contribution and any modifications thereof in the creation of a TIA standards publication; to copyright and sell in TIA's name any TIA standards publication even though it may include portions of this contribution; and at TIA's sole discretion to permit others to reproduce in whole or in part such contributions or the resulting TIA standards. This contributor will also be willing to grant licenses under such copyrights to third parties on reasonable, non-discriminatory terms and conditions, if appropriate. The contributor may hold one or more patents or copyrights that cover information contained in this contribution. A license will be made available to applicants under reasonable terms and conditions that are demonstrably free of any unfair discrimination. Nothing contained herein shall be construed as conferring by implication, estoppel, or otherwise any license or right under any patent, whether or not the use of information herein necessarily employs an invention of any existing or later issued patent, or copyright. The contributor reserves the right to use all material submitted in this contribution for their own purposes, including republication and distribution to others.

Montreal

TR45.2/2001.07.09.___

Background
ANSI-41 systems support call forwarding no answer and call forwarding busy (after the call is extended to the serving system) from the originating system using REDREQ/TRANUMREQ. These calls may also be forwarded from the serving system using TRANUMREQ. GSM systems typically provide CFB and CFNA from the serving system, using information received in the subscriber data from the HLR. GSM systems may also provide a conditional call forwarding service similar to ANSI-41. This is optimal routeing of late call forwarding., see GSM 03.79 or 3GPP 23.079. See also GSM 02.82 (call forwarding) and GSM 09.02 (MAP.)

GAIT method
GAIT call flows show the IIF using TRANUMREQ to obtain CFB and CFNA numbers for a GSM foreign mode user. These numbers are then provided to the GSM serving system (VMSC.)
ANSI-41 Home System HLR IIF ANSI-41 GSM GSM Serving System VMSC 2 Subscriber MS

Normal registration process TRANUMREQ tranumreq TRANUMREQ tranumreq ISD isd [TCAP End]

b c d e f g h

Figure51: Obtainingforwardto numbers

a. b. The subscriber registers on a GSM serving system using the normal registration signalling process. If the subscribers ANSI-41 profile indicates that CFB is authorized and active, and the IIF determines that it does may not have the current CFB forward-to number, then the IIF sends a TRANUMREQ message to the HLR requesting the CFB forward-to number. The HLR responds with the CFB forward-to number in the tranumreq message. If the subscribers ANSI-41 profile indicates that CFNA is authorized and active, and the IIF determines that it does may not have the current CFNA forward-to number, then the IIF sends a TRANUMREQ message to the HLR requesting the CFNA forward-to number. The HLR responds with the CFNA forward-to number in the tranumreq message.

c. d.

e.

f-h. If the CFB forward-to number or CFNA forward-to number, or both numbers, do not correspond with the numbers previously provided to the GSM serving system, then the IIF sends the modified information to the GSM serving system

Montreal

TR45.2/2001.07.09.___

using the InsertSubscriberData operation. The CFNA forward-to number shall be populated as both the CFNRc and CFNRy forward-to numbers.

TransferToNumberRequestReturnResultto Insert SubscriberData Request Mapping of parameters value This table represents how the IIF shall map the value of the parameter it has received to populate the fields of the message it shall transmit. Table1: TransferToNumberRequestReturnResultto Insert SubscriberDataRequestparametermapping TransferToNumberRequestReturnResult Digits (Destination) or DestinationDigits parameter within TerminationList (See Note 1) This is the forwarded-to-number. Format is Type of Digits (1 octet), Nature of Number (1 octet), Numbering Plan (4 bits), Encoding (4 bits), Number of Digits (1 octet), and actual digits in BCD. NoAnswerTime Status M Insert SubscriberDataRequest Forwarding Information List Forwarded-to-Number (See Note 2) E.164 format Status C

Forwarding Information List No Reply Condition time

Note 1: When TerminationList parameter is present, the Digits(Destination) parameter of the TransferToNumberRequest RETURN RESULT is ignored. Note 2: There may be up to three forwarded-to number parameters with the Insert Subscriber Data Request message mapped from TransferToNumberRequest information: one for Call Forwarding Busy, one for Call Forwarding No Reply (mapped from CFNA results), and another for Call Forwarding Not Reachable (also mapped from CFNA results).

GAIT Optimal Routing - Success Case

Scenario: ANSI-41 Subscriber A makes a call origination attempt at ANSI-41 MSC-A to ANSI-41 Subscriber B roaming and registered in a GSM network at MSC-B. Subscriber B has call forwarding set to an address at MSC-C. Subscriber B is not IMSI detached.

Montreal

TR45.2/2001.07.09.___

ANSI-41 (MSC-A) a b c d e f g h i j k l m n o p
tranumreq redreq Locreq [TLDN] Call Origination LOCREQ

ANSI-41 (Bs HLR)

IIF

GSM (VLR/MSC-B)

(MSC-C) a b

ROUTEREQ Provide Roaming Number[GMSC#,CR#] Provide Roaming NumberAck [MSRN] Routereq [TLDN]

c d e f g h i j k l m

Establish Connection Attempt Resume Call Handling [CR#,reason] REDREQ [REDREASON] TRANUMREQ [REDREASON]

Resume Call HandlingAck Connection Release Call Forward Setup

n o p

Figure60: OptimalRoutingwithLate Call Forwarding(GSMForeignMode)SuccessCase a. b. c. ANSI-41 MSC-A receives a call origination stimulus from Subscriber A. The ANSI-41 MSC-A sends an ANSI-41-Location Request message for routing information to Subscriber B's ANSI-41 HLR with the MSCID address of the originating MSC (ANSI-41 MSC-A). Subscriber B's ANSI-41 HLR determines that Subscriber B is roaming at MSC-B and sends a ANSI-41-Routing Request message number with the MSCID address of the ANSI-41 MSC-A received in step b. to an IIF acting on behalf of MSC-B to get a roaming number. The IIF relays this request to GSM MSC/VLR-B by sending a GSM-Provide Roaming Number message. The IIF generates two parameters: the Call Reference number (for the VLR/MSC-B to use in the GSM-RCH) and the GMSC address set to the IIF address, to indicate that the IIF is capable of supporting optimal routing for late call forwarding. GSM MSC/VLR-B acknowledges the GSM - Provide Roaming Number message with the Mobile Subscriber Roaming Number (MSRN). Upon receipt of this message, the IIF sends the TLDN to Subscriber B's ANSI-41 HLR in the ANSI-41-Routing Request message. Subscriber B's ANSI-41 HLR relays this information to ANSI-41 MSC-A via the ANSI-41-Location Request (Acknowledgment) message. ANSI-41 MSC starts a call setup procedure using TLDN (MSRN) as Subscriber B's called address at GSM MSC/VLRB. The incoming call can not be terminated at GSM MSC/VLR-B because of reasons such as Busy, Not Reachable, or No Reply. Since the GMSC address and the Call Reference Number parameters were present in the GSM-Provide Roaming Number message the GSM MSC-B sends a GSM-Resume Call Handling message to the IIF with the received Call

d.

e. f. g. h.

i.

Montreal

TR45.2/2001.07.09.___

Reference number and all necessary information required for call forwarding. If optimal routing is not supported, the call is forwarded by GSM MSC-B using the forwarding information available. j. When optimal routing is supported and the IIF receives the GSM-Resume Call Handling message, the IIF sends an ANSI-41-Redirecion Request message with the Redirection Reason to the ANSI-41 MSC-A supporting subscriber A's call origination attempt. The ANSI-41 MSC-A passes this Redirection Reason to the Subscriber B's ANSI-41 HLR in the ANSI-41-Transfer To Number message to get call forwarding number information. Based on the Redirection Reason, the ANSI-41 HLR returns the corresponding forwarded-to number to ANSI-41 MSC/VLR-A.

k. l.

m. If ANSI-41 MSC-A received forwarded-to number from ANSI-41 HLR, it sends ANSI-41-Redirection Request (Acknowledgment) message to the IIF. In case of an error, ANSI-41 MSC-A rejects the redirection request. The IIF then returns a GSM-Resume Call Handling Error message to GSM MSC-B, which then attempts to forward the call to MSC-C using the forwarding information available. n. o. p. Upon receiving the ANSI-41-Redirection Request (Acknowledgment) in step m., the IIF sends a GSM-Resume Call Handling Acknowledgment message to GSM MSC-B. The ANSI-41 MSC-A releases all circuit-associated resources specific to GSM MSC/VLR-B. The ANSI-41 MSC-A starts a call setup procedure using the call forwarded-to number as Subscriber B's address at MSC-C.

Proposal
The IIF may be simplified and signaling traffic reduced if the ANSI-41 HLR provides CFB and CFNA numbers along with the profile. New procedures may be defined to send this optional information to the IIF. The HLR could send E.164 numbers for CFB and CFNA in regnot, qualreq, and QUALDIR. The IIF would then map these numbers to the GSM Forwarding information list in the INSERT SUBSCRIBER DATA operation. The CFB number maps to GSM Call Forwarding on Mobile Subscriber Busy. The CFNA number maps to both GSM Call Forwarding on Mobile Subscriber Not Reachable and Call Forwarding on No Reply. The HLR could also send a NoAnswerTime parameter that the IIF would map to the No reply condition timer in the Forwarding information list (5 to 30 seconds, in steps of 5 seconds.) Note that GAIT also supports interworking with the GSM optimal routing feature, but not all carriers and infrastructure will support this feature. Support for call forwarding from the GSM serving system is required.

Recommendation
Consider the proposal. If supported, Qualcomm will develop detailed text for PN-4925.