Improved uplink low layer separation supporting advanced CoMP

Abstract

Methods and systems for implementing or assisting joint equalization, DMRS-based joint equalization, or maximum ratio merging are described. In some embodiments, when indicated by a scheduler, the DU requests the RU to transmit both the equalized DMRS symbol and the equalized data symbol. The DU may estimate the effective channel using the equalized DMRS symbols, including the equalization performed in the RU. The DU then uses the effective channel estimation to perform joint equalization or DMRS-based joint equalization on the equalized data symbols received from the one or more RUs.

Description

[0001] Cross-referencing of relevant information

[0002] This application claims the benefit of U.S. Priority Application No. 63 / 457,021, filed April 4, 2023, entitled “An improved uplink lower layer split supporting advanced CoMP”. Technical Field

[0003] This disclosure generally relates to systems and methods for demodulation and equalization. Background Technology

[0004] Massive MIMO technology was initially implemented in LTE. In 5G, it becomes a key technology component, and will be deployed on a much larger scale than in LTE. It is characterized by the use of a large number of antennas on the base station side, where the number of antennas is typically much greater than the number of user layers. For example, in Frequency Range 1 (FR1), which covers the band of 410-7125 MHz, 64 antennas serve 8 or 16 user layers, and in FR2, which covers the band of 24.25 GHz-71 GHz, 256 / 512 antennas serve 2 or 4 layers. When used herein, a user layer refers, for example, to an independent downlink or uplink data stream intended for a single user. A user or UE (User Equipment) can have one or more user layers. In 3GPP terminology, for example, a user layer is also referred to as a layer. Massive MIMO is also known as massive beamforming, which enables the formation of narrow beams focused in different directions to compensate for increased path loss at higher frequency bands. It also benefits multi-user MIMO, which allows simultaneous transmission to / from multiple users on a single spatial channel resolved by massive MIMO technology, while maintaining high capacity for each user. Therefore, it can significantly increase spectral efficiency and cell capacity.

[0005] At the base station side, the interface between the Distributed Unit (DU) and the Radio Unit (RU) is the fronthaul interface. The huge benefits of massive MIMO at the air interface also introduce new challenges at the base station side. The traditional CPRI-type fronthaul transmits time-domain IQ samples per antenna branch. With the number of antennas in massive MIMO systems increasing proportionally, the required fronthaul capacity also increases proportionally, which significantly increases the fronthaul cost. To address this challenge, the fronthaul interface evolved from CPRI (Common Public Radio Interface) to eCPRI (enhanced or evolved CPRI), i.e., a packet-based fronthaul interface. In eCPRI, other functional separation options between the DU and the RU are supported, referred to as different Low Layer Separation (LLS) options. In the eCPRI standard, the terms eREC (eCPRI Radio Equipment Control) and eRE (eCPRI Radio Equipment) are used instead of DU and RU. The basic idea is to move the frequency-domain beamforming functionality from the DU to the RU, such that the user layers’ frequency samples or data are transmitted over the fronthaul interface. Note that frequency-domain beamforming is sometimes also referred to as precoding in the downlink (DL) direction. More details on possible implementations regarding uplink frequency-domain beamforming will be described below. In this way, the required fronthaul capacity and thus the fronthaul cost are significantly reduced, since the number of user layers is typically much smaller than the number of antennas in massive MIMO. In O-RAN, the DU is referred to as O-DU, while the RU is referred to as O-RU.

[0006] The present disclosure focuses on the uplink direction of the fronthaul interface. Figure 1 An implementation of the UL specification in the O-RAN WG4 standard is shown. By having the beamforming functionality in the O-RU, the number of streams going through the fronthaul interface becomes smaller than the number of antenna branches. However, the beamforming weights are calculated in the O-DU based on SRS (Sounding Reference Signal) signals sent back from the O-RU. Since the SRS channel estimation corresponds to an earlier channel, in order to avoid performance loss compared to using a CPRI-based fronthaul, the number of required streams is still much larger than the number of layers. There is a trade-off between the number of streams used and performance.

[0007] Therefore, O-RAN WG4 is currently studying to improve the current specification by introducing a new UL functional split to achieve the best performance using the minimum fronthaul bitrate, i.e., to reduce the number of streams to the number of layers. There are two solutions proposed to achieve this improvement. Solution A is shown in Figure 2 Solution B is shown in Figure 3Both solutions move the DMRS channel estimation and beamforming weight calculation to the O-RU. One difference is that solution A has the equalization in the O-RU, while solution B has the equalization in the O-DU. The second difference is that solution A does not send DMRS from the O-RU to the O-DU, while solution B sends DMRS from the O-RU to the O-DU. Instead, solution A sends SINR information from the O-RU to the O-DU to help the O-DU demodulate the equalized symbols. The SINR information represents, for example, the measured / estimated SINR value per layer per PRB (Physical Resource Block), which is used by the demodulator to demodulate the symbols per layer per subcarrier, for example, a LLR (Log Likelihood Ratio) based demodulation algorithm. The equalized symbols are commonly referred to as soft values in demodulation terminology. The third difference is that solution B does a second channel estimation in the O-DU to calculate the equalization weights in the O-DU, while solution A directly uses the received SINR information to demodulate the equalized symbols, so that there is no need to do channel estimation again in the O-DU.

[0008] In wireless communications, an equalizer performs equalization on an input signal, which counteracts distortion caused by an end-to-end channel including a transmitter chain, an over-the-air channel (including a desired channel and interference channels), and a receiver chain. After equalization, the equalized signal can be demodulated by a demodulator. When the input signal comes from multiple transmitters sending different data, the equalizer can also mitigate interference among them. An equalizer can be linear or nonlinear. Examples of linear equalizers are a zero-forcing equalizer, an MMSE equalizer, etc. Examples of nonlinear equalizers are a decision feedback equalizer, etc.

[0009] Applicant believes that solution A is a better solution than solution B. Solution A has the following advantages:

[0010] The interface between equalization and demodulation used in solution A is well known. The O-RU and the O-DU can be tested separately. It requires much less integration effort than solution B. In solution B, the equalization weights and the beamforming weights are calculated in different units (i.e., O-DU and O-RU) respectively. This creates algorithm dependency. This will cause interoperability issues between the O-RU and the O-DU due to the ignorance of the algorithm used by the other side. The performance cannot be guaranteed. Therefore, the testing and integration complexity is significantly increased.

[0011] Solution A does not send DMRS symbols over the fronthaul interface. This further reduces the fronthaul bitrate.

[0012] However, it can be believed that when the DU is connected to multiple RUs (as in Figure 1), the SINR information from the O-RU to the O-DU is not sufficient to demodulate the equalized symbols. The O-DU needs to know the DMRS symbols to demodulate the equalized symbols.Figure 4 Solution B can better support CoMP (Coordinated Multi-Point) (see also for the dual RU example). A CoMP receiver at the DU can utilize the signals received from multiple RUs for the same UE to improve performance.

[0013] Figure 5 A CoMP implementation of Solution A is shown. This implementation is also referred to as MRC (Maximum Ratio Combining) CoMP. The equalized symbols from different RUs, which have been made in phase by the equalizer in each RU, are scaled based on the received SINR information and then combined before demodulation. In this way, maximum ratio combining can be achieved. In this implementation, the performance is improved from diversity gain due to the equalized signals, where more energy is available for demodulation after combining.

[0014] Figure 6 A CoMP implementation of Solution B is shown. Joint equalization is utilized in the DU with beamformed signals from both RUs. In this way, the signal dimension is expanded. The expanded dimension is used by the joint equalizer to further mitigate interference and obtain more energy. This is a more advanced CoMP than MRC CoMP. Thus, this advanced CoMP can achieve better performance than MRC CoMP.

[0015] There are certain challenges. Solution A, which improves the UL functional split, cannot support advanced CoMP, although it has other advantages over Solution B. SUMMARY

[0016] One embodiment of the present disclosure includes a method implemented by a DU for implementing equalization. The method includes requesting one or more equalized DMRS symbols and one or more equalized data symbols from one or more radio units, receiving the one or more equalized DMRS symbols and the one or more equalized data symbols, implementing one or more channel estimates based at least in part on the one or more equalized DMRS symbols, implementing equalization of the one or more equalized data symbols based at least in part on the one or more channel estimates, computing one or more SINR data, and implementing demodulation and decoding of the one or more equalized data symbols based at least in part on the one or more SINR data.

