Wireless communication method, terminal device, and network device

Abstract

Provided are a wireless communication method, a terminal device, and a network device. The wireless communication method comprises: a terminal device sends first information to a network device, wherein the first information is related to interference between GNSS reception and NTN transmission.

Description

Methods, terminal devices, and network devices for wireless communication Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a method, terminal device, and network device for wireless communication. Background Technology

[0002] Terminal devices typically support multiple radio access technologies (RATs), and interference can occur between different RATs. For example, if the frequency band used by a terminal device to receive Global Navigation Satellite System (GNSS) signals is close to the frequency band used for transmission via non-terrestrial network (NTN), interference may occur between them. Therefore, how to avoid interference between GNSS reception and NTN transmission becomes a problem that needs to be solved. Summary of the Invention

[0003] This application provides a method, terminal device, and network device for wireless communication. The various aspects covered in this application are described below.

[0004] In a first aspect, a method for wireless communication is provided, comprising: a terminal device sending first information to a network device, the first information relating to interference between GNSS reception and NTN transmission.

[0005] In a second aspect, a method for wireless communication is provided, comprising: if GNSS reception and NTN transmission of a terminal device interfere with each other, the terminal device refuses to perform transmission on some or all of the uplink time domain resources of the NTN transmission.

[0006] Thirdly, a method for wireless communication is provided, comprising: a network device receiving first information transmitted by a terminal device, the first information relating to interference between GNSS reception and NTN transmission.

[0007] Fourthly, a method for wireless communication is provided, comprising: a network device sending second configuration information to a terminal device, the second configuration information being associated with the terminal device refusing to perform transmission on some or all uplink time domain resources of NTN transmission, wherein the terminal device refusing to perform transmission on some or all uplink time domain resources of NTN transmission is performed when interference occurs between the terminal device's GNSS reception and NTN transmission.

[0008] Fifthly, a terminal device is provided, comprising: a transmitting module for transmitting first information to a network device, the first information being related to interference between GNSS reception and NTN transmission.

[0009] In a sixth aspect, a terminal device is provided, comprising: a processing module configured to refuse to perform transmission on some or all of the uplink time domain resources of the NTN transmission if interference occurs between the GNSS reception and NTN transmission of the terminal device.

[0010] In a seventh aspect, a network device is provided, comprising: a receiving module for receiving first information sent by a terminal device, the first information being related to interference between GNSS reception and NTN transmission.

[0011] Eighthly, a network device is provided, comprising: a transmitting module for transmitting second configuration information to a terminal device, the second configuration information being associated with the terminal device refusing to perform transmission on some or all uplink time domain resources of NTN transmission, wherein the terminal device refusing to perform transmission on some or all uplink time domain resources of NTN transmission is performed when interference occurs between the terminal device's GNSS reception and NTN transmission.

[0012] A ninth aspect provides a terminal device, including a processor and a memory, the memory being used to store one or more computer programs, the processor being used to invoke the computer programs in the memory to cause the terminal device to perform some or all of the steps in the method of the first aspect or the second aspect.

[0013] In a tenth aspect, a network device is provided, including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the network device to perform some or all of the steps of the method in the third or fourth aspect.

[0014] Eleventhly, embodiments of this application provide a communication system, which includes the aforementioned terminal device and / or network device. In another possible design, the system may further include other devices that interact with the terminal device or network device as described in the embodiments of this application.

[0015] In a twelfth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a computer to perform some or all of the steps in the methods described above.

[0016] In a thirteenth aspect, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0017] In a fourteenth aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0018] In this embodiment, the terminal device can send first information to the network device, wherein the first information relates to interference between GNSS reception and NTN transmission. In this way, the network device can schedule NTN transmission and / or GNSS reception based on the first information, thereby helping to avoid interference between GNSS reception and NTN transmission. Attached Figure Description

[0019] Figure 1 is an example diagram of the system architecture of a wireless communication system applicable to embodiments of this application.

[0020] Figure 2 is another example diagram of the system architecture of a wireless communication system to which embodiments of this application are applicable.

[0021] Figure 3 is another example diagram of the system architecture of a wireless communication system to which the embodiments of this application are applicable.

[0022] Figure 4 is a flowchart illustrating a method for wireless communication provided in an embodiment of this application.

[0023] Figure 5 is a flowchart illustrating a method for wireless communication provided in another embodiment of this application.

[0024] Figure 6 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application.

[0025] Figure 7 is a schematic diagram of the structure of a terminal device provided in another embodiment of this application.

[0026] Figure 8 is a schematic diagram of the structure of a network device provided in an embodiment of this application.

[0027] Figure 9 is a schematic diagram of the structure of a network device provided in another embodiment of this application.

[0028] Figure 10 is a schematic structural diagram of the communication device provided in an embodiment of this application. Detailed Implementation

[0029] Communication system architecture

[0030] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, evolution of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, NTN system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), and Wireless Fidelity (WF). Fidelity (WiFi), 5th-generation (5G) communication systems or other communication systems, such as future communication systems, such as 6th-generation mobile communication systems, or satellite communication systems.

[0031] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to these communication systems.

[0032] The communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

[0033] The communication system in this application embodiment can be applied to unlicensed spectrum, which can also be considered as shared spectrum; or, the communication system in this application embodiment can also be applied to licensed spectrum, which can also be considered as dedicated spectrum.

[0034] The embodiments of this application can be applied to NTN systems as well as terrestrial network (TN) systems. By way of example and not limitation, NTN systems include NR-based NTN systems and Internet of Things (IoT)-based NTN systems. For example, in scenarios where narrowband Internet of Things (NB-IoT) and enhanced machine-type communication (eMTC) access NTN, the system composed of IoT terminal devices and the NTN network can be understood as an IoT-based NTN system.

[0035] This application describes various embodiments in conjunction with network devices and terminal devices. The terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment, etc.

[0036] In the embodiments of this application, the terminal device may be a station (ST) in a WLAN, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (PLMN) network, etc.

[0037] In the embodiments of this application, the terminal device can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as handheld devices with wireless connectivity, in-vehicle devices, etc. The terminal device in the embodiments of this application can be a mobile phone, tablet computer, laptop computer, PDA, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a scheduling entity, providing sidelink signals between terminal devices in V2X or D2D, etc. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices can communicate without relaying communication signals through base stations.

[0038] The network device in this application embodiment can be a device for communicating with a terminal device. This network device can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master MeNB, auxiliary SeNB, multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in D2D, V2X, and M2M communications, network-side devices in 6G networks, and devices that perform base station functions in future communication systems. Base stations can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

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

[0040] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.

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

[0042] By way of example and not limitation, in the embodiments of this application, the network device may have mobility characteristics; for example, the network device may be a mobile device. In some embodiments of this application, the network device may be a satellite or a balloon station. For example, the satellite may be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments of this application, the network device may also be a base station located on land, water, or other similar locations.

[0043] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0044] For example, Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. As shown in Figure 1, the communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120 (or a communication terminal, terminal). The network device 110 may provide communication coverage for a specific geographical area and may communicate with terminal devices located within that coverage area. For example, the network device may be a satellite.

[0045] Figure 1 illustrates an exemplary network device and two terminal devices. In some embodiments of this application, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area. This application does not limit this aspect.

[0046] It should be noted that Figure 1 is only an example illustrating the system to which this application applies. Of course, the method shown in the embodiments of this application can also be applied to other systems, such as 5G communication systems, LTE communication systems, etc., and the embodiments of this application do not specifically limit this.

[0047] In some embodiments of this application, the wireless communication system shown in FIG1 may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but this application does not limit this.

[0048] As described above, the technical solutions provided in this application can be applied to NTN systems. For ease of understanding, some related technical knowledge (e.g., NTN network architecture) involved in the embodiments of this application will be introduced first. The following related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0049] NTN

[0050] The 3rd Generation Partnership Project (3GPP) is currently researching NTN technology. NTN typically uses satellite communication to provide communication services to terrestrial users. Compared to terrestrial communication networks (e.g., terrestrial cellular networks), satellite communication has many unique advantages.

[0051] First, satellite communication is not limited by the user's geographical location. For example, conventional terrestrial communication networks cannot cover areas such as oceans, mountains, and deserts where network equipment cannot be deployed. Alternatively, terrestrial communication networks cannot cover certain areas that are sparsely populated and therefore not covered. However, with satellite communication, since a single satellite can cover a large area of ​​the Earth, and satellites orbit the Earth, theoretically, every corner of the Earth can be covered by satellite communication networks.

[0052] Secondly, satellite communication has significant social value. It can reach remote mountainous areas and impoverished, underdeveloped countries or regions at a relatively low cost, enabling people in these areas to enjoy advanced voice communication and mobile internet technologies. From this perspective, satellite communication helps bridge the digital divide with developed regions and promotes development in those areas.

[0053] Secondly, satellite communication has a long range, and the communication cost does not increase significantly with the increase in communication distance.

[0054] Finally, satellite communication is highly stable and unaffected by natural disasters.

[0055] Communication satellites can be classified according to their orbital altitude, such as LEO satellites, MEO satellites, GEO satellites, and HEO satellites. Currently, research primarily focuses on LEO and GEO satellites.

[0056] LEO satellites typically operate at altitudes ranging from 500 km to 1500 km. Correspondingly, their orbital periods are approximately 1.5 to 2 hours. For LEO satellites, the signal propagation delay for single-hop communication between users is generally less than 20 ms. The maximum visible time for LEO satellites is approximately 20 minutes. LEO satellites offer advantages such as short signal propagation distances, low link loss, and low requirements for the transmission power of terminal equipment.

[0057] The GEO satellite orbits at an altitude of approximately 35,786 km. Its orbital period around the Earth is 24 hours. For GEO satellites, the signal propagation delay for single-hop communication between users is typically around 250 ms.

