# US 2004/0064528 A1 · Safe interoperability among web services

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

- Number: US 2004/0064528 A1
- Document ID: US20040064528A1
- Status: Published application
- Kind: A1
- Application number: 10/262,551
- Filed: 2002-09-30
- Published: 2004-04-01
- Earliest claimed: 2002-09-30
- Assignees: Microsoft Corporation
- Inventors: L. Greg Meredith; Steve Bjorg; David Richter
- Web page: https://patentgrep.com/patent/US20040064528A1

## CPC

- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/14: Session management (for real-time applications in data packet communications networks H04L65/1066)
- H04L 69/12: Protocol engines
- H04L 69/329: in the application layer [OSI layer 7]
- H04L 61/10: of different types
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The joining of Web services is accomplished via a virtual contract through the use of safeties. The joining of Web services heightens the safe interoperability of Web services to create greater functionality than each Web service alone can provide. Moreover, because the joining of Web services is formed programmatically, Web services are more trustworthy, dependable, and available if the safeties of Web services are complied with. The programmatic joining reduces or eliminates mistakes, lost requests, faults in the face of invalid requests, or corrupt persisted data in the interoperability of Web services

## Claims

### Claim 1

A networked system for allowing Web services to communicate, comprising:
a first Web service for offering computing services, the first Web service including a first port for transmitting and receiving messages, the first port including a first porttype; and
a second Web service that desires the computing services offered by the first Web service, the second Web service including a second port for transmitting and receiving messages, the second port including a second porttype, the second port being fusable with the first port for safe access to the services offered by the first Web service if the second porttype is compatible with the first porttype.

### Claim 2 (depends on 1)

The networked system of claim 1, wherein the first Web service includes a third port for transmitting messages, and the second Web service provides a fourth port for receiving messages from the third port.

### Claim 3 (depends on 2)

The networked system of claim 2, wherein the fourth port is located on a third Web service, the fourth port being provided to the second Web service by the third Web service.

### Claim 4 (depends on 1)

The networked system of claim 1, wherein the first Web service is executed on a first computing device.

### Claim 5 (depends on 2)

The networked system of claim 2, wherein the second Web service is executed on a second computing device.

### Claim 6

A networked system for allowing Web services to communicate, comprising:
a first Web service offering a first set of services, the first Web service including a first safety that programmatically expresses safe access to the first set of services; and
a second Web service offering a second set of services, the second Web service including a second safety that programmatically expresses safe access to the second set of services, the second Web service accessing the first set of services and the first Web service accessing the second set of services if the second safety is able to programmatically align with the first safety.

### Claim 7 (depends on 6)

The networked system of claim 6, wherein the first set of services of the first Web service are accessible via a first set of operations, the first safety programmatically specifying allowable invocation permutations of the first set of operations.

### Claim 8 (depends on 7)

The networked system of claim 7, wherein the second set of services of the second Web service are accessible via a second set of operations, the second safety programmatically specifying allowable invocation permutations of the second set of operations.

### Claim 9 (depends on 8)

The networked system of claim 8, wherein the first Web service includes a first porttype, the first porttype including the first set of operations and the first safety.

### Claim 10 (depends on 9)

The networked system of claim 9, wherein the second Web service includes a second porttype, the second porttype including the second set of operations and the second safety.

### Claim 11

A networked system for allowing Web services to communicate, comprising:
a first Web service offering services, the first Web service including a safety that programmatically describes an order in which to access the offered services; and
a second Web service that desires he services offered by the first Web service, the second Web service accepting the safety of the first Web service to form a virtual contract with the first Web service so that the second Web service can access the offered services.

### Claim 12 (depends on 11)

The networked system of claim 11, wherein the first Web service includes a first porttype and the second Web service includes a second porttype, wherein the virtual contract is formed when the first porttype is compatible with the second porttype.

### Claim 13 (depends on 11)

The networked system of claim 11, wherein the second Web service includes another safety, wherein the virtual contract is formed when the safeties are acceptable to both the first Web service and the second Web service.

### Claim 14 (depends on 11)

The networked system of claim 11, wherein the first Web service includes a first port and the second Web service includes a second port, wherein the first port and the second port is fused when the virtual contract is formed.

### Claim 15 (depends on 11)

The networked system of claim 11, wherein the first Web service programmatically joins the second Web service when the virtual contract is created to form a composition Web service that comprises both the first Web service and the second Web service.

### Claim 16

A computer-readable medium having a customizable, tag-based data structure stored thereon for use by a Web service to evaluate safe interoperability with another Web service, the data structure comprising:
a porttype tag that is indicative of operations capable of being invoked by Web services; and
a safety tag that is indicative of a safety that programmatically specifies an order by which Web services invoke the operations.

### Claim 17 (depends on 16)

The computer-readable medium of claim 16, wherein the safety tag is nested within the porttype tag.

### Claim 18 (depends on 17)

The computer-readable medium of claim 17, wherein nesting within the porttype tag are one or more signature tags that are indicative of signatures of the operations.

### Claim 19 (depends on 17)

The computer-readable medium of claim 17, wherein nesting within the safety tag is a stop safety tag that is indicative of inactivity or termination of the safety.

### Claim 20 (depends on 17)

The computer-readable medium of claim 17, wherein nesting within the safety tag is a choice safety tag that is indicative of a choice between two safeties.

### Claim 21 (depends on 17)

The computer-readable medium of claim 17, wherein nesting within the safety tag is a menu safety tag that is indicative of a choice between two safeties.

### Claim 22 (depends on 17)

The computer-readable medium of claim 17, wherein nesting within the safety tag is a parallel safety tag that is indicative of parallel execution of two safeties.

### Claim 23 (depends on 17)

The computer-readable medium of claim 17, wherein nesting within the safety tag is a recursion safety tag that is indicative of a recursion of the safety.

### Claim 24 (depends on 17)

The computer-readable medium of claim 17, wherein nesting within the safety tag is a reference safety tag that is indicative of a name for the safety.

### Claim 25

A computer-implemented method for creating a specification for a Web service that corresponds to a program of the Web service, the method comprising:
creating a set of operations that are capable of being invoked by Web services; and
creating a safety that specifies the permissible invocation permutations of the set of operations.

### Claim 26 (depends on 25)

The method of claim 25, wherein the method further comprising creating a porttype and placing the set of operations and the safety in the porttype.

### Claim 27 (depends on 26)

The method of claim 26, wherein the method further comprising creating abstract definitions of the Web service and placing the porttype into the abstract definitions of the Web service.

### Claim 28 (depends on 27)

The method of claim 27, wherein the method further comprising creating concrete descriptions for the Web service.

### Claim 29

A computer-readable medium having computer-executable instructions for performing a method of creating a specification for a Web service that corresponds to a program of the Web service, the method comprising:
creating a set of operations that are capable of being invoked by Web services; and
creating a safety that specifies the permissible invocation permutations of the set of operations.

### Claim 30 (depends on 29)

The computer-readable medium of claim 29, wherein the method further comprising creating a porttype and placing the set of operations and the safety in the porttype.

### Claim 31 (depends on 30)

The computer-readable medium of claim 30, wherein the method further comprising creating abstract definitions of the Web service and placing the porttype into the abstract definitions of the Web service.

### Claim 32 (depends on 31)

The computer-readable medium of claim 31, wherein the method further comprising creating concrete descriptions for the Web service.

### Claim 33

A computer-implemented method for checking the compatibility of a first porttype of a first Web service and a second porttype of the second Web service, the method comprising:
extracting a first safety (S1) from the first porttype of the first Web service and a second safety (S2) from the second porttype of the second Web service; and
testing the compatibility of the first safety with the second safety by binding the first safety with the second safety (S1:=:S2) to determine whether the result of the binding is an input-guarded process.

### Claim 34 (depends on 33)

The method of claim 33, wherein the first Web service includes a first port of the first porttype and the second Web service includes a second port of the second porttype, the first port being fusable with the second port if the result of the binding is an input guarded process.

### Claim 35 (depends on 33)