[0017] Another embodiment is a method implemented by a DU for implementing DMRS-based joint equalization. The method includes receiving scheduling information from a scheduler. Next, if the scheduling information indicates that DMRS-based joint equalization is used, then the following steps are implemented; requesting one or more equalized DMRS symbols and one or more equalized data symbols from one or more radio units; receiving the one or more equalized DMRS symbols and the one or more equalized data symbols; implementing one or more channel estimates based at least in part on the one or more equalized DMRS symbols; implementing equalization of the one or more equalized data symbols based at least in part on the one or more channel estimates; computing a first one or more SINR data; and implementing demodulation and decoding of the one or more equalized data symbols based at least in part on the first one or more SINR data. If the scheduling information does not indicate that DMRS-based joint equalization is used, then the method includes implementing the following steps; requesting the one or more equalized data symbols and a second one or more SINR data from the one or more radio units; receiving the one or more equalized data symbols and the second one or more SINR data; and if the scheduling information indicates MRC CoMP, then implementing MRC CoMP and demodulation; and if the scheduling information does not indicate MRC CoMP, then implementing demodulation separately for each of the one or more radio units.

[0018] Another embodiment is a method implemented by a DU for implementing DMRS-based joint equalization. The method includes requesting one or more equalized DMRS symbols and one or more equalized data symbols from one or more radio units; and receiving the one or more equalized DMRS symbols and the one or more equalized data symbols.

[0019] Another embodiment includes a method implemented by an RU for assisting DMRS-based joint equalization in a DU. The method includes receiving a request from a distributed unit for one or more equalized DMRS symbols and one or more equalized data symbols; equalizing one or more DMRS symbols and one or more data symbols to create the one or more equalized DMRS symbols and the one or more equalized data symbols; and sending the one or more equalized DMRS symbols and the one or more equalized data symbols to the DU for use by the DU for channel estimation and equalization.

[0020] Another embodiment includes a method for assisting DMRS-based joint equalization in a DU implemented by one or more RUs, wherein the DU has received scheduling information from a scheduler. The method includes: if the scheduling information indicates to use joint equalization, then the one or more RUs implement the following steps; receiving a request from the DU for one or more equalized DMRS symbols and one or more equalized data symbols; equalizing one or more DMRS symbols and one or more data symbols to create the one or more equalized DMRS symbols and the one or more equalized data symbols; and sending the one or more equalized DMRS symbols and the one or more equalized data symbols to the DU for use by the DU for channel estimation and DMRS-based joint equalization. If the scheduling information does not indicate to use joint equalization, then the RUs implement the following steps: receiving a request from the DU for the one or more equalized data symbols and one or more SINR data; equalizing one or more DMRS symbols and one or more data symbols to create the one or more equalized DMRS symbols and the one or more equalized data symbols; and sending the one or more equalized data symbols and one or more SINR data to the DU, wherein the one or more equalized data symbols and one or more SINR data: are used for MRC CoMP and demodulation in case the scheduling information indicates MRC CoMP; and are used for implementing demodulation individually for each RU including the one or more RUs in case the scheduling information does not indicate MRC CoMP.

[0021] This summary is provided to introduce some concepts of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an indication of the scope of the claimed subject matter. BRIEF DESCRIPTION OF DRAWINGS

[0022] For a more complete understanding of this disclosure, reference is now made to the following description taken in conjunction with the accompanying drawings in which:

[0023] Figure 1 The current UL specification for O-RAN WG4 is shown;

[0024] Figure 2 Solution A for improved UL function split is shown;

[0025] Figure 3 Solution B for improved UL function split is shown;

[0026] Figure 4 An example of two RUs connected to one DU is shown;

[0027] Figure 5 MRC CoMP implementation for the dual RU example is shown for solution A;

[0028] Figure 6 High level CoMP implementation for the dual RU example is shown for solution B;

[0029] Figure 7 A possible method embodiment for high level CoMP implementation for improved solution A for the dual RU example according to the present disclosure is shown;

[0030] Figure 8 A flow diagram of the improved solution A of the present disclosure is shown;

[0031] Figure 9 Simulation results for 2 RUs and 64 antennas per RU are shown;

[0032] Figure 10 Simulation results for 2 RUs and 16 antennas per RU are shown;

[0033] Figure 11 A flow diagram of a method embodiment according to the present disclosure is shown;

[0034] Figure 12 A flow diagram of a method embodiment according to the present disclosure is shown;

[0035] Figure 13 A flow diagram of a method embodiment according to the present disclosure is shown;

[0036] Figure 14 A flow diagram of a method embodiment according to the present disclosure is shown;

[0037] Figure 15 A flow diagram of a method embodiment according to the present disclosure is shown;

[0038] Figure 16 A schematic diagram of a communication system embodiment according to the present disclosure is shown;

[0039] Figure 17 A schematic diagram of a user equipment embodiment according to the present disclosure is shown;

[0040] Figure 18 A schematic diagram of a network node embodiment according to the present disclosure is shown;

[0041] Figure 19 A schematic diagram of a host computer embodiment according to the present disclosure is shown;

[0042] Figure 20 A schematic diagram of a virtualization environment embodiment according to the present disclosure is shown; and

[0043] Figure 21 A schematic representation of embodiments of communication between nodes, hosts, and user equipment according to the present disclosure is shown. DETAILED DESCRIPTION

[0044] Before describing various embodiments of the disclosure in detail, it is to be understood that the disclosure is not limited in scope to the particular examples described herein, which can of course vary. Thus, while it will be described in detail and with reference to specific configurations, parameters, components, elements and / or the like, these are described with the intent that they be illustrative only, and not limiting to the scope of the embodiments claimed. Additionally, the terminology employed herein is for the purpose of describing embodiments and is not intended to be limiting.

[0045] As noted above, there are certain challenges. Solution A of improved UL functional split cannot support advanced CoMP, although it has other advantages over solution B. In the present disclosure, methods and systems are presented to extend solution A to support advanced CoMP more advanced than MRC CoMP, where a joint equalizer is enabled in the DU to further improve performance.

[0046] Certain aspects of the present disclosure and embodiments thereof can provide solutions to these or other challenges. In certain embodiments, when the scheduler decides to use advanced CoMP, the DU requests both the equalized DMRS symbols and the equalized data symbols to be sent by the RUs. The DU uses the equalized DMRS symbols to estimate the effective channel, including the equalization done in the RUs. Then, the DU implements joint equalization on the equalized data symbols received from the multiple RUs using the effective channel estimate. When the scheduler decides to use MRC CoMP or no CoMP, the DU only requests the equalized data symbols. Certain embodiments are described further below, including in the flowchart of FIG. 1 and the description of FIG. 2. Figure 8 Certain embodiments are described further below, including in the flowchart of FIG. 1 and the description of FIG. 2. Figure 7 Certain embodiments are described further below, including in the flowchart of FIG. 1 and the description of FIG. 2.

[0047] Certain embodiments can provide one or more of the following technical advantages. Certain embodiments presented extend solution A to support advanced CoMP more advanced than MRC to further improve performance. The joint equalization enabled by the presented embodiments is able to exploit the expanded signal dimension for performance improvement. Simulation results show that embodiments of the present disclosure are able to achieve the same CoMP performance as solution B. The improved solution A is able to achieve such performance by doing advanced CoMP processing only as needed. The overall complexity is lower than solution B, since solution B has to do additional channel estimation in the DU all the time.

[0048] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. The embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. It should be noted that throughout the specification and drawings referenced herein, at certain points, the MMSE (Minimum Mean Square Error) receiver algorithm is given as an example. In fact, the present disclosure is not limited to MMSE receivers or the specific equalization algorithm exemplified. The present disclosure can be applied to other types of receivers and with other equalization algorithms.

[0049] Figure 7 An extended solution A of the present disclosure is shown to support one possible embodiment of advanced CoMP. The system 1000 includes a DU 1015 connected to two RUs 1020, 1025, with a fronthaul interface 1010 at the interface between the DU 1015 and the RUs 1020, 1025. As can be seen, when data is received from the UE, each RU 1020, 1025 implements CP (Cyclic Prefix) removal and FFT (Fast Fourier Transform) at 1030, 1035. The data and DMRS symbols are then sent to MMSE receivers 1070, 1055. At 1040, 1050, the DMRS symbols are obtained from the data stream of data and DMRS symbols, and DMRS channel estimation is implemented at 1045, 1060. When advanced CoMP is used, each RU 1020, 1025 equalizes both the data symbols and the DMRS symbols in the MMSE receivers 1055, 1070. Each RU 1020, 1025 sends the equalized DMRS symbols and the equalized data symbols to the DU 1015. The DU 1015 extracts the equalized DMRS symbols at 1065, and uses the equalized DMRS symbols to estimate the effective channel seen from the DU, i.e., the effective channel from the UE to the DU 1015, including the over-the-air channel and the RU processing (including equalization in the O-RU) at 1075. The channel estimate of the effective channel is then used to compute the weights for a joint equalizer 1080 (which can be a MMSE receiver). The received equalized data symbols are jointly equalized by the joint equalizer 1080. And the jointly equalized data symbols are demodulated at 1085 with the SINR information computed by the joint equalizer. The data can then proceed to decoding at 1090, and other processing as needed. The joint equalizer 1080 can include various equalizer or receiver types.

