Wireless communication method, terminal device, and network device

Abstract

The embodiments of the present application provide a wireless communication method, a terminal device, and a network device, the method including: a terminal device receiving a first control channel, the first control channel corresponding to a first shared channel; and the terminal device not monitoring a control channel candidate in any time unit from a first time unit to a second time unit. In an IoT-NTN system, by designating a time period during which the terminal device does not monitor a control channel candidate, i.e., any time unit from the first time unit to the second time unit, normal operation of a terminal device that does not have a function for simultaneously transmitting and receiving signals can be ensured, and a power saving effect can also be obtained.

Description

[Technical Field]

[0001] FIELD Embodiments of the present application relate to the field of communications, and more particularly to a wireless communication method, a terminal device, and a network device. [Background technology]

[0002] Terminal devices in an Internet of Things (IoT-NTN) system use a Global Navigation Satellite System (GNSS) module, and the functions of transmitting and receiving signals in the IoT-NTN system cannot be used simultaneously. Terminal devices may also not have the capability to simultaneously transmit and receive signals. Furthermore, due to the large propagation delay in the NTN system, i.e., the large range of TA values, the uplink-downlink timing relationship in a terrestrial network (TN) system cannot be applied to the uplink-downlink timing relationship in an IoT-NTN system. Furthermore, terminal devices in an IoT-NTN system cannot efficiently monitor the control channel, resulting in reduced communication reliability.

[0003] Therefore, how to effectively prevent terminal devices in IoT-NTN systems from monitoring the control channel in order to improve communication reliability is a technical problem that needs to be solved urgently in this field. Summary of the Invention [Problem to be solved by the invention]

[0004] The embodiments of the present application provide a wireless communication method, terminal device, and network device that ensure normal operation of terminal devices that do not have the ability to simultaneously send and receive signals in an IoT-NTN system, improving communication reliability and also achieving power saving effects. [Means for solving the problem]

[0005] In a first aspect, the present application provides a wireless communication method, the method comprising: a terminal device receiving a first control channel, the first control channel corresponding to a first shared channel; The terminal device does not monitor control channel candidates in any time unit from the first time unit to the second time unit; Here, the first time unit is determined based on at least one of n, n+k, and n+m, and the second time unit is determined based on at least one of n, n+k, and n+m, where n represents the time unit in which the end position of the first control channel is located, n+k represents the time unit in which the transmission start position of the first shared channel is located, and n+m represents the time unit in which the transmission end position of the first shared channel is located.

[0006] In a second aspect, the present application provides a wireless communication method, the method comprising: a network device transmitting a first control channel, the first control channel corresponding to a first shared channel; The network device does not transmit a control channel candidate in any time unit from a first time unit to a second time unit; Here, the first time unit is determined based on at least one of n, n+k, and n+m, and the second time unit is determined based on at least one of n, n+k, and n+m, where n represents the time unit in which the end position of the first control channel is located, n+k represents the time unit in which the transmission start position of the first shared channel is located, and n+m represents the time unit in which the transmission end position of the first shared channel is located.

[0007] In a third aspect, the present application provides a wireless communication method, the method comprising: a terminal device transmitting a first shared channel; The terminal device does not monitor control channel candidates and / or does not receive data within a half-duplex protection interval or in any time unit from a first time unit to a second time unit, where the first time unit is determined based on s and the second time unit is determined based on s, and s represents the time unit in which the transmission end position of the first shared channel is located.

[0008] In a fourth aspect, the present application provides a wireless communication method, the method comprising: receiving, by a network device, a first shared channel; The network device does not transmit a control channel candidate and / or does not transmit data within a half-duplex protection interval or in any time unit from a first time unit to a second time unit, wherein the first time unit is determined based on s, and the second time unit is determined based on s, and s represents the time unit in which the transmission end position of the first shared channel is located.

[0009] In a fifth aspect, the present application provides a terminal device for performing the method of the first aspect, the third aspect, or any of the embodiments thereof, specifically, the terminal device comprising a functional module configured to perform the method of the first aspect, the third aspect, or any of the embodiments thereof.

[0010] In one embodiment, the terminal device may comprise a processing unit for performing functions related to information processing, for example, the processing unit may be a processor.

[0011] In one embodiment, the terminal device may include a transmitting unit and / or a receiving unit. The transmitting unit is for performing a function related to transmission, and the receiving unit is for performing a function related to reception. For example, the transmitting unit may be a transmitter or an emitter, and the receiving unit may be a receiver or an acceptor. In yet another example, if the terminal device is a communication chip, the transmitting unit may be an input circuit or an interface of the communication chip, and the transmitting unit may be an output circuit or an interface of the communication chip.

[0012] In a sixth aspect, the present application provides a network device for performing the method of the second aspect, the fourth aspect, or any of the embodiments described above. Specifically, the network device comprises a functional module configured to perform the method of the second aspect, the fourth aspect, or any of the embodiments described above.

[0013] In one embodiment, the network device may include a processing unit for performing functions related to information processing, for example, the processing unit may be a processor.

[0014] In one embodiment, the network device may include a transmitting unit and / or a receiving unit. The transmitting unit is for performing a function related to transmission, and the receiving unit is for performing a function related to reception. For example, the transmitting unit may be a transmitter or an emitter, and the receiving unit may be a receiver or an acceptor. In yet another example, the network device is a communications chip, the receiving unit may be an input circuit or an interface of the communications chip, and the transmitting unit may be an output circuit or an interface of the communications chip.

[0015] In a seventh aspect, the present application provides a terminal device comprising a processor and a memory, the memory being configured to store a computer program, the processor calling and executing the computer program stored in the memory to perform the method of the first aspect, the third aspect or any of the embodiments thereof.

[0016] In one embodiment, the processor(s) is / are one or more, and the memory(s) is / are one or more.

[0017] In one embodiment, the memory may be integrated with the processor or may be separate from the processor.

[0018] In one embodiment, the terminal device further comprises a transmitter (emitter) and a receiver (acceptor).

[0019] In an eighth aspect, the present application provides a network device comprising a processor and a memory, wherein the memory is configured to store a computer program, and the processor executes the method of the second aspect, the fourth aspect, or any of the embodiments thereof by calling and executing the computer program stored in the memory.

[0020] In one embodiment, the processor(s) is / are one or more, and the memory(s) is / are one or more.

[0021] In one embodiment, the memory may be integrated with the processor or may be separate from the processor.

[0022] In one embodiment, the network device further comprises a transmitter (emitter) and a receiver (acceptor).

[0023] In a ninth aspect, the present application provides a chip for implementing the method of any one of the first to fourth aspects or their respective implementations. Specifically, the chip includes a processor, and the processor calls and executes a computer program from a memory, thereby implementing the method of any one of the first to fourth aspects or their respective implementations in a device equipped with the chip.

[0024] In a tenth aspect, the present application provides a computer-readable storage medium for storing a computer program, the computer program causing a computer to execute a method in any one of the first to fourth aspects above or each implementation form thereof.

[0025] In an eleventh aspect, the present application provides a computer program product including computer program instructions, the computer program instructions causing a computer to perform a method according to any one of the first to fourth aspects above or each implementation thereof.

[0026] In a twelfth aspect, the present application provides a computer program, which, when executed by a computer, causes the computer to execute the method of any one of the first to fourth aspects above or each of their realizations.

[0027] According to the above technical solution, in the IoT-NTN system, by specifying a time period during which the terminal device does not monitor control channel candidates, i.e., any time unit from the first time unit to the second time unit, it is possible to ensure the normal operation of terminal devices that do not have the function of simultaneously transmitting and receiving signals, and also to achieve power saving effects. [Brief explanation of the drawings]

[0028] [Figure 1] FIG. 1 is a schematic block diagram of a system framework according to an embodiment of the present application. [Figure 2] FIG. 1 is a schematic block diagram of a system framework according to an embodiment of the present application. [Figure 3] FIG. 1 is a schematic block diagram of a system framework according to an embodiment of the present application. [Figure 4] Schematic diagrams of NTN scenes based on transparent and regenerative transmission satellites are shown, respectively. [Figure 5] Schematic diagrams of NTN scenes based on transparent and regenerative transmission satellites are shown, respectively. [Figure 6] 1 illustrates an example of timing relationships in an IoT-NTN system according to an embodiment of the present application. [Figure 7] 1 illustrates an example of timing relationships in an IoT-NTN system according to an embodiment of the present application. [Figure 8] 1 illustrates an example of a control channel monitoring method in an NB-IoT system according to an embodiment of the present application. [Figure 9] 1 illustrates an example of a control channel monitoring method in an NB-IoT system according to an embodiment of the present application. [Figure 10] 1 illustrates an example of a control channel monitoring method in an NB-IoT system according to an embodiment of the present application. [Figure 11] 1 illustrates an example of a control channel monitoring method in an NB-IoT system according to an embodiment of the present application. [Figure 12] 1 illustrates an example of a control channel monitoring method in an NB-IoT system according to an embodiment of the present application. [Figure 13] 1 illustrates an exemplary interaction diagram of a wireless communication method according to an embodiment of the present application. [Figure 14] 3 illustrates an example of a first time unit and a second time unit according to an embodiment of the present application. [Figure 15] 3 illustrates an example of a first time unit and a second time unit according to an embodiment of the present application. [Figure 16] 1 illustrates another exemplary interaction diagram of a wireless communication method according to an embodiment of the present application. [Figure 17] 10 illustrates another example of a first time unit and a second time unit according to an embodiment of the present application. [Figure 18] 10 illustrates another example of a first time unit and a second time unit according to an embodiment of the present application. [Figure 19]FIG. 2 is an exemplary block diagram of a terminal device according to an embodiment of the present application. [Figure 20] FIG. 1 is an exemplary block diagram of a network device according to an embodiment of the present application. [Figure 21] FIG. 1 is an exemplary block diagram of a communication device according to an embodiment of the present application. [Figure 22] FIG. 1 is an exemplary block diagram of a chip according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0029] The following describes the technical solutions of the embodiments of the present application with reference to the drawings.

[0030] FIG. 1 is a schematic diagram of an application scene of an embodiment of the present invention.

[0031] 1, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 can communicate with the terminal device 110 via an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120.

[0032] Although the embodiments of the present application are exemplarily described using only the communication system 100, the embodiments of the present application are not limited thereto. That is, the technical solutions in the embodiments of the present application can be applied to various communication systems, such as a Long Term Evolution (LTE) system, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunication System (UMTS), an Internet of Things (IoT) system, a Narrow Band Internet of Things (NB-IoT) system, an enhanced Machine-Type Communications (eMTC) system, a 5G communication system (also called a New Radio (NR) communication system), or future communication systems.

[0033] 1, the network equipment 120 may be access network equipment that communicates with the terminal equipment 110. The access network equipment may provide communication coverage to a particular geographic area and may communicate with the terminal equipment 110 (e.g., UE) located within the coverage.

[0034] The network device 120 may be an evolved base station (eNB or eNode B: Evolutional Node B) in a Long Term Evolution (LTE) system, a base station (gNB) in a Next Generation Radio Access Network (NG RAN) or NR system, or a radio controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a network bridge, a router, or a network device in a future evolved Public Land Mobile Network (PLMN).

[0035] Terminal device 110 may be any terminal device, including, but not limited to, a terminal device that is connected to network device 120 or other terminal devices via wired or wireless connections.

