IP Library Granted Patent US 7,062,535
Granted Patent B1
US 7,062,535 · App. 09/661,499 · Granted Jun 13, 2006

Individual XML message processing platform

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,062,535
App. No.
09/661,499
Granted
Jun 13, 2006
Kind
B1
Abstract

A communications platform (Centerpost) is disclosed containing a message processing platform along with an XML message format (SmartMessage) which provides for the reception, organization, summarization, filing, storage, synthesis, routing, formatting, and intelligent processing of XML-based electronic messages and SMTP electronic mail from corporations and other senders to fully integrate individuals' existing e-mail boxes, cellular telephones, paging equipment, facsimile machines, wireless and wired telephones, and other devices. The Centerpost platform utilizes a nickname-based routing to enable device specific sending without knowledge of the specific device address. The Centerpost platform provides sender-defined information folios, which enable synthesized filing, viewing and storage of all received SmartMessages, and the platform allows semi-private access control for the user, which allows access by others. The platform also utilizes a web-based user interface, which greatly simplifies the user's viewing, control and configuration of the individual user's particular platform. The Centerpost SmartDelivery platform also allows for corporations to utilize the Centerpost functions for its customers without requiring those customers to have a Centerpost account. The platform also provides for Amateur Informants, which facilitate the use of the Centerpost system for individuals and small businesses. The platform also provides for 2-way XML messages, a Centerpost subscriber web page, an endpoint wallet, which allows subscribers to easily transfer their endpoint information, a message based endpoint configuration, which automatically sets up a new messaging device as an endpoint.

Claims (52)

1. A communications platform that enables users to receive electronic messages from corporations and others comprising a nickname-based routing system, said nickname-based routing system comprising logic for:

receiving an electronic message;

parsing the electronic message to determine a designation for a user;

parsing the electronic message to determine a nickname of an endpoint designated in the electronic message, the nickname of the endpoint being distinct from the designation for the user, the nickname for the endpoint being selected from a plurality of nicknames and being dynamically dependent on the endpoint selected;

accessing a database, based on the determined designation of the user and the determined nickname of the endpoint, to determine an address and type of an endpoint to route the electronic message to based on the nickname, the database correlating the designation of the user to the plurality of nicknames of endpoints the database correlating the plurality of nicknames to a plurality of addresses;

determining a type of endpoint;

formatting at least a portion of the electronic message based on the determined type of endpoint; and

sending at least a portion of the formatted message to the determined address of the endpoint,

where the nickname for the endpoint eliminates a sender to memorize the plurality of addresses for the plurality of endpoints.

2. The communications platform in claim 1 , wherein said endpoint comprises an electronic mail box, a wired or wireless telephone, a facsimile machine, a paging device, or a personal digital assistant.

3. The communications platform in claim 2 , wherein said nickname-based routing system comprises at least one address containing a nickname.

4. The communications platform in claim 3 , wherein said nickname comprises information pertaining to said user's name and endpoint.

5. The communications platform in claim 4 , wherein said nickname further comprises information pertaining to said endpoint.

6. The communications platform in claim 5 , wherein said information pertaining to said endpoint comprises a telephone number, a facsimile number, a pager number, an electronic address or a resident address.

7. The communications platform in claim 1 , wherein the electronic message is addressed to the communications platform.

8. The communications platform in claim 1 , wherein the designation for the user comprises a user's name.

9. The communications platform in claim 1 , wherein the nickname is selected from the group consisting of phone and fax.

10. The communications platform in claim 1 , wherein the nickname was previously designated by the user.

11. The communications platform in claim 1 , wherein determining a type of endpoint to route the electronic message to is further based on the designation for the user.

12. The communications platform in claim 1 , wherein determining an address of the endpoint comprises accessing the database to determine the address of the endpoint based on the nickname and based on the designation for the user.

13. The communications platform in claim 1 , wherein the nickname for the endpoint is selected from a plurality of nicknames.

14. The communications platform in claim 13 , wherein the designation for the user is non-changeable for a specific user.

15. The communications platform in claim 14 , wherein format for the electronic message comprises the designation of the user, a connector, the nickname, and the address of the communication platform.

16. The communications platform in claim 1 , wherein the electronic message includes an @ symbol, and wherein the nickname of the endpoint is prior to the @ symbol in the electronic message.

17. The communications platform in claim 16 , wherein the designation of the user is prior to the @ symbol in the electronic message.

18. The communications platform in claim 16 , wherein the nickname of the endpoint is prior to the @ symbol in the electronic message.

19. The communications platform in claim 1 , wherein the nickname of the endpoint is not a domain name.

20. The communications platform in claim 1 , wherein the electronic message comprises a domain name of the communications platform, the domain name for the communications platform being separate from the nickname of the endpoint.

