Patent Grant
8584132
This application is related to an Application bearing Ser. No. 12/334,110 entitled “Power Settings in Wireless Ultra-Wide Band Universal Serial Bus” filed on Dec. 12, 2008, the disclosure of which is incorporated by reference herein.
Ultra-Wideband (UWB) technology enables information to be transmitted over a large bandwidth and can enable high data rate wireless connectivity. UWB technology is described in a set of specifications defined by the WiMedia Alliance (referred to hereinafter as “WiMedia”). In a typical scenario, a host controller wirelessly communicates with one or more devices. A host controller can be embodied on a computing device such as a desktop or laptop computer.
Ultra-Wideband hardware includes a radio controller sub function called the “URC” and one or more sub-functions which run on top of the radio and are considered clients of the radio. Each of the clients is referred to as a Protocol Adaption Layer or “PAL”. Today, PALs exist in the form of Wireless USB PALs, but in the future different bus technologies will inevitably lead to the incorporation of different PALs such as, for example, WUSB PALs, WLP PALs, Bluetooth PALs, vendor-specific PALs and the like.
Individual PALs are utilized to establish connections with associated devices and can share the same UWB radio. As such, hardware and software stacks can be designed to support multiple different types of PALs. One of the challenges associated with enabling wireless connectivity between host controllers and associated devices is to develop two-way interfaces that enable communication between a URC driver (referred to as “URCD”) and PAL drivers.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
Various embodiments provide a two-way interface between a URC driver (“URCD”) and various Protocol Adaption Layer (PAL) drivers. The two-way interface can enable bandwidth to be shared and managed among multiple different PALs. The two-way interface can also be used to implement common radio functionality such as beaconing, channel selection, and address conflict resolution. In at least some embodiments, the two-way interface can be utilized for power management to place PALs in lower power states to conserve power and to support remote wake-up functionality. Further, at least some embodiments can enable vendor-specific PALs to interact with vendor-specific hardware.
The same numbers are used throughout the drawings to reference like features.
Overview
Various embodiments provide a two-way interface between a URC radio driver (referred to as the “URCD”) and various Protocol Adaption Layer (PAL) drivers. The two-way interface can enable bandwidth to be shared and managed among multiple different PALs. The two-way interface can also be used to implement common radio functionality such as beaconing, channel selection, and address conflict resolution. In at least some embodiments, the two-way interface can be utilized for power management to place PALs in lower power states to conserve power and to support remote wake-up functionality. Further, at least some embodiments can enable vendor-specific PALs to interact with vendor-specific hardware. In the discussion that follows, Ultra-Wideband technology is utilized to enable different bus technologies to establish a wireless connection with devices and to allow interaction between PAL drivers, the URCD and hardware associated with the PAL drivers.
In the discussion that follows, a section entitled “Operating Environment” describes but one environment in which the various embodiments can be employed. Following this, a section entitled “Example Radio Software” describes a radio software architecture in accordance with one or more embodiments. Next, a section entitled “URCD-PAL Interface—Implementation Example” describes an example interface in accordance with one or more embodiments. Following this, a section entitled “Example Sequence of Operations” describes an example sequence of operations in accordance with one or more embodiments. Next, a section entitled “Example Interface” gives specific examples of an implementation of the URCD-PAL interface. Following this, a section entitled “Power Management” describes an example sequence of power conserving operations in accordance with one or more embodiments. Last, a section entitled “Example System” describes an example system that can implement one or more embodiments.
Operating Environment
Host controller 102 also includes radio software 110 which interfaces with radio hardware 112 to enable wireless communication with one or more external devices. In the illustrated and described embodiments, the host controller 102 utilizes Ultra-Wideband technology, e.g., any technology whose signals span a frequency range greater than 500 MHz, as a medium to enable wireless communication with the external devices. It is to be appreciated and understood that the various embodiments described herein can be utilized in connection with UWB technology that is compliant with specifications defined by WiMedia, as well as others.
The radio software 110 can include, in one or more embodiments, one or more Protocol Adaption Layers (PALs) and an Ultra-Wideband Radio Controller Driver (URCD). The PAL(s) use an interface with the URCD to manage use of shared resources, e.g. the radio. Host controller 102 includes an antenna 113 via which wireless communication can take place with a number of external devices shown generally at 114.
Devices 114 can include, by way of example and not limitation, a scanner 116, a printer 118, external storage 120, a digital camera 122, a wireless adapter 124 and/or a digital camcorder 126. The external devices interface, in at least some embodiments, with host controller 102 via a Wireless Universal Serial Bus (WUSB) which leverages Ultra-Wideband technology, as will become apparent below. Other means of connecting with the host controller can be used including other bus technologies and transports including, but not limited to PCI, PCIe, cardbus, expresscard and the like.
The computer-readable media can include, by way of example and not limitation, all forms of volatile and non-volatile memory and/or storage media that are typically associated with a computing device. Such media can include ROM, RAM, flash memory, hard disk, removable media and the like. One specific example of a computing device is shown and described below in
Having considered an example operating environment, consider now a discussion of example radio software in accordance with one or more embodiments.
Example Radio Software
In the illustrated and described embodiment, PALs 206, 208, 210 and URCD 212 communicate by way of a two-way interface or API that is represented using the plug notation generally at 213. An example of a suitable API is described below.
As will be appreciated by the skilled artisan and as noted above, Ultra-Wideband (UWB) can enable different bus technologies (WUSB, WLP, Bluetooth, Vendor Specific, etc) to establish a connection with their associated devices. UWB also has the potential that more than one bus technology can share the same UWB Radio. In this context, URCD 212 is configured to perform a number of different functions including, by way of example and not limitation, beaconing, channel selection, bandwidth allocation, conflict resolution, and address management. In addition, individual PALs are configured to perform a number of different functions including, by way of example and not limitation, requesting bandwidth from the URCD and using bandwidth allocated from the URCD to perform data transfers, set up PAL-specific channels, and the like.
To accomplish these functions, the PALs and the URCD communicate using a two-way interface an example of which is provided below.
To enable communication between the PALs and the URCD, the URCD creates a Query Interface for which the PAL drivers can query. In one implementation, each PAL driver sends an IRP_MN_QUERY_INTERFACE to exchange an interface between the PAL and the URCD. A Radio Management Layer exposes a table of functions that PALs can call, and PALs expose a table of notification callbacks that the URCD can call. This interface is used by both the PAL and the URCD to communicate with each other.
Having considered example radio software including a driver architecture in accordance with one or more embodiments, consider now a discussion of an example URCD-PAL interface.
URCD-PAL Interface—Implementation Example
In operation, the URCD-PAL Interface utilizes a number of different data structures and data types, examples of which are provided below.
STATUS—This represents the standard NTSTATUS. Custom status codes can be defined here.
PAL_HANDLE—Handle to the PAL. This gets assigned by the URCD to the PAL during initial PAL registration discussed below. PAL uses this handle when calling into URCD.
IE_HANDLE—Handle to an information element that was added by the PAL.
NOTIFICATION_LEVEL—A data type used by some functions described below. This type is defined as an enum:
PAL_Identifier—2 byte value (e.g. a USHORT). This value identifies the PAL's function. PAL fills in this value during registration. The higher order byte is reserved and should be 0. The lower order byte is the URC capability ID.
MAC_CAP_BITMAP—A data type defining the Medium Access Controller (MAC) Capabilities:
PHY_CAP_BITMAP—A data type defining the physical interface (Phy) Capabilities:
UWB_BW_INTERVAL: Enum to specify bandwidth (BW) Interval while requesting BW. A “zone” is a set of sixteen temporally consecutive MASes.
UWB_MAS_MAP—struct used to keep track of MAS Map in a superframe. A “MAS” refers to a Media Access Slot which is a 256 microsecond unit of time.
CHANNEL_BITMAP—struct used to keep track of supported channels:
If we call the least significant bit within a byte as Bit0 and the most significant bit as Bit7, then the following is the mapping of bits in the Channel BitMap to actual channel numbers.
If a bit is set, it means the represented channel is supported and if bit is not set, then the channel is not supported.
UWB_BW_REQUEST_STATUS—enum used to maintain the state of a BW Request
Having described some example data structures and data types, consider first a discussion of a sequence of operations that can be performed by a PAL in accordance with one or more embodiments. Following this discussion, a description of an example interface is provided to illustrate but one way the example sequence of operations can be performed.
Example Sequence of Operations
To begin a sequence of operations, a PAL will typically register with the URC using a particular interface. In the example just below, the PAL registers with the URC by using IRP_MN_QUERY_INTERFACE. Next, a means of communication is established between the PAL and the URCD.
After starting the channel, the following operations can be performed in any order and/or multiple times: allocate and release bandwidth; add/remove IEs; send vendor specific commands; acquire/release TKIDs (“Temporal Key Identifiers” that are used to secure a given packet); get information from URC such as: DevAddress, PhyCapabilityBitMap, MacCapabilityBitMap; set a new channel BitMask; and/or perform a sleep resume cycle.
A cleanup can also be performed for all the commands executed in paragraph [0045]. This can include, by way of example and not limitation, releasing and deleting BW handles and groups; removing added IEs; and/or releasing TKIDs.
The channel can also be stopped when communication is to be terminated and the PAL may or may not unregister with the URC.
It is to be appreciated and understood that the operational steps that begin with starting a channel and continue through those described in the paragraph just above can be repeated any number of times. Having considered an example sequence of operations in accordance with one or more embodiments, consider now a discussion of an example interface that can be used to implement the above-described sequence of operations as well as other operations.
Example Interface
In this section, a formal definition of a URCD-to-PAL Interface is provided. The URCD-to-PAL Interface is exchanged between the URCD and the PAL by IRP_MN_QUERY_INTERFACE. The guide for this interface is defined by:
The type of the interface is UWB_PAL_INTERFACE. It is defined as:
The following is an explanation of various fields and functions employed by the Interface in accordance with one or more embodiments.
Struct INTERFACE
USHORT Size—Size should be size of the interface.
USHORT Version—Version should be the version of the interface.
PVOID Context—This is unused and should be NULL.
Registration of a PAL
In the illustrated and described embodiment, registration of a PAL happens by the IRP_MN_QUERY_INTERFACE. The PAL fills in the following portions of the URCD_INTERFACE structure and sends it down to the URCD with the IRP_MN_QUERY_INTERFACE Irp.
As part of UwbFromPalInfo, PAL passes a “PalContext” to the URCD. This context is used by URCD whenever calling back into the PAL. The URCD gets the desired information from the URCD_INTERFACE, adds URCD specific information in the following portion and completes the IRP.
As part of UwbToPalInfo, URCD assigns a PAL_HANDLE to the PAL. The PAL_HANDLE is used by the PAL whenever calling into the URCD to identify itself. This completes the registration process. The following functions are used in relation to registration activities:
UnRegisterPAL
Arguments:
This is a routine to un-register the PAL. Before the PAL un-registers, it ensures that:
Step 300 attempts to register with a URCD. The step can be performed in any suitable way an example of which is provided above. Step 302 registers the PAL and step 304 returns a PAL handle to the PAL that just registered.
Step 306 receives the PAL handle. The PAL handle can be used for subsequent calls into the URCD as will become apparent below.
Registration for Notifications
In the illustrated and described embodiment, there are three categories of notification callbacks for which a PAL may register.
Examples of functions that are utilized in connection with notification registrations include, by way of example and not limitation:
RegisterForBeaconNotifications
This function allows a PAL to register for beacon notifications/beacon change notifications from its all devices or a particular device.
Arguments:
This function allows a PAL to unregister for beacon received notifications/beacon change notifications from all its devices or a particular device.
Arguments:
a. Pal: The handle to the PAL received when the PAL registered with the URCD.
Return Value:
RegisterForASIENotifications
This function allows a PAL to register for IE or ASIE received notifications/change notifications from its all devices or a particular device.
Arguments:
Return Value:
Returns an NT_SUCCESS( ) value if Register call is successful; otherwise an appropriate error is returned.
UnregisterForASIENotifications
UnregisterForIENotifications
These functions allow a PAL to unregister for IE or ASIE notifications/IE or ASIE change notifications from its all or particular devices.
Arguments:
NONE
In one or more embodiments, a PAL may register for some other notification callbacks with the URCD. It does this by implementing the following notification callbacks. These notification callbacks are sent to the URCD when the PAL registers with the URCD using the IRP_MN_QUERY_INTERFACE.
AddrChangeNotification
This function is used whenever the URCD sets a new 16 bit device address, it will call using this function to notify the PAL about it.
Arguments:
This function is used whenever the URCD is about to change a channel. It first calls the PAL to let it know about the change and to give the PAL a chance to let its devices know about the change. When the PAL is done processing this notification, it calls the PrepareChannelChangeCompletion function that was passed in this function by the URCD.
Arguments:
ChannelChangeNotification
This function is used by URCD to notify PAL about a channel change operation.
Arguments:
a. PalContext: Context that was passed by PAL during registration (in the UwbFromPalInfo structure).
b. Channel: The new channel being used by URCD
VendorSpecificEventNotification
This function is used by URCD to notify PAL about a vendor specific event received from the hardware. URCD just acts a pass through in this case and it is up to the PAL to decode the event.
Arguments:
a. PalContext: Context that was passed by PAL during registration (in the UwbFromPalInfo structure).
b. Rceeb: The new RCEEB (Radio Controller Extended Event Block) received by the hardware. The size information is contained within the RCEEB—so no separate parameter is used.
CommandFrameReceivedNotification
This function is used by URCD to notify PAL about a command frame received over the air.
Arguments:
a. PalContext: Context that was passed by PAL during registration (in the UwbFromPalInfo structure).
b. RcebSize—Size of the RCEB (Radio Controller Event Block) received by the hardware
c. Rceb—RCEB received by the hardware.
PrepareForRemoteWakeBwChanges
This function is used whenever the URCD is about to send allocation changes for its remote wake bandwidth. It first calls the PAL to let it know about the allocation change and give it a chance to prepare. If the PAL is sleeping, it might need to wake up its hardware. When PAL is done processing this notification, it calls the completion function that was passed by URCD:
PrepareRemoteWakeBwChangesCompletion.
Arguments:
NoMoreRemoteWakeBwChanges
This function is used whenever the URCD is about to send allocation changes for its remote wake bandwidth, it first calls in the PAL to let it know about the allocation change and give it a chance to prepare through PrepareForRemoteWakeBwChanges. When URCD is done sending all the notifications for changes in remote wake bandwidth, it calls NoMoreRemoteWakeBwChanges. If the PAL woke itself up for these changes, it might need to go back to sleep. When PAL is done processing this notification, it calls the completion function, NoMoreRemoteWakeBwChangesCompletion.
Arguments:
Step 400 registers for one or more notifications. Examples of how a PAL can register for a notification and various types of notifications are described above. Step 402 receives a notification registration from the PAL and step 404 registers the PAL for one or more notifications. In an event a registered-for notification is generated, step 406 generates one or more notifications and sends the notifications to the PAL that registered for the notification(s).
Step 408 receives the one or more notifications from the URCD.
Adding IE & ASIE
In one or more embodiments, a PAL may request the URCD to add certain IEs and ASIEs to the HOST Beacon. In connection with these activities, the following functions can be used:
AddIE
This function allows the PAL to add ASIEs and/or certain other types of IEs.
Arguments:
The prototype for the callback is:
Status: is the result of trying to add the given IE
Context: is the context which was passed in the AddIE function.
IEHandle: is the handle to the IE that should be preserved by the PAL to be used later while removing the IE
VOID
RemoveIE
in
in
in
This function allows the PAL to remove IEs and ASIEs from the URCs beacon. The PAL can remove the IEs it added with the AddIEs API call.
Arguments:
The prototype for the callback is:
Context: is the context which was passed in the RemoveIE function.
NONE.
RemoveAllIEs (PAL_HANDLE Pal)
This function allows the PAL remove all IEs and ASIEs that it had added with the AddIEs API call.
Arguments:
a. Pal: The handle to the PAL received when the PAL registered with the URCD.
Return Value:
NONE.
In one or more embodiments, there can be a callback that the PAL provides that can tell the client that all the IE data it had notified about has been deleted. This would be helpful in a recovery situation in case an unexpected error happens in the URCDs IE module. Alternately or additionally, there can be a callback that the PAL provides that could be a reset callback that would mean that the URCD has reset itself and now contains no PAL specific information. In this case, the PALs would re-register and restart their work.
Bandwidth Negotiation
In one or more embodiments, individual PALs utilize bandwidth for transferring data and bandwidth allocations are divided into two classes: Critical BW and Varying BW. Critical BW refers to reservations that a PAL needs to function well. Varying BW, on the other hand, refers to reservations in addition to Critical reservations that the PAL can use for improving its data transfers.
In one or more embodiments, before the PAL can request BW from the URCD, it creates a Bandwidth Group that defines the (Owner, Target, StreamIndex, ReservationType). After it has created the Bandwidth Group, the PAL can create Bandwidth that is associated with a BW Group.
In connection with bandwidth negotiation activities, the following functions can be used:
BWGroupCreate
This function can be used if a PAL needs bandwidth from the URCD. The PAL first creates a bandwidth group. A bandwidth group defines the (Target Device Address, Stream Index, and Reservation Type). Once a bandwidth group has been created, the PAL may create and reserve several bandwidth components to get the required bandwidth.
Arguments:
The prototype is
STATUS—STATUS_INSUFFICIENT_RESOURCES if there is a low memory situation.
BWGroupReleaseandDeleteAllBw
This request tells the URCD to release and delete any Bandwidth components of this BW Group. In one or more embodiments, the PAL treats the BW_HANDLEs that are associated with the BW Group as destroyed as soon as this function is called and PAL may not use any such BW_HANDLE after issuing this call.
Arguments:
The prototype of the callback is
NONE
BWGroupDelete
This request tells the URCD to delete the BW Header that was created during the BWGroupCreate call. It is to be noted that if the PAL has some BW that was reserved for the BW Group, the PAL first releases and deletes each of those BW requests, OR, the PAL calls BWGroupReleaseAndDeleteAllBw and waits for that request to complete before making a call to BWGroupDelete.
The PAL treats the BW_GROUP_HANDLE as destroyed as soon as this function is called and PAL may not use BW_GROUP_HANDLE after issuing this call.
Arguments:
a. BWGroupHandle: The Handle of BW Group received on a call to BWGroupCreate
Return Value:
NONE
BwGroupUpdateMasAvailability
If the PAL provided a DeviceAvailability during the BWGroupCreate Call, it can update that Availability Info by calling this function.
Arguments:
NONE
BWCreate
This routine allows the PAL to create a BW Component for a BW Group it had created earlier.
Arguments:
STATUS—STATUS_INSUFFICIENT_RESOURCES if we are in low memory situation.
CriticalBWReserve
After the PAL has create a BW Handle, the PAL uses this routine to request Critical BW.
Arguments:
The prototype is
STATUS—STATUS_INSUFFICIENT_RESOURCES if we are in low memory situation.
VaringBWReserve
After the PAL has setup a BW Header, the PAL uses this routine to request a Varying BW.
Arguments:
The prototype is
STATUS—STATUS_INSUFFICIENT_RESOURCES if we are in low memory situation.
BWRelease
This request tells the URCD to release the BW reservation.
Arguments:
After the CallbackOnRelease has been called, the PAL may reuse the BW_HANDLE to send a new BwReserve request to the URCD.
Return Value:
NONE
BWDelete
This request tells the URCD to delete the BW that was created during the BWCreate. It should be noted that if this BW_HANDLE was used in a call to CriticalBWReserve or VaryingBWReserve call, the PAL first releases that BW by calling the BWRelease function. Further, the PAL treats that BW_HANDLE as destroyed as soon as this function is called and the PAL may not use BW_HANDLE after issuing this call.
Arguments:
NONE
VOID VarvingBWInitiateAutoAdjust(
This request tells the URCD to start adjusting the Varying BW.
Arguments:
NONE
BWUpdateMasAvailability
If the PAL provided AvailabilityInfo during Allocate BW Call, it can update that Availability Info by calling this function.
Arguments:
NONE
Consider now some implementation considerations concerning bandwidth negotiation in accordance with one or more embodiments. In one or more embodiments, to be able to reserve any BW, the user should have: a BW group (created earlier by BWGroupCreate) and a BW component (created earlier by BWCreate). In the above-described embodiment, two types of BW can be reserved: Critical and Varying (CriticalBWReserve, VaryingBWReserve). Further, multiple BW components can belong to the same group. In addition, in at least some embodiments, Reserve may be called only once for each BW component, unless the previous Reserve was released (BWRelease) or Reserve failed (in case of critical). For example, a BW component may be used again to reserve another BW, once it has been released. Further, if the BW was reserved, in at least some embodiments, it must be released before it can be deleted. In addition, in at least some embodiments, Release BW for critical BW should only be called if the reserve completion routine returned success. Lastly, in at least some embodiments, all BW handles (belonging to a BW group) must be deleted before that BW group can be deleted.
Step 500 calls the URCD to create a bandwidth group. An example of how this can be done is provided above. Step 502 receives the call from the PAL to create a bandwidth group and step 504 creates a bandwidth group. Step 506 then returns a bandwidth group handle to the PAL.
Step 508 receives the bandwidth group handle and step 510 uses the bandwidth group handle to make bandwidth reservations. Step 512 reserves bandwidth for the PAL using the bandwidth group handle. A handle to the reserved bandwidth is also passed back to the PAL.
Step 514 uses the bandwidth group handle (or the handle to the reserved bandwidth) to make other bandwidth-related calls. Examples of other bandwidth-related calls are given above. Step 516 receives the bandwidth related calls and step 518 takes a bandwidth-related action. Examples of bandwidth-related actions are provided above.
URC Info
In one or embodiments, various functions can be provided to handle URC information. By way of example and not limitation, these functions can include the following:
GetPhyCapablityBitmap
Arguments:
Arguments:
Arguments:
Arguments:
In one or embodiments, various functions can be provided to handle channel management activities. By way of example and not limitation, these functions can include the following:
SetChannelBitMask
In one or more embodiments, by default, all of the channels that are supported by the URC are also supported by the PALs. Assume, for example, that a PAL (such as WUSB) is connected to a device that supports only certain channels. This function allows the PAL to tell the URCD to only use certain channels. This information may be useful to the URCD's Channel Manager if some other PAL requests to change to a channel not supported by the PAL. In at least some embodiments, less than all of the channels can be supported. For example, in certain regions, less than all of the channels might be supported because of regulatory issues.
Arguments:
In one or more embodiments, when a PAL wants to start a channel, it lets the URCD know by calling this function. The URCD will then call the completion routine when it has finished starting the channel.
Arguments:
The prototype is
VOID
StopChannel
In one or more embodiments, when a PAL wants to stop a channel, it uses this function to let the URCD know about it. Before the PAL calls this function, it should have released and deleted all bandwidth objects. It should also have removed all the IEs and ASIEs that it might have added.
Arguments:
The prototype is
VOID
ScanAllChannels
This command starts a Scan for all channels.
Arguments:
Consider now some usage notes for the channel management functions in accordance with one or more embodiments. First, a PAL should not call StartChannel more than once before calling StopChannel in between. In at least some embodiments, there should be one stop channel for a start channel. In addition, SetChannelBitMask can be called any time. If called after startchannel, then it might result in a channel change (e.g., the PAL will get a notification for that, if it has provided a ChannelChange function). Finally, before changing channels, the URC calls PrepareStopChannel (if they have provided one) to the PALS which they use to complete (through a completion routine) before the URC actually changes channels.
Having considered some example functions associated with channel management activities, consider now a few miscellaneous functions.
Miscellaneous
VendorSpecificCommand
This function allows Vendor Specific commands to be issued by the PAL to the URC. Thus, this function can facilitate extensibility of the overall system.
Arguments:
Status: Status returned by the software indicating whether the command was successfully sent or not
EventBlock: RCEB returned by the hardware, in response to the command
Context: Context that passed in the VendorSpecificCommand function
AcquireTKID
This generates a TKID which is unique across all PALs.
Arguments:
Return Value:
The generated TKID
ReleaseTKID
This releases a TKID earlier acquired by the PAL.
Arguments:
a. TKID: The TKID to be released.
Having considered various aspects of a URCD-PAL interface, consider now a discussion of various power management features, including various functions associated with power management.
Power Management
In one or more embodiments, a PAL can decide to go to an idle state based on its own idle heuristics. If the PAL will not be using any bandwidth while idle, then it can let the URC know about it so that the URC can conserve power by going to its own idle state or altogether stop beaconing. When the PAL is in the idle state, it can also decide to go to a lower power device state. A PAL can also go to such a state in response to a system wide sleep state transition. Before going to such a state, a PAL notifies the URC.
In at least some embodiments, the URC does not initiate a sleep on its own. It follows the idle states of its PALs. The URC device stack follows the device state of the PAL stacks.
In at least some embodiments, a PAL can choose to arm itself for remote wake from its devices. For remote wake to work, the PAL can come up periodically and ask for device notifications. In order to do this, PALSs use some bandwidth. PALs are responsible for reserving this bandwidth before they go to sleep. The URC (and URCD) are responsible for maintaining this remote wake bandwidth, regardless of its own sleep state. A PAL should be prepared to handle bandwidth allocation changes while sleeping.
In at least some embodiments, PALs also inform the URCD about its remote wake polling interval and also how long will it need the channel in each sleep cycle. Since the URCD manages multiple PALs, the URCD might override these values and send them back to the PAL.
While a PAL is sleeping, the URCD will continue to give all the notifications to the PAL driver as usual. It is up to the PAL driver to decide whether to buffer that notification or process it. One exception is remote wake bandwidth allocation change notification which PALs process.
When a bandwidth conflict occurs, the URCD might have to send multiple bandwidth allocation change notifications to the PAL to resolve it. Since it is possible that the PAL might temporarily wake up its hardware to process these bandwidth changes, it is undesirable for the PAL to wake up for each of these notifications. To overcome this problem, in at least some embodiments, the URCD provides two additional notifications, which the PAL provides during initial registration: PrepareForRemoteWakeBwChanges and NoMoreRemoteWakeBwChanges. When the PAL receives the PrepareForRemoteWakeBwChanges notification, it should do whatever is necessary to process the bandwidth changes (e.g., wake up its hardware) before calling the completion routine. When PAL receives the NoMoreRemoteWakeBwChanges, it can safely go back to the previous state.
In at least some embodiments, a PAL will also consider synchronization issues that might arise because of the various independent events overlapping with each other, e.g., the URCD giving bandwidth allocation change notifications and the PAL getting a wake signal (either from the hardware or from software). In order to assist PALs, the URCD can serialize the processing of Remote wake BW change notifications and ResumeChannel Calls so that if a PAL calls ResumeChannel while a Bandwidth Allocation Change is in progress, the URCD will not call the completion routine for the ResumeChannel call until the current BW allocation change process completes i.e. it receives a CompletionCallback for NoMoreRemoteWakeBwChanges from the PAL.
Consider now some various functions associated with power management activities.
SleepChannel
When the PAL has gone to sleep, it lets URCD know by calling this function.
Arguments:
The prototype is
VOID
ResumeChannel
When a PAL wants to resume from a channel, it uses this function to make sure the URC is awake.
Arguments:
The prototype is
VOID
RemoteWakeBWReserve
A Pal uses this function to reserve bandwidth required for supporting remote wake. The meaning of the parameters and return value is the same as the CriticalBWReserve function. When the PAL gets CallbackOnChange for such bandwidth, the PAL might have to wake itself, deal with the change and then go back to sleep. The PAL should call the completion routine for the CallBackOnChange routine when all these steps have been completed.
RemoteWakeSetParameters
A PAL uses this function to tell the URCD about its remote wake requirements before it goes to sleep so that when the URCD sends the URC to sleep, it can make sure that URC wakes up periodically and keep the channel awake as per the PAL's requirements.
Arguments:
STATUS—URCD returns STATUS_INVALID PARAMETER if it cannot satisfy PAL's requirements, otherwise returns STATUS_SUCCESS.
Having considered various power management functions, consider now some usage notes for the power management functions in accordance with one or more embodiments.
The following is a sequence of operations that will typically be used by a PAL for sleeping when it detects that it is idle. First, all bandwidth is released and a request is made for remote wake bandwidth. Remote wake parameters are set and modified parameters returned from the URCD are stored. Next, the associated hardware for remote wake is programmed and then sent to sleep. Next, the URC is notified by calling SleepChannel.
While sleeping, if a PrepareForRemoteWakeBwChanges.call is received, it is processed in the following way. First, the hardware is awakened and the completion routine is called for PrepareForRemoteWakeBwChanges. Next, a bandwidth allocation change notification is acquired from the PAL and the associated hardware is re-programmed with the new allocation. Bandwidth allocation change notifications and associated hardware re-programming are performed until the URCD calls NoMoreRemoteWakeBwChanges. At this point, the hardware is sent back to sleep and the completion routine is called for NoMoreRemoteWakeBwChanges.
While sleeping, if a remote wake signal is received, it is processed in the following way. First, the signal is verified to ensure that is was generated by the associated hardware. If it was not, then the signal is ignored. If it was generated by the associated hardware, then ResumeChannel is called and the system waits for its completion. Once the URCD has called ResumeChannelCompletion, then the associated hardware is awakened and the remote wake bandwidth is released. Normal functioning can now resume.
Example System
Computing device 600 includes one or more processors or processing units 602, one or more memory and/or storage components 604, one or more input/output (I/O) devices 606, and a bus 608 that allows the various components and devices to communicate with one another. Bus 608 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. Bus 608 can include wired and/or wireless buses.
Memory/storage component 604 represents one or more computer storage media. Component 604 can include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). Component 604 can include fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., a Flash memory drive, a removable hard drive, an optical disk, and so forth).
One or more input/output devices 606 allow a user to enter commands and information to computing device 600, and also allow information to be presented to the user and/or other components or devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone, a scanner, and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, and so forth.
Various techniques may be described herein in the general context of software or program modules. Generally, software includes routines, programs, objects, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. An implementation of these modules and techniques may be stored on or transmitted across some form of computer readable media. Computer readable media can be any available medium or media that can be accessed by a computing device. By way of example, and not limitation, computer readable media may comprise “computer storage media”.
“Computer storage media” include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
Various embodiments provide a two-way interface between a URC driver (“URCD”) and various Protocol Adaption Layer (PAL) drivers. The two-way interface can enable bandwidth to be shared and managed among multiple different PALs. The two-way interface can also be used to implement common radio functionality such as beaconing, channel selection, and address conflict resolution. In at least some embodiments, the two-way interface can be utilized for power management to place PALs in lower power states to conserve power and to support remote wake-up functionality. Further, at least some embodiments can enable vendor-specific PALs to interact with vendor-specific hardware.
Although the subject matter has been described in language specific to structural features and/or methodological steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as example forms of implementing the claimed subject matter
| Number | Name | Date | Kind |
|---|---|---|---|
| 5768527 | Zhu et al. | Jun 1998 | A |
| 6067534 | Terho et al. | May 2000 | A |
| 6141565 | Feuerstein et al. | Oct 2000 | A |
| 6175856 | Riddle | Jan 2001 | B1 |
| 7047305 | Brooks et al. | May 2006 | B1 |
| 20020073238 | Doron | Jun 2002 | A1 |
| 20020136164 | Fukuda et al. | Sep 2002 | A1 |
| 20020141392 | Tezuka et al. | Oct 2002 | A1 |
| 20030152032 | Yanagihara et al. | Aug 2003 | A1 |
| 20030236892 | Coulombe | Dec 2003 | A1 |
| 20040107245 | Bodnar | Jun 2004 | A1 |
| 20040113933 | Guler | Jun 2004 | A1 |
| 20040133701 | Karaoguz et al. | Jul 2004 | A1 |
| 20040253991 | Azuma | Dec 2004 | A1 |
| 20050018768 | Mabey et al. | Jan 2005 | A1 |
| 20050073575 | Thacher et al. | Apr 2005 | A1 |
| 20050273491 | Meyer et al. | Dec 2005 | A1 |
| 20050276255 | Aiello et al. | Dec 2005 | A1 |
| 20060079209 | Oda | Apr 2006 | A1 |
| 20070002840 | Song et al. | Jan 2007 | A1 |
| 20070066314 | Sherman et al. | Mar 2007 | A1 |
| 20070174489 | Iwabuchi | Jul 2007 | A1 |
| 20070174881 | Idehara et al. | Jul 2007 | A1 |
| 20070248114 | Jia et al. | Oct 2007 | A1 |
| 20070271358 | Gaddy | Nov 2007 | A1 |
| 20080165895 | Lesser et al. | Jul 2008 | A1 |
| 20080225750 | Jefremov | Sep 2008 | A1 |
| 20080225844 | Jefremov | Sep 2008 | A1 |
| 20090198859 | Orishko et al. | Aug 2009 | A1 |
| 20090234919 | Jefremov et al. | Sep 2009 | A1 |
| Number | Date | Country |
|---|---|---|
| 1463323 | Sep 2004 | EP |
| 11215481 | Aug 1999 | JP |
| WO-9722201 | Jun 1997 | WO |
| WO-2005002261 | Jan 2005 | WO |
| WO-2005009019 | Jan 2005 | WO |
| WO-2008027724 | Mar 2008 | WO |
| WO-2008110871 | Sep 2008 | WO |
| WO-2008110930 | Sep 2008 | WO |
| Entry |
|---|
| “Wireless Host Controller Interface Specification for Certified Wireless Universal Serial Bus: Certified Wireless USB 1.0”. Intel Corporation. Jun. 16, 2006. |
| Bhesania, Fred et al. “UltraWide Band Architecture for Windows”. Microsoft PowerPoint Presentation dated 2006. |
| Lee, Seung-sik et al. A WiMedia UWB Transceiver for 4-HD Channel Streaming. IEEE Transactions on Consumer Electronis, vol. 53, No. 2, May 2007. |
| Mayerhofer, Michael B., “Introduction to Wireless USB—An embedded perspective”, Streamunlimited Engineering GmbH Gutheil-Schoder-Gasse 10, A-1102 Vienna, Austria, (Sep. 11, 2005),1-10. |
| Perez-Gonzalez, Inaky “Proceedings of the Linux Symposium”, Open source Technology Center, Intel Corporation, (Jun. 27-30, 2007),1-10. |
| “Ultra-Wideband (UWB Technology)”, Copyright 2005 Intel Corporation. All rights reserved., Enabling high-speed wireless personal area networks. (2005), 1-8. |
| Chiani, et al., “Ultra Wide Bandwidth communications towards Cognitive Radio”, EMC Europe Workshop 2005—Rome, Italy, (2005),1-4. |
| “Support UWB & WUSB on OpenSolaris”, Version 1.0, WUSB (Wireless USB) is a new technology from, the Wireless Universal Serial Bus Specification Revision 1.0 released at May 12, 2005. WUSB chooses UWB(Ultra Wide Band), from WiMedia Alliance, as its radio module.,(May 12, 2005),1-11. |
| “Ultra-Wideband (UWB) Technology” Copyright 2005 Intel Corporation., (2005),1-4. |
| “Final Office Action”, U.S. Appl. No. 12/004,457, (Mar. 1, 2012), 29 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/EP2009/052916, (Jul. 10, 2009), 14 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/IB2007/004510, (Sep. 5, 2008), 12 pages. |
| “International Search Report”, PCT/IB2008/001353, (Sep. 12, 2008), 4 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 12/004,457, (Aug. 1, 2011), 21 pages. |
| “Written Opinion”, Application No. PCT/IB2008/001353, (Sep. 12, 2008), 8 pages. |
| Sato, Jun et al., “Compressed Video Transmission Protocol Considering Dynamic QoS Control”, Architecture and OS Support for Multimedia Applications/Flexible Communication Systems/Wireless Networks and Mobile Computing, 1998 ICPP Workshops, (Jan. 1998), pp. 95-104. |
| Number | Date | Country | |
|---|---|---|---|
| 20100153973 A1 | Jun 2010 | US |
