Support for envelope reporting

Abstract

A method for supporting envelope reporting is proposed in radio communication networks with control plane CP functions that are separate from user plane UP functions. The method is executed in a CP node of a radio communication network and includes: setting (S100) a Time Quota Mechanism (TQM) in a URR (Usage Reporting Rule), the TQM corresponding to a Service Data Stream (SDF) suitable for envelope reporting; setting (S100) at least one report trigger in the URR to instruct a UP (Upgraded User) function to generate a usage report upon envelope closure; setting (S100) a measurement method in the URR to instruct the UP function to collect usage data in terms of quantity, time, and / or events; sending (S110) the set URR to the UP function; receiving (S120) one or more usage reports from the UP function in response to the sent URR, wherein the received usage report includes at least: a usage report trigger set for envelope closure; determining (S130) a start time and / or end time for each envelope based on the received usage report; and storing (S140) each envelope with the determined start time and / or end time for online or offline billing. A CP node, a UP node, a computer program, and a computer program product are also provided.

Description

[0001] This application is a divisional application of the Chinese patent application “Support for Envelope Reporting” with application number 201780093596.6 (filing date is August 1, 2017). Technical Field

[0002] The present invention relates to a method for supporting envelope reporting in a radio communication network, a control plane node supporting envelope reporting in a radio communication network, a user plane node supporting envelope reporting in a radio communication network, a corresponding computer program and a corresponding computer program product. Background Art

[0003] The following describes the requirements for envelope reporting in the 3rd Generation Partnership Project (3GPP), Technical Specification (TS) 32.299.

[0004] 6.5.6 Envelope report

[0005] In addition to the standard quota management provided in Request for Change (RFC) 4006

[402] , the Online Charging Function (OCF) may determine the need for additional detailed reporting that identifies the start and end times of specific activities. The OCF controls this by sending a credit control answer (CCA) with an Envelope-Report attribute-value pair (AVP) with appropriate values. Upon receiving this command, the Charging Trigger Function (CTF) monitors the traffic for the time period controlled by the Quota-Consumption-Time AVP and reports each time period as a single envelope for each quota consumption time expiration for which there is traffic. The OCF can request envelope reports for time only, time and volume, time and number of events, or time and volume and number of events.

[0006] 6.5.7 Combined Quotas

[0007] When granting time-based quotas, the quota consumption time mechanism described in Section 6.5.4 may be extended (and replaced) to potentially provide more efficient use of the online charging interface, i.e. reduced traffic and potentially simpler algorithms in the OCF. The alternative handling mechanisms defined in this section are:

[0008] l. Continuous Time Period (CTP)

[0009] 2. Discrete Time Period (DTP)

[0010] Both DTP and CTP define the time envelope in their own way. The method of forming the time envelope is controlled by the Time Quota Mechanism AVP, which selects the algorithm and the length of the basic time interval.

[0011] The basic interval specified by the basic-interval AVP is the basic unit used to consume quota. The quota is considered to be consumed at the beginning of each basic interval. The CTF shall allow traffic to pass for the duration of the basic interval.

[0012] For DTP, the basic time interval defines the length of the discrete time period. One time envelope corresponds to exactly one DTP (and therefore one basic time interval). Quota consumption is only restored on the first transaction after the DTP expires (or envelope closes).

[0013] For CTP, the mechanism constructs a time envelope from consecutive basic time intervals in which traffic has occurred up to and including the first basic time interval containing no traffic. Therefore, if there was traffic in the previous basic time interval, quota consumption continues within the time envelope. After the envelope is closed, quota consumption is resumed only on the first traffic after the envelope is closed. The envelope of a CTP includes the last basic time interval, i.e. the basic time interval containing no traffic. The end of the envelope can only be determined when looking back.

[0014] If the CTF receives a Multi-Service Credit Control AVP with both the Quota Consumed Time AVP and the Time Quota Mechanism AVP, the Time Quota Mechanism AVP takes precedence and the CTF shall behave accordingly.

[0015] In those cases where quota is consumed in envelopes, if the server requires detailed information on when DTP and CTP occur, the server SHOULD request reporting of the corresponding time envelopes by including the Envelope-Report AVP when granting quota in the CCA(Initial) to indicate whether the client should report the start and end of each time envelope. The CTF generates envelopes according to the above rules and carries each envelope in a separate instance of the Envelope AVP in the Credit Control Request (CCR).

[0016] Assume that this problem is solved by:

[0017] For the control plane (CP) function, time quota measurement (TQM) and envelope reporting provisioning need to be added to the user plane (UP) function:

[0018] TQM to provide CTP or DTP to UP function:

[0019] - For CTP, the time measurement starts from the time when the service occurs until the first time interval that does not contain the service. The time measurement should include the last basic time interval, that is, the basic time interval that does not contain the service. After receiving the subsequent service, the time measurement is resumed through the UP function.

[0020] - For DTP, time measurement shall be resumed on the first transaction after the expiration of the DTP.

[0021] - Envelope reporting to request the UP function to monitor traffic over a time period controlled by the basic time interval included in the Inactivity Detection Time or TQM. The CP function can instruct the UP function to report only time, time and quantity, time and events, or time and quantity and number of events.

[0022] The CP function can request the UP function to report the envelope with the following criteria:

[0023] - If an Inactivity Detection Time is included, the UP function shall report a single envelope per Inactivity Detection Time period for each Inactivity Detection Time expiry where traffic is present.

