TECHNICAL FIELD

Embodiments herein relate to a network node and a method therein. In some aspects, they relate to controlling time critical events of multiple functional blocks building up a transceiver system in the network node.

BACKGROUND

In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and/or User Equipments (UE)s, communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. 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.

3GPP is the standardization body for specify the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for the Evolved Packet System (EPS), also called a Fourth Generation (4G) network, have been completed within the 3rd Generation Partnership Project (3GPP). As a continued network evolution, the new releases of 3GPP specifies a 5G network also referred to as 5G New Radio (NR).

Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station, 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. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. Such systems and/or related techniques are commonly referred to as MIMO.

There is an increasing demand for radio capacity, energy saving and energy efficiency optimization features in radio base stations today. The number of antenna branches have grown over the years. Thus, the number of components relating to the growing number of antenna branches to be controlled by a signal controller Application- Specific Integrated Circuitry (ASIC), comprised in a radio board of a radio base station has also increased significantly. A radio board when used herein e.g. means a unit built- up by a group of electrical, mechanical or electromechanical components which is capable of performing functions required to process baseband information and translate the information to modulated signals to be sent out via air interface, as well as receiving modulated signals from air interface and convert them to baseband information.

SUMMARY

As a part of developing embodiments herein the inventors identified a problem which first will be discussed.

Time critical control signals are often implemented by allocating individual General- Purpose Input/Output (GPIO) pins for each signal on a radio board. A Time critical control signal when used herein is a signal to switch between different operating states such as e.g., normal traffic/calibration/power save/error protection etc., in a timely manner fulfilling 3GPP requirements, e.g., TX ON to OFF transient time within 10us, optimizing the radio performance, e.g., fast adjustment of the UL gain with a deterministic latency, or protecting the radio hardware, e.g., putting certain parts of the radio into safe state. With growing number of components and increased integration level of the controller ASIC, the amount of GPIO pins needed becomes a limiting factor for the ASIC package size.

A GPIO is an uncommitted digital signal pin on an integrated circuit or electronic circuit board which may be used as an input or output, or both, and is controllable by an application at runtime.

In order to reduce the amount of GPIO pin counts, it is possible to control target components via serial bus protocol, such as Improved Inter-Integrated Circuit (I3C) and Serial Peripheral Interface (SPI).

I3C protocol is a 2 signals bus, e.g., a Serial Data Line (SDA) and Serial Clock Line (SCL) bus, where timing event information is sent from the controller to the target components. Timing event information when used herein is e.g. event information to an operational state in addressed devices such as turning on or off a transmitter. However, the bus speed is 12.5 Mbps in standard data rate, and 25Mbps in double data rate. This is too slow for time critical controls that needs to fulfill the 3GPP LTE/NR symbol-based level resolution requirement.

The SPI protocol bus speed is higher than the I3C protocol, the SPI protocol can support up to 60Mbps. It has at least 3 signals, Master Out Slave In (MOSI), Master In Slave Out (MISO), and Clock Output from Master (CLK), and 1 Chip Select (CS) signal for each target component. This means that the CS signals needed are scaled by the number of target components.

The timing accuracy requirement for the system is really high and it is difficult for the I3C or SPI controllers to fulfill this this requirement, and/or an extra synchronization signal is needed for each of the target components. There is also a trade-off between pin counts, bus speed, and number of target components, e.g. referred to as fanout issue, to be connected on one shared bus. In addition, the realization of the control mechanism is also limited to the standard I3C/SPI protocol specification.

An object of embodiments herein is therefore to provide an improved way of controlling time critical events of multiple components, also referred to as functional blocks, in a wireless communications network. This would provide for the growing number of components.

According to an aspect, the object is achieved by a method performed by a network node of a wireless communications network. The method is for controlling time critical events of multiple functional blocks building up a transceiver system in the network node. The network node sends a common message to the multiple functional blocks on a shared bus in advance of the time critical event. The common message comprises a common indication indicating time critical event data. The which common indication enables each respective individual functional block out of the multiple functional blocks, to: Interpret the common indication of the time critical event data to retrieve its own individual set of rules, assigned to the common indication indicating the time critical event data, and apply one or more actions according to the set of rules of the time critical events.

