# US 2012/0233595 A1 · Service definition document for providing blended services utilizing multiple service endpoints

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

- Number: US 2012/0233595 A1
- Document ID: US20120233595A1
- Status: Published application
- Kind: A1
- Application number: 13/109,826
- Filed: 2011-05-17
- Published: 2012-09-13
- Earliest claimed: 2011-03-10
- Assignees: Infosys Technologies Limited
- Inventors: Ravindra K. Ghanathe; Subrahmanya R. Mruthyunjaya; Rashmi Shenoy
- Web page: https://patentgrep.com/patent/US20120233595A1

## CPC

- G06F 8/30: Creation or generation of source code
- G06F 8/10: Requirements analysis; Specification techniques
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A service definition document (SDD) framework is provided for defining blended services that utilize multiple service endpoints. The SDD framework can comprise a first category that defines a service endpoint representing a blended service, a second category that defines a plurality of service endpoints utilized by the blended service, and a third category that defines execution of the blended service. Blended services can be provided by creating a model of a blended service and saving a representation of the model of the blended service in a service definition document (SDD) framework. A blended service defined in a SDD framework can be executed by receiving the SDD and executing the blended service as defined by the SDD using a service execution environment (SEE).

## Claims

### Claim 1

A service definition document (SDD) framework for defining blended service software applications that utilize multiple service endpoints, the SDD framework comprising:
a first category of the SDD, wherein the first category of the SDD defines a service endpoint representing a blended service;
a second category of the SDD, wherein the second category of the SDD defines a plurality of other service endpoints utilized by the blended service; and
a third category of the SDD, wherein the third category of the SDD defines execution of the blended service.

### Claim 2 (depends on 1)

The SDD framework of claim 1, wherein the first category of the SDD defines input parameters and output parameters for the blended service. 15

### Claim 3 (depends on 1)

The SDD framework of claim 1, wherein the SDD is defined in an extensible markup language (XML) format.

### Claim 4 (depends on 1)

The SDD framework of claim 1, wherein the second category of the SDD defines service access adapters for the plurality of other service endpoints.

### Claim 5 (depends on 1)

The SDD framework of claim 1, wherein the third category of the SDD defines gateways which indicate sequence flow of the blended service, including gateways which define parallel execution, gateways which define joining from parallel execution, and gateways which define synchronous/asynchronous communication.

### Claim 6 (depends on 1)

The SDD framework of claim 1, wherein the blended service is deployed for use by users by executing the SDD using a service execution environment.

### Claim 7 (depends on 1)

The SDD framework of claim 1, wherein the blended service is executed as a client-side application.

### Claim 8 (depends on 1)

The SDD framework of claim 1, wherein the plurality of service endpoints comprises at least one primary service endpoint and at least one blended service endpoint.

### Claim 9 (depends on 1)

The SDD framework of claim 1, wherein the SDD framework supports operation of the blended service according to a state machine model, wherein the state machine model comprises the following components:
a start component representing start of the blended service;
a synchronous service component;
an asynchronous service component;
a fork state component representing a fork in the blended service;
a join state component representing a join of a fork in the blended service;
a timer-wait component for triggering a timer-based event; and
an end component representing a final state of the blended service.

### Claim 10

A method, implemented at least in part by a computing device, for defining blended service software applications that utilize multiple service endpoints using a service definition document (SDD) framework, the method comprising:
creating, using a graphical blended service creation environment, a model of a blended service; and
saving, using the graphical blended service creation environment, a representation of the model of the blended service as a service definition document (SDD) framework;
wherein the SDD framework comprises:
a first category of the SDD, wherein the first category of the SDD defines a service endpoint representing a blended service;
a second category of the SDD, wherein the second category of the SDD defines a plurality of other service endpoints utilized by the blended service; and
a third category of the SDD, wherein the third category of the SDD defines execution of the blended service.

### Claim 11 (depends on 10)

The method of claim 10, wherein the first category of the SDD defines input parameters and output parameters for the blended service;
wherein the second category of the SDD defines service access adapters for the plurality of other service endpoints; and
wherein the third category of the SDD defines gateways which indicate sequence flow of the blended service, including gateways which define parallel execution, gateways which define joining from parallel execution, and gateways which define synchronous/asynchronous communication.

### Claim 12 (depends on 10)

The method of claim 10, wherein the SDD is defined in an extensible markup language (XML) format.

### Claim 13 (depends on 10)

The method of claim 10, further comprising:
deploying, using a service execution environment (SEE), the blended service for use by users, wherein the deploying comprises executing the SDD using the SEE.

### Claim 14 (depends on 10)

The method of claim 10, wherein the blended service is executed as a client-side application.

### Claim 15 (depends on 10)

The method of claim 10, wherein the plurality of service endpoints comprises at least one primary service endpoint and at least one blended service endpoint.

### Claim 16

A method, implemented at least in part by a service execution environment (SEE) running on a computing device, for executing a blended service using a service definition document (SDD), the method comprising:
receiving, by the SEE, the service definition document, wherein the SDD defines the blended service, wherein the blended service integrates information from a plurality of service endpoints, and wherein the plurality of service endpoints are a plurality of different service endpoints provided by a plurality of different service providers; and
executing, by the SEE, the blended service as defined by the SDD, wherein the executing the blended service comprises:
connecting, by the SEE, to the plurality of service endpoints, wherein the plurality of service endpoints are located remotely, via a communication network, from the SEE.

### Claim 17 (depends on 16)

The method of claim 16, wherein the SDD is defined by a framework comprising:
a first category of the SDD, wherein the first category of the SDD defines a service endpoint representing a blended service;
a second category of the SDD, wherein the second category of the SDD defines the plurality of service endpoints utilized by the blended service; and
a third category of the SDD, wherein the third category of the SDD defines execution of the blended service.

### Claim 18 (depends on 17)

The method of claim 17, wherein the first category of the SDD defines input parameters and output parameters for the blended service;
wherein the second category of the SDD defines service access adapters for the plurality of service endpoints; and
wherein the third category of the SDD defines gateways which indicate sequence flow of the blended service, including gateways which define parallel execution, gateways which define joining from parallel execution, and gateways which define synchronous/asynchronous communication.

### Claim 19 (depends on 17)

The method of claim 17, wherein the SDD is defined in an extensible markup language (XML) format.

### Claim 20 (depends on 16)

The method of claim 16, wherein the plurality of service endpoints comprises at least one primary service endpoint and at least one blended service endpoint.
