System and method for providing caller identification for a TDM conference call

BACKGROUND OF THE INVENTION

Time-division multiplexing (TDM) is a method for transferring multiple data streams in a single signal by separating the signal into many segments. The circuit that combines the signals at the transmitting end of a communications link is known as a multiplexer. The multiplexer accepts the input from each individual end user, breaks each signal into segments, and assigns the segments to the composite signal in a rotating sequence. At a receiving end, the individual signals are separated out by a demultiplexer and routed to the proper end users.

TDM technology is often used in conference calls. A conference call is a telephone call connecting multiple telephone lines for enabling simultaneous communication between multiple parties. In most cases, the participants of a conference call calls into a conference call by dialing into a special telephone number that connects to a conference server (a specialized type of equipment that links telephone lines). Most companies use a specialized service provider who maintains the conference server, or who provides the phone numbers and PIN codes that participants dial to access the meeting or conference call.

However, currently, TDM conference call technology does not provide the host with caller identification of participant callers of a conference call. In most situations, a participant calling into the conference call verbally announces their identity when joining the conference call. Thus, the disclosed embodiments recognize that a major security hole exists because anyone that knows a conference call number and/or pin code may call and listen in to a conference call without informing the host of their presence.

SUMMARY

Embodiments of the disclosed invention include a system and method for providing caller identification for a conference call that utilizes a time division multiplex (TDM) telecommunication switching system, hereinafter referred to as a TDM conference call. For example, in accordance with one embodiment, a method performed by a conference server for providing caller identification information for a TDM conference call is disclosed. In one embodiment, the method includes receiving a request from a host to set up a TDM conference call. The method further includes receiving host configuration parameters for providing the host with caller ID information of callers participating in the conference call. The method provides the host with a calling number for enabling callers participating in the conference call to call in. In response to receiving a call and caller ID information associated with a participant calling the calling number, the method connects the call to the conference call and provides the caller ID information to the host based on the host-provided configuration parameters.

In accordance with another embodiment, a conference server for providing caller identification information for a TDM conference call is disclosed. In one embodiment, the conference server includes a memory component for storing computer executable instructions, a processing unit for executing the computer executable instructions, a conference call module for setting up the TDM conference call and for receiving host configuration parameters for providing the host with caller ID information of callers participating in the TDM conference call, a communication interface for receiving a caller ID associated with an incoming call to the TDM conference call, a conference bridge for connecting the incoming call to the TDM conference call, and a caller ID module for providing the caller ID associated with the incoming call to the host based on the host-provided configuration parameters.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments of the present invention are described in detail below with reference to the attached drawing figures, which are incorporated by reference herein and wherein:

<figref idref="DRAWINGS">FIG. 1</figref> depicts an embodiment a network environment in which the illustrative embodiments may be implemented;

<figref idref="DRAWINGS">FIG. 2</figref> depicts an embodiment of a sequence diagram for providing caller identification for a TDM conference call in accordance with the illustrative embodiments;

<figref idref="DRAWINGS">FIG. 3</figref> depicts a conference server in accordance with an illustrative embodiment;

<figref idref="DRAWINGS">FIG. 4</figref> depicts a flowchart illustrating an embodiment of a process for providing caller identification for a TDM conference call in accordance with the illustrative embodiments; and

<figref idref="DRAWINGS">FIG. 5</figref> depicts an embodiment a webpage user interface for configuring the host configuration parameters for a TDM conference call in accordance with the illustrative embodiments.

DETAILED DESCRIPTION

The disclosed embodiments and advantages thereof are best understood by referring to <figref idref="DRAWINGS">FIGS. 1-5</figref> of the drawings, like numerals being used for like and corresponding parts of the various drawings. Other features and advantages of the disclosed embodiments will be or will become apparent to one of ordinary skill in the art upon examination of the following figures and detailed description. It is intended that all such additional features and advantages be included within the scope of the disclosed embodiments, and protected by the accompanying drawings. Further, the illustrated figures are only exemplary and not intended to assert or imply any limitation with regard to the environment, architecture, or process in which different embodiments may be implemented.

