Microsoft Technology Licensing, LLC

Other

Sand Codex

Uber Technologies, Inc.

Seadragon Software, Inc.

Microsoft Corporation

Blaise Aguera Y Arcas

Stephen L Lawler

Eyal Ofek

Steven Mark Drucker

Donald James Lindsay

Brett David Brewer

Karim Taji Farouki

Gary William Flake

Markus Unger

Benny Schlesinger

Eran Yariv

Scott Vernon Fynn

Adam P Sheppard

Douglas Christopher Burger

Richard S Szeliski

Donald Allen Barnett

Hen Fitoussi

David Maxwell Gedye

Daniel Massey

Gur Kimchi

Sudipta Narayan Sinha

Michael Kroepfl

Eric Joel Stollnitz

Johannes P Kopf

Julian R Walker

Bart J F De Smet

John Daniell Hebert

Brian C Beckman

Michael F Cohen

Avi Bar-Zeev

Jeffrey Jon Weir

Scott M Isaacs

Yonatan Wexler

Konrad Karner

Tomasz Kasperkiewicz

Saar Yahalom

Ian A Gilman

Meir Ben-Itay

Pasquale DeMaio

Matthew Bret MacLaurin

Gonzalo Alberto Ramos

Christian James Colando

Tomasz S M Kasperkiewicz

Christina Summer Chen

Eric Paul Bennett

Ariel J Lazier

Jonathan Robert Dughi

Margaret Novotny

Bryan Kent Ressler

Alfred Astort

Roberto R Molinari

Guy Kashtan

Dan Hou

Jeffery David Howard

Tony Ernst

Steven Drucker

Gary W Flake

Brett D Brewer

Karim Farouki

Andrew David Wilson

Billy P Chen

Asta Jane Roseway

Shira Weinberg

Julio Estrada

Anthony T Chor

Eric Steven Anderson

Adam Sheppard

Christopher Stephen Messer

Timo Pekka Pylvaenaeinen

Donald A Barnett

Konrad Kamer

Scott Isaacs

Johannes Kopf

Johannes Peter Kopf

Richard Stephen Szeliski

In server/client architectures, the server application and client applications are often developed in different languages and execute in different environments specialized for the different contexts of each application (e.g., low-level, performant, platform-specialized, and stateless instructions on the server, and high-level, flexible, platform-agnostic, and stateful languages on the client) and are often executed on different devices. Convergence of these environments (e.g., server-side JavaScript using Node.js) enables the provision of a server that services client applications executing on the same device. The local server may monitor local events occurring on the device, and may execute one or more server scripts associated with particular local events on behalf of local clients subscribing to the local event (e.g., via a subscription model). These techniques may enable development of local event services in the same language and environment as client applications, and the use of server-side code in the provision of local event service.

Event service for local client applications through local server

One or more techniques and/or systems are provided for ordering images for panorama stitching and/or for providing a focal point indicator for image capture. For example, one or more images, which may be stitched together to create a panorama of a scene, may be stored within an image stack according to one or more ordering preferences, such as where manually captured images are stored within a first/higher priority region of the image stack as compared to automatically captured images. One or more images within the image stack may be stitched according to a stitching order to create the panorama, such as using images in the first region for a foreground of the panorama. Also, a current position of a camera may be tracked and compared with a focal point of a scene to generate a focal point indicator to assist with capturing a new/current image of the scene.

Image capture and ordering

In the field of computing, many scenarios involve the execution of an application within a virtual environment of a device (e.g., web applications executing within a web browser). Interactions between applications and device components are often enabled through hardware abstractions or component application programming interfaces (API), but such interactions may provide more limited and/or inconsistent access to component capabilities for virtually executing applications than for native applications. Instead, the device may provide hardware interaction as a service to the virtual environment utilizing a callback model, wherein applications within the virtual environment initiate component request specifying a callback, and the device initiates the component requests with the components and invokes associated callbacks upon completion of a component request. This model may enable the applications to interact with the full capability set of the components, and may reduce blocked execution of the application within the virtual application in furtherance of application performance.

Inversion-of-control component service models for virtual environments

Various embodiments provide techniques for geographic navigation via one or more block views. According to some embodiments, a block view can include a visual image of a geographic location that is visually similar to a panoramic image. In some example implementations, a block view can be scrolled to navigate images of a geographic location. In one or more embodiments, a bubble view can be displayed of one or more locations within the block view. The bubble view can include a zoomed image of one or more aspects of a block view. Further to some embodiments, a map view can be utilized along with the block view and/or the bubble view. The map view can include a two-dimensional representation of the geographic location from an aerial perspective, and can include a more general level of detail concerning the geographic location, such as streets, cities, states, bodies of water, and so on.

Block view for geographic navigation