[0050] Figure 8One embodiment of a method 1200 that supports improved solution A for advanced CoMP in accordance with the present disclosure is shown. At step 1210, the DU receives scheduling information from the scheduler (note that the scheduler is also part of the DU). At step 1220, it is determined whether to use advanced CoMP (e.g., in accordance with embodiments of the present disclosure). Here, advanced CoMP refers to a CoMP receiver that implements joint equalization for received signals from multiple RUs. If the scheduler decides to use advanced CoMP, then at step 1230, the DU requests the RUs to send both equalized DMRS symbols and equalized data symbols. In further steps, the DU implements advanced CoMP processing as described in Figure 7 FIG. 13A, at step 1240, the DU receives both equalized data symbols and DMRS symbols from the multiple RUs. At step 1250, the DU implements channel estimation based on the received DMRS symbols. At step 1260, the DU implements joint equalization and computes SINR information based on the channel estimation. At step 1270, the DU demodulates and decodes the equalized data symbols. Returning to step 1220, if the scheduler decides to use MRC CoMP or not to use CoMP at all, then at step 1280, the DU requests only equalized data symbols and SINR information. Then, the DU implements processing for MRC CoMP as shown in Figure 5 FIG. 13B or processing for non-CoMP as shown in Figure 2 FIG. 13C. For example, at step 1290, for MRC CoMP, the DU then implements MRC CoMP and related demodulation. Alternatively, if CoMP is not used, then at step 1290, the DU implements demodulation separately for different RUs, etc. Note that advanced CoMP is more beneficial when the interference is strong. In cases where the interference is weak, MRC CoMP can exhibit even better performance because the interference information can not be accurately estimated, which would degrade the performance of advanced CoMP.

[0051] Figure 9 and Figure 10 CoMP simulation results for two RUs with eight layers of eight strong interferers are shown. For Figure 9 measurements are taken with 64 antennas per RU. For Figure 10 measurements are taken with 16 antennas per RU. The results show that improved solution A using advanced CoMP achieves the same performance as solution B using advanced CoMP. It is also shown that the performance improvement of advanced CoMP over MRC CoMP decreases as the number of antennas per RU increases.

[0052] Embodiments in accordance with the present disclosure can be implemented in a cloud environment. For example, the DU can be implemented as a virtualized network function running in a cloud environment. Other embodiments can be implemented in an O-RAN or other network embodiment.

[0053] Figure 11 A further possible method embodiment in accordance with the present disclosure is shown, method 1500 comprising a method implemented by a DU for implementing equalization. Step 1510 is requesting one or more equalized DMRS symbols and one or more equalized data symbols from one or more radio units. Step 1520 is receiving the one or more equalized DMRS symbols and the one or more equalized data symbols. Step 1530 is implementing one or more channel estimates based at least in part on the one or more equalized DMRS symbols. Step 1540 is implementing equalization of the one or more equalized data symbols based at least in part on the one or more channel estimates. Step 1550 is computing one or more SINR data. Step 1560 is implementing demodulation and decoding of the one or more equalized data symbols based at least in part on the one or more SINR data. Method 1500 can include a number of variations and embodiments and / or additional and / or alternative steps.

[0054] Figure 12Another possible method embodiment in accordance with the present disclosure is shown. Method 1700 includes a method implemented by a DU for implementing DMRS-based joint equalization. Step 1710 is receiving scheduling information from a scheduler. Next, if the scheduling information indicates joint equalization is used, step 1720 is requesting one or more equalized DMRS symbols and one or more equalized data symbols from one or more radio units. Step 1730 is receiving the one or more equalized DMRS symbols and the one or more equalized data symbols. Step 1740 is implementing one or more channel estimates based at least in part on the one or more equalized DMRS symbols. Step 1750 is implementing equalization of the one or more equalized data symbols based at least in part on the one or more channel estimates. Step 1760 is calculating first one or more SINR data. Step 1770 is implementing demodulation and decoding of the one or more equalized data symbols based at least in part on the first one or more SINR data. If the scheduling information does not indicate joint equalization is used, step 1780 is requesting one or more equalized data symbols and second one or more SINR data from the one or more radio units. Step 1785 is receiving the one or more equalized data symbols and the second one or more SINR data. If the scheduling information indicates MRC CoMP, 1790 is implementing MRC CoMP and demodulation. If the scheduling information does not indicate MRC CoMP, step 1795 is implementing demodulation separately for each of the one or more radio units. Method 1700 can include multiple variations and embodiments and / or additional and / or alternative steps.

[0055] Figure 13 Another possible method embodiment in accordance with the present disclosure is shown. Method 1800 includes a method implemented by a DU for implementing DMRS-based joint equalization. Step 1810 is requesting one or more equalized DMRS symbols and one or more equalized data symbols from one or more radio units. Step 1820 is receiving the one or more equalized DMRS symbols and the one or more equalized data symbols. Method 1800 can include multiple variations and embodiments and / or additional and / or alternative steps.

[0056] Figure 14Another possible method embodiment according to the present disclosure is shown. Method 1900 includes a method implemented by a RU for assisting DMRS-based joint equalization in a DU. Step 1910 is receiving a request from the DU for one or more equalized DMRS symbols and one or more equalized data symbols. Step 1920 is equalizing one or more DMRS symbols and one or more data symbols to create one or more equalized DMRS symbols and one or more equalized data symbols. Step 1930 is sending the one or more equalized DMRS symbols and the one or more equalized data symbols to the DU for use by the DU for channel estimation and equalization. Method 1900 can include multiple variants and embodiments and / or additional steps and / or alternative steps.

[0057] Figure 15 Another possible method embodiment according to the present disclosure is shown. Method 2000 includes a method implemented by one or more RUs for assisting DMRS-based joint equalization in a DU, where the DU has received scheduling information from a scheduler. If the scheduling information indicates to use joint equalization, then the one or more RUs implement step 2010, receiving a request from the DU for one or more equalized DMRS symbols and one or more equalized data symbols. Step 2020 is equalizing one or more DMRS symbols and one or more data symbols to create one or more equalized DMRS symbols and one or more equalized data symbols. Step 2030 is sending the one or more equalized DMRS symbols and the one or more equalized data symbols to the DU for use by the DU for channel estimation and equalization. If the scheduling information does not indicate to use joint equalization, then the RUs implement step 2040, receiving a request from the DU for one or more equalized data symbols and one or more SINR data. Step 2050 is equalizing one or more DMRS symbols and one or more data symbols to create one or more equalized DMRS symbols and one or more equalized data symbols. Step 2060 is sending the one or more equalized data symbols and the one or more SINR data to the DU, where the one or more equalized data symbols and the one or more SINR data: are used for MRC CoMP and demodulation at step 2070 in the case that the scheduling information indicates MRC CoMP; and are used to implement modulation individually for each RU including the one or more RUs at step 2080 in the case that the scheduling information does not indicate MRC CoMP. Method 2000 can include multiple alternative embodiments with additional or alternative steps.

