Asynchronous event notification

• US 8,203,964 B2
• Filed: 05/08/2006
• Issued: 06/19/2012
• Est. Priority Date: 05/06/2005
• Status: Expired due to Fees

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Broadcom Corporation (Broadcom, Inc.)
• Inventors: Talayco, Daniel, Baird, Brian
• Primary Examiner(s): RENNER, BRANDON M
• Application Number:
  US11/429,287
• Publication Number:
  US 20060271676A1
• Time in Patent Office: 2,234 Days
• Field of Search: None
• US Class Current: 370/254
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

The invention includes a method system and apparatus for an asynchronous event notification. In the event that a system-wide application requires notification of an asynchronous event that occurs in a remote device within the communications system, the event is locally detected and the necessary information is forwarded to the application.

Claims

1. A method for asynchronous event notification within a communication system, comprising:

creating a first list at a local processor that controls a local network stack, the first list identifying a first local device in the local network stack and a remote event about which the first local device wants to be notified when the remote event occurs on a remote network stack;

sending a registration request to a remote processor that controls the remote network stack, the registration request identifying the local processor and the remote event;

receiving at the local processor a registration request from a second remote processor that controls a second remote network stack, the registration request identifying the second remote processor and a local event about which the second remote processor wants to be notified when the local event occurs on the local network stack; and

creating a second list at the local processor, the second list identifying the local event and the second remote processor to notify when the local event occurs.

2. The method of claim 1, further comprising:

receiving a message from the remote processor that the remote event has occurred;

determining from the first list the identify of the first local device that wants to be notified when the remote event occurs; and

sending a notification message to the first local device that the remote event has occurred.

3. The method of claim 1, wherein the remote processor and the second remote processor are the same processor, and the remote network stack and the second remote network stack are the same network stack.

4. The method of claim 1, further comprising:

receiving notification at the local processor that the local event has occurred;

determining from the second list the identity of the second remote processor to be notified when the local event has occurred; and

sending the second remote processor a notification that the local event has occurred.

5. The method of claim 4, wherein the notification received at the local processor that the local event has occurred is an interrupt message from a second local device on the local network stack.

6. The method of claim 5, wherein the first local device and the second local device are the same device.

7. A network stack, comprising:

at least one network device;

a processor that controls the at least one network device; and

a memory for storing instructions that when executed by the processor causes the processor to;

create a first list that identifies the at least one network device and a remote event about which the at least one network device wants to be notified when the remote event occurs on a remote network stack;

send a registration request to a remote processor that controls the remote network stack, the registration request identifying the processor and the remote event;

receive a registration request from a second remote processor that controls a second remote network stack, the registration request identifying the second remote processor and a local event about which the second remote processor wants to be notified when the local event occurs on the network stack; and

create a second list that identifies the local event and the second remote processor to notify when the local event occurs.

8. The network stack of claim 7, wherein the memory further stores instructions that when executed by the processor causes the processor to:

receive a message from the remote processor that the remote event has occurred;

determine from the first list the identify of the at least one network device that wants to be notified when the remote event occurs; and

send a notification message to the at least one network device that the remote event has occurred.

9. The network stack of claim 7, wherein the remote processor and the second remote processor are the same processor, and the remote network stack and the second remote network stack are the same network stack.

10. The network stack of claim 7, wherein the memory further stores instructions that when executed by the processor causes the processor to:

receive notification that the local event has occurred;

determine from the second list the identity of the second remote processor to be notified when the local event has occurred; and

send the second remote processor a notification that the local event has occurred.

11. The network stack of claim 10, wherein the notification received at the processor that the local event has occurred is an interrupt message from a second device on the network stack.

12. The network stack of claim 11, wherein the at least one network device and the second device are the same device.

13. An apparatus, comprising:

a processor; and

a memory for storing instructions that when executed by the processor causes the processor to;

create a first list that identifies at least one network device and a remote event about which the at least one network device wants to be notified when the remote event occurs on a remote network stack;

send a registration request to a remote processor that controls the remote network stack, the registration request identifying the processor and the remote event;

receive a registration request from a second remote processor that controls a second remote network stack, the registration request identifying the second remote processor and a local event about which the second remote processor wants to be notified when the local event occurs on the network stack; and

create a second list that identifies the local event and the second remote processor to notify when the local event occurs.

14. The apparatus of claim 13, wherein the memory further stores instructions that when executed by the processor causes the processor to:

receive a message from the remote processor that the remote event has occurred;

determine from the first list the identify of the at least one network device that wants to be notified when the remote event occurs; and

send a notification message to the at least one network device that the remote event has occurred.

15. The apparatus of claim 13, wherein the remote processor and the second remote processor are the same processor, and the remote network stack and the second remote network stack are the same network stack.

16. The apparatus of claim 13, wherein the memory further stores instructions that when executed by the processor causes the processor to:

receive notification that the local event has occurred;

determine from the second list the identity of the second remote processor to be notified when the local event has occurred; and

send the second remote processor a notification that the local event has occurred.

17. The apparatus of claim 16, wherein the notification received at the processor that the local event has occurred is an interrupt message from a second device on the network stack.

18. The apparatus of claim 17, wherein the at least one network device and the second device are the same device.