Classifications

• • 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
  • H04L67/10—Protocols in which an application is distributed across nodes in the network
  • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L67/1004—Server selection for load balancing
  • H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/90—Details of database functions independent of the retrieved data types
  • G06F16/95—Retrieval from the web
  • G06F16/954—Navigation, e.g. using categorised browsing
• • 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
  • H04L67/10—Protocols in which an application is distributed across nodes in the network
  • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L67/1004—Server selection for load balancing
  • H04L67/1006—Server selection for load balancing with static server selection, e.g. the same server being selected for a specific client
• • 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
  • H04L67/10—Protocols in which an application is distributed across nodes in the network
  • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L67/1004—Server selection for load balancing
  • H04L67/1014—Server selection for load balancing based on the content of a request
• • 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
  • H04L67/10—Protocols in which an application is distributed across nodes in the network
  • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L67/1004—Server selection for load balancing
  • H04L67/1019—Random or heuristic server selection
• • 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
  • H04L67/10—Protocols in which an application is distributed across nodes in the network
  • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L67/1004—Server selection for load balancing
  • H04L67/1023—Server selection for load balancing based on a hash applied to IP addresses or costs
• • 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
  • H04L67/10—Protocols in which an application is distributed across nodes in the network
  • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L67/1034—Reaction to server failures by a load balancer
• • 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
  • H04L67/10—Protocols in which an application is distributed across nodes in the network
  • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L67/1038—Load balancing arrangements to avoid a single path through a load balancer
• • 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/2866—Architectures; Arrangements
  • H04L67/30—Profiles
  • H04L67/306—User profiles
• • 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/535—Tracking the activity of the user
• • 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
  • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
• • 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
  • H04L67/10—Protocols in which an application is distributed across nodes in the network
  • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
• • 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
  • H04L67/10—Protocols in which an application is distributed across nodes in the network
  • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L67/10015—Access to distributed or replicated servers, e.g. using brokers
• • 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

