Patent Description:
In today's wireless communications networks a number of different technologies are used, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/Enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible technologies for wireless communication. A wireless communications network comprises radio base stations or wireless access points providing radio coverage over at least one respective geographical area forming a cell. This may be referred to as a Radio Access Network, RAN. The cell definition may also incorporate frequency bands used for transmissions, which means that two different cells may cover the same geographical area but using different frequency bands. Wireless devices, also referred to herein as User Equipments, UEs, mobile stations, and/or wireless terminals, are served in the cells by the respective radio base station and are communicating with respective radio base station in the RAN. Commonly, the wireless devices transmit data over an air or radio interface to the radio base stations in uplink, UL, transmissions and the radio base stations transmit data over an air or radio interface to the wireless devices in downlink, DL, transmissions.

One way for an operator to determine the level of user experience in a wireless communications network is to measure throughput. In the 3GPP specification TS <NUM>, it is determined that a base station, such as e.g. a eNodeB/gNodeB, should support to measure a distribution of throughput values over a defined period of time, such as, e.g. <NUM> minutes. It also specifies a counter for this purpose that should be supported in order for the base station to be compliant with 3GPP. This counter may be referred to as a <NUM>-tpt-counter.

According to the 3GPP specification TS <NUM>, one such <NUM>-tpt-counter is associated with each radio cell and is supposed to account for carrier aggregation. Each mentioned throughput value may represent the data throughput associated with data transferred during one RRC connection. Also, according to 3GPP specification TS <NUM>, a RRC connection will not yield a throughput value if the per UE buffer was never non-empty. The detailed reason for this can be found in 3GPP specification TS <NUM>. Hence, the mentioned distribution of throughput values according to the <NUM>-tpt-counter will contain at most as many throughput values as the number of RRC connections that had been active during the mentioned defined period of time.

The measurements from the <NUM>-tpt-counter are normally very important and relevant for operators of the wireless communications network because they provide a strong indication of the mobile broadband subscribers' user experience, i.e. the user experience in the wireless communications network. Further, the measurements from the <NUM>-tpt-counter are often also used by the operators of the wireless communications network to decide whether or not a certain base station, such as, e.g. eNodeB/gNodeB, should get upgraded with more capacity. This may, for example, include adding an additional radio carrier or other measures to increase the throughput.

However, in some cases, the <NUM>-tpt-counter described above may not accurately measure what it is supposed to measure or what the operator think is being measured, that is, the actual throughput distribution in the wireless communications network. Hence, in such case, erroneous information may be provided to the operators of the wireless communications network, which may result in unnecessary and costly investments in the wireless communications network being made. <NPL>, discloses proposals related to throughput measurement for carrier aggregation. <NPL>, disclose proposals including small data burst for measurements related to Distribution of scheduled IP throughput. <CIT> disclose measuring data in a data stream between a UE and an enhanced access network.

It is an object of embodiments herein to improve the user experience in a wireless communications network.

According to a first aspect, the object is achieved by a method performed by a base station for operating a data throughput counter in a wireless communications as defined by independent claim <NUM>.

According to a second aspect, the object is achieved by a base station for operating a downlink, DL, data throughput counter in a wireless communications as defined by independent claim <NUM>.

By excluding throughput values that are based on too little data and/or too little time as described above, an enhanced counter in comparison to the <NUM>-tpt-counter is obtained. This means that operator and service providers of a wireless communications network may be provided with a simple yet accurate and reliable way to monitor user experience in the wireless communications network. It also means that the operator and service providers of a wireless communications network are able to detect radio cells that are becoming overloaded, and therefore may require a capacity expansion in order to maintain suitable level of user experience. Hence, the user experience in a wireless communications network is improved.

The figures are schematic and simplified for clarity, and they merely show details which are essential to the understanding of the embodiments presented herein, while other details have been left out. Throughout, the same reference numerals are used for identical or corresponding parts or steps.

In the following, the invention is best understood in view of <FIG> and <FIG>. The remaining embodiments, aspects and examples disclosed below are included for illustrative purposes and for facilitating the understanding of the invention.

