WO2020067977A1 - Inter-working between a time-sensitive network and a cellular communication network - Google Patents

Abstract

A device in a cellular communication network (10) receives a message (16) that is forwarded by a network node in the cellular network. The message (16) includes time information from a grandmaster clock (22) for a Time Sensitive Network (TSN) working domain external to the cellular network. The message (16) also includes a network-side timestamp which indicates a time at which the network node received the message (16) from the TSN working domain (18), according to a cellular network clock (11). The device determines a device-side timestamp that indicates a time at which the device received the message (16), according to the cellular network clock (11). The device calculates, based on the network-side timestamp and the device-side timestamp, a time delay taken to transmit the message (16) from the network node to the device. Based on the calculated time delay, the device adds time information to the message (16) and forwards the message (16) with the added time information.

Description

INTER-WORKING BETWEEN A TIME-SENSITIVE NETWORK AND A CELLULAR

COMMUNICATION NETWORK

TECHNICAL FIELD

The present application relates generally to a cellular communication network, and relates more particularly to inter-working between a cellular communication network and a time-sensitive network (TSN).

BACKGROUND

Time-Sensitive Networking (TSN) is a set of standards developed by the Institute of Electrical and Electronics Engineers (IEEE) for providing deterministic services through IEEE standard 802.3 Ethernet wired networks. The services provided by TSN include time synchronization, guaranteed low latency transmissions, and high reliability, to make legacy Ethernet, designed for best-effort communication, deterministic.

Challenges exist in exploiting a cellular communication network to connect devices wirelessly to a TSN network. A cellular communication network and a TSN network define different mechanisms to achieve communication determinism, making it challenging to arrange them in a way that enables end-to-end deterministic networking. One challenge in this regard is that a wireless device in a cellular communication network heretofore can only be synchronized to one clock; namely, the cellular network clock that provides a common time reference applicable for the cellular communication network. Known approaches for inter-working between a TSN network and a cellular communication network are therefore limited in that they require the cellular network clock to be synchronized to the working clock applicable to the TSN network.

SUMMARY

Some embodiments herein provide inter-working between a cellular communication network and a time-sensitive network (TSN), e.g., in a way that allows the cellular network’s clock to be asynchronous with the TSN network’s clock. Some embodiments in this regard allow a message indicating the TSN network’s clock to be effectively signaled over or through the cellular network, so that devices can be connected wirelessly to the TSN network. To do this, the offset between the cellular network’s clock and the TSN network’s clock is identified and used by the cellular network in order to recreate the TSN network’s clock after the message has traversed the cellular network. In some embodiments, this offset is identified and exploited upon ingress of the message to the cellular network, whereas in other embodiments this offset is identified and exploited upon egress of the message from the cellular network.

More particularly, embodiments herein include a method performed by a device in a cellular communication network. The method comprises receiving, at the device, a message that is forwarded by a network node in the cellular communication network. The message includes time information from a grandmaster clock which provides a time reference applicable to a Time Sensitive Network (TSN) working domain external to the cellular communication network. The message also includes a network-side timestamp which indicates a time at which the network node received the message from a TSN domain node in the TSN working domain, according to a cellular network clock which provides a time reference applicable to the cellular communication network. The method also includes determining a device-side timestamp that indicates a time at which the device received the message, according to the cellular network clock. The method then includes calculating, based on the network-side timestamp and the device-side timestamp, a time delay taken to transmit the message from the network node to the device via the cellular communication network. The method further comprises, based on the calculated time delay, adding time information to the message. The method then includes forwarding the message with the added time information.

In some embodiments, the added time information is a function of the calculated time delay and the time information from the grandmaster clock.

In some embodiments, the added time information is the time information from the grandmaster clock modified according to the calculated time delay.

In some embodiments, the message is a Precision Time Protocol (PTP) message received from a TSN domain node that provides the grandmaster clock. In this case, the time information from the grandmaster clock comprises PTP time information.

In some embodiments, the message is forwarded from the device towards a TSN device, a TSN bridge, or a TSN endpoint.

In some embodiments, the device is a user equipment.

Embodiments herein also includes a method performed by a network node in a cellular communication network. The method comprises receiving a message from a TSN domain node in a Time Sensitive Network (TSN) working domain external to the cellular

communication network. The message includes time information from a grandmaster clock which provides a time reference applicable to the TSN working domain. The method also comprises adding, to the message, a network-side timestamp which indicates a time at which the network node received the message from the TSN domain node, according to a cellular network clock which provides a time reference applicable to the cellular

communication network. The method further comprises forwarding the message, with the network-side timestamp added thereto, towards a device in the cellular communication network.

In some embodiments, the message is a Precision Time Protocol (PTP) message received from a TSN domain node that provides the grandmaster clock. In this case, the time information from the grandmaster clock comprises PTP time information.

In some embodiments, the device is a user equipment.

Embodiments herein also include corresponding apparatus, computer programs, and carriers. For example, embodiments herein include a device configured for use in a cellular communication network. The device is configured (e.g., via communication circuitry and processing circuitry) to receive a message that is forwarded by a network node in the cellular communication network. The message includes time information from a grandmaster clock which provides a time reference applicable to a Time Sensitive Network (TSN) working domain external to the cellular communication network. The message also includes a network-side timestamp which indicates a time at which the network node received the message from a TSN domain node in the TSN working domain, according to a cellular network clock which provides a time reference applicable to the cellular communication network. The device is further configured to determine a device-side timestamp that indicates a time at which the device received the message, according to the cellular network clock. The device is also configured to calculate, based on the network-side timestamp and the device-side timestamp, a time delay taken to transmit the message from the network node to the device via the cellular communication network. The device may be further configured to, based on the calculated time delay, add time information to the message. The device may then be configured to forward the message with the added time information.

Embodiments herein also include a network node configured for use in a cellular communication network. The network node is configured (e.g., via communication circuitry and processing circuitry) to receive a message from a TSN domain node in a Time Sensitive

Network (TSN) working domain external to the cellular communication network. The message includes time information from a grandmaster clock which provides a time reference applicable to the TSN working domain. The network node is also configured to add, to the message, a network-side timestamp which indicates a time at which the network node received the message from the TSN domain node, according to a cellular network clock which provides a time reference applicable to the cellular communication network. The network node may be further configured to forward the message, with the network-side timestamp added thereto, towards a device in the cellular communication network.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a block diagram of a cellular communication network configured to interwork with a TSN network according to some embodiments.

Figure 2 is a logic flow diagram of a method performed by a wireless device according to some embodiments.

Figure 3 is a logic flow diagram of a method performed by a network node according to some embodiments.

Figure 4 is a block diagram of a wireless device according to some embodiments.

Figure 5 is a block diagram of a network node according to some embodiments.

Figure 6 is a block diagram of a distributed TSN configuration model according to some embodiments.

Figure 7 is a block diagram of a centralized TSN configuration model according to some embodiments.

Figure 8 is a block diagram of a fully centralized TSN configuration model according to some embodiments.

Figure 9 is a call flow diagram of a procedure of TSN stream configuration using the fully centralized configuration model according to some embodiments.

Figure 10 is a block diagram of a 5G network architecture according to some embodiments.

Figure 11 is a block diagram of interworking of a 5G network and a TSN network according to some embodiments.

Figure 12 is a block diagram of multiple TSN gPTP time domains in a factory plant according to some embodiments.

Figure 13 is a timing diagram illustrating how a base station can synchronize a UE to a cellular reference time according to some embodiments.

Figure 14 is a block diagram of a scenario where a device is connected over a cellular link to a TSN domain according to some embodiments.

Figure 15 is a block diagram of a shop floor scenario where a TSN domain is connected to a virtual controller over a cellular link according to some embodiments.

Figure 16 is a block diagram of a scenario where two TSN networks are connected over a cellular link according to some embodiments. Figure 17 is a timing diagram of a procedure for establishing another time domain from a base station to a UE based on an offset, according to some embodiments.

Figure 18 is a timing diagram of a procedure for establishing another time domain from a UE to a base station using an offset, according to some embodiments.

Figure 19 is a timing diagram of a procedure for establishing another time domain from a base station to a UE based on an offset, according to some embodiments.

Figure 20 is a timing diagram of a procedure for establishing another time domain from a UE to a base station using an offset, according to some embodiments.

Figure 21 is a block diagram of receiver-side offset calculation using timestamps according to some embodiments.

Figure 22 is a block diagram of a wireless communication network according to some embodiments.

Figure 23 is a block diagram of a user equipment according to some embodiments.

Figure 24 is a block diagram of a virtualization environment according to some embodiments.

Figure 25 is a block diagram of a communication network with a host computer according to some embodiments.

Figure 26 is a block diagram of a host computer according to some embodiments.

Figure 27 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.

Figure 28 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.

Figure 29 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.

Figure 30 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.

Figure 31 depicts a method performed by a wireless device for reducing deviations between a common cellular reference timing signal, according to certain embodiments.

Figure 32 illustrates a schematic block diagram of a virtual apparatus in a wireless network.

Figure 33 depicts a method by a network node such as, for example, a base station for reducing deviations between a common cellular reference timing signal, according to certain embodiments.

Figure 34 illustrates a schematic block diagram of a virtual apparatus in a wireless network.

Figure 35 depicts a method performed by a wireless device for reducing deviations between a common cellular reference timing signal, according to certain embodiments.

Figure 36 illustrates a schematic block diagram of a virtual apparatus in a wireless network.

Figure 37 depicts a method by a network node such as, for example, a base station for reducing deviations between a common cellular reference timing signal, according to certain embodiments.

Figure 38 illustrates a schematic block diagram of a virtual apparatus in a wireless network.

DETAILED DESCRIPTION

Figure 1 shows a cellular communication network 10 according to some

embodiments. A cellular network clock 11 provides a time reference applicable to the cellular communication network 10. The cellular communication network 10 is nonetheless configured to inter-work with a time-sensitive networking (TSN) network according to some embodiments.

The cellular communication network 10 in this regard includes an ingress node 12. The ingress node 12 receives a message 14 (e.g., a Precision Time Protocol, PTP, message) from a TSN domain node 15 in a TSN working domain 18 external to the cellular communication network 10. The TSN domain node 15 may for instance be a TSN device, a TSN bridge, or a TSN endpoint. Regardless, the message 14 includes TSN time information 20, e.g., PTP time information. The TSN time information 20 comprises time information from a grandmaster clock 22 which provides a time reference applicable to the TSN working domain 18.

The ingress node 12 adds ingress time information 24 to the message 14 to form a message 16. In some embodiments, the ingress time information 24 is an offset calculated by the ingress node 12; namely, an offset between the grandmaster clock 22 and the cellular network clock 11 , e.g., as of receipt of the message 14 by the ingress node 12. In other embodiments, the ingress time information 24 is an ingress timestamp which indicates a time at which the ingress node 12 received the message 14, according to the cellular network clock 11. In any event, the ingress node 12 then forwards the message 16 towards an egress node 26 in the cellular communication network 10.

Based on the ingress time information 24 and the TSN time information 20 in the message 16, the egress node 26 forms a message 28. The message 28 includes TSN time information 30 that may or may not be updated with respect to the TSN time information 20 included in messages 14 and 16. The message 28 in some embodiments may also include egress time information 32. Regardless, the egress node 26 forwards this message 28 to a TSN domain node 34, e.g., a TSN device, a TSN bridge, or a TSN endpoint. This TSN domain node 34 may re-establish or re-create the grandmaster clock 22 using the message 28.

For example, in embodiments where the ingress time information 24 includes an offset between the grandmaster clock 22 and the cellular network clock 11 , the egress node 26 uses the offset and the TSN time information 20 to generate updated TSN time information. The updated TSN time information may thereby represent the grandmaster clock 22 as of the egress node’s reception of the message 16. The egress node 26 may then include this updated TSN time information as the TSN time information 30 in the message 28 to be forwarded to the TSN domain node 34.

In another example, in embodiments where the ingress time information 24 includes an ingress timestamp which indicates a time at which the ingress node 12 received the message 14, the egress node 26 may determine an egress timestamp which indicates a time at which the egress node 26 received the message 16. The egress node 26 may then calculate, based on the ingress timestamp and the egress timestamp, a time delay taken to transmit the message 16 from the ingress node 12 to the egress node 26 via the cellular communication network 10. Based on this time delay, the egress node 26 adds the egress time information 32 to the message 28 before forwarding that message 28 to the TSN domain node 34. The added egress time information 32 in some embodiments may for instance be a function of the calculated time delay and the TSN time information 20 from the grandmaster clock 22. In one such embodiment, the added egress time information 32 is the TSN time information 20 from the grandmaster clock 22, modified according to the calculated time delay, e.g., so as to reflect an update to the TSN time information 20 to account for the time delay.

Note that in some embodiments the ingress node 12 may be a network node in the cellular communication network 10, and the egress node 26 may be a device (e.g., a wireless device such as a user equipment). In this case, the ingress time information 24 may be referred to as network-side time information, e.g., a network-side offset or network-side timestamp. And the egress time information 32 may be referred to as device-side time information, e.g., a device-side timestamp. In view of the above modifications and variations, Figure 2 shows a method performed by a device in a cellular communication network 10. The method comprises receiving, at the device, a message 16 that is forwarded by a network node in the cellular communication network 10 (Block 200). The message 16 includes time information 20 from a grandmaster clock 27 which provides a time reference applicable to a Time Sensitive Network (TSN) working domain 18 external to the cellular communication network 10. The message 16 also includes a network-side timestamp which indicates a time at which the network node received the message from the TSN working domain18, according to a cellular network clock 11 which provides a time reference applicable to the cellular communication network 10. The method also includes determining a device-side timestamp that indicates a time at which the device received the message 16, according to the cellular network clock 11 (Block 210). The method then includes calculating, based on the network-side timestamp and the device-side timestamp, a time delay taken to transmit the message 16 from the network node to the device via the cellular communication network 10 (Block 220). The method further comprises, based on the calculated time delay, adding time information to the message (Block 230). The method then includes forwarding the message 28 with the added time information (Block 240).

In some embodiments, the added time information is a function of the calculated time delay and the time information 20 from the grandmaster clock 22.

In some embodiments, the added time information is the time information from the grandmaster clock 22 modified according to the calculated time delay.

In some embodiments, the message 16 is a Precision Time Protocol (PTP) message received from a TSN node 15 that provides the grandmaster clock 22. In this case, the time information 20 from the grandmaster clock 22 comprises PTP time information.

In some embodiments, the message 28 is forwarded towards a TSN device, a TSN bridge, or a TSN endpoint.

In some embodiments, the device is a user equipment.

Figure 3 shows a method performed by a network node in a cellular communication network 10. The method comprises receiving a message 14 from a TSN domain node 15 in a Time Sensitive Network (TSN) working domain 18 external to the cellular communication network 10 (Block 300). The message 14 includes time information 20 from a grandmaster clock 22 which provides a time reference applicable to the TSN working domain 18. The method also comprises adding, to the message 14, a network-side timestamp which indicates a time at which the network node received the message from the TSN working domain 18, according to a cellular network clock 11 which provides a time reference applicable to the cellular communication network 10 (Block 310). The method further comprises forwarding the message 16, with the network-side timestamp added thereto, towards a device in the cellular communication network 10 (Block 320).

In some embodiments, the message 14 is a Precision Time Protocol (PTP) message received from a TSN node 15 that provides the grandmaster clock 22. In this case, the time information 20 from the grandmaster clock 22 comprises PTP time information.

In some embodiments, the device is a user equipment.

The apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

Figure 4 for example illustrates a device 400 (e.g., a wireless device, such as a user equipment) as implemented in accordance with one or more embodiments. The device 400 may for instance be an example of egress node 26 in some embodiments. As shown, the device 400 includes processing circuitry 410 and communication circuitry 420. The communication circuitry 420 (e.g., radio circuitry) is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology.

Such communication may occur via one or more antennas that are either internal or external to the device 400. The processing circuitry 410 is configured to perform processing described above, e.g., in Figure 2, such as by executing instructions stored in memory 430.

The processing circuitry 410 in this regard may implement certain functional means, units, or modules.

Figure 5 illustrates a network node 500 as implemented in accordance with one or more embodiments. The network node 500 may be an example of ingress node 12 according to some embodiments. As shown, the network node 500 includes processing circuitry 510 and communication circuitry 520. The communication circuitry 520 is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. The processing circuitry 510 is configured to perform processing described above, e.g., in Figure 3, such as by executing instructions stored in memory 530. The processing circuitry 510 in this regard may implement certain functional means, units, or modules.

Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

Additional embodiments will now be described. At least some of these embodiments may be described as applicable in certain contexts and/or wireless network types for illustrative purposes, but the embodiments are similarly applicable in other contexts and/or wireless network types not explicitly described.

Factory automation in the‘Industry 4.0’ vision brought high requirements on the network infrastructure to support a vast number of new use cases. These use cases range from pure industrial plant measurement to high precision motion control in a robotized factory cell. Time sensitive flow of information plays a crucial role for such industrial use cases. To enable these services, IEEE 802.1 Time Sensitive Network (TSN) Task Group (TG) and fifth generation (5G) mobile communication technology are working side-by-side in the third generation partnership project (3GPP).

Time Sensitive Networking (TSN) is based on the IEEE 802.3 Ethernet standard. TSN provides deterministic services through IEEE802.3 networks, including time

synchronization, guaranteed low latency transmissions and high reliability to make legacy Ethernet, designed for best-effort communication, deterministic. The TSN features available today can be grouped into the following categories: (i) Time Synchronization (e.g. IEEE 802.1AS); (ii) Bounded Low Latency (e.g. IEEE 802.1Qav, IEEE 802.1Qbu, IEEE 802.1Qbv, IEEE 802.1Qch, IEEE 802.1Qcr); (iii) Ultra-Reliability (e.g. IEEE 802.1CB, IEEE 802.1Qca, IEEE 802.1Qci); and (iv) Network Configuration and Management (e.g. IEEE 802.1Qat,

IEEE 802.1Qcc, IEEE 802.1Qcp, IEEE 802.1CS).

The communication endpoints inside TSN are called Talker and Listener. A TSN network consist of multiple entities and features. All the switches (i.e., bridges) in between Talker and Listener need to support certain TSN features, like e.g. IEEE 802.1AS time synchronization. A TSN domain enables synchronized communication among nodes. The communication between Talker and Listener happens in streams. A stream is based on certain requirements in terms of data rate and latency given by an application implemented at Talker and Listener.

The TSN configuration and management features are used to setup the stream and guarantee the stream’s requirements across the network. The configuration and

management of a TSN network can be implemented in different manners, either in a centralized or in a distributed setup as defined in IEEE 802.1Qcc. The different configuration models are shown in Figures 6, 7, and 8. Figure 6 shows a distributed TSN configuration model. Figure 7 shows a centralized TSN configuration model. And Figure 8 shows a fully centralized TSN configuration model.

In the distributed model from Figure 6, the Talker and Listener might for example use the Stream Reservation Protocol (SRP) to setup and configure a TSN stream in every switch along the path from Talker to Listener in the TSN network. Nevertheless, some TSN features require a central management entity called Centralized Network Configuration (CNC) as shown in Figure 7. The CNC uses for example Netconf and YANG models to configure the switches in the network for each TSN stream. This also allows the use of time-gated queueing as defined in IEEE 802.1Qbv that enables data transport in a TSN network with deterministic latency. With time-gated queueing on each switch, queues are opened or closed following a precise schedule that allows high priority packets to pass through the switch with minimum latency and jitter if it arrives at an ingress port within the time the gate is scheduled to be open. In the fully centralized model, also a Centralized User Configuration (CUC) entity is added that is used as a point of contact for Listener and Talker. The CUC collects stream requirements and endpoint capabilities from the devices and communicates with the CNC directly. The details about TSN configuration is explained in IEEE 802.1Qcc.

Figure 9 illustrates a sequence chart of the procedure of TSN stream configuration using the fully centralized configuration model as shown in Figure 8, e.g., based on IEEE 802.1Qcc]

The steps to setup a TSN stream in the TSN network in the fully centralized configuration mode are as follows.

1. CUC may take input from e.g. an industrial application/engineering tool (e.g. a

Programmable Logic Controller, PLC) which specifies the devices which are supposed to exchange time-sensitive streams

2. CUC reads the capabilities of end stations and applications in the TSN network that includes information about the period/interval of user traffic and payload sizes

3. Based on this above information, the CUC creates (i) StreamID as an identifier for each TSN stream; (ii) StreamRank; and (iii) UsertoNetwork Requirements

4. CNC discovers the physical network topology using for example LLDP and any network management protocol

5. CNC uses a network management protocol to read TSN capabilities of bridges (e.g.

IEEE 802.1Q, 802.1AS, 802.1CB) in the TSN network

6. CUC initiates join requests to configure the streams in order to configure network

resources at the bridges for a TSN stream from one Talker to one Listener

7. Talker and Listener groups (group of elements specifying a TSN stream) are created by CUC specified in IEEE 802.1Qcc, 46.2.2)

8. CNC configures the TSN domain

9. CNC checks physical topology and checks if the time sensitive streams are supported by bridges in the network

10. CNC performs scheduling and path computation of streams

