Method and apparatus for wireless communication

WO2026236887A1PCT designated stage Publication Date: 2026-11-19QUECTEL WIRELESS SOLUTIONS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/094335
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-12
Publication Date
2026-11-19

Smart Images

  • Figure CN2025094335_19112026_PF_FP_ABST
    Figure CN2025094335_19112026_PF_FP_ABST
Patent Text Reader

Abstract

Provided are a method and apparatus for wireless communication. The method comprises: a terminal device receives a first downlink channel on the basis of first indication information, wherein the first indication information is associated with repeated transmission of the first downlink channel, the first downlink channel is used establishing a connection between the terminal device and a network device in an NTN, and the first indication information comprises a repeated transmission parameter of the first downlink channel, and / or a repeated transmission parameter of a second downlink channel related to the first downlink channel.
Need to check novelty before this filing date? Find Prior Art

Description

Methods and apparatus for wireless communication Technical Field

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

[0002] Non-terrestrial network (NTN) systems suffer from problems such as long transmission periods, wide frequency ranges, significant Doppler shift effects, and beam skipping. To enhance downlink coverage in NTN systems, repeated transmission of the downlink channel is introduced. However, how terminal equipment receives the repeated downlink transmissions becomes a technical problem that needs to be solved. Summary of the Invention

[0003] This application provides a method and apparatus for wireless communication. The various aspects related to the embodiments of this application are described below.

[0004] In a first aspect, a method for wireless communication is provided, comprising: a terminal device receiving a first downlink channel according to first indication information; wherein the first indication information is associated with repetition transmission of the first downlink channel, the first downlink channel being used by the terminal device to establish a connection with a network device in an NTN; the first indication information includes repetition transmission parameters of the first downlink channel, and / or repetition transmission parameters of a second downlink channel associated with the first downlink channel.

[0005] In a second aspect, a method for wireless communication is provided, comprising: a network device performing repeated transmission of a first downlink channel according to first indication information; wherein the first downlink channel is used for a terminal device to establish a connection with the network device in an NTN; the first indication information includes repeated transmission parameters of the first downlink channel, and / or repeated transmission parameters of a second downlink channel related to the first downlink channel.

[0006] Thirdly, an apparatus for wireless communication is provided, the apparatus being a terminal device, the apparatus comprising: a receiving unit configured to receive a first downlink channel according to first indication information; wherein the first indication information is associated with repetition transmission of the first downlink channel, the first downlink channel being used by the terminal device to establish a connection with a network device in an NTN; the first indication information includes repetition transmission parameters of the first downlink channel, and / or repetition transmission parameters of a second downlink channel associated with the first downlink channel.

[0007] Fourthly, an apparatus for wireless communication is provided, the apparatus being a network device, the apparatus comprising: a transmitting unit configured to perform repeated transmission of a first downlink channel according to first indication information; wherein the first downlink channel is used for a terminal device to establish a connection with the network device in an NTN; the first indication information includes repeated transmission parameters of the first downlink channel, and / or repeated transmission parameters of a second downlink channel related to the first downlink channel.

[0008] Fifthly, a communication device is provided, including a memory and a processor, the memory for storing a program, and the processor for calling the program in the memory to perform the method as described in the first or second aspect.

[0009] A sixth aspect provides an apparatus including a processor for calling a program from memory to perform the method as described in the first or second aspect.

[0010] A seventh aspect provides a chip including a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in the first or second aspect.

[0011] Eighthly, a computer-readable storage medium is provided having a program stored thereon that causes a computer to perform the method as described in the first or second aspect.

[0012] Ninth aspect, a computer program product is provided, including a program that causes a computer to perform the method as described in the first or second aspect.

[0013] In a tenth aspect, a computer program is provided that causes a computer to perform the method as described in the first or second aspect.

[0014] In this embodiment, the terminal device can receive repeatedly transmitted first downlink channels according to first indication information. The first indication information includes repeated transmission parameters of the first downlink channel and / or repeated transmission parameters of a second downlink channel related to the first downlink channel. Therefore, the terminal device can receive one or more first downlink channels according to the first indication information, which helps improve the transmission efficiency of the downlink channels. Attached Figure Description

[0015] Figure 1 shows the wireless communication system used in an embodiment of this application.

[0016] Figure 2 shows an NTN system used in an embodiment of this application.

[0017] Figure 3 shows another NTN system used in an embodiment of this application.

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

[0019] Figure 5 is a schematic diagram of two possible implementations of repeated transmission within a time slot.

[0020] Figure 6 is a schematic diagram of one possible implementation of inter-slot repetitive transmission.

[0021] Figure 7 is a schematic diagram of a device for wireless communication provided in an embodiment of this application.

[0022] Figure 8 is a schematic diagram of another device for wireless communication provided in an embodiment of this application.

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

[0024] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

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

[0026] Traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, communication systems can support not only traditional cellular communication but also one or more other types of communication. For example, a communication system can support one or more of the following communication methods: device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), enhanced machine-type communication (eMTC), vehicle-to-vehicle (V2V) communication, and vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to communication systems that support the above-mentioned communication methods.

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

[0028] The communication system in this application embodiment can be applied to unlicensed spectrum. This unlicensed spectrum can also be considered a shared spectrum. Alternatively, the communication system in this application embodiment can also be applied to licensed spectrum. This licensed spectrum can also be considered a dedicated spectrum.

[0029] The embodiments of this application can be applied to NTN systems. As an example, the NTN system can be a 4G-based NTN system, an NR-based NTN system, an Internet of Things (IoT)-based NTN system, or a narrowband Internet of Things (NB-IoT)-based NTN system.

[0030] A communication system may include one or more terminal devices. The terminal devices mentioned in the embodiments of this application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc.

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

[0032] In some embodiments, the terminal device may be a device that provides voice and / or data connectivity to a user. For example, the terminal device may be a handheld device, an in-vehicle device, etc., with wireless connectivity. As some specific examples, the terminal device may be a mobile phone, tablet, laptop, PDA, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc.

[0033] In some embodiments, the terminal device may be deployed on land. For example, the terminal device may be deployed indoors or outdoors. In some embodiments, the terminal device may be deployed on water, such as on a ship. In some embodiments, the terminal device may be deployed in the air, such as on an airplane, balloon, or satellite.

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

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

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

[0037] By way of example and not limitation, in the embodiments of this application, the network device may have mobility characteristics; for example, the network device may be a mobile device. In some embodiments of this application, the network device may be a satellite or a balloon station. In some embodiments of this application, the network device may also be a base station located on land, water, or other similar locations.

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

[0039] For example, FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of this application. The wireless communication system 100 shown in FIG1 includes a network device and multiple terminal devices. The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within the coverage area. The multiple terminal devices are, for example, terminal devices 120a to 120j in FIG1.

[0040] Optionally, the wireless communication system 100 shown in FIG1 may further include multiple network devices and each network device may include other number of terminal devices within its coverage area. This application embodiment does not limit this.

[0041] For example, Figure 2 is a schematic diagram of an architecture of the NTN system mentioned above. The NTN system 200 shown in Figure 2 uses satellite 210 as an airborne platform. As shown in Figure 2, the satellite radio access network includes satellite 210, service link 220, feeder link 230, terminal equipment 240, gateway (GW) 250, and network 260 including base stations and core network.

[0042] Satellite 210 is a spacecraft based on a space platform. Service link 220 refers to the link between satellite 210 and terminal equipment 240. Feeder link 230 refers to the link between gateway 250 and satellite 210. The Earth-based gateway 250 connects satellite 210 to the base station or core network, depending on the NTN architecture chosen.

[0043] The NTN architecture shown in Figure 2 is a bend-tube transponder architecture. In this architecture, the base station is located on Earth behind gateway 250, and satellite 210 acts as a relay. Satellite 210 operates as a relay that forwards signals from feeder link 230 to serving link 220, or forwards signals from serving link 220 to feeder link 230. That is, satellite 210 does not have the function of a base station; communication between terminal device 240 and the base station in network 260 needs to be relayed through satellite 210.

[0044] For example, Figure 3 is a schematic diagram of another architecture of the NTN system. As shown in Figure 3, the satellite radio access network 300 includes a satellite 310, a service link 320, a feeder link 330, a terminal device 340, a gateway 350, and a network 360. Unlike Figure 2, the satellite 310 has a base station 312, and the network 360 behind the gateway 350 only includes the core network.

[0045] Figure 3 shows the NTN architecture, which is a regenerative transponder architecture. In this architecture, satellite 310 carries base station 312, which can be directly connected to the Earth-based core network via a link. Satellite 310 has the function of a base station, and terminal device 340 can communicate directly with satellite 310. Therefore, satellite 310 can be referred to as a network device.

[0046] The communication system with the architecture shown in Figures 2 and 3 may include multiple network devices, and each network device may include other terminal devices within its coverage area. This application embodiment does not limit this.

[0047] In the embodiments of this application, the communication system shown in Figures 1 to 3 may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), which are not limited in this embodiment.

[0048] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Taking the communication system 100 shown in FIG1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 can be the specific devices described above, which will not be repeated here. The communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities, and other network entities. This application embodiment does not limit this.

[0049] To facilitate understanding, some related technical knowledge involved in the embodiments of this application is first introduced. The following related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0050] With the development of communication technologies, communication systems (such as 5G) will integrate the market potential of satellite and terrestrial network infrastructure. For example, the 5G standard makes NTN, including satellite segments, part of the recognized 3rd generation partnership project (3GPP) 5G connectivity infrastructure.

[0051] NTN refers to a network or network segment that uses radio frequency (RF) resources on spacecraft (e.g., satellites) or unmanned aerial system (UAS) platforms. Satellites are classified according to their orbital altitude, including low Earth orbit (LEO), medium Earth orbit (MEO), geostationary Earth orbit (GEO), and highly elliptical orbit (HEO). LEO is a geocentric orbit with an altitude of 2000 km or less, or at least 11.25 cycles per day, with an eccentricity of less than 0.25. Most man-made objects in outer space are located in LEO. LEO satellites orbit the Earth at high speeds (mobility), but in predictable or deterministic orbits.

[0052] Satellites at different orbital altitudes have different orbital periods. For example, typical LEO altitudes are 250-1500 km with orbital periods of 90-120 minutes; typical MEO altitudes are 5000-25000 km with orbital periods of 3-15 hours; and GEO altitudes are approximately 35786 km with orbital periods of 24 hours.

[0053] As shown in Figures 2 and 3 above, which use satellite as an example, typical scenarios for terminal devices accessing the NTN system involve either a transparent NTN payload or a regenerative NTN payload. Specifically, the bent-tube transponder architecture shown in Figure 2 corresponds to a transparent NTN payload, with the satellite or UAS platform acting as a relay; the regenerative transponder architecture shown in Figure 3 corresponds to a regenerative NTN payload, with a base station on the satellite or UAS platform. In the network architectures shown in Figures 2 and 3, the base station can involve various communication systems, such as NB-IoT.

[0054] In NTN systems, terminal devices communicate with network equipment via satellite or airborne platforms. Satellites and other airborne platforms cover a larger area; therefore, the number of terminal devices served within an NTN cell is typically much greater than in a terrestrial network (TN) cell. In NTN systems, enhancing uplink (UL) / downlink (DL) capacity and coverage, and improving spectrum utilization efficiency are worthwhile research topics.

[0055] Compared to terrestrial networks, NTN systems suffer from longer transmission cycles, wider frequency ranges, and greater Doppler shift. Since satellites cannot transmit all beams simultaneously, they typically employ periodic beam switching (beam hopping) to cover different areas. In other words, to meet the traffic demands of wide-area users, satellites can communicate based on beam hopping or beam switching. Specifically, satellites can periodically activate different beams in different areas / directions to achieve regional coverage. Furthermore, downlink coverage enhancement also needs to be considered.

[0056] In terrestrial networks, downlink control channels can enhance downlink coverage through repetitive transmissions. For example, relevant 3GPP protocols introduce intra-slot repetition of the physical downlink control channel (PDCCH), applicable only to the UE-specific search space (USS) and the type 3 common search space (CSS). In repetitive transmissions of the downlink control channel, each repetition can have the same number of control channel elements (CCEs) and coded bits, corresponding to the same downlink control information (DCI) payload. For example, coding / rate matching can be configured in one repetition, repeating the same coded bits in another.

[0057] However, in NTN systems, due to issues such as long transmission periods, wide frequency ranges, significant Doppler shift effects, and beam switching, repeated transmissions of the downlink control channel will face more challenges, and further enhancement of downlink coverage needs to be considered.

[0058] For example, for repeated transmissions within a time slot, the terminal device in the NTN may fail to decode the PDCCH in each time slot. Alternatively, when the terminal device performs a beam switch during PDCCH transmission, it may cause PDCCH errors or loss.

[0059] For example, in NTN, it is also necessary to consider the repeated transmission of PDCCH for downlink data channels (e.g., physical downlink shared channel, PDSCH) and other types of CSS besides type 3. In the NTN scenario, PDCCH CSS can be used for system information (SI) broadcasting, random access (RA), paging, and other control signaling transmissions. Among them, type 0A CSS is responsible for other system information (OSI) scheduling and is used for SIB transmission; type 1 CSS can be used for message 2 (Msg2) scheduling in the random access process; and type 2 CSS can be used to transmit paging PDCCH.

[0060] Furthermore, for terminal devices, how to receive repeatedly transmitted downlink data channels before establishing a connection with network devices is also a problem that needs to be considered. For example, during the correlation process of random access, the terminal device will receive PDSCH based on System Information Block (SIB) 1 and PDSCH based on Message 4. For beam-hopping scenarios in NTN systems that involve transmission delay and Doppler effect, the terminal device needs to know the repeated transmission parameters of the PDSCH in order to receive it appropriately according to its own capabilities. Also, how to configure the PDCCH and CSS corresponding to Type 0A, Type 1, and Type 2 CSS sets is another problem that needs to be solved.

[0061] In summary, how terminal devices receive repeated transmissions of the downlink channel in NTN systems is a technical problem that needs to be solved.

[0062] To address the aforementioned problems, this application proposes a method for wireless communication. Using this method, a terminal device in an NTN can receive a repeatedly transmitted first downlink channel based on first indication information. The first indication information may include repetition parameters of the first downlink channel and / or repetition parameters of a second downlink channel associated with the first downlink channel, which helps improve the efficiency of the terminal device in receiving the downlink channel and enhances the flexibility of downlink channel repetition transmission.

[0063] For ease of understanding, the method proposed in this application embodiment will be described in detail below with reference to Figure 4. Figure 4 is presented from the perspective of the interaction between the terminal device and the network device. The method shown in Figure 4 includes step S410.

[0064] The terminal device can be any type of communication terminal or relay described above, without limitation. In some embodiments, the terminal device can be any terminal device in the NTN system, such as a UE. In some embodiments, the terminal device can be any terminal device in the NB-IoT system, such as an electricity meter. In some embodiments, the terminal device can be any communication terminal within the coverage of the network device, such as terminal devices 120a to 120j in FIG1.

[0065] As one implementation, the terminal device is located within the coverage area of ​​the NTN satellite. For example, the terminal device is an NTN IoT terminal.

[0066] As one implementation, a terminal device is a communication device in any communication system that sends uplink data to devices on the network side.

[0067] In some implementations, the terminal device is any one of multiple terminal devices. These multiple terminal devices can be multiple communication terminals communicating with the satellite within an NTN cell. These multiple terminal devices can belong to a terminal device group, such as a first terminal device group.

[0068] The network device can be any of the network-side communication devices described above. In some embodiments, the network device includes a satellite in an NTN system, and the terminal device can communicate with the network device via the satellite. For example, when a base station is deployed on a satellite, the terminal device can communicate directly with the base station on the satellite. For example, when the satellite acts as a relay, the terminal device can communicate with a network device located on the ground via the satellite. As an embodiment, when the network device includes a satellite, the terminal device can be currently located within the service area of ​​that satellite to perform uplink transmission to the network device via the satellite.

[0069] As one implementation method, the network device can be a GEO satellite, or communicate with the terminal device via a GEO satellite.

[0070] As one implementation, network devices can be LEO satellites, or communicate with terminal devices via LEO satellites.

[0071] As one implementation method, the network device can be a MEO satellite, or communicate with the terminal device via a MEO satellite.

[0072] In some implementations, network devices can be replaced by satellites. Communication between the network device and the terminal device is equivalent to communication between the satellite and the terminal device.

[0073] In some implementations, multiple terminal devices within the first terminal device group are currently within the coverage area of ​​the same satellite.

[0074] Referring to Figure 4, in step S410, the terminal device receives the first downlink channel according to the first instruction information.

[0075] The first downlink channel can be a downlink data channel or a downlink control channel transmitted by a network device. For example, the first downlink channel may include a PDSCH. Alternatively, the first downlink channel may include a PDCCH. The PDCCH can be determined based on multiple PDCCH candidates.

[0076] As one implementation, the first downlink channel can be a data channel for transmitting message 4 during the random access procedure. That is, the first downlink channel is used to carry message 4 during the random access procedure. For example, the first downlink channel can be a PDSCH based on message 4.

[0077] As another implementation, the first downlink channel can be a data channel for transmitting system information blocks. For example, the first downlink channel can be a PDSCH for transmitting SIB1 / SIB19. By supporting repeated transmission of SIB1 / SIB19 via PDSCH, the decoding success rate of SIB1 / SIB19 in weak signal environments can be improved, ensuring that the terminal can correctly obtain system information. Weak signal environments can include high path loss areas in NTN (e.g., rural and remote areas), and can also include high latency scenarios (such as scenarios covered by GEO satellites).

[0078] As another implementation, the first downlink channel is the PDCCH of different CSS types. Different types of CSS can belong to the same control resource set (CORESET) or different CORESETs.

[0079] As another implementation, the first downlink channel is a PDCCH transmitted through one or more synchronization signal block (SSB) beams. In the embodiments of this application, SSB can also represent a synchronization signal (SS) / physical broadcast channel (PBCH) block, i.e., an SS / PBCH block.

[0080] It should be noted that dynamic SSB / SIB1 transmission based on beam hopping is a feasible mechanism in NTN systems. Satellites can dynamically adjust the transmission of common signals as needed. For example, satellites will only transmit the SSB and SIB1 of a specific beam "on demand" when there is an initial access request from a terminal device or when a periodic window arrives. This dynamic transmission reduces unnecessary duplicate broadcasts and improves power utilization. Simultaneously, terminal devices can prepare in advance based on known hopping cycles, listening for the SSB / SIB1 of a specific beam at predetermined times. Furthermore, starting with Rel-18, 3GPP research on satellite power-saving technologies includes schemes such as on-demand transmission of common signals.

[0081] In some implementations, the first downlink channel can be a downlink channel used before or during the connection establishment process between the terminal device and the network device. Alternatively, the first downlink channel can be used to establish a connection between the terminal device and the network device in the NTN. Exemplarily, this connection can be an initial connection between the terminal device and the network device, or a connection that needs to be restored. Exemplarily, this connection can be a radio resource control (RRC) connection.

[0082] The first indication information is used to indicate the repeated transmission of the first downlink channel. The terminal device can receive the repeated downlink channel according to the first indication information. The network device can perform repeated transmission of the first downlink channel according to the first indication information, thereby enhancing downlink coverage through repeated transmission and adapting to different channel conditions by improving downlink reliability.

[0083] For example, repeated transmission of the first downlink channel can refer to the first downlink channel being transmitted N times, where N is an integer greater than 1. Therefore, repeated transmission of the first downlink channel refers to the network device transmitting the same data or signaling N times in the first downlink channel.

[0084] In some implementations, the retransmission of the first downlink channel can be either a retransmission of PDSCH or a retransmission of PDCCH. PDSCH retransmission scenarios can include both message 4-based PDSCH retransmission and SIB1-based PDSCH retransmission. PDCCH retransmission requires consideration of the configuration of the search space (SS) used for retransmitting the PDCCH.

[0085] The first indication information can be used by the terminal device and the network device to determine the retransmission configuration of the first downlink channel. This retransmission configuration can be used to indicate the transmission resources of N first downlink channels. In some implementations, the first downlink channel received by the terminal device can be at least one of the N first downlink channels. For example, the terminal device can receive one first downlink channel. Alternatively, the terminal device can receive multiple first downlink channels and determine the retransmission configuration based on these multiple first downlink channels.

[0086] In some implementations, receiving the first downlink channel by the terminal device also includes combining at least two received first downlink channels to improve the decoding success rate of the first downlink channel. The downlink channel combining method is determined by the terminal device and may include soft combining at the log likelihood ratio (LLR) level, such as maximum ratio combining (MRC).

[0087] In one implementation, the terminal device combines multiple received first downlink channels. This combining is related to the quality of at least one of the multiple first downlink channels. At least one first downlink channel can participate in the combining through a quality weighting factor.

[0088] As an example, terminal devices can improve PDCCH decoding success rate through LLR soft combining. For instance, the terminal device can monitor the PDCCH in time slots n0 and n0+X and perform LLR-level soft combining based on MRC. The combined LLR' satisfies the following formula: LLR' = LLR n0 +α*LLR n0+X ;

[0089] Where α is the channel quality weighting factor.

[0090] As an implementation approach, when the number of repeated transmissions is fixed at two, it means that the terminal device can combine and decode repeated transmissions from two consecutive or discontinuous time slots. Based on soft combining, the decoding success rate can be improved. For example, when the terminal device knows, according to its configuration, that PDCCH candidate transmissions are repeated in two consecutive time slots, it can perform soft combining on these two candidates during reception. Through combining, the terminal device can achieve a higher signal-to-noise ratio, thereby improving the success rate of DCI decoding.

[0091] As an implementation method, soft combining can improve the efficiency of PDCCH blind detection by terminal devices. For advanced NTN terminal devices, PDCCH blind detection and soft combining can be performed in two time slots. For traditional terminal devices, after monitoring the PDCCH in time slot n, due to limited coverage, the PDCCH may be decoded correctly or incorrectly. If the PDCCH in time slot n is not decoded correctly, the traditional terminal device may not be able to find the PDSCH scheduled in time slot n. The terminal device can continue to perform PDCCH blind decoding in time slot n+1.

[0092] In the above implementation, the terminal device can receive PDCCH in multiple time slots and perform soft combining based on LLR level, thereby improving the reliability of PDCCH. For example, the terminal device can store PDCCH soft information received in different time slots and perform MRC to ensure the reliability of PDCCH under long latency, reduce NTN resource consumption, and improve scheduling flexibility.

[0093] The first indication information may include repetition transmission parameters of the first downlink channel and / or repetition transmission parameters of the second downlink channel associated with the first downlink channel. Therefore, the first indication information can directly indicate the repetition transmission configuration of the first downlink channel, or it can implicitly indicate the repetition transmission configuration of the first downlink channel based on the repetition transmission of the second downlink channel.

[0094] In some implementations, the second downlink channel associated with the first downlink channel can be one of the following: a control channel for scheduling the first downlink channel; or a data channel received by the terminal device before receiving the first downlink channel.

[0095] In one implementation, the first downlink channel is the PDSCH for transmitting message 4, and the second downlink channel is the PDSCH for transmitting SIB1. The terminal device can receive the PDSCH for transmitting SIB1 before transmitting message 4 and perform random access based on the information in SIB1.

[0096] In another implementation, the first downlink channel is a first PDSCH, and the second downlink channel is a PDCCH that schedules the first PDSCH. The first PDSCH can be the PDSCH for transmitting message 4, the PDSCH for transmitting SIB1 / SIB19, or any other PDSCH. For example, the first downlink channel can be the PDSCH for transmitting SIB1, and the second downlink channel can be the PDCCH that schedules the transmission of SIB1. Or, the first downlink channel can be the PDSCH for transmitting message 4, and the second downlink channel can be the PDCCH that schedules the transmission of message 4.

[0097] In the above implementation, when the second downlink channel is PDCCH, PDCCH can correspond to the first transmission mode. The first transmission mode can be used to determine the repetition transmission parameters of PDCCH. The first transmission mode is related to CSS. For example, the transmission type of the first transmission mode can correspond to different types of CSS. Furthermore, the transmission type of the first transmission mode can be determined based on the CSS configuration.

[0098] As an example, the transmission type of the first transmission mode can correspond to one of PDCCH Type 0A CSS, PDCCH Type 1 CSS, and PDCCH Type 2 CSS. PDCCH Type 0A CSS can be replaced with PDCCH CSS of type 0A; PDCCH Type 1 CSS can be replaced with PDCCH CSS of type 1; and PDCCH Type 2 CSS can be replaced with PDCCH CSS of type 2.

[0099] In the above example, when the transmission type of the first transmission mode corresponds to PDCCH Type 0A CSS, the PDCCH supports repeated transmission between time slots; when the transmission type of the first transmission mode corresponds to PDCCH Type 1 CSS or PDCCH Type 2 CSS, the PDCCH supports repeated transmission within time slots and repeated transmission between time slots. The repeated transmission supported by the PDCCH can refer to repeated transmission of the PDCCH itself, or to repeated transmission of the PDSCH scheduled by the PDCCH.

[0100] For example, when the transmission type of the first transmission mode corresponds to PDCCH Type0A CSS, the repeated transmission of PDCCH is the repeated transmission between time slots, and / or, the repeated transmission of the first downlink channel is the repeated transmission between time slots.

[0101] For example, when the transmission type of the first transmission mode corresponds to PDCCH Type1 CSS or PDCCH Type2 CSS, the repeated transmission of PDCCH is one of inter-slot repeated transmission and intra-slot repeated transmission, and / or, the repeated transmission of the first downlink channel is one of inter-slot repeated transmission and intra-slot repeated transmission.

[0102] In some implementations, the retransmission parameters may include one or more of the following: the number of retransmissions, the retransmission type, the retransmission duration, and the time-frequency resources for the retransmission. The number of retransmissions indicates the number of first downlink channels; the retransmission type may include inter-time-unit retransmissions and intra-time-unit retransmissions. The retransmission duration indicates the time required for the network device to complete the retransmission; the time-frequency resources for the retransmission include one or more time units used for the retransmission. These retransmission parameters may be for the first downlink channel or for the second downlink channel.

[0103] In some implementations, the number of retransmissions can be one of 2, 4, or 8, or an integer greater than or equal to 1. It should be understood that the number of retransmissions can include the first downlink channel transmission, or it can only include multiple downlink channels after the first transmission. For example, a retransmission count of 2 could mean that the network device transmits a total of 2 first downlink channels, or it could mean that the network device transmits the first first downlink channel followed by 2 more first downlink channels.

[0104] As an implementation method, the number of retransmissions can also be referred to as the repetition factor or repetition count of the downlink channel. The number of retransmissions can be one of several candidate retransmission counts. These candidate retransmission counts can be determined through protocol predefinition or higher-layer signaling.

[0105] As one implementation, when the first downlink channel is a data channel, the number of retransmissions is 2 or 4. For example, when the first downlink channel is a PDSCH with message 4, the candidate number of retransmissions for the first downlink channel can include 2 and 4. Alternatively, when the first downlink channel is a PDSCH used to carry SIB1, the number of retransmissions for the first downlink channel can be fixed at 2.

[0106] As one implementation, when the first downlink channel is a control channel, the number of repetitions is a positive integer greater than 1. For example, when the first downlink channel is a PDCCH, the number of repetitions for the first downlink channel can be an integer such as 2, 3, or 4.

[0107] In some implementations, the repetitive transmission type can include repetitive transmission between time units and repetitive transmission between time units. The time unit can be a subframe, time slot, symbol, etc., and is not limited here.

[0108] As an implementation method, the retransmission type can include inter-slot retransmission and intra-slot retransmission.

[0109] As an implementation, repeat transfer types can include repeat transfers between symbols and repeat transfers within symbols.

[0110] As an implementation, retransmission types can include inter-frame retransmission and intra-frame retransmission.

[0111] In some implementations, the retransmission duration can be the time range for repeated transmissions on the first downlink channel or the second downlink channel. In other words, the retransmission duration can be used to indicate the length of time it takes for the first or second downlink channel to complete repeated transmissions, thus avoiding continuous downlink channel monitoring by the terminal device and saving power. The retransmission duration can be predefined by the protocol.

[0112] As one implementation, the first downlink channel is the data channel for transmitting system information blocks, and the maximum time for repeated transmission is 20 milliseconds. In other words, when the first downlink channel is a PDSCH based on SIB1, the repeated transmission duration can be 20 milliseconds. For example, in NTN or low-coverage scenarios, to enhance the reliability of system broadcast information (such as SIB1 and SIB19), the PDSCH needs to repeat within 20 milliseconds, and the number of repeated transmissions can be fixed at 2.

[0113] As one implementation, the time-domain resources corresponding to the repeated transmission duration include the resources for multiple repeated transmissions of the first downlink channel.

[0114] In some implementations, the time-frequency resources for repeated transmissions may include time-domain resources and / or frequency-domain resources. Time-frequency resources may include one or more time units for repeated transmissions, as described above. Frequency-domain resources may include one or more carriers, frequency ranges, subbands, bandwidth portions, etc., for repeated transmissions, and are not limited thereto.

[0115] As one implementation, the time-domain resources for repeated transmissions can be a single time unit. For example, the first downlink channel can be a repeated transmission within a time slot, where a time unit is a time slot.

[0116] In the above implementation, when the first downlink channel is a PDCCH, the repetition of two PDCCHs transmitted in the search spaces of the two connections can be combined with repetitions within the same time slot. The search spaces of the two connections can be different types of CSSs or the same type of CSSs. Different types of CSSs can be type 1 CSSs and type 2 CSSs.

[0117] To facilitate understanding, the following example, using Figure 5, illustrates two repetition methods for intra-slot retransmission. In Figure 5, the first downlink channel is the PDCCH, and the number of repetitions is 2, representing the first repetition (1... st rep) and the second repetition (2) ndThe first and second repetitions can correspond to Type 1 CSS and Type 2 CSS, respectively. The intra-slot repetition of PDCCH can include 2 DCIs, and the 2 DCIs have the same payload, scheduling offset "K0", and resource allocation field.

[0118] As shown in Figure 5, within time slot t, the symbols of the first and second repetitions in repetition mode 1 are consecutive; the symbols of the first and second repetitions in repetition mode 2 are discontinuous. In repetition mode 1, the DCI of the first repetition occupies symbols 1 and 2, and the DCI of the second repetition occupies symbols 3 and 4. In repetition mode 2, the DCI of the first repetition occupies symbols 1 and 2, and the DCI of the second repetition occupies symbols 8 and 9.

[0119] In Figure 5, the DCIs in the first and second repetitions are the same. Since the DCI can be used to schedule PDSCH, the time / frequency resources for the corresponding PDSCH transmissions are also the same. As an implementation, PDCCH repetition within a time slot can be used to support one or two DCIs scheduling one PDSCH transmission.

[0120] The repetition method shown in Figure 5 can be used for PDSCH repetition of SIB1, as well as PDCCH repetition corresponding to CSS of type 0. That is, PDSCH repetition based on SIB1 and some PDCCH repetitions can be transmitted in the same time slot.

[0121] As one implementation, when the time-domain resources for repeated transmission are multiple time units, the first downlink channel transmits within each of these multiple time units. For example, if the multiple time units are multiple time slots, the repeated transmission of the first downlink channel is inter-slot repeated transmission. Compared to intra-slot repeated transmission, inter-slot repeated transmission ensures that the terminal device can still receive data in different time slots.

[0122] To facilitate understanding, Figure 6 is used as an example to illustrate inter-slot repetitive transmission. In Figure 6, the first downlink channel is the PDCCH, and the number of repetitions is 2, namely the first repetition and the second repetition.

[0123] As shown in Figure 6, the first repetition of the PDCCH is transmitted in time slot ti, and the second repetition is transmitted in time slot tj. In time slot ti, the first repetition of the DCI occupies symbols 1 and 2; in time slot tj, the second repetition of the DCI also occupies symbols 1 and 2.

[0124] In Figure 6, the same DCI is transmitted in different PDCCH candidates in different time slots. The network can schedule multiple PDSCHs, each PDSCH corresponding to a scheduled DCI, to simplify scheduling. If the scheduled PDSCHs are the same, soft combination of PDSCHs can be achieved through terminal equipment. Repeated transmission of PDCCHs between time slots usually means that multiple DCIs schedule multiple PDSCHs.

[0125] In the above implementation, when the PDCCH repeats in two time slots, the transmission of the associated PDSCH can also repeat in those two time slots. The associated PDSCH can refer to the PDSCH scheduled by the PDCCH. As an implementation, each PDSCH repetition occurs within the same time slot used to schedule each PDCCH candidate for DCI. Two associated PDSCH repetitions can have the same redundancy version (RV). PDSCH repetition transmission based on inter-slot repetition helps improve decoding success rate.

[0126] In the above implementation, inter-slot repetition of PDCCH can be achieved through explicit connections between two or more search space sets. These connected search space sets can be associated with different CORESETs with different transmission configuration indicator (TCI) states, thereby achieving beam diversity of PDCCH transmission. By restricting the configuration of the search space sets of two connections, connections can be specified at the PDCCH candidate level to ensure a one-to-one mapping between monitoring timing and PDCCH candidates within the set. The terminal device can also report whether linked PDCCH candidates require two or three blind decodings.

[0127] In some implementations, the repetition mode of the first downlink channel is related to the associated information of the first downlink channel. For example, when the first downlink channel is a PDCCH, the repetition mode is related to the CSS type of the PDCCH. That is, different types of CSS can support different repetition modes. As one implementation, a CSS of type 0A can only support repetition between time slots, and the number of repetitions is N, where N is a positive integer, such as 2, 3, or 4. As another implementation, CSS of type 1 and CSS of type 2 can support repetition both within and between time slots, and the number of repetitions is N, where N is a positive integer, such as 2, 3, or 4.

[0128] As one implementation, when the time-domain resource for repeated transmission is multiple time units, the repeated transmission can be intra-beam repeated transmission or inter-beam repeated transmission. When the first downlink channel is PDCCH, depending on the associated SSB beam, there are two types of inter-slot PDCCH repeated transmission. One is PDCCH repeated transmission within one SSB beam, and the other is PDCCH repeated transmission across multiple SSB beams.

[0129] For PDCCH repetition within an SSB beam, PDCCH transmission spans multiple time slots within each beam, thus requiring a longer dwell time. To ensure a longer dwell time, the dwell time of the common signal transmission covered by each beam needs to be extended. As one implementation, the SSB beam corresponding to SSB index 0 can transmit in time slots i and j.

[0130] For PDCCH repetition between SSB beams, this PDCCH repetition can be transmitted during a common beam scan. In some scenarios of NTN systems, to avoid coverage holes between adjacent beam coverage areas, each beam coverage area uses a 50km diameter. The signal from each beam coverage area can be received within the target equivalent isotropic radiated power (EIRP) of the corresponding beam coverage area, but can also be received outside the 50km diameter beam coverage area. This means that within any beam coverage area, the terminal equipment can actually receive signals from several adjacent beam coverage areas. If the PDCCH transmitted within adjacent beam coverage areas is the same, the signal leaked into adjacent beam coverage areas can be used to improve the performance of common channels (such as common PDCCH). For example, by combining PDCCH CSS from different beams within adjacent beam coverage areas, not only can coverage be improved, but the dwell time of common signal transmission for each beam footprint can also be affected.

[0131] As an implementation method, inter-beam repetition can also be called cross-SSB repetition. When the network side sends SI and schedules DCI through SIBx, DCI can be repetitively transmitted across SSBs to ensure that terminal devices can receive correctly in different beams. It should be noted that inter-SSB beam repetition (time slot n0, n+1) can work together with intra-SSB beam repetition in time slots n0 and n+1.

[0132] As one implementation, for the inter-beam repetition transmission mechanism, the PDCCH can be repeated in different SSBs to ensure that the NTN terminal equipment may experience beam switching. For example, the first repetition time slot n0 is associated with SSB-0, and the second repetition time slot n+1 is associated with SSB-1. Based on the PDCCH replication during SSB beam switching, it is ensured that the terminal equipment can receive DCI under different beams.