According to another aspect, the object is achieved by a network node configured to control time critical events of multiple functional blocks building up a transceiver system in the network node of a wireless communications network. The network node is further configured to send a common message to the multiple functional blocks on a shared bus in advance of the time critical event. The common message is adapted to comprise a common indication indicating time critical event data. The common indication is adapted to enable each respective individual functional block out of the multiple functional blocks, to interpret the common indication of the time critical event data to retrieve its own individual set of rules, assigned to the common indication indicating the time critical event data, and apply one or more actions according to the set of rules of the time critical events.

BIEF DESCRIPTION OF THE DRAWINGS

Figure 1a is a schematic block diagram depicting embodiments of a wireless communications system.

Figure 1b is a schematic block diagram depicting embodiments of a controller of the network node and multiple functional blocks in a wireless communications system. Figure 2 is a flow chart depicting embodiments of a method performed by a network node.

Figure 3 is a schematic block diagram depicting embodiments herein.

Figure 4 is a schematic block diagram depicting embodiments herein.

Figure 5 is a schematic block diagram depicting embodiments herein.

Figures 6 a and b are schematic block diagrams depicting embodiments of a network node.

Figure 7 schematically illustrates a telecommunication network connected via an intermediate network to a host computer.

Figure 8 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection.

Figures 9 to 12 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment.

DETAILED DESCRIPTION

Some example embodiments herein referred to as a compact time-synchronized digital control interface.

Example embodiments herein e.g., provide a compact physical interface, with only three signals. An advantage is that they allow time-synchronized event control by a network node e.g., by means of a controller in the network node, to multiple functional blocks such as target components. A further advantage is that they also allow the multiple functional blocks to signal errors back to the to the controller without extra pins. A common message is sent to the multiple functional blocks on a shared bus in advance of a time critical event. The common message transferred over the three signals which indicate a time critical event to multiple or selected functional blocks. The indicated time critical event data may be coded and/or decoded at the respective network node and/or the multiple functional blocks side, to retrieve a functional block’s own individual, e.g., programmed, set of rules e.g., via its own individual look up table. An advantage is that this provides a high level of flexibility for future product configuration. Figure 1a 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.

Network nodes such as the network node 110 operate in the wireless communications network 100. The network node 110 e.g. provides a number of cells and may use these cells for communicating with UEs such as e.g. a UE 125. The one or more cells are provided by means of antenna beams e.g. provided by a transceiver system 120 comprising multiple components, referred to as functional blocks 111, 112, herein. These are not shown in Figure 1a but are depicted in Figure 1b which will be described below.

The 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 a cell served by the network node 110 depending e.g. on the radio access technology and terminology used.

UEs operate in the wireless communications network 100, such as a UE 125. The UE 125 may provide radio coverage by means of a number of antenna beams 127, also referred to as beams herein.

The UE 125 may 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.

Methods herein may in one aspect 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 Figure 1a, may be used for performing or partly performing the methods.

Figure 1b depicts a controller 150 of the network node 110 and multiple functional blocks 111, 112. A functional block when used herein is e.g. any one out of a digital signal processing block, analog-to-digital or digital-to-analog conversion block, analog signal shaping block, power amplifier, signal switching block, power and/or signal management, beam control block etc. The network node 110 is e.g. associated, connected, accessible to the multiple functional blocks 111 , 112. The number of multiple functional blocks in Figure 1b is 25, but for simplicity, only two of the multiple functional blocks are marked with reference numbers 111 , 112. When using the term multiple functional blocks 111, 112, all multiple functional blocks are meant to be included. However, the number of multiple functional blocks may vary, such as e.g. depending on product category, number of antennas and how much are integrated in each functional block. The maximum number of the multiple functional blocks on a three-signal bus according to embodiments herein, e.g., on a radio board may be decided by product level systemization and radio board design signal integrity factor.

The multiple functional blocks 111, 112 are building up a transceiver system 120 in the network node 110, e.g. in a radio unit of the network node 110. The transceiver system 120 may e.g. be seen as an air interface towards UEs served by the network node and will be used in communications with UEs such as a UE 125..

