Communication method and apparatus

Abstract

The application provides a communication method, comprising: a terminal device acquiring GNSS position information in a preset period, wherein the time when the terminal device starts to acquire the GNSS position information is a first time, and the time when the terminal device completes the acquisition of the GNSS position information is a second time; after acquiring the GNSS position information, the terminal device triggers a TAR; or between the first time and the second time, the terminal device prohibits triggering the TAR; or between the first time and the second time, the terminal device triggers a first TAR; after acquiring the GNSS position information, the terminal device determines whether to cancel the first TAR according to a first change amount; or between the first time and the second time, the terminal device prohibits generating a TA reporting MAC CE, and the TA reporting MAC CE is used for reporting a TA. The scheme based on the embodiments of the application can improve the accuracy of the terminal device in reporting the TA.

Description

[0001] This application is a divisional application. The original application has the application number 202310541138.1 and the original application date is May 12, 2023. The entire contents of the original application are incorporated herein by reference.

[0002] This application claims priority to Chinese Patent Application No. 202310166517.7, filed on February 16, 2023, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communications, and more specifically, to a communication method and apparatus. Background Technology

[0004] Currently, there exists a type of terminal device with relatively weak capabilities. Specifically, the Global Navigation Satellite System (GNSS) acquisition module and communication module of this type of terminal device cannot work simultaneously, thus requiring dedicated time for GNSS location information acquisition.

[0005] For example, such terminal devices can be Internet of Things (IoT) devices, which are generally used in transportation and logistics (such as marine, highway, railway and aviation), solar energy, oil and gas extraction, agriculture and animal husbandry, environmental monitoring, mining and other industries.

[0006] These types of terminal devices can access non-terrestrial networks (NTNs), which provide communication services to them. Accessing the network requires GNSS location information as an aid; for example, GNSS information is needed to calculate timing advance (TA) for time and frequency synchronization.

[0007] However, during GNSS location information acquisition, these types of terminal devices may trigger a Time Advance Report (TAR). The TA value corresponding to this TAR is obtained based on outdated GNSS location information. Therefore, this TA value may be inaccurate. In other words, when these terminal devices trigger a TAR during GNSS measurements, they may report inaccurate TA values ​​to the network equipment. Inaccurate TA values ​​may cause these terminal devices to lose synchronization with the network equipment.

[0008] Therefore, improving the accuracy of the TA values ​​reported by such terminal devices is a problem that needs to be solved. Summary of the Invention

[0009] This application provides a communication method and apparatus for improving the accuracy of TA values ​​reported by terminal devices.

[0010] Firstly, a communication method is provided, including:

[0011] The terminal device acquires GNSS location information within a preset time period, wherein the moment when the terminal device begins acquiring the GNSS location information is the first moment, and the moment when the terminal device completes acquiring the GNSS location information is the second moment.

[0012] It should be noted that the preset time period is the time period during which the terminal device acquires GNSS location information; alternatively, the preset time period can also be a GAP, which is a time period specifically used by the terminal device for acquiring GNSS location information, during which the terminal device acquires GNSS location information. In this case, the first moment can also be the start moment of the GAP; the second moment can also be the end moment of the GAP.

[0013] After acquiring the GNSS location information, the terminal device triggers a TAR; or, between the first time and the second time, the terminal device prohibits triggering a TAR; or, between the first time and the second time, the terminal device triggers a first TAR; after acquiring the GNSS location information, the terminal device determines whether to cancel the first TAR based on a first change amount, where the first change amount is the change of the first TA relative to the second TA, the first TA is obtained based on the GNSS location information, and the second TA is the latest TA reported by the terminal device before the preset time period; or, between the first time and the second time, the terminal device prohibits generating TAs and reporting them to the media access control element (MAC CE), where the TA reporting to the MAC CE is used to report TAs.

[0014] According to an embodiment of this application, the terminal device is prohibited from triggering TAR during GNSS measurements. Alternatively, the terminal device is prohibited from triggering TAR during GAP (Gap-Off) periods. This method prevents the terminal device from reporting inaccurate TA (Target Acquisition) data to the network device, thus addressing the aforementioned problem at its source.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the end time of the preset time period is the third time. After acquiring the GNSS location information, the terminal device triggers TAR, including:

[0016] The terminal device triggers TAR between the second time and the third time; or, the terminal device triggers TAR after the third time.

[0017] In conjunction with the first aspect, in certain implementations of the first aspect, after acquiring the GNSS location information, the terminal device triggers TAR, including:

[0018] After acquiring the GNSS location information, the terminal device does not need to determine whether to trigger TAR based on the first change amount; that is, TAR is triggered immediately after acquiring the GNSS location information. The first change amount is the change in the first TA relative to the second TA. The first TA is obtained based on the GNSS location information, and the second TA is the latest TA reported by the terminal device before the preset time period. Equivalently, acquiring the GNSS location information could also be after the preset time period ends, or after the GAP ends.

[0019] In conjunction with the first aspect, in certain implementations of the first aspect, after acquiring the GNSS location information, the terminal device triggers TAR, including:

[0020] After acquiring the GNSS location information, the terminal device determines a first change, which is the change in the first TA relative to a second TA. The first TA is obtained based on the GNSS location information, and the second TA is the latest TA reported by the terminal device before the preset time period. If the first change is greater than or equal to a preset threshold, the terminal device triggers a TAR (Temporary Asynchronous Response). Equivalently, acquiring the GNSS location information can also occur after the preset time period ends or after the GAP (Gap-Off) ends.

[0021] In conjunction with the first aspect, in certain implementations of the first aspect, the terminal device determines whether to cancel the first TAR based on the first change amount, including:

[0022] If the first change amount is less than a preset threshold, the terminal device cancels the first TAR.

[0023] In conjunction with the first aspect, in certain implementations of the first aspect, between the first time point and the second time point, the terminal device is prohibited from generating TA to report MAC CE, including:

[0024] Between the first time point and the second time point, the terminal device is prohibited from using the uplink shared channel UL-SCH resource and is prohibited from triggering scheduling requests.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, the terminal device is an Internet of Things (IoT) terminal.

[0026] Secondly, a communication method is provided, including:

[0027] The terminal device acquires the GNSS location information of the first global navigation satellite system during a preset time period; the terminal device determines whether to trigger a conditional switching (CHO) during the preset time period.

[0028] In conjunction with the second aspect, in certain implementations of the second aspect, the terminal device determines whether to trigger a CHO during the preset time period, including:

[0029] The terminal device determines that CHO should be prohibited from being triggered during the preset time period.

[0030] According to the embodiments of this application, since the reliability (or accuracy) of the GNSS location information of the terminal device is low during a preset time period, if the terminal device evaluates whether to trigger a Change-On (CHO) based on the low reliability of the GNSS information, it may result in the handover being too early or too late. Therefore, the terminal device can prohibit the triggering of a CHO during this preset time period.

[0031] In conjunction with the second aspect, in some implementations of the second aspect, the moment when the terminal device begins acquiring the first GNSS location information is designated as the first moment, and the moment when the terminal device completes acquiring the first GNSS location information is designated as the second moment. The terminal device determines whether to trigger a Choo (CHO) during the preset time period, including:

[0032] The terminal device determines that CHO can be triggered based on the first GNSS location information after the second time.

[0033] According to an embodiment of this application, after GNSS measurement is completed, first GNSS location information (i.e., updated GNSS location information) is obtained. At this time, the preset time period may not have ended yet. The terminal device can use the first GNSS location information to assess whether a CHO (Confirmation of Hazard) has been triggered before the preset time period ends, thereby helping the terminal device to switch to a new network device in a timely manner.

[0034] In conjunction with the second aspect, in certain implementations of the second aspect, the terminal device determines whether to trigger a CHO during the preset time period, including:

[0035] The terminal device determines that CHO can be triggered during the preset time period.

[0036] In conjunction with the second aspect, in certain implementations of the second aspect, the terminal device is able to switch from a source network device to a target network device based on a CHO, and the terminal device determines that triggering a CHO is permitted during the preset time period, including:

[0037] The terminal device determines the remaining service duration, which is the remaining duration for which the source network device can provide services to the terminal device. If the remaining service duration is less than a preset threshold, the terminal device determines that a Choke on the Second GNSS Location Information and / or a First RSRP is allowed to be triggered during the preset time period, wherein the second GNSS location information and the first RSRP are both acquired by the terminal device before the preset time period. If the remaining service duration is greater than the preset threshold, the terminal device determines that a Choke on the First GNSS Location Information is allowed to be triggered during the preset time period.

[0038] In conjunction with the second aspect, in certain implementations of the second aspect, the terminal device determines that triggering a CHO is permitted during the preset time period, including:

[0039] The terminal device determines that it is permissible to trigger a CHO based on the second GNSS location information and / or the first RSRP during the preset time period, wherein the second GNSS location information and the first RSRP are both acquired by the terminal device before the preset time period.

[0040] Thirdly, a communication method is provided, including:

[0041] The terminal device starts a first timer. During the operation of the first timer, the terminal device needs to perform at least one of the following tasks: radio link monitoring, cell selection, serving cell measurement, neighbor cell measurement, system information reading, and radio link reconstruction. When the terminal device starts GNSS measurement before the first timer expires, the terminal device does not run the first timer during the GNSS measurement, wherein the terminal device cannot perform the task during the GNSS measurement.

[0042] In conjunction with the third aspect, in certain implementations of the third aspect, when the terminal device initiates GNSS measurement before the first timer expires, the terminal device does not run the first timer during the GNSS measurement, including:

[0043] The terminal device pauses the first timer before the GNSS measurement begins and restarts the first timer after the GNSS measurement is completed.

[0044] In conjunction with the third aspect, in certain implementations of the third aspect, when the terminal device initiates GNSS measurement before the first timer expires, the terminal device does not run the first timer during the GNSS measurement, including:

[0045] The terminal device stops the first timer before the GNSS measurement begins.

[0046] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes:

[0047] After the GNSS measurement is completed, the terminal device starts a second timer, and the first timer and the second timer are of the same type.

[0048] In conjunction with the third aspect, in some implementations of the third aspect, the preset timeout duration of the first timer is the same as the preset timeout duration of the second timer.

[0049] In conjunction with the third aspect, in some implementations of the third aspect, the preset timeout duration of the second timer is a first value, which is equal to the preset timeout duration of the first timer minus the runtime of the first timer.

[0050] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes:

[0051] When the GNSS measurement begins, the terminal device activates a second timer. The first timer and the second timer are of the same type, and the preset timeout duration of the second timer is a third value, which is equal to the preset timeout duration of the first timer plus the duration required for the GNSS measurement.

[0052] Fourthly, a communication method is provided, including:

[0053] The terminal device reads system information, which includes satellite-aided information. The satellite-aided information includes at least one of the following: ephemeris information, satellite-to-reference point delay parameters, effective duration of satellite-aided information, and reference time of satellite-aided information. The terminal device sends first information to the network device, which indicates the remaining effective time of the satellite-aided information obtained by the terminal device.

[0054] The terminal device receives second information from the network device, the second information being used to indicate a first time period, the first time period being used for the terminal device to perform GNSS measurements, wherein the terminal device does not read system information during the first time period.

[0055] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the end time of the first time period is before the start time of the system information reading.

[0056] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the start time of the first time period is after the end time of the system information reading.

[0057] Fifthly, a communication method is provided, including:

[0058] The network device acquires first information, which indicates the remaining effective time of satellite auxiliary information; the network device determines a first time period based on the first information, the first time period is used for the terminal device to perform GNSS measurements, and the first time period does not overlap with a second time period, the second time period is used for the terminal device to reread system information, the system information including satellite auxiliary information; the network device sends second information to the terminal device, the second information indicating the first time period.

[0059] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the end time of the first time period is before the start time of the second time period.

[0060] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the start time of the first time period is after the end time of the second time period.

[0061] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first information is also used to indicate a reference time point for the remaining effective time of the satellite-assisted information.

[0062] Sixthly, a communication method is provided, comprising:

[0063] The terminal device performs GNSS measurements in a first time period, the end time of which is before a preset time, the preset time being the end time when the first cell can provide services to the terminal device; the terminal device switches from the first cell to the second cell after the end time of the first time period.

[0064] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the time interval between the end of the first time period and the preset time is greater than or equal to a preset threshold.

[0065] Seventhly, a communication method is provided, comprising:

[0066] The network device determines a first time period based on a preset time; wherein the end time of the first time period is before the preset time, the first time period is used for the terminal device to perform GNSS measurements, and the preset time is the end time when the first cell can provide services to the terminal device; the network device sends the information of the first time period to the terminal device.

[0067] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the time interval between the end of the first time period and the preset time is greater than or equal to a preset threshold.

[0068] In conjunction with the seventh aspect, in certain implementations of the seventh aspect, the network device determines a first time period based on a preset time, including:

[0069] When the preset time is before the GNSS information expires, and the interval between the preset time and the GNSS information expiration time is less than a threshold, the network device determines the first time period based on the preset time.

[0070] In conjunction with the seventh aspect, in certain implementations of the seventh aspect, the network device determines a first time period based on a preset time, including:

[0071] When the preset time is after the GNSS information has expired, and the interval between the preset time and the GNSS information expiration time is less than a threshold, the network device determines the first time period based on the preset time.

[0072] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the threshold is the time required to perform GNSS measurements.

[0073] Eighthly, a communication method is provided, comprising:

[0074] The terminal device acquires information from the first time period and information from the second time period; the terminal device performs GNSS measurements in the first time period; the terminal device performs a handover from the first cell to the second cell in the second time period, wherein the end time of the second time period is after the end time of the first time period.

[0075] In conjunction with the eighth aspect, in certain implementations of the eighth aspect, the terminal device acquires information from the first time period and information from the second time period, including:

[0076] The terminal device receives information from the network device during the first time period and information during the second time period.

[0077] In conjunction with the eighth aspect, in certain implementations of the eighth aspect, the terminal device acquires information from the first time period and information from the second time period, including:

[0078] The terminal device receives information from the network device during the first time period and information during the third time period, wherein the end time of the third time period is before the end time of the first time period, and the third time period is used by the terminal device to perform the process of handing over from the first cell to the second cell; the terminal device also receives information from the network device during the second time period, which is used to update the third time period.

[0079] In conjunction with the eighth aspect, in certain implementations of the eighth aspect, the terminal device acquires information from the first time period and information from the second time period, including:

[0080] The terminal device receives information from the network device during a third time period, the end time of which is before the end time of the first time period. The third time period is used by the terminal device to perform a handover from the first cell to the second cell. The terminal device sends information from the first time period to the network device. The terminal device receives information from the network device during a second time period, the second time period being used to update the third time period.

[0081] Ninth aspect, a communication method is provided, comprising:

[0082] The network device acquires information for a first time period and information for a third time period. The first time period is used for the terminal device to perform GNSS measurements, and the third time period is used for the terminal device to perform the process of handing over from the first cell to the second cell. The network device determines that the end time of the third time period is before the end time of the first time period. The network device sends information for a second time period to the terminal device. The second time period is used to update the third time period, and the end time of the second time period is after the end time of the first time period.

[0083] In conjunction with the ninth aspect, in certain implementations of the ninth aspect, the network device acquires information from the first time period, including:

[0084] The network device receives information from the terminal device during the first time period.

[0085] Tenthly, a communication method is provided, comprising:

[0086] The terminal device receives information about the execution conditions for conditional switching from the network device, wherein the execution conditions for conditional switching include valid GNSS information; if the execution conditions for conditional switching are met, the terminal device performs conditional switching.

[0087] In conjunction with aspect ten, in some implementations of aspect ten, the validity of the GNSS information includes: the remaining validity time of the GNSS information is greater than or equal to a preset threshold.

[0088] Eleventhly, a communication device is provided. In one possible implementation, the communication device may include modules or units that perform the methods / operations / steps / actions described in the first to tenth aspects. The modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0089] In a twelfth aspect, a communication device is provided, comprising a communication interface and a processor, the communication interface being used to output and / or input signals, and the processor being used to execute a computer program or instructions stored in a memory, causing the communication device to perform the methods of the first to tenth aspects.

[0090] Optionally, the memory may be included in the communication device. In one way, the memory may be set separately from the processor; in another way, the memory may be located in the processor and integrated with the processor.

[0091] Alternatively, the memory can also be coupled to the processor outside the communication device.

[0092] In a thirteenth aspect, a computer-readable storage medium is provided, including a computer program that, when run on a computer, causes the computer to perform the method in any of the possible implementations of the first to tenth aspects.

[0093] In a fourteenth aspect, a chip or chip system is provided, the chip or chip system including processing circuitry and input / output interfaces, the processing circuitry being used to perform the method in any of the possible implementations of the first to tenth aspects.

[0094] In the fifteenth aspect, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when executed, causes a computer to perform a method in any of the possible implementations of the first to tenth aspects.

[0095] In a sixteenth aspect, a communication system is provided, including a network device and a terminal device. The terminal device is used to perform the method in any possible implementation of the first aspect.

[0096] Alternatively, the terminal device may be used to execute the method in any of the possible implementations of the second aspect.

[0097] Alternatively, the terminal device may be used to execute the method in any of the possible implementations of the third aspect.

[0098] Alternatively, the terminal device may execute the method in any of the possible implementations of the fourth aspect, and the network device may execute the method in any of the possible implementations of the fifth aspect.

[0099] Alternatively, the terminal device may be used to execute the method in any of the possible implementations of the sixth aspect, and the network device may be used to execute the method in any of the possible implementations of the seventh aspect.

[0100] Alternatively, the terminal device may be used to execute the method in any possible implementation of the eighth aspect, and the network device may be used to execute the method in any possible implementation of the ninth aspect.

[0101] Alternatively, the terminal device may be used to execute the method in any of the possible implementations of aspect ten. Attached Figure Description

[0102] Figure 1 The communication system to which this application applies is shown.

[0103] Figure 2 This is a schematic diagram of a stationary cell.

[0104] Figure 3 This is a schematic diagram of a mobile cell.

[0105] Figure 4 This is a schematic diagram of TA.

[0106] Figure 5 A method proposed in this application is shown.

[0107] Figure 6 A method proposed in this application is shown.

[0108] Figure 7 A method proposed in this application is shown.

[0109] Figure 8 A method proposed in this application is shown.

[0110] Figure 9 A method proposed in this application is shown.

[0111] Figure 10 A method proposed in this application is shown.

[0112] Figure 11 A method proposed in this application is shown.

[0113] Figure 12 A schematic block diagram of the communication device provided in this application.

[0114] Figure 13 A schematic block diagram of the communication device provided in this application. Detailed Implementation

[0115] The technical solutions of this application embodiment can be applied to various 3rd generation partnership project (3GPP) communication systems, such as: long term evolution (LTE) systems, such as LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, 5th generation (5G) communication systems, and future evolution communication systems, such as: 6th generation (6G) communication systems, etc.

[0116] Figure 1 The present application illustrates a communication system to which access network equipment, core network equipment, and terminal equipment are included.

[0117] To facilitate understanding, the terminology used in this application will be explained first.

[0118] (1) Network equipment

[0119] The network device in this application embodiment can be an access network device or a core network device.

[0120] Access network equipment refers to radio access network (RAN) nodes (or equipment) that connect terminal equipment to a wireless network; it can also be called a base station. This base station can be a next-generation base station (gNB), an evolved Node B (eNB or eNodeB) in an LTE system, a base station in a 5G system, or a next-generation base station in a 6G system or subsequent communication systems.

[0121] The embodiments of this application do not limit the specific technology and equipment form used in the base station. For example, it can be: a macro base station, a micro base station (also called a small station), a relay station, an access point, a transmitting and receiving point (TRP), a transmitting point (TP), a mobile switching center, network equipment in a non-terrestrial network (NTN) communication system (i.e., it can be deployed on a high-altitude platform or satellite), and sidelink scenarios (e.g., device-to-device (D2D), vehicle-to-everything (V2X)). The network equipment can be a module or unit that performs some of the functions of the base station; for example, it can be a central unit (CU) or a distributed unit (DU). The CU and DU each perform a portion of the base station's protocol stack functions. Furthermore, the functions of the CU can be implemented by multiple entities; for example, the functions of the CU's control plane (CP) and user plane (UP) can be separated to form a CU control plane (CU-CP) and a CU user plane (CU-UP). For example, CU-CP and CU-UP can be implemented by different functional entities and connected through an E1 interface. CU-CP and CU-UP can be coupled with DU.

[0122] Core network equipment refers to the equipment in the core network (CN) that provides service support for terminal equipment. Examples of core network equipment include: Access and Mobility Management Function (AMF) entities, Session Management Function (SMF) entities, and User Plane Function (UPF) entities.

[0123] (2) Terminal equipment

[0124] The terminal equipment in this application refers to a terminal equipment with relatively weak capabilities. Specifically, the GNSS acquisition module and communication module of this type of terminal equipment cannot work simultaneously, thus requiring dedicated time for GNSS location information acquisition.

[0125] These terminal devices can be various devices that provide voice and / or data connectivity to users, and can also be referred to as terminals, user equipment (UE), mobile stations, mobile terminals, etc. Terminal devices can be widely used in various scenarios, such as customer-premises equipment (CPE), point-of-sale (POS) machines, sidelink scenarios (e.g., D2D, V2X), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, drones, in-vehicle equipment, aerospace equipment, etc. In the embodiments of this application, the chip used in the above-mentioned devices can also be referred to as a terminal.

[0126] (3)NTN

[0127] NTN communication boasts advantages such as wide coverage, long communication distance, high reliability, high flexibility, and high throughput. Unaffected by geographical environment, climate conditions, or natural disasters, it has been widely applied in fields such as aviation, maritime, and military communications. Non-terrestrial network equipment includes aerial network equipment such as satellites, drones, and high altitude platform station (HAPS) communication systems. Introducing NTN into 5G can improve the performance of communication systems. In NTN systems, satellite communication architectures fall into two main categories: transparent relay architecture, where the satellite acts only as a relay or amplifier, performing functions such as RF filtering and amplification to regenerate the signal; and regenerative architecture, where the satellite can act as a gNB, distributed unit (DU), or relay. This relay function differs from the first type; it is no longer simply a relay but also includes signal processing capabilities.

[0128] (4) Fixed cell and moving cell

[0129] Generally speaking, the higher the satellite's orbit, the larger its coverage area, but the longer the communication delay. According to orbital altitude, satellites can be divided into: (1) Low Earth Orbit (LEO): orbital altitude of 160-2000km; (2) Middle Earth Orbit (MEO): orbital altitude of 2000-35786km; (3) Geostationary Orbit (GEO): orbital altitude of 35786km; GEO satellites are also called geostationary satellites. The satellite's motion speed is the same as the Earth's rotation system, so the satellite remains stationary relative to the ground. Correspondingly, the cell of a GEO satellite is also stationary.

[0130] MEO and LEO satellites are collectively referred to as non-geostationary Earth orbit (NGSO) satellites. Taking LEO satellites as an example, LEO satellites move relatively quickly relative to the ground, therefore the coverage area they provide also moves. LEO satellites project two types of cells onto the ground: fixed cells and moving cells.

[0131] Stationary cell: This refers to a cell projected onto the ground that is stationary relative to the ground. NGSO satellites overhead adjust their beam direction to cover the same location on the ground. When one NGSO satellite can no longer provide coverage, another NGSO satellite takes over. For example... Figure 2 As shown, the mapping method of stationary cells refers to the fact that the location of the cells on the ground is fixed, and the moving satellites form these cells by adjusting their beams. For example, at time T1: cells 1 and 2 are covered by the beam of gNB1, and cells 3 and 4 are covered by the beam of gNB2; at time T2: although gNB1 and gNB2 have moved to the left, they can still adjust their beams to ensure coverage of cells 1, 2, 3, and 4; at time T3: compared to time T1, gNB1 and gNB2 have moved a sufficient distance, and gNB1 can no longer provide coverage for cell 2 by adjusting its beam, and gNB2 can no longer provide coverage for cell 4 by adjusting its beam. At this time, gNB2 can provide coverage for cell 2, and gNB3 can provide coverage for cell 4.

[0132] Moving cell: This refers to a cell projected onto the ground that moves along with the NGSO satellite, while the beam direction of the NGSO satellite remains unchanged during the movement. For example... Figure 3 As shown, the mapping method of a ground mobile cell means that the moving satellite does not dynamically adjust its beam direction; the beam generated by the moving satellite moves on the ground as the satellite moves. For example: at time T1: (e.g.) Figure 2The area shown is covered by cells 1, 2, 3, and 4 of gNB1 and gNB2, while at time T3, the area is covered by cells 2, 3, 4, and 5 of gNB1, gNB2, and gNB3.

[0133] (5) Internet of Things (IoT) NTN

[0134] IoT NTN refers to providing communication services for IoT devices through the NTN network.

[0135] IoT devices are categorized into narrowband (NB) IoT devices and enhanced machine-type communication (eMTC) devices. NB IoT devices are used in intermittent, lightweight communication scenarios with low data usage, such as most sensors in the IoT. eMTC devices are primarily used in machine communication scenarios and require higher data rates compared to NB IoT devices. Similar to New Radio (NR), IoT devices also require GNSS location information to access the network, for example, for time and frequency synchronization. The system architecture and operating mode of IoT NTN are the same as NR NTN. The difference lies in the fact that IoT NTN terminal devices have weaker capabilities; the GNSS acquisition module and communication module cannot operate simultaneously. Therefore, IoT NTN devices require dedicated time for GNSS location information acquisition.

[0136] (6)TA

[0137] A key characteristic of uplink transmission is that uplink transmissions from different terminal devices within the same cell do not interfere with each other. To ensure orthogonality of uplink transmission and avoid intra-cell interference, network devices require that signals from different terminal devices originating from the same subframe but using different frequency domain resources arrive at the network device at essentially the same time. As long as the network device receives the uplink data sent by the terminal device within the cyclic prefix range, it can correctly decode the uplink data. Therefore, uplink synchronization requires that the arrival times of signals from different terminal devices within the same subframe all fall within the cyclic prefix range.

[0138] To ensure time synchronization on the receiving side (network device side), an uplink timing advance mechanism is introduced. By appropriately controlling the offset of each terminal device, the network device can control the arrival time of uplink signals from different terminal devices. For terminal devices farther from the network device, due to the larger transmission delay, uplink data must be sent earlier than that of terminal devices closer to the network device.

[0139] In NTN scenarios, TA is calculated by the terminal device based on its own GNSS location information and satellite location information (satellite location information can be obtained from ephemeris information). For example... Figure 4 As shown, the Transmission Time (TA) in NTN consists of two parts: one is the transmission delay from the terminal device to the satellite (represented by the service link RTT), and the other is the transmission delay from the satellite to the reference point (RP) (represented by the Common TA). The Common TA is calculated by the network side and sent to the terminal device, while the service link RTT is calculated by the terminal device based on GNSS location information and satellite location information. The terminal device calculates the total TA (i.e., Figure 4 T in TA Then the total TA is reported to the network.

[0140] (7) Obtain GNSS location information

[0141] Taking IoT devices as an example, since IoT devices do not support the simultaneous operation of the GNSS acquisition module and the communication module, IoT devices cannot communicate during the GNSS acquisition process.

[0142] The methods for obtaining GNSS location information include, but are not limited to, the following three:

[0143] 1) Configure a preset time period for IoT devices to acquire GNSS location information. For example, the preset time period can be a GAP, which is a dedicated preset time period during which the IoT device only acquires GNSS location information and the network device does not schedule the IoT device.

[0144] For example, network devices can configure this preset time period for IoT devices.

[0145] For example, IoT devices can configure this preset time period for themselves.

[0146] 2) After an IoT device loses uplink synchronization, a radio link failure (RLF) is triggered. During the RLF recovery period, the IoT device acquires GNSS location information. The preset time period is either the period required for RLF recovery or the period required for GNSS location information acquisition.

[0147] 3) Configure a timer for the IoT device. The timer length is configured by the network device, and the timer is started by the IoT device. The timing of starting the timer can be determined by the IoT device itself or specified by the network device. After the timer expires, the IoT device triggers GNSS measurement to obtain GNSS location information. Unlike 2), RLF is not triggered here.

[0148] (8) Conditional handover (CHO)

[0149] To prevent link quality degradation at the source base station from hindering normal signaling communication between the terminal device and the source base station, existing technologies propose a Call-Only (CHO) mechanism. Specifically, when the link quality between the source base station and the terminal device is relatively good, the source base station sends CHO configuration information to the terminal device. This configuration information includes CHO trigger conditions and candidate cell information. Upon receiving this configuration information, the terminal device determines whether the candidate cell meets the handover trigger conditions and selects a candidate cell that meets the conditions as the target cell. Then, the terminal device initiates random access to the target cell. After successful random access, the terminal device sends a Radio Resource Control (RRC) reconfiguration completion message to the base station to which the target cell belongs (i.e., the target base station), notifying the target base station that the conditional handover is complete.

[0150] CHOs can be categorized into time-based CHOs, location-based CHOs, and measurement-based CHOs.

[0151] Among them, time-based CHO is the time window configured by the base station for the terminal device to perform handover, and the terminal device evaluates the handover execution conditions and completes the handover within the time window; distance-based CHO is the distance threshold configured by the base station for the terminal device, and the handover is completed when the distance threshold is met; measurement-based CHO is the terminal device evaluating whether to perform handover based on the reference signal receiving power (RSRP).

[0152] Both distance-based and time-based Call for Responses (CHOs) rely on the terminal device's location; therefore, the terminal device's GNSS location information is crucial for CHO execution. Furthermore, both distance-based and time-based CHOs require handover assessment based on the reference signal receiving power (RSRP). During gap periods or GNSS measurements, the terminal device cannot perform measurements, and therefore cannot make CHO execution decisions based on the latest RSRP, affecting successful CHO execution. As satellites move, the Terminal Aspect (TA) changes during GNSS measurements, potentially triggering a Time-Based Response (TAR). Since the terminal device's location may have changed, the GNSS location information may be inaccurate, and the TAR may report inaccurate TA values ​​to the network device. Inaccurate TA values ​​can cause the terminal device to lose synchronization with the network device.

[0153] Regarding this issue, such as Figure 5 As shown, this application embodiment provides a communication method 200, which includes:

[0154] S201, The terminal device acquires GNSS location information within a preset time period.

[0155] For ease of description, this GNSS location information will be referred to as GNSS location information #A.

[0156] The first moment is the time when the terminal device begins to acquire GNSS location information #A, and the second moment is the time when the terminal device completes the acquisition of GNSS location information #A.

[0157] It is understood that this preset time period is the period during which the terminal device performs GNSS measurements and acquires GNSS location information #A. This preset time period can also be the GAP mentioned above. When the preset time period is the GAP, the first moment can also be the start time of the GAP; the second moment can also be the end time of the GAP. The terminal device can perform GNSS measurements based on any of the following:

[0158] (1) The network device can send a first message to the terminal device, which includes the preset time period. The terminal device is configured to perform GNSS measurements within the preset time period according to the first message sent by the network device, and obtain GNSS location information #A. The preset time period can be determined based on the time required to obtain the GNSS location information, and the length of the preset time period should not be shorter than the time required to obtain the GNSS location information. Optionally, the time required to obtain the GNSS location information can be determined by the terminal device and reported to the network. The preset time period can be configured to the terminal device through MAC CE; or it can be configured to the terminal device through RRC signaling, such as the RRC Reconfiguration message.

[0159] The first message may also include the start time of a preset time period, or the start time for the terminal device to perform GNSS measurements. Optionally, the terminal device can start GNSS measurements according to the start time configured by the network side and stop GNSS measurements before the end of the preset time period. Optionally, the terminal device can also determine the start time of the measurement itself. Optionally, when the terminal device determines the start time of the GNSS measurement, it reports the start time to the network side. For example, the network side uses the start time to align the preset time period with the terminal device and does not schedule the terminal device within the preset time period.

[0160] (2) The terminal device itself can configure the preset time period. The terminal device performs GNSS measurements within the preset time period according to its own configuration to obtain GNSS location information #A. The preset time period can be determined based on the time required to obtain the GNSS location information, and the length of the preset time period should not be shorter than the time required to obtain the GNSS location information. The terminal device can determine the GNSS measurement start time itself. Optionally, the terminal device can report the start time and / or the length of the preset time period to the network side. For example, the network side uses the start time and the length of the preset time period to align the preset time period with the terminal device and does not schedule the terminal device within the preset time period.

[0161] (3) The terminal device triggers an RLF and performs GNSS measurements during the RLF recovery period to obtain GNSS location information #A. Optionally, the timer duration for waiting for the RLF recovery should not be shorter than the time required to obtain the GNSS location information.

[0162] (4) The network device can configure a preset duration for the timer to the terminal device. The terminal device starts the timer. The timing of starting the timer can be determined by the terminal device itself or specified by the network device. If the timer expires and no instruction to acquire GNSS information is received from the network device, the terminal device will perform GNSS measurement within the preset time period to acquire GNSS location information #A.

[0163] To address the above problems, as a first solution, the method further includes S202-1:

[0164] S202-1, between the first and second time points, the terminal device is prohibited from triggering TAR.

[0165] In other words, the terminal device is prohibited from triggering TAR during GNSS measurements. Alternatively, the terminal device is prohibited from triggering TAR during GAP (Gap). For example, it can be stipulated that the terminal device does not trigger TAR during GNSS measurements. Or, it can be stipulated that the terminal device does not trigger TAR during GAP. Regarding this first solution, optionally, after the second time point, the terminal device determines whether to trigger TAR based on a first change quantity. The first change quantity is the change of the second TA relative to the first TA. Here, the first TA is the latest TA reported by the terminal device to the network device before the preset time period (or, in other words, the last TA reported by the terminal device to the network device before this time period, or, the first TA is the TA currently maintained / used by the network side, or, the first TA is the TA last reported by the terminal device to the network device). The second TA is determined based on the GNSS location information #A. The first and second TAs will not be elaborated further below.

[0166] Optionally, the terminal device may trigger TAR when the first change is greater than or equal to a preset threshold.

[0167] When the first change is less than the preset threshold, the terminal device does not trigger TAR.

[0168] According to the embodiments of this application, by prohibiting the triggering of TAR during GNSS measurements, it is possible to prevent the terminal device from reporting inaccurate TA to the network device, thereby solving the above-mentioned problem at its root.

[0169] To address the aforementioned issues, as a second solution, the method further includes S202-2:

[0170] S202-2, After obtaining GNSS location information #A, the terminal device triggers TAR.

[0171] Equivalently, the terminal device can trigger TAR after the GAP ends; or the terminal device can trigger TAR after the preset time period ends.

[0172] The following example illustrates the S202-2 method, using "after obtaining GNSS location information #A, the terminal device triggers TAR".

[0173] Method 1:

[0174] After the terminal device acquires GNSS location information #A, it triggers TAR regardless of whether the first change is greater than or equal to a preset threshold or less than a preset threshold. The first change is the change of the second TA relative to the first TA. For an explanation of the first and second TA, please refer to the above text.

[0175] In other words, in this method 1, after the terminal device obtains the GNSS location information #A, it does not need to determine the change of the second TA relative to the first TA and triggers TAR unconditionally.

[0176] Method 2:

[0177] After acquiring GNSS location information, the terminal device determines a first change, which is the change in the second TA relative to the first TA. For an explanation of the first and second TA, please refer to the above text.

[0178] Furthermore, the terminal device will only trigger TAR if the first change is greater than or equal to the preset threshold.

[0179] In other words, in this method 2, the terminal device needs to determine the amount of change of the second TA relative to the first TA.

[0180] It should be noted that, equivalently, "after obtaining GNSS location information #A" can also be expressed as "after the GAP ends", or "after the preset time period ends".

[0181] This method ensures that the Reporting Transaction (TA) on the network side is updated in a timely manner. The following examples describe the process of updating the reported TA in various scenarios using this method.

[0182] For ease of description, a TAR triggered by the terminal device between the first time and the second time is denoted as the first TAR, and a TAR triggered by the terminal device after the second time is denoted as the second TAR. For example, the second TAR can be triggered between the second time and the end time of the preset period, or it can be triggered after the end time of the preset period, without restriction.

[0183] The first TAR is used to report the third TA, and the second TAR is used to report the second TA. The second TA is obtained based on GNSS location information #A.

[0184] In the first scenario, both the first and second TARs are triggered. The terminal device assembles packets based on both the third and second TAs. The terminal device sends a MAC CE report to the network device using the TA obtained from the second TA, but does not send a MAC CE report using the TA obtained from the third TA. In other words, in this scenario, the first TAR is not completed; that is, the terminal device does not report the third TA to the network device.

[0185] In the second scenario, the terminal device does not assemble packets based on the third TA, but only on the second TA. For example, within a preset time period, there is no uplink grant, or no uplink resources (e.g., uplink shared channel (UL-SCH) resources are unavailable). That is, the terminal device does not complete packet assembly within the preset time period. After the preset time period, the terminal device assembles packets based on the second TA. In other words, in this case, the first TAR is not completed; that is, the terminal device does not report the third TA to the network device.

[0186] In the third scenario, the terminal device completes the first TAR, meaning it reports the third TA to the network device. After the second TAR is triggered, the second TA is subsequently reported to the network device as well. In this scenario, according to existing technology, the terminal device determines whether to trigger the second TAR based on the first change value (described above). However, existing technology may prevent erroneous TAs from being updated for a period of time. For example, after acquiring GNSS location information #A, the third TA has not yet been reported to the network when the first change value is evaluated, so the first change value is evaluated based on the first TA. If the second TAR is not forcibly (or unconditionally) triggered at this time...

[0187] In a TAR (True Anchor) mechanism, the terminal device will not trigger a second TAR if the change in the second TA (Transmission Attribute) relative to the first TA is less than a preset threshold. After the third TA is reported to the network device, the network device will use the erroneous TA (third TA) until the next TA update. With this method, even if the third TA is reported to the network device, the second TA will soon be reported as well, thus ensuring timely updates to the TA at the network device.

[0188] In the fourth scenario, the first TAR is not triggered, meaning the terminal device does not trigger a TAR within the preset time period. After the GNSS location information #A is acquired, the TA is updated, at which point the second TAR is triggered, and the second TA is reported to the network device, updating the TA value maintained by the network device.

[0189] Therefore, after the terminal device obtains GNSS location information #A, it will trigger TAR regardless of whether the first change is greater than or equal to the preset threshold, or whether TAR is triggered during the preset time period.

[0190] It should be noted that in this application document, packet assembly is also described as TA reporting MAC CE generation, or MAC protocol data unit (PDU) generation.

[0191] To address the above issues, as a third solution, this method also includes S202-3:

[0192] S202-3, between the first and second time points, the terminal device triggers the first TAR. After acquiring GNSS location information #A, the terminal device determines whether to cancel the first TAR based on a first change amount. If the first change amount is less than a preset threshold, the terminal device cancels the first TAR.

[0193] The first TAR is used to report the third TA. The first change is the change in the second TA relative to the first TA. For an explanation of the first and second TA, please refer to the above.

[0194] It should be noted that, equivalently, the time between the first moment and the second moment can also be expressed as during the GAP period, or as within a preset time period.

[0195] Understandably, if the first change is less than a preset threshold, the terminal device does not trigger the second TAR, which is used to report the second TA.

[0196] In other words, if the first change is less than the preset threshold, the first TAR is not completed, meaning that the terminal device does not report the third TA to the network device.

[0197] To address the above problems, as a fourth solution, this method also includes S202-4:

[0198] S202-4, Between the first and second time points, the terminal device is prohibited from generating TA to report MAC CE. The TA to report MAC CE is used to report TA.

[0199] It should be noted that, equivalently, the time between the first moment and the second moment can also be expressed as during the GAP period, or as within a preset time period.

[0200] In this embodiment of the application, the terminal device is prohibited from generating TA to report MAC CE between the first time and the second time (or within a preset time period). For example, the protocol may stipulate that the terminal device is prohibited from generating TA to report MAC CE during GNSS measurement (or within a preset time period). Optionally, the protocol may also stipulate that the terminal device is prohibited from using UL-SCH resources and from triggering scheduling requests between the first time and the second time (or expressed as within a preset time period, or during the GAP); or, it may be expressed as: UL-SCH resources are unavailable between the first time and the second time (or within a preset time period), and triggering scheduling requests is prohibited during the preset time period.

[0201] Regarding S202-4, between the first and second time points, the terminal device may or may not trigger the first TAR. The first TAR is used to report the third TA.

[0202] If the first TAR is triggered, since the terminal device is prohibited from generating a TA to report a MAC CE between the first and second moments, it will not generate a TA to report a MAC CE based on the third TA. In other words, the first TAR is not completed, meaning the terminal device does not report the third TA to the network device.

[0203] After obtaining GNSS location information #A, the terminal device can determine the second TA based on GNSS location information #A. It's understandable that the terminal device uses the latest TA when generating the TA to report the MAC CE. Since the second TA is the latest TA compared to the third TA, the terminal device generates the TA to report the MAC CE based on the second TA, and does not generate the TA to report the MAC CE based on the third TA. Therefore, the second TA is ultimately reported to the network device.

[0204] Optionally, the terminal device can determine a first change amount. When the first change amount is greater than or equal to a preset threshold, the terminal device generates a TA based on the second TA and reports it to MAC CE; otherwise, the first TAR is canceled. For a description of this first change amount, please refer to the above.

[0205] Furthermore, as another scenario, the terminal device triggers a TAR before a preset time period, but because the terminal device cannot perform reporting within the preset time period, the corresponding TA value is not reported to the network. Since the accuracy of the TA obtained by the terminal device decreases the closer to the preset time period, the unreported TA value is also considered inaccurate and should not be reported to the network side. Therefore, the aforementioned first time to second time period can be extended to a third time to second time period, where the third time period is before the first time period. Moreover, the time interval between the third time period and the first time period can be pre-configured.

[0206] In other words, in response to this situation, the first solution mentioned above can be extended to: the terminal device is prohibited from triggering TAR between the third time and the second time.

[0207] The third solution described above can be extended as follows: Between the third moment and the second moment, the terminal device triggers the first TAR. After acquiring the GNSS location information #A, the terminal device determines whether to cancel the first TAR based on the first change amount. If the first change amount is less than a preset threshold, the terminal device cancels the first TAR.

[0208] The fourth solution mentioned above can be extended to: between the third time and the second time, the terminal device is prohibited from generating TA to report MAC CE, and the TA to report MAC CE is used to report TA.

[0209] The second issue addressed in this application is as follows:

[0210] Currently, the CHO triggering mechanism for terminal devices within a preset time period is not perfect. On the one hand, the current CHO triggering mechanism does not specify whether a terminal device can trigger a CHO within a preset time period. On the other hand, since GNSS information and RSRP are not updated during the preset time period, the current CHO triggering mechanism does not specify whether the corresponding information before or after the update should be used to assess whether the triggering conditions are met if a CHO is triggered within the preset time period.

[0211] Regarding this issue, such as Figure 6 As shown, this application proposes method 300. Specifically, method 300 includes the following steps.

[0212] S301, The terminal device acquires the first GNSS location information within a preset time period.

[0213] The process of obtaining the first GNSS location information can be referred to in S201.

[0214] S302, the terminal device determines whether to trigger CHO within a preset time period.

[0215] The following section provides a detailed explanation of S302 in different scenarios.

[0216] Scenario 1:

[0217] The terminal device determines that CHOs should not be triggered during a preset time period. For example, the protocol can specify that the terminal device should not trigger CHOs during this preset time period.

[0218] The phrase "terminal devices are prohibited from triggering CHOs during a preset time period" can also refer to the terminal devices not evaluating CHO triggering conditions during that preset time period. For example, not evaluating CHO execution based on outdated GNSS location information and / or RSRP during the preset time period.

[0219] According to the embodiments of this application, since the reliability (or accuracy) of the GNSS location information or RSRP of the terminal device is low during a preset time period, if the terminal device evaluates whether to trigger a CHO based on the low reliability of the GNSS information or RSRP, it may lead to inaccurate handover timing (handover performed too early or too late), or handover performed under conditions where handover is not possible (for example, the actual RSRP of the target cell is poor, and the terminal device cannot successfully handover to the target cell). Therefore, the terminal device can prohibit triggering CHO during this preset time period.

[0220] Scenario 2:

[0221] The terminal device acquires the first GNSS location information within a preset time period, and the moment when it begins acquiring the first GNSS location information is called the first moment, and the moment when the terminal device completes acquiring the first GNSS location information is called the second moment.

[0222] The terminal device determines that it is permitted to trigger a CHO based on the first GNSS location information after the second time point. For example, it can be specified in the protocol that the terminal device can trigger a CHO after the GNSS measurement is completed.

[0223] According to an embodiment of this application, after GNSS measurement is completed, first GNSS location information (i.e., updated GNSS location information) is obtained. At this time, the preset time period may not have ended yet. The terminal device can use the first GNSS location information to assess in advance whether a CHO (Confirmation of Hazard) is triggered before the preset time period ends, thereby helping the terminal device to switch to the target network device in a timely manner.

[0224] Scenario 3:

[0225] The terminal device determines that CHO can be triggered during a preset time period.

[0226] In this situation, the information used by the terminal device to determine whether to trigger a CHO may differ depending on the scenario. Specifically, it can be divided into 6 scenarios as shown in Table 1 below.

[0227] Table 1

[0228] Fixed cell Scene #1 Scene #2 Scene #3 Moving cell Scene #4 Scene #5 Scene #6

[0229] In this case 3, regarding scenario 1:

[0230] A terminal device performs a CHO (Content Hitch) to switch from a source network device to a target network device. The terminal device can determine the remaining service duration, which is the remaining time the source network device can provide service to the terminal device.

[0231] Furthermore, if the remaining service duration is less than a preset threshold, the terminal device determines that a CHO (Confirmation of Hazard) can be triggered based on the second GNSS location information and / or the first RSRP (Real-Time Perimeter) within a preset time period. Both the second GNSS location information and the first RSRP were acquired by the terminal device before the preset time period. In other words, at this time, the terminal device can evaluate whether to execute a CHO based on outdated GNSS location information and / or outdated RSRP.

[0232] Alternatively, if the remaining service duration exceeds a preset threshold, the terminal device determines that a CHO (Confirmation of Hazard) can be triggered based on the first GNSS location information within a preset time period. In other words, if the remaining service duration exceeds the preset threshold, the terminal device can wait until the GNSS measurement is completed and then assess whether to trigger a CHO based on the first GNSS location information (i.e., the updated GNSS location information).

[0233] Alternatively, if the remaining service duration exceeds a preset threshold, the terminal device determines that a CHO can be triggered based on the second RSRP after a preset period. In other words, if the remaining service duration exceeds the preset threshold, the terminal device can update the first RSRP after a preset period to obtain the second RSRP (i.e., the updated RSRP), and evaluate whether to trigger a CHO based on the second RSRP.

[0234] For scenario 2:

[0235] The information used by the terminal device to assess whether a CHO is triggered is the same as in Scenario 1, and will not be repeated here.

[0236] For scenario 3:

[0237] The terminal device can determine the remaining service duration, which is the remaining duration for which the source network device can provide services to the terminal device.

[0238] Furthermore, if the remaining service duration is less than a preset threshold, the terminal device determines whether to trigger a CHO based on the first RSRP within a preset time period. For an explanation of the first RSRP, please refer to Scenario 1 above.

[0239] Alternatively, if the remaining service duration exceeds a preset threshold, the terminal device determines whether to trigger a CHO based on a second RSRP after a preset time period. For an explanation of this second RSRP, please refer to Scenario 1 above.

[0240] For scenario 4:

[0241] The information used by the terminal device to assess whether a CHO is triggered is the same as in Scenario 1, and will not be repeated here.

[0242] For scenario 5:

[0243] The terminal device determines whether to trigger a CHO based on the second GNSS location information and / or the first RSRP during a preset time period. For an explanation of the second RSRP and the first RSRP, please refer to Scenario 1 above.

[0244] For scenario 6:

[0245] The terminal device determines whether to trigger a CHO based on the first RSRP during a preset time period. For an explanation of the first RSRP, please refer to Scenario 1 above.

[0246] S303, the terminal device executes the corresponding action based on the judgment result in S302.

[0247] According to the embodiments of this application, the CHO triggering mechanism of the terminal device during GNSS measurement has been further improved.

[0248] The third issue addressed in this application is as follows.

[0249] During the execution of radio link monitoring, cell selection, serving cell measurement, neighbor cell measurement, system information reading (or system message reading), or radio link reconstruction, the terminal device starts corresponding timers and performs corresponding operations when the timers expire. During the timer's execution, the terminal device or the network side may trigger GNSS measurements. For some specific terminal devices (e.g., IoT NTN terminal devices), the terminal device cannot simultaneously perform communication (or signaling / message transmission and reception) and GNSS measurement. If the terminal device performs GNSS measurements before the timer expires, its communication module cannot transmit or receive signaling / messages, causing the timer to expire. A timer expiration will result in the terminal device performing an incorrect action.

[0250] For example:

[0251] Example 1:

[0252] In the RLF-related process, if the terminal device loses synchronization with the network, the physical layer reports a synchronization failure indication to the upper layer. Further, if the terminal device receives N310 consecutive out-of-sync indications, it starts timer T310. If, before T310 expires (or "times out"), the terminal device receives N311 consecutive in-sync indications, it restores the radio link with the network; otherwise, radio link restoration fails, and the terminal device needs to perform cell reselection. Therefore, after T310 expires, the terminal device starts T311, during which it performs cell reselection. If the terminal device selects a cell before T311 expires, it starts T301 and simultaneously performs reselection to the target cell, i.e., sends an RRC re-establishment request to the network device. If the terminal device does not select a cell before T311 expires, it enters an idle state. If no RRC re-establishment response is received from the network before T301 times out, the terminal device enters an idle state.

[0253] As shown above, in the RLF-related process, the terminal device may start one or more timers. During the timer's execution, the terminal device needs to communicate, such as transmitting and receiving measurement signals, reference signals, or signaling. If the terminal device initiates GNSS measurement during RLF, for IoT NTN terminal devices, the terminal device cannot transmit or receive reference signals or signaling during GNSS acquisition. Therefore, the timer's stop condition cannot be met during GNSS acquisition. During or after GNSS measurement, the timer will expire, causing the terminal device to perform erroneous operations.

[0254] It should be noted that the GNSS acquisition period can also be equivalent to the GNSS measurement gap period. Connected terminal devices perform GNSS measurements during the configured gap period. The gap period is a time range determined by the network device or the terminal device.

[0255] For example, if the terminal device triggers GNSS measurements during T310 operation, it will be unable to receive synchronization instructions, causing T310 to expire.

[0256] For example, during T311 operation, if the terminal device triggers GNSS measurement, it will be unable to receive SIB messages and neighbor cell reference signals, and therefore will be unable to reselect the target cell, causing T311 to expire.

[0257] Example 2:

[0258] The reading of system information by terminal equipment is also affected by GNSS measurements.

[0259] For example, system information block (SIB) 31 contains satellite and synchronization-related information for the NTN serving cell, and SIB3x (the name of this SIB is not limited in this application) contains satellite and synchronization-related information for neighboring NTN cells. The satellite auxiliary information carried by SIB31 and SIB3x has a validity period; after the validity period expires, the terminal device will reread SIB31 and SIB3x. For example, the ephemeris information and CommonTA parameter carried in the above SIB messages have a validity period (ul-SyncValidityDuration). When the above information expires, it is necessary to reread SIB31 or SIB3x.

[0260] For example, T317 is used to monitor ephemeris information and the validity period of CommonTA. After T317 expires, the terminal device needs to reread SIB31 and start T318. If the terminal device still cannot read SIB31 after T318 expires, the terminal device executes the RLF-related procedures.

[0261] Therefore, if the terminal device performs GNSS measurements during the operation of T318, the terminal device will be unable to read SIB31, causing T318 to expire.

[0262] Understandably, similar issues exist for SIB3x as well.

[0263] Regarding the third question mentioned above, such as Figure 7 As shown, this application proposes a method 400. Specifically, method 400 includes the following steps.

[0264] S401, The terminal device starts the first timer. During the operation of the first timer, the terminal device needs to perform at least one of the following tasks: radio link monitoring, cell selection, serving cell measurement, neighbor cell measurement, system information reading, and radio link reconstruction.

[0265] In other words, the terminal device needs to communicate (or use the communication module) during the first timer operation. For example, the terminal device needs to transmit and receive measurement signals, or reference signals, or signaling.

[0266] For example, the first timer is a timer associated with the RLF. For instance, the first timer is any one of T310, T311, or T301.

[0267] For example, the first timer is a timer related to system information reading. For instance, the first timer is T318.

[0268] The first timer can be a timer that functions similarly to the timers listed above, and this application does not limit the name of the timer.

[0269] S402, When the terminal device starts GNSS measurement before the first timer expires, the terminal device does not run the first timer during the GNSS measurement, wherein the terminal device cannot perform any of the following tasks during the GNSS measurement: radio link monitoring, cell selection, serving cell measurement, neighbor cell measurement, system information reading, radio link reconstruction.

[0270] It should be noted that the GNSS measurement period can be extended to the GNSS measurement gap period, the GNSS measurement start can be extended to the GNSS measurement gap start, and the GNSS measurement end can be extended to the GNSS measurement gap end. These extensions apply to methods 400 to 800.

[0271] The following section explains how to initiate GNSS measurements using the terminal equipment.

[0272] Scenario 1:

[0273] The network device triggers GNSS measurements. The network device configures the time period for GNSS measurements to be performed to the terminal device (e.g., this time period can be denoted as time period #A). Accordingly, the terminal device receives information for time period #A. Further, the terminal device performs GNSS measurements based on the information for time period #A.

[0274] For example, a network device can send information about time period #A to a terminal device via RRC signaling. This information about time period #A may include the starting subframe number of time period #A and the length of time period #A.

[0275] Specifically, the terminal device can determine the time required for GNSS measurement and send this time as supplementary information to the network device. Furthermore, the network device can determine the length of time period #A based on the required GNSS measurement time. For example, the length of time period #A can be greater than the required GNSS measurement time. Additionally, the terminal device can send the remaining valid time of the GNSS information to the network device. The network device can determine the start and / or end time of time period #A based on the remaining valid time of the GNSS information. For example, the end time of time period #A may be before the end of the remaining valid time of the GNSS information. Further, the network device sends the information for time period #A to the terminal device via RRC signaling.

[0276] For example, a network device can send information about time period #A to a terminal device via MAC CE signaling. This information can include the start time of time period #A and its length. For instance, the start time of time period #A might be n+X, where n is the last subframe number the terminal device received from the MAC CE, and X is a predefined value or a value configured by the network device for the terminal device.

[0277] Scenario 2:

[0278] The terminal device itself triggers GNSS measurements and acquires GNSS location information during a certain time period (e.g., time period #B). At this time, the terminal device can determine the time required for the GNSS measurements, the length of which is the required time for the GNSS measurements. Optionally, the terminal device can send an indication message to the network device indicating that it has started GNSS measurements. Optionally, this indication message includes the time information for starting the GNSS measurements. Based on this indication message, the network device can align with the terminal device for time period #B. That is, the network device can know that the terminal device is conducting GNSS measurements during time period #B.

[0279] The following explains "the terminal equipment does not run the first timer during GNSS measurements".

[0280] Scenario 1:

[0281] Optionally, if the first timer is running before the GNSS measurement begins, the terminal device may pause the first timer and restart it after the GNSS measurement is completed.

[0282] Alternatively, after the GNSS measurement is completed, the terminal device can determine whether the conditions for starting the first timer are met. If the conditions for starting the first timer are met, the terminal device starts the first timer.

[0283] For example, the first timer is T310 associated with RLF, and the condition for the first timer to be turned on is that the terminal device receives N310 consecutive out-of-step instructions.

[0284] The terminal equipment clears the first counter before GNSS measurement begins. For example, during radio link monitoring, if the terminal equipment's higher layers receive a loss-of-synchronization indication reported by the physical layer, counter N310 starts counting. If the terminal equipment needs to perform GNSS measurement during the counting process, N310 needs to be cleared. If a loss-of-synchronization indication is still received after the GNSS measurement is completed, the loss-of-synchronization indication count needs to be restarted. T310 is only activated after N310 consecutive loss-of-synchronization indications are received.

[0285] Scenario 2:

[0286] Optionally, if the first timer is running before the GNSS measurement begins, the terminal device stops the first timer. After the GNSS measurement is completed, the terminal device starts the second timer. The first and second timers are of the same type, and the preset timeout duration of the first and second timers is the same.

[0287] For example, both the first timer and the second timer are timers T310 related to RLF. The preset timeout duration of the first timer can be a seconds, and the preset timeout duration of the second timer can also be a seconds.

[0288] Alternatively, after the GNSS measurement is completed, the terminal device can determine whether the conditions for starting the second timer are met. If the conditions for starting the second timer are met, the terminal device starts the second timer.

[0289] For example, the second timer is T311 associated with RLF, and the condition for the second timer to be turned on is that the terminal device has not received N311 consecutive synchronization instructions before T310 expires.

[0290] Scenario 3:

[0291] Optionally, if the first timer is running before the GNSS measurement begins, the terminal device stops the first timer. After the GNSS measurement is completed, the terminal device starts the second timer. The first and second timers are of the same type, and the preset timeout duration of the second timer is a first value, which is equal to the preset timeout duration of the first timer minus the running duration of the first timer.

[0292] For example, if the preset timeout duration of the first timer is a seconds and the first timer has been running for b seconds, then the first value = ab.

[0293] Alternatively, after the GNSS measurement is completed, the terminal device can determine whether the conditions for starting the second timer are met. If the conditions for starting the second timer are met, the terminal device starts the second timer. Please refer to the above for more information.

[0294] Scenario 4:

[0295] Optionally, if the first timer is running before the GNSS measurement begins, the terminal device stops the first timer and starts the second timer. The first and second timers are of the same type, and the preset timeout duration of the second timer is a second value, which is equal to the preset timeout duration of the first timer plus the duration required for the GNSS measurement and minus the running duration of the first timer.

[0296] For example, if the preset timeout duration of the first timer is a seconds, the duration required for GNSS measurement is b seconds, and the duration already run by the first timer is c seconds, then the second value = a + bc.

[0297] Alternatively, after the GNSS measurement is completed, the terminal device can determine whether the conditions for starting the second timer are met. If the conditions for starting the second timer are met, the terminal device starts the second timer. Please refer to the above for more information.

[0298] Scenario 5:

[0299] Optionally, if the first timer is running before the GNSS measurement begins, the terminal device stops the first timer and starts the second timer. The first and second timers are of the same type, and the preset timeout duration of the second timer is a third value, which is equal to the preset timeout duration of the first timer plus the duration required for the GNSS measurement.

[0300] For example, if the preset timeout duration of the first timer is a seconds and the duration required for GNSS measurement is b seconds, then the third value = a + b.

[0301] Situation 6:

[0302] Optionally, if the first timer is running before GNSS measurements begin, the terminal device may stop the first timer.

[0303] Optionally, the terminal device clears the first counter before GNSS measurement begins. For example, during radio link monitoring, if the terminal device's higher layers receive a loss-of-synchronization indication reported by the physical layer, counter N310 starts counting. If the terminal device needs to perform GNSS measurement during the counting process, N310 needs to be cleared. If a loss-of-synchronization indication is still received after the GNSS measurement is completed, the loss-of-synchronization indication needs to be counted again, and T310 is only activated after N310 consecutive loss-of-synchronization indications are received.

[0304] For example, during wireless link monitoring, when the higher layer of the terminal device receives a synchronization indication reported by the physical layer, N311 starts counting. If the terminal device needs to perform GNSS measurements during the counting process, N311 needs to be cleared. If a synchronization indication is still received after the GNSS measurement is completed, the synchronization indication needs to be counted again. Only after receiving N311 consecutive synchronization indications can it be determined that the terminal device's wireless link has been restored.

[0305] According to the method 400 proposed in this application, when the terminal device starts GNSS measurement before the first timer expires, the terminal device does not run the first timer during the GNSS measurement, thereby avoiding the timer expiration caused by GNSS measurement and reducing the possibility of the terminal device performing erroneous actions.

[0306] Regarding the third question mentioned above, for reading system information, such as Figure 8 As shown, this application also proposes a method 500. Specifically, method 500 includes the following steps:

[0307] S501, the terminal device obtains the first system information.

[0308] The first system information includes satellite auxiliary information, which includes at least one of the following: ephemeris information, satellite-to-reference point time delay parameters (i.e., common TA parameters), satellite auxiliary information validity duration (e.g., ntn-UlSyncValidityDuration), and the reference time corresponding to the satellite auxiliary information (e.g., epochTime).

[0309] S502, the terminal device sends the first information to the network device. Correspondingly, the network device receives the first information.

[0310] The first piece of information indicates the remaining validity period of the satellite assistance information obtained by the terminal device. The remaining validity period of the satellite assistance information refers to the time interval between the expiration time of the satellite assistance information and the reference time. For example, the remaining validity period of the satellite assistance information can be determined based on at least one of the following: the effective duration of the satellite assistance information, the reference time corresponding to the satellite assistance information, and the time since the satellite assistance information has been in effect. For instance, the remaining validity period of the satellite assistance information can be the effective duration of the satellite assistance information minus the time since the satellite assistance information has been in effect.

[0311] Optionally, the terminal may reacquire satellite auxiliary information after the remaining validity period of the satellite auxiliary information expires.

[0312] Optionally, the first information is also used to indicate a reference time point for the remaining valid time of the satellite auxiliary information.

[0313] S503, the network device determines the first time period based on the first information and the remaining valid time of the GNSS information.

[0314] The first time period is used for the terminal equipment to perform GNSS measurements, and the first time period does not overlap with the second time period. The second time period is used for the terminal equipment to reread system information.

[0315] For example, the end time of the first time period is before the start time of the second time period.

[0316] For example, the start time of the first time period is after the end time of the second time period.

[0317] S504, the network device sends the second information to the terminal device. Correspondingly, the terminal device receives the second information.

[0318] The second information indicates the first time period.

[0319] Optionally, the terminal device can perform GNSS measurements in the first time period based on the second information; the terminal device can also reread the system information in the second time period.

[0320] According to the method 500 proposed in this application, the time period for the terminal device to perform GNSS measurements does not overlap with the time period for rereading system information, thereby avoiding timeouts of related timers caused by GNSS measurements and reducing the possibility of the terminal device performing erroneous actions.

[0321] The fourth issue addressed in this application is now discussed.

[0322] If the remaining service time of a terminal device in its current serving cell (denoted as cell 1) is about to expire, the terminal device can perform a handover to cell 2. During the handover process, if the validity period of the GNSS information is also about to expire, the terminal device needs to perform GNSS measurements and update the GNSS information. That is, there is an overlap between the time period for GNSS measurements and the time period for handover. In this situation, if the terminal device performs GNSS measurements first, it may fail to successfully handover to cell 2 before the remaining service time of the current serving cell expires, resulting in handover failure. After a handover failure, the terminal device will reselect a cell for access. If the terminal device performs cell handover first, the validity period of the GNSS information may have expired after the handover, and using expired GNSS information will cause the terminal device to fail to synchronize successfully in cell 2.

[0323] It should be noted that, in this application, the remaining service time of a cell refers to the time when the cell stops providing service to the currently covered area or the end time of providing service to terminal devices. For example, for a quasi-Earth fixed cell in an NTN, the cell will broadcast this time, such as t-service.

[0324] Regarding this fourth question, such as Figure 9 As shown, this application proposes method 600. Specifically, method 600 includes the following steps:

[0325] S601, the network device determines the first time period according to the preset time.

[0326] The first time period ends before the preset time. The first time period is used for the terminal device to perform GNSS measurements. The preset time is the end time when the first cell can provide services to the terminal device. For example, the preset time can be denoted as t-service.

[0327] Optionally, the time interval between the end of the first time period and the preset time is greater than or equal to a preset threshold.

[0328] Optionally, if the preset time is before the current GNSS information expiration time of the terminal device, and the distance between the preset time and the GNSS information expiration time is less than a threshold, the network device determines a first time period, such that the end time of the first time period is before the preset time. Optionally, the threshold is the length of the GNSS measurement gap, or the threshold is the time required for the GNSS measurement reported by the terminal device. Optionally, the end time of the first time period is before the preset time.

[0329] Optionally, when the preset time is after the current GNSS information expiration time of the terminal device, and the distance between the preset time and the GNSS information expiration time is less than a threshold, the network device determines a first time period, such that the end time of the first time period is before the preset time, or the start time of the first time period is before the GNSS information expiration time. Optionally, the threshold is the length of the GNSS measurement gap, or the threshold is the time required for the GNSS measurement reported by the terminal device.

[0330] Optionally, the network device determines an appropriate end time for the first time period to ensure that the GNSS information of the terminal device is valid during the handover process from the first cell to the second cell.

[0331] S602, the network device sends an instruction to the terminal device to perform GNSS measurements.

[0332] Optionally, the indication information indicates information for the first time period. Accordingly, the terminal device receives the information for the first time period.

[0333] For example, a network device can send information about a first time period to a terminal device via RRC signaling. This information may include at least one of the following: the starting subframe number of the first time period and the length of the first time period.

[0334] For example, a network device can send information about a first time period to a terminal device via MAC CE signaling. This information may include at least one of the following: the start time of the first time period and the length of the first time period. For example, the start time of the first time period may be n+X, where n is the last subframe number received by the MAC CE, and X is a predefined value or a value configured by the network device.

[0335] For example, after receiving the instruction, the terminal device initiates GNSS measurements in the first time period according to the rules agreed upon with the network device in advance.

[0336] S603, the terminal equipment performs GNSS measurements in the first time period.

[0337] S604, optional, the terminal device switches from the first cell to the second cell after the end of the first time period.

[0338] It is understandable that the handover from the first cell to the second cell can be a normal handover, a conditional handover, or another form of handover, and this application does not impose any restrictions.

[0339] For example, the terminal device performs a handover from the first cell to the second cell between the end of the first time period and a preset time. Alternatively, the terminal device receives a handover command from the network device after the end of the first time period.

[0340] For example, the terminal device can perform the process of switching from the first cell to the second cell after a preset time.

[0341] For example, after the end of the first time period, the terminal device completes the process of switching from the first cell to the second cell.

[0342] According to the method 600 proposed in this application, when the remaining service time of the terminal device is close to the expiration time of the remaining valid time of the current GNSS, the network side needs to configure appropriate GNSS measurement for the terminal device so that the end time of the GNSS measurement is before the preset time, so that the GNSS information of the terminal device remains valid during the handover process, ensuring that the terminal device can access or synchronize with the target cell.

[0343] Regarding this fourth question, such as Figure 10 As shown, this application proposes a method 700. Specifically, method 700 includes the following steps:

[0344] S701, the terminal device obtains information for the first time period and information for the second time period.

[0345] The second time period ends after the end of the first time period. The first time period is used for the terminal equipment to perform GNSS measurements. The second time period is used for the terminal equipment to perform the handover from the first cell to the second cell. The second time period can also be understood as the time window for the terminal equipment to perform the handover. For example, the second time period can be a time window in a time-based conditional handover.

[0346] The following describes several ways for terminal devices to obtain information from the first time period and the second time period.

[0347] Method 1:

[0348] The network device configures the terminal device with information for the first time period and information for the second time period. Accordingly, the terminal device receives the information for the first time period and information for the second time period.

[0349] The t-service corresponding to the currently serving cell is within the second time period. The end time of the second time period is after the end time of the first time period.

[0350] Optionally, the length of the second time period is longer than the length of the first time period. Before the end time of the second time period minus the length of the first time period, the network device sends an instruction to the terminal device to perform GNSS measurements.

[0351] Optionally, you can configure the first time period and the second time period at the same time, or you can configure the first time period first and then the second time period, or you can configure the second time period first and then the first time period.

[0352] Optionally, the configuration can be configured for the second time period after the first time period configuration is sent to the terminal device, or configured for the first time period after the second time period configuration is sent.

[0353] Method 2:

[0354] Network devices configure information for a third time period to terminal devices. This third time period is used by the terminal device during the handover process from the first cell to the second cell. For example, the third time period is a time window in time-based conditional handover.

[0355] The network equipment configures the first time period information to the terminal equipment, and the terminal equipment performs GNSS measurements during the first time period.

[0356] The network device determines that the first time period overlaps with the third time period. For example, the end time of the third time period is before the end time of the first time period, or the end time of the third time period is the same as the end time of the first time period. Optionally, there may be no sequential constraint between the network device configuring the first time period information to the terminal device and the network device configuring the second time period information to the terminal device. For example, after configuring the third time period information, the network device determines that the current GNSS measurement end time of the terminal device is after the end time of the third time period, and then the network device configures the second time period information to the terminal device.

[0357] The network device configures the terminal device with information for a second time period, the end time of which is after the end time of the first time period. For example, the second time period is a time window in a time-based conditional handover.

[0358] Optionally, the end time of the second time period is after the t-service corresponding to the current serving cell. Optionally, the start time of the second time period is before the t-service corresponding to the current serving cell.

[0359] Method 3:

[0360] Network devices configure information for a third time period to terminal devices. This third time period is used by the terminal device during the handover process from the first cell to the second cell. For example, the third time period is a time window in time-based conditional handover.

[0361] The terminal device triggers GNSS measurements and sends the information for the first time period to the network device.

[0362] The network device determines that the first time period overlaps with the third time period. For example, the end time of the third time period is before the end time of the first time period, or the end time of the third time period is the same as the end time of the first time period.

[0363] The network device configures the second time period information to the terminal device. This second time period is used to update the third time period, or the conditional switching corresponding to the second time period is an update to the conditional switching corresponding to the third time period (e.g., the network device deletes the conditional switching corresponding to the third time period, or the network device configures the conditional switching corresponding to the second time period). The end time of the second time period is after the end time of the first time period. Optionally, the end time of the second time period is after the t-service corresponding to the current serving cell. Optionally, the start time of the second time period is before the t-service corresponding to the current serving cell.

[0364] S702, the terminal equipment performs GNSS measurements in the first time period.

[0365] S703, the terminal device performs the process of switching from the first cell to the second cell in the second time period.

[0366] According to the method 700 proposed in this application, the end time of the cell handover performed by the terminal device is after the end time of the GNSS measurement, so that the terminal device still has the opportunity to perform cell handover and switch to the target cell after the end time of the GNSS measurement.

[0367] Regarding this fourth question, such as Figure 11 As shown, this application proposes a method 800. Specifically, method 800 includes the following steps:

[0368] S801, the network device sends information about the execution conditions for conditional handover to the terminal device. Correspondingly, the terminal device receives the information about the execution conditions for conditional handover.

[0369] The execution condition for this conditional handover includes the validity of GNSS information. In other words, the method in this application enhances (or adds) the existing execution conditions for conditional handover, so that when determining the execution conditions for conditional handover, in addition to judging the existing handover execution conditions, such as distance-based criteria, time-based criteria, or measurement event-based criteria, it is also necessary to determine the validity of GNSS information.

[0370] Optionally, valid GNSS information includes GNSS information that has not expired at the time of the condition switching decision.

[0371] Optionally, valid GNSS information includes GNSS information remaining validity time being greater than or equal to a preset threshold at the time of condition switching decision.

[0372] S802, if the conditions for condition switching are met, the terminal device performs condition switching.

[0373] For example, if the existing conditions for switching are met and the GNSS information is valid, the terminal device will perform the switching.

[0374] For example, if the existing conditions for switching are met and the GNSS information is invalid, the terminal device will perform GNSS measurements to update the GNSS information.

[0375] For example, if the existing conditions for switching are met and the remaining valid time of GNSS is greater than a preset threshold, then the terminal device will perform a condition switch.

[0376] For example, if the existing conditions for switching are met and the remaining valid time of GNSS is less than a preset threshold, the terminal device will perform GNSS measurements and update the GNSS information.

[0377] According to the method 800 proposed in this application, the execution conditions of the existing conditional handover are enhanced so that the execution conditions of the conditional handover include the validity of GNSS information, thereby avoiding the situation where the GNSS information has become invalid after the handover is completed.

[0378] The methods 200 to 800 proposed in this application have been described above. Figure 12 A communication device provided in this application includes a transceiver unit and a processing unit.

[0379] The transceiver unit is used to implement corresponding information sending and receiving functions. The transceiver unit can also be called a communication interface or communication unit. The processing unit is used to perform processing operations.

[0380] For example, the device further includes a storage unit that can be used to store instructions and / or data, and the processing unit can read the instructions and / or data in the storage unit to enable the device to perform the actions of the device in the foregoing method embodiments.

[0381] As one implementation, the device can be the terminal device in the foregoing embodiments, or it can be a component of the terminal device (such as a chip). The transceiver unit and the processing unit can be used to implement the relevant operations of the terminal device.

[0382] For example, the processing unit can be used to perform the operation of acquiring GNSS location information during a preset time period in S201.

[0383] Alternatively, the processing unit can be used to perform the operation of prohibiting the triggering of TAR between the first time and the second time in S202-1.

[0384] Alternatively, the processing unit may be used to perform the operation in S202-2 of triggering TAR after acquiring GNSS location information #A.

[0385] Alternatively, the processing unit may be used to perform the operation of triggering the first TAR between the first time and the second time in S202-3; after obtaining the GNSS location information #A, determine whether to cancel the operation of the first TAR based on the first change amount; and cancel the operation of the first TAR if the first change amount is less than a preset threshold.

[0386] Alternatively, the processing unit may be used to perform the operation in S202-4 of prohibiting the generation of TA to report MAC CE between the first time and the second time.

[0387] The transceiver unit can be used to perform the corresponding data packet sending operation.

[0388] For example, the processing unit can be used to perform the operation of obtaining the first GNSS location information in the preset time period in S301, and the operation of determining whether CHO is triggered in the preset time period in S302.

[0389] In one implementation, the device can be the terminal device in the foregoing embodiments, and the processing unit can be used to execute S401 and S402.

[0390] In one implementation, the device can be the terminal device in the foregoing embodiments, and the transceiver unit can be used to execute S502 and S504. Alternatively, the device can be the network device in the foregoing embodiments, and the processing unit can be used to execute S503.

[0391] In one implementation, the device can be the terminal device in the foregoing embodiments, and the processing unit can be used to execute S603 and S604. Alternatively, the device can be the network device in the foregoing embodiments, and the processing unit can be used to execute S601, while the transceiver unit can be used to execute S602.

[0392] As one implementation, the device can be the terminal device in the foregoing embodiments, the transceiver unit can be used to execute S701, and the processing unit can be used to execute S702 and S703.

[0393] In one implementation, the device can be the terminal device in the foregoing embodiments, and the processing unit can be used to execute S802. Alternatively, the device can be the network device in the foregoing embodiments, and the transceiver unit can be used to execute S801.

[0394] It is understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0395] The transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as processing units, can be replaced by processors, which respectively execute the transceiver operations and related processing operations in each method embodiment.

[0396] In addition, the aforementioned transceiver unit can also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit can be a processing circuit.

[0397] Figure 13 Another communication device provided in this application includes a processor and a communication interface. The processor executes programs or instructions stored in a memory, or reads data stored in a memory, to perform the relevant actions in the above method embodiments. Exemplarily, there may be one or more processors. The communication interface is used for receiving and / or transmitting signals.

[0398] Exemplarily, the communication device may further include a memory for storing computer programs or instructions and / or data. The memory may be integrated with the processor or may be disposed separately. Of course, the communication device may also exclude the memory, which may be located outside the communication device. Exemplarily, there may be one or more memories.

[0399] For example, the processor, communication interface, and memory are interconnected via a bus; the bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. These buses can be categorized as address buses, data buses, and control buses, etc. For ease of illustration, only one thick line is used in the diagram, but this does not imply that there is only one bus or one type of bus.

[0400] It is understood that the processor mentioned in the embodiments of this application may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor may further include a hardware chip. The aforementioned hardware chip may be an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The aforementioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0401] It is also understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache.