<FIG> depicts a wireless communications network <NUM> in which embodiments herein may operate. In some embodiments, the wireless communications network <NUM> may be a radio communications network, such as, <NUM> or NR network. Although, the wireless communications network <NUM> is exemplified herein as an <NUM> or NR network, the wireless communications network <NUM> may also employ technology of any one of LTE, LTE-Advanced, WCDMA, GSM/EDGE, WiMax, UMB, GSM, or any other similar network or system. The wireless communications network <NUM> may also employ technology of an Ultra Dense Network, UDN, which e.g. may transmit on millimetre-waves (mmW).

The wireless communications network <NUM> comprises a network node <NUM>. The network node <NUM> may serve wireless devices in at least one cell <NUM>, or coverage area. The network node <NUM> may correspond to any type of network node or radio network node capable of communicating with a wireless device and/or with another network node, such as, a base station (BS), a radio base station, gNB, eNB, eNodeB, a Home NodeB, a Home eNodeB, a femto Base Station (BS), or a pico BS in the wireless communications network <NUM>. Further examples of the network node <NUM> may be a repeater, multi-standard radio (MSR) radio node such as MSR BS, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, a Remote Radio Unit (RRU), a Remote Radio Head (RRH), nodes in distributed antenna system (DAS), or core network node.

In <FIG>, a wireless device <NUM> is located within the cell <NUM>. The wireless device <NUM> is configured to communicate within the wireless communications network <NUM> via the network node <NUM> over a radio link served by the network node <NUM>. Utilizing the radio link, a bi-directional communications flow may be set up between the wireless device <NUM> and any entity capable of communication via the wireless communications network <NUM>. The wireless device <NUM> may transmit data over an air or radio interface to the radio base station <NUM> in uplink, UL, transmissions <NUM> and the radio base station may transmit data over an air or radio interface to the wireless devices in downlink, DL, transmissions <NUM>. The wireless device <NUM> may refer to any type of wireless device or user equipment (UE) communicating with a network node and/or with another wireless device in a cellular, mobile or radio communication network or system. Examples of such wireless devices are mobile phones, cellular phones, Personal Digital Assistants (PDAs), smart phones, tablets, sensors equipped with a UE, Laptop Mounted Equipment (LME) (e.g. USB), Laptop Embedded Equipments (LEEs), Machine Type Communication (MTC) devices, or Machine to Machine (M2M) device, Customer Premises Equipment (CPE), target device, device-to-device (D2D) wireless device, wireless device capable of machine to machine (M2M) communication.

As part of the developing of the embodiments described herein, it has been realized that there currently exist certain challenge(s) with the <NUM>-tpt-counter. In fact, the definition of the <NUM>-tpt-counter include at least two major flaws.

<FIG> shows a throughput distribution from the <NUM>-tpt-counter which comprise at least two major flaws which both lead to a strong biases in the throughput distribution from the <NUM>-tpt-counter. These are denoted as area/flaw A and area/flaw B in <FIG>. Each flaw by itself and both flaws in combination may result in a drastic underestimation of average values, such as, e.g., median, 90th percentile, etc., that operators commonly derive from the throughput distribution from the <NUM>-tpt-counter. These are then used as input to decision making about aspects in the wireless communications network, such as, e.g. how and where to perform capacity expansion.

In realizing flaw A in the throughput distribution from the <NUM>-tpt-counter, it is noted that flaw A reveals that a certain kind of RRC connections is not considered at all by the <NUM>-tpt-counter. These are RRC connections where the per UE buffer was never non-empty. At the same time, these are RRC connections that in most cases would have resulted in a large throughput value had the UE buffer been non-empty at least once. This flaw A may create a strong bias, i.e. area/flaw A in <FIG>, in the throughput distribution because a relatively great number of RRC connections are probably of this kind.

In realizing flaw B in the throughput distribution from the <NUM>-tpt-counter, it is noted that flaw B may be described as "too little data in too much time" and is the result of the fact that the smallest unit of time over which throughput may be calculated in LTE is the so-called Transmission-Time-Interval, TTI, of <NUM>. This flaw B may also create a strong bias, e.g. area/flaw B in <FIG>, in the throughput distribution. More specifically, the <NUM>-tpt-counter may also include RRC connections that are too small in terms of the data volume and/or in terms of the time, which are both the input values to calculate the mentioned throughput value. Those RRC connections may not be observed by the system long enough to measure the mentioned throughput value with sufficient reliability, as denoted by the area/flaw B in <FIG>.

