Data volume reporting in 5GS

A method performed by a first network node includes generating a data volume report based on one or more characteristics associated with data communicated between the first network node and a user equipment. The one or more characteristics identify that the data volume report is to be generated on at least one of a per Data Radio Bearer basis and a per Quality of Service basis. The data volume report is transmitted to a second network node. The data volume report further includes an indication of a radio access technology type associated with the data volume report.

TECHNICAL FIELD

The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for data volume reporting in 5GS.

BACKGROUND

Data Volume Reporting was introduced for Evolved Universal Terrestrial Radio Access (E-U IRA) New Radio-Dual Connectivity (EN-DC) access in Evolved-Universal Terrestrial Radio Access Network (E-UTRAN) in order to allow to charge or control a customer's usage of New Radio (NR) access. E-UTRAN provides by S1 Application Protocol (S1AP) signalling means information to the Evolved Packet Core (EPC) about the usage of NR access on a per E-RAB basis by a User Equipment (UE). This function is described in Section 10.11 of 3GPP TS 37.340 as follows:

10.11 Secondary [Radio Access Technology] Data Volume Reporting

10.11.1 EN-DCThe secondary RAT data volume reporting function is used to report the data volume of secondary RAT to [Core Network]. In EN-DC, if configured, the [Master Node] reports the uplink and downlink data volumes of used NR resources to the EPC on a per [Evolved Packet System] bearer basis as specified in TS 36.300 [2]. Periodic reporting is performed by periodically sending the Secondary RAT Data Volume Report messages to the [Mobile Management Entity].The data volume is counted by the node hosting [Packet Data Convergence Protocol]. Downlink data volume is counted in bytes of PDCP [Service Data Units] successfully delivered to the UE over NR (for [Radio Link Control Acknowledged Mode]) or transmitted to the UE over NR (for [Radio Link Control Unacknowledged Mode]). Uplink data volume is counted in bytes of PDCP SDUs received by the node hosting PDCP over NR. Forwarded packets shall not be counted when PDCP entity is relocated. When PDCP duplication is activated, packets shall be counted only once.

FIG.1illustrates an example signalling flow for secondary RAT data volume periodic reporting according to EN-DC. As depicted, if periodic reporting is configured, then the Secondary Node (SN) periodically sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes of used NR radio resources for the related SN-terminated EPS-Radio Access Bearers (E-RABs). The MN then sends the Secondary RAT Data Usage Report message to MME to provide information on the used NR resource. The Secondary RAT Data Usage Report message sent by the MN may also include secondary RAT report information of MN-terminated bearers. In 5GS, such feature is also requested and is discussed in 3GPP TS 23.501, entitled Usage Data Reporting for Secondary RAT. Equivalent to EN-DC, the SN is requested to provide data volume reports on a per Quality of Service (QoS) flow basis for both, usage of NR access and usage of E-UTRA resources.

There currently exist certain challenges. For example, reporting on a per QoS flow basis may create problems, as Data Radio Bearers (DRBs) may carry more than one QoS flow. Unlike in EPS, where a DRB can be mapped to only one E-RAB/EPS-bearer with a single well defined QoS characteristic, a DRB in NR may carry more than one QoS flow, each QoS flow with different QoS characteristics.

In downlink (DL), the radio protocol entity that is responsible for processing data volume reports, once radio resources have been allocated (i.e. QoS flows have been mapped to a DRB), the PDCP entity would not need to regard the identity of the QoS flow at all. For efficiency reasons, the radio protocols would only convey the QoS flow identity to the UE in special circumstances such as, for example, when reflective QoS flow mapping is performed. Hence, the PDCP machinery would need to process the QoS flow ID, set up counters etc. For DRBs that use AM RLC, the QoS flow information per PDCP Packet Data Unit (PDU) would need to stay in PDCP until the PDCP PDU was successfully transmitted to the UE. This might cause problems such as, for example, if the number of counters needed are not known beforehand at DRB set up, as QoS flows might be added during the lifetime of radio resources providing resources to a PDU Session, which might be up to 64 (with current protocol means). Further, processing always consumes time, so the end-to-end delay performance might be hit, in case per QoS flow data volume counting is enabled.

In uplink (UL), per QoS flow reporting is only possible if the Service Data Adaptation Protocol (SDAP) header is configured such as, for example, if per PDCP PDU additional information is provided for the QoS flow associated with the PDCP PDU. For the default DRB, the SDAP header is mandated to be configured. For non-default DRBs, however, it is assumed to be the case as well if more than one QoS flow is mapped to a DRB, in order to control the (configured) UE behaviour in UL. Like in DL, allocating counters for each QoS flow may cause performance problems or require complex implementations.

Currently, the solution standardized for EN-DC reporting does not include any control mechanism from the Core Network. There is no possibility to choose which type of reporting is done or what E-RAB should be monitored. The reporting is configured for all the E-RABs setup for the UE.

SUMMARY

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. In particular, certain embodiments may provide a flexible control and reporting mechanism for secondary RAT Data Volume Reporting in 5GS.

According to certain embodiments, a method performed by a first network node includes generating a data volume report based on one or more characteristics associated with data communicated between the first network node and a user equipment. The one or more characteristics identify that the data volume report is to be generated on at least one of a per Data Radio Bearer basis and a per Quality of Service basis. The data volume report is transmitted to a second network node. The data volume report further includes an indication of a radio access technology type associated with the data volume report.

According to certain embodiments, a first network node includes processing circuitry configured to generate a data volume report based on one or more characteristics associated with data communicated between the first network node and a user equipment. The one or more characteristics identify that the data volume report is to be generated on at least one of a per Data Radio Bearer basis and a per Quality of Service basis. The data volume report is transmitted to a second network node. The data volume report further includes an indication of a radio access technology type associated with the data volume report.

Certain embodiments may provide one or more of the following technical advantage(s). For example, in some embodiments, the proposed mechanisms allow the 5GS to choose among several possibilities for Data Volume Reporting. As such, certain embodiments allow a simpler and more flexible implementation and control the system behaviour based on, for example, charging policies, type of user, current system load, or other factors.

DETAILED DESCRIPTION

According to certain embodiments, flexible control and reporting mechanisms are provided for secondary Radio Access Technology (RAT) Data Volume Reporting in 5GS. Certain solutions may be implemented over the NG, E1 and/or Xn interfaces and Operations Administration and Maintenance (OAM) to allow flexibility at Data Volume reporting. For example, certain embodiments may include:1. In a 5GS, Data Volume reporting is deployeda. either common for all user equipments (UEs), configured by OAM, meaning that the way how consumed Data Volumes are reported is the same for all UEs.b. or on a per UE basis, where the 5GCore (5GC) provides per UE control information on how consumed Data Volume is reported via Next Generation-Core (NG-C) when Next Generation-Radio Access Network (NG-RAN) resources for a Packet Data Unit (PDU) Session are established or modified.2. Consumed Data Volumes are reported per UE per Radio Access Technology (RAT), separate for uplink (UL) and downlink (DL):a. on a per PDU Session basisb. on a per Quality of Service (QoS) flow basis, for either all QoS flows in a PDU Session or only selected QoS flowsc. or combining a. and b.3. Impacts on NG-C, Xn-C, E1 and OAM for the configuration of Data Volume reporting are as follows:a. On NG-C, if per UE reporting is deployed, the 5GC provides control information on how Data Volume reporting shall be performed, per UE/per PDU session/per QoS flow.b. On Xn-C, if per UE reporting is deployed,i. in case of Direct Connectivity (DC), if Data Volume Reports have to be generated by the Secondary NG-RAN node, XnAP also conveys respective configuration information from the Master NG-RAN node to the Secondary NG-RAN (S-NG-RAN) node.ii. if the UE context is transferred towards a new serving NG-RAN, in case of handover (HO), Radio Resource Control_Inactive (RRC_INACTIVE) and re-establishment mobility scenarios, respective configuration information is also conveyed to prepare for subsequent DC configurations.c. On E1, if per UE reporting is deployed, each Bearer Context in the CU-UP is configured by the Central Unit-Control Plane (CU-CP) to support the requested type of reporting, independent of whether the type of Data volume reporting is controlled by Next Generation Application Protocol (NGAP) signaling or OAM.d. OAM: if common UE reporting is deployed, no signaling is needed on NG-C/Xn-C/E1. OAM will configure RAN nodes to perform data volume reporting on a per UE/RAT/PDU Session/QoS flow basis.4. Impacts on NG-C, Xn-C, E1 for Data Volume reporting is independent of whether per UE or common data volume reporting is deployed.a. On NG-C, the serving NG-RAN node (in case of DC, this is the Master NG-RAN node), reports consumed Data Volumes in UL and DL per UE per RAT per PDU Session and/or QoS Flow.b. On Xn-C, in case of DC, if PDCP is hosted by the S-NG-RAN node, the reporting is equivalent to the reporting on NG, most likely XnAP signaling will put per QoS flow reporting into a per DRB data structure.c. On E1, Data Volume reporting is equivalent to the method on NG-C/Xn-C.

According to a particular embodiment, for example per UE Data Volume reporting may be performed, and configuration data may be provided via NG-C and/or Xn-C.FIG.2illustrates a signalling flow50for the setup of a Data Radio Bearer (DRB1) with two cell groups such as, for example radio legs, according to certain embodiments. Specifically, the signalling flow50shows how the basic signalling might work on NG-C and Xn-C. The same approach may be used between a Central Unit-Control Plane (CU-CP) and a Central Unit-User Plane (CU-UP) on E1, where configuration information is received via NG(/Xn) is conveyed to the CU-UP.

At step 1, the Serving/Master NG-RAN node receives configuration information along the possibilities described above whenever a RAN resources for a PDU Session are setup and (if applicable) when modified. This information is provided independent of whether Dual Connectivity is actually used.

At step 2, in case of DC, when PDCP is hosted by the S-NG-RAN node for PDU Session resources, the M-NG-RAN node provide respective information, corresponding to information received from the 5GC.

At step 3, the S-NG-RAN node replies to the M-NG-RAN node.

At step 4, the Serving/M-NG-RAN node replies to the 5GC.

According to certain embodiments, a data structure for reporting consumed Data Volumes at NG-C, Xn-C and E1 is provided. Specifically, information about consumed Data Volumes may be provided either when RAN resources are released or periodically. Data Volumes are either reported within release messages or within explicit report messages. An example of how the NGAP, XnAP or E1AP may structure the respective Information Element (IE) is provided in Tables 1 and 2 below.

