WO2021244767A1

WO2021244767A1 - Pfcp protocol extension related to event reporting

Info

Publication number: WO2021244767A1
Application number: PCT/EP2020/073943
Authority: WO
Inventors: Miguel Angel Munoz De La Torre Alonso; Carlos JIMENEZ I
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2020-06-01
Filing date: 2020-08-27
Publication date: 2021-12-09
Anticipated expiration: 2022-12-01

Abstract

The disclosure relates to Packet Core 4G or 5G communication networks, and in particular, it relates to reporting and charging.The disclosure refers to UPF, User Plane Function, (200) device and method wherein events generated during an application session are detected, and at least one extended URR, Usage Reporting Rule, report is generated that includes data relative to the number of events detected by the UPF within a session, wherein the extended URR report is forwarded to a SMF, Session Management Function. The disclosure also refers to a SMF, Session Management Function, (100) device and method, wherein extended URR, Usage Reporting Rule, reports are received at the SMF that include data relative to the number of events detected by a UPF within an application session, and wherein the SMF triggers a charging request to an CHF, Charging Function, based on the extended URR report. The disclosure also refers to a communication network that comprises the UPF and SMF devices.

Description

PFCP PROTOCOL EXTENSION RELATED TO EVENT REPORTING

Technical field

The present disclosure relates to Packet Core in 4G and 5G communication networks, and specifically to Policy (traffic analysis, classification and charging/reporting). In particular, this disclosure relates to reporting and charging in 5G networks.

Background

Figure 1 depicts the 3GPP reference architecture for 5G, and Figure 2 depicts the 3GPP 5GC reference architecture for policy, charging and analytics.

Some architectural functions involved in those reference architectures are:

• CHF (Charging Function),

• PCF (Policy Control Function),

• SMF (Session Management Function),

• UPF (User Plane Function).

CHF (Charging Function):

The Charging Function (CHF) supports offline and/or online charging functionality and exhibits a Nchf interface towards the consumers (e.g. SMF).

PCF (Policy Control Function):

The Policy Control Function (PCF) supports unified policy framework to govern the network behavior. Specifically, PCF provides PCC (Policy and Charging Control) rules to the SMF.

SMF (Session Management Function):

The Session Management function (SMF) supports different functionalities, e.g. Session Establishment, modify and release, and policy related functionalities like termination of interfaces towards Policy control functions, Charging data collection, support of charging interfaces and control and coordination of charging data collection at UPF. Specifically, SMF receives PCC rules from PCF and configures UPF accordingly through N4 reference point (PFCP protocol) as follows:

• SMF controls the packet processing in the UPF by establishing, modifying or deleting PFCP Sessions and by provisioning (i.e. adding, modifying or deleting) PDRs, FARs, QERs and/or URRs per PFCP session, whereby a PFCP session may correspond to an individual PDU session or a standalone PFCP session not tied to any PDU session.

• Each PDR contains a PDI specifying the traffic filters or signatures against which incoming packets are matched. Each PDR is associated to the following rules providing the set of instructions to apply to packets matching the PDI:

• one FAR, which contains instructions related to the processing of the packets, specifically forward, duplicate, drop or buffer the packet with or without notifying the CP function about the arrival of a DL packet.

• zero, one or more QERs, which contains instructions related to the QoS enforcement of the traffic;

• zero, one or more URRs, which contains instructions related to traffic measurement and reporting.

UPF (User Plane Function):

The User Plane function (UPF) supports handling of user plane traffic based on the rules received from SMF, specifically for this disclosure, packet inspection (through PDRs) and different enforcement actions, e.g. traffic steering, QoS, Charging/Reporting (through FARs, QERs, URRs).

For event-based reporting, the SMF may provision:

- Event Threshold IE, to request the UP function to generate a usage report when the number of events reaches the event threshold;

- Event Quota IE, to request the UPF to stop forwarding packets applicable to the event (or only allow forwarding of some limited user plane traffic, based on operator policy in the UPF) and, if no Event threshold is provisioned, to also generate a usage report, when the number of events reaches the event quota; An event is preconfigured with one or more event detection logic in the UPF. Each event detection logic is associated with an Application ID. The SMF activates the detection and reporting of an event by provisioning PDR(s) with the PDI set to an Application ID and by provisioning a URR with an event threshold or event quota reporting trigger. The SMF identifies an event reported in a Usage Report by the URR ID.

Problems of current technology

The 3GPP TS 29.244 specifies the PFCP protocol, specifically event-based reporting but it has the following problems: · When event-based reporting is enabled, and UPF detects and reports the corresponding events to the SMF, the information included in the URR is not detailed enough. For example, for MMS event-based charging based on the number of recipients, and with a reporting threshold of N events: o URR does not indicate the number of events detected (e.g. the detection by UPF of a single MMS with M>N events implies triggering a

URR report, but it is currently not possible to indicate SMF that M events have been detected). This would lead to incorrect charging. o URR does not indicate any detail on the events detected (e.g. it is not possible for SMF to discriminate if the event report refers to a single MMS with X recipients or X MMS with a single recipient). Additionally, in an MMS, the recipients can be included in different MMS fields (To, Cc and Bcc), so it is not possible for SMF to discriminate to which MMS field each event refers to.