Embodiments described herein provide solutions to the challenges described above with reference to <FIG>. In other words, by excluding throughput values that are based on too little data and/or too little time may provide advantageous effects to overcome the flaws A and B, as described above with reference to <FIG>, when determining data throughput distribution in a base station in wireless communications network. In the embodiments described below, a description of counters and attributes thereof are provided. The counters described in the embodiments herein may also be referred to as filtered user equipment throughput counters.

Examples of embodiments of a method performed by a base station <NUM> for operating a data throughput counter in a wireless communications network <NUM> will now be described with reference to the flowchart depicted in <FIG> is an illustrated example of actions or operations which may be taken by the base station <NUM> in the wireless communication network <NUM>. The method may comprise the following actions.

The base station <NUM> determines a number of data throughput values over a determined period of time, wherein each determined data throughput value represents the data throughput associated with data transferred during a Radio Resource Connection, RRC, connection or part thereof. Here, it should be noted that in <NUM>, and potentially also in <NUM>, there is a suspend resume procedure where an RRC connection can be very long and interrupted by a suspend and then resume. In these cases, the individual parts may, according to embodiments herein, be treated as their own sessions with a measurement for each sub part. In other words, each determined data throughput value may also represents the data throughput associated with data transferred during a session. For both <NUM>, such as, e.g. an LTE network, and <NUM>, such as, e.g. a New Radio (NR) network, this would then mean one individual throughput value per session. However, in <NUM>, it should be noted that one RRC connection may contain one or more sessions. In more detailed, this may also be described as one individual throughput value for each session that had at least one transmission period with a non-empty buffer. Here, it should be noted that the data transfer may be performed in a downlink, DL, direction or uplink, UL, direction in the wireless communication network <NUM>.

After the determination in Action <NUM>, the base station <NUM> increments the data throughput counter based on those determined throughput values for which the amount of data transferred is above a first threshold value, and/or for which the transport time of said amount of data is above a second threshold value. This enables a data throughput distribution or a characteristic total throughput value as described in Actions <NUM>-<NUM> below to be obtained. In other words, the base station <NUM> may increment the data throughput counter based only, i.e. explicitly, on those determined throughput values for which the amount of data transferred is above a first threshold value, and/or for which the transport time of said amount of data is above a second threshold value. Here, the term "incrementing" the data throughput counter also may be referred to as stepping, clocking, or pegging the data throughput counter.

According to some embodiments, the amount of data may be associated with a Packet Data Convergence Protocol, PDCP, data volume in a UE session, and wherein the first threshold value may be a PDCP data volume threshold. In some embodiments, the amount of data may be associated with a Radio Link Control, RLC, data volume in a UE session, and wherein the first threshold value may be a RLC data volume threshold. In some embodiments, the amount of data may be associated with a Medium Access Control, MAC, data volume in a UE session, and wherein the first threshold value may be a MAC data volume threshold. The examples listed above should be considered as mere examples, and not as an exclusive list of alternatives for which amount of data is to be considered. Further, the transport time may be a portion of the time that a RRC connection is active. In some embodiments, the portion of the time that the RRC connection is active may correspond to the time during which a data buffer associated with the mentioned RRC connection is non-empty.

Optionally, after the incrementing of the data throughput counter in Action <NUM>, the base station <NUM> may obtain a data throughput distribution based on the output of the data throughput counter. This means that a data throughput distribution is established based on determined throughput values for which the amount of data transferred is above a first threshold value, and/or for which the transport time of said amount of data is above a second threshold value.

It should here be noted that the above description does not exclude the possibility of using determined throughput values for which the amount of data transferred is above a first threshold value and for which the transport time of said amount of data is above a second threshold value, together with determined throughput values that only fulfils one of these criteria in order to obtain the total throughput distribution. In other words, the total throughput distribution may be a function of the output of the data throughput counter where there are values based on the throughput values that exceeds both the first and second thresholds, and additionally also a number of values which exceeds the first threshold, but not the second threshold, or vice versa.

After the incrementing of the data throughput counter in Action <NUM>, the base station <NUM> determines a characteristic total throughput value based on the output of the data throughput counter. This means that a characteristic total throughput value is established based on determined throughput values for which the amount of data transferred is above a first threshold value, and/or for which the transport time of said amount of data is above a second threshold value. The characteristic total throughput value comprises any one of an average value, a median value, a percentile value.

