IP Library Granted Patent US 7,127,518
Granted Patent B2
US 7,127,518 · App. 09/835,876 · Granted Oct 24, 2006

System and method for implementing application functionality within a network infrastructure

Assignee: Circadence Corporation
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,127,518
App. No.
09/835,876
Granted
Oct 24, 2006
Kind
B2
Abstract

A system and method for implementing functionality within a network on behalf of first and second computers communicating with each other through the network. A front-end computer is provided within the network having an interface for communicating data traffic with the first computer. A back-end computer is also implemented within the network having an interface for communicating data traffic with the second computer. A communication channel couples the front-end computer and the back-end computer. Data traffic is encoded over the communication channel in a first process in the front-end computer. Data traffic is also encoded over the communication channel in a second process in the back-end computer, wherein the first process and the second process implement compatible semantics.

Claims (50)

1. A method for implementing functionality within a network on behalf of first and second computers communicating with each other through the network, the method comprising the acts of:

providing a front-end computer within the network having an interface for communicating data traffic with the first computer, wherein the front-end computer implements a web server;

providing a back-end computer within the network having an interface for communicating data traffic with the second computer, wherein the back-end computer implements a web server;

providing a communication channel coupling the front-end computer and the back-end computer;

encoding data traffic over the communication channel in a first process in the front-end computer;

encoding data traffic over the communication channel in a second process in the back-end computer,

decoding the encoded data traffic from the front-end computer in a third process in the back-end computer;

decoding the encoded data traffic from the back-end computer in a fourth process in the front-end computer,

wherein the first, second, third, and fourth processes implement preselected compatible semantics to perform the encoding and the decoding on the data traffics

wherein the preselected compatible semantics comprise processes for sharing operational information for the front-end and back-end computers and wherein the act of encoding comprises:

communicating quality of service information about the communication channel between the front-end and back-end computers.

2. The method of claim 1 wherein the act of encoding comprises:

communicating time-based synchronization information defined by the compatible semantics between the front-end computer and the back-end computer.

3. The method of claim 1 wherein the act of encoding comprises compression/decompression processes defined by the compatible semantics.

4. The method of claim 1 wherein the act of encoding comprises encryption/decryption processes defined by the compatible semantics.

5. The method of claim 1 wherein the act of encoding comprises forward error correction processes defined by the compatible semantics.

6. A system for transporting data through a network comprising:

a plurality of client applications generating requests for network services;

a plurality of network servers configured to provide services in response to received requests;

a front-end web server within the network having a first interface configured to handle request/response traffic with the client applications;

a back-end web server within the network having a first interface configured to handle request/response traffic with a selected set of network servers;

a communication channel through the network between the front-end web server and the back-end web server;

encoding the request/response traffic over the communication channel in a first process in the front-end computer;

encoding the request/response traffic over the communication channel in a second process in the back-end computer,

decoding the encoded request/response traffic from the front-end computer in a third process in the back-end computer;

decoding the encoded request/response traffic from the back-end computer in a fourth process in the front-end computer,

wherein the first, second, third, and fourth processes implement preselected compatible semantics to perform the encoding and the decoding on the request/response traffic;

wherein the preselected compatible semantics comprise processes for sharing operational information for the front-end and back-end computers and wherein the act of encoding comprises communicating quality of service information about the communication channel between the front-end and back-end computers; and

wherein the front-end server and the back-end server are time synchronized and the back-end server comprises means for ascertaining when a request/response was issued by the front-end server.

7. The system of claim 6 wherein the front-end server and back-end server are time synchronized and the front-end server comprises means for ascertaining when a request/response was issued by the back-end server.

8. The system of claim 6 wherein the front-end server and back-end server include compression mechanisms for compressing traffic transported across the communication channel.

9. The system of claim 6 wherein the front-end server and back-end server include encryption mechanisms for encrypting traffic transported across the communication channel.

10. The system of claim 6 wherein the front-end server and back-end server include forward error correcting mechanisms for error correcting traffic transported across the communication channel.

11. A system for transporting data through a network comprising:

a plurality of network-connected applications generating requests for network services;

a plurality of network-connected computers configured to provide services in response to received requests;

a plurality of front-end web computers each having at least one interface configured to handle request/response traffic with the network-connected applications;

a plurality of back-end web computers each having at least one interface configured to handle request/response traffic with a selected set of the network-connected computers; and

a many-to-many communication channel through the network between the front-end computers and the back-end computers,

encoding the request/response traffic over the communication channel in a first process in the front-end computer;

encoding the request/response traffic over the communication channel in a second process in the back-end computer,

decoding the encoded request/response traffic from the front-end computer in a third process in the back-end computer;

decoding the encoded request/response traffic from the back-end computer in a fourth process in the front-end computer,

wherein the first, second, third, and fourth processes implement preselected compatible semantics to perform the encoding and the decoding on the request/response traffic;

wherein the preselected compatible semantics comprise processes for sharing operational information for the front-end and back-end computers and wherein the act of encoding comprises communicating quality of service information about the communication channel between the front-end and back-end computers; and

wherein the front-end computer and the back-end computer are time synchronized and the back-end server comprises means for ascertaining when a request/response was issued by the front-end computer.

12. The system of claim 11 wherein the many-to-many communication channel is dynamically re-configurable.

13. The method of claim 1 , wherein the front-end and the back-end computers are programmably assigned to a particular web site.

