# US 2013/0275571 A1 · Configuring an enforcement device according to a contract

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

- Number: US 2013/0275571 A1
- Document ID: US20130275571A1
- Status: Published application
- Kind: A1
- Application number: 13/448,741
- Filed: 2012-04-17
- Published: 2013-10-17
- Earliest claimed: 2012-04-17
- Assignees: Hewlett Packard Enterprise Development LP
- Inventors: Lukas Barton; Vladimir Dubsky; Pavel Zavora
- Web page: https://patentgrep.com/patent/US20130275571A1

## CPC

- H04N 21/2541: {Rights Management (protecting software against unauthorised usage in a vending or licensing environment G06F21/10; security in data switching network management H04L41/28; security management or policies for network security H04L63/20; access security in wireless networks H04W12/08)}
- H04L 41/5022: by giving priorities, e.g. assigning classes of service
- H04L 43/55: Testing of service level quality, e.g. simulating service usage
- H04N 21/278: Content descriptor database or directory service for end-user access {(details of content or meta data based information retrieval of video data in video databases G06F16/739)}
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A repository stores a contract between a service consumer and a service provider that provides a service, the contract specifying a service-level objective associated with a service to be applied for the service consumer. An enforcement device is configured according to the contract, where the configuring causes the enforcement device to perform enforcement of the service-level objective in a connection between the service consumer and the service provider, the connection allowing the service consumer to access the service in response to the enforcement device confirming that the service consumer is associated with the contract.

## Claims

### Claim 1

A method comprising:
storing, in a repository, a contract between a service consumer and a service provider that provides a service, the contract specifying a service-level objective associated with a service to be applied for the service consumer; and
configuring an enforcement device according to the contract, where the configuring causes the enforcement device to perform enforcement of the service-level objective in a connection between the service consumer and the service provider, the connection allowing the service consumer to access the service in response to the enforcement device confirming that the service consumer is associated with the contract.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving, by the enforcement device, a contract identifier from the service consumer;
determining, by the enforcement device, whether the contract identifier is valid,
wherein the enforcement device confirming that the service consumer is associated with the contract is in response to determining that the contract identifier is valid.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
rejecting, by the enforcement device, access of the service in response to the enforcement device determining that the contract identifier is invalid.

### Claim 4 (depends on 2)

The method of claim 2, wherein the contract identifier is received with a request from the service consumer for access of the service.

### Claim 5 (depends on 1)

The method of claim 1, wherein the service is a service of a service-oriented architecture.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
providing the contract to any lifecycle stage of a lifecycle of the service; and
enforcing, by the enforcement device, access of the service according to the service-level objective of the contract after conditions defined in a contract lifecycle have been met.

### Claim 7 (depends on 6)

The method of claim 6, wherein the service lifecycle comprises multiple stages.

### Claim 8 (depends on 7)

The method of claim 7, wherein a lifecycle of the contract comprises multiple stages including a testing stage, wherein the contract being in the testing stage of the contract lifecycle allows the service consumer to access an instance of the service that has been created or deployed during the development stage of the service lifecycle.

### Claim 9 (depends on 8)

The method of claim 8, further comprising determining that the service-level objective of the contract can be met during the testing stage of the contract lifecycle before the service consumer is given access to the instance of the service during a production stage of the service lifecycle.

### Claim 10

An article comprising at least one machine-readable storage medium storing instructions that upon execution cause a system to:
associate information with a service during a development stage of a lifecycle of a service, the information including a contract that specifies a service-level objective associated with a service to be provided by a service provider, and the contract being between a service consumer and the service provider;
store the information in a repository; and
configure an enforcement device according to the information, where the configuring causes the enforcement device to perform enforcement of the service-level objective in a connection between the service consumer and the service provider, the connection allowing the service consumer to access the service in response to the enforcement device confirming that the service consumer is associated with the contract

### Claim 11 (depends on 10)

The article of claim 10, wherein storing the information in the repository comprises further storing a runtime policy of the service in the repository.

### Claim 12 (depends on 10)

The article of claim 10, wherein the instructions upon execution cause the system to further monitor data during execution of the service, and store the monitored data in the repository.

### Claim 13 (depends on 10)

The article of claim 10, wherein the instructions upon execution cause the system to further allow, by the enforcement device, access of the service by the consumer during a second stage of the lifecycle of the service.

### Claim 14 (depends on 10)

The article of claim 10, wherein the instructions upon execution cause the system to further:
receive, by the enforcement device, a contract identifier from the service consumer;
determine, by the enforcement device, whether the contract identifier is valid,
wherein the enforcement device confirming that the service consumer is associated with the contract is in response to determining that the contract identifier is valid.

### Claim 15 (depends on 14)

The article of claim 14, wherein the instructions upon execution cause the system to further:
reject, by the enforcement device, access of the service in response to the enforcement device determining that the contract identifier is invalid.

### Claim 16 (depends on 10)

The article of claim 10, wherein the instructions upon execution cause the system to further perform lookup of the service using an identifier of the contract.

### Claim 17

A system comprising:
a repository to store a contract between a service consumer and a service provider that provides a service, the contract specifying a service-level objective associated with a service to be applied for the service consumer; and
at least one processor to:
configure an enforcement device according to the contract, where the configuring causes the enforcement device to perform enforcement of the service-level objective in a connection between the service consumer and the service provider, the connection allowing the service consumer to access the service in response to the enforcement device confirming that the service consumer is associated with the contract.

### Claim 18 (depends on 17)

The system of claim 17, wherein the repository is to further store a runtime policy associated with the service.

### Claim 19 (depends on 17)

The system of claim 17, further comprising the enforcement device, the enforcement device to:
receive a contract identifier from the service consumer;
determine whether the contract identifier is valid,
wherein the enforcement device confirming that the service consumer is associated with the contract is in response to determining that the contract identifier is valid.
