Patent application number | Description | Published |
20090138625 | SPLIT USER-MODE/KERNEL-MODE DEVICE DRIVER ARCHITECTURE - A device driver includes a kernel stub and a user-mode module. The device driver may access device registers while operating in user-mode to promote system stability while providing a low-latency software response from the system upon interrupts. Upon receipt of an interrupt, the kernel stub may run an interrupt service routine and write information to shared memory. Control is passed to the user-mode module by a reflector. The user-mode module may then read the information from the shared memory to continue servicing the interrupt. | 05-28-2009 |
20090204978 | SYNCHRONIZING SPLIT USER-MODE/KERNEL-MODE DEVICE DRIVER ARCHITECTURE - A device driver includes a kernel mode and a user-mode module. The device driver may access device registers while operating in user-mode to promote system stability while providing a low-latency software response from the system upon interrupts. The device driver may include kernel stubs that are loaded into the operating system, and may be device specific code written. The stubs may be called by a reflector to handle exceptions caught by the stubs. A reset stub may be invoked by the reflector when the user-mode module or host terminates abruptly or detects an interrupt storm. The reset stub may also be invoked if errant DMA operations are being performed by a hardware device. The reset stub may ensure that hardware immediately stops unfinished DMA from further transfer, and may be called by the user-mode driver module. | 08-13-2009 |
20090210888 | SOFTWARE ISOLATED DEVICE DRIVER ARCHITECTURE - A device driver includes a hypervisor stub and a virtual machine driver module. The device driver may access device registers while operating within a virtual machine to promote system stability while providing a low-latency software response from the system upon interrupts. Upon receipt of an interrupt, the hypervisor stub may run an interrupt service routine and write information to shared memory. Control is passed to the virtual machine driver module by a reflector. The virtual machine driver module may then read the information from the shared memory to continue servicing the interrupt. | 08-20-2009 |
20140359160 | MANAGEMENT OF MULTILEVEL QUEUES FOR SHARED NETWORK ADAPTERS - Technology for managing queuing resources of a shared network adapter is disclosed. The technology includes selectively transferring data from data transmission sources to a queue of the shared network adapter based on status indications from the shared network adapter regarding availability of queuing resources at the shared network adapter. In addition, the technology also includes features for selectively controlling transfer rates of data to the shared network adapter from applications, virtual network stations, other virtual adapters, or other data transmission sources. As one example, this selective control is based on how efficiently data from these data transmission sources are transmitted from the shared network adapter. | 12-04-2014 |
20140379883 | NETWORK MODE CONFLICT RESOLUTION - Technology for managing operational modes of a network adapter is disclosed. The technology includes features for selectively preempting (e.g., canceling, suspending, deferring, pausing, changing to a “no-op” state, changing to a passive state, or otherwise deprioritizing) execution for a current operational mode of the network adapter, executing a requested network control operation, and optionally restoring the preempted operational mode. The operational mode may be selectively preempted based on priority information associated with the current operational mode and the requested network control operation. | 12-25-2014 |
20140379884 | PRIORITIZATION OF NETWORK CONTROL OPERATIONS - Technology for prioritizing and executing network control operations is disclosed. The technology includes prioritizing requested network control operations against other network control operations and executing network control operations based on this prioritization. The prioritization may be based on priority information and classes with which the network control operations are associated. The classes may be based on expected durations of time for executing the network control operations. The technology also includes prioritizing and executing network control operations in a virtualized networking system. | 12-25-2014 |
Patent application number | Description | Published |
20080258865 | BINARY VERIFICATION SERVICE - A binary is received at a binary verification service from a binary verification client agent. The binary verification service performs binary verification of the binary, wherein binary verification includes determining whether the binary is complicit with a set of usage rules. The binary verification service sends a binary verification result to the binary verification client agent. | 10-23-2008 |
20090158301 | Multi-function device ID with unique identifier - A computer system that recognizes multi-function devices and associates functions with multi-function devices. Each multi-function device may be represented by a multi-function object, allowing tools, applications or other components within the computer to take actions relating to the entire device or relating to a function based on the association of that function with other functions in the same device. These actions include displaying information about devices, instead of or in addition to information about functions. Actions also include selecting functions based on proximity within a device. Functions may be associated with a multi-function device using a unique device identifier provided by the device or generated for the function based on a connection hierarchy between functions and the computer. Devices may be configured to provide the same identifier regardless of the transport over which the device is accessed. | 06-18-2009 |
20090293070 | DEVICE DISPLAY OBJECT INFRASTRUCTURE - Multi-function devices expose multiple functions to device drivers or other lower-level software. Device function providers can interface with such drivers or lower-level software and can provide information, including device identifiers regarding such functions, to a device display object infrastructure. A device display object can then be created that encompasses one or more functions such that, in one embodiment, the device display object corresponds to a single, physical multi-function device. Alternatively, any combination of functionality from one or more physical devices can be combined into a single device display object representing a virtual multi-function device. Properties of the device display object can be set with reference to user-specified settings, remotely maintained metadata, locally available metadata, and information associated with each function. Functions can be ranked such that, if there is a conflict, information from more highly ranked functions is used to set the properties of the device display object. | 11-26-2009 |
20090319660 | GENERALIZED ARCHITECTURE TO SUPPORT REPRESENTATION OF MULTI-TRANSPORT DEVICES - A computer system that accesses multi-transport devices and associates device instances of the multi-transport device with each other. Devices provide the same device identifier such as a device unique identifier regardless of the transport over which the device is accessed. A visual representation for the multi-transport device may be provided to a user using the device identifier. Also, a single functional representation for the multi-transport device may be provided based on an identifier provided by each function of the device. The functional representation may be independent of the addition and removal of transports and allows abstracting device access via multiple transports from a user and an application. Transports may be selected at an application and/or a system level. Operating characteristics of available transports may be used to select a desired transport, based on transport requirements specified by the application, the user or the system. | 12-24-2009 |
20100040233 | PROTOCOL FOR DEVICE TO STATION ASSOCIATION - A technique that enables a portable device to be automatically associated with a plurality of computers. Information that a computer can use to authenticate a portable device and establish a trusted relationship prior to creating an association with the portable device is created and stored in a data store that is accessible by a plurality of computers and is associated with a user of the portable device. When a computer discovers such a portable device with which it is not yet associated, the computer can identify a user logged into the computer and use information identifying the user to retrieve authentication information that is device independent and is expected to be presented by the portable device to authenticate it and allow automatic association. | 02-18-2010 |
20100043056 | PORTABLE DEVICE ASSOCIATION - A technique that enables a portable device to be automatically associated with a plurality of computers. Information that a computer can use to authenticate a portable device and establish a trusted relationship prior to creating an association with the portable device is created and stored in a data store that is accessible by a plurality of computers and is associated with a user of the portable device. When a computer discovers such a portable device with which it is not yet associated, the computer can identify a user logged into the computer and use information identifying the user to retrieve authentication information that is device independent and is expected to be presented by the portable device to authenticate it and allow automatic association. | 02-18-2010 |
20110225640 | CLOUD-BASED DEVICE INFORMATION STORAGE - Device information for each of multiple devices associated with a user account is maintained by a cloud service. The device information can include credential information allowing the device to be accessed by other ones of the multiple devices, remote access information indicating how the device can be accessed by other ones of the multiple devices on other networks, and property information including settings and/or device drivers for the device. The device information for each of the multiple devices is made available to other ones of the multiple devices, and can be used by the multiple devices to access one another and provide a consistent user experience across the multiple devices. | 09-15-2011 |
20120284702 | BINDING APPLICATIONS TO DEVICE CAPABILITIES - Installation data associated with a hardware device is obtained (e.g., at the time the device is installed on a computing device). Identifiers of applications that are allowed to access a capability of the hardware device are identified from the installation data and stored in a device permissions record as being allowed to access the capability of the hardware device. Subsequently, a request to access the capability of the hardware device is received from an application. A check is made as to whether the application is identified in a device permissions record as being allowed to access the capability of the hardware device. The application is allowed to access the capability of the hardware device if the device permissions record indicates the application is allowed to access the capability of the hardware device, and otherwise the request from the application is denied. | 11-08-2012 |
20130067531 | Access Brokering Based on Declarations and Consent - Embodiments include processes, systems, and devices for brokering application access to capabilities, such as device capabilities. An access broker receives requests from applications to access capabilities. The access broker determines whether to grant access based at least in part on whether the application manifest declares the capability. The access broker also may cause a user interface element to be displayed requesting user consent to the access request. Also, an in-application user interface element is provided that displays capability access settings for a particular application. The in-application user interface element includes selectable options for changing those settings. Changes in those settings via the user interface update the settings in the access broker. | 03-14-2013 |
20130125144 | Device Display Object Infrastructure - Multi-function devices expose multiple functions to device drivers or other lower-level software. Device function providers can interface with such drivers or lower-level software and can provide information, including device identifiers regarding such functions, to a device display object infrastructure. A device display object can then be created that encompasses one or more functions such that, in one embodiment, the device display object corresponds to a single, physical multi-function device. Alternatively, any combination of functionality from one or more physical devices can be combined into a single device display object representing a virtual multi-function device. Properties of the device display object can be set with reference to user-specified settings, remotely maintained metadata, locally available metadata, and information associated with each function. Functions can be ranked such that, if there is a conflict, information from more highly ranked functions is used to set the properties of the device display object. | 05-16-2013 |
20130151737 | Multi-function Device ID with Unique Identifier - A computer system that recognizes multi-function devices and associates functions with multi-function devices. Each multi-function device may be represented by a multi-function object, allowing tools, applications or other components within the computer to take actions relating to the entire device or relating to a function based on the association of that function with other functions in the same device. These actions include displaying information about devices, instead of or in addition to information about functions. Actions also include selecting functions based on proximity within a device. Functions may be associated with a multi-function device using a unique device identifier provided by the device or generated for the function based on a connection hierarchy between functions and the computer. Devices may be configured to provide the same identifier regardless of the transport over which the device is accessed. | 06-13-2013 |
20150058955 | Cloud-Based Device Information Storage - Device information for each of multiple devices associated with a user account is maintained by a cloud service. The device information can include credential information allowing the device to be accessed by other ones of the multiple devices, remote access information indicating how the device can be accessed by other ones of the multiple devices on other networks, and property information including settings and/or device drivers for the device. The device information for each of the multiple devices is made available to other ones of the multiple devices, and can be used by the multiple devices to access one another and provide a consistent user experience across the multiple devices. | 02-26-2015 |