Method to provide service to high-speed user equipments
By determining and pre-compensating for Doppler shifts using aviation navigation systems, the method addresses the challenge of excessive Doppler shifts in 5G terrestrial systems, enabling reliable communications for high-speed UEs in large cell air-to-ground networks.
Patent Information
- Application Number
- PCT/SE2024/050514
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-26
- Filing Date
- 2024-05-24
- Publication Date
- 2024-12-05
AI Technical Summary
Current 5G terrestrial systems are unable to provide service to high-speed user equipment (UEs) such as airplanes and fast UAVs in large cell air-to-ground networks due to excessive Doppler shifts, which exceed the limitations of existing Doppler compensation capabilities.
A method that determines the position, velocity, and trajectory of high-speed UEs to pre-compensate for Doppler shifts in communications by using aviation navigation systems and gateway devices, enabling effective Doppler compensation for both uplink and downlink transmissions.
This solution enables reliable air-to-ground communications for high-speed vehicles, overcoming the limitations of current specifications and allowing for high-speed connectivity in large cell networks.
Smart Images

Figure SE2024050514_05122024_PF_FP_ABST
Abstract
Description
METHOD TO PROVIDE SERVICE TO HIGH-SPEED USER EQUIPMENTSTECHNICAL FIELD
[0001] The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.BACKGROUND
[0002] Digitalizing airspace has become a topic of research and commercialization in 5G. Besides civil flight traffic, even national security and public safety (NSPS) and peace keeping and defense (PK&D) agencies are showing great interest in using / reusing terrestrial cellular network to also cover 3D.
[0003] Typical requirements are the support of 5G voice and data services (10-100 Mbit / s) to flying vehicles (drones, planes, etc.) with flight speeds up to 1200 km / h, in high altitude scenarios (3-12 km). Also, in mid altitude range (3-12 km) speeds up to 460 km / h are envisioned for unmanned aerial vehicles (UAVs, e.g., drones) and helicopters providing NSPS use cases such as situational awareness, goods transport / delivery, inspection and surveillance, etc.) and airtaxi services.
[0004] To ease network build-out and reduce control signaling such air-to-ground (ATG) networks typically are built with large cells of inter-site distance of around 100-300 km as indicated in 3GPP, RP-220962, "New WID: Air-to-ground network for NR:, CMCC and illustrated in Figure 1. In Figure 1, ISD is an abbreviation for inter-site distance.SUMMARY
[0005] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Various embodiments address the tradeoff between high speed UEs and cell range using a method for Doppler compensation that pre-compensates large Doppler shifts in communications.
[0006] According to some embodiments, a method of operating a UE is provided. The method includes determining a position of a base station. The method further includes determining a position of the UE, a velocity of the UE, and a trajectory of the UE. The method further includes determining a Doppler shift compensation for communications between the UE and the base station based on the position of the base station, the velocity of the UE, and the trajectory of the UE. The method further includes communicating with the base station by precompensating for Doppler shift based on the Doppler shift compensation.
[0007] According to other embodiments, a method performed by a gateway device is provided. The method includes determining a position of a base station. The method futherincludes determining a position of the user equipment, UE, a velocity of the UE, and a trajectory of the UE. The method further includes determining a Doppler shift compensation for communication between the UE and the base station based on the position of the base station, the position of the UE, the velocity of the UE, and the trajectory of the UE. The method further includes transmitting an indication of the Doppler shift compensation to the UE.
[0008] According to other embodiments, a network node, communication device, UE, gateway device, system, host, computer program, or computer program product is provided to perform one of the above methods.
[0009] Certain embodiments may provide one or more of the following technical advantage(s). ATG use-case is enabled for NSPS and PK&D high-speed vehicles overcoming the limits of current specifications.BRIEF DESCRIPTION OF THE DRAWINGS
[0010] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:
[0011] Figure 1 is an illustration of air-to-ground networks;
[0012] Figure 2 is an illustration of Doppler shift due to moving UEs;
[0013] Figure 3A is an illustration of a ground-based UE communicating with a satellite;
[0014] Figure 3B is an illustration of a UE in a flying vehicle pre-compensating for Doppler shift according to some embodiments;
[0015] Figure 4 is an illustration of Doppler compensation being directly done in a UE according to some embodiments;
[0016] Figure 5 is an illustration of distributed processing wherein Doppler calculations are computed in a gateway and Doppler compensation is performed in a UE according to some embodiments;
[0017] Figure 6 is a flow chart illustrating operations of a UE according to some embodiments;
[0018] Figure 7 is a flow chart illustrating operations of a gateway according to some embodiments;
[0019] Figure 8 is a block diagram of a communication system in accordance with some embodiments;
[0020] Figure 9 is a block diagram of a user equipment in accordance with someembodiments;
[0021] Figure 10 is a block diagram of a network node in accordance with some embodiments;
[0022] Figure 11 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments;
[0023] Figure 12 is a block diagram of a virtualization environment in accordance with some embodiments; and
[0024] Figure 13 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.DETAILED DESCRIPTION
[0025] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present / used in another embodiment.
[0026] There currently exist certain challenge(s). These typical requirements exceed what a 3GPP (3rd Generation Partnership Project) LTE (long term evolution) and NR (new radio) terrestrial system can provide today. The most challenging high-speed train use-case as standardized in 3GPP currently supports 500 km / h in Rel-18 and typically up to 350 km / h in earlier releases in cells or size 30km in a typical 2D scenario.
[0027] There is a strict limitation on UE (user equipment) velocity and cell maximum range (that corresponds to approximately half of the maximum inter-site distance ISD). The reason is that the random access procedure at a UE that the UE performs to register to the network cannot succeed due to too high Doppler shifts.
[0028] As an example, the range of Doppler shift in frequency range 1, FR1, (e.g., band n79; 5 GHz) is 5.6 kHz for 1200 km / h which doubles at the base-station due to DL (downlink) signal and UL (uplink) frequency errors, in total -11.6 kHz in Doppler. See Figure 2 where theDL Doppler shift and UL Doppler shift are illustrated for a base station (BS) transmitting a DL signal at a transmit frequency of DL TX frequency and being received at UE1 and UE2 at a frequency of DL RX frequency UE1 and RL RX frequency UE2, respectively. DL Doppler shift for UE1 and for UE2 can be seen as DL Doppler shifter UE1 and DL Doppler shift UE2, respectively. At a duplex distance from the reception frequency, UE1 and UE2 transmit a signal to the BS at a frequency of UL TX frequency UE1 and a frequency of UL TX frequency UE2, respectively. The UL signals are received at the BS at a frequency of UL RX frequency UE1 and a frequency of UL RX frequency UE2, respectively. The UL Doppler shift for UE1 and UE2 are illustrated as UL Doppler Shift UE1 and UL Doppler Shift UE2, respectively. Note that Figure 2 shows FDD (frequency division duplexing) to show duplex distancing. For TDD (time division duplexing), the same holds true but has a duplexing distance of 0 Hz.
[0029] Terrestrial 5G access procedures are not able to handle that large shift and such 5G networks today cannot provide service to high-velocity UEs (like air-planes, fast UAVs) in large cell ATG networks. As an example, in NR with a subcarrier spacing of 1.25 kHz or 5 kHz for a long physical random access channel (PRACH) preamble sequence, cell ranges up to 100 km are possible but are sensitive to Doppler and can handle shift notably lower than 11.6 kHz. Other sequences can handle higher Doppler, for example, format 0 and format 1 with a max Doppler for 2.3 kHz, but cell ranges are limited to 19 km (restricted set B) and 33 km (restricted set A).
[0030] Field tests have shown that PRACH pre-ample formats 1 for large cells with ISD up to 100 km can handle speeds of up to 250 km / h in a 5G ATG network.
[0031] In Figure 3A, the base station on-board the satellite 300 provides ephemeris data (trajectory) to the UE 900 (see Figure 9) for calculating Doppler compensation parameters by using its own GNSS (global navigation satellite system) position. In this case, even though the satellite is moving at around 20,000 km / hour, the trajectory of the satellite 300 is deterministic and can be calculated with great precision also for the future. The position of the UE 900 as determined by the integrated GNSS receiver is sufficient as UE speed is limited on the ground.
[0032] In the satellite case, the (relatively stationary) UE determines its own position with its own positioning means (e.g., GPS) and calculates the satellite's (high) speed, position, distance / delay from ephemeris data transmitted by the satellite to determine Doppler parameters. However, as previously indicated, terrestrial 5G access procedures are not able to handle large Doppler shifts of high-velocity UEs (like UEs on airplanes, UAVs, etc.) and such 5G networks today cannot provide service to high-velocity UEs in large cell air-to-ground networks.
[0033] In the case of, e.g., airplane UE (i.e., a UE on-board an airplane) to ground basestation communication, calculations are still with the UE (or its attached gateway device if present), but the UE now has to receive all needed data from other sources. The (stationary) base station position is obtained in the ways listed below, and the (high) speed and position of the UE needs to be obtained from the airplane’s systems since the normal UE means are not fast and / or accurate enough. A simple swap of roles such that the airplane transmits trajectory data to the base station and the base station knows or determines its own position and makes Doppler compensation accordingly does not work for the random access scenario because the decision to make a random access to the system is on the UE and the base station knows nothing about the UE until the UE has made the access attempt.
[0034] Figure 3B illustrates an embodiment where the UE 900 is a high-velocity UE as the UE 900 is on, within, or part of an air vehicle 310 such as an airplane, UAV (unmanned aerial vehicle), etc. In order for the UE to communicate to ground-based devices, base stations (BSs) positions are fixed and known (and limited in number) but need to be available to the UE 900 in the air in a secure way as this data is sensitive. The data can be stored in the UE's SIM / eSIM card or as a secret in a “gateway box” in order to protect the position data without being exposed over the air-interface Uu (which is also an option and should be protected as well). Transmission over the air interface is also an option but the information should be protected, e.g., with encryption. Secrecy is required against eavesdropping, but in a commercial scenario (as opposed to military) it might be desirable to keep the base station locations secret also from the air vehicle operator. The data can also be securely stored in the gateway-box by a trusted authority.
[0035] Additionally, the flight path of the UE 900 in the air vehicle 310 (e.g., airplane or UAV) is not deterministic and estimations / predictions of the flight path need to be of high quality to be useful. As the UE-integrated GNSS receiver signal is not sufficient, the air vehicle’s GNSS infrastructure needs to be used to give instantaneous and prediction flight path values for successful Doppler shift compensation and full radio coordination feature support.
[0036] Using the GNSS position and flight path data for speed / acceleration from the flying air vehicle 310, the UE 900 in the air can pre-compensate for the Doppler shift and enable PRACH access and data transmission even if cell ISDs and UE speed is high according to the embodiments described herein.
[0037] In a first embodiment illustrated in Figure 4, a specialized aviation gateway 400 connects to the aviation navigation system 402 to pull high quality position / trajectory data as well as base station locations from UE (e)SIM or a secret storage in the gateway 400 to perform calculations (distance / delay, velocity, Doppler UL / DL) and provide compensation information(e.g., Doppler UL / DL compensation data) to be handed to the UE PHY (physical layer) to compensate for Doppler shift illustrated as PRACH Doppler compensation execution.
[0038] The gateway 400 enables Doppler (pre-)compensation for uplink and downlink communication to allow for high-speed connectivity in large cells, by• Base station 1000 to advertise position information to UEs 900 via o A secret list in the eSIM / SIM (embedded subscriber identity module / subscriber identity module) card or a “gateway box” o In-band in Uu LI protocol (e.g., system information block (SIB))• UE 900 to gather position and velocity / trajectory information via o An interface to inject this data from external navigation system (e.g., airplane, vehicle, ...)• UE 900 or gateway box 400 to predict or control future UAV / plane trajectory (e.g., flight corridor) for some short time instance to allow PRACH operation.
[0039] The gateway 400 has an interface to a capable aviation navigation system 402 to read instantaneous positions and velocity data of the air vehicle 310, predication of flight trajectory of the air vehicle 310, and a method to influence a vehicle's flight path during RACH access and other related communication protocols. The gateway 400 also has an interface and secret storage to retrieve / store terrestrial network base station position data. The storage can be in USIM or eSIM (with update functionality over-the-air or local interface), be in the gateway 400, and receive the data via a data connection / interface.
[0040] The gateway 400 receives navigation data (e.g., position, velocity, trajectory, 3D velocity) (instantaneous data and prediction data) from the aviation navigation system 400 of the air vehicle 310.
[0041] The gateway 400 in some embodiments is implemented in a virtualization environment 1200 such as virtual network functions in a cloud environment outside (or a part) of the UE 900. In other embodiments, the gateway 400 is integrated into the UE 900.
[0042] Figure 5 illustrates an embodiment where the Doppler compensation is directly done in the UE 900 which determines the UE position data via an inbuilt high-performance GNSS receiver if available and either receives (over Uu) or retrieves (from (e)SIM) base station position data to calculate and (pre-) compensate for Doppler in UL / DL.
[0043] In some embodiments, if the inbuilt GNSS receiver is not of sufficient accuracy to obtain position of the high speed air vehicle 310, then the position of the UE (sometimes referred to herein as the UE position) can be determined from the aviation navigation system 402. Inorder get sufficient position and trajectory data for the fast-moving UE in such scenarios, an interface to the air vehicle's aviation navigation infrastructure is provided that the UE 900 or gateway 400 uses to overcome the lack of accuracy of UE-integrated GNSS receiver technology and to allow future prediction of flight path / corridor for optimum Doppler compensation during RACH events, hand-over events, etc. and data transmission.
[0044] In additional or alternative embodiments, the position of the UE (sometimes referred to herein as the UE position), the velocity of the UE (sometimes referred to herein as the UE velocity), or the trajectory of the UE (sometimes referred to herein as the UE trajectory) can be determined based on measurements of signals received from a plurality of base stations. In some examples, a position of a UE can be determined based on a triangulation of a set of signals transmit from a set of base stations. In additional or alternative embodiments, an indication of the UE position, the UE velocity, or the UE trajectory can be received from one or more base stations that are communicating with the UE.
[0045] Figure 6 illustrates operations the UE 900 performs in the embodiments described above. Turning to Figure 6, in block 601, the UE 900 determines (which may include obtaining) a position of a base station. The position in some embodiments is retrieved from a SIM / e-SIM card on the UE 900. In other embodiments, the position is received from the gateway 400 or securely advertised from the base station 1000).
[0046] In block 603, the UE 900 determines a UE position, a UE velocity, and a UE distance to a base station. The UE position, velocity, and distance may be received from the aviation navigation system 402 or when a gateway 400 is present, from the gateway 400.
[0047] In block 605, the UE 900 determiens a Doppler shift compensation for uplink transmissions and DL transmissions between the UE 900 and a base station 1000. When there is a gateway 400, the gateway 400 performs calculations based on the position, distance / delay and velocity to determine the Doppler shift. The gateway 400 then determines the Doppler UL compensation and the Doppler DL compensation, collectively Doppler UL / DL compensation and provides the Doppler UL / DL compensation to the PHY layer of the UE 900.
[0048] In embodiments where the UE 900 performs the calculations, the UE performs the calculations based on the navigation data received from the aviation navigation system 402. Calculating the Doppler shift can be determined bywhere c is the velocity of waves in the medium, vris the velocity of the receiver relative to themedium (positive if the receiver is moving towards the source and negative if in the opposite direction), vsis the velocity of the source relative to the medium (positive if the source is moving away from the receiver and negative if in the opposite direction), f is the observed frequency, and f0is the emitted frequency.
[0049] In some embodiments, the above formula can be simplified when a source or receiver is effectively stationary when one of the source or receiver is at a high speed. The Doppler shift can be determined bywhere v is the velocity of the high speed device.
[0050] The Doppler UL / DL compensation is then obtained based on the Doppler Shift and the trajectory of the air vehicle 310.
[0051] In block 607, the UE 900 communicates with the base station by pre-compensating for the Doppler shift in communications between the UE 900 and a base station 1000 based on the Doppler shift compensation. For example, for a trajectory of a UE 900 being traveling towards a base station, then the Doppler shift compensation moves up a transmit send time for an uplink signal to be received by the UE 900 at a designated time.
[0052] As can be seen from the foregoing, the various embodiments enable air-to ground communications for NSPS and PK&D high-speed vehicles overcoming limitations of current specifications.
[0053] Figure 7 illustrates operations that a gateway 400 performs in the embodiments described above. The gateway 400 may be a stand-alone device or integrated with the UE 900. Turning to Figure 7, in block 701, the gateway 400 determines (which is used herein to include calculating, receiving, or obtaining) a position of a base station. In some embodiments, the gateway 400 receives the position of the base station in a secure communication from a base station (1000). In other embodiments, the gateway 400 retrieves the position of the base station from a subscriber identify module, SIM, card in the UE 900. In yet other embodiments, the position of the base station is securely pre-stored in the gateway 400.
[0054] In block 703, the gateway 400 determines a user equipment, UE, position, a UE velocity, and a UE trajectory (e.g., a flight path of the UE, which can be referred to as the UE flight path) of a UE 900 to determine a UE distance to the base station. In some embodiments, the gateway 400 receieves the UE position, the UE velocity and the UE trajectory or UE flight path from an aviation navigation system 402.
[0055] In block 705, the gateway 400 determines a Doppler shift compensation for uplink communications and downlink communications. In some embodiments, the gateway 400 determines the Doppler shift by calculating a Doppler shift based on the UE velocity and calculating the Doppler shift compensation based on the Doppler shift and the UE trajectory.
[0056] In block 707, the gateway 400 transmits an indication of the Doppler shift compensation to the UE 900.
[0057] Figure 8 shows an example of a communication system 800 in accordance with some embodiments.
[0058] In the example, the communication system 800 includes a telecommunication network 802 that includes an access network 804, such as a radio access network (RAN), and a core network 806, which includes one or more core network nodes 808. The access network 804 includes one or more access network nodes, such as network nodes 810A and 810B (one or more of which may be generally referred to as network nodes 810), or any other similar 3rdGeneration Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 810 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 812A, 812B, 812C, and 812D (one or more of which may be generally referred to as UEs 812) to the core network 806 over one or more wireless connections.
[0059] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 800 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 800 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0060] The UEs 812 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 810 and other communication devices. Similarly, the network nodes 810 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 812 and / or with other network nodes or equipment in the telecommunication network 802 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 802.
[0061] In the depicted example, the core network 806 connects the network nodes 810 to one or more hosts, such as host 816. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 806 includes one more core network nodes (e.g., core network node 808) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 808. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).
[0062] The host 816 may be under the ownership or control of a service provider other than an operator or provider of the access network 804 and / or the telecommunication network 802, and may be operated by the service provider or on behalf of the service provider. The host 816 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0063] As a whole, the communication system 800 of Figure 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z- Wave, Near Field Communication (NFC) ZigBee, LiFi (Light Fidelity), and / or any low-power wide-area network (LPWAN) standards such as LoRa (Long Range) and Sigfox.
[0064] In some examples, the telecommunication network 802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 802. For example, the telecommunications network 802 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT (Internet of Things) services to yet further UEs.
[0065] In some examples, the UEs 812 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 804. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
[0066] In the example, the hub 814 communicates with the access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812C and / or 812D) and network nodes (e.g., network node 810B). In some examples, the hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 814 may be a broadband router enabling access to the core network 806 for the UEs. As another example, the hub 814 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 810, or by executable code, script, process, or other instructions in the hub 814. As another example, the hub 814 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 814 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 814 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 814 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0067] The hub 814 may have a constant / persistent or intermitent connection to the network node 81 OB. The hub 814 may also allow for a different communication scheme and / or schedule between the hub 814 and UEs (e.g., UE 812C and / or 812D), and between the hub 814 and the core network 806. In other examples, the hub 814 is connected to the core network 806 and / or one or more UEs via a wired connection. Moreover, the hub 814 may be configured to connect to an M2M service provider over the access network 804 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 810 while still connected via the hub 814 via a wired or wireless connection. In some embodiments, the hub 814 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 810B. In other embodiments, the hub 814 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 81 OB, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0068] Figure 9 shows a UE 900 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0069] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smartpower meter).
[0070] The UE 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input / output interface 906, a power source 909, a memory 910, a communication interface 912, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 9. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0071] The processing circuitry 902 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 910. The processing circuitry 902 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 902 may include multiple central processing units (CPUs).
[0072] In the example, the input / output interface 906 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 900. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
[0073] In some embodiments, the power source 908 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet),photovoltaic device, or power cell, may be used. The power source 908 may further include power circuitry for delivering power from the power source 908 itself, and / or an external power source, to the various parts of the UE 900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 908. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 908 to make the power suitable for the respective components of the UE 900 to which power is supplied.
[0074] The memory 910 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 910 includes one or more application programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916. The memory 910 may store, for use by the UE 900, any of a variety of various operating systems or combinations of operating systems.
[0075] The memory 910 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (U1CC) including one or more subscriber identity modules (SIMs), such as a US1M and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 910 may allow the UE 900 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 910, which may be or comprise a device-readable storage medium.
[0076] The processing circuitry 902 may be configured to communicate with an access network or other network using the communication interface 912. The communication interface 912 may comprise one or more communication subsystems and may include or becommunicatively coupled to an antenna 922. The communication interface 912 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 918 and / or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., antenna 922) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0077] In the illustrated embodiment, communication functions of the communication interface 912 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0078] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 912, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0079] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
[0080] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 900 shown in Figure 9.
[0081] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmit the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3 GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.
[0082] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0083] Figure 10 shows a network node 1000 in accordance with some embodiments. Asused herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
[0084] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0085] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0086] The network node 1000 includes a processing circuitry 1002, a memory 1004, a communication interface 1006, and a power source 1008. The network node 1000 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1000 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). Thenetwork node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1000.
[0087] The processing circuitry 1002 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 1000 components, such as the memory 1004, to provide network node 1000 functionality.
[0088] In some embodiments, the processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, the radio frequency (RF) transceiver circuitry 1012 and the baseband processing circuitry 1014 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.
[0089] The memory 1004 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1002. The memory 1004 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and / or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and memory 1004 is integrated.
[0090] The communication interface 1006 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, thecommunication interface 1006 comprises port(s) / terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. The communication interface 1006 also includes radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, the antenna 1010. Radio front-end circuitry 1018 comprises filters 1020 and amplifiers 1022. The radio front-end circuitry 1018 may be connected to an antenna 1010 and processing circuitry 1002. The radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002. The radio front-end circuitry 1018 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1020 and / or amplifiers 1022. The radio signal may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed to the processing circuitry 1002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0091] In certain alternative embodiments, the network node 1000 does not include separate radio front-end circuitry 1018, instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012, as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).
[0092] The antenna 1010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1010 may be coupled to the radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1010 is separate from the network node 1000 and connectable to the network node 1000 through an interface or port.
[0093] The antenna 1010, communication interface 1006, and / or the processing circuitry 1002 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and / or the processing circuitry1002 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0094] The power source 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein. For example, the network node 1000 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1008. As a further example, the power source 1008 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0095] Embodiments of the network node 1000 may include additional components beyond those shown in Figure 10 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000.
[0096] Figure 11 is a block diagram of a host 1100, which may be an embodiment of the host 816 of Figure 8, in accordance with various aspects described herein. As used herein, the host 1100 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1100 may provide one or more services to one or more UEs.
[0097] The host 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1104 to an input / output interface 1106, a network interface 1108, a power source 1110, and a memory 1112. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 9 and 10, such that the descriptions thereof are generally applicable to the corresponding components of host 1100.
[0098] The memory 1112 may include one or more computer programs including one or more host application programs 1114 and data 1116, which may include user data, e.g., data generated by a UE for the host 1100 or data generated by the host 1100 for a UE. Embodiments of the host 1100 may utilize only a subset or all of the components shown. The host application programs 1114 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.71 1), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1114 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1 100 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 1114 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
[0099] Figure 12 is a block diagram illustrating a virtualization environment 1200 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1200 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.
[0100] Applications 1202 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1200 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0101] Hardware 1204 includes processing circuitry, memory that stores software and / orinstructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1206 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1208 A and 1208B (one or more of which may be generally referred to as VMs 1208), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1206 may present a virtual operating platform that appears like networking hardware to the VMs 1208.
[0102] The VMs 1208 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1206. Different embodiments of the instance of a virtual appliance 1202 may be implemented on one or more of VMs 1208, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
[0103] In the context of NFV, a VM 1208 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1208, and that part of hardware 1204 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1208 on top of the hardware 1204 and corresponds to the application 1202.
[0104] Hardware 1204 may be implemented in a standalone network node with generic or specific components. Hardware 1204 may implement some functions via virtualization.Alternatively, hardware 1204 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1210, which, among others, oversees lifecycle management of applications 1202. In some embodiments, hardware 1204 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. Insome embodiments, some signaling can be provided with the use of a control system 1212 which may alternatively be used for communication between hardware nodes and radio units.
[0105] Figure 13 shows a communication diagram of a host 1302 communicating via a network node 1304 with a UE 1306 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 812A of Figure 8 and / or UE 900 of Figure 9), network node (such as network node 810A of Figure 8 and / or network node 1000 of Figure 10), and host (such as host 816 of Figure 8 and / or host 1 100 of Figure 11) discussed in the preceding paragraphs will now be described with reference to Figure 13.
[0106] Like host 1100, embodiments of host 1302 include hardware, such as a communication interface, processing circuitry, and memory. The host 1302 also includes software, which is stored in or accessible by the host 1302 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1306 connecting via an over-the-top (OTT) connection 1350 extending between the UE 1306 and host 1302. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1350.
[0107] The network node 1304 includes hardware enabling it to communicate with the host 1302 and UE 1306. The connection 1360 may be direct or pass through a core network (like core network 806 of Figure 8) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.
[0108] The UE 1306 includes hardware and software, which is stored in or accessible by UE 1306 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1306 with the support of the host 1302. In the host 1302, an executing host application may communicate with the executing client application via the OTT connection 1350 terminating at the UE 1306 and host 1302. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1350 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1350.
[0109] The OTT connection 1350 may extend via a connection 1360 between the host 1302 and the network node 1304 and via a wireless connection 1370 between the network node 1304and the UE 1306 to provide the connection between the host 1302 and the UE 1306. The connection 1360 and wireless connection 1370, over which the OTT connection 1350 may be provided, have been drawn abstractly to illustrate the communication between the host 1302 and the UE 1306 via the network node 1304, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
[0110] As an example of transmitting data via the OTT connection 1350, in step 1308, the host 1302 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1306. In other embodiments, the user data is associated with a UE 1306 that shares data with the host 1302 without explicit human interaction. In step 1310, the host 1302 initiates a transmission carrying the user data towards the UE 1306. The host 1302 may initiate the transmission responsive to a request transmitted by the UE 1306. The request may be caused by human interaction with the UE 1306 or by operation of the client application executing on the UE 1306. The transmission may pass via the network node 1304, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1313, the network node 1304 transmits to the UE 1306 the user data that was carried in the transmission that the host 1302 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1314, the UE 1306 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1306 associated with the host application executed by the host 1302.
[0111] In some examples, the UE 1306 executes a client application which provides user data to the host 1302. The user data may be provided in reaction to or response to the data received from the host 1302. Accordingly, in step 1316, the UE 1306 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 1306. Regardless of the specific manner in which the user data was provided, the UE 1306 initiates, in step 1318, transmission of the user data towards the host 1302 via the network node 1304. In step 1320, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1304 receives user data from the UE 1306 and initiates transmission of the received user data towards the host 1302. In step 1322, the host 1302 receives the user data carried in the transmission initiated by the UE 1306.
[0112] In an example scenario, factory status information may be collected and analyzed by the host 1302. As another example, the host 1302 may process audio and video data which mayhave been retrieved from a UE for use in creating maps. As another example, the host 1302 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1302 may store surveillance video uploaded by a UE. As another example, the host 1302 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1302 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.
[0113] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1350 between the host 1302 and UE 1306, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1302 and / or UE 1306. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1304. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1302. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1350 while monitoring propagation times, errors, etc.
[0114] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed byprocessing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0115] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.
Claims
24-05-202427CLAIMSWhat is claimed is:
1. A method performed by a user equipment, UE, (812A-812D, 900, 1202, 1304) comprising: determining (601) a position of a base station; determining (603) a position of the UE, a velocity of the UE, and a trajectory of the UE; determining (605) a Doppler shift compensation for communications between the UE and the base station based on the position of the base station, the velocity of the UE, and the trajectory of the UE; and communicating (607) with the base station by pre-compensating for Doppler shift based on the Doppler shift compensation.
2. The method of Claim 1, wherein determining the position of the base station comprises receiving an indication of the position of the base station via a secure communication from a gateway (400).
3. The method of Claim 1, wherein determining the position of the base station comprises retrieving an indication of the position of the base station from a subscriber identify module, SIM, card in the UE.
4. The method of Claim 3, wherein the SIM card comprises an embedded SIM, eSIM, card.
5. The method of any of Claims 1-4, wherein determining the position of the UE, the velocity of the UE, and the trajectory of the UE comprises receiving an indication of at least one of the position of the UE, the velocity of the UE, and the trajectory of the UE from a plurality of base stations.
6. The method of any of Claims 1-4, wherein determining the position of the UE, the velocity of the UE, and the trajectory of the UE comprises at least one of: receiving an indication of at least one of the position of the UE, the velocity of the UE, and the trajectory of the UE from a gateway (400); and receiving an indication of at least one of the position of the UE, the velocity of the UE, andthe trajectory of the UE from an aviation navigation system (402).
7. The method of any of Claims 1-6, wherein determining the Doppler shift compensation comprises: transmitting an indication of at least one of the position of the base station, the position of the UE, the velocity of the UE, and the trajectory of the UE to a gateway (400); and responsive to transmitting the indication of at least one of the position of the base station, the position of the UE, the velocity of the UE, and the trajectory of the UE to the gateway, receiving an indication of the Doppler shift compensation from the gateway.
8. The method of any of Claims 1-6, wherein determining the Doppler shift compensation comprises: determining a distance between the UE and the base station based on the position of the UE and the position of the base station; and determining the Doppler shift compensation based on the distance between the UE and the base station, the velocity of the UE, and the trajectory of the UE.
9. The method of any of Claims 1-8, wherein determining the Doppler shift compensation comprises: calculating a Doppler shift based on the velocity of the UE; calculating the Doppler shift compensation based on the Doppler shift and the trajectory of the UE.
10. The method of any of Claims 1-9, wherein the trajectory of the UE includes a predicted trajectory of the UE.
11. A method performed by a gateway device (400, 812A-812D, 900, 1202, 1304), the method comprising: determining (701) a position of a base station; determining (703) a position of the user equipment, UE, a velocity of the UE, and a trajectory of the UE; determining (705) a Doppler shift compensation for communication between the UE and the base station based on the position of the base station, the position of the UE, the velocity ofthe UE, and the trajectory of the UE; and transmitting (707) an indication of the Doppler shift compensation to the UE.
12. The method of Claim 11, wherein determining the position of the base station comprises receiving an indication of the position of the base station via a secure communication from a base station (1000).
13. The method of Claim 11, wherein determining the position of the base station comprises receiving the position of the base station from a subscriber identify module, SIM, card in the UE.
14. The method of Claim 13, wherein the SIM card comprises an embedded SIM, eSIM, card.
15. The method of Claim 11, wherein determining the position of the base station comprises retrieving the position of the base station from a securely stored location in the gateway device.
16. The method of any of Claims 11-15, wherein determining the position of the UE, the velocity of the UE, and the trajectory of the UE comprises receiving an indication of at least one of the position of the UE, the velocity of the UE, and the trajectory of the UE from the UE.
17. The method of any of Claims 11-16, wherein determining the position of the UE, the velocity of the UE, and the trajectory of the UE comprises receiving an indication of at least one of the position of the UE, the velocity of the UE, and the trajectory of the UE from an aviation navigation system (402).
18. The method of any of Claims 11-17, wherein determining the Doppler shift compensation comprises: determining a distance between the UE and the base station based on the position of the UE and the position of the base station; and determining the Doppler shift compensation based on the distance between the UE and the base station, the velocity of the UE, and the trajectory of the UE.
19. The method of any of Claims 11-18, wherein determining the Doppler shift compensation comprises:calculating a Doppler shift based on the UE velocity; calculating the Doppler shift compensation based on the Doppler shift and the UE trajectory.
20. The method of any of Claims 11-19, wherein the trajectory of the UE is a predicted trajectory of the UE.
21. A user equipment, UE, (812A-812D, 900, 1202, 1304) adapted to perform operations comprising: determining(601) a position of a base station; determining (603) a position of the UE, a velocity of the UE, and a trajectory of the UE; determining (605) a Doppler shift compensation for communications between the UE and the base station based on the position of the base station, the velocity of the UE, and the trajectory of the UE; and communicating (607) with the base station by pre-compensating for Doppler shift based on the Doppler shift compensation.
22. The UE of Claim 21 , the operations further comprising any of the operations of Claims 2- 10.
23. A computer program comprising program code to be executed by processing circuitry (902) of a user equipment, UE, (812A-812D, 900, 1202, 1304), whereby execution of the program code causes the UE to perform operations comprising: determining (601) a position of a base station; determining (603) a position of the UE, a velocity of the UE, and a trajectory of the UE; determining (605) a Doppler shift compensation for communications between the UE and the base station based on the position of the base station, the velocity of the UE, and the trajectory of the UE; and communicating (607) with the base station by pre-compensating for Doppler shift based on the Doppler shift compensation.
24. The computer program of Claim 23, the operations further comprising any of the operations of Claims 2-10.
25. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (902) of a user equipment, UE, (812A- 812D, 900, 1202, 1304), whereby execution of the program code causes the UE to perform operations comprising: determining (601) a position of a base station; determining (603) a position of the UE, a velocity of the UE, and a trajectory of the UE; determining (605) a Doppler shift compensation for communications between the UE and the base station based on the position of the base station, the velocity of the UE, and the trajectory of the UE; and communicating (607) with the base station by pre-compensating for Doppler shift based on the Doppler shift compensation.
26. The computer program product of Claim 25, the operations further comprising any of the operations of Claims 2-10.
27. A user equipment, UE, (812A-812D, 900, 1202, 1304) comprising: processing circuitry (902); and memory (910) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the UE to perform operations comprising: determining (601) a position of a base station; determining (603) a position of the UE, a velocity of the UE, and a trajectory of the UE; determining (605) a Doppler shift compensation for communications between the UE and the base station based on the position of the base station, the velocity of the UE, and the trajectory of the UE; and communicating (607) with the base station by pre-compensating for Doppler shift based on the Doppler shift compensation.
28. The UE of Claim 27, the operations further comprising any of the operations of Claims 2- 10.
29. A computer readable medium (910) having instructions stored therein that are executable by processing circuitry (902) of a user equipment, UE, (812A-812D, 900, 1202, 1304) to cause the UE to perform operations comprising: determining (601) a position of a base station; determining (603) a position of the UE, a velocity of the UE, and a trajectory of the UE; determining (605) a Doppler shift compensation for communications between the UE and the base station based on the position of the base station, the velocity of the UE, and the trajectory of the UE; and communicating (607) with the base station by pre-compensating for Doppler shift based on the Doppler shift compensation.
30. The computer readable medium of Claim 29, the operations further comprising any of the operations of Claims 2-10.
31. A gateway device (400, 812A-812D, 900, 1202, 1304) adapted to perform operations comprising: determining (701) a position of a base station; determining (703) a position of the user equipment, UE, a velocity of the UE, and a trajectory of the UE; determining (705) a Doppler shift compensation for communication between the UE and the base station based on the position of the base station, the position of the UE, the velocity of the UE, and the trajectory of the UE; and transmitting (707) an indication of the Doppler shift compensation to the UE.
32. The gateway device of Claim 31 , the operations further adapted to perform any of the operations of Claims 11-20.
33. A computer program comprising program code to be executed by processing circuitry (902) of a gateway device (400, 812A-812D, 900, 1202, 1304), whereby execution of the program code causes the gateway device to perform operations comprising: determining (701) a position of a base station; determining (703) a position of the user equipment, UE, a velocity of the UE, and a trajectory of the UE;determining (705) a Doppler shift compensation for communication between the UE and the base station based on the position of the base station, the position of the UE, the velocity of the UE, and the trajectory of the UE; and transmitting (707) an indication of the Doppler shift compensation to the UE.
34. The computer program of Claim 33, the operations further comprising any of the operations of Claims 12-20.
35. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (902) of a gateway device (400, 812A- 812D, 900, 1202, 1304), whereby execution of the program code causes the gateway device to perform operations comprising: determining (701) a position of a base station; determining (703) a position of the user equipment, UE, a velocity of the UE, and a trajectory of the UE; determining (705) a Doppler shift compensation for communication between the UE and the base station based on the position of the base station, the position of the UE, the velocity of the UE, and the trajectory of the UE; and transmitting (707) an indication of the Doppler shift compensation to the UE.
36. The computer program product of Claim 35, the operations further comprising any of the operations of Claims 12-20.
37. A gateway device (400, 812A-812D, 900, 1202, 1304) comprising: processing circuitry (902); and memory (910) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the gateway device to perform operations comprising: determining (701) a position of a base station; determining (703) a position of the user equipment, UE, a velocity of the UE, and a trajectory of the UE; determining (705) a Doppler shift compensation for communication between the UE and the base station based on the position of the base station, the position of the UE, the velocityof the UE, and the trajectory of the UE; and transmitting (707) an indication of the Doppler shift compensation to the UE.
38. The gateway device of Claim 37, the operations further comprising any of the operations of Claims 12-20.
39. A computer readable medium (910) having instructions stored therein that are executable by processing circuitry (902) of a gateway device (400, 812A-812D, 900, 1202, 1304) to cause the gateway device to perform operations comprising: determining (701) a position of a base station; determining (703) a position of the user equipment, UE, a velocity of the UE, and a trajectory of the UE; determining (705) a Doppler shift compensation for communication between the UE and the base station based on the position of the base station, the position of the UE, the velocity of the UE, and the trajectory of the UE; and transmitting (707) an indication of the Doppler shift compensation to the UE.
40. The computer readable medium of Claim 39, the operations further comprising any of the operations of Claims 12-20.
Citation Information
Patent Citations
GNSS-assisted wireless communication
US20200186236A1
Methods and system of frequency synchronization mechanisms for integration terrestrial network and non terrestrial network
WO2021163877A1
First network node, second network node, wireless device and methods performed thereby for handling doppler shift pre-compensation
WO2023038557A1