[0058] Figure 16An example of a communication system 2100 is shown in accordance with some embodiments. In this example, the communication system 2100 includes a telecommunication network 2102 that comprises an access network 2104, such as a RAN, and a core network 2106 that comprises one or more core network nodes 2108. The access network 2104 comprises one or more access network nodes, such as network nodes 2110a and 2110b (one or more of which can be referred to collectively as network nodes 2110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 2110 facilitate direct or indirect connection of UEs, for example by connecting UEs 2112a, 2112b, 2112c, and 2112d (one or more of which can be referred to collectively as UEs 2112) to the core network 2106, through one or more wireless connections.

[0059] Example wireless communications over the wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information over a wire, a cable, or other material conductor is not used. In addition, in different embodiments, the communication system 1100 can include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in communication (whether wired or wireless) of data and / or signals. The communication system 2100 can include any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system and / or interface therewith.

[0060] The UEs 2112 can be any of various communication devices, including wireless devices arranged, configured and / or operable to communicate wirelessly with the network nodes 2110 and other communication devices. Similarly, the network nodes 2110 are arranged, capable, configured and / or operable to communicate directly or indirectly with UEs 2112 and / or other network nodes or devices in the telecommunication network 2102 to enable and / or provide network access (such as wireless network access) and / or to implement other functions (such as management) in the telecommunication network 2102.

[0061] In the depicted example, core network 2106 connects network nodes 2110 to one or more hosts, such as host 2116. These connections can be direct or indirect, such as through one or more intermediate networks or devices. In other examples, network nodes can be directly coupled to hosts. Core network 2106 includes one or more core network nodes, such as core network node 2108, comprised of hardware and software components. The features of these components can be substantially similar to the features described for UEs, network nodes, and / or hosts, such that their description generally applies to corresponding components of core network node 2108. Example core network nodes include functionality of one or more of: a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier de-concealing function (SIDF), a unified data management (UDM), a security edge protection proxy (SEPP), a network exposure function (NEF), and / or a user plane function (UPF).

[0062] Host 2116 can be under the ownership or control of a service provider other than the operator or provider of access network 2104 and / or telecommunication network 2102, and can be operated by the service provider or on behalf of the service provider. Host 2116 can host various applications to provide one or more services. Examples of such applications include live and on-demand audio / video content, data collection services (e.g., retrieving and compiling data detected by various environmental conditions by a plurality of UEs), analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions implemented by servers.

[0063] Overall, Figure 16 The communication system 2100 enables connectivity between UEs, network nodes, and hosts. In this regard, the communication system can be configured to operate according to predefined rules or procedures, such as a particular standard, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunication System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standard, or any applicable future generation standard (e.g., 6G); Wireless Local Area Network (WLAN) standard, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other appropriate wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near-Field Communication (NFC), ZigBee, LiFi, and / or any Low Power Wide-Area Network (LPWAN) standard, such as LoRa and Sigfox.

[0064] In some examples, the telecommunication network 2102 is a cellular network that implements 3GPP standardized features. Thus, the telecommunication network 2102 can support network slicing to provide different logical networks to different devices connected to the telecommunication network 2102. For example, the telecommunication network 2102 can provide Ultra-Reliable and Low-Latency Communications (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communications (mMTC) / massive IoT services to other UEs.

[0065] In some examples, the UEs 2112 are configured to transmit and / or receive information without direct human interaction. For example, a UE can be designed to transmit information to the access network 2104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 2104. In addition, UEs can be configured for operation in single-RAT or multi-RAT or multi- standard modes. For example, UEs can operate using any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for Multi-Radio Dual Connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0066] In this example, hub 2114 is in communication with access network 2104 to facilitate indirect communication between one or more UEs (e.g., UEs 2112c and / or 2112d) and a network node (e.g., network node 2110b). In some examples, hub 2114 can be a controller, router, content source, and analytics, or any other communication device described herein with respect to a UE. For example, hub 2114 can be a broadband router that enables a UE to access core network 2106. As another example, hub 2114 can be a controller that sends commands or instructions to one or more actuators in a UE. The commands or instructions can be received from a UE, network node 2110, or by executable code, scripts, processes, or other instructions in hub 2114. As another example, hub 2114 can be a data collector that acts as temporary storage for UE data, and in some embodiments, can implement analysis or other processing of the data. As another example, hub 2114 can be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, hub 2114 can retrieve VR assets, video, audio, or other media or data related to sensing information via a network node, which hub 2114 then provides to the UE directly, after implementing local processing, and / or after adding additional local content. In yet another example, hub 2114 acts as a proxy server or orchestrator for UEs, particularly where one or more UEs are low-energy IoT devices.

[0067] Hub 2114 can have a constant / persistent or intermittent connection with network node 2110b. Hub 2114 can also allow for different communication schemes and / or schedules between hub 2114 and UEs (e.g., UEs 2112c and / or 2112d) and between hub 2114 and core network 2106. In other examples, hub 2114 is connected to core network 2106 and / or one or more UEs via a wired connection. Further, hub 2114 can be configured to connect to a M2M service provider through access network 1104 and / or to another UE through a direct connection. In some scenarios, a UE can establish a wireless connection with network node 2110 while still connecting via hub 2114 through a wired or wireless connection. In some embodiments, hub 2114 can be a dedicated hub, that is, a hub whose primary function is to route communications from and to UEs to and from network node 2110b. In other embodiments, hub 2114 can be a non-dedicated hub, that is, a device that is capable of operating to route communications between UEs and network node 2110b, but is also capable of operating as a communication origin and / or terminus for certain data channels.

[0068] Figure 17 A UE 2200 according to some embodiments is shown. As used herein, a UE refers to a device that is capable, configured, arranged and / or operable to communicate wirelessly with a network node and / or other UEs. Examples include, but are not limited to, smart phones, mobile phones, cellular phones, Voice Over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, laptop embedded equipment (LEE) s, laptop mounted equipment (LME) s, smart devices, wireless customer-premise equipment (CPE) s, in-vehicle or embedded / instrumental wireless equipment, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including Narrow- Band Internet of Things (NB-IoT) UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0069] A UE can support device-to-device (D2D) communication, e.g., through implementation of the 3GPP standard for sidelink communication, dedicated short range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X). In other examples, UEs can not necessarily have a user in the sense of a human user that owns and / or operates the relevant device. Instead, a UE can represent a device that is intended for sale to, or operation by, a human user but that can not, or that can not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE can represent a device that is not intended for sale to, or operation by, an end user but that can be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0070] The UE 2200 includes processing circuitry 2202 that is operatively coupled to input / output interface 2206, power source 2208, memory 2210, communication interface 2212, and / or any other component(s) or combination thereof, via bus 2204 or a similar communication coupling. Some of the components or all of the components can not be present in certain UEs. The Figure 10 The level of integration between the components can vary from one UE to another. Furthermore, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0071] The processing circuit 2202 is configured to process instructions and data, and can be configured as any sequential state machine operative to read stored instructions and data and perform the operations required by the instructions. The processing circuit 2202 can be implemented with one or more hardware implemented state machines (e.g., with discrete logic circuitry, with an

[0072] In this example, the input / output interface 2206 can be configured to provide one or more interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. Examples of input devices include a touch-sensitive display or a presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence- sensitive display can include a capacitive or resistive touch sensor to sense input from a user. Examples of sensors include accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, biometric sensors, etc., or any combination thereof. The output devices can use the same type of interface port as the input devices. For example, a universal serial bus (USB) port can be used to provide both input and output to the

[0073] In some embodiments, the power supply 2208 is configured as a battery or battery pack. Other types of power supplies, such as an external power supply (e.g., a power cord that is plugged into a wall outlet), a photovoltaic device, or a connection to an electrical grid can also be used. The power supply 2208 can also include a power supply circuit that is used to deliver power from the power supply 2208 and / or an external power source to the various components of the UE 2200 via an input circuit or interface (e.g., a power cable). The power can be delivered from the power supply 2208, for example, to charge the power supply 2208. The power supply circuit can perform any formatting, conversion, or other modification to the power from the power supply 2208 to make the power suitable for use by the respective components of the UE 2200 to which power is supplied.

[0074] Memory 2210 can be or include cache such as cache 2212, buffer such as buffer 2213, and / or a combination of cache and buffer. Memory 2210 can be or be configured to include a variety of memories, such as random access memory (RAM), read only memory (ROM), programmable read only memory (PROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), magnetic disks, optical disks, hard drives, floppy disks, flash memory, or a combination of these memories. In one example, memory 2210 includes one or more applications 2214 (such as an operating system, a web browser application, widgets, a widget engine, or other applications) and corresponding data 2216. Memory 2210 can store any of a variety of operating systems for use by the UE 2200.

[0075] Memory 2210 can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drives, external hard drives, thumb drives, pen drives, key drives, High-Density-Digital- Versatile-Disk (HDD-DVD) optical drives, internal hard drives, Blu-Ray optical drives, holographic optical drives, external mini-dual in-line memory modules (DIMMs), synchronous dynamic random access memory (SDRAM), external micro-DIMMs, smart card memory such as that typically found in a Universal Integrated Circuit Card (UICC) form factor, including one or more Subscriber Identity Modules (SIM), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may, for example, be an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC, commonly referred to as a "SIM card." Memory 2210 can allow the UE 2200 to access instructions, application programs, etc. stored on transitory or non-transitory storage media to off-load data or to upload data. An article of manufacture, such as one utilizing a communication system can be tangibly embodied in or by memory 2210, which can be a device readable storage medium or include a device readable storage medium.

[0076] The processing circuit 2202 can be configured to communicate with an access network or other networks using the communication interface 2212. The communication interface 2212 can include one or more communication subsystems and can include an antenna 2222 or be communicatively coupled to an antenna 2222. The communication interface 2212 can include one or more transceivers for communicating with other devices, for example, another UE or a network node in an access network, over one or more wireless communication links. Each transceiver can include a transmitter 2218 and / or a receiver 2220 adapted to provide network communications, for example, optical, electrical, frequency allocations, etc. Moreover, the transmitter 2218 and the receiver 2220 can be coupled to one or more antennas, for example, the antenna 2222, and can share circuit components, software, or firmware, or alternatively be implemented separately.

[0077] In the illustrated embodiment, the communication functionality of the communication interface 2212 can include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as determining a location using the global positioning system (GPS), another like communication functionality, or any combination thereof. The communication can be implemented according to one or more communication protocols and / or standards, for example, IEEE 802.11, code division multiple access (CDMA), wideband code division multiple access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / Internet protocol (TCP / IP), synchronous optical networking (SONET), asynchronous transfer mode (ATM), QUIC, hypertext transfer protocol (HTTP), etc.

[0078] Regardless of the type of sensor, the UE can provide output of data captured by its sensors via a wireless connection with a network node through its communication interface 2212. Data captured by the sensors of the UE can be transmitted via another UE over a wireless connection with a network node. The output can be periodic (e.g., every 15 minutes if it reports sensed temperature), random (e.g., to balance the load of reports from multiple sensors), responsive to a triggering event (e.g., sending an alert when moisture is detected), responsive to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0079] As another example, the UE includes an actuator, motor, or switch related to a communication interface configured to receive a wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight according to the received input, or adjusts a robotic arm performing a medical procedure according to the received input.