[0058] To ensure satellite coverage and enhance the overall capacity of the satellite communication system, satellites typically employ multi-beam coverage of ground areas. Therefore, a single satellite can generate dozens or even hundreds of beams to cover a ground area. One satellite beam can typically cover a ground area with a diameter of tens to hundreds of kilometers.

[0059] Currently, NTN systems can include NR NTN systems and IoT NTN systems.

[0060] NTN network architecture

[0061] The NTN network architecture can include the following network elements: gateway, feeder link, service link, and satellite.

[0062] An NTN network architecture may include one or more gateways, which can be used to connect satellite and terrestrial public networks.

[0063] A feeder link can refer to the communication link between a gateway and a satellite.

[0064] A service link can refer to the communication link between a terminal device and a satellite.

[0065] From the perspective of the functions provided by satellites, they can be divided into transparent payload satellites and regenerative payload satellites. Transparent payload satellites only provide radio frequency filtering, frequency conversion, and amplification functions. In other words, transparent payload satellites only provide transparent signal forwarding without altering the waveform of the forwarded signal. Regenerative payload satellites, in addition to providing radio frequency filtering, frequency conversion, and amplification functions, can also provide one or more of the following functions: demodulation, decoding, routing, conversion, encoding, modulation, etc. Regenerative payload satellites can have some or all of the functions of a base station. Based on the different functions provided by satellites in the NTN network, the NTN network architecture can be divided into transparent payload NTN network architecture and regenerative payload NTN network architecture. Figures 2 and 3 show example diagrams of transparent payload NTN network architecture and regenerative payload NTN network architecture, respectively.

[0066] In some embodiments, the NTN network architecture may also include inter-satellite links (ISLs). For example, inter-satellite links may exist in a regenerable forwarding NTN network architecture.

[0067] In-device coexistence (IDC) interference

[0068] Terminal devices typically support multiple RATs, such as cellular networks, WLAN, and Bluetooth. When these RATs operate simultaneously, they may cause IDC interference between each other.

[0069] To address the IDC interference problem of terminal devices, three solutions have been introduced: a frequency division multiplexing (FDM) based solution, a time division multiplexing (TDM) based solution, and an autonomous denial solution. These three solutions will be described in detail below.

[0070] FDM-based approach: When network devices allow terminal devices to report IDC issues via an FDM-based approach, the terminal devices can report affected NR frequencies, including attack frequencies and victim frequencies. When the affected NR frequency is an attack frequency, the terminal device can indicate the type of victim system, such as Bluetooth. In some embodiments, when the interference type between NR and other RATs is harmonic interference, the terminal device can indicate a list of affected NR frequencies, where each instance in the list contains an NR frequency and its bandwidth. In some embodiments, when the interference type between NR and other RATs is inter-modulation distortion (IMD) interference, the terminal device can indicate a list of affected NR frequency combinations, where each NR frequency combination in the list includes multiple NR frequencies and their bandwidths.

[0071] TDM-based scheme: When a network device is configured with a TDM-based scheme, the terminal device is allowed to report its preferred activation time, period, and start offset on the affected frequency. In this way, the network device can use the TDM mode reported by the terminal device to schedule the terminal device's transmission or reception on the affected frequency, such as how to start or stop the UE's transmission or reception on the affected frequency. In some embodiments, the terminal device can report its preferred activation time, period, and start offset on the affected frequency through IDC-TDM-Assistance, the content of which is shown in the following example.

[0072] The autonomous rejection scheme: Network devices can provide terminal devices with autonomous rejection configuration information for each cell group. Based on this configuration information, terminal devices are allowed to reject uplink transmissions on certain time slots within a cell group. However, the time slots rejected by the terminal device cannot exceed the maximum uplink transmission time slots configured by the network device. Terminal devices can determine which uplink transmissions can be rejected through their implementation, thereby mitigating interference with other RATs (Remote Access Terminals).

[0073] GNSS reception of terminal equipment

[0074] According to the current 36.331 protocol, if the network device is configured with gnss-PositionFixDurationReporting in SystemInformationBlockType2(-NB), then the terminal device can report gnss-PositionFixDuration in the RRC Connection Reestablishment Complete message or the RRC Connection Reconfiguration Complete message.

[0075] The terminal device can indicate the time required to acquire GNSS positioning via gnss-PositionFixDuration. The value of gnss-PositionFixDuration can be 1s, 2s, ..., with a maximum of 31s. An example of the gnss-PositionFixDuration information element (IE) is shown below.

[0076] Among them, the value s1 corresponds to 1s, the value s2 corresponds to 2s, and so on.

[0077] In addition, the terminal device can indicate the valid duration of GNSS maintained by the terminal device via GNSS-ValidityDuration. The minimum value of GNSS-ValidityDuration is 10 seconds, and the maximum value is 120 minutes. An example of GNSS-ValidityDuration IE is shown below.

[0078] Among them, the value s10 corresponds to 10s, the value s20 corresponds to 20s, and so on; the value min5 corresponds to 5 minutes, the value min10 corresponds to 10 minutes, and so on.

[0079] In current communication systems, the frequency band used by terminal devices located in the NTN to receive GNSS is relatively close to the frequency band used for transmission within the NTN. This can cause interference between the terminal device's GNSS reception and its uplink transmission on the NTN band. For example, when a terminal device performs uplink transmission on the NTN band, it may interfere with GNSS reception, preventing the terminal device from correctly receiving GNSS data.

[0080] To address the aforementioned problems, this application proposes Embodiment 1 and Embodiment 2. Embodiment 1 and Embodiment 2 will be described below.

[0081] Example 1: Terminal device reports first information

[0082] Figure 4 is a schematic flowchart of a method for wireless communication provided in an embodiment of this application. The method shown in Figure 4 is described from the perspective of interaction between a terminal device and a network device. For a description of the terminal device and the network device, please refer to the descriptions in Figures 1-3. In some embodiments, the terminal device refers to a terminal device accessing an NTN.

[0083] The method shown in Figure 4 may include step S410, which will be described below.

[0084] In step S410, the terminal device sends the first information to the network device.

[0085] In some embodiments, the first information relates to interference between GNSS reception and NTN transmission. Alternatively, the first information may include auxiliary information related to interference between GNSS reception and NTN transmission. Therefore, in some embodiments, the first information may also be referred to as or understood as interference auxiliary information related to interference between GNSS reception and NTN transmission.

[0086] In some embodiments, after receiving the first information, the network device can schedule GNSS reception and / or NTN transmission according to the first information in order to avoid interference between GNSS reception and NTN transmission.

[0087] This application does not specifically limit the first information, as long as it is related to the interference between GNSS reception and NTN transmission. For example, the first information may include relevant information for FDM-based schemes and / or relevant information for TDM-based schemes.

[0088] In some embodiments, the first information may be used to indicate one or more of the following: interference information between GNSS reception and NTN transmission, information related to the terminal device performing GNSS reception, and information related to the terminal device's tendency (or preference, expectation) for TDM.

[0089] In some embodiments, the first information can be used to indicate one of the above. For example, the first information can be used to indicate interference information between GNSS reception and NTN transmission. As another example, the first information can be used to indicate information related to the terminal device performing GNSS reception. Yet another example, the first information can be used to indicate information related to the terminal device's preference for TDM.

[0090] In some embodiments, the first information can be used to indicate multiple of the above. For example, the first information can be used to indicate interference information between GNSS reception and NTN transmission, as well as information related to the terminal device performing GNSS reception. As another example, the first information can be used to indicate interference information between GNSS reception and NTN transmission, as well as information related to the terminal device's preferred TDM. As another example, the first information can be used to indicate information related to the terminal device performing GNSS reception, as well as information related to the terminal device's preferred TDM. As another example, the first information can be used to indicate interference information between GNSS reception and NTN transmission, information related to the terminal device performing GNSS reception, and information related to the terminal device's preferred TDM.

[0091] In some embodiments, the interference information between GNSS reception and NTN transmission described above can be used to indicate frequency-related information of the interference between GNSS reception and NTN transmission. In this way, network devices can know the frequency of the interference based on the first information, thereby facilitating the avoidance of interference between GNSS reception and NTN transmission using an FDM-based approach.

