WO2022069931A1 - Methods providing consolidation of policies and related network nodes - Google Patents

Abstract

A method of operating a first CN node is disclosed. A session establishment request message for a communication device is received including a first PDR and a first action rule. The first PDR includes an appID for the application. A session modification request message for the communication device is received including a second PDR and a second action rule. The second PDR includes flow information for the application. That a received packet matches the second PDR is detected based on the flow information of the second PDI and the packet matching. That the received packet matches the first PDR is detected based on the appID of the first PDR and the packet matching. The packet of application traffic is processed based on the at least one first action rule and/or based on the at least one second action rule.

Description

METHODS PROVIDING CONSOLIDATION OF POLICIES AND RELATED NETWORK NODES

TECHNICAL FIELD

[0001] The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.

BACKGROUND

[0002] The 5G reference network architecture is shown in Figure 1 which illustrates the 5G reference architecture as defined by the 3rd Generation Partnership Project 3GPP.

[0003] Relevant architectural aspects for the present disclosure include: AF (Application Function); NEF (Network Exposure Function); PCF (Policy Control Function); SMF (Session Management Function); and UPF (User Plane Function).

[0004] The Application Function (AF) at a Content Provider's server side interacts with the 3GPP Core Network, CN, in the context of the present disclosure, to exchange information with the network operator, specifically to provision (external) policies relative to the content provider's application traffic.

[0005] The Network Exposure Function (NEF) supports different functionality, and in the context of the present disclosure, the NEF acts as the entry point into the operator's network, so that an external AF (Content Provider) interacts with the 3GPP Core Network through an NEF.

[0006] The Policy Control Function (PCF) supports a unified policy framework to govern the network behavior. For the present disclosure, the PCF provides PCC (Policy and Charging Control) rules to the PCEF (Policy and Charging Enforcement Function), i.e. the SMF/UPF that enforces policy and charging decisions according to provisioned PCC rules.

[0007] The Session Management function (SMF) supports different functionality, e.g., Session Establishment, modify and release, and policy related functionalities such as termination of interfaces towards Policy control functions, Charging data collection, support of charging interfaces and control and coordination of charging data collection at UPF. For the present disclosure, SMF receives PCC rules from PCF and configures UPF accordingly through N4 reference point (PFCP protocol) as discussed below.

[0008] The SMF controls the packet processing in the UPF by establishing, modifying or deleting PFCP Sessions and by provisioning (i.e., adding, modifying or deleting) Packet Detection Rules PDRs, Forwarding Action Rules FARs, Quality of Service QoS Enforcement Rules QERs and/or Usage Reporting Rules URRs per Packet Flow Control Protocol PFCP session, whereby a Packet Forwarding Control Protocol PFCP session may correspond to an individual Protocol Data Unit PDU session or a standalone PFCP session not tied to any PDU session.

[0009] Each PDR contains Packet Detection Information PDI specifying the traffic filters or signatures against which incoming packets are matched. Each PDR is associated with the following rules (relating to FARs, QERs, and URRs) providing the set of instructions to apply to packets matching the PDI.

[0010] One FAR contains instructions related to the processing of the packets, specifically forward, duplicate, drop or buffer the packet with or without notifying the Control Plane CP function about the arrival of a Downlink DL packet.

[0011] Zero, one or more QERs contain instructions related to QoS enforcement of the traffic.

[0012] Zero, one or more URRs contain instructions related to traffic measurement and reporting.

[0013] The User Plane function (UPF) supports handling of user plane traffic based on the rules received from SMF. For the present disclosure, support for such handling may include packet inspection (through PDRs) and different enforcement actions, e.g. traffic steering, Quality of Service QoS, and Charging/Reporting (through FARs, QERs, and URRs). The 3GPP Exposure framework is discussed below.

[0014] Content Providers (e.g., Google) are interested in operator networks applying a specific handling (e.g., High QoS, Sponsored data) for their applications traffic (e.g., YouTube). 3GPP has defined a framework for Exposure to support the above in a dynamic way. For example, a northbound interface may be provided between the content provider (AF) and the network operator (NEF). In the context of the present disclosure, provisioning (external) policies relative to the content provider's application traffic, for example, to request a certain QoS (e.g., High/Low QoS) and/or Charging (e.g., Sponsored Data) for a Content Provider's traffic in a certain PDU session, may be provided using: Nnef Northbound Application Program Interface API for “Setting up an AS session with required QoS”; and/or Nnef Northbound API for “Changing the chargeable party at session set up or during the session”. In the APIs discussed above, the traffic subject to a certain QoS and/or Charging handling is defined by a flow description (flowinfo), which is composed of packet filters (N-tuples).

[0015] In some situations, however, a conflict may occur between a policy /policies defined by a content provider and a policy/policies defined by a subscription associated with a communication device. With conflicting policies, an incorrect policy may be applied.

SUMMARY

[0016] According to some embodiments of inventive concepts, a method is provided to operate a first core network CN node. A session establishment request message for a communication device is received. The session establishment request message is received from a second CN node, the session establishment request message includes a first packet detection rule PDR for an application supported by an application server, the first PDR includes first packet detection information PDI including an application identifier appID for the application, and the session establishment request message includes at least one first action rule associated with the first PDR. A session modification request message for the communication device is received. The session modification request message is received from the second CN node, the session modification request message includes a second PDR for the application supported by the application server, the second PDR includes a second PDI including flow information for the application, the session modification request message includes at least one second action rule associated with the second PDR, and the appID and the flow information are different. A packet of application traffic is received. The CN node detects that the packet of application traffic matches the second PDR based on the flow information of the second PDI matching flow information of the packet of application traffic. The CN node detects that the packet of application traffic matches the first PDR based on the appID of the first PDR matching an appID of the packet of application traffic. The packet of application traffic is processed based on the at least one first action rule associated with the first PDR and/or based on the at least one second action rule associated with the second PDR. [0017] According to some embodiments of inventive concepts, a method is provided to operate a first core network CN node. A session establishment request message for a communication device is transmitted to a second CN node. The session establishment request message includes a first packet detection rule PDR for an application supported by an application server, the first PDR includes first packet detection information PDI including an application identifier appID for the application, and the session establishment request message includes at least one first action rule associated with the first PDR. A session modification request message for the communication device is transmitted to the second CN node. The session modification request message includes a second PDR for the application supported by the application server, the second PDR includes second PDI including flow information for the application, the session modification request message includes at least one second action rule associated with the second PDR, and the appID and the flow information are different.

[0018] According to some embodiments of inventive concepts, a method is provided to operate a first core network CN node. A policy control create message for a communication device is transmitted to a second core network CN node. The policy control create message includes a Policy and Charging Control PCC rule of the policy control create message, and the PCC rule of the policy control create message includes an application identifier appID for an application supported by an application server. A policy control update request message for the communication device is transmitted to the second CN node. The policy control update request message includes a PCC rule of the policy control update request message, wherein the PCC rule of the policy control update request message includes flow information for the application, and an indication to apply policy consolidation for application traffic between the communication device and the application server.

[0019] According to some embodiments, a network operator may be better able to consolidate conflicting policies defined by a content provider and a subscription associated with a communication device, so that a correct policy/policies is/are applied.

BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings: [0021] Figure 1 is a block diagram illustrating a 5G reference non-roaming architecture;

[0022] Figure 2 is a block diagram illustrating handling of Policy and Charging Control PCC rules and Policy Detection Rules PDRs;

[0023] Figures 3A to 3F provide a message diagram illustrating messages/operations according to some embodiments of inventive concepts;

[0024] Figure 4 is a block diagram illustrating a communication device UE (also referred to as a wireless device or wireless communication device) according to some embodiments of inventive concepts;

[0025] Figure 5 is a block diagram illustrating a radio access network RAN node (e.g., a base station eNB/gNB) according to some embodiments of inventive concepts;

[0026] Figure 6 is a block diagram illustrating a core network CN node (e.g., an AMF node, an SMF node, etc.) according to some embodiments of inventive concepts;