<figref idref="DRAWINGS">FIG. 1</figref> depicts an embodiment a network environment <b>100</b> in which the illustrative embodiments may be implemented. In the depicted embodiment, a plurality of devices, such as, but not limited to, one or more communication devices and data processing systems, may communicate over communication network <b>110</b>. In some embodiments, communication network <b>110</b> may include a public switched telephone network (PSTN), a mobile network, and/or a data network, such as, but not limited to, the Internet, for routing communications between the one or more communication devices and data processing systems. The Internet is a global system of interconnected computer networks that interchange data using the standardized Internet Protocol Suite (TCP/IP). In addition, in some embodiments, communication network <b>110</b> may include other types of data networks, such as, but not limited to, an intranet, a private local area network (LAN), a wide area network (WAN), and a wireless local area network (WLAN).

In accordance with the disclosed embodiments, a host <b>132</b> utilizing a communication device <b>130</b> and/or a data processing system <b>128</b> may communicate with a conference server <b>112</b> via communication network <b>110</b> for setting up and configuring a TDM conference call between host <b>132</b>, caller <b>1</b>, caller <b>2</b>, and caller <b>3</b>. In some embodiments, communication device <b>130</b> may be in IP phone, an analog phone, or a cellular phone. Data processing system <b>128</b> may be, but is not limited to, a personal computer, a smart phone, and/or a personal digital assistant (PDA). In addition, caller <b>1</b>, caller <b>2</b>, and caller <b>3</b> may utilize any type of communication device capable of communicating with a communication network <b>110</b> for participating in a TDM conference call. For example, in one embodiment, caller <b>1</b> may utilize an IP phone <b>102</b> with broadband access for enabling voice over IP communication with conference server <b>112</b>. Additionally, caller <b>2</b> may utilize a regular analog phone <b>104</b> and caller <b>3</b> may utilize a cellular phone for communicating with conference server <b>112</b>.

As will be further described, in one embodiment, conference server <b>112</b> comprises a combination of hardware and software that allows 3 or more clients/callers to participate in a real-time voice conference. In some embodiments, conference server <b>112</b> may be a third party network device located within communication network <b>110</b>. Alternatively, in some embodiments, conference server <b>112</b> may be located at a telephone company's central office, such as, but not limited to, central office <b>114</b>. In one embodiment, central office <b>114</b> may be a building in a locality to which subscriber lines associated with conference server <b>112</b> are connected. In some embodiments, central office <b>114</b> may have switching equipment that can switch calls locally or to long-distance carrier phone offices, such as, but not limited to, a class 5 TDM telephone switch <b>116</b>.

In accordance with the disclosed embodiments, class 5 TDM telephone switch <b>116</b> utilizes time division multiplexing technology for providing telephony service to conference server <b>112</b>, such as, but not limited to, local switching, call routing, and other network services. In one embodiment, class 5 TDM telephone switch <b>116</b> may include a number of electrical components, such as, but not limited to, processing unit <b>118</b>, memory <b>120</b>, and data storage <b>122</b>. In some embodiments, processing unit <b>118</b> may comprise a plurality of microprocessors and/or digital circuits for providing the services of class 5 TDM telephone switch <b>116</b>. Memory <b>120</b> may be utilized to store executing computer instructions. In one embodiment, data storage <b>122</b> may store configuration data associated with providing telephony service to conference server <b>112</b>. For example, in accordance with one embodiment, class 5 TDM telephone switch <b>116</b> may be configured to send, to conference server <b>112</b>, the caller IDs associated with incoming calls to a TDM conference call hosted by conference server <b>112</b>. Additionally, in some embodiments, class 5 TDM telephone switch <b>116</b> and/or conference server <b>112</b> may communicate with a calling names database (CNAM) <b>126</b> for retrieving a calling name/subscriber name associated with a caller ID calling into a TDM conference call. In other embodiments, host <b>132</b> may provide a list of expected caller IDs and calling names associated with a TDM conference call for enabling conference server <b>112</b> to retrieve calling names locally from the host-provided list.

