WO2000013107A9 - Method and apparatus for encoding content characteristics - Google Patents
Method and apparatus for encoding content characteristicsInfo
- Publication number
- WO2000013107A9 WO2000013107A9 PCT/US1999/018990 US9918990W WO0013107A9 WO 2000013107 A9 WO2000013107 A9 WO 2000013107A9 US 9918990 W US9918990 W US 9918990W WO 0013107 A9 WO0013107 A9 WO 0013107A9
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- retrieval
- retrieval characteristics
- computer
- url
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/165—Combined use of TCP and UDP protocols; selection criteria therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/35—Network arrangements, protocols or services for addressing or naming involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/604—Address structures or formats
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Definitions
- This invention relates to the field of computer software, and, more specifically, to optimizing network traffic.
- a computer user may try to obtain a file from a central storage location (server).
- server central storage location
- Existing schemes can waste time looking for the file and can often use an inefficient delivery method to provide the file to the user.
- a network also may include resources, such as printers, modems, file servers, etc., and may also include services, such as electronic mail. Transferring information across a network may be a time consuming process.
- the prior art does not provide an efficient manner to optimize the transfer and retrieval of information on a network.
- a network can be a small system that is physically connected by cables or via wireless communication (a local area network or "LAN”), or several separate networks can be connected together to form a larger network (a wide area network or "WAN").
- LAN local area network
- WAN wide area network
- Other types of networks include the internet, tel- com networks, the World Wide Web, intranets, extranets, wireless networks, and other networks over which electronic, digital, and /or analog data may be communicated.
- the Internet is a client/server system.
- a "client” is the computer that you use to access the Internet.
- Information including data, files, and the web pages to be viewed are often transferred between the client and the server.
- the server or client may have to evaluate the information prior to processing.
- one method for transferring the data may be more efficient than another method depending on the type of data being transferred.
- the Internet is a worldwide network of interconnected computers.
- An Internet client accesses a computer on the network via an Internet provider.
- An Internet provider is an organization that provides a client (e.g., an individual or other organization) with access to the Internet (via analog telephone line or Integrated Services Digital Network line, for example).
- a client can, for example, download a file from or send an electronic mail message to another computer /client using the Internet.
- An Intranet is an internal corporate or organizational network that uses many of the same communications protocols as the Internet.
- the terms Internet, World Wide Web (WWW), and Web as used herein includes the Intranet as well as the Internet.
- the components of the WWW include browser software, network links, and servers.
- the browser software, or browser is a user-friendly interface (i.e., front-end) that simplifies access to the Internet.
- a browser allows a client to communicate a request without having to learn a complicated command syntax, for example.
- a browser typically provides a graphical user interface (GUI) for displaying information and receiving input. Examples of browsers currently available include Netscape Navigator and Internet Explorer.
- GUI graphical user interface
- a browser displays information to a client or user as pages or documents.
- a language called Hypertext Markup Language (HTML) is used to define the format for a page to be displayed in the browser.
- HTML Hypertext Markup Language
- a Web page is transmitted to a client as an HTML document.
- the browser executing at the client parses the document and produces and displays a Web Page based on the information in the HTML document. Consequently, the HTML document defines the Web Page that is rendered at runtime on the browser.
- Transfer Protocols generally specify the data format, timing, sequencing, and error checking of data transmissions. Numerous transfer protocols are used in the networking environment. For example, one family of transfer protocols is referred to as the transmission control protocol /internet protocol ("TCP/IP"). The TCP/IP family of transfer protocols is the set of transfer protocols used on the internet and on many multiplatform networks.
- TCP/IP transmission control protocol /internet protocol
- the TCP/IP transfer protocol family is made up of numerous individual protocols (e.g., file transfer protocol (“FTP”), transmission control protocol (“TCP”), and network terminal protocol (“TELNET”)).
- the TCP protocol is responsible for breaking up a message to be transmitted into datagrams of manageable size, reassembling the datagrams at the receiving end, resending any datagrams that get lost (or are not transferred), and reordering the data (from the datagrams) in the appropriate order.
- a datagram is a unit of data or information (also referred to as a packet) that is transferred or passed across the internet.
- a datagram contains a source and destination address along with the data.
- the TCP transfer protocol is often utilized to transmit large amounts of information because of its ability to break up the information into datagrams and reassemble the information at the receiving end.
- UDP user datagram protocol
- UDP is designed for applications and data transmissions where sequences of datagrams do not need to be reassembled at the receiving end. UDP does not keep track of what has been transmitted in order to resend a datagram if necessary. Additionally, UDP's header information (information regarding the source and destination and other relevant information) is shorter than the header information utilized in TCP.
- HTTP HyperText Transfer Protocol
- HTTP is the standard application protocol for communication with an information server on the WWW. HTTP has communication methods that allow clients to request data from a server and send information to the server.
- the client contacts the HTTP server and transmits the request to the HTTP server.
- the request contains the communication method requested for the transaction (e.g., GET an object from the server or POST data to an object on the server).
- the HTTP server responds to the client by sending a status of the request and the requested information. The connection is then terminated between the client and the HTTP server.
- a client request therefore, consists of establishing a connection between the client and the HTTP server, performing the request, and terminating the connection.
- the HTTP server does not need to maintain any state about the connection once it has been terminated.
- HTTP is, therefore, a stateless application protocol. That is, a client can make several requests of an HTTP server, but each individual request is treated independent of any other request.
- the server has no recollection of any previous request. The server does not need to retain state from a prior request.
- a proxy 102 is a server that carries out requests transmitted to it (i.e., from client 100), keeping copies of fetched documents or information for some time so that they can be accessed more quickly in the future, speeding up access for commonly requested information.
- This maintaining of information and fetched documents by the proxy 102 is referred to as caching and the information maintained in the proxy 102 is referred to as a cache or proxy cache.
- a proxy 102 may be viewed as an intermediary between the server 104 and client 100.
- the client 100 requests information.
- the request is forwarded to the proxy 102.
- the client 100 first checks the proxy cache to see if the relevant information is maintained by the proxy 102. If the proxy cache contains the information, the client 100 does not need to contact the server 104 and loads the information directly from the proxy 102 at step 208. Alternatively, if the proxy cache does not contain the relevant information, the request is forwarded to the server 104 at step 210.
- the client 100 retrieves the information from the server 104. When http is the protocol that is being transmitted over the internet protocol, the proxy 102 is referred to as a web proxy.
- a firewall is a mechanism that blocks access between the client and the server.
- a proxy or proxy server may sit atop a firewall and act as a conduit, providing a specific connection for each network connection.
- Proxy software retains the ability to communicate with external sources, yet is trusted to communicate with the internal network. For example, proxy software may require a username and password to access certain sections of the internal network and completely block other sections from any external access.
- An addressing scheme is employed to identify Internet resources (e.g., HTTP server, file or program). This addressing scheme is called Uniform Resource Locator (URL).
- a URL may contain the application protocol to use when accessing the server (e.g., HTTP), the Internet domain name (also referred to as the server host name) of the site on which the server is running, the port number of the server (the port number may not be specified in the URL but obtained by translating the server host name), and the location of the resource in the file structure of the server.
- the URL "http://www.sunlabs.com/research/hsn/index.html” specifies the application protocol ("http"), the server host name ("www.sunlabs.com”), and the filename to be retrieved (“/research/hsn/index.html”).
- the HTTP server locates the file and sends it to the client.
- An HTTP server also has the ability to delegate work to Common Gateway Interface (CGI) programs.
- CGI Common Gateway Interface
- the CGI specification defines the mechanisms by which HTTP servers communicate with gateway programs.
- a gateway program is referenced using a URL.
- the HTTP server activates the program specified in the URL and uses CGI mechanisms to pass program data sent by the client to the gateway program. Data is passed from the server to the gateway program via command-line arguments, standard input, or environment variables.
- the gateway program processes the data, generates an HTML document, and returns the HTML document as its response to the server using CGI (via standard input, for example).
- the server forwards the HTML document to the client using the HTTP. Once files have been retrieved, the client may utilize or process the file.
- a client's web browser may parse the HTML document and display the document.
- the client may activate an application to process the file. For example, if a word processing document is retrieved, the client may activate a word processor to process the document.
- an image viewer may be activated to process and display the image.
- a file suffix or extension may be utilized.
- a file extension or suffix often consists of a period ".” and several letters that are attached to the end of a file name.
- an HTML document may end with the suffix ".htm” or “.html” (e.g., “index.html” or “home.html”)
- a word processing document filename may end with the suffix ".doc” (e.g., "report.doc” or “letter.doc")
- a JPEG (Joint Photographic Experts Group) image filename may end with the suffix ".jpg” (e.g., “image.jpg” or “picture.jpg”)
- a postscript document (document created in the postscript page description language) may end with the suffix ".ps” (e.g., “calendar.ps” or “font.ps”).
- the client browser Upon receiving a file, the client browser will typically examine the extension to determine how to process the file after receipt (e.g., launch an application program to process the file).
- the client first searches the web proxy cache for the relevant web pages or information and if not present then processes the request with the server requiring a second search.
- UDP transfer protocol instead of TCP (i.e., for smaller files)
- the prior art first attempts to transfer information using UDP at step 302.
- a method and apparatus for encoding characteristics for the retrieval of information In a network of computers, clients and servers communicate and exchange data and information. Depending on characteristics of the data or information, certain methods for exchanging or retrieving the information may be preferred. For example, if the information is too large to utilize a UDP (User Datagram Protocol) transfer protocol, then the TCP (Transmission Control Protocol) transfer protocol may be preferred. In addition, if the information is not cacheable, then it is preferable to retrieve the information directly from the server instead of searching the cache first.
- UDP User Datagram Protocol
- TCP Transmission Control Protocol
- a URL Uniform Resource Locator
- the suffix of a file indicator is utilized to identify how to process the data or information subsequent to retrieval.
- One or more embodiments of the invention provide for encoding characteristics of data to be transferred that indicates or hints at an optimal method to retrieve the data.
- the URL may specify that TCP is the preferred transfer protocol, thereby avoiding an attempted transfer using UDP.
- the encoding may specify that the data is not cacheable so that the client may retrieve the information directly from the server instead of searching the proxy cache. This encoded information may be published by the server and parsed by the client prior to executing data retrieval. Thus, the client may retrieve the data efficiently, decreasing the overhead utilized influencing the behavior of the data transfer over a network.
- the characteristics or preferred retrieval method may be encoded in a any portion of a URL. Additionally, one or more embodiments of the invention provide for backwards compatibility with existing internet browsers by encoding the characteristics in the file location portion of the URL instead of the application protocol identifier portion.
- Figure 1 illustrates the client, server, and proxy relationship.
- Figure 2 demonstrates a prior art method for retrieving information with a proxy.
- Figure 3 demonstrates a prior art method for retrieving information using TCP or UDP.
- Figure 4 is a block diagram of one embodiment of a computer system capable of providing a suitable execution environment for one or more embodiments of the invention.
- Figure 5 demonstrates a method for the encoding and use of information in URLs according to one or more embodiments of the invention.
- the invention is a method and apparatus for encoding content characteristics.
- numerous specific details are set forth to provide a more thorough description of embodiments of the invention. It is apparent, however, to one skilled in the art, that the invention may be practiced without these specific details. In other instances, well known features have not been described in detail so as not to obscure the invention.
- An embodiment of the invention can be implemented as computer software in the form of computer readable code executed on a general purpose computer such as computer 400 illustrated in Figure 4, or in the form of bytecode class files running on such a computer.
- a keyboard 410 and mouse 411 are coupled to a bi-directional system bus 418. The keyboard and mouse are for introducing user input to the computer system and communicating that user input to processor 413. Other suitable input devices may be used in addition to, or in place of, the mouse 411 and keyboard 410.
- I/O (input/ output) unit 419 coupled to bi-directional system bus 418 represents such I/O elements as a printer, A/V (audio/video) I/O, etc.
- Computer 400 includes a video memory 414, main memory 415 and mass storage 412, all coupled to bi-directional system bus 418 along with keyboard 410, mouse 411 and processor 413.
- the mass storage 412 may include both fixed and removable media, such as magnetic, optical or magnetic optical storage systems or any other available mass storage technology.
- Bus 418 may contain, for example, thirty-two address lines for addressing video memory 414 or main memory 415.
- the system bus 418 also includes, for example, a 32-bit data bus for transferring data between and among the components, such as processor 413, main memory 415, video memory 414 and mass storage 412. Alternatively, multiplex data /address lines may be used instead of separate data and address lines.
- the processor 413 is a microprocessor manufactured by Motorola, such as the 680X0 processor or a microprocessor manufactured by Intel, such as the 80X86, or Pentium processor, or a SPARC microprocessor from Sun Microsystems, Inc.
- Main memory 415 is comprised of dynamic random access memory (DRAM).
- Video memory 414 is a dual-ported video random access memory. One port of the video memory 414 is coupled to video amplifier 416.
- the video amplifier 416 is used to drive the cathode ray tube (CRT) raster monitor 417.
- Video amplifier 416 is well known in the art and may be implemented by any suitable apparatus. This circuitry converts pixel data stored in video memory 414 to a raster signal suitable for use by monitor 417.
- Monitor 417 is a type of monitor suitable for displaying graphic images.
- Computer 400 may also include a communication interface 420 coupled to bus 418.
- Communication interface 420 provides a two-way data communication coupling via a network link 421 to a local network 422.
- ISDN integrated services digital network
- communication interface 420 provides a data communication connection to the corresponding type of telephone line, which comprises part of network link 421.
- LAN local area network
- communication interface 420 provides a data communication connection via network link 421 to a compatible LAN.
- Wireless links are also possible.
- communication interface 420 sends and receives electrical, electromagnetic or optical signals which carry digital data streams representing various types of information.
- Network link 421 typically provides data communication through one or more networks to other data devices.
- network link 421 may provide a connection through local network 422 to local server computer 423 or to data equipment operated by an Internet Service Provider (ISP) 124.
- ISP 424 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the "Internet" 425.
- Internet 425 uses electrical, electromagnetic or optical signals which carry digital data streams.
- the signals through the various networks and the signals on network link 421 and through communication interface 420, which carry the digital data to and from computer 400, are exemplary forms of carrier waves transporting the information.
- Computer 400 can send messages and receive data, including program code, through the network(s), network link 421, and communication interface 420.
- remote server computer 426 might transmit a requested code for an application program through Internet 425, ISP 424, local network 422 and communication interface 420.
- one such application is that of remotely configuring a computer.
- the received code may be executed by processor 413 as it is received, and /or stored in mass storage 412, or other non-volatile storage for later execution. In this manner, computer 400 may obtain application code in the form of a carrier wave.
- Application code may be embodied in any form of computer program product.
- a computer program product comprises a medium configured to store or transport computer readable code, or in which computer readable code may be embedded.
- Some examples of computer program products are CD-ROM disks, ROM cards, floppy disks, magnetic tapes, computer hard drives, servers on a network, and carrier waves.
- a variety of facts or hints are encoded into URLs to enable client side optimizations as well as optimizations at intermediate processing points, such as proxy caches or application layer firewalls.
- the facts or hints are characteristics of the data that is to be transferred that allow for optimization in the retrieval of the information from the server thereby influencing the transfer of information across a network. Further, the facts or hints may be encoded into any part of a URL.
- Figure 5 demonstrates a method for the encoding and use of information in URLs according to one or more embodiments of the invention.
- a server has knowledge about the details and characteristics of the information and files the server maintains (e.g., the length of the file, or the fact that the file is cacheable).
- the server or web server may publish one or more of the characteristics regarding the file or transfer of the file in the URL for the file.
- a publication may be a universal convention that applies across all clients and servers.
- the server may provide the encoded information to the clients in a manner that is similar to the way servers provide cookies (a small piece of information that can later be read back from a browser) to a client or browser.
- the server may include an additional (and optional) field in the reply that informs the client about the various retrieval methods and how such information is encoded (referred to as retrieval identifier).
- retrieval identifier When future information is encoded with a retrieval identifier, the client maintains the knowledge regarding the meaning of the retrieval identifier and how to retrieve the encoded information. For example, a single retrieval identifier statement would include the following information:
- the property field may be "not-cacheable” or "TCP-only”; the pattern field may contain "*-nc-*; the applicable host domain field may be "*.sun.com”; and the lifetime field is an optional field that informs the clients when this information expires.
- the client views and examines the published characteristics or transmitted information.
- the client transmits the request to the server (using an application protocol, e.g., HTTP).
- the client request uses the desired retrieval method.
- the retrieval method may consist of the transfer protocol (i.e., TCP or UDP) or it may consist of caching information (i.e., whether the information being transmitted is cacheable or not).
- the server transmits the information to the client using the specified retrieval method.
- the client receives the information and processes it as desired.
- the post-transfer processing may consist of initializing an application program to read or display the file.
- Step 500 of Figure 5 demonstrates the encoding aspects of the present invention.
- the client may optimize the retrieval of the information.
- Some examples of the hints or characteristics that can be encoded are "Don't use UDP", “Please use UDP”, “Don't use TCP”, “Please use TCP”, “Do not cache”, “Cache if possible”, or "Don't retrieve file from proxy”. These messages may be encoded in any portion of the URL.
- the client will not attempt file retrieval using UDP first (steps 302- 304), saving on the wasted overhead of a failed UDP transfer attempt. Instead, the client will retrieve the information using TCP at step 306 without a failed transfer attempt, eliminating steps 302-304.
- the client web browser will go directly to the server to retrieve the information at step 212 instead of performing a cache lookup on the web proxy first eliminating steps 204-210.
- the client web browser will go directly to the server to retrieve the information at step 212 instead of performing a cache lookup on the web proxy first eliminating steps 204-210.
- the URL is encoded with characteristics that will optimize the retrieval of files.
- the protocol identifier can be supplemented with the desired characteristic /retrieval method.
- the URL may be "HTTP/UDP" instead of merely "HTTP”, or to specify that the information is cacheable, the URL may be "HTTP/C".
- web browsers may not be configured to process arbitrary data such as a preferred retrieval method in the application protocol identifier portion of a URL. Thus, users of prior art web browsers will be unable to process any URLs that have such data in the application protocol identifier portion of the URL.
- the ability to use an old web browser with a new data format is referred to as backwards compatibility.
- one or more embodiments of the invention encode the characteristics in the Internet domain name or resource server location portion of the URL.
- the suffix of the resource server location portion may be supplemented with additional characters to indicate the retrieval method.
- the file suffix "htmlt" in the URL may be supplemented with additional characters to indicate the retrieval method.
- One or more embodiments of the invention may provide for the retrieval characteristics to be encoded in the domain name or resource server location portion or the URL and hide that information from display in the web browser.
- Such information may be passed in the form of a parameter in HTML. For example, the file suffix "html?u" in the URL
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP99951380A EP1029410A2 (en) | 1998-09-01 | 1999-08-19 | Method and apparatus for encoding content characteristics |
AU63827/99A AU6382799A (en) | 1998-09-01 | 1999-08-19 | Method and apparatus for encoding content characteristics |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/146,381 US6519646B1 (en) | 1998-09-01 | 1998-09-01 | Method and apparatus for encoding content characteristics |
US09/146,381 | 1998-09-01 |
Publications (3)
Publication Number | Publication Date |
---|---|
WO2000013107A2 WO2000013107A2 (en) | 2000-03-09 |
WO2000013107A3 WO2000013107A3 (en) | 2000-06-08 |
WO2000013107A9 true WO2000013107A9 (en) | 2000-10-26 |
Family
ID=22517117
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1999/018990 WO2000013107A2 (en) | 1998-09-01 | 1999-08-19 | Method and apparatus for encoding content characteristics |
Country Status (4)
Country | Link |
---|---|
US (1) | US6519646B1 (en) |
EP (1) | EP1029410A2 (en) |
AU (1) | AU6382799A (en) |
WO (1) | WO2000013107A2 (en) |
Families Citing this family (46)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8352400B2 (en) | 1991-12-23 | 2013-01-08 | Hoffberg Steven M | Adaptive pattern recognition based controller apparatus and method and human-factored interface therefore |
US6400996B1 (en) * | 1999-02-01 | 2002-06-04 | Steven M. Hoffberg | Adaptive pattern recognition based control system and method |
US20010032278A1 (en) * | 1997-10-07 | 2001-10-18 | Brown Stephen J. | Remote generation and distribution of command programs for programmable devices |
KR100285122B1 (en) * | 1999-01-13 | 2001-03-15 | 이수복 | internet email add-on service system |
US7966078B2 (en) | 1999-02-01 | 2011-06-21 | Steven Hoffberg | Network media appliance system and method |
JP3401719B2 (en) * | 1999-03-30 | 2003-04-28 | パナソニック コミュニケーションズ株式会社 | Image communication device and electronic mail communication method |
US6513062B1 (en) * | 1999-05-25 | 2003-01-28 | Grischa Corporation | Method, apparatus, and computer program product for efficient server response generation using intermediate state caching |
US6751191B1 (en) | 1999-06-29 | 2004-06-15 | Cisco Technology, Inc. | Load sharing and redundancy scheme |
US8032605B2 (en) * | 1999-10-27 | 2011-10-04 | Roy-G-Biv Corporation | Generation and distribution of motion commands over a distributed network |
US20100131078A1 (en) * | 1999-10-27 | 2010-05-27 | Brown David W | Event driven motion systems |
US6683873B1 (en) * | 1999-12-27 | 2004-01-27 | Cisco Technology, Inc. | Methods and apparatus for redirecting network traffic |
US6839829B1 (en) | 2000-01-18 | 2005-01-04 | Cisco Technology, Inc. | Routing protocol based redundancy design for shared-access networks |
US7058007B1 (en) | 2000-01-18 | 2006-06-06 | Cisco Technology, Inc. | Method for a cable modem to rapidly switch to a backup CMTS |
US7231426B1 (en) * | 2000-05-24 | 2007-06-12 | Microsoft Corporation | System and method for sending a web page via electronic mail |
US6968380B1 (en) * | 2000-05-30 | 2005-11-22 | International Business Machines Corporation | Method and system for increasing ease-of-use and bandwidth utilization in wireless devices |
US6985933B1 (en) | 2000-05-30 | 2006-01-10 | International Business Machines Corporation | Method and system for increasing ease-of-use and bandwidth utilization in wireless devices |
US7562147B1 (en) * | 2000-10-02 | 2009-07-14 | Microsoft Corporation | Bi-directional HTTP-based reliable messaging protocol and system utilizing same |
AUPR129300A0 (en) * | 2000-11-07 | 2000-11-30 | Devsecure Pty Ltd | Encoding of universal resource locators in a security gateway to enable manipulation by active content |
FR2817433A1 (en) * | 2000-11-30 | 2002-05-31 | Koninkl Philips Electronics Nv | DATA TRANSMISSION SYSTEM INVOLVING A SERVER, STATION SUITABLE FOR SUCH A SYSTEM, AND METHOD FOR DOWNLOADING DATA |
EP1217806A1 (en) * | 2000-12-22 | 2002-06-26 | Sun Microsystems, Inc. | Network server and method of controlling a network server |
US7904194B2 (en) * | 2001-02-09 | 2011-03-08 | Roy-G-Biv Corporation | Event management systems and methods for motion control systems |
US7881208B1 (en) | 2001-06-18 | 2011-02-01 | Cisco Technology, Inc. | Gateway load balancing protocol |
US20030069998A1 (en) * | 2001-08-31 | 2003-04-10 | Brown David W. | Motion services protocol accessible through uniform resource locator (URL) |
TWI241494B (en) * | 2001-09-07 | 2005-10-11 | Fen Peng | Data storing and updating method for system document and device thereof |
JP4215197B2 (en) * | 2002-04-12 | 2009-01-28 | パナソニック株式会社 | Image encoding method and image decoding method |
MY141160A (en) * | 2003-01-13 | 2010-03-31 | Multimedia Glory Sdn Bhd | System and method of preventing the transmission of known and unknown electronic content to and from servers or workstations connected to a common network |
US7562390B1 (en) * | 2003-05-21 | 2009-07-14 | Foundry Networks, Inc. | System and method for ARP anti-spoofing security |
US7516487B1 (en) | 2003-05-21 | 2009-04-07 | Foundry Networks, Inc. | System and method for source IP anti-spoofing security |
US20040255154A1 (en) * | 2003-06-11 | 2004-12-16 | Foundry Networks, Inc. | Multiple tiered network security system, method and apparatus |
US20050066044A1 (en) * | 2003-06-30 | 2005-03-24 | Hemant Chaskar | IP-based location service within code division multiple access network |
US7876772B2 (en) * | 2003-08-01 | 2011-01-25 | Foundry Networks, Llc | System, method and apparatus for providing multiple access modes in a data communications network |
US7735114B2 (en) * | 2003-09-04 | 2010-06-08 | Foundry Networks, Inc. | Multiple tiered network security system, method and apparatus using dynamic user policy assignment |
US7774833B1 (en) | 2003-09-23 | 2010-08-10 | Foundry Networks, Inc. | System and method for protecting CPU against remote access attacks |
US8027349B2 (en) | 2003-09-25 | 2011-09-27 | Roy-G-Biv Corporation | Database event driven motion systems |
US20060064503A1 (en) * | 2003-09-25 | 2006-03-23 | Brown David W | Data routing systems and methods |
US20070022194A1 (en) * | 2003-09-25 | 2007-01-25 | Brown David W | Database event driven motion systems |
EP1690173A4 (en) * | 2003-11-17 | 2010-04-21 | Roy G Biv Corp | Command processing systems and methods |
US8528071B1 (en) | 2003-12-05 | 2013-09-03 | Foundry Networks, Llc | System and method for flexible authentication in a data communications network |
US8274909B2 (en) * | 2009-03-26 | 2012-09-25 | Limelight Networks, Inc. | Conditional protocol control |
WO2007047986A1 (en) * | 2005-10-21 | 2007-04-26 | Wisconsin Alumni Research Foundation | Method and system for delivering nucleic acid into a target cell |
US20070198482A1 (en) * | 2006-02-21 | 2007-08-23 | International Business Machines Corporation | Dynamic data formatting during transmittal of generalized byte strings, such as XML or large objects, across a network |
US8887039B2 (en) * | 2008-01-02 | 2014-11-11 | Microsoft Corporation | Web page based program versioning |
AU2010276462B1 (en) | 2010-12-27 | 2012-01-12 | Limelight Networks, Inc. | Partial object caching |
CN102203758A (en) * | 2008-09-19 | 2011-09-28 | 杰出网络公司 | Content delivery network stream server vignette distribution |
AU2010202034B1 (en) | 2010-04-07 | 2010-12-23 | Limelight Networks, Inc. | Partial object distribution in content delivery network |
WO2014110736A1 (en) | 2013-01-16 | 2014-07-24 | Nokia Corporation | Web content communication |
Family Cites Families (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5532939A (en) | 1994-07-27 | 1996-07-02 | At&T Global Information Solutions Company | Method and apparatus for data communication efficiency analysis |
US6020885A (en) * | 1995-07-11 | 2000-02-01 | Sony Corporation | Three-dimensional virtual reality space sharing method and system using local and global object identification codes |
US5878233A (en) * | 1995-08-07 | 1999-03-02 | International Business Machines Corporation | System, method, and computer program product for reviewing and creating advisories for data located on a content server |
US6029175A (en) * | 1995-10-26 | 2000-02-22 | Teknowledge Corporation | Automatic retrieval of changed files by a network software agent |
KR19990072122A (en) | 1995-12-12 | 1999-09-27 | 바자니 크레이그 에스 | Method and apparatus for real-time image transmission |
US5862348A (en) * | 1996-02-09 | 1999-01-19 | Citrix Systems, Inc. | Method and apparatus for connecting a client node to a server node based on load levels |
US5963915A (en) * | 1996-02-21 | 1999-10-05 | Infoseek Corporation | Secure, convenient and efficient system and method of performing trans-internet purchase transactions |
US5987134A (en) * | 1996-02-23 | 1999-11-16 | Fuji Xerox Co., Ltd. | Device and method for authenticating user's access rights to resources |
US5878219A (en) | 1996-03-12 | 1999-03-02 | America Online, Inc. | System for integrating access to proprietary and internet resources |
US6025837A (en) * | 1996-03-29 | 2000-02-15 | Micrsoft Corporation | Electronic program guide with hyperlinks to target resources |
US5764910A (en) * | 1996-04-02 | 1998-06-09 | National Semiconductor Corporation | Method and apparatus for encoding and using network resource locators |
US5835712A (en) * | 1996-05-03 | 1998-11-10 | Webmate Technologies, Inc. | Client-server system using embedded hypertext tags for application and database development |
US5944781A (en) * | 1996-05-30 | 1999-08-31 | Sun Microsystems, Inc. | Persistent executable object system and method |
US5961601A (en) * | 1996-06-07 | 1999-10-05 | International Business Machines Corporation | Preserving state information in a continuing conversation between a client and server networked via a stateless protocol |
US5903732A (en) * | 1996-07-03 | 1999-05-11 | Hewlett-Packard Company | Trusted gateway agent for web server programs |
US6058373A (en) * | 1996-10-16 | 2000-05-02 | Microsoft Corporation | System and method for processing electronic order forms |
US6006332A (en) * | 1996-10-21 | 1999-12-21 | Case Western Reserve University | Rights management system for digital media |
US5966135A (en) * | 1996-10-30 | 1999-10-12 | Autodesk, Inc. | Vector-based geographic data |
US5852717A (en) * | 1996-11-20 | 1998-12-22 | Shiva Corporation | Performance optimizations for computer networks utilizing HTTP |
US5991802A (en) * | 1996-11-27 | 1999-11-23 | Microsoft Corporation | Method and system for invoking methods of objects over the internet |
US5896502A (en) * | 1996-12-10 | 1999-04-20 | International Business Machines Corporation | Internet data transfer control via a client system to reduce delay |
US5987504A (en) * | 1996-12-31 | 1999-11-16 | Intel Corporation | Method and apparatus for delivering data |
US6012087A (en) * | 1997-01-14 | 2000-01-04 | Netmind Technologies, Inc. | Unique-change detection of dynamic web pages using history tables of signatures |
US5958053A (en) * | 1997-01-30 | 1999-09-28 | At&T Corp. | Communications protocol with improved security |
US6038603A (en) * | 1997-03-25 | 2000-03-14 | Oracle Corporation | Processing customized uniform resource locators |
US6119167A (en) * | 1997-07-11 | 2000-09-12 | Phone.Com, Inc. | Pushing and pulling data in networks |
US5991810A (en) * | 1997-08-01 | 1999-11-23 | Novell, Inc. | User name authentication for gateway clients accessing a proxy cache server |
US6167453A (en) * | 1997-11-20 | 2000-12-26 | International Business Machines Corporation | Method and apparatus for utilizing URLs to specify local or remote java bean repositories |
US6029200A (en) * | 1998-03-09 | 2000-02-22 | Microsoft Corporation | Automatic protocol rollover in streaming multimedia data delivery system |
-
1998
- 1998-09-01 US US09/146,381 patent/US6519646B1/en not_active Expired - Lifetime
-
1999
- 1999-08-19 AU AU63827/99A patent/AU6382799A/en not_active Abandoned
- 1999-08-19 WO PCT/US1999/018990 patent/WO2000013107A2/en active Application Filing
- 1999-08-19 EP EP99951380A patent/EP1029410A2/en not_active Withdrawn
Also Published As
Publication number | Publication date |
---|---|
AU6382799A (en) | 2000-03-21 |
EP1029410A2 (en) | 2000-08-23 |
WO2000013107A3 (en) | 2000-06-08 |
WO2000013107A2 (en) | 2000-03-09 |
US6519646B1 (en) | 2003-02-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6519646B1 (en) | Method and apparatus for encoding content characteristics | |
EP1886470B1 (en) | Method and system for object prediction | |
US6701374B2 (en) | Method and apparatus for dynamic proxy insertion in network traffic flow | |
US8131823B2 (en) | System and method for reading ahead of content | |
US5948066A (en) | System and method for delivery of information over narrow-band communications links | |
CA2353359C (en) | A system and method for abbreviating information sent to a viewing device | |
US8805957B2 (en) | Method and apparatus for communications over low bandwidth communications networks | |
US7761500B1 (en) | URL based communication protocol from a client computer to a network device | |
US6463447B2 (en) | Optimizing bandwidth consumption for document distribution over a multicast enabled wide area network | |
US20020026460A1 (en) | Reduction of meta data in a network | |
KR20010086381A (en) | Method and apparatus for transparently processing DNS traffic | |
US20090144395A1 (en) | System and method for optimizing content retrieval over a data network | |
US20020156896A1 (en) | System and method for providing a gateway between mobile two-way messaging devices and remote computer networks | |
US20020078076A1 (en) | Simulator disposed between a server and a client system | |
US20140379784A1 (en) | Method and apparatus for using a command design pattern to access and configure network elements | |
US8028091B1 (en) | System and method for reducing DNS lookup traffic in a computer data network | |
WO2001001621A2 (en) | Customizing web content based on network conditions | |
Yap | A technical overview of the New HTTP/1.1 specification | |
KR20000001124A (en) | Multi-server access unification method using yet-another hypertext transmission protocol |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref country code: AU Ref document number: 1999 63827 Kind code of ref document: A Format of ref document f/p: F |
|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM 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 |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1999951380 Country of ref document: EP |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
AK | Designated states |
Kind code of ref document: A3 Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM 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 |
|
AL | Designated countries for regional patents |
Kind code of ref document: A3 Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
WWP | Wipo information: published in national office |
Ref document number: 1999951380 Country of ref document: EP |
|
AK | Designated states |
Kind code of ref document: C2 Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM 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 |
|
AL | Designated countries for regional patents |
Kind code of ref document: C2 Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
COP | Corrected version of pamphlet |
Free format text: PAGES 1/5-5/5, DRAWINGS, REPLACED BY NEW PAGES 1/5-5/5; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |