9.42.4.1 NRFSpecificationUDR

When an HTTP/2 Server agent has the custom specification for the 5G profile enabled, the agent expects to receive the NRFSpecificationUDR in order to perform the NF (Network Function) registration, heartbeat and de-registration.

The following fields are included in NRFSpecificationUDR:

Field	Description
`registerCycleUDR`	This field is populated by the contents of `RequestCycle` UDR, and body of `RequestCycle` UDR should using NFProfile as a payload.
`heartbeatCycleUDR`	This field is populated by the contents of `RequestCycle` UDR, and body of `RequestCycle` UDR should using List of PatchItem as a payload.
`deregisterCycleUDR`	This field is populated by the contents of `RequestCycle` UDR.
`nfInstanceIdFieldName`	Field mapping for nfInstanceId in NFProfile. This is an optional field. If the field is left unpopulated, the value in `nfInstanceId` will be used.
`nfTypeFieldName`	Field mapping for nfType in NFProfile. This is an optional field. If the field is left unpopulated, the value in `nfType` will be used.
`heartBeatFieldName`	Field mapping for heartbeatTimer in NFProfile. This is an optional field. If the field is left unpopulated, the value in `heartbeatTimer` will be used.
`nfProfileChangesSupportIndFieldName`	Field mapping for nfProfileChangesSupportInd in NFProfile. This is an optional field. If the field is left unpopulated, the value in `nfProfileChangesSupportInd` will be used.

Next:

9.43 HTTPD Agent