[0027] Figure 7 is a flow chart illustrating operations of a UPF node according to some embodiments of inventive concepts;

[0028] Figure 8 is a flow chart illustrating operations of an SMF node according to some embodiments of inventive concepts; and

[0029] Figure 9 is a flow chart illustrating operations of a PCF node according to some embodiments of inventive concepts.

DETAILED DESCRIPTION

[0030] Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

[0031] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter.

[0032] Figure 4 is a block diagram illustrating elements of a communication device UE 400 (also referred to as a mobile terminal, a mobile communication terminal, a wireless device, a wireless communication device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. As shown, communication device UE may include an antenna 407, and transceiver circuitry 401 (also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (also referred to as a RAN node) of a radio access network. Communication device UE may also include processing circuitry 403 (also referred to as a processor) coupled to the transceiver circuitry, and memory circuitry 405 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 405 may include computer readable program code that when executed by the processing circuitry 403 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 403 may be defined to include memory so that separate memory circuitry is not required. Communication device UE may also include an interface (such as a user interface) coupled with processing circuitry 403, and/or communication device UE may be incorporated in a vehicle.

[0033] As discussed herein, operations of communication device UE may be performed by processing circuitry 403 and/or transceiver circuitry 401. For example, processing circuitry 403 may control transceiver circuitry 401 to transmit communications through transceiver circuitry 401 over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry 401 from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry 405, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 403, processing circuitry 403 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to wireless communication devices). According to some embodiments, a communication device UE 400 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines.

[0034] Figure 5 is a block diagram illustrating elements of a radio access network RAN node 500 (also referred to as a network node, base station, eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configured to provide cellular communication according to embodiments of inventive concepts. As shown, the RAN node may include transceiver circuitry 501 (also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink radio communications with mobile terminals. The RAN node may include network interface circuitry 507 (also referred to as a network interface) configured to provide communications with other nodes (e.g., with other base stations) of the RAN and/or core network CN. The network node may also include processing circuitry 503 (also referred to as a processor) coupled to the transceiver circuitry, and memory circuitry 505 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 505 may include computer readable program code that when executed by the processing circuitry 503 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 503 may be defined to include memory so that a separate memory circuitry is not required.

[0035] As discussed herein, operations of the RAN node may be performed by processing circuitry 503, network interface 507, and/or transceiver 501. For example, processing circuitry 503 may control transceiver 501 to transmit downlink communications through transceiver 501 over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver 501 from one or more mobile terminals UEs over a radio interface. Similarly, processing circuitry 503 may control network interface 507 to transmit communications through network interface 507 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory 505, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 503, processing circuitry 503 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to RAN nodes). According to some embodiments, RAN node 500 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines. [0036] According to some other embodiments, a network node may be implemented as a core network CN node without a transceiver. In such embodiments, transmission to a wireless communication device UE may be initiated by the network node so that transmission to the wireless communication device UE is provided through a network node including a transceiver (e.g., through a base station or RAN node). According to embodiments where the network node is a RAN node including a transceiver, initiating transmission may include transmitting through the transceiver.

[0037] Figure 6 is a block diagram illustrating elements of a core network CN node 600 (e.g., an SMF node, an AMF node, a UPF node, a PCF node, a UDR node, an NEF node, etc.) of a communication network configured to provide cellular communication according to embodiments of inventive concepts. As shown, the CN node may include network interface circuitry 607 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the radio access network RAN. The CN node may also include a processing circuitry 603 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 605 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 605 may include computer readable program code that when executed by the processing circuitry 603 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 603 may be defined to include memory so that a separate memory circuitry is not required.

[0038] As discussed herein, operations of the CN node may be performed by processing circuitry 603 and/or network interface circuitry 607. For example, processing circuitry 603 may control network interface circuitry 607 to transmit communications through network interface circuitry 607 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 605, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 603, processing circuitry 603 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes). According to some embodiments, CN node 600 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines. [0039] In current 3GPP specifications, the network operator may need to handle simultaneously the following policies: External policies from a content provider, which may be defined on a per flow basis (through flow description/s or flowinfo); and Local policies configured at the network operator, which may be defined on a per application basis (through application identifier or appID).

[0040] It may be difficult for the network operator, specifically for the PCF, to correlate between the above external and local policies. This may result in the PCF installing separate PCC rules corresponding to both external and local policies, with the potential that the wrong enforcement actions may be executed (as the external and local policies might refer to the same traffic). An example is discussed below with respect to Figure 2.

[0041] Operation 201.) A Content Provider (e.g., Google) wants to sponsor YouTube traffic for certain subscribers. In order to do that, the Content Provider (e.g., Application Function AF server) triggers a policy request message towards the NEF entity/node (using the Nnef northbound ChangeChargeableParty API). This external policy request message includes an indication to Sponsor the traffic corresponding to certain packet filter/s (flowinfo). The NEF entity/node forwards this policy request to the PCF entity/node.

[0042] Operation 202.) The PCF entity/node receives the external policy request of Operation 201 and retrieves the (local) subscriber policy from the UDR entity/node. In this example, there is a YouTube policy (appID = YouTube) including a QoS policy (to apply a certain QoS value: QoSx) and a Charging policy (to charge the traffic to the end subscriber with a certain Rating Group RG).

[0043] Operation 203.) The PCF entity/node generates the corresponding PCC rules based on: External policies (from the AF server); and Local policies (from the UDR entity/node).

PCC rule #1 (External policy):

• flowinfo

• Charging: Sponsored

PCC rule #2 (Local policy):

• appID = YouTube

• QoS: QoSx

• Charging: Not Sponsored

[0044] Operation 204.) The SMF entity/node translates the above PCC rules into

PDRs, FARs, QERs, URRs, and installs them in the UPF entity/node:

PDR #1: • PDI with flowinfo

• FAR #1

• URR #1: Report volume (Sponsored) PDR #2:

• PDI with appID = YouTube

• FAR #2

• QER #2: QoSx

• URR #2: Report volume (Not Sponsored)

[0045] Operation 205.) The UPF entity/node matches incoming traffic against the PDRs of Operation 204. If the subscriber is running the YouTube application, the traffic corresponding to flowinfo will match PDR#1 and the corresponding enforcement actions will be executed. In this case the traffic will be Sponsored but no QoS policy will be executed. This is an incorrect behavior as the subscriber policy indicates that for YouTube traffic a QoS policy (QoSx) should be enforced.

[0046] Some embodiments of inventive concepts may address problems described above and/or may provide a mechanism to consolidate external and local policies. Some embodiments may be provided as discussed below.

[0047] During a PFCP Association procedure between UPF and SMF entities/nodes, mechanisms may be extended to report UPF capabilities with a new capability (e.g., referred to as Policy consolidation).

[0048] After PDU session establishment, when the PCF entity/node receives any external policy (e.g., Charging, QoS, etc.) from a Content Provider (e.g., Application Function AF server) that applies on a per flow basis (through flow description/s or flowinfo) and the PCF entity/node does not know if this external policy has any relationship with any of the subscriber local policies, the PCF entity/node generates the corresponding PCC rule (with flowinfo) including an indication requesting the SMF entity/node to consolidate this particular PCC rule.

[0049] When the SMF entity/node receives the above PCC rule from the PCF entity/node, the SMF entity/node will generate/transmit the corresponding rule (through PDR, FAR, QER, URR, etc.) towards the UPF entity/node, including an indication (e.g., in the PDR) requesting the UPF entity/node to consolidate this rule.