[0036] For example, the terminal device 110 may refer to an access terminal, User Equipment (UE), user unit, subscriber station, mobile station, mobile console, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment. The access terminal may be a mobile phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), 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 of a 5G network, or a terminal device of a future evolved network, etc.

[0037] The terminal device 110 can be used for D2D (Device to Device) communication.

[0038] The wireless communication system 100 may further include a core network device 130 that communicates with a base station. The core network device 130 may be a 5G core network (5GC: 5G Core) device, such as an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), a User Plane Function (UPF), and a Session Management Function (SMF). Optionally, the core network device 130 may be an Evolved Packet Core (EPC) device of an LTE network, such as a Session Management Function + Core Packet Gateway (SMF + PGW-C) device. The SMF + PGW-C can simultaneously implement the functions that the SMF and the PGW-C can implement. In the course of network evolution, the above-mentioned core network devices may be called by other names, and new network entities may be formed by dividing the core network functions, but the embodiments of the present application are not limited thereto.

[0039] Communication between the functional units in the communication system 100 can be achieved by establishing connections via next generation network (NG) interfaces.

[0040] For example, a terminal device may establish an air interface connection with an access network device via an NR interface to transmit user plane data and control plane signaling. The terminal device may establish a control plane signaling connection with an AMF via NG interface 1 (abbreviated as N1). An access network device, such as a next-generation radio access network base station (gNB), may establish a user plane data connection with a UPF via NG interface 3 (abbreviated as N3). The access network device may establish a control plane signaling connection with an AMF via NG interface 2 (abbreviated as N2). The UPF may establish a control plane signaling connection with an SMF via NG interface 4 (abbreviated as N4). The UPF may interact with a data network via NG interface 6 (abbreviated as N6). The AMF may establish a control plane signaling connection with an SMF via NG interface 11 (abbreviated as N11). The SMF may establish a control plane signaling connection with a PCF via NG interface 7 (abbreviated as N7).

[0041] FIG. 1 exemplarily illustrates one base station, one core network device, and two terminal devices; optionally, the wireless communication system 100 may include multiple base station devices, and the coverage of each base station may include other numbers of terminal devices, and the embodiments of the present application are not limited thereto.

[0042] 3GPP is researching non-terrestrial network (NTN) technology, which will provide communication services to terrestrial users via satellite communications. Satellite communications have many unique advantages over terrestrial cellular communications. First, satellite communications are not limited by geographic location. For example, conventional terrestrial communications cannot cover areas where communication facilities cannot be installed, such as oceans, mountains, and deserts, or areas with low population density that cannot provide communication coverage. However, satellite communications can cover a wide area of ​​the Earth, and because satellites can orbit the Earth, theoretically, every corner of the planet can be reached by satellite communications. Second, satellite communications have greater social value. Satellite communications can reach remote areas, mountainous regions, and poor and underdeveloped countries and regions at low cost, allowing people in these regions to enjoy advanced voice communications and mobile Internet technology, narrowing the digital divide with developed regions and promoting their development. Second, satellite communications have long range, and communication costs do not increase significantly even as the distance increases. Finally, satellite communications are highly stable and are not affected by natural disasters.

[0043] NTN technology can be combined with various communication systems. For example, NTN technology can be combined with an NR system to form an NR-NTN system. In another example, NTN technology can be combined with an Internet of Things (IoT) system to form an IoT-NTN system. For example, an IoT-NTN system can include an NB-IoT-NTN system and an eMTC-NTN system.

[0044] FIG. 2 is a schematic diagram of the architecture of a communication system according to an embodiment of the present application.

[0045] As shown in FIG. 2 , the communication system includes a terminal device 1101 and a satellite 1102, and wireless communication is possible between the terminal device 1101 and the satellite 1102. The network formed between the terminal device 1101 and the satellite 1102 may also be referred to as an NTN. In the communication system architecture shown in FIG. 2 , the satellite 1102 functions as a base station, and direct communication is possible between the terminal device 1101 and the satellite 1102. In the system architecture, the satellite 1102 may also be referred to as a network device. In some embodiments of the present application, the communication system may include multiple network devices 1102, and the coverage of each network device 1102 may include other numbers of terminal devices, and the embodiments of the present application are not limited thereto.

[0046] FIG. 3 is a schematic diagram of the architecture of a communication system according to an embodiment of the present application.

[0047] As shown in FIG. 3 , the communication system includes a terminal device 1201, a satellite 1202, and a base station 1203. Wireless communication is possible between the terminal device 1201 and the satellite 1202, and communication is possible between the satellite 1202 and the base station 1203. The network formed among the terminal device 1201, the satellite 1202, and the base station 1203 may also be referred to as an NTN. In the communication system architecture shown in FIG. 3 , the satellite 1202 may not function as a base station, and communication between the terminal device 1201 and the base station 1203 must be relayed via the satellite 1202. In the system architecture, the base station 1203 may also be referred to as a network device. In some embodiments of the present application, the communication system may include multiple network devices 1203, and the coverage of each network device 1203 may include other numbers of terminal devices; the embodiments of the present application are not limited thereto. The network device 1203 may be the network device 120 in FIG. 1.

[0048] The satellite 1102 or 1202 is These include, but are not limited to, low Earth orbit (LEO) satellites, medium Earth orbit (MEO) satellites, geostationary Earth orbit (GEO) satellites, and highly elliptical orbit (HEO) satellites. Satellites can employ multiple beams to cover the ground; for example, one satellite can form tens to hundreds of beams to cover the ground. In other words, satellite beams can cover a ground area tens to hundreds of kilometers in diameter, which not only ensures satellite coverage but also improves the system capacity of the entire satellite communication system.

[0049] For example, the altitude range of LEO is 500km to 1500km, the corresponding orbital period is approximately 1.5 to 2 hours, the signal propagation delay for single-hop communication between users is generally less than 20ms, the maximum satellite visibility time is 20 minutes, the signal propagation distance in LEO is short, the link loss is small, and the requirements for the transmission power of user terminals are not high.The orbital altitude of GEO is 35,786km, the rotation period around the Earth is 24 hours, and the signal propagation delay for single-hop communication between users is generally 250ms.

[0050] To ensure satellite coverage and increase the overall system capacity of satellite communication systems, satellites use multiple beams to cover the ground. A single satellite can form tens to hundreds of beams to cover the ground, and a single satellite beam can cover a ground area tens to hundreds of kilometers in diameter.

[0051] 1 to 3 exemplify systems to which the present application is applied, and the methods described in the embodiments of the present application can also be applied to other systems. The terms "system" and "network" are used interchangeably throughout the present specification. The term "and / or" used herein describes only an associated relationship and indicates that three relationships may exist. For example, A and / or B can indicate three cases: A exists independently, both A and B exist, and B exists independently. The symbol " / " used herein generally indicates that the relationship between associated objects is an "or" relationship. The term "indicate" in the embodiments of the present application may indicate directly or indirectly, or may indicate a relationship. For example, A indicating B can indicate that A directly indicates B, e.g., that B can be obtained by A, or that A indirectly indicates B, e.g., that A indicates C and B can be obtained via C, or that A and B have an associated relationship. Furthermore, the term "corresponding" referred to in the embodiments of the present application may indicate a direct or indirect correspondence between two things, an association relationship between two things, or a relationship such as indicating and being indicated, configuring and being configured, etc. Furthermore, the "predefined" or "predefined rule" referred to in the embodiments of the present application may be realized by storing corresponding codes, forms, or other methods that can be used to indicate related information in a device (e.g., including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, "predefined" means defined by a protocol. Furthermore, in the embodiments of the present application, the "protocol" may refer to a standard protocol in the communications field, and may include, for example, an LTE protocol, an NR protocol, and related protocols applied to future communication systems, and the present application is not limited thereto.

[0052] Satellites can be classified into transparent payload and regenerative payload types based on the functions they provide. Transparent payload satellites only provide radio frequency filtering, frequency conversion, and amplification functions, and only transmit signals transparently without changing the transmitted waveform signals. Regenerative payload satellites can provide radio frequency filtering, frequency conversion, and amplification, as well as demodulation / decoding, routing / conversion, and symbolization / modulation functions, and have some or all of the functions of a base station.

[0053] The NTN may include one or more gateways for communication between satellites and terminals.

[0054] Figures 4 and 5 show schematic diagrams of NTN scenes based on transparent and regenerative satellites, respectively.

[0055] As shown in Figure 4, in an NTN scenario based on transparent forwarding satellites, communication between gateways and satellites occurs via a feeder link, and communication between satellites and terminals occurs via a service link. As shown in Figure 5, in an NTN scenario based on regenerative forwarding satellites, communication between satellites occurs via an interstar link, communication between gateways and satellites occurs via a feeder link, and communication between satellites and terminals occurs via a service link.

[0056] The timing relationships of the IoT-NTN system are explained below.

[0057] In terrestrial communication systems, the propagation delay of signal communication is usually less than 1 ms. In IoT-NTN systems, due to the long communication distance between terminal equipment and satellites (or network equipment), the propagation delay of signal communication is large, ranging from tens of milliseconds to hundreds of milliseconds, and is specifically related to the altitude of the satellite orbit and the type of satellite communication service. To deal with the large propagation delay, the timing relationship of the IoT-NTN system needs to be strengthened relative to IoT systems (e.g., eMTC or NB-IoT).

[0058] In an IoT-NTN system, similar to an IoT system, a UE must consider the impact of timing advance (TA) when performing uplink transmission. Because of the large propagation delay in the system, the range of TA values ​​is also large. When a UE is scheduled to perform uplink transmission in subframe n, the UE takes into account the round-trip propagation delay and transmits in advance during the uplink transmission so that, upon arrival at the network device, the signal is transmitted in uplink subframe n on the network device side. Specifically, the timing relationship in an IoT-NTN system can be considered in two cases, as shown in Figures 6 and 7, respectively.

[0059] In Case 1, as shown in Figure 6, the downlink subframe and the uplink subframe on the network device side are aligned. When scheduling the UE to perform uplink transmission, an offset value Koffset needs to be introduced, and the offset value Koffset corresponds to the TA of the UE. For example, the length of time corresponding to the offset value Koffset is greater than or equal to the length of time corresponding to the TA of the UE. In this case, the round trip delay on the UE side is determined based on the TA of the UE.

[0060] In Situation 2, as shown in FIG. 7, an uplink-downlink timing offset exists between the uplink subframe and the downlink subframe on the network device side. When scheduling the UE to perform uplink transmission, an offset value Koffset must also be introduced, and the offset value Koffset corresponds to the TA of the UE. For example, the length of time corresponding to the offset value Koffset is greater than or equal to the length of time corresponding to the TA of the UE. In this case, the round trip delay on the UE side is determined based on the TA of the UE and the uplink-downlink timing offset value of the base station.

[0061] To facilitate understanding of the solution of the present application, the control channel monitoring method in the NB-IoT system will be described below.

[0062] The downlink control channel candidate monitoring scheme between the uplink grant and the uplink shared channel is as follows.

[0063] Optionally, the UE-specific search space assumes that two HARQ processes are configured in the terminal device.

[0064] If the end position of a first downlink control channel carrying a first uplink grant (e.g., corresponding to DCI format N0) received by a terminal device is in subframe n, and transmission of a first uplink shared channel corresponding to the first uplink grant (e.g., corresponding to NPUSCH format 1) starts in subframe n+k, the terminal device is not requested to monitor downlink control channel candidates in any subframes from subframe n+k-2 to subframe n+k-1. An example is shown in Figure 8.

[0065] The terminal device does not want to receive a second downlink control channel carrying a second uplink grant (e.g., corresponding to DCI format N0) before subframe n+k-2, where the transmission end position of the second uplink shared channel corresponding to the second uplink grant (e.g., corresponding to NPUSCH format 1) is after subframe n+k+255. An example is shown in Figure 9.

[0066] Optionally, in TDD, if the transmission end position of the first uplink shared channel corresponding to the first uplink grant (e.g., corresponding to NPUSCH format 1) is located in subframe n+m, the terminal device is not required to monitor downlink control channel candidates in any subframe from subframe n+k to subframe n+m-1. An example is shown in Figure 10.

[0067] If not, If the end position of a first downlink control channel carrying a first uplink grant (e.g., corresponding to DCI format N0) received by a terminal device is in subframe n, or if the reception end position of a first downlink shared channel carrying a random access response (RAR) grant is in subframe n and transmission of the first uplink shared channel corresponding to the first uplink grant or the RAR grant (e.g., corresponding to NPUSCH format 1) starts in subframe n+k, the terminal device is not requested to monitor downlink control channel candidates in any subframes from subframe n+1 to subframe n+k-1. An example is shown in Figure 11.

[0068] Optionally, in TDD, if the end position of a first downlink control channel carrying a first uplink grant (e.g., corresponding to DCI format N0) received by a terminal device is in subframe n, or the reception end position of a first downlink shared channel carrying a random access response (RAR) grant is in subframe n and the transmission end position of a first uplink shared channel corresponding to the first uplink grant or the RAR grant (e.g., corresponding to NPUSCH format 1) is in subframe n+k, the terminal device is not requested to monitor downlink control channel candidates in any subframes from subframe n+1 to subframe n+k. An example is shown in Figure 12.

[0069] The guard interval also affects monitoring for downlink control channel candidates.

[0070] Optionally, it is assumed that two HARQ processes are configured in the terminal device.

[0071] If the end position of the transmission of the first uplink signal (uplink shared channel, e.g., NPUSCH) by the terminal device is in subframe n, in FDD, if Type B half-duplex guard periods are configured, the terminal device is not required to receive transmissions within the Type B half-duplex guard periods.

[0072] Optionally, for a half-duplex guard interval in an FDD scenario, in the case of Type A half-duplex FDD operation, the terminal device creates one guard interval, i.e., the terminal device does not receive in the last part of the downlink subframe before its uplink subframe. In the case of Type B half-duplex FDD operation, the terminal device creates multiple guard intervals, each guard interval being associated with one half-duplex guard subframe, i.e., the terminal device does not receive in the downlink subframe before its uplink subframe, and the terminal device does not receive in the downlink subframe following its uplink subframe.

[0073] Terminal devices in the IoT-NTN (Internet of Things NTN) system use a GNSS (Global Navigation Satellite System) module, and the functions of sending and receiving data in the IoT-NTN system cannot be used simultaneously.

[0074] The GNSS module is configured to allow the terminal device to acquire synchronization information. For example, when the terminal device receives a paging message or a wake-up signal (WUS) while in an idle state, the terminal device needs to perform time synchronization after receiving the paging message or WUS, or the terminal device needs to perform time-frequency synchronization to receive the paging message or WUS. In this process, the terminal device needs to start the GNSS module to fix the GNSS position, such as completing the GNSS Time To First Fix (TTFF). Then, the terminal device switches from the GNSS module to the IoT-NTN system operation module and acquires the serving satellite ephemeris for uplink synchronization by acquiring the NTN System Information Block (SIB). Typically, when a terminal device is hot started, it takes one second for one GNSS TTFF, i.e., if the GNSS ephemeris information (ephemeris) corresponding to the previous TTFF was acquired within four hours, it takes one second for one GNSS TTFF, and when a terminal device is warm started, it takes less than five seconds for one GNSS TTFF, i.e., if the GNSS almanac information (almanac) corresponding to the previous TTFF was acquired within 180 days, it takes less than five seconds for one GNSS TTFF.

[0075] Additionally, the terminal device may not have the capability to simultaneously transmit and receive signals.

[0076] Also, as noted above, NTN systems have a large range of TA values ​​due to the large propagation delay.

[0077] Therefore, the uplink-downlink timing relationship in the terrestrial network (TN) system cannot be applied to the uplink-downlink timing relationship in the IoT-NTN system. Furthermore, the terminal equipment in the IoT-NTN system cannot monitor the control channel efficiently, which reduces the reliability of communication.

[0078] Based on this, the embodiments of the present application provide a wireless communication method, terminal device, and network device that can ensure the normal operation of terminal devices that do not have the function of simultaneously transmitting and receiving signals in an IoT-NTN system, improve communication reliability, and also achieve power saving effects.

[0079] FIG. 13 is an exemplary flowchart of a wireless communication method 200 according to an embodiment of the present application. The method 200 can be performed by a terminal device and a network device interacting with each other. The terminal device illustrated in FIG. 13 may be the terminal device illustrated in FIGS. 1 to 5, and the network device illustrated in FIG. 13 may be the access network device illustrated in FIGS. 1 to 5. Note that FIG. 13 is merely an example of the present application and should not be understood as a limitation on the present application. For example, in another alternative embodiment, the wireless communication method provided by the present application can also be applied to sidelink communication. That is, in another alternative embodiment, the wireless communication method provided by the present application can be performed by two terminal devices interacting with each other, for example, a receiving terminal and a transmitting terminal interacting with each other. Specifically, the transmitting terminal can transmit the first control channel illustrated in FIG. 13 to the receiving terminal, or the first control channel is a sidelink control channel. The method of the present application will be described below using an example in which the terminal device and the network device perform the method 200.

[0080] As shown in FIG. 13, the method 200 may include some or all of the following:

[0081] At S210, a first control channel is received, where the first control channel corresponds to a first shared channel.

[0082] In S220, control channel candidates are not monitored in any time unit from the first time unit to the second time unit.

[0083] Here, the first time unit is determined based on at least one of n, n+k, and n+m, and the second time unit is determined based on at least one of n, n+k, and n+m, where n represents the time unit in which the end position of the first control channel is located, n+k represents the time unit in which the transmission start position of the first shared channel is located, and n+m represents the time unit in which the transmission end position of the first shared channel is located.

[0084] In other words, the end position of the first control channel received by the terminal device is at time unit n, the transmission start position of the first shared channel corresponding to the first control channel is at time unit n+k, and the transmission end position of the first shared channel corresponding to the first control channel is at time unit n+m.

[0085] According to the above technical solution, in the IoT-NTN system, by specifying a time period during which the terminal device does not monitor control channel candidates, i.e., any time unit from the first time unit to the second time unit, it is possible to ensure the normal operation of terminal devices that do not have the function of simultaneously transmitting and receiving signals, and also to achieve power saving effects.

[0086] In some embodiments, at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, and n+m and the first offset, or the first time unit is determined based on at least one of n, n+k, and n+m and the third offset, the first offset representing an offset between the uplink timing and downlink timing of the terminal device, and the third offset being greater than the first offset.

[0087] Optionally, the first offset is configured by a network device, or the first offset is determined based on a configuration parameter of the network device.

[0088] Optionally, the first offset is a TA value of the terminal device.

[0089] Optionally, the third offset is configured by a network device, or the third offset is determined based on a configuration parameter of the network device.

[0090] Optionally, the third offset represents an offset after extension of the uplink timing of the terminal equipment.

[0091] Optionally, for the transmission timing of uplink shared channel transmission, if the end position of the uplink grant received by the terminal device is in downlink time unit n, the terminal device starts transmitting the uplink shared channel scheduled by the uplink grant in an uplink time unit corresponding to downlink time unit n+K2+O3, where K2 is the uplink transmission timing of the uplink shared channel scheduled by the uplink grant in the TN network; or downlink time unit n+K2+O3 corresponds to the same uplink time unit as downlink time unit n+k, where O3 represents a third offset.

[0092] In some embodiments, the time unit corresponding to uplink timing includes the time unit being determined based on the uplink timing.

[0093] In some embodiments, the time unit corresponds to uplink timing, or determining the time unit based on uplink timing, can be understood as the time unit taking into account the effect of TA (including the effect of the timing advance), or can be translated as: the time unit takes into account the effect of TA.

[0094] In some embodiments, the time unit corresponding to downlink timing includes the time unit being determined based on downlink timing.

[0095] In some embodiments, the time unit corresponds to downlink timing, or determining the time unit based on downlink timing, can be understood as assuming the timing advance is 0, or without the effect of the timing advance, or can be replaced by: assuming the time unit is 0, or without the effect of the timing advance.

[0096] Optionally, at least one of n, n+k, n+m is a time unit based on the downlink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, n+m and the first offset, or the first time unit is determined based on at least one of n, n+k, n+m and the third offset, where the first time unit corresponds to the downlink timing of the terminal device, or the first time unit is determined based on the downlink timing of the terminal device, or when determining the first time unit, it is assumed that TA is 0 or does not include the effect of TA.

[0097] In some embodiments, at least one of n, n+k, and n+m is a time unit based on the uplink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, and n+m.

[0098] Optionally, at least one of n, n+k, n+m is a time unit based on the uplink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, n+m, where at least one of n, n+k, n+m corresponds to the uplink timing of the terminal device, or the first time unit corresponds to an uplink time unit determined based on the uplink timing of the terminal device, or the first time unit is determined by an uplink time unit determined based on the uplink timing of the terminal device, or the first time unit takes into account the effect of TA.

[0099] In some embodiments, at least one of n, n+k, and n+m is a time unit based on downlink timing of the terminal equipment, and the first time unit is determined based on at least one of n, n+k, and n+m and a second offset, and the second offset is configured by a network equipment, or the second offset is determined based on a configuration parameter of the network equipment.

[0100] Optionally, said second offset represents an offset between uplink and downlink timing of a network device.

[0101] Optionally, said second offset represents an offset between downlink timing and uplink timing of a network device.

[0102] Optionally, if downlink timing of said network equipment is aligned with uplink timing, said second offset is 0.

[0103] Optionally, at least one of n, n+k, n+m is a time unit based on the downlink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, n+m and a second offset, where the first time unit corresponds to the downlink timing of the terminal device, or the first time unit is determined based on the downlink timing of the terminal device, or when determining the first time unit, it is assumed that TA is 0 or does not include the effect of TA.

[0104] In some embodiments, at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, and n+m.

[0105] Optionally, at least one of n, n+k, n+m is a time unit based on the downlink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, n+m, where the first time unit corresponds to the downlink timing of the terminal device, or the first time unit is determined based on the downlink timing of the terminal device, or when determining the first time unit, it is assumed that TA is 0 or does not include the effect of TA.

[0106] In some embodiments, the downlink timing of the terminal device includes at least one first downlink time unit that fully overlaps or partially overlaps with a time unit determined based on at least one of n, n+k, and n+m, and the at least one first downlink time unit includes the first time unit.

[0107] Optionally, the time unit determined based on at least one of said n, n+k, n+m is a first uplink time unit.

[0108] Optionally, the at least one first downlink time unit comprises a time unit that fully overlaps or partially overlaps with the first uplink time unit.

[0109] For example, when the time unit determined based on at least one of n, n+k, and n+m is a first uplink time unit, the first uplink time unit may correspond to two downlink time units, and the first time unit may correspond to the first downlink time unit of the two downlink time units or the second downlink time unit of the two downlink time units. That is, the start time unit for not monitoring control channel candidates may be the first downlink time unit of the two downlink time units or the second downlink time unit of the two downlink time units.

[0110] Optionally, the at least one first downlink time unit is a plurality of first downlink time units, and the first time unit is any one first downlink time unit of the plurality of first downlink time units or the earliest first downlink time unit.

[0111] Optionally, the at least one first downlink time unit is two downlink time units, the first time unit being an earlier downlink time unit of the two downlink time units.

[0112] In some embodiments, at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on at least one of n, n+k, and n+m and the first offset, or the second time unit is determined based on at least one of n, n+k, and n+m and the third offset, the first offset representing an offset between the uplink timing and downlink timing of the terminal device, and the third offset being greater than the first offset.

[0113] Optionally, the first offset is configured by a network device, or the first offset is determined based on a configuration parameter of the network device.

[0114] Optionally, the first offset is a TA value of the terminal device.

[0115] Optionally, the third offset is configured by a network device, or the third offset is determined based on a configuration parameter of the network device.

[0116] Optionally, the third offset represents an offset after extension of the uplink timing of the terminal equipment.

[0117] Optionally, for the transmission timing of uplink shared channel transmission, if the end position of the uplink grant received by the terminal device is in downlink time unit n, the terminal device starts transmitting the uplink shared channel scheduled by the uplink grant in an uplink time unit corresponding to downlink time unit n+K2+O3, where K2 is the uplink transmission timing of the uplink shared channel scheduled by the uplink grant in the TN network; or downlink time unit n+K2+O3 corresponds to the same uplink time unit as downlink time unit n+k, where O3 represents a third offset.

[0118] Optionally, at least one of n, n+k, n+m is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on at least one of n, n+k, n+m and the first offset, or the second time unit is determined based on at least one of n, n+k, n+m and the third offset, wherein the second time unit corresponds to the downlink timing of the terminal device, or the second time unit is determined based on the downlink timing of the terminal device, or when determining the first time unit, it is assumed that TA is 0 or does not include the effect of TA.

[0119] In some embodiments, at least one of n, n+k, and n+m is a time unit based on the uplink timing of the terminal device, and the second time unit is determined based on at least one of n, n+k, and n+m.

[0120] Optionally, at least one of n, n+k, n+m is a time unit based on the uplink timing of the terminal device, and the second time unit is determined based on at least one of n, n+k, n+m, where at least one of n, n+k, n+m corresponds to the uplink timing of the terminal device, or the second time unit corresponds to an uplink time unit determined based on the uplink timing of the terminal device, or the second time unit corresponds to an uplink time unit determined based on the uplink timing of the terminal device, or the second time unit takes into account the effect of TA.

[0121] In some embodiments, at least one of n, n+k, n+m is a time unit based on a downlink timing of the terminal device, and the second time unit is determined based on at least one of n, n+k, n+m and a second offset, the second offset being configured by a network device, or the second offset being determined based on a configuration parameter of a network device.

[0122] Optionally, said second offset represents an offset between uplink and downlink timing of a network device.

[0123] Optionally, said second offset represents an offset between downlink timing and uplink timing of a network device.

[0124] Optionally, if downlink timing of said network equipment is aligned with uplink timing, said second offset is 0.

[0125] Optionally, at least one of n, n+k, n+m is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on at least one of n, n+k, n+m and a second offset, where the second time unit corresponds to the downlink timing of the terminal device, or the second time unit is determined based on the downlink timing of the terminal device, or when determining the first time unit, it is assumed that TA is 0 or does not include the effect of TA.

[0126] In some embodiments, at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on at least one of n, n+k, and n+m.

[0127] Optionally, at least one of n, n+k, n+m is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on at least one of n, n+k, n+m, where the second time unit corresponds to the downlink timing of the terminal device, or the second time unit is determined based on the downlink timing of the terminal device, or when determining the first time unit, it is assumed that TA is 0 or does not include the effect of TA.

[0128] In some embodiments, the downlink timing of the terminal device includes at least one second downlink time unit that fully overlaps or partially overlaps with a time unit determined based on at least one of n, n+k, and n+m, and the at least one second downlink time unit includes the second time unit.

[0129] Optionally, the time unit determined based on at least one of said n, n+k, n+m is a second uplink time unit.

[0130] Optionally, the at least one second downlink time unit comprises a time unit that at least partially overlaps with the second uplink time unit.

[0131] For example, when the time unit determined based on at least one of n, n+k, and n+m is a second uplink time unit, the second uplink time unit may correspond to two downlink time units, and the second time unit may correspond to the first downlink time unit of the two downlink time units or the second downlink time unit of the two downlink time units. That is, the end time unit for not monitoring control channel candidates may be the first downlink time unit of the two downlink time units or the second downlink time unit of the two downlink time units.

[0132] Optionally, the at least one second downlink time unit is a plurality of second downlink time units, and the second time unit is any one second downlink time unit of the plurality of second downlink time units or the latest second downlink time unit.

[0133] Optionally, the at least one second downlink time unit is two downlink time units, the second time unit being a later downlink time unit of the two downlink time units.

[0134] In some embodiments, the first time unit is determined based on n+k.

[0135] Optionally, if the first device is configured with two or more Hybrid Automatic Repeat Request (HARQ) processes, the first time unit is determined based on n+k.

[0136] In some embodiments, the first time unit is determined based on n.

[0137] Optionally, if the first device is configured with one Hybrid Automatic Repeat Request (HARQ) process, the first time unit is determined based on n.

[0138] In some embodiments, the second time unit is determined based on n+k.

[0139] Optionally, in a frequency division duplex (FDD) scenario, the second time unit is determined based on n+k.

[0140] In some embodiments, the second time unit is determined based on n+m.

[0141] Optionally, in a time division duplex (TDD) scenario, the second time unit is determined based on n+m.

[0142] In some embodiments, when the first device is configured with two or more Hybrid Automatic Repeat Request (HARQ) processes, in an FDD scenario, the first time unit comprises: at least one of n+k−2, n+k−2−O1, and n+k−2−O3; Here, O1 represents a first offset, O3 represents a third offset, the first offset represents an offset between the uplink timing and the downlink timing of the terminal device, and the third offset is greater than the first offset.

[0143] In some embodiments, when the first device is configured with two or more Hybrid Automatic Repeat Request (HARQ) processes, in an FDD scenario, the second time unit comprises: at least one of n+k-1, n+k-1+O2, n+k, and n+k+O2; Here, O2 represents a second offset, which is configured by a network device.

[0144] In some embodiments, when the first device is configured with two or more Hybrid Automatic Repeat Request (HARQ) processes, in a TDD scenario, the first time unit comprises: at least one of n+k, n+k-O1, and n+k-O3; Here, O1 represents a first offset, O3 represents a third offset, the first offset represents an offset between the uplink timing and the downlink timing of the terminal device, and the third offset is greater than the first offset.

[0145] In some embodiments, when the first device is configured with two or more Hybrid Automatic Repeat Request (HARQ) processes, in an FDD scenario, the second time unit comprises: at least one of n+m-1, n+m-1+O2, n+m, and n+m+O2; Here, O2 represents a second offset, which is configured by a network device.

[0146] In some embodiments, when the first device is configured with one Hybrid Automatic Repeat Request (HARQ) process, in an FDD scenario, the first time unit comprises: at least one of n+1, n+1-O1, and n+1-O3; Here, O1 represents a first offset, O3 represents a third offset, the first offset represents an offset between the uplink timing and the downlink timing of the terminal device, and the third offset is greater than the first offset.

[0147] In some embodiments, when the first device is configured with one Hybrid Automatic Repeat Request (HARQ) process, in an FDD scenario, the second time unit comprises: at least one of n+k-1, n+k-1+O2, n+k, and n+k+O2; Here, O2 represents a second offset, which is configured by a network device.

[0148] In some embodiments, when the first device is configured with one Hybrid Automatic Repeat Request (HARQ) process, in a TDD scenario, the first time unit comprises: at least one of n+1, n+1-O1, and n+1-O3; Here, O1 represents a first offset, O3 represents a third offset, the first offset represents an offset between the uplink timing and the downlink timing of the terminal device, and the third offset is greater than the first offset.

[0149] In some embodiments, when the first device is configured with one Hybrid Automatic Repeat Request (HARQ) process, in a TDD scenario, the second time unit comprises: at least one of n+m-1, n+m-1+O2, n+m, and n+m+O2; Here, O2 represents a second offset, which is configured by a network device.

[0150] In some embodiments, when the first device is configured with two or more hybrid automatic repeat request (HARQ) processes, time units prior to the first time unit are not used to monitor a second control channel for scheduling a second shared channel, wherein a transmission end position of the second shared channel is after a third time unit, and the length of time between the third time unit and the first time unit is a first predetermined value.

[0151] Optionally, the first predetermined value is P+2.

[0152] Optionally, P is 255, or P is an integer value less than 255.

[0153] In some embodiments, the method 200 comprises: The terminal device may further include receiving configuration information, the configuration information being used to determine at least one of a first offset, a second offset, and a third offset, the first time unit being determined based on at least one of n, n+k, n+m and at least one of the first offset, the second offset, and the third offset, and the second time unit being determined based on at least one of n, n+k, n+m and at least one of the first offset, the second offset, and the third offset.

[0154] Optionally, the configuration information comprises: It is carried in at least one of a system message, a radio resource control (RRC), a media access control (MAC) control element (CE), and a downlink control information (DCI).

[0155] Optionally, the unit of the first offset value may be a unit of time unit, such as a subframe, a slot, a symbol, a frame, etc., or the unit of the first offset value may be an absolute value, such as milliseconds, microseconds, seconds, etc.

[0156] Optionally, the unit of the second offset value may be a unit of time unit, such as a subframe, a slot, a symbol, a frame, etc., or the unit of the second offset value may be an absolute value, such as milliseconds, microseconds, seconds, etc.

[0157] Optionally, the unit of the third offset value may be a unit of time unit, such as a subframe, a slot, a symbol, a frame, etc., or the unit of the third offset value may be an absolute value, such as milliseconds, microseconds, seconds, etc.

[0158] The method 200 will be described below with reference to a specific embodiment.

[0159] Example 1: FIG. 14 shows an example of a first time unit and a second time unit according to an embodiment of the present application.

[0160] As shown in Example 1 of Figure 14, at least one of n, n+k, and n+m is a time unit based on the uplink timing of the terminal device, and the first time unit is time unit n+k-2. As shown in Example 2 of Figure 14, at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the first time unit may be time unit n+k-O1-2. As shown in Example 3 of Figure 14, at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the first time unit may be time unit n+k-O3-2.

[0161] As shown in Example 1 or Example 3 of Figure 14, at least one of n, n+k, n+m is a time unit based on the downlink timing of the terminal device, and the second time unit is time unit n+m. As shown in Example 2 of Figure 14, at least one of n, n+k, n+m is a time unit based on the uplink timing of the terminal device, and the second time unit is time unit n+m, or at least one of n, n+k, n+m is a time unit based on the downlink timing of the terminal device, and the second time unit is time unit n+m-O1.

[0162] In this embodiment, O1 is six time units and O3 is seven time units, for example, but the present application is not limited to these.

[0163] Example 2: FIG. 15 shows an example of a first time unit and a second time unit according to an embodiment of the present application.

[0164] As shown in Examples 1, 2, and 4 of Figure 14, at least one of n, n+k, and n+m is a time unit based on the uplink timing of the terminal device, and the first time unit is time unit n+k-2, or at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the first time unit is time unit n+k-O1-2. As shown in Example 3 of Figure 14, at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the first time unit is time unit n+k-O3-2.

[0165] As shown in Examples 1 and 3 of Figure 14, at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the second time unit is time unit n+m. As shown in Example 2 of Figure 14, at least one of n, n+k, and n+m is a time unit based on the uplink timing of the terminal device, and the second time unit is time unit n+m, or at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the second time unit is time unit n+m-O1. As shown in Example 4 of Figure 14, at least one of n, n+k, and n+m is a time unit based on the uplink timing of the terminal device, and the second time unit is time unit n+m+O2.

[0166] In this embodiment, O1 is 6 time units, O3 is 7 time units, and O2 is 4 time units, for example, but the present application is not limited to these.

[0167] Above, the wireless communication method according to the embodiments of the present application has been described in detail from the perspective of terminal equipment with reference to Figures 13 to 15. Below, the wireless communication method provided in the embodiments of the present application will be described from the perspective of network equipment with reference to Figure 13.

[0168] As shown in FIG. 13, the method 200 may include some or all of the following:

[0169] At S210, a first control channel is transmitted, where the first control channel corresponds to a first shared channel.

[0170] In S230, no control channel candidate is transmitted in any time unit from the first time unit to the second time unit.

[0171] Here, the first time unit is determined based on at least one of n, n+k, and n+m, and the second time unit is determined based on at least one of n, n+k, and n+m, where n represents the time unit in which the end position of the first control channel is located, n+k represents the time unit in which the transmission start position of the first shared channel is located, and n+m represents the time unit in which the transmission end position of the first shared channel is located.

[0172] In some embodiments, the first time unit is determined based on n+k.

[0173] Optionally, if the first device is configured with two or more Hybrid Automatic Repeat Request (HARQ) processes, the first time unit is determined based on n+k.

[0174] In some embodiments, the first time unit is determined based on n.

[0175] Optionally, if the first device is configured with one Hybrid Automatic Repeat Request (HARQ) process, the first time unit is determined based on n.

[0176] In some embodiments, the second time unit is determined based on n+k.

[0177] Optionally, in a frequency division duplex (FDD) scenario, the second time unit is determined based on n+k.

[0178] In some embodiments, the second time unit is determined based on n+m.

[0179] Optionally, in a time division duplex (TDD) scenario, the second time unit is determined based on n+m.

[0180] In some embodiments, the method 200 comprises: The network device may further include transmitting configuration information, wherein the configuration information is used to determine at least one of a first offset, a second offset, and a third offset, wherein the first time unit is determined based on at least one of n, n+k, n+m and at least one of the first offset, the second offset, and the third offset, and the second time unit is determined based on at least one of n, n+k, n+m and at least one of the first offset, the second offset, and the third offset.

[0181] It should be noted that for the interaction steps in the method 200, the network device side can refer to the corresponding steps on the terminal device side, and will not be repeated here for the sake of brevity.

[0182] FIG. 16 is an exemplary flowchart of a wireless communication method 300 according to an embodiment of the present application. The method 300 can be performed by a terminal device and a network device interacting with each other. The terminal device illustrated in FIG. 16 may be the terminal device illustrated in FIGS. 1 to 5, and the network device illustrated in FIG. 16 may be the access network device illustrated in FIGS. 1 to 5. Note that FIG. 16 is merely an example of the present application and should not be understood as a limitation on the present application. For example, in another alternative embodiment, the wireless communication method provided by the present application may also be applied to sidelink communication. That is, in another alternative embodiment, the wireless communication method provided by the present application may be performed by two terminal devices interacting with each other, for example, a receiving terminal and a transmitting terminal interacting with each other. Specifically, the transmitting terminal may transmit the first control channel illustrated in FIG. 16 to the receiving terminal, or the first control channel may be a sidelink control channel. The method of the present application will be described below using an example in which the terminal device and the network device perform the method 300.

[0183] As shown in FIG. 16, the method 300 may include some or all of the following:

[0184] In S310, the first shared channel is transmitted.

[0185] In S320, no control channel candidates are monitored and / or no data is received within the half-duplex protection interval or in any time unit from the first time unit to the second time unit, where the first time unit is determined based on s and the second time unit is determined based on s, and s represents the time unit in which the transmission end position of the first shared channel is located.

[0186] In some embodiments, the terminal device is in a frequency division duplex (FDD) scenario and / or the half-duplex protection interval comprises a configured type B half-duplex protection interval.

[0187] In some embodiments, s is a time unit based on the downlink timing of the terminal device, and the first time unit is determined based on s and the first offset, or the first time unit is determined based on s and the third offset, the first offset representing an offset between the uplink timing and downlink timing of the terminal device, and the third offset being greater than the first offset.

[0188] Optionally, the first offset is configured by a network device, or the first offset is determined based on a configuration parameter of the network device.

[0189] Optionally, the first offset is a TA value of the terminal device.

[0190] Optionally, the third offset is configured by a network device, or the third offset is determined based on a configuration parameter of the network device.

[0191] Optionally, the third offset represents an offset after extension of the uplink timing of the terminal equipment.

[0192] Optionally, for the transmission timing of uplink shared channel transmission, if the end position of the uplink grant received by the terminal device is in downlink time unit n, the terminal device starts transmitting the uplink shared channel scheduled by the uplink grant in an uplink time unit corresponding to downlink time unit n+K2+O3, where K2 is the uplink transmission timing of the uplink shared channel scheduled by the uplink grant in the TN network; or downlink time unit n+K2+O3 corresponds to the same uplink time unit as downlink time unit n+k, where O3 represents a third offset.

[0193] In some embodiments, the time unit corresponds to an uplink timing includes the time unit being determined based on the uplink timing.

[0194] In some embodiments, the time unit corresponds to uplink timing, or determining the time unit based on uplink timing, can be understood as the time unit taking into account the effect of TA (including the effect of the timing advance), or can be translated as: the time unit takes into account the effect of TA.

[0195] In some embodiments, the time unit corresponding to downlink timing includes the time unit being determined based on downlink timing.

[0196] In some embodiments, the time unit corresponds to downlink timing, or determining the time unit based on downlink timing, can be understood as assuming the timing advance is 0, or without the effect of the timing advance, or can be replaced by: assuming the time unit is 0, or without the effect of the timing advance.

[0197] Optionally, the s is a time unit based on the downlink timing of the terminal device, and the first time unit is determined based on the s and the first offset, or the first time unit is determined based on the s and the third offset, where the first time unit corresponds to the downlink timing of the terminal device, or the first time unit is determined based on the downlink timing of the terminal device, or when determining the first time unit, it is assumed that TA is 0 or does not include the effect of TA.

[0198] In some embodiments, s is a time unit based on an uplink timing of the terminal device, and the first time unit is determined based on s.

[0199] Optionally, s is a time unit based on the uplink timing of the terminal device, and the first time unit is determined based on the s, where s corresponds to the uplink timing of the terminal device, or the first time unit corresponds to an uplink time unit determined based on the uplink timing of the terminal device, or the first time unit corresponds to an uplink time unit determined based on the uplink timing of the terminal device, or the first time unit takes into account the effect of TA.

[0200] In some embodiments, s is a time unit based on the downlink timing of the terminal device, and the first time unit is determined based on s and a second offset, and the second offset is configured by a network device, or the second offset is determined based on a configuration parameter of the network device.

[0201] Optionally, said second offset represents an offset between uplink and downlink timing of a network device.

[0202] Optionally, said second offset represents an offset between downlink timing and uplink timing of a network device.

[0203] Optionally, if downlink timing of said network equipment is aligned with uplink timing, said second offset is 0.

[0204] Optionally, s is a time unit based on the downlink timing of the terminal device, and the first time unit is determined based on s and a second offset, where the first time unit corresponds to the downlink timing of the terminal device, or the first time unit is determined based on the downlink timing of the terminal device, or when determining the first time unit, it is assumed that TA is 0 or does not include the effect of TA.

[0205] In some embodiments, s is a time unit based on downlink timing of the terminal device, and the first time unit is determined based on s.

[0206] Optionally, s is a time unit based on the downlink timing of the terminal device, and the first time unit is determined based on s, where the first time unit corresponds to the downlink timing of the terminal device, or the first time unit is determined based on the downlink timing of the terminal device, or when determining the first time unit, it is assumed that TA is 0 or does not include the effect of TA.

[0207] In some embodiments, the downlink timing of the terminal device includes at least one first downlink time unit that fully overlaps or partially overlaps with a time unit determined based on s, and the at least one first downlink time unit includes the first time unit.

[0208] Optionally, the time unit determined based on s is a first uplink time unit.

[0209] Optionally, the at least one first downlink time unit comprises a time unit that fully overlaps or partially overlaps with the first uplink time unit.

[0210] For example, when the time unit determined based on s is the first uplink time unit, the first uplink time unit may correspond to two downlink time units, and the first time unit may correspond to the first downlink time unit of the two downlink time units, or the second downlink time unit of the two downlink time units. That is, the start time unit for not monitoring control channel candidates may be the first downlink time unit of the two downlink time units, or the second downlink time unit of the two downlink time units.

[0211] Optionally, the at least one first downlink time unit is a plurality of first downlink time units, and the first time unit is any one first downlink time unit of the plurality of first downlink time units or the earliest first downlink time unit.

[0212] Optionally, the at least one first downlink time unit is two downlink time units, the first time unit being an earlier downlink time unit of the two downlink time units.

[0213] In some embodiments, s is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on s and the first offset, or the second time unit is determined based on s and the third offset, the first offset representing an offset between the uplink timing and downlink timing of the terminal device, and the third offset being greater than the first offset.

[0214] Optionally, the first offset is configured by a network device, or the first offset is determined based on a configuration parameter of the network device.

[0215] Optionally, the first offset is a TA value of the terminal device.

[0216] Optionally, the third offset is configured by a network device, or the third offset is determined based on a configuration parameter of the network device.

[0217] Optionally, the third offset represents an offset after extension of the uplink timing of the terminal equipment.

[0218] Optionally, for the transmission timing of uplink shared channel transmission, if the end position of the uplink grant received by the terminal device is in downlink time unit n, the terminal device starts transmitting the uplink shared channel scheduled by the uplink grant in an uplink time unit corresponding to downlink time unit n+K2+O3, where K2 is the uplink transmission timing of the uplink shared channel scheduled by the uplink grant in the TN network; or downlink time unit n+K2+O3 corresponds to the same uplink time unit as downlink time unit n+k, where O3 represents a third offset.

[0219] Optionally, s is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on s and the first offset, or the second time unit is determined based on s and the third offset, where the second time unit corresponds to the downlink timing of the terminal device, or the second time unit is determined based on the downlink timing of the terminal device, or when determining the first time unit, it is assumed that TA is 0 or does not include the effect of TA.

[0220] In some embodiments, s is a time unit based on an uplink timing of the terminal device, and the second time unit is determined based on s.

[0221] Optionally, the s is a time unit based on the uplink timing of the terminal device, and the second time unit is determined based on the s, where the s corresponds to the uplink timing of the terminal device, or the second time unit corresponds to an uplink time unit determined based on the uplink timing of the terminal device, or the second time unit corresponds to an uplink time unit determined based on the uplink timing of the terminal device, or the second time unit takes into account the effect of TA.

[0222] In some embodiments, s is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on s and a second offset, and the second offset is configured by a network device, or the second offset is determined based on a configuration parameter of the network device.

[0223] Optionally, said second offset represents an offset between uplink and downlink timing of a network device.

[0224] Optionally, said second offset represents an offset between downlink timing and uplink timing of a network device.

[0225] Optionally, if downlink timing of said network equipment is aligned with uplink timing, said second offset is 0.

[0226] Optionally, s is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on s and a second offset, where the second time unit corresponds to the downlink timing of the terminal device, or the second time unit is determined based on the downlink timing of the terminal device, or when determining the first time unit, it is assumed that TA is 0 or does not include the effect of TA.

[0227] In some embodiments, s is a time unit based on downlink timing of the terminal device, and the second time unit is determined based on s.

[0228] Optionally, s is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on s, where the second time unit corresponds to the downlink timing of the terminal device, or the second time unit is determined based on the downlink timing of the terminal device, or when determining the first time unit, it is assumed that TA is 0 or does not include the effect of TA.

[0229] In some embodiments, the downlink timing of the terminal device includes at least one second downlink time unit that fully overlaps or partially overlaps with a time unit determined based on s, and the at least one second downlink time unit includes the second time unit.

[0230] Optionally, the time unit determined based on s is a second uplink time unit.

[0231] Optionally, the at least one second downlink time unit comprises a time unit that at least partially overlaps with the second uplink time unit.

[0232] For example, when the time unit determined based on s is a second uplink time unit, the second uplink time unit may correspond to two downlink time units, and the second time unit may correspond to the first downlink time unit of the two downlink time units or the second downlink time unit of the two downlink time units. That is, the end time unit for not monitoring control channel candidates may be the first downlink time unit of the two downlink time units or the second downlink time unit of the two downlink time units.

[0233] Optionally, the at least one second downlink time unit is a plurality of second downlink time units, and the second time unit is any one second downlink time unit of the plurality of second downlink time units or the latest second downlink time unit.

[0234] Optionally, the at least one second downlink time unit is two downlink time units, the second time unit being a later downlink time unit of the two downlink time units.

[0235] In some embodiments, the first time unit comprises: at least one of s+1, s+1-O1, and s+1-O3; Here, O1 represents a first offset, O3 represents a third offset, the first offset represents an offset between the uplink timing and the downlink timing of the terminal device, and the third offset is greater than the first offset.

[0236] In some embodiments, the second time unit comprises: at least one of s, s+1, s+O2, s+1+O2; Here, O2 represents a second offset, which is configured by a network device.

[0237] In some embodiments, the method 300 comprises: The method may further include receiving configuration information, wherein the configuration information is used to determine at least one of a first offset, a second offset, and a third offset, wherein the first time unit is determined based on s and at least one of the first offset, the second offset, and the third offset, and the second time unit is determined based on s and at least one of the first offset, the second offset, and the third offset.

[0238] Example 3: FIG. 17 shows an example of a first time unit and a second time unit according to an embodiment of the present application.

[0239] As shown in Examples 1 to 4 of Figure 17, the s is a time unit based on the uplink timing of the terminal device, and the first time unit is time unit s+1. As shown in Example 2 of Figure 17, the s is a time unit based on the uplink timing of the terminal device, and the second time unit is s+1. As shown in Example 3 of Figure 17, the s is a time unit based on the downlink timing of the terminal device, and the second time unit is s+1. As shown in Example 4 of Figure 17, the s is a time unit based on the downlink timing of the terminal device, and the second time unit is s.

[0240] In this embodiment, O1 is six time units as an example, but the present application is not limited thereto.

[0241] Example 4: FIG. 18 illustrates another example of the first time unit and the second time unit according to an embodiment of the present application.

[0242] As shown in Examples 1 to 4 of Figure 18, s is a time unit based on the uplink timing of the terminal device, and the first time unit is time unit s+1. As shown in Example 2 of Figure 18, s is a time unit based on the downlink timing of the terminal device, and the second time unit is s+1. As shown in Example 3 of Figure 18, s is a time unit based on the downlink timing of the terminal device, and the second time unit is s. As shown in Example 4 of Figure 18, s is a time unit based on the downlink timing of the terminal device, and the second time unit is s+O2.

[0243] In this embodiment, O1 is six time units and O2 is four time units, for example, but the present application is not limited to these.

[0244] Above, the wireless communication method according to the embodiments of the present application has been described in detail from the perspective of terminal equipment with reference to Figures 16 to 18. Below, the wireless communication method provided in the embodiments of the present application will be described from the perspective of network equipment with reference to Figure 18.

[0245] As shown in FIG. 18, the method 300 may include some or all of the following:

[0246] In S310, the first shared channel is received.

[0247] In S330, no control channel candidate is transmitted and / or no data is received within the half-duplex protection interval or in any time unit from the first time unit to the second time unit, where the first time unit is determined based on s and the second time unit is determined based on s, and s represents the time unit in which the transmission end position of the first shared channel is located.

[0248] In some embodiments, the terminal device is in a frequency division duplex (FDD) scenario and / or the half-duplex protection interval comprises a configured type B half-duplex protection interval.

[0249] In some embodiments, the method 300 comprises: The method may further include transmitting configuration information, wherein the configuration information is used to determine at least one of a first offset, a second offset, and a third offset, wherein the first time unit is determined based on s and at least one of the first offset, the second offset, and the third offset, and the second time unit is determined based on s and at least one of the first offset, the second offset, and the third offset.

[0250] It should be noted that for the interaction steps in the method 300, the network device side can refer to the corresponding steps on the terminal device side, and will not be repeated here for the sake of brevity.

[0251] Although the preferred embodiments of the present application have been described above with reference to the drawings, the present application is not limited to the specific details of the above embodiments. Various simple modifications can be made to the technical solutions of the present application within the scope of the technical concept of the present application, and all such simple modifications fall within the scope of protection of the present application. For example, the specific technical features described in the above specific embodiments can be combined in any appropriate manner without contradiction, and to avoid unnecessary repetition, the present application does not describe various possible combinations. In another example, various different embodiments of the present application can also be combined in any manner, and as long as they do not violate the concept of the present application, such combinations should also be considered as the content disclosed in the present application.

[0252] Furthermore, in the embodiments of the methods of the present application, the magnitude of the sequence numbers of the above processes does not indicate the order of execution. The order of execution 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 the present application. In the embodiments of the present application, the terms "downlink" and "uplink" are used to indicate the transmission direction of a signal or data, where "downlink" indicates that the transmission direction of a signal or data is the first direction from a station to a user equipment of a cell, and "uplink" indicates that the transmission direction of a signal or data is the second direction from a user equipment of a cell to a station. For example, a "downlink signal" indicates that the transmission direction of the signal is the first direction. In the embodiments of the present application, the term "and / or" only describes an associated relationship and indicates that three relationships may exist. Specifically, A and / or B can indicate three cases: A exists independently, both A and B exist, and B exists independently. In the present specification, the symbol " / " generally indicates that the relationship between associated objects is an "or" relationship.

[0253] An embodiment of the method of the present application has been described in detail above with reference to FIGS. 1 to 18. Below, an embodiment of the apparatus of the present application will be described in detail with reference to FIGS.

[0254] FIG. 19 is an exemplary block diagram of a terminal device 400 according to an embodiment of the present application.

[0255] The terminal device 400 shown in Figure 19 may correspond to the corresponding executing entity in the method 200 of the embodiment of the present application, and the above-mentioned operations and other operations and / or functions of each unit in the terminal device 400 are for realizing the corresponding process in each method of Figure 13. As shown in Figure 19, the terminal device 400 a communication unit 410 configured to receive a first control channel, the first control channel corresponding to a first shared channel; a processing unit 420 configured to not monitor control channel candidates in any time unit from the first time unit to the second time unit; Here, the first time unit is determined based on at least one of n, n+k, and n+m, and the second time unit is determined based on at least one of n, n+k, and n+m, where n represents the time unit in which the end position of the first control channel is located, n+k represents the time unit in which the transmission start position of the first shared channel is located, and n+m represents the time unit in which the transmission end position of the first shared channel is located.

[0256] In some embodiments, at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, and n+m and the first offset, or the first time unit is determined based on at least one of n, n+k, and n+m and the third offset, the first offset representing an offset between the uplink timing and downlink timing of the terminal device, and the third offset being greater than the first offset.

[0257] In some embodiments, at least one of n, n+k, and n+m is a time unit based on the uplink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, and n+m.

[0258] In some embodiments, at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal equipment, and the first time unit is determined based on at least one of n, n+k, and n+m and a second offset, and the second offset is configured by a network equipment.

[0259] In some embodiments, at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, and n+m.

[0260] In some embodiments, the downlink timing of the terminal device includes at least one first downlink time unit that fully overlaps or partially overlaps with a time unit determined based on at least one of n, n+k, and n+m, and the at least one first downlink time unit includes the first time unit.

[0261] In some embodiments, the at least one first downlink time unit is a plurality of first downlink time units, and the first time unit is any one of the first downlink time units or the earliest first downlink time unit of the plurality of first downlink time units.

[0262] In some embodiments, at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on at least one of n, n+k, and n+m and the first offset, or the second time unit is determined based on at least one of n, n+k, and n+m and the third offset, the first offset representing an offset between the uplink timing and downlink timing of the terminal device, and the third offset being greater than the first offset.

[0263] In some embodiments, at least one of n, n+k, and n+m is a time unit based on the uplink timing of the terminal device, and the second time unit is determined based on at least one of n, n+k, and n+m.

[0264] In some embodiments, at least one of n, n+k, n+m is a time unit based on downlink timing of the terminal equipment, and the second time unit is determined based on at least one of n, n+k, n+m and a second offset, the second offset being configured by a network device.

[0265] In some embodiments, at least one of n, n+k, and n+m is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on at least one of n, n+k, and n+m.

[0266] In some embodiments, the downlink timing of the terminal device includes at least one second downlink time unit that fully overlaps or partially overlaps with a time unit determined based on at least one of n, n+k, and n+m, and the at least one second downlink time unit includes the second time unit.

[0267] In some embodiments, the at least one second downlink time unit is a plurality of second downlink time units, and the second time unit is any one second downlink time unit of the plurality of second downlink time units or the latest second downlink time unit.

[0268] In some embodiments, the third offset represents an offset after extension of the uplink timing of the terminal device.

[0269] In some embodiments, the second offset is zero if the downlink timing of the network device is aligned with the uplink timing.

[0270] In some embodiments, the first time unit is determined based on n+k.

[0271] In some embodiments, if the first device is configured with two or more hybrid automatic repeat request (HARQ) processes, the first time unit is determined based on n+k.

[0272] In some embodiments, the first time unit is determined based on n.

[0273] In some embodiments, if the first device is configured with one hybrid automatic repeat request (HARQ) process, the first time unit is determined based on n.

[0274] In some embodiments, the second time unit is determined based on n+k.

[0275] In some embodiments, in a frequency division duplex (FDD) scenario, the second time unit is determined based on n+k.

[0276] In some embodiments, the second time unit is determined based on n+m.

[0277] In some embodiments, in a time division duplex (TDD) scenario, the second time unit is determined based on n+m.

[0278] In some embodiments, when the first device is configured with two or more Hybrid Automatic Repeat Request (HARQ) processes, in an FDD scenario, the first time unit comprises: at least one of n+k−2, n+k−2−O1, and n+k−2−O3; Here, O1 represents a first offset, O3 represents a third offset, the first offset represents an offset between the uplink timing and the downlink timing of the terminal device, and the third offset is greater than the first offset.

[0279] In some embodiments, when the first device is configured with two or more Hybrid Automatic Repeat Request (HARQ) processes, in an FDD scenario, the second time unit comprises: at least one of n+k-1, n+k-1+O2, n+k, and n+k+O2; Here, O2 represents a second offset, which is configured by a network device.

[0280] In some embodiments, when the first device is configured with two or more Hybrid Automatic Repeat Request (HARQ) processes, in a TDD scenario, the first time unit comprises: at least one of n+k, n+k-O1, and n+k-O3; Here, O1 represents a first offset, O3 represents a third offset, the first offset represents an offset between the uplink timing and the downlink timing of the terminal device, and the third offset is greater than the first offset.

[0281] In some embodiments, when the first device is configured with two or more Hybrid Automatic Repeat Request (HARQ) processes, in an FDD scenario, the second time unit comprises: at least one of n+m-1, n+m-1+O2, n+m, and n+m+O2; Here, O2 represents a second offset, which is configured by a network device.

[0282] In some embodiments, when the first device is configured with one Hybrid Automatic Repeat Request (HARQ) process, in an FDD scenario, the first time unit comprises: at least one of n+1, n+1-O1, and n+1-O3; Here, O1 represents a first offset, O3 represents a third offset, the first offset represents an offset between the uplink timing and the downlink timing of the terminal device, and the third offset is greater than the first offset.

[0283] In some embodiments, when the first device is configured with one Hybrid Automatic Repeat Request (HARQ) process, in an FDD scenario, the second time unit comprises: at least one of n+k-1, n+k-1+O2, n+k, and n+k+O2; Here, O2 represents a second offset, which is configured by a network device.

[0284] In some embodiments, when the first device is configured with one Hybrid Automatic Repeat Request (HARQ) process, in a TDD scenario, the first time unit comprises: at least one of n+1, n+1-O1, and n+1-O3; Here, O1 represents a first offset, O3 represents a third offset, the first offset represents an offset between the uplink timing and the downlink timing of the terminal device, and the third offset is greater than the first offset.

[0285] In some embodiments, when the first device is configured with one Hybrid Automatic Repeat Request (HARQ) process, in a TDD scenario, the second time unit comprises: at least one of n+m-1, n+m-1+O2, n+m, and n+m+O2; Here, O2 represents a second offset, which is configured by a network device.

[0286] In some embodiments, when the first device is configured with two or more hybrid automatic repeat request (HARQ) processes, time units prior to the first time unit are not used to monitor a second control channel for scheduling a second shared channel, wherein a transmission end position of the second shared channel is after a third time unit, and the length of time between the third time unit and the first time unit is a first predetermined value.

[0287] In some embodiments, the first predetermined value is P+2.

[0288] In some embodiments, P is 255, or P is an integer value less than 255.

[0289] In some embodiments, the communication unit 410 further comprises: The wireless communication device is configured to receive configuration information, the configuration information being used to determine at least one of a first offset, a second offset, and a third offset, the first time unit being determined based on at least one of n, n+k, n+m and at least one of the first offset, the second offset, and the third offset, and the second time unit being determined based on at least one of n, n+k, n+m and at least one of the first offset, the second offset, and the third offset.

[0290] The terminal device 400 shown in Figure 19 may correspond to the corresponding executing entity in the method 300 of the embodiment of the present application, and the above-mentioned operations and other operations and / or functions of each unit in the terminal device 400 are for realizing the corresponding process in each method of Figure 16. As shown in Figure 19, the terminal device 400 a communication unit 410 configured to transmit a first shared channel; and a processing unit 420 configured to not monitor control channel candidates and / or not receive data within a half-duplex protection interval or in any time unit from a first time unit to a second time unit, where the first time unit is determined based on s and the second time unit is determined based on s, and s represents the time unit in which a transmission end position of the first shared channel is located.

[0291] In some embodiments, the terminal device is in a frequency division duplex (FDD) scenario and / or the half-duplex protection interval comprises a configured type B half-duplex protection interval.

[0292] In some embodiments, s is a time unit based on the downlink timing of the terminal device, and the first time unit is determined based on s and the first offset, or the first time unit is determined based on s and the third offset, the first offset representing an offset between the uplink timing and downlink timing of the terminal device, and the third offset being greater than the first offset.

[0293] In some embodiments, s is a time unit based on an uplink timing of the terminal device, and the first time unit is determined based on s.

[0294] In some embodiments, s is a time unit based on downlink timing of the terminal device, and the first time unit is determined based on s and a second offset, and the second offset is configured by a network device.

[0295] In some embodiments, s is a time unit based on downlink timing of the terminal device, and the first time unit is determined based on s.

[0296] In some embodiments, the downlink timing of the terminal device includes at least one first downlink time unit that fully overlaps or partially overlaps with a time unit determined based on s, and the at least one first downlink time unit includes the first time unit.

[0297] In some embodiments, the at least one first downlink time unit is a plurality of first downlink time units, and the first time unit is any one of the first downlink time units or the earliest first downlink time unit of the plurality of first downlink time units.

[0298] In some embodiments, s is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on s and the first offset, or the second time unit is determined based on s and the third offset, the first offset representing an offset between the uplink timing and downlink timing of the terminal device, and the third offset being greater than the first offset.

[0299] In some embodiments, s is a time unit based on an uplink timing of the terminal device, and the second time unit is determined based on s.

[0300] In some embodiments, s is a time unit based on the downlink timing of the terminal device, and the second time unit is determined based on s and a second offset, the second offset being configured by a network device.

[0301] In some embodiments, s is a time unit based on downlink timing of the terminal device, and the second time unit is determined based on s.

[0302] In some embodiments, the downlink timing of the terminal device includes at least one second downlink time unit that fully overlaps or partially overlaps with a time unit determined based on s, and the at least one second downlink time unit includes the second time unit.

[0303] In some embodiments, the at least one second downlink time unit is a plurality of second downlink time units, and the second time unit is any one second downlink time unit of the plurality of second downlink time units or the latest second downlink time unit.

[0304] In some embodiments, the third offset represents an offset after extension of the uplink timing of the terminal device.

[0305] In some embodiments, the second offset is zero if the downlink timing of the network device is aligned with the uplink timing.

[0306] In some embodiments, the first time unit comprises: at least one of s+1, s+1-O1, and s+1-O3; Here, O1 represents a first offset, O3 represents a third offset, the first offset represents an offset between the uplink timing and the downlink timing of the terminal device, and the third offset is greater than the first offset.

[0307] In some embodiments, the second time unit comprises: at least one of s, s+1, s+O2, s+1+O2; Here, O2 represents a second offset, which is configured by a network device.

[0308] In some embodiments, the communication unit 410 further comprises: The system is configured to receive configuration information, the configuration information being used to determine at least one of a first offset, a second offset, and a third offset, the first time unit being determined based on s and at least one of the first offset, the second offset, and the third offset, and the second time unit being determined based on s and at least one of the first offset, the second offset, and the third offset.

[0309] FIG. 20 is an exemplary block diagram of a network device 500 according to an embodiment of the present application.

[0310] The network device 500 shown in Figure 20 may correspond to a corresponding executing entity in the method 200 of the embodiment of the present application, and the above-mentioned operations and other operations and / or functions of each unit in the network device 500 are for realizing the corresponding process in each method of Figure 13. As shown in Figure 20, the network device 500 includes: a communication unit 510 configured to transmit a first control channel, the first control channel corresponding to a first shared channel; a processing unit 520 configured to not transmit control channel candidates in any time unit from the first time unit to the second time unit; Here, the first time unit is determined based on at least one of n, n+k, and n+m, and the second time unit is determined based on at least one of n, n+k, and n+m, where n represents the time unit in which the end position of the first control channel is located, n+k represents the time unit in which the transmission start position of the first shared channel is located, and n+m represents the time unit in which the transmission end position of the first shared channel is located.

[0311] In some embodiments, the first time unit is determined based on n+k.

[0312] In some embodiments, if the first device is configured with two or more hybrid automatic repeat request (HARQ) processes, the first time unit is determined based on n+k.

[0313] In some embodiments, the first time unit is determined based on n.

[0314] In some embodiments, if the first device is configured with one hybrid automatic repeat request (HARQ) process, the first time unit is determined based on n.

[0315] In some embodiments, the second time unit is determined based on n+k.

[0316] In some embodiments, in a frequency division duplex (FDD) scenario, the second time unit is determined based on n+k.

[0317] In some embodiments, the second time unit is determined based on n+m.

[0318] In some embodiments, in a time division duplex (TDD) scenario, the second time unit is determined based on n+m.

[0319] In some embodiments, the communication unit 510 further comprises: The wireless communication device is configured to transmit configuration information, the configuration information being used to determine at least one of a first offset, a second offset, and a third offset, the first time unit being determined based on at least one of n, n+k, n+m and at least one of the first offset, the second offset, and the third offset, and the second time unit being determined based on at least one of n, n+k, n+m and at least one of the first offset, the second offset, and the third offset.

[0320] The network device 500 shown in Figure 20 may correspond to a corresponding executing entity in the method 300 of the embodiment of the present application, and the above-mentioned operations and other operations and / or functions of each unit in the network device 500 are for realizing the corresponding process in each method of Figure 16. As shown in Figure 20, the network device 500 a communication unit 510 configured to receive the first shared channel; and a processing unit 520 configured to not transmit control channel candidates and / or not transmit data within a half-duplex protection interval or in any time unit from a first time unit to a second time unit, where the first time unit is determined based on s and the second time unit is determined based on s, and s represents the time unit in which a transmission end position of the first shared channel is located.

[0321] In some embodiments, the terminal device is in a frequency division duplex (FDD) scenario and / or the half-duplex protection interval comprises a configured type B half-duplex protection interval.

[0322] In some embodiments, the communication unit 510 further comprises: The mobile station is configured to transmit configuration information, the configuration information being used to determine at least one of a first offset, a second offset, and a third offset, the first time unit being determined based on s and at least one of the first offset, the second offset, and the third offset, and the second time unit being determined based on s and at least one of the first offset, the second offset, and the third offset.

[0323] Thus, with reference to the drawings, the communication device of the present application has been described in terms of functional modules. It should be noted that the functional modules may be implemented in the form of hardware, software instructions, or a combination of hardware and software modules. Specifically, each step of the method embodiment in the present application may be completed by a hardware integrated logic circuit and / or software instructions in a processor. The method steps disclosed in the embodiments of the present application may be completed by a hardware decoding processor or a combination of hardware and software modules in the decoding processor. Optionally, the software modules may be located in a conventional storage medium such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium may be located in a memory, and the processor may read information in the memory and complete the steps of the above method embodiment in combination with the hardware.

[0324] For example, the processing unit and communication unit described above may be realized by a processor and a transceiver.

[0325] FIG. 21 is an exemplary block diagram of a communication device 600 according to an embodiment of the present application.

[0326] As shown in FIG. 21, the communication device 600 may include a processor 610 .

[0327] Here, the processor 610 can implement the method in the embodiment of the present application by calling and executing a computer program from the memory.

[0328] As shown in FIG. 21, the communication device 600 may further include a memory 620 .

[0329] Here, the memory 620 may be used to store instruction information, or may be configured to store codes, instructions, etc. to be executed by the processor 610. Here, the processor 610 can implement the methods in the embodiments of the present application by calling and executing computer programs from the memory 620. The memory 620 may be a separate device independent of the processor 610, or may be integrated into the processor 610.

[0330] As shown in FIG. 21, the communication device 600 may further include a transceiver 630 .

[0331] Here, the processor 610 can control the transceiver 630 to communicate with other devices, specifically, to transmit information or data to other devices or receive information or data transmitted by other devices. The transceiver 630 can include a transmitter and a receiver. The transceiver 630 can further include one or more antennas.

[0332] The components of the communication device 600 are connected by a bus system, which includes a power bus, a control bus, and a status signal bus in addition to a data bus.

[0333] Furthermore, the communication device 600 may be a terminal device in the embodiments of the present application, and the communication device 600 may implement the corresponding processes implemented by the terminal device in each method in the embodiments of the present application. That is, the communication device 600 in the embodiments of the present application may correspond to the terminal device 400 in the embodiments of the present application, and may correspond to the corresponding operating entity of the method 200 in the embodiments of the present application, and for the sake of brevity, the description thereof will not be repeated here. Similarly, the communication device 600 may be a network device in the embodiments of the present application, and the communication device 600 may execute the corresponding processes implemented by the network device in each method in the embodiments of the present application, and for the sake of brevity, the description thereof will not be repeated here. That is, the communication device 600 in the embodiments of the present application may correspond to the communication device 500 in the embodiments of the present application, and may correspond to the corresponding operating entity of the method 200 in the embodiments of the present application, and for the sake of brevity, the description thereof will not be repeated here.

[0334] Additionally, embodiments of the present application further provide a chip.

[0335] For example, the chip may be an integrated circuit chip with signal processing capabilities, and may implement or perform the methods, steps, and logical block diagrams disclosed in the embodiments of the present application. The chip may be called a system-level chip, a system chip, a chip system, a system-on-chip, etc. Optionally, the chip may be applied to various communication devices, so that the communication devices equipped with the chip can implement the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.

[0336] FIG. 22 is a schematic diagram showing the configuration of a chip 700 according to an embodiment of the present invention.

[0337] As shown in FIG. 22, the chip 700 may include a processor 710 .

[0338] Here, the processor 710 can implement the method in the embodiment of the present application by calling and executing a computer program from the memory.

[0339] As shown in FIG. 22, the chip 700 may further include a memory 720 .

[0340] Here, the processor 710 can implement the methods of the embodiments of the present application by calling and executing a computer program from the memory 720. The memory 720 may be used to store instruction information, or may be configured to store code, instructions, etc. to be executed by the processor 710. The memory 720 may be a separate device independent of the processor 710, or may be integrated into the processor 710.

[0341] As shown in FIG. 22, the chip 700 may further include an input interface 730 .

[0342] Here, the processor 710 can control the input interface 730 to communicate with other devices or chips, and specifically can obtain information or data sent by other devices or chips.

[0343] As shown in FIG. 22, the chip 700 may further include an output interface 740 .

[0344] Here, the processor 710 can control the output interface 740 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0345] It should be noted that the chip 700 may be applied to a network device in the embodiments of the present application, and the chip may execute the corresponding process implemented by the network device in each method in the embodiments of the present application, and may execute the corresponding process implemented by the terminal device in each method in the embodiments of the present application, which will not be repeated here for the sake of brevity.

