METHODS FOR CLOCK SYNCHRONIZATION BETWEEN NETWORK NODES USING ETHERNET AND TRANSMITTING FORWARD ERROR CORRECTION (FEC) MARKERS, AND NODE

Abstract

A disclosed method is performed by a primary device that is configured to code data using forward error correction (FEC) coding for transmission to a secondary device. The FEC coding adds a FEC marker to FEC coded data. The method by the primary device includes transmitting to the secondary device a marker planned transmission time indication which indicates when the primary device will transmit the FEC marker toward the secondary device. The method also includes transmitting the FEC marker of the FEC coded data at the time indicated by the marker planned transmission time indication.

Description

TECHNICAL FIELD

The present disclosure relates generally to timing synchronization between communicating circuits and units for high speed ethernet link communications.

BACKGROUND

The need for synchronization in Radio Access Networks (RANs) has grown as new radio technologies and network architectures emerge to boost efficiency and support demanding 5G use cases. Although the fundamental synchronization requirements have not become more stringent in 5G, the need for precise time synchronization has become much more critical with the introduction of millimeter wavelengths in radio spectrum.

Accurate and reliable synchronization has long been a fundamental prerequisite for the correct operation of telecommunications networks.

RANs are designed to optimize service performance and reliability, and synchronization is a vital enabler. The RANs use different sources, often in combination, to provide synchronization characteristics to match the network use case and services delivered. Finding the right balance between timing accuracy, availability and cost is key to making services successful.

New network architectures imply new approaches to addressing the various synchronization needs. This includes using Precision Time Protocol (PTP) and radio interface-based methods to synchronize distributed radio units in the evolved RAN architecture, where the upper and lower parts of the 5G New Radio (NR) RAN are separated in the different logical units: the centralized unit (CU), the distributed unit (DU) and the radio unit (RU).

Within the RU there is also a need to achieve high precision sync between different devices, e.g. between digital and analog front end components. One interface widely used today is JESD204, this standard handle both IQ (in-phase and quadrature component) transport between the digital and analog front end, as well as defining a method for inter device synchronization.

In an increasingly connected world, security and the quality of data exchange is a great concern and there is a need to ensure the synchronization of different communicating nodes. Hence, various schemes to enhance clock synchronization has been proposed. The introduction of 5G technology will impose more stringent requirements on communication networks. Higher speeds of communication with single or multi lane pose huge challenges to the accuracy and precision of synchronization. One of the major requirements is that the clock synchronization error is kept to a minimum. This error corresponds to the clock phase and frequency offset between two Ethernet communicating nodes.

SUMMARY

Some embodiments of the present disclosure are directed to a method by a primary device configured to code data using forward error correction (FEC) coding for transmission to a secondary device. The FEC coding adds a FEC marker to FEC coded data. The method includes transmitting to the secondary device a marker planned transmission time indication which indicates when the primary device will transmit the FEC marker toward the secondary device. The method also includes transmitting the FEC marker of the FEC coded data at the time indicated by the marker planned transmission time indication.

In some further embodiments, the method by the primary device also includes receiving the FEC marker from the secondary device. The method also includes determining a FEC marker reception time based on when the FEC marker was received from the secondary device. The method also includes calculating a round trip delay based on a difference between the time indicated by the marker planned transmission time indication and the FEC marker reception time.

Some other embodiments of the present disclosure are directed to a method by a secondary device. The method includes receiving from a primary device a marker planned transmission time indication which indicates when the primary device will transmit a FEC marker toward the secondary device. The method also includes receiving from the primary device the FEC marker as part of FEC coded data from the primary device. The method also includes adjusting an internal clock of the secondary device based on a difference between when the marker planned transmission time indicates the FEC marker was transmitted by the primary device and a time indicated by the internal clock when the FEC marker was received by the secondary device.

In some further embodiments, the method by the secondary device also includes transmitting the FEC marker received from the primary device toward the primary device for calculating a round trip delay.

Some other embodiments of the present disclosure are directed to a primary device configured to code data using FEC coding for transmission to a secondary device. The FEC coding adds a FEC marker to FEC coded data. The primary device includes at least one processor and at least one memory including computer program code comprising instructions. When the at least one processor executes the instructions, the at least one processor is configured to transmit to the secondary device a marker planned transmission time indication which indicates when the primary device will transmit the FEC marker toward the secondary device. The at least one processor is also configured to transmit the FEC marker of the FEC coded data at the time indicated by the marker planned transmission time indication.

Potential advantages of various embodiments include that the operations require less computational resources, such as less processing, reduced PPP stack, and reduced buffer size. By synchronizing the secondary clock time to the primary clock time, the secondary device can more accurately perform sampling of signals transmitted by the primary device.

These and further embodiments are described in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

FIG. 1A illustrates a block diagram of a primary device communicating with two secondary devices in accordance with some embodiments of inventive concepts;