[0024] - For CTP, the time envelope comprises consecutive basic time intervals in which traffic has occurred, up to and including the first basic time interval containing no traffic.

[0025] - For DTP, the time envelope corresponds exactly to one elementary time interval.

[0026] Some details are also specified for the Information Elements (IEs) used for provision and reporting between the CP function and the UP function:

[0027] 8.2.x2 Envelope Report

[0028] The envelope report should be as follows Figure 8 .2.x2-1 is encoded and is used to indicate to the UP function what needs to be reported by the UP function in the envelope.

[0029] Figure 8 .2.x2-1: Envelope Report

[0030]

[0031] Byte 5 shall be encoded as follows:

[0032] - Bits 1 to 4 indicate the quota that should be reported, as shown in Table 8.2.x2-2.

[0033] - Bits 5 to 8 - are reserved for future use and are set to zero.

[0034] Table 8.2.x2-2: Envelope report values

[0035] The type of quota to be reported Value (decimal) Do not report envelope 0 Report Envelope 1 Use volume to report envelope 2 Reporting Envelopes Using Events 3 Reporting envelopes using volume and events 4 Reserved for future use 5 to 15

[0036] 8.2.x3 Time quota mechanism

[0037] TQM type should be Figure 8 .2.x3-1 is encoded.

[0038] Figure 8 .2.x3-1: Time quota mechanism

[0039] Basic time interval types Value (decimal) CTP 0 DTP 1 Reserved for future use 2 to 3

[0040] As specified in clause 7.2.29 of 3GPP TS 32.299, the basic time interval shall be encoded as Unsigned32.

[0041] The architecture reference of 3GPP TS 23.214 comes from 4.2.1 Non-roaming and roaming architectures.

[0042] This clause defines supplementary aspects of the architectural reference model specified in clause 4.2 of TS 23.401 and clauses 4.2.2 and 4.2.3 of TS 23.402 for interfaces based on the General Packet Radio Service (GPRS) Tunneling Protocol (GTP) when the CP functionality and UP functionality of the Serving Gateway (SGW), Packet Gateway (PGW) and Traffic Detection Function (TDF) are separated.

[0043] For the S2a, S2b, S5 and S8 reference points, the architecture reference model is supported only by GTP-based interfaces. Proxy Mobile IPv6 (PMIP)-based interfaces and S2c interfaces are not supported.

[0044] Figure 1 The architecture reference model is shown in the case where the CP and UP are separated. The architecture reference model covers non-roaming as well as home routing and local breakout roaming scenarios.

[0045] The -C or -U suffix appended to the existing reference points of S2a, S2b, S5 and S8 indicates only the CP and UP components of these interfaces.

[0046] Figure 1The architecture in only describes the case where the CP and UP functions of all SGW, PGW and TDF nodes are separated (split). However, other cases are also supported, in which the CP and UP functions of only one of these nodes are separated while the CP and UP functions of the other interface node are not separated, for example, the control plane and user plane of the PGW are separated, while the control plane and user plane of the SGW are not separated. The separation architecture of the node does not impose any architectural requirements on the peer nodes connected to its interface. TDF is an optional functional entity.

[0047] For roaming architecture with local breakout, a Gx interface is defined between the PGW-C and the Policy and Charging Rules Function (PCRF) in the visited network.

[0048] The architectural reference from 3GPP TS 23.21 is 4.2.2 Combined SGW / PGW architecture.

[0049] The use of combined SGW / PGW as documented in TS 23.401 is still feasible in deployments with separate CP and UP. This functionality can be enabled by adopting a common parameter structure for both non-combined and combined cases to support the Sx interface. Figure 2 An architectural reference model for a combined SGW / PGW in the case where the CP and UP are separated is shown.

[0050] As an example, the PGW-U may be required to perform counting packets and applying Quality of Service (QoS) enforcement per Service Data Flow (SDF), per bearer (aggregation of all SDFs associated with a bearer), and / or per session (aggregation of all SDFs associated with a Packet Data Network (PDN) connection). Summary of the invention

[0051] The object of the present invention is to provide an efficient mechanism to support envelope reporting, wherein the User Plane (UP) functionality is separated from the Control Plane (CP) functionality, keeping the UP functionality 3GPP agnostic.

[0052] According to a first aspect, a method for supporting envelope reporting in a radio communication network having a CP function separated from a UP function is proposed. The method is performed in a CP node of the radio communication network and includes: setting a time quota mechanism (TQM) in a usage reporting rule (URR), and the service data flow (SDF) corresponding to the TQM is applicable to envelope reporting; setting at least one report trigger in the URR to instruct the UP function to generate a usage report when the envelope is closed, and setting a measurement method in the URR to instruct the UP function to collect usage of quantity, time and / or event; sending the set URR to the UP function; receiving one or more usage reports from the UP function in response to the sent URR, wherein the received usage report includes at least: a usage report trigger set as envelope closure; determining the start time and / or end time of each envelope based on the received usage report; and storing each envelope using the determined start time and / or end time for online or offline charging.

[0053] By including the complex envelope mechanism into the CP function, unnecessary information about the envelope mechanism can be avoided from being sent to the UP, making it irrelevant to 3GPP.

[0054] The TQM may include a basic time interval (BTI) and a BTI type, which is either a continuous time period (CTP) or a discrete time period (DTP).