11. CNC configures TSN features in bridges along the path in the TSN network

12. CNC returns status (success or failure) of resulting resource assignment for streams to CUC 13. CUC further configures end stations (this protocol used for this information exchange is not in the scope of the IEEE 802.1Qcc specification) to start the user plane traffic exchange as defined initially between Listener and Talker

In the TSN network, the streamID is used to uniquely identify stream configurations.

It is used to assign TSN resources to a user’s stream. The streamID consists of the two tuples: (1) MacAddress associated with the TSN Talker; and (2) UniquelD to distinguish between multiple streams within end stations identified by MacAddress.

In the distributed configuration model as illustrated in Figure 6, there is no CUC and no CNC. The Talker is therefore responsible for initiation of a TSN stream. As no CNC is present, the bridges are configuring themselves which does not allow the use of, for example, time-gated queuing as defined in 802.1Qbv.

In the centralized model as depicted in Figure 7, the Talker is responsible for stream initialization but the bridges are configured by CNC.

To connect devices wirelessly to a TSN network, 5G seems to be a promising solution. The 5G standard as well addresses factory use cases through a lot of new features, especially on the Radio Access Network (RAN) to make it more reliable and reduce the transmit latency compared to 4G. The 5G network consists of three main components, which are user entity (UE), radio access network (RAN) instantiated as the gNB and nodes within the core network (5GCN). Figure 10 illustrates the 5G network architecture.

An ongoing research challenge is the inter-working of 5G and TSN as illustrated in Figure 11. Both technologies define their own methods for network management and configuration and different mechanisms to achieve communication determinism that must somehow be arranged to enable end-to-end deterministic networking for industrial networks. In the following, the device connected to the 5G network is referred to as 5G endpoint. A device connected to the TSN domain is referred to as a TSN endpoint.

Despite what is shown in Figure 11 , it is also possible that the UE is not connected to a single endpoint but instead to a TSN network comprising of at least one TSN bridge and at least one endpoint. The UE is then part of a TSN-5G gateway.

It should be noted that the User Plane Function (UPF) of Figure 11 , is assumed to support the Precision Time Protocol (PTP) and can therefore be synchronized to a

GrandMaster clock in the TSN network using PTP messages transported using UDP/IP (e.g. per IEEE 1588-2008). The method by which the UPF subsequently forwards clock information (derived from the GrandMaster clock) to a gNB is considered to be

implementation specific. The gNB can, if needed, send multiple instances of clock information derived from multiple sources (e.g. GPS based, GrandMaster based) to UEs using 5G network based methods. Further distribution of clock information from a UE to one or more endpoints is possible (e.g. a UE in possession of clock information can serve as a source clock for one or more endpoints). Specific use cases for which a UE will require or will distribute multiple instances of clock information to endpoints are for further study.

Figure 11 can support two basic scenarios for ethernet protocol data unit (PDU) processing. In Scenario 1 , Ethernet PDUs are relayed over the 5G Network. This scenario assumes the case where a single UE needs to support multiple endpoints, each having a distinct ethernet Medium Access Control (MAC) layer address (i.e. a UE supports multiple ethernet ports). The UPF that interfaces with the TSN switch is assumed to support the reception and transmission of ethernet PDUs that do not carry IP packets as higher layer payload. Upon receiving an ethernet PDU from the TSN switch, the UPF must have a method for associating the destination MAC address with a specific IP address and then relay the ethernet PDU to the appropriate node (e.g. PDN-GW) in the 5G network. The appropriate 5G network node uses the IP address to identify a specific UE and its corresponding Radio Network Temporary Identity (RNTI) so that the ethernet PDU can then be forwarded to the appropriate gNB for delivery using the identified RNTI. The gNB sends the ethernet PDU to the UE using a data radio bearer (DRB) with reliability and latency attributes appropriate for supporting ethernet PDU transmission. The UE recovers the ethernet PDU (e.g. from the Packet Data Convergence Protocol, PDCP, layer) and sends it to the endpoint associated with the destination MAC address (i.e. a UE may support one or more ethernet connected endpoints). In summary, the original ethernet PDU received by the UPF from the TSN switch is delivered transparently through the 5G network. For the uplink direction, the 5G network is expected to determine when a RNTI is associated with ethernet operation thereby allowing uplink payload (i.e. an ethernet PDU) associated with such a RNTI to be routed to a UPF. The UPF then simply sends the received ethernet PDU to a TSN switch.

In Scenario 2, Ethernet PDUs are terminated at the 5G Network. This scenario assumes the case where a single UE supports a single endpoint in which case there is no need for the UE to support any ethernet ports. The UPF that interfaces with the TSN switch is assumed to support the reception and transmission of ethernet PDUs that carry IP packets as higher layer payload. Upon receiving an ethernet PDU from the TSN switch the UPF extracts the IP packet from the ethernet PDU and sends it to the appropriate 5G network node for further routing. The 5G network uses the destination IP address to identify a specific UE and its corresponding RNTI so that the IP packet can be forwarded to the appropriate gNB for delivery using the identified RNTI. The gNB sends the IP packet to the UE using a data radio bearer (DRB) with reliability and latency attributes appropriate for supporting ethernet PDU transmission (i.e. even though the ethernet PDU terminates at the UPF the 5G network must support ethernet like QoS attributes when delivering the IP packets carried by ethernet PDUs). The UE recovers the IP packet (e.g. from the PDCP layer) and sends it to the IP layer application. In summary, the ethernet protocol layer is terminated when the ethernet PDU is received by the UPF from the TSN switch but its IP packet payload is delivered transparently through the 5G network. For the uplink direction the 5G network is expected to determine when a RNTI is associated with ethernet operation thereby allowing uplink payload (i.e. an IP packet) associated with such a RNTI to be routed to a UPF. The UPF must then have a method by which it can map source and destination IP addresses to source and destination MAC addresses (e.g. using ARP) so that it can construct an ethernet PDU containing those MAC addresses and the IP packet as payload for transmission to the TSN switch.

Many TSN features are based on precise time synchronization between all peers. As introduced above, this is achieved using e.g. IEEE 802.1 AS or IEEE 802.1AS-rev. Within the TSN network, it is therefore possible to achieve a synchronization with sub-microsecond error. To achieve this level of accuracy, hardware support is mandatory; e.g. for

timestamping of packets.

In a network, a grandmaster (GM) is a node that transmits timing information to all other nodes in a master-slave architecture. It might be elected out of several potential nodes, by certain criteria that makes the selected grandmaster superior.

In a TSN-extension of 802.1 AS, it has been defined that next to a main GM also a redundant backup GM can be configured. In case the first GM fails for any reason, devices in the TSN domain can be synched to the second GM. The redundant GM might work in a hot-standby configuration.

In TSN based on IEEE 802.1AS-rev (also called gPTP, generalized Precise Timing

Protocol) there are multiple time domains supported in a TSN network. One time domain could be a global time domain based on for example the PTP epoch, and other might be local time domains with an arbitrary epoch. There are two timescales which are supported by gPTP. In Timescale PTP, the epoch is the PTP epoch (details in IEEE 802.1 AS-rev section

8.2.2) and this timescale is continuous. The unit of measure of the time is the SI second as realized on the rotating period. In Timescale ARB (arbitrary), the epoch for this timescale is domain startup time and can be setup by administrative procedure (more details in IEEE 802.1AS-rev, section 3.2).

Devices in a TSN network can be synched to multiple time domains. A local arbitrary time domain is also referred to as a working clock. Working clocks are used in industrial networks for TSN functions.

One of the initial steps for setting up the TSN stream, as explained above, and shown in Figure 9, is establishing of a TSN domain by the CNC, by grouping endpoints (talkers and listeners) that are supposed to exchange time-sensitive streams. This list is provided by CUC to the CNC. The CNC further configures the bridges connecting these endpoints such that each TSN domain (talkers, listeners and bridges) has its own working clock. Technically this can be done according to IEEE 802.1AS-rev, by configuring external port role configuration, mechanism.

Multiple time domains in an industrial application scenario is now described. As introduced above, a TSN domain works with different clocks (global and working clocks). Furthermore, the clocks of each TSN domain are not necessarily synchronized and a factory network might comprise of several TSN domains. Therefore, across a factory network, there might be several independent TSN domains with arbitrary timescales, where different maybe overlapping subsets of devices need to be synchronized. As shown in Figure 12, each TSN domain can have their own working clock. That is, Figure 12 shows multiple TSN gPTP time domains in a factory plant.

To satisfy time synchronization requirements for TSN in manufacturing use cases, a cellular network is required to provide a time reference to which all machines (sensor or actuators) can be synchronized.

Currently in 3GPP standardization, efforts are seen to realize a time synchronization over the LTE radio access in Release 15.

3GPP document R2-1809053 shows the current contribution in discussion in 3GPP RAN 2, which proposes to add two Information Elements (IE) into SIB 16, i.e. time reference with 0.25ps granularity and uncertainty value, and the DL RRC message UETimeReference to inform GPS time to the UE with three lEs added in RRC message.

The main purpose of this procedure is to transfer GPS-based time reference information to UEs along with inaccuracy of that information. LTE defines several system information blocks (SIBs), related to timing information in SIB 16, which contains information related to GPS time and coordinated universal time (UTC).

SIBs are transmitted over Downlink shared channel (DL-SCH). The presence of a SIB in the subframe is indicated by the transmission of a corresponding Physical Downlink Control Channel (PDCCH) marked with a special system-information RNTI (SI-RNTI).

The IE SIB 16 contains information related to GPS time and UTC. The UE uses the parameter blocks to obtain the GPS and the local time.

The following shows the structure of a SIB 16 message, and Table 1 describes the fields of the SIB 16 message.

- ASN1 START

