US20080147435A1 - Universal point of contact identifier system and method - Google Patents

Universal point of contact identifier system and method Download PDF

Info

Publication number
US20080147435A1
US20080147435A1 US12/036,683 US3668308A US2008147435A1 US 20080147435 A1 US20080147435 A1 US 20080147435A1 US 3668308 A US3668308 A US 3668308A US 2008147435 A1 US2008147435 A1 US 2008147435A1
Authority
US
United States
Prior art keywords
subscriber
contact
point
preferred
poc
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12/036,683
Inventor
Ayman Hariri
Scott D. Birnbaum
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AYMAN LLC
Original Assignee
AYMAN LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by AYMAN LLC filed Critical AYMAN LLC
Priority to US12/036,683 priority Critical patent/US20080147435A1/en
Assigned to AYMAN, LLC reassignment AYMAN, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BIRNBAUM, SCOTT D., HARIRI, AYMAN
Publication of US20080147435A1 publication Critical patent/US20080147435A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1069Session establishment or de-establishment
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/018Certifying business or products
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42229Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42229Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
    • H04M3/42263Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location where the same subscriber uses different terminals, i.e. nomadism
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/46Arrangements for calling a number of substations in a predetermined sequence until an answer is obtained
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/46Arrangements for calling a number of substations in a predetermined sequence until an answer is obtained
    • H04M3/465Arrangements for simultaneously calling a number of substations until an answer is obtained
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q3/00Selecting arrangements
    • H04Q3/0016Arrangements providing connection between exchanges
    • H04Q3/0029Provisions for intelligent networking
    • H04Q3/005Personal communication services, e.g. provisions for portability of subscriber numbers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2203/00Aspects of automatic or semi-automatic exchanges
    • H04M2203/45Aspects of automatic or semi-automatic exchanges related to voicemail messaging
    • H04M2203/4536Voicemail combined with text-based messaging
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/487Arrangements for providing information services, e.g. recorded voice services or time announcements
    • H04M3/493Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
    • H04M3/4931Directory assistance systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Arrangements for interconnection between switching centres
    • H04M7/0003Interconnection between telephone networks and data networks
    • H04M7/0009Interconnection between telephone networks and data networks where voice calls remain entirely in the telephone network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Arrangements for interconnection between switching centres
    • H04M7/0024Services and arrangements where telephone services are combined with data services
    • H04M7/0054Services and arrangements where telephone services are combined with data services where the data service is an electronic mail service