• The same issue applies for other applications, e.g. o Audio/Video conference applications (e.g. Skype), where charging applies based on the number of invited parties of the multi-party session. Furthermore, it is also not possible for SMF (and the Charging System) to differentiate if the Skype session is IM, Video and/or Voice. o Audio/Video streaming applications (e.g. Spotify, Netflix, YouTube), where charging applies based on audio or video content watched either partially or completely. It is not possible for SMF (and the Charging System) to differentiate between the above situations. For example, for HTTP Audio/Video streaming, it is currently not possible to indicate if the event relates to the start of a transaction (e.g. first packet of HTTP GET), to the completion of a transaction (last packet of HTTP 200 OK), or when receiving HTTP responses (first packet of 200 OK response). o Email applications (e.g. using SMTP and IMAP protocols), where charging applies based on the number of emails sent and the number of recipients. It is not possible for SMF (and the Charging System) to retrieve detailed information to apply charging correctly.

Accordingly, it has been detected the need in this technical field, for detailed event reporting that enables a network operator to correctly charge network subscribers.

Summary

The combination of features described in the accompanying independent claims solve the above-described drawbacks of the existing technology, by extending a protocol for packets flow control, preferably the PFCP protocol, specifically by adding an Event Measuring IE in the URR for event-based reporting.

Therefore, the present disclosure comprises the following functionalities:

- At operator^'s network, event-based charging for a certain application (e.g. MMS) based on number of events detected within an application session (e.g. the number of recipients).

- For each PFCP session, SMF activates the detection and reporting of events by provisioning PDR(s) with the PDI set to an Application ID (e.g. MMS) and by provisioning a URR with an event threshold and/or event quota reporting trigger. - UPF analyzes traffic for the PFCP session (which matches the corresponding PDRs) and detects the corresponding events (e.g. a certain number of MMS messages sent by the user, each including a certain number of recipients). If the reporting conditions are met, UPF reports the detected events in a extended URR report that includes an Event Measurement IE with the detected number of events and optionally with events details.

- SMF receives the extended URR report from UPF and applies the corresponding logic (e.g. online/offline charging towards CHF including MMS recipient information) based on the extended URR.

More specifically, an aspect of this disclosure refers to a UPF, User Plane Function, device adapted to detect events generated during an application session, and to generate at least one extended URR, Usage Reporting Rule, report that includes data relative to the number of events detected by the UPF within a session. The UPF is adapted to forward the at least one extended URR report to a SMF, Session Management Function.

The UPF is further adapted to trigger a protocol association request to the SMF, and to report to the SMF its capabilities for generating extended URR reports. Preferably, the protocol is a PFCP, Packet Flow Control Protocol.

The UPF device is further adapted to receive and process a protocol session establishment request from the SMF to carry out a PDU, Protocol Data Unit, session establishment, wherein the request includes at least one URR containing an event threshold (N).

The UPF device is further adapted to analyze application traffic originated at a UE, User Equipment, and to detect events and determine whether a predefined event threshold (N) has been reached, and if so, triggering a Protocol Session Report Request to the SMF. The Session Report Request comprises an extended URR report that includes the number of events detected.

The term UE, refers to a device for instance used by a person, the user, for his or her personal communication as a subscribed of a communication network. It can be a telephone type of device, for example a telephone or a cellular telephone, a mobile station, cordless phone, or a personal digital assistant type of device like laptop, notebook, notepad, tablet equipped with a wireless connection.

Another aspect of the disclosure, refers to a SMF, Session Management Function, device adapted to receive extended URR, Usage Reporting Rule, reports that include data relative to the number of events detected by a UPF within an application session, and to trigger a charging request to an CHF, Charging Function, based on the extended URR report.

The SMF is further adapted to carry out a protocol association with at least one UPF, during which the SMF detects the capabilities of at least one UPF to generate extended URR reports. In this way, the SMF is capable of selecting UPF^'s that support extended URR reports. Preferably, the protocol is a PFCP, Packet Flow Control Protocol.

The SMF is further adapted to retrieve from a UDR, User Data Repository, subscriber policy profile that includes data indicating that a subscriber has to be charged for application session based on extended URR reports that includes data relative to the number of events detected by the UPF.

The SMF device can be configured with PCC rules for at least one application, wherein the PCC rules include data for the extended reporting and charging based on the number of detected events.

Another aspect of the disclosure refers to a method performed by an UPF, User Plane Function, wherein the method comprises the step of detecting events generated during an application session, and generating at least one extended URR, Usage Reporting Rule, report that includes data relative to the number of events detected by the UPF within a session. The method additionally includes forwarding the at least one extended URR report to a SMF, Session Management Function.

Additionally, in the method the UPF triggers a protocol association request to the SMF, during which the UPF reports to the SMF its capabilities for generating extended URR reports. Preferably, the protocol is a PFCP, Packet Flow Control Protocol. The method further comprises the step of receiving and processing in the UPF a session establishment request from the SMF to carry out a PDU, Protocol Data Unit, session establishment, wherein the request includes at least one URR containing an event threshold (N).