FIG. 1B illustrates a block diagram of another system in which a centralized unit is communicating with distributing units which, in turn, are communicating with a pair of radio units, and which communications may be performed in accordance with some embodiments of inventive concepts;

FIG. 2 illustrates a primary device and a plurality of secondary devices which perform time synchronization relative to a CWM or AM inserted by FEC by the primary device, in accordance with some embodiments of inventive concepts;

FIG. 3 is a block diagram of sending and receiving operational blocks of a primary device and secondary device which can be configured to operate in accordance with some embodiments of inventive concepts;

FIG. 4 is a block diagram illustrating a wireless communication device or other user equipment (UE) according to some embodiments of inventive concepts;

FIG. 5 is a block diagram illustrating a radio access network RAN node (e.g., a base station eNB/gNB) according to some embodiments of inventive concepts;

FIG. 6 is a block diagram illustrating a core network CN node (e.g., an AMF node, an SMF node, etc.) according to some embodiments of inventive concepts;

FIGS. 9-11 illustrate flow charts of operations and associated methods by a first network node according to some embodiments of inventive concepts;

FIG. 7 is a block diagram of a communication system in accordance with some embodiments of inventive concepts;

FIG. 8 is a block diagram of a user equipment in accordance with some embodiments of inventive concepts;

FIG. 9 is a block diagram of a network node in accordance with some embodiments of inventive concepts;

FIG. 10 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments of inventive concepts;

FIG. 11 is a block diagram of a virtualization environment in accordance with some embodiments of inventive concepts; and

FIG. 12 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments of inventive concepts.

DETAILED DESCRIPTION

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, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

The Precision Time Protocol (PTP) uses a timestamping method to reduce the clock synchronization error between Ethernet communicating nodes. But as new networks are being introduced the constraints on network parameters are becoming more rigid. With the implementation of PTP, the clock synchronization error natively is in the range of 10ths of nanoseconds which can be acceptable for platform and transport level synchronization. For a board internal inter device synchronization PTP synchronization can reach numbers as low as in the sub ns level. But PTP approach comes with a large overhead in terms of multiple PTP stacks on the devices needed to be synchronized.

With the JESD204 SYSREF based approach it is possible to achieve a very high level of accuracy, but it comes at a large cost in added complexity on printed circuit boards (PCBs) for trace length matching, as well as special clocking circuitry on the board. The implementation also requires more attention and possibly added logic since the clock structure, phase locked loops (PLLs) and input/output circuits (IOs) must be designed to support handling of SYSREF together with the reference clock to satisfy higher accuracy requirements.

Some embodiments are directed to operationally relating the Ethernet FEC frame structure to the radio frame timing and synchronization. Various embodiments may remove the need for the sideband synchronization signal in JESD204 and for a PTP solution and thereby avoid the need for a processor with PTP stack.

Some embodiments of the present disclosure uses the Ethernet layer 1 structure to enhance the implementation and synchronization. The sender marks an event on layer 1 with a FEC marker and the receiver aligns according to the marking and sends its delay indication back. The marking is then used as an indication of a defined timepoint in the radio frame. The synchronization is transmitted with the Ethernet layer 1 frame, enabling Ethernet to carry precise timing information.

Various embodiments are directed to using the FEC marker to indicate defined time events. A FEC marker as used herein may be a Code Word Marker (CWM), Alignment Marker (AM), or another term used to indicate defined time events in Ethernet protocol. CWM insertion is defined for the IEEE 802.3 (2018) 25 gigabit ethernet (GbE) FEC specification. AM insertion is defined for the IEEE 802.3 multi lane 40 GbE and 100 GbE FEC specification.

In IEEE 802.3, the CWM/AM are used to indicate FEC boundaries and information. The CWM/AM are inserted repetitively by the FEC but don't have a predictable pattern.

Some embodiments of the present disclosure are directed to improving accuracy of synchronization of different circuits on, e.g., a same card, and may simplify synchronization functions between the circuits. In some types of communication systems, such as a multiple-input and multiple-output (MIMO) advanced antenna system (AAS), one central card with one time communicates with a number of circuits which need to know the time and perform synchronization.

Various operational approaches have been described for IQ and synchronization support over Ethernet with RS-FEC. Other operational approaches that can be similar thereto can be performed with other high-speed interfaces that have inline predictable layer 1 events, such as PCIe 6.

Potential advantages of various embodiments include the synchronization information being transmitted with existing mechanism in Ethernet layer 1 frames without the need for extra signals or special routing on the PCB. It reduces the complexity of timing slave compared to using PTP since no PTP software stack or timestamping of packet is needed. The embodiments are future proof since it will work also for coming IEEE Ethernet or other standards with RS-FEC. The logic needed to be implemented in order to support the embodiments may be distributed or described to chip vendors when components are sourced.