Definitions

  • the invention relates to communication systems. More particularly, it relates to methods and apparatuses for establishing communication sessions between a communication initiator and a recipient of the communication based on preferences of the recipient.
  • a communication portal service company give a subscriber to that service one telephone number. This one telephone number is intended to replace all other telephone numbers. The subscriber could then give out only one telephone number to his or her clients and friends, as opposed to the slew of numbers he or she would normally give out.
  • Email addresses are both unique and often reflect an individual's name.
  • John Smith might have the email addresses jsmith@domainame.com, john@domainame.com, john.smith@domainame.com, js@domainame.com, john.smith@domainame.org, etc.
  • “domainame” indicates the network domain in which the subscriber, John Smith, has an email account.
  • the individual also can have email accounts with other service providers using different network domains.
  • John Smith could have additional email addresses for different network domains, such as John.Smith@domainame1.com, John.Smith@domainame2.com, etc.
  • Each of these email addresses would be recognized as relating to John Smith's name, and are more likely to be remembered than his telephone number.
  • Some communication portal services offer unified messaging or unified communications services. Such services allow a caller to leave a message for a recipient using a variety of means, such as facsimile machines, telephones, and computers, and then store those messages in a message box for the recipient to retrieve. These communication portal services might also notify a recipient of new messages in a variety of ways, such as by voicemail, email, etc. However, these services do not provide a communication session between a caller and a recipient, but only allow for messaging between them.
  • Other services and systems enable a caller to connect with a variety of devices designated by the recipient, but require the caller to use a computer to access a web page containing the recipient's contact information.
  • the web page returns the recipient's contact information to a program, such as a Java applet, on the caller's computer so the caller can use the program to contact the recipient using the returned contact information.
  • a program such as a Java applet
  • the recipient's contact information is in jeopardy of being disclosed to the caller.
  • such systems do not automatically establish a communication session with the recipient's preferred point of contact, but require additional action by the caller or the caller's computer to initiate the contact. Further still, the caller must use a computer with a highly functional web browser to initiate the contact.
  • No communication portal services allow a recipient to distribute easily remembered point of contact information, such as the recipient's email address, that a caller can use to automatically establish a communication session with the recipient's preferred point of contact. Accordingly, there is a need for such a service and a system to enable that service.
  • a universal point of contact identifier enables a communication initiator, such as a caller who places a telephone call, to contact a subscriber of a point of contact service, at the subscriber's preferred destination device.
  • a communication initiator using an initiator's device enters the POC ID, which preferably is an email address, that is routed to a requester unit.
  • the communication initiator enters the email address by using a telephone with an alphanumeric entry device, such as a keyboard.
  • the communication initiator can enter the email address by voice, and a voice recognition unit transforms the POC ID into a computer readable string corresponding to the email address.
  • the requestor unit based on the input POC ID, sends a request for the subscriber's preferred point of contact information to a server in the network domain providing the subscriber's email service.
  • the server identifies a lookup table holding the subscriber's preferred contact information. Based on the type of contact the initiator indicates, the preferred point of contact information for the specified type of contact is returned to the requester unit.
  • the requester unit then controls a switch to connect the initiating device with the destination device corresponding to the returned preferred contact information.
  • FIG. 1A is an illustration of a conventional business card with many different points of contact printed on the card.
  • FIG. 1B is an illustration of another conventional business card, with fewer points of contact printed on the card than the card shown in FIG. 1A , but still having multiple points of contact printed on the card.
  • FIG. 1C is an illustration of a business card that has only a single point of contact printed on it, and can be used concomitantly with the present invention.
  • FIG. 2 is a block diagram illustrating a universal point of contact (POC) identifier (ID) system, in which a subscriber to a universal contact service has a universal point of contact ID that is used by a communication initiator to initiate contact with the subscriber.
  • POC point of contact
  • ID universal point of contact
  • FIG. 3 shows a data structure, preferably residing in the requester unit shown in FIG. 2 , associating a subscriber's universal point of contact ID domain name with an Internet Protocol (IP) address for a server on which the subscriber's contact information is stored.
  • IP Internet Protocol
  • FIG. 4 shows a data structure, preferably residing in the server and lookup table shown in FIG. 2 , with a subscriber's universal point of contact information recorded in it.
  • FIG. 5 shows a message structure for a message sent from a requester unit to a server in which a subscriber's universal point of contact information is recorded.
  • FIGS. 6A-C are flowcharts showing a process for using a universal point of contact ID to contact a subscriber.
  • FIG. 7 is a block diagram illustrating another embodiment of a universal point of contact (POC) identifier (ID) system, in which the requester unit includes a switch.
  • POC point of contact
  • ID identifier
  • a universal point of contact (POC) identifier is a unique identifier that is associated with a person and that person's points of contact.
  • POC ID is a unique identifier that is associated with a person and that person's points of contact.
  • Such a person with a POC ID can subscribe to a service that stores information about the person's various points of contact, for example, the person's home telephone numbers, business telephone numbers, facsimile numbers, email addresses, and physical addresses (e.g., home and business postal addresses).
  • An effect of having a universal POC ID is that only that POC ID need be given to others in order to contact that person to whom the POC ID is assigned (hereinafter “the subscriber”). This effect is illustrated by considering a person's business card. A conventional business card is shown in FIG.
  • FIG. 1A includes a physical address, two telephone numbers, a facsimile number, a cellular telephone number and an email address, for a total of six points of contacts.
  • FIG. 1B shows a business card that could be used by subscribers of certain existing services that consolidate the subscriber's telephone numbers into a single telephone number. However, a subscriber to such a system still must inform others of the subscriber's physical address and email address, in addition to the consolidated telephone number. Accordingly, there is a need to further simplify the point of contact information a person disseminates.
  • the present invention meets that need by enabling subscribers to disseminate only a single, universal point of contact ID, preferably an email address.
  • a single, universal point of contact ID preferably an email address.
  • FIG. 1C the only information that need be printed on a subscriber's business card is the subscriber's name and the subscriber's universal POC ID, here, an email address.
  • the subscriber to the universal point of contact service has a user ID of “John.Smith” in the network domain “domainame.com”. Often, the domain name will be the name of the subscriber's service provider.
  • FIG. 2 A system for using a universal POC ID is shown in FIG. 2 .
  • the system includes an initiator's device 10 that enables a communication initiator to enter a subscriber's universal POC ID while using, preferably, a conventional device such as a telephone or facsimile (fax) machine.
  • An example of a communication initiator is a caller using a telephone device to call the subscriber.
  • the communication initiator is referred to hereinafter as a caller, however, it will be understood that a communication initiator can initiate communication with a subscriber using initiating devices other than a telephone.
  • the caller uses the initiator's device to input a universal POC ID, preferably an email address, in order to establish a communications session with a device the subscriber has designated as his or her preferred point of contact, referred to here as a destination device.
  • the initiator's device 10 also enables a caller to indicate the type of contact the caller is attempting to make with the subscriber, such as a voice conversation or a fax transmission.
  • the initiator's device 10 shown in FIG. 2 , has either connected to it or integral with it, a universal POC ID entry device 20 , such as a keyboard with separate numeric and non-numeric keys, for entering numeric and non-numeric information, respectively.
  • the communication session can be established through a public switched telephone network (PSTN), using a conventional telephone or fax machine as the initiator's device.
  • PSTN public switched telephone network
  • the communication session can be established in an alternative communication medium, for example as a voice session over a data network, using for example, a voice over internet protocol (VoIP).
  • VoIP voice over internet protocol
  • the initiator's device 10 is connected to a switch 30 in a telephone company's central office. Connected to the switch 30 , preferably, is a requester unit 40 .
  • the requestor unit 40 is connected to a data network 60 .
  • the requester unit 40 includes a network interface unit (NIU) 40 a for interfacing with the telephone network switch 30 , a control unit 40 b connected to the NIU for controlling the requestor unit, and a repository interface unit (RIU) 40 c , which is connected to the control unit 40 b , and interfaces with the data network 60 .
  • the NIU 40 a can include a voice response unit (VRU) 40 d for receiving voice signals from the switch 30 and converting them to textual information.
  • VRU voice response unit
  • the requestor unit's role is to receive, via switch 30 , a universal POC ID input to the initiator's device 10 by a caller, and locate a repository of the subscriber's contact information based on the universal POC ID. Once that repository is located, the POC ID can query it and receive back information concerning the subscriber's preferred contact point.
  • the requester unit 40 uses well-known domain name services (DNS) to locate the repository based on the POC ID.
  • the requester unit can have a storage unit 50 that holds routing information for locating the subscriber's preferred contact information.
  • FIG. 3 shows an example of routing information 300 held in storage unit 50 .
  • the routing information associates a domain name in a universal POC ID with a network address.
  • the domain name in a universal POC ID John.Smith@domainame.com
  • IP internet protocol
  • the routing information 300 can be used when domain name services (DNS) are not available.
  • the requester unit 40 is connected to the data network 60 , such as an internet, to communicate with servers connected to the network 60 .
  • the subscriber's service provider has a server 70 located in a network domain where the subscriber has his or her email account.
  • a storage unit 80 holding the subscriber's points of contact information, such as telephone numbers, facsimile numbers, email addresses, postal addresses, etc.
  • the storage unit 80 can contain a lookup table, such as the example lookup table 400 shown in FIG. 4 .
  • the server 70 and storage unit 80 form a repository for holding the subscriber's preferred point of contact information.
  • a subscriber can access the server 70 and lookup table 400 in storage unit 80 by way of a subscriber interface 90 , such as with a World-Wide Web browser 90 , and can add or modify the POC information held in the database 80 .
  • the subscriber via the interface 90 , can also designate the POC IDs by which the subscriber prefers to be contacted.
  • the switch 30 also connects initiator's device 10 to a PSTN 100 , and operates to route a call to a destination device. Also connected to the PSTN 100 , at a destination end, is another central office 110 . Central office 110 connects a destination device, such as a telephone 120 a or a fax machine 120 b , to the PSTN 100 . Alternatively, if the destination device is a wireless device, such as a cellular telephone 120 c or a personal digital assistant (PDA) 120 d , a wireless system 110 receives the call from the PSTN and transmits it to the subscriber's wireless destination device.
  • the wireless system 110 includes a master switch center (MSC).
  • MSC master switch center
  • the MSC in response to receiving a call for the subscriber's device, establishes a wireless connection with that device, thereby establishing a connection between the initiator's device 10 and the subscriber's wireless device (e.g., cellular telephone 120 c ) corresponding to the subscriber's preferred point of contact.
  • the subscriber's wireless device e.g., cellular telephone 120 c
  • the requester unit 40 upon receiving the universal POC ID and an indication of the type of contact, will inspect the POC ID and detect the domain name of the web server 70 . For example, if the caller enters the POC ID “John.Smith@domainame.com,” the requestor unit 40 will recognize the domain name as “domainame.com.” It will then formulate a request for the subscriber's preferred point of contact and send that request to the server identified by the domain name in the POC ID.
  • the requester unit 40 can send the request using conventional domain name services (DNS).
  • the requester unit 40 can include a database 50 that holds mapping information relating a POC ID to a domain name for the subscriber.
  • FIG. 3 shows an example data structure 300 that maps the domain name portion of a universal POC ID (i.e., John.Smith@domainame.com) to a domain address (i.e., Internet protocol (IP) address: 123.45.67.89) for a server in a domain servicing the subscriber.
  • a universal POC ID i.e., John.Smith@domainame.com
  • IP Internet protocol
  • the requestor unit 40 communicates with the server 70 by sending a message 500 , an example of which is shown in FIG. 5 .
  • the message 500 includes the subscriber's user ID known within the server's domain, and an indication of the type of contact the initiator is attempting.
  • message 500 can contain a fully qualified POC ID.
  • the caller is attempting to initiate a voice contact with the subscriber, and accordingly, the “type of contact” field in message 500 indicates that the initiator is attempting to contact the subscriber by telephone to have a voice conversation with the subscriber.
  • the storage unit 80 holds the subscriber's point of contact information in a manner suitable for the server environment. For example, a lookup table can be employed to hold the subscriber's point of contact information. Where appropriate, the point of contact information can be stored in a database. In either case, the universal POC ID in message 500 operates as a key or an index to locate and reference the subscriber's point of contact information.
  • FIG. 4 shows a data structure 400 for holding the subscriber's point of contact information.
  • the subscriber's POC data structure associates the subscriber's universal POC ID with two different home telephone numbers, two different business telephone numbers, a facsimile telephone number, an e-mail address, and a postal address, all for contacting the subscriber.
  • the POC data structure also includes a “type” field associated with each POC entry to indicate the type of POC for that entry.
  • the POC data structure also includes a “preference” field associated with each POC entry to indicate if the subscriber has designated that entry as a preferred point of contact.
  • the data structure 500 can take any form so long as a subscriber's point of contact information can be located and retrieved based on the subscriber's universal POC ID, or a portion of it.
  • FIGS. 6A and 6B are flowcharts illustrating a process that a caller can follow to send a message to a subscriber by way of the subscriber's preferred contact method.
  • a caller initiates a contact with a subscriber by first entering a predetermined input signifying that a universal POC ID will be used to make the contact ( 600 ).
  • a predetermined input signifying that a universal POC ID will be used to make the contact ( 600 ).
  • the caller can initiate a contact using a universal POC ID by entering a predetermined dialing sequence, such as *88.
  • This predetermined sequence signifies to the CO switch 30 that the contact will be made using a universal POC ID, and the CO switch connects the initiator's device 10 with the requestor unit 40 ( 610 ).
  • the caller After entering the predetermined sequence, the caller enters the universal POC ID and an indication of the type of contact the caller desires to make with the subscriber ( 620 ).
  • the universal POC ID is an email address.
  • a caller can enter the email address any number of ways. For example, if the initiator's device 10 is equipped with a keyboard, the caller can type the subscriber's email address, and the email address is passed to the requestor unit 40 .
  • the voice response unit (VRU) 40 d can be employed to allow the caller to input the email address by speaking it ( 620 ).
  • the VRU can be located within the NIU 40 a of the requester unit 40 , as shown in FIG.
  • the VRU can be programmed to prompt the caller to speak the email address and indicate verbally the type of contact.
  • the VRU can include voice recognition capabilities to convert the spoken email address into an address in a computer readable form, such as an ASCII string, using known voice recognition technology.
  • Operations 600 through 620 described above illustrate an example of a process for entering an email address.
  • the invention is not limited to those operations, and other techniques can be used.
  • the CO switch 30 is equipped to support voice recognition dialing, that technique can be used to enter the subscriber's email address.
  • a caller when first connecting to the CO switch, instead of entering a predetermined dial tone sequence, could just speak the email address.
  • the CO switch 30 is equipped to recognize a voice, as opposed to recognizing only dial tones, it could accept the spoken email address and translate it into a computer readable string to pass to the requestor unit 40 .
  • either the CO switch 30 or the requester unit 40 can prompt the caller to indicate the type of contact desired. The caller would then indicate, verbally for example, the type of desired contact.
  • the requestor unit 40 receives the POC ID and the indicator of the type of contact, and based on the type of contact will determine the appropriate subscriber contact information to request from the lookup table 80 , i.e., a facsimile number, telephone number, etc. ( 630 ). The requester unit then extracts the domain name from the universal POC ID ( 640 ). Alternatively, the requester unit 40 looks up the network address for a server storing the subscriber's POC information, by locating the record 300 in database 50 , if the requestor unit includes such a database 50 . Once the subscriber's domain server's address is determined, the requester unit sends a message, such as message 500 shown in FIG. 5 , to server 70 by way of a network 60 ( 650 ).
  • a message such as message 500 shown in FIG. 5
  • the subscriber's domain server 70 receives the message from the requester unit 40 , and in response to that message, locates the subscriber's POC record 400 in storage unit 80 , for example, in lookup table 400 .
  • the server 70 retrieves the requested POC information from the subscriber's POC record 400 .
  • the POC information that is retrieved is POC information that is appropriate for the type of contact (e.g., a facsimile number in this example) and that has been designated by the subscriber as the preferred POC for that type of communication.
  • the server then returns that retrieved POC information to the requester unit 40 ( 660 ).
  • the server 70 locates the subscriber's record, here the record 400 for universal POC ID John.Smith@domainame.com.
  • the server performs a lookup in record 400 for the voice type entry that the subscriber has designated as the preferred voice number.
  • the subscriber has designated his or her first business telephone line as the telephone number at which the subscriber prefers to be called. Accordingly, the server 70 retrieves that telephone number, (202) 555-1235, and returns it to the requester unit 40 .
  • the connector labeled “A” designates a similarly labeled connector point in FIG. 6B , at which the process flow continues.
  • the requestor unit 40 receives the preferred contact data from server 70 , and sends that data in the appropriate form to CO switch 30 ( 670 ).
  • the requester unit 40 receives the subscriber's first business telephone line number, (202) 555-1235, and sends it to CO switch 30 .
  • the CO switch 30 uses the preferred contact information sent to it to establish a connection to the specified point of contact ( 680 ).
  • the CO switch 30 uses that telephone number to connect the initiator's device to the destination device attached to the subscriber's first business telephone line.
  • the requester unit can continue to monitor the call after sending the preferred contact data to the CO switch to intervene if necessary.
  • a subscriber may want to keep the subscriber's preferred contact data hidden from those attempting to contact the subscriber, thereby concealing the destination device and possibly the subscriber's location. Since the requestor unit interacts with the CO switch to automatically establish the connection with the preferred point of contact, there is no need to send the preferred point of contact data to the initiating device. Accordingly, this aspect of the invention enables an initiating device to connect with the subscriber's preferred point of contact without disclosing that point of contact to the initiator. Alternatively, the requester unit can be programmed to send the preferred point of contact data to the initiating device.
  • the process is complete and the voice or fax session between the initiator's device and the subscriber's preferred device commences ( 700 ).
  • the requestor unit will handle disposing of the call, such as by directing the call to a voice messaging unit to have a message recorded and delivered to the subscriber ( 710 ).
  • the destination device at the subscriber's preferred contact point has the capability to record a voice message if the subscriber does not answer the call.
  • the voice messaging unit could be located at a telephone number designated in the subscriber's lookup table as the desired number for recording voice messages (not shown in FIG. 4 ). Accordingly, the requestor unit 40 would control the CO switch to direct the call to that voice message number.
  • the requestor unit 40 has the capability to record messages and deliver them to the subscriber, in the event the connection with the subscriber's preferred point of contact is not made.
  • operations 710 and 720 are replaced with operations 730 through 760 , shown in FIG. 6C , where like reference numerals refer to like operations in FIG. 6B .
  • the requester unit 40 handles the call differently, depending on whether the type of contact is a voice contact or a fax contact ( 730 ).
  • the requester unit 40 provides for the caller to record a voice message and then sends that recorded message as an email to the subscriber or to a message box on the subscriber's server ( 740 ). If the attempted connection was for a fax session, the requester unit 40 receives the fax, stores it and sends it as an image file to the subscriber's email address or to a message box on the subscriber's server ( 750 ). Once the voice recording or the fax recording is sent to the subscriber's email address or message box, the process ends ( 760 ).
  • Another application of the invention is to provide physical addresses that the subscriber desires to make available, such as the postal addresses for the subscriber's home and business.
  • Such physical addresses can be recorded in the subscriber's point of contact information.
  • the lookup table 400 shown in FIG. 4 has recorded in it the subscriber's business address.
  • This aspect of the invention can be used to provide a shipper with timely information about a subscriber's preferred address.
  • the subscriber grants certain shippers, such as overnight delivery companies, access to the subscriber's preferred postal address and voice address.
  • the subscriber supplies the shipper with his or her universal POC ID.
  • the shipper then accesses the subscriber's preferred shipping address by sending a request for the subscriber's preferred postal address, and if necessary the subscriber's preferred voice point of contact.
  • the shipper can have a requester unit 70 with an interface to it, such as a web browser interface, to enter the subscriber's universal POC address, such as the subscriber's email address, to request a physical address for delivery.
  • the server 70 upon receiving the request, retrieves the physical address in the lookup table 400 that is designated as the preferred physical address for deliveries, and returns it, and optionally the preferred voice address, to the requestor unit for the shipper's use. The shipper then sends the package to that preferred physical address.
  • the invention benefits both the shipper and the consumer, because the shipper has the most current, and hence, likely the most accurate address for the consumer.
  • the consumer gets the package delivered to the address he or she prefers. This aspect of the invention is especially beneficial if the consumer had recently moved to a new address or if the consumer frequently travels.
  • a requester unit 42 includes a switch 43 for connecting to a PSTN.
  • the switch 43 within requester unit 42 makes the connection between the initiator's device and the subscriber's preferred destination device by sending the telephone number for the subscriber's preferred point of contact to central office switch 30 . This avoids the need for the CO switch 30 to match the subscriber's preferred telephone number provided by the requestor unit to the call from the initiator's device.
  • the switch 43 can connect to an alternative network, such as a data network.
  • This data network can provide for a voice connection, using a protocol such as voice over internet (VoIP).
  • VoIP voice over internet
  • the requester unit 40 is shown in FIG. 2 separate from the CO switch 30 , the requestor unit 40 can be integrated into the CO switch 20 .
  • the CO switch receives the email address input by way of a keyboard-enabled telephone or by way of the caller speaking it. If the email address is spoken, the voice response unit translates the spoken email address into computer readable form. The CO switch then sends a request to the server 70 for the subscriber's preferred point of contact information.
  • the central office switch 30 described here, can be a well-known service control point (SCP), appropriately programmed to operate as described here.
  • SCP service control point
  • the invention also enables a subscriber to maintain his or her point of contact information confidential.
  • the requester unit 40 and server 70 /lookup table 80 can be modified to provide point of contact information only for callers the subscriber has designated to the server 70 /lookup table 80 .
  • the requester unit 40 can use caller ID features provided by the central office switch 20 to identify the caller, or can be programmed to require the caller to enter identifying information such as a user ID and password that the subscriber administers.
  • the requester unit's involvement in a call can terminate once a subscriber's preferred POC telephone number is sent to a switch to initiate the call.
  • the requestor unit can continue to monitor the call until it is successfully placed, or alternatively, can continue to monitor the call for a longer period of time up through the end of the call to afford the call participants with further calling options.
  • a subscriber can achieve a find-me-follow me function by designating more than one point of contact as the preferred point of contact.
  • server 70 returns point of contact data for more than one preferred point of contact, based on the subscriber's designations.
  • the requestor unit 40 uses the plurality of preferred points of contact to initiate contacts with the subscriber.
  • the requester unit 40 can initiate these contacts in parallel with one another, or in a serial manner. For example, if three telephone numbers are returned as the preferred contact points, the requester unit 40 can initiate three telephone calls at the same time. By monitoring which telephone call successfully connects with the subscriber, the requester unit 40 can terminate the other calls. Alternatively, the requester unit 40 can initiate calls to the three telephone numbers in sequence.
  • the second telephone number is attempted, and then the third number if the second number is not successful.
  • the calls can be initiated using a combination of parallel and sequential calls. For example, the requester unit 40 can attempt to place the call using a first of the preferred points of contact. If that attempt fails, the requester unit 40 can then initiate calls to the other preferred points of contact, in parallel, all at substantially the same time.
  • the server 70 is programmed to return point of contact data for more than one preferred point of contact, according to preferences the subscriber designates.
  • the subscriber designates one of the points of contact as a primary contact point for a particular type of communication, such as for receiving facsimiles.
  • the subscriber also designates one or more other points of contact as secondary points of contact, for use if a connection cannot be established using the primary point of contact.
  • the requester unit 40 upon receiving the primary and secondary preferred points of contact, would attempt to establish a communication session using the primary preferred point of contact, and if that attempt is unsuccessful, it uses the secondary preferred points of contact to establish a communication session.
  • the attempts using the secondary preferred points of contact may be performed in parallel or sequentially.
  • the subscriber can designate certain preferred points of contact based on the day of the week, and/or the time of day. For example, the subscriber can designate that on Monday through Friday from 9 a.m. to 5 p.m. a work telephone number is the preferred point of contact. From the hours of 5 p.m. to 10 p.m., for example, the subscriber can designate his or her home telephone number as the preferred point of contact. Further still, the subscriber can designate that from the hours of 10 p.m. to 9 a.m. the subscriber's voicemail telephone number is the preferred point of contact.
  • the caller selects the preferred point of contact to use in attempting to establish a communication session.
  • the requestor unit 40 generates a selection message indicating the different preferred points of contact returned by the server 70 .
  • the message is sent to the initiating device for presenting the selection choices to the caller. This presentation can be in the form of displaying an icon or short message for each point of contact selection choice. So as not to disclose the subscriber's preferred point of contact data, the selection message sent to the initiating device does not contain the point of contact information, but instead contains only indicators of the point of contact information.
  • the indicators in the selection message could cause the initiating unit to display three selection items, each relating to a different point of contact, such as “Washington, D.C. fax”, “New York fax” and “Chicago fax”.
  • the caller selects one of those selection items, “Washington, D.C. fax”, for example, as the point of contact to which to send a facsimile.
  • the initiating device returns to the requester unit a selection message containing an indicator of the selected point of contact.
  • the requester unit receives that selection message, recognizes that the “Washington, D.C. fax” indicator was selected, and attempts to establish a communication session using the point of contact information it had previously received from the server that corresponds to the subscriber's Washington, D.C. facsimile point of contact.
  • the requestor unit and initiating device can be programmed to use various permutations of these point of contact selection techniques, such as allowing the caller to select a plurality of the presented points of contacts for simultaneously attempting to establish a plurality of communication sessions.