[0092] In some embodiments, after receiving information about the terminal device's GNSS reception, the network device can determine a scheduling scheme for the terminal device's NTN transmission (i.e., schedule the terminal device's NTN transmission) based on this information, thereby helping to avoid interference between GNSS reception and NTN transmission. For example, after receiving information about the terminal device's GNSS reception, the network device can choose not to perform scheduling during the time the terminal device is performing GNSS reception, i.e., not schedule the terminal device to perform NTN transmission.

[0093] In some embodiments, after receiving information about the TDM preferred by the terminal device, the network device can determine the scheduling scheme for the NTN transmission of the terminal device based on the information about the TDM preferred by the terminal device, thereby helping to avoid interference between GNSS reception and NTN transmission.

[0094] In some embodiments, the relevant information of the terminal device’s preferred TDM may include one or more of the terminal device’s preferred activation time, period, and start offset.

[0095] In some embodiments, information related to the TDM preferred by the terminal device can be indicated by the discontinuous reception (DRX) parameter preferred by the terminal device. The DRX parameter preferred by the terminal device will be described in detail later.

[0096] In some embodiments, the first information may include one or more of the following: affected NTN frequency information, start time of GNSS reception performed by the terminal device, offset of the start time of GNSS reception performed by the terminal device, duration of GNSS reception performed by the terminal device, effective duration of GNSS maintained by the terminal device, frequency information of the terminal device performing GNSS reception, DRX cycle preferred by the terminal device, wake-up duration of DRX preferred by the terminal device, DRX start time offset preferred by the terminal device, and DRX slot offset preferred by the terminal device.

[0097] In some embodiments, the first information may include one of the information described above. For example, the first information may include affected NTN frequency information. As another example, the first information may include the duration for which the terminal device performs GNSS reception. As another example, the first information may include the effective duration of GNSS maintained by the terminal device. As another example, the first information may include the DRX cycle preferred by the terminal device. As another example, the first information may include the wake-up duration of the DRX preferred by the terminal device.

[0098] In some embodiments, the first information may include multiple of the information described above. For example, the first information may include the affected NTN frequency information and the duration of GNSS reception performed by the terminal device. As another example, the first information may include the start time of GNSS reception performed by the terminal device, the offset of the start time of GNSS reception performed by the terminal device, the duration of GNSS reception performed by the terminal device, and the effective duration of GNSS maintained by the terminal device. As another example, the first information may include the duration of GNSS reception performed by the terminal device and the effective duration of GNSS maintained by the terminal device. As another example, the first information may include the DRX cycle preferred by the terminal device, the wake-up duration of the DRX cycle preferred by the terminal device, the DRX start time offset preferred by the terminal device, and the DRX slot offset preferred by the terminal device. As another example, the first information may include the affected NTN frequency information, the DRX cycle preferred by the terminal device, and the wake-up duration of the DRX cycle preferred by the terminal device. As another example, the first information may include the duration of GNSS reception performed by the terminal device, the effective duration of GNSS maintained by the terminal device, and the DRX cycle preferred by the terminal device.

[0099] It should be noted that the above examples are merely illustrations, and the first piece of information may include any one or more of the above information. For the sake of brevity, they will not be listed one by one here.

[0100] This application does not limit the affected NTN frequency information, which can be any NTN frequency (such as an NTN frequency number) and / or the bandwidth range corresponding to that NTN frequency (such as a bandwidth part (BWP) range). For example, the affected NTN frequency information may include one or more of the following frequency bands: N255, N256, and N254. As another example, the affected NTN frequency information may include any NTN frequency number within the NTN frequency range and the bandwidth range corresponding to that NTN frequency number. In some embodiments, the NTN frequency number can be indicated by NTN frequency number indication information.

[0101] In some embodiments, the affected NTN frequency information may include attack frequency information and / or victim frequency information. In some embodiments, if the affected NTN frequency information includes attack frequency information, the terminal device may indicate the type of victim system in the first information, such as Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), BeiDou Satellite System, etc.

[0102] In some embodiments, if the type of interference between NTN transmission and GNSS reception is harmonic interference, the terminal device may indicate a list of affected NTN frequencies in the first information, where each instance in the NTN frequency list may include an NTN frequency and the bandwidth of that NTN frequency.

[0103] In some embodiments, if the type of interference between NTN transmission and GNSS reception is IMD interference, the terminal device may indicate a list of affected NTN frequency combinations in the first information. Each NTN frequency combination in the list may include multiple NTN frequencies and the bandwidth corresponding to the multiple NTN frequencies.

[0104] In some embodiments, the start time of GNSS reception by the terminal device can be used to indicate the time when the terminal device begins to acquire GNSS positioning. Therefore, the start time of GNSS reception by the terminal device can also be referred to as or understood as the start time of GNSS positioning acquisition by the terminal device.

[0105] In some embodiments, the offset of the start time of the terminal device performing GNSS reception can be used to indicate the offset of the time when the terminal device begins to acquire GNSS positioning. Therefore, the offset of the start time of the terminal device performing GNSS reception can also be referred to as or understood as the offset of the start time of the terminal device acquiring GNSS positioning.

[0106] In some embodiments, the duration of GNSS reception performed by the terminal device can be used to indicate the time required for the terminal device to acquire GNSS positioning. Therefore, in some embodiments, the duration of GNSS reception performed by the terminal device can be indicated by gnss-PositionFixDuration IE.

[0107] In some embodiments, after the terminal device indicates the duration for which it performs GNSS reception in the first information, the network device may not perform scheduling during that period.

[0108] In some embodiments, the duration of GNSS validity maintained by the terminal device can be indicated by GNSS-ValidityDuration IE.

[0109] In some embodiments, the frequency information in which the terminal device performs GNSS reception can be used to instruct the terminal device to obtain the frequency of GNSS positioning. This application does not limit the frequency information in which the terminal device performs GNSS reception; it can perform GNSS reception within the GNSS-related frequency number and / or bandwidth range.

[0110] In some embodiments, one or more of the following can be understood as or referred to as relevant information about the terminal device performing GNSS reception: the start time of GNSS reception performed by the terminal device, the offset of the start time of GNSS reception performed by the terminal device, the duration of GNSS reception performed by the terminal device, the effective duration of GNSS maintained by the terminal device, and the frequency information in which the terminal device performs GNSS reception.

[0111] In some embodiments, one or more of the following are DRX parameters preferred by the terminal device: the DRX period preferred by the terminal device, the wake-up duration of the DRX preferred by the terminal device, the DRX start time offset preferred by the terminal device, and the DRX slot offset preferred by the terminal device. These DRX parameters preferred by the terminal device are described in illustrative terms below.

[0112] In some embodiments, the DRX parameters preferred by the terminal device can be determined based on information related to the terminal device performing GNSS reception. For example, the DRX period preferred by the terminal device can be determined based on information related to the terminal device performing GNSS reception (such as the duration of GNSS reception). As another example, the wake-up duration of the DRX preferred by the terminal device can be determined based on information related to the terminal device performing GNSS reception (such as the duration of GNSS reception). As yet another example, the DRX start time offset and / or the DRX slot offset preferred by the terminal device can be determined based on one or more of the information related to the terminal device performing GNSS reception (such as the duration of GNSS reception, the start time of GNSS reception, and the offset of the start time of GNSS reception).

[0113] Correspondingly, the DRX parameters configured by the network device can be determined based on information related to the GNSS reception performed by the terminal device. For example, the DRX period configured by the network device can be determined based on information related to the GNSS reception performed by the terminal device (such as the duration of GNSS reception). Similarly, the DRX wake-up duration configured by the network device can be determined based on information related to the GNSS reception performed by the terminal device (such as the duration of GNSS reception). Furthermore, the DRX start time offset and / or the DRX timeslot offset configured by the network device can be determined based on information related to the GNSS reception performed by the terminal device (such as the duration of GNSS reception performed by the terminal device, the start time of GNSS reception performed by the terminal device, and the offset of the start time of GNSS reception performed by the terminal device, or one or more of these parameters).

[0114] In some embodiments, the DRX period preferred by the terminal device can be used to indicate the DRX period that the terminal device expects the network device to configure when interference occurs between GNSS reception and NTN transmission. This application does not limit the value of the DRX period preferred by the terminal device; it can be any positive number.

[0115] In some embodiments, the DRX period preferred by the terminal device and / or the DRX period configured by the network device can be greater than or equal to the duration of GNSS reception performed by the terminal device. For example, if the duration of GNSS reception performed by the terminal device is 6 seconds, the DRX period preferred by the terminal device and / or the DRX period configured by the network device can be greater than or equal to 6 seconds. Similarly, if the duration of GNSS reception performed by the terminal device is 31 seconds, the DRX period preferred by the terminal device and / or the DRX period configured by the network device can be greater than or equal to 31 seconds.

[0116] In some embodiments, the maximum value of the DRX period preferred by the terminal device can be less than or equal to 10240 milliseconds. For example, if the maximum value of the DRX period preferred by the terminal device is 10240 milliseconds, then the DRX period preferred by the terminal device can be a value less than 10240 milliseconds. Correspondingly, the maximum value of the DRX period configured by the network device for the terminal device can be less than or equal to 10240 milliseconds. For example, if the maximum value of the DRX period configured by the network device for the terminal device is 10240 milliseconds, then the DRX period configured by the network device can be a value less than 10240 milliseconds.

[0117] For example, the DRX period preferred by the terminal device and / or the DRX period configured by the network device may include one of the following: 2 milliseconds, 3 milliseconds, 4 milliseconds, 5 milliseconds, 6 milliseconds, 7 milliseconds, 8 milliseconds, 10 milliseconds, 14 milliseconds, 16 milliseconds, 20 milliseconds, 30 milliseconds, 32 milliseconds, 35 milliseconds, 60 milliseconds, 64 milliseconds, 70 milliseconds, 80 milliseconds, 96 milliseconds, 100 milliseconds, 128 milliseconds, 160 milliseconds, 256 milliseconds, 320 milliseconds, 512 milliseconds, 640 milliseconds, 1024 milliseconds, 1280 milliseconds, 2048 milliseconds, 2560 milliseconds, 5120 milliseconds, and 10240 milliseconds.

[0118] In other embodiments, the maximum value of the DRX period preferred by the terminal device can be greater than 10240 milliseconds. For example, the maximum value of the DRX period preferred by the terminal device can be 20480 milliseconds, 40960 milliseconds, etc. This is because the time required for the terminal device to perform GNSS reception may be relatively long (e.g., up to 31 seconds), and a larger preferred DRX period makes it easier to avoid interference with GNSS reception. Correspondingly, the maximum value of the DRX period configured by the network device for the terminal device can be greater than 10240 milliseconds. For example, the maximum value of the DRX period configured by the network device can be 20480 milliseconds, 40960 milliseconds, etc.

[0119] For example, the DRX period preferred by the terminal device and / or the DRX period configured by the network device may include one of the following: 4 milliseconds, 8 milliseconds, 10 milliseconds, 20 milliseconds, 32 milliseconds, 35 milliseconds, 60 milliseconds, 64 milliseconds, 70 milliseconds, 80 milliseconds, 96 milliseconds, 100 milliseconds, 128 milliseconds, 160 milliseconds, 256 milliseconds, 320 milliseconds, 512 milliseconds, 640 milliseconds, 1024 milliseconds, 1280 milliseconds, 2048 milliseconds, 2560 milliseconds, 5120 milliseconds, 10240 milliseconds, 20480 milliseconds, or 40960 milliseconds.

[0120] In some embodiments, the preferred DRX cycle of the terminal device can be indicated by the parameter cycleLength.

