Rules relating to route selection

Abstract

According to an aspect, there is provided a method of operating a policy control node that is part of a core network of a first communication network. The method comprises: validating (601) one or more rules for the UE relating to route selection to determine if one or more rules are authorised; and, if one or more rules are determined to be unauthorised, sending (602), to a second node, an indication that one or more rules for a User Equipment, UE, relating to route selection are not authorised.

Description

[0001] Rules relating to route selection

[0002] Technical Field

[0003] This disclosure relates to a policy control node in a core network of a communication network, and in particular to rules for a User Equipment (UE) relating to route selection.

[0004]

[0005] As defined in the 3rdGeneration Partnership Project (3GPP) Technical Standard (TS) 23.502 v19.0.0, clause 4.15.6.7.1, Service Parameters are service specific information which needs to be provisioned in the Network and delivered to the User Equipment (UE) in order to support a service identified by a Service Description.

[0006] Service specific parameter provisioning by the Application Function (AF) to the Home Public Land Mobile Network (HPLMN)

[0007] 3GPP TS 23.502 v19.0.0, clause 4.15.6.7.2 specifies Service Parameter provisioning by the Application Function (AF) to the Home Public Land Mobile Network (HPLMN).

[0008] To authorize the AF request (including e.g. UE Route Selection Policy (URSP) influence data), a Network Exposure Function (NEF) (step 2.b) may authorize the service specific parameter provisioning request with a Unified Data Management (UDM) using the Nudm_ServiceSpecificAuthorization as shown in Fig. 1. Fig. 1 corresponds to Figure 4.15.6.7a-1 from 3GPP TS 23.502 v19.0.0: Service Specific Authorization for an individual UE or group of UEs.

[0009] The description of Figure 4.15.6.7a-1 from 3GPP TS 23.502 v19.0.0 is as follows (with bold added for emphasis):

[0010] The AF initiates the procedure as specified in clause 4.15.6.7.

[0011] 2. The NEF sends Nudm ServiceSpecificAuthorisation Create Request including the GPSI [Generic Public Subscription Identifier] or External Group Id, S-NSSAI / DNN, service type, (optional) AF ID, (optional) MTC Provider Information and notification address to receive updates of the authorization from UDM.

[0012] 3. The UDM maps the GPSI or External Group Id included in the request from the NEF to SUPI or Internal Group Id.

[0013] If the request is for an individual UE, the UDM checks the list of subscribed / allowed S- NSSAI / DNNs for the UE and other service info (e.g. MTC provider is authorized for the UE).If the request is for a group of UEs, the UDM checks whether the group related data (e.g. DNN / S-NSSAI group related data, see table 4.15.6.3b-1) and other service info, e.g. MTC provider is authorized for the group.

[0014] 4. The UDM responds to the NEF with the service authorization result. If authorization succeeds, the UDM includes the SUPI or Internal Group Id mapping the GPSI or External Group Id provided by the NEF.

[0015] If authorization fails (e.g. DNN is not subscribed for the UE or it is different from the group related data, UE subscription or group related data does not allow to modify URSP rules dynamically by an AF or by such specific AF or MTC provider), UDM returns a negative response with an appropriate error code and the NEF rejects the request with the proper error code to inform the AF about the request not authorized.

[0016] NOTE 1: The MTC Provider Information can be used by any type of Service Providers (MTC or non-MTC) or Corporate or External Parties for, e.g. to distinguish their different customers.

[0017] 5. The procedure continues as specified in clause 4.15.6.7.

[0018] Fig. 2 illustrates a procedure for updating or revoking an existing Service Specific Authorization. Fig. 2 corresponds to Figure 4.15.6.7a-2 from 3GPP TS 23.502 v19.0.0: Service Specific Authorization Update procedure.

[0019] The description of Figure 4.15.6.7a-2 from 3GPP TS 23.502 v19.0.0 is as follows:

[0020] 0. UDM provided a successful authorization for a request to provision service specific parameters as defined in Figure 4.15.6.7a-1. The authorization for the provisioning of the service specific parameters is modified in UDM (e.g. due to subscription withdrawal or to the DNN associated to the authorization being removed from UE subscription).

[0021] 1. The UDM sends a Nudm_ServiceSpecificAuthorisation_UpdateNotify Request (GPSI or External Group Id, SUPI or Internal Group Id, S-NSSAI, DNN, Service Type, (optional) AF ID, (optional) MTC Provider Information, Status, Cause) message to the NEF to update a UE's or group of UEs' authorization.

[0022] 2. The NEF sends Nudm_ServiceSpecificAuthorisation_UpdateNotify Response message to the UDM to acknowledge the authorization update.

[0023] 3. If the authorization is revoked, the NEF removes the service specific parameters from the UDR.

[0024] 4. The NEF informs the AF that the service parameters authorisation status has changed by sending Nnef_ServiceParameter_Notify Request (GPSI or External Group Id, TLTRI [T8Long Term Transaction Resource Identifier], Status, Cause) message to the AF to update the authorization.

[0025] 5. The AF responds to the NEF with Nnef_ServiceParameter_Notify Response message.

[0026] AF on LIRSP rule The AF guidance on LIRSP rules, as described in 3GPP TS 23.502 v19.0.0, clause 4.15.6.10, consists of a list of LIRSP rules, where for each LIRSP rule, the AF includes (with bold_added for emphasis):

[0027] - An application traffic descriptor, whose definition corresponds to that of the LIRSP Traffic Descriptors (as defined for the LIRSP rule in TS 23.503

[0020] Table 6.6.2.1-2). When AF provides application guidance for LIRSP determination for PIN, the application traffic descriptor shall include PIN ID.

[0028] - one or more sets of Route selection parameters, each parameter may correspond to:

[0029] - (DNN, S-NSSAI). This may be provided by the AF or determined by the NEF based on the AF Identifier when it is not provided by the AF and the AF provides only one instance of AF guidance for LIRSP determination. In the case of AF guidance for LIRSP determination for PIN [Personal loT Network], this shall be provided by the AF. - Requested PDU session type.

[0030] - (•••)

[0031] NOTE 2: The different sets of Route selection parameters indicate different sets of PDU Session information (DNN, S-NSSAI) that can be associated with applications matching the application traffic descriptor. Each set is meant to apply for a specific (set of) spatial validity condition. Each set is associated with a Route selection precedence to cope with the case where multiple spatial validity conditions overlap. - VPLMN ID(s) that indicates the PLMN(s) [Public Land Mobile Network(s)] where the AF guidance on URSP determination and all its RSD(s), applies.

[0032] the AF to a Visited Public Land Mobile Network

[0033]

[0034] 3GPP TS 23.502 v19.0.0, clause 4.15.6.7.3, specifies Service Parameter provisioning by the AF to the VPLMN. Fig. 3 corresponds to Figure 4.15.6.7.3-1 from 3GPP TS 23.502 v19.0.0: Service specific information provisioning by AF to VPLMN.

[0035] The description of Figure 4.15.6.7.3-1 from 3GPP TS 23.502 v19.0.0 is as follows:

[0036] 0a. Same as in step 0a of Figure 4.15.6.7.2-1 from 3GPP TS 23.502.Ob-Oc. The V-PCF may request to V-UDR on changes in UE policy information and H-PCF may subscribe to H-LIDR.

[0037] 1-2. Steps 1-2 of Figure 4.15.6.7.2-1 apply with the following differences:

[0038] - The AF and NEF belong to the VPLMN. The AF may belong to third party with agreement with VPLMN.

[0039] - When the AF provides application guidance on LIRSP Rule determination to the VPLMN, it will target "PLMN ID(s) of inbound roamers". The NEF in the VPLMN rejects any request for a GPSI or an External-Group-ID of a different PLMN.

[0040] 3-5. Steps 3-5 of Figure 4.15.6.7.2-1 apply with the following differences:

[0041] - AF, NEF and UDR belong to VPLMN. The AF may belong to third party with agreement with VPLMN.

[0042] - The UDR in the VPLMN notifies the V-PCF(s) [Visited-PCF(s)] that have subscribed to the reception of application guidance on URSP determination.

[0043] - In step 5, the V-PCF receives updates on application guidance on URSP determination for the PLMN ID of a SUPI that has a UE Policy Association established. The PLMN ID of the SUPI is included in the target "PLMN ID(s) of inbound roamers" in step 2. In this case, the V-PCF checks whether application guidance on URSP determination applies for the SUPI as specified in clause 6.1.2.2.4 of TS 23.503

[0020] ,

[0044] 5a. The V-PCF sends the Service Parameters including the mapped HPLMN S-NSSAI values to the H-PCF [Home-PCF(s)] and subscribes to the result of the delivery of UE Policies if the delivery result was requested by the AF, using the event reporting on "Notification on outcome of UE Policies delivery" described in clause 6.1.3.18 of TS 23.503

[0020] ,

[0045] NOTE: The AMF determines whether LBO is allowed and performs SMF selection to select the SMF in VPLMN for LBO case as described in clause 6.3.2 of TS 23.501 [2], The H-PCF requests V-PCF to notify the result of UE policy delivery to the UE.

[0046] 6. The H-PCF generates new or updated URSP Rules considering the Service Parameters received from the V-PCF in step 5a as specified in clause 6.1.2.2.4 of TS 23.503

[0020] , 7-8. Steps 7-8 of Figure 4.15.6.7.2-1 apply with the following differences:

[0047] - Notification is sent from V-PCF to the AF belonging to the VPLMN or third party with agreement with VPLMN.

[0048] There currently exist certain challenge(s).

[0049] As described in the “AF guidance on URSP rule” sub-section above:- A Route Selection Description may include the Protocol Data Unit (PDU) Session Type. However, this parameter cannot be validated against UE or Group of UE subscription information in UDM, on one hand, because the parameter is not defined (see the “Service specific parameter provisioning by the AF to the HPLMN” sub-section above, Table 6.8.6.2.4-1 in 3GPP TS 29.503 v19.1.0) and on the other hand, because the ServiceSpecificAuthorization Application Programming Interface (API) does not provide authorization on the parameters included in the Route Selection Description (see above).

[0050] The service specific parameter provisioning procedure used by the AF to influence VPLMN Specific URSP rules, via request to the HPLMN, as described in the “Service specific parameter provisioning by the AF to the HPLMN” sub-section above, or via request to the VPLMN, as described in the “Service specific parameter provisioning by the AF to the VPLMN” sub-section above, should not progress if the target UE (a UE or the UEs within the Group Id in the AF request to the HPLMN case, or the inbound roamers, in the case of AF request to the VPLMN case) are not allowed to perform Local BreakOut (LBO) for the Data Network Name (DNN) and Slice-Network Slice Selection Assistance Information (S-NSSAI) included in the Route Selector Description(s). However, this early check is not specified.

[0051] The checking of whether LBO is allowed for the target UE:

[0052] o if the AF is interacting with the HPLMN, cannot be done using the ServiceSpecificAuthorization API, because the validation needs to be done based on Route Selection Description, DNN and S-NSSAI combination, and LBO information is not available.

[0053] o if the AF is interacting with the VPLMN, cannot be done using the ServiceSpecificAuthorization API, because the NEF in the VPLMN cannot interact with the UDM in the HPLMN.