Further potential advantages of various embodiments include operations requiring less computational resources, such as less processing, reduced PPP stack, and buffer utilization. By synchronizing the secondary clock time to the primary clock time, the secondary device can more accurately perform sampling of signals transmitted by the primary device.

With the introduction of single and multi-lane 25 Gbit Ethernet for higher speed application in IEEE 802.3 (2018) and IEEE 802.3 CD (2018), additional mechanisms for the control of Bit Error Rate (BER) is required. One mechanism for BER control and multi-lane clock skew reduction and alignment are though Reed Solomon Forward Error Correction RS-FEC.

For 25 Gbit 802.3 clause 108 RS-FEC defines a Code Word Marker (CWM) and rapid CWM, which is special RS-FEC code words, built up by Alignment Markers. These two types of CWM markers are used for fast synchronization of RS-FEC encoder in the sender and decoder in the receiver. These CWM and rapid CWM are inserted in sender IEEE 802.3 clause 108.5.2.4 and removed in receiver IEEE 802.3 clause 108.5.3.4. The CWMs insertion and removal are functions of RS-FEC sublayer and part of Physical layer close to medium. The CWM is the first 257 bits of every 1024 RS-FEC codeword. Whereas in the case of rapid CWM, they are sent at the beginning of the first 40 codeword and thereafter sent after every 1024 RS-FEC codeword.

IEEE 802.3 Ethernet defines FEC subsystems for 10 Gbps and higher speeds, and for 10 and 25 Gbps the FEC is optional. For 50 and above the FEC is mandatory. FEC codewords form fixed codewords where user payload is amended with parity symbols. IEEE 802.3 clause 108 defines: 25 Gbps RSFEC (528, 514); 514 10 UI symbols, 14 10 UI symbols; a Code Word Marker, special 25 symbol, is inserted in every 1024:th codeword about 200 us.

FIG. 1A illustrates a block diagram of a primary device communicating with two secondary devices in accordance with some embodiments of inventive concepts. Referring to FIG. 1A, the primary device includes a pair of ethernet interface circuits 103 which respectively communicate with ethernet interface circuits 103 in DFE devices 101 and 102. As will be explained in further detail below, each device 100, 101, and 102 can be configured to code data using forward error correction (FEC) coding for transmission to another device, where the FEC coding adds a FEC marker to FEC coded data. Each ethernet interface circuit 103 can be configured to transmit a marker planned transmission time indication which indicates when the ethernet interface circuit 103 will transmit a FEC marker, and then transmit the FEC marker of the FEC coded data at the time indicated by the marker planned transmission time indication.

FIG. 1B illustrates a block diagram of another system in which a centralized unit 104 is communicating with distributing units 105a and 105b which, in turn, are communicating with a pair of radio units 106a and 106b or pair of radio units 106c and 106d, and which communications may be performed in accordance with some embodiments of inventive concepts. The radio units 106a-106b may correspond to remote radio heads which receive digital signals which are ready for analog conversion, amplification, and transmission through antennas. Each of the ethernet interface circuit 103 show in FIG. 1B can be configured to operate as described for FIG. 1A and below.

FIG. 2 illustrates a primary device 100 and a plurality of secondary devices 200 which perform time synchronization relative to a FEC marker 220 inserted by FEC by the primary device 100, in accordance with some embodiments. The secondary devices 200 may be relatively low-complexity devices such as digital-to-analog front end circuitry. The primary and secondary devices may reside in a same enclosure, on a same circuit board, or within a same multichip package, which can thereby benefit from more precise time synchronization capability. The FEC marker 220 is inserted by FEC by the primary device 100 into a packet 210.

In one embodiment, the primary device may correspond to digital modem circuitry and the secondary device may correspond to RF front-end circuitry which conditions a signal for transmission through the illustrated antenna. In a 5G Radio Access Network, the primary device may correspond to distributed unit and the secondary device may correspond to a radio unit. Alternatively in a 5G Radio Access Network, the primary device may correspond to centralized unit and the secondary device may correspond to a distributed unit.

As shown in FIG. 2, the secondary device contains a delay buffer 202. Size of the delay buffer 202 can be reduced by improving synchronization between clocks of the primary and secondary devices, so that the primary device transmits data for receipt by the secondary device closer to when the secondary device is ready to process and transit the data through the illustrated antenna and reduces the risk of the delay buffer overflowing.

FIG. 3 is a block diagram of sending and receiving operational blocks of a primary device and secondary device which can be configured to operate in accordance with some embodiments of inventive concepts.

