Source: http://www.google.com/patents/US20010028654?dq=6,256,642
Timestamp: 2014-10-31 09:29:26
Document Index: 241494255

Matched Legal Cases: ['arty 72', 'arty 72', 'arty 72', 'arty 72', 'arty 72', 'arty 72']

Patent US20010028654 - Architecture for the rapid creation of telephony services in a next ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA service architecture for the rapid development of next generation telephony services that overcomes the limitations of the current closed PSTN architecture and service model. In this architecture services are provided by multiple cooperating distributed service providers. This architecture is built...http://www.google.com/patents/US20010028654?utm_source=gb-gplus-sharePatent US20010028654 - Architecture for the rapid creation of telephony services in a next generation networkAdvanced Patent SearchPublication numberUS20010028654 A1Publication typeApplicationApplication numberUS 09/783,493Publication dateOct 11, 2001Filing dateFeb 14, 2001Priority dateDec 11, 1998Also published asUS6967957Publication number09783493, 783493, US 2001/0028654 A1, US 2001/028654 A1, US 20010028654 A1, US 20010028654A1, US 2001028654 A1, US 2001028654A1, US-A1-20010028654, US-A1-2001028654, US2001/0028654A1, US2001/028654A1, US20010028654 A1, US20010028654A1, US2001028654 A1, US2001028654A1InventorsFarooq Anjum, Francesco Caruso, Ravi Jain, Paolo Missier, Adalberto ZordanOriginal AssigneeFarooq Anjum, Francesco Caruso, Ravi Jain, Paolo Missier, Adalberto ZordanExport CitationBiBTeX, EndNote, RefManReferenced by (21), Classifications (10), Legal Events (10) External Links: USPTO, USPTO Assignment, EspacenetArchitecture for the rapid creation of telephony services in a next generation networkUS 20010028654 A1Abstract A service architecture for the rapid development of next generation telephony services that overcomes the limitations of the current closed PSTN architecture and service model. In this architecture services are provided by multiple cooperating distributed service providers. This architecture is built upon an object-oriented call model which is defined as a small set of extensions to the standard Java Telephony API call model. This new object-oriented call model hides the detail of the underlying call-state management protocols and hardware from applications. Images(6) Claims(8)
DETAILED DESCRIPTION OF THE INVENTION [0023] To understand our invention in detail, reference will be made to the preferred embodiment of our invention the example of which is illustrated in the accompanying drawings. First we describe our inventive Java Call Control model as embodied in a software object as it is used in our inventive architecture to implement service activation and deployment. Second we describe the network and service architecture with which our Java Call Model would operate. [0024] A. Software Object [0025] Our invention is a new call model we call the Java Call Control (JCC) model. Our JCC model is an extension of the JTAPI model to support media negotiation during call set-up. This model hides the details of the underlying communication protocols and architectures. It does this by providing a suitable abstraction of the telephony network (the combined PSTN/IP network), and offers a high-level object model for maintaining and managing the state of a call session. Specifically, our inventive call model (JCC) builds upon complementary ideas developed by the Computer Telephony Integration (CTI) and Information Technology (IT) communities. [0026] The main goals of the JCC in accordance with our invention are to: (1) provide for greater flexibility in service deployment and activation, e.g. support dynamic service download, one-time service activation, and, in accordance with a particular aspect of our invention, multiple parallel sessions between various users; (2) facilitate rapid development of applications by providing higher-layer abstractions (rather than simply sockets or JTAPI); (3) provide application portability across various communication protocols, e.g. SIP or H.323, and across platforms, using Java. [0027] The Java Telephony API (JTAPI), is a portable, object-oriented interface for Java-based computer-telephony applications. This API defines a core call model to support basic call setup and a number of extensions, mostly designed to model call center features, multi-party conference calls, call routing, etc. This core model consists of a few telephony classes and their relationships, and the software objects are as shown in FIG. 2. The Provider 21 is an abstraction of a telephony service provider. A Provider 21 manages Call objects 22, representing calls at various stage of progress. Terminal objects 26 represent the physical endpoint of a call, while Address objects 25 are logical endpoints. Notice that each Address object 25 can be associated with multiple Terminals 26 and vice versa, reflecting the standard configuration for a call center. The Connection object 27 models the logical relationship between a Call object 22 and an Address object 25. For a multi-party call, one Connection object is associated to each leg of the call. Finally, a Terminal Connection 23 represents the relationship between one Connection 27 and one physical terminal 26. [0028] The state of a telephone call is maintained by finite state machines associated with Call, Connection and Terminal connection objects (e.g., when a call is answered by the called party, the originating Connection moves to the CONNECTED state). The complete definition of the state machines is part of the published JTAPI specifications. However, in accordance with our invention, we have extended the state machine on the Connection object to include four new states. FIG. 3 depicts this new call state machine in accordance with our invention. The new states introduced are Sender_Consult (31), Sender_Suspend (32), Receiver_Consult (33), and Receiver_Suspend (34). All state transitions occur in response to events that are generated by the parties involved. One instance of the state machine is instantiated for each connection (leg) of a call. The sender and receiver states are used by the caller's and receiver's connections, respectively. [0029] Table I below shows the state transitions. TABLE I 1. EE1: Caller initiates call attempts. 2. EE2: Time Out. 3. EE3: Called party concludes action (e.g. download). 4. EE4: Called party accepts call. 5. EE5: User hangs up. 6. EE6: Suggest action (e.g. URL for download) to called party. 7. EE7: Called party authorization. 8. EE8: Called party supports media. 9. EE9: Called party does not support media. [0030] The software object itself is structured in accordance with the functional software layers understood by those who practice in the art. FIG. 6 illustrates the functional layers of a software object developed in accordance with our invention. Our new software object would be comprised, in a PC or other smart user terminal 68, of a Session Initiation Protocol (SIP) session control protocol 61 a or an equivalent (e.g. H.323), the JTAPI call model software 62 a, our inventive JCC software 63 a, and the service application 64 a, the software 61 a, 62 a, 63 a, and 64 a supporting the PC hardware and low-level software designated 66 and with the PC 68. As implemented in a gateway 14 between the PSTN 10 and the internet 12, the software object comprising the SIP 61 b, the JTAPI call model 62 b, the JCC software 63 b in accordance with our invention, and the service application 64 b would operate and interface with the gateway hardware and low-level software 65 within the gateway 14. The advantage to this layers approach to the software implementation in accordance with our invention is that our JCC software 63 a, 63 b offers a high-level API to the applications software 64 a, 64 b, thus freeing them for the tasks of call-state maintenance. [0031] B. Service Architecture [0032] Our new service architecture consists of two main software entities: Endpoints and Providers. FIG. 4 illustrates a network designed in accordance with our invention. Endpoints 42 and 44 are entities with a single unique logical address (which may be a phone number or an Internet address) in the system. Services are accessed by Endpoints 44 through a Terminal Manager (TM) 43 a, either resident within the terminal 44 or, in the case of dumb terminals 42, resident in a proxy server 45. A user's terminal may be a black phone, a wireless handset, a laptop, or a workstation. [0033] While endpoints 42 and 44 have a single logical address, service providers 46 manage disjoint sets of such addresses, called domains, and provide network connectivity through the network 47 and session management for the corresponding endpoints 44 and 45. As an example one JCC enabled provider 46 a, in accordance with our invention, manages the call processing logic, defined as a state machine, among peer TMs 43 a. Similarly another JCC enabled provider 46 b manages the call processing logic among another set of peer TMs 43 b. In accordance with our invention, services can be hosted by providers 46 or directly by the TMs 43, or both. [0034] Services traditionally provided in the PSTN can be permanently installed and constantly active at a provider. For instance, an 800-number translation service, which maps 800-numbers to a physical access line number (or an Internet address), can be offered by a Provider for its domain. The number translation can take place in a transparent way during a normal session setup when the caller application requests a connection to a peer identified by the 800 number. (The actual 800-number database could be installed at a provider, or the provider could itself access a database offered by a service provider via the network.) Alternatively, a service can be provided by the user's terminal management (TM) software. For instance, a speed-dialing service, in which important or frequently dialed numbers are mapped to single digits (represented as hardware or software buttons on the user's terminal) could be provided by the TM. Whether a particular service is provided by a TM or a provider depends upon several factors, one consideration being that a service that is likely to be shared by many TMs (e.g. 800-number translation) may be better located at the provider, while services that are very specialized or user-specific may be better located at a TM. [0035] In our invention services are provided by software components that plug-in to the TM or the provider. FIG. 5 illustrates the relationship between the service components and the TMs and providers. Two types of dynamic resources provide access to services. The first consists of terminal components 51 that can be attached to a TM 52 statically, or dynamically during call setup, and typically are user-specific or specialized services. The second type of resource comprises provider components 53 which implement services that typically are shared amongst TMs in the domain and can be inserted into the Java Call Control Platform 54. A terminal component is implemented as a software component (e.g. a JavaBean) that is analogous to (or, depending upon the service, could in fact actually be) a Web applet. A provider component is implemented as a software component (e.g. a JavaBean, Enterprise Java Bean, or a �CORBA Component�, Developing Java Beans, R. Englander, Eds., O'Reilly & Associates; 1997; JavaBeans� 1.01 specification, available at http://java.sun.com/beans/docs/spec.html; CORBA Component Model Draft Specification, available at http://www.omg.org/cgi-bin/doc?ptc/99-10-10′) that is analogous to a Web servlet. (One simple definition of servlets is that servlets are to Web servers what applets are to Web browsers.) An example of a terminal component is a JavaBean that provides a speed-dialing service. An example of a provider component is an Enterprise JavaBean that maintains a cache of 800-number translations, and if a dialed number is not available in the cache, contacts a database offered by an 800-number service provider to obtain the translation. [0036] The motivation for implementing services as software components is that, in principle, different third-party software vendors can provide competing implementations of the same service. For instance, a provider may remove one vendor's implementation of 800-number translation and replace it with another vendor's implementation that offers better functionality (e.g. is more up-to-date), performance (e.g. better caching or search algorithms) or cost. Current software component technology, like JavaBeans and Enterprise JavaBeans, offers support for discovering the attributes of a software component at run-time by means of standardized naming conventions, and, given further standardization of the service interface itself, allowing components to be �plugged-in� for use dynamically. [0037] Provider components 53, such as components 53 a and 53 b depicted in FIG. 5, are registered in a component directly 55 and can be activated either by a TM or implicitly by the platform 54. The 800 number translation service is an example of the latter. A request for a connection to an 800 number triggers the service invocation on the platform. Once the service invocation returns with the translated destination number, the provider completes the connection. Notice that there is nothing preventing a provider implementation from exposing the service to the TM for a direct invocation. [0038] The issue of managing software components in our invention is similar to that of managing applets and servlets in a Web-based client-server environment. In general, in our invention services are registered as software components in a Component Directory. In the case of Terminal Components, our implementation only allows for services that set up communications sessions with different types of media. Thus services are represented by media types, which are described using the familiar notion of Multipurpose Internet Mail Extension (MIME) types. So for instance, suppose that during call setup the caller requests the use of a whiteboard. A specific MIME type, say �media/whiteboard�, is used for the request. On the called party's side, if a Terminal Component is associated with the requested type, then the call can be immediately accepted and the component can be activated. Otherwise, an attempt will be made to obtain a resource that can be associated with that MIME type, using dynamic service download. [0039] Our extended connection state machine, FIG. 3, along with extensions to Session Initiation Protocol (SIP) enables the dynamic service download. SIP is extended with new protocol states, in order to allow parties to negotiate the use of external services that can be activated on demand during session setup. FIG. 7 illustrates the dynamic service download example. The caller 70 initially sends an INVITE message 71 to a party 72 specifying the use of a particular media type. If the called party 72 does not have a resource corresponding to that media, it can respond with an UNSUPPORTED_MEDIA message 73, which moves the caller's connection state to Sender-consult. In this state, the caller's TM 70 has a chance to provide a suggestion 79 to the called party 72, indicating a third-party service provider, reachable through a Uniform Resource Locator (URL), which may be able to supply the resource. If the called party 72 accepts the suggestion, it initiates a negotiation with the third-party provider. Since this operation takes place during call setup but is in fact conducted with a party not involved in the call, the connection for the called party 72 moves to the Receiver_Consult state 74. In this state the called party end may be consulted, e.g. to authorize payment for or download of the service. The caller 70 is notified of the suspension through a SUSPEND event 75, and its connection is moved to Sender_Suspend state 76. When the called party 72 has terminated the acquisition of the resource, it notifies the caller 70. In case of an OK message 77, the caller 70 then resumes its processing by moving the standard (JTAPI) Established state 78. Notice that at any point of time, either party can unilaterally decide to disconnect the call and return to the IDLE state. Also, various timeouts, not indicated in the figure, are set up in order to provide an upper bound on the negotiation time. The remaining standard state transitions are defined in the JTAPI documentation. [0040] Another example of the use of the JCC of our invention for programming complex user-level sessions, together with media negotiation, is the support for concurrent sessions between the same TMs. Consider the example scenario of a business card exchange service. Suppose that, during a session, (after a call has been set up), two users want to exchange their business cards within that session. That is, incidentally, a common problem when business is conducted over the phone and a buyer is repeatedly requested to supply her name, phone number, address, etc. (business card information format is in fact being standardized, and software for performing this function in limited domains, e.g., between PalmPilot hand-held personal computers, is available.) Suppose also that such a card exchange service is in fact available to the users through a third party. [0041] A straightforward way to accommodate this scenario in a service architecture in accordance with our invention is to consider business cards as a new media type. Supporting mid-call negotiation to exchange this media, however, would further complicate the call model. The alternative we use is to start a new call, in which the new media is included during setup, and then manage the logical relationship between the old and the new call. This alternative provides an opportunity to introduce and experiment with dependent relationships between calls, simplifies the design of the Provider for the support of complex interactions, and offers more flexibility to the users. The same Address Objects and Terminal Objects share a number of active calls. Each call connection with the Endpoint is represented by a different connection and terminal connection object. [0042] A higher-level session between TMs consists of all the calls shared by those TMs. Each call can be handled independently, or an explicit parent-child relationship can be enforced among them. In the case of the business card exchange, for instance, the TMs could specify whether terminating the main session would imply the termination of all the further calls that were setup during that session. Managing related calls is also useful for billing. For instance, calls that belong to the same high-level session can be billed together, possibly at a discount. [0043] In our illustrative embodiment, SIP is used as the common signaling protocol among distributed providers. Compared to other proposed protocols, such as H.323, SIP offers the advantages of specification and implementation simplicity, extensibility, and neutrality with respect both to the transport protocol and to address format. The protocol is text-based, much in the spirit of HTTP, and is designed to be part of a larger suite of session management protocols for the internet, that includes for instance the Service Location Protocol (SLP) as well as the Session Definition Protocol (SDP). Namely, we used SIP's features to define specific messages for suspending and resuming a session, for suggesting service providers' URLs, and for informing a party of the unavailability of a resource. [0044] Our inventive architecture can be deployed in various ways to provide for scalability and, potentially, for fault tolerance. In the distributed deployment each provider is responsible for a partition of the global address space, and providers communicate using SIP as their common signaling protocol. In the centralized, �PBX-like� configuration, one single provider manages all the connections, as well as the interface with the PSTN. Other intermediate configurations are possible, ranging from applications that run on top of a dedicated provider, to one centralized call center with only one provider. Providers and endpoints can themselves be connected remotely, or they can be co-located on a host. [0045] Another advantage of the distributed nature of our inventive call model is that it can scale reasonably well with the size of the address space, i.e., ultimately, with the number of endpoints in the network. In fact, while one provider manages an entire partition over the global address space, the partitioning itself is quite arbitrary. This makes it possible to introduce new providers and to reassign addresses to providers as needed in order to balance the load across all of them. Address resolution currently remains a centralized operation that can limit scalability. In our invention, address resolution is done simply by mapping a logical address to the IP addresses and port number of the Provider responsible for that address. The mapping table is managed by a translator server that is, in principle, distinct from all of the providers. A call is setup by contracting the involved provides through the IP address returned by the translator. Each provider will then internally route the call to the appropriate TM, by setting up the call model as described earlier. Several solutions are available for scaling the translation step to a large number of addresses, such as hierarchical resolution. [0046] Another clear benefit of provider distribution is its potential for fault tolerance. We can take advantage of the fact that each call object contains the full call model, i.e., it models all the legs of a call, to provide replication across providers for every single call. In the case of a single provider (i.e., of a �local call�), a detached hot-standby provider can be used for replication. [0047] The foregoing description of the preferred embodiment has been presented to illustrate the invention without intent to be exhaustive or to limit the invention to the form disclosed. In applying the invention, modifications and variations can be made by those skilled in the pertaining art without departing from the scope and spirit of the invention. It is intended that the scope of the invention be defined by the claims appended hereto, and their equivalents. APPENDIX [0048] AIN Advanced Intelligent Network [0049] API Application Programming Interface [0050] CTI Computer Telephony Integration [0051] HTTP HyperText Transport Protocol [0052] ISCP Intelligent Service Control Network [0053] IP Internet Protocol [0054] IT Information Technology [0055] ICC Java Call Control [0056] JTAPI Java Telephony Application Programming Interface [0057] MIME Multipurpose Internet Mail Extension [0058] PSTN Public Switched Telephone Network [0059] RMI Remote Method Integration [0060] SDP Service Definition Protocol [0061] SIP Session Initiation Protocol [0062] SLP Service Location Protocol [0063] TAPI Telephony Application Programming Interface [0064] TM Terminal Manager [0065] TSAPI Telephony Server Application Programming Interface [0066] URL Uniform Resource Locator Referenced byCiting PatentFiling datePublication dateApplicantTitleUS6445695 *Dec 31, 1998Sep 3, 2002Nortel Networks LimitedSystem and method for supporting communications services on behalf of a communications device which cannot provide those services itselfUS6714978 *Dec 15, 1999Mar 30, 2004Worldcom, Inc.Method and system for processing records in a communications networkUS7110368 *Sep 24, 2001Sep 19, 2006Santera Systems, Inc.System and method for distributed multi-party call controlUS7111056 *Oct 8, 1999Sep 19, 2006Nortel Networks LimitedMethod, apparatus and article of manufacture for web-based control of a unified multi-service communication systemUS7184534Dec 19, 2002Feb 27, 2007International Business Machines CorporationUsing a telephony application server for call control with a voice serverUS7243162 *Mar 26, 2001Jul 10, 2007British Telecommunications Public Limited CompanyProcessing network communication control messagesUS7266591 *Dec 17, 2001Sep 4, 2007Verizon Business Global LlcProviding content delivery during a call hold conditionUS7356806Mar 11, 2004Apr 8, 2008Verizon Business Global LlcMethod and system for processing records of events during use of a communications systemUS7397806Dec 1, 2003Jul 8, 2008Siemens AktiengesellschaftMethod for integration of a packet-oriented network into a communication systemUS7418509Nov 13, 2001Aug 26, 2008Nokia CorporationMethod and apparatus for a distributed server treeUS7571221 *Apr 3, 2002Aug 4, 2009Hewlett-Packard Development Company, L.P.Installation of network services in an embedded network serverUS7599354 *Jan 8, 2004Oct 6, 2009M5 Networks, Inc.Architecture and method for rapid development and implementation of voice over IP featuresUS7948973 *Jan 8, 2008May 24, 2011At&T Intellectual Property Ii, L.P.Session initiation protocol (SIP) message incorporating a multi-purpose internet mail extension (MIME) media type for describing the content and format of information included in the SIP messageUS8176213 *Jan 25, 2008May 8, 2012Seiko Epson CorporationProcessing responding device, processing requesting device and their methodsUS8363648May 20, 2011Jan 29, 2013At&T Intellectual Property Ii, L.P.Session initiation protocol (SIP) message incorporating a multi-purpose internet mail extension (MIME) media type for describing the content and format of information included in the SIP messageUS8566454 *Dec 8, 2009Oct 22, 2013Qualcomm IncorporatedMethods for enhancing SDP preconditions signalling for IP multimedia sessionsUS8634412Nov 28, 2012Jan 21, 2014At&T Intellectual Property Ii, L.P.Session initiation protocol (SIP) message incorporating a multi-purpose internet mail extension (MIME) media type for describing the content and format of information included in the SIP messageUS8793338Sep 4, 2007Jul 29, 2014Verizon Patent And Licensing Inc.Providing content delivery during a call hold conditionUS20100220716 *Dec 8, 2009Sep 2, 2010Qualcomm IncorporatedMethods for Enhancing SDP Preconditions Signalling for IP Multimedia SessionsWO2003042852A1 *Oct 28, 2002May 22, 2003Nokia CorpMethod and apparatus for a distributed server treeWO2003052607A1 *Nov 25, 2002Jun 26, 2003Worldcom IncProviding content delivery during a call hold condition* Cited by examinerClassifications U.S. Classification370/401, 370/352International ClassificationH04M7/00, H04Q3/00Cooperative ClassificationH04Q3/0045, H04M7/0003, H04Q3/0054European ClassificationH04M7/00B, H04Q3/00D3H, H04Q3/00D3SLegal EventsDateCodeEventDescriptionMar 18, 2013FPAYFee paymentYear of fee payment: 8Feb 10, 2012ASAssignmentOwner name: INTELLECTUAL VENTURES II LLC, DELAWAREFree format text: MERGER;ASSIGNOR:TTI INVENTIONS B LLC;REEL/FRAME:027682/0210Effective date: 20120206Nov 8, 2010ASAssignmentEffective date: 20100128Owner name: TTI INVENTIONS B LLC, DELAWAREFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TELCORDIA LICENSING COMPANY LLC;REEL/FRAME:025322/0054Jun 11, 2010ASAssignmentOwner name: TELCORDIA TECHNOLOGIES, INC.,NEW JERSEYFree format text: RELEASE;ASSIGNOR:WILMINGTON TRUST COMPANY, AS COLLATERAL AGENT;REEL/FRAME:24515/622Effective date: 20100430Owner name: TELCORDIA TECHNOLOGIES, INC., NEW JERSEYFree format text: RELEASE;ASSIGNOR:WILMINGTON TRUST COMPANY, AS COLLATERAL AGENT;REEL/FRAME:024515/0622Jun 26, 2009ASAssignmentOwner name: TELCORDIA LICENSING COMPANY LLC, NEW JERSEYFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TELCORDIA TECHNOLOGIES, INC.;REEL/FRAME:022878/0821Effective date: 20090616Mar 20, 2009FPAYFee paymentYear of fee payment: 4Mar 17, 2009ASAssignmentOwner name: TELCORDIA TECHNOLOGIES, INC., NEW JERSEYFree format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:WILMINGTON TRUST COMPANY;REEL/FRAME:022408/0410Effective date: 20090220Owner name: TELCORDIA TECHNOLOGIES, INC.,NEW JERSEYFree format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:WILMINGTON TRUST COMPANY;US-ASSIGNMENT DATABASE UPDATED:20100216;REEL/FRAME:22408/410Owner name: TELCORDIA TECHNOLOGIES, INC.,NEW JERSEYFree format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:WILMINGTON TRUST COMPANY;US-ASSIGNMENT DATABASE UPDATED:20100211;REEL/FRAME:22408/410Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:WILMINGTON TRUST COMPANY;US-ASSIGNMENT DATABASE UPDATED:20100330;REEL/FRAME:22408/410Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:WILMINGTON TRUST COMPANY;US-ASSIGNMENT DATABASE UPDATED:20100413;REEL/FRAME:22408/410Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:WILMINGTON TRUST COMPANY;US-ASSIGNMENT DATABASE UPDATED:20100427;REEL/FRAME:22408/410Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:WILMINGTON TRUST COMPANY;US-ASSIGNMENT DATABASE UPDATED:20100511;REEL/FRAME:22408/410Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:WILMINGTON TRUST COMPANY;REEL/FRAME:22408/410Jul 17, 2007ASAssignmentOwner name: WILMINGTON TRUST COMPANY, AS COLLATERAL AGENT, DELFree format text: SECURITY AGREEMENT;ASSIGNOR:TELCORDIA TECHNOLOGIES, INC.;REEL/FRAME:019562/0309Effective date: 20070629Owner name: WILMINGTON TRUST COMPANY, AS COLLATERAL AGENT,DELAFree format text: SECURITY AGREEMENT;ASSIGNOR:TELCORDIA TECHNOLOGIES, INC.;US-ASSIGNMENT DATABASE UPDATED:20100413;REEL/FRAME:19562/309Free format text: SECURITY AGREEMENT;ASSIGNOR:TELCORDIA TECHNOLOGIES, INC.;US-ASSIGNMENT DATABASE UPDATED:20100330;REEL/FRAME:19562/309Free format text: SECURITY AGREEMENT;ASSIGNOR:TELCORDIA TECHNOLOGIES, INC.;US-ASSIGNMENT DATABASE UPDATED:20100518;REEL/FRAME:19562/309Free format text: SECURITY AGREEMENT;ASSIGNOR:TELCORDIA TECHNOLOGIES, INC.;REEL/FRAME:19562/309Jul 6, 2007ASAssignmentOwner name: TELCORDIA TECHNOLOGIES, INC., NEW JERSEYFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:019520/0174Effective date: 20070629Owner name: TELCORDIA TECHNOLOGIES, INC.,NEW JERSEYFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;US-ASSIGNMENT DATABASE UPDATED:20100330;REEL/FRAME:19520/174Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;US-ASSIGNMENT DATABASE UPDATED:20100413;REEL/FRAME:19520/174Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;US-ASSIGNMENT DATABASE UPDATED:20100518;REEL/FRAME:19520/174Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:19520/174Apr 20, 2001ASAssignmentOwner name: TELCORDIA TECHNOLOGIES, INC., NEW JERSEYFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ANJUM, FAROOQ;CARUSO, FRANCESCO;JAIN, RAVI;AND OTHERS;REEL/FRAME:011735/0899;SIGNING DATES FROM 20010220 TO 20010313RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google