[0050] When the UPF entity/node receives incoming traffic for the PDU session, the UPF entity/node runs a PDR matching procedure as discussed below. In the event that a packet matches a PDR (e.g., PDR #X) including the indication above: the UPF entity/node will store the matched PDR (PDR #X); the UPF entity/node will continue the PDR matching process, but only evaluate PDRs with PDI of type appID according to their precedence. If there is a match with any of the above PDRs (PDR #Y), the UPF entity/node will store the matched PDR (PDR #Y)’ and the UPF entity/node will apply (consolidate) the corresponding enforcement actions according to the rule's precedence (e.g., as discussed below with respect to the example of Figures 3A-3F).

[0051] Following the previous example (of Figure 2), if the user is running the YouTube application, and if a packet matches PDR #1 (flowinfo), PDR evaluation will continue and will eventually match PDR#2 (appID = YouTube).

PDR #1:

• PDI with flowinfo

• FAR #1 ENFORCED

• URR #1: Report volume (Sponsored) ENFORCED PDR #2:

• PDI with appID = YouTube

• FAR #2 NOT ENFORCED

• QER #2: QoSx ENFORCED

• URR #2: Report volume (Not Sponsored) NOT ENFORCED

[0052] The UPF entity/node will then apply the corresponding enforcement actions according to the rule's precedence, i.e. FAR #1 (not FAR #2), URR #1 (not URR #2) and QER #2, so the correct Charging (Sponsored) and QoS handling (QoSx) will be applied.

[0053] According to some embodiments, the network operator may be able to consolidate between the external and local policies, so the policy enforcements (e.g., QoS and/or Charging) will be correctly applied.

[0054] Some embodiments of inventive concepts may allow the network operator to consolidate the external and the local policies by extending the protocols for N7 and N4 interfaces with an indication to request policy consolidation.

[0055] Figures 3A-3F provide a message diagram illustrating an example according to some embodiments where the UPF entity/node consolidates the external and the local policies for a subscriber's PDU session. Operations of Figures 3A-3F are discussed below.

[0056] Operations 301 and 302) At a PFCP Association procedure between UPF and SMF entities/nodes, mechanisms are extended to report UPF capabilities with a new capability (e.g., referred to as Policy consolidation POCU as shown in the table below). This extension may allow the SMF entity/node to know which UPF entities/nodes support this capability and thus can influence UPF selection by the SMF entity/node. At operation 301, the UPF entity/node may transmit the PFCP Association Request message (including a UPF capability indicating that Policy Consolidation is supported) to the SMF entity/node, and at operation 302, the SMF entity/node may respond with a PFCP association response message acknowledging the PFCP association request message.

[0057] The table below is a modification of Table 8.2.25-1 (“UP Function Features”) of 3GPP TS 29.244 V15.5.0 (2019-03), also referred to as Reference [2], according to some embodiments of inventive concepts.

[0058] Operations 303 and 304.) The UE triggers PDU session establishment, by sending a PDU Session Establishment Request message to an Access and Mobility Management Function AMF entity/node. The AMF entity/node selects an SMF entity/node to manage the PDU session (e.g., the SMF selection function in the AMF entity/node selects an SMF instance based on the available SMF instances obtained from an NRF entity/node or on the configured SMF information in the AMF entity/node) and triggers a Nsmf PDU Session Create message. Note that the message diagram of Figures 3A-3F does not include all the signaling messages involved in the PDU Session Establishment procedure. Signaling messages relevant for the present disclosure are described in subsequent operations.

[0059] Operation 305.) The SMF entity/node triggers transmission of a Npcf_SMPolicyControl_Create Request message to the PCF entity/node to retrieve Session Management SM policies for the user PDU session.

[0060] Operation 306.) The PCF entity/node triggers transmission of a Nudr_Query Request message to the UDR entity/node to retrieve the policy data for this user's PDU session.

[0061] Operation 307.) The UDR entity/node answers with a Nudr_Query Response message including the Subscriber Policy Data, which includes a YouTube policy (e.g., requesting to apply a certain QoS handling for YouTube application traffic).

[0062] Operation 308.) The PCF entity/node generates the corresponding PCC rule/s based on Subscriber Policy Data (including a PCC rule for YouTube with certain QoS handling).

[0063] Operation 309.) Based on the Subscriber policy data and the PCC rule(s) of operations 307 and 308, the PCF entity/node triggers transmission of a Npcf_SMPolicyControl_Create Response message (including the PCC rules) to the SMF entity/node to be applied for this user PDU session. In this case, as an example, there will be a PCC rule for the YouTube application including different enforcement actions (specifically a certain QoS handling).

[0064] Operation 310.) The SMF entity/node triggers transmission of a PFCP Session Establishment Request message to the UPF entity/node, with the PFCP Session Establishment Request message including the corresponding PDRs/FARs/QERs/URRs (based on the PCC rule/rules received at operation 309). In this case, there will be a PDR with PDI of type application with appID = YouTube, and a corresponding FAR, QER and URR.

[0065] Operation 311.) The UPF entity/node stores the PDRs/FARs/QERs/URRs and answers back to the SMF entity/node with a PFCP Session Establishment Response message acknowledging the PFCP Session Establishment Request message. [0066] Operations 312 and 313.) The user opens an application (e.g., YouTube) at the UE and sends traffic towards the Content Provider's AF server (e.g., a QUIC Client Hello CHLO message, also referred to as an application initiation message).

[0067] Operation 314.) The content provider (e.g., Google Inc.) wants to sponsor a certain application (e.g., YouTube). In order to do that, the Content Provider (AF server) triggers the Nnef Northbound "Changing the chargeable party" procedure. This procedure is used by Content Provider to request charging to a sponsor (e.g., Google Inc.) for the target application (e.g., YouTube) for a specific user.

[0068] Operation 315.) The Content Provider triggers transmission of a Nnef HTTP POST message to the network operator's NEF entity/node. The body of the HTTP POST message includes an AF Identifier (e.g., afID = Google Inc), the flow information corresponding to the flow created by the user in Operation 313 (flowinfo), the external user identity (externallD or gpsi) and sponsorinformation (indicating who will be charged).

[0069] Operations 316 and 317.) After receiving the message of Operation 315, the NEF entity/node shall authorize the request and respond back to AF server (e.g., using an Nnef 200 OK successful response message in this case) to acknowledge the Nnef HTTP POST message). NEF maps the externalld or General Public Subscription Identifier GPSI to an internal user identity and looks for the PCF handling the user session.

[0070] Operation 318.) The NEF entity/node triggers transmission of a Npcf HTTP POST message towards the PCF entity/node. The body of HTTP POST message shall include AF Identifier (afID=Google Inc), the flow information (flowinfo), the internal user identity (internalld or gpsi) and sponsorinformation (indicating who will be charged).

[0071] Operation 319.) The PCF entity/node answers back to the NEF entity/node (e.g., using Npcf 200 OK successful response message in this case) to acknowledge the Npcf_HTTP_POST message.

[0072] Operations 320 and 321.) As the PCF entity/node is not able to map this external policy to any of the subscriber local policies, the PCF entity/node generates a separate PCC rule. The PCF entity/node triggers transmission of a Npcf_SMPolicyControl_Update Request message (to the SMF entity/node) with the PCC rule of operation 320, including the flow information (flowinfo), sponsorinformation and an indication requesting that the SMF entity/node apply policy consolidation (policyConsolidation). [0073] Operation 322.) The SMF entity/node answers back to the PCF entity/node with a Npcf_SMPolicyControl_Update Response message to acknowledge the Npcf_SMPolicyControl_Update Request message.

[0074] Operation 323.) The SMF entity/node generates the corresponding rule (PDR with PDI = flowinfo, FAR, URR) including an indication requesting that the UPF entity/node apply policy consolidation (policyConsolidation).

[0075] Operation 324.) The SMF entity/node triggers transmission of a PFCP Session Modification Request message (to the UPF entity/node) including a PDR (e.g., PDR #Y) with PDI of type Service Data Flow SDF Filter (including flowinfo), an indication requesting that the UPF entity/node apply policy consolidation (policyConsolidation), and a corresponding FAR and URR (e.g., FAR #Y and URR #Y).

[0076] Operation 325.) The UPF entity/node answers back to the SMF entity/node with a PFCP Session Modification Response message to acknowledge the PFCP Session Modification Request message.

[0077] Operation 326.) When the UPF entity/node receives incoming traffic for the PDU session, the UPF entity/node runs a PDR matching procedure as follows:

