Network node and methods for frequency division duplex radio synchronization

Abstract

A method performed by a network node for handling Frequency Division Duplexing (FDD) radio in a wireless communications network is provided The network node receives (501) at least one dual-band calibration signal comprising signaling in at least one Uplink (UL) band and at least one Downlink (DL) band. The signaling in the at least one UL band is received by at least one UL receive path. The signaling in the at least one DL band is received by at least one DL receive path. The network node determines (502) a difference between the at least one UL receive path and the at least one DL receive path. The difference being in phase and / or delay between receiving the signaling in the at least one UL receive path and receiving the signaling the at least one DL receive path. The network node handles (503) FDD radio based on the determined difference between the at least one UL receive path and the at least one DL receive path.

Description

[0001] NETWORK NODE AND METHODS FOR FREQUENCY DIVISION DUPLEX RADIO SYNCHRONIZATION

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a network node and methods therein. In some aspects, they relate to handling Frequency Division Duplexing (FDD) radio in a wireless communications network.

[0004] BACKGROUND

[0005] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or UEs, communicate via a Local Area Network such as a Wi-Fi network or a Radio Access Network (RAN) to one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a NodeB, eNodeB (eNB), or gNB as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on radio frequencies with the wireless device within range of the radio network node.

[0006] Specifications for the Evolved Packet System (EPS), also called a Fourth Generation (4G) network, have been completed within the 3rd Generation Partnership Project (3GPP) and this work continues in the coming 3GPP releases, for example to specify a 5G network also referred to as 5G New Radio (NR). The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a variant of a 3GPP radio access network wherein the radio network nodes are directly connected to the EPC core network rather than to RNCs used in 3G networks. In general, in E- UTRAN / LTE the functions of a 3G RNC are distributed between the radio network nodes, e.g. eNodeBs in LTE, and the core network. As such, the RAN of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks, i.e. they are not connected to RNCs. To compensate for that, the E- UTRAN specification defines a direct interface between the radio network nodes, this interface being denoted the X2 interface.

[0007] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. The performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. Such systems and / or related techniques are commonly referred to as MIMO.

[0008] In current 5G and upcoming 6G RAN, Distributed MIMO (D-MIMO) technology is used for enhanced cell coverage, to increase throughput, and to improve spectrum usage, among other use cases. In D-MIMO, a UE receives signal(s) from multiple transmission and reception points (TRPs) in Uplink (UL) and Downlink (DL), typically with Coherent Join Transmission (C-JT) in DL. Multiple TRPs may receive signal(s) from a UE with Coherent Combining in UL (UL Comp).

[0009] Both C-JT and UL Comp require accurate time synchronizations between TRPs or gNBs, for example, a time alignment requirement is 130ns for coherent UL Comp. The requirement is difficult to adhere to by only using synchronization solutions using backhaul connections. This is since there are usually switches or other variable factors in the backhaul path between TRPs and a synchronization source, e.g., Global Navigation Satellite System (GNSS) receiver, which may cause a significant Time Alignment Error (TAE).

[0010] It's worthy to be noted that there are other features like positioning, radar sensing etc. which also need accurate time synchronizations.

[0011] SUMMARY

[0012] Problems with FDD radio as identified as part of developing embodiments herein are that synchronization, in particular Over The Air (OTA) synchronization methods, are not possible to utilize when using FDD radio.

[0013] OTA synchronization solutions such as by using Radio Interface Based Signal (RIBS) have been proven useful for Time Division Duplex (TDD) radio networks to achieve a better performance of time alignment between TRPs or gNBs. In TDD, DL and UL use the same frequency. This means that signals such as RIBS can be transmitted and received by gNBs using any suitable well-known method as depicted in Fig. 1.

[0014] However there is a problem to enable synchronization between bands for FDD radio. As shown in Fig. 2, carrier frequencies for DL, e.g., Transmission (TX) and UL, e.g., Reception (RX) are different in FDD, so signaling from a DL band is not able to be received as part of a UL receive path. In other words, currently, it is not possible to transmit and receive the synchronization signals between FDD radios or gNBs. Instead, synchronization needs to be performed over the same bands, in the same way as performed in TDD radio, which limits how network nodes are able to synchronize with other radio units, in particular using OTA synchronization. In particular, synchronizations between UE and gNBs on UL band are not able to be based on OTA synchronization between gNBs.

[0015] To overcome at least some of these problems and / or associated problems, example embodiments herein provide an efficient solution to use at least one calibration signal on both UL and DL bands to find a difference of UL and DL paths. This allows to provide any suitable alignments between communication in UL and DL bands. Also, some embodiments herein may relate to a solution enabling the transmitting and receiving of the synchronization signals over FDD radios, e.g., between gNBs and / or other radio units.

[0016] An object of embodiments herein is to provide a more efficient synchronization for FDD radio.

[0017] According to a first aspect, a method performed by a network node for handling FDD radio in a wireless communications network is provided. The network node receives at least one dual-band calibration signal comprising signaling in at least one UL band and at least one DL band. The signaling in the at least one UL band is received by at least one UL receive path. The signaling in the at least one DL band is received by at least one DL receive path. The network node determines a difference between the at least one UL receive path and the at least one DL receive path based on the received signaling of the at least one dual-band calibration signal. The determined difference is in phase and / or delay between receiving the signaling in the at least one UL receive path and receiving the signaling the at least one DL receive path. The network node handles FDD radio based on the determined difference between the at least one UL receive path and the at least one DL receive path.

[0018] According to a second aspect, a network node performed by a network node for handling FDD radio in a wireless communications network is provided. The network node is configured to receive at least one dual-band calibration signal comprising signaling in at least one UL band and at least one DL band. The signaling in the at least one UL band is received by at least one UL receive path. The signaling in the at least one DL band is received by at least one DL receive path. The network node is configured to determine a difference between the at least one UL receive path and the at least one DL receive path based on the received signaling of the at least one dual-band calibration signal. The difference is in phase and / or delay between receiving the signaling in the at least one UL receive path and receiving the signaling the at least one DL receive path. The network node is configured to handle FDD radio based on the determined difference between the at least one UL receive path and the at least one DL receive path.

[0019] According to further aspects, a computer program and a carrier comprising the computer program are provided as part of embodiments herein.

[0020] Since the at least one dual-band calibration signal comprising signaling in UL and DL band is received by the at least one UL receive path and the at least one DL receive path it is possible to determine the difference in phase and / or delay of the signaling in the respective receive path. When the difference is determined, it is enabled for the network node to handle FDD radio based on the determined difference such as by performing calibrated and synchronized between UL and DL bands in FDD radio. Typically, network nodes may already be synchronized over DL bands and since the difference in phase and / or delay between the respective paths is known by the aspects discussed above, communication over DL and UL bands may also be synchronized in an accurate and efficient manner.

