EP4662884A1

EP4662884A1 - Outcome of policy delivery notification in roaming scenarios

Info

Publication number: EP4662884A1
Application number: EP24704922.4A
Authority: EP
Inventors: Antonio INIESTA GONZALEZ; Maria Belen PANCORBO MARCOS
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-02-10
Filing date: 2024-02-09
Publication date: 2025-12-17
Also published as: WO2024166062A1; CN120898439A

Abstract

A method in a V-PCF core node associated with a V-PLMN is described and includes obtaining a first indication indicating one or more service parameters. The one or more service parameters are associated with a registration and roaming from a H-PLMN to the V-PLMN and including a request to notify an AF core node about a policy delivery outcome concerning delivery of the one or more service parameters. A second indication indicating one or more of the service parameters of the first indication and notification information associated with a policy delivery outcome related to the one or more service parameters is transmitted. The method also includes receiving a third indication indicating the policy delivery outcome and transmitting a fourth indication to a NEF core node the fourth indication indicating the policy delivery outcome.

Description

OUTCOME OF POLICY DELIVERY NOTIFICATION IN ROAMING

SCENARIOS

TECHNICAL FIELD

The present disclosure relates to wireless communications, and in particular, to user equipment (UE) and/or wireless device (WD) policy delivery notification in roaming scenarios.

BACKGROUND

The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WDs)(e.g., UEs), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

In some existing systems, such as those which implement procedures as defined in 3GPP such as, for example, 3GPP Technical Standard (TS) 23.502 version 18.0.0 dated 2022-12-21 (hereinafter “3GPP TS 23.502”), clause 4.15.6.10, may allow an application function (AF) to provide guidance for user equipment (UE) route selection policy (URSP) determination to 5G system via network exposure functionality (NEF). In some existing systems, URSP may be used by a wireless device (e.g., UE) to determine how to route outgoing traffic. NEF may refer to external exposure of capabilities of network functions. The AF uses Nnef_ServiceParameter service to provide the service specific parameters to the PLMN and the wireless device (e.g., UE). The policy control function (PCF) and the NEF considered in this clause of 3GPP TS 23.502 are in the Home public land mobile network (PLMN). The Service Parameters provided by the AF may be stored by the NEF in the unified data repository (UDR). The home PCF (H-PCF) (i.e., a PCF in the HPLMN) is a function that may determine the URSP for the wireless device (e.g., UE) and takes the Service Parameters stored in the UDR by the NEF as input for the determination of URSP applicable for a wireless device.

FIG. 1 is a signaling diagram illustrating an example service specific information provisioning procedure in the H-PLMN as described in 3GPP such as, for example, 3GPP TS 23.502, clause 4.15.6.7, in which a wireless device (e.g., UE) communicates with one or more network nodes, such as a radio access network (RAN) node, an Access and Mobility management Function (AMF) node (i.e., a node which implements one or more AMF functionalities), a PCF node (i.e., a node which implements one or more PCF functionalities), a unified data management (UDM) node (i.e., a node which implements one or more UDM functionalities), a UDR node (i.e., a node which implements one or more UDR functionalities), an NEF node (i.e., a node which implements one or more NEF functionalities), and an AF core node (i.e., a node which implements one or more AF functionalities).

In addition to the provisioning of Service Parameters by invoking Nnef_ServiceParameter_Create (in step 2 in FIG. 1), the AF may subscribe to notifications about the outcome of the UE Policies delivery due to application guidance for URSP determination. If the AF subscribed to notifications about the outcome of UE Policies delivery due to Service specific parameter provisioning, the PCF notifies the outcome of the procedure of UE Policies delivery to the NEF by sending Npcf_EventExposure_Notify (step 7) and then the NEF notifies to AF by sending Nnef_ServiceParameter_Notify (step 8).

The Service Parameters stored in the UDR by the NEF contain the notification uniform resource identifier (URI) that has to be used by the PCF to notify the NEF about the outcome of the UE Policy delivery procedure. When the NEF receives Npcf_EventExposure_Notify, the NEF performs information mapping (e.g., AF Transaction Internal ID provided in Notification Correlation ID to AF Transaction ID, Subscription Permanent Identifier (SUPI) to Generic Public Subscription Identifier (GPSI), etc.) and triggers the appropriate Nnef_ServiceParameter_Notify message.

In addition, as described in 3GPP Technical Report (TR) 23.700-85 version 1.2.0 (2022-11) for the support of roaming scenarios in Key Issue #1 (KI#1), the information on the AF guidance for URSP determination provided by the AF to a PLMN (e.g. PLMN_A) may be associated instead to inbound roaming wireless devices (e.g., UEs) from other PLMN (e.g., PLMN_B). In this scenario, the AF is considered as the visited (V) AF (V- AF) and then provides the Service Parameters to the V-NEF and stores them in the V- UDR. The V-PCF obtains the Service Parameters from the V-UDR and provides them to the H-PCF (in PLMN_B) during the establishment of UE Policy Association establishment, which uses them as input for the generation of the URSP applicable to a wireless device while roaming in the V-PLMN (PLMN_A). This solution has been described in 3GPP SA2 CR S2-2301620 (2023-01), approved in SA2 154Ah. Existing systems, however, lack suitable configurations for notifications regarding the outcome of UE Policies delivery.

SUMMARY

For scenarios where the V-AF (i.e., the AF in the V-PEMN) provides Service Parameters through the V-NEF to the V-PCF and wants/requests to be notified about the outcome of the UE Policies delivery due to application guidance for URSP determination, it is undefined in existing systems how such notifications are provided to the V-AF. Thus, some embodiments of the present disclosure may provide one or more apparatuses, methods, and systems for providing such notifications.

In some embodiments of the present disclosure, when the V-AF provides Service Parameters to the V-PCF through the V-NEF and subscribes to notifications about the outcome of the UE policy delivery, the V-PCF requests to the H-PCF to be notified about the outcome of the UE policies delivery procedure. Therefore, the H-PCF, after invoking the corresponding policy delivery procedure, may notify the V-PCF about the outcome of the procedure, and then the V-PCF may notify the V-NEF by sending Npcf_EventExposure_Notify. UE policy and WD policy may be used interchangeably. Similarly, UE policy delivery and WD policy delivery may be used interchangeably.

Various embodiments are provided herein for the request and transfer of notifications from/to the V-PCF and H-PCF, for example:

1. In some embodiments, a new Policy Control Request Trigger (PCRT) is defined for the transfer of notifications about the outcome of UE Policy Delivery. When the V-PCF takes the Service Parameters from the V-UDR and they contain information about the subscriptions to notifications about the outcome of UE Policy Delivery, the V-PCF may include the new PCRT in the establishment of the UE Policy Association towards the H-PCF. Then, after invoking the corresponding UE Policy Delivery procedure, the H-PCF may provide the outcome of such procedure by invoking, e.g., Npcf_UEPolicyControl_updateNotify, as the information associated to the new PCRT.

2. In some embodiments, the V-PCF may provide the information related to the event subscription (e.g., subscribed events and notification URI) in addition to the Service Parameters to the H-PCF, but including its own address as notification URI (instead of the NEF one). Therefore, the H-PCF, same than in case a subscription to notification is requested as part of a Service Parameter request from the Home PLMN, after invoking the corresponding UE Policy Delivery procedure, may notify the outcome of the procedure by sending Npcf_eventExposure_notify to the V-PCF including the event “UE Policy delivery outcome”. The V-PCF then may forward such notification to the V- NEF (to the notification URI stored in the Service Parameters in the V-UDR).

Alternatively, in some embodiments, the V-PCF may provide the information related to the event subscription (subscribed events and notification URI) in addition to the Service Parameters to the H-PCF. Therefore, the H-PCF, same than in case a subscription to notification is requested as part of a Service Parameter request from the Home PLMN, after invoking the corresponding UE Policy Delivery procedure, may notify the outcome of the procedure by sending Npcf_eventExposure_notify to the V-NEF including the event “UE Policy delivery outcome”. Although this alternative embodiment may imply the definition of a new roaming interface between the H-PCF and V-NEF, it is also considered as a valid option.

Additionally, in some embodiments, the V-PCF may process the UE Policy Containers received from the AMF containing the delivery report from the wireless device (e.g., UE), e.g., "MANAGE UE POLICY COMPLETE" message or "MANAGE UE POLICY COMMAND REJECT" message, according to one or more legacy definitions, such as the examples defined in Annex D.5 of 3GPP TS 24.501 version 18.0.1 dated 2022- 09-26 (hereinafter “3GPP TS 24.501”), prior to being forwarded to the H-PCF, may determine from them the outcome of the procedure, and then may notify the V-NEF, e.g., by sending Npcf_eventExposure_notify.

Embodiments of the present disclosure may provide a mechanism for the H-PCF to notify the V-PCF about the outcome of the UE Policies delivery procedure associated with a request from a V-AF (i.e., the AF in a V-PLMN) to provide guidance for URSP determination in roaming scenario. This notification may be used by the V-PCF to notify the V-NEF when the V-AF subscribed to notifications about the outcome of the UE Policies delivery due to application guidance for URSP determination. Embodiments of the present disclosure provide one or more of the following features and/or advantages:

- A new PCRT may be defined in Npcf_UEPolicyControl service between the V- PCF and the H-PCF for the transfer of notifications about the outcome of UE Policy Delivery.

- The V-PCF may provide information related to the event subscription (e.g., subscribed events and notification URI) in addition to the Service Parameters to the H- PCF but including its own address as notification URI. Additionally, in some embodiments, the V-PCF may provide the information related to the event subscription (subscribed events and notification URI) in addition to the Service Parameters to the H-PCF.

Additionally, in some embodiments, the V-PCF may process the UE Policy Containers received from the AMF containing the delivery report from the wireless device (e.g., UE), e.g., prior to being forwarded to the H-PCF, and may determine from them the outcome of the procedure and then notify the V-NEF, e.g., by sending Npcf_eventExposure_notify.

Embodiments of the present disclosure may advantageously provide solutions for notifying the V-AF (i.e., the AF in a V-PLMN) about the outcome of the UE Policies delivery procedure associated with a request from the V-AF, e.g., to provide improved guidance for URSP determination in roaming scenarios, e.g., as compared to existing systems.

According to one aspect, a method in a visited policy control function (V-PCF) core node configured to communicate with and configure a wireless device (WD) is described. The V-PCF core node is associated a visited public land mobile network (V- PLMN). The method includes obtaining a first indication indicating one or more service parameters for the WD, where the one or more service parameters are associated with a registration and roaming of the WD from a home public land mobile network (H-PLMN) to the V-PLMN and including a request to notify an application function (AF) core node about a policy delivery outcome concerning delivery of the one or more service parameters. The method also includes transmitting to a home policy control function (H- PCF) core node a second indication indicating one or more of the service parameters of the first indication. The second indication further indicates notification information associated with the policy delivery outcome related to the one or more service parameters. The method also includes receiving, from the H-PCF core node responsive to the second indication, a third indication indicating the policy delivery outcome and transmitting, responsive to receiving the third indication, a fourth indication to a network exposure function (NEF) core node associated with the V-PLMN, the fourth indication indicating the policy delivery outcome.

In some embodiments, the notification information indicates one or more of: (A) one or both of a trigger and a request for notification of the policy delivery outcome; (B) one or more subscribed events; and (C) an address associated with one or both the V-PCF core node and the NEF core node for the notification of the policy delivery outcome. In some other embodiments, obtaining the first indication includes retrieving the first indication from a UDR core node or receive the first indication from the UDR core node.

In some embodiments, the method further includes one or both of determining and identifying the H-PCF core node associated with the H-PLMN.

In some other embodiments, the fourth indication is configured to cause the NEF core node to map the one or more service parameters to information associated with one or both of the WD and the V-PLMN.

In some embodiments, the fourth indication is further configured to cause the NEF core node to transmit policy delivery outcome information to the AF core node associated with the V-PLMN based on the notification information.

In some other embodiments, the one or more service parameters correspond to information indicating whether application guidance on a user equipment, UE, route selection policy (URSP) determination associated with the WD exists and applies to a subscription permanent identifier (SUPI).

In some embodiments, transmitting the second indication corresponds with the V- PCF core node subscribing to the policy delivery outcome.

In some other embodiments, the policy delivery outcome corresponds to a result of delivery of UE policies, and the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE Policies.

In some embodiments, the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE Policies is performed if requested by the AF core node to the H-PCF core node, using an event reporting.

According to another aspect, a visited policy control function (V-PCF) core node configured to communicate with and configure a wireless device (WD) is described. The V-PCF core node is associated with a visited public land mobile network (V-PLMN). The V-PCF is configured to obtain a first indication indicating one or more service parameters for the WD, where the one or more service parameters are associated with a registration and roaming of the WD from a home public land mobile network, H-PLMN, to the V- PLMN and includes a request to notify an application function (AF) core node about a policy delivery outcome concerning delivery of the one or more service parameters. The V-PCF is also configured to transmit to a home policy control function (H-PCF) core node a second indication indicating one or more of the service parameters of the first indication. The second indication further indicates notification information associated with the policy delivery outcome related to the one or more service parameters. The V-PCF is also configured to receive, from the H-PCF core node responsive to the second indication, a third indication indicating the policy delivery outcome and transmit, responsive to receiving the third indication, a fourth indication to a network exposure function (NEF) core node associated with the V-PLMN. The fourth indication indicates the policy delivery outcome.

In some embodiments, the notification information indicates one or more of: (A) one or both of a trigger and a request for notification of the policy delivery outcome; (B) one or more subscribed events; and (C) an address associated with one or both the V-PCF core node and the NEF core node for the notification of the policy delivery outcome.

In some other embodiments, obtaining the first indication includes retrieving the first indication from a UDR core node (15c) or receiving the first indication from the UDR core node (15c).

In some other embodiments, obtaining the first indication includes retrieving the first indication from a UDR core node or receiving the first indication from the UDR core node.

In some other embodiments, the one or more service parameters correspond to information indicating whether application guidance on a user equipment (UE) route selection policy (URSP) determination associated with the WD exists and applies to a subscription permanent identifier (SUPI).

In some embodiments, transmitting the second indication corresponds with the V- PCF core node (15d) subscribing to the policy delivery outcome.

In some embodiments, the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE Policies is performed if requested by the AF core node to the H-PCF core node, using an event reporting. According to one aspect, a method in a home policy control function (H-PCF) core node configured to communicate with configure a wireless device (WD) is described. The H-PCF core node is associated a home public land mobile network (H-PLMN). The method includes receiving a first indication indicating one or more service parameters for the WD associated with a registration and roaming of the WD from the H-PLMN to a visited public land mobile network (V-PLMN). The first indication is received from a visited policy control function (V-PCF) core node associated with the V-PLMN and further indicates notification information associated with a policy delivery outcome related to the one or more service parameters. The method also includes determining, responsive to the first indication, the policy delivery outcome associated with the WD and transmitting, to the V-PCF core node responsive to determining the policy delivery outcome, a second indication indicating the policy delivery outcome.

In some embodiments, the method further includes determining a notification destination based on the notification information, and the notification information indicates one or more of: (A) one or both of a trigger and a request for notification of the policy delivery outcome; (B) one or more subscribed events; and (C) an address associated with one or both the V-PCF core node and an NEF core node for the notification of the policy delivery outcome.

In some embodiments, the one or more service parameters are associated with the V-PCF core node subscribing to the policy delivery outcome.

In some embodiments, the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE Policies is performed if requested by an AF core node to the H-PCF core node, using an event reporting.

According to another aspect, a home policy control function (H-PCF) core node configured to communicate with configure a wireless device (WD) is described. The H- PCF core node is associated is a home public land mobile network (H-PLMN). The H- PCF core node is configured to receive a first indication indicating one or more service parameters for the WD associated with a registration and roaming of the WD from the H- PLMN (1 lb) to a visited public land mobile network (V-PLMN). The first indication is received from a visited policy control function (V-PCF) core node associated with the V- PLMN. The first indication further indicates notification information associated with a policy delivery outcome related to the one or more service parameters. The H-PCF core node is further configured to determine, responsive to the first indication, the policy delivery outcome associated with the WD and transmit, to the V-PCF core node responsive to determining the policy delivery outcome, a second indication indicating the policy delivery outcome.

In some embodiments, the H-PCF core node is further configured to determine a notification destination based on the notification information, and the notification information indicates one or more of: (A) one or both of a trigger and a request for notification of the policy delivery outcome; (B) one or more subscribed events; and (C) an address associated with one or both the V-PCF core node and an NEF core node for the notification of the policy delivery outcome.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein: FIG. 1 is a signaling diagram illustrating an example procedure for service specific information provisioning in the H-PLMN;

FIG. 2 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

FIG. 3 is a block diagram of a host computer communicating via a network node and core node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

FIG. 4 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node, a core node, and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

FIG. 5 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node, a core node, and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

FIG. 6 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node, a core node, and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

FIG. 7 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node, a core node, and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

FIG. 8 is a flowchart of an example process in a core node, according to some embodiments of the present disclosure;

FIG. 9 is a flowchart of another example process in another core node, according to some embodiments of the present disclosure;

FIG. 10 is a flowchart of another example process in a core node, according to some embodiments of the present disclosure;

FIG. 11 is a flowchart of another example process in another core node, according to some embodiments of the present disclosure;

FIG. 12 is a signaling diagram of an example process, according to some embodiments of the present disclosure; FIG. 13 is a signaling diagram of another example process, according to some embodiments of the present disclosure;

FIG. 14 is a signaling diagram of another example process, according to some embodiments of the present disclosure;

FIG. 15 is a signaling diagram of another example process, according to some embodiments of the present disclosure; and

FIG. 16 is a signaling diagram of another example process, according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to policy delivery notifications in roaming scenarios associated with a WD. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH). In some embodiments, the non-limiting term “core node” or “core network node” may be used. The core node herein can be any type of node (e.g., virtual and/or logical and/or physical and/or cloud-based computing devices) for performing one or more core network functionalities. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a Packet Data Network Gateway (P-GW), an access and mobility management function (AMF), a session management function (AMF), a user plane function (UPF), a Service Capability Exposure Function (SCEF), or the like. In some embodiments, one or more core nodes may be implemented by network nodes, and/or one or more network nodes may provide one or more core node functionalities. In some embodiments, network node and core node may be used interchangeably. In some embodiments, the one or more core nodes may be implemented in separate devices, while in some embodiments, one or more core nodes may be implemented in one or more same devices.

Note that although terminology from one particular wireless system, such as, for example, 3GPP ETE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

Note further, that functions described herein as being performed by a wireless device or a core node (and/or network node) may be distributed over a plurality of wireless devices and/or core nodes (and/or core nodes). In other words, it is contemplated that the functions of the core node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

Some embodiments provide systems, methods, and apparatuses for UE Policy delivery notifications in roaming scenarios. Referring now to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 2 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which includes a public land mobile network (PLMN) 11, which comprises an access network 12, such as a radio access network, and a core network 14 comprising and/or in communication with one or more core nodes 15. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 and/or core nodes 15 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16. Further, it is contemplated that communication system 10 may include multiple PLMNs 11 with respective access networks 12 and/or core networks 14, and/or a first communication system 10 may be in communication with a second communication system 10 including a respective second PLMN 11, second access network 12, second core network 14, etc.

Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and/or core node 15 and more than one type of network node 16 and/or core node 15. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

The communication system of FIG. 2 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

A core node 15 is configured to include a policy delivery unit 32 which is configured for supporting UE Policy delivery notifications in roaming scenarios.

Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 3. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22. The processing circuitry 42 of the host computer 24 may include a configuration unit 54 configured to enable the service provider to observe/monitor/ control/transmit to/receive from/etc. the network node 16, core node 15, and/or the wireless device 22.

The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16.

The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.

The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22.

The communication system 10 further includes a core node 15 provided in a communication system 10 and including hardware 94 enabling it to communicate with the host computer 24, network node 16, and with the WD 22. The hardware 94 may include a communication interface 96 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10. The communication interface 96 may be configured to facilitate connection 66 to the host computer 24. The connection 66 may be direct or it may pass through one or more intermediate networks 30 outside the communication system 10.

In the embodiment shown, the hardware 94 of the core node 15 further includes processing circuitry 98. The processing circuitry 98 may include a processor 100 and a memory 102. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 98 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 100 may be configured to access (e.g., write to and/or read from) the memory 102, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the core node 15 further has software 104 stored internally in, for example, memory 102, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the core node 15 via an external connection. The software 104 may be executable by the processing circuitry 98. The processing circuitry 98 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by core node 15. Processor 100 corresponds to one or more processors 100 for performing core node 15 functions described herein. The memory 102 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 104 may include instructions that, when executed by the processor 100 and/or processing circuitry 98, causes the processor 100 and/or processing circuitry 98 to perform the processes described herein with respect to core node 15. In some embodiments, the inner workings of the core node 15, network node 16, WD 22, and host computer 24 may be as shown in FIG. 3 and independently, the surrounding network topology may be that of FIG. 2.

In FIG. 3, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16 and/or core node 15, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the core node 15 or network node 16, and it may be unknown or imperceptible to the core node 15 or network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22.

In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16 and/or core node 15. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.

Although FIGS. 2 and 3 show various “units” such as policy delivery unit 32, as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

FIG. 4 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 2 and 3, in accordance with one embodiment. The communication system may include a host computer 24, a core node 15, a network node 16 and a WD 22, which may be those described with reference to FIG. 3. In a first step of the method, the host computer 24 provides user data (Block S100). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block S102). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block S104). In an optional third step, the network node 16 and/or core node 15 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block S106). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block S108).

FIG. 5 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a core node 15, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block S 112). The transmission may pass via the network node 16 and/or core node 15, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

FIG. 6 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a core node 15, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

FIG. 7 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a core node 15, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 and/or core node 15 receives user data from the WD 22 (Block S128). In an optional second step, the network node 16 and/or core node 15 initiates transmission of the received user data to the host computer 24 (Block SI 30). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 and/or core node 15 (Block SI 32).

FIG. 8 is a flowchart of an example process in a first core node 15, such as a PCF core node 15 of a visiting or visited PLMN (V-PCF core node 15), for supporting UE Policy delivery notifications in roaming scenarios. One or more blocks described herein may be performed by one or more elements of core node 15 such as by one or more of processing circuitry 98 (including the policy delivery unit 32), processor 100, and/or communication interface 96. The first PCF core node 15 is configured to receive (Block 134) a first indication indicating one or more service parameters for a wireless device 22 during and/or associated with a registration and/or roaming of the wireless device 22 from a second PLMN 1 lb (e.g., home PLMN) to the first PLMN I la. The first PCF core node 15 is configured to determine and/or identify (Block SI 36) a second PCF core node associated with the second PLMN The first PCF core node 15 is configured to transmit (Block S 136) to the second PCF 15 core node a second indication indicating one or more of the service parameters of the first indication, the second indication further indicating notification information associated with a policy delivery outcome. The first PCF core node 15 is configured to receive (Block SI 36), from the second PCF core node 15 responsive to the second indication, a third indication indicating the policy delivery outcome. The first PCF core node 15 is configured to transmit (Block S136), responsive to receiving the third indication, a fourth indication to a network exposure function (NEF) core node 15 associated with the first PLMN, the fourth indication indicating the policy delivery outcome and being configured to cause the NEF core node 15 to map one or more of the service parameters to information associated with the wireless device 22 and/or the first PLMN I la.

In some embodiments, the notification information indicates at least one of a trigger and/or request for notification of the policy delivery outcome, one or more subscribed events, and an address associated with the first PCF core node 15 and/or with an application function (AF) core node 15 associated with the first PLMN 11 for the notification of the policy delivery outcome. In some embodiments, the fourth indication is further configured to cause the NEF core node 15 to transmit policy delivery outcome information to an application function (AF) core node 15 associated with the first PLMN 11 based on the notification information.

In some embodiments, non-transitory computer readable medium having recorded thereon statements and instructions is provided (e.g., stored in memory 102), which, when executed by a processor of a first policy control function (PCF) core node (e.g., a core node 15 and/or network node 16 configured to implement one or more PCF functionalities), perform the above-described functionalities and/or steps and/or configurations.

FIG. 9 is a flowchart of an example process in a first core node 15, such as a PCF core node 15, e.g., a home PCF (H-PCF 15), for supporting UE Policy delivery notifications in roaming scenarios. One or more blocks described herein may be performed by one or more elements of core node 15 such as by one or more of processing circuitry 98 (including the policy delivery unit 32), processor 100, and/or communication interface 96. The first PCF core node 15 (e.g., H-PCF core node 15) is configured to receive (Block S144) a first indication indicating one or more service parameters for a wireless device 22 during and/or associated with a registration and/or roaming of the wireless device 22 from the first PLMN 11b (e.g., home PLMN) to a second PLMN I la (e.g., visiting PLMN), the first indication being received from a second PCF core node 15 associated with the second PLMN I la, the second indication further indicating notification information associated with a policy delivery outcome. The first PCF core node 15 is configured to determine (Block SI 46) , responsive to the first indication, the policy delivery outcome associated with the wireless device 22 and a notification destination based on the notification information. The first PCF core node 15 is configured to transmit (Block S148), to the second PCF core node 15 responsive to determining the policy delivery outcome and the notification destination, a second indication indicating the policy delivery outcome, the second indication being configured to cause the second PCF core node 15 to transmit a third indication to a network exposure function (NEF) core node 15 associated with the second PLMN I la, the third indication indicating the policy delivery outcome and being configured to cause the NEF core node 15 to map one or more of the service parameters to information associated with the wireless device 22 and/or the second PLMN Ila.

In some embodiments, the notification information indicates at least one of a trigger and/or request for notification of the policy delivery outcome, one or more subscribed events, and an address associated with the second PCF core node 15 and/or with an application function (AF) core node 15 associated with the second (e.g., visiting) PLMN 11 for the notification of the policy delivery outcome. In some embodiments, the third indication is further configured to cause the NEF core node 15 to transmit policy delivery outcome information to an application function (AF) core node 15 associated with the second (e.g., visiting or visited) PLMN 11 based on the notification information.

FIG. 10 is a flowchart of an example process in a core node 15, such as a visiting PCF (V-PCF) core node 15 of a visited PLMN (V-PLMN). One or more blocks described herein may be performed by one or more elements of core node 15 such as by one or more of processing circuitry 98 (including the policy delivery unit 32), processor 100, and/or communication interface 96. The V-PCF core node 15 is configured to obtain (Block SI 50) a first indication indicating one or more service parameters for the WD 22, where the one or more service parameters are associated with a registration and roaming of the WD 22 from a home public land mobile network (H-PLMN) 1 lb to the V-PLMN I la and including a request to notify an application function (AF) core node 15a about a policy delivery outcome concerning delivery of the one or more service parameters. The method also includes transmitting (Block SI 52) to a home policy control function (H-PCF) core node 15e a second indication indicating one or more of the service parameters of the first indication. The second indication further indicates notification information associated with the policy delivery outcome related to the one or more service parameters. The method also includes receiving (Block SI 54), from the H-PCF core node 15e responsive to the second indication, a third indication indicating the policy delivery outcome and transmitting (Block SI 56), responsive to receiving the third indication, a fourth indication to a network exposure function, (NEF) core node 15b associated with the V-PLMN Ila, the fourth indication indicating the policy delivery outcome.

In some embodiments, the notification information indicates one or more of: (A) one or both of a trigger and a request for notification of the policy delivery outcome; (B) one or more subscribed events; and (C) an address associated with one or both the V-PCF core node 15d and the NEF core node 15b for the notification of the policy delivery outcome.

In some other embodiments, obtaining the first indication includes retrieving the first indication from a UDR core node 15c or receive the first indication from the UDR core node 15c.

In some embodiments, the method further includes one or both of determining and identifying the H-PCF core node 15e associated with the H-PLMN 11b.

In some other embodiments, the fourth indication is configured to cause the NEF core node 15b to map the one or more service parameters to information associated with one or both of the WD 22 and the V-PLMN I la.

In some embodiments, the fourth indication is further configured to cause the NEF core node 15b to transmit policy delivery outcome information to the AF core node 15a associated with the V-PLMN I la based on the notification information.

In some other embodiments, the one or more service parameters correspond to information indicating whether application guidance on a user equipment, UE, route selection policy, URSP, determination associated with the WD exists and applies to a subscription permanent identifier (SUPI).

In some embodiments, transmitting the second indication corresponds with the V- PCF core node 15d subscribing to the policy delivery outcome.

In some other embodiments, the policy delivery outcome corresponds to a result of delivery of UE policies, and the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE Policies. In some embodiments, the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE Policies is performed if requested by the AF core node 15a to the H-PCF core node 15e, using an event reporting.

FIG. 11 is a flowchart of an example process in a core node 15, such as a home PCF (H-PCF) core node 15 of a home PEMN (H-PLMN). One or more blocks described herein may be performed by one or more elements of core node 15 such as by one or more of processing circuitry 98 (including the policy delivery unit 32), processor 100, and/or communication interface 96. The H-PCF core node 15 is configured to receive (Block SI 58) a first indication indicating one or more service parameters for the WD 22 associated with a registration and roaming of the WD 22 from the H-PLMN 11b to a visited public land mobile network (V-PLMN) I la. The first indication is received from a visited policy control function (V-PCF) core node 15d associated with the V-PLMN I la and further indicates notification information associated with a policy delivery outcome related to the one or more service parameters. The H-PCF core node 15 is also configured to determine (Block SI 60), responsive to the first indication, the policy delivery outcome associated with the WD 22 and transmit (Block S162), to the V-PCF core node 15d responsive to determining the policy delivery outcome, a second indication indicating the policy delivery outcome.

In some embodiments, the method further includes determining a notification destination based on the notification information, and the notification information indicates one or more of: (A) one or both of a trigger and a request for notification of the policy delivery outcome; (B) one or more subscribed events; and (C) an address associated with one or both the V-PCF core node 15d and an NEF core node 15b for the notification of the policy delivery outcome.

In some embodiments, the one or more service parameters are associated with the V-PCF core node 15d subscribing to the policy delivery outcome.

In some other embodiments, the policy delivery outcome corresponds to a result of delivery of UE policies, and the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE Policies. In some embodiments, the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE Policies is performed if requested by an AF core node 15a to the H-PCF core node 15e, using an event reporting.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for supporting policy delivery notifications in roaming scenarios associated with a WD 22.

One or more core node 15 functions described below may be performed by one or more of processing circuitry 98, processor 100, policy delivery unit 32, etc. One or more embodiments refer to the term “UE” which may refer to “WD.” In a nonlimiting example, UE policy may refer to WD policy, UE policy delivery may refer to WD policy delivery, UE policy association may refer to WD policy association, etc.

Some embodiments of the present disclosure may be applied to scenarios where the information on the AF guidance for URSP determination provided by the AF (e.g., V- AMF 15f and/or AMF 15f) to a PEMN I la (e.g., PLMN_A, V-PLMN) applies to the inbound roaming wireless devices 22 (e.g., UEs) from one or more other PLMN 1 lb (e.g., PLMN_B, H-PLMN). In some embodiments, the AF is considered as (and/or is implemented by) the V-AF 15a and then provides the Service Parameters to the V-NEF 15b (e.g., a core node 15 which provides V-NEF functionality) and store them in the V- UDR 15c (e.g., a core node 15 which provides V-UDR functionality). The V-PCF 15d obtains the Service Parameters from the V-UDR 15c and provides them to the H-PCF 15e (in PLMN_B) during the establishment of UE Policy Association establishment, which uses them as input for the generation of the URSP applicable to a wireless device 22 while roaming in the V-PLMN I la (PLMN_A).

One or more examples describe a V-AF 15a in PLMN I la (PLMN_A or V- PLMN) provides the service parameters for inbound roamers of PLMN 11b (PLMN_B or H-PLMN) and there are ongoing UE Policy associations already established for inbound roamers of PLMN 11b (PLMN_B).

Note that the procedures described herein may be similar for the case where the service parameters are already provisioned in the V-UDR 15c in PLMN Ila (PLMN_A) prior to the establishment of the UE policy association for an inbound roamer. One possible difference is that in this case, the V-PCF 15d provides the Service Parameters to the H-PCF 15e during the establishment of the UE Policy Association, i.e., during Npcf_UEPolicyControl_Create (instead of invoking Npcf_UEPolicyControl_Update as are depicted in some of the examples below).

Example Embodiment 1 : A new PCRT is defined in Npcf UEPolicyControl

FIG. 12 is a signaling diagram which illustrates an example procedure based in the definition of a new PCRT (“Notification on Outcome of UE Policy Delivery”) in Npcf_UEPolicyControl service between the V-PCF 15d and the H-PCF 15e for the transfer of notifications about the outcome of UE Policy Delivery. In the example of FIG. 12, a WD 22 is in communication with one or more core nodes 15a-15g (which may be implemented in the same hardware device(s) or in one or more separate physical and/or virtual device(s)). In the example, core nodes 15a-15f, corresponding to V-AMF 15f, V- NEF 15b, V-UDR 15c, and V-PCF 15d, are associated with PLMN I la (PLMN_A, V- PLMN), and core nodes 15e and 15g are associated with PLMN 11b (PLMN_B, H- PLMN).

Step S200: During the registration of a wireless device 22 from PLMN 11b (PLMN_B) in PLMN I la (PLMN_A), a UE Policy association is established between the AMF 15f (and/or V-AMF 15f), V-PCF 15d and H-PCF 15e as described in 3GPP such as in, for example, 3GPP TS 23.502 section 4.1.6.11

Step S202: At some point in time the AF (e.g., as implemented in one or more core nodes 15, such as V-AF 15a) decides to create a new request to provide Service Parameters to any inbound roamer of PLMN 1 lb (PLMN_B) including subscription information to the report of the outcome of UE Policy Delivery.

Step S204: The AF (e.g., V-AF 15a) sends the request to the NEF (e.g., V-NEF 15b) by invoking Nnef_ServiceParameter_Create, including the Service Parameters, the PLMNId for the inbound roamers (PLMN_B), the subscribed event and the notificationDestination URI to receive the notifications.

Step S206: The V-NEF 15b stores the information applicable to the inbound roamers in the V-UDR 15c.

Step S208: The V-NEF 15b answers the V-AF 15a, e.g., providing Nnef_ServiceParameter_Create information.

Step S2105: The V-UDR 15c notifies the V-PCF 15d about the new Service Parameters.

Step S212: The V-PCF 15d provides the Service Parameters to the H-PCF 15e and activates the new PCRT (Notification on Outcome of UE Policy Delivery) by invoking Npcf_UEPolicyControl_Update. Step S214: The H-PCF 15e answers the V-PCF 15d.

Step S216: The H-PCF 15e determines the applicable URSP for the wireless device 22 (e.g., UE) taking as input the provided Service Parameters (other inputs may be also used).

Step S218: The H-PCF 15e initiates the delivery of new/updated URSP to the wireless device 22 (e.g., UE), which may be according to a legacy procedure such as specified in 3GPP TS 23.502 clause 4.16.12.2 steps 3-9 (e.g., which may be performed at least in part by one or more AMF 15f, which may be a legacy AMF 15f)

Step S220: When the H-PCF 15e determines the outcome of the UE Policy delivery procedure, the H-PCF 15e may provide this outcome, or an indication thereof, to the V-PCF 15d by invoking Npcf_UEPolicyControl_UpdateNotify as information associated to the new PCRT (Notification on Outcome of UE Policy Delivery).

Step S222: The V-PCF 15d answers the H-PCF 15e.

Step S224: When the V-PCF 15d receives the update including the outcome of the UE Policy Delivery, the V-PCF 15d provides this outcome to the V-NEF 15b by invoking Npcf_eventExposure using the notificationDestination URI provided by the V-NEF 15b in Step S204.

Step S226: When the NEF (e.g., V-NEF 15b) receives Npcf_EventExposure_Notify, the NEF (e.g., V-NEF 15b) may perform information mapping (e.g., AF Transaction Internal ID provided in Notification Correlation ID to AF Transaction ID, SUPI to GPSI, etc.) and may trigger the appropriate Nnef_ServiceParameter_Notify message(s).

Example Embodiment 2: Implicit subscription to H-PCF 15e Npcf eventExposure from V-PCF 15d

FIG. 13 is a signaling diagram illustrating another example embodiment of the present disclosure based in the V-PCF 15d providing the information related to the event subscription (subscribed events and notification URI) in addition to the Service Parameters to the H-PCF 15e but including its own address as notification URI. The WD 22 is in communication with one or more core nodes 15a- 15g.

Step S300a through Step S310: these steps may be similar to the corresponding steps described above with respect to FIG. 12.

Step S312: The V-PCF 15d may provide the Service Parameters to the H-PCF 15e, and in addition: the information of the subscribed event; and/or a notificationDestination URI pointing to the V-PCF 15d for the reception of the legacy Npcf_EventExposure from H-PCF 15e for the event “UE Policy delivery outcome”.

Step S314: The H-PCF 15e answers the V-PCF 15d. The H-PCF 15e will use the new information in the same way than when a subscription to notification of UE policy delivery outcome is requested as part of a Service Parameter request from an AF in the H- PEMN (PLMN 1 lb), i.e., the H-PCF 15e after determination of the result of the UE Policy delivery will send Npcf_EventExposure to the URI provided as notificationDestination.

Steps S316 and S318: These steps may be similar to the corresponding steps described with respect to FIG. 12.

Step S320: When the H-PCF 15e determines the outcome of the UE Policy delivery procedure, the H-PCF 15e may notify this outcome by invoking Npcf_EventExposure to the URI provided as notificationDestination in step 6, i.e., to the V-PCF 15d.

Step S322: When the V-PCF 15d receives the Npcf_EventExposure including the event “UE Policy delivery outcome”, the V-PCF 15d may forward this notification to the V-NEF 15b to the notificationDestination URI provided by the V-NEF 15b in step 2.

Step S324: When the NEF (e.g., V-NEF 15b) receives Npcf_EventExposure_Notify, the NEF (e.g., V-NEF 15b) performs information mapping (e.g., AF Transaction Internal ID provided in Notification Correlation ID to AF Transaction ID, SUPI to GPSI, etc.) and triggers the appropriate Nnef_ServiceParameter_Notify message.

Example Embodiment 3: Implicit subscription to H-PCF 15e Npcf eventExposure FIG. 14 is a signaling diagram which illustrates another example procedure according to some embodiments of the present disclosure based in the V-PCF 15d providing the information related to the event subscription (subscribed events and notification URI) in addition to the Service Parameters to the H-PCF 15e for the H-PCF 15e notify directly the V-NEF 15b through a new roaming interface. As with FIG. 12 and FIG. 13, the wireless device 22 may be in communication with one or more core nodes 15a-15g, each associated with one of a first PLMN I la and a second PLMN 1 lb.

Step S400a-S410: these steps may be similar to the corresponding steps described above with respect to FIG. 12.

Step S412: The V-PCF 15d provides the Service Parameters to the H-PCF 15e, and in addition: the information of the subscribed event; and/or the notificationDestination URI received from V-NEF 15b in step S404, for the reception of the legacy Npcf_EventExposure from H-PCF 15e for the event “UE Policy delivery outcome”.