[0121] In some embodiments, the DRX on-duration can be used to indicate the active duration or on-duration of the terminal device within a DRX cycle. In some embodiments, the terminal device's preferred DRX on-duration can be used to indicate the DRX on-duration that the terminal device expects the network device to configure when interference occurs between GNSS reception and NTN transmission. In some embodiments, the terminal device's preferred DRX on-duration can be indicated by the parameter activeDuration.

[0122] This application does not limit the value of the wake-up duration of the DRX preferred by the terminal device and / or the wake-up duration of the DRX configured by the network device; it can be any value less than the DRX period. For example, with a DRX period of 10240 milliseconds, the wake-up duration of the DRX preferred by the terminal device and / or the wake-up duration of the DRX configured by the network device can be any value less than 10240 milliseconds. Similarly, with a DRX period of 40960 milliseconds, the wake-up duration of the DRX preferred by the terminal device and / or the wake-up duration of the DRX configured by the network device can be any value less than 40960 milliseconds.

[0123] In some embodiments, the wake-up duration of the DRX preferred by the terminal device and / or the wake-up duration of the DRX configured by the network device may be relatively small, such as less than a threshold (e.g., 1024 milliseconds, 512 milliseconds, etc.). This is because the shorter the wake-up duration of the DRX of the terminal device, the less likely there is interference between the terminal device performing GNSS reception and NTN transmission.

[0124] In some embodiments, the wake-up duration of the DRX preferred by the terminal device and / or the wake-up duration of the DRX configured by the network device can be 0. For example, the wake-up duration of the DRX preferred by the terminal device and / or the wake-up duration of the DRX configured by the network device can be 0. In this way, the network device can be configured not to perform scheduling throughout the entire DRX cycle, thereby avoiding interference between GNSS reception and NTN transmission.

[0125] In some embodiments, the DRX start time offset can be used to determine the timing of the terminal device's listening within the DRX cycle. In some embodiments, the terminal device's preferred DRX start time offset can be used to indicate the DRX start time offset that the terminal device expects the network device to configure when interference occurs between GNSS reception and NTN transmission. In some embodiments, the terminal device's preferred DRX start time offset can be indicated by the parameter startOffset.

[0126] In some embodiments, the maximum value of the DRX start time offset is determined based on the DRX period. For example, the maximum value of the DRX start time offset preferred by the terminal device is determined based on the DRX period preferred by the terminal device. As another example, the maximum value of the DRX start time offset configured by the network device is determined based on the DRX period configured by the network device. Taking a terminal device's preferred DRX period of 10240 milliseconds as an example, the maximum value of the terminal device's preferred DRX start time offset is 10239, meaning the terminal device's preferred DRX start time offset can be a value between 0 and 10239. Taking a terminal device's preferred DRX period of 40960 milliseconds as an example, the maximum value of the terminal device's preferred DRX start time offset is 40959, meaning the terminal device's preferred DRX start time offset can be a value between 0 and 40659.

[0127] In some embodiments, the DRX slot offset can be used to determine the listening timing of the terminal device within the DRX cycle. In some embodiments, the DRX slot offset preferred by the terminal device can be used to indicate the DRX slot offset that the terminal device expects the network device to configure when interference occurs between GNSS reception and NTN transmission. In some embodiments, the DRX slot offset preferred by the terminal device can be indicated by the parameter slotOffset.

[0128] This application does not limit the values ​​of the DRX timeslot offset preferred by the terminal device and / or the DRX timeslot offset configured by the network device. For example, the values ​​of the DRX timeslot offset preferred by the terminal device and / or the DRX timeslot offset configured by the network device can be positive integers less than or equal to 31. However, this application is not limited to this; for example, the values ​​of the DRX timeslot offset preferred by the terminal device and / or the DRX timeslot offset configured by the network device can be extended to values ​​greater than 31, such as 32, 35, etc.

[0129] The content of the first information has been introduced above. The configuration of the first information and the way the first information is carried will be introduced below.

[0130] Referring again to Figure 4, in some embodiments, the method shown in Figure 4 may further include step S405. In step S405, the terminal device receives first configuration information sent by the network device.

[0131] In some embodiments, the first configuration information is associated with the reporting of the first information. In other words, the first configuration information is the configuration information used to report the first information.

[0132] This application does not limit the content of the first configuration information in its embodiments. In some embodiments, the first configuration information may include first indication information, which can be used to indicate whether the terminal device is allowed to report the first information. Of course, in addition to the first indication information, the first configuration information may also include other information. For example, the first configuration information may also indicate which information in the first information the terminal device should report, or the first configuration information may also indicate the resources for reporting the first information.

[0133] This application does not limit the indication method of the first indication information in its embodiments. In some embodiments, the first indication information may explicitly indicate whether the terminal device is allowed to report the first information. As one implementation, the first indication information may use one or more bits to indicate whether the terminal device is allowed to report the first information. For example, when the value of the first indication information is a first value (such as 1), it indicates that the terminal device is allowed to report the first information; when the value of the first indication information is a second value (such as 0), it indicates that the terminal device is not allowed to report the first information. In other embodiments, the first indication information may implicitly indicate whether the terminal device is allowed to report the first information. As one implementation, when the first indication information includes the content to be reported and / or includes the number of information to be reported, it indicates that the terminal device is allowed to report the first information.

[0134] In some embodiments, the first indication information used to indicate whether the terminal device is allowed to report first information may include one or more of the following: whether the terminal device is allowed to report first information based on a first field, and whether the terminal device is allowed to report first information based on a second field. For example, the first indication information may be used to indicate whether the terminal device is allowed to report first information based on a first field. As another example, the first indication information may be used to indicate whether the terminal device is allowed to report first information based on a second field. As yet another example, the first indication information may be used to indicate whether the terminal device is allowed to report first information based on a first field, and whether the terminal device is allowed to report first information based on a second field. The first and second fields will be described later and will not be detailed here.

[0135] This application does not limit the method of carrying the first configuration information. For example, the first configuration information can be carried by one or more of the following: radio resource control (RRC) signaling, medium access control (MAC) signaling, and downlink control information (DCI).

[0136] In some embodiments, the first configuration information can be carried by dedicated signaling (such as RRC dedicated signaling). This application embodiment does not limit the RRC signaling (such as RRC dedicated signaling) carrying the first configuration information. Exemplarily, the RRC signaling carrying the first configuration information may include one or more of the following: RRC Reconfiguration message and RRC Resume message.

[0137] In some embodiments, after receiving the first configuration information, if the terminal device detects interference between GNSS reception and NTN transmission, and the terminal device has not yet reported the first information to the network device, the terminal device may report the first information to the network device.

[0138] This application does not limit the method of carrying the first information in its embodiments. In some embodiments, the first information can be carried by uplink signaling. For example, the first information can be carried by one or more of the following: uplink RRC signaling, uplink MAC signaling, and uplink control information (UCI). In some embodiments, the first information can be carried by the auxiliary information of the terminal device, that is, the first information can be carried by the UE's auxiliary information (UAI).

[0139] In some embodiments, the first information may be carried through a first field of the UAI. This first field may be dedicated to carrying the first information. In some embodiments, the first field may be a new field defined in a future communication system, dedicated to carrying the first information.

[0140] In some embodiments, when the first information is carried through a first field, the first information may include some or all of the following: affected NTN frequency information, start time of GNSS reception performed by the terminal device, offset of the start time of GNSS reception performed by the terminal device, duration of GNSS reception performed by the terminal device, effective duration of GNSS maintained by the terminal device, frequency information of the terminal device performing GNSS reception, DRX cycle preferred by the terminal device, wake-up duration of DRX preferred by the terminal device, DRX start time offset preferred by the terminal device, and DRX slot offset preferred by the terminal device. For example, the first information may include affected NTN frequency information. Another example is that the first information may include affected NTN frequency information and related information of GNSS reception performed by the terminal device (such as the start time of GNSS reception, duration of GNSS reception, etc.). Yet another example is that the first information may include affected NTN frequency information and DRX parameters preferred by the terminal device (such as DRX cycle, DRX wake-up duration, etc.). Yet another example is that the first information may include related information of GNSS reception performed by the terminal device and DRX parameters preferred by the terminal device. For example, the first information may include the affected NTN frequency information, information related to the terminal device performing GNSS reception, and the DRX parameters preferred by the terminal device.

[0141] In some embodiments, when the first information is carried through the first field, the value range of the DRX parameter preferred by the terminal device does not need to be expanded; the existing value range can be applied directly. For example, the value ranges of one or more of the following—DRX period, DRX start time offset, DRX wake-up duration, and DRX timeslot offset—do not need to be expanded. As an example, when the first information is carried through the first field and includes information related to the terminal device receiving GNSS reception, the value range of the DRX parameter preferred by the terminal device does not need to be expanded. As another example, when the first information is carried through the first field and includes information related to the terminal device receiving GNSS reception and interference information between GNSS reception and NTN transmission, the value range of the DRX parameter preferred by the terminal device does not need to be expanded. As yet another example, when the first information is carried through the first field and includes information related to the terminal device receiving GNSS reception and information related to the terminal device's preferred TDM, the value range of the DRX parameter preferred by the terminal device does not need to be expanded.

[0142] In some embodiments, the first information can be carried through a second field of the UAI. This second field can be used to carry TDM-based IDC auxiliary information or FDM-based IDC auxiliary information.

[0143] In some embodiments, when the first information is carried through the second field, the first information may include some of the information listed above. For example, if the second field is used to carry IDC auxiliary information for FDM, the first information may include affected NTN frequency information. Similarly, if the second field is used to carry IDC auxiliary information for TDM, the first information may include DRX parameters preferred by the terminal device (e.g., one or more of DRX period, DRX wake-up duration, DRX start time offset, and DRX timeslot offset).

[0144] In some embodiments, when the first information is carried through the second field, the range of values ​​for the DRX parameters preferred by the terminal device needs to be expanded, such as the range of values ​​for one or more of the following: DRX period, DRX start time offset, DRX wake-up duration, and DRX time slot offset.

[0145] For ease of understanding, the scheme of Embodiment 1 will be described by way of example below with reference to Embodiments 1.1 and 1.2.

[0146] Example 1.1: Reporting the first information through the first field in UAI

[0147] First, the terminal device can obtain the first configuration information through dedicated signaling (such as RRC reconfiguration messages and RRC recovery messages). The first configuration information can indicate whether the terminal device is allowed to report the first information (or whether the terminal device is allowed to report the first information based on the first field) through the first indication information.

[0148] After receiving the first configuration information, if the terminal device detects interference between GNSS reception and NTN transmission, and the terminal device has not yet reported the first information through the UAI process, the terminal device can trigger the UAI process. For example, during the UAI process, the terminal device can report one or more of the following information through a first field (such as a newly defined field): affected NTN frequency information, the start time of the terminal device performing GNSS reception, the offset of the start time of the terminal device performing GNSS reception, the duration of the terminal device performing GNSS reception, the effective duration of the GNSS maintained by the terminal device, the frequency information of the terminal device performing GNSS reception, the preferred DRX cycle of the terminal device, the wake-up duration of the preferred DRX cycle of the terminal device, the preferred DRX start time offset of the terminal device, and the preferred DRX timeslot offset of the terminal device.

[0149] Example 1.2: Terminal device reports first information based on TDM solution

[0150] First, the terminal device can obtain the first configuration information through dedicated signaling (such as RRC reconfiguration messages and RRC recovery messages). The first configuration information can indicate whether the terminal device is allowed to report the first information (or whether the terminal device is allowed to report the first information based on the second field, or whether the terminal device is allowed to report IDC auxiliary information based on TDM) through the first indication information.

[0151] After receiving the first configuration information, if the terminal device detects interference between GNSS reception and NTN transmission, the terminal device can trigger the UAI process and report one or more of the following information through the second field: the terminal device's preferred DRX period, the terminal device's preferred DRX wake-up duration, the terminal device's preferred DRX start time offset, and the terminal device's preferred DRX timeslot offset.

[0152] In some embodiments, to allow the DRX period to be greater than the duration of GNSS reception performed by the terminal device (e.g., greater than the maximum value of the duration of GNSS reception performed by the terminal device), the DRX period can be extended. For example, the DRX period can be extended to 20480 milliseconds or 40960 milliseconds. In this case, the preferred DRX period value reported by the terminal device can also be extended to the corresponding extended value (e.g., 20480 milliseconds or 40960 milliseconds).

[0153] In some embodiments, due to the extension of the DRX period, the range of the DRX start time offset also needs to be extended accordingly. For example, if the DRX period is extended to 40960 milliseconds, the range of the DRX start time offset also needs to be extended to 0-40959 milliseconds. Similarly, if the DRX period is extended to 20480 milliseconds, the range of the DRX start time offset also needs to be extended to 0-20479 milliseconds.

[0154] In some embodiments, the wake-up duration of DRX can also be extended. For example, the wake-up duration of DRX can be extended to 0, allowing the network device to not perform scheduling for the entire DRX cycle.

[0155] Example 2: The terminal device autonomously refuses to perform transmission on some or all of the uplink time domain resources of the NTN.

[0156] Figure 5 is a flowchart illustrating a method for wireless communication according to another embodiment of this application. The method shown in Figure 5 can be executed by a terminal device, such as the terminal devices shown in Figures 1-3. In some embodiments, the terminal device may refer to a terminal device accessing an NTN.

[0157] The method shown in Figure 5 includes step S510, which will be described below.

[0158] In step S510, if interference occurs between the GNSS reception and NTN transmission of the terminal device, the terminal device refuses to perform transmission on some or all of the uplink time domain resources of the NTN transmission. Alternatively, if interference occurs between the GNSS reception and NTN transmission of the terminal device, the terminal device autonomously refuses to perform transmission on some or all of the uplink time domain resources of the NTN transmission.

[0159] In some embodiments, the terminal device refuses to perform transmission on some or all uplink time domain resources of the NTN transmission, including: the terminal device refuses to perform transmission on K uplink time domain resources of the NTN transmission for a first valid duration, wherein the first valid duration and / or K may be configured by the network device. For example, K may be configured by the network device through third indication information. Another example is that the first valid duration may be configured by the network device through fourth indication information. However, the embodiments of this application are not limited to this; for example, the first valid duration and / or K may be predefined or preconfigured, such as protocol predefined.

[0160] In some embodiments, the method shown in FIG5 may further include step S505. In step S505, the terminal device receives second configuration information sent by the network device.

[0161] In some embodiments, the second configuration information is associated with the terminal device's refusal to perform transmission on some or all of the uplink time domain resources of the NTN transmission. Alternatively, the second configuration information is the configuration information obtained by the terminal device to voluntarily refuse uplink NTN transmission.

[0162] This application embodiment does not limit the content of the second configuration information. For example, the second configuration information may include one or more of the following: second indication information, third indication information, and fourth indication information.

[0163] In some embodiments, the second indication information can be used to indicate whether the terminal device is allowed to refuse to perform transmission on some or all of the uplink time domain resources of the NTN transmission. Alternatively, the second indication information can be used to indicate whether the terminal device is allowed to voluntarily refuse uplink NTN transmission.

[0164] This application does not limit the indication method of the second indication information in its embodiments. In some embodiments, the second indication information may explicitly indicate whether the terminal device is allowed to voluntarily refuse uplink NTN transmission. As one implementation, the second indication information may use one or more bits to indicate whether the terminal device is allowed to voluntarily refuse uplink NTN transmission. For example, when the value of the second indication information is a first value (e.g., 1), it indicates that the terminal device is allowed to voluntarily refuse uplink NTN transmission; when the value of the second indication information is a second value (e.g., 0), it indicates that the terminal device is not allowed to voluntarily refuse uplink NTN transmission. In other embodiments, the second indication information may implicitly indicate whether the terminal device is allowed to voluntarily refuse uplink NTN transmission. As one implementation, when the second indication information includes third and / or fourth indication information, it indicates that the terminal device is allowed to voluntarily refuse uplink NTN transmission.

[0165] In some embodiments, the third indication information can be used to indicate the number of uplink time domain resources that the terminal device is allowed to reject. This application does not limit the range of values ​​indicated by the third indication information (or, in other words, the number of uplink time domain resources that the terminal device is allowed to reject). In some embodiments, the maximum value indicated by the third indication information can be less than or equal to 30 time slots, such as 30 time slots. In other embodiments, the maximum value indicated by the third indication information can be greater than 30 time slots; for example, 50, 100, 200, 500, 1000, 2000, or 4000 time slots. This is because the terminal device receives GNSS for a relatively long time; therefore, the number of time slots that the terminal device can autonomously reject for uplink NTN transmission needs to be expanded to more, such as 50, 100, 200, 500, 1000, 2000, or 4000 time slots.

[0166] Taking an example where the maximum value of the third indication information is extended to 100 time slots, the value range of the third indication information can include 0-100 time slots. Taking an example where the maximum value of the third indication information is extended to 2000 time slots, the value range of the third indication information can include 0-2000 time slots.

[0167] In some embodiments, the third indication information can be indicated by the parameter autonomousDenialSlots.

[0168] In some embodiments, the fourth indication information can be used to indicate the effective duration for which the terminal device refuses to perform transmission on some or all of the uplink time domain resources of the NTN transmission. Alternatively, the fourth indication information can be used to indicate the effective duration for which the terminal device voluntarily refuses uplink NTN transmission.

[0169] This application does not limit the range of the value indicated by the fourth indication information (or, in other words, the effective duration for the terminal device to autonomously refuse uplink NTN transmission). In some embodiments, the maximum value of the fourth indication information may be less than or equal to 2000 time slots, such as 2000 time slots. In other embodiments, the maximum value of the fourth indication information may be greater than 2000 time slots, for example, 3000, 4000, 5000, 6000, or 8000 time slots. This is because the terminal device receives GNSS for a relatively long time; therefore, the effective duration for the terminal device to autonomously refuse uplink NTN transmission also needs to be extended to more, such as 3000, 4000, 5000, 6000, or 8000 time slots.

[0170] Taking an extension of the maximum value of the fourth indication information to 4000 time slots as an example, the value range of the fourth indication information can include 0-4000 time slots. Taking an extension of the maximum value of the fourth indication information to 6000 time slots as an example, the value range of the fourth indication information can include 0-6000 time slots.

[0171] In some embodiments, the fourth indication information can be indicated by the parameter autonomousDenialValidity.

[0172] In some embodiments, the value of the fourth indication information is greater than or equal to the value of the third indication information. For example, the value of the fourth indication information is 3000 time slots, while the value of the third indication information is 50 time slots.

[0173] This application does not limit the method of carrying the second configuration information. For example, the second configuration information can be carried by one or more of the following: RRC signaling, MAC signaling, and DCI.

[0174] In some embodiments, the second configuration information can be carried by dedicated signaling (such as RRC dedicated signaling). This application embodiment does not limit the RRC signaling (such as RRC dedicated signaling) carrying the second configuration information. Exemplarily, the RRC signaling carrying the second configuration information may include one or more of the following: RRC Reconfiguration message and RRC Resume message.

[0175] In some embodiments, after receiving the second configuration information, when the terminal device detects interference between GNSS reception and NTN transmission, the terminal device can autonomously refuse to perform transmission on some or all uplink time domain resources of NTN transmission based on the second configuration information. For example, the terminal device can refuse to perform transmission on K uplink time domain resources of NTN transmission within a first valid duration.

[0176] The method embodiments of this application have been described in detail above with reference to Figures 1 to 5. The apparatus embodiments of this application will be described in detail below with reference to Figures 6 to 10. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0177] Figure 6 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. The terminal device 600 shown in Figure 6 includes a transmitting module 610. The transmitting module 610 can be used to transmit first information to a network device, the first information being related to interference between GNSS reception and NTN transmission.