A time critical event when used herein e.g., means events such as e.g., changing the operation of a functional block such as switching on/off one or more functional block, e.g., fully or partly. Time critical event data when used herein e.g., means messages to be decoded by an individual receiving functional block.

Example embodiments of a method e.g., comprises to send in advance, time critical event data to the multiple functional blocks, also referred to as target components, e.g., via a more compact control protocol comprising a compact communication bus. This protocol needs only three signals to be sent on a shared bus as a message. The three signals e.g. comprise a selected mode signal (MODE_SEL), a mode status signal (MODE_STATUS) and a Clock and/or Synchronization mode signal (MODE_CLK/SYNC). These will be described ore in detail below.

The time critical event data is sent by the network node 110, such as its controller 150 in advance to multiple functional blocks on a shared bus as a message. For each common message, the multiple functional blocks may make its own interpretation on what actions to be taken based on predefined rules such as e.g. in a LUT. A LUT is an example to implement the one or more rules and applying the action when the sync signal arrived.

Thus, the actions to be taken by the multiple functional blocks is e.g., preprogramed via LUT, and thus one and the same common message may be sent to the multiple functional blocks. When looked up, different actions may be taken by the different functional blocks.

Therefore, this is e.g., a compact communication bus, where only one three-signal bus is needed to communicate with many target components such as multiple functional blocks. The maximum number of the multiple functional blocks on a three-signal bus e.g., on a radio board may be decided by product level systemization and radio board design signal integrity factors.

Figure 2 shows an example embodiment of a method performed by the network node 110 in the wireless communications network 100. The network node 110 may e.g. be a radio base station. The method is for controlling time critical events of the multiple functional blocks 111 , 112. The multiple functional blocks 111 , 112 are building up the transceiver system 120 in the network node 110, e.g. in a radio unit. The time critical events to be controlled may in an example scenario be related to a communication between the network node 110 and the UE 125 over an air interface.

In some embodiments, the transceiver system 120 operates in at least one system mode, e.g., a well-defined system mode, for example “normal operation”, “calibration”, “sleep-mode”, “power save mode”, etc. A well-defined system mode when used herein e.g. means “the mode that the system operates in”. Each individual functional block out of the multiple functional blocks 111 , 112 may support a corresponding block mode that builds up each of the at least one system mode. In this way multiple system modes may be supported. Each functional block out of the multiple functional blocks 111, 112 may have an individual mapping between the system mode and the block mode, that may be predefined. This is e.g., to be able to send the same message to multiple functional blocks even when functional blocks shall have different block modes.

The at least one system mode may comprise any one out of: normal operation mode, calibration mode, idle mode, sleep mode, reduced capacity mode, fault protection and/or recovery mode, boost mode, high-capacity mode, reset mode, fail and/or safe modes, soft antenna expansion mode, co-exist mode and others system modes required.

The modes will be described more in detail below. Optional actions are comprised in dashed boxes in Figure 2. The method comprises any one or more out of the actions below:

Action 201

In some embodiments, the network node 110, such as its controller 150, establishes upcoming individual time critical events related to respective functional block of the multiple functional blocks. E.g., the network node 110 establishes upcoming system mode and related individual time critical events related to respective functional block of the multiple functional blocks. This e.g., means that the network node 110, finds out upcoming individual time critical events that are related to respective functional block of the multiple functional blocks.

Action 202

The network node 110, such as its controller 150, sends a common message to the multiple functional blocks 111 , 112. A common message when used herein e.g. means a message to the multiple functional blocks 111, 112, to set the next active system mode. The common message is sent on a shared bus in advance of the time critical event. A shared bus when used herein e.g. means one physical interface from the controller 150 of the network node 110 which is connected to the multiple functional blocks 111 ,112.

The common message comprises a common indication indicating time critical event data. This means that one same common indication of the time critical event data is sent to all functional blocks 111 , 112, but the common indication will be interpreted in different ways in the different functional blocks as will be described below. The common indication enables each respective individual functional block 111 , 112 out of the multiple functional blocks 111 , 112, to:

- Interpret the common indication of the time critical event data, e.g. in its LUT, to retrieve its own individual set of rules, e.g., a programmed set of rules. This set of rules is assigned to the common indication indicating the time critical event data. E.g. the common indication of the time critical event data may be mapped, e.g. in the LUT, to its own individual set of rules. The set of rules e.g. relate to different states that the functional block 111 , 112, need to operate in. The interpretation of the common indication of the time critical event data, in order to retrieve the individual set of rules may be performed by but not limited to consider a preprogrammed LUT, simple hardware state machine and/or logic or other realization methods.

- The common indication further enables to apply one or more actions according to the set of rules of the time critical events e.g., related to the common synchronization mode signal. E.g. apply one or more necessary actions according to the set of rules of the time critical events. The one or more actions may relate to the individual time critical event and may comprise actions that need to be taken sequentially, e.g. in a few micro-second apart, such as switching off a digital receiving chain and switch the analog transceiver from RX mode to TX mode.

In some embodiments, each block mode supported by the respective functional block out of the multiple functional blocks 111, 112, defines a state switch pattern. The state switch pattern may define a state of a control signal to control the time critical events of the respective functional block out of the multiple functional blocks 111, 112. A position in the state switch pattern may be controlled by a synchronization signal in the common message. The state switch pattern will be described more in detail below.

As mentioned above, in some embodiments, each individual e.g., programmed, set of rules is mapped to a common indication, and comprises in these embodiments, a mapping of modes between the at least one system modes and the block mode. The time critical event data indicated in the common indication may comprise a system mode. The system mode may enable each respective individual functional block 111 , 112 out of the multiple functional blocks 111 , 112 to look up the indicated system mode in its individual e.g., programmed, set of rules to retrieve its individual corresponding block mode.

In some embodiments, the common message is a common three signal bus message indicating time critical event data. The three signals e.g., comprises: A selected mode signal, also referred to as MODE_SEL, a mode status signal, also referred to as MODE_STATUS, and a clock and/or synchronization mode signal, also referred to as MODE_CLK/SYNC.

The selected mode signal is e.g., a signal that may comprise select functions used to inform about which one out of time critical event data (1) or (2) that is selected to be comprised any one or more out of the other two signals mode status signal and clock and/or synchronization mode described below. The mode status signal is e.g., a signal that may comprise time critical event data of any one or more out of:

(1) Data to be sent from the controlling network node 110, such as its controller 150, to the multiple functional blocks 111 , 112. The data may comprise serialized information, e.g., including parity. Serialized information when used herein e.g., means system mode setting, configuration and/or control instructions, functional block mapping.

(2) Data from the multiple functional blocks to the controlling network node 110, such as its controller 150. The data may comprise error signalling, e.g. by pulling the signal LOW, e.g., pulling the signal in a predefined pattern.

The clock and/or synchronization mode signal is e.g., is a signal that may comprise time critical event data of any one or more out of:

(1) Data to be sent from the controlling network node 110, such as its controller 150, to the multiple functional blocks: This data may comprise a clock. This means that the data rate may be defined based on the need; in addition, this also open up possibility to use this interface for functional blocks which don’t have core clock.

(2) Data to be sent from the controlling network node 110 to the multiple functional blocks: This data may comprise a synchronization data and/or strobe signal. This means that the synchronization signal is used to release the predefined critical action.

Action 203

In some embodiments, and as mentioned above, the network node 110, such as its controller 150, receives from one or more of the multiple functional blocks, in a common message on a shared bus, an indication that an error has occurred.

The methods will now be further explained and exemplified in below embodiments. These below embodiments may be combined with any suitable embodiment as described above.

Figure 1 b as described above and Figure 3 illustrate example scenarios of the transceiver system 120 according to embodiments herein. Embodiments herein may be suitable for time critical and synchronous control of the multiple functional blocks 111, 112 building transceiver system 120 as illustrated in these figures.

Figure 3 depicts one functional block 111 out of the multiple functional blocks. Each functional block 111, 112, including the functional block 111 may have several control signals as illustrated in Figure 3. These are referred to as A, B, C, D, and E. There may be an arbitrary number of control signals that are decoded from the interface, e.g. used to control several parts of the transceiver and feedback signal chain, including but not limiting to selecting a correct frequency generator.