Step S414: The H-PCF 15e answers the V-PCF 15d. The H-PCF 15e may use the new information in the same way as when a subscription to notification of UE policy delivery outcome is requested as part of a Service Parameter request from an AF (e.g., V- AF 15a) in the H-PLMN (PLMN 11b), i.e., the H-PCF 15e after determination of the result of the UE Policy delivery may send Npcf_EventExposure to the URI provided as notificationDestination.

Steps S416 and S418: These steps may be similar to the corresponding steps described above with respect to FIG. 10.

Step S420: When the H-PCF 15e determines the outcome of the UE Policy delivery procedure the H-PCF 15e notify this outcome by invoking Npcf_EventExposure to the URI provided as notificationDestination in step 6, i.e., to the V-NEF 15b.

Step S422: When the NEF (e.g., V-NEF 15b) receives Npcf_EventExposure_Notify, the NEF (e.g., V-NEF 15b) performs information mapping (e.g., AF Transaction Internal ID provided in Notification Correlation ID to AF Transaction ID, SUPI to GPSI, etc.) and triggers the appropriate Nnef_ServiceParameter_Notify message.

Example Embodiment 4: V-PCF 15d processes UE Policy delivery

FIG. 15 is a signaling diagram illustrating another example procedure according to some embodiments of the present disclosure based in the V-PCF 15d processing the UE Policy Containers received from the AMF 15f (and/or V-AMF 15f) containing the delivery report from the UE prior to be forwarded to the H-PCF 15e, determine from them the outcome of the procedure and then notify the V-NEF 15b by sending Npcf_eventExposure_notify. One or more of the following may be performed:

Step S500a-S510: these steps may be similar to the corresponding steps described above with respect to FIG. 12.

Step S512: The V-PCF 15d may provide the Service Parameters to the H-PCF 15e.

Step S514: The H-PCF 15e may answer the V-PCF 15d.

Steps S516 and S518: These steps may be similar to the corresponding steps described above with respect to FIG. 12, e.g., which may be performed by one or more AMF 15f. Step S520: During the UE Policy delivery in step 9 the V-PCF 15d processes the UE Policy Containers received from the AMF 15f and/or V-AMF 15f containing the delivery report from the wireless device 22, e.g., "MANAGE UE POLICY COMPLETE" message and/or "MANAGE UE POLICY COMMAND REJECT" message, and determines from them the outcome of the UE Policy procedure.

Step S522: The V-PCF 15d notify the V-NEF 15b ( to the notificationDestination URI provided by the V-NEF 15b in step 2) about the outcome of the UE Policy Delivery by invoking Npcf_EventExposure_Notify.

Step S524: When the NEF (e.g., V-NEF 15b) receives Npcf_EventExposure_Notify, the NEF 15b performs information mapping (e.g., AF Transaction Internal ID provided in Notification Correlation ID to AF Transaction ID, SUPI to GPSI, etc.) and triggers the appropriate Nnef_ServiceParameter_Notify message.

FIG. 16 shows a signaling diagram illustrating another example procedure according to some embodiments of the present disclosure. One or more of the following may be performed:

Step S600a: The AMF 15f establishes UE Policy Association.

Steps S600b-600c: The V-PCF 15d may request to V-UDR 15c on changes in UE policy information and H-PCF 15e may subscribe to H-UDR 15g.

Steps S602 and S604: An AF request is created. The AF 15a and NEF 15b belong to the VPLMN I la. The AF 15a may belong to third party with agreement with VPLMN I la. When the AF 15a provides application guidance on URSP Rule determination to the VPLMN 1 la, it will target "PLMN ID(s) of inbound roamers". The NEF 15b in the VPLMN I la rejects any request for a GPSI or an External-Group-ID of a different PLMN 11. AF 15a, NEF 15b and UDR 15c belong to VPLMN I la. The AF 15a may belong to third party with agreement with VPLMN I la. The UDR 15c in the VPLMN I la notifies the V-PCF(s) 15d that have subscribed to the reception of application guidance on URSP determination.

Step S610: The V-PCF 15d 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 may be included in the target "PLMN ID(s) of inbound roamers" in step S604. In this case, the V-PCF 15d checks whether application guidance on URSP determination applies for the SUPI.

Step S610a: The V-PCF 15d sends the Service Parameters including the mapped HPLMN S-NSSAI values to the H-PCF 15e and subscribes to the result of the delivery of UE Policies if the delivery result was requested by the AF 15a, using the event reporting on "Notification on outcome of UE Policies delivery". The AMF 15f may determine whether LBO is allowed and performs SMF selection to select the SMF in VPLMN I la for LBO case. The H-PCF 15e requests V-PCF 15d to notify the result of UE policy delivery to the WD 22.

Step S612: The H-PCF 15e generates new or updated URSP Rules considering the Service Parameters received from the V-PCF 15d in step S610a.

Steps S614 and S616: Notification is sent from V-PCF 15d to the AF 15a belonging to the VPLMN or third party with agreement with VPLMN.

In some embodiments, when the UE Policy Association (e.g., WD policy association) is established or the V-PCF receives updates on application guidance on URSP determination for a SUPI that has a UE Policy Association established, the V-PCF 15d checks whether application guidance on URSP determination exists and applies for the SUPI. Then the V-PCF 15d: maps the S-NSSAI of the VPLMN into the S-NSSAI of the HPLMN 1 lb, using the Configured NSSAI for the Serving PLMN 11 provided by the AMF 15f and stored in PCF; and/or subscribes to the result of the delivery of UE Policies if it was requested by the AF15a to the H-PCF 15e, using the event reporting on “Notification on outcome of UE Policies delivery”.

The following is a nonlimiting list of example embodiments.

Embodiment AL A first policy control function (PCF) core node 15d (e.g., a core node 15 and/or network node 16 configured to implement one or more PCF functionalities) configured to communicate with and/or configure a wireless device 22, the first PCF core node 15d being associated a first public land mobile network (PLMN) I la (e.g., visiting PLMN Ila), the first PCF core node 15d configured to, and/or comprising a communication interface 96 and/or comprising processing circuitry 98 configured to: receive a first indication indicating one or more service parameters for a wireless device 22 during and/or associated with a registration and/or roaming of the wireless device 22 from a second PLMN 11b (e.g., home PLMN 11b) to the first PLMN 11; determine and/or identify a second PCF core node 15e associated with the second

PLMN 11b; transmit to the second PCF core node 15e a second indication indicating one or more of the service parameters of the first indication, the second indication further indicating notification information associated with a policy delivery outcome; receive, from the second PCF core node 15e responsive to the second indication, a third indication indicating the policy delivery outcome; and transmit, responsive to receiving the third indication, a fourth indication to a network exposure function (NEF) core node 15b associated with the first PLMN I la, the fourth indication indicating the policy delivery outcome and being configured to cause the NEF core node 15b to map one or more of the service parameters to information associated with the wireless device 22 and/or the first PLMN I la.

Embodiment A2. The first PCF core node 15d of Embodiment Al, wherein the notification information indicates at least one of: a trigger and/or request for notification of the policy delivery outcome; one or more subscribed events; and an address associated with the first PCF core node 15d and/or with an application function (AF) core node 15a associated with the first PLMN 1 la for the notification of the policy delivery outcome.

Embodiment A3. The first PCF core node 15d of any one of Embodiments Al and A2, wherein the fourth indication is further configured to cause the NEF core node 15b to transmit policy delivery outcome information to an application function (AF) core node 15a associated with the first PLMN I la based on the notification information.

Embodiment BL A method implemented in a first policy control function (PCF) core node 15d (e.g., a core node 15 and/or network node 16 configured to implement one or more PCF functionalities) configured to communicate with and/or configure a wireless device 22, the first PCF core node 15d being associated a first public land mobile network (PLMN) 1 la (e.g., visiting PLMN 1 la), the method comprising: receiving a first indication indicating one or more service parameters for a wireless device 22 during and/or associated with a registration and/or roaming of the wireless device from a second PLMN 1 lb (e.g., home PLMN 1 lb) to the first PLMN I la; determining and/or identify a second PCF core node 15e associated with the second PLMN 11b; transmitting to the second PCF core node 15e a second indication indicating one or more of the service parameters of the first indication, the second indication further indicating notification information associated with a policy delivery outcome; receiving, from the second PCF core 15e node responsive to the second indication, a third indication indicating the policy delivery outcome; and transmitting, responsive to receiving the third indication, a fourth indication to a network exposure function (NEF) core node 15b associated with the first PLMN I la, the fourth indication indicating the policy delivery outcome and being configured to cause the NEF core node 15b to map one or more of the service parameters to information associated with the wireless device and/or the first PLMN I la.

Embodiment B2. The method of Embodiment B 1 , wherein the notification information indicates at least one of: a trigger and/or request for notification of the policy delivery outcome; one or more subscribed events; and an address associated with the first PCF core node and/or with an application function (AF) core node 15a associated with the first PLMN 1 la for the notification of the policy delivery outcome.

Embodiment B3. The method of any one of Embodiments B 1 and B2, wherein the fourth indication is further configured to cause the NEF core node 15b to transmit policy delivery outcome information to an application function (AF) core node 15a associated with the first PLMN I la based on the notification information.

Embodiment B4. A non-transitory computer readable medium having recorded thereon statements and instructions that, when executed by a processor 100 of a first policy control function (PCF) core node 15d (e.g., a core node and/or network node configured to implement one or more PCF functionalities), configure the processor 100 to implement the method of any one of Embodiments Bl to B3.

Embodiment CL A first policy control function (PCF) core node 15e (e.g., a core node 15 and/or network node 16 configured to implement one or more PCF functionalities) configured to communicate with and/or configure a wireless device 22, the first PCF core node 15e being associated a first public land mobile network 11b (PLMN) (e.g., home PLMN 11b), the first PCF core node 15e configured to, and/or comprising a communication interface 96 and/or comprising processing circuitry 98 configured to: receive a first indication indicating one or more service parameters for a wireless device 22 during and/or associated with a registration and/or roaming of the wireless device 22 from the first PLMN 11b (e.g., home PLMN 11b) to a second PLMN I la (e.g., visiting PLMN Ila), the first indication being received from a second PCF core node 15d associated with the second PLMN I la, the second indication further indicating notification information associated with a policy delivery outcome; determine, responsive to the first indication, the policy delivery outcome associated with the wireless device and a notification destination based on the notification information; transmit, to the second PCF core node 15d responsive to determining the policy delivery outcome and the notification destination, a second indication indicating the policy delivery outcome, the second indication being configured to cause the second PCF core node 15d to transmit a third indication to a network exposure function (NEF) core node 15b associated with the second PLMN Ila, the third indication indicating the policy delivery outcome and being configured to cause the NEF core node 15b to map one or more of the service parameters to information associated with the wireless device 22 and/or the second PLMN I la.

Embodiment C2. The first PCF core node 15e of Embodiment Cl, wherein the notification information indicates at least one of: a trigger and/or request for notification of the policy delivery outcome; one or more subscribed events; and an address associated with the second PCF core node 15d and/or with an application function (AF) core node 15a associated with the second PLMN Ila for the notification of the policy delivery outcome.

Embodiment C3. The first PCF core node 15e of any one of Embodiments Cl and C2, wherein the third indication is further configured to cause the NEF core node 15b to transmit policy delivery outcome information to an application function (AF) core node 15a associated with the second PLMN based on the notification information.

Embodiment DI. A method implemented in a first policy control function (PCF) core node 15e (e.g., a core node 15 and/or network node 16 configured to implement one or more PCF functionalities) configured to communicate with and/or configure a wireless device 22, the first PCF core node 15e being associated a first public land mobile network (PLMN) 1 lb (e.g., home PLMN 1 lb), the method comprising: receiving a first indication indicating one or more service parameters for a wireless device 22 during and/or associated with a registration and/or roaming of the wireless device 22 from the first PLMN 11b (e.g., home PLMN 11b) to a second PLMN Ila (e.g., visiting PLMN Ila), the first indication being received from a second PCF core node 15d associated with the second PLMN I la, the second indication further indicating notification information associated with a policy delivery outcome; determining, responsive to receiving the first indication, the policy delivery outcome associated with the wireless device and a notification destination based on the notification information; transmitting, to the second PCF core node 15d responsive to determining the policy delivery outcome and the notification destination, a second indication indicating the policy delivery outcome, the second indication being configured to cause the second PCF core node 15d to transmit a third indication to a network exposure function (NEF) core node 15b associated with the second PLMN I la, the third indication indicating the policy delivery outcome and being configured to cause the NEF core node 15b to map one or more of the service parameters to information associated with the wireless device and/or the second PLMN I la.

Embodiment D2. The method of Embodiment DI, wherein the notification information indicates at least one of: a trigger and/or request for notification of the policy delivery outcome; one or more subscribed events; and an address associated with the second PCF core node 15d and/or with an application function (AF) core node 15a associated with the second PLMN Ila for the notification of the policy delivery outcome.

Embodiment D3. The method of any one of Embodiments DI and D2, wherein the third indication is further configured to cause the NEF core node 15b to transmit policy delivery outcome information to an application function (AF) core node 15a associated with the second PLMN I la based on the notification information.

Embodiment D4. A non-transitory computer readable medium having recorded thereon statements and instructions that, when executed by a processor of a first policy control function (PCF) core node 15e (e.g., a core nodel5 and/or network node 16 configured to implement one or more PCF functionalities), configure the processor 100 to implement the method of any one of Embodiments DI to D3.

