Microsoft Technology Licensing, LLC

National Products Limited

Scott Daniel Anderson

David John Linsley

Jeffrey D Carnevali

Kinshumann Kinshumann

Hari R Pulapaka

Md Nazmus Sakib

Jeffrey A Sutherland

Deskin M Miller

Stefan Thom

Arun Upadhyaya Kishan

Scott Randall Shell

Robert Karl Spiger

James A Schwartz, Jr

Nicholas Stephen Judge

Jeffrey Richard McKune

Niraj Majmudar

Thomas W Caldwell

Erik Lee Holt

Magnus Bo Gustaf Nyström

Douglas M MacIver

Benjamin M Schultz

Adrian Mihail Marinescu

Mark Fishel Novak

Frederick Justus Smith

Innokentiy Basmov

Emily Nicole Wilson

David Bradley Probert, Jr

Alain Franck Gefflaut

Alex Mark Semenko

Nathan Jeffrey Ide

Magnus Nyström

Giridhar Viswanathan

Ning Zhang

Richard Allen Pletcher

James Anthony Schwartz, Jr

Charles Glenn Jeffries

Hakki Tunc Bostanci

Margarit Simeonov Chenchev

Malcolm James Smith

Kinshuman Kinshumann

Michael J Grass

Stefan Michael Gottschalk

Magnus Nystrom

Kinshumann

Alex Bendetov

James Aaron Holmes

Mikael P Horal

Andrey Shedel

JianMing M Zhou

Deepak Jagannathan Manohar

Vandana Gunupudi

Troy E Shaw

Aaron M Farmer

Thomas Walter Caldwell, Iii

Jake Parker

Jianming Zhou

Nicholas S Judge

Niraj V Majmudar

Douglas M Maciver

A dock for an electronic device includes a base configured to fit over at least a portion of a back surface of the electronic device, the base including a back surface and defining a first opening through the base; a tray extending from the base; and a heater module coupled, or coupleable, to the back surface of the base over the first opening. The heater module includes a fan to draw air to generate an air flow through the first opening of the base, a heating element to heat the drawn air, a temperature sensor coupled, or coupleable, to the base to monitor a temperature of the dock, the electronic device, or the heated air, and a processor configured to turn the fan and the heating element on or off in response to a temperature monitored by the temperature sensor.

Heating module for electronic device dock and methods of making and using

A dock for a mobile device includes a housing; a mobile device connector disposed at least partially within the housing; a power source connector for coupling a power source to the dock, wherein the power source connector is electrically coupled to the mobile device connector; a controller disposed in the housing for facilitating data transfer between the mobile device and a data device, wherein the controller is electrically coupled to the mobile device connector; a data device connector for coupling the data device to the dock, wherein the data device connector is electrically coupled to the controller; wherein the controller, data device connector, power source connector, and mobile device connector are configured for simultaneously providing data transfer between the mobile device and the data device and charging the mobile device using the power source with a charging current of at least 1 Amp.

Docks for mobile devices with simultaneous data transfer and charging and systems and methods using the docks

An application is installed on a computing device from an application package. An origin of the application (e.g., a managed installer for an enterprise, a reputation checking service) is propagated to files written to a storage device of the computing device as part of the installation, such as by writing origin information to the storage device as metadata associated with the file. The origin information for a file, in conjunction with a policy on the computing device specifying one or more trusted origins for applications on the computing device, is used to identify whether a particular action can be taken with and/or by the file. These actions can include, for example, execution of an application from an executable file. If the origin information for a file indicates an origin that is a trusted origin specified by the policy, then the action can be performed.

Propagating origin information for applications during application installation

A mobile device dock arrangement includes a mobile device dock and a near field communication (NFC) device. The NFC device includes a first NFC antenna for obtaining data from a readable object when the NFC device is operatively coupled to the NFC reader, where the first NFC antenna permits positioning the first NFC antenna remote from the mobile device dock and the mobile device for obtaining the data from the readable object at a position remote from the mobile device dock and the mobile device; a second NFC antenna coupleable to the mobile device dock and configured, when coupled to the mobile device dock, for presenting the data in readable form to the NFC reader of the mobile device; and a cord coupled, or coupleable, to the first NFC antenna and the second NFC antenna for carrying the data from the first NFC antenna to the second NFC antenna.

Remote repeater device for mobile device dock and methods of making and using

A USB cable that includes a cable coupling element selected from a first connector, a printed circuit board, or a device, as well as a multi-port connector that includes a multi-port connector including a housing, at least two ports defined by the housing, at least two female USB connectors disposed within the housing, and at least two retention arms extending from the housing. The USB cable also includes conductors electrically coupling the first connector to the at least two female USB connectors and a jacket extending between the first connector and the multi-port connector, wherein the conductors are at least partially disposed within the jacket. In another USB cable, in addition to or as an alternative to the retention arms, each of the at least two female USB connectors is spaced at least 10 mm from the opening of the port through which the female USB connector is accessible.