Order and timing are important for some or all the control signals. This is provided by embodiments herein by the individual states switch pattern, also referred to as step sequence, controlling one or several control signals. The stepping through the switch pattern is e.g., controlled by the synchronization signal, which comprises the time critical actions.

Modes

As mentioned above, embodiments herein allow the transceiver system 120 to operate in one or several modes. In some embodiments, the individual functional blocks out of the multiple functional blocks 111, 112 support corresponding block modes that build up the system mode. Example of system modes may be normal operation mode, calibration mode, idle mode, sleep mode, reduced capacity mode, fault protection and/or recovery mode, boost mode, high-capacity mode, reset mode, fail and/or safe modes, soft antenna expansion mode, co-exist mode and others system modes required etc.

Example of system modes are illustrated in Figure 4. In Figure 4 the multiple functional blocks 111, 112 building up the transceiver system 120 are illustrated in four different system modes each illustrated as a respective array. The example system modes for each respective array are referred to as A, B, C, and D and the block modes are referred to as IDs 1, 2, 3, and 4 for each functional block out of the multiple functional blocks 111, 112 in Figure 4. All the multiple functional blocks are referred to as 111, or 112, but for simplicity, only two functional blocks in each array have a reference number in Figure 4.

In the example of system mode A, the multiple functional blocks 111 , 112 of the transceiver system 120 are set in block mode 1. This system mode A may for example be used when system in normal operation, e.g. multiple functional blocks are focusing a beam to a single UE. In the example of system mode B, some of the multiple functional blocks 111 of the transceiver system 120 at the right part of the array are set in block mode 1 , and the other multiple functional blocks 112 of the transceiver system 120 at the left part of the array are set in block mode 2. This system mode B may for example be used for reduced capacity mode.

In the example of system mode C, a few of the multiple functional blocks 111 of the transceiver system 120 are set in block mode 3 and are spread over the array, and the rest of the multiple functional blocks 112 of the transceiver system 120 are set in block mode 1. This system mode C may for example be used for a calibration mode 1.

In the example of system mode D, about half of the multiple functional blocks 111 of the transceiver system 120 are set in block mode 1 , and the other multiple functional blocks 112 of the transceiver system 120 are set in block mode 4. Here every other block mode is set to 1 in the array, and every other block mode is set to 4 in the array. This system mode D may for example be used for a calibration mode 2.

Thus in some embodiments, each functional block has an individual mapping between system mode and the block mode. This mapping may e.g. be defined during configuration.

State patterns

Each block mode in the respective functional block may define a state switch pattern also referred to as a step sequence. The state pattern defines the state of the control signals. These control signals are signals that are transmitted in accordance with the one or more actions corresponding to the retrieved individual set of rules. Example state switch patterns in four different functional blocks out of the multiple functional blocks are illustrated in Figure 5. Figure 5 exemplifies state switch patterns of respective control signals 501 , 502, 503, 504 in the four different functional blocks 111, 112. The position on, upper position of the respective control signal, and the position off, lower position of the respective control signal, or vice versa, since it may be the other way round too, in the respective state pattern is controlled by a control signal referred to as a synchronization signal, transmitted by the network node 110 such as its controller 150. This e.g., means that multiple functional blocks need to follow a sequence as released by the sync signal to be able to change from one functional block mode to another functional block mode. The sync event represents a step in these sequences. The rules define which individual control signal that are impacted as a function of the position in the step sequence. At synchronization event 1 , Sync 1, the control signal 501 is switching off, the control signal 502 is switched off, the control signal 503 is switching off, and the control signal 504 is switched off.

At synchronization event 2, Sync 2, the control signal 501 is switched off, the control signal 502 is switching on, the control signal 503 is switched off, and the control signal 504 is switched off.

At synchronization event 3, Sync 3, the control signal 501 is switching on, the control signal 502 is switched on, the control signal 503 is switched off, and the control signal 504 is switched off.

