generate barcode c# free Basic Intersystem Handoff Functions in C#.NET

Scanner Quick Response Code in C#.NET Basic Intersystem Handoff Functions

9:

Otherwise, notify the serving MSC that its path minimization request is accepted, using the handthird message Wait until the MS is detected on the target radio channel Then complete the path between the radio channel and the other party to the call Notify the old serving MSC that the MS has successfully moved to the new radio channel, and initiate release of the inter-MSC circuit between the tandem MSC and the old serving MSC; the tandem MSC uses the FACREL message for this purpose

As shown in Figure 910, when the target is not the anchor MSC or a tandem MSC, then the target MSC simply executes the target MSC handoff-forward process described in the section entitled Handoff Forward the target MSC is unaware of the path minimization taking place

The ANSI-41 call release functions control the release at the end of a call, of the inter-MSC circuits and internal MSC resources that were used during the handoff process Without these functions, the parties to the call could hang up, but the handoff chain from the anchor MSC to the serving MSC would continue to exist The call release can be initiated either by the anchor MSC; for example, based on a call release indication received from the PSTN, or by the serving MSC, based on information it receives (or does not receive, in the case of lost radio contact) from the mobile station

ANSI-41 call-release processes include the initiating call-release process and the receiving call-release process, illustrated in Figure 913

Downloaded from Digital Engineering Library @ McGraw-Hill (wwwdigitalengineeringlibrarycom) Copyright 2004 The McGraw-Hill Companies All rights reserved Any use is subject to the Terms of Use as given at the website

Part 2:

Figure 913 An example of the call release processes: (1) One of the parties to the call hangs up The anchor MSC releases the unnecessary interMSC circuit towards the serving MSC (2) The tandem MSC requests release of the unnecessary inter-MSC circuit to the serving MSC (3) The serving MSC accepts the release request The facrel message may contain billing information for use by the anchor MSC (4) The interMSC circuit between the tandem MSC and the serving MSC is released and is now ready for other handoff purposes (5) The tandem MSC accepts the release request It forwards any billing

The initiating call release process sends a FACREL message to notify the receiving MSC of call release When the initiator receives the response, it clears its internal resources used for the call (eg, software processes and memory) and marks the inter-MSC circuit idle

Downloaded from Digital Engineering Library @ McGraw-Hill (wwwdigitalengineeringlibrarycom) Copyright 2004 The McGraw-Hill Companies All rights reserved Any use is subject to the Terms of Use as given at the website

9:

If the receiver is either the anchor MSC or the serving MSC, then the receiving call release process is completed by returning a facrel message to the initiating call release process and then marking the inter-MSC circuit idle The receiver may initiate other processes, eg, for features (see 12), to release the radio channel to the MS or the land-line circuit to the PSTN However, these processes are generally beyond the scope of ANSI-41 In the case of a tandem MSC, both types of call-release process are invoked during call release; on one side, the receiving process executes, while the initiating process executes on the other side Also note that the initiating call-release process is nested within the receiving callrelease process at the tandem MSC (see Figure 913) This allows information (eg, the total number of inter-MSC segments involved in the call, which is useful for recording purposes) received by the tandem MSC to be relayed toward the anchor MSC This ANSI-41 function was initially introduced in IS-41-C; prior to Revision C, the operations executed in an asynchronous fashion, as shown in Figure 914

Figure 914 The call release processes prior to IS-41-C Note that steps 4 and 5 are not nested within steps 1 and 2 as in IS-41-C (and later)