A three dimensional (3D) model of an object or environment may be created from images and other information of the object or environment. The 3D model may be created by aligning the images. The 3D model may include surfaces that are based on surfaces of the object or environment. The 3D model may be displayed, exported, modified and so on.

Procedural authoring

Personalized services often utilize individual profiles, such as social network profiles, product purchase histories, or browsing histories. However, personalization may exhibit or imply a familiarity level between the service and the individual that is beyond the individual's comfort level. Presented herein are techniques for adapting personalized services to request supplemental individual information only within a current familiarity stage that has been established by the individual with the service, and only to provide a requested usage of a service. Such solicitation may inform the individual of the intended usage of the requested information. Usages that may involve more sensitive information may be predicated upon requesting and receiving individual consent from the individual to advance to a higher familiarity stage. The user may be permitted to provide individual consent to advancing to a higher familiarity stage only for a particular service, and/or only temporarily for a particular usage of the service.

Service personalization with familiarity sensitivity

One or more techniques and/or systems are provided for cloud service hosting on a client device. For example, a cloud service may comprise data and/or functionality that may be consumed by apps on client devices. The cloud service may be hosted within a cloud computing environment because a client device may not comprise processing resources capable of hosting the entire cloud service. Accordingly, a local service may be deployed on a client device as a local instantiation of the cloud service. For example, the local service may be a local instantiation of at least a portion of the data and/or functionality of the cloud service. In this way, the local service may utilize fewer resources than the cloud service, and may locally process requests from apps on the client device. For example, a map local service may process requests using map data locally cached from a map cloud service.

Cloud service hosting on client device

Among other things, one or more techniques and/or systems are provided for mitigating redundant pixel texture contribution for texturing a geometry. That is, the geometry may represent a multidimensional surface of a scene, such as a city. The geometry may be textured using one or more texture images (e.g., an image comprising color values and/or depth values) depicting the scene from various view directions (e.g., a top-down view, an oblique view, etc.). Because more than one texture image may contribute to texturing a pixel of the geometry (e.g., due to overlapping views of the scene), redundant pixel texture contribution may arise. Accordingly, a redundant textured pixel within a texture image may be knocked out (e.g., in-painted) from the texture image to generate a modified texture image that may be relatively efficient to store and/or stream to a client due to enhanced compression of the modified texture image.

Redundant pixel mitigation

Among other things, one or more techniques and/or systems are provided for defining a view direction for a texture image used to texture a geometry. That is, a geometry may represent a multi-dimensional surface of a scene, such as a city. The geometry may be textured using one or more texture images depicting the scene from various view directions. Because more than one texture image may contribute to texturing portions of the geometry, a view direction for a texture image may be selectively defined based upon a coverage metric associated with an amount of non-textured geometry pixels that are textured by the texture image along the view direction. In an example, a texture image may be defined according to a customized configuration, such as a spherical configuration, a cylindrical configuration, etc. In this way, redundant texturing of the geometry may be mitigated based upon the selectively identified view direction(s).

View direction determination

Systems and methods for providing client-side integration of apps and services is provided. An integration framework execution upon a computing device provides integration of various apps, applications, services, sensors and the like. Upon receiving a request for a service, the integration framework accesses a registry of a plurality of services of a respective plurality of providers registered with the integration framework. Each of the services is registered with the integration framework is associated with a trust level of a hierarchy of trust levels. The integration framework iteratively searches the registry for a provider of the requested service according to the hierarchy of trust levels, beginning with the most trusted level of the trust levels to the less trusted trust level until a provider of the requested service is found or until all levels of the hierarchy are searched without finding a provider of the requested service.

Client-side integration framework of services

Systems and methods of a personal daemon, executing as a background process on a mobile computing device, for providing personal assistant to an associated user is presented. Also executing on the mobile computing device is a scheduling manager. The personal daemon executes one or more personal assistance actions on behalf of the associated user. The scheduling manager responds to events in support of the personal daemon. More particularly, in response to receiving an event the scheduling manager determines a set of apps that are responsive to the received event and from that set of apps, identifies at least a first subset of apps for execution on the mobile computing device. The scheduling manager receives feedback information regarding the usefulness of the executed apps of the first subset of apps and updates the associated score of each of the apps of the first subset of apps.

Incentive-based app execution

A badge may be assigned to a person, where the badge represents a characteristic or recurrent behavior of the person. A query may be associated with a badge, and the query may be continually used in a search request in combination with the person's context, thereby allowing the person to be continually provided with fresh results that may be relevant to the person's durable characteristics and current context. In one example, the person carries a handheld device, and the results are presented to the user on the user's desktop or lock screen. The act of providing the results may be triggered in various ways, such as movement of the person who carries the device, or the availability of sufficiently high-quality results.

Persistent contextual searches

Growing community of inventors

Seattle, WA, United States of America

Blaise Aguera Y Arcas