[0054] In addition, as described in the “Service specific parameter provisioning by the AF to the HPLMN” and “AF guidance on URSP rule” sub-sections above, the validation of the AF requested parameters with the UDM is based on the validation of the DNN and S-NSSAI of the service parameter request service operation, but according to 3GPP TS 29.503 v19.1.0, it is not based on the validation of the DNN and S-NSSAI information included in the Route Selection Descriptor. However, as indicated in Note 2 of the “AF guidance on URSP rule” sub-section above, the AF provided Route Selection Descriptors may contain different combinations of DNN and S-NSSAI and it might be that some of these combinations are not allowed by subscription.Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. A solution proposes to extend the Nnef_ServiceParameter_Notify and / or Npcf_EventExposure_Notify service operations to add to the URSP rule delivery outcome a new indication of unauthorized LIRSP rule.

[0055] In particular, when the validation of the LIRSP guidance information fails because it is not according to the subscription information stored in the Policy Data, the Policy Control Function (PCF) can report the list of unauthorized LIRSP rules within LIRSP delivery outcome information, using the Npcf_EventExposure_Notification service operation. The NEF can forward the received information to the AF using the Nnef_ServiceParameter_Notification service operation.

[0056] Certain embodiments may provide one or more of the following technical advantage(s). The network can provide an awareness to the AF about whether the AF provided LIRSP guidance is according to the UE or Group of UEs subscription information stored in Policy Data, and therefore about the actual derived LIRSP rules that can be provisioned to the UE.

[0057] According to a first aspect, there is provided a method of operating a policy control node that is part of a core network of a first communication network. The method comprises: validating one or more rules for the UE relating to route selection to determine if one or more rules are authorised; and, if one or more rules are determined to be unauthorised, sending, to a second node, an indication that one or more rules or policies for a User Equipment, UE, relating to route selection are not authorised.

[0058] According to a second aspect, there is provided a receiving, from a policy control node that is part of a core network of a first communication network, an indication that one or more rules or policies for a User Equipment, UE, relating to route selection are not authorised.

[0059] According to a third aspect, there is provided a computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method according to the first aspect, the second aspect, or any embodiments thereof.

[0060] According to a fourth aspect, there is provided a node, configured to perform the method according to the first aspect, the second aspect, or any embodiments thereof.

[0061] According to a fifth aspect, there is provided a node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said node is operative to perform the method according to the first aspect, the second aspect, or any embodiments thereof.Brief Description of the Drawings

[0062] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which:

[0063] Fig. 1 corresponds to Figure 4.15.6.7a-1 from 3GPP TS 23.502 v19.0.0: Service Specific Authorization for an individual UE or group of UEs;

[0064] Fig. 2 corresponds to Figure 4.15.6.7a-2 from 3GPP TS 23.502 v19.0.0: Service Specific Authorization Update procedure;

[0065] Fig. 3 corresponds to Figure 4.15.6.7.3-1 from 3GPP TS 23.502 v19.0.0: Service specific information provisioning by AF to VPLMN;

[0066] Fig. 4 is a diagram illustrating signalling between various nodes in a core network according to embodiments of the disclosure;

[0067] Fig. 5 is another diagram illustrating signalling between various nodes in a core network according to embodiments of the disclosure;

[0068] Fig. 6 is a flow chart illustrating a method performed by a policy control node in accordance with some embodiments;

[0069] Fig. 7 is a flow chart illustrating a method performed by a second node in accordance with some embodiments;

[0070] Fig. 8 shows an example of a communication system in accordance with some embodiments;

[0071] Fig. 9 shows another example of a communication system in accordance with some embodiments;

[0072] Fig. 10 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;

[0073] Fig. 11 shows a core network node in accordance with further embodiments;

[0074] Fig. 12 corresponds to Figure 4.15.6.7.2-1 from 3GPP TS 23.502 v19.2.0; and

[0075] Fig. 13 is an amended Table 6.1.3.18-1 of 3GPP TS 23.503 19.2.0.

[0076] Detailed

[0077]

[0078] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Additional information may also be found in the document(s) provided in Appendices 1 and 2.

[0079] As noted above, there are several issues with the procedures currently defined in the 3GPP standards. These issues include that a Route Selection Description may include the PDU SessionType, but this parameter cannot be validated against UE or Group of UE subscription information in UDM, on one hand, because the parameter is not defined, and on the other hand, because the ServiceSpecificAuthorization Application Programming Interface (API) does not provide authorization on the parameters included in the Route Selection Description (see above).

[0080] Another issue is that the service specific parameter provisioning procedure used by the AF to influence VPLMN Specific LIRSP rules, via request to the HPLMN, as described in the “Service specific parameter provisioning by the AF to the HPLMN” sub-section above, or via request to the VPLMN, as described in the “Service specific parameter provisioning by the AF to the VPLMN” sub-section above, should not progress if the target UE (a UE or the UEs within the Group Id in the AF request to the HPLMN case, or the inbound roamers, in the case of AF request to the VPLMN case) are not allowed to perform LBO for the DNN and S-NSSAI included in the Route Selector Description(s). However, this early check is not specified.

[0081] Another issue is that the checking of whether LBO is allowed for the target UE - where the AF is interacting with the HPLMN - cannot be done using the ServiceSpecificAuthorization API, because the validation needs to be done based on Route Selection Description, DNN and S-NSSAI combination, and LBO information is not available.

[0082] Another issue is that the checking of whether LBO is allowed for the target UE - where the AF is interacting with the VPLMN - cannot be done using the ServiceSpecificAuthorization API, because the NEF in the VPLMN cannot interact with the UDM in the HPLMN.

[0083] A further issue is that, as described in the “Service specific parameter provisioning by the AF to the HPLMN” and “AF guidance on URSP rule” sub-sections above, the validation of the AF requested parameters with the UDM is based on the validation of the DNN and S-NSSAI of the service parameter request service operation, but according to 3GPP TS 29.503 v19.1.0, it is not based on the validation of the DNN and S-NSSAI information included in the Route Selection Descriptor. However, as indicated in Note 2 of the “AF guidance on URSP rule” sub-section above, the AF provided Route Selection Descriptors may contain different combinations of DNN and S-NSSAI and it might be that some of these combinations are not allowed by subscription.

[0084] The solution(s) described herein aim to address one or more of the above issues and problems. One solution proposes to extend the Nnef_ServiceParameter_Notify and / or Npcf_EventExposure_Notify service operations to add a new indication of unauthorized URSP rule to the URSP rule delivery outcome.

[0085] In particular, when the validation of the URSP guidance information fails because it is not according to the subscription information stored in the Policy Data, the Policy Control Function (PCF) can report the list of unauthorized URSP rules within URSP delivery outcome information, using the Npcf_EventExposure_Notification service operation. The NEF can forward the receivedinformation to the AF using the Nnef_ServiceParameter_Notification service operation.

[0086] The solution(s) set out above can enable the network to provide an awareness to the AF about whether the AF provided URSP guidance is according to the UE or Group of UEs subscription information stored in Policy Data, and therefore about the actual derived LIRSP rules that can be provisioned to the UE.

[0087] The following description sets out potential implementations of the described solutions into the 3GPP standards. In particular, potential implementations are described with respect to Section 5.5.8.1 of 3GPP TS 29.513 v19.1.0, and Section 5.5.8.2 of 3GPP TS 29.513 v19.1.0.

[0088] Implementation in Section 5.5.8.1 of 3GPP TS 29.513 v19.1.0: AF-based service parameter provisioning to HPLMN

[0089] Figure 5.5.8.1-1 of 3GPP TS 29.513 v19.1.0 shows the procedure for service specific parameter provisioning by the AF to HPLMN. The AF uses Nnef_ServiceParameter service to provide the service specific parameters to the HPLMN and the UE. In the roaming case, the PCF is replaced by Home-PCF (H-PCF), and the Access and Mobility Management Function (AMF) interacts with the Visited-PCF (V-PCF) which interacts with H-PCF.

[0090] Fig. 4 shows signalling and steps performed by an AMF, a PCF, User Data Repository (UDR), NEF and AF according to a particular implementation of the described solution(s).

[0091] Fig. 4 is a modified version of Figure 5.5.8.1-1 of 3GPP TS 29.513 v19.1.0. The signals and steps that have been added to Figure 5.5.8.1-1 of 3GPP TS 29.513 v19.1.0 to form Fig. 4 are indicated by the presence of “new” in the numbering / labelling of those signals and steps. For completeness, the signals and steps that have been added to form Fig. 4 are: step “6new” and signals “6new1”, “6new2”, “6new3” and “6new4” in block 6A, and step “6new” and signals “6new1”, “6new2”, “6new3” and “6new4” in block 6B.

[0092] The description of the steps and signalling in Fig. 4 is set out below. The description is based on the description of Figure 5.5.8.1-1 of 3GPP TS 29.513 v19.1.0, and the bold parts describe the new steps and signalling in Fig. 4.

[0093] 1. To provide service specific parameters (e.g., for URSP influence, for V2X [Vehicle-to- Everything], for A2X [Aircraft-to-Everything], for 5G ProSe [Proximity-based Services], for Ranging / SL (i.e. , Ranging and Sidelink)) to a UE or a group of UEs, the AF invokes the Nnef_ServiceParameter_Create service operation to the NEF by sending an HTTP [HyperText Transfer Protocol] POST request to the "Service Parameter Subscriptions" resource.To update existing service specific parameters, the AF invokes the Nnef_ServiceParameter_Update service operation by sending an HTTP PUT or PATCH request to the concerned "Individual Service Parameter Subscription" resource.

[0094] To remove existing service specific parameters, the AF invokes the Nnef_ServiceParameter_Delete service operation by sending an HTTP DELETE request to the concerned "Individual Service Parameter Subscription" resource.

[0095] The request may include AF subscription information to the report of the outcome of UE Policy procedure.

[0096] NOTE 1: For further details on the Nnef_ServiceParameter_Create / Update / Delete service operations, refer to 3GPP TS 29.522

[0024] .

[0097] 2. Upon reception of the AF request, the NEF authorizes it and then performs the mapping of the information provided by the AF into associated information needed by the 5GC (e.g. GPSI to SUPI), as described in 3GPP TS 23.502 [3], The NEF may also support service specific authorization as described in clause 4.4.20 of 3GPP TS 29.522

[0024] ,

[0098] 3-4. When receiving the Nnef_ServiceParameter_Create request, the NEF invokes the Nudr_DataRepository_Create service operation to store the received service parameters in the UDR by sending an HTTP PUT request to the "Individual Service Parameter Data" resource, and the UDR replies with a "201 Created" response (if the processing of the request is successful).

[0099] When receiving the Nnef_ServiceParameter_Update request, the NEF invokes the Nudr_DataRepository_Update service operation to request the modification of the service parameters in the UDR by sending an HTTP PUT / PATCH request to the concerned "Individual Service Parameter Data" resource, and the UDR replies with a "200 OK" or "204 No Content" response (if the processing of the request is successful).

[0100] When receiving the Nnef_ServiceParameter_Delete request, the NEF invokes the Nudr_DataRepository_Delete service operation to request the deletion of the service parameters from the UDR by sending an HTTP DELETE request to the concerned "Individual Service Parameter Data" resource, and the UDR replies with a "204 No Content" response (if the processing of the request is successful).

[0101] 5. The NEF sends back an HTTP response message to the AF correspondingly.

[0102] 6A. If the PCF(s) have previously subscribed to the changes of service parameters during the UE Policy Association Establishment procedure (see clause 5.6.1), then:

[0103] 6a. The UDR invokes the Nudr_DataRepository_Notify service operation to the PCF(s) that have subscribed to the changes of service parameters by sending an HTTP POST request to the associated callback URI(s) [Uniform Resource Identifier] "{notificationUri}";6b. The PCF(s) send back "204 No Content" response(s) to the UDR;

[0104] 6new. The PCF validates the notified data (e.g. against Route Selection Parameters information stored in Policy Data); and

