Objective

To use to a metadata service, the sender needs to know the location of that service. The e-SENS Service Location ABB defines a standard location for metadata service providers.The located metadata service can be used to obtain service metadata to properly configure the transport connection to the endpoint for that entity (or service provider) and to send documents or data to an end entity (or its service provider).

The ABB can be specified as a profile of open standards message protocols. The related e-SENS Specification provides a specification based on the based on the BDX Location OASIS specification.

Location service lookup is the first step into the dynamic discovery mechanism. It provides address and access information on capability services (Please refer to ABB – Capability Lookup). If a message is going to travel in the e-SENS system from an endpoint to another, the capability information of the receiving end-point is first needed in order to decide whether that endpoint is eligible and able to receive that message. To obtain the capability information, location service lookup is the prerequisite. In other words, if the sender entity needs to get information on the capabilities of an endpoint, it first has to learn the location of the capability service.


Version1.1

Interoperability

Level

Generic Requirements

The requirements for the Service Location ABB were first identified in D6.1, based on input from CC6.1 experts, experience from previous LSPs, and initial input from WP5 domains.

For D6.2 and D6.3, the updated WP5 domain pilot plans have been reviewed and the following list of requirements is found to be still valid.

Requirement
ID

Requirement description

Source

R-SerLoc-B1

Obtain location information to route messages to end entities

R5.1-UC1-11,

R5.1-UC1-16,

R5.1-UC4-6,

R5.2-UC1-7,

R5.3-UC1-4,

R5.3-UC4-4,

R5.4-UC1-16,

R5.4-UC2-16

R-SerLoc-B2

Location Lookup Services must be decoupled from transport protocols and security models it is used in conjunction with

 

R-SerLoc-B3

Ability to switch end entity identification information at the right point in time

R5.1-UC1-11,

R5.1-UC1-16,

R5.3-UC1-4, R5.3-UC4-4,

R5.4-UC1-16,

R5.4-UC2-16

R-SerLoc-T1

Discover the location of a metadata service for an identified end entity

R5.1-UC1-11,

R5.1-UC1-17,

R5.1-UC4-6,

R5.2-UC1-7

R-SerLoc-T2

Retrieve service metadata for an identified end entity from a discovered service location in a machine-readable format

R5.1-UC1-17,

R5.1-UC4-6,

R5.2-UC1-7

R-SerLoc-T3

Ability to parametrize location for separate environments (production, test)

 

R-SerLoc-T4

Ability to partition location information across communities (with community-specific terms and conditions, governance models etc.)

R5.1-UC1-17,

R5.2-UC1-7, R5.3-UC1-4,

R5.3-UC4-4

R-SerLoc-T5

Ability to locate service metadata for an entity using search criteria other than identifier

R5.1-UC1-17,

R5.1-UC4-6,

R5.3-UC1-4,

R5.3-UC4-4

Provided Services

Provided ServicesPurposeOutcome
Address Resolution

There are two types of access to Address Resolution Service;

  1. Originator of the message stands in C1 or C4 and uses "Backend Integration" ABB to reach the Address Resolution Service of Service Location ABB. The service returns the address of the end-entity's capability service.
  2. Sender agent stands in C2 or C3 and use Address Resolution Service of Service Location ABB directly. The service returns the address of the recipient agent's capability service.

Respectively;

  1. The service returns the address of the end entity's capability service address.
  2. The service returns the address of the recipient agent's capability service address.

Application View

Figure 1. Service realization view for Location Service Lookup ABB.


Information View

Figure 2. Hierarchical information structure view for Location Service Lookup ABB.

 


ABB Capability Realization

ABB SpecificationChoice CriteriaSustainability Assessment
PR - BDXL 1.3.0Decision Log - Service Location and Capability LookupCompleted

Contributors

Name

Surname

Organisation

Country

Iva

Milutinovic

Ministry of Justice, North Rhine Westphalia

Germany

Muhammet

Yildiz

TUBITAK

Turkey

Melis Ozgur

Cetinkaya Demir

TUBITAK

Turkey

Pim

van der Eijk

Ministry of Justice, North Rhine Westphalia

Germany

History

Version

Date

Changes made

Modified By

0.1

30.04.2014

First draft derived from ENTSOG profile

Iva Milutinovic

0.2

13.05.2014

First draft for review in CC6.1

Carmen Rotuna,

Pim van der Eijk

0.3

22.07.2014

ArchiMate diagrams added

Iva Milutinovic

Muhammet Yildiz

Melis Ozgur Cetinkaya Demir

0.411.02.2015D6.2 comments processed.

Iva Milutinovic and Pim van der Eijk

0.413.03.2015ArchiMate diagrams updated WRT D6.2 Comments

Melis Ozgur Cetinkaya Demir

Muhammet Yildiz

0.625.03.2015Structured according to the eSENS BB Descriptions.Melis Ozgur Cetinkaya Demir
0.730.03.2015

Generated the contents of the sections "Provided Services",

"Related ABBs" and "ABB Capability Realization".

Melis Ozgur Cetinkaya Demir
1.008.04.2014

Updated Objectives to be technology neutral.

Bumped version number to 1.0

Added WP5 to source of requirements.

Removed status as per email KVP

Removed sustainability assessment, as that applies to the

ABB Specification.

Pim van der Eijk
1.122.04.2015

The Message Exchange requirements are matched to the domain specific requirements of

  • WP5.1
  • WP5.2
  • WP5.3
  • WP5.4

Editorial:

  • Fixed link to related ABBs and ABB Capabiltiy realization
  • Bumped version
Melis Ozgur Cetinkaya Demir
  • No labels