Abstract

A subscriber to a universal point of contact service designates a preferred point of contact at which a communication initiator, such as a telephone caller, can contact the subscriber. Such an initiator desiring to contact the subscriber uses the subscriber's email address to establish a communication session with a device associated with the subscriber's preferred point of contact. The subscriber's email address is input to an initiating device, preferably a telephone or facsimile machine, using an entry device capable of entering an email address. A requestor unit, receiving the email address, locates a repository of the subscriber's point of contact information, and requests that information. The repository sends the point of contact information the subscriber has designated as preferred, and the requester unit uses that information to control a telephone switch to establish a communication session between the initiating device and the subscriber's preferred point of contact device.

Description

    CROSS REFERENCE TO RELATED APPLICATION
  • This application is a divisional of application Ser. No. 09/873,433 filed Jun. 5, 2001, which claims benefit of Provisional Application No. 60/274,208 filed Mar. 9, 2001. The entire disclosures of the prior applications is hereby incorporated by reference.
  • BACKGROUND OF THE INVENTION
  • 1. Field of the Invention
  • The invention relates to communication systems. More particularly, it relates to methods and apparatuses for establishing communication sessions between a communication initiator and a recipient of the communication based on preferences of the recipient.
  • 2. Description of the Related Art
  • Communication has become a vital part of every day life. For some people, being disconnected is a concept that is inexcusable. If not using office telephones, people use cellular telephones. If not accessing email via a home or office computer, people buy various devices that allow them to access email accounts outside the home or office.
  • With all these different modes of communication comes a long list of communication points of contact. These points of contact range from telephone numbers, including numbers for cell phones, faxes, home phones, office phones, and pagers, to postal addresses, to email addresses. With different competing companies offering different services, these points of contact (POC) can often be subject to change. For some people, these changes happen more frequently than for others.
  • Out of a need to consolidate a person's points of contact a new breed of company has developed. These companies aim to consolidate an individual's communication needs into one portal. Such companies, referred to here as a communication portal service company, give a subscriber to that service one telephone number. This one telephone number is intended to replace all other telephone numbers. The subscriber could then give out only one telephone number to his or her clients and friends, as opposed to the slew of numbers he or she would normally give out.
  • However, people using such communication portal services still have to supply additional contact information. For example, a subscriber to one of these communication portal services would still have to provide others with the subscriber's various email addresses and physical addresses associated with the subscriber. These communication portal services, while consolidating some information, in the end give the subscriber yet another number for people to remember. The result is that instead of making the list of POC's shorter, these communication portal services add yet another item to the list of contact information associated with the subscriber. Accordingly, there is a need to consolidate all or many of a person's POC's into one ID.
  • As with any POC, it needs to be unique to the individual and recognized as such from a global perspective. People's names, as is commonly known, are not useable as ID's because, in general, they are not unique. As an example, the name John Smith is a very common name and does not uniquely identify only one person. Telephone numbers on the other hand, are unique and have been used for decades to place telephone calls. However, telephone numbers do not reflect their owner's name and often can be difficult to remember. Moreover, telephones are designed with keys for entry of numeric telephone numbers, and do not easily facilitate entering non-numeric information.
  • Email addresses are both unique and often reflect an individual's name. For example, an individual named John Smith might have the email addresses jsmith@domainame.com, john@domainame.com, john.smith@domainame.com, js@domainame.com, john.smith@domainame.org, etc. In these examples, “domainame” indicates the network domain in which the subscriber, John Smith, has an email account. The individual also can have email accounts with other service providers using different network domains. Accordingly, in the example here, John Smith could have additional email addresses for different network domains, such as John.Smith@domainame1.com, John.Smith@domainame2.com, etc. Each of these email addresses would be recognized as relating to John Smith's name, and are more likely to be remembered than his telephone number.
  • Some communication portal services offer unified messaging or unified communications services. Such services allow a caller to leave a message for a recipient using a variety of means, such as facsimile machines, telephones, and computers, and then store those messages in a message box for the recipient to retrieve. These communication portal services might also notify a recipient of new messages in a variety of ways, such as by voicemail, email, etc. However, these services do not provide a communication session between a caller and a recipient, but only allow for messaging between them.
  • Other services and systems enable a caller to connect with a variety of devices designated by the recipient, but require the caller to use a computer to access a web page containing the recipient's contact information. The web page returns the recipient's contact information to a program, such as a Java applet, on the caller's computer so the caller can use the program to contact the recipient using the returned contact information. However, by returning the recipient's contact information to the caller's computer, the recipient's contact information is in jeopardy of being disclosed to the caller. Further, such systems do not automatically establish a communication session with the recipient's preferred point of contact, but require additional action by the caller or the caller's computer to initiate the contact. Further still, the caller must use a computer with a highly functional web browser to initiate the contact.
  • No communication portal services allow a recipient to distribute easily remembered point of contact information, such as the recipient's email address, that a caller can use to automatically establish a communication session with the recipient's preferred point of contact. Accordingly, there is a need for such a service and a system to enable that service.
  • SUMMARY OF THE INVENTION
  • A universal point of contact identifier (a POC ID) enables a communication initiator, such as a caller who places a telephone call, to contact a subscriber of a point of contact service, at the subscriber's preferred destination device. A communication initiator using an initiator's device enters the POC ID, which preferably is an email address, that is routed to a requester unit. Preferably, the communication initiator enters the email address by using a telephone with an alphanumeric entry device, such as a keyboard. Alternatively, the communication initiator can enter the email address by voice, and a voice recognition unit transforms the POC ID into a computer readable string corresponding to the email address. The requestor unit, based on the input POC ID, sends a request for the subscriber's preferred point of contact information to a server in the network domain providing the subscriber's email service. The server identifies a lookup table holding the subscriber's preferred contact information. Based on the type of contact the initiator indicates, the preferred point of contact information for the specified type of contact is returned to the requester unit. The requester unit then controls a switch to connect the initiating device with the destination device corresponding to the returned preferred contact information.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1A is an illustration of a conventional business card with many different points of contact printed on the card.
  • FIG. 1B is an illustration of another conventional business card, with fewer points of contact printed on the card than the card shown in FIG. 1A, but still having multiple points of contact printed on the card.
  • FIG. 1C is an illustration of a business card that has only a single point of contact printed on it, and can be used concomitantly with the present invention.
  • FIG. 2 is a block diagram illustrating a universal point of contact (POC) identifier (ID) system, in which a subscriber to a universal contact service has a universal point of contact ID that is used by a communication initiator to initiate contact with the subscriber.
  • FIG. 3 shows a data structure, preferably residing in the requester unit shown in FIG. 2, associating a subscriber's universal point of contact ID domain name with an Internet Protocol (IP) address for a server on which the subscriber's contact information is stored.
  • FIG. 4 shows a data structure, preferably residing in the server and lookup table shown in FIG. 2, with a subscriber's universal point of contact information recorded in it.
  • FIG. 5 shows a message structure for a message sent from a requester unit to a server in which a subscriber's universal point of contact information is recorded.
  • FIGS. 6A-C are flowcharts showing a process for using a universal point of contact ID to contact a subscriber.
  • FIG. 7 is a block diagram illustrating another embodiment of a universal point of contact (POC) identifier (ID) system, in which the requester unit includes a switch.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • Preferred embodiments according to the present invention are described below with reference to the above drawings, in which like reference numerals designate like components.
  • A universal point of contact (POC) identifier (ID), according to the present invention, is a unique identifier that is associated with a person and that person's points of contact. Such a person with a POC ID can subscribe to a service that stores information about the person's various points of contact, for example, the person's home telephone numbers, business telephone numbers, facsimile numbers, email addresses, and physical addresses (e.g., home and business postal addresses). An effect of having a universal POC ID is that only that POC ID need be given to others in order to contact that person to whom the POC ID is assigned (hereinafter “the subscriber”). This effect is illustrated by considering a person's business card. A conventional business card is shown in FIG. 1A, and includes a physical address, two telephone numbers, a facsimile number, a cellular telephone number and an email address, for a total of six points of contacts. FIG. 1B shows a business card that could be used by subscribers of certain existing services that consolidate the subscriber's telephone numbers into a single telephone number. However, a subscriber to such a system still must inform others of the subscriber's physical address and email address, in addition to the consolidated telephone number. Accordingly, there is a need to further simplify the point of contact information a person disseminates.
  • The present invention meets that need by enabling subscribers to disseminate only a single, universal point of contact ID, preferably an email address. This situation is illustrated by FIG. 1C in which the only information that need be printed on a subscriber's business card is the subscriber's name and the subscriber's universal POC ID, here, an email address. As shown in FIG. 1C, the subscriber to the universal point of contact service has a user ID of “John.Smith” in the network domain “domainame.com”. Often, the domain name will be the name of the subscriber's service provider.
  • Universal Point of Contact System
  • A system for using a universal POC ID is shown in FIG. 2. The system includes an initiator's device 10 that enables a communication initiator to enter a subscriber's universal POC ID while using, preferably, a conventional device such as a telephone or facsimile (fax) machine. An example of a communication initiator is a caller using a telephone device to call the subscriber. The communication initiator is referred to hereinafter as a caller, however, it will be understood that a communication initiator can initiate communication with a subscriber using initiating devices other than a telephone. The caller uses the initiator's device to input a universal POC ID, preferably an email address, in order to establish a communications session with a device the subscriber has designated as his or her preferred point of contact, referred to here as a destination device. The initiator's device 10 also enables a caller to indicate the type of contact the caller is attempting to make with the subscriber, such as a voice conversation or a fax transmission. Preferably, the initiator's device 10, shown in FIG. 2, has either connected to it or integral with it, a universal POC ID entry device 20, such as a keyboard with separate numeric and non-numeric keys, for entering numeric and non-numeric information, respectively. The communication session can be established through a public switched telephone network (PSTN), using a conventional telephone or fax machine as the initiator's device. Alternatively, the communication session can be established in an alternative communication medium, for example as a voice session over a data network, using for example, a voice over internet protocol (VoIP).
  • Preferably, the initiator's device 10 is connected to a switch 30 in a telephone company's central office. Connected to the switch 30, preferably, is a requester unit 40. The requestor unit 40 is connected to a data network 60.
  • The requester unit 40 includes a network interface unit (NIU) 40 a for interfacing with the telephone network switch 30, a control unit 40 b connected to the NIU for controlling the requestor unit, and a repository interface unit (RIU) 40 c, which is connected to the control unit 40 b, and interfaces with the data network 60. The NIU 40 a can include a voice response unit (VRU) 40 d for receiving voice signals from the switch 30 and converting them to textual information.
  • The requestor unit's role is to receive, via switch 30, a universal POC ID input to the initiator's device 10 by a caller, and locate a repository of the subscriber's contact information based on the universal POC ID. Once that repository is located, the POC ID can query it and receive back information concerning the subscriber's preferred contact point. Preferably, the requester unit 40 uses well-known domain name services (DNS) to locate the repository based on the POC ID. Alternatively, the requester unit can have a storage unit 50 that holds routing information for locating the subscriber's preferred contact information. FIG. 3 shows an example of routing information 300 held in storage unit 50. The routing information associates a domain name in a universal POC ID with a network address. Here, the domain name in a universal POC ID, John.Smith@domainame.com, is associated with an internet protocol (IP) address for the network domain servicing John Smith's email address. The routing information 300 can be used when domain name services (DNS) are not available.
  • The requester unit 40 is connected to the data network 60, such as an internet, to communicate with servers connected to the network 60. Here, the subscriber's service provider has a server 70 located in a network domain where the subscriber has his or her email account.
  • Associated with server 70 is a storage unit 80 holding the subscriber's points of contact information, such as telephone numbers, facsimile numbers, email addresses, postal addresses, etc. The storage unit 80 can contain a lookup table, such as the example lookup table 400 shown in FIG. 4. Together the server 70 and storage unit 80 form a repository for holding the subscriber's preferred point of contact information. —A subscriber can access the server 70 and lookup table 400 in storage unit 80 by way of a subscriber interface 90, such as with a World-Wide Web browser 90, and can add or modify the POC information held in the database 80. The subscriber, via the interface 90, can also designate the POC IDs by which the subscriber prefers to be contacted.
  • The switch 30 also connects initiator's device 10 to a PSTN 100, and operates to route a call to a destination device. Also connected to the PSTN 100, at a destination end, is another central office 110. Central office 110 connects a destination device, such as a telephone 120 a or a fax machine 120 b, to the PSTN 100. Alternatively, if the destination device is a wireless device, such as a cellular telephone 120 c or a personal digital assistant (PDA) 120 d, a wireless system 110 receives the call from the PSTN and transmits it to the subscriber's wireless destination device. The wireless system 110 includes a master switch center (MSC). The MSC, in response to receiving a call for the subscriber's device, establishes a wireless connection with that device, thereby establishing a connection between the initiator's device 10 and the subscriber's wireless device (e.g., cellular telephone 120 c) corresponding to the subscriber's preferred point of contact.
  • The requester unit 40, preferably, upon receiving the universal POC ID and an indication of the type of contact, will inspect the POC ID and detect the domain name of the web server 70. For example, if the caller enters the POC ID “John.Smith@domainame.com,” the requestor unit 40 will recognize the domain name as “domainame.com.” It will then formulate a request for the subscriber's preferred point of contact and send that request to the server identified by the domain name in the POC ID. The requester unit 40 can send the request using conventional domain name services (DNS). Alternatively, the requester unit 40 can include a database 50 that holds mapping information relating a POC ID to a domain name for the subscriber. FIG. 3 shows an example data structure 300 that maps the domain name portion of a universal POC ID (i.e., John.Smith@domainame.com) to a domain address (i.e., Internet protocol (IP) address: 123.45.67.89) for a server in a domain servicing the subscriber.
  • The requestor unit 40 communicates with the server 70 by sending a message 500, an example of which is shown in FIG. 5. The message 500 includes the subscriber's user ID known within the server's domain, and an indication of the type of contact the initiator is attempting. Alternatively, message 500 can contain a fully qualified POC ID. In the case illustrated by FIG. 5, the caller is attempting to initiate a voice contact with the subscriber, and accordingly, the “type of contact” field in message 500 indicates that the initiator is attempting to contact the subscriber by telephone to have a voice conversation with the subscriber.
  • The storage unit 80 holds the subscriber's point of contact information in a manner suitable for the server environment. For example, a lookup table can be employed to hold the subscriber's point of contact information. Where appropriate, the point of contact information can be stored in a database. In either case, the universal POC ID in message 500 operates as a key or an index to locate and reference the subscriber's point of contact information. FIG. 4 shows a data structure 400 for holding the subscriber's point of contact information. Here, for example, the subscriber's POC data structure associates the subscriber's universal POC ID with two different home telephone numbers, two different business telephone numbers, a facsimile telephone number, an e-mail address, and a postal address, all for contacting the subscriber. The POC data structure also includes a “type” field associated with each POC entry to indicate the type of POC for that entry. The POC data structure also includes a “preference” field associated with each POC entry to indicate if the subscriber has designated that entry as a preferred point of contact. The data structure 500 can take any form so long as a subscriber's point of contact information can be located and retrieved based on the subscriber's universal POC ID, or a portion of it.
  • Operation and Use of a Universal Contact Identifier
  • FIGS. 6A and 6B are flowcharts illustrating a process that a caller can follow to send a message to a subscriber by way of the subscriber's preferred contact method. Referring to FIG. 6, a caller initiates a contact with a subscriber by first entering a predetermined input signifying that a universal POC ID will be used to make the contact (600). For example, assuming the initiator's device is a telephone, the caller can initiate a contact using a universal POC ID by entering a predetermined dialing sequence, such as *88. This predetermined sequence signifies to the CO switch 30 that the contact will be made using a universal POC ID, and the CO switch connects the initiator's device 10 with the requestor unit 40 (610).
  • After entering the predetermined sequence, the caller enters the universal POC ID and an indication of the type of contact the caller desires to make with the subscriber (620). Preferably, the universal POC ID is an email address. A caller can enter the email address any number of ways. For example, if the initiator's device 10 is equipped with a keyboard, the caller can type the subscriber's email address, and the email address is passed to the requestor unit 40. Alternatively, the voice response unit (VRU) 40 d can be employed to allow the caller to input the email address by speaking it (620). The VRU can be located within the NIU 40 a of the requester unit 40, as shown in FIG. 2, but can also be located elsewhere such as an enhanced service provided by the telephone service provider. The VRU can be programmed to prompt the caller to speak the email address and indicate verbally the type of contact. The VRU can include voice recognition capabilities to convert the spoken email address into an address in a computer readable form, such as an ASCII string, using known voice recognition technology.
  • Operations 600 through 620 described above illustrate an example of a process for entering an email address. However, the invention is not limited to those operations, and other techniques can be used. For example, if the CO switch 30 is equipped to support voice recognition dialing, that technique can be used to enter the subscriber's email address. In that case, a caller, when first connecting to the CO switch, instead of entering a predetermined dial tone sequence, could just speak the email address. If the CO switch 30 is equipped to recognize a voice, as opposed to recognizing only dial tones, it could accept the spoken email address and translate it into a computer readable string to pass to the requestor unit 40. Similarly, either the CO switch 30 or the requester unit 40 can prompt the caller to indicate the type of contact desired. The caller would then indicate, verbally for example, the type of desired contact.
  • The requestor unit 40 receives the POC ID and the indicator of the type of contact, and based on the type of contact will determine the appropriate subscriber contact information to request from the lookup table 80, i.e., a facsimile number, telephone number, etc. (630). The requester unit then extracts the domain name from the universal POC ID (640). Alternatively, the requester unit 40 looks up the network address for a server storing the subscriber's POC information, by locating the record 300 in database 50, if the requestor unit includes such a database 50. Once the subscriber's domain server's address is determined, the requester unit sends a message, such as message 500 shown in FIG. 5, to server 70 by way of a network 60 (650).
  • The subscriber's domain server 70 receives the message from the requester unit 40, and in response to that message, locates the subscriber's POC record 400 in storage unit 80, for example, in lookup table 400. The server 70 retrieves the requested POC information from the subscriber's POC record 400. The POC information that is retrieved is POC information that is appropriate for the type of contact (e.g., a facsimile number in this example) and that has been designated by the subscriber as the preferred POC for that type of communication. The server then returns that retrieved POC information to the requester unit 40 (660). For example, if the caller indicates a desire to contact the subscriber to have a voice conversation, the server 70 locates the subscriber's record, here the record 400 for universal POC ID John.Smith@domainame.com. The server performs a lookup in record 400 for the voice type entry that the subscriber has designated as the preferred voice number. In this case, the subscriber has designated his or her first business telephone line as the telephone number at which the subscriber prefers to be called. Accordingly, the server 70 retrieves that telephone number, (202) 555-1235, and returns it to the requester unit 40.
  • At this point in the flowchart shown in FIG. 6A, the connector labeled “A” designates a similarly labeled connector point in FIG. 6B, at which the process flow continues.
  • The requestor unit 40 receives the preferred contact data from server 70, and sends that data in the appropriate form to CO switch 30 (670). In the example here, the requester unit 40 receives the subscriber's first business telephone line number, (202) 555-1235, and sends it to CO switch 30. The CO switch 30 uses the preferred contact information sent to it to establish a connection to the specified point of contact (680). Here, the CO switch 30 uses that telephone number to connect the initiator's device to the destination device attached to the subscriber's first business telephone line. The requester unit can continue to monitor the call after sending the preferred contact data to the CO switch to intervene if necessary. A subscriber may want to keep the subscriber's preferred contact data hidden from those attempting to contact the subscriber, thereby concealing the destination device and possibly the subscriber's location. Since the requestor unit interacts with the CO switch to automatically establish the connection with the preferred point of contact, there is no need to send the preferred point of contact data to the initiating device. Accordingly, this aspect of the invention enables an initiating device to connect with the subscriber's preferred point of contact without disclosing that point of contact to the initiator. Alternatively, the requester unit can be programmed to send the preferred point of contact data to the initiating device.
  • If the connection is successfully established (690), the process is complete and the voice or fax session between the initiator's device and the subscriber's preferred device commences (700). However, if the CO switch 30 cannot establish a communication session with the preferred POC (690), then the requestor unit will handle disposing of the call, such as by directing the call to a voice messaging unit to have a message recorded and delivered to the subscriber (710). Preferably, the destination device at the subscriber's preferred contact point has the capability to record a voice message if the subscriber does not answer the call. Alternatively, however, the voice messaging unit could be located at a telephone number designated in the subscriber's lookup table as the desired number for recording voice messages (not shown in FIG. 4). Accordingly, the requestor unit 40 would control the CO switch to direct the call to that voice message number. After the caller's initiating device is connected to a voice messaging unit, the process ends (720).
  • In another alternative, the requestor unit 40 has the capability to record messages and deliver them to the subscriber, in the event the connection with the subscriber's preferred point of contact is not made. In this alternative, operations 710 and 720 are replaced with operations 730 through 760, shown in FIG. 6C, where like reference numerals refer to like operations in FIG. 6B. In this alternative, if a connection is not made with the subscriber's preferred contact point, the process flows to operation 730. Here, the requester unit 40 handles the call differently, depending on whether the type of contact is a voice contact or a fax contact (730). If the attempted connection was for a voice session, the requester unit 40 provides for the caller to record a voice message and then sends that recorded message as an email to the subscriber or to a message box on the subscriber's server (740). If the attempted connection was for a fax session, the requester unit 40 receives the fax, stores it and sends it as an image file to the subscriber's email address or to a message box on the subscriber's server (750). Once the voice recording or the fax recording is sent to the subscriber's email address or message box, the process ends (760).
  • Physical Point of Contact Addresses
  • Another application of the invention is to provide physical addresses that the subscriber desires to make available, such as the postal addresses for the subscriber's home and business. Such physical addresses can be recorded in the subscriber's point of contact information. For example, the lookup table 400 shown in FIG. 4 has recorded in it the subscriber's business address.
  • This aspect of the invention can be used to provide a shipper with timely information about a subscriber's preferred address. Here, the subscriber grants certain shippers, such as overnight delivery companies, access to the subscriber's preferred postal address and voice address. In this case the subscriber supplies the shipper with his or her universal POC ID. The shipper then accesses the subscriber's preferred shipping address by sending a request for the subscriber's preferred postal address, and if necessary the subscriber's preferred voice point of contact. The shipper can have a requester unit 70 with an interface to it, such as a web browser interface, to enter the subscriber's universal POC address, such as the subscriber's email address, to request a physical address for delivery. The server 70, upon receiving the request, retrieves the physical address in the lookup table 400 that is designated as the preferred physical address for deliveries, and returns it, and optionally the preferred voice address, to the requestor unit for the shipper's use. The shipper then sends the package to that preferred physical address.
  • The invention benefits both the shipper and the consumer, because the shipper has the most current, and hence, likely the most accurate address for the consumer. The consumer gets the package delivered to the address he or she prefers. This aspect of the invention is especially beneficial if the consumer had recently moved to a new address or if the consumer frequently travels.
  • Alternatives
  • Another aspect of the invention is described with reference to FIG. 7, in which a requester unit 42 includes a switch 43 for connecting to a PSTN. In this alternative the switch 43 within requester unit 42 makes the connection between the initiator's device and the subscriber's preferred destination device by sending the telephone number for the subscriber's preferred point of contact to central office switch 30. This avoids the need for the CO switch 30 to match the subscriber's preferred telephone number provided by the requestor unit to the call from the initiator's device.
  • According to still another aspect of the invention, instead of the switch 43 connecting to a PSTN 100, the switch 43 can connect to an alternative network, such as a data network. This data network can provide for a voice connection, using a protocol such as voice over internet (VoIP).
  • Although the requester unit 40 is shown in FIG. 2 separate from the CO switch 30, the requestor unit 40 can be integrated into the CO switch 20. In this regard, the CO switch receives the email address input by way of a keyboard-enabled telephone or by way of the caller speaking it. If the email address is spoken, the voice response unit translates the spoken email address into computer readable form. The CO switch then sends a request to the server 70 for the subscriber's preferred point of contact information. The central office switch 30, described here, can be a well-known service control point (SCP), appropriately programmed to operate as described here.
  • The invention also enables a subscriber to maintain his or her point of contact information confidential. The requester unit 40 and server 70/lookup table 80 can be modified to provide point of contact information only for callers the subscriber has designated to the server 70/lookup table 80. The requester unit 40 can use caller ID features provided by the central office switch 20 to identify the caller, or can be programmed to require the caller to enter identifying information such as a user ID and password that the subscriber administers.
  • According to another aspect of the invention, the requester unit's involvement in a call can terminate once a subscriber's preferred POC telephone number is sent to a switch to initiate the call. As discussed above, the requestor unit can continue to monitor the call until it is successfully placed, or alternatively, can continue to monitor the call for a longer period of time up through the end of the call to afford the call participants with further calling options.
  • According to yet another aspect of the invention, a subscriber can achieve a find-me-follow me function by designating more than one point of contact as the preferred point of contact. Here, server 70 returns point of contact data for more than one preferred point of contact, based on the subscriber's designations. The requestor unit 40 uses the plurality of preferred points of contact to initiate contacts with the subscriber. The requester unit 40 can initiate these contacts in parallel with one another, or in a serial manner. For example, if three telephone numbers are returned as the preferred contact points, the requester unit 40 can initiate three telephone calls at the same time. By monitoring which telephone call successfully connects with the subscriber, the requester unit 40 can terminate the other calls. Alternatively, the requester unit 40 can initiate calls to the three telephone numbers in sequence. If the subscriber is not contacted using the first telephone number, the second telephone number is attempted, and then the third number if the second number is not successful. The calls can be initiated using a combination of parallel and sequential calls. For example, the requester unit 40 can attempt to place the call using a first of the preferred points of contact. If that attempt fails, the requester unit 40 can then initiate calls to the other preferred points of contact, in parallel, all at substantially the same time.
  • According to still another aspect of the invention, the server 70 is programmed to return point of contact data for more than one preferred point of contact, according to preferences the subscriber designates. Here, the subscriber designates one of the points of contact as a primary contact point for a particular type of communication, such as for receiving facsimiles. The subscriber also designates one or more other points of contact as secondary points of contact, for use if a connection cannot be established using the primary point of contact. The requester unit 40, upon receiving the primary and secondary preferred points of contact, would attempt to establish a communication session using the primary preferred point of contact, and if that attempt is unsuccessful, it uses the secondary preferred points of contact to establish a communication session. The attempts using the secondary preferred points of contact may be performed in parallel or sequentially.
  • According to yet another aspect of the invention, the subscriber can designate certain preferred points of contact based on the day of the week, and/or the time of day. For example, the subscriber can designate that on Monday through Friday from 9 a.m. to 5 p.m. a work telephone number is the preferred point of contact. From the hours of 5 p.m. to 10 p.m., for example, the subscriber can designate his or her home telephone number as the preferred point of contact. Further still, the subscriber can designate that from the hours of 10 p.m. to 9 a.m. the subscriber's voicemail telephone number is the preferred point of contact.
  • According to yet a further aspect of the invention, if a plurality of points of contact are returned from the server 70, the caller selects the preferred point of contact to use in attempting to establish a communication session. Here, the requestor unit 40 generates a selection message indicating the different preferred points of contact returned by the server 70. The message is sent to the initiating device for presenting the selection choices to the caller. This presentation can be in the form of displaying an icon or short message for each point of contact selection choice. So as not to disclose the subscriber's preferred point of contact data, the selection message sent to the initiating device does not contain the point of contact information, but instead contains only indicators of the point of contact information. For example, the indicators in the selection message could cause the initiating unit to display three selection items, each relating to a different point of contact, such as “Washington, D.C. fax”, “New York fax” and “Chicago fax”. The caller selects one of those selection items, “Washington, D.C. fax”, for example, as the point of contact to which to send a facsimile. The initiating device returns to the requester unit a selection message containing an indicator of the selected point of contact. The requester unit receives that selection message, recognizes that the “Washington, D.C. fax” indicator was selected, and attempts to establish a communication session using the point of contact information it had previously received from the server that corresponds to the subscriber's Washington, D.C. facsimile point of contact.
  • The requestor unit and initiating device can be programmed to use various permutations of these point of contact selection techniques, such as allowing the caller to select a plurality of the presented points of contacts for simultaneously attempting to establish a plurality of communication sessions.
  • It will be understood that the invention can be practiced using computer programmable devices, and with using hardware and/or software designed to operate according to the descriptions here.
  • Having described preferred embodiments of universal point of contact systems and methods, it is believed that other modifications, variations and changes will be suggested to those skilled in the art in view of the teachings set forth herein. It is therefore to be understood that all such variations, modifications and changes are believed to fall within the scope of the present invention as defined by the appended claims. Although specific terms are employed herein, they are used in their ordinary and accustomed manner only, unless expressly defined differently herein, and not for purposes of limitation.

