Desktop ProfileDesktop Profile

Web ProfileWeb Profile

Mobile ProfileMobile Profile

Communications ProfileCommunications Profile

Service FrameworkService Framework

AbstractionAbstraction

Ide

nti

ty M

an

ag

em

en

tId

en

tity

Ma

na

ge

me

nt

Po

lic

yP

oli

cy

Lif

e C

yc

le M

gm

tL

ife

Cy

cle

Mg

mt

Tel

eco

m M

anag

em

ent

SO

A P

rofi

le

Se

cu

rity

Se

cu

rity

ComponentService

Tier

ComponentService

Tier

Event DrivenArchitectureEvent DrivenArchitecture

Presentation andEncoding

Event Notification

Service Facades

SIP, CSTA…other SIP, CSTA…other R

IA

FA

T

Hyb

rid

System(I.e. B2B, cloud, social..)

System(I.e. B2B, cloud, social..)

65

4 2

31

Inter-o

perab

ility1. Transaction

Endpoints Specification

2. Notification

3. SOAP Protocol

4. SAML Token Correlation

5. User-ID Forwarding

6. Services exposing Management Interface

7. Metadata in support of Service Lifecycle Management

8. Universal Communications Profile,

7

8

Desktop ProfileDesktop Profile

Web ProfileWeb Profile

Mobile ProfileMobile Profile

Communications ProfileCommunications Profile

SOA FrameworkSOA Framework

AbstractionAbstraction

Ide

nti

ty M

an

ag

em

en

tId

en

tity

Ma

na

ge

me

nt

Po

lic

yP

oli

cy

Lif

e C

yc

le M

gm

tL

ife

Cy

cle

Mg

mt

Tel

eco

m M

anag

em

ent

SO

A P

rofi

le

Se

cu

rity

Se

cu

rity

ComponentService

Tier

ComponentService

Tier

Event DrivenArchitectureEvent DrivenArchitecture

Presentation andEncoding

Event Notification

Service Facades

SIP, CSTA…other SIP, CSTA…other

RIA

FA

T

Hyb

rid

System(I.e. B2B, cloud, social..)

System(I.e. B2B, cloud, social..)

Use Case and Definitions1. Transaction Endpoints Specification, related to a possible issue on the W3C WS-

Addressing specification; the necessity to specify the endpoint of a final result of a “process/transaction" (i.e. asynchronous response) result should be sent.

2. Notification, related to a possible issue on the OASIS WS-Notification specification, the necessity to specify for the Provider of a notifications service to specify the endpoint to which the Notification should be sent.

3. SOAP Protocol issue, related on a possible issue on the W3C SOAP specification; the necessity for an “intermediate SOAP node” to also cover the role of “SOAP ultimate receiver node”.

4. SAML Token Correlation, related to a possible issue on the OASIS WS-Security specification; the necessity of enabling “correlation” of a security token to another.

5. User-ID Forwarding, related to a possible issue in the OASIS WS-Security specification; the necessity to define a common means to add two (or more) credentials in one message.

6. Services exposing Management Interface, related to possible issues on the OASIS SOA Reference Model (SOA RM) and SOA Service Component Architecture (SCA) Assembly Model; the necessity to specify more than one service interface for a single SOA service.

7. Metadata in support of Service Lifecycle Management, related to the possibility to enrich the OASIS SOA Reference Architecture (SOA RA) with metadata necessary for Service Lifecycle Management identified within the TM Forum SDF program.

8. Universal Communications Profile, related to the specification of a possible common profile for universal interoperability across domains.