[0133] Whether it's intra-beam or inter-beam repetition, the buffering time on the terminal device side needs to be longer to perform soft combination of DCI repetition in time slots n0 and n+1. Beam coverage switching may affect PDCCH decoding, as NTN terminal devices may enter different beams in different time slots. Based on PDCCH repetition across multiple time slots, the terminal device can correctly decode the PDCCH.

[0134] In some implementations, the time-domain resources for repeated transmission of the first downlink channel can be continuous or discontinuous. In other words, the time-domain resources for repeated transmission can be multiple continuous time units or multiple discontinuous time units. When the time unit is a time slot, the first downlink channel can be repeatedly transmitted through continuous time slots (e.g., time slot tj is adjacent to time slot ti in Figure 6) or through discontinuous time slots (e.g., time slot tj is not adjacent to time slot ti in Figure 6).

[0135] The following section uses the example of a first downlink channel being PDCCH and a time unit being a time slot, and introduces several implementation methods.

[0136] As one implementation, for the repetition of consecutive time slots, the repeated transmission of PDCCH can be within the same beam. For example, for consecutive time slots n0 and n0+1, the repeated transmission of PDCCH can be based on the same SSB beam.

[0137] As one implementation, for repetition of consecutive time slots, PDCCH retransmission can be inter-beam retransmission. That is, in consecutive time slots n0 and n0+1, PDCCH retransmission across SSB beams can be performed. PDCCH candidates in time slot n0 associated with different SSB indices are repetitions of each other and can share the same aggregation level (AL), coded bits, and candidate index. For example, in time slot n0, the network device selects a PDCCH candidate from the search space (e.g., SS-Set-1 in CORESET-1) corresponding to SSB index A (e.g., SSB-0) and generates a DCI using a predetermined aggregation level and coding parameters. In the immediately following time slot n0+1, the network device retransmits the same DCI from the search space (e.g., SS-Set-2 in CORESET-2) corresponding to a different SSB index B (e.g., SSB-1). The PDCCH candidates in the two time slots can be completely consistent at the physical layer (including the same coded bits, modulation scheme and candidate index), only they are transmitted on different beams (determined by different SSB indices).

[0138] The above implementation is illustrated using two consecutive time slots as an example. It should be understood that the PDCCH can be repeatedly transmitted over multiple consecutive time slots to increase the opportunities for terminal devices to monitor the PDCCH. Network devices can indicate PDCCH repetition in DCI 1_0 or DCI 1_1, allowing the PDCCH to repeat within consecutive time slots (e.g., time slots n, n+1, n+2). The search space set (SS set) can be extended to allow NTN terminal devices to monitor the PDCCH across multiple consecutive time slots.

[0139] For example, based on the search space implementation, search space sets configured in multiple consecutive time slots can correspond to the same CORESET. Specifically, time slot n: CORESET-1, SS-Set-1; time slot n+1: CORESET-1, SS-Set-2; time slot n+2: CORESET-1, SS-Set-3, and so on. Based on this configuration, PDCCH errors caused by Doppler variations can be reduced, lowering the blind decoding burden on terminal equipment. Furthermore, through cross-time slot repetition and soft combining, not only is beam diversity achieved, but the scheduling reliability throughout the random access process is also improved.

[0140] In scenarios where the first downlink channel is a data channel, the terminal device can perform reception and merging of the first downlink channel by monitoring and scheduling the PDCCH of this data channel. For example, when the first downlink channel is a PDSCH for transmitting SIB1, each SSB index can have two candidate SIB1 transmissions on two time slots. The system can select one of the two time slots to schedule the transmission of SIB1. The terminal device can monitor the PDCCH in the CSS set on these two time slots. This method supports soft merging of two candidate SIB1s in time slots n0 and n+1, and also supports PDCCH repetition by connecting two search spaces or connecting two monitoring times in one search space.

[0141] As one implementation, for the repetition of discontinuous time slots, PDCCHs in slot n0 associated with different SSB indices can share the same aggregation level, coding bits, and candidate index. For example, the repetition of discontinuous time slots can support repeated PDCCH candidates in two time slots n0 and n0+X (or time slots n0+1 and n0+1+X) associated with the same SSB index, where X>1 and X is a predefined or pre-configured value. Repeated PDCCH candidates can share the same aggregation level, coding bits, and candidate index.

[0142] In the above implementation, the PDCCH can be repeated in two discontinuous time slots (such as time slots n0 and n0+X) and associated with the same SSB. Network devices can instruct the PDCCH to repeat in future discontinuous time slots via DCI 1_0 or DCI 1_1 to ensure that terminal devices monitor the PDCCH only in the specified time slots.

[0143] When the time-domain resources being repeatedly transmitted are multiple non-contiguous time units, the duration between adjacent time units needs to be limited to ensure system latency and avoid making terminal devices wait for too long.

[0144] As one implementation, the duration of adjacent time units can be an absolute duration or indicated by the number of time units. For example, the number X of time units between any two adjacent time units in a set of time units satisfies the following condition:

[0145] Where T represents the duration of a time unit, T max T represents the upper limit of latency. RTTX represents the round-trip time (RTT) for communication between the terminal device and the network device, and γ represents the ratio between the upper limit of latency and the RTT. By controlling the maximum value of X, it can be ensured that the latency caused by the repetition of discontinuous time slots will not exceed the upper limit allowed by the system, thereby avoiding excessive waiting time for the terminal device and preventing excessive waiting delay from having an excessive impact on the overall RTT.

[0146] As one implementation approach, assume the time unit is a time slot, and the duration T of each time slot can be either 0.5ms or 1ms. The system's allowed upper limit for additional delay (latency cap) T. max For example, it is 20ms. Since repeated transmissions occur between time slots n0 and n0+X, the terminal device's waiting delay roughly satisfies the following condition: T delay = X*T. Furthermore, since γ is the proportion of the system's allowed additional delay not exceeding RTT, the waiting delay satisfies the following condition: X*T ≤ min{T} max ,γ*T RTT}

[0147] In the above implementation, the network device can instruct the PDCCH to be repeatedly transmitted in future discontinuous time slots via DCI 1_0 or DCI 1_1. For example, the terminal device can monitor the same PDCCH in multiple discontinuous time slots (such as time slots n, n+3, n+6). The search space sets configured in the multiple discontinuous time slots can correspond to different CORESETs. Specifically, time slot n: CORESET-1, SS-Set-1; time slot n+3: CORESET-2, SS-Set-2; time slot n+6: CORESET-3, SS-Set-3, and so on.

[0148] In some implementations, the first indication information includes retransmission parameters for the first downlink channel, so that network devices and terminal devices can directly perform retransmission and reception of the first downlink channel based on the retransmission parameters.

[0149] In some implementations, the first indication information includes the retransmission parameters of the second downlink channel. Network devices and terminal devices can determine the retransmission parameters of the first downlink channel based on the retransmission parameters of the second downlink channel. For example, when the first downlink channel is a PDSCH based on message 4 and the second downlink channel is a PDSCH based on SIB1, the retransmission parameters of the PDSCH transmitting message 4 can be implicitly determined based on the retransmission parameters of the PDSCH transmitting SIB1. Alternatively, when the first downlink channel is the first PDSCH, the retransmission parameters of the first PDSCH can be determined based on the indirect indication from the PDCCH that schedules the first PDSCH.

[0150] As one implementation, network devices can indirectly control the repetition factor of the first PDSCH through the scheduling information of the PDCCH. As an example, network devices can use different radio network temporary identifiers (RNTIs) in the scheduling to indicate different repetition factors. These RNTIs could be, for example, temporary cell RNTIs (TC-RNTIs) or cell RNTIs (C-RNTIs). As another example, network devices can implicitly indicate the repetition factor of the first PDSCH through the time-frequency resources scheduled by the PDCCH. For example, specific reserved resources can be used for specific repetition transmission configurations.

[0151] In the above implementation, when the first downlink channel is the first PDSCH scheduled by the PDCCH, the time unit for transmitting the first PDSCH is adjacent to or close to the time unit for transmitting the PDCCH. For example, when the PDCCH is a PDSCH with SIB1 repetition, the PDSCH can be transmitted after the time slot with type 0 PDCCH CSS repetition. Furthermore, the SIB1 PDCCH and PDSCH can be repeatedly transmitted on the SSB beams corresponding to time slot i and time slot i+2, respectively.

[0152] As one implementation, when the first downlink channel is the PDSCH for transmitting SIB1, the network device can enable the retransmission of SIB1 by scheduling SIB1 through DCI, or it can implicitly indicate the retransmission of SIB1 by retransmitting PDCCH.

[0153] As one implementation, some parameters in the repetition parameters of the first downlink channel are the same as their corresponding parameters in the repetition parameters of the second downlink channel. For example, the number of repetitions in the first downlink channel is the same as the number of repetitions in the second downlink channel. For instance, when the repetition indication of the PDCCH implicitly includes the repetition indication of the first PDSCH, the number of repetitions for the PDCCH and the first PDSCH is the same. That is, when scheduling the DCI repetition of the first PDSCH, the first PDSCH can be repetitive synchronously to ensure the integrity of data transmission. If the number of repetitions for the PDCCH and the first PDSCH are different, they need to be indicated separately.

[0154] In some implementations, the first indication information includes repetition transmission parameters for the first and second downlink channels. When the first downlink channel is the PDSCH for transmitting SIB1 and the second downlink channel is the PDCCH for scheduling SIB1, the first indication information can also incorporate beamgroup and CORESET configuration coordination. As one implementation, when a beam is activated in the current time slot to cover an area, the PDCCH / PDSCH transmission of SIB1 can be scheduled immediately after the SSB of that beam to ensure that terminal devices in that area receive SIB1 information in a timely manner. If beam switching occurs, SIB1 broadcasting needs to be repeated to increase the reception opportunities for terminal devices. If a beam leaves an area for an extended period, the latest SIB1 can be rebroadcast when the beam covers the area again.

[0155] As one implementation, the first indication information can include the correspondence between beam groups and CORESETs. For example, multiple related beams can be grouped together, sharing the same CORESET0 and search space within the group to configure SIB1. Thus, the same SIB1 can be carried by different beams at different times. Therefore, corresponding PDCCH resources (e.g., multiple TCI states of CORESET0) can be pre-configured for each possible beam direction. When a beam is activated, the terminal device monitors SIB1 on the CORESET corresponding to that beam. This way, even if the SSB beam changes continuously, the control channel of SIB1 can always find its location under the corresponding beam and will not fail due to beam changes. To support this flexible scheduling, the allocation of PDCCH CORESET resources needs to be sufficiently general and switchable. For example, network devices can configure multiple type 0 PDCCH search spaces via RRC, each corresponding to a different SSB index or beam. When a beam changes, the corresponding search space is activated by switching. The network-side scheduler also needs to identify the currently serving beam and select the correct CORESET to send SIB1.

[0156] In some implementations, the retransmission parameters of the first downlink channel can be carried in one or more of the following information: DCI, RRC signaling, master information block (MIB), SIB1.

[0157] As one implementation, when the first downlink channel transmits the PDSCH of message 4, the number of retransmissions of the PDSCH can be determined through DCI scheduling. As an example, DCI can schedule a portion of the fields in message 4 to indicate the number of retransmissions of the PDSCH. This portion of the fields can be existing fields in DCI or new fields with reserved bits. The existing fields can be the modulation and coding scheme (MCS) field. As another example, DCI can provide specific retransmission indications for the terminal device or configure the retransmission parameters of message 4.

[0158] As one implementation, when the first downlink channel is transmitting a PDSCH for SIB1, the time-domain resources for repeated transmission can be determined through DCI scheduling. For example, when the first downlink channel is transmitting a PDSCH for SIB1, the time-domain resources for PDSCH transmission include two transmission time slots. The first transmission time slot can be scheduled for SIB1 through DCI, with K0 used to determine the start time of the PDSCH (the offset of the PDCCH relative to the PDSCH); the second transmission time slot can be fixed at K0+1 to ensure that the second PDSCH transmission is completed within 20ms. Furthermore, when indicating repeated PDSCH transmission through DCI scheduling for SIB1, a repeated indication bit for the PDSCH can be added to DCI 1_0 or DCI 1_1 (scheduling PDSCH). Additionally, the repeated transmission parameters for the PDSCH can be indicated using 15 reserved bits in the DCI. One of these 15 reserved bits can also be used to indicate whether repeated transmission of the PDSCH is enabled. For example, when SIB1 is implicitly indicated to repeat via PDCCH, a special RNTI or resource mapping mode of PDCCH can be used to implicitly indicate whether repeat transmission is enabled for SIB1.