• In the event that a packet matches a PDR (PDR #A) including the indication above: o The UPF entity/node will store the matched PDR (PDR #A) o The UPF entity/node will continue the PDR matching process, but only evaluate PDRs with PDI of appID according to their precedence. o If there is a match with any of the above PDRs (e.g., PDR #B), the UPF entity/node will store the matched PDR (PDR #B). o The UPF entity/node will apply (consolidate) the corresponding enforcement actions according to the rule's precedence (e.g., as discussed with respect to the example below).

[0078] In this example, the UPF entity/node detects traffic matching the PDR with PDI of type SDF Filter (including flowinfo) requiring policy consolidation, so that the UPF entity/node continues PDR evaluation and matches the PDR with PDI appID =YouTube. The UPF entity/node applies the corresponding actions (Charging and QoS) as per the rule's precedence, as follows:

PDR #A:

• PDI with flowinfo, and policyConsolidation

• FAR #A ENFORCED

• URR #A: Report volume (Sponsored) ENFORCED

PDR #B: • PDI with appld= YouTube

• FAR #B NOT ENFORCED

• QER #B: QoSx ENFORCED

• URR #B: Report volume (Not Sponsored) NOT ENFORCED

[0079] Accordingly, the UPF entity/node will enforce FAR #A (not FAR #B), URR #A (not URR #B) and QER #B, so that the correct Charging (Sponsored) and QoS handling (QoSx) will be applied.

[0080] Finally, approaches described in the present disclosure may apply not only to 5^th Generation 5G network architectures, but also to 4^th Generation 4G network architectures, for example, by replacing: NEF with SCEF; AF with SCS/AS; PCF with PCRF; SMF with PGW-C or TDF-C; and/or UPF with PGW-U or TDF-U.

[0081] According to some embodiments, mechanism may thus be provided to consolidate external and local policies in 5G networks.

[0082] Operations of a Core Network CN node 600 (implemented using the structure of Figure 6) will now be discussed with reference to the flow chart of Figure 7 according to some embodiments of inventive concepts. For example, modules may be stored in memory 605 of Figure 6, and these modules may provide instructions so that when the instructions of a module are executed by respective CN node processing circuitry 603, processing circuitry 603 performs respective operations of the flow chart.

[0083] According to some embodiments at block 7301, processing circuitry 603 transmits (through network interface 607) an association request message to a second CN node. The association request message includes an indication that the first CN node supports policy consolidation. Operations of block 7301 may be performed, for example, as discussed above with respect to operation 301 of Figure 3 A where the PFCP Association Request Message is transmitted to the SMF entity/node.

[0084] According to some embodiments at block 7302, processing circuitry 603 receives (through network interface 607) an association response message from the second CN node acknowledging the association request message of block 7301. Operations of block 7302 may be performed, for example, as discussed above with respect to operation 302 of Figure 3A where the PFCP Association Response message is received from the SMF entity/node. [0085] According to some embodiments at block 7310, processing circuitry 603 receives (through network interface 607) a session establishment request message for a communication device. The session establishment request message is received from a second CN node, the session establishment request message includes a first packet detection rule PDR for an application supported by an application server, the first PDR includes first packet detection information PDI including an application identifier appID for the application, and the session establishment request message includes at least one first action rule associated with the first PDR. For example, the at least one first action rule may include a first usage reporting rule URR associated with the first PDR. Operations of block 7310 may be performed, for example, as discussed above with respect to operation 310 of Figure 3B where the PFCP Session Establishment Request Message is received from the SMF entity/node.

[0086] According to some embodiments at block 7311, processing circuitry 603 transmits (through network interface 607) a session establishment response message to the second CN node acknowledging the session establishment request message of block 7310. Operations of block 7311 may be performed, for example, as discussed above with respect to operation 311 of Figure 3B where the PFCP Session Establishment Response message is transmitted to the SMF entity/node.

[0087] According to some embodiments at block 7324, processing circuitry 603 receives (through network interface 607) a session modification request message for the communication device. The session modification request message is received from the second CN node, the session modification request message includes a second PDR for the application supported by the application server, the second PDR includes a second PDI including flow information for the application, the session modification request message includes at least one second action rule associated with the second PDR, and the appID and the flow information are different. For example, the session modification request message may include an indication to apply policy consolidation, and/or the at least one second action rule may include a second URR associated with the second PDR. Operations of block 7324 may be performed, for example, as discussed above with respect to operation 324 of Figure 3E where the PFCP Session Modification Request message is received from the SMF entity/node.

[0088] According to some embodiments at block 7325, processing circuitry 603 transmits (through network interface 607) a session modification response message to the second CN node acknowledging the session modification request message of operation 7324. Operations of block 7325 may be performed, for example, as discussed above with respect to operation 325 of Figure 3E where the PFCP Session Modification Response message is transmitted to the SMF entity/node.

[0089] According to some embodiments at block 7326a, processing circuitry 603 receives (through network interface 607) a packet of application traffic. Operations of block 7326a may be performed, for example, as discussed above with respect to operation 326a of Figure 3F where a packet of uplink application traffic from the UE is received by the UPF entity/node for retransmission to the content provider (AF) and/or where a packet of downlink application traffic from the content provider (AF) is received by the UPF entity/node for retransmission to the UE.

[0090] According to some embodiments at block 7326b- 1, processing circuitry 603 detects that the packet of uplink/downlink application traffic matches the second PDR based on the flow information of the second PDI matching flow information of the packet of application traffic. According to some embodiments at block 7326b-2, processing circuitry 603 detects that the uplink/downlink packet of application traffic matches the first PDR based on the appID of the first PDR matching an appID of the packet of application traffic. For example, detecting that the packet of application traffic matches the first PDR may include detecting that the packet of application traffic matches the first PDR based on the first PDI including the appID responsive to the session modification request message including the indication to apply policy consolidation. Operations of blocks 7326b- 1 and/or 7326b-2 may be performed, for example, as discussed above with respect to operation 326b of Figure 3F.

[0091] According to some embodiments at block 7327, processing circuitry 603 processes the packet of uplink/downlink application traffic based on the at least one first action rule associated with the first PDR and/or based on the at least one second action rule associated with the second PDR. For example, processing the packet of application traffic may include processing the packet of application traffic based on the at least one first action rule associated with the first PDR and based on the at least one second action rule associated with the second PDR responsive to the session modification request message including the indication to apply policy consolidation. Operations of block 7327 may be performed, for example, as discussed above with respect to operation 327 where a packet of uplink application traffic is retransmitted to the content provider AF and/or where a packet downlink application traffic is retransmitted to the UE.

[0092] According to some embodiments at block 7328, processing circuitry 603 applies the second URR associated with the second PDR for the packet of application traffic responsive to the session modification request message including the indication to apply policy consolidation. Operations of block 7328 may be performed, for example, as discussed above with respect to operation 328 of Figure 3F. For example, the first URR may indicate that application traffic is charged against a quota of data associated with the communication device, the second URR may indicate that application traffic associated with the second PDR is sponsored, and the second URR is applied so that the packet of application traffic is not charged against the quota of data associated with the communication device.

[0093] According to some embodiments, the at least one second action rule may include a forwarding action rule FAR associated with the second PDR, and processing the packet of application traffic at block 7327 may include forwarding the packet of application traffic according to the FAR associated with the second PDR responsive to the session modification request message including the indication to apply policy consolidation. For example, the at least one first action rule may include an FAR associated with the first PDR, such that the FAR associated with the first PDR is not applied when forwarding the packet of application traffic responsive to the session modification request message including the indication to apply policy consolidation. According to some embodiments for a packet of downlink application traffic, the packet of application traffic is received from the application server, and the packet of application traffic is forwarded to the communication device (UE) according to the FAR associated with the second PDR. According to some embodiments for a packet of uplink application traffic, the packet of application traffic is received from the communication device (UE), and the packet of application traffic is forwarded to the application server according to the FAR associated with the second PDR.

[0094] According to some embodiments, the at least one first action rule may include a Quality of Service Enforcement Rule QER associated with the first PDR, and the session modification request message does not include a QER associated with the second PDR. In this situation, the packet of application traffic may be processed at block 7327 by forwarding the packet of application traffic according to the QER associated with the first PDR. [0095] According to some embodiments, processing circuitry 603 may detect that the packet matches the first PDR at block 7326b-2 by detecting that the packet of application traffic matches the first PDR after detecting that the packet of application traffic matches the second PDR.

[0096] According to some embodiments, the flow information for the application may include at least one of a source Internet Protocol IP address for the communication device, a source port for the communication device, a destination IP address for the application server, a destination port for the application server, and/or an indication of an IP protocol.

[0097] According to some embodiments, the flow information is omitted from the session establishment request message, and/or the appID is omitted form the session modification request message.

[0098] According to some embodiments of Figure 7, the first CN node may be one of a user plane function UPF entity/node, a PDN Gateway User plane function PGW-U entity/node and/or a Traffic Detection Function User plane function TDF-U entity/node, and the second CN node may be one of a session management function SMF entity/node, a PDN Gateway Control plane function PGW-C entity/node and/or a Traffic Detection Function Control plane function TDF-C entity/node.

[0099] Various operations from the flow chart of Figure 7 may be optional with respect to some embodiments of CN nodes and related methods. Regarding methods of some embodiments, for example, operations of blocks 7301, 7302, 7311, 7325, and/or 7328 of Figure 7 may be optional.

[0100] Operations of a Core Network CN node 600 (implemented using the structure of Figure 6) will now be discussed with reference to the flow chart of Figure 8 according to some embodiments of inventive concepts. For example, modules may be stored in memory 605 of Figure 6, and these modules may provide instructions so that when the instructions of a module are executed by respective CN node processing circuitry 603, processing circuitry 603 performs respective operations of the flow chart.

[0101] According to some embodiments at block 8301, processing circuitry 603 receives (through network interface 607) an association request message from the second CN node, with the association request message including an indication that the second CN node supports policy consolidation. Operations of block 8301 may be performed, for example, as discussed above with respect to operation 301 of Figure 3 A where the PFCP Association Request Message is received from the UPF entity/node.

[0102] According to some embodiments at block 8302, processing circuitry 603 transmits (through network interface 607) an association response message to the second CN node acknowledging the association request message of block 8301. Operations of block 8302 may be performed, for example, as discussed above with respect to operation 302 of Figure 3A where the PFCP Association Response message is transmitted to the UPF entity/node.

[0103] According to some embodiments at block 8304, processing circuitry 603 receives (through network interface 607) a session create message from another CN node (e.g., an AMF entity/node), with the session create message relating to session establishment for the communication device. Operations of block 8304 may be performed, for example, as discussed above with respect to operation 304 of Figure 3 A where the Nsmf PDU Session Create message is received from the AMF entity/node.

[0104] According to some embodiments at block 8305, processing circuitry 603 transmits (through network interface 607) a policy control create request message to a third CN node, with the policy control create request message being transmitted responsive to receiving the session create message. Operations of block 8305 may be performed, for example, as discussed above with respect to operation 305 of Figure 3A where the Npcf SMPolicyControl Create Request message is transmitted to the PCF entity/node.

[0105] According to some embodiments at block 8309, processing circuitry 603 receives (through network interface 607) a policy control create message from the third CN node. The policy control create message includes a Policy and Charging Control PCC rule of the policy control create message, and the PCC rule of the policy control create message includes the appID for the application. In addition, the PCC rule of the policy control create message may include Quality of Service QoS information for the application, and/or the policy control create message may be a policy control create response message corresponding to the policy control create request message of block 8305. Operations of block 8309 may be performed, for example, as discussed above with respect to operation 309 of Figure 3B where the Npcf PolicyControl Create Response message is received from the PCF entity/node.

[0106] According to some embodiments at block 8310, processing circuitry 603 transmits (through network interface 607) a session establishment request message for a communication device to a second CN node. The session establishment request message includes a first packet detection rule PDR for an application supported by an application server, the first PDR includes first packet detection information PDI including an application identifier appID for the application, and the session establishment request message includes at least one first action rule associated with the first PDR. Operations of block 8310 may be performed, for example, as discussed above with respect to operation 310 of Figure 3B where the PFCP Session Establishment Request message is transmitted to the UPF entity /node.

[0107] According to some embodiments, the first PDI may include the appID responsive to the PCC rule of the policy control create message of block 8309 including the appID, and the at least one first action rule associated with the first PDR may be generated based on the PCC rule of the policy control create message.

[0108] According to some embodiments, the at least one first action rule may include a usage reporting rule URR associated with the first PDR, and the URR associated with the first PDR may indicate that application traffic associated with the first PDR is charged against a quota of data associated with the communication device. Moreover, the URR associated with the first PDR may be generated based on the PCC rule of the policy control create message of block 8309.

[0109] According to some embodiments, the at least one first action rule associated with the first PDR may be generated based on QoS information for the application of block 8309. For example, the at least one first action rule may include a Quality of Service Enforcement Rule QER associated with the first PDR, and the QER associated with the first PDR may be generated based on the QoS information.

[0110] According to some embodiments, the at least one first action rule may include a forwarding action rule FAR associated with the first PDR, and the FAR associated with the first PDR may be generated based on the PCC rule of the policy control create message of block 8309.

[0111] According to some embodiments at block 8311, processing circuitry 603 receives (through network interface 607) a session establishment response message from the second CN node acknowledging the session establishment request message of block 8310. Operations of block 8311 may be performed, for example, as discussed above with respect to operation 311 of Figure 3B where the PFCP Session Establishment Response message is received from the UPF entity/node.

[0112] According to some embodiments at block 8321, processing circuitry 603 receives (through network interface 607) a policy control update request message from a third CN node (e.g., PCF entity/node and/or a PCRF entity/node), with the policy control update request message including a Policy and Charging Control PCC rule of the policy control update request message. The PCC rule of the policy control update request message also includes the flow information for the application, and a first indication to apply policy consolidation. In addition, the PCC rule of the policy control update request message may include sponsor information indicating that application traffic associated with the second PDR is sponsored so that application traffic is not charged against a quota of data associated with the communication device. Operations of block 8321 may be performed, for example, as discussed above with respect to operation 321 of Figure 3E where the Npcf SMPolicyControl Update Request message is received from the PCF entity/node.

[0113] According to some embodiments at block 8322, processing circuitry 603 transmits (through network interface 607) a policy control update response message to the third CN node acknowledging the policy control update request message of block 8321. Operations of block 8322 may be performed, for example, as discussed above with respect to operation 322 of Figure 3E where the Npcf SMPolicyControl Update Response message is transmitted to the PCF entity/node.

[0114] According to some embodiments at block 8324, processing circuitry 603 transmits (through network interface 607) a session modification request message for the communication device to the second CN node. The session modification request message includes a second PDR for the application supported by the application server, the second PDR includes second PDI including flow information for the application, the session modification request message includes at least one second action rule associated with the second PDR, and the appID and the flow information are different. In addition, the session modification request message may include a second indication to apply policy consolidation responsive to the association request message of block 8301 including the indication that the second CN node supports policy consolidation. Operations of block 8324 may be performed, for example, as discussed above with respect to operation 324 of Figure 3E where the PFCP Session Modification Request message is transmitted to the UPF entity/node.

[0115] According to some embodiments, the session modification request message may include the second indication to apply policy consolidation responsive to the policy control update request message including the first indication to apply policy consolidation, the second PDI of the session modification request message may include the flow information for the application responsive to the PCC rule of the policy control update request message including the flow information for the application, and the at least one second action rule associated with the second PDR may be generated based on the PCC rule of the policy control update request message.

[0116] According to some embodiments, the at least one second action rule may include a usage reporting rule URR associated with the second PDR indicating that application traffic associated with the second PDR is sponsored responsive to the PCC rule of the policy control update request message including the sponsor information indicating that application traffic associated with the second PDR is sponsored.

[0117] According to some embodiments, the at least one second action rule may include a forwarding action rule FAR associated with the second PDR, and the FAR associated with the second PDR may be generated based on the PCC rule of the policy control update request message.

[0118] According to some embodiments the at least one second action rule may include a quality of service enforcement rule QER associated with the second PDR, and the QER associated with the second PDR may be generated based on the PCC rule of the policy control update request message.

[0119] According to some embodiments at block 8325, processing circuitry 603 receives (through network interface 607) a session modification response message from the second CN node acknowledging the session modification request message of block 8324. Operations of block 8325 may be performed, for example, as discussed above with respect to operation 325 of Figure 3E where the PFCP Session Modification Response message is received from the UPF entity/node.

[0120] According to some embodiments, the flow information for the application may include at least one of a source Internet Protocol IP address for the communication device, a source port for the communication device, a destination IP address for the application server, a destination port for the application server, and/or an indication of an IP protocol.

[0121] According to some embodiments, the flow information may be omitted from the session establishment request message, and/or the appID may be omitted from the session modification request message.

[0122] According to some embodiments of Figure 8, the first CN node may be one of a session management function SMF entity /node, a PDN Gateway Control plane function PGW-C entity/node and/or a Traffic Detection Function Control plane function TDF-C entity/node, and the second CN node may be one of a user plane function UPF entity/node, a PDN Gateway User plane function PGW-U entity/node and/or a Traffic Detection Function User plane function TDF-U entity/node.

[0123] Various operations from the flow chart of Figure 8 may be optional with respect to some embodiments of CN nodes and related methods. Regarding methods of some embodiments, for example, operations of blocks 8301, 8302, 8304, 8305, 8309, 8311, 8321, 8322, and/or 8325 of Figure 8 may be optional.

[0124] Operations of a Core Network CN node 600 (implemented using the structure of Figure 6) will now be discussed with reference to the flow chart of Figure 9 according to some embodiments of inventive concepts. For example, modules may be stored in memory 605 of Figure 6, and these modules may provide instructions so that when the instructions of a module are executed by respective CN node processing circuitry 603, processing circuitry 603 performs respective operations of the flow chart.

[0125] According to some embodiments at block 9305, processing circuitry 603 receives (through network interface 607) a policy control create request message from a second CN node, with the policy control create request message relating to session establishment for a communication device. Operations of block 9305 may be performed, for example, as discussed above with respect to operation 305 of Figure 3 A where the Npcf SMPolicyControl Create Request message is received from the SMF entity/node.

[0126] According to some embodiments at block 9306, processing circuitry 603 transmits (through network interface 607) a query request message to a third CN node (e.g., a UDR entity/node) responsive to receiving the policy control create request message of block 9305. Operations of block 9306 may be performed, for example, as discussed above with respect to operation 306 of Figure 3A where the Nudr_DM_Query Request message is transmitted to the UDR entity/node.

[0127] According to some embodiments at block 9307, processing circuitry 603 receives (through network interface 607) a query response message from the third CN node. The query response message corresponds to the query request message, and the query response message includes subscriber policy data including the appID for the application. Operations of block 9307 may be performed, for example, as discussed above with respect to operation 307 of Figure 3A where the Nudr_DM_Query Response message is received from the UDR entity/node.

[0128] According to some embodiments at block 9308, processing circuitry 603 generates a Policy and Charging Control PCC rule(s) corresponding to the query response message of block 9307. For example, the PCC rule may be generated based on the subscriber policy data of the query response message including the appID, the subscriber policy data may include Quality of Service QoS information for the application, and/or the policy control create message may include the QoS information for the application from the query response message. Operations of block 9308 may be performed, for example, as discussed above with respect to operation 308 of Figure 3B where the PCF entity/node generates the corresponding PCC rules based on subscriber policy data from the Nudr_DM_Query Response message of operation 307.

[0129] According to some embodiments at block 9309, processing circuitry 603 transmits (through network interface 607) a policy control create (response) message for the communication device to a second core network CN node. The policy control create message includes the PCC rule(s) of the policy control create message, and the PCC rule of the policy control create message includes an application identifier appID for an application supported by an application server. For example, the policy control create (response) message may be a policy control create response message that is transmitted responsive to receiving the policy control create request message of block 9305. Operations of block 9309 may be performed, for example, as discussed above with respect to operation 309 of Figure 3B where the Npcf PolicyControl Create Response message is transmitted to the SMF entity/node.

[0130] According to some embodiments at block 9318, processing circuitry 603 receives (through network interface 607) a post message from a fourth CN node (e.g., a network exposure function NEF entity/node and/or a Service Capability Exposure Function SCEF entity/node). The post message includes flow information for the application and first sponsor information indicating that application traffic associated with the application is sponsored so that application traffic associated with the application is not charged against a quota of data associated with the communication device. The post message may also include an application function identifier afID associated with a provider of the application and an internal identifier associated with the communication device. Operations of block 9318 may be performed, for example, as discussed above with respect to operation 318 of Figure 3D where the Npcf HTTP POST message is received from the NEF entity /node.

[0131] According to some embodiments at block 9319, processing circuitry 603 transmits (through network interface 607) a post response message acknowledging the Post message of block 9318. Operations of block 9319 may be performed, for example, as discussed above with respect to operation 319 of Figure 3D where the Npcf 200 OK message is transmitted to the NEF entity /node.

[0132] According to some embodiments at block 9320, processing circuitry 603 generates a PCC rule(s) based on the post message of block 9318 (also referred to as the PCC rule of the of the policy control update request message). The PCC rule of the policy control update request message may include second sponsor information indicating that application traffic associated with the application is sponsored responsive to the post message including the first sponsor information, and/or the PCC rule of the policy control update request message may include flow information for the application responsive to the post message including the flow information for the application. Operations of block 9320 may be performed, for example, as discussed above with respect to operation 320 of Figure 3D where the PCF entity/node generates the PCC rule(s) corresponding to the Npcf HTTP POST message.

[0133] According to some embodiments at block 9321, processing circuitry 603 transmits (through network interface 607) a policy control update request message for the communication device to the second CN node. The policy control update request message includes the PCC rule of operation 9320 (also referred to as the PCC rule of the policy control update request message), and the PCC rule of the policy control update request message includes flow information for the application and an indication to apply policy consolidation for application traffic between the communication device and the application server. Operations of block 9321 may be performed, for example, as discussed above with respect to operation 321 of Figure 3E where the Npcf SMPolicyControl Update Request message is transmitted to the SMF entity/node. Operations of block 9321 may be performed, for example, as discussed above with respect to operation 321 of Figure 3E where the Npcf SMPolicyControl Update Request message is transmitted to the SMF entity/node.

[0134] According to some embodiments at block 9322, processing circuitry 603 receives (through network interface 607) a Policy Control Update Response message acknowledging the policy control update request message of block 9321. Operations of block 9322 may be performed, for example, as discussed above with respect to operation 322 of Figure 3E where the Npcf SMPolicyControl Update Response message is received from the SMF entity/node.

[0135] According to some embodiments of Figure 9, the first CN node may be one of a Policy Control Function PCF entity/node and/or a Policy and Charging Rule Function PCRF entity/node, and the second CN node may be one of a session management function SMF entity/node, a PDN Gateway Control plane function PGW-C entity/node and/or a Traffic Detection Function Control plane function TDF-C entity/node.

[0136] Various operations from the flow chart of Figure 9 may be optional with respect to some embodiments of CN nodes and related methods. Regarding methods of some embodiments, for example, operations of blocks 9305, 9306, 9307, 9308, 9318, 9319, 9320, and/or 9322 of Figure 9 may be optional.

[0137] Explanations are provided below for various abbreviations/acronyms used in the present disclosure.

Abbreviation Explanation

3 GPP 3rd Generation Partnership Project

4G 4th Generation

5G 5th Generation

5GC 5th Generation Core

AF Application Function

AMF Access and Mobility Management Function

API Application Program Interface

AS Application Server

CHLO Client Hello

CP Control Plane CUPS Control User Plane Separation

DL Downlink

FAR Forwarding Action Rule

FQDN Fully Qualified Domain Name

GPSI Generic Public Subscription Identifier

HTTP Hyper Text Transfer Protocol

HTTPS Hyper Text Transfer Protocol Secure

NEF Network Exposure Function

NRF Network Resource Function

OTT Over The Top

PCC Policy and Charging Control

PCF Policy Control Function

PCRF Policy and Charging Rule Function

PDI Packet Detection Information

PDN Packet Data Network

PDR Packet Detection Rule

PDU Protocol Data Unit

PFCP Packet Flow Control Protocol

PGW Packet Gateway

PGW-C PDN Gateway Control plane function

PGW-U PDN Gateway User plane function

POCU Policy Consolidation

QER QoS Enforcement Rule

QoE Quality of Experience

QoS Quality of Service

QUIC Quick UDP Internet Connection

RAN Radio Access Network

RG Rating Group

SBA Service Based Architecture

SCEF Service Capability Exposure Function

SCS Service Capability Server SDF Service Data Flow

SLA Service Level Agreement

SM Session Management

SMF Session Management Function

TCP Transport Control Protocol

TDF-C Traffic Detection Function Control plane function

TDF-U Traffic Detection Function User plane function

TLS Transport Layer Security

UDP User Datagram Protocol

UDR Unified Data Repository

UE User Equipment

UL UpLink

UP User Plane

UPF User Plane Function

URR Usage Reporting Rule

[0138] References are identified below.

[1] 3GPP TS 23.501 V16.3.0 (2019-12), System architecture for the 5G System (5GS)

[2] 3GPP TS 29.244 V15.5.0 (2019-03), Interface between the Control Plane and the User Plane Nodes; Stage 3 (Release 16)

[0139] Additional explanation is provided below.

[0140] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0141] Some of the embodiments contemplated herein have been described with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0142] Further definitions and embodiments are discussed below.