The UPF additionally detects events originated at a UE, User Equipment, and analyzes the events as to determine whether a predefined event threshold has been reached, and if so, triggering with the UPF a Protocol Session Report Request to the SMF, the Session Report Request including an extended URR report that includes the number of events detected.

Another aspect of the disclosure refers to a method performed by a SMF, Session Management Function, that comprises the steps of: receiving at least one extended URR, Usage Reporting Rule, report that includes data relative to the number of events detected by a UPF within an application session, and triggering a charging request to an CHF, Charging Function, based on the extended URR report.

A protocol association between the SMF and the UPF is carrying out, during which the SMF identifies the capabilities of the UPF to generate extended URR reports.

The SMF retrieves from a UDR, User Data Repository, a subscriber policy profile that includes data indicating that that subscribed has to be charged for application session based on the extended URR report.

PCC rules for at least one application are installed in the SMF, wherein the PCC rules include data for the extended reporting and charging based on the number of detected events.

In a preferred embodiment of the UPF and/or the SMF devices and methods described above, the application is a MMS, Multimedia Message Service, and an event is a MMS message. The extended URR report and charging are based on data relative to the number of recipients of a message, or data relative to the number of recipients of a message and message recipients addresses.

In a preferred embodiment of the UPF and/or the SMF devices and method described above, the application is a Video and/or Audio conference application, and an event is a Video and/or Audio conference session. The extended URR report and charging are additionally based on the number of invited parties to the conference, or it is based on the number of invited parties to the conference and the invited parties addresses.

In a preferred embodiment of the UPF and/or the SMF devices and method described above, the application is a Video and/or Audio streaming application, and the event is a Video and/or Audio streaming session. The extended URR report and charging are additionally based on audio or video content watched either partially or completely, or it is based on audio or video content watched either partially or completely and predefined packets of a transaction.

In a preferred embodiment of the UPF and/or the SMF devices and method described above, the application is an email application, and an event is an email message. The extended URR report and charging are based on the number of emails sent and the number of recipients, or it based on the number of emails sent and the number of recipients and the recipients addresses.

Another aspect of this disclosure refers to a network apparatus that comprises at least one processor, and at least one memory operatively communicated with the processor. The memory includes a computer program code adapted such that when computer program is run on the processor, the computer program causes the apparatus to, at least, perform SMF method steps.

Another aspect of this disclosure refers to a network apparatus that comprises at least one processor, and at least one memory operatively communicated with the processor. The memory includes a computer program code adapted such that when computer program is run on the processor, the program causes the apparatus to, at least, perform the UPF method.

The disclosure also refers to a computer program product comprising a computer readable code, which when run in the UPF, User Plane Function, device defined above causes the UPF to perform the steps of the above-defined UPF method. The disclosure also refers to a computer program product comprising a computer readable code, which when run in the SMF, Session Management Function, device defined above causes the SMF to perform the steps of the above-defined SMF method.

Another aspect of the disclosure refers to a communication network that comprises a CHF, Charging Function, for charging network subscribes, and a SMF, Session Management Function, adapted to manage application sessions, and additionally adapted to trigger charging to the CHF. Furthermore, the CHF is adapted to charge subscribers for an application session based on extended URR report forwarded by the SMF, that include data relative to the number of events detected for the session.

The communication network, preferably is a 4G or 5G communication network, that supports a PFCP, Packet Flow Control Protocol, and additionally comprises an UPF, User Plane Function, adapted to detect events associated with an Application, and to generate URR, Usage Reporting Rule, reports that include detailed event reporting. In addition, the detailed event reporting comprises data relative to the number of events detected by the UPF within a PFCP session. In this way, a network operator could support event-based reporting and correct charging.

The CHF, Charging Function, is adapted for offline and/or online charging, and the SMF, Session Management Function, is adapted to manage PFCP sessions. The SMF is additionally adapted to trigger events-based reporting and event-based charging to the CHF based on the URR detailed event reporting.

In a preferred embodiment, the URR reports include detailed event reporting to the SMF, and the detailed event reporting further comprises data identifying an Application protocol.

Furthermore, the UPF is further adapted to trigger a PFCP association request to the SMF, and the association request includes data relative to the UPF capabilities for detailed event reporting.

The communication network further comprises a PCF, Policy Control Function, and a UDR, User Data Repository, such that the PCF is adapted to provide to the SMF as a response to a session establishment request from a UE, User Equipment, for a PDU, Protocol Data Unit, Policy and Charging Control Rules, PCC, and to retrieve from the UDR a subscriber policy profile that includes data for the detailed event reporting relative to an Application.

Furthermore, the PCF is further adapted to install in the SMF, a PCC rules for at least one application, and wherein the PCC rules include data for the detailed event reporting and the detailed event charging. The SMF is further adapted to trigger a PFCP, Packet Flow Control Protocol, Session Establishment request to the UPF, to provision the PDRs, Packet Detection Rule for a PDU session, and to provision a URR with an event threshold and/or event quota reporting trigger. The SMF is additionally adapted to provision a UL (Uplink) / DL (Downlink) PDR associated to a URR with detailed event reporting enabled.