Claims (4)

1. A method of delivering a package to a person's preferred mailing address, the person having a universal point of contact identifier, and the package being addressed with the person's universal point of contact identifier, the method comprising:
inputting the person's universal point of contact identifier into an initiating device, wherein the person's universal point of contact identifier is different from the person's preferred mailing address;
receiving, in response to inputting the person's universal point of contact identifier, the preferred mailing address that has been designated as a preferred delivery address; and
delivering the package to the preferred mailing address.
2. The method of claim 1, wherein the universal point of contact identifier is an email address.
3. The method of claim 2, wherein the email address consists of a user identification portion, a domain name portion and a demarcation symbol between the user identification and domain name portions.
4. The method of claim 3, wherein the email address is of the form userid@domainname, wherein userid is the user identification portion which is an identifier for the person within a computing domain having the domain name portion designated by domainname.
US12/036,683 2001-03-09 2008-02-25 Universal point of contact identifier system and method Abandoned US20080147435A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/036,683 US20080147435A1 (en) 2001-03-09 2008-02-25 Universal point of contact identifier system and method

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US27420801P 2001-03-09 2001-03-09
US09/873,433 US7379543B2 (en) 2001-03-09 2001-06-05 Universal point of contact identifier system and method
US12/036,683 US20080147435A1 (en) 2001-03-09 2008-02-25 Universal point of contact identifier system and method

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/873,433 Division US7379543B2 (en) 2001-03-09 2001-06-05 Universal point of contact identifier system and method