[0055] The method may further include setting an inactivity detection timer IDT in the URR to a quota consumption time (QCT) received from an online charging system (OCS).

[0056] The at least one reporting trigger may be set to envelope closure for the CTP and / or the DTP.

[0057] Determination of the envelope start time may be based on the time of the first packet in each usage report following a received usage report having a usage report trigger set to envelope closure.

[0058] Determination of the envelope end time may be based on a time at which a received usage report having a user report trigger set as envelope closure has been generated.

[0059] According to a second aspect, a method for supporting envelope reporting in a radio communication network having a CP function separated from a UP function is proposed. The method is performed in a UP node of the radio communication network and comprises: receiving a usage reporting rule URR from the CP function, the URR comprising: a TQM and at least one report trigger set to envelope closure; and sending a usage report to the CP function indicating envelope closure.

[0060] The TQM may include a BTI and a BTI type, the BTI type being CTP or DTP. The received URR may include a measurement method, an IDT, and a BTI type being CTP, and wherein the usage report includes: measurements of time, quantity, and / or events as indicated in the received measurement method over a time period containing consecutive BTIs until the IDT expires or when no usage is detected for the BTI. The received URR may include a measurement method and a BTI type being DTP, and wherein the usage report includes: measurements of time, quantity, and / or events as indicated by the received measurement method for each BTI.

[0061] The usage report may include a usage report trigger that is set to be envelope closed.

[0062] According to a third aspect, a CP node is proposed for supporting envelope reporting in a radio communication network having a CP function separated from a UP function. The CP node includes a processor and a computer program product storing instructions, which, when executed by the processor, causes the CP node to: set a TQM in a URR, the service data flow SDF corresponding to the TQM being suitable for envelope reporting; set at least one report trigger in the URR to instruct the UP function to generate a usage report when the envelope is closed; set a measurement method in the URR to instruct the UP function to collect usage of quantity, time and / or event; send the set URR to the UP function; receive one or more usage reports from the UP function in response to the sent URR, wherein the received usage reports at least include a usage report trigger set as envelope closure, determine the start time and / or end time of each envelope based on the received usage reports; and store each envelope with the determined start time and / or end time for online or offline charging.

[0063] TQM can include BTI and BTI type, and BTI type is CTP or DTP.

[0064] The CP node may further be caused to set the inactivity detection timer IDT in the URR to the QCT received from the OCS.

[0065] The at least one reporting trigger may be set to envelope closure for the CTP and / or the DTP.

[0066] Determination of the envelope start time may be based on the time of the first packet in each usage report following a received usage report having said usage report trigger set to envelope closing.

[0067] Determination of the envelope end time may be based on a time at which a received usage report having a user report trigger set as envelope closure has been generated.

[0068] According to a fourth aspect, a UP node is provided for supporting envelope reporting in a radio communication network having a CP function separated from the UP function. The UP node comprises a processor and a computer program product storing instructions, which when executed by the processor causes the UP node to: receive a URR from the CP function, the URR comprising: a TQM and at least one report trigger set to envelope closure; and send a usage report to the CP function indicating envelope closure.

[0069] The TQM may include a BTI and the type of BTI which may be a CTP or a DTP.

[0070] The received URR may include a measurement method, an IDT, and a BTI type that is a CTP, and wherein the usage report includes: measurements of time, quantity and / or events as indicated in the received measurement method over a time period including consecutive BTIs until the IDT expires or when no usage is detected for the BTI.

[0071] The received URR may include a measurement method and a BTI type that is a DTP, and wherein the usage report includes, for each BTI, measurements of time, volume, and / or events as indicated by the received measurement method.

[0072] The usage report may include a usage report trigger that is set to be envelope closed.

[0073] According to a fifth aspect, a CP node is proposed for supporting envelope reporting in a radio communication network having a CP function separated from a UP function. The CP node includes a communication manager and a determination manager, the communication manager being used to: set a TQM in a URR, the service data flow SDF corresponding to the TQM being suitable for envelope reporting; set at least one report trigger in the URR to instruct the UP function to generate a usage report when the envelope is closed; set a measurement method in the URR to instruct the UP function to collect usage of quantity, time and / or event; send the set URR to the UP function; receive one or more usage reports from the UP function in response to the sent URR, wherein the received usage report includes at least a usage report trigger set to envelope closure; and store (S140) each envelope with a determined start time and / or end time for online or offline charging. The determination manager is used to determine the start time and / or end time of each envelope based on the received usage report.

[0074] According to a sixth aspect, a UP node is provided for supporting envelope reporting in a radio communication network having a CP function separated from the UP function. The UP node comprises a communication manager for: receiving a URR from the CP function, the URR comprising a TQM and at least one report trigger set to envelope closure; and for sending a usage report to the CP function to indicate envelope closure.

[0075] According to a seventh aspect, a computer program for supporting envelope reporting in a radio communication network having a CP function separated from a UP function is proposed. The computer program includes computer program code, which, when running on a CP node, causes the CP node to: set a TQM in a URR, the service data flow SDF corresponding to the TQM being applicable to envelope reporting; set at least one report trigger in the URR to instruct the UP function to generate a usage report when the envelope is closed; set a measurement method in the URR to instruct the UP function to collect usage of quantity, time and / or event; send the set URR to the UP function; receive one or more usage reports from the UP function in response to the sent URR, wherein the received usage report includes at least: a usage report trigger set to envelope closure; determine the start time and / or end time of each envelope based on the received usage report; and store each envelope with the determined start time and / or end time for online or offline billing.