SystemlnformationBlockType16-r11 ::= SEQUENCE {

timelnfo-r11 SEQUENCE {

timelnfoUTC-r11 INTEGER (0..549755813887),

dayLightSavingTime-r11 BIT STRING (SIZE (2)) OPTIONAL, -

Need OR

leapSeconds-r11 INTEGER (-127..128) OPTIONAL, Need OR

localTimeOffset-r11 INTEGER (-63..64) OPTIONAL- Need

OR

} OPTIONAL,

Need OR

lateNonCriticalExtension OCTET STRING OPTIONAL,

GG qranularitvOneQuarterUs-r15 _ INTEGER (0..360287970189639671

OPTIONAL. - Need OR

uncert-quarter-us-r15 INTEGER (0..39991 OPTIONAL

SystemlnformationBlockTypel 6 field descriptions

dayLightSavingTime

t indicates if and how daylight saving time (DST) is applied to obtain the local time. The semantics is the same as the semantics of the Daylight Saving Time E in TS 24.301 [35] and TS 24.008 [49] The first/leftmost bit of the bit string contains the b2 of octet 3, i.e. the value part of the Daylight Saving Time IE, and the second bit of the bit string contains b1 of octet 3.

Another way of providing time synchronization is described in R2-1809053. The time reference information message in RRC signaling may also be used to transmit the GPS time to the UE.

Certain problems exist. For example, as per the state-of-art, a UE can only be synchronized to one clock that is supported by the base station (BS) (e.g. eNB) to which it is connected.

The main issue here is that the clock used to provide time reference over 3GPP radio can be different than the working clock (arbitrary GM clock) used to provide a time reference to a TSN domain. Currently there is no such mechanism to provide a TSN domain time clock that is not synchronized with a clock being used for time reference transmission from BS to UE.

Also, another issue is, if the UE is used as a TSN-Cellular gateway, it might further be possible that an independent clock grandmaster is present on the UE-side of the cellular network. The TSN application is then connected to the time-synchronization source instead of the BS for the TSN network to work. In this scenario also, currently there is no way the UE might transfer this timing information to other peers within the cellular network.

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, according to certain embodiments, a method is provided to allow the establishment of multiple time domains on both BS and UE sides based on a precise cellular network synchronization. The cellular network is thereby able to support, for example, two or more different time domains (e.g. a global clock and a working clock) towards a TSN application residing in a UE, i.e. an application which is based on the receiving time synchronization information from a BS. Furthermore, some embodiments provide a method whereby, in a cellular network, the UE can signal a time to the BS if a working clock GM is present on the U E-side and whereby the UE might be required to connect (i.e. provide precise cellular network synchronization information to) other TSN equipment located in the same TSN domain.

Certain embodiments may provide one or more of the following technical

advantages. For example, one technical advantage may be that certain embodiments allow end-to-end time synchronization with multiple time-domains based on a single precise time reference signaling over the air. The efforts to support the additional time-domains are reduced due to the methods proposed herein.

According to certain embodiments, a method is provided by which a UE can synchronize to one or multiple TSN domain working clocks based on a time synchronization solution. Further, the solution is extended to support a device (which is connected to a TSN domain over a cellular link) getting synchronized with a working clock of the TSN domain running behind the UE (here UE acts as a TSN gateway). Also, in case a relevant GM clock is deployed on the UE side, the UE might be able to signal this clock signal to the cellular network such as, for example, a base station (BS). The cellular network might forward this information to a TSN endpoint or network it is connected to.

Herein, it is assumed that there is a mechanism to synchronize UEs to a BS in a cellular network with sufficient precision. For a TSN end-to-end synchronization that is required by TSN features (for e.g. time aware traffic scheduler) this error might be on the order of 1 microsecond. Usually, the synchronization in the cellular network is based on a common global clock from an available trusted source, such as a Global Positioning System (GPS) signal.

It is assumed herein that the error for the 5G synchronization signal is sufficiently small to support the desired working clock accuracies for TSN communication. Figure 13 illustrates how a BS can synchronize a UE to a cellular reference time.

According to certain embodiments, the methods introduced are exemplified by three scenarios described below and shown in Figures 14-61. The Devices (Dev x) are assumed to be TSN endpoints, the GMs are TSN endpoints acting as a clock GM for the TSN network.

Specifically, Figure 14 illustrates a scenario where a Device (Dev 1) is assumed to be connected over a cellular link to a TSN domain. The Device (Dev 1) gets synchronized to a specific working clock (GM) of a TSN domain connected over a cellular link. This TSN domain can have its working clock (GM). The cellular network is providing time reference information to UE over dedicated RRC signaling or with enhanced SIB block (as explained above), based on e.g. GPS. According to certain embodiments, a method is proposed by which Dev 1 gets information on a TSN working clock which is based on the time reference that is already provided by the cellular network and based on e.g. GPS.

Figure 15 illustrates is a shop floor scenario assuming a TSN domain which is connected to a virtual controller (Dev 2) over a cellular link. In this scenario, Dev 2 gets synchronized to TSN domain’s working clock (GM) which is connected over a cellular link. Here, the challenge is how Dev 2 can be synchronized to the working clock (GM) of the TSN domain connected via UE. Some embodiments herein include a method that enables the UE to be able to communicate this local working clock of the GM to the BS and Dev 2 respectively.

Figure 16 illustrates the third scenario, where it is assumed two TSN networks are connected over a Cellular link. Here, two TSN domains get tightly coupled by sharing a common working clock (GM) over cellular link. The first part of the network is considered as the backbone of the cellular network and the other part is assumed as a shop floor. The GM clock can be either on the backbone or on the shop floor side of the network. It is a generic combination of scenario a) and b).

To address the challenges exemplified in the three scenarios above, some embodiments herein define two methods. So-called Method 1 is an example of embodiments where the ingress time information 22 from Figure 1 includes an offset between the grandmaster clock 22 and the cellular network clock 11 , the ingress node 12 is a BS, and the egress node 26 is a UE. More particularly, in Method 1 , the BS measures the timing offset and deviations between a common cellular reference timing signal (e.g. based on GPS) and various other timing signals (like e.g. working clocks of a TSN GM). This offset may be mapped to a TSN domain. The offset can be transmitted to a UE over dedicated Radio Resource Control (RRC) signaling or can be broadcasted using SIB block information elements (in case of broadcast over SIB, an offset value needs to be mapped with a TSN domain identification parameter). A UE will use this offset to re-establish the original time signal based on the common cellular reference time. The UE may then provide this time to a TSN application. Figure 17 illustrates the procedure of Method 1 according to some embodiments. As shown, next to the cellular reference time, another time domain is established from BS to UE based on offsets.

So-called Method 2 is an example of embodiments where the ingress time information 22 from Figure 1 includes an offset between the grandmaster clock 22 and the cellular network clock 11 , the ingress node 12 is a US, and the egress node 26 is a BS. In Method 2, a UE measures the timing offset and deviations between a common cellular reference timing signal (e.g. based on GPS) it is receiving from a cellular network and various other timing signals like different working clocks it is receiving from different TSN domains or from a single TSN domain that it is a part of. Here the UE acts as a gateway between a TSN network (including a TSN clock grandmaster) and the cellular network. The UE will transmit this offset to a BS e.g. over RRC signaling. The BS uses this offset to re establish the original time signal (i.e. corresponding to the TSN network the UE is a part of) based on the common cellular reference time. The BS then may provide this additional time signal to applications operating with same TSN domain. Figure 18 illustrates the procedure of Method 2, according to certain embodiments. As shown, next to the cellular reference time, another time domain is established from UE to BS based on offsets.

Both methods consider a periodic signaling of time-offsets to communicate to the other side of the cellular network about the timing offsets to be able to support multiple time domains.

Method 1 will now be described in more detail. Note that Method 1 here is a specific example of the embodiments from Figure 1 where the ingress node 12 is a BS, the ingress time information 24 is the offset between the cellular network clock 11 and the grandmaster clock 22, the egress node 26 is a UE, and the TSN time information 30 is the adjusted time reference per the offset.

The base assumption of the procedure of Method 1 is that, the epoch of the working clock and 5G time reference are the same or negotiated between UE and BS beforehand or the epoch of the additional time signals are arbitrary. Furthermore, the clocks used at UE and BS are of sufficient precision to support the time signals. Also, the UE is sufficiently synchronized to the BS to the common cellular reference time. Both UE and BS may be equipped with multiple clocks and relevant functionality to support different time signals in parallel.

Figure 19 illustrates the sequence flow for Method 1 , according to certain

embodiments. In Steps 1 and 2, a GM clock (from TSN network) provides a local time reference to the 5G core, which relays the GM clock to a BS in the cellular network. In Step

3, the BS in the cellular network calculates the offset by comparing the received local time reference from GM with the cellular reference time (e.g. a global GPS based cellular reference time). This cellular reference time is periodically transmitted to UEs (Step 4). In

Step 5, the calculated offset along with other necessary information (e.g. epoch, TSN domain number, time domain identifier) is delivered to one or multiple UE(s) over e.g. a dedicated RRC signal. UE(s) decode the offset and adjusts the local time reference per the indicated offset before providing it, In Step 6, to e.g., a TSN device, a bridge or a TSN endpoint.

According to certain embodiments, the embodiment of Method 1 allows the definition of multiple time domains for the cellular UEs. As such, a cellular reference time (e.g. based on GPS) is broadcasted to all UEs.

Additionally, TSN domain specific working times are established between BS and UEs by transmission of time offsets to individual UEs. The offsets will be calculated at the BS based on the common broadcasted cellular reference time.

According to a particular embodiment, the BS transmits (by broadcast or unicast) the offsets along with TSN domain identifiers to the UEs in the given domain. The UEs identify their required TSN domain (or are configured to use a specific TSN domain) and, thus, consider the time offset corresponding to that TSN domain to tune their clocks to the specific TSN domain working time/local reference time i.e. considering the cellular reference time plus the specific time offset.

Method 1 is explained assuming a 5G cellular network and one additional time signal from a TSN domain in the backbone. According to certain embodiments, the BS broadcasts the cellular reference time (10:00, 10:10, 10:20 ...) at defined points in time to all UEs; in addition, the BS will also transmit a TSN-domain specific working clock to UE1 by signaling the offset to the cellular reference time. Compared to the baseline cellular reference time synchronization method between BS and UE, the requirements for the transmission of the offsets is lowered as a calculation of the transmission and processing times is not necessary. Still, the offsets need to be communicated with sufficient periodicity and an indication of uncertainty/accuracy.

Method 2 will now be described in more detail. Note that Method 2 here is a specific example of the embodiments from Figure 1 where the ingress node 12 is a UE, the ingress time information 24 is the offset between the cellular network clock 11 and the grandmaster clock 22, the egress node 26 is a BS, and the TSN time information 30 is the adjusted time reference per the offset.

Figure 20 illustrates the sequence flow for Method 2, according to certain

embodiments. In Step 1 , a UE receives a working clock time reference directly from the TSN network it is connected to. The UE also receives a cellular time reference received from BS in Step 2. In Step 3, the UE compares the time reference from the TSN domain with the cellular time reference received from BS in order to calculate an individual offset. In Step 4, the UE further delivers the calculated offset to BS, e.g. by RRC signaling. The BS receives the offset message from UE and adjusts a time reference based on the received offset from UE. Subsequently, in step 5, the BS sends the modified time reference to the 5G Core, which in Step 6 sends the modified time reference to a TSN device on the cellular network as described in the scenario 2. This way, the TSN device on the network side is tuned to the TSN working time instead of the cellular reference time.

Note that Method 2 is based on the same assumptions as Method 1. That is, Method 2 is explained assuming a 5G cellular network and one additional time signal from a TSN domain on the UE side. In a particular embodiment, Method 2 might include the need to have multiple clocks at the BS or a core network function that uses the offsets to calculate working clocks for TSN networks based on the cellular reference time that supports multiple clocks in parallel.

Consider now an example of other embodiments where the ingress time information 24 includes an ingress timestamp which indicates a time at which the ingress node 12 received the message 14, the ingress node 12 is a network node (e.g., a BS), the egress node 26 is a device (e.g., a UE), and the message 28 includes an adjusted PTP timestamp which accounts for the time delay between the ingress timestamp and the egress timestamp.

For example, according to some embodiments, receiver-side offset calculation using timestamps may be performed. Specifically, the described solution may be used, for example, to transmit a PTP time information from an external grandmaster between UE and gNB in a time-aware manner. Therefore, a common reference time is used to evaluate the variable time t_d it took to transmit the packet from one layer at one of both nodes, to another layer at the other node.

The common reference time between UE and gNB is used to estimate t_d. As already explained above, PTP is often used in industrial context to synchronize systems.

This mechanism of course also works the other way around where the UE is synched to a PTP grandmaster. This transmission of ptp packets could be done transparently to the external PTP devices or by letting the UE and gNB jointly act like a boundary clock.

Important to mention is that the timestamping in this case is not required in a round-way fashion as done in PTP to calculate the roundtrip delay - it can happen at a higher layer and only the one way delay t_d is required as both UE and gNB already have a sufficient synchronization as a baseline This is illustrated in Figure 21 for a gNB to UE sync. As shown, the gNB receives a PTP message from the external grandmaster of a TSN domain. The PTP message includes a PTP timestamp of 16:32. The gNB adds to the PTP message the time at which the gNB received the message according to the common cellular reference time, i.e., 10:07 in this example. The gNB then transmits the PTP message, with the added timestamp, to the UE. The transmission of the PTP message from the gNB to the UE takes a time delay t_d. The UE receives the PTP message at 10:09 in this example according to the common cellular reference time (e.g., GNSS time). The UE calculates t_d = 0:02 using the timestamp of 10:07 included in the PTP message. The UE also calculates the PTP timestamp as being the PTP timestamp plus the calculated t_d, i.e., 16:32 + 0:02 = 16:34 in this example. The UE then forwards the calculated PTP timestamp to an application.

Figure 22 illustrates a wireless network, in accordance with some embodiments. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 22. For simplicity, the wireless network of Figure 22 only depicts network 2206, network nodes 2260 and 2260b, and WDs 2210, 2210b, and 2210c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 2260 and wireless device (WD) 2210 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS),

Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for

Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards. Network 2206 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 2260 and WD 2210 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.

