# US 2012/0254899 A1 · Method and apparatus for providing application with interface to composite network service

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

- Number: US 2012/0254899 A1
- Document ID: US20120254899A1
- Status: Published application
- Kind: A1
- Application number: 13/077,630
- Filed: 2011-03-31
- Published: 2012-10-04
- Earliest claimed: 2011-03-31
- Assignees: Alcatel-Lucent USA Inc.
- Inventors: Alok Sharma; Yigang Cai
- Web page: https://patentgrep.com/patent/US20120254899A1

## CPC

- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method of providing an application with an interface to a composite network service includes: a) receiving a request for a composite network service at an exposure engine associated with an SCF, the composite network service associated with multiple network services, multiple service providers, multiple service networks, or multiple communication sessions; and b) selecting an API container based on the requested composite network service, the API container formed by a composition engine associated with the SCF and including composite service logic and composite enabler logic or composite normalization logic. The composite service logic including program calls. The composite enabler logic providing external protocol interfaces that do not require normalization. The composite normalization logic providing external protocol interfaces that require normalization. An apparatus for providing an application with an interface to a composite network service includes the exposure engine and API engine.

## Claims

### Claim 1

A method of providing an application with an interface to a composite network service, comprising:
a) receiving a request for a composite network service from a source network element at an exposure engine associated with a service composition framework (SCF), wherein the request is originated by a subscriber to the composite network service activating an application program for the composite network service via a user device in operative communication with the source network element, wherein the composite network service is associated with at least one of multiple network services, multiple service providers, multiple service networks, and multiple communication sessions; and
b) selecting an API container based at least in part on the composite network service associated with the request, the API container formed by a composition engine associated with the SCF and comprising composite service logic and at least one of composite enabler logic and composite normalization logic, the composite service logic comprising an arrangement of program calls based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service, the composite enabler logic selected from the exposure engine to provide protocol interfaces with any network service, service provider, service network, and communication session associated with the composite network service that does not require normalization, the composite normalization logic selected from a normalization engine associated with the SCF to provide protocol interfaces with any network service, service provider, service network, and communication session associated with the composite network service that requires normalization.

### Claim 2 (depends on 1)

The method set forth in claim 1, further comprising:
c) invoking an orchestration engine associated with the SCF to selectively process the composite service logic, composite enabler logic, and composite normalization logic in the API container to provide the composite network service in response to the request.

### Claim 3 (depends on 1)

The method set forth in claim 1 wherein the composite network service is associated with at least one service partner associated with some corresponding service provider.

### Claim 4 (depends on 1)

The method set forth in claim 1 wherein the API container selected in b) is an existing API container.

### Claim 5 (depends on 4)

The method set forth in claim 4, further comprising:
c) modifying the existing API container based at least in part on the request received in a); and
d) storing the modified API container in the SCF for subsequent reuse.

### Claim 6 (depends on 5)

The method set forth in claim 5, further comprising:
e) modifying the composite service logic in the existing API container by changing the arrangement of program calls, removing an existing program call, or adding a new program call based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service.

### Claim 7 (depends on 5)

The method set forth in claim 5, further comprising:
e) modifying the composite enabler logic in the existing API container by removing an existing enabler component or adding a new enabler component based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service.

### Claim 8 (depends on 5)

The method set forth in claim 5, further comprising:
e) modifying the composite normalization logic in the existing API container by removing an existing normalization component or adding a new normalization component based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service.

### Claim 9 (depends on 1)

The method set forth in claim 1, further comprising:
c) forming the API container selected in b) based at least in part on the request received in a), including forming the composite service logic, composite enabler logic, and composite normalization logic based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service; and
d) storing the API container in the SCF for subsequent reuse.

### Claim 10

An apparatus for providing an application with an interface to a composite network service, comprising:
an exposure engine associated with a service composition framework (SCF) for receiving a request for a composite network service from a source network element, wherein the request is originated by a subscriber to the composite network service activating an application program for the composite network service via a user device in operative communication with the source network element, wherein the composite network service is associated with at least one of multiple network services, multiple service providers, multiple service networks, and multiple communication sessions; and
an API container selected by the exposure engine based at least in part on the composite network service associated with the request, the API container formed by a composition engine associated with the SCF and comprising:
composite service logic comprising an arrangement of program calls based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service; and
at least one of composite enabler logic and composite normalization logic, the composite enabler logic selected from the exposure engine to provide protocol interfaces with any network service, service provider, service network, and communication session associated with the composite network service that does not require normalization, the composite normalization logic selected from a normalization engine associated with the SCF to provide protocol interfaces with any network service, service provider, service network, and communication session associated with the composite network service that requires normalization.