[0076] According to an eighth aspect, a computer program is provided for supporting envelope reporting in a radio communication network having a CP function separated from a UP function. The computer program includes computer program code, which, when executed on a UP node, causes the UP node to: receive a URR from the CP function, the URR including: a TQM and at least one report trigger set to envelope closure; and send a usage report to the CP function indicating envelope closure.

[0077] A computer program product is also proposed, comprising a computer program and a computer readable storage device on which the computer program is stored.

[0078] Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field unless explicitly defined otherwise herein. Unless explicitly stated otherwise, all references to "a / an / the element, device, component, part, step, etc." should be publicly interpreted as referring to at least one instance of an element, device, component, part, step, etc. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated. BRIEF DESCRIPTION OF THE DRAWINGS

[0079] The present invention will now be described by way of example with reference to the accompanying drawings, in which:

[0080] Figure 1 Schematically illustrates an architecture reference model in the case where the control plane and the user plane are separated;

[0081] Figure 2 Schematically illustrates an architectural reference model for a combined SGW / PGW in the case of separation of the control plane and the user plane;

[0082] Figure 3 Schematically shows an envelope report for DTP;

[0083] Figure 4 An envelope report for CTP is schematically shown;

[0084] Figure 5 is a flow chart schematically illustrating an embodiment of the control plane proposed herein;

[0085] Figure 6 is a flow chart schematically illustrating an embodiment of the user plane proposed herein;

[0086] Figure 7 is a schematic diagram showing some components of the control plane proposed in this article;

[0087] Figure 8 is a schematic diagram showing some components of the user plane proposed in this article;

[0088] Fig. 9 is a schematic diagram showing the functional modules of the control plane proposed in this article; and

[0089] Fig.10 is a schematic diagram showing the functional modules of the user plane proposed in this article. DETAILED DESCRIPTION

[0090] The present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the invention are shown. However, the present invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided merely as examples so that the present disclosure will be thorough and complete and the scope of the invention will be fully conveyed to those skilled in the art. Throughout the specification, the same numerals represent the same elements.

[0091] Subclause 6.5.6 of 3GPP TS 32.299 specifies an envelope measurement and reporting mechanism to provide additional detailed reporting, such as corresponding volume usage for extending time-based charging usage reporting. Envelope reporting is only used to indicate how time-based usage should be reported, but it is reported in different ways depending on the measurement method used (i.e. CTP or DTP). Envelope reporting is independent of quota management (i.e. there is no interaction).

[0092] According to the TS, the measurement and envelope reporting methods may be enabled by local configuration or may be specified by an Online Charging System (OCS) corresponding to the OCF described in the TS.

[0093] However, there is no mechanism that specifies how to support the separation of control plane (CP) functionality and user plane (UP) functionality.

[0094] A major problem with the hypothetical solution proposed in the background is that it unnecessarily pushes the complexity of both the time-based measurement (TQM) mechanism and the envelope reporting mechanism to the UP functionality, which runs counter to the principle of separating CP and UP functionality (i.e., making the UP functionality independent of 3GPP).

[0095] Some other disadvantages of this hypothetical solution:

[0096] 1. It does not explain the connection between the Continuous Time Period (CTP) and the Inactivity Detection Timer (IDT), which can be mapped to the Quota Consumption Time (QCT).

[0097] 2. For usage reporting from UP function to CP function, it adds more usage parameters within the envelope, which is not effectively signaled.

[0098] A mechanism is proposed to support envelope reporting in the context of separation of CP functionality and UP functionality.

[0099] The mechanism includes the following aspects of CP functionality:

[0100] -When envelope reporting is required, the CP function provides the UP function with a TQM (including the Basic Time Interval (BTI) type, which can be either CTP or DTP), and the BTI for time-based measurements added in the Usage Reporting Rules (URR). (This corresponds to Section 6.5.7 in 3GPP TS 32.299: For CTP, time measurements start at the time when the traffic occurs and continue until the first time interval that does not contain traffic. Time measurements shall include the last basic time interval, i.e., the basic time interval that does not contain traffic. After receiving subsequent traffic, time measurements are resumed by the UP function. For DTP, time measurements shall be resumed on the first traffic after the DTP expires.)

[0101] - When an envelope report is required where the BTI type in TQM is set to CTP, the CP function requests the UP function to report traffic for a period of time until the IDT expires or if no usage (traffic) is detected for the first BTI.

[0102] - When an envelope report is required in which the BTI type in TQM is set to DTP, the CP function requests the UP function to report the traffic for each BTI.

[0103] -The CP function may instruct the UP function to report only time, time and amount, time and events, or time and amount and number of events by setting the measurement method accordingly. The CP function sets the report trigger to Envelope Closure for CTP or Envelope Closure for DTP in the Report Trigger Information Element (IE).

[0104] Correspondingly, for the UP function:

[0105] -When the reporting trigger in the corresponding URR is set to envelope closure for CTP, and IDT is included and the BTI type in the TQM is set to CTP, the UP function sends measurement reports on time and / or quantities and / or events as indicated in the measurement method over a time period that may include multiple consecutive BTIs until the IDT expires or when no usage / traffic is first detected for the BTI.