[0346] The components of the chip 700 are connected by a bus system, which includes a power bus, a control bus, and a status signal bus in addition to a data bus.

[0347] The processor described above This may include, but is not limited to, a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc.

[0348] The processor can be configured to realize or execute each method, step, and logic block diagram disclosed in the embodiments of the present application. The steps of the methods disclosed in the embodiments of the present application may be directly performed by a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software modules can be located in conventional storage media such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage media is located in the memory, and the processor reads information in the memory and completes the steps of the above method in combination with the hardware.

[0349] The memory described above is This includes, but is not limited to, volatile and / or non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM) used as an external cache. By way of illustrative but non-limiting example, RAM may come in many forms, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus random access memory (DR RAM).

[0350] It should be noted that memory as described herein may include these and any other suitable types of memory.

[0351] The present embodiment further provides a computer-readable storage medium having a computer program stored thereon. The computer-readable storage medium stores one or more programs, the one or more programs including instructions, which, when executed by a portable electronic device including a plurality of applications, cause the portable electronic device to perform the method of the embodiment shown in method 200. Optionally, the computer-readable storage medium may be applied to a network device in the present embodiment, and the computer program causes a computer to perform corresponding processes implemented by the network device in each method of the present embodiment, which will not be described again for brevity. Optionally, the computer-readable storage medium may be applied to a mobile terminal / terminal device in the present embodiment, and the computer program causes a computer to perform corresponding processes implemented by the mobile terminal / terminal device in each method of the present embodiment, which will not be described again for brevity.