[0143] In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0144] When an element is referred to as being "connected", "coupled", "responsive", or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, "coupled", "connected", "responsive", or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term "and/or" (abbreviated “/”) includes any and all combinations of one or more of the associated listed items.

[0145] It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.

[0146] As used herein, the terms "comprise", "comprising", "comprises", "include", "including", "includes", "have", "has", "having", or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation "e.g.", which derives from the Latin phrase "exempli gratia," may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation "i.e.", which derives from the Latin phrase "id est," may be used to specify a particular item from a more general recitation.

[0147] Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

[0148] These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer- readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as "circuitry," "a module" or variants thereof.

[0149] It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0150] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments and/or claims are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Claims

CLAIMS:

1. A method of operating a first core network, CN, node, the method comprising: receiving (7310) a session establishment request message for a communication device, wherein the session establishment request message is received from a second CN node, wherein the session establishment request message includes a first packet detection rule, PDR, for an application supported by an application server, wherein the first PDR includes first packet detection information, PDI, including an application identifier, appID, for the application, and wherein the session establishment request message includes at least one first action rule associated with the first PDR; receiving (7324) a session modification request message for the communication device, wherein the session modification request message is received from the second CN node, wherein the session modification request message includes a second PDR for the application supported by the application server, wherein the second PDR includes a second PDI including flow information for the application, wherein the session modification request message includes at least one second action rule associated with the second PDR, and wherein the appID and the flow information are different; receiving (7326a) a packet of application traffic; detecting (7326b- 1) that the packet of application traffic matches the second PDR based on the flow information of the second PDI matching flow information of the packet of application traffic; detecting (7326b-2) that the packet of application traffic matches the first PDR based on the appID of the first PDR matching an appID of the packet of application traffic; and processing (7327) the packet of application traffic based on the at least one first action rule associated with the first PDR and/or based on the at least one second action rule associated with the second PDR.

