Support for Prime PFD Message
The StarOS-based UPF node needs basic ECS rules configuration pushed from SMF. These default rules need to be provisioned in UPF dynamically even for dynamic PCC policy.
-
The StarOS UPF expects SMF to send the configuration in a new custom message. This message is called SX_PRIME_PFD_MANAGEMENT_REQUEST. The custom message ID of this message is 0x2F.
-
The response sent by UPF for this message is SX_PRIME_PFD_MANAGEMENT_RESPONSE with message ID 0x30.
The following snapshot shows the contents of this message:
[U-PLANE]PFCP Rx PDU, from 192.60.181.6:40259 to 192.60.181.2:8805 (81)
SEID: NA, Message type: SX_MSG_PRIME_PFD_MANAGEMENT_REQUEST (0x2F)
Sequence Number: 0x000001 (1)
PFCP HEADER
Version number: 1
SEID flag: Not present
Message Length: 0x004D (77)
INFORMATION ELEMENTS
CONFIG ACTION:
Type: 202 Length: 1
Value: ADD
Hex: 00CA 0001 01
CORRELATION ID:
Type: 203 Length: 2
Value: 4
Hex: 00CB 0002 0004
SUB PART NUMBER:
Type: 204 Length: 1
Value: 245
Hex: 00CC 0001 F5
CONTENT TLV:
Type: 206 Length: 53
Value:
Content Type: ACS_LEVEL_INFO
Content Length: 50
Hex: 00CE 0035 0B00 325C 00F1 015F 5F64 657F
6661 756C 745F 5F10 0113 2C01 0111 C801
132C 0101 132C 0101 532C 0101 0155 01FF
01FF 0101 1001 032C 01
Tuesday August 21 2018
<<<<OUTBOUND 09:43:39:380 Eventid:221302(3)
[U-PLANE]PFCP Tx PDU, from 192.60.181.2:8805 to 192.60.181.6:40259 (19)
SEID: NA, Message type: SX_MSG_PRIME_PFD_MANAGEMENT_RESPONSE (0x30)
Sequence Number: 0x000001 (1)
PFCP HEADER
Version number: 1
SEID flag: Not present
Message Length: 0x000F (15)
INFORMATION ELEMENTS
CAUSE:
Type: 19 Length: 1
Value:
Cause: PFCP_CAUSE_REQUEST_ACCEPTED (0x01)
Hex: 0013 0001 01
CORRELATION ID:
Type: 203 Length: 2
Value: 4
Hex: 00CB 0002 0004