[0106] -When the reporting trigger in the corresponding URR is set to envelope closure for DTP, and the BTI type in the TQM is set to DTP, the UP function sends a measurement report on time, and / or quantity, and / or event as indicated in the measurement method for each BTI.

[0107] In other words, a mechanism for supporting envelope reporting in a wireless communication system in which a UP function is separated from a CP function includes the following aspects.

[0108] 1) In the CP function, TQM parameters for online charging or configured for offline charging that may be received via the Gy interface are mapped to IEs used via the Sx interface.

[0109] 2) Provide the UP with TQM and possibly IDT related to the reporting envelope by specifying details of whether to use CTP or DTP.

[0110] 3) Based on the envelope reporting quota type used (volume vs. time, or Synchronous Supply Unit (SSU) vs. time, etc.), provide the appropriate quota type (by setting e.g., volume quota / threshold, time quota / threshold, and so on in the request to UP).

[0111] 4) Existing quota-related parameters (such as volume quota, time quota, IDT, etc.) are used to indicate to the UP function what to measure.

[0112] 5) The logic of the envelope report is hosted by the CP function, i.e. no reporting related parameters such as the type of quota to be reported to the UP are provided, so the CP function creates the envelope report based on the usage report from the UP function in anticipation of the need for envelope reports and simply seals the envelope with appropriate content.

[0113] The UP function then only needs to perform measurements based on the method provided by the CP function, such as CTP or DTP.

[0114] However, in addition, the UP function adds a report trigger to indicate that the usage report is triggered by envelope closure.

[0115] Two cases of envelope reporting for CTP and DTP will now be illustrated in more detail.

[0116] In the DPT example, each complete envelope is reported from the UP function to the CP function in one usage report, whereas in the CTP example, the envelope report may be split into multiple usage reports from the UP function to the CP function when there are other report triggers that occur before the envelope is closed (charging events, in this example, usage depletion).

[0117] However, still in the DPT scenario, the CP function may also receive the envelope reported via some usage reports from the UP function when other reporting triggers occur before the envelope closure reporting trigger.

[0118] Figure 3 An example of an envelope report for a DTP is shown.

[0119] The OCS sends a request for an envelope report to the CP function, wherein the request notifies the TQM set as the DTP, the volume quota, the time quota, and the quota holding time (QHT) of 30 seconds.

[0120] In response, the CP function sets the URR with a TQM including an indication of the DTP, a BTI of 10 seconds, a QHT of 30 seconds, and the volume and time quotas. The request with the URR is sent to the UP function.

[0121] In response, the UP function starts measuring traffic. When the first traffic is detected, the envelope start time is set to t1. After the BTI, the usage report is triggered and reports the requested volume and time usage, as well as the start time t1 and the end time t2. The usage report also indicates that the usage report trigger is envelope closure.

[0122] The CP function receives the usage report and determines the start and end times of the envelopes and creates and stores the first envelope based on the trigger being an indication of envelope closure.

[0123] The UP function continues to measure the traffic. The previous envelope end time t2 is also the new envelope start time t2. After another BTI, another usage report is triggered and again reports the requested volume and time usage, along with the envelope start time t2 and end time t3. The usage report also indicates that the usage report was triggered as envelope closure.

[0124] The CP function creates and stores a second envelope accordingly.

[0125] The third and fourth envelopes are also created and stored in a corresponding manner. However, the fourth BTI and corresponding usage report do not contain traffic. Starting at time t4 after the last data packet is received, at time t7 after 30 seconds of QHT, a URR with the requested volume and time usage and an indication that the usage report trigger is QHT will be sent.

[0126] The CP function receives the usage report and, based on an indication that the trigger is a QHT, creates a reporting envelope to the OCS, the report including the first envelope to the fourth envelope and the aggregated quantity usage.

[0127] Figure 4 An example of an envelope report for a CTP is shown.

[0128] The OCS sends an instruction for envelope reporting to the CP function, where the request notification is set to TQM of CTP, quantity quota, time quota, QCT of 20 seconds, and quota holding time (QHT) of 30 seconds.

[0129] In response, the CP function sets the URR with a TQM including an indication of CTP, an IDT of 20 seconds, a BTI of 10 seconds, a QHT of 30 seconds, and a volume and time quota. A request with the URR is sent to the UP function.

[0130] In response to this, the UP function starts measuring traffic. When the first traffic is detected, the envelope start time is set to t1. After the BTI, at time t2, the UP function continues to measure traffic until another BTI expires at time t3.

[0131] In the third BTI segment, the volume quota has been exhausted and the UP function sends a usage report with the start time t1, the time and volume usage, and an indication that the trigger is the quota exhaustion.

[0132] The CP function receives the usage report and determines the start time of the envelope, but the end time is missing and the trigger is quota exhaustion rather than envelope closure. The CP function then uses the volume and time usage to report an incomplete envelope and indicates that the reporting reason is volume exhaustion.

[0133] In turn, the OCS sends an update instruction with the volume quota and the remaining time quota to the CP function.

[0134] In response to the updated instruction, the CP function sends a request with an updated URR to the UP function.

[0135] In response to the updated URR, the UP function continues to measure the service at the same BTI.

[0136] After time t5, no traffic is measured, and after the IDT expires at t8, the UP function will send a usage report containing the volume and time usage since the updated URR, and an indication of envelope closure.