In some embodiments, conference server <b>112</b> may communicate with a web server <b>110</b> for receiving configuration data associated with a TDM conference call. For example, in one embodiment, a host utilizing data processing system <b>128</b> may communicate with web server <b>110</b> for setting up and configuring a TDM conference call with conference server <b>112</b>. For instance, in one embodiment, web server <b>110</b> may host a webpage <b>111</b> for enabling a host to reserve and configure a TDM conference call on conference server <b>112</b>. In some embodiments, webpage <b>111</b> may include a user-selectable option for configuring conference server <b>112</b> to provide the caller IDs associated with incoming calls to a TDM conference call to a host. In addition, in some embodiments, webpage <b>111</b> may include a user-selectable option for configuring the means by which the caller IDs associated with incoming calls to the TDM conference are provided to the host. For example, in one embodiment, host <b>132</b> may configure conference server <b>112</b> to provide the caller IDs associated with incoming calls to a TDM conference call as an e-mail message to a host-provided email address. For example, in one embodiment, conference server <b>112</b> may communicate with an email server, such as, but not limited to, email server <b>108</b>, for transmitting email messages. In another embodiment, host <b>132</b> may configure conference server <b>112</b> to provide the caller IDs associated with incoming calls to a TDM conference call as an SMS text message to a host-provided phone number.

With reference now to <figref idref="DRAWINGS">FIG. 2</figref>, an embodiment of a sequence diagram <b>150</b> for providing caller identification for a TDM conference call is presented in accordance with the illustrative embodiments. Sequence diagram <b>150</b> depicts host <b>132</b> utilizing communication device <b>130</b> and/or data processing system <b>128</b> for configuring and monitoring caller ID information associated with participating callers of a TDM conference call. For example, in the depicted embodiment, caller <b>2</b> represents a caller participating in a TDM conference call arranged by host <b>132</b>.

Sequence diagram <b>150</b> begins with host <b>132</b> communicating with conference server <b>112</b> for setting up a TDM conference call. For example, in one embodiment, host <b>132</b> may utilize communication device <b>130</b> to contact conference server <b>112</b> for setting up a TDM conference call and for providing host configuration parameters, such as, but not limited to, an expected time and date of the conference call (step <b>152</b>). As referenced herein, host configuration parameters are settings provided by a host of a TDM conference call for setting up the TDM conference call and may include settings for specifying the means by which the host is provided with the caller IDs of participating callers of the TDM conference call. For instance, in one embodiment, conference server <b>112</b> may utilize an interactive voice response (IVR) system for receiving user input associated with setting up and configuring a TDM conference call. In another embodiment, host <b>132</b> may utilize data processing system <b>128</b> for setting up a TDM conference call and for providing host configuration parameters to conference server <b>112</b> via a webpage (step <b>154</b>). For example, in one embodiment, web server <b>110</b> may host a webpage for enabling a host to request and configure a TDM conference call on conference server <b>112</b>. In these embodiments, web server <b>110</b> may communicate the conference call configuration data to conference server <b>112</b> (step <b>156</b>).

In accordance with one embodiment, when caller <b>2</b>, utilizing communication device <b>104</b>, calls a calling number associated with the arranged conference call (step <b>158</b>), class 5 TDM telephone switch <b>116</b> receives the call and identifies the caller ID, e.g., a telephone number associated with communication device <b>104</b>. As referenced herein, a calling number may include a pin and/or access number for calling into a TDM conference call. In one embodiment, class 5 TDM telephone switch <b>116</b> is configured to pass the call and the caller ID to conference server <b>112</b> (step <b>160</b>). Additionally, in some embodiments, conference server <b>112</b> is configured to communicate with calling names database <b>126</b> for querying (step <b>162</b>) and retrieving a calling name associated with the caller ID (step <b>164</b>). In some embodiments, conference server <b>112</b> may pass the caller ID and calling name to web server <b>110</b> (step <b>166</b>) for enabling web server <b>110</b> to update and display a list of caller IDs and calling names that are connected to a TDM conference call on a webpage (step <b>168</b>). In these embodiments, host <b>132</b> may monitor the webpage, using data processing system <b>128</b>, for identifying the participants of the TDM conference call (step <b>170</b>).