• the invention relates to a system and method for automated Web site launching. More specifically, this invention relates to a system and method for automated Web site launching based on user preferences.
• the Web is a group of computer on the Internet providing a distributed hypermedia framework for presenting and viewing multimedia documents.
• Web page refers to a discrete document usually formatted using the Hypertext Markup Language (HTML); however, other formatting standards may also be used such as the Extensible Markup Language (XML) or Standard Generic Markup Language (SGML).
• HTML Hypertext Markup Language
• XML Extensible Markup Language
• SGML Standard Generic Markup Language
• Such documents may include a variety of multimedia elements either included directly or by reference.
• Web pages, and elements included within such pages, may be addressed on the Web utilizing Uniform Resource Locators, or URLs.
• a URL has three basic components a protocol indicator, a server indicator and a location indicator.
• a typical URL for a Web page might be http://www.myserver.com:8080/dirl/dir2/rsrc.html.
• the protocol indicator indicates the protocol that a Web client should utilize to access the desired resource; typically, the protocol used to retrieve Web pages is the Hypertext Transfer Protocol (HTTP).
• HTTP Hypertext Transfer Protocol
• Other protocols include the file transfer protocol (FTP), the gopher distributed document protocol (GOPHER) and a variety of other Internet standard protocols that will be known to those of skill in the art.
• the protocol indicator is separated from the remainder of the URL with a colon.
• the URL specifies the HTTP protocol.
• the server indicator corresponds to a particular computer on the Internet to which a Web client should connect using the indicated protocol to retrieve the desired resource.
• the server indicator will be a text name of the desired server; however, the indicator could also be the underlying numeric Internet Protocol (IP) address to which the text name corresponds.
• IP Internet Protocol
• a URL may also contain a port specification indicating a particular communication port on the indicated server to which the Web client should connect. Default ports are assumed based on the communication protocol if no port specification is included. For instance, by default HTTP request connections utilize port 80 on the indicated server. In the example URL above, the URL specifies connection to port 8080 on the machine www.myserver.com.
• Different Web clients such as Navigator (by Netscape) and Internet Explorer (by Microsoft) may present visual indications of links in a variety of ways. Activation of such links will usually through a pointing/clicking devise such as a mouse; however, alternate methods such as via the keyboard, a speech recognition interface or other suitable interaction interfaces are equally feasible.
• portal sites have evolved to provide access to Web destinations based on category hierarchies.
• Portals provide an organizational framework for locating sites of interest.
• an end user must have a specific goal in mind, namely a particular category of Web destinations.
• Another solution is Web search technology. Search sites allow an end user to enter keywords; and the search engine retrieves pages that may match the specified keywords. Use of such sites requires the end user to have an even narrower goal than a portal.
• the system and method of the present invention address these and other problems of both advertisers and end users by providing automated Web site launching based upon user preferences.
• the present invention is directed to a system and method for automated Web site launching based on user preferences.
• a system according to the present invention causes a client to present to an end user a selected destination.
• N typical system according to the present invention includes a host computer and a database server. The host computer receives a request for a destination from a client used by an end user. N destination is selected based on data associated with the end user. The selected destination is transmitted to the client in a reply, which, upon receipt by the client, presents on the client the selected destination.
• the data associated with the end user is collected through a registration process and stored in the database server.
• the destination is selected through querying the database server for a destination meeting the data associated with the end user via SQL select statements.
• N relational database contains tables of data associated with all available destinations and of data associated with the end user.
• the data associated with end users may be stored in cookies residing on a client computer running the client. Alternated storage vehicles for both the end user data and the data associated with destination and other selection methods may be used within the scope of the present invention.
• FIG. 1 displays a typical system according to the present invention.
• FIG. 2 is an architecture diagram for a Web site that could be used in conjunction with the present invention.
• FIG. 3 is a screen capture of a base home page 205 of FIG. 2.
• FIG. 4 is a screen capture of a member area display page.
• FIG. 5 is a diagram of the registration process in a preferred embodiment.
• FIG. 6 is a process diagram detailing the steps occurring upon submission of a registration form presented in step 520 of FIG. 5.
• FIG. 7 is a screen capture of a registration page 220 of FIG. 2.
• FIG. 8 is a screen capture of a set start page 225 of FIG. 2.
• FIG. 9 is a screen capture of an education page 240 of FIG. 2.
• FIG. 10 is a screen capture of a member start page 245 of FIG. 2.
• FIGs. 11A-11D displays the tables in a relational database used in a preferred embodiment of the present invention.
• FIG. 12 is a process diagram providing an overview of the steps in a typical automatic Web site launching according to the present invention.
• FIG. 13 is a process diagram providing additional details on the process to handle parameters included in the request, step 1240 of FIG. 12.
• FIG. 14 is a process diagram providing additional details on the process select a Web destination for launch based on user data, step 1250 of FIG. 12.
• FIG. 15 is a process diagram providing additional details on the Web destination selection process from among campaign Web destinations, step 1440 of FIG. 14.
• FIG. 16 is a process diagram providing additional details on the Web destination selection process from among non-campaign Web destinations, step 1470 of FIG. 14.
• the Web server 105 and the database server 110 may use any of a variety of commercially available hardware and software.
• the hardware platform is based upon microprocessor technology, specifically an Intel-based multiprocessor system, running the Windows/NT (Microsoft) operating system.
• the Web server software is the Internet Information Server (IIS) (Microsoft), and the database server software is SQL Server 7.0.
• IIS Internet Information Server
• SQL Server 7.0 the database server software
• the Web server 105 and database server 110 communicate via an Ethernet 115.
• An end user communicates with the Web server via the Internet 120.
• the end user may use any Internet-capable Web client to communicate with the Web server 105.
• Such Web clients will include Web-capable applications running on client computers or other suitable hardware platforms or Web-capable devices.
• Web clients will include, but are not limited to, Web browsers such as Navigator (Netscape) or Internet Explorer (Microsoft) running on suitable client computer platforms such as desktop computers, notebook computer, hand held computers, etc., other Web-capable software running on suitable hardware platforms such as Web-capable cellular telephones and other wireless devices or Web-capable personal data assistants (PDAs) such as the Palm Pilot (3Com).
• the database server in a preferred embodiment stores a relational database.
• FIGs. 11A-1 ID display the tables used in the relational database.
• the database server supports SQL queries and updates.
• Other database architectures such as object- oriented or hierarchical databases could be used in other embodiments.
• the Web server 105 used in conjunction with the present invention may contain pages as seen in FIG. 2.
• a base home page 205 is presented upon initial entry to the site; a typical base home page is seen in FIG. 3.
• the end user may elect to view a help page 210, view a page about the owner of the site 215, view a page providing information about the automated Web destination launching 255, view a page about rewards associated with the use of the automated Web destination launching 260, view pages associated with registering for automated Web destination launching 220 - 245 or view a login page allowing access to the members' area 250.
• the rewards page 260 would be eliminated.
• the members' area login page 250 provides access to a variety of information for individuals already registered; a typical members' area display page shown subsequent to login is seen in FIG. 4. This area could provide an interface for end users to alter data associated with themselves such as changing preferences, add electronic mail service if available and if declined during initial registration, view information on accumulated reward points if rewards are available, quit the automated Web destination launch service, view history of sites presented to them and support other desired functionality.
• an end user must register as a member before being able to utilize the automated Web destination launching functionality.
• the data associated with the end user including his interest preferences is collected through this registration process.
• N diagram of the registration process is seen in FIG. 5.
• a home page is seen by an end user via a Web client; for example, a typical home page as viewed with Internet Explorer (Microsoft) as the Web client is seen in FIG. 3. The end user selects to register.
• a registration page 220 such as seen in FIG. 7, is presented to the end user.
• the end user may select to view a privacy information page 222 or information relevant to international users 224; in either case, the user returns back to the registration page 220.
• the end user fills out the provided form.
• the registration form requests personal information concerning the end user such as name, postal code, e-mail address, a password for use in subsequent login, date of birth, gender, marital status, education level, profession, residential status and income level. Additional and/or differing information could be requested in alternate embodiments.
• the form also requests interest information from the end user with interests broken into eight categories with numerous interests listed under each category, as shown in the table below.
• the end user selects the desired interests and submits the registration page 220.
• the above set of interest is exemplary and, as such, other selections of interests, or combinations of interests, are equally within the scope of the present invention.
• a registration submission process occurs as depicted in FIG. 6.
• the fields in the registration form are validated 610.
• a determination is made as to whether all fields have valid data 630. If not 634, an error message is presented to the end user 620. For instance, if the end user neglected to fill out a required field, an error message would be presented, and the end user would be given an opportunity to correct the error.
• all data is valid 638, a member record is created 640, and a member's interest record is created 650. In a preferred embodiment, these records are stored on the database server 110.
• FIGS. 1 IB and 11C display the tables associated with members used in a relational database in a preferred embodiment. An initiation transaction is logged with respect to the new registered end user 660.
• Associate counts are updated 670. Nn associate count is used to pay associates commissions based upon the count of users referred by the particular associate.
• a member identification is sent to the Web client for storage on the client computer associated with the end user. This identification is preferably sent and received as cookie data.
• the end user data acquired from the registration form could be sent to the Web client for storage on the client computer associated with the end user in the form of cookie data.
• some of the accumulated data associated with the end user could be stored on the database server 110 while other data could be sent to the Web client for storage as cookie data. For instance, demographic data could be stored on the database server 110 while interest information was stored as cookie data, or conversely, interest information could be stored on the database server 110 while demographic data was stored as cookie data.
• N typical set start page is seen in FIG. 8.
• an educational page is presented to the end user in step 580.
• a typical education page is seen in FIG. 9.
• the process is complete and a member start page with an automatically selected and launched site based upon the user-selected preferences is presented 245 as more fully discussed below.
• N typical member start page is seen in FIG. 10.
• an e-mail account is available to the end user.
• the following additional steps may be performed during the registration process.
• step 540 a determination is made as to whether the end user has chosen to have an e-mail account or not. If yes 548, an e-mail sign up page 230 is presented in step 550. Upon completion of this form, a confirmation page 235 is presented in step 560.
• step 570 the database of e-mail addresses is updated. If no e-mail account is selected 544, the registration process occurs as stated above.
• users data may be collected via usage of the automated Web destination launching functionality rather than, or as a supplement to, a registration process.
• view time of and/or interactions with particular destinations and user indicated ratings for particular destinations could form the basis of establishing or modifying end user interest preferences.
• the user data may be collected via a third-party. Marketing and demographic data received from third- parties such as marketing firms could be imported and form the basis of the data associated with the end user as used in the present invention.
• user data associated with an end user may be subject to modification based upon usage. For example, interests included in the user data may be weighted rather than all or nothing flags.
• view times of and/or interactions with particular destinations and user indicated ratings could be used to modify the weighted values of the users interests based upon the particular destination. Under this approach, user interests are further refined and may be used to better select Web destinations for automated launching.
• the Web server directs the Web client used by the end user to a Web destination based on data associated with the end user upon the receipt of a request from the Web client.
• FIG. 12 provides an overview of the steps in this process.
• the request may be generated in a variety of ways by the end user 1210.
• the end user is directed to a Web destination upon the completion of the registration process.
• the end user could login into the Web server 105 through the member area login page 250 or the home page 205.
• the end user could manually enter the URL for the start page 245, click on a bookmark corresponding to this page or click on a history item in his browser corresponding to this page.
• the end user could simply launch is Web client to generate the request if the Web client designates the start page 245 as its home page.
• other user actions may result in the invocation of automated Web site launching. No matter which user action occurred in step 1210, the Web client initiates a request to the Web server 105 in step 1220.
• step 1230 a determination is made as to whether the request includes parameters indicating an override of the automated Web destination selection.
• step 1310 a determination is made as to whether an edit field associated with the request is populated with a URL. If the field is populated, the URL contained in the field is formatted 1320 and returned 1360 for reply generation and transmission 1260. If the field is not populated, a further check is made to see if a query string associated with the request is populated 1330 and if the populated query string contains a URL 1340. If either of these checks generates a negative result, a selection of Web destination based upon user data occurs via step 1250, which is returned 1360 for reply generation and transmission 1260. If both checks generate a positive result, the URL in the query string is formatted 1360 and returned 1360 for reply generation and transmission 1260.
• a Web destination is selected based upon user data associated with the end user in step 1250 as seen in FIG. 14. First, a determination is made as to whether the request includes a specific interest of the end user 1410. If an interest is included 1414, a query is passed to the database server in SQL requesting all Web destinations meeting the included interest, and a Web destination from the query result is selected at random or under some priority scheme such as revenue generated from directing a Web client to a particular destination
• the URL of the selected Web destination is formatted 1430 and returned 1490 for reply generation and transmission 1260.
• Web destinations fall into two categories campaign Web destinations and non-campaign Web destination.
• N campaign Web destination is a Web destination whose owner has agreed to pay the launch service provider a commission for directing end users to the campaign Web destination; a Web destination may fall into the campaign category for a limited time period and/or for a limited number of directed end users per day.
• Campaign Web destinations are effectively a subset of non-campaign Web destinations.
• an attempt is made to locate a campaign Web destination based upon user data and to select a Web destination from among the located campaign Web destination 1440 as more fully described below.
• a determination is made as to whether a selected Web destination was found among campaign destination 1450. If a selected Web destination was found, the URL of the selected Web destination is formatted 1460 and returned 1490 for reply generation and transmission 1260. If a selected Web destination was not found, a Web destination is selected from among non-campaign Web destination 1470 as more fully described below. The selected Web destination is formatted 1480 and returned 1490 for reply generation and transmission 1260.
• FIG. 15 provides details of the campaign Web destination selection level process 1440. In step 1502, a set of active campaign Web destination is retrieved along with the selection criteria for those campaign destinations.
• step 1505 a check is made to see if a campaign match based upon interests will yield a non-empty set of campaign Web destinations. If a non-empty set would result, the set is generated in step 1510. A further check is made in step 1515 to determine whether any of the campaign Web destinations matches the demographic data associated with the end user. If a demographic match occurs within the interest matched set, a finalized set of campaigns is generated in step 1520. If either an interest match 1505 or a demographic match 1515 fails, a failure condition is returned to process requesting a campaign Web destination 1550. This failure will lead to the selection of a Web destination via the second level, non- campaign approach 1470.
• a campaign Web destination is selected in step 1540. If selection fails due to an empty finalized set 1545, a failure condition is returned to process requesting a campaign Web destination 1550. This failure will lead to the selection of a Web destination via the second level, non-campaign approach 1470.
• the selection may occur at random; however, in a preferred embodiment, the selection is based upon factors associated with the campaign Web destinations in the finalized set such as priority levels of particular campaigns, revenue generated for directing an end user to a particular campaign, the time of day and current numbers of end users directed to the campaign Web destinations.
• the selected campaign Web destination is return in step 1560 for formatting in step 1460 and for further return in step 1490.
• the following SQL query is used in conjunction with a relational database having the tables in FIGs. 11 A - 1 ID to generate the set of active campaign Web destinations and the selection criteria associated with these campaigns, step 1502:
• FIG. 16 provides details of the non-campaign Web destination selection level process 1470.
• a set of Web destinations is selected based upon data associated with the end user. This set is preferably determined based upon the end user's interests and demographic data.
• the following SQL query is used in conjunction with a relational database having the tables in FIGs. 11 A
• step 1250 may not include a two level selection approach.
• a single query is used to select a Web destination without regard to distinctions between campaign Web destinations and non-campaign Web destinations.
• step 1250 may involve a sorting step that prioritizes the group of potential selected Web destinations. For instance, in the two level approach the campaign Web destination determined based upon user data associated with the end user may be sorted according to revenue derived from the particular campaign. In another embodiment, the sorting may be made based upon weighting of the different interests associated with the end user to achieve an ordering of Web destination from the highest likely interest level to the lowest likely interest level.
• this reply includes a Web page having two component parts a display area for displaying the selected Web destination and a navigation bar allowing further interaction with the Web server 105.
• the Web client retrieves and formats the two components parts: the content for the display area from the selected Web destination and the content for the navigation area from the Web server 105.
• the Web server 105 finally determines the type of visit the end user has made in step 1270 and records a transaction corresponding to this visit in step 1280.
• the accumulated recorded transactions of visits by end users to selected Web destinations may be used to bill the respective owners of the Web destinations.
• the recorded transactions are used to generate invoices to billing contacts associated with the owners of the respective Web destinations.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• General Engineering & Computer Science (AREA)
• Databases & Information Systems (AREA)
• Computer Hardware Design (AREA)
• Theoretical Computer Science (AREA)
• Remote Sensing (AREA)
• Data Mining & Analysis (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Radar, Positioning & Navigation (AREA)
• Information Transfer Between Computers (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Applications Claiming Priority (3)

Publications (1)

Family

ID=22312607

Family Applications (1)

Country Status (4)

Families Citing this family (3)

Family Cites Families (3)

• 1999
  • 1999-11-02 WO PCT/US1999/025839 patent/WO2000026800A1/en not_active Application Discontinuation
  • 1999-11-02 EP EP99956878A patent/EP1127317A1/de not_active Withdrawn
  • 1999-11-02 NZ NZ512154A patent/NZ512154A/xx unknown
  • 1999-11-02 AU AU13395/00A patent/AU1339500A/en not_active Abandoned

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events