### Claim 11 (depends on 10)

The apparatus set forth in claim 10, further comprising:
an orchestration engine associated with the SCF and invoked by the exposure engine to selectively process the composite service logic, composite enabler logic, and composite normalization logic in the API container to provide the composite network service in response to the request.

### Claim 12 (depends on 10)

The apparatus set forth in claim 10, further comprising:
the composition engine for forming the API container selected by the exposure engine based at least in part on the request for the composite network service, including forming the composite service logic, composite enabler logic, and composite normalization logic based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service; and
a storage device for storing the API container in the SCF for subsequent reuse.
wherein the composition engine is also for modifying an existing API container based at least in part on another request for another composite network service, including at least one of modifying the composite service logic in the existing API container by changing the arrangement of program calls, removing an existing program call, or adding a new program call based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service, modifying the composite enabler logic in the existing API container by removing an existing enabler component or adding a new enabler component based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service, and modifying the composite normalization logic in the existing API container by removing an existing normalization component or adding a new normalization component based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service;
wherein the storage device is also for storing the modified API container in the SCF for subsequent reuse.

### Claim 13

A method of providing an application with an interface to a composite network service, comprising:
a) receiving a request for a composite network service from a source network element at an exposure engine associated with a service composition framework (SCF), wherein the request is originated by an application developer of a corresponding application program via a user device in operative communication with the source network element, wherein the composite network service is associated with at least one of multiple network services, multiple service providers, multiple service networks, and multiple communication sessions; and
b) selecting an API container based at least in part on the composite network service associated with the request, the API container formed by a composition engine associated with the SCF and comprising composite service logic and at least one of composite enabler logic and composite normalization logic, the composite service logic comprising an arrangement of program calls based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service, the composite enabler logic selected from the exposure engine to provide protocol interfaces with any network service, service provider, service network, and communication session associated with the composite network service that does not require normalization, the composite normalization logic selected from a normalization engine associated with the SCF to provide protocol interfaces with any network service, service provider, service network, and communication session associated with the composite network service that requires normalization.

### Claim 14 (depends on 13)

The method set forth in claim 13, further comprising:
c) invoking an orchestration engine associated with the SCF to selectively process the composite service logic, composite enabler logic, and composite normalization logic in the API container to test the ability of the SCF to provide the composite network service using the API container in response to the request.

### Claim 15 (depends on 13)

The method set forth in claim 13 wherein the composite network service is associated with at least one service partner associated with some corresponding service provider.

### Claim 16 (depends on 13)

The method set forth in claim 13 wherein the API container selected in b) is an existing API container.

### Claim 17 (depends on 16)

The method set forth in claim 16, further comprising:
c) modifying the existing API container based at least in part on the request received in a); and
d) storing the modified API container in the SCF for subsequent reuse.

### Claim 18 (depends on 17)

The method set forth in claim 17, further comprising:
e) modifying the composite service logic in the existing API container by changing the arrangement of program calls, removing an existing program call, or adding a new program call based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service.

### Claim 19 (depends on 17)

The method set forth in claim 17, further comprising:
e) modifying the composite enabler logic in the existing API container by removing an existing enabler component or adding a new enabler component based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service.

### Claim 20 (depends on 17)

The method set forth in claim 17, further comprising:
e) modifying the composite normalization logic in the existing API container by removing an existing normalization component or adding a new normalization component based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service.

### Claim 21 (depends on 13)

The method set forth in claim 13, further comprising:
c) forming the API container selected in b) based at least in part on the request received in a), including forming the composite service logic, composite enabler logic, and composite normalization logic based at least in part on the corresponding network services, service providers, service networks, and communication sessions associated with the composite network service; and
d) storing the API container in the SCF for subsequent reuse.