[0021] BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Examples of embodiments herein are described in more detail with reference to attached drawings in which:

[0023] Fig. 1 is a schematic block diagram illustrating prior art.

[0024] Fig. 2 is a schematic block diagram illustrating prior art.

[0025] Fig. 3 is a schematic block diagram illustrating example embodiments of a wireless communications network.

[0026] Fig. 4 is a flowchart depicting a combined flow chart and sequence diagram illustrating an example scenario.

[0027] Fig. 5 is a flowchart depicting example embodiments of a method.

[0028] Fig. 6 is a schematic block diagram illustrating example embodiments.

[0029] Fig. 7 is a schematic block diagram illustrating example embodiments.

[0030] Fig. 8 is a line diagram illustrating example embodiments.

[0031] Fig. 9 is a schematic block diagram illustrating example embodiments. Fig. 10 is a schematic block diagram illustrating example embodiments of a network node.

[0032] Fig. 11 shows an example of a communication system QQ100 in accordance with some embodiments.

[0033] Fig. 12 shows a UE QQ200 in accordance with some embodiments.

[0034] Fig. 13 shows a network node QQ300 in accordance with some embodiments.

[0035] Fig. 14 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Fig. 11 , in accordance with various aspects described herein.

[0036] Fig. 15 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized.

[0037] Fig. 16 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments.

[0038] DETAILED DESCRIPTION

[0039] As summarized above, as part of developing embodiments herein the inventors have identified problems synchronization in FDD radio as introduced in the summary.

[0040] In embodiments herein, FDD radio may relate to communication in both UL and DL bands. Bands as used herein may relate to different one or more frequencies, or different one or more intervals of frequencies.

[0041] Embodiments herein may relate to a solution in a network node to utilize at least one DL receive path to receive one or more synchronization signals such as RIBS in FDD radio. The at least one DL receive path may comprise and / or may be represented by at least one Transmitter Observation Receiver (TOR) path. A TOR path as used herein may be a path associated with a processing or receiving of signals in DL band such as any path represented between any suitable Power Amplifier (PA) or coupling unit and an Analog to Digital Converter (ADC) for converting . It should be noted that TOR path as used herein may mean any suitable TOR path, which respective TOR path may be modified or not, e.g., as in some of the embodiments herein

[0042] To achieve this, at least one calibration signal is received in the at least one DL path and in at least one UL path. The at least one calibration signal may be used to determine a difference delay and / or phase between the at least one DL path and the at least one UL path. Using the difference, the at least one DL path and the at least one UL path can be synchronized such as to achieve improved beamforming gain for synchronization signal receiving as well as a UL timing alignment with OTA synchronization. This calibration solution further improves the time alignment between the at least one DL path and the at least one UL path such that the UL timing can be sync with OTA synchronization signals, such as OTA RIBS.

[0043] While some advantages have already been mentioned above, advantages to embodiments herein may overcome at least some of the above-mentioned problems and may also relate to any one or more out of the below-mentioned advantages:

[0044] Embodiments herein may enable OTA synchronization in FDD radio networks, such as OTA RIBS synchronization.

[0045] Embodiments herein may enable receiving synchronization signals such as RIBS with a low cost solution by utilizing at least one TOR path, Embodiments herein may enable improved beamforming gain with calibration on multiple TOR paths, this may be achieved by a coherent combining of received signals.

[0046] Embodiments herein may enable that UL timing may be aligned with synchronization such as OTA synchronization by utilizing dual band calibration on TOR and UL paths, Embodiments herein may improve performance of UL coordination features such as UL Comp and / or positioning on FDD radio.

[0047] Fig. 3 is a schematic overview depicting a wireless communications network 100 wherein embodiments herein may be implemented. The wireless communications network 100 comprises one or more RANs and one or more CNs. The wireless communications network 100 may use 5G NR but may further use a number of other different technologies, such as, Wi-Fi, (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0048] Network nodes such as a network node 110 operates in the wireless communications network 100. The network node 110 may provide a number of cells referred, and may use these cells for communicating with any one or more suitable UEs operating in these cells. The radio network node 110 may be a transmission and reception point e.g. a radio access network node such as a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNodeB, eNode B), an NR Node B (gNB), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a Wireless Local Area Network (WLAN) access point, an Access Point Station (AP STA), an access controller, a UE acting as an access point or a peer in a Device to Device (D2D) communication, or any other network unit capable of communicating with a UE within any cell served by the radio network node 110, e.g. depending on the radio access technology and terminology used. In particular, the radio network node 110 may be able to handle MBS sessions and associated MBS session multicast communication. The radio network node 110 may at least partly be configured to hand an RRC state for UEs. The radio network node 110 may at least partly be configured to forward MBS session communication and / or other communication from network nodes in the CN to one or more UEs and / or vice versa from UE to the CN. MBS broadcast and multicast data may be strictly in Downlink (DL) only. In a connected mode, Uplink (UL) signaling may exist for both MBS broadcast and multicast.