[0105] 6new1. If the AF subscribed to notifications about the outcome of UE Policies delivery due to Service specific parameter provisioning and the PCF determined that the corresponding UE policies are not authorized, the PCF invokes the Npcf_EventExposure_Notify service operation to inform the NEF about the unauthorized URSP rules.

[0106] 6new2. The NEF sends back "204 No Content" response to the PCF.

[0107] 6new3. When the NEF receives Npcf_EventExposure_Notify, the NEF performs information mapping as described in 3GPP TS 29.522

[0024] and triggers the appropriate Nnef_ServiceParameter_Notify message.

[0108] 6new4. The AF sends back an HTTP response message to the NEF to acknowledge the notification;_and

[0109] 6c. The PCF(s) may derive UE policies (e.g., URSP, V2X policies, A2X policies, 5G ProSe policies, Ranging / SL policies) based on the received service parameters from the UDR, UE subscription data, local operator policies, the previously received requested V2X / 5G ProSe / A2X / Ranging / SL policies and UE capabilities (e.g., V2X capabilities) from the AMF, and initiate a UE Policy Association Modification procedure if applicable (see clause 5.6.2.2) to deliver the UE policies to the UE.

[0110] B.

[0111] 6B1 During UE Policy Association Establishment procedure (see clause 5.6.1), the PCF(s) retrieve the service parameters in the UDR by invoking the Nudr_DataRepository_Query service operation, and

[0112] 6new. The PCF validates the received service parameter data (e.g. against Route Selection Parameters information stored in Policy Data); and

[0113] 6new1. If the AF subscribed to notifications about the outcome of UE Policies delivery due to Service specific parameter provisioning and the PCF determined that the corresponding UE policies are not authorized, the PCF invokes the Npcf_EventExposure_Notify service operation to inform the NEF about the unauthorized URSP rules.

[0114] 6new2. The NEF sends back "204 No Content" response to the PCF.

[0115] 6new3. When the NEF receives Npcf_EventExposure_Notify, the NEF performs information mapping as described in 3GPP TS 29.522

[0024] and triggers the appropriate Nnef_ServiceParameter_Notify message.6new4. The AF sends back an HTTP response message to the NEF to acknowledge the notification

[0116] And, for the authorized URSP rules, the PCF determine UE policies (e.g., LIRSP, V2X policies, A2X policies, 5G ProSe policies, Ranging / SL policies) based on the retrieved service parameters from the UDR, UE subscription data, local operator policies and UE capabilities (e.g. V2X capabilities, A2X capabilities and / or 5G ProSe capabilities) from the AMF and if applicable, deliver the UE policies (including the determined V2XP [V2X Policy], A2XP [A2X Policy], 5G ProSeP [ProSe Policy] and / or RSLPP [Ranging / SL Policy]) to the UE and corresponding V2X N2 PC5, A2X N2 PC5, ProSe N2 PC5 and / or Ranging / SL N2 PC5 policy to the NG-RAN.

[0117] 6B2. After registration, when the UE requests V2XP, A2XP, 5G ProSeP and / or RSLPP, the AMF sends to the PCF an Namf_Communication_N1MessageNotify service operation with the requested V2XP, A2XP, 5G ProSeP and / or RSLPP. The PCF retrieves the service parameter in the UDR by invoking the Nudr_DataRepository_Query service operation, determines V2XP, A2XP, 5G ProSeP and / or RSLPP based on the retrieved service parameter from the UDR, the received requested V2XP, A2XP, 5G ProSeP and / or RSLPP, UE subscription data, local operator policies and the UE capabilities (e.g., V2X capabilities, A2X capabilities, ProSe capabilities, Ranging / SL capabilities) previously received from the AMF, and delivers the V2XP, A2XP and / or 5G ProSeP to the UE and the corresponding V2X N2 PC5, A2X N2 PC5, ProSe N2 PC5 and / or Ranging / SL N2 PC5 policy to the NG-RAN.

[0118] NOTE 2: For further details on the Nudr_DataRepository_Create / Update / Delete / Notify service operations, refer to 3GPP TS 29.504

[0027] and 3GPP TS 29.519

[0012] , 7. If the AF subscribed to notifications about the outcome of UE Policies delivery (provision / update / removal) due to Service specific parameter provisioning and the PCF derived the corresponding UE policies, the PCF invokes the Npcf_EventExposure_Notify service operation to inform the NEF about the outcome of the procedure by sending the HTTP POST request to the callback URI "{notifUri}".

[0119] NOTE 3: The Callback URI "{notifUri}" is used for both implicit and explicit subscriptions as described in 3GPP TS 29.523

[0049] , Notification URI for implicit subscriptions is retrieved from UDR as described in 3GPP TS 29.519

[0012] ,

[0120] 8. The NEF sends back "204 No Content" response to the PCF.

[0121] 9. When the NEF receives Npcf_EventExposure_Notify, the NEF performs information mapping as described in 3GPP TS 29.522

[0024] and triggers the appropriate Nnef_ServiceParameter_Notify message.10. The AF sends back an HTTP response message to the NEF to acknowledge the notification.

[0122] Implementation in Section 5.5.8.2 of 3GPP TS 29.513 v19.1.0: AF-based service parameter provisioning to VPLMN

[0123] Figure 5.5.8.2-1 of 3GPP TS 29.513 v19.1.0 shows the procedure for service specific parameter provisioning by the AF to VPLMN.

[0124] Fig. 4 shows signalling and steps performed by a UE, (Radio) Access Network ((R)AN), an AMF, a V-PCF, a Visited-UDR (V-UDR), Visited-NEF (V-NEF), AF and a H-PCF according to a particular implementation of the described solution(s).

[0125] Fig. 5 is a modified version of Figure 5.5.8.2-1 of 3GPP TS 29.513 v19.1.0. The signals and steps that have been added to Figure 5.5.8.2-1 of 3GPP TS 29.513 v19.1.0 to form Fig. 5 are indicated by the presence of “new” in the numbering / labelling of those signals and steps. For completeness, the signals and steps that have been added to form Fig. 5 are: step “4new” and signals “4new1”, “4new2”, “4new3” and “4new4” in block 4A, and step “4new” and signals “4new1”, “4new2”, “4new3” and “4new4” in block 4B.

[0126] The description of the steps and signalling in Fig. 5 is set out below. The description is based on the description of Figure 5.5.8.1-1 of 3GPP TS 29.513 v19.1.0, and the underlined parts describe the new steps and signalling in Fig. 5.

[0127] 1. To provide service specific parameters (e.g. for AF influence on VPLMN-specific LIRSP rule) for any inbound roamer of the indicated PLMN IDs, the AF invokes the Nnef_ServiceParameter_Create / Update / Delete service operation to the V-NEF by sending an HTTP POST request to the "Service Parameter Subscriptions" resource.

[0128] The request may include AF subscription information to the report of the outcome of UE Policy procedure.

[0129] NOTE 1: For further details on the Nnef_ServiceParameter_Create / Update / Delete service operations, refer to 3GPP TS 29.522

[0024] ,

[0130] 2. Upon reception of the AF request, the V-NEF authorizes it and then performs the mapping of the information provided by the AF into associated information needed by the 5GC, as described in 3GPP TS 23.502 [3],

[0131] When receiving the Nnef_ServiceParameter_Create request, the V-NEF invokes the Nudr_DataRepository_Create service operation to store the received service parameters in the V-UDR by sending an HTTP PUT request to the "Individual Service Parameter Data"resource, and the V-UDR replies with a "201 Created" response (if the processing of the request is successful).

[0132] When receiving the Nnef_ServiceParameter_Update request, the V-NEF invokes the Nudr_DataRepository_Update service operation to request the modification of the service parameters in the V-LIDR by sending an HTTP PUT / PATCH request to the concerned "Individual Service Parameter Data" resource, and the UDR replies with a "200 OK" or "204 No Content" response (if the processing of the request is successful).

[0133] When receiving the Nnef_ServiceParameter_Delete request, the V-NEF invokes the Nudr_DataRepository_Delete service operation to request the deletion of the service parameters from the V-LIDR by sending an HTTP DELETE request to the concerned "Individual Service Parameter Data" resource, and the V-LIDR replies with a "204 No Content" response (if the processing of the request is successful).

[0134] . The V-NEF sends back an HTTP response message to the AF correspondingly.

[0135] A. If the V-PCF(s) have previously subscribed to the changes of service parameters during the UE Policy Association Establishment procedure (see clause 5.6.1), then:

[0136] 4a1. The V-LIDR invokes the Nudr_DataRepository_Notify service operation to the V- PCF(s) that have subscribed to the changes of service parameters by sending an HTTP POST request to the associated callback URI(s) "{notificationUri}";

[0137] The PCF(s) send back "204 No Content" response(s) to the UDR; and

[0138] 4new. The PCF validates the AF guidance data received from UDR (e.g. against the UE subscription data received from the AMF); and

[0139] 4new1. If the AF subscribed to notifications about the outcome of UE Policies delivery due to Service specific parameter provisioning and the PCF determined that the corresponding UE policies are not authorized, the PCF invokes the Npcf_EventExposure_Notify service operation to inform the NEF about the unauthorized URSP rules.

[0140] 4new2. The NEF sends back "204 No Content" response to the PCF.

[0141] 4new3. When the NEF receives Npcf_EventExposure_Notify, the NEF performs information mapping as described in 3GPP TS 29.522

[0024] and triggers the appropriate Nnef_ServiceParameter_Notify message.

[0142] 4new4. The AF sends back an HTTP response message to the NEF to acknowledge the notification; and

[0143] 4a2. For each retrieved Service Parameter resource, the V-PCF forwards to the H-PCF(s) the authorized AF guidance on VPLMN-specific URSP rule information received from the V-UDR for the SUPI(s) that belong to one of the indicated target PLMN ld(s) ofinbound roamers by sending an HTTP POST request to the "Individual UE Policy Association" resource(s). The V-PCF determines the SLIPI(s) that belong to one of the target PLMN ld(s) of inbound roamers by the longest matching criteria for the MCC [Mobile Country Code] and / or MNC [Mobile Network Code] of the SlIPI and the PLMN Id. The V-PCF includes the mapped HPLMN S-NSSAI values in the request and, if obtained from the V-LIDR, the AF subscription to VPLMN-specific LIRSP rule delivery outcome.

[0144] 4a3. The H-PCF makes the policy decision including the applicable updated Policy Control Request Trigger(s) and / or updated UE Policy and indicates the delivery of UE Policies to the UE as defined in clause 5.6.2.1.3, from step 3 to step 9. If the H-PCF cannot authorize the request UE policy delivery will be skipped and step 6 to step 9 will take place.

[0145] B.

[0146] 4b1. The V-PCF receives the Npcf_UEPolicyControl_Create service operation as specified in clause 5.6.1.3, step 1.

[0147] 4b2. If the VPLMNSpecificURSP feature as specified in 3GPP TS 29.504

[0027] is supported with the V-UDR, the V-PCF retrieves service parameters with URSP guidance invoking the Nudr_DataRepository_Query service operation and subscribes to changes in service parameters invoking the Nudr_DataRepository_Subscribe service operation.

[0148] 4new. The PCF validates the AF guidance data received from UDR (e.g. against the UE subscription data received from the AMF); and

[0149] 4new1. If the AF subscribed to notifications about the outcome of UE Policies delivery due to Service specific parameter provisioning and the PCF determined that the corresponding UE policies are not authorized, the PCF invokes the Npcf_EventExposure_Notify service operation to inform the NEF about the unauthorized URSP rules.

[0150] 4new2. The NEF sends back "204 No Content" response to the PCF.