2. The method of Claim 1 , wherein the session modification request message includes an indication to apply policy consolidation, wherein detecting that the packet of application traffic matches the first PDR comprises detecting that the packet of application traffic matches the first

34 PDR based on the first PDI including the appID responsive to the session modification request message including the indication to apply policy consolidation.

3. The method of Claim 2, wherein processing the packet of application traffic comprises processing the packet of application traffic based on the at least one first action rule associated with the first PDR and based on the at least one second action rule associated with the second PDR responsive to the session modification request message including the indication to apply policy consolidation.

4. The method of any of Claims 2-3, wherein the at least one second action rule comprises a forwarding action rule, FAR, associated with the second PDR, and wherein processing the packet of application traffic comprises forwarding the packet of application traffic according to the FAR associated with the second PDR responsive to the session modification request message including the indication to apply policy consolidation.

5. The method of Claim 4, wherein the at least one first action rule comprises an FAR associated with the first PDR, and wherein the FAR associated with the first PDR is not applied when forwarding the packet of application traffic responsive to the session modification request message including the indication to apply policy consolidation.

6. The method of any of Claims 4-5, wherein receiving the packet of application traffic comprises receiving the packet of application traffic from the application server, and wherein forwarding the packet of application traffic comprises forwarding the packet of application traffic to the communication device according to the FAR associated with the second PDR.

