F3.6.2 Manage Content Provider Registrations : 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:
{B032435E-6A52-4920-97B0-C13BB3E8BFC7}
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 a request from an entity that wants to become new NAP data provider.<br/>(2) The ability to check the new NAP data provider in (1) above to include identification, verification that the requesting entity exists and is believed to be capable of providing road related static and/or dynamic data based on information included in the request.<br/>(3) The ability to load information about the entity submitting the request in (1) above into the NAP Data Providers data store, if the identification, verification and acceptance in (2) above is successful.<br/>(4) The ability to provide authorisation credentials to the requesting entity.<br/>(5) The ability to send a rejection notice (including the reason for rejection) to the entity that submitted the request in (1) above if the identification, verification and acceptance in (2) and (3) above was not successful.<br/>(6) The ability to check the authorisation of a data provider which sends its credentials to the Function Provide Interface for Data Providers and to response to this Function if the authorisation check has been successful.<br/>(7) The ability to process the information provided in an unsuccessful request for the automatic update of NAP data so that a suitable response can be sent to the entity that made the request and future unsuccessful update requests monitored.<br/>
(a) continuously monitor for the receipt of the first three logical input data flows;<br/>(b) if the first logical input data flow is received in (a), process the request and separate the data from the information about the data provider;<br/>(c) carry out any necessary checks to establish the existence, legitimacy and any other checks for the data provider to be able to submit data to either of the NAP data stores;<br/>(d) load the data found in (b) into the second output logical data flow and send it;<br/>(e) load the information about the data provider found in (b) into the first logical output data flow and send it;<br/>(f) if the second logical input data flow is received in (a), load the request into the second output logical data flow and send it;<br/>(g) if the third logical input data flow is received in (a), process the data it contains and check to see if this data provider has previously tried to load data into either of the NAP data stores and then carry out the checks in (c) above before updating internal records with the result;<br/>(h) when (f) is complete load the third logical output data flow with a "rejection" and if the checks in (g) were successful a "reminder to register" texts and send it to the destination obtained from the processing in (f).<br/>