Embodiment EL A method in a visited policy control function, V-PCF, core node 15d configured to communicate with and configure a wireless device, WD, 22 the V- PCF core node 15d being associated a visited public land mobile network, V-PLMN, I la, the method comprising: obtaining a first indication: indicating one or more service parameters for the WD 22, the one or more service parameters being associated with a registration and roaming of the WD 22 from a home public land mobile network, H-PLMN, 1 lb to the V-PLMN I la; and including a request to notify an application function, AF, core node (15a) about a policy delivery outcome concerning delivery of the one or more service parameters; and transmitting to a home policy control function, H-PCF, core node 15e a second indication indicating one or more of the service parameters of the first indication, the second indication further indicating notification information associated with a policy delivery outcome related to the one or more service parameters.

Embodiment E2. The method of Embodiment El , wherein the method further includes receiving, from the H-PCF core node 15e responsive to the second indication, a third indication indicating the policy delivery outcome.

Embodiment E3. The method of Embodiment E2, wherein the method further includes transmitting, responsive to receiving the third indication, a fourth indication to a network exposure function, NEF, core node 15b associated with the V-PLMN I la, the fourth indication indicating the policy delivery outcome.

Embodiment Fl. A visited policy control function, V-PCF, core node 15d configured to communicate with and configure a wireless device, WD, 22 the V-PCF core node 15d being associated a visited public land mobile network, V-PLMN, Ila, the V- PCF core node 15d being configured to: obtain a first indication: indicating one or more service parameters for the WD 22, the one or more service parameters being associated with a registration and roaming of the WD 22 from a home public land mobile network, H-PLMN, 1 lb to the V-PLMN I la; and including a request to notify an application function, AF, core node (15a) about a policy delivery outcome concerning delivery of the one or more service parameters; and transmit to a home policy control function, H-PCF, core node 15e a second indication indicating one or more of the service parameters of the first indication, the second indication further indicating notification information associated with a policy delivery outcome related to the one or more service parameters. Embodiment F2. The V-PCF core node 15d of Embodiment Fl, wherein the V-PCF core node 15d is configured to receive, from the H-PCF core node 15e responsive to the second indication, a third indication indicating the policy delivery outcome.

Embodiment F3. The V-PCF core node 15d of Embodiment F2, wherein the V-PCF core node 15d is configured to transmit, responsive to receiving the third indication, a fourth indication to a network exposure function, NEF, core node 15b associated with the V-PEMN I la, the fourth indication indicating the policy delivery outcome.

Embodiment Gl. A method in a home policy control function, H-PCF, core node 15e configured to communicate with configure a wireless device, WD, 22, the H- PCF core node 15e being associated a home public land mobile network, H-PLMN, 1 lb, the method comprising: receiving a first indication indicating one or more service parameters for the WD 22 associated with a registration and roaming of the WD 22 from the H-PLMN 1 lb to a visited public land mobile network, V-PLMN, I la, the first indication being received from a visited policy control function, V-PCF, core node 15d associated with the V-PLMN I la, the first indication further indicating notification information associated with a policy delivery outcome related to the one or more service parameters.

Embodiment G2. The method of Embodiment Gl , wherein the method further includes one or both of: determining, responsive to the first indication, the policy delivery outcome associated with the WD 22 and a notification destination based on the notification information; and transmitting, to the V-PCF core node 15d responsive to determining the policy delivery outcome and the notification destination, a second indication indicating the policy delivery outcome.

Embodiment HL A home policy control function, H-PCF, core node 15e configured to communicate with configure a wireless device, WD, 22, the H-PCF core node 15e being associated a home public land mobile network, H-PLMN, 1 lb, the H-PCF core node 15e being configured to: receive a first indication indicating one or more service parameters for the WD 22 associated with a registration and roaming of the WD 22 from the H-PLMN 11b to a visited public land mobile network, V-PLMN, I la, the first indication being received from a visited policy control function, V-PCF, core node 15d associated with the V-PLMN I la, the first indication further indicating notification information associated with a policy delivery outcome related to the one or more service parameters.

Embodiment H2. The H-PCF core node 15e of Embodiment Hl, wherein the H-PCF core node 15e is further configured to one or both of: determine, responsive to the first indication, the policy delivery outcome associated with the WD 22 and a notification destination based on the notification information; and transmit, to the V-PCF core node 15d responsive to determining the policy delivery outcome and the notification destination, a second indication indicating the policy delivery outcome.

In some embodiments, VPLMN specific URSP Rules may be defined. A VPLMN specific URSP Rule is applicable when the UE is registered in the VPLMN or its equivalent VPLMN only. VPLMN specific URSP rules are provided from the HPLMN and includes, based on agreements with VPLMN, HPLMN values for Network Slice Selection Policies and DNN Selection Policies. When provided, the Time and Location criteria in each of the RSD may include VPLMN values. It is provided to the UE to route traffic on a PDU Session to a SMF and UPF in the VPLMN. VPLMN configuration is used to ensure that the local VPLMN values are used when a PDU Session is established for a roaming UE. When the UE sends a PDU Session Establishment the HPLMN values that are included in the S -NS SAI and DNN need to be translated to VPLMN values to be able to select a SMF at the VPLMN. This means that the AMF select a local DNN that is used to select a SMF in the VPLMN. How the AMF selects a local DNN is to be decided during normative phase. The AMF also sends the local DNN, if decided, as “Selected DNN” to the SMF, while the DNN requested by the UE is sent as “Requested DNN”. The VPLMN provides the service parameters to HPLMN for HPLMN to generate the VPLMN specific URSP rules. The H-PCF creates VPLMN specific URSP rules corresponding to different VPLMN. The H-PCF may provide the VPLMN specific URSP rules to the UE. This can be triggered by the UE's registration in the VPLMN or it can happen before UE roams into the VPLMN. The URSP Rules received by UE in VPLMN are only applicable when the UE is registered in that VPLMN or its equivalent VPLMNs. If the UE does not find a match using the URSP rules associated with the VPLMN ID or equivalent VPLMN ID, it uses the URSP rules associated with the HPLMN. NOTE: The PCF may provide VPLMN specific URSP rules based on existing PCRT report from PCF such as PLMN Change or other triggers. Further, with respect to VPLMN specific URSP Rules, a new clause may define how the H-PCF provide VPLMN specific URSP Rules to the UE. How the AF provides Application guidance on URSP and rules to route the traffic to the VPLMN may be provided, either to the VPLMN or to the HPLMN. In addition, how to configure the VPLMN to select a local SMF may be described, e.g., using the existing DNN replacement function.

Definitions

The following may be defined:

• Application detection filter: A logic used to detect packets generated by an application based on extended inspection of these packets, e.g. header and/or payload information, as well as dynamics of packet flows. The logic is entirely internal to a UPF, and is out of scope of this specification.

• Application identifier: An identifier referring to a specific application detection filter.

• Application service provider: A business entity responsible for the application that is being / will be used by a UE, which may be either an AF operator or has an association with the AF operator.

• Authorised QoS: The maximum QoS that is authorised for a service data flow. In the case of an aggregation of multiple service data flows within one QoS Flow, the combination of the "Authorised QoS" information of the individual service data flows is the "Authorised QoS" for the QoS Flow. It may include the 5QI and the data rate.

• Binding: The association between a service data flow and the QoS Flow transporting that service data flow.

• Binding mechanism: The method for creating, modifying and deleting bindings.

• Charging control: The process of associating packets, belonging to a service data flow, to a charging key and applying online charging and/or offline charging, as appropriate.

• Charging key: Information used by the CHF for rating purposes.

• Detected application traffic: An aggregate set of packet flows that are generated by a given application and detected by an application detection filter.

• Dynamic PCC Rule: a PCC rule, for which the definition is provided to the SMF by the PCF. • Gating control: The process of blocking or allowing packets, belonging to a service data flow / detected application's traffic, to pass through to the UPF.

• Monitoring key: information used by the SMF and PCF for usage monitoring control purposes as a reference to a given set of service data flows or application (s), that all share

• a common allowed usage on a per UE and DNN basis.

• Non-3GPP access network selection information: It consists of ePDG identifier configuration, N3IWF identification and non-3GPP access node selection information, as defined in clause 6.3.6.1 in 3GPP TS 23.501.

• Non-Seamless Offload: A capability of the UE to access the data networks via non-3GPP access (e.g. WLAN radio access) outside of a PDU Session.

• Operator-controlled service: A service for which complete PCC rule information, including service data flow filter information, is available in the PCF through configuration and/or dynamic interaction with an AF.

• Operating System (OS): Collection of UE software that provides common services for applications.

• Operating System Identifier (OSId): An identifier identifying the operating system.

• OS specific Application Identifier (OSAppId): An identifier associated with a given application and uniquely identifying the application within the UE for a given operating system.

• Packet flow: A specific user data flow from and/or to the UE.

• Packet Flow Description (PFD): A set of information enabling the detection of application traffic provided by a 3rd party service provider.

• PCC decision: A PCF decision for policy and charging control provided to the SMF (consisting of PCC rules and PDU Session related attributes), a PCF decision for access and mobility related control provided to the AMF, a PCF decision for UE policy information provided to the UE or a PCF decision for background data transfer policy provided to the AF.

• PCC rule: A set of information enabling the detection of a service data flow and providing parameters for policy control and/or charging control and/or other control or support information. The possible information is described in clause 6.3.1. • Policy control: The process whereby the PCF indicates to the SMF how to control the QoS Flow. Policy control includes QoS control and/or gating control.

• Policy Control Request trigger report: a notification, possibly containing additional information, of an event which occurs that corresponds with a Policy Control Request trigger.

• Policy Control Request trigger: defines a condition when the SMF may interact again with the PCF.

• Policy counter: A mechanism within the CHF to track spending applicable to a subscriber.

• Policy counter identifier: A reference to a policy counter in the CHF for a subscriber.

• Policy counter status: A label whose values are not standardized and that is associated with a policy counter's value relative to the spending limit(s) (the number of possible policy counter status values for a policy counter is one greater than the number of thresholds associated with that policy counter, i.e. policy counter status values describe the status around the thresholds). This is used to convey information relating to subscriber spending from CHF to PCF. Specific labels are configured jointly in CHF and PCF.

• Policy Section: A Policy Section is identified by a Policy Section Identifier and consists of one or multiple URSP rule(s) or one or multiple WLANSP rule(s) or non-3GPP access network selection information or a combination of WLANSP rule(s) and non-3GPP access network selection information.

• Predefined PCC Rule: a PCC rule that has been provisioned directly into the SMF by the operator.

• Redirection: Redirect the detected service traffic to an application server (e.g. redirect to a top-up / service provisioning page).

• Service data flow: An aggregate set of packet flows carried through the UPF that matches a service data flow template.

• Service data flow filter: A set of packet flow header parameter values/ranges used to identify one or more of the packet flows in the UPF.

• Service data flow filter identifier: A scalar that is unique for a specific service data flow (SDF) filter within a PDU Session. • Service data flow template: The set of service data flow filters in a PCC Rule or an application identifier in a PCC rule referring to an application detection filter in the SMF or in the UPF, required for defining a service data flow.

• Service identifier: An identifier for a service. The service identifier provides the most detailed identification, specified for flow based charging, of a service data flow. A concrete instance of a service may be identified if additional AF information is available.

• Session based service: An end user service requiring application level signalling, which is separated from service rendering.

• Spending limit: A spending limit is the usage limit of a policy counter (e.g. monetary, volume, duration) that a subscriber is allowed to consume.

• Spending limit report: a notification, containing the current policy counter status generated from the CHF to the PCF.

• Subscribed guaranteed bandwidth QoS: The per subscriber, authorized cumulative guaranteed bandwidth QoS which is provided by the UDR to the PCF.

• Subscriber category: is a means to group the subscribers into different classes, e.g. gold user, silver user and bronze user.

• UE Local Configuration: Information about the association of an application to either a PDU Session or to non-seamless Offload is configured in the Mobile Termination (MT) and in the Terminal Equipment (TE). For example, UE Local Configuration can include operator specific configuration (e.g. operator provided S-NSSAI(s)), or application specific parameters to set up a PDU Session or end user configuration for specific applications.

• UE policy information: Policy information preconfigured in the UE and/or provisioned to the UE for access selection (i.e. ANDSP), PDU Session selection (i.e. URSP), V2X communications (i.e. V2XP) and/or ProSe operations (i.e. ProSeP).

• Uplink binding verification: The network enforcement of terminal compliance with the negotiated uplink traffic mapping to QoS Flows.

• User Preferences On Non-3GPP Access Selection: The list of configuration parameters provided by a layer (e.g. application) above NAS and used by the UE for access network discovery and selection. • VPLMN specific URSP Rules: A VPLMN specific URSP Rule is applicable when the UE is registered in the VPLMN. VPLMN specific URSP rules are provided from the HPLMN and contains, based on agreements with VPLMN, HPLMN values for Network Slice Selection Policies and DNN Selection Policies. When provided, the Time and

• Location criteria in each of the RSD contain VPLMN values. It is provided to the UE to route traffic on a PDU Session to a SMF and UPF in the VPLMN.

