Data Stream Contents

correlation-id

This is a unique identifier in the message for correlation within a single transaction.

If an intermediate Oracle NF like SCP or SEPP sees a correlation-id custom header in the message, then it forwards the header without any modification.
Oracle NFs add the correlation-id custom header in the responses.

The actual correlation-id custom header name is confirmed during the implementation.

consumer-id

This is a 5G NF Instance ID of the NF originating the received message.

Depends on the presence of the User-Agent header in the received service request
Recommended User-Agent header format: User-Agent:<NF Type>-<NF Instance ID> <NF FQDN>

producer-id

This is a 5G NF Instance ID of the destination NF.

Oracle SCP can find the destination NF instance Id using the authority in the service request and learning from the NRF.
Other Oracle NFs may not be able to find NF instance id of destination in be able to put destination FQDN.

consumer-fqdn

This is a FQDN of the network function originating the received message.

Depends on the presence of User-Agent header in the received service request
Recommended User-Agent header format: User-Agent:<NF Type>-<NF Instance ID> <NF FQDN>

producer-fqdn

This is an FQDN of the destination NF.

Depends on the presence of FQDN in the authority of service request.

hop-by-hop-id

Oracle NFs can add Hop-by-Hop id to identify a request and response pair to the next node.

This is required in addition to correlation-id for uniquely identifying the request-response pair in case of re-routing.

re-route cause

Indicates the re-route cause. Contains one of the following:

Circuit breaking: Flag to indicate that a message is an alternate attempt due to circuit breaking functionality at the SCP.
Outlier detection: Flag to indicate that a message is an alternate attempt due to outlier detection functionality at the SCP.
Egress-rate-limit: Flag to indicate that a message is an alternate attempt due to egress rate limiting functionality at the SCP.
producer-nf-congestion: Flag to indicate that a message is an alternate attempt due to producer NF congestion.
Error received
Timeout
Not Available

timestamp

This is a timestamp (in nanoseconds) at the traffic feed trigger point when the message is received or forwarded by the SCP. It is an epoch time.

message-direction

This is a parameter to indicate whether a message is ingress to or egress from NF.

It can be indicated by putting the traffic feed trigger point name.

RxRequest
TxRequest
RxResponse
TxResponse

feed-source

Source of this traffic feed. This contains the identity of the node sending the traffic feed.

Feed-source:

FQDN = NF's FQDN
NF instance id = NF instance id
Pod instance id = pod instance id

Data Director makes reasonable attempts to deliver packets in the same sequence as received from each pod (SCP Worker pod, NRF, or SEPP API GW pod).

Due to the parallel nature of sending packets across multiple pods within CNE and IP routing, reception in order at the monitoring system cannot be guaranteed. Note that within a single transaction, request and answer follow the same path and processed by the same pod, therefore, there is no need to follow the packet order across multiple pods.