Protocol driver application programming interface for operating systems

• US 20030145129A1
• Filed: 01/31/2002
• Published: 07/31/2003
• Est. Priority Date: 01/31/2002
• Status: Abandoned Application

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Nagalkar, Dhananjay A.
• Application Number:
  US10/062,863
• Publication Number:
  US 20030145129A1
• Time in Patent Office: Days
• US Class Current: 719/321
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/321 Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers

Abstract

A method and apparatus is provided in which communication between an application and protocol drivers to transmit data to and from a network interface is performed using a standardized protocol driver application programming interface. The interface includes functions having one or more parameters called from an application to cause the protocol driver to drive a protocol service engine (PSE) coupled to the network interface, the PSE being capable of operating a communication channel between the application and the network interface. The interface also includes messages conveying information from the protocol driver to the application about the operation of the communication channel and the data transmitted therein.

Claims

1. A method of communication between an application and a protocol driver to facilitate the transmission of data to a network interface comprising:

calling a function having a parameter from an application to cause a protocol driver to drive a protocol service engine (PSE) coupled to a network interface, the PSE being capable of operating a communication channel for transmitting a data between the application and the network interface; and

sending a message from the protocol driver to the application conveying a result triggered by calling the function.

2. The method of claim 1, wherein the result conveyed in the message is about the data transmitted between the application and the network interface.

3. The method of claim 1, further comprising calling the function from an operating system kernal to cause the protocol driver to drive the PSE to discover a device that is supported by the protocol driver and, if discovered, again calling the function to initialize a messaging and an interrupt-handling interface between the device and the operating system kernal.

4. The method of claim 3, further comprising calling the function from the operating system kernal to cause the protocol driver to drive the PSE to configure the device according to the function'"'"'s parameter value.

5. The method of claim 1, wherein calling the function from the application causes the protocol driver to drive the PSE to initiate the communication channel according to the function'"'"'s parameter value.

6. The method of claim 1, wherein calling the function from the application causes the protocol driver to drive the PSE to allocate a bandwidth for the communication channel according to the function'"'"'s parameter value.

7. The method of claim 1, wherein calling the function from the application causes the protocol driver to drive the PSE to terminate the communication channel according to the function'"'"'s parameter value.

8. The method of claim 1, wherein calling the function from the application causes the protocol driver to drive the PSE to activate the communication channel according to the function'"'"'s parameter value.

9. The method of claim 1, wherein calling the function from the application causes the protocol driver to drive the PSE to transmit a data frame across the communication channel according to function'"'"'s parameter value.

10. A method of operating a protocol service engine (PSE), the PSE having a standard interface comprising a function having at least one parameter, the parameter containing a pointer to a data structure associated with the function, wherein invoking the function controls the PSE to process a data stream over a channel between an application and a network.

11. The method of claim 10 wherein the function comprises one of:

identifying a device associated with the PSE having at least one device attribute as specified in the data structure;

configuring the identified device based on a device configuration as specified in the data structure;

allocating the channel on the identified device and at least one timeslot on the channel based on at least one channel attribute as specified in the data structure;

initializing the channel based on a channel configuration as specified in the data structure; and

setting a loopback configuration on the channel based on a loopback type specified in the data structure.

12. The method of claim 11, wherein the function further comprises one of:

activating the channel to transmit and receive the data stream; and

transmitting a frame of the data stream to a transmit queue for the channel.

13. The method of claim 11, wherein the function further comprises one of:

deactivating the channel to suspend transmitting and receiving the data stream; and

terminating the channel to free the channel and the at least one timeslot.

14. The method of claim 11, wherein the function further comprises one of:

returning a state of the channel, the state being placed in the data structure;

resetting the state of the channel to null;

retrieving a statistics counter value of the channel, the statistics counter value being placed in the data structure;

resetting the statistics counter value of the channel;

starting a trace on the channel, a result of the trace being placed in a trace buffer as specified in the data structure; and

stopping the trace on the channel.

15. The method of claim 11, wherein the function further comprises one of:

disabling an inbound data stream on the channel;

enabling the inbound data stream on the channel;

disabling an outbound data stream on the channel; and

enabling an outbound data stream on the channel.

16. The method of claim 10, further comprising a message having at least one message parameter, the message parameter containing a pointer to a message data structure associated with the message.

17. The method of claim 16, wherein the message comprises one of:

acknowledging that a frame of the data stream on the channel has been transmitted;

acknowledging that the frame of the data stream on the channel has been received;

indicating that an error has occurred on the channel, the error specified in the message data structure; and

indicating that a trace buffer containing the result of a trace on the channel has been filled.

18. An apparatus to process a data stream on a network comprising:

an application;

a protocol driver;

a protocol service engine (PSE); and

a protocol driver application programming interface (API) coupled to the PSE, wherein the API communicates with the application and the protocol driver using a standard interface to cause the PSE to process a data stream over a channel between the application and a network, the standard interface comprising a function having at least one parameter, the parameter containing a pointer to a data structure associated with the function.

19. The apparatus of claim 18 wherein the function is capable of identifying a device associated with the PSE having at least one device attribute as specified in the data structure.