[0049] UEs may operate in the wireless communications network 100. UEs as used herein may respectively provide radio coverage by means of a number of antenna beams, also referred to as beams herein. UEs as used herein may respectively e.g. be an NR device, a mobile station, a wireless terminal, an NB-loT device, an eMTC device, an NR RedCap device, a CAT-M device, a Wi-Fi device, an LTE device and a non-access point (non-AP) STA, a STA, that communicates via a base station such as e.g. the network node 110, one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN). It should be understood by the skilled in the art that the UE relates to a non-limiting term which means any UE, terminal, wireless communication terminal, user equipment, (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.

[0050] One or more radio units 111, 112 may operate in the wireless communications network 100 such as a first radio unit 111 and / or a second radio unit 112. The one or more radio units 111, 112 may respectively be UEs or network nodes or any suitable radio units. In some embodiments, the first radio unit may be a network node and the second radio unit 112 may be a UE.

[0051] The network node 110 may be configured to communicate with the first radio unit 111 and / or the second radio unit 112 at least partly using at least one DL receive path 160 of the network node 110 and / or at least one UL receive path 150 of the network node 110. Each of the at least one UL receive path 150 and the at least one DL receive path 160 may respectively comprise any suitable units for receiving the signaling in respective frequency band, such as any one or more out of: analog to digital converters, amplifiers, filters, control units, circulators, (de-)multiplexers, and any other suitable unit. In particular, the least one DL receive path 160 may comprise at least one TOR path.

[0052] A TOR path as used herein may mean a full path for signals to be communicated from a Power Amplifier to a Analog to Digital Converter of the DL receive path 160. In embodiments herein, when discussing embodiments herein, the at least one DL received path may correspond to at least one TOR path, or may correspond to at least one TOR path which has been modified to receive amplified communication.

[0053] The first radio unit 111 and / or the second radio unit 112 may be configured to communicate with the network node 110 using FDD radio, e.g., in DL and / or UL bands using any or both of the least one DL receive path 160 and the at least one DL receive path 150. In particular, the first radio unit 111 may be a second network node, e.g., a gNB, configured to communicate with the network node 110 using DL band e.g., using the at least one DL receive path 160. In particular, the second radio unit 112 may be a UE configured to communicate with the network node 110 using UL band e.g., using the at least one UL receive path 150.

[0054] Methods herein may be performed by the network node 110. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud 140 as shown in Fig. 3, may be used for performing or partly performing the methods and embodiments herein.

[0055] In particular, some embodiments herein may relate to any one or more out of: enabling a synchronization solution for FDD radio in the wireless communications network 100, in particular relating to OTA synchronization such as RIBS OTA, utilize a hardware (HW) design to utilize the at least one DL receive path 160 for receiving synchronization signals such as RIBS, and

[0056] Calibrate the at least one DL receive path 160 and the at least one UL receive path 150 for aligning phase in UL / DL communication, and as a consequence to achieve a beamforming gain, and

[0057] Dual Band Calibration on the at least one DL receive path 160 and the at least one UL receive path 150 for aligning timing between UL and DL communication. Embodiments herein address at least some above-mentioned problems. Below follows a number of embodiment which may be performed in any suitable combination.

[0058] Fig. 4 illustrates an example scenario of some embodiments herein. The network node 110 may communicate using FDD radio with the first radio unit 111 and the second radio unit 112. The first radio unit 111 may be a second network node such as a gNB. The second radio unit 112 may be a UE. Some actions described below may be optional, such as the actions depicted by dashed boxes. The network node 110 and the first radio unit 111 may initially synchronize 400 with each other such that their communication over DL band may be synchronized, e.g., at least coarsely synchronized such as to a reference point. This may be performed using any suitable method, e.g. synchronization via the backhaul. The network node 110 receives 401 at least one dual-band calibration signal. The at least one dual-band calibration signal may be received from any suitable source, typically generated internally by the network node 110.

[0059] The at least one dual-band calibration signal may comprise signaling in both UL band and DL band, which may be received by the least one DL receive path 160 and the at least one UL receive path 150 based on the different bands being separated as part of FDD using any suitable technique to split the respective signaling.

[0060] The network node 110 determines 402 a difference in phase and / or delay between the least one DL receive path 160 and the at least one UL receive path 150 i.e. , based on how each respective path receives the at least one dual-band calibration signal. The difference may be further be used to synchronize communication over UL and DL, in particular communication received in the least one DL receive path 160 and the at least one DL receive path 150 can be aligned and / or compensated such that synchronization signals in both UL and DL band can be received such that synchronization over FDD radio is enabled.

[0061] The network node may handle 403 FDD radio based on the determined difference. Handling the FDD radio based on the determined difference may relate to communication using UL and DL bands in FDD radio, e.g., taking into account the determined difference in phase and / or delay between the least one DL receive path 160 and the at least one UL receive path 150 i.e., based on how each respective path receives the at least one dualband calibration signal. Handling the FDD radio based on the determined difference may comprise the following Actions 404-405 or any other suitable actions.

[0062] The first radio unit 111 may transmit and / or receive 411 a synchronization signal in DL band. The second radio unit 112 may transmit 421 a synchronization signal in UL band. The network node 110 may receive and / or transmit 404 the one or more synchronization signals, as transmitted / received by the first radio unit 111 and / or the second radio unit 112, and may consider the determined difference to utilize the received signals for synchronization, e.g., by apply necessary compensation. Therefore a finegrained synchronization between the network node unit 110 and the first radio unit 111 , and / or the second radio unit 112, such as in some embodiments herein, may need to be performed to synchronized them in time and / or phase.

[0063] The second radio unit 112 may transmit 422 traffic signal(s) in UL band, and the network node 110 may receive 405 said traffic signal(s) from the second radio unit 112. The traffic signal(s) may comprise any suitable communication data and may be received based on the determined difference and / or synchronization performed on the basis of the above synchronization signals.

[0064] A number of embodiments will now be described, some of which may be seen as alternatives, while some may be used in combination.

[0065] Fig. 5 illustrates a flow chart of a method performed by the network node 110 for handling FDD radio in the wireless communications network 100. In some embodiments herein, the network node 110 comprises, at least partly as part of the at least one DL receive path 160, at least one TOR path. The method comprises the following actions in any suitable order. Boxes in Fig. 5 illustrated by dashed borders may be considered optional actions.

[0066] Action 501

[0067] The network node 110 receives at least one dual-band calibration signal comprising signaling in at least one UL band and at least one DL band. In other words, the at least one dual-band calibration signal may comprise signaling in FDD radio where UL bands and DL bands are used simultaneously. The signaling in the at least one UL band is received by the at least one UL receive path 150. The signaling in the at least one DL band is received by at least one DL receive path 160. The at least one DL receive path 160 may be the at least one TOR path which may be configured to obtain DL band communication, e.g., through an amplifier such as a low noise amplifier.

[0068] The at least one dual-band calibration signal may be received as transmitted from any suitable entity such as the first radio unit 111. Alternatively, the at least one dual-band calibration signal may be received as internally generated and transmitted from the network node 110. The at least one dual-band calibration signal may comprise signaling in both UL and DL band as part of an FDD radio signal.

[0069] In embodiment when the network node 110 comprises, at least partly as part of the at least one DL receive path 160, the at least one TOR path. The network node 110 may receive the at least one dual-band calibration signal using the at least one TOR path.

[0070] In some embodiments, the network node 110 is configured to receive communication on the at least one DL band from a circuit , i.e., a HW circuit, configured to provide the communication from at least one antenna unit of the at least one DL receive path 160 using at least one amplifying unit of the circuit. In these embodiments, network node may receive the at least one dual-band calibration signal from the at least one antenna unit, via the at least one amplifying unit of the circuit.

[0071] In some embodiments, the at least one dual-band calibration signal comprises a first dual-band calibration signal received at a first point in time and a second dual-band calibration signal received at a second point in time different from the first point in time

[0072] Action 502

[0073] The network node 110 determines a difference between the at least one UL receive path 150 and the at least one DL receive path 160. The difference is determined based on the received signaling of the at least one dual-band calibration signal. The difference is in phase and / or delay between receiving the signaling in the at least one UL receive path 150 and receiving the signaling the at least one DL receive path 160.

[0074] In other words, the at least one dual-band calibration signal may be received with different phase and / or delay in the at least one UL receive path 150 and receiving the signaling the at least one DL receive path 160.

[0075] The difference in phase and / or delay may be caused by that the different paths may have different components, entities or units, for handling and / or processing the signaling which may take longer time and / or may affect the phase of the signaling differently and / or respective paths may physically relate to different circuit characteristics.

[0076] Since the difference is determined, communication is enabled to be synchronized with respect to the determined difference.

[0077] In some embodiments herein, determining the phase and / or delay between the at least one UL receive path 150 and the at least one DL receive path 160, comprises establishing at least one channel response for the at least one UL receive path 150 and the at least one DL receive path 160. The channel response may be based on the received signaling and a predefined indication of the signaling as transmitted. In some embodiments herein, determining the phase and / or delay between the at least one UL receive path 150 and the at least one DL receive path 160 based on the established at least one channel response.

[0078] Action 503

[0079] The network node 110 handles FDD radio in the wireless communications network 100 based on the determined difference between the at least one UL receive path 150 and the at least one DL receive path 160, e.g., as determined in action 502. Handling the FDD radio based on the determined difference may relate to receiving and / or transmitting communication such as one or more synchronization signals using a combination of UL and DL bands in FDD radio, e.g., taking into account the determined difference in phase and / or delay between the least one DL receive path 160 and the at least one UL receive path 150 i.e. , based on how each respective path receives the at least one dual-band calibration signal as received in Action 501. Handling the FDD radio based on the determined difference may comprise the following Actions 504-505 or any other suitable actions or embodiments as described herein.

[0080] Action 504

[0081] In some embodiments, the network node 110, determines a compensation for aligning communication in the at least one UL receive path 150 and the at least one DL receive path 160. The compensation may be determined based on the determined difference in phase and / or delay between the at least one UL receive path 150 and the at least one DL receive path 160. In this way, the communication in the at least one UL receive path 150 and the at least one DL receive path 160 can be aligned such that the different paths can jointly be used for synchronization signals for any suitable purpose needing synchronized communication.

[0082] In some embodiments herein, Action 504 may be performed as part of, instead of, or combined with, Action 503.

[0083] Action 505

[0084] In some embodiments, the network node 110, communicates, e.g., transmitting and / or receiving one or more synchronization signals with one or more radio units 111, 112, such as both the first radio unit 111 and the second radio unit 112, taking into account the determined difference in phase and / or delay between the at least one UL receive path 150 and the at least one DL receive path 160. Typically, the one or more synchronization signals relates to communication using the at least one DL band. The one or more synchronization signals may comprise one or more OTA, synchronization signals. In particular, the one or more synchronization signals relates to any one or more out of: clock synchronization,

[0085] RIBS or corresponding synchronization signaling, positioning, and radio-based sensing such as Joint Communication and Sensing (JCAS).

[0086] JCAS may relate to joint use of radio measurements / communication or lack thereof in a number of different nodes or units to sense objects or areas, such as associated motions or status.

[0087] The communication of the one or more synchronization signals with the first radio unit 111 and / or the second radio unit 112 may be compensated using the compensation as determined in action 504. The network node 110 may communicate with the first radio unit 111 in the at least one DL receive path 160, and / or with the second radio unit 112 in the at least one UL receive path 150.

[0088] In embodiment when the network node 110 comprises, at least partly as part of the at least one DL receive path 160, the at least one TOR path. The network node 110 may communicate the one or more synchronization signals with the one or more radio units 111 , 112 by communicating one or more OTA synchronization signals, e.g., using the at least one TOR path.

[0089] In some embodiments herein, Action 505 may be performed as part of, instead of, or combined with, Action 503. Additionally or alternatively, Action 505 may be performed in combination with any suitable embodiments as described in Action 503 or 504.

[0090] Fig. 6 illustrates a schematic design of a HW part of the network node 110, which may be used to implement at least some of the embodiments herein.

[0091] The network node 110 comprises the at least one DL receive path 160 for receiving signaling and / or other communication in DL band.

[0092] The network node 110 comprises the at least one UL receive path 150 for receiving signaling and / or other communication in UL band.

[0093] The network node 110 may further comprise a DL transmit path 610 for transmitting signaling or communication in DL band. Likewise the network node 110 may further comprise a UL transmit path for transmitting signaling or communication in UL band (not illustrated).

[0094] The network node 110 may comprise at least one antenna 671 for receiving radio such as FDD radio, e.g., the at least one dual-band calibration signal. The at least one antenna 671 may be the at least one antenna 671 discussed in the actions above. The at least one antenna 671 may comprise one, two, or more antenna(s) per pair of DL / LIL path out of the at least one DL receive path 160 and the at least one UL receive path 150, but any suitable configuration apply to embodiments herein.

[0095] The at least one antenna 671 may further be connected to an first coupling unit 600 of the network node 110. The first coupling unit 600 may be configured to forward radio between the at least one antenna 671 and one or more filtering units 601, 602 of the network node 110, or between the at least one antenna 671 and an antenna calibration unit 620 of the network node 110. The antenna calibration unit 620 may be arranged to connect the at least on antenna 671 with one or more receive and / or transmit paths of one or more other antennas of the network node 110. This may be to ensure that signals can be transmitted between antennas and their respective receive and / or transmit paths such that respective paths and / or antennas may calibrate with respect to calibration signals transmitted using the antenna calibration unit 620 such as the at least one dualband calibration signal.

[0096] The one or more filtering units 601 , 602 may be configured to split, filter, or otherwise process signals or other communication such that FDD radio as received by the at least one antenna 671 may be split into DL signals to be received into the at least one DL receive path 160 and into UL signals to be received into the at least one UL receive path 150. In the opposite direction, the one or more filtering units 601, 602 may be used to separate signals from DL and UL bands, e.g., to form FDD radio for transmission and receiving by the at least one antenna 671.

[0097] A DL filtering unit 602 of the or more filtering units 602 may be connected to a circulator 603 of the network node 110. The circulator 603 may be arranged to route or forward signals from the DL filtering unit 602, towards a second coupling unit 604 and / or to route or forward signals to a circuit 670 of the at least one DL receive path 160. The circulator 603 may be optional and may only be needed when the circuit 670 is part of the embodiments. Instead, the DL filtering unit 602 may be connected directly with the second coupling unit 604.

[0098] The second coupling unit 604 may be arranged to forward signals from the DL filtering unit 602, to the at least one DL receive path 160, or alternatively, to forward signals from the DL transmit path 610 to the one or more filtering units, 602.

[0099] The second coupling unit 604 may be arranged to forward signals from the DL filtering unit 602, to the at least one DL receive path 160, typically passing through a TOR multiplexing unit 662 which may be used for sharing units within the at least one DL receive path 160. In some embodiments herein, the signal forwarded by the second coupling unit 601 may be too weak or noisy, in particular relating to determining a difference in phase and / or delay with respect to the at least one dual-band calibration signal. Due to this reason, the circulator 603 may be configured to route signals such as the DL part of the at least one dual-band calibration signal the circuit 670, which may pass signals through at least one amplifying unit 672 before being forwarded towards a DL ADC 665. In this way, signals may be amplified to the at least one DL receive path 160, e.g., being a TOR path, for improved quality of signals received, such as the DL part of the at least one dual-band calibration signal. The circuit 670 and / or the at least one amplifying unit 672 may be the circuit and / or the at least one amplifying unit as discussed in the actions above. The at least one amplifying unit 672 may comprise at least one Low Noise Amplifier (LNA).

[0100] In other words, Fig. 6 illustrates a HW design which may reuse a TOR path, i.e., the at least one DL receive path 160, e.g., for receiving the one or more synchronization signals. The circuit 670 may be arranged to receive the one or more synchronization signals, e.g., RIBS, and may receive a signal from the circulator 603 after and amplifies by the at least one amplifying unit 672 similar to achieve a low noise figure. The amplified signal in the TX / DL band is switched into the at least one DL receive path 160, e.g., being a TOR path, by an analog switch in front of a 1:4 TOR sharing Multiplexer (MUX), i.e., the TOR multiplexing unit 662. The switching may be done in this way or by a 1 :5 MUX instead of the 1:4, or by any other suitable MUX.

[0101] An identified drawback to the above-mentioned solution of Fig. 6 may be that a digital delay between a UL ADC 666 of the at least one UL receive path 160, and the DL ADC 665 may have an unknown delay relationship, e.g., due to timing uncertainty associated with circuits of the different receive paths such as due to clock synchronization for the ADCs 665, 666 and / or delay in associated digital circuits and / or due to temperature varying delays differences between the TX and RX parts in the duplex filter, i.e., the one or more filtering units 601 , 602, and for any filters in the different receive paths 150, 160. These delay uncertainties may be calibrated with an antenna calibration network such as the antenna calibration unit to achieve better time accuracies for synchronization and future 6G features like positioning and evolved MIMO, e.g., as discussed in the actions above.

[0102] While not explicitly being illustrated to be part of the at least one DL receive path 160 in Fig. 6, it should be noted that the second coupling unit 604 and / or the circulator 603 may also be considered to be part of the at least one DL receive path 160. With regards to the respective at least one TOR path of the at least one DL receive path 160, the at least one TOR path may be from the second coupling unit 604 and / or the at least one amplifying unit 672, to the DL ADC 665. The at least one TOR path may or may not comprise part of, or the entire circuit 670.

[0103] Fig. 7 illustrates a calibration solution for the at least one DL receive path 160 and the at least one UL path 150. In some embodiments it may be possible to reuse Antenna Calibration (AC) units which already typically exist in network nodes employing FDD radio, in particular for Advanced Antenna Systems (AAS). The antenna calibration unit 720 may be such a reused unit as part of the network node 110. A dual-band calibration signal 700 is illustrated with two bands, signaling in DL band is indicated by a solid line and signaling in UL band is indicated by the dashed line. In a corresponding manner, the path for the signaling of the dual-band calibration signal 700 is indicated by the solid line as being transmitted towards the at least one DL receive path 160, and the dashed line being transmitted towards the at least one UL path 150. The dual-band calibration signal 700 may be, or may be part of the at least one dual-band calibration signal discussed in the actions above. The dual band calibration signal 700 may be transmitted to the at least one DL receive path 160, and the at least one UL path 150, simultaneously or in a time division manner. After calibration or at least finding the difference in time delay and / or phase as the dual band calibration signal 700, time and / or phase can be aligned between the at least one DL receive path 160, and the at least one UL path 150 for any upcoming communication or signaling events such that accurate synchronization may be made with the network node 110 using a combination of UL and DL communication, e.g., by communication with both UEs and network nodes for synchronization purposes and / or for positioning and / or for JCAS, etc.

[0104] Calibration

[0105] To calibrate the two paths, i.e. , the at least one DL receive path 160, and the at least one UL path 150, a dual band signal x may be transmitted, e.g., such as the at least one dual-band calibration signal as transmitted from the antenna calibration unit 620.

[0106] The dual band signal x may comprise or contain xD, a DL band signaling part, and xU tan UL band signaling part, which may comprise predefined sequences of signaling. A variable k may be used to represent an index of a frequency bin such that x is a function of k as in Equation 1 below. The frequency bin may determine which bands to use for UL and DL.

[0107] Equation 1 : x( / c) = %o( / <) + %u( / c) Then as respective parts of the dual band signal x, a DL calibration signal yDmay be received in the at least one DL receive path 160, and a UL calibration signal yvin the at least one UL path 150.

[0108] A channel response, e.g., as discussed in actions above may be calculated as below in Equations 2-3:

[0109] Equation 2:

[0110] Equation 3:

[0111] A channel matrix may be constructed considering multiple paths or branches e.g., out of the at least one UL path 150 and / or the at least one DL receive path 160. N may be a number of DL paths or TOR paths, e.g., out of the at least one DL receive path 160. M may be a number of UL paths, e.g., out of the at least one UL path 150.

[0112] In equations below, phase may be used as example e.g. by p = angle(Ji).

[0113] In Equation 4 phase for the at least one DL receive path 160 may be calculated, e.g., as receiving its part of the at least one calibration signal,.

[0114] In Equation 5 phase for the at least one UL path 150 may be calculated, e.g., as receiving its part of the at least one calibration signal.

[0115] Equation 4:

[0116] Equation 5:

[0117] An average phase of the at least one UL path 150 and the at least one DL receive path 160 may be respectively calculated as part of Equations 6-7.

[0118] Equation s:

[0119] Equation 7:

[0120] To align delay and phase of the at least one UL path 150 and the at least one DL receive path 160, to a reference point, it may be needed to compensate a phase difference Ap due to frequency difference of the different bands Af as discussed below. G may be a distance between a starting point of a DL band, e.g., of the at least one dualband calibration signal, and the 1stoccupied frequency bin of UL band, e.g., of the at least one dual-band calibration signal, is illustrated in Fig. 8. Af and G may be predefined parameters. py(l) may be calculated from above formula. A starting point may not be immediately from the occupied frequency bin due to presence of a guard band, e.g., as indicated by the distance G.

[0121] A difference in phase Ap may be calculated as in Equation 8 below.

[0122] Equation s: Ap = > ^p0(l) It is further possible to align the phase of UL signal(s) to DL signal(s) by subtracting Ap. One or more compensation weights (cr) for the at least one DL receive path 160 and (cy) for the at least one UL path 150 may be calculated as in Equations 9-10 and may form the compensation as discussed in the actions above.

[0123] Equation 9:

[0124] Equation 10:

[0125] Fig. 9 illustrates and end-to-end communications diagram where the difference in phase and delay may be taken into account such that synchronized communication by the one or more synchronization signals, such as RIBS, may be received in the at least one antenna, from the one or more radio units 111, 112 such as from the first radio unit 111 , e.g., a gNB, in a DL signal, and from the second radio unit 112, e.g., a UE, in a UL signal. The at least one antenna 671 may in these scenario comprise multiple antennas with respective UL and DL paths of the at least one UL path 150 and the at least one DL receive path 160.

[0126] The one or more synchronization signals, e.g., RIBS, from the one or more radio units 111 , 112, may be received in the multiple antennas as time and phase aligned signals 929. This is since each communication passing through the respective UL and DL paths of the at least one UL path 150 and the at least one DL receive path 160 may be compensated using respective compensation units 911, 912, 913, 914, which may be arranged to align signaling based on the determined difference in phase and delay of between the at least one UL path 150 and the at least one DL receive path 160 such as applying the compensation as calculated by Equations 9 and 10 above.

[0127] It follows that UL coordinated features may achieve a higher accuracy based on OTA synchronization such as using RIBS, over FDD radio. It further follows that positioning or other features needing time and phase aligned UL and DL communication may be performed using different units, e.g., UEs and gNBs, in mixed UL and DL, over FDD radio.

[0128] To perform the method actions above, the network node 110 may comprise an arrangement depicted in Fig. 10. The network node 110 may be configured to handle FDD radio in the wireless communications network 100.

[0129] The network node 110 may comprise an input and output interface 1000 configured to communicate with any suitable entity described herein, e.g., the one or more radio units 111, 112. The input and output interface 1000 may comprise a wireless receiver not shown, and a wireless transmitter not shown.

[0130] The network node 110 is configured to receive at least one dual-band calibration signal comprising signaling in at least one UL band and at least one DL band. The signaling in the at least one UL band is received by the at least one UL receive path 150. The signaling in the at least one DL band is received by the at least one DL receive path 160. The network node 110 is configured to, based on the received signaling of the at least one dual-band calibration signal, determine a difference between the at least one UL receive path 150 and the at least one DL receive path 160. The difference is in phase and / or delay between receiving the signaling in the at least one UL receive path 150 and receiving the signaling the at least one DL receive path 160.

[0131] In some embodiments, the network node 110 is configured to determine the phase and / or delay between the at least one UL receive path 150 and the at least one DL receive path 160, by: based on the received signaling and a predefined indication of the signaling as transmitted, establishing at least one channel response for the at least one UL receive path 150 and the at least one DL receive path 160, and determining the phase and / or delay between the at least one UL receive path 150 and the at least one DL receive path 160 based on the established at least one channel response.

[0132] In some embodiments, the network node 110 is configured to, based on the determined difference in phase and / or delay between the at least one UL receive path 150 and the at least one DL receive path 160, determine a compensation for aligning communication in the at least one UL receive path 150 and the at least one DL receive path 160.

[0133] In some embodiments, the network node 110 is configured to communicate one or more synchronization signals with one or more radio units 111, 112, taking into account the determined difference in phase and / or delay between the at least one UL receive path 150 and the at least one DL receive path 160.

[0134] In some embodiments, the one or more synchronization signals relates to communication using the at least one DL band.

[0135] In some embodiments, the network node 110 comprises, at least partly as part of the at least one DL receive path 160, the at least one TOR path. In some embodiments, the network node 110 may be configured to communicate the one or more synchronization signals with the one or more radio units 111 , 112 by communicating one or more OTA synchronization signals, e.g., using the at least one TOR path.

[0136] In some embodiments, the one or more synchronization signals relates to any one or more out of: clock synchronization, positioning, and radio-based sensing such as JCAS.

[0137] In some embodiments, the network node 110 comprises, at least partly as part of the at least one DL receive path 160, the at least one TOR path. In some of these embodiments, the network node 110 may be configured to receive the at least one dualband calibration signal using the at least one TOR path.

[0138] In some embodiments, the network node 110 is configured to receive communication on the at least one DL band from the circuit 670. The circuit 670 may be configured to provide the communication from the at least one antenna unit 671 of the at least one DL receive path 160 using the at least one amplifying unit 672 of the circuit 670. The network node 110 may be configured to receive the at least one dual-band calibration signal from the at least one antenna unit 671 , via the at least one amplifying unit 672 of the circuit 670.

[0139] In some embodiments, the at least one dual-band calibration signal comprises a first dual-band calibration signal received at a first point in time and a second dual-band calibration signal received at a second point in time different from the first point in time.

[0140] The embodiments herein may be implemented through a processor or one or more processors, such as at least one processor 1040 of a processing circuitry in the network node 110 depicted in Fig. 10, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the network node 110. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the network node 110.

[0141] The network node 110 may further comprise respective a memory 1050 comprising one or more memory units. The memory comprises instructions executable by the processor in the network node 110. The memory is arranged to be used to store instructions, data, configurations, and applications to perform the methods herein when being executed in the network node 110.

[0142] In some embodiments, a computer program 1060 comprises instructions, which when executed by the at least one processor, cause the at least one processor of the network node 110 to perform the actions above.

[0143] In some embodiments, a respective carrier 1070 comprises the respective computer program, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0144] The network node 110 may further be configured to perform any one or more out of actions the above-mentioned actions in any suitable order, e.g., by used of the at least one processor 1040 and / or by use of a control unit, and / or by use of any other suitable means.

