Abstract:
Apparatus and method for management of optimal voicemail deposit to the voicemail of a currently roaming mobile telephony user during late call forwarding, is located at the user&#39;s home network and includes a disconnection unit for disconnecting an international link upon detection of late call forwarding; a triggering unit that ensures that a trigger signal is available for triggering the passing of control of the call to allow direct forwarding of the caller to the voicemail; and a direct forwarding unit that receives the control and carries out the forwarding. Generally the roaming user only generates a single trigger, and this causes difficulties if multiple services need triggering for the same call, such as a prepaid unit and the optimal voicemail deposit. The disclosure teaches methods which when used in combination provide a system that can operate at the home network irrespective of the configuration of the roaming network.

Description:
RELATIONSHIP TO EXISTING APPLICATIONS  
       [0001]     This application claims the benefit of U.S. Provisional Patent Applications Nos. 60/754,198, filed on Dec. 28, 2005, 60/755,080 filed on Jan. 3, 2006, 60/776,696 filed on Feb. 27, 2006 and 60/788,071 filed on Apr. 3, 2006. The contents of the above applications are hereby incorporated by reference. 
     
    
     FIELD AND BACKGROUND OF THE INVENTION  
       [0002]     The present invention relates to an optimal voicemail deposit system for a roaming user whose voicemail is on a home network, which is different from the network where he is currently roaming, and, more particularly, but not exclusively to an optimal voicemail deposit system which is suitable for both prepaid and postpaid users.  
         [0003]     Mobile subscribers usually set call forwarding to the voicemail, so that if they cannot answer a call for whatever reason, then the caller has an opportunity to leave them a message. Call forwarding may be divided into two categories, early call forwarding and late call forwarding. Late call forwarding is performed conditionally, due to the subscriber&#39;s inability to answer a call routed to the handset. Conversely, early call forwarding is performed without the network attempting to route the call to the handset. This happens when the handset is shut off or when the subscriber requests unconditional forwarding of all incoming calls. Late Call Forwarding for busy/no-answer/not-reachable conditions can be configured to any number and is usually configured to the subscriber&#39;s voice mailbox.  
         [0004]     Mobile subscribers roaming abroad want to stay in touch with work and home, and to continue to use their mobile services, such as voicemail. Naturally, they also want the same user experience as that in the home network—such as seamless caller access to mailbox, caller-ID indication upon retrieval and direct forwarding of calls to their voice mailbox or to any of their pre-set forwarding destinations. It goes without saying that they expect the same user experience for their callers.  
         [0005]     However, when a roamer cannot take a call, he may either be unavailable, busy or simply may choose not to answer—the visited network routes the call back to the home voicemail system, which is the default setting for most roamers. As the originating call was most probably made in the home network, the rerouting in turn causes inefficient international tromboning, that is to say the call is connected from the home country to the roaming country and back to the home country. The result is that the called party has to pay for two International legs, resulting in a negative impact on the caller and in subscriber experience and forces roamers to pay international tariffs for voicemail deposits.  
         [0006]      FIG. 1  illustrates the existing non-optimal routing late call forwarding while roaming. The figure shows a home network  10  and a visited network  12 . A call originates at the home network and is forwarded to the roaming user at the visited network. The user at the visited network does not answer the call, and the call is routed from the visited network to the user&#39;s voicemail at voicemail server  14  at the home network  10 . At this point two international connections  16  and  18  simultaneously exist for the same call.  
       The Result: Reduced Service and Use  
       [0007]     Higher subscriber costs—The high cost to the user caused by the international tromboning of voicemail causes many roamers to disable voicemail forwarding while roaming. Some home networks disable call forwarding for their outbound roaming subscribers, in order to avoid subscriber frustration.  
         [0008]     Complicated use—Due to the filtering of signaling data by switch vendors and by some international networks, the original dialed number may not be transferred to the home network&#39;s voicemail system via these doubled International links. This forces the caller to re-enter the original dialed number. For the same reason, Caller ID is not available to the voicemail system and the phone number of the caller is not provided during message retrieval, resulting in a voicemail message whose origin cannot be traced if not self-explanatory from the message itself.  
         [0009]     Higher operator costs—Roaming subscribers, unaware of the high cost of forwarding calls, may be surprised and angered when receiving their monthly bills. The immediate response is usually to call Customer Care to complain and inquire about the charges. In addition to customer dissatisfaction, this in turn engages operator&#39;s manpower and communications resources.  
         [0010]     Loss of potential revenue—Disabling call forwarding to voicemail while roaming—either by the subscriber or by the operator—means loss of potential revenue that otherwise would have come from:  
         [0011]     Originator call completion  
         [0012]     Subscriber voicemail retrieval  
         [0013]     Subscriber call back  
         [0014]     There is thus a widely recognized need for, and it would be highly advantageous to have, a late call forwarding system for roaming users which is devoid of the above limitations.  
       SUMMARY OF THE INVENTION  
       [0015]     According to one aspect of the present invention there is provided apparatus for management of optimal voicemail deposit to the voicemail of currently roaming mobile telephony user during late call forwarding, the apparatus being located at the home network of said user, the apparatus comprising:  
         [0016]     a triggering unit configured to set a trigger for a mobile terminated call directed to a subscriber of the home network roaming in a visited network, such that when the call is disconnected, the control of the call is handed over for direct forwarding, said setting being irrespective of triggering being required for other purposes;  
         [0017]     a disconnection unit for disconnecting an international link in a mobile terminated call following subjecting of said call to a late call forwarding;  
         [0018]     a direct forwarding unit for forwarding a caller to said voicemail, thereby providing an optimal voicemail deposit.  
         [0019]     According to a second aspect of the present invention there is provided a method for management of optimal voicemail deposit to the voicemail of currently roaming mobile telephony user during late call forwarding, the method being carried out at the home network of said user, the method comprising:  
         [0020]     providing a trigger signal for passing control of a late forwarded call to allow direct forwarding to a respective voicemail;  
         [0021]     disconnecting an international link associated with said call; and  
         [0022]     using said trigger making said direct forwarding to said voicemail.  
         [0023]     Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The materials, methods, and examples provided herein are illustrative only and not intended to be limiting.  
         [0024]     Implementation of the method and system of the present invention involves performing or completing certain selected tasks or steps manually, automatically, or a combination thereof. Moreover, according to actual instrumentation and equipment of preferred embodiments of the method and system of the present invention, several selected steps could be implemented by hardware or by software on any operating system of any firmware or a combination thereof. For example, as hardware, selected steps of the invention could be implemented as a chip or a circuit. As software, selected steps of the invention could be implemented as a plurality of software instructions being executed by a computer using any suitable operating system. In any case, selected steps of the method and system of the invention could be described as being performed by a data processor, such as a computing platform for executing a plurality of instructions. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0025]     The invention is herein described, by way of example only, with reference to the accompanying drawings. With specific reference now to the drawings in detail, it is stressed that the particulars shown are by way of example and for purposes of illustrative discussion of the preferred embodiments of the present invention only, and are presented in order to provide what is believed to be the most useful and readily understood description of the principles and conceptual aspects of the invention. In this regard, no attempt is made to show structural details of the invention in more detail than is necessary for a fundamental understanding of the invention, the description taken with the drawings making apparent to those skilled in the art how the several forms of the invention may be embodied in practice.  
         [0026]     In the drawings:  
         [0027]      FIG. 1  is a simplified diagram showing existing voicemail deposit architectures including a double International leg or tromboning.  
         [0028]      FIG. 2  is a simplified diagram showing a system architecture to which the present embodiments may be applied.  
         [0029]      FIG. 3  is a simplified flow diagram illustrating the process of voicemail deposit according to a first preferred embodiment of the present invention.  
         [0030]      FIG. 4  is a simplified service flow chart showing optimal voicemail deposit for a postpaid user, according to a preferred embodiment of the present invention based on double triggering.  
         [0031]      FIG. 5  is a simplified service flow chart showing optimal voicemail deposit for a prepaid user in a Camel enabled roaming network, according to the double triggering embodiment of  FIG. 4 .  
         [0032]      FIG. 6  is a simplified diagram showing double triggering for a prepaid roamer in a non-Camel enabled network, according to the embodiment of  FIG. 4 .  
         [0033]      FIG. 7  illustrates the service flow for a prepaid user in a Camel enabled roaming network according to a preferred embodiment of the present invention based on an IN service broker.  
         [0034]      FIG. 8  illustrates the service flow for a prepaid user in a non-Camel enabled network according to the IN service broker embodiment of  FIG. 7 .  
         [0035]      FIG. 9  is a simplified service flow diagram for a postpaid user in either a Camel enabled or non-enabled visited network, according to a preferred embodiment of the present invention in which call status triggers are used.  
         [0036]      FIG. 10  is a simplified service flow diagram for a prepaid user in a Camel enabled visited network, according to the embodiment of  FIG. 9  in which call status triggers are used.  
         [0037]      FIG. 11  is a simplified flow diagram for a postpaid roaming user in a non-camel enabled visited network, according to a preferred embodiment of the present invention that uses a SOR emulator based on probes, specifically an SS7 probe.  
         [0038]      FIG. 12  is postpaid roaming user in a non-camel enabled visited network, according to the embodiment of  FIG. 11  that uses a SOR emulator but this time based specifically on an SCCP relay.  
     
    
     DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0039]     The present embodiments comprise apparatus and methods for alerting the home network about call forwarding involving a roamer so that the home network can forward the caller directly to the voicemail and disconnect the International link. In this way not only is tromboning avoided, but also the connection to the voicemail works better because the caller ID is correctly forwarded to the voicemail.  
         [0040]     The GSM standard includes features to avoid International tromboning but these have never effectively been implemented. The present inventors, in one embodiment, instead of relying on the eventual implementation of these features, make use of the roaming trigger that the home network in fact does issue. This raises the problem that the roaming trigger may be required for other purposes, in particular for alerting the system in the case of a pre-paid subscriber to ensure that his prepayment covers the roaming interaction. The present inventors have inter alia solved the problem in such a way that call forwarding to the voicemail is carried out regardless of other requirements of the roaming trigger. As a result there is a call forwarding system that is equally applicable to pre-paid and post-paid users.  
         [0041]     In an alternative embodiment the present inventors have found a way of taking advantage of the partial adoption of the features in the GSM standard to allow a given network that at least partly uses the features to view other networks as if they use the features.  
         [0042]     The above embodiments are jointly or severally incorporated into an Optimal Voicemail Deposit (OVMD) service, in order to overcome the above-described problem of international tromboning that is caused by incomplete signaling when a called party traveling abroad cannot answer a call and the call is diverted to the home VMS or to another pre-set forwarding destination.  
         [0043]     Optimal voicemail deposit is intended to improve the caller&#39;s experience and to significantly reduce the cost of voicemail deposits billed to the roaming subscriber, thereby allowing mobile operators to regain previously lost revenue. The OVMD system is supported by gateways provided at the networks of the mobile operators to support roaming users, and the gateways provide a comprehensive package of connectivity services to their outbound roaming subscribers. The roaming gateways are alternately referred to herein as Intelligates.  
         [0000]     The Optimal Voicemail Deposit service provides the following benefits:  
         [0000]    
       
         
           
              Direct forwarding—The caller receives direct in-network access to the forwarded destination, whatever number is dialed—mobile or fixed—or to the called party&#39;s voice mailbox. No international calls are implicated.  
              Home-like user experience—When forwarding the call to the voicemail, the application makes the original called number and calling party&#39;s number available to the voicemail system. This in turn ensures a positive user experience, both for the subscriber and the caller.  
              Increased call completion rate—Without international call rates, late call forwarding, while roaming, helps callers complete more calls and encourages subscribers to activate their voicemail for message deposits, thereby further increasing the call completion rate. This in turn increases the number of voicemail retrieval calls and callbacks.  
              No dependencies on visited network—various of the embodiments presented herein do not require any coordination or interoperability with the visited networks. A single solution at the home network suits all visited networks.  
           
         
       
     
         [0048]     The principles and operation of an apparatus and method according to the present invention may be better understood with reference to the drawings and accompanying description.  
         [0049]     Before explaining at least one embodiment of the invention in detail, it is to be understood that the invention is not limited in its application to the details of construction and the arrangement of the components set forth in the following description or illustrated in the drawings. The invention is capable of other embodiments or of being practiced or carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein is for the purpose of description and should not be regarded as limiting.  
         [0050]     Reference is now made to  FIG. 2 , which illustrates the generalized architecture of an optimal voicemail deposit system according to a first preferred embodiment of the present invention. A home network  20  includes a roaming gateway or Intelligate  22 . Gateway Mobile Switching Centre (GMSC)  24  provides an edge function within the home cellular network, and terminates the PSTN (Public Switched Telephone Network) signalling and traffic formats and converts this to protocols employed in mobile networks. For mobile terminated calls, it interacts with Home Location Register  26  to obtain routing information that is to say to locate the mobile telephone required and communicate with it. In the case of International roaming, the HLR is being used to find the roaming network.  
         [0051]     The Optimal Voicemail Deposit system can be integrated with the operator&#39;s network via the GMSC  24  in one of the following two ways, essentially two signaling methods: 
        Intelligent Network (IN), including CAMEL     ISUP (Service Node)        
 
         [0054]     Based on these two alternative signaling methods, the present embodiments provide a generic technical solution for the service. The final delivered solution to the operator however, is preferably adjusted to the specific network configuration and parameters, such as: network size and topology, traffic volume, INAP vendor&#39;s variant, CAMEL version—if relevant and to the operator&#39;s preferences. All these parameters are usually discussed prior to specifying the final technical solution.  
         [0055]     Reference is now made to  FIG. 3  which is a simplified flow chart showing OVMD in action. A call is placed and not answered. The solutions discussed herein include two stages. A first stage involves disconnecting the trombone and the second involves obtaining a trigger. In the following are provided four methods for obtaining a trigger, and then three methods for disconnecting the trombone. The issue of disconnecting the trombone and obtaining the trigger may be considered separately. The disconnecting of the trombone can be either by capturing the call with the VM deposit number, or by operating in association with the FTN (Forward-To-Number), as described in greater detail below.  
         [0056]     A first solution for obtaining a trigger is simply to provide a double trigger. The DP12 trigger is the trigger provided by the IN for an MT (Mobile Terminated) call. The DP12 trigger is used by the prepaid system if the MT is directed to a roaming subscriber. Double triggering is possible at the local MSC based on the ability of the switch at the home network to send the trigger twice, which is to two different addresses. The idea is that one address used is the prepaid feature or any other feature needed by the specific user, and the second address is the anti-tromboning feature which is described in greater detail elsewhere herein. The anti-tromboning feature once triggered is able to cut the International links and forward the caller directly to the voicemail as necessary.  
         [0057]     In fact, the double trigger may be intended as part of the CAMEL system for inbound roamers. The present system for the first time utilizes the trigger for outbound roamers. However, the double trigger solution does not have to be CAMEL. The switch need only have Intelligent Network (IN), with double triggering support. Double triggering support includes a prefix that can be added after the first trigger, in order to process the second trigger.  
         [0058]     A difficulty with the double trigger solution is that it is not widely available, in that many switches are unable to produce a roaming trigger that can be directed to two addresses. A comprehensive solution utilizes the double trigger where available but requires other solutions for other cases.  
         [0059]     A second solution uses a software or firmware entity referred to as a broker. A broker can be provided as part of the Intelligent Network IN system for cellular networks. This is referred to hereinbelow as the IN service broker. A regular trigger is used, and the broker is provided as the single address by the trigger. The broker receives the trigger and looks at the service profile for the associated callee. Based on the callee the broker then decides what to do with the trigger. If the user is a prepaid user then the broker sends its own trigger to the prepaid system, and the broker retains the ability to trigger the anti-tromboning and voicemail deposit.  
         [0060]     The caller profile can be used to allow a range of features for the roaming user, in that the profile allows the broker to make a decision which is as simple or complex as necessary to trigger any combination of services for the roaming user. A prepaid user would automatically have a trigger provided to the prepaid system but users in general could have triggers provided to any IN services relevant for the current call.  
         [0061]     A third solution makes use of call status triggers. A set of what may be termed late call triggers, because they occur after the call has begun, may be used. Such triggers include the “no answer” notification, the “busy” notification etc. The call goes to the prepaid system in the normal way using the roaming trigger. Likewise the call is forwarded to the callee, who does not answer etc. The no-answer status returns to the home network, which can now be used to trigger the anti-tromboning system, and direct it to disconnect the International branch of the call at the gateway, and forward the caller directly to the voicemail.  
         [0062]     A busy notification may likewise be used as a trigger for the anti-tromboning feature. The busy trigger also reaches the home network.  
         [0063]     In either case, on receipt of the notification, the system has to determine if there is a voicemail to forward the call to. The voicemail is defined by a forward to number (FTN). In fact it should be noted that users on many systems are free to define other numbers to which their calls can be forwarded, not just voicemail, and the present embodiments encompass forwarding of calls to these numbers as well. The FTN is obtained from the home location register (HLR) of the callee. If there is no FTN defined then the call is disconnected. It is noted that a call being forwarded to a voicemail includes a notification in its header that it is for voicemail. Thus the very presence of a call with a voicemail deposit notification in its header may be used to trigger the anti-tromboning feature. As above, once triggered, the anti-tromboning feature may disconnect the International call and subsequently allow connection of the caller to the callee&#39;s voicemail. The anti-tromboning feature is responsible for the trombone disconnect, but it is noted that the forwarding to the voicemail is done by another component, the component that receives the trigger, checks the FTN and then decides if or where to route the call.  
         [0064]     In general, when a call is forwarded back to the home network with a voicemail notification, and disconnected by the anti-tromboning feature, then a TDP13/14 trigger at the MSC enquires what to do with the call. As long as the TDP13 is answered within a certain time delay then the call can be handled. If not then the call is cut off. It is added that some roaming network switches do not release the call on time. A workaround can be provided by playing a ring back tone from the Intelligate. The ring back tone operates to prevent the home MSC from disconnecting the call until the release trigger is received from the visited network.  
         [0065]     Summarizing the 3 rd  method, the call is routed to the mobile handset. If the handset is busy or does not answer, then the call is forwarded to the FTN destination, which is typically a voicemail. Then the International leg of the call that reaches the voicemail is disconnected. At that point, the TDP 13/14 trigger arrives at the roaming gateway or Intelligate, asking what to do. As mentioned above, there are two main steps involved, firstly disconnecting the trombone, and secondly obtaining the trigger.  
         [0066]     A fourth method is based on Standard Optimal Routing (SOR), otherwise referred to as standard-based late call forwarding. SOR is the optimal routing system defined in the GSM standard that was always intended to avoid the existence of tromboning. Standard optimal routing is supported by certain International switches, particular those provided by Ericsson. Such optimal routing typically only works if the switches at both networks have SOR support and this is rare.  
         [0067]     The ETSI/3GPP standard 23.079, the contents of which are hereby incorporated by reference, provides the description for the optimal routing of late call forwarding, using the Support of Optimal Routing (SOR) feature. This standard solution requires interoperability between the home network or HPMN and the visited network or VPMN, in order to provide the service. The present solution eliminates the need for such cooperation between the home network and each one of the visited networks. Such cooperation has not happened so far, due to the complexity of upgrading the network components to support this feature, and the requirement of having agreements to be signed with all visited networks or a portion of them.  
         [0068]     The present solution comprises placing apparatus at the home network which emulates SOR functions. If the roaming network has SOR then the roaming network simply produces the necessary signals to provide optimal routing and allows the home network to respond to these signals. The apparatus is not required to do anything when the roaming network has SOR. If, on the other hand, the roamer is in a network without SOR support, then the apparatus sends to the home network signals that simulate the roamer having SOR. In essence the apparatus serves as a home network based SOR emulator, for providing the SOR signaling that the roaming network should be providing but does not. Upon receipt of this signaling the home network is able to connect the caller directly to the voicemail. Equipped with such apparatus the home network sees all roaming networks as having SOR support.  
         [0069]     It is noted that in the above solution, the home network has SOR capability. However for the present solution the SOR feature need only be activated in the HLR and the GMSC. SOR does not need to be activated in all of the MSCs, as it would be in the general SOR solution. The method is described in greater detail hereinbelow, where it is explained how probes can be used by the emulator for it to obtain the information it needs in order to carry out the emulation.  
         [0070]     The solution relies on the Intelligate, with the following interfaces to the HPMN&#39;s network, as will be explained in greater detail below:  
         [0071]     SCCP relay (PRN &amp; PRN ACK messages) or an SS7 probe  
         [0072]     INAP/ISUP  
         [0073]     There now follows a description of three methods for disconnecting the trombone.  
         [0074]     The first way to disconnect the trombone is to capture the call according to the voicemail deposit number. The second is simply to cancel the FTN, either through the HLR, or through the roaming gateway, by sending a new ISD profile to the VLR. An ISD profile is the subscriber profile stored in the HLR and downloaded to the current VLR, using the MAP Insert Subscriber Data message.  
         [0075]     Canceling the FTN preferably causes the first international leg to disconnect without creating the tromboning in the first place.  
         [0076]     A third way to disconnect the trombone comprises setting a CAMEL trigger to the subscriber, at the roaming VLR. In that case, the roaming gateway or Intelligate receives a trigger before setting the second leg to the voicemail or the FTN. In this case a trigger is obtained before the disconnect occurs, but then the TDP 13/14 trigger is obtained later on, after the disconnect. In all the above three methods, the TDP 13/14 trigger is received after the trombone disconnects. In fact, the same applies to the other methods explained herein including the TDP12, the IN service broker, and the SOR, the latter of which is explained below.  
         [0077]     In the following is a description of the two signaling options referred to above, IN and ISUP.  
         [0078]     Intelligent Network (IN)—Including CAMEL  
         [0079]     Using the IN architecture, the IntelliGate  22  controls mobile terminated calls delivered to outbound roaming subscribers. The IN solution suits networks that are already IN or CAMEL ready, that is IN or Camel compatible, and/or networks that experience relatively high outbound roaming traffic.  
         [0080]     Using INAP or CAP protocols, call control is performed using a combination of Trigger Detection Points and Event Detection points.  
         [0081]     ISUP—Including Loop Around  
         [0082]     In particular cases—such as: a non-IN network environment, cases where there is relatively low outbound roaming traffic, or, when specifically requested by the operator, call control is performed using ISUP signaling—In this case all MT roaming calls are physically routed to the Intelligate platform. The Loop Around method is a much better method, where only the ISUP signaling is routed to the Intelligate, while the physical voice part actually stays on the MSC. This is achieved by connecting the E1/T1 lines back to the MSC, creating a physical loop. This method avoids the transfer of the huge amount of voice traffic to the Intelligate, by having a “semi IN” solution.  
         [0000]     GSM-MAP  
         [0083]     Using GSM-MAP, the IntelliGate automatically deactivates the forwarding settings of roaming subscribers in the visited network, when registering to a foreign network, as well as when returning to the operator&#39;s network. It should be noted that in some networks the deactivation of the FTN for a roamer is performed by the network. The IntelliGate can use this network feature and provide a complete service  
         [0000]     Probe Interface  
         [0084]     Referring again to  FIG. 2 , Intelligate  22  typically comprises an SS7 Mobility Probe  28  to monitor International signaling links. Thus, the IntelliGate is connected to the operator&#39;s international SCCP signaling links in a completely passive mode.  
         [0085]     The probe interface obtains for the OVMD from the signaling links the relevant subscriber information, such as the MSISDN and the forwarding-to-number (FTN) referred to above.  
         [0086]     It is noted that in many networks, the OVMD service can be implemented without using a probe and probe interface to monitor the signaling links.  
         [0000]     Provisioning Interface  
         [0087]     The application provides a provisioning interface  30  to enable the management of application parameters and subscriber lists. For example OVMD may be a restricted service, available only to certain subscribers, say those who have complained in the past about tromboning, and the operator may allow the provisioning of IMSI/MSISDN numbers of those subscribers who are entitled to use the Optimal Voicemail Deposit service (white list).  
         [0000]     Service Structure and Processes  
         [0088]     Considering  FIG. 3  again and the service comprises the two separate logical parts of disconnecting the trombone and receiving a trigger which enables the local routing to a voicemail (or another preferred FTN) or call disconnect  
         [0089]     The different embodiments discussed herein may be mixed and matched in whatever way is most appropriate to provide a highly customizable solution to support different networks and constellations of networks in terms of diverting calls to voicemail as well as in releasing the forwarded trombone.  
         [0000]     Methods for Releasing the Trombone  
         [0090]     Above was discussed in general terms the issue of releasing the trombone. One of the alternatives for releasing the trombone is explicitly to release the returning leg of the trombone.  
         [0091]     A set of methods for releasing the returning leg of the trombone waits until the forwarded call returns from the visited network and only then releases the call, thus causing the release of the trombone.  
         [0000]     ISUP/INAP Trigger at GMSC to IntelliGate  
         [0092]     In one method, a routing rule/IN trigger is defined in the GMSC  24  for all incoming calls from abroad with a specific DN value. The DN value would be a pointer to the Voicemail Deposit number, and the trigger is handed to the IntelliGate  22 . The Intelligate  22  then releases the call.  
         [0000]     By GMSC  
         [0093]     Another method is similar to the above. However, instead of triggering the IntelliGate  22  the GMSC  24  itself has the capability of releasing those calls. To provide the GMSC with such an ability, a special patch may need to be installed in the GMSC.  
         [0000]     SCCP Relay  
         [0094]     Yet a further method intercepts CAMEL O-CSI triggers coming from the visited network before the trombone occurs and releases the mobile-forwarded calls, thus causing the trombone to be released. It will be appreciated that such a method requires the visited network to produce such triggers.  
         [0000]     Suppression of FTN While Roaming.  
         [0095]     One method to prevent tromboning is to suppress the FTN and such suppression may be carried out in a number of ways including the following.  
         [0000]     By HLR  
         [0096]     The FTN may be suppressed by the HLR  26 . A feature in the HLR that causes the HLR not to send the FTNs is the MAP_ISD message that is used when the subscriber is roaming.  
         [0000]     By Probe &amp; Additional ISD  
         [0097]     Another method for suppressing the FTN relies on the IntelliGate  22  monitoring MAP_ISD messages sent by the HLR  26 . After each MAP_ISD message is sent by the HLR  26  to the VLR at which the roaming user is located, the IntelliGate  22  issues a consecutive MAP_ISD message in which the FTN is marked as disabled. Such a disablement prevents the VLR, which is at the visited network, from forwarding unanswered calls. Thus the trombone is never formed in the first place.  
         [0000]     Maximum Redirection Counter  
         [0098]     A further method is applicable when the IntelliGate  22  itself handles mobile terminated (MT) calls before they leave the home network  20 , also referred to as the HPMN. The method involves DP12 redirection using the redirection counter field of an initial address message (IAM). When the call is sent to the visited network, IntelliGate  22 , which is handling the call, is able to place a maximum value in the redirection counter field in the IAM message.  
         [0099]     It is noted that due to inconsistency in International carrier behavior the redirection parameter is sometimes omitted on the way.  
         [0000]     Methods for Forwarding Unanswered Calls to Voicemail  
         [0100]     The OVMD preferably includes a variety of methods for diverting unanswered calls to the voicemail (or other destinations). Due to the variance between mobile networks, each solution may best suit specific networks, and a complete package preferably includes multiple options.  
         [0101]     The following describes several possibilities for providing late call forwarding without international tromboning. The offered solutions have been outlined above and can be divided into two groups of solutions:  
         [0000]     1. IN-based solutions  
         [0000]     a. Double Triggering on DP12  
         [0000]     b. IN Service Broker for DP12  
         [0000]     c. Call status triggers such as “call busy” or “no answer” 
         [0000]     2. NSS-based solution  
         [0000]     a. Standard-based late call forwarding  
         [0000]     Double Triggering on DP12  
         [0102]     Reference is now made to  FIG. 4  which is a schematic diagram illustrating a solution based on the capability of an MSC to trigger two different SCPs, one using CAP and the second using INAP.  
         [0103]     The first trigger, that using CAP, is rerouted to the IntelliGate  22  by using a GT translation rule in the STP and the IntelliGate  22  responds with a CAP-Connect message with a predefined prefix on the directory number (DN) to activate the second trigger in the MSC based on this prefix.  
         [0104]     Postpaid Call Flow based on a foreign mobile station roaming number (MSRN) is illustrated in the figure and the flow is explained according to table 1 below.  
                         TABLE 1                           Postpaid User with Foreign MSRN            Step   Description               1   Mobile terminated (MT) call reaches the GMSC.           GMSC sends SRI message, HLR sends a PRN to the VLR to obtain the roamer&#39;s MSRN.       2   IntelliGate may be required to monitor the MAP-PRN and MAP_PRN_ACK messages in order to be           able to correlate between the MSRN and B-Party MSISDN, in case B-MSISDN is omitted from the           trigger in step #3.       3   Based on the foreign MSRN value the GMSC triggers the IntelliGate.       4   IntelliGate responds with a Connect to the MSRN and the call is sent to the visited network       5   After the roamer has not answered the call (or busy, or not reachable) the call is forwarded back to           the Voicemail Deposit number. A second trigger is defined on the GMSC for all calls coming from           abroad with DN = VoicemailDeposit to be sent to the IntelliGate. IntelliGate releases the call, causing           the trombone to be released.       6   When the release on the first international leg reaches the GMSC, it issues an ERB message to the           IntelliGate which sends a connect message to divert the call to the voicemail.       7   The voicemail answers the call and A-Party deposits a message.                  
 
         [0105]     Prepaid Roamer in a CAMEL Enabled VPMN  
         [0106]     Reference is now made to  FIG. 5  which is a schematic diagram illustrating the process flow when a prepaid roamer is roaming in a roaming network (VPMN) which is Camel enabled. In such a case the Camel provided IDP trigger may be used.  FIG. 5  is explained with reference to table 2 below.  
                         TABLE 2                           Prepaid Roamer in Camel enabled visited network            Step   Description               1   MT call reaches the GMSC.           GMSC sends SRI message, HLR sends the terminating trigger indication and the VLR#       2   The GMSC initiates an IDP message towards the Prepaid SCP. Based on a GT routing rule (SCCP) in the STP (1),           the trigger is rerouted to the IntelliGate, which responds with an RRB and a Connect message with a prefix added           to the DN value.       3   Based on the prefixed DN the GMSC issue a second INAP trigger and sends an IDP to the Prepaid SCP       4   A second MAP_SRI message is sent to the HLR, which sends a MAP_PRN to the VLR       5   The call is sent to the visited network based on the roamer&#39;s MSRN.       6   When the roamer does not answer the call, the visited network sends a CAMEL_IDP towards the prepaid system to           acknowledge the Mobile-Forwarded call. The O-CSI_IDP is again rerouted based on GT routing rule (SCCP), to the           IntelliGate. The IntelliGate checks if this is a MF call, if yes, it releases the call.           NOTE: if this is a regular MO call, IntelliGate relays the message to the Prepaid SCP (Actual GT) for further           handling. Please refer to Option 2 in the diagram above.       7   After the trombone has been released the GMSC sends an ERB to the Prepaid SCP, and a second ERB to the           IntelliGate       8   Using MAP_INTERROGATE_SS the IntelliGate retrieves the forward-to-numbers (FTN) before diverting the call to           the requested destination       9   The Voicemail answers the call and the caller (A-Party) can deposit a message                  
 
 Prepaid Roamer in a Non CAMEL VPMN 
 
         [0107]     Reference is now made to  FIG. 6 , which is a simplified schematic diagram illustrating the case of the prepaid roamer who is roaming in a network which is not Camel enabled. In this case the double triggering method referred to above is used based on adding a prefix to the DN value. The flow is explained with reference to Table 3 below. It is noted that while the visited network is not Camel enabled, the home network may be, and the case illustrated is that in which the home network is Camel-enabled.  
                         TABLE 3                           Prepaid user at a non-Camel enabled roaming network.            Step   Description               1   MT call reaches the GMSC.           GMSC sends SRI message, HLR sends the terminating trigger indication and the VLR#       2   The GMSC initiates an IDP message towards the Prepaid SCP. Based on a GT routing rule (SCCP) in the STP (1),           the trigger is rerouted to the IntelliGate, which responds with an RRB and a Connect message with a prefix added           to the DN value.       3   Based on the prefixed DN the GMSC issue a second INAP trigger and sends an IDP to the Prepaid SCP       4   A second MAP_SRI message is sent to the HLR, which sends a MAP_PRN to the VLR       5   The call is sent to the visited network based on the roamer&#39;s MSRN.       6   When the roamer does not answer (or Busy, or not reachable) the visited network releases the call. Once the           release message reaches the GMSC it sends an ERB to the prepaid SCP and a second ERB to the IntelliGate       7   Using MAP_INTERROGATE_SS the IntelliGate retrieves the forward-to-numbers (FTN) before diverting the call to           the requested destination (Connect(VMD))       8   The Voicemail answers the call and the caller (A-Party) can deposit a message                  
 
 Service Flow Using IN Service Broker 
 
         [0108]     Reference is now made to  FIG. 7 , which is a simplified diagram illustrating the service flow for a prepaid user in a Camel-enabled visited network where an IN service broker is used as the initial target of a trigger. In many cases a subscriber can have only one subscription-based trigger in the HLR. This means that in theory a subscriber can have only one application in the network that can be triggered. That is to say only one SCP can obtain the trigger. The purpose of having an IN Service Broker component in a network is to receive the trigger and then send out multiple triggers based thereon. In other words the broker can split the single trigger into multiple SCPs to be able to provide multiple services with a single subscription trigger.  
         [0109]     As the DP12 trigger is already taken for prepaid mobile-terminated calls while roaming, an IN Service Broker can be used in order to allow another service such as Optimal Voicemail Deposit for prepaid roamers to share the same DP12 IN trigger. In the following are discussed the call flows of the service when an IN Service Broker is in use.  
         [0110]     It is noted that the service broker is totally separated from the OVMD Service, logically and even physically.  
         [0111]      FIG. 7  illustrates the call flow for a prepaid roaming user in a CAMEL enabled VPMN, and shows the use of the IN service broker to provide two triggers. The call flow is explained in table below.  
                         TABLE 4                           Prepaid Roamer in Camel enabled visited network using IN service broker.            Step   Description               1   MT call reaches the GMSC.           GMSC sends SRI message, HLR sends the terminating trigger T-CSI indicator and the VLR#       2   The T-CSI IDP is sent from the GMSC to the Service Broker.           NOTE: The actual GT address of the IDP can be the prepaid SCP but the message should be rerouted by the STP           to the Service Broker, hence providing higher service availability in case of failure in the Service Broker       3   The Service Broker sends an IDP message to the first SCP - IntelliGate, and afterwards to the second SCP -           prepaid SCP.       4   An Accumulated response is sent from the Service Broker to the GMSC with all requests joined from all Back-end           SCPs IntelliGate and Prepaid system)       5   A second MAP_SRI is sent to the VLR to get the MSRN. The call is sent to the visited network.       6   When roamer does not answer, an O-CSI trigger for the forwarded leg is sent to the SCP. A routing rule in the STP           reroutes the trigger to the IntelliGate/Service Broker. When the IntelliGate gets the trigger it releases the call, thus           releasing the trombone       7   When the release message arrives, the GMSC sends an ERB message to the Service Broker, which sends an ERB           to the prepaid system (to close the charging session) and to the IntelliGate.       8   The IntelliGate diverts the call to the Voicemail Deposit number       9   A-Party deposits a message.                    
 Prepaid Roamer in Non CAMEL VPMN 
 
         [0112]     Reference is now made to  FIG. 8 , which is a simplified diagram illustrating the case of the use of an IN service broker for a prepaid roaming user located in a roaming network which is not Camel enabled. The flow is explained in Table below.  
                         TABLE 5                           Roaming user in non-Camel roaming network with use of IN service broker.            Step   Description               1   MT call reaches the GMSC.           GMSC sends SRI message, HLR sends the terminating trigger T-CSI indicator and the VLR#       2   The T-CSI IDP is sent from the GMSC to the Service Broker.           NOTE: The actual GT address of the IDP can be the prepaid SCP but the message should be rerouted by the STP           to the Service Broker. This shall provide higher service availability in case of failure in the Service Broker       3   The Service Broker sends an IDP message to the first SCP - IntelliGate, and afterwards to the second SCP -           prepaid SCP.       4   An Accumulated response is sent from the Service Broker to the GMSC with all requests joined from all Back-end           SCPs IntelliGate and Prepaid system)       5   A second MAP_SRI is sent to the VLR to get the MSRN. The call is sent to the visited network.       6   When the call is not answered, it is released because the VPMN has no CAMEL relationship with the HPMN.       7   When the release message arrives, the GMSC sends an ERB message to the Service Broker, which sends an ERB           to the prepaid system (to close the charging session) and to the IntelliGate.       8   The IntelliGate diverts the call to the Voicemail Deposit number       9   A-Party deposits a message.                  
 
 Service Flow Using INAP/CAP Call Status Triggers (“Such as “Call Busy” or “no Answer”) 
 
         [0113]     In the following are described different service flows for the methods based on making use of the call status triggers as outlined above. Specifically, use is made of INAP/CAP call status triggers, such as the triggers for “call busy” or “call not answered”. By using these triggers, the service overcomes the conflict with other services that use the TDP12, such as: Prepaid, Call Screening, VPN, etc services. The system is based on the TDP 13 and TDP 14, that is the busy and no answer triggers respectively.  
         [0114]     Reference is now made to  FIG. 9 , which is a simplified diagram illustrating the service flow when the roamer is a postpaid user. The flow is explained with respect to table 6 below.  
                         TABLE 6                           Call Termination Triggers with Postpaid User.            Step   Description               1   MT call reaches the GMSC.           GMSC sends SRI message, HLR sends a PRN to the VLR to get the roamer&#39;s MSRN       2   The GMSC sends the call to the visited network using the MSRN       3   The GMSC triggers the IntelliGate for all calls from abroad with DN = Voicemail Deposit (VMD)           number. The forwarded leg causes the GSMC to trigger the IntelliGate. The IntelliGate releases the           forwarded leg causing the release of the voicemail trombone.       4   When the mobile-terminated call is released without answer, a TDP13(Busy) or TDP14(No Answer)           situation is raised in the SSP, causing the SSP to trigger the IntelliGate with the relevant call details -           B-MSISDN, CLI, Release Cause.       5   MAP_SRI_SM is used for translating the MSISDN to IMSI, this is required for the next step       6   MAP_INTERROGATE_SS is used to retrieve the Forward-To-Number for the Release Cause       7   IntelliGate diverts the call to the corresponding destination according to the FTN.                  
 
 Prepaid Roamer in CAMEL VPMN Service Flow 
 
         [0115]     Reference is now made to  FIG. 10 , which illustrates a variation of the call termination trigger, TD13 and TD14 approach in the case of a prepaid roamer who is roaming in a Camel-enabled roaming network. The flow is explained with respect to table 7 below.  
                                   TABLE 7                           Call Termination Triggers with Prepaid User, Camel-Enabled roaming network.            Step   Description                    1   MT call reaches the GMSC, GMSC send first MAP_SRI to the HLR and gets the VLR# and T-CSI           subscription.       2   GMSC triggers the prepaid SCP, after processing the SCP responds with RRB, and Continue (or           Connect)       3   GMSC sends second SRI message, HLR sends a PRN to the VLR to get the roamer&#39;s MSRN. The           GMSC sends the call to the visited network using the MSRN.       4   When the call is not answered the visited MSC triggers the prepaid SCP (due to O-CSI). The prepaid           SCP responds with RRB and Continue (or Connect)       5   The forwarded leg is sent back home (to the voicemail deposit number). The GMSC is configured to           send all calls from abroad with DN = Voicemail Deposit (VMD) number to the IntelliGate, which           releases the call, thus releases the trombone.       6   The release of the forwarded leg causes the visited MSC to send an ERB back to the prepaid SCP.       7   The release of the mobile-terminated call causes the GSMC to send an ERB to the prepaid SCP.           This shall stop the charging session for the roaming MT call.       8   When the mobile-terminated call is released without answer, a TDP13(Busy) or TDP14(No Answer)           situation is raised in the SSP, causing the SSP to trigger the IntelliGate with the relevant call details -           B-MSISDN, CLI, Relase Cause.       9   MAP_SRI_SM is used for translating the MSISDN to IMSI, this is required for the           MAP_INTERROGATE_SS which is used to retrieve the Forward-To-Number for the Release Cause       10   IntelliGate shall divert the call to the corresponding destination according to the FTN.                  
 
 Service Flow Using Standard-based Late Call Forwarding 
 
         [0116]     In the following is described the fourth triggering option outlined above. As explained, GSM includes support for optimal routing (SOR). The following methods are possible when the home network (HPMN) supports the 3GPP standard Support for Optimal Routing (SOR). The home based IntelliGate includes a module that emulates Support for Optimal Routing with all visited networks. That is to say the emulator supplies the signals that the visited network is supposed to supply but usually does not in order to provide optimal routing. As a result of using the emulator the home network sees a universe of neighboring networks which all appear to behave as if they are SOR compatible and thus tromboning can be prevented.  
         [0117]     The emulator preferably uses probes that monitor the International signaling links and is thus able to obtain sufficient information to provide the emulation. Typically the emulator uses the SCCP relay module for relaying specific MAP messages before the call is initially routed to the visited network.  
         [0118]     Reference is now made to  FIG. 11 , which is a simplified schematic diagram that illustrates the process flow with a SOR emulator that uses probes when a postpaid roaming user is located in a Non CAMEL VPMN that is not SOR compatible. It will be appreciated that if the VPMN is SOR compatible then the emulation does not need to do anything.  
                                   TABLE 8                           SOR emulation for a postpaid User in non-SOR compatible, non-Camel       Roaming Network, using a regular probe.            Step   Description                    1   MT call reaches the GMSC.           All GMSCs and HLRs of the operator are configured to perform SOR for every MT call by roaming           subscribers           (by specifying the relevant fields in the Send Routing Information (SRI) and Provide Roaming Number           (PRN) MAP messages).           GMSC sends SRI message, specifying SOR is requested, the Call Reference and the GMSC           Address.       2   PRN message is sent from HLR to foreign VLR.           Foreign VLR, that does not support SOR or does not have a SOR agreement with the HPMN, will           simply ignore the SOR indication, and continue (allocate MSRN).       3   PRN ACK messages returning from foreign VLR are forwarded to HLR.           Messages contain the MSRN.           Intelligate MAP probe captures the PRN transaction (PRN &amp; PRN Ack), and stores its relevant           parameters:           IMSI, MSRN, Call Reference &amp; GMSC Address.           In addition, same probe is used offline for the registration process (UL &amp; SD messages), and stores           relevant information about the subscriber (IMSI, MSISDN, Call Forwarding Information, O-CSI           information etc).       4   SRI with MSRN is returned to the GMSC.       5   GMSC routes the call towards MSRN.           An ISUP routing rule or IN trigger on the GMSC routes the call to the IntelliGate. Criteria is Called           Number = foreign MSRN (MT call to roaming destination).           IntelliGate receives ISUP_IAM or IN_IDP message.       6   IntelliGate connects the call towards the original MSRN, by using another ISUP_IAM message or           IN_CONNECT.           If using IN, IntelliGate arms the relevant DPs (Busy, No-Answer, Answer).       7   GMSC routes the call towards the MSRN, to the foreign MSC (through international).           Call reaches the visited MSC (serving MSC of B Party).       8   B Party is not reachable/rejects the call/does not answer.           In order to prevent the trombone, the forwarded leg must be released, can either:           1. Have call forwarding disabled by HLR during registration to the visited network           (HLR not sending FTNs in MAP_ISD)           2. Let IntelliGate send a following MAP_ISD (with disabled FTNs) after each           MAP_ISD sent by HLR           3. Leave the call forwarding setting as is, but disconnect the forwarded leg that           returns to the HPMN (disconnect is done by IntelliGate to all incoming calls with           DN = VM Deposit)           4. In CAMEL VPMNs, redirect the O-CSI IDP to the IntelliGate to respond with a           IN_ReleaseCall to MF calls or relay all MO calls to original SCP.           In all cases, the next step (9) occurs.       9   Visited MSC releases the call towards the HPMN.       10   GMSC receives the release from the visited network, and passes it to the IntelliGate - using ISUP           REL message or IN_ERB message.       11   IntelliGate does NOT pass the release on.           Instead, it sends Resume Call Handling (RCH) MAP message towards the GMSC, specifying the Call           Reference of the call (as received in the PRN), the Forwarding Reason and any required additional           information (like the forwarding information, O-CSI etc).       12   GMSC performs the SOR logic, which causes it to release the forward leg towards the IntelliGate.       13   GMSC continues the SOR logic, routing the call towards the forwarded leg, i.e., Voicemail system.       14   Call is connected to destination forwarding.                  
 
         [0119]     Reference is now made to  FIG. 12  which illustrates SOR emulation in the case that a postpaid Roamer is located in a Non CAMEL visited network VPMN. An SCCP Relay is used, as opposed to the probe in the embodiment of  FIG. 11 .  
                                   TABLE 9                           SOR emulation for a Postpaid roaming user in a roaming network which is       neither Camel nor SOR enabled. The emulator uses an SCCP relay.            Step   Description                    1   MT call reaches the GMSC.           All GMSCs and HLRs of the operator are configured to perform SOR for every MT call by roaming subscribers           (by specifying the relevant fields in the Send Routing Information (SRI) and Provide Roaming Number (PRN) MAP           messages).           GMSC sends SRI message, specifying SOR is requested and the Call Reference.       2   All PRN messages directed to foreign VLRs are routed to the IntelliGate (by the operator&#39;s STP).           The IntelliGate removes all SOR-related features, and relays the PRN towards the original VLR.       3   All PRN ACK messages returning from foreign VLRs are routed to the IntelliGate (by the operator&#39;s STP).           The IntelliGate replaces the MSRN returned in the PRN ACK with its own DID numbers, and relays the PRN ACK to           the HLR.       4   SRI with MSRN = DID is returned to the GMSC.       5   GMSC places a call towards the DID.           An ISUP routing rule or IN trigger routes the call to the IntelliGate, based on the DID prefix.           IntelliGate receives ISUP_IAM or IN_IDP message.       6   IntelliGate connects the call towards the original MSRN, by using another ISUP_IAM message or IN_CONNECT.           If using IN, IntelliGate arms the relevant DPs (Busy, No-Answer, Answer).       7   GMSC routes the call towards the MSRN, to the foreign MSC (through international link).           Call reaches the visited MSC (serving MSC of B Party).       8   B Party is not reachable/rejects the call/does not answer.           In order to prevent the trombone, the forwarded leg must be released, this can be achieved by one of the following           options:           5. Having call forwarding disabled by the HLR during registration to the visited network (HLR not           sending FTNs in MAP_ISD)           6. Having the IntelliGate send a following MAP_ISD (with disabled FTNs) after each MAP_ISD           sent by HLR           7. Leaving the call forwarding setting as is, but disconnecting the forwarded leg that returns to the           HPMN (disconnect is done by IntelliGate to all incoming calls with DN = VM Deposit)           8. In CAMEL VPMNs, redirect the O-CSI IDP to the IntelliGate to respond with a IN_ReleaseCall           to MF calls or relay all MO calls to original SCP.           In all cases, the next step (9) occurs.       9   Visited MSC releases the call towards the HPMN.       10   GMSC receives the release from the visited network, and passes it to the IntelliGate - using ISUP REL message or           IN_ERB message.       11   IntelliGate does NOT pass the release on.           Instead, it sends a Resume Call Handling (RCH) MAP message towards the GMSC, specifying the Call Reference           of the call (as received in the PRN) and the Forwarding Reason.       12   GMSC performs the SOR logic, which causes it to release the forward leg towards the IntelliGate DID.       13   GMSC continues the SOR logic, sending an SRI message towards the HLR, requesting the forwarding information           for the specified forwarding reason.       14   The GMSC routes the call towards the forwarded leg, i.e., Voicemail system.                  
 
       SUMMARY  
       [0120]     All of the optimal voicemail deposit methods have the advantages that they eliminate tromboning, meaning they bypass international leg for voicemail, significantly reducing costs to the subscriber. They thus encourage greater use of the mobile phone and voicemail, in particular by optimizing user experience and significantly reducing voicemail deposit costs. In each case described there is no dependency on the visited network since different workflows are available for each different visited network configuration. That is to say the same solution enables the elimination of voicemail trombone and recovery of lost revenue without any dependency on the visited network.  
         [0121]     It is expected that during the life of this patent many relevant devices and systems will be developed and the scope of the terms herein, is intended to include all such new technologies a priori.  
         [0122]     It is appreciated that certain features of the invention, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the invention, which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable subcombination.  
         [0123]     Although the invention has been described in conjunction with specific embodiments thereof, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art. Accordingly, it is intended to embrace all such alternatives, modifications and variations that fall within the spirit and broad scope of the appended claims. All publications, patents, and patent applications mentioned in this specification are herein incorporated in their entirety by reference into the specification, to the same extent as if each individual publication, patent or patent application was specifically and individually indicated to be incorporated herein by reference. In addition, citation or identification of any reference in this application shall not be construed as an admission that such reference is available as prior art to the present invention.