Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 37.340  Word version:  18.1.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.3…   5…   7…   8…   9   10…   10.2…   10.2.2…   10.3…   10.3.2   10.4…   10.5…   10.5.2   10.6   10.7…   10.8…   10.9…   10.10…   10.11…   10.12…   10.12.2   10.13…   10.14…   10.15   10.16…   10.17…   10.18…   10.19…   10.20   11…   A   B…

 

10.13  Notification Control Indicationp. 98

10.13.1  EN-DCp. 98

Notification Control Indication procedure is not supported in EN-DC.

10.13.2  MR-DC with 5GCp. 98

The Notification Control Indication procedure may be initiated either by the MN or by the SN and is used to indicate that GFBR for one or several QoS flows cannot be fulfilled any more or can be fulfilled again by the reporting node.
Reproduction of 3GPP TS 37.340, Fig. 10.13.2-1: Notification Control Indication procedure
Up
Figure 10.13.2-1 shows an example signalling flow for the Notification Control Indication procedure.
Step 1.
The MN may, for an SN terminated bearer, indicate, that the GFBR requested from the MN cannot be fulfilled anymore.
In case the SN terminated bearer is configured as a split bearer, the SN may decide to increase the share provided by the SN or it may decide to notify the MN that resources requested for the SN terminated bearer cannot fulfill the GFBR any more.
Step 2.
Continuing the example message flow from step 1, the SN informs the MN that the GFBR for an SN terminated bearer cannot be fulfilled any more.
Step 3.
The MN decides to inform the 5GC that NG-RAN cannot fulfill the GFBR for a GBR QoS flow any more.
Up

Up   Top   ToC