[0352] The present embodiment further provides a computer program product including a computer program. Optionally, the computer program product may be applied to a network device in the present embodiment, causing a computer to execute corresponding processes implemented by the network device in the methods of the present embodiment, which will not be described again for brevity. Optionally, the computer program product may be applied to a mobile terminal / terminal device in the present embodiment, causing a computer to execute corresponding processes implemented by the mobile terminal / terminal device in the methods of the present embodiment, which will not be described again for brevity.

[0353] An embodiment of the present application further provides a computer program, which, when executed by a computer, causes the computer to perform the method of the embodiment shown in method 200 or 300. Optionally, the computer program may be applied to a network device in an embodiment of the present application, and when executed by the computer, causes the computer to perform corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described again for the sake of brevity. Optionally, the computer program may be applied to a mobile terminal / terminal device in an embodiment of the present application, and when executed by the computer, causes the computer to perform corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described again for the sake of brevity.

[0354] An embodiment of the present application further provides a communication system, which may include the terminal equipment and network equipment described above to form the communication system 100 shown in Figure 1, and for the sake of brevity, the description will not be repeated here. Note that terms such as "system" in this specification may also be referred to as "network management architecture" or "network system".

[0355] Furthermore, the terms used in the examples and the appended claims are for the purpose of describing particular examples only and are not intended to limit the examples of the present application. For example, the singular forms "a," "the," "said," and "the" as used in the examples and the appended claims are intended to include the plural forms unless the context clearly dictates otherwise.