[0178] In some embodiments, the first information is used to indicate one or more of the following: interference information between the GNSS reception and the NTN transmission; relevant information regarding the terminal device performing the GNSS reception; and relevant information regarding the TDM preferred by the terminal device.

[0179] In some embodiments, the TDM-related information of the terminal device is indicated by the DRX parameter of the terminal device.

[0180] In some embodiments, the first information includes one or more of the following: affected NTN frequency information; start time of GNSS reception performed by the terminal device; offset of the start time of GNSS reception performed by the terminal device; duration of GNSS reception performed by the terminal device; effective duration of GNSS maintained by the terminal device; frequency information of the terminal device performing GNSS reception; DRX cycle preferred by the terminal device; wake-up duration of DRX preferred by the terminal device; DRX start time offset preferred by the terminal device; DRX slot offset preferred by the terminal device.

[0181] In some embodiments, the first information is carried by auxiliary information of the terminal device.

[0182] In some embodiments, the first information is carried by a first field of the auxiliary information, the first field being dedicated to carrying the first information; or, the first information is carried by a second field of the auxiliary information, the second field being used to carry IDC auxiliary information based on TDM or IDC auxiliary information based on Frequency Division Multiplexing (FDM).

[0183] In some embodiments, the DRX parameters preferred by the terminal device and / or the DRX parameters configured by the network device are determined based on relevant information obtained by the terminal device when performing the GNSS reception.

[0184] In some embodiments, the DRX period preferred by the terminal device and / or the DRX period configured by the network device is greater than or equal to the duration for which the terminal device performs the GNSS reception.

[0185] In some embodiments, the DRX period preferred by the terminal device and / or the DRX period configured by the network device is greater than 10240 milliseconds.

[0186] In some embodiments, the values ​​of the wake-up duration preferred by the terminal device and / or the wake-up duration configured by the network device include 0.

[0187] In some embodiments, the terminal device further includes a receiving module 620, configured to receive first configuration information sent by the network device, wherein the first configuration information is associated with the reporting of the first information.

[0188] In some embodiments, the first configuration information includes first indication information, which is used to indicate whether the terminal device is allowed to report the first information.

[0189] In some embodiments, the first indication information is used to indicate whether the terminal device is allowed to report the first information, including one or more of the following: whether the terminal device is allowed to report the first information based on a first field; whether the terminal device is allowed to report the first information based on a second field; wherein the first field is dedicated to carrying the first information, and the second field is used to carry IDC auxiliary information based on TDM or IDC auxiliary information based on FDM.

[0190] In some embodiments, the first configuration information is carried by RRC dedicated signaling.

[0191] In some embodiments, the transmitting module 610 may be a transceiver 1030. The terminal device 600 may also include a processor 1010 and a memory 1020, as shown in FIG10.

[0192] Figure 7 is a schematic diagram of the structure of a terminal device provided in another embodiment of this application. The terminal device 700 shown in Figure 7 includes a processing module 710. The processing module 710 can be used to refuse to perform transmission on some or all of the uplink time domain resources of the NTN transmission if interference occurs between the GNSS reception and NTN transmission of the terminal device.

[0193] In some embodiments, the terminal device further includes: a receiving module, configured to receive second configuration information sent by the network device, the second configuration information being associated with the terminal device's refusal to perform transmission on some or all of the uplink time domain resources of the NTN transmission.

[0194] In some embodiments, the second configuration information includes one or more of the following: second indication information for indicating whether the terminal device is allowed to refuse to perform transmission on some or all uplink time domain resources of the NTN transmission; third indication information for indicating the number of uplink time domain resources that the terminal device is allowed to refuse; and fourth indication information for indicating the effective duration for the terminal device to refuse to perform transmission on some or all uplink time domain resources of the NTN transmission.

[0195] In some embodiments, the maximum value indicated by the third indication information is greater than 30 time slots; and / or the maximum value indicated by the fourth indication information is greater than 2000 time slots.

[0196] In some embodiments, the second configuration information is carried via RRC dedicated signaling.

[0197] In some embodiments, the processing module 710 is further configured to: refuse to perform transmission on K uplink time domain resources of the NTN transmission within a first valid duration, wherein the first valid duration and / or the value of K is configured by the network device.

[0198] In some embodiments, the processing module 710 may be a processor 1010. The terminal device 700 may also include a transceiver 1030 and a memory 1020, as shown in FIG10.

[0199] Figure 8 is a schematic diagram of the structure of a network device provided in an embodiment of this application. The network device 800 shown in Figure 8 includes a receiving module 810. The receiving module 810 can be used to receive first information sent by a terminal device, the first information being related to interference between GNSS reception and NTN transmission.

[0200] In some embodiments, the first information is used to indicate one or more of the following: interference information between the GNSS reception and the NTN transmission; relevant information regarding the terminal device performing the GNSS reception; and relevant information regarding the TDM preferred by the terminal device.

[0201] In some embodiments, the TDM-related information of the terminal device is indicated by the DRX parameter of the terminal device.

[0202] In some embodiments, the first information includes one or more of the following: affected NTN frequency information; start time of GNSS reception performed by the terminal device; offset of the start time of GNSS reception performed by the terminal device; duration of GNSS reception performed by the terminal device; effective duration of GNSS maintained by the terminal device; frequency information of the terminal device performing GNSS reception; DRX cycle preferred by the terminal device; wake-up duration of DRX preferred by the terminal device; DRX start time offset preferred by the terminal device; DRX slot offset preferred by the terminal device.

[0203] In some embodiments, the first information is carried by auxiliary information of the terminal device.

[0204] In some embodiments, the first information is carried by a first field of the auxiliary information, the first field being dedicated to carrying the first information; or, the first information is carried by a second field of the auxiliary information, the second field being used to carry IDC auxiliary information based on TDM or IDC auxiliary information based on Frequency Division Multiplexing (FDM).

[0205] In some embodiments, the DRX parameters preferred by the terminal device and / or the DRX parameters configured by the network device are determined based on relevant information obtained by the terminal device when performing the GNSS reception.

[0206] In some embodiments, the DRX period preferred by the terminal device and / or the DRX period configured by the network device is greater than or equal to the duration for which the terminal device performs the GNSS reception.

[0207] In some embodiments, the DRX period preferred by the terminal device and / or the DRX period configured by the network device is greater than 10240 milliseconds.

[0208] In some embodiments, the values ​​of the wake-up duration preferred by the terminal device and / or the wake-up duration configured by the network device include 0.

[0209] In some embodiments, the network device further includes a sending module 820, configured to send first configuration information to a terminal device, wherein the first configuration information is associated with the reporting of the first information.

[0210] In some embodiments, the first configuration information includes first indication information, which is used to indicate whether the terminal device is allowed to report the first information.

[0211] In some embodiments, the first indication information is used to indicate whether the terminal device is allowed to report the first information, including one or more of the following: whether the terminal device is allowed to report the first information based on a first field; whether the terminal device is allowed to report the first information based on a second field; wherein the first field is dedicated to carrying the first information, and the second field is used to carry IDC auxiliary information based on TDM or IDC auxiliary information based on FDM.

[0212] In some embodiments, the first configuration information is carried by RRC dedicated signaling.

[0213] In some embodiments, the network device further includes a scheduling module, configured to schedule the GNSS reception and / or the NTN transmission based on the first information.

[0214] In some embodiments, the receiving module 810 may be a transceiver 1030. The network device 800 may also include a processor 1010 and a memory 1020, as shown in FIG10.

[0215] Figure 9 is a schematic diagram of a network device according to another embodiment of this application. The network device 900 shown in Figure 9 includes a transmitting module 910. The transmitting module 910 can be used to send second configuration information to a terminal device. The second configuration information is associated with the terminal device refusing to perform transmission on some or all uplink time domain resources of NTN transmission. The refusal of the terminal device to perform transmission on some or all uplink time domain resources of NTN transmission is performed when interference occurs between the GNSS reception and NTN transmission of the terminal device.

[0216] In some embodiments, the second configuration information includes one or more of the following: second indication information for indicating whether the terminal device is allowed to refuse to perform transmission on some or all uplink time domain resources of the NTN transmission; third indication information for indicating the number of uplink time domain resources that the terminal device is allowed to refuse; and fourth indication information for indicating the effective duration for the terminal device to refuse to perform transmission on some or all uplink time domain resources of the NTN transmission.

[0217] In some embodiments, the maximum value indicated by the third indication information is greater than 30 time slots; and / or the maximum value indicated by the fourth indication information is greater than 2000 time slots.

[0218] In some embodiments, the second configuration information is carried via RRC dedicated signaling.

[0219] In some embodiments, the terminal device refuses to perform transmission on some or all uplink time domain resources of NTN transmission, including: the terminal device refuses to perform transmission on K uplink time domain resources of NTN transmission for a first valid duration, wherein the first valid duration and / or the value of K is configured by the network device.

[0220] In some embodiments, the transmitting module 910 may be a transceiver 1030. The network device 900 may also include a processor 1010 and a memory 1020, as shown in FIG10.

[0221] Figure 10 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 10 indicate that the unit or module is optional. This device 1000 can be used to implement the methods described in the above method embodiments. The device 1000 can be a chip, a terminal device, or a network device.

[0222] Apparatus 1000 may include one or more processors 1010. The processor 1010 may support apparatus 1000 in implementing the methods described in the preceding method embodiments. The processor 1010 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0223] The apparatus 1000 may further include one or more memories 1020. The memories 1020 store a program that can be executed by the processor 1010, causing the processor 1010 to perform the methods described in the preceding method embodiments. The memories 1020 may be independent of the processor 1010 or integrated within the processor 1010.

[0224] The device 1000 may also include a transceiver 1030. The processor 1010 can communicate with other devices or chips via the transceiver 1030. For example, the processor 1010 can send and receive data with other devices or chips via the transceiver 1030.

[0225] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal device or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0226] This application also provides a computer program product. The computer program product includes a program. This computer program product can be applied to a terminal device or network device provided in the embodiments of this application, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0227] This application also provides a computer program. This computer program can be applied to the terminal device or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal device or network device in various embodiments of this application.

