name: V-PCF
full_form: Visited Policy Control Function
context: Figure 4.15.6.7.3-1 shows procedure for service specific parameter provisioning by the AF to VPLMN. Figure 4.15.6.7.3-1: Service specific information provisioning by AF to VPLMN 0a. Same as in step 0a of Figure 4.15.6.7.2-1. 0b-0c. The V-PCF may request to V-UDR on changes in UE policy information and H-PCF may subscribe to H-UDR. 1-2. Steps 1-2 of Figure 4.15.6.7.2-1 apply with the following differences: - The AF and NEF belong to the VPLMN. The AF may belong to third party with agreement with VPLMN. - When the AF provides application guidance on URSP Rule determination to the VPLMN, it will target "PLMN ID(s) of inbound roamers". The NEF in the VPLMN rejects any request for a GPSI or an External-Group-ID of a different PLMN. 3-5. Steps 3-5 of Figure 4.15.6.7.2-1 apply with the following differences: - AF, NEF and UDR belong to VPLMN. The AF may belong to third party with agreement with VPLMN. - The UDR in the VPLMN notifies the V-PCF(s) that have subscribed to the reception of application guidance on URSP determination. - In step 5, the V-PCF receives updates on application guidance on URSP determination for the PLMN ID of a SUPI that has a UE Policy Association established. The PLMN ID of the SUPI is included in the target "PLMN ID(s) of inbound roamers" in step 2. In this case, the V-PCF checks whether application guidance on URSP determination applies for the SUPI as specified in clause 6.1.2.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ]  [20]. 5a. The V-PCF sends the Service Parameters including the mapped HPLMN S-NSSAI values to the H-PCF and subscribes to the result of the delivery of UE Policies if the delivery result was requested by the AF, using the event reporting on "Notification on outcome of UE Policies delivery" described in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ]  [20]. NOTE: The AMF determines whether LBO is allowed and performs SMF selection to select the SMF in VPLMN for LBO case as described in clause 6.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ]  [2]. The H-PCF requests V-PCF to notify the result of UE policy delivery to the UE. 6. The H-PCF generates new or updated URSP Rules considering the Service Parameters received from the V-PCF in step 5a as specified in clause 6.1.2.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ]  [20]. 7-8. Steps 7-8 of Figure 4.15.6.7.2-1 apply with the following differences: - Notification is sent from V-PCF to the AF belonging to the VPLMN or third party with agreement with VPLMN.
description: The Visited Policy Control Function (V-PCF) is a network function within the visited public land mobile network (VPLMN) that plays a crucial role in managing policies for roaming users. It interacts with other network functions such as the Application Function (AF), Network Exposure Function (NEF), and Home Policy Control Function (H-PCF) to ensure proper policy control and charging for services provided to roaming subscribers.
explanation: V-PCF is classified as a Network Function because it serves as an intermediary between different network functions within the VPLMN, facilitating communication and data exchange necessary for effective policy management and service provisioning. Its role in managing policies for inbound roamers and interacting with other network components aligns with the 3GPP's specifications for efficient network operations.
section_title: 4.15.6.7.3 Service specific parameter provisioning by AF to VPLMN
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Device,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Miscellaneous,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Parameter,O,O,O,B-Parameter,I-Parameter,O,O,B-Parameter,O,O,O,B-Device,O,O,O,O,B-Parameter,I-Parameter,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,B-Network,O,B-Procedure,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,B-Network,O,O,O,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,B-Network Function,I-Network Function,I-Network Function,O,O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O