System and method for optimizing air-to-ground time division dual man-time slot utilization

Abstract

A method (1300) by a network node (510) for optimizing time division duplex, TDD, slot utilization includes obtaining (1302) information indicative of a round trip time, RTT, between the network node and a user equipment, UE (512). Based on the RTT, the network node inserts (1304) a guard period within a downlink, DL, transmission to the UE.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, and more specifically to systems and methods for optimizing time division duplex (TDD) time slot utilization in air-to-ground (ATG) communications. Background Technology

[0002] Air-to-ground (ATG) is a current work project in the 3rd Generation Partnership Project (3GPP), aiming to enable communication between aircraft and ground-based base stations using New Radio (NR). User Equipment (UE) is expected to be a dedicated device mounted on the aircraft body, possibly with an antenna array to achieve link budget. Base stations are expected to be dedicated to ATG communication. Conventional NR base stations are expected to be usable for ATG with some adjustments to antenna configuration and orientation. The possibility of base stations deployed for terrestrial networks being used for ATG is not entirely ruled out.

[0003] The ATGUE will be used to distribute internet connectivity to passengers on board the aircraft. The method of data distribution within the aircraft is not specified. The service is likely to be enhanced mobile broadband (eMBB), although other types of services, such as latency-critical or high-reliability services, are not excluded. The ATG can be used to provide internet connectivity for commercial passenger aircraft. Given the potentially large number of passengers on commercial aircraft, the capacity requirements could be significant.

[0004] The cellular range of ATG may vary, but a range of at most 200km-300km is the design target. A Doppler shift between the aircraft and the base station (BS) is expected, which is related to the typical aircraft cruise speed. The aircraft can typically cruise at an altitude of 10km-11km, but operations during takeoff / landing are expected to drop to a minimum altitude (typically around 3km).

[0005] The aircraft is expected to be served at a long distance from the base station (BS). A line-of-sight (LoS) path is anticipated between the aircraft and the BS, thus enabling a high signal-to-noise ratio (SNR) regardless of distance. Service to the aircraft is expected to begin from a distance of approximately 20-50 km from the BS, up to the maximum distance. When the aircraft is closer to the BS than the minimum distance, it will be served by a more distant BS. This is due to the fact that the BS antenna cannot be pointed directly upwards. However, it is not ruled out that installing a directly upward-pointing antenna would allow service to be provided when the aircraft is closer to the BS.

[0006] Figure 1 This shows the overlapping coverage area pointing towards the horizon. Specifically, Figure 1 Three beamforming bases (BS) are shown, providing overlapping coverage areas. Beamforming avoids interference between coverage areas.

[0007] Figure 2The aircraft is shown at its maximum altitude and at its minimum distance from the ATG BS.

[0008] In the initial work project, three frequency bands were considered: n1, n78, and n79. n1 is a Frequency Division Duplex (FDD) band, while n78 and n79 are Time Division Duplex (TDD) bands. The TDD bands were preferred due to the increased bandwidth and smaller antenna array size available. It is claimed that ATG trials have been conducted using TDD bands in China.

[0009] ATG BS is expected to be deployed in rural areas, but within the geographic area of ​​the terrestrial network, or even coexist with the terrestrial network. ATG needs to be synchronized with the terrestrial network to avoid interference between operators.

[0010] To facilitate demodulation, so-called Doppler pre-compensation is expected. Doppler pre-compensation means that the UE understands its Doppler frequency relative to the BS, enabling Doppler compensation in the receiver. In the transmitter, the transmission frequency is offset according to the Doppler frequency.

[0011] It is also expected that the UE will implement timing advance (TA) based on timing pre-compensation. The propagation time between the UE and the BS will be known to the UE, and the UE will advance its uplink transmission based on the propagation delay. This is particularly important when using the Physical Random Access Channel (PRACH) for initial access, as the network cannot provide timing advance information to the UE before the PRACH is transmitted.

[0012] Pre-compensation can be achieved using the same signaling designed for satellites that are part of a non-terrestrial network (NTN) WI. In this case, the SIB19 within the broadcast information contains information about the ATG BS location. The ATG UE needs to have positioning using technologies such as Global Navigation Satellite System (GNSS) and, based on this, be able to calculate its distance to the BS and its velocity relative to the BS, and further calculate Doppler and time pre-compensation. Obtaining pre-compensation information through methods other than SIB19 signaling is not excluded.

[0013] However, there are certain challenges. For example, for ATG TDD systems, ATG UEs must implement large TAs for their uplink (UL) transmissions so that, after propagation delays to the gNodeB (gNB) or other BSs, the reception of UL signals from the UE can be aligned with the UL time slots and symbol timings at the gNB.

[0014] The downlink (DL) signal arriving at the ATG UE will be delayed relative to the gNB by the propagation time from the gNB to the UE. However, the UE must begin transmitting the UL one propagation delay earlier. This means that, from the UE's perspective, UL transmission must begin 2 * propagation time (i.e., round-trip time (RTT)) earlier than the end of the DL signal arriving at the UE.

[0015] The UE cannot transmit and receive simultaneously. Therefore, a guard period equal to the RTT is necessary, during which the gNB neither transmits nor receives.

[0016] ATG cell sizes can be up to 300km. For large cells, RTT can be up to 2 milliseconds. TDD handovers can occur every 5 milliseconds. Importantly, TDD handovers are frequent due to UL latency and control signaling.

[0017] Reserving a 2-millisecond protection period every 5 milliseconds represents a significant overhead for the protection period. Even for small cell sizes, a large protection period is required; for example, a cell radius of 100km might require a 0.67-millisecond protection period.

[0018] ATG networks can handover less frequently to reduce handover-related overhead. However, ATG networks may not be able to use UL time slots from any terrestrial network (TN) in the geographic area for downlink transmission because this would cause gNB-gNB inter-operator interference. Therefore, even with this solution, assuming TN handovers UL-DL at normal frequencies, ATG networks will still have poor time slot utilization. Furthermore, fewer DL-UL handovers will significantly increase UL latency and potentially reduce UL coverage and throughput. Summary of the Invention

[0019] Certain aspects of this disclosure and its embodiments may provide solutions to these or other challenges. For example, methods and systems are provided for enabling a gNB to know the propagation time between the ATG UE and the gNB.

[0020] According to some embodiments, a method for optimizing TDD time slot utilization by a network node includes obtaining information indicating the RTT (Redirect Time To Response) between the network node and the UE. Based on this RTT, the network node inserts a guard period within the DL (Deep Stream) transmission to the UE.

[0021] According to some embodiments, a network node for optimizing TDD time slot utilization is configured to obtain information indicating the RTT between the network node and the UE. Based on this RTT, the network node inserts a guard period within the DL transmission to the UE.

[0022] Some embodiments may provide one or more of the following technical advantages. For example, some embodiments may provide the technical advantage of significantly reducing the overhead of the protection period. For example, because the BS knows when it can continue scheduling DL data before the UE UL transmission, the protection period required for each individual UE can be at least halved.

[0023] As another example, some embodiments offer the technical advantage of allowing protection periods to be configured individually for each UE, rather than based on cell radius. Therefore, protection periods can be minimized for UEs located closer to the gNB than the cell edge.

[0024] Other advantages will be apparent to those skilled in the art. Some embodiments may not have the advantages described, or may have some of the advantages described, or may have all of the advantages described. Attached Figure Description

[0025] To gain a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description in conjunction with the accompanying drawings, in which: Figure 1 Shows the overlapping coverage area pointing towards the horizon; Figure 2 The aircraft is shown at its maximum altitude and minimum distance to ATG BS. Figure 3 The TDD structure from the UE's perspective is shown according to certain embodiments; Figure 4 Another example TDD structure according to certain embodiments is shown; Figure 5 This illustrates another example TDD structure that still exists according to certain embodiments; Figure 6 This illustrates another example TDD structure that still exists according to certain embodiments; Figure 7 An example communication system according to certain embodiments is shown; Figure 8 Example UEs according to certain embodiments are shown; Figure 9 Example network nodes are shown according to certain embodiments; Figure 10 A block diagram of a host according to certain embodiments is shown; Figure 11 A virtualized environment according to certain embodiments is illustrated, wherein functionality implemented by some embodiments can be virtualized; Figure 12 The illustration shows a host communicating with a UE via a network node through a partial wireless connection according to certain embodiments; Figure 13 This illustrates example methods used by a UE to optimize TDD time slot utilization according to certain embodiments; Figure 14 This illustrates example methods used by network nodes to optimize TDD time slot utilization according to certain embodiments; Figure 15 This illustrates another example method, according to certain embodiments, for network nodes to optimize TDD slot utilization; and Figure 16 This illustrates another example method used by a UE to optimize TDD time slot utilization according to certain embodiments. Detailed Implementation

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

[0027] As used herein, a 'node' can be a network node or a UE. Examples of network nodes are: NodeB, Base Station (BS), Multi-Standard Radio (MSR) radio nodes (such as MSR BS), eNodeB (eNB), gNodeB (gNB), Primary eNB (MeNB), Secondary eNB (SeNB), Integrated Access Backhaul (IAB) node, Network Controller, Radio Network Controller (RNC), Base Station Controller (BSC), Repeater, Donor Node Control Repeater, Base Transceiver Station (BTS), Central Unit (e.g., in gNB), Distributed Unit (e.g., in gNB), Baseband Unit, Centralized Baseband, C-RAN, Access Point (AP), Transport Point, Transport Node, Remote Radio Unit (RRU), Remote Radio Header (RRH), nodes in Distributed Antenna System (DAS), Core Network Nodes (e.g., Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operation and Maintenance (O&M), Operation Support System (OSS), Self-Organizing Network (SON), Location Node (e.g., E-SMLC), etc.

[0028] Another example of a node is a User Equipment (UE), which is a non-limiting term and refers to any type of wireless device that communicates with network nodes and / or with another UE in a cellular or mobile communication system. Examples of UEs are: target devices, device-to-device (D2D) UEs, vehicle-to-vehicle (V2V) UEs, machine-type UEs, MTC UEs or UEs capable of machine-to-machine (M2M) communication, personal digital assistants (PDAs), tablet computers, mobile terminals, smartphones, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), unified serial bus (USB) dongles, etc.

[0029] In some embodiments, the generic term "radio network node" or simply "network node (NW node)" is used. It can be any kind of network node, which may include: base station, radio base station, base transceiver station, base station controller, network controller, evolved Node B (eNB), Node B, gNodeB (gNB), relay node, access point, radio access point, remote radio unit (RRU), remote radio headend (RRH), central unit (e.g., in gNB), distributed unit (e.g., in gNB), baseband unit, centralized baseband, C-RAN, access point (AP), etc.

[0030] The term "Radio Access Technology (RAT)" can refer to any RAT, such as, for example, Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRA), Narrowband Internet of Things (NB-IoT), WiFi, Bluetooth, Next Generation RAT, NR, 4G, 5G, etc. Any device referred to by the terms "node," "network node," or "radio network node" may be able to support one or more RATs.

[0031] As used herein, the term "signal" or "radio signal" can refer to any physical signal or physical channel. Examples of downlink (DL) physical signals are reference signals (RS), such as the primary synchronization signal (PSS), secondary synchronization signal (SSS), channel state information-reference signal (CSI-RS), demodulation reference signal (DMRS) in the SS / PBCH block (SSB), discovery reference signal (DRS), cell-specific reference signal (CRS), location reference signal (PRS), etc. RS can be periodic. For example, the timing of an RS carrying one or more RSs can occur at a certain period (e.g., 20 ms, 40 ms, etc.). RS can also be aperiodic.

[0032] Each SSB carries the New Radio-Primary Synchronization Signal (NR-PSS), the New Radio-Secondary Synchronization Signal (NR-SSS), and the New Radio-Physical Broadcast Channel (NR-PBCH) in four consecutive symbols. One or more Synchronization Signal Blocks (SSBs) are transmitted in an SSB burst that repeats at a certain period, such as, for example, 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms. The UE is configured with information about the SSBs on a cell at a certain carrier frequency via one or more SS / PBCH Block Measurement Timing Configuration (SMTC). The SMTC configuration includes parameters such as the SMTC periodicity, the SMTC timing duration or length, and the SMTC time offset relative to a reference time (e.g., the SFN of the serving cell). Therefore, the SMTC timing can also occur at a certain period (e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms). Examples of uplink (UL) physical signals are reference signals, such as sounding reference signals (SRS), demodulation reference signals (DMRS), etc. The term "physical channel" refers to any channel that carries higher-layer information (such as data, control, etc.). Examples of physical channels are physical broadcast channels (PBCH), physical downlink control channels (PDCCH), physical downlink shared channels (PDSCH), physical uplink shared channels (PUSCH), physical uplink control channels (PUCCH), physical uplink shared channels (PUSCH), short PUSCH (sPUCCH), short PDSCH (sPDSCH), short PUCCH (sPUCCH), short PUSCH (sPUSCH), MTC PDCCH (MPDCCH), narrowband PBCH (NPBCH), narrowband PDCCH (NPDCCH), narrowband PDSCH (NPDSCH), narrowband PUSCH (NPUSCH), enhanced PDCCH (E-PDCCH), etc.

[0033] The term "time resource" as used in this document can refer to any type of physical or radio resource expressed in terms of time length. Examples of time resources are: symbols, time slots, subframes, radio frames, TTI, interleaving time, slots, subslots, microslots, system frame number (SFN) periods, super-SFN (H-SFN) periods, etc.

[0034] According to some embodiments, methods and systems are provided for enabling the gNB to know the propagation time between the ATG UE and the gNB. For example, the ATG UE may indicate its current timing advance or its location (or from external data such as aircraft location indication). The gNB then configures a protection period at an appropriate time and for as short a period as possible.

[0035] According to some embodiments, the UE is configured such that, from the UE's perspective, handover to UL can occur as soon as DL reception is complete, thus allowing a short period for RX to TX handover. DL reception can resume once UL transmission is completed at the UE, although DL transmission may not typically be available immediately after UL to avoid DL / UL conflicts on the BS side. While the UE may need to wait some time after UL transmission, this reduces protection period overhead compared to implementing a protection period baseline without knowing the UE timing.

[0036] According to certain embodiments, for example, a method for optimizing the utilization of available time slots in a TDD system with a large propagation RTT may include one or more of the following: - Obtain RTT (Real-Time Tolerance) between the network and the UE at the network location; - Insert a protection period within the network DL transmission based on RTT; - If possible, continue DL transmission on the network side after the protection period, depending on the RTT and UL durations; and - Maximize the utilization of DL time slots based on RTT knowledge to the UE.

[0037] In addition to avoiding TX / RX conflicts at the UE, a short protection period is required before each TX-RX or RX-TX handover at the BS and UE to accommodate the transition time. Since the transition time will be extremely short compared to the large protection period considered due to cell size, and for the sake of clarity in this discussion, the need for GP to adapt to the handover time is omitted. However, in implementations, in some cases, it may be necessary to insert some additional short protection periods within the time slot to accommodate the handover time.

[0038] Consider the first example scenario, which uses a 300km ATG cell as the baseline. The round-trip time is 2 milliseconds. For SCS = 30 kHz, TDD frames are organized into 10 0.5 millisecond slots (numbered 1-10). Slots 1-7 should be DL slots, slot 8 is a "special" slot (where most symbols are configured for downlink), and slots 9 and 10 are allocated for UL.

[0039] Due to the propagation time to the cell edge, for this SCS = 30 kHz example, the gNB needs to allocate time slots 5, 6, 7, and 8 as guard periods. However, all SCSs are possible, such as, for example, 15, 20, 60, 120, 240, 480, and 960 kHz, and differ only by scaling the number of time slots based on the example considered here.

[0040] Figure 3An example TDD structure 100 from the UE's perspective is shown according to some embodiments. As depicted, the UL begins receiving the DL portion of each frame with a 2-slot or 1-millisecond delay. For the UE UL transmission to arrive at the gNB at the correct time, the UE needs to switch to UL after receiving DL slot 4. After transmitting two UL slots, timing at the UE causes slots 7 and 8 to occur; these are guard slots. Following the guard slots, the next two slots, marked "X" in the figure, are slots during which the UE does not receive any data, as they correspond to the slots during which the gNB receives the UL transmission (delayed by 1 millisecond).

[0041] Figure 4 Another example TDD structure 200 according to certain embodiments is shown. In this example embodiment, the ATG is located at the edge of the ATG cell. The gNB receives information about the propagation delay from the UE and allocates a protection period that begins twice the propagation delay (i.e., RTT) earlier than the UL period and has a duration equal to that of the UL period. However, after this protection period, the gNB immediately resumes transmitting DL data to the UE until the UL period begins.

[0042] At the UE, the UE is configured to apply TA to the UL signal (as usual), and then assumes that DL data can begin immediately after it has finished transmitting the UL signal, such as... Figure 4 As described in the document. In this way, half of the guard period slots can be removed. From the UE's perspective, there is no guard period; however, there are two slots in which the UE does not receive downlink data (this is because there is no DL transmission during those slots due to UL reception at the gNB).

[0043] In the second example scenario, the cell size is 300 km, but the ATG UE is located 150 km away from the gNB. The propagation time is 0.5 milliseconds or 1 time slot. Figure 5 An example TDD structure 300 for such a scenario is shown according to certain embodiments.

[0044] In this example scenario, the gNB is made aware that the propagation time is 0.5 milliseconds. The gNB provides a protection period equal to the 0.5 millisecond propagation time at two time slots or one RTT before its UL time slot (i.e., in slot 7). This is the same as in the first example, but scaled down to a smaller RTT. Because the UL is two time slots in duration, the gNB cannot transmit to the UE in slot 8, as the UE will still transmit the UL during that time slot after the propagation delay.

[0045] From the UE's perspective, the UE receives the first 6 DL time slots and then switches to UL. After transmitting UL, the UE does not receive any DL in the next 2 time slots because these time slots correspond to the time when the gNB is receiving the UL signal.

[0046] In the third example scenario, the UE is located 75 km from the gNB. The propagation time is now 0.25 milliseconds, or half a time slot. Figure 6 An example TDD structure 400 for such a scenario is shown according to certain embodiments. Specifically, as depicted, the gNB transmits DL within time slots 1-7. At the beginning of time slot 8, a half-time slot protection period is inserted at 1 RTT = 0.5 milliseconds (1 time slot) before the UL period, which is also equal to the propagation time in the time slot. The gNB cannot transmit during the remaining time of time slot 8 because the DL transmission would overlap with the UE UL transmission.

[0047] From the UE's perspective, the UE receives the first 7 DL time slots and then switches to UL. After the UL time slot, the UE does not receive any data for one time slot, because this time slot corresponds to the second UL time slot received in the gNB.

[0048] Figure 7 An example of a communication system 500 according to some embodiments is shown. In this example, the communication system 500 includes a telecommunications network 502, which includes an access network 504 such as a radio access network (RAN) and a core network 506. The core network 506 includes one or more core network nodes 508. The access network 504 includes one or more access network nodes, such as network nodes 510a and 510b (one or more of which may be collectively referred to as network node 510), or any other similar 3GPP access node or non-3GPP access point. Network node 510 facilitates direct or indirect connections for UEs, such as by connecting UEs 512a, 512b, 512c, and 512d (one or more of which may be collectively referred to as UE 512) to the core network 506 over one or more radio connections.

[0049] Examples of wireless communication over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other conductors. Furthermore, in various embodiments, communication system 500 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals (whether via a wired or wireless connection). Communication system 500 may include any type of communication network, telecommunications network, data network, cellular network, radio network, and / or other similar systems, and / or be connected to them via an interface.

[0050] UE 512 can be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with network node 510 and other communication devices. Similarly, network node 510 is arranged, capable, configured, and / or operable to communicate directly or indirectly with UE 512 and / or with other network nodes or devices in telecommunication network 502 to enable and / or provide network access (such as wireless network access) and / or perform other functions (such as management in telecommunication network 502).

[0051] In the depicted example, core network 506 connects network node 510 to one or more hosts, such as host 516. These connections can be direct or indirect (via one or more intermediate networks or devices). In other examples, network nodes can be directly coupled to hosts. Core network 506 includes one or more core network nodes (e.g., core network node 508), which are constructed through hardware and software components. The characteristics of these components can be substantially similar to those described for UEs, network nodes, and / or hosts, such that the description is generally applicable to the corresponding components of core network node 508. Example core network nodes include the functionality of one or more of the following: MSC, MME, Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Unhiding Function (SIDF), Unified Data Management (UDM), Security Edge Protection Agent (SEPP), Network Open Function (NEF), and / or User Plane Function (UPF).

[0052] Host 516 may be under the ownership or control of a service provider other than the operator or provider of access network 504 and / or telecommunications network 502, and may be operated by or on behalf of the service provider. Host 516 may host various applications to provide one or more services, examples of which include live and pre-recorded audio / video content, data collection services (such as retrieving and compiling data about various environmental conditions detected by multiple UEs), analytics functionality, social media, functionality for controlling or otherwise interacting with remote devices, functionality for alarm and monitoring centers, or any other such functionality performed by a server.

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

[0054] In some examples, telecommunications network 502 is a cellular network implementing 3GPP standardized features. Therefore, telecommunications network 502 can support network slicing to provide different logical networks to different devices connected to it. For example, telecommunications network 502 can provide ultra-reliable low-latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or massive machine-type communication (mMTC) / massive IoT services to yet another UE.

[0055] In some examples, UE 512 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to access network 504 according to a predetermined schedule when triggered by an internal or external event, or in response to a request from access network 504. Additionally, the UE may be configured to operate in single RAT, multi-RAT, or multi-standard modes. For example, the UE may operate using any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for multiple radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) NR-Dual Connectivity (EN-DC).

[0056] In this example, hub 514 communicates with access network 504 to facilitate indirect communication between one or more UEs (e.g., UEs 512c and / or 512d) and network nodes (e.g., network node 510b). In some examples, hub 514 may be, for example, a controller, router, content source and analytics, or any other communication device described herein with respect to the UE. For example, hub 514 may be a broadband router capable of enabling UE access to core network 506. As another example, hub 514 may be a controller that sends commands or instructions to one or more actuators in the UE. Commands or instructions may be received from the UE, from network node 510, or via executable code, scripts, procedures, or other instructions in hub 514. As another example, hub 514 may be a data collector that acts as a temporary storage device for UE data and, in some embodiments, may perform analysis or other processing on the data. As another example, hub 514 may be a content source. For example, for a UE acting as a VR headset, display, speaker, or other media delivery device, hub 514 can retrieve VR assets, video, audio, or other media or sensory information-related data via network nodes, and then hub 514 provides this content directly to the UE after performing local processing, and / or provides it to the UE after adding additional local content. In another example, hub 514 acts as a proxy server or orchestrator for the UE, especially when one or more devices in the UE are low-power IoT devices.

[0057] Hub 514 may have a constant / persistent or intermittent connection to network node 510b. Hub 514 may also allow different communication schemes and / or scheduling between hub 514 and UEs (e.g., UEs 512c and / or 512d) and between hub 514 and core network 506. In other examples, hub 514 is connected to core network 506 and / or one or more UEs via a wired connection. Furthermore, hub 514 may be configured to connect to an M2M service provider via access network 504 and / or to another UE via a direct connection. In some cases, a UE may establish a wireless connection with network node 510 while still being connected via hub 514 via a wired or wireless connection. In some embodiments, hub 514 may be a dedicated hub—that is, a hub whose primary function is to route communication to / from the UE to / from network node 510b. In other embodiments, the central hub 514 may be a non-dedicated central hub—that is, a device capable of operating to route communication between the UE and the network node 510b, but also capable of operating as the start and / or end point of communication for certain data channels.

[0058] Figure 8 A UE 600 is illustrated according to some embodiments. As used herein, a UE refers to a device capable of, configured, positioned, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including Narrowband Internet of Things (NB-IoT) UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0059] The UE may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, the UE may not necessarily be a user in the sense of a human user who owns and / or operates the associated device. Instead, the UE may represent a device intended to be sold to or operated by a human user, but which may not or initially may not be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent a device not intended to be sold to or operated by an end user, but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0060] UE 600 includes processing circuitry 602, which is operatively coupled via bus 604 to input / output interface 606, power supply 608, memory 610, communication interface 612, and / or any other components or any combination thereof. A particular UE may utilize... Figure 8 All components shown, or a subset thereof. The level of integration between components can vary from one UE to another. Furthermore, a particular UE may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0061] Processing circuitry 602 is configured to process instructions and data and can be configured to implement any sequential state machine operable to execute instructions stored in memory 610 as a machine-readable computer program. Processing circuitry 602 can be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic along with appropriate firmware; one or more stored computer programs, general-purpose processors (such as microprocessors or digital signal processors (DSPs)) along with appropriate software; or any combination thereof. For example, processing circuitry 602 may include multiple central processing units (CPUs).

[0062] In this example, input / output interface 606 can be configured to provide one or more interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, other output devices, or any combination thereof. Input devices can allow a user to capture information into UE 600. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, webcams, etc.), microphones, sensors, mice, trackballs, orientation pads, tracking pads, scroll wheels, smart cards, and the like. Presence-sensitive displays may include capacitive or resistive touch sensors to sense input from the user. Sensors may be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, biometric sensors, etc., or any combination thereof. Output devices can use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port can be used to provide both input and output devices.

[0063] In some embodiments, power source 608 may be configured as a battery or battery pack. Other types of power sources may be used, such as external power sources (e.g., power outlets), photovoltaic devices, or power units. Power source 608 may also include power circuitry for delivering power from power source 608 itself and / or external power sources to various parts of UE 600 via input circuitry or an interface such as a power cable. For example, delivering power may be used to charge power source 608. The power circuitry may perform any formatting, conversion, or other modifications on the power from power source 608 to make the power suitable for the corresponding components of UE 600 to which power is supplied.

[0064] Memory 610 can be configured to include memories such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, hard disk, removable cassette tape, flash drive, etc. In one example, memory 610 includes one or more applications 614 (such as an operating system, web browser application, widget, utility engine, or other application) and corresponding data 616. Memory 610 can store any operating system or combination of operating systems from a wide variety of operating systems for use by UE 600.

[0065] Memory 610 can be configured to include multiple physical drive units, such as a Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard drive, thumb drive, pen drive, key drive, high-density digital universal disc (HD-DVD) optical disc drive, internal hard drive, Blu-ray disc drive, holographic digital data storage (HDDS) optical disc drive, external micro dual in-line memory modules (DIMMs), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, smart card memory (such as tamper-proof modules in the form of universal integrated circuit cards (UICCs), including one or more subscriber identification modules (SIMs), such as USIM and / or ISIM), other memory, or any combination thereof. The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card." Memory 610 can allow UE 600 to access instructions, applications, and the like stored on transient or non-transient storage media to offload or upload data. Articles of art (such as articles of art utilizing communication systems) may be tangibly embodied in or contained in memory 610, which may be or may include a device-readable storage medium.

[0066] Processing circuitry 602 can be configured to communicate with an access network or other networks using communication interface 612. Communication interface 612 may include one or more communication subsystems and may include or be communicatively coupled to antenna 622. Communication interface 612 may include one or more transceivers for communication, such as communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in the access network). Each transceiver may include a transmitter 618 and / or a receiver 620 adapted to provide network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, transmitter 618 and receiver 620 may be coupled to one or more antennas (e.g., antenna 622) and may share circuitry, software, or firmware, or alternatively be implemented separately.

[0067] In the illustrated embodiment, the communication functions of the communication interface 612 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth and near-field communication, location-based communication such as using a Global Positioning System (GPS) to determine location, another similar communication function, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so on.

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

[0069] As another example, the UE includes an actuator, motor, or switch associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch can change in response to the received wireless input. For example, the UE may include a motor that adjusts the control surfaces or rotors of a flying drone based on the received input, or control a robotic arm performing a medical procedure based on the received input.

[0070] When a UE takes the form of an Internet of Things (IoT) device, it can be a device for use in one or more application areas, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include devices as or embedded in the following: connected refrigerators or freezers, TVs, connected lighting fixtures, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, monitoring systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, augmented reality (AR) or virtual reality (VR) head-mounted displays, wearable devices for haptic or sensory enhancement, sprinklers, animal or object tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any type of medical device, such as heart rate monitors or remote-controlled surgical robots. In addition to the above... Figure 8 In addition to the other components described in UE 600 shown, a UE in the form of an IoT device also includes circuitry and / or software depending on the intended application of the IoT device.

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

[0072] In practice, any number of UEs can be used together for a single use case. For example, the first UE may be or be integrated into the drone and provide the drone's speed information (obtained via a speed sensor) to a second UE, which acts as a remote controller operating the drone. When the user makes changes from the remote controller, the first UE can adjust the throttle on the drone (e.g., by controlling the actuators) to increase or decrease the drone's speed. The first and / or second UEs may also include more than one of the aforementioned functionalities. For example, a UE may include sensors and actuators and handle data communication between both the speed sensor and the actuators.

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

[0074] Base stations can be classified based on the coverage they provide (or, in other words, their transmission power level), and therefore, depending on the coverage provided, can be called femtocells, picocells, microcells, or macrocells. A base station can be a relay node or a relay donor node controlling a relay. Network nodes can also include one or more (or all) portions of a distributed radio base station, such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as remote radio headends (RRHs). Such remote radio units can be integrated with an antenna or as a radio device integrated with an antenna without integration. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS).

[0075] Other examples of network nodes include multi-transport point (multi-TRP) 5G access nodes, multi-standard radio (MSR) devices such as MSR BS, network controllers such as radio network controllers (RNC) or base station controllers (BSC), base transceiver stations (BTS), transport points, transport nodes, multi-cell / multicast coordination entities (MCE), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, location nodes (e.g., evolved serving mobile location centers (E-SMLC)), and / or minimized drive tests (MDT).

[0076] Network node 700 includes processing circuitry 702, memory 704, communication interface 706, and power supply 708. Network node 700 may consist of multiple physically separate components (e.g., node B components and RNC components, or BTS components and BSC components, etc.), each having its own corresponding components. In the specific case where network node 700 includes multiple separate components (e.g., BTS and BSC components), one or more of these separate components may be shared among several network nodes. For example, a single RNC can control multiple node Bs. In such scenarios, in some instances, each unique node B and RNC pair may be considered a single, separate network node. In some embodiments, network node 700 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 704 for different RATs), and some components may be reused (e.g., the same antenna 710 may be shared by different RATs). Network node 700 may also include multiple sets of various illustrated components for different wireless technologies integrated into network node 700, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-Wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 700.

[0077] The processing circuitry 702 may include one or more of the following: a microprocessor, a controller, a central processing unit, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coding logic operable to provide the functionality of the network node 700, either alone or in combination with other network node 700 components such as memory 704.

[0078] In some embodiments, processing circuitry 702 includes a system-on-a-chip (SOC). In some embodiments, processing circuitry 702 includes one or more of a radio frequency (RF) transceiver circuitry 712 and a baseband processing circuitry 714. In some embodiments, the RF transceiver circuitry 712 and the baseband processing circuitry 714 may be on separate chips (or chipsets), boards, or units, such as radio units and digital units. In alternative embodiments, some or all of the RF transceiver circuitry 712 and the baseband processing circuitry 714 may be on the same chip or chipset, board, or unit.

[0079] Memory 704 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, compact discs (CDs), or digital video discs (DVDs)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by processing circuitry 702. Memory 704 may store any suitable instructions, data, or information, including computer programs, software, applications (including one or more of logic, rules, codes, tables, etc.) and / or other instructions (capable of being executed by processing circuitry 702 and utilized by network node 700). Memory 704 may be used to store any calculations performed by processing circuitry 702 and / or any data received via communication interface 706. In some embodiments, processing circuitry 702 and memory 704 are integrated.

[0080] Communication interface 706 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, communication interface 706 includes one or more ports / terminals 716 for transmitting and receiving data to and from a network, for example, via a wired connection. Communication interface 706 also includes radio front-end circuitry 718, which may be coupled to antenna 710 or, in some embodiments, is part of antenna 710. Radio front-end circuitry 718 includes a filter 720 and an amplifier 722. Radio front-end circuitry 718 may be connected to antenna 710 and processing circuitry 702. Radio front-end circuitry 718 may be configured to modulate the signal transmitted between antenna 710 and processing circuitry 702. Radio front-end circuitry 718 may receive digital data to be transmitted to other network nodes or UEs via a wireless connection. Radio front-end circuitry 718 may use a combination of filter 720 and / or amplifier 722 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 710. Similarly, when receiving data, antenna 710 can collect radio signals, which are then converted into digital data by radio front-end circuitry 718. The digital data can then be passed to processing circuitry 702. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0081] In some alternative embodiments, network node 700 does not include a separate radio front-end circuitry 718; instead, processing circuitry 702 includes radio front-end circuitry and is connected to antenna 710. Similarly, in some embodiments, all or part of RF transceiver circuitry 712 is part of communication interface 706. In other embodiments, communication interface 706 includes one or more ports or terminals 716, radio front-end circuitry 718, and RF transceiver circuitry 712 as part of a radio unit (not shown), and communication interface 706 communicates with baseband processing circuitry 714 as part of a digital unit (not shown).

[0082] Antenna 710 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 710 may be coupled to radio front-end circuitry 718 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 710 may be detachable from network node 700 and may be connected to network node 700 via an interface or port.

[0083] Antenna 710, communication interface 706, and / or processing circuitry 702 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals can be received from the UE, another network node, and / or any other network device. Similarly, antenna 710, communication interface 706, and / or processing circuitry 702 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to the UE, another network node, and / or any other network device.

[0084] Power source 708 provides power to the various components of network node 700 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). Power source 708 may also include or be coupled to power management circuitry to provide power to the components of network node 700 for performing the functionality described herein. For example, network node 700 may be connectable to an external power source (e.g., the power grid, a power outlet) via input circuitry or an interface such as a cable, thereby supplying power to the power circuitry of power source 708. As another example, power source 708 may include a power source in the form of a battery or battery pack, which is connected to or integrated into the power circuitry. The battery can provide backup power in the event of a failure of the external power source.

[0085] Embodiments of network node 700 may include Figure 9Additional components beyond those shown herein are used to provide certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the topics described herein. For example, network node 700 may include a user interface device to allow information to be input into and output from network node 700. This allows users to perform diagnostic, maintenance, repair, and other management functions for network node 700.

[0086] Figure 10 Based on the block diagram of host 800 described in this document, host 800 can be... Figure 7 An embodiment of host 516.

[0087] As used herein, host 800 can be or include various combinations of hardware and / or software, including standalone servers, blade servers, cloud-implemented servers, distributed servers, virtual machines, containers, or processing resources in a server farm. Host 800 can provide one or more services to one or more UEs.

[0088] Host 800 includes processing circuitry 802 operably coupled via bus 804 to input / output interface 806, network interface 808, power supply 810, and memory 812. Other components may be included in other embodiments. These components may be characterized substantially similarly to those for previous figures (such as...). Figure 6 and Figure 7 The features described in the device make its description generally applicable to the corresponding components of the host 800.

[0089] Memory 812 may include one or more computer programs containing one or more host applications 814 and data 816. Data 816 may contain user data, such as data generated by the UE for the host 800 or data generated by the host 800 for the UE. Embodiments of the host 800 may utilize only a subset or all of the components shown. Host application 814 may be implemented in a content-based architecture and may provide support for video codecs (e.g., Universal Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, and g.711), including encoding conversion for multiple different categories, types, or implementations of the UE (e.g., mobile phones, desktop computers, wearable display systems, heads-up display systems). Host application 814 may also provide user authentication and authorization checks and may periodically report health, routing, and content availability to a central node (such as a device in or at the edge of the core network). Therefore, host 800 can select and / or indicate different hosts for over-the-top services for the UE. Host application 814 can support various protocols, such as HTTP Live Streaming (HLS), Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0090] Figure 11 This is a block diagram illustrating a virtualized environment 900 in which functionality implemented by some embodiments can be virtualized.

[0091] In this context, virtualization means creating virtual versions of devices or apparatuses, which may include virtualized hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to any apparatus or its components described herein and involves at least a portion of its functionality being implemented as one or more virtual components. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) in one or more virtual environments 900 hosted by one or more hardware nodes, which are hardware computing devices such as network nodes, UEs, core network nodes, or hosts. Furthermore, in embodiments where virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes can be fully virtualized.

[0092] Application 902 (which may alternatively be referred to as a software instance, virtual device, network function, virtual node, virtual network function, etc.) runs in virtualization environment 900 to implement some of the features, functions, and / or benefits of some embodiments disclosed herein.

[0093] Hardware 904 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, etc. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 908a and 908b (one or more of which may be collectively referred to as VM 908), and / or perform any functionality, features, and / or benefits described with respect to some embodiments described herein. Virtualization layer 906 may present a virtual operating platform to VM 908 that appears to be networked hardware.

[0094] VM 908 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can be operated by a corresponding virtualization layer 906. Different embodiments of instances of virtual devices 902 can be implemented on one or more VMs 908, and these implementations can be performed in different ways. Hardware virtualization is referred to in some contexts as Network Functions Virtualization (NFV). NFV can be used to consolidate many types of network devices onto industry-standard high-capacity server hardware, physical switches, and physical storage devices (which can reside in data centers and customer premises).

[0095] In the context of NFV, VMs 908 can be software implementations of the physical machine running programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 908, along with the portion of the hardware 904 executing that VM (whether dedicated to that VM or shared by that VM with other VMs), forms a separate virtual network element. Still within the context of NFV, the virtual network function is responsible for handling specific network functions running on one or more VMs 908 above the hardware 904 and corresponds to application 902.

[0096] Hardware 904 can be implemented in a standalone network node with general-purpose or special-purpose components. Hardware 904 may implement some functions via virtualization. Alternatively, hardware 904 may be part of a larger hardware cluster (e.g., in a data center or CPE), where many hardware nodes work together and are managed via management and orchestration 910, which, among other operations, oversees the lifecycle management of application 902. In some embodiments, hardware 904 is coupled to one or more radio units, each including one or more transmitters that can be coupled to one or more antennas and one or more receivers. The radio units may communicate directly with other hardware nodes via one or more suitable network interfaces and may be used in conjunction with virtual components to provide a radio-capable virtual node, such as a radio access node or base station. In some embodiments, some signaling may be provided using a control system 912, which may alternatively be used for communication between the hardware nodes and the radio units.

[0097] Figure 12 A communication diagram is shown showing a host 1002 communicating with a UE 1006 via a network node 1004 through a partial wireless connection, according to some embodiments.

[0098] Now refer to Figure 12 Describe the UEs discussed in the preceding paragraphs (such as...) Figure 7 UE 512a and / or Figure 8 UE600), network nodes (such as Figure 7 Network node 510a and / or Figure 9 Network node 700) and host (such as Figure 7 Host 516 and / or Figure 10 Example implementations of the host 800 according to various embodiments.

[0099] Similar to host 800, embodiments of host 1002 include hardware such as a communication interface, processing circuitry, and memory. Host 1002 also includes software stored in or accessible by host 1002 and executable by the processing circuitry. This software includes a host application operable to provide services to remote users, such as UE 1006 connected via an over-the-top (OTT) connection 1050 extending between UE 1006 and host 1002. When providing services to remote users, the host application can provide user data transmitted using the OTT connection 1050.

[0100] Network node 1004 includes hardware that enables it to communicate with host 1002 and UE 1006. Connection 1060 can be direct or via a core network (e.g., Figure 7The core network (506) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network could be a backbone network or the Internet.

[0101] UE 1006 includes hardware and software stored in or accessible by UE 1006 and executable by UE processing circuitry. The software includes client applications, such as web browsers or carrier-specific "apps," operable to provide services to human or non-human users via UE 1006 with the support of host 1002. In host 1002, the executing host application can communicate with the executing client application via OTT connection 1050, which terminates between UE 1006 and host 1002. When providing services to a user, the UE's client application can receive request data from the host application of the host and provide user data in response to that request data. OTT connection 1050 can transmit request data and user data. The UE's client application can interact with the user to generate user data, which it provides to the host application via OTT connection 1050.

[0102] OTT connection 1050 can be extended via connection 1060 between host 1002 and network node 1004 and via wireless connection 1070 between network node 1004 and UE 1006 to provide connectivity between host 1002 and UE 1006. Connection 1060 and wireless connection 1070, on which OTT connection 1050 can be provided, have been abstractly drawn to illustrate communication between host 1002 and UE 1006 via network node 1004 without explicitly referring to any intermediate devices and the precise routing of messages via these devices.

[0103] As an example of data transmission via OTT connection 1050, in step 1008, host 1002 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 1006. In other embodiments, the user data is associated with UE 1006, which shares data with host 1002 without explicit human interaction. In step 1010, host 1002 initiates a transmission carrying user data to UE 1006. Host 1002 may initiate the transmission in response to a request transmitted by UE 1006. This request may be caused by human interaction with UE 1006 or by operation of a client application executed on UE 1006. According to the teachings of the embodiments described throughout this disclosure, the transmission may be carried out via network node 1004. Therefore, in step 1012, according to the teachings of the embodiments described throughout this disclosure, network node 1004 transmits the user data carried in the transmission initiated by host 1002 to UE 1006. In step 1014, UE 1006 receives the user data carried in the transmission, which can be performed by a client application running on UE 1006 associated with a host application running on host 1002.

[0104] In some examples, UE 1006 executes a client application that provides user data to host 1002. The user data may be provided as a response or reaction to data received from host 1002. Therefore, in step 1016, UE 1006 can provide user data, which can be done by executing a client application. When providing user data, the client application may also consider user input received from a user via the input / output interface of UE 1006. Regardless of the specific manner in which the user data is provided, in step 1018, UE 1006 initiates a transmission of user data to host 1002 via network node 1004. In step 1020, in accordance with the teachings of the embodiments described throughout this disclosure, network node 1004 receives user data from UE 1006 and initiates a transmission of the received user data to host 1002. In step 1022, host 1002 receives the user data carried in the transmission initiated by UE 1006.

[0105] One or more embodiments in various examples use OTT connection 1050 to improve the performance of OTT services provided to UE 1006, wherein wireless connection 1070 forms the final segment. More specifically, the teachings of these embodiments can improve one or more of, for example, data rate, latency, and / or power consumption, and thereby provide benefits such as, for example, reduced user wait time, relaxed restrictions on file size, improved content resolution, better responsiveness, and / or extended battery life.

[0106] In the example scenario, factory status information can be collected and analyzed by host 1002. As another example, host 1002 can process audio and video data retrieved from the UE for map creation. As another example, host 1002 can collect and analyze real-time data to help control traffic congestion (e.g., control traffic lights). As another example, host 1002 can store surveillance video uploaded by the UE. As another example, host 1002 can store or control access to media content, such as video, audio, VR, or AR, which can be broadcast, multicast, or unicast to the UE. As other examples, host 1002 can be used for energy pricing, remote control of non-time-critical electrical loads to balance generation demand, location services, presentation services (such as compiled graphs based on data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data.

[0107] In some examples, a measurement process may be provided for the purpose of monitoring data rates, latency, and other factors that improve upon one or more of the embodiments. Optional network functionality may also be present for reconfiguring the OTT connection 1050 between host 1002 and UE 1006 in response to changes in measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection may be implemented in the software and hardware of host 1002 and / or in the software and hardware of UE 1006. In embodiments, sensors (not shown) may be deployed in or associated with other devices traversed by the OTT connection 1050; the sensors may participate in the measurement process by providing values ​​of the monitored quantities illustrated above or by providing values ​​of other physical quantities that the software can use to calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1050 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not require a direct change to the operation of network node 1004. Such processes and functionalities may be known and practiced in the art. In some embodiments, the measurements may involve dedicated UE signaling, which helps host 1002 to measure throughput, propagation time, latency, and the like. These measurements are made possible because the software uses OTT connection 1050 to transmit messages (especially empty or “pseudo” messages) while monitoring propagation time, errors, etc.

[0108] Figure 13An example method 1100 for optimizing TDD time slot utilization by UE 512 according to certain embodiments is illustrated. In the illustrated embodiment, the method includes a transmission step 1102, a receiving step at 1104, and a transmission step at 1106. For example, in step 1102, UE 512 may transmit information indicating the RTT time between the UE and the network node to network node 510. As another example, in the receiving step 1104, UE 512 may receive a DL transmission from network node 510. As another example, in the transmission step 1106, after receiving the DL transmission, UE 512 may transmit a UL transmission to network node 510 in a first resource.

[0109] Figure 14 An example method 1200 for optimizing TDD time slot utilization by network node 510 according to certain embodiments is illustrated. In the illustrated embodiment, the method includes an acquisition step at 1202 and an insertion step at 1204. For example, in step 1202, network node 510 may acquire information indicating the RTT between network node 510 and UE 512. For example, in step 1204, network node 510 may insert a protection period within a DL transmission to UE 512 based on the RTT.

[0110] Figure 15 A method 1300 for optimizing TDD time slot utilization by network node 510 according to certain embodiments is illustrated. The method begins at step 1302, when network node 510 obtains information indicating the RTT between network node 510 and UE 512. Based on the RTT, network node 510 inserts a guard period within the DL transmission to the UE.

[0111] In a particular embodiment, obtaining information indicating the RTT between the network node and the UE includes receiving the information from the UE 512.

[0112] In a particular embodiment, network node 510 determines when to resume the DL transmission after the protection period based on the duration of the RTT and the UL transmission from UE 512.

[0113] In a particular embodiment, network node 510 schedules at least one resource based on the RTT and the duration of the UL transmission from UE 512 to resume the DL transmission after the protection period. Network node 510 resumes the DL transmission in the at least one resource.

[0114] In a particular embodiment, the at least one resource is scheduled before the UL transmission is received from the UE 512.

[0115] In a particular embodiment, the UL transmission is received in a first time slot, the at least one resource including a second time slot that occurs after the first time slot, and the second time slot is determined based on the duration of the UL transmission.

[0116] In a particular embodiment, the duration of the protection period is longer when the UE 512 is located closer to the cell edge, and the duration of the protection period is shorter when the UE 512 is located closer to the cell center.

[0117] In a particular embodiment, the protection period is inserted twice the propagation delay before the UL period. Network node 150 resumes the DL transmission in a first resource after the protection period.

[0118] In a particular embodiment, the protection period is inserted one RTT before the UL period, and network node 510 resumes the DL transmission in a first resource after the UL period.

[0119] In a particular embodiment, network node 510 receives the UL signal in the first resource after the protection period.

[0120] In a particular embodiment, the UE is an ATG UE.

[0121] Figure 16 A method 1400 for optimizing TDD time slot utilization by UE 512 according to certain embodiments is illustrated. The method includes step 1402, in which UE 512 transmits information indicating RTT between UE 512 and network node 510 to network node 510.

[0122] In a particular embodiment, UE 512 is configured or at least one resource is scheduled based on information indicating RTT sent to network node 510.

[0123] In a particular embodiment, network node 510 uses the RTT to optimize TDD time slot utilization.

[0124] In a particular embodiment, UE 512 receives DL transmissions from network node 510 and, after receiving the DL transmissions, transmits UL transmissions to network node 510 in a first resource.

[0125] In a particular embodiment, UE 512 receives additional or resumed DL transmissions in the first resource after transmitting the UL transmission.

[0126] In a particular embodiment, network node 510 uses the RTT to schedule at least one resource for an additional or resumed DL transfer.

[0127] In a particular embodiment, the additional or resumed DL transmission is received in at least one resource that occurs after the duration of the UL transmission.

[0128] In a particular embodiment, the DL transmission is received in a first time slot. The UE 512 transmits the UL transmission in a second time slot, and the first and second time slots are consecutive time slots.

[0129] In a particular embodiment, the UE is an ATG UE.

[0130] While the computing devices described herein (e.g., UE, network node, host) may include combinations of the hardware components shown, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by processing circuitry that processes information by, for example, converting acquired information into other information, comparing the acquired or converted information with information stored in a network node, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing. Furthermore, although components are depicted as individual boxes located within larger boxes or nested within multiple boxes, in practice, a computing device may include multiple different physical components constituting a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between processing circuitry and the communication interface. In another example, non-computationally intensive functions of any such component may be implemented in software or firmware, and computationally intensive functions may be implemented in hardware.

[0131] In some embodiments, some or all of the functionality described herein may be provided by processing circuitry that executes instructions stored in memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, the processing circuitry may be configured to perform the described functionality regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functionality are not limited to individual processing circuitry or other components of the computing device, but are enjoyed by the computing device as a whole and / or generally by the end user and wireless network.

[0132] Example Implementation Group A Example Implementation Example Implementation A1. A method for optimizing TDD time slot utilization of ATG by a user equipment, the method comprising: any of the above-described user equipment steps, features, or functions, either alone or in combination with the other steps, features, or functions described above.

[0133] Example Implementation A2. The method of the preceding embodiment further includes one or more of the additional user equipment steps, features, or functions described above.

[0134] Example Implementation A3. The method of any of the foregoing embodiments further includes: providing user data; and forwarding the user data to a host computer via transmission to a network node.

[0135] Group B Example Implementation Example Implementation B1. A method for optimizing TDD time slot utilization of ATG, performed by a network node, the method comprising: any network node step, feature, or function, either alone or in combination with the other steps, features, or functions described above.

[0136] Example Implementation B2. The method of the preceding embodiment further includes one or more of the additional network node steps, features, or functions described above.

[0137] Example Implementation B3. The method of any of the foregoing embodiments further includes: obtaining user data; and forwarding the user data to a host or user equipment.

[0138] Group C Example Implementation Example Implementation C1. A method for optimizing TDD time slot utilization by a UE, the method comprising: transmitting information indicating the RTT time between the UE and the network node to a network node; receiving a DL transmission from the network node; and, after receiving the DL transmission, transmitting a UL transmission to the network node in a first resource.

[0139] Example Implementation C2. The method of Example Implementation C1 includes switching from a receive mode to a transmit mode immediately after receiving the DL transmission.

[0140] Example Implementation C3. The method of Example Implementations C1 to C2 includes switching from a transmit mode to a receive mode immediately after receiving the DL transmission.

[0141] Example Implementation C4. The method of Example Implementations C1 to C3 includes receiving an additional or restored DL transmission in a first resource after transmitting the UL transmission.

[0142] Example Implementation C5. The method of Example Implementation C4, wherein at least one resource is scheduled for the additional or resumed DL transmission based on the RTT and the duration of the UL transmission from the UE.

[0143] Example Implementation C6. The method of Example Implementation C5, wherein the at least one resource is scheduled before the UE transmits the UL transmission.

[0144] Example embodiment C7. The method of any one of example embodiments C5 to C6, wherein the additional or resumed DL transmission is received in at least one resource occurring after the duration of the UL transmission.

[0145] Example Implementation C8. The method of any one of Example Implementations C1 to C7, wherein transmitting the UL transmission in a first resource after receiving the DL transmission includes transmitting the UL transmission in a first time slot immediately preceding the time slot of receiving the DL transmission.

[0146] Example Implementation C9. A method of any one of Example Implementations C1 to C7, wherein the DL transmission is received in a first time slot, and wherein transmitting the UL transmission in the first resource includes transmitting the UL transmission in a second time slot, and wherein the first time slot and the second time slot are consecutive time slots.

[0147] Example embodiment C10. The method of any one of example embodiments C1 to C9, wherein the UE is an ATG UE.

[0148] Example embodiment C11. The method of example embodiments C1 to C10 further includes: providing user data; and forwarding the user data to a host via transmission to the network node.

[0149] Example embodiment C12. A user equipment includes processing circuitry configured to perform any of the methods of example embodiments C1 to C11.

[0150] Example Implementation C13. A user equipment configured to perform any of the methods of Example Implementations C1 to C11.

[0151] Example embodiment C14. A wireless device includes processing circuitry configured to perform any of the methods of example embodiments C1 to C11.

[0152] Example Implementation C15. A computer program including instructions that, when executed on a computer, perform any of the methods of Example Implementations C1 to C11.

[0153] Example Implementation C16. A computer program product including a computer program, the computer program including instructions that, when executed on a computer, perform any of the methods of Example Implementations C1 to C11.

[0154] Example Implementation C17. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods of Example Implementations C1 to C11.

[0155] Example Implementation of Group D Example Implementation D1. A method for optimizing TDD time slot utilization by a network node, the method comprising: obtaining information indicating the RTT between the network node and a UE; and inserting a guard period in a DL transmission to the UE based on the RTT.

[0156] Example Implementation D2. The method of Example Implementation D1 includes determining when to resume the DL transmission after the protection period based on the RTT and the duration of the UL transmission from the UE.

[0157] Example Implementation D3. A method of any one of Example Implementations D1 to D2, comprising scheduling at least one resource for resuming the DL transmission after the protection period, based on the RTT and the duration of the UL transmission from the UE.

[0158] Example Implementation D4. The method of Example Implementation D3, wherein the at least one resource is scheduled before receiving the UL transmission from the UE.

[0159] Example Implementation D5. A method of any one of Example Implementations D3 to D4, comprising resuming the DL transfer in the at least one resource.

[0160] Example embodiment D6. The method of example embodiments D3 to D5, wherein the UL transmission is received in a first time slot, and wherein the at least one resource includes a second time slot that occurs immediately after the first time slot, and wherein the first time slot and the second time slot are consecutive time slots.

[0161] Example embodiment D7. The method of example embodiments D3 to D5, wherein the UL transmission is received in a first time slot, and wherein the at least one resource includes a second time slot that occurs after the first time slot, and wherein the second time slot is determined based on the duration of the UL transmission.

[0162] Example Implementation D8. The method of any one of Example Implementations D1 to D7, wherein the duration of the protection period is determined based on the cell radius.

[0163] Example Implementation D9. The method of any one of Example Implementations D1 to D8, wherein the duration of the protection period increases as the RTT between the network and the UE increases.

[0164] Example Implementation D10. The method of any one of Example Implementations D1 to D9, wherein the duration of the protection period is longer when the UE is located closer to the cell edge and shorter when the UE is located closer to the cell center.

[0165] Example Implementation D11. The method of any one of Example Implementations D1 to D10, wherein the protection period is inserted at twice the RTT before the uplink transmission period, and wherein the method includes resuming the DL transmission in a first resource after the protection period.

[0166] Example Implementation D12. A method of any one of Example Implementations D1 to D10, wherein the guard period is inserted at an RTT preceding the uplink transmission period, and wherein the method includes resuming the DL transmission in a first resource following the uplink transmission period.

[0167] Example Implementation D13. The method of any one of Example Implementations D1 to D12 includes receiving an uplink signal in the first resource after the protection period.

[0168] Example Implementation D14. The method of any one of Example Implementations D1 to D13, wherein the UE is an ATG UE.

[0169] Example Implementation D15. A method of any one of Example Implementations D1 to D14, wherein obtaining the information indicating the RTT between the network node and the UE includes receiving the information from the UE.

[0170] Example Implementation D16. The method of any one of Example Implementations D1 to D15, wherein the network node includes gNodeB (gNB).

[0171] Example Implementation D17. The method in any of the foregoing example implementations further includes: obtaining user data; and forwarding the user data to a host or user equipment.

[0172] Example Implementation D18. A network node including processing circuitry configured to perform any of the methods in Example Implementations D1 to D17.

[0173] Example Implementation D19. A network node configured to perform any of the methods in Example Implementations D1 to D17.

[0174] Example Implementation D20. A computer program including instructions that, when executed on a computer, perform any of the methods of Example Implementations D1 to D17.

[0175] Example Implementation D21. A computer program product including a computer program, the computer program including instructions that, when executed on a computer, perform any of the methods of Example Implementations D1 to D17.

[0176] Example Implementation D22. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods in Example Implementations D1 to D17.

[0177] Example Implementation of Group E Example Implementation E1: A user equipment includes: processing circuitry configured to perform any step of any example embodiment in the example embodiments of Group A and Group C; and a power supply circuitry configured to supply power to the processing circuitry.

[0178] Example Implementation E2: A network node comprising: processing circuitry configured to perform any step of any example embodiment in the example embodiments of Group B and Group D; and a power supply circuitry configured to supply power to the processing circuitry.

[0179] Example Implementation E3: A user equipment (UE) includes: an antenna configured to transmit and receive wireless signals; radio front-end circuitry connected to the antenna and connected to processing circuitry, and configured to modulate signals transmitted between the antenna and the processing circuitry; processing circuitry configured to perform any step of any example embodiment in the example embodiments of Group A and Group C; an input interface connected to the processing circuitry and configured to allow information to be input into the UE for processing by the processing circuitry; an output interface connected to the processing circuitry and configured to output information processed by the processing circuitry from the UE; and a battery connected to the processing circuitry and configured to supply power to the UE.

[0180] Example Implementation E4: A host configured to operate in a communication system to provide over-the-top (OTT) services, the host including: processing circuitry configured to provide user data; and a network interface configured to initiate the transmission of user data to a cellular network for transmission to a UE, wherein the UE includes a communication interface and processing circuitry, the UE's communication interface and processing circuitry being configured to perform any step of any example embodiment in the Group A and Group C example embodiments to receive user data from the host.

[0181] Example Implementation E5: The host according to the previous example implementation, wherein the cellular network further includes a network node configured to communicate with the UE to transmit user data from the host to the UE.

[0182] Example Implementation E6: The host according to the first two example implementations, wherein: the host's processing circuitry is configured to execute a host application to provide user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0183] Example Implementation E7: A method implemented by a host operating in a communication system, the communication system further including a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating a transmission carrying the user data to the UE via a cellular network including the network node, wherein the UE performs any operation of any example embodiment in any example embodiment of Group A example embodiments to receive user data from the host.

[0184] Example Implementation E8: The method according to the previous example implementation further includes: on the host, executing a host application associated with a client application executed on the UE to receive user data from the UE.

[0185] Example Implementation E9: The method according to the previous example implementation further includes: transmitting input data to a client application executed on the UE at the host, the input data being provided by executing the host application, wherein user data is provided by the client application in response to input data from the host application.

[0186] Example Implementation E10: A host configured to operate in a communication system to provide over-the-top (OTT) services, the host including: processing circuitry configured to provide user data; and a network interface configured to initiate the transmission of user data to a cellular network for transmission to a user equipment (UE), wherein the UE includes a communication interface and processing circuitry, the UE's communication interface and processing circuitry being configured to perform any step of any example embodiment in the Group A and Group C example embodiments to transmit user data to the host.

[0187] Example Implementation E11: The host according to the previous example implementation, wherein the cellular network further includes a network node configured to communicate with the UE to transmit user data from the UE to the host.

[0188] Example Implementation E12: The host according to the first two example implementations, wherein: the host's processing circuitry is configured to execute a host application to provide user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0189] Example Implementation E13: A method implemented by a host configured to operate in a communication system including a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted from the UE to the host via the network node, wherein the UE performs any step of any example embodiment in the example embodiments of Group A and Group C to transmit the user data to the host.

[0190] Example Implementation E14: The method according to the previous example implementation further includes: on the host, executing a host application associated with a client application executed on the UE to receive user data from the UE.

[0191] Example Implementation E15: The method according to the previous example implementation further includes: transmitting input data to a client application executed on the UE at the host, the input data being provided by executing the host application, wherein user data is provided by the client application in response to input data from the host application.

[0192] Example Implementation E16: A host configured to operate in a communication system to provide over-the-top (OTT) services, the host including: processing circuitry configured to provide user data; and a network interface configured to initiate the transmission of user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any operation of any example embodiment in the example embodiments of Group B and Group D to transmit user data from the host to the UE.

[0193] Example Implementation E17: The host according to the previous example implementation, wherein: the host's processing circuitry is configured to execute a host application that provides user data; and the UE includes processing circuitry configured to execute a client application associated with the host application to receive transmissions of user data from the host.

[0194] Example Implementation E18: A method implemented in a host configured to operate in a communication system including a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating a transmission of the user data to the UE via a cellular network including the network node, wherein the network node performs any operation of any example embodiment in the example embodiments of Group B and Group D to transmit the user data from the host to the UE.

[0195] Example Implementation E19: The method according to the previous example implementation further includes: at a network node, transmitting user data provided by the host to the UE.

[0196] Example Implementation E20: The method described in any of the example embodiments of the first two example embodiments, wherein user data is provided on the host by executing a host application that interacts with a client application executed on the UE, the client application being associated with the host application.

[0197] Example Implementation E21: A communication system configured to provide over-the-top services, the communication system including a host, the host including: processing circuitry configured to provide user data to a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate the transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any operation of any example embodiment in the example embodiments of Group B and Group D to transmit the user data from the host to the UE.

[0198] Example embodiment E22: The communication system according to the previous example embodiment further includes: the network node; and / or the user equipment.

[0199] Example Implementation E23: A host configured to operate in a communication system to provide over-the-top (OTT) services, the host including: processing circuitry configured to initiate the reception of user data; and a network interface configured to receive user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any operation of any example embodiment in the example embodiments of Group B and Group D to receive user data from the host's user equipment (UE).

[0200] Example Implementation E24: The host according to the first two example implementations, wherein: the processing circuit of the host is configured to execute a host application to provide user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0201] Example Implementation E25: The host described in any of the example embodiments in the first two example embodiments, wherein initiating the reception of user data includes requesting user data.

[0202] Example Implementation E26: A method implemented by a host configured to operate in a communication system including network nodes and user equipment (UE), the method comprising: At the host, the reception of user data from the UE is initiated. This user data originates from a transmission already received by the network node from the UE. The network node performs any step of any example embodiment in the example embodiments of Groups B and D to receive user data from the UE at the host.

[0203] Example Implementation E27: The method according to the previous example implementation further includes: at the network node, transmitting the received user data to the host.

Claims

1. A method (1300) for optimizing time-division duplex (TDD) time slot utilization by a network node (510), the method comprising: Obtain (1302) information indicating the round-trip time (RTT) between the network node and the user equipment (UE) (512); as well as Based on the RTT, a protection period (1304) is inserted within the downlink DL transmission to the UE.

2. The method as described in claim 1, wherein, Obtaining the information indicating the RTT between the network node and the UE includes receiving the information from the UE.

3. The method of any one of claims 1 to 2, comprising determining when to resume the DL transmission after the protection period based on the duration of the RTT and the UL transmission from the UE.

4. The method according to any one of claims 1 to 3, comprising: Based on the duration of the RTT and the UL transmission from the UE, at least one resource is scheduled to resume the DL transmission after the protection period; as well as Resume the DL transfer in at least one of the resources.

5. The method of claim 4, wherein, The at least one resource is scheduled before receiving the UL transmission from the UE.

6. The method as described in claims 4 to 5, wherein: The UL transmission is received in the first time slot. The at least one resource includes a second time slot that occurs after the first time slot, and The second time slot is determined based on the duration of the UL transmission.

7. The method according to any one of claims 1 to 6, wherein, The duration of the protection period is longer when the UE is located closer to the cell edge, and shorter when the UE is located closer to the cell center.

8. The method according to any one of claims 1 to 7, wherein, The protection period is inserted twice the propagation delay before the uplink period, and the method includes resuming the DL transmission in a first resource after the protection period.

9. The method according to any one of claims 1 to 7, wherein, The protection period is inserted one RTT before the uplink period, and the method includes resuming the DL transmission in a first resource after the uplink period.

10. The method of any one of claims 1 to 9, comprising receiving an uplink signal in the first resource after the protection period.

11. The method according to any one of claims 1 to 10, wherein, The UE is an air-to-ground UE (ATG UE).

12. A method (1400) for optimizing time division duplex (TDD) time slot utilization by a user equipment (UE) (512), the method comprising: Transmit (1402) information indicating the round-trip time between the UE and the network node to the network node (510).

13. The method of claim 12, wherein, Configure the UE or schedule at least one resource based on the information sent to the network node instructing the RTT.

14. The method according to any one of claims 12 to 13, wherein, The network uses the RTT to optimize TDD time slot utilization.

15. The method of any one of claims 12 to 14, comprising: Receive downlink DL transmissions from the network node; as well as After receiving the DL transmission, an uplink UL transmission is transmitted to the network node in the first resource.

16. The method of claim 15, further comprising receiving, in the first resource, an additional or resumed DL transmission after the UL transmission has been transmitted.

17. The method of claim 16, wherein, The network node uses the RTT to schedule at least one resource for the additional or resumed DL transfer.

18. The method of claim 17, wherein, The additional or resumed DL transmission is received in at least one resource after the duration of the UL transmission.

19. The method according to any one of claims 15 to 18, wherein, The DL transmission is received in a first time slot, and wherein transmitting the UL transmission in the first resource includes transmitting the UL transmission in a second time slot, and wherein the first time slot and the second time slot are consecutive time slots.

20. The method of any one of claims 12 to 19, wherein, The UE is an air-to-ground UE (ATG UE).

21. A network node (510) for optimizing time-division duplex (TDD) time slot utilization, the network node being configured to: Obtain information indicating the round-trip time (RTT) between the network node and the user equipment (UE) (512); and Based on the RTT, a protection period is inserted during the downlink DL transmission to the UE.

22. The network node as described in claim 21, wherein, When the information indicating the RTT between the network node and the UE is obtained, the network node is configured to receive the information from the UE.

23. The network node as described in any one of claims 21 to 22, wherein, The network node is configured to determine when to resume the DL transmission after the protection period based on the RTT and the duration of the UL transmission from the UE.

24. The network node as claimed in any one of claims 21 to 23, wherein, The network node is configured as follows: Based on the duration of the RTT and the UL transmission from the UE, at least one resource is scheduled to resume the DL transmission after the protection period; and Resume the DL transfer in at least one of the resources.

25. The network node as described in claim 24, wherein, The at least one resource is scheduled before receiving the UL transmission from the UE.

26. The network node as described in claims 24 to 25, wherein: The UL transmission is received in the first time slot. The at least one resource includes a second time slot that occurs after the first time slot, and The second time slot is determined based on the duration of the UL transmission.

27. The network node as claimed in any one of claims 21 to 26, wherein, The duration of the protection period is longer when the UE is located closer to the cell edge, and shorter when the UE is located closer to the cell center.

28. The network node as claimed in any one of claims 21 to 27, wherein, The protection period is inserted twice the propagation delay before the uplink period, and the method includes resuming the DL transmission in a first resource after the protection period.

29. The network node as claimed in any one of claims 21 to 27, wherein, The protection period is inserted one RTT before the uplink period, and the method includes resuming the DL transmission in a first resource after the uplink period.

30. The network node of any one of claims 21 to 29, comprising receiving an uplink signal in the first resource after the protection period.

31. The network node as claimed in any one of claims 21 to 30, wherein, The UE is an air-to-ground UE (ATG UE).

32. A user equipment (UE) (512) for optimizing time division duplex (TDD) time slot utilization, the UE being configured to Transmit information indicating the round-trip time between the UE and the network node to the network node (510).

33. The UE of claim 32, configured to perform any one of the methods of claims 13 to 20.

Images