In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, 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.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless 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 may then also 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). Yet further examples of network nodes include 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), core network nodes

(e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-

SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In Figure 22, network node 2260 includes processing circuitry 2270, device readable medium 2280, interface 2290, auxiliary equipment 2284, power source 2286, power circuitry 2287, and antenna 2262. Although network node 2260 illustrated in the example wireless network of Figure 22 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 2260 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 2280 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 2260 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 2260 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 NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 2260 may be configured to support multiple radio access technologies (RATs). In such embodiments, some

components may be duplicated (e.g., separate device readable medium 2280 for the different RATs) and some components may be reused (e.g., the same antenna 2262 may be shared by the RATs). Network node 2260 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2260, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 2260.

Processing circuitry 2270 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 2270 may include processing information obtained by processing circuitry 2270 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry 2270 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 2260

components, such as device readable medium 2280, network node 2260 functionality. For example, processing circuitry 2270 may execute instructions stored in device readable medium 2280 or in memory within processing circuitry 2270. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 2270 may include a system on a chip (SOC).

In some embodiments, processing circuitry 2270 may include one or more of radio frequency (RF) transceiver circuitry 2272 and baseband processing circuitry 2274. In some embodiments, radio frequency (RF) transceiver circuitry 2272 and baseband processing circuitry 2274 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 2272 and baseband processing circuitry 2274 may be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 2270 executing instructions stored on device readable medium 2280 or memory within processing circuitry 2270. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 2270 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 2270 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 2270 alone or to other components of network node 2260 but are enjoyed by network node 2260 as a whole, and/or by end users and the wireless network generally. Device readable medium 2280 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 2270. Device readable medium 2280 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 2270 and, utilized by network node 2260. Device readable medium 2280 may be used to store any calculations made by processing circuitry 2270 and/or any data received via interface 2290. In some embodiments, processing circuitry 2270 and device readable medium 2280 may be considered to be integrated.

Interface 2290 is used in the wired or wireless communication of signalling and/or data between network node 2260, network 2206, and/or WDs 2210. As illustrated, interface 2290 comprises port(s)/terminal(s) 2294 to send and receive data, for example to and from network 2206 over a wired connection. Interface 2290 also includes radio front end circuitry 2292 that may be coupled to, or in certain embodiments a part of, antenna 2262. Radio front end circuitry 2292 comprises filters 2298 and amplifiers 2296. Radio front end circuitry 2292 may be connected to antenna 2262 and processing circuitry 2270. Radio front end circuitry may be configured to condition signals communicated between antenna 2262 and processing circuitry 2270. Radio front end circuitry 2292 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 2292 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 2298 and/or amplifiers 2296. The radio signal may then be transmitted via antenna 2262. Similarly, when receiving data, antenna 2262 may collect radio signals which are then converted into digital data by radio front end circuitry 2292. The digital data may be passed to processing circuitry 2270. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 2260 may not include separate radio front end circuitry 2292, instead, processing circuitry 2270 may comprise radio front end circuitry and may be connected to antenna 2262 without separate radio front end circuitry 2292. Similarly, in some embodiments, all or some of RF transceiver circuitry 2272 may be considered a part of interface 2290. In still other embodiments, interface 2290 may include one or more ports or terminals 2294, radio front end circuitry 2292, and RF transceiver circuitry 2272, as part of a radio unit (not shown), and interface 2290 may communicate with baseband processing circuitry 2274, which is part of a digital unit (not shown).

Antenna 2262 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 2262 may be coupled to radio front end circuitry 2290 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 2262 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to

transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as Ml MO. In certain embodiments, antenna 2262 may be separate from network node 2260 and may be connectable to network node 2260 through an interface or port.

Antenna 2262, interface 2290, and/or processing circuitry 2270 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment.

Similarly, antenna 2262, interface 2290, and/or processing circuitry 2270 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry 2287 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 2260 with power for performing the functionality described herein. Power circuitry 2287 may receive power from power source 2286. Power source 2286 and/or power circuitry 2287 may be configured to provide power to the various components of network node 2260 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).

Power source 2286 may either be included in, or external to, power circuitry 2287 and/or network node 2260. For example, network node 2260 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 2287. As a further example, power source 2286 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 2287. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

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

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

As illustrated, wireless device 2210 includes antenna 2211 , interface 2214, processing circuitry 2220, device readable medium 2230, user interface equipment 2232, auxiliary equipment 2234, power source 2236 and power circuitry 2237. WD 2210 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 2210, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless

technologies may be integrated into the same or different chips or set of chips as other components within WD 2210.

Antenna 2211 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 2214. In certain alternative embodiments, antenna 2211 may be separate from WD 2210 and be connectable to WD 2210 through an interface or port. Antenna 2211 , interface 2214, and/or processing circuitry 2220 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 2211 may be considered an interface.

As illustrated, interface 2214 comprises radio front end circuitry 2212 and antenna

2211. Radio front end circuitry 2212 comprise one or more filters 2218 and amplifiers 2216.

Radio front end circuitry 2214 is connected to antenna 2211 and processing circuitry 2220 and is configured to condition signals communicated between antenna 2211 and processing circuitry 2220. Radio front end circuitry 2212 may be coupled to or a part of antenna 2211.

In some embodiments, WD 2210 may not include separate radio front end circuitry 2212; rather, processing circuitry 2220 may comprise radio front end circuitry and may be connected to antenna 2211. Similarly, in some embodiments, some or all of RF transceiver circuitry 2222 may be considered a part of interface 2214. Radio front end circuitry 2212 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 2212 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 2218 and/or amplifiers 2216. The radio signal may then be transmitted via antenna 2211. Similarly, when receiving data, antenna 2211 may collect radio signals which are then converted into digital data by radio front end circuitry 2212. The digital data may be passed to processing circuitry 2220. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry 2220 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 2210 components, such as device readable medium 2230, WD 2210 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 2220 may execute instructions stored in device readable medium 2230 or in memory within processing circuitry 2220 to provide the functionality disclosed herein.

As illustrated, processing circuitry 2220 includes one or more of RF transceiver circuitry 2222, baseband processing circuitry 2224, and application processing circuitry

2226. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry

2220 of WD 2210 may comprise a SOC. In some embodiments, RF transceiver circuitry

2222, baseband processing circuitry 2224, and application processing circuitry 2226 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 2224 and application processing circuitry 2226 may be combined into one chip or set of chips, and RF transceiver circuitry 2222 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 2222 and baseband processing circuitry 2224 may be on the same chip or set of chips, and application processing circuitry 2226 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 2222, baseband processing circuitry 2224, and application processing circuitry 2226 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 2222 may be a part of interface 2214. RF transceiver circuitry 2222 may condition RF signals for processing circuitry 2220.

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

Processing circuitry 2220 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 2220, may include processing information obtained by processing circuitry 2220 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 2210, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 2230 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 2220. Device readable medium 2230 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 2220. In some embodiments, processing circuitry 2220 and device readable medium 2230 may be considered to be integrated. User interface equipment 2232 may provide components that allow for a human user to interact with WD 2210. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 2232 may be operable to produce output to the user and to allow the user to provide input to WD 2210. The type of interaction may vary depending on the type of user interface equipment 2232 installed in WD 2210. For example, if WD 2210 is a smart phone, the interaction may be via a touch screen; if WD 2210 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 2232 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 2232 is configured to allow input of information into WD 2210 and is connected to processing circuitry 2220 to allow processing circuitry 2220 to process the input information. User interface equipment 2232 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 2232 is also configured to allow output of information from WD 2210, and to allow

processing circuitry 2220 to output information from WD 2210. User interface equipment 2232 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 2232, WD 2210 may

communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.

Auxiliary equipment 2234 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 2234 may vary depending on the embodiment and/or scenario.

Power source 2236 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 2210 may further comprise power circuitry 2237 for delivering power from power source 2236 to the various parts of WD 2210 which need power from power source 2236 to carry out any functionality described or indicated herein. Power circuitry 2237 may in certain embodiments comprise power management circuitry. Power circuitry 2237 may additionally or alternatively be operable to receive power from an external power source; in which case WD 2210 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 2237 may also in certain embodiments be operable to deliver power from an external power source to power source 2236. This may be, for example, for the charging of power source 2236. Power circuitry 2237 may perform any formatting, converting, or other modification to the power from power source 2236 to make the power suitable for the respective components of WD 2210 to which power is supplied.