Provision of URSP to route traffic to the VPLMN

The H-PCF may provision VPLMN specific URSP Rules to UE for the purpose to route traffic to the VPLMN. The H-PCF may use application guidance on URSP determination, received from the V-PCF or retrieved from UDR at the HPLMN, as input to generate new or update existing VPLMN specific URSP Rules, as well as other input data as described in clause 6.2.1.1. The list of parameters provided for application guidance on URSP Rule determination is defined in clause 4.15.6.10 of 3GPP TS 23.502. The AF may provide application guidance on URSP Rule determination to the VPLMN or to the HPLMN.

When the AF provides application guidance on URSP Rule determination to the VPLMN, it will target “any inbound roamer”, and optionally per PLMN ID(s), the NEF in the VPLMN authorizes requests based on local configuration using e.g., the AF identifier before storing them in UDR, as defined in in clause 4.15.6.7 of 3GPP TS 23.502. The NEF in the VPLMN rejects any request for a GPSI or an External-Group-ID of a different PLMN. The UDR in the VPLMN notifies the V-PCF(s) that has subscribed to the reception of application guidance on URSP determination.

When the AF provides application guidance on URSP Rule determination to the HPLMN, it will target either a GPSI or an External-Group-ID or “any UE” of the HPLMN. The

NEF in the HPLMN, may, based on the HPLMN operator local policy, authorize any request for a GPSI or an External-Group-ID and maps it into a SUPI or an Internal- Group-ID via UDM, before storing them in UDR as Application Data. The UDR notifies the H-PCF(s) that has subscribed to the reception of application guidance on URSP determination.

The Application guidance on traffic routing may contain the VPLMN ID(s) where the Service Parameters apply. If the VPLMN ID is not included, i.e., when the V-PCF provides. Application guidance on traffic routing to the H-PCF, the H-PCF applies the VPLMN ID of the PLMN where the UE is roaming.

When the UE Policy Association is established or the V-PCF receives updates on application guidance on URSP determination for a SUPI that has a UE Policy Association established, the V-PCF checks whether application guidance on URSP determination exists and applies for the SUPI then the V-PCF:

- maps the S-NSSAI of the VPLMN into the S-NSSAI of the HPLMN and maps the DNN of the VPLMN into the DNN of the HPLMN based on local configuration, and

- subscribes to the result of the delivery of UE Policies if it was requested by the AF to the H-PCF, using the event reporting on “Notification on outcome of UE Policies delivery" described in clause 6.1.3.18.

The H-PCF generates new or updated URSP Rules using the application guidance on URSP Rule determination where the VPLMN ID included in the Service Parameters is used to indicate to the UE that this URSP Rule applies when the UE is registered in the VPLMN ID. The H-PCF provides the list of PSIs applicable per VPLMN ID to the UE.

When providing the new or updated RSDs to the UE with a new DNN, the H-PCF may also provide or update the list of DNNs and its corresponding S-NSSAI value that are used in those RSDs to the V-PCF. At the reception of this list, the V-PCF sets the PCRT for “SMF selection management” to the AMF to contact the V-PCF at PDU Session establishment (as specified in clause 6.1.2.5) including the list of DNNs and corresponding S-NSSAI provided by the HPLMN. When the PCRT is triggered, the AMF contacts the V-PCF that replaces the DNN value of the HPLMN to a DNN value in the VPLMN locally and provide it to the AMF to enable selection of an SMF at the VPLMN, see clause 4.3.2.2.1 of 3GPP TS 23.502.

How the UE associates applications to PDU Sessions based on URSP Rules may follow the same procedure as described in clause 6.6.2.3.

Distribution of the policies to UE

The UE policy control enables the PCF to provide UE access selection related policy information, PDU Session related policy information and V2X Policy information to the UE, i.e. UE policies, that includes Access network discovery & selection policy (ANDSP) or UE Route Selection Policy (URSP) or V2X Policy (V2XP) or ProSe Policy (ProSeP) or their combinations using Npcf and Namf service operations.

The PCF may be triggered to provide the UE policy information during UE Policy Association Establishment and UE Policy Association Modification procedures as defined in clause 4.16.11 and clause 4.16.12 of 3GPP TS 23.502. NOTE 1: The PCF can install a PCC Rule and activate start and stop of application detection in the SMF. When the same PCF is selected for SM policy association control and UE policy association control, the reporting of start and stop of an application can trigger the installation or update of a URSP rule in the UE to send the application traffic to the PDU Session as defined in the URSP rule. NOTE 2: The PCF can subscribe to the UDR on service specific information change, which will be taken into consideration by the PCF to determine the updated V2XP and ProSeP as defined in clause 4.15.6.7 of 3GPP TS 23.502.

Operator defined policies in the PCF may depend on input data such as UE location, time of day, information provided by other NFs, etc. as defined in clause 6.2.1.2. The PCF includes the UE policy information delivered to the UE into a Policy Section identified by a Policy Section Identifier (PSI). The PCF may divide the UE policy information into different Policy Sections, each one identified by a PSI. Each Policy Section provides a list of self-contained UE policy information to the UE, via AMF. The PCF may ensure that a Policy Section is under a predefined size limit, known by the PCF. NOTE 3: The size limit to allow the policy information to be delivered using NAS transport is specified in 3GPP TS 29.507 version 18.0.0 dated 2022-12-16. The size limit is configured in the PCF.

A list of self-contained UE policy information may imply that:

- when the PCF delivers URSP rules to the UE, the PCF provides the list of URSP rules in the order of precedence and without splitting a URSP rule across Policy Sections.

- when the PCF delivers V2XP to the UE, the PCF provides the list of V2XP in the order of precedence and without splitting a V2XP across Policy Sections;

- when the PCF delivers ProSeP to the UE, the PCF provides the list of ProSeP in the order of precedence and without splitting a ProSeP across Policy Sections;

- when the PCF delivers WEANSP rules, the list of WEANSP rules are provided in the order of priority and without splitting a WEANSP rule across Policy Sections;

- when the PCF delivers the non-3GPP access network selection information, the whole list of non-3GPP access network selection information (as defined in clause 6.6.1.1) is provided in one Policy Section.

It is up to the PCF to decide how to divide the UE policy information into Policy Sections as long as the requirements for the predefined size limit and the self-contained content (described above) are fulfilled. NOTE 4: The Policy Section list can be different per user. One PSI and its corresponding content can be the same for one or more users. NOTE 5: The PCF may, for example, assign the URSP as one whole Policy Section, or it may subdivide the information in the URSP into multiple Policy Sections by assigning one or several URSP rules to each Policy Section.

The PLMN ID may be provided to the UE together with UE policy information and it is used to indicate which PLMN a Policy Section list belongs to. The AMF forwards the UE policy information transparently to the UE. If the (H-)PCF decides to split the UE policies to be sent to the UE, the PCF provides multiple PolicySections separately to the AMF and then AMF uses UE configuration Update procedure for transparent UE policies delivery procedure to deliver the policies to the UE, this is defined in clauses 4.2.4.3 and 4.16 of 3GPP TS 23.502. NOTE 6: The AMF does not need to understand the content of the UE policy, rather send them to the UE for storage.

The UE may update the stored UE policy information with the one provided by the PCF as follows (details are specified in 3GPP TS 24.501):

- If the UE has no Policy Sections with the same PSI, the UE stores the Policy Section;

- If the UE has an existing Policy Section with the same PSI, the UE replaces the stored Policy Section with the received information;

- The UE removes the stored Policy Section if the received information contains only the PSI.

The UE keeps the received UE policies stored even when registering in another PLMN. The number of UE policies to be kept stored in the UE for PLMNs other than the HPLMN is up to UE implementation. If necessary, e.g. the number of UE policies stored in UE for PLMNs exceeds the maximum value, the UE may remove earlier stored UE policy in UE. NOTE 7: For aspects related to URSP rules for an SNPN-enabled UE, please refer to clause 6.6.2.2.2.

The ANDSP for VPLMN, if provided within the UE policy in the UE Configuration Update procedure described in clause 4.2.4.3 of 3GPP TS 23.502, applies to the equivalent PLMN(s) indicated in the last received list of equivalent PLMNs in Registration Accept. At Initial Registration or the Registration to 5GS when the UE moves from EPS to 5GS:

- The UE provides the list of stored PSIs which identify the Policy Sections associated to the home PLMN and the visited PLMN (if the UE is roaming) that are currently stored in the UE. If USIM is changed, the UE does not provide any PSI. If no policies are stored in the UE for the home PLMN, the UE does not provide any PSI associated to the home PLMN. If the UE is roaming and has policies for the home PLMN but no associated policies for the visited PLMN the UE includes only the list of PSIs associated to the home PLMN.

- UE may indicate its ANDSP support to the PCF. If it is received, the PCF may take it into account for the determination on whether to provide the ANDSP to the UE. The PCF does not provide ANDSP rules to the UE if the UE does not indicate support for ANDSP. NOTE 8: In the roaming scenario, during AMF relocation with V-PCF change, if the H-PCF does not provide the Indication of UE support for ANDSP, then the behaviour of V-PCF to determine whether to provide ANDSP rules to the UE is implementation specific.

- UE may indicate the V2X Policy Provisioning Request in the UE Policy Container. If this indication is received, the PCF includes V2XP in the UE policy information as defined in clause 6.2.2 of 3GPP TS 23.287 version 17.5.0 dated 2022-12- 21 (hereinafter “3GPP TS 23.287”).

- UE may indicate the 5G ProSe Policy and Parameter Provisioning Request in the UE Policy Container. If this indication is received, the PCF includes ProSeP in the UE policy information as defined in clause 6.2.2 of 3GPP TS 23.304 version 18.0.0 dated 2022-12-21 (hereinafter “3GPP TS 23.304”). PCF determines contents of ProSeP based on the information contained in the 5G ProSe Policy and Parameter Provisioning Request as defined in clause 4.3.1 of 3GPP TS 23.304.

- The UE may also provide the OSId.

The UE may trigger an Initial registration with the list of stored PSIs to request a synchronization for example if the UE powers up without USIM being changed. During Initial Registration, the (H-)PCF retrieves the list of PSIs and its content stored in the (H- )UDR for this SUPI while the V-PCF (in the roaming scenario) retrieves the list of PSIs and its content stored in the V-UDR for the PLMN ID of this UE (alternatively, the V- PCF can have this information configured locally). NOTE 9: The PSI list and content stored/configured for a PLMN ID can be structured according to, e.g., location areas (e.g., TAs, PRAs). The V-PCF can then provide PSIs and its content only if they correspond to the current UE location. The PCF provides to the UE the tuple (PLMN ID, list of PSIs associated with the PLMN ID) and the Policy Sections containing URSP Rules. In roaming scenarios, the H-PCF provides this information via V-PCF. When the UE is registered to a VPLMN, the UE evaluates URSP Rules that are associated with the VPLMN ID and, if there is a match, the UE follows the URSP rule to establish the PDU session. If the UE does not find a match that is associated with the VPLMN ID, the UE uses the URSP rules associated with the HPLMN ID.

In the roaming scenario, the V-PCF may also forward any UE provided PSIs that are associated to the home PLMN to the H-PCF. When the PCF (i.e., the (H-)PCF as well as the V-PCF) receives a list of PSIs associated to the PLMN of the PCF from the UE, the PCF compares the list of PSIs provided by the UE and the list of PSIs retrieved from the UDR. In addition, the PCF checks whether the list of PSIs provided by the UE or its content needs to be updated according to operator policies, e.g., change of Location and/or time. If the two lists of PSIs are different or an update is necessary according to operator policies (which includes the case that the UE did not provide a list of PSIs associated to the PLMN of the PCF), the PCF provides the changes in the list of PSIs or the corresponding content to the AMF which forwards them to the UE. The (H-)PCF maintains the latest list of PSIs delivered to each UE as part of the information related to the Policy Association until the UE policy association termination request is received from the AMF. Then the (H-)PCF stores the latest list of PSIs and its contents in the (H-)UDR using the Nudr_DM_Update including DataSet "Policy Data" and Data Subset "Policy Set Entry". The (H-)PCF may use the PEI provided by the AMF and/or the OSId provided by the UE, to determine the operating system of the UE.

If the PEI, the OSId or the indication of UE support for ANDSP is available to the (H-)PCF, the (H-)PCF stores them in the (H-)UDR using Nudr_DM_Create including DataSet "Policy Data" and Data Subset "UE context policy control data" when such information is received from the UE in the UE Policy Container. If the (H-)PCF is not able to determine the operating system of the UE, and if the (H-)PCF requires to deliver URSP rules that contain Application descriptors as Traffic Descriptors, then the Traffic Descriptors of such URSP rules include multiple instances of Application descriptors each associated to supported UE operating systems by the network operator implementation.

If the (H-)PCF determines the operating system of the UE and if the (H-)PCF requires to deliver URSP rules that contain Application descriptors as Traffic Descriptors, then the Traffic Descriptors of such URSP rules include the Application descriptors associated with the operating system determined by the PCF. NOTE 10: If the PCF does not take into account the received PEI and/or OSId then the PCF can send URSP rules containing application traffic descriptors associated to multiple operating systems.

