WO2010060082A2 - Systèmes, procédés et supports lisibles par ordinateur pour assurer un service sans frais dans un réseau de télécommunications - Google Patents

Systèmes, procédés et supports lisibles par ordinateur pour assurer un service sans frais dans un réseau de télécommunications Download PDF

Info

Publication number
WO2010060082A2
WO2010060082A2 PCT/US2009/065733 US2009065733W WO2010060082A2 WO 2010060082 A2 WO2010060082 A2 WO 2010060082A2 US 2009065733 W US2009065733 W US 2009065733W WO 2010060082 A2 WO2010060082 A2 WO 2010060082A2
Authority
WO
WIPO (PCT)
Prior art keywords
message
toll
free
signaling
query
Prior art date
Application number
PCT/US2009/065733
Other languages
English (en)
Other versions
WO2010060082A3 (fr
Inventor
Rohini Vijay Marathe
Devesh Agarwal
Ranghavendra Gopala Rao
Peter Joseph Marsico
Original Assignee
Tekelec
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tekelec filed Critical Tekelec
Publication of WO2010060082A2 publication Critical patent/WO2010060082A2/fr
Publication of WO2010060082A3 publication Critical patent/WO2010060082A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/4228—Systems providing special services or facilities to subscribers in networks
    • H04M3/42306—Number translation services, e.g. premium-rate, freephone or vanity number services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/08—Metering calls to called party, i.e. B-party charged for the communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/63—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the content carried by the session initiation protocol [SIP] messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8292—Charging for signaling or unsuccessful connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0025—Provisions for signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0029—Provisions for intelligent networking
    • H04Q3/005—Personal communication services, e.g. provisions for portability of subscriber numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2207/00—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place
    • H04M2207/12—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place intelligent networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/62—Called party billing, e.g. reverse billing, freephone, collect call, 0800 or 0900

Definitions

  • the subject matter described herein relates to providing a service in a telecommunications network. More particularly, the subject matter described herein relates to systems, methods, and computer readable media for providing toll-free service in a telecommunications network.
  • a toll-free number is a telephone number in which the cost of the call is charged to the called party rather than to the calling party.
  • telephone numbers are of the form NPA-NXX-YYYY, where NPA is the numbering plan area code, roughly corresponding to a particular geographical area, and NXX is the exchange, which identifies a physical switching facility, called a central office (CO).
  • CO central office
  • the remaining digits, YYYY identify a line card within the CO.
  • a toll-free number may have an "8XX" area code (e.g., 800, 877, 866, etc.), that does not correspond to any geographical location of the called party, and thus cannot be used by itself to determine the destination of the call or how it should be routed. For this reason, switches in conventional telecommunications networks that provide toll free service must send a query to a toll-free database to determine the true destination of the toll-free called party. For example, a CO in a signaling system number 7 (SS7) network may issue a transaction capabilities application part (TCAP) query to a service control point (SCP) that maintains a toll-free database.
  • TCAP transaction capabilities application part
  • SCP service control point
  • a query to a toll-free database is herein referred to as a "toll-free query.”
  • toll-free (TF) service is provided by the switch, which issues a toll-free query in response to detecting an attempt to place a call to a toll-free called party.
  • the switch must be configured or provisioned to perform the additional steps needed to provide toll-free service. For example, when the switch detects a call attempt, the switch must additionally determine whether the called party is a toll-free number, and if so, issue a toll-free query to a toll-free database that maps the toll-free number to a directory number (DN), and receive the DN associated with the toll-free number. The switch can then route the call setup message accordingly.
  • DN directory number
  • a subscriber may change location and/or service provider but still keep the same directory number.
  • a subscriber may have been moved from the original switch that served the subscriber, called the donor switch, to a new switch, called the recipient switch.
  • the switch must be additionally configured to perform a NP lookup using the first DN, i.e., the DN that was returned by the toll-free query. If the directory number associated with the toll-free number has been ported, the NP query may return a second DN, a routing number (RN) of the recipient switch, or both.
  • RN routing number
  • a telecommunications network may support wireline subscribers, wireless subscribers, or both.
  • a “wireline subscriber” is a subscriber to or user of a network who accesses the network over a physical connection, such as a telephone line, local loop, cable modem, or other physical medium including wire or optical fiber.
  • a “wireless subscriber” is a subscriber to or user of a network who accesses the network over a wireless connection, such as via a mobile phone, wireless LAN, wireless modem, etc.
  • a wireless subscriber may also be referred to as a "mobile subscriber”.
  • the switch must also be configured to perform a mobility management query using available information, e.g., the first DN, the second DN, or the RN.
  • a mobility management query may return information identifying the mobile switching center that is currently serving the mobile subscriber.
  • the subject matter described herein includes a method for providing toll-free service in a telecommunications network.
  • the method includes, at a signaling node that includes at least one processor: receiving a first signaling message that includes a toll-free called party number, where the first signaling message is a non-TCAP call setup message, a mobility management query, a number portability query, or an E.164 number query; determining a directory number associated with the toll-free called party number; and sending the first signaling message or a second signaling message, the sent message including the directory number, the routing information associated with the directory number, or both.
  • the subject matter described herein includes a signaling node for providing toll-free service in a telecommunications network.
  • the node includes a communications interface for receiving a first signaling message that includes a toll-free called party number, where the first signaling message is a non-TCAP call setup message, a mobility management query, a number portability query, or an E.164 number query.
  • the node includes a toll-free service module (TFSM), operatively associated with the signaling node, for determining a directory number associated with the toll-free called party number for sending the first signaling message or a second signaling message, the sent message including the directory number, the routing information associated with the directory number, or both.
  • TFSM toll-free service module
  • the subject matter described herein includes a system for providing toll-free service in a telecommunications network.
  • the system includes a signaling node for receiving a first signaling message that includes a toll-free called party number, where the first signaling message is a non-TCAP call setup message, a mobility management query, a number portability query, or an E.164 number query.
  • the system includes a toll-free service module (TFSM) for determining a directory number associated with the toll-free called party number and for sending the first signaling message or a second signaling message, the sent message including the directory number, the routing information associated with the directory number, or both.
  • TFSM toll-free service module
  • the subject matter described herein for providing toll-free service in a telecommunications network may be implemented in hardware, software, firmware, or any combination thereof.
  • the terms “function” or “module” as used herein refer to hardware, software, and/or firmware for implementing the feature being described.
  • the subject matter described herein may be implemented using a computer readable medium having stored thereon computer executable instructions that when executed by the processor of a computer perform blocks.
  • Exemplary computer readable media suitable for implementing the subject matter described herein include non-transitory computer-readable media, such as disk memory devices, chip memory devices, programmable logic devices, and application specific integrated circuits.
  • 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.
  • Figure 1 is a block diagram illustrating an exemplary system for providing toll-free service according to an embodiment of the subject matter described herein;
  • Figure 2 is a flow chart illustrating an exemplary process for providing toll-free service in a telecommunications network according to an embodiment of the subject matter described herein;
  • Figure 3 is a flow chart illustrating in more detail an exemplary process for providing toll-free service in a telecommunications network according to an embodiment of the subject matter described herein;
  • Figure 4 is a block diagram illustrating an exemplary signaling message routing node for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein;
  • Figure 5A is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, including exemplary signaling messages that may be generated during a mobile-to- wireline call setup in a network that does not support number portability;
  • Figure 5B is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, including exemplary signaling messages that may be generated during a mobile-to- mobile call setup in a network that does not support number portability;
  • Figure 5C is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, in which the toll- free database is a component within the signaling message routing node;
  • Figure 5D is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, in which the directory number and routing information are concatenated together and returned in a single field or parameter;
  • Figure 5E is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, including exemplary signaling messages that may be generated during a mobile-to- wireline call setup in a network that supports number portability;
  • Figure 5F is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, including exemplary signaling messages that may be generated during a mobile-to- mobile call setup in a network that supports number portability;
  • Figure 6 is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, in which the identity of the switch that is serving the calling mobile subscriber is provided as part of the toll- free number lookup;
  • Figure 7 A is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, including exemplary signaling messages that may be generated during a wireline-to- wireline call setup in a network in which supports number portability;
  • Figure 7B is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, where the number portability database is located remotely from the signaling message routing node;
  • Figure 7C is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, where the toll-free database and the number portability database are components of the signaling message routing node;
  • Figure 8A is a block diagram illustrating an exemplary system for providing triggerless toll-free service with release in a telecommunications network according to another embodiment of the subject matter described herein, including exemplary signaling messages that may be generated during a mobile-originated call setup;
  • Figure 8B is a block diagram illustrating an exemplary system for providing triggerless toll-free service with release in a telecommunications network according to another embodiment of the subject matter described herein, where the network supports number portability;
  • Figure 8C is a block diagram illustrating an exemplary system for providing triggerless toll-free service with release in a telecommunications network according to another embodiment of the subject matter described herein, where the number portability database is located remotely from the signaling message routing node;
  • Figure 9A is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, including exemplary signaling messages that may be generated in a system that supports number portability;
  • Figure 9B is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, including exemplary signaling messages that may be generated in a system that does not support number portability;
  • Figure 9C is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, including signaling messages that may be generated in a system that supports mobile subscribers but does not support number portability;
  • Figure 9D is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein, including exemplary signaling messages that may be generated in a system that supports mobile subscribers and also supports number portability;
  • Figure 10A is a block diagram illustrating an exemplary system for providing triggerless toll-free service with release in a telecommunications network according to another embodiment of the subject matter described herein, using ENUM queries to provide triggered toll-free service
  • Figure 10B is a block diagram illustrating an exemplary system for providing triggerless toll-free service with redirect in a telecommunications network using SIP protocol according to another embodiment of the subject matter described herein;
  • Figure 10C is a block diagram illustrating an exemplary system for providing triggerless toll-free service without release in a telecommunications network using SIP protocol according to another embodiment of the subject matter described herein.
  • FIG. 1 is a block diagram illustrating an exemplary system for providing toll-free service according to an embodiment of the subject matter described herein.
  • telecommunications network 100 includes a first switch (S1) 102, via which a subscriber 104 accesses network 100.
  • S1 102 is the switch that services a calling party, such as subscriber 104
  • S1 102 may also be referred to as the "originating switch”.
  • S1 102 may be a service switching point (SSP), such as an end office (EO) for servicing wireline subscribers.
  • SSP service switching point
  • EO end office
  • S1 102 may be a mobile switching center (MSC) for servicing wireless or mobile subscribers, a tandem office (TO), a call session control function (CSCF), a Softswitch (SS), or any other type of switch in a telecommunications network.
  • MSC mobile switching center
  • TO tandem office
  • CSCF call session control function
  • SS Softswitch
  • Network 100 may include a signaling node 106, such as a signaling message routing node, for routing signaling messages within network 100.
  • signaling node 106 is a signal transfer point (STP).
  • the signaling message routing node may be a signaling gateway (SGW), a Softswitch (SS), a media gateway controller (MGC), a media gateway (MGW), or other entity for routing signaling messages within network 100.
  • SGW signaling gateway
  • SS Softswitch
  • MSC media gateway controller
  • MGW media gateway
  • Network 100 may include a toll-free database (TFDB) 108, which maps toll-free numbers, such as 1-8XX numbers in the United States, to directory number.
  • TFDB toll-free database
  • Table 1 An example toll-free database is shown in Table 1 , below. Each row in Table 1 represents an entry in TFDB 108, and each entry maps a toll-free number (TFN), shown in the left column, to a DN, shown in the right column.
  • a directory number may also be referred to as a "B-party number”. Referring to Table 1 , the toll-free number (800) 345-0393 would be mapped to the directory number (919) 469-2255.
  • network 100 may support number portability, ln the embodiment illustrated in Figure 1 , network 100 may include a number portability database (NPDB) 110, which maps a ported subscriber's directory number (DN) to the routing number (RN) of the recipient switch.
  • NPDB number portability database
  • network 100 may support mobile subscribers.
  • network 100 may include a home location register (HLR) 112 for maintaining information for each mobile subscriber, including information about the current location of a roaming mobile subscriber.
  • HLR home location register
  • system 100 may include a toll-free service module (TFSM) 114, for performing toll-free processing on behalf of S1 102.
  • TFSM toll-free service module
  • system 100 may include a toll-free service module (TFSM) 114, for performing toll-free processing on behalf of S1 102.
  • TFSM 114 is a component of signaling node
  • TFSM 114 may be located remotely from signaling node 106.
  • the TFSM 114 functions may be performed in whole or in part by a service capabilities interaction manager function, such the TekSCIM ® product, available from Tekelec of Morrisville, North Carolina.
  • a service capabilities interaction manager is described in commonly-assigned U.S. Patent Application Serial No. 12/106,807, entitled “Systems, methods, and computer program products for providing service interaction and mediation in a communications network", filed on April 21 , 2008, the disclosure of which is incorporated by reference herein in its entirety.
  • Another implementation of a service capabilities interaction manager is described in commonly-assigned U.S. Patent Application Serial No. 12/106,869, entitled “Methods, systems, and computer program products for providing fault-tolerant service interaction and mediation function in a communications network", also filed on April 21 , 2008, the disclosure of which is incorporated by reference herein in its entirety.
  • system 100 may include a routing database 116 for mapping directory numbers to routing numbers.
  • An example routing database is shown in Table 2, below. Each row of Table 2 represents an entry in routing database 116, and each entry maps a range of directory numbers, shown in the left column, to routing information, shown in the right column.
  • the routing information may be a routing number (RN) 1 a local routing number (LRN), a mobile switch routing number (MSRN), or other type of routing information.
  • RN routing number
  • LRN local routing number
  • MSRN mobile switch routing number
  • routing database 116 may be internal or external to signaling node 106.
  • system 100 includes a second switch (S2) 118, which serves toll-free called party 120.
  • S2 118 When a switch, such as S2 118, services a called party, such as called party 120, that switch may also be referred to as the "terminating switch".
  • S2 118 may be an
  • System 100 may also include other types of databases.
  • system 100 includes an E.164 (ENUM) database 122.
  • ENUM E.164
  • the system embodied in Figure 1 significantly differs from conventional systems.
  • the burden of performing the toll-free query rests on an originating switch, such as S1 102
  • the toll-free service is provided instead by a signaling node, such as signaling node 106.
  • This arrangement has several distinct benefits.
  • signaling node 106 may perform both triggered and triggerless toll-free lookups.
  • a "triggered" operation is one that is explicitly initiated by an end office or other switch, which usually initiates the operation via an explicit request or query.
  • a "triggerless” operation by comparison, is triggered by some mechanism other than an explicit request for the operation.
  • a triggerless operation may be initiated as a result of detection of a specific event, by interception of a type or class of message, etc.
  • Figures 5A through 7C and 10A illustrate triggered embodiments, while Figures 8A through 9D, 10B, and 10C illustrate triggerless embodiments.
  • S1 102 in network 100 may reuse existing triggers to perform toll-free operations.
  • S1 102 may be configured so that calls to a toll-free number are treated the same way that calls to a mobile subscriber are treated, e.g., S1 102 issues an SRI query including the TFN.
  • S1 102 may be configured so that calls to a toll-free number are treated the same way that calls to potentially ported subscribers are treated, e.g., S1 102 issues a NP query including the TFN.
  • an S1 102 can implement toll- free services by using (or reusing) existing protocols, without having to add support for other protocols.
  • the term "native protocol" refers to a protocol which the switch already supports and uses for non-toll-free services.
  • Various embodiments may use various native protocols.
  • Figures 5A through 6 illustrate embodiments which reuse a mobility management protocol to provide toll-free service.
  • Figures 7A through 7C illustrate embodiments which reuse a number portability protocol to provide toll-free service.
  • signaling node 106 is configured to recognize the SRI query (or NP query, as the case may be) as a toll-free query and respond appropriately.
  • Some legacy networks may have switches that do not support toll- free triggers, or that do not support the additional protocols needed to access TFDB 108.
  • toll-free service could be provided triggerlessly by signaling node 106, obviating the need to perform expensive upgrades to switches in the legacy network.
  • FIG. 2 is a flow chart illustrating an exemplary process for providing toll-free service in a telecommunications network according to an embodiment of the subject matter described herein.
  • a first signaling message is received from a switch, the first signaling message including a toll-free called party number, abbreviated as "TFN" ( Figure 1 , message 1).
  • the first signaling message may be a non-TCAP call setup message, a mobility management query, a number portability query, or an E.164 number query.
  • S1 102 may send a non-TCAP call setup message (Figure 1 , message 1), such as an ISUP initial address message (IAM), an ISUP subsequent address message (SAM), a bearer- independent call control (BICC) message, or a SIP INVITE message, that includes the toll-free called party number.
  • a non-TCAP call setup message such as an ISUP initial address message (IAM), an ISUP subsequent address message (SAM), a bearer- independent call control (BICC) message, or a SIP INVITE message, that includes the toll-free called party number.
  • calling subscriber 104 may be a mobile subscriber and S1 102 may be a mobile switching center (MSC), which may issue a mobility management message, such as a mobile application part (MAP) send routing information (SRI) message, a MAP send routing information for short message (SRI_SM) message, an anytime interrogation (ATI) message, or an ANSI-41 location request (LOCREQ) message, that includes the toll-free called party number.
  • MAP mobile application part
  • SRI_SM MAP send routing information for short message
  • ATI anytime interrogation
  • LOCREQ ANSI-41 location request
  • calling subscriber 104 may be a wireline subscriber and S1 102 may be an end office (EO), a central office (CO), a service switching point (SSP), or similar entity, which may issue a call setup message that includes the toll-free called party number.
  • S1 102 may issue a number portability (NP) query that includes the toll-free called party number.
  • EO end office
  • CO central office
  • SSP service switching point
  • NP number portability
  • calling subscriber 104 may be a user agent client (UAC) in a session initiation protocol (SIP) network and S1 102 may be a SIP router, SIP application server (SAS), media gateway (MGW), or similar entity, which may issue SIP INVITE message, an ENUM query, or other message that includes the toll-free called party number.
  • UAC user agent client
  • SIP session initiation protocol
  • SAS SIP application server
  • MGW media gateway
  • a directory number associated with the toll-free called party number is determined.
  • this process may involve issuing a toll-free query (Figure 1 , message 2) to TFDB 108 and receiving a response ( Figure 1 , message 3), issuing a number portability query (Figure 1 , message 4) to NPDB 110 and receiving a response ( Figure 1 , message 5), issuing a mobility management query ( Figure 1 , message 6) to HRL 112 and receiving a response ( Figure 1 , message 7), issuing an ENUM query to ENUM database 122 and receiving a response (messages not shown in Figure 1), or some combination of the above.
  • a toll-free query Figure 1 , message 2
  • the sent message includes the directory number and/or routing information associated with the toll-free called party number.
  • the original message i.e., the first signaling message
  • a new message i.e., the second signaling message
  • a new signaling message may be generated and sent back to the sender of the first message, e.g., the second message may be a response to the first message query.
  • Blocks 202 and 204 will now be described in more detail in Figure 3.
  • Figure 3 is a flow chart illustrating in more detail an exemplary process for providing toll-free service in a telecommunications network according to an embodiment of the subject matter described herein. This process will be described with reference to Figures 1 and 3.
  • Figure 3 illustrates blocks 200, 202 and 204 of Figure 2, with blocks 202 and 204 in particular shown in more detail.
  • Block 202 of Figure 2 is shown as a series of sub-blocks 300, 302, 304, 306, 308, 310, and 312 in Figure 3.
  • Block 204 of Figure 2 is shown as a series of sub-blocks 314, 316, 318, 320, and 322 in Figure 3.
  • S1 102 sends a signaling message containing a toll-free number from calling subscriber 104.
  • S1 102 detects an attempt by calling subscriber 104 to place a call to toll-free called party 120, and in response, sends a signaling message containing the toll-free number to signaling node 106 ( Figure 1 , message 1).
  • this signaling message may take a variety of forms.
  • S1 102 sends a non-TCAP call setup message to signaling node 106.
  • S1 102 issues a NP query, mobility management query, or ENUM query to signaling node 106, the query containing the toll-free number.
  • signaling node 106 forwards the received signaling message to TFSM 114 for processing.
  • the toll-free number is used to perform a toll-free query, which returns a directory number for the toll-free called party.
  • TFSM 114 issues a toll-free query ( Figure 1 , message 2) to TFDB 108, the toll- free query including the toll-free number.
  • TFDB 108 may respond with a directory number (DN 1) for the toll-free number ( Figure 1 , message 3).
  • Example query/response message protocols include, but are not limited to, a transaction capabilities application part (TCAP) protocol, a mobile application part (MAP) protocol, IN/AIN/WIN protocols, a CAMEL protocol, and other suitable protocols.
  • TCAP transaction capabilities application part
  • MAP mobile application part
  • IN/AIN/WIN protocols IN/AIN/WIN protocols
  • CAMEL protocol CAMEL protocol
  • TFSM 114 determines whether a number portability lookup is needed for DN 1. If a number portability lookup is needed, the process moves to block 304, and if not, the process moves to block 306.
  • a number portability query is performed using DN 1 , which may return a routing number that identifies the switch currently serving the subscriber, if the subscriber has been ported to a recipient switch.
  • TFSM 114 issues a NP query ( Figure 1 , message 4) to NPDB 110, the NP query including DN1.
  • NPDB 110 may respond with a routing number, RN, a second directory number, DN2, or both ( Figure 1 , message 5). The process then moves to block 306.
  • TFSM 114 may analyze DN 1 , RN, or DN2 (depending on whether or not an NP query was required) to determine whether the called party is a mobile subscriber. If so, TFSM 114 seeks to determine the current location of the mobile subscriber, toll-free called party 120. If toll-free called party 120 is a mobile subscriber, the process moves to block 308, and if not, the process moves to block 310.
  • a mobility management query such as a send routing information (SRI) query
  • TFSM 114 sends an SRI query ( Figure 1 , message 6) to a network entity, such as HLR 112, that can provide routing information, the SRI query including DN1 , DN2, or RN.
  • An SRI query is a mobile application part (MAP) message that is sent to the subscriber's HLR to request routing information in order to route a call towards a mobile subscriber.
  • the SRI message typically includes information identifying the mobile subscriber, such as the mobile subscriber's directory number.
  • HLR 112 may respond with the address of a visited mobile switching center (VMSC), a mobile station roaming number (MSRN), or other information identifying the mobile switching center that is currently serving the mobile subscriber ( Figure 1 , message 7).
  • VMSC visited mobile switching center
  • MSRN mobile station roaming number
  • TFSM 114 may send a query, such as a message using the DIAMETER protocol, to a home subscriber server (HSS). The process then moves to block 310.
  • TFSM 114 may not yet have routing information for the directory number. This could occur, for example, if it was determined at block 302 that an NP query was not needed and it was determined at block 306 that a mobility management query was not needed. Thus, at block 310 it is determined whether routing information is yet unknown for the DN for the toll- free called party. If routing information is needed, the process moves to block 312; otherwise, the process moves to block 314. At block 312, routing information, such as a routing number, may be determined for DN. In the embodiment illustrated in Figure 1, for example, TFSM 114 queries routing database 116, which may be local or remote to TFSM 114. The process then moves to the series of steps that make up block 204, starting with block 314.
  • TFSM 114 determines whether the toll-free service is triggered or triggerless based on the type of message that was received by signaling node 106: non-TCAP call setup messages will be processed triggerlessly, and the process will move to block 318, but queries, such as NP, mobility management, or ENUM queries, indicate a triggered request, and the process will move to block 316.
  • the triggered process starts at block 316, in which TFSM 114 sends a response message ( Figure 1 , message 8) that includes the directory number, routing information, or both, to S1 102, and the process ends.
  • S1 102 may be configured to treat toll-free numbers as mobile subscriber numbers, in which case S1 102 will send an SRI message to TFSM 114, which will respond by sending an SRI_ACK message back to S1 102.
  • S1 102 may be configured to treat all toll-free numbers as potentially ported numbers, in which case S1 102 will send a NP query to TFSM 114, which will respond by sending an NP response message back to S1 102.
  • S1 102 may be configured to perform an ENUM query on all toll-free numbers, in which case S1 102 will send an ENUM query to TFSM 114, which will respond by sending an ENUM response message back to S1 102.
  • the query message may be addressed to signaling node 106, or it may be addressed to another node, e.g., to NPDB 110, ENUM DB 122, etc., but intercepted by signaling node 106.
  • the signaling message is processed by TFSM 114 in either case.
  • the triggerless process starts at block 318, in which it is determined whether a release is needed, i.e., whether a bearer path has been reserved to the wrong destination and should be released for use by another call. If a release is needed, the process moves to block 320. If a release is not needed, the process moves to block 322.
  • TFSM 114 sends a release message ( Figure 1 , message 8) to S1 102, the release message including the directory number and/or routing information for the toll-free called party number, and the process ends.
  • release message refers to a message sent to an entity, such as a switch, that manages call paths.
  • the message includes information by which the entity may determine that a particular bearer path that has been reserved in anticipation of use by a call is no longer needed.
  • the release message may indicate that the originating switch should attempt to connect the call path via another destination node.
  • SIP REDIRECT message One example of such a message.
  • the release/redirect message may also contain enough information to allow the entity to determine which bearer path should be reserved or which call path should be used instead.
  • TFSM 114 modifies the received message (Figure 1 , message 1) to include the directory number and/or routing information and forwards the modified message to its destination, and the process ends.
  • TFSM 114 may send the modified message ( Figure 1 , message 9) to S2 118, the switch that serves toll- free called party 120.
  • system 100 may be a packet network, in which case there is no reservation of a bearer path
  • signaling node 106 and TFSM 114 may be configured to intercept and detect ISUP IAM, SAM, or BICC messages containing a toll-free called party number.
  • S1 102 will typically reserve a bearer circuit to another network node, herein referred to as the "destination node", as part of the call setup process.
  • S1 102 will typically select the destination node based on the called party number. However, since the called party number received by S1 102 is a toll- free called party number, S1 102 may not have enough information to determine the correct destination node and may need a DN or routing information to determine how to route the signaling message.
  • the actions that a switch in a circuit switched network, such as S1 102, may take when processing a call setup to a toll-free called party number includes, but is not limited to, the following: 1) reserve a bearer circuit that is currently available; 2) reserve whichever bearer circuit has the least amount of traffic at that time; 3) reserve a bearer circuit to a destination node identified as the preferred destination, at least initially, for all toll-free called party calls; 4) reserve a dummy bearer circuit; or 5) reserve no bearer circuit at all.
  • S1 102 may maintain or have access to a list of destination nodes for one or more toll-free numbers, in which case S1 102 may reserve a bearer circuit to what is likely to be the correct destination node. This is not intended to be an exhaustive list, but is intended to illustrate the point that an S1 102 may not be able to rely on a portion of the called party number, such as the area code, to help it determine which bearer circuit to reserve, leading to an increased likelihood that S1 102 guessed incorrectly.
  • S1 102 does guess incorrectly, for example, if S1 102 reserves a trunk circuit to the wrong switch (S3), not shown in Figure 2, there are at least two ways to correct the situation.
  • One approach is to keep the bearer path between S1 102 and S3, and simply create a new bearer path between S3 and the correct destination, S2 118. This first approach is inefficient, however, because two bearer circuits are occupied - between S1 102 and S3, and between S3 and S2 118 - when only one circuit between S1 102 and S2 118 would be sufficient.
  • Another approach is to dismantle the bearer path between S1 102 and S3 and establish a new path between S1 102 and S2 118.
  • release messages such as the ISUP REL message.
  • signaling node 106 may issue an ISUP REL message ( Figure 1 , message 8) to S1 102 containing routing information RN.
  • S1 102 may release the bearer circuit that it had reserved and reserve another bearer circuit between itself and the switch identified by RN.
  • the SIP REDIRECT message could be issued by a SIP node, for example, and be converted into an ISUP REL message at a signaling gateway.
  • Other release messages are contemplated.
  • TFSM 118 may determine, at block 318, that a release is not necessary and may send the second signaling message ( Figure 1 , message 9) on toward the destination switch S2 118.
  • This message may be a new call setup message or it may be the original message, i.e., Figure 1 , message 1 , that has been modified to include the DN and/or RN information associated with the toll-free called subscriber.
  • the sent message includes the DN and/or routing information associated with the toll-free called party.
  • a routing information associated with the DN is a routing number, but the subject matter described herein is not so limited.
  • a routing number is one form of switch identity or switch address by which the identity or location of S2 118 may be identified for the purpose of correctly routing signaling messages, but other forms of switch identity or address are also contemplated to be within the scope of the subject matter claimed.
  • the routing information may be a routing number (RN), a local routing number (LRN), a mobile station roaming number (MSRN), a signaling system 7 (SS7) network address, a point code and subsystem number (PC/SSN), a visited mobile switching center (MSC) identifier, a network node identifier, a switch identifier, a switch address, a message service center address, a voice mail server identifier, an interactive voice response (IVR) server identifier, a network identifier, a universal resource identifier (URI), a session initiation protocol (SIP) address, an IP address, a domain name, or other information which may be used to route signaling messages.
  • RN routing number
  • LRN local routing number
  • MSRN mobile station roaming number
  • SS7 signaling system 7
  • PC/SSN point code and subsystem number
  • MSC visited mobile switching center
  • URI universal resource identifier
  • SIP session initiation protocol
  • the toll-free service functions are performed by a separate entity, TFSM 114, but the subject matter described herein is not so limited; it will be obvious to one of ordinary skill in the art that the functions attributed to TFSM 114 may be embodied in separate modules within signaling node 106, distributed between signaling node 106 and another network entity, or implemented in other configurations within the scope of the subject matter claimed.
  • FIG. 4 is a block diagram illustrating an exemplary signaling message routing node 106 for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • signaling node 106 may be a signal transfer point (STP).
  • Node 106 includes a link interface module (LIM) 400, a data communications module (DCM) 402, and a database services module (DSM) 404.
  • LIM link interface module
  • DCM data communications module
  • DSM database services module
  • Each module 400, 402, and 404 may include a printed circuit board having one or more processors.
  • each module may include an application processor for performing application level processing of signaling messages, and a communications processor for controlling inter-processor communications via inter-processor communications system 406.
  • Inter-processor communications system 406 may be any suitable mechanism for providing message communication between processing modules 400, 402, and 404.
  • communications system 406 may be a bus, an Ethernet LAN, or any other suitable mechanism for providing communications between processors.
  • LIM 400 includes various functions for sending and receiving signaling messages over SS7 signaling links.
  • LIM 400 includes a message transfer part (MTP) level 1 and 2 function 408, an I/O buffer 410, a gateway screening (GWS) function 412, a discrimination function 414, a distribution function 416, and a routing function 418.
  • MTP level 1 and 2 function 408 performs MTP level 1 and 2 functions, such as error detection, error correction, and sequencing of signaling messages.
  • I/O buffer 410 stores inbound signaling messages before the messages are processed by higher layers. I/O buffer 410 also stores outbound signaling messages waiting to be transmitted over a signaling link by MTP level 1 and 2 function 408.
  • Gateway screening function 412 screens inbound signaling messages based on destination point code and, optionally, based on originating point code to determine whether the messages should be allowed into the network.
  • Discrimination function 414 analyzes the destination point code in each received signaling message to determine whether the signaling message should be processed by an internal processing module within node 106 or whether the message should be routed over an outbound signaling link. Discrimination function 414 forwards messages that are to be internally processed to distribution function 416. Discrimination function 414 forwards messages that are to be routed over an outbound signaling link to routing function 418.
  • Distribution function 416 distributes messages that are identified as requiring internal processing to the appropriate internal processing module. For example, distribution function 416 may forward SCCP messages to database services module 404 for SCCP processing. Routing function 418 routes signaling messages that are addressed to point codes other than the point code of node 106. For example, routing function 418 may forward messages to another link interface module (not shown in Figure 8) or to data communications module 402 for transmission over an outbound signaling link.
  • DCM 402 includes various functions for sending and receiving signaling messages over IP signaling links.
  • Example signaling messages include SS7 over IP messages, session initiation protocol (SIP) messages, and others.
  • SIP session initiation protocol
  • these functions include a physical layer function 420, a network layer function 422, a transport layer function 424, an adaptation layer function 426, and SS7 MTP functions 410, 412, 414, 416, and 418 as described with regard to LIM 400.
  • Physical layer function 420 may be any suitable physical layer function for sending and receiving frames that encapsulate network layer packets.
  • physical layerfunction 420 may be implemented using an Ethernet transceiver.
  • Network layer function 422 may be implemented using Internet protocol, such as IPv4 or IPv6.
  • Transport layer function 424 may be implemented using any suitable transport layer protocol.
  • Adaptation layerfunction 426 may be implemented using any suitable adaptation layer, including adaption layers for sending SS7 messages over IP.
  • Examples of adaptation layers suitable for use with the subject matter described herein include M3UA, M2PA, SUA, and TALI, as described in the correspondingly named IETF Internet drafts and RFCs.
  • the remaining functions of DCM 402 are the same as those described with regard to LIM 400. Hence, a description thereof will not be repeated herein.
  • DSM 404 includes various functions and databases for processing signaling messages.
  • DSM 404 includes a service selection function 428, a target message screening function 430, and a routing function 432.
  • Database services module 404 also includes toll-free service module (TFSM) 114 for processing signaling messages related to toll-free calls.
  • Service selection function 428 receives messages from interface processors and determines the type of service required for each message. For example, service selection function 428 may determine whether further screening of messages is required or whether the messages are simply to be global title translated and routed. For CAP or INAP messages, service selection function 428 may forward the messages to target message screening function 430.
  • Target message screening function 430 screens CAP or INAP messages received by DSM 404 to identify targeted message types.
  • target message screening function 430 may identify call setup messages, such as ISUP IAM or SAM, as a targeted message type requiring further processing. For call setup messages, targeted message screening function 430 may communicate with TFSM 114 to process signaling messages associated with toll-free calls.
  • call setup messages such as ISUP IAM or SAM
  • TFSM 114 may receive a mobility management message related to a toll-free call. For example, TFSM 114 may receive an SRI message including a toll-free number ( Figure 1 , message 1 ). In response, TFSM 114 may identify the SRI message as one that requires toll-free processing and take appropriate action. For example, TFSM 114 may generate a TF query and send the generated query to TFDB 108 via LIM 400 or DCM 402 as appropriate ( Figure 1 , message 2). TFSM 114 may subsequently receive a response to the TF query ( Figure 1 , message 3), and perform additional queries to other databases as needed.
  • databases TFDB 108, NPDB 110, and HLR 112 are external to signaling node 106, which issues queries and receives responses via network 100.
  • signaling message routing node 106 may include local databases 434.
  • DSM 404 may include an internal toll-free database, an internal number portability database, an internal HLR database, and so on. It will be obvious to one of skill in the subject matter described herein contemplates both internal and external, local and remote databases, in any combination.
  • database refers to a database, a table, a data structure, a portion of memory or data storage, or other means to store and retrieve data, in particular two pieces of data in a key/value relationship.
  • database query refers to not only a database query, but also a table lookup or access to a data structure, for example.
  • a database query such as may be used to determine a directory number associated with a toll-free called party number or to determine routing information associated with a directory number, could be performed using one or more protocols, including but not limited to a TCAP or MAP protocol, an Internet protocol (IP), a signaling connection and control part (SCCP) user adaptation (SUA) protocol, a session initiation protocol (SIP), or other protocols usable to perform a data query.
  • IP Internet protocol
  • SCCP signaling connection and control part
  • SIP session initiation protocol
  • FIG. 5A-5F each include a block diagram illustrating an exemplary system for providing toll-free service according to another embodiment of the subject matter described herein.
  • Figures 5A-5F illustrate the use of the send routing information (SRI) to provide toll-free service.
  • telecommunications network 500 includes: a switch S1 102, which may be a mobile switching center (MSC), via which a subscriber, such as mobile subscriber 104, accesses network 500; a signaling node 106, which includes a toll-free service module (TFSM) 114; a toll-free database (TFDB) 108 for mapping a toll-free number associated with called party 220 to a directory number; and one or more databases for determining a routing number, such as number portability database NPDB 110 or routing database 116.
  • the functions of elements 102, 104, 106, 108, 114, 116, and 120 are substantially identical to the like-numbered elements in Figure 1 , and
  • Figure 5A is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 5A illustrates exemplary signaling messages that may be generated during a mobile-to-wireline call setup in a network that does not support number portability.
  • Mobile subscriber 104 initiates a call to a toll-free called party number that is associated with wireline subscriber 120.
  • S1 102 may be configured to issue an SRI query ( Figure 5A, message 1) in response to a determination that the called party number is a toll-free number, such as by a determination that the called party number is a 1 -8XX number.
  • S1 102 may be configured to treat every called party number in the same way, such as by issuing an SRI query for every number, whether or not the called party number is a toll-free number.
  • the SRI query includes the toll-free number (TFN), also referred to as a "toll-free B-party" number, either as a parameter or stored in some field within the message.
  • TFN toll-free number
  • the S1 102 may avoid having to be provisioned to support additional protocols. Specifically, by issuing an SRI message, S1 102 may avoid having to support the intelligent network (IN) protocol and its derivatives, such as advanced intelligent network (AIN), wireless intelligent network (WIN), and others, or the customized applications for mobile networks enhanced logic (CAMEL) application part (CAP) protocol, for example.
  • AIN advanced intelligent network
  • WIN wireless intelligent network
  • CAP application part
  • Signaling node 106 receives the SRI query from S1 102.
  • signaling node 106 issues a TF query to TFDB 108 in response to determining that the called party number is a toll-free number.
  • signaling node 106 may issue a TF query to TFDB 108 for every called party number without first determining whether it is a toll-free number.
  • the TF query ( Figure 5A, message 2) and TF response ( Figure 5A, message 3) may be any of a variety of protocols, including WIN, INAP, and CAMEL
  • the TF response contains the translated DN associated with the TFN.
  • TFSM 114 queries routing database 116, which returns an RN associated with the translated DN.
  • Signaling node 106 then issues an SRI_ACK ( Figure 5A, message 4) to S1 102.
  • the SRI_ACK includes both the RN and DN associated with the TFN.
  • Figure 5B is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 5B illustrates exemplary signaling messages that may be generated during a mobile-to-mobile call setup in a network that does not support number portability.
  • Mobile subscriber 104 initiates a call to a toll-free called party number that is associated with mobile subscriber 120.
  • S1 102 has been configured to issue an SRI query (Figure 5B, message 1) including the TFN in response to a determination that the called party number is a toll-free number
  • signaling node 106 receives the SRI query from S1 102 and engages in a toll-free query and response with TFDB 108 (Figure 5B 1 messages 2 and 3).
  • TFSM 114 determines that the translated DN returned by TFDB 108 belongs to a mobile subscriber, and thus queries HLR 112 to determine the current routing information for mobile called party 120 (Figure 5B, message 4).
  • HLR 112 returns the MSRN of the MSC currently serving mobile called party 120 ( Figure 5B 1 message 5).
  • FIG. 5C is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 5C illustrates an embodiment of network 500 in which toll-free database TFDB 108 is local to signaling node 106, rather than remote from signaling node 106 as shown in Figure 5B.
  • Figure 5D is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 5D illustrates an embodiment of network 500 in which signaling node 106 returns the RN and DN data not as separate fields or parameters as shown in Figure 5C, but concatenated together in a single field or parameter.
  • Figure 5E is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 5E illustrates exemplary signaling messages that may be generated during a mobile-to-wireline call setup in a network that supports number portability.
  • the operation of the embodiment of network 500 illustrated in Figure 5E is substantially identical to that illustrated in Figure 5A, except that after the toll- free number TFN has been translated to a DN, TFSM 114 determines routing information for the DN by querying number portability database NPDB 110 rather than routing database 116.
  • TFSM 114 may perform an NP query only for DNs that have been identified as having been ported.
  • TFSM 114 may perform an NP query for every DN, or even for every called party number detected.
  • Figure 5F is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 5F illustrates exemplary signaling messages that may be generated during a mobile-to-mobile call setup in a network that supports number portability.
  • the operation of the embodiment of network 500 illustrated in Figure 5F is substantially identical to that illustrated in Figure 5E, except that TFSM 114 may determine that the called party is a mobile subscriber, an thus engage in an SRI query and response with HLR 112 ( Figure 5E, messages 4 and 5).
  • the routing number returned by NPDB 110 may be used to identify the network to which the toll-free called party 120 now belongs. This information may be used, for example, to determine which HLR 112 to query.
  • NPDB 110 may return the identity of the network to which toll-free called party 120 belongs, or the network address of a gateway to the network.
  • signaling node 106 may then modify the original SRI query ( Figure 5F, message 1 , for example) to include the DN and RN information that it currently has, and forward the query to the network or network gateway node.
  • the SRI query may be processed by the network or some entity therein, which sends an response to the SRI query directly to S1 102.
  • the SRI response may or may not be routed through signaling node 106 on its way back to MSC 102.
  • Figure 6 is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 6 illustrates exemplary signaling messages that may be generated in a system for providing toll-free service according to another embodiment of the subject matter described herein.
  • Figure 6 illustrates an implementation of toll-free service in which the identity of the switch that is serving the calling mobile subscriber is provided as part of the toll-free number lookup, to assist selection of an appropriate directory number based on the location of the calling party, herein referred to as calling-party-location sensitive toll-free translation.
  • Telecommunications network 600 includes a switch S1 102, such as an MSC, via which a subscriber, such as mobile subscriber 104, accesses network 600.
  • network 600 has a signaling node 106; a toll-free database TFDB 108 for mapping a toll-free number associated with called party 120 to a directory number; a toll-free service module 114; and a routing database 116.
  • the functions of elements 102, 104, 106, 108, 114, 116, and 120 are substantially identical to the like- numbered elements in Figure 2, and therefore their descriptions will not be repeated herein.
  • S1 102 has been configured to issue an SRI query (Figure
  • S1 102 has also been configured to provide, as part of the SRI query, information identifying itself.
  • the information could be, for example, an origination point code (OPC), an SCCP calling party address, a MAP-layer MSCJD, a MAP-layer VLRJD, an MSC entity address, or other identifying information.
  • OPC origination point code
  • SCCP SCCP calling party address
  • MAP-layer MSCJD a MAP-layer MSCJD
  • VLRJD MAP-layer VLRJD
  • MSC entity address or other identifying information.
  • the identity of the MSC can be used to provide an indication of the geographic location of the calling party, mobile subscriber 104.
  • This geographic location information could be used, for example, by a company with a business presence in several different geographic areas. Such a company may desire to provide a single toll-free number, which, when called, will connect the calling party to the office or representative geographically closest to the calling party. For example, a caller on the east coast may be connected to an east coast office while a caller on the west coast may be connected to a west coast office. Similarly, a caller of a world-wide toll-free number may be connected to the office in the appropriate continent or county.
  • signaling node 106 may include at least a portion of this originating switch identity information in the toll-free database query ( Figure 6, message 2), thereby providing TFDB 108 with sufficient calling party location information to perform a calling location-sensitive toll-free translation.
  • Table 3 shows an example of a toll-free database configured to return a directory number based on the geographic location of the calling party, as derived from the area code of the calling party.
  • a caller of the toll-free number "1-800-TEKELEC" (1-800-835-3532) will be connected to one of several different directory numbers, depending on the calling party's area code.
  • callers from the west coast of the United States such as callers from area codes 415 and 630, will be connected to the Illinois office at (630) 268-2524, while callers from the east coast, such as callers from area codes 704 and 919, will be connected to the North Carolina office at (919)
  • signaling node 106 may extract an SS7 origination point code (OPC) network address value from the SRI message, and map the OPC to a switch identity / entity address or "dummy" telephone number associated with the switch originating the SRI. This switch entity address or telephone number is then included in the toll-free query.
  • OPC origination point code
  • a calling party mapping database 602 may be provided for mapping an origination point code of the originating switch to a directory number or routing number which is then passed to TFDB 108 as party of the toll-free query.
  • An example of such a calling party mapping database is shown in Table 4, below. Table 4 - Calling Party Mapping DB
  • mobile subscriber 104 calls the toll-free number associated with toll-free mobile called party 120.
  • mobile subscriber 104 has a mobile telephone number (919) 555- 5555 and MSC 102 has a point code of 2-4-3.
  • MSC 102 determines that the called party number is a toll-free number, and, in response, sends an SRI query including the MSC identifier, point code 2-4-3 ( Figure 6, message 1) to signaling node 106.
  • TFSM 114 determines that the SRI query includes a toll-free number, and, in response, issues a toll-free query (Figure 6, message 2) to TFDB 108.
  • the toll-free query includes MSC point code 2-4-3 along with the toll-free called party number.
  • TFDB 108 first determines the toll-free calling party ID by mapping the OPC of MSC 102 to a directory number, calling party mapping DB 602, the contents of which are shown in Table 4, above, which returns a calling party ID of "2124580000".
  • TFDB 108 uses the calling party ID returned by calling party mapped DB 602 and includes that as the MSC identifier in a toll- free query (Figure 6, message 2) to TFDB 108.
  • TFDB 108 then uses the first three digits of the MSC ID, i.e., "212", along with the toll-free called party number, i.e., "8008353532", to determine the translated directory number for toll-free called party, by using Table 3, above.
  • TFDB 108 will return directory number "6302682524" to TFSM 114 ( Figure 6, message 3).
  • TFSM 108 will determine a routing number associated with the translated directory number by using, for example, any of the methods described above.
  • Signaling node 106 will then send an SRI ACK containing the routing number associated with the translated directory number ( Figure 6, message 4) to MSC 102.
  • TFDB 108 used the mobile subscriber's directory number "9195555555” instead of the MSC ID, TFDB 108 would have returned "9194605500" as the directory number for the toll-free called party. In this case, mobile subscriber 104 would not have been connected to the called party number geographically closest to mobile subscriber 104.
  • Figures 7A-7C each include a block diagram illustrating an exemplary system for providing toll-free service according to another embodiment of the subject matter described herein.
  • Figures 7A-7C illustrate the use of a number portability (NP) query to provide toll-free service.
  • telecommunications network 700 includes: a switch, such as end office (EO) 102, via which a subscriber, such as fixed line subscriber 104, accesses network 700; a signaling node 106, which includes a toll-free service module (TFSM) 114; a toll-free database (TFDB) 108 for mapping a toll-free number associated with called party 120 to a directory number; and a number portability database NPDB 110.
  • a switch such as end office (EO) 102, via which a subscriber, such as fixed line subscriber 104, accesses network 700
  • a signaling node 106 which includes a toll-free service module (TFSM) 114
  • TFDB toll-free
  • Figure 7A is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 7A illustrates exemplary signaling messages that may be generated during a wireline-to-wireline call setup in a network in which supports number portability.
  • calling party 104 is a wireline subscriber
  • originating switch 102 is an end office (EO) that has been configured to issue NP queries whenever it determines that the called party number is a toll-free number.
  • EO end office
  • Calling party 104 dials a toll-free number associated with called party 120, which in this example is a wireline subscriber.
  • E0102 determines that the called party number is a toll-free number, and, in response, issues an NP query including the toll-free number, TFN, to signaling node 106 ( Figure 7A, message 1).
  • signaling node 106 has been configured to determine whether an incoming NP query includes a toll-free number, and if so, to direct the query to TFSM 114.
  • TFSM 114 determines that the called party is a toll-free number and issues a TF query to TFDB 108 ( Figure 7A, message 2).
  • TFDB 108 translates the toll-free number contained in the query, TFN, to a directory number (DN), and returns the translated DN to signaling node 106 ( Figure 7A, message 3).
  • TFSM 114 receives the DN and performs a number portability query using NPDB 110, which returns routing information, such as a location routing number (LRN), to TFSM 114.
  • LRN location routing number
  • Signaling node 106 then sends the routing information back to EO 102 as an NP response ( Figure 7A, message 4).
  • calling party 104 may be a mobile subscriber and S1 102 may be a MSC.
  • Figure 7B is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 7B illustrates an embodiment of network 700 which is substantially identical to the embodiment illustrated in Figure 7A, except that in Figure 7B, NPDB 110 is located remotely from signaling node 106.
  • NPDB 110 is a component within signaling node 106.
  • TFSM 114 or signaling node 106 may perform the NP query with NPDB 110 ( Figure 7A, messages 4 and 5) using one or more of the protocols discussed above.
  • NPDB 110 may issue an NP response that includes a routing number.
  • the NP response from NPDB 110 may include the directory number that was used in the query, i.e., the translated DN, as well as the routing number.
  • Figure 7C is a block diagram illustrating an exemplary system for providing toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 7C illustrates an embodiment of network 700 which is substantially identical to the embodiment illustrated in Figure 7A, except that in Figure 7C, both TFDB 108 and NPDB 110 are local to signaling node 106.
  • the embodiments of signaling node 106 illustrated in Figure 7A, 7B, and 7C have identical behavior: EO 102 issues an NP query containing a toll-free called party number, and signaling node 106 responds with routing information and optionally with the translated DN as well.
  • FIGS 8A-8C each include a block diagram illustrating an exemplary system for providing toll-free service according to another embodiment of the subject matter described herein.
  • Figures 8A-8C illustrate a triggerless implementation of toll-free service, with release.
  • telecommunications network 800 includes: a switch 102, such as an end office (EO), a service switching point (SSP), or MSC, via which a fixed line or mobile subscriber 104 accesses network 800; a signaling message routing node, signaling node 106, which includes a toll-free service module (TFSM) 114; and a toll-free database (TFDB) 108 for mapping a toll-free number associated with called party 120 (not shown) to a directory number.
  • a switch 102 such as an end office (EO), a service switching point (SSP), or MSC, via which a fixed line or mobile subscriber 104 accesses network 800
  • a signaling message routing node, signaling node 106 which includes a to
  • Figures 8B and 8C also include a number portability database NPDB 110.
  • NPDB 110 a number portability database
  • Figure 8A is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 8A illustrates exemplary signaling messages that may be generated during a mobile-originated call setup.
  • an originating switch such as MSC 102, sends a call setup message (Figure 8A, message 1).
  • Example call setup messages include ISUP IAM, ISUP SAM, and BICC messages.
  • the call setup message includes called party information and may include information identifying a bearer circuit, such as a circuit identification code (CIC), which provides information about where the voice part of the call is carried, e.g., on which trunk and in which timeslot.
  • CIC circuit identification code
  • the call setup message is intercepted by a signaling message processing node, such as signaling node 106.
  • TFSM 114 issues a toll-free query (Figure 8A, message 2) to TFDB 108 and receives from TFDB 108 a response that includes a translated DN ( Figure 8A, message 3).
  • network MSC 102 is configured to determine whether the called party number is a toll-free number, and if so, to reserve a dummy circuit.
  • TFSM 114 may always issue a release message ( Figure 8A, message 4) to MSC 102, the release message including the translated DN.
  • MSC 102 receives the translated DN from signaling node 106 and issues a second call setup message based on the translated DN.
  • MSC 102 may receive the translated DN and perform a routing query based on the translated DN, receive routing information, such as a routing number (RN), and include the RN in the second call setup message.
  • MSC 102 may determine that the translated DN is for a mobile subscriber and issue an SRI request to an HLR, receive an MSRN, and send the second call setup request to the switch identified by the MSRN, and so on.
  • MSC 102 may route to a default destination switch and reserve an actual (i.e., not dummy) circuit to the target destination.
  • signaling node 106 intercepts the call setup message (Figure 8A, message 1), performs the TF query ( Figure 8A, messages 2 and 3), and determines, based on the translated DN, whether the reserved bearer circuit was the correct one. If so, signaling node 106 may opt not to issue the release message ( Figure 8A, message 4), but instead simply forward the call setup message to the next node in the path. (This scenario is described in more detail with regards to Figure 9A, below.)
  • Figure 8B is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 8B illustrates an embodiment of network 800 which is substantially identical to the embodiment illustrated in Figure 8A, except that in Figure 8B, network 800 supports number portability.
  • signaling node 106 may also perform a NP query using NPDB 110 to determine routing information, which is also included in the release message ( Figure 4B, message 4) sent to MSC 102.
  • Figure 8C is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 8C illustrates an embodiment of network 800 which is substantially identical to the embodiment illustrated in Figure 8B, except that in Figure 8C, number portability database NPDB 110 is located remotely from signaling message routing node 106.
  • Figure 8C also illustrates an embodiment in which signaling message routing node 106 is a SIP router.
  • FIG. 9A-9D each include a block diagram illustrating an exemplary system for providing toll-free service according to another embodiment of the subject matter described herein.
  • Figures 9A-9D illustrate a triggerless implementation of toll-free service, without release.
  • telecommunications network 900 includes: a switch 102, such as an end office (EO), a service switching point (SSP), or MSC, via which a fixed line or mobile subscriber 104 accesses network 900; a signaling message routing node, signaling node 106, which includes a toll-free service module (TFSM) 114; a toll-free database (TFDB) 108 for mapping a toll-free number associated with called party 120 (not shown) to a directory number; and one or more databases, such as number portability database NPDB 110, HLR 112, or routing database 116, for determining a routing number to a terminating switch (S2) 118, which may be an SSP, an MSC, or a tandem
  • S2 terminat
  • Figure 9A is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 9A illustrates exemplary signaling messages that may be generated in a system that implements triggerless toll-free service and that supports number portability.
  • end office 102 sends a call setup message, such as an ISUP IAM, ISUP SAM, or BICC message, the message including the toll-free number of the called party.
  • Signaling node 106 intercepts the call setup message ( Figure 9A, message 1), determines that the call setup message includes a toll-free called party number, and passes the message to TFSM 114.
  • TFSM 114 queries TFDB 108 (Figure 9A, message 2) using the toll-free called party number TFN.
  • TFDB 108 returns the translated DN ( Figure 9A 1 message 3).
  • TFSM 114 queries NPDB 110 ( Figure 9A, message 4) using the translated DN.
  • NPDB 110 returns a location routing number LRN ( Figure 9A, message 5).
  • TFSM 114 sends a call setup message including the translated DN and LRN ( Figure 9A, message 6) to S2 118.
  • Figure 9B is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 9B illustrates exemplary signaling messages that may be generated in a system that implements triggerless toll-free service but does not support number portability.
  • messages 1 - 3 may be substantially the same as for the embodiment illustrated in Figure 9A.
  • TFSM 114 upon receipt of the translated DN from TFDB 108, TFSM 114 does not yet have routing information for the call, and so may query routing DB 116 to determine a routing number RN associated with the translated DN.
  • TFSM 114 may forward the call setup message, now including the translated DN and RN, to S2 118 ( Figure 9B, message 4).
  • a routing number may be determined for the translated DN by other means, such as those described above.
  • Figure 9C is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 9C illustrates exemplary signaling messages that may be generated in a system that implements triggerless toll-free service and supports mobile subscribers but does not support number portability.
  • messages 1 - 3 may be substantially the same as for the embodiment illustrated in Figure 9A.
  • TFSM 114 upon receipt of the translated DN from TFDB 108, TFSM 114 may determine that the translated DN is a mobile number. If so, TFSM 114 determines routing information for the mobile called party subscriber.
  • TFSM 114 may issue an SRI query including the translated DN ( Figure 9C, message 4) to HLR 112, which responds with an SRI_ACK message including the MSRN for the mobile called party subscriber ( Figure 9C 1 message 5). TFSM 114 may then issue a call setup message including the MSRN and translated DN ( Figure 9C, message 6), to S2 118. If, in this example, the translated DN provided by TFDB 108 was associated with a wireline called party, TFSM 114 may query routing database 116 to determine routing information.
  • Figure 9D is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 9D illustrates exemplary signaling messages that may be generated in a system that implements triggerless toll-free service, supports mobile subscribers, and supports number portability.
  • messages 1 - 3 may be substantially the same as for the embodiment illustrated in Figure 9A.
  • TFSM 114 may determine that a number portability lookup is required. If so, TFSM 114 may query NPDB 110 using the translated DN, which may return routing information, such as a local routing number, associate with the translated DN.
  • TFSM 114 may then determine that the translated DN is a mobile number. If so, TFSM 114 determines routing information for the mobile called party subscriber. In one embodiment, TFSM 114 may issue an SRI query including the translated DN ( Figure 9D, message 4) to HLR 112, which responds with an SRI_ACK message including the MSRN for the mobile called party subscriber ( Figure 9D, message 5). TFSM 114 may then issue a second call setup message including the MSRN and translated DN ( Figure 9C, message 6), to S2 118.
  • the routing information RN provided as a result of the NP query may be used by TFSM 114 to determine identify an appropriate HLR to which to send the SRI query.
  • RN may be a network identifier, which TFSM 114 can use to determine which network's HLR to use (i.e., to which HLR the SRI query should be sent).
  • the routing information provided by the NP query is used to get the routing information from the HLR.
  • TFSM 114 may route the second call setup message based on the routing information provided by the NP query.
  • the routing information provided by the NP query may be discarded and/or replaced by any routing information provided by HLR 112.
  • the call signaling flows illustrated in Figures 9A-9D may also be implemented in a system that supports release, but, due to particular circumstances, does not issue a release message.
  • EO 102 will usually reserve a bearer channel or bearer circuit for connecting the bearer portion of the call between EO 102 and the anticipated next node in the call path.
  • TFSM 114 determines that S2 118 is the correct destination, there is no need to issue a release. In this case, TFSM 114 would issue message 6 as shown in Figure 9A.
  • FIGS 10A-10C each include a block diagram illustrating an exemplary system for providing toll-free service according to another embodiment of the subject matter described herein.
  • Figures 10A-1 OC illustrate implementation of toll-free service in a SIP network.
  • telecommunications network 1000 includes: a switch S1 102 in a SIP network, such as a Softswitch (SS).
  • Alternative switches include, but are not limited to, media gateway controllers (MGCs), media gateways (MGWs), and call session control functions (CSCFs).
  • S1 102 serves SIP user agent client (UAC) 104.
  • UAC SIP user agent client
  • Network 1000 also includes: a signaling node 106, such as a SIP router, which includes TFSM 114; a toll-free database TFDB 108 for mapping a toll-free number associated with called party 120 (not shown) to a directory number; and a routing database, such as an E.164 number mapping (ENUM) database (ENUM DB) 122 for mapping a directory number to a URI or other address within the SIP network.
  • a signaling node 106 such as a SIP router, which includes TFSM 114
  • TFDB 108 for mapping a toll-free number associated with called party 120 (not shown) to a directory number
  • a routing database such as an E.164 number mapping (ENUM) database (ENUM DB) 122 for mapping a directory number to a URI or other address within the SIP network.
  • ENUM E.164 number mapping
  • FIG 10A is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 10A illustrates an embodiment of network 1000 which uses ENUM queries to provide triggered toll-free service.
  • S1 102 is configured to issue an ENUM query in response to detection of a call signaling message that contains a toll-free called party.
  • a calling party such as SIP network subscriber 104, initiates a call to a toll-free calling party, for example, by issuing a call setup message, such as a SIP INVITE message.
  • S1 102 receives the call setup message from calling party 104.
  • the call setup message includes information indicating that the called party is a toll-free called party.
  • a SIP message may include a toll-free number, such as a 1-800 number, in the form of a URI associated with a toll-free service, such as "tel:+1 -800-555-0000", "sip:+18005550000", etc.
  • S1 102 may then issue an ENUM query (Figure 10A, message 1) including the toll-free called party number (TFN).
  • S1 102 may issue the ENUM query in response to determining that the called party setup message contains a toll-free called party.
  • S1 102 may always issue an ENUM query, and thus avoids the block of determining whether the called party number is a toll-free number.
  • signaling node 106 is configured to analyze incoming ENUM queries in order to detect ENUM queries that contain toll-free called party numbers.
  • SIP router and/or TFSM 114 determines that the ENUM query contains a toll-free called party number, and in response, may issue a TF query to TFDB 108 ( Figure 10A, message 2).
  • TFDB 108 may respond with a translated DN ( Figure 10A, message 3).
  • Figure 10B is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 10B illustrates an implementation of triggerless toll-free service with release.
  • signaling node 106 is configured to intercept call setup messages that include a toll-free called party and pass them to TFSM 114 for processing.
  • signaling node 106 intercepts a SIP INVITE message containing a toll-free called party number, TFN ( Figure 10B, message 1).
  • TFDB 108 may return a translated directory number to signaling node 106 ( Figure 10B, message 3).
  • signaling node 106 determines routing information for the translated DN by issuing an ENUM query (Figure 10B, message 4) to ENUM database 122.
  • ENUM database 122 returns an ENUM response ( Figure 10B, message 5) that includes routing information for the translated DN.
  • ENUM database 122 may return a toll-free URI, a SIP address, etc.
  • signaling node 106 may issue a redirect message, such as a SIP 3XX message ( Figure 10B, message 5), to indicate that the called party has moved; this message may contain information to indicate to S1 102 the new location of the called party.
  • the SIP 3XX message includes the routing information provided by the ENUM query, e.g., the toll-free URI.
  • FIG. 10C is a block diagram illustrating an exemplary system for providing triggerless toll-free service in a telecommunications network according to another embodiment of the subject matter described herein.
  • Figure 10C illustrates an implementation of triggerless toll-free service without release.
  • Figure 10C illustrates an embodiment of network 1000 which is substantially identical to the embodiment illustrated in Figure 10B, except that in Figure 10C, a release message is not issued, either because network 1000 does not support release or because a release was not needed.
  • signaling node 106 may issue a second call setup message, such as another SIP INVITE ( Figure 10C, message 6), which includes the routing information returned by the ENUM query.
  • a second call setup message such as another SIP INVITE ( Figure 10C, message 6)

Abstract

On décrit des procédés, des systèmes et des progiciels informatiques destinés à assurer un service sans frais dans un réseau de télécommunications. Selon un aspect, la présente invention comprend un procédé destiné à assurer un service sans frais dans un réseau de télécommunications et comportant les étapes consistant, au niveau d’un nœud de signalisation comprenant au moins un processeur : à recevoir un premier message de signalisation comprenant un numéro d’appelé sans frais, le premier message de signalisation étant un message d’établissement d’appel non-TCAP, une interrogation de gestion de mobilité, une interrogation de portabilité de numéro (NP) ou une interrogation de numéro E.164 (ENUM) ; à déterminer un numéro d’annuaire associé avec le numéro d’appelé sans frais ; et à envoyer le premier message de signalisation ou un deuxième message de signalisation, le message envoyé comprenant le numéro d’annuaire et / ou les informations de routage associées au numéro d’annuaire.
PCT/US2009/065733 2008-11-24 2009-11-24 Systèmes, procédés et supports lisibles par ordinateur pour assurer un service sans frais dans un réseau de télécommunications WO2010060082A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11754508P 2008-11-24 2008-11-24
US61/117,545 2008-11-24

Publications (2)

Publication Number Publication Date
WO2010060082A2 true WO2010060082A2 (fr) 2010-05-27
WO2010060082A3 WO2010060082A3 (fr) 2010-08-05

Family

ID=42198850

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2009/065733 WO2010060082A2 (fr) 2008-11-24 2009-11-24 Systèmes, procédés et supports lisibles par ordinateur pour assurer un service sans frais dans un réseau de télécommunications

Country Status (2)

Country Link
US (1) US8600007B2 (fr)
WO (1) WO2010060082A2 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8520828B2 (en) 2005-03-21 2013-08-27 Tekelec, Inc. Methods, systems, and computer program products for providing telecommunications services between a session initiation protocol (SIP) network and a signaling system 7 (SS7) network
US8600007B2 (en) 2008-11-24 2013-12-03 Tekelec Global, Inc. Systems, methods, and computer readable media for providing toll-free service in a telecommunications network
US9712341B2 (en) 2009-01-16 2017-07-18 Tekelec, Inc. Methods, systems, and computer readable media for providing E.164 number mapping (ENUM) translation at a bearer independent call control (BICC) and/or session intiation protocol (SIP) router

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8634498B2 (en) * 2008-12-17 2014-01-21 Entropic Communications, Inc. Systems and methods for probing wired communication channels
US8391273B2 (en) * 2008-12-18 2013-03-05 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for providing intra-carrier IP-based connections using a common telephone number mapping architecture
US8432923B2 (en) 2008-12-18 2013-04-30 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for providing inter-carrier IP-based connections using a common telephone number mapping architecture
US9219677B2 (en) 2009-01-16 2015-12-22 Tekelec Global, Inc. Methods, systems, and computer readable media for centralized routing and call instance code management for bearer independent call control (BICC) signaling messages
US8254545B2 (en) 2009-06-23 2012-08-28 At&T Intellectual Property I, L.P. System and methods for enhanced multimedia in VoIP networks
US9100415B2 (en) * 2009-12-17 2015-08-04 Verizon Patent And Licensing Inc. On-net direct access to voicemail
US9444854B2 (en) * 2010-09-07 2016-09-13 T-Mobile Usa, Inc. Session initiation protocol (SIP) router
US9241258B2 (en) 2011-09-15 2016-01-19 At&T Intellectual Property I, Lp Method and apparatus for managing calls
US8693464B2 (en) 2011-09-15 2014-04-08 At&T Intellectual Property I, Lp Method and apparatus for processing calls
US9178989B2 (en) 2013-03-15 2015-11-03 Genesys Telecommunications Laboratories, Inc. Call event tagging and call recording stitching for contact center call recordings
WO2016070095A1 (fr) 2014-11-01 2016-05-06 SMS/800, Inc. Plateforme de gestion de télécommunications sans frais
US10560583B2 (en) 2014-11-01 2020-02-11 Somos, Inc. Toll-free numbers metadata tagging, analysis and reporting
US9992352B2 (en) 2014-11-01 2018-06-05 Somos, Inc. Toll-free telecommunications and data management platform
US10270917B2 (en) * 2015-09-11 2019-04-23 Level 3 Communications, Llc Method and system for routing of inbound toll-free communications
US11316983B2 (en) 2015-09-11 2022-04-26 Level 3 Communications, Llc Method and system for routing of inbound toll-free communications
DK3373621T3 (da) * 2017-03-07 2021-01-04 Telia Co Ab Roamingløsning
CA3051556A1 (fr) 2018-08-10 2020-02-10 Somos, Inc. Interface de gestion des donnees de telecommunications sans fil
CN111917726B (zh) * 2020-07-01 2022-03-15 中国建设银行股份有限公司 适配层、语音通信系统及其控制方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040228466A1 (en) * 2002-11-05 2004-11-18 Bedingfield James Carlton Methods, systems, and computer program products for routing calls based on the originating network
US7085362B1 (en) * 1995-09-08 2006-08-01 Sprint Communications Company L.P. System for managing telecommunications
US20060209791A1 (en) * 2005-03-21 2006-09-21 Tekelec Methods, systems, and computer program products for providing telecommunications services between a session initiation protocol (SIP) network and a signaling system 7 (SS7) network

Family Cites Families (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4191860A (en) * 1978-07-13 1980-03-04 Bell Telephone Laboratories, Incorporated Data base communication call processing method
US5282243A (en) * 1990-07-03 1994-01-25 At&T Bell Laboratories Recording of automatic number identification to identify lost customers
EP0721721B1 (fr) * 1993-09-22 1999-01-07 AT&T Corp. Procede permettant a des abonnes de modifier des caracteristiques d'appel en temps reel
US5425090A (en) * 1993-12-07 1995-06-13 Bell Communications Research, Inc. System and method for providing advanced intelligent network services
US5550909A (en) * 1994-10-14 1996-08-27 At & T Corp. International toll-free calling process
CA2165856C (fr) * 1995-12-21 2001-09-18 R. William Carkner Methode pour realiser la transportabilite des numeros utilisant la consultation d'une base de donnees
US6779030B1 (en) * 1997-10-06 2004-08-17 Worldcom, Inc. Intelligent network
US6069946A (en) * 1997-12-02 2000-05-30 Lucent Technologies Inc. Telecommunications system for providing a calling party control service
US6320952B1 (en) * 1998-04-30 2001-11-20 At&T Corp. Method and system for transferring digital data calls between different destinations
US6647111B1 (en) * 1998-05-07 2003-11-11 Mci Communications Corporation System for executing advanced interactive voice response services using service-independent building blocks
US6366658B1 (en) * 1998-05-07 2002-04-02 Mci Communications Corporation Telecommunications architecture for call center services using advanced interactive voice responsive service node
US6493433B2 (en) * 1998-07-07 2002-12-10 Mci Communications Corporation Multi-threaded database system for an interactive voice response platform
US6289095B1 (en) * 1998-09-29 2001-09-11 Lucent Technologies Inc. NPA split management in intelligent network environment
WO2000033519A1 (fr) * 1998-12-01 2000-06-08 Thor Simon Systeme de signalisation ameliore pour telecommunications
US6353896B1 (en) * 1998-12-15 2002-03-05 Lucent Technologies Inc. Method and apparatus for testing event driven software
US6636504B1 (en) * 1999-03-18 2003-10-21 Verizon Services Corp. Reverse billing of internet telephone calls
US20010053218A1 (en) * 1999-05-26 2001-12-20 Alex Leung Transaction bridging/forwarding in signaling system of telecommunications network
US6920214B1 (en) * 1999-07-01 2005-07-19 Sprint Communications Company L.P. Telecommunications system with centralized call redirection control logic and speed dial translation logic
US6826173B1 (en) * 1999-12-30 2004-11-30 At&T Corp. Enhanced subscriber IP alerting
US6654451B1 (en) * 2000-02-07 2003-11-25 Bellsouth Intellectual Property Corporation Methods and systems for billing and routing local toll-free calls
EP1303994B1 (fr) 2000-07-14 2005-09-28 Tekelec Services de filtrage sans declencheur
EP1217816A1 (fr) 2000-12-22 2002-06-26 Lucent Technologies Inc. Support de services vocaux centrales éxistants dans un réseau IP multimedia
US6940857B2 (en) * 2001-07-12 2005-09-06 At&T Corp. Broadcast/multicast system and protocol for circuit-switched networks
US6788777B2 (en) * 2001-07-20 2004-09-07 Lucent Technologies Inc. Alternative treatment for AIN fault handling
US6724869B2 (en) * 2001-07-31 2004-04-20 International Business Machines Corporation Multimodal telephone numbers
WO2003039128A2 (fr) * 2001-11-01 2003-05-08 Lang Alexander C Lancement d'appel gratuit utilisant un module d'initialisation d'un appel alphanumerique
US7286545B1 (en) * 2002-03-26 2007-10-23 Nortel Networks Limited Service broker
US6785374B2 (en) * 2002-09-30 2004-08-31 Guanglu Wang Method and apparatus for providing transaction capabilities application part information in a session initiation protocol system
JP4155920B2 (ja) * 2003-12-25 2008-09-24 株式会社日立コミュニケーションテクノロジー メディアゲートウェイおよび自動電話転送サービスシステム
EP1555844B1 (fr) * 2004-01-13 2007-03-07 Siemens Aktiengesellschaft Procédé, appareill et configuration de réseau pour établir des connextions dans un réseau de commnunication
US7657015B1 (en) * 2005-12-28 2010-02-02 At&T Corp. Method and apparatus for processing multiple services per call
US7650367B2 (en) * 2006-01-13 2010-01-19 Tekelec Methods, systems, and computer program products for detecting and restoring missing or corrupted data in a distributed, scalable, redundant measurement platform database
WO2008094648A1 (fr) * 2007-01-31 2008-08-07 Tekelec Procédés, systèmes et produits de programme informatique pour appliquer de multiples services de communication à un appel
US8503642B2 (en) * 2007-03-01 2013-08-06 NOS Communications, Inc. System and method for managing a telecommunications network
EP2143230A1 (fr) * 2007-04-20 2010-01-13 Tekelec Procédés, systèmes et produits de programme informatique pour fournir une fonction d'interaction et de médiation de service insensible aux défaillances dans un réseau de communications
US8184797B1 (en) * 2007-05-18 2012-05-22 Richard Rosen System and method for improved directory assistance searches
US20080294448A1 (en) * 2007-05-23 2008-11-27 At&T Knowledge Ventures, Lp Methods and systems associated with telephone directory advertisements
US20090041223A1 (en) * 2007-08-10 2009-02-12 Devesh Agarwal Systems, methods, and computer readable media for triggerless call redirection with release
WO2010060087A2 (fr) * 2008-11-24 2010-05-27 Tekelec Systèmes, procédés et supports lisibles par ordinateur pour traduction sensible au lieu du numéro de la partie appelée dans un réseau de télécommunications
US8600007B2 (en) * 2008-11-24 2013-12-03 Tekelec Global, Inc. Systems, methods, and computer readable media for providing toll-free service in a telecommunications network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7085362B1 (en) * 1995-09-08 2006-08-01 Sprint Communications Company L.P. System for managing telecommunications
US20040228466A1 (en) * 2002-11-05 2004-11-18 Bedingfield James Carlton Methods, systems, and computer program products for routing calls based on the originating network
US20060209791A1 (en) * 2005-03-21 2006-09-21 Tekelec Methods, systems, and computer program products for providing telecommunications services between a session initiation protocol (SIP) network and a signaling system 7 (SS7) network

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8520828B2 (en) 2005-03-21 2013-08-27 Tekelec, Inc. Methods, systems, and computer program products for providing telecommunications services between a session initiation protocol (SIP) network and a signaling system 7 (SS7) network
US8600007B2 (en) 2008-11-24 2013-12-03 Tekelec Global, Inc. Systems, methods, and computer readable media for providing toll-free service in a telecommunications network
US9712341B2 (en) 2009-01-16 2017-07-18 Tekelec, Inc. Methods, systems, and computer readable media for providing E.164 number mapping (ENUM) translation at a bearer independent call control (BICC) and/or session intiation protocol (SIP) router

Also Published As

Publication number Publication date
US8600007B2 (en) 2013-12-03
US20100158201A1 (en) 2010-06-24
WO2010060082A3 (fr) 2010-08-05

Similar Documents

Publication Publication Date Title
US8600007B2 (en) Systems, methods, and computer readable media for providing toll-free service in a telecommunications network
US9584959B2 (en) Systems, methods, and computer readable media for location-sensitive called-party number translation in a telecommunications network
EP1733571B1 (fr) Procedes, systemes et produits logiciels pour traiter des messages de requete d'origine mobile destines aux abonnes mobiles a prepaiement dans un environnement a portabilite de numero
EP2311284B1 (fr) Procédé, système et support lisible par ordinateur pour un routage/filtrage sans déclenchement basé sur la position d'un abonné mobile
US7606202B2 (en) Methods, systems, and computer program products for offloading call control services from a first network of a first type to a second network of a second type
US7881288B2 (en) Routing media streams from packet switched network to circuit switched network
US8254553B2 (en) Systems, methods, and computer program products for number translation with local directory number support
EP2127348B1 (fr) Procédés, systèmes et progiciels pour utiliser un mécanisme d'interrogation et de réponse à base de numéro d'acheminement à l'emplacement pour acheminer des appels à des abonnés de sous-système ims multimédia par ip
US6914973B2 (en) Methods and systems for improving trunk utilization for calls to ported numbers
US20010040957A1 (en) Methods and systems for providing universal triggerless number portability
US20090041223A1 (en) Systems, methods, and computer readable media for triggerless call redirection with release
US8358650B2 (en) Methods, systems, and computer program products for communicating calling name (CNAM) services for session initiation protocol (SIP) originated calls terminating in a circuit switched network
US8630651B2 (en) Cost effective call routing from IMS networks to local carrier networks
US8855654B2 (en) Methods, systems, and computer readable media for tracking and communicating long term evolution (LTE) handset communication capability
US8730970B2 (en) Methods systems, and computer program products for providing voicemail routing information in a network that provides customized voicemail services
EP1131943A1 (fr) Systeme de telephonie ip et son procede de fonctionnement grace a un reseau ss7
US8934380B2 (en) Methods, systems, and computer readable media for switching office trigger induction by an intermediate signaling node
CN101554079A (zh) 用于将呼叫控制服务从第一类型的第一网络卸载到第二类型的第二网络的方法、系统和计算机程序产品
Pang et al. GSM‐IP: A VoIP service for mobile networks

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09828377

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09828377

Country of ref document: EP

Kind code of ref document: A2