Communication methods, equipment and systems for non-terrestrial networks

By receiving configuration information and performing frequency offset compensation in a non-terrestrial network via a terminal, the Doppler frequency offset problem caused by high-speed movement between satellites and ground base stations is solved, thereby improving synchronization accuracy and communication quality and reducing the burden on ground base stations.

CN123125982APending Publication Date: 2026-11-17BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202680002181.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-06-30
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In non-terrestrial networks, the Doppler frequency offset caused by the high-speed relative motion between satellites and ground base stations is difficult to compensate effectively, affecting the uplink and downlink synchronization accuracy and communication quality of feeder links, and the frequency offset estimation and compensation processing of ground base stations has a heavy load.

Method used

The terminal receives configuration information sent by network equipment, determines the frequency offset compensation parameters of the feeder link, and performs frequency offset compensation to reduce the processing load of the ground base station.

Benefits of technology

It improves the uplink and downlink synchronization accuracy and communication quality of the feeder link, and reduces the frequency offset estimation and compensation processing load of the ground base station.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125982A_ABST
    Figure CN123125982A_ABST
Patent Text Reader

Abstract

This disclosure proposes a communication method, communication device, and communication system for non-terrestrial networks, relating to the field of communication technology. The method includes: a network device sending configuration information to a terminal; the terminal receiving the configuration information from the network device; determining frequency offset compensation parameters for the feeder link based on the configuration information; and then performing frequency offset compensation for the feeder link according to these parameters. In an NTN scenario, the terminal can perform frequency offset compensation for the feeder link based on the configuration information sent by the network device, effectively compensating for Doppler frequency offset caused by the high-speed relative motion between the satellite and the ground base station. This not only improves the accuracy of feeder link frequency offset compensation, thereby enhancing the uplink and downlink synchronization accuracy and communication quality of the feeder link, but also reduces the load on the ground base station for frequency offset estimation and compensation processing under a transparent payload architecture.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication equipment and communication system for non-terrestrial networks. Background Technology

[0002] Non-terrestrial networks (NTNs) are wireless communication networks that use non-terrestrial aircraft such as satellites or high-altitude platform stations (HAPS) as communication nodes. They can solve communication problems in remote areas, oceans, or airspace where traditional base stations cannot provide coverage. Summary of the Invention

[0003] This disclosure presents a communication method, communication equipment, and communication system for non-terrestrial networks.

[0004] A first aspect of this disclosure provides a communication method for a non-terrestrial network, executed by a terminal, the method comprising: receiving configuration information sent by a network device; determining frequency offset compensation parameters for a feeder link based on the configuration information; and performing frequency offset compensation for the feeder link according to the frequency offset compensation parameters.

[0005] A second aspect of this disclosure provides a communication method for a non-terrestrial network, executed by a network device, the method comprising: sending configuration information to a terminal; wherein the configuration information is used to determine frequency offset compensation parameters for a feeder link; the frequency offset compensation parameters are used for frequency offset compensation of the feeder link.

[0006] A third aspect of this disclosure provides a terminal, including: a processing module and a transceiver module, wherein the transceiver module is configured to receive configuration information sent by a network device; the processing module is configured to determine frequency offset compensation parameters for a feeder link based on the configuration information; and to perform frequency offset compensation for the feeder link according to the frequency offset compensation parameters.

[0007] A fourth aspect of this disclosure provides a network device, including: a transceiver module and a processing module, wherein the transceiver module is configured to send configuration information to a terminal; wherein the configuration information is used to determine frequency offset compensation parameters for a feeder link; the frequency offset compensation parameters are used for frequency offset compensation of the feeder link.

[0008] A fifth aspect of this disclosure provides a communication device for performing the method described in the first aspect embodiment or the method described in the second aspect embodiment.

[0009] A sixth aspect of this disclosure provides a communication system including a terminal and a network device, wherein the terminal is configured to implement the method described in the first aspect embodiment, and the network device is configured to implement the method described in the second aspect embodiment.

[0010] A seventh aspect embodiment of this disclosure provides a storage medium that, when the instructions are executed on a communication device, causes the communication device to perform the method as described in the first aspect embodiment or the method as described in the second aspect embodiment.

[0011] An eighth aspect of this disclosure provides a program product including at least one of a program and instructions, wherein the program and instructions, when executed by a communication device, implement the method described in the first aspect embodiment or the method described in the second aspect embodiment.

[0012] The technical solution provided in this disclosure involves a network device sending configuration information to a terminal. The terminal receives the configuration information from the network device, determines the frequency offset compensation parameters for the feeder link based on the configuration information, and then performs frequency offset compensation for the feeder link according to these parameters. In an NTN scenario, the terminal can perform frequency offset compensation for the feeder link based on the configuration information sent by the network device. Compared to the terrestrial base station performing the frequency offset compensation for the feeder link entirely, this embodiment allows the terminal to calculate and execute the frequency offset compensation for the feeder link. This effectively compensates for the Doppler frequency offset caused by the high-speed relative motion between the satellite and the terrestrial base station, improving the accuracy of the feeder link frequency offset compensation, thereby enhancing the uplink and downlink synchronization accuracy and communication quality of the feeder link. Furthermore, it reduces the load on the terrestrial base station for frequency offset estimation and compensation processing under a transparent payload architecture.

[0013] Additional aspects and advantages of this disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this disclosure. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0015] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure.

[0016] Figure 2A This is a timing diagram illustrating a communication method for a non-terrestrial network provided in an embodiment of this disclosure.

[0017] Figure 2B This is a timing diagram illustrating a communication method for a non-terrestrial network provided in an embodiment of this disclosure.

[0018] Figure 2C This is a timing diagram illustrating a communication method for a non-terrestrial network provided in an embodiment of this disclosure.

[0019] Figure 3A This is a schematic diagram of a non-terrestrial network communication method provided in an embodiment of this disclosure.

[0020] Figure 3B This is a schematic diagram of a non-terrestrial network communication method provided in an embodiment of this disclosure.

[0021] Figure 4A This is a structural block diagram of a terminal provided in an embodiment of this disclosure.

[0022] Figure 4B This is a structural block diagram of a network device provided in an embodiment of this disclosure.

[0023] Figure 5A This is a schematic diagram of the structure of a communication device provided in an embodiment of this disclosure.

[0024] Figure 5B This is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0025] The embodiments of this disclosure are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this disclosure, and should not be construed as limiting this disclosure. It should be noted that, unless otherwise specified, the embodiments of this disclosure and the features in the embodiments can be combined with each other.

[0026] This disclosure presents a communication method, communication device, and communication system for non-terrestrial networks.

[0027] In a first aspect, embodiments of this disclosure propose a communication method for a non-terrestrial network, executed by a terminal, the method comprising:

[0028] Receive configuration information sent by network devices;

[0029] Based on the configuration information, determine the frequency offset compensation parameters for the feeder link;

[0030] Frequency offset compensation of the feeder link is performed according to the frequency offset compensation parameters.

[0031] Through the technical solution of the embodiments of this disclosure, the terminal can perform frequency offset compensation of the feeder link based on the configuration information issued by the network device. This can effectively compensate for the Doppler frequency offset caused by the high-speed relative motion between the satellite and the ground base station. This not only improves the uplink and downlink synchronization accuracy and communication quality of the feeder link, but also reduces the load of frequency offset estimation and compensation processing of the ground base station under the transparent payload architecture.

[0032] In conjunction with some embodiments of the first aspect, the frequency offset compensation parameters include at least one of uplink frequency offset compensation parameters and downlink frequency offset compensation parameters;

[0033] The step of performing frequency offset compensation for the feeder link according to the frequency offset compensation parameters includes at least one of the following:

[0034] Based on the uplink frequency offset compensation parameters, perform uplink frequency offset pre-compensation for the feeder link;

[0035] Based on the downlink frequency offset compensation parameters, perform downlink frequency offset compensation on the feeder link.

[0036] In this way, the terminal performs unidirectional or bidirectional frequency offset compensation on the feeder link. The terminal can flexibly choose the compensation method according to the actual configuration of the network side and its own hardware capabilities, which can be adapted to different application scenarios.

[0037] In conjunction with some embodiments of the first aspect, determining the frequency offset compensation parameters of the feeder link based on the configuration information includes any one of the following:

[0038] The uplink frequency offset compensation parameters are determined based on the configuration information, and the downlink frequency offset compensation parameters of the feeder link are determined based on the uplink frequency offset compensation parameters and the ratio between the uplink carrier frequency and the downlink carrier frequency.

[0039] The downlink frequency offset compensation parameters are determined based on the configuration information, and the uplink frequency offset compensation parameters of the feeder link are determined based on the downlink frequency offset compensation parameters and the ratio between the uplink carrier frequency and the downlink carrier frequency.

[0040] In this way, network devices can send frequency offset compensation parameters in only one direction, and terminals can deduce the frequency offset compensation parameters in the other direction, saving the transmission overhead of network signaling.

[0041] In conjunction with some embodiments of the first aspect, the feeder link is a transmission link between a ground base station and a satellite;

[0042] The configuration information includes at least one of the following:

[0043] The location information of the ground base station;

[0044] The carrier frequency of the feeder link;

[0045] Satellite ephemeris information;

[0046] epochal time information;

[0047] The first indication of the Doppler frequency offset of the feeder link;

[0048] The second indication of Doppler frequency drift of the feeder link;

[0049] The third indication of the common TA of the feeder link;

[0050] The fourth indication of the common TA drift of the feeder link;

[0051] The fifth indication of the common TA drift rate of the feeder link.

[0052] This multi-dimensional configuration information can help the terminal accurately determine the frequency offset compensation parameters and / or time offset compensation parameters. Network devices can issue appropriate configurations based on satellite orbit type, terminal positioning capability, and terminal computing power to meet the needs of different application scenarios.

[0053] In conjunction with some embodiments of the first aspect, determining the frequency offset compensation parameters of the feeder link based on the configuration information includes:

[0054] Based on the configuration information, determine the Doppler frequency offset and / or Doppler frequency drift of the feeder link;

[0055] The frequency offset compensation parameters are determined based on the Doppler frequency offset and / or the Doppler frequency drift.

[0056] By decomposing Doppler frequency shift into Doppler frequency offset and Doppler frequency drift, the terminal can compensate not only for the static frequency offset at a certain moment, but also for the continuous frequency changes caused by the relative acceleration of the satellite, making the frequency offset compensation more accurate. Furthermore, the terminal can choose to perform partial frequency offset compensation, while the network device performs the other part, thereby reducing the processing load on the network device to some extent.

[0057] In conjunction with some embodiments of the first aspect, determining the Doppler frequency offset of the feeder link based on the configuration information includes any one of the following:

[0058] Based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information, the Doppler frequency offset is determined;

[0059] The Doppler frequency offset is determined based on the first indication;

[0060] The Doppler frequency offset is determined based on the common TA drift of the feeder link and the carrier frequency of the feeder link.

[0061] These optional methods for determining Doppler frequency offset can meet the needs of different scenarios. For example, the terminal can independently calculate the Doppler frequency offset, or directly determine the Doppler frequency offset according to network instructions, or derive the Doppler frequency offset using time offset compensation parameters, etc.

[0062] In conjunction with some embodiments of the first aspect, determining the Doppler frequency drift of the feeder link based on the configuration information includes any one of the following:

[0063] Based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information, the Doppler frequency drift is determined;

[0064] The Doppler frequency drift is determined based on the second indication;

[0065] The Doppler frequency drift is determined based on the common TA drift rate of the feeder link and the carrier frequency of the feeder link.

[0066] These optional methods for determining Doppler frequency drift can meet the needs of different scenarios. For example, the terminal can autonomously calculate Doppler frequency drift, or directly determine Doppler frequency drift according to network instructions, or derive Doppler frequency drift using time offset compensation parameters, etc.

[0067] In conjunction with some embodiments of the first aspect, the method further includes:

[0068] The timing advance (TA) pre-compensation value of the feeder link is determined based on the configuration information.

[0069] Based on the TA pre-compensation value, time offset compensation is performed on the feeder link.

[0070] The solution provided by the embodiments of this disclosure enables time offset compensation and frequency offset compensation for feeder links under a transparent load architecture, thereby accurately achieving synchronization with the network side.

[0071] In conjunction with some embodiments of the first aspect, determining the TA pre-compensation value of the feeder link based on the configuration information includes:

[0072] Based on the location information of the ground base station, the satellite ephemeris information, and the epoch time information, the TA pre-compensation value of the feeder link is determined.

[0073] In this way, the terminal can autonomously calculate the TA pre-compensation value based on these parameters. At the same time, these parameters can also be used to calculate the frequency offset compensation parameters. Then, the network can send out the same parameters to simultaneously achieve time offset compensation and frequency offset compensation of the feeder link.

[0074] In conjunction with some embodiments of the first aspect, determining the TA pre-compensation value of the feeder link based on the configuration information includes:

[0075] Based on the configuration information, at least one of the following is determined for the feeder link: common TA, common TA drift, and common TA drift rate;

[0076] The TA pre-compensation value of the feeder link is determined based on at least one of the common TA, the common TA drift, and the common TA drift change rate.

[0077] In this way, the TA pre-compensation value of the feeder link can be accurately calculated, which is applicable to different terminal computing power conditions. The terminal can choose to perform part of the time offset compensation, while the network device performs the other part of the time offset compensation, thereby saving the processing load of the network device to a certain extent.

[0078] In conjunction with some embodiments of the first aspect, determining the common TA of the feeder link based on the configuration information includes:

[0079] The common TA is determined according to the third instruction, the third instruction including at least one of the following parameters for determining the common TA:

[0080] Propagation delay between the ground base station and the satellite;

[0081] The distance between the ground base station and the satellite;

[0082] The elevation angle between the ground base station and the satellite.

[0083] In this way, network devices can instruct parameters used to calculate the common TA, such as the propagation delay between the terrestrial base station and the satellite, the distance between the terrestrial base station and the satellite, or the elevation angle between the terrestrial base station and the satellite.

[0084] In conjunction with some embodiments of the first aspect, determining the common TA drift of the feeder link based on the configuration information includes any of the following:

[0085] The common TA drift is determined according to the fourth indication;

[0086] The common TA drift is determined based on the Doppler frequency offset of the feeder link and the carrier frequency of the feeder link.

[0087] In this way, in addition to the method of directly indicating the common TA drift through the network, it can also be derived from the frequency offset parameter, saving the transmission overhead of network signaling and enabling accurate indication while achieving time offset compensation and frequency offset compensation.

[0088] In conjunction with some embodiments of the first aspect, the common TA drift rate of the feeder link is determined based on the configuration information, including any one of the following:

[0089] The common TA drift rate is determined according to the fifth indication;

[0090] The common TA drift rate is determined based on the Doppler frequency drift of the feeder link and the carrier frequency of the feeder link.

[0091] In this way, in addition to the method of directly indicating the common time offset (TA) drift rate, it can also be derived from the frequency offset parameter, saving the transmission overhead of network signaling and enabling accurate indication while achieving time offset compensation and frequency offset compensation.

[0092] Secondly, embodiments of this disclosure propose a communication method for a non-terrestrial network, executed by a network device, the method comprising:

[0093] Send configuration information to the terminal;

[0094] The configuration information is used to determine the frequency offset compensation parameters of the feeder link; the frequency offset compensation parameters are used for frequency offset compensation of the feeder link.

[0095] In conjunction with some embodiments of the second aspect, the frequency offset compensation parameters include at least one of uplink frequency offset compensation parameters and downlink frequency offset compensation parameters;

[0096] The frequency offset compensation of the feeder link includes at least one of the following:

[0097] The uplink frequency offset pre-compensation of the feeder link;

[0098] Downlink frequency offset compensation for the feeder link.

[0099] In conjunction with some embodiments of the second aspect, the feeder link is a transmission link between a ground base station and a satellite;

[0100] The configuration information includes at least one of the following:

[0101] The location information of the ground base station;

[0102] The carrier frequency of the feeder link;

[0103] Satellite ephemeris information;

[0104] epochal time information;

[0105] The first indication of the Doppler frequency offset of the feeder link;

[0106] The second indication of Doppler frequency drift of the feeder link;

[0107] The third indication of the common TA of the feeder link;

[0108] The fourth indication of the common TA drift of the feeder link;

[0109] The fifth indication of the common TA drift rate of the feeder link.

[0110] In conjunction with some embodiments of the second aspect, the configuration information is used to determine the Doppler frequency offset and / or Doppler frequency drift of the feeder link, and the Doppler frequency offset and / or the Doppler frequency drift is used to determine the frequency offset compensation parameter.

[0111] In some embodiments of the second aspect, the Doppler frequency offset is determined based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information; or,

[0112] The Doppler frequency offset is determined based on the first indication; or...

[0113] The Doppler frequency offset is determined based on the common TA drift of the feeder link and the carrier frequency of the feeder link.

[0114] In some embodiments of the second aspect, the Doppler frequency drift is determined based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information; or,

[0115] The Doppler frequency drift is determined based on the second indication; or...

[0116] The Doppler frequency drift is determined based on the common TA drift rate of the feeder link and the carrier frequency of the feeder link.

[0117] In conjunction with some embodiments of the second aspect, the configuration information is also used to determine the TA pre-compensation value of the feeder link; the TA pre-compensation value is used for time offset compensation of the feeder link.

[0118] In conjunction with some embodiments of the second aspect, the TA pre-compensation value of the feeder link is determined based on the location information of the ground base station, the satellite ephemeris information, and the epoch time information.

[0119] In conjunction with some embodiments of the second aspect, the configuration information is used to determine at least one of the common TA, common TA drift, and common TA drift change rate of the feeder link; the common TA, common TA drift, and common TA drift change rate are used to determine the TA pre-compensation value of the feeder link.

[0120] In conjunction with some embodiments of the second aspect, the common TA is determined according to the third indication, the third indication including at least one of the following parameters for determining the common TA:

[0121] Propagation delay between the ground base station and the satellite;

[0122] The distance between the ground base station and the satellite;

[0123] The elevation angle between the ground base station and the satellite.

[0124] In conjunction with some embodiments of the second aspect, the common TA drift is determined according to the fourth indication; or,

[0125] The common TA drift is determined based on the Doppler frequency offset of the feeder link and the carrier frequency of the feeder link.

[0126] In conjunction with some embodiments of the second aspect, the common TA drift rate of change is determined according to the fifth indication; or,

[0127] The common TA drift rate is determined based on the Doppler frequency drift of the feeder link and the carrier frequency of the feeder link.

[0128] Thirdly, embodiments of this disclosure provide a terminal, including: a processing module and a transceiver module, wherein the transceiver module is configured to receive configuration information sent by a network device; the processing module is configured to determine frequency offset compensation parameters for a feeder link based on the configuration information; and to perform frequency offset compensation for the feeder link according to the frequency offset compensation parameters.

[0129] Fourthly, this disclosure provides a network device, including a transceiver module and a processing module, wherein the transceiver module is configured to send configuration information to a terminal; wherein the configuration information is used to determine frequency offset compensation parameters for a feeder link; and the frequency offset compensation parameters are used for frequency offset compensation of the feeder link.

[0130] Fifthly, embodiments of this disclosure provide a communication device for performing the method described in the first aspect embodiment or the method described in the second aspect embodiment.

[0131] In a sixth aspect, embodiments of this disclosure provide a communication system including a terminal and a network device, wherein the terminal is configured to implement the method described in the first aspect embodiment, and the network device is configured to implement the method described in the second aspect embodiment.

[0132] In a seventh aspect, embodiments of this disclosure provide a storage medium that, when the instructions are executed on a communication device, causes the communication device to perform the method as described in the first aspect embodiment or the second aspect embodiment.

[0133] Eighthly, embodiments of this disclosure provide a program product including at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the method described in the first aspect embodiment or the second aspect embodiment.

[0134] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in the first aspect embodiment or the second aspect embodiment.

[0135] In a tenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described above as in the first aspect embodiment or the second aspect embodiment.

[0136] It is understood that the aforementioned network devices, terminals, communication devices, communication systems, storage media, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0137] This disclosure provides a communication method, communication device, and communication system for a non-terrestrial network. In some embodiments, the terms "communication method" and "information processing method," "information sending method," and "information receiving method" can be used interchangeably; the terms "communication device" and "information processing device," "information sending device," and "information receiving device" can be used interchangeably; and the terms "information processing system," "communication system," "information sending system," and "information receiving system" can be used interchangeably.

[0138] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0139] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0140] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0141] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0142] In the embodiments disclosed herein, "multiple" refers to two or more.

[0143] In some embodiments, the terms “at least one of”, “at least one of”, “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0144] The descriptions in this disclosure, such as "at least one of A, B, C..." or "A and / or B and / or C...", include the case where any one of A, B, C... exists alone, as well as the case where any combination of any of A, B, C... exists alone. Each case can exist alone. For example, "at least one of A, B, C" includes the cases of A alone, B alone, C alone, A and B combination, A and C combination, B and C combination, and A and B and C combination. For example, A and / or B includes the cases of A alone, B alone, and A and B combination.

[0145] In some embodiments, the notation "in one case A, in another case B" or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: A is executed regardless of B, i.e., A is executed in some embodiments; B is executed regardless of A, i.e., B is executed in some embodiments; A and B are selectively executed, i.e., A and B are selected for execution in some embodiments; A and B are both executed, i.e., A and B are executed in some embodiments. The same applies when there are more branches such as A, B, and C.

[0146] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0147] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0148] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0149] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0150] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0151] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0152] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0153] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriberstation, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, and narrowband Internet of Things (NB-IoT) device can be used interchangeably.

[0154] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures that replace communication between access network devices, core network devices, or network devices and terminals with communication between multiple terminals (e.g., also referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, uplink link, downlink link, etc., can be replaced with sidelink link.

[0155] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0156] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0157] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0158] In some embodiments, the threshold mentioned in this disclosure may be a numerical value, a constant, or some fixed value.

[0159] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0160] The correspondences shown in the tables of this disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this disclosure is not limiting. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this disclosure may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headers of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0161] The predefined terms in this disclosure can be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0162] The following description, in conjunction with the accompanying drawings, details a communication method, communication equipment, and communication system for a non-terrestrial network provided in this disclosure.

[0163] Figure 1 A structural diagram of a communication system according to an embodiment of the present disclosure is shown, such as Figure 1 As shown, the system architecture may include a terminal 101 and a network device 102.

[0164] In some embodiments, terminal 101 may also be referred to as terminal, user equipment, mobile station (MS), mobile terminal (MT), etc. For example, terminals include at least one of the following: wearable devices (such as smartwatches, health monitoring bracelets, etc.), Internet of Things devices (such as NB-IoT devices), industrial wireless sensors, red-capped terminals, smartphones, cars with communication capabilities, smart cars, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminal devices in industrial control, wireless terminal devices in self-driving, wireless terminal devices in remote medical surgery, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, and wireless terminal devices in smart homes, but are not limited thereto.

[0165] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0166] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), advanced Node B (aNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station (e.g., aNB) in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but is not limited thereto.

[0167] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0168] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0169] In some embodiments, a core network device may be a single device, including one or more network elements, or it may be multiple devices or a group of devices, each including all or part of one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), 6G Core Network (6GCN), and Next Generation Core (NGC).

[0170] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0171] The following embodiments of this disclosure can be applied to Figure 1 The communication system shown, or part of the main body, but not limited to it. Figure 1 The entities shown are illustrative; a communication system may include... Figure 1 All or part of the main body, or may include Figure 1 Other entities besides the main body, the number and form of each entity are arbitrary, the connection relationship between the entities is illustrative, the entities may not be connected or may be connected, and the connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0172] The embodiments disclosed herein can be applied to satellite communications, Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), 5th generation mobile communication system (6G), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other non-terrestrial network communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0173] In NTN transmission scenarios, wireless resources can be provided via network equipment such as satellites or High Altitude Platforms (HAPS) instead of terrestrial base stations. Depending on how the satellite processes the signal, it can be divided into transparent transmission mode (or transparent payload architecture) and regeneration mode. Transparent transmission mode: The terrestrial base station transmits the gNB signal to the satellite. The satellite converts the signal to its own frequency band and then transmits it to the terminal. Aside from frequency conversion and signal amplification, the satellite does not demodulate the gNB signal, acting as a repeater. Regeneration mode: After the terrestrial base station transmits the gNB signal to the satellite, the satellite first demodulates and decodes the signal, then re-encodes and modulates it (this process is regeneration), and then transmits the regenerated signal through its own frequency band.

[0174] In some examples, for transparent payload architectures, the frequency offset compensation of the feeder link is performed by the ground base station. However, this scheme, which relies entirely on the ground base station to perform the feeder link frequency offset compensation, has obvious shortcomings: on the one hand, the Doppler frequency offset caused by the high-speed motion of the satellite will greatly occupy the processing load of the ground base station; on the other hand, the ground base station has difficulty in accurately tracking the rapidly changing Doppler frequency offset, which can easily lead to the accumulation of residual frequency offset and affect the accuracy of feeder link frequency offset compensation.

[0175] To address the aforementioned issues, this disclosure provides an NTN communication scheme in which the terminal performs frequency offset compensation for the feeder link based on configuration information issued by the network device. Compared to the terrestrial base station performing the feeder link frequency offset compensation entirely, this disclosure allows the terminal to calculate and execute the feeder link frequency offset compensation, effectively compensating for Doppler frequency offset caused by the high-speed relative motion between the satellite and the terrestrial base station. This not only improves the accuracy of feeder link frequency offset compensation, thereby enhancing the uplink and downlink synchronization accuracy and communication quality of the feeder link, but also reduces the load on the terrestrial base station for frequency offset estimation and compensation processing under the transparent payload architecture.

[0176] Figure 2A This is a schematic diagram illustrating a communication method for a non-terrestrial network according to an embodiment of this disclosure. (For illustrative purposes) Figure 1 An alternative implementation of the communication system, this method can be used to enable the terminal to perform frequency offset compensation on the feeder link, such as... Figure 2A As shown, the method includes the following steps:

[0177] Step S2101: The network device sends configuration information to the terminal.

[0178] In some embodiments, configuration information sent by the network device can be used to determine frequency offset compensation parameters for the feeder link, which are used for frequency offset compensation of the feeder link.

[0179] In some embodiments, network devices may transmit configuration information via at least one of terminal-specific radio resource control (RRC) signaling, system messages, beam-specific signaling, etc.

[0180] In some examples, if configuration information is sent to the terminal via a system message bearer, the system message may include at least one of System Information Block (SIB) 1, SIB 19, other system messages (OSI), etc.

[0181] In some examples, network devices may send configuration information at the cell level, meaning that the configuration information is applicable to all terminals within the cell.

[0182] In some examples, the frequency offset compensation parameters determined based on configuration information can be cell-level parameters, for example, the frequency offset compensation parameters are common to terminals throughout the entire cell.

[0183] In some embodiments, the feeder link may be a transmission link between a ground base station (or a ground gateway station, etc.) and a satellite. Correspondingly, the transmission link between the terminal and the satellite may be called a service link.

[0184] In some embodiments, the configuration information sent by the network device includes at least one of the following A1 to A9:

[0185] A1. Location information of ground base station.

[0186] In some examples, to enable the terminal to autonomously and accurately calculate the frequency offset compensation parameters of the feeder link, the configuration information sent by the network device to the terminal may include the location information of the ground base station where the network device is located. After obtaining the location information of the ground base station, the terminal can combine it with information such as satellite ephemeris data to determine the relative motion state between the satellite and the ground base station, and then calculate the Doppler frequency offset of the feeder link.

[0187] Optionally, considering the requirements for frequency offset compensation accuracy and the limitations of air interface signaling overhead in different scenarios, the location information of the ground base station in this embodiment may include coarse location information or accurate location information. The network device can choose to send one type of location information to the terminal according to the actual system configuration or satellite orbital altitude.

[0188] As an optional implementation, when the network device sends coarse location information to the terminal, the precision granularity of this coarse location information can be configured to a preset distance value, such as approximately M kilometers (e.g., M=2, i.e., precision 2km). Since satellites are typically far from the ground in a transparent payload architecture, the small errors in the location of the ground base station have an acceptable impact on the overall Doppler frequency offset of the terminal's calculation feeder link. Therefore, using coarse location information can significantly reduce signaling transmission overhead while meeting the frequency offset compensation accuracy requirements. Furthermore, in the signaling field design, this coarse location information can be carried using an optional eight-bit byte string field. In specific implementation, to achieve the aforementioned preset distance value (e.g., 2km) precision granularity, the network device will truncate the original precise latitude and longitude data. The network device will set a preset number of least significant bits (LSBs) representing latitude and longitude to 0. The first (or leftmost) bit of the first eight-bit byte contains the most significant bit (MSB). The specific number of least significant bits set to 0 to meet specific precision granularity requirements can be determined by the actual implementation method or network configuration of the ground base station.

[0189] As an alternative embodiment, when the network device sends precise location information to the terminal, this precise location information is not subject to the aforementioned low-order truncation processing, thus retaining complete coordinate accuracy. In the signaling field design, an Ellipsoid-Point Information Element (IE) can be used to describe this geographic location. Specifically, the Ellipsoid-Point data structure may include the following fields:

[0190] (1) Latitude sign, for example, used to indicate north or south latitude;

[0191] (2) Latitude, for example, can be configured as a 23-bit field with a value range of 0 to 8388607;

[0192] (3) Longitude (degrees): For example, configured as a 24-bit field, the value range can be... - 8388608 to 8388607.

[0193] A2. Carrier frequency of the feederlink. For example, the magnitude of the Doppler frequency offset is related not only to the relative speed between the satellite and the ground base station, but also to the carrier frequency used for signal transmission. Therefore, the feederlink carrier frequency can be used as a reference for the terminal to autonomously calculate the feederlink Doppler frequency offset.

[0194] In some examples, the carrier frequency of the feeder link may include the uplink carrier frequency and / or the downlink carrier frequency.

[0195] A3. Ephemeris Information: This information may include parameters of the satellite's orbit in space.

[0196] A4. Epoch time information, which can be used as a reference time point.

[0197] A5. A first indication of the Doppler offset of the feeder link, wherein the Doppler offset can be considered as the difference between the carrier frequency received by the receiver and the carrier frequency transmitted by the transmitter at a specific moment due to the relative radial velocity between the satellite and the ground base station. For example, the Doppler offset can be the frequency offset value between the ground base station and the satellite due to the rapid movement of the satellite at the first moment. Optionally, this first moment can also be configured / indicated to the terminal by the base station, such as an epoch time.

[0198] In some examples, the first indication can be used to indicate the Doppler frequency offset of a feeder link, for example, when a network device issues configuration information and directly indicates the Doppler frequency offset of the feeder link in that configuration information.

[0199] A6. A second indicator of the Doppler drift (doppler rate) of the feeder link, wherein the Doppler drift can be the rate at which the Doppler frequency offset changes over time, equivalent to the first derivative of the Doppler frequency offset. For example, the Doppler drift is the rate at which the Doppler frequency shift changes continuously over time, caused by the relative acceleration of the satellite relative to the ground base station.

[0200] The second indication can be used to indicate the Doppler frequency drift of the feeder link, for example, when the network device issues configuration information and directly indicates the Doppler frequency drift of the feeder link in the configuration information.

[0201] A7. The third indication of the common TA of the feeder link, wherein the common TA is the TA value corresponding to the propagation delay of the feeder link (between the ground base station and the satellite) at a specific time (such as epoch time), which can be regarded as the time advance shared by all terminals in the beam / cell.

[0202] In some examples, the third indication includes at least one of the following parameters for determining the public TA:

[0203] (1) Propagation delay between the ground base station and the satellite; this propagation delay can be the bidirectional propagation delay between the ground base station and the satellite at a specific time, or the unidirectional propagation delay between the ground base station and the satellite at a specific time. The common transmission delay of the feeder link can be accurately determined through this transmission delay.

[0204] (2) The distance between the ground base station and the satellite; this distance can be the straight-line distance between the ground base station and the satellite at a specific time. Based on this distance, the propagation delay between the ground base station and the satellite at a specific time can be calculated, thereby obtaining the TA value between the ground base station and the satellite at a specific time, i.e. the common TA of the feeder link.

[0205] (3) Elevation angle between the ground base station and the satellite; This elevation angle can be the elevation angle between the ground base station and the satellite at a specific time. The satellite orbital altitude information is obtained based on the satellite ephemeris information. Based on the elevation angle between the ground base station and the satellite at a specific time and the satellite orbital altitude information, the propagation distance between the ground base station and the satellite at a specific time is calculated, and then the propagation delay is inferred. Thus, the TA value between the ground base station and the satellite at a specific time is calculated, which is the common TA of the feeder link.

[0206] In some examples, the specific moments in examples (1), (2), and (3) above may be epoch times.

[0207] A8. The fourth indicator of common TA drift in feeder links, where common TA drift can be the rate at which common TA changes over time, equivalent to the first derivative of common TA.

[0208] In some examples, this fourth indication can be used to indicate common TA drift of a feeder link, for example, when a network device issues configuration information and directly indicates common TA drift of a feeder link in that configuration information.

[0209] A9, the fifth indicator of the common TA drift variation of the feeder link, wherein the common TA drift variation can be the rate at which the common TA drift changes over time, equivalent to the second derivative of the common TA.

[0210] This fifth indication can be used to indicate the common TA drift rate of a feeder link, for example, when a network device issues configuration information and directly indicates the common TA drift of the feeder link in that configuration information.

[0211] In step S2102, the terminal receives configuration information sent by the network device and determines the frequency offset compensation parameters of the feeder link based on the configuration information.

[0212] In some embodiments, the terminal can determine the Doppler frequency offset and / or Doppler frequency drift of the feeder link based on configuration information; then, based on the Doppler frequency offset and / or Doppler frequency drift, it determines the frequency offset compensation parameters of the feeder link. For example, based on the Doppler frequency offset and Doppler frequency drift, the terminal calculates the overall Doppler frequency shift caused by satellite movement, thereby compensating for the large Doppler frequency offset of the feeder link caused by rapid satellite movement.

[0213] In some embodiments, the terminal can determine the Doppler frequency offset of the feeder link based on at least one parameter in the configuration information in several optional ways:

[0214] As an optional method for determining Doppler frequency offset, when the configuration information includes the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information, the terminal can autonomously calculate the Doppler frequency offset caused by satellite movement based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information, thereby compensating for the large Doppler frequency offset caused by the rapid movement of the satellite in the feeder link.

[0215] As another optional method for determining Doppler frequency offset, when the configuration information includes a first indication of the Doppler frequency offset of the feeder link, the terminal can directly determine the Doppler frequency offset based on the first indication. For example, if the network device indicates the Doppler frequency offset in the configuration information, the terminal can directly determine the Doppler frequency offset of the feeder link according to the network indication.

[0216] As another optional method for determining Doppler frequency offset, the terminal can determine the Doppler frequency offset based on time offset compensation related parameters in the configuration information. Optionally, the time offset compensation related parameters can be at least one of the common TA of the feeder link, common TA drift, and common TA drift change rate.

[0217] Optionally, the Doppler frequency offset of the feeder link can be determined based on the common TA drift of the feeder link and the carrier frequency of the feeder link.

[0218] For example, when the configuration information includes a fourth indication of the common TA drift of the feeder link and the carrier frequency of the feeder link, the common TA drift is determined based on the fourth indication, and the Doppler frequency offset of the feeder link is derived by combining it with the carrier frequency of the feeder link.

[0219] In some embodiments, the terminal can determine the Doppler frequency drift of the feeder link based on at least one parameter in the configuration information in several alternative ways:

[0220] As an optional method for determining Doppler frequency drift, when the configuration information includes the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information, the terminal can autonomously calculate the Doppler frequency drift of the feeder link based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information.

[0221] As an alternative method for determining Doppler frequency drift, when the configuration information includes a second indication of the Doppler frequency drift of the feeder link, the terminal can directly determine the Doppler frequency drift based on this second indication. For example, if the network device indicates the Doppler frequency drift in the configuration information, the terminal can directly determine the Doppler frequency drift of the feeder link based on the network indication.

[0222] As another optional method for determining Doppler frequency offset, the terminal can determine the Doppler frequency drift based on time offset compensation related parameters in the configuration information. Optionally, the time offset compensation related parameters can be at least one of the common TA of the feeder link, common TA drift, and common TA drift change rate.

[0223] Optionally, the terminal can determine the Doppler frequency drift of the feeder link based on the common TA drift rate and the carrier frequency of the feeder link.

[0224] For example, when the configuration information includes a fifth indication of the common TA drift rate of the feeder link and the carrier frequency of the feeder link, the common TA drift rate is determined based on the fifth indication, and the Doppler frequency drift of the feeder link is derived by combining it with the carrier frequency of the feeder link.

[0225] Furthermore, in some embodiments, the frequency offset compensation parameters may specifically include at least one of uplink frequency offset compensation parameters and downlink frequency offset compensation parameters. The specific meaning and configuration method of the feeder link carrier frequency issued by the network device also differ depending on the compensation direction.

[0226] In some examples, for uplink frequency offset pre-compensation, from the terminal's perspective, the complete propagation path of the uplink signal is terminal → satellite → ground base station. In this scenario, the feeder link that the terminal needs to compensate for refers to the link in the "satellite → ground base station" propagation direction. Therefore, the carrier frequency configured by the network equipment is specifically the uplink carrier frequency of the feeder link. The terminal uses this uplink carrier frequency, combined with the relative motion speed between the satellite and the ground base station, to calculate the Doppler frequency offset of the uplink feeder link, and performs pre-compensation in advance when transmitting the uplink signal, thereby ensuring that the frequency is accurately aligned when the signal reaches the ground base station via transparent relay from the satellite.

[0227] In some examples, for downlink frequency offset post-compensation, from the terminal's perspective, the complete propagation path of the downlink signal is terrestrial base station → satellite → terminal. In this scenario, the feeder link that the terminal needs to compensate for refers to the link in the propagation direction of "terrestrial base station → satellite". Therefore, the carrier frequency configured by the network equipment is specifically the downlink carrier frequency of the feeder link. After receiving the downlink signal, the terminal uses this downlink feeder link carrier frequency to calculate the Doppler frequency offset of the downlink feeder link and performs post-compensation (i.e., frequency offset correction) on the received signal, thereby recovering the accurate baseband signal.

[0228] In some examples, considering that in many practical NTN system deployments, the uplink and downlink feeder links may use the same frequency band, or the impact of their carrier frequency differences on the Doppler frequency offset calculation results may be within system tolerance, only one common carrier frequency is configured to further save signaling overhead. The terminal reuses this common carrier frequency for Doppler parameter calculation during both uplink frequency offset pre-compensation and downlink frequency offset post-compensation. This configuration method reduces network signaling overhead while ensuring frequency offset compensation accuracy.

[0229] In some embodiments, if the network device is not configured with relevant information for determining frequency offset compensation parameters, the terminal may not perform frequency offset compensation for the feeder link.

[0230] In some embodiments, one of the above-mentioned schemes for determining frequency offset compensation parameters to perform feeder link frequency offset compensation can be predefined by the protocol. The terminal performs frequency offset compensation based on configuration information according to the scheme predefined by the protocol, and performs feeder link frequency offset compensation according to the frequency offset compensation parameters.

[0231] In some embodiments, when the terminal simultaneously supports uplink frequency offset pre-compensation and downlink frequency offset post-compensation for the feeder link, and the network device is configured with only one carrier frequency in one transmission direction, the terminal may process the data according to one of the following behaviors:

[0232] Behavior a: The terminal does not perform frequency offset compensation in the unconfigured transmission direction. For example, if the network device only configures the uplink carrier frequency of the feeder link but not the downlink carrier frequency of the feeder link, the terminal will not perform downlink frequency offset compensation for the feeder link.

[0233] Behavior b: The terminal performs compensation based on the carrier frequency of the other transmission direction. For example, if the network device does not configure the downlink carrier frequency of the feeder link, but configures the uplink carrier frequency of the feeder link, the terminal performs downlink frequency offset compensation of the feeder link based on the uplink carrier frequency configured by the network device; or, if the network device does not configure the uplink carrier frequency of the feeder link, but configures the downlink carrier frequency of the feeder link, the terminal performs uplink frequency offset pre-compensation of the feeder link based on the downlink carrier frequency configured by the network device.

[0234] As an example, the network device is configured only with the feeder link uplink carrier frequency (i.e., the carrier frequency in the direction from satellite to ground base station), but not with the feeder link downlink carrier frequency (i.e., the carrier frequency in the direction from ground base station to satellite). In this case, the terminal calculates the Doppler frequency offset based on the configured uplink carrier frequency and can apply this Doppler frequency offset to the frequency offset compensation of the downlink transmission.

[0235] In some embodiments, the network device can configure the uplink frequency offset compensation parameters and the downlink frequency offset compensation parameters independently. For example, the terminal can autonomously calculate the uplink frequency offset compensation parameters based on the location information of the ground base station, the uplink carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information. In addition, the downlink frequency offset compensation parameters are determined according to the first indication of the downlink Doppler frequency offset of the feeder link and / or the second indication of the downlink Doppler frequency drift of the feeder link.

[0236] In step S2103, the terminal performs frequency offset compensation for the feeder link according to the frequency offset compensation parameters.

[0237] In some embodiments, the terminal may determine frequency offset compensation parameters based on the Doppler frequency offset and / or Doppler frequency drift of the feeder link, and use the frequency offset compensation parameters to perform frequency offset compensation of the feeder link.

[0238] In some embodiments, the terminal may perform uplink frequency offset pre-compensation for the feeder link based on uplink frequency offset compensation parameters. For example, for uplink frequency offset pre-compensation of the feeder link, the terminal needs to determine the Doppler frequency offset and / or Doppler drift in the transmission direction from satellite to ground base station. That is, the uplink frequency offset compensation parameters may include the uplink Doppler frequency offset and / or Doppler drift of the feeder link, and the uplink Doppler frequency offset and / or Doppler drift are used to perform uplink frequency offset pre-compensation.

[0239] In some embodiments, downlink frequency offset compensation for the feeder link can be performed based on downlink frequency offset compensation parameters. For example, for downlink frequency offset compensation for the feeder link, the terminal needs to determine the Doppler frequency offset and / or Doppler drift in the transmission direction from the ground base station to the satellite. That is, the downlink frequency offset compensation parameters may include the downlink Doppler frequency offset and / or Doppler drift of the feeder link, and downlink frequency offset pre-compensation is performed using the downlink Doppler frequency offset and / or Doppler drift.

[0240] In some embodiments, uplink frequency offset pre-compensation of the feeder link can be performed based on uplink frequency offset compensation parameters, and downlink frequency offset post-compensation of the feeder link can be performed based on downlink frequency offset compensation parameters.

[0241] In one alternative example, the network device can independently configure the uplink Doppler frequency offset and the downlink Doppler frequency offset. For example, the uplink Doppler frequency offset parameter can be configured for the terminal to perform uplink frequency offset pre-compensation for the feeder link; and the downlink Doppler frequency offset parameter can be configured for the terminal to perform downlink frequency offset post-compensation for the feeder link.

[0242] In another alternative example, the network device can independently configure uplink Doppler drift and downlink Doppler drift. For example, it can configure uplink Doppler drift parameters for the terminal to perform uplink frequency offset pre-compensation for the feeder link; and configure downlink Doppler drift parameters for the terminal to perform downlink frequency offset post-compensation for the feeder link.

[0243] In another alternative example, the network device can be configured with a common Doppler frequency offset parameter, which is used for both uplink frequency offset pre-compensation and downlink frequency offset post-compensation of the feeder link.

[0244] In another alternative example, the network device can be configured with a common Doppler frequency drift parameter, which is used for both uplink frequency offset pre-compensation and downlink frequency offset post-compensation of the feeder link.

[0245] In some embodiments, when the terminal needs to perform downlink frequency offset compensation for the feeder link and the configuration information is used to determine the uplink frequency offset compensation parameters, the terminal can first determine the uplink frequency offset compensation parameters based on the configuration information, and then derive the downlink frequency offset compensation parameters for the feeder link based on the uplink frequency offset compensation parameters and the ratio between the uplink carrier frequency and the downlink carrier frequency. In this way, the network device can issue only the configuration for determining the uplink frequency offset compensation parameters to enable the terminal to perform downlink frequency offset compensation for the feeder link. Especially when the terminal needs to perform uplink and downlink frequency offset compensation, issuing the parameter configuration for one direction can achieve time offset compensation in both directions, saving network signaling overhead.

[0246] In some embodiments, when the terminal needs to perform uplink frequency offset pre-compensation for the feeder link, and the configuration information is used to determine the downlink frequency offset compensation parameters, the terminal first determines the downlink frequency offset compensation parameters based on the configuration information. Then, based on the downlink frequency offset compensation parameters and the ratio between the uplink carrier frequency and the downlink carrier frequency, it derives the uplink frequency offset pre-compensation parameters for the feeder link. In this way, the network device can issue only the configuration for determining the downlink frequency offset compensation parameters to enable the terminal to perform uplink frequency offset pre-compensation for the feeder link. Especially when the terminal needs to perform uplink and downlink frequency offset compensation, the parameter configuration for one direction can be issued to achieve time offset compensation in both directions, saving network signaling overhead.

[0247] In some embodiments, the terminal may only perform partial time offset compensation for the feeder link, with the remaining portion compensated by the network equipment (ground base station). For example, for frequency offset compensation, the terminal only compensates for Doppler frequency offset, while the frequency offset variation caused by Doppler frequency drift is compensated by the ground base station.

[0248] In some embodiments, the above-described time-frequency offset compensation mechanism may be applied to at least one of the following Global Navigation Satellite System (GNSS) operating modes:

[0249] GNSS-based operation;

[0250] GNSS resilient / degraded operation mode;

[0251] GNSS-less operation.

[0252] It is understood that this embodiment is only an illustrative example. In practical applications, the execution order of each step and the specific values ​​of each parameter can be flexibly adapted according to the protocol version and deployment requirements, and all of these fall within the protection scope of this solution.

[0253] The communication method for non-terrestrial networks involved in the embodiments of this disclosure may include at least one of steps S2101 to S2103. For example, step S2101 may be implemented as a standalone embodiment; or step S2102 may be implemented as a standalone embodiment; or step S2103 may be implemented as a standalone embodiment. In addition, some or all of the steps in steps S2101 to S2103 may be combined as standalone embodiments, and the embodiments of this disclosure do not limit this.

[0254] This disclosure proposes an NTN communication scheme in which the terminal performs frequency offset compensation of the feeder link based on configuration information issued by the network device. Compared with the terrestrial base station performing the frequency offset compensation of the feeder link entirely, this disclosure allows the terminal to calculate and execute the frequency offset compensation of the feeder link, which can effectively compensate for the Doppler frequency offset caused by the high-speed relative motion between the satellite and the terrestrial base station. This not only improves the accuracy of the feeder link frequency offset compensation, thereby improving the uplink and downlink synchronization accuracy and communication quality of the feeder link, but also reduces the load of frequency offset estimation and compensation processing of the terrestrial base station under the transparent payload architecture.

[0255] Figure 2B This is a schematic diagram illustrating a communication method for a non-terrestrial network according to an embodiment of this disclosure. (For illustrative purposes) Figure 1Another alternative implementation of the communication system, which can be used to enable the terminal to simultaneously perform frequency offset compensation and time offset compensation on the feeder link, such as... Figure 2B As shown, the method includes the following steps:

[0256] Step S2201: The network device sends configuration information to the terminal.

[0257] In some embodiments, the configuration information sent by the network device can be used to determine the frequency offset compensation parameters and time offset compensation parameters of the feeder link. The frequency offset compensation parameters are used for frequency offset compensation of the feeder link, and the time offset compensation parameters are used for time offset compensation of the feeder link.

[0258] In some embodiments, the time offset compensation parameter may include a TA pre-compensation value for the feeder link, which is used for time offset compensation of the feeder link.

[0259] In some embodiments, the network device may transmit configuration information via at least one bearer, such as terminal-specific RRC signaling, system messages, or beam-specific signaling. In some examples, if the configuration information is transmitted to the terminal via a system message bearer, the system message may include at least one of SIB1, SIB19, or OSI.

[0260] In some examples, network devices may send configuration information at the cell level, for example, configuration information that is applicable to all terminals within the cell.

[0261] In some examples, the frequency offset compensation parameters and time offset compensation parameters determined based on configuration information can be cell-level parameters.

[0262] In some embodiments, the configuration information sent by the network device includes at least one of the following B1 to B9:

[0263] B1. Location information of ground base stations.

[0264] B2, the carrier frequency of the feeder link.

[0265] B3. Satellite ephemeris information.

[0266] B4. Era Time Information.

[0267] B5, the first indication of Doppler frequency offset in the feeder link.

[0268] B6, the second indicator of Doppler frequency drift in the feeder link.

[0269] B7, the third indication of the common TA of the feeder link.

[0270] B8, the fourth indicator of common TA drift in the feeder link.

[0271] B9, the fifth indicator of the common TA drift rate of the feeder link.

[0272] The explanations for B1 to B9 above can be found in the corresponding descriptions of A1 to A9 in step S2101, and will not be repeated here.

[0273] In step S2202, the terminal receives configuration information sent by the network device and determines the frequency offset compensation parameters and TA pre-compensation value of the feeder link based on the configuration information.

[0274] In some embodiments, the terminal can determine the Doppler frequency offset and / or Doppler frequency drift of the feeder link based on configuration information; and then determine the frequency offset compensation parameters of the feeder link based on the Doppler frequency offset and / or Doppler frequency drift.

[0275] In some embodiments, the terminal can determine the Doppler frequency offset of the feeder link based on at least one parameter in the configuration information in several optional ways:

[0276] As an optional method for determining Doppler frequency offset, when the configuration information includes the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information, the terminal can autonomously calculate the Doppler frequency offset caused by satellite movement based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information, thereby compensating for the large Doppler frequency offset caused by the rapid movement of the satellite in the feeder link.

[0277] As another optional method for determining Doppler frequency offset, when the configuration information includes a first indication of the Doppler frequency offset of the feeder link, the terminal can directly determine the Doppler frequency offset based on the first indication.

[0278] As another optional method for determining Doppler frequency offset, the terminal can determine the Doppler frequency offset based on time offset compensation related parameters in the configuration information. Optionally, the time offset compensation related parameters can be at least one of the common TA of the feeder link, common TA drift, and common TA drift change rate.

[0279] Optionally, the Doppler frequency offset of the feeder link can be determined based on the common TA drift and the carrier frequency of the feeder link. For example, when the configuration information includes a fourth indication of the common TA drift of the feeder link and the carrier frequency of the feeder link, the common TA drift is determined based on the fourth indication, and the Doppler frequency offset of the feeder link is derived by combining it with the carrier frequency of the feeder link.

[0280] In some embodiments, the terminal can determine the Doppler frequency drift of the feeder link based on at least one parameter in the configuration information in several alternative ways:

[0281] As an optional method for determining Doppler frequency drift, when the configuration information includes the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information, the terminal can autonomously calculate the Doppler frequency drift of the feeder link based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information.

[0282] As an alternative method for determining Doppler frequency drift, when the configuration information includes a second indication of the Doppler frequency drift of the feeder link, the terminal can directly determine the Doppler frequency drift based on this second indication. For example, if the network device indicates the Doppler frequency drift in the configuration information, the terminal can directly determine the Doppler frequency drift of the feeder link based on the network indication.

[0283] As another optional method for determining Doppler frequency offset, the terminal can determine the Doppler frequency drift based on time offset compensation related parameters in the configuration information. Optionally, the time offset compensation related parameters can be at least one of the common TA of the feeder link, common TA drift, and common TA drift change rate.

[0284] Optionally, the terminal can determine the Doppler frequency drift of the feeder link based on the common TA drift rate and the carrier frequency of the feeder link. For example, when the configuration information includes a fifth indication of the common TA drift rate and the carrier frequency of the feeder link, the common TA drift rate is determined according to the fifth indication, and the Doppler frequency drift of the feeder link is derived by combining it with the carrier frequency of the feeder link.

[0285] Furthermore, in some embodiments, the frequency offset compensation parameter may specifically include at least one of the uplink frequency offset compensation parameter and the downlink frequency offset compensation parameter.

[0286] In some embodiments, one of the above-mentioned schemes for determining frequency offset compensation parameters to perform feeder link frequency offset compensation can be predefined in the protocol. The terminal performs frequency offset compensation parameter determination based on configuration information according to the predefined scheme, and performs feeder link frequency offset compensation according to the frequency offset compensation parameters. Optionally, the protocol can pre-configure support for either a scheme based on autonomous calculation based on ground base station location, satellite ephemeris information, etc., or a scheme based on network-directly indicated Doppler parameters. If neither is configured, the terminal does not need to perform feeder link frequency offset compensation. In addition, uplink and downlink transmission can adopt independent parameter configuration methods, for example, the uplink can adopt an autonomous calculation scheme, and the downlink can adopt a network indication scheme.

[0287] In some embodiments, when the terminal simultaneously supports uplink frequency offset pre-compensation and downlink frequency offset post-compensation for the feeder link, if the network device only configures a carrier frequency in one transmission direction, the terminal does not perform frequency offset compensation in the unconfigured transmission direction. For example, if the network device only configures the feeder link uplink carrier frequency but not the feeder link downlink carrier frequency, the terminal will not perform downlink frequency offset post-compensation for the feeder link. Alternatively, the terminal may perform compensation based on the carrier frequency of another transmission direction. For example, if the network device does not configure the feeder link downlink carrier frequency but configures the feeder link uplink carrier frequency, the terminal performs downlink frequency offset post-compensation for the feeder link based on the uplink carrier frequency configured by the network device; or, if the network device does not configure the feeder link uplink carrier frequency but configures the feeder link downlink carrier frequency, the terminal performs uplink frequency offset pre-compensation for the feeder link based on the downlink carrier frequency configured by the network device.

[0288] In some embodiments, the terminal may determine the TA pre-compensation value of the feeder link based on at least one parameter in the configuration information in several optional ways:

[0289] As an optional method for determining the TA pre-compensation value, when the configuration information includes the location information of the ground base station, satellite ephemeris information, and epoch time information, the terminal can autonomously calculate the TA pre-compensation value of the feeder link based on the location information of the ground base station, satellite ephemeris information, and epoch time information.

[0290] For example, based on the location information of the ground base station, satellite ephemeris information, epoch time information, etc., the terminal can calculate the distance between the ground base station and the satellite at a specific moment (such as epoch time), and thus perform uplink TA pre-compensation on the feeder link.

[0291] As another optional method for determining the TA pre-compensation value, the terminal may first determine at least one of the common TA, common TA drift, and common TA drift change rate of the feeder link based on the configuration information; and then determine the TA pre-compensation value of the feeder link based on the common TA, common TA drift, and common TA drift change rate.

[0292] In one alternative method for determining the common TA of a feeder link, the terminal may determine the common TA of the feeder link based on a third instruction in the configuration information.

[0293] In some examples, the third indication includes at least one of the following parameters for determining the public TA:

[0294] (1) Propagation delay between ground base station and satellite. For example, network equipment indicates the propagation delay at a specific time (such as epoch time) in the configuration information, and the terminal can directly determine the common TA of the feeder link based on the propagation delay.

[0295] (2) The distance between the ground base station and the satellite. For example, the network device indicates this distance at a specific time (such as epoch time) in the configuration information. The terminal can calculate the propagation delay between the ground base station and the satellite at a specific time based on this distance, thereby obtaining the TA value between the ground base station and the satellite at a specific time, that is, the common TA of the feeder link.

[0296] (3) Elevation angle between the ground base station and the satellite. For example, the network device indicates the elevation angle at a specific time (such as epoch time) in the configuration information. Based on the elevation angle between the ground base station and the satellite at that specific time, as well as the satellite orbital altitude information, the terminal calculates the propagation distance between the ground base station and the satellite at that specific time, and then infers the propagation delay, thereby calculating the TA value between the ground base station and the satellite at that specific time, which is the common TA of the feeder link.

[0297] In one alternative method for determining the common TA drift of a feeder link, the terminal can determine the common TA drift of the feeder link based on a fourth indication in the configuration information. For example, if the network device indicates common TA drift in the configuration information, the terminal can directly determine the common TA drift of the feeder link based on the network indication.

[0298] In another alternative method for determining the common TA drift of a feeder link, the terminal can also derive the common TA drift of the feeder link based on frequency offset compensation parameters, which can be determined based on configuration information issued by the network device.

[0299] As an example, the common TA drift of the feeder link can be derived based on the Doppler frequency offset and the carrier frequency of the feeder link. The Doppler frequency offset of the feeder link can be obtained based on any of the aforementioned optional methods for determining the Doppler frequency offset.

[0300] In one alternative method for determining the common TA drift rate of a feeder link, the terminal can determine the common TA drift rate of the feeder link according to the fifth indication in the configuration information. For example, the network device indicates the common TA drift rate in the configuration information, and the terminal can directly determine the common TA drift rate of the feeder link according to the network indication.

[0301] In another alternative method for determining the common TA drift rate of the feeder link, the terminal can also derive the common TA drift rate of the feeder link based on the frequency offset compensation parameter, which can be determined based on the configuration information issued by the network device.

[0302] As an example, the terminal can derive the common TA drift rate of the feeder link based on the Doppler frequency drift and the carrier frequency of the feeder link. The Doppler frequency drift of the feeder link can be obtained based on any of the aforementioned optional methods for determining the Doppler frequency offset.

[0303] In some embodiments, for implicit indications of configuration information, parsing of specific parameter combinations, and behavior determination, the terminal can also determine the compensation behavior in the following ways:

[0304] (1) If the network device does not configure the carrier frequency of the feeder link, but configures other parameters (such as the location of the ground base station, satellite ephemeris information, etc.), the terminal implicitly indicates that it will only perform uplink time offset pre-compensation of the feeder link at this time, and will not perform uplink frequency offset pre-compensation.

[0305] (2) If the network device is configured with parameters other than the uplink carrier frequency, the terminal will not perform uplink frequency offset pre-compensation, but will only perform uplink time offset pre-compensation and downlink frequency offset post-compensation; or the terminal will reuse the downlink carrier frequency to perform uplink frequency offset pre-compensation. If the downlink carrier frequency is not configured but other parameters are configured, the terminal may not perform downlink frequency offset post-compensation, or may perform downlink frequency offset post-compensation based on the uplink carrier frequency.

[0306] (3) For specific parameter combinations, the terminal can perform joint derivation: For example, when the configuration information includes epoch time, TA drift, Doppler frequency drift, carrier frequency, and common TA, the terminal calculates the TA drift change rate based on the Doppler frequency drift and carrier frequency, and then calculates the time offset based on the TA drift and common TA; at the same time, it inversely deduces the Doppler frequency offset based on the TA drift and carrier frequency, and calculates the frequency offset based on the Doppler frequency drift. Conversely, when the configuration information includes epoch time, Doppler frequency offset, TA drift change rate, carrier frequency, and common TA, the terminal calculates the TA drift based on the Doppler frequency offset and carrier frequency, and then calculates the time offset; at the same time, it inversely deduces the Doppler frequency drift based on the TA drift change rate and carrier frequency, and calculates the frequency offset based on the Doppler frequency offset.

[0307] (4) The terminal can also determine whether to perform uplink TA pre-compensation based on other parameters (such as the location of the uplink synchronization reference point, whether the operating mode is transparent or regenerative). For example, uplink TA pre-compensation for the feeder link is only performed when the terminal determines that the operating mode is transparent and the uplink synchronization reference point is located on the ground network equipment side; if the reference point is located on the satellite or the operating mode is regenerative, the terminal will not perform uplink TA pre-compensation even if the network is configured with relevant parameters.

[0308] (5) The terminal can perform time offset and frequency offset compensation based on independent parameter sets. For example, the time offset parameter set is ground base station location information + satellite ephemeris information + epoch time information, or public TA related information + epoch time information, while the frequency offset parameter set is independently Doppler frequency offset + Doppler frequency drift + epoch time information.

[0309] In step S2203, the terminal performs frequency offset compensation for the feeder link according to the frequency offset compensation parameters, and performs time offset compensation for the feeder link according to the TA pre-compensation value.

[0310] In some embodiments, the terminal may determine frequency offset compensation parameters based on the Doppler frequency offset and / or Doppler frequency drift of the feeder link, and use the frequency offset compensation parameters to perform frequency offset compensation of the feeder link.

[0311] In some embodiments, the terminal may perform uplink frequency offset pre-compensation for the feeder link based on uplink frequency offset compensation parameters. For example, for uplink frequency offset pre-compensation of the feeder link, the terminal needs to determine the Doppler frequency offset and / or Doppler drift in the transmission direction from satellite to ground base station. That is, the uplink frequency offset compensation parameters may include the uplink Doppler frequency offset and / or Doppler drift of the feeder link, and the uplink Doppler frequency offset and / or Doppler drift are used to perform uplink frequency offset pre-compensation.

[0312] In some embodiments, downlink frequency offset compensation for the feeder link can be performed based on downlink frequency offset compensation parameters. For example, for downlink frequency offset compensation for the feeder link, the terminal needs to determine the Doppler frequency offset and / or Doppler drift in the transmission direction from the ground base station to the satellite. That is, the downlink frequency offset compensation parameters may include the downlink Doppler frequency offset and / or Doppler drift of the feeder link, and downlink frequency offset pre-compensation is performed using the downlink Doppler frequency offset and / or Doppler drift.

[0313] In some embodiments, uplink frequency offset pre-compensation of the feeder link can be performed based on uplink frequency offset compensation parameters, and downlink frequency offset post-compensation of the feeder link can be performed based on downlink frequency offset compensation parameters.

[0314] In one alternative example, the network device can independently configure the uplink Doppler frequency offset and the downlink Doppler frequency offset. For example, the uplink Doppler frequency offset parameter can be configured for the terminal to perform uplink frequency offset pre-compensation for the feeder link; and the downlink Doppler frequency offset parameter can be configured for the terminal to perform downlink frequency offset post-compensation for the feeder link.

[0315] In another alternative example, the network device can independently configure uplink Doppler drift and downlink Doppler drift. For example, it can configure uplink Doppler drift parameters for the terminal to perform uplink frequency offset pre-compensation for the feeder link; and configure downlink Doppler drift parameters for the terminal to perform downlink frequency offset post-compensation for the feeder link.

[0316] In another alternative example, the network device can be configured with a common Doppler frequency offset parameter, which is used for both uplink frequency offset pre-compensation and downlink frequency offset post-compensation of the feeder link.

[0317] In another alternative example, the network device can be configured with a common Doppler frequency drift parameter, which is used for both uplink frequency offset pre-compensation and downlink frequency offset post-compensation of the feeder link.

[0318] In some embodiments, when the terminal needs to perform downlink frequency offset compensation for the feeder link and the configuration information is used to determine the uplink frequency offset compensation parameters, the terminal can first determine the uplink frequency offset compensation parameters based on the configuration information, and then derive the downlink frequency offset compensation parameters for the feeder link based on the uplink frequency offset compensation parameters and the ratio between the uplink carrier frequency and the downlink carrier frequency. For example, the terminal can calculate the downlink Doppler frequency offset / frequency drift based on the downlink carrier frequency, the uplink carrier frequency, and the uplink Doppler frequency offset / frequency drift through a proportional relationship. In this way, the network device can issue only the configuration for determining the uplink frequency offset compensation parameters to enable the terminal to perform downlink frequency offset compensation for the feeder link. Especially when the terminal needs to perform uplink and downlink frequency offset compensation, the parameter configuration for one direction can be issued to achieve time offset compensation in both directions, saving network signaling overhead.

[0319] In some embodiments, when the terminal needs to perform uplink frequency offset pre-compensation for the feeder link and the configuration information is used to determine the downlink frequency offset compensation parameters, the terminal first determines the downlink frequency offset compensation parameters based on the configuration information. Then, based on the downlink frequency offset compensation parameters and the ratio between the uplink carrier frequency and the downlink carrier frequency, the terminal derives the uplink frequency offset pre-compensation parameters for the feeder link. For example, the terminal calculates the uplink Doppler frequency offset / frequency drift based on the uplink carrier frequency, downlink carrier frequency, and downlink Doppler frequency offset / frequency drift through a proportional relationship, and performs uplink TA pre-compensation calculation accordingly. In this way, the network device can issue only the configuration for determining the downlink frequency offset compensation parameters to enable the terminal to perform uplink frequency offset pre-compensation for the feeder link. Especially when the terminal needs to perform uplink and downlink frequency offset compensation, the parameter configuration for one direction can be issued to achieve time offset compensation in both directions, saving network signaling overhead. If the network device does not configure either the uplink or downlink carrier frequency, the terminal can choose not to perform frequency offset compensation or time offset pre-compensation in the corresponding direction based on the protocol agreement.

[0320] In some embodiments, the terminal may perform only partial time offset and / or frequency offset compensation for the feeder link, with the remaining portion compensated by the network device.

[0321] For example, for frequency offset compensation, the terminal only compensates for Doppler frequency offset, while the frequency offset change caused by Doppler frequency drift is compensated by the ground base station.

[0322] For example, in time offset compensation, the terminal only compensates for the common TA, while the delay changes caused by common TA drift and the rate of change of common TA drift are compensated by the ground base station.

[0323] For example, for time offset compensation, the terminal only performs delay compensation for the common TA and the delay caused by common TA drift, and the common TA drift rate is compensated by the ground base station.

[0324] For example, for time offset compensation, the terminal only performs TA pre-compensation for common TA drift and the rate of change of common TA drift, while the common TA is compensated by the ground base station.

[0325] In some embodiments, for the time-frequency compensation process, the terminal performs time offset compensation of the feeder link based on the TA pre-compensation value.

[0326] In some embodiments, if the configuration information sent by the network device does not include information for determining time offset compensation parameters (such as TA pre-compensation value), then the terminal will not perform time offset compensation for the feeder link.

[0327] In some embodiments, the above-described time-frequency offset compensation mechanism may be applied to at least one of the following GNSS operating modes:

[0328] GNSS-based working mode; GNSS flexible / degraded working mode; No GNSS working mode.

[0329] It is understood that this embodiment is only an illustrative example. In practical applications, the execution order of each step and the specific values ​​of each parameter can be flexibly adapted according to the protocol version and deployment requirements, and all of these fall within the protection scope of this solution.

[0330] The communication method for non-terrestrial networks involved in the embodiments of this disclosure may include at least one of steps S2201 to S2203. For example, step S2201 may be implemented as a standalone embodiment; or step S2202 may be implemented as a standalone embodiment; or step S2203 may be implemented as a standalone embodiment. In addition, some or all of the steps in steps S2201 to S2203 may be combined as standalone embodiments, and the embodiments of this disclosure do not limit this.

[0331] Optionally, the alternative implementations of steps S2201 to S2203 can be found in other alternative implementations involved in steps S2101 to S2103, which will not be repeated here.

[0332] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0333] This disclosure proposes an NTN communication scheme in which the terminal performs frequency offset compensation and time offset compensation of the feeder link based on the configuration information issued by the network device. This not only improves the accuracy of the frequency and time offset compensation of the feeder link, thereby improving the uplink and downlink synchronization accuracy and communication quality of the feeder link, but also reduces the compensation processing load of the ground base station under the transparent payload architecture.

[0334] Figure 2C This is a schematic diagram illustrating a communication method for a non-terrestrial network according to an embodiment of this disclosure. (For illustrative purposes) Figure 1 Another alternative implementation of the communication system, this method can be used to enable the terminal to perform time offset compensation on the feeder link, such as... Figure 2C As shown, the method includes the following steps:

[0335] Step S2301: The network device sends configuration information to the terminal.

[0336] In some embodiments, configuration information sent by a network device can be used to determine the time offset compensation parameters of a feeder link, which are used for time offset compensation of the feeder link.

[0337] In some embodiments, the time offset compensation parameter may include a TA pre-compensation value for the feeder link, which is used for time offset compensation of the feeder link.

[0338] In some embodiments, the network device may transmit configuration information via at least one bearer, such as terminal-specific RRC signaling, system messages, or beam-specific signaling. In some examples, if the configuration information is transmitted to the terminal via a system message bearer, the system message may include at least one of SIB1, SIB19, or OSI.

[0339] In some examples, network devices may send configuration information at the cell level, for example, configuration information that is applicable to all terminals within the cell.

[0340] In some examples, the time offset compensation parameters determined based on configuration information can be cell-level parameters.

[0341] In some embodiments, the configuration information sent by the network device includes at least one of the following C1 to C9:

[0342] C1. Location information of ground base stations.

[0343] C2, the carrier frequency of the feeder link.

[0344] C3. Satellite ephemeris information.

[0345] C4. Era Time Information.

[0346] C5, the first indicator of Doppler frequency offset in the feeder link.

[0347] C6, the second indicator of Doppler frequency drift in the feeder link.

[0348] C7, the third indication of the common TA of the feeder link.

[0349] C8, the fourth indicator of common TA drift in the feeder link.

[0350] C9, the fifth indicator of the common TA drift rate of the feeder link.

[0351] The explanations for C1 to C9 above can be found in the corresponding descriptions of A1 to A9 in step S2101, and will not be repeated here.

[0352] In some embodiments, the configuration information may only include frequency offset compensation-related parameters, such as at least one of C1 to C6. The terminal can then derive time offset compensation parameters based on the frequency offset compensation-related parameters, and subsequently perform time offset compensation on the feeder link based on the time offset compensation parameters.

[0353] In step S2302, the terminal receives configuration information sent by the network device and determines the TA pre-compensation value of the feeder link based on the configuration information.

[0354] As an optional method for determining the TA pre-compensation value, the terminal may first determine at least one of the common TA, common TA drift, and common TA drift change rate of the feeder link based on the configuration information; and then determine the TA pre-compensation value of the feeder link based on the common TA, common TA drift, and common TA drift change rate.

[0355] As another optional method for determining the TA pre-compensation value, when the configuration information includes the location information of the ground base station, satellite ephemeris information, and epoch time information, the terminal can autonomously calculate the TA pre-compensation value of the feeder link based on the location information of the ground base station, satellite ephemeris information, and epoch time information.

[0356] For example, based on the location information of the ground base station, satellite ephemeris information, epoch time information, etc., the terminal can calculate the distance between the ground base station and the satellite at the first moment, and thus perform uplink TA pre-compensation on the feeder link.

[0357] As another optional method for determining the TA pre-compensation value, the terminal can also derive the common TA drift of the feeder link based on the frequency offset compensation parameter. This frequency offset compensation parameter can be determined based on the configuration information issued by the network device, and then the terminal determines the TA pre-compensation value of the feeder link based on the common TA drift.

[0358] In one example, the common TA drift of the feeder link can be derived based on the Doppler frequency offset and the carrier frequency of the feeder link, and then the TA pre-compensation value of the feeder link can be determined based on the common TA drift.

[0359] As another optional method for determining the TA pre-compensation value, the terminal can also derive the common TA drift change rate of the feeder link based on the frequency offset compensation parameter. This frequency offset compensation parameter can be determined based on the configuration information issued by the network device, and then the terminal determines the TA pre-compensation value of the feeder link based on the common TA drift change rate.

[0360] In one example, the common TA drift rate of the feeder link can be derived based on the Doppler frequency offset and the carrier frequency of the feeder link, and then the TA pre-compensation value of the feeder link can be determined based on the common TA drift rate.

[0361] In step S2303, the terminal performs time offset compensation for the feeder link based on the TA pre-compensation value.

[0362] In some embodiments, for the time-frequency compensation process, the terminal performs time offset compensation of the feeder link based on the TA pre-compensation value.

[0363] In some embodiments, the terminal may perform only part of the time offset compensation for the feeder link, with the remaining part compensated by the network device.

[0364] For example, for time offset compensation, the terminal only compensates for the common TA, while the delay changes caused by common TA drift and the rate of change of common TA drift are compensated by the ground base station.

[0365] For example, for time offset compensation, the terminal only performs delay compensation for the common TA and the delay caused by common TA drift, and the common TA drift rate is compensated by the ground base station.

[0366] For example, for time offset compensation, the terminal only performs TA pre-compensation for common TA drift and the rate of change of common TA drift, while the common TA is compensated by the ground base station.

[0367] In some embodiments, the above-described time-frequency offset compensation mechanism may be applied to at least one of the following GNSS operating modes:

[0368] GNSS-based working mode; GNSS flexible / degraded working mode; No GNSS working mode.

[0369] It is understood that this embodiment is only an illustrative example. In practical applications, the execution order of each step and the specific values ​​of each parameter can be flexibly adapted according to the protocol version and deployment requirements, and all of these fall within the protection scope of this solution.

[0370] The communication method for non-terrestrial networks involved in the embodiments of this disclosure may include at least one of steps S2301 to S2303. For example, step S2301 may be implemented as a standalone embodiment; or step S2302 may be implemented as a standalone embodiment; or step S2303 may be implemented as a standalone embodiment. In addition, some or all of the steps in steps S2301 to S2303 may be combined as standalone embodiments, and the embodiments of this disclosure do not limit this.

[0371] Optionally, the alternative implementations of steps S2301 to S2303 can be found in steps S2101 to S2103. Other alternative implementations involved in steps S2201 to S2203 will not be described here.

[0372] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0373] This disclosure proposes an NTN communication scheme in which the terminal performs time offset compensation for the feeder link based on configuration information issued by the network device. Specifically, based on the frequency offset compensation parameters determined by the configuration information, the time offset compensation parameters for the feeder link can be further derived, and then used to perform time offset compensation for the feeder link. In this way, the network device only needs to configure the frequency offset compensation parameters to achieve time offset compensation for the feeder link by the terminal. There is no need to configure the time offset compensation parameters separately, which can save network signaling transmission overhead.

[0374] Figure 3A This is a schematic diagram illustrating a communication method for a non-terrestrial network according to an embodiment of this disclosure. For example... Figure 3A As shown, the method includes:

[0375] Step S3101: The terminal receives configuration information sent by the network device.

[0376] In some embodiments, configuration information is used to determine the frequency offset compensation parameters and / or time offset compensation parameters (such as TA pre-compensation values) of the feeder link.

[0377] In some examples, the feeder link is a transmission link between a ground base station and a satellite.

[0378] In some examples, the configuration information includes at least one of the following:

[0379] The location information of the ground base station; the carrier frequency of the feeder link; satellite ephemeris information; epoch time information; a first indication of the Doppler frequency offset of the feeder link; a second indication of the Doppler frequency drift of the feeder link; a third indication of the common TA of the feeder link; a fourth indication of the common TA drift of the feeder link; and a fifth indication of the rate of change of the common TA drift of the feeder link.

[0380] In step S3102, the terminal determines the frequency offset compensation parameters of the feeder link based on the configuration information.

[0381] In some embodiments, the terminal determines the uplink frequency offset compensation parameters according to the configuration information, and determines the downlink frequency offset compensation parameters of the feeder link based on the uplink frequency offset compensation parameters and the ratio between the uplink carrier frequency and the downlink carrier frequency.

[0382] In some embodiments, the terminal determines the downlink frequency offset compensation parameter according to the configuration information, and determines the uplink frequency offset compensation parameter of the feeder link based on the downlink frequency offset compensation parameter and the ratio between the uplink carrier frequency and the downlink carrier frequency.

[0383] In some embodiments, the terminal determines the Doppler frequency offset and / or Doppler frequency drift of the feeder link based on the configuration information; and then determines the frequency offset compensation parameter based on the Doppler frequency offset and / or the Doppler frequency drift.

[0384] In some examples, the terminal determines the Doppler frequency offset based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information.

[0385] In some examples, the terminal determines the Doppler frequency offset based on the first indication.

[0386] In some examples, the terminal determines the Doppler frequency offset based on the common TA drift of the feeder link and the carrier frequency of the feeder link.

[0387] In some examples, the terminal determines the Doppler frequency drift based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information.

[0388] In some examples, the terminal determines the Doppler frequency drift based on the second instruction.

[0389] In some examples, the terminal determines the Doppler frequency drift based on the common TA drift rate of the feeder link and the carrier frequency of the feeder link.

[0390] In step S3103, the terminal performs frequency offset compensation for the feeder link according to the frequency offset compensation parameters.

[0391] In some embodiments, the frequency offset compensation parameters include at least one of uplink frequency offset compensation parameters and downlink frequency offset compensation parameters.

[0392] In some embodiments, performing frequency offset compensation of the feeder link according to the frequency offset compensation parameters includes at least one of the following:

[0393] The terminal performs uplink frequency offset pre-compensation of the feeder link according to the uplink frequency offset compensation parameters; the terminal performs downlink frequency offset post-compensation of the feeder link according to the downlink frequency offset compensation parameters.

[0394] In some embodiments, the terminal further determines the TA pre-compensation value of the feeder link based on the configuration information; and then performs time offset compensation of the feeder link according to the TA pre-compensation value.

[0395] In some examples, the terminal determines the TA pre-compensation value of the feeder link based on the location information of the ground base station, the satellite ephemeris information, and the epoch time information.

[0396] In some examples, the terminal determines at least one of the common TA, common TA drift, and common TA drift change rate of the feeder link based on the configuration information; then, based on at least one of the common TA, common TA drift, and common TA drift change rate, it determines the TA pre-compensation value of the feeder link.

[0397] In some examples, the terminal determines the common TA based on the third indication, which includes at least one of the following parameters for determining the common TA:

[0398] The propagation delay between the ground base station and the satellite; the distance between the ground base station and the satellite; the elevation angle between the ground base station and the satellite.

[0399] In some examples, the terminal determines the common TA drift based on the fourth instruction; then, it determines the common TA drift based on the Doppler frequency offset of the feeder link and the carrier frequency of the feeder link.

[0400] In some examples, the terminal determines the common TA drift rate of change based on the fifth instruction.

[0401] In some examples, the terminal determines the common TA drift rate based on the Doppler drift of the feeder link and the carrier frequency of the feeder link.

[0402] Optionally, the alternative implementations of steps S3101 to S3103 can be found in other alternative implementations involved in steps S2101 to S2103, S2201 to S2203, and S2301 to S2303, which will not be elaborated here.

[0403] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0404] The communication method for non-terrestrial networks involved in the embodiments of this disclosure may include at least one of steps S3101 to S3103. For example, step S3101 may be implemented as a standalone embodiment; or step S3102 may be implemented as a standalone embodiment; or step S3103 may be implemented as a standalone embodiment. In addition, some or all of the steps in steps S3101 to S3103 may be combined as standalone embodiments, and the embodiments of this disclosure do not limit this.

[0405] This disclosure proposes an NTN communication scheme in which the terminal performs frequency offset compensation of the feeder link based on configuration information issued by the network device. Compared with the terrestrial base station performing the frequency offset compensation of the feeder link entirely, this disclosure allows the terminal to calculate and execute the frequency offset compensation of the feeder link, which can effectively compensate for the Doppler frequency offset caused by the high-speed relative motion between the satellite and the terrestrial base station. This not only improves the accuracy of the feeder link frequency offset compensation, thereby improving the uplink and downlink synchronization accuracy and communication quality of the feeder link, but also reduces the load of frequency offset estimation and compensation processing of the terrestrial base station under the transparent payload architecture.

[0406] Figure 3B This is a schematic diagram illustrating a communication method for a non-terrestrial network according to an embodiment of this disclosure. For example... Figure 3B As shown, the method includes:

[0407] Step S3201: The network device sends configuration information to the terminal.

[0408] In some embodiments, the configuration information is used to determine the frequency offset compensation parameters of the feeder link.

[0409] In some examples, the frequency offset compensation parameters are used for frequency offset compensation of the feeder link.

[0410] In some embodiments, the frequency offset compensation parameters include at least one of uplink frequency offset compensation parameters and downlink frequency offset compensation parameters.

[0411] In some embodiments, the frequency offset compensation of the feeder link includes at least one of the following:

[0412] The uplink frequency offset pre-compensation of the feeder link; the downlink frequency offset post-compensation of the feeder link.

[0413] In some embodiments, the feeder link is a transmission link between a ground base station and a satellite.

[0414] In some embodiments, the configuration information includes at least one of the following:

[0415] The location information of the ground base station; the carrier frequency of the feeder link; satellite ephemeris information; epoch time information; a first indication of the Doppler frequency offset of the feeder link; a second indication of the Doppler frequency drift of the feeder link; a third indication of the common TA of the feeder link; a fourth indication of the common TA drift of the feeder link; and a fifth indication of the rate of change of the common TA drift of the feeder link.

[0416] In some embodiments, the configuration information is used to determine the Doppler frequency offset and / or Doppler frequency drift of the feeder link, and the Doppler frequency offset and / or the Doppler frequency drift is used to determine the frequency offset compensation parameter.

[0417] In some embodiments, the Doppler frequency offset is determined based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information.

[0418] In some embodiments, the Doppler frequency offset is determined based on the first indication.

[0419] In some embodiments, the Doppler frequency offset is determined based on the common TA drift of the feeder link and the carrier frequency of the feeder link.

[0420] In some embodiments, the Doppler frequency drift is determined based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information.

[0421] In some embodiments, the Doppler frequency drift is determined based on the second indication.

[0422] In some embodiments, the Doppler frequency drift is determined based on the common TA drift rate of the feeder link and the carrier frequency of the feeder link.

[0423] In some embodiments, the configuration information is further used to determine the timing advance (TA) pre-compensation value of the feeder link;

[0424] In some examples, the TA pre-compensation value is used for time offset compensation of the feeder link.

[0425] In some embodiments, the TA pre-compensation value of the feeder link is determined based on the location information of the ground base station, the satellite ephemeris information, and the epoch time information.

[0426] In some embodiments, the configuration information is used to determine at least one of the common TA, common TA drift, and common TA drift change rate of the feeder link.

[0427] In some examples, at least one of the common TA, the common TA drift, and the common TA drift change rate is used to determine the TA pre-compensation value of the feeder link.

[0428] In some embodiments, the common TA is determined according to the third indication, the third indication including at least one of the following parameters for determining the common TA:

[0429] The propagation delay between the ground base station and the satellite; the distance between the ground base station and the satellite; the elevation angle between the ground base station and the satellite.

[0430] In some embodiments, the common TA drift is determined according to the fourth indication.

[0431] In some embodiments, the common TA drift is determined based on the Doppler frequency offset of the feeder link and the carrier frequency of the feeder link.

[0432] In some embodiments, the common TA drift rate of change is determined according to the fifth indication.

[0433] In some embodiments, the common TA drift rate is determined based on the Doppler frequency drift of the feeder link and the carrier frequency of the feeder link.

[0434] Optionally, alternative implementations of step S3201 can be found in steps S2101 to S2103, S2201 to S2203, S2301 to S2303, and other alternative implementations involved in steps S3101 to S3103, which will not be elaborated here.

[0435] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0436] This disclosure proposes an NTN communication scheme in which the terminal performs frequency offset compensation of the feeder link based on configuration information issued by the network device. Compared with the terrestrial base station performing the frequency offset compensation of the feeder link entirely, this disclosure allows the terminal to calculate and execute the frequency offset compensation of the feeder link, which can effectively compensate for the Doppler frequency offset caused by the high-speed relative motion between the satellite and the terrestrial base station. This not only improves the accuracy of the feeder link frequency offset compensation, thereby improving the uplink and downlink synchronization accuracy and communication quality of the feeder link, but also reduces the load of frequency offset estimation and compensation processing of the terrestrial base station under the transparent payload architecture.

[0437] The following are some exemplary specific solutions proposed in the embodiments of this disclosure:

[0438] In some embodiments of this disclosure, a compensation mechanism is proposed for the feeder link (i.e., the transmission link between the ground base station and the satellite) in transparent payload scenarios of non-terrestrial network (NTN) communication (i.e., scenarios where the base station is located on the ground). Specifically, the terminal compensates for at least one of the following aspects of the feeder link:

[0439] Frequency offset compensation for feeder links; time offset compensation for feeder links.

[0440] Optionally, based on the above pre-compensation mechanism, this disclosure provides at least one of the following designs to perform compensation for the feeder link:

[0441] Regarding the signaling configuration method, the network device (base station) can configure the first parameter required for feeder link compensation to the terminal based on at least one of UE-dedicated RRC signaling, System Message Block 1 (SIB1), System Message Block 19 (SIB19), other system messages (OSI), and beam-specific signaling. The first parameter can be a cell-specific parameter.

[0442] In terms of specific compensation schemes, the compensation of the feeder link includes at least one of the following directions or schemes:

[0443] Direction 1: The terminal only performs frequency offset pre-compensation for the feeder link.

[0444] Option 1: The terminal performs frequency offset compensation based on at least one of the following first parameters:

[0445] The location of the base station in the ground can optionally be a coarse location, for example, with a precision of 2 km. For example, a configuration field design for a coarse location is as follows: an optional octet string field is used. In this field, the first bit of the first (or leftmost) octet contains the most significant bit (MSB). The least significant bits (LSB) of the latitude and longitude are set to 0 to meet a precision granularity requirement of approximately MM kilometers (e.g., M = 2M = 2, i.e., 2 km). The specific number of least significant bits set to 0 to meet the precision requirement is determined by the implementation of the ground base station. Alternatively, the location of the ground base station can be an accurate location. For example, a configuration field design for an accurate location also uses the above Ellipsoid-Point structure, but without truncating the least significant bit to zero.

[0446] (2) The carrier frequency of the feeder link, wherein the frequency offset compensation of the feeder link includes at least one of the following:

[0447] Upward pre-compensation, downward post-compensation.

[0448] Optionally, for uplink pre-compensation (from the terminal's perspective), the carrier frequency is the carrier frequency used in the propagation direction of "satellite → ground base station". That is, the parameter includes the uplink carrier frequency (ULcarrier frequency of the feeder link).

[0449] Optionally, for downlink transmission (from the terminal's perspective), the terminal can also perform post-compensation for the Doppler frequency offset of the feeder link. In this case, the carrier frequency is the carrier frequency used in the propagation direction of "ground base station → satellite". That is, the parameter includes the downlink carrier frequency (DL carrier frequency of the feeder link).

[0450] Optionally, the terminal can perform uplink frequency offset pre-compensation and downlink frequency offset post-compensation simultaneously. However, for uplink and downlink frequency offset compensation, the base station is only configured with a common carrier frequency.

[0451] (3) Epoch time.

[0452] (4) Satellite Ephemeris Information: Based on the location of the ground base station, the satellite's ephemeris information, and the carrier frequency of the feeder link, the terminal can calculate the Doppler offset and Doppler drift / Doppler rate caused by satellite movement, thereby compensating for the large overall Doppler offset caused by the rapid movement of the satellite on the feeder link.

[0453] Alternatively, if the base station is not configured with the first parameter mentioned above, the terminal will not perform frequency offset compensation for the feeder link.

[0454] Optionally, the terminal can simultaneously perform uplink pre-compensation and downlink post-compensation for the feeder link. If the base station has not configured the carrier frequency for one of the transmission directions (the first transmission direction), the terminal will exhibit at least one of the following behaviors:

[0455] Behavior A: Do not perform frequency offset compensation in the transmission direction;

[0456] Action B: Perform frequency offset compensation for the first transmission direction based on the carrier frequency of the other transmission direction. For example, if the base station has not configured a downlink (from the terminal's perspective) carrier frequency for the feeder link but has configured an uplink carrier frequency for the feeder link, the terminal performs downlink frequency offset compensation for the feeder link based on the uplink carrier frequency configured by the base station, or vice versa.

[0457] Option 2: The terminal performs frequency offset compensation based on at least one of the following first parameters:

[0458] (1) Doppler offset of the feeder link, wherein the Doppler offset is the frequency offset between the ground base station and the satellite at a first moment due to the rapid movement of the satellite. Optionally, the first moment may also be configured or indicated to the terminal by the base station, for example, as epoch time.

[0459] Optionally, the frequency offset compensation includes at least one of the following: uplink frequency offset pre-compensation of the feeder link, and downlink frequency offset post-compensation of the feeder link.

[0460] Based on this, for uplink frequency offset pre-compensation of the feeder link, the terminal needs to determine the Doppler frequency offset of the transmission direction of the feeder link "satellite → ground base station". That is, the parameter includes the uplink Doppler offset of the feeder link, which is from the perspective of the terminal.

[0461] For downlink compensation of the feeder link, the terminal needs to determine the Doppler frequency offset of the transmission direction of the feeder link "ground base station → satellite". That is, the parameter includes the downlink Doppler offset of the feeder link. The downlink is from the perspective of the terminal.

[0462] Optionally, the terminal can simultaneously perform uplink frequency offset pre-compensation and downlink frequency offset post-compensation for the feeder link. For uplink frequency offset compensation and downlink frequency offset compensation, the base station is configured with a common doppler offset.

[0463] (2) Doppler drift of the feeder link, which is the rate at which the Doppler frequency shift changes continuously over time, caused by the relative acceleration of the satellite relative to the ground base station.

[0464] Optionally, the frequency offset compensation includes at least one of the following: uplink frequency offset pre-compensation of the feeder link, and downlink frequency offset post-compensation of the feeder link.

[0465] Based on this, for uplink frequency offset pre-compensation of the feeder link, the terminal needs to determine the Doppler frequency drift in the transmission direction of the feeder link "satellite → ground base station", that is, the parameters include the uplink Doppler drift of the feeder link.

[0466] For downlink frequency offset compensation of the feeder link, the terminal needs to determine the Doppler frequency drift in the transmission direction of the feeder link "ground base station → satellite". That is, the parameter includes the downlink doppler drift of the feeder link. The downlink is from the perspective of the terminal.

[0467] Optionally, the terminal can simultaneously perform uplink frequency offset pre-compensation and downlink frequency offset post-compensation for the feeder link. For uplink frequency offset compensation and downlink frequency offset compensation, the base station configures a common Doppler drift of the feeder link.

[0468] That is, the terminal calculates the overall Doppler frequency shift caused by satellite movement based on Doppler frequency offset and Doppler frequency drift, thereby compensating for the large Doppler frequency offset caused by the rapid movement of the satellite on the feeder link.

[0469] Alternatively, if the base station is not configured with at least one of the above first parameters, the terminal will not perform frequency offset compensation for the feeder link.

[0470] Alternatively, the terminal can simultaneously perform uplink pre-compensation and downlink post-compensation for the feeder link. If the base station does not configure the first parameter for one of the transmission directions (the first transmission direction), the terminal will exhibit at least one of the following behaviors:

[0471] Action A: Do not perform frequency offset compensation in the first transmission direction;

[0472] Action B: Frequency offset compensation in the first transmission direction is performed based on a first parameter (at least one of Doppler frequency offset and Doppler frequency drift) in another transmission direction. For example, if the base station has not configured downlink (from the terminal's perspective) Doppler frequency offset and Doppler frequency drift for the feeder link, but has configured uplink transmission direction Doppler frequency offset and Doppler frequency drift for the feeder link, the terminal performs downlink frequency offset compensation for the feeder link based on the first parameter configured for uplink transmission by the base station, or vice versa.

[0473] Option 3: The protocol is pre-configured to support the configuration of either Option 1 or Option 2's first parameter set. If neither is configured, the terminal does not need to perform frequency offset compensation for the feeder link.

[0474] Optionally, uplink and downlink transmissions can have independent parameter configuration methods. For example, uplink transmission can use Scheme 1 to configure the first parameter, while downlink transmission can use Scheme 2 to configure the first parameter.

[0475] Direction 2: The terminal supports time offset and frequency offset compensation for the feeder link.

[0476] For time-frequency offset compensation in FeederLink, at least one of the following schemes exists:

[0477] Direction 2-1: The terminal performs uplink time offset and frequency offset compensation based on at least some of the shared first parameters.

[0478] In other words, the value of frequency offset can be implicitly determined through time offset correlation parameters, or the value of time offset correlation can be implicitly determined through frequency offset correlation parameters. For example, TA drift can be determined by using Doppler frequency offset and carrier frequency, and TA drift variation can be determined by using Doppler frequency drift and carrier frequency; or conversely, Doppler frequency offset can be determined by using TA drift and carrier frequency, and Doppler frequency drift can be determined by using TA drift variation and carrier frequency, etc.

[0479] Option 1: In Option 1 for the same direction, the terminal performs time offset compensation and frequency offset compensation for the feeder link based on at least one of the following parameters: the location of the ground base station, the carrier frequency of the feeder link (including uplink carrier frequency, downlink carrier frequency or common carrier frequency, or the carrier frequency corresponding to the uplink frequency offset pre-compensation after downlink frequency offset compensation), satellite ephemeris information, and epoch time / second time (this parameter is the timestamp information of the time when at least one of the above parameters is generated).

[0480] For frequency offset compensation: Based on the location of the ground base station, the satellite's ephemeris information, timestamp information, and the carrier frequency of the feeder link, the terminal calculates the Doppler frequency offset and Doppler frequency drift caused by satellite movement, thereby compensating for the overall Doppler frequency offset caused by the rapid movement of the satellite on the feeder link during the first moment of transmission.

[0481] For time offset compensation: The terminal can calculate the distance between the ground base station and the satellite at the first moment based on the location information of the ground base station, satellite ephemeris information, timestamp information (e.g., epoch time), so that uplink TA pre-compensation can be performed on the feeder link at the first moment. The uplink is the uplink transmission from the perspective of the station terminal.

[0482] Optionally, the following considerations apply to the configuration of carrier frequency: if the base station does not configure the carrier frequency of the feeder link, but configures other first parameters, it implicitly indicates that only uplink time offset pre-compensation of the feeder link is performed at this time, and uplink frequency offset pre-compensation of the feeder link is not performed.

[0483] Optionally, if the base station is configured with parameters other than the feeder link uplink carrier frequency, then at least one of the following resolution methods is available:

[0484] Option 1: Do not perform uplink frequency offset pre-compensation for the feeder link, but perform uplink time offset pre-compensation and downlink frequency offset post-compensation;

[0485] Option 2: Do not perform uplink time offset and frequency offset pre-compensation on the feeder link, and perform downlink frequency offset post-compensation;

[0486] Option 3: The terminal simultaneously performs uplink time offset and frequency offset pre-compensation on the feeder link, as well as downlink frequency offset post-compensation. Additionally, the terminal performs uplink frequency offset pre-compensation based on the downlink carrier frequency of the feeder link.

[0487] Optionally, if the base station is configured with parameters other than the feeder link downlink carrier frequency, then at least one of the following resolution methods is available:

[0488] Option 1: Do not perform downlink frequency offset compensation for the feeder link;

[0489] Option 2: Perform downlink frequency offset compensation based on the uplink carrier frequency of the feeder link.

[0490] Other design references can be found in Scheme 1 of Direction 1.

[0491] Option 2: The terminal performs time and frequency offset compensation on the feeder link based on at least one of the following first parameters: Doppler frequency offset (value can be positive or negative, and uplink and downlink can have independent configuration parameters), Doppler frequency drift (value can be positive or negative, and uplink and downlink can have independent configuration parameters), carrier frequency, common TA / first distance / first elevation angle + ephemeris information, epoch time / second moment.

[0492] Wherein, the common TA is the bidirectional propagation delay between the ground base station and the satellite at the second moment, or the unidirectional propagation delay between the ground base station and the satellite at the second moment; the first distance is the straight-line distance between the ground base station and the satellite at the second moment, and the propagation delay can be calculated based on the first distance to obtain the common TA value; the first elevation angle is the elevation angle between the ground base station and the satellite at the second moment, and the satellite orbital altitude can be obtained based on the satellite ephemeris information, and the propagation distance can be calculated by combining the first elevation angle to infer the propagation delay and obtain the common TA value.

[0493] For time offset compensation: the TA drift at the first moment is determined by at least one of the following methods:

[0494] Option 1, calculated based on uplink Doppler frequency offset and uplink carrier frequency;

[0495] Option 2 is calculated based on the downlink Doppler frequency offset and the downlink carrier frequency.

[0496] The rate of change of TA drift at the first moment is determined by at least one of the following methods:

[0497] Option 1, calculated based on uplink Doppler frequency drift and uplink carrier frequency;

[0498] Option 2, calculated based on downlink Doppler frequency drift and downlink carrier frequency.

[0499] For example, one possible calculation formula is as follows:

[0500]

[0501] Where t1 represents a specific time, such as the epoch time; Doppler_offset(t1) represents the Doppler frequency offset at time t1, and f c Let t represent the carrier frequency of the feeder link, and TA(t) represent the common TA at time t.

[0502] 2. Second derivative (rate of change of TA drift):

[0503]

[0504] Where t1 represents the reference time, such as the epoch time; Doppler_drift(t1) represents the Doppler frequency drift at time t1, and f c Let t represent the carrier frequency of the feeder link, and TA(t) represent the common TA at time t.

[0505] Furthermore, propagation delay is calculated using TA drift, TA drift rate of change, common TA, and epoch time (e.g., unidirectional propagation delay is calculated using a formula; the bidirectional propagation delay of the feeder link is the value of the feeder link TA pre-compensation to be performed by the terminal). See the following formula for details:

[0506]

[0507] Among them, Delay common (t) represents the TA pre-compensation at time t, TA common Represents public TA, TA commonDrift Indicates common TA drift, TA commonDriftVariant t represents the rate of change of common TA drift. epoch Indicates epochal time.

[0508] Optionally, the frequency offset compensation method is the same as Scheme 2 in the same direction as 1.

[0509] Optionally, if any parameter such as carrier frequency or common TA determination is not configured, the terminal is implicitly instructed not to perform bias pre-compensation for the feeder link.

[0510] Option 3: The terminal performs time offset and frequency offset compensation on the feeder link based on at least one of the following first parameters:

[0511] Common TA / first distance / first elevation angle + satellite ephemeris information; Common TA drift; Common TA drift variation; carrier frequency; epoch time.

[0512] For time offset pre-compensation, refer to the relevant formula, where delay is the one-way propagation delay of the feeder link (between ground network equipment and satellite).

[0513]

[0514] Among them, Delay common (t) represents the TA pre-compensation at time t, TA common Represents public TA, TA commonDrift Indicates common TA drift, TA commonDriftVariantt represents the rate of change of common TA drift. epoch Indicates epochal time.

[0515] For frequency offset pre-compensation: Specifically, at the first moment, the terminal calculates the Doppler frequency offset based on the common TA drift and the carrier frequency, and calculates the Doppler frequency drift based on the common TA drift change rate. The terminal calculates the Doppler frequency offset at the first moment based on at least one parameter, including the Doppler frequency offset, Doppler frequency drift, and epoch time. For uplink and downlink transmissions, optionally, the carrier frequency can be an independent value. See the following formula for details:

[0516]

[0517] Among them, f d (t1) represents the Doppler frequency shift at time t1, f c TA represents the carrier frequency of the feeder link. commonDrift Indicates common TA drift, TA commonDriftVariant t represents the rate of change of common TA drift. epoch Indicates epochal time.

[0518] Optionally, if the downlink carrier frequency of the feeder link is not configured, the terminal is implicitly instructed not to perform downlink frequency offset compensation.

[0519] Optionally, in this mode, if the base station is not configured with common TA / first distance / first elevation angle + satellite ephemeris information, it means that the terminal does not perform uplink time offset pre-compensation for the feeder link.

[0520] Option 4: The terminal performs time offset and frequency offset compensation on the feeder link based on at least one of the following first parameters:

[0521] Second moment / epoch time, TA drift, Doppler frequency drift, carrier frequency, common TA / first distance / first elevation angle + ephemeris information (the definitions of common TA, first distance, and first elevation angle are the same as in Scheme 2).

[0522] Uplink time-off pre-compensation: The terminal calculates the TA drift rate based on the uplink / downlink Doppler frequency drift and the uplink / downlink carrier frequency. Further, based on the TA drift rate, TA drift, common TA, and epoch time, the TA pre-compensation value for the feeder link at the first moment is calculated.

[0523] Frequency offset compensation: For downlink frequency offset post-compensation, the downlink Doppler frequency offset is calculated based on the downlink carrier frequency and TA drift. Based on the downlink Doppler frequency drift, downlink Doppler frequency offset, and epoch time, the Doppler frequency offset at the first moment is calculated, and downlink Doppler frequency offset post-compensation is performed on the feeder link. The downlink Doppler frequency drift can be configured by the base station or determined based on the downlink carrier frequency, uplink carrier frequency, and uplink Doppler frequency drift using the scheme described in point four. For uplink frequency offset pre-compensation, the uplink Doppler frequency offset is calculated based on the uplink carrier frequency and TA drift. Based on the uplink Doppler frequency drift, uplink Doppler frequency offset, and epoch time, the uplink Doppler frequency offset at the first moment is calculated, and uplink Doppler frequency offset pre-compensation is performed on the feeder link.

[0524] Option 5: The terminal performs time and frequency offset compensation on the feeder link based on at least one of the following first parameters: second time / epoch time, Doppler frequency offset, TA drift rate, carrier frequency, common TA / first distance / first elevation angle + ephemeris information (defined as in Option 2).

[0525] Uplink timing offset pre-compensation: The terminal calculates the TA drift based on the downlink / uplink Doppler frequency offset and the downlink / uplink carrier frequency, and calculates the propagation delay of the feeder link at the first moment based on the TA drift, TA drift change rate, common TA, and epoch time, thereby determining the timing advance of the feeder link that needs pre-compensation.

[0526] Frequency offset compensation: For downlink frequency offset post-compensation, the terminal calculates the downlink Doppler frequency drift based on the downlink carrier frequency and TA drift change rate. Based on the downlink Doppler frequency drift, downlink Doppler frequency offset, and epoch time, it calculates the Doppler frequency offset at the first moment and performs downlink frequency offset post-compensation based on the Doppler frequency offset. The downlink Doppler frequency offset can be configured by the base station or determined by the terminal based on the uplink Doppler frequency offset, uplink carrier frequency, and downlink carrier frequency. For uplink frequency offset pre-compensation, the calculation method for the Doppler frequency offset at the first moment is analogous to that of downlink frequency offset post-compensation.

[0527] Other designs for direction 2-1:

[0528] Optionally, the terminal determines whether to perform uplink time offset pre-compensation for the feeder link using at least one of the following methods:

[0529] Option 1: If the network side does not configure the first parameter corresponding to the feeder link, then the terminal will not perform uplink time offset pre-compensation for the feeder link. For example, for Scheme 1, if at least one of the following is not broadcast: ground base station location, ephemeris information, epoch time; for Scheme 2, if any one of the following is not configured: Doppler frequency offset, Doppler frequency drift, carrier frequency, common TA; for Scheme 3, if any one of the following is not configured: common TA, common TA drift, common TA drift change rate, epoch time; for Scheme 4, if any one of the following is not configured: epoch time, TA drift, Doppler frequency drift, carrier frequency, common TA; for Scheme 5, if any one of the following is not configured: Doppler frequency offset, TA drift change rate, carrier frequency, common TA, epoch time, the terminal will not perform uplink time offset pre-compensation.

[0530] Option 2: The terminal determines whether to perform uplink TA pre-compensation for the feeder link based on the first parameter based on at least one of the following second parameters: the location of the uplink synchronization reference point and the operating mode (i.e., transparent payload or regenerative payload). The second parameter is configured by the base station or determined based on the base station configuration parameters. Specifically: if the terminal determines that the operating mode is transparent payload and determines that the uplink synchronization reference point is located on the terrestrial network equipment side, then the terminal performs uplink TA pre-compensation for the feeder link based on at least one of Schemes 1 to 5; if the terminal determines that the operating mode is transparent payload and determines that the uplink synchronization reference point is located on the satellite, the terminal does not perform uplink TA pre-compensation for the feeder link even if the network configures the first parameter; if the terminal determines that the operating mode is regenerative payload, similarly, the terminal does not perform uplink TA pre-compensation for the feeder link even if the network configures the first parameter.

[0531] Direction 2-2: Compensate for time offset and frequency offset on the feeder link based on independent first parameters.

[0532] Option 6: The terminal performs time offset and frequency offset compensation on the feeder link based on at least one of the following first parameters:

[0533] For time offset compensation, the first parameter corresponding to the feeder link corresponds to at least one of the following sets:

[0534] The second set includes: the reference location of the network equipment in the ground, ephemeris information, and epoch time.

[0535] First set: Common TA / First distance / First elevation angle + Satellite ephemeris information, Common TA drift, Common TA drift rate, epoch time.

[0536] For frequency offset compensation, the first parameter corresponding to the feeder link includes at least one of the following: Doppler offset, Doppler rate / drift, and epoch time.

[0537] Option 7: The protocol is pre-configured so that the terminal can determine the time and frequency offset of the feeder link using any set of first parameters corresponding to at least one of Options 1 through 6. If all parameters are not configured, the terminal does not need to perform time and frequency offset compensation for the feeder link. Furthermore, the terminal determines whether to perform at least one of uplink frequency offset pre-compensation, uplink time offset pre-compensation, or downlink frequency offset post-compensation, similar to the design in any of Options 1 and 2.

[0538] Key Point Three: Partial Compensation Mechanism

[0539] Based on point two above, optionally, the terminal can compensate for partial time offset and / or frequency offset of the feeder link. For example, at least one of the following methods can be used:

[0540] Option 1: For Doppler frequency offset, in the first instant, the terminal only compensates for the Doppler offset (determined based on at least one method in point two), and the base station only configures the first parameter corresponding to the Doppler offset determination. The final frequency offset change caused by Doppler drift on the feeder link is compensated by the base station.

[0541] Option 2: For Doppler time offset, at the first moment, the terminal only compensates for the Common Time Aspect (TA). The changes in propagation delay caused by TA drift and the rate of change of TA drift are compensated by the base station. The base station only configures the first parameter corresponding to the determination of the Common TA.

[0542] Option 3: For Doppler time offset, at the first moment, the terminal only performs feeder link TA compensation related to the propagation delay changes caused by the common TA and TA drift. The propagation delay changes caused by the TA drift rate are handled by the base station. The base station only configures the first parameter corresponding to the determination of the common TA and TA drift.

[0543] Option 4: The terminal only performs TA pre-compensation based on TA drift and TA drift change rate; the common TA is handled by the base station. The base station only configures the first parameter corresponding to TA drift and TA drift change rate, without configuring the parameters corresponding to the common TA determination.

[0544] Key Point 4: Parameter Derivation of Uplink and Downlink Joint Compensation:

[0545] Optionally, in response to the terminal simultaneously performing uplink and downlink Doppler frequency offset compensation, the terminal performs uplink and downlink Doppler frequency offset and time offset compensation based on at least one of the following methods:

[0546] Method 1: The terminal performs uplink and downlink Doppler frequency offset compensation based on uplink Doppler frequency offset and uplink Doppler frequency drift, and performs uplink synchronization pre-compensation for the feeder link. Specifically, the terminal needs to determine at least one of the following first parameters:

[0547] Downlink carrier frequency, uplink carrier frequency, uplink Doppler frequency offset, uplink Doppler frequency drift.

[0548] For TA pre-compensation: The terminal calculates TA drift based on the uplink carrier frequency and uplink Doppler frequency offset, calculates the TA drift change rate based on the uplink carrier frequency and uplink Doppler frequency drift, and calculates the pre-compensation TA value based on the TA drift and TA drift change rate.

[0549] For frequency offset compensation: the downlink Doppler frequency offset is calculated based on the downlink carrier frequency, uplink carrier frequency, and uplink Doppler frequency offset. One possible calculation formula is as follows:

[0550]

[0551] In the formula, Doppler_offset1 represents the upward Doppler frequency offset, f c1 f represents the uplink carrier frequency. c2 This indicates the downlink carrier frequency, and Doppler_offset2 indicates the downlink Doppler frequency offset;

[0552] In some examples, downlink Doppler drift is calculated based on the downlink carrier frequency, uplink carrier frequency, and uplink Doppler drift. One possible calculation formula is as follows:

[0553]

[0554] In the formula, Doppler_drift1 represents the uplink Doppler frequency drift, f c1 f represents the uplink carrier frequency. c2 Doppler_drift2 represents the downlink carrier frequency;

[0555] Based on the downlink Doppler frequency drift, downlink Doppler frequency offset, and epoch time, the terminal calculates the Doppler frequency offset of the downlink transmission of the feeder link at the first moment and performs downlink frequency offset compensation.

[0556] Based on the uplink Doppler frequency offset, uplink Doppler frequency drift, and epoch time, the terminal calculates the Doppler frequency offset of the feeder link uplink transmission at the first moment and performs uplink frequency offset pre-compensation.

[0557] Method 2: The terminal performs uplink and downlink Doppler frequency offset compensation based on downlink Doppler frequency offset and downlink Doppler frequency drift. Specifically, the terminal needs to determine: uplink carrier frequency, downlink carrier frequency, downlink Doppler frequency offset, and downlink Doppler frequency drift. The calculation logic for TA pre-compensation and frequency offset compensation is analogous to Method 1 (deriving uplink parameters based on downlink parameters).

[0558] Method 3: The protocol is pre-supported by both Method 1 and Method 2, and performs TA pre-compensation and frequency offset compensation based on at least one set of first parameters configured by the base station.

[0559] The terminal determines whether to perform time offset pre-compensation based on at least one of the following methods: Based on method one, if the base station has not configured the uplink carrier frequency, then time offset pre-compensation will not be performed; based on method two, if the base station has not configured the downlink carrier frequency, then uplink time offset pre-compensation for the feeder link will not be performed; or the terminal determines whether to perform uplink time offset pre-compensation for the feeder link through protocol preset.

[0560] The terminal determines whether to perform uplink and downlink Doppler frequency offset compensation based on at least one of the following methods:

[0561] Option 1: According to the protocol, the terminal performs Doppler frequency offset compensation for both the uplink and downlink.

[0562] Option 2: Based on Method 1, if the base station has not configured all parameters, the terminal will not perform uplink and downlink Doppler frequency offset compensation for the feeder link. If either the uplink carrier frequency or the downlink carrier frequency has not been configured, the terminal will not perform downlink Doppler frequency offset compensation.

[0563] Option 3: Based on Method 2, if the base station has not configured all parameters, the terminal will not perform uplink and downlink Doppler frequency offset compensation for the feeder link. If either the uplink carrier frequency or the downlink carrier frequency is not configured, the terminal will not perform Doppler frequency offset pre-compensation for the feeder link during uplink transmission.

[0564] Point 5: Applicable GNSS operating modes:

[0565] This mechanism applies to at least one of the following Global Navigation Satellite System (GNSS) operation modes:

[0566] (1) GNSS-based operation;

[0567] (2) GNSS resilient / degraded operation mode;

[0568] (3) GNSS-less operation.

[0569] The different methods in the above embodiments can be executed individually or in combination. For details, please refer to the optional implementation methods involved in steps S2101-S2103, S2201-S2203, S2301-S2303, S3101-S3103, and step S3201, which will not be repeated here. For example, the examples in the above methods can be executed individually or in combination, etc., and this disclosure does not limit the scope of the embodiments.

[0570] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0571] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0572] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0573] Figure 4A This is a schematic diagram of the structure of a terminal according to an embodiment of this disclosure. The terminal is used to execute any of the above methods. In some embodiments, such as Figure 4A As shown, the terminal may include at least one of a transceiver module 5101, a processing module 5102, etc. In some embodiments, the transceiver module 5101 is configured to receive configuration information sent by a network device; the processing module 5102 is configured to determine frequency offset compensation parameters for the feeder link based on the configuration information; and perform frequency offset compensation for the feeder link according to the frequency offset compensation parameters. Optionally, the transceiver module 5101 is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, which will not be elaborated here. Optionally, the processing module 5102 is used to perform at least one of the other steps performed by the terminal in any of the above methods, which will not be elaborated here.

[0574] Figure 4B This is a schematic diagram of the structure of a network device according to an embodiment of this disclosure. The network device is used to perform any of the above methods. In some embodiments, such as Figure 4BAs shown, the network device may include at least one of a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module 5201 is configured to send configuration information to the terminal; wherein the configuration information is used to determine the frequency offset compensation parameters of the feeder link; the frequency offset compensation parameters are used for frequency offset compensation of the feeder link. Optionally, the transceiver module 5201 is used to perform the communication steps such as sending and / or receiving performed by the network device in any of the above methods, which will not be described in detail here. Optionally, the processing module 5202 is used to perform other steps performed by the network device in any of the above methods, which will not be described in detail here.

[0575] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0576] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0577] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0578] Figure 5A This is a schematic diagram of the structure of the communication device 6100 proposed in this embodiment. The communication device 6100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0579] like Figure 5A As shown, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0580] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceivers 6102 perform the communication steps such as sending and / or receiving in the above method, and the processor 6101 performs other processing steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, sending unit, transmitter, sending circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0581] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data and / or instructions. Optionally, one or more processors 6101 are used to invoke instructions stored in the memory 6103 to cause the communication device 6100 to perform any of the above methods. Optionally, all or part of the memory 6103 may also be located outside the communication device 6100. In optional embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6102 and can be used to receive data and / or instructions from the memory 6102 or other devices, and can be used to send data and / or instructions to the memory 6102 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6102 and send the data and / or instructions to the processor 6101.

[0582] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may vary. Figure 5A The limitations. The communication device may be a standalone device or part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally including storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0583] Figure 5B This is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to... Figure 5B The diagram shown is a schematic representation of the structure of chip 6200, but it is not limited to this.

[0584] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

[0585] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data and / or instructions. Optionally, all or part of the memories 6203 may be located outside of chip 6200. Optionally, the interface circuits 6202 are connected to the memories 6203, and the interface circuits 6202 can be used to receive data and / or instructions from the memories 6203 or other devices, and can be used to send data and / or instructions to the memories 6203 or other devices. For example, the interface circuits 6202 can read data and / or instructions stored in the memories 6203 and send the data and / or instructions to the processor 6201.

[0586] In some embodiments, the interface circuit 6202 performs communication steps such as sending and / or receiving in the above-described method. For example, the interface circuit 6202 performing communication steps such as sending and / or receiving in the above-described method refers to the interface circuit 6202 performing data and / or instruction interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs other processing steps.

[0587] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0588] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0589] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0590] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method of a non-terrestrial network, characterized by, The method, executed by a terminal, includes: Receive configuration information sent by network devices; Based on the configuration information, determine the frequency offset compensation parameters for the feeder link; Frequency offset compensation of the feeder link is performed according to the frequency offset compensation parameters.

2. The method of claim 1, wherein, The frequency offset compensation parameters include at least one of uplink frequency offset compensation parameters and downlink frequency offset compensation parameters; The step of performing frequency offset compensation for the feeder link according to the frequency offset compensation parameters includes at least one of the following: Based on the uplink frequency offset compensation parameters, perform uplink frequency offset pre-compensation for the feeder link; Based on the downlink frequency offset compensation parameters, perform downlink frequency offset compensation on the feeder link.

3. The method of claim 2, wherein, The determination of the frequency offset compensation parameters for the feeder link based on the configuration information includes any one of the following: The uplink frequency offset compensation parameters are determined based on the configuration information, and the downlink frequency offset compensation parameters of the feeder link are determined based on the uplink frequency offset compensation parameters and the ratio between the uplink carrier frequency and the downlink carrier frequency. The downlink frequency offset compensation parameters are determined based on the configuration information, and the uplink frequency offset compensation parameters of the feeder link are determined based on the downlink frequency offset compensation parameters and the ratio between the uplink carrier frequency and the downlink carrier frequency.

4. The method according to any one of claims 1 to 3, characterized in that, The feeder link is the transmission link between the ground base station and the satellite; The configuration information includes at least one of the following: The location information of the ground base station; The carrier frequency of the feeder link; Satellite ephemeris information; epochal time information; The first indication of the Doppler frequency offset of the feeder link; The second indication of Doppler frequency drift of the feeder link; The third indication of the common TA of the feeder link; The fourth indication of the common TA drift of the feeder link; The fifth indication of the common TA drift rate of the feeder link.

5. The method of claim 4, wherein, The step of determining the frequency offset compensation parameters of the feeder link based on the configuration information includes: Based on the configuration information, determine the Doppler frequency offset and / or Doppler frequency drift of the feeder link; The frequency offset compensation parameters are determined based on the Doppler frequency offset and / or the Doppler frequency drift.

6. The method of claim 5, wherein, Determining the Doppler frequency offset of the feeder link based on the configuration information includes any one of the following: Based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information, the Doppler frequency offset is determined; The Doppler frequency offset is determined based on the first indication; The Doppler frequency offset is determined based on the common TA drift of the feeder link and the carrier frequency of the feeder link.

7. The method of any one of claims 5-6, wherein, Determining the Doppler frequency drift of the feeder link based on the configuration information includes any one of the following: Based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information, the Doppler frequency drift is determined; The Doppler frequency drift is determined based on the second indication; The Doppler frequency drift is determined based on the common TA drift rate of the feeder link and the carrier frequency of the feeder link.

8. The method according to any one of claims 4 to 7, characterized in that, The method further includes: The timing advance (TA) pre-compensation value of the feeder link is determined based on the configuration information. Based on the TA pre-compensation value, time offset compensation is performed on the feeder link.

9. The method of claim 8, wherein, The step of determining the TA pre-compensation value of the feeder link based on the configuration information includes: Based on the location information of the ground base station, the satellite ephemeris information, and the epoch time information, the TA pre-compensation value of the feeder link is determined.

10. The method of claim 8, wherein, The step of determining the TA pre-compensation value of the feeder link based on the configuration information includes: Based on the configuration information, at least one of the following is determined for the feeder link: common TA, common TA drift, and common TA drift rate; The TA pre-compensation value of the feeder link is determined based on at least one of the common TA, the common TA drift, and the common TA drift change rate.

11. The method of claim 10, wherein, Determining the common TA of the feeder link based on the configuration information includes: The common TA is determined according to the third indication, which includes at least one of the following parameters for determining the common TA: Propagation delay between the ground base station and the satellite; The distance between the ground base station and the satellite; The elevation angle between the ground base station and the satellite.

12. The method of any one of claims 10-11, wherein, Determining the common TA drift of the feeder link based on the configuration information includes any one of the following: The common TA drift is determined according to the fourth indication; The common TA drift is determined based on the Doppler frequency offset of the feeder link and the carrier frequency of the feeder link.

13. The method according to any one of claims 10 to 12, characterized in that, The common current transfer rate (CT) drift rate of the feeder link is determined based on the configuration information, including any one of the following: The common TA drift rate is determined according to the fifth indication; The common TA drift rate is determined based on the Doppler frequency drift of the feeder link and the carrier frequency of the feeder link.

14. A communication method of a non-terrestrial network, characterized by, Performed by a network device, the method includes: Send configuration information to the terminal; The configuration information is used to determine the frequency offset compensation parameters of the feeder link; the frequency offset compensation parameters are used for frequency offset compensation of the feeder link.

15. The method of claim 14, wherein, The frequency offset compensation parameters include at least one of uplink frequency offset compensation parameters and downlink frequency offset compensation parameters; The frequency offset compensation of the feeder link includes at least one of the following: The uplink frequency offset pre-compensation of the feeder link; Downlink frequency offset compensation for the feeder link.

16. The method of any one of claims 14-15, wherein, The feeder link is the transmission link between the ground base station and the satellite; The configuration information includes at least one of the following: The location information of the ground base station; The carrier frequency of the feeder link; Satellite ephemeris information; epochal time information; The first indication of the Doppler frequency offset of the feeder link; The second indication of Doppler frequency drift of the feeder link; The third indication of the common TA of the feeder link; The fourth indication of the common TA drift of the feeder link; The fifth indication of the common TA drift rate of the feeder link.

17. The method of claim 16, wherein, The configuration information is used to determine the Doppler frequency offset and / or Doppler frequency drift of the feeder link, and the Doppler frequency offset and / or the Doppler frequency drift is used to determine the frequency offset compensation parameter.

18. The method of claim 17, wherein, The Doppler frequency offset is determined based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information; or... The Doppler frequency offset is determined based on the first indication; or... The Doppler frequency offset is determined based on the common TA drift of the feeder link and the carrier frequency of the feeder link.

19. The method of any one of claims 17-18, wherein, The Doppler frequency drift is determined based on the location information of the ground base station, the carrier frequency of the feeder link, the satellite ephemeris information, and the epoch time information; or... The Doppler frequency drift is determined based on the second indication; or... The Doppler frequency drift is determined based on the common TA drift rate of the feeder link and the carrier frequency of the feeder link.

20. The method of any one of claims 16-19, wherein, The configuration information is also used to determine the timing advance (TA) pre-compensation value of the feeder link; the TA pre-compensation value is used for time offset compensation of the feeder link.

21. The method of claim 20, wherein, The TA pre-compensation value of the feeder link is determined based on the location information of the ground base station, the satellite ephemeris information, and the epoch time information.

22. The method according to claim 20, characterized in that, The configuration information is used to determine at least one of the common TA, common TA drift, and common TA drift change rate of the feeder link; the common TA, common TA drift, and common TA drift change rate are used to determine the TA pre-compensation value of the feeder link.

23. The method according to claim 22, characterized in that, The common TA is determined according to the third indication, which includes at least one of the following parameters for determining the common TA: Propagation delay between the ground base station and the satellite; The distance between the ground base station and the satellite; The elevation angle between the ground base station and the satellite.

24. The method according to any one of claims 22 to 23, characterized in that, The common TA drift is determined according to the fourth indication; or... The common TA drift is determined based on the Doppler frequency offset of the feeder link and the carrier frequency of the feeder link.

25. The method according to any one of claims 22 to 24, characterized in that, The common TA drift change rate is determined according to the fifth indication; or... The common TA drift rate is determined based on the Doppler frequency drift of the feeder link and the carrier frequency of the feeder link.

26. A communication system, characterized in that, The device includes a terminal and a network device, the terminal being configured to implement the method of any one of claims 1 to 13, and the network device being configured to implement the method of any one of claims 14 to 25.

27. A communication device, characterized in that, The communication device is used to perform the method according to any one of claims 1 to 13 or 14 to 25.

28. A storage medium storing instructions, characterized in that, When the instructions are executed on a communication device, the communication device performs the method of any one of claims 1 to 13 or 14 to 25.

29. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by a communication device, it implements the method of any one of claims 1 to 13 or 14 to 25.