The Ref2-1 MR-DC Data Usage Report List IE provides information on the data usage for the UE connected to 5GC, e.g., secondary RAT in MR-DC. This IE allows for reporting for more than one RAT on either a consumed Data Volume per PDU Session (IE #6) or per—probably selected—QoS flows (IE #7-#10).

According to certain embodiments, a data structure is provided for controlling per UE reporting of consumed Data Volumes at NG-C, Xn-C and E1.

The control information indicates how the receiving node shall perform per UE data volume reporting. An example for how the NGAP, XnAP, or E1AP may structure the respective IE is given below in Example 3-1: NGAP: Including Data Volume reporting control information into the existing PDU Session related SMF containers.

The PDU Session Resource Setup Request Transfer IE is transparent to the AMF.

The Ref3-1-1 Data Volume Reporting Control IE provides information on how the receiving node shall perform Data Volume reporting for a UE. The IE is expected to be contained in signalling related to setup or modify NG-RAN node resources for a PDU Session.

Including Data Volume reporting control information into the existing Bearer Context Setup Request existing PDU Session Resource To Setup List and QoS Flows Information To Be Setup, e.g. as given below, in red colour

According to certain embodiments, an OAM configuration may be provided for common UE reporting.

According to certain embodiments, common UE reporting is deployed, and the OAM will configure the NG-RAN nodes (and gNB-CU-UP in case of CP/UP separation) with one of the following option:Reporting per PDU SessionReporting per PDU Session and per QoS FlowReporting per QoS FlowReporting per PDU Session and per selected QoS Flow (i.e. 5QI)Reporting per selected QoS Flow (i.e. 5QI)
Whatever the option configured in the NG-RAN nodes, the reporting will be performed using the same mechanisms described in the embodiments described above and, thus similar to the per UE configuration over NG-U, Xn-U and E1.

According to certain embodiments, the new control information (see data structure above) may be added to existing message.

As described above, the control information on how Data Volume reporting shall be performed has to be transferred if the UE context is transferred towards a new serving NG-RAN (e.g. in case of Handover, RRC_INACTIVE or re-establishment) or if a SN is added or modified or if the NG-RAN node is a disaggregated NG-RAN node. This may include (but is not limited to) the following procedures:XnAP:a. Handover Preparationb. Retrieve UE Contextc. S-NG-RAN node Addition Preparationd. M-NG-RAN node initiated S-NG-RAN node Modification PreparationE1AP:a. Bearer Context Setupb. Bearer Context Modification (gNB-CU-CP initiated)

As described above, the reporting can be periodical or triggered by events. The new reporting structure described in this invention may be used in messages sent when the following events are triggered (but not limited to):Secondary Node Modification (MN/SN initiated)Secondary Node Release (MN/SN initiated)Secondary Node Change (MN/SN initiated)Inter-Master Node handover with/without Secondary Node changeMaster Node to eNB/gNB Change

InFIG.4, network node160includes processing circuitry170, device readable medium180, interface190, auxiliary equipment184, power source186, power circuitry187, and antenna162. Although network node160illustrated in the example wireless network ofFIG.4may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node160are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium180may comprise multiple separate hard drives as well as multiple RAM modules).

Processing circuitry170may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node160components, such as device readable medium180, network node160functionality. For example, processing circuitry170may execute instructions stored in device readable medium180or in memory within processing circuitry170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry170may include a system on a chip (SOC).

Interface190is used in the wired or wireless communication of signalling and/or data between network node160, network106, and/or wireless devices110. As illustrated, interface190comprises port(s)/terminal(s)194to send and receive data, for example to and from network106over a wired connection. Interface190also includes radio front end circuitry192that may be coupled to, or in certain embodiments a part of, antenna162. Radio front end circuitry192comprises filters198and amplifiers196. Radio front end circuitry192may be connected to antenna162and processing circuitry170. Radio front end circuitry may be configured to condition signals communicated between antenna162and processing circuitry170. Radio front end circuitry192may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry192may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters198and/or amplifiers196. The radio signal may then be transmitted via antenna162. Similarly, when receiving data, antenna162may collect radio signals which are then converted into digital data by radio front end circuitry192. The digital data may be passed to processing circuitry170. In other embodiments, the interface may comprise different components and/or different combinations of components.

Power circuitry187may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node160with power for performing the functionality described herein. Power circuitry187may receive power from power source186. Power source186and/or power circuitry187may be configured to provide power to the various components of network node160in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source186may either be included in, or external to, power circuitry187and/or network node160. For example, network node160may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry187. As a further example, power source186may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Antenna111may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface114. In certain alternative embodiments, antenna111may be separate from wireless device110and be connectable to wireless device110through an interface or port. Antenna111, interface114, and/or processing circuitry120may be configured to perform any receiving or transmitting operations described herein as being performed by a wireless device. Any information, data and/or signals may be received from a network node and/or another wireless device. In some embodiments, radio front end circuitry and/or antenna111may be considered an interface.

