Content for TS 23.333 Word version: 17.1.0

1… 4 5… 5.8… 5.12… 5.14… 5.20… 5.24… 6… 6.1.8… 6.2… 6.2.3… 6.2.4… 6.2.5 6.2.6… 6.2.7… 6.2.8… 6.2.9… 6.2.10… 6.2.10.2.7 6.2.10.3… 6.2.11… 6.2.13… 6.2.13.2.6… 6.2.14… 6.2.15… 6.2.16… 6.2.18… 6.2.19… 6.2.19.3… 6.2.20… 6.2.21… 6.2.22… 6.2.23 6.2.24… 7 8… 8.11… 8.20 8.21 8.22 8.23… 8.30… 8.39… 8.45… 8.56…

6.1.8 Audit of MRFP 6.1.9 MRFP Capability Change 6.1.10 MRFC Out of service 6.1.11 MRFP Resource Congestion Handling - Activate 6.1.12 MRFP Resource Congestion Handling -Indication 6.1.13 Hanging termination detection
...

6.1.8 Audit of MRFP p. 68

6.1.8.1 Audit of Value p. 68

The MRFC may request the MRFP to report the current values assigned to distinct objects in the MRFP.

Copy of original 3GPP image for 3GPP TS 23.333, Fig. 6.1.8.1.1: Audit Value

Figure 6.1.8.1.1: Audit Value
(⇒ copy of original 3GPP image)

6.1.8.2 Audit of Capability p. 69

The MRFC may request the MRFP to report the capabilities of distinct objects in the MRFP.

Copy of original 3GPP image for 3GPP TS 23.333, Fig. 6.1.8.2.1: Audit Capability

Figure 6.1.8.2.1: Audit Capability
(⇒ copy of original 3GPP image)

6.1.9 MRFP Capability Change p. 69

The MRFP reports a change of capability of distinct objects in the MRFP.

Copy of original 3GPP image for 3GPP TS 23.333, Fig. 6.1.9.1: Capability Update

Figure 6.1.9.1: Capability Update
(⇒ copy of original 3GPP image)

The MRFC can use the Audit Value and/or Audit Capability procedures to obtain further information, about the objects whose capabilities have changed.

6.1.10 MRFC Out of service p. 69

Copy of original 3GPP image for 3GPP TS 23.333, Fig. 6.1.10.1: MRFC Out of Service

Figure 6.1.10.1: MRFC Out of Service
(⇒ copy of original 3GPP image)

If an MRFC discovers that it wants to go out of service it starts an MRFC Out of Service procedure. The MRFC can indicate whether it requires the context to be cleared immediately (forced) or cleared when all terminations are released.(Graceful)

6.1.11 MRFP Resource Congestion Handling - Activate p. 70

When the MRFC requires that an MRFP congestion notification mechanism be applied in the MRFP, the MRFC shall use the MRFP Resource Congestion Handling - Activate procedure towards the MRFP.

Copy of original 3GPP image for 3GPP TS 23.333, Fig. 6.1.11.1: MRFP Resource Congestion Handling - Activate

Figure 6.1.11.1: MRFP Resource Congestion Handling - Activate
(⇒ copy of original 3GPP image)

6.1.12 MRFP Resource Congestion Handling -Indication p. 70

When the MRFC receives a load reduction notification from the MRFP via the MRFP Resource Congestion Handling - Indication procedure, the MRFC tries to reduce the processing load that the MRFC creates on the MRFP. The MRFP shall decide the actual level of traffic reduction.

Copy of original 3GPP image for 3GPP TS 23.333, Fig. 6.1.12.1: MRFP Resource Congestion Handling-Indication

Figure 6.1.12.1: MRFP Resource Congestion Handling-Indication
(⇒ copy of original 3GPP image)

6.1.13 Hanging termination detection p. 70

Whenever requesting new IP bearer terminations, the MRFC shall request the MRFP to periodically report termination heartbeat indications to detect hanging context and termination in the MRFP that may result e.g. from a loss of communication between the MRFC and the MRFP.

When the MRFC receives a termination heartbeat notification from the MRFP via the Termination heartbeat - Indication procedure, the MRFC shall return a Termination heartbeat - Indication Ack (without an error) if the context id / termination identity combination exists in the MRFC. If it does not exist, the MRFC shall return an error and shall correct the mismatch, e.g. by requesting the MRFP to subtract the indicated termination and to clear any associated context.

Copy of original 3GPP image for 3GPP TS 23.333, Fig. 6.1.13.1: Termination heartbeat - Indication

Figure 6.1.13.1: Termination heartbeat - Indication
(⇒ copy of original 3GPP image)