Figure 23 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or 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). UE 23200 may be any UE identified by the 3^rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type

communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 2300, as illustrated in Figure 23, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure 23 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In Figure 23, UE 2300 includes processing circuitry 2301 that is operatively coupled to input/output interface 2305, radio frequency (RF) interface 2309, network connection interface 2311 , memory 2315 including random access memory (RAM) 2317, read-only memory (ROM) 2319, and storage medium 2321 or the like, communication subsystem 2331 , power source 2333, and/or any other component, or any combination thereof.

Storage medium 2321 includes operating system 2323, application program 2325, and data 2327. In other embodiments, storage medium 2321 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 23, or only a subset of the components. 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. In Figure 23, processing circuitry 2301 may be configured to process computer instructions and data. Processing circuitry 2301 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine- readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 2301 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 2305 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 2300 may be configured to use an output device via input/output interface 2305. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 2300. The output device may be 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. UE 2300 may be configured to use an input device via input/output interface 2305 to allow a user to capture information into UE 2300. The input device may 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, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In Figure 23, RF interface 2309 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 2311 may be configured to provide a communication interface to network 2343a. Network 2343a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.

For example, network 2343a may comprise a Wi-Fi network. Network connection interface 2311 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 2311 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 2317 may be configured to interface via bus 2302 to processing circuitry 2301 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 2319 may be configured to provide computer instructions or data to processing circuitry 2301. For example, ROM 2319 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.

Storage medium 2321 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 2321 may be configured to include operating system 2323, application program 2325 such as a web browser application, a widget or gadget engine or another application, and data file 2327. Storage medium 2321 may store, for use by UE 2300, any of a variety of various operating systems or combinations of operating systems.

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

In Figure 23, processing circuitry 2301 may be configured to communicate with network 2343b using communication subsystem 2331. Network 2343a and network 2343b may be the same network or networks or different network or networks. Communication subsystem 2331 may be configured to include one or more transceivers used to

communicate with network 2343b. For example, communication subsystem 2331 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.23, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 2333 and/or receiver 2335 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 2333 and receiver 2335 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 2331 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 2331 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 2343b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 2343b may be a cellular network, a W-Fi network, and/or a near-field network. Power source 2313 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 2300.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 2300 or partitioned across multiple components of UE 2300.

Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem

2331 may be configured to include any of the components described herein. Further, processing circuitry 2301 may be configured to communicate with any of such components over bus 2302. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 2301 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 2301 and communication subsystem 2331. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

Figure 24 is a schematic block diagram illustrating a virtualization environment 2400 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 a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) 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 (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 2400 hosted by one or more of hardware nodes 2430. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

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

Virtualization environment 2400, comprises general-purpose or special-purpose network hardware devices 2430 comprising a set of one or more processors or processing circuitry 2460, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 2490-1 which may be non-persistent memory for temporarily storing instructions 2495 or software executed by processing circuitry 2460.

Each hardware device may comprise one or more network interface controllers (NICs) 2470, also known as network interface cards, which include physical network interface 2480. Each hardware device may also include non-transitory, persistent, machine-readable storage media 2490-2 having stored therein software 2495 and/or instructions executable by processing circuitry 2460. Software 2495 may include any type of software including software for instantiating one or more virtualization layers 2450 (also referred to as hypervisors), software to execute virtual machines 2440 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

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

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

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

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, virtual machine 2440 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 2440, and that part of hardware 2430 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 2440, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 2440 on top of hardware networking infrastructure 2430 and corresponds to application 2420 in Figure 24.

In some embodiments, one or more radio units 24200 that each include one or more transmitters 24220 and one or more receivers 24210 may be coupled to one or more antennas 24225. Radio units 24200 may communicate directly with hardware nodes 2430 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 affected with the use of control system 24230 which may alternatively be used for communication between the hardware nodes 2430 and radio units 24200.

Figure 25 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

With reference to FIGURE 25, in accordance with an embodiment, a communication system includes telecommunication network 2510, such as a 3GPP-type cellular network, which comprises access network 2511 , such as a radio access network, and core network 2514. Access network 2511 comprises a plurality of base stations 2512a, 2512b, 2512c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 2513a, 2513b, 2513c. Each base station 2512a, 2512b,

2512c is connectable to core network 2514 over a wired or wireless connection 2515. A first UE 2591 located in coverage area 2513c is configured to wirelessly connect to, or be paged by, the corresponding base station 2512c. A second UE 2592 in coverage area 2513a is wirelessly connectable to the corresponding base station 2512a. While a plurality of UEs 2591 , 2592 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 2512. Telecommunication network 2510 is itself connected to host computer 2530, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. Host computer 2530 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider. Connections 2521 and 2522 between telecommunication network 2510 and host computer 2530 may extend directly from core network 2514 to host computer 2530 or may go via an optional

intermediate network 2520. Intermediate network 2520 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 2520, if any, may be a backbone network or the Internet; in particular, intermediate network 2520 may comprise two or more sub-networks (not shown).

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

Figure 26 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 26. In communication system 2600, host computer 2610 comprises hardware 2615 including communication interface 2616 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 2600. Host computer 2610 further comprises processing circuitry

2618, which may have storage and/or processing capabilities. In particular, processing circuitry 2618 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 2610 further comprises software 2611 , which is stored in or accessible by host computer 2610 and executable by processing circuitry 2618. Software 2611 includes host application 2612. Host application 2612 may be operable to provide a service to a remote user, such as UE 2630 connecting via OTT connection 2650 terminating at UE 2630 and host computer 2610. In providing the service to the remote user, host application 2612 may provide user data which is transmitted using OTT connection 2650.

Communication system 2600 further includes base station 2620 provided in a telecommunication system and comprising hardware 2625 enabling it to communicate with host computer 2610 and with UE 2630. Hardware 2625 may include communication interface 2626 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 2600, as well as radio interface 2627 for setting up and maintaining at least wireless connection 2670 with UE 2630 located in a coverage area (not shown in Figure 26) served by base station 2620.

Communication interface 2626 may be configured to facilitate connection 2660 to host computer 2610. Connection 2660 may be direct or it may pass through a core network (not shown in Figure 26) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 2625 of base station 2620 further includes processing circuitry 2628, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 2620 further has software 2621 stored internally or accessible via an external connection.

Communication system 2600 further includes UE 2630 already referred to. Its hardware 2635 may include radio interface 2637 configured to set up and maintain wireless connection 2670 with a base station serving a coverage area in which UE 2630 is currently located. Hardware 2635 of UE 2630 further includes processing circuitry 2638, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 2630 further comprises software 2631 , which is stored in or accessible by

UE 2630 and executable by processing circuitry 2638. Software 2631 includes client application 2632. Client application 2632 may be operable to provide a service to a human or non-human user via UE 2630, with the support of host computer 2610. In host computer 2610, an executing host application 2612 may communicate with the executing client application 2632 via OTT connection 2650 terminating at UE 2630 and host computer 2610. In providing the service to the user, client application 2632 may receive request data from host application 2612 and provide user data in response to the request data. OTT connection 2650 may transfer both the request data and the user data. Client application 2632 may interact with the user to generate the user data that it provides.

It is noted that host computer 2610, base station 2620 and UE 2630 illustrated in Figure 26 may be similar or identical to host computer 2530, one of base stations 2512a, 2512b, 2512c and one of UEs 2591 , 2592 of Figure 25, respectively. This is to say, the inner workings of these entities may be as shown in Figure 26 and independently, the surrounding network topology may be that of Figure 25.

In Figure 26, OTT connection 2650 has been drawn abstractly to illustrate the communication between host computer 2610 and UE 2630 via base station 2620, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 2630 or from the service provider operating host computer 2610, or both.

While OTT connection 2650 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing

consideration or reconfiguration of the network).

Wireless connection 2670 between UE 2630 and base station 2620 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 2630 using OTT connection 2650, in which wireless connection 2670 forms the last segment.

More precisely, the teachings of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and/or extended battery lifetime.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 2650 between host computer 2610 and UE 2630, in response to variations in the measurement results.

The measurement procedure and/or the network functionality for reconfiguring OTT connection 2650 may be implemented in software 2611 and hardware 2615 of host computer 2610 or in software 2631 and hardware 2635 of UE 2630, or both. In

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

Figure 27 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 20 and 21. For simplicity of the present disclosure, only drawing references to Figure 27 will be included in this section. In step 2710, the host computer provides user data. In substep 2711 (which may be optional) of step 2710, the host computer provides the user data by executing a host application. In step 2720, the host computer initiates a transmission carrying the user data to the UE. In step 2730 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2740 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 28 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 20 and 21. For simplicity of the present disclosure, only drawing references to Figure 28 will be included in this section. In step 2810 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 2820, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2830 (which may be optional), the UE receives the user data carried in the transmission.

Figure 29 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 20 and 21. For simplicity of the present disclosure, only drawing references to Figure 29 will be included in this section. In step 2910 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2920, the UE provides user data. In substep 2921 (which may be optional) of step 2920, the UE provides the user data by executing a client application. In substep 2911 (which may be optional) of step 2910, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 2930 (which may be optional), transmission of the user data to the host computer. In step 2940 of the method, the host computer receives the user data transmitted from the UE, in

accordance with the teachings of the embodiments described throughout this disclosure.

Figure 30 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 20 and 21. For simplicity of the present disclosure, only drawing references to Figure 30 will be included in this section. In step 3010 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 3020 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 3030 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

Figure 31 depicts a method 3100 performed by a wireless device for reducing deviations between a common cellular reference timing signal, according to certain embodiments. The method begins at step 3102 when the wireless device receives a first timing signal from a cellular network. At step 3104, the wireless device receives a second timing signal from at least one TSN to which the wireless device is connected. The first timing signal is compared to the second timing signal to determine an offset, at step 3106.

At step 3108, the wireless device transmits the offset to a network node. Figure 32 illustrates a schematic block diagram of a virtual apparatus 3200 in a wireless network (for example, the wireless network shown in Figure 22). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 2210 or network node 2260 shown in Figure 22). Apparatus 3200 is operable to carry out the example method described with reference to Figure 31 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 31 is not necessarily carried out solely by apparatus 3200. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 3200 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random- access memory, cache memory, flash memory devices, optical storage devices, etc.

Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause first receiving module 3210, second receiving module 3220, comparing module 3230, transmitting module 3240, and any other suitable units of apparatus 3200 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, first receiving module 3210 may perform certain of the receiving functions of the apparatus 3200. For example, first receiving module 3210 may receive a first timing signal from a cellular network.