Publications (1)

Publication Number Publication Date
US20080147435A1 true US20080147435A1 (en) 2008-06-19

Family

ID=23047242

Family Applications (6)

Application Number Title Priority Date Filing Date
US09/873,433 Expired - Lifetime US7379543B2 (en) 2001-03-09 2001-06-05 Universal point of contact identifier system and method
US12/036,793 Active 2024-07-02 US8548142B2 (en) 2001-03-09 2008-02-25 Universal point of contact identifier system and method
US12/036,683 Abandoned US20080147435A1 (en) 2001-03-09 2008-02-25 Universal point of contact identifier system and method
US14/042,125 Expired - Lifetime US8971508B2 (en) 2001-03-09 2013-09-30 Universal point of contact identifier system and method
US14/634,811 Abandoned US20150181035A1 (en) 2001-03-09 2015-02-28 Universal point of contact identifier system and method
US15/043,486 Expired - Lifetime US10333997B2 (en) 2001-03-09 2016-02-12 Universal point of contact identifier system and method

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US09/873,433 Expired - Lifetime US7379543B2 (en) 2001-03-09 2001-06-05 Universal point of contact identifier system and method
US12/036,793 Active 2024-07-02 US8548142B2 (en) 2001-03-09 2008-02-25 Universal point of contact identifier system and method

