Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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:

FieldDescription
registerCycleUDRThis field is populated by the contents of RequestCycle UDR, and body of RequestCycle UDR should using NFProfile as a payload.
heartbeatCycleUDRThis field is populated by the contents of RequestCycle UDR, and body of RequestCycle UDR should using List of PatchItem as a payload.
deregisterCycleUDRThis field is populated by the contents of RequestCycle UDR.
nfInstanceIdFieldNameField mapping for nfInstanceId in NFProfile. This is an optional field. If the field is left unpopulated, the value in nfInstanceId will be used.
nfTypeFieldNameField mapping for nfType in NFProfile. This is an optional field. If the field is left unpopulated, the value in nfType will be used.
heartBeatFieldNameField mapping for heartbeatTimer in NFProfile. This is an optional field. If the field is left unpopulated, the value in heartbeatTimer will be used.
nfProfileChangesSupportIndFieldNameField mapping for nfProfileChangesSupportInd in NFProfile. This is an optional field. If the field is left unpopulated, the value in nfProfileChangesSupportInd will be used.
  • No labels