[0356] Those skilled in the art will understand that each exemplary unit and algorithm step described with reference to the embodiments disclosed herein may be realized by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented by hardware or software depends on the specific application and design constraints of the technical solution. Professionals may implement the described functions using different methods for each specific application, but such implementations should not be considered beyond the scope of the embodiments of the present application. When implemented in the form of a software functional module and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on this understanding, an essential part of the technical solution of the present application, i.e., a part that contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to execute all or part of the steps of the method described in the embodiments of the present application. The aforementioned storage medium includes various media capable of storing program code, such as a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk.

[0357] Those skilled in the art will understand that for convenience and brevity, the specific operating processes of the above-described systems, devices, and units can refer to the corresponding processes in the above-described method embodiments, and will not be described again here. It should be understood that in some embodiments provided herein, the disclosed systems, devices, and methods can be realized in other manners. For example, the division of units, modules, or components in the above-described device embodiments is merely a division of logical functions. In actual implementation, other division methods may be used. For example, multiple units, modules, or components may be integrated or integrated into another system, or some units, modules, or components may be ignored or not implemented. In another example, the units, modules, or components described above as individual / display components may or may not be physically separated, i.e., may be located in one place or distributed across multiple network units. Depending on actual needs, some or all of the parts therein may be selected to achieve the objectives of the technical solutions in the embodiments of the present application. Finally, it should be understood that the mutual couplings or direct couplings or communication connections displayed or discussed above may be realized using some communication interfaces, and that the indirect couplings or communication connections between the devices or units may be electrical, mechanical or in other forms.