Multi-port USB cable with cable retention and methods of making and using

A case for a mobile device includes a flexible covering defining a cavity for receiving and holding the mobile device; a rigid frame at least partially disposed within the flexible covering; and an adapter disposed at least partially within the rigid frame and the flexible covering, the adapter including first contacts, a male plug extending into the cavity, and second contacts disposed on the male plug and electrically coupled to the first contacts; where the adapter, in combination with at least one of the flexible covering or the rigid frame, defines a first male structure extending away from the cavity, where the first contacts of the adapter are disposed on the first male structure. Another case includes at least the flexible covering and adapter and also includes a female connector electrically coupled to the second contacts and having an opening disposed on the first male structure.

Cases for mobile devices with a flexible covering and rigid frame or with two different connector arrangements and methods of making and using

Examples described herein generally relate to a computer device including a memory, and at least one processor configured to determine whether to allow execution of an application file on the computer device. The processor receives a command to execute a file. The processor determines whether the file is associated with a package reputation of an installation package. The processor determines a file reputation of the file. The processor determines whether to allow execution of the file based on a combination of the file reputation of the file and whether the file is associated with the good package reputation.

Binary authorization based on both file and package attributes

A case for a mobile device includes a cover defining a cavity for receiving and holding the mobile device; an adapter disposed at least partially within the cover; and a light arrangement disposed within or adjacent to the cover. The adapter includes first contacts disposed on an exterior of the case, a male plug extending into the cavity for insertion into a female socket of the mobile device, and second contacts disposed on the male plug and electrically coupled to the first contacts. The light arrangement includes a light and a light actuator for manually turning the light on or off. The light is electrically coupled to at least one of the first contacts or the second contacts to obtain power from the mobile device received in the cover or from an external device electrically coupled to the first contacts.

Cases for mobile devices incorporating a light within the case and methods of making and using

Facilities are provided to secure guest runtime environments (GREs). Security policy specifications may be associated with GREs. A GRE's security policy may be specific to the GRE and may also include security policy inherited from higher levels such as a host operating environment. The security policy of a GRE specifies restrictions and/or permissions for activities that may be performed within the scope of execution of the GRE. A GRE's security policy may limit what the GRE's guest software may do within the GRE. Restrictions/permissions may be applied to objects such as files, configuration data, and the like. Security specifications may be applied to execution initiated within a GRE. A GRE's security specification may restrict/permit executable objects from loading and executing within the GRE. The executability or accessibility of objects may be conditioned on factors such as the health/integrity of the GRE, the host system, requested files, and others.

Securing virtual execution environments

Anti-malware process protection techniques are described. In one or more implementations, an anti-malware process is launched. The anti-malware process is verified based at least in part on an anti-malware driver that contains certificate pairs which contain an identity that is signed with the trusted certificate from a verified source. After the anti-malware process is verified, the anti-malware process may be assigned a protection level, and an administrative user may be prevented from altering the anti-malware process.

Protecting anti-malware processes

Embodiments of the disclosure provide access to data in a compressed container through dynamic redirection, without storing decompressed data in persistent memory. The compressed container is stored in a first portion of memory. User data and reference files, with redirect pointers, for accessing corresponding files in the compressed container are stored in a second portion of memory. A command to access data is detected by a computing device. The redirect pointer in the reference file associated with the command redirects access to the corresponding compressed version of data stored in the compressed container. The corresponding accessed compressed version of data is decompressed on the fly and provided in response to the command without storing the decompressed data in persistent memory. Some embodiments provide integrity protection to validate the data coming from the compressed container.

Accessing data in a compressed container through dynamic redirection

Anti-malware process protection techniques are described. In one or more implementations, an anti-malware process is launched. The anti-malware process is verified based at least in part on an anti-malware driver that contains certificates which contain an identity that is signed with the trusted certificate from a verified source. After the anti-malware process is verified, the anti-malware process may be assigned a protection level, and an administrative user may be prevented from altering the anti-malware process.

In a pre-operating system environment on a device prior to loading and running an operating system on the device, a policy identifying configuration settings for the operating system is obtained. The operating system itself is prevented from changing this policy, but the policy can be changed under certain circumstances by components of the pre-operating system environment. The policy is compared to configuration values used by the operating system, and the operating system is allowed to boot with the configuration values if the configuration values satisfy the policy. However, if the configuration values do not satisfy the policy, then a responsive action is taken.

Protecting operating system configuration values using a policy identifying operating system configuration settings

Growing community of inventors

Kirkland, WA, United States of America

Scott Daniel Anderson