B2B Web Service Infrastructure/Architecture · Presentation of DNM NOP B2B Web Services SWIM Master Class - Initiation Day - 14 June 2012 7. Writen and Presented by Bertrand BOUSQUET-HOURAT.

B2B Web Service Infrastructure/Architecture

Writen and presented byBOUSQUET-HOURAT BERTRAND

[email protected]

Presentation of DNM NOP B2B Web ServicesSWIM Master Class - Initiation Day - 14 June 2012

2Writen and Presented by Bertrand BOUSQUET-HOURAT

Architecture Agenda

Architecture constraints

Service architecture

Publish / subscribe

NM releases / systems available

Conclusion / Q&A



Architecture NM Releases

• Release Cycle

RL 13

RL 14

RL 15

RL 16RL 17

RL 13.1

RL 14.1

RL 15.5

RL 16.5 RL

17.5



• 2 platforms• Pre-Operational platform (Pre-OPS) for test• Operational platform (OPS)

• 2 services versions• Deprecated release: RL 15• Current release: RL 16

Architecture Operational systems

Client Application

NM system

ATM partner system

NM B2B Web Service Pre-OPS system

OPS system

RL 15RL 16

RL 15RL 16

NMVP system



Architecture Operational systems

B2B Web Services CustomersDeprecated versus Current release usage

01020304050607080

Apr 20

11May

2011

Jun 2

011

Jul 2

011

Aug 20

11Sep

2011

Oct 20

11Nov

2011

Dec 20

11Ja

n 201

2Feb

2012

Mar 20

12Apr

2012

Fully migrated Partially migrated Not yet migrated



• 1 additional platform• Non-Operational platform for Validation exercise

• 1 service version (anticipated compare to OPS and pre-OPS)• Current release: NM 16.5 still under development• Exercise ongoing on same platform (SESAR

Validation exercise preparation).

Architecture SWIM Master Class dedicated system

Client Application

NM system

ATM partner system

NM B2B Web Service

NMVP system

RL 16.5

NMVP system



Architecture Web Services / RPC*

• Web services paradigm: based on query/reply communication• Service’s Consumer explicitly requests the service to the

provider• Asymmetric communication: always initiated by the consumer• The provider never sends spontaneously any information

• Pure client-server example, where:• The consumer is the client

• the one that initiates the communication• the active part

• The provider is the server,• the one that waits for requests and serves them• the passive part

This type of communication is adequate to ask the provider to execute a service

* RPC: Remote Procedure Call²



Architecture NM Solutions

• Simple and Powerful Solutions Based on Query/Reply• RPC paradigm is simpler than the publish/subscribe one

• consumer remains a client application• provider remains a server application• SLA is well understood.

• Also, the “subscribe” part vanished: the consumer requests what it needs when it needs it:

• access to the NM information is not subject to any preliminary registration

• only subject to what is exactly required at an exact moment in time.• Same way as when querying information in the past:

• consumer does not need to store the information on its side: NM stores that data already. => duplicate storage is not efficient and not recommended

In this paradigm, the consumer polls the NM to get the information that it needs, with two alternatives



• Registration handled by the consumer application • Consumer application has a

publish/subscribe layer• Publish/subscribe layer registers the

subscription information (callback, class of information requested)

• The publish/subscribe layer polls the NM to check if there is new information available

• When new data is available, the publish/subscribe layer invokes the callback of the upper layer

• For the upper layer it is as if the Publish/Subscribe is done with the NM

Upper Layer

Pub/Sub Layer

NMThis solution can be readily used. No new development by NM.

Architecture Publish / Subscribe



Software

Architecture Constraints

NM Services

CFSP

CFSP

Software• Certificate

• Not duplicated (1 / end customer / connection)

• CFSP alone, only PreOPS access• User ID and Password associated to

each certificate• Agreement:

• 1 to be signed per end user => Listing all certificates

• Charging• 2 free per end customer• Admin. fee for subsequent one

PreOPS only

AO

AO

AO

AOARO



Architecture Conclusions

• B2B Web Services Releases available:• SWIM Master Class (on NMVP) => Only NM 16.5• Operational systems => NM 15 and NM 16

• Web services paradigm• based on query/reply• Publish/subscribe only via your own intermediate layer

• Certificates (for Operational usage)• Not duplicated (1 / end customer / connection)• Only 1 connection per certificate at a time• CFSP alone, only PreOPS access



Questions?Questions?

Architecture

B2B Web Service Infrastructure/Architecture · Presentation of DNM NOP B2B Web Services SWIM Master Class - Initiation Day - 14 June 2012 7. Writen and Presented by Bertrand BOUSQUET-HOURAT.

Documents