Alternatively, in some embodiments, class 5 TDM telephone switch <b>116</b> may, instead of conference server <b>112</b>, be configured to query (step <b>172</b>) and retrieve a calling name associated with the caller ID (step <b>174</b>). In these embodiments, class 5 TDM telephone switch <b>116</b> may pass the call, caller ID, and calling name to conference server <b>112</b> (step <b>176</b>).

Additionally, in some embodiments, conference server <b>112</b> may be configured with a host-provided list of calling names associated with expected caller IDs corresponding to communication devices of participants of a TDM conference call. In one embodiment, conference server <b>112</b> may be configured to locally retrieve, if available, the calling names corresponding to a caller ID from the host-provided calling list. In addition, in some embodiments, conference server <b>112</b> may be configured to notify/alert host <b>132</b> of an unexpected caller ID in response to a caller ID associated with a caller not being on the host-provided list. In these embodiments, host <b>132</b> may take the appropriate measures for identifying the caller associated with unexpected caller ID, such as, but not limited to, ensuring the caller verbally identify himself.

In addition, in some embodiments, conference server <b>112</b> may be configured to provide the caller ID and calling name of the caller to a host communication device, such as, but not limited to, communication device <b>130</b> (step <b>178</b>). For example, in one embodiment, communication device <b>130</b> may include caller ID capability for displaying the caller ID and calling name on a display component of communication device <b>130</b> (step <b>180</b>). Alternatively, or in addition to, in some embodiments, conference server <b>112</b> may transmit the caller ID and calling name to an e-mail server (step <b>182</b>), such as, but not limited to, e-mail server <b>108</b>, for notifying host <b>132</b> by way of an e-mail message sent to a host-provided e-mail address (step <b>184</b>).

With reference now to <figref idref="DRAWINGS">FIG. 3</figref>, an embodiment of conference server <b>112</b> in accordance with the illustrative embodiments is presented. In the depicted embodiment, conference server <b>112</b> includes, among other things, a processing unit <b>200</b>, a memory component <b>204</b>, and a data storage unit <b>206</b>. Processing unit <b>200</b> may comprise of one or more microprocessors for executing computer usable program code/instructions for providing caller identification for a TDM conference call. For example, in one embodiment, processing unit <b>200</b> executes computer executable instructions <b>220</b> stored in memory component <b>204</b> for retrieving a calling name associated with a caller ID of a participating caller on a TDM conference call.

In some embodiments, memory component <b>204</b> is a volatile memory component of conference server <b>112</b>. Volatile memory is memory that loses its contents when conference server <b>112</b> loses power. For example, in some embodiments, memory component <b>204</b> may be random access memory (RAM). Random access memory stores currently executing instructions and/or data utilized by a software application and/or hardware device.

Data storage unit <b>206</b> is a non-volatile memory component of conference server <b>112</b>, such as, but not limited to, a hard disk drive. Non-volatile memory retains stored data when power is loss. In some embodiments, data storage unit <b>206</b> may be an external hard drive and/or a network data storage unit. Additionally, in some embodiments, data storage unit <b>206</b> may store host configuration parameters <b>224</b> associated with providing caller identification for a TDM conference call. In addition, in some embodiments, data storage unit <b>206</b> may also store a host-provided list of expected caller IDs <b>230</b> in connection with a TDM conference call. For example, in one embodiment, the host-provided list of expected caller IDs <b>230</b> may be utilized to identify and alert a host of an unexpected caller ID. Further, in some embodiments, data storage unit <b>206</b> may store a host-provided list of expected caller IDs with corresponding calling names <b>232</b> for locally identifying the calling names associated with a caller ID.