[0145] Those skilled in the art will also appreciate that the functional modules in the network node 110, described below may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware, e.g. stored in the network node 110, that when executed by the respective one or more processors such as the at least one processor described above cause the respective at least one processor to perform actions according to any of the actions above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

[0146] ADDITIONAL EXPLANATION

[0147] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0148] Fig. 11 shows an example of a communication system QQ100 in accordance with some embodiments.

[0149] In the example, the communication system QQ100, e.g., the wireless communications network 100, includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network RAN, and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as the network node 110 and may be referred to as network nodes QQ110, or any other similar 3rd Generation Partnership Project 3GPP access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN ORAN network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification e.g., a specification published by the O-RAN Alliance, or any similar organization and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0150] Examples of an ORAN network node include an open radio unit 0-Rll, an open distributed unit 0-Dll, an open central unit O-CU, including an O-CU control plane O-CU- CP or an O-CU user plane O-CU-UP, a RAN intelligent controller near-real time or non- real time hosting software or software plug-ins, such as a near-real time control application e.g., xApp or a non-real time control application e.g., rApp, or any combination thereof the adjective “open” designating support of an ORAN specification. The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment described further below in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment UE, such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d one or more of which may be generally referred to as UEs QQ112 being examples of a UE 121 to the core network QQ106 over one or more wireless connections.

