[go: up one dir, main page]

WO2021244767A1 - Extension de protocole pfcp liée à un rapport d'événement - Google Patents

Extension de protocole pfcp liée à un rapport d'événement Download PDF

Info

Publication number
WO2021244767A1
WO2021244767A1 PCT/EP2020/073943 EP2020073943W WO2021244767A1 WO 2021244767 A1 WO2021244767 A1 WO 2021244767A1 EP 2020073943 W EP2020073943 W EP 2020073943W WO 2021244767 A1 WO2021244767 A1 WO 2021244767A1
Authority
WO
WIPO (PCT)
Prior art keywords
upf
smf
application
urr
session
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/EP2020/073943
Other languages
English (en)
Inventor
Miguel Angel Munoz De La Torre Alonso
Carlos JIMENEZ I
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2021244767A1 publication Critical patent/WO2021244767A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/57—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for integrated multimedia messaging subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/62—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/852—Low balance or limit reached
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/853—Calculate maximum communication time or volume
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/854—Available credit
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information

Definitions

  • 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.
  • Figure 1 depicts the 3GPP reference architecture for 5G
  • Figure 2 depicts the 3GPP 5GC reference architecture for policy, charging and analytics.
  • the Charging Function supports offline and/or online charging functionality and exhibits a Nchf interface towards the consumers (e.g. SMF).
  • PCF Policy Control Function
  • PCF Policy Control Function
  • PCC Policy and Charging Control
  • SMF Session Management Function
  • the Session Management function 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.
  • 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:
  • UPF User Plane Function
  • the User Plane function 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).
  • PDRs packet inspection
  • QoS QoS
  • Charging/Reporting through FARs, QERs, URRs.
  • 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.
  • 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.
  • event-based charging for a certain application e.g. MMS
  • number of events detected within an application session e.g. the number of recipients.
  • 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.
  • PDR(s) with the PDI set to an Application ID (e.g. MMS)
  • 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.
  • the corresponding logic e.g. online/offline charging towards CHF including MMS recipient information
  • 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.
  • 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.
  • 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.
  • 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.
  • the SMF is capable of selecting UPF ' s that support extended URR reports.
  • 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.
  • 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.
  • 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.
  • 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.
  • the application is a Video and/or Audio conference application
  • 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.
  • the application is a Video and/or Audio streaming application
  • 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.
  • the application is an email application
  • 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.
  • 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
  • SMF Session Management Function
  • the SMF is additionally adapted to trigger events-based reporting and event-based charging to the CHF based on the URR detailed event reporting.
  • the URR reports include detailed event reporting to the SMF, and the detailed event reporting further comprises data identifying an Application protocol.
  • 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.
  • PCF Policy Control Function
  • UDR User Data Repository
  • 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.
  • 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.
  • the Create URR IE includes: an event measurement method, a reporting trigger and an event threshold.
  • 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.
  • 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.
  • 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.
  • 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.
  • the Application is a Video and/or Audio streaming Application
  • 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.
  • 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.
  • a UP, User Plane function include the capability of detailed event reporting DEVU (highlighted in bold), that might be coded in the following form:
  • 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):
  • 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.
  • 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.
  • Audio/Video conference applications e.g. Skype
  • Audio/Streaming applications e.g. Spotify, Netflix, YouTube
  • Email applications e.g.
  • Steps (1 to 19) of the sequence are shown in Figure 3A, and Step (20) of the sequence is shown in Figure 3B.
  • 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.
  • 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.
  • DEVU Detailed Event Reporting
  • 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.
  • 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.
  • the subscriber policy profile response indicates that MMS charging based on the number of recipients, is to be enabled for that subscriber.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • the UPF then transmits to the SMF in Step (10) a PFCP session establishment response.
  • 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:),
  • an Application message e.g. a MMS message
  • M>N a certain number of message recipients
  • the UPF Upon receiving the message, the UPF detects the MO Application message and analyzes it (Step 12).
  • 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).
  • 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.
  • 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.
  • Recipient- Info includes at least the number of recipients (M) and optionally each recipient address (e.g. the GPSI of each recipient).
  • Audio/Video conference applications e.g. Skype
  • 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.
  • o Number of Events 1 (1 event, corresponding to 1 Skype session)
  • o Event Detailed Information includes:
  • 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.
  • M the number of parties
  • Audio/Video streaming applications e.g. Spotify, Netflix, YouTube
  • 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).
  • UPF could detect if the user is just browsing through the Netflix movie catalogue or if the user is watching a movie.
  • 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:
  • Start (indicates the user has requested a streaming session to start)
  • the above events also include a timestamp.
  • Email applications e.g. using SMTP and IMAP protocols
  • charging applies based on the number of emails sent and the number of recipients.
  • 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.
  • 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).
  • FIG. 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.
  • a SMF 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).
  • the SMF device (100) is the one defined for
  • FIG. 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.
  • 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,
  • 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).
  • a UPF is the UPF (200) described for

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne des réseaux de communication 4G ou 5G centraux par paquets, et en particulier, la notification et la facturation. L'invention concerne un dispositif à fonction plan utilisateur UP (200) et un procédé dans lequel les événements générés pendant une session d'application sont détectés, et au moins un rapport détaillé de règle de reporting d'utilisation ou URR est généré, lequel comprend des données relatives au nombre d'événements détectés par l'UPF dans une session, et le rapport URR détaillé est transmis à une fonction de gestion de session SMF. L'invention concerne également un dispositif à fonction de gestion de session SMF (100) et un procédé dans lequel des rapports détaillés de règle de reporting d'utilisation ou URR sont reçus au niveau du SMF, lesquels comprennent des données relatives au nombre d'événements détectés par une UPF dans une session d'application, et la SMF déclenche une demande de facturation vers une fonction de facturation CHF d'après le rapport URR détaillé. L'invention concerne également un réseau de communication qui comprend les dispositifs UPF et SMF.
PCT/EP2020/073943 2020-06-01 2020-08-27 Extension de protocole pfcp liée à un rapport d'événement Ceased WO2021244767A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP20382464.4 2020-06-01
EP20382464 2020-06-01