[0159] As an implementation approach, the RRC layer can pre-configure the number of retransmissions for the first downlink channel. For example, RRC signaling can indicate the number of retransmissions for the PDSCH of transmission message 4. This approach is suitable for network environments with relatively little change, i.e., fixed or semi-static scenarios, such as the NTN scenario for high-orbit satellites, to reduce the overhead of DCI signaling.

[0160] As one implementation, retransmission parameters can be indicated via physical layer SIB broadcast. For example, SIBs can be used to broadcast the number of retransmissions for the first downlink channel, a method suitable for scenarios where network devices want all terminal devices to use the same retransmission configuration. In NTN scenarios, this method can reduce the interaction between terminal devices and network devices.

[0161] As one implementation, when SIB1 is transmitted on the first downlink channel, the network side can enable repeated transmission of SIB1 indicated by MIB.

[0162] As one implementation, when the first downlink channel is PDCCH, the network device can also indicate its repeated transmission via MIB. For example, to enable inter-slot repetition of PDCCH of type 0PDCCH CSS, searchSpaceZero is configured in MIB PDCCH-ConfigSIB1 to enable PDCCH repeated transmission. Alternatively, the network device can use a spare 1-bit bit in the MIB, a reserved bit in the PBCH payload, or reuse code points in the PBCH payload for indication. During the initial access of the terminal device, the terminal device will perform blind decoding without network signaling.

[0163] In the above implementation, for type 0 PDCCH, the MIB provides the terminal device with the CORESET0 and CSS Type0 configurations required to receive the relevant PDCCH. The terminal device can determine the CORESET of the configuration-related CSS set from the MIB. The controlResourceSetZero in PDCCH-ConfigSIB1 can indicate the number of consecutive resource blocks and consecutive symbols of the CSS set in the CORESET.

[0164] In the above implementation, when PDCCH retransmission is enabled via searchSpaceZero configured in MIB PDCCH-ConfigSIB1, this method supports repetitive PDCCH candidates in two consecutive time slots n0 and n0+1 associated with the same SSB index. As mentioned earlier, repetitive PDCCH candidates can share the same aggregation level, coded bits, and candidate index. If a network device repetitive a type 0 PDCCH in two consecutive time slots, the terminal device can decode the PDCCH and associated PDSCH in one time slot and skip PDCCH monitoring in the other time slot. By repetitively transmitting PDCCH in two consecutive time slots, the success rate of PDCCH decoding can be improved, especially in cases of poor channel quality (such as edge users).

[0165] In some implementations, the repetition parameters of the first downlink channel can be dynamically adjusted according to actual conditions to improve transmission efficiency. As one implementation, the repetition parameters of the first downlink channel are adjusted based on one or more of the following: terminal device capability information; the current channel quality of the first downlink channel; and feedback information related to the first downlink channel. The capability information indicates the repetition parameters of the downlink channels supported by the terminal device.

[0166] As one implementation, the terminal device can send capability information to the network device. This capability information indicates the repetition parameters of the downlink channels supported by the terminal device, ensuring that these parameters remain within the terminal device's capabilities. Capability information can also be used by the network device to determine or update the repetition parameters of the downlink channels, thereby enabling dynamic adaptation based on the terminal device's capabilities. For example, if the terminal device has the relevant capabilities, it can report its capabilities related to the repetition of message 4 in the physical uplink shared channel (PUSCH) transmitting message 3 (Msg3). Furthermore, in an NR NTN scenario, when the first downlink channel is a PDSCH with message 4, the repetition parameters involve indicating the repetition factor and reporting the terminal device's capabilities.

[0167] For example, based on the terminal device capability report at the time of RRC connection establishment, the network device can dynamically decide whether to enable PDCCH retransmission for a specific terminal device to ensure that terminal devices with different capabilities can decode correctly.

[0168] For example, a terminal device can report multiple retransmission factors that it can support. For instance, when a terminal device reports capability information via PUSCH in transmission message 3, this capability information can be carried in the medium access control element (MAC-CE) or RRC signaling.

[0169] In the above implementation, the network device can also group the terminal devices according to their capabilities. Taking the repetition of consecutive time slots as an example, for a group of terminal devices that support repeated transmission of downlink channels, the first downlink channel can be repeatedly transmitted in consecutive time slots n0 and n0+1; for a group of terminal devices that do not support repeated transmission of downlink channels, the first downlink channel is scheduled only in a single time slot to avoid decoding anomalies caused by repeated transmission of downlink channels on the terminal device side.

[0170] As one implementation, the terminal device can send the current channel quality of the first downlink channel to the network device. This current channel quality can be used by the network device to update the retransmission parameters of the first downlink channel. For scenarios with poor channel conditions, the network device can automatically increase the number of retransmissions during scheduling without requiring additional DCI signaling. This approach not only provides high flexibility but also adapts to the actual communication needs of different terminal devices or different channel environments.

[0171] As one implementation, the terminal device can send capability information and current channel quality to the network device. This capability information and current channel quality can then be used by the network device to update the repetition parameters of the first or second downlink channel. For example, the network device can dynamically adjust the repetition factor of the first downlink channel based on feedback from the terminal device (such as supported repetition capabilities and current channel quality).

[0172] As one implementation, the feedback information related to the first downlink channel can include adaptive adjustments based on hybrid automatic repeat request (HARQ) feedback. For example, the network device can adjust the repetition factor of the PDSCH based on the acknowledgement (ACK) / negative acknowledgement (NACK) feedback for message 4. If the PDSCH transmitting message 4 fails to be decoded successfully, the network device can increase the repetition factor during rescheduling. This approach does not require prior indication of the repetition factor but allows for adaptive adjustment based on real-time feedback.

[0173] The above, with reference to Figures 4 to 6, describes an embodiment of a method for a terminal device to receive a repeatedly transmitted first downlink channel according to first indication information. The first downlink channel can be a data channel or a control channel. When the first downlink channel is a PDCCH, the first indication information also includes a configuration of the search space corresponding to PDCCH repetition. PDCCH repetition can be replaced by repeated transmission of the PDCCH. This configuration is used to indicate that PDCCH repetition is either a PDCCH repeated transmission within the search space or a PDCCH repeated transmission across the search space.

[0174] A PDCCH repetition includes multiple PDCCHs. The number of PDCCHs included in a PDCCH repetition is determined by the number of repetitions. Multiple PDCCHs are transmitted over specified time units. In some implementations, multiple PDCCHs are transmitted over multiple time units. Multiple PDCCHs correspond to multiple time unit indices, which are the indices used to transmit the multiple PDCCHs.

[0175] As one implementation, multiple time unit indices correspond one-to-one with multiple time units. For example, when the time unit is a time slot, multiple time units can correspond to multiple time slots. Multiple PDCCHs are transmitted on these multiple time slots.

[0176] In some implementations, the search space for the PDCCH can indicate candidate locations that the terminal device needs to monitor. If configured improperly, the terminal device may miss PDCCH transmissions. Therefore, for repeated PDCCH transmissions, the search space set needs to be managed uniformly. For example, in repeated transmissions of non-contiguous time slots, multiple search space sets need to be configured, and an association mechanism should be used to ensure that the PDCCH can be correctly decoded in each time slot. If the NTN's terminal device cannot correctly predict which time slots the PDCCH will repeat, blind decoding needs to be performed in each time slot, increasing computational complexity and power consumption.

[0177] In some implementations, the multiple time unit indices corresponding to multiple PDCCHs can be determined based on one or more of the following information: one or more control resource set (CORESET) IDs corresponding to the search space ID and the search space ID; the search space ID and one or more search space sets corresponding to the search space ID; the indication information carried by the first PDCCH among the multiple PDCCHs; and the association information between the search space set and the HARQ feedback. The search space ID is the ID of the search space corresponding to the multiple PDCCHs. The configuration parameters of this search space can indicate the search space ID, and can also indicate the aforementioned information related to the search space set.

[0178] As an implementation approach, a Search Space ID (SS ID) can be introduced when configuring the search space corresponding to PDCCH repetition to simplify configuration signaling. The Search Space ID can be used to configure multiple search space sets corresponding to PDCCH repetition, associating any search space set with the transmission time unit of the corresponding PDCCH. Through search space set association, the terminal device monitors the PDCCH only in the specified time slot, thereby improving decoding efficiency. Furthermore, since NTN may schedule PDCCHs in different beam coverage areas, search space set association ensures that the PDCCH can still adapt to the current beam status in different time slots, improving reliability.

[0179] As an implementation, network devices can configure the association between search space sets and time units based on RRC signaling. When multiple search space sets are configured via RRC, RRC parameters can be used to explicitly associate the search space sets and time units to ensure that NTN terminal devices can monitor the PDCCH in multiple non-contiguous time slots. For example, RRC parameters can include the SearchSpaceSetList from PDCCH-Config to define multiple search space sets. RRC parameters can also include search space IDs and slot mappings. The search space ID can be associated with the CORESET ID and / or the search space set to ensure that NTN terminal devices correctly match the PDCCH position in different time slots. The slot mapping indicates in which time slots the PDCCH needs to be repeatedly transmitted.

[0180] For example, a search space ID can correspond to one or more CORESET IDs, allowing the configuration of CORESETs to determine multiple time unit indices corresponding to multiple PDCCHs. One search space ID can correspond to one CORESET ID.

[0181] For example, a search space ID can correspond to one or more search space sets, so that the association between the search space set and the time unit can be used to determine the multiple time unit indices corresponding to multiple PDCCHs. One search space ID can correspond to one or more search space sets.

[0182] As one implementation, the repeated search space of PDCCH corresponds to a search space ID. This search space ID corresponds to multiple search space sets, and these multiple search space sets correspond one-to-one with multiple time unit indices. When multiple time units are multiple time slots, these time slots can be consecutive or non-consecutive. Table 1 illustrates this using non-consecutive time slots as an example.

[0183] Table 1

[0184] As shown in Table 1, time slots n, n+3, and n+6 associated with search space 1 are used to repeatedly transmit multiple PDCCHs corresponding to search space 1. Time slots n+1, n+4, and n+7 associated with search space 2 are used to repeatedly transmit the PDCCHs corresponding to search space 2. The three time slots associated with search space 1 and search space 2 are non-contiguous time slots, and each time slot corresponds to a different search space set.

[0185] As one implementation, a network device can indicate multiple time unit indices based on a DCI (PDCCH). This DCI can be indication information carried by the first PDCCH among the multiple PDCCHs. This indication information can indicate the time unit index of the second PDCCH among the multiple PDCCHs, and the transmission time of the first PDCCH is earlier than the transmission time of the second PDCCH. The first PDCCH can be any PDCCH among the multiple PDCCHs except the last one. When the first PDCCH is the first PDCCH among the multiple PDCCHs, the second PDCCH can be one or more PDCCHs among the multiple PDCCHs except the first PDCCH.

[0186] For example, the indication information (DCI) carried by the first PDCCH can indicate in which non-contiguous time slots the second PDCCH will be repeated, ensuring that NTN terminal devices monitor the PDCCH only in the specified time slots, as shown in Table 2. The core fields of this DCI may include a PDCCH repetition indication field to notify the terminal device which non-contiguous time slots will be used to retransmit the PDCCH in the future. The core fields of this DCI may also include a HARQ process ID association field to ensure that NTN terminal devices can correctly match the PDCCH and the corresponding HARQ feedback.

[0187] Table 2

[0188] As shown in Table 2, search space sets 1 to 3 are associated with time slots n, n+3, and n+6, respectively. A DCI sent in time slot n indicates that PDCCH will be repeatedly transmitted in time slot n+3, allowing the terminal device to monitor PDCCH. A DCI sent in time slot n+3 indicates that PDCCH will be repeatedly transmitted in time slot n+6, also allowing the terminal device to monitor PDCCH. If time slot n+3 does not send a DCI related to PDCCH retransmission, or if the DCI does not indicate further retransmission, it indicates that the current retransmission has ended.