As illustrated, interface114comprises radio front end circuitry112and antenna111. Radio front end circuitry112comprise one or more filters118and amplifiers116. Radio front end circuitry114is connected to antenna111and processing circuitry120, and is configured to condition signals communicated between antenna111and processing circuitry120. Radio front end circuitry112may be coupled to or a part of antenna111. In some embodiments, wireless device110may not include separate radio front end circuitry112; rather, processing circuitry120may comprise radio front end circuitry and may be connected to antenna111. Similarly, in some embodiments, some or all of RF transceiver circuitry122may be considered a part of interface114. Radio front end circuitry112may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry112may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters118and/or amplifiers116. The radio signal may then be transmitted via antenna111. Similarly, when receiving data, antenna111may collect radio signals which are then converted into digital data by radio front end circuitry112. The digital data may be passed to processing circuitry120. In other embodiments, the interface may comprise different components and/or different combinations of components.

As illustrated, processing circuitry120includes one or more of RF transceiver circuitry122, baseband processing circuitry124, and application processing circuitry126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry120of wireless device110may comprise a SOC. In some embodiments, RF transceiver circuitry122, baseband processing circuitry124, and application processing circuitry126may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry124and application processing circuitry126may be combined into one chip or set of chips, and RF transceiver circuitry122may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry122and baseband processing circuitry124may be on the same chip or set of chips, and application processing circuitry126may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry122, baseband processing circuitry124, and application processing circuitry126may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry122may be a part of interface114. RF transceiver circuitry122may condition RF signals for processing circuitry120.

Processing circuitry120may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a wireless device. These operations, as performed by processing circuitry120, may include processing information obtained by processing circuitry120by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

User interface equipment132may provide components that allow for a human user to interact with wireless device110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment132may be operable to produce output to the user and to allow the user to provide input to wireless device110. The type of interaction may vary depending on the type of user interface equipment132installed in wireless device110. For example, if wireless device110is a smart phone, the interaction may be via a touch screen; if wireless device110is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment132may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment132is configured to allow input of information into wireless device110, and is connected to processing circuitry120to allow processing circuitry120to process the input information. User interface equipment132may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment132is also configured to allow output of information from wireless device110, and to allow processing circuitry120to output information from wireless device110. User interface equipment132may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment132, wireless device110may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment134is operable to provide more specific functionality which may not be generally performed by wireless devices. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment134may vary depending on the embodiment and/or scenario.

Power source136may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. Wireless device110may further comprise power circuitry137for delivering power from power source136to the various parts of wireless device110which need power from power source136to carry out any functionality described or indicated herein. Power circuitry137may in certain embodiments comprise power management circuitry. Power circuitry137may additionally or alternatively be operable to receive power from an external power source; in which case wireless device110may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry137may also in certain embodiments be operable to deliver power from an external power source to power source136. This may be, for example, for the charging of power source136. Power circuitry137may perform any formatting, converting, or other modification to the power from power source136to make the power suitable for the respective components of wireless device110to which power is supplied.

RAM217may be configured to interface via bus202to processing circuitry201to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM219may be configured to provide computer instructions or data to processing circuitry201. For example, ROM219may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium221may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium221may be configured to include operating system223, application program225such as a web browser application, a widget or gadget engine or another application, and data file227. Storage medium221may store, for use by UE200, any of a variety of various operating systems or combinations of operating systems.

InFIG.6, processing circuitry201may be configured to communicate with network243busing communication subsystem231. Network243aand network243bmay be the same network or networks or different network or networks. Communication subsystem231may be configured to include one or more transceivers used to communicate with network243b. For example, communication subsystem231may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another wireless device, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter233and/or receiver235to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter233and receiver235of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In some embodiments, some signalling can be effected with the use of control system3230which may alternatively be used for communication between the hardware nodes330and radio units3200.