7. The method of any of Claims 4-5, wherein receiving the packet of application traffic comprises receiving the packet of application traffic from the communication device, and wherein forwarding the packet of application traffic comprises forwarding the packet of application traffic to the application server according to the FAR associated with the second PDR.

35

8. The method of any of Claims 2-7, wherein the at least one first action rule includes a first usage reporting rule, URR, associated with the first PDR, and wherein the at least one second action rule includes a second URR associated with the second PDR, the method further comprising: applying (7328) the second URR associated with the second PDR for the packet of application traffic responsive to the session modification request message including the indication to apply policy consolidation.

9. The method of Claim 8, wherein the first URR indicates that application traffic is charged against a quota of data associated with the communication device, wherein the second URR indicates that application traffic associated with the second PDR is sponsored, and wherein the second URR is applied so that the packet of application traffic is not charged against the quota of data associated with the communication device.

10. The method of any of Claims 2-9, wherein the at least one first action rule includes a Quality of Service Enforcement Rule, QER, associated with the first PDR, and wherein processing the packet of application traffic comprises forwarding the packet of application traffic according to the QER associated with the first PDR.

11. The method of Claim 10, wherein the session modification request message does not include a QER associated with the second PDR.

12. The method of any of Claims 1-11, wherein detecting that the packet matches the first PDR comprises detecting that the packet of application traffic matches the first PDR after detecting that the packet of application traffic matches the second PDR.

13. The method of any of Claims 1-12, wherein the flow information for the application includes at least one of a source Internet Protocol, IP, address for the communication device, a source port for the communication device, a destination IP address for the application server, a destination port for the application server, and/or an indication of an IP protocol.

14. The method of any of Claims 1-13, wherein the flow information is omitted from the session establishment request message, and/or wherein the appID is omitted form the session modification request message.

15. The method of any of Claims 1-14, wherein the first CN node comprises one of a user plane function, UPF, node, a PDN Gateway User plane function, PGW-U, node and/or a Traffic Detection Function User plane function, TDF-U, node, and wherein the second CN node comprises one of a session management function, SMF, node, a PDN Gateway Control plane function, PGW-C, node and/or a Traffic Detection Function Control plane function, TDF-C, node.

16. The method of any of Claims 1-15 further comprising: transmitting (7301) an association request message to the second CN node, wherein the association request message includes an indication that the first CN node supports policy consolidation.

17. A method of operating a first core network, CN, node, the method comprising: transmitting (8310) a session establishment request message for a communication device, wherein the session establishment request message is transmitted to a second CN node, wherein the session establishment request message includes a first packet detection rule, PDR, for an application supported by an application server, wherein the first PDR includes first packet detection information, PDI, including an application identifier, appID, for the application, and wherein the session establishment request message includes at least one first action rule associated with the first PDR; and transmitting (8324) a session modification request message for the communication device, wherein the session modification request message is transmitted to the second CN node, wherein the session modification request message includes a second PDR for the application supported by the application server, wherein the second PDR includes second PDI including flow information for the application, wherein the session modification request message includes at least one second action rule associated with the second PDR, and wherein the appID and the flow information are different.

18. The method of Claim 17, wherein the session modification request message includes an indication to apply policy consolidation.