[0080] When in the form of an Internet of Things (IoT) device, the UE can be a device for one or more application areas including, but not limited to, urban wearable technology, extended industry applications, and healthcare. Non-limiting examples of such IoT devices are devices that are a or are embedded in a networked refrigerator or freezer, a TV, a networked lighting device, an electricity meter, a robotic vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / water level sensor, an electric door lock, a networked doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for augmented reality (AR) or virtual reality (VR), a wearable device for tactile or sensory augmentation, a sprinkler, an animal or item tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any kind of medical device such as a heart rate monitor or a teleoperated surgical robot. In addition to the other components described in relation to the UE 2200 shown in Figure 10 In addition to the other components described in relation to the UE 2200 shown in

[0081] As yet another particular example, in an IoT scenario, the UE can represent a machine or other device that implements monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another UE and / or a network node. In this case, the UE can be a M2M device, which can be referred to as an MTC device in a 3GPP context. As one particular example, the UE can implement the 3GPP NB-IoT standard. In other scenarios, the UE can represent a vehicle, such as an automobile, a bus, a truck, a ship, and an airplane, or other equipment that is capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[0082] In practice, any number of UEs can be used together for a single use case. For example, a first UE can be or be integrated in a drone, and provide speed information of the drone (obtained by a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes a change from the remote controller, the first UE can adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the speed of the drone. The first UE and / or the second UE can also include more than one of the above-mentioned functions. For example, a UE can include a sensor and an actuator, and handle communications for both the speed sensor and the actuator.

[0083] Figure 18 A network node 3300 according to some embodiments is shown. As used herein, a network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment in a telecommunications network. Examples of network nodes include but are not limited to: access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR Node Bs (gNBs)).

[0084] Base stations can be classified based on the amount of coverage they provide (or in other words, their transmission power level) and can thus be referred to as femto, pico, micro, or macro base stations depending on the provided coverage amount. A base station can be a relay node or a relay donor node controlling relays. Network nodes can also include one or more (or all) components of a distributed radio base station, such as a centralized core network unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit can or can not be integrated with an antenna as an antenna integrated radio. The components of a distributed radio base station can also be referred to as nodes in a distributed antenna system (DAS).

[0085] Other examples of network nodes include: multi -transmit and multi -receive point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), operations and maintenance (O&M) nodes, operations support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Center (E-SMLC)), and / or minimizing drive testing (MDT).

[0086] The network node 3300 includes processing circuitry 3302, memory 3304, communication interface 3306, and power source 3308. The network node 3300 can include a plurality of physically separate components (e.g., Node B components and RNC components, or BTS components and BSC components, etc.), each of which can have its own respective components. In certain scenarios in which the network node 3300 includes a plurality of separate components (e.g., BTS and BSC components), one or more of the separate components can be shared among a plurality of network nodes. For example, a single RNC can control multiple Node Bs. In such scenarios, in certain instances, each unique pair of Node B and RNC can be considered a single separate network node. In some embodiments, the network node 3300 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g., separate memory 3304 for

[0087] The processing circuitry 3302 can include 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 connection with other network node 3300 components, such as the memory 3304, network node 3300 functionality.

[0088] In some embodiments, the processing circuitry 3302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 3302 includes one or more of radio frequency (RF) transceiver circuitry 3312 and baseband processing circuitry 3314. In some embodiments, the radio frequency (RF) transceiver circuitry 3312 and the baseband processing circuitry 3314 can 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 the RF transceiver circuitry 3312 and baseband processing circuitry 3314 can be on the same chip or set of chips, boards, or units.

[0089] Memory 3304 can include any form of volatile or nonvolatile 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 for use by processing circuitry 3302. Memory 3304 can store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, codes, tables, etc. and / or other instructions capable of being executed by processing circuitry 3302 and utilized by network node 3300. Memory 3304 can be used to store any calculations made by processing circuitry 3302 and / or any data received

[0090] Communication interface 3306 is used in the wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As illustrated, communication interface 3306 includes a port / terminal 3316 to send and receive data, for example, to and from a network over a wired connection. Communication interface 3306 also includes radio-front end circuitry 3318 that can be coupled to, or be part of, antenna 3310. Radio-front end circuitry 3318 comprises filters 3320 and amplifiers 3322. Radio-front end circuitry 3318 can be connected to antenna 3310 and processing circuitry 3302. Radio-front end circuitry 3318 can be configured to condition signals communicated between antenna 3310 and processing circuitry 3302. Radio- front end circuitry 3318 can receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. Radio-front end circuitry 3318 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 3320 and / or amplifiers 3322. The radio signal can then be transmitted via antenna 3310. Similarly, when receiving data, antenna 3310 can collect radio signals, which are then converted into digital data by radio-front end circuitry 3318. The digital data can be passed to processing circuitry 3302. In other embodiments, communication interface can include different components and / or different combinations of components.

[0091] In certain alternative embodiments, network node 3300 does not include separate radio front-end circuitry 3318, but rather the processing circuitry 3302 includes radio front-end circuitry and is connected to antenna 3310. Similarly, in some embodiments, all or portions of RF transceiver circuitry 3312 are part of communications interface 3306. In other embodiments, communications interface 3306 includes one or more ports or terminals 3316, radio front-end circuitry 3318, and RF transceiver circuitry 3312 as part of a radio

[0092] Antenna 3310 can include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 3310 can be coupled to radio front-end circuitry 3318 and can be any type of antenna and / or antenna array capable of

[0093] Antenna 3310, communications interface 3306, and / or processing circuitry 3302 can be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by a network node. Any information, data and / or signals can be received from a UE, another network node and / or any other network equipment. Similarly, antenna 3310, communications interface 3306, and / or processing circuitry 3302 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and / or signals can be transmitted to a UE, another network node and / or any other network equipment.

[0094] Power source 3308 provides power to various components of network node 3300 in a form suitable for use by each respective component (e.g., at a voltage and current level needed for each respective component). Power source 3308 can also include, or be coupled to, power management circuits to provide power for implementing the functions described herein to the components of network node 3300. For example, network node 3300 can be connected to an external power source (e.g., an electricity grid, an electrical outlet) via an input circuit or interface (e.g., an electrical cable) that provides power to power supply circuitry of the power source 3308 for powering the components of network node 3300. As another example, power source 3308 can comprise a rechargeable battery or battery pack or a renewable energy source (e.g., solar, photovoltaic) that is recharged

[0095] Embodiments of network node 3300 can include Figure 18Additional components can be included in the network node 3300 as part of the components illustrated in FIG. 33, or as standalone components, that provide certain aspects of the functionality of the network node, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For instance, the network node 3300 can include user interface equipment to allow input of information into the network node 3300 and to allow output of information from the network node 3300. This can allow a user to implement diagnostics, maintenance, repairs and other management functions for the network node 3300.

