8.2.217 Vendor-Specific Node Report Type

29.2443GPPInterface between the Control Plane and the User Plane nodesRelease 17TS

The Vendor-Specific Node Report Type IE shall be encoded as shown in Figure 8.2.217-1. It indicates the type of the Vendor-Specific node report the UP function sends to the CP function.

		Bits
	Octets	8	7	6	5	4	3	2	1
	1 to 2	Type = 320 (decimal)
	3 to 4	Length = n
	5 to 6	Enterprise ID
	7	Spare	Spare	Spare	Spare	Spare	Spare	Spare	Spare
	8 to (n+4)	These octet(s) is/are present only if explicitly specified

Figure 8.2.217-1: Vendor-Specific Node Report Type

Octet 7 (and following octets if needed) shall be encoded as a bitmask, where each bit in the bitmask shall indicate a Vendor-Specific Node Report Type. The definition and semantic of the bits in the bitmask are out of scope of 3GPP.

Enterprise ID in octets 5 to 6 shall be encoded as defined in clause 8.1.1. The Enterprise ID may identify a Standards Development Organization. The report types indicated by octet 7 (and following octets if needed) are specific to the Standards Development Organization or enterprise identified by the Enterprise ID.

Spare bits are for future use and shall be set to "0".

At least one bit shall be set to "1".

NOTE: The Vendor-Specific Node Report Type IE in the PFCP Node Report Request message can be used by non-3GPP Standards Development Organizations for interfaces relying on PFCP as the protocol for Control and User Plane Separation, for identifying the type of vendor-specific node reports not defined by 3GPP. The definition and semantic of the bits within the bitmask are to be specified by each non-3GPP Standards Development Organization (without liaising with 3GPP CT4). See clauses 5.9 and 8.1.1 for the definition and usage of Vendor Specific IEs.