Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L61/00—Network arrangements, protocols or services for addressing or naming
  • H04L61/35—Network arrangements, protocols or services for addressing or naming involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• • 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/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
  • H04L51/21—Monitoring or handling of messages
  • H04L51/214—Monitoring or handling of messages using selective forwarding
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
  • H04L51/48—Message addressing, e.g. address format or anonymous messages, aliases
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L61/00—Network arrangements, protocols or services for addressing or naming
  • H04L61/30—Managing network names, e.g. use of aliases or nicknames
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L61/00—Network arrangements, protocols or services for addressing or naming
  • H04L61/45—Network directories; Name-to-address mapping
  • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
  • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L2101/00—Indexing scheme associated with group H04L61/00
  • H04L2101/30—Types of network names
  • H04L2101/37—E-mail addresses

Definitions

• the present invention relates to art of computer networks and their interaction with other systems. It finds particular application in conjunction with the use of the Domain Name System (DNS) for parameter-based commands issued over networks, and in conjunction with electronic mail (email) addressing systems for computer networks and, accordingly, will be described with particular reference thereto. However, it is to be appreciated that the present invention is also amenable to other like applications.
• DNS Domain Name System
• the Internet is a constantly expanding network of computer networks with various kinds of information and services. Commands are used to access these information and services by the trillions each day. While these commands are used over the Internet, similar commands are regularly employed on intranets and other networks in countless numbers as well. Over networks, especially over Internet protocol networks, many of these commands are issued by individual people. Therefore, it is desirable to streamline the command issuing process, whenever possible.
• Input commands are used to retrieve information.
• Output commands are used to send information.
• Processing commands are used to manipulate and change information. For the purposes of this invention, we will focus on parameter-based commands as opposed to direct commands with no parameters.
• a parameter-based command is a "standard order given with modifying details". For instance, within a universal resource locator (URL) box on a web browser, you may type: www.domain.com. This is a command to go to that specific Internet address. In this case, each Internet domain is a direct command with no parameters. [0006] If you were to type: www.domain.com/users, this would be a command to go to that Internet address and then specifically to go to the "users" sub-directory. The "/users" component of this command would be a parameter to the command, in other words, items following a forward slash typically supply modifying details.
• URL universal resource locator
• This command is fairly incomprehensible to most, but it provides critical information to the search engine. While user inability to comprehend the commands is clearly illustrated in the search engine context, this drawback is shared over most of the internet protocol addressing system. Accordingly, due to the familiarity of search engines and their dependence on parameters, the examples herein will use search engine commands with the understanding that these examples are merely illustrative of more pervasive problems. [0009]
• the search engine paradigm illustrates many of the problems associated with parameter-based network commands. For example, it often takes many steps to get answers. Indeed, most search engines require five steps to get relevant answers from the initial seeking of the search engine home page to the review of results.
• sub-domains of network addresses that use DNS-like structure for parameter placeholders are used to issue commands instead of host addresses. This is more fully described below. However, a brief example is as follows:
• the command may look as follows: search(5).cleveland.pizza.telenumber.com [0019] This would "pass” the parameters or terms: “Cleveland” and “pizza” to an email based search engine and send the search results for "Cleveland and pizza" to the senders reply email address.
• Another embodiment of the present invention is directed to is a process used to improve an Internet or intranet email system.
• the method involves someone "creating" an email address or virtual email address for most if not all telephone numbers in a given area accessible through a single domain.
• An example is:
• a covered "regional" area could be an area code, city, state, nation, or the world.
• the domain and how the telephone number is included in the email address may take different forms. However, it is desirable that the format of the telephone number within the domain remains consistent. This will allow anyone knowing the addressing format to properly address an email message to any "telephone number" in the world (or region covered) through that given domain.
• Preferred delivery options are obtained from the subscriber.
• the email address itself is what gives us the ability to obtain these delivery options from the subscriber via the telephone number included in the email address as entered by the email sender.
• An aspect of this email addressing system is that not only does the subscriber need not have a current email address, but also, the delivery options can be obtained after the email message has been sent. Typically, a particular delivery mode is designated for a specific recipient before the message can be sent and delivered. [0024] If an email message is sent to an email address using the present invention, the system has either:
• the email will be routed accordingly.
• the system If the system has not obtained the subscribers preferred delivery options, then the system initiates an appropriate "call" to the telephone number to obtain the selection from the subscriber directly.
• a sample call to a subscriber's regular telephone number may be scripted as follows:
• a method of processing a domain name tree includes receiving the domain name tree including a domain name segment and a sub-domain segment .
• a processor is identified from the domain name segment, and at least one command parameter is selected from the sub- domain segment .
• the selected command parameters are converted to terms, such as search terms or alternate address components, configured for further processing.
• the method includes passing the terms converted from the selected command parameters to a search engine to be searched or operated upon.
• the results of the search engine operation are received and provided to a user, for example via reply email or directing a browser to a results page.
• the method includes parsing the terms for separating characters indicative of predefined Boolean operations and forwarding the Boolean operations to the search engine to be operated upon with others of the terms.
• the method includes receiving with the domain tree, data such as an email message, to be forwarded on an alternate service.
• data such as an email message
• the terms converted from the selected command parameters are processed into an alternate service address and the data is forwarded to the address via the alternate service.
• the method includes confirming delivery of the data via the alternate service to a user.
• the method includes identifying a telephone number from data including the terms converted from the selected command parameters and delivering data associated with the domain name tree to a recipient identified by the telephone number.
• the method includes selecting a delivery method hierarchy for data directed to the telephone number and attempting delivery of the data according to the selected delivery method hierarchy.
• a method for passing non-addressed sub-domain information as parameter-based command criteria to a host computer is provided. It works with networks that use multiple domain levels as is common on the Internet and most intranets using the Domain Name System (DNS).
• DNS Domain Name System
• Figure 1 is a representation of a typical network addressing system or domain name structure
• Figure 2 is a typical search engine URL usable by the present invention.
• FIG. 3 is flowchart suitable to practice an embodiment of this invention.
• Figure 4 is an exemplary screen shot of an email search suitable to practice an embodiment of this invention.
• Figure 5 is another exemplary screen shot of an email forwarding service suitable to practice an embodiment of this invention.
• Figure 6 is flowchart suitable to practice another embodiment of this invention.
• Figure 7 is another exemplary screen shot of another forwarding service suitable to practice an embodiment of this invention.
• Figure 8 is yet another exemplary screen shot of another forwarding service suitable to practice an embodiment of this invention.
• existing domain name structures include a base level domain (BLD) 10, otherwise known as a "top level domain” or a "first level domain.”
• Base level domains 10 are not associated with an IP address itself but are a logical grouping used to distinguish between, for example, countries (e.g., .US, .CA, .UK, .HK, etc.), colleges (e.g., .EDU), US military (e.g., .MIL), US government (e.g., .GOV), corporations (e.g., .COM, .ORG), Internet service providers (ISPs) (e.g., .NET) and the like.
• These base level domains 10 manage inquiries to the second level sub-domains 12.
• the second level sub-domain (2LD) 12 is normally associated with an IP address when used in conjunction with a BLD 10.
• a second level domain name are IBM as used in IBM.COM, or OSU as used in OSU.EDU.
• the second level domain 12 usually manages any inquiries to the third level sub-domain 16.
• the third level sub-domain (3LD) 16 is also normally associated with an IP address when used in conjunction with a second level sub-domain 12 and a base level domain 10 (i.e. .2LD.BLD).
• An example of a third level domain name is: SUPPORT, as used in SUPPORT.IBM.COM.
• the third level sub-domain 16 usually manages any inquiries to the fourth level sub-domain 18.
• the fourth level sub-domain (4LD) 18 is usually associated with an IP address when used in conjunction with a third level sub-domain 16, second level sub- domain 12 and a base level domain 10 (i.e. .3LD.2LD.BLD).
• a fourth level domain name include: PC or AIX as used in PC.SUPPORT.IBM.COM or AIX.SUPPORT.IBM.COM.
• the fourth level sub-domain 18 usually manages any inquiries to the next domain and so on to the Nth level domain 20.
• the Nth level domain 20 represents any and all higher level domains.
• the N is representative of any and all higher level domains (i.e., 2, 3, 4, 5, 6, etc.).
• All domain names can contain word(s) or a phrase consisting of letters, numbers, and certain punctuation marks or characters, (a..z, 0..9, etc.).
• the "dot,” or domain separator 30 typically separates domain name levels. This separator 30 is used to designate managing control of higher domain levels to their next lower domain level.
• a domain name segment 34 contains a .BLD 10, and optionally, any number of upper level sub-domains 12, 16, 18, 20.
• Some examples of domain name segments 34 are single level segments (e.g., .COM, .NET, or any .BLD); and multi-level segments (e.g., IBM.COM, ABC.DEF.ORG, one.two.three.four.five.six.NET, etc.).
• Sub- domain segments 38 are any group of one or more discrete "names" separated by a period ".” that does not contain a .BLD 10.
• sub-domain segments 38 are single level segments (e.g., ABC, IBM, telenumber, etc.); and multi-level segments; (e.g., ABC.DEF, Support. IBM, one.two.three.four.five.six, etc). These segments 34, 38 when combined form a complete domain name or a domain name tree 32.
• domain name trees 32 may optionally contain parameters or commands 40 typically separated by forward slashes "/" 42. When these commands 40 contain difficult but required syntax, they are usually derived by a hosting computer from user entries into form-like boxes on a web page. While functional, this system adds additional steps or page views before the user obtains a first hint at the desired information.
• an embodiment of the present invention includes commands 50 placed partially or entirely in a sub-domain segment 38' as sub-domains 16', 18', 20' which are passed to the host computer.
• the sub- domains 16', 18', 20' include search parameters prefixed to a sub-domain segment 38'.
• This sub-domain segment 38' is then passed through to a host, search engine, database, etc. which processes the commands 50 and gives results.
• the host for example, is identified by the domain name segment 34'. In one respect, this method avoids the somewhat longer and confusing method currently used by many search sites.
• Figure 2 begins with receipt of the domain name tree 32' by a host processor as seen in step 52. If the domain name segment 34' is not identified, it is extracted as seen in step 52.
• a processor selects command parameters 50 from the sub-domain segment 38' as seen in step 56.
• the selected command parameters 50 are converted into terms, such as search terms, address fields or other data as seen in step 58.
• Separators 30 are parsed and appropriate Boolean operators are assigned as seen in step 60.
• the terms and Boolean operators are passed to a search engine as seen in step 62, and the results are provided to the user as seen in step 64.
• FIG. 4 another embodiment of the present invention includes a request formatted as an email message.
• the email message includes search parameters or other parameters 60 to be passed to a host in an email address 62.
• the host is identified by the base level-like segment 34" and is separated from other commands 64 by the at symbol, "@" 66.
• the sender's email address 68 is forwarded along with the request, enabling the host to auto-reply results of the command to the sender's email address.
• the other commands field 64 may employ definitions for Boolean operators such as "search.and" where the separator is listed and followed by the definition. Further separators and definitions may be appended as necessary.
• FIG. 5 Another embodiment that suitably practices the invention includes a postal mailing service for email messages.
• the sender would use the their email client application and insert parameters
• These parameters 60' provide an address mechanism permitting a receiving host, identified by the base-level segment 34", to forward the email body 70 to a service for printing and/or delivery to an address indicated by the address parameters 60'.
• the body 70 of the email message would be "the message to be sent".
• This is one example of a command line that the sender has been pre-instructed to use when it is desired to deliver email messages using postal-type addressing, for example the following command format:
• Figure 5 begins with receipt of the domain name tree and data to be forwarded, as seen in step 72.
• the base level 34 here telenumber.com, includes an email system set up as discussed in the above referenced processes to take the sub-domain names 60' (handled as parameters) and pass them to a processor as field variables, as seen in step 74. To continue, the processor converts the parameters into fields such as:
• the processor forwards the data 70 to the address identified by the fields as seen in step 78. In one example, this passed data is then used to print off a mailing label, and the body of the message is printed, placed into an envelope or onto a postcard that has the label affixed for postal mailing.
• the "address" can alternately be any suitable identifier such as the postal address illustrated, an electronic mail address, a telephone number, and the like.
• Additional commands 80 optionally are prefixed, for example, prior to the at symbol "@" 66 and can include routing, handling and other like instructions.
• this embodiment desirably enables a user to "email" a person knowing only a traditional postal mail address, or other identifier such as a telephone number and the like.
• other message delivery mechanisms such as fax, voice mail, telephone call, text messaging to mobile devices and the like can be substituted with no loss of functionality.
• the above domain, Telenumber, may alternately be setup with multiple commands called a command environment.
• the specific command 80 was given within the user name section of the email address. This command was: "SendPostalMail”.
• Telenumber.com could have been setup as a single command domain. Then no command within the usemame would be used, and anything could occupy that place.
• a World Wide Web / URL / Html embodiment includes an address 90 in the command line of a browser window.
• the server or processor identified by "telenumber.com” parsed the address 90 and identified the listed fields 92 from the address, specifically,
• the user verifies the accuracy of the address, types in the body of a message and indicates completion, for example by clicking a Submit button 94.
• the domain telenumber.com receives the information via HTTP and performs the same task as the email version discussed above.
• telenumber.com is a single command domain. So, it automatically knew that the user desired to send a postal message. However, where the domain offers various functionality, command environments are established where the specific command would also be "entered" using a web browser URL, such as:
• a sub- domain includes several digits of a telephone number 100.
• the host processor extracts command parameters from, in the illustrated example, the sub-domain segments 100 and the address portion 104.
• the format is established where the country code, 1 , and the area code 440 form sub-domains, while the remainder of the number lies in the address portion 104. These are converted into a telephone number, which is then called to either deliver the message or to ascertain alternate delivery options.
• the telephone call is carried out using an Interactive Voice Response (IVR) system, although it could easily be accomplished live operators, or in some combination thereof, where, if a subscriber doesn't make a choice using the IVR system, an operator gets on the line or calls back.
• IVR Interactive Voice Response
• Those skilled in the art can appreciate that different phone number portions can reside in different parts of the address and that the illustration is exemplary only.
• Some other numbers such as fax numbers, pager numbers and voice mail numbers may have their own variations on how the delivery options will be obtained.
• delivery options are a few examples of delivery options:
• Fax numbers The IVR system that calls the telephone number, uses an auto-fax detection device. This device informs the system that the telephone number in question is a fax number. The system could then fax to the subscriber, a Subscriber
• Preferred Delivery Options Form It would inform them that they have a pending email much like the IVR script described above.
• This fax form could be pre-coded to automatically "read” it after it is faxed back in by the subscriber. This fax reading system would then know who the fax was from, how they wanted their email delivered, and to where. This system could then route it appropriately as the subscriber desired.
• Voicemail numbers The IVR system that calls the telephone number, uses an auto-voicemail detection device. This device informs the system that the telephone number in question is a voice mail number. The system could then, on the same call, attempt to leave a message to the subscriber. This message would inform them that they have a pending email much like the beginning of the IVR script described above. In the message, the system would also leave a telephone number to call for the subscriber to finish the IVR call as described above. When calling, the subscriber would enter in the telephone number that was called (the telephone number from the original email), so the system will know which message to administer. After receiving the delivery options, the system could then route the email message appropriately as the subscriber desired.
• Pager Numbers The IVR system that calls the telephone number, uses an auto-pager detection device. This device informs the system that the telephone number in question is a pager number. The system could then, on the same call, attempt to leave a telephone number for the subscriber to call. When the Subscriber calls the number, the message would inform them that they have a pending email much like the IVR script above. When calling, the subscriber would enter in the telephone number that was called
• the system will know which message to administer. After receiving the delivery options, the system could then route the email message appropriately as the subscriber desired.
• Some telephone numbers are modem lines. In these cases where an operator may be able to identify what type of number it is, but may not be able to go further, one approach would be to do, telephone number cross referencing. This may allow the system to find out whom the number belongs to by various directory or other sources. Then, we can call the party in question and complete the email delivery. These types of phone numbers will be "marked" in our system, so that future emails to these types of telephone numbers will be handle more smoothly.
• Delivery Options When a subscriber is giving their preferred delivery options, they will be asked how they would like future email messages to be delivered. If they choose fax only, then email messages will automatically be faxed thereinafter. No telephone call to the subscriber is made, only a fax call. The same could go for spoken only, mailed only, or emailed to the email address of their choice. Some subscribers will choose various versions of enhanced email accounts. This would allow the email messages to go right into a pop3 account which is the actual email address sent.
• Some subscribers may opt to choose each time an email message comes in, or to redirect the message to one of the other delivery media. Also, they may desire to have this choice made by the IVR call each time, or by fax, mail, email, or to go to a web site to make the choice. Each of these delivery mechanisms will have the options to direct or redirect the message to another location of their choice. The system will "remember" their preferred addresses for telephone numbers (maybe even mobile phone numbers for remote email notification, fax numbers, mailing addresses, email addresses, and web addresses that they access this related information.
• a single Internet or intranet domain is employed, however, for simplicity herein, reference will only be made to an "Internet” domain.
• Internet domains are “.com”, “telenumber.com”, or even “tele.nmbr.net”.
• “.com” is an example of an Internet “top-level” domain.
• "telenumber.com” is a 2nd level domain with “.com” being the “top-level” of that domain.
• the “telenumber” part is called a "sub-domain” or "the 2 nd level” of the domain.
• “.net” is the top- level domain
• “nmbr” is a sub-domain of ".net”
• the 3 rd level of the domain is "tele”.
• the domain is the "tele.nmbr.net” domain. For our example, we will use the domain
• email addresses are formatted as: username@domain.com [0076]
• create an email address for every telephone number in a given area such as the United States or even the whole world.
• separators can be dots ".” or dashes "-" or other possibilities.
• the telephone number can be all together or split up into different pieces and moved around.
• the telephone number can be within one domain or in sub domains. In can also be split up across many sub domains. Additionally, it could be put partially or fully within the user name section.
• any emails to any telephone number email address would go to some call center.
• an email sender would send an email message, formatted using any predetermined format, to the telephone number email address, it will be forwarded to the call center.
• the email would be routed to an IVR system.
• Joe asks for information about the baseball card collection for sale and asks for a returned call and a pricing. Notice Joe converted the telephone number into the properly formatted email address. Joe sends the message.
• an individual within the call center, receives the email message.
• the Operator picks up a telephone and dials the telephone number as formatted within the email message, which is 1-312-222-3333.
• the operator proceeds to follow a manual process doing the same things the IVR system did in the IVR example above. Primarily, this means they will obtain the preferred delivery options from the subscriber, and then, proceed to manually convert and deliver, the email message to the subscriber. Also, the Operator would ask the subscriber, how they would like to handle future emails. In this example, we will show how the operator could fulfill the delivery of the emailed message in much the same way as the IVR system example.
• Each subscriber preference listed below will give a possible scenario for the
• EMAIL Preference When the subscriber chooses to have the message emailed to them. The Operator goes to the email software client where they received the senders telephone number email message, and use a standard FORWARD function included with most email clients such as Eudora, Microsoft Outlook, or Lotus Notes. The message would be forwarded to the email address given by the subscriber. Also, if the client wanted to have all future messages emailed, the Operator could go to the email server(s) and change the forwarding. Future messages would not go to the call center but to the new forwarding address as changed in the email system, using the email address given by the subscriber.
• the Operator within a remote call center did not have access to the email server(s) they could forward a change order request to an email change specialist located at the email server(s) location. When the Operator was finished, they could then record the transactions in a file on the subscriber, or in an appropriate database program.
• FAX Preference When the subscriber chooses to have the message faxed to them.
• the Operator goes to the email software client where they received the senders telephone number email message, and uses a standard PRINT or PRINT-FAX function included with most email clients such as Eudora, Microsoft Outlook, or Lotus Notes.
• PRINT or PRINT-FAX function included with most email clients such as Eudora, Microsoft Outlook, or Lotus Notes.
• the fax functionality is offered with programs such as Winfax or Microsoft Fax. If the Operator printed out the email message, this printed document would be faxed using a standard stand-alone fax machine. The message would be faxed to the fax number given by the subscriber.
• the Operator could go to the email server(s) and change the forwarding to a Fax-only Operator who would take any future incoming email messages and send them to the subscriber using the process mentioned above.
• the Fax-only Operator would probably use the shared filing system or database as a "central" place for all subscriber preferred deliver options. Future messages would not go to the call center but to the new forwarding address as changed in the email system, using a pre-established email address for the Fax-only operator(s).
• the Spoken-only Operator who would take any future incoming email messages and call and read them to the subscriber.
• the Spoken-only Operator would probably use the shared filing system or database as a "central" place for all subscriber preferred deliver options so they would have the information need to fulfill the subscribers requests. Future messages would not go to the call center but to the new forwarding address as changed in the email system, using a pre-established email address for the Spoken-only Operator(s). If the Operator, within a remote call center did not have access to the email server(s) they could forward a change order request to an email change specialist located at the email server(s) location. When the Operator was finished, they could then record the transactions in a file on the subscriber, or in an appropriate database program (Central Subscriber Options
• POSTAL MAIL Preference When the subscriber chooses to have the message mailed to them. The Operator goes to the email software client where they received the senders telephone number email message, and uses a standard PRINT function included with most email clients such as Eudora, Microsoft Outlook, or Lotus
• This printed document would be mailed to the postal mailing address given by the subscriber. Also, if the client wanted to have all future messages mailed, the Operator could go to the email server(s) and change the forwarding to a Mail-only Operator who would take any future incoming email messages and send them to the subscriber using the process mentioned above.
• the Mail-only Operator would probably use the shared filing system or database as a "central" place for all subscriber preferred deliver options. Future messages would not go to the call center but to the new forwarding address as changed in the email system, using a pre-established email address for the Mail-only Operator(s).
• the Operator could go to the email server(s) and change the forwarding to a Web-view-only Operator who would take any future incoming email messages and publish them on the web for the subscriber.
• the Web-view-only Operator would probably use the shared filing system or database as a "central" place for all subscriber preferred deliver options. Future messages would not go to the call center but to the new forwarding address as changed in the email system, using a pre-established email address for the Web-view-only Operator(s). If the Operator, within a remote call center did not have access to the email server(s) they could forward a change order request to an email change specialist located at the email server(s) location.
• ASK ALWAYS Preference When the subscriber chooses to be asked about each message. The Operator would follow the appropriate directions for each document delivery means above. Then, since the subscriber wants to be asked about all future messages, the Operator would leave the email server(s) just as they are. This would have future email messages go back to the call center each time.
• DELETE function included with most email clients such as Eudora, Microsoft Outlook, or
• an email message may be sent back to the sender, notifying them that the message was rejected. Also, if the client wanted to have all future messages destroyed, the Operator could go to the email server(s) and change the forwarding to a
• Destroy-only Operator who would take any future incoming email messages and destroy them for the subscriber.
• the Destroy-only Operator would probably use the shared filing system or database as a "central" place for all subscriber preferred deliver options. Future messages would not go to the call center but to the new forwarding address as changed in the email system, using a pre-established email address for the Destroy-only

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Databases & Information Systems (AREA)
• Theoretical Computer Science (AREA)
• Data Mining & Analysis (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Information Transfer Between Computers (AREA)

Applications Claiming Priority (3)

Publications (2)

Family

ID=22757200

Family Applications (1)

Country Status (3)

Families Citing this family (1)

Citations (4)

Family Cites Families (1)

• 2001
  • 2001-05-15 WO PCT/US2001/015594 patent/WO2001088723A1/en not_active Application Discontinuation
  • 2001-05-15 EP EP01939039A patent/EP1299810A4/de not_active Withdrawn
  • 2001-05-15 AU AU2001264602A patent/AU2001264602A1/en not_active Abandoned

Patent Citations (4)

Non-Patent Citations (3)

Also Published As

Similar Documents

Legal Events