[0151] 4new3. When the NEF receives Npcf_EventExposure_Notify, the NEF performs information mapping as described in 3GPP TS 29.522

[0024] and triggers the appropriate Nnef_ServiceParameter_Notify message.

[0152] 4new4. The AF sends back an HTTP response message to the NEF to acknowledge the notification; and

[0153] 4b3. For each service parameter resource retrieved, if the UE belongs to one of the target PLMN I d(s) of inbound roamers, the V-PCF forwards to the H-PCF the authorized AF(s) guidance on VPLMN-specific URSP rule, includes the mapped HPLMN S-NSSAI valuesand, if available, AF(s) subscription to the VPLMN-specific URSP rule delivery outcome retrieved from the V-LIDR by invoking the Npcf_UEPolicyControl_Create service operation as specified in clause 5.6.1.3, step 1. The V-PCF determines the SLIPI(s) that belong to one of the target PLMN ld(s) of inbound roamers by the longest matching for the MCC and / or MNC of the SlIPI and the PLMN Id. If the service information is authorized by the H-PCF, the H-PCF triggers the delivery of UE Policies to the UE procedure as described in clause 5.6.1.3, steps 8-26.

[0154] 5. When the H-PCF received the response of the UE Policy delivery outcome, if the V-PCF indicated that the AF(s) subscribed to notifications about the outcome of VPLMN-specific URSP rules or if the service information was not authorized by the H-PCF, the H-PCF invokes the Npcf_UEPolicyControl_UpdateNotify service operation by sending an HTTP POST request to the callback URI "{notificationUri} / update" with the corresponding successful or unsuccessful delivery indication as specified in 3GPP TS 29.525

[0031] , clause 4.2.4.7.

[0155] 6. If the AF subscribed to notifications about the outcome of UE Policies delivery (provision / update / removal) due to Service specific parameter provisioning, the V-PCF invokes the Npcf_EventExposure_Notify service operation to inform the V-NEF about the outcome of the procedure (as indicated by the H-PCF) by sending the HTTP POST request to the callback URI "{notifUri}" as described in 3GPP TS 29.523

[0049] ,

[0156] NOTE 2: The Callback URI "{notifUri}" is used for both implicit and explicit subscriptions as described in 3GPP TS 29.523

[0049] , Notification URI for implicit subscriptions is retrieved from UDR as described in 3GPP TS 29.519

[0012] ,

[0157] 7. The V-NEF sends back "204 No Content" response to the V-PCF.

[0158] 8. When the NEF receives Npcf_EventExposure_Notify, the NEF performs information mapping as described in 3GPP TS 29.522

[0024] and triggers the appropriate Nnef_ServiceParameter_Notify message.

[0159] 9. The AF sends back an HTTP response message to the NEF to acknowledge the notification.

[0160] Fig. 6 depicts a method performed by a node in accordance with particular embodiments. The method in Fig. 6 may be performed by a node such as a core network node 808 or core network node 1100 as described later with reference to Fig. 8 and 11 respectively). In particular embodiments, the method is performed by a policy control node in a communication network, for example a Policy Control Function (PCF). The node, e.g. a PCF, can be part of a core network of a first communication network. The first communication network may be a homecommunication network for a UE (e.g. a Home Public Land Mobile Network (HPLMN)), or a visited communication network for the UE (e.g. a Visited Public Land Mobile Network (VPLMN)).

[0161] The method begins at step 601, which is optional. In step 601, the policy control node validate one or more rules for the UE relating to route selection to determine if one or more rules are authorised.

[0162] If one or more rules are determined to be unauthorised in step 601, then in step 602 an indication is sent to a second node. The second node can be an Application Function (AF), which may be in the first communication network or outside the first communication network.

[0163] The indication indicates that one or more rules for a UE relating to route selection are not authorised. The indication may be sent in a first request message, which may be an event exposure notification request message, such as an Npcf_EventExposure_Notify Request message. An example of the indication or first request message containing the indication is shown as signal 6new1 in 6A and / or 6B of Fig. 4. Another example of the indication or first request message containing the indication is shown as signal 4new1 in 4A and / or 4B of Fig. 4.

[0164] The indication, or a message in which the indication is sent, can also include an indication of a reason or cause for the one or more rules not being authorised.

[0165] The rule(s) may relate to route selection related to routing of data or a session in the communication network (e.g. a Protocol Data Unit (PDU) Session). The rule(s) may be a UE Route Selection Policy (URSP), or a URSP rule.

[0166] Some exemplary reasons for a rule(s) for the UE relating to route selection not being authorised include:

[0167] if a Data Network Name (DNN) is not authorised;

[0168] if one or more service parameters provided by an AF are not authorised;

[0169] if one or more service parameters provided by an AF are not authorised for a Subscription Permanent Identifier (SUPI) of the UE; or

[0170] application guidance on URSP determination does not apply for a SUPI of the UE. The indication sent in step 602 may be sent to the second node via a third node.

[0171] The method may further comprise the node receiving a response to the indication from the second node. In some embodiments this response can be received from the second node via a third node.

[0172] In the embodiments referencing the third node, the second node may have subscribed to the third node for notifications relating to validity or authorisation of rules for the UE. The third node may be a node for exposing functions or interfaces of the first communication network to one or more internal and / or external nodes or functions, such as a Network Exposure Function (NEF).Validating the one or more rules for the UE in step 601 can be performed in a number of different ways. For example, the one or more rules can be validated by validating received notified data for the UE or received service parameter data for the UE. In another example, the one or more rules can be validated by validating received notified data for the UE or received service parameter data for the UE against Route Selection Parameters information stored in Policy Data. In another example, the one or more rules can be validated by validating received guidance data or Application Function (AF) guidance data. In yet another example, the one or more rules can be validated by validating received guidance data against UE subscription data. In yet another example, the one or more rules can be validated by validating guidance data received from a User Data Repository (UDR) against UE subscription data received from an Access and Mobility Management Function (AMF).

[0173] Fig. 7 depicts a method performed by another node (a “second node”) in accordance with particular embodiments. The method in Fig. 7 may be performed by a node such as a core network node 808 or core network node 1100 as described later with reference to Fig. 8 and 11 respectively). In particular embodiments, the second node is an AF. The AF may be part of or in a first communication network, or be outside the first communication network.

[0174] The method begins at step 702 in which an indication is received from a policy control node, for example a Policy Control Function (PCF). The policy control node can be part of a core network of a first communication network. The first communication network may be a home communication network for a UE (e.g. a HPLMN), or a visited communication network for the UE (e.g. a VPLMN). The indication may be received from the policy control node in step 702 if one or more rules are determined to be unauthorised (e.g. by the policy control node).

[0175] The indication indicates that one or more rules for a UE relating to route selection are not authorised. The indication may be received in a second request message, which may be a service parameter notify request message, such as an Nnef_ServiceParameter_Notify Request message. The indication, or a message in which the indication is sent, can also include an indication of a reason or cause for the one or more rules not being authorised. An example of the indication or second request message containing the indication is shown as signal 6new3 in 6A and / or 6B of Fig. 4. Another example of the indication or first request message containing the indication is shown as signal 4new3 in 4A and / or 4B of Fig. 4.

[0176] The rule(s) may relate to route selection related to routing of data or a session in the communication network (e.g. a PDU Session). The rule(s) may be a UE URSP, or a URSP rule.

[0177] Some exemplary reasons for a rule(s) for the UE relating to route selection not being authorised include:

[0178] if a DNN is not authorised;if one or more service parameters provided by an AF are not authorised; if one or more service parameters provided by an AF are not authorised for a Subscription Permanent Identifier (SlIPI) of the UE; or

[0179] application guidance on LIRSP determination does not apply for a SLIPI of the UE. The indication received in step 702 may be received from the policy control node via a third node.

[0180] The method may further comprise the second node sending a response to the indication to the policy control node. In some embodiments this response can be sent to the policy control node via a third node.

[0181] In the embodiments referencing the third node, the second node may have subscribed to the third node for notifications relating to validity or authorisation of rules for the UE. The third node may be a node for exposing functions or interfaces of the first communication network to one or more internal and / or external nodes or functions, such as a Network Exposure Function (NEF).

[0182] Fig. 8 shows an example of a communication system 800 in accordance with some embodiments. In the example, the communication system 800 includes a telecommunication network 802 that includes an access network 804, such as a radio access network (RAN), and a core network 806, which includes one or more core network nodes 808. The access network 804 includes one or more access network nodes or base stations of various types, such as access network nodes 810a and 810b (one or more of which are also referred to as RAN network nodes or RAN nodes 810 herein), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (AP). Some embodiments of the access network 804 may include more than one access network technology. The network nodes 810 of access network 804 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 812A, 812B, 812C, and 812D (one or more of which may be generally referred to as UEs 812) to the core network 806 over one or more wireless connections.

[0183] Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 802 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities ofany node in the telecommunication network 802, including one or more access network nodes 810 and / or core network nodes 808.

[0184] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-Cll user plane (O-CU-UP), a RAN intelligent controller (RIC) (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration (SMO) Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0185] The network nodes 810 facilitate direct or indirect connection of wireless devices / UEs 812, such as by connecting UEs 812a, 812b, 812c, and 812d (one or more of which may be generally referred to as UEs 812) to the core network 806 over one or more wireless connections. The access network nodes 810 may be, for example, access points (APs) (e.g. radio access points), base stations (BSs) (e.g. radio base stations, Node Bs, evolved Node Bs (eNBs) and New Radio (NR) NodeBs (gNBs)).

[0186] Unless otherwise indicated, the general term ‘network node’ as used herein refers to access network nodes 810 and core network nodes 808.

[0187] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 800 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 800 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0188] The wireless devices / UEs 812 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly withthe network nodes 810 and other communication devices. Similarly, the access network nodes 810 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 812 and / or with other network nodes or equipment in the telecommunication network 802 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 802. More specifically, UEs 812 may send messages, data, and / or other signals to network nodes 808, 810 or other elements of the telecommunications network 802 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 808, 810 may send messages, data, and other signals to UEs 8122, other network nodes 808, 810, and other devices in telecommunications network 802 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 812 by transmitting the message to an access network node 810 that will then transmit the message to the intended UE 812. Similarly, a core network node 108 may receive a particular message from a UE 812 by receiving the message from an access network node 810 that itself received the message from the UE 812.

[0189] In the depicted example, the core network 806 connects elements of the access network 804 (e.g. one or more of the access network nodes 810) to one or more host computing systems, such as host 816. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 806 includes one more core network nodes (e.g. core network node 808) of various types that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the wireless devices / UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 808. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Deconcealing function (SIDF), Unified Data Management (UDM), User Data Repository (UDR), Policy Control Function (PCF), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0190] The host 816 may be under the ownership or control of a service provider other than an operator or provider of the access network 804 and / or the telecommunication network 802. The host 816 may be operated by the service provider or on behalf of the service provider. The host816 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0191] As a whole, the communication system 800 of Fig. 8 enables connectivity between the wireless devices / UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2ndGeneration (2G), 3rdGeneration (3G), 4thGeneration (4G), 5thGeneration (5G) standards, or any applicable future generation standard (e.g. 6thGeneration (6G)); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 800 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 800 supporting different standards, protocols, or rule sets.

[0192] As one example, in certain embodiments, access network 804 may contain some access network nodes 810 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 810 support (or the same access network nodes 810 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 802 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0193] In some examples, the telecommunication network 802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 802. For example, the telecommunications network 802 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, whileproviding Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0194] In some examples, the UEs 812 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 804. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UTRA (UMTS Terrestrial Radio Access) Network) New Radio - Dual Connectivity (EN-DC).