[0358] The above content is only a specific embodiment of the embodiments of the present application, and the protection scope of the embodiments of the present application is not limited thereto. Any modifications or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the embodiments of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. 1. A wireless communication method, comprising: receiving, by a terminal device, a first control channel, the first control channel corresponding to a first shared channel; The terminal device does not monitor control channel candidates in any time unit from the first time unit to the second time unit; the first time unit is determined based on at least one of n, n+k, and n+m, and the second time unit is determined based on at least one of n, n+k, and n+m, where n represents the time unit in which the end position of the first control channel is located, n+k represents the time unit in which the transmission start position of the first shared channel is located, and n+m represents the time unit in which the transmission end position of the first shared channel is located; a downlink timing of the terminal device including at least one first downlink time unit that fully overlaps or partially overlaps with a time unit determined based on at least one of n, n+k, and n+m, and the at least one first downlink time unit includes the first time unit.

2. At least one of n, n+k, and n+m is a time unit based on an uplink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, and n+m. The wireless communication method according to claim 1 .

3. At least one of n, n+k, and n+m is a time unit based on a downlink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, and n+m. The wireless communication method according to claim 1 .

4. the at least one first downlink time unit is a plurality of first downlink time units, and the first time unit is any one of the plurality of first downlink time units or the earliest first downlink time unit; The wireless communication method according to claim 1 .

