8.2.69 Node Report Type
29.2443GPPInterface between the Control Plane and the User Plane nodesRelease 17TS
The Node Report Type IE shall be encoded as shown in Figure 8.2.69-1. It indicates the type of the node report the UP function sends to the CP function.
|
Bits |
||||||||||
|
Octets |
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
|
1 to 2 |
Type = 101 (decimal) |
|||||||||
|
3 to 4 |
Length = n |
|||||||||
|
5 |
Spare |
Spare |
VSR |
PURR |
GPQR |
CKDR |
UPRR |
UPFR |
||
|
6 to (n+4) |
These octet(s) is/are present only if explicitly specified |
|||||||||
Figure 8.2.69-1: Node Report Type
Octet 5 shall be encoded as follows:
– Bit 1 – UPFR (User Plane Path Failure Report): when set to "1", this indicates a User Plane Path Failure Report.
– Bit 2 – UPRR (User Plane Path Recovery Report): when set to "1", this indicates a User Plane Path Recovery Report.
Bit 3 – CKDR (Clock Drift Report): when set to "1", this indicates a Clock Drift Report.
– Bit 4 – GPQR (GTP-U Path QoS Report): when set to "1", this indicates a GTP-U Path QoS Report.
– Bit 5 – PURR (peer GTP-U entity Restart Report): when set to "1", this indicates a Peer GTP-U Restart report.
– Bit 6 – VSR (Vendor-Specific Report): when set to "1", this indicates a Vendor-Specific Report.
– Bit 7 to 8 – Spare, for future use and set to "0".
At least one bit shall be set to "1". Several bits may be set to "1".
NOTE 1: If UPFR, UPRR and/or PURR bits are set to "1", the Remote GTP-U Peer IEs in the User Plane Path Failure Report IE, in the User Plane Path Recovery Report IE and/or Peer UP Restart Report IE are different.
NOTE 2: A Vendor-Specific Report can be used in the PFCP Node Report Request message by non-3GPP Standards Development Organizations for interfaces relying on PFCP as the protocol for Control and User Plane Separation, for reports not defined by 3GPP. See clauses 5.9 and 8.1.1 for the definition and usage of Vendor Specific IEs.