[0096] Figure 19 is a block diagram of a host 4400 in accordance with various aspects described herein, which can be an embodiment of the host 2116. As used herein, the host 4400 can be or include various combinations of hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a processing resource in a server farm. The host 4400 can provide one or more services to one or more UEs. Figure 16

[0097] The host 4400 includes processing circuitry 4402 operably coupled to input / output interface 4406, network interface 4408, power source 4410, and memory 4412 via bus 4404. Other components can be included in other embodiments. Features of these components can be substantially similar to those described for the devices of the previous figures (e.g., the host 2116), such that their description generally applies to the corresponding components of the host 4400. Figure 17 and Figure 18

[0098] ​​Memory 4412 can include one or more computer programs, including one or more host applications 4414 and data 4416, which can include user data, such as data generated by a UE for the host 4400 or data generated by the host 4400 for a UE. Embodiments of the host 4400 can utilize all or only a subset of the components shown. The host applications 4414 can be implemented in a container-based architecture and can provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., cellphones, desktop computers, wearable display systems, heads-up display systems). The host applications 4414 can also provide user authentication and permission checks, and can periodically report health, routing, and content availability to a central node (e.g., a device in the core network or on the edge). Thus, the host 4400 can select and / or indicate different hosts for over-the-top services for UEs. The host applications 4414 can support various protocols, such as the HTTP Live Streaming (HLS) protocol, the Real-Time Messaging Protocol (RTMP), the Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), and the like.

[0099] Figure 20 FIG. 55 is a block diagram illustrating a virtualization environment 5500 in which functions implemented by some embodiments can be virtualized. In current context, virtualization means the creation of virtual versions of apparatuses or devices that can include virtualization of hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device or component thereof described herein and involves a process in which at least a portion of the functionality is implemented as a virtual component. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 5500 hosted by one or more hardware nodes (e.g., hardware computing devices operating as network nodes, UEs, core network nodes, or hosts). Further, in embodiments in which a virtual node does not require radio connectivity (e.g., core network nodes or hosts), the nodes can be entirely virtualized.

[0100] An application 5502, which can optionally be referred to as a software instance, virtual apparatus, network function, virtual node, virtual network function, etc., runs in the virtualization environment 5500 to implement certain features, functions, and / or benefits of some of the embodiments disclosed herein.

[0101] Hardware 5504 comprises processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, e.g., network interfaces, input / output interfaces, etc. The software can be executable by the processing circuitry to instantiate one or more virtualization layers 5506 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide VMs 5508a and 5508b (one or more of which can be referred to collectively as VMs 5508), and / or implement any of the functions, features and / or benefits described with respect to some embodiments described herein. The virtualization layer 5506 can present a virtual operating platform that appears like networking hardware to the VMs 5508.

[0102] VMs 5508 comprise virtual processing, virtual memory, virtual networks or interfaces and virtual storage, and can be run by a corresponding virtualization layer 5506. Different embodiments of the instance of virtual appliance 5502 can be implemented on one or more of VMs 5508, and can be implemented in different manners. In some contexts, the virtualization of the hardware is referred to as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches and physical storage, which can be located in data centers, and customer premise equipment.

[0103] In the context of NFV, VMs 5508 can be software implementations of physical machines that run programs as if the programs were executing on a physical, non-virtualized machine. Each VM 5508, along with the components of the hardware 5504 that execute that VM (hardware dedicated to that VM and / or hardware shared by that VM with others) form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that are run in one or more VMs 5508 on top of hardware 5504, and corresponds to an application 5502.

[0104] Hardware 5504 can be implemented in a standalone network node with general- purpose or specialized components. Hardware 5504 can implement some functions via virtualization. Alternatively, hardware 5504 can be part of a larger cluster of hardware, such as in a data center or CPE, where many hardware nodes work together and are managed via management and orchestration 5510, which oversees, among other things, lifecycle management of applications 5502. In some embodiments, hardware 5504 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that can be coupled to one or more antennas. Radio units can communicate directly with other hardware nodes via one or more appropriate networks, and can be used in combination with virtual components to provide a virtual node such as a radio access node or base station. In some embodiments, some signaling can be provided using control system 5512, which can optionally be used for communication between hardware nodes and radio units.