In a preferred embodiment, the PFCP protocol includes a detailed event reporting flag in the Measurement Information Element, IE, at the PFCP Session Establishment/Modification Request in the Create/Update URR IE. Preferably, the Create URR IE includes: an event measurement method, a reporting trigger and an event threshold.

Furthermore, the UPF is additionally adapted to detect events originated at a UE, and if the detailed event reporting flag is enabled, the UPF analyzes events details as to determine whether the event threshold has been reached, and if so, the UPF is adapted to trigger a PFCP Session Report Request to the SMF. In addition, the PFCP Session Report Request includes a URR report containing detailed event reporting.

The SMF is further adapted to trigger an online or offline charging request including detailed event reporting to the CHF, and the CHF is adapted to charge a subscriber based on the detailed event reporting that comprises the detected number of events within a session.

In a preferred embodiment, the Application is a MMS, Multimedia Message Service, and the events are MMS messages. The detailed event charging is additionally based on: data relative to the number of recipients of a MMS message, or data relative to the number of recipients of a MMS message and MMS message recipients addresses. In another preferred embodiment, the Application is a Video and/or Audio conference application, and the events are Video and/or Audio conference sessions. The detailed event charging is additionally based on: the number of invited parties to the conference, or alternatively it is based on the number of invited parties to the conference and the invited parties addresses.

In another preferred embodiment, the Application is a Video and/or Audio streaming Application, and the events are Video and/or Audio streaming sessions. The detailed event charging is additionally based on: audio or video content watched either partially or completely, or alternatively it is based on audio or video content watched either partially or completely and when partially, include the percentage of completion.

In another preferred embodiment, the Application is an email application, and the events are email messages. The detailed event charging is additionally based on: the number of emails sent and the number of recipients, or alternatively it is based on the number of emails sent and the number of recipients and the recipients addresses.

In a preferred embodiment, a UP, User Plane function include the capability of detailed event reporting DEVU (highlighted in bold), that might be coded in the following form:

As an example, the proposed protocol extension can be coded as shown below, wherein it has been highlighted in bold at the Application Detection Information IE within Usage Report IE specifically the field “Application Specific Information” (IE):

The present disclosure does not only apply to 5G network architectures, but the same mechanisms can be applied to 4G, just by replacing:

- PCF by PCRF 0 - SMF by PGW-C or TDF-C

- UPF by PGW-U or TDF-U.

Some advantages of above-described disclosure are the followings: - It allows a network operator to properly support event-based reporting, for which current technology has some relevant limitations that may lead to incorrect charging.

- In addition, it allows a network operator to support extra Use Cases (not related with event-based reporting or charging), specifically to report Application specific information which is not supported by existing technologies.

- It reduces energy consumption at nodes equipment.

Brief description of the drawings

The disclosure is now described, by way of example, with reference to the accompanying figures, wherein:

Figure 1.- shows a 5G Network Architecture, according to the prior-art.

Figure 2.- shows a 3GPP 5G 5GC Network Architecture for policy, charging and analytics, according to the prior-art.

Figure 3.- shows in Figures A and B, a Sequence Diagram showing the proposed disclosure for event reporting, in the example of the figure for a MMS application. Steps of the sequence are numbered at the left-hand side column.

Figure 4 shows Event Measurement IE encoding according to the present disclosure.

Figure 5.- shows a schematic diagram of the UPF device.

Figure 6.- shows a schematic diagram of the SMF device.

Detailed description

In the following, exemplary embodiments of the disclosure are described with reference to the accompanying drawings. It is to be understood that the following description of embodiments is not to be taken in a limiting sense, and that the scope of the disclosure is not limited by the embodiments described hereinafter or by the drawings, which have a illustrative purpose only.

Figures 3A,3B show the sequence diagram of an exemplary implementation of the present disclosure, that corresponds to the Use Case example of a Multimedia Message Service MMS event-based charging based on the number of recipients, that requires for its implementation the precondition that the MMS charging based on number of recipient’s policy, is pre-configured in UDR as subscriber policy data.

It would be understood that the proposed solution can be also be applied to other Use Cases like: Audio/Video conference applications (e.g. Skype), Audio/Streaming applications (e.g. Spotify, Netflix, YouTube), or Email applications.

The Steps (1 to 19) of the sequence are shown in Figure 3A, and Step (20) of the sequence is shown in Figure 3B.

In Steps (1, 2): a PFCP Association procedure between the UPF and SMF entities is carried out, wherein the UPF report to the SMF its capabilities for detailed event reporting, so that the SMF can takes this information into account when selecting a UPF.

According to the present disclosure the existing mechanism to report UPF capabilities is extended to include the capability for Detailed Event Reporting (DEVU), that allows the SMF to know which UPFs support this capability.

More specifically, in Step (1) the UPF sends to the SMF a PFCP Association request wherein the report of the UPF capabilities includes the DEVU capability, and in Step (2), the SMF responds to the UPF with a PFCP Association request.

In Steps (3 to 10): a PDU Session Establishment triggered by a User Equipment UE is carried out, wherein the SMF is provisioned with a subscriber profile that includes data indicating that that subscribed has to be charged based on detailed event reporting.

