Address defined session management over stateless communications channels

• US 20020080822A1
• Filed: 12/22/2000
• Published: 06/27/2002
• Est. Priority Date: 12/22/2000
• Status: Abandoned Application

• Current Assignee: Brown & Michaels PC, Joshua A. Cooper
• Original Assignee: Brown & Michaels PC, Joshua A. Cooper
• Inventors: Brown, Michael K., Cooper, Joshua A.
• Application Number:
  US09/748,049
• Publication Number:
  US 20020080822A1
• Time in Patent Office: Days
• US Class Current: 370/475
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 69/327 in the session layer [OSI layer 5]

Abstract

Address defined session management permits data interchange across a stateless channel utilizing the existing addressing protocol in a particular communications channel without altering the body of the message itself. By establishing a session identifier, applications and/or users can engage in interactive data communications through any stateless communications channel with any corresponding application that requires interactive communication.

Claims

1. A method for managing a transmission session over a stateless communication channel, comprising the steps of:

a. permitting an application to originate a message to a specific terminating address;

b. assigning an originating address to the application from a pool of originating addresses;

c. including the terminating address and the originating address in the application message for defining a managed transmission message; and

d. transmitting the managed transmission message.

2. The method of claim 1, wherein the originating address is randomly assigned to the application.

4. The method of claim 1, wherein the originating address is static throughout the session.

5. The method of claim 1, further comprising the step of replying to the managed transmission message from the transmission terminal by using the included terminating address and originating address for identifying the message originator and specifically identifying the reply transmitter to the originator.

6. The method of claim 1, wherein the application is selected from a plurality of defined applications.

7. The method of claim 6, wherein the plurality of defined applications is provided in an accessible database.

8. The method of claim 1, wherein the application is selected from a plurality of defined applications and wherein the selection of the application initiates the selection of the originating address.

9. The method of claim 8, wherein the plurality of defined applications is provided in an accessible database.

10. The method of claim 8, wherein the originating address is embedded in the selected application.

11. The method of claim 8, wherein the originating address is selected from a plurality of defined originating addresses.

12. The method of claim 11, wherein the plurality of defined originating address is provided in an accessible database.

13. The method of claim 11, wherein the selected originating address is randomly selected and associated with a selected application.

14. The method of claim 8, wherein the originating address is embedded in the selected application message for defining a managed transmission message.

15. The method of claim 1, wherein a session is defined by the application identification and a terminating address.

16. The method of claim 15, wherein the session is further defined by the assignment of an originating address.

17. The method of claim 6, wherein a reply message is transmitted to a selected application by comparing the originating address and the terminating address in the application message.

18. The method of claim 1, including the step of transmitting the managed transmission message via a stateless communication channel.

19. The method of claim 1, including the step of transmitting the managed transmission message via a wireless telephonic system.

20. The method of claim 19, wherein the telephonic system comprises a global system for mobility (GSM).

21. The method of claim 19, wherein the telephonic system comprises a public switch telephonic network (PSTN).

22. The method of claim 19, wherein the telephonic system comprises a public land mobile network (PLMN).

23. The method of claim 1, including the step of transmitting the managed transmission message via a personal area network.

24. The method of claim 1, including the step of transmitting the managed transmission system via a pager network.

25. The method of claim 1, including the step of transmitting the managed transmission message via a local area network.

26. The method of claim 1, including the step of transmitting the managed message via a wide area network.

27. The method of claim 1, including the step of transmitting the managed message via the Internet.

28. The method of claim 1, further including a mobile telephone as the transmission terminal.

29. The method of claim 1, further including the step of assigning a session identifier associated with the managed transmission message and unique to the selected terminating address and application whereby a reply message may be matched to a managed transmission message.

30. The method of claim 29, further including the originating address as a segment of the session identifier.

31. The method of claim 30, further including the step of routing a matched reply message to the application.

32. The method of claim 1, wherein the transmitting step includes initially transmitting the managed transmission message from an originating application base to a terminating terminal designated by the terminating address.

33. The method of claim 1, wherein the transmitting step includes initially transmitting the managed transmission message from a terminating terminal to an originating application base.

34. The method of claim 32, wherein the terminating terminal is another originating application destination.

35. The application of claim 33, wherein the terminating terminal is another originating application destination.

36. The method of claim 29, wherein the application is selected from a plurality of defined applications and wherein the selection of the application initiates the selection of the originating address, and wherein the origination address remains static throughout a session.

37. The method of claim 36, wherein the selection of the originating address is from the plurality of originating addresses is random.

38. The method of claim 29, wherein the application is selected from a plurality of defined applications and wherein the selection of the application initiates the selection of the originating address, and wherein the origination address is dynamic throughout a session.

39. The method of claim 38, wherein the selection of the originating address is from the plurality of originating addresses is random.

40. The method of claim 1, wherein the application and the user are only identifiable through an anonymous proxy.

41. The method of claim 40, wherein the application is an anonymous payment system.

3. The method of claim one, wherein the originating address is dynamically assigned and changes throughout the session.