Universal connection point for resources and communication unrelated to a physical endpoint

• US 5,826,039 A
• Filed: 12/29/1995
• Issued: 10/20/1998
• Est. Priority Date: 12/29/1995
• Status: Expired due to Term

• Current Assignee: Alcatel-Lucent USA, Inc. (Nokia Corporation)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Jones, Mark Alan
• Primary Examiner(s): Rinehart, Mark H.
• Application Number:
  US08/580,670
• Time in Patent Office: 1,026 Days
• Field of Search: 395/200.04, 395/200.12, 395/200.14, 395/200.18, 395/182.02, 395/200.36, 395/200.55, 395/200.58, 395/200.57, 395/200.75 , 395/200.76, 395/200.67, 707/6
• US Class Current: 709/206
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 61/4547 for personal communications, i.e. using a personal identifier
• CPC Class Codes: H04L 61/4594 Address books, i.e. directories containing contact information about correspondents telephone directories in user terminals H04M1/27453
• CPC Class Codes: H04M 2201/60 Medium conversion
• CPC Class Codes: H04M 3/4931 Directory assistance systems
• CPC Class Codes: H04M 3/5307 for recording messages comprising any combination of audio and non-audio components
• CPC Class Codes: Y10S 707/99936 Pattern matching access

Abstract

A communication network system provides a network presence for an entity, the network presence being identified by handle information relating to the entity, the handle information being unrelated to a physical endpoint. Attributes of the entity are associated with the handle information. The handle is a source of vendor services to the entity, and may be a source of services from the entity to others.

Claims

1. A communications system comprising:

means for providing a network presence for an entity, wherein said network presence is identified by a handle unrelated to a physical endpoint, said handle being unique relative to handles for other entities at any point in time, said handle having associated attributes; and

means for resolving a declarative query specifying at least one attribute to generate a set of handles including at least said handle of said entity, said declarative query provided to identify entities.

2. The system of claim 1, wherein said handle is other than a telephone number.

3. The system of claim 1, wherein said handle includes at least some alphabetic information.

4. The system of claim 1 wherein said entity is a person, group, organization, department, use group or functional role.

5. The system of claim 1, wherein said entity has multiple network presences.

6. The system of claim 1, wherein a sponsor is associated with said network presence, and the sponsor is other than the entity.

7. The system of claim 1, wherein said handle is associated with said entity while said network presence exists.

8. The system of claim 1, wherein said network presence provides a vendor service to said entity.

9. The system of claim 8, wherein said vendor service is a software agent.

10. The system of claim 1, wherein said entity provides a vendor service to other entities through said network presence.

11. The system of claim 1, wherein said attributes includes entity related attributes, and said handle is based on one of the entity related attributes.

12. The system of claim 1, wherein one of the attributes indicates a preferred media format for receiving messages.

13. The system of claim 1, further comprising directory means for storing said attributes associated with said handle.

14. The system of claim 13, wherein said directory means provides at least one of said attributes in response to a directory query including said handle.

15. The system of claim 14, wherein said attributes have a hierarchical relationship.

16. The system of claim 15, wherein said directory query includes information dependent on said hierarchical relationship.

17. The system of claim 13, wherein said directory means provides said handle in response to a directory query including at least one of said attributes.

18. The system of claim 17, wherein the provided handle is automatically transferred to a vendor service.

19. The system of claim 18, wherein said vendor service is a message composition service.

20. The system of claim 13, further comprising means for automatically administering changes in attributes on the basis of entity preferences.

21. The system of claim 13, wherein an address book is associated with said entity, and said directory means is operative to provide selected attributes for handles indicated by said address book.

22. The system of claim 21, wherein said address book includes information provided by said entity for at least one of the indicated handles.

23. The system of claim 21, wherein said address book includes temporal information for at least one of the indicated handles.

24. The system of claim 13, wherein said attributes are associated with authenticity information.

25. The system of claim 13, wherein said attributes are associated with security indication information indicating whether the associated attribute is public or non-public.

26. The system of claim 25, wherein said directory means is operative to provide only those of said attributes associated with a public security indication in response to a directory query including said handle.

27. The system of claim 25, wherein said directory means is operative to accept a directory query from a query source, said directory query including at least one of said attributes having a non-public security indication, and to automatically transfer the handle to a vendor service without disclosing the handle to said query source.

28. The system of claim 27, wherein said vendor service is a message composition service.

29. The system of claim 1, further comprising delivery means for delivering a message from a sender to said network presence using said handle as an address.

30. The system of claim 29, wherein said message is in a multimedia format.

31. The system of claim 29, wherein identifying information for said sender is omitted from said message.

32. The system of claim 29, wherein said delivery means is operative to append non-repudiable sender information to said message.

33. The system of claim 29, wherein said delivery means is operative to accept selected attributes from said sender as an address, and to replace the selected attributes with the handle as said address without disclosing the handle to said sender.

34. The system of claim 29, wherein said attributes include a processing preference for a message delivered to said network presence, and further comprising a software agent for processing the delivered message in accordance with said processing preference.

35. The system of claim 34, wherein said processing preference is a preferred media format, and said software agent is operative to convert a media format of the delivered message to the preferred media format.

36. The system of claim 34, wherein said processing preference specifies one of a notifying action, a forwarding action, a deleting action and a storing action, and said software agent is operative to perform the action specified by said processing preference when said message is delivered to said network presence.

37. The system of claim 1, further comprising storage means for storing a message from a sender to said network presence, said message having said handle as an address.

38. The system of claim 37, wherein said message has properties, and said storage means is operative to accept a query including a specified property, and to generate a mailbox including said message when one of the message properties is the specified property.

39. The system of claim 38, wherein said query is a one-time query.

40. The system of claim 38, wherein said query is a persistent query.

41. The system of claim 37, wherein said storage means is operative to obtain proxy objects from a proxy storage means.

42. The system of claim 37, wherein said attributes include a processing preference for the stored message to said network presence, and further comprising a software agent for processing said stored message in accordance with said processing preference.

43. The system of claim 42, wherein said processing preference is a preferred media format, and said software agent is operative to convert a media format of said stored message to the preferred media format.

44. The system of claim 42, wherein said processing preference specifies one of a notifying action, a deleting action and an archiving action, and said software agent is operative to perform the action specified by said processing preference on said stored message.

45. The system of claim 37, further comprising means for automatically generating a summary of said message.

46. The system of claim 45, further comprising means for automatically appending the generated summary to said message.

47. A communications system comprising:

means for providing a network presence for an entity, wherein said network presence is identified by a handle unrelated to a physical endpoint, said handle being unique relative to handles for other entities at any point in time, said handle having associated attributes; and

means for delivering a message having a generation modality determined by a generator of the message to said entity in a delivery modality specified by said entity and associated with said network presence, the delivery modality being unknown to the generator of the message, the message including a declarative query for identifying entities to receive the message, the declarative query specifying at least one attribute.