Also here, it should be noted that the above description does not exclude the possibility of using determined throughput values for which the amount of data transferred is above a first threshold value and for which the transport time of said amount of data is above a second threshold value, together with determined throughput values that only fulfils one of these criteria in order to obtain the characteristic total throughput value. In other words, the characteristic total throughput value may be a function of the output of the data throughput counter where there are values based on the throughput values that exceeds both the first and second thresholds, and additionally also a number of values which exceeds the first threshold, but not the second threshold, or vice versa.

According to some embodiment, the base station <NUM> may transmit information indicating the output of the data throughput counter, the obtained data throughput distribution, and/or the determined characteristic total throughput value. The base station may, for example, transmit to a network node in the wireless communications network <NUM>. Optionally, in some embodiments, the base station <NUM> may also obtain user data and forward the user data to a host computer or a wireless device.

Examples of embodiments of the method performed by a base station <NUM> for operating a data throughput counter in a wireless communications network <NUM> described with reference <FIG> will now be described with reference to the flowchart depicted in <FIG> is an illustrated example of actions or operations which may be taken by the base station <NUM> in the wireless communication network <NUM>.

In other words, <FIG> is a flow chart illustrating some embodiments of a method for operating a data throughput counter in a wireless communications network, and exemplifies in which order the different conditions may be evaluated and respective counters may be pegged. Here, it may be noted that the fifth counter, referred to as pmUeThpDIMbbFilteredDistr in <FIG>, is a counter which may operate as a replacement of the implementation of the <NUM>-tpt-counter in the base station <NUM>. MBB may refer to Mobile Broadband, PDCP may refer to Packet Data Convergence Protocol, and DRB may refer to Data Radio Bearer. The method may comprise the following actions.

Initiation of the procedure may begin at the end of each UE data session or radio opportunity, ROP.

After initiation, the base station <NUM> may determine if the data session is associated with a VoIP service. If YES (Y), then the base station proceeds to Action <NUM>. Otherwise, the base station <NUM> proceeds to Action <NUM>.

The base station <NUM> may here increment a first counter, referred to here as pmUeExcIThpDIVolte This may be performed when a specific condition is fulfilled. The specific condition may, for example, be that the UE data session contains QCI1 DRB. The first counter, pmUeExcIThpDIVolte, may be implemented to keep track of the number of user equipment (UEs), i.e. wireless devices, that are excluded from DL throughput calculation due to VoLTE traffic.

After incrementing of the first counter in Action <NUM>, the base station <NUM> may determine if the PDCP volume of the UE data session is below a certain volume threshold. If NO (N), then the base station <NUM> may proceed to Action <NUM>. Otherwise, the base station <NUM> may proceed to Action <NUM> and end the procedure.

After the determination in Action <NUM>, the base station <NUM> may increment a second counter, referred to as pmUeExclThpDlVolteMbb. This may be performed when a specific condition is fulfilled. The specific condition may, for example, be when all PDCP volume except QCI1 in the UE data session is greater than a threshold value. The second counter, pmUeExclThpDlVolteMbb, may be implemented to keep track of the number of user equipment (UEs), i.e. wireless devices, that are excluded from DL throughput calculation due to VoLTE traffic but with simultaneous sizable MBB traffic. The base station <NUM> may then proceed to Action <NUM> and end the procedure.

After determining that the UE data session is not a VoIP service, the base station <NUM> may determine if a session PDCP volume of the UE data session is below a certain volume threshold. For example, an attribute filterUeDIThpVolThr = <NUM> {<NUM>. <NUM>} may define a PDCP volume threshold for fifth counter pmUeThpDIMbbFilteredDistr in Action <NUM> below. This means that a UE data session with PDCP volume less than this threshold is filtered out.

If YES (Y), then the base station <NUM> may proceed to Action <NUM>. Otherwise, the base station <NUM> proceed to Action <NUM>.

The base station <NUM> may here increment a third counter, referred to here as pmUeExclThpDlSmallVol. This may be performed when a specific condition is fulfilled. The specific condition may, for example, be that the UE data session PDCP volume is less than a data volume threshold. The third counter, pmUeExclThpDlSmallVol, may be implemented to keep track of the number of MBB user equipment (UEs), i.e. wireless devices, that are excluded from DL throughput calculation due to small data volume. The base station <NUM> may proceed to Action <NUM> and end the procedure.