[0151] Example wireless communications over a 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 without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0152] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

[0153] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes e.g., core network node QQ108 that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center MSC, Mobility Management Entity MME, Home Subscriber Server HSS, Access and Mobility Management Function AMF, Session Management Function SMF, Authentication Server Function AUSF, Subscription Identifier Deconcealing function SIDF, Unified Data Management UDM, Security Edge Protection Proxy SEPP, Network Exposure Function NEF, and / or a User Plane Function UPF.

[0154] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0155] As a whole, the communication system QQ100 of Fig. 11 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications GSM; Universal Mobile Telecommunications System UMTS; Long Term Evolution LTE, and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard e.g., 6G; wireless local area network WLAN standards, such as the Institute of Electrical and Electronics Engineers IEEE 802.11 standards WiFi; and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access WiMax, Bluetooth, Z-Wave, Near Field Communication NFC ZigBee, LiFi, and / or any low-power wide-area network LPWAN standards such as LoRa and Sigfox.

[0156] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication URLLC services to some UEs, while providing Enhanced Mobile Broadband eMBB services to other UEs, and / or Massive Machine Type Communication mMTC / Massive loT services to yet further UEs.

[0157] In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi- RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR New Radio and LTE, i.e. being configured for multi-radio dual connectivity MR-DC, such as E-UTRAN Evolved-UMTS Terrestrial Radio Access Network New Radio - Dual Connectivity EN-DC.

