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

Version 1 Current »

The 5G UDR types are designed to exchange data between the workflows, and can be viewed in the UDR Internal Format Browser.

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.


  • No labels