WO1995032588A1 - Mediation of open advanced intelligent network interface by shared execution environment - Google Patents
Mediation of open advanced intelligent network interface by shared execution environment Download PDFInfo
- Publication number
- WO1995032588A1 WO1995032588A1 PCT/US1995/003536 US9503536W WO9532588A1 WO 1995032588 A1 WO1995032588 A1 WO 1995032588A1 US 9503536 W US9503536 W US 9503536W WO 9532588 A1 WO9532588 A1 WO 9532588A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- service provider
- message
- ain
- network
- Prior art date
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
-
- 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/0045—Provisions for intelligent networking involving hybrid, i.e. a mixture of public and private, or multi-vendor systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13515—Indexing scheme relating to selecting arrangements in general and for multiplex systems authentication, authorisation - fraud prevention
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13522—Indexing scheme relating to selecting arrangements in general and for multiplex systems traffic management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13526—Indexing scheme relating to selecting arrangements in general and for multiplex systems resource management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13533—Indexing scheme relating to selecting arrangements in general and for multiplex systems multivendor and hybrid, e.g. public/private, networks, inc. international
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13541—Indexing scheme relating to selecting arrangements in general and for multiplex systems routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13561—Indexing scheme relating to selecting arrangements in general and for multiplex systems congestion - inc. overflow
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13566—Indexing scheme relating to selecting arrangements in general and for multiplex systems mediation
Definitions
- the present invention relates to the field of switched telephony and in particular is a method of mediating message content and network impact that will be allowed by providing access to the advanced intelligent network associated with modern telephone switching systems to a wide range of entities other than a telephone service provider.
- a telephone company central office or central office switch is a device to which multiple subscriber lines are connected, each of which is terminated by a telephonic device of a customer. For conventional residential telephone service, one or more telephone sets will be connected to the subscriber line. Additionally, the central office has multiple trunk circuits connecting it to other central offices. Other trunk circuits are provided to customers, such as trunks feeding a private branch exchange (PBX) switch in a business office.
- PBX private branch exchange
- MF signaling is a species of in-band signaling in that the information signals (identification of the called number) was transmitted by signals within the voice frequency band, over the same trunk circuits that carried the voice signal once the call was completed.
- CCIS common channel interoffice signaling
- the identity of the called number can be transmitted over the interoffice signaling data links from the originating central office in Atlanta to the terminating central office in Seattle.
- the terminating central office is the central office that services the called number. If the called number is busy, data providing this information is transmitted back over the interoffice signaling link to the originating central office in Atlanta that locally provides a audible busy signal to the caller. Therefore, no long distance trunk capacity is occupied during this process and the voice circuits between Atlanta and Seattle that formerly would have been used to attempt to complete the call remain free for other uses. If the called number in Seattle is not busy, various devices in the network respond to the information about this call to assign interoffice trunks to set up a connection for the call, and it is then completed.
- the public switched telephone network has evolved in the 1980s to a complex and very versatile system, most of which supports and is controlled by a form of common channel interoffice signaling.
- the basics of this network were designed by AT&T. Development of the network by the Regional Bell Operating Companies (RBOC) as well as other independent local telephone service providers has continued since the judicially mandated divestiture of local exchange carriers by AT&T in 1984.
- the basic architecture of the switched telephone network is, in significant parts, identical throughout the United States and the developed industrialized world including western Europe and Japan.
- the specifics of the current network described in this specification are those employed by the RBOCs and other local exchange carriers operating in the United States.
- This network architecture is used by all modern telephone switching systems in the United States and is virtually identical to modern systems in western Europe and Japan.
- the Advanced Intelligent Network may be thought of as a superset of existing interoffice signaling in that it has the following characteristics. First, it also uses the SS7 protocol. Basically, the Advanced Intelligent Network is the collection of resources and interconnections that cause AIN messages known as triggers to be generated and provide the appropriate responses. A trigger is a particular event that generates a new AIN message sequence. Customers of the local exchange carriers must pay a tariff for having triggers provided to the AIN in connection with particular trigger events. For example, specialized services that relate to inbound calls to a number normally require the customer for that directory number to subscribe to a termination attempt trigger.
- SS7 signaling system 7
- the need for the present invention results from an event that many people familiar with the ' telephone business in the United States believe will be forthcoming in the near future: provision of access to the Advanced Intelligent Networks operated by local exchange carriers to third parties so that they may provide competitive telephone related services to local exchange carrier subscribers.
- the local exchange carriers i.e., the local telephone service providers
- the Advanced Intelligent Network controls many modern features and services offered by telephone companies, i ⁇ ding the setting up and taking down of voice connections.
- Figure 1 of this specification is a block diagram rej enting at least part of the AIN of a typical local exchange c r. While the diagram is simple, the components thereon are known to those skilled in the art.
- a plurality of c: itral of" vitches is provided in a typical public switched t ⁇ 3phone rk.
- a Service Switching Point (SSP) is the AIN c mpone modern central office switch. These are indicated as SSP £ ds 15-15' in Figure 1. The dashed line between these in. ⁇ e that the number is arbitrary.
- non-SSP switches such as switch 16 are also included within the network.
- the former includes intelligent network functionality. This is an indication that the switch is equipped with appropriate hardware and software so that, when a set of predetermined conditions are detected, the switch will initiate a trigger for a predetermined state of a call on a subscriber line, generate the trigger as an appropriate message to be sent out over the AIN, suspend handling of a call until it receives a reply from the network instructing it to take certain action.
- the switch will have a default task to execute if a timeout occurs and no response is provided by the network to the query made by the switch.
- Non-SSP switch 16 is an electronic switch that can generate certain rudimentary packets and provide them over the network, but which must rely on other equipment, described in greater detail hereinbelow, to provide subscriber lines connected to such a switch with more complex features and services available in the intelligent network.
- Central offices 15-15' and 16 each have a plurality of subscriber lines commonly designated as 17-17', connected thereto. Typically, the number of subscriber lines will be on the order of 10,000 to 70,000 lines.
- Each of subscriber lines 17-17' is connected to a terminating piece of customer premises equipment, that is represented by a like plurality of telephone sets 18-18' for each of the switches.
- Interconnecting central office switches 15 and 16 are a plurality of trunk circuits indicated as 19a and 19b in Figure 1. These are the voice path trunks that interconnect the central office and over which calls are connected when completed. It should be understood that central office trunking in a typical urban environment is not limited to a daisy chain arrangement implied by Figure 1. In other words, in a typical network, trunk circuits will exist between central office switch 15' and central office switch 16. Therefore, when a local call is made between two central offices, if a direct trunk connection exists between the offices, and is not busy, the network will assign that trunk to the completion of that particular call. If there is no direct trunking between the two central offices, or the direct trunks are all in use, the call will be routed along trunks from the originating central office to at least one other central office, and through subsequent trunk connections on to the terminating central office.
- Switch 15 through 16 is connected to a local signal transfer point (STP) 20 via respective data links 21a, 21b, and 21c. Cunently, these data links are 56 kilobit per second bidirectional data links employing a signaling protocol referred to as Signaling System 7 (SS7).
- STP local signal transfer point
- SS7 Signaling System 7
- the SS7 protocol is well known to those skilled in the art and is described in a specification promulgated by the American National Standards Institute (ANSI).
- ANSI American National Standards Institute
- the SS7 protocol is a layered protocol wherein each layer provides services for layers above it and relies on the layers below to provide it with services.
- the protocol employs packets that include the usual beginning and terminating flags and a check bit. Additionally, a signal information field is provided that includes a variable length user specific data and a routing label. A service information octet is provided that identifies a priority of the message, the national network of the destination of the message, and the user name identifying the entity that created the message. Also, certain control and sequence numbers are included within the packet, the uses and designations of which are known to those skilled in the art and described in the above referenced ANSI specification.
- STP signal transfer point
- STP 20 is simply a multi-port high speed packet switch that is programmed to respond to the routing information in the appropriate layer of the SS7 protocol, and route the packet to its intended destination.
- the signal transfer point is not normally, per se, the destination of a packet, but merely directs traffic among the other entities on the network that generate and respond to the data packets.
- signal transfer point devices such as STP 20 are conventionally installed in redundant pairs within the network so that if one device fails, its mate takes over until the first STP is able to return to service. In practice, there are redundant data links between each of central office switches 15 through 16 for enhanced reliability.
- Network access point 22 is a computing device programmed to detect trigger conditions. It requires the support of an SSP switch to notify AIN network systems of these trigger detection events.
- An SSP can support multiple NAP switches. Logically, this SSP is designated as the destination address for many of the packets generated by the network that would otherwise be routed to the 1 AESS NAP if it were an SSP equipped switch.
- SCP local service control point
- SCP local service control point
- service control points are physically implemented by relatively powerful fault tolerant computers. Typical implementation devices include the Star Server FT Model 3200 or the Star Server FT Model 3300, both sold by American Telephone & Brass Company. The architectures of these computers are based on Tandem Integrity S2 and Integrity SI platforms, respectively. In most implementations of a public switched telephone network, service control points are also provided in redundant mated pairs in order to assure reliability and continued operation of the network.
- the computing devices implementing service control points typically accommodate one to twenty seven disk drives ranging from 300 megabytes to 1.2 gigabytes per drive, and have main memory on the order of 24 to 192 megabytes. Thus, it will be appreciated that these are large and powerful computing machines.
- the functions performed by the service control points are maintenance of network databases used in providing enhanced services.
- the computers embodying the SCPs can execute at a speed on the order of 17 million instructions per second. Using the SS7 protocol, this translates to about 50 to 100 transactions (query/response pairs) of network messages per second.
- Service control point computers were initially introduced into the network to handle the necessary translations and billing transactions for the implementation of 800 number service, i.e., toll free (to the caller) long distance service.
- An 800 number subscriber has at least one dial-up line number that is to be called when a call to that subscriber's 800 number is placed.
- service control points also include databases for credit card call transactions.
- service control points include databases that identify particular service customers.
- a relatively small set of triggers are defined at the switches for each call.
- a trigger in the network is an event associated with a particular subscriber line that generates a packet to be sent to a service control point.
- the trigger causes the service control point to query its database to determine whether some customized calling feature or enhanced service should be implemented for this particular call, or whether conventional plain dial-up telephone service should be provide for the call.
- the results of the database inquiry are sent back to the switch from SCP 26 through STP 20.
- the return packet includes instructions to the switch as to how to process the call.
- the instruction may be to take some special action as a result of a customized calling service or enhanced feature, or may simply be an indication that there is no entry in its database that indicates that anything other than plain telephone service should be provided for the particular call.
- the switch In response to receiving the latter type message, the switch will move through its call states, collect the called digits, and generate further packets that will be used to set up and route the call, as described hereinabove.
- the regional STP 28 is connected to local STP 20 via an SS7 data link 30.
- the regional STP 28 is connected to the regional SCP 29 via a data link 31 that is physically and functionally the same as data link 27 between the corresponding local devices.
- regional STPs and STCs are provided in mated redundant pairs for the purposes of reliability.
- SMS service management system
- the service management system is also implemented by a large general purpose digital computer and interfaces to business offices of the local exchange carrier and interexchange carriers.
- the service management system downloads information to the databases of the service control points 26 and 29 when subscribers modify their ensemble of AIN services. Similarly, the service management system downloads, on a non-realtime basis, billing information that is needed in order to appropriately invoice telephone company subscribers for the services provided.
- the modern Advanced Intelligent Network also includes service nodes (SNs) such as service node 39 shown in Figure 1.
- service nodes which are physically implemented by the same types of computers that embody the service control points 26 and 29.
- service node 39 also includes voice and DTMF signal recognition devices and voice synthesis devices.
- Service node 39 is connected to service management system 37 via a data link 40 that services the service node in essentially the same way it services SCPs 26 and 29. While service node 39 is physically quite similar to SCP 26, there are some important differences in the uses to which it is put.
- Service control points such as SCP 26 normally implement high volume routing services, such as call forwarding and 800 number translation and routing.
- service control points are only used for database look up and routing services that take place prior to the logical completion of the call, i.e., the provision of a ringing signal to the called subscriber line and ring back to the calling subscriber.
- service nodes such as service node 39
- service node 39 is typically connected to one or more (but normally only a few) switches via Integrated Service Digital Network (ISDN) links shown as 41.
- ISDN Integrated Service Digital Network
- services that are implemented during a call usually employ the facility of a service node such as service node 39.
- voice announcement of a calling party is a custom feature that is implemented via service node 39.
- a subscriber dials the number of another subscriber, Ms. Jones, who subscribes to a service to provide voice announcement of incoming calls.
- One of the call progress states for an SSP equipped switch occurs after collection of the dialed digits when a termination request trigger is generated by the switch.
- This trigger consists of an SS7 data packet that is routed through STP 20 to SCP 26 and identifies the particular called party number.
- the SCP looks up the record for the directory number associated with Ms. Jones' phone line and detects that she is a subscriber to a service that provides voice announcements identifying incoming calls.
- SCP 26 then sends packets back over data link 27 to STP 20 that are routed to both the central office associated with the calling party's subscriber line and that of Ms. Jones.
- the central office of the calling party is instructed to wait or place ring back on the calling party's subscriber line.
- Another packet is routed to switch 15'. It includes the identity of Ms. Jones' directory number, the calling party number, and a request for access to a voice synthesizer channel in service node 37.
- Switch 15' establishes a voice and data circuit over ISDN links 41 with the service node and passes a packet (in an appropriate ISDN format) to the service node.
- the service node queries its database to determine if there is an entry in Ms. Jones' record (actually the record for her directory number) for the particular calling number.
- protocol translation takes place so that the information in these packets is formatted into proper SS7 protocol packets that are then passed on to signal transfer point 20 and routed to appropriate offices to either set up the voice link between the calling party and Ms. Jones' subscriber line, or to provide appropriate audible indication (such as busy or reorder tone) to the calling party.
- the inventor of the present invention believes that opening the network SS7 data links to third parties so that they may provide customized services over the telephone network will be regulated so that the third party providers will not be required to provide extensive information to the local exchange carrier about the nature of the service provided.
- the prospect of opening the network to third party suppliers of enhanced calling services is one that requires careful mediation at the interface between the local exchange earner network and the third party, and monitoring of activity and data packet messages to protect both the integrity and operation of the network and the privacy of all service providers' subscribers.
- the Advanced Intelligent Network is a complex high speed, high traffic volume packet switched messaging arrangement that provides a great deal of versatility in the handling of telephone calls.
- Most network elements, and in particular the SSP switches, are designed so that a relatively simple format of a query message is generated upon certain events and the switch will wait for a response from the network before proceeding with call processing.
- These procedures employ a watchdog timer that will timeout in the event a response to the query is not received.
- timeouts as opposed to a valid response, for a large percentage of the calls being processed, there would be a significant deterioration in the performance of the network. It would cause customers to experience undue delays in call processing or the inability to have enhanced features properly provided.
- the present invention is a method of mediating traffic in packet messages in an intelligent telephone network that includes a plurality of digital data communications channels among a plurality of Advanced Intelligent Network (AIN) elements including a plurality of service switching points at a like plurality of central offices and at least one service control point, that comprises the steps of causing a first one of the plurality of AIN elements that originates a new Transactional Capabilities Application Part (TCAP) message sequence to generate a transaction number for each new TCAP message sequence, causing the first one of the plurality of AIN elements to store the transaction number in a first transaction identifier table, the invention being characterized by said service control point being a mediated service control point that includes a SCP computer running a Shared Execution Environment (SEE) interpreter for processing Local Exchange Carrier applications and Service Provider applications, the method comprising the steps of including the transaction number and a first message identifier in a first TCAP message of said TCAP message sequence and transmitting said first TCAP message to a second one of the plurality of the pluralit
- the present invention is a method of mediating AIN message traffic in an open AIN environment by the use of an instruction language interpreter in a shared execution environment. More particularly, the preferred form of the present invention is accomplished by using an instruction interpreter on a service control point computer that interprets instructions from multiple service provider services (i.e., non ⁇ local exchange carrier providers) wherein the same computer is running service control point applications on behalf of the local exchange carrier.
- An important aspect of the present invention is the use of unique transaction IDs in conversational messages. Transaction and process IDs are already used within the advanced intelligent network (AIN).
- the methodology of the present invention defines the mediated interface between a non-local exchange carrier service provider and the local exchange carrier as the interface between the service provider application program and the shared execution environment (SEE) interpreter.
- the SEE interpreter accepts program language instructions from the service provider application and generates executable calls to the operating system for a service control point computer to generate AIN message packets.
- An important aspect of the present invention is an enhancement of existing interpreter languages to mediate traffic across the boundary between the interpreter and the service provider application.
- the opening of the AIN to non-local exchange carrier service providers creates a tension between the need to have every element in the system, i.e., both local exchange carrier (LEC) applications and service provider applications, unambiguously detect the destination of AIN messages and the appropriate destination for a response on the one hand, and the need to assure that a service provider cannot use access to the AIN to obtain improper access to information about his competitors or somehow sabotage operation of the network or operation of a particular competitor's application on the system.
- the present invention employs the SEE interpreter to maintain transaction identifier tables at a shared execution environment service control point.
- the tables include a list of unique transaction identifiers (transaction IDs) for cunently active transactions.
- Each of these IDs is mapped into a process ID for an application on the service provider's side of the interface.
- the transaction ID table is consulted. If no entry is found, the message is rejected. If an entry is found, the SEE interpreter strips at least the originating point code information from the message and passes the message across the mediated interface to the service provider application with the process identifier attached so that the application can unambiguously determine its process to which the message relates. This isolates the service provider process from information identifying specific point code addresses for the destination of a reply message.
- the method of the present invention causes the AIN element that originates a new conversational message sequence to generate a unique transaction number for the new sequence.
- AIN elements that originate query messages already generate transaction numbers.
- separate SSPs can generate identical transaction numbers since the transaction number is a sequential number generated by the SSP for identifying an SSP transaction.
- existing service control points can be dealing with conversational message sequences for different SSPs that have identical transaction numbers.
- a unique transaction identifier refers to a transaction identifier that is unique across the entire network of the AIN.
- most conversational message sequences are generated by a trigger or query message originating with a service switching point (SSP).
- SSP service switching point
- the unique transaction identifier of the preferred embodiment or message sequence initiated by an SSP trigger is a concatenation of the SSP transaction number that is generated by the service switching point, and an SSP point code is associated with the service switching point and identifies it.
- a subsystem number is included in the u jue transaction identifier to assure its uniqueness if the transaction identifier makes its way across a boundary between local exchange carriers.
- SCP service control point
- the unique transaction identifier is a currently unused random number.
- the statement that the numbers currently unused means that the SCP keeps track of the particular random numbers that have been assigned to transactions that are in progress and, when a random number is requested from a pseudo random number generator, a list is checked to make sure that it does not duplicate the random number of a transaction that is in progress.
- the use of random or pseudo random numbers as transaction identifiers in this instance increases the security of each transaction. It effectively prevents the possibility of an entity with access to the AIN from detecting a pattern in the assignment of transaction identifiers for SCP originated messages and later exploiting that pattern.
- AIN elements that receive a first message, such as when a query message is transmitted to the service control point, concatenation the elements of the unique transaction ID, then add the transaction ID to a table of then-current valid transaction IDs. Subsequently, all AIN messages that are not the first messages in a conversational sequence that are received at the mediated interface cause the table to be c: eked for the message's transaction ID. If it is not present in ,._e table, the message will be rejected by the SCP or other AIN element.
- the message is routed to the shared execution environment interpreter.
- the SEE interpreter selects a process ID for a new process. This process ID is placed in an entry in the SCP transaction identifier table together with the transaction identifier that is used on the local exchange carrier side of the interface.
- the service provider application when it has an outbound message to send affecting this transaction, it includes its process ID in the request for creation of the message that is passed from the application to the SEE interpreter. Assuming the message passes other criteria described hereinbelow, the SEE interpreter checks the transaction ID table and finds the LEC side unique transaction identifier that corresponds to the process identifier for this particular application and includes the transaction number associated with that unique transaction identifier in the outbound reply message. Therefore, the service provider applications cannot have access to the details of the unique transaction identifier, which can include significant information about how the LEC network is being operated. However, the integrity of the process is maintained because the SEE interpreter will never pass the message across the mediated interface to the service provider application unless the transaction identifier in the inbound message is valid.
- a number of lists and tables are maintained in databases stored on disks connected to the service control point computer in a mediated access service control point executing the method of the present invention.
- tables of directory numbers that are customers of each service provider are maintained in the SCP computer.
- a list of authorized network element addresses for each application is likewise maintained in an address table matching service provider applications to sets of authorized network addresses.
- the authorized network element addresses specify the network elements that can be legally addressed by each application.
- Legality relates to the contractual arrangement between the service provider creating and operating the application and the local exchange carrier.
- the service provider wishes to use some of the capability of a service node in providing that service, it needs to make an appropriate contractual arrangement with the local exchange carrier. This will be reflected in an entry in an address table maintained at the mediated SCP indicating that this particular application is an authorized user of the service node. Thus, there will be a table entry identifying the application and pairing it with the network element address for service nodes that may be used under the contract.
- the table of directory numbers for customers is used to validate any request that an AIN message be generated that will in any way reroute or otherwise provide non-standard handling of a call to a particular directory number.
- the entries in the table are also used to select the service provider application for a particular trigger/directory number pair.
- the SEE interpreter enforces the requirement that confirmation of the status of the directory number as a customer of the application making the request be made prior to causing the SCP computer to generate the AIN message requested by the service provider application.
- authorized access to the directory number of a customer implies authorized access to the SSP associated with the switch that handles that directory number.
- the separate table of authorized network element addresses is specifically designed, although not limited to, addresses for non- switch elements such as service nodes and other service control points.
- the mediation process may be used for providing access among databases located in multiple service control points that are operated by non-local exchange carrier entities.
- one service provider could have information in a database and contractually provide access to that database to another service provider whose application is run at a different SCP. This creates an opportunity for the local exchange carrier to obtain revenue from providing the mediation service to protect the integrity of the database and enforce appropriate rules so that others do not obtain similar access to the database without making payment for same.
- the shared execution environment must support a service provider application's request to route a call, which request has a trunk group parameter specifying one or more trunk group route indices. As is known to those skilled in the art these indices specify, normally in an order of preference, the trunk group through which a call should be routed. Since an entity (the service provider application program) over which the LEC has no control can request particular trunk group routings, the SEE interpreter mediates these requests by checking to make sure that the service provider whose application makes a request with a trunk group parameter is contractually authorized to use the trunk group requested. This precludes the chance that an unscrupulous service provider would request trunk routing through tie lines and the like that are leased by another entity in order to reduce its costs and effectively steal services from the entity that leases the trunk.
- the mediation process of the present invention monitors the requests from particular service provider applications for relatively scarce network resources.
- the preferred form is to require the service provider to specify a maximum number of resources of one or more classes that it may occupy simultaneously.
- a list of permitted resource occupancy numbers for the classes of network resources are maintained and an up-down count is maintained by the service control point computers to enforce this limit. If a request for an additional resource in a class above the allowed limit is made, the SEE interpreter will refuse to generate the AIN message that made such a request until the number of such resources occupied by the service provider drops below the permitted occupancy number for that class of resource.
- An additional aspect of the present invention is a method of maintaining an intelligent switched telephone network in the environment of shared access to the advanced intelligent network that controls same.
- AIN message for example from a service management center, is received that requests entry of a new item in the table indicating that an already active trigger should invoke a second service, such entry is refused and an error message is returned to the network element that sent the request. Therefore, one and only one service may be invoked by any trigger for a given directory number.
- FIG. 1 is a diagram of a prior art existing intelligent switched telephone network including the advanced intelligent network that controls same.
- FIG. 2 is a block diagram of some typical elements in the advanced intelligent network and a block diagram of a mediated service control point that performs the method of the preferred embodiment.
- FIG. 3 is a flow diagram for the action of the SEE interpreter of the preferred embodiment upon receiving an inbound message showing how the transaction identifier/service process identifier table is used in the prefened embodiment.
- FIG. 4 is a logical flow diagram of the process of creating a transaction ID with respect to a transaction initiated by a mediated service control point in the prefened of the present invention.
- FIG. 5 is a flow diagram of the steps executed by the shared execution environment interpreter controlling a service control point computer to mediate AIN messages generated by a service provider application in the preferred embodiment.
- FIG 2 shows a subset of the typical AIN network elements that were shown on FIG. 1, which was discussed in connection with the Background of the Invention section above.
- Service node 39 is connected to SSP 15' and voice circuits from its associated switch through ISDN links 41.
- the signal transfer point 20 is connected via SS7 circuit line 27 to the mediated service control point 50.
- applicatior s 56a through 56m Exemplary service provid r appli.... ions are represented as applicatior s 56a through 56m.
- An additional set of local exchange carrier applications are shown as 57a through 57n. It should be understood that m and n in FIG. 2 are r;eant to suggest generalized integers, indicating that there may be an arbitrary number of service provider applications and local f .hange carrier provider applications running on SCP computer 51.
- a logical structure of the application for 56a is shown explicitly in FIG. 2.
- the application includes the instructions of the service provider application, indicated at
- any request for generation of an AIN message that is made by application 58 is first checked by the SEE interpreter 59 to determine if it requires mediation. If it does, appropriate instructions, discussed hereinbelow, are generated by the SEE interpreter to cause processor and operating system 52 to read the required information from disk storage 55 and ascertain whether the AIN message requested by application 58 should be generated. If the mediation process does not indicate any illegal or unauthorized requests, the interpreter generates the calls to the processor and operating system 52 to cause SCP computer 51 to generate the requested message.
- communications between mediated SCP 50 and service node 39 are routed through signal transfer point 20, SSP 15' and are then translated into messages in a protocol for the ISDN to pass over through ISDN link 41 to service node 39.
- SSP 15' may be direct connections between a signal transfer point and a service node in systems that practice the present invention.
- the first message of such a message sequence is refened to as a query.
- a query is identifiable in the protocol Signaling System 7 as a first message in a transaction or new message sequence. This alerts the receiving network element that any transaction ID information contained in this should not necessarily already be in a table. Triggers generated by these service switching points 15 and 15' are the most common form of query messages.
- the SCP computer 51 determines which of applications 56 and 57 should be the recipient of the message based on a table of directory numbers and triggers stored in the database disk drive 55. Using the example of it being intended for service provider application 58 within application 56a, the message is routed to the SEE interpreter 59.
- the SEE interpreter Upon receipt of a query message the SEE interpreter selects a new process ID a request across interface 60 to application 58 requesting that it start a new process. When this is received, the SEE interpreter 59 passes this back to the processor and operating system 52 which then concatenates the transaction number associated with the trigger that was generated by the SSP with the point code for the originating SSP and its system number to create the complete unique transaction ID, and adds an entry into a transaction ID/service process ID table maintained on disk 55.
- the handling of received messages by mediated service control point 50 is illustrated in FIG. 3.
- a typical sequence for initiating and conducting a conversational TCAP message sequence will be described in connection with FIG. 3. Assume the typical situation in which a telephone line connected to the switch associated with SSP 15 has gone off hook and dialed a particular number. While several triggers may be activated during this process, typically a termination attempt trigger is provided when dialing is complete. Such a termination attempt trigger will be activated by the non-LEC service provider when the subscriber for the dialed number is a subscriber to one of the service provider's specialized services.
- a special call forwarding and messaging service can be provided and will typically be invoked by a termination attempt trigger when the customer's directory number is dialed.
- This trigger is an AIN message that is passed over SS7 link 21, through signal transfer point 20 and on through link 27 to mediated SCP 50 (FIG. 2).
- the termination attempt trigger is received by SCP computer 51 which makes an inquiry into a database on disk 55 and determines that the dialed directory number is a customer of the service provider of application 56a and that this application should be notified on a termination attempt trigger. It therefore passes the message (stripped of its address information that routed it to SCP 50) to SEE interpreter 59.
- the handling by SEE interpreter 59 is what is illustrated on FIG. 3.
- the routine is entered at the block 65 labeled message received.
- the interpreter first executes decisional step 66 at which it determines if the inbound message is a query message, i.e., whether it is the first message in a new conversational message sequence. Assume first that it is not a query message and no branch 67 is taken from step 66, which leads to step 68 at which the unique transaction ID is created by the concatenation of the SSP generated transaction number, the originating point code for the SSP that originated the message and the system number. This creates the complete unique transaction ID employed by the prefened embodiment of the present invention.
- decisional step 69 is executed at which SCP computer 51 (FIG. 2) determines if the transaction identifier is already in the active transaction table stored on disk drive 55 (FIG. 2). If it is not, it means that a non-query conversational message has been received from an AIN element employing an invalid transaction number. Therefore, NO branch 70 is taken from step 69 and the message is rejected at step 71. The routine is exited at point 72 after rejection of the message.
- step 69 If the transaction ID already exists in the table, YES branch 75 is taken from step 69 and the routines indicated at block 76 are executed. Since the transaction ID already appears in the table, it follows that an associated service process ID is paired with the transaction ID in the table entry. SCP computer 51 strips the message of its address information, adds the service process identifier to the message and passes it across mediated interface 60 (FIG. 2) to service provider application 58 which then responds in accordance with the instructions written by the service provider in the application. The program then branches to exit point 77 as the handling of this inbound message has been completed.
- the message received at step 65 is a query message, i.e., it is the first message of a new TCAP message sequence, i.e., a trigger message.
- YES branch 78 is taken from decisional step 66.
- the first step is to look up the particular application that handles the particular trigger for the particular directory number identified in the message. This is indicated at step 79.
- one constraint of the present invention is that for each directory number, each trigger can invoke one and only one service.
- the results of the look-up indicated at step 79 could be that this particular trigger for this particular directory number is serviced by either one of service provider applications 56 or local exchange carrier applications 57 indicated on FIG. 2.
- SCP computer 51 passes an instruction to the SEE interpreter 59 indicating that it should assign a new service process identifier for service provider application 58. This is indicated at step 80 in Figure 3.
- the new service process identifier that is unique for the then cunent active processes being executed by the mediated SCP 50.
- step 81 is executed.
- the unique transaction identifier is created by a concatenation of the transaction number, originating point code and subsystem number as described in connection with step 68.
- This unique transaction identifier is coupled with the service process ID obtained at step 80 into a transaction identifier/service process ID pair, and this pair is added to the SCP computer's transaction identifier table stored on disk drive 55 (FIG. 2).
- the substance of the message i.e., the identification of the trigger and the directory number associated with it is passed from SEE interpreter 59 across interface 60 to the service provider application 58. This is indicated at step 82 in FIG. 3. As shown at step 82, the point code for the originating SSP is removed prior to passage of the message across the boundary. Thus, the service provider application is simply told that this message is the message that initiated the new process for which a new service process identifier was just requested, and the service provider application then generates instructions for the
- FIG. 4 a flow diagram of the process of creating a unique transaction ID for message sequences that originate with a first message from a service control point is shown. These steps are executed by the SEE interpreter for instances where the initial message in a TCAP message sequence originates with the service control point. This usually happens in applications of the preferred embodiment, when a service provider application wishes to initiate a conversational message sequence.
- the interpreter detects a valid request for an initial TCAP message from the application, as indicated at step 85.
- a pseudo random number N is requested from the pseudo random number generator provided by the SEE interpreter. Routines for generating long sequences of pseudo random numbers are well known to those skilled in the art.
- the returned pseudo random number N is checked against transaction numbers in the transaction table of cunently active transactions being handled by the SCP. In the unlikely event that the number N is identical to a transaction number for a cunent table entry, YES branch 88 is taken that loops back to step 86, at which another pseudo random number is obtained. If the number N is not identical to an existing transaction number in the transaction table, NO branch 89 is taken to step 90 where the TCAP message is generated using the pseudo random number N as the transaction number.
- the entire transaction ID is stored as part of a transaction ID/service process number pair in the transaction table at step 91.
- the service process number is obtained from the SEE interpreter initially, when the request for an initial TCAP message is detected at step 85.
- the interpreter determines whether access affecting a particular directory number (i.e., a subscriber directory number or a non-switch AIN element) is requested by the message requested by the application. If it is, the directory number table stored in disk drive 55 is checked to determine if the service provider application originating the request is authorized to affect a call to or communicate with this particular directory number. If not, an enor message is generated at step 91 informing the interpreter that it made an invalid request and the message is not sent. At step 95, the message is sent and this portion of the controlling code is exited at point 96.
- a particular directory number i.e., a subscriber directory number or a non-switch AIN element
- An SSP response message sent to the SCP as a result of an SCP originated message simply retums the transaction ID in the SCP originated message. Since response messages are a distinct class of messages (as contrasted to query messages) no concatenation of the transaction ID with the SSP point code is necessary or used in the prefened embodiment. The uniqueness of the transaction ID at the mediation service control point is assured when it is selected by the SEE interpreter.
- FIG. 5 the processes executed by the preferred embodiment for mediating requests from service provider applications for particular types of AIN messages is illustrated. It should be understood that the steps illustrated thereon are executed by the SEE interpreter.
- the inquiries with respect to authorized activities are stored in various tables of the database tables and lists stored on disk drive 55 (FIG. 2).
- This portion of the mediation process is entered at step 110 where the SEE interpreter receives a request for an AIN message from a service provider application.
- the transaction table is consulted for an entry that matches the process ID that accompanied the request generated at step 110.
- the necessary transaction ID information is then obtained from the transaction ID that is coupled with the service process ID in the table entry, which information is used for addressing and routing if the request for the message passes the mediation tests illustrated on Figure 5.
- the first mediation test is decisional step 112 at which it is determined whether the handling of a call to a particular directory number is affected by the message requested by the application. If it is not, NO branch 115 is taken that loops around mediation test 117. If a directory number is affected, YES branch 116 is taken to step 117 where the directory number table stored on disk drive 55 is consulted to see if that particular directory number is a customer of the service provider that owns the application making the request. If the answer is yes, YES branch 118 is taken from step 117 as the message request has passed this first mediation test. If the directory number affected by the request is not a customer of this particular service provider, NO branch 119 will be taken from step 117.
- steps 120 and 121 that are executed if a request for an AIN message fails any mediation test illustrated on Figure 5.
- the message is rejected and at step 121 an appropriate enor message is used to notify the service provider application of the fact of message rejection and, preferably, of the reason for it.
- the mediation process is exited at point 122.
- step 125 This checks whether there is any request for a particular trunk group routing in the request for an AIN message generated by the service provider application. If no trunk group is requested, NO branch 126 is taken that loops around the test for a valid trunk group request. If one or more trunk groups are requested, YES branch 127 is taken from step 125 to step 128. At step 128 the SEE interpreter checks a table of legal trunk group route indices for the particular service provider application that generated the message request. As indicated on the figure, this test is conducted for each trunk group that is specified in the request since multiple trunk groups, that may be used in the alternative, may be specified in a request for trunk group routing.
- NO branch 129 is taken from step 128. This leads to the rejection sequence that commences with step 120. If the service provider application is authorized to use each trunk group contained in the request for a trunk group routing, YES branch 130 is taken from step 128 and the message request has thus far passed the mediation tests.
- the prefened embodiment rejects the message in the event that any request for possible use of an unauthorized trunk group is detected. It is also possible to cause the SEE interpreter to reconstruct the message requested by the service provider application to delete the unauthorized trunk group, but include one or more trunk groups that the service provider application is authorized to use. However, it is considered preferable to place the burden of making proper requests for trunk group routing on the service provider who is responsible for the particular application.
- a non-switch AIN element is requested.
- authorization to affect a call to a particular directory number implies authorization to communicate with the SSP associated with the switch that handles that directory number.
- a separate test is included for message requests that seek access to non-switch AIN elements such as other service control points or service nodes.
- a service node is not an AIN element under cunently installed versions of the Advanced Intelligent Network. This is because service nodes are not cunently connected directly to the AIN, but rather through a switch and ISDN links as illustrated in Figure 1. However, it is logically an AIN element and it is also known that future, already specified enhancements of the software controlling the AIN accommodate SS7 formatted messages being sent to service nodes.
- NO branch 132 is taken that loops around the authorization test. If the message request contains a request for access to a non-switch AIN element, YES branch 135 is taken to step 136, at which a directory number table is consulted to determine if the directory number for the non-switch AIN element is included in a list of authorized directory numbers for this particular service provider application. It should be noted that it is preferable to store designations of the non-switch elements by their directory numbers, which have been conventionally assigned to non-switch AIN elements. The directory number is the preferred way of designating the non-switch element. In this instance, it should be noted that the directory number is not a directory number associated with a particular subscriber line or subscriber leased trunks as is the case with the directory number that is tested at step 112.
- a limited resource As before, if the service provider application is not authorized to access the requested non-switch AIN element, NO branch 137 is taken that leads to message rejection. If the service provider application is authorized, YES branch 138 is taken to step 139 that commences the last mediation test shown on Figure 5. The last test is determined if the message request seeks use of a limited resource.
- the preferred embodiment defines a limited resource as at least one class of network resources of which there is some limited number, and a need to strictly control the time they are occupied by any given service provider. While the concept as used in this specification is not so limited, a limited resource will normally be a device that is involved in an audio connection to a call in real time to process some form of audio signal either provided by a caller or sent to a caller.
- switch digit receivers and voice announcement devices are classified as limited resources. However, other embodiments of the present invention may classify other devices as limited resources and indeed, there can be multiple hierarchical classes of resources defined for an implementation of the present invention. If no limited resource is requested, NO branch 140 is taken, which indicates that the mediation tests have been successfully passed. If this occurs, the AIN message with the appropriate transaction number and address information obtained at step 111 is generated, and the message is sent at step 142. The routine is then exited at step 122.
- YES branch 145 is taken to step 146. This tests whether the service provider application is authorized to use this resource or class of resources. If the request fails this test NO branch 147 is taken to the reject message sequence. If the service provider application is authorized to use the resource, YES branch 148 is taken to step 149 that tests for an important mediation function of the prefened embodiment. Because the class of network resources defined as limited resources by the prefened embodiment are devices that are typically occupied for long periods of time each time they are used, the method of the preferred embodiment places a limitation on the number of such devices that can be occupied simultaneously by a given service provider application or a given service provider. This upper limit is refened to as a resource occupancy number, and is simply a predetermined number of the limited resource devices that may be occupied simultaneously by the service provider or its application.
- the resource occupancy number not only by a maximum tolerable number, given the number of service providers that are accommodated, but to scale the number in accordance with a tariff.
- service providers that anticipate making high volume use of voice announcing equipment will need to pay a higher tariff to the local exchange carrier for its provision of access to these resources so that the service provider can occupy a relatively large number of them simultaneously.
- the resource occupancy number there is an alternate way of defining the resource occupancy number that may be used in lieu of or in addition to a total number of limited resources or a class of resources.
- the method of the present invention defines a resource occupancy number that is a predetermined maximum limit on the number of limited resources that may be simultaneously occupied by a service provider application.
- the system maintains a limited resource count as an up/down count for each service provider application. If step 149 is reached, the SEE interpreter tests whether the limited resource count for this particular service provider application currently exceeds the resource occupancy number for that application. If this test is true, YES branch 150 is taken to the reject message sequence. It is incumbent upon the service provider writing the application to address issues of retry attempts and the like in order to provide the service to its customer that requires the use of the limited resource, the request for which has just been rejected at step 149.
- step 152 At which the limited resource count is incremented.
- all mediation tests have been passed and the message is generated and sent at steps 141 and 142, respectively, as previously described.
- other routines for handling the termination of conversations which are not illustrated in the drawing figures, are responsible for decrementing the limited resource count whenever the user of a limited resource as requested by the particular service provider application has been completed. Implementation of such an up/down counting scheme is simple and well known to those skilled in the art.
- the methods described herein provide effective mediation across the mediated interface between service provider applications and a shared execution environment interpreter that is run at an LEC operated service control point.
- the use of the unique transaction identifiers in the transaction identifier/service process number pair table effectively isolates the service providers from access to sensitive information concerning the local exchange earner's operation of the network as well as potential access to information about the service provider's competitors.
- the mediation steps illustrated in Figure 5 assure the integrity of messages generated by service provider applications. Furthermore, they enforce local exchange carrier tariffing of certain privileges within the AIN that are granted to service providers and cause local exchange carriers to expend money to support such privileges. This prevents any particular service provider from tying up an inordinate percentage of certain types of resources in the network to the detriment of customers of other service providers as well as to the detriment of the local exchange carrier.
Abstract
Description
Claims
Priority Applications (9)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AT95914793T ATE205989T1 (en) | 1994-05-20 | 1995-03-21 | PROVIDING AN ADVANCED INTELLIGENT NETWORK INTERFACE USING A SHARED EXECUTION ENVIRONMENT |
DK95914793T DK0765579T3 (en) | 1994-05-20 | 1995-03-21 | Providing an advanced intelligent network interface using a split execution environment |
MX9605634A MX9605634A (en) | 1995-03-21 | 1995-03-21 | Mediation of open advanced intelligent network interface by shared execution environment. |
NZ283562A NZ283562A (en) | 1994-05-20 | 1995-03-21 | Advanced intelligent network of telephony carrier open to other service providers through shared execution environment |
DE69522805T DE69522805T2 (en) | 1994-05-20 | 1995-03-21 | MEDIATION OF AN ADVANCED INTELLIGENT NETWORK INTERFACE WITH THE help of a shared execution environment |
CA002189264A CA2189264C (en) | 1994-05-20 | 1995-03-21 | Mediation of open advanced intelligent network interface by shared execution environment |
JP7530270A JP3011461B2 (en) | 1994-05-20 | 1995-03-21 | Traffic routing of packet messages in intelligent switched telephone networks. |
AU21894/95A AU699654B2 (en) | 1994-05-20 | 1995-03-21 | Mediation of open advanced intelligent network interface by shared execution environment |
EP95914793A EP0765579B1 (en) | 1994-05-20 | 1995-03-21 | Mediation of open advanced intelligent network interface by shared execution environment |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/246,876 US5430719A (en) | 1993-06-28 | 1994-05-20 | Mediation of open advanced intelligent network interface by shared execution environment |
US08/246,876 | 1994-05-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1995032588A1 true WO1995032588A1 (en) | 1995-11-30 |
Family
ID=22932620
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1995/003536 WO1995032588A1 (en) | 1994-05-20 | 1995-03-21 | Mediation of open advanced intelligent network interface by shared execution environment |
Country Status (12)
Country | Link |
---|---|
US (1) | US5430719A (en) |
EP (5) | EP1005236B1 (en) |
JP (1) | JP3011461B2 (en) |
AT (5) | ATE226779T1 (en) |
AU (1) | AU699654B2 (en) |
CA (1) | CA2189264C (en) |
DE (5) | DE69528675T2 (en) |
DK (1) | DK0765579T3 (en) |
ES (1) | ES2167426T3 (en) |
NZ (1) | NZ283562A (en) |
PT (1) | PT765579E (en) |
WO (1) | WO1995032588A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6016307A (en) * | 1996-10-31 | 2000-01-18 | Connect One, Inc. | Multi-protocol telecommunications routing optimization |
Families Citing this family (199)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5353331A (en) | 1992-03-05 | 1994-10-04 | Bell Atlantic Network Services, Inc. | Personal communications service using wireline/wireless integration |
DE69530534T2 (en) * | 1994-02-25 | 2004-03-18 | Hewlett-Packard Co. (N.D.Ges.D.Staates Delaware), Palo Alto | Message receiving circuit for a signaling network |
CA2153281C (en) * | 1994-07-08 | 2000-05-16 | Ronald Schwartz | Mediated access to an intelligent network |
US5537467A (en) * | 1994-08-23 | 1996-07-16 | Bell Communications Research, Inc. | Method for forwarding a call to a temporarily utilized portable telephone |
US5705998A (en) * | 1994-08-24 | 1998-01-06 | Siemens Aktiengesellschaft | Method for routing telecommunication calls in a network |
US5570410A (en) * | 1994-10-13 | 1996-10-29 | Bellsouth Corporation | Dynamic resource allocation process for a service control point in an advanced intelligent network system |
US5579371A (en) * | 1994-11-22 | 1996-11-26 | Unisys Corporation | Common channel signaling network applications platform |
US5574782A (en) * | 1995-04-14 | 1996-11-12 | Lucent Technologies Inc. | Minimizing service disruptions in handling call request messages where new message formats are needed in a telecommunication network |
US5870460A (en) * | 1995-05-31 | 1999-02-09 | Mci Communications Corporation | System for least cost routing of data transactions in a telecommunications network |
US5721843A (en) * | 1995-08-31 | 1998-02-24 | Lucent Technologies Inc. | Optimizing network utilization by using image reconstruction techniques |
US5566235A (en) * | 1995-10-05 | 1996-10-15 | Bell Atlantic Network Services, Inc. | Customer controlled service mediation management |
US5835583A (en) * | 1995-10-05 | 1998-11-10 | Bell Atlantic Network Services, Inc. | Mediated AIN control of short code access to information service providers |
GB9603582D0 (en) | 1996-02-20 | 1996-04-17 | Hewlett Packard Co | Method of accessing service resource items that are for use in a telecommunications system |
US5712908A (en) * | 1995-12-22 | 1998-01-27 | Unisys Corporation | Apparatus and method for generating call duration billing records utilizing ISUP messages in the CCS/SS7 telecommunications network |
WO1997031473A1 (en) * | 1996-02-23 | 1997-08-28 | Bell Communications Research, Inc. | Distributed service management system and method for personal communication services |
US6154445A (en) | 1996-04-18 | 2000-11-28 | Bell Atlantic Network Services, Inc. | Telephony communication via varied redundant networks |
US6069890A (en) * | 1996-06-26 | 2000-05-30 | Bell Atlantic Network Services, Inc. | Internet telephone service |
EP0810800A3 (en) * | 1996-05-28 | 2001-01-03 | Siemens Aktiengesellschaft | Method for connecting subscribers to the communication systems of a plurality of network service providers |
US5867570A (en) * | 1996-07-29 | 1999-02-02 | Northern Telecom Limited | Directory number portability in telephone networks |
US7187686B1 (en) * | 1996-11-01 | 2007-03-06 | Sbc Properties, B.P. | Telecommunication system, method and subscriber unit for use therein |
US6370149B1 (en) * | 1998-07-20 | 2002-04-09 | Ameritech Corporation | Telecommunication system, method and subscriber unit for use therein |
US6052458A (en) * | 1996-11-22 | 2000-04-18 | Lucent Technologies Inc. | Method for message marking and detection of message looping among signaling networks in a telecommunications system |
US5974128A (en) * | 1996-11-27 | 1999-10-26 | Ameritech Corporation | Method and system for providing calling name identification requery |
US6891939B1 (en) * | 1996-11-27 | 2005-05-10 | Sbc Properties, L.P. | Method and system for providing calling name identification with advanced intelligent network |
US5982867A (en) | 1996-11-27 | 1999-11-09 | Ameritech Corporation | Method and system for providing the name of the state of a calling party |
US6078582A (en) | 1996-12-18 | 2000-06-20 | Bell Atlantic Network Services, Inc. | Internet long distance telephone service |
US6072857A (en) * | 1996-12-19 | 2000-06-06 | Bellsouth Intellectual Property Management Corporation | Methods and system for monitoring the operational status of a network component in an advanced intelligent network |
US5940187A (en) | 1997-01-06 | 1999-08-17 | Bellsouth Corporation | Method for certifying facsimile communications over a telephone network |
US6044274A (en) * | 1997-02-13 | 2000-03-28 | Telefonaktiebolaget Lm Ericsson | Handling of mobile originated intelligent network calls from a non-intelligent capable mobile switching center |
US5946684A (en) | 1997-02-18 | 1999-08-31 | Ameritech Corporation | Method and system for providing computer-network related information about a calling party |
US5978806A (en) * | 1997-02-18 | 1999-11-02 | Ameritech Corporation | Method and apparatus for communicating information about a called party to a calling party |
US6137869A (en) | 1997-09-16 | 2000-10-24 | Bell Atlantic Network Services, Inc. | Network session management |
US6574216B1 (en) | 1997-03-11 | 2003-06-03 | Verizon Services Corp. | Packet data network voice call quality monitoring |
US6216168B1 (en) * | 1997-03-17 | 2001-04-10 | Cabletron Systems, Inc. | Perspective-based shared scope address resolution method and apparatus |
US6870827B1 (en) * | 1997-03-19 | 2005-03-22 | Verizon Services Corp. | Voice call alternative routing through PSTN and internet networks |
US6292479B1 (en) | 1997-03-19 | 2001-09-18 | Bell Atlantic Network Services, Inc. | Transport of caller identification information through diverse communication networks |
US5953404A (en) * | 1997-04-11 | 1999-09-14 | Stentor Resource Centre, Inc. | Method and system for providing mediated access between signaling networks |
US6286011B1 (en) * | 1997-04-30 | 2001-09-04 | Bellsouth Corporation | System and method for recording transactions using a chronological list superimposed on an indexed list |
SE512270C2 (en) | 1997-04-30 | 2000-02-21 | Ericsson Telefon Ab L M | Methods and systems for use in a telecommunications network |
US5943409A (en) * | 1997-07-11 | 1999-08-24 | Bellsouth Intellectual Property Corporation | Method and system for providing automatic recall information in a telecommunications network |
US5949763A (en) * | 1997-07-17 | 1999-09-07 | Ameritech Corporation | Method and apparatus for providing broadband access conferencing services |
US7149514B1 (en) | 1997-07-30 | 2006-12-12 | Bellsouth Intellectual Property Corp. | Cellular docking station |
US6480714B1 (en) | 1997-07-30 | 2002-11-12 | Bellsouth Intellectual Property Corporation | Cellular docking station |
US20080207197A1 (en) | 1997-07-30 | 2008-08-28 | Steven Tischer | Apparatus, method, and computer-readable medium for interfacing devices with communications networks |
US7194083B1 (en) | 2002-07-15 | 2007-03-20 | Bellsouth Intellectual Property Corporation | System and method for interfacing plain old telephone system (POTS) devices with cellular networks |
US6173049B1 (en) | 1997-08-11 | 2001-01-09 | Bellsouth Intellectual Property Corporation | System and method for automated provision and customer selection of temporary caller identification services |
US6188757B1 (en) | 1997-08-11 | 2001-02-13 | Bellsouth Intellectual Property Corporation | System and method for automatic provision customer selection, and deactivation of temporary advance intelligent network services |
US6173047B1 (en) | 1997-08-11 | 2001-01-09 | Dale W. Malik | System and method for temporary voicemail service |
US6181787B1 (en) | 1997-08-11 | 2001-01-30 | Bellsouth Intellectual Property Corporation | System and method for automated provision and customer selection of temporary advanced intelligent network services |
AU9089698A (en) * | 1997-09-25 | 1999-04-12 | British Telecommunications Public Limited Company | Signaling method in a telecommunications network |
US6148069A (en) * | 1997-11-04 | 2000-11-14 | Ameritech Corporation | System and method for mixed mode communications in an advanced intelligent network telephone system |
US6141356A (en) * | 1997-11-10 | 2000-10-31 | Ameritech Corporation | System and method for distributing voice and data information over wireless and wireline networks |
US6687707B1 (en) | 1997-11-28 | 2004-02-03 | International Business Machines Corporation | Unique object identification in a network of computing systems |
US6041112A (en) * | 1997-12-02 | 2000-03-21 | Bellsouth Intellectual Property Corporation | Method for transferring switch-based information to an external network element |
US6137806A (en) * | 1997-12-22 | 2000-10-24 | Northern Telecom Limited | Intelligent network with alternate routing of signalling messages, and method of operating such network |
US6332022B1 (en) | 1997-12-22 | 2001-12-18 | Nortel Networks Limited | Method and apparatus for routing emergency services calls in an intelligent network |
US7590133B2 (en) * | 1998-02-24 | 2009-09-15 | Canon Kabushiki Kaisha | Data communication system, data communication method, and data communication apparatus |
US6167129A (en) * | 1998-04-03 | 2000-12-26 | Tekelec | Method and apparatus for signal mediation in a common channel signaling network |
US6295351B1 (en) | 1998-04-23 | 2001-09-25 | Bellsouth Intellectual Propety Corporation | System and method for invocation of a check of a telecommunications application through use of a call probe |
ES2242401T3 (en) * | 1998-05-08 | 2005-11-01 | Siemens Aktiengesellschaft | PROCEDURE FOR CONTROL OF TELECOMMUNICATIONS SERVICES. |
US6154535A (en) * | 1998-05-15 | 2000-11-28 | Bellsouth Corporation | Methods and system for obtaining processing information relating to a communication |
US6301349B1 (en) | 1998-06-04 | 2001-10-09 | Bellsouth Intellectual Property Corporation | Method and system to connect an unanswered forwarded communication directly to a voice mail service |
US7545760B1 (en) | 1998-06-30 | 2009-06-09 | At&T Intellectual Property I, L.P. | Methods and systems for providing an extension service to wireless units and wireline units |
US6463130B1 (en) * | 1998-07-31 | 2002-10-08 | Bellsouth Intellectual Property Corporation | Method and system for creating automated voice response menus for telecommunications services |
US6275872B1 (en) * | 1998-10-20 | 2001-08-14 | Bellsouth Intellectual Property Corporation | Method for performing migration of uninitialized entries from a storage to a repository within an intelligent peripheral in an advanced intelligent network |
FI106596B (en) * | 1998-10-30 | 2001-02-28 | Nokia Networks Oy | Interaction of services in a telecommunications network |
US7394897B1 (en) | 1998-11-04 | 2008-07-01 | At&T Delaware Intellectual Property, Inc. | Method and system for routing service calls made from resold lines |
US6442169B1 (en) | 1998-11-20 | 2002-08-27 | Level 3 Communications, Inc. | System and method for bypassing data from egress facilities |
US6614781B1 (en) | 1998-11-20 | 2003-09-02 | Level 3 Communications, Inc. | Voice over data telecommunications network architecture |
US6252954B1 (en) | 1998-11-20 | 2001-06-26 | Bellsouth Intellectual Property Corporation | System and method for delaying the ringing of a line |
NL1010625C2 (en) * | 1998-11-23 | 2000-05-24 | Koninkl Kpn Nv | Communication structure. |
US6654453B1 (en) | 1998-12-03 | 2003-11-25 | Bellsouth Intellectual Property Corporation | Method and system for minimizing database structure overhead in handling large volume advanced intelligent network services |
US6606505B1 (en) | 1998-12-31 | 2003-08-12 | At&T Corp. | Wireless centrex call screen |
US6654603B1 (en) | 1998-12-31 | 2003-11-25 | At&T Corp. | Call waiting in a wireless centrex system |
US6745025B1 (en) | 1998-12-31 | 2004-06-01 | At&T Corp. | Time-of-day call forwarding in a wireless centrex services system |
US6618600B1 (en) | 1998-12-31 | 2003-09-09 | At&T Corp. | Distinctive ringing in a wireless centrex system |
US6631258B1 (en) | 1998-12-31 | 2003-10-07 | At&T Corp. | Busy call forwarding in a wireless centrex services system |
US6738615B1 (en) | 1998-12-31 | 2004-05-18 | At&T Corp. | Wireless centrex caller ID |
US6711401B1 (en) | 1998-12-31 | 2004-03-23 | At&T Corp. | Wireless centrex call return |
US6606493B1 (en) | 1998-12-31 | 2003-08-12 | At&T Corp. | Wireless centrex conference call deleting a party |
US6771953B1 (en) | 1998-12-31 | 2004-08-03 | At&T Corp. | Wireless centrex call transfer |
US6819945B1 (en) | 1998-12-31 | 2004-11-16 | At&T Corp. | Wireless centrex feature activation/deactivation |
US6654615B1 (en) | 1998-12-31 | 2003-11-25 | Albert Chow | Wireless centrex services |
US6785560B1 (en) | 1998-12-31 | 2004-08-31 | At&T Corp. | Speed calling in a wireless centrex system |
US6587683B1 (en) * | 1998-12-31 | 2003-07-01 | At&T Corp. | Unconditional call forwarding in a wireless centrex services system |
US6643507B1 (en) | 1998-12-31 | 2003-11-04 | At&T Corp. | Wireless centrex automatic callback |
US6591115B1 (en) | 1998-12-31 | 2003-07-08 | At&T Corp. | Wireless centrex call hold |
US6791971B1 (en) * | 1999-03-10 | 2004-09-14 | Nortel Networks Limited | Method and apparatus for providing a communications service, for communication and for extending packet network functionality |
US6411802B1 (en) | 1999-03-15 | 2002-06-25 | Bellsouth Intellectual Property Management Corporation | Wireless backup telephone device |
US6873691B1 (en) | 1999-04-06 | 2005-03-29 | Bellsouth Intellectual Property Corporation | Methods and systems for using the public switched telephone network to conduct a transaction between customer accounts |
US6532285B1 (en) * | 1999-04-14 | 2003-03-11 | Bellsouth Intellectual Property Corporation | Method and system for providing multiple services per trigger |
US6335936B1 (en) | 1999-04-22 | 2002-01-01 | Ameritech Corporation | Wide area communication networking |
US6285671B1 (en) * | 1999-04-22 | 2001-09-04 | Ameritech Corporation | Method and system for providing facsimile service over a digital subscriber line |
US6560327B1 (en) | 1999-10-01 | 2003-05-06 | Sprint Spectrum, L.P. | Method and system for providing telecommunications services using mediated service logic |
US6738458B1 (en) | 1999-11-09 | 2004-05-18 | Bell South Intellectual Property Corporation | Methods and systems for changing the domain association of a mailbox in a messaging system |
US6532490B1 (en) | 1999-11-10 | 2003-03-11 | Bellsouth Intellectual Property Corporation | Methods and elements to reduce the number of quieries to a foreign network element |
DE19954694A1 (en) * | 1999-11-13 | 2001-05-23 | Alcatel Sa | System for Internet service function module selection has a graphical user interface with symbols for procedure modules used to create packet network messages |
US6687351B1 (en) | 1999-12-07 | 2004-02-03 | Bellsouth Intellectual Property Corporation | Method for providing telephone services for commercial classes of service |
US7092505B2 (en) * | 1999-12-23 | 2006-08-15 | Tekelec | Methods and systems for universal, automatic service selection in a telecommunications signaling network |
US6775708B1 (en) * | 2000-02-08 | 2004-08-10 | Microsoft Corporation | Identification of transactional boundaries |
US6721415B1 (en) * | 2000-02-17 | 2004-04-13 | Bellsouth Intellectual Property Corporation | Telephone voice messaging system and method using off-hook immediate trigger |
US6944150B1 (en) * | 2000-02-28 | 2005-09-13 | Sprint Communications Company L.P. | Method and system for providing services in communications networks |
US7324635B2 (en) * | 2000-05-04 | 2008-01-29 | Telemaze Llc | Branch calling and caller ID based call routing telephone features |
US7433459B2 (en) * | 2000-06-19 | 2008-10-07 | Verizon Services Corp. | Methods and apparatus for providing telephone support for internet sales |
US7224686B1 (en) | 2000-06-30 | 2007-05-29 | Verizon Services Corp. | Method of and apparatus for mediating common channel signaling messages between networks using a pseudo-switch |
US7184538B1 (en) | 2000-06-30 | 2007-02-27 | Verizon Services Corp. | Method of and apparatus for mediating common channel signaling message between networks using control message templates |
US7360090B1 (en) | 2000-06-30 | 2008-04-15 | Verizon Services Corp. | Method of and apparatus for authenticating control messages in a signaling network |
US6826529B1 (en) | 2000-08-09 | 2004-11-30 | Bellsouth Intellectual Property Corporation | Network and method for providing a call screening telecommunications service with automatic speech recognition capability |
US6907111B1 (en) | 2000-08-09 | 2005-06-14 | Bellsouth Intellectual Property Corporation | Network and method for providing a name and number delivery telecommunications services with automatic speech recognition capability |
US6505163B1 (en) | 2000-08-09 | 2003-01-07 | Bellsouth Intellectual Property Corporation | Network and method for providing an automatic recall telecommunications service with automatic speech recognition capability |
US6993119B1 (en) | 2000-08-09 | 2006-01-31 | Bellsouth Intellectual Property Corporation | Network and method for providing a flexible call forwarding telecommunications service with automatic speech recognition capability |
US6778640B1 (en) | 2000-08-09 | 2004-08-17 | Bellsouth Intellectual Property Corporation | Network and method for providing a user interface for a simultaneous ring telecommunications service with automatic speech recognition capability |
US6873686B1 (en) | 2000-08-09 | 2005-03-29 | Bellsouth Intellectual Property Corporation | Network and method for providing a calling name telecommunications service with automatic speech recognition capability |
US7082300B1 (en) | 2000-08-29 | 2006-07-25 | Bellsouth Intellectual Property Corp. | Roaming virtual long distance |
US6823056B1 (en) | 2000-09-01 | 2004-11-23 | Bellsouth Intellectual Property Corporation | Multiple services per trigger within a telecommunications network |
US7320019B2 (en) * | 2000-11-30 | 2008-01-15 | At&T Delaware Intellectual Property, Inc. | Method and apparatus for automatically checking e-mail addresses in outgoing e-mail communications |
US6771755B1 (en) | 2000-11-30 | 2004-08-03 | Bellsouth Intellectual Property Corporation | Personalized caller identification in a telephone network |
US6788775B1 (en) | 2000-12-11 | 2004-09-07 | Bellsouth Intellectual Property Corporation | System and method for passcode validation during telephone call processing |
US6748064B2 (en) | 2000-12-28 | 2004-06-08 | Bellsouth Intellectual Property Corporation | Systems and methods for least cost routing of long distance or international telephone calls |
US7388949B2 (en) | 2000-12-28 | 2008-06-17 | At&T Delaware Intellectual Property, Inc. | System and method for audio caller identification service |
US7283811B2 (en) * | 2001-02-23 | 2007-10-16 | Lucent Technologies Inc. | System and method for aggregation of user applications for limited-resource devices |
EP1379983A2 (en) * | 2001-02-23 | 2004-01-14 | Mobilitec, Inc. | System and method for charging for directed provisioning of user applications on limited-resource devices |
US7330717B2 (en) * | 2001-02-23 | 2008-02-12 | Lucent Technologies Inc. | Rule-based system and method for managing the provisioning of user applications on limited-resource and/or wireless devices |
US7254226B1 (en) | 2001-05-08 | 2007-08-07 | At&T Intellectual Property, Inc. | Call waiting priority alert |
US6944594B2 (en) | 2001-05-30 | 2005-09-13 | Bellsouth Intellectual Property Corporation | Multi-context conversational environment system and method |
US7085358B2 (en) | 2001-06-25 | 2006-08-01 | Bellsouth Intellectual Property Corporation | Visual caller identification |
US7012999B2 (en) | 2001-06-25 | 2006-03-14 | Bellsouth Intellectual Property Corporation | Audio caller identification |
US7298835B1 (en) | 2001-06-26 | 2007-11-20 | At&T Bls Intellectual Property, Inc. | Systems and methods for implementing a parental control feature within a telecommunications network |
US7315614B2 (en) | 2001-08-14 | 2008-01-01 | At&T Delaware Intellectual Property, Inc. | Remote notification of communications |
US7403768B2 (en) | 2001-08-14 | 2008-07-22 | At&T Delaware Intellectual Property, Inc. | Method for using AIN to deliver caller ID to text/alpha-numeric pagers as well as other wireless devices, for calls delivered to wireless network |
WO2003017599A1 (en) * | 2001-08-16 | 2003-02-27 | Tekelec | Methods and systems for providing end office support in a signaling network |
US7197036B2 (en) * | 2001-08-16 | 2007-03-27 | Tekelec Us | Methods and systems for routing messages between a mated pair of routing nodes with a distributed processing architecture and one or more redundantly connected remote applications |
US6937710B1 (en) * | 2001-08-24 | 2005-08-30 | Bellsouth Intellectual Property Corporation | Methods and systems for providing usage pattern service for telecommunications customers |
US6813348B1 (en) * | 2001-09-06 | 2004-11-02 | Bellsouth Intellectual Property Corporation | Method and system of call origination using a service circuit node in an advanced intelligent network |
US7269249B2 (en) | 2001-09-28 | 2007-09-11 | At&T Bls Intellectual Property, Inc. | Systems and methods for providing user profile information in conjunction with an enhanced caller information system |
US7079837B1 (en) * | 2001-11-06 | 2006-07-18 | Bellsouth Intellectual Property Corporation | Caller identification queue for wireless telephones |
US7120454B1 (en) * | 2001-12-26 | 2006-10-10 | Bellsouth Intellectual Property Corp. | Auto sensing home base station for mobile telephone with remote answering capabilites |
US7315618B1 (en) | 2001-12-27 | 2008-01-01 | At&T Bls Intellectual Property, Inc. | Voice caller ID |
US7385992B1 (en) | 2002-05-13 | 2008-06-10 | At&T Delaware Intellectual Property, Inc. | Internet caller-ID integration |
US7586898B1 (en) | 2002-05-13 | 2009-09-08 | At&T Intellectual Property, I, L.P. | Third party content for internet caller-ID messages |
US8526466B2 (en) | 2002-07-15 | 2013-09-03 | At&T Intellectual Property I, L.P. | Apparatus and method for prioritizing communications between devices |
US8416804B2 (en) | 2002-07-15 | 2013-04-09 | At&T Intellectual Property I, L.P. | Apparatus and method for providing a user interface for facilitating communications between devices |
US7200424B2 (en) | 2002-07-15 | 2007-04-03 | Bellsouth Intelectual Property Corporation | Systems and methods for restricting the use and movement of telephony devices |
US8543098B2 (en) | 2002-07-15 | 2013-09-24 | At&T Intellectual Property I, L.P. | Apparatus and method for securely providing communications between devices and networks |
US8000682B2 (en) | 2002-07-15 | 2011-08-16 | At&T Intellectual Property I, L.P. | Apparatus and method for restricting access to data |
US8554187B2 (en) | 2002-07-15 | 2013-10-08 | At&T Intellectual Property I, L.P. | Apparatus and method for routing communications between networks and devices |
US8275371B2 (en) | 2002-07-15 | 2012-09-25 | At&T Intellectual Property I, L.P. | Apparatus and method for providing communications and connection-oriented services to devices |
US7139374B1 (en) | 2002-07-23 | 2006-11-21 | Bellsouth Intellectual Property Corp. | System and method for gathering information related to a geographical location of a callee in a public switched telephone network |
US7623645B1 (en) | 2002-07-23 | 2009-11-24 | At&T Intellectual Property, I, L.P. | System and method for gathering information related to a geographical location of a caller in a public switched telephone network |
CA2400548A1 (en) * | 2002-08-30 | 2004-02-29 | Catena Networks Canada Inc. | Call control system for the dynamic migration of subscribers from legacy access networks to next-generation packet networks |
US7170989B1 (en) * | 2002-09-06 | 2007-01-30 | Sprint Communications Company L.P. | Transaction dependency manager |
US7848767B2 (en) | 2002-10-15 | 2010-12-07 | Tekelec | Methods and systems for migrating between application layer mobile signaling protocols |
US7283625B2 (en) | 2003-04-18 | 2007-10-16 | At&T Bls Intellectual Property, Inc. | Caller ID messaging telecommunications services |
US7443964B2 (en) | 2003-04-18 | 2008-10-28 | At&T Intellectual Property, I,L.P. | Caller ID messaging |
US7280646B2 (en) | 2003-04-18 | 2007-10-09 | At&T Bls Intellectual Property, Inc. | Dynamic Caller ID messaging |
US7463727B2 (en) | 2003-04-18 | 2008-12-09 | At&T International Property, I, L.P. | Caller ID messaging device |
US7978833B2 (en) | 2003-04-18 | 2011-07-12 | At&T Intellectual Property I, L.P. | Private caller ID messaging |
US7269412B2 (en) | 2003-05-29 | 2007-09-11 | At&T Bls Intellectual Property, Inc. | Caller identification device and method of operation thereof |
US7609832B2 (en) | 2003-11-06 | 2009-10-27 | At&T Intellectual Property, I,L.P. | Real-time client survey systems and methods |
US7623849B2 (en) * | 2003-11-13 | 2009-11-24 | At&T Intellectual Property, I, L.P. | Method, system, and storage medium for providing comprehensive originator identification services |
US7672444B2 (en) | 2003-12-24 | 2010-03-02 | At&T Intellectual Property, I, L.P. | Client survey systems and methods using caller identification information |
US20060002403A1 (en) * | 2004-06-30 | 2006-01-05 | Glenayre Electronics, Inc. | Distributed IP architecture for telecommunications system |
US8195136B2 (en) | 2004-07-15 | 2012-06-05 | At&T Intellectual Property I, L.P. | Methods of providing caller identification information and related registries and radiotelephone networks |
US20070002367A1 (en) * | 2005-06-29 | 2007-01-04 | Eric Yuan | Methods and apparatuses for selectively controlling a remote device |
US7889716B2 (en) | 2005-12-01 | 2011-02-15 | Tekelec | Methods, systems, and computer program products for using an E.164 number (ENUM) database for message service message routing resolution among 2G and subsequent generation network systems |
EP1989894B1 (en) * | 2006-02-15 | 2019-02-13 | Tekelec Global, Inc. | Methods, systems, and computer program products for selectively processing or redirecting signaling connection control part (sccp) messages |
US20080018649A1 (en) * | 2006-07-18 | 2008-01-24 | Zheng Yuan | Methods and apparatuses for utilizing an application on a remote device |
US8185605B2 (en) * | 2006-07-18 | 2012-05-22 | Cisco Technology, Inc. | Methods and apparatuses for accessing an application on a remote device |
US7787445B2 (en) | 2006-07-20 | 2010-08-31 | Tekelec | Methods, systems, and computer program products for routing and processing ENUM queries |
US8254551B2 (en) * | 2006-12-07 | 2012-08-28 | Tekelec, Inc. | Methods, systems, and computer program products for providing quality of service using E.164 number mapping (ENUM) data in a communications network |
WO2008113054A2 (en) * | 2007-03-14 | 2008-09-18 | Zonit Structured Solutions, Llc | Data center network distribution system |
US8848722B2 (en) * | 2007-03-14 | 2014-09-30 | Zonit Structured Solutions, Llc | Data center network distribution system |
US7706368B2 (en) * | 2007-04-06 | 2010-04-27 | Research In Motion Limited | System and method for correlating messages within a wireless transaction |
US20080281760A1 (en) * | 2007-04-30 | 2008-11-13 | Bellsouth Intellectual Property Corporation | Service Negotiation |
US7996541B2 (en) * | 2007-06-15 | 2011-08-09 | Tekelec | Methods, systems, and computer program products for identifying a serving home subscriber server (HSS) in a communications network |
US8538000B2 (en) | 2007-08-10 | 2013-09-17 | Tekelec, Inc. | Methods, systems, and computer program products for performing message deposit transaction screening |
US8243909B2 (en) | 2007-08-22 | 2012-08-14 | At&T Intellectual Property I, L.P. | Programmable caller ID |
US8160226B2 (en) | 2007-08-22 | 2012-04-17 | At&T Intellectual Property I, L.P. | Key word programmable caller ID |
EP2258128B1 (en) | 2008-03-07 | 2017-01-11 | Tekelec Global, Inc. | Methods, systems, and computer readable media for routing a message service message through a communications network |
WO2010060087A2 (en) | 2008-11-24 | 2010-05-27 | Tekelec | Systems, methods, and computer readable media for location-sensitive called-party number translation in a telecommunications network |
US9021014B2 (en) | 2009-03-25 | 2015-04-28 | Tekelec, Inc. | Methods, systems, and computer readable media for providing home subscriber server (HSS) proxy |
WO2010132436A2 (en) | 2009-05-11 | 2010-11-18 | Tekelec | Methods, systems, and computer readable media for providing scalable number portability (np) home location register (hlr) |
US8238538B2 (en) | 2009-05-28 | 2012-08-07 | Comcast Cable Communications, Llc | Stateful home phone service |
US8224337B2 (en) * | 2009-09-16 | 2012-07-17 | Tekelec, Inc. | Methods, systems, and computer readable media for providing foreign routing address information to a telecommunications network gateway |
US8750126B2 (en) | 2009-10-16 | 2014-06-10 | Tekelec, Inc. | Methods, systems, and computer readable media for multi-interface monitoring and correlation of diameter signaling information |
US9313759B2 (en) | 2009-10-16 | 2016-04-12 | Tekelec, Inc. | Methods, systems, and computer readable media for providing triggerless equipment identity register (EIR) service in a diameter network |
US8958306B2 (en) * | 2009-10-16 | 2015-02-17 | Tekelec, Inc. | Methods, systems, and computer readable media for providing diameter signaling router with integrated monitoring functionality |
WO2011106690A2 (en) | 2010-02-25 | 2011-09-01 | Tekelelec | Systems, methods, and computer readable media for using a signaling message routing node to provide backup subscriber information management service |
US8375066B2 (en) | 2010-04-26 | 2013-02-12 | International Business Machines Corporation | Generating unique identifiers |
US8560698B2 (en) | 2010-06-27 | 2013-10-15 | International Business Machines Corporation | Allocating unique identifiers using metadata |
CN103385012B (en) | 2010-12-23 | 2016-08-10 | 泰克莱克股份有限公司 | For revising the method for Diameter signaling message, system and the equipment of billing function node to be mail to |
JP5885757B2 (en) | 2011-01-21 | 2016-03-15 | テケレック・インコーポレイテッドTekelec, Inc. | Method, system, and computer-readable medium for screening Diameter messages in a Diameter signaling router (DSR) having a distributed message processor architecture |
CN103493436B (en) | 2011-03-18 | 2016-10-05 | 泰科来股份有限公司 | Method, apparatus and system for configurable diameter address resolution |
US9100796B2 (en) | 2011-12-15 | 2015-08-04 | Tekelec, Inc. | Methods, systems, and computer readable media for seamless roaming between diameter and non-diameter networks |
US8855654B2 (en) | 2013-01-28 | 2014-10-07 | Tekelec Global, Inc. | Methods, systems, and computer readable media for tracking and communicating long term evolution (LTE) handset communication capability |
US9143942B2 (en) | 2013-03-14 | 2015-09-22 | Tekelec Global, Inc. | Methods, systems, and computer readable media for providing a multi-network equipment identity register |
US20140269440A1 (en) * | 2013-03-15 | 2014-09-18 | Vonage Network, Llc | Systems and methods for handling incoming communications directed to a telephony device |
US9635526B2 (en) | 2013-03-15 | 2017-04-25 | Tekelec, Inc. | Methods, systems, and computer readable media for utilizing a diameter proxy agent to communicate short message service (SMS) messages |
US10117127B2 (en) | 2015-07-08 | 2018-10-30 | Oracle International Corporation | Methods, systems, and computer readable media for communicating radio access network congestion status information for large numbers of users |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4577066A (en) * | 1983-08-03 | 1986-03-18 | At&T Bell Laboratories | Telephone interexchange call routing |
US5042064A (en) * | 1990-05-03 | 1991-08-20 | At&T Bell Laboratories | Call control strategy for high capacity telecommunication services |
EP0509705A2 (en) * | 1991-04-17 | 1992-10-21 | AT&T Corp. | Processing interactions among telecommunications call features |
EP0559979A2 (en) * | 1992-03-09 | 1993-09-15 | Advantis | Subscriber call routing process system |
WO1993018606A1 (en) * | 1992-03-05 | 1993-09-16 | Bell Atlantic Network Services, Inc. | Personal communications service using wireline/wireless integration |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4611094A (en) * | 1983-12-01 | 1986-09-09 | At&T Bell Laboratories | Method for customer definable telephone capability |
US4782519A (en) * | 1986-05-22 | 1988-11-01 | Network Access Corporation | Method and apparatus for enhancing the operating capabilities of a telephone switching system |
US4748658A (en) * | 1986-07-16 | 1988-05-31 | Bell Communications Research, Inc. | Architecture for allocating resources in a telecommunications network |
US4756019A (en) * | 1986-08-27 | 1988-07-05 | Edmund Szybicki | Traffic routing and automatic network management system for telecommunication networks |
US5027384A (en) * | 1986-09-22 | 1991-06-25 | Dytel Corporation | Personalized automatic call routing |
US4768221A (en) * | 1986-10-20 | 1988-08-30 | Planum Technology Corp. | Remote reprogramming system for telephone call forwarding service |
FR2616024B1 (en) * | 1987-05-26 | 1989-07-21 | Quinquis Jean Paul | SYSTEM AND METHOD FOR PACKET FLOW CONTROL |
US5109405A (en) * | 1988-07-11 | 1992-04-28 | Dytel Corporation | Automated call screening |
US4943996A (en) * | 1989-01-06 | 1990-07-24 | International Business Machines Corporation | Shared access to voice and information |
US4979118A (en) * | 1989-03-10 | 1990-12-18 | Gte Laboratories Incorporated | Predictive access-control and routing system for integrated services telecommunication networks |
US5231631A (en) * | 1989-08-15 | 1993-07-27 | At&T Bell Laboratories | Arrangement for regulating traffic in a high speed data network |
EP0419958B1 (en) * | 1989-09-29 | 1997-02-19 | Siemens Aktiengesellschaft | Circuit arrangement for detecting the data quantity transmitted in an ATM-switching system and for checking compliance with specified bit rates |
US5001710A (en) * | 1989-10-24 | 1991-03-19 | At&T Bell Laboratories | Customer programmable automated integrated voice/data technique for communication systems |
US5142570A (en) * | 1990-06-15 | 1992-08-25 | Bell Communications Research, Inc. | Routing of network traffic using discrete traffic measurement data |
JPH04100342A (en) * | 1990-08-20 | 1992-04-02 | Toshiba Corp | Traffic control system |
US5212727A (en) * | 1990-09-26 | 1993-05-18 | At&T Bell Laboratories | Queuing trigger in call processing |
US5282244A (en) * | 1991-06-24 | 1994-01-25 | At&T Bell Laboratories | Virtual signaling network method |
US5195090A (en) * | 1991-07-09 | 1993-03-16 | At&T Bell Laboratories | Wireless access telephone-to-telephone network interface architecture |
US5295183A (en) * | 1991-11-21 | 1994-03-15 | Northern Telecom Limited | Congestion control system for telecommunications |
-
1994
- 1994-05-20 US US08/246,876 patent/US5430719A/en not_active Expired - Lifetime
-
1995
- 1995-03-21 EP EP00102796A patent/EP1005236B1/en not_active Expired - Lifetime
- 1995-03-21 DE DE69528675T patent/DE69528675T2/en not_active Expired - Fee Related
- 1995-03-21 AT AT00102799T patent/ATE226779T1/en not_active IP Right Cessation
- 1995-03-21 DE DE69522805T patent/DE69522805T2/en not_active Expired - Fee Related
- 1995-03-21 EP EP95914793A patent/EP0765579B1/en not_active Expired - Lifetime
- 1995-03-21 NZ NZ283562A patent/NZ283562A/en unknown
- 1995-03-21 JP JP7530270A patent/JP3011461B2/en not_active Expired - Fee Related
- 1995-03-21 CA CA002189264A patent/CA2189264C/en not_active Expired - Fee Related
- 1995-03-21 DE DE69528673T patent/DE69528673T2/en not_active Expired - Fee Related
- 1995-03-21 DE DE69528718T patent/DE69528718T2/en not_active Expired - Fee Related
- 1995-03-21 AT AT95914793T patent/ATE205989T1/en not_active IP Right Cessation
- 1995-03-21 AT AT00102797T patent/ATE226780T1/en not_active IP Right Cessation
- 1995-03-21 EP EP00102798A patent/EP1003341B1/en not_active Expired - Lifetime
- 1995-03-21 DE DE69528674T patent/DE69528674T2/en not_active Expired - Fee Related
- 1995-03-21 AU AU21894/95A patent/AU699654B2/en not_active Ceased
- 1995-03-21 ES ES95914793T patent/ES2167426T3/en not_active Expired - Lifetime
- 1995-03-21 PT PT95914793T patent/PT765579E/en unknown
- 1995-03-21 EP EP00102797A patent/EP1005237B1/en not_active Expired - Lifetime
- 1995-03-21 EP EP00102799A patent/EP1003342B1/en not_active Expired - Lifetime
- 1995-03-21 AT AT00102796T patent/ATE227063T1/en not_active IP Right Cessation
- 1995-03-21 AT AT00102798T patent/ATE226778T1/en not_active IP Right Cessation
- 1995-03-21 WO PCT/US1995/003536 patent/WO1995032588A1/en active IP Right Grant
- 1995-03-21 DK DK95914793T patent/DK0765579T3/en active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4577066A (en) * | 1983-08-03 | 1986-03-18 | At&T Bell Laboratories | Telephone interexchange call routing |
US5042064A (en) * | 1990-05-03 | 1991-08-20 | At&T Bell Laboratories | Call control strategy for high capacity telecommunication services |
EP0509705A2 (en) * | 1991-04-17 | 1992-10-21 | AT&T Corp. | Processing interactions among telecommunications call features |
WO1993018606A1 (en) * | 1992-03-05 | 1993-09-16 | Bell Atlantic Network Services, Inc. | Personal communications service using wireline/wireless integration |
EP0559979A2 (en) * | 1992-03-09 | 1993-09-15 | Advantis | Subscriber call routing process system |
Non-Patent Citations (9)
Title |
---|
BAUGHAN ET AL.: "Transaction Capabilities - The new dimension", SECOND IEE NATIONAL CONFERENCE ON TELECOMMUNICATIONS, 2 April 1989 (1989-04-02), YORK GB, pages 411 - 417, XP000041220 * |
BENNETT ET AL.: "Intelligent Network OAM&P capabilities and evolutions for network elements", AT & T TECHNICAL JOURNAL, vol. 70, no. 3/4, SHORT HILLS US, pages 85 - 98, XP000271090 * |
BRAY: "Impact of new services on SCP performance", IEEE INTERNATIONAL CONFERENCE ON COMMUNICATIONS ICC '90, vol. 1, 15 April 1990 (1990-04-15), ATLANTA US, pages 241 - 247, XP000147409 * |
CHEN: "Open AIN operations strategies", IEEE NETWORK OPERATIONS AND MANAGEMENT SYMPOSIUM, vol. 1, 14 February 1994 (1994-02-14), KISSIMMEE US, pages 140 - 152, XP000452403 * |
JABBARI: "Common Channel Signalling System Number 7 for ISDN and Intelligent Networks", PROCEEDINGS OF THE IEEE, vol. 79, no. 2, NEW YORK US, pages 155 - 169, XP000226399 * |
KETTLER ET AL.: "Evolution of the Intelligent Network to support global services", INTERNATIONAL SWITCHING SYMPOSIUM, vol. 2, 25 October 1992 (1992-10-25), YOKOHAMA JP, pages 53 - 57, XP000429942 * |
RÉGNIER ET AL.: "Personal Communication Services - The new POTS", IEEE GLOBAL TELECOMMUNICATIONS CONFERENCE & EXHIBITION, vol. 1, 2 December 1990 (1990-12-02), SAN DIEGO US, pages 420 - 426, XP000218765 * |
THEUS ET AL.: "Open access to the Intelligent Network: The road to more flexible and responsive services", TELEPHONY, vol. 226, no. 18, 2 May 1994 (1994-05-02), US, pages 68 - 72 * |
YEGENOGLU ET AL.: "Transaction Capabilities Application Part and Intelligent Network services", SUPERCOMM / INTERNATIONAL CONFERENCE ON COMMUNICATIONS '92, vol. 2, 14 June 1992 (1992-06-14), CHICAGO US, pages 582 - 586, XP000326748 * |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6016307A (en) * | 1996-10-31 | 2000-01-18 | Connect One, Inc. | Multi-protocol telecommunications routing optimization |
US9036499B2 (en) | 1996-10-31 | 2015-05-19 | Patentmarks Communications, Llc | Multi-protocol telecommunications routing optimization |
US9806988B2 (en) | 1996-10-31 | 2017-10-31 | Patentmarks Communications, Llc | Multi-protocol telecommunications routing optimization |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
AU699654B2 (en) | Mediation of open advanced intelligent network interface by shared execution environment | |
US5701301A (en) | Mediation of open advanced intelligent network in SS7 protocol open access environment | |
EP0706743B1 (en) | Mediation of open advanced intelligent network interface for public switched telephone network | |
US6430276B1 (en) | Telecommunications system and method providing generic network access service | |
US5533106A (en) | Method and system for processing calls wherein the display of calling party ID information has been inhibited | |
US5600710A (en) | Method for providing a recorded message to a telephone caller when called number is busy | |
US7664244B2 (en) | Method and system for providing calling number restoral | |
US5263080A (en) | Telephone message storage system with out-of-band signalling | |
US7106846B2 (en) | System and method for caller control of a distinctive ring | |
US5519768A (en) | Facsimile detection system and method | |
US5812640A (en) | System and method for using alternative switch announcements in advanced intelligent network services | |
US6944276B1 (en) | System and method to detect privacy screening | |
AU718459B2 (en) | Mediation of open advanced intelligent network interface by shared execution environment | |
US7099446B1 (en) | Method for providing telephone services for commercial classes of service | |
US20030215082A1 (en) | Triggerless call treatment service implementation in a telecommunications network | |
MXPA96005634A (en) | Advanced intelligent network interface mediation through compart execution environment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AM AT AU BB BG BR BY CA CH CN CZ DE DK EE ES FI GB GE HU JP KE KG KP KR KZ LK LR LT LU LV MD MG MN MW MX NL NO NZ PL PT RO RU SD SE SI SK TJ TT UA UZ VN |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): KE MW SD SZ UG AT BE CH DE DK ES FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN ML MR NE SN TD TG |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WR | Later publication of a revised version of an international search report | ||
WWE | Wipo information: entry into national phase |
Ref document number: 283562 Country of ref document: NZ |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2189264 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: PA/a/1996/005634 Country of ref document: MX |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1995914793 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWP | Wipo information: published in national office |
Ref document number: 1995914793 Country of ref document: EP |
|
WWG | Wipo information: grant in national office |
Ref document number: 1995914793 Country of ref document: EP |