In Step (3) a User Equipment UE triggers a PDU Session Establishment procedure to an Access and Mobility Function AMF, which in turn in Step (4) triggers a Namf session create message to the SMF. The SMF then sends in Step (5) a Npcf policy request to a Policy Control Function PCF, which in Step (6) sends a User Data Repository UDR policy profile request to the UDR including a subscriber identifier, and then it retrieves in Step (7), from the UDR the subscriber policy profile response, that according to the present disclosure, indicates that the Application charging should be based on event-based charging for that subscriber, that might include, not only that a threshold has been exceeded, but the number of events detected or measured, and/or details of the events detected that would allow the SMF to discriminate accurately the event reporting.

In the particular example of Figures 3A,3B, the subscriber policy profile response, indicates that MMS charging based on the number of recipients, is to be enabled for that subscriber.

In Step (8): the PCF installs in the SMF, Policy and Charging Control PCC rules for the different applications. Specifically, a PCC rule with application identifier set to MMS will indicate charging based both on the number of MMS messages sent and on the number of recipients. In particular, the PCF forwards a Npcf policy response to the SMF with PCC rules including MMS charging based on number of recipients.

In Step (9): the SMF triggers PFCP Session Establishment request to the UPF to provision the Packet Detection Rules PDRs (and the corresponding enforcement actions: Forwarding Action Rule FARs, Usage Reporting Rules URRs) for the PDU session. Specifically, SMF will provision a (UL/DL) PDR (including a PDR with Packet Detection Information PDI Application, in this case the MMS), URRs (including a URR with event threshold (N) and to report detailed Application information, MMS in this example) associated to a URR with detailed event reporting enabled.

In order to achieve this function, the PFCP protocol is extended by adding a “Detailed event reporting Flag” in a Measurement Information IE element at “PFCP Session Establishment/Modification Request” in “Create/Update URR IE”, such that, this flag is a bit that is set for example to 1 when the detailed event reporting is required.

Additionally, the Create URR IE above includes: o Measurement Method = Event o Reporting Trigger = EVETH (Event Threshold) o Event Threshold = N

The UPF then transmits to the SMF in Step (10) a PFCP session establishment response.

In Steps (11 to 20), the PDU session establishment continues and Application traffic (for a MMS Application in the exemplary embodiment of Figures 3A,3B) messages are exchanged between entities, starting in Step (11) with the mobile originated MO transmission of an Application message (e.g. a MMS message) from the UE to the UPF including a certain number of message recipients (e.g. M>N), (To:, Cc:, Bcc:),

Upon receiving the message, the UPF detects the MO Application message and analyzes it (Step 12). In the example of Figures 3A,3B, the UPF detects the MO MMS message (by matching the PDR with appld=MMS) and, as the Detailed event reporting Flag is enabled in the URR associated to the matched PDR, UPF further analyzes MMS message contents, specifically the MMS header fields (To, Cc, Bcc fields), and it forwards this information (Step 13) to the Application server. Then, the UPF counts (Step 14) the number of recipients (M) and detects whether and event threshold (N) has been reached, and it triggers a URR report. The UPF then forwards in Step (15) a PFCP session report request to the SMF that includes the URR report with the Event measurement IE containing the detailed event information for the Application (e.g. MMS information).

In Step (16) the SMF answers the UPF with a PFCP session report response, and triggers (Step 17) online/offline charging including Application detailed information, in the example of Figures 3A,3B for a MMS Application with the number of MMS messages and recipients information, which is transmitted (Step 18) to the Charging Function CHF as a Nchf charging request. The CHF then sends back to the SMF (Step 19) a Nchf charging response.

Finally, in Step (20) the CHF charges the subscriber based on the detailed event reporting, that in the example of Figures 3A,3B, would be based on both on the number of MMS messages sent and on the number of recipients, such that a subscribed can be charged correctly.

An example of the proposed syntax for the Event Measurement is shown in Figure 4. The Event Measurement IE contains the measured events, and It shall be encoded for example as shown in Figure 4: o Number of Events =1 (1 event, corresponding to 1 MMS message) o Event Detailed Information includes:

[ Protocol ] = MMS [ Number-Of-Messages-Sent ] = 1

* [ Recipient- Info ] includes at least the number of recipients (M) and optionally each recipient address (e.g. the GPSI of each recipient).

The sequence diagram in Figure 3 is just an example for MMS charging based on the number of recipients, but the proposed disclosure applies to any other Application which requires detailed event-based reporting, e.g.:

• Audio/Video conference applications (e.g. Skype), where charging applies based on the number of invited parties of the multi-party session. UPF could detect the number of participants (e.g. by detecting the number of flows towards different destinations) and report them to SMF in the Event Measurement IE. Additionally, UPF could detect if the Skype session relates to IM, Video and/or Voice and report that in the Event Measurement IE.

In this example: o Number of Events =1 (1 event, corresponding to 1 Skype session) o Event Detailed Information includes:

[ Protocol ] = Skype

[ Type-of-Session ] = Audio/Video Conference