[0137] The CP function receives the usage report and determines the start time (for a complete envelope) t1 and the end time t8 of the envelope, and creates and stores the first envelope based on the trigger being an indication of envelope closure. The volume usage includes the usage of the entire envelope.

[0138] However, the fifth BTI contains no traffic, and after 30 seconds of QHT (counting from time t5 after the last data packet is received), a URR is sent with a request amount and time usage of zero, and an indication that the usage report trigger is QHT.

[0139] The CP function receives the usage report and creates a reporting envelope to the OCS based on the indication that the trigger is QHT, the report including the first envelope and the summarized quantity usage.

[0140] The proposed solution provides an efficient mechanism to support envelope reporting by distributing the complexity of time-based measurements and envelope reporting mechanisms between UP and CP. It follows the principle that URR is only used to instruct the UP function how to count packets. It also avoids complicating the implementation of the UP function with unnecessary information, such as sending the envelope reporting mechanism over the Sx interface.

[0141] Reference Figure 5, a method for supporting envelope reporting in a radio communication network having a CP function separated from a UP function according to an embodiment is proposed. The method is performed in a CP node of the radio communication network and includes: setting (S100) a TQM in a URR, the service data flow SDF corresponding to the TQM being suitable for envelope reporting; setting (S100) at least one report trigger in the URR to instruct the UP function to generate a usage report when the envelope is closed; setting (S100) a measurement method in the URR to instruct the UP function to collect usage of quantity, time and / or event; then sending (S110) the set URR to the UP function; in response to the sent URR, receiving (S120) one or more usage reports from the UP function, wherein the received usage reports at least include: a usage report trigger set as envelope closure; based on the received usage reports, determining (S130) a start time and / or end time of each envelope; and storing (S140) each envelope with the determined start time and / or end time for online or offline charging.

[0142] The TQM may include a basic time interval BTI and a BTI type, where the BTI type is a continuous time period CTP or a discrete time period DTP.

[0143] The method may further include setting (S100) an inactivity detection timer IDT in the URR to a quota consumption time QCT received from the online charging system OCS.

[0144] The at least one reporting trigger may be set to envelope closure for the CTP and / or the DTP.

[0145] Determination of the envelope start time may be based on the time of the first packet in each usage report following a received usage report having a usage report trigger set to envelope closure.

[0146] Determination of the envelope end time may be based on a time at which a received usage report having a user report trigger set as envelope closure has been generated.

[0147] Reference Figure 6 , a method for supporting envelope reporting in a radio communication network having a CP function separated from a UP function according to an embodiment is proposed. The method is performed in a UP node of the radio communication network and comprises: receiving (S200) a URR from the CP function, the URR comprising a TQM and at least one report trigger set to envelope closure; and sending (S220) a usage report to the CP function, indicating envelope closure.

[0148] TQM may include basic time intervals BTI and BIT types, where the BTI type is a continuous time period CTP or a discrete time period DTP.

[0149] The received URR may include a measurement method, an inactivity detection timer IDT, and a BTI type that is a CTP, and wherein the usage report includes: measurements of time, quantity and / or events as indicated in the received measurement method over a time period (the time period comprising consecutive BTIs) until the IDT expires or when no usage is detected for the BTI.

[0150] The received URR may include a measurement method and a BTI type that is a DTP, and wherein the usage report includes, for each BTI, measurements of time, volume, and / or events as indicated by the received measurement method.

[0151] The usage report may include a usage report trigger that is set to be envelope closed.

[0152] Reference Figure 7 , shows a CP node according to an embodiment, the CP node being used to support envelope reporting in a radio communication network having a CP function separated from a UP function. The CP node includes a processor 10 and a computer program product 12, 13, the computer program product 12, 13 storing instructions, which when executed by the processor causes the CP node to: set (S100) a TQM in a URR, the service data flow SDF corresponding to the TQM being suitable for envelope reporting; set (S100) at least one report trigger in the URR to instruct the UP function to generate a usage report when the envelope is closed; set (S100) a measurement method in the URR to instruct the UP function to collect usage of quantity, time and / or event; send (S110) the set URR to the UP function; receive (S120) one or more usage reports from the UP function in response to the sent URR, wherein the received usage reports include at least a usage report trigger set for envelope closure; determine (S130) a start time and / or end time of each envelope based on the received usage reports; and store (S140) each envelope with the determined start time and / or end time for online or offline charging.

[0153] The TQM may include a basic time interval BTI and a BTI type, where the BTI type is a continuous time period CTP or a discrete time period DTP.

[0154] The CP node may further be caused to set ( S100 ) the inactivity detection timer IDT in the URR to the quota consumption time QCT received from the online charging system OCS.

[0155] The at least one reporting trigger may be set to envelope closure for the CTP and / or the DTP.

[0156] Determination of the envelope start time may be based on the time of the first packet in each usage report following a received usage report having a usage report trigger set to envelope closure.

[0157] Determination of the envelope end time may be based on a time at which a received usage report having a user report trigger set as envelope closure has been generated.

[0158] Figure 7 1 is a schematic diagram showing some components of a CP node. The processor 10 may be provided using any combination of one or more of a suitable central processing unit CPU, a multiprocessor, a microcontroller, a digital signal processor DSP, an application specific integrated circuit, etc. capable of executing software instructions of a computer program 14 stored in a memory. The memory may therefore be considered to be or form part of a computer program product 12. The processor 10 may be configured to execute the computer program product 12 described herein. Figure 5 Describe the method.