[0189] As one implementation, network devices can drive PDCCH monitoring and time unit association based on HARQ feedback. During search space configuration, the association information between the search space set and HARQ feedback can be configured. This association information can determine the search space set containing the PDCCH that needs to be monitored based on the HARQ feedback. When multiple time unit indices correspond to multiple time slots, HARQ feedback can instruct the terminal device to monitor PDCCH repetition on a portion of the multiple time slots. This portion of the multiple time slots does not include the transmission time slot of the PDCCH corresponding to the HARQ feedback. This portion of the time slots can refer to one or more time slots following the transmission time slot.

[0190] For example, high latency in NTN (such as GEO satellites) or loss of HARQ feedback may cause PDCCH decoding failure. Based on HARQ feedback-driven search space set association, network devices can use HARQ-ACK / NACK feedback to indicate to terminal devices in which time slots they need to continue monitoring PDCCH, as shown in Table 3. For example, if a terminal device fails to monitor the PDCCH in time slot n, it will continue monitoring in the next associated search space set. Based on this approach, NTN terminal devices can continue monitoring PDCCH only after a failure, avoiding additional decoding overhead. Since PDCCH monitoring is only continued when needed, the blind decoding burden on terminal devices can also be reduced.

[0191] Table 3

[0192] As shown in Table 3, search space sets 1 to 3 are associated with time slots n, n+3, and n+6, respectively. HARQ feedback indicates the PDCCH monitoring results for different time slots. In time slot n corresponding to search space set 1, the terminal device monitors the PDCCH. In time slot n+3 corresponding to search space set 2, the terminal device continues monitoring even if monitoring in time slot n fails. Monitoring failure can refer to PDCCH reception or decoding failure. In time slot n+6 corresponding to search space set 3, the terminal device continues monitoring even if monitoring in time slot n+3 fails. It should be noted that Table 3 only indicates monitoring failure as an example. In some scenarios, even if PDCCH is successfully monitored in a certain time slot, the terminal device may still need to continue monitoring PDCCH in subsequent time slots.

[0193] In some implementations, various combinations of PDCCH retransmission and search space expansion can be used to achieve maximum system energy efficiency. For example, in some scenarios, retransmission of consecutive time slots and search space expansion can be used to ensure that the terminal device can decode the PDCCH in multiple consecutive time slots, improving reliability. In other scenarios, retransmission of non-consecutive time slots and PDCCH soft combining can be used to reduce the impact of latency on PDCCH reception success rate.

[0194] As one implementation, when the satellite orbit altitude in the NTN falls within a first altitude range, PDCCH repetition can be transmitted over multiple consecutive time units to improve reliability; when the satellite orbit altitude in the NTN falls within a second altitude range, PDCCH repetition is transmitted over multiple non-consecutive time units to reduce latency. Specifically, all altitudes within the first altitude range are lower than all altitudes within the second altitude range. Alternatively, the maximum value in the first altitude range is lower than the minimum value in the second altitude range.

[0195] For example, for LEO / MEO scenarios, continuous time-slot PDCCH transmission and search space set expansion are used; for GEO scenarios, non-continuous time-slot PDCCH transmission and PDCCH soft merging are used to reduce the impact of long latency on PDCCH success rate in GEO scenarios.

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

[0197] Figure 7 is a schematic block diagram of a device for wireless communication according to an embodiment of this application. The device 700 can be any of the terminal devices described above. The device 700 shown in Figure 7 includes a receiving unit 710.

[0198] The receiving unit 710 can be used to receive a first downlink channel according to a first indication information; wherein the first indication information is associated with the retransmission of the first downlink channel, and the first downlink channel is used by the terminal device to establish a connection with the network device in the NTN; the first indication information includes the retransmission parameters of the first downlink channel, and / or the retransmission parameters of a second downlink channel related to the first downlink channel.

[0199] As one implementation, the retransmission parameters include one or more of the following: number of retransmissions; retransmission type, including retransmissions between time units and retransmissions within time units; retransmission duration, used to indicate the time length for completing the retransmission; and time-domain resources for retransmission, used to indicate one or more time units corresponding to the retransmission.

[0200] In one implementation, the first downlink channel is a data channel, and the number of repeated transmissions is 2 or 4; or, the first downlink channel is a control channel, and the number of repeated transmissions is a positive integer greater than 1.

[0201] In one implementation, the first downlink channel is a data channel for transmitting SIBs, and the maximum time for completing the repeated transmission is 20 milliseconds.

[0202] As one implementation, the time-domain resource of the repeated transmission is multiple time units, and the repeated transmission is either intra-beam repeated transmission or inter-beam repeated transmission.

[0203] As one implementation, the time-domain resources of the repeated transmission are multiple non-contiguous time units, and the number X of time units between any two adjacent time units satisfies the following condition:

[0204] Where T represents the duration of a time unit, T max T represents the upper limit of latency. RTT The round-trip time is represented by γ, where γ represents the ratio between the upper limit of latency and the round-trip time.

[0205] In one implementation, the first indication information includes retransmission parameters of the first downlink channel, which are carried in one or more of the following information: DCI, RRC signaling, MIB, SIB1.

[0206] As one implementation, the information carrying the retransmission parameters is also used to indicate whether the first downlink channel enables retransmission.

[0207] In one implementation, the retransmission parameters of the first downlink channel are adjusted according to one or more of the following: the capability information of the terminal device, which indicates the retransmission parameters of the downlink channels supported by the terminal device; the current channel quality of the first downlink channel; and feedback information related to the first downlink channel.

[0208] In one implementation, the first downlink channel is a data channel for transmitting message 4 during the random access process, or the first downlink channel is a data channel for transmitting SIB1.

[0209] In one implementation, the second downlink channel is one of the following: a control channel for scheduling the first downlink channel; or a data channel received by the terminal device before receiving the first downlink channel.

[0210] In one implementation, the first downlink channel is the PDSCH for transmitting message 4, and the second downlink channel is the PDSCH for transmitting SIB1; or, the first downlink channel is the first PDSCH, and the second downlink channel is the PDCCH for scheduling the first PDSCH.

[0211] As one implementation, the second downlink channel is a PDCCH, which corresponds to a first transmission mode, and the first transmission mode is related to CSS.

[0212] As one implementation, when the transmission type of the first transmission mode corresponds to PDCCH Type0A CSS, the PDCCH supports repeated transmission between time slots; when the transmission type of the first transmission mode corresponds to PDCCH Type1 CSS or PDCCH Type2 CSS, the PDCCH supports repeated transmission within time slots and repeated transmission between time slots.

[0213] In one implementation, the first downlink channel is a PDCCH, and the first indication information also includes a configuration of the search space corresponding to the PDCCH repetition. The configuration is used to indicate that the PDCCH repetition is a PDCCH repetition transmission within the search space or a PDCCH repetition transmission across the search space.

[0214] As one implementation, the PDCCH repetition includes multiple PDCCHs, each corresponding to a multiple time unit index. The multiple time unit indexes are determined based on one or more of the following: a search space ID and one or more control resource set IDs corresponding to the search space ID; a search space ID and one or more search space sets corresponding to the search space ID; indication information carried by the first PDCCH among the multiple PDCCHs; and association information between the search space set and HARQ feedback.

[0215] In one implementation, the search space of the PDCCH repetition corresponds to a search space ID, the search space ID corresponds to multiple search space sets, and the multiple search space sets correspond one-to-one with the multiple time unit indices.

[0216] In one implementation, the indication information carried by the first PDCCH is used to indicate the time unit index of the second PDCCH among the plurality of PDCCHs, and the transmission time of the first PDCCH is earlier than the transmission time of the second PDCCH.

[0217] In one implementation, the multiple time unit indices correspond to multiple time slots, and the HARQ feedback is used to instruct the terminal device to monitor the PDCCH repetition on a portion of the multiple time slots.

[0218] In one implementation, the satellite orbit altitude in the NTN falls within a first altitude range, and the PDCCH is repeatedly transmitted within multiple consecutive time units; in another implementation, the satellite orbit altitude in the NTN falls within a second altitude range, and the PDCCH is repeatedly transmitted within multiple non-consecutive time units.

[0219] As one implementation, the apparatus 700 further includes a processing unit that can be used to merge multiple received first downlink channels; wherein the merging is related to the quality of at least one of the multiple first downlink channels.

[0220] In one implementation, the receiving unit 710 may be part of the transceiver 930, and the device 700 may also include a processor 910 and a memory 920, as shown in Figure 9.

[0221] Figure 8 is a schematic block diagram of another device for wireless communication according to an embodiment of this application. This device 800 can be any of the network devices described above. The device 800 shown in Figure 8 includes a transmitting unit 810.

[0222] The transmitting unit 810 can be used to perform repeated transmission of a first downlink channel according to a first indication information; wherein, the first downlink channel is used for the terminal device to establish a connection with the network device in the NTN; the first indication information includes repeated transmission parameters of the first downlink channel, and / or repeated transmission parameters of a second downlink channel related to the first downlink channel.

[0223] As one implementation, the retransmission parameters include one or more of the following: number of retransmissions; retransmission type, including retransmissions between time units and retransmissions within time units; retransmission duration, used to indicate the time length for completing the retransmission; and time-domain resources for retransmission, used to indicate one or more time units corresponding to the retransmission.

[0224] In one implementation, the first downlink channel is a data channel, and the number of repeated transmissions is 2 or 4; or, the first downlink channel is a control channel, and the number of repeated transmissions is a positive integer greater than 1.

[0225] In one implementation, the first downlink channel is a data channel for transmitting SIBs, and the maximum time for completing the repeated transmission is 20 milliseconds.

[0226] As one implementation, the time-domain resource of the repeated transmission is multiple time units, and the repeated transmission is either intra-beam repeated transmission or inter-beam repeated transmission.

[0227] As one implementation, the time-domain resources of the repeated transmission are multiple non-contiguous time units, and the number X of time units between any two adjacent time units satisfies the following condition:

[0228] Where T represents the duration of a time unit, T max T represents the upper limit of latency. RTT The round-trip time is represented by γ, where γ represents the ratio between the upper limit of latency and the round-trip time.

[0229] In one implementation, the first indication information includes retransmission parameters of the first downlink channel, which are carried in one or more of the following information: DCI, RRC signaling, MIB, SIB1.

[0230] As one implementation, the information carrying the retransmission parameters is also used to indicate whether the first downlink channel enables retransmission.

[0231] In one implementation, the retransmission parameters of the first downlink channel are adjusted according to one or more of the following: the capability information of the terminal device, which indicates the retransmission parameters of the downlink channels supported by the terminal device; the current channel quality of the first downlink channel; and feedback information related to the first downlink channel.

[0232] In one implementation, the first downlink channel is a data channel for transmitting message 4 during the random access process, or the first downlink channel is a data channel for transmitting SIB1.

[0233] In one implementation, the second downlink channel is one of the following: a control channel for scheduling the first downlink channel; or a data channel received by the terminal device before receiving the first downlink channel.

[0234] In one implementation, the first downlink channel is the PDSCH for transmitting message 4, and the second downlink channel is the PDSCH for transmitting SIB1; or, the first downlink channel is the first PDSCH, and the second downlink channel is the PDCCH for scheduling the first PDSCH.

[0235] As one implementation, the second downlink channel is a PDCCH, which corresponds to a first transmission mode, and the first transmission mode is related to CSS.

[0236] As one implementation, when the transmission type of the first transmission mode corresponds to PDCCH Type0A CSS, the PDCCH supports repeated transmission between time slots; when the transmission type of the first transmission mode corresponds to PDCCH Type1 CSS or PDCCH Type2 CSS, the PDCCH supports repeated transmission within time slots and repeated transmission between time slots.

[0237] In one implementation, the first downlink channel is a PDCCH, and the first indication information also includes a configuration of the search space corresponding to the PDCCH repetition. The configuration is used to indicate that the PDCCH repetition is a PDCCH repetition transmission within the search space or a PDCCH repetition transmission across the search space.

[0238] As one implementation, the PDCCH repetition includes multiple PDCCHs, each corresponding to a multiple time unit index. The multiple time unit indexes are determined based on one or more of the following: a search space ID and one or more control resource set IDs corresponding to the search space ID; a search space ID and one or more search space sets corresponding to the search space ID; indication information carried by the first PDCCH among the multiple PDCCHs; and association information between the search space set and HARQ feedback.