At synchronization event 4, Sync 4, the control signal 501 is switched on, the control signal 502 is switched on, the control signal 503 is switched off, and the control signal 504 is switching on.

At synchronization event 5, Sync 5, the control signal 501 is switched on, the control signal 502 is switched on, the control signal 503 is switched off, and the control signal 504 is switching on.

Functionality

Embodiments herein may e.g. support for the following functionality:

Configuration: Definition of mapping of modes between system modes and block modes to be configured. Definition of the state patterns to be configured. Interface settings etc. to be configured. The configuration is not time critical and may be done once or repeatedly depending on need, e.g. at design, or at build, or at integration or at system start or at reconfiguration etc. The configuration may be done via a bus such as e.g. I2C, I3C, SPI, JESD etc. or via re-use of the common 3-signal bus, this may e.g. be referred to as a MODE_SEL, MODE_STATUS, MODE_CLK/SYNC interface, sharing a mode select, a state pattern step and/or synchronization signals and/or lines.

Mode selection: Selection of system mode. This may be performed by the network node 110, such as its controller 150. This may be done via a common bus. The common bus may be realized as a parallel bus or a serial bus depending on the need for modes and timing resolution.

State pattern stepping: The control signals within each functional block may be defined by the common sync signal. This allows for very high time synchronization. Status feedback: Allowing a controlled functional block to signal back to the controller that an error has occurred. If time allows the controlling network node 110 may resend the mode or take other actions to mitigate the potential damage.

Figure 6a and 6b shows an example of arrangement in the network node 110.

The network node 110 may comprise an input and output interface configured to communicate internally and/or with other entities. The input and output interface may comprise a receiver, e.g. wired and/or wireless, (not shown) and a transmitter, e.g. wired and/or wireless, (not shown).

The network node 110 may comprise any one or more out of: An establishing unit, a sending unit, and a receiving unit, to perform the method actions as described herein.

The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor of a processing circuitry in the network node 110 depicted in Figure 6a, 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.

The network node 110 may further comprise respective a memory 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.

In some embodiments, a computer program 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. In some embodiments, a respective carrier 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.

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).

When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of".

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

Embodiments

Below, some example embodiments 1-16 are shortly described. See e.g. Figures 1a-b, 2, 3a-c, 4, 5, 6a, and 6b.

Embodiment 1. A method performed by a network node 110, e.g. a radio base station, for controlling time critical events of multiple functional blocks 111 , 112 building up a transceiver system 120 in the network node 110, e.g. in a radio unit, of a wireless communications network 100, the method comprising any one or more out of: establishing 201 upcoming individual time critical event/s related to respective functional block of the multiple functional blocks, sending 202 a common message to the multiple functional blocks on a shared bus in advance of the time critical event, which common message comprises a common indication indicating time critical event data, which common indication enables each respective individual functional block 111, 112 out of the multiple functional blocks 111, 112, to:

- interpret the common indication of the time critical event data, e.g. in its Look Up Table, LUT, to retrieve its own individual, e.g., programmed, set of rules, assigned to the common indication indicating the time critical event data, and

- apply e.g., necessary one or more actions according to the set of rules of the time critical events.

Embodiment 2. The method according to Embodiment 1 , wherein:

- the transceiver system 120 operate in at least one system mode,

- each individual functional block out of the multiple functional blocks 111, 112 support a corresponding block mode that build up each of the at least one system mode, and

- each functional block out of the multiple functional blocks 111, 112 has an individual mapping between the system mode and the block mode.

Embodiment 3. The method according to any of the Embodiments 1-2, wherein the at least one system mode comprises any one out of: normal operation mode, calibration mode, idle mode, sleep mode, reduced capacity mode, fault protection/recovery mode, boost mode, high capacity mode, reset mode, fail/safe modes, soft antenna expansion mode, co-exist mode and others system modes required.

Embodiment 4. The method according to any of the Embodiments 1-3, wherein:

- each block mode supported by the respective functional block out of the multiple functional blocks 111, 112, defines a state switch pattern,

- the state switch pattern defines a state of a control signal to control the time critical events of the respective functional block out of the multiple functional blocks 111, 112,