19. The method of Claim 18 further comprising: receiving (8301) an association request message from the second CN node, wherein the association request message includes an indication that the second CN node supports policy consolidation; wherein the session modification request message includes the indication to apply policy consolidation responsive to the association request message including the indication that the second CN node supports policy consolidation.

20. The method of any of Claims 18-19, wherein the indication to apply policy consolidation is a second indication to apply policy consolidation, the method further comprising: receiving (8321) a policy control update request message from a third CN node, wherein the policy control update request message includes a Policy and Charging Control, PCC, rule of the policy control update request message, wherein the PCC rule of the policy control update request message includes the flow information for the application, and a first indication to apply policy consolidation; wherein the session modification request message includes the second indication to apply policy consolidation responsive to the policy control update request message including the first indication to apply policy consolidation, wherein the second PDI of the session modification request message includes the flow information for the application responsive to the PCC rule of the policy control update request message including the flow information for the application, and wherein the at least one second action rule associated with the second PDR is generated based on the PCC rule of the policy control update request message.

21. The method of Claim 20, wherein the PCC rule of the policy control update request message includes sponsor information indicating that application traffic associated with the second PDR is sponsored so that application traffic is not charged against a quota of data

38 associated with the communication device, and wherein the at least one second action rule includes a usage reporting rule, URR, associated with the second PDR indicating that application traffic associated with the second PDR is sponsored responsive to the PCC rule of the policy control update request message including the sponsor information indicating that application traffic associated with the second PDR is sponsored.

22. The method of any of Claims 20-21, wherein the at least one second action rule comprises a forwarding action rule, FAR, associated with the second PDR, wherein the FAR associated with the second PDR is generated based on the PCC rule of the policy control update request message.

23. The method of any of Claims 20-22, wherein the at least one second action rule comprises a quality of service enforcement rule, QER, associated with the second PDR, wherein the QER associated with the second PDR is generated based on the PCC rule of the policy control update request message.

24. The method of any of Claims 20-23 further comprising: receiving (8309) a policy control create message from the third CN node, wherein the policy control create message includes a Policy and Charging Control, PCC, rule of the policy control create message, wherein the PCC rule of the policy control create message includes the appID for the application; wherein the first PDI includes the appID responsive to the PCC rule of the policy control create message including the appID, and wherein the at least one first action rule associated with the first PDR is generated based on the PCC rule of the policy control create message.

25. The method of Claim 24, wherein the at least one first action rule includes a usage reporting rule, URR, associated with the first PDR, wherein the URR associated with the first PDR indicates that application traffic associated with the first PDR is charged against a quota of data associated with the communication device, and wherein the URR associated with the first PDR is generated based on the PCC rule of the policy control create message.

39

26. The method of any of Claims 24-25, wherein the PCC rule of the policy control create message includes Quality of Service, QoS, information for the application, and wherein the at least one first action rule associated with the first PDR is generated based on the QoS information for the application.

27. The method of Claim 26, wherein the at least one first action rule includes a Quality of Service Enforcement Rule, QER, associated with the first PDR, wherein the QER associated with the first PDR is generated based on the QoS information.

28. The method of any of Claims 24-27, wherein the at least one first action rule includes a forwarding action rule, FAR, associated with the first PDR, wherein the FAR associated with the first PDR is generated based on the PCC rule of the policy control create message.

29. The method of any of Claims 24-28 further comprising: receiving (8304) a session create message from a fourth CN node, wherein the session create message relates to session establishment for the communication device; and transmitting (8305) a policy control create request message to a third CN node, wherein the policy control create request message is transmitted responsive to receiving the session create message; wherein the policy control create message is a policy control create response message corresponding to the policy control create request message.

30. The method of Claim 29, wherein the fourth CN node comprises an Access and Mobility Management Function, AMF, node.

31. The method of any of Claims 20-30, wherein the third CN node comprises at least one of a Policy Control Function PCF node and/or a Policy and Charging Rule Function PCRF node.

32. The method of any of Claims 17-31, wherein the flow information for the application includes at least one of a source Internet Protocol, IP, address for the communication device, a

40 source port for the communication device, a destination IP address for the application server, a destination port for the application server, and/or an indication of an IP protocol.

33. The method of any of Claims 17-32, wherein the flow information is omitted from the session establishment request message, and/or wherein the appID is omitted from the session modification request message.

34. The method of any of Claims 17-33, wherein the first CN node comprises one of a session management function, SMF, node, a PDN Gateway Control plane function, PGW-C, node and/or a Traffic Detection Function Control plane function, TDF-C, node, and wherein the second CN node comprises one of a user plane function, UPF, node, a PDN Gateway User plane function, PGW-U, node and/or a Traffic Detection Function User plane function, TDF-U, node.

35. A method of operating a first core network, CN, node, the method comprising: transmitting (9309) a policy control create message for a communication device to a second core network, CN, node, wherein the policy control create message includes a Policy and Charging Control, PCC, rule of the policy control create message, wherein the PCC rule of the policy control create message includes an application identifier, appID, for an application supported by an application server; and transmitting (9321) a policy control update request message for the communication device to the second CN node, wherein the policy control update request message includes a PCC rule of the policy control update request message, and wherein the PCC rule of the policy control update request message includes flow information for the application and an indication to apply policy consolidation for application traffic between the communication device and the application server.

36. The method of Claim 35 further comprising: receiving (9305) a policy control create request message from the second CN node, wherein the policy control create request message relates to session establishment for the communication device;

41 wherein the policy control create message is a policy control create response message that is transmitted responsive to receiving the policy control create request message.

37. The method of Claim 36 further comprising: transmitting (9306) a query request message to a third CN node responsive to receiving the policy control create request message; and receiving (9307) a query response message from the third CN node, wherein the query response message corresponds to the query request message, wherein the query response message comprises subscriber policy data including the appID for the application; wherein the PCC rule of the policy control create message is generated based on the subscriber policy data of the query response message including the appID.

38. The method of Claim 37, wherein the subscriber policy data includes Quality of Service, QoS, information for the application, and wherein the policy control create message includes the QoS information for the application from the query response message.

39. The method of any of Claims 37-38, wherein the third CN node comprises a unified data repository, UDR, node.

40. The method of any of Claims 35-39 further comprising: receiving (9318) a post message from a fourth CN node, wherein the post message includes the flow information for the application and sponsor information indicating that application traffic associated with the application is sponsored so that application traffic associated with the application is not charged against a quota of data associated with the communication device; wherein the PCC rule of the policy control update request message is generated based on the post message.

41. The method of Claim 40, wherein the sponsor information of the post message is first sponsor information, wherein the PCC rule of the policy control update request message includes

42 second sponsor information indicating that application traffic associated with the application is sponsored responsive to the post message including the first sponsor information.

42. The method of Claim 40, wherein the PCC rule of the policy control update request message includes the flow information for the application responsive to the post message including the flow information for the application.

43. The method of any of Claims 40-42, wherein the post message includes an application function identifier, afID, associated with a provider of the application, and an internal identifier associated with the communication device.

44. The method of any of Claims 40-43, wherein the fourth CN node comprises one of a network exposure function, NEF, node and/or a Service Capability Exposure Function, SCEF, node.

45. The method of any of Claims 35-44, wherein the first CN node comprises one of a Policy Control Function, PCF, node and/or a Policy and Charging Rule Function, PCRF, node, and wherein the second CN node comprises one of a session management function, SMF, node, a PDN Gateway Control plane function, PGW-C, node and/or a Traffic Detection Function Control plane function, TDF-C, node.

46. A first core network, CN, node (600) comprising: processing circuitry (603); and memory (605) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the first CN node to perform operations according to any of Embodiments 1-45.

47. A first core network, CN, node (600) adapted to perform according to any of

Embodiments 1-45.

43

48. A computer program comprising program code to be executed by processing circuitry (403) of a first core network, CN, node (600), whereby execution of the program code causes the first CN node (600) to perform operations according to any of embodiments 1-45.

49. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (603) of a first core network, CN, node (600), whereby execution of the program code causes the first CN node (600) to perform operations according to any of embodiments 1-45.

44