In addition, conference server <b>112</b> may include a communication interface <b>216</b> for receiving signals and/or data from other network devices, such as, but not limited to, communication device <b>130</b>, data processing system <b>128</b>, web server <b>110</b>, class 5 TDM telephone switch <b>116</b>, and/or calling names database <b>126</b>. For example, in some embodiments, communication interfaces <b>216</b> may include an Ethernet port and/or a telephone line port for connecting conference server <b>112</b> to class 5 TDM telephone switch <b>116</b> over communication network <b>110</b> for receiving caller ID information.

Additionally, in some embodiments, conference server <b>112</b> may include a conference bridge <b>226</b>. In one embodiment, conference bridge <b>226</b> may be a printed circuit board (PCB) with electrical components for bridging or connecting multiple circuits in order to effectuate a TDM conference call. In other embodiments, conference bridge <b>226</b> may be software and/or a combination of hardware and software for handling a TDM conference call.

In some embodiments, conference server <b>112</b> may include a conference call module <b>228</b> for setting up and managing a TDM conference call, such as, but not limited to, handling the joining and leaving of participants. In some embodiments, conference call module <b>228</b> may also handle routing of the call audio from all participants to all other participants. In one embodiment, conference call module <b>228</b> may communicate with an interactive voice response (IVR) module <b>208</b> for receiving user input for reserving and/or configuring a TDM conference call. For instance, in one embodiment, interactive voice response (IVR) module <b>208</b> may answer a phone call from host <b>132</b> and present host <b>132</b> with a list of menus and/or features for configuring a TDM conference call. In other embodiments, conference call module <b>228</b> may communicate with a web interface module <b>214</b> to receive user input for reserving and/or configuring a TDM conference call. For example, in one embodiment, host <b>132</b> reserves and/or configure a TDM conference call with conference server <b>112</b> via a webpage hosted by web server <b>110</b>. In these embodiments, web server <b>110</b> may pass the conference call data to web interface module <b>214</b> for enabling conference server <b>112</b> to configure the TDM conference call. Alternatively, in some embodiments, conference server <b>112</b> may locally host a webpage for enabling a user to reserve and/or configure a TDM conference call.

In addition, in one embodiment, conference server <b>112</b> may include a caller ID module <b>218</b> for receiving a caller ID associated with an incoming call to a TDM conference call from class 5 TDM telephone switch <b>116</b>. In some embodiments, caller ID module <b>218</b> may also receive a calling name associated with a caller ID. In other embodiments, caller ID module <b>218</b> may communicate with a third-party calling names database for querying and retrieving a calling name associated with a caller ID. Alternatively, in some embodiments, caller ID module <b>218</b> may identify a calling name associated with an incoming caller ID using a host-provided caller IDs/calling names list. Further, in some embodiments, caller ID module <b>218</b> may be configured to identify an unexpected caller ID from a host-provided list of expected caller IDs associated with a TDM conference call.

Additionally, in some embodiments, host <b>132</b> may configure the means by which caller ID module <b>218</b> notifies host <b>132</b> of a caller ID, such as, but not limited to, presenting the caller ID on a webpage, sending the caller ID to host <b>132</b> via an e-mail or SMS message, and/or routing the caller ID to a communication device, such as, but not limited to, a conference telephone associated with host <b>132</b>. For instance, in one embodiment, caller ID module <b>218</b> may utilize web interface module <b>214</b> for passing caller ID information from conference server <b>112</b> to web server <b>110</b> for displaying of the caller ID information on a webpage.

<figref idref="DRAWINGS">FIG. 4</figref> depicts a flowchart illustrating an embodiment of a process <b>400</b> for providing caller identification for a TDM conference call in accordance with the disclosed embodiments. In one embodiment, process <b>400</b> may be performed by a conference server, such as, but not limited to, conference server <b>112</b> as depicted in <figref idref="DRAWINGS">FIG. 3</figref>. Process <b>400</b> begins by receiving a request from a host to set up a TDM conference call at step <b>402</b>. For example, in one embodiment, the host provides a desired date and time for reserving conference server <b>112</b> for a TDM conference call. In addition, at step <b>404</b>, the process may receive host configuration parameters associated with the TDM conference call, such as, but not limited to, whether to provide the caller IDs associated with participating callers of the conference call to the host. In one embodiment, the process, at step <b>406</b>, may provide the host with a calling number for enabling a caller to call into conference server <b>112</b> and connect to the conference call. In some embodiments, the host may be provided with a unique access number for enabling conference server <b>112</b> to identify the host.

