# US 2012/0254279 A1 · System and method for service mobility

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

- Number: US 2012/0254279 A1
- Document ID: US20120254279A1
- Status: Published application
- Kind: A1
- Application number: 13/078,948
- Filed: 2011-04-02
- Published: 2012-10-04
- Earliest claimed: 2011-04-02
- Assignees: Recursion Software, Inc.
- Inventors: Robert W. Peterson; Thomas T. Wheeler
- Web page: https://patentgrep.com/patent/US20120254279A1

## CPC

- G06F 9/5055: {considering software capabilities, i.e. software resources associated or available to the machine}
- H04L 67/563: Data redirection of data network streams
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

When service requirements require moving of services registered with an object request broker (ORB) at a source server, continuity of service to service requests from clients may be provided by queuing the service requests at the source server. A server context with the same GUID as a source server context may be established at a destination server. URLs for the moved services may be registered with a destination ORB which may then begin receiving service requests. The source server may then respond to the queued service requests with respective URLs for the services registered at the destination ORB. Endpoints at the clients may be updated with the new URLs prior to resending the service requests. The movement of the ORB to the destination server may thus be transparent to the client application.

## Claims

### Claim 1

A method for moving an object request broker comprising at least one registered service from a source server to a destination server, the method comprising:
suspending processing of new service requests for the at least one registered service in the source server;
queuing service requests received by the source server from one or more clients after the suspension of service request processing;
establishing a destination object request broker in a destination server;
communicating the at least one service from the source server to the destination object request broker;
registering the at least one service in the destination object request broker; and
responding to the queued service requests from the source server to the one or more clients with an identity of the destination object request broker.

### Claim 2 (depends on 1)

The method of claim 1 wherein establishing a destination object request broker comprises establishing a destination server context at the destination server, the destination server context comprising the destination object request broker and a server context identity that is the same as a server context identity of a source server context.

### Claim 3 (depends on 2)

The method of claim 2 wherein the server context identity is independent of a network address of the source server.

### Claim 4 (depends on 1)

The method of claim 1 comprising communicating a URL of the at least one service registered with the destination object request broker to the source server.

### Claim 5 (depends on 4)

The method of claim 4 wherein responding to the queued service requests comprises communicating a URL for a requested service received from the destination server context by the source server to the client.

### Claim 6 (depends on 5)

The method of claim 5 comprising:
receiving a response to a queued request in a client; and
updating an endpoint in the client with a URL indicated in the response.

### Claim 7 (depends on 6)

The method of claim 6 comprising:
creating a new connection at the client to the destination server using the URL indicated in the response;
retrieving a cached service request in the client;
resending the cached service request using the new connection.

### Claim 8 (depends on 1)

The method of claim 1 comprising deconstructing a source server context after responding to the plurality of queued service requests.

### Claim 9 (depends on 1)

The method of claim 1 comprising:
communicating a URL of each service registered with a source server to the destination server; and
creating a server connection in the destination server for each URL communicated from the source server.

### Claim 10 (depends on 9)

The method of claim 9 wherein suspending processing of new service requests is performed after the server connections are created in the destination server.

### Claim 11

A method for requesting services from a client application to a source server, the method comprising:
sending a service request to the source server using a URL stored in an endpoint at the client;
caching the service request in the client;
receiving a response to the service request from the source server, the response indicating a destination server;
retrieving the cached service request; and
resending the cached service request to the destination server.

### Claim 12 (depends on 11)

The method of claim 11 comprising updating the URL stored in the endpoint with a URL received in the response from the source server.

### Claim 13

A system comprising:
a source server comprising a source server application executing on the source server, the source server application configured to:
generate a source server context comprising a server context identity and a source object request broker;
register one or more services with the source object request broker; and
communicate a move command to the destination server, the move command indicating the one or more services and the server context identity of the source server context; and
a destination server comprising a destination server application executing on the destination server, the destination server application configured to:
receive the move command from the source server application;
establish a destination server context in response to the move command, the destination server context comprising the server context identity and a destination object request broker; and
register the one or more services with the destination object request broker.

### Claim 14 (depends on 13)

The system of claim 13 comprising at least one client comprising a client application executing on the client, the client application configured to:
generate a proxy that references at least one of the one or more services, the proxy comprising a client context that comprises an endpoint that stores a URL of the at least one service;
generate a service request using the URL of the endpoint; and
send the service request in accordance with the URL.

### Claim 15 (depends on 14)

The system of claim 14 wherein the source server application is configured to:
receive the service request from the client application;
queue the service request while the one or more services are being moved to the destination object request broker;
respond to the service request after the one or more services have been registered in the destination object request broker, a response to the service request indicating a URL of the requested service at the destination object request broker.

### Claim 16 (depends on 15)

The system of claim 15 wherein the client application is configured to:
cache the service request;
receive the response from the source server;
update the endpoint with the URL indicated in the response;
retrieve the cached service request;
resend the service request using the updated URL.

### Claim 17

The system of 13 wherein the identity of the server context is independent of an identity of the source server.

### Claim 18 (depends on 13)

The system of claim 13 wherein the destination server application is configured to communicate a URL of the at least one service registered with the destination object request broker to the source server.

### Claim 19 (depends on 13)

The system of claim 13 wherein the source server application is configured to queue each service request received from a client application for a service registered at the source object request broker while the one or more services are moved to the destination object request broker.

### Claim 20 (depends on 13)

The system of claim 13 wherein the source server application is configured to respond to each queued service request with an identity of the requested service at the destination object request broker and to deconstruct the source server context after responding to each queued request.