[0159] The memory may be any combination of read-write memory RAM and read-only memory ROM. The memory may also include permanent storage, which may be any one or combination of magnetic memory, optical memory, solid-state memory or even remotely mounted memory, for example.

[0160] A second computer program product 13 in the form of a data memory may also be provided, for example for reading and / or storing data during execution of software instructions in the processor 10. The data memory may be any combination of read-write memory RAM and read-only memory ROM, and may also include permanent storage, which may be any one or a combination of magnetic memory, optical memory, solid-state memory or even remotely mounted memory, for example. The data memory may, for example, hold other software instructions 15 to improve the functionality of the CP node.

[0161] The CP node may further include an input / output (I / O) interface 11, which includes, for example, a user interface. The CP may further include: a receiver configured to receive signaling from other nodes; and a transmitter configured to send signaling to other nodes (not shown). Other components of the CP node are omitted to avoid obscuring the concepts presented herein.

[0162] Fig. 9is a schematic diagram showing the functional blocks of a CP node. These modules may be implemented as only software instructions (e.g., a computer program executed in a cache server) or only hardware (e.g., an application specific integrated circuit, a field programmable gate array, discrete logic components, a transceiver, etc.) or a combination thereof. In alternative embodiments, some functional blocks may be implemented by software and other functional blocks may be implemented by hardware. These modules correspond to Figure 5 The steps in the method shown include determining a manager unit 90 and a communication manager unit 91. In embodiments where one or more modules are implemented by a computer program, it should be understood that these modules do not necessarily correspond to processing modules, but may be written as instructions according to the programming language in which they are to be implemented, as some programming languages ​​generally do not contain processing modules.

[0163] The determination manager 90 is used to support envelope reporting. This module corresponds to Figure 5 When the computer program is run, this module may be, for example, Figure 7 The processor 10 is implemented.

[0164] The communication manager 91 is used to support envelope reporting. This module corresponds to Figure 5 The setting step S100, sending step S110, receiving step S120 and storing step 140 in the computer program. When the computer program is run, the module can be, for example, Figure 7 The processor 10 is implemented.

[0165] Figure 8 2 is a schematic diagram showing some components of a UP node. The processor 20 may be provided using any combination of one or more of a suitable central processing unit CPU, a multiprocessor, a microcontroller, a digital signal processor DSP, an application specific integrated circuit, etc. capable of executing software instructions of a computer program 24 stored in a memory. The memory may therefore be considered to be a computer program product 22 or form part of a computer program product 22. The processor 20 may be configured to perform the Figure 6 Describe the method.

[0166] The memory may be any combination of read-write memory RAM and read-only memory ROM. The memory may also include permanent storage, which may be any one or combination of magnetic memory, optical memory, solid-state memory or even remotely mounted memory, for example.

[0167] A second computer program product 23 in the form of a data memory may also be provided, for example for reading and / or storing data during execution of software instructions in the processor 20. The data memory may be any combination of read-write memory RAM and read-only memory ROM, and may also contain permanent storage, which may for example be any one or a combination of magnetic memory, optical memory, solid-state memory or even remotely mounted memory. The data memory may for example hold other software instructions 25 to improve the functionality of the UP node.

[0168] The UP node may further include an input / output (I / O) interface 21, which includes, for example, a user interface. The UP may further include: a receiver configured to receive signaling from other nodes; and a transmitter configured to send signaling to other nodes (not shown). Other components of the UP node are omitted to avoid confusing the concepts presented herein.

[0169] Fig.10 is a schematic diagram showing the functional blocks of a UP node. These modules may be implemented as only software instructions (e.g., a computer program executed in a cache server) or only hardware (e.g., an application specific integrated circuit, a field programmable gate array, discrete logic components, a transceiver, etc.) or a combination thereof. In alternative embodiments, some functional blocks may be implemented by software and other functional blocks may be implemented by hardware. These modules correspond to Figure 6 The steps in the method shown include determining the manager unit 100 and the communication manager unit 101. In embodiments where one or more modules are implemented by a computer program, it should be understood that these modules do not necessarily correspond to processing modules, but may be written as instructions according to the programming language in which they are to be implemented, as some programming languages ​​generally do not contain processing modules.

[0170] The determination manager 100 is used to support envelope reporting in a radio communication network having a control plane CP function separated from the UP function. This module corresponds to Figure 6 When the computer program is run, this module can be, for example, Figure 8 The processor 20 is implemented.

[0171] The communication manager 101 is used to support envelope reporting in a radio communication network having a control plane CP function separated from the UP function. This module corresponds to Figure 6 When the computer program is executed, the module may be, for example, Figure 8 The processor 20 is implemented.

[0172] The invention has mainly been described above with reference to a few embodiments. However, as is readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the invention, as defined by the appended claims.

Claims

1. A method for supporting envelope reporting, the method being performed by a control plane CP function, and include: sending a usage reporting rule (URR) to a user plane (UP) function, wherein the URR sent to the UP function comprises a report trigger indicator for instructing the UP function to generate a usage report when the envelope is closed; receiving a usage report generated by the UP function when the envelope is closed, wherein the received usage report includes: a usage report trigger indicator indicating that the usage report is generated by the UP function when the envelope is closed; and Based on the received usage report, a start time and / or an end time of the envelope is determined.