FIG.8illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. With reference toFIG.8, in accordance with an embodiment, a communication system includes telecommunication network410, such as a 3GPP-type cellular network, which comprises access network411, such as a radio access network, and core network414. Access network411comprises a plurality of base stations412a,412b,412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area413a,413b,413c. Each base station412a,412b,412cis connectable to core network414over a wired or wireless connection415. A first UE491located in coverage area413cis configured to wirelessly connect to, or be paged by, the corresponding base station412c. A second UE492in coverage area413ais wirelessly connectable to the corresponding base station412a. While a plurality of UEs491,492are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station412.

Communication system500further includes base station520provided in a telecommunication system and comprising hardware525enabling it to communicate with host computer510and with UE530. Hardware525may include communication interface526for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system500, as well as radio interface527for setting up and maintaining at least wireless connection570with UE530located in a coverage area (not shown inFIG.9) served by base station520. Communication interface526may be configured to facilitate connection560to host computer510. Connection560may be direct or it may pass through a core network (not shown inFIG.9) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware525of base station520further includes processing circuitry528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station520further has software521stored internally or accessible via an external connection.

It is noted that host computer510, base station520and UE530illustrated inFIG.9may be similar or identical to host computer430, one of base stations412a,412b,412cand one of UEs491,492ofFIG.8, respectively. This is to say, the inner workings of these entities may be as shown inFIG.9and independently, the surrounding network topology may be that ofFIG.8.

Wireless connection570between UE530and base station520is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE530using OTT connection550, in which wireless connection570forms the last segment. More precisely, the teachings of these embodiments may improve the flexibility with which data consumption is reported and thereby provide benefits such as improved load balancing to provide better user experience.

FIG.14depicts a method1000performed by a first network node160, according to certain embodiments. At step1002, the first network node160generates a data volume report based on one or more characteristics associated with data communicated between the first network node and a user equipment. The one or more characteristics identify that the data volume report is to be generated on at least one of a per DRB basis and/or a per QoS basis. At step1004, the first network node160transmits the data volume report to a second network node160. The data volume report further includes an indication of a radio access technology type associated with the data volume report.

According to a particular embodiment, the one or more characteristics identify that the data volume report is to be based on both the per Data Radio Bearer basis and the per Quality of Service basis.

According to a particular embodiment, the one or more characteristics identify that the data volume report is to be based on a per UE basis.

According to a particular embodiment, the one or more characteristics identify that the data volume report is to be on a per RAT basis.

According to a particular embodiment, the data volume report is transmitted periodically.

According to a particular embodiment, the data volume report is transmitted when RAN resources are released.

According to a particular embodiment, the data volume report is transmitted in response to a triggering event, which m ay include at least one of: a secondary node modification; a secondary node release; a secondary node change; an inter-master node handover with or without a secondary node change; and a master node to eNodeB or gNodeB change.

According to a particular embodiment, prior to generating the data volume report, the first network node160receives a message from the second network node. The message specifies the one or more characteristics for generating the data volume report.

According to a particular embodiment, the message includes at least one of: a handover preparation message; a user equipment, UE, context retrieval message; a Radio Access Network, RAN, node addition message; a RAN node modification message; a bearer context setup message; or a bearer context modification message.

According to a particular embodiment, at least one of the first network node160and the second network node include a RAN node.

According to a particular embodiment, the second network node includes a core network node.

FIG.15illustrates a schematic block diagram of a virtual apparatus1100in a wireless network (for example, the wireless network shown inFIG.3). The apparatus may be implemented in a network node (e.g., network node160shown inFIG.3). Apparatus1100is operable to carry out the example method described with reference toFIG.14and possibly any other processes or methods disclosed herein. It is also to be understood that the method ofFIG.14is not necessarily carried out solely by apparatus1100. At least some operations of the method can be performed by one or more other entities.