* [ Recipient-Info ] includes at least the number of parties (M) and optionally each party address (e.g. the GPSI of each party) • Audio/Video streaming applications (e.g. Spotify, Netflix, YouTube), where charging applies based on audio or video content watched either partially or completely. For example, for HTTP based audio and video streaming (e.g. Netflix), UPF could detect events like the start of a transaction (e.g. first packet of HTTP GET), the completion of a transaction (last packet of HTTP 200 OK), or when receiving HTTP responses (first packet of 200 OK response). Additionally, UPF could detect if the user is just browsing through the Netflix movie catalogue or if the user is watching a movie.

In this example: o Number of Events =1 (1 event, corresponding to 1 Netflix session) o Event Detailed Information includes:

[ Protocol ] = Netflix [ Type-of-Session ] = Video streaming [ Session-Info ] includes one of the following events:

Complete (indicates the streaming session has been completed)

Start (indicates the user has requested a streaming session to start)

Response (indicates the streaming session has just started) The above events also include a timestamp.

• Email applications (e.g. using SMTP and IMAP protocols), where charging applies based on the number of emails sent and the number of recipients. For example, UPF could detect the number of messages sent (e.g. by detecting the number of SMTP MAIL commands), the number of recipients, and report them to SMF in the Event Measurement IE.

In this example: o Number of Events =1 (1 event, corresponding to 1 email) o Event Detailed Information includes:

[ Protocol ] = SMTP [ Number-Of-Messages-Sent ] = 1 * [ Recipient- Info ] includes at least the number of recipients (M) and optionally each recipient address (e.g. the GPSI of each recipient).

The present disclosure also refers to Use Cases not related with event based charging or reporting, and the Application Detection Information IE at Usage Report IE is extended within PFCP Session Report Request, specifically in the case of the “Start of Traffic” event, so e.g. in case of MMS application, the Application Detection Information IE includes the Recipient-Info, to indicate the number of recipients (M) and optionally each recipient address (e.g. the GPSI of each recipient).

Figure 5 shows a schematic diagram of a network apparatus configured as a UPF device (200) according to the present disclosure, that comprises a processor (201), a memory (204) operatively communicated with the processor (201), and including a computer program (203) adapted such that when computer program is run on the processor (201), causes the UPF device (200) apparatus to at least: detect events generated during an application session, generate at least one extended URR, Usage Reporting Rule, report that includes data relative to the number of events detected by the UPF within a session, and to forward the at least one extended URR report to a SMF (100), Session Management Function.

The UPF device (200) preferably includes a first interface (202) for the bidirectional communication with nodes (N3,N6) of a communication network, and a second interface (205) for the bidirectional communication with a SMF device (100) through a network node (N4). Preferably, the SMF device (100) is the one defined for

Figure 6.

Figure 6 shows a schematic diagram of a network apparatus configured as a SMF device (100) according to the present disclosure, that comprises a processor (101), a memory (104) operatively communicated with the processor (101), and including a computer program (103) adapted such that when computer program is run on the processor (101), causes the SMF (100) to at least receive extended URR, Usage Reporting Rule, reports that include data relative to the number of events detected by a UPF within an application session, and to trigger a charging request to an CHF, Charging Function, based on the extended URR report. The SMF device (100) preferably includes a first interface (102) for the bidirectional communication with a communication network, for example by means of a Nsmf inferface, and a second interface (105) for the bidirectional communication with a UPF^'s through a network node (N4). Preferably a UPF is the UPF (200) described for

Figure 5.

ABBREVIATIONS:

Abbreviation Definition

AMF Access and Mobility Management Function

CHF Charging Function

DL Downlink

IE Information Element

FAR Forwarding Action Rule

GPSI Global Public Subscriber Identifier

IM Instant Message

MMS Multimedia Message Service

MO Mobile Originated

NR Next Generation Radio/New Radio

PCC Policy and Charging Control

PCF Policy Control Function

PCRF Policy Control Rules Function

PDR Packet Detection Rule

PDI Packet Detection Information

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

QER QoS Enforcement Rule

QoS Quality of Service

SMF Session Management Function

SMS Short Message Service

UDR Unified Data Repository

UE User Equipment

UL Uplink UP User Plane

UDR User Data Repository,

UPF User Plane Function

URR Usage Reporting Rule

Other preferred embodiments of the present disclosure are described in the appended dependent claims and the multiple combinations of those claims.

Claims

C L A I M S

1.- An UPF, User Plane Function, (200) device adapted to: detect events generated during an application session, generate at least one extended URR, Usage Reporting Rule, report that includes data relative to the number of events detected by the UPF within a session, and forward the at least one extended URR report to a SMF, Session Management Function.

2.- An UPF device according to claim 1, wherein the UPF is further adapted to trigger a protocol association request to the SMF, and to report to the SMF its capabilities for generating extended URR reports.

3.- An UPF device according to claim 1 or 2, further adapted to receive and process a protocol session establishment request from the SMF to carry out a PDU, Protocol Data Unit, session establishment, wherein the request includes at least one URR containing an event threshold (N).