Family Applications After (3)

Application Number Title Priority Date Filing Date
US14/042,125 Expired - Lifetime US8971508B2 (en) 2001-03-09 2013-09-30 Universal point of contact identifier system and method
US14/634,811 Abandoned US20150181035A1 (en) 2001-03-09 2015-02-28 Universal point of contact identifier system and method
US15/043,486 Expired - Lifetime US10333997B2 (en) 2001-03-09 2016-02-12 Universal point of contact identifier system and method

Country Status (4)

Country Link
US (6) US7379543B2 (en)
EP (1) EP1368975A1 (en)
JO (1) JO2490B1 (en)
WO (1) WO2002073984A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050215273A1 (en) * 2004-02-17 2005-09-29 Nec Corporation Push-to-talk over cellular system
US11178541B2 (en) * 2019-06-25 2021-11-16 T-Mobile Usa, Inc. Address retrieval systems and methods

Families Citing this family (85)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7912199B2 (en) * 2002-11-25 2011-03-22 Telesector Resources Group, Inc. Methods and systems for remote cell establishment
US20060276179A1 (en) * 2001-02-27 2006-12-07 Reza Ghaffari Methods and systems for integrating communications services
US8750482B2 (en) 2001-02-27 2014-06-10 Verizon Data Services Llc Methods and systems for preemptive rejection of calls
US8503639B2 (en) 2001-02-27 2013-08-06 Verizon Data Services Llc Method and apparatus for adaptive message and call notification
US8503650B2 (en) 2001-02-27 2013-08-06 Verizon Data Services Llc Methods and systems for configuring and providing conference calls
US8472606B2 (en) 2001-02-27 2013-06-25 Verizon Data Services Llc Methods and systems for directory information lookup
US8472428B2 (en) 2001-02-27 2013-06-25 Verizon Data Services Llc Methods and systems for line management
US8488761B2 (en) 2001-02-27 2013-07-16 Verizon Data Services Llc Methods and systems for a call log
US8873730B2 (en) 2001-02-27 2014-10-28 Verizon Patent And Licensing Inc. Method and apparatus for calendared communications flow control
US8751571B2 (en) 2001-02-27 2014-06-10 Verizon Data Services Llc Methods and systems for CPN triggered collaboration
US8761363B2 (en) 2001-02-27 2014-06-24 Verizon Data Services Llc Methods and systems for automatic forwarding of communications to a preferred device
US8467502B2 (en) 2001-02-27 2013-06-18 Verizon Data Services Llc Interactive assistant for managing telephone communications
US8798251B2 (en) 2001-02-27 2014-08-05 Verizon Data Services Llc Methods and systems for computer enhanced conference calling
US8494135B2 (en) 2001-02-27 2013-07-23 Verizon Data Services Llc Methods and systems for contact management
US8488766B2 (en) 2001-02-27 2013-07-16 Verizon Data Services Llc Methods and systems for multiuser selective notification
US8774380B2 (en) * 2001-02-27 2014-07-08 Verizon Patent And Licensing Inc. Methods and systems for call management with user intervention
US6771756B1 (en) * 2001-03-01 2004-08-03 International Business Machines Corporation System and method to facilitate team communication
US20020124057A1 (en) * 2001-03-05 2002-09-05 Diego Besprosvan Unified communications system
EP1368975A1 (en) 2001-03-09 2003-12-10 Ayman L.L.C. Universal point of contact identifier system and method
JP3540781B2 (en) * 2001-07-02 2004-07-07 パナソニック コミュニケーションズ株式会社 Internet communication control device and transmission control method thereof
US7092498B2 (en) 2001-11-26 2006-08-15 Ayman, Llc Universal point of contact identifier system calling device and method
US9392120B2 (en) 2002-02-27 2016-07-12 Verizon Patent And Licensing Inc. Methods and systems for call management with user intervention
US20040044734A1 (en) * 2002-08-27 2004-03-04 Mark Beck Enhanced services electronic mail
US7792683B2 (en) * 2002-11-07 2010-09-07 Siemens Industry, Inc. Method and system for address information distribution
EP1568202A4 (en) * 2002-11-25 2012-10-03 Telesector Resources Group Inc Method and apparatus for adaptive message notification
FR2849315B1 (en) * 2002-12-24 2005-08-26 Cit Alcatel DATA PROCESSING DEVICE FOR ESTABLISHING COMMUNICATIONS BY SELECTING USER TERMINALS ACCORDING TO THEIR ACCESSIBILITY
KR100939432B1 (en) 2003-02-14 2010-01-28 주식회사 케이티 Session initiation method using an email address
US8606723B2 (en) 2004-06-04 2013-12-10 Sap Ag Consistent set of interfaces derived from a business object model
US8694397B2 (en) 2004-06-18 2014-04-08 Sap Ag Consistent set of interfaces derived from a business object model
US7680256B2 (en) * 2005-08-18 2010-03-16 One Number Corporation Contact number encapsulation system
US9762475B2 (en) * 2005-09-28 2017-09-12 One Smart Star Limited Communicating with business customers
US20070092072A1 (en) * 2005-09-30 2007-04-26 Microsoft Corporation Efficient phone and e-mail resolution with contact data
EP2076874A4 (en) 2006-05-13 2011-03-09 Sap Ag Consistent set of interfaces derived from a business object model
DE102006030237A1 (en) * 2006-06-30 2008-01-10 Vodafone Holding Gmbh Method, portal and terminal for managing messages between at least two participants
US20080259918A1 (en) 2007-04-19 2008-10-23 Craig Elliott Walker Method and apparatus for managing telephone calls
US20080273680A1 (en) * 2007-05-04 2008-11-06 Ido Eli Zohar System and method for network communication using alternative identifiers
US20080313019A1 (en) * 2007-06-14 2008-12-18 Jeffers Martin C System and method for extracting contact information from website traffic statistics
US9178916B2 (en) 2007-06-28 2015-11-03 Voxer Ip Llc Real-time messaging method and apparatus
US8645477B2 (en) * 2009-01-30 2014-02-04 Voxer Ip Llc Progressive messaging apparatus and method capable of supporting near real-time communication
US20100198922A1 (en) 2009-01-30 2010-08-05 Rebelvox Llc Methods for using the addressing, protocols and the infrastructure of email to support near real-time communication
US8180029B2 (en) 2007-06-28 2012-05-15 Voxer Ip Llc Telecommunication and multimedia management method and apparatus
US20110019662A1 (en) 2007-06-28 2011-01-27 Rebelvox Llc Method for downloading and using a communication application through a web browser
US11095583B2 (en) 2007-06-28 2021-08-17 Voxer Ip Llc Real-time messaging method and apparatus
US8688789B2 (en) * 2009-01-30 2014-04-01 Voxer Ip Llc Progressive messaging apparatus and method capable of supporting near real-time communication
US8825772B2 (en) 2007-06-28 2014-09-02 Voxer Ip Llc System and method for operating a server for real-time communication of time-based media
US8417593B2 (en) 2008-02-28 2013-04-09 Sap Ag System and computer-readable medium for managing consistent interfaces for business objects across heterogeneous systems
US20090326988A1 (en) 2008-06-26 2009-12-31 Robert Barth Managing consistent interfaces for business objects across heterogeneous systems
US20100153297A1 (en) 2008-12-12 2010-06-17 Sap Ag Managing Consistent Interfaces for Credit Portfolio Business Objects Across Heterogeneous Systems
US8849927B2 (en) 2009-01-30 2014-09-30 Voxer Ip Llc Method for implementing real-time voice messaging on a server node
US20100250592A1 (en) * 2009-03-31 2010-09-30 Paquet Vincent F Unifying Web And Phone Presence
US8396751B2 (en) 2009-09-30 2013-03-12 Sap Ag Managing consistent interfaces for merchandising business objects across heterogeneous systems
US9135585B2 (en) 2010-06-15 2015-09-15 Sap Se Managing consistent interfaces for property library, property list template, quantity conversion virtual object, and supplier property specification business objects across heterogeneous systems
US8732083B2 (en) 2010-06-15 2014-05-20 Sap Ag Managing consistent interfaces for number range, number range profile, payment card payment authorisation, and product template template business objects across heterogeneous systems
US9553983B2 (en) * 2010-10-05 2017-01-24 Comcast Cable Communications, Llc Data and call routing and forwarding
CN103650450A (en) * 2011-06-27 2014-03-19 阿尔卡特朗讯 Notification of too many 'no answer' of forwarded to number
US8725654B2 (en) 2011-07-28 2014-05-13 Sap Ag Managing consistent interfaces for employee data replication business objects across heterogeneous systems
US8601490B2 (en) 2011-07-28 2013-12-03 Sap Ag Managing consistent interfaces for business rule business object across heterogeneous systems
US8521838B2 (en) 2011-07-28 2013-08-27 Sap Ag Managing consistent interfaces for communication system and object identifier mapping business objects across heterogeneous systems
US8775280B2 (en) 2011-07-28 2014-07-08 Sap Ag Managing consistent interfaces for financial business objects across heterogeneous systems
US10325240B2 (en) * 2011-09-16 2019-06-18 United States Postal Service Systems and methods for creating and using a hybrid-digital mailbox
US8984050B2 (en) * 2012-02-16 2015-03-17 Sap Se Consistent interface for sales territory message type set 2
US8762454B2 (en) * 2012-02-16 2014-06-24 Sap Ag Consistent interface for flag and tag
US9232368B2 (en) 2012-02-16 2016-01-05 Sap Se Consistent interface for user feed administrator, user feed event link and user feed settings
US8762453B2 (en) * 2012-02-16 2014-06-24 Sap Ag Consistent interface for feed collaboration group and feed event subscription
US8756274B2 (en) * 2012-02-16 2014-06-17 Sap Ag Consistent interface for sales territory message type set 1
US9237425B2 (en) 2012-02-16 2016-01-12 Sap Se Consistent interface for feed event, feed event document and feed event type
US8756135B2 (en) 2012-06-28 2014-06-17 Sap Ag Consistent interface for product valuation data and product valuation level
WO2014000200A1 (en) 2012-06-28 2014-01-03 Sap Ag Consistent interface for document output request
US9246869B2 (en) * 2012-06-28 2016-01-26 Sap Se Consistent interface for opportunity
US9400998B2 (en) 2012-06-28 2016-07-26 Sap Se Consistent interface for message-based communication arrangement, organisational centre replication request, and payment schedule
US8521621B1 (en) * 2012-06-28 2013-08-27 Sap Ag Consistent interface for inbound delivery request
US8949855B2 (en) 2012-06-28 2015-02-03 Sap Se Consistent interface for address snapshot and approval process definition
US8615451B1 (en) 2012-06-28 2013-12-24 Sap Ag Consistent interface for goods and activity confirmation
US9367826B2 (en) 2012-06-28 2016-06-14 Sap Se Consistent interface for entitlement product
US9043236B2 (en) 2012-08-22 2015-05-26 Sap Se Consistent interface for financial instrument impairment attribute values analytical result
US9547833B2 (en) 2012-08-22 2017-01-17 Sap Se Consistent interface for financial instrument impairment calculation
US9076112B2 (en) 2012-08-22 2015-07-07 Sap Se Consistent interface for financial instrument impairment expected cash flow analytical result
US9191343B2 (en) 2013-03-15 2015-11-17 Sap Se Consistent interface for appointment activity business object
US9191357B2 (en) 2013-03-15 2015-11-17 Sap Se Consistent interface for email activity business object
US20160255157A1 (en) * 2015-02-27 2016-09-01 Sonim Technologies, Inc Initiating communication session using preferred mode of communication while maintaining confidentiality
US10223426B2 (en) * 2016-05-25 2019-03-05 Bank Of America Corporation System for providing contextualized search results of help topics
US10333998B1 (en) * 2016-12-27 2019-06-25 Amazon Technologies, Inc. Managing connection requests for multiple devices
FR3072650B1 (en) 2017-10-24 2021-07-30 Dassault Aviat SIDE TRACK CONTROL SYSTEM OF AN AIRCRAFT ON THE GROUND
US11582345B2 (en) * 2018-09-21 2023-02-14 Dell Products L.P. Context data management interface for contact center
US11909918B2 (en) 2022-01-28 2024-02-20 Zoom Video Communications, Inc. Mapping a universal contact center service access point to a service access point specific to a determined modality

