WO1998044707A1 - System and method for managing feature interaction of telephone services - Google Patents

System and method for managing feature interaction of telephone services Download PDF

Info

Publication number
WO1998044707A1
WO1998044707A1 PCT/US1998/006068 US9806068W WO9844707A1 WO 1998044707 A1 WO1998044707 A1 WO 1998044707A1 US 9806068 W US9806068 W US 9806068W WO 9844707 A1 WO9844707 A1 WO 9844707A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
feature
processors
customer
call processing
Prior art date
Application number
PCT/US1998/006068
Other languages
French (fr)
Inventor
Craig L. Schafer
Steven E. Valin
Timothy M. Weinrich
Gregory M. Fisher
Douglas Beck
Original Assignee
Bell Communications Research, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bell Communications Research, Inc. filed Critical Bell Communications Research, Inc.
Priority to JP54183698A priority Critical patent/JP3507510B2/en
Priority to CA002283861A priority patent/CA2283861C/en
Priority to EP98913200A priority patent/EP1013060A1/en
Publication of WO1998044707A1 publication Critical patent/WO1998044707A1/en

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/42136—Administration or customisation of services
    • H04M3/4217—Managing service interactions
    • 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/0041—Provisions for intelligent networking involving techniques for avoiding interaction of call service features

Definitions

  • the present invention relates to the field of service management in a telephone network, and in particular to managing service features in a service control point.
  • Bellcore has developed the SPACE® and MSAP® applications to permit the development and instantiation of telephone services in the advanced intelligent network (“AIN").
  • Multiple service providers utilize the SPACE and MSAP languages.
  • call processing records corresponding to each customer are generated by a service provider and stored in a database associated with a service control point ("SCP") in a telephone network. Calls to or from a customer trigger execution of the call processing records to provide the subscribed-to services for each customer.
  • SCP service control point
  • the system was oriented toward a single service per trigger execution, using predetermined service components . Adding a new feature to an existing service involved changing the service itself.
  • the invention includes a service control point for a telephone network, including one or more service feature processors, each service feature processor including means for executing a predetermined set of instructions to implement a predetermined telephone service, and one or more customer call processing records, each call processing record including data corresponding to one or more service features in each customer's service portfolio, a feature manager processor including means responsive to one or more trigger messages for selecting one or more service feature processors dynamically to implement each customer's service portfolio .
  • the invention further includes a SCP including one or more customer call processing records and one or more service feature processors, a method of implementing one or more of a plurality of service features, including the steps of identifying which service features a particular customer subscribes to, and dynamically executing each of the identified service features.
  • FIG. 1 illustrates a block diagram of an ISCP with a feature manager processor in accordance with one; embodiment of the present invention
  • Fig. 2 includes flow processing of a feature manager processor that manages seven service features: "do not disturb,” “selective call filtering,” “call forwarding,” selective call forwarding,” “free phone,” “distinctive ringing,” and “premium rate” services, in accordance with one embodiment of the invention; and
  • Fig. 3 illustrates a block diagram of an ISCP in accordance with an alternative embodiment of the present invention. Best Mode for Carrying Out the Invention
  • Fig. 1 illustrates a block diagram of an ISCP with a feature manager processor in accordance with one embodiment of the present invention.
  • ISCP 100 includes feature manager processor 102, a plurality of call processing records 104a-104n, and a plurality of service features processors 106a-106n.
  • service feature processors 106 provide specific call processing for predetermined telephone services.
  • service feature processor A 106a may correspond to a call forward feature
  • service feature processor B 106b may correspond to a call blocking feature
  • service feature processor C 106n may correspond to a distinctive ring feature.
  • Service feature processors 106 preferably comprise software applications developed using the Bellcore SPACE® language as described, for example, in Bellcore Document No. BR 780-003- 186
  • Call processing records (“CPRs") 104 correspond to each individual service customer.
  • the CPRs 104 preferably identify the services each customer subscribes to and includes the data necessary to execute each service.
  • CPR 1 corresponds to a first customer who subscribers to service A. Accordingly, CPR 1 includes data A that is used by the service feature processor A 106a to execute that service for the customer.
  • a customer who subscribes to services B and C would have a CPR such as CPR 2 104b which includes data B and C used by service feature processor B 106b and service feature processor C 106n to execute those services.
  • the configuration of such call processing records is described, for example, in Bellcore Document No. BR 780-003-186.
  • feature manager processor 102 communicates with each CPR 104 and each service feature processor 106 to manage the processes provided by a service provider.
  • Feature manager processor 102 controls the manner in which services are executed (if at all) for each customer.
  • Feature manager processor 102 manages multiple features on a single line and manages the interaction of these features.
  • a service provider can program a feature manager processor 102 to manage a portfolio of services provided by that service provider.
  • call processing is provided by the service feature processors 106 using data from the customer's CPRs under the control of a feature manager processor 102.
  • feature manager processor 102 makes decisions about whether a customer subscribes to certain features and requests execution of those service features by the corresponding service feature processors 106 depending on whether the customer subscribes to the service. Feature manager processor 102 also makes decisions based on the results provided by service feature processors 106. This configuration allows service creators the flexibility to modulize features and functions.
  • feature manager processor 102 may comprise any hardware processor and corresponding application necessary to implement the functionality described herein.
  • feature manager processor 102 includes the Bellcore application implemented using the Bellcore SPACE software, as described in Bellcore Document No. BR 780-003-186.
  • Fig. 2 includes flow processing of a feature manager processor that manages seven service features: "do not disturb,” “selective call filtering,” “call forwarding,” selective call forwarding,” “free phone,” “distinctive ringing,” and “premium rate” services.
  • a service provider programs the feature manager processor to execute these services as provided, for example, in Fig. 2.
  • each call directed to any of the customers corresponding to CPRs 104 would be processed according to the processing flow of Fig. 2.
  • feature manager processor 102 responds to a termination attempt (step 200).
  • the termination attempt is a trigger corresponding to a called telephone number of a customer.
  • feature manager processor 102 initially performs a "feature invoke” operation for the "do not disturb” feature (step 202).
  • the "feature invoke” operation initially determines whether the customer subscribes to that service. Feature manager processor 102 preferably does so by reviewing the data in the CPR corresponding to the dialed telephone number. If the customer subscribes to the "do not disturb” feature, feature manager processor 102 hands over the processing to the service feature processor 106 corresponding to the "do not disturb" feature.
  • the corresponding service feature processor 106 performs the corresponding call processing and returns an instruction to the feature manager processor 102, which uses the information from the service feature processor 106 to further control processing (step 204) .
  • the service feature processor 106 may have determined that the customer being called does not wish to receive calls after 9:00 p.m. If the phone call is being made at 10:00 p.m., the service feature processor 106 will return a "terminate call" message to the feature manager processor 102 (step 206) .
  • the processing then preferably jumps to the corresponding call processing to terminate the call (steps 208-212).
  • the feature manager process 102 simply continues processing to step 204.
  • the feature manager processor 104 invokes the next feature, "selective call filtering" (step 216) .
  • the "selective call filtering" feature may be used to block a call from a particular party.
  • feature manager processor 102 initially determines whether the customer subscribes to a "selective call filtering" feature 106. If so, feature manager processor 102 hands over processing to the corresponding service feature processor. If not, feature manager processor 102 continues.
  • Feature manager processor 102 then awaits the results of the processing by the service feature processor 106 and uses the information returned by that service feature processor 106 to determine further processing (step 218). For example, if the service feature processor 106 returns the instruction to terminate the call (step 220) , feature manager processor 102 jumps to the processing necessary to terminate the call (steps 208-212) . For any other instruction (step 222), feature manager processor 102 continues. In this example, feature manager processor 102 next determines whether the customer subscribes to a "call forwarding" service and hands over processing to the corresponding service feature processor 106 if the customer does so subscribe (step 224) . If the customer does not subscribe to a "call forwarding" feature, feature manager processor 102 continues to step 226.
  • the feature invoke 224 and the subsequent feature invoke "selective call forwarding" service (step 226) provides for overriding feature invocation.
  • the "call forwarding" service may route calls to the customer's home phone during certain times of day and to a business phone during other times of the day.
  • the "selective call forwarding" feature may provide a specific list of parties that will be forwarded to the customer's cellular phone.
  • Feature manager processor 102 invokes both of these features before deciding on further call processing (step 228).
  • any call state changes affected by the "selective call forwarding" feature override those of the "call forward” feature.
  • This overriding mechanism is used in this example to "specialize” the behavior of one feature with another. For example, if a customer has requested that phone calls be routed to the home phone during certain times of day, the call state will be set to "forward call” and the called party will be routed to the customer's home phone.
  • Feature manager processor 102 makes a decision to continue processing based on the information returned from the two service feature processors 106 corresponding to the "call forwarding" and "selective call forwarding" features.
  • step 230 the instruction "forward call” (step 230) or any other message other than "auth-termination” (step 236) , the feature manager processor jumps to the steps necessary to complete to the call (steps 208, 232, and 234).
  • the authorized termination state corresponds to a caller who has made it through the "do not disturb" and “selective call” filtering features without being blocked and has proceeded through the "call forwarding" and “selective call forwarding” features without being forwarded.
  • feature manager processor 102 decides whether the customer subscribes to a "free phone" service (step 240) .
  • Feature invoke decide node allows the premium rate feature to be invoked if the free phone feature was not executed. This differs from the feature invoke node for which execution proceeds indiscriminately to the following node.
  • step 240 feature manager processor 102 determines that the customer does not subscribe to a "free phone” service, feature manager processor 102 then determines whether the customer subscribes for a "premium rate” service. In this manner only one of these two features may be executed.
  • the premium rate service charges a premium to any caller calling the customer, similarly to a 900 telephone number (step 244) .
  • Fig. 3 illustrates an ISCP configuration in accordance with an alternative embodiment of the present invention.
  • an ISCP includes multiple feature manager processors 302 and 304 and a trigger manager 306, as well as call processing records 104a-104n and service feature processors 106a-106n.
  • each feature manager processor 302 and 304 manages a selected number of service feature processors 106. For example, feature manager processor 1 302 manages service feature processors A 106a, B 106b, and C 106c, while feature manager processor 2 304 manages service feature processors C 106c and D 106n.
  • Trigger manager 306 is included to determine which feature manager processor to invoke to control the call processing. For example, feature manager processor 1 302 may be dedicated to all services that trigger on a dialed telephone number, while feature manager processor 2 304 may be dedicated to manager all features corresponding to a calling number. In response to a called telephone number, trigger manager 306 would select feature manager processor 1 302 to perform call processing. In response to a call from a customer, trigger manager 306 would select feature manager processor 2 304 to continue call processing.

Abstract

A service control processor (100) includes a plurality of service feature processors (106a-106n), each corresponding to a selected telephone service, and a plurality of call processing records (104a, 104n), each corresponding to a customer of a service provider. The customer call processing records specify services subscribed to by the caller. A feature manager processor (102) manages call processing and the implementation and execution of services by managing the individual service feature processors. In an alternative embodiment, multiple feature manager processors are included, and a trigger manager selects between them in response to call processing triggers.

Description

SYSTEM AND METHOD FOR MANAGING FEATURE INTERACTION OF
TELEPHONE SERVICES
Field of the Invention The present invention relates to the field of service management in a telephone network, and in particular to managing service features in a service control point.
Background of the Invention Bellcore has developed the SPACE® and MSAP® applications to permit the development and instantiation of telephone services in the advanced intelligent network ("AIN"). Multiple service providers utilize the SPACE and MSAP languages. In general, call processing records corresponding to each customer are generated by a service provider and stored in a database associated with a service control point ("SCP") in a telephone network. Calls to or from a customer trigger execution of the call processing records to provide the subscribed-to services for each customer. Prior to this invention, the system was oriented toward a single service per trigger execution, using predetermined service components . Adding a new feature to an existing service involved changing the service itself.
Accordingly, it is an object of the invention to improve call processing applications and to improve the efficiency and effectiveness of call processing procedures.
Description of the Invention To achieve these and other advantages and in accordance with the purposes of the invention, as embodied and broadly described, the invention includes a service control point for a telephone network, including one or more service feature processors, each service feature processor including means for executing a predetermined set of instructions to implement a predetermined telephone service, and one or more customer call processing records, each call processing record including data corresponding to one or more service features in each customer's service portfolio, a feature manager processor including means responsive to one or more trigger messages for selecting one or more service feature processors dynamically to implement each customer's service portfolio .
The invention further includes a SCP including one or more customer call processing records and one or more service feature processors, a method of implementing one or more of a plurality of service features, including the steps of identifying which service features a particular customer subscribes to, and dynamically executing each of the identified service features.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.
Brief Description of the Drawings Fig. 1 illustrates a block diagram of an ISCP with a feature manager processor in accordance with one; embodiment of the present invention;
Fig. 2 includes flow processing of a feature manager processor that manages seven service features: "do not disturb," "selective call filtering," "call forwarding," selective call forwarding," "free phone," "distinctive ringing," and "premium rate" services, in accordance with one embodiment of the invention; and
Fig. 3 illustrates a block diagram of an ISCP in accordance with an alternative embodiment of the present invention. Best Mode for Carrying Out the Invention
Reference will now be made in detail to the construction and operation of preferred implementations of the present invention which are illustrated in the accompanying drawings .
The following description of the preferred implementations of the present invention is only exemplary of the invention. The present invention is not limited to these implementations, but may be realized by other implementations .
Fig. 1 illustrates a block diagram of an ISCP with a feature manager processor in accordance with one embodiment of the present invention.
ISCP 100 includes feature manager processor 102, a plurality of call processing records 104a-104n, and a plurality of service features processors 106a-106n. In accordance with the present invention, service feature processors 106 provide specific call processing for predetermined telephone services. For example, service feature processor A 106a may correspond to a call forward feature, service feature processor B 106b may correspond to a call blocking feature, and service feature processor C 106n may correspond to a distinctive ring feature. Service feature processors 106 preferably comprise software applications developed using the Bellcore SPACE® language as described, for example, in Bellcore Document No. BR 780-003- 186
Call processing records ("CPRs") 104 correspond to each individual service customer. The CPRs 104 preferably identify the services each customer subscribes to and includes the data necessary to execute each service. For example, CPR 1 corresponds to a first customer who subscribers to service A. Accordingly, CPR 1 includes data A that is used by the service feature processor A 106a to execute that service for the customer. A customer who subscribes to services B and C would have a CPR such as CPR 2 104b which includes data B and C used by service feature processor B 106b and service feature processor C 106n to execute those services. The configuration of such call processing records is described, for example, in Bellcore Document No. BR 780-003-186.
In accordance with the present invention, feature manager processor 102 communicates with each CPR 104 and each service feature processor 106 to manage the processes provided by a service provider. Feature manager processor 102 controls the manner in which services are executed (if at all) for each customer. Feature manager processor 102 manages multiple features on a single line and manages the interaction of these features. A service provider can program a feature manager processor 102 to manage a portfolio of services provided by that service provider. Thus, call processing is provided by the service feature processors 106 using data from the customer's CPRs under the control of a feature manager processor 102.
Generally, to process a call to or from a subscriber, feature manager processor 102 makes decisions about whether a customer subscribes to certain features and requests execution of those service features by the corresponding service feature processors 106 depending on whether the customer subscribes to the service. Feature manager processor 102 also makes decisions based on the results provided by service feature processors 106. This configuration allows service creators the flexibility to modulize features and functions. In accordance with the present invention, feature manager processor 102 may comprise any hardware processor and corresponding application necessary to implement the functionality described herein. Preferably, feature manager processor 102 includes the Bellcore application implemented using the Bellcore SPACE software, as described in Bellcore Document No. BR 780-003-186.
To help illustrate the functionality of a feature manager processor 102, Fig. 2 includes flow processing of a feature manager processor that manages seven service features: "do not disturb," "selective call filtering," "call forwarding," selective call forwarding," "free phone," "distinctive ringing," and "premium rate" services. To manage these services, a service provider programs the feature manager processor to execute these services as provided, for example, in Fig. 2. Thus, each call directed to any of the customers corresponding to CPRs 104 would be processed according to the processing flow of Fig. 2.
Initially, feature manager processor 102 responds to a termination attempt (step 200). The termination attempt is a trigger corresponding to a called telephone number of a customer. In response, feature manager processor 102 initially performs a "feature invoke" operation for the "do not disturb" feature (step 202). The "feature invoke" operation initially determines whether the customer subscribes to that service. Feature manager processor 102 preferably does so by reviewing the data in the CPR corresponding to the dialed telephone number. If the customer subscribes to the "do not disturb" feature, feature manager processor 102 hands over the processing to the service feature processor 106 corresponding to the "do not disturb" feature. The corresponding service feature processor 106 performs the corresponding call processing and returns an instruction to the feature manager processor 102, which uses the information from the service feature processor 106 to further control processing (step 204) . For example, for the "do not disturb" feature, the service feature processor 106 may have determined that the customer being called does not wish to receive calls after 9:00 p.m. If the phone call is being made at 10:00 p.m., the service feature processor 106 will return a "terminate call" message to the feature manager processor 102 (step 206) . The processing then preferably jumps to the corresponding call processing to terminate the call (steps 208-212).
If the customer does not subscribe to the "do not disturb" feature, the feature manager process 102 simply continues processing to step 204.
If the "do not disturb" service feature processor returns any message other than terminate call (step 214) or the feature did not execute, then the feature manager processor 104 invokes the next feature, "selective call filtering" (step 216) . The "selective call filtering" feature may be used to block a call from a particular party.
Here again, feature manager processor 102 initially determines whether the customer subscribes to a "selective call filtering" feature 106. If so, feature manager processor 102 hands over processing to the corresponding service feature processor. If not, feature manager processor 102 continues.
Feature manager processor 102 then awaits the results of the processing by the service feature processor 106 and uses the information returned by that service feature processor 106 to determine further processing (step 218). For example, if the service feature processor 106 returns the instruction to terminate the call (step 220) , feature manager processor 102 jumps to the processing necessary to terminate the call (steps 208-212) . For any other instruction (step 222), feature manager processor 102 continues. In this example, feature manager processor 102 next determines whether the customer subscribes to a "call forwarding" service and hands over processing to the corresponding service feature processor 106 if the customer does so subscribe (step 224) . If the customer does not subscribe to a "call forwarding" feature, feature manager processor 102 continues to step 226.
In the example shown in Fig. 2, the feature invoke 224 and the subsequent feature invoke "selective call forwarding" service (step 226) provides for overriding feature invocation. For example, the "call forwarding" service may route calls to the customer's home phone during certain times of day and to a business phone during other times of the day. The "selective call forwarding" feature may provide a specific list of parties that will be forwarded to the customer's cellular phone. Feature manager processor 102 invokes both of these features before deciding on further call processing (step 228). Since "selective call forwarding" (step 226) may execute immediately following the "call forwarding" feature without confirming the results of the "call forward" feature, any call state changes affected by the "selective call forwarding" feature override those of the "call forward" feature. This overriding mechanism is used in this example to "specialize" the behavior of one feature with another. For example, if a customer has requested that phone calls be routed to the home phone during certain times of day, the call state will be set to "forward call" and the called party will be routed to the customer's home phone. However, if the subsequent "selective call forward" feature determines that the particular caller should be routed to the customer's cellular phone, the call state will be changed appropriately thus overriding the action requested by the prior feature. Feature manager processor 102 then makes a decision to continue processing based on the information returned from the two service feature processors 106 corresponding to the "call forwarding" and "selective call forwarding" features.
For example, if the instruction "forward call" (step 230) or any other message other than "auth-termination" (step 236) , the feature manager processor jumps to the steps necessary to complete to the call (steps 208, 232, and 234).
The authorized termination state (step 238) corresponds to a caller who has made it through the "do not disturb" and "selective call" filtering features without being blocked and has proceeded through the "call forwarding" and "selective call forwarding" features without being forwarded. For these callers, feature manager processor 102 then decides whether the customer subscribes to a "free phone" service (step 240) . Feature invoke decide node allows the premium rate feature to be invoked if the free phone feature was not executed. This differs from the feature invoke node for which execution proceeds indiscriminately to the following node.
If in step 240, feature manager processor 102 determines that the customer does not subscribe to a "free phone" service, feature manager processor 102 then determines whether the customer subscribes for a "premium rate" service. In this manner only one of these two features may be executed. The premium rate service charges a premium to any caller calling the customer, similarly to a 900 telephone number (step 244) .
Lastly, the feature manager processor 102 uses a feature invoke "distinctive ringing" step (step 242) to determine whether the customer desires distinctive ringing for incoming calls. At step 208, the feature manager processor examines the final state of the call and routes or terminates the current call as needed. Fig. 3 illustrates an ISCP configuration in accordance with an alternative embodiment of the present invention. In this embodiment, an ISCP includes multiple feature manager processors 302 and 304 and a trigger manager 306, as well as call processing records 104a-104n and service feature processors 106a-106n. In this embodiment, each feature manager processor 302 and 304 manages a selected number of service feature processors 106. For example, feature manager processor 1 302 manages service feature processors A 106a, B 106b, and C 106c, while feature manager processor 2 304 manages service feature processors C 106c and D 106n.
Trigger manager 306 is included to determine which feature manager processor to invoke to control the call processing. For example, feature manager processor 1 302 may be dedicated to all services that trigger on a dialed telephone number, while feature manager processor 2 304 may be dedicated to manager all features corresponding to a calling number. In response to a called telephone number, trigger manager 306 would select feature manager processor 1 302 to perform call processing. In response to a call from a customer, trigger manager 306 would select feature manager processor 2 304 to continue call processing.
While there has been illustrated and described what are at present considered to be preferred embodiments and methods of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made, and equivalents may be substituted for elements thereof without departing from the true scope of the invention.
In addition, many modifications may be made to adapt a particular element, technique or implementation to the teachings of the present invention without departing from the central scope of the invention. Therefore, it is intended that this invention not be limited to the particular embodiments and methods disclosed herein, but that the invention include all embodiments falling within the scope of the appended claims.

Claims

Claims
1. A service control point for a telephone network, comprising: one or more service feature processors, each service feature processor including means for executing a predetermined set of instructions to implement a predetermined telephone service; and one or more customer call processing records, each call processing record including data corresponding to one or more service features in each customer's service portfolio; and a feature manager processor including means responsive to one or more trigger messages for selecting said one or more service feature processors dynamically to implement each customer's service portfolio.
2. A SCP according to claim 1, wherein said data is used by a corresponding one of said one or more service processors when executing said predetermined set of instructions .
3. A service control point for a telephone network, comprising: one or more service feature processors, each service feature processor including means for executing a predetermined set of instructions to implement a predetermined telephone feature; one or more customer call processing records, each call processing record including data corresponding to one or more service features in each customer's service portfolio; and a feature manager processor including: means for identifying which service features a particular customer subscribes to; and means for dynamically executing said service feature processors corresponding to said identified service features .
4. A SCP according to claim 3, wherein said data is used by a corresponding one of said one or more service processors when executing said predetermined set of instructions .
5. A SCP according to claim 1, wherein said feature manager processor further includes means for communicating with each of said service feature processors.
6. A SCP according to claim 3, wherein said feature manager processor further includes means for communicating with each of said service feature processors.
7. In a SCP including one or more customer call processing records and one or more service feature processors, a method of implementing one or more of a plurality of service features, comprising the steps of: identifying which service features a particular customer subscribes to; and executing each of said identified service features.
8. The method according to claim 7, wherein said executing step includes the step of arranging more than one feature invoke nodes in a predetermined order.
9. The method according to claim 7, wherein said executing step includes the step of executing based on data from a call processing record.
10. The method according to claim 7, wherein said executing step includes the step of executing based on data from a current call state.
11. A service control point ("SCP"), comprising: one or more service feature processors, each service feature processor including means for executing a predetermined set of instructions to implement a predetermined telephone service; one or more customer call processing records, each call processing record including data corresponding to one or more service features in each customer's service portfolio; a plurality of feature manager processors, each feature manager processor corresponding to a predetermined set of said service feature processors; and a trigger manager for selecting one of said plurality of feature manager processors depending on a trigger.
12. A SCP according to claim 11, wherein each of said feature manager processors includes: means for identifying which service features a particular customer subscribes to; and means for selecting said service feature processors corresponding to said identified service features; and means for determining an order of execution of said service feature processors.
13. An SCP according to claim 12, wherein said determining means includes more than one feature invoke nodes in a predetermined order.
14. An SCP according to claim 13, wherein said determining means includes data from a call processing record.
15. An SCP according to claim 13, wherein said determining means includes data from a current call state.
PCT/US1998/006068 1997-03-31 1998-03-27 System and method for managing feature interaction of telephone services WO1998044707A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP54183698A JP3507510B2 (en) 1997-03-31 1998-03-27 System and method for managing the exchange of telephone service features
CA002283861A CA2283861C (en) 1997-03-31 1998-03-27 System and method for managing feature interaction of telephone services
EP98913200A EP1013060A1 (en) 1997-03-31 1998-03-27 System and method for managing feature interaction of telephone services

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US08/829,595 US5966434A (en) 1997-03-31 1997-03-31 System and method for managing feature interaction of telephone services
US08/829,595 1997-03-31

Publications (1)

Publication Number Publication Date
WO1998044707A1 true WO1998044707A1 (en) 1998-10-08

Family

ID=25254958

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1998/006068 WO1998044707A1 (en) 1997-03-31 1998-03-27 System and method for managing feature interaction of telephone services

Country Status (5)

Country Link
US (1) US5966434A (en)
EP (1) EP1013060A1 (en)
JP (1) JP3507510B2 (en)
CA (1) CA2283861C (en)
WO (1) WO1998044707A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999018706A2 (en) * 1997-09-25 1999-04-15 Nokia Networks Oy Service interaction in an intelligent network
WO2000062559A1 (en) * 1999-04-14 2000-10-19 Bellsouth Intellectual Property Corporation Multiple services per trigger
EP2375715A3 (en) * 2004-04-07 2011-11-02 France Telecom Event processing system in a communication network

Families Citing this family (52)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
US6041109A (en) 1995-12-29 2000-03-21 Mci Communications Corporation Telecommunications system having separate switch intelligence and switch fabric
US6069890A (en) * 1996-06-26 2000-05-30 Bell Atlantic Network Services, Inc. Internet telephone service
US6154445A (en) 1996-04-18 2000-11-28 Bell Atlantic Network Services, Inc. Telephony communication via varied redundant networks
US6445782B1 (en) * 1996-11-19 2002-09-03 British Telecommunications Public Limited Company Service management system for use in communications
US6078582A (en) 1996-12-18 2000-06-20 Bell Atlantic Network Services, Inc. Internet long distance telephone service
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
US6292479B1 (en) 1997-03-19 2001-09-18 Bell Atlantic Network Services, Inc. Transport of caller identification information through diverse communication networks
US6870827B1 (en) 1997-03-19 2005-03-22 Verizon Services Corp. Voice call alternative routing through PSTN and internet networks
US7024450B1 (en) * 1997-10-06 2006-04-04 Mci, Inc. Method and apparatus for deploying service modules among service nodes distributed in an intelligent network
US6363411B1 (en) 1998-08-05 2002-03-26 Mci Worldcom, Inc. Intelligent network
US6418461B1 (en) 1997-10-06 2002-07-09 Mci Communications Corporation Intelligent call switching node in an intelligent distributed network architecture
US6779030B1 (en) * 1997-10-06 2004-08-17 Worldcom, Inc. Intelligent network
US6393481B1 (en) 1997-10-06 2002-05-21 Worldcom, Inc. Method and apparatus for providing real-time call processing services in an intelligent network
US6594355B1 (en) 1997-10-06 2003-07-15 Worldcom, Inc. Method and apparatus for providing real time execution of specific communications services in an intelligent network
US6804711B1 (en) 1997-10-06 2004-10-12 Mci, Inc. Method and apparatus for managing call processing services in an intelligent telecommunication network
US6425005B1 (en) 1997-10-06 2002-07-23 Mci Worldcom, Inc. Method and apparatus for managing local resources at service nodes in an intelligent network
US6332023B1 (en) * 1998-06-04 2001-12-18 Mci Communications Corporation Method of and system for providing services in a communications network
US6788649B1 (en) 1998-08-03 2004-09-07 Mci, Inc. Method and apparatus for supporting ATM services in an intelligent network
US6256409B1 (en) 1998-10-19 2001-07-03 Sony Corporation Method for determining a correlation between images using multi-element image descriptors
US6445834B1 (en) * 1998-10-19 2002-09-03 Sony Corporation Modular image query system
US6560326B1 (en) * 1999-04-21 2003-05-06 Lucent Technologies Inc. Service brokering system for intelligent telecommunications network
GB9925070D0 (en) * 1999-10-22 1999-12-22 Nokia Networks Oy Communication control in a telecommunications system
US6714978B1 (en) 1999-12-04 2004-03-30 Worldcom, Inc. Method and system for processing records in a communications network
US6697814B1 (en) 1999-12-04 2004-02-24 Worldcom, Inc. System for processing records in a communications network
US6687355B1 (en) * 1999-12-04 2004-02-03 Worldcom, Inc. Method and system for processing records in a communications network
US6823056B1 (en) * 2000-09-01 2004-11-23 Bellsouth Intellectual Property Corporation Multiple services per trigger within a telecommunications network
KR20070114325A (en) * 2000-10-11 2007-11-30 유나이티드 비디오 프로퍼티즈, 인크. Systems and methods for caching data in media-on-demand systems
US20030059017A1 (en) * 2001-09-21 2003-03-27 Dusica Cugalj Method and system for controlling services during call establishment
US20030123638A1 (en) * 2001-12-28 2003-07-03 Hines Warner Lee Multi-application operations management for single system environments
US20040039772A1 (en) * 2002-04-25 2004-02-26 De Miguel Angel Boveda Methods and arrangements in a telecommunication network
US20070011334A1 (en) * 2003-11-03 2007-01-11 Steven Higgins Methods and apparatuses to provide composite applications
DE602004029101D1 (en) * 2004-10-05 2010-10-21 Mentor Graphics Corp ACCELERATED HARDWARE EMULSION ENVIRONMENT FOR PROCESS-BASED SYSTEMS
US7207112B2 (en) * 2005-01-12 2007-04-24 Wen-Ya Yeh Combination hairdressing scissor assembly
TWI272800B (en) * 2005-06-22 2007-02-01 Inventec Multimedia & Telecom Network phone apparatus
US8782201B2 (en) * 2005-10-28 2014-07-15 Bank Of America Corporation System and method for managing the configuration of resources in an enterprise
US8239498B2 (en) * 2005-10-28 2012-08-07 Bank Of America Corporation System and method for facilitating the implementation of changes to the configuration of resources in an enterprise
US8868660B2 (en) * 2006-03-22 2014-10-21 Cellco Partnership Electronic communication work flow manager system, method and computer program product
US7912195B2 (en) 2006-06-07 2011-03-22 Comcast Cable Holdings, Llc Method for provisioning subscribers, products, and services in a broadband network
US8238538B2 (en) 2009-05-28 2012-08-07 Comcast Cable Communications, Llc Stateful home phone service
US10019486B2 (en) 2016-02-24 2018-07-10 Bank Of America Corporation Computerized system for analyzing operational event data
US10366337B2 (en) 2016-02-24 2019-07-30 Bank Of America Corporation Computerized system for evaluating the likelihood of technology change incidents
US10387230B2 (en) 2016-02-24 2019-08-20 Bank Of America Corporation Technical language processor administration
US10430743B2 (en) 2016-02-24 2019-10-01 Bank Of America Corporation Computerized system for simulating the likelihood of technology change incidents
US10216798B2 (en) 2016-02-24 2019-02-26 Bank Of America Corporation Technical language processor
US10275182B2 (en) 2016-02-24 2019-04-30 Bank Of America Corporation System for categorical data encoding
US10366338B2 (en) 2016-02-24 2019-07-30 Bank Of America Corporation Computerized system for evaluating the impact of technology change incidents
US10067984B2 (en) 2016-02-24 2018-09-04 Bank Of America Corporation Computerized system for evaluating technology stability
US10366367B2 (en) 2016-02-24 2019-07-30 Bank Of America Corporation Computerized system for evaluating and modifying technology change events
US10275183B2 (en) 2016-02-24 2019-04-30 Bank Of America Corporation System for categorical data dynamic decoding
US10223425B2 (en) 2016-02-24 2019-03-05 Bank Of America Corporation Operational data processor

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5404396A (en) * 1993-08-27 1995-04-04 Telefonaktiebolaget Lm Ericsson Feature interaction manager
US5455853A (en) * 1992-08-25 1995-10-03 Bell Communications Research, Inc. Method of creating a telecommunication service template
US5586177A (en) * 1995-09-06 1996-12-17 Bell Atlantic Network Services, Inc. Intelligent signal transfer point (ISTP)

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH03150660A (en) * 1989-11-08 1991-06-27 Fujitsu Ltd Additional processor control system
EP0576864B1 (en) * 1992-06-30 2002-12-18 Siemens Information and Communication Networks, Inc. A call processing system
US5448631A (en) * 1992-10-13 1995-09-05 U S West Advanced Technologies, Inc. Apparatus for handling features in a telephone network
CA2124379C (en) * 1993-06-25 1998-10-27 Thomas F. La Porta Distributed processing architecture for control of broadband and narrowband communications networks
JPH07160617A (en) * 1993-12-09 1995-06-23 Canon Inc Multimedia server
JPH07226797A (en) * 1993-12-17 1995-08-22 Hitachi Ltd Communication system and communication service control method

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5455853A (en) * 1992-08-25 1995-10-03 Bell Communications Research, Inc. Method of creating a telecommunication service template
US5404396A (en) * 1993-08-27 1995-04-04 Telefonaktiebolaget Lm Ericsson Feature interaction manager
US5586177A (en) * 1995-09-06 1996-12-17 Bell Atlantic Network Services, Inc. Intelligent signal transfer point (ISTP)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999018706A2 (en) * 1997-09-25 1999-04-15 Nokia Networks Oy Service interaction in an intelligent network
WO1999018706A3 (en) * 1997-09-25 1999-06-17 Nokia Telecommunications Oy Service interaction in an intelligent network
US6661887B1 (en) 1997-09-25 2003-12-09 Nokia Networks Oy Service interaction in an intelligent network
WO2000062559A1 (en) * 1999-04-14 2000-10-19 Bellsouth Intellectual Property Corporation Multiple services per trigger
US6532285B1 (en) 1999-04-14 2003-03-11 Bellsouth Intellectual Property Corporation Method and system for providing multiple services per trigger
US6700968B2 (en) 1999-04-14 2004-03-02 Bellsouth Intellectual Property Corporation Method and system for providing multiple services per trigger
EP2375715A3 (en) * 2004-04-07 2011-11-02 France Telecom Event processing system in a communication network

Also Published As

Publication number Publication date
US5966434A (en) 1999-10-12
CA2283861A1 (en) 1998-10-08
JP2000510315A (en) 2000-08-08
JP3507510B2 (en) 2004-03-15
CA2283861C (en) 2002-08-13
EP1013060A1 (en) 2000-06-28

Similar Documents

Publication Publication Date Title
US5966434A (en) System and method for managing feature interaction of telephone services
US6430276B1 (en) Telecommunications system and method providing generic network access service
US5259026A (en) Method for speed calling automatic update
US7062028B2 (en) Method and apparatus for routing calls based on the identification of the calling party or calling line
US6055302A (en) System and method for incoming and outgoing interrogations for store-and-forward services
JP2006054905A (en) Intelligent telecommunication network
JPH07170342A (en) Dialog of processing between communication call features
JPH11177694A (en) Telephone service management device
US6167126A (en) Method for flexibly provisioning switching devices and a switching device incorporating the same
US6823056B1 (en) Multiple services per trigger within a telecommunications network
US6847639B2 (en) Managing feature interaction among a plurality of independent feature servers in telecommunications servers
EP0922363B1 (en) System and method for incoming and outgoing interrogations for store-and-forward services
GB2431819A (en) Method of realizing call connection in intelligent network system
US20020126818A1 (en) Advanced internet call session manager
JPH10304075A (en) Method and system for realizing intelligent telecommunication service utilizing failure resistant object-oriented architecture having self-persistence
JP3746955B2 (en) Service execution in intelligent networks
FI110655B (en) Reducing messaging traffic in an intelligent network
FI108325B (en) Provision of services in a telecommunications network
US20020018551A1 (en) Initiation of services in telecommunications network
US6661887B1 (en) Service interaction in an intelligent network
US6760425B2 (en) Interworking between services in telecommunications network
US6850482B1 (en) System and method for data traffic redirection
US6968051B1 (en) Programmable feature queues
US20020137495A1 (en) Method for providing in services in a network, and associated network system
US7100107B2 (en) Method of changing service attributes in a service logic execution environment

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): CA JP

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE

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
WWE Wipo information: entry into national phase

Ref document number: 1998913200

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2283861

Country of ref document: CA

Ref country code: CA

Ref document number: 2283861

Kind code of ref document: A

Format of ref document f/p: F

ENP Entry into the national phase

Ref country code: JP

Ref document number: 1998 541836

Kind code of ref document: A

Format of ref document f/p: F

WWP Wipo information: published in national office

Ref document number: 1998913200

Country of ref document: EP

WWW Wipo information: withdrawn in national office

Ref document number: 1998913200

Country of ref document: EP