4 An UPF device according to any of the claimsl to 3, further adapted to analyze application traffic originated at a UE, User Equipment, to detect events and to determine whether a predefined event threshold (N) has been reached, and if so, triggering a Protocol Session Report Request to the SMF, wherein the Session Report Request comprises an extended URR report that includes the number of events detected..

5.- An UPF device according to any of the claims 1 to 4, wherein the application is a MMS, Multimedia Message Service, and an event is a MMS message, and wherein the extended URR report includes data relative to the number of recipients of a message, or data relative to the number of recipients of a message and message recipients addresses.

6.- An UPF device according to any of the claims 1 to 4, wherein the application is a Video and/or Audio conference application, and an event is an Video and/or Audio conference session, and wherein the extended URR report includes data relative to the number of invited parties to the conference, or data relative to the number of invited parties to the conference and the invited parties addresses.

7.- An UPF device according to any of the claims 1 to 4, wherein the application is a Video and/or Audio streaming application, and the event is a Video and/or Audio streaming session, and wherein the extended URR report includes data relative to the audio or video content watched either partially or completely, or data relative to audio or video content watched either partially or completely and predefined packets of a transaction.

8.- An UPF device according to any of the claims 1 to 4, wherein the application is an email application, and an event is an email message, and wherein the extended URR report includes data relative to the number of emails sent and the number of recipients, or data relative to the number of emails sent and the number of recipients and the recipients addresses.

9.- An UPF device according to any of the claims 2 to 8, wherein the protocol is a PFCP, Packet Flow Control Protocol.

10.- A SMF, Session Management Function, (100) device adapted to: receive extended URR, Usage Reporting Rule, reports that include data relative to the number of events detected by a UPF within an application session, and to trigger a charging request to an CHF, Charging Function, based on the extended URR report.

11.- A SMF device according to claim 10, further adapted to carry out a protocol association with at least one UPF, wherein the SMF is adapted to detect the capabilities of at least one UPF to generate extended URR reports, and to select UPF^'s that support extended URR reports.

12.- A SMF device according to claim 10 or 11, further adapted to retrieve from a UDR, User Data Repository, subscriber policy profile that includes data indicating that a subscriber has to be charged for application session based on extended URR reports that includes data relative to the number of events detected by the UPF.

13.- A SMF device according to any of the claims 10 to 12, further adapted to be configured with PCC rules for at least one application, wherein the PCC rules include data for the extended reporting and charging based on the number of detected events.

14.- A SMF device according to any of the claims 10 to 13, wherein the application is a MMS, Multimedia Message Service, and an event is a MMS message, and wherein the charging is additionally based on data relative to the number of recipients of a message, or data relative to the number of recipients of a message and message recipients addresses.

15.- A SMF device according to any of the claims 10 to 13, wherein the application is a Video and/or Audio conference application, and an event is an Video and/or Audio conference session, and wherein the charging is additionally based on the number of invited parties to the conference, or it is based on the number of invited parties to the conference and the invited parties addresses.

16.- A SMF device according to any of the claims 10 to 13, wherein the application is a Video and/or Audio streaming application, and the event is a Video and/or Audio streaming session, and wherein the charging is additionally based on audio or video content watched either partially or completely, or it is based on audio or video content watched either partially or completely and predefined packets of a transaction.

17.- A SMF device according to any of the claims 10 to 13, wherein the application is an email application, and an event is an email message, and wherein the charging is additionally based on the number of emails sent and the number of recipients, or it based on the number of emails sent and the number of recipients and the recipients addresses.

18.- A SMF device according to any of the claims 11 to 17, wherein the protocol is a PFCP, Packet Flow Control Protocol.

19.- A method performed by an UPF, User Plane Function, wherein the method comprises: detecting events generated during an application session, generating at least one extended URR, Usage Reporting Rule, report that includes data relative to the number of events detected by the UPF within a session, and forwarding the at least one extended URR report to a SMF, Session Management Function.

20.- A method according to claim 19, comprising the step of triggering with the UPF a protocol association request to the SMF, wherein the UPF reports to the SMF its capabilities for generating extended URR reports.

21.- A method according to claim 19 or 20, comprising the step of receiving and processing in the UPF a session establishment request from the SMF to carry out a PDU, Protocol Data Unit, session establishment, wherein the request includes at least one URR containing an event threshold (N).

22.- A method according to any of the claims 19 to 21, further comprising the step of detecting with the UPF events originated at a UE, User Equipment, and analyzing with the UPF events as to determine whether a predefined event threshold has been reached, and if so, triggering with the UPF a Protocol Session Report Request to the SMF, the Session Report Request including an extended URR report that includes the number of events detected.

23.- A method according to any of the claims 19 to 22, wherein the application is a MMS, Multimedia Message Service, and an event is a MMS message, and wherein the extended URR report includes data relative to the number of recipients of a message, or data relative to the number of recipients of a message and message recipients addresses.

24.- A method according to any of the claims 19 to 22 wherein the application is a Video and/or Audio conference application, and an event is a Video and/or Audio conference session, and wherein the extended URR report includes data relative to the number of invited parties to the conference, or data relative to the number of invited parties to the conference and the invited parties addresses.

