throbber

`
`
`
` www.uspatentfiles.com
`
`
`
`
`
`
` Filed Wrapper for – WO1999057918
`
`
`
`
`
`
`
`
`Pub. No.:
`WO/1999/057918
`
`
`Publication Date:
`11.11.1999
`Chapter 2 Demand Filed: 01.12.1999
`IPC:
`
`International Application No.:
`
`International Filing Date:
`
`
`PCT/US1999/009493
`
`29.04.1999
`
`
`
`H04Q 3/00 (2006.01), H04Q 3/545 (2006.01)
`
`Applicants: GATEWAY TECHNOLOGIES, INC. [US/US]; Suite 102 1544 Valwood Parkway Carrollton, TX 75006
`(US)
`BROWN, Barry, D.; (US).
`HOGG, John, S.; (US)
`PATEL, Rajiv, P.; Fenwick & West LLP Two Palo Alto Square Palo Alto, CA 94306 (US)
`Agent:
`Priority Data: 09/072,436 04.05.1998 US
`Title
`(EN) TELECOMMUNICATION RESOURCE ALLOCATION
`(FR) ALLOCATION DE RESSOURCES DE TELECOMMUNICATION
`
`Inventors:
`
`
`
`
`
`Abstract:
`
`Designated
`States:
`
`
`(EN)A telecommunication system includes a plurality of applications, a plurality of telecommunication
`resources, and a telecommunication services kernel. At least one telecommunication resource is capable
`of generating an event and each application is capable of responding to an event. The telecommunication
`services kernel couples a requested application triggered by the event with a telecommunication resource
`required by the application. The telecommunication services kernel also de-couples the requested
`application and the required telecommunication resource in response to the requested application
`completing execution. The required telecommunication resource is now available to other applications. A
`method for allocating a telecommunication resource to an application in a telecommunications system is
`also disclosed.
`(FR)Ce système de télécommunication comprend plusieurs applications, plusieurs ressources de
`télécommunication et un noyau de services de télécommunication. Une ressource de télécommunication
`au moins est à même de produire un événement auquel chaque application est en mesure de répondre.
`Le noyau de services de télécommunication couple une application demandée déclenchée par un
`événement à une ressource de télécommunication demandée par l'application. Ce noyau de services de
`télécommunication découple également l'application de la ressource de télécommunication demandées
`en réponse à l'application demandée assurant l'exécution. La ressource de télécommunication
`demandée est alors à la disposition d'autres applications. L'invention porte également sur une technique
`d'allocation d'une ressource de télécommunication à une application dans un système de
`télécommunications.
`AE, AL, AM, AT, AU, AZ, BA, BB, BG, BR, BY, CA, CH, CN, CU, CZ, DE, DK, EE, ES, FI, GB, GD, GE,
`GH, GM, HR, HU, ID, IL, IN, IS, JP, KE, KG, KP, KR, KZ, LC, LK, LR, LS, LT, LU, LV, MD, MG, MK, MN,
`MW, MX, NO, NZ, PL, PT, RO, RU, SD, SE, SG, SI, SK, SL, TJ, TM, TR, TT, UA, UG, UZ, VN, YU, ZA,
`ZW.
`African Regional Intellectual Property Org. (ARIPO) (GH, GM, KE, LS, MW, SD, SL, SZ, UG, ZW)
`Eurasian Patent Organization (EAPO) (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM)
`European Patent Office (EPO) (AT, BE, CH, CY, DE, DK, ES, FI, FR, GB, GR, IE, IT, LU, MC, NL, PT,
`SE)
`African Intellectual Property Organization (OAPI) (BF, BJ, CF, CG, CI, CM, GA, GN, GW, ML, MR, NE,
`SN, TD, TG).
`
`Publication Language:
`Filing Language:
`
`
`
`
`English (EN)
`English (EN)
`
`1
`
`GTL 1005
`IPR of U.S. Patent 7,324,637
`
`

`

`PCT
`WORLD INTELLECTUAL PROPERTY ORGANIZATION
`International Bureau
`INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY (PCT)
`wo 99/57918
`(51) International Patent Classification 6 :
`H04Q 3/00
`
`(11) International Publication Number:
`
`Al
`
`(43) International Publication Date:
`
`11 November 1999 (11.11.99)
`
`(21) International Application Number:
`
`PCT/US99/09493
`
`(22) International Filing Date:
`
`29 April 1999 (29.04.99)
`
`(30) Priority Data:
`09/072,436
`
`4 May 1998 (04.05.98)
`
`us
`
`(71) Applicant: GATEWAY TECHNOLOGIES, INC. [US/US];
`Suite 102, 1544 Valwood Parkway, Carrollton, TX 75006
`(US).
`
`(81) Designated States: AE, AL, AM, AT, AU, AZ, BA, BB, BG,
`BR, BY, CA, CH, CN, CU, CZ, DE, DK, EE, ES, FI, GB,
`GD, GE, GH, GM, HR, HU, ID, IL, IN, IS, JP, KE, KG,
`KP, KR, KZ, LC, LK, LR, LS, LT, LU, LV, MD, MG, MK,
`MN, MW, MX, NO, NZ, PL, PT, RO, RU, SD, SE, SG, SI,
`SK, SL, TJ, TM, TR, TT, UA, UG, UZ, VN, YU, ZA, ZW,
`ARIPO patent (GH, GM, KE, LS, MW, SD, SL, SZ, UG,
`ZW), Eurasian patent (AM, AZ, BY, KG, KZ, MD, RU, TJ,
`TM), European patent (AT, BE, CH, CY, DE, DK, ES, FI,
`FR, GB, GR, IE, IT, LU, MC, NL, PT, SE), OAPI patent
`(BF, BJ, CF, CG, CI, CM, GA, GN, GW, ML, MR, NE,
`SN, TD, TG).
`
`(72) Inventors: BROWN, Barry, D.; 3201 Colby Circle, Mesquite,
`TX 75149 (US). HOGG, John, S.; 1104 Overbill Street, Published
`Hurst, TX 76022 (US).
`With international search report.
`
`(74) Agents: PATEL, Rajiv, P. eta!.; Fenwick & West LLP, Two
`Palo Alto Square, Palo Alto, CA 94306 (US).
`
`(54) Title: TELECOMMUNICATION RESOURCE ALLOCATION
`
`TELECOMMUNICATION
`SERVICE KERNEL 320
`
`SESSION
`MANAGER
`430
`
`SYSTEM
`MANAGER
`425
`
`...
`CONNECTION f'l
`•
`CORE SERVICES MODULE
`MANAGER ~
`INTERFACE
`315a
`445
`,.
`~~==~~==~~~==~!
`
`b..tl APPLICATION
`~ 410
`
`~ESOURCE
`MANAGER
`440
`
`...
`HARDWARE
`MANAGER
`435
`
`(57) Abstract
`
`A telecommunication system includes a plurality of applications, a plurality of telecommunication resources, and a telecommunication
`services kernel. At least one telecommunication resource is capable of generating an event and each application is capable of responding
`to an event. The telecommunication services kernel couples a requested application triggered by the event with a telecommunication
`resource required by the application. The telecommunication services kernel also de-couples the requested application and the required
`telecommunication resource in response to the requested application completing execution. The required telecommunication resource is now
`available to other applications. A method for allocating a telecommunication resource to an application in a telecommunications system is
`also disclosed.
`
`2
`
`

`

`FOR THE PURPOSES OF INFORMATION ONLY
`
`Codes used to identify States party to the PCT on the front pages of pamphlets publishing international applications under the PCT.
`
`AL
`AM
`AT
`AU
`AZ
`BA
`BB
`BE
`BF
`BG
`BJ
`BR
`BY
`CA
`CF
`CG
`CH
`CI
`CM
`CN
`cu
`cz
`DE
`DK
`EE
`
`Albania
`Annenia
`Austria
`Australia
`Azerbaijan
`Bosnia and Herzegovina
`Barbados
`Belgium
`Burkina Faso
`Bulgaria
`Benin
`Brazil
`Belarus
`Canada
`Central African Republic
`Congo
`Switzerland
`C<lte d'Ivoire
`Cameroon
`China
`Cuba
`Czech Republic
`Gennany
`Denmark
`Estonia
`
`ES
`FI
`FR
`GA
`GB
`GE
`GH
`GN
`GR
`HU
`IE
`IL
`IS
`IT
`JP
`KE
`KG
`KP
`
`KR
`KZ
`LC
`LI
`LK
`LR
`
`Spain
`Finland
`France
`Gabon
`United Kingdom
`Georgia
`Ghana
`Guinea
`Greece
`Hungary
`Ireland
`Israel
`Iceland
`Italy
`Japan
`Kenya
`Kyrgyzstan
`Democratic People's
`Republic of Korea
`Republic of Korea
`Kazakstan
`Saint Lucia
`Liechtenstein
`Sri Lanka
`Liberia
`
`LS
`LT
`LU
`LV
`MC
`MD
`MG
`MK
`
`ML
`MN
`MR
`MW
`MX
`NE
`NL
`NO
`NZ
`PL
`PT
`RO
`RU
`SD
`SE
`SG
`
`Lesotho
`Lithuania
`Luxembourg
`Latvia
`Monaco
`Republic of Moldova
`Madagascar
`The fonner Yugoslav
`Republic of Macedonia
`Mali
`Mongolia
`Mauritania
`Malawi
`Mexico
`Niger
`Netherlands
`Norway
`New Zealand
`Poland
`Portugal
`Romania
`Russian Federation
`Sudan
`Sweden
`Singapore
`
`SI
`SK
`SN
`sz
`TD
`TG
`TJ
`TM
`TR
`TT
`UA
`UG
`us
`uz
`VN
`YU
`zw
`
`Slovenia
`Slovakia
`Senegal
`Swaziland
`Chad
`Togo
`Tajikistan
`Turkmenistan
`Turkey
`Trinidad and Tobago
`Ukraine
`Uganda
`United States of America
`Uzbekistan
`VietNam
`Yugoslavia
`Zimbabwe
`
`3
`
`

`

`W099/57918
`
`PCT/US99/09493
`
`TELECOMMUNICATION RESOURCE ALLOCATION .
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`1.
`
`BACKGROUND OF THE INVENTION
`Field of the Invention
`This invention relates to the field of telecommunications systems, and
`more particularly, to systems and methods for allocating telecommunication
`resources to an application in a telecommunications system .
`. 2.
`Description of the Related Art
`Conventional computer telephony products allow for connecting
`applications to particular computer telephony resources, or components. To
`connect these components within a computer telephony product, the
`application must be written to use each manufacturers programming
`interface for the application to be able to communicate with the telephony
`resources. For each telephony resource within a computer telephony product,
`it is necessary to write a portion of the application that is dedicated to
`issuing instructions to that particular type of telephony resource.
`In conventional computer
`telephony products, each application
`includes a design phase, coding phase, testing phase, and integration phase.
`Specifically, each portion of the application must be designed to integrate
`with a specific functionality of each dedicated computer telephony resource
`and the overall product. This functionality is specifically coded, or written,
`using computer language code. Each coded portion of the application is then
`tested to ensure that it functions exactly as designed. Finally, each portion
`of the application must be integrated to create the final product.
`In creating such conventional computer telephony products, multiple
`development paths are followed during the development cycle. Further, the
`complexity of conventional computer telephony products requires a large
`number of paths and a large number of operations along each path.
`Specifically, these paths must be followed for each portion of the overall
`system, such as an interface to a particular computer telephony resource or
`a particular user interface. Moreover, in every instance that a computer
`
`4
`
`

`

`wo 99/57918
`
`PCT /US99/09493
`
`telephony resource is changed or added, the appropriate development path~
`must also be changed or added. This is particularly troublesome when the
`
`computer telephony resource involves different types of hardware.
`
`To help ease development, a
`
`first generation of software based
`
`5
`
`computer telephony products used Computer Aided Software Engineering
`
`(CASE) tools to design systems. These conventional CASE development
`
`systems make it easier to determine how many paths or what changes are
`
`needed on a given path to build or reconfigure a computer telephony product.
`
`These conventional systems, however, do not reduce complexity because they
`
`10
`
`can not, for example, reduce the number of paths needed to complete
`
`changes in a conventional computer telephony product.
`
`A second generation of software based computer telephony products
`
`used Code Generators (CG) to design systems. The CG development systems
`
`automated the process for developing paths to completion. This makes the
`
`15
`
`actual time spent following the paths to completion more reasonable.
`
`Conventional CG developed or derived systems, however, have numerous
`
`drawbacks.
`
`For example, similar to the conventional CASE developed
`
`systems the CG developed systems cannot reduce the number of paths
`
`necessary to be followed for completion.
`
`20
`
`Moreover, any additional computer code input beyond that generated
`
`by the CG program is lost and must to be re-done for each change in the
`
`path to completion. These changes, of course, are tedious and laborious and
`
`the process is prone to introducing new or additional errors into the
`
`computer telephony product.
`
`25
`
`To further help ease the development process, a third generation of
`
`computer telephony products developed through the vendor companies that
`
`produce the computer telephony resources.
`
`Specifically, these vendors
`
`developed two divergent design schemes that provide design specifications
`
`that computer telephony resource manufactures might follow.
`
`If followed,
`
`30
`
`the specifications allow for computer telephony resources from different
`
`vendors to operate within the same computer telephony product.
`
`2
`
`5
`
`

`

`W099/57918
`
`PCT/US99/09493
`
`The first of the two design schemes developed is Multi-Vendor Interface
`Protocol ("MVIP'') and the second design scheme is SCBus. It is noted that
`the original design scheme was called SCSA for Signal Computing System
`Architecture, later this was modified to SCBus, which is Signal Computing
`5 Bus, and it has now been extended for multi-chassis integration and is call
`SCxBus for Signal Computing extended Bus.
`
`Although
`
`these design schemes allow
`for having multi-vendor
`computer telephony resources within a single conventional computer
`telephony product, there are still drawbacks to this generation of computer
`telephony products. Foremost among the problems is that these standards
`only apply to the communications between telephony resources and make no
`changes in the application to telephony resource communication. That is,
`with the MVIP or SCBus protocol, it is possible to put different vendor's
`hardware into the same product, but the application must still be written to
`each individual telephony resource within the product.
`In an attempt to address the shortcomings of the previous three
`generations, a fourth generation of computer telephony products was
`developed. These conventional computer telephony products were developed
`using the MVIP and SCBus design schemes and layered on a new application
`protocol that allowed multiple applications to run on a given set of computer
`telephony resources.
`
`These conventional computer
`
`telephony products do allow
`
`for
`
`allocating multiple
`
`computer
`telephony
`resources
`among multiple
`applications, but only in a static manner. That is, resource allocation in
`these products is fixed during an initialization of the product by using a
`configuration file provided by a product administrator and this configuration
`file cannot be changed without re-starting or re-initializing the product
`which, of course, requires all applications to be shut down.
`This fourth generation of computer telephony products still has a
`number of drawbacks. For example, the computer telephony resources must
`be allocated to an application before any application goes into operation.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`3
`
`6
`
`

`

`W099/57918
`
`PCT/US99/09493
`
`Further, these products lack flexibility, such as dynamic configuration,
`because all resources must be allocated at initialization to particular
`applications. Moreover, these products lack dynamic scalability because the
`addition or subtraction of new computer telephony resources requires re-
`start andre-initializing of the computer telephony product.
`Therefore, there is a need for a telecommunication system and method
`that (1) allows for dynamic configurability of telecommunication resources
`that (2) does not require applications
`to be dedicated
`to particular
`telecommunication resources at development or system initialization, while
`(3) providing system flexibility and scalability by allowing for addition or
`subtraction of telecommunication resources without re-initializing
`the
`telecommunication services system and (4) provides fewer and shorter paths
`to completion for applications.
`
`SUMMARY OF THE INVENTION
`
`The present
`invention
`includes a
`telecommunication
`(including
`computer telephony) system and a method for dynamically allocating one or
`more telecommunication resources to a requesting telecommunications
`application within a telecommunications product. The present invention
`includes computer hardware components; for example, a central processing
`unit, a memory, and a storage device that are coupled through a data bus
`line. The present invention may also include other computer hardware
`components; for example, a video card, a serial port, a device controller, and
`a network card.
`
`In one embodiment, the telecommunication system or product also a
`plurality of telecommunication resources and a telecommunication services
`kernel. The telecommunication system works with one or more applications
`that provide telecommunication functions. Each application is capable of
`responding to an event generated within the telecommunication system.
`Further, at least one telecommunication resource is capable of generating an
`event for a requested application. This event may include executing
`(processing) a requested application.
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`4
`
`7
`
`

`

`W099/57918
`
`PCT /US99/09493
`
`5
`
`15
`
`20
`
`The
`telecommunication
`services kernel couples
`the
`requested
`application with a required telecommunication resource or resources for that
`application. When the application completes execution and finishes use of
`the
`telecommunication resource or resources,
`the
`telecommunication
`services kernel de-couples the required telecommunication resource or
`resources from the requested application and makes it available for another
`instance of that application or another application within the system.
`In one embodiment, the telecommunication services kernel includes a
`system manager module, a session manager module, a hardware manager
`10 module, a resource manager module, and a connection manager module.
`The modules are coupled through a core services module interface to a core
`services module. The core services module passes messages between an
`operating system that interfaces with the hardware components of the
`telecommunication system, and the modules of the telecommunication
`services kernel.
`The system manager module provides an inventory of the plurality of
`logical telecommunication resources in the telecommunication system.
`In
`addition, the system manager starts applications as requested in response to
`the event. The session manager module is coupled to the system manager
`and registers each application that is started and currently executing in the
`telecommunication system.
`The hardware manager module initially configures each physical
`telecommunication resource and maps physical resources into logical units
`that is in or added to the telecommunication system. The hardware manager
`25 module also tracks each telecommunication resource that is not allocated
`from the plurality of telecommunication resources. The resource manager is
`coupled to the hardware manager module. The resource manager module
`tracks each telecommunication resource that is allocated to and in use by
`any application.
`The connection manager module 1s coupled to the resource manager
`module. The connection manager module establishes routing information in
`
`30
`
`5
`
`8
`
`

`

`W099/57918
`
`PCT/US99/09493
`
`all
`
`possible
`
`the telecommunication system using internal routing tables, internal and
`external telephony resource mapping, and it's own internal connection map.
`The routing information includes voice and data paths both internally, as
`well as externally to, the telecommunication system.
`Where possible, the connection manager provides a route from this
`routing information to a telecommunication resource in response to the
`telecommunication resource needing a particular voice or data path. The
`connection manager then notifies the application that the path is either
`successfully set up or was not successful, in which case each application
`10 must determine what further action may be necessary.
`The telecommunication system also includes a virtual device interface
`that is coupled, or may be integrated with, to the telecommunication services
`kernel. The virtual device interface provides an interface between an
`application and the telecommunication services kernel. The virtual device
`interface
`is
`a
`virtual
`telephony
`resource
`having
`telecommunication resource capabilities.
`The virtual device
`interface
`includes a translation unit, a command receive unit, and a command send
`unit.
`
`5
`
`15
`
`20
`
`25
`
`The command receive unit receives a request from the application to
`perform a particular function. The translation unit translates this virtual
`device command from the application to the specific hardware-related
`commands that can be understood by the vendor- or standards-specific
`telecommunication resources
`in
`the
`telecommunication system.
`
`The
`
`command send unit
`
`issues
`the specific commands
`to
`the specific
`telecommunication resource. The components and process also function vice
`versa so that a telecommunication resource command is translated for the
`application.
`
`Thus, applications may be written to this single interface rather than to
`each specific interface associated with each telecommunication resource.
`30 This allows development of systems without prior knowledge or
`understanding of the capabilities of particular hardware vendors or other
`
`6
`
`9
`
`

`

`wo 99/57918
`
`PCT JUS99/09493
`
`telephony resources, thereby reducing and shortening the number of
`
`development paths necessary.
`
`The telecommunication system provides a process for dynamically
`
`assigning at least one telecommunication resource
`
`to the application
`
`5
`
`requesting the telecommunication resources in response to the triggering
`
`event
`
`signal.
`
`Specifically,
`
`the event
`
`signal
`
`is
`
`received by
`
`the
`
`telecommunication services kernel. The telecommunication system starts
`
`and executes an application in response to the event signal.
`
`The application then signals a request for a
`
`telecommunication
`
`10
`
`resource from the telecommunication services kernel.
`
`In response to this
`
`request,
`
`the
`
`telecommunication
`
`services kernel
`
`determines
`
`if
`
`a
`
`telecommunication
`
`resource
`
`is
`
`allocation.
`If
`a
`telecommunication resource is available for allocation it proceeds to allocate
`
`available
`
`for
`
`that available
`
`telecommunication
`
`resource
`
`to
`
`the application.
`
`If
`
`15
`
`telecommunication resources are not available, the application is notified and
`
`the application provides further responses as to a relevant course of action.
`
`When
`
`the
`
`application
`
`completes
`
`execution,
`
`it
`
`notifies
`
`the
`
`telecommunication services kernel. The telecommunication services kernel
`
`de-allocates the telecommunication resource from the application. The
`
`20
`
`telecommunication resource is now available to be allocated for a future
`
`request for a telecommunication resource by an application.
`
`The telecommunication system and method of the present invention
`
`advantageously allows for allocating a telecommunication resource to an
`
`application in a dynamic manner. By keeping a single pool or multiple
`
`25
`
`administrator defined pools of telecommunication resources, rather than
`
`dedicating each particular
`
`telecommunication resources
`
`to particular
`
`applications, the present invention beneficially increases overall system
`
`utilization and efficiency. Moreover, the present invention decreases system
`
`costs because more applications can be introduced into the system without
`
`30
`
`having to arrange for additional dedicated telecommunication resources.
`
`7
`
`10
`
`

`

`W099/57918
`
`PCT/US99/09493
`
`the
`
`In addition,
`the present invention allows for
`telecommunication
`resources to be dynamically added or subtracted from the telecommunication
`system without having
`to
`re-start and
`re-initialize because
`services kernel manages
`
`telecommunication
`
`the
`
`telecommunication
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`resources and
`
`the applications are not dedicated
`to any particular
`telecommunication resource. Further, application developments costs are
`also reduced because applications can be written to a single, standardized
`virtual device interface so that concerns of writing to specific or particular
`vendor or manufacturer defined telecommunication resource specifications
`are eliminated.
`
`The features and advantages described in the specification are not all
`inclusive and, in particular, many additional features and advantages will be
`apparent to one of ordinary skill in the art in view of the drawings,
`specification, and claims. Moreover, it should be noted that the language
`used in the specification has been principally selected for readability and
`instructional purposes, and may not have been selected to delineate or
`circumscribe the inventive subject matter.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`Figure 1 is a block diagram illustrating one embodiment of a
`telecommunication system in accordance with the present invention;
`Figure 2a is a block diagram illustrating one embodiment of a
`telecommunication service system in accordance with the present invention;
`Figure 2b is a block diagram illustrating another embodiment of a
`telecommunication service system in accordance with the present invention;
`Figure 3
`is a block diagram illustrating one embodiment of a
`telecommunication sub-system in a memory that interfaces with a central
`processing unit in accordance with the present invention;
`Figure 4
`is a block diagram illustrating one embodiment of a
`telecommunication service kernel in accordance with the present invention;
`Figure 5 is a block diagram illustrating one embodiment of a system
`manager module in accordance with the present invention;
`
`8
`
`11
`
`

`

`W099/57918
`
`PCT /US99/09493
`
`Figure 6 is a block diagram illustrating one embodiment of a session
`manager module in accordance with the present invention;
`Figure 7 is a block diagram illustrating one embodiment of a hardware
`manager module in accordance with the present invention;
`Figure 8 is a block diagram illustrating one embodiment of a resource
`manager module in accordance with the present invention;
`Figure 9
`is a block diagram illustrating one embodiment of a
`connection manager module in accordance with the present invention;
`Figure 10 is a block diagram illustrating one embodiment of a virtual
`device interface in accordance with the present invention;
`Figure 11 is a flow diagram illustrating one embodiment of a general
`process for allocating a telecommunication resource to an application m a
`telecommunication system in accordance with the present invention;
`Figure 12 is a flow diagram illustrating one embodiment of a process
`for executing an application in a telecommunication system in accordance
`with the present invention;
`Figure 13 is a flow diagram illustrating one embodiment of a process
`for preparing allocation of a telecommunication resource to an application in
`a telecommunication system in accordance with the present invention;
`Figure 14 is a flow diagram illustrating one embodiment of a process
`for establishing a connection between a
`telecommunication resource
`allocated to an application and another point in accordance with the present
`invention;
`
`for
`
`Figure 15 is a flow diagram illustrating one embodiment of a process
`communication
`between
`an
`application
`and
`an
`allocated
`telecommunication resource through a virtual device interface in accordance
`with the present invention; and
`Figure 16 is a flow diagram illustrating one embodiment of a process
`for de-coupling and returning an assigned telecommunication resource from
`an application back to a pool of telecommunication resources m a
`telecommunication system in accordance with the present invention.
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`9
`
`12
`
`

`

`W099/57918
`
`PCT/US99/09493
`
`DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
`The present
`invention
`includes a
`telecommunication
`(including
`computer telephony) system and a method for dynamically allocating one or
`more
`telecommunication resources
`to a
`requesting
`telecommunication
`
`application.
`Figure 1 is a block diagram illustrating one embodiment of a
`telecommunication system 100 in accordance with the present invention.
`The telecommunication system 100 includes a primary telecommunication
`service system 110. The telecommunication system 100 may also include
`one or more additional telecommunication service systems 110' and a
`network 120.
`The primary telecommunication service system 110 and the additional
`telecommunication service systems 110' are coupled as nodes on the network
`120. The network 120 can be any data passing network, for example, local
`area network, wide area network, telecommunication network, or computer
`system data bus. Further, a connection to a public switched telephone
`network ("PSTN") can be made from any node (i.e., the primary node 11 0 or
`any of the additional nodes 1101 within the system.
`Figure 2a is a block diagram illustrating a second embodiment of the
`telecommunication service system 110a in accordance with the present
`invention. The telecommunication service system 110a includes a central
`processing unit ("CPU") 205, a memory 210, a storage device 215, one or
`more telecommunication (including computer telephony) resources 220a-
`220n (generally 220), a data bus 225, and a mezzanine bus 230. The central
`processing unit 205, the memory 210, the storage device 215, and each of
`the telecommunication resources 220a-220n are coupled through the data
`bus 225. Further, each of the telecommunication resources 220a-220n are
`coupled to each other through the mezzanine bus 230.
`The telecommunication service system 11 Oa is coupled to one or more
`standard telecommunication equipment devices or systems ("STE") 235.
`Specifically, each STE device 235 may be coupled to a telecommunication
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`10
`
`13
`
`

`

`W099/57918
`
`PCT/US99/09493
`
`resource, e.g., 220c. The STE device 235 is coupled to a public switched
`
`telephone network ("PSTN") 240.
`
`The central processing unit 205 may be a conventional processor or
`
`processing device or system, for example, a x86 or Pentium™ processor by
`
`5
`
`Intel Corporation of Santa Clara, CA, a SPARC processor by Sun
`
`Microsystems, Inc. or Palo Alto, CA, a PowerPC processor by Motorola, Inc. of
`
`Schaumburg, IL, or other processing device or system that processes
`
`computer instructions. The memory 210 may be a conventional memory
`
`device or system, for example, a dynamic random access memory, a static
`
`10
`
`random access memory, or other memory device or system that stores dates,
`
`instruction, or the like.
`
`It is noted that the memory 210 may extend to
`
`include the storage device 215.
`
`The storage device 215 may be a conventional mass storage device or
`
`system, for example, a hard disk, a CD-ROM, a write-able CD-ROM, a flash
`
`15 memory, tape drive, a compression storage drive, or other storage device or
`
`system that allows for longer term storage of data, instructions, or the like.
`
`The data bus 225 may be a conventional data bus, for example, an Industry
`
`Standard Architecture ("ISA") data bus, a Peripheral Component Interface
`
`("PCI") data bus, or other data bus capable of transferring data, instructions,
`
`20
`
`and the like.
`
`The telecommunication resource ("TR") 220 may be a conventional or
`
`custom line card that interfaces with the PSTN 240 or the STE 235, for
`
`example, a Rhetorex ASI Station Interface Card from Lucent Technologies
`
`Inc., of Murray Hill, NJ, a Natural MicroSystems Station Interface Card from
`
`25 Natural MicroSystems, Inc., of Framingham, MA, or other interface card that
`
`is cable of interfacing with the PSTN 240 or the STE 235. Moreover, the
`
`telecommunication resource 220 can be integrated with the PSTN 240 or the
`
`STE 235. The mezzanine bus 230 may be a conventional mezzanine bus, for
`
`example, a Multi-Vendor Interface Protocol
`
`("MVIP'') bus,
`
`the Signal
`
`30 Computing System Architecture SCBus ("SCBus") or Signal Computing
`
`extended bus ("SCxBus"), or the like.
`
`11
`
`14
`
`

`

`W099/57918
`
`PCT/US99/09493
`
`5
`
`10
`
`15
`
`The STE 235 device or system may be a conventional STE device or
`system, for example, a public branch exchange ("PBX"), a standard
`telephone, a pay telephone, a cellular telephone, an answering system, a
`playback system, a facsimile system, a voice mail system, or other STE device
`or system capable of providing voice, media, or data telecommunication
`functions. The PSTN 240 is a conventional public switched telephone
`network, including wireless communication networks, for example, those
`owned and operated by SBC Communications Inc. of San Antonio, TX or
`Cellular One Group of Dallas, TX, or other public switched telephone network
`that allows for telephone communications.
`Figure 2b is a block diagram illustrating a third embodiment of a
`telecommunication service system 110b in accordance with the present
`invention. The telecommunication service system 11 Ob includes a central
`processing unit system 205a, a data port system 255, a video system 260, a
`network system 265, a storage controller system 275, a hard disk 215a, a
`high speed communication system 270, a data bus 225a, one or more sets
`(pools

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket