Communication method and communication device

Abstract

The invention provides a communication method and a communication device applied to the technical field of wireless communication. In the technical scheme provided by the invention, the terminal can obtain the first receiving opportunity and / or the second receiving opportunity, receive the GNSS signal based on the first receiving opportunity and receive the ephemeris data based on the second receiving opportunity, so that the uplink signal is pre-compensated when the uplink signal is sent. In the technical scheme provided by the invention, as the first receiving opportunity and / or the second receiving opportunity is related to the actual timing deviation tolerance and frequency deviation tolerance of the network equipment, the uplink timing deviation and the frequency deviation error which can be actually tolerated by the network equipment may be greater than the uplink timing deviation and the frequency deviation error indicated in the existing protocol; the power consumption of the terminal can be saved, and the network performance of the terminal is improved.

Description

Technical Field

[0001] This application relates to the field of wireless communication, and more particularly to a communication method and a communication device. Background Technology

[0002] In non-terrestrial network (NTN) satellite communication, terminals can pre-compensate for the timing and frequency offset of the transmitted uplink signals based on the location information and ephemeris information of the global navigation satellite system (GNSS). This ensures that the uplink signals transmitted by different terminals arrive at the network equipment with the same timing and frequency offset, thereby guaranteeing the performance of the network equipment.

[0003] However, this method has the following problem: the terminal consumes a lot of power. Summary of the Invention

[0004] This application provides a communication method and a communication device, applicable to the field of wireless communication. In the technical solution provided by this application, the terminal consumes relatively low power when performing uplink signal pre-compensation.

[0005] In a first aspect, this application provides a communication method applied to a terminal, the method comprising: acquiring a first reception timing and / or a second reception timing, wherein the first reception timing and the second reception timing are determined based on at least one of the following: the timing deviation tolerance capability of a network device, the frequency deviation tolerance capability of the network device, the GNSS measurement error that the network device can tolerate, the ephemeris calculation error that the network device can tolerate, or the GNSS error, wherein the first reception timing is a reception timing for a GNSS signal, and the second reception timing is a reception timing for ephemeris data; receiving the GNSS signal according to the first reception timing, and / or receiving the ephemeris data according to the second reception timing.

[0006] This method can be executed by the terminal, or by a chip system, hardware circuit and / or software module applied in the terminal, or by other devices capable of implementing the functions of the terminal, without any limitation.

[0007] Global Navigation Satellite System (GNSS) signals can be understood as signals transmitted by GNSS satellites. GNSS satellites provide global positioning and navigation services. GNSS signals can contain information such as the precise time of the GNSS satellite, its identification information, and its ephemeris data. Terminals can determine their GNSS location information using these signals. GNSS location information can include the terminal's location. Ephemeris data can be understood as the ephemeris data of communication satellites in a satellite communication system. Ephemeris data contains information such as the satellite's position, velocity, and acceleration.

[0008] The timing deviation tolerance of a network device refers to the tolerance it can meet regarding the timing deviation of uplink signals transmitted by terminals; in other words, it's an indicator of the acceptable timing offset error of the uplink signal. This indicator represents both the limit of the timing deviation the network device itself can tolerate and the requirement that the uplink signal transmitted by the terminal should meet. The timing offset error can be understood as the error between the timing offset determined by the terminal and the actual timing offset between the terminal and the network device. Similarly, the frequency offset tolerance of a network device refers to the tolerance it can meet regarding the frequency offset error of uplink signals transmitted by terminals; in other words, it's an indicator of the acceptable frequency offset error of the uplink signal. This indicator represents both the limit of the frequency offset error the network device itself can tolerate and the requirement that the uplink signal transmitted by the terminal should meet. The frequency offset error can be understood as the error between the frequency offset determined by the terminal and the actual frequency offset between the terminal and the network device.

[0009] GNSS measurement error refers to the error in the GNSS position information determined by the terminal through GNSS signals, such as the deviation between the GNSS position information determined by the terminal and the actual GNSS position information. Ephemeris calculation error refers to the error in the communication satellite position information (such as the position and velocity of the communication satellite) determined by the terminal through ephemeris data, such as the deviation between the communication satellite position information determined by the terminal and the actual position information of the communication satellite. GNSS error refers to the error introduced by the terminal's own performance (such as the performance of hardware circuits, software modules, antennas, etc.). For example, GNSS error can include at least one of the following: the error in the GNSS position information determined by the terminal, the accuracy of the GNSS position information determined by the terminal, the error in the communication satellite position information determined by the terminal, the accuracy of the communication satellite position information determined by the terminal, or the terminal's startup accuracy. The terminal's startup accuracy can be understood as the time and accuracy required for the terminal to go from a powered-off state to full startup and reach normal operating status.

[0010] As an example, the terminal can determine the first reception timing and / or the second reception timing by obtaining at least one of the following information: the timing deviation tolerance capability of the network device, the frequency deviation tolerance capability of the network device, the GNSS measurement error that the network device can tolerate, the ephemeris calculation error that the network device can tolerate, or the GNSS error. The timing deviation tolerance capability, frequency deviation tolerance capability, GNSS measurement error that the network device can tolerate, and ephemeris calculation error that the network device can tolerate can be predefined by the protocol or pre-configured in the terminal; no specific limitations are imposed here.

[0011] In this technical solution, the terminal can receive GNSS signals based on a first reception timing and receive ephemeris data based on a second reception timing, thereby achieving uplink signal pre-compensation. Since the first and second reception timings are related to the actual timing and frequency offset tolerance capabilities of the network equipment, and the actual uplink timing and frequency offset errors that the network equipment can tolerate may be greater than those indicated in the protocol, the terminal can avoid continuous operation, thus reducing its power consumption.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, obtaining the first receiving timing and / or the second receiving timing includes: receiving first information, wherein the first information indicates the first receiving timing and / or the second receiving timing.

[0013] In this implementation, the network device can send first information to the terminal, indicating a first reception timing and / or a second reception timing. For example, after the terminal randomly accesses the network, the network device can send the first information to the terminal. For example, the network device can send the first information during radio resource control (RRC) configuration, RRC reconfiguration, or capability information exchange. Alternatively, the network device can send the first information via a system message. Correspondingly, the terminal can receive the first information.

[0014] In this implementation, the network device can directly indicate the first reception timing and / or the second reception timing to the terminal. For example, the first information may include the first reception timing and / or the second reception timing.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the first information indicates the timing deviation tolerance capability and / or the frequency deviation tolerance capability of the network device.

[0016] In this implementation, the network device can indicate the first reception timing and / or the second reception timing by indicating the network device's timing deviation tolerance capability and / or frequency deviation tolerance capability.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the timing deviation tolerance capability and / or the frequency deviation tolerance capability are related to at least one of the following: the signal type of the uplink signal transmitted by the terminal, the modulation order of the uplink signal, the format of the pilot sequence of the uplink signal, the Radio Resource Control Protocol (RRC) status of the terminal, the network procedure executed by the terminal, the moving speed of the terminal, the communication system in which the terminal is located, or the manufacturer of the network equipment.

[0018] In this implementation, the signal types of the uplink signals transmitted by the terminal include, but are not limited to: physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), physical random access channel (PRACH), and sounding reference signal (SRS). The demodulation modes of the uplink signals include, but are not limited to: quadrature phase shift keying (QPSK) and quadrature amplitude modulation (QAM). QAM can include 16QAM and 64QAM. Specifically, QPSK has a modulation order of 2, 16QAM has a modulation order of 4, and 64QAM has a modulation order of 6. The pilot sequence of the uplink signal can be a demodulation reference signal (DMRS) sequence. The format of the pilot sequence is, for example, the number of columns in the pilot sequence. The RRC state of the terminal can include: idle, connected, and inactive. The network procedures executed by the terminal may include random access procedures, handover procedures, paging procedures, etc. In some embodiments, the timing deviation tolerance and / or frequency deviation tolerance of the network device may differ when the terminal executes different steps of the same network procedure. The terminal's movement speed may include one or more speed levels, such as low speed, medium speed, and fast speed. The speed levels of the terminal can be set according to actual needs and are not limited here. The communication system in which the terminal operates can be a satellite communication system or a new radio (NR) communication system, and is not limited here. The network device manufacturer can be any network device manufacturer.

[0019] In this implementation, the timing deviation tolerance and frequency deviation tolerance of the network device can be related to information such as the signal type and modulation order of the uplink signal sent by the terminal, thereby improving the flexibility of the terminal in performing uplink signal pre-compensation.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, the first information indicates a numerical value or range of the timing deviation tolerance capability; and / or, the first information indicates a numerical value or range of the frequency deviation tolerance capability.

[0021] In this implementation, the network device can directly indicate the values ​​of its timing error tolerance and / or frequency error tolerance. For example, the first information may include specific values ​​for frequency error tolerance and / or timing error tolerance. Frequency error tolerance indicates the network device's frequency error tolerance. Timing error tolerance indicates the network device's timing error tolerance.

[0022] In this implementation, the network device can indicate the numerical range of timing deviation tolerance and / or frequency deviation tolerance. For example, the first information can include a first reported value and / or a second reported value. The first reported value can have a first mapping relationship with the frequency deviation tolerance. The second reported value can have a second mapping relationship with the timing deviation tolerance. The first and second mapping relationships can be predefined by the protocol or configured by the network device; this application does not limit this.

[0023] In conjunction with the first aspect, in certain implementations of the first aspect, the first information indicates the GNSS measurement errors that the network device can tolerate and / or the ephemeris calculation errors that the network device can tolerate.

[0024] In this implementation, the network device can indicate the first reception timing and / or the second reception timing by specifying the GNSS measurement errors and / or ephemeris calculation errors that the network device can tolerate. For example, the network device can determine the GNSS measurement errors and / or ephemeris calculation errors that it can tolerate based on its own timing offset tolerance and frequency offset tolerance, and then send this information to the terminal via the first message. Therefore, the terminal can directly determine the first reception timing and / or the second reception timing based on the GNSS measurement errors and / or ephemeris calculation errors that the network device can tolerate. In this implementation, the terminal does not need to determine the GNSS measurement errors and / or ephemeris calculation errors that the network device can tolerate based on the network device's timing offset tolerance and / or frequency offset tolerance, thus saving the terminal's power consumption.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, the first receiving timing and / or the second receiving timing are predefined.

[0026] In this implementation, the first reception timing and / or the second reception timing can be predefined by the protocol or pre-configured in the terminal. This application does not impose any restrictions on this.

[0027] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: sending second information, the second information being used to request the first information.

[0028] In this implementation, the terminal can send a second message to the network device to request the network device to indicate a first reception timing and / or a second reception timing, thereby saving the terminal's power consumption. For example, the terminal can send the second message before performing uplink signal pre-compensation.

[0029] In conjunction with the first aspect, in some implementations of the first aspect, obtaining the first reception timing and / or the second reception timing includes: obtaining third information, the third information indicating the timing deviation tolerance capability and the frequency deviation tolerance capability of the network device, the third information including at least one of the following: the signal type of the uplink signal transmitted by the terminal, the modulation order of the uplink signal, the format of the pilot sequence of the uplink signal, the RRC status of the terminal, the network process executed by the terminal, the moving speed of the terminal, the communication system in which the terminal is located, or, the manufacturer of the network device; and determining the first reception timing and / or the second reception timing based on the third information.

[0030] In this implementation, when the timing deviation tolerance and frequency deviation tolerance of the network device are related to the third information, the terminal can determine the timing deviation tolerance and frequency deviation tolerance of the network device by obtaining the third information, thereby determining the first reception timing and the second reception timing, and thus realizing the pre-compensation of the uplink signal.

[0031] In conjunction with the first aspect, in some implementations of the first aspect, the first reception timing includes at least one of the following: the first reception period of the GNSS signal, or the reception duration of the GNSS signal within a first reception period; and / or, the second reception timing includes at least one of the following: the second reception period of the ephemeris data, or the reception duration of the ephemeris data within a second reception period.

[0032] In this implementation, if the first reception period is N seconds (s), the terminal can activate once every N seconds to receive GNSS signals. If the reception duration of the GNSS signal in one first reception period is M seconds, the terminal can receive GNSS signals for M seconds after activation, and can remain in sleep mode for the rest of the time to save power consumption. N and M are positive integers, where M is less than or equal to N.

[0033] It should be noted that the reception duration of GNSS signals within each first reception cycle can be the same or different. The start time of reception for GNSS signals within each first reception cycle can also be the same or different.

[0034] The second receiving timing is similar to the first receiving timing, and the details can be found in the relevant description of the first receiving timing, which will not be repeated here.

[0035] Secondly, this application provides a communication method applied to a network device, the method comprising: determining first information, the first information indicating a first reception timing and / or a second reception timing, the first reception timing being a GNSS signal reception timing and the second reception timing being an ephemeris data reception timing; and transmitting the first information.

[0036] This method can be executed by a network device, or by a chip system, hardware circuit and / or software module applied in the network device, or by other means capable of implementing the functions of the network device, without limitation.

[0037] GNSS signals can be understood as signals transmitted by GNSS satellites. GNSS satellites are used to provide global positioning and navigation services. GNSS signals can contain information such as the precise time of the GNSS satellite, its identification information, and its ephemeris data. Terminals can determine their GNSS location information through GNSS signals. GNSS location information can include the terminal's location. Ephemeris data can be understood as the ephemeris data of communication satellites in a satellite communication system. Ephemeris data contains information such as the satellite's position, velocity, and acceleration.

[0038] In this technical solution, the network device can send first information to the terminal to indicate a first reception timing and / or a second reception timing, so that the terminal can receive GNSS signals based on the first reception timing and / or receive ephemeris data based on the second reception timing, thereby achieving uplink signal pre-compensation. This technical solution helps reduce the power consumption of the terminal when performing uplink signal pre-compensation.

[0039] In conjunction with the second aspect, in some implementations of the second aspect, the first information indicates the timing deviation tolerance capability and / or the frequency deviation tolerance capability of the network device, and the first reception timing and / or the second reception timing are determined based on at least one of the following: the timing deviation tolerance capability of the network device, or the frequency deviation tolerance capability of the network device.

[0040] In this implementation, the first reception timing and / or the second reception timing can be indicated by specifying the actual timing deviation tolerance and / or frequency deviation tolerance of the network device. The timing deviation tolerance of the network device refers to the index of timing deviation of the uplink signal transmitted by the terminal that the network device can tolerate; that is, the index of the timing offset error of the uplink signal that the network device can tolerate. This index is both the limit of timing deviation that the network device itself can tolerate and the index that the uplink signal transmitted by the terminal should meet. The timing offset error can be understood as the error between the timing offset determined by the terminal and the actual timing offset between the terminal and the network device. The frequency deviation tolerance of the network device refers to the index of frequency offset error of the uplink signal transmitted by the terminal that the network device can tolerate; that is, the index of the frequency offset error of the uplink signal that the network device can tolerate. This index is both the limit of frequency offset error that the network device itself can tolerate and the index that the uplink signal transmitted by the terminal should meet. The frequency offset error can be understood as the error between the frequency offset determined by the terminal and the actual frequency offset between the terminal and the network device.

[0041] In this implementation, since the uplink timing deviation and frequency offset error that the network device can actually tolerate may be greater than the uplink timing deviation and frequency offset error indicated in the protocol, the terminal does not need to work continuously when performing uplink signal pre-compensation based on the actual timing deviation tolerance and frequency offset tolerance of the network device, thereby saving the terminal's power consumption.

[0042] In conjunction with the second aspect, in some implementations of the second aspect, the timing deviation tolerance capability and the frequency deviation tolerance capability are related to at least one of the following: the signal type of the uplink signal transmitted by the terminal, the modulation order of the uplink signal, the format of the pilot sequence of the uplink signal, the Radio Resource Control Protocol (RRC) status of the terminal, the network procedure executed by the terminal, the moving speed of the terminal, the communication system in which the terminal is located, or the manufacturer of the network equipment.

[0043] In this implementation, the signal types of the uplink signals transmitted by the terminal include, but are not limited to: PUCCH, PUSCH, PRACH, and SRS. The demodulation modes of the uplink signals include, but are not limited to: QPSK and QAM. QAM can include 16QAM and 64QAM. Specifically, QPSK has a modulation order of 2, 16QAM has a modulation order of 4, and 64QAM has a modulation order of 6. The pilot sequence of the uplink signal can be a DMRS sequence. The format of the pilot sequence is, for example, the number of columns in the pilot sequence. The RRC state of the terminal can include: idle, connected, and inactive. The network procedures executed by the terminal can include random access procedures, handover procedures, paging procedures, etc. In some embodiments, when the terminal executes different steps of the same network procedure, the timing deviation tolerance and / or frequency deviation tolerance of the network device can also be different. The terminal's movement speed can include one or more speed levels. For example, low speed, medium speed, fast speed, etc. The division of the terminal's movement speed levels can be set according to actual needs and is not limited here. The communication system used by the terminal can be a satellite communication system or an NR communication system; there are no restrictions. The network equipment manufacturer can be any network equipment manufacturer.

[0044] In this implementation, the timing deviation tolerance and frequency deviation tolerance of the network device can be related to information such as the signal type and modulation order of the uplink signal sent by the terminal, thereby improving the flexibility of the terminal in performing timing and frequency deviation pre-compensation of the uplink signal.

[0045] In conjunction with the second aspect, in some implementations of the second aspect, the first information indicates a numerical value or range of the timing deviation tolerance capability; and / or, the first information indicates a numerical value or range of the frequency deviation tolerance capability.

[0046] In this implementation, the network device can directly indicate the values ​​of its timing error tolerance and / or frequency error tolerance. For example, the first information may include specific values ​​for frequency error tolerance and / or timing error tolerance. Frequency error tolerance indicates the network device's frequency error tolerance. Timing error tolerance indicates the network device's timing error tolerance.

[0047] In this implementation, the network device can indicate the numerical range of timing deviation tolerance and / or frequency deviation tolerance. For example, the first information can include a first report value and / or a second report value. The first report value can have a first mapping relationship with the frequency deviation tolerance. The second report value can have a second mapping relationship with the timing deviation tolerance. The first and second mapping relationships can be predefined by the protocol or configured by the network device; this application does not limit this.

[0048] In conjunction with the second aspect, in some implementations of the second aspect, the first information indicates the GNSS measurement error that the network device can tolerate and / or the ephemeris calculation error that the network device can tolerate, and the first reception timing and / or the second reception timing are determined based on at least one of the following: the GNSS measurement error that the network device can tolerate, or the ephemeris calculation error that the network device can tolerate.

[0049] In this implementation, the network device can indicate the first reception timing and / or the second reception timing by indicating the GNSS measurement error and / or ephemeris calculation error that the network device can tolerate. For example, the network device can determine the GNSS measurement error and / or ephemeris calculation error that the network device can tolerate based on its own timing offset tolerance and frequency offset tolerance, and then send the first information to the terminal.

[0050] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: receiving second information, the second information being used to request the first information.

[0051] In this implementation, the network device can send the first information to the terminal after receiving the second information, thereby improving the utilization rate of network resources.

[0052] In conjunction with the second aspect, in some implementations of the second aspect, the first reception timing includes at least one of the following: the first reception period of the GNSS signal, or the reception duration of the GNSS signal within a first reception period; and / or, the second reception timing includes at least one of the following: the second reception period of the ephemeris data, or the reception duration of the ephemeris data within a second reception period.

[0053] In this implementation, if the first reception period is N seconds (s), the terminal can activate once every N seconds to receive GNSS signals. If the reception duration of the GNSS signal in one first reception period is M seconds, the terminal can receive GNSS signals for M seconds after activation, and can remain in sleep mode for the rest of the time to save power consumption. N and M are positive integers, where M is less than or equal to N.

[0054] It should be noted that the reception duration of GNSS signals within each first reception cycle can be the same or different. The start time of reception for GNSS signals within each first reception cycle can also be the same or different.

[0055] The second receiving timing is similar to the first receiving timing, and can be referred to the relevant description of the first receiving timing, which will not be repeated here.

[0056] Thirdly, this application provides a communication device comprising modules for implementing the methods of the first aspect or any of the implementations thereof, each module being implemented in hardware and / or software.

[0057] For example, the device may include a processing module and a receiving module. The processing module is configured to acquire a first receiving timing and / or a second receiving timing, the first receiving timing and the second receiving timing being determined based on at least one of the following: the timing deviation tolerance capability of the network device, the frequency deviation tolerance capability of the network device, the GNSS measurement error that the network device can tolerate, the ephemeris calculation error that the network device can tolerate, or GNSS error, the first receiving timing being a GNSS signal receiving timing, and the second receiving timing being an ephemeris data receiving timing; the receiving module is configured to receive the GNSS signal according to the first receiving timing; the receiving module is further configured to receive the ephemeris data according to the second receiving timing.

[0058] In conjunction with the third aspect, in some implementations of the third aspect, the receiving module is further configured to receive first information, the first information indicating the first receiving timing and / or the second receiving timing.

[0059] In conjunction with the third aspect, in some implementations of the third aspect, the first information indicates the timing deviation tolerance capability and / or the frequency deviation tolerance capability of the network device.

[0060] In conjunction with the third aspect, in some implementations of the third aspect, the timing deviation tolerance capability and the frequency deviation tolerance capability are related to at least one of the following: the signal type of the uplink signal transmitted by the terminal, the modulation order of the uplink signal, the format of the pilot sequence of the uplink signal, the Radio Resource Control Protocol (RRC) status of the terminal, the network procedure executed by the terminal, the moving speed of the terminal, the communication system in which the terminal is located, or the manufacturer of the network equipment.

[0061] In conjunction with the third aspect, in some implementations of the third aspect, the first information indicates a numerical value or range of the timing deviation tolerance capability; and / or, the first information indicates a numerical value or range of the frequency deviation tolerance capability.

[0062] In conjunction with the third aspect, in some implementations of the third aspect, the first information indicates the GNSS measurement errors that the network device can tolerate and / or the ephemeris calculation errors that the network device can tolerate.

[0063] In conjunction with the third aspect, in some implementations of the third aspect, the first receiving timing and / or the second receiving timing are predefined.

[0064] In conjunction with the third aspect, in some implementations of the third aspect, the apparatus may include a sending module. The sending module is configured to send second information, the second information being used to request the first information.

[0065] In conjunction with the third aspect, in some implementations of the third aspect, the processing module is specifically used to: acquire third information, the third information indicating the timing deviation tolerance capability and frequency deviation tolerance capability of the network device, the third information including at least one of the following: the signal type of the uplink signal transmitted by the terminal, the modulation order of the uplink signal, the format of the pilot sequence of the uplink signal, the Radio Resource Control Protocol (RRC) status of the terminal, the network procedure executed by the terminal, the moving speed of the terminal, the communication system in which the terminal is located, or, the manufacturer of the network device; and determine the first reception timing and / or the second reception timing based on the third information.

[0066] In conjunction with the third aspect, in some implementations of the third aspect, the first reception timing includes at least one of the following: the first reception period of the GNSS signal, or the reception duration of the GNSS signal within a first reception period; and / or, the second reception timing includes at least one of the following: the second reception period of the ephemeris data, or the reception duration of the ephemeris data within a second reception period.

[0067] Fourthly, this application provides a communication device comprising modules for implementing the methods of the second aspect or any of the implementations thereof, each module being implemented in hardware and / or software.

[0068] For example, the device may include a processing module and a transmitting module. The processing module is configured to determine first information, the first information indicating a first reception timing and / or a second reception timing, the first reception timing being a GNSS signal reception timing and the second reception timing being an ephemeris data reception timing; the transmitting module is configured to transmit the first information.

[0069] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first information indicates the timing deviation tolerance capability and / or the frequency deviation tolerance capability of the network device, and the first reception timing and / or the second reception timing are determined based on at least one of the following: the timing deviation tolerance capability of the network device, or the frequency deviation tolerance capability of the network device.