[0195] In the example, the hub 814 communicates with the access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812c and / or 812d) and network nodes (e.g., network node 810b). In some examples, the hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 814 may be a broadband router enabling access to the core network 806 for the UEs. As another example, the hub 814 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 810, or by executable code, script, process, or other instructions in the hub 814. As another example, the hub 814 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 814 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 814 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 814 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy Internet of Things (loT) devices.

[0196] The hub 814 may have a constant / persistent or intermittent connection to the network node 810b. The hub 814 may also allow for a different communication scheme and / or schedule between the hub 814 and UEs (e.g., UE 812c and / or 812d), and between the hub 814 and the core network 806. In other examples, the hub 814 is connected to the core network 806 and / or one or more UEs via a wired connection. Moreover, the hub 814 may be configured to connect to a machine-to-machine (M2M) service provider over the access network 804 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection withthe network nodes 810 while still connected via the hub 814 via a wired or wireless connection. In some embodiments, the hub 814 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 810b. In other embodiments, the hub 814 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 810b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0197] It will be appreciated that for any of the UEs 812, the telecommunication network 802 can be the home network (i.e. HPLMN) forthat UE 812, or a visited network (i.e. VPLMN) for that UE 812 (i.e. the UE 812 is roaming in the visited network.

[0198] Fig. 9 is another example of a communication system 900 according to some embodiments. As used herein, the communication system 900 includes multiple access points (APs) 910 (with four exemplary APs 910A, 910B, 910C, and 910D being depicted) and multiple wireless devices, referred to in the context of communication system 900 as stations (STAs) 912 (referred to individually as STA912A, STA 912B, STA 912C, STA 912D, and STA 912E). STA 912A is served by AP 910A in a first basic service set (BSS) 920A. STA 910B and STA 910C are served by AP 910B in a second BSS, BSS 920B. STA 912D is served by AP 910C in a third BSS, BSS 920C. STA 912E is served by AP 910D in a fourth BSS, BSS 920D. Stations 912 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 912 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0199] Each of STAs 912 may connect through a radio link to one of APs 910. For example, depending on location or channel conditions experienced by a given STA 912, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0200] Each AP 910 may provide data connectivity to STAs 912 connected to a particular AP 910. As illustrated, APs 910 may be connected to a data network 930. In this way, APs 910 may also provide data connectivity between STAs 912 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio linkestablished between a given STA 912 and its serving AP 910 may be used for providing various kinds of services to STA 912, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 912 and / or on a device linked to STA 912. By way of example, Fig. 9 illustrates an application service platform 932 provided in data network 930. The application(s) executed on STA 912 and / or on one or more other devices linked to STA 912 may use the radio link for data communication with one or more other STA 912 and / or the application service platform 932, thereby enabling utilization of the corresponding service(s) at STA 912.

[0201] Fig. 10 is a block diagram illustrating a virtualization environment 1000 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1000 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In particular, any one or more of the described AMF, PCF, UDR, NEF, AF, V-PCF, V-LIDR, V-NEF and H-PCF can be implemented in a virtualization environment, such as virtualization environment 1000. A virtualization environment 1000 can implement just one type of node, or multiple types of node. In either case, a first virtualization environment 1000 that implements one or more nodes may communicate as required with a second virtualization environment 1000 that implements one or more other nodes.

[0202] In some embodiments, the virtualization environment 1000 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0203] Applications 1002 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0204] Hardware 1004 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software maybe executed by the processing circuitry to instantiate one or more virtualization layers 1006 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 1008Aand VM 1008B (which may be collectively referred to as VMs 1008), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1006 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 1008.

[0205] The VMs 1008 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 1006. Different embodiments of the instance of a virtual appliance 1002 may be implemented on one or more of VMs 1008, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0206] In the context of NFV, each of the VMs 1008 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1008, and that part of hardware 1004 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 1008 on top of the hardware 1004 and corresponds to an application 1002.

[0207] Hardware 1004 may be implemented in a standalone network node with generic or specific components. Hardware 1004 may implement some functions via virtualization. Alternatively, hardware 1004 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1010, which, among others, oversees lifecycle management of applications 1002. In some embodiments, hardware 1004 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1012 which may alternatively be used for communication between hardware nodes and radio units.

[0208] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprisecomputing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0209] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0210] Fig. 11 shows a core network node 1100 in accordance with some embodiments. As used herein, core network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other core network nodes or equipment or RAN network nodes, in a telecommunication network. The core network node 1100 may be operable as a core network node, a core network function or, more generally, a core network entity, such as the core network node 808 described above with respect to Fig. 8). Examples of core network nodes in this context include core network entities such as one or more of a MobileSwitching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (ALISF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), User Data Repository (UDR), Policy Control Function (PCF), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0211] The core network node 1100 includes processing circuitry 1102, a memory 1104, a communication interface 1106, and a power source 1108, and / or any other component, or any combination thereof. The core network node 1100 may be composed of multiple physically separate components, which may each have their own respective components. In certain scenarios in which the core network node 1100 comprises multiple separate components, one or more of the separate components may be shared among several core network nodes.

[0212] The processing circuitry 1102 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other core network node 1100 components, such as the memory 1104, core network node 1100 functionality. For example, the processing circuitry 1102 may be configured to cause the network node to perform the methods as described with reference to Figs. 6 and / or 7.

[0213] The memory 1104 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1102. The memory 1104 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1102 and utilized by the core network node 1100. The memory 1104 may be used to store any calculations made by the processing circuitry 1102 and / or any data received via the communication interface 1106. In some embodiments, the processing circuitry 1102 and memory 1104 are integrated.

[0214] The communication interface 1106 is used in wired or wireless communication of signalling and / or data between a core network node, access network node(s), and / or UE.The power source 1108 provides power to the various components of core network node 1100 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1108 may further comprise, or be coupled to, power management circuitry to supply the components of the core network node 1100 with power for performing the functionality described herein. For example, the core network node 1100 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1108. As a further example, the power source 1108 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0215] Embodiments of the core network node 1100 may include additional components beyond those shown in Fig. 11 for providing certain aspects of the core network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the core network node 1100 may include user interface equipment to allow input of information into the core network node 1100 and to allow output of information from the core network node 1100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the core network node 1100.

[0216] Although the computing devices described herein (e.g., wireless devices, UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communicationinterface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0217] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0218] The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the scope of the disclosure. Various exemplary embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.APPENDIX 1

[0219] 3GPP TSG-WG2 Meeting #166-Ad Hoc-e S2-250xxxx Electronic meeting, 2025-01-20 - 2025-01-24

[0220] CR-Form-v12.3 CHANGE REQUEST

[0221] 23.502 CR xxxx rev - Current version: 19.2.0

[0222] For HELP on using this form: comprehensive instructions can be found at http: / / www.3gpp. org / Change-Requests.

[0223] Proposed change affects: UICC apps | | ME | | Radio Access Network! I Core Network|~X~|

[0224]

[0225]

[0226] Misalignment with 23.503, clause 6.1.2.2.4 Distribution ofVPLMN specific URSP rules to the UE.

[0227] &

[0228]

[0229] 4.15.6.7.2 Service specific parameter provisioning by AF to HPLMN

[0230] Figure 4.15.6.7.2-1 shows procedure for service specific parameter provisioning. The AF uses Nnef ServiceParameter service to provide the service specific parameters to the HPLMN and the UE. In the roaming case, PCF is replaced by H-PCF, the AMF interacts with the V-PCF which interacts with H-PCF.

[0231] [[Fig. 12: Figure 4.15.6.7.2-1: Service specific information provisioning by AF to HPLMN]]

[0232] 0a. The AMF establishes UE Policy Association as specified in clause 4.16.11.

[0233] Ob. PCF requests notifications from the UDR on changes in UE policy information.

[0234] 1. To create a new request, the AF invokes an Nnef_ServiceParameter_Create service operation. The request may include subscription information to the report of the outcome of UE Policy delivery.

[0235] To update or remove an existing request, the AF invokes an Nnef_ServiceParameter_Update or Nnef_ServiceParameter_Delete service operation together with the corresponding Transaction Reference ID which was provided to the AF in Nnef_ServiceParameter_Create response message.

[0236] The content of this service operation (AF request) includes the information described in clause 5.2.6.11. 2. The AF sends its request to the NEF. The NEF authorizes the AF request. The NEF performs the following mappings:

[0237] - Map the AF-Service-Identifier into DNN and S-NSSAI combination, determined by local configuration. - Map the External Application Identifier into the corresponding Application Identifier known in the core network.

[0238] 2a. The NEF may invoke Nudm_SDM_Get service operation to perform the following mappings:

[0239] - Map the GPSI in Target UE Identifier into SUPI, according to information received from UDM.- Map the External Group Identifier in T arget UE Identifier into Internal Group Identifier, according to information received from UDM.

[0240] If the AF subscribed to the outcome of UE Policy delivery, the AF indicates where the AF receives the corresponding notifications.

[0241] (in the case of Nnef_ServiceParameter_Create): The NEF assigns a Transaction Reference ID to the Nnef_ServiceParameter_Create request.

[0242] 2b. (in the case of Nnef_ServiceParameter_Create or Update): The NEF may need to authorize the service specific parameter provisioning request with the UDM by sending a Nudm_ServiceSpecificAuthorisation_Create service operation as defined in clause 4.15.6.7a.

[0243] NOTE 2: The NEF skips the mapping of GPSI or External Group Identifier in step 2a if it needs to authorize the service specific parameter provisioning request with the UDM as the response of the authorization request from UDM includes the SUPI or Internal Group Identifier.

[0244] (in the case of Nnef_ServiceParameter_delete): The NEF requests the UDM to remove the authorization of the service specific parameters provisioned by sending a Nudm_ServiceSpecificAuthorisation_Remove service operation.

[0245] 3. (in the case of Nnef_ServiceParameter_Create or Update): The NEF stores the AF request information in the UDR as the "Application Data" (Data Subset setting to "Service specific information") together with the assigned Transaction Reference ID.

[0246] (in the case of Nnef_ServiceParameter_delete): The NEF deletes the AF request information from the UDR.

[0247] 4. The NEF responds to the AF. In the case of Nnef_ServiceParameter_Create response message, the response message includes the assigned Transaction Reference ID.

[0248] If the UE is registered to the network and the PCF performs the subscription to notification to the data modified in the UDR by invoking Nudr DM Subscribe (AF service parameter provisioning information, SUPI, Data Set setting to "Application Data", Data Subset setting to "Service specific information") at step 0, the following steps are performed:

[0249] 5. The PCF(s) receive(s) a Nudr DM Notify notification of data change from the UDE. The PCF checks w hether application guidance on URSP determination applies for the SUPI as specified in clause 6.1.3. 1 S of TS 23.503 1201. if this check fails, step 7 and step follow , the PCF notifies the failure with an appropriate cause.

[0250] NOTE 3: PCF does not have to subscribe for each UE the application specific information, e.g. if PCF has already received the application specific information for a group of UE or for a DNN by a subscription of other UE. The same application specific information is delivered to every UE in a group or a DNN.

[0251] For PIN service, PCF generates the URSP rules with PIN ID in the Traffic Descriptor as specified in Table 6.6.2.1-2 of TS 23.503

[0020] ,

[0252] 6. The PCF initiates UE Policy delivery as specified in clause 4.2.4.3.