After determining that the PDCP volume of the UE data session is above a certain volume threshold in Action <NUM>, the base station <NUM> may determine if a session transport time of the UE data session is below a certain time threshold. For example, an attribute filterUeDIThpTimeThr= <NUM> {<NUM>. <NUM>} may define DRB transport time threshold for the fifth counter pmUeThpDIMbbFilteredDistr in Action <NUM> below. This means that a UE data session with DRB transport time less than this threshold is filtered out.

The base station <NUM> may here increment a fourth counter, referred to here as pmUeExcIThpDIShortDrb. This may be performed when a specific condition is fulfilled. The specific condition may, for example, be that the UE data session time is less than a DRB time threshold. The fourth counter, pmUeExcIThpDIShortDrb, may be implemented to keep track of the number of MBB user equipment (UEs), i.e. wireless devices, that are excluded from DL throughput calculation due to short transport time. The base station <NUM> may then proceed to Action <NUM> and end the procedure.

After determining that the session transport time of the UE data session is above a certain time threshold in Action <NUM>, the base station <NUM> may increment a fifth counter, referred to here as pmUeThpDIMbbFilteredDistr. This may be performed when a specific condition is fulfilled. The specific condition may, for example, be when the UE session is MBB only, and both the PDCP volume and the DRB time are bigger than their respective thresholds. The fifth counter, pmUeThpDIMbbFilteredDistr, may be implemented to obtain a distribution of the filtered MBB UE DL throughput, i.e. e.g. obtain a throughput distribution as described in Action <NUM> or determine a characteristic total throughput value as described in Action <NUM>. The base station <NUM> may then proceed to Action <NUM> and end the procedure.

To perform the method actions in a base station <NUM> for operating a data throughput counter in a wireless communications network <NUM>, the base station <NUM> may comprise the following arrangement depicted in <FIG> shows a schematic block diagram of embodiments of a virtual apparatus <NUM> that may be implemented in base station <NUM>.

<FIG> illustrates a schematic block diagram of embodiments of an apparatus <NUM> in a wireless communications network <NUM> (for example, the wireless network shown in <FIG> or <FIG>). The apparatus <NUM> may be implemented in a base station or network node <NUM> (e.g. the network node QQ160 shown in <FIG>). Apparatus <NUM> is operable to carry out the example method described with reference to <FIG>, and possibly any other processes or methods disclosed herein. It is also to be understood that the method of <FIG> is not necessarily carried out solely by apparatus <NUM>. At least some operations of the method can be performed by one or more other entities.

Apparatus <NUM>, also referred to as a virtual apparatus implemented in a base station, may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause a determining unit <NUM> and a incrementing unit <NUM>, and any other suitable units of apparatus <NUM> to perform corresponding functions according one or more embodiments of the present disclosure.

The base station <NUM> or processing circuitry therein is configured to, or may comprise the determining unit <NUM> configured to, determining a number of data throughput values over a determined period of time, wherein each determined data throughput value represents the data throughput associated with data transferred during a Radio Resource Connection, RRC, connection or part thereof. Also, the base station <NUM> or processing circuitry therein is configured to, or may comprise the incrementing unit <NUM> configured to, incrementing (also referred to as stepping, clocking or pegging) the data throughput counter based on those determined throughput values for which the amount of data transferred is above a first threshold value, and/or for which the transport time of said amount of data is above a second threshold value.

In some embodiments, the amount of data is associated with a Packet Data Convergence Protocol, PDCP, data volume in a UE session, and wherein the first threshold value is a PDCP data volume threshold. Alternatively, the amount of data is associated with a Radio Link Control, RLC, data volume in a UE session, and wherein the first threshold value is a RLC data volume threshold. Another option may be that the amount of data is associated with a Medium Access Control, MAC, data volume in a UE session, and wherein the first threshold value is a MAC data volume threshold. Also, according to some embodiments, the transport time is a portion of the time that a RRC connection is active. In this case, according to some embodiments, the portion of the time that the RRC connection is active corresponds to the time during which a data buffer associated with the mentioned RRC connection is non-empty.