According to certain embodiments, second receiving module 3220 may perform certain other of the receiving functions of the apparatus 3200. For example, second receiving module 3220 may receive a second timing signal from at least on TSN to which the wireless device is connected.

According to certain embodiments, comparing module 3230 may perform certain of the comparing functions of the apparatus 3200. For example, comparing module 3230 may compare the first timing signal to the second timing signal to determine an offset.

According to certain embodiments, transmitting module 3240 may perform certain of the transmitting functions of the apparatus 3200. For example, transmitting module 3240 may transmit the offset to a network node. The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Figure 33 depicts a method by a network node such as, for example, a base station for reducing deviations between a common cellular reference timing signal, according to certain embodiments. The method begins at step 3302 when the network node transmits, to a wireless device, a first timing signal for a cellular network. At 3304, the network node receives, from the wireless device, an offset measured by the wireless device. The offset is based on a difference between the first timing signal for the cellular network and a second timing signal associated with at least on time sensitive network (TSN) to which the wireless device is connected. Based on the offset received from the wireless device, a third timing signal for the cellular network is determined at step 3306. The third timing signal is an adjusted time signal of the first timing signal. At step 3308, the network node transmits, to the wireless device, the third timing signal network node.

Figure 34 illustrates a schematic block diagram of a virtual apparatus 3400 in a wireless network (for example, the wireless network shown in Figure 22). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 2210 or network node 2260 shown in Figure 22). Apparatus 3400 is operable to carry out the example method described with reference to Figure 33 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 33 is not necessarily carried out solely by apparatus 3400. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 3400 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random- access memory, cache memory, flash memory devices, optical storage devices, etc.

Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause first transmitting module 3410, receiving module 3420, determining module 3430, and second transmitting module 3440, and any other suitable units of apparatus 3400 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, first transmitting module 3410 may perform certain of the transmitting functions of the apparatus 3400. For example, first transmitting module 3410 may transmit , to a wireless device, a first timing signal for a cellular network.

According to certain embodiments, receiving module 3420 may perform certain of the receiving functions of the apparatus ZZ 2900. For example, receiving module 3420 may receive, from the wireless device, an offset measured by the wireless device. The offset is based on a difference between the first timing signal for the cellular network and a second timing signal associated with at least on time sensitive network (TSN) to which the wireless device is connected.

According to certain embodiments, determining module 3430 may perform certain of the determining functions of the apparatus 3400. For example, determining module 3430 may determine a third timing signal for the cellular network based on the offset received from the wireless device.

According to certain embodiments, second transmitting module 3440 may perform certain other of the transmitting functions of the apparatus 3400. For example, second transmitting module 3440 may transmit, to the wireless device, the third timing signal network node.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures,

computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Figure 35 depicts a method 3500 performed by a wireless device for reducing deviations between a common cellular reference timing signal, according to certain embodiments. The method begins at step 3502 when the wireless device receives a first timing signal from a cellular network. At step 3504, the wireless device receives a second timing signal from at least one time sensitive network (TSN). At step 3506, the wireless device receives, from a network node associated with the cellular network, an offset measured by the network node. The offset is based on a difference between the first timing signal for the cellular network and the second timing signal from the at least one TSN. The offset is used to reduce a deviation between the first time signal and the second time signal, at step 3508.

Figure 36 illustrates a schematic block diagram of a virtual apparatus 3670 in a wireless network (for example, the wireless network shown in Figure 22). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 2210 or network node 2260 shown in Figure 22). Apparatus 3600 is operable to carry out the example method described with reference to Figure 35 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 35 is not necessarily carried out solely by apparatus 3600. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 3600 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random- access memory, cache memory, flash memory devices, optical storage devices, etc.

Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause first receiving module 3610, second receiving module 3620, third receiving module 3630, using module 3640, and any other suitable units of apparatus 3600 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, first receiving module 3610 may perform certain of the receiving functions of the apparatus 3600. For example, first receiving module 3610 may receive a first timing signal from a cellular network.

According to certain embodiments, second receiving module 3620 may perform certain other of the receiving functions of the apparatus 3600. For example, second receiving module 3620 may receive a second timing signal from at least on time sensitive network (TSN).

According to certain embodiments, third receiving module 3630 may perform certain other of the receiving functions of the apparatus 3600. For example, third receiving module

3630 may receive, from a network node associated with the cellular network, an offset measured by the network node. The offset is based on a difference between the first timing signal for the cellular network and the second timing signal from the TSN.

According to certain embodiments, using module 3640 may perform certain of the using functions of the apparatus 3600. For example, using module 3640 may use the offset to reduce a deviation between the first time signal and the second time signal.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Figure 37 depicts a method by a network node such as, for example, a base station for reducing deviations between a common cellular reference timing signal, according to certain embodiments. The method begins at step 3702 when the network node receives a second timing signal from at least on time sensitive network (TSN). At step 3704, the network node performs a comparison the second timing signal to a first time signal for a cellular network. Based on the comparison, an offset comprising a difference between the first timing signal for the cellular network and a second timing signal from the TSN is determined at step 3706. At step 3708, the offset is transmitted to a wireless device connected to the TSN.

Figure 38 illustrates a schematic block diagram of a virtual apparatus 3800 in a wireless network (for example, the wireless network shown in Figure 22). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 2210 or network node 2260 shown in Figure 22). Apparatus 3800 is operable to carry out the example method described with reference to Figure 36 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 36 is not necessarily carried out solely by apparatus 3800. At least some operations of the method can be performed by one or more other entities.

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

According to certain embodiments, receiving module 3810 may perform certain of the receiving functions of the apparatus 3800. For example, receiving module 3810 may receive a second timing signal from at least on time sensitive network (TSN).

According to certain embodiments, performing module 3820 may perform certain of the performing functions of the apparatus 3800. For example, performing module 3820 may perform a comparison the second timing signal to a first time signal for a cellular network.

According to certain embodiments, determining module 3830 may perform certain of the determining functions of the apparatus 3800. For example, determining module 3830 may an offset comprising a difference between the first timing signal for the cellular network and a second timing signal from the TSN based on the comparison.

According to certain embodiments, transmitting module 3840 may perform certain of the transmitting functions of the apparatus 3800. For example, transmitting module 3840 may transmit the offset to a wireless device connected to the TSN.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random- access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure. In view of the above, then, embodiments herein generally include a communication system including a host computer. The host computer may comprise processing circuitry configured to provide user data. The host computer may also comprise a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE). The cellular network may comprise a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the embodiments described above for a base station.

In some embodiments, the communication system further includes the base station.

In some embodiments, the communication system further includes the UE, wherein the UE is configured to communicate with the base station.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data. In this case, the UE comprises processing circuitry configured to execute a client application associated with the host application.

Embodiments herein also include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, providing user data. The method may also comprise, at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station. The base station performs any of the steps of any of the embodiments described above for a base station.

In some embodiments, the method further comprising, at the base station, transmitting the user data.

In some embodiments, the user data is provided at the host computer by executing a host application. In this case, the method further comprises, at the UE, executing a client application associated with the host application.

Embodiments herein also include a user equipment (UE) configured to communicate with a base station. The UE comprises a radio interface and processing circuitry configured to perform any of the embodiments above described for a UE.

Embodiments herein further include a communication system including a host computer. The host computer comprises processing circuitry configured to provide user data, and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE). The UE comprises a radio interface and processing circuitry. The UE’s components are configured to perform any of the steps of any of the embodiments described above for a UE. In some embodiments, the cellular network further includes a base station configured to communicate with the UE.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data. The UE’s processing circuitry is configured to execute a client application associated with the host application.

Embodiments also include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, providing user data and initiating a transmission carrying the user data to the UE via a cellular network comprising the base station. The UE performs any of the steps of any of the embodiments described above for a UE.

In some embodiments, the method further comprises, at the UE, receiving the user data from the base station.

Embodiments herein further include a communication system including a host computer. The host computer comprises a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station. The UE comprises a radio interface and processing circuitry. The UE’s processing circuitry is configured to perform any of the steps of any of the embodiments described above for a UE.

In some embodiments the communication system further includes the UE.

In some embodiments, the communication system further including the base station. In this case, the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application. And the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application, thereby providing request data. And the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

Embodiments herein also include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, receiving user data transmitted to the base station from the UE. The UE performs any of the steps of any of the embodiments described above for the UE. In some embodiments, the method further comprises, at the UE, providing the user data to the base station.

In some embodiments, the method also comprises, at the UE, executing a client application, thereby providing the user data to be transmitted. The method may further comprise, at the host computer, executing a host application associated with the client application.

In some embodiments, the method further comprises, at the UE, executing a client application, and, at the UE, receiving input data to the client application. The input data is provided at the host computer by executing a host application associated with the client application. The user data to be transmitted is provided by the client application in response to the input data.

Embodiments also include a communication system including a host computer. The host computer comprises a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station. The base station comprises a radio interface and processing circuitry. The base station’s processing circuitry is configured to perform any of the steps of any of the embodiments described above for a base station.

In some embodiments, the communication system further includes the base station.

In some embodiments, the communication system further includes the UE. The UE is configured to communicate with the base station.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application. And the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

Embodiments moreover include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE. The UE performs any of the steps of any of the embodiments described above for a UE.

In some embodiments, the method further comprises, at the base station, receiving the user data from the UE.

In some embodiments, the method further comprises, at the base station, initiating a transmission of the received user data to the host computer.

Embodiments herein also include a method performed by a wireless device for reducing deviations between a common cellular reference timing signal, the method comprising: (i) receiving a first timing signal from a cellular network; (ii) receiving a second timing signal from at least on time sensitive network (TSN) to which the wireless device is connected; (iii) comparing the first timing signal to the second timing signal to determine an offset; and (iv) transmitting the offset to a network node.

In some embodiments, the wireless device is a part of the TSN domain.

In some embodiments, the first timing signal comprises a cellular time reference. In some embodiments, the first timing signal is received from the network node.

In some embodiments, the second timing signal comprises a working clock time reference.

In some embodiments, the offset is a measurement of a difference in time between the first timing signal and the second timing signal.

In some embodiments, the offset is transmitted to the network node via RRC signaling.

In some embodiments, the method further comprises receiving, from the network node, a third timing signal from the cellular network, the third timing signal being an adjusted time signal of the first timing signal.

In some embodiments, the method further comprises adjusting a local time reference based on the offset.

In some embodiments, the method further comprises transmitting the offset to the

TSN.

In some embodiments, the method further comprises transmitting at least one of an epoch, a TSN domain number, a time domain identifier to at least one of the network node and the TSN.

Embodiments herein also include a method performed by a base station for reducing deviations between a common cellular reference timing signal, the method comprising: (i) transmitting, to a wireless device, a first timing signal for a cellular network; (ii) receiving, from the wireless device, an offset measured by the wireless device, the offset based on a difference between the first timing signal for the cellular network and a second timing signal associated with at least on time sensitive network (TSN) to which the wireless device is connected; (iii) based on the offset received from the wireless device, determining a third timing signal for the cellular network, the third timing signal being an adjusted time signal of the first timing signal; and (iv) transmitting, to the wireless device, the third timing signal network node. In some embodiments, the method further comprises transmitting at least one of the offset and the third timing signal to the TSN.

In some embodiments, the first timing signal comprises a cellular time reference.

In some embodiments, the second timing signal comprises a working clock time reference.

In some embodiments, the offset is a measurement of a difference in time between the first timing signal and the second timing signal.

In some embodiments, the offset is transmitted to the network node via RRC signaling.

Embodiments herein further include a method performed by a wireless device for reducing deviations between a common cellular reference timing signal, the method comprising: (i) receiving a first timing signal from a cellular network; (ii) receiving a second timing signal from at least on time sensitive network (TSN); (iii) receiving, from a network node associated with the cellular network, an offset measured by the network node, the offset based on a difference between the first timing signal for the cellular network and the second timing signal from the TSN; and (iv) using the offset to reduce a deviation between the first time signal and the second time signal.

In some embodiments, the first time signal is periodically received from the cellular network.

In some embodiments, the second timing signal is received from a GM associated with the TSN.

In some embodiments, the method further comprises receiving, from the network node, at least one of an epoch, a TSN domain number, a time domain identifier.

In some embodiments, the offset is received over dedicate remote resource control (RRC) signaling.

In some embodiments, the second timing signal comprises a working clock time reference.

In some embodiments, the offset is a measurement of a difference in time between the first timing signal and the second timing signal.

In some embodiments, using the offset to reduce the deviation between the first time signal and the second time signal comprises adjusting a local time reference based on the offset.

In some embodiments, the method further comprises transmitting the offset to the

TSN. Embodiments herein also include a method performed by a base station for reducing deviations between a common cellular reference timing signal, the method comprising: (i) receiving a second timing signal from at least on time sensitive network (TSN); (ii) performing a comparison the second timing signal to a first time signal for a cellular network; (iii) based on the comparison, determining an offset comprising a difference between the first timing signal for the cellular network and a second timing signal from the TSN; and (iv) transmitting the offset to a wireless device connected to the TSN.

In some embodiments, the method further comprises transmitting the first time signal to the wireless device, wherein the offset is used by the wireless device to reduce a deviation between the first time signal and the second time signal. In one embodiment, the first time signal is periodically transmitted to the wireless device.

In some embodiments, the second timing signal is received from a GM associated with the TSN.

In some embodiments, the method further comprises transmitting, to the wireless device at least one of an epoch, a TSN domain number, a time domain identifier to at least one of the wireless device and the TSN.

In some embodiments, the offset is transmitted to the wireless device over dedicate remote resource control (RRC) signaling.

In some embodiments, the second timing signal comprises a working clock time reference.

In some embodiments, the offset is a measurement of a difference in time between the first timing signal and the second timing signal.

In some embodiments, the method further comprises adjusting a local time reference based on the offset.

In some embodiments, the method further comprises transmitting the offset to the

TSN.

In some embodiments, the method further comprises transmitting the offset to a plurality of wireless devices connected to the TSN.

Embodiments herein also include a wireless device for improving network efficiency, the wireless device comprising: (i) processing circuitry configured to perform any of the steps of any of the embodiments above; and (ii) power supply circuitry configured to supply power to the wireless device.

Embodiments herein further include a base station for improving network efficiency, the base station comprising: (i) processing circuitry configured to perform any of the steps of any of the embodiments above; and (ii) power supply circuitry configured to supply power to the wireless device.

Embodiments herein also include a user equipment (UE) for improving network efficiency, the UE comprising: (i) an antenna configured to send and receive wireless signals; (ii) radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; (iii) the processing circuitry being configured to perform any of the steps of any of the embodiments above; (iv) an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; (v) an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and (vi) a battery connected to the processing circuitry and configured to supply power to the UE.

Note that terminologies such as base station/gNodeB and UE should be considered non-limiting and do in particular not imply a certain hierarchical relation between the two; in general,“gNodeB” could be considered as device 1 and“UE” could be considered as device 2 and these two devices communicate with each other over some radio channel. And the transmitter or receiver could be either gNB, or UE.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the description.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures,

computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Some of the embodiments contemplated herein are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

Claims

CLAIMS What is claimed is:

1. A method performed by a device in a cellular communication network (10), the method comprising:

receiving (200), at the device, a message (16) that is forwarded by a network node in the cellular communication network (10) and that includes:

time information (20) from a grandmaster clock (22) which provides a time reference applicable to a Time Sensitive Network (TSN) working domain external to the cellular communication network (10); and a network-side timestamp which indicates a time at which the network node received the message (14) from a TSN domain node (15) in the TSN working domain (18), according to a cellular network clock (11) which provides a time reference applicable to the cellular communication network (10);

determining (210) a device-side timestamp that indicates a time at which the device received the message (16), according to the cellular network clock (11); calculating (220), based on the network-side timestamp and the device-side

timestamp, a time delay taken to transmit the message (16) from the network node to the device via the cellular communication network (10); based on the calculated time delay, adding (230) time information to the message (16); and

forwarding (240) the message (16) with the added time information.

2. The method of claim 1 , wherein the added time information is a function of the calculated time delay and the time information from the grandmaster clock (22).

3. The method of any of claims 1-2, wherein the added time information is the time information from the grandmaster clock (22) modified according to the calculated time delay.

4. The method of any of claims 1-3, wherein the message (16) is a Precision Time Protocol (PTP) message received from a TSN node (15) that provides the grandmaster clock (22), and wherein the time information from the grandmaster clock (22) comprises PTP time information.

5. The method of any of claims 1-4, wherein the message (16) is forwarded towards a TSN device, a TSN bridge, or a TSN endpoint.

6. The method of any of claims 1-5, wherein the device is a user equipment.

7. A method performed by a network node in a cellular communication network (10), the method comprising:

receiving (200), from a Time Sensitive Network (TSN) domain node (15) in a TSN working domain external to the cellular communication network (10), a message (14) that includes time information from a grandmaster clock (22) which provides a time reference applicable to the TSN working domain (18); adding (210), to the message (14), a network-side timestamp which indicates a time at which the network node received the message (14) from the TSN domain node (15) in the TSN working domain (18), according to a cellular network clock (11) which provides a time reference applicable to the cellular communication network (10); and

forwarding (220) the message (14), with the network-side timestamp added thereto, towards a device in the cellular communication network (10).

8. The method of claim 7, wherein the message (14) is a Precision Time Protocol (PTP) message received from a TSN node that provides the grandmaster clock (22), and wherein the time information from the grandmaster clock (22) comprises PTP time information.

9. The method of any of claims 7-8, wherein the device is a user equipment.

10. A device configured for use in a cellular communication network (10), the device configured to:

receive a message (16) that is forwarded by a network node in the cellular

communication network (10) and that includes:

time information from a grandmaster clock (22) which provides a time

reference applicable to a Time Sensitive Network (TSN) working domain external to the cellular communication network (10); and a network-side timestamp which indicates a time at which the network node received the message (14) from a TSN domain node (15) in the TSN working domain (18), according to a cellular network clock (11) which provides a time reference applicable to the cellular communication network (10);

determine a device-side timestamp that indicates a time at which the device received the message (16), according to the cellular network clock (11); calculate, based on the network-side timestamp and the device-side timestamp, a time delay taken to transmit the message (16) from the network node to the device via the cellular communication network (10);

based on the calculated time delay, add time information to the message (16); and forward the message (16) with the added time information.

11. The device of claim 10, configured to perform the method of any of claims 2-6.

12. A network node configured for use in a cellular communication network (10), the network node configured to:

receive, from a Time Sensitive Network (TSN) domain node (15) in a TSN working domain external to the cellular communication network (10), a message (14) that includes time information from a grandmaster clock (22) which provides a time reference applicable to the TSN working domain (18);

add, to the message (14), a network-side timestamp which indicates a time at which the network node received the message (14) from the TSN domain node (15) in the TSN working domain (18), according to a cellular network clock (11) which provides a time reference applicable to the cellular communication network (10); and

forward the message (14), with the network-side timestamp added thereto, towards a device in the cellular communication network (10).

13. The network node of claim 12, configured to perform the method of any of claims 8-9.

14. A computer program comprising instructions which, when executed by at least one processor of a device configured for use in a cellular communication network (10), causes the device to perform the method of any of claims 1-6.

15. A computer program comprising instructions which, when executed by at least one processor of a network node configured for use in a cellular communication network (10), causes the network node to perform the method of any of claims 7-9.

16. A carrier containing the computer program of any of claims 14-15, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

17. A device (400) configured for use in a cellular communication network (10), the device (400) comprising:

processing circuitry (410) configured to:

receive a message (16) that is forwarded by a network node in the cellular communication network (10) and that includes:

time information from a grandmaster clock (22) which provides a time reference applicable to a Time Sensitive Network (TSN) working domain external to the cellular communication network (10); and

a network-side timestamp which indicates a time at which the network node received the message (16) from the TSN working domain (18), according to a cellular network clock (11) which provides a time reference applicable to the cellular communication network (10);

determine a device-side timestamp that indicates a time at which the device received the message (16), according to the cellular network clock (1 1);

calculate, based on the network-side timestamp and the device-side

timestamp, a time delay taken to transmit the message (16) from the network node to the device via the cellular communication network (10);

based on the calculated time delay, add time information to the message (16); and

forward the message (16) with the added time information.

18. The device of claim 17, wherein the processing circuitry (410) is configured to perform the method of any of claims 2-6.

19. A network node (500) configured for use in a cellular communication network (10), the network node (500) comprising:

processing circuitry (520) configured to:

receive, from a Time Sensitive Network (TSN) working domain external to the cellular communication network (10), a message (14) that includes time information from a grandmaster clock (22) which provides a time reference applicable to the TSN working domain (18);

add, to the message (14), a network-side timestamp which indicates a time at which the network node received the message (14) from a TSN domain node (15) in the TSN working domain (18), according to a cellular network clock (11) which provides a time reference applicable to the cellular communication network (10); and forward the message (14), with the network-side timestamp added thereto, towards a device in the cellular communication network (10).

20. The network node of claim 19, wherein the processing circuitry (520) is configured to perform the method of any of claims 8-9.