Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

A version of this page is also available for

4/8/2010

This enumeration specifies the types of messaging events conveyed through messaging queues.

The RIL driver and the packet driver (radio stack) each generate events.

The term event does not refer to the event system used within Windows Embedded CE; rather, it refers to the specific events in the messaging queues.

Syntax


// As defined in Rilndisoem1.h typedef enum oemndiseventtype_tag { OEM_NDIS_RX_PACKET, OEM_NDIS_TX_PACKET_COMPLETE, OEM_NDIS_XOFF, OEM_NDIS_XON, OEM_NDIS_TX_PACKET, OEM_NDIS_RX_PACKET_COMPLETE, OEM_NDIS_CLOSE_COMPLETE, OEM_NDIS_OPEN_COMPLETE, OEM_NDIS_IP_CONFIGURATION, OEM_NDIS_NUMBER_OF_EVENTS } OEMNDISEVENTTYPE; // As defined in Rilndisoem2.h typedef enum oemndiseventtype_tag { OEM_NDIS_NULL_EVENT, OEM_NDIS_RX_PACKET, OEM_NDIS_TX_PACKET_COMPLETE, OEM_NDIS_IP_CONFIGURATION, OEM_NDIS_XOFF, OEM_NDIS_XON, OEM_NDIS_INITIALISE_COMPLETE, OEM_NDIS_OPEN_COMPLETE, OEM_NDIS_CLOSE_COMPLETE, OEM_NDIS_REGISTRATION_STATUS, OEM_NDIS_TX_PACKET, OEM_NDIS_RX_PACKET_COMPLETE, OEM_NDIS_OPEN_CONNECTION, OEM_NDIS_CLOSE_CONNECTION, OEM_NDIS_REQUEST_BUFFER_STATUS, OEM_NDIS_BUFFER_STATUS, OEM_NDIS_NUMBER_OF_EVENTS } OEMNDISEVENTTYPE;

// As defined in Rilndisoem1.h
typedef enum oemndiseventtype_tag
{
  OEM_NDIS_RX_PACKET,
  OEM_NDIS_TX_PACKET_COMPLETE,
  OEM_NDIS_XOFF,
  OEM_NDIS_XON,
  OEM_NDIS_TX_PACKET,
  OEM_NDIS_RX_PACKET_COMPLETE,
  OEM_NDIS_CLOSE_COMPLETE,
  OEM_NDIS_OPEN_COMPLETE,
  OEM_NDIS_IP_CONFIGURATION,
  OEM_NDIS_NUMBER_OF_EVENTS
} OEMNDISEVENTTYPE;

// As defined in Rilndisoem2.h
typedef enum oemndiseventtype_tag
{
  OEM_NDIS_NULL_EVENT,
  OEM_NDIS_RX_PACKET,
  OEM_NDIS_TX_PACKET_COMPLETE,
  OEM_NDIS_IP_CONFIGURATION,
  OEM_NDIS_XOFF,
  OEM_NDIS_XON,
  OEM_NDIS_INITIALISE_COMPLETE,
  OEM_NDIS_OPEN_COMPLETE,
  OEM_NDIS_CLOSE_COMPLETE,
  OEM_NDIS_REGISTRATION_STATUS,
  OEM_NDIS_TX_PACKET,
  OEM_NDIS_RX_PACKET_COMPLETE,
  OEM_NDIS_OPEN_CONNECTION,
  OEM_NDIS_CLOSE_CONNECTION,
  OEM_NDIS_REQUEST_BUFFER_STATUS,
  OEM_NDIS_BUFFER_STATUS,
  OEM_NDIS_NUMBER_OF_EVENTS
} OEMNDISEVENTTYPE;

Elements (as defined in Rilndisoem1.h)

OEM_NDIS_RX_PACKET: A packet has been received. Generated by the packet driver (radio stack). Used in the RIL message reception queue. Valid data associated with the event is RILNDISPACKET.

OEM_NDIS_TX_PACKET_COMPLETE: A packet has completed transmission. Generated by the packet driver (radio stack). Used in the RIL message reception queue. Valid data associated with the event is RILNDISPACKETand the Status member of the OEMNDISEVENTTYPEstructure.

OEM_NDIS_XOFF: A request to stop sending packets to the radio stack. Generated by the packet driver (radio stack). Used in the RIL message reception queue. No data is associated with this event.

OEM_NDIS_XON: A request to restart sending packets to the radio stack. Generated by the packet driver (radio stack). Used in the RIL message reception queue. No data is associated with this event.

OEM_NDIS_TX_PACKET: A packet has been transmitted. Generated by the RIL GSM driver. Used in the RIL message transmission queue. Valid data associated with the event is RILNDISPACKET.