25.- A method according to any of the claims 19 to 22 wherein the application is a Video and/or Audio streaming application, and the event is a Video and/or Audio streaming session, and wherein the extended URR report includes data relative to the audio or video content watched either partially or completely, or data relative to the audio or video content watched either partially or completely and predefined packets of a transaction.

26.- A method according to any of the claims 19 to 22 wherein the application is an email application, and an event is an email message, and wherein the extended URR report includes data relative to the number of emails sent and the number of recipients, or data relative to the number of emails sent and the number of recipients and the recipients addresses.

27.- A method according to any of the claims 20 to 26 wherein the protocol is a PFCP, Packet Flow Control Protocol.

28.- A method performed by a SMF, Session Management Function, comprising the steps of: receiving at least one extended URR, Usage Reporting Rule, report that includes data relative to the number of events detected by a UPF within an application session, and triggering a charging request to an CHF, Charging Function, based on the extended URR report.

29.- A method according to claim 28, further comprising the step of carrying out a protocol association between the SMF and the UPF, wherein the SMF identifies the capabilities of the UPF to generate extended URR reports.

30- A method according to claim 28 or 29, further comprising the step of retrieving from a UDR, User Data Repository, a subscriber policy profile that includes data indicating that that subscribed has to be charged for application session based on the extended URR report.

31.- A method according to any of claims 28 to 30, further comprising the step of installing in the SMF, PCC rules for at least one application, wherein the PCC rules include data for the extended reporting and charging based on the number of detected events.

32.- A method according to any of the claims 28 to 31, wherein the application is a MMS, Multimedia Message Service, and an event is a MMS message, and wherein the charging is additionally based on data relative to the number of recipients of a message, or data relative to the number of recipients of a message and message recipients addresses.

33.- A method according to any of the claims 28 to 31, wherein the application is a Video and/or Audio conference application, and an event is an Video and/or Audio conference session, and wherein the charging is additionally based on the number of invited parties to the conference, or it is based on the number of invited parties to the conference and the invited parties addresses.

34.- A method according to any of the claims 28 to 31, wherein the application is a Video and/or Audio streaming application, and the event is a Video and/or Audio streaming session, and wherein the charging is additionally based on audio or video content watched either partially or completely, or it is based on audio or video content watched either partially or completely and predefined packets of a transaction.

35.- A method according to any of the claims 28 to 31, wherein the application is an email application, and an event is an email message, and wherein the charging is additionally based on the number of emails sent and the number of recipients, or it based on the number of emails sent and the number of recipients and the recipients addresses.

36.- A method according to any of the claims 29 to 35, wherein the protocol is a PFCP, Packet Flow Control Protocol.

37.- A communication network comprising: a CHF, Charging Function, for charging network subscribes, a SMF, Session Management Function, adapted to manage application sessions, and additionally adapted to trigger charging to the CHF, and wherein the CHF is adapted to charge subscribers for an application session based on extended URR report forwarded by the SMF, that include data relative to the number of events detected for the session.

38.- A communication network according to claim 37, further comprising at least one UPF, User Plane Function, adapted to detect events associated with an application, and adapted to generate extended URR, Usage Reporting Rule, reports that includes data relative to the number of events detected by the UPF within a session, and wherein the UPF is further adapted to trigger a protocol association request to the SMF, and wherein the association request includes data relative to the UPF capabilities to generate extended URR reports.

39.- A communication network according to claim 37 or 38, further comprising a PCF, Policy Control Function, and a UDR, User Data Repository, wherein the PCF is adapted to provide to the SMF as a response to a session establishment request from a UE, User Equipment, for a PDU, Protocol Data Unit, Policy and Charging Control Rules, PCC, and to retrieve from the UDR a subscriber policy profile that includes data for charging a subscriber based on the number of detected events.

40.- A communication network according to claim 39, wherein the PCF is further adapted to install in the SMF, a PCC rules for at least one Application, and wherein the PCC rules include data for the detailed event reporting and the detailed event charging.

41.- A communication network according to any of the claims 37 to 40, wherein the SMF is further adapted to trigger a PFCP, Packet Flow Control Protocol, Session Establishment request to the UPF, to provision the PDRs, Packet Detection Rule for a PDU session, and to provision a URR with an event threshold and/or event quota reporting trigger.

42.- A communication network according to claim 41 , wherein the PFCP protocol includes a detailed event reporting flag in the Measurement Information Element, IE, at the PFCP Session Establishment/Modification Request in the Create/Update URR IE.

43.- A network system according any of the claims 37 to 42, adapted to operate as a 4G or 5G communication network.

44.- A network apparatus comprising: at least one processor, at least one memory operatively communicated with the processor, and including a computer program code adapted such that when computer program is run on the processor, causes the apparatus to at least perform the method steps defined in any of the claims 19 to 27, or any of the claims 28 to 36.

45.- A computer program product comprising a computer readable code, which when run in a UPF, User Plane Function, device causes the UPF to perform the method steps of any one of the claims 19 to 27.

46.- A computer program product comprising a computer readable code, which when run in a SMF, Session Management Function, device causes the SMF to perform the method steps of any one of the claims 28 to 36.