Communication method and apparatus, computer-readable storage medium, and computer program product

By adopting phased GNSS accuracy error requirements and resource management in satellite communication terminal equipment, the problem of excessive power consumption of terminal equipment in idle state is solved, a balance between power consumption and synchronization performance is achieved, and the equipment's battery life and communication efficiency are improved.

WO2026233147A1PCT designated stage Publication Date: 2026-11-12HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/092937
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-04-24
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In satellite communications, frequent GNSS measurements performed by terminal devices in idle states result in excessive power consumption, affecting the terminal devices' battery life and efficiency.

Method used

Terminal equipment adopts different GNSS accuracy error requirements at different stages. When sending random access preamble, a lower error requirement is adopted to reduce power consumption. After accessing the network, a higher error requirement is adopted to ensure uplink synchronization performance. Power consumption and synchronization performance are optimized through closed-loop frequency offset correction and semi-static resource management.

Benefits of technology

While ensuring uplink synchronization performance, it significantly reduces the power consumption of terminal devices, thereby improving the battery life and communication efficiency of terminal devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026092937_12112026_PF_FP_ABST
    Figure CN2026092937_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The embodiments of the present disclosure provide a communication method and apparatus, a computer-readable storage medium, and a computer program product, which can be applied to a non-terrestrial network (NTN), such as a satellite communication system. In the method, a terminal apparatus sends a random access preamble to a network apparatus, wherein the sending of the random access preamble satisfies a first error requirement. The terminal apparatus also performs global navigation satellite system (GNSS) measurement. The terminal apparatus further sends, to the network apparatus, an indication of completing GNSS measurement, wherein the sending of the indication of completing GNSS measurement satisfies a second error requirement. The first error requirement is lower than the second error requirement. In this way, different GNSS accuracy error requirements are satisfied, such that a first error requirement is applied when a random access preamble is sent (at which time, a terminal apparatus has not accessed a network), while a second error requirement is applied when an indication of completing GNSS measurement is sent (at which time, the terminal apparatus has accessed the network or is about to access the network), and different error requirements are applied as needed at different stages, thereby allowing for a reduction in power consumption overhead by using a lower first error requirement, while ensuring uplink synchronization performance by using a higher second error requirement.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method, apparatus, computer-readable storage medium and program product

[0001] This application claims priority to the Chinese Invention Patent Application No. 202510603608.1, filed on May 9, 2025, and entitled “Communication method, apparatus, computer-readable storage medium and program product”, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0002] The present disclosure relates generally to the field of communications, and more specifically to a communication method, apparatus, computer-readable storage medium and computer program product. BACKGROUND

[0003] Satellite communication has many advantages compared to ground communication, for example, it can provide communication services for some areas that ground communication network cannot cover, such as oceans and forests, provide wider coverage, ensure that users on airplanes, trains, etc. obtain better communication services, enhance the reliability of communication, are not easily damaged by natural disasters or external forces, and provide more data transmission resources for communication, and improve the speed of the network. Therefore, satellite communication has significant advantages in terms of wide coverage, reliability, multi-connection, high throughput, etc., and supporting communication with the ground and with satellites is an inevitable trend for future communication.

[0004] However, the round-trip transmission delay of satellite communication is large, and the terminal needs to perform uplink timing advance compensation according to its own position and the position of the satellite obtained by global navigation satellite system (GNSS) measurement to achieve uplink synchronization. For a terminal in an idle state, since it does not know when there is an access demand, the terminal may frequently perform GNSS measurement in the idle state, which will cause a large power consumption overhead. SUMMARY

[0005] Embodiments of the present disclosure provide a communication method, apparatus, computer-readable storage medium and computer program product, which can reduce the power consumption overhead of the terminal side while ensuring the uplink synchronization performance.

[0006] The first aspect of the present disclosure provides a communication method, the execution subject of the method is a terminal device, which can be a terminal device, or a component (e.g., a module, a communication module, a circuit or a chip responsible for a communication function (such as a modem chip, also known as a baseband chip, or a system on chip (SoC) chip or a system in package (SIP) chip containing a modem core) in a terminal device, and can also be a logical node, a logical module or software that can realize all or part of the functions of a terminal device. In the method, the terminal device sends a random access preamble to a network device, the sending of the random access preamble meets a first error requirement. The terminal device also performs a global navigation satellite system (GNSS) measurement. The terminal device also sends an indication of completing the GNSS measurement to the network device, the sending of the indication of completing the GNSS measurement meets a second error requirement. Wherein, the first error requirement is lower than the second error requirement. In this way, different GNSS accuracy error requirements are achieved, so that the first error requirement is used when sending the random access preamble (at this time the terminal device has not accessed the network), and the second error requirement is used when sending the indication of completing the GNSS measurement (at this time the terminal device has accessed or is close to accessing the network), different error requirements are used as needed in different links, which can not only reduce power consumption overhead by using the lower first error requirement, but also ensure uplink synchronization performance by using the higher second error requirement.

[0007] In some implementations, the first error requirement includes at least one of a first timing error requirement or a first frequency offset error requirement; and the second error requirement includes at least one of a second timing error requirement or a second frequency offset error requirement. In this way, the timing error requirement and / or the frequency offset error requirement used by the terminal device and the network device can be aligned.

[0008] In some implementations, the uplink transmission applying the first error requirement is associated with closed-loop frequency offset error correction; or the uplink transmission applying the second error requirement is not associated with closed-loop frequency offset error correction. In this way, when the lower first error requirement is applied, the error needs to be corrected by closed-loop frequency offset error correction to ensure uplink synchronization performance, and when the higher second error requirement is applied, the error does not need to be corrected by closed-loop frequency offset error correction, reducing the closed-loop frequency offset correction overhead and reducing the impact on location-dependent mobility management.

[0009] In some implementations, the uplink transmission of the terminal device satisfies the first error requirement before the GNSS measurement is completed or the sending of the indication of the completion of the GNSS measurement. In this way, the boundary for determining the switching error requirement is determined as the boundary before the sending of the indication of the completion of the GNSS measurement, and the error requirements adopted are aligned between the terminal device and the network device.

[0010] In some implementations, the method further includes: the terminal device receiving, from the network device, confirmation information of the indication of the completion of the GNSS measurement, wherein the accumulated closed-loop timing adjustment amount and / or closed-loop frequency offset adjustment amount is cleared before the receiving of the confirmation information. In this way, the terminal device can determine that the network device has received the indication of the completion of the GNSS measurement, which is conducive to the synchronization between the terminal device and the network device, and can reduce the adjustment amount storage overhead in the case of adopting the higher second error requirement.

[0011] In some implementations, the confirmation information includes at least one of the closed-loop timing adjustment amount or the closed-loop frequency offset adjustment amount. In this way, the network device can configure a new closed-loop timing adjustment amount and / or closed-loop frequency offset adjustment amount to the terminal device to ensure the uplink synchronization performance.

[0012] In some implementations, the method further includes: the terminal device receiving, from the network device, configuration information about at least one semi-static resource. Wherein the sending, by the terminal device to the network device, of the indication of the completion of the GNSS measurement includes: sending the indication of the completion of the GNSS measurement by using a first semi-static resource of the at least one semi-static resource. In this way, the terminal device can send the indication of the completion of the GNSS measurement to the network device by using the semi-static resource configured by the network device.

[0013] In some implementations, the first semi-static resource is determined based on the time of the completion of the GNSS measurement. In this way, a way of determining the specific semi-static resource for sending the indication of the completion of the GNSS measurement is given.

[0014] The second aspect of the present disclosure provides a communication method, the execution subject of the method can be a terminal device, the terminal device can be a terminal equipment, or a component (e.g., a module, a communication module, a circuit or a chip responsible for a communication function (such as a modem chip, also known as a baseband chip, or a system on chip (SoC) chip or a system in package (SIP) chip containing a modem core), a logical node, a logical module or software capable of realizing all or part of the functions of the terminal equipment. In the method, the terminal device sends a random access preamble to a network device, the sending of the random access preamble satisfies a third error requirement. The terminal device also performs a global navigation satellite system (GNSS) measurement. The terminal device also sends an indication of completing the GNSS measurement to the network device. The terminal device also receives, from the network device, confirmation information of the indication of completing the GNSS measurement. The terminal device also performs uplink transmission to the network device, the uplink transmission satisfies a fourth error requirement, and the third error requirement is lower than the fourth error requirement. In this way, different GNSS accuracy error requirements are achieved, the third error requirement is used when sending the random access preamble (at this time, the terminal device has not accessed the network), and the fourth error requirement is used after receiving the confirmation information of the indication of completing the GNSS measurement, and when performing the uplink transmission (at this time, the terminal device has accessed the network or is close to accessing the network). Different error requirements are used in different links as needed, which can not only reduce the power consumption overhead by using the lower third error requirement, but also ensure the uplink synchronization performance by using the higher fourth error requirement. In addition, the error requirements are switched based on the terminal device receiving the confirmation information of the indication of completing the GNSS measurement, which is conducive to aligning the error requirements used between the terminal device and the network device, and further ensures the accuracy of the alignment between the network and the terminal.

[0015] In some implementations, the third error requirement includes at least one of a third timing error requirement or a third frequency offset error requirement; and the fourth error requirement includes at least one of a fourth timing error requirement or a fourth frequency offset error requirement. In this way, the timing error requirements and / or the frequency offset error requirements used between the terminal device and the network device can be aligned.

[0016] In some implementations, the uplink transmission applying the third error requirement is associated with closed-loop frequency offset error correction; or the uplink transmission applying the fourth error requirement is not associated with closed-loop frequency offset error correction. In this way, when the lower third error requirement is applied, the error needs to be corrected by the closed-loop frequency offset error correction to ensure the uplink synchronization performance, and when the higher fourth error requirement is applied, the error does not need to be corrected by the closed-loop frequency offset error correction, which reduces the closed-loop frequency offset correction overhead and reduces the impact on the location-dependent mobility management.

[0017] In some implementations, at least one of the following is satisfied before the reception of the confirmation information: the accumulated closed loop timing adjustment amount is the closed loop timing adjustment amount; or the accumulated closed loop frequency offset adjustment amount is the closed loop frequency offset adjustment amount. In this way, it is ensured that the accumulated closed loop timing adjustment amount and / or the closed loop frequency offset adjustment amount can be employed for error adjustment before the terminal device receives the confirmation information of the indication of completion of GNSS measurement.

[0018] In some implementations, the indication of completion of GNSS measurement is transmitted through at least one of: a physical uplink control channel (PUCCH); a medium access control control element (MAC CE); uplink control information (UCI); a random access request message based on a non-contention based random access procedure; or a random access request message based on a contention based random access procedure. In this way, different ways of transmitting the indication of completion of GNSS measurement are given, and signaling overhead can be saved compared to introducing new signaling to transmit the indication of completion of GNSS measurement.

[0019] In some implementations, the confirmation information comprises at least one of a closed loop timing adjustment amount or a closed loop frequency offset adjustment amount. In this way, the network device is able to configure the terminal device with additional closed loop timing adjustment amount and / or closed loop frequency offset adjustment amount.

[0020] In some implementations, the method further comprises: receiving, by the terminal device, configuration information about the at least one semi-static resource from the network device. Wherein the transmitting, by the terminal device, the indication of completion of GNSS measurement to the network device comprises: transmitting the indication of completion of GNSS measurement using a first semi-static resource of the at least one semi-static resource. In this way, the terminal device can use the semi-static resource configured by the network device to transmit the indication of completion of GNSS measurement to the network device.

[0021] In some implementations, the first semi-static resource is determined based on a time of completion of GNSS measurement. In this way, a way of determining a specific semi-static resource for transmitting the indication of completion of GNSS measurement is given.

[0022] The third aspect of the present disclosure provides a communication method, and an execution subject of the method is a network device. The network device can be a network equipment, or a component (e.g., a module, a communication module, a circuit or a chip responsible for communication function (e.g., a modem chip, or a SoC chip or a SIP chip containing a modem core), a chip system or a processor) in a communication equipment, and can also be a logic node, a logic module or software capable of realizing all or part of the function of the communication equipment. In the method, the network device receives a random access preamble from a terminal device, and the transmission of the random access preamble satisfies a first error requirement. The network device receives an indication of completing GNSS measurement from the terminal device, and the transmission of the indication of completing GNSS measurement satisfies a second error requirement, wherein the first error requirement is lower than the second error requirement. In this way, different GNSS accuracy error requirements are achieved, so that the first error requirement is used when the random access preamble is received (at this time, the terminal device has not accessed the network), and the second error requirement is used when the indication of completing GNSS measurement is received (at this time, the terminal device has accessed or is close to accessing the network), and different error requirements are used in different links as needed, which can not only reduce the power consumption overhead by using the lower first error requirement, but also ensure the uplink synchronization performance by using the higher second error requirement.

[0023] In some implementations, the first error requirement includes at least one of a first timing error requirement or a first frequency offset error requirement; and the second error requirement includes at least one of a second timing error requirement or a second frequency offset error requirement. In this way, the timing error requirement and / or the frequency offset error requirement used by the terminal device and the network device can be aligned.

[0024] In some implementations, the uplink transmission applying the first error requirement is associated with closed-loop frequency offset error correction; or the uplink transmission applying the second error requirement is not associated with closed-loop frequency offset error correction. In this way, when the lower first error requirement is applied, the error needs to be corrected by the closed-loop frequency offset error correction to ensure the uplink synchronization performance, and when the higher second error requirement is applied, the error does not need to be corrected by the closed-loop frequency offset error correction, which reduces the closed-loop frequency offset correction overhead and reduces the impact on the location-dependent mobility management.

[0025] In some implementations, before the completion of the GNSS measurement or the transmission of the indication of completing the GNSS measurement, the uplink transmission of the terminal device satisfies the first error requirement. In this way, the completion of the GNSS measurement or the transmission of the indication of completing the GNSS measurement is used as a boundary to determine the boundary of switching the error requirement, and the error requirements used by the terminal device and the network device are aligned.

[0026] In some implementations, the method further includes the network device sending, to the terminal device, confirmation information of the indication of completing the GNSS measurement. In this way, the terminal device can determine that the network device has received the indication of completing the GNSS measurement, facilitating the synchronization between the terminal device and the network device.

[0027] In some implementations, the confirmation information includes at least one of a closed loop timing adjustment amount or a closed loop frequency offset adjustment amount. In this way, the network device can configure a new closed loop timing adjustment amount and / or a closed loop frequency offset adjustment amount to the terminal device to guarantee the uplink synchronization performance.

[0028] In some implementations, the method further includes the network device sending, to the terminal device, configuration information about the at least one semi-static resource. Wherein the network device receiving, from the terminal device, the indication of completing the GNSS measurement includes receiving the indication of completing the GNSS measurement using a first semi-static resource of the at least one semi-static resource. In this way, the network device can receive the indication of completing the GNSS measurement from the terminal device using the configured semi-static resource.

[0029] In some implementations, the first semi-static resource is determined based on a time of completing the GNSS measurement. In this way, a manner of determining a specific semi-static resource for sending the indication of completing the GNSS measurement is given.

[0030] In some implementations, the method further includes releasing, in response to receiving the indication of completing the GNSS measurement, remaining semi-static resources of the at least one semi-static resource. In this way, the reserved semi-static resources are released after the GNSS measurement is completed, optimizing the resource allocation.

[0031] The fourth aspect of the present disclosure provides a communication method, the execution subject of the method can be a network device, the network device can be a network equipment, or a component (such as a module, a communication module, a circuit or a chip responsible for communication function (such as a modem chip, or a SoC chip or a SIP chip containing a modem core), a chip system or a processor) in a communication equipment, and can also be a logic node, a logic module or software capable of realizing all or part of the communication equipment function. In the method, the network device receives a random access preamble from a terminal device, the transmission of the random access preamble satisfies a third error requirement. The network device also receives an indication of completing GNSS measurement from the terminal device. The network device also sends confirmation information of the indication of completing GNSS measurement to the terminal device. The network device also receives an uplink transmission from the terminal device, the uplink transmission satisfies a fourth error requirement, wherein the third error requirement is lower than the fourth error requirement. In this way, different GNSS accuracy error requirements are realized, so that the third error requirement is used when the random access preamble is received (at this time the terminal device has not accessed the network), and the fourth error requirement is used after the confirmation information of the indication of completing GNSS measurement is sent and the uplink transmission is received (at this time the terminal device has accessed the network or is close to accessing the network), different error requirements are used in different links as needed, both the lower third error requirement is used to reduce power consumption overhead, and the higher fourth error requirement is used to ensure uplink synchronization performance. In addition, the error requirement is switched based on the terminal device receiving the confirmation information of the indication of completing GNSS measurement, which is beneficial to aligning the error requirements used between the terminal device and the network device, and further ensures the accuracy of the alignment between the network and the terminal.

[0032] In some implementations, the third error requirement includes at least one of a third timing error requirement or a third frequency offset error requirement; and the fourth error requirement includes at least one of a fourth timing error requirement or a fourth frequency offset error requirement. In this way, the timing error requirement and / or the frequency offset error requirement used between the terminal device and the network device can be aligned.

[0033] In some implementations, the uplink transmission to which the third error requirement is applied is associated with closed-loop frequency offset error correction; or the uplink transmission to which the fourth error requirement is applied is not associated with closed-loop frequency offset error correction. In this way, when the lower third error requirement is applied, the error needs to be corrected through closed-loop frequency offset error correction to ensure uplink synchronization performance, and when the higher fourth error requirement is applied, the error does not need to be corrected through closed-loop frequency offset error correction, reducing the closed-loop frequency offset correction overhead and reducing the impact on the location-dependent mobility management.

[0034] In some implementations, the indication of completion of the GNSS measurement is transmitted through at least one of: a physical uplink control channel (PUCCH); a medium access control control element (MAC CE); uplink control information (UCI); a random access request message of a non-contention-based random access procedure; or a random access request message of a contention-based random access procedure. In this way, different ways of transmitting the indication of completion of the GNSS measurement are given, and signaling overhead can be saved compared to introducing new signaling to transmit the indication of completion of the GNSS measurement.

[0035] In some implementations, the confirmation information includes at least one of a closed loop timing adjustment amount or a closed loop frequency adjustment amount. In this way, the network apparatus can configure a new closed loop timing adjustment amount and / or a closed loop frequency adjustment amount to the terminal apparatus to ensure uplink synchronization performance.

[0036] In some implementations, the method further includes: transmitting, by the network apparatus, configuration information about the at least one semi-static resource to the terminal apparatus. Wherein receiving, by the network apparatus, the indication of completion of the GNSS measurement from the terminal apparatus includes receiving the indication of completion of the GNSS measurement using a first semi-static resource of the at least one semi-static resource. In this way, the network apparatus can receive the indication of completion of the GNSS measurement from the terminal apparatus using the configured semi-static resource.

[0037] In some implementations, the first semi-static resource is determined based on a time of completion of the GNSS measurement. In this way, a way of determining a specific semi-static resource for transmitting the indication of completion of the GNSS measurement is given.

[0038] In some implementations, the method further includes: releasing, in response to receiving the indication of completion of the GNSS measurement, remaining semi-static resources of the at least one semi-static resource. In this way, the reserved semi-static resources are released after completion of the GNSS measurement, optimizing resource allocation.

[0039] A fifth aspect of the present disclosure provides a communication apparatus, the advantages of which can be referred to the description of the first aspect, the second aspect, the third aspect, and / or the fourth aspect, which will not be described here. The communication apparatus has functions to implement the behaviors in the method examples of the above-mentioned first aspect, the second aspect, the third aspect, and / or the fourth aspect. The functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions. In one possible design, the communication apparatus includes units performing the methods of the first aspect, the second aspect, the third aspect, and / or the fourth aspect or their implementation manners.

[0040] The sixth aspect of the present disclosure provides an apparatus, comprising: a processor configured to perform any method according to the first aspect, the second aspect, the third aspect, and / or the fourth aspect and implementation manners thereof. Optionally, further comprising a memory storing computer programs or instructions. The computer programs or instructions, when executed by the processor, cause the electronic device to perform any method according to the first aspect, the second aspect, the third aspect, and / or the fourth aspect and implementation manners thereof.

[0041] The seventh aspect of the present disclosure provides a processing apparatus, comprising a processor and an input / output interface, for example, applied in a terminal apparatus and / or a network apparatus, for implementing functions or methods involved in the above-mentioned first aspect, the second aspect, the third aspect, and / or the fourth aspect. The processing apparatus can be a chip system, for example. In a feasible implementation manner, the chip system further comprises a memory, configured to store program instructions and data necessary for implementing functions of the methods in the above-mentioned first aspect, the second aspect, the third aspect, and / or the fourth aspect.

[0042] The chip system in the above-mentioned aspects can be a system on chip (SOC), or a baseband chip, etc. The baseband chip can comprise a processor, a channel encoder, a digital signal processor, a modem, an interface module, etc.

[0043] In the specific implementation process, the input signal received by the input interface can be received and input by a receiver, for example, but is not limited to. The output signal output by the output interface can be output to and transmitted by a transmitter, for example, but is not limited to. The input interface and the output interface can be an integrated same interface, which is used as the input interface and the output interface at different times, respectively. The present application does not limit the specific implementation manner of the processor and various interfaces.

[0044] The eighth aspect of the present disclosure provides a computer readable storage medium, which stores computer programs or instructions. The computer programs or instructions, when executed by an electronic device, cause the electronic device to perform the method performed by the apparatus in the above-mentioned aspects.

[0045] The ninth aspect of the present disclosure provides a computer program (product), which comprises computer programs or instructions. The computer programs or instructions, when executed by an electronic device, cause the electronic device to perform the method performed by the apparatus in the above-mentioned aspects.

[0046] A tenth aspect of this disclosure provides a chip system including a processor for implementing the functions of the means in the methods of the above aspects. In one possible design, the chip system further includes a memory for storing computer programs or instructions and / or data. This chip system may be composed of chips or may include chips and other discrete devices.

[0047] The eleventh aspect of this disclosure provides a communication system, including: communication means for performing the first aspect, the second aspect, the third aspect, and / or the fourth aspect. Attached Figure Description

[0048] Figure 1 shows a schematic diagram of a communication system according to some embodiments of the present disclosure.

[0049] Figure 2 illustrates a schematic diagram of a satellite network application scenario according to some embodiments of the present disclosure.

[0050] Figure 3 illustrates a schematic diagram of a satellite network application scenario according to some other embodiments of the present disclosure.

[0051] Figure 4 illustrates a schematic diagram of a communication flow according to some embodiments of the present disclosure.

[0052] Figure 5 illustrates a schematic diagram of a communication flow according to some other embodiments of the present disclosure.

[0053] Figure 6 shows a schematic flowchart of implementation at a terminal device according to some embodiments of the present disclosure.

[0054] Figure 7 shows a schematic flowchart of implementation at a terminal device according to some other embodiments of the present disclosure.

[0055] Figure 8 shows a schematic flowchart of implementation at a network device according to some embodiments of the present disclosure.

[0056] Figure 9 shows a schematic flowchart of implementation at a network device according to some other embodiments of the present disclosure.

[0057] Figure 10 is a block diagram of a device that can be used to implement some embodiments of this application.

[0058] Figure 11 is a schematic diagram of the structure of an apparatus according to some embodiments of this application.

[0059] Figure 12 is a schematic diagram of the structure of an apparatus according to some other embodiments of this application.

[0060] Figure 13 is a schematic diagram of the structure of an apparatus according to some other embodiments of the present application.

[0061] Figure 14 is a schematic diagram of the structure of an apparatus according to some other embodiments of the present application. Detailed Implementation

[0062] Embodiments of the present disclosure will be described in more detail with reference to the drawings. While certain embodiments of the present disclosure are shown in the drawings, it is understood that the embodiments of the present disclosure can be embodied by various forms, and should not be interpreted as being limited to the embodiments set forth herein, but rather, the embodiments are provided so that the present disclosure can be more thoroughly and completely understood. It is understood that the drawings of the present disclosure and the embodiments are for exemplary purposes only, and are not intended to limit the scope of protection of the present disclosure.

[0063] In the description of embodiments of the present disclosure, the term "comprising" and its conjugations should be understood to encompass the meanings of "consisting of" and "consisting essentially of", i.e., "comprising but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "an embodiment" should be understood as "at least one embodiment". The terms "a first", "a second", etc. can refer to different or the same objects. Other explicit and implicit definitions can also be included below.

[0064] Embodiments of the present disclosure can be implemented according to any appropriate communication protocol, including but not limited to, cellular communication protocols such as third generation (3G), fourth generation (4G), fifth generation (5G), and future communication protocols, wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol now known or developed in the future. The technical solutions provided in the present application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems. The methods provided in the embodiments of the present application can also be applied to non-terrestrial network (NTN) communication systems or scenarios in which NTNs are integrated with terrestrial networks (TNs). The NTN system can be an NTN system integrated with 4G, 5G, and any future generation communication system, such as an NR NTN, an IoT NTN, etc. The NTN communication system may, for example, be a satellite communication system, or it can include unmanned aerial vehicles, high altitude platform stations (HAPS), and other aerial access network devices, which are not limited in the present application.

[0065] Figure 1 illustrates a schematic diagram of a communication system 100 according to some embodiments of the present disclosure. As shown in Figure 1, the communication system 100 of the embodiments of the present disclosure shows a terminal device 102 and at least one network device. Exemplarily, the at least one network device may include network devices 104 and 106. In some examples, network device 104 may be an access network device, such as a base station, satellite base station, ground station, satellite ground station, etc. In some examples, network device 106 may be a core network device. In some embodiments, the communication system 100 may be used in a satellite communication scenario, such as a multi-orbit satellite scenario. In some embodiments, the terminal device 102 may send a random access preamble to the network device 104, the transmission of which may satisfy a first error requirement. The terminal device 102 may perform Global Navigation Satellite System (GNSS) measurements. The terminal device 102 may send an indication of completion of GNSS measurements to the network device 104, the transmission of which may satisfy a second error requirement. The first error requirement is lower than the second error requirement. It should be noted that although Figure 1 uses a single terminal device and network device as examples for illustration, the communication system 100 may include any number of terminal devices or network devices.

[0066] The communication system 100 in this disclosure includes, but is not limited to: narrowband Internet of Things (NB-IoT), global system for mobile communications (GSM), enhanced data rate for GSM evolution (EDGE), wideband code division multiple access (WCDMA), code division multiple access 2000 (CDMA2000), time division-synchronization code division multiple access (TD-SCDMA), long term evolution (LTE), long term evolution advanced (LTE-A), and the three major application scenarios of 5G mobile communication systems: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and enhanced machine type communication (eMTC).

[0067] In the embodiments of this disclosure, the term "terminal" or "terminal device" refers to any terminal device capable of wired or wireless communication with network devices or with each other. A terminal device may sometimes be referred to as user equipment (UE). A terminal device can be any type of mobile terminal, fixed terminal, or portable terminal. A terminal device can be various wireless communication devices with wireless communication capabilities. For example, a terminal device (such as terminal device 102 as shown in FIG1) can be a user equipment, terminal, access terminal, terminal unit, terminal station, mobile station (MS), remote station, remote terminal, mobile terminal, wireless communication device, terminal agent, or terminal device, etc. A terminal device can also be a communication chip with a communication module, a vehicle with communication capabilities, or in-vehicle equipment (such as an in-vehicle communication device, in-vehicle communication chip), etc. Terminal equipment can also be a component within a terminal device (e.g., a module, communication module, circuitry or chip responsible for communication functions, such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip), or a logical node, logical module, or software capable of implementing all or part of the terminal device's functions. This terminal device may have wireless transceiver capabilities, enabling it to communicate (e.g., wireless communication) with one or more network devices in one or more communication systems and receive network services provided by these network devices, including but not limited to access network devices. User equipment includes, but is not limited to, mobile terminals, mobile telephones, handsets, portable equipment, mobile stations, and computers with wireless communication capabilities. User equipment can be portable, pocket-sized, handheld, built-in computer, vehicle-mounted, aircraft-mounted, or other mobile devices. User equipment can be connected via a radio access network. The network (RAN) communicates with one or more core networks. Terminal devices can be used to send uplink signals to network devices or receive downlink signals from network devices. Terminal devices can also be communication modules with satellite communication capabilities, satellite phones or components thereof, or satellite communication terminals, such as very small aperture terminals (VSATs), portable stations, fixed stations, vehicle-mounted or airborne satellite communication terminals, etc.It should be understood that satellite communication terminals can act as micro base stations to further provide data interfaces to accessed user equipment.

[0068] The terminal device can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in 5G or future communication networks, or terminal device in a future evolved PLMN network, etc.

[0069] Specifically, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.

[0070] In addition, terminal devices can be deployed on the ground, including indoors or outdoors, handheld or vehicle-mounted. Terminal devices can also be deployed on water (such as ships). Terminal devices can also be deployed in the air (e.g., on airplanes, balloons, and satellites).

[0071] Various devices with wireless communication capabilities can be used to connect people, objects, and machines. Terminal devices can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer (P2P), M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation, autonomous delivery, etc. Terminal devices can be terminals in any of the above scenarios, such as MTC terminals, IoT terminals, etc. Terminal devices can be third-generation partner projects (3GPPs).rd The term "terminal equipment" refers to user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile equipment, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, SIP phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (e.g., drones, helicopters, multi-helicopters, quad-helicopters, or airplanes), ship, remote control device, smart home device, industrial equipment, or devices built into the aforementioned devices (e.g., communication modules, modems, or chips in the aforementioned devices), or other processing devices connected to a wireless modem, all conforming to the 3GPP (Generation Partnership Project) standard. In the following text, "terminal equipment," "terminal device," "terminal," and "UE" are used interchangeably. In some scenarios, terminal equipment can also be used as a base station. For example, the terminal device can act as a scheduling entity, providing sidelink signals between UEs in scenarios such as V2X, D2D, or P2P.

[0072] In this embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be a device that supports the terminal device in implementing the functions, such as a chip system or a chip. This device can be installed in the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0073] The network device in this embodiment (network device 104 as shown in Figure 1) can be a device for communicating with terminal devices. This network device can also be called an access network device or a radio access network device, such as an access network device (or access point). The network device can be used to receive uplink signals from the terminal device or send downlink signals to the terminal device. An access network device refers to a device that provides network access functionality, such as a radio access network (RAN) base station. Specifically, the network device may include a base station (BS), or a base station and radio resource management equipment for controlling the base station. The network device may also include relay stations (relay equipment), access points, and base stations in 5G networks or NR base stations, or base stations in future PLMN networks. The network device can be a wearable device or an in-vehicle device. The network device can also be a communication chip with a communication module. Network equipment can also be a component in communication equipment (e.g., a module, communication module, circuit or chip responsible for communication functions (such as a modem chip, or a SoC chip or SIP chip containing a modem core), chip system, or processor), or a logical node, logical module, or software that can implement all or part of the functions of the communication equipment. Base stations include, but are not limited to, ordinary base stations (such as gNB, eNB, or NodeB), remote radio units (RRUs), macro stations, micro stations (pico, femto, etc.), relays, access points (APs) with wireless transceiver capabilities, transmission reception points (TRPs), or any other wireless access device. Base stations are used to provide wireless access services to terminal devices.For example, network equipment (such as access network equipment) includes, but is not limited to: base stations (g nodeB, gNB) in 5G, mobile communication base stations in future communication systems, evolved node B (eNB) in long term evolution (LTE) systems, radio network controllers (RNC), radio controllers (RNCs) in cloud radio access networks (CRAN) systems, base station controllers (BSCs), home base stations (e.g., home evolved nodeB, or home node B, HNB), baseband units (BBUs), transmitting and receiving points (TRPs), transmitting points (TPs), mobile switching centers, and can also be evolved NBs (eNBs or eNodeBs) in LTE, base station equipment in future 5G networks, access network equipment in future evolved PLMN networks, access nodes in Wi-Fi systems, and wearable devices or vehicle-mounted devices. Network equipment can also be satellites (or satellite base stations) or high altitude platform stations (HAPS), or base station equipment mounted on satellites / HAPS. Satellites can include at least one of the following: geostationary earth orbit (GEO) satellites (or geosynchronous orbit satellites) or non-geostationary earth orbit (NGEO) satellites. Non-geostationary earth orbit satellites can include at least one of the following: medium earth orbit (MEO) satellites or low earth orbit (LEO) satellites. There are no restrictions here. Network equipment can also be gateway stations (or ground stations, earth stations, signaling stations, gateways, or gateway stations).

[0074] In some deployments, network devices can be centralized units (CUs) or distributed units (DUs). Network devices may also include active antenna units (AAUs). The CU implements some of the network device's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing the functions of the radio resource control (RRC) layer and the packet data convergence protocol (PDCP) layer. The DU handles physical layer protocols and real-time services, implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of the active antenna. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered as being sent by the DU, or by the DU+AAU. It is understood that network devices can be one or more of the following: CU nodes, DU nodes, and AAU nodes. Furthermore, CUs can be classified as network devices in the radio access network (RAN) or in the core network (CN), and this application does not limit this classification. Examples of network devices include, but are not limited to, NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), future communication system NodeBs (gNBs), Transmitter Receiver Points (TRPs), Remote Radio Units (RRUs), Radio Heads (RHs), Remote Radio Heads (RRHs), Integrated Access and Backhaul (IAB) nodes, low-power nodes such as femtonodes, piconodes, reconfigurable smart surfaces (RISs), and network-controlled repeaters. In different communication systems, CUs (or CU-CPs and CU-UPs), DUs, or RUs may have different names, but their meanings will be understood by those skilled in the art. For example, in the ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU.For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0075] Furthermore, network devices such as access network devices (network device 106 as shown in Figure 1) can be core network devices or devices connected to the core network (CN). Core network devices can be used to provide core network services to access network devices and terminal devices. Core network devices can correspond to different devices in different systems. For example, in 3G, core network devices can correspond to the Serving GPRS Support Node (SGSN) and / or the Gateway GPRS Support Node (GGSN) of the General Packet Radio System (GPRS). In 4G, core network devices can correspond to the Mobility Management Entity (MME) and / or the Serving Gateway (S-GW). In 5G, core network devices can correspond to the Access and Mobility Management Function (AMF), the Session Management Function (SMF), or the User Plane Function (UPF).

[0076] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0077] In this embodiment, the means for implementing the function of the network device can be the network device itself, or it can be a means that enables the network device to implement the function, such as a chip system or a chip, which can be installed in the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0078] Network devices and terminal devices can be deployed on the ground, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0079] RAN can be a 3GPP-related cellular system, such as 4G, 5G mobile communication systems, or future-oriented evolution systems. RAN can also be an open access network (open RAN, O-RAN or ORAN), (cloud RAN, CRAN), or wireless fidelity (WiFi) system. RAN can also be a communication system that integrates two or more of the above systems.

[0080] Figure 2 illustrates a schematic diagram of a satellite network application scenario 200 according to some embodiments of the present disclosure. As shown in Figure 2, the communication system 200 according to embodiments of the present disclosure includes a terminal, a base station, a ground station, a user plane processing unit, a data network, and a control plane (including access mobility management function and session management function). The base station can be a 4G base station (also called an LTE base station) or a 5G base station (also called an NR base station). The terminal can access the base station through the air interface, and the base station can access the ground station through the NG interface (for NR) or the S1 interface (for LTE). The ground station is connected to the user plane (including the user plane processing unit and data network) and control plane (including access mobility function and session management function) of the core network. The base station can be deployed on a satellite (called a satellite base station) and connected to the ground core network through a wireless link, or it can be deployed on the ground (called a ground base station). When the base station is deployed on a satellite, there can be a wireless link between satellites to realize signaling interaction and user data transmission between base stations. The ground station is responsible for forwarding signaling and service data between the base station and the core network. Base stations connect to each other via the Xn interface (for NR) or the X2 interface (for LTE) for signaling exchange, such as handover. The NG interface can act as the interface between the NR 5G base station and the NR 5G core network, used for exchanging non-access stratum (NAS) signaling and user service data. The S1 interface can act as the interface between the LTE 4G base station and the LTE 4G core network, used for exchanging NAS signaling and user service data.

[0081] Figure 3 illustrates a schematic diagram of a satellite network application scenario 300 according to some other embodiments of the present disclosure. As shown in Figure 3, the communication system 300 according to an embodiment of the present disclosure includes a terminal, a satellite, a base station, a ground station, a user plane processing unit, a data network, and a control plane (including access mobility management functions and session management functions). The satellite can act as a transparent relay node, used to relay signaling interaction and user data transmission between the terminal and the ground station and ground base station. In this scenario, communication between satellites is typically not possible.

[0082] Generally, satellite communication offers numerous advantages over terrestrial communication. For example, it can provide communication services to areas inaccessible to terrestrial networks, such as oceans and forests, offering wider coverage, ensuring higher-quality communication services for users on airplanes and trains, enhancing reliability, reducing susceptibility to natural disasters or external damage, and providing more data transmission resources, thus increasing network speed. Therefore, satellite communication boasts significant advantages in wide coverage, reliability, multiple connections, and high throughput, and supporting both terrestrial and satellite communication is an inevitable trend for future communication.

[0083] However, satellite communication has a significant round-trip transmission delay. Terminals need to perform uplink timing advance compensation based on their own position and the satellite's position obtained through Global Navigation Satellite System (GNSS) measurements to achieve uplink synchronization. Currently, only fixed GNSS accuracy requirements are specified, and these requirements are relatively high. However, the inventors of this disclosure have discovered that terminals sometimes do not require such high GNSS accuracy. For example, for terminals in idle mode, since they do not know when there will be access needs, they will frequently perform GNSS measurements in idle mode to ensure that they meet the high GNSS accuracy requirements, which will cause significant power consumption. However, for terminals in idle mode, even if the GNSS accuracy requirement is reduced, it does not affect subsequent uplink transmission because uplink transmission can still be compensated for by closed-loop timing error correction and / or closed-loop frequency offset error correction. For connected users, a higher GNSS accuracy requirement is needed to reduce the overhead of closed-loop timing error correction and / or closed-loop frequency offset error correction, and to reduce the impact on location-dependent mobility management. How to ensure uplink transmission reliability while reducing power consumption is a problem that needs to be solved.

[0084] To address this, some embodiments of this disclosure provide a GNSS accuracy error requirement switching scheme applicable to the scenarios shown in Figures 1 to 3. In some embodiments, the terminal device can send a random access preamble to the network device, the transmission of which satisfies a first error requirement. The terminal device can also perform Global Navigation Satellite System (GNSS) measurements. The terminal device can also send an indication of completion of GNSS measurements to the network device, the transmission of which satisfies a second error requirement. The first error requirement is lower than the second error requirement. In these embodiments of this disclosure, different GNSS accuracy error requirements are implemented, such that the first error requirement is used when sending the random access preamble (when the terminal device has not yet connected to the network), and the second error requirement is used when sending the indication of completion of GNSS measurements (when the terminal device has connected to the network or is close to connecting to the network). By using different error requirements as needed at different stages, it is possible to reduce power consumption by utilizing the lower first error requirement and ensure uplink synchronization performance by utilizing the higher second error requirement.

[0085] Other embodiments of this disclosure provide another GNSS accuracy error requirement switching scheme applicable to the scenarios shown in Figures 1 to 3. In some embodiments, the terminal device can send a random access preamble to the network device, the transmission of which satisfies a third error requirement. The terminal device can also perform Global Navigation Satellite System (GNSS) measurements. The terminal device can also send an indication of completion of GNSS measurements to the network device. The terminal device can also receive confirmation information from the network device regarding the completion of GNSS measurements. The terminal device can also perform uplink transmissions to the network device, the uplink transmissions satisfying a fourth error requirement, wherein the third error requirement is lower than the fourth error requirement. In this way, different GNSS accuracy error requirements are implemented, such that the third error requirement is used when sending the random access preamble (when the terminal device has not yet connected to the network), and the fourth error requirement is used after receiving confirmation information regarding the completion of GNSS measurements and performing uplink transmissions (when the terminal device has connected to the network or is close to connecting to the network). Different error requirements are used as needed at different stages, which can reduce power consumption by utilizing the lower third error requirement and ensure uplink synchronization performance by utilizing the higher fourth error requirement. Furthermore, switching error requirements based on the confirmation information received by the terminal device indicating the completion of GNSS measurements is beneficial for aligning the error requirements used between the terminal device and the network device, further ensuring the accuracy of network and terminal alignment. It should be understood that the terms "first error requirement," "second error requirement," "third error requirement," and "fourth error requirement" are for illustrative purposes only and are not intended to limit the scope of this disclosure. "Third error requirement" can also be "first error requirement," and "fourth error requirement" can also be "second error requirement."

[0086] Figure 4 illustrates a schematic diagram of a communication flow 400 according to some embodiments of the present disclosure. As shown in Figure 4, flow 400 involves a terminal device 402 and a network device 404. Terminal device 402 may correspond to terminal device 102 shown in Figure 1, and network device 404 may correspond to network device 104 shown in Figure 1. In some examples, the terminal device 402 involved in flow 400 may be replaced by a chip, module, or assembly in the terminal device 402. The network device 404 involved in flow 400 may be replaced by a chip, module, or assembly in the network device 404. In some examples, terminal device 402 is, for example, a UE (User Equipment). In some examples, network device 404 may be a base station, such as a gNB (Gateway Node.js), or a ground station.

[0087] In process 400, at point 410, terminal device 402 sends a random access preamble to network device 404, the transmission of which satisfies a first error requirement. At point 420, terminal device 402 performs Global Navigation Satellite System (GNSS) measurements. At point 430, terminal device 402 sends an indication of completion of GNSS measurements to network device 404, the transmission of which satisfies a second error requirement. The first error requirement (a more lenient requirement) is lower than the second error requirement (a more stringent requirement). In this way, different GNSS accuracy error requirements are implemented, allowing the first error requirement to be used when sending the random access preamble (before terminal device 402 is connected to the network), and the second error requirement to be used when sending the indication of completion of GNSS measurements (when terminal device 402 is connected to or nearing network access). By employing different error requirements at different stages, the lower first error requirement can be used to reduce power consumption, while the higher second error requirement can be used to ensure uplink synchronization performance.

[0088] As an example, as shown in Table 1, the first error requirement corresponds to a GNSS accuracy of 2500m (i.e., a relatively lenient GNSS accuracy), and the second error requirement corresponds to a GNSS accuracy of 50m (i.e., a more stringent GNSS accuracy). Assuming the average hourly power consumption of the GNSS chip is 23mAh when activated every 1 second, then when designing to support a terminal speed of 180km / h (i.e., 50m / s), to meet the 50m GNSS positioning accuracy requirement, a GNSS measurement needs to be performed every second, resulting in an average hourly power consumption of 23mAh, and a daily power consumption of 23*24 = 552mAh. When designing to support a terminal speed of 30km / h (i.e., 8.3m / s), to meet the 50m GNSS positioning accuracy requirement, a GNSS measurement needs to be performed every 6 seconds. The average hourly power consumption is 1 / 6 of that at a terminal speed of 180km / h, and the daily power consumption is 23*24*1 / 6 = 92mAh. When designing a terminal to support a speed of 180 km / h (50 m / s), to meet the 2500 m GNSS positioning accuracy requirement, a GNSS measurement needs to be performed every 50 seconds. This means the average hourly power consumption is 1 / 50th of the power consumption under the 50 m GNSS positioning accuracy requirement, resulting in a daily power consumption of 23 * 24 * 1 / 50 = 11.04 mAh. When designing a terminal to support a speed of 30 km / h (8.3 m / s), to meet the 2500 m GNSS positioning accuracy requirement, a GNSS measurement needs to be performed every 300 seconds. The average hourly power consumption is 1 / 6th of that at a speed of 180 km / h, resulting in a daily power consumption of 11.04 * 1 / 6 = 1.84 mAh. Therefore, the terminal consumes less power under the more lenient 2500 m GNSS accuracy requirement, but more power under the stricter 50 m GNSS accuracy requirement.

[0089] Table 1

[0090] In some examples, the first error requirement includes at least one of a first timing error requirement or a first frequency offset error requirement, and the second error requirement includes at least one of a second timing error requirement or a second frequency offset error requirement. Different GNSS accuracy error requirements (e.g., the first error requirement, the second error requirement) can be implemented by direct definition or by defining different timing error requirements and / or spectral error requirements, and then extrapolating them based on the defined different timing error requirements and / or spectral error requirements. The timing error requirement can also be referred to as the time offset error requirement. The first error requirement and the second error requirement can also be referred to as the first time-frequency offset error requirement and the second time-frequency offset error requirement. As an example, the timing error requirement can be presented in the form shown in Table 2. To address frequency offset error requirements, the basic measurement interval for the modulated carrier frequency of a non-terrestrial network (NTN) satellite UE is one UL time slot. The NTN satellite UE pre-compensates the uplink modulated carrier frequency by estimating the Doppler frequency shift. Compared with the ideal pre-compensated reference uplink carrier frequency, the average value of the basic measurement of the NTN UE modulated carrier frequency is accurate to ±0.1 parts per million (PPM) during a 1ms cumulative measurement interval.

[0091] Table 2

[0092] In some examples, uplink transmissions applying the first error requirement are associated with closed-loop frequency offset error correction, while uplink transmissions applying the second error requirement are not associated with closed-loop frequency offset error correction. In other words, because the first error requirement is more lenient, it requires closed-loop frequency offset error correction to ensure uplink synchronization performance, while the second error requirement is more stringent, so it does not require closed-loop frequency offset error correction to reduce closed-loop frequency offset correction overhead and minimize the impact on location-dependent mobility management. In other examples, uplink transmissions applying the first error requirement may also be associated with closed-loop timing error correction, while uplink transmissions applying the second error requirement may not be associated with closed-loop timing error correction. In still other examples, both uplink transmissions applying the first and second error requirements may be associated with closed-loop timing error correction, but uplink transmissions applying the first error requirement are associated with more closed-loop timing error correction, while uplink transmissions applying the second error requirement are associated with fewer closed-loop timing error correction.

[0093] In some examples, the uplink transmission of terminal device 402 meets a first error requirement before the completion of GNSS measurement or the transmission of an indication of completion of GNSS measurement. In this case, although a more lenient first error requirement is adopted, synchronization between terminal device 402 and network device 404 can still be guaranteed through closed-loop frequency offset error correction. In some embodiments, the uplink transmission of terminal device 402 meets a second error requirement after the completion of GNSS measurement or the transmission of an indication of completion of GNSS measurement.

[0094] In some examples, the method further includes: the terminal device 402 receiving confirmation information from the network device 404 regarding the completion of GNSS measurement. In this way, the terminal device 402 can determine that the network device 404 has received the indication of completion of GNSS measurement, which is beneficial for synchronization between the terminal device 402 and the network device 404. Prior to receiving the confirmation information, the accumulated closed-loop timing adjustment and / or closed-loop frequency offset adjustment are cleared to zero. In some examples, besides Msg2 indicating the absolute values ​​of closed-loop timing error and closed-loop frequency offset error, other indications regarding timing error and frequency offset error are adjustment amounts, i.e., increasing or decreasing the adjustment timing advance amount based on the current amount to correct the timing advance error introduced by the terminal or ephemeris error. The terminal device 402 needs to continuously accumulate the adjustment amount indicated by the network side. In this example, if the terminal has completed the GNSS measurement and obtained the correct location information, the previously accumulated closed-loop timing adjustment and / or closed-loop frequency offset adjustment are cleared to zero, thus reducing the adjustment amount storage overhead when using a higher second error requirement.

[0095] In some examples, the confirmation information may include at least one of closed-loop timing adjustment or closed-loop frequency offset adjustment. Since the previous adjustment is reset to zero, the adjustment configured through the confirmation information is equivalent to an absolute value. In this way, network device 404 can configure new closed-loop timing adjustment and / or closed-loop frequency offset adjustment to terminal device 402 to ensure uplink synchronization performance.

[0096] In some examples, terminal device 402 receives configuration information about at least one semi-static resource from network device 404. Terminal device 402 can use a first semi-static resource among the at least one semi-static resource to send an indication of GNSS measurement completion. In this way, terminal device 402 can use the semi-static resources configured by network device 404 to send the indication of GNSS measurement completion to network device 404. The first semi-static resource can be determined based on the time of GNSS measurement completion. In this way, the terminal can select the semi-static resource closest to the time of GNSS measurement completion to send the indication of GNSS measurement completion, providing a method for determining the specific semi-static resource used to send the indication of GNSS measurement completion. In some examples, in response to receiving the indication of GNSS measurement completion, network device 404 can release the remaining semi-static resources among the at least one semi-static resource. In this way, reserved semi-static resources are released after GNSS measurement is completed, optimizing resource allocation and avoiding resource waste.

[0097] With respect to the embodiments described above in Figure 4, a more lenient first error requirement is adopted when the terminal is not connected to the network, so the terminal does not need to perform GNSS measurements frequently, which can reduce power consumption. After the terminal completes the GNSS measurement or sends an indication that the GNSS measurement is completed, a more stringent second error requirement is adopted to meet the uplink synchronization requirements.

[0098] Figure 5 illustrates a schematic diagram of a communication flow 500 according to some other embodiments of the present disclosure. As shown in Figure 5, flow 500 involves a terminal device 502 and a network device 504. Terminal device 502 may correspond to terminal device 102 shown in Figure 1, and network device 504 may correspond to network device 104 shown in Figure 1. In some examples, the terminal device 502 involved in flow 500 may be replaced by a chip, module, or assembly in terminal device 502. The network device 504 involved in flow 500 may be replaced by a chip, module, or assembly in network device 504. In some examples, terminal device 502 is, for example, a UE (User Equipment). In some examples, network device 504 may be a base station, such as a gNB (Gateway Node.js), or a ground station.

[0099] In process 500, at 510, terminal device 502 sends a random access preamble to network device 504, the transmission of which satisfies a third error requirement. At 520, terminal device 502 performs a Global Navigation Satellite System (GNSS) measurement. At 530, terminal device 502 sends an indication of completion of the GNSS measurement to network device 504, the transmission of which satisfies a fourth error requirement. The third error requirement (a more lenient error requirement) is less stringent than the fourth error requirement (a more stringent error requirement). At 540, terminal device 502 receives confirmation information from network device 504 regarding the indication of completion of the GNSS measurement. At 550, terminal device 502 performs an uplink transmission to network device 504, the uplink transmission satisfying the fourth error requirement. It should be understood that the terms "first error requirement," "second error requirement," "third error requirement," and "fourth error requirement" are for illustrative purposes only and are not intended to limit the scope of this disclosure. The "third error requirement" can also be the "first error requirement," and the "fourth error requirement" can also be the "second error requirement." In this way, different GNSS accuracy error requirements are achieved. A third error requirement is used when sending the random access preamble (before the terminal device 502 is connected to the network), and a fourth error requirement is used after receiving confirmation of the completion of the GNSS measurement and during uplink transmission (when the terminal device 502 is connected to or near the network). Different error requirements are used as needed at different stages. This allows for reducing power consumption using the lower third error requirement and ensuring uplink synchronization performance using the higher fourth error requirement. Furthermore, switching the error requirement based on the terminal device 502 receiving confirmation of the completion of the GNSS measurement facilitates alignment between the terminal device 502 and the network device 504, further ensuring the accuracy of network and terminal alignment.

[0100] Similar to the embodiment described with reference to Figure 4, the third error requirement can correspond to a GNSS accuracy of 2500m (i.e., a more lenient GNSS accuracy), and the fourth error requirement can correspond to a GNSS accuracy of 50m (i.e., a more stringent GNSS accuracy). Specific embodiments of the first and second error requirements described with reference to Figure 4 are applicable to the third and fourth error requirements in process 500, and will not be repeated here.

[0101] In some examples, the third error requirement includes at least one of a third timing error requirement or a third frequency offset error requirement, and the fourth error requirement includes at least one of a fourth timing error requirement or a fourth frequency offset error requirement. Different GNSS accuracy error requirements (e.g., the third error requirement, the fourth error requirement) can be implemented by direct definition, or by defining different timing error requirements and / or spectral error requirements, and then calculating them based on the defined different timing error requirements and / or spectral error requirements. In this way, the terminal device 502 and the network device 504 can be aligned using the adopted timing error requirements and / or frequency offset error requirements.

[0102] In some examples, uplink transmissions applying the third error requirement are associated with closed-loop frequency offset error correction, while uplink transmissions applying the fourth error requirement are not. In other words, because the third error requirement is more lenient, it requires closed-loop frequency offset error correction to ensure uplink synchronization performance, while the fourth error requirement is more stringent, so it does not require closed-loop frequency offset error correction, thus reducing closed-loop frequency offset correction overhead and minimizing the impact on location-dependent mobility management. In other examples, uplink transmissions applying the third error requirement may also be associated with closed-loop timing error correction, while uplink transmissions applying the fourth error requirement may not be associated with closed-loop timing error correction. In still other examples, both uplink transmissions applying the third and fourth error requirements may be associated with closed-loop timing error correction, but uplink transmissions applying the third error requirement are associated with more closed-loop timing error correction, while uplink transmissions applying the fourth error requirement are associated with fewer closed-loop timing error correction.

[0103] In some examples, the accumulated closed-loop timing adjustment and / or accumulated closed-loop frequency offset adjustment are used before the confirmation information is received. In this example, a more lenient fourth error requirement is still applied before the terminal receives confirmation information indicating completion of the GNSS measurement, therefore, correction is needed using the accumulated closed-loop timing adjustment and / or accumulated closed-loop frequency offset adjustment. In this way, it is ensured that error adjustment can be performed using the accumulated closed-loop timing adjustment and / or closed-loop frequency offset adjustment before the terminal device 502 receives confirmation information indicating completion of the GNSS measurement.

[0104] In some examples, the indication of completion of GNSS measurements can be sent via the Physical Uplink Control Channel (PUCCH). Alternatively or additionally, the indication of completion of GNSS measurements can be sent via the Media Access Control Unit (MAC CE). Alternatively or additionally, the indication of completion of GNSS measurements can be sent via Uplink Control Information (UCI). Alternatively or additionally, the indication of completion of GNSS measurements can be sent via a random access request message (e.g., Msg1) based on a non-contention-based random access procedure. In this example, the indication of completion of GNSS measurements can be sent using a random access request message based on a non-contention-based random access procedure and the resources allocated for the random access procedure, saving the overhead of introducing additional signaling and requiring no additional resource allocation. Alternatively or additionally, the indication of completion of GNSS measurements can be sent via a random access request message (e.g., MsgA) based on a contention-based random access procedure. In this example, the random access request message of a contention-based random access procedure and the resources allocated for the random access procedure can be used to send the indication of completion of GNSS measurements. This saves the overhead of introducing additional signaling and requires no additional resource allocation, and also reduces the occupation of non-contention-based random access sequences. The above describes a different way of sending the indication of completion of GNSS measurements, and it saves signaling overhead compared to introducing new signaling to send the indication of completion of GNSS measurements.

[0105] In some examples, the confirmation information includes at least one of closed-loop timing adjustment or closed-loop frequency offset adjustment. In this way, network device 504 can configure additional closed-loop timing adjustment and / or closed-loop frequency offset adjustment to terminal device 502.

[0106] In some examples, terminal device 502 receives configuration information about at least one semi-static resource from network device 504. Terminal device 502 can use a first semi-static resource among the at least one semi-static resource to send an indication of GNSS measurement completion. In this way, terminal device 502 can use the semi-static resources configured by network device 504 to send the indication of GNSS measurement completion to network device 504. The first semi-static resource can be determined based on the time of GNSS measurement completion. In this way, the terminal can select the semi-static resource closest to the time of GNSS measurement completion to send the indication of GNSS measurement completion, providing a method for determining the specific semi-static resource used to send the indication of GNSS measurement completion. In some examples, in response to receiving the indication of GNSS measurement completion, network device 504 can release the remaining semi-static resources among the at least one semi-static resource. In this way, reserved semi-static resources are released after GNSS measurement is completed, optimizing resource allocation and avoiding resource waste.

[0107] By employing a more lenient third error requirement when the terminal is not connected to the network, the terminal does not need to perform GNSS measurements frequently, thus reducing power consumption. After the terminal receives confirmation from the network that the GNSS measurement is complete, a stricter second error requirement is adopted to meet uplink synchronization requirements. Furthermore, in the embodiment described in Figure 4, if the network does not receive confirmation of GNSS measurement completion, the network and terminal may not have aligned understandings of the error requirements. Compared to the embodiment described in Figure 4, the embodiment described in Figure 5 uses the confirmation of GNSS measurement completion received by the terminal from the network as the time limit, further ensuring the accuracy of alignment between the network and the terminal.

[0108] Figure 6 illustrates a schematic flowchart 600 implemented at a terminal device according to some embodiments of the present disclosure. As shown in Figure 6, the process 600 can be executed by a terminal device, such as terminal device 402 or a chip, module, or assembly within terminal device 402. In block 610, the terminal device sends a random access preamble to a network device, the transmission of which satisfies a first error requirement. In block 620, the terminal device performs a Global Navigation Satellite System (GNSS) measurement. In block 630, the terminal device sends an indication of completion of the GNSS measurement to the network device, the transmission of which satisfies a second error requirement. The first error requirement is lower than the second error requirement. In some embodiments, the process 600 may also include other operations performed at terminal device 402 as described in conjunction with Figure 4 in embodiments of the present disclosure.

[0109] Figure 7 illustrates a schematic flowchart 700 implemented at a terminal device according to some other embodiments of the present disclosure. As shown in Figure 7, process 700 can be executed by a terminal device, such as terminal device 502 or a chip, module, or assembly within terminal device 502. In block 710, the terminal device sends a random access preamble to a network device, the transmission of which satisfies a third error requirement. In block 720, the terminal device performs a Global Navigation Satellite System (GNSS) measurement. In block 730, the terminal device sends an indication of completion of the GNSS measurement to the network device. In block 740, the terminal device receives confirmation information from the network device regarding the completion of the GNSS measurement. In block 750, the terminal device performs an uplink transmission to the network device, the uplink transmission satisfying a fourth error requirement. The third error requirement is lower than the fourth error requirement. In some embodiments, process 700 may also include other operations performed at terminal device 502 as described in conjunction with Figure 5 in embodiments of the present disclosure.

[0110] Figure 8 illustrates a schematic flowchart 800 implemented at a network device according to some embodiments of the present disclosure. As shown in Figure 8, process 800 can be executed by a network device, such as network device 404 or a chip, module, or assembly within network device 404. In block 810, the network device receives a random access preamble from a terminal device, the transmission of which satisfies a first error requirement. In block 820, the network device receives an indication of completion of GNSS measurement from the terminal device, the transmission of which satisfies a second error requirement. The first error requirement is lower than the second error requirement. In some embodiments, process 800 may also include other operations performed at network device 404 as described in conjunction with Figure 4 in embodiments of the present disclosure.

[0111] Figure 9 illustrates a schematic flowchart 900 implemented at a network device according to some other embodiments of the present disclosure. As shown in Figure 9, the process 900 can be executed by a network device, such as network device 504 or a chip, module, or assembly within network device 504. In block 910, the network device receives a random access preamble from a terminal device, the transmission of which satisfies a third error requirement. In block 920, the network device receives an indication of completion of GNSS measurement from the terminal device. In block 930, the network device sends an acknowledgment message to the terminal device confirming the completion of the GNSS measurement. In block 940, the network device receives an uplink transmission from the terminal device, the uplink transmission satisfying a fourth error requirement. The third error requirement is lower than the fourth error requirement. In some embodiments, the process 900 may also include other operations performed at network device 504 as described in conjunction with Figure 5 in embodiments of the present disclosure.

[0112] Figure 10 is a block diagram of a device 1000 that can be used to implement some embodiments of this application. In some embodiments, device 1000 may be an element of a communication network infrastructure, such as a base station (e.g., NodeB, evolved NodeB (eNodeB or eNB), future communication system NodeB (sometimes referred to as gNodeB or gNB), Home Subscriber Server (HSS), gateway (GW), such as a packet gateway (PGW) or serving gateway (SGW), or various other nodes or functions within a core network (CN) or public land mobile network (PLMN). In other embodiments, device 1000 may be a device connected to network infrastructure via a wireless interface, such as a mobile phone, smartphone, or other such device that can be classified as user equipment (UE). In some embodiments, device 1000 may be a machine-type communication (M) device. This refers to a TC (Traffic Side Unit) device (also known as a machine-to-machine (M2M) device), or another such device that, although not providing direct service to a user, can be classified as a UE. In some embodiments, device 1000 may be a roadside unit (RSU), vehicle UE (V-UE), pedestrian UE (P-UE), or infrastructure UE (I-UE). In some scenarios, device 1000 may also be referred to as a mobile device, a term intended to reflect a device connected to a mobile network, regardless of whether the device itself is designed for or capable of being mobile. A particular device may utilize all or only a subset of the components shown, and the level of integration may vary depending on the device. Furthermore, device 1000 may contain multiple instances of components, such as multiple processors, memory, transmitters, receivers, etc.

[0113] Device 1000 typically includes a processor 1002, such as a central processing unit (CPU), and may further include a dedicated processor, such as a graphics processing unit (GPU) or other such processor, memory 1004, a network interface 1006, and a bus 1008 for connecting the components of device 1000. Optionally, device 1000 may also include components such as a mass storage device 1010, a video adapter 1012, and an I / O interface 1016 (shown in dashed lines).

[0114] Memory 1004 may include any type of non-transitory system memory readable by processor 1002, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or combinations thereof. In one embodiment, memory 1004 may include more than one type of memory, such as ROM used at startup and DRAM used for program and data storage during program execution. Bus 1008 may be one or more of a plurality of bus architectures of any type, including a memory bus or memory controller, a peripheral bus, or a video bus.

[0115] Device 1000 may also include one or more network interfaces 1006, which may include at least one of wired network interfaces and wireless network interfaces. As shown in FIG10, network interface 1006 may include a wired network interface for connecting to network 1022, and may also include a wireless access network interface 1020 for connecting to other devices via a wireless link. When device 1000 is a network infrastructure element, the wireless access network interface 1020 may be omitted for nodes or functions that are elements of a PLMN rather than elements at the wireless edge (e.g., eNB). When device 1000 is infrastructure at the wireless edge of the network, both wired and wireless network interfaces may be included. When device 1000 is a wirelessly connected device, such as a user equipment, the wireless access network interface 1020 may be present and may be supplemented by other wireless interfaces such as a WiFi network interface. Network interface 1006 allows device 1000 to communicate with remote entities such as those connected to network 1022.

[0116] Mass storage 1010 may include any type of non-transitory storage device configured to store data, programs, and other information and make the data, programs, and other information accessible via bus 1008. Mass storage 1010 may include, for example, one or more of a solid-state drive, hard disk drive, disk drive, or optical disk drive. In some embodiments, mass storage 1010 may be located remotely from device 1000 and may be accessed using a network interface such as interface 1006. In the illustrated embodiment, mass storage 1010 is distinct from the memory 1004 that includes it, and mass storage 1010 typically performs storage tasks compatible with higher latency but typically provides low or no fluctuation. In some embodiments, mass storage 1010 may be integrated with heterogeneous memory 1004.

[0117] Optional video adapter 1012 and I / O interface 1016 (shown in dashed lines) provide interfaces for coupling device 1000 to external input and output devices. Examples of input and output devices include a display 1014 coupled to video adapter 1012 and an I / O device 1018, such as a touchscreen, coupled to I / O interface 1016. Other devices may be coupled to device 1000 and may utilize additional or fewer interfaces. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide interfaces for external devices. Those skilled in the art will understand that in embodiments where device 1000 is part of a data center, I / O interface 1016 and video adapter 1012 may be virtualized and provided via network interface 1006.

[0118] Figure 11 is a schematic diagram of the structure of a device 1100 according to some embodiments of this application. As shown in Figure 11, the device 1100 includes a first transmitting unit 1102, an execution unit 1104, and a second execution unit 1106. The device 1100 can be applied to the communication systems shown in Figures 1 to 3, and can implement the methods provided in the preceding embodiments, such as method 400. Optionally, the physical manifestation of the device 1100 can be a terminal device, such as a UE. Alternatively, the device 1100 can be other devices capable of implementing the functions of a terminal device, such as a processor or chip inside the terminal device. Specifically, the device 1100 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC).

[0119] In some embodiments, the first transmitting unit 1102 may be configured to transmit a random access preamble to the network device, the transmission of which satisfies a first error requirement. The execution unit 1104 may be configured to perform Global Navigation Satellite System (GNSS) measurements. The second transmitting unit 1106 may be configured to transmit an indication of completion of GNSS measurements to the network device, the transmission of which satisfies a second error requirement. The first error requirement is lower than the second error requirement. In some other embodiments, the device 1100 may include various other units or modules that may be configured to perform various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

[0120] Figure 12 is a schematic diagram of the structure of a device 1200 according to some embodiments of this application. As shown in Figure 12, the device 1200 includes a first transmitting unit 1202, a first executing unit 1204, a second transmitting unit 1206, a receiving unit 1208, and a second executing unit 1210. The device 1200 can be applied to the communication systems shown in Figures 1 to 3, and can implement the methods provided in the foregoing embodiments, such as method 500. Optionally, the physical manifestation of the device 1200 can be a terminal device, such as a UE. Alternatively, the device 1200 can be other devices capable of implementing the functions of a terminal device, such as a processor or chip inside the terminal device. Specifically, the device 1200 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC).

[0121] In some embodiments, the first transmitting unit 1202 may be configured to transmit a random access preamble to the network device, the transmission of which satisfies a third error requirement. The first executing unit 1204 may be configured to perform Global Navigation Satellite System (GNSS) measurements. The second transmitting unit 1206 may be configured to transmit an indication of completion of GNSS measurements to the network device. The receiving unit 1208 may be configured to receive confirmation information from the network device regarding the indication of completion of GNSS measurements. The second executing unit 1210 may be configured to perform an uplink transmission to the network device, the uplink transmission satisfying a fourth error requirement. The third error requirement is lower than the fourth error requirement. In some other embodiments, the device 1200 may include various other units or modules that may be configured to perform various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

[0122] Figure 13 is a schematic diagram of the structure of a device 1300 according to some embodiments of this application. As shown in Figure 13, the device 1300 includes a first receiving unit 1302 and a second receiving unit 1304. The device 1300 can be applied to the communication systems shown in Figures 1 to 3 and can implement the methods provided in the foregoing embodiments, such as method 400. Optionally, the physical manifestation of the device 1300 can be a network device, such as a base station or ground station. Alternatively, the device 1300 can be other devices capable of implementing the functions of a network device, such as a processor or chip inside the network device. Specifically, the device 1300 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC).

[0123] In some embodiments, the first receiving unit 1302 may be configured to receive a random access preamble from the terminal device, the transmission of which satisfies a first error requirement. The second receiving unit 1304 may be configured to receive an indication of completion of GNSS measurement from the terminal device, the transmission of which satisfies a second error requirement. The first error requirement is lower than the second error requirement. In some other embodiments, the device 1300 may include various other units or modules that may be configured to perform the various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

[0124] Figure 14 is a schematic diagram of the structure of a device 1400 according to some embodiments of this application. As shown in Figure 14, the device 1400 includes a first receiving unit 1402, a second receiving unit 1404, a transmitting unit 1406, and a third receiving unit 1408. The device 1400 can be applied to the communication systems shown in Figures 1 to 3 and can implement the methods provided in the preceding embodiments, such as method 500. Optionally, the physical manifestation of the device 1400 can be a network device, such as a base station or ground station. Alternatively, the device 1400 can be other devices capable of implementing the functions of a network device, such as a processor or chip inside the network device. Specifically, the device 1400 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC).

[0125] In some embodiments, the first receiving unit 1402 may be configured to receive a random access preamble from the terminal device, the transmission of which satisfies a third error requirement. The second receiving unit 1404 may be configured to receive an indication of completion of GNSS measurement from the terminal device. The sending unit 1406 may be configured to send confirmation information to the terminal device regarding the indication of completion of GNSS measurement. The third receiving unit 1408 may be configured to receive an uplink transmission from the terminal device, the uplink transmission satisfying a fourth error requirement. The third error requirement is lower than the fourth error requirement. In some other embodiments, the apparatus 1400 may include various other units or modules that may be configured to perform the various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

[0126] It should be noted that the module division in the above embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical units, or be integrated into one unit by two or more units. The integrated units described above can be implemented in hardware or as software functional units.

[0127] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, or all or part of it, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0128] Based on the above embodiments, this application also provides a computer program that, when run on a computer, causes the computer to execute any of the methods provided in the above embodiments.

[0129] Based on the above embodiments, this application also provides a computer-readable storage medium storing a computer program. When executed by a computer, the computer program causes the computer to perform any of the methods provided in the above embodiments. The storage medium can be any available medium that can be accessed by a computer. By way of example, but not limited to, a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code having the form of instructions or data structures and that can be accessed by a computer.

[0130] Based on the above embodiments, this application also provides a chip for reading a computer program stored in a memory and implementing any of the methods provided in the above embodiments.

[0131] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the functions involved in the communication devices in the above embodiments. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete components.

[0132] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0133] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0134] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0135] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0136] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of protection of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method for a terminal device, comprising: Send a random access preamble to the network device, wherein the transmission of the random access preamble satisfies a first error requirement; Perform Global Navigation Satellite System (GNSS) measurements; as well as The network device is sent an indication that the GNSS measurement is complete, and the transmission of the indication that the GNSS measurement is complete satisfies a second error requirement, wherein the first error requirement is lower than the second error requirement.

2. The method according to claim 1, wherein, The first error requirement includes at least one of a first timing error requirement or a first frequency offset error requirement; and The second error requirement includes at least one of a second timing error requirement or a second frequency deviation error requirement.

3. The method according to claim 1 or 2, wherein, The uplink transmission, applying the first error requirement, is associated with the frequency offset error correction of the closed loop; or The uplink transmission applying the second error requirement is not associated with closed-loop frequency offset error correction.

4. The method according to any one of claims 1 to 3, wherein, Before the completion of the GNSS measurement or the transmission of the indication of completion of the GNSS measurement, the uplink transmission of the terminal device satisfies the first error requirement.

5. The method according to any one of claims 1 to 4, further comprising: Receive confirmation information from the network device regarding the completion of the GNSS measurement. Prior to receiving the confirmation information, the accumulated closed-loop timing adjustment and / or closed-loop frequency offset adjustment are cleared to zero.

6. The method according to any one of claims 1 to 5, wherein, The confirmation information includes at least one of the closed-loop timing adjustment or the closed-loop frequency offset adjustment.

7. A communication method for a terminal device, comprising: Send a random access preamble to the network device, wherein the transmission of the random access preamble satisfies a third error requirement; Perform Global Navigation Satellite System (GNSS) measurements; Send an instruction to the network device to complete the GNSS measurement; Receive confirmation information from the network device regarding the completion of the GNSS measurement; as well as Uplink transmission is performed to the network device, and the uplink transmission satisfies the fourth error requirement. The third error requirement is lower than the fourth error requirement.

8. The method according to claim 7, wherein, The third error requirement includes at least one of a third timing error requirement or a third frequency offset error requirement; and The fourth error requirement includes at least one of the fourth timing error requirement or the fourth frequency deviation error requirement.

9. The method according to claim 7 or 8, wherein, The uplink transmission, applying the third error requirement, is associated with the frequency offset error correction of the closed loop; or The uplink transmission applying the fourth error requirement is not associated with the closed-loop frequency offset error correction.

10. The method according to any one of claims 7 to 9, wherein, Before the confirmation information is received, at least one of the following must be satisfied: The cumulative closed-loop timing adjustment is the closed-loop timing adjustment; or The cumulative closed-loop frequency offset adjustment is the closed-loop frequency offset adjustment.

11. The method according to any one of claims 7 to 10, wherein, The indication of completion of the GNSS measurement is sent by at least one of the following: Physical Uplink Control Channel (PUCCH); Media Access Control Unit (MAC CE); Uplink Control Information (UCI); Random access request messages based on a non-contention-based random access procedure; or Random access request message based on a contention-based random access procedure.

12. The method according to any one of claims 7 to 11, wherein, The confirmation information includes at least one of the closed-loop time offset adjustment or the closed-loop frequency offset adjustment.

13. The method according to claim 1 or 7, further comprising: Receive configuration information about at least one semi-static resource from the network device. Sending an instruction to the network device to complete GNSS measurements includes: The indication of completion of GNSS measurement is transmitted using the first semi-static resource of the at least one semi-static resource.

14. The method according to claim 13, wherein, The first semi-static resource is determined based on the time it takes to complete the GNSS measurement.

15. A communication method for a network device, comprising: The terminal device receives a random access preamble, and the transmission of the random access preamble satisfies a first error requirement. as well as The terminal device receives an indication that the GNSS measurement is completed, and the transmission of the indication that the GNSS measurement is completed satisfies the second error requirement; The first error requirement is lower than the second error requirement.

16. The method according to claim 15, wherein, The first error requirement includes at least one of a first timing error requirement or a first frequency offset error requirement; and The second error requirement includes at least one of a second timing error requirement or a second frequency deviation error requirement.

17. The method according to claim 15 or 16, wherein, The uplink transmission, applying the first error requirement, is associated with the frequency offset error correction of the closed loop; or The uplink transmission applying the second error requirement is not associated with closed-loop frequency offset error correction.

18. The method according to any one of claims 15 to 17, wherein, Before receiving the completion of the GNSS measurement or the indication of completion of the GNSS measurement, the uplink transmission of the terminal device satisfies the first error requirement.

19. The method according to any one of claims 15 to 18, further comprising: Send a confirmation message to the terminal device indicating that the GNSS measurement has been completed.

20. The method according to any one of claims 15 to 19, wherein, The confirmation information includes at least one of the closed-loop timing adjustment or the closed-loop frequency offset adjustment.

21. A communication method for a network device, comprising: The terminal device receives a random access preamble, the transmission of which satisfies the third error requirement; Receive an instruction from the terminal device indicating that the GNSS measurement has been completed; Send a confirmation message to the terminal device indicating that the GNSS measurement has been completed; as well as The terminal device receives uplink transmissions that satisfy the fourth error requirement. The third error requirement is lower than the fourth error requirement.

22. The method according to claim 21, wherein, The third error requirement includes at least one of a third timing error requirement or a third frequency offset error requirement; and The fourth error requirement includes at least one of the fourth timing error requirement or the fourth frequency deviation error requirement.

23. The method according to claim 21 or 22, wherein, The uplink transmission, applying the third error requirement, is associated with the frequency offset error correction of the closed loop; or The uplink transmission applying the fourth error requirement is not associated with the closed-loop frequency offset error correction.

24. The method according to any one of claims 21 to 23, wherein, The indication of completion of the GNSS measurement is received by at least one of the following: Physical Uplink Control Channel (PUCCH); Media Access Control Unit (MAC CE); Uplink Control Information (UCI); Random access request messages based on a non-contention-based random access procedure; or Random access request message based on a contention-based random access procedure.

25. The method according to any one of claims 21 to 24, wherein, The confirmation information includes at least one of the closed-loop time offset adjustment or the closed-loop frequency offset adjustment.

26. The method according to claim 15 or 21, further comprising: Send configuration information about at least one semi-static resource to the terminal device. Receiving an instruction from the terminal device indicating completion of GNSS measurement includes: The instruction to complete the GNSS measurement is received using the first semi-static resource of the at least one semi-static resource.

27. The method according to claim 26, wherein, The first semi-static resource is determined based on the time it takes to complete the GNSS measurement.

28. The method according to claim 26 or 27, further comprising: In response to receiving the instruction to complete the GNSS measurement, the remaining semi-static resources in the at least one semi-static resource are released.

29. A communication device, comprising: Units for performing the method according to any one of claims 1 to 6, or claims 7 to 14, or claims 15 to 20, or claims 21 to 28.

30. A communication device, comprising: A processor for performing the method according to any one of claims 1 to 6, or claims 7 to 14, or claims 15 to 20, or claims 21 to 28.

31. A computer-readable storage medium storing instructions that, when executed, cause the method according to any one of claims 1 to 6, or claims 7 to 14, or claims 15 to 20, or claims 21 to 28 to be performed.

32. A computer program product comprising instructions that, when executed, cause the method according to any one of claims 1 to 6, or claims 7 to 14, or claims 15 to 20, or claims 21 to 28 to be performed.