[0253] 7. If the AF subscribed to notifications about the outcome of UE Policies delivery due to Service specific parameter provisioning and the PCF is notified of UE Policy Container from the AMF, the PCF notifies the UE Policy delivery result contained in the UE Policy container as the outcome of the procedure to NEF by sending Npcf_EventExposure_Notify including the SUPI, the list of GPSI(s) if available, and if provided in the step 2a, the Intemal-Group-Id.

[0254] If the PCF is notified about UE Policy delivery failure from the AMF due to UE not reachable, the PCF may determine to retry step 6 of this procedure when the UE becomes reachable. In such a case, the PCF mayreport the interim status i.e. UE is temporarily unreachable as the outcome of the procedure to NEF by sending Npcf_EventExposoure_Notify .

[0255] If the PCF determines the failure of the UE Policies delivery procedure, the PCF notifies the failure with an appropriate cause such as UE is unreachable. DNN not authorized as the outcome of the procedure to NEF by sending Npcf_EventExposure_Notify .

[0256] If the PCF determines that it cannot yet deliver URSP Rules that are based on the service parameters from the AF, then the PCF may report in the interim status that URSP Rules have not yet been delivered by the PCF as the outcome of the procedure to NEF by sending Npcf_EventExposure_Notify.

[0257] The content of event reporting in this step is described in clause 6.1.3.18 of TS 23.503

[0020] ,

[0258] 8. 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, SUPI to GPSI, Intemal-Group-Id to Extemal-Group-Id, etc.) and triggers the appropriate Nnef_ServiceParameter_Notify message.

[0259] 4.15.6.7.3 Service specific parameter provisioning by AF to VPLMN

[0260] Figure 4.15.6.7.3-1 shows procedure for service specific parameter provisioning by the AF to VPLMN.

[0261] [[Fig.3: Figure 4.15.6.7.3-1: Service specific information provisioning byAF to VPLMN]]

[0262] 0a. Same as in step 0a of Figure 4.15.6.7.2-1.

[0263] Ob-Oc. The V-PCF may request to V-UDR on changes in UE policy information and H-PCF may subscribe to H-UDR.

[0264] 1-2. Steps 1-2 of Figure 4.15.6.7.2-1 apply with the following differences:

[0265] The AF and NEF belong to the VPLMN. The AF may belong to third party with agreement with VPLMN.

[0266] When the AF provides application guidance on URSP Rule determination to the VPLMN, it will target "PLMN ID(s) of inbound roamers". The NEF in the VPLMN rejects any request for a GPSI or an Extemal-Group-ID of a different PLMN.

[0267] 3-5. Steps 3-5 of Figure 4.15.6.7.2-1 apply with the following differences:

[0268] - AF, NEF and UDR belong to VPLMN. The AF may belong to third party with agreement with VPLMN. The UDR in the VPLMN notifies the V-PCF(s) that have subscribed to the reception of application guidance on URSP determination.

[0269] In step 5, the V-PCF receives updates on application guidance on URSP determination for the PLMN ID of a SUPI that has a UE Policy Association established. The PLMN ID of the SUPI is included in the target "PLMN ID(s) of inbound roamers" in step 2. In this case, the V-PCF checks whether application guidance on URSP determination applies for the SUPI as specified in clause 6.1.2.2.4 of TS 23.50.3 1201, if this check

[0270]

[0271] 5a. The V-PCF sends the Service Parameters including the mapped HPLMN S-NSSAI values to the H-PCF and subscribes to the result of the delivery of UE Policies if the delivery result was requested by the AF, using theevent reporting on "Notification on outcome of UE Policies delivery" described in clause 6.1.3.18 of TS 23.503

[0020] ,

[0272] NOTE: The AMF determines whether LBO is allowed and performs SMF selection to select the SMF in VPLMN for LBO case as described in clause 6.3.2 of TS 23.501 [2],

[0273] The H-PCF requests V-PCF to notify the result of UE policy delivery to the UE.

[0274] 6. The H-PCF generates new or updated URSP Rules considering the Service Parameters received from the V- PCF in step 5a as specified in clause 6.1.2.2.4 of TS 23.503

[0020] ,

[0275] 7-8. Steps 7-8 of Figure 4.15.6.7.2-1 apply with the following differences:

[0276] - Notification is sent from V-PCF to the AF belonging to the VPLMN or third party with agreement with VPLMN.

[0277] This clause describes the procedures to allow an AF to provide guidance for URSP determination to 5G system via NEF. The AF may belong to the operator or to an external party. The PCF may be in the Home PLMN, as it is the PCF that determines the URSP for the UE, or in the VPLMN and then the Application guidance for URSP determination is provided to the PCF in the HPLMN via the PCF of the VPLMN. The PCF in the VPLMN translates the Service Parameters values provided by the AF for inbound roamer to values applicable to the HPLMN, e.g. S-NSSAI as described in TS 23.503

[0020] ,

[0278] NOTE 1 : The operator can negotiate with external party (typically a Corporate represented by an AF) dedicated DNN(s) and / or S-NSSAI(s) for the traffic of UE(s) of this external party. UE(s) of the external party can be identified by a group identifier.

[0279] The guidance for URSP determination may be used to provide 5GC with guidance for the URSPs depending on the UE location. This is further described in TS 23.548

[0074] ,

[0280] For providing guidance for URSP determination, the procedure defined in clause 4.15.6.7 is performed with the following considerations:

[0281] 1) Service Description indicates an AF Identifier.

[0282] 2) Service Parameters.

[0283] Information on the AF guidance for URSP determination which consists of a list of URSP rules that associate an application traffic descriptor with requested features for the candidate PDU sessions the application traffic may use:

[0284] - An application traffic descriptor, whose definition corresponds to that of the URSP Traffic Descriptors (as defined for the URSP rule in TS 23.503

[0020] Table 6.6.2.1-2). When AF provides application guidance for URSP determination for PIN, the application traffic descriptor shall include PIN ID. one or more sets of Route selection parameters, each parameter may correspond to:

[0285] - (DNN, S-NSSAI). This may be provided by the AF or determined by the NEF based on the AF Identifier when it is not provided by the AF and the AF provides only one instance of AF guidance for URSP determination. In the case of AF guidance for URSP determination for PIN, this shall be provided by the AF.

[0286] Requested PDU session type.a default Route selection precedence value to be used for the application traffic when Route selection precedence with a corresponding spatial validity condition is not provided.

[0287] - Route selection precedence with a corresponding spatial validity condition that indicates where the Route selection parameters apply. This may correspond to a geographical area (e.g. a civic address or shapes).

[0288] NOTE 2: The different sets of Route selection parameters indicate different sets of PDU Session information (DNN, S-NSSAI) that can be associated with applications matching the application traffic descriptor. Each set is meant to apply for a specific (set of) spatial validity condition. Each set is associated with a Route selection precedence to cope with the case where multiple spatial validity conditions overlap. - VPLMN ID(s) that indicates the PLMN(s) where the AF guidance on URSP determination and all its RSD(s), applies.

[0289] If the AF provides a geographical area as spatial validity condition, it is up to the NEF to transform this information into 3GPP identifiers (e.g. TAI(s)).

[0290] An AF sets the Requested PDU session type if the AF requests to change the PDU session type of the URSP rules.

[0291] NEF may, based on local configuration, complement missing service parameters. Additionally, based on operator's local policy, NEF may request UDM for service specific authorization for the service parameters for an individual UE (e.g. to authorize the Corporate or MTC provider represented by the AF and the requested DNN, S-NSSAI for the related UE) before storing the service parameters into the UDR. If the request is targeting a group of UEs, NEF may also request UDM for service specific authorization for the group related data (see table 4.15.6.3b-l), i.e. the DNN, S-NSSAI associated to the group. If the request is targeting any UE (all UEs), NEF authorizes the request based on local policy (e.g. based on AF Id) without requesting for any service specific authorization from UDM. NEF requests UDM for service specific authorization for the service parameters provisioned via the Nudm ServiceSpecificAuthorisation Create service operation as defined in clause 4.15.6.7a.

[0292] If a group of UEs or any Uli, possibility of the when roamiim in oilier Pl.\l\. is

[0293]

[0294] requested, each individual UE authorization is performed at a later stage by P( . the PCI max report a failure of the i ndi \ idual I ' I i authorization lo the Al- as described in clause 4 I 5.6 72 and in clause 4 I 5 6 " 3

[0295] NOTE 3: The operator needs to ensure the consistency between the group related data and the UE group members subscription data, i.e. if a group is authorized for a given DNN / S-NSSAI as defined in the group related data, it needs to be ensured that all UE members of the group are provisioned with such DNN / S-NSSAI, since no individual UE check is required to be done by NEF against UDM.

[0296] NOTE 4: AF guidance for application traffic is not related with 5G VN group.

[0297] 3) The Target UE identifier(s) that may be a specific UE, identified by a GPSI, or a group of UE(s), identified by an Extemal-Group-ID, or any UE of the PLMN of the NEF, or the PLMN ID(s) of inbound roamers that the AF request may be associated with.The information on the AF guidance for URSP determination provided by the AF may be associated to: a) UEs of the PLMN (of the NEF) when roaming in other PLMNs. In this case, the AF guidance for URSP determination targets to a specific UE, a group of UEs or any UE of the PLMN. In this case, the AF guidance for URSP determination associated to a specific UE, a group of UEs or any UE of the PLMN shall be also associated with the corresponding VPLMN(s) where the AF guidance for URSP determination shall be applied if the UE roams to that VPLMN(s). The list of VPLMN ID(s) is included in the Service Parameters.

[0298] b) An inbound roamer from one or more PLMN(s). In this case, the AF targets the AF guidance for URSP determination only with the inbound roamers of corresponding PLMN(s). The PLMN ID is included in the Service Parameters.

[0299] NOTE 5: Wildcarding of "PLMN ID of inbound roamers" will be handled by stage 3.

[0300] 4) Subscription to events.

[0301] The AF may subscribe to notifications about the outcome of the UE Policies delivery due to application guidance for URSP determination.

[0302] The usage of the AF guidance for application traffic is described in clause 6.6 of TS 23.548

[0074] ,

[0303]

[0304] APPENDIX 2

[0305] 3GPP TSG-WG2 Meeting #166-Ad Hoc-e S2-250xxxx Electronic meeting, 2025-01-20 - 2025-01-24

[0306]

[0307] For HELP on using this form: comprehensive instructions can be found at http: / / www.3gpp. org / Change-Requests.

[0308] Proposed change affects: UICC apps | | ME | | Radio Access Network! I Core Network|~X~|

[0309]

[0310] Reason for change: Clause 6.1.2.2.4 specifies that “The H-PCF generates new or updated URSP Rules using the application guidance on URSP Rule determination.... The H-PCF provides RSD values in the URSP Rules that are within the subscribed values defined in the S-NSSAI subscription information defined in Table 6.2.1.3-1”. It may happen that some of the application guidance is not in the subscribed values, i.e, when the PCF authorizes the service parameters for a target UE set to any UE or a group of UE as defined in clause 4.5.6.10 in TS 23.502: “If a group of UEs or any UE is requested, each individual UE authorization is performed at a later stage by PCF.” For the distribution of VPLMN specific URSP rules to the UE, the H-PCF provides URSP Rules that contained subscribed values, as defined in clause 6.1.2.2.4, as such the H-PCF may also indicate to the AF, via V-PCF that the application guidance is not within the subscribed values for a certain UE.

[0311] Clause 6.1.3.18 on Event reporting includes the possibility to notify a failure in the delivery of URSP Rules to the UE, some clarifications to indicate that the failure may be not only due to UE not reachable but also due to authorization failure at the PCF is proposed.

[0312] Summary of change: Clause 6.1.3.18 on Envet reporting includes the possibility to notify a failure in the delivery of URSP Rules to the UE, some clarifications to indicate that