14. The method of claim 1 , wherein software and hardware mechanisms implementing the processes of the front-end and the back-end computers are below the network protocol layer of an Open System Interconnection (OSI) model.

15. The method of claim 1 , wherein the first computer comprises a web browser and the second computer comprises a server providing a web site and wherein the web browser and the web site server are outside the network.

Assignments (7)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 30, 2021
From: CIRCADENCE CORPORATION
To: SONS OF INNOVATION LLC
Reel/Frame 056106/0493 →
SECURITY INTEREST Recorded Dec 20, 2018
From: CIRCADENCE CORPORATION
To: RUNWAY GROWTH CREDIT FUND INC.
Reel/Frame 047973/0029 →
RELEASE OF SECURITY INTEREST Recorded Dec 11, 2015
From: AUGUSTINE FUND, LP; CAROL W. ASHER REVOCABLE TRUST; LAMPHERE, JTWRS, CHARLES AND SARAH; CRAIG ASHER REVOCABLE TRUST; DLWS PARTNERSHIP; DONALD L. ASHER REVOCABLE TRUST; GABRIEL ASHER 2011 SUSMAN TRUST; HENRY ASHER 2011 SUSMAN TRUST; HOPE E. ASHER REVOCABLE TRUST; MATARAZZO, JOSEPH; NANETTE O. LAMPHERE TRUST; ROBERT G. LAMPHERE TRUST DTD 5/13/93; SARAH ASHER 2011 SUSMAN TRUST; SHOFFNER, JOHN; WILLIAM ASHER 2011 SUSMAN TRUST; VAN VLISSINGEN PROFIT SHARING TRUST; DAVID L. ASHER REVOCABLE TRUST
To: CIRCADENCE CORPORATION
Reel/Frame 037269/0758 →
RELEASE OF SECURITY INTEREST Recorded Dec 9, 2015
From: VAN VLISSINGEN PROFIT SHARING TRUST; JTWRS, CHARLES AND SARAH LAMPHERE; C&S LAMPHERE INVESTMENTS, LLC; CRAIG ASHER REVOCABLE TRUST; CAROL W. ASHER REVOCABLE TRUST; DAVID L. ASHER REVOCABLE TRUST; DONALD L. ASHER REVOCABLE TRUST; GABRIEL ASHER 2011 SUSMAN TRUST; HENRY ASHER 2011 SUSMAN TRUST; HOPE E. KALINSKI REVOCABLE TRUST; SARAH ASHER 2011 SUSMAN TRUST; WILLIAM ASHER 2011 SUSMAN TRUST; SHOFFNER, JOHN; AUGUSTINE FUND, LP; SILVERLEAF CONSULTING, LLC; MATARAZZO, JOSEPH, DR.; HARLAN, JOHN; SAINTS CAPITAL IV, LP; HART, STEPHEN; PASQUALE, JUDY; MELTON, R. NEAL
To: CIRCADENCE CORPORATION
Reel/Frame 037247/0137 →
SECURITY INTEREST Recorded Feb 10, 2015
From: CIRCADENCE CORPORATION
To: VAN VLISSINGEN PROFIT SHARING TRUST; JTWRS, CHARLES AND SARAH LAMPHERE; C&S LAMPHERE INVESTMENTS, LLC; CRAIG ASHER REVOCABLE TRUST; CAROL W. ASHER REVOCABLE TRUST; DAVID L. ASHER REVOCABLE TRUST; DONALD L. ASHER REVOCABLE TRUST; GABRIEL ASHER 2011 SUSMAN TRUST; HENRY ASHER 2011 SUSMAN TRUST; HOPE E. KALINSKI REVOCABLE TRUST; SARAH ASHER 2011 SUSMAN TRUST; WILLIAM ASHER 2011 SUSMAN TRUST; SHOFFNER, JOHN; AUGUSTINE FUND, LP; SILVERLEAF CONSULTING, LLC; MATARAZZO, DR. JOSEPH, DR.; HARLAN, JOHN; SAINTS CAPITAL IV, LP; HART, STEPHEN; PASQUALE, JUDY; MELTON, R. NEAL
Reel/Frame 034927/0043 →
SECURITY AGREEMENT Recorded May 10, 2012
From: CIRCADENCE CORPORATION
To: DLWS PARTNERSHIP; AUGUSTINE FUND, LP; CAROL W. ASHER REVOCABLE TRUST; CHARLES AND SARAH LAMPHERE, JTWRS; CRAIG ASHER REVOCABLE TRUST; DONALD L. ASHER REVOCABLE TRUST; GABRIEL ASHER 2011 SUSMAN TRUST; HENRY ASHER 2011 SUSMAN TRUST; HOPE E. ASHER REVOCABLE TRUST; MATARAZZO, JOSEPH; NANETTE O. LAMPHERE TRUST; ROBERT G. LAMPHERE TRUST DTD 5/13/93; SARAH ASHER 2011 SUSMAN TRUST; SHOFFNER, JOHN; WILLIAM ASHER 2011 SUSMAN TRUST; VAN VLISSINGEN PROFIT SHARING TRUST; DAVID L. ASHER REVOCABLE TRUST
Reel/Frame 028192/0705 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 13, 2001
From: VANGE, MARK; PLUMB, MARC; KOUTS, MICHAEL; WILSON, GLENN SYDNEY
To: CIRCADENCE CORPORATION
Reel/Frame 012074/0332 →
Continuity (2)
Provisional Application 6019749000 · Apr 17, 2000
Related Publication 20020002636A1 · Jan 3, 2002