WO1998034385A1 - Automatic detection of protocols in a network - Google Patents
Automatic detection of protocols in a network Download PDFInfo
- Publication number
- WO1998034385A1 WO1998034385A1 PCT/US1998/001797 US9801797W WO9834385A1 WO 1998034385 A1 WO1998034385 A1 WO 1998034385A1 US 9801797 W US9801797 W US 9801797W WO 9834385 A1 WO9834385 A1 WO 9834385A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- protocol
- computer
- data
- responses
- server
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/16—Analogue secrecy systems; Analogue subscription systems
- H04N7/173—Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
- H04N7/17309—Transmission or handling of upstream communications
- H04N7/17336—Handling of requests in head-ends
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
- H04L65/612—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/80—Responding to QoS
-
- 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/61—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 taking into account QoS or priority requirements
-
- 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/63—Routing a service request depending on the request content or context
-
- 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/18—Multiprotocol handlers, e.g. single devices capable of handling multiple 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/24—Negotiation of communication capabilities
-
- 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]
-
- 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
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/234—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs
- H04N21/23406—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs involving management of server-side video buffer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/234—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs
- H04N21/2343—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
- H04N21/234381—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements by altering the temporal resolution, e.g. decreasing the frame rate by frame skipping
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/234—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs
- H04N21/2343—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
- H04N21/23439—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements for generating different versions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/44—Processing of video elementary streams, e.g. splicing a video clip retrieved from local storage with an incoming video stream, rendering scenes according to MPEG-4 scene graphs
- H04N21/44004—Processing of video elementary streams, e.g. splicing a video clip retrieved from local storage with an incoming video stream, rendering scenes according to MPEG-4 scene graphs involving video buffer management, e.g. video decoder buffer or video display buffer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/44—Processing of video elementary streams, e.g. splicing a video clip retrieved from local storage with an incoming video stream, rendering scenes according to MPEG-4 scene graphs
- H04N21/4402—Processing of video elementary streams, e.g. splicing a video clip retrieved from local storage with an incoming video stream, rendering scenes according to MPEG-4 scene graphs involving reformatting operations of video signals for household redistribution, storage or real-time display
- H04N21/440281—Processing of video elementary streams, e.g. splicing a video clip retrieved from local storage with an incoming video stream, rendering scenes according to MPEG-4 scene graphs involving reformatting operations of video signals for household redistribution, storage or real-time display by altering the temporal resolution, e.g. by frame skipping
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/637—Control signals issued by the client directed to the server or network components
- H04N21/6373—Control signals issued by the client directed to the server or network components for rate control, e.g. request to the server to modify its transmission rate
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/637—Control signals issued by the client directed to the server or network components
- H04N21/6377—Control signals issued by the client directed to the server or network components directed to server
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/637—Control signals issued by the client directed to the server or network components
- H04N21/6377—Control signals issued by the client directed to the server or network components directed to server
- H04N21/6379—Control signals issued by the client directed to the server or network components directed to server directed to encoder, e.g. for requesting a lower encoding rate
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/65—Transmission of management data between client and server
- H04N21/658—Transmission by the client directed to the server
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/65—Transmission of management data between client and server
- H04N21/658—Transmission by the client directed to the server
- H04N21/6587—Control parameters, e.g. trick play commands, viewpoint selection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/85—Assembly of content; Generation of multimedia applications
- H04N21/854—Content authoring
- H04N21/8547—Content authoring involving timestamps for synchronizing content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session 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/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/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
Definitions
- the present invention relates to data communication in a computer network. More particularly, the present invention relates to improved methods and apparatus for permitting a client computer in a client-server architecture computer network to automatically detect the most advantageous protocol, among the protocols available, for use in communicating with the server irrespective whether there exist firewalls or proxies in the network.
- Client-server architectures are well known to those skilled in the computer art. For example, in a typical computer network, one or more client computers may be coupled to any number of server computers. Client computers typically refer to terminals or personal computers through which end users interact with the network. Server computers typically represent nodes in the computer network where data, application programs, and the like reside. Server computers may also represent nodes in the network for forwarding data, programs, and the like from other servers to the requesting client computers.
- Fig. 1 illustrates a computer network 100, representing for example a subset of an international computer network popularly known as the Internet.
- the Internet represents a well-known international computer network that links, among others, various military, governmental, educational, nonprofit, industrial and financial institutions, commercial enterprises, and individuals.
- server computer 104 is separated from client computer 106 by a firewall 108, which may be implemented in either software or hardware, and may reside on a computer and/or circuit between client computer 106 and server computer 104.
- Firewall 108 may be specified, as is well known to those skilled in the art, to prevent certain types of data and/or protocols from traversing through it.
- the specific data and/or protocols prohibited or permitted to traverse firewall 108 depend on the firewall parameters, which are typically set by a system administrator responsible for the maintenance and security of client computer 106 and/or other computers connected to it, e.g., other computers in a local area network.
- firewall 108 may be set up to prevent TCP, UDP, or HTTP (Transmission Control Protocol, User Datagram Protocol, and Hypertext Transfer Protocol, respectively) data and/or other protocols from being transmitted between client computer 106 and server 104.
- the firewalls could be configured to allow specific TCP or UDP sessions, for example outgoing TCP connection to certain ports, UDP sessions to certain ports, and the like.
- any type of data and/or protocol may be communicated between a client computer and a server computer if appropriate software and/or hardware are employed.
- server 102 resides on the same side of firewall 108 as client computer 106, i.e., firewall 108 is not disposed in between the communication path between server 102 and client computer 106. Accordingly, few if any, of the protocols that client computer 106 may employ to communicate with server 102 may be blocked.
- proxies i.e., software codes or hardware circuities that facilitate the indirect communication between a client computer and a server around a firewall.
- client computer 106 may communicate with server 104 through proxy 120.
- proxy 120 HTTP data, which may otherwise be blocked by firewall 108 for the purpose of this example, may be transmitted between client computer 106 and server computer 104.
- one or more protocols may be available for communication between the client computer and the server computer.
- one of these protocols is often more advantageous, i.e., suitable, than others.
- the client computer executing that application selects a protocol that permits the greatest degree of control over the transmission of data packets and/or enables data transmission to occur at the highest possible rate. This is because these applications are fairly demanding in terms of their bit rate and connection reliability requirements. Accordingly, the quality of the data rendered, e.g., the video and/or audio clips played, often depends on whether the user has successfully configured the client computer to receive data from the server computer using the most advantageous protocol available.
- the selection of the most advantageous protocol for communication between client computer 106 and server computer 104 typically requires a high degree of technical sophistication on the part of the user of client computer 106.
- the most advantageous protocol communication e.g., in terms of data transmission rate, transmission control, and the like.
- the ability to employ the most advantageous protocol for communication, while desirable for most networking applications, is particularly critical in applications such as real-time data rendering (e.g., rendering of audio, video, and/or annotation data as they are received from the server). If a less than optimal protocol is chosen for communication, the quality of the rendered data, e.g., the video clips and/or audio clips, may suffer.
- the invention relates, in one embodiment, to a method in a computer network for automatically detecting a most advantageous protocol for communication by a client computer.
- the client computer is configured to be coupled to a server computer via a computer network.
- the method includes sending from the client computer to the server computer, a plurality of data requests. Each of the data requests employs a different protocol and a different connection.
- the data requests are configured to solicit, responsive to the data requests, a set of responses from the server computer.
- Each of the responses employs a protocol associated with a respective one of the data requests.
- the method further includes receiving at the client computer at least a subset of the responses.
- the method also includes monitoring the subset of the responses as each response is received from the server computer to select the most advantageous protocol from protocols associated with the subset of the responses, wherein the most advantageous protocol is determined based on a predefined protocol priority.
- the invention in another embodiment, relates to a method in a computer network for automatically detecting a most advantageous protocol for communication by a client computer.
- the client computer is configured to be coupled to a server computer via a computer network.
- the method includes sending from the client computer to the server computer, a plurality of data requests. Each of the data requests employs a different protocol and a different connection.
- the method further includes receiving at least a subset of the data requests at the server computer.
- the method additionally includes sending a set of responses form the server computer to the client computer.
- the set of responses is responsive to the subset of the data requests.
- Each of the responses employs a protocol associated with a respective one of the subset of the data requests.
- the method also includes receiving at the client computer at least a subset of the responses. There is further included selecting, for the communication between the client computer and the server computer, the most advantageous protocol from protocols associated with the subset of the responses, wherein the most advantageous protocol is determined based on a predefined protocol priority.
- the invention relates to a computer-readable medium containing computer-readable instructions for automatically detecting a most advantageous protocol for communication by a client computer.
- the client computer is configured to be coupled to a server computer via a computer network.
- the computer-readable instructions comprise computer-readable instructions for sending in a substantially parallel manner, from the client computer to the server computer, a plurality of data requests. Each of the data requests employs a different protocol and a different connection.
- the data requests are configured to solicit, responsive to the data requests, a set of responses from the server computer. Each of the responses employs a protocol associated with a respective one of the data requests.
- the computer-readable medium further includes computer-readable instructions for receiving at the client computer at least a subset of the responses.
- FIG. 1 illustrates a computer network, representing for example a portion of an international computer network popularly known as the Internet.
- Fig. 2 is a block diagram of an exemplar computer system for carrying out the autodetect technique according to one embodiment of the invention.
- Fig. 3 illustrates, in accordance with one embodiment, the control and data connections between a client application and a server computer when no firewall is provided in the network.
- Fig. 4 illustrates another network arrangement wherein control and data connections are established through a firewall.
- Figs. 5A-B illustrate another network arrangement wherein media control commands and media data may be communicated between a client computer and server computer using the HTTP protocol.
- Figs. 5C-D illustrate another network arrangement wherein multiple HTTP control and data connections are multiplexed through a single HTTP port.
- Fig. 6 illustrates another network arrangement wherein control and data connections are transmitted between the client application and the server computer via a proxy.
- Fig. 7 depicts, in accordance with one embodiment of the present invention, a simplified flowchart illustrating the steps of the inventive autodetect technique.
- Fig. 8 A depicts, in accordance with one aspect of the present invention, the steps involved in executing the UDP protocol thread of Fig. 7.
- Fig. 8B depicts, in accordance with one aspect of the present invention, the steps involved in executing the TCP protocol thread of Fig. 7.
- Fig. 8C depicts, in accordance with one aspect of the present invention, the steps involved in executing the HTTP protocol thread of Fig. 7.
- Fig. 8D depicts, in accordance with one aspect of the present invention, the steps involved in executing the HTTP 80 protocol thread of Fig. 7.
- Fig. 8E depicts, in accordance with one aspect of the present invention, the steps involved in executing the HTTP 8080 protocol thread of Fig. 7.
- Fig. 9 illustrates, in accordance with one embodiment of the present invention, the steps involved in executing the control thread of Fig. 7.
- the client computer in a heterogeneous client-server computer network (e.g., client computer 106 in Fig. 1) is provided with an autodetect mechanism.
- the autodetect mechanism advantageously permits client computer 106 to select, in an efficient and automatic manner, the most advantageous protocol for communication between the client computer and its server. Once the most advantageous protocol is selected, parameters pertaining to the selected protocol are saved to enable the client computer, in future sessions, to employ the same selected protocol for communication.
- the inventive autodetect mechanism simultaneously employs multiple threads, through multiple connections, to initiate communication with the server computer, e.g., server 104.
- Each thread preferably employs a different protocol and requests the server computer to respond to the client computer using the protocol associated with that thread.
- client computer 106 may, employing the autodetect mechanism, initiate five different threads, using respectively the TCP, UDP, one of HTTP and HTTP proxy, HTTP through port (multiplex) 80, and HTTP through port (multiplex) 8080 protocols to request server 104 to respond.
- server 104 Upon receiving a request, server 104 responds with data using the same protocol as that associated with the thread on which the request arrives. If one or more protocols is blocked and fails to reach server 104 (e.g., by a firewall), no response employing the blocked protocol would of course be transmitted from server 104 to client computer 106. Further, some of the protocols transmitted from server 104 to client computer 106 may be blocked as well. Accordingly, client computer may receive only a subset of the responses sent from server 104. In one embodiment, client computer 106 monitors the set of received responses. If the predefined "best" protocol is received, that protocol is then selected for communication by client computer 106. The predefined "best" protocol may be defined in advance by the user and/or the application program.
- the most advantageous protocol may simply be selected from the set of protocols received back by the client computer. In one embodiment, the selection may be made among the set of protocols received back by the client computer within a predefined time period after the requests are sent out in parallel.
- the selection of the most advantageous protocol for communication among the protocols received by client computer 106 may be performed in accordance with some predefined priority.
- the UDP protocol may be preferred over TCP protocol, which may in turn be preferred over the HTTP protocol.
- HTTP data while popular nowadays for use in transmitting web pages, typically involves a higher number of overhead bits, making it less efficient relative to the UDP protocol for transmitting real-time data.
- the HTTP protocol is typically built on top of TCP.
- the underlaying TCP protocol typically handles the transmission and retransmission requests of individual data packets automatically. Accordingly, the HTTP protocol tends to reduce the degree of control client computer 106 has over the transmission of the data packets between server 104 and client computer 106.
- other priority schemes may exist for different applications, or even for different real-time data rendering applications.
- the autodetect mechanism is invoked to allow client computer 106 to send transmission requests in parallel (e.g., using different protocols over different connections) in the manner discussed earlier.
- server 104 responds with data via multiple connections/protocols and the most advantageous protocol has been selected by client computer 106 for communication (in accordance with some predefined priority), the parameters associated with the selected protocol are then saved for future communication.
- the autodetect mechanism may be disabled, and future communication between client computer 106 and server 104 may proceed using the selected most advantageous protocol without further invocation of the autodetect mechanism. If the topology of computer network 100 changes and communication using the previously selected "most advantageous" protocol is no longer appropriate, the autodetect mechanism may be executed again to allow client computer 106 to ascertain a new "most advantageous" protocol for communication with server 104.
- the user of client computer 106 may, if desired, initiate the autodetect mechanism at any time in order to enable client computer 106 to update the "most advantageous" protocol for communication with server 104 (e.g., when the user of client computer 106 has reasons to suspect that the previously selected "most advantageous" protocol is no longer the most optimal protocol for communication).
- the inventive autodetect mechanism may be implemented either in software or hardware, e.g., via an IC chip. If implemented in software, it may be carried out by any number of computers capable of functioning as a client computer in a computer network.
- Fig. 2 is a block diagram of an exemplar computer system 200 for carrying out the autodetect technique according to one embodiment of the invention.
- Computer system 200 may be employed to implement either a client or a server of a computer network.
- the computer system 200 includes a digital computer 202, a display screen (or monitor) 204, a printer 206, a floppy disk drive 208, a hard disk drive 210, a network interface 212, and a keyboard 214.
- the digital computer 202 includes a microprocessor 216, a memory bus 218, random access memory (RAM) 220, read only memory (ROM) 222, a peripheral bus 224, and a keyboard controller 226.
- RAM random access memory
- ROM read only memory
- peripheral bus 224 a peripheral bus 224
- the digital computer 200 can be a personal computer (such as an Apple computer, e.g., an Apple Macintosh, an IBM personal computer, or one of the compatibles thereof), a workstation computer (such as a Sun Microsystems or Hewlett-Packard workstation), or some other type of computer.
- a personal computer such as an Apple computer, e.g., an Apple Macintosh, an IBM personal computer, or one of the compatibles thereof
- a workstation computer such as a Sun Microsystems or Hewlett-Packard workstation
- some other type of computer such as an Apple computer, e.g., an Apple Macintosh, an IBM personal computer, or one of the compatibles thereof.
- the microprocessor 216 is a general purpose digital processor which controls the operation of the computer system 200.
- the microprocessor 216 can be a single-chip processor or can be implemented with multiple components. Using instructions retrieved from memory, the microprocessor 216 controls the reception and manipulation of input data and the output and display of data on output devices.
- the memory bus 218 is used by the microprocessor 216 to access the RAM 220 and the ROM 222.
- the RAM 220 is used by the microprocessor 216 as a general storage area and as scratch-pad memory, and can also be used to store input data and processed data.
- the ROM 222 can be used to store instructions or program code followed by the microprocessor 216 as well as other data.
- the peripheral bus 224 is used to access the input, output, and storage devices used by the digital computer 202.
- these devices include the display screen 204, the printer device 206, the floppy disk drive 208, the hard disk drive 210, and the network interface 212, which is employed to connect computer 200 to the network.
- the keyboard controller 226 is used to receive input from keyboard 214 and send decoded symbols for each pressed key to microprocessor 216 over bus 228.
- the display screen 204 is an output device that displays images of data provided by the microprocessor 216 via the peripheral bus 224 or provided by other components in the computer system 200.
- the printer device 206 when operating as a printer provides an image on a sheet of paper or a similar surface. Other output devices such as a plotter, typesetter, etc. can be used in place of, or in addition to, the printer device 206.
- the floppy disk drive 208 and the hard disk drive 210 can be used to store various types of data.
- the floppy disk drive 208 facilitates transporting such data to other computer systems, and hard disk drive 210 permits fast access to large amounts of stored data.
- the microprocessor 216 together with an operating system operate to execute computer code and produce and use data.
- the computer code and data may reside on the RAM 220, the ROM 222, the hard disk drive 220, or even on another computer on the network.
- the computer code and data could also reside on a removable program medium and loaded or installed onto the computer system 200 when needed.
- Removable program mediums include, for example. CD-ROM, PC-CARD, floppy disk and magnetic tape.
- the network interface circuit 212 is used to send and receive data over a network connected to other computer systems.
- An interface card or similar device and appropriate software implemented by the microprocessor 216 can be used to connect the computer system 200 to an existing network and transfer data according to standard protocols.
- the keyboard 214 is used by a user to input commands and other instructions to the computer system 200.
- Other types of user input devices can also be used in conjunction with the present invention.
- pointing devices such as a computer mouse, a track ball, a stylus, or a tablet can be used to manipulate a pointer on a screen of a general -purpose computer.
- the invention can also be embodied as computer-readable code on a computer-readable medium.
- the computer-readable medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of the computer-readable medium include read-only memory, random- access memory, CD-ROMs, magnetic tape, optical data storage devices.
- the computer-readable code can also be distributed over a network coupled computer system so that the computer-readable code is stored and executed in a distributed fashion.
- Figs. 3-6 illustrate, to facilitate discussion, some possible arrangements for the transmission and receipt of data in a computer network. The arrangements differ depending on which protocol is employed and the configuration of the network itself.
- Fig. 3 illustrates, in accordance with one embodiment, the control and data connections between a client application 300 and server 302 when no firewall is provided in the network.
- Client application 300 may represent, for example, the executable codes for executing a real-time data rendering program such as the Web Theater Client 2.0, available from VXtreme, Inc. of Sunnyvale, California.
- client application 300 includes the inventive autodetect mechanism and may represent a plug-in software module that may be installed onto a browser 306.
- Browser 306 may represent, for example, the application program which the user of the client computer employs to navigate the network.
- browser 306 may represent one of the popular Internet browser programs, such as NetscapeTM by Netscape Communications Inc. of Mountain View, California or Microsoft Explorer by Microsoft Corporation of Redmond, Washington.
- client application 300 When the autodetect mechanism of client application 300 is executed in browser 306 (e.g., during the set up of client application 300), client application 300 sends a control request over control connection 308 to server 302.
- server 302. Although multiple control requests are typically sent in parallel over multiple control connections using different protocols as discussed earlier, only one control request is depicted in Fig. 3 to facilitate ease of illustration.
- the protocol employed to send the control request over control connection 308 may represent, for example, TCP, or HTTP. If UDP protocol is requested from the server, the request from the client may be sent via the control connection using for example the TCP protocol.
- each control request from client application 300 may include, for example, the server name that identifies server 302, the port through which control connection may be established, and the name of the video stream requested by client application 300.
- Server 302 then responds with data via data connection 310.
- data connection 310 it is assumed that no proxies and/or firewalls exist. Accordingly, server 302 responds using the same protocol as that employed in the request. If the request employs TCP, however, server 302 may attempt to respond using either UDP or TCP data connections (depending on the specifics of the request). The response is sent to client application via data connection 310.
- control connection 308 may include, for example, stop, play, fast forward, rewind, pause, unpause, and the like. These control requests may be utilized by server 302 to control the delivery of the data stream from server 302 to client application 300 via data connection 310.
- Fig. 3 illustrates another network arrangement wherein control and data connections are established through a firewall.
- a firewall may have policies that restrict or prohibit the traversal of certain types of data and/or protocols.
- a firewall 400 is disposed between client application 300 and server 402. Upon execution, client application 300 sends control request using a given protocol via firewall 400 to server 402. Server 402 then responds with data via data connection 410, again via firewall 400.
- client application 300 may then receive data from server 402 (through data connection 408) in the same protocol used in the request.
- server 402 may respond with data connections for either TCP or UDP protocol (depending on the specifics of the request). Protocols that may traverse a firewall may include one or more of the following: UDP, TCP, and HTTP.
- the HTTP protocol may be employed to send/receive media data (video, audio, annotation, or the like) between the client and the server.
- Fig. 5 A is a prior art drawing illustrating how a client browser may communicate with a web server using a port designated for communication.
- Web server 550 representing the software module for serving web pages to a browser application 552.
- Web server 550 may be any of the commercially available web servers that are available from, for example, Netscape Communications Inc. of Mountain View, California or Microsoft Corporation of Redmond, Washington.
- Browser application 552 represents for example the Netscape browser from the aforementioned Netscape Communications, Inc., or similarly suitable browser applications.
- HTTP port 554 may represent any port through which HTTP communication is enabled.
- HTTP port 554 may also represent the default port for communicating web pages with client browsers.
- the HTTP default port may represent, for example, either port 80 or port 8080 on web server 550.
- one or both of these ports on web server 550 may be available for web page communication even if there are firewalls disposed between the web server 550 and client browser application 552, which otherwise block all HTTP traffic in other ports.
- web server 550 may then obtain the desired web page(s) for sending to client browser application 552 via data connection 556.
- the invention in one embodiment, involves employing the HTTP protocol to communicate media commands from a browser application or browser plug-in to the server.
- Media commands are, for example, PLAY, STOP, REWIND, FAST FORWARD, and PAUSE.
- the server computer may represent, for example, a web server.
- the server computer may also represent a video server for streaming video to the client computer.
- the client computer may successfully send media control requests and receive media data through any HTTP port. If the default HTTP port, e.g., port 80 or 8080, is specified, the client may successfully send media control requests and receive media data even if there exists a firewall or an HTTP Proxy disposed in between the server computer and the client computer, which otherwise blocks all other traffic that does not use the HTTP protocol. For example, these firewalls or HTTP Proxies do not allow regular TCP or UDP packets to go through.
- the HTTP protocol typically defines only three types of requests to be sent from the client computer to the server, namely GET, POST, and HEAD.
- the POST command for instance, is specified in RFC 1945 to be composed of a Request-Line, one or more Headers and Entity-Body.
- the invention in one embodiment sends the media command as part of the Entity-Body of the HTTP POST command.
- the media command can be in any format or protocol, and can be, for instance, in the same format as that employed when firewalls are not a concern and plain TCP protocol can be used. This format can be, for example, RTSP (Real Time Streaming Protocol).
- a server When a server gets an HTTP request, it answers the client with an HTTP Response. Responses are typically composed of a Status-Line, one or more headers, and an Entity-Body. In one embodiment of this invention, the response to the media commands is sent as the Entity-Body of the response to the original HTTP request that carried the media command.
- Fig. 5B illustrates this use of HTTP for sending arbitrary media commands.
- the plug-in application 560 within client browser application 562 may attempt to receive media data (e.g., video, audio, annotation, or the like) by first sending an HTTP request to server 564 via control connection 565.
- media data e.g., video, audio, annotation, or the like
- a REWIND command could be sent from the client 560 to the server 564 as an HTTP packet 570 of the form: "POST/HTTP/ 1.0 ⁇ Entity-Body containing rewind command in any suitable media protocol>”.
- the server can answer to this request with an HTTP response 572 of the form: "HTTP/1.0 200ok ⁇ Entity-Body containing rewind response in any suitable media protocol>".
- the HTTP protocol can be also used to send media data across firewalls.
- the client can send a GET request to the video server, and the video server can then send the video data as the Entity-Body of the HTTP response to this GET request.
- firewalls may be restrictive with respect to HTTP data and may permit HTTP packets to traverse only on a certain port, e.g., port 80 and/or port 8080.
- Fig. 5C illustrates one such situation.
- the control and data communications for the various data stream e.g., audio, video, and/or annotation associated with different rendering sessions (and different clients) may be multiplexed using conventional multiplexer code and/or circuit 506 at client application 300 prior to being sent via port 502 (which may represent, for example, HTTP port 80 or HTTP port 8080).
- the inventive combined use of the HTTP protocol and of the multiplexer for transmitting media control and data is referred to as the HTTP multiplex protocol, and can be used to send this data across firewalls that only allow HTTP traffic on specific ports, e.g., port 80 or 8080.
- conventional demultiplexer code and/or circuit 508 may be employed to decode the received data packets to identify which stream the control request is associated with.
- data sent from server 402 to client application 300 may be multiplexed in advance at server 402 using for example conventional multiplexer code and/or circuit 510.
- the multiplexed data is then sent via port 502.
- the multiplexed data may be decoded via conventional demultiplexer code and/or circuit 512 to identify which stream the received data packets is associated with (audio, video, or annotation).
- Multiplexing and demultiplexing at the client and/or server may be facilitated for example by the use of the Request-URL part of the Request-Line of HTTP requests.
- the Request-URL may, for example, identify the stream associated with the data and/or control request being transmitted.
- the additional information in the Request-URL in the HTTP header may be as small as one or a few bits added to the HTTP request sent from client application 300 to server 402.
- the plug-in application 660 within client plug-in application 660 may attempt to receive media data (e.g., video, audio, annotation, or the like) by first sending a control request 670 to server 664 via control connection 665.
- the control request is an HTTP request, which arrives at the HTTP default port 654 on server 664.
- the default HTTP port may be either port 80 or port 8080 in one embodiment.
- control request 670 from client plug-in 660 takes the form of a command to "POST/12469 HTTP/1.0 ⁇ Entity-Body>" which indicates to the server (through the designation 12469 as the Request-URL) that this is a control connection.
- the Entity-Body contains, as described above, binary data that informs the video server that the client plug-in 660 wants to display a certain video or audio clip.
- Software codes within server 664 may be employed to assign a unique ID to this particular request from this particular client.
- server 664 associates unique ID 35,122 with a video data connection between itself and client plug-in application 660, and unique ID 29,999 with an audio data connection between itself and client plug-in application.
- the unique ID is then communicated as message 672 from server 664 to client plug-in application 660, again through the aforementioned HTTP default port using data connection 667.
- the Entity-Body of message 672 contains, among other things and as depicted in detail 673, the audio and/or video session ID.
- the unique ID is unique to each data connection (e.g., each of the audio, video, and annotation connections) of each client plug-in application (since there may be multiple client plug-in applications attempting to communicate through the same port).
- client plug-in application 660 may issue a command "GET/35, 122 HTTP/1.0" or "POST/35,122 HTTP/1.0 ⁇ Entity-Body containing binary data with the REWIND media command>" to request a video file or to rewind on the video file.
- rewind command is used in Figs. 5A-5D to facilitate ease of discussion, other media commands, e.g., fast forward, pause, real-time play, live-play, or the like, may of course be sent in the Entity-Body.
- the unique ID is employed in place of or in addition to the Request-URL to qualify the Request-URL.
- the server may be employed by the server to demultiplex the command to associate the command with a particular client and data file.
- This unique ID number can also attach to the HTTP header of HTTP responses set from server 664 to client plug-in application 660, through the same HTTP default port 654 on server 664, to permit client plug-in application 660 to ascertain whether an HTTP data packet is associated with a given data stream.
- the invention permits media control commands and media data to be communicated between the client computer and the server computer via the default HTTP port, e.g., port 80 or 8080 in one embodiment, even if HTTP packets are otherwise blocked by a firewall disposed between the client computer and the server computer.
- each control connection and data connection to each client with a unique ID advantageously permits multiple control an data connections (from one or more clients) to be established through the same default HTTP port on the server, advantageously bypassing the firewall. Since both the server and the client have the demultiplexer code and/or circuit that resolve a particular unique ID into a particular data stream, multiplexed data communication is advantageously facilitated thereby.
- Fig. 6 illustrates this situation wherein client application 300 employs proxy 602 to communicate with server 402.
- the use of proxy 602 may be necessary since client application 300 may employ a protocol which is strictly prohibited by firewall 604.
- the identity of proxy 602 may be found in browser program 306, e.g., Netscape as it employs the proxy to download its web pages, or may be configured by the user himself.
- Typical protocols that may employ a proxy for communication, e.g., proxy 602 includes HTTP and UDP.
- the multiple protocols that may be employed for communication between a server computer and a client computer are tried in parallel during autodetect.
- the connections depicted in Figs. 3, 4, 5C and 6 may be attempted simultaneously and in parallel over different control connections by the client computer.
- the server is requested to respond with various protocols. If the predefined "best" protocol (predetermined in accordance with some predefined protocol priority) is received by the client application from the server, autodetect may, in one embodiment, end immediately and the "best" protocol is selected for immediate communication.
- UDP is considered the "best” protocol, and the receipt of UDP data by the client may trigger the termination of the autodetect.
- Fig. 7 depicts, in accordance with one embodiment of the present invention, a simplified flowchart illustrating the steps of the inventive autodetect technique.
- the client application starts (in step 702) by looking up the HTTP proxy, if there is any, from the browser.
- the client computer may have received a web page from the browser, which implies that the HTTP protocol may have been employed by the browser program for communication.
- HTTP proxy the name and location of the HTTP proxy is likely known to the browser, and this knowledge may be subsequently employed by the client to at least enable communication with the server using the HTTP proxy protocol, i.e., if a more advantageous protocol cannot be ascertained after autodetect.
- step 704 the client begins the autodetect sequence by starting in parallel the control thread 794, along with five protocol threads 790, 792, 796, 798, and 788.
- parallel refers to both the situation wherein the multiple protocol threads are sent parallely starting at substantially the same time (having substantially similar starting time), and the situation wherein the multiple protocol threads simultaneously execute (executing at the same time), irrespective when each protocol thread is initiated. In the latter case, the multiple threads may have, for example, staggered start time and the initiation of one thread may not depend on the termination of another thread.
- Control thread 794 represents the thread for selecting the most advantageous protocol for communication. The other protocol threads 790.
- 792, 796, 798, and 788 represent threads for initiating in parallel communication using the various protocols, e.g., UDP, TCP, HTTP proxy, HTTP through port 80 (HTTP 80), and HTTP through port 8080 (HTTP 8080). Although only five protocol threads are shown, any number of protocol threads may be initiated by the client, using any conventional and/or suitable protocols. The steps associated with each of threads 794, 790, 792, 796, 798, and 788 are discussed herein in connection with Figs. 8A-8E and 9.
- the UDP protocol thread is executed.
- the client inquires in step 716 whether a UDP proxy is required. If the UDP proxy is required, the user may obtain the name of the UDP proxy from, for example, the system administrator in order to use the UDP proxy to facilitate communication to the proxy (in step 718). If no UDP proxy is required, the client may directly connect to the server (in step 720). Thereafter, the client may begin sending a data request (i.e., a control request) to the server in step 722 using the UDP protocol (either through the proxy if a proxy is involved or directly to the server if no proxy is required).
- a data request i.e., a control request
- the TCP protocol thread is executed. If TCP protocol is employed, the client typically directly connects to the server (in step 726). Thereafter, the client may begin sending a data request (i.e., a control request) to the server using the TCP protocol (step 724).
- a data request i.e., a control request
- the HTTP protocol thread is executed.
- the client inquires in step 716 whether an HTTP proxy is required. If the HTTP proxy is required, the user may obtain the name of the HTTP proxy from, for example, the browser since, as discussed earlier, the data pertaining to the proxy may be kept by the browser. Alternatively, the user may obtain data pertaining to the HTTP proxy from the system administrator in order to use the HTTP proxy to facilitate communication to the server (in step 732).
- the client may directly connect to the server (in step 730). Thereafter, the client may begin sending a data request (i.e., a control request) to the server in step 734 using the HTTP protocol (either through the proxy if a proxy is involved or directly to the server if no proxy is required).
- a data request i.e., a control request
- the HTTP 80 protocol thread is executed. If HTTP 80 protocol is employed, HTTP data may be exchanged but only through port 80, which may be for example the port on the client computer through which communication with the network is permitted. Through port 80, the client typically directly connects to the server (in step 736). Thereafter, the client may begin sending a data request (i.e., a control request) to the server (step 738) using the HTTP 80 protocol.
- the HTTP 8080 protocol thread is executed. If HTTP 8080 protocol is employed, HTTP data may be exchanged but only through port 8080, which may be the port on the client computer for communicating with the network. Through port 8080, the client typically directly connects to the server (in step 740).
- the client may begin sending a data request (i.e., a control request) to the server (step 742) using the HTTP 8080 protocol.
- a data request i.e., a control request
- the server may begin sending a data request (i.e., a control request) to the server (step 742) using the HTTP 8080 protocol.
- the multiplexing and demultiplexing techniques that may be employed for communication through port 8080, as well as port 80 of Fig. 8D, have been discussed earlier and are not repeated here for brevity sake.
- Fig. 9 illustrates, in accordance with one embodiment of the present invention, control thread 794 of Fig. 7. It should be emphasized that Fig. 7 is but one way of implementing the control thread; other techniques of implementing the control thread to facilitate autodetect should be apparent to those skilled in the art in view of this disclosure.
- the thread determines whether the predefined timeout period has expired.
- the predefined timeout period may be any predefined duration (such as 7 seconds for example) from the time the data request is sent out to the server (e.g., step 722 of Fig. 8 A).
- each protocol thread has its own timeout period whose expiration occurs at the expiration of a predefined duration after the data request using that protocol has been sent out.
- the thread moves to step 754 wherein the most advantageous protocol among the set of protocols received back from the server is selected for communication.
- the selection of the most advantageous protocol may be performed in accordance with some predefined priority scheme, and data regarding the selected protocol may be saved for future communication sessions between this server and this client.
- step 748 the thread proceeds to step 748 to wait for either data from the server or the expiration of the timeout period. If timeout occurs, the thread moves to step 754, which has been discussed earlier. If data is received from the server, the thread moves to step 750 to ascertain whether the protocol associated with the data received from the server is the predefined "best" protocol, e.g., in accordance with the predefined priority.
- the thread preferably moves to step 754 to terminate the autodetect and to immediately begin using this protocol for data communication instead of waiting for the timeout expiration.
- the duration of the autodetect sequence may be substantially shorter than the predefined timeout period. In this manner, rapid autodetect of the most suitable protocol and rapid establishment of communication are advantageously facilitated.
- step 750 the thread proceeds to step 752 to add the received protocol to the received set.
- This received protocol set represents the set of protocols from which the "most advantageous" (relatively speaking) protocol is selected.
- the most advantageous protocol is ascertained relative to other protocols in the received protocol set irrespective whether it is the predefined "best" protocol in accordance with the predefined priority.
- UDP may be deemed to be best (i.e., the predefined best), followed by TCP, HTTP, then HTTP 80 and HTTP 8080 (the last two may be equal in priority).
- the most advantageous protocol is selected from the received protocol set preferably upon the expiration of the predefined timeout period. From step 752, the thread returns to step 746 to test whether the timeout period has expired. If not, the thread continues along the steps discussed earlier.
- the time lag between the time the autodetect mechanism begins to execute and the time when the most advantageous protocol is determined is minimal. If communication attempts have been tried in serial, for example, the user would suffer the delay associated with each protocol thread in series, thereby disadvantageously lengthening the time period between communication attempt and successful establishment of communication.
- the saving in time is even more dramatic in the event the network is congested or damaged.
- it may take anywhere from 30 to 90 seconds before the client application realizes that an attempt to connect to the server (e.g., step 720, 726, 730, 736, or 740) has failed.
- the delay may, in some cases, reach minutes before the user realizes that the network is unusable and attempts should be made at a later time.
- the user does not have to wait for multiple attempts and failures before being able to ascertain that the network is unusable and an attempt to establish communication should be made at a later time.
- the user is advised to try again as soon as it is realized that parallel attempts to connect with the server have all failed. In this manner, less of the user's time is needed to establish optimal communication with a network.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP98903846A EP0956686B1 (en) | 1997-01-30 | 1998-01-30 | Automatic detection of protocols in a network |
JP53309698A JP3498746B2 (en) | 1997-01-30 | 1998-01-30 | Automatic detection of protocols in the network |
DE69829361T DE69829361T2 (en) | 1997-01-30 | 1998-01-30 | AUTOMATIC RECOGNITION OF LOGS IN A NETWORK |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US3666297P | 1997-01-30 | 1997-01-30 | |
US3666197P | 1997-01-30 | 1997-01-30 | |
US60/036,661 | 1997-01-30 | ||
US60/036,662 | 1997-01-30 | ||
US08/818,769 US5999979A (en) | 1997-01-30 | 1997-03-14 | Method and apparatus for determining a most advantageous protocol for use in a computer network |
US08/818,769 | 1997-03-14 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1998034385A1 true WO1998034385A1 (en) | 1998-08-06 |
Family
ID=27365074
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1998/001797 WO1998034385A1 (en) | 1997-01-30 | 1998-01-30 | Automatic detection of protocols in a network |
Country Status (5)
Country | Link |
---|---|
US (1) | US5999979A (en) |
EP (1) | EP0956686B1 (en) |
JP (1) | JP3498746B2 (en) |
DE (1) | DE69829361T2 (en) |
WO (1) | WO1998034385A1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2000016520A2 (en) * | 1998-09-11 | 2000-03-23 | Teledesic Llc | Method of data transmission in a data communication network |
WO2002056175A2 (en) * | 2001-01-11 | 2002-07-18 | Embrace Networks, Inc. | Method and apparatus for firewall traversal |
WO2005111837A1 (en) | 2004-05-03 | 2005-11-24 | Microsoft Corporation | Fast startup for streaming media |
US7315537B2 (en) | 2001-09-25 | 2008-01-01 | Siemens Aktiengesellschaft | Method for the transmission of data in a packet-oriented data network |
EP2214346A1 (en) * | 2009-02-03 | 2010-08-04 | Brother Kogyo Kabushiki Kaisha | Management device, managing method and computer program |
Families Citing this family (110)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6128653A (en) * | 1997-03-17 | 2000-10-03 | Microsoft Corporation | Method and apparatus for communication media commands and media data using the HTTP protocol |
US6396805B2 (en) * | 1997-03-25 | 2002-05-28 | Intel Corporation | System for recovering from disruption of a data transfer |
US6311215B1 (en) * | 1997-03-25 | 2001-10-30 | Intel Corporation | System for dynamic determination of client communications capabilities |
US6128668A (en) * | 1997-11-07 | 2000-10-03 | International Business Machines Corporation | Selective transformation of multimedia objects |
US6175860B1 (en) * | 1997-11-26 | 2001-01-16 | International Business Machines Corporation | Method and apparatus for an automatic multi-rate wireless/wired computer network |
US6446225B1 (en) | 1998-04-23 | 2002-09-03 | Microsoft Corporation | Server system with scalable session timeout mechanism |
AU3728499A (en) * | 1998-04-27 | 1999-11-16 | Digital Electronics Corporation | Control system, display, host computer for control, and data transmitting method |
US6687753B2 (en) * | 1998-06-25 | 2004-02-03 | International Business Machines Corporation | Method and system for providing three-dimensional graphics over computer networks |
US6233688B1 (en) * | 1998-06-30 | 2001-05-15 | Sun Microsystems, Inc. | Remote access firewall traversal URL |
JP3042504B2 (en) * | 1998-07-03 | 2000-05-15 | 富士通株式会社 | Recording medium storing communication control program, communication control method, and communication control device |
US6202081B1 (en) * | 1998-07-21 | 2001-03-13 | 3Com Corporation | Method and protocol for synchronized transfer-window based firewall traversal |
PT1003313E (en) * | 1998-09-11 | 2005-04-29 | Two Way Media Ltd | SUPPLY OF INTERACTIVE APPLICATIONS |
US6622171B2 (en) * | 1998-09-15 | 2003-09-16 | Microsoft Corporation | Multimedia timeline modification in networked client/server systems |
US6415326B1 (en) | 1998-09-15 | 2002-07-02 | Microsoft Corporation | Timeline correlation between multiple timeline-altered media streams |
US6490615B1 (en) * | 1998-11-20 | 2002-12-03 | International Business Machines Corporation | Scalable cache |
JP3472498B2 (en) * | 1999-01-27 | 2003-12-02 | シャープ株式会社 | Data transfer device, data transfer method, and medium recording data transfer program |
US6434617B1 (en) * | 1999-02-22 | 2002-08-13 | Hewlett-Packard Co. | Extensible, object-oriented network interface |
US7293280B1 (en) | 1999-07-08 | 2007-11-06 | Microsoft Corporation | Skimming continuous multimedia content |
US7313808B1 (en) | 1999-07-08 | 2007-12-25 | Microsoft Corporation | Browsing continuous multimedia content |
US6807648B1 (en) * | 1999-09-13 | 2004-10-19 | Verizon Laboratories Inc. | Variable-strength error correction in ad-hoc networks |
US6658476B1 (en) * | 1999-11-29 | 2003-12-02 | Microsoft Corporation | Client-server protocol support list for standard request-response protocols |
US7149359B1 (en) | 1999-12-16 | 2006-12-12 | Microsoft Corporation | Searching and recording media streams |
US6928655B1 (en) | 1999-12-16 | 2005-08-09 | Microsoft Corporation | Live presentation searching |
US6868440B1 (en) | 2000-02-04 | 2005-03-15 | Microsoft Corporation | Multi-level skimming of multimedia content using playlists |
US20070214262A1 (en) * | 2000-02-25 | 2007-09-13 | Anywheremobile, Inc. | Personal server technology with firewall detection and penetration |
US20020078198A1 (en) * | 2000-02-25 | 2002-06-20 | Buchbinder John E. | Personal server technology with firewall detection and penetration |
EP1269754A4 (en) | 2000-03-14 | 2009-03-11 | Joseph Robert Marchese | Digital video system using networked cameras |
US7237254B1 (en) | 2000-03-29 | 2007-06-26 | Microsoft Corporation | Seamless switching between different playback speeds of time-scale modified data streams |
US6985966B1 (en) | 2000-03-29 | 2006-01-10 | Microsoft Corporation | Resynchronizing globally unsynchronized multimedia streams |
US7814208B2 (en) * | 2000-04-11 | 2010-10-12 | Science Applications International Corporation | System and method for projecting content beyond firewalls |
AU2001251748A1 (en) * | 2000-04-14 | 2001-10-30 | Solidstreaming, Inc. | A system and method for multimedia streaming |
EP1150472B1 (en) * | 2000-04-27 | 2004-10-06 | Hewlett-Packard Company | Method and system for installing available network protocols |
US6601094B1 (en) * | 2000-04-27 | 2003-07-29 | Hewlett-Packard Development Company, L.P. | Method and system for recommending an available network protocol |
US7302490B1 (en) | 2000-05-03 | 2007-11-27 | Microsoft Corporation | Media file format to support switching between multiple timeline-altered media streams |
US6772216B1 (en) | 2000-05-19 | 2004-08-03 | Sun Microsystems, Inc. | Interaction protocol for managing cross company processes among network-distributed applications |
US20020116205A1 (en) * | 2000-05-19 | 2002-08-22 | Ankireddipally Lakshmi Narasimha | Distributed transaction processing system |
EP1161048A3 (en) * | 2000-05-19 | 2005-02-16 | Attachmate Corporation | System and method for secure duplex browser communication over disparate networks |
US6971096B1 (en) | 2000-05-19 | 2005-11-29 | Sun Microsystems, Inc. | Transaction data structure for process communications among network-distributed applications |
KR100434459B1 (en) * | 2000-06-27 | 2004-06-05 | 삼성전자주식회사 | Method and apparatus for controlling transmission of data packet in mobile telecommunication system |
US7441270B1 (en) * | 2000-07-06 | 2008-10-21 | Intel Corporation | Connectivity in the presence of barriers |
AU2001280072A1 (en) * | 2000-08-15 | 2002-02-25 | Polycom Israel Ltd. | A multimedia communication control unit as a secure device for multimedia communication between lan users and other network users |
US7392301B1 (en) * | 2000-11-14 | 2008-06-24 | Siemens Subscriber Networks, Inc. | Method and apparatus for automated assistance in configuring customer premises equipment |
US7155487B2 (en) * | 2000-11-30 | 2006-12-26 | Intel Corporation | Method, system and article of manufacture for data distribution over a network |
KR100501080B1 (en) * | 2000-12-19 | 2005-07-18 | 노병희 | A method and system for distinguishing higher layer protocols of the internet traffic |
US7305697B2 (en) * | 2001-02-02 | 2007-12-04 | Opentv, Inc. | Service gateway for interactive television |
FI114265B (en) * | 2001-03-26 | 2004-09-15 | First Hop Oy | Methods and arrangements for realizing effective data transmission over a speed-limited communication link |
WO2002080457A1 (en) * | 2001-03-29 | 2002-10-10 | Sphere Software Corporation | Layering enterprise application services using semantic firewalls |
US20020144276A1 (en) * | 2001-03-30 | 2002-10-03 | Jim Radford | Method for streamed data delivery over a communications network |
KR100757466B1 (en) * | 2001-04-17 | 2007-09-11 | 삼성전자주식회사 | System for providing service with device in home network and method thereof and System for receiving service in homenetwork and method thereof |
JP3491626B2 (en) * | 2001-05-29 | 2004-01-26 | ソニー株式会社 | Transmission device, reception device, and transmission / reception device |
US6941356B2 (en) * | 2001-06-29 | 2005-09-06 | International Business Machines Corporation | Automated configuration enabled via interrogation over network |
FI110900B (en) * | 2001-07-11 | 2003-04-15 | Nokia Corp | Protocol-based end-users |
US7369537B1 (en) | 2001-07-18 | 2008-05-06 | Global Ip Solutions, Inc. | Adaptive Voice-over-Internet-Protocol (VoIP) testing and selecting transport including 3-way proxy, client-to-client, UDP, TCP, SSL, and recipient-connect methods |
US20030023731A1 (en) * | 2001-07-24 | 2003-01-30 | Adtran, Inc. | Mechanism for automatically determining signaling role and associated protocol of frame relay communication device |
US8650321B2 (en) * | 2001-07-24 | 2014-02-11 | Digi International Inc. | Network architecture |
JP4224958B2 (en) * | 2001-08-10 | 2009-02-18 | 富士ゼロックス株式会社 | Internet printing method, system thereof, proxy device, and print server |
US20030154244A1 (en) * | 2002-02-13 | 2003-08-14 | Zellers Mark H. | Method and system to provide flexible HTTP tunnelling |
JP4126928B2 (en) * | 2002-02-28 | 2008-07-30 | 日本電気株式会社 | Proxy server and proxy control program |
AU2003226128A1 (en) * | 2002-03-27 | 2003-10-13 | First Virtual Communications | System and method for traversing firewalls with protocol communications |
US7644172B2 (en) * | 2002-06-24 | 2010-01-05 | Microsoft Corporation | Communicating via a connection between a streaming server and a client without breaking the connection |
US7120858B2 (en) * | 2002-08-21 | 2006-10-10 | Sun Microsystems, Inc. | Method and device for off-loading message digest calculations |
US7277915B2 (en) * | 2002-11-11 | 2007-10-02 | Openwave Systems Inc. | Application-based protocol and proxy selection by a mobile device in a multi-protocol network environment |
US7191356B2 (en) * | 2003-02-27 | 2007-03-13 | Sun Microsystems, Inc. | Method for asynchronous support of fault-tolerant and adaptive communication |
US7178051B2 (en) * | 2003-02-27 | 2007-02-13 | Sun Microsystems, Inc. | Method for synchronous support of fault-tolerant and adaptive communication |
JP4374202B2 (en) * | 2003-02-28 | 2009-12-02 | 株式会社日立製作所 | Stream distribution computer, program, NAS device |
US7409454B2 (en) * | 2003-06-02 | 2008-08-05 | Microsoft Corporation | Automatic detection of intermediate network device capabilities |
US20050013589A1 (en) * | 2003-07-14 | 2005-01-20 | Microsoft Corporation | Adding recording functionality to a media player |
US7685603B2 (en) * | 2003-09-08 | 2010-03-23 | Sap Ag | Selecting client adapters |
US7486698B2 (en) * | 2003-12-19 | 2009-02-03 | Solace Systems, Inc. | Multiplexing of control and data over an HTTP connection |
US20050283535A1 (en) * | 2004-06-17 | 2005-12-22 | Michele Covell | Method and system for interactive control of media over a network |
US8689313B2 (en) * | 2004-06-21 | 2014-04-01 | Insors Integrated Communications | Real time streaming data communications through a security device |
US7826401B2 (en) * | 2004-06-21 | 2010-11-02 | Insors Integrated Communications | Methods and program products for mapping a network address translator |
JP2006019934A (en) * | 2004-06-30 | 2006-01-19 | Kddi Corp | Method for setting call of packet switched network |
US7526557B2 (en) * | 2004-06-30 | 2009-04-28 | Signiant, Inc. | System and method for transferring data in high latency firewalled networks |
US20060106929A1 (en) * | 2004-10-15 | 2006-05-18 | Kenoyer Michael L | Network conference communications |
JPWO2006085500A1 (en) * | 2005-02-09 | 2008-06-26 | 松下電器産業株式会社 | Surveillance camera device, surveillance system using the same, and surveillance image transmission method |
US20060179134A1 (en) * | 2005-02-09 | 2006-08-10 | Enure Networks Ltd. | Device, method, and system for module level network supervision |
TW200532544A (en) * | 2005-03-09 | 2005-10-01 | Tul Corp | Personal multimedia on-line broadcasting system and method thereof |
KR20070116893A (en) | 2005-03-30 | 2007-12-11 | 웰치알린인코포레이티드 | Communication of information between a plurality of network elements |
US20060235939A1 (en) * | 2005-04-18 | 2006-10-19 | Wai Yim | Apparatus and methods for tunneling a media streaming application through a firewall |
US8190773B2 (en) * | 2005-06-03 | 2012-05-29 | Nokia Corporation | System and method for accessing a web server on a device with a dynamic IP-address residing behind a firewall |
US8010850B2 (en) | 2005-08-31 | 2011-08-30 | Microsoft Corporation | Client extended error handling |
US7600030B2 (en) * | 2005-08-31 | 2009-10-06 | Microsoft Corporation | Compounding of HTTP authoring protocol |
US20070220587A1 (en) * | 2006-03-15 | 2007-09-20 | Loyer Douglas E | Systems, Methods, and Apparatus for Most Advantageous Media Delivery for Rich Media Applications |
US8024421B2 (en) | 2006-03-30 | 2011-09-20 | Welch Allyn, Inc. | Device data sheets and data dictionaries for a dynamic medical object information base |
US9166883B2 (en) * | 2006-04-05 | 2015-10-20 | Joseph Robert Marchese | Network device detection, identification, and management |
US20070288604A1 (en) * | 2006-06-08 | 2007-12-13 | Jeffrey Mark Achtermann | Method for determining optimal number of connections in multi-connection download configuration |
US9516128B2 (en) * | 2007-12-13 | 2016-12-06 | International Business Machines Corporation | Generic remote connection to a command line interface application |
US20090216880A1 (en) * | 2008-02-26 | 2009-08-27 | Viasat, Inc. | Methods and Systems for Dynamic Transport Selection Based on Last Mile Network Detection |
GB2463329B (en) * | 2008-09-10 | 2013-02-20 | Echostar Advanced Technologies L L C | Set-top box emulation system |
US8762460B2 (en) * | 2009-07-13 | 2014-06-24 | Qualcomm Incorporated | Group communication sessions between session participants communicating via two or more different contact protocols within a wireless communications system |
US8214566B2 (en) | 2009-07-24 | 2012-07-03 | Welch Allyn, Inc. | Configurable health-care equipment apparatus |
USD671222S1 (en) | 2010-07-22 | 2012-11-20 | Welch Allyn, Inc. | Module for a patient-monitor or the like |
USD632397S1 (en) | 2010-07-22 | 2011-02-08 | Welch Allyn, Inc. | Portions of a patient-monitor housing |
USD635681S1 (en) | 2010-07-22 | 2011-04-05 | Welch Allyn, Inc. | Patient-monitor housing |
JP2013118493A (en) * | 2011-12-02 | 2013-06-13 | Oki Electric Ind Co Ltd | Relay device, communication terminal and communication network |
US8930475B1 (en) | 2012-03-30 | 2015-01-06 | Signiant Inc. | Systems and methods for secure cloud-based media file sharing |
EP2878141A4 (en) * | 2012-05-10 | 2016-04-27 | Drawbridge Inc | System and method for determining related digital identities |
US9692799B2 (en) | 2012-07-30 | 2017-06-27 | Signiant Inc. | System and method for sending and/or receiving digital content based on a delivery specification |
WO2014035431A1 (en) * | 2012-08-31 | 2014-03-06 | Hewlett Packard Development Company, L.P. | Communication system |
CN103534984A (en) * | 2012-10-08 | 2014-01-22 | 华为终端有限公司 | Port setting method, apparatus and computer program product for routing |
US9781214B2 (en) * | 2013-04-08 | 2017-10-03 | Amazon Technologies, Inc. | Load-balanced, persistent connection techniques |
DE102015224886A1 (en) | 2015-12-10 | 2017-06-29 | Siemens Aktiengesellschaft | Avoiding weak spots |
KR102347069B1 (en) * | 2015-12-14 | 2022-01-04 | 삼성전자주식회사 | Electronic device and operating method for the same |
US10735516B1 (en) | 2019-02-15 | 2020-08-04 | Signiant Inc. | Cloud-based authority to enhance point-to-point data transfer with machine learning |
CN111565332A (en) * | 2020-04-27 | 2020-08-21 | 北京字节跳动网络技术有限公司 | Video transmission method, electronic device, and computer-readable medium |
US11902599B2 (en) * | 2020-12-09 | 2024-02-13 | Hulu, LLC | Multiple protocol prediction and in-session adaptation in video streaming |
EP4305779A1 (en) * | 2021-03-10 | 2024-01-17 | Telefonaktiebolaget LM Ericsson (publ) | Methods and apparatuses for establishing a transport protocol connection |
KR102613591B1 (en) * | 2022-10-19 | 2023-12-14 | 한국전자기술연구원 | Method and system for selecting the optimal synchronization broker for each workload |
US11848756B1 (en) | 2023-03-20 | 2023-12-19 | International Business Machines Corporation | Automatic detection of optimal networking stack and protocol |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0613274A2 (en) * | 1993-01-29 | 1994-08-31 | International Business Machines Corporation | Socket structure for concurrent multiple protocol access |
EP0751656A2 (en) * | 1995-06-27 | 1997-01-02 | Canon Kabushiki Kaisha | Protocol independent and adaptive network interface |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4931250A (en) * | 1988-05-12 | 1990-06-05 | Codex Corporation | Multimode modem |
JP2930257B2 (en) * | 1991-04-22 | 1999-08-03 | 株式会社東芝 | Portable electronic devices |
US5202899A (en) * | 1991-08-16 | 1993-04-13 | Rockwell International Corporation | Apparatus for providing dynamic selection of modem protocol to support multiple modem types |
EP0596648A1 (en) * | 1992-11-02 | 1994-05-11 | National Semiconductor Corporation | Network link endpoint capability detection |
US5557724A (en) * | 1993-10-12 | 1996-09-17 | Intel Corporation | User interface, method, and apparatus selecting and playing channels having video, audio, and/or text streams |
-
1997
- 1997-03-14 US US08/818,769 patent/US5999979A/en not_active Expired - Lifetime
-
1998
- 1998-01-30 EP EP98903846A patent/EP0956686B1/en not_active Expired - Lifetime
- 1998-01-30 DE DE69829361T patent/DE69829361T2/en not_active Expired - Lifetime
- 1998-01-30 JP JP53309698A patent/JP3498746B2/en not_active Expired - Fee Related
- 1998-01-30 WO PCT/US1998/001797 patent/WO1998034385A1/en active IP Right Grant
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0613274A2 (en) * | 1993-01-29 | 1994-08-31 | International Business Machines Corporation | Socket structure for concurrent multiple protocol access |
EP0751656A2 (en) * | 1995-06-27 | 1997-01-02 | Canon Kabushiki Kaisha | Protocol independent and adaptive network interface |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7817639B2 (en) | 1998-09-11 | 2010-10-19 | Noah Joseph Breslow | Method of data transmission in a data communication network |
WO2000016520A3 (en) * | 1998-09-11 | 2001-02-01 | Teledesic Llc | Method of data transmission in a data communication network |
US8644319B2 (en) | 1998-09-11 | 2014-02-04 | Wengen Wireless Llc | Method of data transmission in a data communication network |
US6493342B1 (en) | 1998-09-11 | 2002-12-10 | Teledesic Llc | Method of data transmission in a data communication network |
US8509139B2 (en) | 1998-09-11 | 2013-08-13 | Wengen Wireless Llc | Method of data transmission in a data communication network |
WO2000016520A2 (en) * | 1998-09-11 | 2000-03-23 | Teledesic Llc | Method of data transmission in a data communication network |
US7827601B2 (en) | 2001-01-11 | 2010-11-02 | Digi International Inc. | Method and apparatus for firewall traversal |
US7631349B2 (en) | 2001-01-11 | 2009-12-08 | Digi International Inc. | Method and apparatus for firewall traversal |
WO2002056175A3 (en) * | 2001-01-11 | 2003-01-23 | Embrace Networks Inc | Method and apparatus for firewall traversal |
WO2002056175A2 (en) * | 2001-01-11 | 2002-07-18 | Embrace Networks, Inc. | Method and apparatus for firewall traversal |
US7315537B2 (en) | 2001-09-25 | 2008-01-01 | Siemens Aktiengesellschaft | Method for the transmission of data in a packet-oriented data network |
CN100450118C (en) * | 2001-09-25 | 2009-01-07 | 西门子公司 | Method for the transmission of data in a packet-oriented data network |
EP1745387A1 (en) * | 2004-05-03 | 2007-01-24 | Microsoft Corporation | Fast startup for streaming media |
WO2005111837A1 (en) | 2004-05-03 | 2005-11-24 | Microsoft Corporation | Fast startup for streaming media |
EP1745387A4 (en) * | 2004-05-03 | 2011-04-06 | Microsoft Corp | Fast startup for streaming media |
EP2214346A1 (en) * | 2009-02-03 | 2010-08-04 | Brother Kogyo Kabushiki Kaisha | Management device, managing method and computer program |
US8499089B2 (en) | 2009-02-03 | 2013-07-30 | Brother Kogyo Kabushiki Kaisha | Management device, managing method and computer program |
Also Published As
Publication number | Publication date |
---|---|
DE69829361T2 (en) | 2006-04-13 |
JP3498746B2 (en) | 2004-02-16 |
JP2000509592A (en) | 2000-07-25 |
EP0956686A1 (en) | 1999-11-17 |
EP0956686B1 (en) | 2005-03-16 |
DE69829361D1 (en) | 2005-04-21 |
US5999979A (en) | 1999-12-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP0956686B1 (en) | Automatic detection of protocols in a network | |
US7761585B2 (en) | Techniques for automatically detecting protocols in a computer network | |
US7716345B2 (en) | Client to server streaming of multimedia content using HTTP | |
EP1916820B1 (en) | Methods and apparatuses for transferring data | |
US6594699B1 (en) | System for capability based multimedia streaming over a network | |
JP4456113B2 (en) | System and method for selecting a data provider | |
US8117328B2 (en) | System and method for automatically recovering from failed network connections in streaming media scenarios | |
US7447775B1 (en) | Methods and apparatus for supporting transmission of streaming data | |
US8671163B2 (en) | Multi-output packet server with independent streams | |
JP2007536796A (en) | Fast startup for streaming media | |
CN111107445B (en) | Media protocol stream optimization method and system | |
JP4285101B2 (en) | Real-time data communication system, real-time data communication apparatus, and real-time data communication method | |
KR20050062945A (en) | Rtsp module for streaming server and processing method of control messages therefor |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): JP |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
ENP | Entry into the national phase |
Ref country code: JP Ref document number: 1998 533096 Kind code of ref document: A Format of ref document f/p: F |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1998903846 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1998903846 Country of ref document: EP |
|
WWG | Wipo information: grant in national office |
Ref document number: 1998903846 Country of ref document: EP |