20. The apparatus of claim 18 wherein the function is capable of configuring a device based on a device configuration as specified in the data structure.

21. The apparatus of claim 18 wherein the function is capable of allocating the channel on a device and at least one timeslot on the channel based on at least one channel attribute as specified in the data structure.

22. The apparatus of claim 18 wherein the function is capable of initializing the channel based on a channel configuration as specified in the data structure.

23. The apparatus of claim 18 wherein the function is capable of setting a loopback configuration on the channel based on a loopback type specified in the data structure.

24. The apparatus of claim 18 wherein the function is capable of activating the channel to transmit and receive the data stream.

25. The apparatus of claim 18 wherein the function is capable of causing the channel to transmit a frame of the data stream to a transmit queue.

26. The apparatus of claim 18 wherein the function is capable of deactivating the channel to suspend transmitting and receiving the data stream.

27. The apparatus of claim 18 wherein the function is capable of terminating the channel to free the channel and to free any timeslot that was allocated for the channel.

28. The apparatus of claim 18 wherein the function is capable of returning a state of the channel, the state being placed in the data structure.

29. The apparatus of claim 18 wherein the function is capable of resetting a state of the channel to null.

30. The apparatus of claim 18 wherein the function is capable of retrieving a statistics counter value of the channel, the statistics counter value being placed in the data structure.

31. The apparatus of claim 18 wherein the function is capable of resetting the statistics counter value of the channel.

32. The apparatus of claim 18 wherein the function is capable of starting a trace on the channel, a result of the trace being placed in a trace buffer as specified in the data structure.

33. The apparatus of claim 18 wherein the function is capable of stopping a trace on the channel.

34. The apparatus of claim 18 wherein the function is capable of disabling an inbound data stream on the channel.

35. The apparatus of claim 18 wherein the function is capable of enabling the inbound data stream on the channel.

36. The apparatus of claim 18 wherein the function is capable of disabling an outbound data stream on the channel.

37. The apparatus of claim 18 wherein the function is capable of enabling an outbound data stream on the channel.

38. The apparatus of claim 18, wherein the standard interface further comprises a message having at least one message parameter, the message parameter containing a pointer to a message data structure associated with the message.

39. The apparatus of claim 38 wherein the message is capable of conveying an acknowledgement that a frame of the data stream on the channel has been transmitted.

40. The apparatus of claim 38 wherein the message is capable of conveying an acknowledgement that a frame of the data stream on the channel has been received.

41. The apparatus of claim 38 wherein the message is capable of conveying an Indication that an error has occurred on the channel, the error specified in the message data structure.

42. The apparatus of claim 38 wherein the message is capable of conveying an indication that a trace buffer containing the result of a trace on the channel has been filled.

43. An article of manufacture comprising a machine-accessible medium including data that, when accessed by a machine, cause the machine to:

generate a function call, the function call having a parameter containing a pointer to a data structure associated with the function call, wherein the function call is capable of causing the protocol driver to drive a protocol service engine (PSE) coupled to a network interface, the PSE being capable of operating a communication channel between an application and the network interface; and

generate a message, the message having a message parameter containing a pointer to a message data structure associated with the message, the message capable of being sent from the protocol driver to the application to convey information regarding the operation of the communication channel.

44. The article of manufacture of claim 43, wherein the generated function call further causes the machine to:

identify a device associated with the PSE having at least one device attribute as specified in the data structure;

configure the identified device based on a device configuration as specified in the data structure;

allocate the channel on the identified device and at least one timeslot on the channel based on at least one channel attribute as specified in the data structure;

initialize the channel based on a channel configuration as specified in the data structure; and

set a loopback configuration on the channel based on a loopback type specified in the data structure.

45. The article of manufacture of claim 43, wherein the generated function call further causes the machine to:

activate the channel to transmit and receive the data stream; and

transmit a frame of the data stream to a transmit queue for the channel.

46. The article of manufacture of claim 43, wherein the generated function call further causes the machine to:

deactivate the channel to suspend transmitting and receiving the data stream; and

terminate the channel to free the channel and the at least one timeslot.

47. The article of manufacture of claim 43, wherein the generated function call further causes the machine to:

return a state of the channel, the state being placed in the data structure;

reset the state of the channel to null;

retrieve a statistics counter value of the channel, the statistics counter value being placed in the data structure;

reset the statistics counter value of the channel;

start a trace on the channel, a result of the trace being placed in a trace buffer as specified in the data structure; and

stop the trace on the channel.

48. The article of manufacture of claim 43, wherein the generated function call further causes the machine to:

disable an inbound data stream on the channel;

enable the inbound data stream on the channel;

disable an outbound data stream on the channel; and

enable an outbound data stream on the channel.

49. The article of manufacture of claim 43, wherein the generated message further causes the machine to convey:

an acknowledgement that a frame of the data stream on the channel has been transmitted;

an acknowledgement that the frame of the data stream on the channel has been received;

an indication that an error has occurred on the channel, the error specified in the message data structure; and

an indication that a trace buffer containing the result of a trace on the channel has been filled.