21. The communications platform in claim 20 , wherein the nickname for the endpoint is not used to route the electronic message to the domain name for the communications platform.

22. The communications platform in claim 1 , wherein the nickname for the endpoint is not an address.

23. The communications platform in claim 1 , wherein a plurality of users have user designations; and

wherein the database correlates, for each of the user designations, an address for an endpoint associated with the nickname, with the addresses of the endpoints being different for each of the user designations.

24. A communications platform that enables users to receive electronic messages from corporations and others comprising a nickname-based routing system, said nickname-based routing system comprising logic for:

receiving an electronic message addressed to the communications platform with fields for a nickname of an endpoint and an address of the endpoint the nickname of the endpoint being selected from a plurality of nicknames and being dynamically dependent on the endpoint selected;

parsing the electronic message to determine the nickname of the endpoint designated in the electronic message;

parsing the electronic message for the address of the endpoint designated in the electronic message;

accessing a database to determine type of the endpoint to route the electronic message to based on the nickname the database correlating the nickname to a type of endpoint;

formatting at least a portion of the electronic message based on the determined type of endpoint; and

sending at least a portion of the formatted message to the determined address of the endpoint,

where sending the electronic message using the nickname of the endpoint and the address of the endpoint enables a sender to dynamically define the nickname in the electronic message.

25. The communications platform in claim 24 , wherein the address of the communications platform comprises an internet address.

26. The communications platform in claim 25 , wherein the address of the communications platform comprises a .com address.

27. The communications platform in claim 25 , wherein the address of the endpoint comprises a telephone number.

28. The communications platform in claim 24 , wherein the electronic message comprises a field for a designation of a user; and

further comprising parsing the electronic message to determine the designation for a user; and

wherein sending at least a portion of the formatted message to the determined address of the endpoint comprises sending at least a portion of the formatted message to the determined address of the endpoint on behalf of the determined designation of the user.

29. The communications platform in claim 24 , wherein the address comprises a numeric address.

30. The communications platform in claim 24 , wherein the electronic message includes an @ symbol, and wherein the address of the endpoint is prior to the @ symbol in the electronic message.

31. The communications platform in claim 24 , wherein the nickname of the endpoint is not a domain name.

32. The communications platform in claim 24 , wherein the electronic message comprises a domain name of the communications platform, the domain name for the communications platform being separate from the nickname of the endpoint.

33. The communications platform in claim 32 , wherein the nickname for the endpoint is not used to route the electronic message to the domain name for the communications platform.

34. The communications platform in claim 24 , wherein the nickname for the endpoint is not an address.

Assignments (6)
OMNIBUS ASSIGNMENT OF SECURITY INTEREST IN INTELLECTUAL PROPERTY Recorded Nov 25, 2024
From: UBS AG, STAMFORD BRANCH (AS SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH IN ITS CAPACITY AS COLLATERAL AGENT)
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS THE SUCCESSOR COLLATERAL AGENT
Reel/Frame 069438/0775 →
RELEASE OF SECURITY INTEREST Recorded Dec 20, 2022
From: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS SUCCESSOR TO WACHOVIA BANK, NATIONAL ASSOCIATION
To: INTERCALL, INC.; INTRADO INC.; WEST CORPORATION; WEST DIRECT, LLC; WEST NOTIFICATIONS GROUP, INC.
Reel/Frame 062201/0960 →
RELEASE OF SECURITY INTEREST Recorded May 1, 2018
From: U.S. BANK NATIONAL ASSOCIATION
To: WEST CORPORATION; WEST INTERACTIVE SERVICES CORPORATION; WEST SAFETY SERVICES, INC.; WEST UNIFIED COMMUNICATIONS SERVICES, INC.; RELIANCE COMMUNICATIONS, LLC
Reel/Frame 046046/0547 →
NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS (FIRST LIEN) Recorded Oct 10, 2017
From: WEST INTERACTIVE SERVICES CORPORATION
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 044169/0017 →
SECURITY INTEREST Recorded Jun 20, 2016
From: WEST CORPORATION; WEST INTERACTIVE SERVICES CORPORATION; WEST SAFETY SERVICES, INC.; WEST UNIFIED COMMUNICATIONS SERVICES, INC.; RELIANCE COMMUNICATIONS, LLC
To: U.S. BANK NATIONAL ASSOCIATION
Reel/Frame 039093/0944 →
SECURITY AGREEMENT Recorded Apr 16, 2010
From: INTERCALL, INC.; INTRADO, INC.; WEST CORPORATION; WEST DIRECT, LLC; WEST NOTIFICATIONS GROUP, INC.
To: WACHOVIA BANK, NATIONAL ASSOCIATION, AS ADMINISTRATIVE AGENT
Reel/Frame 024244/0216 →