[0070] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the timing deviation tolerance capability and the frequency deviation tolerance capability are related to at least one of the following: the signal type of the uplink signal transmitted by the terminal, the modulation order of the uplink signal, the format of the pilot sequence of the uplink signal, the Radio Resource Control Protocol (RRC) status of the terminal, the network procedure executed by the terminal, the moving speed of the terminal, the communication system in which the terminal is located, or the manufacturer of the network equipment.

[0071] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first information indicates a numerical value or range of the timing deviation tolerance capability; and / or, the first information indicates a numerical value or range of the frequency deviation tolerance capability.

[0072] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first information indicates the GNSS measurement error that the network device can tolerate and / or the ephemeris calculation error that the network device can tolerate, and the first reception timing and / or the second reception timing are determined based on at least one of the following: the GNSS measurement error that the network device can tolerate, or the ephemeris calculation error that the network device can tolerate.

[0073] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the apparatus may further include: a receiving module. The receiving module is configured to receive second information, the second information being used to request the first information.

[0074] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first reception timing includes at least one of the following: the first reception period of the GNSS signal, or the reception duration of the GNSS signal within a first reception period; and / or, the second reception timing includes at least one of the following: the second reception period of the ephemeris data, or the reception duration of the ephemeris data within a second reception period.

[0075] Fifthly, this application provides a communication device including a processor that can be coupled to a memory for calling program code in the memory to perform the method described in the first aspect or any of its possible implementations. Optionally, the device further includes a memory. Optionally, the device further includes a communication interface to which the processor can be coupled.

[0076] As an example, the device can be a terminal, a chip system, hardware circuit and / or software module applied in a terminal, or other device that can realize terminal functions, without limitation.

[0077] Sixthly, this application provides a communication device including a processor that can be coupled to a memory for calling program code in the memory to perform the method described in the second aspect or any of its possible implementations. Optionally, the device further includes a memory. Optionally, the device further includes a communication interface to which the processor can be coupled.

[0078] As an example, the device can be a network device, a chip system, hardware circuit and / or software module applied in a network device, or other device that can realize the functions of a network device, without limitation.

[0079] In a seventh aspect, this application provides a communication system that includes the means of the third or fourth aspect, as well as the means of the fifth or sixth aspect.

[0080] In this technical solution, the timing deviation tolerance and frequency deviation tolerance of the network equipment can vary depending on the communication system. The communication system can be a satellite communication system or an NR communication system.

[0081] Eighthly, this application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the method as described in the first aspect, the second aspect, or any possible implementation thereof.

[0082] Ninthly, this application provides a computer-readable medium storing program code for execution by a device, the program code including methods for performing the methods described in the first aspect, the second aspect, or any possible implementation thereof.

[0083] The technical effects that can be achieved by any of the third to ninth aspects above, and any possible design of any of the aspects above, are described in the description of the technical effects that can be achieved by the first to second aspects above, and will not be repeated here. Attached Figure Description

[0084] Figure 1a A schematic diagram of a satellite communication system in a transparent transmission scenario provided in one embodiment of this application;

[0085] Figure 1b A schematic diagram of a satellite communication system in a regeneration scenario provided in one embodiment of this application;

[0086] Figure 1c A schematic diagram of a satellite communication system in a regeneration scenario is provided for another embodiment of this application;

[0087] Figure 2 A schematic flowchart illustrating a communication method provided in one embodiment of this application;

[0088] Figure 3 A schematic diagram illustrating a first receiving timing according to an embodiment of this application;

[0089] Figure 4 A schematic flowchart illustrating a communication method provided in yet another embodiment of this application;

[0090] Figure 5 This is a schematic diagram of the structure of a communication device provided in one embodiment of this application;

[0091] Figure 6 A schematic diagram of the structure of a communication device provided in yet another embodiment of this application;

[0092] Figure 7 This is a schematic diagram of the structure of a communication device provided in another embodiment of this application.

[0093] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0094] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0095] Non-terrestrial networks (NTNs) refer to networks that utilize satellite equipment as communication infrastructure to achieve seamless global coverage and high-speed communication. NTN technology is a crucial component of 5G (5th generation mobile communication technology), providing wider coverage and higher transmission rates for wireless communication worldwide. NTN technology can establish global communication networks in a relatively short time, enabling people to communicate at high speeds anytime, anywhere. It also provides a more reliable communication infrastructure for applications such as mobile internet and the Internet of Things (IoT). Application scenarios for NTN technology include aviation, maritime, polar regions, deserts, and other areas difficult for humans to access, as well as ensuring communication during emergencies such as natural disasters and wars. The development of NTN technology will provide more stable and reliable support for global digital transformation.

[0096] In NTN satellite communication, terminals need to pre-compensate for the timing and frequency offset of their transmitted uplink signals to ensure that the timing and frequency offsets of uplink signals sent by different terminals to network devices are the same, thus guaranteeing the performance of the network devices. For example, terminals can determine the timing and frequency offsets of uplink signals based on Global Navigation Satellite System (GNSS) position information and ephemeris data, and pre-compensate for these offsets when transmitting uplink signals to ensure that the signals are correctly transmitted to the network devices. It should be understood that timing pre-compensation can be achieved by adjusting the transmission time of the uplink signal, and frequency offset pre-compensation can be achieved by adjusting the frequency or frequency point of the uplink signal. The frequency offset can be simply referred to as the frequency deviation. GNSS position information can include the terminal's location, such as its longitude, latitude, and altitude. In some embodiments, GNSS position information can also include the terminal's velocity. Ephemeris data can be understood as the ephemeris data of the communication satellite. The communication satellite is the satellite that communicates with the terminal in the satellite communication system. Ephemeris data contains information such as the satellite's position, velocity, and acceleration.

[0097] When the terminal performs uplink signal pre-compensation, the timing offset error and frequency offset error of the uplink signal determined by the terminal should meet the accuracy requirements of NTN uplink timing frequency offset. The accuracy requirements of NTN uplink timing frequency offset indicate the uplink timing deviation and frequency offset error that network equipment can tolerate. The accuracy requirements of NTN uplink timing frequency offset can be specified through protocols. In existing protocols, the uplink frequency offset error that network equipment can tolerate is 0.1 parts per million (ppm) per 370 Hz (standard frequency), and the tolerable uplink timing deviation is 0.72 microseconds (µs).

[0098] However, the accuracy requirements for uplink timing frequency offset specified in existing protocols for NTN are too high. To meet these accuracy requirements, the terminal needs to operate continuously, resulting in high power consumption. Continuous terminal operation includes continuously acquiring GNSS location information and continuously updating ephemeris data. It should be noted that satellite communication systems broadcast ephemeris data from communication satellites, and the terminal receives this data periodically to update it.

[0099] In real-world satellite communication scenarios, the uplink timing and frequency offset errors that network devices can actually tolerate may be greater than those indicated in the protocol. Therefore, if the terminal performs uplink signal pre-compensation based on the uplink timing and frequency offset errors that the network device can actually tolerate, the terminal does not need to operate continuously, thereby reducing the terminal's power consumption.

[0100] In view of this, this application provides a communication method and a communication device applied in the field of wireless communication. In the technical solution provided by this application, the terminal can determine its operating state based on the uplink timing deviation and frequency offset error that the network device can actually tolerate, and perform uplink signal pre-compensation based on the determined operating state. The technical solution provided by this application can reduce the power consumption of the terminal.

[0101] The following is combined with Figure 1a , Figure 1b , Figure 1c Examples of application scenarios applicable to the embodiments of this application are provided.

[0102] Figure 1a A schematic diagram of a satellite communication system in a transparent transmission scenario is shown. Figure 1a As shown, terminals can access the network via an air interface (which can be of various types, such as 5G), and base stations can be deployed on the ground and connected to ground stations that communicate with satellites; satellites can connect to ground stations via wireless links; ground stations and base stations can connect to the core network via wired or wireless links; the core network can connect to the data network. Satellites can communicate with each other via wireless links. Figure 1a In the system shown, the satellites only have the function of transparent transmission and forwarding (i.e., the corresponding base stations are deployed on the ground), and the satellites only achieve transparent transmission and forwarding between each other.

[0103] Figure 1b , Figure 1c A schematic diagram of a satellite communication system in a regeneration scenario is shown. Figure 1b As shown, terminals can access the network via an air interface (which can be of various types, such as a 5G air interface), and base stations can be deployed on satellites (e.g., in satellite regeneration mode), for example, base stations or some base station functions can be deployed on satellites; satellites can complete signaling interaction and user data transmission between base stations, such as... Figure 1c As shown in the diagram. The satellite can connect to the ground station via a wireless link; the ground station can connect to the core network via a wired or wireless link; and the core network can connect to the data network.

[0104] For example, Figures 1a to 1c The various network elements and their interfaces are described below:

[0105] Terminals include mobile devices that support New Radio (NR), such as mobile phones and tablets. Terminals can access satellite networks and initiate calls, access the Internet, and perform other services through the air interface.

[0106] Base stations are used to provide wireless access services, allocate wireless resources to accessing terminals, and provide reliable wireless transmission protocols and data encryption protocols.

[0107] Ground stations are responsible for relaying signaling and service data between satellite base stations and the core network.

[0108] The core network is responsible for services such as user access control, mobility management, session management, and user security authentication or accounting. The core network can consist of multiple functional units, such as functional entities including control plane and data plane components. For example, Figures 1a to 1c The core network shown may include the Access and Mobility Management Function (AMF) and the User Plane Function (UPF). The AMF is responsible for user access management, authentication, and mobility management; the UPF is responsible for managing user plane data transmission and traffic statistics.

[0109] Figures 1a to 1c The air interface shown can be understood as the wireless link between the terminal and the base station, or the wireless link between the satellite and the ground station; the Xn interface can be understood as the interface between base stations, mainly used for signaling interaction such as handover; the NG interface can be used as the interface between the base station and the core network, mainly used for exchanging non-access stratum (NAS) signaling of the core network, as well as user service data.

[0110] It should be understood that the technical solutions provided in the embodiments of this application can be applied to 5G mobile communication systems, future communication systems, and other communication systems, and this application does not make any specific limitations in this regard.

[0111] The terminal in this application embodiment can be the terminal itself, or a device that enables the terminal to perform this function, such as a chip system. This device can be installed in the terminal, or it can be other devices that can perform the terminal's function; no limitation is made here. In this application embodiment, the chip system can be composed of chips, or it can include chips and other discrete components.

[0112] The network device in this application embodiment can be the network device itself, or a device that enables the network device to achieve this function, such as a chip system. This device can be installed in the network device, or it can be other devices that can achieve the function of the network device, without limitation. In the satellite transparent transmission scenario, the network device can be a base station deployed on the ground, connected to the terminal by satellite relay signals; in the satellite regeneration scenario, the network device can be a satellite, that is, the base station is carried on the satellite, such as a communication satellite.

[0113] The following is combined with Figures 2 to 4 This application provides a detailed description of the technical solution provided.

[0114] Figure 2 This is a schematic flowchart illustrating a communication method provided in one embodiment of this application. Figure 2 As shown, the method may include S201 and S202.

[0115] As an example, the method can be executed by the terminal, or by a chip system, hardware circuit and / or software module applied in the terminal, or by other devices capable of implementing the functions of the terminal, without limitation.

[0116] S201, obtain a first receiving opportunity and / or a second receiving opportunity, wherein the first receiving opportunity is the receiving opportunity of the GNSS signal and the second receiving opportunity is the receiving opportunity of the ephemeris data.

[0117] In this embodiment, GNSS signals can be understood as signals transmitted by GNSS satellites. GNSS satellites are used to provide global positioning and navigation services. GNSS signals may contain information such as the precise time of the GNSS satellite, the satellite's identification information, and its ephemeris data. The terminal can determine its GNSS location information through GNSS signals. Ephemeris data can be understood as the ephemeris data of communication satellites.

[0118] As an example, the first reception timing and / or the second reception timing may be predefined by the protocol, or may be pre-configured in the terminal, or the terminal may obtain them through other means; this application does not impose any restrictions on this.

[0119] In this embodiment, the first reception timing and the second reception timing may be related to at least one of the following: the timing deviation tolerance capability of the network device, the frequency deviation tolerance capability of the network device, the GNSS measurement error that the network device can tolerate, the ephemeris calculation error that the network device can tolerate, or GNSS error. Therefore, the terminal obtaining the first reception timing and / or the second reception timing may include: obtaining at least one of the following: the timing deviation tolerance capability of the network device, the frequency deviation tolerance capability of the network device, the GNSS measurement error that the network device can tolerate, the ephemeris calculation error that the network device can tolerate, or GNSS error; and determining the first reception timing and / or the second reception timing based on the obtained at least one piece of information. The timing deviation tolerance capability, the frequency deviation tolerance capability, the GNSS measurement error that the network device can tolerate, and the ephemeris calculation error that the network device can tolerate can be predefined by the protocol or pre-configured in the terminal; this application does not specifically limit this.

[0120] The timing deviation tolerance of a network device refers to the tolerance it can meet regarding the timing deviation of uplink signals transmitted by terminals; in other words, it's the tolerance index for the timing offset error of uplink signals. This index represents both the limit of timing deviation the network device itself can tolerate and the requirement that the uplink signals transmitted by terminals should meet. The timing offset error can be understood as the error between the timing offset determined by the terminal and the actual timing offset between the terminal and the network device. Similarly, the frequency offset tolerance of a network device refers to the tolerance it can meet regarding the frequency offset error of uplink signals transmitted by terminals; in other words, it's the tolerance index for the frequency offset error of uplink signals. This index represents both the limit of frequency offset error the network device itself can tolerate and the requirement that the uplink signals transmitted by terminals should meet. The frequency offset error can be understood as the error between the frequency offset determined by the terminal and the actual frequency offset between the terminal and the network device.

[0121] GNSS measurement error refers to the error in the GNSS position information determined by the terminal using GNSS signals. GNSS measurement error can be understood as the deviation between the GNSS position information determined by the terminal and the actual GNSS position information. Ephemeris calculation error refers to the error in the communication satellite position information (such as position, velocity, etc.) determined by the terminal using ephemeris data. Ephemeris calculation error can be understood as the deviation between the communication satellite position information determined by the terminal and the actual position information of the communication satellite. It should be understood that the GNSS measurement error and ephemeris calculation error that network equipment can tolerate also reflect the timing offset tolerance and frequency offset tolerance capabilities of the network equipment.

[0122] GNSS error refers to errors introduced by the terminal's own performance (e.g., hardware circuitry, software modules, antenna performance). For example, GNSS error can include at least one of the following: error in the GNSS location information determined by the terminal, accuracy of the GNSS location information determined by the terminal, error in the communication satellite location information determined by the terminal, accuracy of the communication satellite location information determined by the terminal, or the terminal's startup accuracy. Terminal startup accuracy can be understood as the time and accuracy required for the terminal to fully start up and reach normal operating status from a powered-off state.

[0123] The first reception timing may include at least one of the following: the first reception period of the GNSS signal, or the reception duration of the GNSS signal within a first reception period. Therefore, the terminal acquiring the first reception timing can be understood as the terminal acquiring the first reception period of the GNSS signal and / or the reception duration of the GNSS signal within a first reception period.

[0124] Figure 3 This is a schematic diagram illustrating a first receiving timing according to an embodiment of this application. Figure 3 As shown, the first reception period for the GNSS signal is N seconds, meaning the terminal can activate once every N seconds to receive the GNSS signal. The reception duration of the GNSS signal within one first reception period is M seconds, meaning the terminal can receive the GNSS signal for M seconds after activation, and can remain in sleep mode for the rest of the time to save power. N and M are positive integers, where M is less than or equal to N. The first reception timing may also include the start time of M.

[0125] It should be noted that the reception duration of GNSS signals within each first reception cycle can be the same or different, such as... Figure 3 The M in the first reception period and the M in the second reception period can be the same or different. The first reception period is as follows: Figure 3 The duration from 0 to N seconds in the second first receiving cycle is as follows: Figure 3 The time interval is from N to 2N. The start time of GNSS signal reception in each first reception cycle can be the same or different.

[0126] In some embodiments, N and M can be 0. In this case, the terminal does not need to determine GNSS location information through GNSS signals.

[0127] The second reception timing may include at least one of the following: the second reception period of the ephemeris data, or the reception duration of the ephemeris data within a second reception period. The second reception timing is similar to the first reception timing; for details, please refer to the aforementioned description of the first reception timing, which will not be repeated here.

[0128] S202, receive GNSS signals according to a first reception timing, and / or receive ephemeris data according to a second reception timing.

[0129] In this embodiment, after obtaining the first reception opportunity, the terminal can receive the GNSS signal according to the first reception opportunity. For example, the terminal can determine the first reception period of the GNSS signal and / or the reception duration of the GNSS signal within a first reception period based on the first reception opportunity, thereby realizing the reception of the GNSS signal.

[0130] In this embodiment, after obtaining the second reception timing, the terminal can receive ephemeris data according to the second reception timing. For example, the terminal can determine the second reception timing of the ephemeris data and / or the reception duration of the ephemeris data within a second reception cycle based on the second reception timing, thereby realizing the reception of the ephemeris data.

[0131] If the terminal only obtains one of the first and second reception opportunities, the other can be determined using existing methods. For example, if the terminal only obtains the first reception opportunity, it can determine the second reception opportunity based on the accuracy requirements of the uplink timing frequency offset specified in the existing protocol for NTN, thereby achieving ephemeris data reception. Alternatively, the terminal can achieve ephemeris data reception based on the second reception opportunity configured by the network device based on assumed terminal performance. It should be noted that the network device can assume the terminal's performance based on the performance of other terminals or other factors, and can configure the second reception opportunity for the terminal based on the assumed terminal performance. However, the actual performance of the terminal may be stronger than the terminal performance assumed by the network device. Therefore, the power consumption is relatively high when the terminal receives ephemeris data based on the second reception opportunity configured by the network device based on assumed terminal performance.

[0132] In this embodiment, after receiving GNSS signals and ephemeris data, the terminal can determine GNSS location information based on the received GNSS signals, and determine the timing offset and frequency offset of the uplink signal based on the GNSS location information and ephemeris data, thereby achieving uplink signal pre-compensation. In this embodiment, since the first and second reception timings are related to the actual timing deviation tolerance of the network device, the frequency deviation tolerance of the network device, and the actual performance of the terminal, and the uplink timing deviation and frequency offset errors that the network device can actually tolerate may be greater than those indicated in the protocol, and the actual performance of the terminal may also be stronger than the terminal capabilities assumed by the network device, when the terminal receives GNSS signals according to the first reception timing and / or receives ephemeris data according to the second reception timing, the terminal does not need to operate continuously, thereby reducing the terminal's power consumption. In some embodiments, if the terminal receives GNSS signals according to the first reception timing and / or receives ephemeris data according to the second reception timing, the terminal can be considered to be in an NTN low-power state.

[0133] It should be noted that currently, after determining the terminal's position and velocity based on GNSS signals and the communication satellite's position and velocity based on ephemeris data, the terminal can determine the relative distance and angle between the terminal and the communication satellite based on their respective positions. After determining the relative distance and angle, the timing offset can be determined based on the relative distance, and the frequency offset can be determined based on the satellite's velocity and the angle between the terminal and the communication satellite. The angle between the terminal and the communication satellite can be understood as the angle between the line connecting the terminal and the communication satellite and the communication satellite's velocity. To ensure that the timing offset and frequency offset determined by the terminal meet the accuracy requirements of the NTN uplink timing frequency offset, the errors in the GNSS position information determined by the terminal and the communication satellite's position information must meet requirements. In other words, the GNSS measurement error and the ephemeris calculation error must meet requirements, which in turn requires that the timing of the terminal receiving the GNSS signal and the timing of receiving the ephemeris data meet requirements. For example, if the GNSS measurement error calculated by the terminal based on the accuracy requirements of the uplink timing frequency offset of NTN specified in the existing protocol is 2 kilometers (km), the timing for the terminal to receive GNSS signals can be determined by combining the terminal's current speed, i.e., how often to receive GNSS signals. Similarly, the timing for the terminal to receive ephemeris data can be determined by combining the satellite's current speed or ephemeris aging rate (e.g., the relationship between time passage and ephemeris error), i.e., how often to receive ephemeris data. Therefore, when the actual timing offset tolerance and / or frequency offset tolerance of the network equipment exceeds the accuracy requirements of the uplink timing frequency offset of NTN specified in the existing protocol, and / or when the actual performance of the terminal exceeds the assumed performance of the network equipment, the terminal can relax the requirements for GNSS measurement error and ephemeris calculation error, reducing the terminal's operating time and saving power consumption.

[0134] Figure 4 This is a schematic flowchart illustrating a communication method provided in yet another embodiment of this application. Figure 4 In the method shown, the terminal can obtain a first reception opportunity and / or a second reception opportunity by interacting with the network device. For example... Figure 4 As shown, the method may include S401 and S402.

[0135] S401, Receive first information, the first information indicating a first reception timing and / or a second reception timing.

[0136] In this embodiment, the network device can send first information to the terminal, the first information indicating a first reception timing and / or a second reception timing. Correspondingly, the terminal can receive the first information. The first information can be carried in signaling, signals, or channels, and this application does not limit this. For example, the first information can be carried in any of the following messages: broadcast message, system message, radio resource control (RRC) message, non-access stratum (NAS) message, system message, or media access control-control element (MAC-CE) signaling.

[0137] In one possible implementation, the network device can indicate the first reception timing and / or the second reception timing by indicating the network device's timing offset tolerance and / or frequency offset tolerance.

[0138] As an example, the network device can directly indicate the numerical values ​​of its timing error tolerance and / or frequency error tolerance. For instance, the first information may include specific values ​​for frequency error tolerance and / or timing error tolerance. Frequency error tolerance indicates the network device's frequency error tolerance. The unit of frequency error tolerance can be Hertz. Timing error tolerance indicates the network device's timing error tolerance. The unit of timing error tolerance can be nanoseconds, the basic time unit for NR, or other time units; this application does not limit this. The basic time unit for NR can be T. c or T s T c =1 / (△f) max *N f ). T s =1 / (△f) ref *N f，ref ). △f max =480*10 3 Hz, N f =4096, △f ref =15*10 3 Hz, N f，ref =2048. T c The number of divisions for the indicator symbol. As an example, the frequency offset error tolerance can be an integer from 0 to 4000. The timing error tolerance can be an integer from 0 to 255.

[0139] As an example, a network device can indicate the numerical range of its timing deviation tolerance and / or frequency deviation tolerance. For instance, the first information may include a first reported value and / or a second reported value. The first reported value may have a first mapping relationship with the frequency deviation tolerance. The second reported value may have a second mapping relationship with the timing deviation tolerance. The first and second mapping relationships can be predefined by a protocol or configured by the network device; this application does not limit this.

[0140] As an example, Table 1 shows a first mapping relationship.

[0141] Table 1

[0142] First Reporting Value Frequency deviation tolerance unit 0 ＜1000 Hz 1 ＜2000 Hz 2 ＜3000 Hz

[0143] As shown in Table 1, the first report value is an integer from 0 to 2. When the first report value is 0, the network device's frequency offset tolerance is less than 1000Hz; when the first report value is 1, the network device's frequency offset tolerance is less than 2000Hz; and when the first report value is 2, the network device's frequency offset tolerance is less than 3000Hz. It should be noted that a frequency offset tolerance of less than 1000Hz can be understood as the network device being able to tolerate an uplink signal frequency offset error of no more than 1000Hz.

[0144] In one possible implementation, the timing deviation tolerance and frequency deviation tolerance of the network device can be related to third information. This third information may include at least one of the following: the signal type of the uplink signal transmitted by the terminal, the modulation order of the uplink signal, the format of the pilot sequence of the uplink signal, the RRC status of the terminal, the network procedure executed by the terminal, the terminal's movement speed, the subcarrier spacing (SCS) of the uplink signal, the communication system in which the terminal operates, or the manufacturer of the network device. Therefore, the network device can indicate its timing deviation tolerance and frequency deviation tolerance by sending this third information. In other words, the terminal can obtain the timing deviation tolerance and frequency deviation tolerance of the network device by acquiring this third information. The terminal can obtain the manufacturer of the network device through broadcast system messages.

[0145] The uplink signal types transmitted by the terminal include, but are not limited to: physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), physical random access channel (PRACH), and sounding reference signal (SRS). The demodulation modes of the uplink signals include, but are not limited to: quadrature phase shift keying (QPSK) and quadrature amplitude modulation (QAM). QAM can include 16QAM and 64QAM. Specifically, QPSK has a modulation order of 2, 16QAM has a modulation order of 4, and 64QAM has a modulation order of 6. The pilot sequence of the uplink signal can be a demodulation reference signal (DMRS) sequence. The format of the pilot sequence is, for example, the number of columns in the pilot sequence. The RRC state of the terminal can include: idle, connected, and inactive. The network processes executed by the terminal may include random access processes, handover processes, paging processes, etc. In some embodiments, the timing deviation tolerance and / or frequency deviation tolerance of the network device may differ when the terminal executes different steps of the same network process. The terminal's movement speed may include one or more speed levels, such as low speed, medium speed, and fast speed. The speed levels of the terminal can be set according to actual needs, and this application does not limit this. The uplink signal SCS may be, for example, 15 kHz, 30 kHz, etc., and this application does not limit this. The communication system in which the terminal operates can be a satellite communication system or an NR communication system, and this is not limited. That is, when the terminal operates in different communication systems, the timing deviation tolerance and / or frequency deviation tolerance of the network device may differ. The network device manufacturer may be any network device manufacturer.

[0146] As an example, Table 2 shows the relationship between the demodulation mode of an uplink signal and the timing deviation tolerance and frequency deviation tolerance of network devices.

[0147] Table 2

[0148] Demodulation mode Frequency deviation tolerance Timing deviation tolerance 64QAM 0.5ppm 1 / 2CP 16QAM 1ppm 1 / 2CP QPSK 2ppm 1 / 2CP

[0149] The cyclic prefix (CP) is formed by copying the signal from the tail of an orthogonal frequency division multiplexing (OFDM) symbol to the head.

[0150] In one possible implementation, the network device can indicate the first reception timing and / or the second reception timing by indicating the GNSS measurement errors and / or ephemeris calculation errors that the network device can tolerate. For example, the network device can determine the GNSS measurement errors and / or ephemeris calculation errors that the network device can tolerate based on its own timing offset tolerance and frequency offset tolerance, and then send the first information to the terminal.

[0151] In one possible implementation, the network device can directly indicate the first reception timing and / or the second reception timing. For example, the network device can determine the first reception timing and / or the second reception timing based on its own timing offset tolerance and frequency offset tolerance, and then send the first information to the terminal.

[0152] S402, determine the first receiving timing and / or the second receiving timing based on the first information.

[0153] In this embodiment, after receiving the first information, the terminal can determine the first receiving time and / or the second receiving time based on the first information.

[0154] In some embodiments, after receiving the first information, the terminal may determine the first receiving time and / or the second receiving opportunity based on the actual performance of the terminal and the first information.

[0155] If the terminal can only determine one of the first reception timing and the second reception timing, the other can be determined according to existing methods. For details, please refer to the relevant description in S202, which will not be repeated here.

[0156] In this embodiment, when the first information indicates the timing offset tolerance and / or frequency offset tolerance of the network device, or when the first information indicates the GNSS measurement error and / or ephemeris calculation error that the network device can tolerate, no specific restrictions are placed on the specific implementation method of the terminal determining the first and second reception timing based on the first information. For example, the terminal can reverse-engineer the first and / or second reception timing based on the current method of determining the timing offset and frequency offset of the uplink signal based on GNSS location information and ephemeris data.

[0157] In this embodiment, the accuracy requirements for timing and frequency offset of uplink signals can be reduced based on the actual timing and frequency offset tolerance capabilities of the network device and the actual performance of the terminal, thereby saving terminal power consumption and achieving energy saving. Furthermore, the actual timing and frequency offset tolerance capabilities of the network device can be related to information such as the signal type and modulation order of the uplink signal transmitted by the terminal, thus improving the flexibility of the terminal in performing uplink signal pre-compensation.

[0158] In some embodiments, the network device may proactively send first information to the terminal. For example, after the terminal randomly accesses the network, the network device may send the first information to the terminal. For example, the network device may send the first information during RRC configuration, RRC reconfiguration, or capability information exchange. Alternatively, the network device may indicate a first reception timing and / or a second reception timing to the terminal via system messages.

[0159] In some embodiments, the network device may send the first information to the terminal after receiving the request information from the terminal. For example, the terminal may send second information to the network device, the second information being used to request a first reception timing and / or a second reception timing. Accordingly, the network device may receive the second information and, after receiving the second information, send the first information to the terminal. The second information may be carried in an RRC message, and this application does not impose any restrictions on this.

[0160] In some implementations, the terminal may include a GNSS receiver. For example, the GNSS receiver may be located within the terminal. Alternatively, the GNSS receiver may be independent of the terminal, and the terminal may be able to invoke the GNSS receiver. In some embodiments, the GNSS receiver may be a GNSS chip, which is not limited in this application. Therefore, GNSS location information can also be understood as the location of the GNSS receiver.

[0161] In this implementation, the GNSS receiver can be used to receive GNSS signals and ephemeris data. Therefore, the first reception timing can be understood as the timing when the GNSS receiver receives GNSS signals, and the second reception timing can be understood as the timing when the GNSS receiver receives ephemeris data. Thus, after determining the first and second reception timings, the terminal can instruct the GNSS receiver on the first and second reception timings, enabling the GNSS receiver to receive both GNSS signals and ephemeris data.

[0162] Optionally, after receiving a GNSS signal, the GNSS receiver can output Q GNSS results every P seconds. P and Q are positive integers. The GNSS results may include GNSS location information, such as the location of the GNSS receiver, including its longitude, latitude, and altitude. Accordingly, the terminal can receive the GNSS results. In some embodiments, P and Q can be 0.

[0163] Optionally, after receiving ephemeris data, the GNSS receiver can also output communication satellite position information U times every O seconds. O and U are positive integers. Correspondingly, the terminal can receive the communication satellite position information. In some embodiments, O and U can be 0.

[0164] In this implementation, the terminal can determine the uplink signal timing offset and frequency offset based on the GNSS results output by the GNSS receiver and the communication satellite position information, thereby pre-compensating the uplink signal when transmitting it.

[0165] In some implementations, the terminal in the technical solution provided in this application can be replaced with a GNSS receiver, that is, the GNSS receiver performs the various operations or steps performed by the terminal in the aforementioned method embodiments.

[0166] Figure 5 This is a schematic diagram of the structure of a communication device provided in one embodiment of this application. Figure 5 The illustrated device 500 can be used to implement the various steps / operations performed by the terminal in the aforementioned method embodiments. For example... Figure 5 As shown, the device 500 may include a processing module 510 and a receiving module 520.

[0167] As an example, device 500 can be used to implement Figure 2 The methods shown are the various steps / operations performed by the terminal. For example, processing module 510 can be used to implement S201; receiving module 520 can be used to implement S202.

[0168] As an example, device 500 can be used to implement Figure 4 The methods shown include the various steps / operations performed by the terminal. For example, processing module 510 can be used to implement S402; receiving module 520 can be used to implement the operations performed by the terminal in S401.

[0169] In some embodiments, the apparatus 500 may further include a sending module 530. The sending module 530 may be used to send second information to a network device.

[0170] Figure 6 This is a schematic diagram of the structure of a communication device provided in another embodiment of this application. Figure 6 The apparatus shown can be used to implement the various steps / operations performed by the network device in the foregoing method embodiments. For example... Figure 6 As shown, the device 600 may include a transmitting module 610.

[0171] As an example, device 600 can be used to implement Figure 4 The methods shown include the various steps / operations performed by the network device. For example, the sending module 610 can be used to implement the operations performed by the network device in S401.

[0172] In some embodiments, the device 600 may further include a processing module 620 and a receiving module 630. The processing module 620 may be used to determine first information before sending the first information. The receiving module 630 may be used to receive second information sent by the terminal.

[0173] Figure 7 This is a schematic diagram of the structure of a communication device provided in another embodiment of this application. Figure 7 The apparatus 700 shown can be used to implement the method executed by a terminal or network device in any of the foregoing embodiments.

[0174] like Figure 7 As shown, the device 700 of this embodiment includes a memory 710, a processor 720, a communication interface 730, and a bus 740. The memory 710, processor 720, and communication interface 730 are interconnected via the bus 740.

[0175] The memory 710 can be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 710 can store programs, and when the program stored in the memory 710 is executed by the processor 720, the processor 720 uses it to execute... Figure 2 or Figure 4 The steps in the method shown are performed by the terminal or network device.

[0176] The processor 720 may be a general-purpose central processing unit (CPU), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, used to execute relevant programs to implement the communication method shown in the embodiments of this application.

[0177] The processor 720 can also be an integrated circuit chip with signal processing capabilities. In implementation, each step of the communication method shown in the embodiments of this application can be completed by the integrated logic circuitry in the processor 720 or by software instructions.

[0178] The processor 720 described above can also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor.

[0179] The steps of the method disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory 710. The processor 720 reads the information in memory 710 and, in conjunction with its hardware, completes the functions required by the units included in the communication device of this application. For example, it can execute... Figure 2 or Figure 4 The steps / functions performed by the terminal or network device in the method shown.

[0180] Alternatively, the memory 710 and the processor 720 can be integrated together.

[0181] The communication interface 730 can use, but is not limited to, transceivers to enable communication between the device 700 and other devices or apparatuses.

[0182] Bus 740 may include a pathway for transmitting information between various components of device 700 (e.g., memory 710, processor 720, communication interface 730).

[0183] Some embodiments of this application also provide a computer program product that, when run on a processor, can implement the methods shown in the foregoing embodiments. Some embodiments of this application also provide a computer-readable storage medium containing computer instructions that, when run on a processor, can implement the methods shown in the foregoing embodiments.

[0184] It should be noted that the modules or components shown in the above embodiments can be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), etc. Furthermore, when a module is implemented by a processing element calling program code, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors capable of calling program code, such as a controller. Additionally, these modules can be integrated together to implement a system-on-a-chip (SOC).

[0185] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, software modules, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0186] The term "multiple" in this document refers to two or more. The term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates an "or" relationship between the preceding and following related objects; in formulas, " / " indicates a "division" relationship. Additionally, it should be understood that in the description of this application, words such as "first" and "second" are used only for descriptive purposes and should not be construed as indicating or implying relative importance or order.

[0187] It is understood that the terms "exemplary" or "for example" used herein are intended to mean as an example, illustration, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0188] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application.

[0189] It is understood that, in the embodiments of this application, the order of the above-mentioned process numbers does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

Claims

1. A communication method, characterized in that, The method is applied to a terminal, and the method includes: A first reception timing and / or a second reception timing are obtained, wherein the first reception timing and the second reception timing are determined based on at least one of the following: the timing deviation tolerance capability of the network device, the frequency deviation tolerance capability of the network device, the GNSS measurement error that the network device can tolerate, the ephemeris calculation error or GNSS error that the network device can tolerate, the first reception timing being the reception timing of the GNSS signal, and the second reception timing being the reception timing of the ephemeris data. The GNSS signal is received according to the first reception timing, and / or the ephemeris data is received according to the second reception timing.

2. The method according to claim 1, characterized in that, The acquisition of the first receiving timing and / or the second receiving timing includes: Receive first information, the first information indicating the first receiving time and / or the second receiving time.

3. The method according to claim 2, characterized in that, The first information indicates the timing deviation tolerance capability and / or frequency deviation tolerance capability of the network device.

4. The method according to claim 3, characterized in that, The timing deviation tolerance and the frequency deviation tolerance are related to at least one of the following: the signal type of the uplink signal transmitted by the terminal, the modulation order of the uplink signal, the format of the pilot sequence of the uplink signal, the Radio Resource Control (RRC) status of the terminal, the network procedure executed by the terminal, the moving speed of the terminal, the communication system in which the terminal is located, or the manufacturer of the network equipment.

5. The method according to claim 3 or 4, characterized in that, The first information indicates a numerical value or range of the timing deviation tolerance capability; and / or, The first information indicates the numerical value or range of the frequency offset tolerance capability.

6. The method according to claim 2, characterized in that, The first information indicates the GNSS measurement error that the network device can tolerate and / or the ephemeris calculation error that the network device can tolerate.

7. The method according to any one of claims 2 to 6, characterized in that, The method further includes: Send a second message, which is used to request the first message.

8. The method according to claim 1, characterized in that, The first reception timing and / or the second reception timing are predefined.

9. The method according to any one of claims 1 to 8, characterized in that, The first reception timing includes at least one of the following: the first reception period of the GNSS signal, or the reception duration of the GNSS signal within a first reception period; and / or, The second reception timing includes at least one of the following: the second reception period of the ephemeris data, or the reception duration of the ephemeris data within a second reception period.

10. A communication method, characterized in that, The method is applied to a network device, and the method includes: First information is determined, the first information indicating a first reception timing and / or a second reception timing, the first reception timing being the reception timing of GNSS signals, and the second reception timing being the reception timing of ephemeris data; Send the first message.

11. The method according to claim 10, characterized in that, The first information indicates the timing deviation tolerance capability and / or the frequency deviation tolerance capability of the network device, and the first reception timing and / or the second reception timing are determined based on at least one of the following: the timing deviation tolerance capability of the network device, or the frequency deviation tolerance capability of the network device.

12. The method according to claim 11, characterized in that, The timing deviation tolerance capability and the frequency deviation tolerance capability are related to at least one of the following: the signal type of the uplink signal transmitted by the terminal, the modulation order of the uplink signal, the format of the pilot sequence of the uplink signal, the Radio Resource Control Protocol (RRC) status of the terminal, the network procedure executed by the terminal, the moving speed of the terminal, the communication system in which the terminal is located, or the manufacturer of the network equipment.

13. The method according to claim 11 or 12, characterized in that, The first information indicates a numerical value or range of the timing deviation tolerance capability; and / or, The first information indicates the numerical value or range of the frequency offset tolerance capability.

14. The method according to claim 10, characterized in that, The first information indicates the GNSS measurement error that the network device can tolerate and / or the ephemeris calculation error that the network device can tolerate. The first reception timing and / or the second reception timing are determined based on at least one of the following: the GNSS measurement error that the network device can tolerate, or the ephemeris calculation error that the network device can tolerate.

15. The method according to any one of claims 10 to 14, characterized in that, The method further includes: Receive second information, which is used to request the first information.

16. The method according to any one of claims 10 to 15, characterized in that, The first reception timing includes at least one of the following: the first reception period of the GNSS signal, or the reception duration of the GNSS signal within a first reception period; and / or, The second reception timing includes at least one of the following: the second reception period of the ephemeris data, or the reception duration of the ephemeris data within a second reception period.

17. A communication device, characterized in that, It includes various functional modules for implementing the method as claimed in any one of claims 1 to 9 or any one of claims 10 to 16.

18. A communication device, characterized in that, include: A processor coupled to a memory for storing a computer program, which, when invoked by the processor, causes the apparatus to perform the method as claimed in any one of claims 1 to 9 or any one of claims 10 to 16.

19. A computer program product, characterized in that, It includes computer program code that, when run on a computer, causes the computer to implement the method as claimed in any one of claims 1 to 9 or any one of claims 10 to 16.

20. A computer-readable medium, characterized in that, The computer-readable medium stores program code for computer execution, the program code including instructions for performing the method as claimed in any one of claims 1 to 9 or any one of claims 10 to 16.

Images