The method of claim 33, wherein the first Web service includes a first port of the first porttype and the second Web service includes a second port of the second porttype, the first port being fusable with the second port if the result of the binding is not an input-guarded process and both the first Web service and the second Web service tolerate the fusing of the first port and the second port.

### Claim 36 (depends on 33)

The method of claim 33, wherein if the first safety is a stop safety (0) and the second safety is of the form (S), the result of the binding is the second safety.

### Claim 37 (depends on 33)

The method of claim 33, wherein if the first safety is a sequence safety (M.S) and the second safety is a parallel safety (S0|S1), the result of the binding is a menu safety ((S:=:S0/M)&(S:=:S1/M)).

### Claim 38 (depends on 33)

The method of claim 33, wherein if the first safety is a choice safety (S0+S1) and the second safety is of the form (S), the result of the binding is a choice safety ((S0:=:S)+(S1:=:S)).

### Claim 39 (depends on 33)

The method of claim 33, wherein if the first safety is a menu safety (S0&S1) and the second safety is of the form (S), the result of the binding is a menu safety ((S0:=:S)&(S1:=:S)).

### Claim 40 (depends on 33)

The method of claim 33, wherein if the first safety is a parallel safety (S0|S1) and the second safety is another parallel safety (S2|S3), the result of the binding is a menu safety ((S0,2,3,1)&(S1,2,3,0)&(S2,0,1,3)&(S3,0,1,2)).

### Claim 41 (depends on 40)

The method of claim 40, wherein each choice in the menu safety ((S0,2,3,1)&(S1,2,3,0)&(S2,0,1,3)&(S3,0,1,2)) can be placed in a form (Si,m,n,j), wherein if a relationship ((Si:=:(Sm|Sn)):=:Sj) is defined for a particular choice, the result of the binding is the relationship ((Si:=:(Sm|Sn)):=:Sj) or otherwise the result of the binding is another relationship ((Si:=:(Sm|Sn))|Sj).

### Claim 42 (depends on 33)

The method of claim 33, wherein if the first safety is a recursion safety (rec(K).S0) and the second safety is of the form (S), the result of the binding is a relationship (S0{rec(K).S0/K}:=:S).

### Claim 43 (depends on 33)

The method of claim 33, wherein if the first safety is of the form (S) and the second safety is of the form (0/S0), the result of the binding is undefined.

### Claim 44 (depends on 33)

The method of claim 33, wherein if the first safety is of the form (S) and the second safety is of the form (M0.S/M1) and a match function (match(M0, M1)) is defined, the result of the binding is equated to a cut function (cut(M0, M1)).

### Claim 45 (depends on 33)

The method of claim 33, wherein if the first safety is of the form (S) and the second safety is of the form (M0.S/M1) and a match function (match(M0, M1)) is not defined, the result of the binding is undefined.

### Claim 46 (depends on 33)

The method of claim 33, wherein if the first safety is of the form (S) and the second safety is of the form ((S0+S1)/M), the result of the binding is equated to a choice safety ((S0/M)+(S1/M)).

### Claim 47 (depends on 33)

The method of claim 33, wherein if the first safety is of the form (S) and the second safety is of the form ((S0&S1)/M), the result of the binding is equated to a menu safety ((S0/M)&(S1/M)).

### Claim 48 (depends on 33)

The method of claim 33, wherein if the first safety is of the form (S) and the second safety is of the form ((S0|S1)/M), the result of the binding is equated to a menu safety ((S0/M)&(S1/M)).

### Claim 49 (depends on 33)

The method of claim 33, wherein if the first safety is of the form (S) and the second safety is of the form (rec(K).S/M), the result of the binding is equated to a recursion safety (rec(K).(S/M)).

### Claim 50

A computer-readable medium having computer-executable instructions for performing a method for checking the compatibility of a first porttype of a first Web service and a second porttype of the second Web service, the method comprising:
extracting a first safety (S1) from the first porttype of the first Web service and a second safety (S2) from the second porttype of the second Web service; and
testing the compatibility of the first safety with the second safety by binding the first safety with the second safety (S1:=:S2) to determine whether the result of the binding is an input-guarded process.

### Claim 51 (depends on 50)