Citations (51)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4313035A (en) * 1980-01-18 1982-01-26 Bell Telephone Laboratories, Incorporated Method of providing person locator service
US4446294A (en) * 1982-07-30 1984-05-01 Imperial Chemical Industries Plc Aromatic etherketone/sulphone copolymers
US4677609A (en) * 1985-05-08 1987-06-30 American Telephone And Telegraph Company, At&T Bell Laboratories Semi-automated directory assistance systems
US4734931A (en) * 1986-03-21 1988-03-29 American Telephone And Telegraph Company And At&T Information Systems Inc. Integrated calling directory
US4837798A (en) * 1986-06-02 1989-06-06 American Telephone And Telegraph Company Communication system having unified messaging
US5239577A (en) * 1990-12-03 1993-08-24 Bell Communications Research, Inc. Network and method for providing cross-media connections
US5243645A (en) * 1990-11-01 1993-09-07 At&T Bell Laboratories Automatic system for forwarding of calls
US5452350A (en) * 1992-03-09 1995-09-19 Advantis Subscriber call routing processing system
US5533115A (en) * 1994-01-31 1996-07-02 Bell Communications Research, Inc. Network-based telephone system providing coordinated voice and data delivery
US5555290A (en) * 1990-04-23 1996-09-10 Mci Communications Corporation Long distance telephone switching system with enhanced subscriber services
US5608786A (en) * 1994-12-23 1997-03-04 Alphanet Telecom Inc. Unified messaging system and method
US5633916A (en) * 1994-12-30 1997-05-27 Unisys Corporation Universal messaging service using single voice grade telephone line within a client/server architecture
US5691973A (en) * 1991-06-28 1997-11-25 Telefonaktiebolaget Lm Ericsson Modular application software for telecommunications exchanges for providing all end user services traffic handling and charging requirements of an application type
US5742668A (en) * 1994-09-19 1998-04-21 Bell Communications Research, Inc. Electronic massaging network
US5742763A (en) * 1995-12-29 1998-04-21 At&T Corp. Universal message delivery system for handles identifying network presences
US5796813A (en) * 1995-06-30 1998-08-18 Siemens Telecom Networks Method for routing a call
US5802510A (en) * 1995-12-29 1998-09-01 At&T Corp Universal directory service
US5805810A (en) * 1995-04-27 1998-09-08 Maxwell; Robert L. Apparatus and methods for converting an electronic mail to a postal mail at the receiving station
US5812865A (en) * 1993-12-03 1998-09-22 Xerox Corporation Specifying and establishing communication data paths between particular media devices in multiple media device computing systems based on context of a user or users
US5826039A (en) * 1995-12-29 1998-10-20 Lucent Technologies Inc. Universal connection point for resources and communication unrelated to a physical endpoint
US5826036A (en) * 1996-05-23 1998-10-20 Sharp Kabushiki Kaisha Information processing apparatus
US5850433A (en) * 1996-05-01 1998-12-15 Sprint Communication Co. L.P. System and method for providing an on-line directory service
US5862325A (en) * 1996-02-29 1999-01-19 Intermind Corporation Computer-based communication system and method using metadata defining a control structure
US6014711A (en) * 1997-08-29 2000-01-11 Nortel Networks Corporation Apparatus and method for providing electronic mail relay translation services
US6072862A (en) * 1996-07-02 2000-06-06 Srinivasan; Thiru Adaptable method and system for message delivery
US6104799A (en) * 1997-10-24 2000-08-15 At&T Corp. Customer defined call setup
US6134548A (en) * 1998-11-19 2000-10-17 Ac Properties B.V. System, method and article of manufacture for advanced mobile bargain shopping
US6173272B1 (en) * 1998-04-27 2001-01-09 The Clearing House Service Company L.L.C. Electronic funds transfer method and system and bill presentment method and system
US6215784B1 (en) * 1997-12-24 2001-04-10 Nortel Networks Limited Method and system for voice call completion using information retrieved from an open application on a computing machine
US6243398B1 (en) * 1996-10-21 2001-06-05 Vocaltec Communications Ltd. System and method for personal multimedia communication over a packet switched network
US6259782B1 (en) * 1998-05-04 2001-07-10 Mci Communications Corporation One-number communications system and service integrating wireline/wireless telephone communications systems
US6275577B1 (en) * 1996-06-28 2001-08-14 Harris Corporation Call handling
US6275575B1 (en) * 2000-01-12 2001-08-14 Right4Me.Com, Inc. Method and system for coordinating and initiating cross-platform telephone conferences
US6275490B1 (en) * 1996-08-21 2001-08-14 Netspeak Corporation Method and apparatus for establishing communications from browser application
US6330308B1 (en) * 1998-04-09 2001-12-11 Bell Atlantic Network Services, Inc. Voice mail system for obtaining forwarding number information from directory assistance systems having speech recognition
US6337858B1 (en) * 1997-10-10 2002-01-08 Nortel Networks Limited Method and apparatus for originating voice calls from a data network
US6337902B1 (en) * 1997-12-10 2002-01-08 Alcatel Method for procuring instructions regarding a target subscriber in a telecommunication network and nodal points for this
US20020007421A1 (en) * 2000-05-05 2002-01-17 Thomas Dixon Universal address system
US6343120B1 (en) * 1996-10-08 2002-01-29 At&T Wireless Services, Inc. Method and apparatus for providing a caller ID alias
US6343119B1 (en) * 1997-04-04 2002-01-29 International Business Machines Corporation Access to extended telephone services via the internet
US20020016174A1 (en) * 2000-05-03 2002-02-07 Gibson Eric J. Use of telephone numbers as domain names and as applied in portable electronic devices
US20020042846A1 (en) * 2000-10-05 2002-04-11 Bottan Gustavo L. Personal support network
US6373817B1 (en) * 1999-12-30 2002-04-16 At&T Corp. Chase me system
US6385646B1 (en) * 1996-08-23 2002-05-07 At&T Corp. Method and system for establishing voice communications in an internet environment
US20020118800A1 (en) * 1998-08-27 2002-08-29 Maria Martinez Telecommunication systems and methods therefor
US6625675B2 (en) * 2001-03-23 2003-09-23 International Business Machines Corporation Processor for determining physical lane skew order
US20040030654A1 (en) * 1998-03-06 2004-02-12 Walker Jay S. System and method for facilitating account-based transactions
US6754317B1 (en) * 2000-10-30 2004-06-22 Agere Systems Inc. Telephony access using an email address
US20040202299A1 (en) * 2001-02-21 2004-10-14 Schwartz Lisa Miller Method and system for providing alternative media address information
US6944628B1 (en) * 1999-12-06 2005-09-13 Anthony Jacques Louis De Breed Method for electronically addressing of a person or organization
US7484088B2 (en) * 2000-03-17 2009-01-27 United States Postal Service Methods and systems for proofing identities using a certificate authority

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0531268A3 (en) 1991-09-03 1994-09-21 Ericsson Telefon Ab L M Business communication number
JP3328360B2 (en) * 1993-03-31 2002-09-24 三井化学株式会社 Thermoplastic elastomer
JPH0832618A (en) 1994-07-14 1996-02-02 Hitachi Ltd Voice mail system and voice mail exchange device
FR2760634B1 (en) * 1997-03-14 2002-10-11 Oreal SOLID TOPICAL AQUEOUS COMPOSITION HAVING THE APPEARANCE OF A GEL ALLOWING THE FORMATION OF A FILM DURING ITS APPLICATION
AU8050298A (en) 1997-06-17 1999-01-04 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for accessing and retrieving messages
FI114069B (en) 1998-06-24 2004-07-30 Elisa Oyj Method of controlling transmission in telecommunications
US6584490B1 (en) 1998-10-30 2003-06-24 3Com Corporation System and method for providing call-handling services on a data network telephone system
DE19858112A1 (en) 1998-12-16 2000-06-29 Siemens Ag Establishment of a telecommunication connection to a subscriber to whom several possible connection destinations are assigned
EP1142286B1 (en) 1999-01-08 2006-04-19 NetNumber.com, Inc. Method and apparatus for correlating a unique identifier, such as a pstn telephone number, to an internet address to enable communications over the internet
GB9901859D0 (en) 1999-01-29 1999-03-17 Ridgeway Systems & Software Lt Audio-video telephony
WO2000052902A1 (en) 1999-03-03 2000-09-08 Mediaring.Com Limited Universal internet voice addressing scheme
NO313728B1 (en) 1999-04-30 2002-11-18 Ericsson Telefon Ab L M Customization of services in telecommunications networks
AUPQ028599A0 (en) 1999-05-11 1999-06-03 Vista Group Pty Limited Telecommunications system
CA2376214A1 (en) 1999-06-08 2000-12-14 The Trustees Of Columbia University In The City Of New York Network telephony appliance and system for inter/intranet telephony
AU5933700A (en) 1999-07-13 2001-01-30 All Advantage. Com, Inc. Method and system for classifying users of an electronic network
ATA136499A (en) 1999-08-09 2001-10-15 Leuchs Gerhard Dr DEVICE FOR LIGHTING AN OBJECT WITH FOCUSED LIGHT
US7804815B1 (en) 1999-09-17 2010-09-28 Intertex Data Ab System and apparatus for telecommunication
US6577622B1 (en) 1999-09-27 2003-06-10 3Com Corp. System and method for using a portable information device to establish a conference call on a telephony network
US7934149B1 (en) 1999-09-30 2011-04-26 Instantis, Inc. Automated creation and maintenance of programs to process internet form related submissions
US6625274B1 (en) 1999-10-12 2003-09-23 Broadsoft, Inc. Computer system and method for providing services to users of communication systems using service entities, interface entities, and a service bus
WO2001031472A1 (en) 1999-10-22 2001-05-03 Telcordia Technologies, Inc. Method and system for host mobility management protocol
WO2001035594A2 (en) 1999-11-08 2001-05-17 British Telecommunications Public Limited Company Telecommunications control protocol processing
AU4714901A (en) 1999-12-08 2001-07-03 Mci Worldcom, Inc. Session initiation protocol servlet application programming interface
US6823364B1 (en) 1999-12-21 2004-11-23 Nortel Networks Limited Distribution of location information in IP networks by intelligent endpoints
US20020010759A1 (en) 1999-12-30 2002-01-24 Hitson Bruce L. System and method for multimedia content composition and distribution
AU2001261341A1 (en) 2000-05-10 2001-11-20 Plezecall, Inc. System for enabling one-click telephone connections
WO2002011408A2 (en) 2000-07-27 2002-02-07 Alcatel Usa Sourcing, L.P. Universal communications database system and method for integrated services
US7197120B2 (en) * 2000-12-22 2007-03-27 Openwave Systems Inc. Method and system for facilitating mediated communication
EP1368975A1 (en) * 2001-03-09 2003-12-10 Ayman L.L.C. Universal point of contact identifier system and method

