Existing Bearers Are Rejected Call Flow
This section describes the Existing Bearers Are Rejected call flow.

Step |
Description |
---|---|
1 |
The SMF sends a N7 Create request to the PCF. |
2 |
The PCF responds to the SMF with a N7 Create Success response. |
3 |
The AF sends N5 Create request (Audio and Video) message to the PCF. |
4 |
The PCF performs the N5 Authorization CRD lookup. |
5 |
The N5 Authorization CRD evaluates both, the audio and video bearers. If successful authorization, PCF sends N5 Create success response to AF. |
6 |
The PCF sends N7 Notify (Audio and Video) message. |
7 |
The SMF responds with N7-Notify-Resp (Success) to the PCF. |
8 |
The SMF sends N7 Update (RAT-Type Change). |
9 |
The PCF performs the N5 Authorization CRD lookup. |
10 |
When PCF reevaluates the existing bearer and the N5 Authorization CRD detects a VIDEO bearer with the Bearer-Authorization=REJECT, PCF rejects the bearer with Error-Message=Throttled. The PCF sends N7-UPDATE (Success) Charging Rule Remove for VIDEO to the SMF. |
11 |
The PCF sends N5 Notify request (Video) AF-Event=FAILED_RESOURCES_ALLOCATION to the AF |
12 |
The AF responds with N5 Notify success-response to the PCF. |