# US 2012/0254239 A1 · Locating and executing objects in a distributed network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254239 A1
- Document ID: US20120254239A1
- Status: Published application
- Kind: A1
- Application number: 13/074,260
- Filed: 2011-03-29
- Published: 2012-10-04
- Earliest claimed: 2011-03-29
- Assignees: Microsoft Corporation
- Inventors: Ray Patch; Liviu Tiganus; Rajeev Chauhan
- Web page: https://patentgrep.com/patent/US20120254239A1

## CPC

- G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links}
- G06F 9/548: {Object oriented; Remote method invocation [RMI] (non-remote method invocation G06F9/449)}
- G06F 16/986: {Document structures and storage, e.g. HTML extensions}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The subject disclosure relates to interaction and execution of objects in a distributed network or in the cloud. Each object comprises a Uniform Resource Identifier (URI) path that names the object in the cloud through a distributed object directory. A client device can directly interface with a live instance of an object based on the URI path. The object can be agnostic to remote procedure call semantics. In some aspects, the object can be connected to an interacted with either remotely or locally. Further, single instances or multiple instances of the object can exist at substantially the same time.

## Claims

### Claim 1

A system, comprising:
an object manager component configured to access an object based on a request for a Uniform Resource Identifier (URI) received from a client device; and
an object processing component configured to interact remotely with the object.

### Claim 2 (depends on 1)

The system of claim 1, wherein the object is agnostic to remote procedures.

### Claim 3 (depends on 1)

The system of claim 1, wherein the object manager component is configured to connect to a live instance of the object.

### Claim 4 (depends on 1)

The system of claim 1, wherein the object processing component is configured to receive real-time feedback of a condition of the object.

### Claim 5 (depends on 1)

The system of claim 1, wherein the object processing component is configured to indirectly interact with at least a second object that performs at least one function on behalf of the object.

### Claim 6 (depends on 1)

The system of claim 1, wherein the object is configured to offload at least a portion of its functionality to a distributed object, wherein the object processing component is unaware of an existence of the distributed object.

### Claim 7 (depends on 1)

The system of claim 1, wherein the object processing component is configured to interact with the object anonymously.

### Claim 8 (depends on 1)

The system of claim 1, wherein the URI is a relative URI or an absolute URI.

### Claim 9 (depends on 1)

The system of claim 1, further comprising an abstraction layer configured to communicate with the client device on behalf of the object and to communicate with the object on behalf of the client device.

### Claim 10

A method, comprising:
writing an object to a web-service;
saving the object in a database associated with the web-service; and
executing the object based on receipt of a request directed to an Uniform Resource Identifier (URI).

### Claim 11 (depends on 10)

The method of claim 10, wherein the saving the object comprises assigning the URI to the object, wherein the URI is universal.

### Claim 12 (depends on 10)

The method of claim 10, wherein the executing is based on the request from a first device, the method further comprising:
ascertaining the first device has disconnected from the object;
saving a first version of the object;
receiving a second request from the first device or a second device; and
executing the first version of the object as a function of the second request.

### Claim 13 (depends on 10)

The method of claim 10, further comprising:
processing at least one change to the object, wherein the request and the at least one change are received from a first device; and
automatically saving the at least one change in the database associated with the web-service.

### Claim 14 (depends on 13)

The method of claim 13, further comprising:
receiving a second request from a second device; and
presenting the object with the at least one change to the second device.

### Claim 15 (depends on 10)

The method of claim 10, wherein the executing comprises interacting with at least a second object, wherein the second object is associated with the object.

### Claim 16

A method for distributed execution of an object, comprising:
receiving a call for the object, wherein the object comprises a first sub-object and a second sub-object; and
executing at least one of the object, the first sub-object, and the second sub-object as a function of the call, wherein the execution is performed in the cloud.

### Claim 17 (depends on 16)

The method of claim 16, wherein the executing comprising moving at least a portion of the object during execution.

### Claim 18 (depends on 16)

The method of claim 16, wherein the executing comprises executing the first sub-object in a first machine and executing the second sub-object in a second machine.

### Claim 19 (depends on 16)

The method of claim 16, wherein the executing comprises offloading at least one function of the object to the first sub-object or the second sub-object.

### Claim 20 (depends on 16)

The method of claim 16, further comprising:
monitoring use of the object, the first sub-object, and the second sub-object; and
offloading functionality of at least one of the object, the first sub-object, and the second sub-object based on the monitoring.