Policy Control Request Triggers relevant for AMF The Policy Control Request Triggers relevant for AMF and 3GPP access type are listed in table 6.1.2.5-1 and define the conditions when the AMF may interact again with PCF after the AM Policy Association Establishment or UE Policy Association Establishment. The PCF provides Policy Control Request Triggers to the AMF indicating a specific UE (i.e., SUPI or PEI) in the Policy Association establishment and modification procedures defined in the 3GPP TS 23.502. The Policy Control Request Triggers are transferred from the old AMF to the new AMF when the AMF changes. The Policy Control Request Triggers may not be applicable any longer at termination of the AM Policy Association or termination of UE Policy Association. Table 6.1.2.5-1: Policy Control Request Triggers relevant for AMF and 3GPP access type.

NOTE: In the following description of the Policy Control Request Triggers relevant for AMF and 3GPP access type, the term trigger is used instead of Policy Control Request Trigger where appropriate. If the Location change trigger are armed, the AMF may activate the relevant procedure which reports any changes in location as explained in clause 5.6.11 of 3GPP TS 23.501 by subscribing with the Npcf_AMPolicyAssociation service or Npcf_UEPolicyAssociation service. The reporting is requested to the level indicated by the trigger (i.e., Tracking Area). The AMF reports that the Location change trigger was met and the Tracking Area identifier.

If the Change of UE presence in Presence Reporting Area trigger is armed, i.e., the PCF subscribed to reporting change of UE presence in a Presence Reporting Area, including a list of PRA ids. In addition, for "UE-dedicated Presence Reporting Area" a short list of TAs and/or NG-RAN nodes and/or cells identifiers is included. Then, the AMF may activate the relevant procedure which reports any Change of UE presence in Area of Interest as explained in clause 5.6.11 of 3GPP TS 23.501. The reporting is requested for the specific condition when target UE moved into a specified PRA. The AMF reports the PRA Identifier(s) and indication(s) whether the UE is inside or outside the Presence Reporting Area(s) to the PCF.

The Service Area restriction change trigger and the RFSP index change trigger may trigger the AMF to interact with the PCF for all changes in the Service Area restriction or RFSP index data received in AMF from UDM. The reporting includes that the trigger is met and the subscribed Service Area restriction or the subscribed RFSP index provided to AMF by UDM, as described in clause 6.1.2.1.

The Change of the Allowed NSSAI trigger may trigger the AMF to interact with the (V-)PCF if the Allowed NSSAI has been changed. The reporting includes that the trigger is met and the new Allowed NSSAI. (V-)The PCF may update RFSP index and/or SMF selection management related policy information (described in clause 6.5) in the AMF based on the Allowed NSSAI.

The Generation of a Target NSSAI trigger may trigger the AMF to interact with the PCF. The reporting includes that the trigger is met and the generated Target NSSAI. The PCF may generate RFSP index associated with the Target NSSAI. The UE-AMBR change trigger may trigger the AMF to interact with the PCF for all changes in the subscribed UE-AMBR data received in AMF from UDM. The reporting includes that the trigger is met and the subscribed UE-AMBR provided to AMF by UDM, as described in clause 6.1.2.1. The Slice-UE-MBR change trigger may trigger the AMF to interact with the PCF for all changes in the Subscribed UE-Slice-MBR for each subscribed S-NSSAI in the NSSAI with a Subscribed UE-Slice-MBR received at the AMF from UDM. The reporting includes that the trigger is met, as described in clause 6.1.2.1. If the PLMN change trigger is armed, the AMF may report it to the PCF to trigger the update of V2X service authorization parameters to the UE as defined in clause 6.2.2 of 3GPP TS 23.287 and to trigger the update of ProSe authorization parameters to the UE as defined in clause 6.2.2 of 3GPP TS 23.304. The reporting includes the event with the serving PLMN ID.

If the SMF selection management trigger is set, then the AMF may contact the (V- )PCF when the AMF detects that the UE requested an unsupported DNN and the (V-)PCF indicated DNN replacement of unsupported DNNs in the Access and mobility related policy information (see clause 6.5 of, for example, 3GPP TS 23.304). The (V-)PCF may select a DNN and provide the selected DNN to the AMF.

If the SMF selection management trigger is set, then the AMF may contact the (V- )PCF when the UE requested a DNN within the list of DNN candidates for replacement for the S-NSSAI indicated in the Access and mobility related policy information (see clause 6.5). The (V-)PCF may select the DNN and provide the selected DNN to the AMF. If the Connectivity state changes trigger is set, then the AMF may notify the PCF when the UE connectivity state is changed e.g. from IDLE to CONNECTED. The AMF then reset the trigger.

The NWDAF info change trigger may trigger the AMF to interact with the PCF when the list of NWDAF Instance IDs used for the UE or associated Analytics IDs used for the UE at the AMF are changed in the AMF.

Access and mobility related policy information

To enable the enforcement in the 5GC system of the access, and mobility and PDU Session related policy decisions made by the PCF to the AMF for the control of the service area restrictions and RFSP Index, the 5GC system may provide the Access and mobility related policy information from the PCF to the AMF.

Table 6.5-1: Access and mobility related policy information

The list of allowed TAIs indicates the TAIs where the UE is allowed to be registered, see clause 5.3.4 of 3GPP TS 23.501 for the description on how AMF uses this information. The list of non-allowed TAIs indicates the TAIs where the UE is not allowed to be registered, see clause 5.3. of 3GPP TS 23.501 for the description on how AMF uses this information. The Maximum number of allowed TAs indicates the maximum number of allowed Tracking Areas, the list of TAI is defined in the AMF and not explicitly provided by the PCF. The RFSP Index for Allowed NSSAI and RFSP Index for Target NSSAI defines the RFSP Index for radio resource management functionality. The UE- AMBR limits the aggregated bit rate across all Non-GBR QoS Flows of a UE in the serving network.

The list of UE-Slice-MBR defines the list of authorized UE-Slice-MBR allocated for a UE, how it is enforced is described in clause 5.7.1.10 of 3GPP TS 23.501. The DNN replacement of unsupported DNNs indicates that the AMF may contact the (V-)PCF for replacement of an unsupported DNN requested by the UE. The List of S-NSSAIs defines the S-NSSAIs, valid in the serving network, of the Allowed NSSAI that contain DNN candidates for replacement by (V-)PCF. The V-PCF receives the list of HPLMN S- NSSAIs from the H-PCF. The V-PCF maps it into S-NSSAI values, valid in the serving network, of the Allowed NSSAI then uses it to set the list of SNSSAIs to the AMF.

The List of DNNs defines the DNN candidates for which the AMF may contact the (V-)PCF for replacement if such a DNN is requested by a UE. The V-PCF receives the list of HPLMN DNNs that are candidate for replacement from the HPLMN, then uses to set the list of DNNs to the AMF. The 5G access stratum time distribution indicates the 5G access stratum time distribution parameters to be indicated to the NG- RAN via AMF.

Event reporting from the PCF

The AF may subscribe/unsubscribe to notifications of events from the PCF for the PDU Session to which the AF session is bound. The AF can either subscribe/unsubscribe directly at the PCF or indirectly via an NEF or a TSCTSF.

The PCF for the UE may subscribe/unsubscribe to notifications of events from the PCF for the PDU Session of a UE. Other NFs may subscribe/unsubscribe to notifications of events from the PCF for a PDU Session or for a UE. The events that can be subscribed by the AF and by other NFs are listed in Table 6.1.3.18-1.

If an AF requests the PCF to report the PLMN identifier where the UE is currently located, then the PCF may provide the PLMN identifier or the SNPN identifier to the AF if available. Otherwise, the PCF may provision the corresponding PCC rules, and the Policy Control Request Trigger to report PLMN change to the SMF. The PCF may, upon receiving the PLMN identifier or the SNPN identifier from the SMF forward this information to the AF, including the PLMN Id and if available the NID. If the H-PCF requests to report the PLMN identifier where the UE is currently located, the VPCF provisions the PCRT on “PLMN change” to the AMF as described in clause 6.1.2.5 and then forwards the PLMN ID received from the AMF to the H-PCF. If an AF requests the PCF to report on the change of Access Type, the PCF may provide the corresponding Policy Control Request Trigger to the SMF to enable the report of the Change in Access Type to the PCF. The PCF may, upon reception of information about the Access Type the user is currently using and upon indication of change of Access Type, notify the AF on changes of the Access Type and forward the information received from the SMF to the AF. The change of the RAT Type may also be reported to the AF, even if the Access Type is unchanged. For MA PDU Session the Access Type information may include two Access Type information that the user is currently using. If an AF requests the PCF to report on the signalling path status, for the AF session, the PCF may, upon indication of removal of PCC Rules identifying signalling traffic from the SMF report it to the AF.

If an AF requests the PCF to report Access Network Charging Correlation Information, the PCF may provide to the AF the Access Neltwork Charging Correlation Information, which allows to identify the usage reports that include measurements for the Service Data Flow(s), once the Access Network Charging Correlation Information is known at the PCF.

If an AF requests the PCF to report Access Network Information (i.e., the User Location Report and/or the UE Timezone Report) at AF session establishment, modification or termination, the PCF may set the Access Network Information report parameters in the corresponding PCC rule(s) and provision them together with the corresponding Policy Control Request Trigger to the SMF. For those PCC rule(s) based on preliminary service information the PCF may assign the 5QI and ARP of the QoS Flow associated with the default QoS rule to avoid signalling to the UE.

NOTE 1: The PCF can also use the dynamic or pre-defined PCC Rules related to the IMS signalling to request Access Network Information reporting. This can be used to support, e.g., regulatory requirements for SMS over IP, where the IMS network (i.e., P- CSCF) needs to retrieve the user location and/or UE Time Zone information. Note that due to regulatory requirements, the Access Network Information can be requested for SMS over IP, impacting a large number of PDU Sessions, that can lead to significant increase in signalling load when the Access Network Information is requested from AMF.

The PCF may, upon receiving an Access Network Information report corresponding to the AF session from the SMF, forward the Access Network Information as requested by the AF (if the SMF only reported the serving PLMN identifier or the SNPN identifier to the PCF, as described in clause 6.1.3.5, the PCF may forward it to the AF). For AF session termination the communication between the AF and the PCF may be kept alive until the PCF report is received.

If an AF requests the PCF to report the Usage for Sponsored Data Connectivity, the PCF may provision the corresponding PCC rules, and the Policy Control Request Trigger to the SMF. If the usage threshold provided by the

AF has been reached or the AF session is terminated, the PCF forwards such information to the AF.

If an AF requests the PCF to report the Service Data Flow deactivation, the PCF may report the release of resources corresponding to the AF session. The PCF may, upon being notified of the removal of PCC Rules corresponding to the AF session from the SMF, forward this information to the AF. The PCF may also forward, if available, the reason why the resources are released, the user location information and the UE Timezone.

If an AF requests the PCF to report the Resource allocation outcome, the PCF may report the outcome of the resource allocation of the Service Data Flow(s) related to the AF session. The AF may request to be notified about successful or failed resource allocation. In this case, the PCF may instruct the SMF to report the successful resource allocation trigger (see clause 6.1.3.5). If the SMF has notified the PCF that the resource allocation of a Service Data Flow is successful and the currently fulfilled QoS matches an Alternative QoS parameter set (as described in clause 6.2.2.1), the PCF may also provide to the AF the QoS Reference parameter or the Requested Alternative QoS Parameter Set which corresponds to the Alternative QoS parameter set referenced by the SMF. If an AF requests the PCF to report when the QoS targets can no longer (or can again) be fulfilled for a particular media flow, the PCF may set the QNC indication in the corresponding PCC rule(s) that includes a GBR or delay critical GBR 5QI value and provision them together with the corresponding Policy Control Request Trigger to the SMF. At the time, the SMF notifies that GFBR can no longer (or can again) be guaranteed for a QoS Flow to which those PCC Rule(s) are bound, the PCF may report to the AF the affected media flow and provides the indication that QoS targets can no longer (or can again) be fulfilled. If additional information is received with the notification from SMF (see clause 5.7.2.4 of 3GPP TS 23.501), the PCF may also provide to the AF the QoS Reference parameter or the Requested Alternative QoS Parameter Set which corresponds to the Alternative QoS parameter set referenced by the SMF. If the SMF has indicated that the lowest priority Alternative QoS parameter set cannot be fulfilled, the PCF may indicate to the AF that the lowest priority QoS Reference or the lowest priority set of Requested Alternative QoS Parameters of the Alternative Service Requirements cannot be fulfilled. If the AF subscribes to be notified of the QoS Monitoring reports, the PCF decides about the path for the QoS Monitoring reports and sets the QoS Monitoring for URLLC Policy Control Request Trigger accordingly, as described in clause 6.1.3.21. The PCF may further send the QoS Monitoring reports it receives from the SMF to the AF, unless the AF has provided an indication of direct event notification (i.e., in this case, the AF will receive the QoS Monitoring reports directly from the UPF). NOTE 2: This event may only be subscribed as part of an AF session with required QoS (described in clause 6.1.3.22). If an AF requests the PCF to report on the Out of credit event for the associated service data flow(s), the PCF may inform the AF (when it gets informed by the SMF) that credit is no longer available for the services data flow(s) related to the AF session together with the applied termination action. If an AF requests the PCF to report on the Reallocation of credit event for the associated service data flow(s), the PCF may inform the AF (when it gets informed by the SMF) that credit has been reallocated after credit was no longer available and the termination action was applied for the service data flow(s) related to the AF session.