[0158] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs e.g., UE QQ112c and / or QQ112d and network nodes e.g., network node QQ110b. In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0159] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs e.g., UE QQ112c and / or QQ112d, and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0160] Fig. 12 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP VoIP phone, wireless local loop phone, desktop computer, personal digital assistant PDA, wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment LEE, laptop-mounted equipment LME, smart device, wireless customerpremise equipment CPE, vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project 3GPP, including a narrow band internet of things NB-loT UE, a machine type communication MTC UE, and / or an enhanced MTC eMTC UE.

[0161] A UE may support device-to-device D2D communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication DSRC, vehicle-to-vehicle V2V, vehicle-to-infrastructure V2I, or vehicle-to- everything V2X. In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user e.g., a smart sprinkler controller. Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user e.g., a smart power meter.

[0162] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure QQ2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0163] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines e.g., in discrete logic, field-programmable gate arrays FPGAs, application specific integrated circuits ASICs, etc.; programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor DSP, together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units CPUs.

[0164] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device 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. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or 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 may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus USB port may be used to provide an input device and an output device.

[0165] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source e.g., an electricity outlet, photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0166] The memory QQ210 may be or be configured to include memory 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 disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0167] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks RAID, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc HD-DVD optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage HDDS optical disc drive, external mini-dual in-line memory module DIMM, synchronous dynamic random access memory SDRAM, external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card UICC including one or more subscriber identity modules SIMs, such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC eUlCC, integrated UICC iUICC or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non- transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0168] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication e.g., another UE or a network node in an access network. Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications e.g., optical, electrical, frequency allocations, and so forth. Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas e.g., antenna QQ222 and may share circuit components, software or firmware, or alternatively be implemented separately.

