Question: When Paging Policy Differentiation is enabled in a network, how does the SMF instruct the UPF to handle incoming DL PDUs with specific DSCP values in their IP headers for a UE in RRC Inactive state?
Option 1: By provisioning a single PDR with all possible DSCP codes mapped to a default PPI.
Option 2: By provisioning multiple PDRs, each containing one or more DSCP code(s) matched against the IP header's TOS (IPv4) / TC (IPv6) value, mapped to corresponding PPIs.
Option 3: By directly inserting the PPI into the DL PDU without analyzing the DSCP in the IP header.
Option 4: By ignoring the DSCP values and relying on ARP for Paging Policy Differentiation.
Explanation: This is correct because, when Paging Policy Differentiation is enabled, the SMF must provision multiple PDRs where each can contain one or more DSCP codes. These DSCP codes are matched against the TOS (IPv4) / TC (IPv6) value in the IP header of incoming DL PDUs, and each set of DSCP codes is mapped to a corresponding PPI. This process allows the UPF to insert the correct PPI into the GTP-U PDU Session Container extension header based on detected DSCP values, facilitating differentiated paging policies for UEs in RRC Inactive state.