[0313]

[0314] &

[0315]

[0316] | This CR's revision history:

[0317]

[0318] * * * * 1st change

[0319] 6.1.3.18 Event reporting from the PCF

[0320] 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.

[0321] The PCF for the UE may subscribe / unsubscribe to notifications of events from the PCF for the PDU Session. Other NFs may subscribe / unsubscribe to notifications of events from the PCF for the PDU Session or from the PCF for the UE.

[0322] The events that can be subscribed by the AF and by other NFs are listed in Table 6.1.3.18-1.

[0323] [[Fig. 13: Table 6.1.3.18-1]]

[0324] If an AF requests the PCF to report the PLMN identifier where the UE is currently located, then the PCF shall provide the PLMN identifier or the SNPN identifier to the AF if available. Otherwise, the PCF shall provision the corresponding PCC rules, and the Policy Control Request Trigger to report PLMN change to the SMF. The PCF shall, 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 V-PCF 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.

[0325] If an AF requests the PCF to report on the change of Access Type, the PCF shall 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 shall, 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 shall 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.

[0326] If an AF requests the PCF to report on the signalling path status, for the AF session, the PCF shall, upon indication of removal of PCC Rules identifying signalling traffic from the SMF report it to the AF.

[0327] If an AF requests the PCF to report Access Network Charging Correlation Information, the PCF shall provide to the AF the Access Network 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 shall 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.

[0328] 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 shall, 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 shall forward it to the AF). For AF session termination the communication between the AF and the PCF shall be kept alive until the PCF report is received.

[0329] If an AF requests the PCF to report the Usage for Sponsored Data Connectivity, the PCF shall 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.

[0330] If an AF or TSCTSF requests the PCF to report the Service Data Flow deactivation, the PCF shall report the release of resources corresponding to the AF session. The PCF shall, 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 shall also forward, if available, the reason why the resources are released, the user location information and the UE Timezone.

[0331] If an AF or TSCTSF requests the PCF to report the Resource allocation outcome, the PCF shall report the outcome of the resource allocation of the Service Data Flow(s) related to the AF session. The AF or TSCTSF may request to be notified about successful or failed resource allocation. In this case, the PCF shall 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 shall 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 notified the PCF about resource allocation failure together with an Access Type (as described in clause 6.1.3.5), the PCF shall only notify the AF when the PCC rule is removed and without forwarding any Access Type information. If the SMF has notified the PCF about resource allocation failure due to UE temporary unreachable together with a maximum waiting time, if available, (as described in clause 6.1.3.5), the PCF shall notify the AF on resource allocation failure and provide the UE temporary unreachable and the maximum waiting time, if available.

[0332] 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 shall 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 shall 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 TS 23.501 [2]), the PCF shall 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 shall 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.

[0333] 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 Policy Control Request Trigger accordingly, as described in clause 6.1.3.21. The PCF sends the QoS Monitoring reports to AF based on the QoS Monitoring reports that itreceives from the SMF, according to AF subscription and PCF selected notification path e.g. PCF does not report to AF if AF will receive the QoS Monitoring reports directly from the UPF.

[0334] NOTE 2: The QoS Monitoring report received by the PCF and the information sent to the AF can be different.

[0335] The QoS Monitoring report (e.g. packer delay) may be used by PCF to calculate the requested QoS parameter (e.g. packet delay variation).

[0336] NOTE 3: This event can only be subscribed as part of an AF session with required QoS (described in clause 6.1.3.22) and as part of AF requested QoS for a UE or group of UEs not identified by a UE address (described in clause 6.1.3.28).

[0337] NOTE 4: If the service data flow is mapped to two QoS Flows (i.e. the UL traffic and DL traffic of the service data flow are separated into two QoS Flows respectively) in the same PDU Session, the PCF triggers QoS Monitoring for each direction packet delay of the individual QoS Flows respectively and generates the QoS Monitoring reports for the AF based on the packet delay monitored on the QoS Flow for each direction (as described in clause 5.37.4 of TS 23.501 [2]).

[0338] If the AF subscribes to be notified of Packet Delay Variation reports (the variation of UL / DL packet delay between UE and PSA UPF), the PCF triggers the QoS monitoring procedure, derives the 5GS Packet Delay Variation and reports the value to the AF, as described in clause 6.1.3.26.

[0339] NOTE 5: This event can only be subscribed as part of an AF session with required QoS (described in clause 6.1.3.22).

