The 5G UDR types are designed to exchange data between the workflows, and can be viewed in the UDR Internal Format Browser.
Anchor | ||||
---|---|---|---|---|
|
When an HTTP/2 Server agent has the custom specification for the 5G profile enabled, the agent expects to receive the the NRFSpecificationUDR
in in order to perform the NF (Network Function) registration, heartbeat and de-registration.
The following fields are included in in NRFSpecificationUDR
:
Field | Description |
---|---|
| This field is populated by the contents |
of |
UDR, and body of |
UDR should using NFProfile as a payload. | |
| This field is populated by the contents |
of |
UDR, and body of |
UDR should using List of PatchItem as a payload. | |
| This field is populated by the contents |
of |
UDR. | |
| Field mapping for nfInstanceId in NFProfile. This is an optional field. If the field is left unpopulated, the value |
in |
will be used. | |
| Field mapping for nfType in NFProfile. This is an optional field. If the field is left unpopulated, the value |
in |
will be used. | |
| Field mapping for heartbeatTimer in NFProfile. This is an optional field. If the field is left unpopulated, the value |
in | |
| Field mapping for nfProfileChangesSupportInd in NFProfile. This is an optional field. If the field is left unpopulated, the value |
in |
Scroll pagebreak |
---|