[0228] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0229] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0230] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0231] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0232] In the embodiments of this application, the term "comprising" can refer to direct inclusion or indirect inclusion. Optionally, "comprising" in the embodiments of this application can be replaced with "instructing" or "used to determine". For example, "A includes B" can be replaced with "A instructs B" or "A is used to determine B".

[0233] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0234] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0235] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0236] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

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

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

[0239] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0240] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

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

Claims

1. A method for wireless communication, characterized in that, include: The terminal device sends first information to the network device, which relates to interference between GNSS reception and NTN transmission.

2. The method according to claim 1, characterized in that, The first information is used to indicate one or more of the following: Interference information between the GNSS reception and the NTN transmission; The terminal device executes the relevant information received by the GNSS; The terminal device is inclined to use Time Division Multiplexing (TDM) related information.

3. The method according to claim 2, characterized in that, The relevant information of the TDM that the terminal device prefers is indicated by the discontinuous reception DRX parameter that the terminal device prefers.

4. The method according to any one of claims 1-3, characterized in that, The first information includes one or more of the following: Information on affected NTN frequencies; The start time for the terminal device to perform GNSS reception; The offset of the start time of the terminal device performing GNSS reception; The duration for which the terminal device performs GNSS reception; The effective duration of GNSS maintained by the terminal device; The terminal device performs GNSS reception of the frequency information; The DRX cycle preferred by the terminal device; The duration of wake-up for the DRX preferred by the terminal device; The DRX start time offset tended by the terminal device; The terminal device tends to have a DRX time slot offset.

5. The method according to any one of claims 1-4, characterized in that, The first information is carried by the auxiliary information of the terminal device.

6. The method according to claim 5, characterized in that: The first information is carried by a first field of the auxiliary information, and the first field is dedicated to carrying the first information; or, The first information is carried by the second field of the auxiliary information, which is used to carry auxiliary information of the device coexisting IDC based on TDM or auxiliary information of the IDC based on frequency division multiplexing (FDM).

7. The method according to any one of claims 1-6, characterized in that, The DRX parameters preferred by the terminal device and / or the DRX parameters configured by the network device are determined based on relevant information obtained by the terminal device when performing the GNSS reception.

8. The method according to claim 7, characterized in that, The DRX period preferred by the terminal device and / or the DRX period configured by the network device is greater than or equal to the duration for which the terminal device performs the GNSS reception.

9. The method according to claim 7 or 8, characterized in that, The terminal device tends to have a DRX period and / or the network device is configured to have a DRX period greater than 10240 milliseconds.

10. The method according to any one of claims 1-9, characterized in that, The values ​​of the wake-up duration preferred by the terminal device and / or the wake-up duration configured by the network device include 0.

11. The method according to any one of claims 1-10, characterized in that, The method further includes: The terminal device receives first configuration information sent by the network device, and the first configuration information is associated with the reporting of the first information.

12. The method according to claim 11, characterized in that, The first configuration information includes first indication information, which is used to indicate whether the terminal device is allowed to report the first information.

13. The method according to claim 12, characterized in that, The first indication information is used to indicate whether the terminal device is allowed to report the first information, including one or more of the following: Whether the terminal device is allowed to report the first information based on the first field; Whether the terminal device is allowed to report the first information based on the second field; The first field is dedicated to carrying the first information, and the second field is used to carry IDC auxiliary information based on TDM or IDC auxiliary information based on FDM.

14. The method according to any one of claims 11-13, characterized in that, The first configuration information is carried by the dedicated signaling of Radio Resource Control (RRC).

15. A method for wireless communication, characterized in that, include: If interference occurs during GNSS reception and NTN transmission on the terminal device, the terminal device will refuse to perform transmission on some or all of the uplink time domain resources of the NTN transmission.

16. The method according to claim 15, characterized in that, The method further includes: The terminal device receives second configuration information sent by the network device, the second configuration information being associated with the terminal device refusing to perform transmission on some or all of the uplink time domain resources of the NTN transmission.

17. The method according to claim 16, characterized in that, The second configuration information includes one or more of the following: The second indication information is used to indicate whether the terminal device is allowed to refuse to perform transmission on some or all of the uplink time domain resources of the NTN transmission; The third indication information is used to indicate the number of uplink time domain resources that the terminal device is allowed to reject; The fourth indication information is used to indicate the effective duration for which the terminal device refuses to perform transmission on part or all of the uplink time domain resources of the NTN transmission.

18. The method according to claim 17, characterized in that: The maximum value indicated by the third indication information is greater than 30 time slots; and / or The maximum value indicated by the fourth indication information is greater than 2000 time slots.

19. The method according to any one of claims 16-18, characterized in that, The second configuration information is carried by the dedicated signaling of Radio Resource Control (RRC).

20. The method according to any one of claims 15-19, characterized in that, The terminal device refuses to perform transmission on some or all of the uplink time domain resources of the NTN transmission, including: The terminal device refuses to perform transmission on K uplink time domain resources of the NTN transmission within a first valid duration, wherein the first valid duration and / or the value of K is configured by the network device.

21. A method for wireless communication, characterized in that, include: The network device receives first information sent by the terminal device, the first information being related to interference between GNSS reception and NTN transmission.

22. The method according to claim 21, characterized in that, The first information is used to indicate one or more of the following: Interference information between the GNSS reception and the NTN transmission; The terminal device executes the relevant information received by the GNSS; The terminal device is inclined to use Time Division Multiplexing (TDM) related information.

23. The method according to claim 22, characterized in that, The relevant information of the TDM that the terminal device prefers is indicated by the discontinuous reception DRX parameter that the terminal device prefers.

24. The method according to any one of claims 21-23, characterized in that, The first information includes one or more of the following: Information on affected NTN frequencies; The start time for the terminal device to perform GNSS reception; The offset of the start time of the terminal device performing GNSS reception; The duration for which the terminal device performs GNSS reception; The effective duration of GNSS maintained by the terminal device; The terminal device performs GNSS reception of the frequency information; The DRX cycle preferred by the terminal device; The duration of wake-up for the DRX preferred by the terminal device; The DRX start time offset tended by the terminal device; The terminal device tends to have a DRX time slot offset.

25. The method according to any one of claims 21-24, characterized in that, The first information is carried by the auxiliary information of the terminal device.

26. The method according to claim 25, characterized in that: The first information is carried by a first field of the auxiliary information, and the first field is dedicated to carrying the first information; or, The first information is carried by the second field of the auxiliary information, which is used to carry auxiliary information of the device coexisting IDC based on TDM or auxiliary information of the IDC based on frequency division multiplexing (FDM).

27. The method according to any one of claims 21-26, characterized in that, The DRX parameters preferred by the terminal device and / or the DRX parameters configured by the network device are determined based on relevant information obtained by the terminal device when performing the GNSS reception.

28. The method according to claim 27, characterized in that, The DRX period preferred by the terminal device and / or the DRX period configured by the network device is greater than or equal to the duration for which the terminal device performs the GNSS reception.

29. The method according to claim 27 or 28, characterized in that, The terminal device tends to have a DRX period and / or the network device is configured to have a DRX period greater than 10240 milliseconds.

30. The method according to any one of claims 21-29, characterized in that, The values ​​of the wake-up duration preferred by the terminal device and / or the wake-up duration configured by the network device include 0.

31. The method according to any one of claims 21-30, characterized in that, The method further includes: The network device sends first configuration information to the terminal device, and the first configuration information is associated with the reporting of the first information.

32. The method according to claim 31, characterized in that, The first configuration information includes first indication information, which is used to indicate whether the terminal device is allowed to report the first information.

33. The method according to claim 32, characterized in that, The first indication information is used to indicate whether the terminal device is allowed to report the first information, including one or more of the following: Whether the terminal device is allowed to report the first information based on the first field; Whether the terminal device is allowed to report the first information based on the second field; The first field is dedicated to carrying the first information, and the second field is used to carry IDC auxiliary information based on TDM or IDC auxiliary information based on FDM.

34. The method according to any one of claims 31-33, characterized in that, The first configuration information is carried by the dedicated signaling of Radio Resource Control (RRC).

35. The method according to any one of claims 21-34, characterized in that, The method further includes: The network device schedules the GNSS reception and / or the NTN transmission based on the first information.

36. A method for wireless communication, characterized in that, include: The network device sends second configuration information to the terminal device, the second configuration information being associated with the terminal device refusing to perform transmission on some or all uplink time domain resources of the non-terrestrial network NTN transmission, wherein the terminal device refusing to perform transmission on some or all uplink time domain resources of the NTN transmission is performed when interference occurs between the terminal device's Global Navigation Satellite System (GNSS) reception and NTN transmission.

37. The method according to claim 36, characterized in that, The second configuration information includes one or more of the following: The second indication information is used to indicate whether the terminal device is allowed to refuse to perform transmission on some or all of the uplink time domain resources of the NTN transmission; The third indication information is used to indicate the number of uplink time domain resources that the terminal device is allowed to reject; The fourth indication information is used to indicate the effective duration for which the terminal device refuses to perform transmission on part or all of the uplink time domain resources of the NTN transmission.

38. The method according to claim 37, characterized in that: The maximum value indicated by the third indication information is greater than 30 time slots; and / or The maximum value indicated by the fourth indication information is greater than 2000 time slots.

39. The method according to any one of claims 36-38, characterized in that, The second configuration information is carried by the dedicated signaling of Radio Resource Control (RRC).

40. The method according to any one of claims 36-39, characterized in that, The terminal device refuses to perform transmissions on some or all of the uplink time domain resources of NTN transmissions, including: The terminal device refuses to perform transmission on K uplink time domain resources of the NTN transmission within a first valid duration, wherein the first valid duration and / or the value of K is configured by the network device.

41. A terminal device, characterized in that, include: The transmitting module is used to send first information to network devices, the first information being related to interference between GNSS reception and NTN transmission.