Publications (1)

Publication Number Publication Date
WO2021244767A1 true WO2021244767A1 (fr) 2021-12-09

Family

ID=70977907

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2020/073943 Ceased WO2021244767A1 (fr) 2020-06-01 2020-08-27 Extension de protocole pfcp liée à un rapport d'événement

Country Status (1)

Country Link
WO (1) WO2021244767A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119497065A (zh) * 2024-11-13 2025-02-21 南京邮电大学 基于改进的pfcp协议的用户终端位置信息传递方法

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003094534A2 (fr) * 2002-05-06 2003-11-13 Telefonaktiebolaget Lm Ericsson (Publ) Services de messagerie multimedia multiutilisateur

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003094534A2 (fr) * 2002-05-06 2003-11-13 Telefonaktiebolaget Lm Ericsson (Publ) Services de messagerie multimedia multiutilisateur

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Interface between the Control Plane and the User Plane Nodes; Stage 3 (Release 16)", vol. CT WG4, no. V16.3.1, 3 April 2020 (2020-04-03), pages 1 - 297, XP051893770, Retrieved from the Internet <URL:ftp://ftp.3gpp.org/Specs/archive/29_series/29.244/29244-g31.zip 29244-g31.docx> [retrieved on 20200403] *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control framework for the 5G System (5GS); Stage 2 (Release 16)", vol. SA WG2, no. V16.4.1, 6 April 2020 (2020-04-06), pages 1 - 115, XP051893851, Retrieved from the Internet <URL:ftp://ftp.3gpp.org/Specs/archive/23_series/23.503/23503-g41.zip 23503-g41.docx> [retrieved on 20200406] *
"OMA Mobile_Email Charging Specification ; OMA-TS-Mobile_Email_Charging-V1_0-20090506-D", no. 1.0, 6 May 2009 (2009-05-06), pages 1 - 20, XP064008010, Retrieved from the Internet <URL:ftp/Public_documents/ARCH/ARC-MEM_Charging/Permanent_documents/> [retrieved on 20090507] *
HUAWEI: "Number of occurrences for an event", vol. CT WG4, no. E-Meeting; 20200818 - 20200828, 25 August 2020 (2020-08-25), XP051921785, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ct/WG4_protocollars_ex-CN4/TSGCT4_99e_meeting/Docs/C4-204399.zip C4-204399 was 4166 TEI16 29.244-Event Amount.docx> [retrieved on 20200825] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119497065A (zh) * 2024-11-13 2025-02-21 南京邮电大学 基于改进的pfcp协议的用户终端位置信息传递方法

Similar Documents

Publication Publication Date Title
US10575146B2 (en) Method and apparatus relating to online charging in an IP multimedia subsystem
CN102098649B (zh) 基于策略计费控制系统的增值业务处理方法、装置及系统
RU2435205C2 (ru) Способ законного перехвата информации и устройство для этого
US9344580B2 (en) Charging for short message delivery
US8965962B2 (en) Diameter session audits
US8995305B2 (en) Sy session creation and recovering from inconsistent session state between PCRF and OCS
US10244032B2 (en) Reducing application detection notification traffic
US20130322365A1 (en) Methods and apparatus for mitigating service interruption
EP2003917A9 (fr) Procédé et système de décision concernant l&#39;information sur les services dans un système de communication mobile
TW201004431A (en) Charging in LTE/EPC communication networks
CN107743714A (zh) 对基于商业群组的消息传送计费
EP2314039B1 (fr) Système de communication
EP2716083B1 (fr) Procédé et appareil de charge dans un réseau de communication
US20150189097A1 (en) Vectored charging data record (cdr) reconciliation
US9820183B2 (en) User plane congestion control
WO2021244767A1 (fr) Extension de protocole pfcp liée à un rapport d&#39;événement
CN102918804B (zh) 策略控制方法、装置以及通信系统
KR101362502B1 (ko) 아웃바운드 메시지의 실패 관리를 위한 프레임워크
WO2008148355A1 (fr) Procédé, système et appareil de facturation
US9420059B2 (en) Indication of authorized and unauthorized PCC rules
WO2011127666A1 (fr) Procédé, dispositif et système de traitement pour un prélèvement
US20090041014A1 (en) Obtaining Information From Tunnel Layers Of A Packet At A Midpoint
US12328290B2 (en) Using commercially available user devices for MMS messaging capacity testing
KR102092877B1 (ko) 에러 코드 처리 방법 및 장치
CN103856925A (zh) 一种基于移动通信网络的计费管理方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20760481

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20760481

Country of ref document: EP

Kind code of ref document: A1