Some embodiments of the present disclosure are directed to a method by a primary device 100 configured to code data using forward error correction, FEC, coding for transmission to a secondary device 200, the FEC coding adding a FEC marker 220 to FEC coded data 230. The method by the primary device 100 includes transmitting 300 to the secondary device 200 a marker planned transmission time indication which indicates when the primary device 100 will transmit the FEC marker 220 toward the secondary device 200. The method by the primary device 100 also includes transmitting 302 the FEC marker 220 of the FEC coded data 230 at the time indicated by the marker planned transmission time indication.

In some embodiments, the FEC marker 220 is a CWM, or AM added by the FEC coding to the FEC coded data 230.

The secondary device may align its FEC marker (CWM/AM) towards the primary device with a known position in relation with the primary device FEC marker (CWM/AM).

For example, a secondary device may align its sending of FEC marker (CWM/AM) with a time at which FEC marker (CWM/AM) was received plus time for jitter buffer.

This now creates a round trip delay that the primary device can use to adjust timing in time domain samples to be sent towards digital front end (DFE) circuitry.

Referring to FIG. 3, in some embodiments, the method by the primary device 100 also includes receiving 304 the FEC marker 220 from the secondary device 200. The method also includes determining 306 a FEC marker 220 reception time based on when the FEC marker 220 was received 304 from the secondary device. The method also includes calculating 308 a round trip delay based on a difference between the time indicated by the marker planned transmission time indication and the FEC marker 220 reception time.

In some further embodiments, the round trip delay is further calculated based on deducting a defined delay time which the secondary device 200 waits after receipt of the FEC marker 220 before transmitting 302 the FEC marker 220 back to the primary device 100.

The primary and secondary devices are configured to operate to know when the FEC marker is transmitted by the primary device relative to a reference clock. A marker planned transmission time indication is transmitted to the secondary device which informs the secondary device at what primary device clock time the primary device will transmit the FEC marker toward the secondary device.

The marker planned transmission time indication therefore may indicate a time relative to an internal clock of the primary device when the FEC marker will next be transmitted by the primary device toward the secondary device or may indicate a time relative to another reference clock when the FEC marker will next be transmitted.

In some embodiments, the marker planned transmission time indication indicates a time relative to a reference clock, which is internal to the primary device, when the primary device will transmit 302 the FEC marker 220 toward the secondary device.

In some embodiments, the marker planned transmission time indication indicates a time relative to a reference clock, which is external to the primary device 100, when the primary device will transmit 302 the FEC marker 220 toward the secondary device.

The marker planned transmission time indication can be transmitted to the secondary device through the same path as the FEC marker or may be transmitted through another path such as through a control interface.

In some embodiments, the marker planned transmission time indication is transmitted 300 to the secondary device through a communication pathway that is also used by the primary device 100 to transmit 302 the FEC marker 220 to the secondary device 200.

In some embodiments, the marker planned transmission time indication is transmitted 300 to the secondary device 200 through a communication pathway that is different than another communication pathway through which the FEC marker 220 is transmitted 302 by the primary device 100 toward the secondary device 200.

The primary device may embed the marker planned transmission time indication in a packet header or elsewhere in a packet transmitted to the secondary device.

In some embodiments, the marker planned transmission time indication is included in a first packet transmitted to the secondary device through the communication pathway. The marker planned transmission time indication indicates when the primary device 100 will transmit the FEC marker 220 in a second packet toward the secondary device 200, wherein the second packet is transmitted next after the first packet.

Accordingly, the primary device may send the marker planned transmission time indication to the secondary device through in-band signalling by, for example, embedding the marker planned transmission time indication in a message header. Alternatively or additionally, the primary device may send the marker planned transmission time indication to the secondary device through out-of-band signalling by, for example, sending the marker planned transmission time indication in a message transmitted through a different pathway than the FEC marker.

In one embodiment, the primary device sends a packet to the secondary device indicating a primary clock time, according to an internal clock of the primary device, when the primary device will send a next FEC marker toward the secondary device with data coded by a FEC. Accordingly, the primary device can determine what time it will next transmit a FEC marker to the secondary device and send an indication of that time as the marker planned transmission time indication to the secondary device. The secondary device may respond to receipt of the FEC marker from the primary device by synchronizing its internal clock based on the time of receipt and based on the primary clock time indicated by the packet.

In some embodiments, the secondary device sends the FEC marker back to the primary device in a next packet transmitted toward the primary device. The primary device computes round-trip delay based on when the primary device sent the FEC marker to the secondary device and when the primary device received the FEC marker from the secondary device. The primary device may wait a defined delay time after receipt of the FEC marker to transmit the next packet, where the defined delay time may approximate delay from the processing time and transmission time of the secondary device and where the primary device can be aware of and use the defined delay time when computing the round-trip delay.

