...

PRH needs to send additional information coming in the PNF registration event that is BBS use case specific in the PNF_READY event (attachmentPoint, accessID, CVLAN, SVLAN).
It is initially agreed, that PRH will copy in 1:1 fashion the contents of VES.pnfRegistration.additionalFields into the PNF_READY event, along with the correlationID parameter sent there already in ONAP/Casbalanca release.
This allows other applications in the flow (BBS uS, SO,...) to react based on domain specific information sent in the pnfRegistration.additionalFields

Service-instance-related information

We need to provide further details for each piece of data we want to store under A&AI as part of a service instance, since SO handles service-related information.

See AAI-BBS Proposals for Dublin Release#BBSProposalsforDublinRelease-Item6.Specificdecisionsmadeforeachattribute 

Specifically

• Where this information comes from? Ext-API when ordering a service? CL event? What is the API used?
• Is the piece really needed to be in A&AI? (for example if only SDN-C uses it for resource controlling, then it could just come as input to its NBI and stored in MD-SAL)
• Which component is going to use it from A&AI?

...