[0169] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system GPS to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing 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, and so forth.

[0170] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic e.g., once every 15 minutes if it reports the sensed temperature, random e.g., to even out the load from reporting from several sensors, in response to a triggering event e.g., when moisture is detected an alert is sent, in response to a request e.g., a user initiated request, or a continuous stream e.g., a live video feed of a patient.

[0171] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0172] A UE, when in the form of an Internet of Things loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot 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 / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smartwatch, a fitness tracker, a head-mounted display for Augmented Reality AR or Virtual Reality VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle UAV, and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure QQ2.

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

[0174] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information obtained through a speed sensor to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone e.g. by controlling an actuator to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0175] Fig. 13 shows a network node QQ300 in accordance with some embodiments. As used herein, 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 telecommunication 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 NodeBs gNBs, O-RAN nodes or components of an O-RAN node e.g., O-RU, O-DU, O-CU.

[0176] Base stations may be categorized based on the amount of coverage they provide or, stated differently, their transmit power level and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more or all parts of a distributed radio base station such as centralized digital units, distributed units e.g., in an O-RAN access node and / or remote radio units RRUs, sometimes referred to as Remote Radio Heads RRHs. Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system DAS.

[0177] Other examples of network nodes include multiple transmission 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, Operation and Maintenance O&M nodes, Operations Support System OSS nodes, Self-Organizing Network SON nodes, positioning nodes e.g., Evolved Serving Mobile Location Centers E-SMLCs, and / or Minimization of Drive Tests MDTs.

[0178] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc., which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components e.g., BTS and BSC components, one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies RATs. In such embodiments, some components may be duplicated e.g., separate memory QQ304 for different RATs and some components may be reused e.g., a same antenna QQ310 may be shared by different RATs. The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification RFID or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

[0179] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

[0180] In some embodiments, the processing circuitry QQ302 includes a system on a chip SOC. In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency RF transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency RF transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips or sets of chips, boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

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

[0182] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises ports / terminals QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0183] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit not shown, and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit not shown.

[0184] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0185] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0186] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components e.g., at a voltage and current level needed for each respective component. The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source e.g., the power grid, an electricity outlet via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0187] Embodiments of the network node QQ300 may include additional components beyond those shown in Fig. 13 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

[0188] Fig. 14 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Fig. 11 , in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

[0189] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 14 and QQ3, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0190] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs e.g., Versatile Video Coding WC, High Efficiency Video Coding HEVC, Advanced Video Coding AVC, MPEG, VP9 and audio codecs e.g., FLAG, Advanced Audio Coding AAC, MPEG, G.711 , including transcoding for multiple different classes, types, or implementations of UEs e.g., handsets, desktop computers, wearable display systems, heads-up display systems. The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming HLS protocol, Real-Time Messaging Protocol RTMP, Real-Time Streaming Protocol RTSP, Dynamic Adaptive Streaming over HTTP MPEG-DASH, etc.

[0191] Fig. 15 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines VMs implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity e.g., a core network node or host, then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0192] Applications QQ502 which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc. are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0193] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 also referred to as hypervisors or virtual machine monitors VMMs, provide VMs QQ508a and QQ508b one or more of which may be generally referred to as VMs QQ508, and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0194] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization NFV. NFV may 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.

[0195] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0196] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware e.g. such as in a data center or CPE where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0197] Fig. 16 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE such as a UE QQ112a of Fig. 11 and / or UE QQ200 of Figure QQ2, network node such as network node QQ110a of Fig. 11 and / or network node QQ300 of Fig. 13, and host such as host QQ116 of Fig. 11 and / or host QQ400 of Fig. 14 discussed in the preceding paragraphs will now be described with reference to Fig. 16.

[0198] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top OTT connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

