Electronic device, infrastructure equipment and method

Abstract

An electronic device (UE) comprising circuitry configured to compensate for the effect of a common TA (T com ) in a transparent payload non-terrestrial network configuration of a feeder link pair of a non-terrestrial network component (NT-RN) and an infrastructure equipment (gNB) tethered by the non-terrestrial network component (NT-RN).

Description

Technical Field

[0001] This disclosure generally relates to entities and user equipment of mobile telecommunications systems, and more specifically to non-terrestrial networks (NTNs). Background Technology

[0002] Several generations of mobile telecommunications systems are known, such as the third generation (“3G”) based on the International Mobile Telecommunications-2000 (IMT-2000) specification, the fourth generation (“4G”) providing capabilities as defined in the International Mobile Telecommunications-Advanced Standard (IMT-Advanced Standard), and the current fifth generation (“5G”) providing a new air interface called the New Radio Access Technology (NR) system. 5G technology is based on 4G technologies, such as LTE, standardized under the control of 3GPP (“3rd Generation Partnership Project”). There exists a subsequent LTE-A (Advanced LTE) that allows for higher data rates than basic LTE, and it is also standardized under the control of 3GPP. LTE is based on previous generations of mobile communication technologies, such as second-generation (“2G”) GSM / EDGE (“Global System for Mobile Communications” / “Evolution of Enhanced Data Rates GSM”, also known as EGPRS) and third-generation (“3G”) UMTS / HSPA (“Universal Mobile Telecommunications System” / “High-Speed ​​Packet Access”) network technologies.

[0003] Since 5G systems are based on either LTE or LTE-A, the specific requirements of 5G technology are handled by the functions and methods already defined in the LTE and LTE-A standard documents.

[0004] The areas of current interest in 5G technology are referred to as the "Internet of Things" or simply IoT, as well as "Machine-to-Machine (M2M)" or "Machine-Type (MTC)" communication. 3GPP is developing technologies to support narrowband (NB)-IoT using LTE or 4G radio access interfaces and wireless infrastructure. These IoT devices are expected to be low-complexity and economical devices requiring infrequent communication with relatively low bandwidth data. It is also anticipated that a very large number of IoT devices will need to be supported within the cells of wireless communication networks.

[0005] See 3GPP TR38.821, “NR Solution for Supporting Non-Land Networks (NTN) (Revision 16)”, December 2019.

[0006] The technical report "Research on New Radio (NR) Supporting Non-Land Networks," 3GPP TR 38.811 V15.3.0 (2020-07), addresses the Non-Land Network (NTN) component of 5G systems. The NTN component in 5G systems relies on space / aircraft such as satellites to provide 5G service in unserved areas (remote / distant areas, airplanes or ships, high-speed trains, etc.) and service-deficient areas (e.g., suburban / rural areas) where terrestrial 5G networks cannot provide coverage. The NTN also enhances 5G service reliability by providing service continuity for M2M / IoT devices or ensuring service availability anywhere, especially for critical communications and future rail / sea / space communications, and enables 5G network scalability by providing efficient multicast / broadcast resources for data delivery to the network edge or even user terminals. The NTN component in 5G systems is expected to play a role in transportation, public safety, media and entertainment, e-health, energy, agriculture, finance, and automotive sectors.

[0007] Typically, in mobile communication networks such as 3G, 4G, and 5G, the time a user equipment (e.g., a mobile phone) is allowed to transmit traffic within a time slot is adjusted based on the distance between the UE and the base station (eNodeB, gNB) to address transmission delays and prevent interference with neighboring users. Timing advance (TA) is the variable that controls this adjustment. Generally, timing advance (TA) is the time the UE must advance its transmission so that the transmission arrives at the base station at the appropriate time within the uplink subframe, the start of which is aligned with the downlink subframe. This offset at the UE is necessary to ensure that downlink and uplink subframes are synchronized at the base station (gNB). The base station (gNB) continuously measures the timing of uplink signals from each UE and adjusts the uplink transmission timing by issuing a timing advance (TA) value to the corresponding UE. As long as the UE transmits some uplink data or signals (PUSCH / PUCCH / SRS), the gNB can estimate the uplink signal arrival time, which can then be used to calculate the required timing advance value.

[0008] Because the footprint size of non-terrestrial network (NTN) components is larger than that of normal terrestrial cells, the timing advance (TA) is expected to be larger than the typical TA in terrestrial networks, where cell size is much smaller. The technical specification "NR Solution Supporting Non-Terrestrial Networks (NTNs)," 3GPP TR 38.821 V16.0.0 (2019-12), describes the uplink timing advance / RACH procedure in section 6.3 and addresses aspects of maintaining UL timing advance and synchronization in this NTN cell in section 6.3.4, introducing a common TA and a UE-specific TA, the common TA being determined relative to a common reference point defined by the non-terrestrial network entity. However, improvements to the techniques for maintaining UL timing advance and synchronization are needed when involving non-terrestrial network (NTN) components. Summary of the Invention

[0009] According to a first aspect, this disclosure provides an electronic device comprising: circuitry configured to compensate for the impact of a power supply link on a public TA in a transparent payload non-terrestrial network configuration having non-terrestrial network components and infrastructure equipment tethered by the non-terrestrial network components.

[0010] According to another aspect, this disclosure provides an infrastructure device comprising: circuitry configured to provide information to a user equipment for compensating for the impact of a feeder link on the common TA in a transparent payload non-terrestrial network configuration having non-terrestrial network components and base stations tethered by the non-terrestrial network components.

[0011] According to another aspect, this disclosure provides a method comprising: compensating for the impact of a feeder link on a public TA in a transparent payload non-terrestrial network configuration having non-terrestrial network components and infrastructure equipment tethered by the non-terrestrial network components.

[0012] Other aspects are set forth in the dependent claims, the following description, and the accompanying drawings. Attached Figure Description

[0013] The embodiments are explained by way of example with respect to the accompanying drawings, in which:

[0014] Figure 1 The non-terrestrial network (NTN) is shown, in which space / aircraft vehicles transparently relay NR signals between the gNB and the UE;

[0015] Figure 2 An embodiment of uplink (UL) time synchronization in a transparent payload NTN scenario is illustrated schematically;

[0016] Figure 3aA first embodiment of a common TA process for compensating for changes at the UE in a transparent payload NTN is shown;

[0017] Figure 3b A variation of the first embodiment is shown, wherein the UE determines the common TA;

[0018] Figure 4a A second embodiment of the common TA process for compensating for variations in the transparent payload NTN is shown;

[0019] Figure 4b A variation of the second embodiment is shown, wherein the UE determines the common TA;

[0020] Figure 5 A third embodiment of the common TA process for compensating for variations in the transparent payload NTN is shown;

[0021] Figure 6 A fourth embodiment of the common TA process for compensating for variations in the transparent payload NTN is shown;

[0022] Figure 7 An example of determining TA adjustment based on the drift figure and direction sent from the network to the UE is shown;

[0023] Figure 8 An example representing ephemeris data is shown;

[0024] Figure 9 A schematic block diagram of the communication path between the UE and the gNB is shown; and

[0025] Figure 10 An embodiment of a controller for a UE, gNB, relay node, or non-terrestrial network component is shown. Detailed Implementation

[0026] Reference Figure 1 Before describing the embodiments in detail, some general explanations will be given first.

[0027] The embodiments described below disclose an electronic device comprising: circuitry configured to compensate for the impact of a feed link on the common TA in a transparent payload non-terrestrial network configuration having non-terrestrial network components and infrastructure equipment tethered by the non-terrestrial network components.

[0028] The electronic device can be a user equipment (UE). A UE can be any device associated with an end user or terminal for communication in systems such as Universal Mobile Telecommunications System (UMTS) and 3GPP Long Term Evolution (LTE or aLTE). In addition to legacy systems such as LTE, the UE can also support newer radio access technology systems and other improvements. A UE can also be a machine-type communication (MTC) terminal. A UE can also have relay functionality, where it forwards transmissions from other tethered UEs toward the network.

[0029] The circuitry of an electronic device may include at least one of the following: processor, microprocessor, dedicated circuit, memory, storage, radio interface, wireless interface, network interface, etc., such as typical electronic components included in user equipment such as mobile phones.

[0030] User equipment (UE) can also be an aviation UE. An aviation UE can be, for example, a UE provided within, on, or at an aircraft. An aviation device can be, for example, an unmanned aerial vehicle (UAV) (“UAV”) or an aircraft operating with varying degrees of autonomy, such as under the remote control of a human operator or autonomously operated by an onboard microcontroller. An aviation UE can be a mobile communication device configured to communicate data using a wireless access interface via the transmission and reception of signals representing data. In the context of this application, the term aviation UE is also used for electronic devices that operate autonomously or semi-autonomously within an aviation device without requiring a device operator (or “user”) located at or near the device. Therefore, the term user equipment (UE) also relates to devices where the user is located remotely.

[0031] The circuitry of the electronic device can be configured to absorb variations in the propagation time of the feed link as part of the UE-specific differential TA.

[0032] The circuitry of the electronic device can be configured to repeatedly adjust the UE-specific differential TA to account for varying distances between non-terrestrial network components and infrastructure equipment.

[0033] The circuitry of the electronic device can be configured to receive information about the ephemeris of non-terrestrial network components and the location of infrastructure equipment, and to repeatedly calculate the distance between the non-terrestrial network components and the infrastructure equipment based on that information.

[0034] The circuitry of the electronic device can be configured to receive information about the ephemeris of the non-terrestrial network component and the initial distance between the infrastructure equipment and the non-terrestrial network component, and to repeatedly calculate the distance between the non-terrestrial network component and the infrastructure equipment based on that information.

[0035] The circuitry of the electronic device can be configured to receive information about the location of the infrastructure equipment or the distance of the infrastructure equipment from non-terrestrial network components once the electronic device enters RRC connection mode and / or shortly after a power supply link switch occurs.

[0036] The circuitry of the electronic device can be configured to receive information in encrypted form about the location of infrastructure equipment or the distance of infrastructure equipment from non-terrestrial network components.

[0037] The circuitry of the electronic device can be configured to repeatedly receive the current TA adjustment and adjust the common TA based on that TA adjustment.

[0038] The circuitry of the electronic device can be configured to repeatedly determine the current TA adjustment based on the TA drift coefficient and its direction, and to adjust the common TA based on that TA adjustment.

[0039] The TA drift coefficient and its direction can include both the drift caused by the satellite's movement in its orbit and the displacement due to changes in its distance from tethered infrastructure equipment.

[0040] The circuitry of the electronic device can be configured to receive the TA drift coefficient and its direction as part of the RAR response in msg2 of a 4-step RACH or msgB of a 2-step RACH, or by a regular MAC message.

[0041] The embodiments also disclose a system comprising: an electronic device as defined in claim 1, ground-based infrastructure equipment, and a non-terrestrial network component configured to relay uplink and downlink traffic between user equipment and infrastructure equipment.

[0042] The embodiments also disclose an infrastructure device comprising: circuitry configured to provide information to user equipment for compensating for the impact of feeder links on public TAs in a transparent payload non-terrestrial network configuration having non-terrestrial network components and base stations tethered by the non-terrestrial network components.

[0043] Infrastructure equipment, also known as base stations or network elements, such as entities within the core network, enhanced Node Bs, or coordinating entities, can provide wireless access interfaces to one or more communication devices within a coverage area or cell. Infrastructure equipment can be, for example, any entity within a telecommunications system, such as entities within a new radio access technology system, such as a next-generation Node B.

[0044] The circuitry of infrastructure equipment may include at least one of the following: processor, microprocessor, dedicated circuit, memory, storage, radio interface, wireless interface, network interface, etc., such as typical electronic components included in a base station, such as a gNB.

[0045] The circuitry of infrastructure equipment can be configured to send ephemeris information about non-terrestrial network components to user equipment.

[0046] The circuitry of infrastructure equipment can be configured to send information to user equipment about the location of the infrastructure equipment tethered by non-terrestrial network components.

[0047] The circuitry of infrastructure equipment can be configured to send information to user equipment about the initial distance between the infrastructure equipment and non-terrestrial network components.

[0048] The circuitry of the infrastructure equipment can be configured to send information about the location of the infrastructure equipment or its distance from non-terrestrial network components to the user equipment once the electronic device enters RRC connection mode and / or shortly after a power supply link switch occurs.

[0049] The circuitry of infrastructure equipment can be configured to send information about the location of the infrastructure equipment or the distance of the infrastructure equipment from non-terrestrial network components in encrypted form to user equipment.

[0050] The circuitry of infrastructure equipment can be configured to repeatedly send current TA adjustments to user equipment.

[0051] The circuitry of infrastructure equipment can be configured to send the TA drift coefficient and its direction to user equipment.

[0052] The circuitry of the infrastructure equipment can be configured to include the TA drift coefficient and its direction as part of the RAR response in msg2 of a 4-step RACH or msgB of a 2-step RACH, or by a regular MAC message.

[0053] The embodiments also disclose a method comprising: compensating for the impact of a feeder link on a common TA in a transparent payload non-terrestrial network configuration having non-terrestrial network components and infrastructure equipment tethered by the non-terrestrial network components. This method may be computer-implemented.

[0054] The embodiments also disclose a computer program including instructions that, when executed by a processor, direct the processor to compensate for the impact of feeder links on common transport links (TAs) in a transparent payload non-terrestrial network configuration having non-terrestrial network components and infrastructure equipment tethered by the non-terrestrial network components. The embodiments also disclose a computer-readable medium storing the computer program.

[0055] The embodiments will now be described in more detail with reference to the accompanying drawings.

[0056] As stated in the introductory section of this application, the non-terrestrial network (NTN) component in a 5G system relies on space / aircraft (such as satellites) to provide 5G service in unserved or poorly served areas that cannot be adequately covered by terrestrial 5G networks. The purpose of the space / air network component is to provide a 5G service enabler to user equipment (UE) such as handheld devices.

[0057] This space / airborne network is considered to be configured with base station functionality (next-generation Node B, or gNB) on a space / airborne vehicle. This scenario is called "Regenerative Payload NTN". Other scenarios exist where the space / airborne vehicle only transparently relays NR signals between the gNB and the UE. In this latter scenario (also known as "Transparent Payload" or "Bend Payload"), there is no base station functionality on the space / airborne vehicle.

[0058] Generally, the term "feed link" refers to the radio link between the space / air platform and the gateway connecting the satellite or aeronautical access network to the core network, and the term "service link" refers to the radio link between the user equipment (UE) and the space / air platform. In addition to the service link to the space / air platform, the UE can also support radio links with the terrestrial RAN.

[0059] Figure 1 This illustrates a non-terrestrial network (NTN) in which a space / aircraft relays NR signals transparently between the gNB and the UE. The non-terrestrial network device NT-RN (e.g., a space / aircraft, such as a satellite) includes the functionality to relay NR signals between the UE and the terrestrial next-generation Node B gNB via the Un interface. The gNB communicates with the NG core component (NGC), specifically the core data network. Here, the gNB includes the functionality of an NTN gateway acting as a router interfacing with the NGC. Through the non-terrestrial network device NT-RN, the gNB provides NR user plane and control plane protocol terminals to the UE and connects to the NG core (NGC) via the NG interface.

[0060] Here, Un interface refers to the radio interface between the UE and gNB via the non-terrestrial network device NT-RN. Furthermore, NGc refers to the control plane interface between the gNB and NGC, and NGu refers to the user plane interface between the gNB and NGC.

[0061] Transparent Mode NTN Configuration

[0062] In such Figure 1In the described transparent mode NTN configuration, space / air network components (e.g., satellites) are transparent to the UE, and the one-way propagation delay from the UE to the gNB incorporates the feed link connecting the satellite to the terrestrial gNB. Since the length of this feed link varies due to satellite orbital movement and occasional feed link switching, this needs to be reflected in the timing adjustments between the UE and the gNB.

[0063] Figure 2 This diagram schematically illustrates an embodiment of uplink (UL) time synchronization in a transparent payload NTN scenario. A terrestrial gNB provides NR user plane and control plane protocol terminals to user equipment UE1, UE2, ..., UEx via a non-terrestrial (space / air) network component (e.g., satellite) NT-RN. The non-terrestrial network component NT-RN acts as a non-terrestrial relay node NT-RN and relays uplink and downlink signals from and to the gNB for user equipment UE1, UE2, ..., UEx within its service area 20 (the coverage area of ​​the spot beam of the space / air network component NT-RN). For this purpose, the space / air network component NT-RN is connected to the gNB via an NG interface.

[0064] Knowing the ephemeris of the non-terrestrial network component (satellite) NT-RN and the location of the gNB, the network NGC calculates a common timing adjustment (TA). All UEs within a given service area 20 can use this common TA to advance their UL transmissions so that, at the gNB, all UL receive frames and DL transmit frames can be aligned.

[0065] Public timed adjustment (public TA)T com Defined as the delay between gNB and reference point RP defined in beam coverage area 20:

[0066] T com =2×(D 01 +D 02 ) / c

[0067] Among them, D 01 D is the distance between the reference point RP and the space / airborne relay node NT-RN. 02 It is the distance between the space / airborne network relay node NT-RN and the gNB, where c is the speed of light. This public TAT com It can be viewed as the average delay between the gNB and all locations of the UE within the coverage area 20 of the dot beam.

[0068] The reference point RP can be considered, for example, as the center of the beam coverage area 20 on the Earth's surface. Specifically, the common TA reference point can be defined, for example, as the ground-based center of the beam coverage area when the satellite is at its zenith. This can be calculated by the network, as it knows the satellite's ephemeris and the general beam coverage area. If the reference point is on Earth, any UE that happens to be in the air (e.g., a passenger's UE on an airplane) will generally be closer to the space / airborne network component than the common TA reference point. For such UEs, their UE-specific differential TA will be negative. To ensure that the differential TA of all UEs (including airborne UEs) is always positive, the reference point RP can be defined at an airborne location above the beam center on Earth. The altitude of this location can, for example, be a predetermined maximum altitude to which a known UE could potentially ascend, e.g., the highest altitude an airplane can fly (e.g., 15,000 km above sea level).

[0069] There are several ways to determine public TAT com For example, the network can calculate the common TA and broadcast it within the beam, for example, in system information. Alternatively, in connected mode, the network can send the common TA to the UE via MAC signaling (e.g., a MAC CE message). Furthermore, knowing the common TA reference point of its beam and the current satellite location (through knowledge of ephemeris), the UE can calculate the common TA itself. If the UE must calculate the common TA, the location of the common TA reference point can be broadcast to the UE, for example, via system information (specifically to all UEs within the beam coverage area), so that the UE knows the reference point for calculating the common TA. Ephemeris data can be provided to the UE according to the principles described in section 7.3.6.2 of 3GPP TR 38.821 V16.0.0, which is discussed below. Figure 8 These principles are outlined in the corresponding descriptions.

[0070] Each UE should derive a UE-specific differential delay adjustment T related to the propagation time between the x-th UE and the reference point of the public TA. UEx (For the xth UE):

[0071] T UEx =2×(D 1x —D 01 ) / c

[0072] Among them, D 01 D is the distance between reference point RP and gNB. 1xLet be the distance between the gNB and the x-th UE, and c be the speed of light. Since the beam coverage area of ​​the NTN component is larger than that of a normal terrestrial cell, it is expected that even the UE-specific differential TA will be larger than the typical TA in a terrestrial network, where the cell size is much smaller. A UE capable of positioning itself, knowing its own location and the reference point RP of its public TA, can use its differential delay T. UEx The propagation time to the common TA reference point is calculated. Alternatively, a network that knows the UE's location (e.g., reported by a UE capable of location) can also calculate the propagation time from the UE to the common TA reference point RP, and the network also knows the common TA reference point RP for any of its current beams. The network can then send this propagation time to the UE in connected mode. Even more alternatively, the UE can perform a RACH and then receive its differential TA from the RAR. For this RACH, the UE must advance the transmission time of its RACH transmission to the common TA. Therefore, the UE needs to know the value of the common TA before it can derive its differential TA via the RACH.

[0073] From UE-specific differential delay T UEx and public timed adjustment T com Obtain the full TAT for each UE full :

[0074] T full =T com +T UEx

[0075] Then the full TAT full It can be used by the UE to maintain UL timing advance and synchronization in the NTN cell.

[0076] The common TA of the varying transparent payload NTN

[0077] In a regenerable payload NTN, the gNB (or its distributed unit gNB-DU) is on the satellite, and therefore, the common TA is essentially the satellite's altitude above the reference point. This depends primarily on the satellite's orbital altitude, and therefore for a given beam or satellite, this altitude is largely fixed, meaning that the common TA does not change significantly over time. However, in Figure 1In the transparent payload NTN shown, the gNB is located on the ground, and the common TA depends on both the satellite altitude and the propagation delay between the satellite and the land-based gNB. This second component changes as the satellite describes its orbit, and therefore the common TA also changes. The embodiments described below address in more detail how to deal with this aspect of the changing common TA in the transparent payload NTN, which changes due to: (a) the changing distance caused by the satellite orbit between the gNB and the satellite, or (b) a feeder link handover. When a feeder link handover occurs, the network switches its connection to the UE from the current serving gateway to another target gateway. The distance between the target gateway and the satellite may differ from the distance between the original serving gateway and the satellite.

[0078] Figure 3a A first embodiment of the process for compensating for changes in the public TA at the UE in the transparent payload NTN is shown. At 31, the UE receives the public TA from the network, information about the satellite's ephemeris, and the location of the serving gNB tethered by the satellite. At 32, the UE determines the UE-specific differential TA. This can occur according to any of the methods described above (depending on the chosen method for determining the UE-specific differential TA, the network can provide...) Figure 3a Additional information not shown in the text, such as the location of the reference point RP, UE-specific propagation time, etc.). Knowing the satellite's ephemeris and therefore its orbital velocity, at point 33, the UE calculates the satellite's location based on the information about the satellite's ephemeris. This calculation of satellite location based on information about the satellite's ephemeris can be performed according to the principles set forth in Appendix A of 3GPP TR 38.821 VI 6.0.0, which is incorporated herein by reference. At point 34, the UE calculates the distance between the satellite and its tethered gNB based on the satellite's position and the gNB's position. Based on this distance between the satellite and its tethered gNB, at point 35, the UE adjusts its UE-specific differential TA (e.g., in each UL transmission) to account for any changes in the distance between the satellite and its tethered gNB. At point 36, the UE determines the full TA based on the (constant) common TA obtained from the network and based on the adjusted UE-specific differential TA. The UE then uses the full TA to maintain UL timing advance and synchronization in the NTN cell. Figure 3a As indicated by the arrows, steps 33, 34, 35, and 36 are repeated when the UE is within the spot beam of the satellite and therefore within the service area of ​​the gNB tethered by the satellite.

[0079] In this embodiment, the common TA remains constant, while variations in the feed link propagation time are absorbed as part of the UE-specific differential TA. The location of the serving gNB can be provided once the UE enters RRC connection mode and / or shortly after a feed link handover. The location of the serving gNB can be provided to the UE, for example, in MAC signaling (e.g., MAC control element (MAC CE)). In RRC connection mode, the gNB location information can be encrypted, and this information is transmitted in encrypted user plane packets or protected RRC signaling. Ephemeris data can be provided to the UE according to the principles described in section 7.3.6.2 of 3GPP TR 38.821 V16.0.0, as discussed below. Figure 8 The corresponding descriptions outline these principles.

[0080] exist Figure 3a In one embodiment, at point 31, the UE receives a public TA from the network. Figure 3b A variation of the first embodiment is shown. In this variation, the UE does not receive the common TA from the network. Instead, at 31a, the UE receives information from the network about the satellite's ephemeris and the gNB's location. At 31b, the UE determines the common TA based on the information about the satellite's ephemeris and the gNB's location, and then follows the... Figure 3a The same steps 33 to 36 are used in the embodiments.

[0081] Figure 4a A second embodiment of the process for compensating for changes in the common TA in a transparent payload NTN is shown. At 41, the UE receives the common TA from the network, information about the satellite's ephemeris, and the initial distance between the satellite and the serving gNB tethered by the satellite. At 42, the UE determines the UE-specific differential TA. Knowing the satellite's ephemeris and therefore its orbital velocity, at 43, the UE calculates the distance between the satellite and the gNB based on the initial distance between the satellites and the information about the satellite's ephemeris. Based on this distance between the satellite and its tethered gNB, at 44, the UE adjusts its UE-specific differential TA (e.g., in each UL transmission) to account for any changes in the distance between the satellite and its tethered gNB. At 45, the UE determines its full TA based on the (constant) common TA obtained from the network and based on the adjusted UE-specific differential TA. The UE then uses the full TA to maintain UL timing advance and synchronization in the NTN cell. Figure 4a As indicated by the arrows, steps 43, 44, and 45 are repeated when the UE is within the spot beam of the satellite and thus within the service area of ​​the gNB tethered by the satellite.

[0082] like Figure 3a The embodiments are also in Figure 4aIn this embodiment, the common TA remains constant, while variations in the feeder link propagation time are absorbed as part of the UE-specific differential TA. The service gNB distance can be provided to the UE once the UE enters RRC connection mode and shortly after a feeder link handover. The location of the service gNB can be provided to the UE, for example, in the MAC control element (MAC CE). In RRC connection mode, the gNB distance information can be encrypted.

[0083] exist Figure 4a In one embodiment, at point 41, the UE receives a public TA from the network. Figure 4b A variation of this second embodiment is shown. In this variation, the UE does not receive the common TA from the network. Instead, at 41a, the UE receives information from the network about the satellite's ephemeris and the distance to the gNB. At 41b, the UE determines the common TA based on the information about the satellite's ephemeris and the gNB's location, and then follows the... Figure 4a The same steps 43 to 45 are used in the embodiments.

[0084] Figure 5 A third embodiment of the process for compensating for changes in the common TA in a transparent payload NTN is shown. At 51, the UE receives the common TA from the network. At 52, the UE determines its UE-specific differential TA. At 53, the UE in connected mode regularly receives a common TA adjustment message. This message carries a common TA adjustment calculated by the network, which is caused by normal orbital movement of the satellite or a feed link switch. Because this signaling is UE-specific and there may be many UEs within a large coverage area of ​​a specific point beam, it consumes significant resources. At 54, the UE adjusts the common TA based on the common TA adjustment received from the network. At 55, the UE determines its full TA based on the adjusted common TA and its UE-specific differential TA. The UE then uses the full TA to maintain UL timing advance and synchronization in the NTN cell. Figure 5 As indicated by the arrows, steps 53, 54, and 55 are repeated when the UE is within the spot beam of the satellite and therefore within the service area of ​​the gNB tethered by the satellite.

[0085] Adjusted public TAT com, adjusted It can be, for example, based on the constant public TAT initially received from the network, according to the following formula. com And adjust T based on the corresponding current TA repeatedly received from the network. adjust To determine:

[0086] T com, adjusted =T com +T adjust

[0087] Figure 6A fourth embodiment of the process for compensating for changes in the common TA in a transparent payload NTN is shown. At 61, the UE receives the common TA, TA drift coefficients, and their directions from the network. The drift coefficients and drift directions are derived by the network from satellite ephemeris information. TA drift includes both drift due to the movement of the satellite in its orbit and displacement due to changes in its distance to the serving gNB calculated by the network. The network may, for example, send the TA drift coefficients and their directions as part of the RAR response in msg2 of a 4-step RACH or msgB of a 2-step RACH, or via a regular MAC message to the UE. At 62, the UE determines its UE-specific differential TA. At 63, the UE determines the current TA adjustment based on the drift coefficients and directions obtained from the network. At 64, the UE adjusts the common TA based on the current TA adjustment obtained from the drift coefficients and directions. At 65, the UE determines its full TA based on the adjusted common TA and its UE-specific differential TA. The UE then uses the full TA to maintain UL timing advance and synchronization in the NTN cell. Figure 6 As indicated by the arrows, steps 63, 64, and 65 are repeated when the UE is within the spot beam of the satellite and thus within the service area of ​​the gNB tethered by the satellite.

[0088] This implementation scheme is applicable to all types of satellite orbits, including elliptical orbits, and allows the UE to have three components in its TA adjustment: common TA, TA drift, and UE-specific differential TA. Regarding the drift coefficient and direction, the signaling is UE-specific, but the drift coefficient and direction can be compared to... Figure 5 The implementation scheme provides the signaling to the UE at a lower frequency. Therefore, this signaling is compared to... Figure 5 The signaling in the embodiment consumes fewer resources.

[0089] exist Figure 6 In one embodiment, the UE receives the TA drift coefficient and its direction from the network. In an alternative embodiment, the UE will only receive the TA drift coefficient from the network, and the UE will determine the drift direction from the ephemeris.

[0090] Figure 7 An example is shown of determining the TA adjustment based on the drift coefficient and direction (or the drift direction determined by the UE from ephemeris) transmitted from the network to the UE, as described in process step 62 of the fourth embodiment above. In this example, for example, the drift coefficient and direction ΔT com / Δt=+2 μs / 10 ms=+0.0002 is sent from the network to the UE. The drift coefficient 0.0002 indicates the amount of TA drift, while the plus sign indicates the direction of TA drift (here: TA drift increases with time). The graph shows the common TA in microseconds (μs) on the vertical axis and time in milliseconds (ms) on the horizontal axis. The solid line shows the common TA as calculated by the UE based on the drift coefficient and direction obtained from the network. com, adjusted The adjusted public TAT com, adjusted For example, based on the following formula, the time t, drift coefficient, and direction ΔT can be used... com / Δt and the scheduled fixed public TAT received from the network com To determine:

[0091] T com, adjusted =T com + (ΔT) com / Δt)×t

[0092] The above embodiments all solve the problem of the impact of the power supply link on the common TA, and thus can maintain UL timing advance and synchronization in the NTN cell.

[0093] Ephemeris data for NTN

[0094] Ephemeris data used for NTN is processed in more detail in section 7.3.6 of 3GPP TR 38.821 V16.0.0, which is incorporated herein by reference. Ephemeris data may contain information about the orbital trajectory of artificial satellites, as described, for example, in Appendix A of 3GPP TR 38.821 V16.0.0. Different possible representations of ephemeris data exist.

[0095] Figure 8 This illustrates one possibility for representing ephemeris data. According to this example, orbital parameters such as semi-major axis α, eccentricity e, inclination i0, right ascension Ω0 of the ascending node, argument ω of the pericenter, mean anomaly Mo at the reference time point, and epoch t are used. 06 The first five parameters determine the orbital plane, and the other two are used to determine the exact satellite position at a given time. The description table and corresponding diagrams of the orbital parameters are as follows:

[0096]

[0097] However, the embodiments are not limited to this representation of ephemeris data. Another possible option is to provide the satellite's position in coordinates (x, y, z), such as ECEF coordinates. Furthermore, velocity vectors (vx, vy, vz) and again, a reference time point can be provided.

[0098] Ephemeris data can be provided to the UE according to the principles outlined in Section 7.3.6.2 of 3GPP TR 38.821 V16.0.0. Providing ephemeris data, or portions thereof, from the network to the UE can be done via a memory card, such as a uSIM. However, the UE does not need to store the orbital parameters of all satellites. If the orbital parameters of each satellite are pre-provided, the UE only needs to store the ephemeris data of the satellites that can serve the UE. Another possible solution is to broadcast the orbital parameters of the serving satellite and a few neighboring satellites, which would be sufficient for initial access and mobility processing on the UE side.

[0099] The means of updating ephemeris data stored in the UE are foreseeable, such as those described in section 7.3.6.3 of 3GPP TR 38.821V16.0.0, which is incorporated herein by reference.

[0100] Given a specific point in time, it is straightforward to calculate the satellite position according to the principles set forth in Appendix A of 3GPP TR 38.821 V16.0.0, which is incorporated herein by reference.

[0101] Implementation

[0102] Figure 9 A schematic block diagram of the communication path between UE 800, non-terrestrial (space / air) relay node NT-RN 820 (e.g., satellite), and gNB 830 is shown. Figure 9 As shown, the UE includes a transmitter 801, a receiver 802, and a controller 803 to control the transmission of signals to and from the gNB. Uplink signals are indicated by arrow 860. Downlink signals are indicated by arrow 850. The space / air relay node RT-RN 820 includes a transmitter 821, a receiver 822, and a controller 823. The RT-RN 820 may include functionality for relaying downlink and uplink signals between the UE 800 and the gNB 820 according to the radio access interface. The gNB 830 includes a transmitter 831, a receiver 832, and a controller 833. The gNB 830 may include a scheduler for scheduling the transmission and reception of signals on the downlink and uplink according to the radio access interface.

[0103] Figure 10 An embodiment of controller 900 is described. This controller 900 can be implemented such that it can be used substantially as any type of device or entity as described herein, a base station, a relay node, a transmitting and receiving point, or a user equipment. Controller 900 can therefore act as… Figure 9The controller 900 has components 931 to 940 that can form circuits, such as any of the circuits of entities, base stations, and user equipment as described herein.

[0104] Examples of embodiments using software, firmware, programs, etc. to perform the methods described herein may be installed on controller 900 and then configured to suit a particular embodiment.

[0105] The controller 900 has a CPU 931 (central processing unit) that can execute various types of programs and methods as described herein, such as programs stored in read-only memory (ROM) 932, programs stored in memory 937 and loaded into random access memory (RAM) 933, programs stored in medium 940 that can be inserted into a corresponding driver 939, etc.

[0106] CPU 931, ROM 932, and RAM 933 are connected to bus 941, which in turn is connected to input / output interface 934. The number of CPUs, memory, and storage devices is merely exemplary, and those skilled in the art will understand that controller 900 can be adapted and configured accordingly to meet the specific requirements that arise when it is used as a base station and user equipment.

[0107] At the input / output interface 934, several components are connected: input 935, output 936, memory 937, communication interface 938, and driver 939. Media 940 (compressed disc, digital video disc, compact flash memory, etc.) can be inserted into them.

[0108] Input 935 can be a pointing device (mouse, chart, etc.), keyboard, microphone, camera, touchscreen, etc. Output 936 can be a display (LCD, CRT, LED, etc.), speaker, etc. Memory 937 can be a hard disk, solid-state drive, etc.

[0109] The communication interface 938 can be adapted to communicate via, for example, a local area network (LAN), a wireless local area network (WLAN), a mobile telecommunications system (GSM, UMTS, LTE, etc.), Bluetooth, infrared, etc. When the controller 900 is used as a base station, the communication interface 938 may also have a corresponding air interface (providing, for example, E-UTRA protocol OFDMA (downlink) and SC-FDMA (uplink)) and a network interface (e.g., implementing protocols such as S1-AP, GTP-U, S1-MME, X2-AP, etc.). Furthermore, the controller 900 may have one or more antennas and / or antenna arrays. This disclosure is not limited to any characteristics of such protocols.

[0110] It should be understood that the embodiments describe an exemplary ordering of method steps. However, the specific ordering of method steps is given for illustrative purposes only and should not be construed as binding. For example, it can be changed... Figure 3b The ordering of process steps 31b and 32 in the method. Other changes to the ordering of method steps may be obvious to those skilled in the art.

[0111] It should also be noted that... Figure 10 The division of the control or circuitry into units 931 to 940 is for illustrative purposes only, and this disclosure is not limited to any particular functional division within any particular unit. For example, at least a portion of the circuitry may be implemented by a suitable programming processor, a field-programmable gate array (FPGA), a dedicated circuit, etc.

[0112] Unless otherwise stated, all units and entities described in this specification and claimed in the appended claims may be implemented as, for example, integrated circuit logic on a chip, and unless otherwise stated, the functionality provided by such units and entities may be implemented by software.

[0113] As with the implementation of the embodiments of the present disclosure using at least part of a software-controlled data processing apparatus, it will be understood that the computer program providing this software control, and the transmission, memory or other medium through which this computer program is provided, are contemplated as aspects of the present disclosure.

[0114] Note that this technology can also be configured as follows:

[0115] (1) An electronic device (UE) comprising: a transparent payload non-terrestrial network (NTN) configuration having a non-terrestrial network component (NT-RN) and an infrastructure device (gNB) tethered by the non-terrestrial network component (NT-RN) to compensate for the impact on the public TA (T) in a transparent payload non-terrestrial network (NTN) configuration. com The circuit is affected by the power supply link.

[0116] (2) The electronic device (UE) according to (1), wherein the circuit is configured to use the change in the propagation time of the feed link as a UE-specific differential TA (T UEx It absorbs a portion of the nutrients.

[0117] (3) The electronic device (UE) according to (1) or (2), wherein the circuit is configured to repeatedly adjust (35, 44) the UE-specific differential TA (T) UEx This takes into account the varying distances between non-terrestrial network components (NT-RN) and infrastructure equipment (gNB).

[0118] (4) An electronic device (UE) according to any one of (1) to (3), wherein the circuit is configured to receive (31) information about the ephemeris of the non-terrestrial network component (NT-RN) and the location of the infrastructure equipment (gNB), and to repeatedly calculate (33, 34) the distance between the non-terrestrial network component (NT-RN) and the infrastructure equipment (gNB) based on the information.

[0119] (5) An electronic device (UE) according to any one of (1) to (4), wherein the circuit is configured to receive (41) information about the ephemeris of the non-terrestrial network component (NT-RN) and the initial distance between the infrastructure equipment (gNB) and the non-terrestrial network component (NT-RN), and to repeatedly calculate (43) the distance between the non-terrestrial network component (NT-RN) and the infrastructure equipment (gNB) based on the information.

[0120] (6) An electronic device (UE) according to any one of (1) to (5), wherein the circuit is configured to receive (31) information about the location of the infrastructure device (gNB) or information about the distance of the infrastructure device (gNB) from the non-terrestrial network component (NT-RN) once the electronic device (UE) enters the RRC connection mode and / or shortly after the power supply link switch occurs.

[0121] (7) An electronic device (UE) according to any one of (1) to (6), wherein the circuit is configured to receive (31) information in encrypted form about the location of the infrastructure device (gNB) or about the distance of the infrastructure device (gNB) from the non-terrestrial network component (NT-RN).

[0122] (8) An electronic device (UE) according to any one of (1) to (7), wherein the circuit is configured to repeatedly receive (53) the current TA adjustment (T adjust ), and adjustments based on that TA (T) adjust To adjust (54) public TA (T) com ).

[0123] (9) An electronic device (UE) according to any one of (1) to (8), wherein the circuit is configured to adjust according to the TA drift coefficient and its direction ΔT com / Δt to repeatedly determine (63) the current TA adjustment ((ΔT) com / Δt)×t), and adjust (T) according to this TA. adjust To adjust (64) public TA (T) com ).

[0124] (10) According to the electronic device (UE) of (9), wherein the TA drift coefficient and its direction (ΔT)com / Δt) includes both the drift caused by the satellite’s movement in its orbit and the displacement caused by changes in its distance from the tethered infrastructure equipment (gNB).

[0125] (11) The electronic device (UE) according to (9) or (10), wherein the circuit is configured to receive the TA drift coefficient and its direction as part of the RAR response in msg2 of 4-step RACH or msgB of 2-step RACH or by a regular MAC message.

[0126] (12) A system comprising: an electronic device (UE) as defined in any one of (1) to 12, a ground-based infrastructure device (gNB), and a non-terrestrial network component (NT-RN) configured to relay uplink and downlink traffic between the user equipment (UE) and the infrastructure device (gNB).

[0127] (13) An infrastructure device (gNB; NTC) comprising: information configured to provide information to a user equipment (UE) for compensating for public TA (T) in a transparent payload non-terrestrial network (NTN) configuration having a non-terrestrial network component (NT-RN) and a base station (gNB) tethered by the non-terrestrial network component (NT-RN). com The circuit is affected by the power supply link.

[0128] (14) The infrastructure equipment (gNB; NTC) according to (13), wherein the circuit is configured to send ephemeris information about the non-terrestrial network component (NT-RN) to the user equipment (UE).

[0129] (15) The infrastructure device (gNB; NTC) according to (13) or (14), wherein the circuit is configured to send information to the user equipment (UE) about the location of the infrastructure device (gNB) tethered by the non-terrestrial network component (NT-RN).

[0130] (16) An infrastructure device (gNB; NTC) according to any one of (13) to (15), wherein the circuit is configured to send information to the user equipment (UE) about the initial distance between the infrastructure device (gNB) and the non-terrestrial network component (NT-RN).

[0131] (17) An infrastructure device (gNB; NTC) according to any one of (13) to (16), wherein the circuit is configured to send information to the user equipment (UE) about the location of the infrastructure device (gNB) or about the distance of the infrastructure device (gNB) from the non-terrestrial network component (NT-RN) once the electronic device (UE) enters RRC connection mode and / or shortly after a power supply link handover occurs.

[0132] (18) An infrastructure device (gNB; NTC) according to any one of (13) to (17), wherein the circuit is configured to send information in encrypted form to the user equipment (UE) about the location of the infrastructure device (gNB) or about the distance of the infrastructure device (gNB) from the non-terrestrial network component (NT-RN).

[0133] (19) An infrastructure device (gNB; NTC) according to any one of (13) to (18), wherein the circuit is configured to repeatedly issue current TA adjustments (T) to the user equipment (UE). adjust ).

[0134] (20) An infrastructure device (gNB; NTC) according to any one of (13) to (19), wherein the circuit is configured to send the TA drift coefficient, or the TA drift coefficient and its direction (ΔT) to the user equipment (UE). com / Δt).

[0135] (21) According to the infrastructure equipment (gNB; NTC) of (20), wherein the circuit is configured to transfer the TA drift coefficient and its direction (ΔT) com / Δt) is sent as part of the RAR response in msg2 of a 4-step RACH or msgB of a 2-step RACH, or by a regular MAC message.

[0136] (22) A method comprising: compensating for the impact on the public TA (T) in a transparent payload non-terrestrial network (NTN) configuration having a non-terrestrial network component (NT-RN) and infrastructure equipment (gNB) tethered by the non-terrestrial network component (NT-RN). com The impact of the power supply link.

Claims

1. An electronic device for mobile telecommunications, the electronic device comprising: A circuit is configured to compensate for the impact of a feeder link on the common timing advance (TA) in a transparent payload non-terrestrial network configuration having non-terrestrial network components and infrastructure equipment connected by the non-terrestrial network components, wherein the circuit is configured to absorb variations in the feeder link propagation time as part of a user equipment-specific differential TA, and wherein the circuit is configured to repeatedly adjust the user equipment-specific differential TA to account for varying distances between the non-terrestrial network components and the infrastructure equipment.

2. The electronic device according to claim 1, wherein, The circuit is configured to receive information about the ephemeris of the non-terrestrial network component and the location of the infrastructure equipment, and to repeatedly calculate the distance between the non-terrestrial network component and the infrastructure equipment based on the information.

3. The electronic device according to claim 1, wherein, The circuit is configured to receive information about the initial distance between the infrastructure equipment and the non-terrestrial network component and the ephemeris of the non-terrestrial network component, and to repeatedly calculate the distance between the non-terrestrial network component and the infrastructure equipment based on the information.

4. The electronic device according to claim 1, wherein, The circuit is configured to receive information about the location of the infrastructure equipment or the distance between the infrastructure equipment and the non-terrestrial network components once the electronic device enters RRC connection mode and / or shortly after a power supply link switch occurs.

5. The electronic device according to claim 1, wherein, The circuit is configured to receive, in encrypted form, information about the location of the infrastructure equipment or information about the distance between the infrastructure equipment and the non-terrestrial network components.

6. The electronic device according to claim 1, wherein, The circuit is configured to repeatedly receive the current TA adjustment and adjust the common TA based on the TA adjustment.

7. The electronic device according to claim 1, wherein, The circuit is configured to repeatedly determine the current TA adjustment based on the TA drift coefficient and the direction of TA drift, and to adjust the common TA based on the TA adjustment.

8. The electronic device according to claim 7, wherein, The TA drift coefficient and the direction of TA drift include drift caused by the movement of the satellite in its orbit, and also include the displacement of the satellite and the connected infrastructure equipment.

9. A system for mobile telecommunications, the system comprising: The electronic device as described in claim 1, the ground-based infrastructure equipment, and the non-terrestrial network component configured to relay uplink and downlink traffic between the user equipment and the infrastructure equipment.

10. An infrastructure device, the infrastructure device comprising: A circuit is configured to provide information to a user equipment (UE) for compensating for the impact of a feeder link on the common timing advance (TA) in a transparent payload non-terrestrial network configuration having a non-terrestrial network component and a base station connected by the non-terrestrial network component. The circuit is configured to absorb variations in the feeder link propagation time as part of the UE-specific differential TA. The circuit is also configured to repeatedly adjust the UE-specific differential TA to account for varying distances between the non-terrestrial network component and the infrastructure equipment.

11. The infrastructure equipment according to claim 10, wherein, The circuit is configured to send ephemeris information about the non-terrestrial network component to the user equipment.

12. The infrastructure equipment according to claim 10, wherein, The circuit is configured to send information to the user equipment regarding the location of the infrastructure equipment connected by the non-terrestrial network component.

13. The infrastructure equipment according to claim 10, wherein, The circuit is configured to send information to the user equipment regarding the initial distance between the infrastructure equipment and the non-terrestrial network component.

14. The infrastructure equipment according to claim 10, wherein, The circuit is configured to send information to the user equipment about the location of the infrastructure equipment or the distance between the infrastructure equipment and the non-terrestrial network components once the user equipment enters RRC connection mode and / or shortly after a power supply link switch occurs.

15. The infrastructure equipment according to claim 10, wherein, The circuit is configured to send information about the location of the infrastructure equipment or the distance between the infrastructure equipment and the non-terrestrial network components to the user equipment in encrypted form.

16. The infrastructure equipment according to claim 10, wherein, The circuit is configured to repeatedly send the current TA adjustment to the user equipment.

17. The infrastructure equipment according to claim 10, wherein, The circuit is configured to send the TA drift coefficient, or the TA drift coefficient and the direction of TA drift, to the user equipment.

18. A method for mobile telecommunications, the method comprising: The impact of the compensation feeder link on the common timing advance (TA) in a transparent payload non-terrestrial network configuration with non-terrestrial network components and infrastructure equipment connected by the non-terrestrial network components; The variation in the propagation time of the feeder link is absorbed as part of the user equipment-specific differential transfer (TA). as well as Repeatedly adjust the user equipment-specific differential TA to account for the varying distances between the non-terrestrial network components and the infrastructure equipment.

Images