2. The method according to claim 1, further comprising: include: The envelope with the determined start time and / or end time is stored for online or offline charging.

3. The method according to claim 1, in, The URR also includes a time quota mechanism TQM and a measurement method indicator.

4. The method according to claim 3, in, The TQM includes a basic time interval BTI and a BTI type, and the BTI type is a continuous time period CTP or a discrete time period DTP.

5. The method according to claim 4, in, The report trigger indicator included in the URR is set to envelope closure for the CTP and / or DTP.

6. The method according to claim 1, in, The URR further includes an inactivity detection timer IDT, which is set to a quota consumption time QCT received from an online charging system OCS.

7. The method according to claim 1, in, The method includes: determining the start time of the envelope based on the received usage report; Determining the start time is based on a time of a first packet in each usage report following a received usage report having the usage report trigger indicator set to envelope closed.

8. The method according to claim 1, in, The method includes: determining the end time of the envelope based on the received usage report; Determining the end time is based on a time at which a received usage report having the usage report trigger indicator set to envelope closed has been generated.

9. A method for supporting envelope reporting in a radio communication network, the radio communication network having a control plane CP function and a user plane UP function, the method being performed by the UP function, and include: receiving a usage reporting rule (URR) sent by the CP function, the URR including a report trigger indicator for instructing the UP function to generate a usage report when an envelope is closed; When the envelope is closed, generating the usage report; as well as The usage report is sent to the CP function, wherein the usage report includes a usage report trigger indicator indicating that the usage report is generated by the UP function when the envelope is closed.

10. The method according to claim 9, in, The URR also includes a time quota mechanism TQM.

11. The method according to claim 10, in, The TQM includes a basic time interval BTI and a BTI type, and the BTI type is a continuous time period CTP or a discrete time period DTP.

12. The method according to claim 11, in, The received URR also includes: a measurement method and an inactivity detection timer IDT, and the BTI type is CTP, and wherein the usage report comprises: measurements of time, quantity and / or events as indicated in the received measurement method over a time period comprising consecutive BTIs until the IDT has expired or when no usage is detected for the BTI; or A measurement method is received, and the BTI type is DTP, and wherein the usage report includes: for each BTI, a measurement of time, amount and / or event as indicated by the received measurement method.

13. A control plane CP function for supporting envelope reporting, the CP function include: processor; as well as a memory storing instructions that, when executed by the processor, cause the CP function to perform a process comprising: sending a usage reporting rule (URR) to a user plane (UP) function, wherein the URR sent to the UP function comprises a report trigger indicator for instructing the UP function to generate a usage report when the envelope is closed; receiving a usage report generated by the UP function when the envelope is closed, wherein the received usage report includes: a usage report trigger indicator indicating that the usage report is generated by the UP function when the envelope is closed; and Based on the received usage report, a start time and / or an end time of the envelope is determined.

14. The CP function according to claim 13, in, The process also includes storing the envelope with the determined start time and / or end time for online or offline charging.

15. The CP function according to claim 13, in, The URR also includes a time quota mechanism TQM and a measurement method indicator; The TQM includes a basic time interval BTI and a BTI type, and the BTI type is a continuous time period CTP or a discrete time period DTP.

16. The CP function according to claim 13, in, The process also includes: The inactivity detection timer IDT in the URR is set to the quota consumption time QCT received from the online charging system OCS.

17. The CP function according to claim 13, in, The process includes: determining the start time of the envelope based on the received usage report; Determining the start time is based on a time of a first packet in each usage report following a received usage report having the usage report trigger indicator set to envelope closed.

18. The CP function according to claim 13, in, The process includes: determining the end time of the envelope based on the received usage report; Determining the end time is based on a time at which a received usage report having the usage report trigger indicator set to envelope closed has been generated.

19. A user plane (UP) function for supporting envelope reporting in a radio communication network, the radio communication network having a control plane (CP) function separate from the UP function, the UP function include: processor; as well as a memory storing instructions, wherein when the instructions are executed by the processor, the UP function performs a process, the process comprising: receiving a usage reporting rule (URR) sent by the CP function, the URR including a report trigger indicator for instructing the UP function to generate a usage report when an envelope is closed; When the envelope is closed, generating the usage report; and The usage report is sent to the CP function, wherein the usage report includes a usage report trigger indicator indicating that the usage report is generated by the UP function when the envelope is closed.

20. The UP function according to claim 19, in, The URR also includes a time quota mechanism TQM; The TQM includes a basic time interval BTI and a BTI type, and the BTI type is a continuous time period CTP or a discrete time period DTP.

21. The UP function according to claim 20, in, The received URR also includes: a measurement method and an inactivity detection timer IDT, and the BTI type is CTP, and wherein the usage report comprises: measurements of time, quantity and / or events as indicated in the received measurement method over a time period comprising consecutive BTIs until the IDT has expired or when no usage is detected for the BTI; or A measurement method is received, and the BTI type is DTP, and wherein the usage report includes: for each BTI, a measurement of time, amount and / or event as indicated by the received measurement method.

22. A non-transitory computer readable medium storing a computer program for causing a control plane function to perform the method of claim 1.

23. A non-transitory computer readable medium storing a computer program for causing a user plane function to perform the method of claim 9.

Images