The PCF can arm the trigger of 5GS Bridge information available to SMF based on local policy (i.e., without an AF request) or based on subscription request from TSCTSF. The PCF may, upon reception of the 5GS Bridge information (refer to clause 6.1.3.23) from the SMF, forward this information to the TSN AF or the TSCTSF. When the PCF has received the User plane node Management Information Container or Port Management Information Container and related port number from SMF, the PCF also provides User plane node Management Information Container or Port Management Information Container and related port number to the TSN AF or TSCTSF. When SMF has reported the 5GS Bridge information and no AF session exists, the PCF forward this information to a pre-configured TSN AF, or to a pre-configured TSCTSF or a TSCTSF discovered and selected via NRF. In the case of private IPv4 address being used for IP type PDU Session, the PCF may additionally report DNN and S-NSSAI of the PDU Session to TSCTSF.

If the AF requests the PCF to report on the outcome of the service area coverage change, the PCF reports the outcome of the service area coverage change to the AF and notifies the current service area coverage to the AF. The outcome is the result of the execution of the request of service coverage change at the PCF; the outcome is successful if the request was executed, and includes the current service area coverage that may be the same or different from the service area coverage provided by the AF. The subscription may also be implicit. In this case there may be bulk subscription, either for an Internal- Group-Id or for any UE. In order to prevent massive notifications to the AF, the request for any UE is associated to a specific Application Identifier or DNN, S-NSSAI. For bulk subscription, when the AF request includes an expiration time, the PCF stops reporting to the AF when the expiration time is reached. If the AF requests the (H-)PCF, via V-PCF when roaming, to report on the outcome of the UE Policies delivery due to service specific parameter provisioning procedure targeting a single UE, the (H-)PCF reports the outcome of the related UE Policies provisioning procedure for the related traffic descriptor for the UE to the AF, via V-PCF when roaming. The outcome of the UE Policies provisioning procedure includes the success, the failure with an appropriate cause or the interim status report such as UE is temporarily unreachable. (See clauses 4.15.6.7 and 5.2.5.7 of 3GPP TS 23.502) A request to report Start of application traffic detection and Stop of application traffic detection triggers the reporting when the PCF receives start of application traffic detection event or stop of application traffic detection event from SMF. The reception of a subscription to this event triggers the setting of the corresponding Policy Control Request Trigger to SMF, if not already subscribed.

If an AF requests the PCF to report on the change between different satellite backhaul categories (i.e., GEO, MEO, FEO, OTHERS AT) or the change between satellite backhaul and non-satellite backhaul, the PCF may provide the corresponding Policy Control Request Trigger to the SMF to enable the report of satellite backhaul category change (see clause 6.1.3.5) to the PCF. The PCF may, upon reception of information about the change between satellite backhaul categories or change between satellite backhaul and non-satellite backhaul, notify the AF on the satellite backhaul category change event was met and forward the current satellite backhaul category information received from the SMF to the AF, or indicate that a satellite backhaul is no longer used. If 5G DDNMF requests the PCF to report on the Change of PDUID, the PCF may notify whenever a new PDUID is allocated. Further details on how the 5G DDNMF retrieves and subscribes to notifications on Change of PDUID are defined in 3GPP TS 23.304. A request to report SM Policy Association established or terminated triggers the reporting when the PCF receives the request for notification on the SM Policy Association from SMF. The PCF notifies on the EventID "SM Policy Association established/terminated", includes the PCF binding information of the PCF for the PDU Session of the UE, as described in clause 6.1.1.2.2.

As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible (i.e. non- transitory) computer readable medium may be utilized including hard disks, CD-ROMs, electonic storage devices, optical storage devices, or magnetic storage devices.

Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows. Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is claimed is:

1. A method in a visited policy control function, V-PCF, core node (15d) configured to communicate with and configure a wireless device, WD, (22) the V-PCF core node (15d) being associated with a visited public land mobile network, V-PLMN, (I la), the method comprising: obtaining (SI 50) a first indication: indicating one or more service parameters for the WD (22), the one or more service parameters being associated with a registration and roaming of the WD (22) from a home public land mobile network, H-PLMN, (1 lb) to the V-PLMN (I la); and including a request to notify an application function, AF, core node (15a) about a policy delivery outcome concerning delivery of the one or more service parameters; transmitting (SI 52) to a home policy control function, H-PCF, core node (15e) a second indication indicating one or more of the service parameters of the first indication, the second indication further indicating notification information associated with the policy delivery outcome related to the one or more service parameters; receiving (SI 54), from the H-PCF core node (15e) responsive to the second indication, a third indication indicating the policy delivery outcome; and transmitting (SI 56), responsive to receiving the third indication, a fourth indication to a network exposure function, NEF, core node (15b) associated with the V-PLMN (I la), the fourth indication indicating the policy delivery outcome.

2. The method of Claim 1, wherein the notification information indicates one or more of: one or both of a trigger and a request for notification of the policy delivery outcome; one or more subscribed events; and an address associated with one or both the V-PCF core node (15d) and the NEF core node (15b) for the notification of the policy delivery outcome.

3. The method of any one of Claims 1 and 2, wherein obtaining the first indication includes retrieving the first indication from a UDR core node (15c) or receiving the first indication from the UDR core node (15c).

4. The method of any one of Claims 1-3, further comprising: one or both of determining and identifying the H-PCF core node (15e) associated with the H-PLMN (llb).

5. The method of any one of Claims 1-4, wherein the fourth indication is configured to cause the NEF core node (15b) to map the one or more service parameters to information associated with one or both of the WD (22) and the V-PLMN (I la).

6. The method of any one of Claims 1-5, wherein the fourth indication is further configured to cause the NEF core node (15b) to transmit policy delivery outcome information to the AF core node (15a) associated with the V-PLMN (1 la) based on the notification information.

7. The method of any one of Claims 1-6, wherein the one or more service parameters correspond to information indicating whether application guidance on a user equipment, UE, route selection policy, URSP, determination associated with the WD exists and applies to a subscription permanent identifier, SUPI.

8. The method of any one of Claims 1-7, wherein transmitting the second indication corresponds with the V-PCF core node (15d) subscribing to the policy delivery outcome.

9. The method of Claim 8, wherein the policy delivery outcome corresponds to a result of delivery of UE policies, and the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE policies.

10. The method of Claim 9, wherein the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE policies is performed if requested by the AF core node (15a) to the H-PCF core node (15e), using an event reporting.

11. A visited policy control function, V-PCF, core node (15d) configured to communicate with and configure a wireless device, WD, (22) the V-PCF core node (15d) being associated with a visited public land mobile network, V-PLMN, (I la), the V-PCF being configured to: obtain a first indication: indicating one or more service parameters for the WD (22), the one or more service parameters being associated with a registration and roaming of the WD (22) from a home public land mobile network, H-PLMN, (1 lb) to the V-PLMN (I la); and including a request to notify an application function, AF, core node (15a) about a policy delivery outcome concerning delivery of the one or more service parameters; transmit to a home policy control function, H-PCF, core node (15e) a second indication indicating one or more of the service parameters of the first indication, the second indication further indicating notification information associated with a policy delivery outcome related to the one or more service parameters; receive, from the H-PCF core node (15e) responsive to the second indication, a third indication indicating the policy delivery outcome; and transmit, responsive to receiving the third indication, a fourth indication to a network exposure function, NEF, core node (15b) associated with the V-PLMN (I la), the fourth indication indicating the policy delivery outcome.

12. The V-PCF core node (15d) of Claim 11, wherein the notification information indicates one or more of: one or both of a trigger and a request for notification of the policy delivery outcome; one or more subscribed events; and an address associated with one or both the V-PCF core node (15d) and the NEF core node (15b) for the notification of the policy delivery outcome.

13. The V-PCF core node (15d) of any one of Claims 11 and 12, wherein obtaining the first indication includes retrieving the first indication from a UDR core node (15c) or receiving the first indication from the UDR core node (15c).

14. The V-PCF core node (15d) of any one of Claims 11-13, wherein the V- PCF core node (15d) is further configured to: one or both of determine and identify the H-PCF core node (15e) associated with the H-PLMN (llb).

15. The V-PCF core node (15d) of any one of Claims 11-14, wherein the fourth indication is configured to cause the NEF core node (15b) to map the one or more service parameters to information associated with one or both of the WD (22) and the V-PLMN (Ha).

16. The V-PCF core node (15d) of any one of Claims 11-15, wherein the fourth indication is further configured to cause the NEF core node (15b) to transmit policy delivery outcome information to the AF core node (15a) associated with the V-PLMN (I la) based on the notification information.

17. The V-PCF core node (15d) of any one of Claims 11-16, wherein the one or more service parameters correspond to information indicating whether application guidance on a user equipment, UE, route selection policy, URSP, determination associated with the WD exists and applies to a subscription permanent identifier, SUPI.

18. The V-PCF core node (15d) of any one of Claims 11-17, wherein transmitting the second indication corresponds with the V-PCF core node (15d) subscribing to the policy delivery outcome.

19. The V-PCF core node (15d) of Claim 18, wherein the policy delivery outcome corresponds to a result of delivery of UE policies, and the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE policies.

20. The V-PCF core node (15d) of Claim 19, wherein the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE policies is performed if requested by the AF core node (15a) to the H-PCF core node (15e), using an event reporting.

21. A method in a home policy control function, H-PCF, core node (15e) configured to communicate with configure a wireless device, WD, (22), the H-PCF core node (15e) being associated with a home public land mobile network, H-PLMN, (1 lb), the method comprising: receiving (SI 58) a first indication indicating one or more service parameters for the WD (22) associated with a registration and roaming of the WD (22) from the H-PLMN (1 lb) to a visited public land mobile network, V-PLMN, (I la), the first indication being received from a visited policy control function, V-PCF, core node (15d) associated with the V-PLMN (I la), the first indication further indicating notification information associated with a policy delivery outcome related to the one or more service parameters; determining (SI 60), responsive to the first indication, the policy delivery outcome associated with the WD (22); and transmitting (S162), to the V-PCF core node (15d) responsive to determining the policy delivery outcome, a second indication indicating the policy delivery outcome.

22. The method of Claim 21, further comprising: determining a notification destination based on the notification information, and wherein the notification information indicates one or more of: one or both of a trigger and a request for notification of the policy delivery outcome; one or more subscribed events; and an address associated with one or both the V-PCF core node (15d) and an NEF core node (15b) for the notification of the policy delivery outcome.

23. The method of any one of Claims 21 and 22, wherein the one or more service parameters correspond to information indicating whether application guidance on a user equipment, UE, route selection policy, URSP, determination associated with the WD exists and applies to a subscription permanent identifier, SUPI.

24. The method of any one of Claims 21-23, wherein the one or more service parameters are associated with the V-PCF core node (15d) subscribing to the policy delivery outcome.

25. The method of Claim 24, wherein the policy delivery outcome corresponds to a result of delivery of UE policies, and the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE policies.

26. The method of Claim 25, wherein the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE policies is performed if requested by an AF core node (15a) to the H-PCF core node (15e), using an event reporting.

27. A home policy control function, H-PCF, core node (15e) configured to communicate with configure a wireless device, WD, (22), the H-PCF core node (15e) being associated with a home public land mobile network, H-PEMN, (1 lb), the H-PCF core node (15e) being configured to: receive a first indication indicating one or more service parameters for the WD (22) associated with a registration and roaming of the WD (22) from the H-PLMN (1 lb) to a visited public land mobile network, V-PLMN, (I la), the first indication being received from a visited policy control function, V-PCF, core node (15d) associated with the V- PLMN (I la), the first indication further indicating notification information associated with a policy delivery outcome related to the one or more service parameters; determine, responsive to the first indication, the policy delivery outcome associated with the WD (22); and transmit, to the V-PCF core node (15d) responsive to determining the policy delivery outcome, a second indication indicating the policy delivery outcome.

28. The H-PCF core node (15e) of Claim 27, wherein the H-PCF core node is further configured to determine a notification destination based on the notification information, and wherein the notification information indicates one or more of: one or both of a trigger and a request for notification of the policy delivery outcome; one or more subscribed events; and an address associated with one or both the V-PCF core node (15d) and an NEF core node (15b) for the notification of the policy delivery outcome.

29. The H-PCF core node (15e) of any one of Claims 27 and 28, wherein the one or more service parameters correspond to information indicating whether application guidance on a user equipment, UE, route selection policy, URSP, determination associated with the WD exists and applies to a subscription permanent identifier, SUPI.

30. The H-PCF core node (15e) of any one of Claims 27-29, wherein the one or more service parameters are associated with the V-PCF core node (15d) subscribing to the policy delivery outcome.

31. The H-PCF core node (15e) of Claim 30, wherein the policy delivery outcome corresponds to a result of delivery of UE policies, and the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE policies.

32. The H-PCF core node (15e) of Claim 31, wherein the subscribing to the policy delivery outcome includes subscribing to the result of the delivery of UE policies is performed if requested by an AF core node (15a) to the H-PCF core node (15e), using an event reporting.