[0105] Figure 21 A communication diagram illustrating host 6602 in communication with UE 6606 via network node 6604 over a partial wireless connection is shown in accordance with some embodiments. Example implementations of a UE (such as UE 2112a and / or UE 2200 of Figure 21 the previous paragraphs in accordance with various embodiments will now be described with reference to Figure 16 Figure 21, Figure 22, and Figure 44, respectively. Figure 17 Figure 21, Figure 22, and Figure 44, respectively. Figure 16 Figure 21, Figure 22, and Figure 44, respectively. Figure 18 Figure 21, Figure 22, and Figure 44, respectively. Figure 16 Figure 21, Figure 22, and Figure 44, respectively. Figure 19 Figure 21, Figure 22, and Figure 44, respectively.

[0106] Similar to host 4400, embodiments of host 6602 include hardware, such as a communication interface, processing circuitry, and memory. Host 6602 also includes software, which is stored in or accessible by the host 6602 and executable by the processing circuitry. The software includes a host application, which can be operable to provide a service to a remote user (such as UE 6606 connecting via an over-the-top (OTT) connection 6650 extending between UE 6606 and host 6602). In providing the service to the remote user, the host application can provide user data, which is transmitted using OTT connection 6650.

[0107] Network node 6604 includes hardware that enables it to communicate with host 6602 and UE 6606. Connection 6660 can be direct or via a core network (like core network 3100 of Figure 16The core network 2106) and / or one or more other intermediate networks, e.g., one or more public, private, or hosted networks. For example, the intermediate network can be a backbone network or the Internet.

[0108] The UE 6606 includes hardware and software. The software is stored in or accessible by the UE 6606 and executable by the UE's processing circuitry. The software includes a client application, e.g., a web browser or a client-specific application exposed to a human or non-human user via the UE 6606. In the host computer 6602, a host application is executed that can communicate with the client application via the OTT connection 6650 terminating at the UE 6606 and the host computer 6602. In providing services to the user, the UE's client application can receive request data from the host computer's host application and provide user data in response to the request data. The OTT connection 6650 can carry both the request data and the user data. The UE's client application can interact with the user to generate user data that it provides to the host computer application.

[0109] The OTT connection 6650 can extend via an internet protocol connection 6660 between the host computer 6602 and a network node 6604 of a telecommunication network, and via an air interface connection 6670 between the network node 6604 and the UE 6606 operated by the wireless device. The internet protocol connection 6660 can be implemented via the public Internet, a private

[0110] As an example of transmitting data via OTT connection 6650, in step 6608, host computer 6602 provides user data, which can be implemented by executing a host application. In some embodiments, the user data is associated with a particular human user who interacts with UE 6606. In other embodiments, the user data is associated with UE 6606, e.g., without human interaction with host computer 6602. In step 6610, host computer 6602 initiates a transmission carrying the user data towards UE 6606. Host computer 6602 can initiate the transmission in response to a request sent by UE 6606. The request can be caused by a human user interacting with UE 6606, or by the operation of a client application executed on UE 6606. According to the teachings of the embodiments described throughout this disclosure, the transmission can pass through network node 6604. In step 6612, network node 6604 then transmits the user data carried in the transmission originating from host computer 6602 towards UE 6606, according to the teachings of the embodiments described throughout this disclosure. In step 6614, UE 6606 receives the user data carried in the transmission, which can be implemented by a client application executed on UE 6606 associated with the host application executed by host computer 6602.

[0111] In some examples, UE 6606 executes a client application that provides user data to host computer 6602. The user data can be provided in response to receiving data from host computer 6602 or as a response to it. Thus, in step 6616, UE 6606 can provide user data, which can be implemented by executing a client application. In providing the user data, the client application can further consider user input received from a user via an input / output interface of UE 6606. Regardless of the specific manner in which the user data is provided, in step 6618, UE 6606 initiates a transmission of the user data towards host computer 6602 via network node 6604. In step 6620, network node 6604 receives the user data from UE 6606 and initiates a transmission of the received user data towards host computer 6602, according to the teachings of the embodiments described throughout this disclosure. In step 6622, host computer 6602 receives the user data carried in the transmission initiated by UE 6606.

[0112] One or more of the various embodiments improve the performance of OTT services provided to UE 6606 using OTT connection 6650, in which wireless connection 6670 forms the last segment. More specifically, the teachings of these embodiments can improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restrictions on file size, improved content resolution, better responsiveness, and / or extended battery lifetime.

[0113] In an example scenario, host 6602 can collect and analyze factory status information. As another example, host 6602 can process audio and video data that can have been retrieved from UEs for creating a map. As another example, host 6602 can collect and analyze real-time data to assist in controlling vehicular congestion (e.g., controlling traffic lights). As another example, host 6602 can store surveillance videos uploaded by UEs. As another example, host 6602 can store or control access to media content such as videos, audio, VR, or AR that host 6602 can broadcast, multicast, or unicast to UEs. As yet other examples, host 6602 can be used for energy pricing, remote control of non-time critical electric loads to balance power generation needs, positioning services, presence services (e.g., to edit a presentation based on data collected from remote devices, etc.), or any other functionality that collects, retrieves, stores, analyzes, and / or transmits data.

[0114] In some embodiments, a measurement procedure can be provided for the purpose of monitoring the data rate, the delay, and other factors on which the one or more embodiments improve. There can further be an optional network functionality for reconfiguring the OTT connection 6650 between the host 6602 and the UE 6606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection can be implemented in software and hardware of the host 6602 and / or the UE 6606. In some embodiments, sensors (not shown) can be deployed in or in association with other devices through which the OTT connection 6650 passes; the sensors can participate in the measurement procedure by providing values of the monitored quantities exemplified above, or providing values of other physical quantities from which software can compute or estimate the monitored quantities. The reconfiguring of the OTT connection 6650 can include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not

[0115] Although the computing devices described herein (e.g., UEs, network nodes, hosts) can include the illustrated combinations of hardware components, other embodiments can comprise computing devices with different combinations of components. It is contemplated that these computing devices can include any suitable combination of hardware and / or software necessary to implement the tasks, features, functions, and methods disclosed herein. Determinations, calculations, or similar operations described herein can be implemented by processing circuitry, which can process information, including by transforming the obtained information, comparing the obtained information or transformed information to information stored in the network node, and / or implementing one or more operations based on the obtained information or transformed information, and as a result of the processing, making a determination. Moreover, although components are depicted as single boxes or single boxes nested within multiple boxes inside of larger boxes, in practice, computing devices can include multiple distinct physical components constituting a single illustrated component, and the functionality can be divided between separate components. For example, a communication interface can be configured to include any of the components described herein, and / or the functionality of components can be divided between processing circuitry and a communication interface. In another example, non-computationally intensive functionality of any of such components can be implemented in software or firmware, while computation-intensive functionality can be implemented in hardware.

[0116] In certain embodiments, some or all of the functionality described herein can be provided by a processing circuitry executing instructions stored in a memory, which in certain embodiments can be a computer program product in the form of a non-transitory computer readable storage medium. In alternative embodiments, some or all of the functionality can be provided by a processing circuitry without executing instructions stored by a separate or discrete device readable storage medium, for example, in a hard-wired manner. In either of these particular embodiments, whether executing instructions stored on a non-transitory computer readable storage medium or not, the processing circuitry can be configured to implement the described functionality. The benefits provided by such functionality are not limited to the processing circuitry or other components of the computing device alone or in isolation, but are enjoyed by the computing device as a whole and / or by end users and wireless networks generally.

[0117] It will be appreciated that computer systems are increasingly taking a wide variety of forms. In this description and in the claims, the term "controller," "computer system," or "computing system" is intended to include any device or system, or combination thereof, that includes at least one physical and tangible processor, and that has physical and tangible memory capable of having stored therein computer-executable instructions that can be executed by the processor. As used in this description and in the claims, the term "computer system" or "computing system" is intended to encompass a personal computer, desktop computer, laptop, tablet, handheld device (e.g., mobile telephone, PDA, pager), microprocessor-based or programmable consumer electronic, minicomputer, mainframe computer, multiprocessor system, network PC, distributed computing system, data center, message processor, router, switch, and even devices that are not generally considered to be computing systems, such as a wearable device (e.g., glasses).

[0118] There are also multiple structures on the computing system that are commonly referred to as "executable components." For example, the memory of the computing system can include executable components. The term "executable component" is the name of a structure that those of ordinary skill in the computing arts will fully appreciate can be software, hardware, or a combination thereof. For example, when implemented in software, those of ordinary skill in the art will appreciate that the structure of an executable component can comprise software objects, routines, methods, or the like that can be executed on one or more processors on the computing system, whether such executable components exist in the heap of the computing system, or whether the executable components exist on computer-readable storage media. The structure of the executable component exists on computer-readable media in such a manner that the computing system, when executing the structure of the executable component, is operable to perform one or more functions, such as those functions and methods described herein. Such structure can be computer readable directly from the computer-readable media, as in the case of an executable component that is binary, or alternatively, the structure can be constructed, either explicitly or implicitly, as an interpretable and / or compilable (whether in a single stage or multiple stages) to become such binary directly executable by the processor.

[0119] The terms "component," "service," "engine," "module," "control," "generator," and so on can also be used in the present description. As used in this description and in this case, these terms (whether expressed with or without the adjective modifier) are also intended to be synonymous with the term "executable component," and thus also have the structure that those of ordinary skill in the computing arts will fully appreciate.

[0120] For purposes of computer implementation, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms "computer", "processor" and "controller" can be used interchangeably. Where functions are provided by a computer, processor or controller, this can be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which can be shared or distributed. Moreover, the term "processor" or "controller" also refers to other hardware capable of implementing such functions and / or executing software, such as the example hardware described above.

[0121] Generally, the various exemplary embodiments can be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software which can be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various aspects of exemplary embodiments of this disclosure can be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein can be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controler or other computing devices, or some combination thereof.

[0122] While not all computing systems require a user interface, in some embodiments, the computing system includes a user interface for communicating information to / from a user. The user interface can include output mechanisms as well as input mechanisms. The principles described herein are not limited to precise output mechanisms or input mechanisms as these will depend on the nature of the device. However, output mechanisms can include, for example, speakers, displays, tactile outputs, projectors, holograms, etc. Examples of input mechanisms can include, for example, microphones, touchscreens, projectors, holograms, cameras, keyboards, styluses, mouse or other pointer input, any type of sensor, etc.

[0123] Abbreviations and defined terms

[0124] To aid understanding of the scope and content of the written description and the appended claims of this book, some selected terms are directly defined below. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0125] As used herein, the terms “about,” “approximately,” and “substantially” mean quantities or conditions close to the stated amount or condition that still perform a desired function or achieve a desired result. For example, the terms “about,” “approximately,” and “substantially” can refer to an amount or condition that is within less than 10%, or within less than 5%, or within less than 1%, or within less than 0.1%, or within less than 0.01% of a particular recited amount or condition.

[0126] Various aspects of the disclosure can be described in reference to one or more embodiments or implementations, including devices, systems, and methods, which are exemplary in nature. As used herein, the term “exemplary” means “serving as an example, instance, or illustration,” and should not necessarily be construed as preferred or advantageous over other embodiments disclosed herein. Additionally, reference to “an implementation” of the disclosure or embodiments includes a particular implementation of one or more embodiments of the disclosure, and vice versa, and is intended to provide illustrative examples of the disclosure without limiting the scope of the disclosure, which is governed by the appended claims, not the specification.

[0127] As used in the specification, a word appearing in the singular encompasses its plural counterpart, and a word appearing in the plural encompasses its singular counterpart, unless implicitly or explicitly understood or stated otherwise. Thus, it is to be understood that, as used in the specification and the appended claims, the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. For example, reference to “a” or “an” item includes a plurality of such items unless the context clearly dictates otherwise. Similarly, reference to a “plurality” of items includes a single item or one item, unless the context clearly dictates otherwise. For example, reference to “a” or “an” item does not necessarily preclude a plurality of such items, and vice versa.

[0128] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described can include a particular feature, structure, or characteristic, but every embodiment can not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of those skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described or claimed. As used herein, “and / or” means and.

[0129] It should be understood that, although the terms“first” and“second” etc. can be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element without departing from the scope of the example embodiments. As used herein, the term“and / or” includes any and all combinations of one or more of the associated listed items.

[0130] It should also be understood that the terms“comprise”,“comprising”,“have”,“hasing”,“including” and / or“containing” when used herein, specify the presence of stated features, elements and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0131] CONCLUSION

[0132] The present disclosure includes any novel feature or combination of features disclosed herein explicitly or any generalization thereof. Various modifications and adaptations to the foregoing exemplary embodiments of this disclosure can become apparent to those skilled in the relevant art in view of the foregoing description, when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of this disclosure.