[0402] It is understood that if the embodiments of this application are implemented in software form and sold or used as independent products, the corresponding program (also referred to as code or instructions) can be stored in a readable storage medium. Therefore, this application also provides a readable storage medium including a program that, when run on a device or computer, causes the device or computer to perform any possible implementation of the above-described scheme.

[0403] Readable storage media include: USB flash drives, external hard drives, ROM, RAM, magnetic disks or optical disks, and other media that can store program code.

[0404] The technical solution of this application can be embodied in the form of a software product. Therefore, this application also provides a program product, which includes: a program that, when run, causes a device or computer to execute any possible implementation of the above-described solution.

[0405] Furthermore, this application also provides a chip system (or chip). The chip system includes a processor and an interface circuit. The interface circuit is used to provide the processor with the transmission and / or reception of data, instructions, or information. The processor is used to execute any possible implementation of the above-described scheme.

[0406] The above are merely specific embodiments 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 communication method, characterized in that, include: The Global Navigation Satellite System (GNSS) location information is acquired within a preset time period, wherein the moment when the acquisition of the GNSS location information begins is the first moment, and the moment when the acquisition of the GNSS location information is completed is the second moment. After the second time point, the trigger condition switching CHO is allowed; or, The CHO is prohibited from being triggered during the preset time period; During GNSS measurements, at least one of the following tasks shall not be performed: radio link monitoring, cell selection, serving cell measurement, neighbor cell measurement, system information reading, or radio link reconstruction. Start a first timer, and execute the at least one of the tasks during the execution of the first timer; When the GNSS measurement is initiated before the first timer expires, the first timer is paused during the GNSS measurement.

2. The method according to claim 1, characterized in that, During the preset time period, the permission to trigger a CHO includes: Whether to allow triggering a CHO is determined based on the remaining service time, where the remaining service time is the remaining time that the source network device can provide services to the terminal device.

3. The method according to claim 1 or 2, characterized in that, The method further includes: After acquiring the GNSS location information, a timed advance report to TAR is triggered; or, TAR activation is prohibited between the first time point and the second time point; or, Between the first time point and the second time point, a first TAR is triggered; whether to cancel the first TAR is determined based on a first change amount, where the first change amount is the change in the first timing advance TA relative to the second TA, the first TA is obtained based on the GNSS location information, and the second TA is the most recently reported TA; or... Between the first time point and the second time point, the generation of a timed advance reporting Media Access Control Unit (MAC CE) is prohibited. The timed advance reporting MAC CE is used to report TA.

4. The method according to claim 3, characterized in that, After acquiring the GNSS location information, triggering TAR includes: After acquiring the GNSS location information, a first change amount is determined; TAR is triggered when the first change is greater than or equal to a preset threshold.

5. The method according to claim 3, characterized in that, The step of determining whether to cancel the first TAR based on the first change amount includes: If the first change is less than a preset threshold, the first TAR is cancelled.

6. The method according to claim 3, characterized in that, Between the first time point and the second time point, the generation of timed advance reporting MAC CEs is prohibited, including: Between the first time point and the second time point, the use of the uplink shared channel UL-SCH resource is prohibited, and scheduling requests are prohibited from being triggered.

7. The method according to claim 1, characterized in that, The method further includes: The first timer is restarted after the GNSS measurement is completed.

8. The method according to claim 1 or 7, characterized in that, The method further includes: The first timer is paused before the GNSS measurement begins.

9. The method according to claim 1, 7 or 8, characterized in that, The first timer is any one of T310, T311 or T301.

10. A communication device, characterized in that, Includes a unit for performing the method of any one of claims 1-9.

11. A communication device, characterized in that, include: A communication interface and a processor, the processor being configured to execute a computer program or instructions that cause the communication device to perform the method as described in any one of claims 1-9.

12. A communication system, characterized in that, The communication system includes a terminal device and a network device, wherein the terminal device is used to perform the method as described in any one of claims 1-9.

13. A computer-readable storage medium, characterized in that, Includes a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1-9.

14. A computer program product, characterized in that, It includes instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-9.

Images