According to certain embodiments, generating unit1110may perform certain of the generating functions of the apparatus1100. For example, generating unit1110may generate a data volume report based on one or more characteristics. The one or more characteristics identify that the data volume report is to be generated on at least one of a per DRB basis and/or a per QoS basis.

According to certain embodiments, transmitting module1120may perform certain of the transmitting functions of the apparatus1100. For example, transmitting module1120may transmit the data volume report to a second network node160.

EXAMPLE EMBODIMENTS

Example Embodiments 1. A method performed by a wireless device for reporting data volumes, the method comprising: receiving a first message specifying one or more characteristics to be associated with a data volume report; and transmitting a second message comprising the data value report.

Example Embodiments 2. The method of 1 wherein the first message specifies any one or more characteristics discussed above.

Example Embodiments 3. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station.

Example Embodiments 4. A method performed by a network node for reporting data volumes, the method comprising: receive a first message specifying one or more characteristics to be associated with a data volume report.

Example Embodiments 5. The method of 4 further comprising transmitting a second message specifying the one or more characteristics to be associated with a data volume report.

Example Embodiments 6. The method of 4 further comprising: generating the data volume report based on the one or more characteristics specified in the first message; and transmitting the data volume report.

Example Embodiments 7. The method of 6 wherein the data volume report is transmitted periodically or when RAN resources are released.

Example Embodiments 8. The method of any of the previous embodiments wherein the first message specifies any one or more characteristics discussed above.

Example Embodiments 9. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless device.

Example Embodiments 10. A wireless device for reporting data volumes, the wireless device comprising: processing circuitry configured to perform any of the steps of any of Embodiments 1 to 3; and power supply circuitry configured to supply power to the wireless device.

Example Embodiments 11. A base station for reporting data volumes, the base station comprising: processing circuitry configured to perform any of the steps of any of Embodiments 4 to 9; power supply circuitry configured to supply power to the base station.

Example Embodiments 12. A user equipment (UE) for reporting data volumes, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of Embodiments 1 to 3; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

Example Embodiments 13. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of Embodiments 4 to 9.

Example Embodiments 14. The communication system of the previous embodiment further including the base station.

Example Embodiments 16. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

Example Embodiments 18. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

Example Embodiments 19. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

Example Embodiments 20. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.

Example Embodiments 21. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE's components configured to perform any of the steps of any of Embodiments 1 to 3.

Example Embodiments 22. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE. The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE's processing circuitry is configured to execute a client application associated with the host application.

Example Embodiments 24. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.

Example Embodiments 25. A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any of Embodiments 1 to 3.

Example Embodiments 26. The communication system of the previous embodiment, further including the UE.

Example Embodiments 27. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

Example Embodiments 30. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of Embodiments 1 to 3.

Example Embodiments 31. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.

Example Embodiments 32. The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

Example Embodiments 35. The communication system of the previous embodiment further including the base station.

Example Embodiments 36. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

Example Embodiments 38. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of Embodiments 1 to 3.

Example Embodiments 39. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.

Example Embodiments 40. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

