8.2.77 PFCP Association Release Request
29.2443GPPInterface between the Control Plane and the User Plane nodesRelease 17TS
The PFCP Association Release Request IE shall be encoded as shown in Figure 8.2.77-1.
|
Bits |
||||||||||
|
Octets |
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
|
1 to 2 |
Type = 111 (decimal) |
|||||||||
|
3 to 4 |
Length = n |
|||||||||
|
5 |
Spare |
URSS |
SARR |
|||||||
|
6 to (n+4) |
These octet(s) is/are present only if explicitly specified |
|||||||||
Figure 8.2.77-1: PFCP Association Release Request
The following flags are coded within Octet 5:
– Bit 1 – SARR (PFCP Association Release Request): If this bit is set to "1", then the UP function requests the release of the PFCP association.
– Bit 2 – URSS (non-zero Usage Reports for the affected PFCP Sessions Sent): If this bit is set to "1", it indicates that the UP function has sent all the non-zero usage reports to the CP function for all PFCP essions affected by the PFCP Association Release.
– Bit 3 to 8: Spare, for future use and set to "0".