42. The terminal device according to claim 41, characterized in that, The first information is used to indicate one or more of the following: Interference information between the GNSS reception and the NTN transmission; The terminal device executes the relevant information received by the GNSS; The terminal device is inclined to use Time Division Multiplexing (TDM) related information.

43. The terminal device according to claim 42, characterized in that, The relevant information of the TDM that the terminal device prefers is indicated by the discontinuous reception DRX parameter that the terminal device prefers.

44. The terminal device according to any one of claims 41-43, characterized in that, The first information includes one or more of the following: Information on affected NTN frequencies; The start time for the terminal device to perform GNSS reception; The offset of the start time of the terminal device performing GNSS reception; The duration for which the terminal device performs GNSS reception; The effective duration of GNSS maintained by the terminal device; The terminal device performs GNSS reception of the frequency information; The DRX cycle preferred by the terminal device; The duration of wake-up for the DRX preferred by the terminal device; The DRX start time offset tended by the terminal device; The terminal device tends to have a DRX time slot offset.

45. The terminal device according to any one of claims 41-44, characterized in that, The first information is carried by the auxiliary information of the terminal device.

46. ​​The terminal device according to claim 45, characterized in that: The first information is carried by a first field of the auxiliary information, and the first field is dedicated to carrying the first information; or, The first information is carried by the second field of the auxiliary information, which is used to carry auxiliary information of the device coexisting IDC based on TDM or auxiliary information of the IDC based on frequency division multiplexing (FDM).

47. The terminal device according to any one of claims 41-46, characterized in that, The DRX parameters preferred by the terminal device and / or the DRX parameters configured by the network device are determined based on relevant information obtained by the terminal device when performing the GNSS reception.

48. The terminal device according to claim 47, characterized in that, The DRX period preferred by the terminal device and / or the DRX period configured by the network device is greater than or equal to the duration for which the terminal device performs the GNSS reception.

49. The terminal device according to claim 47 or 48, characterized in that, The terminal device tends to have a DRX period and / or the network device is configured to have a DRX period greater than 10240 milliseconds.

50. The terminal device according to any one of claims 41-49, characterized in that, The values ​​of the wake-up duration preferred by the terminal device and / or the wake-up duration configured by the network device include 0.

51. The terminal device according to any one of claims 41-50, characterized in that, The terminal device also includes: The receiving module is used to receive first configuration information sent by the network device, wherein the first configuration information is associated with the reporting of the first information.

52. The terminal device according to claim 51, characterized in that, The first configuration information includes first indication information, which is used to indicate whether the terminal device is allowed to report the first information.

53. The terminal device according to claim 52, characterized in that, The first indication information is used to indicate whether the terminal device is allowed to report the first information, including one or more of the following: Whether the terminal device is allowed to report the first information based on the first field; Whether the terminal device is allowed to report the first information based on the second field; The first field is dedicated to carrying the first information, and the second field is used to carry IDC auxiliary information based on TDM or IDC auxiliary information based on FDM.

54. The terminal device according to any one of claims 51-53, characterized in that, The first configuration information is carried by the dedicated signaling of Radio Resource Control (RRC).

55. A terminal device, characterized in that, include: The processing module is configured to refuse to perform transmission on some or all of the uplink time domain resources of the NTN transmission if interference occurs in the GNSS reception of the terminal device and the NTN transmission.

56. The terminal device according to claim 55, characterized in that, The terminal device also includes: The receiving module is configured to receive second configuration information sent by the network device, wherein the second configuration information is associated with the terminal device's refusal to perform transmission on some or all of the uplink time domain resources of the NTN transmission.

57. The terminal device according to claim 56, characterized in that, The second configuration information includes one or more of the following: The second indication information is used to indicate whether the terminal device is allowed to refuse to perform transmission on some or all of the uplink time domain resources of the NTN transmission; The third indication information is used to indicate the number of uplink time domain resources that the terminal device is allowed to reject; The fourth indication information is used to indicate the effective duration for which the terminal device refuses to perform transmission on part or all of the uplink time domain resources of the NTN transmission.

58. The terminal device according to claim 57, characterized in that: The maximum value indicated by the third indication information is greater than 30 time slots; and / or The maximum value indicated by the fourth indication information is greater than 2000 time slots.

59. The terminal device according to any one of claims 56-58, characterized in that, The second configuration information is carried by the dedicated signaling of Radio Resource Control (RRC).

60. The terminal device according to any one of claims 55-59, characterized in that, The processing module is further used for: For a first valid duration, transmission on K uplink time-domain resources of the NTN transmission is refused, wherein the first valid duration and / or the value of K is configured by the network device.

61. A network device, characterized in that, include: The receiving module is used to receive first information sent by the terminal device, which is related to interference between GNSS reception and NTN transmission.

62. The network device according to claim 61, characterized in that, The first information is used to indicate one or more of the following: Interference information between the GNSS reception and the NTN transmission; The terminal device executes the relevant information received by the GNSS; The terminal device is inclined to use Time Division Multiplexing (TDM) related information.

63. The network device according to claim 62, characterized in that, The relevant information of the TDM that the terminal device prefers is indicated by the discontinuous reception DRX parameter that the terminal device prefers.

64. The network device according to any one of claims 61-63, characterized in that, The first information includes one or more of the following: Information on affected NTN frequencies; The start time for the terminal device to perform GNSS reception; The offset of the start time of the terminal device performing GNSS reception; The duration for which the terminal device performs GNSS reception; The effective duration of GNSS maintained by the terminal device; The terminal device performs GNSS reception of the frequency information; The DRX cycle preferred by the terminal device; The duration of wake-up for the DRX preferred by the terminal device; The DRX start time offset tended by the terminal device; The terminal device tends to have a DRX time slot offset.

65. The network device according to any one of claims 61-64, characterized in that, The first information is carried by the auxiliary information of the terminal device.

66. The network device according to claim 65, characterized in that: The first information is carried by a first field of the auxiliary information, and the first field is dedicated to carrying the first information; or, The first information is carried by the second field of the auxiliary information, which is used to carry auxiliary information of the device coexisting IDC based on TDM or auxiliary information of the IDC based on frequency division multiplexing (FDM).

67. The network device according to any one of claims 61-66, characterized in that, The DRX parameters preferred by the terminal device and / or the DRX parameters configured by the network device are determined based on relevant information obtained by the terminal device when performing the GNSS reception.

68. The network device according to claim 67, characterized in that, The DRX period preferred by the terminal device and / or the DRX period configured by the network device is greater than or equal to the duration for which the terminal device performs the GNSS reception.

69. The network device according to claim 67 or 68, characterized in that, The terminal device tends to have a DRX period and / or the network device is configured to have a DRX period greater than 10240 milliseconds.

70. The network device according to any one of claims 61-69, characterized in that, The values ​​of the wake-up duration preferred by the terminal device and / or the wake-up duration configured by the network device include 0.

71. The network device according to any one of claims 61-70, characterized in that, The network device also includes: The sending module is used to send first configuration information to the terminal device, wherein the first configuration information is associated with the reporting of the first information.

72. The network device according to claim 71, characterized in that, The first configuration information includes first indication information, which is used to indicate whether the terminal device is allowed to report the first information.

73. The network device according to claim 72, characterized in that, The first indication information is used to indicate whether the terminal device is allowed to report the first information, including one or more of the following: Whether the terminal device is allowed to report the first information based on the first field; Whether the terminal device is allowed to report the first information based on the second field; The first field is dedicated to carrying the first information, and the second field is used to carry IDC auxiliary information based on TDM or IDC auxiliary information based on FDM.

74. The network device according to any one of claims 71-73, characterized in that, The first configuration information is carried by the dedicated signaling of Radio Resource Control (RRC).

75. The network device according to any one of claims 61-74, characterized in that, The network device also includes: The scheduling module is used to schedule the GNSS reception and / or the NTN transmission based on the first information.

76. A network device, characterized in that, include: The sending module is used to send second configuration information to the terminal device. The second configuration information is associated with the terminal device refusing to perform transmission on some or all uplink time domain resources of non-terrestrial network NTN transmission. The refusal of the terminal device to perform transmission on some or all uplink time domain resources of NTN transmission is performed when interference occurs between the terminal device's GNSS reception and NTN transmission.

77. The network device according to claim 76, characterized in that, The second configuration information includes one or more of the following: The second indication information is used to indicate whether the terminal device is allowed to refuse to perform transmission on some or all of the uplink time domain resources of the NTN transmission; The third indication information is used to indicate the number of uplink time domain resources that the terminal device is allowed to reject; The fourth indication information is used to indicate the effective duration for which the terminal device refuses to perform transmission on part or all of the uplink time domain resources of the NTN transmission.

78. The network device according to claim 77, characterized in that: The maximum value indicated by the third indication information is greater than 30 time slots; and / or The maximum value indicated by the fourth indication information is greater than 2000 time slots.

79. The network device according to any one of claims 76-78, characterized in that, The second configuration information is carried by the dedicated signaling of Radio Resource Control (RRC).

80. The network device according to any one of claims 76-79, characterized in that, The terminal device refuses to perform transmissions on some or all of the uplink time domain resources of NTN transmissions, including: The terminal device refuses to perform transmission on K uplink time domain resources of the NTN transmission within a first valid duration, wherein the first valid duration and / or the value of K is configured by the network device.

81. A terminal device, characterized in that, It includes a memory and a processor, the memory being used to store a program, and the processor being used to invoke the program in the memory to cause the terminal device to perform the method as described in any one of claims 1-14 or 15-20.

82. A network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the network device performs the method as described in any one of claims 21-35 or 36-40.

83. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-14, 15-20, 21-35, or 36-40.

84. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-14, 15-20, 21-35, or 36-40.

85. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-14, 15-20, 21-35, or 36-40.

86. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-14, 15-20, 21-35, or 36-40.

87. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-14, 15-20, 21-35, or 36-40.

Images