ABBREVIATIONS

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).1×RTT CDMA2000 1× Radio Transmission Technology3GPP 3rd Generation Partnership Project5G 5th GenerationABS Almost Blank SubframeARQ Automatic Repeat RequestAWGN Additive White Gaussian NoiseBCCH Broadcast Control ChannelBCH Broadcast ChannelCA Carrier AggregationCC Carrier ComponentCCCH SDU Common Control Channel SDUCDMA Code Division Multiplexing AccessCGI Cell Global IdentifierCIR Channel Impulse ResponseCP Cyclic PrefixCPICH Common Pilot ChannelCPICH Ec/No CPICH Received energy per chip divided by the power density in the bandCQI Channel Quality informationC-RNTI Cell RNTICSI Channel State InformationDCCH Dedicated Control ChannelDL DownlinkDM DemodulationDMRS Demodulation Reference SignalDRX Discontinuous ReceptionDTX Discontinuous TransmissionDTCH Dedicated Traffic ChannelDUT Device Under TestE-CID Enhanced Cell-ID (positioning method)E-SMLC Evolved-Serving Mobile Location CentreECGI Evolved CGIeNB E-UTRAN NodeBePDCCH enhanced Physical Downlink Control ChannelE-SMLC evolved Serving Mobile Location CenterE-UTRA Evolved UTRAE-UTRAN Evolved UTRANFDD Frequency Division DuplexFFS For Further StudyGERAN GSM EDGE Radio Access NetworkgNB Base station in NRGNSS Global Navigation Satellite SystemGSM Global System for Mobile communicationHARQ Hybrid Automatic Repeat RequestHO HandoverHSPA High Speed Packet AccessHRPD High Rate Packet DataLOS Line of SightLPP LTE Positioning ProtocolLTE Long-Term EvolutionMAC Medium Access ControlMBMS Multimedia Broadcast Multicast ServicesMBSFN Multimedia Broadcast multicast service Single Frequency NetworkMBSFN ABS MBSFN Almost Blank SubframeMDT Minimization of Drive TestsMIB Master Information BlockMME Mobility Management EntityMSC Mobile Switching CenterNPDCCH Narrowband Physical Downlink Control ChannelNR New RadioOCNG OFDMA Channel Noise GeneratorOFDM Orthogonal Frequency Division MultiplexingOFDMA Orthogonal Frequency Division Multiple AccessOSS Operations Support SystemOTDOA Observed Time Difference of ArrivalO&M Operation and MaintenancePBCH Physical Broadcast ChannelP-CCPCH Primary Common Control Physical ChannelPCell Primary CellPCFICH Physical Control Format Indicator ChannelPDCCH Physical Downlink Control ChannelPDCP Packet Data Convergence ProtocolPDP Profile Delay ProfilePDSCH Physical Downlink Shared ChannelPGW Packet GatewayPHICH Physical Hybrid-ARQ Indicator ChannelPLMN Public Land Mobile NetworkPMI Precoder Matrix IndicatorPRACH Physical Random Access ChannelPRS Positioning Reference SignalPSS Primary Synchronization SignalPUCCH Physical Uplink Control ChannelPUSCH Physical Uplink Shared ChannelRACH Random Access ChannelQAM Quadrature Amplitude ModulationRAN Radio Access NetworkRAT Radio Access TechnologyRLC Radio Link ControlRLM Radio Link ManagementRNC Radio Network ControllerRNTI Radio Network Temporary IdentifierRRC Radio Resource ControlRRM Radio Resource ManagementRS Reference SignalRSCP Received Signal Code PowerRSRP Reference Symbol Received Power OR Reference Signal Received PowerRSRQ Reference Signal Received Quality ORReference Symbol Received QualityRSSI Received Signal Strength IndicatorRSTD Reference Signal Time DifferenceSCH Synchronization ChannelSCell Secondary CellSDAP Service Data Adaptation ProtocolSDU Service Data UnitSFN System Frame NumberSGW Serving GatewaySI System InformationSIB System Information BlockSNR Signal to Noise RatioSON Self Optimized NetworkSS Synchronization SignalSSS Secondary Synchronization SignalTDD Time Division DuplexTDOA Time Difference of ArrivalTOA Time of ArrivalTSS Tertiary Synchronization SignalTTI Transmission Time IntervalUE User EquipmentUL UplinkUMTS Universal Mobile Telecommunication SystemUSIM Universal Subscriber Identity ModuleUTDOA Uplink Time Difference of ArrivalUTRA Universal Terrestrial Radio AccessUTRAN Universal Terrestrial Radio Access NetworkWCDMA Wide CDMAWLAN Wide Local Area Network