- a position in the state switch pattern is controlled by a synchronization signal in the common message. Embodiment 5. The method according to any of the Embodiments 1-4, wherein:

- each individual e.g., programmed, set of rules is mapped to a common indication, comprising a mapping of modes between the at least one system modes and the block mode, and

- the time critical event data indicated in the common indication comprises a system mode, and which system mode enables each respective individual functional block 111 ,

112 out of the multiple functional blocks 111 , 112 to look up the indicated system mode in its individual e.g., programmed, set of rules to retrieve its individual corresponding block mode.

Embodiment 6. The method according to any of the Embodiments 1-5, further comprising: receiving 203 from one or more of the multiple functional blocks, in a common message on a shared bus, an indication that an error has occurred.

Embodiment 7. The method according to any of the Embodiments 1-6, wherein the common message is a common three signal bus message e.g., comprising: a selected mode signal, also referred to as MODE_SEL, a mode status signal, also referred to as MODE_STATUS, and a clock and/or synchronization mode signal, also referred to as MODE_CLK/SYNC.

Embodiment 8. A computer program comprising instructions, which when executed by a processor, causes the processor to perform actions according to any of the Embodiments 1-7.

Embodiment 9. A carrier comprising the computer program of Embodiment 8, 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.

Embodiment 10. A network node 110, e.g. a radio base station, configured to control time critical events of multiple functional blocks 111, 112 building up a transceiver system 120 in the network node 110, e.g. in a radio unit, of a wireless communications network 100, the network node 110 further being configured to any one or more out of: establish, e.g. by means of a sending unit comprised in the network node 110, upcoming individual time critical event/s related to respective functional block of the multiple functional blocks, send, e.g. by means of a sending unit comprised in the network node 110, a common message to the multiple functional blocks on a shared bus in advance of the time critical event, which common message is adapted to comprise a common indication indicating time critical event data, which common indication is adapted to enable each respective individual functional block 111, 112 out of the multiple functional blocks 111 , 112, to:

- interpret the common indication of the time critical event data, e.g. in its Look Up Table, LUT, to retrieve its own individual e.g., programmed, set of rules, assigned to the common indication indicating the time critical event data, and

- apply necessary one or more actions according to the set of rules of the time critical events.

Embodiment 11. The network node 110 according to Embodiment 10, wherein:

- the transceiver system 120 is arranged to operate in at least one system mode,

- each individual functional block out of the multiple functional blocks 111, 112 is adapted to support a corresponding block mode that build up each of the at least one system mode, and

- each functional block out of the multiple functional blocks 111, 112 is adapted to have an individual mapping between the system mode and the block mode.

Embodiment 12. The network node 110 according to any one of the Embodiments 10-11 , wherein the at least one system mode is adapted to comprise any one out of: normal operation mode, calibration mode, idle mode, sleep mode, reduced capacity mode, fault protection/recovery mode, boost mode, high capacity mode, reset mode, fail/safe modes, soft antenna expansion mode, co-exist mode and others system modes required.

Embodiment 13. The network node 110 according to any out of the Embodiments 10-12, wherein:

- each block mode supported by the respective functional block out of the multiple functional blocks 111, 112, is adapted to define a state switch pattern, - the state switch pattern is adapted to define a state of a control signal to control the time critical events of the respective functional block out of the multiple functional blocks 111 , 112,

- a position in the state switch pattern is adapted to be controlled by a synchronization signal in the common message.

Embodiment 14. The network node 110 according to any one of the Embodiments 10-13, wherein:

- each individual e.g., programmed, set of rules is adapted to be mapped to a common indication, comprising a mapping of modes between the at least one system modes and the block mode, and

- the time critical event data indicated in the common indication is adapted to comprise a system mode, and which system mode is adapted to enable each respective individual functional block 111 , 112 out of the multiple functional blocks 111, 112 to look up the indicated system mode in its individual e.g., programmed, set of rules to retrieve its individual corresponding block mode.

Embodiment 15. The network node 110 according to any one of the Embodiments 10-14, further configured to: receive, e.g. by means of a receiving unit comprised in the network node 110, from one or more of the multiple functional blocks, in a common message on a shared bus, an indication that an error has occurred.