5. At least one of n, n+k, and n+m is a time unit based on an uplink timing of the terminal device, and the second time unit is determined based on at least one of n, n+k, and n+m. The wireless communication method according to any one of claims 1 to 4.

6. The downlink timing of the terminal device includes at least one second downlink time unit that fully or partially overlaps with a time unit determined based on at least one of the n, n+k, and n+m, and the at least one second downlink time unit includes the second time unit. The wireless communication method according to any one of claims 1 to 5.

7. the at least one second downlink time unit is a plurality of second downlink time units, and the second time unit is any one second downlink time unit of the plurality of second downlink time units or the latest second downlink time unit; The wireless communication method according to claim 6.

8. 1. A wireless communication method, comprising: a network device transmitting a first control channel, the first control channel corresponding to a first shared channel; The network device does not transmit a control channel candidate in any time unit from a first time unit to a second time unit; the first time unit is determined based on at least one of n, n+k, and n+m, and the second time unit is determined based on at least one of n, n+k, and n+m, where n represents the time unit in which the end position of the first control channel is located, n+k represents the time unit in which the transmission start position of the first shared channel is located, and n+m represents the time unit in which the transmission end position of the first shared channel is located; a downlink timing of a terminal device including at least one first downlink time unit that fully overlaps or partially overlaps with a time unit determined based on at least one of n, n+k, and n+m, and the at least one first downlink time unit includes the first time unit.

9. At least one of n, n+k, and n+m is a time unit based on an uplink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, and n+m. The wireless communication method according to claim 8.

10. At least one of n, n+k, and n+m is a time unit based on a downlink timing of the terminal device, and the first time unit is determined based on at least one of n, n+k, and n+m. The wireless communication method according to claim 8.

11. At least one of n, n+k, and n+m is a time unit based on an uplink timing of the terminal device, and the second time unit is determined based on at least one of n, n+k, and n+m. The wireless communication method according to any one of claims 8 to 10.

12. A terminal device, A terminal device comprising a processor, a memory and a transceiver, the memory storing a computer program, the processor cooperating with the transceiver to execute the method of any one of claims 1 to 7.

13. A network device, A network device comprising a processor, a memory and a transceiver, wherein the memory stores a computer program, and the processor cooperates with the transceiver to execute the method of any one of claims 8 to 11.

Images