Patent Grant
8730970
The subject matter described herein relates to voicemail routing. More particularly, the subject matter described herein relates to providing voicemail routing information in a network that provides customized voicemail services.
Current voicemail routing systems typically use a range-based mechanism where voicemail (VM) calls are routed to one of several voicemail server centers (VMSCs) in an equal load-sharing scheme. For example, in an exemplary network including multiple conventional VMSCs, each VMSC may be assigned a range of subscribers. Subscribers may be identified by a subscriber identifier, such as mobile station ISDN number (MSISDN) or directory number (DN). Therefore, when a VM call arrives at a particular mobile switching center (MSC), the MSC may simply route the voicemail call to a VMSC based on the subscriber identifier. By equally dividing subscriber identifiers among multiple VMSCs, current methods load-share voicemail services for all network subscribers across all available VMSCs.
Current voicemail routing systems also typically provision each VMSC with the same set of voicemail services, regardless of whether the distribution of users requiring those services is uniform. Yet with the introduction of premium voicemail services, such as video-voicemail and multimedia-voicemail, network operators employing conventional voicemail routing systems must either upgrade all of their existing VMSCs or forgo these advanced services. For example, in an exemplary network containing multiple VMSCs providing standard voicemail services, all VMSCs in the network must be upgraded in order to provide premium voicemail services to a minority of subscribers.
Therefore, one problem associated with current voicemail routing systems is the inability assign subscribers to VMSCs on an individual basis. Moreover, because the desire for premium voicemail services is unevenly distributed throughout the customer base, yet VMSCs must be identically provisioned, network operators must either over-provision or under-provision voicemail server resources, thereby incurring added inefficiency and expense.
Accordingly, a need exists for improved methods, systems, and computer program products for providing voicemail routing information in a network that provides customized voicemail services.
According to one aspect, the subject matter described herein comprises methods, systems, and computer program products for providing voicemail routing information in a network that provides customized voicemail services. One method includes receiving a voicemail routing query at an advanced voicemail routing node, where the query includes at least one parameter associated with a voicemail transaction. Based on at least one query parameter, voicemail routing information may be determined that identifies a voicemail server. In one implementation, the voicemail server may be identified from a plurality of voicemail servers, where at least some of the voicemail servers provide different services. A voicemail routing query response may then be generated including the determined voicemail routing information.
The term “advanced voicemail routing node,” as used herein, refers to a node that provides or obtains voicemail routing information and that routes signaling messages. The voicemail routing information obtained by the advanced voicemail routing node may be voicemail routing information that identifies a specific voicemail server or service in a network that provides plural voicemail servers or services. In one example, the network may include a plurality of non-identically provisioned voicemail servers and the voicemail routing information may identify a specific voicemail server from the non-identically provisioned voicemail servers. In an alternate implementation, the network may include a plurality of identically provisioned voicemail servers where different subscribers are assigned to different servers, and the voicemail routing information may identify the voicemail server from the identically provisioned voicemail servers to which a subscriber is assigned.
According to another aspect, an advanced voicemail routing node may include a communications module configured to receive a voicemail routing query, and a voicemail routing module configured to determine voicemail routing information based on at least one voicemail routing query parameter and to generate a voicemail routing query response including a determined voicemail routing information. The voicemail routing query may include at least one parameter associated with a voicemail transaction and voicemail routing information may identify a voicemail server. In one implementation, the voicemail server may be identified from a plurality of voicemail servers where at least some of the voicemail servers provide different services.
The subject matter described herein for may be implemented in hardware, software, firmware, or any combination thereof. As such, the terms “function” or “module” as used herein refer to hardware, software, and/or firmware for implementing the feature being described. In one exemplary implementation, the subject matter described herein may be implemented using a computer program product comprising computer executable instructions embodied in a computer readable medium. Exemplary computer readable media suitable for implementing the subject matter described herein include disk memory devices, chip memory devices, programmable logic devices, application specific integrated circuits, and downloadable electrical signals. In addition, a computer program product that implements the subject matter described herein may be located on a single device or computing platform or may be distributed across multiple devices or computing platforms.
The subject matter described herein will now be explained with reference to the accompanying drawings of which:
Advanced voicemail routing query 112 may include, for example, the calling party number, the dialed number, and the voice/video capabilities of calling party 102. Query 112 may then be received by communications module 116, which communicates with voicemail routing module 118. Voicemail routing module 118 may use the information contained in query 118 to search one or more tables for voicemail routing information associated with the call. These tables may be provisioned by an external database, such as one located on external provisioning and application processor (EPAP) node 120. Upon determining voicemail routing information associated with the call, voice mail routing module 118 may generate a voicemail routing query response 122 and forward the response to communications module 116, which sends the response over an external signaling link. Voicemail routing response 122 may be received by MSC 104 and used to connect calling party 102 to one of VMSCs 106-110 by communicating with one of communications modules 124 located on each VMSC 106-110. Communications modules 124 may then use the voicemail routing information to route calling party 102 to one of voicemail services 126-142.
In
In the embodiment illustrated in
In one exemplary implementation, voicemail routing module 118 may examine a call condition in addition to subscriber identification information in a voice mail query to determine the VMSC and service to which a call should be routed. For example, voicemail routing module may determine from parameters in the query message whether a voice mail deposit or retrieval is being made. If a deposit is being made, routing information may be returned that indicates the VMSC provisioned to receive voice mail deposits for the called party. If a retrieval is being made, routing information may be returned that indicates the VMSC provisioned to store voice mail messages for the calling party.
Referring to Table 1, exemplary voicemail routing query 112 may include a message transfer part (MTP) originating point code (OPC) and a destination point code (DPC) associated with the query originator and query destination, respectively. For example, the OPC may identify MSC 104 and the DPC may identify advanced voicemail routing node 114. Query 112 may further include a signaling connection and control part (SCCP) calling party identifier (CgPA) and called party identifier (CdPA). The SCCP CdPA may also be used to identify advanced voicemail routing node 114. However, the SCCP CdPA may by identify node 114 by global title address (GTA) or by point code (PC) and subsystem number (SSN) depending on whether “route-on-GT” or “route-on-PC/SSN” is used.
Query 112 may also include a parameter containing either an intelligent network application part (INAP) called party number (CdPN) associated with a voicemail number, or a customized applications for mobile networks enhances logic (CAMEL) application part (CAP) called party identifier associated with a voicemail prefix+MSISDN. A similar parameter may be included for the INAP/CAP calling party number (CgPN).
The INAP/CAP information in the query may include the MSISDN digits, which may be used to identify the subscriber (calling or called party) and the call condition (deposit or retrieval). For example, query 112 may include an INAP or CAP redirect indicator (RDI) indicating whether or not the call has been redirected. For example, an RDI=1 may indicate that the call has been redirected and is therefore associated with a voicemail deposit. And an RDI=0 may indicate that the call has not been redirected, and therefore may be associated with a voicemail deposit or retrieval transaction, depending on the values of other parameters that may be included in query 112. Query 112 may also include an INAP/CAP original called number (OCN) or redirecting dialed number (RDN) that may be used to determine an MSISDN if the call is redirected. An OCN may be included in query 112 depending on a number of factors and an RDN may be included when no OCN exists.
Finally, query 112 may include an INAP/CAP bearer capabilities indicator. The bearer capabilities indicator specifies, for example, whether the calling party is capable of performing a standard voicemail transaction or whether it is capable of also performing advanced voicemail transactions, such as video-voicemail deposits and retrievals. For standard voicemail transactions, the bearer capabilities parameter may include the text string “3.1 kHz audio”. Alternatively, for premium video-voicemail transactions, the bearer capabilities parameter may include the string “64 kb/s unified display interface (UDI) video”.
It is appreciated that voicemail routing query 112 may include an international telecommunication union (ITU) European telecommunications standards institute (ETSI) intelligent network application part (INAP) initial detection point (IDP) query or a third generation partnership project 3GPP customized applications for mobile networks enhanced logic (CAMEL) application part (CAP) IDP query.
In block 202, voicemail routing information may be determined based on at least one of the plurality of voicemail routing query parameters described in Table 1 above. The voicemail routing information may identify a voicemail server from among a plurality of voicemail servers, where at least some of the voicemail servers are configured to provide different services. The voicemail routing information may also identify a voicemail service from among the various voicemail services provided by a particular VMSC.
In one embodiment, voicemail routing information may be determined by searching one or more tables containing voicemail routing information associated with information like the information contained in voicemail routing query 112. For example, advanced routing node 114 may include three tables, such as Tables 300, 400, and 500, which contain voicemail routing information. In this exemplary embodiment, a first table may contain one or more voicemail server center identifiers (VMSC IDs) associated with one or more subscriber identifiers, such as an MSISDN or DN. Voicemail routing module 118 may search this first table in order to determine the VMSC ID associated with a particular MSISDN. A second table may contain one or more voicemail service indexes (VM Indexes) associated with various call decision criteria. Voicemail routing module 118 may search this second table in order to obtain a VM Index associated with the call, such as a voicemail deposit or voicemail retrieval service. Finally, a third table may contain one or more VMSC IDs and VM Indexes associated with a unique VM routing number (RN). Voicemail routing module 118 may then search this third table in order to determine a VM RN associated with the VMSC ID and VM Index obtained from the first and second tables. The VM RN may then be used by MSC 104 to connect the calling party to the appropriate voicemail server and service.
Returning to the determination made by voicemail routing module 118 of a VMSC ID based on a subscriber identifier, such as an MSISDN, in order to make this determination advanced voicemail routing node 114 may first perform a process hereinafter referred to as “number conditioning” on information contained in query 112 in order to obtain an MSISDN. For example, query 112 typically contains a subscriber identifier used by voicemail routing module 118, such as an MSISDN or DN. However, this subscriber identifier may be located in any one of several different parameters in query 112. The location of the subscriber identifier may be based various factors, such as whether the calling party is roaming. Therefore, advanced voicemail routing node 114 may determine the location of subscriber identifier information included in query 112 based on an examination of these factors, and extract the subscriber identifier from the appropriate parameter location. Once extracted, the subscriber identifier may then be used by voicemail routing module 118 to search Table 300.
Exemplary number conditioning may include examining a voicemail routing query 112 that contains a parameter including both a VM prefix and a MSISDN. This parameter may include a VM prefix and a MSISDN if a first subscriber dials the voicemail number of another subscriber without being redirected. In this situation, node 114 may extract the MSISDN from the parameter by removing the VM prefix. Alternatively, if the calling subscriber has been redirected, as indicated by an RDI=1, node 114 may extract an MSISDN from the OCN or RDN parameters in query 112.
In some situations, node 114 may fail to obtain a valid MSISDN or other subscriber identifier from a parameter in query 112. For example, an invalid MSISDN may result from an attempted voicemail retrieval from a landline phone or an attempted voicemail retrieval from a mobile phone forwarded from a landline phone. In situations where no valid subscriber identifier is obtained, a default subscriber identifier may be used to search Table 300 for an appropriate VMSC ID.
It is appreciated that voicemail routing information may be contained in a single table or distributed across multiple tables without departing from the subject matter described herein. Moreover, any table or tables searched by voicemail routing module 118 may be implemented in software, hardware or any combination thereof.
In block 204, a voicemail routing response may be generated including the voicemail routing information determined in block 202. The voicemail routing response may then be used by the MSC 104 to connect calling party 102 to the voicemail server and voicemail service on that server indicated by the voicemail routing information. For example, advanced voicemail routing node 114 may generate voicemail routing response 122 that includes VM RN=612000589. Therefore, upon receiving voicemail routing response 122, MSC 104 may connect calling party 102 to voicemail deposit service 126 located on standard voicemail server 106 in order to perform a standard voicemail deposit.
Table 300 includes one or more subscriber identifiers associated with a VMSC ID. In the embodiment illustrated in
It is appreciated that the exact structure and contents of Table 300 may be determined by the implementation. In one implementation, Table 300 may be created by adding VMSC ID associations to a pre-existing table including one or more subscriber identifiers as well as other information. Such a pre-existing table may be located, for example, on a signaling message network node, such as a signal transfer point (STPs), that may be include advanced voicemail routing module 118.
In order to illustrate the process of obtaining a VMSC ID based on a subscriber identifier obtained from voicemail routing query 112 using Table 300, exemplary scenarios are described below which illustrate conditions for directing a subscriber to different voicemail services within the same voicemail server, or for directing a subscriber to a different voicemail server based on an MSISDN.
In one example, VMSC ID=1 may be obtained corresponding to standard voicemail server 106 based on a search of Table 300 for MSISDN=611061**. In this case, it will be appreciated from Table 300 shown in
In another example, VMSC ID=2 may be obtained corresponding to standard voicemail server 108 based on a search of Table 300 for MSISDN=611062**. In this case, it will be appreciated from Table 300 shown in
In another example, VMSC ID=3 may be obtained corresponding to premium voicemail server 110 based on a search of Table 300 for MSISDN=611063**. In this case, it will be appreciated from Table 300 shown in
It is appreciated that MSISDNs included in Table 300 may be stored in International format which is defined to include a country code (CC)+a national destination code (NDC)+a subscriber number (SN). Table 300 may support individual MSISDN entries and MSISDN range entries comprising 1-15 digits of any hexadecimal value. Table 300 may be searched according to a longest match, best-fit algorithm for any length of entry or range of entries. If no specific individual entry is found matching the search criteria, a range-match search may be performed. In one implementation, table 300 may be arranged to have range-based entries and exception-based entries where the range-based entries correspond to MSISDN ranges and the exception-based entries contain individual MSISDN numbers that are within one of the ranges defined by the range-based entries or outside of all of the ranges defined by the range-based entries. An exception-based entry that contains an MSISDN that is within one of the ranges defined by a range-based entry may have a different VMSC ID provisioned from the corresponding range-based entry. In operation, a lookup may be first performed in table 300 for an exception-based entry that matches an MSISDN in a query message. If the lookup results in a match, the VMSC ID corresponding to the exception-based entry may be extracted. If the lookup fails to result in a match, table 300 may be searched for a range-based entry corresponding to a range within the MSISDN falls. If a matching range-based entry is located, the VMSC ID corresponding to the matching range-based entry is extracted. If no match occurs, an error may be returned, or a default VMSC ID may be returned. After obtaining a VMSC ID in Table 300, node 114 may obtain a VMSC Index using a call decision table, such as Table 400 illustrated in
In the example call decision table 400 illustrated in
Similar to VM Indexes 1-3 described above, VM Indexes 4-6 correspond to similar transactions, except for being related to video-voicemail transactions rather than standard voice-voicemail transactions. For example, VM Index=4 indicates a video-voicemail deposit. VM Index=5 indicates an authorized video-voicemail retrieval and VM Index=6 indicates an unauthorized video-voicemail retrieval. VM Indexes=7 and above may be reserved for default or error voicemail transactions.
In
Column 406 includes INAP/CAP bearer capabilities values indicating, for example, whether the calling party is placing a voice- or video-based voicemail call. Column 408 may include a value indicating whether an entry matching the MSISDN extracted from query 112 was located in Table 300. For example, a text string such as “yes” or “no” may be included in column 408, or a numerical method similar to column 404. Column 410 includes VM Indexes corresponding to VM services located on each VMSC 106-110. In exemplary Table 400, VM Indexes 1-6 are illustrated, corresponding to deposit and retrieval services for both standard voicemail and premium video-voicemail transactions.
In the standard voicemail deposit scenario described earlier, a VMSC ID=1 was obtained for the MSISDN 611061**. Using this same MSISDN, a VMSC Index=1 may be obtained in entry 412 based on a match between information contained in query 112 and call decision criteria located in columns 402-410. For example, a VMSC Index=1 may be obtained in Table 400 based on a lookup performed based on CdPN=611061***, RDI=1, 3.1 kHz audio bearer capabilities, and locating the MSISDN in Table 300. Based on these parameters, a calling party wishing to make a voicemail deposit may be routed to a voicemail deposit service on an appropriate VMSC.
Continuing the authenticated standard voicemail retrieval scenario described above, a VMSC ID=2 was obtained for the MSISDN 611062**. Using this MSISDN, a VMSC Index=2 may be obtained in entry 414 based on a match between information contained in query 112 and call decision criteria located in columns 402-410. For example, a VMSC Index=2 may be obtained in Table 400 based on a voicemail routing query 112 that contains CdPN=611062***, RDI=0, 3.1 kHz audio bearer capabilities, and successfully locating the MSISDN in Table 300.
Continuing the unauthenticated standard voicemail retrieval scenario described above, a VMSC ID=3 was obtained for the MSISDN 611062**. Using this MSISDN, a VMSC Index=3 may be obtained in entry 416 based on a match between information contained in query 112 and call decision criteria located in columns 402-410. For example, a VMSC Index=3 may be obtained in Table 400 based on a voicemail routing query 112 that contains CdPN=611062***, RDI=0, 3.1 kHz audio bearer capabilities, and not locating the MSISDN in Table 300.
Continuing the premium voicemail deposit scenario described above, a VMSC ID=4 was obtained for the MSISDN 611063**. Using this MSISDN, a VMSC Index=4 may be obtained in entry 418 based on a match between information contained in query 112 and call decision criteria located in columns 402-410. For example, a VMSC Index=4 may be obtained in Table 400 based on a voicemail routing query 112 that contains CdPN=611063***, RDI=1, 64 kb/s UDI video bearer capabilities, and successfully locating the MSISDN in Table 300.
It is appreciated in
Continuing the standard voicemail deposit scenario described above, a VMSC ID=1 resulting from the determination made in Table 300 and a VM Index=1 resulting from the determination made in Table 400 are associated with entry 508 containing VM RN=612000589 in Table 500. This VM RN corresponds to a standard voicemail deposit service located on standard voicemail server 106.
Continuing the authenticated voicemail retrieval scenario described above, a VMSC ID=2 resulting from the determination made in Table 300 and a VM Index=2 resulting from a determination made in Table 400 are associated with entry 510 containing VM RN=612000713 in Table 500. This VM RN corresponds to an authenticated voicemail retrieval service located on standard voicemail server 106.
Continuing the unauthenticated voicemail retrieval scenario described above, a VMSC ID=2 resulting from the determination made in Table 300 and a VM Index=3 resulting from a determination made in Table 400 are associated with entry 512 containing VM RN=612000900 in Table 500. This VM RN corresponds to an authenticated voicemail retrieval service located on standard voicemail server 106.
Continuing the video-voicemail deposit scenario described above, a VMSC ID=3 resulting from the determination made in Table 300 and a VM Index=4 resulting from the determination made in Table 400 are associated with entry 514 containing VM RN=614000557. This VM RN corresponds to a standard vide-voicemail deposit service located on premium voicemail server 110.
Each module 124, 602, and 604 may execute the applications or functions that reside on each module and control communication with other modules via bus 608. For example, DSM 604 may execute software that determines voicemail routing information in a network that provides customized voicemail services.
LIM 124 may include an SS7 MTP level 1 and 2 function 610, an I/O buffer 611, a gateway screening (GWS) function 612, a message discrimination function 614, a message distribution function 616, and a route manager 618. MTP level 1 and 2 function 610 sends and receives digital data over a particular physical interface, provides error detection, error correction, and sequenced delivery of SS7 message packets. I/O buffer 611 provides temporary buffering of incoming and outgoing signaling messages.
GWS function 612 examines received message packets and determines whether the message packets should be allowed into signaling message routing node 114 for processing and/or routing. Discrimination function 614 performs discrimination operations, which may include determining whether the received message packet requires processing by an internal processing subsystem or is simply to be through switched (i.e., routed on to another node in the network). Messages that are permitted to enter signaling message routing node 114, such as voicemail routing queries, may be routed to other communications modules in the system or distributed to an application engine or processing module via bus 608.
DSM 604 may receive voicemail routing queries from LIM 124 via message distribution function 616. Distribution function 616 located on LIM 124 may forward initial detection point (IDP) queries to DSM 604 via bus 608. Upon receiving an IDP query, voicemail routing function 606 may perform a lookup in voicemail routing database 607 to determine a voicemail routing number based on information contained in the IDP query. Voicemail routing database 607 may contain voicemail routing information, such as MSISDNs, VMSC IDs, VM indexes, bearer capabilities, and other information as illustrated in
DCM 602 includes functionality for sending and receiving SS7 messages over IP signaling links. In the illustrated example, DCM 602 includes a physical layer function 622, a network layer function 624, a transport layer function 626, an adaptation layer function 628, and functions 612, 616, and 618 described above with regard to LIM 601. Physical layer function 622 performs open systems interconnect (OSI) physical layer operations, such as transmitting messages over an underlying electrical or optical interface. In one example, physical layer function 622 may be implemented using Ethernet. Network layer function 624 performs operations, such as routing messages to other network nodes. In one implementation, network layer function 624 may implement Internet protocol. The transport layer function 626 implements OSI transport layer operations, such as providing connection oriented transport between network nodes, providing connectionless transport between network nodes, or providing stream oriented transport between network nodes. Transport layer function 626 may be implemented using any suitable transport layer protocol, such as stream control transmission protocol (SCTP), transmission control protocol (TCP), or user datagram protocol (UDP). Adaptation layer function 628 performs operations for sending and receiving SS7 messages over IP transport. Adaptation layer function 628 may be implemented using any suitable IETF or other adaptation layer protocol. Examples of suitable protocols include MTP level 2 peer-to-peer user adaptation layer (M2PA), MTP level 3 user adaptation layer (M3UA), and/or signaling connection control part (SCCP) user adaptation layer (SUA). Functions 612, 616, and 618 perform the same operations as the corresponding components described above with regard to LIM 601.
Voicemail routing database 604 may be provisioned by a centralized database, such as the EAGLE™ provisioning and application server available from Tekelec, Inc. of Morrisville, N.C. EPAP and advanced voicemail routing node 114 may each include a provisioning database interface (PDBI) for providing provisioning services, where the PDBI is a socket-based interface connecting nodes via transmission control protocol/Internet protocol (TCP/IP). The PDBI supports creating or deleting an MSISDN and/or a VMSC ID in Table 300, as well as retrieving attributes of an MSISDN with a specific status when an MSISDN does not exist or cannot be located in Table 300.
In the examples described above, advanced voicemail routing information is obtained for SS7 signaling messages. However, the presently disclosed subject matter is not limited to these examples. In an alternate example, advanced voicemail routing information can be obtained for SIP signaling messages.
In the scenario illustrated in
Upon receiving Invite message 712, SIP signaling point 700 may route message 712 to called party 702. In this exemplary scenario, called party 702 is unavailable to receive the call and therefore, in response, may generate 486 busy message 714. It is appreciated that additional URI parameters may be generated by called party 702 including, but not limited to, unknown/not available 404, no reply 408, unconditional 302, deflection during alerting 487, deflection immediate response 480, mobile subscriber not reachable 503.
SIP signaling node may then generate and send voicemail query 716 to advanced voicemail routing node 704 which includes Cause parameter 486 Busy extracted from message 714. In addition, voicemail query 716 may include information included in Invite message 712, such as the called party URI and the media type. In response to advanced voicemail routing query 716, advanced voicemail routing node 704 may generate voicemail response message 718 and send it to one of voicemail servers 706-710 based on an examination of information included in query 716.
In the example illustrated in
Accordingly, it is appreciated that multiple levels of voicemail discrimination are possible by advanced voicemail routing node 704 depending on the type of information included in, for example, voicemail query message 716. A first level of discrimination for determining a particular voicemail server to be associated with a given voicemail transaction includes the called party identifier. A second level of discrimination may include determining a voicemail server based on media type information included in, for example, a SIP Invite message associated with the transaction. Thirdly, the Cause code generated by the called party may be used to determine the type of voicemail transaction to be performed. For example, in one possible embodiment, voicemail servers 706-710 may be divided by transaction type in addition to media type and called party identifier. Therefore, advanced voicemail routing node may examine SIP information associated with the voicemail transaction in order to route the message to the proper voicemail server.
In the example in
The exemplary embodiment shown in
In the illustrated embodiment, advanced voicemail routing function 1112 may return a location routing number (LRN) associated with the selected VM server and terminate IAM message 1108. Advanced voicemail routing function 1112 may then generate an ISUP response message, such as REL message 1118, that is returned to EO 1100, where the ISUP response message includes information which identifies the selected VM server. Exemplary ISUP response messages may include, but are not limited to an ISUP RELEASE (REL) message and an ISUP Address Complete (ACM) message. In the exemplary embodiment shown in
Upon receiving the REL message 1118, EO 1100 may generate a subsequent ISUP IAM message, such as ISUP IAM message 1120, which includes the LRN of the selected VM server, as well as the original CdPN and CgPN information. It is appreciated that EO 1100 may also generate an ISUP Release Complete message (not shown) without departing from the scope of the subject matter described herein. IAM message 1120 may then be routed via STP 1110 to VM server 1116 identified by the included VM LRN.
As such, using the triggerless advanced voicemail routing functionality described herein, an EO (or MSC, MGC, SS, etc.) may take advantage of advanced voicemail routing functionality without requiring AIN/IN triggers or TCAP query/response transactions.
Continuing the illustrated example, EO 1100 may generate IAM message 1108 and include the VM Redirect Number. IAM message 1108 may then be transmitted to STP 1110, where STP 1110 may include an integrated advanced voicemail routing function or a non-integrated advanced voicemail routing function may be accessible by STP 1110. In the example shown, STP 1110 includes an integrated advanced voicemail routing function 1112. STP 1110 receives IAM message 1108 and examines the Redirect Number information contained in the message. STP 1110 identifies the Redirect Number as being associated with STP/advanced voicemail routing function 1110, and passes IAM message 1108 to advanced voicemail routing function 1112. Advanced voicemail routing function 1112 examines information contained in IAM message 1108 and, based on this information, may select one of many VM servers 1114 to which the call should directed. Exemplary IAM information that may be used to select a VM server includes, but is not limited to, called party number information. Advanced voicemail routing function 1112 may return a local routing number associated with the selected VM server, such as VM server 1116 in the example illustrated in
As opposed to the triggerless embodiment described in
As such, using such triggerless V-flex functionality, an EO (or MSC, MGC, SS, etc.) may take advantage of V-flex functionality without requiring AIN/IN triggers or TCAP query/response transactions.
It will be understood that various details of the subject matter described herein may be changed without departing from the scope of the subject matter described herein. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation.
This application claims the benefit of U.S. Provisional Patent Application Ser. No. 60/903,185 filed Feb. 23, 2007, the disclosure of which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3917915 | Karras | Nov 1975 | A |
| 4162377 | Mearns | Jul 1979 | A |
| 4191860 | Weber | Mar 1980 | A |
| 4310727 | Lawser | Jan 1982 | A |
| 4313035 | Jordan et al. | Jan 1982 | A |
| 4385206 | Bradshaw et al. | May 1983 | A |
| 4754479 | Bicknell et al. | Jun 1988 | A |
| 4756020 | Fodale | Jul 1988 | A |
| 4769834 | Billinger et al. | Sep 1988 | A |
| 4788718 | McNabb et al. | Nov 1988 | A |
| 4897835 | Gaskill et al. | Jan 1990 | A |
| 4897870 | Golden | Jan 1990 | A |
| 4959849 | Bhusri | Sep 1990 | A |
| 4972461 | Brown et al. | Nov 1990 | A |
| 5008929 | Olsen et al. | Apr 1991 | A |
| 5150357 | Hopner et al. | Sep 1992 | A |
| 5291481 | Doshi et al. | Mar 1994 | A |
| 5315580 | Phaal | May 1994 | A |
| 5341608 | Mains, Jr. | Aug 1994 | A |
| 5402474 | Miller et al. | Mar 1995 | A |
| 5426688 | Anand | Jun 1995 | A |
| 5430709 | Galloway | Jul 1995 | A |
| 5438570 | Karras et al. | Aug 1995 | A |
| 5457692 | Ishinabe et al. | Oct 1995 | A |
| 5457729 | Hamann et al. | Oct 1995 | A |
| 5473596 | Garafola et al. | Dec 1995 | A |
| 5475732 | Pester, III | Dec 1995 | A |
| 5506893 | Buscher et al. | Apr 1996 | A |
| 5521902 | Ferguson | May 1996 | A |
| 5539804 | Hong et al. | Jul 1996 | A |
| 5546398 | Tucker et al. | Aug 1996 | A |
| 5550914 | Clarke et al. | Aug 1996 | A |
| 5572579 | Orriss et al. | Nov 1996 | A |
| 5579371 | Aridas et al. | Nov 1996 | A |
| 5583926 | Venier et al. | Dec 1996 | A |
| 5586177 | Farriss et al. | Dec 1996 | A |
| 5592530 | Brockman et al. | Jan 1997 | A |
| 5598464 | Hess et al. | Jan 1997 | A |
| 5602909 | Carkner et al. | Feb 1997 | A |
| 5606600 | Elliott et al. | Feb 1997 | A |
| 5610969 | McHenry et al. | Mar 1997 | A |
| 5610977 | Williams et al. | Mar 1997 | A |
| 5625681 | Butler, II | Apr 1997 | A |
| 5671225 | Hooper et al. | Sep 1997 | A |
| 5689555 | Sonnenberg | Nov 1997 | A |
| 5696816 | Sonnenberg | Dec 1997 | A |
| 5711011 | Urs et al. | Jan 1998 | A |
| 5712908 | Brinkman et al. | Jan 1998 | A |
| 5740239 | Bhagat et al. | Apr 1998 | A |
| 5757895 | Aridas et al. | May 1998 | A |
| 5764745 | Chan et al. | Jun 1998 | A |
| 5768352 | Elliott et al. | Jun 1998 | A |
| 5768358 | Venier et al. | Jun 1998 | A |
| 5771284 | Sonnenberg | Jun 1998 | A |
| 5774532 | Gottlieb et al. | Jun 1998 | A |
| 5784443 | Chapman et al. | Jul 1998 | A |
| 5796813 | Sonnenberg | Aug 1998 | A |
| 5812639 | Bartholomew et al. | Sep 1998 | A |
| 5838683 | Corley et al. | Nov 1998 | A |
| 5867558 | Swanson | Feb 1999 | A |
| 5903726 | Donovan et al. | May 1999 | A |
| 5949871 | Kabay et al. | Sep 1999 | A |
| 5999525 | Krishnaswamy et al. | Dec 1999 | A |
| 6006098 | Rathnasabapathy et al. | Dec 1999 | A |
| 6009160 | Sonnenberg | Dec 1999 | A |
| 6021126 | White et al. | Feb 2000 | A |
| 6028914 | Lin et al. | Feb 2000 | A |
| 6061432 | Wallace et al. | May 2000 | A |
| 6091957 | Larkins et al. | Jul 2000 | A |
| 6091959 | Souissi et al. | Jul 2000 | A |
| 6094573 | Heinonen et al. | Jul 2000 | A |
| 6097719 | Benash et al. | Aug 2000 | A |
| 6097960 | Rathnasabapathy et al. | Aug 2000 | A |
| 6108332 | Kasiviswanathan | Aug 2000 | A |
| 6108782 | Fletcher et al. | Aug 2000 | A |
| 6111946 | O'Brien | Aug 2000 | A |
| 6115754 | Landgren | Sep 2000 | A |
| 6119014 | Alperovich et al. | Sep 2000 | A |
| 6122510 | Granberg | Sep 2000 | A |
| 6128304 | Gardell et al. | Oct 2000 | A |
| 6128377 | Sonnenberg | Oct 2000 | A |
| 6134307 | Brouckman et al. | Oct 2000 | A |
| 6134314 | Dougherty et al. | Oct 2000 | A |
| 6134316 | Kallioniemi et al. | Oct 2000 | A |
| 6134432 | Holmes et al. | Oct 2000 | A |
| 6134618 | Hebert | Oct 2000 | A |
| 6137869 | Voit et al. | Oct 2000 | A |
| 6138023 | Agarwal et al. | Oct 2000 | A |
| 6181937 | Joensuu | Jan 2001 | B1 |
| 6182086 | Lomet et al. | Jan 2001 | B1 |
| 6188752 | Lesley | Feb 2001 | B1 |
| 6215790 | Voit et al. | Apr 2001 | B1 |
| 6219551 | Hentiläet al. | Apr 2001 | B1 |
| 6249572 | Brockman et al. | Jun 2001 | B1 |
| 6252952 | Kung et al. | Jun 2001 | B1 |
| 6272136 | Lin et al. | Aug 2001 | B1 |
| 6301609 | Aravamudan et al. | Oct 2001 | B1 |
| 6304565 | Ramamurthy | Oct 2001 | B1 |
| 6321268 | Dillon et al. | Nov 2001 | B1 |
| 6324183 | Miller et al. | Nov 2001 | B1 |
| 6333931 | LaPier et al. | Dec 2001 | B1 |
| 6359979 | Wang et al. | Mar 2002 | B1 |
| 6363411 | Dugan et al. | Mar 2002 | B1 |
| 6373930 | McConnell et al. | Apr 2002 | B1 |
| 6393269 | Hartmaier et al. | May 2002 | B1 |
| 6424621 | Ramaswamy et al. | Jul 2002 | B1 |
| 6430176 | Christie, IV | Aug 2002 | B1 |
| 6434155 | Jones et al. | Aug 2002 | B1 |
| 6438223 | Eskafi et al. | Aug 2002 | B1 |
| 6446127 | Schuster et al. | Sep 2002 | B1 |
| 6453034 | Donovan et al. | Sep 2002 | B1 |
| 6453158 | Donovan et al. | Sep 2002 | B2 |
| 6456708 | Copley et al. | Sep 2002 | B1 |
| 6466796 | Jacobson et al. | Oct 2002 | B1 |
| 6470179 | Chow et al. | Oct 2002 | B1 |
| 6480588 | Donovan | Nov 2002 | B1 |
| 6496690 | Cobo et al. | Dec 2002 | B1 |
| 6510164 | Ramaswamy et al. | Jan 2003 | B1 |
| 6515997 | Feltner et al. | Feb 2003 | B1 |
| 6516194 | Hanson | Feb 2003 | B2 |
| 6535727 | Abbasi et al. | Mar 2003 | B1 |
| 6564261 | Gudjonsson et al. | May 2003 | B1 |
| 6571094 | Begeja et al. | May 2003 | B1 |
| 6574481 | Rathnasabapathy et al. | Jun 2003 | B1 |
| 6584183 | Manto | Jun 2003 | B2 |
| 6611516 | Pirkola et al. | Aug 2003 | B1 |
| 6633764 | Garcia | Oct 2003 | B1 |
| 6718178 | Sladek et al. | Apr 2004 | B1 |
| 6731741 | Fourcand et al. | May 2004 | B1 |
| 6747970 | Lamb et al. | Jun 2004 | B1 |
| 6760343 | Krishnamurthy et al. | Jul 2004 | B1 |
| 6795532 | Gross et al. | Sep 2004 | B1 |
| 6836477 | West et al. | Dec 2004 | B1 |
| 6865266 | Pershan | Mar 2005 | B1 |
| 6917612 | Foti et al. | Jul 2005 | B2 |
| 6944666 | Belkin | Sep 2005 | B2 |
| 6963583 | Foti | Nov 2005 | B1 |
| 6968052 | Wullert, II | Nov 2005 | B2 |
| 7010114 | Stahl et al. | Mar 2006 | B2 |
| 7058036 | Yu et al. | Jun 2006 | B1 |
| 7079853 | Rathnasabapathy et al. | Jul 2006 | B2 |
| 7254391 | McCann | Aug 2007 | B2 |
| 7260207 | Marsico | Aug 2007 | B2 |
| 7864752 | Bennett et al. | Jan 2011 | B1 |
| 20010031641 | Ung et al. | Oct 2001 | A1 |
| 20010034224 | McDowell et al. | Oct 2001 | A1 |
| 20010040957 | McCann et al. | Nov 2001 | A1 |
| 20020029189 | Titus et al. | Mar 2002 | A1 |
| 20020048360 | Zambre et al. | Apr 2002 | A1 |
| 20020058507 | Valentine et al. | May 2002 | A1 |
| 20020111153 | Hartmaier et al. | Aug 2002 | A1 |
| 20020136206 | Gallant et al. | Sep 2002 | A1 |
| 20020150079 | Zabawskyj et al. | Oct 2002 | A1 |
| 20030026289 | Mukherjee et al. | Feb 2003 | A1 |
| 20030031160 | Gibson Ang et al. | Feb 2003 | A1 |
| 20030037108 | Peiffer et al. | Feb 2003 | A1 |
| 20030177281 | McQuillan et al. | Sep 2003 | A1 |
| 20030203740 | Bahl et al. | Oct 2003 | A1 |
| 20040003037 | Fujimoto et al. | Jan 2004 | A1 |
| 20040024894 | Osman et al. | Feb 2004 | A1 |
| 20040047341 | Staack et al. | Mar 2004 | A1 |
| 20040121761 | Tripathy et al. | Jun 2004 | A1 |
| 20040153506 | Ito et al. | Aug 2004 | A1 |
| 20040155757 | Litwin et al. | Aug 2004 | A1 |
| 20040264671 | Lamberton et al. | Dec 2004 | A1 |
| 20050027867 | Mueller et al. | Feb 2005 | A1 |
| 20050053223 | Bedingfield | Mar 2005 | A1 |
| 20050070310 | Caspi et al. | Mar 2005 | A1 |
| 20050091157 | Suzuki et al. | Apr 2005 | A1 |
| 20050111632 | Caputo et al. | May 2005 | A1 |
| 20050113095 | Allison | May 2005 | A1 |
| 20050201362 | Klein et al. | Sep 2005 | A1 |
| 20050202836 | Schaedler et al. | Sep 2005 | A1 |
| 20050213740 | Williams et al. | Sep 2005 | A1 |
| 20060029045 | Kobayashi et al. | Feb 2006 | A1 |
| 20060077965 | Garcia-Martin et al. | Apr 2006 | A1 |
| 20060105766 | Azada et al. | May 2006 | A1 |
| 20060177012 | Forney et al. | Aug 2006 | A1 |
| 20060210027 | Kafri | Sep 2006 | A1 |
| 20060244744 | Kandori et al. | Nov 2006 | A1 |
| 20100202446 | McCann et al. | Aug 2010 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 088 639 | Sep 1983 | EP |
| 0 212 654 | May 1987 | EP |
| 0 258 654 | Mar 1988 | EP |
| 0 264 023 | Apr 1988 | EP |
| WO 0016583 | Mar 2000 | EP |
| 1 100 279 | May 2001 | EP |
| 2 382 267 | May 2003 | GB |
| 58-215164 | Dec 1983 | JP |
| 62-200859 | Sep 1987 | JP |
| 1020030025024 | Mar 2003 | KR |
| WO 8401073 | Mar 1984 | WO |
| WO 8603915 | Jul 1986 | WO |
| WO 8800419 | Jan 1988 | WO |
| WO 9733441 | Sep 1997 | WO |
| WO 9914910 | Mar 1999 | WO |
| WO 0022543 | Apr 2000 | WO |
| WO 0035155 | Jun 2000 | WO |
| WO 0120920 | Mar 2001 | WO |
| WO 0156308 | Aug 2001 | WO |
| WO 2004084530 | Sep 2004 | WO |
| WO 2005083995 | Sep 2005 | WO |
| WO 2006031678 | Mar 2006 | WO |
| WO 2008103371 | Aug 2008 | WO |
| Entry |
|---|
| “BICC Architecture and BICC Protocol Details,” Tekelec, p. 28-41 (2008). |
| “BICC Signaling Router (BSR) Reference Architecture (WP005274),” Tekelec, p. 2-91 (2008). |
| “GPRS Tunneling Protocol (GTP),” Trillium, Continuous Computing, pp. 1-3 (Copyright 2007). |
| “Gateway Control Protocol: Version 3,” Series H: Audiovisual and Multimedia Systems; Infrastructure of Audiovisual Services—Communication Procedures, ITU-T H.248.1 (Sep. 2005). |
| Faltstrom et al., “The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM),” www.ietf.org, pp. 1-16 (Apr. 2004). |
| “Interworking Between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol or ISDN User Part,” ITU-T Q.1912.5, p. 1-101 (Mar. 2004). |
| “Services and Protocols for Advanced Networks (SPAN); Bearer Independent Call Control (BICC) Capability Set 2 (CS2); Protocol Specification,” ETSI EN 302 213 V1.1.2 (Jan. 2004). |
| “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Technology Mapping; Implementation of TIPHON Architecture Using BICC,” ETSI TS 102 228 V4.1.1 (Nov. 2003). |
| Camarillo et al., “Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP),” Network Working Group, RFC 3578 (Aug. 2003). |
| “Series Q: Switching and Signalling; Broadband ISDN—Signalling ATM Adaptation Layer (SAAL); Signalling Transport converter on SCTP,” ITU-T Q.2150.3 (Dec. 2002). |
| “Bearer Independent Call Bearer Control Protocol,” ITU-T Q.1950, p. 1-96 (Dec. 2002). |
| Camarillo et al., “Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping,” Network Working Group, RFC 3398 (Dec. 2002). |
| Vemuri et al., “Session Initiation Protocol for Telephones (SIP-T): Context and Architectures,” Network Working Group, RFC 3372 (Sep. 2002). |
| Chang, “BICC Extension of SIP in Inter-Network Configuration,” Internet Engineering Task Force, draft-chang-sipping-bicc-network-00.txt, pp. 1-17 (Mar. 2002). |
| Multiservice Switching Forum, “Implementation Agreement or BICC,” MSF-IA-BICC.001-FINAL (Feb. 2002). |
| Marshall et al., “SIP Extensions for Supporting Distributed Call State,” SIP Working Group, Internet Draft, pp. 1-12 (Aug. 2001). |
| “Searles Q: Switching and Signalling; Specification of Signalling Related to Bearer Independent. Call Control (BICC); Bearer Independent Call Control Protocol (Capability Set 2): Basic Call Procedures,” ITU-T Q1902.4 (Jul. 2001). |
| “Bearer Independent Call Control Protocol (Capability Set 2) and Signalling System No. 7 ISDN User Part: Formats and Codes,” ITU-T Q.1902.3, p. 1-141 (Jul. 2001). |
| “Bearer Independent Call Control Protocol (Capability Set 2) and Signaling System No. 7 ISDN user part: General Functions of Messages and Parameters,” ITU-T Q.1902.2 (Jul. 2001). |
| “Bearer Independent Call Control Protocol (Capability Set 2): Functional Description,” ITU-T Q.1902.1, p. 1-23 (Jul. 2001). |
| “Series Q: Switching and Signalling, Specification of Signalling Related to Bearer Independent Call Control (BICC); BICC Bearer Control Tunnelling Protocol,” ITU-T Q.1990 (Jul. 2001). |
| “Series Q: Switching and Signalling; Specifications of Signalling System No. 7—ISDN User Part; Signalling System No. 7—Application Transport Mechanism: Bearer Independent Call Control (BICC); Amendment 1: Bearer Independent Call Control Capability Set 2,” ITU-T Q.765.5 (Jul. 2001). |
| “Series Q: Switching and Signalling; Specifications of Signalling Related to Bearer Independent Call Control (BICC): Interworking Between Signalling System No. 7 ISDN User Part and the Bearer Independent Call Control Protocol,” ITU-T Q1912.1 (Jul. 2001). |
| “Series Q: Switching and Signalling; Interworking Between Selected Signalling Systems (PSTN Access, DSS1, C5, R1, R2, TUP) and the Bearer Independent Call Control Protocol,” ITU-T Q1912.2 (Jul. 2001). |
| “Signalling Transport Converter on MTP3 and MTP3b,” ITU-T Q.2150.1 (May 2001). |
| “Generic Signalling Transport Service,” ITU-T Q.2150.0 (May 2001). |
| “ITU-Q1970: Draft New ITU-T Recommendation Q.1970 BICC IP Bearer Control Protocol,” Network Dictionary (2001). |
| “Gateway Control Protocol: Transport Over Stream Control Transmission Protocol (SCTP),” Series H: Audiovisual and Multimedia Systems; Infrastructure of Audiovisual Services—Communication Procedures, H.248.4 (Nov. 2000). |
| “Bearer Independent Call Control Protocol,” ITU-T Q.1901 (Jun. 2000). |
| Sugano et al., “Presence Information Data Format for IMPP,” Internet draft, draft-ietf-impp-pidf-01.text, Network Working Group, p. 1-17, (Mar. 10, 2000). |
| “Signalling System No. 7—ISDN User Part Enhancements for the Support of Number Portability,” ITU-T Q.769.1 (Dec. 1999). |
| “Signalling System No. 7—ISDN User Part Formats and Codes,” ITU-T Q.763 (Dec. 1999). |
| “Signalling System No. 7—ISDN User Part General Functions of Messages and Signals,” ITU-T Q.762 (Dec. 1999). |
| “Signalling System No. 7—ISDN User Part Functional Description,” ITU-T Q.761 (Dec. 1999). |
| “Series Q: Switching and Signalling; Specifications of Signalling System No. 7—ISDN Supplementary Services; ISDN User Part Supplementary Services,” ITU-T Q.730 (Dec. 1999). |
| Liao et al., “SS7-TCAP/IP Interworking,” Internet Engineering Task Force, pp. 1-14 (Mar. 1999). |
| De Ment, “The Evolution of Signaling,” NMS Communications, p. 1-28 (Publication Date Unknown). |
| “Mobile Wireless Overview,” Cisco IOS Mobile Wireless Configuration Guide, pp. MWC-1-MWC-8 (Publication Date Unknown). |
| Jennings et al., “Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR),” The Internet Society (Apr. 2006). |
| Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US08/02220 (Jul. 8, 2008). |
| Non-Final Official Action for U.S. Appl. No. 12/689,702 (Feb. 2, 2012). |
| First Office Action for Chinese Patent Application No. 200880012885.X (Jan. 11, 2012). |
| Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2010/021374 (Aug. 19, 2010). |
| Applicant-Initiated Interview Summary for U.S. Appl. No. 12/689,702 (Jun. 5, 2012). |
| Decision of Rejection for Chinese Patent Application No. 200880012885.X (May 6, 2013). |
| Second Office Action for Chinese Application No. 200880012885.X (Sep. 27, 2012). |
| Extended European Search Report for European Application No. 08725814.1 (Sep. 23, 2013). |
| Final Office Action for U.S. Appl. No. 12/689,702 (Aug. 15, 2013). |
| Number | Date | Country | |
|---|---|---|---|
| 20080205603 A1 | Aug 2008 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60903185 | Feb 2007 | US |