In some embodiments, the marker planned transmission time indication may be sent in a packet with the FEC marker from the primary device to the secondary device and may be then returned from the secondary device to the primary device. It may be advantageous for the secondary device to return the same packet blocks containing the marker planned transmission time indication and the FEC marker to the primary device so that the data transfer time from the primary device to the secondary device can be assumed to be the same data transfer time from the secondary device back to the primary device, which simplifies computation of round-trip delay. These operations are quite different from PTP protocol because, for example, the clock synchronization does not require sending delay request or delay response messages, and do not require use of a software entity with associated processing resources to monitor a PTP stack. Accordingly, in some embodiments, the packet carrying the marker planned transmission time indication is moved into layer 1. Thus, when a secondary device detects the FEC marker, the secondary device can know how many bits until the next FEC marker. This predictability enables the secondary device to have less operational intelligence and minimize processing resources.

In one particular example, the primary device may transmitted in-phase (I) and quadrature (Q) data to the secondary device configured as front end circuitry which operates to transmit signals through one or more antennas and a radio interface. The primary device may include the marker planned transmission time indication as part of the packet carrying the I/Q data to the secondary device. For example, the primary device may perform beam forming functions and output I/Q data to a remote radio transceiver of the secondary device. In accordance with some embodiments, the primary device notifies the secondary device, via the marker planned transmission time indication, of what time the next FEC marker generated by forward error correction coding will be sent to the secondary device. The secondary device responds to receipt of the FEC marker by synchronizing its clock based on the time indicated by the notification from the primary device, and may send return data to the primary device upon a defined delay after receipt of the FEC marker. The primary device may responsively compute the round-trip delay in communications with the secondary device.

In some embodiments, the marker planned transmission time indication transmitted 300 to the secondary device 200 is included as part of a packet carrying in-phase and quadrature, I/Q, FEC coded data 230 to the secondary device 200.

Various embodiments of the present disclosure are directed to a method by a secondary device 200. The method by the secondary device 200 includes receiving 310 from a primary device 100 a marker planned transmission time indication which indicates when the primary device 100 will transmit a FEC marker 220 toward the secondary device 200. The method by the secondary device 200 also includes receiving 312 from the primary device 100 the FEC marker 220 as part of FEC coded data 230 from the primary device 100. The method by the secondary device 200 also includes adjusting 314 an internal clock of the secondary device based on a difference between when the marker planned transmission time indicates the FEC marker 220 was transmitted by the primary device 100 and a time indicated by the internal clock when the FEC marker 220 was received by the secondary device 200.

In some embodiments, the FEC marker 220 is a CWM, or AM added by the FEC coding to the FEC coded data 230.

In some embodiments, the method by the secondary device 200 also includes transmitting 316 the FEC marker 220 received 312 from the primary device 100 toward the primary device 100 for calculating a round trip delay.

In some embodiments, the method by the secondary device 200 also includes performing the transmitting 316 of the FEC marker 220 at a defined delay time after the time indicated by the internal clock when the FEC marker 220 was received by the secondary device 200.

In some embodiments, the marker planned transmission time indication is received 310 by the secondary device 200 through a communication pathway that is also used by the secondary device 200 to receive 312 the FEC marker 220 from the secondary device 200.

In some embodiments, the marker planned transmission time indication is included in a first packet received 310 by the secondary device 200 through the communication pathway. The marker planned transmission time indication indicates when the primary device 100 will transmit the FEC marker 220 in a second packet toward the secondary device 200, wherein the second packet is transmitted next after the first packet.

In some embodiments, the marker planned transmission time indication is received 310 by the secondary device through a communication pathway that is different than another communication pathway through which the FEC marker 220 is received 312 by the secondary device 200.

In some embodiments, the marker planned transmission time indication received 310 by the secondary device 200 as part of a packet carrying in-phase and quadrature, I/Q, FEC coded data 230.

In some embodiments, the method by the secondary device 200 also includes decoding the FEC coded data to obtain I/Q data, and transmitting the I/Q data through a radio air interface.