In some embodiments, the base station <NUM> or processing circuitry therein may be configured to, or may comprise an obtaining unit <NUM> configured to, obtain a data throughput distribution based on the output of the data throughput counter. In some embodiments, the base station <NUM> or processing circuitry therein may be configured to, or may comprise the determining unit <NUM> configured to, determine a characteristic total throughput value based on the output of the data throughput counter. In some embodiments, the base station <NUM> or processing circuitry therein may be configured to, or may comprise an transmitting unit <NUM> configured to, transmit, to a network node in the wireless communications network <NUM>, information indicating the output of the data throughput counter, the obtained data throughput distribution, and/or the determined characteristic total throughput value. In some embodiments, the data transfer may be performed in an downlink, DL, direction or uplink, UL, direction in the wireless communication network <NUM>.

The description of the example embodiments provided herein have been presented for purposes of illustration. The description is not intended to be exhaustive or to limit example embodiments to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of various alternatives to the provided embodiments. The examples discussed herein were chosen and described in order to explain the principles and the nature of various example embodiments and its practical application to enable one skilled in the art to utilize the example embodiments in various manners and with various modifications as are suited to the particular use contemplated. The features of the embodiments described herein may be combined in all possible combinations of methods, apparatus, modules, systems, and computer program products. It should be appreciated that the example embodiments presented herein may be practiced in any combination with each other.

It should also be noted that the various example embodiments described herein are described in the general context of method steps or processes, which may be implemented in one aspect by a computer program product, embodied in a computer-readable medium, including computer-executable instructions, such as program code, executed by computers in networked environments. A computer-readable medium may include removable and non-removable storage devices including, but not limited to, Read Only Memory (ROM), Random Access Memory (RAM), compact discs (CDs), digital versatile discs (DVD), etc. Generally, program modules may include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in <FIG>. For simplicity, the wireless network of <FIG> only depicts network QQ106, network nodes QQ160 and QQ160b, and WDs QQ110, QQ110b, and QQ110c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node QQ160 and wireless device (WD) QQ110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node QQ160 and WD QQ110 comprise various components described in more detail below.

In <FIG>, network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162. Although network node QQ160 illustrated in the example wireless network of <FIG> may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. Moreover, while the components of network node QQ160 are 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 medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node QQ160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node QQ160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. In some embodiments, network node QQ160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium QQ180 for the different RATs) and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs). Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ160.

Processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, 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.

Processing circuitry QQ170 may 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 node QQ160 components, such as device readable medium QQ180, network node QQ160 functionality. For example, processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. In some embodiments, processing circuitry QQ170 may include a system on a chip (SOC).

In some embodiments, processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.

Device readable medium QQ180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ170. Device readable medium QQ180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ170 and, utilized by network node QQ160. Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190. In some embodiments, processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.

Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170. Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170. Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192. The digital data may be passed to processing circuitry QQ170.

In certain alternative embodiments, network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190. In still other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, <NUM> and <NUM>. In certain embodiments, antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node.

Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160. For example, network node QQ160 may 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 circuitry QQ187. As a further example, power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187.

Alternative embodiments of network node QQ160 may include additional components beyond those shown in <FIG> that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc.. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device QQ110 includes antenna QQ111, interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137. WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ110.

Antenna QQ111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111 may be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port. Antenna QQ111, interface QQ114, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. In some embodiments, radio front end circuitry and/or antenna QQ111 may be considered an interface.

As illustrated, interface QQ114 comprises radio front end circuitry QQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111 and processing circuitry QQ120. Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ111. In some embodiments, WD QQ110 may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ111. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122 may be considered a part of interface QQ114. Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ118 and/or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120.

Processing circuitry QQ120 may 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 WD QQ110 components, such as device readable medium QQ130, WD QQ110 functionality. For example, processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.

As illustrated, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In certain embodiments processing circuitry QQ120 of WD QQ110 may comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122 may be a part of interface QQ114. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end users and the wireless network generally.

Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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.

Device readable medium QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120. Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120. In some embodiments, processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated.

User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is 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 equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may 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 equipment QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110. User interface equipment QQ132 may 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 equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. 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 equipment QQ134 may vary depending on the embodiment and/or scenario.

Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any functionality described or indicated herein. Power circuitry QQ137 may in certain embodiments comprise power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may 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 circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.

UE QQ2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE QQ200, as illustrated in <FIG>, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or <NUM> standards.

In <FIG>, UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231, power source QQ233, and/or any other component, or any combination thereof. Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information.

