Abstract: Concepts and technologies disclosed herein are directed to recursive modularization of service provider components to reduce service delivery time and cost. In accordance with one aspect disclosed herein, a module is executable by a hardware compute resource of a virtualization platform. The module can include a module controller and a module instance. The module controller can expose a set of application programming interfaces (“APIs”). The set of APIs can include a configuration API that collects a configuration to be utilized to instantiate the module instance. The set of APIs also can include an instance provisioning API that instantiates the module instance based upon the configuration. The set of APIs also can include one or more other APIs to manage the module instance. The module instance can be a service module instance. The service module instance can encapsulate additional service module instances that have been instantiated by another module.

Abstract: Concepts and technologies disclosed herein are directed to recursive modularization of service provider components to reduce service delivery time and cost. In accordance with one aspect disclosed herein, a module is executable by a hardware compute resource of a virtualization platform. The module can include a module controller and a module instance. The module controller can expose a set of application programming interfaces (“APIs”). The set of APIs can include a configuration API that collects a configuration to be utilized to instantiate the module instance. The set of APIs also can include an instance provisioning API that instantiates the module instance based upon the configuration. The set of APIs also can include one or more other APIs to manage the module instance. The module instance can be a service module instance. The service module instance can encapsulate additional service module instances that have been instantiated by another module.

Abstract: An AIN system having a service switching point (SSP), a service control point (SCP) and an intelligent peripheral (IPe) is disclosed. A calling party makes a call to a called party which results in a trigger signal at the originating SSP. The trigger signal causes the SSP to access the SCP which, in turn, sends a Send_to_Resource message to the SSP. In response to the Send_to_Resource message, the SSP establishes a first connection to an IPe, whose functionality is required. The IPe establishes a second connection carrying a second call to the called party, the first and second calls being connected at the IPe. The IPe subsequently requests that the SSP merge the first and second calls. In response, the call between the called party and the calling party is connected via the SSP, thereby releasing the IPe connections formerly used to connect calling and called parties.

Abstract: An enhanced intelligent network telephony system includes at least one service nodes (SN) imbued with special routing, message handling and billing capabilities. Using the Extension Parameter in an Analyze-Route message, a service control point (SCP) provides a set of service node parameters including service node identification and message content. The SN receives, processes and implements the services corresponding to the message content. Included among these may be announcement IDs corresponding to announcements, such as advertisements, that the SN can initiate at an intelligent peripheral for playing to calling and called parties, and routing numbers which the SN can use to route a particular destination under certain conditions as per the service needs. The SN is also able to request an originating switch to update an Automated Message Accounting (AMA) record created at the originating switch, using information created by the SN.

Abstract: A self-provisioning names database adds new names to a database for associating names to calling address data in a caller identification with name delivery service. A new caller's name is added to the database each time the new caller places a call to a service subscriber. The database reaches only a nominal size in accordance with Perado's rule that approximately 80% of incoming calls to a subscriber will be from the same small group of callers. Alternatively or in addition, a new party's name is added to the database each time a service subscriber places a call to a party whose name is not already in the names database. Caller names that have been stored in the database and not retrieved for a long period of time are discarded to store new names. Also, the database may periodically request updated data for a stored name, for example, to determine if a different telephone number or address has been assigned to the given name data.