[0239] In one implementation, the search space of the PDCCH repetition corresponds to a search space ID, the search space ID corresponds to multiple search space sets, and the multiple search space sets correspond one-to-one with the multiple time unit indices.

[0240] In one implementation, the indication information carried by the first PDCCH is used to indicate the time unit index of the second PDCCH among the plurality of PDCCHs, and the transmission time of the first PDCCH is earlier than the transmission time of the second PDCCH.

[0241] In one implementation, the multiple time unit indices correspond to multiple time slots, and the HARQ feedback is used to instruct the terminal device to monitor the PDCCH repetition on a portion of the multiple time slots.

[0242] In one implementation, the satellite orbit altitude in the NTN falls within a first altitude range, and the PDCCH is repeatedly transmitted within multiple consecutive time units; in another implementation, the satellite orbit altitude in the NTN falls within a second altitude range, and the PDCCH is repeatedly transmitted within multiple non-consecutive time units.

[0243] In one implementation, the terminal device receives multiple first downlink channels for merging, and the merging is related to the quality of at least one of the multiple first downlink channels.

[0244] In one implementation, the transmitting unit 810 may be part of the transceiver 930, and the device 800 may also include a processor 910 and a memory 920, as shown in Figure 9.

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

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

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

[0248] The device 900 may also include a transceiver 930. The processor 910 can communicate with other devices or chips via the transceiver 930. For example, the processor 910 can send and receive data with other devices or chips via the transceiver 930.

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

[0250] The computer-readable storage medium can be any available medium that a computer can read, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

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

[0252] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.

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

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

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

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

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

[0258] In the embodiments of this application, determining B based on A or based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

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

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

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

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

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

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

Claims

1. A method for wireless communication, comprising: include: The terminal device receives the first downlink channel according to the first instruction information; The first indication information is associated with the repeated transmission of the first downlink channel, which is used by the terminal device to establish a connection with network devices in the non-terrestrial network (NTN). The first indication information includes the repeated transmission parameters of the first downlink channel and / or the repeated transmission parameters of a second downlink channel related to the first downlink channel.

2. The method of claim 1, wherein, The repeated transmission parameters include one or more of the following: Number of repeated transmissions; Repeated transmission types include repeated transmissions between time units and repeated transmissions within time units; Repeat transmission duration indicates the length of time required to complete a repeat transmission. Repeated transmission time-frequency resources include one or more time units used for repeated transmission.

3. The method of claim 2, wherein, The first downlink channel is a data channel, and the number of repeated transmissions is 2 or 4; or, the first downlink channel is a control channel, and the number of repeated transmissions is a positive integer greater than 1.

4. The method according to claim 2 or 3, characterized in that, The first downlink channel is a data channel for transmitting SIBs, and the maximum time for completing the repeated transmission is 20 milliseconds.

5. The method according to any one of claims 2 to 4, characterized in that, The time-domain resource of the repeated transmission is multiple time units, and the repeated transmission is either intra-beam repeated transmission or inter-beam repeated transmission.

6. The method according to any one of claims 2 to 5, characterized in that, The time domain resource of the repeated transmission is discontinuous multiple time units, and the number X of time units between any two adjacent time units in the multiple time units satisfies the following condition: wherein T represents a time length of a time unit, T max represents an upper limit of a time delay, T RTT represents a round-trip time of communication between the terminal device and the network device, and γ represents a ratio between the upper limit of the time delay and the round-trip time.

7. The method according to any one of claims 1 to 6, characterized in that, The first indication information includes the retransmission parameters of the first downlink channel, which are carried in one or more of the following information: downlink control information (DCI), radio resource control (RRC) signaling, master information block (MIB), and SIB1.

8. The method of claim 7, wherein, The information carrying the retransmission parameters is also used to indicate whether the first downlink channel enables retransmission.

9. The method according to any one of claims 1 to 8, characterized in that, The retransmission parameters of the first downlink channel are adjusted according to one or more of the following: The capability information of the terminal device, wherein the capability information is used to indicate the repetition transmission parameters of the downlink channels supported by the terminal device; The current channel quality of the first downlink channel; Feedback information related to the first downlink channel.

10. The method according to any one of claims 1 to 9, characterized in that, The first downlink channel is a data channel for transmitting message 4 in the random access process, or the first downlink channel is a data channel for transmitting SIB1.

11. The method of claim 10, wherein, The second downlink channel is one of the following: A control channel used for scheduling the first downlink channel; The terminal device receives the data channel before receiving the first downlink channel.

12. The method of claim 11, wherein, The first downlink channel is the Physical Downlink Shared Channel (PDSCH) for transmitting message 4, and the second downlink channel is the PDSCH for transmitting SIB1; or, the first downlink channel is the first PDSCH, and the second downlink channel is the Physical Downlink Control Channel (PDCCH) for scheduling the first PDSCH.

13. The method according to any one of claims 1 to 11, characterized in that, The second downlink channel is PDCCH, which corresponds to the first transmission mode, and the first transmission mode is related to the Common Search Space (CSS).

14. The method of claim 13, wherein, When the transmission type of the first transmission mode corresponds to PDCCH Type0A CSS, the PDCCH supports repeated transmission between time slots; when the transmission type of the first transmission mode corresponds to PDCCH Type1 CSS or PDCCH Type2 CSS, the PDCCH supports repeated transmission within time slots and repeated transmission between time slots.

15. The method according to any one of claims 1 to 9, characterized in that, The first downlink channel is PDCCH, and the first indication information also includes the configuration of the search space corresponding to PDCCH repetition. The configuration is used to indicate that the PDCCH repetition is a PDCCH repetition within the search space or a PDCCH repetition across the search space.

16. The method of claim 15, wherein, The PDCCH repetition includes multiple PDCCHs, each PDCCH corresponding to multiple time unit indices, which are determined based on one or more of the following information: The search space identifier ID and one or more control resource set IDs corresponding to the search space ID; Search space ID and one or more search space sets corresponding to the search space ID; The indication information carried by the first PDCCH among the plurality of PDCCHs; Search space set and related information in the HARQ (Hybrid Automatic Repeat Request) feedback.

17. The method of claim 16, wherein, The search space for the PDCCH repetition corresponds to a search space ID, the search space ID corresponds to multiple search space sets, and the multiple search space sets correspond one-to-one with the multiple time unit indices.

18. The method of claim 16 or 17, wherein, The indication information carried by the first PDCCH is used to indicate the time unit index of the second PDCCH among the plurality of PDCCHs, and the transmission time of the first PDCCH is earlier than the transmission time of the second PDCCH.

19. The method of any one of claims 16-18, wherein, The multiple time unit indices correspond to multiple time slots, and the HARQ feedback is used to instruct the terminal device to monitor the PDCCH repetition in a portion of the multiple time slots.

20. The method of any one of claims 15-19, wherein, The satellite orbit altitude in the NTN falls within a first altitude range, and the PDCCH is repeatedly transmitted within multiple consecutive time units; the satellite orbit altitude in the NTN falls within a second altitude range, and the PDCCH is repeatedly transmitted within multiple non-consecutive time units.

21. The method of any one of claims 1 to 20, wherein, After the terminal device receives the first downlink channel according to the first indication information, the method further includes: The terminal device merges the received first downlink channels; The merging is related to the quality of at least one of the plurality of first downlink channels.

22. A method for wireless communication, comprising: include: The network device performs repeated transmissions on the first downlink channel according to the first instruction information; The first downlink channel is used by the terminal device to establish a connection with the network device in the non-terrestrial network (NTN); the first indication information includes the repetition transmission parameters of the first downlink channel and / or the repetition transmission parameters of the second downlink channel related to the first downlink channel.

23. The method of claim 22, wherein, The repeated transmission parameters include one or more of the following: Number of repeated transmissions; Repeated transmission types include repeated transmissions between time units and repeated transmissions within time units; Repeat transmission duration indicates the length of time required to complete a repeat transmission. The time-domain resource for repeated transmissions is used to indicate one or more time units corresponding to repeated transmissions.

24. The method of claim 23, wherein, The first downlink channel is a data channel, and the number of repeated transmissions is 2 or 4; or, the first downlink channel is a control channel, and the number of repeated transmissions is a positive integer greater than 1.

25. The method of claim 23 or 24, wherein, The first downlink channel is the data channel of the transmission system information block (SIB), and the maximum time length for completing the repeated transmission is 20 milliseconds.

26. The method of any one of claims 23-25, wherein, The time-domain resource of the repeated transmission is multiple time units, and the repeated transmission is either intra-beam repeated transmission or inter-beam repeated transmission.

27. The method of any one of claims 23-26, wherein, The time domain resource of the repeated transmission is discontinuous multiple time units, and the number X of time units between any two adjacent time units in the multiple time units satisfies the following condition: wherein T represents a time length of a time unit, T max represents an upper limit of a time delay, T RTT represents a round-trip time of communication between the terminal device and the network device, and γ represents a ratio between the upper limit of the time delay and the round-trip time.

28. The method of any one of claims 22-27, wherein, The first indication information includes the retransmission parameters of the first downlink channel, which are carried in one or more of the following information: downlink control information (DCI), radio resource control (RRC) signaling, master information block (MIB), and SIB1.

29. The method of claim 28, wherein, The information carrying the retransmission parameters is also used to indicate whether the first downlink channel enables retransmission.

30. The method of any one of claims 22-29, wherein, The retransmission parameters of the first downlink channel are adjusted according to one or more of the following: The capability information of the terminal device, wherein the capability information is used to indicate the repetition transmission parameters of the downlink channels supported by the terminal device; The current channel quality of the first downlink channel; Feedback information related to the first downlink channel.

31. The method of any one of claims 22-30, wherein, The first downlink channel is a data channel for transmitting message 4 in the random access process, or the first downlink channel is a data channel for transmitting SIB1.

32. The method of claim 31, wherein, The second downlink channel is one of the following: A control channel used for scheduling the first downlink channel; The terminal device receives the data channel before receiving the first downlink channel.

33. The method of claim 32, wherein, The first downlink channel is the Physical Downlink Shared Channel (PDSCH) for transmitting message 4, and the second downlink channel is the PDSCH for transmitting SIB1; or, the first downlink channel is the first PDSCH, and the second downlink channel is the Physical Downlink Control Channel (PDCCH) for scheduling the first PDSCH.

34. The method of any one of claims 22-32, wherein, The second downlink channel is PDCCH, which corresponds to the first transmission mode, and the first transmission mode is related to the Common Search Space (CSS).

35. The method of claim 34, wherein, When the transmission type of the first transmission mode corresponds to PDCCH Type0A CSS, the PDCCH supports repeated transmission between time slots; when the transmission type of the first transmission mode corresponds to PDCCH Type1 CSS or PDCCH Type2 CSS, the PDCCH supports repeated transmission within time slots and repeated transmission between time slots.

36. The method of any one of claims 22-30, wherein, The first downlink channel is PDCCH, and the first indication information also includes the configuration of the search space corresponding to PDCCH repetition. The configuration is used to indicate that the PDCCH repetition is a PDCCH repetition transmission within the search space or a PDCCH repetition transmission across the search space.

37. The method of claim 36, wherein, The PDCCH repetition includes multiple PDCCHs, each PDCCH corresponding to multiple time unit indices, which are determined based on one or more of the following information: The search space identifier ID and one or more control resource set IDs corresponding to the search space ID; Search space ID and one or more search space sets corresponding to the search space ID; The indication information carried by the first PDCCH among the plurality of PDCCHs; Search space set and related information in the HARQ (Hybrid Automatic Repeat Request) feedback.

38. The method of claim 37, wherein, The search space for the PDCCH repetition corresponds to a search space ID, the search space ID corresponds to multiple search space sets, and the multiple search space sets correspond one-to-one with the multiple time unit indices.

39. The method of claim 37 or 38, wherein, The indication information carried by the first PDCCH is used to indicate the time unit index of the second PDCCH among the plurality of PDCCHs, and the transmission time of the first PDCCH is earlier than the transmission time of the second PDCCH.