Embodiment 16. The network node 110 according to any one of the Embodiments 10-15, wherein the common message is adapted to be a common three signal bus message e.g., comprising: a selected mode signal, also referred to as MODE_SEL, a mode status signal, also referred to as MODE_STATUS, and a clock and/or synchronization mode signal, also referred to as MODE_CLK/SYNC.

Further Extensions and Variations

With reference to Figure 7, in accordance with an embodiment, a communication system includes a telecommunication network 3210 such as the wireless applications network 100, e.g. an loT network, or a WLAN, such as a 3GPP-type cellular network, which comprises an access network 3211, such as a radio access network, and a core network 3214. The access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as the network node 110, access nodes, AP STAs NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 over a wired or wireless connection 3215. A first user equipment (UE) e.g. the UE 125 such as a Non-AP STA 3291 located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c. A second UE 3292 e.g. the UE 125, such as a Non-AP STA in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291 , 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.

The telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220. The intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub-networks (not shown).

The communication system of Figure 7 as a whole enables connectivity between one of the connected UEs 3291 , 3292 and the host computer 3230. The connectivity may be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291 , 3292 are configured to communicate data and/or signaling via the OTT connection 3250, using the access network 3211 , the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries. The OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications. For example, a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 8. In a communication system 3300, a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300. The host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities. In particular, the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The host computer 3310 further comprises software 3311 , which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318. The software 3311 includes a host application 3312. The host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.

The communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330. The hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown) served by the base station 3320. The communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310. The connection 3360 may be direct or it may pass through a core network (not shown in Figure 8) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The base station 3320 further has software 3321 stored internally or accessible via an external connection.

The communication system 3300 further includes the UE 3330 already referred to. Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located. The hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, applicationspecific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 3330 further comprises software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338. The software 3331 includes a client application 3332. The client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310. In the host computer 3310, an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the user, the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 may transfer both the request data and the user data. The client application 3332 may interact with the user to generate the user data that it provides.

It is noted that the host computer 3310, base station 3320 and UE 3330 illustrated in Figure 8 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291 , 3292 of Figure 7, respectively. This is to say, the inner workings of these entities may be as shown in Figure 8 and independently, the surrounding network topology may be that of Figure 7.

In Figure 8, the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the use equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network). The wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the applicable RAN effect: data rate, latency, power consumption, and thereby provide benefits such as corresponding effect on the OTT service: e.g. reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime.

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 3350 between the host computer 3310 and UE 3330, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 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 3311, 3331 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that the software 3311, 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.

Figure 9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station such as the network node 110, and a UE such as the UE 125, which may be those described with reference to Figure 7 and Figure 8. For simplicity of the present disclosure, only drawing references to Figure 9 will be included in this section. In a first action 3410 of the method, the host computer provides user data. In an optional subaction 3411 of the first action 3410, the host computer provides the user data by executing a host application. In a second action 3420, the host computer initiates a transmission carrying the user data to the UE. In an optional third action 3430, the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional fourth action 3440, the UE executes a client application associated with the host application executed by the host computer.

Figure 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 7 and Figure 8. For simplicity of the present disclosure, only drawing references to Figure 10 will be included in this section. In a first action 3510 of the method, the host computer provides user data. In an optional subaction (not shown) the host computer provides the user data by executing a host application. In a second action 3520, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third action 3530, the UE receives the user data carried in the transmission.

Figure 11 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 7 and Figure 8. For simplicity of the present disclosure, only drawing references to Figure 11 will be included in this section. In an optional first action 3610 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second action 3620, the UE provides user data. In an optional subaction 3621 of the second action 3620, the UE provides the user data by executing a client application. In a further optional subaction 3611 of the first action 3610, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in an optional third subaction 3630, transmission of the user data to the host computer. In a fourth action 3640 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Figure 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 7 and Figure 8. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section. In an optional first action 3710 of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In an optional second action 3720, the base station initiates transmission of the received user data to the host computer. In a third action 3730, the host computer receives the user data carried in the transmission initiated by the base station.