FIG. 4 is a block diagram illustrating elements of a communication device UE 400 (also referred to as a mobile terminal, a mobile communication terminal, a wireless device, a wireless communication device, a wireless terminal, mobile device, a device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. (Communication device 400 may be provided, for example, as discussed below with respect to wireless devices UE QQ112A, UE QQ112B, and wired or wireless devices UE QQ112C, UE QQ112D of FIG. 7, UE QQ200 of FIG. 8, virtualization hardware QQ504 and virtual machines QQ508A, QQ508B of FIG. 11, and UE QQ606 of FIG. 12, all of which should be considered interchangeable in the examples and embodiments described herein and be within the intended scope of this disclosure, unless otherwise noted.) As shown, communication device UE may include one or more antenna(s) (e.g., corresponding to antenna QQ222 of FIG. 8), and transceiver circuitry 401 (also referred to as a transceiver, e.g., corresponding to interface QQ212 of FIG. 8 having transmitter QQ218 and receiver QQ220) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (e.g., corresponding to network node QQ110A, QQ110B of FIG. 7, network node QQ300 of FIG. 9, and network node QQ604 of FIG. 12 also referred to as a RAN node) of a radio access network. Communication device UE may also include processing circuitry 403 (also referred to as a processor, e.g., corresponding to processing circuitry QQ202 of FIG. 8, and control system QQ512 of FIG. 11) coupled to the transceiver circuitry, and memory circuitry 405 (also referred to as memory, e.g., corresponding to memory QQ210 of FIG. 7) coupled to the processing circuitry. The memory circuitry 405 may include computer readable program code that when executed by the processing circuitry 403 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 403 may be defined to include memory so that separate memory circuitry is not required. Communication device UE may also include an interface (such as a user interface) coupled with processing circuitry 403, and/or communication device UE may be incorporated in a vehicle.

As discussed herein, operations of communication device UE 400 may be performed by processing circuitry 403 and/or transceiver circuitry 401. For example, processing circuitry 403 may control transceiver circuitry 401 to transmit communications through transceiver circuitry 401 over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry 401 from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry 405, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 403, processing circuitry 403 performs respective operations (e.g., operations discussed below with respect to Example Embodiments disclosed herein, e.g., FIGS. 1-3, relating to communication devices and communication network nodes). According to some embodiments, a communication device UE 400 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines. Various operations by the UE in accordance with embodiments of the present disclosure may be performed by discrete logic such as an application-specific integrated circuit (ASIC), which may include a field programmable gate array (FPGA), neural processing unit (NPU), etc., or may be performed by a central processing unit (CPU), a graphics processing unit (GPU), a line card, etc.

FIG. 5 is a block diagram illustrating elements of a radio access network RAN node 500 (also referred to as a network node, base station, eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configured to provide cellular communication according to embodiments of inventive concepts. (RAN node 500 may be provided, for example, as discussed below with respect to network node QQ110A, QQ110B of FIG. 7, network node QQ300 of FIG. 9, hardware QQ504 or virtual machine QQ508A, QQ508B of FIG. 11, and/or base station QQ604 of FIG. 12, all of which should be considered interchangeable in the examples and embodiments described herein and be within the intended scope of this disclosure, unless otherwise noted.) As shown, the RAN node may include transceiver circuitry 501 (also referred to as a transceiver, e.g., corresponding to portions of RF transceiver circuitry QQ312 and radio front end circuitry QQ318 of FIG. 9) including a transmitter which transmits through one or more antenna(s) 440 (e.g., MIMO configured plurality of antennas) and a receiver configured to provide uplink and downlink radio communications with mobile terminals. The RAN node may include network interface circuitry 507 (also referred to as a network interface, e.g., corresponding to portions of communication interface QQ306 of FIG. 9) configured to provide communications with other nodes (e.g., with other base stations) of the RAN and/or core network CN. The network node may also include processing circuitry 503 (also referred to as a processor, e.g., corresponding to processing circuitry QQ302 of FIG. 9) coupled to the transceiver circuitry, and memory circuitry 505 (also referred to as memory, e.g., corresponding to memory QQ304 of FIG. 9) coupled to the processing circuitry. The memory circuitry 405 may include computer readable program code that when executed by the processing circuitry 403 causes the processing circuitry to perform operations according to embodiments disclosed herein e.g., FIGS. 1-3. According to other embodiments, processing circuitry 503 may be defined to include memory so that a separate memory circuitry is not required. Various operations by the RAN node in accordance with embodiments of the present disclosure may be performed by discrete logic such as a FPGA.

As discussed herein, operations of the RAN node may be performed by processing circuitry 503, network interface 507, and/or transceiver 501. For example, processing circuitry 503 may control transceiver 501 to transmit downlink communications through transceiver 501 over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver 501 from one or more mobile terminals UEs over a radio interface. Similarly, processing circuitry 503 may control network interface 507 to transmit communications through network interface 507 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory 505, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 503, processing circuitry 503 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to RAN nodes, e.g., FIGS. 1-3). According to some embodiments, RAN node 500 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines.

According to some other embodiments, a network node may be implemented as a core network CN node without a transceiver. In such embodiments, transmission to a wireless communication device UE may be initiated by the network node so that transmission to the wireless communication device UE is provided through a network node including a transceiver (e.g., through a base station or RAN node). According to embodiments where the network node is a RAN node including a transceiver, initiating transmission may include transmitting through the transceiver.

FIG. 6 is a block diagram illustrating elements of a core network (CN) node 600 (e.g., an SMF (session management function) node, an AMF (access and mobility management function) node, etc.) of a communication network configured to provide cellular communication according to embodiments of inventive concepts. (CN node 600 may be provided, for example, as discussed below with respect to core network node QQ108 of FIG. 7, hardware QQ504 or virtual machine QQ508A, QQ508B of FIG. 11, all of which should be considered interchangeable in the examples and embodiments described herein and be within the intended scope of this disclosure, unless otherwise noted) As shown, the CN node may include network interface circuitry 607 configured to provide communications with other nodes of the core network and/or the radio access network RAN. The CN node may also include a processing circuitry 603 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 605 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 605 may include computer readable program code that when executed by the processing circuitry 603 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 603 may be defined to include memory so that a separate memory circuitry is not required.

As discussed herein, operations of the CN node 600 may be performed by processing circuitry 603 and/or network interface circuitry 607. For example, processing circuitry 603 may control network interface circuitry 607 to transmit communications through network interface circuitry 607 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 605, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 603, processing circuitry 603 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes, e.g., FIGS. 1-3). According to some embodiments, CN node 600 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines. Various operations by the CN node 600 in accordance with the present disclosure may be performed by discrete logic such as a FPGA.