40. The method of any one of claims 37-39, wherein, The multiple time unit indices correspond to multiple time slots, and the HARQ feedback is used to instruct the terminal device to monitor the PDCCH repetition in a portion of the multiple time slots.

41. The method of any one of claims 36-40, wherein, The satellite orbit altitude in the NTN falls within a first altitude range, and the PDCCH is repeatedly transmitted within multiple consecutive time units; the satellite orbit altitude in the NTN falls within a second altitude range, and the PDCCH is repeatedly transmitted within multiple non-consecutive time units.

42. The method of any one of claims 22-41, wherein, The terminal device receives multiple first downlink channels for merging, and the merging is related to the quality of at least one of the multiple first downlink channels.

43. A device for wireless communication, characterized in that, The device is a terminal device, and the device includes: The receiving unit is configured to receive the first downlink channel according to the first indication information; The first indication information is associated with the repeated transmission of the first downlink channel, which is used by the terminal device to establish a connection with network devices in the non-terrestrial network (NTN). The first indication information includes the repeated transmission parameters of the first downlink channel and / or the repeated transmission parameters of a second downlink channel related to the first downlink channel.

44. The device of claim 43, wherein, The repeated transmission parameters include one or more of the following: Number of repeated transmissions; Repeated transmission types include repeated transmissions between time units and repeated transmissions within time units; Repeat transmission duration indicates the length of time required to complete a repeat transmission. Repeated transmission time-frequency resources include one or more time units used for repeated transmission.

45. The device of claim 44, wherein, The first downlink channel is a data channel, and the number of repeated transmissions is 2 or 4; or, the first downlink channel is a control channel, and the number of repeated transmissions is a positive integer greater than 1.

46. The device of claim 44 or 45, wherein, The first downlink channel is a data channel for transmitting SIBs, and the maximum time for completing the repeated transmission is 20 milliseconds.

47. The apparatus of any one of claims 44-46, wherein, The time-domain resource of the repeated transmission is multiple time units, and the repeated transmission is either intra-beam repeated transmission or inter-beam repeated transmission.

48. The apparatus of any one of claims 44-47, wherein, The time domain resource of the repeated transmission is discontinuous multiple time units, and the number X of time units between any two adjacent time units in the multiple time units satisfies the following condition: wherein T represents a time length of a time unit, T max represents an upper limit of a time delay, T RTT represents a round-trip time of communication between the terminal device and the network device, and γ represents a ratio between the upper limit of the time delay and the round-trip time.

49. The apparatus of any one of claims 43-48, wherein, The first indication information includes the retransmission parameters of the first downlink channel, which are carried in one or more of the following information: downlink control information (DCI), radio resource control (RRC) signaling, master information block (MIB), and SIB1.

50. The device of claim 49, wherein, The information carrying the retransmission parameters is also used to indicate whether the first downlink channel enables retransmission.

51. The apparatus of any one of claims 43-50, wherein, The retransmission parameters of the first downlink channel are adjusted according to one or more of the following: The capability information of the terminal device, wherein the capability information is used to indicate the repetition transmission parameters of the downlink channels supported by the terminal device; The current channel quality of the first downlink channel; Feedback information related to the first downlink channel.

52. The apparatus of any one of claims 43-51, wherein, The first downlink channel is a data channel for transmitting message 4 in the random access process, or the first downlink channel is a data channel for transmitting SIB1.

53. The device of claim 52, wherein, The second downlink channel is one of the following: A control channel used for scheduling the first downlink channel; The terminal device receives the data channel before receiving the first downlink channel.

54. The device of claim 53, wherein, The first downlink channel is the Physical Downlink Shared Channel (PDSCH) for transmitting message 4, and the second downlink channel is the PDSCH for transmitting SIB1; or, the first downlink channel is the first PDSCH, and the second downlink channel is the Physical Downlink Control Channel (PDCCH) for scheduling the first PDSCH.

55. The apparatus of any one of claims 43-53, wherein, The second downlink channel is PDCCH, which corresponds to the first transmission mode, and the first transmission mode is related to the Common Search Space (CSS).

56. The device of claim 55, wherein, When the transmission type of the first transmission mode corresponds to PDCCH Type0A CSS, the PDCCH supports repeated transmission between time slots; when the transmission type of the first transmission mode corresponds to PDCCH Type1 CSS or PDCCH Type2 CSS, the PDCCH supports repeated transmission within time slots and repeated transmission between time slots.

57. The apparatus of any one of claims 43-51, wherein, The first downlink channel is PDCCH, and the first indication information also includes the configuration of the search space corresponding to PDCCH repetition. The configuration is used to indicate that the PDCCH repetition is a PDCCH repetition within the search space or a PDCCH repetition across the search space.

58. The device of claim 57, wherein, The PDCCH repetition includes multiple PDCCHs, each PDCCH corresponding to multiple time unit indices, which are determined based on one or more of the following information: The search space identifier ID and one or more control resource set IDs corresponding to the search space ID; Search space ID and one or more search space sets corresponding to the search space ID; The indication information carried by the first PDCCH among the plurality of PDCCHs; Search space set and related information in the HARQ (Hybrid Automatic Repeat Request) feedback.

59. The device of claim 58, wherein, The search space for the PDCCH repetition corresponds to a search space ID, the search space ID corresponds to multiple search space sets, and the multiple search space sets correspond one-to-one with the multiple time unit indices.

60. The device of claim 58 or 59, wherein, The indication information carried by the first PDCCH is used to indicate the time unit index of the second PDCCH among the plurality of PDCCHs, and the transmission time of the first PDCCH is earlier than the transmission time of the second PDCCH.

61. The device of any one of claims 58-60, wherein, The multiple time unit indices correspond to multiple time slots, and the HARQ feedback is used to instruct the terminal device to monitor the PDCCH repetition in a portion of the multiple time slots.

62. The apparatus of any one of claims 57-61, wherein, The satellite orbit altitude in the NTN falls within a first altitude range, and the PDCCH is repeatedly transmitted within multiple consecutive time units; the satellite orbit altitude in the NTN falls within a second altitude range, and the PDCCH is repeatedly transmitted within multiple non-consecutive time units.

63. The device of any one of claims 43-62, wherein, The device further includes: A processing unit is used to combine multiple received first downlink channels; The merging is related to the quality of at least one of the plurality of first downlink channels.

64. An apparatus for wireless communication, the apparatus comprising: The device is a network device, and the device includes: The transmitting unit is used to perform repeated transmission of the first downlink channel according to the first indication information; The first downlink channel is used by the terminal device to establish a connection with the network device in the non-terrestrial network (NTN); the first indication information includes the repetition transmission parameters of the first downlink channel and / or the repetition transmission parameters of the second downlink channel related to the first downlink channel.

65. The device of claim 64, wherein, The repeated transmission parameters include one or more of the following: Number of repeated transmissions; Repeated transmission types include repeated transmissions between time units and repeated transmissions within time units; Repeat transmission duration indicates the length of time required to complete a repeat transmission. The time-domain resource for repeated transmissions is used to indicate one or more time units corresponding to repeated transmissions.

66. The device of claim 65, wherein, The first downlink channel is a data channel, and the number of repeated transmissions is 2 or 4; or, the first downlink channel is a control channel, and the number of repeated transmissions is a positive integer greater than 1.

67. The device of claim 65 or 66, wherein, The first downlink channel is the data channel of the transmission system information block (SIB), and the maximum time length for completing the repeated transmission is 20 milliseconds.

68. The device of any one of claims 65-67, wherein, The time-domain resource of the repeated transmission is multiple time units, and the repeated transmission is either intra-beam repeated transmission or inter-beam repeated transmission.

69. The device of any one of claims 65-68, wherein, The time domain resource of the repeated transmission is discontinuous multiple time units, and the number X of time units between any two adjacent time units in the multiple time units satisfies the following condition: wherein T represents a time length of a time unit, T max represents an upper limit of the time delay, T RTT represents a round-trip time of communication between the terminal device and the network device, and γ represents a ratio between the upper limit of the time delay and the round-trip time.

70. The device of any one of claims 64-69, wherein, The first indication information includes the retransmission parameters of the first downlink channel, which are carried in one or more of the following information: downlink control information (DCI), radio resource control (RRC) signaling, master information block (MIB), and SIB1.

71. The device of claim 70, wherein, The information carrying the retransmission parameters is also used to indicate whether the first downlink channel enables retransmission.

72. The device of any one of claims 64-71, wherein, The retransmission parameters of the first downlink channel are adjusted according to one or more of the following: The capability information of the terminal device, wherein the capability information is used to indicate the repetition transmission parameters of the downlink channels supported by the terminal device; The current channel quality of the first downlink channel; Feedback information related to the first downlink channel.

73. The device of any one of claims 64-72, wherein, The first downlink channel is a data channel for transmitting message 4 in the random access process, or the first downlink channel is a data channel for transmitting SIB1.

74. The device of claim 73, wherein, The second downlink channel is one of the following: A control channel used for scheduling the first downlink channel; The terminal device receives the data channel before receiving the first downlink channel.

75. The device of claim 74, wherein, The first downlink channel is the Physical Downlink Shared Channel (PDSCH) for transmitting message 4, and the second downlink channel is the PDSCH for transmitting SIB1; or, the first downlink channel is the first PDSCH, and the second downlink channel is the Physical Downlink Control Channel (PDCCH) for scheduling the first PDSCH.

76. The device of any one of claims 64-74, wherein, The second downlink channel is PDCCH, which corresponds to the first transmission mode, and the first transmission mode is related to the Common Search Space (CSS).

77. The device of claim 76, wherein, When the transmission type of the first transmission mode corresponds to PDCCH Type0A CSS, the PDCCH supports repeated transmission between time slots; when the transmission type of the first transmission mode corresponds to PDCCH Type1 CSS or PDCCH Type2 CSS, the PDCCH supports repeated transmission within time slots and repeated transmission between time slots.

78. The device of any one of claims 64-72, wherein, The first downlink channel is PDCCH, and the first indication information also includes the configuration of the search space corresponding to PDCCH repetition. The configuration is used to indicate that the PDCCH repetition is a PDCCH repetition within the search space or a PDCCH repetition across the search space.

79. The device of claim 64, wherein, The PDCCH repetition includes multiple PDCCHs, each PDCCH corresponding to multiple time unit indices, which are determined based on one or more of the following information: The search space identifier ID and one or more control resource set IDs corresponding to the search space ID; Search space ID and one or more search space sets corresponding to the search space ID; The indication information carried by the first PDCCH among the plurality of PDCCHs; Search space set and related information in the HARQ (Hybrid Automatic Repeat Request) feedback.

80. The device of claim 79, wherein, The search space for the PDCCH repetition corresponds to a search space ID, the search space ID corresponds to multiple search space sets, and the multiple search space sets correspond one-to-one with the multiple time unit indices.

81. The device of claim 79 or 80, wherein, The indication information carried by the first PDCCH is used to indicate the time unit index of the second PDCCH among the plurality of PDCCHs, and the transmission time of the first PDCCH is earlier than the transmission time of the second PDCCH.

82. The device of any one of claims 79-81, wherein, The multiple time unit indices correspond to multiple time slots, and the HARQ feedback is used to instruct the terminal device to monitor the PDCCH repetition in a portion of the multiple time slots.

83. The device of any one of claims 78-82, wherein, The satellite orbit altitude in the NTN falls within a first altitude range, and the PDCCH is repeatedly transmitted within multiple consecutive time units; the satellite orbit altitude in the NTN falls within a second altitude range, and the PDCCH is repeatedly transmitted within multiple non-consecutive time units.

84. The device of any of claims 64-83, wherein, The terminal device receives multiple first downlink channels for merging, and the merging is related to the quality of at least one of the multiple first downlink channels.

85. A communications device, characterized by The method includes a memory and a processor, the memory being used to store a program and the processor being used to invoke the program in the memory to perform the method as claimed in any one of claims 1 to 21 or 22 to 42.

86. An apparatus comprising: Includes a processor for calling a program from memory to perform the method as described in any one of claims 1 to 21 or 22 to 42.

87. A chip, comprising: Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 21 or 22 to 42.

88. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1 to 21 or 22 to 42.

89. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1 to 21 or 22 to 42.

90. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1 to 21 or 22 to 42.