F3.6.3 Provide Interface for Content Providers : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created:
24.10.2019 12:44:24
Modified:
08.09.2021 11:24:33
Project:
Author:
Update after transfer
Version:
5.0
Phase:
1.0
Status:
Proposed
Complexity:
Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:
{B623B347-AA95-44be-9043-55050E3CFC41}
Appears In:
SSTP Function Allocation, Content Provider View, 02 NAP Functional View, 02 NAP Functional View with data exchange, 03 NAP Organisational View, 04 NAP Physical View, Functional Tree of F3.6 Operate National Access Point, DFD F3.6 Operate National Access Point, 04 NAP Physical View with data exchange, 05 NAP Communication View with data exchange, 05 NAP Communication View
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to receive and process request to upload new or updated meta-data from a data provider.<br/>(2) The ability to forward the authorisation credentials of the data provider to the Function Manage Data Provider Registrations and to receive a result about the authorised registration of the data provider from the Function Manage Data Provider Registrations.<br/>(3) The ability to send the NAP meta-data included in the request in (1) above to the Function Manage NAP Meta-Data for loading into the data store if the checks in (2) and (3) above were successful.<br/>(4) The ability to send a "failure" response to the entity that made the request in (1) above if the checks in (2) and (3) above were unsuccessful or a “success” response if the checks were successful.<br/>
(a) continuously monitor for the receipt of the data flow from the Content Provider;<br/>(b) when the data flows arrives in (a), send the supplied authorisation credentials take in the data flow to the Data Store D3.17;<br/>(c) as a result of (b) continuously monitor for the receipt of the return data flow from the Data Store D3.17;<br/>(d) when the data flow in (c) is received, if its content indicates success, load the meta-data received in (a) in the data flow that enables it to be sent to Data Store D3.15;<br/>(e) continuously monitor for receipt of the resulting data flow from the Data Store D3.15;<br/>(f) in the data flow in (e) indicates success, the send a data flow indicating success to the Content Provider;<br/>(g) if either of the data flows in (c) or (e) indicate failure, send a data flow indicating at what stage the failure occurred to the Content Provider.<br/>