[0199] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network like core network QQ106 of Figure QQ1 and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0200] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650. The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0201] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

[0202] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0203] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment.

[0204] In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion e.g., controlling traffic lights. As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services such as compiling diagrams etc. from data collected from remote devices, or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0205] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and / or UE QQ606. In some embodiments, sensors not shown may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

[0206] Although the computing devices described herein e.g., UEs, network nodes, hosts may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0207] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may 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 may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally. When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of".

[0208] The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.

Claims

CLAIMS1. A method performed by a network node (110) for handling Frequency Division Duplexing, FDD, radio in a wireless communications network (100), the method comprising: receiving (501) at least one dual-band calibration signal comprising signaling in at least one Uplink, UL, band and at least one Downlink, DL, band, o wherein the signaling in the at least one UL band is received by at least one UL receive path (150), o wherein the signaling in the at least one DL band is received by at least one DL receive path (160), based on the received signaling of the at least one dual-band calibration signal, determining (502) a difference between the at least one UL receive path (150) and the at least one DL receive path (160), the difference being in phase and / or delay between receiving the signaling in the at least one UL receive path and receiving the signaling the at least one DL receive path, and handling (503) FDD radio in the wireless communications network (100) based on the determined difference between the at least one UL receive path (150) and the at least one DL receive path (160).

2. The method according to claim 1, wherein determining (502) the phase and / or delay between the at least one UL receive path (150) and the at least one DL receive path (160), comprises: based on the received signaling and a predefined indication of the signaling as transmitted, establishing at least one channel response for the at least one UL receive path (150) and the at least one DL receive path (160), and determining the phase and / or delay between the at least one UL receive path (150) and the at least one DL receive path (160) based on the established at least one channel response.

3. The method according to claim 1 or 2, further comprising: based on the determined difference in phase and / or delay between the at least one UL receive path (150) and the at least one DL receive path (160),determining (504) a compensation for aligning communication in the at least one UL receive path (150) and the at least one DL receive path (160).

4. The method according to any of claims 1-3, further comprising: communicating (505) one or more synchronization signals with one or more radio units (111, 112), taking into account the determined difference in phase and / or delay between the at least one UL receive path (150) and the at least one DL receive path (160).

5. The method according to claim 4, wherein the one or more synchronization signals relates to communication using the at least one DL band.

6. The method according to claim 4 or 5, wherein communicating the one or more synchronization signals with the one or more radio units (111, 112) comprises communicating one or more Over The Air, OTA, synchronization signals.

7. The method according to claim 4 or 6, wherein the one or more synchronization signals relates to any one or more out of: clock synchronization, positioning, and radio-based sensing such as Joint Communication and Sensing, JCAS.

8. The method according to any of claims 1-7, wherein the network node (110) comprises, at least partly as part of the at least one DL receive path (160), at least one Transmitter Observation Receiver, TOR, path.

9. The method according to claim 1-8 wherein the network node (110) is configured to receive communication on the at least one DL band from a circuit(670) configured to provide the communication from at least one antenna unit(671) of the at least one DL receive path (160) using at least one amplifying unit(672) of the circuit (670), and wherein the method comprises receiving (501) the at least one dual-band calibration signal from the at least one antenna unit (671), via the at least one amplifying unit (672) of the circuit (670).

10. The method according to any of claims 1-9, wherein the at least one dual-band calibration signal comprises a first dual-band calibration signal received at a firstpoint in time and a second dual-band calibration signal received at a second point in time different from the first point in time.

11. A network node (110) configured to handle Frequency Division Duplexing, FDD, radio in a wireless communications network (100), the network node (110) is further configured to: receive at least one dual-band calibration signal comprising signaling in at least one Uplink, UL, band and at least one Downlink, DL, band, o wherein the signaling in the at least one UL band is received by at least one UL receive path (150), o wherein the signaling in the at least one DL band is received by at least one DL receive path (160), based on the received signaling of the at least one dual-band calibration signal, determine a difference between the at least one UL receive path (150) and the at least one DL receive path (160), the difference being in phase and / or delay between receiving the signaling in the at least one UL receive path (150) and receiving the signaling the at least one DL receive path (160), and handle FDD radio in the wireless communications network (100) based on the determined difference between the at least one UL receive path (150) and the at least one DL receive path (160).

12. The network node (110) according to claim 11 , further configured to determine the phase and / or delay between the at least one UL receive path (150) and the at least one DL receive path (160), by: based on the received signaling and a predefined indication of the signaling as transmitted, establishing at least one channel response for the at least one UL receive path (150) and the at least one DL receive path (160), and determining the phase and / or delay between the at least one UL receive path (150) and the at least one DL receive path (160) based on the established at least one channel response.

13. The network node (110) according to claim 11 or 12, further configured to: based on the determined difference in phase and / or delay between the at least one UL receive path (150) and the at least one DL receive path (160),determine a compensation for aligning communication in the at least one UL receive path (150) and the at least one DL receive path (160).

14. The network node (110) according to any of claims 11-13, further configured to: communicate one or more synchronization signals with one or more radio units (111 , 112), taking into account the determined difference in phase and / or delay between the at least one UL receive path (150) and the at least one DL receive path (160).

15. The network node (110) according to claim 14, wherein the one or more synchronization signals relates to communication using the at least one DL band.

16. The network node (110) according to claim 14 or 15, wherein the network node (110) is configured to communicate the one or more synchronization signals with the one or more radio units (111 , 112) by communicating one or more Over The Air, OTA, synchronization.

17. The network node (110) according to claim 14 or 16, wherein the one or more synchronization signals relates to any one or more out of: clock synchronization, positioning, and radio-based sensing such as Joint Communication and Sensing, JCAS.

18. The network node (110) according to any of claims 11-17, wherein the network node (110) comprises, at least partly as part of the at least one DL receive path (160), at least one Transmitter Observation Receiver, TOR, path, and wherein the network node (110) is configured to receive the at least one dual-band calibration signal using the at least one TOR path.

19. The network node (110) according to claim 18 wherein the network node (110) is configured to receive communication on the at least one DL band from a circuit (670) configured to provide the communication from at least one antenna unit (671) of the at least one DL receive path (160) using at least one amplifying unit (672) of the circuit (670), and wherein the network node (110) is configuredto receive the at least one dual-band calibration signal from the at least one antenna unit (671), via the at least one amplifying unit (672) of the circuit (670).

20. The network node (110) according to any of claims 11-19, wherein the at least one dual-band calibration signal comprises a first dual-band calibration signal received at a first point in time and a second dual-band calibration signal received at a second point in time different from the first point in time.

21. A computer program (1060) comprising instructions, which when executed by a processor (1050), causes the processor to perform actions according to any of claims 1-10.

22. A carrier (1070) comprising the computer program (1060) of claim 21, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

Images