In the description herein, while the communication device may be any of the communication device 400, wireless device QQ112A, QQ112B, wired or wireless devices UE QQ112C, UE QQ112D, UE QQ200, virtualization hardware QQ504, virtual machines QQ508A, QQ508B, or UE QQ606, the communication device shall be used to describe the functionality of the operations of the communication device. Operations of the communication device may be implemented according to one or more of the flowcharts of FIGS. 9-11 according to some embodiments of inventive concepts. For example, modules may be stored in memory 405 of FIG. 4, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 403, processing circuitry 403 performs respective operations of the flow chart. Alternatively or additionally, the operations may be implemented in a FPGA or other digital logic device.

In the description herein, while the network node may be any of the RAN node 500, network node QQ110A, QQ110B, QQ300, QQ606, hardware QQ504, or virtual machine QQ508A, QQ508B, the RAN node 500 shall be used to describe the functionality of the operations of the network node. Operations of the RAN node 500 may be implemented according to one or more of the flowcharts of FIGS. 9-11 according to some embodiments of inventive concepts. For example, modules may be stored in memory 505 of FIG. 5, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 503, processing circuitry 503 performs respective operations of the flow chart. Alternatively or additionally, the operations may be implemented in a FPGA or other digital logic device.

In the description herein, while the core network node may be any of the core network node 600, core network node QQ108, hardware QQ504, or virtual machine QQ508A, QQ508B, the core network node 600 shall be used to describe the functionality of the operations of the network node. Operations of the Core Network CN node 600 may be implemented according to one or more of the flowcharts of FIGS. 9-11 according to some embodiments of inventive concepts. For example, modules may be stored in memory 605 of FIG. 6, and these modules may provide instructions so that when the instructions of a module are executed by respective CN node processing circuitry 603, processing circuitry 603 performs respective operations of the flow chart. Alternatively or additionally, the operations may be implemented in a FPGA or other digital logic device.

FIG. 7 shows an example of a communication system QQ100 in accordance with some embodiments.

In the example, the communication system QQ100 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 network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. 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) to the core network QQ106 over one or more wireless connections.

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.

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.

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 De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

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.

As a whole, the communication system QQ100 of FIG. 7 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.

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 IoT services to yet further UEs.

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

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 in if one or more of the UEs are low energy IoT devices.

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.

FIG. 8 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 customer-premise equipment (CPE), 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-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

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

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 FIG. 8. 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.

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

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.

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.

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.

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 (eUICC), 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.

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.

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.

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

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.

A UE, when in the form of an Internet of Things (IoT) 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 IoT 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 smart watch, 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 IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE QQ200 shown in FIG. 8.

As yet another specific example, in an IoT 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-IoT 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.

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.

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

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

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

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.

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.

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.

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.

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 port(s)/terminal(s) 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.

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

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.

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.

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.

Embodiments of the network node QQ300 may include additional components beyond those shown in FIG. 9 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.

FIG. 10 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of FIG. 7, 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.

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 QQ2 and QQ3, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

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 (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., 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.

FIG. 11 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.

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.

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.

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.

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.

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.

FIG. 12 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. 7 and/or UE QQ200 of FIG. 8), network node (such as network node QQ110a of FIG. 7 and/or network node QQ300 of FIG. 9), and host (such as host QQ116 of FIG. 7 and/or host QQ400 of FIG. 10) discussed in the preceding paragraphs will now be described with reference to FIG. 12.

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.

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

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.

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.

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.

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.

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.

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.

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.

Further definitions and embodiments are discussed below.

In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

When an element is referred to as being “connected”, “coupled”, “responsive”, or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected”, “directly coupled”, “directly responsive”, or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, “coupled”, “connected”, “responsive”, or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term “and/or” (abbreviated “/”) includes any and all combinations of one or more of the associated listed items.

It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.

As used herein, the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”, “have”, “has”, “having”, or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation “e.g.”, which derives from the Latin phrase “exempli gratia,” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation.

Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as “circuitry,” “a module” or variants thereof.