[0340] If the AF subscribes to Round-trip delay measurement over two service data flows considering the UL direction of a service data flows and the DL direction of another service data flow, PCF triggers the QoS monitoring procedure to derive the Round-Trip delay measurement for delay measurements on the individual QoS Flows respectively (as described in clause 6.1.3.27.1 and in clause 5.37.4 of TS 23.501 [2], The PCF derives the Round-Trip delay based on the packet delay measurement reports of the QoS Flows of each direction and reports the results to the AF. PCF sets QoS Monitoring Policies for each of the individual service data flows and QoS Monitoring Policy Control Request Trigger as described in clause 6.1.3.21.

[0341] NOTE 6: This event can only be subscribed as part of an AF session with required QoS (described in clause 6.1.3.22).

[0342] If the AF indicates ECN marking for L4S support by the application, PCF authorizes the request and sets the ECN marking for L4S can no longer (or can again) be performed trigger accordingly. PCF shall further send the notification it receives from the SMF to AF on whether the network can not (or can again) perform ECN marking for L4S, for example, if due to user mobility neither target RAN nor UPF PSA support ECN marking for L4S. If an AF requests the PCF to report on the Out of credit event for the associated service data flow(s), the PCF shall 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.

[0343] If an AF requests the PCF to report on the Reallocation of credit event for the associated service data flow(s), the PCF shall 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 / Router information available to SMF based on local policy (i.e. without an AF request) or based on subscription request from TSCTSF. The PCF shall, upon reception of the 5GS Bridge / Router information (refer to clauses 6.1.3.23, 6.1.3.23a, 6.1.3.23b) 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 / Router 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 shall 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 Intemal-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.

[0344] 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, 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,

[0345]

[0346] temporarily unreachable or that URSP Rules have not yet been delivered by the H-PCF (see clauses 4.15.6.7 and 5.2.5.7 of TS 23.502 [3]). The PCF reports the outcome of the UE Policy provisioning procedure for each of the UEs that were included as Target UEs in the service specific information Data Subset in UDR. When the AF requested the PCF for the UE to report on the outcome of the UE Policies delivery due to service specific parameter provisioning procedure targeting a single UE, the Result of UE Policy Container delivery via EPS event trigger shall be subscribed.

[0347] NOTE 7 : An example reason for sending an interim status report that indicates that "URSP Rules have not yet been delivered by the H-PCF" may be that the UE does not support the VPLMN Specific URSP Rules feature and is not registered in the PLMN where the service parameters apply.

[0348] 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.

[0349] A request to forward UE reporting Connection Capabilities from an associated URSP rule triggers the reporting when the PCF receives UE reporting of URSP rule enforcement information from the SMF matching specific Connection Capabilities (see clause 6.6.2.4). The request may include SUPI(s), DNN(s) and / or S-NSSAI(s) to which the request applies. The PCF reports the received Connection Capabilities and PDU Session information including the SUPI, UE requested DNN, Selected DNN, S-NSSAI, SSC Mode, PDU Session Type. The reception of a subscription to this event triggers the setting of the corresponding Policy Control Request Trigger to SMF, if not already subscribed.

[0350] If an AF requests the PCF to report Start of application traffic detection and Stop of application traffic detection via bulk subscription, the AF shall provide the application identifier together with the S-NSSAI and DNN. The PCF provides a PCC rule for the application identifier together with the corresponding Policy Control Request Trigger to the SMF for every PDU Session to this S-NSSAI and DNN. When the PCF receives start of application traffic detection event or stop of application traffic detection event for the PCC rule in a PDU Session, the PCF forwards the event to the AF together with the UE identifier and optionally the IP address of the PDU Session corresponding to this PCC rule. When the AF removes bulk subscription for this application identifier, then the PCF removes the Policy Control Request Trigger from the SMF for every PDU Session to this S-NSSAN and DNN, if it is not used for other purpose.

[0351] NOTE 8: The restriction of the bulk subscription to a specific combination of S-NSSAI and DNN avoids excessive signalling load.

[0352] If an AF requests the PCF to report on the change between different types of satellite backhaul or the change between satellite backhaul and non-satellite backhaul (as specified in clause 5.43.4 of TS 23.501 [2]), the PCF shall 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 shall, upon reception of information about the change of Satellite backhaul category, notify the AF on the Satellite backhaul category change event was met and forward thecurrent Satellite backhaul category received from the SMF to the AF. When the satellite backhaul is no longer used, the Satellite backhaul category indicates that a non-satellite backhaul is used.

[0353] If 5G DDNMF requests the PCF to report on the Change of PDUID, the PCF shall 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 TS 23.304

[0034] ,

[0354] 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.

[0355] If the TSCTSF requests the PCF notifications for reporting of extra UE addresses, the PCF shall provide the extra UE addresses allocated to the PDU Session due to Framed Routes or IPv6 prefix delegation. The report shall include the actual list of IPv4 address masks or a list of IPv6 prefixes as currently allocated.

[0356] If the AF provides the Capability for BAT adaptation or BAT Window and subscribes to PCF for Notification on BAT offset, the PCF will trigger the subscription to SMF for Notification on BAT offset defined in clause 6.1.3.5. When the Notification on BAT offset trigger is set and the PCF receives a BAT offset and optionally an adjusted periodicity from the SMF, the PCF identifies the affected AF session (based on the PCC rule indicated by the SMF) and forwards the BAT offset and optionally the adjusted periodicity for this AF session to the TSCTSF.

[0357] A request to report Result of UE Policy Container delivery via EPS triggers the reporting when the PCF for the PDU Session receives the UE Policy Container from the UE during UE Policy Container delivery via EPS, or a delivery failure result for UE Policy Container delivery via EPS with appropriate reason from the 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.

[0358] If an AF requests the PCF to report on the UE reachability status change, the PCF shall provide the corresponding Policy Control Request Trigger to the SMF to enable the report of the UE reachability status change to the PCF, if not already subscribed. The PCF shall, upon indication of change of reachability status, notify the AF and forward the information received from the SMF to the AF.

[0359]

[0360] The following numbered statements set out various exemplary embodiments of the techniques described herein:

[0361] Group A Embodiments

[0362] 1. A method of operating a policy control node that is part of a core network of a first communication network, the method comprising:

[0363] sending, to a second node, an indication that one or more rules for a User Equipment, UE, relating to route selection are not authorised.

[0364] 2. The method of embodiment 1, wherein the one or more rules relating to route selection relate to routing of data or a session in the communication network.

[0365] 3. The method of embodiment 2, wherein the data or session in the communication network is a Protocol Data Unit, PDU, Session.

[0366] 4. The method of any of embodiments 1-3, wherein one or more rules for the UE is a UE Route Selection Policy, URSP, or a URSP rule.

[0367] 5. The method of any of embodiments 1-4, wherein the indication is sent to the second node via a third node.

[0368] 6. The method of any of embodiments 1-5, wherein the method further comprises:

[0369] receiving, from the second node, a response to the indication.

[0370] 7. The method of embodiment 6, wherein the response to the indication is received from the second node via a third node.

[0371] 8. The method of embodiment 5 or 7, wherein the second node has subscribed to the third node for notifications relating to validity or authorisation of rules for the UE.

[0372] 9. The method of any of embodiments 5, 7 or 8, wherein the third node is a node for exposing functions or interfaces of the first communication network to one or more internal and / or external nodes or functions.10. The method of any of embodiments 5 or 7-9, wherein the third node is a Network Exposure Function, NEF.

[0373] 11. The method of any of embodiments 1-10, wherein the first node is a Policy Control Function, PCF.

[0374] 12. The method of any of embodiments 1-11, wherein the indication is sent in a first request message.

[0375] 13. The method of embodiment 12, wherein the first request message is an event exposure notification request message.

[0376] 14. The method of embodiment 12 or 13, wherein the first request message is a Npcf_EventExposure_Notify Request message.

[0377] 15. The method of any of embodiments 1-14, wherein the second node is an Application Function, AF.

[0378] 16. The method of embodiment 15, wherein the AF is in the first communication network or outside the first communication network.

[0379] 17. The method of any of embodiments 1-16, wherein the method further comprises:

[0380] validating one or more rules for the UE relating to route selection to determine if one or more rules are authorised.

[0381] 18. The method of embodiment 17, wherein the indication is sent to the second node if one or more rules are determined to be unauthorised.

[0382] 19. The method of embodiment 17 or 18, wherein the step of validating the one or more rules for the UE comprises any of:

[0383] validating received notified data for the UE or received service parameter data for the UE; validating received notified data for the UE or received service parameter data for the UE against Route Selection Parameters information stored in Policy Data;

[0384] validating received guidance data or Application Function, AF, guidance data; validating received guidance data against UE subscription data; orvalidating guidance data received from a User Data Repository, UDR, against UE subscription data received from an Access and Mobility Management Function, AMF.

[0385] 20. The method of any of embodiments 1-19, wherein the indication, or a message in which the indication is sent, further comprises an indication of a reason or cause for the one or more rules not being authorised.

[0386] 21. The method of any of embodiments 1-20, wherein the one or more rules for the UE relating to route selection are not authorised if:

[0387] a Data Network Name, DNN, is not authorised;

[0388] one or more service parameters provided by an Application Function, AF, are not authorised;

[0389] one or more service parameters provided by an AF are not authorised for a Subscription Permanent Identifier, SUPI, of the UE; or

[0390] application guidance on UE Route Selection Policy, URSP, determination does not apply fora Subscription Permanent Identifier, SUPI, of the UE.

[0391] 22. The method of any of embodiments 1-21, wherein the first communication network is a home communication network for the UE.

[0392] 23. The method of any of embodiments 1-22, wherein the first communication network is a visited communication network for the UE.

[0393] 24. A method of operating a second node, the method comprising:

[0394] receiving, from a policy control node that is part of a core network of a first communication network, an indication that one or more rules or policies for a User Equipment, UE, relating to route selection are not authorised.

[0395] 25. The method of embodiment 24, wherein the one or more rules relating to route selection relate to routing of data or a session in the first communication network.

[0396] 26. The method of embodiment 25, wherein the data or session in the first communication network is a Protocol Data Unit, PDU, Session.27. The method of any of embodiments 24-26, wherein one or more rules for the UE is a UE Route Selection Policy, LIRSP, or a LIRSP rule.

[0397] 28. The method of any of embodiments 24-27, wherein the indication is received from the policy control node via a third node.

[0398] 29. The method of any of embodiments 24-28, wherein the method further comprises:

[0399] sending, to the policy control node, a response to the indication.

[0400] 30. The method of embodiment 29, wherein the response to the indication is sent to the policy control node via a third node.

[0401] 31. The method of embodiment 28 or 30, wherein the second node has subscribed to the third node for notifications relating to validity or authorisation of rules for the UE.

[0402] 32. The method of any of embodiments 28, 30 or 31, wherein the third node is a node for exposing functions or interfaces of the first communication network to one or more internal and / or external nodes or functions.

[0403] 33. The method of any of embodiments 28, 30-32, wherein the third node is a Network Exposure Function, NEF.

[0404] 34. The method of any of embodiments 24-33, wherein the indication is received in a second request message.

[0405] 35. The method of embodiment 34, wherein the second request message is a service parameter notify request message.

[0406] 36. The method of embodiment 34 or 35, wherein the second request message is a Nnef_ServiceParameter_Notify Request message.

[0407] 37. The method of any of embodiments 24-36, wherein the second node is an Application Function, AF.38. The method of embodiment 37, wherein the AF is in a first communication network or outside the first communication network.

[0408] 39. The method of embodiment 38, wherein the indication is received from the policy control node if one or more rules are determined to be unauthorised.

[0409] 40. The method of any of embodiments 24-39, wherein the indication, or a message in which the indication is received, further comprises an indication of a reason or cause for the one or more rules not being authorised.

[0410] 41. The method of any of embodiments 24-40, wherein the one or more rules for the UE relating to route selection are not authorised if:

[0411] a Data Network Name, DNN, is not authorised;

[0412] one or more service parameters provided by an Application Function, AF, are not authorised;

[0413] one or more service parameters provided by an AF are not authorised for a Subscription Permanent Identifier, SlIPI, of the UE; or

[0414] application guidance on UE Route Selection Policy, URSP, determination does not apply for a Subscription Permanent Identifier, SUPI, of the UE.

[0415] 42. The method of any of embodiments 24-41, wherein the policy control node is a Policy Control Function, PCF.

[0416] 43. The method of any of embodiments 24-41, wherein the first communication network is a home communication network for the UE.

[0417] 44. The method of any of embodiments 24-41, wherein the first communication network is a visited communication network for the UE.

[0418] Group B Embodiments

[0419] 45. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of the Group A embodiments.46. A node, configured to perform the method of any of the Group A embodiments.

[0420] 47. A node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said node is operative to perform the method of any of the Group A embodiments.

[0421] 48. A node, comprising:

[0422] processing circuitry configured to cause the node to perform any of the steps of any of the Group A embodiments;

[0423] power supply circuitry configured to supply power to the processing circuitry.

Claims

Claims1. A method of operating a policy control node that is part of a core network of a first communication network, the method comprising:validating one or more rules for the UE relating to route selection to determine if one or more rules are authorised; andif one or more rules are determined to be unauthorised, sending, to a second node, an indication that one or more rules for a User Equipment, UE, relating to route selection are not authorised.

2. The method of embodiment 1 , wherein the indication, or a message in which the indication is sent, further comprises an indication of a reason or cause for the one or more rules not being authorised.

3. The method of embodiment 2, wherein the reason or cause for the one or more rules not being authorised comprises:a Data Network Name, DNN, is not authorised;one or more service parameters provided by an Application Function, AF, are not authorised;one or more service parameters provided by an AF are not authorised for a Subscription Permanent Identifier, SUPI, of the UE; orapplication guidance on UE Route Selection Policy, URSP, determination does not apply fora Subscription Permanent Identifier, SUPI, of the UE.

4. The method of any of claims 1-3, wherein the one or more rules relating to route selection related to routing of data or a session in the communication network.

5. The method of claim 4, wherein the data or session in the communication network is a Protocol Data Unit, PDU, Session.

6. The method of any of claims 1-5, wherein one or more rules for the UE is a UE Route Selection Policy, URSP, or a URSP rule.

7. The method of any of claims 1-6, wherein the indication is sent to the second node via a third node.

8. The method of any of claims 1-7, wherein the method further comprises:receiving, from the second node, a response to the indication.

9. The method of claim 8, wherein the response to the indication is received from the second node via a third node.

10. The method of claim 7 or 9, wherein the second node has subscribed to the third node for notifications relating to validity or authorisation of rules for the UE.

11. The method of any of claims 7, 9 or 10, wherein the third node is a node for exposing functions or interfaces of the first communication network to one or more internal and / or external nodes or functions.

12. The method of any of claims 7 or 9-11, wherein the third node is a Network Exposure Function, NEF.

13. The method of any of claims 1-12, wherein the policy control node is a Policy Control Function, PCF.

14. The method of any of claims 1-13, wherein the indication is sent in a first request message.

15. The method of claim 14, wherein the first request message is an event exposure notification request message.

16. The method of claim 14 or 15, wherein the first request message is a Npcf_EventExposure_Notify Request message.

17. The method of any of claims 1-16, wherein the second node is an Application Function, AF.

18. The method of claim 17, wherein the AF is in the first communication network or outside the first communication network.

19. The method of any of claims 1-18, wherein the step of validating the one or more rules for the UE comprises any of:validating received notified data for the UE or received service parameter data for the UE; validating received notified data for the UE or received service parameter data for the UE against Route Selection Parameters information stored in Policy Data;validating received guidance data or Application Function, AF, guidance data; validating received guidance data against UE subscription data; orvalidating guidance data received from a User Data Repository, UDR, against UE subscription data received from an Access and Mobility Management Function, AMF.

20. The method of any of claims 1-19, wherein the first communication network is a home communication network for the UE.

21. The method of any of claims 1-20, wherein the first communication network is a visited communication network for the UE.

22. A method of operating a second node, the method comprising:receiving, from a policy control node that is part of a core network of a first communication network, an indication that one or more rules or policies for a User Equipment, UE, relating to route selection are not authorised.

23. The method of claim 22, wherein the indication, or a message in which the indication is received, further comprises an indication of a reason or cause for the one or more rules not being authorised.

24. The method of claim 23, wherein the reason or cause for the one or more rules not being authorised comprises:a Data Network Name, DNN, is not authorised;one or more service parameters provided by an Application Function, AF, are not authorised;one or more service parameters provided by an AF are not authorised for a Subscription Permanent Identifier, SUPI, of the UE; orapplication guidance on UE Route Selection Policy, URSP, determination does not apply for a Subscription Permanent Identifier, SUPI, of the UE.

25. The method of any of claims 22-24, wherein the one or more rules relating to route selection related to routing of data or a session in the first communication network.

26. The method of any of claim 22-25, wherein the data or session in the first communication network is a Protocol Data Unit, PDU, Session.

27. The method of any of claims 22-26, wherein one or more rules for the UE is a UE Route Selection Policy, URSP, or a URSP rule.

28. The method of any of claims 22-27, wherein the indication is received from the policy control node via a third node.

29. The method of any of claims 22-28, wherein the method further comprises:sending, to the policy control node, a response to the indication.

30. The method of claim 29, wherein the response to the indication is sent to the policy control node via a third node.

31. The method of claim 28 or 30, wherein the second node has subscribed to the third node for notifications relating to validity or authorisation of rules for the UE.

32. The method of any of claims 28, 30 or 31, wherein the third node is a node for exposing functions or interfaces of the first communication network to one or more internal and / or external nodes or functions.

33. The method of any of claims 28, 30 or 32, wherein the third node is a Network Exposure Function, NEF.

34. The method of any of claims 22-33, wherein the indication is received in a second request message.

35. The method of claim 34, wherein the second request message is a service parameter notify request message.

36. The method of claim 34 or 35, wherein the second request message is a Nnef_ServiceParameter_Notify Request message.

37. The method of any of claims 22-36, wherein the second node is an Application Function, AF.

38. The method of claim 37, wherein the AF is in a first communication network or outside the first communication network.

39. The method of claim 38, wherein the indication is received from the policy control node if one or more rules are determined to be unauthorised.

40. The method of any of claims 22-39, wherein the policy control node is a Policy Control Function, PCF.

41. The method of any of claims 22-40, wherein the first communication network is a home communication network for the UE.

42. The method of any of claims 22-41, wherein the first communication network is a visited communication network for the UE.

43. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of claims 1-42.

44. A node, configured to perform the method of any of claims 1-42.

45. A node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said node is operative to perform the method of any of claims 1-42.

Images