Patent Citations (51)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4313035A (en) * 1980-01-18 1982-01-26 Bell Telephone Laboratories, Incorporated Method of providing person locator service
US4446294A (en) * 1982-07-30 1984-05-01 Imperial Chemical Industries Plc Aromatic etherketone/sulphone copolymers
US4677609A (en) * 1985-05-08 1987-06-30 American Telephone And Telegraph Company, At&T Bell Laboratories Semi-automated directory assistance systems
US4734931A (en) * 1986-03-21 1988-03-29 American Telephone And Telegraph Company And At&T Information Systems Inc. Integrated calling directory
US4837798A (en) * 1986-06-02 1989-06-06 American Telephone And Telegraph Company Communication system having unified messaging
US5555290A (en) * 1990-04-23 1996-09-10 Mci Communications Corporation Long distance telephone switching system with enhanced subscriber services
US5243645A (en) * 1990-11-01 1993-09-07 At&T Bell Laboratories Automatic system for forwarding of calls
US5239577A (en) * 1990-12-03 1993-08-24 Bell Communications Research, Inc. Network and method for providing cross-media connections
US5691973A (en) * 1991-06-28 1997-11-25 Telefonaktiebolaget Lm Ericsson Modular application software for telecommunications exchanges for providing all end user services traffic handling and charging requirements of an application type
US5452350A (en) * 1992-03-09 1995-09-19 Advantis Subscriber call routing processing system
US5812865A (en) * 1993-12-03 1998-09-22 Xerox Corporation Specifying and establishing communication data paths between particular media devices in multiple media device computing systems based on context of a user or users
US5533115A (en) * 1994-01-31 1996-07-02 Bell Communications Research, Inc. Network-based telephone system providing coordinated voice and data delivery
US5742668A (en) * 1994-09-19 1998-04-21 Bell Communications Research, Inc. Electronic massaging network
US5608786A (en) * 1994-12-23 1997-03-04 Alphanet Telecom Inc. Unified messaging system and method
US5633916A (en) * 1994-12-30 1997-05-27 Unisys Corporation Universal messaging service using single voice grade telephone line within a client/server architecture
US5805810A (en) * 1995-04-27 1998-09-08 Maxwell; Robert L. Apparatus and methods for converting an electronic mail to a postal mail at the receiving station
US5796813A (en) * 1995-06-30 1998-08-18 Siemens Telecom Networks Method for routing a call
US5742763A (en) * 1995-12-29 1998-04-21 At&T Corp. Universal message delivery system for handles identifying network presences
US5802510A (en) * 1995-12-29 1998-09-01 At&T Corp Universal directory service
US5826039A (en) * 1995-12-29 1998-10-20 Lucent Technologies Inc. Universal connection point for resources and communication unrelated to a physical endpoint
US5862325A (en) * 1996-02-29 1999-01-19 Intermind Corporation Computer-based communication system and method using metadata defining a control structure
US5850433A (en) * 1996-05-01 1998-12-15 Sprint Communication Co. L.P. System and method for providing an on-line directory service
US5826036A (en) * 1996-05-23 1998-10-20 Sharp Kabushiki Kaisha Information processing apparatus
US6275577B1 (en) * 1996-06-28 2001-08-14 Harris Corporation Call handling
US6072862A (en) * 1996-07-02 2000-06-06 Srinivasan; Thiru Adaptable method and system for message delivery
US6275490B1 (en) * 1996-08-21 2001-08-14 Netspeak Corporation Method and apparatus for establishing communications from browser application
US6385646B1 (en) * 1996-08-23 2002-05-07 At&T Corp. Method and system for establishing voice communications in an internet environment
US6343120B1 (en) * 1996-10-08 2002-01-29 At&T Wireless Services, Inc. Method and apparatus for providing a caller ID alias
US6243398B1 (en) * 1996-10-21 2001-06-05 Vocaltec Communications Ltd. System and method for personal multimedia communication over a packet switched network
US6343119B1 (en) * 1997-04-04 2002-01-29 International Business Machines Corporation Access to extended telephone services via the internet
US6014711A (en) * 1997-08-29 2000-01-11 Nortel Networks Corporation Apparatus and method for providing electronic mail relay translation services
US6337858B1 (en) * 1997-10-10 2002-01-08 Nortel Networks Limited Method and apparatus for originating voice calls from a data network
US6104799A (en) * 1997-10-24 2000-08-15 At&T Corp. Customer defined call setup
US6337902B1 (en) * 1997-12-10 2002-01-08 Alcatel Method for procuring instructions regarding a target subscriber in a telecommunication network and nodal points for this
US6215784B1 (en) * 1997-12-24 2001-04-10 Nortel Networks Limited Method and system for voice call completion using information retrieved from an open application on a computing machine
US20040030654A1 (en) * 1998-03-06 2004-02-12 Walker Jay S. System and method for facilitating account-based transactions
US6330308B1 (en) * 1998-04-09 2001-12-11 Bell Atlantic Network Services, Inc. Voice mail system for obtaining forwarding number information from directory assistance systems having speech recognition
US6173272B1 (en) * 1998-04-27 2001-01-09 The Clearing House Service Company L.L.C. Electronic funds transfer method and system and bill presentment method and system
US6259782B1 (en) * 1998-05-04 2001-07-10 Mci Communications Corporation One-number communications system and service integrating wireline/wireless telephone communications systems
US20020118800A1 (en) * 1998-08-27 2002-08-29 Maria Martinez Telecommunication systems and methods therefor
US6134548A (en) * 1998-11-19 2000-10-17 Ac Properties B.V. System, method and article of manufacture for advanced mobile bargain shopping
US6944628B1 (en) * 1999-12-06 2005-09-13 Anthony Jacques Louis De Breed Method for electronically addressing of a person or organization
US6373817B1 (en) * 1999-12-30 2002-04-16 At&T Corp. Chase me system
US6275575B1 (en) * 2000-01-12 2001-08-14 Right4Me.Com, Inc. Method and system for coordinating and initiating cross-platform telephone conferences
US7484088B2 (en) * 2000-03-17 2009-01-27 United States Postal Service Methods and systems for proofing identities using a certificate authority
US20020016174A1 (en) * 2000-05-03 2002-02-07 Gibson Eric J. Use of telephone numbers as domain names and as applied in portable electronic devices
US20020007421A1 (en) * 2000-05-05 2002-01-17 Thomas Dixon Universal address system
US20020042846A1 (en) * 2000-10-05 2002-04-11 Bottan Gustavo L. Personal support network
US6754317B1 (en) * 2000-10-30 2004-06-22 Agere Systems Inc. Telephony access using an email address
US20040202299A1 (en) * 2001-02-21 2004-10-14 Schwartz Lisa Miller Method and system for providing alternative media address information
US6625675B2 (en) * 2001-03-23 2003-09-23 International Business Machines Corporation Processor for determining physical lane skew order

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050215273A1 (en) * 2004-02-17 2005-09-29 Nec Corporation Push-to-talk over cellular system
US11178541B2 (en) * 2019-06-25 2021-11-16 T-Mobile Usa, Inc. Address retrieval systems and methods

Also Published As

Publication number Publication date
US20150181035A1 (en) 2015-06-25
US8971508B2 (en) 2015-03-03
US8548142B2 (en) 2013-10-01
JO2490B1 (en) 2009-10-05
US20140029739A1 (en) 2014-01-30
US10333997B2 (en) 2019-06-25
US20080144791A1 (en) 2008-06-19
EP1368975A1 (en) 2003-12-10
US20160164925A1 (en) 2016-06-09
US7379543B2 (en) 2008-05-27
US20020126817A1 (en) 2002-09-12
WO2002073984A1 (en) 2002-09-19

Similar Documents

Publication Publication Date Title
US10333997B2 (en) Universal point of contact identifier system and method
US6788769B1 (en) Internet directory system and method using telephone number based addressing
US6738462B1 (en) Unified communications automated personal name addressing
US20170180956A1 (en) Systems and methods of forwarding communication requests based on handling instructions in an internet protocol environment
US6823047B1 (en) Voice messaging system
CN1910883B (en) Instant messaging using telephone sets
US7092498B2 (en) Universal point of contact identifier system calling device and method
JP3636266B2 (en) Web phone dialer system
EP1973319A1 (en) Routing a call to an alternate endpoint different from the one identified by a calling party in accordance with the presence status of the called party
US20040086094A1 (en) Method of providing personal event notification during call setup
EP1284084B1 (en) Communication system
US20040096043A1 (en) Technique for assisting a user with information services at an information/call center
US20060029219A1 (en) Call agent apparatus, IP telephone apparatus and IP telephone system
KR100940977B1 (en) Wireless telephone system including voice over ip and pots
CN1846452B (en) Wireless telephone system including voice over IP and POTS
KR100738201B1 (en) Method for providing the information of user to the other user using address-book in mobile telecommunication network
US20050138129A1 (en) Methods and systems of responsive messaging
KR20010028687A (en) Operator PC Using Absent Call History Announcement Method In Switching System
JPH05308376A (en) Electronic mail address specifying method
KR20040067180A (en) Apparatus and method for providing call and voice recording service on pstn and mobile network
JPH07177236A (en) Real-time storage integration type speech communication device
JP2002135401A (en) Phone dialing system by mail address

Legal Events

Date Code Title Description
AS Assignment

Owner name: AYMAN, LLC, MARYLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HARIRI, AYMAN;BIRNBAUM, SCOTT D.;REEL/FRAME:020556/0116

Effective date: 20010604

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION