Satellite communication method and apparatus

Abstract

The application discloses a satellite communication method and device. The method can be applied to an NTN, such as a satellite communication field. The method comprises the following steps: determining a first effective time length of GNSS of a first communication device; a second communication device sends a TAC in the first effective time length of GNSS; and in the case that the first communication device receives the TAC from the second communication device in the first effective time length of GNSS, the first communication device determines a second effective time length of GNSS based on an effective time length of the TAC and the first effective time length of GNSS. The method can effectively improve the communication time length of a terminal device.

Description

[0001] This application is a divisional application. The original application has the application number 202310361968.6 and the original application date is March 30, 2023. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a satellite communication method and apparatus. Background Technology

[0003] Satellite communication offers unique advantages over terrestrial communication, such as wider coverage and the reduced vulnerability of satellite base stations to natural disasters or external damage. Future communication technologies incorporating satellite can provide services to areas inaccessible to terrestrial networks, such as oceans and forests; enhance communication reliability, ensuring higher-quality communication for users on airplanes, trains, and other modes of transportation; and provide more data transmission resources, increasing network speeds. Therefore, supporting both terrestrial and satellite communication is an inevitable trend for future communication, offering significant benefits in terms of wider coverage, reliability, connectivity, and high throughput.

[0004] Satellite communication has been incorporated into the 3rd Generation Partnership Project (3GPP) standard as a communication scenario for 5th generation (5G) communication, known as non-terrestrial network (NTN). NTN supports not only various 5G terminals but also Internet of Things (IoT) terminals. The key characteristics of satellite communication are high mobility and high latency. Therefore, unlike terrestrial communication, terminals require synchronization based on Global Navigation Satellite System (GNSS) or ephemeris information in addition to uplink synchronization. After reporting GNSS information, the terminal can maintain a connection for a certain effective duration; if GNSS fails, the terminal enters an idle state.

[0005] However, the above method causes the terminal to continuously initiate random access to enter and exit the connection state, making it impossible for the terminal to communicate continuously for a long time. Summary of the Invention

[0006] This application provides a satellite communication method and apparatus that can effectively improve the communication duration of terminal devices.

[0007] In a first aspect, embodiments of this application provide a satellite communication method. The method is applied to a first communication device, which may be a terminal device, a chip in the terminal device, or a functional module in the terminal device. The method includes: determining a first effective duration of Global Navigation Satellite System (GNSS) for the first communication device; receiving a time advance command (TAC) from a second communication device within the first effective duration of GNSS; and determining a second effective duration of GNSS, wherein the second effective duration of GNSS is determined based on the first effective duration of GNSS and the effective duration of the TAC, and the second effective duration of GNSS is longer than the first effective duration of GNSS.

[0008] In this embodiment, the terminal device can achieve uplink synchronization based on GNSS information and TAC. Therefore, by extending the effective duration of GNSS information (i.e., the second effective duration of GNSS is longer than the first effective duration of GNSS), the communication duration of the terminal device (or the duration of the terminal device in the connected state) can be effectively increased, enabling the terminal device to achieve long-term communication. Compared to the scheme where the terminal device enters the idle state after GNSS information expires (i.e., without delaying the effective duration of GNSS information), and then initiates random access again to enter the connected state and exit the connected state again (e.g., GNSS information expires), this embodiment can also effectively avoid the signaling overhead caused by the terminal device constantly entering and exiting the connected state, reducing signaling overhead and power consumption of the terminal device.

[0009] In conjunction with the first aspect, in one possible implementation, the method further includes:

[0010] If no information for triggering GNSS measurement is received from the second communication device within the second valid duration, the device enters an idle state; or, if no information for triggering GNSS measurement is received from the second communication device within the second valid duration, a timer is started, and if the GNSS measurement is completed within the timer's duration, communication with the second communication device continues, wherein the start time of the timer is the end time of the second valid GNSS duration.

[0011] In this embodiment of the application, when the second valid duration of GNSS ends and no information for triggering GNSS measurement is received, the terminal device can also start a timer to perform GNSS measurement on its own. If the GNSS measurement is completed within the timer's duration, the terminal device can continue to maintain the connection state, thus further reducing the number of times the terminal device disconnects and further increasing the communication duration between the terminal device and the network device.

[0012] Secondly, embodiments of this application provide a satellite communication method, the method being applied to a second communication device, the second communication device being a network device or a chip or functional module in the network device, the method comprising: determining a first effective duration of the Global Navigation Satellite System (GNSS) of a first communication device; sending a timing advance command (TAC) to the first communication device within the first effective duration of the GNSS; and determining a second effective duration of the GNSS, the second effective duration of the GNSS being determined based on the first effective duration of the GNSS and the effective duration of the TAC, wherein the second effective duration of the GNSS is longer than the first effective duration of the GNSS.

[0013] In conjunction with the first or second aspect, in one possible implementation, the end time of the effective duration of the TAC is later than the end time of the first effective duration of the GNSS.

[0014] In this embodiment, the end time of the TAC is after the end time of the first valid GNSS duration, thus extending the first valid GNSS duration. This not only effectively increases the communication time of the terminal device, but also allows the terminal device to adjust its uplink timing in advance based on the TAC, resulting in more accurate uplink synchronization within the valid duration of the TAC. This approach balances both the communication duration and the accuracy of uplink synchronization for the terminal device.

[0015] In conjunction with the first or second aspect, in one possible implementation, the first effective duration of GNSS is the initial effective duration of GNSS, or the first effective duration of GNSS is an effective duration updated based on the second effective duration of GNSS.

[0016] In conjunction with the first or second aspect, in one possible implementation, when the first valid GNSS duration is an effective duration updated based on the second valid GNSS duration, the difference between the second valid GNSS duration and the first valid GNSS duration is determined based on the effective duration of one TAC, and the method further includes: updating the second valid GNSS duration to a new first valid GNSS duration.

[0017] In conjunction with the first or second aspect, in one possible implementation, the difference between the second effective duration of GNSS and the initial effective duration of GNSS is determined based on the effective duration of N TACs, where N is a positive integer.

[0018] In conjunction with the first or second aspect, in one possible implementation, the determination of the difference between the second effective duration of GNSS and the initial effective duration of GNSS based on the effective duration of N TACs includes: the difference between the second effective duration of GNSS and the initial effective duration of GNSS is determined based on the effective duration of N TACs and the maximum extension duration.

[0019] In conjunction with the first or second aspect, in one possible implementation, the determination of the difference between the second effective duration of GNSS and the initial effective duration of GNSS based on the effective duration of N TACs includes: the difference between the second effective duration of GNSS and the initial effective duration of GNSS is determined based on the effective duration of N TACs and the maximum number of TACs.

[0020] In conjunction with the first or second aspect, in one possible implementation, the difference between the second effective duration of GNSS and the initial effective duration of GNSS, determined based on the effective duration of N TACs, includes: the difference between the second effective duration of GNSS and the initial effective duration of GNSS being less than the effective duration of N TACs; or, the difference between the second effective duration of GNSS and the initial effective duration of GNSS being equal to the effective duration of N TACs.

[0021] Thirdly, embodiments of this application provide a first communication device for executing the method in the first aspect or any possible implementation thereof. The first communication device includes units for executing the method in the first aspect or any possible implementation thereof.

[0022] For example, the first communication device may be a terminal device or a chip, and the chip may be used in terminal devices, etc.

[0023] Fourthly, embodiments of this application provide a second communication device for executing the method in the second aspect or any possible implementation thereof. The second communication device includes units for executing the method in the second aspect or any possible implementation thereof.

[0024] For example, the second communication device can be a network device or a chip, which can be applied to network devices, etc.

[0025] Fifthly, embodiments of this application provide a first communication device, which includes a processor for executing the method described in the first aspect or any possible implementation thereof. Alternatively, the processor is configured to execute a program stored in a memory, wherein when the program is executed, the method described in the first aspect or any possible implementation thereof is executed.

[0026] In one possible implementation, the memory is located outside the aforementioned first communication device.

[0027] In one possible implementation, the memory is located within the aforementioned first communication device.

[0028] In this embodiment, the processor and memory can also be integrated into a single device, that is, the processor and memory can be integrated together. For example, the first communication device can be a chip.

[0029] In one possible implementation, the first communication device further includes a transceiver for receiving or transmitting signals. Exemplarily, the transceiver may also be used to receive TAC (Trigger Information) or information for triggering GNSS measurements (which may be simply referred to as trigger information). Exemplarily, the transceiver may also be used to transmit information such as the initial effective duration of GNSS. Exemplarily, the first communication device may be a terminal device.

[0030] Sixthly, embodiments of this application provide a second communication device, which includes a processor for executing the method shown in the second aspect or any possible implementation thereof. Alternatively, the processor is configured to execute a program stored in a memory, wherein when the program is executed, the method shown in the second aspect or any possible implementation thereof is executed.

[0031] In one possible implementation, the memory is located outside the aforementioned second communication device.

[0032] In one possible implementation, the memory is located within the aforementioned second communication device.

[0033] In this embodiment, the processor and memory can be integrated into a single device, i.e., the processor and memory can be integrated together. For example, the second communication device can be a chip. For example, the memory can be used to store the initial effective duration of GNSS, the maximum number of GNSS devices, or the maximum extended duration, etc.

[0034] In one possible implementation, the second communication device further includes a transceiver for receiving or transmitting signals. For example, the transceiver may be used to transmit TAC or trigger information. For example, the transceiver may also be used to receive information such as the initial effective duration of GNSS. For example, the second communication device may be a network device.

[0035] In a seventh aspect, embodiments of this application provide a first communication device, which includes a logic circuit and an interface, wherein the logic circuit and the interface are coupled; the interface is used to input and / or output information, and the logic circuit is used to perform the method described in the first aspect or any possible implementation thereof. The interface for inputting information may include: the interface for inputting TAC or trigger information, and the interface for outputting information may include: the interface for outputting information such as the initial effective duration of GNSS.

[0036] For example, the logic circuit is used to determine a first valid GNSS duration; and to determine a second valid GNSS duration based on the TAC input from the interface and the first valid GNSS duration.

[0037] For example, the logic circuit is also configured to update the second valid GNSS duration to a new first valid GNSS duration.

[0038] For example, the logic circuit is also configured to control the terminal device to enter an idle state if no trigger information is received within the second valid GNSS duration; or to start a timer and, if the GNSS measurement is completed within the timer's duration, continue to communicate with the second communication device through the interface.

[0039] Eighthly, embodiments of this application provide a second communication device, which includes logic circuitry and an interface coupled together. The interface is used for inputting and / or outputting information, and the logic circuitry is used to perform the method described in the second aspect or any possible implementation thereof. The interface is used for inputting information including: inputting information about the initial effective duration of GNSS; and the interface is used for outputting information including: outputting TAC or trigger information.

[0040] For example, the logic circuit is used to determine a first valid GNSS duration; and to determine a second valid GNSS duration based on the TAC output by the interface and the first valid GNSS duration.

[0041] For example, the logic circuit is also configured to update the second valid GNSS duration to a new first valid GNSS duration.

[0042] Ninthly, embodiments of this application provide a computer-readable storage medium for storing a computer program that, when run on a computer, causes the methods shown in the first aspect or any possible implementation thereof to be executed.

[0043] In a tenth aspect, embodiments of this application provide a computer-readable storage medium for storing a computer program that, when run on a computer, causes the methods shown in the second aspect or any possible implementation thereof to be executed.

[0044] Eleventhly, embodiments of this application provide a computer program product, which includes a computer program or computer code, and when run on a computer, causes the method shown in the first aspect or any possible implementation thereof to be executed.

[0045] In a twelfth aspect, embodiments of this application provide a computer program product comprising a computer program or computer code that, when run on a computer, causes the methods shown in the second aspect or any possible implementation thereof to be executed.

[0046] In a thirteenth aspect, embodiments of this application provide a computer program that, when run on a computer, executes the methods shown in the first aspect or any possible implementation thereof.

[0047] In a fourteenth aspect, embodiments of this application provide a computer program that, when run on a computer, executes the methods shown in the second aspect or any possible implementation thereof.

[0048] In a fifteenth aspect, embodiments of this application provide a communication system comprising a first communication device and a second communication device, wherein the first communication device is configured to perform the method shown in the first aspect or any possible implementation thereof, and the second communication device is configured to perform the method shown in the second aspect or any possible implementation thereof. Attached Figure Description

[0049] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0050] Figure 2a This is a schematic diagram of a satellite communication system in a transparent transmission scenario provided in an embodiment of this application;

[0051] Figure 2b This is a schematic diagram of a satellite communication system in a regeneration scenario provided in an embodiment of this application;

[0052] Figure 2c This is a schematic diagram of a satellite communication system in a regeneration scenario provided in an embodiment of this application;

[0053] Figure 3 This is a flowchart illustrating a satellite communication method provided in an embodiment of this application;

[0054] Figure 4a This is a schematic diagram of a satellite communication method provided in an embodiment of this application;

[0055] Figure 4b This is a schematic diagram of a satellite communication method provided in an embodiment of this application;

[0056] Figure 5a This is a schematic diagram illustrating the relationship between the first effective duration and the second effective duration of GNSS provided in an embodiment of this application;

[0057] Figure 5b This is a schematic diagram illustrating the relationship between the first effective duration and the second effective duration of GNSS provided in an embodiment of this application;

[0058] Figure 5c This is a schematic diagram illustrating the relationship between the first effective duration and the second effective duration of GNSS provided in an embodiment of this application;

[0059] Figure 6a This is a schematic diagram illustrating the relationship between the initial effective duration and the second effective duration of GNSS provided in an embodiment of this application;

[0060] Figure 6b This is a schematic diagram illustrating the relationship between the initial effective duration and the second effective duration of GNSS provided in an embodiment of this application;

[0061] Figure 6c This is a schematic diagram illustrating the relationship between the initial effective duration and the second effective duration of GNSS provided in an embodiment of this application;

[0062] Figure 6d This is a schematic diagram illustrating the relationship between the initial effective duration and the second effective duration of GNSS provided in an embodiment of this application;

[0063] Figure 7a This is a schematic diagram illustrating the relationship between the initial effective duration and the second effective duration of GNSS provided in an embodiment of this application;

[0064] Figure 7b This is a schematic diagram illustrating the relationship between the initial effective duration and the second effective duration of GNSS provided in an embodiment of this application;

[0065] Figure 7c This is a schematic diagram illustrating the relationship between the initial effective duration and the second effective duration of GNSS provided in an embodiment of this application;

[0066] Figure 7d This is a schematic diagram illustrating the relationship between the initial effective duration and the second effective duration of GNSS provided in an embodiment of this application;

[0067] Figure 8a This is a flowchart illustrating a satellite communication method provided in an embodiment of this application;

[0068] Figure 8b This is a schematic diagram illustrating the relationship between the initial effective duration and the second effective duration of GNSS provided in an embodiment of this application;

[0069] Figure 9 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0070] Figure 10 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0071] Figure 11 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0072] To facilitate understanding of the technical solution of this application, the application will be further described below with reference to the accompanying drawings.

[0073] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are used only to distinguish different objects and not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0074] The term "embodiment" as used herein means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0075] In this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three or more, and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. "Or" indicates that there can be two relationships, such as only A exists or only B exists; when A and B are not mutually exclusive, it can also mean that there are three relationships, such as only A exists, only B exists, or both A and B exist simultaneously. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c".

[0076] The method provided in this application can be applied to non-terrestrial networks (NTN) communication systems, such as... Figure 1 As shown, this communication system may include terminal equipment, satellites, and ground stations (also known as gateway stations or signaling stations). It is understood that... Figure 1 Only one satellite and one ground station are shown. In actual use, a multi-satellite and / or multi-ground-station architecture can be adopted as needed. Each satellite can provide services to one or more terminal devices, each satellite can correspond to one or more ground stations, and each ground station can correspond to one or more satellites, etc. The embodiments in this application do not provide specific limitations.

[0077] A terminal device is a device with wireless transceiver capabilities. It can communicate with access network equipment (or access devices) in a radio access network (RAN). Terminal devices can also be referred to as user equipment (UE), access terminal, terminal, subscriber unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent, or user device, etc. In one possible implementation, the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as on a ship). In one possible implementation, the terminal device can be a handheld device with wireless communication capabilities, a vehicle-mounted device, a wearable device, a sensor, a terminal in the Internet of Things (IoT), a terminal in the Internet of Vehicles (IoV), a drone, a 5G network, or any form of terminal device in future networks, etc., and this application embodiment does not limit this. For example, terminal devices can also communicate with each other through device-to-device (D2D) and machine-to-machine (M2M) communication. The terminal device shown in the embodiments of this application can also be a device in the Internet of Things (IoT). This IoT network may include, for example, a vehicle-to-everything (V2X) network. The communication methods in the V2X system are collectively referred to as vehicle-to-other-device (V2X), where X can represent anything. For example, V2X may include: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, or vehicle-to-network (V2N) communication, etc.

[0078] Ground stations can be used to connect satellites to base stations or satellites to the core network. The satellite can provide wireless access services to terminal devices, allocate wireless resources to accessing terminal devices, and provide reliable wireless transmission protocols and data encryption protocols. As an example, a satellite can act as a base station for wireless communication, using artificial Earth satellites and high-altitude aircraft, such as evolved NodeBs (eNBs) and next-generation node Bs (gNBs). As another example, a satellite can also act as a relay for these base stations, transmitting their signals to terminal devices.

[0079] Therefore, in some implementations of this application, such as in a satellite transparent transmission scenario, the network device can provide... Figure 1 The base station shown is also called a ground base station. Figure 2a This is a schematic diagram of a satellite communication system in a transparent transmission scenario provided by an embodiment of this application. Exemplarily, terminal devices can access the network via an air interface (which can be various types of air interfaces, such as 5G air interfaces), and network equipment can be deployed on a ground base station. The satellite is connected to the ground station via a wireless link. The ground station and the ground base station are connected to the core network via wired or wireless connections. Wireless links can exist between satellites. Figure 2a In the system shown, the satellite can have transparent transmission and forwarding capabilities. In other implementations of this application, such as in satellite regeneration scenarios, the network device can... Figure 1 The satellite shown. Figure 2b This is a schematic diagram of a satellite communication system in a regeneration scenario provided by an embodiment of this application. For example, terminal devices can access the network via an air interface (which can be various types of air interfaces, such as a 5G air interface), and network equipment can be deployed on satellites (e.g., in satellite regeneration mode), such as base stations or some base station functions being deployed on satellites. Satellites can complete signaling interaction and user data transmission between base stations, such as... Figure 2c As shown.

[0080] For example, Figures 2a to 2c The various network elements and their interfaces can be seen as follows:

[0081] Terminal devices can access the satellite network via the air interface and initiate calls, access the internet, and perform other services. Base stations can provide wireless access services, allocate wireless resources to accessing terminal devices, and provide reliable wireless transmission protocols and data encryption protocols. Ground stations can be responsible for forwarding signaling and service data between the satellite and the core network. The core network can be used for user access control, mobility management, session management, user security authentication, and billing. The core network can consist of multiple functional units, such as functional entities including control plane and data plane components. For example... Figures 2a to 2c The core network shown may include access and mobility management functions (AMF), session management functions (SMF), and user plane functions (UPF). For example, AMF can be used to manage user access, security authentication, and mobility management. UPF can be used to manage user plane data transmission and traffic statistics. Figures 2a to 2c The air interface shown can be understood as the wireless link between the terminal and the base station, or the wireless link between the satellite and the ground station; the Xn interface can be understood as the interface between base stations, mainly used for signaling interaction such as handover; the NG interface can be used as the interface between the base station and the core network, used for exchanging non-access stratum (NAS) signaling of the core network, as well as user service data. In systems with different wireless access technologies, the names of devices with base station functions may vary, and they will not be shown one by one in the embodiments of this application.

[0082] The satellite can be a geostationary Earth orbit (GEO) satellite, a non-geostationary Earth orbit (NGEO) medium Earth orbit (MEO) satellite, or a low Earth orbit (LEO) satellite, or a high altitude platform station (HAPS), etc. This application does not limit the specific type of satellite.

[0083] In some network device deployments, the network device may include a centralized unit (CU) and a distributed unit (DU). In other network device deployments, the CU may be divided into a CU-control plane (CP) and a CU-user plane (UP). In still other network device deployments, the network device may be an open radio access network (ORAN) architecture, etc. This application embodiment does not limit the specific deployment method of the network device. For example, when the network device is an ORAN architecture, the network device shown in this application embodiment may be an access network device in ORAN, or a module in an access network device, etc. In an ORAN system, CU may also be called open (O)-CU, DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. The network device deployment methods listed here are only examples; as standard technologies evolve, network devices may have other deployment forms.

[0084] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions and network architectures provided in the embodiments of this application are also applicable to similar technical problems.

[0085] Currently, there is a short-term connection communication method. In this method, the terminal device initiates random access, sends uplink data, and then exits the connected state. During this process, the GNSS information acquired by the terminal device before the random access remains valid. That is, the GNSS information remains valid until the terminal device exits the RRC connected state. Even if the terminal device moves, the GNSS deviation caused by the movement can still meet the synchronization requirements. For IoT terminal devices, due to the short-packet periodic transmission characteristics of IoT services, the above-mentioned short-term connection communication method is effectively applicable to terminal devices with short-packet periodic transmission characteristics.

[0086] However, the GNSS information obtained by the terminal device in the above method has a limited validity period. When the GNSS information expires, the terminal device cannot maintain the connection and needs to exit the connected state and enter the idle state. Multiple random accesses by the terminal device to enter and exit the connected state can lead to excessive signaling overhead. Alternatively, if the terminal device remains in the connected state for an extended period, the GNSS information may expire, requiring the terminal device to reacquire the GNSS information. However, when the terminal device reacquires GNSS information, communication and GNSS measurement cannot be performed simultaneously; for example, the terminal device may be unable to communicate while performing GNSS measurements.

[0087] For example, the aforementioned effective duration can be determined by the terminal device based on its movement speed, its relative position to the satellite (e.g., whether it is in the central or peripheral area of ​​the satellite coverage), or its relative speed to the satellite, and then reported by the terminal device to the network device. However, when determining the effective duration, the terminal device generally uses a conservative approach, resulting in an insufficient effective duration to support long-term continuous communication. Alternatively, the terminal device may determine the effective duration based on its movement speed without considering the required communication duration, which would also result in an effective duration shorter than the actual communication duration, insufficient to support long-term continuous communication.

[0088] In view of this, the embodiments of this application provide a satellite communication method and apparatus, which can increase the communication duration of the terminal device (or increase the duration of the terminal device in the connected state) on the basis of the terminal device achieving uplink synchronization, so that the terminal device can achieve long-term communication, and can also avoid the signaling overhead caused by the terminal device constantly entering and leaving the connected state, thereby reducing signaling overhead.

[0089] The satellite communication methods shown below (such as...) Figure 3 In this context, the first communication device can be a terminal device, a chip embedded in the terminal device, or a functional module within the terminal device. The second communication device can be a network device, a chip embedded in the network device, or a functional module within the network device. As shown above, the network device can include access network devices or modules under the O-RAN architecture. For detailed descriptions of the terminal device and network device, please refer to [reference needed]. Figure 1 , Figures 2a to 2c Details will not be elaborated here. For ease of description, specific examples may be used in the following description, such as terminal devices and network devices, but these should not be construed as limiting the embodiments of this application.

[0090] Figure 3 This is a flowchart illustrating a satellite communication method provided in an embodiment of this application, as shown below. Figure 3 As shown, the method includes:

[0091] 301. The first communication device determines the first effective duration of GNSS of the first communication device, and the second communication device determines the first effective duration of GNSS of the first communication device.

[0092] Both the first and second valid GNSS durations can represent the effective duration of GNSS information from a first communication device, such as the effective duration of the same GNSS information obtained by the first communication device performing the same GNSS measurement. However, the second valid GNSS duration is longer than the first valid GNSS duration. For example, the second valid GNSS duration can be an extension based on the first valid GNSS duration, or the start time of the second valid GNSS duration can be equal to the start time of the first valid GNSS duration. In specific implementations, the protocol may not distinguish the names of the valid durations of GNSS information; for example, the first and second valid GNSS durations can be collectively referred to as the GNSS effective duration or GNSS validity period. For instance, GNSS measurement is the process of obtaining geographic location information by positioning based on navigation satellite signals. GNSS information can represent information related to the geographic location of the terminal device, such as coordinates X, Y, Z, or longitude, latitude, and altitude.

[0093] There are two interpretations regarding the first effective duration of GNSS:

[0094] A. The first effective duration of GNSS is the initial effective duration of GNSS.

[0095] The initial valid GNSS duration can be understood as: the valid GNSS duration reported by the terminal device to the network device, or the valid GNSS duration determined by the terminal device based on its speed and other information, or the valid duration not extended based on TAC. For example, Figure 3 The method may further include: the terminal device sending information carrying the initial effective duration of GNSS, and correspondingly, the network device receiving the information. For example, the initial effective duration of GNSS determined by the terminal device based on its speed and other information may be on the order of hundreds of seconds, minutes, or hours; this embodiment does not limit this. For instance, the greater the speed of the terminal device, the smaller the initial effective duration of GNSS may be; that is, the initial effective duration of GNSS may decrease as the speed of the terminal device increases.

[0096] B. The first valid duration of GNSS is the valid duration updated based on the second valid duration of GNSS.

[0097] The second valid GNSS duration shown here (e.g., GNSS second valid duration #1) differs from the second valid GNSS duration in step 303 below (e.g., GNSS second valid duration #2). GNSS second valid duration #1 is shorter than GNSS second valid duration #2. However, the method for determining GNSS second valid duration #1 is the same as the method for determining GNSS second valid duration #2. For example, GNSS second valid duration #1 may be an effective duration determined based on the effective duration of TAC before determining the first valid GNSS duration, while GNSS second valid duration #2 is an effective duration determined based on the effective duration of TAC after determining the first valid GNSS duration. Alternatively, GNSS second valid duration #1 may be an effective duration determined based on the initial valid GNSS duration and the effective duration of TAC, while GNSS second valid duration #2 may be an effective duration determined based on GNSS second valid duration #1 and the effective duration of TAC. For example, a terminal device (or network device) can update the second valid GNSS duration #1 to the first valid GNSS duration shown in step 301, and the terminal device (or network device) can update the second valid GNSS duration #2 to the new first valid GNSS duration. That is, when the first valid GNSS duration is an effective duration updated based on the second valid GNSS duration, the first communication device and the second communication device can also perform the step of updating the second valid GNSS duration to the new first valid GNSS duration.

[0098] Given the two descriptions of the first effective duration of GNSS above, the first communication device may determine its first effective duration of GNSS in the following ways: Method 1: The first communication device determines the initial effective duration of GNSS based on information such as its speed. Method 2: The first communication device determines the first effective duration of GNSS based on the initial effective duration of GNSS and the effective duration of TAC (Transmission Control Account). For example, the first communication device may extend the initial effective duration of GNSS based on the initial effective duration of GNSS and the effective duration of TAC. Method 1 corresponds to description A above, and Method 2 corresponds to description B above. The second communication device may determine the first effective duration of GNSS in the following ways: Method 3: The second communication device receives information indicating the initial effective duration of GNSS reported by the first communication device and obtains the initial effective duration of GNSS indicated by the information. Method 4: The second communication device determines the first effective duration of GNSS based on the initial effective duration of GNSS and the effective duration of TAC (Transmission Control Account). For example, the first communication device may extend the initial effective duration of GNSS based on the initial effective duration of GNSS and the effective duration of TAC (Transmission Control Account). Method 3 corresponds to Explanation A above, Method 4 corresponds to Explanation B above, and Method 3 corresponds to Method 1, and Method 4 corresponds to Method 2.

[0099] 302. The second communication device transmits a TAC within the first valid duration of GNSS, and correspondingly, the first communication device receives the TAC within the first valid duration of GNSS.

[0100] Generally, network devices can detect the uplink timing error of terminal devices based on the uplink signals sent by the terminal devices, and instruct the terminal devices to make timing advance adjustments through closed-loop timing offset. Terminal devices can ensure uplink synchronization through uplink timing advance adjustments, which can be calculated based on the location of the terminal devices and the network devices. Furthermore, terminal devices can also make fine adjustments based on the closed-loop timing offset indicated by the network devices.

[0101] For example, if the uplink timing error detected by the network device is less than or equal to a certain threshold, the network device can send a TAC to the terminal device so that the terminal device can determine the second valid duration of GNSS based on the valid duration of the TAC. That is, the terminal device can extend the valid duration of GNSS based on the valid duration of the TAC.

[0102] 303. The first communication device determines the second valid duration of GNSS, and the second communication device determines the second valid duration of GNSS. The second valid duration of GNSS is determined based on the first valid duration of GNSS and the valid duration of TAC, and the second valid duration of GNSS is longer than the first valid duration of GNSS.

[0103] If the first communication device receives a TAC within the first valid GNSS duration, it can determine the second valid GNSS duration based on the first valid GNSS duration and the valid duration of the TAC. If the uplink timing error detected by the second communication device is less than or equal to a certain threshold, it can transmit the TAC within the first valid GNSS duration and determine the second valid GNSS duration based on the first valid GNSS duration and the valid duration of the TAC. For example, the second communication device can first transmit the TAC within the first valid GNSS duration and then determine the second valid GNSS duration; or, the second communication device can first determine the second valid GNSS duration and then transmit the TAC within the first valid GNSS duration.

[0104] Typically, the timing advance adjustment indicated by the network device has a certain effective duration. When the terminal device receives a TAC within its reported GNSS effective duration, it can be assumed that a portion of the terminal device's position error (or uplink timing error) has been corrected by the TAC, and the actual GNSS effective duration may be longer than the initial GNSS effective duration reported by the terminal device. Therefore, by extending the GNSS effective duration, not only can the uplink synchronization of the terminal device be guaranteed, but also the terminal device can communicate with the network device for a longer period of time. If the terminal device receives a TAC within the first GNSS effective duration, it can extend the GNSS effective duration to obtain a second GNSS effective duration. Alternatively, if the network device requires the terminal device to extend the GNSS effective duration, it can send a TAC within the first GNSS effective duration. The order in which the first communication device determines the second GNSS effective duration and the second communication device determine the second GNSS effective duration is not limited in the embodiments of this application.

[0105] For example, the validity duration of the TAC can be configured by the network device via RRC signaling, or by the network device via Media Access Control-Control Element (MAC-CE) signaling. Before step 303, the network device sends RRC signaling carrying the validity duration of the TAC, or MAC-CE signaling carrying the validity duration of the TAC, and the terminal device receives the corresponding RRC signaling or MAC-CE signaling. For example, the validity duration of the TAC may be a value between 500ms and 1024ms, such as 500ms, 750ms, 1200ms, 1920ms, 2560ms, 5120ms, 10240ms, etc., which will not be listed here. Of course, the validity durations of the TAC listed here are merely examples and should not be construed as limiting the embodiments of this application.

[0106] In this embodiment of the application, based on the implementation of uplink synchronization by the terminal device, the communication duration of the terminal device can be increased (or the duration of the terminal device in the connected state can be increased), enabling the terminal device to achieve long-term communication. It can also avoid the signaling overhead caused by the terminal device constantly entering and exiting the connected state, thereby reducing signaling overhead and reducing the power consumption of the terminal device.

[0107] based on Figure 3 The method shown in this application provides two scenarios. Figure 4a and Figure 4b These are schematic diagrams illustrating a satellite communication method provided in the embodiments of this application.

[0108] like Figure 4aAs shown, the first communication device reports information carrying the initial valid duration of GNSS, and the second communication device receives this information. Then, the second communication device sequentially sends TAC#1, TAC#2, and TAC#3, and correspondingly, the first communication device sequentially receives TAC#1, TAC#2, and TAC#3. For example, the second communication device can send TAC#1 within the initial valid duration of GNSS, or TAC#2 within the valid duration of TAC#1, or TAC#3 within the valid duration of TAC#2. Similarly, the first communication device can receive TAC#1 within the initial valid duration of GNSS, or TAC#2 within the valid duration of TAC#1, or TAC#3 within the valid duration of TAC#2. Both the first and second communication devices can determine the second valid duration of GNSS based on the initial valid duration of GNSS, the number of TACs (e.g., N=3), and the valid duration of the TACs.

[0109] like Figure 4b As shown, the first communication device reports information carrying the initial effective duration of GNSS, and the second communication device receives this information. Then, the second communication device transmits TAC#1 within the initial effective duration of GNSS, and correspondingly, the first communication device receives TAC#1 within the same initial effective duration. Both the first and second communication devices can determine the second effective duration of GNSS #1 based on the initial effective duration of GNSS and the effective duration of TAC, and update the second effective duration of GNSS #1 to a new first effective duration of GNSS #1. The second communication device transmits TAC#2 within the new first effective duration of GNSS #1, and correspondingly, the first communication device receives TAC#2 within the same new first effective duration of GNSS #1. Both the first and second communication devices can determine the second effective duration of GNSS #2 based on the new first effective duration of GNSS #1 and the effective duration of TAC, and update the second effective duration of GNSS #2 to a new first effective duration of GNSS #2. Details regarding TAC#2 and the second effective duration of GNSS #3 are not provided here.

[0110] When the first valid duration of GNSS is an updated valid duration based on the second valid duration of GNSS, such as for Figure 4b In general, the relationship between the first effective duration of GNSS and the second effective duration of GNSS can be summarized as follows:

[0111] In the first method, the end time of the second valid GNSS duration can be the end time of the valid TAC duration. For example, the end time of the TAC can be after the end time of the first valid GNSS duration. Figure 5aAs shown, the end time of the second effective duration of GNSS can be the end time of T0. Figures 5a to 5c T0 in the text represents the effective duration of the TAC, which will not be elaborated further below. In this case, if the end time of the TAC is earlier than or equal to the end time of the first effective duration of the GNSS, the first effective duration of the GNSS may not be extended.

[0112] based on Figure 5a The relationship between the first and second valid GNSS durations shown illustrates that the second valid GNSS duration can be understood as follows: If the terminal device receives one or more TACs within the valid GNSS duration, and the end time of the last TAC's valid duration is earlier than or equal to the end time of the initial valid GNSS duration, then the end time of the initial valid GNSS duration is taken as the end time of the second valid GNSS duration. If the end time of the last TAC's valid duration is later than the end time of the initial valid GNSS duration, then the end time of the second valid GNSS duration can be extended according to the number of TACs.

[0113] In this embodiment, the end time of the TAC is after the end time of the first valid GNSS duration, thus extending the first valid GNSS duration. This not only effectively increases the communication time of the terminal device, but also allows the terminal device to adjust its uplink timing in advance based on the TAC, resulting in more accurate uplink synchronization within the valid duration of the TAC. This approach balances both the communication duration and the accuracy of uplink synchronization for the terminal device.

[0114] The second method involves determining the end time of the second valid GNSS duration based on the end time of the first valid GNSS duration and the valid duration of the TAC. For example, if the end time of the TAC is after the end time of the first valid GNSS duration, then... Figure 5b As shown, the second valid GNSS duration can be equal to the sum of the first valid GNSS duration and T0. In this case, as long as the terminal device receives TAC within the first valid GNSS duration, the first valid GNSS duration can be extended to T0.

[0115] In this embodiment, the end time of the second valid GNSS duration is determined based on the end time of the first valid GNSS duration and the valid duration of TAC, which can further improve the communication duration of the terminal device.

[0116] The third method involves determining the end time of the second valid GNSS duration based on the end time of the TAC's valid duration and the TAC's valid duration itself. For example, if the end time of the TAC is after the end time of the first valid GNSS duration, then... Figure 5cAs shown, the second effective duration of GNSS is greater than the sum of the first effective duration of GNSS and T0. That is, the end time of the second effective duration of GNSS can be the time obtained after T0 following the effective duration of TAC.

[0117] Figures 5a to 5c The relationship between the first and second effective GNSS durations shown can be similarly applied to the relationship between the second and initial effective GNSS durations. For ease of description, the following text will use... Figure 5a and Figure 5b The relationship shown below illustrates the relationship between the second valid GNSS duration and the initial valid GNSS duration. N in the following text is a positive integer, and its value is configured by the second communication device or defined by the protocol. Examples include N=1, N=2, or N=3, etc. The possible values ​​of N will not be listed individually. Figure 4a and Figure 4b For example, N=3.

[0118] The relationship between the second effective duration of GNSS and the initial effective duration of GNSS can be summarized as follows:

[0119] The fourth method involves determining the difference between the second valid GNSS duration and the initial valid GNSS duration based on the valid duration of N TACs. This difference can be less than or equal to the valid duration of N TACs. N can be understood as the number of TACs actually transmitted by the network device.

[0120] like Figure 6a As shown, the difference between the end time of the second valid GNSS duration and the start time of the first valid TAC is equal to the valid duration of N TACs, and the start time of the valid TAC is within the initial valid GNSS duration. That is, the difference between the second valid GNSS duration and the initial valid GNSS duration is less than the valid duration of N TACs. For example, if a terminal device receives another TAC within the valid duration of one TAC, that TAC still has a certain valid duration, and therefore the valid GNSS duration can be further postponed until the end of the valid duration of the next TAC. Figure 7a As shown, the difference between the second effective duration of GNSS and the initial effective duration of GNSS is equal to the effective duration of N TACs.

[0121] In this embodiment, the network device can continuously send TACs based on the configured number of TACs, such as based on the uplink timing error. That is, as long as the uplink timing error is within the allowable range, the network device can continuously send TACs to extend the effective GNSS duration of the terminal device. In other words, the network device can extend the effective GNSS duration based on the configured number of TACs, or in other words, the network device can decide whether to continue sending TACs based on the implementation. Of course, in a specific implementation, the effective GNSS duration of the terminal device will not be extended indefinitely. Appropriately extending the effective GNSS duration based on the closed-loop TACs can effectively reduce the number of GNSS measurements performed by the terminal device, thereby reducing the power consumption of the terminal device.

[0122] The fifth method is that the difference between the second effective duration of GNSS and the initial effective duration of GNSS can be determined based on the effective duration of N TACs and the maximum extension duration, which is the maximum value that the effective duration of GNSS can be extended to.

[0123] like Figure 6b and Figure 7b As shown, if the end time of the second effective GNSS duration, determined based on the effective duration of N TACs and the initial effective GNSS duration, is earlier than or equal to the end time determined based on the initial effective GNSS duration and the maximum extension duration, the relevant explanation of the second effective GNSS duration can be found in [reference needed]. Figure 6a and Figure 7a This will not be elaborated upon here.

[0124] If the end time of the second effective GNSS duration, determined based on the effective duration of N TACs and the initial effective GNSS duration, is later than the end time determined based on the initial effective GNSS duration and the maximum extended duration, then the end time determined based on the initial effective GNSS duration and the maximum extended duration is the end time of the second effective GNSS duration. For... Figure 6b The relationship shown (or understood as relating to) Figure 5a As shown in the relationship, when a timer (or maximum extension duration) is configured, the start time of the timer (or the start time of the maximum extension duration) is the end time of the initial GNSS effective duration reported by the terminal device. The terminal device can extend the GNSS effective duration according to TAC, and the maximum extension duration cannot exceed the end time of the timer.

[0125] In this embodiment, N can be understood as the number of TACs actually sent by the network device. The maximum extension duration can be defined by the protocol or configured by the network device. For example, a timer can be configured in the terminal device, and a timer can also be configured in the network device. The timing duration (or countdown duration) of the timer is the aforementioned maximum extension duration. The start time of the aforementioned maximum extension duration is the end time of the initial valid GNSS duration. Alternatively, the start time of the timer is the end time of the initial valid GNSS duration, which is the end time of the valid GNSS duration reported by the terminal device. As an example, before the initial valid GNSS duration ends, but before the timing duration of the timer ends (or before the aforementioned maximum extension duration ends), the terminal device can proceed according to the above... Figure 6a or Figure 7a The method shown continuously extends (or expands) the valid GNSS duration. As another example, if the valid duration of the last TAC received by the terminal device has expired before the timer's timing period ends, or before the maximum extension period mentioned above ends, then... Figure 6b For example, the effective duration of the last TAC can be used as the end time of the second effective GNSS duration. As another example, if the effective duration of the last TAC received by the terminal device has not ended, but the timer's timing duration or the maximum extension duration has ended, then the terminal device can use the timer's timing end time or the maximum extension time's end time as the end time of the second effective GNSS duration.

[0126] In this embodiment of the application, by specifying the extension duration of the effective GNSS duration, network devices can determine the required extension length based on the actual communication scenario, thus offering greater flexibility.

[0127] The sixth method involves determining the difference between the second valid GNSS duration and the initial valid GNSS duration based on the valid duration of N TACs and their maximum number (or maximum number of TACs, etc.). This maximum number is the maximum number of TACs that the network device is allowed to send. N can be understood as the number of TACs that the network device actually sends.

[0128] like Figure 6c and Figure 7c As shown, the maximum number is 3. Even if the terminal device receives 4 TACs, the end time of the second valid GNSS duration is still determined based on the valid duration of 3 TACs and the initial valid GNSS duration. That is... Figure 6c and Figure 7c The fourth TAC shown does not affect the GNSS validity period; the end time of the second GNSS validity period is earlier than or equal to the end time of the third TAC's validity period. Regarding... Figure 6c The relationship shown (or understood as relating to) Figure 5a As shown in the relationship, the maximum number of TACs that can be extended by the network device configuration or protocol agreement. If the terminal device receives multiple TACs, when the number of TACs reaches the maximum number of TACs, the end time of the validity period of the last TAC among the multiple TACs shall be used as the end time of the second validity period of GNSS.

[0129] In this embodiment, the maximum number can be defined by the protocol or configured by the network device. That is, with a maximum number of TACs set, the terminal device can determine the second effective GNSS duration based on the number of TACs that affect the GNSS effective duration and the effective duration of each TAC. Specifying the maximum number of TACs effectively ensures that the GNSS effective duration is not excessively extended.

[0130] The seventh method is to determine the difference between the second effective duration of GNSS and the initial effective duration of GNSS based on the effective duration of N TACs, the maximum number of TACs, and the maximum extension duration.

[0131] like Figure 6d and Figure 7d As shown, the end time of the second valid GNSS duration can be the earliest of the following three end times: the end time determined based on the valid duration of N TACs, the end time determined based on the valid duration of N TACs and the maximum number of TACs, and the end time determined based on the valid duration of N TACs and the maximum extension duration. For a detailed description of the embodiments of this application, please refer to the relevant descriptions of the fourth to sixth methods described above, which will not be elaborated here.

[0132] To facilitate the distinction between different examples, the above text uses the first to seventh methods as numbered, and these numbers should not be construed as limiting the embodiments of this application.

[0133] As one possible implementation, the maximum number or maximum duration can also be related to the capabilities of the terminal device. For example, the terminal device can report its maximum supported duration or its maximum supported number of endpoints. The network device configures the maximum duration or maximum number of endpoints based on the capabilities reported by the terminal device; for instance, the greater the terminal device's capabilities, the larger the maximum duration or maximum number of endpoints can be. Of course, the relationship between capabilities and the maximum number of endpoints, or between capabilities and the maximum duration, can also be defined by the protocol. For example, there can be a correspondence between capabilities and the maximum number of endpoints (such as an index relationship), or a correspondence between capabilities and the maximum duration. Therefore, the terminal device can determine the maximum number of endpoints or the maximum duration based on its capabilities, and correspondingly, the network device can determine the maximum number of endpoints or the maximum duration based on the capabilities reported by the terminal device.

[0134] It should be noted that if the terminal device does not receive information from the network device to trigger GNSS measurements within the aforementioned second valid GNSS duration, the terminal device may enter an idle state or start a timer (the timer mentioned here is different from the timer used to time the maximum extension duration). If the terminal device receives information from the network device to trigger GNSS measurements within the aforementioned second valid GNSS duration, the terminal device can perform GNSS measurements within that second valid GNSS duration. For further details, please refer to [link to relevant documentation]. Figure 8a .

[0135] In conjunction with the above Figure 5a , Figures 6b to 6d The GNSS effective duration reported by the terminal device during initial access (i.e., the initial GNSS effective duration) is determined in idle state based on the UE speed obtained after one or more GNSS measurements. During the connected state of the terminal device, the network device can detect uplink (UL) time errors and send a corresponding closed-loop TAC to the terminal device for TA adjustment. Since the closed-loop TAC partially corrects for TA errors caused by the terminal device's mobility, the GNSS effective duration is extended compared to the GNSS effective duration reported by the terminal device. Therefore, to reduce power consumption caused by GNSS positioning, the actual GNSS effective duration should also consider the traditional closed-loop TAC. Figure 5a or Figure 6a This explains the extension of GNSS validity duration due to closed-loop TA error correction. When a terminal device receives a TAC before the end of the reported GNSS validity duration, and the corresponding TAC validity duration expires after the reported GNSS validity period, the actual end time of the GNSS validity duration (i.e., the second GNSS validity duration) will be postponed to the end time of the TAC validity duration. Furthermore, if the terminal device receives another TAC within the validity duration of the previous TAC, the end time of the actual GNSS validity duration will be further extended to the end time of the next TAC validity duration. To ensure that the accumulated frequency error meets RAN4 requirements, the maximum GNSS validity duration extension should be limited. For example, network devices can configure timers for GNSS validity duration extension. Before the timer expires, the actual GNSS validity duration can be extended based on the closed-loop TAC. When the timer expires, even if the UE receives more TACs, the GNSS validity duration will not be extended, as... Figures 6b to 6d As shown.

[0136] If the terminal device receives a MAC CE for GNSS measurements before the GNSS validity period expires, the terminal device will perform GNSS measurements during the configured GNSS measurement gap (within the timer duration shown in step 807 below), and if the terminal device successfully completes the GNSS measurement as described above, the GNSS validity period will restart from the end of the GNSS measurement gap. Then, upon receiving a closed-loop TAC, the GNSS validity period will be extended again from the reported validity period.

[0137] It is understood that the effective duration shown in the embodiments of this application can also be referred to as validity period, validity, etc., and similar names will not be listed one by one. The extension of the GNSS effective duration can also be referred to as the extension of the GNSS effective duration, etc.

[0138] The following description uses the first communication device as the terminal device and the second communication device as the network device to illustrate the method provided in the embodiments of this application. Figure 8a This is a flowchart illustrating a satellite communication method provided in an embodiment of this application. Figure 8a As shown, the method includes:

[0139] 801. The terminal device reports the time required to perform GNSS measurements and the initial effective duration of GNSS.

[0140] For example, the duration required to perform GNSS measurements and the initial valid duration of GNSS can be carried in the same message or in different messages.

[0141] For example, the terminal device may perform step 801 above during the random access process, or it may perform step 801 above after it enters the connected state.

[0142] 802. When the uplink timing error of the terminal device is less than or equal to a certain threshold, the network device sends a TAC within the initial effective duration of GNSS, and the corresponding terminal device receives the TAC.

[0143] For a detailed explanation of step 802, please refer to step 302, which will not be elaborated here.

[0144] 803. The terminal equipment determines the second valid duration of GNSS, and the network equipment determines the second valid duration of GNSS.

[0145] For a detailed explanation of step 803, please refer to step 303, which will not be elaborated here.

[0146] For example, the number of times steps 802 and 803 are executed can be determined based on the number of TACs sent by the network device (as can be referred to). Figure 4a and Figure 4bRegarding the relationship between the second effective duration of GNSS and the initial effective duration of GNSS, please refer to [reference needed]. Figures 5a to 5c ,or Figures 6a to 6d ,or Figures 7a to 7d Etc., will not be elaborated here.

[0147] 804. Within the second valid GNSS duration, the network device sends information to trigger GNSS measurements, and the corresponding terminal device receives the information (or triggering information) used to trigger GNSS measurements.

[0148] For example, the information described above for triggering GNSS measurements may also include resources for the GNSS measurements. These resources may include the duration of the GNSS measurements. The terminal device can receive the instruction information for triggering GNSS measurements, as well as the resources allocated by the network device for the GNSS measurements, within the second valid duration of the GNSS measurements.

[0149] 805. The terminal device performs GNSS measurements on the resources used for GNSS measurements, and continues to communicate with the network device after completing the GNSS measurements.

[0150] 806. The terminal device did not receive the information to trigger GNSS measurement within the second valid GNSS duration, and the terminal device entered the idle state.

[0151] For example, after the terminal device enters the idle state, it can perform GNSS measurements in the idle state and then re-initiate random access. It can be understood that steps 806 and 807 are parallel solutions, and in a specific implementation, the terminal device executes only one of these steps. The solutions shown in steps 804 and 805 are parallel solutions to the solution shown in step 806 (or step 807).

[0152] 807. If the terminal device does not receive information to trigger GNSS measurement within the second valid GNSS duration, a timer is started. If the GNSS measurement is completed within the timer's duration, the terminal device continues to communicate with the network device. The start time (or start timing) of the timer is the end time of the second valid GNSS duration.

[0153] For example, the timing duration of the timer shown here can be configured by the network device to the terminal device via RRC signaling or MAC-CE signaling. The start conditions of the timer can also be configured, such as starting the timer at the end of the second valid GNSS duration. It is understood that the timing duration and timer duration shown in the embodiments of this application can be interchanged, and the start timing time and start timer time (or similar descriptions such as start time) can also be interchanged.

[0154] As an example, the terminal device can communicate with the network device after the timer's duration has expired. For instance, the network device can schedule the terminal device to send an uplink signal after the timer's duration has ended, or the terminal device can initiate an uplink transmission request after the timer's duration has ended. This approach minimizes the impact on communication between the terminal device and the network device while the terminal device is performing GNSS measurements, thus improving communication reliability.

[0155] As another example, the terminal device can communicate with the network device after completing GNSS measurements. Since the network device may not know precisely when the terminal device completed the GNSS measurements, it can continuously attempt uplink scheduling with the terminal device before the timer expires (if the network device receives an uplink signal from the terminal device, it indicates that the terminal device has successfully completed the GNSS measurements), or the terminal device can initiate an uplink transmission request after completing the GNSS measurements. This approach allows the terminal device to resume communication with the network device as soon as possible.

[0156] For example, if the terminal device receives a GNSS measurement trigger message within the second valid GNSS duration, it can perform GNSS measurements based on the configured resources. If the terminal device does not receive a trigger message within the second valid GNSS duration, it starts a timer at the end of the second valid GNSS duration according to step 807 above and performs GNSS measurements automatically based on the timer. This allows the terminal device to perform GNSS measurements automatically even when the second valid GNSS duration ends and no trigger message is received, effectively reducing the number of times the terminal device disconnects.

[0157] In this embodiment, since the terminal device can complete the GNSS measurement before the timer expires, it can continue to communicate with the network device.

[0158] For example, continued communication between the terminal device and the network device may include the terminal device sending an uplink signal to the network device. For example, this uplink signal may carry the initial valid GNSS duration (e.g., the initial valid duration obtained based on the GNSS measurement shown in step 807). The initial valid GNSS duration shown here may be the same as (and if the same, the uplink signal may not carry the initial valid GNSS duration) or different from the initial valid GNSS duration in step 801 above. By sending the initial valid GNSS duration, the terminal device can indicate that it has completed the GNSS measurement. As an example, the terminal device may report the initial valid GNSS duration differentially, such as the difference between the initial valid GNSS duration in step 807 and the initial valid GNSS duration in step 801; or the difference between the initial valid GNSS duration in step 807 and the previously reported initial valid GNSS duration. As another example, terminal devices can report the initial valid duration of GNSS data in an indexed manner. Each initial valid duration of GNSS data can correspond to an index, and the terminal device indicates the corresponding initial valid duration of GNSS data by reporting the index value. Generally, the start time of a new initial valid duration of GNSS data reported by the terminal device can be the end time of the second valid duration of GNSS data, or the end time of a timer. Figure 6b For example, the relationship shown is as follows: Figure 8b As shown, within the timer's duration, the terminal device can perform GNSS measurements. Upon completion of the GNSS measurements, the terminal device can report a new initial valid GNSS duration. For example, the start time of this new initial valid GNSS duration is the end time of the timer.

[0159] For example, if the terminal device fails to complete the GNSS measurement within the timer's duration, it enters an idle state.

[0160] In this embodiment, based on the uplink synchronization achieved by the terminal device, the communication duration of the terminal device can be increased (or the duration of the terminal device in the connected state can be increased), enabling the terminal device to achieve long-term communication. This also avoids the signaling overhead caused by the terminal device constantly entering and exiting the connected state, thus reducing signaling overhead. Furthermore, when the second valid GNSS duration ends and no trigger information is received, the terminal device can automatically start a timer to perform GNSS measurements, further reducing the number of times the terminal device disconnects and further increasing the communication duration between the terminal device and the network device.

[0161] In the embodiments shown above, the terminal device and network device may not determine the second effective GNSS duration, but instead determine an extension of the effective GNSS duration, which may be an extension relative to the first effective GNSS duration. For an explanation of the first effective GNSS duration, please refer to the above text. Figure 3 The two explanations shown will not be elaborated further here. For example, the extended duration can be equal to the difference between the second valid GNSS duration and the first valid GNSS duration. That is, the terminal device and network device can skip the step of determining the second valid GNSS duration, and instead determine the extended duration of the valid GNSS duration based on the first valid GNSS duration, which is equal to the aforementioned difference.

[0162] For specific details regarding the extension duration, please refer to the explanation of the second and first valid GNSS durations above. The difference between the second and first valid GNSS durations can be equal to the extension duration. Alternatively, for further details regarding the extension duration, please refer to the explanation of the second and initial valid GNSS durations above. The difference between the second and initial valid GNSS durations can be equal to the extension duration. The following example illustrates how to determine the extension duration:

[0163] For example, regarding Figure 5a For example, the terminal device can determine the difference between the end time of the effective duration of the TAC and the end time of the first effective duration of the GNSS; this difference is the extension duration. For instance, regarding... Figure 5b In this case, the terminal device can determine the valid duration of the TAC, which is the extended duration. For example, regarding... Figure 5c For example, the terminal device can determine the extension duration based on the difference between the end time of the effective duration of the TAC and the end time of the first effective duration of GNSS, as well as the effective duration of the TAC. For instance, regarding... Figure 6a Specifically, the terminal device can determine the extension duration based on the start time of the TAC's effective duration, the effective duration of the TAC, the number of TACs, and the end time of the initial effective duration of GNSS. For a detailed explanation of the extension duration, please refer to the descriptions of the second effective duration of GNSS, the first effective duration of GNSS, and the initial effective duration of GNSS in the above embodiments, which will not be elaborated here.

[0164] This application also provides a satellite communication method in which a terminal device determines a third valid GNSS duration, which is longer than the initial valid GNSS duration. The terminal device reports the third valid GNSS duration, and correspondingly, a network device receives the third valid GNSS duration. The terminal device communicates with the network device within the third valid GNSS duration. If the terminal device can receive a TAC (Temporary Access Control) within the third valid GNSS duration, it can adjust the uplink timing in advance based on the TAC. Optionally, after the third valid GNSS duration ends, the terminal device can enter an idle state. Alternatively, based on the third valid GNSS duration, the terminal device and the network device can communicate according to the steps shown in 804 to 807 above. As an example, the third valid GNSS duration can be determined based on the initial valid GNSS duration and the communication duration required (or predicted, expected) by the terminal device. As another example, the third valid GNSS duration can be determined based on the initial valid GNSS duration and the capabilities of the terminal device. The greater the capability of the terminal device, the longer the third valid GNSS duration can be.

[0165] For example, the terminal device can report the third valid duration of GNSS in the following ways: the terminal device can send information to carry the third valid duration of GNSS; or, the terminal device can report the third valid duration of GNSS in a differential manner, such as the terminal device can send the difference between the third valid duration of GNSS and the initial valid duration of GNSS.

[0166] For example, the terminal device can periodically report the third valid duration of GNSS, and the specific value of the third valid duration of GNSS can vary depending on the implementation. For example, the terminal device can also report the third valid duration of GNSS at any time.

[0167] In this embodiment of the application, the terminal device can effectively improve the communication duration between the terminal device and the network device by extending the initial effective duration of GNSS and reporting the extended initial effective duration of GNSS to the network device.

[0168] The following describes the communication device provided in the embodiments of this application.

[0169] This application divides the communication device into functional modules according to the above-described method embodiments. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and represents only one logical functional division; other division methods may be used in actual implementation. The following will combine... Figures 9 to 11 The communication device of the embodiments of this application is described in detail.

[0170] Figure 9 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application, such as... Figure 9 As shown, the communication device includes a processing unit 901 and a transceiver unit 902. The transceiver unit 902 can implement corresponding communication functions, and the processing unit 901 is used for data processing. The transceiver unit 902 can also be referred to as an interface, communication interface, or communication unit, etc.

[0171] In some embodiments of this application, the communication device can be used to perform the actions performed by the terminal device in the above method embodiments. In this case, the communication device can be the terminal device or a component (such as a chip or system) configurable on the terminal device. The transceiver unit 902 is used to perform the transceiver-related operations of the terminal device in the above method embodiments, and the processing unit 901 is used to perform the processing-related operations of the terminal device in the above method embodiments. The communication device can be used to perform the steps or functions performed by the terminal device in the above method embodiments.

[0172] For example, processing unit 901 is used to determine the first effective duration of GNSS;

[0173] Transceiver unit 902 is used to receive TAC from network device within the first valid duration of GNSS; or, transceiver unit 902 is used to input TAC to processing unit 901 within the first valid duration of GNSS.

[0174] The processing unit 901 is also used to determine the second effective duration of GNSS.

[0175] For example, the processing unit 901 is also configured to update the second valid duration of GNSS to a new first valid duration of GNSS.

[0176] For example, the processing unit 901 is further configured to control the communication device to enter an idle state if no information for triggering GNSS measurement is received within the second valid GNSS duration; or, if no information for triggering GNSS measurement is received within the second valid GNSS duration, start a timer, and continue communication through the transceiver unit 902 if the GNSS measurement is completed within the timer's duration.

[0177] The specific descriptions of the transceiver unit and processing unit shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver unit and processing unit, please refer to the above method embodiments (such as...). Figure 3 , Figure 4a , Figure 4b , Figure 8a (This will not be elaborated on here.)

[0178] Optionally, the communication device may further include a storage unit, which can be used to store instructions and / or data. The processing unit 901 can read the instructions and / or data from the storage unit to enable the communication device to implement the aforementioned method embodiments. For example, the storage unit can be used to store the initial effective duration of GNSS, the maximum number of GNSS instances, or the maximum extended duration, etc.

[0179] Reuse Figure 9 In other embodiments of this application, the communication device can be used to perform the actions performed by the network device in the above method embodiments. In this case, the communication device can be a network device or a component configurable on a network device. The transceiver unit 902 is used to perform the transceiver-related operations of the network device in the above method embodiments, and the processing unit 901 is used to perform the processing-related operations of the network device in the above method embodiments. The communication device can be used to perform the steps or functions performed by the network device in the above method embodiments.

[0180] For example, processing unit 901 is used to determine the first effective duration of GNSS;

[0181] Transceiver unit 902 is used to transmit TAC within the first valid duration of GNSS; or, transceiver unit 902 is used to output TAC within the first valid duration of GNSS.

[0182] The processing unit 901 is also used to determine the second effective duration of GNSS.

[0183] For example, the processing unit 901 is also configured to update the second valid duration of GNSS to a new first valid duration of GNSS.

[0184] In this application embodiment, the descriptions of the first valid GNSS duration, the second valid GNSS duration, the valid TAC duration, the initial valid GNSS duration, etc., can be found in the above method embodiment (including...). Figure 3 , Figure 4a , Figure 4b , Figures 5a to 5c , Figures 6a to 6d , Figures 7a to 7d , Figure 8a and Figure 8b The details described in the document will not be elaborated here.

[0185] It is understood that the specific descriptions of the transceiver unit and processing unit shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver unit and processing unit, please refer to the above method embodiments, which will not be described in detail here.

[0186] The communication device according to embodiments of this application has been described above. The following describes possible product forms of the communication device. It should be understood that any device possessing the above-described features... Figure 9Any form of the communication device described herein falls within the protection scope of the embodiments of this application. It should also be understood that the following description is merely illustrative and does not limit the form of the communication device in the embodiments of this application to this specific example.

[0187] In one possible implementation, Figure 9 In the communication device shown, the processing unit 901 can be one or more processors, and the transceiver unit 902 can be a transceiver, or the transceiver unit 902 can also be a transmitting unit and a receiving unit. The transmitting unit can be a transmitter, and the receiving unit can be a receiver. The transmitting unit and the receiving unit are integrated into one device, such as a transceiver. In the embodiments of this application, the processor and the transceiver can be coupled, etc., and the connection method between the processor and the transceiver is not limited in the embodiments of this application. In the process of executing the above method, the process of sending information in the above method can be understood as the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After the above information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information in the above method can be understood as the process of the processor receiving the input above information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to undergo other processing before being input into the processor.

[0188] like Figure 10 As shown, the communication device 100 includes one or more processors 1020 and transceivers 1010.

[0189] For example, when the communication device is used to perform the steps, methods or functions performed by the first communication device or terminal device described above, the processor 1020 is used to determine a first valid duration of GNSS; the transceiver 1010 is used to receive TAC from the network device within the first valid duration of GNSS; the processor 1020 is also used to determine a second valid duration of GNSS.

[0190] For example, processor 1020 is also configured to update the second valid duration of GNSS to a new first valid duration of GNSS.

[0191] For example, the processor 1020 is also configured to control the communication device to enter an idle state if no information for triggering GNSS measurement is received within the second valid GNSS duration; or, if no information for triggering GNSS measurement is received within the second valid GNSS duration, start a timer, and continue communicating with the network device via the transceiver 1010 if the GNSS measurement is completed within the timer's duration.

[0192] For example, when the communication device is used to perform the steps, methods or functions performed by the second communication device or network device described above, for example, the processor 1020 is used to determine the first valid duration of GNSS; the transceiver 1010 is used to transmit TAC within the first valid duration of GNSS; and the processor 1020 is also used to determine the second valid duration of GNSS.

[0193] For example, processor 1020 is also configured to update the second valid duration of GNSS to a new first valid duration of GNSS.

[0194] In this application embodiment, the descriptions of the first valid GNSS duration, the second valid GNSS duration, the valid TAC duration, the initial valid GNSS duration, etc., can be found in the above method embodiment (including...). Figure 3 , Figure 4a , Figure 4b , Figures 5a to 5c , Figures 6a to 6d , Figures 7a to 7d , Figure 8a and Figure 8b The details described in [the previous section] will not be repeated here. For further information on the processor and transceiver, please refer to [the relevant documentation]. Figure 9 The descriptions of the processing unit and transceiver unit shown will not be repeated here.

[0195] exist Figure 10 In various implementations of the communication apparatus shown, the transceiver may include a receiver for performing a receiving function (or operation) and a transmitter for performing a transmitting function (or operation). The transceiver is also used to communicate with other devices / appliances via a transmission medium.

[0196] Optionally, the communication device 100 may further include one or more memories 1030 for storing program instructions and / or data. The memories 1030 are coupled to the processor 1020. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules. The processor 1020 may operate in conjunction with the memories 1030. The processor 1020 may execute program instructions stored in the memories 1030. Optionally, at least one of the above-mentioned memories may be included in the processor. In this embodiment, the memories 1030 may store GNSS initial effective duration, maximum number, or maximum extension duration, etc. For example, Figure 10 The memory shown is only exemplarily illustrated for the effective duration of GNSS.

[0197] This application embodiment does not limit the specific connection medium between the transceiver 1010, processor 1020, and memory 1030. This application embodiment... Figure 10 The memory 1030, processor 1020, and transceiver 1010 are connected via a bus 1040, and the bus is in Figure 10 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 10 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0198] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules within the processor.

[0199] In this application embodiment, the memory may include, but is not limited to, non-volatile memory such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or compact disc read-only memory (CD-ROM), etc. Memory is any storage medium capable of carrying or storing program code in the form of instructions or data structures, and capable of being read and / or written by a computer (such as the communication device shown in this application), but is not limited to this. The memory in this application embodiment may also be a circuit or any other device capable of implementing storage functions, used to store program instructions and / or data.

[0200] The processor 1020 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs. The memory 1030 is mainly used to store software programs and data. The transceiver 1010 may include control circuitry and an antenna. The control circuitry is mainly used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0201] When the communication device is powered on, the processor 1020 can read the software program in the memory 1030, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1020 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit then performs RF processing on the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1020. The processor 1020 converts the baseband signal into data and processes the data.

[0202] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0203] It is understood that the communication device shown in the embodiments of this application may also have more than Figure 10 This application does not limit the use of other components or other related elements. The methods performed by the processor and transceiver shown above are merely examples; the specific steps performed by the processor and transceiver can be found in the methods described above.

[0204] For example, this application also provides a network device, which may include an active antenna unit (AAU) and a building base band unit (BBU). The BBU can be a component of a distributed base station, mainly performing baseband processing of signals (such as channel coding, channel demodulation, modulation and demodulation, etc.), providing transmission management and interfaces, managing radio resources, and providing clock signals, among other functions.

[0205] In another possible implementation, Figure 9In the communication device shown, the processing unit 901 can be one or more logic circuits, and the transceiver unit 902 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver unit 902 can also be a transmitting unit and a receiving unit; the transmitting unit can be an output interface, and the receiving unit can be an input interface, integrated into one unit, such as an input / output interface. Figure 11 As shown, Figure 11 The communication device shown includes logic circuitry 1101 and interface 1102. That is, the processing unit 901 can be implemented using logic circuitry 1101, and the transceiver unit 902 can be implemented using interface 1102. The logic circuitry 1101 can be a chip, processing circuit, integrated circuit, or system-on-chip (SoC) chip, etc., and the interface 1102 can be a communication interface, input / output interface, pins, etc. For example, Figure 11 Taking the aforementioned communication device as an example, the chip includes a logic circuit 1101 and an interface 1102.

[0206] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method between the logic circuit and the interface is not limited in this embodiment.

[0207] For example, when the communication device is used to perform the method, function or step performed by the first communication device or terminal device described above, the logic circuit 1101 is used to determine the first effective duration of GNSS; the interface 1102 is used to input TAC to the logic circuit 1101 within the first effective duration of GNSS; the logic circuit 1101 is also used to determine the second effective duration of GNSS.

[0208] For example, logic circuit 1101 is also used to update the second valid duration of GNSS to a new first valid duration of GNSS.

[0209] For example, logic circuit 1101 is also configured to control the communication device to enter an idle state if no information for triggering GNSS measurement is received within the second valid GNSS duration; or, if no information for triggering GNSS measurement is received within the second valid GNSS duration, start a timer, and continue communication through interface 1102 if GNSS measurement is completed within the timer's duration.

[0210] For example, when a communication device is used to perform the method, function or step performed by the second communication device or network device described above, for example, logic circuit 1101 is used to determine the first effective duration of GNSS; interface 1102 is used to output TAC within the first effective duration of GNSS; logic circuit 1101 is also used to determine the second effective duration of GNSS.

[0211] For example, logic circuit 1101 is also used to update the second valid duration of GNSS to a new first valid duration of GNSS.

[0212] For example, Figure 11 The chip shown may also include a memory that can be used to store the initial effective duration of GNSS, the maximum number of GNSS, the maximum extension duration, etc.

[0213] It is understood that the communication device shown in the embodiments of this application can implement the method provided in the embodiments of this application in hardware form or in software form, etc., and the embodiments of this application do not limit it in this way.

[0214] In this application embodiment, the descriptions of the first valid GNSS duration, the second valid GNSS duration, the valid TAC duration, the initial valid GNSS duration, etc., can be found in the above method embodiment (including...). Figure 3 , Figure 4a , Figure 4b , Figures 5a to 5c , Figures 6a to 6d , Figures 7a to 7d , Figure 8a and Figure 8b The details described in the document will not be elaborated here.

[0215] for Figure 11 For specific implementations of the various embodiments shown, please refer to the above embodiments, which will not be described in detail here.

[0216] This application also provides a wireless communication system, which includes a first communication device and a second communication device. The first communication device and the second communication device can be used to perform the methods in any of the foregoing embodiments.

[0217] In addition, this application also provides a computer program for implementing the operations and / or processes performed by the first communication device in the method provided in this application.

[0218] This application also provides a computer program for implementing the operations and / or processes performed by the second communication device in the method provided in this application.

[0219] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by the first communication device in the method provided in this application.

[0220] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by the second communication device in the method provided in this application.

[0221] This application also provides a computer program product, which includes computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by the first communication device in the method provided in this application to be executed.

[0222] This application also provides a computer program product, which includes computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by the second communication device in the method provided in this application to be executed.

[0223] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, or it may be an electrical, mechanical, or other form of connection.

[0224] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of this application.

[0225] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0226] 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, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned readable 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.

[0227] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method of satellite communication, characterized by, The method is applied to a first communication device, and the method comprises: determining a global navigation satellite system (GNSS) validity period; determining an extension time according to a validity time of a timing advance command (TAC), wherein a start time point of the extension time is an end time point of the GNSS validity period, and an end time point of the extension time is an end time point of the validity time of the TAC, and the TAC is received within the GNSS validity period; in a case where the extension time ends and trigger information of GNSS measurement is not received, performing GNSS measurement or entering an idle state.

2. The method of claim 1, wherein, The validity time of the TAC is configured by a network device through radio resource control (RRC) signaling or medium access control-control element (MAC-CE) signaling.

3. The method according to claim 1 or 2, characterized in that, The end time of the validity time of the TAC is later than the end time of the GNSS validity period.

4. The method of claim 1, wherein, The performing GNSS measurement in the case where the extension time ends and trigger information of GNSS measurement is not received comprises: in a case where information for triggering GNSS measurement from a second communication device is not received within the extension time, starting a timer, and in a case where the GNSS measurement is completed within a timing duration of the timer, continuing communication with the second communication device, wherein a start time of the timer is the end time of the extension time.

5. A satellite communication method characterized by, The method comprises: a first communication device determines a global navigation satellite system (GNSS) validity period; a second communication device sends a timing advance command (TAC) to the first communication device, and the TAC is received by the first communication device within the GNSS validity period; the first communication device determines an extension time according to a validity time of the TAC, wherein a start time point of the extension time is an end time point of the GNSS validity period, and an end time point of the extension time is an end time point of the validity time of the TAC; in a case where the extension time ends and trigger information of GNSS measurement is not received, the first communication device performs GNSS measurement or enters an idle state.

6. The method of claim 5, wherein, The validity time of the TAC is configured by a network device through radio resource control (RRC) signaling or medium access control-control element (MAC-CE) signaling.

7. The method according to claim 5 or 6, characterized in that, The end time of the validity time of the TAC is later than the end time of the GNSS validity period.

8. The method of claim 5, wherein, The first communication device performs GNSS measurement in the case where the extension time ends and trigger information of GNSS measurement is not received, comprising: in a case where information for triggering GNSS measurement from a second communication device is not received within the extension time, starting a timer, and in a case where the GNSS measurement is completed within a timing duration of the timer, continuing communication with the second communication device, wherein a start time of the timer is the end time of the extension time.

9. A first communication device, the first communication device comprising: The device comprises: a processing unit configured to determine a global navigation satellite system (GNSS) validity period; The processing unit is further configured to determine an extension time according to a valid time of a timing advance command (TAC), wherein a start time point of the extension time is an end time point of the GNSS validity period, and an end time point of the extension time is an end time point of the valid time of the TAC, and the TAC is received in the GNSS validity period. The processing unit is further configured to perform GNSS measurement or enter an idle state when the extension time ends and no trigger information of GNSS measurement is received.

10. The apparatus of claim 9, wherein, The valid time of the TAC is configured by a network device through radio resource control (RRC) signaling or medium access control-control element (MAC-CE) signaling.

11. The apparatus of claim 9 or 10, wherein, The end time point of the valid time of the TAC is later than the end time point of the GNSS validity period.

12. The apparatus of claim 9, wherein, The processing unit is configured to perform GNSS measurement when the extension time ends and no trigger information of GNSS measurement is received, including: The processing unit is configured to start a timer when no information for triggering GNSS measurement from a second communication device is received in the extension time, and continue to communicate with the second communication device when the GNSS measurement is completed within a timing duration of the timer, wherein a start time of the timer is an end time point of the extension time.

13. A communication system, characterized by The first communication device and the second communication device are configured to perform the method according to any one of claims 5-8.

14. A communications device, characterized by The communication device comprises a processor and a memory; The memory is configured to store instructions; The processor is configured to execute the instructions to cause the method according to any one of claims 1-8 to be performed.

15. The communication apparatus according to claim 14, wherein The communication device is a chip.

16. A communications device, characterized by The communication device comprises a logic circuit and an interface, and the logic circuit and the interface are coupled; The interface is configured to input and / or output information, and the logic circuit is configured to perform the method according to any one of claims 1-8.

17. A computer-readable storage medium, characterized in that, The computer readable storage medium is configured to store a computer program, and when the computer program is executed, the method according to any one of claims 1-8 is performed.

18. A computer program, characterized in that, When the computer program is executed, the method according to any one of claims 1-8 is performed.

Images