In <FIG>, processing circuitry QQ201 may be configured to process computer instructions and data. Processing circuitry QQ201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ201 may include two central processing units (CPUs).

In the depicted embodiment, input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE QQ200 may be configured to use an output device via input/output interface QQ205. For example, a USB port may be used to provide input to and output from UE QQ200. UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200.

In <FIG>, RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a. Network QQ243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243a may comprise a Wi-Fi network. Network connection interface QQ211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface QQ211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 to 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. ROM QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219 may 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 medium QQ221 may 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 medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227. Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.

Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium QQ221 may allow UE QQ200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221, which may comprise a device readable medium.

In <FIG>, processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231. Network QQ243a and network QQ243b may be the same network or networks or different network or networks. Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may 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 WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE <NUM>. QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200. The features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200 or partitioned across multiple components of UE QQ200. In one example, communication subsystem QQ231 may be configured to include any of the components described herein.

Further, processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231.

<FIG> is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized.

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more of hardware nodes QQ330.

The functions may be implemented by one or more applications QQ320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment QQ300, comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory QQ390-<NUM> which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360. Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380. Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-<NUM> having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360. Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines QQ340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.

During operation, processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.

As shown in <FIG>, hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.

In the context of NFV, virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines QQ340, and that part of hardware QQ330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines QQ340 on top of hardware networking infrastructure QQ330 and corresponds to application QQ320 in Figure QQ3. In some embodiments, one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225. Radio units QQ3200 may communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signalling can be effected with the use of control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.

With reference to <FIG>, in accordance with an embodiment, a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411, such as a radio access network, and core network QQ414. Access network QQ411 comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412c is connectable to core network QQ414 over a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c. A second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491, QQ492 are 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 station QQ412.

The communication system of <FIG> as a whole enables connectivity between the connected UEs QQ491, QQ492 and host computer QQ430. The connectivity may be described as an over-the-top (OTT) connection QQ450. Host computer QQ430 and the connected UEs QQ491, QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ411, core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries. OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications. For example, base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491. Similarly, base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491 towards the host computer QQ430.

In communication system QQ500, host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500. Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities. In particular, processing circuitry QQ518 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. Host computer QQ510 further comprises software QQ511, which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518. Software QQ511 includes host application QQ512. Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.

Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530. Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in <FIG>) served by base station QQ520. Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510. Connection QQ560 may be direct or it may pass through a core network (not shown in <FIG>) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, 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 station QQ520 further has software QQ521 stored internally or accessible via an external connection.

Communication system QQ500 further includes UE QQ530 already referred to. Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, 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. UE QQ530 further comprises software QQ531, which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532. Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510. In host computer QQ510, an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the user, client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data. OTT connection QQ550 may transfer both the request data and the user data. Client application QQ532 may interact with the user to generate the user data that it provides. It is noted that host computer QQ510, base station QQ520 and UE QQ530 illustrated in <FIG> may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412c and one of UEs QQ491, QQ492 of <FIG>, respectively.

In <FIG>, OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection QQ570 between UE QQ530 and base station QQ520 is 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 UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments may improve the monitoring of user experience (which e.g. may be used by operators to decide whether a certain eNodeB/gNodeB should get upgraded with more capacity, for example, by adding an additional radio carrier, and thereby provide benefits such as reduced user waiting time.

In step QQ610, the host computer provides user data. In substep QQ611 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

In step QQ710 of the method, the host computer provides user data. In step QQ720, the host computer initiates a transmission carrying the user data to the UE. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission.

In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application. In substep QQ811 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

In step QQ910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step QQ920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

Claim 1:
A method performed by a base station (<NUM>) for operating a data throughput counter in a wireless communications network (<NUM>), the method comprising:
- determining (<NUM>) a number of data throughput values over a determined period of time, wherein each determined data throughput value represents the data throughput associated with data transferred during a Radio Resource Connection, RRC, connection or part thereof;
- incrementing (<NUM>) the data throughput counter based on those determined throughput values for which the amount of data transferred is above a first threshold value, and/or for which the transport time of said amount of data is above a second threshold value; and
- determining (<NUM>) a characteristic total throughput value based on the output of the data throughput counter, wherein the characteristic total throughput value comprises any one of an average value, a median value or a percentile value.