It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Claims

1. A method by a primary device configured to code data using forward error correction, FEC, coding for transmission to a secondary device, the FEC coding adding a FEC marker to FEC coded data, the method comprising: transmitting to the secondary device a marker planned transmission time indication which indicates when the primary device will transmit the FEC marker toward the secondary device; andtransmitting the FEC marker of the FEC coded data at the time indicated by the marker planned transmission time indication.

2. The method by the primary device of claim 1, wherein the FEC marker is a Code Word Marker, CWM, or Alignment Marker, AM, added by the FEC coding to the FEC coded data.

3. The method by the primary device of claim 1, further comprising: receiving the FEC marker from the secondary device;determining a FEC marker reception time based on when the FEC marker was received from the secondary device; andcalculating a round trip delay based on a difference between the time indicated by the marker planned transmission time indication and the FEC marker reception time.

4. The method by the primary device of claim 3, wherein the round trip delay is further calculated based on deducting a defined delay time which the secondary device waits after receipt of the FEC marker before transmitting the FEC marker back to the primary device.

5. The method by the primary device of claim 1, wherein the marker planned transmission time indication indicates a time relative to a reference clock, which is internal to the primary device, when the primary device will transmit the FEC marker toward the secondary device.

6. The method by the primary device of claim 1, wherein the marker planned transmission time indication indicates a time relative to a reference clock, which is external to the primary device, when the primary device will transmit the FEC marker toward the secondary device.

7. The method by the primary device of claim 1, wherein the marker planned transmission time indication is transmitted to the secondary device through a communication pathway that is also used by the primary device to transmit the FEC marker to the secondary device.

8. The method by the primary device of claim 7, wherein: the marker planned transmission time indication is included in a first packet transmitted to the secondary device through the communication pathway; andthe marker planned transmission time indication indicates when the primary device will transmit the FEC marker in a second packet toward the secondary device, wherein the second packet is transmitted next after the first packet.

9. The method by the primary device of claim 1, wherein the marker planned transmission time indication is transmitted to the secondary device through a communication pathway that is different than another communication pathway through which the FEC marker is transmitted by the primary device toward the secondary device.

10. The method by the primary device of claim 1, wherein the marker planned transmission time indication transmitted to the secondary device is included as part of a packet carrying in-phase and quadrature, I/Q, FEC coded data to the secondary device.

11. A method by a secondary device, the method comprising: receiving from a primary device a marker planned transmission time indication which indicates when the primary device will transmit a forward error correction, FEC, marker toward the secondary device;receiving from the primary device the FEC marker as part of FEC coded data from the primary device; andadjusting an internal clock of the secondary device based on a difference between when the marker planned transmission time indicates the FEC marker was transmitted by the primary device and a time indicated by the internal clock when the FEC marker was received by the secondary device.

12. The method by the secondary device of claim 11, wherein the FEC marker is a Code Word Marker, CWM, or Alignment Marker, AM, received as part of the FEC coded data from the primary device.

13. The method by the secondary device of claim 11, further comprising: transmitting the FEC marker received from the primary device toward the primary device for calculating a round trip delay.

14. The method by the secondary device of claim 13, further comprising: performing the transmitting of the FEC marker at a defined delay time after the time indicated by the internal clock when the FEC marker was received by the secondary device.

15. The method by the secondary device of claim 11, wherein the marker planned transmission time indication is received by the secondary device through a communication pathway that is also used by the secondary device to receive the FEC marker from the secondary device.

16. The method by the secondary device of claim 15, wherein: the marker planned transmission time indication is included in a first packet received by the secondary device through the communication pathway; andthe marker planned transmission time indication indicates when the primary device will transmit the FEC marker in a second packet toward the secondary device, wherein the second packet is transmitted next after the first packet.

17. The method by the secondary device of claim 11, wherein the marker planned transmission time indication is received by the secondary device through a communication pathway that is different than another communication pathway through which the FEC marker is received by the secondary device.

18. The method by the secondary device of claim 11, wherein the marker planned transmission time indication received by the secondary device as part of a packet carrying in-phase and quadrature, I/Q, FEC coded data.

19. The method by the secondary device of claim 18, further comprising decoding the FEC coded data to obtain I/Q data, and transmitting the I/Q data through a radio air interface.

20. A primary device configured to code data using forward error correction, FEC, coding for transmission to a secondary device, the FEC coding adding a FEC marker to FEC coded data, the primary device comprises: a processor; andmemory including computer program code comprising instructions, such that when the processor executes the instructions, the processor is configured to,transmit to the secondary device a marker planned transmission time indication which indicates when the primary device will transmit the FEC marker toward the secondary device; andtransmit the FEC marker of the FEC coded data at the time indicated by the marker planned transmission time indication.