The computer-readable medium of claim 50, wherein the first Web service includes a first port of the first porttype and the second Web service includes a second port of the second porttype, the first port being fusable with the second port if the result of the binding is an input guarded process.

### Claim 52 (depends on 50)

The computer-readable medium of claim 50, wherein the first Web service includes a first port of the first porttype and the second Web service includes a second port of the second porttype, the first port being fusable with the second port if the result of the binding is not an input-guarded process and both the first Web service and the second Web service tolerate the fusing of the first port and the second port.

### Claim 53 (depends on 50)

The computer-readable medium of claim 50, wherein if the first safety is a stop safety (0) and the second safety is of the form (S), the result of the binding is the second safety.

### Claim 54 (depends on 50)

The computer-readable medium of claim 50, wherein if the first safety is a sequence safety (M.S) and the second safety is a parallel safety (S0|S1), the result of the binding is a menu safety ((S:=:S0/M)&(S:=:S1/M)).

### Claim 55 (depends on 50)

The computer-readable medium of claim 50, wherein if the first safety is a choice safety (S0+S1) and the second safety is of the form (S), the result of the binding is a choice safety ((S0:=:S)+(S1:=:S)).

### Claim 56 (depends on 50)

The computer-readable medium of claim 50, wherein if the first safety is a menu safety (S0&S1) and the second safety is of the form (S), the result of the binding is a menu safety ((S0:=:S)&(S1:=:S)).

### Claim 57 (depends on 50)

The computer-readable medium of claim 50, wherein if the first safety is a parallel safety (S0|S1) and the second safety is another parallel safety (S2|S3), the result of the binding is a menu safety ((S0,2,3,1)&(S1,2,3,0)&(S2,0,1,3)&(S3,0,1,2)).

### Claim 58 (depends on 57)

The computer-readable medium of claim 57, wherein each choice in the menu safety ((S0,2,3,1)&(S1,2,3,0)&(S2,0,1,3)&(S3,0,1,2)) can be placed in a form (Si,m,n,j), wherein if a relationship ((Si:=:(Sm|Sn)):=:Sj) is defined for a particular choice, the result of the binding is the relationship ((Si:=:(Sm|Sn)):=:Sj) or otherwise the result of the binding is another relationship ((Si:=:(Sm|Sn))|Sj).

### Claim 59 (depends on 50)

The computer-readable medium of claim 50, wherein if the first safety is a recursion safety (rec(K).S0) and the second safety is of the form (S), the result of the binding is a relationship (S0{rec(K).S0/K}:=:S).

### Claim 60 (depends on 50)

The computer-readable medium of claim 50, wherein if the first safety is of the form (S) and the second safety is of the form (0/S0), the result of the binding is undefined.

### Claim 61 (depends on 50)

The computer-readable medium of claim 50, wherein if the first safety is of the form (S) and the second safety is of the form (M0.S/M1) and a match function (match(M0, M1)) is defined, the result of the binding is equated to a cut function (cut(M0, M1)).

### Claim 62 (depends on 50)

The computer-readable medium of claim 50, wherein if the first safety is of the form (S) and the second safety is of the form (M0.S/M1) and a match function (match(M0, M1)) is not defined, the result of the binding is undefined.

### Claim 63 (depends on 50)

The computer-readable medium of claim 50, wherein if the first safety is of the form (S) and the second safety is of the form ((S0+S1)/M), the result of the binding is equated to a choice safety ((S0/M)+(S1/M)).

### Claim 64 (depends on 50)

The computer-readable medium of claim 50, wherein if the first safety is of the form (S) and the second safety is of the form ((S0&S1)/M), the result of the binding is equated to a menu safety ((S0/M)&(S1/M)).

### Claim 65 (depends on 50)

The computer-readable medium of claim 50, wherein if the first safety is of the form (S) and the second safety is of the form ((S0|S1)/M), the result of the binding is equated to a menu safety ((S0/M)&(S1/M)).

### Claim 66 (depends on 50)

The computer-readable medium of claim 50, wherein if the first safety is of the form (S) and the second safety is of the form (rec(K).S/M), the result of the binding is equated to a recursion safety (rec(K).(S/M)).