OEM_NDIS_RX_PACKET_COMPLETE: A packet has been completely received. Generated by the RIL GSM driver. Used in the RIL message transmission queue. Valid data associated with the event is RILNDISPACKET.

OEM_NDIS_CLOSE_COMPLETE: The connection is closed. Asynchronous commands can no longer be sent. Generated by the RIL GSM driver. Used in the RIL message reception queue. Valid data associated with the event is the Status and ContextId members of the OEMNDISEVENTTYPEstructure.

OEM_NDIS_OPEN_COMPLETE: The connection is open. Asynchronous commands can now be sent. Generated by the RIL GSM driver. Used in the RIL message reception queue. Valid data associated with the event is the Status and ContextId members of the OEMNDISEVENTTYPEstructure.

OEM_NDIS_IP_CONFIGURATION: The IP configuration of the packet has changed. Generated by the RIL GSM driver. Used in the RIL message reception queue. Valid data associated with the event is the IpConfig and ContextId members of the OEMNDISEVENTTYPEstructure.

OEM_NDIS_NUMBER_OF_EVENTS

Elements (as defined in Rilndisoem2.h)

OEM_NDIS_NULL_EVENT: No event is available. Generated by the packet driver (radio stack). No data is associated with this event. Used by the NDISReceiveEvent function.

OEM_NDIS_RX_PACKET: A packet has been received. Generated by the packet driver (radio stack). Valid data associated with the event is RILNDISPACKET.

OEM_NDIS_TX_PACKET_COMPLETE: A packet has completed transmission. Generated by the packet driver (radio stack). Once this event has been generated, the transmission buffer can be reused. Valid data associated with the event is RILNDISPACKET.

OEM_NDIS_IP_CONFIGURATION: The IP configuration of the of the network has changed. Generated by the packet driver (radio stack). Valid data associated with the event is the IpConfig and ContextId members of the OEMNDISEVENTTYPEstructure.

OEM_NDIS_XOFF: A request to stop sending packets to the radio stack. Generated by the packet driver (radio stack). No data is associated with this event.

OEM_NDIS_XON: A request to restart sending packets to the radio stack. Generated by the packet driver (radio stack). No data is associated with this event.

OEM_NDIS_INITIALISE_COMPLETE: The communication channel is ready for use. This event is generated after NdisInitialize has returned successfully, and the modem communications initiated by NdisInitialize have completed successfully.

OEM_NDIS_OPEN_COMPLETE: The connection is open. Asynchronous commands can now be sent. Generated by the packet driver (radio stack). Valid data associated with the event is the Status and ContextId members of the OEMNDISEVENTTYPEstructure.

OEM_NDIS_CLOSE_COMPLETE: The connection is closed. Asynchronous commands can no longer be sent. Generated by the RIL GSM driver. Used in the RIL message reception queue. Valid data associated with the event is the Status and ContextId members of the OEMNDISEVENT structure.

OEM_NDIS_REGISTRATION_STATUS: The GSM or GPRS registration status has changed.

OEM_NDIS_TX_PACKET: A packet has been transmitted. Generated by the RIL GSM driver.. Valid data associated with the event is RILNDISPACKET.

OEM_NDIS_RX_PACKET_COMPLETE: A packet has been completely received. Generated by the RIL GSM driver. Once this event has been generated, the receiving buffer can be reused. . Valid data associated with the event is RILNDISPACKET.

OEM_NDIS_OPEN_CONNECTION: Generated by the RIL GSM driver. No data is associated with this event.

OEM_NDIS_CLOSE_CONNECTION: Generated by the RIL GSM driver. No data is associated with this event.

OEM_NDIS_REQUEST_BUFFER_STATUS: Request the current receiving buffer status. Generated by the RIL GSM driver. No data is associated with this event.

OEM_NDIS_BUFFER_STATUS: There has been a significant change in the buffer status (that is,

OEM_NDIS_NUMBER_OF_EVENTS

Remarks

OEMs must include only one of Rilndisoem1.h and Rilndisoem2.h. The sample RIL GSM driver supports two NDIS implementations. Use declarations from Rilndisoem1.h when working with the TI radio stack and use declarations from Rilndisoem2.h when working with the TTPCOM radio stack.

Requirements

Header	Rilndisoem1.h, Rilndisoem2.h
Windows Embedded CE	Windows Embedded CE 6.0 and later
Windows Mobile	Windows Mobile 6, Windows Mobile 6 Standard and later

Syntax

Elements (as defined in Rilndisoem1.h)

Elements (as defined in Rilndisoem2.h)

Remarks

Requirements

See Also

Reference