[0133] It should be understood that, for any given component or embodiment described herein, any possible candidate or alternative listed for that component can generally be used individually or in combination with each other unless implicitly or explicitly understood or stated otherwise. Additionally, it should be understood that any listing of such candidates or alternatives is merely illustrative and not limiting unless implicitly or explicitly understood or stated otherwise.

[0134] Further, unless otherwise indicated herein, numbers expressing quantities of ingredients, properties such as percentage, distances, and other quantitative data, as used in the specification and claims, are to be understood as being modified in all instances by the term“about”. Accordingly, unless indicated to the contrary, the numerical parameters set forth in the specification and attached claims are approximations. Thus, unless otherwise indicated, the numerical parameters set forth in the specification and attached claims are approximations. At the very least, each numerical parameter should at least be construed in light of the number of reported significant digits and by applying ordinary rounding techniques. Notwithstanding the numerical ranges and parameters set forth herein, as varied and described in the subject matter presented in this disclosure, the numerical values set forth in specific examples are reported as precisely as possible. However, any numerical value, inherently contain certain errors necessarily resulting from the standard deviation found in their respective testing measurements.

[0135] Any headings and sub-headings are used for organizational purposes only and do not otherwise limit the scope of the application or the claims. The terms and expressions used herein are used as terms of description and not of limitation, and there is no intention, in the use of such terms and expressions, of excluding any equivalents of the features shown and described or portions thereof. It is recognized that various modifications are possible within the scope of the present disclosure, which scope is to be accorded the full breadth of the following claims.

[0136] It will also be appreciated that systems, devices, products, kits, methods, and / or processes according to particular embodiments of the present disclosure can include, incorporate, or otherwise comprise attributes or features (e.g., components, members, elements, parts, and / or portions) described in other embodiments disclosed and / or described herein. Thus, various features of particular embodiments can be compatible with, combined with, included in, and / or incorporated into other embodiments of the present disclosure. Accordingly, the disclosure of particular features in relation to a particular embodiment of the present disclosure should not be interpreted as limiting application or inclusion of the features to the particular embodiment. Rather, it should be understood that other embodiments can also include the features, members, elements, parts, and / or portions, without necessarily departing from the scope of the present disclosure.

[0137] Furthermore, any of the features herein can be combined with any other feature or features disclosed herein, unless the combination of features is not technically possible. Moreover, various known aspects of illustrative systems, methods, devices, etc. have not been described in detail so as not to obscure aspects of the example embodiments. However, it is also contemplated that these aspects are within the scope of the disclosure.

[0138] It will be apparent to one of ordinary skill in the art that methods, devices, device elements, materials, processes and techniques other than those specifically described herein can be employed in the practice of the embodiments so broadly disclosed without resort to undue experimentation. All art-known functional equivalents of the methods, devices, device elements, materials, processes and techniques described herein are intended to be encompassed by the present disclosure.

[0139] When a group of materials, compositions, components, or compounds is disclosed herein, it is understood that all individual members of the group and all subgroups and permutations of the members of the group are disclosed herein as if each were individually listed. When Markush groups or other groupings are used herein, all individual members of the group and all permutations of the members of the group are intended to be individually included in the disclosure.

[0140] The above embodiments are merely examples. Changes, modifications and variations of the specific embodiments can be made by those skilled in the art without departing from the scope of the specification, which is defined solely by the appended claims.

Claims

1. A method for implementing load balancing by a distributed unit DU (1015), the method comprising: Request (1510) one or more equalized demodulation reference signal (DMRS) symbols and one or more equalized data symbols from one or more radio units (1020, 1025); Receive (1520) the one or more equalized DMRS symbols and the one or more equalized data symbols; (1530) One or more channel estimations are performed, at least in part, based on the one or more equalized DMRS symbols; Equalization of the one or more equalized data symbols is performed (1540) at least in part based on the one or more channel estimates; Calculate (1550) one or more signal-to-interference-plus-noise ratio (SINR) data; as well as At least in part based on the one or more SINR data, demodulation and decoding of the one or more equalized data symbols are performed (1560).

2. A method for implementing joint equalization based on demodulation reference signal DMRS, implemented by a distributed unit DU (1015), the method comprising: Receive scheduling information (1710) from the scheduler; If the scheduling information indicates the use of DMRS-based joint load balancing, then the following steps are performed: Request (1720) one or more equalized DMRS symbols and one or more equalized data symbols from one or more radio units; Receive (1730) the one or more equalized DMRS symbols and the one or more equalized data symbols; (1740) One or more channel estimations are performed, at least in part, based on the one or more equalized DMRS symbols; Equalization of the one or more equalized data symbols is performed (1750) at least in part based on the one or more channel estimates; Calculate (1760) the first or more signal-to-interference-plus-noise ratio (SINR) data; as well as At least in part based on the first one or more SINR data, demodulation and decoding of the one or more equalized data symbols are performed (1770); as well as If the scheduling information does not indicate the use of DMRS-based joint load balancing, then the following steps are performed: Request (1780) the one or more equalized data symbols and the second or more SINR data from the one or more radio units; Receive (1785) the one or more equalized data symbols and the second or more SINR data; as well as If the scheduling information indicates a maximum ratio merge MRC Co-MP, then implement (1790) MRC CoMP and demodulation; and If the scheduling information does not indicate MRC CoMP, demodulation (1795) is performed individually for each of the one or more radio units.

3. The method according to claim 2, further comprising: Detect whether the scheduling information indicates the use of DMRS-based joint load balancing.

4. A method for implementing joint equalization based on demodulation reference signal (DMRS) by a distributed unit (DU), the method comprising: Request (1810) one or more equalized DMRS symbols and one or more equalized data symbols from one or more radio units; as well as Receive (1820) the one or more equalized DMRS symbols and the one or more equalized data symbols.

5. The method according to claim 4, further comprising: One or more channel estimates are performed, at least in part, based on the one or more equalized DMRS symbols; Equalization of the one or more equalized data symbols is performed, at least in part, based on the one or more channel estimates; Calculate one or more signal-to-interference-plus-noise ratio (SINR) data; as well as Demodulation and decoding of the one or more equalized data symbols are performed, at least in part, based on the one or more SINR data.

6. A method for joint equalization based on demodulation reference signal (DMRS) in a distributed unit (DU) implemented by a radio unit (RU), the method comprising: Receive (1910) requests from the distributed unit for one or more balanced DMRS symbols and one or more balanced data symbols; Equalize (1920) one or more DMRS symbols and one or more data symbols to create said one or more equalized DMRS symbols and said one or more equalized data symbols; as well as Send (1930) the one or more equalized DMRS symbols and the one or more equalized data symbols to the DU for the DU to use for channel estimation and equalization.

7. A method for joint equalization based on demodulation reference signal (DMRS) in a distributed unit (DU), implemented by one or more radio units (RUs), wherein, The DU has received scheduling information from the scheduler, and the method includes: If the scheduling information indicates the use of DMRS-based joint load balancing, then the following steps are performed: Receive (2010) a request from the DU for one or more equalized DMRS symbols and one or more equalized data symbols; Equalize (2020) one or more DMRS symbols and one or more data symbols to create said one or more equalized DMRS symbols and said one or more equalized data symbols; and Send (2030) the one or more equalized DMRS symbols and the one or more equalized data symbols to the DU for use by the DU in channel estimation and equalization; and If the scheduling information does not indicate the use of DMRS-based joint load balancing, then the following steps are performed: Receive (2040) a request from the DU for the one or more equalized data symbols and one or more signal-to-interference-plus-noise ratio (SINR) data; Equalize (2050) one or more DMRS symbols and one or more data symbols to create said one or more equalized DMRS symbols and said one or more equalized data symbols; and Send (2060) the one or more equalized data symbols and one or more SINR data to the DU, wherein the one or more equalized data symbols and one or more SINR data are: In the case where the scheduling information indicates maximum ratio merging coordinated multi-point MRC CoMP, it is used for MRC CoMP and demodulation (2070); and In the absence of MRC CoMP indicated in the scheduling information, demodulation is performed individually for each RU including the one or more RUs (2080).

8. A network node (3300) for implementing or assisting joint equalization and / or joint equalization based on demodulation reference signal DMRS, said network node comprising: Processing circuit (3302), configured to implement any one of the steps according to any one of claims 1 to 7; A power supply circuit (3308) is configured to supply power to the processing circuit.

9. The network node according to claim 8, wherein, The network node includes at least one of the following: a distributed unit (1015); a radio unit (1020, 1025).

Images