At step <b>408</b>, the process receives a call and caller ID information corresponding to a caller calling the calling number. In some embodiments, the caller ID information may include a caller ID number and a calling name associated with the caller ID number. In other embodiments, the process may retrieve the calling name from a calling names database. The process, at step <b>410</b>, connects the call to a TDM conference call associated with the calling number. At step <b>412</b>, the process provides caller ID information to the host based on the host configuration parameters associated with the conference call, with process <b>400</b> terminating thereafter. For instance, in one embodiment, the process may transmit the caller ID information to a calling device associated with the host. In other embodiments, the process may update a webpage depicting the caller IDs of participants connected to a TDM conference call.

<figref idref="DRAWINGS">FIG. 5</figref> depicts an embodiment a webpage user interface <b>500</b> for configuring host configuration parameters for a TDM conference call in accordance with the illustrative embodiments. In the depicted embodiment, user interface <b>500</b> includes a user configurable option for selecting a TDM conference call date (<b>501</b>) and start time (<b>502</b>). In addition, in one embodiment, user interface <b>500</b> may provide a host with a calling number and private identification number (PIN) associated with the reserved conference call (<b>504</b>).

In some embodiments, user interface <b>500</b> may include a user-selectable option for receiving participating caller IDs of callers calling into the reserved conference call (<b>506</b>). In addition, in some embodiments, user interface <b>500</b> may include a user configurable notification option <b>508</b>, for selecting one or more means for providing the caller ID information associated with participating callers to the host. For example, in one embodiment, user interface <b>500</b> may include, but is not limited to, a view on webpage option <b>510</b>, a send e-mail to a user specified address option <b>512</b>, a send SMS messages to a user specified phone number option <b>514</b>, and a route to host calling device option <b>516</b>.

Additionally, in some embodiments, user interface <b>500</b> may include a user-selectable option (<b>518</b>) for displaying the calling name associated with a caller ID of a participating caller. In one embodiment, user interface <b>500</b> may include a user-selectable security option (<b>520</b>) for enabling the host to provide a list of expected caller IDs. For example, in one embodiment, conference server <b>112</b> may be configured to notify the host when an unexpected caller ID is encountered. In some embodiments, the host-provided list (<b>526</b>) may include a calling name (<b>524</b>) associated with a particular caller ID (<b>522</b>). Further, in some embodiments, conference server <b>112</b> may be configured to retrieve the calling name locally from the host-provided list of expected caller IDs and calling name.

In summary, the disclosed embodiments present a system and method for providing caller identification for a TDM conference call. As will be appreciated by one skilled in the art, certain aspects of the disclosed embodiments may be embodied as an apparatus, method, or computer program product. In addition, the disclosed embodiments including, but not limited to, the disclosed modules may be implemented entirely with hardware or as a software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects. Furthermore, the disclosed embodiments may take the form of a computer program product embodied in any tangible medium of expression having computer-usable program code embodied in the medium.

Computer program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language, such as Java, Smalltalk, C++, or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

The disclosed embodiments are described above with reference to flowchart illustrations, sequence diagrams, and/or block diagrams. Each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The terminology used herein is for describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprise” and/or “comprising,” when used in this specification and/or the claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described to explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

In addition, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which may include one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The previous detailed description is of a small number of embodiments for implementing the invention and is not intended to be limiting in scope. One of skill in this art will immediately envisage the methods and variations used to implement this invention in other areas than those described in detail. The following claims set forth a number of the embodiments of the invention disclosed with greater particularity.